CPR # | Consolidated Potential Requirement | Original PR # | Comment |
---|---|---|---|
CPR 7.1.1-1 | The 5G system shall be able to receive accurate timing signals from one or more independent timing source(s), which can offer a timing alternative to GNSS, e.g. TBS/MBS [7] [8]], Sync over Fiber [7]. | [PR 5.1.6-1] | |
CPR 7.1.1-2 | The 5G system shall be able to maintain accurate time synchronization as appropriate for the supported applications in the event of degradation or loss of GNSS timing signals. | [PR 5.1.6-3] |
CPR # | Consolidated Potential Requirement | Original PR # | Comment |
---|---|---|---|
CPR 7.1.2-1 | The 5G system shall monitor for timing source failure. | [PR 5.2.6.1-1] | |
CPR 7.1.2-2 | The 5G system shall be able to detect when reference timing signals (e.g., from GNSS or other timing source) are no longer viable for network time synchronization. | [PR 5.1.6-2] | |
CPR 7.1.2-3 | The 5G system shall support a mechanism to determine the time uncertainty of the 5G time synchronization. | [PR 5.4.6.1-1] | |
CPR 7.1.2-4 | The 5G system shall be able to indicate to devices (e.g., UEs, applications) that they need to use an alternate time source (e.g., to 5G system internal holdover capability, atomic clock, Sync over Fiber, TBS, GNSS), taking into account the holdover capability of the devices. | [PR 5.2.6.1-2] | |
CPR 7.1.2-5 | The 5G system shall be able to detect when a timing source fails or is restored for network time synchronization. | [PR 5.2.6.1-4] | |
CPR 7.1.2-6 | The 5G system shall support mechanisms to monitor different time sources and adopt the most appropriate. | [PR 5.4.6.1-2] | |
CPR 7.1.2-7 | The 5G system shall support a mechanism to report timing resiliency information (e.g., divergence from UTC, time uncertainty) to 3rd party applications. | [PR 5.4.6.1-3] |
CPR # | Consolidated Potential Requirement | Original PR # | Comment |
---|---|---|---|
CPR 7.1.3-1 | The 5G system shall support a mechanism for a 3rd party application to request resilient timing with specific KPIs (e.g., accuracy, interval, coverage area). | [PR 5.3.6-3] |
Use-case | Holdover Time (note 3) | Sync Target | Sync accuracy | Service area | Mobility | Remarks |
---|---|---|---|---|---|---|
Power grid (5G network) | Up to 24 hour | UTC (note 1) | <250ns-1000ns [3], [9] (note2) | < 20 km2 | low | When 5G System provides direct PTP Grandmaster capability to sub-stations |
Power grid (time synchronization device) | >5 s | UTC (note 1) | < 250ns-1000ns [3], [9] (note2) | < 20 km2 | Low | When 5G sync modem is integrated into PTP grandmaster solution (with 24h holdover capability) at sub-stations) |
NOTE 1:
A different synchronization target is acceptable as long as the offset is preconfigured when an alternatively sourced time differs from GNSS. In this case, a 5G end device shall provide PPS output which can be used for measuring the difference.
NOTE 2:
Use case [New] in [9] illustrates the different accuracy measurements based on different configurations needed to support the underlying requirements from IEC [3]. The range is between 250 ns and 1000 ns. The actual requirement depends on the specific deployment.
NOTE 3:
This requirement will vary based on deployment options.
|
Type of trading activity | Maximum divergence from UTC | Granularity of the timestamp (note 1) |
---|---|---|
Activity using high frequency algorithmic trading technique | 100μs | ≤ 1μs |
Activity on voice trading systems | 1s | ≤ 1s |
Activity on request for quote systems where the response requires human intervention or where the system does not allow algorithmic trading | 1s | ≤ 1s |
Activity of concluding negotiated transactions | 1s | ≤ 1s |
Any other trading activity | 1ms | ≤ 1ms |
NOTE 1:
Only relevant for the case where the time synchronization assists in configuring the required granularity for the timestamp (for direct use), otherwise it will be configured separately as part of the financial transaction timestamp process.
|