Enhancements for measurement reporting in non-terrestrial networks

Abstract

The method by the wireless device includes determining whether one or more conditions for triggering measurements occur and performing one or more measurements based on the occurrence of the one or more conditions, wherein the one or more conditions for triggering measurements are based on at least one of a timing advance value in a source cell, a distance between the wireless device and a satellite node serving the source cell or a candidate target cell, a predicted time that the wireless device will be served in the source cell and / or the candidate target cell, an elevation angle of the satellite node serving the source cell and / or the candidate target cell, reaching a time point set by a network node, detection of an identifier associated with a particular cell, and a speed or velocity of the wireless device.

Description

[Technical field]

[0001] The present disclosure relates generally to wireless communications, and more particularly to a system and method that provides enhancements for measurement reporting in non-terrestrial networks (NTNs). [Background technology]

[0002] The Third Generation Partnership Project (3GPP) Release 8 specifies the Evolved Packet System (EPS). EPS is based on the Long-Term Evolution (LTE) radio network and the Evolved Packet Core (EPC). It was originally intended to provide voice and wireless broadband (MBB) services, but has evolved continuously to expand its capabilities. Starting with Release 13, Narrowband Internet of Things (NB-IoT) and LTE for Machines (LTE-M) are part of the LTE specification, providing connectivity to massive machine-based communication (mMTC) services.

[0003] 3GPP Release 15 specifies the first release of the 5G system (5GS). This new generation radio access technology is intended to serve use cases such as enhanced Mobile Broadband (eMBB), ultra-reliable and low latency communications (URLLC), and mMTC. The 5G specifications include the New Radio (NR) access layer interface and the 5G Core Network (5GC). The NR physical and higher layers reuse parts of the LTE specifications and add components as required for new use cases.

[0004] In Release 15, 3GPP also started work to prepare NR for operation in non-terrestrial networks (NTN). The work was carried out within the study item "NR for supporting non-terrestrial networks" and resulted in 3GPP Technical Report (TR) 38.811. In Release 16, the work to prepare NR for operation in NTN networks continues in the study item "Solutions for NR to support non-terrestrial networks". In parallel, there is growing interest in adapting LTE for operation in NTN. As a result, 3GPP is considering introducing support for NTN in both LTE and NR in Release 17.

[0005] Typically, a satellite radio access network includes the following components: Satellite: A space-borne platform. Earth-Based Gateway: Connects satellites to base stations or core networks, depending on the choice of architecture. Feeder Link: The link between the Gateway and the Satellite. Access Link: The link between the satellite and the User Equipment (UE).

[0006] Depending on the orbital altitude, satellites may be categorized as Low Earth Orbit (LEO), Medium Earth Orbit (MEO), or Geostationary Orbit (GEO) satellites. LEO: Typical altitudes range from 250 to 1,500 km, and orbital periods range from 90 to 120 minutes. MEO: Typical altitudes range from 5,000 to 25,000 km, and orbital periods range from 3 to 15 hours. GEO: Altitude approximately 35,786 km, orbital period 24 hours.

[0007] Satellite systems tend to have significantly higher path loss than terrestrial networks due to their significant orbital height. Overcoming path loss often requires that the access and feeder links operate in line-of-sight conditions and that the UE be equipped with antennas that provide high beam directionality.

[0008] A communication satellite typically generates several beams over a given area. The beam's "footprint" or "spot beam" is usually elliptical in shape and has traditionally been considered a cell. The beam's footprint may move across the Earth's surface with the satellite moving (often called moving beam or moving cell case). Or the spot beam may be Earth-fixed with some beam-pointing mechanism used by the satellite to compensate for its movement (often called Earth-fixed beam or Earth-fixed cell case). The size of the spot beam depends on the system design and can range from tens of kilometers to thousands of kilometers. Figure 1 shows an example architecture of a satellite network with bent pipe transponders.

[0009] Compared to beams observed in terrestrial networks, NTN beams may be extremely wide and may cover areas outside of the area defined by the served cell. Beams covering adjacent cells overlap, causing significant levels of inter-cell interference. A typical approach to overcome the large levels of interference in NTNs involves configuring different cells with different carrier frequencies and polarization modes.

[0010] In a LEO NTN, satellites are moving at extremely high speeds. This leads to a Doppler shift of the carrier frequency on the service link of up to 24 ppm for a LEO satellite at 600 km altitude. See TR 38.821, Solutions for NR Support of Non-Terrestrial Networks. The Doppler shift is also time-varying due to satellite movements across the sky. The Doppler shift can vary by up to 0.27 ppm / s for a LEO 600 km satellite. The Doppler shift affects the received frequency on the service link compared to the transmitted frequency, i.e. increases or decreases it. In a GEO NTN, satellites may move in orbits inclined to the equatorial plane. The inclination introduces a satellite-relative Earth periodic movement that introduces a predictable and daily periodically repeating Doppler shift of the carrier frequency, as exemplified in the figure below. Figure 2 shows an example of a diurnal Doppler shift of the forward service link observed for a GEO satellite operating from an inclined orbit.

[0011] In 3GPP TR 38.821, it was addressed that ephemeris data should be provided to the UE, for example to help it point a directional antenna (or antenna beam) towards a satellite. See RP-181370, Study on Evaluation of Solutions for NR Support of Non-Terrestrial Networks. For example, a UE that knows its own position, such as thanks to Global Navigation Satellite System (GNSS) support, may also use the ephemeris data to calculate the correct Timing Advance (TA) and Doppler Shift. The details on how to provide and update the ephemeris have not yet been studied in detail.

[0012] A satellite orbit can be fully described using six parameters. The user can choose exactly which set of parameters to use, and many different implementations are possible. For example, a set of parameters (α, ε, i, Ω, ω, t) is often used in astronomy, where the semi-major axis "α" and eccentricity "ε" indicate the shape and size of the orbital ellipse, the inclination "i", the ascending node "Ω", and the declination of the periapsis "ω" determine the position in space, and the epoch "t" determines the reference time (e.g., the time when the satellite moves through the periapsis). This set of parameters is illustrated in FIG. 3, where the periapsis refers to the point where the trajectory is closest to the Earth, the first point of Aries refers to the direction towards the Sun at the vernal equinox, and the ascending node refers to the point where the trajectory passes upward through the equatorial plane.

[0013] Two Line Element Set (TLE) is a data format that encodes a list of orbital elements of an Earth orbiting object for a given time, epoch. As an example of a different parametrization, Two Line Element Set (TLE) uses mean motion "n" and mean anomaly (M) instead of a and t. An entirely different set of parameters is the satellite position and velocity vector (x, y, z, v x , v y , y z ) These are sometimes called orbit state vectors. They are derived from the orbit elements, and vice versa, since the information they contain is equivalent. These formulas (and many others) are possible choices for the format of ephemeris data used in the NTN.

[0014] It is important that the UE is able to determine the satellite position with an accuracy of at least a few meters. See RP-181370, Study on Evaluation of Solutions for NR Support of Non-Terrestrial Networks. However, some studies have shown that this may be difficult to achieve when using the de facto standard of TLE. On the other hand, LEO satellites often have GNSS receivers and can determine their position with a few meter-level accuracy.

[0015] Another aspect discussed in the study section and taken up in 3GPP TR 38.821 is the validity time of the ephemeris data. Predictions of satellite positions generally deteriorate with the age of the ephemeris data used due to atmospheric drag, satellite maneuvers, imperfections in the orbit model used, etc. Therefore, publicly available TLE data is updated, for example, quite frequently. The update frequency depends on the satellite and its orbit, for example, the update frequency may range from many times a day (e.g., for satellites in very low orbits that are exposed to strong atmospheric drag and often need to perform corrective maneuvers) to once a week (e.g., for satellites in relatively higher orbits or exposed to lower atmospheric drag).

[0016] Thus, while it may be possible to provide the required accuracy for satellite positions, care needs to be taken to meet these requirements, for example, when selecting the ephemeris data format or when selecting the orbit model used for orbital propagation.

[0017] The ephemeris data consists of at least five parameters that describe the shape and position in space of the satellite orbit, with a timestamp from when other parameters describing the orbital ellipse were obtained. The position of the satellite at any given time in the near future can be predicted from this data using orbital mechanics. However, the accuracy of the prediction decreases further into the future. The validity time of a particular set of parameters ranges from the order of days to years, depending on many factors such as the type and height of the orbit, as well as the desired accuracy.

[0018] In the connected state, i.e., RRC_CONNECTED state, the UE has an established connection to the network. The purpose of connected state mobility is to ensure that connectivity is maintained without interruption or noticeable degradation as the device moves within the network. The UE is required to perform a search for a new cell on both the current carrier frequency (intra-frequency) and a different carrier frequency (inter-frequency) reported by the network. The UE does not make any decision on its own as to when it is time to trigger a handover procedure to a different cell (partially except in the case of conditional handover). This is rather based on various trigger conditions. Typically, the UE reports the results of any configured measurements to the network so that the network can make a decision as to whether it is time for a handover to a new cell. However, when conditional handover is used, the network partially "delegates" the execution decision to the UE by ordering it to perform a handover if certain trigger conditions are met.

[0019] In 5G NR, handover is a special case of a procedure called "Reconfiguration with Synchronization". In addition, various handover mechanisms such as Dual Active Protocol Stack (DAPS), Conditional Handover (CHO), and RACH-less HO (only for LTE) have been introduced in the specification to improve mobility robustness performance for challenging scenarios that require low latency and high reliability performance. Typically, before the actual HO, the network configures the UE with RRM measurements and makes the HO decision based on the measurement report sent by the UE.

[0020] The following excerpt from TS 38.300 V16.2.0(2020-07) details the measurement model within NR (how cell level and beam layer 3 measurements are derived): In RRC_CONNECTED, the UE measures multiple beams (at least one) of the cell and the measurement results (power values) are averaged to derive the cell quality. In doing so, the UE is configured to consider a subset of the detected beams. Filtering occurs at at least two different levels, the physical layer to derive the beam quality, and then at the RRC level to derive the cell quality from the multiple beams. The cell quality from the beam measurements is derived in the same way for serving and non-serving cells. The measurement report may include the measurement results of the X best beams if the UE is configured to do so by the gNB. The corresponding high-level measurement model is illustrated in Figure 4 and described below. In Figure 4, K-beam corresponds to measurements on SSB or CSI-RS resources configured by the gNB for L3 mobility and detected by the UE on L1. Figure 4 illustrates the following: A: Measurements inside the physical layer (beam-specific samples). Layer 1 filtering: Internal Layer 1 filtering of the input measured at point A. The exact filtering is implementation dependent. How the measurement is actually performed within the physical layer by the implementation (input A and Layer 1 filtering) is not constrained by the standard. A 1 : Measurements reported by layer 1 up to layer 3 after layer 1 filtering (i.e., beam-specific measurements). Beam integration / selection: Beam specific measurements are integrated to derive the cell quality. The behavior of beam integration / selection is standardized and the configuration of this module is provided by RRC signaling. The reporting period at B is A. 1 is equal to one measurement period in B: Measurements derived from beam-specific measurements reported to Layer 3 after beam integration / selection (i.e., cell quality). Layer 3 filtering for cell quality: filtering done on measurements provided by point B. The behavior of the Layer 3 filters is standardized and the settings of the Layer 3 filters are provided by RRC signaling. The filtering reporting period at C is equal to one measurement period at B. C: Measurement after processing in the layer 3 filter. The reported rate is identical to the reported rate at point B. This measurement is used as input for the evaluation of one or more of the reporting criteria. Evaluation of the reporting criteria: Check whether an actual measurement report is required at point D. The evaluation can be based on the flow of two or more measurements at reference point C, for example to compare between different measurements. This is done by comparing inputs C and C. 1 The UE detects that at least the new measurement results are at points C, C 1 The reporting criteria are evaluated every time a UE is reported. The reporting criteria are standardized and the configuration is provided by RRC signaling (UE measurements). D: Measurement report information (message) transmitted over the air interface. L3 Beam Filtering: Point A 1 Filtering is performed on measurements provided by E (i.e., beam-specific measurements). The behavior of the beam filters is standardized and the beam filter settings are provided by RRC signaling. The filtering reporting period in E is 1 is equal to one measurement period in E: Measurement after processing in the beam filter (i.e., beam-specific measurement). The reporting speed is at point A. 1 This measurement is used as input to select the X measurement to be reported. Beam Selection for Beam Reporting: Select measurement X from the measurements provided at point E. The behavior of beam selection is standardized and the configuration of this module is provided by RRC signaling. F: Beam measurement information included within the measurement report (transmitted) over the air interface.

[0021] Layer 1 filtering introduces a certain level of measurement averaging. Exactly how and when the UE makes the desired measurements is implementation specific to the point where the output at B meets the performance requirements set in 3GPP TS 38.133. Layer 3 filtering on the cell quality and related parameters used is specified in 3GPP TS 38.331 and does not introduce any delay in sample availability between points B and C. 1 The measurements at are the inputs used in the event evaluation. The L3 beam filtering and associated parameters are specified in 3GPP TS 38.331 and do not introduce any delay in sample availability between E and F.

[0022] The intra-frequency neighbor (cell) measurements and the inter-frequency neighbor (cell) measurements are defined as follows: Synchronization Signal Block (SSB) based intra-frequency measurement: As long as the center frequency of the serving cell's SSB and the center frequency of the neighboring cell's SSB are the same and the subcarrier spacing of the two SSBs is also the same, the measurement is defined as an SSB based intra-frequency measurement. SSB-based inter-frequency measurement: As long as the center frequency of the SSB of the serving cell and the center frequency of the SSB of the neighboring cell are different, or the subcarrier spacing of the two SSBs is different, the measurement is specified as an SSB-based inter-frequency measurement. It may be noted that in SSB-based measurement, one measurement object corresponds to one SSB, and the UE considers different SSBs as different cells. Channel State Information Reference Signal (CSI-RS) based intra-frequency measurement: As long as the bandwidth of the CSI-RS resource on the neighboring cell configured for the measurement is within the bandwidth of the CSI-RS resource on the serving cell configured for the measurement and the subcarrier spacing of the two CSI-RS resources is the same, the measurement is defined as a CSI-RS based intra-frequency measurement. CSI-RS based inter-frequency measurement: As long as the bandwidth of the CSI-RS resource on the neighboring cell configured for the measurement is not within the bandwidth of the CSI-RS resource on the serving cell configured for the measurement or the subcarrier spacing of the two CSI-RS resources is different, the measurement is defined as a CSI-RS based inter-frequency measurement.

[0023] Whether the measurement is non-gap assisted or gap assisted depends on the UE capabilities, the UE's active bandwidth portion (BWP) and the current operating frequency. In the SSB-based inter-frequency measurement, if the measurement gap requirement information is reported by the UE, the measurement gap configuration may be provided according to the information. Alternatively, the measurement gap configuration is always provided in the following cases: If the UE supports per-UE measurement gaps. If the UE supports per-FR measurement gaps and none of the serving cells are within the same frequency range of the measurement object. In the SSB-based intra-frequency measurement, if the measurement gap requirement information is reported by the UE, the measurement gap configuration may be provided according to the information. Alternatively, the measurement gap configuration is always provided in the following cases: If none of the UE configured BWPs other than the initial BWP contains frequency domain resources of the SSB associated with the initial DL BWP.

[0024] In a non-gap assisted scenario, the UE is not capable of making such measurements without a measurement gap. In a gap assisted scenario, the UE cannot be assumed to be capable of making such measurements without a measurement gap.

[0025] Specification 3GPP TS 38.331 V16.2.0(2020-07) details the configuration of measurement model related parameters in the measurement object (e.g. associated with the configured event and measurement identifiers). JPEG0007681103000001.jpg96170

[0026] The measurement procedure distinguishes between the following types of cells: NR Serving Cells - These are the Special Cell (SpCell) and one or more Secondary Cells (SCells). Listed Cells - These are the cells listed within the measurement object. Detected Cells - These are cells that are not listed in the measurement object, but are detected by the UE on the SSB frequency and subcarrier spacing indicated by the measurement object.

[0027] In this specification, the NR detected cells and listed cells (sometimes called neighbor cells, or non-serving cells) are of most relevance.

[0028] As defined above, an NR listed cell is a cell that is listed in a measurement object, as shown below. JPEG0007681103000002.jpg117170

[0029] As defined above, an NR detected cell is a cell that is not listed in the measurement object, but is detected by the UE on a synchronization signal (SSB) frequency and subcarrier spacing indicated by the measurement object. In the normal case (i.e., in a properly configured network with no physical cell identifier (PCI) collisions), each detected cell in a given frequency (associated with a measurement object) has its own PCI within that frequency.

[0030] In that sense, a detected cell is a cell within a configured frequency (i.e., a configured Measurement Object - MO) at a given PCI associated with the detected SSBs, in that the PCI is derived by detecting the synchronization sequences Primary Synchronization Signal (PSS) and Secondary Synchronization Signal (SSS) as specified in 3GPP TS 38.211 Section 5.5.3. 5.5.3 Measurements being taken 5.5.3.1 Overview […] The UE: […] 1> For each measId in the measIdList in VarMeasConfig: […] 2> If the reportType for the associated reportConfig is periodic, then eventTriggered or condTriggerConfig is: […] 5> If measObject is associated with NR and rsType is set to ssb. 6> reportQuantityRS-Indexes and maxNrofRS-IndexesToReport for the associated reportConfig are set. 7> Derive Layer 3 beam measurements only based on the SS / PBCH blocks for each measurement number indicated in reportQuantityRS-Indexes as described in 5.5.3.3a. 6> Derive cell measurement results based on SS / PBCH blocks for the trigger number and each measurement number indicated in reportQuantityCell using parameters from the associated measObject as described in 5.5.3.3. […] 2> Evaluate the reporting criteria specified in 5.5.4 unless reportConfig is condTrrigerConfig. […] 5.5.4 Measurement reporting triggers 5.5.4.1 Overview If AS security is successfully activated, the UE: 1> For each measId in the measIdList in VarMeasConfig: 2> If the corresponding reportConfig contains a reportType set to eventTriggered or periodic. 3> If the corresponding measObject is related to NR. 4> If eventA1 or eventA2 is set in the corresponding reportConfig. 5> Consider only serving cells where applicable. 4> If eventA3 or eventA5 is set in the corresponding reportConfig. 5> If a serving cell is associated with a measObjectNR and a neighbour is associated with another measObjectNR, then also consider any serving cells associated with the other measObjectNR that are neighbour cells. 4> The corresponding reportConfig contains a reportType set to periodic, or 4> For events of measurement other than eventA1 or eventA2: 5>When useWhiteCellList is set to true. 6> Consider any neighboring cells detected based on the parameters in the associated measObjectNR that are applicable if the cell in question is included in the whiteCellsToAddModList specified in VarMeasConfig for this measld. 5> In other cases: 6> Consider any neighboring cells detected based on the parameters in the associated measObjectNR that are applicable if the cell in question is not included in the blackCellsToAddModList specified in VarMeasConfig for this measld. […] 2> if reportType is set to eventTriggered, and if the entry conditions applicable to this event, i.e. the event corresponding to the eventID in the corresponding reportConfig in VarMeasConfig, are met for one or more applicable cells for all measurements after Layer 3 filtering taken during the timeToTrigger specified for this event in VarMeasConfig, and VarMeasReportList does not contain a measurement report entry for this measId (the first cell triggers the event): 3> Contains the measurement report entry in VarMeasReportList for this measId. 3> Set the numberOfReportsSent specified in the VarMeasReportList for this measId to 0. 3> Include the relevant cell in the cellsTriggeredList defined in the VarMeasReportList for this measId. […] 3> Initiate the measurement reporting procedure as specified in 5.5.5.

[0031] Cell Quality Derivation (CQD) of Neighboring Cells in RRC and Its Use NR in RRC_CONNECTED is configured to perform neighbor cell measurements for event triggered measurement reporting, for example, if the UE is configured with any of the following events: Event A3: Neighborhood has better offset than PCell / PSCell. Event A4: The neighborhood becomes better than the absolute threshold. Event A5: PCell / PSCell becomes worse than absolute threshold 1 and neighbor / SCell becomes better than another absolute threshold 2. Event A6: The neighbor has a better offset than the SCell.

[0032] RRC procedures for neighbor cell measurements are specified for it. The purpose is to allow the network to configure the UE with a measurement event (e.g. A3) where the neighbor cell quality (e.g. RSRP, RSRQ, SINR) is compared with absolute thresholds and / or the quality of the serving cell (possibly to trigger an inter-frequency / intra-frequency handover, possibly called synchronized Master Cell Group (MCG) reconfiguration in NR).

[0033] So far, there are (one or more) specific challenges: The following can be considered as the main challenges that need to be addressed when evolving NR to support NTNs, moving cells, long propagation delays, and large Doppler shifts: Moving Cells: The default assumption in terrestrial network design, e.g., NR or LTE, is that cells are fixed. This is not the case in NTN, especially when LEO satellites are considered. LEO satellites may be visible to UEs on the ground only for a few seconds or minutes. There are two different options for LEO deployments. The beam / cell coverage is fixed relative to the geographic location with Earth fixed beams, i.e. moving beams from the satellites ensure that a particular beam covers the same geographic area even as the satellite moves relative to the Earth's surface. On the other hand, with moving beams, the LEO satellites fix their antenna pointing direction relative to the Earth's surface, e.g., perpendicular to the Earth's surface, and thus the cell / beam coverage sweeps the Earth as the satellite moves. In that case, the spot beam serving the UE may switch every few seconds. Long Propagation Delays: Propagation delays in terrestrial mobile systems are typically less than 1 millisecond. In contrast, propagation delays in NTNs are much longer and can range from a few milliseconds (LEO) to hundreds of milliseconds (GEO), depending on the altitude of the satellites or airborne platforms deployed in the NTN. Large Doppler Shift: The movement of satellites or airborne platforms deployed within the NTN can lead to large Doppler shifts. For example, a LEO satellite at an altitude of 600 km can lead to a time-varying Doppler shift of as much as 24 ppm.

[0034] Another complex aspect of NTNs with earth-fixed cells is that it is assumed that the responsibility for covering a particular geographical cell area switches from one satellite to another (i.e., both the old and new satellites cover the cell area simultaneously) with preferably a short overlap period, which entails a cell change, e.g., a change in PCI, which means that all UEs connected in the old cell (to / via the old satellite) must be handed over to the new cell (and new satellite) with a short period (i.e., overlap period), which may cause high load peaks on RACH resources, random access processing resources and processing resources for handover preparation associated with the new cell. If these resources are overloaded, the consequences may entail, for example, extended cutoff times, handover failures and radio link failures.

[0035] In Release 16, during the study item phase, RAN2 discussed mobility procedures to find solutions addressing the problems that may arise due to the challenges listed above for NTNs with the motivation to reduce service interruption during handover due to large propagation delays, high handover rate due to moving cells, to introduce mechanisms to improve handover robustness due to small signal strength changes in areas of beam overlap, and to compensate for propagation delay differences within the UE measurement window between cells / beams coming from different satellites. This is especially true in the case of LEO NTNs. The technical report concluded during the SI phase in Release 16 addressed aspects related to additional trigger conditions for conditional handover mechanisms, adaptation of measurement based thresholds and events, mobility related configuration, measurement configuration / reporting, and service continuity for mobility between TN and NTN.

[0036] This technical report features the following enhancements to measurement setup and reporting: Conditional triggering of measurement reports: Triggering of measurement reports can be based on UE location. This may be based on UE location vs. reference location, or a combination of location and RSRP / RSRQ. Inclusion of location information in measurement reports: Location information may be piggybacked on top of the measurement reports to provide additional information to the network when determining which HO. Additional design considerations (e.g., signaling overhead impact and potential privacy concerns) can be addressed within the work item phase. Network compensation for propagation delay differences between satellites: The network can compensate for the propagation delay differences within the UE measurement window, for example via system information or via dedicated signaling in a UE-specific manner. Other solutions to this problem are not excluded.

[0037] A common NTN-specific measurement report triggering problem is that neighboring cells in the RSRP range are very similar and events such as A3 may not trigger in time. If the network has better knowledge of the types of NTN-specific conditions the UE sees, the network can maintain connectivity to the UE in a more efficient way. Summary of the Invention

[0038] Certain aspects of the present disclosure and embodiments thereof may provide solutions to these and other problems.

[0039] According to certain embodiments, a method by a wireless device includes determining whether one or more conditions for triggering measurements occur and performing one or more measurements based on the occurrence of the one or more conditions, the one or more conditions for triggering measurements being based on at least one of a timing advance value in a source cell, a distance between the wireless device and a satellite node serving the source cell or a candidate target cell, a predicted time that the wireless device will be served in the source cell and / or the candidate target cell, an elevation angle of the satellite node serving the source cell and / or the candidate target cell, reaching a time point set by a network node, detection of an identifier associated with a particular cell, and a speed or velocity of the wireless device.

[0040] According to certain embodiments, the wireless device is adapted to determine whether one or more conditions for triggering a measurement occur and to perform one or more measurements based on the occurrence of the one or more conditions, the one or more conditions for triggering a measurement being based on at least one of a timing advance value in the source cell, a distance between the wireless device and a satellite node serving the source cell or a candidate target cell, a predicted time that the wireless device will be served in the source cell and / or the candidate target cell, an elevation angle of the satellite node serving the source cell and / or the candidate target cell, reaching a time point set by a network node, detection of an identifier associated with a particular cell, and a speed or velocity of the wireless device.

[0041] According to a particular embodiment, the method by the network node includes transmitting to the wireless device a measurement configuration including one or more conditions for triggering a measurement. The network node receives a measurement report from the wireless device based on the measurement configuration. The one or more conditions for triggering a measurement are based on at least one of a timing advance value in the source cell, a distance between the wireless device and a satellite node serving the source cell or a candidate target cell, a predicted time that the wireless device will be served in the source cell and / or the candidate target cell, an elevation angle of a satellite serving the source cell and / or the candidate target cell, reaching a time point configured by the network node, detection of an identifier associated with a particular cell, and a speed or velocity of the wireless device.

[0042] According to certain embodiments, the network node is adapted to send to the wireless device a measurement configuration including one or more conditions for triggering a measurement. The network node is adapted to receive a measurement report from the wireless device based on the measurement configuration. The one or more conditions for triggering a measurement are based on at least one of a timing advance value in the source cell, a distance between the wireless device and a satellite node serving the source cell or the candidate target cell, a predicted time that the wireless device will be served in the source cell and / or the candidate target cell, an elevation angle of a satellite serving the source cell and / or the candidate target cell, reaching a time point configured by the network node, detection of an identifier associated with a particular cell, and a speed or velocity of the wireless device. Certain embodiments may provide one or more of the following technical advantages(s). By way of example, certain embodiments may provide a technical advantage in that the network may maintain a connection to the UE in a more efficient manner when the network has better knowledge of the type of NTN-specific conditions the UE sees.

[0043] Other advantages may be readily apparent to one of ordinary skill in the art. Some embodiments may have none, some, or all of the listed advantages.

[0044] For a more complete understanding of the disclosed embodiments and their features and advantages, reference is now made to the following descriptions taken in conjunction with the accompanying drawings, in which: [Brief description of the drawings]

[0045] [Figure 1] FIG. 1 illustrates an example architecture of a satellite network with bent pipe transponders. [Diagram 2] FIG. 1 illustrates an example of a diurnal Doppler shift of a forward service link observed for a GEO satellite operating from an inclined orbit. [Diagram 3] FIG. 1 illustrates six exemplary parameters that can describe a satellite orbit. [Figure 4] FIG. 1 illustrates a high-level measurement model. [Diagram 5] FIG. 1 illustrates an exemplary wireless network, according to some embodiments. [Figure 6] FIG. 1 illustrates an exemplary network node, according to some embodiments. [Figure 7] 1 illustrates an exemplary wireless device in accordance with some embodiments. [Figure 8] FIG. 2 illustrates an exemplary user equipment, according to some embodiments. [Figure 9] FIG. 1 illustrates a virtualization environment in which functionality implemented by some embodiments may be virtualized, according to some embodiments. [Figure 10] FIG. 1 illustrates an exemplary communications network connected to a host computer through an intermediate network, according to some embodiments. [Figure 11] FIG. 2 is a generalized block diagram of a host computer communicating with user equipment via a base station over a partially wireless connection in accordance with some embodiments. [Figure 12] FIG. 1 illustrates a method implemented in a communication system according to one embodiment. [Figure 13] FIG. 1 illustrates another method implemented in a communication system according to one embodiment. [Figure 14] FIG. 1 illustrates another method implemented in a communication system according to one embodiment. [Figure 15] FIG. 1 illustrates another method implemented in a communication system according to one embodiment. [Figure 16] 1 illustrates an exemplary method by a wireless device according to some embodiments. [Figure 17] FIG. 2 illustrates an exemplary virtual device, according to some embodiments. [Figure 18] 1 illustrates another exemplary method by a wireless device according to some embodiments. [Figure 19] FIG. 2 illustrates another exemplary virtual device, according to some embodiments. [Figure 20] FIG. 1 illustrates an exemplary method by a network node, according to some embodiments. [Figure 21] FIG. 2 illustrates another exemplary virtual device, according to some embodiments. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0046] Some of the embodiments contemplated herein are further described below with reference to the accompanying drawings, however, other embodiments are within the scope of the subject matter disclosed herein and the disclosed subject matter should not be construed as being limited to only the embodiments described herein, but rather these embodiments are provided as examples to convey the scope of the subject matter to those skilled in the art.

[0047] In general, all terms used herein should be interpreted according to their ordinary meaning in the relevant technical field, unless a different meaning is clearly given and / or suggested by the context of use. All references to elements, devices, components, means, steps, etc. should be openly interpreted as referring to at least one instance of the element, device, component, means, step, etc., unless expressly stated otherwise. The steps of any method disclosed herein need not be performed in the exact order disclosed, unless a step is expressly described as being next to or prior to another step, and / or unless it is implied that a step must be next to or prior to another step. Any feature of any of the embodiments disclosed herein may be applied to any other embodiment, where appropriate. Similarly, any advantage of any embodiment may be applied to any other embodiment, and vice versa. Other objects, features, and advantages of the embodiments of the present specification will become apparent from the following description.

[0048] It should be noted that the method presented below relates to both fixed and mobile cells, serving and feeder link switches, unless expressly stated otherwise. The terms "cell" and "beam" are used interchangeably, unless expressly stated otherwise. The terms "radio terminal", "user equipment", "UE", "radio device" and "device" are used interchangeably in this document, unless expressly stated otherwise. The terms "source cell" or "target cell" do not refer to a global cell ID in this document, assuming that the global cell ID is mapped to a geographical area within a tracking area that is also defined for the geographical area. Certain embodiments of the solution are described using NR terminology, e.g., the term "gNB" instead of the more generic and RAT-dependent term "radio base station", but this should not be construed as limiting, since the solution is also applicable to other RATs that may be used in NTNs, such as LTE. Unless explicitly stated otherwise, the examples described below relate to the following handover mechanisms: "Reconfiguration with Synchronization / Reconfiguration with Mobility Information", "5.2 Dual Active Protocol Stack (DAPS) Handover", "5.3 Conditional Handover (CHO)", and "RACH-less Handover".

[0049] According to certain embodiments, various methods and systems are provided for measurement reporting that can improve measurement reporting for NTN systems. Related aspects for configuring a UE for measurement reporting are also disclosed.

[0050] According to certain embodiments, a method within a device for providing a measurement report may include one or more of the following. The RSRP / RSRQ, SINR or RSSI, or path loss threshold at which the device experienced or inferred path loss should be as follows for the channel quality to be sufficient or good enough in the source cell and / or candidate target cell: The location may be formulated in geographic coordinates, i.e., taking into account the device location in two or three dimensional space. Device speed including direction. The distance between the device and the satellite nodes serving the source cell and / or the candidate target cells, based on the positions of the satellite nodes as known from the ephemeris data. More specifically, the UE may report the distance to specific satellites or cell / PCI center reference points. These specific satellites / cells / PCIs may be referred to as candidate serving cells. This may be added to the RSRP / RSRQ / SINR measurement reports for a given satellite / cell / PCI. The distance or differential delay between the device and the nadir of the satellite serving the source cell and / or the candidate target cell, or any other reference point, may be explicitly specified or provided via common or dedicated signaling in two or three dimensional space. In a dependent embodiment, the device velocity along with the direction of movement is also provided to the network. In a dependent embodiment, the signed Doppler / frequency shift estimated by the device is also provided to the network. The derivative of the distance or differential delay above. The expected time to be served (as specified in TR 38.821) in the source cell or in a candidate target cell. The elevation angle of a satellite serving a source cell or a candidate target cell. The derivative of the elevation angle of a satellite serving a source cell or a candidate target cell. The Timing Advance (TA) value in the source cell and / or candidate target cells. Various combinations of the above.

[0051] In certain embodiments, the device may provide an estimation accuracy of the TA value, such as the number of satellites used to estimate the TA. For RACH-less and large SCS and / or high frequencies, the TA needs to be at the sub-microsecond level. This information is useful for the gNB to know if it should / can initiate RACH-less HO in the target cell.

[0052] Throughout this disclosure, the terms "beam" or "cell" may be used interchangeably unless expressly noted otherwise. Although certain embodiments are described with reference to NTN, the presented methods apply to any wireless network (e.g., any wireless network governed by line-of-sight conditions). Certain embodiments (or portions thereof) may be implemented in accordance with one or more standards, such as 3GPP Release 17+, 3GPP TS 38.331, and / or NR TR 38.821 Release 16.

[0053] Although the subject matter described herein may be implemented in any suitable type of system using any suitable components, the embodiments disclosed herein are described with respect to a wireless network, such as the exemplary wireless network shown in FIG. 5. For simplicity, the wireless network of FIG. 5 illustrates only the network 106, the network nodes 160 and 160b, and the WD 110. In practice, the wireless network may further include any additional elements suitable for supporting communication between wireless devices, or between a wireless device and another communication device, such as a landline telephone, a service provider, or any other network node or end device. Of the illustrated components, the network node 160 and the wireless device (WD) 110 will be described in more detail. The wireless network may provide communication and other types of services to one or more wireless devices to facilitate the wireless devices accessing and / or using services provided by or via the wireless network.

[0054] The wireless network may comprise and / or interfere with any type of communication, telecommunications, data, cellular, and / or radio network, or other similar type of system. In some embodiments, the wireless network may be configured to operate according to a particular standard or other type of predefined rules or procedures. Thus, certain embodiments of the wireless network may implement a communication standard, such as Global System for Mobile Communications (GSM), Universal Mobile Telecommunications System (UMTS), Long Term Evolution (LTE), and / or other suitable 2G, 3G, 4G, or 5G standard, a wireless local area network (WLAN) standard, such as the IEEE 802.11 standard, and / or any other suitable wireless communication standard, such as Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, and / or ZigBee standard.

[0055] The network 106 may comprise one or more backhaul networks, core networks, IP networks, public switched telephone networks (PSTN), packet data networks, optical networks, wide area networks (WANs), local area networks (LANs), wireless local area networks (WLANs), wired networks, wireless networks, metropolitan area networks, and other networks that enable communication between devices.

[0056] Network node 160 and WD 110 comprise various components, which are described in more detail below. These components may cooperate to provide the functionality of a network node and / or a wireless device, such as providing wireless connectivity in a wireless network. In different embodiments, a wireless network may comprise any number of wired or wireless networks, network nodes, base stations, controllers, wireless devices, relay stations, and / or any other components or systems that may facilitate or participate in the communication of data and / or signals, whether via wired or wireless connections.

[0057] FIG. 6 illustrates an exemplary network node 160, according to some embodiments. As used herein, a network node refers to equipment that can, is configured to, is arranged to, and / or is operable to communicate directly or indirectly with wireless devices and / or other network nodes, or equipment in a wireless network that enables and / or provides wireless access to wireless devices and / or performs other functions (e.g., management) of the wireless network. Examples of network nodes include, without limitation, access points (APs) (e.g., wireless access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs), and NR Node Bs (gNBs)). Base stations may be categorized based on the amount of coverage they provide (or in other words, their transmit power levels), and therefore may be referred to as femto base stations, pico base stations, micro base stations, macro base stations. A base station may also be a relay node, or a relay donor node that controls a relay. A network node may also include one or more (or all) parts of a distributed radio base station, such as a centralized digital unit, and / or a remote radio unit (RRU), which may be referred to as a remote radio head (RRH). Such a remote radio unit may or may not be integrated with an antenna as an antenna-integrated radio. A part of a distributed radio base station may also be referred to as a node of a distributed antenna system (DAS). Other further examples of a network node include MSR equipment such as a multi-standard radio (MSR) BS, a network controller such as a radio network controller (RNC) or a base station controller (BSC), a base transceiver station (BTS), a transmission point, a transmitting node, a multi-cell / multicast coordination entity (MCE), a core network node (e.g., MSC, MME), an O&M node, an OSS node, a SON node, a positioning node (e.g., E-SMLC), and / or an MDT. As another example, a network node may be a virtual network node, as described in more detail below.More generally, however, a network node may represent any suitable device (or group of devices) configured, arranged, and / or operable to enable and / or provide access to a wireless network for a wireless device or to provide some service to a wireless device accessing the wireless network.

[0058] In FIG. 6, network node 160 comprises processing circuitry 170, device readable medium 180, interface 190, auxiliary equipment 184, power source 186, power circuitry 187, and antenna 162. Although network node 160 shown in the example wireless network of FIG. 6 may represent a device including the shown combination of hardware components, other embodiments may comprise network nodes having different combinations of components. It should be understood that a network node comprises any suitable combination of hardware and / or software necessary to perform the tasks, features, functions, and methods disclosed herein. Furthermore, although the components of network node 160 are shown as a single box located within a larger box or as a single box nested within multiple boxes, in reality the network node may comprise multiple different physical components that make up a single shown component (e.g., device readable medium 180 may comprise multiple separate hard drives as well as multiple RAM modules).

[0059] Similarly, the network node 160 may be assembled from multiple physically separate components (e.g., a Node B component and an RNC component, or a BTS component and a BSC component, etc.), each of which may have their own respective components. In certain scenarios where the network node 160 comprises multiple separate components (e.g., a BTS component and a BSC component), one or more of the separate components may be shared among several network nodes. For example, a single RNC may control several Node Bs. In such scenarios, each unique Node B and RNC pair may be considered as a single separate network node in some cases. In some embodiments, the network node 160 may be configured to support several radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate device-readable media 180 for different RATs) and some components may be reused (e.g., the same antenna 162 may be shared by the RATs). Network node 160 may also include multiple sets of the various illustrated components for different wireless technologies, such as, for example, GSM, WCDMA, LTE, NR, WiFi, or Bluetooth wireless technologies, integrated into network node 160. These wireless technologies may be integrated in the same or different chips or chipsets, and other components within network node 160.

[0060] The processing circuitry 170 is configured to perform any decision, computation, or similar operations (e.g., certain acquisition operations) described herein as being provided by a network node. These operations performed by the processing circuitry 170 may include processing information acquired by the processing circuitry 170, for example, by transforming the acquired information into other information, comparing the acquired or transformed information to information stored in the network node, and / or performing one or more operations based on the acquired or transformed information, and making a decision as a result of such processing.

[0061] The processing circuitry 170 may comprise one or more combinations of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software, and / or coded logic operable, alone or in conjunction with other network node 160 components, such as device readable medium 180, to provide the functionality of the network node 160. For example, the processing circuitry 170 may execute instructions stored on the device readable medium 180 or in memory within the processing circuitry 170. Such functionality may include providing any of the various wireless features, functions, or benefits discussed herein. In some embodiments, the processing circuitry 170 may include a system on a chip (SOC).

[0062] In some embodiments, the processing circuitry 170 may include one or more of a radio frequency (RF) transceiver circuitry 172 and a baseband processing circuitry 174. In some embodiments, the radio frequency (RF) transceiver circuitry 172 and the baseband processing circuitry 174 may be on separate chips (or chipsets), boards, or units, such as a radio unit and a digital unit. In alternative embodiments, some or all of the RF transceiver circuitry 172 and the baseband processing circuitry 174 may be on the same chip or set of chips, board, or unit.

[0063] In certain embodiments, some or all of the functionality described herein as being provided by a network node, base station, eNB, or other such network device may be performed by the processing circuitry 170 executing instructions stored on the device-readable medium 180, or memory within the processing circuitry 170. In alternative embodiments, some or all of the functionality may be provided by the processing circuitry 170 without executing instructions stored on a separate or distinct device-readable medium, such as in a hardwired manner. In any of those embodiments, the processing circuitry 170 may be configured to perform the described functions, whether or not it executes instructions stored on a device-readable storage medium. Benefits provided by such functionality are not limited to the processing circuitry 170 alone or other components of the network node 160, but are enjoyed by the network node 160 as a whole and / or end users and wireless networks in general.

[0064] The device readable medium 180 may comprise any form of volatile or non-volatile computer readable memory, including, without limitation, persistent storage, solid state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read only memory (ROM), mass storage media (e.g., hard disk), removable storage media (e.g., flash drive, compact disk (CD), or digital video disk (DVD)), and / or any other volatile or non-volatile non-transitory device readable and / or computer executable memory device that stores information, data, and / or instructions that may be used by the processing circuit 170. The device readable medium 180 may store any suitable instructions, data, or information, including computer programs, software, applications (including one or more of logic, rules, codes, tables, etc.), and / or other instructions that may be executed by the processing circuit 170 and utilized by the network node 160. The device readable medium 180 may be used to store calculations performed by the processing circuit 170 and / or data received via the interface 190. In some embodiments, the processing circuit 170 and the device-readable medium 180 may be considered to be integrated.

[0065] The interface 190 is used in wired or wireless communication of signaling and / or data between the network node 160, the network 106, and / or the WD 110. As shown, the interface 190 includes a port / terminal 194 for transmitting data to and receiving data from the network 106, for example, via a wired connection. The interface 190 also includes a radio front-end circuit 192, which is coupled to the antenna 162 or may be part of the antenna 162 in certain embodiments. The radio front-end circuit 192 includes a filter 198 and an amplifier 196. The radio front-end circuit 192 may be connected to the antenna 162 and the processing circuit 170. The radio front-end circuit may be configured to condition signals communicated between the antenna 162 and the processing circuit 170. The radio front-end circuit 192 may receive digital data to be sent to another network node or WD via a wireless connection. The radio front-end circuitry 192 may convert the digital data into a radio signal having appropriate channel and bandwidth parameters using a combination of filters 198 and / or amplifiers 196. The radio signal may then be transmitted via the antenna 162. Similarly, when receiving data, the antenna 162 may collect a radio signal, which is then converted into digital data by the radio front-end circuitry 192. The digital data may be passed to the processing circuitry 170. In other embodiments, the interface may comprise different components and / or different combinations of components.

[0066] In certain alternative embodiments, network node 160 may not include a separate radio front-end circuit 192; instead, processing circuit 170 may comprise a radio front-end circuit and may be connected to antenna 162 without a separate radio front-end circuit 192. Similarly, in some embodiments, all or a portion of RF transceiver circuit 172 may be considered part of interface 190. In yet other embodiments, interface 190 may include one or more ports or terminals 194, radio front-end circuit 192, and RF transceiver circuit 172 as part of a radio unit (not shown), and interface 190 may communicate with baseband processing circuit 174, which is part of a digital unit (not shown).

[0067] Antenna 162 may include one or more antennas or antenna arrays configured to transmit and / or receive wireless signals. Antenna 162 may be coupled to radio front-end circuitry 192 and may be any type of antenna capable of wirelessly transmitting and receiving data and / or signals. In some embodiments, antenna 162 may include one or more omnidirectional, sector, or panel antennas operable to transmit / receive wireless signals, e.g., from 2 GHz to 66 GHz. An omnidirectional antenna may be used to transmit / receive wireless signals in any direction, a sector antenna may be used to transmit / receive wireless signals from devices in a particular area, and a panel antenna may be a line-of-sight antenna used to transmit / receive wireless signals in a relatively straight line. In some instances, the use of more than one antenna may be referred to as MIMO. In certain embodiments, antenna 162 may be separate from network node 160 and may be connectable to network node 160 through an interface or port.

[0068] The antenna 162, the interface 190, and / or the processing circuitry 170 may be configured to perform any receiving operation and / or certain acquisition operations described herein as being performed by a network node. Any information, data, and / or signals may be received from a wireless device, another network node, and / or any other network equipment. Similarly, the antenna 162, the interface 190, and / or the processing circuitry 170 may be configured to perform any transmitting operation described herein as being performed by a network node. Any information, data, and / or signals may be transmitted to a wireless device, another network node, and / or any other network equipment.

[0069] The power circuit 187 may comprise or be coupled to a power management circuit and is configured to provide power to the components of the network node 160 for performing the functions described herein. The power circuit 187 may receive power from the power source 186. The power source 186 and / or the power circuit 187 may be configured to provide power to the various components of the network node 160 in a form suitable for each component (e.g., at the voltage and current levels required for each respective component). The power source 186 may either be included in the power circuit 187 and / or the network node 160 or be external thereto. For example, the network node 160 may be connectable to an external power source (e.g., an electrical outlet) via an input circuit or interface, such as an electrical cable, whereby the external power source provides power to the power circuit 187. As a further example, the power source 186 may comprise a power source in the form of a battery or battery pack connected to or integrated with the power circuit 187. The battery may provide backup power in the event that the external power source fails. Other types of power sources, such as solar cell devices, may also be used.

[0070] Alternate embodiments of network node 160 may include additional components other than those shown in Figure 6 that may be responsible for providing some aspects of the network node's functionality, including any of the functionality described herein and / or functionality necessary to support the subject matter described herein. For example, network node 160 may include user interface devices that allow for the input of information into and output of information from network node 160. This may enable a user to perform diagnostics, maintenance, repair, and other management functions for network node 160.

[0071] FIG. 7 illustrates an exemplary WD 110, according to some embodiments. A WD, as used herein, refers to a device capable, configured, configured, and / or operable to wirelessly communicate with network nodes and / or other wireless devices. Unless otherwise specified, the term WD may be used interchangeably with UE herein. Communicating wirelessly may involve transmitting and / or receiving wireless signals using electromagnetic, radio, infrared, and / or other types of signals suitable for conveying information over the air. In some embodiments, a WD may be configured to transmit and / or receive information without direct human interaction. For example, a WD may be designed to transmit information to a network on a predetermined schedule, when triggered by an internal or external event, or in response to a request from the network. Examples of WDs include, but are not limited to, smartphones, mobile phones, cell phones, voice-over-IP (VoIP) phones, wireless local loop phones, desktop computers, personal digital assistants (PDAs), wireless cameras, gaming consoles or devices, music storage devices, playback appliances, wearable terminal devices, wireless endpoints, mobile stations, tablets, laptops, laptop embedded equipment (LEE), laptop mounted equipment (LME), smart devices, wireless customer premises equipment (CPE), in-vehicle wireless terminal devices, etc. WDs may support device-to-device (D2D) communications, for example, by implementing 3GPP standards for sidelink communications, vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), and vehicle-to-everything (V2X), in which case they may be referred to as D2D communications devices. As yet another specific example, in an Internet of Things (IoT) scenario, a WD may represent a machine or other device that performs monitoring and / or measurements and transmits results of such monitoring and / or measurements to another WD and / or network node.The WD may in this case be a machine-to-machine (M2M) device, which may be referred to as an MTC device in the 3GPP context. As one particular example, the WD may be a UE implementing the 3GPP Narrowband Internet of Things (NB-IoT) standard. Particular examples of such machines or devices are sensors, metering devices such as power meters, industrial machinery, or household or personal appliances (e.g., refrigerators, televisions, etc.), personal wearables (e.g., watches, fitness trackers, etc.). In other scenarios, the WD may represent a vehicle or other equipment that may monitor and / or report its operating status or other functions associated with the operation. The WD as described above may represent an endpoint of a wireless connection, in which case the device may be referred to as a wireless terminal. Furthermore, the WD as described above may be a mobile object, in which case the device may be referred to as a mobile device or mobile terminal.

[0072] As shown, WD 110 includes antenna 111, interface 114, processing circuitry 120, device readable medium 130, user interface equipment 132, auxiliary equipment 134, power source 136, and power circuitry 137. WD 110 may include multiple sets of one or more of the illustrated components for different wireless technologies that WD 110 supports, such as, for example, GSM, WCDMA, LTE, NR, WiFi, WiMAX, or Bluetooth wireless technologies, just to name a few. These wireless technologies may be integrated on the same or different chip or chipset as other components in WD 110.

[0073] Antenna 111 may include one or more antennas or antenna arrays configured to send and / or receive wireless signals and is connected to interface 114. In certain alternative embodiments, antenna 111 may be separate from WD 110 and connectable to WD 110 through an interface or port. Antenna 111, interface 114, and / or processing circuitry 120 may be configured to perform any receiving or transmitting operation described herein as being performed by a WD. Any information, data, and / or signal may be received from a network node and / or another WD. In some embodiments, the wireless front-end circuitry and / or antenna 111 may be considered an interface.

[0074] As shown, the interface 114 comprises a radio front-end circuit 112 and an antenna 111. The radio front-end circuit 112 comprises one or more filters 118 and an amplifier 116. The radio front-end circuit 112 is connected to the antenna 111 and the processing circuit 120 and is configured to condition signals communicated between the antenna 111 and the processing circuit 120. The radio front-end circuit 112 may be coupled to or part of the antenna 111. In some embodiments, the WD 110 may not include a separate radio front-end circuit 112; rather, the processing circuit 120 may comprise a radio front-end circuit and be connected to the antenna 111. Similarly, in some embodiments, some or all of the RF transceiver circuit 122 may be considered part of the interface 114. The radio front-end circuit 112 may receive digital data to be sent to other network nodes or WDs via a wireless connection. The radio front-end circuitry 112 may convert the digital data into a radio signal having appropriate channel and bandwidth parameters using a combination of filters 118 and / or amplifiers 116. The radio signal may then be transmitted via the antenna 111. Similarly, when receiving data, the antenna 111 may collect a radio signal, which is then converted into digital data by the radio front-end circuitry 112. The digital data may be passed to the processing circuitry 120. In other embodiments, the interface may comprise different components and / or different combinations of components.

[0075] Processing circuitry 120 may comprise one or more combinations of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software, and / or coded logic operable to provide WD 110 functionality, either alone or in conjunction with other WD 110 components, such as device readable medium 130. Such functionality may include providing any of the various wireless features or benefits discussed herein. For example, processing circuitry 120 may execute instructions stored on device readable medium 130 or in memory within processing circuitry 120 to provide the functionality disclosed herein.

[0076] As shown, the processing circuitry 120 includes one or more of an RF transceiver circuitry 122, a baseband processing circuitry 124, and an application processing circuitry 126. In other embodiments, the processing circuitry may comprise different components and / or different combinations of components. In a particular embodiment, the processing circuitry 120 of the WD 110 may comprise a SOC. In some embodiments, the RF transceiver circuitry 122, the baseband processing circuitry 124, and the application processing circuitry 126 may be on separate chips or chipsets. In alternative embodiments, some or all of the baseband processing circuitry 124 and the application processing circuitry 126 may be combined into one chip or chipset, and the RF transceiver circuitry 122 may be on a separate chip or chipset. In further alternative embodiments, some or all of the RF transceiver circuitry 122 and the baseband processing circuitry 124 may be on the same chip or chipset, and the application processing circuitry 126 may be on a separate chip or chipset. In yet other alternative embodiments, some or all of the RF transceiver circuitry 122, the baseband processing circuitry 124, and the application processing circuitry 126 may be combined within the same chip or chipset. In some embodiments, the RF transceiver circuitry 122 may be part of the interface 114. The RF transceiver circuitry 122 may condition the RF signals for the processing circuitry 120.

[0077] In some embodiments, some or all of the functionality described herein as being performed by the WD may be provided by the processing circuitry 120 executing instructions stored on the device-readable medium 130, which in some embodiments may be a computer-readable storage medium. In alternative embodiments, some or all of the functionality may be provided by the processing circuitry 120 without executing instructions stored on a separate or distinct device-readable storage medium, such as in a hardwired manner. In any of these particular embodiments, the processing circuitry 120 is configurable to perform the above-mentioned functions, whether or not it executes instructions stored on a device-readable medium. Benefits provided by such functionality are enjoyed by the WD 110 as a whole, and / or by end users and wireless networks in general, but not limited to the processing circuitry 120 alone or other components of the WD 110.

[0078] Processing circuitry 120 may be configured to perform any of the decision, calculation, or similar operations (e.g., some of the acquisition operations) described herein as being performed by a WD. These operations as performed by processing circuitry 120 may include processing information acquired by processing circuitry 120, for example, by transforming the acquired information into other information, comparing the acquired or converted information with information stored by WD 110, and / or performing one or more operations based on the acquired or converted information, and making a decision as a result of such processing.

[0079] The device-readable medium 130 may be operable to store computer programs, software, applications (including one or more of logic, rules, codes, tables, etc.), and / or other instructions that may be executed by the processing circuit 120. The device-readable medium 130 may include computer memory (e.g., random access memory (RAM) or read-only memory (ROM)), mass storage media (e.g., hard disk), removable storage media (e.g., compact disc (CD) or digital video disc (DVD)), and / or any other volatile or non-volatile, non-transitory device-readable and / or computer-executable memory device that stores information, data, and / or instructions that may be used by the processing circuit 120. In some embodiments, the processing circuit 120 and the device-readable medium 130 may be considered to be integrated.

[0080] The user interface device 132 may provide components that allow a human user to interact with the WD 110. Such interaction may be of many forms, such as visual, auditory, tactile, etc. The user interface device 132 may be operable to produce output to the user and to allow the user to provide input to the WD 110. The type of interaction may vary depending on the type of user interface device 132 installed in the WD 110. For example, if the WD 110 is a smartphone, the interaction may be through a touch screen, and if the WD 110 is a smart meter, the interaction may be through a screen that provides usage (e.g., gallons used) or a speaker that provides an audible alert (e.g., if smoke is detected). The user interface device 132 may include input interfaces, devices, and circuits, as well as output interfaces, devices, and circuits. The user interface device 132 is configured to allow input of information to the WD 110 and is connected to the processing circuit 120 to allow the processing circuit 120 to process the input information. The user interface device 132 may include, for example, a microphone, proximity or other sensors, keys / buttons, a touch display, one or more cameras, a USB port, or other input circuitry. The user interface device 132 is also configured to enable output of information from the WD 110 and to enable the processing circuitry 120 to output information from the WD 110. The user interface device 132 may include, for example, a speaker, a display, vibration circuitry, a USB port, a headphone interface, or other output circuitry. Using one or more input and output interfaces, devices, and circuits of the user interface device 132, the WD 110 may communicate with an end user and / or a wireless network and enable the end user and / or the wireless network to benefit from the functionality described herein.

[0081] Auxiliary device 134 is operable to provide more specific functions that a WD may not generally perform. It may include dedicated sensors to take measurements for various purposes, interfaces for additional types of communication such as wired communication, etc. The inclusion and types of components of auxiliary device 134 may vary depending on the embodiment and / or scenario.

[0082] The power source 136 may be in the form of a battery or battery pack in some embodiments. Other types of power sources may also be used, such as an external power source (e.g., an electrical outlet), a photovoltaic device, or a battery. The WD 110 may further comprise a power circuit 137 for delivering power from the power source 136 to various portions of the WD 110 that require power from the power source 136 to perform any functionality described or indicated herein. The power circuit 137 may comprise a power management circuit in certain embodiments. The power circuit 137 may additionally or alternatively be operable to receive power from an external power source, in which case the WD 110 may be connectable to an external power source (such as an electrical outlet) via an interface such as an input circuit or a power cable. The power circuit 137 may also be operable in certain embodiments to deliver power from the external power source to the power source 136. This may be for charging the power source 136, for example. Power circuitry 137 may perform any formatting, conversion, or other modification to the power from power source 136 to make it suitable for the respective components of WD 110 being powered.

[0083] FIG. 8 illustrates an embodiment of a UE according to various aspects described herein. As used herein, user equipment or UE may not necessarily have a user in the sense of a human user who owns and / or operates an associated device. Instead, a UE may represent a device (e.g., a smart sprinkler controller) that is intended for sale to or operation by a human user, but may not be associated with or may not initially be associated with a particular human user. Alternatively, a UE may represent a device (e.g., a smart power meter) that is not intended for sale to or operation by an end user, but may be associated with or operated for the benefit of a user. The UE 2200 may be any UE identified by the 3rd Generation Partnership Project (3GPP), including an NB-IoT UE, a machine-type communication (MTC) UE, and / or an enhanced MTC (eMTC) UE. As shown in Figure 8, UE 200 is an example of a WD configured to communicate according to one or more communications standards promulgated by the Third Generation Partnership Project (3GPP), such as 3GPP's GSM, UMTS, LTE, and / or 5G standards. As noted above, the terms WD and UE may be used interchangeably. Thus, although Figure 8 is a UE, the components described herein are equally applicable to a WD and vice versa.

[0084] In FIG. 8, UE 200 includes processing circuitry 201 operatively coupled to input / output interface 205, radio frequency (RF) interface 209, network connection interface 211, memory 215 including random access memory (RAM) 217, read only memory (ROM) 219, storage medium 221, etc., communication subsystem 231, power source 213, and / or any other components, or any combination thereof. Storage medium 221 includes operating system 223, application programs 225, and data 227. In other embodiments, storage medium 221 may include other similar types of information. Some UEs may utilize all of the components shown in FIG. 8 or only a subset of those components. The level of integration between components may vary from UE to UE. Additionally, a particular UE may include multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0085] In Fig. 8, the processing circuit 201 may be configured to process computer instructions and data. The processing circuit 201 may be configured to implement any sequential state machine operable to execute machine instructions stored in memory as a machine-readable computer program, such as one or more hardware-implemented state machines (e.g., in discrete logic, FPGA, ASIC, etc.), programmable logic with appropriate firmware, one or more pre-programmed, general-purpose processors, such as a microprocessor or digital signal processor (DSP) with appropriate software, or any combination of the above. For example, the processing circuit 201 may include two central processing units (CPUs). The data may be information in a format suitable for use by a computer.

[0086] In the illustrated embodiment, the input / output interface 205 may be configured to provide a communication interface to an input device, an output device, or an input / output device. The UE 200 may be configured to use an output device via the input / output interface 205. The output device may use the same type of interface port as the input device. For example, a USB port may be used to provide input to and output from the UE 200. The output device may be a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smart card, another output device, or any combination thereof. The UE 200 may be configured to enable a user to capture information to the UE 200 using an input device via the output interface 205. The input device may include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a webcam, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smart card, etc. The presence-sensitive display may include a capacitive or resistive touch sensor that senses input from the user. The sensor may be, for example, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, a light sensor, a proximity sensor, another like sensor, or any combination thereof. For example, the input device may be an accelerometer, a magnetometer, a digital camera, a microphone, and a light sensor.

[0087] In FIG. 8, the RF interface 209 may be configured to provide a communication interface to RF components, such as a transmitter, a receiver, and an antenna. The network connection interface 211 may be configured to provide a communication interface to a network 243a. The network 243a may encompass a wired and / or wireless network, such as a local area network (LAN), a wide area network (WAN), a computer network, a wireless network, a communication network, another similar network, or any combination thereof. For example, the network 243a may include a Wi-Fi network. The network connection interface 211 may be configured to include a receiver and a transmitter interface used to communicate with one or more other devices over a communication network according to one or more communication protocols, such as Ethernet, TCP / IP, SONET, ATM, etc. The network connection interface 211 may implement receiver and transmitter functions appropriate for a communication network link (e.g., optical, electrical, etc.). The transmitter and receiver functions may share circuit components, software or firmware, or may be realized separately.

[0088] RAM 217 may be configured to interface to processing circuit 201 via bus 202 for storing or caching data or computer instructions during execution of software programs, such as an operating system, application programs, and device drivers. ROM 219 may be configured to provide computer instructions or data to processing circuit 201. For example, ROM 219 may be configured to store unchanging low-level system code or data for basic system functions, such as basic input / output (I / O), booting, or receiving keystrokes from a keyboard, stored in non-volatile memory. Storage medium 221 may be configured to include memory, such as RAM, ROM, programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disk, optical disk, floppy disk, hard disk, removable cartridge, or flash drive. In one example, storage medium 221 may be configured to include an operating system 223, an application program 225, such as a web browser application, a widget or gadget engine, or another application, and data files 227. Storage medium 221 may store any of a wide variety of different operating systems or combinations of operating systems for use by UE 200.

[0089] The storage medium 221 may be configured to include multiple physical drive units, such as a redundant array of independent disks (RAID), floppy disk drive, flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high density digital versatile disk (HD-DVD) optical disk drive, internal hard disk drive, Blu-Ray optical disk drive, holographic digital data storage (HDDS) optical disk drive, external mini dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smart card memory such as a subscriber identity module or removable user identity (SIM / RUIM) module, other memory, or any combination thereof. The storage medium 221 may enable the UE 200 to access, offload data, or upload data stored in a temporary or non-transitory memory medium, computer executable instructions, application programs, and the like. An article of manufacture, such as an article of manufacture utilizing a communication system, may be tangibly embodied in the storage medium 221, which may include a device-readable medium.

[0090] In FIG. 8, the processing circuit 201 may be configured to communicate with the network 243b using the communication subsystem 231. The networks 243a and 243b may be the same network or networks or different networks or networks. The communication subsystem 231 may be configured to include one or more transceivers used to communicate with the network 243b. For example, the communication subsystem 231 may be configured to include one or more transceivers used to communicate with one or more remote transceivers of another device capable of wireless communication, such as another WD, UE, or base station of a radio access network (RAN), according to one or more communication protocols, such as IEEE 802.2, CDMA, WCDMA, GSM, LTE, UTRAN, WiMax, etc. Each transceiver may include a transmitter 233 and / or a receiver 235 for implementing a transmitter function or a receiver function, respectively, appropriate for the RAN link (e.g., frequency allocation, etc.). Furthermore, the transmitter 233 and the receiver 235 of each transceiver may share circuit components, software or firmware, or may be realized separately.

[0091] In an example embodiment, the communication capabilities of the communication subsystem 231 may include data communications, voice communications, multimedia communications, short-range communications such as Bluetooth, near-field communications, location-based communications such as using a global positioning system (GPS) to determine location, another similar communication capability, or any combination thereof. For example, the communication subsystem 231 may include cellular communications, Wi-Fi communications, Bluetooth communications, and GPS communications. The network 243b may encompass wired and / or wireless networks, such as a local area network (LAN), a wide area network (WAN), a computer network, a wireless network, a communications network, another similar network, or any combination thereof. For example, the network 243b may be a cellular network, a Wi-Fi network, and / or a near-field network. The power source 213 may be configured to provide alternating current (AC) or direct current (DC) power to the components of the UE 200.

[0092] The features, benefits and / or functions described herein may be implemented in one of the components of the UE 200 or distributed across multiple components of the UE 200. Furthermore, the features, benefits and / or functions described herein may be realized in any combination of hardware, software, or firmware. In one example, the communication subsystem 231 may be configured to include any of the components described herein. Furthermore, the processing circuitry 201 may be configured to communicate with any of such components through the bus 202. In another example, any of such components may be represented by program instructions stored in memory that, when executed by the processing circuitry 201, perform the corresponding functions described herein. In another example, the functionality of any of such components may be split between the processing circuitry 201 and the communication subsystem 231. In another example, non-computationally intensive functions of any of such components may be realized in software or firmware, and computationally intensive functions may be realized in hardware.

[0093] 9 is a schematic block diagram illustrating a virtualization environment 300 in which functions implemented by some embodiments may be virtualized. In this context, virtualization means creating a virtual version of an apparatus or device, which may include virtualizing a hardware platform, storage devices, and networking resources. As used herein, virtualization can apply to a node (e.g., a virtualized base station or a virtualized wireless access node) or to a device (e.g., a UE, a wireless device, or any other type of communication device) or components thereof, and relates to implementations that perform at least a portion of the functions as one or more virtual components (e.g., via one or more applications, components, functions, virtual machines, or containers running on one or more physical processing nodes in one or more networks).

[0094] In some embodiments, some or all of the functionality described herein may be implemented as virtual components executed by one or more virtual machines implemented in one or more virtual environments 300 hosted by one or more of the hardware nodes 330. Furthermore, in embodiments where the virtual nodes are not wireless access nodes or do not require wireless connectivity (e.g., core network nodes), the network nodes may be fully virtualized.

[0095] The functionality may be implemented by one or more applications 320 (which may alternatively be referred to as software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) operable to implement some of the features, functions, and / or benefits of some of the embodiments disclosed herein. The applications 320 execute in a virtualization environment 300 that provides hardware 330 including processing circuitry 360 and memory 390. The memory 390 includes instructions 395 that, upon execution by the processing circuitry 360, may cause the applications 320 to operate to provide one or more of the features, benefits, and / or functions disclosed herein.

[0096] The virtualization environment 300 includes a general-purpose or dedicated network hardware device 330 that includes a set of one or more processors or processing circuitry 360, which may be a commercial off-the-shelf (COTS) processor, a dedicated application-specific integrated circuit (ASIC), or any other type of processing circuitry including digital or analog hardware components or dedicated processors. Each hardware device may include memory 390-1, which may be a non-persistent memory for temporarily storing instructions 395 or software executed by the processing circuitry 360. Each hardware device may include one or more network interface controllers (NICs) 370, also known as network interface cards, that include a physical network interface 380. Each hardware device may also include a non-transitory, persistent, machine-readable storage medium 390-2, on which software 395 and / or instructions executable by the processing circuitry 360 are stored. Software 395 may include any type of software, including software to instantiate one or more virtualization layers 350 (also referred to as hypervisors), software to run virtual machines 340, and software that enables the software to perform the functions, features, and / or benefits described in connection with some of the embodiments described herein.

[0097] A virtual machine 340 may comprise virtual processing, virtual memory, virtual networking or interfaces, and virtual storage, and may be run by a corresponding virtualization layer 350 or hypervisor. Different embodiments of the virtual appliance 320 instance may be implemented in one or more of the virtual machines 340, and the implementation may be done in different ways.

[0098] During operation, processing circuitry 360 executes software 395 to instantiate a hypervisor or virtualization layer 350, sometimes referred to as a virtual machine monitor (VMM), which may present to virtual machine 340 a virtual operating platform that looks like networking hardware.

[0099] 9, the hardware 330 may be a standalone network node with general or specific components. The hardware 330 may include an antenna 3225 and may achieve some functionality through virtualization. Alternatively, the hardware 330 may be part of a larger cluster of hardware (e.g., in a data center or customer premises equipment (CPE)) where multiple hardware nodes work together and are managed through a management and orchestration (MANO) 3100 that oversees the lifecycle management of the application 320, among other things.

[0100] In some contexts, hardware virtualization is referred to as network functions virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry-standard high-volume server hardware, physical switches, and physical storage that may be located in data centers, as well as customer premises equipment.

[0101] In the context of NFV, a virtual machine 340 may be a software implementation of a physical machine that runs programs as if they were running on a physical, non-virtualized machine. A virtual machine 340 and the portion of hardware 330 on which it runs constitutes a separate Virtual Network Element (VNE), whether that hardware is dedicated to that virtual machine and / or hardware that the virtual machine shares with other virtual machines 340.

[0102] Further in the context of NFV, a Virtual Network Function (VNF) is responsible for handling a specific network function running in one or more virtual machines 340 on top of the hardware networking infrastructure 330 and corresponds to application 320 in FIG. 9.

[0103] In some embodiments, one or more radio units 3200, each including one or more transmitters 3220 and one or more receivers 3210, may be coupled to one or more antennas 3225. The radio units 3200 may communicate directly with the hardware node 330 via one or more appropriate network interfaces, or may be used in combination with virtualization components to provide a virtual node with wireless capabilities, such as a radio access node or base station.

[0104] In some embodiments, some signaling can be accomplished using a control system 3230, which may alternatively be used for communication between the hardware nodes 330 and the wireless unit 3200.

[0105] FIG. 10 illustrates a communication network connected to a host computer via an intermediate network, according to some embodiments. Referring to FIG. 10, according to one embodiment, a communication system includes a communication network 410, such as a 3GPP-type cellular network, comprising an access network 411, such as a wireless access network, and a core network 414. The access network 411 comprises a number of base stations 412a, 412b, 412c, such as NBs, eNBs, gNBs or other types of wireless access points, each defining a corresponding coverage area 413a, 413b, 413c. Each base station 412a, 412b, 412c can be connected to the core network 414 over a wired or wireless connection 415. A first UE 491 located in the coverage area 413c is configured to wirelessly connect to or be paged by the corresponding base station 412c. A second UE 492 in the coverage area 413a can be wirelessly connected to the corresponding base station 412a. In this example, multiple UEs 491, 492 are shown, however, the disclosed embodiments are equally applicable to situations where one UE is present in a coverage area or where one UE connects to a corresponding base station 412.

[0106] The communication network 410 itself is connected to a host computer 430, which may be embodied in hardware and / or software of a standalone, cloud-implemented, or distributed server, or as a processing resource in a server farm. The host computer 430 may be owned or controlled by a service provider, or may be operated by or on behalf of the service provider. The connections 421 and 422 between the communication network 410 and the host computer 430 may extend directly from the core network 414 to the host computer 430, or may extend through an optional intermediate network 420. The intermediate network 420 may be a combination of one or more of a public network, a private network, or a hosted network, if present, which may be a backbone network or the Internet, and in particular the intermediate network 420 may comprise two or more sub-networks (not shown).

[0107] The communication system of FIG. 10 as a whole enables connectivity between connected UEs 491, 492 and a host computer 430. The connectivity may be described as an over-the-top (OTT) connection 450. The host computer 430 and connected UEs 491, 492 are configured to communicate data and / or signaling via the OTT connection 450 using the access network 411, the core network 414, any intermediate network 420, and possible further infrastructure (not shown) as intermediaries. The OTT connection 450 may be transparent in the sense that the involved communication devices through which the OTT connection 450 passes are unaware of the routing of the uplink and downlink communications. For example, when data originating from the host computer 430 is forwarded (e.g., handed over) to the connected UE 491, the base station 412 may not be informed or need to be informed of the past routing of the incoming downlink communications. Similarly, the base station 412 does not need to be aware of the future routing of outbound uplink communications originating from the UE 491 towards the host computer 430.

[0108] FIG. 11 illustrates a generalized block diagram of a host computer communicating with user equipment via a base station over a partially wireless connection, according to some embodiments. In the communication system 500, the host computer 510 comprises hardware 515 including a communication interface 516 configured to set up and maintain wired or wireless connections with interfaces of different communication devices of the communication system 500. The host computer 510 further comprises a processing circuit 518, which may have storage and / or processing capabilities. In particular, the processing circuit 518 may comprise one or more programmable processors, application specific integrated circuits, field programmable gate arrays, or combinations thereof (not shown) adapted to execute instructions. The host computer 510 further comprises software 511 stored in or accessible by the host computer 510 and executable by the processing circuit 518. The software 511 includes a host application 512. The host application 512 may be operable to provide services to a remote user, such as a UE 530, connecting via an OTT connection 550 that terminates at the UE 530 and the host computer 510. In providing services to remote users, the host application 512 may provide user data that is transmitted using the OTT connection 550.

[0109] The communication system 500 further includes a base station 520 provided in the communication system, the base station 520 comprising hardware 525 enabling the base station 520 to communicate with the host computer 510 and the UE 530. The hardware 525 may include a communication interface 526 for setting up and maintaining wired or wireless connections with interfaces of different communication devices of the communication system 500, as well as a wireless interface 527 for setting up and maintaining at least a wireless connection 570 with a UE 530 located in a coverage area (not shown in FIG. 11 ) served by the base station 520. The communication interface 526 may be configured to facilitate a connection 560 to the host computer 510. The connection 560 may be direct, or the connection 560 may pass through a core network (not shown in FIG. 11 ) of the communication system and / or through one or more intermediate networks outside the communication system. In the embodiment shown, the hardware 525 of the base station 520 further includes processing circuitry 528, which may comprise one or more programmable processors, application specific integrated circuits, field programmable gate arrays, or combinations thereof (not shown) adapted to execute instructions. The base station 520 further includes software 521 stored internally or accessible via an external connection.

[0110] The communication system 500 further includes a UE 530, as previously described. The hardware 535 of the UE 530 may include a wireless interface 537 configured to establish and maintain a wireless connection 570 with a base station serving a coverage area in which the UE 530 is currently located. The hardware 535 of the UE 530 further includes a processing circuit 538, which may comprise one or more programmable processors, application specific integrated circuits, field programmable gate arrays, or combinations thereof (not shown) adapted to execute instructions. The UE 530 further includes software 531 stored in or accessible by the UE 530 and executable by the processing circuit 538. The software 531 includes a client application 532. The client application 532, with the support of the host computer 510, may be operable to provide services to a human or non-human user via the UE 530. At the host computer 510, an executing host application 512 may communicate with an executing client application 532 via an OTT connection 550 that terminates at the UE 530 and the host computer 510. In providing services to a user, the client application 532 may receive request data from the host application 512 and provide user data in response to the request data. The OTT connection 550 may carry both the request data and the user data. The client application 532 may interact with the user to generate the user data that it provides.

[0111] It should be noted that the host computer 510, base station 520, and UE 530 shown in Figure 11 may be similar or equivalent to the host computer 430, one of the base stations 412a, 412b, 412c, and one of the UEs 491, 492, respectively, of Figure 10. That is, the internal workings of these entities may be the same as the internal workings shown in Figure 11, and alternatively, the surrounding network topology may be the network topology of Figure 10.

[0112] 11, the OTT connection 550 is depicted abstractly to show communication between the host computer 510 and the UE 530 via the base station 520, without explicit reference to intermediary devices and the exact routing of messages through those devices. The network infrastructure may determine the routing, and the network infrastructure may be configured to hide the routing from the UE 530, or from the service provider that operates the host computer 510, or both. The network infrastructure may further make decisions while the OTT connection 550 is in effect that cause the network infrastructure to dynamically change the routing (e.g., based on load balancing considerations or network reconfiguration).

[0113] The wireless connection 570 between the UE 530 and the base station 520 follows the teachings of the embodiments described throughout this disclosure. One or more of the various embodiments improve the performance of the OTT service provided to the UE 530 using the OTT connection 550 of which the wireless connection 570 forms the last segment. More precisely, the teachings of these embodiments may improve power consumption, thereby providing benefits such as extended battery life.

[0114] A measurement procedure may be provided for the purpose of monitoring data rates, latency, and other factors that one or more embodiments improve upon. There may further be an optional network function for reconfiguring the OTT connection 550 between the host computer 510 and the UE 530 in response to variations in the measurement results. The measurement process and / or the network function for reconfiguring the OTT connection 550 may be implemented by the software 511 and hardware 515 of the host computer 510, or by the software 531 and hardware 535 of the UE 530, or both. In an embodiment, a sensor (not shown) may be deployed in or associated with the communication device through which the OTT connection 550 passes, and the sensor may participate in the measurement process by providing values ​​of the monitored quantities exemplified above, or values ​​of other physical quantities from which the software 511, 531 may calculate or estimate the monitored quantities. The reconfiguration of the OTT connection 550 may include message formats, retransmission settings, preferred routing, etc., and the reconfiguration need not affect the base station 520 and may be unknown or imperceptible to the base station 520. Such procedures and functionality are known and practiced in some cases in the art. In certain embodiments, the measurements may involve proprietary UE signaling that facilitates the host computer 510 measurements of throughput, propagation time, latency, etc. Measurements may be implemented in the software 511 and 531 in that they result in messages, particularly empty or "dummy" messages, being sent using the OTT connection 550 while the software 511 and 531 monitors propagation times, errors, etc.

[0115] FIG. 12 is a flow chart illustrating a method implemented in a communication system according to one embodiment. The communication system includes a host computer, a base station, and a UE, which may be as described with reference to FIG. 10 and FIG. 11. For simplicity of the disclosure, only a drawing reference to FIG. 12 is included in this section. In step 610, the host computer provides user data. In sub-step 611 (which may be optional) of step 610, the host computer provides the user data by executing a host application. In step 620, the host computer initiates a transmission conveying the user data to the UE. In step 630 (which may be optional), the base station transmits the user data conveyed in the host computer initiated transmission to the UE according to the teachings of the embodiments described throughout this disclosure. In step 640 (which may be further optional), the UE executes a client application associated with the host application executed by the host computer.

[0116] FIG. 13 is a flow chart illustrating a method implemented in a communication system according to one embodiment. The communication system includes a host computer, a base station, and a UE, which may be as described with reference to FIG. 10 and FIG. 11. For simplicity of the disclosure, only drawing reference to FIG. 13 is included in this section. In step 710 of the method, the host computer provides user data. In an optional sub-step (not shown), the host computer provides the user data by executing a host application. In step 720, the host computer initiates a transmission that conveys the user data to the UE. The transmission may go through a base station according to the teachings of the embodiments described throughout this disclosure. In step 730 (which may be optional), the UE receives the user data conveyed in the transmission.

[0117] FIG. 14 is a flow chart illustrating a method implemented in a communication system according to one embodiment. The communication system includes a host computer, a base station, and a UE, which may be as described with reference to FIG. 10 and FIG. 11. For simplicity of the disclosure, only drawing reference to FIG. 14 is included in this section. In step 810 (which may be optional), the UE receives input data provided by the host computer. Additionally or alternatively, in step 820, the UE provides user data. In sub-step 821 (which may be optional) of step 820, the UE provides the user data by executing a client application. In sub-step 811 (which may be optional) of step 810, the UE executes a client application that provides user data in response to the received input data provided by the host computer. In providing the user data, the executed client application may further take into account user input received from the user. Regardless of the particular manner in which the user data is provided, the UE begins transmitting the user data to the host computer in sub-step 830 (which may be optional). In step 840 of the method, the host computer receives user data transmitted from the UE according to the teachings of the embodiments described throughout this disclosure.

[0118] FIG. 15 is a flow chart illustrating a method implemented in a communication system according to one embodiment. The communication system includes a host computer, a base station, and a UE, which may be as described with reference to FIG. 10 and FIG. 11. For simplicity of the disclosure, only a drawing reference to FIG. 15 is included in this section. In step 910 (which may be optional), the base station receives user data from the UE according to the teachings of the embodiments described throughout this disclosure. In step 920 (which may be optional), the base station initiates transmission of the received user data to the host computer. In step 930 (which may be optional), the host computer receives the user data conveyed in the transmission initiated by the base station.

[0119] Any suitable step, method, feature, function, or benefit disclosed herein may be performed through one or more functional units or modules of one or more virtual devices. Each virtual device may comprise several of these functional units. These functional units may be implemented via processing circuitry, which may include one or more microprocessors or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), dedicated digital logic, and the like. The processing circuitry may be configured to execute program code stored in memory, which may include one or several types of memory, such as read-only memory (ROM), random access memory (RAM), cache memory, flash memory devices, optical storage devices, and the like. The program code stored in memory includes program instructions for executing one or more communication and / or data communication protocols as well as instructions for executing one or more of the techniques described herein. In some implementations, the processing circuitry may be used to cause each functional unit to perform a corresponding function according to one or more embodiments of the present disclosure.

[0120] FIG. 16 illustrates a method 1000 according to certain embodiments. In certain embodiments, the method may be performed by a wireless device, such as the WD 110 (e.g., UE 200) discussed above. For example, the wireless device may include a processing circuit 120 (e.g., processing circuit 201) configured to execute a computer program that causes the wireless device to perform the method. The method begins at step 1002, determining one or more measurements to perform, and proceeds to step 1004, performing the one or more measurements. In some embodiments, the one or more measurements to perform may depend on a measurement configuration stored at the wireless device, a measurement configuration received from the network, a current state / condition of the wireless device or the network, and / or whether one or more conditions for triggering activation of the measurement configuration have been met. Examples of measurements that may be performed by the wireless device are described with respect to the "Group A" embodiments below. In some embodiments, the method further includes performing an action of the wireless device based on the one or more measurements, such as performing a measurement report to the network.

[0121] FIG. 17 illustrates a schematic block diagram of a virtual device 1100 in a wireless network (e.g., the wireless network shown in FIG. 5). The virtual device may be implemented in a wireless device or a network node (e.g., the wireless device 110 or the network node 160 shown in FIG. 5). The virtual device 1100 is operable to perform the example method described with respect to FIG. 16, and possibly any other process or method disclosed herein. It should also be understood that the method of FIG. 16 is not necessarily performed solely by the virtual device 1100. At least some operations of the method may be performed by one or more other entities.

[0122] The virtual device 1100 may comprise a processing circuit, which may include one or more microprocessors or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), dedicated digital logic, and the like. The processing circuit may be configured to execute program code stored in a memory, which may include one or several types of memory, such as a read-only memory (ROM), a random access memory, a cache memory, a flash memory device, an optical storage device, and the like. The program code stored in the memory includes, in some embodiments, program instructions for executing one or more communication and / or data communication protocols, as well as instructions for implementing one or more of the techniques described herein. In some implementations, the processing circuit may be used to cause the configuration unit 1102 and the measurement unit 1104, as well as any other suitable units of the device 1100, to perform corresponding functions according to one or more embodiments of the present disclosure.

[0123] As shown in FIG. 17, the virtual device 1100 includes a configuration unit 1102 and a measurement unit 1104. The configuration unit 1102 is configured to determine a measurement configuration for the wireless device 110. The measurement configuration indicates measurements to be performed by the wireless device 110. Examples of types of measurements that may be performed by the wireless device 110 are described with respect to the Group A embodiments below. The measurement unit 1104 performs measurements configured by the configuration unit 1102. The measurement unit 1104 may use the measurements to perform operations of the wireless device 110. For example, in a particular embodiment, the measurement unit 1104 may perform measurement reports to the network.

[0124] FIG. 18 illustrates another method 1200 by a wireless device 110 according to some embodiments. In step 1202, the wireless device 110 determines whether one or more conditions for triggering a measurement have occurred. In step 1204, the wireless device 110 performs one or more measurements based on the occurrence of the one or more conditions. In a particular embodiment, the one or more conditions for triggering a measurement are based on at least one of a timing advance value in the source cell, a distance between the wireless device and a satellite node serving the source cell or a candidate target cell, a predicted time that the wireless device will be served in the source cell and / or the candidate target cell, an elevation angle of the satellite node serving the source cell and / or the candidate target cell, reaching a time point set by a network node, detection of an identifier associated with a particular cell, and a speed or velocity of the wireless device.

[0125] In a particular embodiment, the wireless device 110 determines whether to trigger a measurement report to the network based on whether one or more measurements satisfy one or more reporting conditions.

[0126] In another particular embodiment, the wireless device 110 transmits the measurement report to the network node.

[0127] In certain embodiments, taking the one or more measurements is based at least in part on a measurement configuration received from the network.

[0128] In a particular embodiment, at least one of the measurements is indicative of a channel quality associated with the source cell or the candidate target cell, and the one or more measurements indicative of the channel quality include an RSRP, an RSRQ, a SINR, or an RSSI measurement.

[0129] In a particular embodiment, the at least one measurement is indicative of a path loss associated with a source cell.

[0130] In a particular embodiment, at least one of the measurements is indicative of a location of the wireless device 110 .

[0131] In a particular embodiment, at least one of the measurements indicates a distance or differential delay between the wireless device 110 and a reference point, the reference point corresponding to the nadir of a satellite node serving the source cell and / or a candidate target cell.

[0132] In a particular embodiment, the wireless device 110 receives information indicative of the reference point from the network node 160 via common or dedicated signaling.

[0133] In certain embodiments, at least one of the measurements indicates a derivative of the distance or differential delay.

[0134] FIG. 19 illustrates a schematic block diagram of a virtual device 1300 in a wireless network (e.g., the wireless network shown in FIG. 5). The device may be implemented in a wireless device or a network node (e.g., the wireless device 110 or the network node 160 shown in FIG. 5). The virtual device 1300 is operable to perform the example method described with respect to FIG. 18, and possibly any other process or method disclosed herein. It should also be understood that the method of FIG. 18 is not necessarily performed solely by the virtual device 1300. At least some operations of the method may be performed by one or more other entities.

[0135] The virtual device 1300 may comprise a processing circuit, which may include one or more microprocessors or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), dedicated digital logic, and the like. The processing circuit may be configured to execute program code stored in a memory, which may include one or several types of memory, such as a read-only memory (ROM), a random access memory, a cache memory, a flash memory device, an optical storage device, and the like. The program code stored in the memory, in some embodiments, includes program instructions for executing one or more communication and / or data communication protocols, as well as instructions for implementing one or more of the techniques described herein. In some implementations, the processing circuit may be used to cause the decision unit 1302, the trigger unit 1304, and any other suitable units of the virtual device 1300 to perform corresponding functions according to one or more embodiments of the present disclosure.

[0136] According to some embodiments, the determining unit 1302 may perform some of the determining functions of the virtual device 1300. For example, the determining unit 1302 may determine whether one or more conditions for triggering a measurement have occurred. In a particular embodiment, the one or more conditions for triggering a measurement are based on at least one of a timing advance value in the source cell, a distance between the wireless device and a satellite node serving the source cell or a candidate target cell, a predicted time that the wireless device will be served in the source cell and / or the candidate target cell, an elevation angle of the satellite node serving the source cell and / or the candidate target cell, reaching a time point set by the network node 160, detection of an identifier associated with a particular cell, and a speed or velocity of the wireless device.

[0137] According to some embodiments, the trigger unit 1304 may perform some of the trigger functions of the virtual device 1300. For example, the trigger unit 1304 may perform one or more measurements based on the occurrence of one or more conditions.

[0138] FIG. 20 illustrates a method 1400 by a network node 160, e.g., a base station, according to a particular embodiment. In step 1402, the network node 160 transmits to the wireless device 110 a measurement configuration including one or more conditions for triggering a measurement. In step 1404, the network node 160 receives a measurement report from the wireless device 110 based on the measurement configuration. According to a particular embodiment, the one or more conditions for triggering a measurement are based on at least one of a timing advance value in the source cell, a distance between the wireless device 110 and a satellite node serving the source cell or a candidate target cell, a predicted time that the wireless device 110 will be served in the source cell and / or the candidate target cell, an elevation angle of a satellite serving the source cell and / or the candidate target cell, reaching a time point configured by the network node, detection of an identifier associated with a particular cell, and a speed or velocity of the wireless device.

[0139] In a particular embodiment, the measurement configuration indicates one or more measurements to be taken by the wireless device 110 .

[0140] In a particular embodiment, the one or more conditions indicate when the wireless device 110 should activate the measurement configuration.

[0141] In a particular embodiment, the measurement report indicates the channel quality that the wireless device 110 associates with the source cell or the candidate target cell, where the channel quality includes an RSRP, RSRQ, SINR, or RSSI measurement.

[0142] In a particular embodiment, the measurement report indicates a path loss that the wireless device 110 associates with a source cell or a candidate target cell.

[0143] In a particular embodiment, the measurement report indicates the location of the wireless device 110 .

[0144] In a particular embodiment, the measurement report indicates the distance or differential delay between the wireless device 110 and a reference point, where the reference point corresponds to the nadir of a satellite node serving the source cell and / or the candidate target cell.

[0145] In a particular embodiment, the network node 160 transmits information indicating the reference point to the wireless device 110 via common or dedicated signaling.

[0146] In certain embodiments, the measurement report indicates the derivative of the distance or differential delay.

[0147] FIG. 21 illustrates a schematic block diagram of a virtual device 1500 in a wireless network (e.g., the wireless network shown in FIG. 5). The virtual device may be implemented in a wireless device or a network node (e.g., the wireless device 110 or the network node 160 shown in FIG. 5). The virtual device 1500 is operable to perform the example method described with respect to FIG. 20, and possibly any other process or method disclosed herein. It should also be understood that the method of FIG. 20 is not necessarily performed solely by the virtual device 1500. At least some operations of the method may be performed by one or more other entities.

[0148] The virtual device 1500 may comprise a processing circuit, which may include one or more microprocessors or microcontrollers, as well as other digital hardware, which may include digital signal processors (DSPs), dedicated digital logic, and the like. The processing circuit may be configured to execute program code stored in a memory, which may include one or several types of memory, such as a read-only memory (ROM), a random access memory, a cache memory, a flash memory device, an optical storage device, and the like. The program code stored in the memory, in some embodiments, includes program instructions for executing one or more communication and / or data communication protocols, as well as instructions for implementing one or more of the techniques described herein. In some implementations, the processing circuit may be used to cause the transmitting unit 1502, the receiving unit 1504, and any other suitable units of the virtual device 1500 to perform corresponding functions according to one or more embodiments of the present disclosure.

[0149] According to some embodiments, the transmitting unit 1502 may perform some of the transmitting functions of the virtual device 1500. For example, the transmitting unit 1502 may transmit to the wireless device 110 a measurement configuration including one or more conditions for triggering a measurement. According to a particular embodiment, the one or more conditions for triggering a measurement are based on at least one of a timing advance value in the source cell, a distance between the wireless device 110 and a satellite node serving the source cell or a candidate target cell, a predicted time that the wireless device 110 will be served in the source cell and / or the candidate target cell, an elevation angle of a satellite serving the source cell and / or the candidate target cell, reaching a time point configured by a network node, and detection of an identifier associated with a particular cell.

[0150] According to some embodiments, the receiving unit 1504 may implement some of the receiving functions of the virtual device 1500. For example, the receiving unit 1504 may receive measurement reports from the wireless device 110 based on a measurement configuration.

[0151] As used herein, the term unit may have its usual meaning in the field of electronics, electrical devices, and / or electronic devices and may include, for example, electric and / or electronic circuits, devices, modules, processors, memories, logical solid and / or discrete devices, computer programs or instructions, etc., for performing a respective task, procedure, computation, output, and / or display function, such as those described herein.

[0152] In some embodiments, a computer program, computer program product, or computer readable storage medium comprises instructions that, when executed on a computer, perform any of the embodiments disclosed herein. In a further example, instructions are carried on a signal or carrier that is executable on a computer and, when executed, performs any of the embodiments disclosed herein.

[0153] Exemplary embodiments Group A Embodiments Exemplary embodiment 1 A method implemented by a wireless device, the method including performing one or more measurements.

[0154] Exemplary Embodiment 2 The method of embodiment 1, further comprising: performing an operation on the wireless device based on the one or more measurements.

[0155] Exemplary Embodiment 3 The method of embodiment 2, wherein the operation of the wireless device includes determining whether to trigger a measurement report to the network based on whether the one or more measurements satisfy one or more conditions.

[0156] Exemplary Embodiment 4 The method of embodiment 2 or 3, wherein the operation further includes sending the measurement report to the network.

[0157] Exemplary Embodiment 5. The method of any one of embodiments 1 to 4, wherein taking one or more measurements is based at least in part on a measurement configuration received from a network.

[0158] Exemplary Embodiment 6 The method of any one of embodiments 1 to 5, wherein at least one of the measurements indicates a channel quality associated with a source cell or a candidate target cell.

[0159] Exemplary Embodiment 7. The method of embodiment 6, wherein the measurement indicative of channel quality includes an RSRP, an RSRQ, an SINR, or an RSSI measurement.

[0160] Exemplary Embodiment 8. The method of any one of embodiments 1 to 7, wherein the at least one measurement indicates a path loss associated with a source cell or a candidate target cell.

[0161] Exemplary Embodiment 9. The method of any one of embodiments 1 to 8, wherein at least one of the measurements is indicative of a location of the wireless device.

[0162] Exemplary embodiment 10. The method of embodiment 9, wherein the location includes geographic coordinates.

[0163] Exemplary Embodiment 11. The method of any one of embodiments 1 to 10, wherein at least one of the measurements is indicative of a speed or velocity of the wireless device.

[0164] Exemplary Embodiment 12. The method of any one of embodiments 1-11, wherein at least one of the measurements indicates a distance between the wireless device and a satellite node serving the source cell or a candidate target cell.

[0165] Exemplary Embodiment 13. The method of embodiment 12, wherein the distance is based on the position of the satellite node as known from the ephemeris data.

[0166] Exemplary Embodiment 14. The method of embodiment 12 or 13, wherein the distance is determined based on a reference point associated with the satellite node.

[0167] Exemplary Embodiment 15. The method of any one of embodiments 1-14, wherein at least one of the measurements indicates a distance or a differential delay between the wireless device and a reference point.

[0168] Exemplary Embodiment 16. The method of embodiment 15, wherein the reference point corresponds to the nadir of a satellite node serving the source cell and / or the candidate target cell.

[0169] Exemplary Embodiment 17. The method of embodiment 15 or 16, further comprising receiving information indicating the reference point via common or dedicated signaling from the network.

[0170] Exemplary Embodiment 18. The method of any one of embodiments 1 to 17, wherein at least one of the measurements indicates a derivative of a distance or a differential delay. (For example, examples of distance or differential delay are described with respect to embodiments 12 to 17.)

[0171] Exemplary Embodiment 19. The method of any one of embodiments 1-18, wherein at least one of the measurements indicates an expected time that the wireless device will be served in the source cell or the candidate target cell.

[0172] Exemplary Embodiment 20. The method of any one of embodiments 1-19, wherein at least one of the measurements indicates an elevation angle of a satellite serving the source cell or a candidate target cell.

[0173] Exemplary Embodiment 21 The method of any one of embodiments 1 to 20, wherein at least one of the measurements indicates a derivative of an elevation angle of a satellite serving the source cell or a candidate target cell.

[0174] Exemplary Embodiment 22 The method of any one of embodiments 1 to 21, wherein at least one of the measurements indicates a timing advance value in the source cell and / or the candidate target cell.

[0175] Exemplary Embodiment 23. The method of embodiment 22, wherein the wireless device is provided with an estimation accuracy of the TA value.

[0176] Exemplary Embodiment 24. The method of embodiment 23, wherein the estimation accuracy of the TA value is based on the number of satellites used to estimate the TA.

[0177] Exemplary Embodiment 25. The method of any one of the preceding embodiments, further comprising providing user data and forwarding the user data to the host computer via transmission to the base station.

[0178] Group B Embodiments Exemplary embodiment 26. A method implemented by a network node, the method including receiving a measurement report from a wireless device and performing a network node action based on the measurement report.

[0179] Exemplary Embodiment 27. The method of embodiment 26, further comprising: determining a measurement configuration including one or more measurements to be performed by the wireless device; and transmitting the measurement configuration to the wireless device.

[0180] Exemplary Embodiment 28. The method of embodiment 27, further comprising indicating to the wireless device one or more conditions in response that the wireless device should activate the measurement configuration.

[0181] Exemplary Embodiment 29. The method of any one of embodiments 26-28, wherein the measurement report indicates a channel quality that the wireless device associates with the source cell or the candidate target cell.

[0182] Exemplary embodiment 30. The method of embodiment 29, wherein the channel quality includes an RSRP, an RSRQ, an SINR, or an RSSI measurement.

[0183] Exemplary Embodiment 31 The method of any one of embodiments 26-30, wherein the measurement report indicates a path loss that the wireless device associates with a source cell or a candidate target cell.

[0184] Exemplary embodiment 32. The method of any one of embodiments 26-31, wherein the measurement report indicates a location of the wireless device.

[0185] Exemplary embodiment 33. The method of embodiment 32, wherein the location includes geographic coordinates.

[0186] Exemplary Embodiment 34. The method of any one of embodiments 26-33, wherein the measurement report indicates a speed or velocity of the wireless device.

[0187] Exemplary Embodiment 35. The method of any one of embodiments 26-34, wherein the measurement report indicates a distance between the wireless device and a satellite node serving the source cell or a candidate target cell.

[0188] Exemplary Embodiment 36. The method of embodiment 35, wherein the distance is based on the position of the satellite node as known to the wireless device from ephemeris data.

[0189] Exemplary Embodiment 37. The method of embodiment 35 or 36, wherein the distance is determined by the wireless device based on a reference point associated with the satellite node.

[0190] Exemplary Embodiment 38. The method of any one of embodiments 26-37, wherein the measurement report indicates a distance or a differential delay between the wireless device and a reference point.

[0191] Exemplary Embodiment 39. The method of embodiment 38, wherein the reference point corresponds to the nadir of a satellite node serving the source cell and / or the candidate target cell.

[0192] Exemplary embodiment 40. The method of embodiment 38 or 39, further comprising transmitting information indicative of the reference point to the wireless device via common or dedicated signaling.

[0193] The method of any one of embodiments 26 to 40, wherein the measurement report indicates a derivative of the distance or differential delay. (For example, examples of distance or differential delay are described with respect to embodiments 35 to 40.)

[0194] Exemplary Embodiment 42. The method of any one of embodiments 26-41, wherein the measurement report indicates an expected time that the wireless device will be served in the source cell or the candidate target cell.

[0195] Exemplary Embodiment 43. The method of any one of embodiments 26-42, wherein the measurement report indicates an elevation angle of a satellite serving the source cell or the candidate target cell.

[0196] Exemplary Embodiment 44. The method of any one of embodiments 26-43, wherein the measurement report indicates a derivative of an elevation angle of a satellite serving the source cell or the candidate target cell.

[0197] Exemplary Embodiment 45. The method of any one of embodiments 26-44, wherein the measurement report indicates a timing advance value in the source cell and / or the candidate target cell.

[0198] Exemplary Embodiment 46. The method of embodiment 45, further comprising transmitting the estimated accuracy of the TA value to the wireless device.

[0199] Exemplary Embodiment 47 The method of embodiment 46, wherein the estimation accuracy of the TA value is based on the number of satellites used to estimate the TA.

[0200] Exemplary Embodiment 48. The method of any one of the preceding embodiments, further comprising obtaining user data and transferring the user data to a host computer or wireless device.

[0201] Group C Embodiments Exemplary Embodiment 49. A wireless device comprising: a processing circuit configured to perform any of the steps in any one of the embodiments of group A; and a power supply circuit configured to supply power to the wireless device.

[0202] Exemplary Embodiment 50 A base station comprising a processing circuit configured to perform any of the steps of any of the Group B embodiments, and a power supply circuit configured to supply power to the base station.

[0203] Exemplary embodiment 51. A user equipment (UE) comprising: an antenna configured to send and receive wireless signals; a radio front-end circuit connected to the antenna and a processing circuit and configured to condition signals communicated between the antenna and the processing circuit, the processing circuit configured to perform any of the steps of any one of the embodiments of group A; an input interface connected to the processing circuit and configured to enable input of information to the UE to be processed by the processing circuit; an output interface connected to the processing circuit and configured to output information from the UE that has been processed by the processing circuit; and a battery connected to the processing circuit and configured to provide power to the UE.

[0204] EXEMPLARY EMBODIMENT 52 A computer program comprising instructions for performing any of the steps of any one of the embodiments of group A when the computer program is executed on a computer.

[0205] EXEMPLARY EMBODIMENT 53 A computer program product comprising a computer program, the computer program comprising instructions for performing any of the steps of any one of the embodiments of group A when the computer program is executed on a computer.

[0206] EXEMPLARY EMBODIMENT 54. A non-transitory computer-readable storage medium or carrier comprising a computer program, the computer program comprising instructions for performing any of the steps of any one of the embodiments of Group A when the computer program is executed on a computer.

[0207] EXEMPLARY EMBODIMENT 55 A computer program comprising instructions for performing any of the steps of any one of the embodiments of group B when executed on a computer.

[0208] EXEMPLARY EMBODIMENT 56 A computer program product comprising a computer program, the computer program comprising instructions for performing any of the steps of any one of the embodiments of Group B when the computer program is executed on a computer.

[0209] EXEMPLARY EMBODIMENT 57 A non-transitory computer-readable storage medium or carrier comprising a computer program, the computer program comprising instructions for performing any of the steps of any one of the embodiments of Group B when executed on a computer.

[0210] Exemplary embodiment 58. A communications system including a host computer, the host computer comprising a processing circuit configured to provide user data and a communications interface configured to forward the user data to a cellular network for transmission to a user equipment (UE), the cellular network comprising a base station having a radio interface and a processing circuit, the processing circuit of the base station configured to perform any of the steps of any one of the Group B embodiments.

[0211] EXEMPLARY EMBODIMENT 59 The communication system of the immediately preceding embodiment further comprising a base station.

[0212] Exemplary embodiment 60. The communication system of the preceding two embodiments, further comprising a UE, the UE being configured to communicate with the base station.

[0213] Exemplary Embodiment 61. The communications system of any three preceding embodiments, wherein the processing circuitry of the host computer is configured to execute a host application and thereby provide user data, and the UE comprises processing circuitry configured to execute a client application associated with the host application.

[0214] Exemplary embodiment 62. A method implemented in a communication system including a host computer, a base station, and a user equipment (UE), the method including: providing user data at the host computer; and initiating a transmission at the host computer conveying the user data to the UE via a cellular network including the base station, the base station performing any of the steps of any one of the Group B embodiments.

[0215] Exemplary embodiment 63. The method of the immediately preceding embodiment, further comprising transmitting, at the base station, user data.

[0216] Exemplary Embodiment 64 The method of the preceding two embodiments, wherein the user data is provided by executing a host application at the host computer, and the method further includes executing, at the UE, a client application associated with the host application.

[0217] EXEMPLARY EMBODIMENT 65 A user equipment (UE) configured to communicate with a base station, the UE comprising a radio interface and processing circuitry configured to implement any of the preceding three embodiments.

[0218] Exemplary embodiment 66. A communications system including a host computer, the host computer comprising a processing circuit configured to provide user data and a communications interface configured to forward the user data to a cellular network for transmission to a user equipment (UE), the UE comprising a wireless interface and a processing circuit, the components of the UE being configured to perform any of the steps of any one of the embodiments of group A.

[0219] Exemplary Embodiment 67. The communication system of the immediately preceding embodiment, wherein the cellular network further includes a base station configured to communicate with the UE.

[0220] EXEMPLARY EMBODIMENT 68. The communications system of the two preceding embodiments, wherein the processing circuitry of the host computer is configured to execute a host application and thereby provide user data, and the processing circuitry of the UE is configured to execute a client application associated with the host application.

[0221] Exemplary embodiment 69. A method implemented in a communication system including a host computer, a base station, and a user equipment (UE), comprising: providing user data at the host computer; and initiating a transmission at the host computer to convey the user data to the UE via a cellular network including the base station, wherein the UE performs any of the steps in any one of the embodiments of group A.

[0222] Exemplary embodiment 70. The method of the immediately preceding embodiment, further comprising receiving, at the UE, user data from the base station.

[0223] Exemplary embodiment 71. A communications system including a host computer having a communications interface configured to receive user data originating from a transmission from a user equipment (UE) to a base station, the UE having a wireless interface and processing circuitry, the processing circuitry of the UE configured to perform any of the steps in any one of the embodiments of group A.

[0224] Example Embodiment 72 The communication system of the immediately preceding embodiment, further comprising a UE.

[0225] Exemplary embodiment 73 The communication system of the two preceding embodiments, further including a base station, the base station comprising a wireless interface configured to communicate with the UE, and a communication interface configured to forward user data conveyed by transmission from the UE to the base station to a host computer.

[0226] EXEMPLARY EMBODIMENT 74. The communications system of any three preceding embodiments, wherein the processing circuitry of the host computer is configured to execute a host application and the processing circuitry of the UE is configured to execute a client application associated with the host application and thereby provide user data.

[0227] EXEMPLARY EMBODIMENT 75. The communications system of any of the preceding four embodiments, wherein the processing circuitry of the host computer is configured to execute a host application and thereby provide requested data, and the processing circuitry of the UE is configured to execute a client application associated with the host application and thereby provide user data in response to the requested data.

[0228] Exemplary embodiment 76. A method implemented in a communication system including a host computer, a base station, and a user equipment (UE), the method including receiving, at the host computer, user data transmitted from the UE to the base station, the UE performing any of the steps of any one of the embodiments of group A.

[0229] Example Embodiment 77. The method of the immediately preceding embodiment, further comprising: providing, at the UE, user data to the base station.

[0230] Exemplary embodiment 78 The method of the two preceding embodiments, further comprising: executing, at the UE, a client application, thereby providing user data to be transmitted; and executing, at the host computer, a host application associated with the client application.

[0231] Exemplary Embodiment 79 The method of the preceding three embodiments, further including: executing, at the UE, a client application; and receiving, at the UE, input data for the client application, the input data being provided at the host computer by executing a host application associated with the client application, and the user data to be transmitted being provided by the client application in response to the input data.

[0232] Exemplary embodiment 80. A communications system including a host computer having a communications interface configured to receive user data resulting from a transmission from a user equipment (UE) to a base station, the base station having a wireless interface and processing circuitry, the processing circuitry of the base station configured to perform any of the steps of any one of the Group B embodiments.

[0233] Exemplary Embodiment 81 The communication system of the immediately preceding embodiment, further comprising a base station.

[0234] Exemplary embodiment 82. The communication system of the preceding two embodiments, further comprising a UE, the UE being configured to communicate with the base station.

[0235] Exemplary Embodiment 83. The communications system of any three preceding embodiments, wherein the processing circuitry of the host computer is configured to execute a host application, and the UE is configured to execute a client application associated with the host application, thereby providing user data for reception by the host computer.

[0236] Exemplary embodiment 84. A method implemented in a communications system including a host computer, a base station, and a user equipment (UE), the method including receiving, at the host computer, from the base station, user data originating from a transmission received by the base station from the UE, the UE performing any of the steps of any one of the embodiments of group A.

[0237] Exemplary embodiment 85. The method of the immediately preceding embodiment, further comprising receiving, at the base station, user data from the UE.

[0238] Exemplary Embodiment 86 The method of the preceding two embodiments, further comprising initiating, at the base station, a transmission of the received user data to the host computer.

Claims

1. A method (1200) implemented by a wireless device (110), comprising: Determining 1202 whether one or more conditions for triggering a measurement have occurred; making one or more measurements based on the occurrence of the one or more conditions (1204), at least one of the measurements being indicative of a derivative of a differential delay; The one or more conditions for triggering a measurement include: The timing advance value in the source cell, the distance between the wireless device and a satellite node serving a source cell or a candidate target cell; an expected time that the wireless device will be served in the source cell and / or the candidate target cell; elevation angles of the satellite nodes serving the source cell and / or the candidate target cells; a time point set by the network node (160) has been reached; Finding an identifier associated with a particular cell; and The speed or rate of said wireless device The method is based on at least one of the following:

2. The method of claim 1 , further comprising: determining whether to trigger a measurement report to the network node based on whether the one or more measurements satisfy one or more reporting conditions.

3. The method of claim 2 , further comprising: transmitting a measurement report to the network node.

4. 4. The method of claim 1, wherein the performing of the one or more measurements is based at least in part on a measurement configuration received from the network node.

5. 5. The method of claim 1, wherein at least one of the measurements is indicative of a channel quality associated with a source cell or a candidate target cell, and the one or more measurements indicative of channel quality include a reference signal received power, a reference signal received quality, a signal to interference and noise ratio, or a reference signal strength indicator measurement.

6. The method of claim 1 , wherein at least one measurement is indicative of a path loss associated with a source cell.

7. The method of claim 1 , wherein at least one of the measurements is indicative of a location of the wireless device.

8. 8. The method of claim 1, wherein at least one of the measurements indicates a distance or differential delay between the wireless device and a reference point, the reference point corresponding to the nadir of a satellite node serving the source cell and / or a candidate target cell.

9. 9. The method of claim 8, further comprising receiving information from the network node indicating the reference point via common or dedicated signaling.

10. A method (1400) implemented by a network node (160), comprising: Sending (1402) a measurement configuration to a wireless device (110) including one or more conditions for triggering a measurement; and receiving a measurement report from the wireless device based on the measurement configuration (1404), the measurement report indicating a derivative of a differential delay, the one or more conditions for triggering a measurement including: The timing advance value in the source cell, the distance between the wireless device and a satellite node serving a source cell or a candidate target cell; an expected time that the wireless device will be served in a source cell and / or a candidate target cell; elevation angles of the satellite nodes serving source and / or candidate target cells; a time point set by said network node has been reached; Finding an identifier associated with a particular cell; and The speed or rate of said wireless device The method is based on at least one of the following:

11. The method of claim 10 , wherein the measurement configuration is indicative of the one or more measurements to be performed by the wireless device.

12. The method of claim 10 or 11, wherein the one or more conditions indicate when the wireless device should activate the measurement configuration.

13. 13. The method of claim 10, wherein the measurement report indicates a channel quality that the wireless device associates with a source cell or a candidate target cell, the channel quality comprising a reference signal received power, a reference signal received quality, a signal to interference and noise ratio, or a reference signal strength indicator measurement.

14. The method of claim 10 , wherein the measurement report indicates a path loss that the wireless device associates with a source cell or a candidate target cell.

15. The method of claim 10 , wherein the measurement report indicates a location of the wireless device.

16. 16. The method of claim 10, wherein the measurement report indicates a distance or differential delay between the wireless device and a reference point, the reference point corresponding to the nadir of a satellite node serving the source cell and / or a candidate target cell.

17. 17. The method of claim 16, further comprising transmitting information indicative of the reference point to the wireless device via common or dedicated signaling.

18. A wireless device (110), determining whether one or more conditions for triggering a measurement have occurred; performing one or more measurements based on the occurrence of the one or more conditions, at least one of the measurements being indicative of a derivative of a differential delay; The one or more conditions for triggering a measurement include: The timing advance value in the source cell, the distance between the wireless device and a satellite node serving a source cell or a candidate target cell; an expected time that the wireless device will be served in a source cell and / or a candidate target cell; elevation angles of the satellite nodes serving source and / or candidate target cells; a time point set by the network node (160) has been reached; Finding an identifier associated with a particular cell; and The speed or rate of said wireless device The wireless device is based on at least one of the following:

19. 20. The wireless device of claim 18, further adapted to determine whether to trigger a measurement report to the network node based on whether the one or more measurements satisfy one or more reporting conditions.

20. 20. The wireless device of claim 19, further adapted to transmit measurement reports to the network node.

21. 21. The wireless device of claim 18, wherein performing the one or more measurements is based at least in part on a measurement configuration received from the network node.

22. 22. The wireless device of claim 18, wherein at least one of the measurements is indicative of a channel quality associated with a source cell or a candidate target cell, and the one or more measurements indicative of channel quality include a reference signal received power, a reference signal received quality, a signal to interference and noise ratio, or a reference signal strength indicator measurement.

23. 23. The wireless device of claim 18, wherein at least one measurement is indicative of a path loss associated with a source cell.

24. 24. A wireless device according to any one of claims 18 to 23, wherein at least one of the measurements is indicative of a location of the wireless device.

25. 25. A wireless device according to claim 18, wherein at least one of the measurements indicates a distance or differential delay between the wireless device and a reference point, the reference point corresponding to the nadir of a satellite node serving the source cell and / or a candidate target cell.

26. 26. The wireless device of claim 25, further adapted to receive information from the network node indicating the reference point via common or dedicated signaling.

27. A network node (160), sending a measurement configuration to a wireless device (110) including one or more conditions for triggering a measurement; and receiving a measurement report from a wireless device based on the measurement configuration, the measurement report indicating a derivative of a differential delay, and the one or more conditions for triggering a measurement include: The timing advance value in the source cell, the distance between the wireless device and a satellite node serving a source cell or a candidate target cell; an expected time that the wireless device will be served in a source cell and / or a candidate target cell; elevation angles of said satellites serving the source cell and / or the candidate target cell; a time point set by said network node has been reached; Finding an identifier associated with a particular cell; and The speed or rate of said wireless device The network node is based on at least one of the following:

28. 28. The network node of claim 27, wherein the measurement configuration indicates the one or more measurements to be performed by the wireless device.

29. 29. A network node according to claim 27 or 28, wherein the one or more conditions indicate when the wireless device should activate the measurement configuration.

30. 30. The network node of claim 27, wherein the measurement report indicates a channel quality that the wireless device associates with a source cell or a candidate target cell, the channel quality comprising a reference signal received power, a reference signal received quality, a signal to interference and noise ratio, or a reference signal strength indicator measurement.

31. 31. A network node according to any one of claims 27 to 30, wherein the measurement report indicates a path loss that a wireless device associates with a source cell or a candidate target cell.

32. 32. A network node according to any one of claims 27 to 31, wherein the measurement report is indicative of a position of the wireless device.

33. 33. A network node according to any one of claims 27 to 32, wherein the measurement report indicates a distance or differential delay between the wireless device and a reference point, the reference point corresponding to the nadir of a satellite node serving the source cell and / or a candidate target cell.

34. 34. The network node of claim 33, further adapted to transmit information indicative of the reference point to the wireless device via common or dedicated signaling.

Images