Project

General

Profile

Actions

Feature #1526

open

Acquire/update timing advance (TA)

Added by zecke about 8 years ago. Updated about 3 years ago.

Status:
Stalled
Priority:
Normal
Assignee:
Target version:
-
Start date:
02/22/2016
Due date:
% Done:

30%

Spec Reference:

Description

Currently the TA is derived from the initial RACH request and never updated during the lifetime of a TBF.

Is this handled correctly for network initiated DL TBF establishment?

TS 44.018, 3.5.3.1.2 asks for TA determination on DL TBF establshment if the MS is idle and the TA is not known (see "If the network does not have a valid timing advance ...").

Other related issues:

  • The burst timing info (qta) should be applied (see #1705)
  • Support access bursts on PDCH which can be requested by the PCU if the current TA is unknown (44.060)

Related issues

Related to OsmoPCU - Feature #1545: continuous timing advance loop using PTCCHStalledfixeria02/23/2016

Actions
Related to OsmoPCU - Feature #1531: Use the burst timing information to compute the timing advanceClosedlaforge02/22/2016

Actions
Related to OsmoPCU - Bug #1524: PACCH on the wrong timeslotFeedbackroh02/22/2016

Actions
Related to OsmoPCU - Bug #3472: GPRS connection is in a state where pdp-context is active, but data TX cannot initiate from Network side.Closedkeith08/18/2018

Actions
Related to OsmoBTS - Feature #2977: OsmoBTS measurment processing at L1SAP too complex / pass measurements along with dataStalleddexter02/21/2018

Actions
Actions

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)