Method and apparatus for measuring gaps

Abstract

The logic may determine the frequency range of the PRS based on the PRS configuration, where the PRS configuration defines the resource blocks of the PRS frequency layer. The logic may determine a number of frequency hops between the frequency layers associated with the PRS frequency range during one measurement gap iteration based on the measurement gap configuration per UE, or during up to two measurement gap iterations based on the measurement gap configuration per frequency range (FR), in order to perform PRS measurements within at least one measurement delay. The logic may perform the number of frequency hops and PRS measurements during each of the one measurement gap iterations or up to two measurement gap iterations. The logic may then transmit at least one positioning measurement report via the interface.

Description

[Technical Field]

[0001] Cross-reference of related applications This application also claims priority under 35 U.S.C. § 119 from U.S. Provisional Application No. 63 / 494,677, filed on April 6, 2023, titled "MEASUREMENT GAPS FOR REDCAP USER EQUIPMENT POSITIONING WITH RECEIVER HOPPING," the subject matter of which is incorporated herein by reference. [Background technology]

[0002] Wireless communication technology is growing rapidly, and demand is increasing. Demand for reduced-capacity 5G devices is rapidly increasing. RedCap (New Radio) NR devices aim to simplify user equipment (UE) complexity while maintaining essential functionality. These devices are designed to operate efficiently with lower power consumption and relaxed performance characteristics.

[0003] RedCap NR reduces UE complexity through several mechanisms. For example, RedCap NR can reduce the number of receive and transmit (RX / TX) antennas, lower bandwidth requirements, reduce and / or optimize UE power consumption or power usage, relax data rates to less stringent data rate requirements, reduce processing demands to mitigate UE processing time, and adapt processing capabilities for specific use cases.

[0004] Some use cases for Redcap UE may include industrial wireless sensors for monitoring and control applications, video surveillance for efficient camera deployment, and wearable devices with reduced complexity. [Brief explanation of the drawing]

[0005] [Figure 1] Figure 1 shows one embodiment of a system that includes base stations, user equipment, and cloud-based computing and data services, all interconnected via a communication network. [Figure 2] Figure 2 shows another embodiment of the network, following various embodiments such as the network shown in Figure 1. [Figure 3] Figure 3 shows another embodiment of the network according to various embodiments. [Figure 4] Figure 4 shows one embodiment of a simplified block diagram relating to artificial intelligence (AI)-assisted communication between a UE and a RAN, according to various embodiments. [Figure 5] Figure 5 is one embodiment of a simplified block diagram relating to a base station and user equipment (UE), including the base station or RAN, user equipment (UE), and communication network shown in Figures 1-4. [Figure 6] Figure 6 shows a table of gap combination configurations. [Figure 7] Figure 7 shows a flowchart of one embodiment for a user device, such as the embodiments described in relation to Figures 1-6. [Figure 8] Figure 8 shows one embodiment of a protocol entity that may be implemented in a wireless communication device. [Figure 9] Figure 9 shows embodiments relating to a format for a PHY data unit (PDU) that is transmitted by a PHY device via one or more antennas and can be encoded and decoded by MAC entities such as the processor in Figure 5 and the baseband circuits in Figures 5, 13, and 14, according to several embodiments. [Figure 10A] Figure 10A shows an embodiment of a communication circuit, including the user equipment and the components and modules shown in Figure 5. [Figure 10B] Figure 10B shows an embodiment of a communication circuit, including the user equipment and the components and modules shown in Figure 5. [Figure 11] Figure 11 shows one embodiment relating to the storage medium described herein. [Figure 12] Figure 12 shows an architecture of a network system according to several embodiments. [Figure 13] Figure 13 shows exemplary components relating to devices according to several embodiments, such as the base station and UE shown in Figures 1-12. [Figure 14] Figure 14 shows an exemplary interface relating to a baseband circuit according to several embodiments, such as the baseband circuits shown and / or described in relation to Figures 1-13. [Figure 15] Figure 15 shows one embodiment relating to a block diagram of components for performing the functionality described. [Modes for carrying out the invention]

[0006] The following is a detailed description of the embodiments shown in the drawings. The detailed description covers all modifications, equivalents, and substitutions that fall within the scope of the attached claims.

[0007] Historically, the primary driver of location-based services has been regulatory requirements (e.g., emergency caller location requirements). However, today, many public and private entities demand the distribution of location information to enable commercially motivated location-based services, which often requires greater location accuracy and precision. Therefore, fifth-generation (5G) cellular networks support several enhanced location service capabilities and new radio (NR) native positioning technologies to address the diverse location requirements resulting from new applications and industry verticals.

[0008] 5G NR offers several enhanced parameters for positioning accuracy estimation compared to previous mobile generations, particularly with respect to time-based and angle-based positioning methods. New reference signals have been added to the NR specification to enable more accurate positioning measurements than Long-Term Evolution (LTE). These signals are the downlink positioning reference signal (NRPRS) and the uplink sounding reference signal (SRS). The downlink positioning reference signal (PRS) is the primary reference signal supporting downlink-based positioning methods. While other signals may be used, the PRS is specifically designed to deliver the highest possible level of accuracy, coverage, and interference avoidance and suppression. Special care has been taken to give the signal a large delay spread range in order to design an efficient PRS, because the signal must be received from potentially distant adjacent base stations for position estimation. This is achieved by covering the entire NR bandwidth and transmitting PRS across multiple symbols that can be aggregated to store power.

[0009] The density of subcarriers occupied by a given PRS symbol is called the comb size. Several configurable comb-based PRS patterns exist for comb-2, 4, 6, and 12, suitable for different scenarios serving different use cases. For a comb-N PRS, N symbols can be combined to cover all subcarriers in the frequency domain. Each base station can then transmit with a different set of subcarriers to avoid interference. This solution is also highly latency-efficient, as several base stations can transmit simultaneously without interfering with each other. Furthermore, according to muting patterns, it is possible to mute PRS signals from one or more base stations at a given time, further reducing potential interference. For use cases with higher transmit losses (e.g., in macrocell deployments), the PRS can also be configured to repeat to improve reception.

[0010] In the uplink direction, 3GPP® introduced SRS for positioning in 3GPP Release 16. This new signal solves two aspects specific to positioning. Since positioning involves measurements from multiple receiving base stations, the new signal must have sufficient range to reach not only the serving base station to which the UE is connected, but also neighboring base stations involved in the positioning process. SRS is also designed to cover the entire bandwidth, where resource elements are spread across different symbols to cover all subcarriers. Thus, SRS is also designed using a comb-based pattern similar to PRS. UEs can be multiplexed on the same transmit symbol by assigning different comb patterns. To minimize interference, UEs can be configured with different SRS instances, each having an independent power control loop. This allows SRS directed to neighboring cells to have better reception and keeps interference at the serving cell low.

[0011] Different positioning methods may require different measurements. 3GPP has standardized power, angle, and time measurement support for PRS. Each beam can be regarded as a resource. Measurements are collected over one or more resources and resource sets. Beamforming provides UE location information regarding the angle of departure (AOD) based on the beam ID accessed by the UE, in addition to improving the signal-to-noise ratio (SNR) due to the beamforming gain. On the other hand, multiple antennas in the receiver in the uplink enable fine angle of arrival (AOA) measurements with NR. Many of these measurements are standardized to enable various positioning methods. Since 4G LTE, mobile networks have supported positioning methods based on observed time difference of arrival (OTDOA), uplink time difference of arrival (UL-TDOA), and power measurements. In 5G, the list of supported methods has been extended to include round-trip time (RTT) and angle-based positioning. The inclusion of new positioning methods and the extension of existing positioning methods enable high-precision positioning for some use cases in �G.

[0012] Rel-18 NR extends its reach to adapt to the positioning capabilities of RedCap UEs. These UEs have limited capabilities and complexity and operate with fewer radio frequency (RF) chains and a strictly limited bandwidth (BW) of 20 MHz in frequency range 1 (FR1), i.e., the sub-6 GHz frequency band, and 100 MHz in FR2. To overcome this BW limitation, Rel-18 NR introduces frequency hopping for positioning measurements. This enables RedCap UEs to maintain satisfactory positioning accuracy despite the BW limitation and opens up a wider range of applicability for these devices.

[0013] The accuracy of timing measurements such as reference signal time difference (RSTD) and Rx-Tx time difference is greatly affected by the BW size of the reference signal (RS). In FR1, the BW of normal NR UE downlink (DL) PRS and uplink (UL) SRS is limited to a maximum BW of 100 MHz. To overcome this limitation, Rel-18 NR has introduced BW aggregation for positioning measurements. With this feature, a Tx / Rx architecture with a single RF chain can receive and combine two or three in-band contiguous component carriers (CCs), increasing the effective BW for positioning measurements. Through BW aggregation, the BW of DL PRS and UL SRS is extended beyond the individual CC limits, which can lead to more accurate timing measurements.

[0014] In Rel-18, features introduced in previous releases related to NR positioning are supported for RedCap positioning through frequency hopping such as DL PRS frequency hopping and UL SRS frequency hopping.

[0015] Regarding DL PRS frequency hopping, a RedCap UE can receive a part of a wideband DL PRS, called a frequency hop. By sequentially receiving and combining multiple frequency hops, the RedCap UE can effectively process the wideband DL PRS signal even though the RedCap UE limits the instantaneous maximum BW. However, there are issues such as RF retuning and phase difference. The RedCap UE has to retune the RF receiver at different frequency hops, resulting in a phase difference between frequency hops.

[0016] To accurately reconstruct a wideband DL PRS, these phase differences between frequency hops must be compensated for. One solution is to overlap resource blocks (RBs) across the frequency range between frequency hops. By receiving the DL PRS from overlapping RBs in adjacent frequency hops, the UE can estimate and compensate for the phase difference.

[0017] The UE receives the DL PRS from a frequency hop spanning two symbols and then performs RF retuning on the following two symbols. For gNBs close enough to the UE, two symbols per frequency hop may suffice. However, if the gNB is further away, a longer reception period may be required for each frequency hop to ensure sufficient signal strength, potentially resulting in a longer delay.

[0018] The RedCap UE offers the flexibility to operate with or without frequency hopping. Specifically, the UE can collect positioning measurements from a single frequency hop of the DL PRS, bypassing the complexity of radio frequency (RF) retuning and frequency hopping. Alternatively, the RedCap UE can leverage frequency hopping to construct wider bandwidth DL PRSs, which requires a measurement gap to be configured in the data reception bandwidth for retuning to perform measurements on other frequencies. In the RRC_CONNECTED state, DL PRS frequency hopping occurs within the measurement gap. In the RRC_INACTIVE state, the UE performs frequency hopping during the ON period of selected Discontinuous Reception (DRX).

[0019] The UE may inform the LMF whether the measurement is from a single frequency hop or from multiple frequency hops. This may allow the LMF to prioritize measurements derived from multiple hops for better accuracy.

[0020] Regarding UL SRS frequency hopping, RedCap UEs can use UL SRS frequency hopping to transmit broadband UL SRS signals in segments called frequency hops, such as 20 MHz out of 100 MHz SRS in FR1. SRS frequency hopping requires a separate SRS configuration that includes virtual frequency resource allocation, BW per frequency hop, start PRB, overlap RB, periodicity, offset, and duration for each frequency hop. A base station (such as a gNB) can provide a time window with a length of 1, 2, 4, or 6 slots to prioritize SRS frequency hopping over data communications. This ensures uninterrupted SRS transmission across all frequency hops so that the gNB can accurately reconfigure the broadband SRS. However, if no window is provided, other UL signals will largely take precedence over SRS transmissions, which facilitates stable data communications but may result in delays in obtaining positioning measurements.

[0021] Even if a RedCap UE cannot transmit the entire ZC sequence simultaneously, a single ZC sequence for SRS transmission is generated based on the subcarriers across the entire SRS frequency hop. That is, there are frequency resources that the UE cannot use at a given time, but these frequency resources are virtually allocated for SRS frequency hopping. Adjacent frequency hops intentionally share portions of ZC sequence elements of length L, allowing the gNB to estimate and compensate for phase differences between frequency hops. Similar to DL PRS frequency hopping, to optimize measurement utilization, the gNB explicitly indicates to the LMF whether a measurement was derived from a single frequency hop or from multiple frequency hops.

[0022] LMF can coordinate time and frequency resources for SRS within the effective area to avoid interference. Within the effective area, UE can autonomously adjust timing advance when cell reselection occurs. When UE is configured to measure PRS for positioning or transmit SRS, UE can perform Radio Resource Management (RRM) measurements for positioning within the configured measurement reporting periodicity or SRS transmission periodicity.

[0023] The embodiments generally relate to network communications, cellular networks, data centers, network topologies, edge computing, cloud computing, and communication system implementations, and more particularly to measurement gaps for RedCap user equipment (UE) positioning using receiver (Rx) frequency hopping. The embodiments can enable UEs using RedCap measurements for positioning purposes by adapting radio resource management (RRM) modes for measurement requirements related to frequency hopping of PRS and / or SRS. For example, for at least RAN4, a RedCap UE can at least support measurements on a downlink (DL) PRS using receiver (Rx) frequency hopping using a measurement gap. Support for measurements on a DL PRS using Rx frequency hopping using a measurement gap may include: ●RedCap UE processing capability for DL ​​PRS using Rx frequency hopping and measurement gap (MG), ● Use of a single or multiple instances of MG, and ●This refers to the power per watt (PPW) usage for the Redcap UE.

[0024] PPW measures the amount of power (in watts) consumed by a UE to achieve a specific performance level. A lower PPW indicates better energy efficiency. An efficient UE consumes less power for the same level of service, leading to longer battery life and reduced environmental impact. Lowering PPW may reduce data rates, decrease coverage, and increase latency related to signaling by Redcap UEs. Lowering PPW can also balance energy savings with quality of service (QoS) requirements.

[0025] The RedCap UE can operate in both frequency range 1 (FR1) (410MHz–7125MHz) and frequency range 2 (FR2) (24250MHz–52600MHz–71000MHz). The maximum UE bandwidth can be 20MHz for FR1 and 100MHz for FR2. In some embodiments, the Redcap UE supports one Rx branch, and in some embodiments, the Redcap UE can support multiple-input multiple-output (MIMO).

[0026] MIMO is a general class of techniques that incorporates several transmit and receive techniques using multiple antennas. Spatial multiplexing (SM) involves the transmission of multiple data streams, which are called layers (or frequency layers) in the 3GPP specification. In single-user (SU) MIMO (SU-MIMO), spatial multiplexing involves directing multiple streams to a single user. For multi-user (MU) MIMO (MU-MIMO), layers can be divided among users.

[0027] MIMO can encompass several forms of multi-antenna techniques in transmit mode. MIMO formats include single-antenna, transmit diversity, open-loop SU-MIMO, closed-loop SU-MIMO, closed-loop rank-1 precoding (beamforming), and MU-MIMO. The introduction of larger antenna arrays has enabled multi-layer beamforming (BF), which differs from earlier SM by using multiple antennas for each layer.

[0028] Precoding refers to the multiplexing of data streams onto an antenna port. An antenna port can often represent a non-unique subset of antenna elements controlled by radio frequency (RF) circuitry, often called an RF chain. Each transmit may utilize a set of RF chains within the RF circuitry to transmit data (also called tones) over multiple subcarriers of the transmit bandwidth relative to the carrier frequency.

[0029] In some embodiments, the Radio Resource Management (RRM) may optionally support extended discontinuous reception (eDRX) so that the Redcap UE can favorably reduce power consumption during periods involving relaxed DL latency and relaxed neighbor cell measurements to conserve power.

[0030] Embodiments herein may favorably define gap-based measurements using frequency hopping for RedCap UEs. For gap-based reference signal time difference (RSTD), positioning reference signal-received reference signal power (PRS-RSRP), UE Rx-Tx time difference, and positioning reference signal-received reference signal path power (PRS-RSRPP) measurements, the requirements in sections 9.9A.2, 9.9A.3, 9.9A.4, and 9.9A.5 of the RRM specification 3GPP Technical Specification (TS) 38.133 (e.g., 3GPP TS 38.133 V18.4.0 (2023-12) and later) may apply. The following assumptions are made: -RedCap UE consists of measurement gaps, or pre-configured or concurrent measurement gaps. - All positioning frequency layers are measured, or associated with only one measurement gap per UE. - independentGapConfigPRS-r17 For RedCap UEs that support this feature, all positioning frequency layers within the same FR are measured, or they are associated with only one of the measurement gaps per FR within the corresponding FR. -If a measurement gap is pre-configured, the measurement gap must be activated throughout the entire measurement period. -When simultaneous measurement gaps are configured, one of the combinations of measurement gaps specified in Section 9.1.8.2 of TS 38.133 is configured (see Table 600 in Figure 6). -RedCap UE independentGapConfigPRS-r17 If not supported, the configured or pre-configured gap used to perform PRS measurements must be of a per-UE type. - Active BWP switching does not occur during the measurement gap for PRS measurement.

[0031] All measurement requirements specified in sections 9.9A.2, 9.9A.3, 9.9A.4, and 9.9A.5 of TS 38.133 may be applied without DRX and with any DRX configuration specified in the RRC protocol specification TS 38.331 (e.g., 3GPP TS 38.331 V18.0.0(2023-12)).

[0032] In some embodiments, the RedCap UE is required only to measure PRS resources that completely or partially overlap the measurement gap, and the requirements in sections 9.9A.2, 9.9A.3, 9.9A.4, and 9.9A.5 of TS 38.133 are applicable to PRS resources that completely or partially overlap the measurement gap.

[0033] A PRS resource is considered to fully (or partially) overlap with a measurement gap if all (or some) of its instances overlap with the measurement gap opportunity. nr-DLPRS-ExpectedRSTD-Uncertainty and nr-DL-PRS-ExpectedRSTD A PRS resource instance is considered to overlap with the measurement gap opportunity if the minimum number of unmuted iterations of an instance taking this into account is fully covered by the measurement gap length (MGL), excluding the RF switching time (time for RF retuning for each frequency hop). Here, - The minimum number is given for the accuracy requirement using frequency hop (FH) for two receivers (2 Rx) RedCap UE (as specified in TS 38.133). - The minimum number is given for one receiver (1 Rx) RedCap UE in the accuracy requirement using FH (as specified in TS 38.133).

[0034] When a RedCap UE is configured with measurements for two or more positioning requests, the measurement period for each request may be longer than the measurement period when a RedCap UE is configured with measurements for a single positioning request.

[0035] Positioning measurement gap PosGapConfi When configured via g and activated by a medium access control-control element (MAC CE), no other measurement gap (MG) is configured, and PosGapConfig Assuming that only one measurement gap configured via is activated, the measurement requirements in sections 9.9A.2, 9.9A.3, 9.9A.4, and 9.9A.5 may apply. This requirement may ensure that the MG configuration does not exceed the UE's ability to support multiple MGs simultaneously.

[0036] The MG can be a static configuration having periodicity, duration, time, and location. Once configured, the UE can follow the configuration.

[0037] Furthermore, if the allowable total activated measurement gap is less than [2 per UE, or 3 per FR], the measurement gap for each Rx hop can be the same. This can sometimes be retuned for different RX hops. In other words, for each measurement gap per UE, if the allowable total activated measurement gap is 1, then the measurement gap for all Rx hops is an iteration of the same measurement gap. This can sometimes be retuned for different RX hops by the UE. -If the baseline capability of the UE is per UE, then the UE may have one measurement gap configuration per UE. -If the UE supports the FR measurement gap for each measurement, the UE may have up to two MGs for each FR.

[0038] In further embodiments, if more activated measurement gaps are permitted [e.g., >3 per UE, or >4 per FR], the measurement gap for each Rx hop may be for a different measurement gap. In this way, the UE can support measurements within a simultaneous measurement gap. In such embodiments, the simultaneous measurement gap may be activated together for a specific duration that is greater than the duration of one or both of the individual measurement gaps.

[0039] RSTD measurement for RedCap (RSTD Princesses for RedCap) Regarding RSTD measurements for RedCap, RedCap UE requires the Location Management Function (LMF) to measure and report DL RSTD measurements as defined in TS 38.215 (e.g., 3GPP TS 38.215 V17.4.0 (2023-12)) via the LTE Positioning Protocol (LPP). NR-DL-TDOA-RequestLocationInformationAssuming the message has been received, the requirements in Section 9.9A.2 may apply. The requirements in Section 9.9A.2.5 may apply assuming that the RedCap UE does not support, or supports but is not configured to, measure PRS resources using frequency hopping (FH) in accordance with the indicated UE capabilities. Assuming that the RedCap UE supports and is configured to measure PRS resources using frequency hopping (FH) in accordance with the indicated UE capabilities, the requirements in Section 9A.2.6 may apply.

[0040] The requirements of Section 9.9A.2.6 may apply to periodic and triggered RSTD measurements using FH, provided the following assumptions are made: -For FR1 and FR2, the PRS-RSTD related side conditions for two given Rx RedCap UEs are satisfied for the corresponding bandwidth. -For FR1, the PRS-RSTD related side condition for a given Rx RedCap UE is satisfied for the corresponding bandwidth.

[0041] The RedCap UE PRS RSTD measurement capability conforms to TS 37.355 (e.g., 3GPP TS 37.355 V18.0.0(2023-12)), NR-DL-TDOA-ProvideCapabilities This is as shown by RedCap UE.

[0042] Except for RSTD measurement accuracy, the requirements of Section 9.9.2.4 of TS 38.133 may apply. RSTD measurements performed and reported in accordance with this section may satisfy the RSTD measurement accuracy requirements for each measured DL PRS resource.

[0043] The physical layer is requesting RedCap UE to measure DL RSTD measurements using FH, via LPP, from LMF. NR-TDOA-ProvideAssistanceData Message, and, NR-TDOA-RequestLocationInformation When the RedCap UE receives the last of the messages, N sampleMeasurement period T as defined in section 9.9A.2.5.1 of TS 38.133, using the following definition for PSTD,Toal During this process, multiple DL RSTD measurements can be taken, as defined in TS 38.215 (up to the RedCap UE capability specified in section 9.9A.2.3 of TS 38.133). That is, N sample This is the number of PRS RSTD measurement samples. -RedCap UE supportedDL-PRS-ProcessingSamples-RRC-CONNECTED It supports and when the LMF requests the UE to perform positioning measurements using a reduced number of samples, N sample = 2 -Otherwise, N sample = 4

[0044] Measurement samples under FH are defined as PRS measurements across multiple hops within a single measurement gap opportunity.

[0045] The number of hops in a single MG opportunity may be specified in TS 38.133 or other technical specifications.

[0046] PRS-RSRP measurements for RedCap With respect to PRS-RSRP measurements for RedCap, the requirements in Section 9.9A.3 of TS 38.215 may apply, assuming that the RedCap UE receives a message from the LMF via LPP requesting the RedCap UE to measure and report PRS-RSRP measurements as defined in TS 38.133.

[0047] Measurement samples under FH are defined as PRS measurements across multiple hops within a single measurement gap opportunity.

[0048] The number of hops in a single MG opportunity may be specified in TS 38.133 or other technical specifications.

[0049] UE Rx-Tx time difference measurements for RedCap Regarding UE Rx-Tx time difference measurements for RedCap, the UE requires LMF to measure and report one or more UE Rx-Tx time difference measurements as defined in TS 38.215 (e.g., 3GPP TS 38.215 V17.4.0 (2023-12)) via LPP. nr-Multi-RTT-RequestLocationInformation When receiving a message, the requirements in this section may apply to the RedCap UE.

[0050] If the UE does not support RX frequency hopping (FH) for PRS measurements as indicated by its capabilities, or if the LMF does not require the UE to use RX FH for PRS measurements as indicated in the measurement request, then the requirements in sections 9.9A.4.5, 9.9A.4.6, and 9.9A.4.7 of TS 38.133 may apply to applicable configurations.

[0051] If the UE supports RX frequency hopping (FH) for PRS measurements as indicated by the UE capability, and LMF requires the UE to use RX FH for PRS measurements as indicated in the measurement request, then the requirements in Section 9.9A.4.8 of TS 38.133 may apply.

[0052] The requirements in section 9.9A.4 of TS 38.133 may apply to periodic and triggered UE Rx-Tx time difference measurements, assuming the following: - The side conditions related to UE Rx-Tx time difference measurements given in TS 38.133 or other technical specifications shall be satisfied for the corresponding bandwidth. -SRS is composed of at least one of PCell, PSCell, and SCell. -UE transmits SRS within [-160, 160] msec of DL PRS resources related to at least one TRP in the support data.

[0053] The requirements in this section may apply when the LMF requests that the RedCap UE perform measurements using FH, and when the UE reports measurements based on multiple hops.

[0054] The requirements in Section 9.9A.4.5 may be applied with the following modifications: -N_sample=2 if the UE supports the ability to perform positioning measurements using a reduced number of samples, as specified in TS 37.355, and the LMF requests the UE to perform positioning measurements using a reduced number of samples. - The number of hops in a single MG opportunity is defined in TS 38.133 or other technical specifications. -Measurement samples under FH are defined as PRS measurements spanning multiple hops within a single measurement gap.

[0055] PRS-RSRPP measurements for RedCap Regarding PRS-RSRPP measurements for RedCap, UE requires that UE measure and report one or more PRS-RSRPP measurements as defined in TS 38.215. NR-DL-AoD-RequestLocationInformation When a message is received from the LMF via LPP, the requirements in this section may apply to the RedCap UE.

[0056] If the UE does not support frequency hopping (FH) for PRS measurements as indicated by its capabilities, or if the LMF does not require the UE to use FH for PRS measurements as indicated in the measurement requirements, then the requirements in sections 9.9A.5.5, 9.9A.5.6, and 9.9A.5.7 of TS 38.133 may apply to applicable configurations.

[0057] If the UE supports frequency hopping (FH) for PRS measurements as indicated by the UE capability, and LMF requires the UE to use FH for PRS measurements as indicated in the measurement request, then the requirements in Section 9.9A.5.8 of TS 38.133 may apply.

[0058] The requirements in Section 9.9A.5 of TS 38.133 may apply to periodic and triggered PRS-RSRPP measurements, assuming the following: - The PRS-RSRPP-related side conditions given in TS 38.133 are satisfied for the corresponding bandwidth.

[0059] The UE PRS-RSRPP measurement capability is as follows, according to TS 37.355. NR-DL-AoD-ProvideCapabilities As shown by UE.

[0060] This requirement assumes that measurement reports are not delayed by other LPP signaling on the dedicated control channel (DCCH). This measurement report delay excludes delay uncertainty caused by inserting measurement reports into the transmission time interval (TTI) of the uplink DCCH. The delay uncertainty is 2 × TTIDCCH, where TTIDCCH is the duration of a subframe, slot, or subslot when the measurement report is transmitted on the physical uplink control channel (PUSCH), using subframe, slot, or subslot durations. This measurement report delay excludes any delay caused by the UE lacking UL resources to send the measurement report.

[0061] The reported PRS-RSRPP measurements included in the measurement report can be obtained based on the measurement report mapping requirements specified in Section 10.1.38.3 of TS 38.133.

[0062] The PRS-RSRPP measurement accuracy for all measured PRS resources may be met in accordance with the accuracy requirements specified in TS 38.133 or other technical specifications.

[0063] The measurement period requirements for PRS-RSRP as defined in Section 9.9A.3.5 of TS 38.133 may be reused for PRS-RSRPP.

[0064] Various embodiments may be designed to address different technical issues related to performing positioning measurements via a RedCap UE, defining measurement gaps for a RedCap UE, performing frequency hops by the UE to perform positioning measurements, configuring the UE for measurement gaps, limiting the number of simultaneous measurement gaps for the UE, and so on.

[0065] The different technical problems described above can be addressed by one or more different embodiments. Embodiments can address one or more of these problems related to performing positioning measurements via RedCap UE. For example, some embodiments that address problems related to performing positioning measurements via RedCap UE can do so by one or more different technical means, such as: determining the frequency range of the PRS based on the PRS configuration, where the PRS configuration defines resource blocks of the PRS positioning frequency layer; determining the number of frequency hops between positioning frequency layers associated with the PRS frequency range during iterations involving one measurement gap based on a per-UE measurement gap configuration or up to two measurement gaps based on a per-frequency range (FR) measurement gap configuration to perform PRS measurements within at least one measurement delay; performing the number of frequency hops and measurements related to the PRS during each iteration of one or up to two measurement gaps; causing the transmission of at least one positioning measurement report via an interface, etc.

[0066] Some embodiments include systems with multiple processor cores, such as central servers and access points, and / or stations (STAs) such as modems, routers, switches, servers, workstations, netbooks, mobile devices (laptops, smartphones, tablets, etc.), sensors, meters, controls, instruments, monitors, home or office equipment, and Internet of Things (IoT) gear (watches, glasses, headphones, cameras, etc.). Some embodiments may, for example, provide indoor and / or outdoor “smart” grids and sensor services. In various embodiments, these devices relate to specific applications such as healthcare, home, commercial office and retail, security, and industrial automation and monitoring applications, as well as vehicle applications (automobiles, autonomous vehicles, airplanes, drones, etc.).

[0067] The techniques disclosed herein may involve the transmission of data over one or more radio connections using one or more wireless mobile broadband technologies. For example, various embodiments may involve transmission over one or more radio connections in accordance with one or more technologies and / or standards, including one or more Third Generation Partnership Projects (3GPP), 3GPP Long-Term Evolution (LTE), 3GPP LTE-Advanced (LTE-A), 4G LTE, 5G New Radio (NR), and / or 6G, revisions, successors, and variations thereof. Various embodiments may additionally or alternatively involve transmission in accordance with standards (including revisions, successors, and variations thereof), including one or more GSM (GSM / GPRS) technologies having a Global System for Mobile Communications (GSM) / Enhanced Data Rate for GSM Evolution (EDGE), Universal Mobile Telecommunications System (UMTS) / High-Speed ​​Packet Access (HSPA), and / or General-Purpose Packet Radio Services (GPRS) system, and / or revisions, successors, and variations thereof.

[0068] Examples of wireless mobile broadband technologies and / or standards may also include, but are not limited to, any of the following: the Institute of Electrical and Electronics Engineers (IEEE) 802.16 wireless broadband standards such as IEEE 802.16m and / or 802.16p; International Mobile Communications Advanced (IMT-ADV); Worldwide Interoperability for Microwave Access (WiMAX) and / or WiMAX II; Code Division Multiple Access (CDMA) 2000 (e.g., CDMA2000 1xRTT, CDMA2000 EV-DO, CDMA EV-DV, etc.); High Performance Wireless Metropolitan Area Network (HIPERFMAN); Wireless Broadband (WiBro); High-Speed ​​Downlink Packet Access (HSDPA); High-Speed ​​Orthogonal Frequency Division Multiplexing (OFDM) Packet Access (HSOPA); and High-Speed ​​Uplink Packet Access (HSUPA) technologies and / or standards, including their revisions, successors, and variations.

[0069] Some embodiments may additionally perform wireless communication in accordance with other wireless communication technologies and / or standards. Examples of other wireless communication technologies and / or standards that may be used in various embodiments include, but are not limited to, other IEEE wireless communication standards such as IEEE 802.11-5220, IEEE 802.11ax-5221, IEEE 802.11ay-5221, IEEE 802.11ba-5221, and / or other specifications and standards such as specifications developed by the Wi-Fi Alliance (WFA) Neighbor Awareness Networking (NAN) Task Group, 3GPP Technical Report (TR) 23.887, 3GPP Technical Specifications (TS) 22.368, 3GPP TS 23.682, 3GPP TS 36.133, 3GPP TS 36.306, 3GPP TS 36.321, 3GPP TS.331, 3GPP TS 38.133, 3GPP TS 38.306, and 3GPP TS This may include machine-type communication (MTC) standards, such as those embodied in 38.321, 38.214, and / or 3GPP TS 38.331, and / or near-field communication (NFC) standards, such as standards developed by the NFC Forum, including any revisions, descendants, and / or variations of any of the above. Embodiments are not limited to these examples.

[0070] Figure 1 shows a communication network 100 having user equipment (UEs) such as UE-1, UE-2, and UE-3, as well as base stations such as base stations 101 and 102. The communication network 100 is an orthogonal frequency division multiplexing (OFDM) network comprising a primary base station 101, a secondary base station 102, a cloud-based service 103, a first user equipment UE-1, a second user equipment UE-2, and a third user equipment UE-3. In a 3GPP system based on orthogonal frequency division multiple access (OFDMA) downlink, radio resources are divided into subframes in the time domain, and each subframe consists of two slots. Each OFDMA symbol further consists of a count of OFDMA subcarriers in the frequency domain, depending on the system (or carrier) bandwidth. The basic unit of the resource grid is called a resource element (RE), which spans OFDMA subcarriers across one OFDMA symbol. A resource block (RB) comprises a group of REs, where each RB may have, for example, 12 consecutive subcarriers in one slot.

[0071] Several physical downlink channels and reference signals use a set of resource elements that carry information originating from higher layers of the code. Regarding downlink channels, the physical downlink shared channel (PDSCH) is the data-bearing downlink channel, while the physical downlink control channel (PDCCH) may carry downlink control information (DCI). Control information may include scheduling decisions, information related to reference signal information, rules forming the corresponding transport blocks (TBs) to be carried by the PDSCH, and power control commands. The UE may use cell-specific reference signals (CRS) for demodulation of control / data channels in unprecoded or codebook-based precoded transmit modes, radio link monitoring, and measurement of channel status information (CSI) feedback. The UE may use UE-specific reference signals (DM-RS) for demodulation of control / data channels in non-codebook-based precoded transmit modes.

[0072] The communication network 100 comprises cells such as microcells or macrocells, and base station 101 may provide wireless services to UEs within a cell. Base station 102 may provide wireless services to UEs in another cell located adjacent to or overlapping with a cell. In other embodiments, the communication network 100 comprises macrocells, and base station 102 may operate smaller cells within the macrocell, such as microcells or picocells. Other examples of small cells may include, but are not limited to, microcells, femtocells, or other types of smaller sized cells.

[0073] In various embodiments, base stations 101 and 102 may communicate via backhaul. In some embodiments, the backhaul may be a wired backhaul. In various other embodiments, the backhaul may be a wireless backhaul. In some embodiments, the backhaul may be an Xn interface or an F1 interface, which is an interface defined between two RAN nodes or base stations, such as a backhaul between base station 101 and base station 102. When the architecture of the communication network 100 is a central unit / distributed unit (CU / DU) architecture, the Xn interface is an interface for gNBs, and the F1 interface is an interface for gNBs-distributed units (DUs). For example, in some embodiments, base station 101 may have a CU, and base station 102 may have a DU. In other embodiments, both base stations 101 and 102 may have an eNB or a gNB.

[0074] Base stations 101 and 102 may communicate with protocol data units (PDUs) via backhaul. For example, in the case of the Xn interface, base station 101 may transmit or share control plane PDUs via the Xn-C interface and data PDUs via the Xn-U interface. In the case of the F1 interface, base station 101 may transmit or share control plane PDUs via the F1-C interface and data PDUs via the F1-U interface. Note that the descriptions herein of signaling, sharing, receiving, or transmitting via the Xn interface may refer to signaling, sharing, receiving, or transmitting via the Xn-C interface, the Xn-U interface, or a combination thereof. Similarly, the descriptions herein of signaling, sharing, receiving, or transmitting via the F1 interface may refer to signaling, sharing, receiving, or transmitting via the F1-C interface, the F1-U interface, or a combination thereof.

[0075] In some embodiments, a UE such as UE-1 may include frequency hop logic circuits for determining a series of one or more frequency hops between the positioning frequency layers of the PRS in order to perform positioning measurements such as reference signal time difference (RSTD) measurement, positioning reference signal-received reference signal power (PRS-RSRP) measurement, UE Rx-TX time difference measurement, and positioning reference signal-received signal power (PRS-RSRPP) measurement. The frequency hops may, advantageously, allow the UE to measure PRS with a bandwidth greater than the UE's capability, for example, if the UE is a RedCap UE.

[0076] In many embodiments, the UE is configured or pre-configured with one or two measurement gaps for positioning measurements, such as one per UE measurement gap, or up to two FR measurement gaps for FR1 and / or FR2. Based on the accuracy requirements for the positioning measurements, the measurement delay associated with each positioning measurement, and the delay for retuning the receiver for each frequency layer, the frequency hop logic circuit may determine the number of frequency hops across the periodic measurement gaps required to satisfy the accuracy requirements for all positioning measurements. In some embodiments, the number of frequency hops may differ between iterations of measurement gaps for performing positioning measurements. In other embodiments, the number of frequency hops may be the same between iterations of measurement gaps for performing positioning measurements.

[0077] In some embodiments, base stations such as base stations 101 and 102 may include frequency hop logic circuits for configuring a PRS to signal using the measurement gap configured for the UE. In many embodiments, the base station transmits the measurement gap configuration to the UE and may configure the UE for one measurement gap per UE, or up to two measurement gaps per FR measurement gap. In some embodiments, a location management function (LMF) may provide the measurement gap configuration to the UE via the base station over the LTE positioning protocol (LPP). In further embodiments, different cellular network management functions and / or protocols may provide the measurement gap configuration to the UE via the base station.

[0078] Figure 2 shows embodiments of network 100B, following various embodiments such as network 100 in Figure 1. Network 100B may operate in a manner consistent with 3GPP technical specifications for LTE or 5G / NR systems, as well as O-RAN specifications such as "Near-Real-time RAN Intelligent Controller, E2 Service Model (E2SM), RAN Control". However, the exemplary embodiments are not limited in this respect, and the embodiments described may be applied to other networks that benefit from the principles described herein, such as future 3GPP systems.

[0079] Network 100B includes UE 102B, such as the UE shown in Figure 1, which may include any mobile or non-mobile computing device designed to communicate with RAN 104 via a wireless connection. UE 102B may be coupled to RAN 104 for communication via a Uu interface. UE 102B may, but is not limited to, smartphones, tablet computers, wearable computing devices, desktop computers, laptop computers, automotive infotainment, automotive entertainment devices, instrument clusters, head-up display devices, automotive diagnostic devices, dashboard mobile devices, mobile data terminals, electronic engine management systems, electronic / engine control units, electronic / engine control modules, embedded systems, sensors, microcontrollers, control modules, engine management systems, networked appliances, machine-type communication devices, M2M or D2D devices, IoT devices, etc.

[0080] In some embodiments, network 100B may include multiple UEs directly coupled to each other via sidelink interfaces. The UEs may be M2M / D2D devices that communicate using physical sidelink channels such as PSBCH, PSDCH, PSSCH, PSCCH, and PSFCH.

[0081] In some embodiments, UE 102B may further communicate with AP 106 via a wireless connection. AP 106 may manage a WLAN connection that can function to offload some / all network traffic from RAN 104. The connection between UE 102B and AP 106 may comply with any IEEE 802.11 protocol, where AP 106 may be a Wireless Fidelity (Wi-Fi®) router. In some embodiments, UE 102B, RAN 104, and AP 106 may utilize cellular WLAN aggregation (e.g., LWA / LWIP). Cellular-WLAN aggregation may involve UE 102B configured by RAN 104 to utilize both cellular wireless resources and WLAN resources.

[0082] RAN 104 may include one or more access nodes, for example, AN 108. AN 108 may terminate the air-interface protocol for UE 102B by providing access layer protocols including RRC, PDCP, RLC, MAC, and L1 protocols. In this way, AN 108 may enable data / voice connectivity between CN 120 and UE 102B. In some embodiments, AN 108 may be implemented as one or more software entities running on a server computer, either in a separate device or as part of a virtual network which may be referred to as CRAN or a virtual baseband unit pool, for example. AN 108 is referred to as BS, gNB, RAN node, eNB, ng-eNB, NodeB, RSU, TRxP, TRP, etc. AN 108 may be a macrocell base station, or a low-power base station for providing a femtocell, picocell, or other similar cell with a smaller coverage area, smaller user capacity, or higher bandwidth compared to a macrocell.

[0083] In embodiments where RAN 104 includes multiple ANs, they may be coupled to each other via an X2 interface (if RAN 104 is an LTE RAN) or an Xn interface (if RAN 104 is a 5G RAN). The X2 / Xn interface, which may be separated into a control / user plane interface in some embodiments, may allow ANs to communicate information related to handover, data / context transfer, mobility, load management, interference coordination, etc.

[0084] Each AN of RAN 104 may manage one or more cells, cell groups, component carriers, etc., to provide an air interface for network access to UE 102B. UE 102B may be simultaneously connected to multiple cells provided by the same or different ANs of RAN 104. For example, UE 102B and RAN 104 may use carrier aggregation to enable UE 102B to connect to multiple component carriers, each corresponding to a Pcell or Scell. In a dual connectivity scenario, the first AN may be a master node providing an MCG, and the second AN may be a secondary node providing an SCG. The first / second ANs may be any combination of eNBs, gNBs, ng-eNBs, etc.

[0085] RAN 104 can provide an air interface across authorized or unauthorized spectra. To operate in unauthorized spectra, the node may use LAA, eLAA, and / or feLAA mechanisms based on CA technology with Pcell / Scell. Prior to accessing unauthorized spectra, the node may perform medium / carrier detection operations, for example, based on a Listen Before Talk (LBT) protocol.

[0086] In a V2X scenario, UE 102B or AN 108 may refer to any transport infrastructure entity used for V2X communication, and may be or may act as an RSU. An RSU may be implemented in or by an appropriate AN or fixed (or relatively fixed) UE. In or by an RSU implemented by a UE, the UE may be called a “UE-type RSU,” an eNB a “eNB-type RSU,” a gNB a “gNB-type RSU,” etc. In one example, an RSU is a computing device coupled to a roadside radio frequency circuit that provides connectivity support to a passing vehicle UE. An RSU may also include internal data storage circuitry for storing intersection map geometry, traffic statistics, media, and applications / software for sensing and controlling oncoming vehicle and pedestrian traffic. An RSU may provide very low latency communication required for high-speed events such as collision avoidance, traffic warnings, etc. Additionally or alternatively, an RSU may provide other cellular / WLAN communication services. The RSU components may be packaged in a weather-resistant enclosure suitable for outdoor installation and may include a network interface controller for providing wired connectivity (e.g., Ethernet®) to a traffic signal controller or backhaul network.

[0087] In some embodiments, RAN 104 may be an LTE RAN 110 having an eNB, eNB 112, for example. The LTE RAN 110 may provide an LTE air interface having the following characteristics: a 15 kHz SCS, CP-OFDM waveforms for DL ​​and SC-FDMA waveforms for UL, turbo code for data and TBCC for control, etc. The LTE air interface may rely on CSI-RS for CSI acquisition and beam management, PDSCH / PDCCH DMRS for PDSCH / PDCCH demodulation, and CRS for cell discovery and initial acquisition, channel quality measurement, and channel estimation for coherent demodulation / detection in the UE. The LTE air interface may operate in the sub-6 GHz band.

[0088] In some embodiments, the RAN 104 may be an NG-RAN 114 having a gNB, e.g., gNB 116, or an ng-eNB, e.g., ng-eNB 118. The gNB 116 may connect to a 5G-enabled UE using a 5G NR interface. The gNB 116 may connect to the 5G core via an NG interface, which may include an N2 interface or an N3 interface. The ng-eNB 118 may also connect to the 5G core via an NG interface, but may connect to the UE via an LTE air interface. The gNB 116 and ng-eNB 118 may be interconnected via an Xn interface.

[0089] In some embodiments, the NG interface may be divided into two parts: an NG user plane (NG-U) interface (e.g., N3 interface) that carries traffic data between the NG-RAN114 nodes and the UPF 148, and an NG control plane (NG-C) interface (e.g., N2 interface) that is a signaling interface between the NG-RAN114 nodes and the AMF 144.

[0090] NG-RAN 114 can provide a 5G-NR air interface with the following characteristics: variable SCS, CP-OFDM for DL, CP-OFDM and DFT-s-OFDM for UL, polar, repetitive, 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 does not require CRS, but may use PBCH DMRS for PBCH demodulation, PTRS for phase tracking for PDSCH, and a tracking reference signal for time tracking. The 5G-NR air interface can operate in the FR1 band, including the sub-6GHz band, or in the FR2 band, including the 24.25GHz to 52.6GHz band. The 5G-NR air interface may include SSB, which is an area of ​​the downlink resource grid including PSS / SSS / PBCH.

[0091] In some embodiments, a 5G-NR air interface can utilize BWPs for various purposes. For example, BWPs can be used for dynamic adaptation of SCSs. For instance, UE 102B may be configured with multiple BWPs, each BWP configuration having a different SCS. When a BWP change is indicated to UE 102B, the transmit SCS is also changed accordingly. Another example of a use case for BWPs relates to power saving. In particular, multiple BWPs can be configured for UE 102B with different amounts of frequency resources (e.g., PRBs) to support data transmission under different traffic load (loading) scenarios. BWPs containing fewer PRBs can be used for data transmission with low traffic loads in UE 102B and, in some cases, in gNB 116, while enabling power savings. BWPs containing more PRBs can be used for scenarios with higher traffic loads.

[0092] RAN 104 is communicatively coupled to CN 120, which includes network elements to provide various functionalities to support data and telecommunications services to customers / subscribers (e.g., users of UE 102B). The components of CN 120 may be implemented on one physical node or separate physical nodes. In some embodiments, NFV may be used to virtualize some or all of the functionalities provided by the network elements of CN 120 onto physical computing / storage resources in servers, switches, etc. Logical instantiations of CN 120 are referred to as network slices, and some logical instantiations of CN 120 may be referred to as network subslices.

[0093] In some embodiments, CN 120 may be LTE CN 122, which may also be called EPC. LTE CN 122 may include MME 124, SGW 126, SGSN 128, HSS 130, PGW 132, and PCRF 134, coupled to each other via interfaces (or “reference points”), as shown. The functions of the elements of LTE CN 122 can be briefly described below.

[0094] The MME 124 may implement mobility management capabilities to track the current location of the UE 102B in order to facilitate paging, bearer activation / deactivation, handover, gateway selection, authentication, etc.

[0095] SGW 126 terminates the S1 interface toward the RAN and can route data packets between the RAN and LTE CN 122. SGW 126 is a local mobility anchor point for handovers between RAN nodes and can also provide an anchor for 3GPP-to-3GPP mobility. Other responsibilities may include lawful intercept, billing, and any policy enforcement.

[0096] SGSN 128 can track the location of UE 102B and perform security functions and access control. In addition, SGSN 128 can perform EPC node signaling for mobility between different RAT networks, PDN and S-GW selection as specified by MME 124, MME selection for handover, etc. An S3 reference point between MME 124 and SGSN 128 can enable user and bearer information exchange for mobility between 3GPP access networks in idle / active states.

[0097] HSS 130 may include a database of network users containing subscription-related information to support the processing of communication sessions for network entities. HSS 130 can provide support for routing / roaming, authentication, authorization, naming / addressing resolution, location dependency, etc. An S6a reference point between HSS 130 and MME 124 may enable the transfer of subscription and authentication data for authenticating / authorizing user access to LTE CN 120.

[0098] PGW 132 may terminate an Sgi interface toward a data network (DN) 136, which may include an application / content server 138. PGW 132 may route data packets between the LTE CN 122 and the data network 136. PGW 132 may be coupled to SGW 126 by an S5 reference point to facilitate user plane tunneling and tunnel management. PGW 132 may further include nodes (e.g., PCEF) for policy enforcement and billing data collection. Additionally, the Sgi reference point between PGW 132 and the data network 136 may be an operator-external public, private PDN, or intra-operator packet data network for providing IMS services. PGW 132 may be coupled to PCRF 134 via a Gx reference point.

[0099] PCRF 134 is the policy and billing control element of LTE CN 122. PCRF 134 can be communicatively coupled to application / content (app / content) server 138 to determine appropriate QoS and billing parameters for the service flow. PCRF 132 can provide associated rules to the PCEF (via Gx reference points) using appropriate TFT and QCI.

[0100] In some embodiments, CN 120 may be 5GC 140. 5GC 140 may include AUSF 142, AMF 144, SMF 146, UPF 148, NSSF 150, NEF 152, NRF 154, PCF 156, UDM 158, AF 160, and Location Management Function (LMF) 162, all interconnected via an interface (or "reference point"), as shown in the illustration. The functions of the elements of 5GC 140 can be briefly described below.

[0101] AUSF 142 can store data for authentication of UE 102B and handle authentication-related functionality. AUSF 142 can facilitate a common authentication framework for various access types. In addition to communicating with other elements of 5GC 140 over the reference point, as shown, AUSF 142 can provide a Nausf service-based interface.

[0102] The AMF 144 may enable other functions of the 5GC 140 to communicate with the UE 102B and RAN 104 and to subscribe to notifications about mobility events concerning the UE 102B. The AMF 144 may be responsible for registration management (e.g., to register the UE 102B), connectivity management, reachability management, mobility management, lawful interception of AMF-related events, and access authentication and authorization. The AMF 144 may provide transport for SM messages between the UE 102B and SMF 146 and may act as a transparent proxy for routing SM messages. The AMF 144 may also provide transport for SMS messages between the UE 102B and SMSF. The AMF 144 may interact with the AUSF 142 and UE 102B to perform various security anchor and context management functions. Furthermore, AMF 144 is the endpoint of the RAN CP interface, including, or possibly including, an N2 reference point between RAN 104 and AMF 144, and AMF 144 is the endpoint of NAS(N1) signaling and can perform NAS encryption and integrity protection. AMF 144 may also support NAS signaling with UE 102B via the N3 IWF interface.

[0103] SMF 146 may be responsible for SM (e.g., session establishment, tunnel management between UPF 148 and AN 108), UE IP address allocation and management (including optional authorization), selection and control of UP functions, configuration of traffic steering in UPF 148 for routing traffic to appropriate destinations, termination of interfaces toward policy control functions, policy enforcement, billing, and some control of QoS, lawful interception (of SM events and interfaces toward LI systems), termination of the SM portion of NAS messages, downlink data notification, initiation of AN-specific SM information transmitted across N2 to AN 108 via AMF 144, and determination of the session's SSC mode. SM refers to the management of PDU sessions, and PDU sessions or “session” may refer to PDU connectivity services that provide or enable the exchange of PDUs between UE 102B and data network 136.

[0104] UPF 148 can function as an anchor point for intra-RAT and inter-RAT mobility, an external PDU session point for interconnection to data network 136, and a branching point to support multi-homed PDU sessions. UPF 148 can also perform packet routing and forwarding, perform packet inspection, enforce the user plane portion of policy rules, lawfully intercept packets (UP collection), perform traffic usage reporting, perform QoS processing on the user plane (e.g., packet filtering, gating, UL / DL rate enforcement), perform uplink traffic verification (e.g., SDF-to-QoS flow mapping), perform transport-level packet marking on uplinks and downlinks, and perform downlink packet buffering and downlink data notification triggering. UPF 148 may include an uplink classifier to support routing of traffic flows to the data network.

[0105] NSSF 150 may select a set of network slice instances to service UE 102B. NSSF 150 may also determine, if necessary, mappings to authorized NSSAIs and subscribed S-NSSAIs. NSSF 150 may also determine, based on appropriate configuration and possibly by querying NRF 154, a set of AMFs, or a list of candidate AMFs, to be used to service UE 102B. The selection of a set of network slice instances for UE 102B is triggered by AMF 144, which UE 102B registers with by interacting with NSSF 150, and this may lead to changes in the AMF. NSSF 150 may interact with AMF 144 via the N22 reference point and communicate with other NSSFs in the visited network via the N31 reference point (not shown). Additionally, NSSF 150 may represent an Nnssf service-based interface.

[0106] NEF 152 can securely expose services and capabilities provided by 3GPP network functions to third parties, internal exposure / re-exposure, AFs (e.g., AF 160), edge computing systems, or fog computing systems, etc. In such embodiments, NEF 152 can authenticate, authorize, or throttle AFs. NEF 152 can also convert information exchanged with AF 160 and information exchanged with internal network functions. For example, NEF 152 can convert between AF service identifiers and internal 5GC information. NEF 152 can also receive information from other NFs based on the exposed capabilities of those NFs. This information can be stored in NEF 152 as structured data or in a data storage NF using a standardized interface. The stored information can then be re-exposed by NEF 152 to other NFs and AFs, or used for other purposes such as analysis. Additionally, NEF 152 may represent an Nnef service-based interface.

[0107] NRF 154 supports service discovery functionality, can receive NF discovery requests from NF instances, and can provide NF instances with information about discovered NF instances. NRF 154 also maintains information about available NF instances and the services they support. As used herein, terms such as “instantiate” and “instantiation” may refer to the creation of an instance, and “instance” may refer to the specific occurrence of an object, for example, during the execution of program code. Additionally, NRF 154 may represent an Nnrf service-based interface.

[0108] PCF 156 can provide policy rules to control plane functions to enforce them and also support a unified policy framework to manage network behavior. PCF 156 can also implement a front-end for accessing subscription information related to policy decisions in the UDR of UDM 158. In addition to communicating with functions via reference points as illustrated, PCF 156 exhibits an Npcf service-based interface.

[0109] UDM 158 processes subscription-related information to support the handling of communication sessions for network entities and may store subscription data for UE 102B. For example, subscription data may be communicated via an N8 reference point between UDM 158 and AMF 144. UDM 158 may consist of two parts: an application frontend and a UDR. The UDR may store subscription and policy data for UDM 158 and PCF 156, and / or structured data for exposure and application data for NEF 152 (including PFD for application discovery and application request information for multiple UE 102B). A Nudr service-based interface may be presented by UDR 546, allowing UDM 158, PCF 156, and NEF 152 to access specific sets of stored data, as well as read notifications of changes to relevant data within the UDR, update (e.g., add, modify), delete, and subscribe. The UDM may include a UDM-FE responsible for certificate processing, location management, enrollment management, etc. Several different frontends can serve the same user in different transactions. The UDM-FE accesses subscription information stored in the UDR and performs authentication credential processing, user identification processing, access authorization, enrollment / mobility management, and subscription management. In addition to communicating with other NFs via a reference point, as shown, the UDM 158 may represent a Nudm service-based interface.

[0110] AF 160 provides application impact on traffic routing, provides access to NEF, and can interact with the policy framework for policy control.

[0111] In some embodiments, the 5GC 140 may enable edge computing by selecting operator / third-party services to be geographically closer to the point where the UE 102B is attached to the network. This can reduce latency and load on the network. To provide an edge computing implementation, the 5GC 140 may select a UPF 148 close to the UE 102B and perform traffic steering from the UPF 148 to the data network 136 via the N6 interface. This may be based on UE subscriber data, UE location, and information provided by the AF 160. In this way, the AF 160 may influence UPF (re)selection and traffic routing. When the AF 160 is considered a trusted entity based on operator deployment, the network operator may allow the AF 160 to interact directly with the relevant NF. Additionally, the AF 160 may represent a NAF service-based interface.

[0112] The LMF 162 is central to the 5G / 6G positioning architecture. The LMF 162 receives measurements and assistance information from the Next Generation Radio Access Network (NG-RAN) 114 and UE 102B via the AMF 160 over the NI 1 interface to calculate the location of UE 102B. Due to a new next-generation interface between the NG-RAN and CN 120, the NR Positioning Protocol A (NRPPa) protocol can carry positioning information between the NG-RAN 114 and LMF 162 over the Next Generation Control Plane Interface (NG-C). The LMF 162 can configure UE 102B using the LTE Positioning Protocol (LPP) via the AMF 144. The NG-RAN 114 can configure UE 102B using the RRC protocol over LTE-Uu and NR-Uu.

[0113] The data network 136 may represent various network operator services, internet access, or third-party services that may be provided by one or more servers, for example, including an application / content server 138.

[0114] Figure 3 shows embodiments relating to network 3000, such as the communication network 100 shown in Figure 1 and 100B shown in Figure 2, according to various embodiments. Network 3000 may operate in a manner consistent with the 3GPP technical specifications or technical reports for 6G systems. In some embodiments, network 3000 may operate concurrently with network 100B. For example, in some embodiments, network 3000 may share one or more frequency or bandwidth resources with network 100B. As one particular example, a UE (e.g., UE 3002) may be configured to operate in both network 3000 and network 100B. Such a configuration may be based on a UE that includes circuitry configured for communication with the frequency and bandwidth resources of both network 100B and network 3000. In general, some elements of network 3000 may share one or more characteristics with elements of network 100B. For brevity and clarity, such elements may not be repeated in the description of network 3000.

[0115] Network 3000 includes UE 3002, which may include any mobile or non-mobile computing device designed to communicate with RAN 3008 via a wireless connection. UE 3002 may be similar to, for example, UE 102B. UE 3002 may include, but is not limited to, smartphones, tablet computers, wearable computing devices, desktop computers, laptop computers, automotive infotainment, automotive entertainment devices, instrument clusters, head-up display devices, onboard diagnostic devices, dashboard mobile devices, mobile data terminals, electronic engine management systems, electronic / engine control units, electronic / engine control modules, embedded systems, sensors, microcontrollers, control modules, engine management systems, networked appliances, machine-type communication devices, M2M or D2D devices, IoT devices, etc.

[0116] Although not specifically shown in Figure 3, in some embodiments, network 3000 may include multiple UEs directly coupled to each other via sidelink interfaces. The UEs may be M2M / D2D devices communicating using physical sidelink channels such as PSBCH, PSDCH, PSSCH, PSCCH, and PSFCH, but are not limited to these. Similarly, although not specifically shown in Figure 3, UE 3002 may be communicably coupled to an AP such as AP 106, as described with respect to Figure 2. Additionally, although not specifically shown in Figure 3, in some embodiments, RAN 3008 may include one or more ANs, such as AN 108, as described with respect to Figure 2. RAN 3008 and / or the ANs of RAN 3008 may be referred to as base stations (BS), RAN nodes, or by any other term or name.

[0117] UE 3002 and RAN 3008 may be configured to communicate via an air interface, which may be referred to as a sixth-generation (6G) air interface. A 6G air interface may include one or more features, such as communication in terahertz (THz) or sub-THz bandwidths, or joint communication and sensing. As used herein, the term “joint communication and sensing” may refer to a system that enables wireless communication, as well as radar-based sensing, through various types of multiplexing. As used herein, THz or sub-THz bandwidth may refer to communication in a frequency range of 80 GHz or higher. Such frequency ranges may be additionally or alternatively referred to as “millimeter wave” or “mmWave” frequency ranges.

[0118] RAN 3008 can enable communication between UE 3002 and 6G core network (CN) 3010. Specifically, RAN 3008 can facilitate the transmission and reception of data between UE 3002 and 6G CN 3010. 6G CN 3010 may include various functions such as NSSF 150, NEF 152, NRF 154, PCF 156, UDM 158, AF 160, SMF 146, AUSF 142, and LMF 162. 6G CN 3010 may further include UPF 148 and DN 136, as shown in Figure 3.

[0119] Additionally, RAN 3008 may include a variety of additional functions that complement or replace the functionality of legacy cellular networks, such as 4G or 5G networks. Two such functions may include Computation Control Function (Comp CF) 3024 and Computation Service Function (Comp SF) 3036. Comp CF 3024 and Comp SF 3036 may be parts or functions of the Computation Service Plane. Comp CF 3024 may be a control plane function that provides functionality such as managing Comp SF 3036, generating and managing computing task contexts (e.g., create, read, modify, delete), and interacting with the underlying computing infrastructure for computing resource management. Comp SF 3036 may be a user plane function that acts as a gateway for interfaceping computing service users (such as UE 3002) and the computing nodes behind Comp SF instances. Some functionalities of Comp SF 3036 may include parsing computing service data received from users to compute tasks that can be performed by computing nodes, maintaining a service mesh entry gateway or service API gateway, enforcing service and billing policies, performance monitoring and telemetry collection, etc. In some embodiments, a Comp SF 3036 instance may function as a user plane gateway for a cluster of computing nodes. A Comp CF 3024 instance may control one or more Comp SF 3036 instances.

[0120] The other two such functions include the Communication Control Function (Comm CF) 3028 and the Communication Service Function (Comm SF) 3038, which may be part of the communication service plane. The Comm CF 3028 may be a control plane function for managing the creation / configuration / release of communication sessions and for managing the communication session context. The Comm SF 3038 may be a user plane function for data transport. The Comm CF 3028 and Comm SF 3038 can be seen as upgrades to the SMF 146 and UPF 148 described in Figure 1B for a 5G system. The upgrades provided by the Comm CF 3028 and Comm SF 3038 may enable service-aware transport. For legacy (e.g., 4G or 5G) data transport, the SMF 146 and UPF 148 may still be used.

[0121] The other two such functions include the Data Control Function (Data CF) 3022 and the Data Service Function (Data SF) 3032, which may be part of the data service plane. The Data CF 3022 is a control plane function and provides functionality such as Data SF 3032 management, creation / configuration / release of data services, and data service context management. The Data SF 3032 is a user plane function and can act as a gateway between data service users (various functions of UE 3002 and 6G CN 3010, etc.) and data service endpoints behind the gateway. Specific functionality may include parsing data service user data and forwarding it to the corresponding data service endpoint, generating billing data, and reporting data service status.

[0122] Another such function may be a Service Orchestration and Chaining Function (SOCF) 3020, which can discover, coordinate, and chain communication / computing / data services provided by functions within the network. Once a service request is received from a user, the SOCF 3020 may interact with one or more of the Comp CF 3024, Comm CF 3028, and Data CF 3022 to identify instances of Comp SF 3036, Comm SF 3038, and Data SF 3032, configure service resources, and generate a service chain that may include multiple instances of Comp SF 3036, Comm SF 3038, and Data SF 3032 and their associated computing endpoints. Within the generated service chain, workload processing and data movement may then occur. The SOCF 3020 may also be responsible for maintaining, updating, and releasing the created service chain.

[0123] Another such function is the Service Registration Function (SRF) 3014, which can act as a registry for system services provided in the user plane, such as services provided by service endpoints behind the Comp SF 3036 and Data SF 3032 gateways, as well as services provided by the UE 3002. SRF 3014 can be considered the counterpart to NRF 154, which can act as a registry for network functions.

[0124] Other such functions include the Evolutionary Service Communications Proxy (eSCP) and the Service Infrastructure Control Function (SICF) 3026, which can provide service communications infrastructure for control plane services and user plane services. The eSCP may be associated with the 5G Service Communications Proxy (SCP) with added user plane service communications proxy capabilities. The eSCP is therefore represented in two parts for the control plane service communications proxy and the user plane service communications proxy, respectively: eSCP-C 3012 and eSCP-U 3034. SICF 3026 can control and configure eSCP instances with respect to service traffic routing policies, access rules, load balancing configurations, performance monitoring, etc.

[0125] Another such function is AMF 3044. AMF 3044 may be similar to 144 but has additional functions. Specifically, AMF 3044 may involve potential functional reclassification, such as moving the message forwarding function from AMF 3044 to RAN 3008.

[0126] Another such function is the service orchestration exposure function (SOEF)3018. The SOEF can be configured to expose service orchestration and chaining services to external users, such as applications.

[0127] UE 3002 may include an additional function called Computing Client Service Function (comp CSF) 3004. Comp CSF 3004 has both control plane and user plane functions and can interact with corresponding network-side functions such as SOCF 3020, Comp CF 3024, Comp SF 3036, Data CF 3022, and / or Data SF 3032 for service discovery, request / response, compute task workload exchange, etc. Comp CSF 3004 can also work with network-side functions to determine whether a compute task should be executed on elements of UE 3002, RAN 3008, and / or 6G CN 3010.

[0128] UE 3002 and / or Comp CSF 3004 may include a service mesh proxy 3006. The service mesh proxy 3006 may act as a proxy for service-to-service communication in the user plane. The capabilities of the service mesh proxy 3006 may include one or more of the following: addressing, security, load balancing, etc.

[0129] Figure 4 shows one embodiment of a simplified block diagram relating to artificial intelligence (AI)-assisted communication between UE 4005 and RAN 4010 according to various embodiments. More specifically, as will be described in further detail below, AI / machine learning (ML) models may be used or leveraged to facilitate wireless communication between UE 4005 and RAN 4010.

[0130] Either or both of UE 4005 and RAN 4010 may operate in a manner consistent with 3GPP technical specifications or technical reports for 6G systems. In some embodiments, radio cellular communication between UE 4005 and RAN 4010 may be part of, or concurrent with, networks 3000, 100B, and / or any other networks described herein.

[0131] UE 4005 is similar to UE 3002, UE 102B, and / or several other UEs described herein, and may share one or more features with them. UE 4005 may, but is not limited to, smartphones, tablet computers, wearable computer devices, desktop computers, laptop computers, automotive infotainment, automotive entertainment devices, instrument clusters, head-up display devices, automotive diagnostic devices, dashboard mobile devices, mobile data terminals, electronic engine management systems, electronic / engine control units, electronic / engine control modules, embedded systems, sensors, microcontrollers, control modules, engine management systems, networked appliances, machine-type communication devices, M2M or D2D devices, IoT devices, etc. RAN 4010 is similar to RAN 114, RAN 3008, and / or several other RANs described herein, and may share one or more features with them.

[0132] As can be seen in Figure 4, AI-related elements in UE 4005 may be similar to AI-related elements in RAN 4010. For the purposes of this specification, descriptions of various elements are provided from the perspective of UE 4005, but it will be understood that such descriptions or representations apply to equally named / numbered elements in RAN 4010 unless otherwise explicitly stated.

[0133] As mentioned above, the UE 4005 may include various elements or functions related to AI / ML. Such elements may be implemented as hardware, software, firmware, and / or any combination thereof. In embodiments, one or more elements may be implemented as part of the same hardware (e.g., a chip or multiprocessor chip), software (e.g., a computing program), or firmware as another element.

[0134] One such element could be a data repository 4015. The data repository 4015 may be responsible for data collection and storage. Specifically, the data repository 4015 may collect and store RAN configuration parameters, measurement data, key performance indicators (KPIs), model performance metrics, etc., for model training, updating, and inference. More generally, the collected data is stored in the repository. The stored data can be discovered and extracted from the data repository 4015 by other elements. For example, as can be understood, the inference data selection / filter element 4050 may retrieve data from the data repository 4015. In various embodiments, the UE 4005 may be configured to discover and request data from the data repository 4010 in the RAN, and vice versa. More generally, the data repository 4015 of the UE 4005 may be communicatively coupled with the data repository 4015 of the RAN 4010 so that the respective data repositories of the UE and RAN can share the collected data with each other.

[0135] Another such element may be the training data selection / filtering function block 4020. The training data selection / filtering function block 4020 may be configured to generate training, validation, and test datasets for model training. The training data may be extracted from the data repository 4015. The data may be selected / filtered based on the specific AI / ML model to be trained. The data may optionally be transformed / expanded / preprocessed (e.g., normalized) before being loaded into the dataset. The training data selection / filtering function block 4020 may label the data in the dataset for supervised learning. The generated dataset may then be fed into the model training function block 4025.

[0136] As described above, another such element may be the model training function block 4025. This function block may be responsible for training and updating (retraining) AI / ML models such as encoder NNs and decoder NNs, which are described in conjunction with other figures in this specification. The selected model may be trained using fed-in datasets (including training, validation, and testing) from the training data selection / filtering function block. The model training function block 4025 may generate a trained and tested AI / ML model that is ready for deployment. The generated trained and tested models may be stored in the model repository 4035.

[0137] The model repository 4035 may be responsible for storing and publishing AI / ML models (both trained and untrained). Trained / updated models may be stored in the model repository 4035. Models and model parameters may be discovered and requested by other functional blocks (e.g., the training data selection / filter functional block 4020, and / or the model training functional block 4025). In some embodiments, the UE 4005 may discover and request AI / ML models from the model repository 4035 of the RAN 4010. Similarly, the RAN 4010 may discover and / or request AI / ML models from the model repository 4035 of the UE 4005. In some embodiments, the RAN 4010 may constitute models and / or model parameters in the model repository 4035 of the UE 4005.

[0138] Another such element may be the model management function block 4040. The model management function block 4040 may be responsible for managing the AI / ML models generated by the model training function block 4025. In model deployment, the model management function block 4040 can allocate and schedule hardware and / or software resources for inference based on the received trained and tested models. As used herein, “inference” refers to the process of using the trained AI / ML model to generate data analysis, actions, policies, etc., based on input inference data. In performance monitoring, based on wireless performance KPIs and model performance metrics, the model management function block 4040 may decide to terminate the running model, start model retraining, select a different model, etc. In embodiments, the model management function block 4040 of RAN 4010 may be capable of configuring model management policies in UE 4005, as shown in the figure.

[0139] Another such element could be the inference data selection / filtering function block 4050. The inference data selection / filtering function block 4050 may be responsible for generating the dataset for model inference in the inference function block 4045, as described below. Specifically, the inference data may be extracted from the data repository 4015. The inference data selection / filtering function block 4050 may select and / or filter the data based on the deployed AI / ML model. The data may be transformed / enhanced / preprocessed according to the same transformation / enhanced / preprocessing as in the training data selection / filtering described with respect to function block 4020. The generated inference dataset may be provided to the inference function block 4045.

[0140] Another such element could be the inference function block 4045. The inference function block 4045 may be responsible for performing inference, as described above. Specifically, the inference function block 4045 may consume the inference dataset provided by the inference data selection / filtering function block 4050 and generate one or more results. Such results may be, or include, data analysis, actions, policies, etc. The results may be provided to the performance measurement function block 4030.

[0141] The performance measurement function block 4030 may be configured to measure model performance metrics (e.g., accuracy, model bias, runtime latency, etc.) of the deployed and running model based on inference results for monitoring purposes. Model performance data may be stored in the data repository 4015.

[0142] Figure 5 shows one embodiment of a simplified block diagram 500 relating to a base station 501 and a UE 511 that can perform a predetermined embodiment in a communication network such as a base station or RAN, user equipment (UE), and communication network shown in Figures 1-4. Antenna 546 transmits and receives radio signals to base station 510. RF circuit 544, which is the physical layer of base station 510 and coupled with antenna 546, receives RF signals from antenna 546 and performs operations on the signal such as amplifying the signal and splitting the signal into quadrature-phase signals and common-phase signals. The receiver circuit 590 converts the signal into a digital baseband signal or uplink data and may pass the digital common-mode and quadrature-phase signals to the processor 520 of the baseband circuit 514, also called the processing circuit or baseband processing circuit, via an interface 525 of the baseband circuit 514 for communications (e.g., RF interface 1416 shown in Figure 14) for communications such as an interface for network communications with the UE, an interface for network communications with a core cellular network such as a 5G core, an interface for network communications with other base stations, or an interface for other related network communications. In other embodiments, an analog-to-digital converter of the processor 520 may convert the common-mode and quadrature-phase signals into a digital baseband signal.

[0143] The transmitter circuit 592 can convert the digital baseband signal or downlink data received from the processor 520 into an analog signal. The RF circuit 544 processes and amplifies the analog signal, converts the analog signal into an RF signal, and distributes the amplified analog RF signal to the antenna 546.

[0144] The processor 520 decodes and processes digital baseband signals, or uplink data, and calls different functional modules to perform features at the base station 510. Memory 522 stores program instructions, or code and data 524, for controlling the operation of the base station 510. The host circuit 512 may execute code, such as RRC layer code from code and data 524, to implement RRC layer functionality and code. Note that code executed on top of the media access control (MAC) layer and physical layer (PHY) is often referred to as upper-layer code.

[0145] A similar configuration exists within UE 560, where antenna 596 transmits and receives RF signals. RF circuit 594 coupled with antenna 596 receives RF signals from antenna 596, amplifies the RF signals, and processes the signals to generate analog common-mode and quadrature-phase signals. Receiver circuit 590 processes the analog common-mode and quadrature-phase signals, converts them to digital baseband signals or downlink data via an analog-to-digital converter, and passes the common-mode and quadrature-phase signals to the baseband circuit 564's processor 570 via interface 575 (e.g., RF interface 1416 shown in Figure 14) for communication such as an interface for network communication with other UEs, an interface for network communication with a base station, or an interface for other related network communication. In other embodiments, processor 570 may include an analog-to-digital converter for converting the analog common-mode and analog quadrature-phase signals to digital common-mode and digital quadrature-phase signals.

[0146] The transmitter circuit 592 can convert the digital baseband signal or downlink data received from the processor 570 into an analog signal. The RF circuit 594 processes and amplifies the analog signal, converts the analog signal into an RF signal, and distributes the amplified analog RF signal to the antenna 596.

[0147] RF circuit 594 shows multiple RF chains. RF circuit 594 shows four RF chains, but each UE may have a different number of RF chains, such as eight RF chains. Each of the RF chains in the figure may represent multiple time-domain receive (RX) chains and transmit (TX) chains. The RX and TX chains include circuits that operate on or can modify time-domain signals transmitted through the time-domain chains, such as circuits for inserting guard intervals in the TX chain and circuits for removing guard intervals in the RX chain. For example, RF circuit 594 may include a transmit circuit and a receive circuit, often called a transceiver circuit. The transmitter circuit may prepare digital data from the processor 570 for transmission through the antenna 596. In preparing for transmission, the transmitter may encode the data, modulate the encoded data, and form the modulated and encoded data into orthogonal frequency division multiplexing (OFDM) and / or orthogonal frequency division multiple access (OFDMA) symbols. Subsequently, the transmitter may convert symbols from the frequency domain to the time domain for input to the TX chain. The TX chain may contain a chain for each subcarrier of the RF chain's bandwidth. It may then operate on those time-domain signals to prepare the time-domain signals in the TX chain for transmission on the component subcarriers of the RF chain. In the case of broadband communication, two or more of the RF chains may simultaneously process symbols representing data from the baseband processor.

[0148] The processor 570 decodes and processes digital baseband signals, or downlink data, and calls different functional modules to perform features in the UE 560. Memory 572 stores program instructions or code and data 574 for controlling the operation of the UE 560. The processor 570 may also execute medium access control (MAC) layer code relating to the code and data 574 for the UE 560. For example, MAC layer code may be executed on the processor 570 to cause UL communications to be transmitted to the base station 510 via one or more RF chains of the physical layer (PHY). The PHY consists of the RF circuitry 594 and associated logic such as some or all of the functional modules.

[0149] The host circuit 562 may execute code such as RRC layer code for implementing RRC layer functionality and code or RRM layer code for implementing RRM layer functionality. In some embodiments, the RRC layer code may be upper layer code that provides configuration information to the frequency hop logic circuits 535 and 580 of the base station 510 and UE 560, respectively, via upper layer signaling. The configuration information provided by the upper layer may include parameters such as transmit mode (txConfig), push configuration (puschconfig), dmrs-Type, maxLength, and the number of codewords.

[0150] The base station 510 and UE 560 may include several functional modules and circuits to perform several embodiments. Different functional modules may include circuits or circuit configurations that can be composed of and implemented by code, hardware, or any combination thereof. Each functional module that can implement a function, either as code and processing circuits or as circuits configured to perform a function, may also be called a functional block. For example, the processor 520 is a functional block for composing and implementing the circuits of a functional module so that the base station 510 can schedule (via scheduler 526), ​​encode or decode (via codec 528), modulate or demodulate (via modulator 530), and transmit or receive data to or from the UE 560 via RF circuit 544 and antenna 546.

[0151] The processor 570 may be a functional block for configuring and implementing the circuitry of a functional module so that the UE 560 can, as appropriate, receive or transmit data via the RF circuit 594 and antenna 596, demodulate or modulate it (via demodulator 578), and decode or encode it (via codec 576).

[0152] The base station 510 may also include a functional module, a frequency hop logic circuit 535. The frequency hop logic circuit 535 of the base station 510 may communicate with the LMF via LPP to determine one or more positioning configurations for the UE 560 for positioning measurement. In some embodiments, other cellular management functions and / or protocols may provide positioning configurations to the base station 510 for the UE 560 for positioning measurement. For example, in some embodiments, the LMF may decide to assign a per-UE measurement gap configuration for positioning measurement to the UE 560. In some embodiments, the LMF may decide to assign a per-FR measurement gap configuration for positioning measurement to the UE 560, and may assign a per-FR1 measurement gap, a per-FR2 measurement gap, or both per-FR1 and per-FR2 measurement gaps to the UE 560. In many embodiments, the LMF, the frequency hop logic circuit 535 of the base station 510, or another network component may configure or preconfigure the UE 560 with a positioning measurement gap configuration to identify time and frequency resources (RB) for one or more measurement gaps.

[0153] In many embodiments, the LMF, the frequency hop logic circuit 535 of the base station 510, or another network component may also constitute a PRS for transmission during the iteration of the measurement gap. In many embodiments, the PRS is configured to be available for measurement throughout the measurement gap of the UE 560 so that the UE 560 can determine the timing for frequency hops throughout each iteration of the measurement gap in order to perform positioning measurements.

[0154] The UE 560 may also include a functional module, a frequency hop logic circuit 580. The frequency hop logic circuit 580 of the UE 560 can cause the processor 570 and / or host circuit 562 to receive one or more configurations for positioning measurements, store one or more configurations in memory 572, and access one or more configurations to perform one or more positioning measurements of one or more measurement types, such as reference signal time difference (RSTD) measurement, positioning reference signal-received reference signal power (PRS-RSRP) measurement, UE Rx-TX time difference measurement, and positioning reference signal-received signal power (PRS-RSRPP) measurement. The frequency hop logic circuit 580 of the UE 560 may perform positioning measurements based on the accuracy requirements and measurement delays corresponding to the measurement types. To improve the accuracy of the positioning measurements, the UE 560 may perform more measurements of the PRS within the corresponding measurement delays.

[0155] To perform positioning measurements, the frequency hop logic circuit 580 of the UE 560 may determine a series of two or more frequency hops between the positioning frequency layers of the PRS in a measurement gap iteration. Each frequency hop may involve retuning the receiver of the UE. Thus, the determination of the number of frequency hops may also take into account the delay associated with retuning.

[0156] In many embodiments, the RBs of the positioning frequency layers may overlap to account for the phase difference between measurements of different positioning frequency layers during the measurement gap. For example, if the UE is configured or pre-configured for each UE's measurement gap, the frequency hop logic circuit 580 of the UE 560 may determine the number of frequency hops to perform RSTD measurements, PRS-RSRP measurements, UE Rx-TX time difference measurements, and PRS-RSRPP measurements, so that positioning measurement reports for each measurement type can be transmitted to the base station 560 within the corresponding measurement delay. The measurement delay may be defined as the number of iterations of the measurement gap iteration period (MGRP), and may be defined differently for each of the different measurement types. In some embodiments, the maximum measurement delay for each of the different measurement types is four iterations of the measurement gap or four MGRPs.

[0157] In many embodiments, the frequency hop logic circuit 580 of the UE 560 may generate a positioning measurement report for each of the measurement types, such as RSTD measurement, PRS-RSRP measurement, UE Rx-TX time difference measurement, and PRS-RSRPP measurement, and trigger transmission to the base station 510.

[0158] Figure 6 shows one embodiment relating to Table 600 for gap combination configuration identifiers (IDs) for identifying per-UE or per-FR measurement gap patterns to the frequency hop logic circuit of a UE, such as the embodiments described in relation to Figures 1-5. Table 600 shows the number of gap combination configurations by UE that support both simultaneously measured gap patterns and independently measured gap patterns.

[0159] The requirement applies when a UE requires a measurement gap to identify and measure intra-frequency cells and / or inter-frequency cells and / or inter-RAT E-UTRAN cells, and the UE supports specifying concurrentPerUE-OnlyMeasGap-r17. For this requirement to apply, a cellular network may provide up to two per-UE measurement gap patterns (MGPs) for monitoring all frequency layers.

[0160] If the UE requires a measurement gap to identify and measure intra-frequency cells and / or inter-frequency cells and / or inter-RAT E-UTRAN cells, and the UE supports specifying concurrentPerUE-PerFRCombMeasGap-r17 to apply defined requirements for simultaneous measurement gaps, then the cellular network can provide the MGP combinations specified in Table 600 for monitoring all frequency layers.

[0161] If the UE is unable to perform concurrentMeasGapEUTRA-r17, all E-UTRAN measurements are expected to be associated with a single concurrent MGP. The requirement does not apply if the UE supports concurrent measurement gap patterns and consists of two or more measurement gap patterns per FR or per UE, according to Table 600, and the UE is configured with two or more MGPs with a measurement gap iteration period (MGRP) of 20 milliseconds (ms) in the FR.

[0162] Table 600 includes columns for gap combination configuration IDs and columns for simultaneous measurement gap patterns. The column for simultaneous measurement gap patterns may have three sub-columns to identify the patterns of measurement gaps per FR1, per FR2, and per UE.

[0163] Each row, such as rows 610, 620, and 630, identifies a measurement gap pattern for a specific gap combination configuration ID. For example, row 610 identifies gap combination configuration ID 3 as having one measurement gap in FR1 when the UE is configured for measurement gaps per FR, or as having one measurement gap when the UE is configured for measurement gaps per UE. Row 620 identifies gap combination configuration ID 4 as having one measurement gap in FR2 when the UE is configured for measurement gaps per FR, or as having one measurement gap when the UE is configured for measurement gaps per UE. Row 6300 identifies gap combination configuration ID 5 as having one measurement gap in FR1 and one measurement gap in FR2 when the UE is configured for measurement gaps per FR, or as having one measurement gap when the UE is configured for measurement gaps per UE.

[0164] Figure 7 shows a flowchart 700 of an embodiment of a frequency hop logic circuit of a user device for performing frequency hops between positioning frequency layers for positioning-related measurements, such as the embodiments described in relation to Figures 1-6. Flowchart 700 begins with the frequency hop logic circuit of a UE in a cellular network determining the frequency range of the PRS based on the PRS configuration, where the PRS configuration defines the resource block of the PRS positioning frequency layer (element 710). The UE is configured, or may be pre-configured, with measurement gap configurations for performing positioning measurements for measurement types such as reference signal time difference (RSTD) measurement, positioning reference signal-reference signal received power (PRS-RSRP) measurement, UE Rx-TX time difference measurement, and positioning reference signal-received signal received path power (PRS-RSRPP) measurement.

[0165] DL RSTD is T SubframeRxj-TSubframeRxi This is defined as the DL relative timing difference between the transmission point (TP)j and the reference TPi. Here, T SubframeRxj This is the time when the UE receives the start of one subframe from TPj. T SubframeRxi This is the time when the UE receives from TPi the corresponding start of the one subframe that is temporally closest to the subframe received from TPj.

[0166] Multiple DL PRS resources may be used to determine the start of a single subframe from the TP. For frequency range 1 (FR1), the reference point for DL ​​RSTD may be the antenna connector of the UE. For frequency range 2 (FR2), the reference point for DL ​​RSTD may be the antenna of the UE.

[0167] DL PRS reference signal received power (DL PRS-RSRP) is defined as the linear average of the power contributions ([Watts]) of resource elements carrying the DL PRS reference signal configured for RSRP measurements within the measurement frequency bandwidth under consideration.

[0168] For the frequency range 1 (FR1), the reference point for DL PRS-RSRP can be the UE's antenna connector. For the frequency range 2 (FR2), the DL PRS-RSRP can be measured based on the combined signal from the antenna elements corresponding to a given receiver branch. For the frequency ranges 1 and 2 (FR1 and FR2), when receiver diversity is being used by the UE, the reported DL PRS-RSRP value may not be lower than the corresponding DL PRS-RSRP of any of the individual receiver branches.

[0169] The UE Rx-Tx time difference is defined as T UE-RX - T UE-TX as defined below. Here, T UE_RX is the UE receive timing of the downlink subframe #i from the transmission point (TP), defined by the first detected path within the time. T UE_TX is the UE transmit timing of the uplink subframe #j closest in time to the subframe #i received from the TP. Multiple DL PRSs or channel state information reference signals (CSI-RSs) for tracking resources can be used to determine the start of one subframe of the first arrival path of the TP, as commanded by the upper layer.

[0170] For the frequency range 1 (FR1), the reference point for T UE-RX measurement is the UE's Rx antenna connector, and the reference point for T UE-TX measurement can be the UE's Tx antenna connector. For the frequency range 2 (FR2), the reference point for T UE-RX measurement is the UE's Rx antenna, and the reference point for T UE-TX measurement can be the UE's Tx antenna.

[0171] DL PRS reference signal receive path power (DL PRS-RSRPP) is defined as the linear average power of the channel response at the i-th path delay of the resource element carrying the DL PRS signal configured for measurement. Here, DL PRS-RSRPP for the first path delay is the power contribution corresponding to the first detection path in time.

[0172] For frequency range 1 (FR1), the reference point for DL ​​PRS-RSRPP may be the antenna connector of the UE. For frequency range 2 (FR2), DL PRS-RSRPP may be measured based on the combined signal from the antenna elements corresponding to a given receiver branch.

[0173] For frequency ranges 1 and 2 (FR1 and FR2), when receiver diversity is used by the UE for DL ​​PRS-RSRPP measurements, the reported DL PRS-RSRPP values ​​included within the upper-layer parameter NR-DL-AoD-MeasElement for the first and additional measurements may be provided for the same receiver branch applied for DL ​​PRS-RSRP measurements.

[0174] In element 715, the frequency hop logic circuit of the UE determines the number of frequency hops between positioning frequency layers associated with the frequency range of the PRS during iterations of one measurement gap based on the measurement gap configuration per UE, or up to two measurement gaps based on the measurement gap configuration per frequency range (FR), in order to perform PRS measurements within at least one measurement delay. Each of the frequency layers associated with the number of frequency hops during iterations of one measurement gap or up to two measurement gaps may be associated with different bandwidth portions of the PRS. In many embodiments, the BW portions of the PRS may overlap, and as a result, the frequency hop logic circuit of the UE may adjust the measurement for phase difference via the overlapping RBs.

[0175] In some embodiments, the UE is configured with a positioning gap via base stations such as gNBs, through the Location Management Function (LMF) of the core network. The positioning gap configuration may reside in the UE's memory. In further embodiments, another cellular network component may configure or preconfigure the UE using the positioning gap.

[0176] In many embodiments, the positioning gap configuration is associated as a positioning gap configuration per UE or per FR. In some embodiments, the choice between a positioning gap configuration per UE or per FR is based on the capabilities of the UE. In further embodiments, the choice between a positioning gap configuration per UE or per FR is determined by the cellular network.

[0177] In a positioning measurement gap configuration per UE, the UE may be configured with a single measurement gap having a periodicity of the measurement gap iteration period (MGRP). The frequency hop logic circuit of the UE may then determine the number of frequency hops for each iteration of the measurement gap, based on performing the positioning measurement within the measurement delay. A different measurement delay may be established for each of the different positioning measurement types, or they may all be the same measurement delay. In many embodiments, the measurement delay may be defined as the number of iterations of the measurement gap.

[0178] In a positioning measurement gap configuration per FR, the UE may be configured using one measurement gap per FR (e.g., one MG for FR1, one MG for FR2, or one MG for FR1 and one MG for FR2). Each measurement gap per FR may have a periodicity of measurement gap iteration period (MGRP). The frequency hop logic circuit of the UE may then determine the number of frequency hops for each iteration of the measurement gap for each FR, based on performing positioning measurements within the measurement delay for each FR.

[0179] In element 720, the frequency hop logic circuit of the UE can perform numerous frequency hops and measurements of the PRS during each iteration of the measurement gap configuration, which may consist of one measurement gap per UE or up to two measurement gaps per FR. In many embodiments, for each UE, all positioning frequency layers are measured or associated with just one measurement gap per UE. In many embodiments, for each FR, all positioning frequency layers within the same FR are measured or associated with just one measurement gap per FR within the corresponding FR.

[0180] In element 725, the frequency hop logic circuit of the UE can trigger the transmission of at least one positioning measurement report via the interface. In many embodiments, the measurement delay is defined for each measurement type (RSTD, PRS-RSRP, UE Rx-TX time difference, and PRS-RSRPP) and includes up to four iterations relating to one measurement gap per UE or up to two measurement gaps per FR. The frequency hop logic circuit of the UE can trigger the transmission of each positioning measurement report for each of the measurement types within the measurement delay corresponding for each measurement type.

[0181] Figure 8 shows one embodiment of a protocol entity 8000 that may be implemented in a wireless communication device. In this specification, it includes, according to several embodiments, one or more of the following: a base station, which may be called a user device (UE) 8060, an advanced node B (eNB), or a new radio, a next-generation node B (gNB) 8080, and a network function, which may be called a mobility management entity (MME), or an access and mobility management function (AMF) 8094. In further embodiments, the NodeB may include an xNodeB for the sixth generation and beyond.

[0182] In some embodiments, the gNB 8080 may be implemented as one or more dedicated physical devices, such as macrocells, femtocells, or other suitable devices, or, in an alternative embodiment, as one or more software entities running on a server computer as part of a virtual network called a Cloud Radio Access Network (CRAN).

[0183] In some embodiments, one or more protocol entities that can be implemented in one or more of the UE 8060, gNB 8080, and AMF 8094 may be described as implementing all or part of a protocol stack, where the layers are considered to be ordered from lowest to highest in the order of Physical Layer (PHY), Media Access Control (MAC), Radio Link Control (RLC), Packet Data Convergence Protocol (PDCP), Radio Resource Control (RRC), and Non-Access Layer (NAS). In some embodiments, one or more protocol entities that can be implemented in one or more of the UE 8060, gNB 8080, and AMF 8094 may communicate with their respective peer protocol entities, which may be implemented on other devices, by using the services of their respective lower-layer protocol entities in order to perform such communications.

[0184] In some embodiments, UE PHY layer 8072 and peer entity gNB PHY layer 8090 may communicate using signals transmitted and received over a radio medium. In some embodiments, UE MAC layer 8070 and peer entity gNB MAC layer 8088 may communicate using services provided to them, respectively, by UE PHY layer 872 and gNB PHY layer 8090. In some embodiments, UE RLC layer 8068 and peer entity gNB RLC layer 8086 may communicate using services provided to them, respectively, by UE MAC layer 8070 and gNB MAC layer 8088. In some embodiments, UE PDCP layer 8066 and peer entity gNB PDCP layer 8084 may communicate using services provided to them, respectively, by UE RLC layer 8068 and gNB RLC layer 8086. In some embodiments, the UE RRC layer 8064 and the gNB RRC layer 8082 may communicate using services provided to them, respectively, by the UE PDCP layer 8066 and the gNB PDCP layer 8084. In some embodiments, the UE NAS 8062 and the AMF NAS 8092 may communicate using services provided to them, respectively, by the UE RRC layer 8064 and the gNB RRC layer 8082.

[0185] PHY layers 8072 and 8090 can transmit or receive information used by MAC layers 8070 and 8088 across one or more air interfaces. PHY layers 8072 and 8090 can further perform link adaptive or adaptive modulation and coding (AMC), power control, cell search (e.g., for initial synchronization and handover purposes), and other measurements used by higher layers, such as RRC layers 8064 and 8082. PHY layers 8072 and 8090 can also perform error detection on transport channels, forward error correction (FEC) coding / decoding of transport channels, modulation / demodulation of physical channels, interleaving, rate matching, mapping onto physical channels, and even multi-input multiple-output (MIMO) antenna processing.

[0186] MAC layers 8070 and 8088 can perform the following: mapping between logical channels and transport channels; multiplexing MAC service data units (SDUs) from one or more logical channels onto transport blocks (TBs) to be delivered to the PHY via transport channels; demultiplexing MAC SDUs from transport blocks (TBs) delivered from the PHY via transport channels to one or more logical channels; multiplexing MAC SDUs onto TBs; scheduling information reporting; error correction via Hybrid Automatic Retransmission Requests (HARQs); and logical channel prioritization.

[0187] RLC layers 8068 and 8086 can operate in multiple operating modes, including: Transparent Mode (TM), Unacknowledged Mode (UM), and Acknowledged Mode (AM). RLC layers 8068 and 8086 can perform forwarding of upper-layer protocol data units (PDUs), error correction through automatic retransmission requests (ARQs) for AM data transfers, and concatenation, segmentation, and reassembly of RLC SDUs for UM and AM data transfers. RLC layers 8068 and 8086 can also perform resegmentation of RLC data PDUs for AM data transfers, reordering of RLC data PDUs for UM and AM data transfers, detection of overlapping data for UM and AM data transfers, discarding of RLC SDUs for UM and AM data transfers, detection of protocol errors for AM data transfers, and RLC re-establishment.

[0188] PDCP layers 8066 and 8084 can perform header compression and decompression of Internet Protocol (IP) data, maintain PDCP sequence numbers (SNs), perform in-sequence delivery of upper layer PDUs in lower layer re-establishment, remove overlap of lower layer SDUs in lower layer re-establishment for radio bearers mapped on RLC AM, encrypt and decrypt control plane data, perform integrity protection and integrity verification of control plane data, control timer-based discarding of data, and perform security operations (e.g., encryption, decryption, integrity protection, integrity verification, etc.).

[0189] The main services and functions of RRC layers 8064 and 8082 may include broadcasting system information (e.g., contained in Master Information Blocks (MIBs) or System Information Blocks (SIBs) related to the Non-Access Layer (NAS)), broadcasting system information related to the Access Layer (AS), paging, establishing, maintaining, and releasing RRC connections between the UE and E-UTRAN (e.g., RRC connection paging, RRC connection establishment, RRC connection modification, and RRC connection release), establishing, configuring, maintaining, and releasing point-to-point radio bearers, security functions including key management, radio access technology (RAT) mobility, and measurement configurations for UE measurement reporting. The MIBs and SIBs each contain one or more information elements (IEs), each of which may contain individual data fields or data structures.

[0190] The UE 8060 and RAN node, gNB 8080, can exchange control plane data via a protocol stack comprising PHY layers 8072 and 8090, MAC layers 8070 and 8088, RLC layers 8068 and 8086, PDCP layers 8066 and 8084, and RRC layers 8064 and 8082, utilizing a Uu interface (e.g., LTE-Uu interface).

[0191] The Non-Access Layer (NAS) protocol 8092 forms the top layer of the control plane between the UE 8060 and the AMF 8005. The NAS protocol 8092 supports the mobility and session management procedures of the UE 8060 to establish and maintain IP connectivity between the UE 8060 and the Packet Data Network (PDN) gateway (P-GW).

[0192] Figure 9 shows embodiments of the format of a PHY data unit (PDU) that is transmitted by a PHY device via one or more antennas and can be encoded and decoded by MAC entities such as processors 520 and 570, described in conjunction with Figure 5, and baseband circuitry 1304, described in conjunction with Figures 13 and 14, and / or in conjunction with other figures herein. In some embodiments, upper layer frames, such as frames containing RRC layer information elements, can be transmitted from a base station to a UE or vice versa as one or more MAC service data units (MSDUs) in the payload of one or more PDUs in one or more subframes of a radio frame.

[0193] In some embodiments, the MAC PDU 9100 may consist of a MAC header 9105 and a MAC payload 9110. The MAC payload consists of zero or more MAC control elements 9130, zero or more MAC service data unit (SDU) portions 9135, and zero or one padding portion 9140. In some embodiments, the MAC header 8105 may consist of one or more MAC subheaders, each of which may correspond to a MAC payload portion and appear in a corresponding order. In some embodiments, each of the zero or more MAC control elements 9130 included in the MAC payload 9110 may correspond to a fixed-length subheader 9115 included in the MAC header 9105. In some embodiments, each of the zero or more MAC SDU portions 9135 included in the MAC payload 9110 may correspond to a variable-length subheader 9120 included in the MAC header 8105. In some embodiments, the padding portion 9140 included in the MAC payload 9110 may correspond to the padding subheader 9125 included in the MAC header 9105.

[0194] Figure 10A, shown in conjunction with Figure 5 or other figures herein, illustrates embodiments of the communication circuit 1000, such as the circuitry in the base station 510 and user equipment 560 described herein. Alternatively, the communication circuit 1000 can be grouped according to its function. Components shown in the communication circuit 1000 are shown herein for illustrative purposes only and may include other components not shown herein in Figure 10A.

[0195] The communication circuit 1000 may include a protocol processing circuit 1005. It may implement one or more of the following functions: media access control (MAC), radio link control (RLC), packet data convergence protocol (PDCP), radio resource control (RRC), and non-access layer (NAS). The protocol processing circuit 1005 may include one or more processing cores (not shown) for executing instructions, and one or more memory structures (not shown) for storing program (code) and data information.

[0196] The communication circuit 1000 may further include a digital baseband circuit 1010, which may include one or more of the following functions: hybrid automatic retransmission request (HARQ) functionality, scrambling and / or descrambling, coding and / or decoding, layer mapping and / or demapping, modulation symbol mapping, received symbol and / or bitmetric determination, multi-antenna port precoding and / or decoding which may include one or more of spatiotemporal, spatial frequency, or spatial coding, reference signal generation and / or detection, preamble sequence generation and / or decoding, synchronization sequence generation and / or detection, control channel signal blind decoding, and one or more other related functions.

[0197] The communication circuit 1000 may further include a transmitting circuit 1015, a receiving circuit 1020, and / or an antenna array 1030 circuit.

[0198] The communication circuit 1000 may further include radio frequency (RF) circuits 1025, such as RF circuits 544 and 594 in Figure 2. In one embodiment of one of the embodiments, the RF circuit 1025 may include a plurality of parallel RF chains for one or more transmitting or receiving functions, each connected to one or more antennas of the antenna array 1030.

[0199] In one aspect of this disclosure, the protocol processing circuit 1005 may include one or more instances of a control circuit (not shown) for providing control functions for one or more of the digital baseband circuit 1010, the transmitting circuit 1015, the receiving circuit 1020, and / or the radio frequency circuit 1025.

[0200] Figure 10B, shown in conjunction with Figure 5 or other figures herein, illustrates one embodiment of the radio frequency circuit 1025 of Figure 10A, according to several embodiments, such as the RF circuits 544 and 594 described herein. The radio frequency circuit 1025 may include one or more instances of the radio chain circuit 1072. In some embodiments, it may include one or more filters, power amplifiers, low-noise amplifiers, programmable phase shifters, and power supplies (not shown).

[0201] The radio frequency circuit 1025 may include a power combining and splitting circuit 1074. In some embodiments, the power combining and splitting circuit 1074 may operate bidirectionally, and as a result, the same physical circuit may operate as a power divider when the device is transmitting and as a power combiner when the device is receiving. In some embodiments, the power combining and splitting circuit 1074 may include one or more entirely or partially separate circuits to perform power splitting when the device is transmitting and power combining when the device is receiving. In some embodiments, the power combining and splitting circuit 1074 may include passive circuitry comprising one or more bidirectional power dividers / couplers arranged in a tree structure. In some embodiments, the power combining and splitting circuit 1074 may include active circuitry comprising amplifier circuits.

[0202] In some embodiments, the radio frequency circuit 1025 may be connected to the transmitting circuit 1015 and receiving circuit 1020 of Figure 10A via one or more radio chain interfaces 1076, or a combined radio chain interface 1078. The combined radio chain interface 1078 may form a wide or very wide bandwidth.

[0203] In some embodiments, one or more wireless chain interfaces 1076 may provide one or more interfaces to one or more received or transmitted signals, each associated with a single antenna structure that may comprise one or more antennas.

[0204] In some embodiments, the coupled wireless chain interface 1078 may provide a single interface to one or more received or transmitted signals, associated with a group of antenna structures, each having one or more antennas.

[0205] Figure 11 shows an example of a storage medium 1100 for storing code and data for execution by any one or more processors and / or processing circuits in order to perform the functions of the logic circuits described herein in relation to Figures 1-10 and 12-15. The storage medium 1100 may comprise an article of manufacture. In some examples, the storage medium 1100 may include any non-temporary computer-readable or machine-readable medium, such as optical, magnetic, or semiconductor storage devices. The storage medium 1100 may store various types of computer-executable instructions, such as logic flows and / or instructions for implementing the techniques described herein. Examples of computer-readable or machine-readable storage media may include any tangible medium capable of storing electronic data, including volatile or non-volatile memory, removable or non-removable memory, erasable or non-erasable memory, writable or rewritable memory, and the like. Examples of computer executable instructions can include any appropriate type of code, such as source code, compiled code, interpreted code, executable code, static code, dynamic code, object-oriented code, and visual code.

[0206] Figure 12 shows an architecture relating to a network system 1200 according to several embodiments. System 1200 is shown to include user equipment (UEs) 1510 and UE 1522, such as UEs described in relation to Figures 1-11. UEs 1510 and 1522 are shown as smartphones (e.g., handheld touchscreen mobile computing devices capable of connecting to one or more cellular networks), but may also include any mobile or non-mobile computing devices, such as personal digital assistants (PDAs), pagers, laptop computers, desktop computers, wireless handsets, or any computing devices including wireless communication interfaces.

[0207] In some embodiments, either UE 1510 or 1522 may feature an Internet of Things (IoT) UE. It may feature a network access layer designed for low-power IoT applications that leverage short-lived UE connectivity. The IoT UE may utilize technologies such as public land mobile network (PLMN), proximity-based service (ProSe) or device-to-device (D2D) communication, sensor networks, or machine-to-machine (M2M) or machine-type communication (MTC) to exchange data with MTC servers or devices over the IoT network. M2M or MTC data exchange may be machine-initiated data exchange. The IoT network describes interconnecting IoT UEs, which may include uniquely identifiable embedded computing devices (within the Internet infrastructure), with ephemeral connections. The IoT UE may run background applications (e.g., keep-alive messages, status updates, etc.) to facilitate connectivity within the IoT network.

[0208] UEs 1510 and 1522 can be connected to a radio access network (RAN), for example, in a communicative manner. In this embodiment, this is an evolved universal mobile telecommunications system (UMTS) terrestrial radio access network (E-UTRAN) 1210, such as the base station shown in Figures 1-11. UEs 1510 and 1522 utilize connections 1520 and 1204, respectively, each of which includes a physical communication interface or layer (discussed in more detail below). In other words, in this embodiment, connections 1520 and 1204 are shown as air interfaces to enable communicable coupling and can be compatible with cellular communication protocols such as Global System for Mobile Communications (GSM) protocol, Code Division Multiple Access (CDMA) network protocol, Push-to-Talk (PTT) protocol, PTT over Cellular (POC) protocol, Universal Mobile Telecommunications System (UMTS) protocol, 3GPP Long Term Evolution (LTE) protocol, 5G protocol, New Radio (NR) protocol, etc.

[0209] In this embodiment, UEs 1510 and 1522 may further exchange communication data directly via the ProSe interface 1205. The ProSe interface 1205 may alternatively be called a sidelink interface having one or more logical channels, including, but not limited to, a physical sidelink control channel (PSCCH), a physical sidelink sharing channel (PSSCH), a physical sidelink discovery channel (PSDCH), and a physical sidelink broadcast channel (PSBCH).

[0210] UE 1522 is shown to be configured to access access point (AP) 1206 via connection 1207. Connection 1207 may have a local radio connection, such as a connection compliant with any IEEE 802.11 protocol. Here, AP 1206 has a Wireless Fidelity (WiFi®) router. In this example, AP 1206 is shown to connect to the Internet without connecting to the core network of the radio system (described in more detail below). E-UTRAN 1210 may include one or more access nodes that enable connections 1520 and 1204. These access nodes (ANs) may be called base stations (BS), node B, advanced node B (eNB), next-generation node B (gNB), RAN nodes, etc., and may have ground stations (e.g., ground access points) or satellite stations that provide coverage within a geographical area (e.g., a cell). E-UTRAN 1210 may include one or more RAN nodes for providing macrocells, e.g., macroRAN node 1560, and one or more RAN nodes for providing femtocells or picocells (e.g., cells with smaller coverage area, smaller user capacity, or higher bandwidth compared to macrocells), e.g., low-power (LP)RAN node 1572.

[0211] Either RAN node 1560 or 1572 may terminate the air interface protocol and serve as the first point of contact for UEs 1510 and 1522. In some embodiments, either RAN node 1560 or 1572 may perform various logical functions for E-UTRAN 1210. These include, but are not limited to, radio network controller (RNC) functions such as radio bearer management, dynamic uplink and downlink radio resource management and data packet scheduling, and mobility management.

[0212] According to several embodiments, UEs 1510 and 1522 may be configured to communicate with each other or with either RAN node 1560 or 1572 over multi-carrier communication channels using orthogonal frequency division multiplexing (OFDM) communication signals, according to various communication technologies, including, but not limited to, orthogonal frequency division multiplexing (OFDMA) communication technology (for example, for downlink communication) or single-carrier frequency division multiplexing (SC-FDMA) communication technology (for example, for uplink and ProSe or sidelink communication). However, the scope of embodiments is not limited in this respect.

[0213] In some embodiments, a downlink resource grid may be used for downlink transmissions from either RAN node 1560 or 1572 to UE 1510 or 1522. Uplink transmissions, on the other hand, can utilize similar techniques. The grid may be a time-frequency grid, also called a resource grid or time-frequency resource grid. It represents the physical resources in the downlink at each slot. Such a time-frequency plane representation is a common practice for OFDM systems and makes radio resource allocation intuitive. Each column and row of the resource grid corresponds to one OFDM symbol and one OFDM subcarrier, respectively. The duration of the resource grid in the time domain corresponds to one slot in the radio frame. The smallest time-frequency unit in the resource grid is represented as a resource element. Each resource grid contains several resource blocks, which describe a mapping of a given physical channel to a resource element. Each resource block contains a collection of resource elements. In other words, in the frequency domain, it can represent the minimum amount of resources that can currently be allocated. There are several different physical downlink (DL) channels that are carried using such resource blocks.

[0214] The Physical Downlink Shared Channel (PDSCH) can carry user data and upper-layer signaling to UEs 1510 and 1522. The Physical Downlink Control Channel (PDCCH) can carry, among other things, information regarding transport formats and resource allocation related to the PDSCH channel. It can also notify UEs 1510 and 1522 about transport formats, resource allocation, and HARQ (Hybrid Auto Retransmission Request) information related to the Uplink Shared Channel. Typically, downlink scheduling (allocating control and shared channel resource blocks to UE 102 in a cell) can be performed at either RAN node 1560 or 1572 based on channel quality information fed back from either UE 1510 or 1522. Downlink resource allocation information can be transmitted over the PDCCH used for (e.g., assigned to) each of UEs 1510 and 1522.

[0215] A PDCCH may use Control Channel Elements (CCEs) to transmit control information. Before being mapped to resource elements, the PDCCH complex-valued symbol can first be organized into a quadruplet. It can then be sorted using a subblock interleaver for rate matching. Each PDCCH may be transmitted using one or more of these CCEs, where each CCE may correspond to a set of nine relating to four physical resource elements known as a Resource Element Group (REG). Four orthogonal Phase Shift Keying (QPSK) symbols may be mapped to each REG. Depending on the size of the downlink control information (DCI) and the channel state, a PDCCH may be transmitted using one or more CCEs. There may be four or more different PDCCH formats defined in LTE using different numbers of CCEs (e.g., aggregation level, L=1, 2, 4, or 8).

[0216] Some embodiments may use a concept for resource allocation for control channel information, which is an extension of the concept described above. For example, some embodiments may utilize an Extended Physical Downlink Control Channel (EPDCCH) that uses PDSCH resources for transmitting control information. An EPDCCH may transmit using one or more Extended Control Channel Elements (ECCEs). As above, each ECCE may correspond to a set of nine relating to four physical resource elements known as Extended Resource Element Groups (EREGs). An ECCE may have a different number of EREGs in some situations.

[0217] RAN nodes 1560 and 1572 can communicate with each other and / or with other access nodes within E-UTRAN 1210 and / or other RANs via the X2 interface, which is a signaling interface for communicating data packets between ANs. Some other suitable interface may be used for direct communication of data packets between ANs.

[0218] The E-UTRAN 1210 is shown to be communicably coupled to the core network, in this embodiment, the Evolutionary Packet Core (EPC) network 1220, via the SI interface 1570. In this embodiment, the SI interface 1570 is divided into two parts: the SI-U interface 1214, which carries traffic data between the RAN nodes 1560 and 1572 and the Serving Gateway (S-GW) 1222, and the SI-Mobility Management Entity (MME) interface, which is a signaling interface between the RAN nodes 1560 and 1572 and the MME 1546.

[0219] In this embodiment, the EPC network 1220 comprises an MME 1546, an S-GW 1222, a Packet Data Network (PDN) gateway (P-GW) 1223, and a Home Subscriber Server (HSS) 1224. The MME 1546 may have similar control plane and functionality to a legacy Serving General-Purpose Packet Radio Service (GPRS) Support Node (SGSN). The MME 1546 may manage mobility aspects in access, such as gateway selection and tracking area list management. The HSS 1224 may have a database for network users containing subscription-related information to support the processing of communication sessions of network entities. Depending on the number of mobile subscribers, equipment capacity, network configuration, etc., the EPC network 1220 may have one or more HSSs 1224. For example, the HSS 1224 may provide support for routing / roaming, authentication, authorization, naming / addressing resolution, location dependency, etc.

[0220] S-GW 1222 may terminate the SI interface 1570 toward E-UTRAN 1210 and route data packets between E-UTRAN 1210 and the EPC network 1220. In addition, S-GW 1222 may be a local mobility anchor point for handover between RAN nodes and may also provide an anchor for inter-3GPP mobility. Other responsibilities may include lawful interception, billing, and any policy enforcement.

[0221] The P-GW 1223 may terminate the SGi interface toward the PDN. The P-GW 1223 may route data packets between the EPC network 1220 and external networks, such as the network containing the application server 1230 (alternatively referred to as the Application Function (AF)), via the Internet Protocol (IP) interface 1225. Generally, the application server 1230 may be an element providing applications that use IP bearer resources together with the core network (e.g., UMTS Packet Service (PS) domain, LTE PS data service, etc.). In this embodiment, the P-GW 1223 is shown to be communicatively coupled to the application server 1230 via the IP interface 1225. The application server 1230 may also be configured to support one or more communication services for UEs 1510 and 1522 via the EPC network 1220 (e.g., Voice over Internet Protocol (VoIP) sessions, PTT sessions, group communication sessions, social networking services, etc.).

[0222] P-GW 1223 may also be a node for policy enforcement and billing data collection. The Policy and Charging Enforcement Function (PCRF) 1226 is the policy and billing control element of the EPC network 1220. In a non-roaming scenario, a single PCRF may exist in the Home Public Land Mobile Network (HPLMN) associated with the UE's Internet Protocol Connected Access Network (IP-CAN) session. In a roaming scenario with local traffic breakout, two PCRFs may exist associated with the UE's IP-CAN session: a Home PCRF (H-PCRF) in the HPLMN and a Destination PCRF (V-PCRF) in the Destination Public Land Mobile Network (VPLMN). PCRF 1226 may be communicably coupled to the application server 1230 via P-GW 1223. Application server 1230 may signal PCRF 1226 to indicate a new service flow and select appropriate Quality of Service (QoS) and billing parameters. PCRF 1226 may provide this rule to the Policy and Billing Enforcement Function (PCEF) (not shown) using the appropriate Traffic Flow Template (TFT) and QoS Class Identifier (QCI). It then initiates QoS and billing as specified by application server 1230.

[0223] Figure 13 shows exemplary components relating to device 1300 according to several embodiments, such as base stations and UEs described in relation to Figures 1-12. In some embodiments, device 1300 may include, at least as shown, interconnected application circuitry 1302, baseband circuitry 1304, radio frequency (RF) circuitry 1306, front-end module (FEM) circuitry 1308, one or more antennas 1310, and power management circuitry (PMC) 1312. The illustrated components of device 1300 may be included in a UE or RAN node, such as a base station or gNB. In some embodiments, device 1300 may include fewer elements (for example, a RAN node may not utilize application circuitry 1302, but instead include a processor / controller for processing IP data received from an EPC). In some embodiments, device 1300 may include additional elements, such as memory / storage, displays, cameras, sensors, or input / output (I / O) interfaces. In other embodiments, the components described below may be contained in two or more devices (for example, the circuit may be contained separately in two or more devices for a cloud RAN (C-RAN) implementation).

[0224] The application circuit 1302 may include one or more application processors. For example, the application circuit 1302 may include, but is not limited to, one or more single-core or multi-core processors. The processors may include any combination of general-purpose processors and dedicated processors (e.g., graphics processors, application processors, etc.). The processors may be coupled with or include memory / storage. They may be configured to execute instructions stored in memory / storage to enable various applications or operating systems to run on device 1300. In some embodiments, the processors of the application circuit 1302 may process IP data packets received from the EPC.

[0225] The baseband circuit 1304 may include, but is not limited to, one or more single-core or multi-core processors. The baseband circuit 1304 may include one or more baseband processors or control logic for processing baseband signals received from the receiving signal path of the RF circuit 1306 and for generating baseband signals for the transmitting signal path of the RF circuit 1306. The baseband circuit 1304 may interface with the application circuit 1302 for generating and processing baseband signals and for controlling the operation of the RF circuit 1306. For example, in some embodiments, the baseband circuit 1304 may include a third-generation (3G) baseband processor 1304A, a fourth-generation (4G) baseband processor 1304B, a fifth-generation (5G) baseband processor 1304C, or other baseband processors 1304D for other existing generations, generations under development, or generations to be developed in the future (e.g., second-generation (2G), sixth-generation (6G), etc.). In many embodiments, the fourth-generation (4G) baseband processor 1304B may include the capability for generating and processing baseband signals for LTE radios. The fifth-generation (5G) baseband processor 1304C may include the capability for generating and processing baseband signals for NR.

[0226] The baseband circuit 1304 (for example, one or more of the baseband processors 1304 AD) may handle various radio control functions that enable communication with one or more radio networks via the RF circuit 1306. In other embodiments, some or all of the functions of the baseband processors 1304 AD may be contained in modules stored in memory 1304G and executed via the central processing unit (CPU) 1304E. Radio control functions may include, but are not limited to, signal modulation / demodulation, encoding / decoding, radio frequency shifting, etc.

[0227] In some embodiments, the modulation / demodulation circuit of the baseband circuit 1304 may include fast Fourier transform (FFT), precoding, or constellation mapping / demapping functions. In some embodiments, the encoding / decoding circuit of the baseband circuit 1304 may include convolution, tail-biting convolution, turbo, Viterbi, or low-density parity check (LDPC) encoder / decoder functions. Embodiments of the modulation / demodulation and encoder / decoder functions are not limited to these examples, and other embodiments may include other suitable functions.

[0228] In some embodiments, the baseband circuit 1304 may include one or more audio digital signal processors (DSPs) 1304F. The audio DSPs 1304F may include elements for compression / decompression and echo cancellation. In other embodiments, they may include other appropriate processing elements. The components of the baseband circuit may be appropriately combined on a single chip, a single chipset, or, in some embodiments, on the same circuit board. In some embodiments, some or all of the components of the baseband circuit 1304 and the application circuit 1302 may be implemented together, for example, on a system-on-a-chip (SOC). In some embodiments, the baseband circuit 1304 may provide communication compatible with one or more wireless technologies. For example, in some embodiments, the baseband circuit 1304 may support communication with an Evolved Universal Terrestrial Radio Access Network (E-UTRAN) or other Radio Metropolitan Area Networks (WMAN), Radio Local Area Networks (WLAN), or Radio Personal Area Networks (WPAN). Embodiments in which the baseband circuit 1304 is configured to support wireless communication of two or more radio protocols may be referred to as a multimode baseband circuit.

[0229] The RF circuit 1306 may enable communication with a wireless network using electromagnetic radiation modulated through a non-solid medium. In various embodiments, the RF circuit 1306 may include switches, filters, amplifiers, etc., to facilitate communication with the wireless network. The RF circuit 1306 may include a received signal path that may include a circuit for down-converting the RF signal received from the FEM circuit 1308 and providing the baseband signal to the baseband circuit 1304. The RF circuit 1306 may also include a transmitted signal path that may include a circuit for up-converting the baseband signal provided by the baseband circuit 1304 and providing the RF output signal to the FEM circuit 1308 for transmission.

[0230] In some embodiments, the receive signal path of the RF circuit 1306 may include a mixer circuit 1306a, an amplifier circuit 1306b, and a filter circuit 1306c. In some embodiments, the transmit signal path of the RF circuit 1306 may include a filter circuit 1306c and a mixer circuit 1306a. The RF circuit 1306 may also include a synthesizer circuit 1306d for combining frequencies or component carriers for use by the mixer circuit 1306a in the receive and transmit signal paths. In some embodiments, the mixer circuit 1306a in the receive signal path may down-convert the RF signal received from the FEM circuit 1308 based on the combined frequency provided by the synthesizer circuit 1306d. The amplifier circuit 1306b may amplify the down-converted signal. The filter circuit 1306c may be a low-pass filter (LPF) or a band-pass filter (BPF) for removing unwanted signals from the down-converted signal in order to generate an output baseband signal. The output baseband signal may be provided to the baseband circuit 1304 for further processing.

[0231] In some embodiments, the output baseband signal may be a zero-frequency baseband signal; however, this is not a requirement. In some embodiments, the mixer circuit 1306a in the received signal path may comprise a passive mixer; however, the scope of embodiments is not limited in this respect.

[0232] In some embodiments, the mixer circuit 1306a of the transmit signal path may be configured to upconvert the input baseband signal based on the combined frequency provided by the combiner circuit 1306d to generate an RF output signal for the FEM circuit 1308. The baseband signal is provided by the baseband circuit 1304 and may be filtered by the filter circuit 1306c.

[0233] In some embodiments, the receive signal path mixer circuit 1306a and the transmit signal path mixer circuit 1306a may include two or more mixers, each configured for quadrature down-conversion and up-conversion. In some embodiments, the receive signal path mixer circuit 1306a and the transmit signal path mixer circuit 1306a may include two or more mixers, each configured for image rejection (e.g., Hartley image rejection). In some embodiments, the receive signal path mixer circuit 1306a and the transmit signal path mixer circuit 1306a may be configured for direct down-conversion and direct up-conversion. In some embodiments, the receive signal path mixer circuit 1306a and the transmit signal path mixer circuit 1306a may be configured for superheterodyne operation.

[0234] In some embodiments, the output baseband signal and input baseband signal may be analog baseband signals. However, the scope of embodiments is not limited in this respect. In some alternative embodiments, the output baseband signal and input baseband signal may be digital baseband signals. In these alternative embodiments, the RF circuit 1306 may include an analog-to-digital converter (ADC) and a digital-to-analog converter (DAC) circuit, and the baseband circuit 1304 may include a digital baseband interface for communicating with the RF circuit 1306.

[0235] In some dual-mode embodiments, separate wireless IC circuits may be provided to process signals for each spectrum. However, the scope of embodiments is not limited in this respect.

[0236] In some embodiments, the synthesizer circuit 1306d may be a fractional N synthesizer or a fractional NIN+I synthesizer. However, the scope of embodiments is not limited in this respect, as other types of frequency synthesizers may be suitable. For example, the synthesizer circuit 1306d may be a synthesizer having a delta-sigma synthesizer, a frequency multiplier, or a phase-locked loop having a frequency divider.

[0237] The synthesizer circuit 1306d can synthesize output frequencies for use by the mixer circuit 1306a of the RF circuit 1306 based on the frequency input and the frequency divider control input. In some embodiments, the synthesizer circuit 1306d may be a fractional NIN+I synthesizer.

[0238] In some embodiments, the frequency input may be the output of a voltage-controlled oscillator (VCO), although this is not a requirement. The divider control input may be the output of either the baseband circuit 1304 or the application processor of the application circuit 1302, depending on the desired output frequency. In some embodiments, the divider control input (e.g., N) may be determined from a lookup table based on the channel indicated by the application circuit 1302.

[0239] The combiner circuit 1306d of the RF circuit 1306 may include a frequency divider, a delay-locked loop (DLL), a multiplexer, and a phase accumulator. In some embodiments, the frequency divider may be a dual-modulus frequency divider (DMD), and the phase accumulator may be a digital phase accumulator (DPA). In some embodiments, the DMD may be configured to divide the input signal by either N or N+1 (e.g., based on carry-out) to provide a fractional division ratio. In some exemplary embodiments, the DLL may include a cascaded, adjustable set of delay elements, a phase detector, a charge pump, and a D-type flip-flop. In these embodiments, the delay elements may divide the VCO period into Nd equal-phase packets, where Nd is the number of delay elements in the delay line. In this way, the DLL provides negative feedback to help ensure that the total delay through the delay line is 1 VCO cycle.

[0240] In some embodiments, the combiner circuit 1306d may generate the carrier frequency (or component carrier) as the output frequency. On the other hand, in other embodiments, the output frequency is a multiple of the carrier frequency (e.g., twice the carrier frequency, four times the carrier frequency), and may be used in conjunction with quadrature generator and divider circuits to generate multiple signals at carrier frequencies with multiple different phases relative to each other. In some embodiments, the output frequency may be the local oscillator (LO) frequency (fLO). In some embodiments, the RF circuit 1306 may include an IQ / pole converter.

[0241] The FEM circuit 1308 may include a receive signal path. It may include a circuit that operates on RF signals received from one or more antennas 1310, amplifies the received signals, and provides the amplified version of the received signals to the RF circuit 1306 for further processing. The FEM circuit 1308 may also include a transmit signal path. It may include a circuit configured to amplify the signal for transmission provided by the RF circuit 1306 for transmission by one or more of the antennas 1310. In various embodiments, amplification through the transmit signal path or the receive signal path may occur in the RF circuit 1306 only, in the FEM circuit 1308 only, or in both the RF circuit 1306 and the FEM circuit 1308.

[0242] In some embodiments, the FEM circuit 1308 may include a TX / RX switch for switching between transmit mode operation and receive mode operation. The FEM circuit may include a receive signal path and a transmit signal path. The receive signal path of the FEM circuit may include a low-noise amplifier (LNA) for amplifying the received RF signal and providing the amplified received RF signal as an output (e.g., to the RF circuit 1306). The transmit signal path of the FEM circuit 1308 may include a power amplifier (PA) for amplifying the input RF signal (e.g., provided by the RF circuit 1306), and one or more filters for generating an RF signal for subsequent transmission (e.g., by one or more of the antennas 1310).

[0243] In this embodiment, "radio" refers to the combination of RF circuit 130 and FEM circuit 1308. Radio refers to the part of the circuit that generates, transmits, receives, and processes radio signals. RF circuit 1306 generates a time-domain radio signal having data from a baseband signal and includes a transmitter for applying the radio signal to a subcarrier of the carrier frequency that forms the bandwidth of the channel. The PA in FEM circuit 1308 amplifies the tone for transmission and amplifies the tone received from one or more antennas 1310 via LNA to increase the signal-to-noise ratio (SNR) for interpretation. In radio communication, FEM circuit 1308 may also search for detectable patterns that appear to be radio communication. Subsequently, the receiver in RF circuit 1306 converts the time-domain radio signal to a baseband signal via one or more functional modules, such as the base station 510 and the functional modules shown in user equipment 560 shown in Figure 2.

[0244] In some embodiments, the PMC 1312 can manage the power supplied to the baseband circuit 1304. In particular, the PMC 1312 can control power source selection, voltage scaling, battery charging, or DC-DC conversion. The PMC 1312 may often be included when the device 1300 can be powered by a battery, for example, when the device is contained within a UE. The PMC 1312 can increase power conversion efficiency while providing desirable mounting size and heat dissipation characteristics.

[0245] Figure 13 shows the PMC 1312 coupled only to the baseband circuit 1304. However, in other embodiments, the PMC 1312 may be coupled additionally or alternatively to other components, but not limited to, the application circuit 1302, the RF circuit 1306, or the FEM circuit 1308, and perform similar power management operations for them.

[0246] In some embodiments, the PMC 1312 controls, or may otherwise be part of, various power-saving mechanisms of device 1300. For example, when device 1300 is in the RRC_Connected state, where it expects to receive traffic immediately and is therefore still connected to the RAN node, it may enter a state known as discontinuous receive mode (DRX) after a period of inactivity. During this state, device 1300 may cut off power for short time intervals and thus conserve power.

[0247] If there is no data traffic activity during the extended time period, device 1300 may transition to an RRC idle state. In this state, device 1300 disconnects from the network and does not perform actions such as channel quality feedback, handover, etc. Device 102 enters a very low power state and performs paging. Here, it periodically wakes up to listen to the network again and then cuts off power again. Device 1300 does not need to receive data in this state. To receive data, it must transition back to an RRC connected state.

[0248] An additional power-saving mode may allow the device to be unavailable to the network for periods longer than the paging interval (ranging from a few seconds to several hours). During this time, the device may be completely unreachable to the network and may be completely powered off. Any data transmitted during this time will experience a significant delay, and this delay is assumed to be acceptable.

[0249] The processors of application circuit 1302 and baseband circuit 1304 may be used to execute elements of one or more instances of the protocol stack. For example, the processor of baseband circuit 1304 may be used alone or in combination to execute Layer 3, Layer 2, or Layer 1 functionality. Meanwhile, the processor of application circuit 1302 may utilize data received from these layers (e.g., packet data) and further execute Layer 4 functionality (e.g., Transmission Communication Protocol (TCP) and User Datagram Protocol (UDP) layers). As referred to herein, Layer 3 may comprise the Radio Resource Control (RRC) layer, which is described in more detail below. As referred to herein, Layer 2 may comprise the Medium Access Control (MAC) layer, the Radio Link Control (RLC) layer, and the Packet Data Convergence Protocol (PDCP) layer, which are described in more detail below. As referred to herein, Layer 1 may comprise the Physical (PHY) layer of the UE / RAN node, which is described in more detail below.

[0250] Figure 14 shows exemplary interfaces relating to baseband circuits according to several embodiments, such as the baseband circuits shown and / or described in relation to Figures 1-13. As described above, the baseband circuit 1304 in Figure 13 may comprise processors 1304A-1304E and memory 1304G utilized by these processors. Each of the processors 1304A-1304E may include a memory interface 1404A-1404E for sending and receiving data to and from memory 1304G.

[0251] The baseband circuit 1304 may further include one or more interfaces for communicative coupling to other circuits / devices, such as a memory interface 1412 (e.g., an interface for sending and receiving data to and from memory outside the baseband circuit 1304), an application circuit interface 1414 (e.g., an interface for sending and receiving data to and from the application circuit 1302 in Figure 13), an RF circuit interface 1416 (e.g., interfaces 525 and 575 shown in Figure 5 for communication or network communication, or other interfaces for sending and receiving data to and from the RF circuit 1306 in Figure 13), a wireless hardware connection interface 1418 (e.g., an interface for sending and receiving data to and from a Near Field Communication (NFC) component, a Bluetooth® component (e.g., Bluetooth Low Energy), a Wi-Fi component, and other communication components), and a power management interface 1420 (e.g., an interface for sending and receiving power or control signals to and from the PMC 1312).

[0252] Figure 15 is a block diagram of a component capable of reading instructions from a machine-readable or computer-readable medium (e.g., a non-temporary machine-readable storage medium) and performing any one or more of the methodologies described herein in conjunction with Figures 1-14, according to several exemplary embodiments. Specifically, Figure 15 shows a schematic diagram of a hardware resource 1500, which includes one or more processors (or processor cores) 1510, one or more memory / storage devices 1520, and one or more communication resources 1530, each of which may be communicatively coupled via a bus 1540. In embodiments where node virtualization (e.g., NFV) is utilized, the hypervisor 1502 may be executed to provide an execution environment for one or more network slices / subslice to utilize the hardware resource 1500.

[0253] Processor 1510 (for example, a central processing unit (CPU), a reduced instruction set computing (RISC) processor, a composite instruction set computing (CISC) processor, a graphics processing unit (GPU), a digital signal processor (DSP) such as a baseband processor, an application-specific integrated circuit (ASIC), a radio frequency integrated circuit (RFIC), another processor, or any suitable combination thereof), may include, for example, processors 1512 and 1514.

[0254] The memory / storage device 1520 may include main memory, disk storage, or any suitable combination thereof. The memory / storage device 1520 may include, but is not limited to, 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, or solid-state storage.

[0255] The communication resource 1530 may include interconnects, network interface components, or other suitable devices for communicating with one or more peripheral devices 1504 or one or more databases 1506 via the network 1508. For example, the communication resource 1530 may include wired communication components (e.g., for coupling via Universal Serial Bus (USB)), cellular communication components, NFC components, Bluetooth components (e.g., Bluetooth Low Energy), Wi-Fi components, and other communication components.

[0256] Instruction 1550 may comprise software, programs, applications, applets, apps, or other executable code causing at least one of the processors 1510 to execute any one or more of the methodologies discussed herein. Instruction 1550 may reside entirely or partially in at least one of the processors 1510 (e.g., in the processor's cache memory), in the memory / storage device 1520, or in any preferred combination thereof. Furthermore, any portion of instruction 1550 may be transferred to the hardware resource 1500 from any combination of peripheral devices 1504 or the database 1506. Thus, the memory of the processor 1510, the memory / storage device 1520, the peripheral device 1504, and the database 1506 are examples of computer-readable and machine-readable media.

[0257] In embodiments, one or more elements of Figures 12, 13, 14, and / or 15 may be configured to perform one or more processes, techniques, or methods, or parts thereof, as described herein.

[0258] As used herein, the term “circuitry” means, is part of, or may include, an application-specific integrated circuit (ASIC), electronic circuit, processor (shared, dedicated, or grouped), and / or memory (shared, dedicated, or grouped), combinational logic circuit, and / or other suitable hardware component that runs one or more software or firmware programs and provides the functions described.

[0259] Various examples can be implemented using hardware elements, software elements, or a combination of both. In some examples, hardware elements may include devices, components, processors, microprocessors, circuits, circuit elements (e.g., transistors, resistors, capacitors, inductors, etc.), integrated circuits, application-specific integrated circuits (ASICs), programmable logic devices (PLDs), digital signal processors (DSPs), field-programmable gate arrays (FPGAs), memory units, logic gates, registers, semiconductor devices, chips, microchips, chipsets, etc. In some examples, software elements may include software components, programs, applications, computer programs, application programs, system programs, machine programs, operating system software, middleware, firmware, software modules, routines, subroutines, functions, methods, procedures, software interfaces, application programming interfaces (APIs), instruction sets, computing code, computer code, code segments, computer code segments, words, values, symbols, or any combination thereof. Whether an embodiment is implemented using hardware and / or software elements may vary according to any number of factors, such as desired computation rate, power level, thermal tolerance, processing cycle budget, input data rate, output data rate, memory resources, data bus speed, and other design or performance constraints, as desired for a given implementation form.

[0260] Some examples may be described using the expressions “in one example” or “an example,” along with their derivatives. These terms mean that a particular feature, structure, or characteristic described in relation to an example is contained in at least one example. The phrase “in one example” appearing in various parts of this specification does not necessarily refer to the same example every time.

[0261] Some examples can be described using the expressions “coupled” and “connected” along with their derivatives. These terms are not necessarily intended to be synonyms of each other. For example, a description using the term “connected” and / or “coupled” can indicate that two or more elements are in direct physical or electrical contact with each other. However, the term “coupled” can also mean that two or more elements do not directly contact each other but still cooperate or interact with each other.

[0262] In addition, it can be seen from the foregoing detailed description that, for the purpose of rationalizing the present disclosure, various features are grouped in a single example. The method of this disclosure should not be construed as reflecting an intention that the claimed examples require more features than those explicitly recited in each claim. Rather, as reflected in the subsequent claims, the technical subject matter of the invention lies in fewer features than all the features of a single disclosed example. Accordingly, the subsequent claims are incorporated into the detailed description herein in a state where each claim is independent as a separate example. In the appended claims, the terms “including” and “in which” are used as the ordinary English equivalents of the respective terms “comprising” and “wherein”. Further, terms such as “first”, “second”, “third”, etc. are used merely as labels and are not intended to impose numerical requirements on their objects.

[0263] Although the technical matters are described in language specific to structural features and / or methodological operations, it should be understood that the technical matters defined in the appended claims are not necessarily limited to the specific features or operations described above. Rather, the specific features and operations described above are disclosed as exemplary forms of implementing the claims.

[0264] A data processing system suitable for storing and / or executing program code includes at least one processor directly or indirectly coupled to memory elements via a system bus. The memory elements can include local memory used during actual execution of the program code, a mass storage device, and a cache memory that provides temporary storage of at least some of the program code to reduce the number of times code must be retrieved from the mass storage device during execution. The term "code" covers a wide range of software components and configurations, including applications, drivers, processes, routines, methods, modules, firmware, microcode, and subprograms. Thus, the term "code" can be used to refer to any set of instructions that, when executed by a processing system, perform the desired operations.

[0265] The processing circuits, logic circuits, devices, and interfaces described herein may perform functions implemented in hardware and also using code executed on one or more processors. A processing circuit, or logic circuit, refers to hardware, or hardware and code, that implements one or more logic functions. A circuit is hardware and may refer to one or more circuits. Each circuit may perform a specific function. The circuits of this circuit may comprise individual electrical components interconnected with one or more conductors, integrated circuits, chip packages, chipsets, memory, etc. An integrated circuit may include circuits formed on a substrate such as a silicon wafer and may comprise components. And integrated circuits, processor packages, chip packages, and chipsets may comprise one or more processors.

[0266] A processor can receive signals, such as instructions and / or data, as inputs, and process those signals to produce at least one output. While executing code, the code modifies the physical state and properties of transistors that make up the processor pipeline. The physical state of a transistor is converted into logical bits of 1s and 0s stored in registers within the processor. The processor can transfer the physical state of a transistor to a register and to another storage medium.

[0267] A processor may comprise circuits or circuit configurations for performing one or more sub-functions implemented to perform the overall function of the “processor”. Note that a “processor” comprises one or more processors, and each processor may comprise one or more processor cores that process code and / or data independently or interdependently. Each of the processor cores is also a “processor” and is distinguishable from a processor only for the purpose of describing a physical arrangement or architecture relating to a processor having multiple processor cores on one or more dies and / or in one or more chip packages. Depending on the design of the processor, a processor core may comprise a general-purpose processing core or a processor core configured to perform a specific task. A processor core may be a processor having one or more processor cores. When describing functions performed by a processor, processing circuit, etc. as described herein and claimed, a processor, processing circuit, etc. may comprise one or more processors. Each processor has one or more processor cores, and any one or more of the processors and / or processor cores may reside on one or more dies in one or more chip packages. And it may be able to perform some or all of the processes required to execute the function.

[0268] One example of a processor is a state machine or application-specific integrated circuit (ASIC) having at least one input and at least one output. A state machine may manipulate at least one input to produce at least one output by performing a predetermined series of serial and / or parallel operations or transformations on at least one input.

[0269] Some advantageous effects of the embodiment While not an exhaustive list, several embodiments have one or more potential advantages. An extension to favorably perform positioning frequency hops for positioning measurements, where all positioning frequency layers are measured or associated with only one measurement gap per UE, or where all positioning frequency layers within the same FR are measured or associated with only one measurement gap per FR within the corresponding FR. For example, a UE may be configured with one measurement gap for positioning measurements for a per-UE measurement gap configuration. Alternatively, a UE may be configured with one measurement gap for FR1 positioning measurements, one measurement gap for FR2 positioning measurements, or one measurement gap for FR1 positioning measurements and one measurement gap for FR2 positioning measurements for a per-FR measurement gap configuration. The extension favorably maintains active connectivity with base stations for data UL and DL. The extension favorably reduces the complexity of RedCap UE measurements. The extension favorably facilitates measurements of PRS bandwidths larger than the UE's bandwidth capability.

[0270] Examples of further embodiments The following examples relate to further embodiments. Details in the examples may be used in any of one or more embodiments.

[0271] Example 1 is a device relating to a user device (UE) for receiving a positioning reference signal (PRS) using frequency hops, comprising an interface for communication and a memory coupled to the interface, configured to perform a measurement of the PRS within at least one measurement delay, by determining the number of frequency hops between positioning frequency layers associated with the frequency range of the PRS, based on a measurement gap configuration per UE, during one measurement gap iteration, or based on a measurement gap configuration per frequency range (FR), during up to two measurement gap iterations, by performing a number of frequency hops and measurements of the PRS between each of one measurement gap or up to two measurement gap iterations, and by causing the transmission of at least one positioning measurement report via the interface. In Example 2, the device of Example 1 further comprises a processing circuit comprising a processor and memory coupled to the processor, a radio frequency circuit coupled to the processing circuit, and one or more antennas coupled to the radio frequency circuit. In Example 3, the device in Example 1 has each frequency layer associated with the number of frequency hops during one measurement gap or up to two measurement gap iterations, associated with a bandwidth portion of the PRS. In Example 4, the device in Example 1 has timing between multiple frequency hops based on the accuracy of the positioning measurement defined for each measurement type in the positioning measurement configuration, which includes reference signal time difference (RSTD) measurement, positioning reference signal-received reference signal power (PRS-RSRP) measurement, UE Rx-TX time difference measurement, and positioning reference signal-received signal power (PRS-RSRPP) measurement. In Example 5, the device in Example 4 has the positioning measurement configuration configured via the base station through the core network's location management function, and the positioning measurement configuration resides in memory. In Example 6, the device in Example 4 has at least one measurement delay defined for each measurement type, which includes up to four iterations of one measurement gap or up to two measurement gaps, and the processing circuit triggers the transmission of at least one positioning measurement report for each of the corresponding measurement delays for each measurement type.In Example 7, in any of the devices in Examples 1-6, all positioning frequency layers are either measured or associated with only one measurement gap per UE. In Example 8, in any of the devices in Examples 1-6, all positioning frequency layers within the same FR are either measured or associated with only one measurement gap per FR within the corresponding FR.

[0272] Example 9 relates to a user device (UE) for receiving a positioning reference signal (PRS) using frequency hops, the method comprising the steps of determining the frequency range of the PRS based on a PRS configuration, the PRS configuration being a resource block of positioning frequency layers for the PRS, the number of frequency hops between positioning frequency layers associated with the frequency range of the PRS during iterations of one measurement gap based on a measurement gap configuration per UE or up to two measurement gaps based on a measurement gap configuration per frequency range (FR) to perform PRS measurements within at least one measurement delay, the steps of performing the PRS frequency hops and number of measurements between each iteration of one measurement gap or up to two measurement gaps, and the steps of causing the transmission of at least one positioning measurement report via an interface. In Example 10, in the method of Example 9, each of the frequency layers associated with the number of frequency hops between iterations of one measurement gap or up to two measurement gaps is associated with a bandwidth portion of the PRS. In Example 11, in the method of Example 9, the timing between multiple frequency hops is based on the accuracy of the positioning measurement defined for each measurement type in the positioning measurement configuration, and the measurement types include reference signal time difference (RSTD) measurement, positioning reference signal-received reference signal power (PRS-RSRP) measurement, UE Rx-TX time difference measurement, and positioning reference signal-received signal power (PRS-RSRPP) measurement. In Example 12, in any method of Examples 9-11, all positioning frequency layers are measured in or associated with only one per-UE measurement gap. In Example 13, in any method of Examples 9-11, all positioning frequency layers within the same FR are measured in or associated with only one per-FR measurement gap within the corresponding FR.

[0273] Example 14 is a machine-readable medium containing instructions that cause the processor to perform an operation when executed by the processor of a user device (UE) for receiving a positioning reference signal (PRS) with frequency hops, the operation being to perform the following steps: determine the frequency range of the PRS based on the PRS configuration, the PRS configuration being a resource block of positioning frequency layers of the PRS; determine the number of frequency hops between positioning frequency layers associated with the frequency range of the PRS during one measurement gap iteration based on a measurement gap configuration per UE, or during up to two measurement gap iterations based on a measurement gap configuration per frequency range (FR), and perform a measurement of the PRS within at least one measurement delay; perform the number of frequency hops and the measurement of the PRS between each of one measurement gap iteration or up to two measurement gap iterations; and cause the transmission of at least one positioning measurement report via an interface. In Example 15, in the machine-readable medium of Example 14, each of the frequency layers associated with the number of frequency hops between one measurement gap iteration or up to two measurement gap iterations is associated with a bandwidth portion of the PRS. In Example 16, in the machine-readable medium of Example 14, the timing between multiple frequency hops is based on the accuracy of the positioning measurement defined for each measurement type in the positioning measurement configuration, the measurement types include reference signal time difference (RSTD) measurement, positioning reference signal-reference signal received power (PRS-RSRP) measurement, UE Rx-TX time difference measurement, and positioning reference signal-received signal received path power (PRS-RSRPP) measurement. In Example 17, in the machine-readable medium of Example 16, the UE is configured with a positioning measurement configuration via a base station by the location management function of the core network, and the positioning measurement configuration resides in memory. In Example 18, in the machine-readable medium of Example 16, at least one measurement delay is defined for each measurement type, having one measurement gap or at most two measurement gaps with a maximum of four iterations, and the processor triggers the transmission of at least one positioning measurement report for each within the corresponding measurement delay for each measurement type.In Example 19, in any machine-readable medium from Examples 14-18, all positioning frequency layers are measured or associated with only one measurement gap per UE. In Example 20, in any machine-readable medium from Examples 14-18, all positioning frequency layers within the same FR are measured or associated with only one measurement gap per FR within the corresponding FR.

[0274] Example 21 is a method that includes any of the actions described in any one of Examples 1-20.

[0275] Example 22 is an apparatus comprising means for any method of Example 21.

[0276] Example 23 is a system that includes means for any method of Example 21, such as the system described in Example 2 and the system described in Example 15.

[0277] Example 24 is a machine-readable medium containing instructions that, when executed by a processor, cause the processor to perform an action including any of the methods in Example 21.

Claims

1. A device relating to a user equipment (UE) for receiving a positioning reference signal (PRS) using frequency hopping, Interfaces for communication, A processing circuit coupled to the memory and the interface, Based on the PRS configuration, the frequency range of the PRS is determined, and the PRS configuration defines the resource blocks of the PRS positioning frequency layer. During one measurement gap iteration based on the measurement gap configuration per UE, or during up to two measurement gap iterations based on the measurement gap configuration per frequency range (FR), a number of frequency hops are determined between the positioning frequency layers associated with the frequency range of the PRS, and the PRS measurement is performed within at least one measurement delay. During the iteration of one measurement gap, or during the iteration of up to two measurement gaps, the multiple frequency hops and the PRS measurements are performed, and To transmit at least one positioning measurement report via the interface, A processing circuit that performs the operation in this manner, A device equipped with the following features.

2. The processing circuit comprises a processor and the memory coupled to the processor. The aforementioned device further, The processing circuit comprises a radio frequency circuit coupled to the processing circuit, and one or more antennas coupled to the radio frequency circuit. The apparatus according to claim 1.

3. Each of the positioning frequency layers associated with the number of frequency hops during one measurement gap or the iteration of up to two measurement gaps is associated with a bandwidth portion of the PRS. The apparatus according to claim 1.

4. The timing between the aforementioned number of frequency hops is based on the accuracy of the positioning measurement defined for each measurement type in the positioning measurement configuration. The measurement types include reference signal time difference (RSTD) measurement, positioning reference signal-received reference signal power (PRS-RSRP) measurement, UE Rx-TX time difference measurement, and positioning reference signal-received signal power (PRS-RSRPP) measurement. The apparatus according to claim 1.

5. The aforementioned UE is configured using a positioning measurement configuration via a base station through the location management function of the core network, and The positioning measurement configuration is located in the memory. The apparatus according to claim 4.

6. The at least one measurement delay is defined for each measurement type and includes up to four iterations relating to one measurement gap or up to two measurement gaps. The processing circuit causes each of the at least one positioning measurement report to be transmitted within a measurement delay corresponding to each measurement type. The apparatus according to claim 4.

7. All positioning frequency layers are measured using or associated with only one measurement gap per UE. The apparatus according to any one of claims 1 to 6.

8. All positioning frequency layers within the same FR are measured using, or associated with, just one measurement gap per FR within the corresponding FR. The apparatus according to any one of claims 1 to 6.

9. A method relating to a user device (UE) for receiving a positioning reference signal (PRS) using frequency hopping, This is a step in determining the frequency range of the PRS based on the PRS configuration. The PRS configuration defines a resource block for the PRS positioning frequency layer, and The step of determining a number of frequency hops between the positioning frequency layers associated with the frequency range of the PRS during one measurement gap iteration based on the measurement gap configuration for each UE, or during up to two measurement gap iterations based on the measurement gap configuration for each frequency range (FR), Perform the measurement of the PRS within at least one measurement delay. Steps and The steps include performing the measurement of the numerous frequency hops and the PRS during the repetition of one measurement gap or the repetition of up to two measurement gaps, The steps include: transmitting at least one positioning measurement report via the interface; Methods that include...

10. Each of the positioning frequency layers associated with the number of frequency hops during one measurement gap or the iteration of up to two measurement gaps is associated with a bandwidth portion of the PRS. The method according to claim 9.

11. The timing between the aforementioned number of frequency hops is based on the accuracy of the positioning measurement defined for each measurement type in the positioning measurement configuration. The measurement types include reference signal time difference (RSTD) measurement, positioning reference signal-received reference signal power (PRS-RSRP) measurement, UE Rx-TX time difference measurement, and positioning reference signal-received signal power (PRS-RSRPP) measurement. The method according to claim 9.

12. All positioning frequency layers are measured using or associated with only one measurement gap per UE. The method according to any one of claims 9 to 11.

13. All positioning frequency layers within the same FR are measured using, or associated with, just one measurement gap per FR within the corresponding FR. The method according to any one of claims 9 to 11. The apparatus according to any one of claims 1 to 6.

14. A computer program comprising multiple instructions, wherein when the instructions are executed, the processor of the user device (UE) is instructed to perform an operation for receiving a positioning reference signal (PRS) using frequency hopping, and the operation is: This is a step in determining the frequency range of the PRS based on the PRS configuration. The PRS configuration defines a resource block for the PRS positioning frequency layer, and The step of determining a number of frequency hops between the positioning frequency layers associated with the frequency range of the PRS during one measurement gap iteration based on the measurement gap configuration for each UE, or during up to two measurement gap iterations based on the measurement gap configuration for each frequency range (FR), Perform the measurement of the PRS within at least one measurement delay. Steps and The steps include performing the measurement of the numerous frequency hops and the PRS during the repetition of one measurement gap or the repetition of up to two measurement gaps, The steps include: transmitting at least one positioning measurement report via the interface; A computer program that includes [this].

15. Each of the positioning frequency layers associated with the number of frequency hops during one measurement gap or the iteration of up to two measurement gaps is associated with a bandwidth portion of the PRS. The computer program according to claim 14.

16. The timing between the aforementioned number of frequency hops is based on the accuracy of the positioning measurement defined for each measurement type in the positioning measurement configuration. The measurement types include reference signal time difference (RSTD) measurement, positioning reference signal-received reference signal power (PRS-RSRP) measurement, UE Rx-TX time difference measurement, and positioning reference signal-received signal power (PRS-RSRPP) measurement. The computer program according to claim 14.

17. The aforementioned UE is configured using a positioning measurement configuration via a base station through the location management function of the core network, and The aforementioned positioning measurement configuration resides in memory. The computer program according to claim 16.

18. The at least one measurement delay is defined for each measurement type and includes up to four iterations relating to one measurement gap or up to two measurement gaps. The processor causes each of the at least one positioning measurement report to be transmitted within a measurement delay corresponding to each measurement type. The computer program according to claim 16.

19. All positioning frequency layers are measured using or associated with only one measurement gap per UE. A computer program according to any one of claims 14 to 18.

20. All positioning frequency layers within the same FR are measured using, or associated with, just one measurement gap per FR within the corresponding FR. A computer program according to any one of claims 14 to 18.

Images