WO2022100110A1 - 网络同步的方法、装置、设备、系统及可读存储介质 - Google Patents

网络同步的方法、装置、设备、系统及可读存储介质 Download PDF

Info

Publication number
WO2022100110A1
WO2022100110A1 PCT/CN2021/103822 CN2021103822W WO2022100110A1 WO 2022100110 A1 WO2022100110 A1 WO 2022100110A1 CN 2021103822 W CN2021103822 W CN 2021103822W WO 2022100110 A1 WO2022100110 A1 WO 2022100110A1
Authority
WO
WIPO (PCT)
Prior art keywords
synchronization
flexe
information
network device
mode indication
Prior art date
Application number
PCT/CN2021/103822
Other languages
English (en)
French (fr)
Inventor
江元龙
孟凡顺
吕京飞
陈井凤
Original Assignee
华为技术有限公司
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 华为技术有限公司 filed Critical 华为技术有限公司
Priority to EP21890641.0A priority Critical patent/EP4236121A4/en
Publication of WO2022100110A1 publication Critical patent/WO2022100110A1/zh
Priority to US18/317,697 priority patent/US20230291537A1/en

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04JMULTIPLEX COMMUNICATION
    • H04J3/00Time-division multiplex systems
    • H04J3/16Time-division multiplex systems in which the time allocation to individual channels within a transmission cycle is variable, e.g. to accommodate varying complexity of signals, to vary number of channels transmitted
    • H04J3/1605Fixed allocated frame structures
    • H04J3/1652Optical Transport Network [OTN]
    • H04J3/1658Optical Transport Network [OTN] carrying packets or ATM cells
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L7/00Arrangements for synchronising receiver with transmitter
    • H04L7/0079Receiver details
    • H04L7/0087Preprocessing of received signal for synchronisation, e.g. by code conversion, pulse generation or edge detection
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04JMULTIPLEX COMMUNICATION
    • H04J3/00Time-division multiplex systems
    • H04J3/02Details
    • H04J3/06Synchronising arrangements
    • H04J3/0635Clock or time synchronisation in a network
    • H04J3/0638Clock or time synchronisation among nodes; Internode synchronisation
    • H04J3/0658Clock or time synchronisation among packet nodes
    • H04J3/0661Clock or time synchronisation among packet nodes using timestamps
    • H04J3/0667Bidirectional timestamps, e.g. NTP or PTP for compensation of clock drift and for compensation of propagation delays
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04JMULTIPLEX COMMUNICATION
    • H04J3/00Time-division multiplex systems
    • H04J3/02Details
    • H04J3/06Synchronising arrangements
    • H04J3/0635Clock or time synchronisation in a network
    • H04J3/0638Clock or time synchronisation among nodes; Internode synchronisation
    • H04J3/0647Synchronisation among TDM nodes
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04JMULTIPLEX COMMUNICATION
    • H04J2203/00Aspects of optical multiplex systems other than those covered by H04J14/05 and H04J14/07
    • H04J2203/0001Provisions for broadband connections in integrated services digital network using frames of the Optical Transport Network [OTN] or using synchronous transfer mode [STM], e.g. SONET, SDH
    • H04J2203/0073Services, e.g. multimedia, GOS, QOS
    • H04J2203/0082Interaction of SDH with non-ATM protocols
    • H04J2203/0085Support of Ethernet

Definitions

  • the embodiments of the present application relate to the field of communications technologies, and in particular, to a method, apparatus, device, system, and readable storage medium for network synchronization.
  • the Optical Internet Forum (OIF) organization initiated the flexible ethernet (FlexE) protocol on the basis of the Institute of Electrical and Electronics Engineers (IEEE) 802.3 protocol. Based on the FlexE protocol, the Ethernet interface rate can flexibly match various service scenarios.
  • FlexE flexible ethernet protocol
  • IEEE 802.3 Institute of Electrical and Electronics Engineers
  • the present application provides a method, apparatus, device, system and readable storage medium for network synchronization, so as to simplify the operation process of network synchronization and improve the efficiency of network synchronization.
  • a method for network synchronization is provided.
  • the method is applied to a first network device supporting FlexE.
  • the method includes: the first network device obtains a synchronization mode indication and synchronization information, and the synchronization mode indication is used to indicate a target network device.
  • the synchronization is performed according to the synchronization information; the first network device sends the synchronization mode indication and the synchronization information through the network supporting FlexE.
  • the method provided by the embodiment of the present application can indicate which network devices in the network devices supporting FlexE are used as target network devices to process synchronization information and the network devices to process synchronization by including a synchronization mode indication capable of instructing a target network device to perform synchronization according to synchronization information.
  • Information mode thereby realizing automatic configuration of network devices, simplifying the operation process of configuring network devices when network synchronization is required, and improving the efficiency of network synchronization.
  • sending the synchronization mode indication and synchronization information includes: sending a FlexE overhead frame, where the FlexE overhead frame includes the synchronization mode indication and synchronization information. Since the FlexE overhead frame includes the synchronization mode indication and synchronization information, the target network device can realize network synchronization based on the FlexE overhead frame without processing the service block.
  • the synchronization mode indication includes a first mode indication, and the first mode indication is used to instruct the target network device to enter the FlexE synchronization mode.
  • the first mode indication may be independent of the existing mode, or may be superimposed on the existing mode as an additional attribute, and the processing method is relatively flexible.
  • the method further includes: the first network device obtains target network device indication information, where the target network device indication information is used to indicate that the other end device of the FlexE segment or the other end device of the FlexE path is the target network equipment.
  • the target network device is further indicated by the target network device indication information, which can be realized without occupying additional resources. On the basis of indicating the target network device, resources are further saved.
  • the synchronization mode indication includes target network device indication information.
  • the FlexE overhead frame includes at least one synchronization mode indication field, and the at least one synchronization mode indication field includes a synchronization mode indication;
  • the FlexE overhead frame includes a sixth FlexE overhead block, and the sixth FlexE overhead block includes synchronization information.
  • the first synchronization mode indication field in the at least one synchronization mode indication field includes one or more bits, and the one or more bits include a synchronization mode indication; or, the at least one synchronization mode
  • the indication field includes a second synchronization mode indication field, the second synchronization mode indication field includes at least one bit, and the at least one bit includes at least a part of the synchronization mode indication. Since the synchronization mode indication can be included in different situations in the synchronization mode indication field of the FlexE overhead frame, the carrying manner of the synchronization mode indication is more flexible.
  • the sixth FlexE overhead block includes synchronization information, including: encapsulating the synchronization information into an Ethernet frame, and the sixth FlexE overhead block includes the Ethernet frame.
  • the sixth FlexE overhead block includes the Ethernet frame, including: dividing the Ethernet frame into N code blocks 1, 2, . . . , N-1, N, dividing the Code blocks 1 to i are continuously inserted into the bit field of the sixth FlexE overhead block of the first FlexE overhead frame, N is a positive integer greater than or equal to 2, i is a positive integer greater than or equal to 1 and i is less than N; The i+1 to jth code blocks in the code blocks are continuously inserted into the bit field of the sixth FlexE overhead block of the second FlexE overhead frame, and the second FlexE overhead frame is the next FlexE overhead frame adjacent to the first FlexE overhead frame , j is a positive integer and i+1 ⁇ j ⁇ N.
  • the synchronization information includes one or more of precise time synchronization protocol PTP information and synchronization status information SSM, the PTP information is used to instruct the target network device to perform time synchronization, and the synchronization status information is used to indicate the target network device.
  • Network devices perform frequency synchronization.
  • the first network device supporting flexible Ethernet FlexE includes: a customer edge device supporting FlexE or a node device supporting a FlexE network, and the network supporting FlexE includes a fragmented packet network SPN, a metro transport network Either MTN or Optical Transport Network OTN.
  • the method can be applied to different networks supporting FlexE, and the application scenarios are relatively rich.
  • a method for network synchronization is provided.
  • the method is applied to a second network device supporting flexible Ethernet FlexE.
  • the method includes: the second network device receives a synchronization mode indication and synchronization information through a network supporting FlexE, and the synchronization mode
  • the indication is used to instruct the target network device to perform synchronization according to the synchronization information; based on the synchronization mode indication, the second network device performs synchronization according to the synchronization information.
  • the synchronization mode indication includes a first mode indication, and the first mode indication is used to instruct the target network device to enter the FlexE synchronization mode; based on the synchronization mode indication, the second network device performs synchronization according to the synchronization information, including: Based on the first mode indication, the second network device enters the FlexE synchronization mode, and in the FlexE synchronization mode, the second network device performs synchronization according to the synchronization information.
  • the method further includes: the second network device receives target network device indication information, where the target network device indication information is used to indicate that the other end device of the FlexE segment or the other end device of the FlexE path is the target network equipment.
  • the synchronization mode indication includes target network device indication information.
  • receiving the synchronization mode indication and synchronization information includes: receiving a FlexE overhead frame, where the FlexE overhead frame includes the synchronization mode indication and synchronization information; based on the synchronization mode indication, before the second network device performs synchronization according to the synchronization information , the method further includes: the second network device parses the FlexE overhead frame to obtain a synchronization mode indication and synchronization information.
  • the synchronization information includes one or more of precise time synchronization protocol PTP information and synchronization status information SSM; the second network device performs synchronization according to the synchronization information, including: if the synchronization information includes PTP information, The second network device selects the time synchronization source according to the PTP information, and the second network device performs time synchronization according to the time synchronization source; if the synchronization information includes synchronization state information, the second network device selects the frequency synchronization source according to the synchronization state information, and the second network device selects the frequency synchronization source according to the synchronization state information.
  • the frequency synchronization source performs frequency synchronization.
  • the second network device supporting flexible Ethernet FlexE includes: a customer edge device supporting FlexE or a node device supporting a FlexE network, and the network supporting FlexE includes a fragmented packet network SPN, a metro transport network Either MTN or Optical Transport Network OTN.
  • a network synchronization device is provided, the device is applied to a first network device supporting flexible Ethernet FlexE, and the device includes:
  • an acquisition module configured to acquire a synchronization mode indication and synchronization information, and the synchronization mode indication is used to instruct the target network device to perform synchronization according to the synchronization information;
  • the sending module is used for sending the synchronization mode indication and synchronization information through the network supporting FlexE.
  • the sending module is configured to send a FlexE overhead frame through a network supporting FlexE, where the FlexE overhead frame includes a synchronization mode indication and synchronization information.
  • the synchronization mode indication includes a first mode indication, and the first mode indication is used to instruct the target network device to enter the FlexE synchronization mode.
  • the obtaining module is further configured to obtain target network device indication information, where the target network device indication information is used to indicate that the other end device of the FlexE segment or the other end device of the FlexE path is the target network device.
  • the synchronization mode indication includes target network device indication information.
  • the FlexE overhead frame includes at least one synchronization mode indication field, and the at least one synchronization mode indication field includes a synchronization mode indication;
  • the FlexE overhead frame includes a sixth FlexE overhead block, and the sixth FlexE overhead block includes synchronization information.
  • the first synchronization mode indication field in the at least one synchronization mode indication field includes one or more bits, and the one or more bits include a synchronization mode indication; or, the at least one synchronization mode indication
  • the field includes a second synchronization mode indication field, and the second synchronization mode indication field includes at least one bit that includes at least a portion of the synchronization mode indication.
  • the device further includes:
  • the encapsulation module is configured to encapsulate the synchronization information into an Ethernet frame, and the sixth FlexE overhead block includes the Ethernet frame.
  • the encapsulation module is further configured to divide the Ethernet frame into N code blocks 1, 2, .
  • Code blocks are continuously inserted into the bit field of the sixth FlexE overhead block of the first FlexE overhead frame, N is a positive integer greater than or equal to 2, i is a positive integer greater than or equal to 1 and i is less than N;
  • the i+1 to jth code blocks are continuously inserted into the bit field of the sixth FlexE overhead block of the second FlexE overhead frame, the second FlexE overhead frame is the next FlexE overhead frame adjacent to the first FlexE overhead frame, and j is a positive integer And i+1 ⁇ j ⁇ N.
  • the synchronization information includes one or more of precise time synchronization protocol PTP information and synchronization status information SSM, the PTP information is used to instruct the target network device to perform time synchronization, and the synchronization status information is used to indicate the target network device.
  • Network devices perform frequency synchronization.
  • the first network device supporting flexible Ethernet FlexE includes: a customer edge device supporting FlexE or a node device supporting a FlexE network, and the network supporting FlexE includes a fragmented packet network SPN, a metro transport network Either MTN or Optical Transport Network OTN.
  • a network synchronization device is provided, the device is applied to a second network device supporting flexible Ethernet FlexE, and the device includes:
  • a receiving module configured to receive a synchronization mode indication and synchronization information through a network supporting FlexE, and the synchronization mode indication is used to instruct the target network device to perform synchronization according to the synchronization information;
  • the synchronization module is configured to perform synchronization according to the synchronization information based on the synchronization mode indication.
  • the synchronization mode indication includes a first mode indication, and the first mode indication is used to instruct the target network device to enter the FlexE synchronization mode; the synchronization module is configured to enter the FlexE synchronization mode based on the first mode indication, In FlexE synchronization mode, synchronization is performed according to synchronization information.
  • the receiving module is further configured to receive target network device indication information, where the target network device indication information is used to indicate that the other end device of the FlexE segment or the other end device of the FlexE path is the target network device.
  • the synchronization mode indication includes target network device indication information.
  • a receiving module is configured to receive a FlexE overhead frame, where the FlexE overhead frame includes a synchronization mode indication and synchronization information; the apparatus further includes a parsing module, configured to parse the FlexE overhead frame to obtain the synchronization mode indication and Synchronization information.
  • the synchronization information includes one or more of precise time synchronization protocol PTP information and synchronization status information SSM; if the synchronization information includes PTP information, the synchronization module is configured to select time synchronization according to the PTP information source, and perform time synchronization according to the time synchronization source; if the synchronization information includes synchronization state information, the synchronization module is used to select a frequency synchronization source according to the synchronization state information, and perform frequency synchronization according to the frequency synchronization source.
  • the second network device supporting flexible Ethernet FlexE includes: a customer edge device supporting FlexE or a node device supporting a FlexE network, and the network supporting FlexE includes a fragmented packet network SPN, a metro transport network Either MTN or Optical Transport Network OTN.
  • a network synchronization device comprising: a processor, the processor is coupled to a memory, the memory stores at least one program instruction or code, and the at least one program instruction or code is loaded and executed by the processor, To enable a device to implement the method for network synchronization according to any one of the first aspect or the second aspect.
  • a system for network synchronization comprising: a first network device configured to execute the method described in the first aspect or the first aspect, and a second network device configured to execute the second aspect described above or the method of any one of the second aspect.
  • a computer-readable storage medium is provided, and at least one program instruction or code is stored in the computer-readable storage medium, and when the program instruction or code is loaded and executed by a processor, a computer can implement the first aspect or The method for network synchronization according to any one of the second aspect.
  • Another communication apparatus includes a transceiver, a memory, and a processor.
  • the transceiver, the memory and the processor communicate with each other through an internal connection path, the memory is used for storing instructions, and the processor is used for executing the instructions stored in the memory to control the transceiver to receive signals and control the transceiver to send signals , and when the processor executes the instructions stored in the memory, it causes the processor to execute the method in the first aspect or any possible implementation manner of the first aspect, or execute the second aspect or any one of the second aspect method in a possible implementation.
  • the processor is one or more
  • the memory is one or more.
  • the memory may be integrated with the processor, or the memory may be provided separately from the processor.
  • the memory can be a non-transitory memory, such as a read only memory (ROM), which can be integrated with the processor on the same chip, or can be separately set in different On the chip, the embodiment of the present application does not limit the type of the memory and the setting manner of the memory and the processor.
  • ROM read only memory
  • a computer program (product) comprising: computer program code which, when executed by a computer, causes the computer to perform the methods of the above aspects.
  • a chip including a processor for invoking and executing instructions stored in a memory, so that a communication device on which the chip is installed performs the methods in the above-mentioned aspects.
  • Another chip including: an input interface, an output interface, a processor, and a memory, the input interface, the output interface, the processor, and the memory are connected through an internal connection path, and the processor is used to execute all The code in the memory, when the code is executed, the processor is configured to perform the methods of the above aspects.
  • FIG. 1 is a schematic diagram of an application of the FlexE protocol provided by an embodiment of the present application.
  • FIG. 2 is a schematic diagram of arrangement positions of FlexE overhead blocks and data blocks on a PHY provided by an embodiment of the present application;
  • FIG. 3 is a schematic structural diagram of a FlexE overhead frame and a FlexE overhead multiframe provided by an embodiment of the present application;
  • FIG. 4 is a schematic diagram of an implementation scenario of a method for network synchronization provided by an embodiment of the present application
  • FIG. 5 is a flowchart of a method for network synchronization provided by an embodiment of the present application.
  • FIG. 6 is a schematic structural diagram of an apparatus for network synchronization provided by an embodiment of the present application.
  • FIG. 7 is a schematic structural diagram of another apparatus for network synchronization provided by an embodiment of the present application.
  • FIG. 8 is a schematic structural diagram of a network synchronization device provided by an embodiment of the present application.
  • FIG. 9 is a schematic structural diagram of another network synchronization device provided by an embodiment of the present application.
  • Ethernet interface is a fixed rate, and there is a gap with the transmission requirements. Therefore, the OIF organization has developed the FlexE protocol on the basis of the IEEE802.3 protocol to meet certain Ethernet requirements. Provide higher bandwidth requirements under the network interface speed level.
  • the FlexE protocol defines the FlexE shim, so that the Ethernet interface rate can flexibly match a variety of business scenarios, and when a higher bandwidth network processor (NP)/forwarding device appears, there is no need to wait for new When the fixed rate Ethernet standard is introduced, the maximum performance of the equipment can be exerted.
  • NP network processor
  • FlexE The basic function of FlexE is to map M FlexE customer services to a flexible Ethernet group (FlexE group) composed of N physical layer PHY links according to the time division multiplexing (TDM) mechanism of FlexE shim.
  • TDM time division multiplexing
  • M and N are positive integers.
  • M and N are positive integers.
  • the general architecture of FlexE can be shown in Figure 1, that is, the FlexE shown in Figure 1 maps six FlexE customer services to one by the TDM mechanism of the FlexE shim.
  • PHY physical layer
  • each 100G PHY corresponds to 20 time slots corresponding to 64B/66B code blocks, and each code block corresponds to 5G bits per second (bit/second). /s, bps) rate of payload rate (payload rate).
  • the current FlexE standard supports FlexE on 100G, 200G, 400G, and 50G PHY interfaces.
  • the time slot cycle format of data passing through a 100G PHY is shown in Figure 2.
  • each block is a 64b/66b block (block) encoded according to IEEE802.3 clause 82, and every 20 blocks constitutes a time slot table (calendar), each block is a time slot in the TDM mapping mechanism (time slot).
  • the sixth FlexE overhead block of the FlexE overhead frame can be used either as a management channel from the sill to the shim, or as a synchronization information channel.
  • the sixth FlexE overhead block is indicated as a management channel or a synchronization information channel through a synchronization control (synchronization control, SC) carried in the 11th bit field of the first FlexE overhead block.
  • SC synchronization control
  • the FlexE overhead frame also includes the following information:
  • the 8th bit field of the first FlexE overhead block, the 0th bit field of the second FlexE overhead block, and the 0th bit field of the third FlexE overhead block all carry C.
  • Overhead multiframe indicator called OMF in standards such as OIF-FlexE-01.0/01.1/02.2/02.1, where 01.0/01.1/02.2/02.1 are several versions of the OIF-FlexE standard , used to indicate the boundaries of the overhead multiframe.
  • the 9th bit field of the first FlexE overhead block as shown in Figure 3 carries the OMF.
  • the OMF value of the first 16 FlexE overhead frames is 0, and the OMF value of the last 16 FlexE overhead frames is 1, through the conversion between 0 and 1 , the boundaries of the FlexE overhead multiframe can be determined.
  • RPF Remote PHY fault
  • FlexE group number used to identify the FlexE group.
  • the 12th to 31st bit fields of the first FlexE overhead block as shown in FIG. 3 carry the FlexE group number.
  • FlexE map Used to control which FlexE instances are included in the FlexE group.
  • the 1st to 8th bit fields of the second FlexE overhead block as shown in FIG. 3 carry the FlexE map.
  • the FlexE map includes FlexE instance information in the FlexE group, each bit of the FlexE map corresponds to a FlexE instance, and the value of each bit of the FlexE map is used to indicate whether the FlexE instance corresponding to the bit is in the in the FlexE group.
  • the first value it is considered that the FlexE instance corresponding to the bit is in the FlexE group, and the first value may be 1; if the value of the bit is the second value, it is considered that the bit corresponds to The FlexE instance is not in this FlexE group, the second value can be 0.
  • FlexE instance number Indicates the identity of this FlexE instance within the group.
  • the 9th to 16th bit fields of the second FlexE overhead block as shown in FIG. 3 carry the FlexE instance number.
  • Time slot table A and time slot table B include the time slot table configuration information of all FlexE clients in the FlexE group, to avoid traffic loss when the FlexE client changes the time slot bandwidth configuration, and there is only one time slot table at any time In the working state, the 1st to 16th bit fields of the third FlexE overhead block as shown in FIG. 3 carry the time slot table A, and the 17th to 32nd bit fields carry the time slot table B.
  • Time slot table switch request (calendar switch request, CSR): called CR in OIF-FlexE-01.0/01.1/02.2/02.1 and other standards, it is used to switch the time slot table of the multiplexer and demultiplexer during data transmission. .
  • the CR is carried in the 33rd bit field of the third FlexE overhead block as shown in FIG. 3 .
  • Synchronization head (synchronization head, SH): is the frame header of the FlexE overhead frame, as shown in Figure 3, the first 2 bits of the FlexE overhead block.
  • Valid sync header bits (valid sync header bits, S): fields under SH in the fourth FlexE overhead block to the eighth FlexE overhead block as shown in FIG. 3 carry the S.
  • Segment management channel (management channel-section): used to carry segment management information.
  • the fourth FlexE overhead block and the fifth FlexE overhead block shown in FIG. 3 carry the management channel.
  • Cushion to cushion management channel (management channel-shim to shim): used to carry cushion to cushion management information, when SC is 0, the sixth FlexE overhead block to the eighth FlexE overhead block shown in Figure 3 Carry the management channel; when SC is 1, the seventh FlexE overhead block and the eighth FlexE overhead block as shown in FIG. 3 carry the management channel.
  • Cyclic redundancy check code (cyclic redundancy check, CRC): used to perform cyclic redundancy check protection on the content of the FlexE overhead frame.
  • CRC Cyclic redundancy check code
  • the FlexE overhead frame also includes reserved fields, as shown in FIG.
  • the 47th bit fields are reserved fields.
  • An embodiment of the present application provides a method for network synchronization.
  • the method is applied to a network device supporting FlexE.
  • the method can indicate that a network device supporting FlexE is in the network device.
  • the methods in the embodiments of the present application can be applied to the implementation scenario shown in FIG. 4 , where the implementation scenario includes customer edge devices and operator edge devices (a first node device and a second node device) supporting FlexE, and supporting FlexE synchronization,
  • the first node device and the second node device are both network node devices supporting FlexE.
  • Each operator edge device (the first node device, the second node device) and the customer edge device can exchange information through the FlexE group, while the operator edge device and the intermediate node device can exchange synchronous information.
  • the operator network supporting FlexE access includes any of a sliced packet network (SPN), a metro transport network (MTN) or an optical transport network (OTN). A sort of.
  • the network synchronization method provided by the embodiment of the present application is shown in FIG. 5 , including but not limited to steps 501 to 504 .
  • Step 501 The first network device acquires a synchronization mode indication and synchronization information.
  • the first network device includes a customer edge device supporting FlexE, or an operator edge device (eg, a first node device) supporting FlexE, or an intermediate node device of a network supporting FlexE, wherein the operator edge device supporting FlexE and The intermediate node devices of the network supporting FlexE all belong to the node devices of the network supporting FlexE; the first network device obtains the synchronization mode indication and synchronization information (for example, from the first customer edge device) through FlexE, and the synchronization mode indication is used to indicate the target network.
  • the device is synchronized according to the synchronization information, and the target network device is any network device.
  • the first network device obtains target network device indication information, where the target network device indication information is used to indicate that the device at the other end of the FlexE section or the device at the other end of the FlexE path (path) is the target Network equipment.
  • the synchronization mode indication includes the target network device indication information.
  • the target network device is further indicated by the target network device indication information, which can be realized without occupying additional resources. On the basis of indicating the target network device, resources are further saved.
  • the indication information of the target network device indicates that the device at the other end of the FlexE segment or the device at the other end of the FlexE path is the target network device through the indication bit.
  • the indication information of the target network device indicates the FlexE segment through the first indication bit combination.
  • the other end device of the FlexE segment is the target network device, for example, the first indication bit combination is (0, 1), and the other end device of the FlexE segment is the first node device; the indication information of the target network device indicates the FlexE through the second indication bit combination
  • the device at the other end of the path is the target network device, for example, the second indication bit combination is (1, 0), and the device at the other end of the FlexE path is the second node device; the indication information of the target network device is indicated by the third indication bit combination
  • Neither network device is the target network device, that is, neither network device enters the FlexE synchronization mode, for example, the third indication bit combination is (0, 0).
  • the indication information of the target network device indicates that the device corresponding to the specified FlexE segment or the device corresponding to the specified FlexE path is the target network device through the indication bit.
  • the indication information of the target network device includes a first indication bit, a second indication bit and a third indication bit. Any one of the indication bits, the target network device indication information uses the first indication bit to indicate that the network device specifying the FlexE segment is the target network device, and the second indication bit indicates that any node device in the specified FlexE path is a target network device.
  • the target network device indicates that the end node device specifying the FlexE path is the target network device through the third indication bit.
  • the synchronization mode indication includes a first mode indication, where the first mode indication is used to instruct the receiving target network device to enter the FlexE synchronization mode.
  • the target network device is synchronized according to the synchronization information.
  • the first mode indication may be independent of the existing mode, or may be superimposed on the existing mode as an additional attribute, and the processing method is relatively flexible.
  • the FlexE overhead frame includes a synchronization mode indication and synchronization information. Since the FlexE overhead frame includes the synchronization mode indication and synchronization information, the target network device can realize network synchronization based on the FlexE overhead frame without processing the service block.
  • the FlexE overhead frame includes at least one synchronization mode indication field, and the at least one synchronization mode indication field includes a synchronization mode indication.
  • At least one synchronization mode indication field of the FlexE overhead frame includes a synchronization mode indication, including but not limited to the following two ways.
  • the first synchronization mode indication field in the at least one synchronization mode indication field includes one or more bits, and the one or more bits include a synchronization mode indication.
  • the synchronization mode indications may all be included in the first synchronization mode indication field, and the first synchronization mode indication field may be any synchronization mode indication field in at least one synchronization mode indication field included in the FlexE overhead frame.
  • the FlexE overhead frame includes two synchronization mode indication fields, which are a synchronization mode indication field one and a synchronization mode indication field two, respectively.
  • the synchronization mode indication field 1 is the 17th to 63rd bit fields of the second FlexE overhead block of the FlexE overhead frame
  • the second synchronization mode indication field is the 35th to 47th bit fields of the third FlexE overhead block of the FlexE overhead frame.
  • the synchronization mode indication field one may be used as the first synchronization mode indication field, and the synchronization mode indication may be carried by one or more bits of the synchronization mode indication field one.
  • the second synchronization mode indication field may be used as the first synchronization mode indication field, and the synchronization mode indication may be carried by one or more bits of the second synchronization mode indication field.
  • At least one synchronization mode indication field includes a second synchronization mode indication field, the second synchronization mode indication field includes at least one bit, and the at least one bit includes at least a part of the synchronization mode indication.
  • the synchronization mode indication is included in multiple second synchronization mode indication fields, at least one bit of each second synchronization mode indication field includes at least a part of the synchronization mode indication, and at least one synchronization mode indication is included in the FlexE overhead frame. At least two synchronization mode indication fields in the mode indication fields are the second synchronization mode indication fields. Still, the FlexE overhead frame includes two synchronization mode indication fields, namely the synchronization mode indication field 1 and the synchronization mode indication field 2, and the synchronization mode indication field 1 is the 17th to 63rd bits of the second FlexE overhead block of the FlexE overhead frame.
  • the synchronization mode indication field 2 is the 35th to 47th bit fields of the third FlexE overhead block of the FlexE overhead frame.
  • the synchronization mode indication field 1 and the synchronization mode indication field 2 are both used as the second synchronization mode indication field.
  • the synchronization mode indication field one and the synchronization mode indication field two respectively include a part of the synchronization mode indication.
  • the synchronization mode indication is 0100
  • two bits in the synchronization mode indication field one include 01
  • two bits in the synchronization mode indication field two include 00.
  • the synchronization mode indication is carried by the synchronization mode indication field one and the synchronization mode indication field two.
  • the above example is only taken as an example where all the synchronization mode indication fields included in the FlexE overhead frame are used as the second synchronization mode indication field.
  • some synchronization mode indication fields included in the FlexE overhead frame may also be used The field is used as the second synchronization mode indication field.
  • several synchronization mode indication fields are selected as the second synchronization mode indication field, and which bits are used in each second synchronization mode indication field to carry the synchronization mode indication.
  • This application is not limited, and the above-mentioned mode 1 or the above-described mode 2 is adopted, and the embodiment of the present application is not limited, and can be flexibly set based on the bit length and application scenario indicated by the synchronization mode.
  • the above-mentioned synchronization mode indication field may be multiplexed on the reserved field of the existing FlexE overhead frame.
  • multiple reserved fields of the FlexE overhead frame shown in FIG. 3 are all used as synchronization mode indication fields.
  • the synchronization mode indication can be included in the synchronization mode indication field of the FlexE overhead frame in various manners, the manner of carrying the synchronization mode indication is more flexible.
  • the FlexE overhead frame includes a sixth FlexE overhead block
  • the manner in which the sixth FlexE overhead block includes the synchronization information includes: encapsulating the synchronization information into an Ethernet frame, and the sixth FlexE overhead block includes the Ethernet frame.
  • the synchronization information includes but is not limited to one or more of precision time synchronization protocol (precision time protocol, PTP) information and synchronization status information (synchronous status message, SSM), and the PTP information is used to instruct the target network device to perform time synchronization , the synchronization status information is used to instruct the target network device to perform frequency synchronization.
  • the sixth FlexE overhead block includes synchronization information, including but not limited to the following three situations.
  • the synchronization information includes PTP information, but does not include synchronization status information.
  • the first network device encapsulates the PTP information into an Ethernet frame according to the IEEE802.3 Ethernet encapsulation mechanism, and divides the Ethernet frame into blocks and inserts them into the sixth FlexE overhead block of the FlexE overhead frame, so that the FlexE overhead frame is Include this PTP information.
  • the first network device may also encapsulate the PTP information into a data packet according to the IP encapsulation mechanism, and then encapsulate the data packet into an Ethernet frame according to the IEEE802.3 Ethernet encapsulation mechanism, and insert the Ethernet frame into the first part of the FlexE overhead frame.
  • the FlexE overhead frame is made to include the PTP information.
  • the synchronization information includes synchronization status information, but does not include PTP information.
  • the first network device encapsulates the synchronization state information into an Ethernet frame according to the IEEE802.3 Ethernet encapsulation mechanism, and inserts the Ethernet frame into the sixth FlexE overhead block of the FlexE overhead frame, so that the FlexE overhead frame includes The synchronization status information.
  • the synchronization information includes PTP information and synchronization state information.
  • the first network device encapsulates the PTP information into a first Ethernet frame, encapsulates the synchronization state information into a second Ethernet frame, and further divides the first Ethernet frame and the second Ethernet frame into blocks and inserts the FlexE overhead
  • the FlexE overhead frame includes the PTP information and synchronization state information.
  • the manner in which the first network device encapsulates the PTP information and the synchronization state information is the same as the encapsulation manner in the first case and the second case, respectively, and details are not described herein again.
  • the manner of inserting the encapsulated Ethernet frame into the sixth FlexE overhead block of the FlexE overhead frame includes, but is not limited to: dividing the Ethernet frame into N code blocks 1, 2, ..., N-1, N, the code blocks 1 to i in the N code blocks are continuously inserted into the bit field of the sixth FlexE overhead block of the first FlexE overhead frame, N is a positive integer greater than or equal to 2, and i is a value greater than or equal to 1 A positive integer and i is less than N; the code blocks i+1 to j in the N code blocks are continuously inserted into the bit field of the sixth FlexE overhead block of the second FlexE overhead frame, and the second FlexE overhead frame is adjacent to the first FlexE overhead frame.
  • the next FlexE overhead frame of the FlexE overhead frame j is a positive integer and i+1 ⁇ j ⁇ N.
  • the N code blocks may also be inserted into the bit field of the sixth FlexE overhead block of one FlexE overhead frame.
  • N code blocks are inserted into the bit field of the sixth FlexE overhead block of one FlexE overhead frame, or inserted into the bit field of the sixth FlexE overhead block of multiple FlexE overhead frames, if If the N code blocks are not filled with the bit field of the sixth FlexE overhead block of the FlexE overhead frame, the remaining bit field of the sixth FlexE overhead block is set to the target reserved value, for example, the target reserved value is 0x00.
  • the first Ethernet frame encapsulating the PTP information is divided into multiple first code blocks
  • the second Ethernet frame encapsulating the synchronization state information is divided into multiple first code blocks.
  • Second code block; the sequence of inserting multiple first code blocks and multiple second code blocks into the bit field of the sixth FlexE overhead block of the FlexE overhead frame may be: inserting all the multiple first code blocks into the FlexE overhead frame After the bit field of the sixth FlexE overhead block, insert multiple second code blocks into the bit field of the sixth FlexE overhead block of the FlexE overhead frame, or insert all of the multiple second code blocks into the sixth After the bit field of the FlexE overhead block, insert multiple first code blocks into the bit field of the sixth FlexE overhead block of the FlexE overhead frame, or mix multiple first code blocks and multiple second code blocks into the FlexE overhead Bit field of the sixth FlexE overhead block of the frame.
  • Step 502 The first network device sends a synchronization mode indication and synchronization information through a network supporting FlexE.
  • the first network device sends a synchronization mode indication and synchronization information through a network supporting FlexE.
  • the synchronization mode indication and synchronization information are sent by the first network device through the FlexE group connected to the first network device.
  • the FlexE group connected to the first network device includes multiple PHYs, and the synchronization mode indication and synchronization information may be sent by the first network device through at least one PHY among the multiple PHYs.
  • the first network device is a customer edge device supporting FlexE. If the network supporting FlexE is any one of SPN, MTN or OTN, the first network device is connected to the first network device through a FlexE group sends synchronization mode indication and synchronization information.
  • the method can be applied to different networks supporting FlexE, and the application scenarios are relatively rich.
  • the first network device is a node device of a network supporting FlexE. If the network supporting FlexE is SPN or MTN, the first network device sends the synchronization mode through the FlexE group connected to the first network device. Indication and synchronization information; if the network supporting FlexE is OTN, the first network device sends a synchronization mode instruction through the FlexE group connected to the first network device, and the first network device converts the synchronization information into OTN synchronization information, and the synchronization through OTN The channel sends the OTN synchronization information.
  • the above steps 501 and 502 are both the process of performing the network synchronization on the first network device side.
  • the method for network synchronization is described by taking the second network device side as an example.
  • Step 503 The second network device receives the synchronization mode indication and synchronization information through the network supporting FlexE.
  • the second network device includes a customer edge device that supports FlexE, or an operator edge device that supports FlexE (for example, a second node device), or an intermediate node device of a network that supports FlexE, wherein the operator edge device that supports FlexE and The intermediate node devices of the network supporting FlexE all belong to the node devices of the network supporting FlexE.
  • the synchronization mode indication is used to instruct the target network device to synchronize according to the synchronization information, and the target network device is any network device.
  • the second network device receives the synchronization mode indication and synchronization information sent by the first network device through the FlexE group.
  • Step 504 Based on the synchronization mode indication, the second network device performs synchronization according to the synchronization information.
  • the synchronization mode indication includes a first indication, and the first mode indication is used to instruct the target network device to enter the FlexE synchronization mode; in this embodiment, the second network device is the target network device, based on the synchronization mode Instructing the second network device to perform synchronization according to the synchronization information includes: based on the first mode instruction, the second network device enters the FlexE synchronization mode, and in the FlexE synchronization mode, the second network device performs synchronization according to the synchronization information.
  • the second network device receives target network device indication information, and the target network device indication information is used to indicate that the device at the other end of the FlexE section or the device at the other end of the FlexE path (path) is the target network equipment.
  • the synchronization mode indication includes the target network device indication information.
  • the indication information of the target network device indicates that the device at the other end of the FlexE segment or the device at the other end of the FlexE path is the target network device through the indication bit.
  • the indication information of the target network device indicates the FlexE segment through the first indication bit combination.
  • the other end device of the FlexE path is the target network device, for example, the first indication bit combination is (0, 1); the target network device indication information indicates that the other end device of the FlexE path is the target network device through the second indication bit combination, for example, The second indication bit combination is (1, 0); the target network device indication information indicates through the third indication bit combination that any network device is not the target network device, that is, neither network device enters the FlexE synchronization mode, for example, The third indicator bit combination is (0, 0).
  • the device at the other end of the FlexE segment is clearly indicated as the target network device, that is, the device at the other end of the FlexE segment receives the synchronization mode indication and synchronization information before performing synchronization processing. , for a network device that is not the other end device of the FlexE segment, even if it receives the synchronization mode indication and synchronization information, it will not perform synchronization processing.
  • the indicated target network device and other network devices except the target network device respond to the received synchronization mode indication and synchronization information
  • the indication information of the target network device includes the first indication bit
  • the indicated target network device and other network devices except the target network device respond to the received synchronization mode indication and synchronization information in the same principle.
  • the indication information of the target network device indicates that the device in the FlexE segment or the device corresponding to the FlexE path is the target network device through an indication bit.
  • the indication information of the target network device includes a first indication bit, a second indication bit and the third indicator bit; if the target network device indication information includes the first indicator bit, then clearly indicate that the network device specifying the FlexE segment is the target network device, that is, the network device belonging to the specified FlexE segment receives the Synchronization processing is performed after synchronization mode indication and synchronization information.
  • target network device indication information includes the second indication bit, then clearly indicates that any node device in the specified FlexE path is the target network device; if the target network device indication information includes the third indicator bit, then clearly indicates that the end node device in the specified FlexE path is the target network device.
  • the indicated target network device and other network devices except the target network device will perform synchronization on the received synchronization
  • the response mode of the mode indication and synchronization information is combined with the indication information of the target network device including the first indication bit, the indicated target network device and other network devices other than the target network device will respond to the received synchronization mode indication and synchronization information.
  • the principle of the response method is the same, and will not be repeated here.
  • the second network device if the second network device is the device at the other end of the FlexE segment, based on the indication information of the target network device, the second network device enters the FlexE synchronization mode, and in the FlexE synchronization mode The second network device performs synchronization according to the synchronization information; if the second network device is not the device at the other end of the FlexE segment, based on the indication information of the target network device, the second network device does not enter the FlexE synchronization mode, and the second network device does not enter the FlexE synchronization mode according to the synchronization information. information is synchronized.
  • the process when the second network device performs synchronization according to the synchronization information, for several situations of the synchronization information, the process includes but is not limited to the following three situations.
  • the synchronization information includes PTP information, but does not include synchronization state information SSM.
  • the second network device selects a time synchronization source according to the PTP information, and performs time synchronization according to the selected time synchronization source.
  • the second network device decapsulates the PTP information included in the FlexE overhead frame according to the IEEE802.3 Ethernet decapsulation mechanism to obtain the PTP information, selects the time synchronization source according to the obtained PTP information, and synchronizes the time according to the selected time synchronization source for time synchronization.
  • the second network device decapsulates the PTP information included in the FlexE overhead frame according to the IEEE802.3 Ethernet decapsulation mechanism to obtain a data packet encapsulated according to the IP encapsulation mechanism
  • the second network device further decapsulates the data according to the IP decapsulation mechanism. Packet and decapsulate to obtain PTP information.
  • the synchronization information includes synchronization state information SSM, but does not include PTP information.
  • the second network device selects a frequency synchronization source according to the synchronization state information, and performs frequency synchronization according to the selected frequency synchronization source.
  • the second network device decapsulates the synchronization state information included in the FlexE overhead frame according to the IEEE802.3 Ethernet decapsulation mechanism to obtain the synchronization state information, selects the frequency synchronization source according to the obtained synchronization state information, and selects the frequency synchronization source according to the selected synchronization state information. frequency synchronization source for frequency synchronization.
  • the synchronization information includes PTP information and synchronization state information SSM.
  • the second network device selects a time synchronization source according to the PTP information, and performs time synchronization according to the selected time synchronization source; optionally, the second network device selects a frequency synchronization source according to the synchronization state information, and synchronizes according to the selected frequency source for frequency synchronization.
  • the process of obtaining the PTP information and the synchronization state information by the second network device is respectively the same as the process in the above-mentioned case 1 and case 2, and will not be repeated here.
  • the method provided by the embodiment of the present application can instruct the target network device to perform synchronization according to the synchronization information, that is, instruct which network devices in the network devices supporting FlexE process the synchronization information and the manner in which the network device processes the synchronization information, so as to realize the synchronization of the synchronization information.
  • the automatic configuration of network devices simplifies the operation process of configuring network devices when network synchronization is required, and improves the efficiency of network synchronization.
  • the synchronization mode indication included in the method provided in this embodiment can instruct each hop node device in the network device supporting FlexE to process synchronization information, which improves the synchronization accuracy of the network bearing data.
  • the FlexE synchronization mode in the above network synchronization method may be a newly defined mode, or function multiplexing may be performed on an existing mode.
  • FlexE defines three modes, which are FlexE aware mode, FlexE unaware mode and FlexE termination mode. Among them, the FlexE awareness mode is used to reduce the bandwidth occupation of FlexE service data transmission; the FlexE non-aware mode is used to realize the transmission of FlexE service data on existing Ethernet devices; the FlexE termination mode is used to realize the transmission of different FlexE service data. Diversion of business data.
  • the functions of the FlexE synchronization mode in this embodiment are superimposed on the FlexE sensing mode, and the FlexE sensing mode is used as the FlexE synchronization mode, so as to further superimpose and realize synchronization on the basis of realizing the original functions of the FlexE sensing mode.
  • FIG. 6 is a schematic structural diagram of an apparatus for network synchronization provided by an embodiment of the present application.
  • the apparatus is applied to a first network device supporting flexible Ethernet FlexE, where the first network device is the first network device shown in FIG. 5 .
  • the apparatus for network synchronization shown in FIG. 6 can perform all or part of the operations performed by the first network device. It should be understood that the apparatus may include more additional modules than the shown modules or omit a part of the modules shown therein, which is not limited in this embodiment of the present application.
  • the device includes:
  • an obtaining module 601 configured to obtain a synchronization mode indication and synchronization information, and the synchronization mode indication is used to instruct a target network device to perform synchronization according to the synchronization information;
  • the sending module 602 is configured to send a synchronization mode indication and synchronization information through a network supporting FlexE.
  • the sending module 602 is configured to send a FlexE overhead frame through a network supporting FlexE, where the FlexE overhead frame includes a synchronization mode indication and synchronization information.
  • the synchronization mode indication includes a first mode indication, and the first mode indication is used to instruct the target network device to enter the FlexE synchronization mode.
  • the obtaining module 601 is further configured to obtain target network device indication information, where the target network device indication information is used to indicate that the other end device of the FlexE segment or the other end device of the FlexE path is the target network device.
  • the synchronization mode indication includes target network device indication information.
  • the FlexE overhead frame includes at least one synchronization mode indication field, and the at least one synchronization mode indication field includes a synchronization mode indication;
  • the FlexE overhead frame includes a sixth FlexE overhead block, and the sixth FlexE overhead block includes synchronization information.
  • the first synchronization mode indication field in the at least one synchronization mode indication field includes one or more bits, and the one or more bits include a synchronization mode indication; or, the at least one synchronization mode indication
  • the field includes a second synchronization mode indication field, and the second synchronization mode indication field includes at least one bit that includes at least a portion of the synchronization mode indication.
  • the device further includes:
  • the encapsulation module is configured to encapsulate the synchronization information into an Ethernet frame, and the sixth FlexE overhead block includes the Ethernet frame.
  • the encapsulation module is further configured to divide the Ethernet frame into N code blocks 1, 2, .
  • Code blocks are continuously inserted into the bit field of the sixth FlexE overhead block of the first FlexE overhead frame, N is a positive integer greater than or equal to 2, i is a positive integer greater than or equal to 1 and i is less than N;
  • the i+1 to jth code blocks are continuously inserted into the bit field of the sixth FlexE overhead block of the second FlexE overhead frame, the second FlexE overhead frame is the next FlexE overhead frame adjacent to the first FlexE overhead frame, and j is a positive integer And i+1 ⁇ j ⁇ N.
  • the synchronization information includes one or more of precise time synchronization protocol PTP information and synchronization status information SSM, the PTP information is used to instruct the target network device to perform time synchronization, and the synchronization status information is used to indicate the target network device.
  • Network devices perform frequency synchronization.
  • the first network device supporting flexible Ethernet FlexE includes: a customer edge device supporting FlexE or a node device supporting a FlexE network, and the network supporting FlexE includes a fragmented packet network SPN, a metro transport network Either MTN or Optical Transport Network OTN.
  • FIG. 7 is a schematic structural diagram of an apparatus for network synchronization provided by an embodiment of the present application.
  • the apparatus is applied to a second network device supporting Flexible Ethernet FlexE, where the second network device is the second network device shown in FIG. 5 above.
  • the apparatus for network synchronization shown in FIG. 7 can perform all or part of the operations performed by the second network device. It should be understood that the apparatus may include more additional modules than the shown modules or omit a part of the modules shown therein, which is not limited in this embodiment of the present application.
  • the device includes:
  • a receiving module 701 configured to receive a synchronization mode indication and synchronization information through a network supporting FlexE, where the synchronization mode indication is used to instruct a target network device to perform synchronization according to the synchronization information;
  • the synchronization module 702 is configured to perform synchronization according to synchronization information based on the synchronization mode indication.
  • the synchronization mode indication includes a first mode indication, and the first mode indication is used to instruct the target network device to enter the FlexE synchronization mode; the synchronization module 702 is configured to enter the FlexE synchronization mode based on the first mode indication , in the FlexE synchronization mode, the synchronization is performed according to the synchronization information.
  • the receiving module 701 is further configured to receive target network device indication information, where the target network device indication information is used to indicate that the other end device of the FlexE segment or the other end device of the FlexE path is the target network device.
  • the synchronization mode indication includes target network device indication information.
  • the receiving module 701 is configured to receive a FlexE overhead frame, where the FlexE overhead frame includes a synchronization mode indication and synchronization information; the apparatus further includes a parsing module, configured to parse the FlexE overhead frame to obtain the FlexE overhead frame The carried synchronization mode indication and synchronization information.
  • the synchronization information includes one or more of precise time synchronization protocol PTP information and synchronization status information SSM; if the synchronization information includes PTP information, the synchronization module 702 is configured to select the time according to the PTP information.
  • the synchronization source performs time synchronization according to the time synchronization source; if the synchronization information includes synchronization state information, the synchronization module 702 is configured to select a frequency synchronization source according to the synchronization state information, and perform frequency synchronization according to the frequency synchronization source.
  • the second network device supporting flexible Ethernet FlexE includes: a customer edge device supporting FlexE or a node device supporting a FlexE network, and the network supporting FlexE includes a fragmented packet network SPN, a metro transport network Either MTN or Optical Transport Network OTN.
  • the hardware structure of the network device in the above-mentioned embodiment is as shown in FIG.
  • the transceiver 1501 , the processor 1502 and the memory 1503 are connected through a bus 1504 .
  • the transceiver 1501 is used to receive the synchronization mode indication and synchronization information and send the synchronization mode indication and synchronization information
  • the memory 1503 is used to store instructions or program codes
  • the processor 1502 is used to call the instructions or program codes in the memory 1503 to make the network device.
  • the network device 1500 in this embodiment of the present application may correspond to the first network device in each of the above method embodiments, and the processor 1502 in the network device 1500 reads the instructions or program codes in the memory 1503 to make the FIG.
  • the network device 1500 shown in 8 can perform all or part of the operations performed by the first network device.
  • the network device 1500 in this embodiment of the present application may correspond to the second network device in each of the above method embodiments, and the processor 1502 in the network device 1500 reads the instructions or program codes in the memory 1503 to make the The network device 1500 shown in 8 can perform all or part of the operations performed by the second network device.
  • FIG. 9 shows a schematic structural diagram of a network device 2000 provided by an exemplary embodiment of the present application.
  • the network device 2000 shown in FIG. 9 is configured to perform the operations involved in the network synchronization method shown in FIG. 5 above.
  • the network device 2000 is, for example, a switch, a router, and the like.
  • the network device 2000 includes at least one processor 2001 , memory 2003 and at least one communication interface 2004 .
  • the processor 2001 is, for example, a general-purpose central processing unit (central processing unit, CPU), a digital signal processor (digital signal processor, DSP), a network processor (network processor, NP), a graphics processing unit (graphics processing unit, GPU), A neural-network processing unit (NPU), a data processing unit (DPU), a microprocessor or one or more integrated circuits for implementing the solution of the present application.
  • the processor 2001 includes an application-specific integrated circuit (ASIC), a programmable logic device (PLD), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof.
  • ASIC application-specific integrated circuit
  • PLD programmable logic device
  • the PLD is, for example, a complex programmable logic device (CPLD), a field-programmable gate array (FPGA), a generic array logic (GAL), or any combination thereof. It may implement or execute the various logical blocks, modules and circuits described in connection with the disclosure of the embodiments of the present invention.
  • a processor may also be a combination that implements computing functions, such as a combination of one or more microprocessors, a combination of a DSP and a microprocessor, and the like.
  • the network device 2000 further includes a bus.
  • the bus is used to transfer information between the components of the network device 2000 .
  • the bus may be a peripheral component interconnect (PCI for short) bus or an extended industry standard architecture (EISA for short) bus or the like.
  • PCI peripheral component interconnect
  • EISA extended industry standard architecture
  • the bus can be divided into address bus, data bus, control bus and so on. For ease of presentation, only one thick line is used in FIG. 9, but it does not mean that there is only one bus or one type of bus.
  • the components of the network device 2000 in FIG. 9 may also be connected in other manners, and the embodiment of the present invention does not limit the connection manner of the components.
  • the memory 2003 is, for example, a read-only memory (read-only memory, ROM) or other types of static storage devices that can store static information and instructions, or a random access memory (random access memory, RAM) or a memory device that can store information and instructions.
  • Other types of dynamic storage devices such as electrically erasable programmable read-only memory (EEPROM), compact disc read-only memory (CD-ROM) or other optical disk storage, optical disks storage (including compact discs, laser discs, compact discs, digital versatile discs, Blu-ray discs, etc.), magnetic disk storage media, or other magnetic storage devices, or capable of carrying or storing desired program code in the form of instructions or data structures and capable of Any other medium accessed by a computer without limitation.
  • the memory 2003 exists independently, for example, and is connected to the processor 2001 through a bus.
  • the memory 2003 may also be integrated with the processor 2001 .
  • the communication interface 2004 uses any device such as a transceiver for communicating with other devices or a communication network, which may be Ethernet, a radio access network (RAN), or wireless local area networks (WLAN), or the like.
  • Communication interface 2004 may include a wired communication interface and may also include a wireless communication interface.
  • the communication interface 2004 may be an ethernet (ethernet) interface, a fast ethernet (FE) interface, a gigabit ethernet (GE) interface, an asynchronous transfer mode (ATM) interface, a wireless local area network ( wireless local area networks, WLAN) interfaces, cellular network communication interfaces, or a combination thereof.
  • the Ethernet interface can be an optical interface, an electrical interface or a combination thereof.
  • the communication interface 2004 may be used for the network device 2000 to communicate with other devices.
  • the processor 2001 may include one or more CPUs, such as CPU0 and CPU1 as shown in FIG. 9 .
  • Each of these processors can be a single-core (single-CPU) processor or a multi-core (multi-CPU) processor.
  • a processor herein may refer to one or more devices, circuits, and/or processing cores for processing data (eg, computer program instructions).
  • the network device 2000 may include multiple processors, such as the processor 2001 and the processor 2002 as shown in FIG. 9 .
  • processors can be a single-core processor (single-CPU) or a multi-core processor (multi-CPU).
  • a processor herein may refer to one or more devices, circuits, and/or processing cores for processing data (eg, computer program instructions).
  • the network device 2000 may further include an output device and an input device.
  • the output device communicates with the processor 2001 and can display information in a variety of ways.
  • the output device may be a liquid crystal display (LCD), a light emitting diode (LED) display device, a cathode ray tube (CRT) display device, a projector, or the like.
  • the input device communicates with the processor 2001 and can receive user input in various ways.
  • the input device may be a mouse, a keyboard, a touch screen device, or a sensor device, or the like.
  • the memory 2003 is used to store the program code 2005 for executing the solutions of the present application
  • the processor 2001 can execute the program code 2005 stored in the memory 2003 . That is, the network device 2000 can implement the network synchronization method provided by the method embodiment through the processor 2001 and the program code 2005 in the memory 2003 .
  • One or more software modules may be included in the program code 2005 .
  • the processor 2001 itself may also store program codes or instructions for executing the solutions of the present application.
  • the network device 2000 in this embodiment of the present application may correspond to the first network device in the above method embodiments, and the processor 2001 in the network device 2000 reads the program code 2005 in the memory 2003 or the processor 2001
  • the program codes or instructions stored by itself enable the network device 2000 shown in FIG. 9 to perform all or part of the operations performed by the first network device.
  • the network device 2000 in this embodiment of the present application may correspond to the second network device in each of the above method embodiments, and the processor 2001 in the network device 2000 reads the program code 2005 in the memory 2003 or the processor 2001
  • the program codes or instructions stored by itself enable the network device 2000 shown in FIG. 9 to perform all or part of the operations performed by the second network device.
  • the network device 2000 may also correspond to the apparatuses shown in FIGS. 6 and 7 above, and each functional module in the apparatuses shown in FIGS. 6 and 7 is implemented by software of the network device 2000 .
  • the functional modules included in the apparatuses shown in FIGS. 6 and 7 are generated after the processor 2001 of the network device 2000 reads the program code 2005 stored in the memory 2003 .
  • each step of the method for network synchronization shown in FIG. 5 is completed by an integrated logic circuit of hardware in the processor of the network device 2000 or an instruction in the form of software.
  • the steps of the methods disclosed in conjunction with the embodiments of the present application may be directly embodied as executed by a hardware processor, or executed by a combination of hardware and software modules in the processor.
  • the software modules may be located in random access memory, flash memory, read-only memory, programmable read-only memory or electrically erasable programmable memory, registers and other storage media mature in the art.
  • the storage medium is located in the memory, and the processor reads the information in the memory, and completes the steps of the above method in combination with its hardware, which will not be described in detail here to avoid repetition.
  • An embodiment of the present application further provides a system for network synchronization, the system includes: a first network device and a second network device; the first network device is configured to execute the method performed by the first network device described in FIG. The second network device is configured to execute the method performed by the second network device described in FIG. 5 .
  • processor may be a central processing unit (CPU), or other general-purpose processors, digital signal processors (digital signal processing, DSP), application specific integrated circuits (application specific integrated circuits, ASIC), field programmable gate array (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc.
  • a general purpose processor may be a microprocessor or any conventional processor or the like. It should be noted that the processor may be a processor supporting an advanced RISC machine (ARM) architecture.
  • ARM advanced RISC machine
  • the above-mentioned memory may include read-only memory and random access memory, and provide instructions and data to the processor.
  • the memory may also include non-volatile random access memory.
  • the memory may also store device type information.
  • the memory may be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory.
  • the non-volatile memory may be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically programmable Erase programmable read-only memory (electrically EPROM, EEPROM) or flash memory.
  • Volatile memory may be random access memory (RAM), which acts as an external cache. By way of example and not limitation, many forms of RAM are available.
  • SRAM static RAM
  • DRAM dynamic random access memory
  • SDRAM synchronous dynamic random access memory
  • double data rate synchronous dynamic random access Memory double data date SDRAM, DDR SDRAM
  • enhanced synchronous dynamic random access memory enhanced SDRAM, ESDRAM
  • synchronous link dynamic random access memory direct memory bus random access memory
  • direct rambus RAM direct rambus RAM
  • a computer-readable storage medium is also provided, and at least one program instruction or code is stored in the storage medium.
  • the program instruction or code is loaded and executed by the processor, the computer realizes the method for network synchronization as shown in FIG. 5 above. .
  • the present application provides a computer program.
  • the processor or the computer can execute the corresponding steps and/or processes in the foregoing method embodiments.
  • a chip including a processor for invoking and executing instructions stored in a memory, so that a communication device on which the chip is installed performs the methods in the above-mentioned aspects.
  • Another chip including: an input interface, an output interface, a processor, and a memory, the input interface, the output interface, the processor, and the memory are connected through an internal connection path, and the processor is used to execute all The code in the memory, when the code is executed, the processor is configured to perform the methods of the above aspects.
  • the above-mentioned embodiments it may be implemented in whole or in part by software, hardware, firmware or any combination thereof.
  • software it can be implemented in whole or in part in the form of a computer program product.
  • the computer program product includes one or more computer instructions.
  • the computer program instructions when loaded and executed on a computer, result in whole or in part of the processes or functions described herein.
  • the computer may be a general purpose computer, special purpose computer, computer network, or other programmable device.
  • the computer instructions may be stored in or transmitted from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions may be downloaded from a website site, computer, server or data center Transmission to another website site, computer, server, or data center by wire (eg, coaxial cable, optical fiber, digital subscriber line) or wireless (eg, infrared, wireless, microwave, etc.).
  • the computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. that includes an integration of one or more available media.
  • the usable media may be magnetic media (eg, floppy disks, hard disks, magnetic tapes), optical media (eg, DVDs), or semiconductor media (eg, solid state disks), and the like.
  • the computer program product includes one or more computer program instructions.
  • the methods of the embodiments of the present application may be described in the context of machine-executable instructions, such as included in program modules executed in a device on a target's real or virtual processor.
  • program modules include routines, programs, libraries, objects, classes, components, data structures, etc. that perform particular tasks or implement particular abstract data structures.
  • the functionality of the program modules may be combined or divided among the described program modules.
  • Machine-executable instructions for program modules may be executed within local or distributed devices. In a distributed facility, program modules may be located in both local and remote storage media.
  • Computer program code for implementing the methods of the embodiments of the present application may be written in one or more programming languages. Such computer program code may be provided to a processor of a general purpose computer, special purpose computer or other programmable data processing apparatus such that the program code, when executed by the computer or other programmable data processing apparatus, causes the flowchart and/or block diagrams The functions/operations specified in are implemented.
  • the program code may execute entirely on the computer, partly on the computer, as a stand-alone software package, partly on the computer and partly on a remote computer or entirely on the remote computer or server.
  • computer program code or related data may be carried by any suitable carrier to enable a device, apparatus or processor to perform the various processes and operations described above.
  • suitable carriers include signals, computer-readable media, and the like.
  • Examples of signals may include electrical, optical, radio, acoustic, or other forms of propagated signals, such as carrier waves, infrared signals, and the like.
  • a machine-readable medium may be any tangible medium that contains or stores a program for or in connection with an instruction execution system, apparatus, or device.
  • the machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium.
  • Machine-readable media may include, but are not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices, or devices, or any suitable combination thereof. More detailed examples of machine-readable storage media include electrical connections with one or more wires, portable computer disks, hard disks, random access memory (RAM), read only memory (ROM), erasable programmable read only Memory (EPROM or flash memory), optical storage devices, magnetic storage devices, or any suitable combination thereof.
  • the disclosed systems, devices and methods may be implemented in other manners.
  • the device embodiments described above are only illustrative.
  • the division of the modules is only a logical function division. In actual implementation, there may be other division methods.
  • multiple modules or components may be combined or Integration into another system, or some features can be ignored, or not implemented.
  • the shown or discussed mutual coupling or direct coupling or communication connection may be indirect coupling or communication connection through some interfaces, devices or modules, and may also be electrical, mechanical or other forms of connection.
  • modules described as separate components may or may not be physically separated, and the components shown as modules may or may not be physical modules, that is, may be located in one place, or may be distributed to multiple network modules. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solutions of the embodiments of the present application.
  • each functional module in each embodiment of the present application may be integrated into one processing module, or each module may exist physically alone, or two or more modules may be integrated into one module.
  • the above-mentioned integrated modules can be implemented in the form of hardware, and can also be implemented in the form of software function modules.
  • the integrated modules are implemented in the form of software functional modules and sold or used as independent products, they may be stored in a computer-readable storage medium.
  • the technical solutions of the present application are essentially or part of contributions to the prior art, or all or part of the technical solutions can be embodied in the form of software products, and the computer software products are stored in a storage medium , including several instructions to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods in the various embodiments of the present application.
  • the aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM), random access memory (RAM), magnetic disk or optical disk and other media that can store program codes .
  • first, second and other words are used to distinguish the same or similar items with basically the same function and function, and it should be understood that between “first”, “second” and “nth” There are no logical or timing dependencies, and no restrictions on the number and execution order. It will also be understood that, although the following description uses the terms first, second, etc. to describe various elements, these elements should not be limited by the terms. These terms are only used to distinguish one element from another.
  • a first network device may be referred to as a second network device, and similarly, a second network device may be referred to as a first network device, without departing from the scope of various described examples.
  • Both the first network and device and the second network device may be network devices, and in some cases may be separate and distinct network devices.
  • the size of the sequence number of each process does not mean the sequence of execution, and the execution sequence of each process should be determined by its function and internal logic, and should not be used in the embodiment of the present application. Implementation constitutes any limitation.
  • the meaning of the term “at least one” refers to one or more, and the meaning of the term “plurality” in this application refers to two or more.
  • a plurality of second messages refers to two or more more than one second message.
  • system and “network” are often used interchangeably herein.
  • determining B according to A does not mean that B is only determined according to A, and B may also be determined according to A and/or other information.
  • references throughout the specification to "one embodiment,” “an embodiment,” and “one possible implementation” mean that a particular feature, structure, or characteristic associated with the embodiment or implementation is included herein. in at least one embodiment of the application. Thus, appearances of "in one embodiment” or “in an embodiment” or “one possible implementation” in various places throughout this specification are not necessarily necessarily referring to the same embodiment. Furthermore, the particular features, structures or characteristics may be combined in any suitable manner in one or more embodiments.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Synchronisation In Digital Transmission Systems (AREA)

Abstract

本申请实施例公开了一种网络同步的方法、装置、设备、系统及可读存储介质。该网络同步的方法包括:第一网络设备获取同步模式指示以及同步信息,同步模式指示用于指示目标网络设备根据同步信息进行同步,第一网络设备通过支持FlexE的网络发送该同步模式指示以及同步信息;第二网络设备通过支持FlexE的网络接收同步模式指示以及同步信息,基于该同步模式指示,第二网络设备根据同步信息进行同步。该方法能够指示支持FlexE的网络设备中哪些网络设备为目标网络设备来处理同步信息和该网络设备处理同步信息的方式,简化了网络同步时对网络设备进行配置的操作流程,提高了网络同步的效率。

Description

网络同步的方法、装置、设备、系统及可读存储介质
本申请要求于2020年11月16日提交的申请号为202011275848.7、发明名称为“网络同步方法及设备”的中国专利申请的优先权,其全部内容通过引用结合在本申请中;本申请还要求于2021年2月4日提交的申请号为202110158060.6、发明名称为“网络同步的方法、装置、设备、系统及可读存储介质”的中国专利申请的优先权,其全部内容通过引用结合在本申请中。
技术领域
本申请实施例涉及通信技术领域,尤其涉及一种网络同步的方法、装置、设备、系统及可读存储介质。
背景技术
光互联网论坛(optical internetworking forum,OIF)组织在电气与电子工程师协会(institute of electrical and electronics engineers,IEEE)802.3协议的基础上发起了灵活以太(flexible ethernet,FlexE)协议。基于FlexE协议,以太网接口速率可以灵活匹配多种业务场景。
发明内容
本申请提出一种网络同步的方法、装置、设备、系统及可读存储介质,以简化网络同步的操作流程,提高网络同步的效率。
第一方面,提供了一种网络同步的方法,该方法应用于支持FlexE的第一网络设备,该方法包括:第一网络设备获取同步模式指示以及同步信息,同步模式指示用于指示目标网络设备根据同步信息进行同步;第一网络设备通过支持FlexE的网络发送同步模式指示以及同步信息。
本申请实施例提供的方法,通过包括能够指示目标网络设备根据同步信息进行同步的同步模式指示,能够指示支持FlexE的网络设备中哪些网络设备作为目标网络设备来处理同步信息以及该网络设备处理同步信息的方式,从而实现对网络设备的自动配置,简化了需要网络同步时对网络设备进行配置的操作流程,提高了网络同步的效率。
在一种可能的实现方式中,发送同步模式指示以及同步信息,包括:发送FlexE开销帧,该FlexE开销帧包括同步模式指示以及同步信息。由于FlexE开销帧包括同步模式指示及同步信息,可以使得目标网络设备在不处理业务块的情况下,基于该FlexE开销帧即可实现网络同步。
在一种可能的实现方式中,同步模式指示包括第一模式指示,第一模式指示用于指示目标网络设备进入FlexE同步模式。该第一模式指示可独立于已有的模式,也可作为附加属性叠加到已有模式上,处理方式较为灵活。
在一种可能的实现方式中,该方法还包括:第一网络设备获取目标网络设备指示信息,该目标网络设备指示信息用于指示FlexE段的另一端设备或FlexE路径的另一端设备为目标 网络设备。通过该目标网络设备指示信息进一步指示目标网络设备,无需占用额外的资源即可实现,在达到指示目标网络设备的基础上,进一步节省了资源。
在一种可能的实现方式中,同步模式指示包括目标网络设备指示信息。
在一种可能的实现方式中,FlexE开销帧包括至少一个同步模式指示字段,至少一个同步模式指示字段包括同步模式指示;FlexE开销帧包括第六FlexE开销块,第六FlexE开销块包括同步信息。
在一种可能的实现方式中,至少一个同步模式指示字段中的第一同步模式指示字段包括一个或多个比特位,该一个或多个比特位包括同步模式指示;或者,该至少一个同步模式指示字段包括第二同步模式指示字段,该第二同步模式指示字段包括至少一个比特位,该至少一个比特位包括同步模式指示的至少一部分。由于同步模式指示能够包括在FlexE开销帧的同步模式指示字段的不同情况中,同步模式指示的携带方式更为灵活。
在一种可能的实现方式中,第六FlexE开销块包括同步信息,包括:将同步信息封装为以太帧,第六FlexE开销块包括该以太帧。
在一种可能的实现方式中,第六FlexE开销块包括该以太帧,包括:将以太帧切分为N个码块1,2,…,N-1,N,将N个码块中的第1至i个码块连续插入到第一FlexE开销帧的第六FlexE开销块的比特位字段,N为大于等于2的正整数,i为大于等于1的正整数且i小于N;将N个码块中的第i+1至j个码块连续插入第二FlexE开销帧的第六FlexE开销块的比特位字段,第二FlexE开销帧为邻接第一FlexE开销帧的下一个FlexE开销帧,j为正整数且i+1≤j≤N。
在一种可能的实现方式中,同步信息包括精确时间同步协议PTP信息和同步状态信息SSM中的一种或多种,PTP信息用于指示目标网络设备进行时间同步,同步状态信息用于指示目标网络设备进行频率同步。
在一种可能的实现方式中,支持灵活以太FlexE的第一网络设备包括:支持FlexE的客户边缘设备或支持FlexE的网络的节点设备,支持FlexE的网络包括分片分组网络SPN、城域传送网络MTN或光传送网络OTN中的任一种。该方法能够应用于支持FlexE的不同网络中,应用的场景较为丰富。
第二方面,提供了一种网络同步的方法,该方法应用于支持灵活以太FlexE的第二网络设备,该方法包括:第二网络设备通过支持FlexE的网络接收同步模式指示以及同步信息,同步模式指示用于指示目标网络设备根据同步信息进行同步;基于同步模式指示,第二网络设备根据同步信息进行同步。
在一种可能的实现方式中,同步模式指示包括第一模式指示,第一模式指示用于指示目标网络设备进入FlexE同步模式;基于同步模式指示,第二网络设备根据同步信息进行同步,包括:基于第一模式指示,第二网络设备进入FlexE同步模式,在FlexE同步模式下,第二网络设备根据同步信息进行同步。
在一种可能的实现方式中,该方法还包括:第二网络设备接收目标网络设备指示信息,该目标网络设备指示信息用于指示FlexE段的另一端设备或FlexE路径的另一端设备为目标网络设备。
在一种可能的实现方式中,同步模式指示包括目标网络设备指示信息。
在一种可能的实现方式中,接收同步模式指示以及同步信息,包括:接收FlexE开销帧,FlexE开销帧包括同步模式指示以及同步信息;基于同步模式指示,第二网络设备根据同步信息进行同步之前,该方法还包括:第二网络设备解析FlexE开销帧,得到同步模式指示以及同步信息。
在一种可能的实现方式中,同步信息包括精确时间同步协议PTP信息和同步状态信息SSM中的一种或多种;第二网络设备根据同步信息进行同步,包括:若同步信息包括PTP信息,第二网络设备根据PTP信息选择时间同步源,第二网络设备根据时间同步源进行时间同步;若同步信息包括同步状态信息,第二网络设备根据同步状态信息选择频率同步源,第二网络设备根据频率同步源进行频率同步。
在一种可能的实现方式中,支持灵活以太FlexE的第二网络设备包括:支持FlexE的客户边缘设备或支持FlexE的网络的节点设备,支持FlexE的网络包括分片分组网络SPN、城域传送网络MTN或光传送网络OTN中的任一种。
第三方面,提供了一种网络同步的装置,该装置应用于支持灵活以太FlexE的第一网络设备,该装置包括:
获取模块,用于获取同步模式指示以及同步信息,同步模式指示用于指示目标网络设备根据同步信息进行同步;
发送模块,用于通过支持FlexE的网络发送同步模式指示以及同步信息。
在一种可能的实现方式中,该发送模块,用于通过支持FlexE的网络发送FlexE开销帧,FlexE开销帧包括同步模式指示以及同步信息。
在一种可能的实现方式中,同步模式指示包括第一模式指示,第一模式指示用于指示目标网络设备进入FlexE同步模式。
在一种可能的实现方式中,获取模块,还用于获取目标网络设备指示信息,该目标网络设备指示信息用于指示FlexE段的另一端设备或FlexE路径的另一端设备为目标网络设备。
在一种可能的实现方式中,同步模式指示包括目标网络设备指示信息。
在一种可能的实现方式中,FlexE开销帧包括至少一个同步模式指示字段,该至少一个同步模式指示字段包括同步模式指示;FlexE开销帧包括第六FlexE开销块,该第六FlexE开销块包括同步信息。
在一种可能的实现方式中,至少一个同步模式指示字段中的第一同步模式指示字段包括一个或多个比特位,该一个或多个比特位包括同步模式指示;或者,至少一个同步模式指示字段包括第二同步模式指示字段,第二同步模式指示字段包括至少一个比特位,该至少一个比特位包括同步模式指示的至少一部分。
在一种可能的实现方式中,该装置还包括:
封装模块,用于将同步信息封装为以太帧,第六FlexE开销块包括该以太帧。
在一种可能的实现方式中,该封装模块,还用于将以太帧切分为N个码块1,2,…,N-1,N,将N个码块中的第1至i个码块连续插入到第一FlexE开销帧的第六FlexE开销块的比特位字段,N为大于等于2的正整数,i为大于等于1的正整数且i小于N;将N个码块中的第i+1至j个码块连续插入第二FlexE开销帧的第六FlexE开销块的比特位字段,第二FlexE开销帧为邻接第一FlexE开销帧的下一个FlexE开销帧,j为正整数且i+1≤j≤N。
在一种可能的实现方式中,同步信息包括精确时间同步协议PTP信息和同步状态信息SSM中的一种或多种,PTP信息用于指示目标网络设备进行时间同步,同步状态信息用于指示目标网络设备进行频率同步。
在一种可能的实现方式中,支持灵活以太FlexE的第一网络设备包括:支持FlexE的客户边缘设备或支持FlexE的网络的节点设备,支持FlexE的网络包括分片分组网络SPN、城域传送网络MTN或光传送网络OTN中的任一种。
第四方面,提供了一种网络同步的装置,该装置应用于支持灵活以太FlexE的第二网络设备,该装置包括:
接收模块,用于通过支持FlexE的网络接收同步模式指示以及同步信息,同步模式指示用于指示目标网络设备根据同步信息进行同步;
同步模块,用于基于同步模式指示,根据同步信息进行同步。
在一种可能的实现方式中,同步模式指示包括第一模式指示,第一模式指示用于指示目标网络设备进入FlexE同步模式;该同步模块,用于基于第一模式指示,进入FlexE同步模式,在FlexE同步模式下,根据同步信息进行同步。
在一种可能的实现方式中,接收模块,还用于接收目标网络设备指示信息,该目标网络设备指示信息用于指示FlexE段的另一端设备或FlexE路径的另一端设备为目标网络设备。
在一种可能的实现方式中,同步模式指示包括目标网络设备指示信息。
在一种可能的实现方式中,接收模块,用于接收FlexE开销帧,该FlexE开销帧包括同步模式指示以及同步信息;该装置还包括解析模块,用于解析FlexE开销帧,得到同步模式指示以及同步信息。
在一种可能的实现方式中,同步信息包括精确时间同步协议PTP信息和同步状态信息SSM中的一种或多种;若同步信息包括PTP信息,该同步模块,用于根据PTP信息选择时间同步源,根据时间同步源进行时间同步;若同步信息包括同步状态信息,该同步模块,用于根据同步状态信息选择频率同步源,根据频率同步源进行频率同步。
在一种可能的实现方式中,支持灵活以太FlexE的第二网络设备包括:支持FlexE的客户边缘设备或支持FlexE的网络的节点设备,支持FlexE的网络包括分片分组网络SPN、城域传送网络MTN或光传送网络OTN中的任一种。
第五方面,提供了一种网络同步的设备,该设备包括:处理器,处理器与存储器耦合,存储器中存储有至少一条程序指令或代码,至少一条程序指令或代码由处理器加载并执行,以使设备实现如第一方面或第二方面中任一的网络同步的方法。
第六方面,提供了一种网络同步的系统,该系统包括:第一网络设备用于执行上述第一方面或第一方面任一所述的方法,第二网络设备用于执行上述第二方面或第二方面任一所述的方法。
第七方面,提供了一种计算机可读存储介质,该计算机可读存储介质中存储有至少一条程序指令或代码,程序指令或代码由处理器加载并执行时以使计算机实现如第一方面或第二方面中任一的网络同步的方法。
提供了另一种通信装置,该装置包括:收发器、存储器和处理器。其中,该收发器、该 存储器和该处理器通过内部连接通路互相通信,该存储器用于存储指令,该处理器用于执行该存储器存储的指令,以控制收发器接收信号,并控制收发器发送信号,并且当该处理器执行该存储器存储的指令时,使得该处理器执行第一方面或第一方面的任一种可能的实施方式中的方法,或者执行第二方面或第二方面的任一种可能的实施方式中的方法。
作为一种示例性实施例,所述处理器为一个或多个,所述存储器为一个或多个。
作为一种示例性实施例,所述存储器可以与所述处理器集成在一起,或者所述存储器与处理器分离设置。
在具体实现过程中,存储器可以为非瞬时性(non-transitory)存储器,例如只读存储器(read only memory,ROM),其可以与处理器集成在同一块芯片上,也可以分别设置在不同的芯片上,本申请实施例对存储器的类型以及存储器与处理器的设置方式不做限定。
提供了一种计算机程序(产品),所述计算机程序(产品)包括:计算机程序代码,当所述计算机程序代码被计算机运行时,使得所述计算机执行上述各方面中的方法。
提供了一种芯片,包括处理器,用于从存储器中调用并运行所述存储器中存储的指令,使得安装有所述芯片的通信设备执行上述各方面中的方法。
提供另一种芯片,包括:输入接口、输出接口、处理器和存储器,所述输入接口、输出接口、所述处理器以及所述存储器之间通过内部连接通路相连,所述处理器用于执行所述存储器中的代码,当所述代码被执行时,所述处理器用于执行上述各方面中的方法。
附图说明
图1是本申请实施例提供的FlexE协议应用示意图;
图2是本申请实施例提供的FlexE开销块和数据块在PHY上的排列位置示意图;
图3是本申请实施例提供的FlexE开销帧和FlexE开销复帧的结构示意图;
图4是本申请实施例提供的一种网络同步的方法的实施场景示意图;
图5是本申请实施例提供的一种网络同步的方法流程图;
图6是本申请实施例提供的一种网络同步的装置的结构示意图;
图7是本申请实施例提供的另一种网络同步的装置的结构示意图;
图8是本申请实施例提供的一种网络同步的设备的结构示意图;
图9是本申请实施例提供的另一种网络同步的设备的结构示意图。
具体实施方式
本申请的实施方式部分使用的术语仅用于对本申请的实施例进行解释,而非旨在限定本申请。下面结合附图,对本发明的实施例进行描述。
随着互连网协议(internet protocol,IP)网络应用和业务的多样化,网络流量增加的趋势越来越明显。由于以太网接口的标准制定以及产品开发呈现阶梯型,以太网接口是固定速率,与传送需求存在差距,因此,OIF组织在IEEE802.3协议的基础上发展了FlexE协议,以便满足在一定的以太网接口速率等级下提供更高带宽的需求。该FlexE协议定义了FlexE垫层(shim),使得以太网接口速率可以灵活匹配多种业务场景,并且在更高带宽的网络处理器(network processor,NP)/转发设备出现时,不必等待新的固定速率以太网标准出台,即可发挥设备的最大性能。
FlexE的基本功能是将M个FlexE客户业务按照FlexE shim的时分复用(time division multiplexing,TDM)机制映射到一个由N条物理层PHY链路组成的灵活以太网组(FlexE group)上,其中,M和N均为正整数。示例性地,以M为6,N为4为例,FlexE的通用架构可如图1所示,即图1所示的FlexE是将6个FlexE客户业务按照FlexE shim的TDM机制映射到一个由4条物理层(physical layer,PHY)链路组成的FlexE group上。
以100吉比特(G)PHY为例,FlexE的映射机制中,每条100G PHY对应着20个64B/66B码块对应的时隙(time slot),每个码块对应5G比特/秒(bit/s,bps)速率的净荷速率(payload rate)。当前FlexE标准支持100G,200G,400G,和50G PHY接口上的FlexE。经过一条100G PHY的数据的时隙周期格式如图2所示。图2中,每个块为一个根据IEEE802.3条款82编码的64b/66b块(block),每20个blocks组成一个时隙表(calendar),每个块即TDM映射机制中的一个时隙(time slot)。每个calendar重复1023次之后,插入1个64b/66b编码的FlexE开销块(overhead block)。然后,每8个FlexE开销块组成一个FlexE开销帧,每32个FlexE开销帧组成一个FlexE开销复帧。整个FlexE的流量时隙映射(client-slot mapping)和各种管理,都在FlexE开销复帧内完成。FlexE开销帧和FlexE开销复帧的格式如图3所示。
如图3所示,FlexE开销帧的第六FlexE开销块既可以作为垫层至垫层的管理通道,也可以作为同步信息通道。通过第一FlexE开销块的第11比特位字段携带的同步控制(synchronization control,SC)指示第六FlexE开销块作为管理通道或同步信息通道。示例性地,当SC为0时,第六FlexE开销块作为管理通道,当SC为1时,第六FlexE开销块作为同步信息通道。
如图3所示,FlexE开销帧中除上述第六FlexE开销块的信息以及SC以外,还包括如下信息:
C:用于指示正在使用的时隙配置(calendar configuration in use)。如图3所示的第一FlexE开销块的第8比特位字段、第二FlexE开销块的第0比特位字段和第三FlexE开销块的第0比特位字段均携带C。
开销复帧指示器(overhead multiframe indicator,OMFI):在OIF-FlexE-01.0/01.1/02.2/02.1等标准中称为OMF,其中,01.0/01.1/02.2/02.1是OIF-FlexE标准的几个版本,用于指示开销复帧的边界。如图3所示的第一FlexE开销块的第9比特位字段携带该OMF。其中,如图3所示,在一个FlexE开销复帧中,前16个FlexE开销帧的OMF的值为0,后16个FlexE开销帧的OMF的值为1,通过0和1之间的转换,能够确定FlexE开销复帧的边界。
远程物理故障(remote PHY fault,RPF):用于指示远程物理故障。如图3所示的第一FlexE开销块的第10比特位字段携带该RPF。
灵活以太网组号(FlexE group number):用于标识灵活以太网组。如图3所示的第一FlexE开销块的第12至第31比特位字段携带该FlexE group number。
灵活以太图(FlexE map):用于控制FlexE group中包括哪些FlexE实例(FlexE instance)。如图3所示的第二FlexE开销块的第1至第8比特位字段携带该FlexE map。示例性地,该FlexE map包括FlexE group内的FlexE实例信息,FlexE map的每个比特位对应一个FlexE实例,FlexE map的每个比特位的值用于表示该比特位对应的FlexE实例是否在该FlexE group中。例如,如果比特位的值为第一值,则认为该比特位对应的FlexE实例在该FlexE group中, 第一值可以为1;如果比特位的值为第二值,则认为该比特位对应的FlexE实例不在该FlexE group中,第二值可以为0。
灵活以太实例号(FlexE instance number):表示组中此FlexE实例的标识(identity of this FlexE instance within the group)。如图3所示的第二FlexE开销块的第9至第16比特位字段携带该FlexE instance number。
时隙表A和时隙表B:包括FlexE group中所有的FlexE客户端的时隙表配置信息,避免在FlexE客户端在改变时隙带宽配置时,出现流量损失,任意时间只有一张时隙表处于工作状态,如图3所示的第三FlexE开销块的第1至第16比特位字段携带该时隙表A,第17至第32比特位字段携带该时隙表B。
时隙表切换请求(calendar switch request,CSR):在OIF-FlexE-01.0/01.1/02.2/02.1等标准中称为CR,用于切换数据传输时复用端和解复用端工作的时隙表。如图3所示的第三FlexE开销块的第33比特位字段携带该CR。
时隙表切换确认(calendar switch acknowledgement,CSA):在OIF-FlexE-01.0/01.1/02.2/02.1等标准中称为CA,用于确认解复用端可以切换时隙表。如图3所示的第三FlexE开销块的第34比特位字段携带该CA。
同步头(synchronization head,SH):为FlexE开销帧的帧头,如图3所示的FlexE开销块的前2个比特位。
有效同步头位(valid sync header bits,S):如图3所示的第四FlexE开销块至第八FlexE开销块中的SH下的字段携带该S。
段管理通道(management channel-section):用于携带段管理信息,如图3所示的第四FlexE开销块和第五FlexE开销块携带该管理通道。
垫层至垫层管理通道(management channel-shim to shim):用于携带垫层至垫层管理信息,当SC为0时,如图3所示的第六FlexE开销块至第八FlexE开销块携带该管理通道;当SC为1时,如图3所示的第七FlexE开销块和第八FlexE开销块携带该管理通道。
循环冗余校验码(cyclic redundancy check,CRC):用于对FlexE开销帧的内容进行循环冗余校验保护。如图3所示的第三FlexE开销块的第48至第63比特位字段携带该CRC。
除包括上述信息的字段外,FlexE开销帧还包括预留(reserved)字段,如图3所示的第二FlexE开销块的第17至第63比特位字段、第三FlexE开销块的第35至第47比特位字段均为预留字段。
本申请实施例提供了一种网络同步的方法,该方法应用于支持FlexE的网络设备,该方法通过携带能够指示目标网络设备根据同步信息进行同步的同步模式指示,能够指示支持FlexE的网络设备中哪些网络设备作为目标网络设备来处理同步信息以及该网络设备处理同步信息的方式,从而实现对网络设备的自动配置,简化了需要网络同步时对网络设备进行配置的操作流程,提高了网络同步的效率。
本申请实施例的方法可应用在图4所示的实施场景中,该实施场景包括支持FlexE的客户边缘设备和运营商边缘设备(第一节点设备、第二节点设备),以及支持FlexE同步、光传送网络(optical transport network,OTN)同步或其它同步方式的网络中间节点设备,如图4所示,第一节点设备、第二节点设备均为支持FlexE的网络节点设备。各运营商边缘设备(第一节点设备、第二节点设备)与客户边缘设备能够通过FlexE group进行信息的交互,而运营 商边缘设备与中间节点设备能够进行同步信息的交互。示例性地,支持FlexE接入的运营商网络包括分片分组网络(slicing packet network,SPN)、城域传送网络(metro transport network,MTN)或光传送网络(optical transport network,OTN)中的任一种。
结合图4所示的实施场景,本申请实施例提供的网络同步的方法如图5所示,包括但不限于步骤501至步骤504。
步骤501、第一网络设备获取同步模式指示以及同步信息。
其中,第一网络设备包括支持FlexE的客户边缘设备,或支持FlexE的运营商边缘设备(例如第一节点设备),或支持FlexE的网络的中间节点设备,其中,支持FlexE的运营商边缘设备和支持FlexE的网络的中间节点设备均属于支持FlexE的网络的节点设备;第一网络设备通过FlexE获取同步模式指示以及同步信息(例如从第一客户边缘设备),该同步模式指示用于指示目标网络设备根据同步信息进行同步,该目标网络设备为任一网络设备。
在一种可能的实现方式中,第一网络设备获取目标网络设备指示信息,该目标网络设备指示信息用于指示FlexE段(section)的另一端设备或FlexE路径(path)的另一端设备为目标网络设备。示例性地,同步模式指示包括该目标网络设备指示信息。通过该目标网络设备指示信息进一步指示目标网络设备,无需占用额外的资源即可实现,在达到指示目标网络设备的基础上,进一步节省了资源。
示例性地,该目标网络设备指示信息通过指示位指示FlexE段的另一端设备或FlexE路径的另一端设备为目标网络设备,例如,该目标网络设备指示信息通过第一指示位组合来指示FlexE段的另一端设备为目标网络设备,例如,第一指示位组合为(0,1),FlexE段的另一端设备为第一节点设备;该目标网络设备指示信息通过第二指示位组合来指示FlexE路径的另一端设备为目标网络设备,例如,第二指示位组合为(1,0),FlexE路径的另一端设备为第二节点设备;该目标网络设备指示信息通过第三指示位组合来指示任一网络设备均不是目标网络设备,即任一网络设备均不进入FlexE同步模式,例如,第三指示位组合为(0,0)。示例性地,目标网络设备指示信息通过指示位指示指定FlexE段的设备或指定FlexE路径对应的设备为目标网络设备,例如,目标网络设备指示信息包括第一指示位、第二指示位和第三指示位中的任一种,该目标网络设备指示信息通过第一指示位来指示指定FlexE段的网络设备为目标网络设备,通过第二指示位来指示指定FlexE路径中的任一节点设备均为目标网络设备,通过第三指示位来指示指定FlexE路径的端节点设备为目标网络设备。
在一种可能的实现方式中,同步模式指示包括第一模式指示,该第一模式指示用于指示接收目标网络设备进入FlexE同步模式。在FlexE同步模式下,该目标网络设备根据同步信息进行同步。需要说明的是,该第一模式指示可独立于已有的模式,也可作为附加属性叠加到已有模式上,处理方式较为灵活。
在一种可能的实现方式中,FlexE开销帧包括同步模式指示以及同步信息。由于FlexE开销帧包括同步模式指示及同步信息,可以使得目标网络设备在不处理业务块的情况下,基于该FlexE开销帧即可实现网络同步。示例性地,FlexE开销帧包括至少一个同步模式指示字段,该至少一个同步模式指示字段包括同步模式指示。该FlexE开销帧的至少一个同步模式指示字段包括同步模式指示,包括但不限于以下两种方式。
方式一:至少一个同步模式指示字段中的第一同步模式指示字段包括一个或多个比特位,该一个或多个比特位包括同步模式指示。
该方式一中,同步模式指示可全部包括在第一同步模式指示字段中,而该第一同步模式指示字段可以是FlexE开销帧包括的至少一个同步模式指示字段中的任一同步模式指示字段。示例性地,FlexE开销帧包括两个同步模式指示字段,分别为同步模式指示字段一和同步模式指示字段二。同步模式指示字段一为FlexE开销帧的第二FlexE开销块的第17至第63比特位字段,同步模式指示字段二为FlexE开销帧的第三FlexE开销块的第35至第47比特位字段。例如,可将同步模式指示字段一作为第一同步模式指示字段,通过该同步模式指示字段一的一个或多个比特位来携带该同步模式指示。又例如,可将同步模式指示字段二作为第一同步模式指示字段,通过同步模式指示字段二的一个或多个比特位来携带同步模式指示。
方式二:至少一个同步模式指示字段包括第二同步模式指示字段,第二同步模式指示字段包括至少一个比特位,该至少一个比特位包括同步模式指示的至少一部分。
该方式二中,同步模式指示包括在多个第二同步模式指示字段中,每个第二同步模式指示字段的至少一个比特位包括同步模式指示的至少一部分,而FlexE开销帧包括的至少一个同步模式指示字段中有至少两个同步模式指示字段是第二同步模式指示字段。仍以FlexE开销帧包括两个同步模式指示字段,分别为同步模式指示字段一和同步模式指示字段二,同步模式指示字段一为FlexE开销帧的第二FlexE开销块的第17至第63比特位字段,同步模式指示字段二为FlexE开销帧的第三FlexE开销块的第35至第47比特位字段为例,将该同步模式指示字段一和同步模式指示字段二均作为第二同步模式指示字段,同步模式指示字段一和同步模式指示字段二分别包括同步模式指示的一部分。例如,同步模式指示为0100,同步模式指示字段一中有两个比特位包括01,同步模式指示字段二中有两个比特位包括00。通过同步模式指示字段一和同步模式指示字段二来实现携带同步模式指示。
此外,上述举例仅以FlexE开销帧包括的全部同步模式指示字段均作为第二同步模式指示字段为例进行说明,在一种可能的实现方式中,也可以将FlexE开销帧包括的部分同步模式指示字段作为第二同步模式指示字段,在实施时,选择几个同步模式指示字段作为第二同步模式指示字段,以及每个第二同步模式指示字段中使用哪些比特位来携带同步模式指示,本申请实施例不进行限定,且采用上述方式一还是采用上述方式二,本申请实施例也不进行限定,可基于同步模式指示的比特位长度和应用场景灵活设置。
需要说明的是,在一种可能的实现方式中,上述同步模式指示字段可以在已有的FlexE开销帧的预留字段上进行复用。例如,将图3所示的FlexE开销帧的多个预留字段均作为同步模式指示字段。
由于同步模式指示包括在FlexE开销帧的同步模式指示字段中的方式可以有多种,使得同步模式指示的携带方式更为灵活。
示例性地,FlexE开销帧包括第六FlexE开销块,该第六FlexE开销块包括同步信息的方式,包括:将同步信息封装为以太帧,第六FlexE开销块包括该以太帧。其中,同步信息包括但不限于精确时间同步协议(precision time protocol,PTP)信息和同步状态信息(synchronous status message,SSM)中的一种或多种,PTP信息用于指示目标网络设备进行时间同步,同步状态信息用于指示目标网络设备进行频率同步。针对同步信息的几种情况,第六FlexE开销块包括同步信息包括但不限于以下三种情况。
情况一、同步信息包括PTP信息,不包括同步状态信息。
在一种可能的实现方式中,第一网络设备根据IEEE802.3以太封装机制将PTP信息封装 为以太帧,将该以太帧分成块插入FlexE开销帧的第六FlexE开销块中,使FlexE开销帧包括该PTP信息。示例性地,第一网络设备还可以根据IP封装机制将该PTP信息封装为数据包,进而根据IEEE802.3以太封装机制将该数据包封装为以太帧,将该以太帧插入FlexE开销帧的第六FlexE开销块中,使FlexE开销帧包括该PTP信息。
情况二、同步信息包括同步状态信息,不包括PTP信息。
在一种可能的实现方式中,第一网络设备根据IEEE802.3以太封装机制将同步状态信息封装为以太帧,将该以太帧插入FlexE开销帧的第六FlexE开销块中,使FlexE开销帧包括该同步状态信息。
情况三、同步信息包括PTP信息和同步状态信息。
在一种可能的实现方式中,第一网络设备将PTP信息封装为第一以太帧,将同步状态信息封装为第二以太帧,进而将第一以太帧和第二以太帧分成块插入FlexE开销帧的第六FlexE开销块中,使FlexE开销帧包括该PTP信息和同步状态信息。第一网络设备封装PTP信息和同步状态信息的方式分别与情况一和情况二中的封装方式原理相同,此处不再赘述。
无论是上述哪种情况,将封装的以太帧插入FlexE开销帧的第六FlexE开销块中的方式包括但不限于:将以太帧切分为N个码块1,2,…,N-1,N,将N个码块中的第1至i个码块连续插入到第一FlexE开销帧的第六FlexE开销块的比特位字段,N为大于等于2的正整数,i为大于等于1的正整数且i小于N;将N个码块中的第i+1至j个码块连续插入第二FlexE开销帧的第六FlexE开销块的比特位字段,第二FlexE开销帧为邻接第一FlexE开销帧的下一个FlexE开销帧,j为正整数且i+1≤j≤N。
除了将封装的以太帧切分为N个码块,分别插入到不同FlexE开销帧的第六FlexE开销块的比特位字段的方式外,如果一个FlexE开销帧的第六FlexE开销块的比特位字段大于N个码块的长度,也可将该N个码块均插入到一个FlexE开销帧的第六FlexE开销块的比特位字段。示例性地,无论是将N个码块插入到一个FlexE开销帧的第六FlexE开销块的比特位字段中,还是插入到多个FlexE开销帧的第六FlexE开销块的比特位字段中,若N个码块未插满FlexE开销帧的第六FlexE开销块的比特位字段,则将第六FlexE开销块的剩余比特位字段置为目标保留值,例如,目标保留值为0x00。
示例性地,当同步信息包括PTP信息和同步状态信息时,将封装PTP信息的第一以太帧切分为多个第一码块,将封装同步状态信息的第二以太帧切分为多个第二码块;将多个第一码块和多个第二码块插入FlexE开销帧的第六FlexE开销块的比特位字段的顺序可以为:将多个第一码块全部插入FlexE开销帧的第六FlexE开销块的比特位字段后,将多个第二码块插入FlexE开销帧的第六FlexE开销块的比特位字段,或将多个第二码块全部插入FlexE开销帧的第六FlexE开销块的比特位字段后,将多个第一码块插入FlexE开销帧的第六FlexE开销块的比特位字段,或将多个第一码块与多个第二码块混合插入FlexE开销帧的第六FlexE开销块的比特位字段。
步骤502、第一网络设备通过支持FlexE的网络发送同步模式指示以及同步信息。
其中,第一网络设备通过支持FlexE的网络发送同步模式指示以及同步信息。在一种可能的实现方式中,同步模式指示以及同步信息由第一网络设备通过与该第一网络设备相连的FlexE group发送。示例性地,与第一网络设备相连的FlexE group包括多个PHY,则同步模式指示以及同步信息可以由第一网络设备通过多个PHY中的至少一个PHY发送。
在一种可能的实现方式中,第一网络设备为支持FlexE的客户边缘设备,若支持FlexE的网络为SPN、MTN或OTN的任一种,第一网络设备通过与该第一网络设备相连的FlexE group发送同步模式指示以及同步信息。该方法能够应用于支持FlexE的不同网络中,应用的场景较为丰富。
在一种可能的实现方式中,第一网络设备为支持FlexE的网络的节点设备,若支持FlexE的网络为SPN或MTN,第一网络设备通过与该第一网络设备相连的FlexE group发送同步模式指示以及同步信息;若支持FlexE的网络为OTN,第一网络设备通过与该第一网络设备相连的FlexE group发送同步模式指示,第一网络设备将同步信息转换为OTN同步信息,通过OTN的同步信道发送该OTN同步信息。
上述步骤501和步骤502均为第一网络设备侧执行该网络同步的过程,接下来,以第二网络设备侧为例,对网络同步的方法进行说明。
步骤503、第二网络设备通过支持FlexE的网络接收同步模式指示以及同步信息。
其中,第二网络设备包括支持FlexE的客户边缘设备,或支持FlexE的运营商边缘设备(例如第二节点设备),或支持FlexE的网络的中间节点设备,其中,支持FlexE的运营商边缘设备和支持FlexE的网络的中间节点设备均属于支持FlexE的网络的节点设备。同步模式指示用于指示目标网络设备根据同步信息进行同步,该目标网络设备为任一网络设备。示例性地,第二网络设备通过FlexE group接收第一网络设备发送的同步模式指示以及同步信息。
步骤504、基于同步模式指示,第二网络设备根据同步信息进行同步。
在一种可能的实现方式中,同步模式指示包括第一指示,第一模式指示用于指示目标网络设备进入FlexE同步模式;在本实施例中,第二网络设备为目标网络设备,基于同步模式指示,第二网络设备根据同步信息进行同步,包括:基于该第一模式指示,第二网络设备进入FlexE同步模式,在该FlexE同步模式下,第二网络设备根据同步信息进行同步。
在一种可能的实现方式中,第二网络设备接收目标网络设备指示信息,目标网络设备指示信息用于指示FlexE段(section)的另一端设备或FlexE路径(path)的另一端设备为目标网络设备。示例性地,同步模式指示包括该目标网络设备指示信息。示例性地,该目标网络设备指示信息通过指示位指示FlexE段的另一端设备或FlexE路径的另一端设备为目标网络设备,例如,该目标网络设备指示信息通过第一指示位组合来指示FlexE段的另一端设备为目标网络设备,例如,第一指示位组合为(0,1);该目标网络设备指示信息通过第二指示位组合来指示FlexE路径的另一端设备为目标网络设备,例如,第二指示位组合为(1,0);该目标网络设备指示信息通过第三指示位组合来指示任一网络设备均不是目标网络设备,即任一网络设备均不进入FlexE同步模式,例如,第三指示位组合为(0,0)。
如果该目标网络设备指示信息包括第一指示位组合,则明确指示出FlexE段的另一端设备为目标网络设备,即该FlexE段的另一端设备接收到同步模式指示和同步信息后才进行同步处理,对于不是该FlexE段的另一端设备的网络设备,即使接收到同步模式指示和同步信息,也并不会进行同步处理。其中,目标网络设备指示信息包括第二指示位组合或第三指示位组合时,指示出的目标网络设备和除目标网络设备以外的其他网络设备,对接收到的同步模式指示和同步信息的响应方式与目标网络设备指示信息包括第一指示位组合时,指示出的目标网络设备和除目标网络设备以外的其他网络设备,对接收到的同步模式指示和同步信息的响应方式原理相同,此处不再赘述。
在一种可能的实现方式中,目标网络设备指示信息通过指示位来指示FlexE段的设备或FlexE路径对应的设备为目标网络设备,例如,目标网络设备指示信息包括第一指示位、第二指示位和第三指示位中的任一种;如果该目标网络设备指示信息包括第一指示位,则明确指示出指定FlexE段的网络设备为目标网络设备,即属于指定FlexE段的网络设备接收到同步模式指示和同步信息后才进行同步处理,对于不属于指定FlexE段的网络设备,即使接收到同步模式指示和同步信息,也并不会进行同步处理;如果目标网络设备指示信息包括第二指示位,则明确指示出指定FlexE路径中的任一节点设备均为目标网络设备;如果目标网络设备指示信息包括第三指示位,则明确指示出指定FlexE路径中的端节点设备为目标网络设备。其中,目标网络设备指示信息包括第一指示位、第二指示位或第三指示位中任一种时,指示出的目标网络设备和除目标网络设备以外的其他网络设备,对接收到的同步模式指示和同步信息的响应方式与目标网络设备指示信息包括第一指示位组合时,指示出的目标网络设备和除目标网络设备以外的其他网络设备,对接收到的同步模式指示和同步信息的响应方式原理相同,此处不再赘述。
以目标网络设备指示信息包括第一指示位组合为例,若第二网络设备为FlexE段的另一端设备,基于该目标网络设备指示信息,第二网络设备进入FlexE同步模式,在该FlexE同步模式下,第二网络设备根据同步信息进行同步;若第二网络设备不是FlexE段的另一端设备,基于该目标网络设备指示信息,第二网络设备不进入FlexE同步模式,第二网络设备不根据同步信息进行同步。
其中,第二网络设备根据同步信息进行同步时,针对同步信息的几种情况,该过程包括但不限于如下三种情况。
情况一、同步信息包括PTP信息,不包括同步状态信息SSM。
针对情况一,该第二网络设备根据PTP信息选择时间同步源,根据选择的时间同步源进行时间同步。
在一种可能的实现方式中,第二网络设备将FlexE开销帧包括的PTP信息根据IEEE802.3以太解封装机制解封装得到PTP信息,根据得到的PTP信息选择时间同步源,根据选择的时间同步源进行时间同步。示例性地,若第二网络设备将FlexE开销帧包括的PTP信息根据IEEE802.3以太解封装机制解封装得到根据IP封装机制封装的数据包,第二网络设备进一步根据IP解封装机制将该数据包解封装得到PTP信息。
情况二、同步信息包括同步状态信息SSM,不包括PTP信息。
针对情况二,该第二网络设备根据同步状态信息选择频率同步源,根据选择的频率同步源进行频率同步。
在一种可能的实现方式中,第二网络设备将FlexE开销帧包括的同步状态信息根据IEEE802.3以太解封装机制解封装得到同步状态信息,根据得到的同步状态信息选择频率同步源,根据选择的频率同步源进行频率同步。
情况三、同步信息包括PTP信息和同步状态信息SSM。
针对情况三,该第二网络设备根据PTP信息选择时间同步源,根据选择的时间同步源进行时间同步;可选地,该第二网络设备根据同步状态信息选择频率同步源,根据选择的频率同步源进行频率同步。
其中,第二网络设备得到PTP信息和同步状态信息的过程分别与上述情况一和情况二中 的过程相同,此处不再赘述。
本申请实施例提供的方法通过包括同步模式指示,能够指示目标网络设备根据同步信息进行同步,即指示支持FlexE的网络设备中哪些网络设备处理同步信息以及该网络设备处理同步信息的方式,实现对网络设备的自动配置,简化了需要网络同步时对网络设备进行配置的操作流程,提高了网络同步的效率。此外,本实施例提供的方法包括的同步模式指示,能够指示支持FlexE的网络设备中的每一跳节点设备皆处理同步信息,提高了承载数据的网络的同步精度。
需要说明的是,上述网络同步的方法中的FlexE同步模式可以是新定义的模式,也可以在已有模式上进行功能复用。例如,FlexE定义了三种模式,分别为FlexE感知(aware)模式、FlexE不感知(unaware)模式和FlexE终结(termination)模式。其中,FlexE感知模式用于实现减少FlexE的业务数据传输时的带宽占用;FlexE不感知模式用于实现在已有以太网设备上FlexE的业务数据的传输;FlexE终结模式用于实现对不同FlexE的业务数据的分流。示例性地,将本实施例中的FlexE同步模式的功能在FlexE感知模式上叠加,将FlexE感知模式作为FlexE同步模式,以在实现FlexE感知模式原有功能的基础上,进一步叠加实现同步。
本申请实施例还提供了一种网络同步的装置。图6是本申请实施例提供的一种网络同步的装置的结构示意图,该装置应用于支持灵活以太FlexE的第一网络设备,该第一网络设备为上述图5所示的第一网络设备。基于图6所示的如下多个模块,该图6所示的网络同步的装置能够执行第一网络设备所执行的全部或部分操作。应理解到,该装置可以包括比所示模块更多的附加模块或者省略其中所示的一部分模块,本申请实施例对此并不进行限制。如图6所示,该装置包括:
获取模块601,用于获取同步模式指示以及同步信息,同步模式指示用于指示目标网络设备根据同步信息进行同步;
发送模块602,用于通过支持FlexE的网络发送同步模式指示以及同步信息。
在一种可能的实现方式中,该发送模块602,用于通过支持FlexE的网络发送FlexE开销帧,FlexE开销帧包括同步模式指示以及同步信息。
在一种可能的实现方式中,同步模式指示包括第一模式指示,第一模式指示用于指示目标网络设备进入FlexE同步模式。
在一种可能的实现方式中,获取模块601,还用于获取目标网络设备指示信息,该目标网络设备指示信息用于指示FlexE段的另一端设备或FlexE路径的另一端设备为目标网络设备。
在一种可能的实现方式中,同步模式指示包括目标网络设备指示信息。
在一种可能的实现方式中,FlexE开销帧包括至少一个同步模式指示字段,该至少一个同步模式指示字段包括同步模式指示;FlexE开销帧包括第六FlexE开销块,该第六FlexE开销块包括同步信息。
在一种可能的实现方式中,至少一个同步模式指示字段中的第一同步模式指示字段包括一个或多个比特位,该一个或多个比特位包括同步模式指示;或者,至少一个同步模式指示字段包括第二同步模式指示字段,第二同步模式指示字段包括至少一个比特位,该至少一个比特位包括同步模式指示的至少一部分。
在一种可能的实现方式中,该装置还包括:
封装模块,用于将同步信息封装为以太帧,第六FlexE开销块包括该以太帧。
在一种可能的实现方式中,该封装模块,还用于将以太帧切分为N个码块1,2,…,N-1,N,将N个码块中的第1至i个码块连续插入到第一FlexE开销帧的第六FlexE开销块的比特位字段,N为大于等于2的正整数,i为大于等于1的正整数且i小于N;将N个码块中的第i+1至j个码块连续插入第二FlexE开销帧的第六FlexE开销块的比特位字段,第二FlexE开销帧为邻接第一FlexE开销帧的下一个FlexE开销帧,j为正整数且i+1≤j≤N。
在一种可能的实现方式中,同步信息包括精确时间同步协议PTP信息和同步状态信息SSM中的一种或多种,PTP信息用于指示目标网络设备进行时间同步,同步状态信息用于指示目标网络设备进行频率同步。
在一种可能的实现方式中,支持灵活以太FlexE的第一网络设备包括:支持FlexE的客户边缘设备或支持FlexE的网络的节点设备,支持FlexE的网络包括分片分组网络SPN、城域传送网络MTN或光传送网络OTN中的任一种。
图7是本申请实施例提供的一种网络同步的装置的结构示意图,该装置应用于支持灵活以太FlexE的第二网络设备,该第二网络设备为上述图5所示的第二网络设备。基于图7所示的如下多个模块,该图7所示的网络同步的装置能够执行第二网络设备所执行的全部或部分操作。应理解到,该装置可以包括比所示模块更多的附加模块或者省略其中所示的一部分模块,本申请实施例对此并不进行限制。如图7所示,该装置包括:
接收模块701,用于通过支持FlexE的网络接收同步模式指示以及同步信息,同步模式指示用于指示目标网络设备根据同步信息进行同步;
同步模块702,用于基于同步模式指示,根据同步信息进行同步。
在一种可能的实现方式中,同步模式指示包括第一模式指示,第一模式指示用于指示目标网络设备进入FlexE同步模式;该同步模块702,用于基于第一模式指示,进入FlexE同步模式,在FlexE同步模式下,根据同步信息进行同步。
在一种可能的实现方式中,接收模块701,还用于接收目标网络设备指示信息,该目标网络设备指示信息用于指示FlexE段的另一端设备或FlexE路径的另一端设备为目标网络设备。
在一种可能的实现方式中,同步模式指示包括目标网络设备指示信息。
在一种可能的实现方式中,接收模块701,用于接收FlexE开销帧,该FlexE开销帧包括同步模式指示以及同步信息;该装置还包括解析模块,用于解析FlexE开销帧,得到FlexE开销帧携带的同步模式指示以及同步信息。
在一种可能的实现方式中,同步信息包括精确时间同步协议PTP信息和同步状态信息SSM中的一种或多种;若同步信息包括PTP信息,该同步模块702,用于根据PTP信息选择时间同步源,根据时间同步源进行时间同步;若同步信息包括同步状态信息,该同步模块702,用于根据同步状态信息选择频率同步源,根据频率同步源进行频率同步。
在一种可能的实现方式中,支持灵活以太FlexE的第二网络设备包括:支持FlexE的客户边缘设备或支持FlexE的网络的节点设备,支持FlexE的网络包括分片分组网络SPN、城域传送网络MTN或光传送网络OTN中的任一种。
应理解的是,上述图6、图7提供的装置在实现其功能时,仅以上述各功能模块的划分进行举例说明,实际应用中,可以根据需要而将上述功能分配由不同的功能模块完成,即将设备的内部结构划分成不同的功能模块,以完成以上描述的全部或者部分功能。另外,上述实施例提供的装置与方法实施例属于同一构思,其具体实现过程详见方法实施例,这里不再赘述。
上述实施例中的网络设备的硬件结构如图8所示的网络设备1500,包括收发器1501、处理器1502和存储器1503。收发器1501、处理器1502和存储器1503之间通过总线1504连接。其中,收发器1501用于接收同步模式指示和同步信息和发送同步模式指示和同步信息,存储器1503用于存放指令或程序代码,处理器1502用于调用存储器1503中的指令或程序代码使得网络设备执行上述方法实施例中第一网络设备的相关处理步骤。在具体实施例中,本申请实施例的网络设备1500可对应于上述各个方法实施例中的第一网络设备,网络设备1500中的处理器1502读取存储器1503中的指令或程序代码,使图8所示的网络设备1500能够执行第一网络设备所执行的全部或部分操作。
在具体实施例中,本申请实施例的网络设备1500可对应于上述各个方法实施例中的第二网络设备,网络设备1500中的处理器1502读取存储器1503中的指令或程序代码,使图8所示的网络设备1500能够执行第二网络设备所执行的全部或部分操作。
参见图9,图9示出了本申请一个示例性实施例提供的网络设备2000的结构示意图。图9所示的网络设备2000用于执行上述图5所示的网络同步的方法所涉及的操作。该网络设备2000例如是交换机、路由器等。
如图9所示,网络设备2000包括至少一个处理器2001、存储器2003以及至少一个通信接口2004。
处理器2001例如是通用中央处理器(central processing unit,CPU)、数字信号处理器(digital signal processor,DSP)、网络处理器(network processer,NP)、图形处理器(graphics processing unit,GPU)、神经网络处理器(neural-network processing units,NPU)、数据处理单元(data processing unit,DPU)、微处理器或者一个或多个用于实现本申请方案的集成电路。例如,处理器2001包括专用集成电路(application-specific integrated circuit,ASIC),可编程逻辑器件(programmable logic device,PLD)或者其他可编程逻辑器件、晶体管逻辑器件、硬件部件或者其任意组合。PLD例如是复杂可编程逻辑器件(complex programmable logic device,CPLD)、现场可编程逻辑门阵列(field-programmable gate array,FPGA)、通用阵列逻辑(generic array logic,GAL)或其任意组合。其可以实现或执行结合本发明实施例公开内容所描述的各种逻辑方框、模块和电路。处理器也可以是实现计算功能的组合,例如包括一个或多个微处理器组合,DSP和微处理器的组合等等。
可选的,网络设备2000还包括总线。总线用于在网络设备2000的各组件之间传送信息。总线可以是外设部件互连标准(peripheral component interconnect,简称PCI)总线或扩展工业标准结构(extended industry standard architecture,简称EISA)总线等。总线可以分为地址总线、数据总线、控制总线等。为便于表示,图9中仅用一条粗线表示,但并不表示仅有一根总线或一种类型的总线。图9中网络设备2000的各组件之间除了采用总线连接,还可采用其他方式连接,本发明实施例不对各组件的连接方式进行限定。
存储器2003例如是只读存储器(read-only memory,ROM)或可存储静态信息和指令的其 它类型的静态存储设备,又如是随机存取存储器(random access memory,RAM)或者可存储信息和指令的其它类型的动态存储设备,又如是电可擦可编程只读存储器(electrically erasable programmable read-only memory,EEPROM)、只读光盘(compact disc read-only memory,CD-ROM)或其它光盘存储、光碟存储(包括压缩光碟、激光碟、光碟、数字通用光碟、蓝光光碟等)、磁盘存储介质或者其它磁存储设备,或者是能够用于携带或存储具有指令或数据结构形式的期望的程序代码并能够由计算机存取的任何其它介质,但不限于此。存储器2003例如是独立存在,并通过总线与处理器2001相连接。存储器2003也可以和处理器2001集成在一起。
通信接口2004使用任何收发器一类的装置,用于与其它设备或通信网络通信,通信网络可以为以太网、无线接入网(RAN)或无线局域网(wireless local area networks,WLAN)等。通信接口2004可以包括有线通信接口,还可以包括无线通信接口。具体的,通信接口2004可以为以太(ethernet)接口、快速以太(fast ethernet,FE)接口、千兆以太(gigabit ethernet,GE)接口,异步传输模式(asynchronous transfer mode,ATM)接口,无线局域网(wireless local area networks,WLAN)接口,蜂窝网络通信接口或其组合。以太网接口可以是光接口,电接口或其组合。在本申请实施例中,通信接口2004可以用于网络设备2000与其他设备进行通信。
在具体实现中,作为一种实施例,处理器2001可以包括一个或多个CPU,如图9中所示的CPU0和CPU1。这些处理器中的每一个可以是一个单核(single-CPU)处理器,也可以是一个多核(multi-CPU)处理器。这里的处理器可以指一个或多个设备、电路、和/或用于处理数据(例如计算机程序指令)的处理核。
在具体实现中,作为一种实施例,网络设备2000可以包括多个处理器,如图9中所示的处理器2001和处理器2002。这些处理器中的每一个可以是一个单核处理器(single-CPU),也可以是一个多核处理器(multi-CPU)。这里的处理器可以指一个或多个设备、电路、和/或用于处理数据(如计算机程序指令)的处理核。
在具体实现中,作为一种实施例,网络设备2000还可以包括输出设备和输入设备。输出设备和处理器2001通信,可以以多种方式来显示信息。例如,输出设备可以是液晶显示器(liquid crystal display,LCD)、发光二级管(light emitting diode,LED)显示设备、阴极射线管(cathode ray tube,CRT)显示设备或投影仪(projector)等。输入设备和处理器2001通信,可以以多种方式接收用户的输入。例如,输入设备可以是鼠标、键盘、触摸屏设备或传感设备等。
在一些实施例中,存储器2003用于存储执行本申请方案的程序代码2005,处理器2001可以执行存储器2003中存储的程序代码2005。也即是,网络设备2000可以通过处理器2001以及存储器2003中的程序代码2005,来实现方法实施例提供的网络同步的方法。程序代码2005中可以包括一个或多个软件模块。可选地,处理器2001自身也可以存储执行本申请方案的程序代码或指令。
在具体实施例中,本申请实施例的网络设备2000可对应于上述各个方法实施例中的第一网络设备,网络设备2000中的处理器2001读取存储器2003中的程序代码2005或处理器2001自身存储的程序代码或指令,使图9所示的网络设备2000能够执行第一网络设备所执行的全部或部分操作。
在具体实施例中,本申请实施例的网络设备2000可对应于上述各个方法实施例中的第二网络设备,网络设备2000中的处理器2001读取存储器2003中的程序代码2005或处理器2001自身存储的程序代码或指令,使图9所示的网络设备2000能够执行第二网络设备所执行的全部或部分操作。
网络设备2000还可以对应于上述图6、7所示的装置,图6、7所示的装置中的每个功能模块采用网络设备2000的软件实现。换句话说,图6、7所示的装置包括的功能模块为网络设备2000的处理器2001读取存储器2003中存储的程序代码2005后生成的。
其中,图5所示的网络同步的方法的各步骤通过网络设备2000的处理器中的硬件的集成逻辑电路或者软件形式的指令完成。结合本申请实施例所公开的方法的步骤可以直接体现为硬件处理器执行完成,或者用处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器,闪存、只读存储器,可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器,处理器读取存储器中的信息,结合其硬件完成上述方法的步骤,为避免重复,这里不再详细描述。
本申请实施例还提供了一种网络同步的系统,该系统包括:第一网络设备和第二网络设备;第一网络设备用于执行图5所述的第一网络设备所执行的方法,第二网络设备用于执行图5所述的第二网络设备所执行的方法。
该系统的第一网络设备和第二网络设备各自的功能可参考上述图5所示的相关描述,此处不再一一赘述。
应理解的是,上述处理器可以是中央处理器(central processing unit,CPU),还可以是其他通用处理器、数字信号处理器(digital signal processing,DSP)、专用集成电路(application specific integrated circuit,ASIC)、现场可编程门阵列(field programmable gate array,FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件等。通用处理器可以是微处理器或者是任何常规的处理器等。值得说明的是,处理器可以是支持进阶精简指令集机器(advanced RISC machines,ARM)架构的处理器。
进一步地,在一种可选的实施例中,上述存储器可以包括只读存储器和随机存取存储器,并向处理器提供指令和数据。存储器还可以包括非易失性随机存取存储器。例如,存储器还可以存储设备类型的信息。
该存储器可以是易失性存储器或非易失性存储器,或可包括易失性和非易失性存储器两者。其中,非易失性存储器可以是只读存储器(read-only memory,ROM)、可编程只读存储器(programmable ROM,PROM)、可擦除可编程只读存储器(erasable PROM,EPROM)、电可擦除可编程只读存储器(electrically EPROM,EEPROM)或闪存。易失性存储器可以是随机存取存储器(random access memory,RAM),其用作外部高速缓存。通过示例性但不是限制性说明,许多形式的RAM可用。例如,静态随机存取存储器(static RAM,SRAM)、动态随机存取存储器(dynamic random access memory,DRAM)、同步动态随机存取存储器(synchronous DRAM,SDRAM)、双倍数据速率同步动态随机存取存储器(double data date SDRAM,DDR SDRAM)、增强型同步动态随机存取存储器(enhanced SDRAM,ESDRAM)、同步连接动态随机存取存储器(synchlink DRAM,SLDRAM)和直接内存总线随机存取存储器(direct rambus RAM,DR RAM)。
还提供了一种计算机可读存储介质,存储介质中存储有至少一条程序指令或代码,所述 程序指令或代码由处理器加载并执行时以使计算机实现如上图5所示的网络同步的方法。
本申请提供了一种计算机程序,当计算机程序被计算机执行时,可以使得处理器或计算机执行上述方法实施例中对应的各个步骤和/或流程。
提供了一种芯片,包括处理器,用于从存储器中调用并运行所述存储器中存储的指令,使得安装有所述芯片的通信设备执行上述各方面中的方法。
提供另一种芯片,包括:输入接口、输出接口、处理器和存储器,所述输入接口、输出接口、所述处理器以及所述存储器之间通过内部连接通路相连,所述处理器用于执行所述存储器中的代码,当所述代码被执行时,所述处理器用于执行上述各方面中的方法。
在上述实施例中,可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时,可以全部或部分地以计算机程序产品的形式实现。所述计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行所述计算机程序指令时,全部或部分地产生按照本申请所述的流程或功能。所述计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。所述计算机指令可以存储在计算机可读存储介质中,或者从一个计算机可读存储介质向另一个计算机可读存储介质传输,例如,所述计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线)或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。所述计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。所述可用介质可以是磁性介质,(例如,软盘、硬盘、磁带)、光介质(例如,DVD)、或者半导体介质(例如固态硬盘,solid state disk)等。
以上所述的具体实施方式,对本申请的目的、技术方案和有益效果进行了进一步详细说明,所应理解的是,以上所述仅为本申请的具体实施方式而已,并不用于限定本申请的保护范围,凡在本申请的技术方案的基础之上,所做的任何修改、等同替换、改进等,均应包括在本申请的保护范围之内。
本领域普通技术人员可以意识到,结合本文中所公开的实施例中描述的各方法步骤和模块,能够以软件、硬件、固件或者其任意组合来实现,为了清楚地说明硬件和软件的可互换性,在上述说明中已经按照功能一般性地描述了各实施例的步骤及组成。这些功能究竟以硬件还是软件方式来执行,取决于技术方案的特定应用和设计约束条件。本领域普通技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能,但是这种实现不应认为超出本申请的范围。
本领域普通技术人员可以理解实现上述实施例的全部或部分步骤可以通过硬件来完成,也可以通过程序来指令相关的硬件完成,该程序可以存储于一种计算机可读存储介质中,上述提到的存储介质可以是只读存储器,磁盘或光盘等。
当使用软件实现时,可以全部或部分地以计算机程序产品的形式实现。该计算机程序产品包括一个或多个计算机程序指令。作为示例,本申请实施例的方法可以在机器可执行指令的上下文中被描述,机器可执行指令诸如包括在目标的真实或者虚拟处理器上的器件中执行的程序模块中。一般而言,程序模块包括例程、程序、库、对象、类、组件、数据结构等,其执行特定的任务或者实现特定的抽象数据结构。在各实施例中,程序模块的功能可以在所描述的程序模块之间合并或者分割。用于程序模块的机器可执行指令可以在本地或者分布式设 备内执行。在分布式设备中,程序模块可以位于本地和远程存储介质二者中。
用于实现本申请实施例的方法的计算机程序代码可以用一种或多种编程语言编写。这些计算机程序代码可以提供给通用计算机、专用计算机或其他可编程的数据处理装置的处理器,使得程序代码在被计算机或其他可编程的数据处理装置执行的时候,引起在流程图和/或框图中规定的功能/操作被实施。程序代码可以完全在计算机上、部分在计算机上、作为独立的软件包、部分在计算机上且部分在远程计算机上或完全在远程计算机或服务器上执行。
在本申请实施例的上下文中,计算机程序代码或者相关数据可以由任意适当载体承载,以使得设备、装置或者处理器能够执行上文描述的各种处理和操作。载体的示例包括信号、计算机可读介质等等。
信号的示例可以包括电、光、无线电、声音或其它形式的传播信号,诸如载波、红外信号等。
机器可读介质可以是包含或存储用于或有关于指令执行系统、装置或设备的程序的任何有形介质。机器可读介质可以是机器可读信号介质或机器可读存储介质。机器可读介质可以包括但不限于电子的、磁的、光学的、电磁的、红外的或半导体系统、装置或设备,或其任意合适的组合。机器可读存储介质的更详细示例包括带有一根或多根导线的电气连接、便携式计算机磁盘、硬盘、随机存储存取器(RAM)、只读存储器(ROM)、可擦除可编程只读存储器(EPROM或闪存)、光存储设备、磁存储设备,或其任意合适的组合。
所属领域的技术人员可以清楚地了解到,为了描述的方便和简洁,上述描述的系统、设备和模块的具体工作过程,可以参见前述方法实施例中的对应过程,在此不再赘述。
在本申请所提供的几个实施例中,应该理解到,所揭露的系统、设备和方法,可以通过其它的方式实现。例如,以上所描述的设备实施例仅仅是示意性的,例如,该模块的划分,仅仅为一种逻辑功能划分,实际实现时可以有另外的划分方式,例如多个模块或组件可以结合或者可以集成到另一个系统,或一些特征可以忽略,或不执行。另外,所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口、设备或模块的间接耦合或通信连接,也可以是电的,机械的或其它的形式连接。
该作为分离部件说明的模块可以是或者也可以不是物理上分开的,作为模块显示的部件可以是或者也可以不是物理模块,即可以位于一个地方,或者也可以分布到多个网络模块上。可以根据实际的需要选择其中的部分或者全部模块来实现本申请实施例方案的目的。
另外,在本申请各个实施例中的各功能模块可以集成在一个处理模块中,也可以是各个模块单独物理存在,也可以是两个或两个以上模块集成在一个模块中。上述集成的模块既可以采用硬件的形式实现,也可以采用软件功能模块的形式实现。
该集成的模块如果以软件功能模块的形式实现并作为独立的产品销售或使用时,可以存储在一个计算机可读存储介质中。基于这样的理解,本申请的技术方案本质上或者说对现有技术做出贡献的部分,或者该技术方案的全部或部分可以以软件产品的形式体现出来,该计算机软件产品存储在一个存储介质中,包括若干指令用以使得一台计算机设备(可以是个人计算机,服务器,或者网络设备等)执行本申请各个实施例中方法的全部或部分步骤。而前述的存储介质包括:U盘、移动硬盘、只读存储器(read-only memory,ROM)、随机存取存储器(random access memory,RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
本申请中术语“第一”“第二”等字样用于对作用和功能基本相同的相同项或相似项进行区分,应理解,“第一”、“第二”、“第n”之间不具有逻辑或时序上的依赖关系,也不对数量和执行顺序进行限定。还应理解,尽管以下描述使用术语第一、第二等来描述各种元素,但这些元素不应受术语的限制。这些术语只是用于将一元素与另一元素区别分开。例如,在不脱离各种所述示例的范围的情况下,第一网络设备可以被称为第二网络设备,并且类似地,第二网络设备可以被称为第一网络设备。第一网络和设备和第二网络设备都可以是网络设备,并且在某些情况下,可以是单独且不同的网络设备。
还应理解,在本申请的各个实施例中,各个过程的序号的大小并不意味着执行顺序的先后,各过程的执行顺序应以其功能和内在逻辑确定,而不应对本申请实施例的实施过程构成任何限定。
本申请中术语“至少一个”的含义是指一个或多个,本申请中术语“多个”的含义是指两个或两个以上,例如,多个第二报文是指两个或两个以上的第二报文。本文中术语“系统”和“网络”经常可互换使用。
应理解,在本文中对各种所述示例的描述中所使用的术语只是为了描述特定示例,而并非旨在进行限制。如在对各种所述示例的描述和所附权利要求书中所使用的那样,单数形式“一个(“a”,“an”)”和“该”旨在也包括复数形式,除非上下文另外明确地指示。
还应理解,术语“包括”(也称“includes”、“including”、“comprises”和/或“comprising”)当在本说明书中使用时指定存在所陈述的特征、整数、步骤、操作、元素、和/或部件,但是并不排除存在或添加一个或多个其他特征、整数、步骤、操作、元素、部件、和/或其分组。
还应理解,术语“若”和“如果”可被解释为意指“当...时”(“when”或“upon”)或“响应于确定”或“响应于检测到”。类似地,根据上下文,短语“若确定...”或“若检测到[所陈述的条件或事件]”可被解释为意指“在确定...时”或“响应于确定...”或“在检测到[所陈述的条件或事件]时”或“响应于检测到[所陈述的条件或事件]”。
应理解,根据A确定B并不意味着仅仅根据A确定B,还可以根据A和/或其它信息确定B。
还应理解,说明书通篇中提到的“一个实施例”、“一实施例”、“一种可能的实现方式”意味着与实施例或实现方式有关的特定特征、结构或特性包括在本申请的至少一个实施例中。因此,在整个说明书各处出现的“在一个实施例中”或“在一实施例中”、“一种可能的实现方式”未必一定指相同的实施例。此外,这些特定的特征、结构或特性可以任意适合的方式结合在一个或多个实施例中。

Claims (40)

  1. 一种网络同步的方法,其特征在于,所述方法应用于支持灵活以太FlexE的第一网络设备,所述方法包括:
    所述第一网络设备获取同步模式指示以及同步信息,所述同步模式指示用于指示目标网络设备根据所述同步信息进行同步;
    所述第一网络设备通过支持FlexE的网络发送所述同步模式指示以及所述同步信息。
  2. 根据权利要求1所述的方法,其特征在于,所述发送所述同步模式指示以及所述同步信息,包括:
    发送FlexE开销帧,所述FlexE开销帧包括所述同步模式指示以及所述同步信息。
  3. 根据权利要求1或2所述的方法,其特征在于,所述同步模式指示包括第一模式指示,所述第一模式指示用于指示目标网络设备进入FlexE同步模式。
  4. 根据权利要求1-3任一所述的方法,其特征在于,所述方法还包括:所述第一网络设备获取目标网络设备指示信息,所述目标网络设备指示信息用于指示FlexE段的另一端设备或FlexE路径的另一端设备为目标网络设备。
  5. 根据权利要求4所述的方法,其特征在于,所述同步模式指示包括所述目标网络设备指示信息。
  6. 根据权利要求2所述的方法,其特征在于,所述FlexE开销帧包括至少一个同步模式指示字段,所述至少一个同步模式指示字段包括所述同步模式指示;
    所述FlexE开销帧包括第六FlexE开销块,所述第六FlexE开销块包括所述同步信息。
  7. 根据权利要求6所述的方法,其特征在于,所述至少一个同步模式指示字段中的第一同步模式指示字段包括一个或多个比特位,所述一个或多个比特位包括所述同步模式指示;
    或者,所述至少一个同步模式指示字段包括第二同步模式指示字段,所述第二同步模式指示字段包括至少一个比特位,所述至少一个比特位包括所述同步模式指示的至少一部分。
  8. 根据权利要求6或7所述的方法,其特征在于,所述第六FlexE开销块包括所述同步信息,包括:
    将所述同步信息封装为以太帧,所述第六FlexE开销块包括所述以太帧。
  9. 根据权利要求8所述的方法,其特征在于,所述第六FlexE开销块包括所述以太帧,包括:
    将所述以太帧切分为N个码块1,2,…,N-1,N,将所述N个码块中的第1至i个码 块连续插入到第一FlexE开销帧的第六FlexE开销块的比特位字段,N为大于等于2的正整数,i为大于等于1的正整数且i小于N;
    将所述N个码块中的第i+1至j个码块连续插入第二FlexE开销帧的第六FlexE开销块的比特位字段,所述第二FlexE开销帧为邻接所述第一FlexE开销帧的下一个FlexE开销帧,j为正整数且i+1≤j≤N。
  10. 根据权利要求1-9任一所述的方法,其特征在于,所述同步信息包括精确时间同步协议PTP信息和同步状态信息SSM中的一种或多种,所述PTP信息用于指示目标网络设备进行时间同步,所述同步状态信息用于指示所述目标网络设备进行频率同步。
  11. 根据权利要求1-10任一所述的方法,其特征在于,所述支持灵活以太FlexE的第一网络设备包括:支持FlexE的客户边缘设备或支持FlexE的网络的节点设备,所述支持FlexE的网络包括分片分组网络SPN、城域传送网络MTN或光传送网络OTN中的任一种。
  12. 一种网络同步的方法,其特征在于,所述方法应用于支持灵活以太FlexE的第二网络设备,所述方法包括:
    所述第二网络设备通过支持FlexE的网络接收同步模式指示以及同步信息,所述同步模式指示用于指示目标网络设备根据所述同步信息进行同步;
    基于所述同步模式指示,所述第二网络设备根据所述同步信息进行同步。
  13. 根据权利要求12所述的方法,其特征在于,所述同步模式指示包括第一模式指示,所述第一模式指示用于指示目标网络设备进入FlexE同步模式;
    所述基于所述同步模式指示,所述第二网络设备根据所述同步信息进行同步,包括:
    基于所述第一模式指示,所述第二网络设备进入所述FlexE同步模式,在所述FlexE同步模式下,所述第二网络设备根据所述同步信息进行同步。
  14. 根据权利要求12或13所述的方法,其特征在于,所述方法还包括:所述第二网络设备接收目标网络设备指示信息,所述目标网络设备指示信息用于指示FlexE段的另一端设备或FlexE路径的另一端设备为目标网络设备。
  15. 根据权利要求14所述的方法,其特征在于,所述同步模式指示包括所述目标网络设备指示信息。
  16. 根据权利要求12-15任一所述的方法,其特征在于,所述接收同步模式指示以及同步信息,包括:
    接收FlexE开销帧,所述FlexE开销帧包括所述同步模式指示以及所述同步信息;
    所述基于所述同步模式指示,所述第二网络设备根据所述同步信息进行同步之前,所述方法还包括:
    所述第二网络设备解析所述FlexE开销帧,得到所述同步模式指示以及所述同步信息。
  17. 根据权利要求12-16任一所述的方法,其特征在于,所述同步信息包括精确时间同步协议PTP信息和同步状态信息SSM中的一种或多种;
    所述第二网络设备根据所述同步信息进行同步,包括:
    若所述同步信息包括所述PTP信息,所述第二网络设备根据所述PTP信息选择时间同步源,所述第二网络设备根据所述时间同步源进行时间同步;
    若所述同步信息包括所述同步状态信息,所述第二网络设备根据所述同步状态信息选择频率同步源,所述第二网络设备根据所述频率同步源进行频率同步。
  18. 根据权利要求12-17任一所述的方法,其特征在于,所述支持灵活以太FlexE的第二网络设备包括:支持FlexE的客户边缘设备或支持FlexE的网络的节点设备,所述支持FlexE的网络包括分片分组网络SPN、城域传送网络MTN或光传送网络OTN中的任一种。
  19. 一种网络同步的装置,其特征在于,所述装置应用于支持灵活以太FlexE的第一网络设备,所述装置包括:
    获取模块,用于获取同步模式指示以及同步信息,所述同步模式指示用于指示目标网络设备根据所述同步信息进行同步;
    发送模块,用于通过支持FlexE的网络发送所述同步模式指示以及所述同步信息。
  20. 根据权利要求19所述的装置,其特征在于,所述发送模块,用于通过支持FlexE的网络发送FlexE开销帧,所述FlexE开销帧包括所述同步模式指示以及所述同步信息。
  21. 根据权利要求19或20所述的装置,其特征在于,所述同步模式指示包括第一模式指示,所述第一模式指示用于指示目标网络设备进入FlexE同步模式。
  22. 根据权利要求19-21任一所述的装置,其特征在于,所述获取模块,还用于获取目标网络设备指示信息,所述目标网络设备指示信息用于指示FlexE段的另一端设备或FlexE路径的另一端设备为目标网络设备。
  23. 根据权利要求22所述的装置,其特征在于,所述同步模式指示包括所述目标网络设备指示信息。
  24. 根据权利要求20所述的装置,其特征在于,所述FlexE开销帧包括至少一个同步模式指示字段,所述至少一个同步模式指示字段包括所述同步模式指示;
    所述FlexE开销帧包括第六FlexE开销块,所述第六FlexE开销块包括所述同步信息。
  25. 根据权利要求24所述的装置,其特征在于,所述至少一个同步模式指示字段中的第一同步模式指示字段包括一个或多个比特位,所述一个或多个比特位包括所述同步模式指示;
    或者,所述至少一个同步模式指示字段包括第二同步模式指示字段,所述第二同步模式 指示字段包括至少一个比特位,所述至少一个比特位包括所述同步模式指示的至少一部分。
  26. 根据权利要求24或25所述的装置,其特征在于,所述装置还包括:
    封装模块,用于将所述同步信息封装为以太帧,所述第六FlexE开销块包括所述以太帧。
  27. 根据权利要求26所述的装置,其特征在于,所述封装模块,还用于将所述以太帧切分为N个码块1,2,…,N-1,N,将所述N个码块中的第1至i个码块连续插入到第一FlexE开销帧的第六FlexE开销块的比特位字段,N为大于等于2的正整数,i为大于等于1的正整数且i小于N;
    将所述N个码块中的第i+1至j个码块连续插入第二FlexE开销帧的第六FlexE开销块的比特位字段,所述第二FlexE开销帧为邻接所述第一FlexE开销帧的下一个FlexE开销帧,j为正整数且i+1≤j≤N。
  28. 根据权利要求19-27任一所述的装置,其特征在于,所述同步信息包括精确时间同步协议PTP信息和同步状态信息SSM中的一种或多种,所述PTP信息用于指示目标网络设备进行时间同步,所述同步状态信息用于指示所述目标网络设备进行频率同步。
  29. 根据权利要求19-28任一所述的装置,其特征在于,所述支持灵活以太FlexE的第一网络设备包括:支持FlexE的客户边缘设备或支持FlexE的网络的节点设备,所述支持FlexE的网络包括分片分组网络SPN、城域传送网络MTN或光传送网络OTN中的任一种。
  30. 一种网络同步的装置,其特征在于,所述装置应用于支持灵活以太FlexE的第二网络设备,所述装置包括:
    接收模块,用于通过支持FlexE的网络接收同步模式指示以及同步信息,所述同步模式指示用于指示目标网络设备根据所述同步信息进行同步;
    同步模块,用于基于所述同步模式指示,根据所述同步信息进行同步。
  31. 根据权利要求30所述的装置,其特征在于,所述同步模式指示包括第一模式指示,所述第一模式指示用于指示目标网络设备进入FlexE同步模式;
    所述同步模块,用于基于所述第一模式指示,进入所述FlexE同步模式,在所述FlexE同步模式下,根据所述同步信息进行同步。
  32. 根据权利要求30或31所述的装置,其特征在于,所述接收模块,还用于接收目标网络设备指示信息,所述目标网络设备指示信息用于指示FlexE段的另一端设备或FlexE路径的另一端设备为目标网络设备。
  33. 根据权利要求32所述的装置,其特征在于,所述同步模式指示包括所述目标网络设备指示信息。
  34. 根据权利要求30-33任一所述的装置,其特征在于,所述接收模块,用于接收FlexE开销帧,所述FlexE开销帧包括所述同步模式指示以及所述同步信息;
    所述装置还包括解析模块,用于解析所述FlexE开销帧,得到所述同步模式指示以及所述同步信息。
  35. 根据权利要求30-34任一所述的装置,其特征在于,所述同步信息包括精确时间同步协议PTP信息和同步状态信息SSM中的一种或多种;
    若所述同步信息包括所述PTP信息,所述同步模块,用于根据所述PTP信息选择时间同步源,根据所述时间同步源进行时间同步;
    若所述同步信息包括所述同步状态信息,所述同步模块,用于根据所述同步状态信息选择频率同步源,根据所述频率同步源进行频率同步。
  36. 根据权利要求30-35任一所述的装置,其特征在于,所述支持灵活以太FlexE的第二网络设备包括:支持FlexE的客户边缘设备或支持FlexE的网络的节点设备,所述支持FlexE的网络包括分片分组网络SPN、城域传送网络MTN或光传送网络OTN中的任一种。
  37. 一种网络同步的设备,其特征在于,所述设备包括:处理器,所述处理器与存储器耦合,所述存储器中存储有至少一条程序指令或代码,所述至少一条程序指令或代码由所述处理器加载并执行,以使所述设备实现如权利要求1-18中任一所述的方法。
  38. 一种网络同步的系统,其特征在于,所述系统包括第一网络设备和第二网络设备,所述第一网络设备用于执行如权利要求1-11任一所述的方法,所述第二网络设备用于执行如权利要求12-18任一所述的方法。
  39. 一种计算机可读存储介质,其特征在于,所述计算机可读存储介质中存储有至少一条程序指令或代码,所述程序指令或代码由处理器加载并执行,以使计算机实现如权利要求1-18中任一所述的方法。
  40. 一种计算机程序产品,其特征在于,包括至少一条程序指令或代码,所述程序指令或代码由处理器加载并执行,以使计算机实现如权利要求1-18中任一所述的方法。
PCT/CN2021/103822 2020-11-16 2021-06-30 网络同步的方法、装置、设备、系统及可读存储介质 WO2022100110A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
EP21890641.0A EP4236121A4 (en) 2020-11-16 2021-06-30 NETWORK SYNCHRONIZATION METHOD AND APPARATUS, AND DEVICE, SYSTEM AND READABLE STORAGE MEDIUM
US18/317,697 US20230291537A1 (en) 2020-11-16 2023-05-15 Network Synchronization Method, Apparatus, Device, and System, and Readable Storage Medium

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
CN202011275848.7 2020-11-16
CN202011275848 2020-11-16
CN202110158060.6 2021-02-04
CN202110158060.6A CN114513271A (zh) 2020-11-16 2021-02-04 网络同步的方法、装置、设备、系统及可读存储介质

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US18/317,697 Continuation US20230291537A1 (en) 2020-11-16 2023-05-15 Network Synchronization Method, Apparatus, Device, and System, and Readable Storage Medium

Publications (1)

Publication Number Publication Date
WO2022100110A1 true WO2022100110A1 (zh) 2022-05-19

Family

ID=81547627

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/103822 WO2022100110A1 (zh) 2020-11-16 2021-06-30 网络同步的方法、装置、设备、系统及可读存储介质

Country Status (4)

Country Link
US (1) US20230291537A1 (zh)
EP (1) EP4236121A4 (zh)
CN (1) CN114513271A (zh)
WO (1) WO2022100110A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2024152172A1 (zh) * 2023-01-16 2024-07-25 Oppo广东移动通信有限公司 同步方法和设备

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107800528A (zh) * 2016-08-31 2018-03-13 中兴通讯股份有限公司 一种传输同步信息的方法、装置和系统
CN108880722A (zh) * 2017-05-10 2018-11-23 深圳市中兴软件有限责任公司 时钟同步的方法、系统和光传输设备
CN109428663A (zh) * 2017-08-31 2019-03-05 英飞凌科技股份有限公司 用于高速传感器接口的同步机制
CN109769223A (zh) * 2019-02-28 2019-05-17 上海电气集团股份有限公司 一种噪声信号无线同步的采集方法和数据采集系统
CN110971329A (zh) * 2018-09-28 2020-04-07 英特尔公司 用于管理内部时间同步的技术
EP3713158A1 (en) * 2015-06-30 2020-09-23 Ciena Corporation Time transfer systems and methods over a stream of ethernet blocks

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10193688B2 (en) * 2015-12-11 2019-01-29 Ciena Corporation Flexible Ethernet encryption systems and methods
US10097480B2 (en) * 2015-09-29 2018-10-09 Ciena Corporation Time transfer systems and methods over flexible ethernet
CN106341207A (zh) * 2015-07-06 2017-01-18 华为技术有限公司 一种编码块数据流的发送和接收方法、设备和系统
US10868662B2 (en) * 2018-11-30 2020-12-15 Ciena Corporation Virtualized synchronous Ethernet interfaces
CN113098645A (zh) * 2019-12-23 2021-07-09 中兴通讯股份有限公司 同步信息的配置方法、装置、网络设备和存储介质

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3713158A1 (en) * 2015-06-30 2020-09-23 Ciena Corporation Time transfer systems and methods over a stream of ethernet blocks
CN107800528A (zh) * 2016-08-31 2018-03-13 中兴通讯股份有限公司 一种传输同步信息的方法、装置和系统
CN108880722A (zh) * 2017-05-10 2018-11-23 深圳市中兴软件有限责任公司 时钟同步的方法、系统和光传输设备
CN109428663A (zh) * 2017-08-31 2019-03-05 英飞凌科技股份有限公司 用于高速传感器接口的同步机制
CN110971329A (zh) * 2018-09-28 2020-04-07 英特尔公司 用于管理内部时间同步的技术
CN109769223A (zh) * 2019-02-28 2019-05-17 上海电气集团股份有限公司 一种噪声信号无线同步的采集方法和数据采集系统

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP4236121A4

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2024152172A1 (zh) * 2023-01-16 2024-07-25 Oppo广东移动通信有限公司 同步方法和设备

Also Published As

Publication number Publication date
EP4236121A4 (en) 2024-04-10
EP4236121A1 (en) 2023-08-30
CN114513271A (zh) 2022-05-17
US20230291537A1 (en) 2023-09-14

Similar Documents

Publication Publication Date Title
US11101908B2 (en) Service data transmission method and apparatus
WO2019062227A1 (zh) 数据传输方法、传输设备和传输系统
US11412074B2 (en) Method and device for transparently transmitting service frequency
WO2019071870A1 (zh) 光网络中数据传输方法及光网络设备
WO2022052609A1 (zh) 时延补偿方法、装置、设备及计算机可读存储介质
US11438098B2 (en) Data transmission method, sending apparatus, and receiving apparatus
EP3923511A1 (en) Clock synchronization message interacting method and apparatus
US20230091501A1 (en) Port status configuration method, apparatus, and system, and storage medium
US11412508B2 (en) Data transmission method and device
WO2022027666A1 (zh) 一种时间同步方法及装置
US20230291537A1 (en) Network Synchronization Method, Apparatus, Device, and System, and Readable Storage Medium
US20220149973A1 (en) Service data transmission method and communication apparatus
WO2022217999A1 (zh) 一种dcn报文处理的方法、网络设备及系统
WO2021217520A1 (zh) 一种数据传输方法及装置
CN103731225B (zh) 一种数据传输方法和装置
WO2023165412A1 (zh) 数据处理方法、装置、设备、系统及计算机可读存储介质
CN116743677A (zh) 数据处理方法、装置、设备、系统及计算机可读存储介质
WO2024165009A1 (zh) 数据处理方法、装置、相关设备及存储介质
WO2022048482A1 (zh) 报文处理方法、装置、设备、系统及存储介质
US20240172189A1 (en) Resource Allocation Method, Apparatus, and System
CN117135500A (zh) 一种低时延多业务交叉方法、装置、设备及介质
CN115150017A (zh) 一种ptp报文回传方法和装置
CN117938292A (zh) Ptp报文处理系统、方法和电子设备
US7809022B2 (en) Mapping six (6) eight (8) mbit/s signals to a SONET frame
WO2017177447A1 (zh) 一种数据传输方法及设备

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: 21890641

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2021890641

Country of ref document: EP

Effective date: 20230523

NENP Non-entry into the national phase

Ref country code: DE