[go: up one dir, main page]

WO2025177172A1 - Modification d'avance temporelle pour réseaux non terrestres - Google Patents

Modification d'avance temporelle pour réseaux non terrestres

Info

Publication number
WO2025177172A1
WO2025177172A1 PCT/IB2025/051786 IB2025051786W WO2025177172A1 WO 2025177172 A1 WO2025177172 A1 WO 2025177172A1 IB 2025051786 W IB2025051786 W IB 2025051786W WO 2025177172 A1 WO2025177172 A1 WO 2025177172A1
Authority
WO
WIPO (PCT)
Prior art keywords
value
wireless device
position estimate
satellite
timing adjustment
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
PCT/IB2025/051786
Other languages
English (en)
Inventor
Johan Rune
Zhang Zhang
Ignacio Javier PASCUAL PELAYO
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Telefonaktiebolaget LM Ericsson AB
Original Assignee
Telefonaktiebolaget LM Ericsson AB
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Telefonaktiebolaget LM Ericsson AB filed Critical Telefonaktiebolaget LM Ericsson AB
Publication of WO2025177172A1 publication Critical patent/WO2025177172A1/fr
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W56/00—Synchronisation arrangements
    • H04W56/004—Synchronisation arrangements compensating for timing error of reception due to propagation delay
    • H04W56/0045—Synchronisation arrangements compensating for timing error of reception due to propagation delay compensating for timing error by altering transmission time
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04B—TRANSMISSION
    • H04B7/00—Radio transmission systems, i.e. using radiation field
    • H04B7/14—Relay systems
    • H04B7/15—Active relay systems
    • H04B7/185—Space-based or airborne stations; Stations for satellite systems
    • H04B7/1851—Systems using a satellite or space-based relay
    • H04B7/18513—Transmission in a satellite or space-based system

Definitions

  • EPS Evolved Packet System
  • LTE Long-Term Evolution
  • EPC Evolved Packet Core
  • 3GPP Release 13 narrowband Internet-of-things (NB-IoT) and LTE for machines (LTE-M) are part of the LTE specifications and provide connectivity to massive machine type communications (mMTC) services.
  • 3GPP Release 15 specified the first release of the 5G system (5GS). This is a new generation radio access technology intended to serve use cases such as enhanced mobile broadband (eMBB), ultra-reliable and low latency communication (URLLC) and mMTC services.
  • 5G includes the New Radio (NR) access stratum interface and the 5G Core Network (5GC).
  • NR New Radio
  • 5GC 5G Core Network
  • the NR physical and higher layers reuse parts of the LTE specification, and additional components are introduced when motivated by new use cases.
  • 3GPP also started work to prepare NR for operation in a non-terrestrial network (NTN). The work was performed within the Study Item “NR to support Non-Terrestrial Networks” and resulted in 3GPP TR 38.811. In 3GPP release 16, the work to prepare NR for operation in a NTN continued with the Study Item “Solutions for NR to support Non-Terrestrial Network,” which resulted in 3GPP TR 38.821.
  • NB-IoT uses increased acquisition times and time repetitions to extend the system coverage.
  • the repetitions may be seen as a third level of retransmissions added at the physical layer as a complement to those at medium access control (MAC) hybrid automatic repeat request (HARQ) and Radio Link Control (RLC) automatic repeat request (ARQ).
  • MAC medium access control
  • HARQ hybrid automatic repeat request
  • RLC Radio Link Control
  • a NB-IoT downlink carrier is defined by 12 orthogonal frequency division multiplexing (OFDM) sub-carriers, each of 15 kHz, giving a total baseband bandwidth of 180 kHz. When multiple carriers are configured, several 180 kHz carriers may be used, e.g., for increasing the system capacity, inter-cell interference coordination, load balancing, etc.
  • OFDM orthogonal frequency division multiplexing
  • NB-IoT supports the different deployment scenarios or modes of operation.
  • ‘Stand-alone operation’ uses, for example, the spectrum currently being used by GSM EDGE radio access network (GERAN) systems as a replacement of one or more global system for mobile communication (GSM) carriers. In principle it operates on any carrier frequency which is neither within the carrier of another system nor within the guard band of another system’s operating carrier.
  • the other system can be another NB-IoT operation or any other radio access technology (RAT), e.g. LTE.
  • RAT radio access technology
  • ‘Guard band operation’ uses the unused resource blocks within an LTE carrier’s guard band.
  • guard band may also interchangeably be referred to as guard bandwidth.
  • the guard band operation of NB-IoT can place anywhere outside the central 18 MHz but within 20 MHz LTE bandwidth.
  • ‘In-band operation’ uses resource blocks within a normal LTE carrier.
  • the in-band operation may also interchangeably be referred to as in-bandwidth operation. More generally, the operation of one RAT within the bandwidth of another RAT is also referred to as in-band operation.
  • in a LTE bandwidth of 50 RBs i.e.
  • NB-IoT defines anchor and non-anchor carriers.
  • anchor specific signals including NPSS/NSSS/NPBCH/SIB-NB are transmitted in the downlink.
  • non-anchor carrier the UE does not assume that NPSS/NSSS/NPBCH/SIB-NB are transmitted in downlink.
  • the anchor carrier is transmitted on at least subframes #0, #4, #5 in every frame and subframe #9 in every other frame.
  • Additional downlink subframes in a frame can also be configured on the anchor carrier by means of a downlink bit map.
  • the anchor carriers transmitting NPBCH/SIB-NB contains also NRS.
  • the non-anchor carrier contains NRS during P110778WO02 PCT APPLICATION 3 of 74 certain occasions and UE specific signals such as NPDCCH and NPDSCH.
  • NRS, NPDCCH and NPDSCH are also transmitted on the anchor carrier.
  • the resources for a non-anchor carrier are configured by the network, i.e. the eNB.
  • the non-anchor carrier can be transmitted in any subframe as indicated by a downlink bit map.
  • the eNB signals a downlink bit map of downlink subframes using a Radio Resource Control (RRC) message (DL-Bitmap-NB) which are configured as a non-anchor carrier.
  • RRC Radio Resource Control
  • the anchor carrier and/or non-anchor carrier may typically be operated by the same network node (eNB), e.g., by the serving cell. But the anchor carrier and/or non-anchor carrier may also be operated by different network nodes (i.e., different eNBs).
  • eNB network node
  • the anchor carrier and/or non-anchor carrier may also be operated by different network nodes (i.e., different eNBs).
  • Satellite networks could complement mobile networks on the ground by providing connectivity to underserved areas and multicast/broadcast services.
  • adapting the terrestrial wireless access technologies including LTE and NR for satellite networks is drawing significant interest, which has been reflected in the 3GPP standardization work.
  • 3GPP release 15 3GPP started the work to prepare NR for operation in a non-terrestrial network (NTN).
  • NTN non-terrestrial network
  • 3GPP release 16 the work to prepare NR for operation in an NTN continued with the study item “Solutions for NR to support Non-Terrestrial Network”, which has been captured in 3GPP TR 38.821.
  • 3GPP release 17 contains both a work item on NR NTN and a study item and work item on NB-IoT and LTE-M support for NTN (RP-193235, Study on NB-IoT/eMTC support for Non-Terrestrial Network; RP-211601, NB- IoT/eMTC support for Non-terrestrial Networks (NTN), RAN#92-e, Jun 2021).
  • a satellite radio access network usually includes the following components: a satellite that refers to a space-borne platform; an Earth-based gateway that connects the satellite to a base station or a core network, depending on the choice of architecture; a feeder link that refers to the link between a gateway and a satellite; and an access link, or service link, that refers to the link between a satellite and a UE.
  • a satellite may be categorized as low Earth orbit (LEO), medium Earth orbit (MEO), or geostationary Earth orbit (GEO) satellite.
  • LEO includes typical heights ranging from 250 – 1,500 km, with orbital periods ranging from 90 – 120 minutes.
  • MEO includes typical heights ranging from 1,500 – 35,786 km, with orbital periods, PMEO, in the P110778WO02 PCT APPLICATION 4 of 74 range 2 hours ⁇ PMEO ⁇ 24 hours.
  • MEO and LEO are also known as a non-geosynchronous orbit (NGSO) type of satellite.
  • GEO includes a height at about 35,786 km, with an orbital period of 24 hours.
  • GSO geosynchronous orbit
  • Two basic architectures can be distinguished for satellite communication networks, depending on the functionality of the satellites in the system: [0019]
  • One architecture is transparent payload (also referred to as bent pipe architecture).
  • the satellite forwards the received signal between the terminal and the network equipment on the ground with only amplification and a shift from uplink frequency to downlink frequency.
  • the transparent payload architecture means that the gNB is located on the ground and the satellite forwards signals/data between the gNB and the UE
  • Another architecture is regenerative payload.
  • the satellite includes on-board processing to demodulate and decode the received signal and regenerate the signal before sending it back to the Earth.
  • the regenerative payload architecture means that the gNB is located in the satellite. [0021] In the work item for NR NTN in 3GPP release 17, only the transparent payload architecture is considered.
  • FIGURE 1 shows an example architecture of a satellite network with bent pipe transponders (i.e., the transparent payload architecture).
  • the gNB may be integrated in the gateway or connected to the gateway via a terrestrial connection (wire, optic fiber, wireless link).
  • the significant orbit height means that satellite systems are characterized by a path loss that is significantly higher than what is expected in terrestrial networks. To overcome the pathloss, it is often required that the access and feeder links are operated in line-of-sight conditions, and that the UE is equipped with an antenna offering high beam directivity.
  • a communication satellite typically generates several beams over a given area.
  • the footprint of a beam is usually in an elliptic shape, which has been traditionally considered as a cell (but a cell consisting of multiple beams is not precluded).
  • the footprint of a beam is also often referred to as a spotbeam.
  • the spotbeam may move over the Earth surface with the satellite movement (and the Earth’s rotation) or may be Earth fixed using beam pointing by the satellite to compensate for its motion.
  • the size of a spotbeam depends on the system design and may range from tens of kilometers to a few thousands of kilometers.
  • the NTN beam may, in comparison to the beams observed in a terrestrial network, provide a very wide footprint and may cover an area outside of the area defined by the served cell.
  • NTN supports three types of beams or cells.
  • Earth-fixed beams/cells are provisioned by beam(s) continuously covering the same geographical areas all the time (e.g., for GEO satellites).
  • Quasi-Earth-fixed beams/cells are provisioned by beam(s) covering one geographic area for a limited period and a different geographic area during another period (e.g., for NGSO satellites generating steerable beams).
  • Earth-moving beams/cells are provisioned by beam(s) whose coverage area slides over the Earth’s surface (e.g., in the case of NGSO satellites generating fixed or non-steerable beams).
  • the terms beam and cell are used interchangeably herein, unless explicitly noted otherwise.
  • this in principle means that one cell is replaced by another, although covering the same area (often referred to as a cell switch).
  • a cell switch For a consequence, all UEs connected in the old cell (i.e., UEs in RRC_CONNECTED state) are handed over (or otherwise moved, e.g., using Radio Resource Control (RRC) connection reestablishment) from the old to the new cell, and all UEs camping on the old cell (i.e., UEs in RRC_IDLE or RRC_INACTIVE state) perform cell reselection to the new cell.
  • RRC Radio Resource Control
  • a satellite switch When the satellite serving the area is changed, so that an old cell disappears and a new cell appears, this is referred to as a satellite switch.
  • a consequence of a satellite switch is that both the service link (i.e., the link between the UE and the satellite) and the feeder link (i.e., the link between the satellite and the GW/gNB) are switched.
  • P110778WO02 PCT APPLICATION 6 of 74 [0030]
  • feeder link switches i.e. when the serving satellite remains the same, but its connection to the ground changes from one (old) GW/gNB to another (new) GW/gNB. Also in this case there is a switch between an old cell and a new cell (i.e.
  • Satellite switches and feeder link switches can both be referred to with the umbrella term “cell switch”.
  • Such cell switches include two alternative principles: 1) hard switch; and 2) soft switch.
  • hard switch there is an instantaneous switch from the old to the new cell, i.e., the new cell appears at the same time as the old cell disappears. This makes completely seamless (i.e., interruption free) handover in practice impossible and creates a situation which may lead to overload of the access resources in the new cell, due to potential access attempt peaks when many UEs try to access the new cell right after the cell switch.
  • soft switch there is a time period during which the new and the old cell coexist (i.e., overlap), covering the same geographical area.
  • the coexistence/overlap period allows some time for connected UEs to be handed over and for camping UEs to reselect to the new cell, which facilitates distribution of the access load in the new cell and thereby also provides better conditions for handovers with shorter interruption time.
  • Soft switch is likely to be the most prevalent cell switch principle in quasi-Earth-fixed cell deployments.
  • Yet another possible deployment option is what is usually referred to as discontinuous coverage. With discontinuous coverage, NGSO satellites orbit the Earth, providing coverage to moving or quasi-Earth-fixed cells. What characterizes a discontinuous coverage deployment is that when a satellite ceases to provide coverage in a certain location, another satellite does not immediately take over this task.
  • the location is left without coverage for a certain time until another satellite (or possibly even the same satellite) starts to provide coverage in the location.
  • Discontinuous coverage can thus be seen as a consequence of sparse satellite deployment. It may typically be used during an early phase where the satellite constellation is still being built up and the number of deployed satellites gradually increase. Alternatively, it can be a deployment alternative chosen to reduce the cost of the NTN, e.g., where the targeted customers and applications are insensitive to access delays. In terms of standard specification, special support for discontinuous coverage has so far mainly been taken into account in the specification of the LTE based IoT NTN.
  • the gNB and the GW may be separate entities which are spatially separate with a non- negligible propagation delay between them, or they can be integrated in a single entity, or separate entities but collocated in a way that the propagation delay between them is negligible.
  • the P110778WO02 PCT APPLICATION 7 of 74 embodiments presented herein are applicable in all cases if the (somewhat inappropriate) definition of the feeder link is the communication link between the satellite and the gNB.
  • Ephemeris data (sometimes referred to as “ephemeris information” or “ephemeris parameters” or just “ephemeris”) is data that enables a UE (or other entity) to determine a satellite’s position and velocity, i.e., the ephemeris data contains parameters related to the satellite’s orbit.
  • ephemeris data contains parameters related to the satellite’s orbit.
  • TR 38.821 specifies that ephemeris data should be provided to the UE, for example to assist with pointing a directional antenna (or an antenna beam) towards the satellite, and to calculate a correct timing advance (TA) and Doppler shift.
  • TA timing advance
  • ephemeris data will be broadcast in the system information (SI) in each cell, included in an NTN specific SIB, (labeled SIB19 in NR NTN and SIB31 IoT NTN).
  • SI system information
  • a satellite orbit can be fully described using 6 parameters. Which set of parameters is chosen may be decided by the user; and many different representations are possible. For example, a choice of parameters used often in astronomy is the set (a, ⁇ , i, ⁇ , ⁇ , t).
  • FIGURE 2 illustrates orbital elements – the parameters included in one ephemeris data format.
  • TLEs the two-line elements (TLEs) use mean motion n and mean anomaly M instead of a and t.
  • a completely different set of parameters is the position and velocity vector (x, y, z, vx, vy, vz) of a satellite. These are sometimes referred to as orbital state vectors. They can be derived from the orbital elements and vice versa, because the information they contain is equivalent. All these formats (and many others) are possible choices for the format of ephemeris data to be used in NTN. [0040] An aspect discussed during the 3GPP study item and captured in 3GPP TR 38.821 is the validity time of ephemeris data. Predictions of satellite positions in general degrade with increasing age of the ephemeris data used, due to atmospheric drag, maneuvering of the satellite, imperfections in the orbital models used, etc.
  • the publicly available TLE data are updated quite frequently.
  • the update frequency depends on the satellite and its orbit and ranges from weekly to multiple times a day for satellites on very low orbits which are exposed to strong atmospheric drag and need to perform correctional maneuvers often.
  • Even more frequent updates will be used in NR NTN (and IoT NTN) to enable the UE to determine/predict the P110778WO02 PCT APPLICATION 8 of 74 satellite’s position (and velocity) accurately enough to satisfy the requirements in NTN, e.g., to enable a UE to calculate an accurate enough UE-specific TA.
  • a global navigation satellite system comprises a set of satellites orbiting the Earth in orbits crossing each other, such that the orbits are distributed around the globe.
  • the satellites transmit signals and data that allows a receiving device on Earth to accurately determine time and frequency references and, maybe most importantly, accurately determine its position, provided that signals are received from a sufficient number of satellites (e.g., four).
  • the position accuracy may typically be in the range of a few meters, but using averaging over multiple measurements, a stationary device may achieve much better accuracy.
  • GNSS Global Positioning System
  • GLONASS Russian Global Navigation Satellite System
  • BeiDou Navigation Satellite System the European Galileo.
  • the transmissions from GNSS satellites include signals that a receiving device uses to determine the distance to the satellite. By receiving such signals from multiple satellites, the device can determine its position. However, this requires that the device also knows the positions of the satellites. To enable this, the GNSS satellites also transmit data about their own orbits (from which position at a certain time can be derived). In GPS, such information is referred to as ephemeris data and almanac data (or sometimes lumped together under the term navigation information).
  • the time required to perform a GNSS measurement may vary widely, depending on the circumstances, mainly depending on the status of the ephemeris and almanac data the measuring devices has previously acquired (if any). In the worst case, a GPS measurement can take several minutes. GPS is using a bit rate of 50 bps for transmitting its navigation information. The transmission of the GPS date, time and ephemeris information takes 90 seconds. Acquiring the GPS almanac containing orbital information for all satellites in the GPS constellation takes more than 10 minutes. If a UE already possesses this information, the synchronization to the GPS signal for acquiring the UE position and Coordinated Universal Time (UTC) is a significantly faster procedure.
  • UTC Coordinated Universal Time
  • the state of a GNSS receiver with regards to the above may be classified as cold, warm or hot state, where the time required to perform a GNSS measurement to determine a position is the longest in cold state, and the shortest in hot state.
  • a relevant note on terminology is that a position determined based on a GNSS measurement, or the act of determining a position based on a GNSS measurement, is also referred to as a “position fix”.
  • 3GPP relies on GNSS for NR NTN and IoT NTN.
  • the GNSS receiver enables a device to estimate its geographical position.
  • an NTN gNB carried by a satellite, or communicating via a satellite, broadcasts its ephemeris data (i.e., data that informs the UE about the satellite’s position, velocity, and orbit) to a GNSS equipped UE.
  • the UE can then determine the propagation delay, the delay variation rate, the Doppler shift, and its variation rate based on its own location (obtained through GNSS measurements) and the satellite location and movement (derived from the ephemeris data).
  • the UE may use this knowledge to compensate its uplink transmissions for the propagation delay and Doppler effect.
  • This principle is used in both NR NTN and IoT NTN.
  • an IoT NTN UE is not expected to be able to perform a GNSS measurement while receiving transmissions from network at the same time.
  • the GNSS receiver also enables a device to determine a time reference (e.g., in terms of UTC) and frequency reference.
  • the GNSS measurement must be fresh enough to be reliable.
  • a GNSS validity duration which governs the maximum age UE location information may have when used in such operations (e.g., for calculation of a timing advance).
  • a suitable value for this maximum age may depend on the UE’s implementation, and therefore the GNSS validity duration is a UE implementation specific mechanism.
  • the standard specifications for IoT NTN specify means by which the UE can inform the network (i.e., the serving eNB in IoT NTN) of the remaining validity time of the UE’s current (most recent) GNSS position measurement result.
  • the long propagation delay/round trip time (RTT) in an NTN impacts the timing advance.
  • Propagation delay is an important aspect of satellite communications and its expected impact in NTN is different from the impacts of propagation delay in a terrestrial mobile system.
  • the UE-gNB round-trip delay may, depending on the orbit height, range from a few or tens of ms for LEO satellites to several hundreds of ms for GEO satellites.
  • the round-trip delays in terrestrial cellular networks are typically below 1 ms.
  • the distance between the UE and a satellite can vary significantly, depending on the position of the satellite and thus the elevation angle ⁇ seen by the UE.
  • the propagation delay may also be highly variable due to the high velocity of the LEO and MEO satellites and change in the order of 10 – 100 ⁇ s every second, depending on the orbit altitude and satellite velocity.
  • the long propagation delays in NTN have many consequences, one of which being that large Timing Advance (TA) values have to be used, where a TA is the time a UE has to advance its UL transmission in relation to the corresponding frame, slot and symbol in the DL to achieve alignment between the UL and the DL frame/slot/symbol structure at an UL/DL alignment reference point (in 3GPP NTN terminology also known as the uplink time synchronization reference point), which typically is the gNB, but which the specifications also allow the network/operator to place between the gNB on the ground (in the transparent payload deployment case) and the satellite.
  • TA Timing Advance
  • the part of the TA that accounts for the RTT between the satellite and the uplink time synchronization reference point is common for all UEs in a cell, whereas the part of the TA that accounts for the RTT between the UE and the satellite depends on the UE’s location and is thus specific for each UE. In addition, due to the fast movement of the satellite (excluding GEO satellites), the TA will continuously change and will do so quite rapidly. [0055] 3GPP has dealt with these circumstances through a combination of new parameters and introduction of the principle of UE autonomous adaptation of the TA.
  • the satellite broadcasts in the system information (SIB19 in NR NTN and SIB31 in IoT NTN) Common TA information, consisting of a Common TA value.
  • SIB19 in NR NTN and SIB31 in IoT NTN system information
  • Common TA information consisting of a Common TA value.
  • the UE specific part of the TA i.e., the UE- satellite RTT is left to the UE to autonomously calculate. To do this, the UE has to obtain its own location and the satellite position.
  • the UE can obtain its own location e.g., using GNSS measurements, and the satellite’s position (as well as its velocity) can be derived from the ephemeris data broadcast by the gNB (in the same SIB as the Common TA parameters).
  • the ephemeris data and the Common TA parameters are nominally valid at an epoch time, which is also indicated in the same SIB (or, if the epoch time indication is absent in the SIB, the epoch time is assumed to be the end of the SI window in which the SIB was received).
  • the UE can predict the satellite’s position a certain time into the future, and the first and second time derivatives (i.e., the drift and drift variation parameters) of the Common TA allows the UE to calculate how the Common TA value changes with time. Furthermore, the broadcast ephemeris data and Common TA parameters have a limited validity time, which is also indicated in the same SIB. The ephemeris data and Common TA parameters the UE uses when calculating the UE specific TA have to be valid, i.e. their validity time must not have expired.
  • a UE calculates the transmit timing as defined in 3GPP TS 38.133 version 18.4.0.
  • the uplink frame transmission takes place ( ⁇ TA + ⁇ TA-offset + ⁇ T c A om , a m d j on + ⁇ UE TA,adj ) ⁇ ⁇ c before the reception of the first detected path (in time) of the corresponding downlink frame the reference cell.
  • ⁇ TA-offset is a configurable offset
  • ⁇ T U A E adj is the common timing the broadcast common TA parameters
  • ⁇ T U A E adj is the UE specific TA part covering the RTT of the service link (i.e. the UE-satellite RTT)
  • ⁇ TA is the part that the network adjusts with the Timing Advance Commands (e.g. Timing Advance Command MAC CEs).
  • Kmac a parameter denoted as Kmac.
  • the Kmac parameter takes care of the RTT P110778WO02 PCT APPLICATION 12 of 74 between the gNB and the chosen UL/DL alignment reference point.
  • the UE When calculating the UE specific TA, the UE only uses the Common TA parameters, the ephemeris data and its own location, i.e. Kmac is not needed for this calculation. However, the UE needs to know Kmac for other purposes, so that it can adapt certain timers to the UE-gNB RTT.
  • the long propagation delay means that the timing advance (TA) the UE uses for its uplink transmissions is essential and has to be much greater than in terrestrial networks for the uplink and downlink to be time-aligned at the gNB or eNB (or at another point if Kmac > 0).
  • TA timing advance
  • RA random access
  • the initial message from the UE in the random access procedure has to be transmitted with a timing advance to allow a reasonable size of the RA preamble reception window in the gNB (and to ensure that the cyclic shift of the preamble’s Zadoff-Chu sequence cannot be so large that it makes the Zadoff-Chu sequence, and thus the preamble, appear as another Zadoff Chu sequence, and thus as another preamble, based on the same Zadoff-Chu root sequence), but this TA does not have to be as accurate as the TA the UE subsequently uses for other uplink transmissions, where the TA has to be accurate enough to keep the timing error smaller than the cyclic prefix (CP) (or preferably smaller than a specified timing error limit which the UE is supposed to aim to stay below).
  • CP cyclic prefix
  • the gNB provides the UE with an accurate (i.e. fine-adjusted) TA in the Random Access Response (RAR) message (in 4-step RA) or MsgB (in 2-step RA), based on the time of reception of the random access preamble.
  • RAR Random Access Response
  • MsgB MsgB
  • the gNB can subsequently adjust the UE’s TA using a Timing Advance Command MAC CE (or an Absolute Timing Advance Command MAC CE), based on the timing of receptions of uplink transmissions from the UE.
  • a Timing Advance Command MAC CE or an Absolute Timing Advance Command MAC CE
  • a goal with such network control of the UE’s timing advance is typically to keep the time error of the UE’s uplink transmissions at the gNB’s receiver within the cyclic prefix (which is required for correct decoding of the uplink transmissions, e.g., on the PUSCH and the PUCCH) (or preferably smaller than a specified timing error limit which the UE is supposed to aim to stay below).
  • the timing advance control framework for NR and LTE also P110778WO02 PCT APPLICATION 13 of 74 includes a time alignment timer (TAT) that the gNB configures the UE with. TAT is used to control how long the UE considers the timing advance (TA) information provided by the network as valid.
  • TAT time alignment timer
  • the value is configured per Timing Advance Group (TAG) via a dedicated RRC message or broadcast in System Information.
  • TAT for a Primary Timing Advance Group (PTAG) is (re)started when any of the following conditions are met: a Timing Advance Command MAC CE is received for the TAG; a Timing Advance Command is received in a Random Access Response (RAR) message or a MsgB for a Serving Cell belonging to a TAG; an Absolute Timing Advance Command is received in a MsgB in response to a MsgA transmission including the C-RNTI MAC CE and small data transmission using configured grant (CG) is not ongoing; an instruction from the upper layer has been received for starting the TAT associated with the PTAG, and the MAC entity is configured with rach-LessHO.
  • RAR Random Access Response
  • MsgB for a Serving Cell belonging to a TAG
  • CG configured grant
  • TAT expires, if the TAT is associated with the PTAG, then: flush all HARQ buffers for all Serving Cells; notify RRC to release PUCCH for all Serving Cells, if configured; notify RRC to release sounding reference signal (SRS) for all Serving Cells, if configured; clear any configured downlink assignments and configured uplink grants; clear any PUSCH resource for semi-persistent CSI reporting; and consider all running TATs as expired.
  • SRS sounding reference signal
  • the TAT is associated with an STAG, then for all Serving Cells belonging to this TAG: fush all HARQ buffers; notify RRC to release PUCCH, if configured; notify RRC to release SRS, if configured; clear any configured downlink assignments and configured uplink grants; and clear any PUSCH resource for semi-persistent CSI reporting.
  • the MAC entity shall not perform any uplink transmission on a serving cell except the Random Access Preamble and MsgA transmission when the TAT associated with the TAG to which this serving cell belongs is not running.
  • a crucial extension of the TA framework in NTN is the concept of UE autonomous TA adjustments.
  • the long propagation delays and the resulting large TA a UE has to use also impacts the scheduling of uplink transmissions. Specifically, the network has to take the large TA into account when it determines the delay to be used between an UL grant (i.e. a DCI on the PDCCH allocating uplink transmission resources for the UE to transmit on) and the uplink transmission resources the UL grant allocates.
  • an UL grant i.e. a DCI on the PDCCH allocating uplink transmission resources for the UE to transmit on
  • K offset a new parameter denoted as “K offset ” (or “Koffset” or “K_offset”) has been introduced, which is added to the legacy delay, e.g. added to P110778WO02 PCT APPLICATION 14 of 74 the legacy delay parameter K2 (or K2) contained in the UL grant in NR NTN.
  • the Koffset parameter comes in two forms: the cell-specific Koffset, which is broadcast in the system information and which is common for all UEs in the cell, and the UE-specific Koffset, which the network optionally configures for a specific UE. Note that configuration of a UE-specific Koffset value is optional, and when it is absent, the cell-specific K offset value applies.
  • the broadcast system information may include NTN-specific information. Due to the special operating conditions in a NTN, the system information broadcast in an NTN cell includes NTN-specific information. To serve this purpose, a new SIB (SIB19) is introduced in NR NTN that contains NTN-specific information. In IoT NTN, the new SIB31 more or less corresponds to SIB19 in NR NTN.
  • SIB19 SIB19
  • MovingReferenceLocation Reference location of the serving cell of an NTN Earth moving system at a time reference It is used in location-based measurement initiation in RRC_IDLE and RRC_INACTIVE, as defined in TS 38.304.
  • the time reference of this field is indicated by epochTime in ntn-Config of the serving cell.
  • This field is excluded when determining changes in system information, i.e., changes to movingReferenceLocation should neither result in system information change notifications nor in a modification of valueTag in SIB1. This field is only present in an NTN cell.
  • ntn-Config Provides parameters needed for the UE to access NR via NTN access such as Ephemeris data, common TA parameters, k_offset, validity duration for UL sync information and epoch. In a TN cell, this field is only present in ntn- NeighCellConfigList and ntn-NeighCellConfigListExt. ntn-NeighCellConfigList, ntn-NeighCellConfigListExt Provides a list of NTN neighbour cells including their ntn-Config, carrier frequency and PhysCellId.
  • This set includes all elements of ntn-NeighCellConfigList and all elements of ntn-NeighCellConfigListExt. If ntn-Config is absent for an entry in ntn- NeighCellConfigListExt, the ntn-Config provided in the entry at the same position in ntn-NeighCellConfigList applies. Network provides ntn-Config for the first entry of ntn-NeighCellConfigList. If the ntn-Config is absent for any other entry in ntn- NeighCellConfigList, the ntn-Config provided in the previous entry in ntn- NeighCellConfigList applies.
  • This field is only present in an NTN cell.
  • movingReferenceLocation RRC_INACTIVE as defined in TS 38.304.
  • the time reference of this field is indicated by epochTime in ntn-Config of the serving cell. This field is excluded when determining changes in system information, i.e., changes to movingReferenceLocation should neither result in system information change notifications nor in a modification of valueTag in SIB1. This field is only present in an NTN cell.
  • referenceLocation Reference location of the serving cell provided via NTN quasi-Earth fixed system and is used in location-based measurement initiation in RRC_IDLE and RRC_INACTIVE, as defined in TS 38.304.
  • This field is only present in an NTN cell.
  • satSwitchWithReSync that satellite switch without PCI change is supported in the cell.
  • t-Service Indicates the time information on when a cell provided via NTN system is going to stop serving the area it is currently covering. This field applies for both service link switches in NTN quasi-Earth fixed system and feeder link switches for both NTN quasi-Earth fixed and Earth moving system.
  • the field indicates a time in multiples of 10 ms after 00:00:00 on Gregorian calendar date 1 January, 1900 (midnight between Sunday, December 31, 1899 and Monday, January 1, 1900). The exact stop time is between the time indicated by the value of this field minus 1 and the time indicated by the value of this field.
  • the reference point for t-Service is the uplink time synchronization reference point of the cell. This field is only present in an NTN cell.
  • P110778WO02 PCT APPLICATION 17 of 74 s atSwitchWithReSync field descriptions ssb-TimeOffset Indicates the time offset between the SSB from source and target satellite at the uplink time synchronization reference point. It is given in number of subframes.
  • t-ServiceStart Indicates the time information on when the target area currently covered by the serving satellite.
  • the exact start time is between the time indicated by the value of this field minus 1 and the time indicated by the value of this field.
  • EpochTime-r17 SEQUENCE ⁇ sfn-r17 INTEGER(0..1023), subFrameNR-r17 INTEGER(0..9)
  • TAInfo-r17 SEQUENCE ⁇ ta-Common-r17 INTEGER(0..66485757), ta-CommonDrift-r17 INTEGER(-257303..257303)
  • OPTIONAL -- Need R ta-CommonDriftVariant-r17 INTEGER(0..28949)
  • EphemerisInfo This field provides satellite ephemeris either in format of position and velocity state vector or in format of orbital parameters.
  • EpochTime Indicate the epoch time for the NTN assistance information.
  • EpochTime is the starting time of a DL sub- frame, indicated by a SFN and a sub-frame number signaled together with the assistance information.
  • the reference point for epoch time of the serving satellite ephemeris and Common TA parameters is the uplink time synchronization reference point. If this field is absent, the epoch time is the end of SI window where this SIB19 is scheduled. This field is mandatory present when provided in dedicated configuration.
  • this field is absent in ntn- Config provided via NTN-NeighCellConfig the UE uses epoch time from the serving satellite ephemeris, otherwise the field is based on the timing of the serving cell, i.e. the SFN and sub- frame number indicated in this field refers to the SFN and sub-frame of the serving cell. In case of handover, this field is based on the timing of the target cell, i.e. the SFN and sub- frame number indicated in this field refers to the SFN and sub-frame of the target cell. This field is excluded when determining changes in system information, i.e. changes to epochTime should neither result in system information change notifications nor in a modification of valueTag in SIB1.
  • K_offset is number of slots for a given subcarrier spacing of 15 kHz. If the field is absent UE assumes value 0. kmac Scheduling offset provided by network if downlink and uplink frame timing are not aligned at gNB. It is needed for UE action and assumption on downlink configuration indicated by a MAC CE command in PDSCH [see TS 38.2xy]. If the field is absent UE assumes value 0. For the reference subcarrier spacing value for the unit of K_mac in FR1, a value of 15 kHz is used. The unit of K_mac is number of slots for a given subcarrier spacing.
  • ntn-PolarizationDL indicates polarization information for downlink transmission on service link: including Right hand, Left hand circular polarizations (RHCP, LHCP) and Linear polarization.
  • ntn-PolarizationUL If present, this parameter indicates Polarization information for Uplink service link. If not present and ntn-PolarizationDL is present, UE assumes the same polarization for UL and DL.
  • ntn-UlSyncValidityDuration A validity duration configured by the network for assistance information (i.e.
  • ntn-UlSyncValidityDuration The unit of ntn-UlSyncValidityDuration is second. Value s5 corresponds to 5 s, value s10 indicate 10 s and so on. This parameter applies to both connected and idle mode UEs. If this field is absent in ntn-Config provided via NTN-NeighCellConfig, the UE uses validity duration from the serving cell assistance information. This field is excluded when determining changes in system information, i.e. changes of ntn-UlSyncValidityDuration should neither result in system information change notifications nor in a modification of valueTag in SIB1.
  • ntn-UlSyncValidityDuration is only updated when at least one of epochTime, ta-Info, ephemerisInfo is updated.
  • ta-Common with value of 0 is supported.
  • the granularity of ta-Common is 4.072 ⁇ 10 ⁇ (-3) ⁇ s. Values are given in unit of corresponding granularity. This field is excluded when determining changes in system information, i.e. changes of ta-Common should neither result in system information change notifications nor in a modification of valueTag in SIB1.
  • ta-CommonDrift Indicate drift rate of the common TA.
  • the granularity of ta-CommonDrift is 0.2 ⁇ 10 ⁇ (-3) ⁇ s ⁇ s Values are given in unit of corresponding granularity. This field is excluded when determining changes in system information, i.e. changes of ta-CommonDrift should neither result in system information change notifications nor in a modification of valueTag in SIB1. P110778WO02 PCT APPLICATION 20 of 74 ta-CommonDriftVariant Indicate drift rate variation of the common TA.
  • the granularity of ta-CommonDriftVariation is 0.2 ⁇ 10 ⁇ (-4) ⁇ s ⁇ s ⁇ 2. Values are given in unit of corresponding granularity. This field is excluded when determining changes in system information, i.e.
  • ta-Report When this field is included in SIB19, it indicates reporting of timing advanced is enabled during Random Access due to RRC connection establishment or RRC connection resume, and during RRC connection reestablishment.. When this field is included in ServingCellConfigCommon within dedicated signaling, it indicates TA reporting is enabled during Random Access due to reconfiguration with sync (see TS 38.321, clause 5.4.8).
  • SIB31 contains similar information for IoT NTN as SIB19 does for NR NTN. The following is the ASN.1 code for SIB31 in 3GPP TS 36.331 version 18.0.0.
  • referenceLocation Reference location of the NTN quasi-earth fixed cell or earth moving cell used in location-based measurement initiation in RRC_IDLE (as specified in TS 36.304) and RRC_CONNECTED. If configured by an earth moving cell, the broadcast reference location corresponds to the epoch time, and the UE derives the real-time reference location based on the serving satellite ephemeris, see TS 36.304.
  • stateVectors Instantaneous values of the satellite state vectors. The signalled values are valid at least for the duration as defined by ul-SyncValidityDuration and epochTime.
  • SIB32 with ASN.1 code definition as follows in 3GPP TS 36.331 version 18.0.0, also contains IoT NTN specific information, which in this SIB is tailored for deployments with discontinuous coverage.
  • E-UTRAN always configures tle-EphemerisParameters for a satellite with earth moving cell(s) and always configures t-ServiceStart for a quasi-earth fixed cell.
  • P110778WO02 PCT APPLICATION 25 of 74 tle-EphemerisParameters Mean values of the satellite orbital parameters based on the TLE set format for estimating in-coverage and out-of-coverage periods for a satellite with earth cell(s), see TS 36.304.
  • the NTN described above is based on 5G/NR technology adapted for communication via satellites. But an NTN standard for IoT, denoted as “IoT NTN”, is also being specified in release 17 of the 3GPP standards.
  • IoT NTN is based on the LTE NB-IoT technology adapted for communication via satellites.
  • NTN based on 5G/NR technology is often referred to as “NR NTN”.
  • NR NTN NTN based on 5G/NR technology
  • NTN NTN based on 5G/NR technology
  • NTN NTN based on 5G/NR technology
  • NTN NTN based on 5G/NR technology
  • NTN is sometimes used to refer to either or both of NR NTN and IoT NTN, and sometimes the term “NTN” is used to refer only to NR NTN.
  • TA formula that the network adjusts with its instructions, e.g., the Timing Advance Command MAC CEs. This is the term the network uses to keep the UE’s TA within bounds (or at a desired value) e.g. when the UE’s autonomous TA adjustments do not manage to do this well enough.
  • the UE depends on the accuracy of its estimation of its own position, typically determined by a GNSS measurement, when calculating the ⁇ T U A E , adj term in the TA formula.
  • a UE thus typically performs repeated GNSS measurements to update its estimate of its own position (possibly complemented by other means, such as movement tracking based on internal sensor, such as accelerometers).
  • NTA new (more accurate) position estimate
  • the argument for the latter view (leave NTA as it is) is that the network should remain in full control of N TA and thus the UE should leave it as P110778WO02 PCT APPLICATION 26 of 74 it is (e.g. because the UE does not have the full picture and cannot know for sure the network’s grounds for adjusting N TA to its current value).
  • TA timing advance
  • NTN non-terrestrial network
  • Certain aspects of the disclosure and their embodiments may provide solutions to these or other challenges.
  • particular embodiments are based on two realizations.
  • the first realization is that there are two main sources of UE transmission timing errors contributing to the total transmission timing error: (1) the UE’s movements between updates of the UE’s position information, and (2) the error in the estimation of the serving satellite’s position and the error in the common TA parameters, both caused mainly by the aging of the ephemeris and common TA parameter (i.e. the elapsed time since the associated epoch time). These are thus the errors the network can use NTA to compensate for.
  • NTA_new NTA_old - Terror_UE_position.
  • Particular embodiments include various variations and additional options, e.g. configuration options, as well as a scheme for applying the same principle to the second of the two error sources listed above.
  • the TA value is based at least in part on a position estimate of the wireless device and a timing adjustment value.
  • the method comprises: obtaining a first wireless device position estimate used for calculating a TA value; receiving a timing advance command from a network node, the timing advance command comprising an indication of the timing adjustment value; obtaining a second wireless device position estimate used for calculating the TA value; updating the timing adjustment value based on the second wireless device position estimate to remove a value corresponding to a difference between the first wireless device position estimate and the second wireless device position estimate from the timing adjustment value; calculating a TA value for uplink transmission using the updated timing adjustment value; and transmitting an uplink transmission using the calculated TA value.
  • the method further comprises obtaining a satellite position estimate used for calculating a TA value, and wherein updating the timing adjustment value is further based on the satellite position estimate. [0086] In particular embodiments, the method further comprises transmitting an indication to the network node of the updated timing adjustment value.
  • the first wireless device position estimate and the second wireless device position estimate are used for calculating the ⁇ T U A E , adj term in the TA formula.
  • the difference between the first wireless device position estimate and the second wireless device position estimate is represented as T error_UE_position .
  • the wireless device is operating in a non-terrestrial network.
  • another method is performed by a wireless device for modifying a TA value.
  • the TA value is based at least in part on a position estimate of a satellite and a timing adjustment value.
  • the method comprises: obtaining a first satellite position estimate used for calculating a TA value; receiving a timing advance command from a network node, the timing advance command comprising an indication of the timing adjustment value; obtaining a second satellite position estimate used for calculating the TA value; updating the timing adjustment value based on the second satellite position estimate to remove a value corresponding to a difference between the first satellite position estimate and the second satellite position estimate from the timing adjustment value; calculating a TA value for uplink transmission using the updated timing adjustment value; and transmitting an uplink transmission using the calculated TA value.
  • the method further comprises obtaining a wireless device position estimate used for calculating a TA value, and wherein updating the timing adjustment value is further based on the wireless device position estimate.
  • the method further comprises transmitting an indication to the network node of the updated timing adjustment value.
  • a wireless device comprises processing circuitry operable to perform any of the wireless device methods described above.
  • a computer program product comprising a non-transitory computer readable medium storing computer readable program code, the computer readable program code operable, when executed by processing circuitry to perform any of the methods performed by the wireless devices described above.
  • P110778WO02 PCT APPLICATION 29 of 74 Certain embodiments may provide one or more of the following technical advantages. For example, particular embodiments solve the problem of how a UE should appropriately treat NTA in the TA calculation formula upon acquisition of a new updated UE position estimate, e.g. obtained through a GNSS measurement.
  • FIGURE 1 shows an example architecture of a satellite network with bent pipe transponders
  • FIGURE 2 illustrates orbital elements – the parameters included in one ephemeris data format
  • FIGURE 3 shows an example of a communication system, according to certain embodiments
  • FIGURE 4 shows a user equipment (UE), according to certain embodiments
  • FIGURE 5 shows a network node, according to certain embodiments
  • FIGURE 6 is a block diagram of a host, according to certain embodiments
  • FIGURE 7 is a block diagram illustrating a virtualization environment in which functions implemented by some embodiments may be virtualized
  • FIGURE 8 shows a communication diagram of a host communicating via a network node with a UE over a partially wireless connection in accordance with some embodiments.
  • non-terrestrial network may, depending on the context, refer to either or both of New Radio (NR) NTN and Internet-of-things (IoT) NTN, and sometimes the term is used to refer to only NR NTN.
  • NR New Radio
  • IoT Internet-of-things
  • LTE Long Term Evolution
  • a gNB may be an en-gNB, and if a split gNB architecture is applied (dividing the gNB into multiple separate entities or notes), the term “network” or “network node” or “node” may refer to a part of the gNB, such as a gNB-central unit (CU) (often referred to as just CU), a gNB-distributed unit (DU) (often referred to as just DU), a gNB-CU-control plane (CP) or a gNB-CU-user plane (UP).
  • CU gNB-central unit
  • DU gNB-distributed unit
  • CP gNB-CU-control plane
  • UP gNB-CU-user plane
  • an eNB may be an ng-eNB, and if a split eNB architecture is applied (dividing the gNB into multiple separate entities or notes), the term “network” (and the network node it implies) may refer to a part of the eNB, such as an eNB-CU, an eNB-DU, an eNB-CU-CP or an eNB-CU-UP. Furthermore, the term “network” (and the network node it implies) may also refer to an integrated access and backhaul (IAB)-donor, IAB-donor-CU, IAB-donor-DU, IAB-donor-CU-CP, or an IAB-donor-CU-UP.
  • IAB integrated access and backhaul
  • Ephemeris data is associated with (and applies to) a satellite. However, for convenience, ephemeris data may sometimes be described as associated with a cell, when the ephemeris data referred to actually is associated with the satellite serving the cell. This convenience practice may be seen e.g., in expressions like “a cell’s ephemeris data” or “the P110778WO02 PCT APPLICATION 31 of 74 ephemeris data of the cell”.
  • Parameters/IEs/fields used in ASN.1 code as well as in procedural text in the 3GPP RRC specification for 5G/NR, i.e.3GPP TS 38.331 version 17.3.0, are often named with a suffix indicating the number of the release of the 3GPP standard the parameter/IE/field was introduced in (e.g. the suffix “-r17” for a parameter/IE/field introduced in release 17 of the 3GPP standard).
  • N_TA N_TA
  • T error The main source of the timing error, Terror, the NTA has been adjusted to compensate for are the following.
  • the first source is the UE’s movements, in particular its movements between two position estimate updates, i.e. typically between two GNSS measurements. Such movements lead to an error in the UE’s estimation of its own position which in turn leads to an error in the UE’s calculation of ⁇ T U A E , adj , which hereafter is denoted as T error_UE_position .
  • the network can compensate for this by adjusting NTA accordingly.
  • the second source is that ephemeris and common TA parameters broadcast in SIB19 (in NR NTN) or in SIB32 (in IoT NTN) are fully correct only at the epoch time. They can be used to extrapolate the satellite’s movement in its orbit and to calculate the common TA at a later (or earlier) time, but these calculations will inevitably result in an error in the estimation of the satellite’s position, and thus in turn an error in the distance and propagation delay between the UE and the satellite, as well as an error in the calculated common TA, and these errors typically grow the further away (i.e.
  • Terror_UE_position plus or minus
  • NTA i.e. an NTA > 0
  • T error_satellite_position_and_common_TA This means that when Terror_UE_position is removed from Terror, because the UE recalculates ⁇ T U A E , adj based on the new (accurate) UE position estimate, it is appropriate to remove Terror_UE_position from NTA, i.e.
  • NTA_new NTA_old - Terror_UE_position, where NTA_old is the NTA the UE was using before the UE position update and N TA_new is the N TA the UE should use after the UE position update, i.e. after acquiring a new (accurate) UE position estimate, e.g. based on a new GNSS measurement. This in essence means the UE keeps its overall TA unchanged when fixing TA error by itself.
  • a UEAssistanceInformation RRC message extended with the new notification
  • MAC signaling e.g. a new MAC CE
  • UCI signaling e.g. a new MAC CE
  • RRC signaling e.g., a new RRC message or an existing RRC message, e.g. a UEAssistanceInformation RRC message, extended with the new notification
  • MAC signaling e.g., a new MAC CE
  • UCI signaling e.g., a new MAC CE
  • the notification may be sent to the network using RRC signaling (e.g., a new RRC message or an existing RRC message, e.g. a UEAssistanceInformation RRC message, extended with the new notification), MAC signaling (e.g., a new MAC CE) or UCI signaling.
  • RRC signaling e.g., a new RRC message or an existing RRC message, e.g. a UEAssistanceInformation RRC message, extended with the new notification
  • MAC signaling e.g., a new MAC CE
  • UCI signaling e.g., a new MAC CE
  • K is a value in the range 0 ⁇ K ⁇ 1.
  • the value of K may be specified or may be included in the configuration, optionally with a specified default value to apply in case the K value is absent in the configuration.
  • the notification may be sent to the network using RRC signaling (e.g., a new RRC message or an existing RRC message, e.g.
  • a further signaling option may be that both common signaling and dedicated signaling may be used, wherein the configuration provided using dedicated signaling overrides the configuration provided using common signaling.
  • Particular embodiments include application of reductions of the satellite position error and the common TA error based on obtained newer ephemeris and common TA parameters. With some adaptations to account for the circumstances being different than when the UE updates its own location, the same principle as described above may be applied when the UE obtains new ephemeris and common TA parameters (and consequently recalculates ⁇ T c A om , a m d j on ).
  • the UE may regard the new ephemeris and common TA parameters as correct P110778WO02 PCT APPLICATION 37 of 74 and thus assume that the Terror_satellite_position_and_common_TA before the new ephemeris and common TA parameters were obtained and applied is equal to the difference between the ⁇ T co A m , a m d j on value calculated using the new ephemeris and common TA parameters and the ⁇ T co A m , a m d j on value calculated using the old (previous) ephemeris and common TA parameters,
  • the UE assumes that the ⁇ common T A,adj value calculated using the new ephemeris and common TA parameters is closer to the correct value (i.e., with a smaller error) than the ⁇ T c A om , a m d j on value calculated using the old (previous) ephemeris and common TA parameters) and modifies N TA to compensate for the difference between the ⁇ common value calculated using the new ephemeris and common TA p common T A,adj arameters and the ⁇
  • the communication system 100 may include any number of wired or wireless networks, network nodes, UEs, and/or any other components or systems that may facilitate or participate in the communication of data and/or signals whether via wired or wireless connections.
  • the communication system 100 may include and/or interface with any type of communication, telecommunication, data, cellular, radio network, and/or other similar type of system.
  • the UEs 112 may be any of a wide variety of communication devices, including wireless devices arranged, configured, and/or operable to communicate wirelessly with the network nodes 110 and other communication devices.
  • the network nodes 110 are arranged, capable, configured, and/or operable to communicate directly or indirectly with the UEs 112 and/or with other network nodes or equipment in the telecommunication network 102 to enable and/or provide network access, such as wireless network access, and/or to perform other functions, such as administration in the telecommunication network 102.
  • the core network 106 connects the network nodes 110 to one or more hosts, such as host 116. These connections may be direct or indirect via one or more intermediary networks or devices. In other examples, network nodes may be directly coupled to hosts.
  • the core network 106 includes one more core network nodes (e.g., core network node 108) that are structured with hardware and software components.
  • Example core network nodes include functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier De-concealing function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and/or a User Plane Function (UPF).
  • MSC Mobile Switching Center
  • MME Mobility Management Entity
  • HSS Home Subscriber Server
  • AMF Access and Mobility Management Function
  • SMF Session Management Function
  • AUSF Authentication Server Function
  • SIDF Subscription Identifier De-concealing function
  • UDM Unified Data Management
  • SEPP Security Edge Protection Proxy
  • NEF Network Exposure Function
  • UPF User Plane Function
  • the host 116 may be under the ownership or control of a service provider other than an operator or provider of the access network 104 and/or the telecommunication network 102, and may be operated by the service provider or on behalf of the service provider.
  • the host 116 may host a variety of applications to provide one or more service. Examples of such applications include live and pre-recorded audio/video content, data collection services such as retrieving and compiling data on various ambient conditions detected by a plurality of UEs, analytics functionality, social media, functions for controlling or otherwise interacting with remote devices, functions for an alarm and surveillance center, or any other such function performed by a server.
  • the communication system 100 of FIGURE 3 enables connectivity between the UEs, network nodes, and hosts.
  • the communication system may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE), and/or other suitable 2G, 3G, 4G, 5G standards, or any applicable future generation standard (e.g., 6G); wireless local area network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (WiFi); and/or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, LiFi, and/or any low-power wide-area network (LPWAN) standards such as LoRa and Sigfox.
  • GSM Global System for Mobile Communications
  • UMTS Universal Mobile Telecommunications System
  • LTE Long Term Evolution
  • 6G wireless local area network
  • WiFi wireless local area network
  • WiMax Worldwide Interoperability for Micro
  • the telecommunication network 102 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunications network 102 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network 102. For example, the telecommunications network 102 may provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs, while providing Enhanced Mobile Broadband (eMBB) services to other UEs, and/or Massive Machine Type Communication (mMTC)/Massive IoT services to yet further UEs. P110778WO02 PCT APPLICATION 43 of 74 [0148] In some examples, the UEs 112 are configured to transmit and/or receive information without direct human interaction.
  • URLLC Ultra Reliable Low Latency Communication
  • eMBB Enhanced Mobile Broadband
  • mMTC Massive Machine Type Communication
  • mMTC Massive Machine Type Communication
  • the UEs 112 are configured to transmit and/or receive information without direct human interaction.
  • a UE may be designed to transmit information to the access network 104 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 104.
  • a UE may be configured for operating in single- or multi-RAT or multi-standard mode.
  • a UE may operate with any one or combination of Wi-Fi, NR (New Radio) and LTE, i.e. being configured for multi-radio dual connectivity (MR-DC), such as E-UTRAN (Evolved-UMTS Terrestrial Radio Access Network) New Radio – Dual Connectivity (EN-DC).
  • MR-DC multi-radio dual connectivity
  • the hub 114 communicates with the access network 104 to facilitate indirect communication between one or more UEs (e.g., UE 112c and/or 112d) and network nodes (e.g., network node 110b).
  • the hub 114 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs.
  • the hub 114 may be a broadband router enabling access to the core network 106 for the UEs.
  • the hub 114 may be a controller that sends commands or instructions to one or more actuators in the UEs.
  • the hub 114 acts as a proxy server or orchestrator for the UEs, in particular in if one or more of the UEs are low energy IoT devices.
  • the hub 114 may have a constant/persistent or intermittent connection to the network node 110b.
  • the hub 114 may also allow for a different communication scheme and/or schedule between the hub 114 and UEs (e.g., UE 112c and/or 112d), and between the hub 114 and the core network 106.
  • the hub 114 is connected to the core network 106 and/or one or more UEs via a wired connection.
  • the hub 114 may be configured to connect to an M2M service provider over the access network 104 and/or to another UE over a direct connection.
  • UEs may establish a wireless connection with the network nodes 110 while still connected via the hub 114 via a wired or wireless connection.
  • the hub 114 may be a dedicated hub – that is, a hub whose primary function is to route communications to/from the UEs from/to the network node 110b.
  • the hub 114 may be a non- P110778WO02 PCT APPLICATION 44 of 74 dedicated hub – that is, a device which is capable of operating to route communications between the UEs and network node 110b, but which is additionally capable of operating as a communication start and/or end point for certain data channels.
  • FIGURE 4 shows a UE 200 in accordance with some embodiments.
  • a UE refers to a device capable, configured, arranged and/or operable to communicate wirelessly with network nodes and/or other UEs.
  • Examples of a UE include, but are not limited to, a smart phone, mobile phone, cell phone, voice over IP (VoIP) phone, wireless local loop phone, desktop computer, personal digital assistant (PDA), wireless cameras, gaming console or device, music storage device, playback appliance, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), smart device, wireless customer-premise equipment (CPE), vehicle-mounted or vehicle embedded/integrated wireless device, etc.
  • Other examples include any UE identified by the 3rd Generation Partnership Project (3GPP), including a narrow band internet of things (NB-IoT) UE, a machine type communication (MTC) UE, and/or an enhanced MTC (eMTC) UE.
  • 3GPP 3rd Generation Partnership Project
  • NB-IoT narrow band internet of things
  • MTC machine type communication
  • eMTC enhanced MTC
  • a UE may support device-to-device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, Dedicated Short-Range Communication (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle-to- everything (V2X).
  • D2D device-to-device
  • DSRC Dedicated Short-Range Communication
  • V2V vehicle-to-vehicle
  • V2I vehicle-to-infrastructure
  • V2X vehicle-to- everything
  • a UE may not necessarily have a user in the sense of a human user who owns and/or operates the relevant device.
  • a UE may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller).
  • a UE may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter).
  • the UE 200 includes processing circuitry 202 that is operatively coupled via a bus 204 to an input/output interface 206, a power source 208, a memory 210, a communication interface 212, and/or any other component, or any combination thereof.
  • Certain UEs may utilize all or a subset of the components shown in FIGURE 4. The level of integration between the components may vary from one UE to another UE.
  • the processing circuitry 202 is configured to process instructions and data and may be configured to implement any sequential state machine operative to execute instructions stored as machine-readable computer programs in the memory 210.
  • the processing circuitry 202 may be implemented as one or more hardware-implemented state machines (e.g., in discrete logic, field- programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), etc.); P110778WO02 PCT APPLICATION 45 of 74 programmable logic together with appropriate firmware; one or more stored computer programs, general-purpose processors, such as a microprocessor or digital signal processor (DSP), together with appropriate software; or any combination of the above.
  • the processing circuitry 202 may include multiple central processing units (CPUs).
  • the input/output interface 206 may be configured to provide an interface or interfaces to an input device, output device, or one or more input and/or output devices.
  • Examples of an output device include a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof.
  • An input device may allow a user to capture information into the UE 200.
  • Examples of an input device include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like.
  • the presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user.
  • the memory 210 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as tamper resistant module in the form of a universal integrated circuit card (UICC) including one or more subscriber identity modules (SIMs), such as a USIM and/or ISIM, other memory, or any combination thereof.
  • RAID redundant array of independent disks
  • HD-DVD high-density digital versatile disc
  • HDDS holographic digital data storage
  • DIMM mini-dual in-line memory module
  • SDRAM synchronous dynamic random access memory
  • SDRAM synchronous dynamic random access memory
  • the UICC may for example be an embedded UICC (eUICC), integrated UICC (iUICC) or a removable UICC commonly known as ‘SIM card.’
  • the memory 210 may allow the UE 200 to access instructions, application programs and the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data.
  • An article of manufacture, such as one utilizing a communication system may be tangibly embodied as or in the memory 210, which may be or comprise a device-readable storage medium.
  • the processing circuitry 202 may be configured to communicate with an access network or other network using the communication interface 212.
  • the communication interface 212 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 222.
  • network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NR NodeBs (gNBs)).
  • APs access points
  • BSs base stations
  • Node Bs evolved Node Bs
  • gNBs NR NodeBs
  • Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and so, depending on the provided amount of coverage, may be referred to as femto base stations, pico base stations, micro base stations, or macro base stations.
  • a base station may be a relay node or a relay donor node controlling a relay.
  • a network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units and/or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio. Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS).
  • DAS distributed antenna system
  • the radio front-end circuitry 318 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 320 and/or amplifiers 322. The radio signal may then be transmitted via the antenna 310. Similarly, when receiving data, the antenna 310 may collect radio signals which are then converted into digital data by the radio front-end circuitry 318. The digital data may be passed to the processing circuitry 302. In other embodiments, the communication interface may comprise different components and/or different combinations of components. [0174] In certain alternative embodiments, the network node 300 does not include separate radio front-end circuitry 318, instead, the processing circuitry 302 includes radio front-end circuitry and is connected to the antenna 310.
  • FIGURE 6 is a block diagram of a host 400, which may be an embodiment of the host 116 of FIGURE 3, in accordance with various aspects described herein.
  • the host 400 may be or comprise various combinations hardware and/or software, including a standalone server, a blade server, a cloud-implemented server, a distributed server, a virtual machine, container, or processing resources in a server farm.
  • the host 400 may provide one or more services to one or more UEs.
  • the host 400 includes processing circuitry 402 that is operatively coupled via a bus 404 to an input/output interface 406, a network interface 408, a power source 410, and a memory 412.
  • virtualization can be applied to any device described herein, or components thereof, and relates to an implementation in which at least a portion of the functionality is implemented as one or more P110778WO02 PCT APPLICATION 53 of 74 virtual components.
  • Some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines (VMs) implemented in one or more virtual environments 500 hosted by one or more of hardware nodes, such as a hardware computing device that operates as a network node, UE, core network node, or host.
  • VMs virtual machines
  • hardware nodes such as a hardware computing device that operates as a network node, UE, core network node, or host.
  • the virtual node does not require radio connectivity (e.g., a core network node or host)
  • the node may be entirely virtualized.
  • a virtual appliance 502 may be implemented on one or more of VMs 508, and the implementations may be made in different ways.
  • Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV).
  • NFV network function virtualization
  • NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment.
  • a VM 508 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine.
  • Each of the VMs 508, and that part of hardware 504 that executes that VM forms separate virtual network elements.
  • a virtual network function is responsible for handling specific network functions that run in one or more VMs 508 on top of the hardware 504 and corresponds to the application 502. P110778WO02 PCT APPLICATION 54 of 74 [0187]
  • Hardware 504 may be implemented in a standalone network node with generic or specific components. Hardware 504 may implement some functions via virtualization. Alternatively, hardware 504 may be part of a larger cluster of hardware (e.g.
  • hardware 504 is coupled to one or more radio units that each include one or more transmitters and one or more receivers that may be coupled to one or more antennas. Radio units may communicate directly with other hardware nodes via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station. In some embodiments, some signaling can be provided with the use of a control system 512 which may alternatively be used for communication between hardware nodes and radio units.
  • FIGURE 8 shows a communication diagram of a host 602 communicating via a network node 604 with a UE 606 over a partially wireless connection in accordance with some embodiments.
  • UE such as a UE 112a of FIGURE 3 and/or UE 200 of FIGURE 4
  • network node such as network node 110a of FIGURE 3 and/or network node 300 of FIGURE 5
  • host such as host 116 of FIGURE 3 and/or host 400 of FIGURE 6) discussed in the preceding paragraphs will now be described with reference to FIGURE 8.
  • embodiments of host 602 include
  • the host 602 also includes software, which is stored in or accessible by the host 602 and executable by the processing circuitry.
  • the software includes a host application that may be operable to provide a service to a remote user, such as the UE 606 connecting via an over-the-top (OTT) connection 650 extending between the UE 606 and host 602.
  • OTT over-the-top
  • a host application may provide user data which is transmitted using the OTT connection 650.
  • the network node 604 includes hardware enabling it to communicate with the host 602 and UE 606.
  • the connection 660 may be direct or pass through a core network (like core network 106 of FIGURE 3) and/or one or more other intermediate networks, such as one or more public, private, or hosted networks.
  • the host 602 may initiate the transmission responsive to a request transmitted by the UE 606.
  • the request may be caused by human interaction with the UE 606 or by operation of the client application executing on the UE 606.
  • the transmission may pass via the network node 604, in accordance with the teachings of the embodiments described throughout this disclosure.
  • the network node 604 transmits to the UE 606 the user data that was carried in the transmission that the host 602 initiated, in accordance with the teachings of the embodiments described throughout this disclosure.
  • the UE 606 receives the user data carried in the transmission, which may be performed by a client application executed on the UE 606 associated with the host application executed by the host 602.
  • the UE 606 executes a client application which provides user data to the host 602.
  • the user data may be provided in reaction or response to the data received from the host 602.
  • the UE 606 may provide user data, which may be performed by executing the client application.
  • the client application may further consider user input received from the user via an input/output interface of the UE 606. Regardless of the specific manner in which the user data was provided, the UE 606 initiates, in step 618, P110778WO02 PCT APPLICATION 56 of 74 transmission of the user data towards the host 602 via the network node 604.
  • the host 602 may process audio and video data which may have been retrieved from a UE for use in creating maps. As another example, the host 602 may collect and analyze real-time data to assist in controlling vehicle congestion (e.g., controlling traffic lights). As another example, the host 602 may store surveillance video uploaded by a UE. As another example, the host 602 may store or control access to media content such as video, audio, VR or AR which it can broadcast, multicast or unicast to UEs. As other examples, the host 602 may be used for energy pricing, remote control of non-time critical electrical load to balance power generation needs, location services, presentation services (such as compiling diagrams etc.
  • a measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve.
  • the measurement procedure and/or the network functionality for reconfiguring the OTT connection may be implemented in software and hardware of the host 602 and/or UE 606.
  • FIGURE 9 is a flowchart illustrating an example method 900 in a wireless device, according to certain embodiments. In particular embodiments, one or more steps of FIGURE 9 may be performed by UE 200 described with respect to FIGURE 4.
  • the wireless device is operable to modify a timing advance (TA) value.
  • the TA value is based at least in part on a position estimate of the wireless device and a timing adjustment value.
  • the wireless device is operating in a non- terrestrial network.
  • the wireless device may update the timing adjustment value according to any of the embodiments and examples described herein.
  • the wireless device calculates a TA value for uplink transmission using the updated timing adjustment value.
  • the first satellite position estimate and the second satellite position estimate are used for calculating the ⁇ T c A om , ad m j on term in the TA formula.
  • the difference between the first satellite position estimate satellite position estimate is represented as Terror_UE_position_and_common_TA.
  • the wireless device transmits an uplink transmission using the calculated TA value. P110778WO02 PCT APPLICATION 60 of 74
  • the wireless device may transmit an indication to the network node of the updated timing adjustment value.
  • FIGURE 11 is a flowchart illustrating an example method 1100 in a wireless communication system, according to certain embodiments. In particular embodiments, one or more steps of FIGURE 11 may be performed by UE 200 described with respect to FIGURE 4 and network node 300 described with respect to FIGURE 5. The UE and network node may be operating in a non-terrestrial network.
  • the network node may receive, from the wireless device, an indication that the wireless device updated the timing adjustment value.
  • the indication may indicate that the timing adjustment value changed and/or the indication may include the updated timing adjustment value.
  • the wireless device transmits, to the network node, an uplink transmission using the calculated TA value.
  • the network node may transmit, to the wireless device, a timing advance command comprising an indication of an updated timing adjustment value. For example, based on the indication received in step 1118, the network node may determine to recalculate a timing adjustment value for the wireless device and send the updated timing adjustment value to the wireless device. The new timing adjustment value may override the value previously adjusted by the wireless device.
  • P110778WO02 PCT APPLICATION 61 of 74 Modifications, additions, or omissions may be made to method 1100 of FIGURE 11. Additionally, one or more steps in the method of FIGURE 11 may be performed in parallel or in any suitable order.
  • the computing devices described herein e.g., UEs, network nodes, hosts
  • other embodiments may comprise computing devices with different combinations of components. It is to be understood that these computing devices may comprise any suitable combination of hardware and/or software needed to perform the tasks, features, functions and methods disclosed herein.
  • non-computationally intensive functions of any of such components may be implemented in software or firmware and computationally intensive functions may be implemented in hardware.
  • some or all of the functionality described herein may be provided by processing circuitry executing instructions stored on in memory, which in certain embodiments may be a computer program product in the form of a non-transitory computer- readable storage medium.
  • some or all of the functionality may be provided by the processing circuitry without executing instructions stored on a separate or discrete device-readable storage medium, such as in a hard-wired manner.
  • the processing circuitry can be configured to perform the described functionality.
  • a method performed by a base station comprising: any of the steps, features, or functions described above with respect to base station, either alone or in combination with other steps, features, or functions described above.
  • the method of the previous embodiment further comprising one or more additional base station steps, features or functions described above.
  • the method of any of the previous embodiments further comprising: obtaining user data; and forwarding the user data to a host computer or a wireless device.
  • a mobile terminal comprising: processing circuitry configured to perform any of the steps of any of the Group A embodiments; and power supply circuitry configured to supply power to the wireless device.
  • the communication system of the previous 3 embodiments wherein: the processing circuitry of the host computer is configured to execute a host application, thereby providing the user data; and the UE comprises processing circuitry configured to execute a client application associated with the host application.
  • the method of the previous embodiment further comprising, at the base station, transmitting the user data.
  • a communication system including a host computer comprising a communication interface configured to receive user data originating from a transmission from a user equipment (UE) to a base station, wherein the base station comprises a radio interface and processing circuitry, the base station’s processing circuitry configured to perform any of the steps of any of the Group B embodiments.
  • P110778WO02 PCT APPLICATION 68 of 74 The communication system of the previous embodiment further including the base station.
  • the communication system of the previous 3 embodiments wherein: the processing circuitry of the host computer is configured to execute a host application; the UE is configured to execute a client application associated with the host application, thereby providing the user data to be received by the host computer.
  • the method of the previous embodiment further comprising at the base station, receiving the user data from the UE.
  • the method of the previous 2 embodiments further comprising at the base station, initiating a transmission of the received user data to the host computer.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Physics & Mathematics (AREA)
  • Astronomy & Astrophysics (AREA)
  • Aviation & Aerospace Engineering (AREA)
  • General Physics & Mathematics (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Selon certains modes de réalisation, un procédé est mis en œuvre par un dispositif sans fil pour modifier une valeur d'avance temporelle (TA) représentée par la formule TA, le procédé consistant à : obtenir une première estimation de position du dispositif sans fil utilisée pour calculer le terme (a) dans la formule TA; recevoir une première commande d'avance temporelle en provenance d'un nœud de réseau, la première avance temporelle comprenant une valeur NTA; obtenir une seconde estimation de position du dispositif sans fil utilisé pour calculer le (a) dans la formule TA; ajuster la valeur NTA sur la base de la seconde estimation de position pour supprimer la valeur correspondant à l'erreur de synchronisation éliminée de NTA, NTA_new = NTA_old - Terror_UE_position; calculer une valeur TA pour une transmission en liaison montante à l'aide de la valeur NTA ajustée; et transmettre une transmission en liaison montante à l'aide de la valeur TA calculée.
PCT/IB2025/051786 2024-02-19 2025-02-19 Modification d'avance temporelle pour réseaux non terrestres Pending WO2025177172A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CNPCT/CN2024/077528 2024-02-19
CN2024077528 2024-02-19

Publications (1)

Publication Number Publication Date
WO2025177172A1 true WO2025177172A1 (fr) 2025-08-28

Family

ID=94871434

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/IB2025/051786 Pending WO2025177172A1 (fr) 2024-02-19 2025-02-19 Modification d'avance temporelle pour réseaux non terrestres

Country Status (1)

Country Link
WO (1) WO2025177172A1 (fr)

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20230104479A1 (en) * 2021-10-01 2023-04-06 Qualcomm Incorporated Timing advance slew rate control in a non-terrestrial network

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20230104479A1 (en) * 2021-10-01 2023-04-06 Qualcomm Incorporated Timing advance slew rate control in a non-terrestrial network

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
QUALCOMM INCORPORATED: "Timing requirements in NTN Systems", vol. RAN WG4, no. Electronic Meeting; 20210519 - 20210527, 11 May 2021 (2021-05-11), XP052007904, Retrieved from the Internet <URL:https://ftp.3gpp.org/tsg_ran/WG4_Radio/TSGR4_99-e/Docs/R4-2108971.zip R4-2108971 Timing requirements in NTN Systems.docx> [retrieved on 20210511] *

Similar Documents

Publication Publication Date Title
US20250097811A1 (en) Systems and methods for reducing system information acquisition during cell reselection in a non-terrestrial network
EP4381829A1 (fr) Validité de données de système mondial de navigation par satellite dans des réseaux non terrestres
CN117321932A (zh) Ntn中的ue定时提前报告
US20250142505A1 (en) Method and Apparatus for SSB Measurement Time Configuration in Communication Network
WO2023152707A1 (fr) Combinaison d&#39;accès cho et sans rach basé sur le temps avec des autorisations ul préconfigurées restreintes
US20250159654A1 (en) Paging and system information (si) procedures under adjusted synchronization signal block measurement time configuration (smtc) in non-terrestrial networks (ntn)
US20250287461A1 (en) Ephemeris data for conditional handover
EP4569947A1 (fr) Procédés, appareil et supports lisibles par ordinateur pour déterminer une avance temporelle dans un réseau non terrestre
US20240284333A1 (en) Device reachability in a non-terrestrial network
EP4569346A1 (fr) Informations d&#39;emplacement pour mobilité en ntn
US12487366B2 (en) Methods and systems for signalling ephemeris data in a non-terrestrial network
WO2023096556A1 (fr) Systèmes et procédés pour la prise en charge de l&#39;ajustement autonome d&#39;une avance temporelle
WO2023086001A1 (fr) Systèmes et procédés pour faciliter une longue transmission en liaison montante dans des réseaux non terrestres de l&#39;internet des objets
WO2024171139A1 (fr) Activation d&#39;intervalles de mesure pour ntn
WO2025037179A1 (fr) Mécanismes pour la prise en charge d&#39;une commutation de liaison satellite ou de liaison de connexion avec une fréquence porteuse et pci inchangées
US20240188163A1 (en) Rrc connection re-establishment in iot ntn
WO2023152302A1 (fr) Accès à un réseau non terrestre
WO2025177172A1 (fr) Modification d&#39;avance temporelle pour réseaux non terrestres
US20250261092A1 (en) Systems and methods for system information accumulation in internet of things non-terrestrial networks
EP4666644A1 (fr) Activation d&#39;intervalles de mesure pour ntn
US20250133522A1 (en) Systems and methods to facilitate long uplink transmission in internet of things non-terresterial networks
WO2025210593A1 (fr) Indication de stockage et de transfert pour ntn
WO2024035965A1 (fr) Procédés d&#39;accumulation de si dans un ntn ido avec indication de temps d&#39;époque explicite et implicite
WO2025179475A1 (fr) Communication de réseau non terrestre (ntn) améliorée
WO2025216685A1 (fr) Indication de transfert intercellulaire réussi lorsque certaines conditions indiquent une défaillance de transfert intercellulaire

Legal Events

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

Ref document number: 25710128

Country of ref document: EP

Kind code of ref document: A1