US20160072604A1 - Providing packet synchronization in a virtual private network - Google Patents

Providing packet synchronization in a virtual private network Download PDF

Info

Publication number
US20160072604A1
US20160072604A1 US14/778,229 US201314778229A US2016072604A1 US 20160072604 A1 US20160072604 A1 US 20160072604A1 US 201314778229 A US201314778229 A US 201314778229A US 2016072604 A1 US2016072604 A1 US 2016072604A1
Authority
US
United States
Prior art keywords
node
synchronization
service provider
packet
time
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.)
Abandoned
Application number
US14/778,229
Other languages
English (en)
Inventor
Zhengfu Zhao
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
Assigned to TELEFONAKTIEBOLAGET L M ERICSSON (PUBL) reassignment TELEFONAKTIEBOLAGET L M ERICSSON (PUBL) ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: Zhao, Zhengfu
Publication of US20160072604A1 publication Critical patent/US20160072604A1/en
Abandoned legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04J—MULTIPLEX COMMUNICATION
    • H04J3/00—Time-division multiplex systems
    • H04J3/02—Details
    • H04J3/06—Synchronising arrangements
    • H04J3/0635—Clock or time synchronisation in a network
    • H04J3/0638—Clock or time synchronisation among nodes; Internode synchronisation
    • H04J3/0658—Clock or time synchronisation among packet nodes
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04J—MULTIPLEX COMMUNICATION
    • H04J3/00—Time-division multiplex systems
    • H04J3/02—Details
    • H04J3/06—Synchronising arrangements
    • H04J3/0635—Clock or time synchronisation in a network
    • H04J3/0638—Clock or time synchronisation among nodes; Internode synchronisation
    • H04J3/0641—Change of the master or reference, e.g. take-over or failure of the master
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L49/00—Packet switching elements
    • H04L49/35—Switches specially adapted for specific applications
    • H04L49/351—Switches specially adapted for specific applications for local area network [LAN], e.g. Ethernet switches

Definitions

  • the invention relates to the field of providing packet synchronization in a Virtual Private Network.
  • AAV networks are used widely in some countries in Mobile Backhaul transport.
  • the backhaul portion of a communications network includes intermediate links between the core (or backbone) network and smaller subnetworks at the edge of the communications network.
  • AAV providers provide data carrying bandwidth that can be rented or purchased by a Service Provider for communicating between the core network and an end user.
  • the AAV provider usually uses a Virtual Private Network (VPN), typically L3VPN, L2VPN or L1VPN, to service several different Service Providers.
  • VPN Virtual Private Network
  • FIG. 1 illustrates schematically an exemplary network in which Service Provider A and Service Provider B have core network elements (NE) 1 and 2 respectively.
  • core network elements include Base Station Controller (BSC), Radio Network Controllers (RNC) and Serving Gateways (SGw).
  • BSC Base Station Controller
  • RNC Radio Network Controllers
  • SGw Serving Gateways
  • Service Providers A and B provide service to end users via access network elements 3 and 4 respectively. Both Service Provider A and Service Provider B obtain AAV mobile backhaul from network elements 5 and 6 .
  • the mobile backhaul network has to handle packet networks.
  • the packet network must provide frequency, phase and/or time synchronization for the Radio Access Network (RAN) for different application cases. This is defined, in, for example, ITU-T G.8271/Y.1366, “Time and phase synchronization aspects of packet networks”, which defines the “time and phase synchronization aspects of packet networks” with the performance requirements from different RANs.
  • RAN Radio Access Network
  • Service Provider A and Service Provider B typically require a different frequency, time and phase synchronization from the Mobile Backhaul transport.
  • the AAV network is the packet network carrier providing a VPN service for the Service Providers.
  • the frequency, time and phase synchronization from packet based synchronization is heavily impacted by jitter (delay variant) and delay of the packet network.
  • packet synchronization frames passing through the AAV network are assigned the highest Quality of Service (QoS) value with sufficient bandwidth.
  • QoS Quality of Service
  • Time stamping information for end to end packets is not handled by intermediate AAV nodes because the AAV network would need to supply several different Service Providers with different time stamps if those Service Providers have different clock domains. In this case, larger frame sizes mixed with the synchronization frames would introduce unacceptable levels of jitter into the AAV network, especially if there are multiple hops between nodes within the AAV network.
  • AAV nodes can therefore only provide frequency, time and phase synchronization for use by other nodes within the AAV network (the jitter from jumbo frames also has impact on AAV node-self synchronization accuracy if the network Quality-of-Service (QoS) is not adequately planned), and cannot provide frequency, time and phase synchronization for use by nodes in the core network or at the other end of the communications network.
  • QoS Quality-of-Service
  • a node that provides backhaul service to a plurality of Service Providers in the Virtual Private Network receives a synchronization control packet. It identifies a characteristic relating to the identity of a Service Provider of the plurality of Service Providers, and provides synchronization information to the node on the basis of the identified characteristic. Subsequent packets associated with the identified Service Provider are handled using the synchronization information.
  • This has the advantage that a single node providing synchronization in the backhaul can be synchronize according to the requirements and synchronization of different Service Providers.
  • the packet synchronization comprises frequency synchronization, in which case a multiple output clock is used, each output providing frequency synchronization according to the identified characteristic of the Service Provider.
  • the step of identifying the characteristic relating to the identity of the Service Provider comprises identifying an Ethernet port at which the synchronization control packet was received. This requires very little processing to identify the Service Provider.
  • the method optionally comprises, for each Service Provider of the plurality of service Providers, providing a packet time engine instance, each packet time engine instance arranged to provide time and phase synchronization specific to the Service Provider.
  • the Service Provider associated with the synchronization control packet is identified.
  • the packet time engine instance associated with the identified Service Provider is identified.
  • the time and/or phase data from the packet time engine instance is then used to synchronize the node.
  • the method is performed on a vessel or a vehicle.
  • a node for providing packet synchronization in a Virtual Private Network providing backhaul service to a plurality of Service Providers.
  • the node is provided with a receiver arranged to receive a synchronization control packet and a processor arranged to identify a characteristic relating to the identity of a Service Provider of the plurality of Service Providers.
  • the processor is further arranged to provide synchronization information on the basis of the identified characteristic, and the processor is also arranged to handle subsequent packets associated with the identified Service Provider using the synchronization information. This allows the node to provide synchronization to packets depending on the identity of the Service Provider associated with the packets.
  • the packet synchronization comprises frequency synchronization, in which case the node is provided with a multiple output clock, each output arranged to provide frequency synchronization according to the identified characteristic of the Service Provider.
  • the processor is arranged to identify the characteristic relating to the identity of the Service Provider by identifying an Ethernet port at which the synchronization control packet was received.
  • the node is provided with a plurality of packet time engine instances.
  • Each packet time engine instance is associated with a Service Provider, and is arranged to provide time and phase data specific to the associated Service Provider.
  • the processor is also arranged to identify the Service Provider associated with the synchronization control packet, determine the packet time engine instance associated with the identified Service Provider, and use any of the time and phase data from the clock instance to synchronize the node.
  • the node optionally comprises any of a router node and a switch node.
  • a computer program that comprises computer readable code which, when run on a node in a communications network, causes the node to perform the method as described above in the first aspect.
  • a computer program product comprising a non-transitory computer readable medium and a computer program which, when run on a node in a communications network, causes the node to perform the method as described above in the first aspect, wherein the computer program is stored on the computer readable medium.
  • a vessel or vehicle comprising the node as described above in the second aspect.
  • FIG. 1 illustrates schematically in a block diagram an exemplary network architecture for a mobile backhaul network
  • FIG. 2 is a flow diagram showing exemplary steps for providing synchronization
  • FIG. 3 illustrates schematically in a block diagram exemplary functions for providing frequency synchronization
  • FIG. 4 illustrates schematically in a block diagram exemplary functions for providing time/phase synchronization
  • FIG. 5 illustrates schematically in a block diagram an exemplary Packet Time Engine
  • FIG. 6 illustrates schematically in a block diagram an exemplary node according to an embodiment
  • FIG. 7 illustrates schematically in a block diagram an exemplary network architecture for a mobile backhaul network using a synchronization node
  • FIG. 8 illustrates schematically in a block diagram an exemplary vehicle or vessel.
  • VPS Virtual Private Synchronization
  • AAV Alternative Access Vendor
  • Methods and apparatus are described that allow for frequency synchronization in an AAV network, time/phase synchronization in the AAV network, and a combination of frequency, time and phase synchronization.
  • a node in the backhaul network that is responsible for packet synchronization such as an AAV node is itself synchronized using synchronization control packets.
  • VPS silicon blocks are synchronized to ensure that they have the correct frequency, time and phase synchronization from the synchronization control packet. Packets subsequently handled by the node can then be synchronized by, for example, time stamping, or control frames sent to downstream nodes can be synchronized.
  • a synchronization control packet synchronizes the node, and the node subsequently uses its synchronized time/phase and/or frequency values to synchronize subsequent packets that it handles.
  • FIG. 2 is a flow diagram illustrating steps of embodiments. The following numbering corresponds to that of FIG. 2 .
  • a node that provides backhaul service to a plurality of Service Providers in a VPN receives a synchronization control packet.
  • a characteristic relating to the identity of one of the Service Providers is identified. This may be, for example, a port on which the synchronization control packet was received, or header information, depending on embodiments used as described below.
  • an identity of the Service Provider can be determined by identifying an Ethernet port on which the frequency clock was selected from and/or the synchronization control packet was received.
  • a multiple output clock is used to provide frequency synchronization to the node depending on the identity of the Ethernet port on which the frequency clock was selected from and/or the synchronization control packet was received.
  • the identity of the Service Provider is used to determine which clock instance is associated with the Service Provider that is handling the packet.
  • the node is provided with time/frequency synchronization using the clock instance associated with the Service Provider.
  • steps S 3 -S 4 and S 6 -S 8 are not incompatible.
  • the same node can provide either frequency synchronization, time/phase synchronization, or both frequency and time/phase synchronization.
  • the multiple L1 physical synchronization domain is referred to herein as a frequency Virtual Private Synchronization domain.
  • the multiple time/phase domain per network element (NE) is referred to herein as a time/phase Virtual Private Synchronization domain.
  • FIG. 3 shows a frequency VPS function 7 .
  • the frequency function is provided with a multiple output clock multiplexer (MUX) 8 that receives inputs from different Ethernet ports (in this example, Ports 1 to 6 ).
  • the MUX 8 allocates and assigns different frequency sources to different clock select blocks.
  • VPS 1 clock select block 9 and VPS 2 clock select block 10 are shown.
  • a system T 0 clock select block 11 is provided that is a legacy standard function currently used to ensure backwards compatibility with legacy networks.
  • VPS-n clock select block 12 is also illustrated.
  • the clock loop avoidance is needed when selecting the right inputs to each VPS, similar to existing clock loop avoidance technology.
  • VPS clock select blocks 9 , 10 feed into a clock input 13 which in turn feeds into the six Ethernet ports 14 - 19 illustrated.
  • VPS 1 clock select block 9 and VPS 2 clock select block 10 have a frequency output that is used to drive corresponding VPS ports.
  • VPS 1 clock select block 9 drives the frequency of Ethernet Port 1 and Port 2
  • VPS 2 clock select block 10 drives the frequency of Ethernet Ports 3 and Port 4 .
  • Each VPS clock select block 9 , 10 may be used for one Service Provider that uses the AAV backhaul network.
  • VPS 1 clock select block 9 may be used for Service Provider A
  • VPS 2 clock select block 10 may be used for Service Provider B.
  • the Service Provider can be identified by the port on which on which the frequency clock was selected from and/or a synchronization control packet is received.
  • the number of the VPS clock select blocks supported by a node is typically determined by the system parameters design.
  • the example of two VPS clock select blocks 9 , 10 and one system T 0 clock 11 is shown in FIG. 3 . It should be noted that the number of the VPS clock select blocks will typically be in the range of 1 to 16, although fewer VPS clock select blocks reduces the complexity of the node.
  • FIG. 3 is with reference to Ethernet frequency synchronization.
  • PDH plesiochronous digital hierarchy
  • SDH Synchronous Digital Hierarchy
  • SONET Synchronous Optical Networking
  • OTN Optical Transport Network
  • the clock select blocks 9 , 10 may derive their frequencies from a high precision, free running Oven Controlled Crystal Oscillator (OCXO) driven clock source or another type of clock source such as Ethernet Port 1 to Ethernet Portio of the synchronization Ethernet.
  • OXO Oven Controlled Crystal Oscillator
  • Time/phase Virtual Private Synchronization can also be provided in addition to or as an alternative to frequency Virtual Private Synchronization.
  • FIG. 4 illustrates a time/phase VPS function 20 .
  • the time/phase VPS function 20 handles packets in the AAV network from two different Service Providers, although it will be appreciated that it may handle packets for any number of Services Providers.
  • the exemplary time/phase VPS function 20 is provided with instances of three Packet Time Engines (PTE) 21 , 22 , 23 .
  • PTE Packet Time Engines
  • One PTE instance 23 may be used for local system time/phase synchronization, and the other two PTE instances 21 , 22 are used for time/phase synchronization for Service Provider A and Service Provider B respectively.
  • the dashed lines in FIG. 4 refer to packet synchronization control frames from different Service Providers using the AAV network.
  • Each PTE 21 , 22 , 23 is associated with a Service Provider (SP) packet flow.
  • SP Service Provider
  • PTE 1 21 is associated with SP flow 1 24
  • PTE 2 22 is associated with SP flow 2 25
  • PTE 3 23 is associated with SP flow 3 26 .
  • SP flow 1 24 and SP flow 2 25 use Ethernet Ports 1 14 and Ethernet Port 2 15
  • SP flow 3 26 uses Ethernet Port 3 16 and Ethernet Port 4 17 .
  • FIG. 5 illustrates an exemplary PTE instance 21 .
  • the PTE instance 21 is provided with time control 27 , a time reference selector 28 , a frequency reference selector 28 a , a time-frequency generator 29 and a time counter 30 , along with a packet synchronization frequency output.
  • Each PTE instance 21 , 22 , 23 is typically used by one time/frequency VPS instance, and is therefore used for the packets relating to a single Service Provider.
  • the frequency reference selector 28 a obtains information from a source such as an Ethernet Equipment Clock (EEC), an SDH Equipment Clock (SEC), an OCXO or another type of L1 physical clock source.
  • EEC Ethernet Equipment Clock
  • SEC SDH Equipment Clock
  • OCXO another type of L1 physical clock source.
  • the time/phase VPS function 20 has a packet switching system that classifies packet flows (shown as dark arrows in FIG. 4 ). Each packet flow typically includes embedded packet synchronization control frames. A packet flow passes through the traffic ports, the ingress packet synchronization control frames are filtered out from the packet flow, and sent to the associated PTE instance. So, for example, the packet synchronization control frames for SP flow 1 24 would be sent to PTE 1 21 . Egress packet synchronization control frames are subsequently sent from the associated PTE instance to be mixed with the packet flow output at the relevant traffic ports.
  • Each PTE instance 21 maintains independent time-counter 30 .
  • the independent time-counter 30 is used to perform time-stamping of a packet synchronization control frame alone within each customer traffic flow.
  • the time-counter uses a reference time required by the associated Service Provider.
  • two flows (in this example, SP flow 1 and SP flow 2 ) use the same Ethernet Ports 14 , 15 .
  • they use difference PTE instances 21 , 22 because the flows arise from different Service Providers.
  • Each PTE instance 21 , 22 therefore provides a time stamp to the packet synchronization control frames of the packet flows that is required by the associated Service Provider.
  • the time/phase function 20 in the AAV node allows the AAV node in the backhaul to provide Service Provider A and Service Provider B with different packet synchronization domains for time/phase synchronization of those Service Providers packet synchronization control frames.
  • This allows, for example, multiple instances of the types of transparent clock and boundary clock defined in IEEE1588v2 to be provided at the same AAV node running Virtual Private Synchronization of the Packet System.
  • the transparent clock is not limited to the multiple synchronization instances. Even with a single synchronization instance, there are the possibilities for the transparent clock to support multiple Service Providers.
  • a typical AAV node in the backhaul will therefore have the capability of providing both frequency synchronization and time/phase synchronization.
  • the functions shown in FIGS. 4 , 5 and 6 can therefore be provided in a single node, although it will be appreciated that they could be provided in separate nodes.
  • a single node is advantageous especially in the case where the L1 physical synchronization is used to drive the frequency and synchronization packet layer is used to drive the time/phase.
  • the synchronization node 31 that can provide both time/phase and frequency synchronization.
  • the synchronization node 31 is provided with a receiver 32 for receiving packets, a processor 33 that can implement the frequency function 7 and/or the time/phase function 20 , and a transmitter 34 for forwarding the packets.
  • the synchronization node 31 provides synchronization to packets in the AAV network.
  • the processor identifies a characteristic of the Service Provider associated with an incoming data packet (for example, by identifying an associated Ethernet Port as described above), and provides frequency and/or time/phase synchronization as required on the basis of the identified Service Provider.
  • the node may also be provided with a non-transitory computer readable medium in the form of a memory 35 that can store a computer program 36 which, when executed by the processor 33 , causes the synchronization node 31 to behave as described above.
  • the computer program 36 may also be provided from an external non-transitory computer readable medium 37 , such as a Compact Disk.
  • a synchronization node 31 may use one or more clocks 37 such as an OCXO-driven clock, to drive the frequency and time/phase synchronization.
  • clocks 37 such as an OCXO-driven clock
  • the synchronization node 31 may be a stand-alone node, or co-located in another node, such as a switch or a router, in the AAV network.
  • FIG. 7 shows a network similar to that of FIG. 1 . In this case, two exemplary locations of the synchronization node 31 are shown; in one embodiment, a synchronization node 31 a is co-located in a Network Element AAV 2 6 , where AAV 2 6 is a node such as a switch or a router. In another embodiment, the synchronization node 31 b is a stand-alone node in the AAV network.
  • the synchronization node 31 may be located in a vessel or vehicle 38 , examples of which are a ship, a car, a truck or train.
  • Isolated frequency domains can be provided with multiple instances dependent on the identity of the Service Provider from a single node as the frequency Virtual Private Synchronization.
  • the isolated time/phase domain can have multiple instances support from a single node as the time/phase Virtual Private Synchronization.
  • both frequency VPS and time/phase VPS can be provided from a single node.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Synchronisation In Digital Transmission Systems (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
US14/778,229 2013-03-19 2013-03-19 Providing packet synchronization in a virtual private network Abandoned US20160072604A1 (en)

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2013/072838 WO2014146239A1 (fr) 2013-03-19 2013-03-19 Fourniture d'une synchronisation de paquets dans un réseau privé virtuel

Publications (1)

Publication Number Publication Date
US20160072604A1 true US20160072604A1 (en) 2016-03-10

Family

ID=51579264

Family Applications (1)

Application Number Title Priority Date Filing Date
US14/778,229 Abandoned US20160072604A1 (en) 2013-03-19 2013-03-19 Providing packet synchronization in a virtual private network

Country Status (4)

Country Link
US (1) US20160072604A1 (fr)
EP (1) EP2976922B1 (fr)
CN (1) CN105409300A (fr)
WO (1) WO2014146239A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20170105126A1 (en) * 2015-10-12 2017-04-13 T-Mobile Usa, Inc. Cellular Backhaul Coverage Algortihms

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP7304801B2 (ja) * 2019-12-12 2023-07-07 三菱電機株式会社 中継装置及び通信システム

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20100074278A1 (en) * 2008-09-22 2010-03-25 Iouri Dobjelevski Timing Distribution Within a Network Element While Supporting Multiple Timing Domains
US20120243585A1 (en) * 2011-03-24 2012-09-27 Fujitsu Ten Limited Communication system and communication apparatus
US20130039220A1 (en) * 2009-12-17 2013-02-14 Stefano Ruffini Configuration of synchronisation network having synchronization trails for time sync and frequency sync
US20140019609A1 (en) * 2012-07-10 2014-01-16 Nathaniel C. Williams Methods and Computer Program Products for Analysis of Network Traffic by Port Level and/or Protocol Level Filtering in a Network Device

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101958743B (zh) * 2009-07-13 2014-12-10 中兴通讯股份有限公司 中继链路的同步信号映射方法及装置
CN102026364B (zh) * 2009-09-17 2014-07-09 华为技术有限公司 精确时间协议报文处理方法和时钟设备
WO2011074529A1 (fr) * 2009-12-18 2011-06-23 日本電気株式会社 Système de synchronisation d'heure, nœud esclave, procédé de synchronisation d'heure et programme de synchronisation d'heure
US8966292B2 (en) * 2011-01-03 2015-02-24 Qualcomm Incorporated Performance improvements in a wireless client terminal using assistance from a proxy device
JP5701708B2 (ja) * 2011-07-26 2015-04-15 株式会社日立製作所 通信システム

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20100074278A1 (en) * 2008-09-22 2010-03-25 Iouri Dobjelevski Timing Distribution Within a Network Element While Supporting Multiple Timing Domains
US20130039220A1 (en) * 2009-12-17 2013-02-14 Stefano Ruffini Configuration of synchronisation network having synchronization trails for time sync and frequency sync
US20120243585A1 (en) * 2011-03-24 2012-09-27 Fujitsu Ten Limited Communication system and communication apparatus
US20140019609A1 (en) * 2012-07-10 2014-01-16 Nathaniel C. Williams Methods and Computer Program Products for Analysis of Network Traffic by Port Level and/or Protocol Level Filtering in a Network Device

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20170105126A1 (en) * 2015-10-12 2017-04-13 T-Mobile Usa, Inc. Cellular Backhaul Coverage Algortihms
US9826414B2 (en) * 2015-10-12 2017-11-21 T-Mobile Usa, Inc. Cellular backhaul coverage algorithms
US9986441B2 (en) 2015-10-12 2018-05-29 T-Mobile Usa, Inc. Cellular backhaul coverage algorithms

Also Published As

Publication number Publication date
CN105409300A (zh) 2016-03-16
EP2976922A1 (fr) 2016-01-27
EP2976922A4 (fr) 2016-03-16
WO2014146239A1 (fr) 2014-09-25
EP2976922B1 (fr) 2020-06-17

Similar Documents

Publication Publication Date Title
Nasrallah et al. Ultra-low latency (ULL) networks: The IEEE TSN and IETF DetNet standards and related 5G ULL research
US20230198868A1 (en) Intent-driven cloud branches
US10476657B2 (en) Device and method for supporting clock transfer of multiple clock domains
CN108353314B (zh) 切换用于通过提供回程和前传两者（xhaul）连接性的传输网络的传输的至少两个类型的数据信号
EP1985084B1 (fr) Système et procédé de synchronisation de paquets de services d'émulation de circuits sur des réseaux
EP3468123A1 (fr) Procédé et dispositif devant être utilisés dans le traitement d'un trafic à faible latence
US20180176090A1 (en) Pre-scheduled and pre-configured time-dependent bulk rerouting in transport networks
KR101488233B1 (ko) 패킷-스위칭된 네트워크의 마스터 및 슬레이브 클록들을 동기화하기 위한 비-간섭적인 방법, 및 연관된 동기화 디바이스들
US8644349B2 (en) Clock recovery in a system which transports TDM data over a packet-switched network
Bhattacharjee et al. Network slicing for TSN-based transport networks
Nasrallah et al. Ultra-low latency (ULL) networks: A comprehensive survey covering the IEEE TSN standard and related ULL research
Striffler et al. Time-sensitive networking in 5th generation cellular networks-current state and open topics
Kamoun et al. IP/MPLS networks with hardened pipes: service concepts, traffic engineering and design considerations
EP2976922B1 (fr) Fourniture d'une synchronisation de paquets dans un réseau privé virtuel
Li et al. X-Ethemet: Enabling integrated fronthaul/backhaul architecture in 5G networks
WO2013029453A1 (fr) Procédé et système de synchronisation pour traverser le réseau synchrone d'un tiers
KR20060113834A (ko) 레지덴셜 이더넷에서 수퍼 프레임의 시작에 대한 주기적동기 방법
Salmelin et al. Mobile backhaul
Toy Networks and services: carrier ethernet, PBT, MPLS-TP, and VPLS
US8503458B1 (en) Methods and apparatus for characterizing adaptive clocking domains in multi-domain networks
Paulo et al. FPGA-based testbed for synchronization on Ethernet fronthaul with phase noise measurements
US8416813B1 (en) Methods and apparatus for clocking domain discovery in multi-domain networks
Chowdhury Packet Timing: Precision Time Protocol
Nasrallah Time Sensitive Networking in Multimedia and Industrial Control Applications
US9525615B2 (en) Systems and methods for implementing multiple ISIS routing instances on a network element

Legal Events

Date Code Title Description
AS Assignment

Owner name: TELEFONAKTIEBOLAGET L M ERICSSON (PUBL), SWEDEN

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:ZHAO, ZHENGFU;REEL/FRAME:037093/0439

Effective date: 20130506

STPP Information on status: patent application and granting procedure in general

Free format text: NON FINAL ACTION MAILED

STCB Information on status: application discontinuation

Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION