IP Library › Granted Patent US 12,335,884
Granted Patent B2
US 12,335,884 · App. 17/770,660 · Granted Jun 17, 2025

Network entity for synchronization over a packet-based fronthaul network

Inventors: Eduardo Lins de Medeiros (Bromma, SE); Miguel Berg (Sollentuna, SE); Igor Almeida (Indaiatuba, BR)
Assignee: Telefonaktiebolaget LM Ericsson (publ)
H04W56/001H04L5/1469H04L27/2605
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,335,884
App. No.
17/770,660
Granted
Jun 17, 2025
Kind
B2
Abstract

A method performed by a network entity is provided. The method comprises obtaining information indicating uplink, UL, and downlink, DL, time periods in the packet-based fronthaul network occupied by Time-Division Duplex, TDD, radio transmissions transmitted and/or received by the one or more second fronthaul network units over its radio interface. The method further comprises scheduling packet-based synchronization messages between at least the one or more first fronthaul network units and the one or more second fronthaul network units over the packet-based fronthaul network based on the obtained information. A network entity is also provided, as well as, computer programs and carriers.

Claims (33)

1. A method performed by a network entity for synchronizing one or more first fronthaul network units with one or more second fronthaul network units across a packet-based fronthaul network carrying Time-Division Duplex, TDD, radio transmissions, the method comprising:

obtaining information indicating uplink, UL, time periods and downlink, DL, time periods in the packet-based fronthaul network occupied by the TDD radio transmissions transmitted and/or received by the one or more second fronthaul network units over a radio interface; and

scheduling packet-based synchronization messages for transmission between at least the one or more first fronthaul network units and the one or more second fronthaul network units over the packet-based fronthaul network, the scheduling of the packet-based synchronization messages being based on the obtained information.

2. The method according to claim 1 , wherein the scheduling of the packet-based synchronization messages is performed in a UL and DL direction over the packet-based fronthaul network during time periods not occupied by UL or DL TDD radio transmissions.

3. The method according to claim 1 , wherein scheduling of DL packet synchronization messages is performed in a DL direction over the packet-based fronthaul network during time periods that are not occupied by DL TDD radio transmissions, and scheduling of UL packet synchronization messages is performed in a UL direction over the packet-based fronthaul network during time periods that are not occupied by UL or DL TDD radio transmissions.

4. The method according to claim 1 , in case the TDD radio transmissions are part of a Long-Term Evolution, LTE, transmission, further comprising:

configuring the one or more first fronthaul network units and the one or more second fronthaul network units to not perform any assignments during a DwPTS part and/or transmissions during an UpPTS part in a special subframe, and

wherein the scheduling of the packet-based synchronization messages is further based on said configuration of the one or more first fronthaul network units and the one or more second fronthaul network units.

5. The method according to claim 1 , in case the TDD radio transmissions are part of a Long-Term Evolution, LTE, transmission, further comprising:

configuring the one or more first fronthaul network units and the one or more second fronthaul network units with a special subframe having fewer DwPTS symbols and/or UpPTS symbols than a currently configured special subframe, and

wherein the scheduling of the packet-based synchronization messages is further based on said configuration of the one or more first fronthaul network units and the one or more second fronthaul network units.

6. The method according to claim 1 , in case of having a configurable TDD split ratio between the UL and the DL time periods that are occupied by the TDD radio transmissions, further comprising:

configuring the one or more first fronthaul network units and the one or more second fronthaul network units with a TDD split ratio between the UL and the DL time periods such that one or more guard periods between the UL and the DL time periods comprise one or more OFDM symbols, and to not transmit in an n first and/or an m last of the one or more OFDM symbols of the one or more guard periods, and

wherein the scheduling of the packet-based synchronization messages is further based on said configuration of the one or more first fronthaul network units and the one or more second fronthaul network units.

7. The method according to claim 6 , wherein timing advance commands are used to extend the one or more guard periods by at least a part of an OFDM symbol.

8. The method according to claim 1 , in case of having a configurable TDD split ratio between the UL and the DL time periods that are occupied by the TDD radio transmissions, further comprising:

configuring the one or more first fronthaul network units and the one or more second fronthaul network units with a TDD split ratio between the UL and the DL time periods wherein the UL and the DL time periods comprise one or more OFDM symbols that are restricted from transmissions, and

wherein the scheduling of the packet-based synchronization messages is further based on said configuration of the one or more first fronthaul network units and the one or more second fronthaul network units.

9. The method according to claim 4 , wherein the configuring comprises transmitting configuration information to the one or more first fronthaul network units and/or the one or more second fronthaul network units.

10. The method according to claim 1 , wherein the packet-based fronthaul network is full-duplex, and the packet-based synchronization messages are timestamped data packets according to a packet-based synchronization protocol.

11. A network entity for synchronizing one or more first fronthaul network units with one or more second fronthaul network units across a packet-based fronthaul network carrying Time-Division Duplex, TDD, radio transmissions, the network entity comprising:

a memory that stores computer executable instructions; and

processing circuitry, wherein, in response to executing the computer executable instructions, the processing circuitry is configured to:

obtain information indicating uplink, UL, time periods and downlink, DL, time periods in the packet-based fronthaul network occupied by the TDD radio transmissions transmitted and/or received by the one or more second fronthaul network units over its radio interface, and schedule packet-based synchronization messages for transmission between the network entity, the one or more first fronthaul network units and the one or more second fronthaul network units over the packet-based fronthaul network, the scheduling of the packet-based synchronization messages being based on the obtained information.

12. The network entity according to claim 11 , wherein the scheduling of the packet-based synchronization messages is performed in a UL and DL direction over the packet-based fronthaul network during time periods not occupied by UL/DL TDD radio transmissions.

13. The network entity according to claim 11 , wherein the scheduling of DL packet synchronization messages is performed in a DL direction over the packet-based fronthaul network during time periods that are not occupied by DL TDD radio transmissions, and the scheduling of the packet-based synchronization messages is performed in a UL direction over the packet-based fronthaul network during time periods that are not occupied by UL or DL TDD radio transmissions.

14. The network entity according to claim 11 , wherein, in response to executing the computer executable instructions, the processing circuitry is further configured to, in case TDD radio transmissions are part of a Long-Term Evolution, LTE, transmission, configure the one or more first fronthaul network units and the one or more second fronthaul network units to not perform any assignments during a DwPTS part and/or transmissions during an UpPTS part in a special subframe, and the scheduling of the packet-based synchronization messages is further based on said configuration of the one or more first fronthaul network units and the one or more second fronthaul network units.

15. The network entity according to claim 11 , wherein, in response to executing the computer executable instructions, the processing circuitry is further configured to, in case TDD radio transmissions are part of a Long-Term Evolution, LTE, transmission, configure the one or more first fronthaul network units and the one or more second fronthaul network units with a special subframe having fewer DwPTS symbols and/or UpPTS symbols than a currently configured special subframe, and the scheduling of the packet-based synchronization messages is further based on said configuration of the one or more first fronthaul network units and the one or more second fronthaul network units.

16. The network entity according to claim 11 , wherein, in response to executing the computer executable instructions, the processing circuitry is further configured to, in case of having a configurable TDD split ratio between the UL and the DL time periods that are occupied by the TDD radio transmissions, configure the one or more first fronthaul network units and the one or more second fronthaul network units with a TDD split ratio between the UL and the DL time periods such that one or more guard periods between the UL and the DL time periods comprise one or more OFDM symbols, and to not transmit in an n first and/or an m last of the one or more OFDM symbols of the one or more guard periods, and the scheduling of the packet-based synchronization messages is further based on said configuration of the one or more first fronthaul network units and the one or more second fronthaul network units.

17. The network entity according to claim 16 , wherein, in response to executing the computer executable instructions, the processing circuitry is further configured to use timing advance commands to extend the one or more guard periods by the one or more OFDM symbols.

18. The network entity according to claim 11 , wherein, in response to executing the computer executable instructions, the processing circuitry is further configured to, in case of having a configurable TDD split ratio between the UL and the DL time periods that are occupied by the TDD radio transmissions, configure the one or more first fronthaul network units and the one or more second fronthaul network units with a TDD split ratio between the UL and the DL time periods wherein the UL and the DL time periods comprise one or more OFDM symbols that are restricted from transmissions, and the scheduling of the packet-based synchronization messages is further based on said configuration of the one or more first fronthaul network units and the one or more second fronthaul network units.

19. The network entity according to claim 14 , wherein, in response to executing the computer executable instructions, the processing circuitry is further configured to transmit configuration information to the one or more first fronthaul network units and/or the one or more second fronthaul network units.

20. The network entity according to claim 11 , wherein the packet-based fronthaul network is full-duplex, and the packet-based synchronization messages are timestamped data packets according to a packet-based synchronization protocol.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Apr 21, 2022
From: ALMEIDA, IGOR; BERG, MIGUEL; MEDEIROS, EDUARDO LINS DE
To: TELEFONAKTIEBOLAGET LM ERICSSON (PUBL)
Reel/Frame 059659/0987 →
Continuity (1)
Related Publication 20220369251A1 · Nov 17, 2022
References Cited (20)
US 20130039359A1 · Bedrosian · 2013 [cited by applicant]
US 20180206203A1 · Ruffini et al. · 2018 [cited by applicant]
US 20190116568A1 · Fertonani et al. · 2019 [cited by applicant]
US 20200413360A1 · Ruffini · 2020 [cited by examiner]
US 20210014085A1 · Chen · 2021 [cited by examiner]
US 20210195632A1 · Jungnickel · 2021 [cited by examiner]
US 20210377936A1 · Yuan · 2021 [cited by examiner]
WO 2016145371A2 · 2016 [cited by applicant]
WO 2017012635A1 · 2017 [cited by applicant]
WO 2017088911A1 · 2017 [cited by applicant]
WO 2018017468A1 · 2018 [cited by applicant]
Author Unknown, “IEEE Standard for Information technology—Telecommunications and information exchange between systems—Local and metropolitan area networks—Specific requirements; Part 3: Carrier Sense Multuple Access wit… [cited by applicant]
Author Unknown, “IEEE Standard for a Precision Clock Synchronization Protocol for Networked Measurement and Control Systems,” IEEE Standard 1588, IEEE Instrumentation and Measurement Society, Jul. 24, 2008, New York, Ne… [cited by applicant]
Author Unknown, “Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA); Physical channels and modulation (Release 15),” Technical Specification 36.211, Version 15.4.0, D… [cited by applicant]
Chitimalla, et al., “5G Fronthaul-Latency and Jitter Studies of CPRI Over Ethernet,” Journal Of Optical Communications and Networking, vol. 9, Issue 2, Feb. 2017, Optical Society of America, pp. 172-182. [cited by applicant]
Freire, et al., “Analysis of Controlled Packet Departure to Support Ethernet Fronthaul Synchronization via PTP,” International Symposium on Precision Clock Synchronization for Measurement, Control, and Communication, Se… [cited by applicant]
Mochizuki, et al., “Improving IEEE 1588v2 Clock Performance through Controlled Packet Departures,” IEEE Communications Letters, vol. 14, Issue 5, May 2010, pp. 459-461. [cited by applicant]
Venmani, et al., “On the Role of Network Synchronization for Future Cellular Networks: An Operator's Perspective,” IEEE Communications Magazine, Sep. 2016, pp. 58-64. [cited by applicant]
International Search Report and Written Opinion for International Patent Application No. PCT/SE2019/051039, mailed Nov. 10, 2020, 12 pages. [cited by applicant]
Extended European Search Report for European Patent Application No. 19949789.2, mailed Apr. 24, 2023, 9 pages. [cited by applicant]