WO2023207636A1 - 一种时延补偿方法以及相关设备 - Google Patents

一种时延补偿方法以及相关设备 Download PDF

Info

Publication number
WO2023207636A1
WO2023207636A1 PCT/CN2023/088463 CN2023088463W WO2023207636A1 WO 2023207636 A1 WO2023207636 A1 WO 2023207636A1 CN 2023088463 W CN2023088463 W CN 2023088463W WO 2023207636 A1 WO2023207636 A1 WO 2023207636A1
Authority
WO
WIPO (PCT)
Prior art keywords
communication device
service
node
delay
time
Prior art date
Application number
PCT/CN2023/088463
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 华为技术有限公司
Publication of WO2023207636A1 publication Critical patent/WO2023207636A1/zh

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04J—MULTIPLEX COMMUNICATION
    • H04J3/00—Time-division multiplex systems
    • H04J3/02—Details
    • H04J3/06—Synchronising arrangements
    • H04J3/0635—Clock or time synchronisation in a network
    • H04J3/0638—Clock or time synchronisation among nodes; Internode synchronisation
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04J—MULTIPLEX COMMUNICATION
    • H04J3/00—Time-division multiplex systems
    • H04J3/02—Details
    • H04J3/06—Synchronising arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04J—MULTIPLEX COMMUNICATION
    • H04J3/00—Time-division multiplex systems
    • H04J3/16—Time-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

Definitions

  • the present application relates to the field of communication technology, and in particular, to a delay compensation method and related equipment.
  • Small-granularity technology is a finer-grained circuit switching technology based on the ITU Telecommunications Standardization Sector (ITU-T) metro transport network (MTN) standard extension. It changes the MTN hard pipe granularity from 5 gigabits per Seconds (G-bits per-second, Gpbs) are refined to 10 megabits per second (megabits per second, Mbps) to meet the fifth generation mobile communication technology+ (5th generation mobile communication technology+, 5G+) vertical industry applications and dedicated lines Differentiated business carrying requirements such as small bandwidth, high isolation, and high security in business scenarios.
  • ITU-T ITU Telecommunications Standardization Sector
  • MTN metro transport network
  • FGUs fine granularity units
  • TDM time-division multiplexing
  • the time-division multiplexing (TDM) mechanism is used in small-granule technology to cyclically transmit FGU basic frames at a fixed period.
  • the number and location of time slots contained in each frame are strictly fixed, so the transmission cycle of each time slot is also determined. sexual.
  • the FGU solution uses a multiframe method to divide time slots into 5Gbps particles at the SPN channel layer.
  • a multiframe contains 20 FGU basic frames, each FGU basic frame supports 24 time slots, and an SPN channel layer 5Gbps particle supports 480 time slots.
  • Each FGU basic frame includes overhead (OH), payload and other structures.
  • Slicing packet network (SPN) slicing channel is a transmission path between source and sink nodes in the SPN network. It is used to provide end-to-end Ethernet slice connections in the network, with low latency, transparent transmission, hard isolation, etc. feature.
  • Functions include customer data access/recovery, adding/deleting OAM information, cross-connection of data flows, and channel monitoring and protection.
  • the source node to the sink node is called the first direction
  • the sink node to the source node is called the second direction.
  • the processing flow of the service bit stream in the first direction and the processing of the service bit stream in the second direction are The processes are independent of each other. Since the processing delay of each node in the SPN network may be different, the delay of the service bit streams in the two directions may not be consistent.
  • the embodiment of this application proposes a delay compensation method, including:
  • the first communication device determines a first transmission delay, the first transmission delay indicates the transmission delay of small-granularity services in the first communication device;
  • the first communication device sends the first transmission delay to the second communication device.
  • the first communication device is used at the source node. After the first communication device receives the first service bit stream, the first communication device processes the first service bit stream. First, the first communication device performs slicing processing on the first service bit stream to obtain a service slice corresponding to the first service bit stream.
  • the service slice is also called a service slice corresponding to the first small-granule service.
  • the first communication device encapsulates the service slice to obtain a service container. Specifically, one or more of the following information is added based on the service slice: extended sequence number (Expand Sequence, ESQ), frequency synchronization message (such as timestamp), payload length, padding or check field .
  • the ESQ sequence number is used for lossless protection or loss detection of the service slice;
  • the frequency synchronization message is used to transmit service-related clock information; when the length of the service slice is less than the payload length of the low-order time slot, the payload length or padding needs to be encapsulated , the payload length or padding is used to identify the effective payload length;
  • the check field is used to perform error checking on the service slice.
  • the first communication device After adding overhead to the service slice, the first communication device further encapsulates the service slice with the added overhead to obtain a service container. Specifically, frame boundaries and frame interval encapsulation are added to the service slice that adds overhead to obtain a service container.
  • the first communication device converts the service container into a 64B/66B code block stream, in other words, maps the service container to the corresponding I code block, S code block, T code block and D code block.
  • the first communication device inserts an operation, administration and maintenance (OAM) code block into the above code block stream.
  • OAM operation, administration and maintenance
  • the first communication device maps the code block stream inserted into the OAM code block to the egress time slot position of the first communication device.
  • the data mapped to the egress time slot position of the code block stream is called FGU time slot data.
  • the first communication device sends the FGU time slot data at the egress time slot position through the Ethernet interface or the flexible Ethernet client (FlexE Client) interface.
  • the first communication device determines the transmission delay of the small-granularity service in the first communication device.
  • the transmission delay of the small-granularity service in the first communication device is called the first communication device.
  • a transmission delay is a transmission delay.
  • the end-to-end delay compensation value is calculated by collecting the transmission delay of small and medium-sized services in each node, and then calculating it based on the end-to-end target delay.
  • the business slices corresponding to the small-granularity services are cached.
  • the sink node extracts the service slice from the cache, reassembles it to obtain the service bit stream, and then sends the service bit stream.
  • end-to-end delay compensation is achieved to ensure that the service bit stream sent by the sink node meets the delay compensation requirements, thereby ensuring that the network transmission delay from the source node to the sink node in the small-granularity service network is the same as the sink node to the source node.
  • the network transmission delay is equal to or meets the expected error range, or the network transmission delay from the source node to the sink node and the network transmission delay from the sink node to the source node are adjusted to the expected value to meet business requirements.
  • the delay compensation method proposed in the embodiment of the present application it can ensure that the information collection time between any two terminal devices is consistent, thereby improving the accuracy of the power system's execution of relay protection services.
  • Terminal equipment in the power grid system includes but is not limited to: relay protection devices, power management units, data transmission units, electricity meters, switches, power generation devices, or transformer devices, etc.
  • the information collected by each terminal device in the power grid system includes but is not limited to: voltage, current or voltage frequency, etc.
  • the first communication device determines the transmission delay of the small-granularity service in the first communication device, including:
  • Node delay is the transmission delay of the small particle service in the first communication device
  • T1 is the first time
  • the first time is the time when the first communication device receives the small particle service
  • T2 is the second time
  • the second time is the time when the first communication device sends the small particle service.
  • T1 is the first time
  • the first time is the time when the first communication device receives the small particle service.
  • T1 is the time when the first communication device receives specific bits in the service bit stream carrying the small-granularity service. For example: select the first bit in the service bit stream as a specific bit. When the first communication device receives the first bit of the service bit stream, the first communication device records the reception of the first bit. time. The reception time of the first bit is regarded as T1.
  • the specific bit can be selected according to the actual situation. For example, the specific bit can be the 1st bit, the 100th bit, the 200th bit, the 500th bit, and/or the 1000th bit of the service bit stream, etc. .
  • the first communication device periodically records the reception time according to the number of bits of the received service bit stream, and the reception time is regarded as T1. For example: every time the first communication device receives 1000 bits, it records a reception time (such as the reception time of the 1001st bit), and the reception time is regarded as T1.
  • each one or more bits record a reception moment. Then the receiving time is periodically selected as T1. For example: every time the first communication device receives 1 bit, it records the reception time. The first communication device determines one time as T1 every 1000 reception times.
  • T1 is the time when the first communication device receives the FGU time slot data at the entry time slot position.
  • T1 is the time when the first communication device receives the first FGU time slot data.
  • the first communication device can also select the reception time of other FGU time slot data as T1.
  • T1 is the time when the first communication device receives the 10th FGU time slot data of the small particle service, or T1 is The time when the first communication device receives the 50th FGU time slot data of the small particle service, or T1 is the time when the first communication device receives the 100th FGU time slot data of the small particle service, which is not limited here.
  • the first communication device periodically records the reception time according to the number of time slots of the received FGU time slot data, and the reception time is regarded as T1. For example: every time the first communication device receives 1000 FGU time slot data, it records a reception time (such as the reception time of the 1001st FGU time slot data), and the reception time is regarded as T1.
  • the second moment is the moment when the first communication device sends the small particle unit FGU time slot data
  • the FGU time slot data carries the service bits of the small particle service. The specific bits in the stream.
  • T2 is the second moment.
  • T2 is the time when the first communication device sends FGU time slot data at the egress time slot position.
  • T2 is the time when the first communication device sends the first FGU time slot data, or T2 is the time when the first communication device sends the 50th FGU time slot data, etc., which are not limited here.
  • T2 is the time when the first communication device maps the service container including specific bits to the exit timeslot position.
  • T2 is the time when the first communication device sends FGU time slot data carrying specific bits in the service bit stream, and the service bit stream carries small-granularity services.
  • T1 is the first communication device receiving specific bits in the service bit stream.
  • T2 is the time when the first communication device sends the FGU time slot data carrying the specific bit.
  • the first communication device periodically records the sending time according to the number of FGU time slot data sent, and the sending time is regarded as T2. For example: every time the first communication device sends 1000 FGU time slot data, it records a sending time (such as the sending time of the 1001st FGU time slot data), and the sending time is regarded as T2.
  • the first communication device when the first communication device sends FGU time slot data, it records the sending time every time one or more FGU time slot data is sent. Then periodically select the sending time as T2. For example: every time the first communication device sends one FGU time slot data, it records the sending time. The first communication device determines one time as T2 every 1000 transmission time intervals.
  • T2 is the time when the first communication device sends the first egress time slot position of the small particle service.
  • the first communication device can also select the sending time of other exit time slot positions as T2.
  • T2 is the time when the first communication device sends the 10th exit time slot position of the small particle service, or T2 is The time when the first communication device sends the 50th egress time slot position of the small particle service, or T2 is the time when the first communication device sends the 100th egress time slot position of the small particle service, which is not limited here.
  • the first communication device periodically records the sending time according to the number of time slots of the sent egress time slot position (FGU time slot), and the sending time is regarded as T2. For example: every time the first communication device transmits 1000 egress slot positions (FGU time slots), it records a transmission time (such as the transmission time of the 1001st FGU time slot data), and the transmission time is regarded as T2.
  • the small-granularity service is a fixed bit rate CBR service.
  • the first communication device is used for an intermediate node, and the method further includes:
  • the first communication device receives a second transmission delay from a previous hop node, and the second transmission delay indicates a transmission delay of the small-granularity service from the source node to the previous hop node;
  • the first communication device sends the first transmission delay and the second transmission delay to the next hop node.
  • the second transmission delay includes: the transmission delay of each node through which the small-grain service is transmitted from the source node to the previous hop node;
  • the second transmission delay includes: the sum of the transmission delays of each node through which the small-grain service is transmitted from the source node to the previous hop node.
  • the first communication device sends the first transmission delay to the second communication device, including:
  • the first communication device receives a delay collection message from the previous hop node, where the delay collection message includes the second transmission delay;
  • the first communication device updates the delay collection message, and the updated delay collection message includes the first transmission delay and the second transmission delay;
  • the first communication device sends the updated delay collection message to the second communication device.
  • the first communication device collects messages through delay and sends the first transmission delay to the second communication device. After receiving the delay collection information from the previous hop node, the first communication device fills the first transmission delay measured by itself into the delay collection message. When the upstream of the first communication device also includes other nodes, the first communication device receives the The delay collection message of the hop node includes the second transmission delay. Then, the first communication device updates the delay collection message, and the updated delay collection message includes the first transmission delay and the second transmission delay. The first communication device sends the updated delay collection message to the second communication device (or other downstream node).
  • delay collection messages including but not limited to: messages, packets, new fields in packet headers, bit information (including multiple bits), or type length. Value (type length value, TLV) information, etc.
  • the delay collection message further includes: path information
  • the first communication device determines the second communication device that receives the delay collection message according to the indication of the path information.
  • the delay collection message also includes path information, and the path information indicates the transmission path of the delay collection message.
  • the path information includes forwarding information of one or more nodes.
  • the forwarding information includes but is not limited to: the port number of the previous hop node and/or the next hop node, or the media access control (Media Access Control, MAC) address of the previous hop node and/or the next hop node. , or the Internet Protocol (IP) address of the previous hop node and/or the next hop node, or the small particle channel (channel) number of the previous hop node and/or the next hop node, etc.
  • IP Internet Protocol
  • the node indicated by the path information needs to fill the first transmission delay of its own node in the delay collection message.
  • the first communication device determines the destination node (ie, the next hop node that receives the delay collection message) based on the path information. Then the first communication device sends a delay collection message to the destination node, where the delay collection message carries the first transmission delay of the first communication device. After the destination node receives the delay collection message, the destination node fills its first transmission delay into the delay collection message.
  • the destination node determines the next hop node that receives the updated delay collection message according to the instructions of the path information. Then, the destination node sends the updated delay collection message to the next hop node.
  • the first communication device that receives the delay collection message determines whether to process the delay collection message by detecting whether its own address information matches the address information included in the path information. If it matches, the first communication device fills its first transmission delay into the delay collection message; if it does not match, the first communication device directly forwards the delay collection message, or the first communication device discards the delay collection message. delay collection message, or the first communication device determines the next hop node according to the indication of the path information, and then the first communication device forwards the delay collection message to the next hop node.
  • the second communication device is used for a sink node or a network management device
  • an embodiment of the present application proposes a delay compensation method, which is used in a second communication device.
  • the method includes:
  • the second communication device obtains the first transmission delay, the first transmission delay indicates the transmission delay of the small-granularity service in the first communication device;
  • the second communication device obtains the transmission delay of the small-granule service in the sink node
  • the second communication device determines based on the end-to-end target delay, the first transmission delay of the first n hops of the first communication device, and the transmission delay of the small-grain service in the sink node. Delay compensation value.
  • the delay compensation value is used to perform delay compensation on the small-granule service in the sink node.
  • n is a positive integer.
  • the end-to-end delay compensation value is calculated by collecting the transmission delay of small and medium-sized services in each node, and then calculating it based on the end-to-end target delay.
  • the business slices corresponding to the small-granularity services are cached.
  • the sink node extracts the service slice from the cache, reassembles it to obtain the service bit stream, and then sends the service bit stream.
  • end-to-end delay compensation is achieved to ensure that the service bit stream sent by the sink node meets the delay compensation requirements, thereby ensuring that the network transmission delay from the source node to the sink node in the small-granularity service network is the same as the sink node to the source node.
  • the network transmission delay is equal to or meets the expected error range, or the network transmission delay from the source node to the sink node and the network transmission delay from the sink node to the source node are adjusted to the expected value to meet business requirements.
  • the delay compensation method proposed in the embodiment of the present application it can ensure that the information collection time between any two terminal devices is consistent, thereby improving the accuracy of the power system's execution of relay protection services.
  • Terminal equipment in the power grid system includes but is not limited to: relay protection devices, power management units, data transmission units, electricity meters, switches, power generation devices, or transformer devices, etc.
  • the information collected by each terminal device in the power grid system includes but is not limited to: voltage, current or voltage frequency, etc.
  • the end-to-end target delay is greater than or equal to the largest of the following two transmission delay values: the service transmission delay value in the first direction or the service transmission delay value in the second direction.
  • Business transmission delay value where,
  • the first direction is: from the source node to the sink node;
  • the second direction is: from the sink node to the source node.
  • the second communication device obtains the end-to-end target delay.
  • the end-to-end target delay is greater than or equal to the largest of the following two transmission delay values: the service transmission delay value in the first direction or the second direction.
  • the service transmission delay value wherein the first direction is: from the source node to the sink node; the second direction is: from the sink node to the source node.
  • the end-to-end target delay may be preconfigured in the second communication device, or may be calculated based on the actual measured transmission delay value in the first direction and the transmission delay value in the second direction, which is not limited here. For example, if the transmission delay value in the first direction is 500 milliseconds and the transmission delay value in the second direction is 450 milliseconds, the end-to-end target delay is set to 500 milliseconds.
  • the second communication device is used for the sink node, and the method further includes:
  • the second communication device performs delay compensation on the small-grain service according to the delay compensation value.
  • the second communication device uses the end-to-end target delay, the first transmission delay of the first n hops of the first communication device, and the small
  • the transmission delay of granular services in the sink node includes:
  • the second communication device calculates the delay compensation value in the following manner, including:
  • ⁇ is the delay compensation value
  • Target delay1 is the end-to-end target delay
  • the first communication device is used for the source node or the intermediate node
  • n is the number of nodes of the source node and the intermediate node
  • Node' delay is the transmission delay of the small-granularity service in the sink node.
  • the second communication device is used for the sink node
  • the second communication device obtains the transmission delay of the small-granularity service in the sink node, including:
  • Node' delay is the transmission delay of the small particle service in the sink node
  • T3 is the third moment
  • the third moment is the moment when the sink node receives the small particle unit FGU time slot data
  • the FGU time slot data carries specific bits in the service bit stream of the small-granularity service.
  • T4 is the fourth time.
  • the fourth time is the service container solution obtained by the sink node demapping the FGU time slot data. A moment of encapsulation.
  • the second communication device is used for the sink node
  • the second communication device performs delay compensation on the small particle service according to the delay compensation value, including:
  • the second communication device demaps the FGU time slot data to obtain the service container
  • the second communication device decapsulates the service container to obtain service slices
  • the second communication device stores the service slice in a memory
  • the second communication device extracts the service slice from the memory
  • the second communication device reassembles the service bit stream according to multiple service slices
  • the second communication device sends the service bit stream.
  • the second communication device demaps the FGU time slot data to obtain a service container, and the service container carries the The service bit stream of the small-granule service; then, the second communication device decapsulates the service container to obtain a service slice, and the service slice carries the small-granule service; the second communication device decapsulates the service The slice is stored in the memory; when the residence time of the service slice in the memory reaches the delay compensation value, the second communication device extracts the service slice from the memory; the second communication device The service bit stream is obtained by recombination according to multiple service slices; the second communication device sends the service bit stream.
  • the second communication device stores the obtained service slices in a memory.
  • the memory may be a memory located in the second communication device.
  • the memory may also be a memory independent of the second communication device. There is no limitation here.
  • the second communication device After the second communication device stores the service slice into the memory, the second communication device starts the timer. When the timer reaches the delay compensation value, it means that the residence time of the service slice in the memory reaches the delay compensation value.
  • the second communication device extracts service slices from the memory, and then performs service reorganization based on multiple service slices to obtain corresponding service bit streams.
  • the second communication device sends the service bit stream on the physical interface to realize delay compensation of small-grain services.
  • the second communication device is used in the network management device
  • the second communication device obtains the transmission delay of the small-granularity service in the sink node, including:
  • the second communication device receives the transmission delay of the small-grain service from the sink node in the sink node.
  • the service bit stream sent by the sink node meets the delay compensation requirements, thereby ensuring that the network transmission delay from the source node to the sink node in the small-granular service network is equal to or satisfies the network transmission delay from the sink node to the source node.
  • the expected error range may allow the network transmission delay from the source node to the sink node and the network transmission delay from the sink node to the source node to be adjusted to expected values to meet business requirements.
  • the second communication device is used in the network management device
  • the method also includes:
  • the second communication device sends the delay compensation value to the sink node.
  • the embodiment of this application proposes a delay compensation method, including:
  • the communication device determines the transmission delay of the small particle service in the communication device
  • the communication device performs delay compensation on the small particle service according to the target delay of the node and the transmission delay of the small particle service in the communication device.
  • the above method is used to ensure that the service bit stream sent by each node meets the delay compensation requirements, thereby ensuring that the network transmission delay from the source node to the sink node in the small-granularity service network is equal to the network transmission delay from the sink node to the source node.
  • the network transmission delay is equal or meets the expected error range, or the network transmission delay from the source node to the sink node and the network transmission delay from the sink node to the source node are adjusted to expected values to meet business requirements.
  • the target delay of the node includes: the target delay of the source node, the target delay of the intermediate node, and/or the target delay of the sink node.
  • the target delay of the node includes: the target delay of the source node, the target delay of the intermediate node, and/or the target delay of the sink node.
  • the target delay of the source node, the target delay of the intermediate node, and the target delay of the sink node satisfy: the sum of the target delay of the source node, the target delay of the intermediate node, and the target delay of the sink node is greater than Or equal to the largest of the following two transmission delay values: the service transmission delay value in the first direction or the service transmission delay value in the second direction, where the first direction is: from the source node to the Sink node; the second direction is: from the sink node to the source node.
  • the service transmission delay value may be: the transmission delay value of multiple communication devices carrying the service bit stream of the small-granularity service between the source node and the sink node.
  • the network management device configures a corresponding target delay for each node.
  • the target delay range of the source node can be: 0 ⁇ 100 microseconds
  • the target delay range of the intermediate node can be: 10 ⁇ 20 microseconds
  • the target delay access of the sink node can be: sink node: 100 ⁇ 500 microseconds.
  • the communication device is used for a source node
  • the communication device determines the transmission delay of the small-granularity service in the communication device, including:
  • the communication device obtains a first reception time, which is the time when the source node receives specific bits in the service bit stream carrying the small-granularity service;
  • the communication device obtains a second sending time.
  • the second sending time is the time when the source node sends the small granular unit FGU time slot data.
  • the FGU time slot data carries all the data in the service bit stream of the small granular service. Describe specific bits;
  • the communication device subtracts the first receiving time from the second sending time to obtain the transmission delay of the small-grain service in the source node.
  • the communication device Regarding the possible way for the communication device to obtain the first receiving time, it is similar to the way for the source node to obtain the first time in the aforementioned first aspect, and will not be described in detail here.
  • the communication device to obtain the second sending time it is similar to the way for the source node to obtain the first time in the aforementioned first aspect. Obtaining the second moment is similar and will not be described in detail here.
  • the communication device determines the transmission delay of the small-granularity service in the communication device, including:
  • the communication device obtains a third reception time, which is the time when the intermediate node receives the small particle unit FGU time slot data at the entrance time slot position, and the FGU time slot data carries the small particle service The specific bits in the service bit stream;
  • the communication device obtains a fourth sending time, which is the time when the intermediate node sends the FGU time slot data
  • the communication device subtracts the third receiving time from the fourth sending time to obtain the transmission delay of the small-grain service in the intermediate node.
  • the communication device when the communication device is used for an intermediate node, the communication device obtains a third reception time, and the third reception time is the time when the intermediate node receives FGU time slot data, and the FGU time slot data carries the Specific bits in the service bit stream of the small-granularity service; the communication device obtains the fourth sending time, the fourth sending time is the time when the intermediate node sends the FGU time slot data, and the service bit stream carries the small-granularity service bit stream.
  • Granular service the communication device subtracts the third receiving time from the fourth sending time to obtain the transmission delay of the small granular service in the intermediate node.
  • the communication device receives the FGU time slot data at the entrance time slot position. Then, the communication device maps the FGU time slot data received at the entry time slot position to the egress time slot position based on the indication of the time slot cross mapping table. Finally, the communication device sends the FGU slot data at the egress slot location through the physical interface.
  • the communication device To obtain the third receiving time, it is similar to the way in which the intermediate node in the first aspect obtains the first time, and will not be described in detail here.
  • the communication device obtaining the fourth sending time it is similar to the way in which the intermediate node in the first aspect obtains the first time.
  • the second moment of node acquisition is similar and will not be described in detail here.
  • the communication device determines the transmission delay of the small-granularity service in the communication device, including:
  • the communication device obtains a fifth reception time, which is the time when the sink node receives the small particle unit FGU time slot data, and the FGU time slot data carries all the service bit streams of the small particle service. Describe specific bits;
  • the communication device obtains a sixth sending time.
  • the sixth sending time is the time when the sink node decapsulates the service container.
  • the service container is obtained by demapping the FGU time slot data by the communication device, so The service container carries the specific bits in the service bit stream of the small-granularity service;
  • the communication device subtracts the fifth receiving time from the sixth sending time to obtain the transmission delay of the small particle service in the sink node.
  • the communication device to obtain the fifth receiving time it is similar to the way for the sink node to obtain the third time in the aforementioned second aspect, and will not be described in detail here.
  • the communication device to obtain the sixth sending time it is similar to the way for the intermediate node to obtain the third time in the aforementioned second aspect. Obtaining the fourth moment is similar and will not be described in detail here.
  • the communication device delays the small-granule service according to the target delay of the node and the transmission delay of the small-granule service in the communication device. Compensation includes:
  • the communication device determines a delay compensation value based on the target delay of the node and the transmission delay of the small-grain service in the communication device;
  • the communication device performs delay compensation on the small-grain service according to the delay compensation value.
  • the communication device After the communication device obtains the transmission delay of the small-granularity service in the communication device, the communication device The node's target delay and the transmission delay are used to calculate the node's delay compensation value. Then, the communication device performs delay compensation for small-granularity services in the communication device (own node) based on the delay compensation value of the node, thereby realizing delay compensation on a node-by-node basis.
  • the communication device performs delay compensation on the small-grain service according to the delay compensation value, including:
  • the communication device stores the FGU time slot data in a memory, and the FGU time slot data carries the service bit stream of the small particle service;
  • the communication device extracts the FGU time slot data from the memory;
  • the communication device sends the FGU time slot data.
  • the source node when the communication device is used for the source node, the source node performs delay compensation on the small-grain service according to the delay compensation value, including: after the source node receives the service bit stream, the source node The stream is processed and mapped to the egress time slot position, including: slicing the service bit stream to obtain multiple service slices; then encapsulating the service slices to obtain a service container; mapping the service container to the egress time slot position: specific , the source node maps the business container to the code block stream.
  • the code block stream is segmented to obtain FGU data time slots; the source node stores the FGU time slot data into the memory, and the FGU time slot data carries the service bit stream of the small-grain service; when the FGU of the source node
  • the source node extracts the FGU time slot data of the source node from the memory; the source node sends at the egress time slot position. FGU time slot data of the source node.
  • the communication device performs delay compensation on the small-grain service according to the delay compensation value, including:
  • the communication device intersects the entry time slot position of the intermediate node to the exit time slot position of the intermediate node;
  • the communication device stores the FGU time slot data received at the entry time slot position of the intermediate node into a memory
  • the communication device extracts the FGU time slot data from the memory;
  • the communication device transmits the FGU slot data in an egress slot position of the intermediate node.
  • the intermediate node performs delay compensation on the small-granularity service according to the delay compensation value, including: the intermediate node receives the FGU time slot at the entrance time slot position.
  • Data the FGU time slot data carries the service bit stream of the small granular service; the intermediate node crosses the entry time slot position of the intermediate node to the exit time slot position of the intermediate node; the intermediate node
  • the FGU time slot data is stored in the memory; when the residence time of the FGU time slot data in the memory reaches the delay compensation value, the intermediate node extracts the FGU time slot data from the memory. ;
  • the intermediate node sends the FGU time slot data at the exit time slot position of the intermediate node.
  • the communication device performs delay compensation on the small-grain service according to the delay compensation value, including:
  • the communication device demaps the FGU time slot data to obtain the service container
  • the communication device decapsulates the service container to obtain service slices
  • the communication device stores the service slice in a memory
  • the communication device extracts the service slice from the memory
  • the communication device reassembles the service bit stream according to multiple service slices
  • the communication device sends the service bit stream. Specifically, when the communication device is used for a sink node, the sink node performs delay compensation on the small-grain service according to the delay compensation value, including: the sink node decomposes the FGU time slot data.
  • the sink node decapsulates the service container to obtain a service slice, which carries the service bits of the small-granule service flow; the sink node stores the service slice into the memory; when the residence time of the service slice in the memory reaches the delay compensation value, the sink node extracts the service from the memory Slicing; the sink node reorganizes and obtains the service bit stream according to multiple service slices; the sink node sends the service bit stream.
  • the small granular service carries a fixed bit rate CBR service.
  • an embodiment of the present application proposes a communication device, which is used as a first communication device.
  • the communication device includes:
  • a transceiver module configured to perform reception and/or transmission-related operations performed by the first communication device in the first aspect
  • a processing module configured to perform other operations other than the reception and/or transmission related operations performed by the first communication device in the aforementioned first aspect.
  • the communication devices mentioned in the embodiments of the present application may be, for example, network equipment such as switches and routers, or may be part of the components on the network equipment, such as single boards or line cards on the network equipment. They may also be It is a functional module on the network device, and may also be a chip used to implement the method of the present application, which is not specifically limited in the embodiment of the present application.
  • the transceiver module used to implement the method may be, for example, an interface circuit of the chip, and the processing module may be a processing circuit with a processing function in the chip.
  • the communication devices may be directly connected through, but not limited to, Ethernet cables or optical cables.
  • the communication device includes:
  • a processing module configured to determine a first transmission delay, where the first transmission delay indicates the transmission delay of small-granularity services in the first communication device
  • a transceiver module configured to send the first transmission delay to the second communication device.
  • Node delay is the transmission delay of the small particle service in the first communication device
  • T1 is the first time
  • the first time is the time when the first communication device receives the small particle service
  • T2 is the second time
  • the second time is the time when the first communication device sends the small particle service.
  • the first time is the time when the first communication device receives specific bits in the service bit stream carrying the small-granularity service.
  • the second moment is when the first communication device sends a small particle unit FGU time slot
  • the FGU time slot data carries the specific bits in the service bit stream of the small-granularity service.
  • the small-granularity service is a fixed bit rate CBR service.
  • the transceiver module is also configured to receive a second transmission delay from a previous hop node, where the second transmission delay indicates that the small-granularity service travels from the source node to the previous hop node.
  • the transceiver module is also configured to send the first transmission delay and the second transmission delay to the next hop node.
  • the second transmission delay includes: the transmission delay of each node through which the small-grain service is transmitted from the source node to the previous hop node;
  • the second transmission delay includes: the sum of the transmission delays of each node through which the small-grain service is transmitted from the source node to the previous hop node.
  • the transceiver module is also configured to receive a delay collection message from the previous hop node, where the delay collection message includes the second transmission delay;
  • the processing module is also configured to update the delay collection message, and the updated delay collection message includes the first transmission delay and the second transmission delay;
  • the transceiver module is also configured to send the updated delay collection message to the second communication device.
  • the delay collection message also includes: path information
  • the processing module is further configured to determine the second communication device that receives the delay collection message according to the indication of the path information.
  • the second communication device is used for a sink node or network management device
  • an embodiment of the present application provides a communication device, which is used as a second communication device.
  • the communication device includes:
  • a transceiver module configured to perform reception and/or transmission-related operations performed by the second communication device in the second aspect
  • a processing module configured to perform other operations other than the reception and/or transmission related operations performed by the second communication device in the aforementioned second aspect.
  • the communication devices mentioned in the embodiments of the present application may be, for example, network equipment such as switches and routers, or may be part of the components on the network equipment, such as single boards or line cards on the network equipment. They may also be It is a functional module on the network device, and may also be a chip used to implement the method of the present application, which is not specifically limited in the embodiment of the present application.
  • the transceiver module used to implement the method may be, for example, an interface circuit of the chip, and the processing module may be a processing circuit with a processing function in the chip.
  • the communication devices may be directly connected through, but not limited to, Ethernet cables or optical cables.
  • the communication device includes: a transceiver module, configured to obtain a first transmission delay, where the first transmission delay indicates the transmission delay of small-granularity services in the first communication device;
  • the transceiver module is also used to obtain the transmission delay of the small-granule service in the sink node;
  • a processing module configured to determine the time based on the end-to-end target delay, the first transmission delay of the first communication device in the first n hops, and the transmission delay of the small-grain service in the sink node. Delay compensation value.
  • the delay compensation value is used to perform delay compensation on the small-granule service in the sink node.
  • n is a positive integer.
  • the end-to-end target delay is greater than or equal to the lowest of the following two transmission delay values: The big one:
  • the first direction is: from the source node to the sink node;
  • the second direction is: from the sink node to the source node.
  • the processing module is further configured to perform delay compensation on the small-granularity service according to the delay compensation value.
  • the processing module is also configured to calculate the delay compensation value in the following manner, including:
  • ⁇ is the delay compensation value
  • Target delay1 is the end-to-end target delay
  • the first communication device is used for the source node or the intermediate node
  • n is the number of nodes of the source node and the intermediate node
  • Node' delay is the transmission delay of the small-granularity service in the sink node.
  • Node' delay is the transmission delay of the small particle service in the sink node
  • T3 is the third moment
  • the third moment is the moment when the sink node receives the small particle unit FGU time slot data
  • the FGU time slot data carries specific bits in the service bit stream of the small-granularity service.
  • T4 is the fourth time.
  • the fourth time is the service container solution obtained by the sink node demapping the FGU time slot data. A moment of encapsulation.
  • the processing module is also used to demap the FGU time slot data to obtain the service container;
  • the processing module is also used to decapsulate the business container to obtain business slices;
  • the processing module is also used to store the business slice into memory
  • the processing module is also configured to extract the service slice from the memory when the residence time of the service slice in the memory reaches the delay compensation value;
  • the processing module is also configured to reorganize and obtain the service bit stream according to multiple service slices;
  • the transceiver module is also used to send the service bit stream.
  • the transceiver module is further configured to receive the transmission delay of the small-grain service from the sink node in the sink node.
  • the processing module is further configured to calculate the transmission delay of the small-granularity service in the sink node according to the end-to-end target delay, the first transmission delay, and the transmission delay of the small-granularity service in the sink node. , after determining the delay compensation value, the method further includes:
  • the transceiver module is also configured to send the delay compensation value to the sink node.
  • an embodiment of the present application provides a communication device, which includes:
  • a transceiver module configured to perform reception and/or transmission-related operations performed by the communication device in the third aspect
  • a processing module configured to perform other operations other than the reception and/or transmission related operations performed by the communication device in the aforementioned third aspect.
  • the communication devices mentioned in the embodiments of the present application may be, for example, network equipment such as switches and routers, or may be part of the components on the network equipment, such as single boards or line cards on the network equipment. They may also be It is a functional module on the network device, and may also be a chip used to implement the method of the present application, which is not specifically limited in the embodiment of the present application.
  • the transceiver module used to implement the method may be, for example, an interface circuit of the chip, and the processing module may be a processing circuit with a processing function in the chip.
  • the communication devices may be directly connected through, but not limited to, Ethernet cables or optical cables.
  • the communication device includes: a processing module configured to determine the transmission delay of small-grain services in the communication device;
  • the processing module is also configured to perform delay compensation on the small-granule service according to the target delay of the node and the transmission delay of the small-granule service in the communication device.
  • the target delay of the node includes: the target delay of the source node, the target delay of the intermediate node, and/or the target delay of the sink node.
  • the transceiver module is configured to obtain a first reception time, which is the time when the source node receives specific bits in the service bit stream carrying the small-granularity service;
  • the transceiver module is also used to obtain a second sending time.
  • the second sending time is the time when the source node sends the small particle unit FGU time slot data.
  • the FGU time slot data carries the service of the small particle service. The specific bits described in the bitstream;
  • the processing module is further configured to subtract the first receiving time from the second sending time to obtain the transmission delay of the small-grain service in the source node.
  • the transceiver module is used to obtain a third reception time.
  • the third reception time is the time when the intermediate node receives the small particle unit FGU time slot data at the entrance time slot position.
  • the FGU The time slot data carries the specific bits in the service bit stream of the small-granularity service;
  • the transceiver module is also used to obtain the fourth sending time, which is the time when the intermediate node sends the FGU time slot data;
  • the processing module is further configured to subtract the third receiving time from the fourth sending time to obtain the transmission delay of the small-grain service in the intermediate node.
  • the transceiver module is configured to obtain the fifth reception time, which is the time when the sink node receives the small particle unit FGU time slot data, and the FGU time slot data carries the The specific bits in the service bit stream of the small-grain service;
  • the transceiver module is also used to obtain the sixth sending time.
  • the sixth sending time is the time when the sink node decapsulates the service container.
  • the service container is the communication device decoding the FGU time slot data. Mapping results in that the service container carries the specific bits in the service bit stream of the small-granularity service;
  • the processing module is further configured to subtract the fifth receiving time from the sixth sending time to obtain the transmission delay of the small-grain service in the sink node.
  • the processing module is also configured to determine a delay compensation value based on the target delay of the node and the transmission delay of the small-grain service in the communication device;
  • the processing module is also configured to perform delay compensation on the small-grain service according to the delay compensation value.
  • the processing module is further configured to store the FGU time slot data in the memory, where the FGU time slot data carries the service bit stream of the small-granularity service;
  • the transceiver module is also configured to extract the FGU time slot data from the memory when the residence time of the FGU time slot data in the memory reaches the delay compensation value;
  • the transceiver module is also used to send the FGU time slot data.
  • the processing module is further configured to cross the entry time slot position of the intermediate node to the exit time slot position of the intermediate node;
  • the processing module is also configured to store the FGU time slot data received at the entry time slot position of the intermediate node into a memory;
  • the processing module is also configured to extract the FGU time slot data from the memory when the residence time of the FGU time slot data in the memory reaches the delay compensation value;
  • the transceiver module is also configured to send the FGU time slot data in the egress time slot position of the intermediate node.
  • the processing module is also used to demap the FGU time slot data to obtain the service container;
  • the processing module is also used to decapsulate the business container to obtain business slices;
  • the processing module is also used to store the business slice into memory
  • the processing module is also configured to extract the service slice from the memory when the residence time of the service slice in the memory reaches the delay compensation value;
  • the processing module is also configured to reorganize and obtain the service bit stream according to multiple service slices;
  • the transceiver module is also used to send the service bit stream.
  • the small-granularity service carries a fixed bit rate CBR service.
  • an embodiment of the present application provides a network device, which is used for a first communication device.
  • the network device includes:
  • a processor configured to determine a first transmission delay, where the first transmission delay indicates the transmission delay of small-granularity services in the first communication device
  • a transceiver configured to send the first transmission delay to the second communication device.
  • Node delay is the transmission delay of the small particle service in the first communication device
  • T1 is the first time
  • the first time is the time when the first communication device receives the small particle service
  • T2 is the second time
  • the second time is the time when the first communication device sends the small particle service.
  • the first time is the time when the first communication device receives specific bits in the service bit stream carrying the small-granularity service.
  • the second moment is the moment when the first communication device sends the small particle unit FGU time slot data
  • the FGU time slot data carries the service bit stream of the small particle service. specific bits.
  • the small-granularity service is a fixed bit rate CBR service.
  • the transceiver is further configured to receive a second transmission delay from a previous hop node, where the second transmission delay indicates the transmission of the small-granularity service from the source node to the previous hop node.
  • the transceiver is also configured to send the first transmission delay and the second transmission delay to the next hop node.
  • the second transmission delay includes: the transmission delay of each node through which the small-grain service is transmitted from the source node to the previous hop node;
  • the second transmission delay includes: the sum of the transmission delays of each node through which the small-grain service is transmitted from the source node to the previous hop node.
  • the transceiver is further configured to receive a delay collection message from the previous hop node, where the delay collection message includes the second transmission delay;
  • the processor is further configured to update the delay collection message, and the updated delay collection message includes the first transmission delay and the second transmission delay;
  • the transceiver is further configured to send the updated delay collection message to the second communication device.
  • the delay collection message also includes: path information
  • the processor is further configured to determine the second communication device that receives the delay collection message according to the indication of the path information.
  • the second communication device is used for a sink node or network management device
  • an embodiment of the present application provides a network device, which is used for a second communication device.
  • the network device includes:
  • a transceiver configured to obtain a first transmission delay, where the first transmission delay indicates the transmission delay of the small-grain service in the first communication device;
  • the transceiver is also used to obtain the transmission delay of the small-granule service in the sink node;
  • a processor configured to determine the time based on the end-to-end target delay, the first transmission delay of the first communication device in the first n hops, and the transmission delay of the small-grain service in the sink node. Delay compensation value. The delay compensation value is used to perform delay compensation on the small-granule service in the sink node. n is a positive integer.
  • the end-to-end target delay is greater than or equal to the largest of the following two transmission delay values:
  • the first direction is: from the source node to the sink node;
  • the second direction is: from the sink node to the source node.
  • the processor is further configured to perform delay compensation on the small-grain service according to the delay compensation value.
  • the processor is further configured to calculate the delay compensation value in the following manner, including:
  • ⁇ is the delay compensation value
  • Target delay1 is the end-to-end target delay
  • the first communication device is used for the source node or the intermediate node
  • n is the number of nodes of the source node and the intermediate node
  • Node' delay is the transmission delay of the small-granularity service in the sink node.
  • Node' delay is the transmission delay of the small particle service in the sink node
  • T3 is the third moment
  • the third moment is the moment when the sink node receives the small particle unit FGU time slot data
  • the FGU time slot data carries specific bits in the service bit stream of the small-granularity service.
  • T4 is the fourth time.
  • the fourth time is the service container solution obtained by the sink node demapping the FGU time slot data. A moment of encapsulation.
  • the processor is also used to demap the FGU time slot data to obtain the service container;
  • the processor is also used to decapsulate the business container to obtain business slices;
  • the processor is also used to store the business slice into memory
  • the processor is also configured to extract the service slice from the memory when the residence time of the service slice in the memory reaches the delay compensation value;
  • the processor is further configured to reorganize and obtain the service bit stream according to multiple service slices;
  • the transceiver is also used to send the service bit stream.
  • the transceiver is further configured to receive the transmission delay of the small-grain service from the sink node in the sink node.
  • the processor is further configured to calculate the transmission delay of the small-granular service in the sink node according to the end-to-end target delay, the first transmission delay, and the transmission delay of the small-granularity service in the sink node. , after determining the delay compensation value, the method further includes:
  • the transceiver is also used to send the delay compensation value to the sink node.
  • an embodiment of the present application provides a network device, the network device is used for a communication device, and the network device includes:
  • a processor configured to determine the transmission delay of small particle services in the communication device
  • the processor is further configured to perform delay compensation on the small-granule service according to the target delay of the node and the transmission delay of the small-granule service in the communication device.
  • the target delay of the node includes: the target delay of the source node, the target delay of the intermediate node, and/or the target delay of the sink node.
  • the transceiver is configured to obtain a first reception time, which is the time when the source node receives specific bits in the service bit stream carrying the small-granularity service;
  • the transceiver is also used to obtain a second sending time, which is when the source node sends small particles.
  • the moment of unit FGU time slot data the FGU time slot data carries the specific bits in the service bit stream of the small granular service;
  • the processor is further configured to subtract the first receiving time from the second sending time to obtain the transmission delay of the small-grain service in the source node.
  • the transceiver is used to obtain a third reception time, which is the time when the intermediate node receives the small particle unit FGU time slot data at the entrance time slot position, and the FGU
  • the time slot data carries the specific bits in the service bit stream of the small-granularity service
  • the transceiver is also used to obtain a fourth sending time, which is the time when the intermediate node sends the FGU time slot data;
  • the processor is further configured to subtract the third receiving time from the fourth sending time to obtain the transmission delay of the small-grain service in the intermediate node.
  • the transceiver is used to obtain the fifth reception time, which is the time when the sink node receives the small particle unit FGU time slot data, and the FGU time slot data carries the The specific bits in the service bit stream of the small-grain service;
  • the transceiver is also used to obtain the sixth sending time.
  • the sixth sending time is the time when the sink node decapsulates the service container.
  • the service container is the communication device decoding the FGU time slot data. Mapping results in that the service container carries the specific bits in the service bit stream of the small-granularity service;
  • the processor is further configured to subtract the fifth receiving time from the sixth sending time to obtain the transmission delay of the small-grain service in the sink node.
  • the processor is further configured to determine a delay compensation value based on the target delay of the node and the transmission delay of the small-grain service in the communication device;
  • the processor is further configured to perform delay compensation on the small-grain service according to the delay compensation value.
  • the processor is further configured to store the FGU time slot data in a memory, where the FGU time slot data carries the service bit stream of the small-granularity service;
  • the transceiver is also configured to extract the FGU time slot data from the memory when the residence time of the FGU time slot data in the memory reaches the delay compensation value;
  • the transceiver is also used to send the FGU time slot data.
  • the processor is further configured to cross the entry time slot position of the intermediate node to the exit time slot position of the intermediate node;
  • the processor is further configured to store the FGU time slot data received at the entry time slot position of the intermediate node into a memory
  • the processor is also configured to extract the FGU time slot data from the memory when the residence time of the FGU time slot data in the memory reaches the delay compensation value;
  • the transceiver is also configured to send the FGU time slot data in the egress time slot position of the intermediate node.
  • the processor is also used to demap the FGU time slot data to obtain the service container;
  • the processor is also used to decapsulate the business container to obtain business slices;
  • the processor is also used to store the business slice into memory
  • the processor is also configured to extract the service slice from the memory when the residence time of the service slice in the memory reaches the delay compensation value;
  • the processor is further configured to reorganize and obtain the service bit stream according to multiple service slices;
  • the transceiver is also used to send the service bit stream.
  • the small-granularity service carries a fixed bit rate CBR service.
  • a communication system which includes the network device described in the fourth or fifth aspect.
  • a communication system which includes the network device described in the sixth aspect.
  • a twelfth aspect of the present application provides a computer storage medium, which may be non-volatile; computer readable instructions are stored in the computer storage medium, and when the computer readable instructions are executed by a processor, the first A method in any implementation manner of the aspect or the second aspect or the third aspect.
  • a thirteenth aspect of the present application provides a computer program product containing instructions that, when run on a computer, cause the computer to execute the method in any one implementation of the first aspect, the second aspect, or the third aspect.
  • a fourteenth aspect of the present application provides a chip system.
  • the chip system includes a processor and an interface circuit.
  • the processor and the interface circuit are used to support the communication device to implement the functions involved in the method described in any of the above aspects, such as , send or process the data and/or information involved in the above methods.
  • the chip system also includes a memory for saving necessary program instructions and data for the network device.
  • the chip system may be composed of chips, or may include chips and other discrete devices.
  • a fifteenth aspect of the present application provides a network device, the network device is used as a first communication device, the network device includes: a communication interface;
  • a processor connected to the communication interface causes the first communication device to execute the method in the first aspect based on the communication interface and the processor.
  • a sixteenth aspect of the present application provides a network device, the network device is used as a second communication device, the network device includes: a communication interface;
  • a processor connected to the communication interface causes the second communication device to execute the method in the aforementioned second aspect based on the communication interface and the processor.
  • a seventeenth aspect of the present application provides a network device, the network device is used as a communication device, and the network device includes: a communication interface;
  • a processor connected to the communication interface causes the communication device to execute the method in the third aspect based on the communication interface and the processor.
  • Figure 1 is a schematic diagram of the application scenario of small particle technology applied to smart grid
  • FIG. 2 is a schematic structural diagram of the FGU base frame
  • Figure 3a is a schematic structural diagram of the FGU multiframe
  • Figure 3b is a schematic diagram of FGU base frame overhead
  • Figure 4 is a schematic diagram of the processing flow of CRB business
  • Figure 5 is a schematic diagram of the base frame payload
  • Figure 6 is a schematic diagram of small-granularity service multiframe in an embodiment of the present application.
  • Figure 7 is a schematic diagram of a network scenario in an embodiment of the present application.
  • Figure 8 is a schematic diagram of the 1DM process
  • Figure 9 is a schematic diagram of an embodiment of the delay compensation method in the embodiment of the present application.
  • Figure 10 is a schematic diagram of an embodiment of the delay compensation method in the embodiment of the present application.
  • Figure 11 is a schematic diagram of specific bits in the service bit stream in the embodiment of the present application.
  • Figure 12 is a schematic diagram of specific bits in the service bit stream in the embodiment of the present application.
  • Figure 13 is a schematic diagram of specific bits in the service bit stream in the embodiment of the present application.
  • Figure 14 is a schematic diagram of a scenario of transmission delay in the embodiment of the present application.
  • Figure 15 is a schematic diagram of another scenario of transmission delay in the embodiment of the present application.
  • Figure 16 is a schematic diagram of an application scenario in the embodiment of the present application.
  • Figure 17 is a schematic diagram of another application scenario in the embodiment of the present application.
  • Figure 18 is a schematic diagram of measuring transmission delay in an embodiment of the present application.
  • Figure 19 is a schematic diagram of another application scenario in the embodiment of the present application.
  • Figure 20 is a schematic diagram of another embodiment of the delay compensation method in the embodiment of the present application.
  • Figure 21 is a schematic diagram of another embodiment of the delay compensation method in the embodiment of the present application.
  • Figure 22 is a schematic diagram of forwarding delay collection messages in the embodiment of the present application.
  • Figure 23 is a schematic structural diagram of a communication device 2300 provided by an embodiment of the present application.
  • Figure 24 is a schematic structural diagram of a communication device 2400 provided by an embodiment of the present application.
  • Figure 25 is a schematic structural diagram of a communication device 2500 provided by an embodiment of the present application.
  • Figure 26 is a schematic structural diagram of a communication device 2600 provided by an embodiment of the present application.
  • Figure 27 is a schematic diagram of a network system 2700 proposed in an embodiment of this application.
  • Figure 28 is a schematic diagram of a network system 2800 proposed in an embodiment of this application.
  • the naming or numbering of steps in this application does not mean that the steps in the method flow must be executed in the time/logical sequence indicated by the naming or numbering.
  • the process steps that have been named or numbered can be implemented according to the purpose to be achieved. The order of execution can be changed for technical purposes, as long as the same or similar technical effect can be achieved.
  • the division of units presented in this application is a logical division. In actual applications, there may be other divisions. For example, multiple units may be combined or integrated into another system, or some features may be ignored. , or not executed.
  • the coupling or direct coupling or communication connection between the units shown or discussed may be through some interfaces, and the indirect coupling or communication connection between units may be electrical or other similar forms. There are no restrictions in the application.
  • the units or subunits described as separate components may or may not be physically separated, may or may not be physical units, or may be distributed into multiple circuit units, and some or all of them may be selected according to actual needs. unit to achieve the purpose of this application plan.
  • FGU fine granularity units
  • SPN slicing packet network
  • Gpbs gigabits per second
  • Mbps megabits per second
  • FIG. 1 is a schematic diagram of the application scenario of small particle technology applied to smart grids.
  • Smart grid consists of many parts, which can be divided into: smart substation, smart distribution network, smart energy meter, smart interactive terminal, smart dispatch, smart home appliances, smart power-consuming buildings, smart city power grid, smart power generation system, and/ Or, new energy storage systems, etc.
  • Smart grid is the organic integration of information technology, sensor technology, automatic control technology and power grid infrastructure. It can obtain panoramic information of the power grid and timely discover and foresee possible failures. When a fault occurs, the power grid can quickly isolate the fault and achieve self-recovery, thus avoiding large-scale power outages.
  • smart grids the widespread application of flexible AC/DC transmission, grid-plant coordination, intelligent dispatch, power energy storage, distribution automation and other technologies makes grid operation control more flexible and economical, and can adapt to a large number of distributed power sources and microgrids. and access to electric vehicle charging and discharging facilities.
  • the comprehensive application of communications, information and modern management technology will greatly improve the efficiency of power equipment use, reduce power loss, and make the power grid operation more economical and efficient.
  • smart grid services have high requirements for real-time performance and security.
  • the bandwidth requirements of this type of business are generally not greater than 20Mbps, the end-to-end one-way delay is required to be less than 20 milliseconds (ms), and the reliability and security requirements are high to ensure that there will be no power supply accidents due to communication reasons. It presents typical features of small bandwidth, deterministic low latency, high reliability, High security business features.
  • Small-granularity business scenarios can include a variety of terminal devices and network devices, such as: Power Management Unit (PMU), or data transfer units (Data Transfer Unit, DTU) at all levels. Or, various types of smart meters or smart switches, etc.
  • PMU Power Management Unit
  • DTU data transfer units
  • slices can be divided into multiple types according to their uses. For example: for production services such as transmission network (Area I) and dispatching data network (Area II), small-grain hard slices are used; for integrated data networks (Area III) ) and IV area and other management services, use MTN interface grouping and slicing; for public services, use MTN interface grouping and slicing.
  • production services such as transmission network (Area I) and dispatching data network (Area II
  • Area II small-grain hard slices are used
  • Area III integrated data networks
  • IV area and other management services use MTN interface grouping and slicing
  • MTN interface grouping and slicing for public services, use MTN interface grouping and slicing.
  • small particle technology can also be applied to a variety of scenarios, including but not limited to: medical, port, railway, or dedicated line services, etc., and there are no restrictions here.
  • Fine granularity unit frame also known as fine granularity unit (FGU) frame, or FGU frame.
  • the time-division multiplexing (TDM) mechanism is used in small particle technology to cyclically send small particle unit frames at a fixed period, and the number and position of time slots contained in each frame are strictly fixed, so the transmission cycle of each time slot is also deterministic.
  • TDM time-division multiplexing
  • the small-granule service solution uses a multiframe method to divide the 5Gbps granules into time slots at the SPN channel layer, or divide the 1Gbps granules into time slots, etc.
  • the SPN channel layer is located in the physical coding sublayer (PCS) layer of IEEE 802.3 and adopts the PCS64/66B encoding format of IEEE 802.3.
  • the small-grain unit frame uses the same 64/66B encoding format as the SPN channel layer.
  • the overhead and payload containing multiple time slots are encoded and encapsulated into a fixed-length S block + D block + T block sequence.
  • small-grain unit frames include FGU basic unit frames (also known as FGU basic frames, FGU base frames, base frames or single frames).
  • the FGU base frame has a fixed length and includes 1 start code block (S0), 195 data code block (D) and 1 end code block (T7), a total of 197 66B code blocks (66B blocks).
  • the 195 data code blocks and 1 end (T7) code block of the FGU single frame provide 1567 (195 ⁇ 8+7) bytes of data content, including 7 bytes of overhead and 1560 bytes of payload.
  • the payload is divided into 24 sub-slots of the same size.
  • the 66B code blocks from the service are compressed from 66B to 65B and then filled into the Sub-Slot payload.
  • Each sub-slot is 65 bytes and can carry eight 65-bit code blocks.
  • Figure 2 is a schematic structural diagram of the FGU base frame.
  • Figure 3a is a schematic structural diagram of the FGU multiframe.
  • An FGU multiframe contains 20 FGU basic frames, each FGU basic frame supports 24 time slots, and an SPN channel layer 5Gbps particle supports 480 time slots.
  • Each FGU basic frame includes a base frame overhead (OH) and a base frame payload (payload).
  • the base frame overhead is also called overhead or OH.
  • the FGU basic frame may also include other contents, which is not limited in the embodiments of the present application.
  • FIG. 3b is a schematic diagram of the FGU base frame overhead.
  • Overhead includes: multiframe indication (MFI), identification (Flag) field, reserved (RES) field and overhead information area. details as follows:
  • Multiframe indicator (multiframe indicator, MFI)
  • MFI length is 6 bits, used to indicate the number of each base frame in the FGU multiframe.
  • the value of MFI is 0.
  • the value of MFI is increased by 1 in sequence.
  • the flag field is used to indicate the purpose of the bit position after the CA field in the overhead. This Flag field is also called the overhead channel usage indication field.
  • the overhead information area includes: timeslot increase adjustment notification (S field), timeslot validity indication (C field), change answer (CA) field (CA field is also called timeslot adjustment response field), change request ( change request (CR) field (CR field is also called slot adjustment request field), general communication channel (GCC), client ID (client ID), slot ID (sub-slot ID) and cyclic redundancy Cyclic redundancy check (CRC).
  • the following takes the small-granularity service as a constant bit rate (CBR) service as an example to explain how the node processes the service bitstream to obtain the small-granularity service multiframe after receiving the service bitstream.
  • CBR constant bit rate
  • the small particle services involved in the embodiments of the present application can also be Ethernet services and other services based on small particle technology transmission, and the embodiments of the present application do not limit this.
  • FIG 4 is a schematic diagram of the processing flow of the CRB service.
  • the processing flow of CBR business includes:
  • the node receives the service bit stream, and the service bit stream carries the CBR service.
  • the service bit stream includes j CBR service frames, where j is a positive integer greater than 1.
  • the node slices the service data to obtain corresponding service slices.
  • Specific slicing solutions include: bit-transparent slicing mode, which does not identify the specific content of the service frame, but slices it according to a fixed number of bits. For example, each i bit slice obtains a service slice, where i is a positive integer greater than 1;
  • the frame slicing model identifies the specific frame format and then slices it according to a fixed number of frames. For example, every j frame slices obtain a business slice, where j is a positive integer greater than 1.
  • step S2 after the node slices the service bit stream to obtain the corresponding service slice, it encapsulates the service slice to obtain the corresponding service container. Specifically, overhead is added to the service slice, and the length of the resulting service slice after the overhead is added is the same as the length of the low-order slot payload, for example, both are Y bits, and Y is a positive integer greater than 1.
  • the specific encapsulation process is as follows: add one or more of the following information based on the service slice: extended sequence number (Expand Sequence, ESQ), frequency synchronization message (such as timestamp), payload length, padding or calibration validation field.
  • the ESQ sequence number is used for lossless protection or loss detection of the service slice; the frequency synchronization message is used to transmit service-related clock information; when the length of the service slice is less than the payload length of the low-order time slot, the payload length or padding needs to be encapsulated , the payload length or padding is used to identify the effective payload length; the check field is used to perform error checking on the service slice.
  • the node After the node adds overhead to the business slice, it further encapsulates the business slice with added overhead to obtain a business container. Specifically, frame boundaries and frame interval encapsulation are added to the service slice that adds overhead to obtain a service container.
  • the node converts the service container into a 64B/66B code block stream, in other words, maps the service container to the corresponding I code block, S code block, T code block and D code block.
  • step S3 the node inserts the OAM code block into the code block stream.
  • the OAM code block is also called an OAM message in the embodiment of this application.
  • Step S4 is an optional step.
  • the 64B/66B code block inserted into the OAM code block The stream is transcoded and compressed.
  • the specific transcoding algorithm may be a 64B/65B transcoding algorithm or a 256B/257B transcoding algorithm, which is not limited in the embodiments of this application.
  • step S5 the node performs slicing processing on the transcoded data stream according to a certain bit length, for example: slicing according to the payload length of each time slot (Y bits, Y is a positive integer greater than 1).
  • the net length of each time slot is The payload length is equal to the length of the low-order slot payload.
  • the payload length of each time slot can be Z code blocks, and the code block can be a 64B/66B code block, a transcoded 64B/65B code block, or a 256B/257B code block. The embodiments of the present application do not limit this.
  • FIG. 5 is a schematic diagram of the base frame payload.
  • the encapsulation process of the small-granule service base frame (the small-granule service base frame is referred to as the base frame in the embodiment of this application) is as follows: the FGU base frame uses S code blocks (also known as /S/ code blocks), D code blocks (also known as /S/ code blocks), and D code blocks (also known as /S/ code blocks). (called /D/ code block) and T code block (also called /T/ code block) encapsulation.
  • the data fields in the code block stream together form the payload field segment of the base frame.
  • the data fields in the S code block serve as optional field segments
  • the T code block can be a total of seven code blocks from T 0 to T 7. any of them.
  • the base frame payload field segment is used to load (M/X) low-order slot payloads and low-order slot overhead (overhead, OH).
  • M/X low-order slot payload fields load different low-order channel (sub-Client) data according to the slot table, M is a positive integer greater than 1, and X is a positive integer greater than 1; low-order slot overhead
  • the fields include base frame sequence number, low-order channel time slot allocation table, management message channel (management message channel is optional), overhead verification (overhead verification is optional), etc.
  • the node After the node obtains the base frame, it sends the base frame in the form of a small-granularity service multiframe.
  • the small-granularity service multiframe is mapped to the egress timeslot position and then sent out.
  • FIG. 6 is a schematic diagram of a small-granularity service multiframe in an embodiment of the present application.
  • the node divides M low-order time slots into loops within the Flexible Ethernet (FlexE) client interface or ordinary Ethernet (ETH) port with a bandwidth of N*5 (Gigabits per second, Gbps). Transmission, each cycle is defined as a multiframe, and the multiframe is further divided into X fixed-length base frames, where N is a positive integer greater than 1.
  • (M/X) low-order time slots are loaded in the payload of each base frame.
  • the base frame is encapsulated using S code blocks, T code blocks, and I code blocks (i.e., idle code blocks) to determine the boundaries of each base frame.
  • Each base frame header carries part of the low-level overhead, and X base frame overheads form a multiframe overhead, which is used to transmit low-channel time slot configuration and management messages.
  • the small granular service network includes edge node 1, edge node 2 and intermediate nodes.
  • edge node 1 is regarded as the source node
  • edge node 2 is regarded as the sink node
  • the intermediate nodes include Q nodes, and Q is greater than 1 integer.
  • There is a bidirectional service flow between the source node and the sink node (the bidirectional service flow is also called a service bit stream), and this service flow carries small-granularity services.
  • the direction of the service flow from the source node to the sink node is called the first direction, and the first direction may also be called the forward direction; the direction of the service flow from the sink node to the source node is called the second direction. , this second direction can also be called the backward direction.
  • the above-mentioned nodes can also be called network devices, which include but are not limited to switches, routers, or packet transport network (PTN) devices.
  • the delay measurement currently supported by the FGU network includes: one-way delay measurement (One-way Delay Measurement, 1DM) and two-way delay measurement (Two-way Delay Measurement, 2DM), which are explained below:
  • Figure 8 is a schematic diagram of the 1DM process.
  • the source node After receiving the service bit stream carrying the small-granularity service, the source node performs slicing processing on the service bit stream to obtain corresponding service slices. Then, the business slice is encapsulated to obtain the corresponding business container, and converted into a code block stream. The source node determines the idle code blocks between the code block streams corresponding to the two adjacent service slices, and then replaces the idle code blocks with 1DM code blocks. This process is also called inserting 1DM code blocks (or called : Insert 1DM message, 1DM message includes one or more 1DM code blocks). At this time, the source node records the time when the 1DM code block is inserted as H1.
  • H1 is used as the time when the 1DM code block is sent (specifically, it can be the time when the first block in the 1DM message is sent), and H1 is written into the timestamp field of the 1DM message. Then, the source node maps the code block stream including the 1DM code block to the egress time slot position. Since the data sent in the egress time slot position carries small-granularity services, the time slot sent in the egress time slot position is also called FGU time slot data. Finally, the source node sends the FGU time slot data through the Ethernet interface or flexible Ethernet client (FlexE Client) interface.
  • Ethernet interface or flexible Ethernet client (FlexE Client) interface.
  • the resource granularity of the FGU time slot data in the embodiment of the present application may be: time slot, sub-slot, frame, subframe, or multiframe, etc. This embodiment of the present application does not limit this.
  • the resource granularity of FGU time slot data is a sub-slot as an example.
  • the intermediate node After the intermediate node receives the FGU time slot data at the entry time slot position, the intermediate node sends the FGU time slot data at the exit time slot position.
  • the mapping relationship between the ingress slot position and the egress slot position is indicated by the slot cross configuration table.
  • the FGU time slot data from the intermediate node is received at the entrance time slot position through the Ethernet interface or the flexible Ethernet client (FlexE Client) interface.
  • the sink node demaps the FGU time slot data to obtain the corresponding code block stream, and then obtains the corresponding one or more service containers.
  • the sink node records the time H3 when the 1DM code block is extracted from the code block stream, and H3 is used as the time when the 1DM code block is received (specifically, it may be the time when the first block in the 1DM message is received). Then, the sink node further decapsulates the service container to obtain the corresponding service slice.
  • the sink node After the sink node extracts the time H1 for sending the 1DM code block from the 1DM code block, the sink node calculates the one-way delay based on H1 and H3. The sink node calculates the one-way delay. Specifically: multiple business slices are reorganized to obtain a business bit stream. Finally, the sink node sends the service bit stream.
  • the applicant's research found that in the SPN slicing channel, there is a bidirectional service flow between the source node and the sink node.
  • the source node to the sink node is called the first direction
  • the sink node to the source node is called the second direction.
  • the processing flow of the service bit stream in the first direction and the processing of the service bit stream in the second direction are The processes are independent of each other. Since the processing delay of each node in the SPN network may be different, the delay of the service bit streams in the two directions may not be consistent.
  • an embodiment of the present application proposes a delay compensation method, which includes: a communication device determines the transmission delay of small-granularity services in the communication device; The transmission delay in the communication device is used to compensate for the delay of the small-grain service.
  • the communication device realizes delay compensation for small-grain services and ensures that the delay of the service bit stream in the first direction is consistent with the delay of the service bit stream in the second direction.
  • the small-granule service in the embodiment of the present application may be a fixed bit rate (constant bit rate, CBR) service, an Ethernet frame service, or other small-granule service.
  • CBR constant bit rate
  • Ethernet frame service or other small-granule service.
  • the embodiment of the present application No restrictions.
  • the small particle service is the CBR service as an example for explanation.
  • the first communication device may be used for the source node and/or the intermediate node
  • the second communication device may be used for the sink node or the network management device.
  • FIG. 9 is a schematic diagram of a delay compensation method in an embodiment of the present application.
  • a delay compensation method proposed in the embodiment of this application includes:
  • the first communication device determines the transmission delay of the small-granularity service in the first communication device.
  • the processing flow of the service bit stream by the first communication device is first introduced.
  • the service carried by the service bit stream is a small-granularity service. The details are as follows:
  • the first communication device is used for the source node. After the first communication device receives the first service bit stream, the first communication device processes the first service bit stream.
  • the specific processing flow is similar to the scenarios illustrated in Figures 4 to 5.
  • the first communication device performs slicing processing on the first service bit stream to obtain a service slice corresponding to the first service bit stream.
  • the service slice is also called a service slice corresponding to the first small-granule service.
  • the first communication device encapsulates the service slice to obtain a service container. Specifically, one or more of the following information is added based on the service slice: extended sequence number (Expand Sequence, ESQ), frequency synchronization message (such as timestamp), payload length, padding or check field .
  • the ESQ sequence number is used for lossless protection or loss detection of the service slice;
  • the frequency synchronization message is used to transmit service-related clock information; when the length of the service slice is less than the payload length of the low-order time slot, the payload length or padding needs to be encapsulated , the payload length or padding is used to identify the effective payload length;
  • the check field is used to perform error checking on the service slice.
  • the first communication device After adding overhead to the service slice, the first communication device further encapsulates the service slice with the added overhead to obtain a service container. Specifically, frame boundaries and frame interval encapsulation are added to the service slice that adds overhead to obtain a service container.
  • the first communication device converts the service container into a 64B/66B code block stream, in other words, maps the service container to the corresponding I code block, S code block, T code block and D code block.
  • the first communication device inserts an operation, administration and maintenance (OAM) code block into the above code block stream.
  • OAM operation, administration and maintenance
  • the first communication device maps the code block stream inserted into the OAM code block to the egress time slot position of the first communication device.
  • the data mapped to the egress time slot position of the code block stream is called FGU time slot data.
  • the first communication device sends the FGU time slot data at the egress time slot position through the Ethernet interface or the flexible Ethernet client (FlexE Client) interface.
  • the first communication device determines the transmission delay of the small-granularity service in the first communication device.
  • the transmission delay of the small-granularity service in the first communication device is called the first communication device.
  • Node delay is the transmission delay of the small-granularity service in the first communication device (i.e., the first transmission delay)
  • T1 is the first time
  • the first time is when the first communication device receives The time of the small particle service
  • T2 is the second time
  • the second time is the time when the first communication device sends the small particle service.
  • T1 is the time when the first communication device receives specific bits in the service bit stream carrying the small-granularity service. For example: select the first bit in the service bit stream as a specific bit. When the first communication device receives the first bit of the service bit stream, the first communication device records the reception of the first bit. time. The reception time of the first bit is regarded as T1.
  • the specific bit can be selected according to the actual situation. For example, the specific bit can be the 1st bit, the 100th bit, the 200th bit, the 500th bit, and/or the 1000th bit of the service bit stream, etc. .
  • the first communication device periodically records the reception time according to the number of bits of the received service bit stream, and the reception time is regarded as T1. For example: every time the first communication device receives 1000 bits, it records a reception time (such as the reception time of the 1001st bit), and the reception time is regarded as T1.
  • each one or more bits record a reception moment. Then the receiving time is periodically selected as T1. For example: every time the first communication device receives 1 bit, it records the reception time. The first communication device determines one time as T1 every 1000 reception times.
  • T1 is the time when the first communication device receives the FGU time slot data at the entry time slot position.
  • T1 is the time when the first communication device receives the first FGU time slot data.
  • the first communication device can also select the reception time of other FGU time slot data as T1.
  • T1 is the time when the first communication device receives the 10th FGU time slot data of the small particle service, or T1 is The time when the first communication device receives the 50th FGU time slot data of the small particle service, or T1 is the time when the first communication device receives the 100th FGU time slot data of the small particle service, which is not limited here.
  • the first communication device periodically records the reception time according to the number of time slots of the received FGU time slot data, and the reception time is regarded as T1. For example: every time the first communication device receives 1000 FGU time slot data, it records a reception time (such as the reception time of the 1001st FGU time slot data), and the reception time is regarded as T1.
  • T2 is introduced, when the first communication device is used for the source node:
  • T2 is the time when the first communication device sends FGU time slot data at the egress time slot position.
  • T2 is the time when the first communication device sends the first FGU time slot data
  • T2 is the time when the first communication device sends the 50th FGU time slot data, etc., which are not limited here.
  • T2 is the time when the first communication device maps the service container including specific bits to the exit timeslot position.
  • T2 is the time when the first communication device sends FGU time slot data carrying specific bits in the service bit stream, and the service bit stream carries small-granularity services.
  • T1 is the time when the first communication device receives a specific bit in the service bit stream
  • T2 is the time when the first communication device sends the FGU time slot data carrying the specific bit.
  • the first communication device periodically records the sending time according to the number of FGU time slot data sent, and the sending time is regarded as T2. For example: every time the first communication device sends 1000 FGU time slot data, it records a sending time (such as the sending time of the 1001st FGU time slot data), and the sending time is regarded as T2.
  • the first communication device when the first communication device sends FGU time slot data, it records the sending time every time one or more FGU time slot data is sent. Then periodically select the sending time as T2. For example: every time the first communication device sends one FGU time slot data, it records the sending time. The first communication device determines one time as T2 every 1000 transmission time intervals.
  • T2 is the time when the first communication device sends the first egress time slot position of the small particle service.
  • the first communication device can also select the sending time of other exit time slot positions as T2.
  • T2 is the time when the first communication device sends the 10th exit time slot position of the small particle service, or T2 is The time when the first communication device sends the 50th egress time slot position of the small particle service, or T2 is the time when the first communication device sends the 100th egress time slot position of the small particle service, which is not limited here.
  • the first communication device periodically records the sending time according to the number of time slots of the sent egress time slot position (FGU time slot), and the sending time is regarded as T2. For example: every time the first communication device transmits 1000 egress slot positions (FGU time slots), it records a transmission time (such as the transmission time of the 1001st FGU time slot data), and the transmission time is regarded as T2.
  • the first communication device can select the associated T1 and T2 to calculate the first transmission delay, where the first transmission delay indicates the transmission delay of the small-granularity service in the first communication device.
  • T1 is the reception time of a specific bit
  • T2 is the transmission time of the FGU time slot data carrying the specific bit
  • T1 is the reception time of FGU time slot data carrying specific bits
  • T2 is the sending time of FGU time slot data carrying specific bits
  • T1 is the reception time of the 100th bit in the business bit stream
  • T2 is the sending time of the 100th bit in the business bit stream
  • T1 is the 50th receiving time
  • T2 is the 50th sending time
  • the first communication device can be used specifically for the source node or the intermediate node (the scenario illustrated in Figure 7), the following will be described separately with reference to the accompanying drawings:
  • (A) when the first communication device is used for the source node, in order to facilitate understanding of how the source node determines the transmission delay of small-granularity services in the source node, please refer to Figure 11, which illustrates the implementation of this application.
  • Figure 11 A schematic diagram of specific bits in the service bit stream in the example.
  • the service bit stream carries small-granularity services, and the first bit of the service bit stream is set to a specific bit.
  • the source node receives the first bit of the service bit stream, the source node records the reception time of the first bit, and the reception time is regarded as T1. Then, the source node processes the service bit stream (for example, Figure 4 to Figure 5) and maps it to the egress time slot position. The source node sends FGU slot data at the egress slot position through the physical interface.
  • the intermediate node After the intermediate node receives the FGU time slot data at the entry time slot position through the physical interface, the intermediate node maps the entry time slot position to the egress time slot position according to the time slot cross configuration table.
  • the slot cross configuration table indicates the mapping rules of ingress slot positions to egress slot positions in intermediate nodes.
  • the intermediate node sends the FGU slot data at the egress slot position through the physical interface.
  • the intermediate node records the time when the FGU time slot data (carrying specific bits) is received at the entry time slot position, and this time is regarded as T1.
  • the intermediate node records the time when the FGU time slot data (carrying specific bits) is sent at the egress time slot position, and this time is regarded as T2.
  • the first communication device sends the first transmission delay to the second communication device.
  • the first transmission delay indicates the transmission delay of the small-granularity service in the first communication device.
  • the first communication device after the first communication device determines the first transmission delay, the first communication device sends the first transmission delay to the second communication device, so that the second communication device obtains the first transmission delay.
  • the following is a specific solution for the first communication device to send the first transmission delay to the second communication device for different scenarios:
  • the first communication device when the first communication device is used for the source node and/or the intermediate node, and the second communication device is used for the sink node, the first communication device receives the second transmission delay from the previous hop node, the The second transmission delay indicates the transmission delay of the small-granule service from the source node to the previous hop node. Specifically, when the previous hop node is another intermediate node, the second transmission delay indicates the transmission delay of the small-grain service from the source node to the previous hop node. The first communication device sends the first transmission delay and the second transmission delay to the next hop node.
  • the transmission delay of the first communication device is divided into a first transmission delay and a second transmission delay, where the transmission delay of the own node is called the first transmission delay, The transmission delay from the previous hop node is called the second transmission delay.
  • the first communication device collects messages through delay and sends the first transmission delay to the second communication device. After receiving the delay collection information from the previous hop node, the first communication device fills the first transmission delay measured by itself into the delay collection message. When the upstream of the first communication device also includes other nodes, the first communication device receives a delay collection message from the previous hop node, and the delay collection message includes the second transmission delay. Then, the first communication device updates the delay collection message, and the updated delay collection message includes the first transmission delay and the second transmission delay. The first communication device sends the updated delay collection message to the second communication device (or other downstream node).
  • delay collection messages including but not limited to: messages, packets, new fields in packet headers, bit information (including multiple bits), or type length. Value (type length value, TLV) information, etc.
  • the delay collection message also includes path information, and the path information indicates the transmission path of the delay collection message.
  • the path information includes forwarding information of one or more nodes.
  • the forwarding information includes but is not limited to: the port number of the previous hop node and/or the next hop node, or the Media Access Control (MAC) address of the previous hop node and/or the next hop node. , or the Internet Protocol (IP) address of the previous hop node and/or the next hop node, or the small particle channel (channel) number of the previous hop node and/or the next hop node, etc.
  • IP Internet Protocol
  • the node indicated by the path information needs to fill the first transmission delay of its own node in the delay collection message.
  • the first communication device determines the destination node (ie, the next hop node that receives the delay collection message) based on the path information. Then the first communication device sends a delay collection message to the destination node, where the delay collection message carries the first transmission delay of the first communication device. After the destination node receives the delay collection message, the destination node fills its first transmission delay into the delay collection message.
  • the destination node determines the next hop node that receives the updated delay collection message according to the instructions of the path information. Then, the destination node sends the updated delay collection message to the next hop node.
  • the first communication device that receives the delay collection message determines whether to process the delay collection message by detecting whether its own address information matches the address information included in the path information. If it matches, the first communication device fills its first transmission delay into the delay collection message; if it does not match, the first communication device directly forwards the delay collection message, or the first communication device discards the delay collection message. delay collection message, or the first communication device determines the next hop node according to the indication of the path information, and then the first communication device forwards the delay collection message to the next hop node.
  • Figure 22 is a schematic diagram of delay collection message forwarding in an embodiment of the present application.
  • the scenario illustrated in Figure 22 includes: source node, intermediate node a ⁇ intermediate node g, and sink node.
  • source node source node
  • intermediate node a ⁇ intermediate node g sink node.
  • sink node Take the path information included in the delay collection message as shown in Table 1 as an example:
  • the source node After acquiring the first transmission delay of the source node, the source node fills the first transmission delay of the source node into the delay collection message. The source node then sends the delay collection message to other downstream nodes.
  • the intermediate node f since its own port number does not match the path information, the intermediate node f directly discards the received delay collection message.
  • the intermediate node c since its port number does not match the path information, the received delay collection message is directly discarded.
  • intermediate node a For intermediate node a, since its port number (AAA) matches the path information, intermediate node a updates the delay collection message.
  • the specific update method is as follows: fill the first transmission of intermediate node a in the delay collection message. time delay. Then, the intermediate node a sends the updated delay collection message to other downstream nodes.
  • the delay collection message received by the sink node includes: the first transmission delay of the source node, the first transmission delay of intermediate node a, the first transmission delay of intermediate node d and the first transmission delay of intermediate node e. First transmission delay.
  • the second transmission delay includes: the transmission delay of each node through which the small-grain service is transmitted from the source node to the previous hop node.
  • n is a positive integer greater than 2.
  • the second transmission delay sent by the intermediate node n-1 to the intermediate node n includes: the sum of the first transmission delays of the first n nodes (from the source node to the intermediate node n-2, a total of n-1 nodes).
  • the first transmission delay of intermediate node 1 is 2 milliseconds
  • the first transmission delay of intermediate node 2 is 3 milliseconds.
  • the second transmission delay received from intermediate node 1 is ⁇ 5,2 ⁇ , where "5" indicates that the transmission delay of small-granularity services at the source node is 5 milliseconds, and "2" indicates that the transmission delay of small-granularity services at intermediate node 1 is 5 milliseconds.
  • the transmission delay is 2 milliseconds.
  • the second transmission delay includes: the sum of the transmission delays of each node through which the small-grain service is transmitted from the source node to the previous hop node.
  • the first transmission delay of intermediate node 1 is 2 milliseconds
  • the first transmission delay of intermediate node 2 is 3 milliseconds.
  • the second transmission delay received by the intermediate node 3 from the intermediate node 2 is "7", where "7" indicates that the sum of the transmission delays of the small-grain service from the source node to the intermediate node 1 is 7 milliseconds, that is, the source node's
  • the sum of the first transmission delay and the first transmission delay of intermediate node 1 is 7 milliseconds.
  • Figure 14 is a schematic diagram of a scenario of transmission delay in an embodiment of the present application.
  • the scenario illustrated in Figure 14 includes a source node, P intermediate nodes, and sink nodes, where P is a positive integer greater than 3.
  • the source node After the source node obtains its own first transmission delay, it sends the first transmission delay to the next hop node (for example, intermediate node 1).
  • the intermediate node 1 After the intermediate node 1 obtains the second transmission delay from the source node (that is, the first transmission delay of the source node), the intermediate node 1 sends its own first transmission delay and the second transmission delay from the source node to the next node.
  • One-hop node for example, intermediate node 2).
  • the intermediate node 2 After the intermediate node 2 obtains the second transmission delay from the intermediate node 1 (the second transmission delay from the intermediate node 1 includes: the first transmission delay of the intermediate node 1 and the first transmission delay of the source node), the intermediate node 2. Send its own first transmission delay and the second transmission delay from intermediate node 1 to the next hop node (for example, intermediate node 3).
  • the second transmission delay sent by the intermediate node P-1 to the intermediate node P includes the first transmission delay of a total of P-1 nodes from the source node to the intermediate node P-2.
  • the intermediate node P-1 After receiving the second transmission delay from the previous hop node (intermediate node P-1), the intermediate node P-1 sends the second transmission delay and the first transmission delay of the intermediate node P-1 to the intermediate node P.
  • Figure 15 shows the transmission delay in the embodiment of the present application. Another scene diagram.
  • the scenario illustrated in Figure 15 includes a source node, n intermediate nodes, sink nodes and a network management device.
  • the network management device is connected to the source node, n intermediate nodes and sink nodes.
  • the network management device is responsible for managing and controlling each of the above nodes.
  • n is a positive integer greater than 1.
  • Each of the above nodes reports the transmission delay of the small-granularity service to the network management device.
  • the source node after the source node measures the first transmission delay, it reports the first transmission delay of the source node to the network management device. ; After the intermediate node n-1 measures and obtains the first transmission delay, it reports the first transmission delay of the intermediate node n-1 to the network management device; after the intermediate node n measures and obtains the first transmission delay, it reports the first transmission delay of the intermediate node n-1 to the network management device; The first transmission delay is reported to the network management device; after the sink node measures the transmission delay of the sink node, it reports the transmission delay of the sink node to the network management device.
  • a communication connection is established between the second communication device (network management device) and the source node, the intermediate node and the sink node based on the Network Configuration Protocol (Network Configuration Protocol, NETCONF).
  • Network Configuration Protocol Network Configuration Protocol, NETCONF
  • communication connections can also be established between the second communication device (network management device) and the source node, intermediate node and sink node based on other protocols, which is not limited here.
  • the second communication device obtains the transmission delay of the small particle service in the sink node.
  • the second communication device when the second communication device is used as a sink node, the second communication device detects and determines the transmission delay of small-granularity services in the second communication device; when the second communication device is used as a network management device, the second communication device The second communication device obtains the transmission delay of the small particle service in the sink node from the sink node.
  • Figure 13 shows the service bits in the embodiment of the present application. A diagram of specific bits in a stream.
  • the sink node receives the time slot carrying the small-granularity service at the entrance time slot position, that is, the sink node receives the FGU time slot data.
  • the sink node records the time at which the FGU time slot data including the specific bit is received. Then, the sink node processes the FGU time slot data to obtain the service bit stream (for example, Figure 4 to Figure 5).
  • the sink node When the sink node sends the service bit stream, the sink node records the time when specific bits in the service bit stream are sent. The sink node determines the transmission delay of small-granularity services at the sink node based on the time when it receives the FGU time slot data carrying specific bits and the time when it sends specific bits in the service bit stream.
  • Node' delay is the transmission delay of the small-granularity service in the sink node
  • T3 is the third time
  • the third time is the time when the sink node receives the FGU time slot data.
  • the FGU time slot The data carries specific bits in the service bit stream of the small-granularity service.
  • T4 is the fourth time.
  • the fourth time is the FGU time slot data carried by the sink node (the FGU time slot data includes specific bits).
  • the service container When the service container is decapsulated, the service container carries the specific bit.
  • T3 is the time when the sink node receives time slot data carrying small-granularity services.
  • the FGU time slot data carries data corresponding to small-granularity services.
  • T3 can also be called the time when the sink node receives the FGU time slot data.
  • T3 is, for example, the time when the sink node receives the first FGU time slot data, or T3 is the time when the sink node receives the 50th FGU time slot data, etc., which are not limited here.
  • T3 is the time when the sink node receives the FGU time slot data carrying specific bits in the service bit stream at the entrance time slot position.
  • the service bit stream carries small-granularity services.
  • T1 is the time when the sink node receives a specific bit in the service bit stream
  • T3 is the time when the sink node receives the FGU time slot data carrying the specific bit.
  • the sink node periodically records the reception time according to the number of received entry slot positions (FGU time slots), and the reception time is regarded as T3. For example: every time the sink node receives 1000 FGU time slot data, it records a reception time (such as the reception time of the 1001st FGU time slot data), and the reception time is regarded as T3.
  • the sink node when the sink node receives FGU time slot data at the entrance time slot position, it records the reception time each time it receives one or more FGU time slot data. Then the receiving time is periodically selected as T3. For example: every time the sink node receives 1 FGU time slot data, it records the reception time. The sink node determines one receiving time as T3 every 1000 receiving time intervals.
  • T4 is the time when the sink node sends specific bits in the service bit stream carrying the small-granularity service. For example: select the first bit in the service bit stream as a specific bit. When the sink node sends the first bit of the service bit stream, the sink node records the sending time of the first bit. The sending time of the first bit is as T4.
  • the specific bit can be selected according to the actual situation. For example, the specific bit can be the 1st bit, the 100th bit, the 200th bit, the 500th bit, and/or the 1000th bit of the service bit stream, etc. .
  • the sink node periodically records the sending time according to the number of bits of the sent service bit stream, and the sending time is regarded as T4. For example: every time the sink node sends 1000 bits, it records a sending time (such as the sending time of the 1001st bit), and the sending time is regarded as T4.
  • each one or more bits record the sending time. Then periodically select the sending time as T4. For example: every time the sink node sends 1 bit, the sending time is recorded. The sink node determines one time as T4 every 1000 sending times.
  • the network management device configures a path for reporting the transmission delay for the source node, the intermediate node, and the sink node, for example, the configuration is based on the NETCONF protocol. Then, the network management device obtains the transmission delay of the small-grain service in each node from the source node, intermediate node, and sink node.
  • the second communication device determines the delay compensation value based on the end-to-end target delay, the first transmission delay and the transmission delay of the small-granule service in the sink node.
  • the second communication device obtains the end-to-end target delay.
  • the end-to-end target delay is greater than or equal to the largest of the following two transmission delay values: the service transmission delay value in the first direction or the third transmission delay value.
  • the service transmission delay value in two directions wherein the first direction is: from the source node to the sink node; the second direction is: from the sink node to the source node.
  • the end-to-end target delay may be preconfigured in the second communication device, or may be calculated based on the actual measured transmission delay value in the first direction and the transmission delay value in the second direction, which is not limited here. For example, if the transmission delay value in the first direction is 500 milliseconds and the transmission delay value in the second direction is 450 milliseconds, the end-to-end target delay is set to 500 milliseconds.
  • the second communication device determines the delay compensation value based on the end-to-end target delay, the first transmission delay and the transmission delay of the small particle service in the sink node.
  • the second communication device calculates the delay compensation value in the following manner, including:
  • ⁇ is the delay compensation value
  • Target delay1 is the end-to-end target delay
  • the first communication device is used for the source node or the intermediate node
  • n is the number of nodes of the source node and the intermediate node
  • Node' delay is the transmission delay of the small-granularity service in the sink node.
  • step 905 is entered; when the second communication device (network management device) is used for the network management device, the second communication device (network management device) sends a delay compensation value to the sink node, and the sink node determines the delay compensation value according to the time.
  • the delay compensation value performs delay compensation on small-granularity services, and the specific compensation method is similar to step 905.
  • the second communication device performs delay compensation on the small-grain service according to the delay compensation value.
  • the second communication device demaps the FGU time slot data to obtain a service container.
  • the service container carries The small particles The service bit stream of the service; then, the second communication device decapsulates the service container to obtain a service slice, and the service slice carries the small-granule service; the second communication device stores the service slice to the memory; when the residence time of the service slice in the memory reaches the delay compensation value, the second communication device extracts the service slice from the memory; the second communication device extracts the service slice from the memory according to multiple The service slices are reassembled to obtain the service bit stream; the second communication device sends the service bit stream.
  • the second communication device stores the obtained service slices in a memory.
  • the memory may be a memory located in the second communication device.
  • the memory may also be a memory independent of the second communication device. There is no limitation here.
  • the second communication device After the second communication device stores the service slice into the memory, the second communication device starts the timer. When the timer reaches the delay compensation value, it means that the residence time of the service slice in the memory reaches the delay compensation value.
  • the second communication device extracts service slices from the memory, and then performs service reorganization based on multiple service slices to obtain corresponding service bit streams.
  • the second communication device sends the service bit stream on the physical interface to realize delay compensation of small-grain services.
  • the end-to-end delay compensation value is calculated by collecting the transmission delay of small and medium-sized services in each node, and then calculating it based on the end-to-end target delay.
  • the business slices corresponding to the small-granularity services are cached.
  • the sink node extracts the service slice from the cache, reassembles it to obtain the service bit stream, and then sends the service bit stream.
  • end-to-end delay compensation is achieved to ensure that the service bit stream sent by the sink node meets the delay compensation requirements, thereby ensuring that the network transmission delay from the source node to the sink node in the small-granularity service network is the same as the sink node to the source node.
  • the network transmission delay is equal to or meets the expected error range, or the network transmission delay from the source node to the sink node and the network transmission delay from the sink node to the source node are adjusted to the expected value to meet business requirements.
  • the delay compensation method proposed in the embodiment of the present application it can ensure that the information collection time between any two terminal devices is consistent, thereby improving the accuracy of the power system's execution of relay protection services.
  • Terminal equipment in the power grid system includes but is not limited to: relay protection devices, power management units, data transmission units, electricity meters, switches, power generation devices, or transformer devices, etc.
  • the information collected by each terminal device in the power grid system includes but is not limited to: voltage, current or voltage frequency, etc.
  • the source node After the source node receives the service bit stream, the source node processes the service bit stream and maps it to the egress timeslot position, including: slicing the service bit stream to obtain multiple service slices; and then encapsulating the service slices to obtain a service container. ;Map the service container to the exit slot position: Specifically, the source node maps the service container to the code block stream. Then the code block stream is segmented to obtain FGU data time slots. Finally, the source node sends FGU time slot data at the egress time slot position through the Ethernet interface or flexible Ethernet client (FlexE Client) interface. In the embodiment of this application, the time slot data carrying small-granularity services is called FGU time slot data.
  • FGU time slot data In the embodiment of this application, the time slot data carrying small-granularity services is called FGU time slot data.
  • the source node updates the generated delay collection message based on the first transmission delay of the source node. Updated delay collection messages The first transmission delay of the source node is recorded in . Then the source node sends the updated delay collection message to the next hop node (intermediate node).
  • the intermediate node After the intermediate node receives the FGU time slot data at the entry time slot position through the physical interface, the intermediate node maps the entry time slot position to the egress time slot position according to the time slot cross configuration table.
  • the slot cross configuration table indicates the mapping rules of ingress slot positions to egress slot positions in intermediate nodes. Then, the intermediate node sends the FGU slot data at the egress slot position through the physical interface.
  • the intermediate node records the first time (t3) of the intermediate node and the second time (t4) of the intermediate node, and then the intermediate node determines the first transmission delay of the intermediate node based on the first time and the second time (t4).
  • Node_delay2 t4-t3).
  • the intermediate node updates the delay collection message from the previous hop node based on the first transmission delay of the intermediate node.
  • the first transmission delay of the intermediate node is recorded in the updated delay collection message. Then the intermediate node sends the updated delay collection message to the next hop node.
  • the sink node receives the FGU slot data at the entry slot position through the physical interface. Then, the sink node demaps the FGU time slot data to obtain the corresponding service container. Further, the sink node decapsulates the service container and obtains the corresponding service slice. The sink node caches the service slices in the memory and waits for delay compensation.
  • the sink node is based on: the first transmission delay of the source node (Node_delay1), the first transmission delay of the intermediate node (Node_delay2), the transmission delay of the small-grain service at the sink node (Node_delay3), and the end-to-end target time. Delay, calculate the delay compensation value. After the residence time of the service slice in the memory of the sink node reaches the delay compensation value, the sink node extracts the service slice. Then the sink node performs service reorganization based on multiple service slices to obtain the service bit stream. Finally, the sink node sends the service bit stream on the physical interface.
  • the service bit stream sent by the sink node meets the delay compensation requirements, thereby ensuring that the network transmission delay from the source node to the sink node in the small-granular service network is equal to or satisfies the network transmission delay from the sink node to the source node.
  • the expected error range may allow the network transmission delay from the source node to the sink node and the network transmission delay from the sink node to the source node to be adjusted to expected values to meet business requirements.
  • the source node After the source node receives the service bit stream, the source node processes the service bit stream and maps it to the egress timeslot position, including: slicing the service bit stream to obtain multiple service slices; and then encapsulating the service slices to obtain a service container. ;Map the service container to the exit slot position: Specifically, the source node maps the service container to the code block stream. Then the code block stream is segmented to obtain FGU data time slots. Finally, the source node sends FGU time slot data at the egress time slot position through the Ethernet interface or flexible Ethernet client (FlexE Client) interface. In the embodiment of this application, the time slot data carrying small-granularity services is called FGU time slot data.
  • FGU time slot data In the embodiment of this application, the time slot data carrying small-granularity services is called FGU time slot data.
  • source The node uploads the first transmission delay of the source node to the network management device.
  • the intermediate node After the intermediate node receives the FGU time slot data at the entry time slot position through the physical interface, the intermediate node maps the entry time slot position to the egress time slot position according to the time slot cross configuration table.
  • the slot cross configuration table indicates the mapping rules of ingress slot positions to egress slot positions in intermediate nodes. Then, the intermediate node sends the FGU slot data at the egress slot position through the physical interface.
  • the intermediate node records the first time (t3) of the intermediate node and the second time (t4) of the intermediate node, and then the intermediate node determines the first transmission delay of the intermediate node based on the first time and the second time (t4).
  • Node_delay2 t4-t3).
  • the intermediate node uploads the first transmission delay of the intermediate node to the network management device.
  • the sink node receives the FGU slot data at the entry slot position through the physical interface. Then, the sink node demaps the FGU time slot data to obtain the corresponding service container. Further, the sink node decapsulates the service container and obtains the corresponding service slice. The sink node caches the service slices in the memory and waits for delay compensation.
  • the sink node uploads Node_delay3 to the network management device.
  • the network management device calculates the delay compensation value based on Node_delay1, Node_delay2, Node_delay3 and the end-to-end target delay. Then the sink node receives the delay compensation value, and the sink node performs delay compensation based on the delay compensation value.
  • the specific delay compensation method is similar to the method illustrated in Figure 16 and will not be described again here.
  • the sink node After the sink node generates Node_delay3, it requests the network management device to deliver Node_delay1 and Node_delay2.
  • the sink node calculates the delay compensation value based on Node_delay1, Node_delay2, Node_delay3 and the end-to-end target delay. Then the sink node performs delay compensation based on the delay compensation value.
  • the end-to-end target delay can be configured by the network management device or can be pre-configured, which is not limited here.
  • the service bit stream sent by the sink node meets the delay compensation requirements, thereby ensuring that the network transmission delay from the source node to the sink node in the small-granular service network is equal to or satisfies the network transmission delay from the sink node to the source node.
  • the expected error range may allow the network transmission delay from the source node to the sink node and the network transmission delay from the sink node to the source node to be adjusted to expected values to meet business requirements.
  • FIG. 10 is a schematic diagram of an embodiment of the delay compensation method in the embodiment of the present application.
  • a delay compensation method proposed in the embodiment of this application includes:
  • the communication device determines the transmission delay of the small-granularity service in the communication device.
  • the communication device determines the transmission delay of the small-granularity service in the communication device (that is, its own node).
  • the communication device when the communication device is used for the source node, the communication device obtains the first reception time, and the first reception time is the time when the source node receives specific bits in the service bit stream carrying the small-granularity service. ; The communication device obtains a second sending time, which is the time when the source node sends the FGU time slot data carrying the specific bit; the communication device subtracts the second sending time from the second sending time. At the first receiving moment, the transmission delay of the small-grain service in the source node is obtained.
  • the communication device To obtain the first receiving time, it is similar to the aforementioned way for the source node to obtain the first time, and will not be described in detail here.
  • the communication device to obtain the second sending time it is similar to the aforementioned way for the source node to obtain the second time. Here No further details will be given.
  • the communication device when the communication device is used for an intermediate node, the communication device obtains a third reception time, and the third reception time is the time when the intermediate node receives FGU time slot data, and the FGU time slot data carries the Specific bits in the service bit stream of the small-granularity service; the communication device obtains the fourth sending time, the fourth sending time is the time when the intermediate node sends the FGU time slot data, and the service bit stream carries the small-granularity service bit stream.
  • Granular service the communication device subtracts the third receiving time from the fourth sending time to obtain the transmission delay of the small granular service in the intermediate node.
  • the communication device receives the FGU time slot data at the entrance time slot position. Then, the communication device maps the FGU time slot data received at the entry time slot position to the egress time slot position based on the instructions of the time slot cross mapping table. Finally, the communication device sends the FGU slot data at the egress slot location through the physical interface.
  • the communication device to obtain the third receiving time it is similar to the way in which the aforementioned intermediate node obtains the first time, and will not be described in detail here.
  • the communication device to obtain the fourth sending time it is similar to the aforementioned way for the intermediate node to obtain the second time.
  • the communication device when the communication device is used for the sink node, the communication device obtains the fifth reception time, and the fifth reception time is when the sink node receives the FGU carrying specific bits in the service bit stream of the small-granularity service.
  • the time of the time slot data; the communication device obtains the sixth sending time, the sixth sending time is the time when the sink node decapsulates the service container, and the service container is the communication device for the FGU time slot Data demapping results in that the service container carries the specific bit; the communication device subtracts the fifth receiving time from the sixth sending time to obtain the transmission of the small-granularity service in the sink node. time delay.
  • the communication device demaps the FGU time slot data to obtain the service container; then, the communication device decapsulates the service container to obtain service slices. At this time, the communication device records the time when the service slice is obtained by decapsulation as the sixth sending time.
  • the communication device to obtain the fifth receiving time it is similar to the aforementioned way for the sink node to obtain the third time, and will not be described in detail here.
  • the communication device to obtain the sixth sending time it is similar to the aforementioned way for the intermediate node to obtain the fourth time.
  • No further details will be given.
  • each node obtains the transmission delay of small-granularity services at its own node.
  • the time when the small-granule service is received at the source node is called the first receiving time, and the time when the small-granule service is sent at the source node is called the second sending time;
  • the time when the small-granule service is received at the intermediate node is called is called the third receiving time, and the sending time of small-granularity services at the intermediate node is called the fourth sending time;
  • the receiving time of small-granularity services at the sink node is called the fifth receiving time, and the sending time of small-granularity services at the sink node is called The time is called the sixth sending time.
  • the communication device performs delay compensation on the small particle service based on the target delay of the node and the transmission delay of the small particle service in the communication device.
  • the communication device calculates the delay compensation value of the node based on the target delay of the node and the transmission delay. Then, the communication device performs delay compensation for small-granularity services in the communication device (own node) based on the delay compensation value of the node, thereby realizing delay compensation on a node-by-node basis.
  • the target delay of the node includes: the target delay of the source node, the target delay of the intermediate node, and/or the destination node. point target delay.
  • the target delay of the source node, the target delay of the intermediate node, and the target delay of the sink node satisfy: the sum of the target delay of the source node, the target delay of the intermediate node, and the target delay of the sink node is greater than Or equal to the largest of the following two transmission delay values: the service transmission delay value in the first direction or the service transmission delay value in the second direction, where the first direction is: from the source node to the Sink node; the second direction is: from the sink node to the source node.
  • the service transmission delay value may be: the transmission delay value of multiple communication devices carrying the service bit stream of the small-granularity service between the source node and the sink node.
  • the network management device configures a corresponding target delay for each node.
  • the target delay range of the source node can be: 0 ⁇ 100 microseconds
  • the target delay range of the intermediate node can be: 10 ⁇ 20 microseconds
  • the target delay access of the sink node can be: sink node: 100 ⁇ 500 microseconds.
  • the source node when the communication device is used for the source node, the source node performs delay compensation on the small-grain service according to the delay compensation value, including: after the source node receives the service bit stream, the source node The stream is processed and mapped to the egress time slot position, including: slicing the service bit stream to obtain multiple service slices; then encapsulating the service slices to obtain a service container; mapping the service container to the egress time slot position: specific , the source node maps the business container to the code block stream.
  • the code block stream is segmented to obtain FGU data time slots; the source node stores the FGU time slot data into the memory, and the FGU time slot data carries the service bit stream of the small-grain service; when the FGU of the source node
  • the source node extracts the FGU time slot data of the source node from the memory; the source node sends at the egress time slot position. FGU time slot data of the source node.
  • the intermediate node performs delay compensation on the small-granularity service according to the delay compensation value, including: the intermediate node receives the FGU time slot at the entrance time slot position.
  • Data the FGU time slot data carries the service bit stream of the small granular service; the intermediate node crosses the entry time slot position of the intermediate node to the exit time slot position of the intermediate node; the intermediate node
  • the FGU time slot data is stored in the memory; when the residence time of the FGU time slot data in the memory reaches the delay compensation value, the intermediate node extracts the FGU time slot data from the memory. ;
  • the intermediate node sends the FGU time slot data at the exit time slot position of the intermediate node.
  • the sink node when the communication device is used for a sink node, the sink node performs delay compensation on the small-grain service according to the delay compensation value, including: the sink node decomposes the FGU time slot data. Mapping to obtain a service container, which carries the service bit stream of the small-granule service; the sink node decapsulates the service container to obtain a service slice, which carries the service bits of the small-granule service flow; the sink node stores the service slice into the memory; when the residence time of the service slice in the memory reaches the delay compensation value, the sink node extracts the service from the memory Slicing; the sink node reorganizes and obtains the service bit stream according to multiple service slices; the sink node sends the service bit stream.
  • the above method is used to ensure that the service bit stream sent by each node meets the delay compensation requirements, thereby ensuring that the network transmission delay from the source node to the sink node in the small-granularity service network is equal to the network transmission delay from the sink node to the source node.
  • the network transmission delay is equal or meets the expected error range, or the network transmission delay from the source node to the sink node and the network transmission delay from the sink node to the source node are adjusted to expected values to meet business requirements.
  • Figure 19 is a schematic diagram of another application scenario in the embodiment of the present application.
  • the source node After the source node receives the service bit stream, the source node processes the service bit stream and maps it to the egress timeslot position, including: slicing the service bit stream to obtain multiple service slices; and then encapsulating the service slices to obtain a service container. ; Map the service container to the egress time slot position, and the data carried at the egress time slot position is FGU time slot data.
  • the source node stores the FGU time slot data of the source node in the memory, and the FGU time slot data of the source node corresponds to the service bit stream of the small-granularity service.
  • the source node When the residence time of the FGU time slot data of the source node in the memory reaches the delay compensation value of the source node, the source node extracts the FGU time slot data of the source node from the memory; The source node sends the FGU time slot data of the source node at the egress time slot position through a physical interface (such as an Ethernet interface or a flexible ethernet client (FlexE Client) interface).
  • a physical interface such as an Ethernet interface or a flexible ethernet client (FlexE Client) interface.
  • the intermediate node receives FGU time slot data at the entry time slot position.
  • the intermediate node stores the received FGU time slot data into the memory.
  • the intermediate node extracts the FGU time slot data from the memory.
  • the intermediate node maps the ingress time slot position to the egress time slot position according to the time slot cross configuration table.
  • the intermediate node sends the FGU slot data in the egress slot position through the physical interface.
  • the intermediate node receives FGU time slot data at the entry time slot position.
  • the intermediate node maps the entry time slot position to the exit time slot position according to the time slot cross configuration table.
  • the intermediate node can then store the FGU slot data into memory.
  • the intermediate node extracts the FGU time slot data from the memory.
  • the intermediate node sends the FGU slot data in the egress slot position through the physical interface.
  • the sink node After the sink node receives the FGU time slot at the entrance time slot position, the sink node demaps the FGU time slot to obtain the corresponding service container; then, the sink node decapsulates the service container to obtain the service slice; the sink node will The business slices are cached in the memory and wait for delay compensation.
  • the sink node calculates the delay compensation value of the sink node based on: the transmission delay of the small-granularity service at the sink node (Node_delay3) and the target delay of the sink node.
  • the sink node extracts the service slice. Then the sink node performs service reorganization based on multiple service slices to obtain the service bit stream. Finally, the sink node sends the service bit stream on the physical interface.
  • the slot ID of the FGU slot data (hereinafter referred to as the egress slot) in the slot position is calculated, and then the slot cross mapping table is adjusted based on the calculated slot ID of the ingress slot and the slot ID of the egress slot.
  • This enables the intermediate node to map the FGU time slot data received by the intermediate node at the entrance time slot position to the exit time slot position according to the adjusted time slot cross mapping table, thereby forwarding small particles from the previous hop node to the next hop node. business. Forwarding FGU time slot data according to the adjusted time slot cross-mapping table can ensure that the FGU time slot data forwarded by the intermediate node meets the delay compensation requirements.
  • the specific delay compensation method is as follows:
  • the intermediate node obtains the slot ID of the ingress slot based on the slot ID of the egress slot, the multiframe indication of the ingress slot, and the multiframe indication of the egress slot.
  • FIG. 20 is a schematic diagram of another embodiment of the delay compensation method in the embodiment of the present application.
  • the intermediate node performs delay compensation on the small-granule service based on the target delay of the node and the transmission delay of the small-granule service in the intermediate node, including:
  • the intermediate node obtains the timeslot identifier of the egress timeslot, the multiframe of the ingress timeslot indicates the corresponding phase, and the multiframe of the egress timeslot indicates the corresponding phase, wherein the ingress timeslot is the bearer received by the intermediate node.
  • the time slot of the small particle service, the egress time slot is the time slot for the intermediate node to send and carry the small particle service;
  • the intermediate node determines the target delay of the node, the time slot identifier of the egress time slot, the phase corresponding to the multiframe indication of the ingress time slot, the phase corresponding to the multiframe indication of the egress time slot, and the complex phase of the egress time slot.
  • the frame period and time slot interval are calculated to obtain the time slot identifier of the ingress time slot.
  • the multiframe period is the transmission delay of each multiframe in the egress time slot or the inlet time slot.
  • the time slot The interval is the transmission delay of each time slot in the egress time slot or the ingress time slot. For example, taking the 5G FlexE client interface as an example, the multiframe period is 50.688 microseconds (us), and the time slot interval is 50.688/480 ⁇ 0.1056 microseconds;
  • the intermediate node forwards the small-granule service from the previous hop node to the next hop node according to the time slot identifier of the ingress time slot and the time slot identifier of the egress time slot. Specifically, the intermediate node updates the entry time slot table according to the calculated time slot identification of the entry time slot. The subsequent intermediate node receives the FGU time slot from the previous hop node on the entry time slot according to the updated entry time slot table. The intermediate node can map the ingress time slot (FGU time slot) to the egress time slot according to the time slot cross configuration table. Finally, the intermediate node maps the egress time slot (FGU time slot) to the physical interface and sends the FGU time slot to the next hop node.
  • the intermediate node updates the entry time slot table according to the calculated time slot identification of the entry time slot.
  • the subsequent intermediate node receives the FGU time slot from the previous hop node on the entry time slot according to the updated entry time slot table.
  • the intermediate node can map the ingress time
  • time slot identifier of the entry time slot is calculated in the following manner:
  • RxSlotId is the timeslot identifier of the ingress timeslot
  • Target delay2 is the target delay of the node
  • RxMFI is the phase corresponding to the multiframe indication of the ingress timeslot
  • TxMFI is the multiframe of the egress timeslot.
  • MF period is the multiframe period
  • slot time is the time slot interval
  • TxSlotId is the time slot identifier of the egress time slot
  • K is the minimum delay value required for time slot crossover in the intermediate node.
  • RxMFI is the phase corresponding to the multiframe indication of the ingress timeslot, and the intermediate node obtains the RxMFI according to the multiframe header of the ingress timeslot
  • TxMFI is the phase corresponding to the multiframe indication of the egress timeslot
  • the intermediate node obtains the RxMFI according to the multiframe header of the ingress timeslot.
  • RxMFI-TxMFI refers to the phase difference of the multiframe header, which can be obtained by subtracting the transmission time of the MFI in the egress slot (OutMFI-Timestamp) from the reception time of the MFI in the ingress slot (InMFI-Timestamp).
  • the intermediate node obtains the timeslot ID of the egress timeslot based on the timeslot ID of the ingress timeslot, the multiframe indication of the ingress timeslot, and the multiframe indication of the egress timeslot.
  • FIG. 21 is a schematic diagram of another embodiment of the delay compensation method in the embodiment of the present application.
  • the intermediate node performs delay compensation on the small-granule service based on the target delay of the node and the transmission delay of the small-granule service in the intermediate node, including:
  • the intermediate node obtains the time slot identifier of the entry time slot, the multiframe of the entry time slot indicates the corresponding phase, and the multiframe of the exit time slot indicates the corresponding phase, wherein the entry time slot is the bearer received by the intermediate node.
  • the time slot of the small particle service, the egress time slot is the time slot for the intermediate node to send and carry the small particle service;
  • the intermediate node determines the target delay of the node, the time slot identifier of the ingress time slot, the phase corresponding to the multiframe indication of the ingress time slot, the phase corresponding to the multiframe indication of the egress time slot, and the complex phase.
  • the frame period and time slot interval are calculated to obtain the time slot identifier of the egress time slot.
  • the multiframe period is the transmission delay of each multiframe in the egress time slot or the ingress time slot.
  • the time slot The interval is the transmission delay of each time slot in the egress time slot or the ingress time slot.
  • the intermediate node forwards the small-granule service from the previous hop node to the next hop node according to the time slot identifier of the ingress time slot and the time slot identifier of the egress time slot. Specifically, the intermediate node updates the egress time slot table according to the calculated time slot identifier of the egress time slot. The subsequent intermediate node sends the FGU time slot from the previous hop node on the egress time slot based on the updated egress time slot table. After the subsequent intermediate node receives the FGU time slot from the previous hop node on the ingress time slot, it can map the ingress time slot (FGU time slot) to the egress time slot according to the time slot cross configuration table. Finally, the intermediate node maps the egress time slot (FGU time slot) to the physical interface and sends the FGU time slot to the next hop node.
  • the intermediate node maps the egress time slot (FGU time slot) to the physical interface and sends the FGU time slot to the next hop node
  • time slot identifier of the egress time slot is calculated in the following manner:
  • TxSlotId is the timeslot identifier of the egress timeslot
  • Target delay2 is the target delay of the node
  • RxMFI is the phase corresponding to the multiframe indication of the ingress timeslot
  • TxMFI is the multiframe of the egress timeslot.
  • MF period is the multiframe period
  • slot time is the time slot interval
  • RxSlotId is the time slot identifier of the entrance time slot
  • K is the minimum delay value required for time slot crossover in the intermediate node.
  • the service bit stream sent by the intermediate node meets the delay compensation requirements, thereby ensuring that the network transmission delay from the source node to the sink node in the small-granularity service network is equal to or satisfies the network transmission delay from the sink node to the source node.
  • the expected error range may allow the network transmission delay from the source node to the sink node and the network transmission delay from the sink node to the source node to be adjusted to expected values to meet business requirements.
  • the delay compensation method proposed in the embodiments of this application can also be applied to large-granularity business scenarios.
  • the granularity of hard slicing can be greater than 5 gigabits per second (G-bits per-second, Gpbs).
  • Gpbs gigabits per-second
  • the delay compensation method proposed in the embodiments of this application can also be applied to scenarios where CBR services are carried in large-granularity time slot data (hereinafter referred to as large-granularity time slots).
  • the resource granules of large-granularity time slot data can be It is E*1Gbps, or it can be E*5Gbps.
  • the embodiment of this application does not limit this, where E is a positive integer.
  • the specific business processing process is: the source node encapsulates the CBR service bit stream into a service container and maps it to a large granular time slot; the intermediate node crosses the large granular time slot, and then sends the large granular time slot at the egress time slot; the sink After the node demaps the service container from the large-granularity time slot, it decapsulates the service container to obtain the CBR service flow. Finally, the sink node sends the CBR service flow at the service port.
  • the specific delay compensation method for CBR services carried in large-granularity time slots is similar to the delay compensation method proposed in the foregoing embodiments, and will not be described again here.
  • the network device includes corresponding hardware structures and/or software modules that perform each function.
  • the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is performed by hardware or computer software driving the hardware depends on the specific application and design constraints of the technical solution. Skilled artisans may implement the described functionality using different methods for each specific application, but such implementations should not be considered beyond the scope of this application.
  • Embodiments of the present application can divide the network device into functional modules according to the above method examples.
  • each functional module can be divided corresponding to each function, or two or more functions can be integrated into one processing module.
  • the above integrated modules can be implemented in the form of hardware or software function modules. It should be noted that the division of modules in the embodiment of the present application is schematic and is only a logical function division. In actual implementation, there may be other division methods.
  • the following describes the network equipment in the embodiment of the present application.
  • the network equipment introduced below has any function of the first communication device, the second communication device, or the communication device in the above method embodiment.
  • Figure 23 is a schematic structural diagram of a communication device 2300 provided by an embodiment of the present application.
  • the communication device 2300 includes: a transceiver module 2301 for performing step 902; a processing module 2302 for performing steps 901 and 903. , 904 or 905.
  • the communication device 2300 is used as a first communication device, and the communication device 2300 includes:
  • the processing module 2302 is configured to determine a first transmission delay, where the first transmission delay indicates the transmission delay of small-granularity services in the first communication device;
  • the transceiver module 2301 is configured to send the first transmission delay to the second communication device.
  • Node delay is the transmission delay of the small particle service in the first communication device
  • T1 is the first time
  • the first time is the time when the first communication device receives the small particle service
  • T2 is the second time
  • the second time is the time when the first communication device sends the small particle service.
  • the first time is the time when the first communication device receives specific bits in the service bit stream carrying the small-granularity service.
  • the second moment is the moment when the first communication device sends the small particle unit FGU time slot data
  • the FGU time slot data carries the service bit stream of the small particle service. specific bits.
  • the small-granularity service is a fixed bit rate CBR service.
  • the transceiver module 2301 is also configured to receive a second transmission delay from an upper hop node.
  • the second transmission delay indicates that the small-granularity service travels from the source node to the upper hop node.
  • the transceiver module 2301 is also configured to send the first transmission delay and the second transmission delay to the next hop node.
  • the second transmission delay includes: the transmission delay of each node through which the small-grain service is transmitted from the source node to the previous hop node;
  • the second transmission delay includes: the sum of the transmission delays of each node through which the small-grain service is transmitted from the source node to the previous hop node.
  • the transceiver module 2301 is also configured to receive a delay collection message from the previous hop node, where the delay collection message includes the second transmission delay;
  • the processing module 2302 is also configured to update the delay collection message.
  • the updated delay collection message includes the first transmission delay and the second transmission delay;
  • the transceiver module 2301 is also configured to send the updated delay collection message to the second communication device.
  • the delay collection message also includes: path information
  • the processing module 2302 is further configured to determine the second communication device that receives the delay collection message according to the indication of the path information.
  • the second communication device is used for a sink node or network management device
  • the communication device 2300 is used as a second communication device, and the communication device 2300 includes:
  • the transceiver module 2301 is used to obtain the first transmission delay, which indicates the transmission delay of the small-granularity service in the first communication device;
  • the transceiver module 2301 is also used to obtain the transmission delay of the small-granule service in the sink node;
  • the processing module 2302 is configured to determine based on the end-to-end target delay, the first transmission delay of the first communication device in the first n hops, and the transmission delay of the small-granular service in the sink node. Delay compensation value.
  • the delay compensation value is used to perform delay compensation on the small-granule service in the sink node.
  • n is a positive integer.
  • the end-to-end target delay is greater than or equal to the largest of the following two transmission delay values:
  • the first direction is: from the source node to the sink node;
  • the second direction is: from the sink node to the source node.
  • the processing module 2302 is also configured to perform delay compensation on the small-granularity service according to the delay compensation value.
  • the processing module 2302 is also configured to calculate the delay compensation value in the following manner, including:
  • ⁇ is the delay compensation value
  • Target delay1 is the end-to-end target delay
  • the first communication device is used for the source node or the intermediate node
  • n is the number of nodes of the source node and the intermediate node
  • Node' delay is the transmission delay of the small-granularity service in the sink node.
  • Node' delay is the transmission delay of the small particle service in the sink node
  • T3 is the third moment
  • the third moment is the moment when the sink node receives the small particle unit FGU time slot data
  • the FGU time slot data carries specific bits in the service bit stream of the small-granularity service.
  • T4 is the fourth time.
  • the fourth time is the service container solution obtained by the sink node demapping the FGU time slot data. A moment of encapsulation.
  • the processing module 2302 is also used to demap the FGU time slot data to obtain the service container;
  • the processing module 2302 is also used to decapsulate the business container to obtain business slices;
  • the processing module 2302 is also used to store the business slice into memory
  • the processing module 2302 is also configured to extract the service slice from the memory when the residence time of the service slice in the memory reaches the delay compensation value;
  • the processing module 2302 is also configured to reorganize and obtain the service bit stream according to multiple service slices;
  • the transceiver module 2301 is also used to send the service bit stream.
  • the transceiver module 2301 is also configured to receive the transmission delay of the small-granularity service from the sink node in the sink node.
  • the processing module 2302 is further configured to calculate the transmission time based on the end-to-end target delay, the first transmission delay, and the transmission time of the small-grain service in the sink node. delay, after determining the delay compensation value, the method further includes:
  • the transceiver module 2301 is also used to send the delay compensation value to the sink node.
  • the communication device 2300 may correspond to the first communication device or the second communication device in the above method embodiment.
  • Each unit in the communication device 2300 and the above other operations and/or functions are respectively intended to implement the first communication device or the second communication device in the method embodiment.
  • the above-mentioned division of each functional module is used as an example.
  • the above-mentioned function allocation can be completed by different functional modules as needed, that is, the internal structure of the communication device 2300 is divided into different functional modules.
  • Function modules to complete all or part of the functions described above.
  • the communication device 2300 provided in the above-mentioned embodiments and the above-mentioned embodiment method corresponding to FIG. 9 belong to the same concept. Please refer to the above-mentioned method embodiments for its specific implementation process, which will not be described again here.
  • Figure 24 is a schematic structural diagram of a communication device 2400 provided by an embodiment of the present application.
  • the communication device Setup 2400 includes: a transceiver module 2401, used to send and receive data; a processing module 2402, used to perform step 1001 or 1002.
  • the communication device 2400 is used as a communication device, and the communication device 2400 includes:
  • the processing module 2402 is used to determine the transmission delay of small-granularity services in the communication device
  • the processing module 2402 is also configured to perform delay compensation on the small-granule service according to the target delay of the node and the transmission delay of the small-granule service in the communication device.
  • the target delay of the node includes: the target delay of the source node, the target delay of the intermediate node, and/or the target delay of the sink node.
  • the transceiver module 2401 is configured to obtain the first reception time, which is the time when the source node receives specific bits in the service bit stream carrying the small-granularity service;
  • the transceiver module 2401 is also used to obtain a second sending time.
  • the second sending time is the time when the source node sends the small particle unit FGU time slot data.
  • the FGU time slot data carries the small particle service. The specific bits described in the service bit stream;
  • the processing module 2402 is also configured to subtract the first receiving time from the second sending time to obtain the transmission delay of the small-grain service in the source node.
  • the transceiver module 2401 is used to obtain the third reception time, which is the time when the intermediate node receives the small particle unit FGU time slot data at the entrance time slot position, and the FGU time slot data carries the specific bits in the service bit stream of the small-granularity service;
  • the transceiver module 2401 is also used to obtain the fourth sending time, which is the time when the intermediate node sends the FGU time slot data;
  • the processing module 2402 is also configured to subtract the third receiving time from the fourth sending time to obtain the transmission delay of the small-grain service in the intermediate node.
  • the transceiver module 2401 is used to obtain the fifth reception time.
  • the fifth reception time is the time when the sink node receives the small particle unit FGU time slot data.
  • the FGU time slot data carries the The specific bits in the service bit stream of the small-granularity service;
  • the transceiver module 2401 is also used to obtain the sixth sending time.
  • the sixth sending time is the time when the sink node decapsulates the service container.
  • the service container is the communication device's processing of the FGU time slot data. Demapping results in that the service container carries the specific bits in the service bit stream of the small-granularity service;
  • the processing module 2402 is also configured to subtract the fifth receiving time from the sixth sending time to obtain the transmission delay of the small-granularity service in the sink node.
  • the processing module 2402 is also configured to determine a delay compensation value according to the target delay of the node and the transmission delay of the small-granularity service in the communication device;
  • the processing module 2402 is also configured to perform delay compensation on the small-grain service according to the delay compensation value.
  • the processing module 2402 is further configured to store the FGU time slot data in the memory, where the FGU time slot data carries the service bit stream of the small-granularity service;
  • the transceiver module 2401 is also configured to extract the FGU time slot data from the memory when the residence time of the FGU time slot data in the memory reaches the delay compensation value;
  • the transceiver module 2401 is also used to send the FGU time slot data.
  • the processing module 2402 is also configured to cross the entry time slot position of the intermediate node to the exit time slot position of the intermediate node;
  • the processing module 2402 is also configured to store the FGU time slot data received at the entry time slot position of the intermediate node into memory;
  • the processing module 2402 is also configured to extract the FGU time slot data from the memory when the residence time of the FGU time slot data in the memory reaches the delay compensation value;
  • the transceiver module 2401 is also configured to send the FGU time slot data in the egress time slot position of the intermediate node.
  • the processing module 2402 is also used to demap the FGU time slot data to obtain the service container;
  • the processing module 2402 is also used to decapsulate the business container to obtain business slices;
  • the processing module 2402 is also used to store the business slice into memory
  • the processing module 2402 is also configured to extract the service slice from the memory when the residence time of the service slice in the memory reaches the delay compensation value;
  • the processing module 2402 is also configured to reorganize and obtain the service bit stream according to multiple service slices;
  • the transceiver module 2401 is also used to send the service bit stream.
  • the small-granularity service carries a fixed bit rate CBR service.
  • the communication device 2400 may correspond to the communication device in the above method embodiment.
  • Each unit in the communication device 2400 and the above-mentioned other operations and/or functions are respectively used to implement the various steps and functions implemented by the communication device or controller in the method embodiment.
  • the above-mentioned division of each functional module is used as an example.
  • the above-mentioned function allocation can be completed by different functional modules as needed, that is, the internal structure of the communication device 2400 is divided into different functional modules.
  • Function modules to complete all or part of the functions described above.
  • the communication device 2400 provided in the above-mentioned embodiments and the above-mentioned embodiment method corresponding to FIG. 10 belong to the same concept. Please refer to the above-mentioned method embodiments for its specific implementation process, which will not be described again here.
  • the communication devices mentioned in the embodiments of the present application may be, for example, network equipment such as switches and routers, or may be part of the components on the network equipment, such as single boards or line cards on the network equipment. They may also be It is a functional module on the network device, and may also be a chip used to implement the method of the present application, which is not specifically limited in the embodiment of the present application.
  • the transceiver module used to implement the method may be, for example, an interface circuit of the chip, and the processing module may be a processing circuit with a processing function in the chip.
  • the communication devices may be directly connected through, but not limited to, Ethernet cables or optical cables.
  • FIG. 25 is a schematic structural diagram of a communication device 2500 provided by an embodiment of the present application.
  • communication device 2500 shown in FIG. 25 shows certain specific features, those skilled in the art will realize from the embodiments of the present application that for the sake of simplicity, various other features are not shown in FIG. 25 to avoid confusing the present invention. More relevant aspects of the implementation disclosed in the application examples.
  • communication device 2500 includes one or more processing units (eg, CPU) 2501, network interface 2502, programming interface 2503, memory 2504 and one or more communication buses 2505 for interconnecting the various components.
  • the communication device 2500 may also omit or add some functional components or units based on the above examples.
  • the network interface 2502 is used to connect to one or more other communication devices/servers in a network system.
  • communications bus 2505 includes circuitry that interconnects and controls communications between system components.
  • Memory 2504 may include non-volatile memory, such as read-only memory (ROM), programmable ROM (PROM), erasable programmable read-only memory (erasable PROM, EPROM) , electrically erasable programmable read-only memory (electrically EPROM, EEPROM) or flash memory.
  • Memory 2504 may also include volatile memory, which may be random access memory (RAM), which is used as an external cache.
  • memory 2504 or a non-transitory computer-readable storage medium of memory 2504 stores the following programs, modules and data structures, or subsets thereof, including, for example, a transceiver unit (not shown in the figure), an acquisition unit 25041 and a process Unit 25042.
  • the communication device 2500 may have the first communication device, the second communication device, or any function of the communication device in the method embodiment corresponding to FIG. 9 or FIG. 10 .
  • the communication device 2500 corresponds to the first communication device, the second communication device or the communication device or controller in the above method embodiment, and each module in the communication device 2500 and the above other operations and/or functions are respectively intended to implement the above method.
  • the various steps and methods implemented by the first communication device, the second communication device, the communication device or the controller in the embodiment please refer to the method embodiment corresponding to the above-mentioned Figure 9 or Figure 10 for specific details. For the sake of brevity, they will not be described here. Again.
  • the network interface 2502 on the communication device 2500 can complete the data sending and receiving operations, or the processor can call the program code in the memory and cooperate with the network interface 2502 when necessary to realize the functions of the sending and receiving unit. .
  • the communication device 2500 is used to perform a delay measurement method provided by the embodiment of the present application, for example, to perform a delay measurement method corresponding to the embodiment shown in FIG. 9 or FIG. 10 .
  • Figure 26 is a schematic structural diagram of a communication device 2600 provided by an embodiment of the present application.
  • the communication device 2600 includes: a main control board 2626 and an interface board 2630.
  • the main control board 2626 is also called a main processing unit (MPU) or a route processor.
  • the main control board 2626 is used to control and manage various components in the communication device 2600, including route calculation and device management. , equipment maintenance, protocol processing functions.
  • the main control board 2626 includes: a central processing unit 2611 and a memory 2612.
  • the interface board 2630 is also called a line processing unit (LPU), line card or service board.
  • the interface board 2630 is used to provide various service interfaces and implement data packet forwarding.
  • Business interfaces include but are not limited to Ethernet interfaces, POS (Packet over SONET/SDH) interfaces, etc.
  • the interface board 2630 includes: a central processor 2631, a network processor 2632, a forwarding entry memory 2634, and a physical interface card (physical interface card, PIC) 2633.
  • the central processor 2631 on the interface board 2630 is used to control and manage the interface board 2630 and communicate with the central processor 2611 on the main control board 2626.
  • the network processor 2632 is used to implement packet forwarding processing.
  • the network processor 2632 may be in the form of a forwarding chip.
  • the physical interface card 2633 is used to implement the docking function of the physical layer. The original traffic enters the interface card 2630 through this, and the processed packets are sent out from the physical interface card 2633.
  • the physical interface card 2633 includes at least one physical interface, which is also called a physical interface.
  • the physical interface may be a Flexible Ethernet (FlexE) physical interface.
  • the physical interface card 2633 is also called a daughter card and can be installed on the interface board 2630. It is responsible for converting photoelectric signals into messages and checking the validity of the messages before forwarding them to the network processor 2632 for processing.
  • the central processor 2631 of the interface board 2630 can also perform the functions of the network processor 2632, such as implementing software forwarding based on a general CPU, so that the network processor 2632 is not required in the interface board 2630.
  • the communication device 2600 includes multiple interface boards.
  • the communication device 2600 also includes an interface board 2640.
  • the interface board 2640 includes: a central processor 2641, a network processor 2642, a forwarding entry memory 2644, and a physical interface card 2643.
  • the communication device 2600 also includes a switching network board 2620.
  • the switching fabric unit 2620 may also be called a switching fabric unit (switch fabric unit, SFU).
  • SFU switching fabric unit
  • the switching network board 2620 is used to complete data exchange between the interface boards.
  • the interface board 2630 and the interface board 2640 can communicate through the switching network board 2620.
  • the main control board 2626 is coupled to the interface board.
  • the main control board 2626, the interface board 2630, the interface board 2640, and the switching network board 2620 are connected through a system bus and/or a system backplane to achieve intercommunication.
  • an inter-process communication protocol (IPC) channel is established between the main control board 2626 and the interface board 2630, and the main control board 2626 and the interface board 2630 communicate through the IPC channel.
  • IPC inter-process communication protocol
  • the communication device 2600 includes a control plane and a forwarding plane.
  • the control plane includes a main control board 2626 and a central processor 2631.
  • the forwarding plane includes various components that perform forwarding, such as forwarding entry memory 2634, physical interface card 2633, and network processing.
  • the control plane performs functions such as publishing routes, generating forwarding tables, processing signaling and protocol messages, configuring and maintaining device status, etc.
  • the control plane sends the generated forwarding tables to the forwarding plane.
  • the network processor 2632 is based on the control
  • the forwarding table delivered above looks up the table and forwards the packets received by the physical interface card 2633.
  • the forwarding table delivered by the control plane may be stored in the forwarding table item storage 2634. In some embodiments, the control plane and forwarding plane may be completely separate and not on the same device.
  • the transceiver unit in the communication device 2500 may be equivalent to the physical interface card 2633 or the physical interface card 2643 in the communication device 2600; the acquisition unit 25041 and the processing unit 25042 in the communication device 2500 may be equivalent to the central processing unit in the communication device 2600
  • the processor 2611 or the central processing unit 2631 may also be equivalent to the program code or instructions stored in the memory 2612.
  • the operations on the interface board 2640 in the embodiment of the present application are consistent with the operations on the interface board 2630, and will not be described again for the sake of simplicity.
  • the communication device 2600 in this embodiment may correspond to the first communication device, the second communication device or the communication device in each of the above method embodiments.
  • the main control board 2626, the interface board 2630 and/or the communication device 2600 The interface board 2640 can implement the functions and/or various steps performed by the first communication device, the second communication device, or the communication device in each of the above method embodiments. For the sake of brevity, they will not be described again here.
  • main control boards there may be one or more main control boards, and when there are multiple main control boards, they can include the main main control board and the backup main control board.
  • the communication device does not need a switching network board, and the interface board is responsible for processing the business data of the entire system.
  • the communication device Under the distributed forwarding architecture, the communication device can have at least one switching network board.
  • the switching network board realizes data exchange between multiple interface boards and provides large-capacity data exchange and processing capabilities.
  • the communication device can also be in the form of only one board, that is, there is no switching network board.
  • the functions of the interface board and the main control board are integrated on this board.
  • the central processor and the main control board on the interface board The central processing units on the board can be combined into one central processing unit on the board to perform the superimposed functions of the two.
  • the specific architecture used depends on the specific networking deployment scenario and is not uniquely limited here.
  • the above-mentioned first communication device or second communication device may be implemented as a virtualization device.
  • the virtualization device may be a virtual machine (VM), a virtual router or a virtual switch running a program for sending packets.
  • Virtualization appliances are deployed on hardware devices (e.g., physical servers).
  • the first communication device can be implemented based on a general-purpose physical server combined with network functions virtualization (NFV) technology.
  • NFV network functions virtualization
  • An embodiment of the present application also provides a communication device, which includes: a communication interface;
  • a processor connected to the communication interface, based on the communication interface and the processor.
  • the network device is used for a first communication device, so that the first communication device performs the method in the embodiment illustrated in FIG. 9 .
  • the second communication device is caused to perform the method in the embodiment illustrated in FIG. 9 .
  • the signaling device is caused to perform the method in the embodiment illustrated in FIG. 10 .
  • Embodiments of the present application also provide a computer-readable storage medium that includes instructions that, when run on a computer, cause the computer to control the network device to execute any of the implementations shown in the foregoing method embodiments.
  • Embodiments of the present application also provide a computer program product.
  • the computer program product includes computer program code.
  • the computer program code When the computer program code is run on a computer, it causes the computer to execute any of the implementation methods shown in the foregoing method embodiments.
  • embodiments of the present application also provide a computer program product.
  • the computer program product When the computer program product is run on a network device, it causes the network device to execute the first communication device and the first communication device in the method embodiment corresponding to FIG. 9 or FIG. 10 . 2.
  • the communication device or the method executed by the communication device or controller.
  • An embodiment of the present application also provides a chip system, including a processor and an interface circuit.
  • the interface circuit is used to receive instructions and transmit them to the processor.
  • the processor is used to implement the method in any of the above method embodiments.
  • the chip system also includes memory.
  • the processor can be implemented in hardware or software.
  • the processor may be a logic circuit, an integrated circuit, or the like.
  • the processor may be a general-purpose processor that implements the method in any of the above method embodiments by reading the software code stored in the memory.
  • the memory may be integrated with the processor or may be provided separately from the processor, which is not limited by this application.
  • the memory can be a non-transient processor, such as a read-only memory ROM, which can be integrated on the same chip as the processor, or can be separately provided on different chips.
  • This application describes the type of memory, and the relationship between the memory and the processor. There is no specific limitation on how the processor is configured.
  • FIG 27 is a schematic diagram of a network system 2700 proposed in an embodiment of this application.
  • the network system 2700 includes: a first communication device 2701 and a second communication device 2702.
  • the first communication device 2701 and the second communication device 2702 may be, for example, physical devices such as routers, switches, or gateways, or virtual devices that support route publishing and packet forwarding. This embodiment does not limit the specific types of the first communication device 2701 and the second communication device 2702.
  • the network system 2700 also includes a controller 2703.
  • the controller 2703 may be a server that manages the first communication device 2701 and the second communication device 2702.
  • the first communication device 2701 may be the communication device 2300, the communication device 2400, the communication device 2500 or the communication device 2600.
  • the second communication device 2702 may be the communication device 2300, the communication device 2400, the communication device 2500, or the communication device 2600.
  • the controller 2703 may be the communication device 2300, the communication device 2400, the communication device 2500 or the communication device 2600.
  • FIG 28 is a schematic diagram of a network system 2800 proposed in an embodiment of the present application.
  • the network system 2800 includes: a first communication device 2801, a second communication device 2802, and a third communication device 2803.
  • the first communication device 2801, the second communication device 2802, and the third communication device 2803 may be, for example, physical devices such as routers, switches, or gateways, or virtual devices that support route publishing and packet forwarding.
  • This embodiment does not limit the specific types of the first communication device 2801, the second communication device 2802, and the third communication device 2803.
  • the first communication device 2801 may be the edge node 1
  • one or more of the second communication devices 2802 may be intermediate nodes
  • the third communication device 2803 It can be edge node 2.
  • the network system 2800 shown in Figure 28 also includes a controller 2804. Controller 2804 is not shown in the scenario shown in FIG. 7 .
  • the above-mentioned communication devices in various product forms respectively have the functions of the first communication device, the second communication device, or any of the communication devices in the above-mentioned method embodiments, which will not be described again here.
  • B corresponding to A means that B is associated with A, and B can be determined based on A.
  • determining B based on A does not mean determining B only based on A.
  • B can also be determined based on A and/or other information.
  • the disclosed systems, devices and methods can be implemented in other ways.
  • the device embodiments described above are only illustrative.
  • the division of units is only a logical function division. In actual implementation, there may be other division methods.
  • multiple units or components may be combined or integrated. to another system, or some features can be ignored, or not implemented.
  • the coupling or direct coupling or communication connection between each other shown or discussed may be through some interfaces, and the indirect coupling or communication connection of the devices or units may be in electrical, mechanical or other forms.
  • a unit described as a separate component may or may not be physically separate.
  • a component shown as a unit may or may not be a physical unit, that is, it may be located in one place, or it may be distributed to multiple network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.
  • each functional unit in each embodiment of the present application can be integrated into one processing unit, each unit can exist physically alone, or two or more units can be integrated into one unit.
  • the above integrated units can be implemented in the form of hardware or software functional units.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本申请实施例公开一种时延补偿方法，该方法可以应用于小颗粒业务场景，包括：第一通信装置确定第一传输时延，第一传输时延指示小颗粒业务在第一通信装置中的传输时延；第一通信装置向第二通信装置发送第一传输时延。通过上述方法，确保宿节点发出的业务比特流满足时延补偿要求，进而保证小颗粒业务网络中从源节点到宿节点的网络传输时延与宿节点到源节点的网络传输时延相等或者满足预期的误差范围，或者使得源节点到宿节点的网络传输时延与宿节点到源节点的网络传输时延调整至预期值，以满足业务要求。示例性的，当电网系统应用本申请实施例提出的时延补偿方法时，可以确保任意两个终端设备之间信息采集的时刻一致。

Description

一种时延补偿方法以及相关设备
本申请要求于2022年04月24日提交中国国家知识产权局、申请号为202210435589.2、发明名称为“一种时延补偿方法以及相关设备”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术领域，尤其涉及一种时延补偿方法以及相关设备。
背景技术
小颗粒技术是基于国际电联电信标准化部门(ITU-T)城域传送网(metro transport network，MTN)标准扩展的更细粒度的电路交换技术，其将MTN硬管道颗粒度从5吉比特每秒(G-bits per-second，Gpbs)细化为10兆比特每秒(megabits per second，Mbps)，以满足第五代移动通信技术+(5th generation mobile communication technology+，5G+)垂直行业应用和专线业务等场景下小带宽、高隔离性、高安全性等差异化业务承载需求。
小颗粒技术中，通过小颗粒单元(fine granularity unit，FGU)承载小颗粒业务。小颗粒技术中采用时分复用(time-division multiplexing，TDM)机制，以固定周期循环发送FGU基本帧，而每帧包含的时隙数量和位置都严格固定，因此每时隙的发送周期也是确定性的。为了支持数量更多、粒度更小的时隙通道，同时提高带宽利用率，FGU方案采用复帧方式对SPN通道层的5Gbps颗粒进行时隙划分。一个复帧包含20个FGU基本帧，每个FGU基本帧支持24个时隙，一个SPN通道层5Gbps颗粒支持480个时隙。每个FGU基本帧包括开销(overhead，OH)、净荷(payload)以及其它结构组成。
切片分组网(slicing packet network，SPN)切片通道是SPN网络中源宿节点之间的一条传输路径，用于在网络中提供端到端的以太切片连接，具有低时延、透明传输、硬隔离等特征。采用基于以太网66B码块的序列交叉连接技术、城域传送网通路(MTN Path)层帧结构和城域传送网段(MTN Section)层帧结构及其操作、管理和维护(operation administration and maintenance，OAM)开销，客户层业务在源节点映射到MTN Client，网络的中间节点基于以太网66B码块(66B block)序列进行交叉连接，在目的节点从MTN Client中解映射客户层业务，可实现客户数据的接入/恢复、增加/删除OAM信息、数据流的交叉连接，以及通道的监控和保护等功能。
SPN切片通道中，在源节点与宿节点之间存在双向的业务流。本申请实施例中，将源节点至宿节点称为第一方向，将宿节点至源节点称为第二方向，第一方向的业务比特流的处理流程与第二方向的业务比特流的处理流程相互独立。由于SPN网络中每个节点的处理时延可能不同，因此，两个方向的业务比特流的时延可能无法保持一致。
发明内容
第一方面，本申请实施例提出一种时延补偿方法，包括：
第一通信装置确定第一传输时延，所述第一传输时延指示小颗粒业务在所述第一通信装置中的传输时延；
所述第一通信装置向第二通信装置发送所述第一传输时延。
示例性的，第一通信装置用于源节点，当第一通信装置接收第一业务比特流后，第一通信装置对第一业务比特流进行处理。首先，第一通信装置对第一业务比特流进行切片处理，得到第一业务比特流对应的业务切片，该业务切片又称为第一小颗粒业务对应的业务切片。
然后，第一通信装置对该业务切片进行封装得到业务容器。具体的，在业务切片的基础上新增以下一项或多项信息：扩展序列号(Expand Sequence，ESQ)，频率同步消息(例如时戳)，净荷长度，填充(padding)或者校验字段。其中，ESQ序列号用于对业务切片进行无损保护或者丢失检测；频率同步消息用于传递业务相关的时钟信息；当业务切片的长度小于低阶时隙净荷长度时需要封装净荷长度或者填充，该净荷长度或者填充用于标识有效净荷长度；校验字段用于对业务切片进行误码校验。
第一通信装置对业务切片添加开销后，对添加开销的业务切片进行进一步封装处理得到业务容器。具体的，对添加开销的业务切片添加帧边界和帧间隔封装，得到业务容器。
然后，第一通信装置将业务容器转换为64B/66B码块流，换言之将业务容器映射到对应的I码块、S码块、T码块和D码块上。
然后，第一通信装置在上述码块流中插入操作、管理和维护(operation,administration and maintenance，OAM)码块。
然后，第一通信装置将上述插入OAM码块的码块流，映射到第一通信装置的出口时隙位置上，码块流映射到出口时隙位置上的数据称为FGU时隙数据。
最后，第一通信装置通过以太接口或者灵活以太客户(flexible ethernet client，FlexE Client)接口在出口时隙位置上发送FGU时隙数据。
在上述流程中，第一通信装置确定小颗粒业务在第一通信装置中的传输时延，本申请实施例中为了便于描述，将小颗粒业务在第一通信装置中的传输时延称为第一传输时延。
本申请实施例中，通过采集各个节点中小颗粒业务的传输时延，然后结合端到端的目标时延计算得到端到端的时延补偿值。在宿节点中，将小颗粒业务对应的业务切片缓存。直到该业务切片的驻留时间到达端到端的时延补偿值时，宿节点从缓存中提取业务切片进行重组得到业务比特流，然后发送该业务比特流。通过上述方法，实现端到端的时延补偿，确保宿节点发出的业务比特流满足时延补偿要求，进而保证小颗粒业务网络中从源节点到宿节点的网络传输时延与宿节点到源节点的网络传输时延相等或者满足预期的误差范围，或者使得源节点到宿节点的网络传输时延与宿节点到源节点的网络传输时延调整至预期值，以满足业务要求。示例性的，当电网系统应用本申请实施例提出的时延补偿方法时，可以确保任意两个终端设备之间信息采集的时刻一致，从而提升电力系统执行继电保护业务的准确性。电网系统中的终端设备，包括但不限于：继电保护装置、电源管理单元、数据传输单元、电表、开关、发电装置，或者变电装置等。电网系统中各个终端设备采集的信息包括但不限于：电压、电流或者电压频率等。
在第一方面的一种可能实现方式中，所述第一通信装置确定所述小颗粒业务在所述第一通信装置中的传输时延，包括：
所述第一通信装置通过以下方式计算得到所述小颗粒业务在所述第一通信装置中的传输时延，包括：
Nodedelay＝T2-T1；
其中，Nodedelay为所述小颗粒业务在所述第一通信装置中的传输时延，T1为第一时刻，所述第一时刻为所述第一通信装置接收所述小颗粒业务的时刻，T2为第二时刻，所述第二时刻为所述第一通信装置发送所述小颗粒业务的时刻。
T1为第一时刻，所述第一时刻为所述第一通信装置接收所述小颗粒业务的时刻。
可选的，T1为第一通信装置接收承载小颗粒业务的业务比特流中特定比特位的时刻。例如：选取业务比特流中的第1个比特位作为特定比特位，当第一通信装置接收到该业务比特流的第1个比特位时，第一通信装置记录接收第1个比特位的接收时刻。该第1个比特位的接收时刻作为T1。该特定比特位可以根据实际情况选取，例如：该特定比特位可以是业务比特流的第1个比特、第100个比特、第200个比特、第500个比特、和/或第1000个比特等。
可选的，第一通信装置按照接收的业务比特流的比特数量，周期性的记录接收时刻，该接收时刻作为T1。例如：第一通信装置每接收1000个比特，记录一次接收时刻(如第1001个比特的接收时刻)，该接收时刻作为T1。
可选的，第一通信装置接收业务比特流时，每个一个或多个比特记录一次接收时刻。然后周期性的选取接收时刻作为T1。例如：第一通信装置每接收1个比特，记录一次接收时刻。第一通信装置在每间隔1000个接收时刻确定1个时刻作为T1。
可选的，T1为第一通信装置在入口时隙位置上接收FGU时隙数据的时刻。示例性的，T1为第一通信装置接收第一个FGU时隙数据的时刻。可以理解的是，第一通信装置也可以选取其他FGU时隙数据的接收时刻作为T1，例如：T1为第一通信装置接收小颗粒业务的第10个FGU时隙数据的时刻，或者，T1为第一通信装置接收小颗粒业务的第50个FGU时隙数据的时刻，或者，T1为第一通信装置接收小颗粒业务的第100个FGU时隙数据的时刻，此处不作限制。
可选的，第一通信装置按照接收的FGU时隙数据的时隙数量，周期性的记录接收时刻，该接收时刻作为T1。例如：第一通信装置每接收1000个FGU时隙数据，记录一次接收时刻(如第1001个FGU时隙数据的接收时刻)，该接收时刻作为T1。
在第一方面的一种可能实现方式中，所述第二时刻为所述第一通信装置发送小颗粒单元FGU时隙数据的时刻，所述FGU时隙数据承载所述小颗粒业务的业务比特流中所述特定比特位。
T2为第二时刻。可选的，T2为第一通信装置在出口时隙位置上发送FGU时隙数据的时刻。示例性的，T2为第一通信装置发送第一个FGU时隙数据的时刻，或者，T2为第一通信装置发送第50个FGU时隙数据的时刻等，此处不作限制。
可选的，T2为第一通信装置将包括特定比特位的业务容器映射至出口时隙位置的时刻。
可选的，T2为第一通信装置发送携带业务比特流中特定比特位的FGU时隙数据的时刻，该业务比特流中承载小颗粒业务。例如：T1为第一通信装置接收业务比特流中特定比特位 的时刻，T2为第一通信装置发送携带该特定比特位的FGU时隙数据的时刻。
可选的，第一通信装置按照发送的FGU时隙数据的数量，周期性的记录发送时刻，该发送时刻作为T2。例如：第一通信装置每发送1000个FGU时隙数据，记录一次发送时刻(如第1001个FGU时隙数据的发送时刻)，该发送时刻作为T2。
可选的，第一通信装置发送FGU时隙数据时，每发送一个或多个FGU时隙数据记录一次发送时刻。然后周期性的选取发送时刻作为T2。例如：第一通信装置每发送1个FGU时隙数据，记录一次发送时刻。第一通信装置在每间隔1000个发送时刻确定1个时刻作为T2。
可选的，T2为第一通信装置发送小颗粒业务的第一个出口时隙位置的时刻。换言之，第一通信装置发送第一个承载小颗粒业务的出口时隙位置的时刻，或者，第一通信装置发送第一个FGU时隙数据的时刻。可以理解的是，第一通信装置也可以选取其他出口时隙位置的发送时刻作为T2，例如：T2为第一通信装置发送小颗粒业务的第10个出口时隙位置的时刻，或者，T2为第一通信装置发送小颗粒业务的第50个出口时隙位置的时刻，或者，T2为第一通信装置发送小颗粒业务的第100个出口时隙位置的时刻，此处不作限制。
可选的，第一通信装置按照发送的出口时隙位置(FGU时隙)的时隙数量，周期性的记录发送时刻，该发送时刻作为T2。例如：第一通信装置每发送1000个出口时隙位置(FGU时隙)，记录一次发送时刻(如第1001个FGU时隙数据的发送时刻)，该发送时刻作为T2。
在第一方面的一种可能实现方式中，所述小颗粒业务为固定比特率CBR业务。
在第一方面的一种可能实现方式中，所述第一通信装置用于中间节点，所述方法还包括：
所述第一通信装置接收来自上一跳节点的第二传输时延，所述第二传输时延指示所述小颗粒业务从源节点至所述上一跳节点的传输时延；
所述第一通信装置向下一跳节点发送所述第一传输时延和所述第二传输时延。
在第一方面的一种可能实现方式中，第二传输时延包括：所述小颗粒业务从所述源节点传输至所述上一跳节点所经过的每个节点的传输时延；
或者，所述第二传输时延包括：所述小颗粒业务从所述源节点传输至所述上一跳节点所经过的每个节点的传输时延之和。
在第一方面的一种可能实现方式中，所述第一通信装置向所述第二通信装置发送所述第一传输时延，包括：
所述第一通信装置接收来自所述上一跳节点的时延收集消息，所述时延收集消息中包括所述第二传输时延；
所述第一通信装置更新所述时延收集消息，更新后的所述时延收集消息中包括所述第一传输时延和所述第二传输时延；
所述第一通信装置向所述第二通信装置发送所述更新后的所述时延收集消息。
可选的，第一通信装置通过时延收集消息，向第二通信装置发送第一传输时延。第一通信装置接收来自上一跳节点的时延收集信息后，将自身测量得到的第一传输时延填充至该时延收集消息。当第一通信装置的上游还包括其他节点时，第一通信装置接收来自上一 跳节点的时延收集消息，该时延收集消息中包括第二传输时延。然后，第一通信装置更新该时延收集消息，更新后的时延收集消息中包括第一传输时延和第二传输时延。第一通信装置向第二通信装置(或者其他的下游节点)发送该更新后的时延收集消息。
示例性的，时延收集消息存在多种可能的实现方式，包括但不限于：消息(message)、报文、报文头的新增字段、比特信息(包括多个比特位)、或者类型长度值(type length value，TLV)信息等。
在第一方面的一种可能实现方式中，所述时延收集消息还包括：路径信息；
所述第一通信装置根据所述路径信息的指示，确定接收所述时延收集消息的所述第二通信装置。
可选的，该时延收集消息还包括路径信息，该路径信息指示的时延收集消息的传输路径。该路径信息包括一个或多个节点的转发信息。例如，该转发信息包括但不限于：上一跳节点和/或下一跳节点的端口号，或者，上一跳节点和/或下一跳节点的介质访问控制(Media Access Control，MAC)地址，或者，上一跳节点和/或下一跳节点的互联网协议(Internet Protocol，IP)地址，或者上一跳节点和/或下一跳节点的小颗粒通道(channel)号等。
该路径信息所指示的节点需要在时延收集消息中填充自身节点的第一传输时延。第一通信装置根据路径信息，确定目的节点(即接收该时延收集消息的下一跳节点)。然后第一通信装置向目的节点发送时延收集消息，该时延收集消息中携带第一通信装置的第一传输时延。目的节点接收该时延收集消息后，目的节点将自身的第一传输时延填充至该时延收集消息。目的节点根据路径信息的指示，确定接收该更新后的时延收集消息的下一跳节点。然后，目的节点向该下一跳节点发送该更新后的时延收集消息。
可选的，对于接收该时延收集消息的第一通信装置，通过检测自身的地址信息是否与该路径信息所包括的地址信息匹配，确定是否处理该时延收集消息。若匹配，则第一通信装置将自身的第一传输时延填充至该时延收集消息；若不匹配，则第一通信装置直接转发该时延收集消息，或者，第一通信装置丢弃该时延收集消息，或者，第一通信装置根据路径信息的指示确定下一跳节点，然后第一通信装置向下一跳节点转发该时延收集消息。
在第一方面的一种可能实现方式中，所述第二通信装置用于宿节点或网络管理设备；
第二方面，本申请实施例提出一种时延补偿方法，所述方法用于第二通信装置，所述方法包括：
第二通信装置获取第一传输时延，所述第一传输时延指示小颗粒业务在第一通信装置中的传输时延；
所述第二通信装置获取所述小颗粒业务在宿节点中的传输时延；
所述第二通信装置根据端到端的目标时延、前n跳所述第一通信装置的所述第一传输时延，和所述小颗粒业务在所述宿节点中的传输时延，确定时延补偿值，所述时延补偿值用于在所述宿节点中对所述小颗粒业务进行时延补偿，n为正整数。
本申请实施例中，通过采集各个节点中小颗粒业务的传输时延，然后结合端到端的目标时延计算得到端到端的时延补偿值。在宿节点中，将小颗粒业务对应的业务切片缓存。 直到该业务切片的驻留时间到达端到端的时延补偿值时，宿节点从缓存中提取业务切片进行重组得到业务比特流，然后发送该业务比特流。通过上述方法，实现端到端的时延补偿，确保宿节点发出的业务比特流满足时延补偿要求，进而保证小颗粒业务网络中从源节点到宿节点的网络传输时延与宿节点到源节点的网络传输时延相等或者满足预期的误差范围，或者使得源节点到宿节点的网络传输时延与宿节点到源节点的网络传输时延调整至预期值，以满足业务要求。示例性的，当电网系统应用本申请实施例提出的时延补偿方法时，可以确保任意两个终端设备之间信息采集的时刻一致，从而提升电力系统执行继电保护业务的准确性。电网系统中的终端设备，包括但不限于：继电保护装置、电源管理单元、数据传输单元、电表、开关、发电装置，或者变电装置等。电网系统中各个终端设备采集的信息包括但不限于：电压、电流或者电压频率等。
在第二方面的一种可能实现方式中，所述端到端的目标时延大于或等于以下两种传输时延值中最大的一项：第一方向的业务传输时延值或者第二方向的业务传输时延值，其中，
所述第一方向为：从源节点至所述宿节点；
所述第二方向为：从所述宿节点至所述源节点。
具体的，第二通信装置获取端到端的目标时延，端到端的目标时延大于或等于以下两种传输时延值中最大的一项：第一方向的业务传输时延值或者第二方向的业务传输时延值，其中，所述第一方向为：从源节点至所述宿节点；所述第二方向为：从所述宿节点至所述源节点。
端到端的目标时延可以是预配置于第二通信装置，也可以是基于实际测量得到的第一方向上传输时延值和第二方向上传输时延值计算得到，此处不作限制。例如：第一方向的传输时延值为500毫秒，第二方向的传输时延值为450毫秒，则端到端的目标时延设置为500毫秒。
在第二方面的一种可能实现方式中，所述第二通信装置用于所述宿节点，所述方法还包括：
所述第二通信装置根据所述时延补偿值对所述小颗粒业务进行时延补偿。
在第二方面的一种可能实现方式中，所述第二通信装置根据所述端到端的目标时延、前n跳所述第一通信装置的所述第一传输时延，和所述小颗粒业务在所述宿节点中的传输时延，包括：
所述第二通信装置通过以下方式计算得到所述时延补偿值，包括：
其中，Δ为所述时延补偿值，Targetdelay1为所述端到端的目标时延，为前n跳所述第一通信装置的所述第一传输时延，所述第一通信装置用于所述源节点或者中间节点，n为所述源节点和所述中间节点的节点数量，Node’delay为所述小颗粒业务在所述宿节点中传输时延。
在第二方面的一种可能实现方式中，所述第二通信装置用于所述宿节点；
所述第二通信装置获取所述小颗粒业务在所述宿节点中的传输时延，包括：
所述第二通信装置通过以下方式计算得到所述小颗粒业务在所述宿节点中的传输时延，包括：
Node’delay＝T4-T3；
其中，Node’delay为所述小颗粒业务在所述宿节点中的传输时延，T3为第三时刻，所述第三时刻为所述宿节点接收小颗粒单元FGU时隙数据的时刻，所述FGU时隙数据承载所述小颗粒业务的业务比特流中特定比特位，T4为第四时刻，所述第四时刻为所述宿节点对所述FGU时隙数据解映射得到的业务容器解封装的时刻。
在第二方面的一种可能实现方式中，所述第二通信装置用于所述宿节点；
所述第二通信装置根据所述时延补偿值对所述小颗粒业务进行时延补偿，包括：
所述第二通信装置将所述FGU时隙数据进行解映射，得到所述业务容器；
所述第二通信装置对所述业务容器进行解封装，得到业务切片；
所述第二通信装置将所述业务切片存储至存储器；
当所述业务切片在所述存储器中的驻留时间到达所述时延补偿值，所述第二通信装置从所述存储器中提取所述业务切片；
所述第二通信装置根据多个所述业务切片，重组得到所述业务比特流；
所述第二通信装置发送所述业务比特流。
具体的，第二通信装置(宿节点)在入口时隙位置上接收FGU时隙数据后，所述第二通信装置将FGU时隙数据进行解映射，得到业务容器，所述业务容器承载所述小颗粒业务的业务比特流；然后，所述第二通信装置对所述业务容器进行解封装，得到业务切片，所述业务切片承载所述小颗粒业务；所述第二通信装置将所述业务切片存储至存储器；当所述业务切片在所述存储器中的驻留时间到达所述时延补偿值，所述第二通信装置从所述存储器中提取所述业务切片；所述第二通信装置根据多个所述业务切片，重组得到所述业务比特流；所述第二通信装置发送所述业务比特流。
具体的，第二通信装置将得到的业务切片存储至存储器中，该存储器可以是位于第二通信装置内的存储器，该存储器也可以是与第二通信装置相互独立的存储器，此处不作限制。当第二通信装置将业务切片存储至存储器后，第二通信装置启动计时器。当计时器的时间到达时延补偿值时，意味着存储器中业务切片的驻留时间到达时延补偿值。第二通信装置从存储器中提取业务切片，然后基于多个业务切片进行业务重组，得到对应的业务比特流。第二通信装置在物理接口上发送该业务比特流，实现小颗粒业务的时延补偿。
在第二方面的一种可能实现方式中，所述第二通信装置用于所述网络管理设备；
所述第二通信装置获取所述小颗粒业务在所述宿节点中的传输时延，包括：
所述第二通信装置接收来自所述宿节点的所述小颗粒业务在所述宿节点中的传输时延。
通过上述方法，确保宿节点发出的业务比特流满足时延补偿要求，进而保证小颗粒业务网络中从源节点到宿节点的网络传输时延与宿节点到源节点的网络传输时延相等或者满足预期的误差范围，或者使得源节点到宿节点的网络传输时延与宿节点到源节点的网络传输时延调整至预期值，以满足业务要求。
在第二方面的一种可能实现方式中，所述第二通信装置用于所述网络管理设备；
所述第二通信装置根据所述端到端的目标时延、所述第一传输时延，和所述小颗粒业务在所述宿节点中的传输时延，确定所述时延补偿值之后，所述方法还包括：
所述第二通信装置向所述宿节点发送所述时延补偿值。
第三方面，本申请实施例提出一种时延补偿方法，包括：
通信装置确定小颗粒业务在所述通信装置中的传输时延；
所述通信装置根据节点的目标时延和所述小颗粒业务在所述通信装置中的传输时延，对所述小颗粒业务进行时延补偿。
本申请实施例中，通过上述方法，确保每个节点发出的业务比特流满足时延补偿要求，进而保证小颗粒业务网络中从源节点到宿节点的网络传输时延与宿节点到源节点的网络传输时延相等或者满足预期的误差范围，或者使得源节点到宿节点的网络传输时延与宿节点到源节点的网络传输时延调整至预期值，以满足业务要求。
在第三方面的一种可能实现方式中，所述节点的目标时延包括：源节点的目标时延、中间节点的目标时延，和/或宿节点的目标时延。
具体的，节点的目标时延包括：源节点的目标时延、中间节点的目标时延，和/或宿节点的目标时延。
可选的，源节点的目标时延、中间节点的目标时延和宿节点的目标时延满足：源节点的目标时延、中间节点的目标时延和宿节点的目标时延之和，大于或者等于以下两种传输时延值中最大的一项：第一方向的业务传输时延值或者第二方向的业务传输时延值，其中，所述第一方向为：从源节点至所述宿节点；所述第二方向为：从所述宿节点至所述源节点。该业务传输时延值可以是：承载小颗粒业务的业务比特流在源节点至宿节点之间的多个通信装置的传输时延值。
可选的，网络管理设备为每个节点配置对应的目标时延。其中，源节点的目标时延范围可以是：0～100微秒；中间节点的目标时延范围可以是：10～20微秒；宿节点的目标时延访问可以是：宿节点：100～500微秒。
在第三方面的一种可能实现方式中，所述通信装置用于源节点；
所述通信装置确定所述小颗粒业务在所述通信装置中的传输时延，包括：
所述通信装置获取第一接收时刻，所述第一接收时刻为所述源节点接收承载所述小颗粒业务的业务比特流中特定比特位的时刻；
所述通信装置获取第二发送时刻，所述第二发送时刻为所述源节点发送小颗粒单元FGU时隙数据的时刻，所述FGU时隙数据承载所述小颗粒业务的业务比特流中所述特定比特位；
所述通信装置将所述第二发送时刻减去所述第一接收时刻，得到所述小颗粒业务在所述源节点中的传输时延。
关于通信装置获取第一接收时刻的可能方式，与前述第一方面中源节点获取第一时刻的方式类似，此处不作赘述；关于通信装置获取第二发送时刻，与前述第一方面中源节点获取第二时刻类似，此处不做赘述。
在第三方面的一种可能实现方式中，当所述通信装置用于中间节点时；
所述通信装置确定所述小颗粒业务在所述通信装置中的传输时延，包括：
所述通信装置获取第三接收时刻，所述第三接收时刻为所述中间节点在入口时隙位置上接收小颗粒单元FGU时隙数据的时刻，所述FGU时隙数据承载所述小颗粒业务的业务比特流中所述特定比特位；
所述通信装置获取第四发送时刻，所述第四发送时刻为所述中间节点发送所述FGU时隙数据的时刻；
所述通信装置将所述第四发送时刻减去所述第三接收时刻，得到所述小颗粒业务在所述中间节点中的传输时延。
具体的，当通信装置用于中间节点时，所述通信装置获取第三接收时刻，所述第三接收时刻为所述中间节点接收FGU时隙数据的时刻，所述FGU时隙数据承载所述小颗粒业务的业务比特流中特定比特位；所述通信装置获取第四发送时刻，所述第四发送时刻为所述中间节点发送所述FGU时隙数据的时刻，所述业务比特流承载小颗粒业务；所述通信装置将所述第四发送时刻减去所述第三接收时刻，得到所述小颗粒业务在所述中间节点中的传输时延。
具体的，通信装置在入口时隙位置接收FGU时隙数据。然后，通信装置基于时隙交叉映射表的指示将入口时隙位置上接收的FGU时隙数据，映射至出口时隙位置。最后，通信装置通过物理接口在出口时隙位置上发送FGU时隙数据。
关于通信装置获取第三接收时刻的可能方式，与前述第一方面的中间节点获取第一时刻的方式类似，此处不作赘述；关于通信装置获取第四发送时刻，与前述第一方面的前述中间节点获取第二时刻类似，此处不做赘述。
在第三方面的一种可能实现方式中，当所述通信装置用于宿节点时；
所述通信装置确定所述小颗粒业务在所述通信装置中的传输时延，包括：
所述通信装置获取第五接收时刻，所述第五接收时刻为所述宿节点接收小颗粒单元FGU时隙数据的时刻，所述FGU时隙数据承载所述小颗粒业务的业务比特流中所述特定比特位；
所述通信装置获取第六发送时刻，所述第六发送时刻为所述宿节点将业务容器解封装的时刻，所述业务容器为所述通信装置对所述FGU时隙数据解映射得到，所述业务容器承载所述小颗粒业务的业务比特流中所述特定比特位；
所述通信装置将所述第六发送时刻减去所述第五接收时刻，得到所述小颗粒业务在所述宿节点中的传输时延。
关于通信装置获取第五接收时刻的可能方式，与前述第二方面中宿节点获取第三时刻的方式类似，此处不作赘述；关于通信装置获取第六发送时刻，与前述第二方面中中间节点获取第四时刻类似，此处不做赘述。
在第三方面的一种可能实现方式中，所述通信装置根据所述节点的目标时延和所述小颗粒业务在所述通信装置中的传输时延，对所述小颗粒业务进行时延补偿，包括：
所述通信装置根据所述节点的目标时延和所述小颗粒业务在所述通信装置中的传输时延，确定时延补偿值；
所述通信装置根据所述时延补偿值，对所述小颗粒业务进行时延补偿。
本实施例中，通信装置获取小颗粒业务在通信装置中的传输时延后，通信装置根据节 点的目标时延和该传输时延，计算节点的时延补偿值。然后通信装置根据该节点的时延补偿值，在通信装置(自身节点)内进行小颗粒业务的时延补偿，实现逐节点的时延补偿。
在第三方面的一种可能实现方式中，当所述通信装置用于源节点时；
所述通信装置根据所述时延补偿值，对所述小颗粒业务进行时延补偿，包括：
所述通信装置将所述FGU时隙数据存储至存储器，所述FGU时隙数据承载所述小颗粒业务的业务比特流；
当所述FGU时隙数据在所述存储器中的驻留时间到达所述时延补偿值，所述通信装置从所述存储器中提取所述FGU时隙数据；
所述通信装置发送所述FGU时隙数据。
具体的，当通信装置用于源节点时，所述源节点根据所述时延补偿值，对所述小颗粒业务进行时延补偿，包括：源节点接收业务比特流后，源节点对业务比特流进行处理并映射至出口时隙位置，包括：对业务比特流进行切片，得到多个业务切片；然后对业务切片进行封装处理，得到业务容器；将业务容器映射到出口时隙位置：具体的，源节点将业务容器映射到码块流。然后对码块流进行分割处理得到FGU数据时隙；所述源节点将FGU时隙数据存储至存储器，FGU时隙数据承载所述小颗粒业务的业务比特流；当所述源节点的FGU时隙数据在所述存储器中的驻留时间到达所述时延补偿值，所述源节点从所述存储器中提取所述源节点的FGU时隙数据；所述源节点在出口时隙位置上发送所述源节点的FGU时隙数据。
在第三方面的一种可能实现方式中，当所述通信装置用于中间节点时；
所述通信装置根据所述时延补偿值，对所述小颗粒业务进行时延补偿，包括：
所述通信装置将所述中间节点的入口时隙位置交叉至所述中间节点的出口时隙位置；
所述通信装置将在所述中间节点的入口时隙位置接收的所述FGU时隙数据存储至存储器；
当所述FGU时隙数据在所述存储器中的驻留时间到达所述时延补偿值，所述通信装置从所述存储器中提取所述FGU时隙数据；
所述通信装置在所述中间节点的出口时隙位置中发送所述FGU时隙数据。
具体的，当通信装置用于中间节点时，所述中间节点根据所述时延补偿值，对所述小颗粒业务进行时延补偿，包括：所述中间节点在入口时隙位置接收FGU时隙数据，所述FGU时隙数据承载所述小颗粒业务的业务比特流；所述中间节点将所述中间节点的入口时隙位置交叉至所述中间节点的出口时隙位置；所述中间节点将所述FGU时隙数据存储至存储器；当所述FGU时隙数据在所述存储器中的驻留时间到达所述时延补偿值，所述中间节点从所述存储器中提取所述FGU时隙数据；所述中间节点在所述中间节点的出口时隙位置发送所述FGU时隙数据。
在第三方面的一种可能实现方式中，当所述通信装置用于宿节点时；
所述通信装置根据所述时延补偿值，对所述小颗粒业务进行时延补偿，包括：
所述通信装置将所述FGU时隙数据进行解映射，得到所述业务容器；
所述通信装置对所述业务容器进行解封装，得到业务切片；
所述通信装置将所述业务切片存储至存储器；
当所述业务切片在所述存储器中的驻留时间到达所述时延补偿值，所述通信装置从所述存储器中提取所述业务切片；
所述通信装置根据多个所述业务切片，重组得到所述业务比特流；
所述通信装置发送所述业务比特流。具体的，当通信装置用于宿节点时，所述宿节点根据所述时延补偿值，对所述小颗粒业务进行时延补偿，包括：所述宿节点将所述FGU时隙数据进行解映射，得到业务容器，所述业务容器承载所述小颗粒业务的业务比特流；所述宿节点对所述业务容器进行解封装，得到业务切片，所述业务切片承载所述小颗粒的业务比特流；所述宿节点将所述业务切片存储至存储器；当所述业务切片在所述存储器中的驻留时间到达所述时延补偿值，所述宿节点从所述存储器中提取所述业务切片；所述宿节点根据多个所述业务切片，重组得到所述业务比特流；所述宿节点发送所述业务比特流。
在第三方面的一种可能实现方式中，所述小颗粒业务承载固定比特率CBR业务。
第四方面，本申请实施例提出一种通信装置，所述通信装置用作第一通信装置，所述通信装置包括：
收发模块，用于执行前述第一方面中由第一通信装置所执行的接收和/或发送相关的操作；
处理模块，用于执行前述第一方面中由所述第一通信装置所执行的接收和/或发送相关的操作之外的其它操作。
需要说明的是，本申请实施例中提及的通信装置，例如可以是交换机、路由器等网络设备，也可以是网络设备上的一部分组件，例如是网络设备上的单板，线卡，还可以是网络设备上的一个功能模块，还可以是用于实现本申请方法的芯片，本申请实施例不做具体限定。当通信装置是芯片时，用于实现方法的收发模块例如可以是芯片的接口电路，处理模块可以是芯片中具有处理功能的处理电路。通信装置之间例如可以但不限于通过以太网线或光缆直接连接。
示例性的，所述通信装置包括：
处理模块，用于确定第一传输时延，所述第一传输时延指示小颗粒业务在所述第一通信装置中的传输时延；
收发模块，用于向第二通信装置发送所述第一传输时延。
一种可能的实现方式中，所述处理模块，具体用于通过以下方式计算得到所述小颗粒业务在所述第一通信装置中的传输时延，包括：
Nodedelay＝T2-T1；
其中，Nodedelay为所述小颗粒业务在所述第一通信装置中的传输时延，T1为第一时刻，所述第一时刻为所述第一通信装置接收所述小颗粒业务的时刻，T2为第二时刻，所述第二时刻为所述第一通信装置发送所述小颗粒业务的时刻。
一种可能的实现方式中，所述第一时刻为所述第一通信装置接收承载所述小颗粒业务的业务比特流中特定比特位的时刻。
一种可能的实现方式中，所述第二时刻为所述第一通信装置发送小颗粒单元FGU时隙 数据的时刻，所述FGU时隙数据承载所述小颗粒业务的业务比特流中所述特定比特位。
一种可能的实现方式中，所述小颗粒业务为固定比特率CBR业务。
一种可能的实现方式中，所述收发模块，还用于接收来自上一跳节点的第二传输时延，所述第二传输时延指示所述小颗粒业务从源节点至所述上一跳节点的传输时延；
所述收发模块，还用于向下一跳节点发送所述第一传输时延和所述第二传输时延。
一种可能的实现方式中，所述第二传输时延包括：所述小颗粒业务从所述源节点传输至所述上一跳节点所经过的每个节点的传输时延；
或者，所述第二传输时延包括：所述小颗粒业务从所述源节点传输至所述上一跳节点所经过的每个节点的传输时延之和。
一种可能的实现方式中，所述收发模块，还用于接收来自所述上一跳节点的时延收集消息，所述时延收集消息中包括所述第二传输时延；
所述处理模块，还用于更新所述时延收集消息，更新后的所述时延收集消息中包括所述第一传输时延和所述第二传输时延；
所述收发模块，还用于向所述第二通信装置发送所述更新后的所述时延收集消息。
一种可能的实现方式中，所述时延收集消息还包括：路径信息；
所述处理模块，还用于根据所述路径信息的指示，确定接收所述时延收集消息的所述第二通信装置。
一种可能的实现方式中，所述第二通信装置用于宿节点或网络管理设备；
第五方面，本申请实施例提出一种通信装置，所述通信装置用作第二通信装置，所述通信装置包括：
收发模块，用于执行前述第二方面中由第二通信装置所执行的接收和/或发送相关的操作；
处理模块，用于执行前述第二方面中由所述第二通信装置所执行的接收和/或发送相关的操作之外的其它操作。
需要说明的是，本申请实施例中提及的通信装置，例如可以是交换机、路由器等网络设备，也可以是网络设备上的一部分组件，例如是网络设备上的单板，线卡，还可以是网络设备上的一个功能模块，还可以是用于实现本申请方法的芯片，本申请实施例不做具体限定。当通信装置是芯片时，用于实现方法的收发模块例如可以是芯片的接口电路，处理模块可以是芯片中具有处理功能的处理电路。通信装置之间例如可以但不限于通过以太网线或光缆直接连接。
示例性的，所述通信装置包括：收发模块，用于获取第一传输时延，所述第一传输时延指示小颗粒业务在第一通信装置中的传输时延；
所述收发模块，还用于获取所述小颗粒业务在宿节点中的传输时延；
处理模块，用于根据端到端的目标时延、前n跳所述第一通信装置的所述第一传输时延，和所述小颗粒业务在所述宿节点中的传输时延，确定时延补偿值，所述时延补偿值用于在所述宿节点中对所述小颗粒业务进行时延补偿，n为正整数。
一种可能的实现方式中，所述端到端的目标时延大于或等于以下两种传输时延值中最 大的一项：
第一方向的业务传输时延值或者第二方向的业务传输时延值，其中，
所述第一方向为：从源节点至所述宿节点；
所述第二方向为：从所述宿节点至所述源节点。
一种可能的实现方式中，所述处理模块，还用于根据所述时延补偿值对所述小颗粒业务进行时延补偿。
一种可能的实现方式中，所述处理模块，还用于通过以下方式计算得到所述时延补偿值，包括：
其中，Δ为所述时延补偿值，Targetdelay1为所述端到端的目标时延，为前n跳所述第一通信装置的所述第一传输时延，所述第一通信装置用于所述源节点或者中间节点，n为所述源节点和所述中间节点的节点数量，Node’delay为所述小颗粒业务在所述宿节点中传输时延。
一种可能的实现方式中，所述处理模块，还用于通过以下方式计算得到所述小颗粒业务在所述宿节点中的传输时延，包括：
Node’delay＝T4-T3；
其中，Node’delay为所述小颗粒业务在所述宿节点中的传输时延，T3为第三时刻，所述第三时刻为所述宿节点接收小颗粒单元FGU时隙数据的时刻，所述FGU时隙数据承载所述小颗粒业务的业务比特流中特定比特位，T4为第四时刻，所述第四时刻为所述宿节点对所述FGU时隙数据解映射得到的业务容器解封装的时刻。
一种可能的实现方式中，所述处理模块，还用于将所述FGU时隙数据进行解映射，得到所述业务容器；
所述处理模块，还用于对所述业务容器进行解封装，得到业务切片；
所述处理模块，还用于将所述业务切片存储至存储器；
所述处理模块，还用于当所述业务切片在所述存储器中的驻留时间到达所述时延补偿值，从所述存储器中提取所述业务切片；
所述处理模块，还用于根据多个所述业务切片，重组得到所述业务比特流；
所述收发模块，还用于发送所述业务比特流。
一种可能的实现方式中，所述收发模块，还用于接收来自所述宿节点的所述小颗粒业务在所述宿节点中的传输时延。
一种可能的实现方式中，所述处理模块，还用于根据所述端到端的目标时延、所述第一传输时延，和所述小颗粒业务在所述宿节点中的传输时延，确定所述时延补偿值之后，所述方法还包括：
所述收发模块，还用于向所述宿节点发送所述时延补偿值。
第六方面，本申请实施例提出一种通信装置，所述通信装置包括：
收发模块，用于执行前述第三方面中由通信装置所执行的接收和/或发送相关的操作；
处理模块，用于执行前述第三方面中由所述通信装置所执行的接收和/或发送相关的操作之外的其它操作。
需要说明的是，本申请实施例中提及的通信装置，例如可以是交换机、路由器等网络设备，也可以是网络设备上的一部分组件，例如是网络设备上的单板，线卡，还可以是网络设备上的一个功能模块，还可以是用于实现本申请方法的芯片，本申请实施例不做具体限定。当通信装置是芯片时，用于实现方法的收发模块例如可以是芯片的接口电路，处理模块可以是芯片中具有处理功能的处理电路。通信装置之间例如可以但不限于通过以太网线或光缆直接连接。
示例性的，所述通信装置包括：处理模块，用于确定小颗粒业务在所述通信装置中的传输时延；
所述处理模块，还用于根据节点的目标时延和所述小颗粒业务在所述通信装置中的传输时延，对所述小颗粒业务进行时延补偿。
一种可能的实现方式中，所述节点的目标时延包括：源节点的目标时延、中间节点的目标时延，和/或宿节点的目标时延。
一种可能的实现方式中，收发模块，用于获取第一接收时刻，所述第一接收时刻为所述源节点接收承载所述小颗粒业务的业务比特流中特定比特位的时刻；
所述收发模块，还用于获取第二发送时刻，所述第二发送时刻为所述源节点发送小颗粒单元FGU时隙数据的时刻，所述FGU时隙数据承载所述小颗粒业务的业务比特流中所述特定比特位；
所述处理模块，还用于将所述第二发送时刻减去所述第一接收时刻，得到所述小颗粒业务在所述源节点中的传输时延。
一种可能的实现方式中，收发模块，用于获取第三接收时刻，所述第三接收时刻为所述中间节点在入口时隙位置上接收小颗粒单元FGU时隙数据的时刻，所述FGU时隙数据承载所述小颗粒业务的业务比特流中所述特定比特位；
所述收发模块，还用于获取第四发送时刻，所述第四发送时刻为所述中间节点发送所述FGU时隙数据的时刻；
所述处理模块，还用于将所述第四发送时刻减去所述第三接收时刻，得到所述小颗粒业务在所述中间节点中的传输时延。
一种可能的实现方式中，收发模块，用于获取第五接收时刻，所述第五接收时刻为所述宿节点接收小颗粒单元FGU时隙数据的时刻，所述FGU时隙数据承载所述小颗粒业务的业务比特流中所述特定比特位；
所述收发模块，还用于获取第六发送时刻，所述第六发送时刻为所述宿节点将业务容器解封装的时刻，所述业务容器为所述通信装置对所述FGU时隙数据解映射得到，所述业务容器承载所述小颗粒业务的业务比特流中所述特定比特位；
所述处理模块，还用于将所述第六发送时刻减去所述第五接收时刻，得到所述小颗粒业务在所述宿节点中的传输时延。
一种可能的实现方式中，
所述处理模块，还用于根据所述节点的目标时延和所述小颗粒业务在所述通信装置中的传输时延，确定时延补偿值；
所述处理模块，还用于根据所述时延补偿值，对所述小颗粒业务进行时延补偿。
一种可能的实现方式中，所述处理模块，还用于根据将所述FGU时隙数据存储至存储器，所述FGU时隙数据承载所述小颗粒业务的业务比特流；
所述收发模块，还用于当所述FGU时隙数据在所述存储器中的驻留时间到达所述时延补偿值，从所述存储器中提取所述FGU时隙数据；
所述收发模块，还用于发送所述FGU时隙数据。
一种可能的实现方式中，所述处理模块，还用于将所述中间节点的入口时隙位置交叉至所述中间节点的出口时隙位置；
所述处理模块，还用于将在所述中间节点的入口时隙位置接收的所述FGU时隙数据存储至存储器；
所述处理模块，还用于当所述FGU时隙数据在所述存储器中的驻留时间到达所述时延补偿值，从所述存储器中提取所述FGU时隙数据；
所述收发模块，还用于在所述中间节点的出口时隙位置中发送所述FGU时隙数据。
一种可能的实现方式中，所述处理模块，还用于将所述FGU时隙数据进行解映射，得到所述业务容器；
所述处理模块，还用于对所述业务容器进行解封装，得到业务切片；
所述处理模块，还用于将所述业务切片存储至存储器；
所述处理模块，还用于当所述业务切片在所述存储器中的驻留时间到达所述时延补偿值，从所述存储器中提取所述业务切片；
所述处理模块，还用于根据多个所述业务切片，重组得到所述业务比特流；
所述收发模块，还用于发送所述业务比特流。
一种可能的实现方式中，所述小颗粒业务承载固定比特率CBR业务。
第七方面，本申请实施例提出一种网络设备，所述网络设备用于第一通信装置，所述网络设备包括：
处理器，用于确定第一传输时延，所述第一传输时延指示小颗粒业务在所述第一通信装置中的传输时延；
收发器，用于向第二通信装置发送所述第一传输时延。
一种可能的实现方式中，所述处理器，具体用于通过以下方式计算得到所述小颗粒业务在所述第一通信装置中的传输时延，包括：
Nodedelay＝T2-T1；
其中，Nodedelay为所述小颗粒业务在所述第一通信装置中的传输时延，T1为第一时刻，所述第一时刻为所述第一通信装置接收所述小颗粒业务的时刻，T2为第二时刻，所述第二时刻为所述第一通信装置发送所述小颗粒业务的时刻。
一种可能的实现方式中，所述第一时刻为所述第一通信装置接收承载所述小颗粒业务的业务比特流中特定比特位的时刻。
一种可能的实现方式中，所述第二时刻为所述第一通信装置发送小颗粒单元FGU时隙数据的时刻，所述FGU时隙数据承载所述小颗粒业务的业务比特流中所述特定比特位。
一种可能的实现方式中，所述小颗粒业务为固定比特率CBR业务。
一种可能的实现方式中，所述收发器，还用于接收来自上一跳节点的第二传输时延，所述第二传输时延指示所述小颗粒业务从源节点至所述上一跳节点的传输时延；
所述收发器，还用于向下一跳节点发送所述第一传输时延和所述第二传输时延。
一种可能的实现方式中，所述第二传输时延包括：所述小颗粒业务从所述源节点传输至所述上一跳节点所经过的每个节点的传输时延；
或者，所述第二传输时延包括：所述小颗粒业务从所述源节点传输至所述上一跳节点所经过的每个节点的传输时延之和。
一种可能的实现方式中，所述收发器，还用于接收来自所述上一跳节点的时延收集消息，所述时延收集消息中包括所述第二传输时延；
所述处理器，还用于更新所述时延收集消息，更新后的所述时延收集消息中包括所述第一传输时延和所述第二传输时延；
所述收发器，还用于向所述第二通信装置发送所述更新后的所述时延收集消息。
一种可能的实现方式中，所述时延收集消息还包括：路径信息；
所述处理器，还用于根据所述路径信息的指示，确定接收所述时延收集消息的所述第二通信装置。
一种可能的实现方式中，所述第二通信装置用于宿节点或网络管理设备；
第八方面，本申请实施例提出一种网络设备，所述网络设备用于第二通信装置，所述网络设备包括：
收发器，用于获取第一传输时延，所述第一传输时延指示小颗粒业务在第一通信装置中的传输时延；
所述收发器，还用于获取所述小颗粒业务在宿节点中的传输时延；
处理器，用于根据端到端的目标时延、前n跳所述第一通信装置的所述第一传输时延，和所述小颗粒业务在所述宿节点中的传输时延，确定时延补偿值，所述时延补偿值用于在所述宿节点中对所述小颗粒业务进行时延补偿，n为正整数。
一种可能的实现方式中，所述端到端的目标时延大于或等于以下两种传输时延值中最大的一项：
第一方向的业务传输时延值或者第二方向的业务传输时延值，其中，
所述第一方向为：从源节点至所述宿节点；
所述第二方向为：从所述宿节点至所述源节点。
一种可能的实现方式中，所述处理器，还用于根据所述时延补偿值对所述小颗粒业务进行时延补偿。
一种可能的实现方式中，所述处理器，还用于通过以下方式计算得到所述时延补偿值，包括：
其中，Δ为所述时延补偿值，Targetdelay1为所述端到端的目标时延，为前n跳所述第一通信装置的所述第一传输时延，所述第一通信装置用于所述源节点或者中间节点，n为所述源节点和所述中间节点的节点数量，Node’delay为所述小颗粒业务在所述宿节点中传输时延。
一种可能的实现方式中，所述处理器，还用于通过以下方式计算得到所述小颗粒业务在所述宿节点中的传输时延，包括：
Node’delay＝T4-T3；
其中，Node’delay为所述小颗粒业务在所述宿节点中的传输时延，T3为第三时刻，所述第三时刻为所述宿节点接收小颗粒单元FGU时隙数据的时刻，所述FGU时隙数据承载所述小颗粒业务的业务比特流中特定比特位，T4为第四时刻，所述第四时刻为所述宿节点对所述FGU时隙数据解映射得到的业务容器解封装的时刻。
一种可能的实现方式中，所述处理器，还用于将所述FGU时隙数据进行解映射，得到所述业务容器；
所述处理器，还用于对所述业务容器进行解封装，得到业务切片；
所述处理器，还用于将所述业务切片存储至存储器；
所述处理器，还用于当所述业务切片在所述存储器中的驻留时间到达所述时延补偿值，从所述存储器中提取所述业务切片；
所述处理器，还用于根据多个所述业务切片，重组得到所述业务比特流；
所述收发器，还用于发送所述业务比特流。
一种可能的实现方式中，所述收发器，还用于接收来自所述宿节点的所述小颗粒业务在所述宿节点中的传输时延。
一种可能的实现方式中，所述处理器，还用于根据所述端到端的目标时延、所述第一传输时延，和所述小颗粒业务在所述宿节点中的传输时延，确定所述时延补偿值之后，所述方法还包括：
所述收发器，还用于向所述宿节点发送所述时延补偿值。
第九方面，本申请实施例提出一种网络设备，所述网络设备用于通信装置，所述网络设备包括：
处理器，用于确定小颗粒业务在所述通信装置中的传输时延；
所述处理器，还用于根据节点的目标时延和所述小颗粒业务在所述通信装置中的传输时延，对所述小颗粒业务进行时延补偿。
一种可能的实现方式中，所述节点的目标时延包括：源节点的目标时延、中间节点的目标时延，和/或宿节点的目标时延。
一种可能的实现方式中，收发器，用于获取第一接收时刻，所述第一接收时刻为所述源节点接收承载所述小颗粒业务的业务比特流中特定比特位的时刻；
所述收发器，还用于获取第二发送时刻，所述第二发送时刻为所述源节点发送小颗粒 单元FGU时隙数据的时刻，所述FGU时隙数据承载所述小颗粒业务的业务比特流中所述特定比特位；
所述处理器，还用于将所述第二发送时刻减去所述第一接收时刻，得到所述小颗粒业务在所述源节点中的传输时延。
一种可能的实现方式中，收发器，用于获取第三接收时刻，所述第三接收时刻为所述中间节点在入口时隙位置上接收小颗粒单元FGU时隙数据的时刻，所述FGU时隙数据承载所述小颗粒业务的业务比特流中所述特定比特位；
所述收发器，还用于获取第四发送时刻，所述第四发送时刻为所述中间节点发送所述FGU时隙数据的时刻；
所述处理器，还用于将所述第四发送时刻减去所述第三接收时刻，得到所述小颗粒业务在所述中间节点中的传输时延。
一种可能的实现方式中，收发器，用于获取第五接收时刻，所述第五接收时刻为所述宿节点接收小颗粒单元FGU时隙数据的时刻，所述FGU时隙数据承载所述小颗粒业务的业务比特流中所述特定比特位；
所述收发器，还用于获取第六发送时刻，所述第六发送时刻为所述宿节点将业务容器解封装的时刻，所述业务容器为所述通信装置对所述FGU时隙数据解映射得到，所述业务容器承载所述小颗粒业务的业务比特流中所述特定比特位；
所述处理器，还用于将所述第六发送时刻减去所述第五接收时刻，得到所述小颗粒业务在所述宿节点中的传输时延。
一种可能的实现方式中，
所述处理器，还用于根据所述节点的目标时延和所述小颗粒业务在所述通信装置中的传输时延，确定时延补偿值；
所述处理器，还用于根据所述时延补偿值，对所述小颗粒业务进行时延补偿。
一种可能的实现方式中，所述处理器，还用于根据将所述FGU时隙数据存储至存储器，所述FGU时隙数据承载所述小颗粒业务的业务比特流；
所述收发器，还用于当所述FGU时隙数据在所述存储器中的驻留时间到达所述时延补偿值，从所述存储器中提取所述FGU时隙数据；
所述收发器，还用于发送所述FGU时隙数据。
一种可能的实现方式中，所述处理器，还用于将所述中间节点的入口时隙位置交叉至所述中间节点的出口时隙位置；
所述处理器，还用于将在所述中间节点的入口时隙位置接收的所述FGU时隙数据存储至存储器；
所述处理器，还用于当所述FGU时隙数据在所述存储器中的驻留时间到达所述时延补偿值，从所述存储器中提取所述FGU时隙数据；
所述收发器，还用于在所述中间节点的出口时隙位置中发送所述FGU时隙数据。
一种可能的实现方式中，所述处理器，还用于将所述FGU时隙数据进行解映射，得到所述业务容器；
所述处理器，还用于对所述业务容器进行解封装，得到业务切片；
所述处理器，还用于将所述业务切片存储至存储器；
所述处理器，还用于当所述业务切片在所述存储器中的驻留时间到达所述时延补偿值，从所述存储器中提取所述业务切片；
所述处理器，还用于根据多个所述业务切片，重组得到所述业务比特流；
所述收发器，还用于发送所述业务比特流。
一种可能的实现方式中，所述小颗粒业务承载固定比特率CBR业务。
第十方面，提供了一种通信系统，所述通信系统包括如第四方面或第五方面所述的网络设备。
第十一方面，提供了一种通信系统，所述通信系统包括如第六方面所述的网络设备。
本申请第十二方面提供一种计算机存储介质，该计算机存储介质可以是非易失性的；该计算机存储介质中存储有计算机可读指令，当该计算机可读指令被处理器执行时实现第一方面或者第二方面或者第三方面中任意一种实现方式中的方法。
本申请第十三方面提供一种包含指令的计算机程序产品，当其在计算机上运行时，使得计算机执行第一方面或者第二方面或者第三方面中任意一种实现方式中的方法。
本申请第十四方面提供一种芯片系统，该芯片系统包括处理器和接口电路，所述处理器和接口电路用于支持通信装置实现上述任一方面所述的方法中所涉及的功能，例如，发送或处理上述方法中所涉及的数据和/或信息。在一种可能的设计中，芯片系统还包括存储器，用于保存网络设备必要的程序指令和数据。该芯片系统，可以由芯片构成，也可以包括芯片和其他分立器件。
本申请第十五方面提供一种网络设备，所述网络设备用作第一通信装置，所述网络设备包括：通信接口；
与所述通信接口连接的处理器，基于所述通信接口和所述处理器，使得所述第一通信装置执行如前述第一方面中的方法。
本申请第十六方面提供一种网络设备，所述网络设备用作第二通信装置，所述网络设备包括：通信接口；
与所述通信接口连接的处理器，基于所述通信接口和所述处理器，使得所述第二通信装置执行如前述第二方面中的方法。
本申请第十七方面提供一种网络设备，所述网络设备用作通信装置，所述网络设备包括：通信接口；
与所述通信接口连接的处理器，基于所述通信接口和所述处理器，使得所述通信装置执行如前述第三方面中的方法。
附图说明
图1为小颗粒技术应用于智能电网的应用场景示意图；
图2为FGU基帧的结构示意图；
图3a为FGU复帧的结构示意图；
图3b为FGU基帧开销示意图；
图4为CRB业务的处理流程示意图；
图5为基帧净荷示意图；
图6为本申请实施例中小颗粒业务复帧的示意图；
图7为本申请实施例中一种网络场景示意图；
图8为1DM流程示意图；
图9为本申请实施例中时延补偿方法的一种实施例示意图；
图10为本申请实施例中时延补偿方法的一种实施例示意图；
图11为本申请实施例中业务比特流中特定比特位的一种示意图；
图12为本申请实施例中业务比特流中特定比特位的一种示意图；
图13为本申请实施例中业务比特流中特定比特位的一种示意图；
图14为本申请实施例中传输时延的一种场景示意图；
图15为本申请实施例中传输时延的又一种场景示意图；
图16为本申请实施例中一种应用场景示意图；
图17为本申请实施例中又一种应用场景示意图；
图18为本申请实施例中一种测量传输时延的示意图；
图19为本申请实施例中又一种应用场景示意图；
图20为本申请实施例中时延补偿方法的又一种实施例示意图；
图21为本申请实施例中时延补偿方法的又一种实施例示意图；
图22为本申请实施例中时延收集消息的转发示意图；
图23为本申请实施例提供的一种通信装置2300的结构示意图；
图24为本申请实施例提供的一种通信装置2400的结构示意图；
图25为本申请实施例提供的一种通信装置2500的结构示意图；
图26为本申请实施例提供的一种通信装置2600的结构示意图；
图27为本申请实施例提出的一种网络系统2700示意图；
图28为本申请实施例提出的一种网络系统2800示意图。
具体实施方式
下面，对本申请实施例进行描述。显然，所描述的实施例仅仅是本申请一部分的实施例，而不是全部的实施例。本领域普通技术人员可知，随着新应用场景的出现，本申请实施例提供的技术方案对于类似的技术问题，同样适用。
本申请的说明书和权利要求书及上述附图中的术语“第一”、“第二”等是用于区别类似的对象，而不必用于描述特定的顺序或先后次序。应该理解这样使用的描述在适当情况下可以互换，以便使实施例能够以除了在本申请图示或描述的内容以外的顺序实施。此外，术语“包括”和“具有”以及他们的任何变形，意图在于覆盖不排他的包含，例如，包含了一系列步骤或模块的过程、方法、系统、产品或设备不必限于清楚地列出的那些步骤或模块，而是可包括没有清楚地列出的或对于这些过程、方法、产品或设备固有的其它步骤 或模块。在本申请中出现的对步骤进行的命名或者编号，并不意味着必须按照命名或者编号所指示的时间/逻辑先后顺序执行方法流程中的步骤，已经命名或者编号的流程步骤可以根据要实现的技术目的变更执行顺序，只要能达到相同或者相类似的技术效果即可。本申请中所出现的单元的划分，是一种逻辑上的划分，实际应用中实现时可以有另外的划分方式，例如多个单元可以结合成或集成在另一个系统中，或一些特征可以忽略，或不执行，另外，所显示的或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，单元之间的间接耦合或通信连接可以是电性或其他类似的形式，本申请中均不作限定。并且，作为分离部件说明的单元或子单元可以是也可以不是物理上的分离，可以是也可以不是物理单元，或者可以分布到多个电路单元中，可以根据实际的需要选择其中的部分或全部单元来实现本申请方案的目的。
首先，介绍本申请实施例涉及的一些技术概念。
(1)、小颗粒技术。
小颗粒技术中，通过小颗粒单元(fine granularity unit，FGU)承载小颗粒业务。小颗粒技术继承了切片分组网(slicing packet network，SPN)高效以太网内核，将细粒度切片技术融入SPN整体架构，提供了低成本、精细化、硬隔离的小颗粒承载管道。FGU将硬切片的颗粒度从5吉比特每秒(G-bits per-second，Gpbs)细化为10兆比特每秒(megabits per second，Mbps)，以满足第五代移动通信技术+(5th generation mobile communication technology+，5G+)垂直行业应用和专线业务等场景下小带宽、高隔离性、高安全性等差异化业务承载需求。
下面，结合附图介绍小颗粒技术的应用场景。例如图1示意的场景，图1为小颗粒技术应用于智能电网的应用场景示意图。智能电网由很多部分组成，可分为：智能变电站，智能配电网，智能电能表，智能交互终端，智能调度，智能家电，智能用电楼宇，智能城市用电网，智能发电系统，和/或，新型储能系统等。
智能电网是信息技术、传感器技术、自动控制技术与电网基础设施有机融合，可获取电网的全景信息，及时发现、预见可能发生的故障。故障发生时，电网可以快速隔离故障，实现自我恢复，从而避免大面积停电的发生。在智能电网中，柔性交/直流输电、网厂协调、智能调度、电力储能、配电自动化等技术的广泛应用，使电网运行控制更加灵活、经济，并能适应大量分布式电源、微电网及电动汽车充放电设施的接入。通信、信息和现代管理技术的综合运用，将大大提高电力设备使用效率，降低电能损耗，使电网运行更加经济和高效。实现实时和非实时信息的高度集成、共享与利用，为运行管理展示全面、完整和精细的电网运营状态图，同时能够提供相应的辅助决策支持、控制实施方案和应对预案。在智能电网中建立双向互动的服务模式，用户可以实时了解供电能力、电能质量、电价状况和停电信息，合理安排电器使用；电力企业可以获取用户的详细用电信息，为其提供更多的增值服务。
基于上述要求，智能电网类业务对实时性和安全性要求高。这类业务带宽需求一般不大于20Mbps，端到端单向时延要求为小于20毫秒(ms)，且对可靠性和安全性要求较高，以此来保证不会因通信原因出现供电事故，呈现了典型了小带宽、确定性低时延、高可靠、 高安全的业务特点。在小颗粒业务场景中可以包括多种终端设备和网络设备，例如：电源管理单元(Power Management Unit,PMU)，或者各级的数据传输单元(Data Transfer unit，DTU)。又或者，各类智能电表或者智能开关等。
在智能电网场景中，根据用途可以划分为多类切片，例如：对于传输网(I区)和调度数据网(II区)等生产类业务，采用小颗粒硬切片；对于综合数据网(III区)和IV区等管理类业务，采用MTN接口分组切片；对于公共业务，采用MTN接口分组切片。
可以理解的是，小颗粒技术还可以应用于多种场景，包括但不限于：医疗、港口、铁路、或者专线业务等，此处不做限制。
(2)、小颗粒单元帧。
下面介绍小颗粒单元的具体帧结构。小颗粒单元帧，又称为小颗粒单元(fine granularity unit，FGU)帧，或者FGU帧。小颗粒技术中采用时分复用(time-division multiplexing，TDM)机制，以固定周期循环发送小颗粒单元帧，而每帧包含的时隙数量和位置都严格固定，因此每时隙的发送周期也是确定性的。为了支持数量更多、粒度更小的时隙通道，同时提高带宽利用率。示例性的，小颗粒业务方案采用复帧方式对SPN通道层的5Gbps颗粒进行时隙划分，或者1Gbps颗粒进行时隙划分等。
SPN通道层位于IEEE 802.3的物理编码子层(physical coding sublayer，PCS)层，采用了IEEE 802.3的PCS64/66B编码格式。小颗粒单元帧采用了和SPN通道层相同的64/66B编码格式，将开销和包含多个时隙的净荷编码后封装到固定长度的S块+D块+T块序列。
示例性的，小颗粒单元帧包括FGU基本单元帧(又称为FGU基本帧、FGU基帧、基帧或者单帧)，FGU基帧具有固定长度，包含1个开始码块(S0)、195个数据码块(D)和1个结束码块(T7)，共197个66B码块(66B blocks)。FGU单帧的195个数据码块和1个结束(T7)码块提供了1567(195×8+7)字节的数据内容，包含7字节的开销和1560字节的净荷。其中净荷划分为相同大小的24个子时隙(Sub-Slot)。来自业务的66B码块，经过66B到65B压缩后，填充到Sub-Slot净荷中。每个子时隙(Sub-Slot)为65字节，可以承载8个65bit码块。具体的，请参阅图2，图2为FGU基帧的结构示意图。关于FGU复帧，请参阅图3a，图3a为FGU复帧的结构示意图。一个FGU复帧包含20个FGU基本帧，每个FGU基本帧支持24个时隙，一个SPN通道层5Gbps颗粒支持480个时隙。每个FGU基本帧包括基帧开销(overhead，OH)和基帧净荷(payload)，本申请实施例中基帧开销又称为开销或者OH。需要说明的是，FGU基本帧还可以包括其它内容，本申请实施例对此不作限制。
每个FGU基本帧包括的开销长度为56比特，请参见图3b，图3b为FGU基帧开销示意图。开销包括：复帧指示(MFI)、标识(Flag)字段、保留(RES)字段和开销信息区。具体如下：
复帧指示(multiframe indicator，MFI)，MFI长度为6比特，用于指示FGU复帧中每个基帧的编号，对于复帧中第一个基帧，MFI的值为0。对于第一个基帧之后的基帧，MFI的值依次加1。
标识(Flag)字段，用于指示该开销中CA字段之后的比特位置的用途。该Flag字段又称为开销通道使用指示字段。
开销信息区包括：时隙增大调整通告(S字段)、时隙生效指示(C字段)、变更应答(change answer，CA)字段(CA字段又称为时隙调整应答字段)、变更请求(change request，CR)字段(CR字段又称为时隙调整请求字段)、通用通信信道(general communication channel，GCC)、客户端标识(client ID)、时隙标识(sub-slot ID)和循环冗余码验证(cyclic redundancy check，CRC)。
(4)、从业务比特流到小颗粒业务复帧。
下面以小颗粒业务是固定比特率(constant bit rate，CBR)业务为例，说明节点接收业务比特流后，具体是如何对业务比特流进行处理得到小颗粒业务复帧。可以理解的是，本申请实施例涉及的小颗粒业务还可以是以太网(Ethernet)业务等其他基于小颗粒技术传输的业务，本申请实施例对此不作限制。
请参阅图4，图4为CRB业务的处理流程示意图。CBR业务的处理流程包括：
S1、业务切片。
步骤S1中，节点接收业务比特流，该业务比特流中承载CBR业务。具体的，业务比特流包括j个CBR业务帧，j为大于1的正整数。节点接收j个CBR业务帧后，对业务数据进行切片，得到对应的业务切片。具体的切片方案包括：比特透明切片模式，即不识别业务帧的具体内容，而是按照固定的比特数进行切片，例如每i个比特切片得到一个业务切片，其中i为大于1的正整数；帧切片模型，即识别具体的帧格式，然后按照固定的帧数量进行切片，例如每j个帧切片得到一个业务切片，其中，j为大于1的正整数。
S2、切片封装。
步骤S2中，当节点对业务比特流进行切片处理得到对应的业务切片后，对该业务切片进行封装处理，得到对应的业务容器。具体的，对业务切片添加开销，得到的添加开销后的业务切片的长度和低阶时隙净荷的长度相同，例如都是Y比特，Y为大于1的正整数。具体封装流程如下：在业务切片的基础上新增以下一项或多项信息：扩展序列号(Expand Sequence，ESQ)，频率同步消息(例如时戳)，净荷长度，填充(padding)或者校验字段。其中，ESQ序列号用于对业务切片进行无损保护或者丢失检测；频率同步消息用于传递业务相关的时钟信息；当业务切片的长度小于低阶时隙净荷长度时需要封装净荷长度或者填充，该净荷长度或者填充用于标识有效净荷长度；校验字段用于对业务切片进行误码校验。
节点对业务切片添加开销后，对添加开销的业务切片进行进一步封装处理得到业务容器。具体的，对添加开销的业务切片添加帧边界和帧间隔封装，得到业务容器。
然后，节点将业务容器转换为64B/66B码块流，换言之将业务容器映射到对应的I码块、S码块、T码块和D码块上。
S3、插入操作、管理和维护(operation,administration and maintenance，OAM)码块。
步骤S3中，节点在码块流中插入OAM码块。OAM码块在本申请实施例中又称为OAM消息。
S4、转码压缩后数据。
步骤S4为可选步骤，为了提升数据通道的承载效率，对插入OAM码块的64B/66B码块 流进行转码压缩处理，具体的转码算法可以采用64B/65B转码算法或256B/257B转码算法，本申请实施例对此不作限制。
S5、数据切片为低阶时隙净荷。
步骤S5中，节点对转码后的数据流按照一定比特长度进行切片处理，例如：按照每时隙净荷长度(Y比特，Y为大于1的正整数)进行切片处理，该每时隙净荷长度等于低阶时隙净荷的长度。又例如：该每时隙净荷长度可以是Z个码块，该码块可以是64B/66B码块、也可以是转码后的64B/65B码块，还可以是256B/257B码块，本申请实施例对此不作限制。
当节点得到低阶时隙净荷后，将低阶时隙净荷向基帧净荷(payload)中装载。具体请参阅图5，图5为基帧净荷示意图。小颗粒业务基帧(本申请实施例中将小颗粒业务基帧简称为基帧)的封装过程如下：FGU基帧采用S码块(又称为/S/码块)、D码块(又称为/D/码块)和T码块(又称为/T/码块)封装。码块流中的数据字段共同组成基帧的净荷(payload)域段，其中，S码块中的数据字段作为可选域段，T码块可以是T0-T7共七个码块中的任意一种。基帧净荷域段用于装载(M/X)个低阶时隙净荷和低阶时隙开销(overhead，OH)。(M/X)个低阶时隙净荷字段根据时隙表装载不同低阶通道(sub-Client)数据，M为大于1的正整数、X为大于1的正整数；低阶时隙开销字段包含基帧序列号、低阶通道时隙分配表、管理消息通道(管理消息通道为可选项)和开销校验(开销校验为可选项)等。
当节点得到基帧后，将基帧以小颗粒业务复帧的形式发送出去，换言之将小颗粒业务复帧映射至出口时隙位置上然后发送出去。具体的，请参阅图6，图6为本申请实施例中小颗粒业务复帧的示意图。节点在带宽为N*5(千兆比特每秒，Gbps)的灵活以太网(Flexible Ethernet，FlexE)客户端(Client)接口或普通以太网(ETH)端口内划分M个低阶时隙进行循环传输，每个循环定义为一个复帧，复帧进一步切分成X个定长基帧，其中，N为大于1的正整数。每个基帧的净荷中装载(M/X)个低阶时隙。基帧采用S码块、T码块、I码块(即空闲idle码块)进行封装，确定每个基帧的边界。每个基帧头部携带部分低阶开销，X个基帧开销组成一个复帧开销，用于传输低通道时隙配置和管理消息。
(5)、小颗粒业务的时延测量。
首先，介绍本申请实施例涉及的网络场景。请参阅图7，图7为本申请实施例中一种网络场景示意图。小颗粒业务网络(FGU网络)中包括边缘节点1、边缘节点2和中间节点，其中，边缘节点1视为源节点、边缘节点2视为宿节点，中间节点包括Q个节点，Q为大于1的整数。源节点与宿节点之间存在双向业务流(该双向业务流又称为业务比特流)，该业务流中承载小颗粒业务。本申请实施例中，将源节点发向宿节点的业务流方向称为第一方向，该第一方向也可以称为前向；将宿节点发向源节点的业务流方向称为第二方向，该第二方向也可以称为后向。上述节点又可以称为网络设备，该网络设备包括但不限于：交换机、路由器或者分组传送网(packet transport network，PTN)设备。
结合上述网络场景，目前FGU网络支持的时延测量包括：单向时延测量(One-way Delay Measurement，1DM)和双向时延测量(Two-way Delay Measurement，2DM)，下面分别进行说明：
单向时延测量：
为了便于理解，请参阅图8，图8为1DM流程示意图。当前，源节点接收承载小颗粒业务的业务比特流后，对业务比特流进行切片处理得到对应的业务切片。然后，对业务切片进行封装处理得到对应的业务容器，并转换为码块流。源节点在相邻的两个业务切片对应的码块流之间，确定空闲(idle)码块，然后将空闲码块替换为1DM码块，该流程也称为插入1DM码块(或者称为：插入1DM消息，1DM消息包括一个或多个1DM码块)。此时，源节点记录插入1DM码块的时刻为H1。H1作为发送1DM码块的时刻(具体可以是发送1DM消息中第一个块(block)的时刻)，H1写入1DM消息的时间戳(timestamp)字段。然后，源节点将包括1DM码块的码块流映射到出口时隙位置上，该出口时隙位置中发送的数据由于承载小颗粒业务，因此该出口时隙位置上发送的时隙也称为FGU时隙数据。最后，源节点将FGU时隙数据通过以太接口或者灵活以太客户(flexible ethernet client，FlexE Client)接口发送。
本申请实施例中FGU时隙数据的资源粒度可以是：时隙、子时隙、帧、子帧，或者复帧等，本申请实施例对此不作限制。为了便于描述，本申请实施例中以FGU时隙数据的资源粒度是子时隙为例进行说明。
中间节点在入口时隙位置上接收FGU时隙数据后，中间节点在出口时隙位置上发送FGU时隙数据。入口时隙位置与出口时隙位置之间的映射关系，由时隙交叉配置表指示。
对于宿节点，通过以太接口或者灵活以太客户(flexible ethernet client，FlexE Client)接口在入口时隙位置接收来自中间节点的FGU时隙数据。首先，宿节点对该FGU时隙数据进行解映射处理得到对应的码块流，进而获得对应的一个或多个业务容器。此时，宿节点记录从码块流中提取1DM码块的时刻H3，H3作为接收1DM码块的时刻(具体可以是接收1DM消息中第一个块(block)的时刻)。然后，宿节点对业务容器进行进一步的解封装处理，得到对应的业务切片。宿节点从1DM码块中提取发送1DM码块的时刻H1后，宿节点根据H1和H3计算单向时延。宿节点根据计算得到的单向时延。具体的：对多个业务切片重组得到业务比特流。最后，宿节点将业务比特流发送出去。
申请人研究发现，SPN切片通道中，在源节点与宿节点之间存在双向的业务流。本申请实施例中，将源节点至宿节点称为第一方向，将宿节点至源节点称为第二方向，第一方向的业务比特流的处理流程与第二方向的业务比特流的处理流程相互独立。由于SPN网络中每个节点的处理时延可能不同，因此，两个方向的业务比特流的时延可能无法保持一致。
基于此，本申请实施例提出一种时延补偿方法，包括：通信装置确定小颗粒业务在所述通信装置中的传输时延；所述通信装置根据目标时延和所述小颗粒业务在所述通信装置中的传输时延，对所述小颗粒业务进行时延补偿。通过上述方法，通信装置实现对小颗粒业务的时延补偿，保证第一方向的业务比特流的时延与第二方向的业务比特流的时延一致。
需要说明的是，本申请实施例中的小颗粒业务，可以是固定比特率(constant bit rate，CBR)业务，也可以是以太帧业务，还可以是其他小颗粒业务，本申请实施例对此不作限制。本申请实施例中，以小颗粒业务为CBR业务为例进行说明。
下面，结合附图具体介绍本申请实施例，本申请实施例按照实现时延补偿的位置，具体可以分为：
(1)、源节点到宿节点的端到端时延补偿。
(2)、逐节点的时延补偿。
首先，介绍(1)、源节点到宿节点的端到端时延补偿。具体的，按照网络管理设备是否参与时延补偿，可以细分为以下两个方案：
(1.1)、网络管理设备不参与时延补偿；(1.2)、网络管理设备参与时延补偿。
本申请实施例中，第一通信装置可以用于源节点和/或中间节点，第二通信装置可以用于宿节点或者网络管理设备。请参阅图9，图9为本申请实施例中时延补偿方法的一种实施例示意图。本申请实施例提出的一种时延补偿方法，包括：
901、第一通信装置确定小颗粒业务在第一通信装置中的传输时延。
本实施例中，首先介绍第一通信装置对业务比特流的处理流程，该业务比特流承载的业务为小颗粒业务，具体如下：
具体的，以图7示意的场景为例进行说明。
第一通信装置用于源节点，当第一通信装置接收第一业务比特流后，第一通信装置对第一业务比特流进行处理，具体的处理流程类似图4～图5示意的场景。首先，第一通信装置对第一业务比特流进行切片处理，得到第一业务比特流对应的业务切片，该业务切片又称为第一小颗粒业务对应的业务切片。
然后，第一通信装置对该业务切片进行封装得到业务容器。具体的，在业务切片的基础上新增以下一项或多项信息：扩展序列号(Expand Sequence，ESQ)，频率同步消息(例如时戳)，净荷长度，填充(padding)或者校验字段。其中，ESQ序列号用于对业务切片进行无损保护或者丢失检测；频率同步消息用于传递业务相关的时钟信息；当业务切片的长度小于低阶时隙净荷长度时需要封装净荷长度或者填充，该净荷长度或者填充用于标识有效净荷长度；校验字段用于对业务切片进行误码校验。
第一通信装置对业务切片添加开销后，对添加开销的业务切片进行进一步封装处理得到业务容器。具体的，对添加开销的业务切片添加帧边界和帧间隔封装，得到业务容器。
然后，第一通信装置将业务容器转换为64B/66B码块流，换言之将业务容器映射到对应的I码块、S码块、T码块和D码块上。
然后，第一通信装置在上述码块流中插入操作、管理和维护(operation,administration and maintenance，OAM)码块。
然后，第一通信装置将上述插入OAM码块的码块流，映射到第一通信装置的出口时隙位置上，码块流映射到出口时隙位置上的数据称为FGU时隙数据。
最后，第一通信装置通过以太接口或者灵活以太客户(flexible ethernet client，FlexE Client)接口在出口时隙位置上发送FGU时隙数据。
在上述流程中，第一通信装置确定小颗粒业务在第一通信装置中的传输时延，本申请实施例中为了便于描述，将小颗粒业务在第一通信装置中的传输时延称为第一传输时延。具体的，首先，第一通信装置确定T1，T1为第一通信装置接收小颗粒业务的时刻；第一通信装置确定T2，T2为第一通信装置发送该小颗粒业务的时刻。然后，第一通信装置使用T2减去T1，确定小颗粒业务在第一通信装置中的传输时延。所述第一通信装置通过以下方 式计算得到所述小颗粒业务在所述第一通信装置中的传输时延，包括：
Nodedelay＝T2-T1；
其中，Nodedelay为所述小颗粒业务在所述第一通信装置中的传输时延(即第一传输时延)，T1为第一时刻，所述第一时刻为所述第一通信装置接收所述小颗粒业务的时刻，T2为第二时刻，所述第二时刻为所述第一通信装置发送所述小颗粒业务的时刻。
首先介绍T1：当第一通信装置用于源节点时：
可选的，T1为第一通信装置接收承载小颗粒业务的业务比特流中特定比特位的时刻。例如：选取业务比特流中的第1个比特位作为特定比特位，当第一通信装置接收到该业务比特流的第1个比特位时，第一通信装置记录接收第1个比特位的接收时刻。该第1个比特位的接收时刻作为T1。该特定比特位可以根据实际情况选取，例如：该特定比特位可以是业务比特流的第1个比特、第100个比特、第200个比特、第500个比特、和/或第1000个比特等。
可选的，第一通信装置按照接收的业务比特流的比特数量，周期性的记录接收时刻，该接收时刻作为T1。例如：第一通信装置每接收1000个比特，记录一次接收时刻(如第1001个比特的接收时刻)，该接收时刻作为T1。
可选的，第一通信装置接收业务比特流时，每个一个或多个比特记录一次接收时刻。然后周期性的选取接收时刻作为T1。例如：第一通信装置每接收1个比特，记录一次接收时刻。第一通信装置在每间隔1000个接收时刻确定1个时刻作为T1。
当第一通信装置用于中间节点时：
可选的，T1为第一通信装置在入口时隙位置上接收FGU时隙数据的时刻。示例性的，T1为第一通信装置接收第一个FGU时隙数据的时刻。可以理解的是，第一通信装置也可以选取其他FGU时隙数据的接收时刻作为T1，例如：T1为第一通信装置接收小颗粒业务的第10个FGU时隙数据的时刻，或者，T1为第一通信装置接收小颗粒业务的第50个FGU时隙数据的时刻，或者，T1为第一通信装置接收小颗粒业务的第100个FGU时隙数据的时刻，此处不作限制。
可选的，第一通信装置按照接收的FGU时隙数据的时隙数量，周期性的记录接收时刻，该接收时刻作为T1。例如：第一通信装置每接收1000个FGU时隙数据，记录一次接收时刻(如第1001个FGU时隙数据的接收时刻)，该接收时刻作为T1。
其次介绍T2，当第一通信装置用于源节点时：
可选的，T2为第一通信装置在出口时隙位置上发送FGU时隙数据的时刻。示例性的，T2为第一通信装置发送第一个FGU时隙数据的时刻，或者，T2为第一通信装置发送第50个FGU时隙数据的时刻等，此处不作限制。
可选的，T2为第一通信装置将包括特定比特位的业务容器映射至出口时隙位置的时刻。
可选的，T2为第一通信装置发送携带业务比特流中特定比特位的FGU时隙数据的时刻，该业务比特流中承载小颗粒业务。例如：T1为第一通信装置接收业务比特流中特定比特位的时刻，T2为第一通信装置发送携带该特定比特位的FGU时隙数据的时刻。
可选的，第一通信装置按照发送的FGU时隙数据的数量，周期性的记录发送时刻，该发送时刻作为T2。例如：第一通信装置每发送1000个FGU时隙数据，记录一次发送时刻(如第1001个FGU时隙数据的发送时刻)，该发送时刻作为T2。
可选的，第一通信装置发送FGU时隙数据时，每发送一个或多个FGU时隙数据记录一次发送时刻。然后周期性的选取发送时刻作为T2。例如：第一通信装置每发送1个FGU时隙数据，记录一次发送时刻。第一通信装置在每间隔1000个发送时刻确定1个时刻作为T2。
当第一通信装置用于中间节点时：
可选的，T2为第一通信装置发送小颗粒业务的第一个出口时隙位置的时刻。换言之，第一通信装置发送第一个承载小颗粒业务的出口时隙位置的时刻，或者，第一通信装置发送第一个FGU时隙数据的时刻。可以理解的是，第一通信装置也可以选取其他出口时隙位置的发送时刻作为T2，例如：T2为第一通信装置发送小颗粒业务的第10个出口时隙位置的时刻，或者，T2为第一通信装置发送小颗粒业务的第50个出口时隙位置的时刻，或者，T2为第一通信装置发送小颗粒业务的第100个出口时隙位置的时刻，此处不作限制。
可选的，第一通信装置按照发送的出口时隙位置(FGU时隙)的时隙数量，周期性的记录发送时刻，该发送时刻作为T2。例如：第一通信装置每发送1000个出口时隙位置(FGU时隙)，记录一次发送时刻(如第1001个FGU时隙数据的发送时刻)，该发送时刻作为T2。
进一步的，第一通信装置可以选取关联的T1和T2，计算第一传输时延，第一传输时延指示小颗粒业务在第一通信装置中的传输时延。
例如：T1为特定比特位的接收时刻，T2为承载特定比特位的FGU时隙数据的发送时刻；
又例如：T1为承载特定比特位的FGU时隙数据的接收时刻，T2为承载特定比特位的FGU时隙数据的发送时刻；
又例如：T1为业务比特流中第100个比特的接收时刻，T2为业务比特流中第100个比特的发送时刻；
又例如：T1为第50个接收时刻，T2为第50个发送时刻。
由于第一通信装置具体可用于源节点或者中间节点(图7示意的场景)，因此下面结合附图分别进行说明：
示例性的，(A)、当第一通信装置用于源节点时，为了便于理解源节点是如何确定小颗粒业务在源节点中的传输时延，请参阅图11，图11为本申请实施例中业务比特流中特定比特位的一种示意图。
业务比特流承载小颗粒业务，该业务比特流的第一个比特位设置为特定比特位。当源节点接收业务比特流的第一个比特位时，源节点记录该第一个比特位的接收时刻，该接收时刻作为T1。然后，源节点对业务比特流进行处理(例如图4～图5)，并映射到出口时隙位置。源节点通过物理接口在该出口时隙位置上发送FGU时隙数据。
示例性的，(B)、当第一通信装置用于中间节点时，为了便于理解中间节点是如何确定小颗粒业务在中间节点中的传输时延，请参阅图12，图12为本申请实施例中业务比特流 中特定比特位的一种示意图。
中间节点通过物理接口在入口时隙位置接收FGU时隙数据后，中间节点依据时隙交叉配置表，将入口时隙位置映射至出口时隙位置。时隙交叉配置表指示中间节点中入口时隙位置至出口时隙位置的映射规则。然后，中间节点通过物理接口在出口时隙位置上发送FGU时隙数据。在上述流程中，中间节点记录在入口时隙位置上接收该FGU时隙数据(承载特定比特位)的时刻，该时刻作为T1。中间节点记录在出口时隙位置上发送该FGU时隙数据(承载特定比特位)的时刻，该时刻作为T2。
902、第一通信装置向第二通信装置发送第一传输时延，第一传输时延指示小颗粒业务在第一通信装置中的传输时延。
本实施例中，当第一通信装置确定第一传输时延后，第一通信装置向第二通信装置发送第一传输时延，以便第二通信装置获取第一传输时延。
下面针对不同的场景，介绍第一通信装置具体向第二通信装置发送第一传输时延的方案：
对于(1.1)方案：当第一通信装置用于源节点和/或中间节点，第二通信装置用于宿节点时，第一通信装置接收来自上一跳节点的第二传输时延，所述第二传输时延指示所述小颗粒业务从源节点至所述上一跳节点的传输时延。具体的，当上一跳节点是其他中间节点时，所述第二传输时延指示所述小颗粒业务从源节点至所述上一跳节点的传输时延。所述第一通信装置向下一跳节点发送所述第一传输时延和所述第二传输时延。
本申请实施例中，为了便于区分，将第一通信装置的传输时延分为第一传输时延和第二传输时延，其中，将自身节点的传输时延称为第一传输时延，将来自上一跳节点的传输时延称为第二传输时延。
可选的，第一通信装置通过时延收集消息，向第二通信装置发送第一传输时延。第一通信装置接收来自上一跳节点的时延收集信息后，将自身测量得到的第一传输时延填充至该时延收集消息。当第一通信装置的上游还包括其他节点时，第一通信装置接收来自上一跳节点的时延收集消息，该时延收集消息中包括第二传输时延。然后，第一通信装置更新该时延收集消息，更新后的时延收集消息中包括第一传输时延和第二传输时延。第一通信装置向第二通信装置(或者其他的下游节点)发送该更新后的时延收集消息。
示例性的，时延收集消息存在多种可能的实现方式，包括但不限于：消息(message)、报文、报文头的新增字段、比特信息(包括多个比特位)、或者类型长度值(type length value，TLV)信息等。
可选的，该时延收集消息还包括路径信息，该路径信息指示的时延收集消息的传输路径。该路径信息包括一个或多个节点的转发信息。例如，该转发信息包括但不限于：上一跳节点和/或下一跳节点的端口号，或者，上一跳节点和/或下一跳节点的介质访问控制(Media Access Control，MAC)地址，或者，上一跳节点和/或下一跳节点的互联网协议(Internet Protocol，IP)地址，或者上一跳节点和/或下一跳节点的小颗粒通道(channel)号等。
该路径信息所指示的节点需要在时延收集消息中填充自身节点的第一传输时延。第一通信装置根据路径信息，确定目的节点(即接收该时延收集消息的下一跳节点)。然后第一通信装置向目的节点发送时延收集消息，该时延收集消息中携带第一通信装置的第一传输时延。目的节点接收该时延收集消息后，目的节点将自身的第一传输时延填充至该时延收集消息。目的节点根据路径信息的指示，确定接收该更新后的时延收集消息的下一跳节点。然后，目的节点向该下一跳节点发送该更新后的时延收集消息。
可选的，对于接收该时延收集消息的第一通信装置，通过检测自身的地址信息是否与该路径信息所包括的地址信息匹配，确定是否处理该时延收集消息。若匹配，则第一通信装置将自身的第一传输时延填充至该时延收集消息；若不匹配，则第一通信装置直接转发该时延收集消息，或者，第一通信装置丢弃该时延收集消息，或者，第一通信装置根据路径信息的指示确定下一跳节点，然后第一通信装置向下一跳节点转发该时延收集消息。
为了便于理解，请参阅图22，图22为本申请实施例中时延收集消息的转发示意图。图22示意的场景包括：源节点、中间节点a～中间节点g和宿节点。以时延收集消息包括的路径信息是表1为例：
表1
源节点获取源节点的第一传输时延后，将源节点的第一传输时延填充至时延收集消息。然后源节点向下游的其他节点发送该时延收集消息。
对于中间节点f，由于自身的端口号与路径信息不匹配，因此中间节点f直接丢弃接收的时延收集消息。对于中间节点c，由于自身的端口号与路径信息不匹配，则直接丢弃接收的时延收集消息。
对于中间节点a，由于自身的端口号(AAA)与路径信息相匹配，则中间节点a更新该时延收集消息，具体的更新方式如下：在时延收集消息中填充中间节点a的第一传输时延。然后，中间节点a向下游的其他节点发送更新后的时延收集消息。以此类推，使得宿节点接收到的时延收集消息中包括：源节点的第一传输时延，中间节点a的第一传输时延，中间节点d的第一传输时延和中间节点e的第一传输时延。
可选的，所述第二传输时延包括：所述小颗粒业务从所述源节点传输至所述上一跳节点所经过的每个节点的传输时延。示例性的，对于中间节点n-1，n为大于2的正整数。中间节点n-1向中间节点n发送的第二传输时延包括：前n个节点(从源节点起至中间节点n-2，共n-1个节点)的第一传输时延之和。例如：n＝3，源节点的第一传输时延为5毫秒，中间节点1的第一传输时延为2毫秒，中间节点2的第一传输时延为3毫秒。中间节点3 接收来自中间节点1的第二传输时延为{5,2}，其中，“5”指示小颗粒业务在源节点的传输时延为5毫秒，“2”指示小颗粒业务在中间节点1的传输时延为2毫秒。
可选的，所述第二传输时延包括：所述小颗粒业务从所述源节点传输至所述上一跳节点所经过的每个节点的传输时延之和。例如：n＝3，源节点的第一传输时延为5毫秒，中间节点1的第一传输时延为2毫秒，中间节点2的第一传输时延为3毫秒。中间节点3接收来自中间节点2的第二传输时延为“7”，其中，“7”指示小颗粒业务从源节点传输至中间节点1的传输时延之和为7毫秒，即源节点的第一传输时延和中间节点1的第一传输时延之和为7毫秒。
为了便于理解，请参阅图14，图14为本申请实施例中传输时延的一种场景示意图。图14示意的场景中包括源节点、P个中间节点和宿节点，其中，P为大于3的正整数。源节点获取自身的第一传输时延后，向下一跳节点(例如是中间节点1)发送第一传输时延。
中间节点1获取来自源节点的第二传输时延(即源节点的第一传输时延)后，中间节点1将自身的第一传输时延和来自源节点的第二传输时延发送至下一跳节点(例如中间节点2)。
中间节点2获取来自中间节点1的第二传输时延(来自中间节点1的第二传输时延包括：中间节点1的第一传输时延和源节点的第一传输时延)后，中间节点2将自身的第一传输时延和来自中间节点1的第二传输时延发送至下一跳节点(例如中间节点3)。
以此类推，如图14中，中间节点P-1向中间节点P发送的第二传输时延，包括源节点至中间节点P-2共P-1个节点的第一传输时延。中间节点P-1接收来自上一跳节点(中间节点P-1)的第二传输时延后，向中间节点P发送第二传输时延和中间节点P-1的第一传输时延。
对于(1.2)方案：第一通信装置用于源节点和/或中间节点，第二通信装置用于宿节点或者网络管理设备时，请参阅图15，图15为本申请实施例中传输时延的又一种场景示意图。图15示意的场景中包括源节点、n个中间节点、宿节点和网络管理设备，其中，网络管理设备与上述源节点、n个中间节点和宿节点连接，网络管理设备负责管理控制上述各个节点，n为大于1的正整数。上述各个节点将小颗粒业务在自身的传输时延上报至网络管理设备，例如图15示意的：源节点测量得到第一传输时延后，将源节点的第一传输时延上报至网络管理设备；中间节点n-1测量得到第一传输时延后，将中间节点n-1的第一传输时延上报至网络管理设备；中间节点n测量得到第一传输时延后，将中间节点n的第一传输时延上报至网络管理设备；宿节点测量得到宿节点的传输时延后，将宿节点的传输时延上报至网络管理设备。
可选的，第二通信装置(网络管理设备)与源节点、中间节点和宿节点之间基于网络配置协议(Network Configuration Protocol，NETCONF)建立通信连接。需要说明的是，本申请实施例中，第二通信装置(网络管理设备)与源节点、中间节点和宿节点之间还可以基于其他协议建立通信连接，此处不作限制。
903、第二通信装置获取小颗粒业务在宿节点中的传输时延。
本实施例中，当第二通信装置用于宿节点时，第二通信装置检测并确定小颗粒业务在第二通信装置中的传输时延；当第二通信装置用于网络管理设备时，第二通信装置从宿节点获取小颗粒业务在宿节点中的传输时延。
示例性的，当第二通信装置用于宿节点时，为了便于理解宿节点是如何确定小颗粒业务在宿节点中的传输时延，请参阅图13，图13为本申请实施例中业务比特流中特定比特位的一种示意图。宿节点在入口时隙位置上接收承载小颗粒业务的时隙，也就是宿节点接收FGU时隙数据。在上述过程中，宿节点接收到的FGU时隙数据包括特定比特位时，宿节点记录接收该包括特定比特位的FGU时隙数据的时刻。然后，宿节点对FGU时隙数据进行处理，得到业务比特流(例如图4～图5)。宿节点发送业务比特流时，宿节点记录发送业务比特流中特定比特位的时刻。宿节点依据接收携带特定比特位的FGU时隙数据的时刻，和发送业务比特流中特定比特位的时刻，确定小颗粒业务在宿节点的传输时延。
又一种示例中，所述第二通信装置通过以下方式计算得到所述小颗粒业务在所述宿节点中的传输时延，包括：
Node’delay＝T4-T3；
其中，Node’delay为所述小颗粒业务在所述宿节点中的传输时延，T3为第三时刻，所述第三时刻为所述宿节点接收FGU时隙数据的时刻，该FGU时隙数据承载所述小颗粒业务的业务比特流中特定比特位，T4为第四时刻，第四时刻为所述宿节点对所述FGU时隙数据(该FGU时隙数据包括特定比特位)承载的业务容器解封装的时刻，所述业务容器承载所述特定比特位。
可选的，T3为宿节点接收承载小颗粒业务的时隙数据的时刻。该FGU时隙数据承载小颗粒业务对应的数据。换言之，T3还可以称为宿节点接收FGU时隙数据的时刻。需要说明的是，T3例如：T3为宿节点接收第一个FGU时隙数据的时刻，或者，T3为宿节点接收第50个FGU时隙数据的时刻等，此处不作限制。
可选的，T3为宿节点在入口时隙位置接收携带业务比特流中特定比特位的FGU时隙数据的时刻，该业务比特流中承载小颗粒业务。例如：T1为宿节点接收业务比特流中特定比特位的时刻，T3为宿节点接收携带该特定比特位的FGU时隙数据的时刻。
可选的，宿节点按照接收的入口时隙位置(FGU时隙)的数量，周期性的记录接收时刻，该接收时刻作为T3。例如：宿节点每接收1000个FGU时隙数据，记录一次接收时刻(如第1001个FGU时隙数据的接收时刻)，该接收时刻作为T3。
可选的，宿节点在入口时隙位置接收FGU时隙数据时，每接收一个或多个FGU时隙数据记录一次接收时刻。然后周期性的选取接收时刻作为T3。例如：宿节点每接收1个FGU时隙数据，记录一次接收时刻。宿节点在每间隔1000个接收时刻确定1个接收时刻作为T3。
可选的，T4为宿节点发送承载小颗粒业务的业务比特流中特定比特位的时刻。例如：选取业务比特流中的第1个比特位作为特定比特位，当宿节点发送到该业务比特流的第1个比特位时，宿节点记录发送第1个比特位的发送时刻。该第1个比特位的发送时刻作为 T4。该特定比特位可以根据实际情况选取，例如：该特定比特位可以是业务比特流的第1个比特、第100个比特、第200个比特、第500个比特、和/或第1000个比特等。
可选的，宿节点按照发送的业务比特流的比特数量，周期性的记录发送时刻，该发送时刻作为T4。例如：宿节点每发送1000个比特，记录一次发送时刻(如第1001个比特的发送时刻)，该发送时刻作为T4。
可选的，宿节点发送业务比特流时，每个一个或多个比特记录一次发送时刻。然后周期性的选取发送时刻作为T4。例如：宿节点每发送1个比特，记录一次发送时刻。宿节点在每间隔1000个发送时刻确定1个时刻作为T4。
当第二通信装置用于网络管理设备时，由网络管理设备为源节点、中间节点和宿节点配置上报传输时延的路径，例如基于NETCONF协议进行配置。然后，网络管理设备从源节点、中间节点和宿节点中获取小颗粒业务在各个节点内的传输时延。
904、第二通信装置根据端到端的目标时延，第一传输时延和小颗粒业务在宿节点中的传输时延，确定时延补偿值。
本实施例中，第二通信装置获取端到端的目标时延，端到端的目标时延大于或等于以下两种传输时延值中最大的一项：第一方向的业务传输时延值或者第二方向的业务传输时延值，其中，所述第一方向为：从源节点至所述宿节点；所述第二方向为：从所述宿节点至所述源节点。
端到端的目标时延可以是预配置于第二通信装置，也可以是基于实际测量得到的第一方向上传输时延值和第二方向上传输时延值计算得到，此处不作限制。例如：第一方向的传输时延值为500毫秒，第二方向的传输时延值为450毫秒，则端到端的目标时延设置为500毫秒。
然后，第二通信装置根据端到端的目标时延，第一传输时延和小颗粒业务在宿节点中的传输时延，确定时延补偿值。示例性的，所述第二通信装置通过以下方式计算得到所述时延补偿值，包括：
其中，Δ为所述时延补偿值，Targetdelay1为所述端到端的目标时延，为前n跳所述第一通信装置的所述第一传输时延，所述第一通信装置用于所述源节点或者中间节点，n为所述源节点和所述中间节点的节点数量，Node’delay为所述小颗粒业务在所述宿节点中传输时延。
当第二通信装置用于宿节点时，进入步骤905；当第二通信装置用于网络管理设备时，第二通信装置(网络管理设备)向宿节点发送时延补偿值，由宿节点根据时延补偿值对小颗粒业务进行时延补偿，具体的补偿方法与步骤905类似。
905、第二通信装置根据时延补偿值，对小颗粒业务进行时延补偿。
本实施例中，第二通信装置(宿节点)在入口时隙位置上接收FGU时隙数据后，所述第二通信装置将FGU时隙数据进行解映射，得到业务容器，所述业务容器承载所述小颗粒 业务的业务比特流；然后，所述第二通信装置对所述业务容器进行解封装，得到业务切片，所述业务切片承载所述小颗粒业务；所述第二通信装置将所述业务切片存储至存储器；当所述业务切片在所述存储器中的驻留时间到达所述时延补偿值，所述第二通信装置从所述存储器中提取所述业务切片；所述第二通信装置根据多个所述业务切片，重组得到所述业务比特流；所述第二通信装置发送所述业务比特流。
具体的，第二通信装置将得到的业务切片存储至存储器中，该存储器可以是位于第二通信装置内的存储器，该存储器也可以是与第二通信装置相互独立的存储器，此处不作限制。当第二通信装置将业务切片存储至存储器后，第二通信装置启动计时器。当计时器的时间到达时延补偿值时，意味着存储器中业务切片的驻留时间到达时延补偿值。第二通信装置从存储器中提取业务切片，然后基于多个业务切片进行业务重组，得到对应的业务比特流。第二通信装置在物理接口上发送该业务比特流，实现小颗粒业务的时延补偿。
本申请实施例中，通过采集各个节点中小颗粒业务的传输时延，然后结合端到端的目标时延计算得到端到端的时延补偿值。在宿节点中，将小颗粒业务对应的业务切片缓存。直到该业务切片的驻留时间到达端到端的时延补偿值时，宿节点从缓存中提取业务切片进行重组得到业务比特流，然后发送该业务比特流。通过上述方法，实现端到端的时延补偿，确保宿节点发出的业务比特流满足时延补偿要求，进而保证小颗粒业务网络中从源节点到宿节点的网络传输时延与宿节点到源节点的网络传输时延相等或者满足预期的误差范围，或者使得源节点到宿节点的网络传输时延与宿节点到源节点的网络传输时延调整至预期值，以满足业务要求。示例性的，当电网系统应用本申请实施例提出的时延补偿方法时，可以确保任意两个终端设备之间信息采集的时刻一致，从而提升电力系统执行继电保护业务的准确性。电网系统中的终端设备，包括但不限于：继电保护装置、电源管理单元、数据传输单元、电表、开关、发电装置，或者变电装置等。电网系统中各个终端设备采集的信息包括但不限于：电压、电流或者电压频率等。
结合前述实施例，下面结合附图详细说明(1.1)、网络管理设备不参与时延补偿；(1.2)、网络管理设备参与时延补偿。
首先，(1.1)、网络管理设备不参与时延补偿：请参阅图16，图16为本申请实施例中一种应用场景示意图。
源节点接收业务比特流后，源节点对业务比特流进行处理并映射至出口时隙位置，包括：对业务比特流进行切片，得到多个业务切片；然后对业务切片进行封装处理，得到业务容器；将业务容器映射到出口时隙位置：具体的，源节点将业务容器映射到码块流。然后对码块流进行分割处理得到FGU数据时隙。最后，源节点通过以太接口或者灵活以太客户(flexible ethernet client，FlexE Client)接口在出口时隙位置上发送FGU时隙数据。本申请实施例中将承载小颗粒业务的时隙数据称为FGU时隙数据。
在上述流程中，源节点记录源节点的第一时刻(t1)，和源节点的第二时刻(t2)，然后源节点根据第一时刻和第二时刻确定源节点的第一传输时延(Node_delay1＝t2-t1)。源节点基于该源节点的第一传输时延，更新所生成的时延收集消息。更新后的时延收集消息 中记录源节点的第一传输时延。然后源节点向下一跳节点(中间节点)发送更新后的时延收集消息。
中间节点通过物理接口在入口时隙位置接收FGU时隙数据后，中间节点依据时隙交叉配置表，将入口时隙位置映射至出口时隙位置。时隙交叉配置表指示中间节点中入口时隙位置至出口时隙位置的映射规则。然后，中间节点通过物理接口在出口时隙位置上发送FGU时隙数据。
在上述流程中，中间节点记录中间节点的第一时刻(t3)，和中间节点的第二时刻(t4)，然后中间节点根据第一时刻和第二时刻确定中间节点的第一传输时延(Node_delay2＝t4-t3)。中间节点基于该中间节点的第一传输时延，更新来自上一跳节点的时延收集消息。更新后的时延收集消息中记录中间节点的第一传输时延。然后中间节点向下一跳节点发送更新后的时延收集消息。
宿节点通过物理接口在入口时隙位置上接收FGU时隙数据。然后，宿节点对FGU时隙数据解映射处理，得到对应的业务容器。进一步的，宿节点将业务容器进行解封装处理，得到对应的业务切片。宿节点将业务切片缓存到存储器中，等待时延补偿。
在上述流程中，宿节点记录第三时刻(t5)和第四时刻(t6)，然后，宿节点根据第三时刻和第四时刻，计算得到小颗粒业务在宿节点中的传输时延(Node_delay3＝t6-t5)。宿节点通过来自上一跳节点的时延收集消息，获取小颗粒业务从源节点到上一跳节点的传输时延。宿节点获取端到端的目标时延。最后，宿节点基于：源节点的第一传输时延(Node_delay1)，中间节点的第一传输时延(Node_delay2)、小颗粒业务在宿节点的传输时延(Node_delay3)，和端到端的目标时延，计算得到时延补偿值。宿节点的存储器中业务切片的驻留时间到达时延补偿值后，宿节点提取业务切片。然后宿节点基于多个业务切片进行业务重组，得到业务比特流。最后，宿节点在物理接口上发送该业务比特流。
通过上述方法，确保宿节点发出的业务比特流满足时延补偿要求，进而保证小颗粒业务网络中从源节点到宿节点的网络传输时延与宿节点到源节点的网络传输时延相等或者满足预期的误差范围，或者使得源节点到宿节点的网络传输时延与宿节点到源节点的网络传输时延调整至预期值，以满足业务要求。
(1.2)、网络管理设备参与时延补偿。请参阅图17，图17为本申请实施例中又一种应用场景示意图。
源节点接收业务比特流后，源节点对业务比特流进行处理并映射至出口时隙位置，包括：对业务比特流进行切片，得到多个业务切片；然后对业务切片进行封装处理，得到业务容器；将业务容器映射到出口时隙位置：具体的，源节点将业务容器映射到码块流。然后对码块流进行分割处理得到FGU数据时隙。最后，源节点通过以太接口或者灵活以太客户(flexible ethernet client，FlexE Client)接口在出口时隙位置上发送FGU时隙数据。本申请实施例中将承载小颗粒业务的时隙数据称为FGU时隙数据。
在上述流程中，源节点记录源节点的第一时刻(t1)，和源节点的第二时刻(t2)，然后源节点根据第一时刻和第二时刻确定源节点的第一传输时延(Node_delay1＝t2-t1)。源 节点将该源节点的第一传输时延上传至网络管理设备。
中间节点通过物理接口在入口时隙位置接收FGU时隙数据后，中间节点依据时隙交叉配置表，将入口时隙位置映射至出口时隙位置。时隙交叉配置表指示中间节点中入口时隙位置至出口时隙位置的映射规则。然后，中间节点通过物理接口在出口时隙位置上发送FGU时隙数据。
在上述流程中，中间节点记录中间节点的第一时刻(t3)，和中间节点的第二时刻(t4)，然后中间节点根据第一时刻和第二时刻确定中间节点的第一传输时延(Node_delay2＝t4-t3)。中间节点将该中间节点的第一传输时延上传至网络管理设备。
宿节点通过物理接口在入口时隙位置上接收FGU时隙数据。然后，宿节点对FGU时隙数据解映射处理，得到对应的业务容器。进一步的，宿节点将业务容器进行解封装处理，得到对应的业务切片。宿节点将业务切片缓存到存储器中，等待时延补偿。
在上述流程中，宿节点记录第三时刻(t5)和第四时刻(t6)，然后，宿节点根据第三时刻和第四时刻，计算得到小颗粒业务在宿节点中的传输时延(Node_delay3＝t6-t5)。
可选的，宿节点将Node_delay3上传至网络管理设备。由网络管理设备根据Node_delay1、Node_delay2、Node_delay3和端到端的目标时延，计算得到时延补偿值。然后宿节点接收该时延补偿值，宿节点基于该时延补偿值进行时延补偿。具体时延补偿方法与前述图16示意的方法类似，此处不作赘述。
可选的，宿节点生成Node_delay3后，请求网络管理设备下发Node_delay1和Node_delay2。宿节点根据Node_delay1、Node_delay2、Node_delay3和端到端的目标时延，计算得到时延补偿值。然后宿节点基于该时延补偿值进行时延补偿。在这种可能的实现方式中，端到端的目标时延可以由网络管理设备配置，也可以是预配置的，此处不作限制。
通过上述方法，确保宿节点发出的业务比特流满足时延补偿要求，进而保证小颗粒业务网络中从源节点到宿节点的网络传输时延与宿节点到源节点的网络传输时延相等或者满足预期的误差范围，或者使得源节点到宿节点的网络传输时延与宿节点到源节点的网络传输时延调整至预期值，以满足业务要求。
其次，介绍(2)、逐节点的时延补偿。请参阅图10，图10为本申请实施例中时延补偿方法的一种实施例示意图。本申请实施例提出的一种时延补偿方法，包括：
1001、通信装置确定小颗粒业务在通信装置中的传输时延。
本实施例中，通信装置确定小颗粒业务在通信装置(也就是自身节点)中的传输时延。
具体的，当通信装置用于源节点时，所述通信装置获取第一接收时刻，所述第一接收时刻为所述源节点接收承载所述小颗粒业务的业务比特流中特定比特位的时刻；所述通信装置获取第二发送时刻，所述第二发送时刻为所述源节点发送承载所述特定比特位的FGU时隙数据的时刻；所述通信装置将所述第二发送时刻减去所述第一接收时刻，得到所述小颗粒业务在所述源节点中的传输时延。
关于通信装置获取第一接收时刻的可能方式，与前述源节点获取第一时刻的方式类似，此处不作赘述；关于通信装置获取第二发送时刻，与前述源节点获取第二时刻类似，此处 不做赘述。
具体的，当通信装置用于中间节点时，所述通信装置获取第三接收时刻，所述第三接收时刻为所述中间节点接收FGU时隙数据的时刻，所述FGU时隙数据承载所述小颗粒业务的业务比特流中特定比特位；所述通信装置获取第四发送时刻，所述第四发送时刻为所述中间节点发送所述FGU时隙数据的时刻，所述业务比特流承载小颗粒业务；所述通信装置将所述第四发送时刻减去所述第三接收时刻，得到所述小颗粒业务在所述中间节点中的传输时延。
具体的，通信装置在入口时隙位置接收FGU时隙数据。然后，通信装置基于时隙交叉映射表的指示将入口时隙位置上接收的FGU时隙数据，映射至出口时隙位置。最后，通信装置通过物理接口在出口时隙位置上发送FGU时隙数据。
关于通信装置获取第三接收时刻的可能方式，与前述中间节点获取第一时刻的方式类似，此处不作赘述；关于通信装置获取第四发送时刻，与前述中间节点获取第二时刻类似，此处不做赘述。
具体的，当通信装置用于宿节点时，所述通信装置获取第五接收时刻，所述第五接收时刻为所述宿节点接收承载所述小颗粒业务的业务比特流中特定比特位的FGU时隙数据的时刻；所述通信装置获取第六发送时刻，所述第六发送时刻为所述宿节点将业务容器解封装的时刻，所述业务容器为所述通信装置对所述FGU时隙数据解映射得到，所述业务容器承载所述特定比特位；所述通信装置将所述第六发送时刻减去所述第五接收时刻，得到所述小颗粒业务在所述宿节点中的传输时延。
所述通信装置将所述FGU时隙数据进行解映射，得到所述业务容器；然后，通信装置对业务容器进行解封装处理，得到业务切片。此时，通信装置记录解封装得到业务切片的时刻为第六发送时刻。
关于通信装置获取第五接收时刻的可能方式，与前述宿节点获取第三时刻的方式类似，此处不作赘述；关于通信装置获取第六发送时刻，与前述中间节点获取第四时刻类似，此处不做赘述。
为了便于理解，请参阅图18，图18为本申请实施例中一种测量传输时延的示意图。小颗粒业务的通信场景下，每个节点获取小颗粒业务在自身节点的传输时延。本申请实施例中，将小颗粒业务在源节点的接收时刻称为第一接收时刻，将小颗粒业务在源节点的发送时刻称为第二发送时刻；将小颗粒业务在中间节点的接收时刻称为第三接收时刻，将小颗粒业务在中间节点的发送时刻称为第四发送时刻；将小颗粒业务在宿节点的接收时刻称为第五接收时刻，将小颗粒业务在宿节点的发送时刻称为第六发送时刻。
1002、通信装置根据节点的目标时延和小颗粒业务在通信装置中的传输时延，对小颗粒业务进行时延补偿。
本实施例中，通信装置获取小颗粒业务在通信装置中的传输时延后，通信装置根据节点的目标时延和该传输时延，计算节点的时延补偿值。然后通信装置根据该节点的时延补偿值，在通信装置(自身节点)内进行小颗粒业务的时延补偿，实现逐节点的时延补偿。
具体的，节点的目标时延包括：源节点的目标时延、中间节点的目标时延，和/或宿节 点的目标时延。
可选的，源节点的目标时延、中间节点的目标时延和宿节点的目标时延满足：源节点的目标时延、中间节点的目标时延和宿节点的目标时延之和，大于或者等于以下两种传输时延值中最大的一项：第一方向的业务传输时延值或者第二方向的业务传输时延值，其中，所述第一方向为：从源节点至所述宿节点；所述第二方向为：从所述宿节点至所述源节点。该业务传输时延值可以是：承载小颗粒业务的业务比特流在源节点至宿节点之间的多个通信装置的传输时延值。
可选的，网络管理设备为每个节点配置对应的目标时延。其中，源节点的目标时延范围可以是：0～100微秒；中间节点的目标时延范围可以是：10～20微秒；宿节点的目标时延访问可以是：宿节点：100～500微秒。
具体的，当通信装置用于源节点时，所述源节点根据所述时延补偿值，对所述小颗粒业务进行时延补偿，包括：源节点接收业务比特流后，源节点对业务比特流进行处理并映射至出口时隙位置，包括：对业务比特流进行切片，得到多个业务切片；然后对业务切片进行封装处理，得到业务容器；将业务容器映射到出口时隙位置：具体的，源节点将业务容器映射到码块流。然后对码块流进行分割处理得到FGU数据时隙；所述源节点将FGU时隙数据存储至存储器，FGU时隙数据承载所述小颗粒业务的业务比特流；当所述源节点的FGU时隙数据在所述存储器中的驻留时间到达所述时延补偿值，所述源节点从所述存储器中提取所述源节点的FGU时隙数据；所述源节点在出口时隙位置上发送所述源节点的FGU时隙数据。
具体的，当通信装置用于中间节点时，所述中间节点根据所述时延补偿值，对所述小颗粒业务进行时延补偿，包括：所述中间节点在入口时隙位置接收FGU时隙数据，所述FGU时隙数据承载所述小颗粒业务的业务比特流；所述中间节点将所述中间节点的入口时隙位置交叉至所述中间节点的出口时隙位置；所述中间节点将所述FGU时隙数据存储至存储器；当所述FGU时隙数据在所述存储器中的驻留时间到达所述时延补偿值，所述中间节点从所述存储器中提取所述FGU时隙数据；所述中间节点在所述中间节点的出口时隙位置发送所述FGU时隙数据。
具体的，当通信装置用于宿节点时，所述宿节点根据所述时延补偿值，对所述小颗粒业务进行时延补偿，包括：所述宿节点将所述FGU时隙数据进行解映射，得到业务容器，所述业务容器承载所述小颗粒业务的业务比特流；所述宿节点对所述业务容器进行解封装，得到业务切片，所述业务切片承载所述小颗粒的业务比特流；所述宿节点将所述业务切片存储至存储器；当所述业务切片在所述存储器中的驻留时间到达所述时延补偿值，所述宿节点从所述存储器中提取所述业务切片；所述宿节点根据多个所述业务切片，重组得到所述业务比特流；所述宿节点发送所述业务比特流。
本申请实施例中，通过上述方法，确保每个节点发出的业务比特流满足时延补偿要求，进而保证小颗粒业务网络中从源节点到宿节点的网络传输时延与宿节点到源节点的网络传输时延相等或者满足预期的误差范围，或者使得源节点到宿节点的网络传输时延与宿节点到源节点的网络传输时延调整至预期值，以满足业务要求。
为了便于理解，下面结合附图详细说明(2)、逐节点的时延补偿。请参阅图19，图19为本申请实施例中又一种应用场景示意图。
首先介绍源节点的时延补偿：
源节点接收业务比特流后，源节点对业务比特流进行处理并映射至出口时隙位置，包括：对业务比特流进行切片，得到多个业务切片；然后对业务切片进行封装处理，得到业务容器；将业务容器映射到出口时隙位置上，所述出口时隙位置上承载的数据为FGU时隙数据。源节点将所述源节点的所述FGU时隙数据存储至存储器，所述源节点的FGU时隙数据对应所述小颗粒业务的业务比特流。
在上述流程中，源节点记录源节点的第一接收时刻(t1)，和源节点的第二发送时刻(t2)，然后源节点根据第一接收时刻和第二发送时刻确定小颗粒业务在源节点中的传输时延(Node_delay1＝t2-t1)。最后，源节点基于小颗粒业务在源节点中的传输时延和源节点的目标时延，计算得到源节点的时延补偿值。
当所述源节点的FGU时隙数据在所述存储器中的驻留时间到达所述源节点的时延补偿值，所述源节点从所述存储器中提取所述源节点的FGU时隙数据；所述源节点通过物理接口(例如以太接口或者灵活以太客户(flexible ethernet client，FlexE Client)接口)在出口时隙位置发送所述源节点的FGU时隙数据。
其次，介绍中间节点的时延补偿：
可选的，中间节点在入口时隙位置上接收FGU时隙数据。中间节点将所接收的FGU时隙数据存储至存储器中。当FGU时隙数据在存储器中的驻留时间到达中间节点的时延补偿值后，中间节点从存储器中提取FGU时隙数据。然后，中间节点根据时隙交叉配置表，将入口时隙位置映射至出口时隙位置上。最后，中间节点通过物理接口在出口时隙位置中发送FGU时隙数据。
可选的，中间节点在入口时隙位置上接收FGU时隙数据。中间节点根据时隙交叉配置表，将入口时隙位置映射至出口时隙位置上。然后，中间节点可以将FGU时隙数据存储至存储器中。当FGU时隙数据在存储器中的驻留时间到达中间节点的时延补偿值后，中间节点从存储器中提取FGU时隙数据。最后，中间节点通过物理接口在出口时隙位置中发送FGU时隙数据。
在上述流程中，中间节点记录中间节点的第三接收时刻(t3)，和中间节点的第四发送时刻(t4)，然后中间节点根据第三接收时刻和第四发送时刻确定小颗粒业务在中间节点中的传输时延(Node_delay2＝t4-t3)。最后，中间节点基于小颗粒业务在中间节点中的传输时延和中间节点的目标时延，计算得到中间节点的时延补偿值。
最后，介绍宿节点的时延补偿：
宿节点在入口时隙位置上接收FGU时隙后，宿节点对FGU时隙进行解映射处理，得到对应的业务容器；然后，宿节点对业务容器进行解封装处理，得到业务切片；宿节点将业务切片缓存到存储器中，等待时延补偿。
在上述流程中，宿节点记录第五接收时刻(t5)和第六发送时刻(t6)，然后，宿节点 根据第五接收时刻和第六发送时刻，计算得到小颗粒业务在宿节点中的传输时延(Node_delay3＝t6-t5)。宿节点基于：小颗粒业务在宿节点的传输时延(Node_delay3)，和宿节点的目标时延，计算得到宿节点的时延补偿值。宿节点的存储器中业务切片的驻留时间到达宿节点的时延补偿值后，宿节点提取业务切片。然后宿节点基于多个业务切片进行业务重组，得到业务比特流。最后，宿节点在物理接口上发送该业务比特流。
结合前述实施例，可选的，对于中间节点还存在另一种时延补偿方法：通过计算得到入口时隙位置中的FGU时隙数据(下面简称为入口时隙)的时隙标识或者出口时隙位置中的FGU时隙数据(下面简称为出口时隙)的时隙标识，然后根据计算得到的入口时隙的时隙标识和出口时隙的时隙标识，调整时隙交叉映射表。使得中间节点可以根据调整后的时隙交叉映射表，将中间节点在入口时隙位置接收的FGU时隙数据映射到出口时隙位置，实现向下一跳节点转发来自上一跳节点的小颗粒业务。按照调整后的时隙交叉映射表转发FGU时隙数据，可以确保中间节点转发的FGU时隙数据满足时延补偿要求。具体的时延补偿方法如下：
A1、中间节点根据出口时隙的时隙标识、入口时隙的复帧指示，和出口时隙的复帧指示，得到入口时隙的时隙标识。为了便于理解，请参阅图20，图20为本申请实施例中时延补偿方法的又一种实施例示意图。所述中间节点根据所述节点的目标时延和所述小颗粒业务在所述中间节点中的传输时延，对所述小颗粒业务进行时延补偿，包括：
所述中间节点获取出口时隙的时隙标识，入口时隙的复帧指示对应的相位、出口时隙的复帧指示对应的相位，其中，所述入口时隙为所述中间节点接收承载所述小颗粒业务的时隙，所述出口时隙为所述中间节点发送承载所述小颗粒业务的时隙；
所述中间节点根据所述节点的目标时延、所述出口时隙的时隙标识，所述入口时隙的复帧指示对应的相位、所述出口时隙的复帧指示对应的相位、复帧周期和时隙间隔，计算得到所述入口时隙的时隙标识，所述复帧周期为所述出口时隙或者所述入口时隙中每个复帧的传输时延，所述时隙间隔为所述出口时隙或者所述入口时隙中每个时隙的传输时延。示例性的，以5G FlexE client接口为例，则复帧周期为50.688微秒(us)，时隙间隔为50.688/480≈0.1056微秒；
所述中间节点根据所述入口时隙的时隙标识和所述出口时隙的时隙标识，向下一跳节点转发来自上一跳节点的所述小颗粒业务。具体的，中间节点根据计算得到的入口时隙的时隙标识，更新入口时隙表。后续中间节点依据更新后的入口时隙表，在入口时隙上接收来自上一跳节点的FGU时隙。中间节点可以将入口时隙(FGU时隙)按照时隙交叉配置表映射至出口时隙上。最终，中间节点将出口时隙(FGU时隙)映射到物理接口中，向下一跳节点发送该FGU时隙。
示例性的，通过以下方式计算得到所述入口时隙的时隙标识：
其中，RxSlotId为所述入口时隙的时隙标识，Targetdelay2为所述节点的目标时延，RxMFI为所述入口时隙的复帧指示对应的相位，TxMFI为所述出口时隙的复帧指示对应的相位， MF period为所述复帧周期，slot time为所述时隙间隔，TxSlotId为所述出口时隙的时隙标识，K为中间节点中时隙交叉所需的最小时延值。
具体的，RxMFI为所述入口时隙的复帧指示对应的相位，中间节点根据入口时隙的复帧帧头获取RxMFI；TxMFI为所述出口时隙的复帧指示对应的相位，中间节点根据出口时隙中的复帧帧头获取TxMFI。(RxMFI-TxMFI)指的是复帧帧头的相位差，可以由入口时隙的MFI的接收时刻(InMFI-Timestamp)减去出口时隙中的MFI的发送时刻(OutMFI-Timestamp)得到。
A2、中间节点根据入口时隙的时隙标识、入口时隙的复帧指示，和出口时隙的复帧指示，得到出口时隙的时隙标识。为了便于理解，请参阅图21，图21为本申请实施例中时延补偿方法的又一种实施例示意图。
所述中间节点根据所述节点的目标时延和所述小颗粒业务在所述中间节点中的传输时延，对所述小颗粒业务进行时延补偿，包括：
所述中间节点获取入口时隙的时隙标识，入口时隙的复帧指示对应的相位、出口时隙的复帧指示对应的相位，其中，所述入口时隙为所述中间节点接收承载所述小颗粒业务的时隙，所述出口时隙为所述中间节点发送承载所述小颗粒业务的时隙；
所述中间节点根据所述节点的目标时延、所述入口时隙的时隙标识，所述入口时隙的复帧指示对应的相位、所述出口时隙的复帧指示对应的相位、复帧周期和时隙间隔，计算得到所述出口时隙的时隙标识，所述复帧周期为所述出口时隙或者所述入口时隙中每个复帧的传输时延，所述时隙间隔为所述出口时隙或者所述入口时隙中每个时隙的传输时延。
所述中间节点根据所述入口时隙的时隙标识和所述出口时隙的时隙标识，向下一跳节点转发来自上一跳节点的所述小颗粒业务。具体的，中间节点根据计算得到的出口时隙的时隙标识，更新出口时隙表。后续中间节点依据更新后的出口时隙表，在出口时隙上发送来自上一跳节点的FGU时隙。后续中间节点在入口时隙上接收来自上一跳节点的FGU时隙后，可以将入口时隙(FGU时隙)按照时隙交叉配置表映射至出口时隙上。最终，中间节点将出口时隙(FGU时隙)映射到物理接口中，向下一跳节点发送该FGU时隙。
示例性的，通过以下方式计算得到所述出口时隙的时隙标识：
其中，TxSlotId为所述出口时隙的时隙标识，Targetdelay2为所述节点的目标时延，RxMFI为所述入口时隙的复帧指示对应的相位，TxMFI为所述出口时隙的复帧指示对应的相位，MF period为所述复帧周期，slot time为所述时隙间隔，RxSlotId为所述入口时隙的时隙标识，K为中间节点中时隙交叉所需的最小时延值。
通过上述方法，确保中间节点发出的业务比特流满足时延补偿要求，进而保证小颗粒业务网络中从源节点到宿节点的网络传输时延与宿节点到源节点的网络传输时延相等或者满足预期的误差范围，或者使得源节点到宿节点的网络传输时延与宿节点到源节点的网络传输时延调整至预期值，以满足业务要求。
结合前述实施例，本申请实施例提出的时延补偿方法也可以应用于大颗粒业务场景。大颗粒业务场景下硬切片的颗粒度可以大于5吉比特每秒(G-bits per-second，Gpbs)，具 体的时延补偿方法与前述实施例类似，此处不作赘述。
结合前述实施例，本申请实施例提出的时延补偿方法也可以应用于CBR业务承载在大颗粒时隙数据(后文简称为大颗粒时隙)的场景，大颗粒时隙数据的资源颗粒可以是E*1Gbps，也可以是E*5Gbps，本申请实施例对此不做限制，其中E为正整数。具体的业务处理流程为：源节点将CBR业务比特流封装到业务容器后映射到大颗粒时隙；中间节点对大颗粒时隙进行交叉，然后在出口时隙位置发送该大颗粒时隙；宿节点从大颗粒时隙中解映射得到业务容器后，根据业务容器解封装得到CBR业务流，最后，宿节点在业务端口发送CBR业务流。CBR业务承载在大颗粒时隙的具体时延补偿方法与前述实施例提出的时延补偿方法类似，此处不作赘述。
上述主要以方法的角度对本申请实施例提供的方案进行了介绍。可以理解的是，网络设备为了实现上述功能，其包含了执行各个功能相应的硬件结构和/或软件模块。本领域技术人员应该很容易意识到，结合本文中所公开的实施例描述的各示例的模块及算法步骤，本申请能够以硬件或硬件和计算机软件的结合形式来实现。某个功能究竟以硬件还是计算机软件驱动硬件的方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
本申请实施例可以根据上述方法示例对网络设备进行功能模块的划分，例如，可以对应各个功能划分各个功能模块，也可以将两个或两个以上的功能集成在一个处理模块中。上述集成的模块既可以采用硬件的形式实现，也可以采用软件功能模块的形式实现。需要说明的是，本申请实施例中对模块的划分是示意性的，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式。
以下介绍本申请实施例的网络设备，以下介绍的网络设备具有上述方法实施例中的第一通信装置、第二通信装置或者通信装置的任意功能。
图23为本申请实施例提供的一种通信装置2300的结构示意图，如图23所示，通信装置2300包括：收发模块2301，用于执行步骤902；处理模块2302，用于执行步骤901、903、904或905。
示例性的，所述通信装置2300用于第一通信装置，所述通信装置2300包括：
处理模块2302，用于确定第一传输时延，所述第一传输时延指示小颗粒业务在所述第一通信装置中的传输时延；
收发模块2301，用于向第二通信装置发送所述第一传输时延。
一种可能的实现方式中，所述处理模块2302，具体用于通过以下方式计算得到所述小颗粒业务在所述第一通信装置中的传输时延，包括：
Nodedelay＝T2-T1；
其中，Nodedelay为所述小颗粒业务在所述第一通信装置中的传输时延，T1为第一时刻，所述第一时刻为所述第一通信装置接收所述小颗粒业务的时刻，T2为第二时刻，所述第二时刻为所述第一通信装置发送所述小颗粒业务的时刻。
一种可能的实现方式中，所述第一时刻为所述第一通信装置接收承载所述小颗粒业务的业务比特流中特定比特位的时刻。
一种可能的实现方式中，所述第二时刻为所述第一通信装置发送小颗粒单元FGU时隙数据的时刻，所述FGU时隙数据承载所述小颗粒业务的业务比特流中所述特定比特位。
一种可能的实现方式中，所述小颗粒业务为固定比特率CBR业务。
一种可能的实现方式中，所述收发模块2301，还用于接收来自上一跳节点的第二传输时延，所述第二传输时延指示所述小颗粒业务从源节点至所述上一跳节点的传输时延；
所述收发模块2301，还用于向下一跳节点发送所述第一传输时延和所述第二传输时延。
一种可能的实现方式中，所述第二传输时延包括：所述小颗粒业务从所述源节点传输至所述上一跳节点所经过的每个节点的传输时延；
或者，所述第二传输时延包括：所述小颗粒业务从所述源节点传输至所述上一跳节点所经过的每个节点的传输时延之和。
一种可能的实现方式中，所述收发模块2301，还用于接收来自所述上一跳节点的时延收集消息，所述时延收集消息中包括所述第二传输时延；
所述处理模块2302，还用于更新所述时延收集消息，更新后的所述时延收集消息中包括所述第一传输时延和所述第二传输时延；
所述收发模块2301，还用于向所述第二通信装置发送所述更新后的所述时延收集消息。
一种可能的实现方式中，所述时延收集消息还包括：路径信息；
所述处理模块2302，还用于根据所述路径信息的指示，确定接收所述时延收集消息的所述第二通信装置。
一种可能的实现方式中，所述第二通信装置用于宿节点或网络管理设备；
示例性的，所述通信装置2300用于第二通信装置，所述通信装置2300包括：
收发模块2301，用于获取第一传输时延，所述第一传输时延指示小颗粒业务在第一通信装置中的传输时延；
所述收发模块2301，还用于获取所述小颗粒业务在宿节点中的传输时延；
处理模块2302，用于根据端到端的目标时延、前n跳所述第一通信装置的所述第一传输时延，和所述小颗粒业务在所述宿节点中的传输时延，确定时延补偿值，所述时延补偿值用于在所述宿节点中对所述小颗粒业务进行时延补偿，n为正整数。
一种可能的实现方式中，所述端到端的目标时延大于或等于以下两种传输时延值中最大的一项：
第一方向的业务传输时延值或者第二方向的业务传输时延值，其中，
所述第一方向为：从源节点至所述宿节点；
所述第二方向为：从所述宿节点至所述源节点。
一种可能的实现方式中，所述处理模块2302，还用于根据所述时延补偿值对所述小颗粒业务进行时延补偿。
一种可能的实现方式中，所述处理模块2302，还用于通过以下方式计算得到所述时延补偿值，包括：
其中，Δ为所述时延补偿值，Targetdelay1为所述端到端的目标时延，为前n跳所述第一通信装置的所述第一传输时延，所述第一通信装置用于所述源节点或者中间节点，n为所述源节点和所述中间节点的节点数量，Node’delay为所述小颗粒业务在所述宿节点中传输时延。
一种可能的实现方式中，所述处理模块2302，还用于通过以下方式计算得到所述小颗粒业务在所述宿节点中的传输时延，包括：
Node’delay＝T4-T3；
其中，Node’delay为所述小颗粒业务在所述宿节点中的传输时延，T3为第三时刻，所述第三时刻为所述宿节点接收小颗粒单元FGU时隙数据的时刻，所述FGU时隙数据承载所述小颗粒业务的业务比特流中特定比特位，T4为第四时刻，所述第四时刻为所述宿节点对所述FGU时隙数据解映射得到的业务容器解封装的时刻。
一种可能的实现方式中，所述处理模块2302，还用于将所述FGU时隙数据进行解映射，得到所述业务容器；
所述处理模块2302，还用于对所述业务容器进行解封装，得到业务切片；
所述处理模块2302，还用于将所述业务切片存储至存储器；
所述处理模块2302，还用于当所述业务切片在所述存储器中的驻留时间到达所述时延补偿值，从所述存储器中提取所述业务切片；
所述处理模块2302，还用于根据多个所述业务切片，重组得到所述业务比特流；
所述收发模块2301，还用于发送所述业务比特流。
一种可能的实现方式中，所述收发模块2301，还用于接收来自所述宿节点的所述小颗粒业务在所述宿节点中的传输时延。
一种可能的实现方式中，所述处理模块2302，还用于根据所述端到端的目标时延、所述第一传输时延，和所述小颗粒业务在所述宿节点中的传输时延，确定所述时延补偿值之后，所述方法还包括：
所述收发模块2301，还用于向所述宿节点发送所述时延补偿值。
通信装置2300可以对应于上述方法实施例中的第一通信装置或者第二通信装置，通信装置2300中的各单元和上述其他操作和/或功能分别为了实现方法实施例中的第一通信装置或者第二通信装置所实施的各种步骤和方法，具体细节可参见上述方法实施例，为了简洁，在此不再赘述。
通信装置2300在处理数据块时，仅以上述各功能模块的划分进行举例说明，实际应用中，可以根据需要而将上述功能分配由不同的功能模块完成，即将通信装置2300的内部结构划分成不同的功能模块，以完成以上描述的全部或者部分功能。另外，上述实施例提供的通信装置2300与上述图9对应的实施例方法属于同一构思，其具体实现过程详见上述方法实施例，这里不再赘述。
图24为本申请实施例提供的一种通信装置2400的结构示意图，如图24所示，通信装 置2400包括：收发模块2401，用于收发数据；处理模块2402，用于执行步骤1001或1002。
示例性的，所述通信装置2400用于通信装置，所述通信装置2400包括：
处理模块2402，用于确定小颗粒业务在所述通信装置中的传输时延；
所述处理模块2402，还用于根据节点的目标时延和所述小颗粒业务在所述通信装置中的传输时延，对所述小颗粒业务进行时延补偿。
一种可能的实现方式中，所述节点的目标时延包括：源节点的目标时延、中间节点的目标时延，和/或宿节点的目标时延。
一种可能的实现方式中，收发模块2401，用于获取第一接收时刻，所述第一接收时刻为所述源节点接收承载所述小颗粒业务的业务比特流中特定比特位的时刻；
所述收发模块2401，还用于获取第二发送时刻，所述第二发送时刻为所述源节点发送小颗粒单元FGU时隙数据的时刻，所述FGU时隙数据承载所述小颗粒业务的业务比特流中所述特定比特位；
所述处理模块2402，还用于将所述第二发送时刻减去所述第一接收时刻，得到所述小颗粒业务在所述源节点中的传输时延。
一种可能的实现方式中，收发模块2401，用于获取第三接收时刻，所述第三接收时刻为所述中间节点在入口时隙位置上接收小颗粒单元FGU时隙数据的时刻，所述FGU时隙数据承载所述小颗粒业务的业务比特流中所述特定比特位；
所述收发模块2401，还用于获取第四发送时刻，所述第四发送时刻为所述中间节点发送所述FGU时隙数据的时刻；
所述处理模块2402，还用于将所述第四发送时刻减去所述第三接收时刻，得到所述小颗粒业务在所述中间节点中的传输时延。
一种可能的实现方式中，收发模块2401，用于获取第五接收时刻，所述第五接收时刻为所述宿节点接收小颗粒单元FGU时隙数据的时刻，所述FGU时隙数据承载所述小颗粒业务的业务比特流中所述特定比特位；
所述收发模块2401，还用于获取第六发送时刻，所述第六发送时刻为所述宿节点将业务容器解封装的时刻，所述业务容器为所述通信装置对所述FGU时隙数据解映射得到，所述业务容器承载所述小颗粒业务的业务比特流中所述特定比特位；
所述处理模块2402，还用于将所述第六发送时刻减去所述第五接收时刻，得到所述小颗粒业务在所述宿节点中的传输时延。
一种可能的实现方式中，
所述处理模块2402，还用于根据所述节点的目标时延和所述小颗粒业务在所述通信装置中的传输时延，确定时延补偿值；
所述处理模块2402，还用于根据所述时延补偿值，对所述小颗粒业务进行时延补偿。
一种可能的实现方式中，所述处理模块2402，还用于根据将所述FGU时隙数据存储至存储器，所述FGU时隙数据承载所述小颗粒业务的业务比特流；
所述收发模块2401，还用于当所述FGU时隙数据在所述存储器中的驻留时间到达所述时延补偿值，从所述存储器中提取所述FGU时隙数据；
所述收发模块2401，还用于发送所述FGU时隙数据。
一种可能的实现方式中，所述处理模块2402，还用于将所述中间节点的入口时隙位置交叉至所述中间节点的出口时隙位置；
所述处理模块2402，还用于将在所述中间节点的入口时隙位置接收的所述FGU时隙数据存储至存储器；
所述处理模块2402，还用于当所述FGU时隙数据在所述存储器中的驻留时间到达所述时延补偿值，从所述存储器中提取所述FGU时隙数据；
所述收发模块2401，还用于在所述中间节点的出口时隙位置中发送所述FGU时隙数据。
一种可能的实现方式中，所述处理模块2402，还用于将所述FGU时隙数据进行解映射，得到所述业务容器；
所述处理模块2402，还用于对所述业务容器进行解封装，得到业务切片；
所述处理模块2402，还用于将所述业务切片存储至存储器；
所述处理模块2402，还用于当所述业务切片在所述存储器中的驻留时间到达所述时延补偿值，从所述存储器中提取所述业务切片；
所述处理模块2402，还用于根据多个所述业务切片，重组得到所述业务比特流；
所述收发模块2401，还用于发送所述业务比特流。
一种可能的实现方式中，所述小颗粒业务承载固定比特率CBR业务。
通信装置2400可以对应于上述方法实施例中的通信装置，通信装置2400中的各单元和上述其他操作和/或功能分别为了实现方法实施例中的通信装置或控制器所实施的各种步骤和方法，具体细节可参见上述方法实施例，为了简洁，在此不再赘述。
通信装置2400在处理数据块时，仅以上述各功能模块的划分进行举例说明，实际应用中，可以根据需要而将上述功能分配由不同的功能模块完成，即将通信装置2400的内部结构划分成不同的功能模块，以完成以上描述的全部或者部分功能。另外，上述实施例提供的通信装置2400与上述图10对应的实施例方法属于同一构思，其具体实现过程详见上述方法实施例，这里不再赘述。
需要说明的是，本申请实施例中提及的通信装置，例如可以是交换机、路由器等网络设备，也可以是网络设备上的一部分组件，例如是网络设备上的单板，线卡，还可以是网络设备上的一个功能模块，还可以是用于实现本申请方法的芯片，本申请实施例不做具体限定。当通信装置是芯片时，用于实现方法的收发模块例如可以是芯片的接口电路，处理模块可以是芯片中具有处理功能的处理电路。通信装置之间例如可以但不限于通过以太网线或光缆直接连接。
为了实现上述实施例，本申请还提供了一种通信装置。可以参阅图25，图25为本申请实施例提供的一种通信装置2500的结构示意图。
图25所示的通信装置2500尽管示出了某些特定特征，但是本领域的技术人员将从本申请实施例中意识到，为了简洁起见，图25未示出各种其他特征，以免混淆本申请实施例所公开的实施方式的更多相关方面。为此，作为示例，在一些实现方式中，通信装置2500包括一个或多个处理单元(如，CPU)2501、网络接口2502、编程接口2503、存储器2504 和一个或多个通信总线2505，用于将各种组件互连。在另一些实现方式中，通信装置2500也可以在上述示例基础上省略或增加部分功能部件或单元。
在一些实现方式中，网络接口2502用于在网络系统中和一个或多个其他的通信装置/服务器连接。在一些实现方式中，通信总线2505包括互连和控制系统组件之间的通信的电路。存储器2504可以包括非易失性存储器，例如，只读存储器(read-only memory，ROM)、可编程只读存储器(programmable ROM，PROM)、可擦除可编程只读存储器(erasable PROM，EPROM)、电可擦除可编程只读存储器(electrically EPROM，EEPROM)或闪存。存储器2504也可以包括易失性存储器，易失性存储器可以是随机存取存储器(random access memory，RAM)，其用作外部高速缓存。
在一些实现中，存储器2504或存储器2504的非暂时性计算机可读存储介质存储以下程序、模块和数据结构，或其子集，例如包括收发单元(图中未示出)、获取单元25041和处理单元25042。
在一个可能的实施例中，该通信装置2500可以具有上述图9或者图10对应的方法实施例中的第一通信装置、第二通信装置或者通信装置中的任意功能。
应理解，通信装置2500对应于上述方法实施例中的第一通信装置、第二通信装置或者通信装置或控制器，通信装置2500中的各模块和上述其他操作和/或功能分别为了实现上述方法实施例中的第一通信装置、第二通信装置或者通信装置或控制器所实施的各种步骤和方法，具体细节可参见上述图9或者图10对应的方法实施例，为了简洁，在此不再赘述。
应理解，本申请可以是由通信装置2500上的网络接口2502来完成数据的收发操作，也可以是由处理器调用存储器中的程序代码，并在需要时配合网络接口2502来实现收发单元的功能。
在各种实现中，通信装置2500用于执行本申请实施例提供的一种时延测量方法，例如是执行上述图9或者图10所示的实施例所对应的一种时延测量方法。
本申请图25所述的通信装置具体结构可以为图26所示。
图26为本申请实施例提供的一种通信装置2600的结构示意图，通信装置2600包括：主控板2626和接口板2630。
主控板2626也称为主处理单元(main processing unit，MPU)或路由处理器(route processor)，主控板2626用于对通信装置2600中各个组件的控制和管理，包括路由计算、设备管理、设备维护、协议处理功能。主控板2626包括：中央处理器2611和存储器2612。
接口板2630也称为线路处理单元(line processing unit，LPU)、线卡(line card)或业务板。接口板2630用于提供各种业务接口并实现数据包的转发。业务接口包括但不限于以太网接口、POS(Packet over SONET/SDH)接口等。接口板2630包括：中央处理器2631、网络处理器2632、转发表项存储器2634和物理接口卡(physical interface card，PIC)2633。
接口板2630上的中央处理器2631用于对接口板2630进行控制管理并与主控板2626上的中央处理器2611通信。
网络处理器2632用于实现报文的转发处理。网络处理器2632的形态可以是转发芯片。
物理接口卡2633用于实现物理层的对接功能，原始的流量由此进入接口板2630，以及处理后的报文从该物理接口卡2633发出。物理接口卡2633包括至少一个物理接口，物理接口也称物理口，物理接口可以为灵活以太(Flexible Ethernet,FlexE)物理接口。物理接口卡2633也称为子卡，可安装在接口板2630上，负责将光电信号转换为报文并对报文进行合法性检查后转发给网络处理器2632处理。在一些实施例中，接口板2630的中央处理器2631也可执行网络处理器2632的功能，比如基于通用CPU实现软件转发，从而接口板2630中不需要网络处理器2632。
可选的，通信装置2600包括多个接口板，例如通信装置2600还包括接口板2640，接口板2640包括：中央处理器2641、网络处理器2642、转发表项存储器2644和物理接口卡2643。
可选的，通信装置2600还包括交换网板2620。交换网板2620也可以称为交换网板单元(switch fabric unit，SFU)。在通信装置有多个接口板2630的情况下，交换网板2620用于完成各接口板之间的数据交换。例如，接口板2630和接口板2640之间可以通过交换网板2620通信。
主控板2626和接口板耦合。例如，主控板2626、接口板2630和接口板2640，以及交换网板2620之间通过系统总线和/或系统背板相连实现互通。在一种可能的实现方式中，主控板2626和接口板2630之间建立进程间通信协议(inter-process communication，IPC)通道，主控板2626和接口板2630之间通过IPC通道进行通信。
在逻辑上，通信装置2600包括控制面和转发面，控制面包括主控板2626和中央处理器2631，转发面包括执行转发的各个组件，比如转发表项存储器2634、物理接口卡2633和网络处理器2632。控制面执行发布路由、生成转发表、处理信令和协议报文、配置与维护设备的状态等功能，控制面将生成的转发表下发给转发面，在转发面，网络处理器2632基于控制面下发的转发表对物理接口卡2633收到的报文查表转发。控制面下发的转发表可以保存在转发表项存储器2634中。在有些实施例中，控制面和转发面可以完全分离，不在同一设备上。
应理解，通信装置2500中的收发单元可以相当于通信装置2600中的物理接口卡2633或物理接口卡2643；通信装置2500中的获取单元25041和处理单元25042可以相当于通信装置2600中的中央处理器2611或中央处理器2631，也可以相当于存储器2612中存储的程序代码或指令。
应理解，本申请实施例中接口板2640上的操作与接口板2630的操作一致，为了简洁，不再赘述。应理解，本实施例的通信装置2600可对应于上述各个方法实施例中的第一通信装置、第二通信装置或者通信装置，该通信装置2600中的主控板2626、接口板2630和/或接口板2640可以实现上述各个方法实施例中的第一通信装置、第二通信装置或者通信装置所具有的功能和/或所实施的各种步骤，为了简洁，在此不再赘述。
值得说明的是，主控板可能有一块或多块，有多块的时候可以包括主用主控板和备用主控板。接口板可能有一块或多块，通信装置的数据处理能力越强，提供的接口板越多。 接口板上的物理接口卡也可以有一块或多块。交换网板可能没有，也可能有一块或多块，有多块的时候可以共同实现负荷分担冗余备份。在集中式转发架构下，通信装置可以不需要交换网板，接口板承担整个系统的业务数据的处理功能。在分布式转发架构下，通信装置可以有至少一块交换网板，通过交换网板实现多块接口板之间的数据交换，提供大容量的数据交换和处理能力。可选的，通信装置的形态也可以是只有一块板卡，即没有交换网板，接口板和主控板的功能集成在该一块板卡上，此时接口板上的中央处理器和主控板上的中央处理器在该一块板卡上可以合并为一个中央处理器，执行两者叠加后的功能。具体采用哪种架构，取决于具体的组网部署场景，此处不做唯一限定。
在一些可能的实施例中，上述第一通信装置或者第二通信装置可以实现为虚拟化设备。虚拟化设备可以是运行有用于发送报文功能的程序的虚拟机(virtual machine，VM)，虚拟路由器或虚拟交换机。虚拟化设备部署在硬件设备上(例如，物理服务器)。例如，可以基于通用的物理服务器结合网络功能虚拟化(network functions virtualization，NFV)技术来实现第一通信装置。
应理解，上述各种产品形态的通信装置，分别具有上述方法实施例中第一通信装置、第二通信装置或者通信装置的任意功能，此处不再赘述。
本申请实施例还提供一种通信装置，所述通信装置包括：通信接口；
与所述通信接口连接的处理器，基于所述通信接口和所述处理器。
一种可能的实现方式中，该网络设备用于第一通信装置，使得所述第一通信装置执行如前述图9示意的实施例中的方法。
另一种可能的实现方式中，使得所述第二通信装置执行如前述图9示意的实施例中的方法。
另一种可能的实现方式中，使得所述信装置执行如前述图10示意的实施例中的方法。
本申请实施例还提供的一种计算机可读存储介质，包括指令，当其在计算机上运行时，使得计算机控制网络装置执行如前述方法实施例所示任一项实现方式。
本申请实施例还提供的一种计算机程序产品，计算机程序产品包括计算机程序代码，当计算机程序代码在计算机上运行时，使得计算机执行如前述方法实施例所示任一项实现方式。
进一步地，本申请实施例还提供了一种计算机程序产品，当该计算机程序产品在网络设备上运行时，使得网络设备执行上述图9或者图10对应的方法实施例中第一通信装置、第二通信装置或者通信装置或控制器执行的方法。
本申请实施例还提供了一种芯片系统，包括处理器和接口电路，所述接口电路用于接收指令并传输至处理器。其中，所述处理器用于实现上述任一方法实施例中的方法。可选的，该芯片系统还包括存储器。
该芯片系统中的处理器可以为一个或多个。该处理器可以通过硬件实现也可以通过软件实现。当通过硬件实现时，该处理器可以是逻辑电路、集成电路等。当通过软件实现时，该处理器可以是一个通用处理器，通过读取存储器中存储的软件代码来实现上述任一方法实施例中的方法。
可选的，该芯片系统中的存储器也可以为一个或多个。该存储器可以与处理器集成在一起，也可以和处理器分离设置，本申请并不限定。示例性的，存储器可以是非瞬时性处理器，例如只读存储器ROM，其可以与处理器集成在同一块芯片上，也可以分别设置在不同的芯片上，本申请对存储器的类型，以及存储器与处理器的设置方式不作具体限定。
请参阅图27，图27为本申请实施例提出的一种网络系统2700示意图。该网络系统2700包括：第一通信装置2701和第二通信装置2702。第一通信装置2701和第二通信装置2702例如可以为路由器、交换机或网关等物理设备，也可以是支持路由发布和报文转发的虚拟设备等。本实施例对第一通信装置2701和第二通信装置2702的具体类型不做限定。
可选的，该网络系统2700还包括控制器2703，控制器2703可以是管理上述第一通信装置2701和第二通信装置2702的服务器。可选的，第一通信装置2701可以是通信装置2300、通信装置2400、通信装置2500或者通信装置2600。可选的，第二通信装置2702可以是通信装置2300、通信装置2400、通信装置2500或者通信装置2600。可选的，控制器2703可以是通信装置2300、通信装置2400、通信装置2500或者通信装置2600。
请参阅图28，图28为本申请实施例提出的一种网络系统2800示意图。该网络系统2800包括：第一通信装置2801、第二通信装置2802和第三通信装置2803。第一通信装置2801、第二通信装置2802和第三通信装置2803例如可以为路由器、交换机或网关等物理设备，也可以是支持路由发布和报文转发的虚拟设备等。本实施例对第一通信装置2801、第二通信装置2802和第三通信装置2803的具体类型不做限定。
示例性的，网络系统2800应用于图7所示的场景时，该第一通信装置2801可以为边缘节点1，一个或多个该第二通信装置2802可以是中间节点，该第三通信装置2803可以是边缘节点2。
可选的，图28示意的网络系统2800中还包括控制器2804。控制器2804在图7所示的场景中未示出。
上述各种产品形态的通信装置，分别具有上述方法实施例中第一通信装置、第二通信装置或者通信装置的任意功能，此处不再赘述。
以上对本申请实施例进行了详细介绍，本申请实施例方法中的步骤可以根据实际需要进行顺序调度、合并或删减；本申请实施例装置中的模块可以根据实际需要进行划分、合并或删减。
应理解，说明书通篇中提到的“一个实施例”或“一实施例”意味着与实施例有关的特定特征、结构或特性包括在本申请的至少一个实施例中。因此，在整个说明书各处出现的“在一个实施例中”或“在一实施例中”未必一定指相同的实施例。此外，这些特定的特征、结构或特性可以任意适合的方式结合在一个或多个实施例中。应理解，在本申请的各种实施例中，上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本申请实施例的实施过程构成任何限定。
本文中术语“和/或”，仅仅是一种描述关联对象的关联关系，表示可以存在三种关系， 例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。另外，本文中字符“/”，一般表示前后关联对象是一种“或”的关系。
应理解，在本申请实施例中，“与A相应的B”表示B与A相关联，根据A可以确定B。但还应理解，根据A确定B并不意味着仅仅根据A确定B，还可以根据A和/或其它信息确定B。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统，装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统，装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。上述集成的单元既可以采用硬件的形式实现，也可以采用软件功能单元的形式实现。

Claims (37)

  1. 一种时延补偿方法，其特征在于，包括：
    第一通信装置确定第一传输时延，所述第一传输时延指示小颗粒业务在所述第一通信装置中的传输时延；
    所述第一通信装置向第二通信装置发送所述第一传输时延。
  2. 根据权利要求1所述的方法，其特征在于，所述第一通信装置确定所述小颗粒业务在所述第一通信装置中的传输时延，包括：
    所述第一通信装置通过以下方式计算得到所述小颗粒业务在所述第一通信装置中的传输时延，包括：
    Nodedelay＝T2-T1；
    其中，Nodedelay为所述小颗粒业务在所述第一通信装置中的传输时延，T1为第一时刻，所述第一时刻为所述第一通信装置接收所述小颗粒业务的时刻，T2为第二时刻，所述第二时刻为所述第一通信装置发送所述小颗粒业务的时刻。
  3. 根据权利要求2所述的方法，其特征在于，所述第一时刻为所述第一通信装置接收承载所述小颗粒业务的业务比特流中特定比特位的时刻。
  4. 根据权利要求3所述的方法，其特征在于，所述第二时刻为所述第一通信装置发送小颗粒单元FGU时隙数据的时刻，所述FGU时隙数据承载所述小颗粒业务的业务比特流中所述特定比特位。
  5. 根据权利要求1-4中任一项所述的方法，其特征在于，所述小颗粒业务为固定比特率CBR业务。
  6. 根据权利要求1-5中任一项所述的方法，其特征在于，所述第一通信装置用于中间节点，所述方法还包括：
    所述第一通信装置接收来自上一跳节点的第二传输时延，所述第二传输时延指示所述小颗粒业务从源节点至所述上一跳节点的传输时延；
    所述第一通信装置向下一跳节点发送所述第一传输时延和所述第二传输时延。
  7. 根据权利要求6所述的方法，其特征在于，所述第二传输时延包括：所述小颗粒业务从所述源节点传输至所述上一跳节点所经过的每个节点的传输时延；
    或者，所述第二传输时延包括：所述小颗粒业务从所述源节点传输至所述上一跳节点所经过的每个节点的传输时延之和。
  8. 根据权利要求6-7中任一项所述的方法，其特征在于，所述第一通信装置向所述第二通信装置发送所述第一传输时延，包括：
    所述第一通信装置接收来自所述上一跳节点的时延收集消息，所述时延收集消息中包括所述第二传输时延；
    所述第一通信装置更新所述时延收集消息，更新后的所述时延收集消息中包括所述第一传输时延和所述第二传输时延；
    所述第一通信装置向所述第二通信装置发送所述更新后的所述时延收集消息。
  9. 根据权利要求8所述的方法，其特征在于，所述时延收集消息还包括：路径信息；
    所述方法还包括：
    所述第一通信装置根据所述路径信息的指示，确定接收所述时延收集消息的所述第二通信装置。
  10. 根据权利要求1-5中任一项所述的方法，其特征在于，所述第二通信装置用于宿节点或网络管理设备。
  11. 一种时延补偿方法，其特征在于，所述方法用于第二通信装置，所述方法包括：
    第二通信装置获取第一传输时延，所述第一传输时延指示小颗粒业务在第一通信装置中的传输时延；
    所述第二通信装置获取所述小颗粒业务在宿节点中的传输时延；
    所述第二通信装置根据端到端的目标时延、前n跳所述第一通信装置的所述第一传输时延，和所述小颗粒业务在所述宿节点中的传输时延，确定时延补偿值，所述时延补偿值用于在所述宿节点中对所述小颗粒业务进行时延补偿，n为正整数。
  12. 根据权利要求11所述的方法，其特征在于，
    所述端到端的目标时延大于或等于以下两种传输时延值中最大的一项：
    第一方向的业务传输时延值或者第二方向的业务传输时延值，其中，
    所述第一方向为：从源节点至所述宿节点；
    所述第二方向为：从所述宿节点至所述源节点。
  13. 根据权利要求11或12所述的方法，其特征在于，所述第二通信装置用于所述宿节点，所述方法还包括：
    所述第二通信装置根据所述时延补偿值对所述小颗粒业务进行时延补偿。
  14. 根据权利要求11-13中任一项所述的方法，其特征在于，所述第二通信装置根据所述端到端的目标时延、前n跳所述第一通信装置的所述第一传输时延，和所述小颗粒业务在所述宿节点中的传输时延，包括：
    所述第二通信装置通过以下方式计算得到所述时延补偿值，包括：
    其中，Δ为所述时延补偿值，Targetdelay1为所述端到端的目标时延，为前n跳所述第一通信装置的所述第一传输时延，所述第一通信装置用于所述源节点或者中间节点，n为所述源节点和所述中间节点的节点数量，Node’delay为所述小颗粒业务在所述宿节点中传输时延。
  15. 根据权利要求14所述的方法，其特征在于，所述第二通信装置用于所述宿节点；
    所述第二通信装置获取所述小颗粒业务在所述宿节点中的传输时延，包括：
    所述第二通信装置通过以下方式计算得到所述小颗粒业务在所述宿节点中的传输时延，包括：
    Node’delay＝T4-T3；
    其中，Node’delay为所述小颗粒业务在所述宿节点中的传输时延，T3为第三时刻，所述第三时刻为所述宿节点接收小颗粒单元FGU时隙数据的时刻，所述FGU时隙数据承载所述 小颗粒业务的业务比特流中特定比特位，T4为第四时刻，所述第四时刻为所述宿节点对所述FGU时隙数据解映射得到的业务容器解封装的时刻。
  16. 根据权利要求15所述的方法，其特征在于，所述第二通信装置用于所述宿节点；
    所述第二通信装置根据所述时延补偿值对所述小颗粒业务进行时延补偿，包括：
    所述第二通信装置将所述FGU时隙数据进行解映射，得到所述业务容器；
    所述第二通信装置对所述业务容器进行解封装，得到业务切片；
    所述第二通信装置将所述业务切片存储至存储器；
    当所述业务切片在所述存储器中的驻留时间到达所述时延补偿值，所述第二通信装置从所述存储器中提取所述业务切片；
    所述第二通信装置根据多个所述业务切片，重组得到所述业务比特流；
    所述第二通信装置发送所述业务比特流。
  17. 根据权利要求11-16中任一项所述的方法，其特征在于，所述第二通信装置用于所述网络管理设备；
    所述第二通信装置获取所述小颗粒业务在所述宿节点中的传输时延，包括：
    所述第二通信装置接收来自所述宿节点的所述小颗粒业务在所述宿节点中的传输时延。
  18. 根据权利要求17所述的方法，其特征在于，所述第二通信装置用于所述网络管理设备；
    所述第二通信装置根据所述端到端的目标时延、所述第一传输时延，和所述小颗粒业务在所述宿节点中的传输时延，确定所述时延补偿值之后，所述方法还包括：
    所述第二通信装置向所述宿节点发送所述时延补偿值。
  19. 一种时延补偿方法，其特征在于，包括：
    通信装置确定小颗粒业务在所述通信装置中的传输时延；
    所述通信装置根据节点的目标时延和所述小颗粒业务在所述通信装置中的传输时延，对所述小颗粒业务进行时延补偿。
  20. 根据权利要求19所述的方法，其特征在于，所述节点的目标时延包括：源节点的目标时延、中间节点的目标时延，和/或宿节点的目标时延。
  21. 根据权利要求19-20中任一项所述的方法，其特征在于，所述通信装置用于源节点；
    所述通信装置确定所述小颗粒业务在所述通信装置中的传输时延，包括：
    所述通信装置获取第一接收时刻，所述第一接收时刻为所述源节点接收承载所述小颗粒业务的业务比特流中特定比特位的时刻；
    所述通信装置获取第二发送时刻，所述第二发送时刻为所述源节点发送小颗粒单元FGU时隙数据的时刻，所述FGU时隙数据承载所述小颗粒业务的业务比特流中所述特定比特位；
    所述通信装置将所述第二发送时刻减去所述第一接收时刻，得到所述小颗粒业务在所述源节点中的传输时延。
  22. 根据权利要求19-21中任一项所述的方法，其特征在于，当所述通信装置用于中间节点时；
    所述通信装置确定所述小颗粒业务在所述通信装置中的传输时延，包括：
    所述通信装置获取第三接收时刻，所述第三接收时刻为所述中间节点在入口时隙位置上接收小颗粒单元FGU时隙数据的时刻，所述FGU时隙数据承载所述小颗粒业务的业务比特流中所述特定比特位；
    所述通信装置获取第四发送时刻，所述第四发送时刻为所述中间节点发送所述FGU时隙数据的时刻；
    所述通信装置将所述第四发送时刻减去所述第三接收时刻，得到所述小颗粒业务在所述中间节点中的传输时延。
  23. 根据权利要求19-22中任一项所述的方法，其特征在于，当所述通信装置用于宿节点时；
    所述通信装置确定所述小颗粒业务在所述通信装置中的传输时延，包括：
    所述通信装置获取第五接收时刻，所述第五接收时刻为所述宿节点接收小颗粒单元FGU时隙数据的时刻，所述FGU时隙数据承载所述小颗粒业务的业务比特流中所述特定比特位；
    所述通信装置获取第六发送时刻，所述第六发送时刻为所述宿节点将业务容器解封装的时刻，所述业务容器为所述通信装置对所述FGU时隙数据解映射得到，所述业务容器承载所述小颗粒业务的业务比特流中所述特定比特位；
    所述通信装置将所述第六发送时刻减去所述第五接收时刻，得到所述小颗粒业务在所述宿节点中的传输时延。
  24. 根据权利要求19-23中任一项所述的方法，其特征在于，所述通信装置根据所述节点的目标时延和所述小颗粒业务在所述通信装置中的传输时延，对所述小颗粒业务进行时延补偿，包括：
    所述通信装置根据所述节点的目标时延和所述小颗粒业务在所述通信装置中的传输时延，确定时延补偿值；
    所述通信装置根据所述时延补偿值，对所述小颗粒业务进行时延补偿。
  25. 根据权利要求24所述的方法，其特征在于，当所述通信装置用于源节点时；
    所述通信装置根据所述时延补偿值，对所述小颗粒业务进行时延补偿，包括：
    所述通信装置根据将所述FGU时隙数据存储至存储器，所述FGU时隙数据承载所述小颗粒业务的业务比特流；
    当所述FGU时隙数据在所述存储器中的驻留时间到达所述时延补偿值，所述通信装置从所述存储器中提取所述FGU时隙数据；
    所述通信装置发送所述FGU时隙数据。
  26. 根据权利要求24或25所述的方法，其特征在于，当所述通信装置用于中间节点时；
    所述通信装置根据所述时延补偿值，对所述小颗粒业务进行时延补偿，包括：
    所述通信装置将所述中间节点的入口时隙位置交叉至所述中间节点的出口时隙位置；
    所述通信装置将在所述中间节点的入口时隙位置接收的所述FGU时隙数据存储至存储器；
    当所述FGU时隙数据在所述存储器中的驻留时间到达所述时延补偿值，所述通信装置 从所述存储器中提取所述FGU时隙数据；
    所述通信装置在所述中间节点的出口时隙位置中发送所述FGU时隙数据。
  27. 根据权利要求24-26中任一项所述的方法，其特征在于，当所述通信装置用于宿节点时；
    所述通信装置根据所述时延补偿值，对所述小颗粒业务进行时延补偿，包括：
    所述通信装置将所述FGU时隙数据进行解映射，得到所述业务容器；
    所述通信装置对所述业务容器进行解封装，得到业务切片；
    所述通信装置将所述业务切片存储至存储器；
    当所述业务切片在所述存储器中的驻留时间到达所述时延补偿值，所述通信装置从所述存储器中提取所述业务切片；
    所述通信装置根据多个所述业务切片，重组得到所述业务比特流；
    所述通信装置发送所述业务比特流。
  28. 根据权利要求19-27中任一项所述的方法，其特征在于，所述小颗粒业务承载固定比特率CBR业务。
  29. 一种通信装置，其特征在于，用作第一通信装置，包括：
    收发模块，用于执行权利要求1-10任一项所述的方法中由所述第一通信装置所执行的接收和/或发送相关的操作；
    处理模块，用于执行权利要求1-10任一项所述的方法中由所述第一通信装置所执行的接收和/或发送相关的操作之外的其它操作。
  30. 一种通信装置，其特征在于，用作第二通信装置，包括：
    收发模块，用于执行权利要求11-18任一项所述的方法中由所述第二通信装置所执行的接收和/或发送相关的操作；
    处理模块，用于执行权利要求11-18任一项所述的方法中由所述第二通信装置所执行的接收和/或发送相关的操作之外的其它操作。
  31. 一种通信装置，其特征在于，包括：
    收发模块，用于执行权利要求19-28任一项所述的方法中由所述第二通信装置所执行的接收和/或发送相关的操作；
    处理模块，用于执行权利要求19-28任一项所述的方法中由所述第二通信装置所执行的接收和/或发送相关的操作之外的其它操作。
  32. 一种网络设备，用作第一通信装置，其特征在于，包括；
    通信接口；
    与所述通信接口连接的处理器，基于所述通信接口和所述处理器，使得所述第一通信装置执行如权利要求1至10任一项所述的方法。
  33. 一种网络设备，用作第二通信装置，其特征在于，包括：
    通信接口；
    与所述通信接口连接的处理器，基于所述通信接口和所述处理器，使得所述第二通信 装置执行如权利要求11至18任一项所述的方法。
  34. 一种通信系统，其特征在于，所述通信系统包括第一通信装置和第二通信装置，所述第一通信装置用于执行权利要求1-10任一项所述的方法，所述第二通信装置用于执行权利要求11-18任一项所述的方法。
  35. 一种通信系统，其特征在于，所述通信系统包括通信装置，所述通信装置用于执行权利要求19-28任一项所述的方法。
  36. 一种计算机可读存储介质，包括指令，其特征在于，当所述指令被处理器执行时，实现权利要求1-28任一项所述的方法。
  37. 一种计算机程序产品，包括程序，其特征在于，当所述程序被处理器执行时，实现权利要求1-28任一项所述的方法。
PCT/CN2023/088463 2022-04-24 2023-04-14 一种时延补偿方法以及相关设备 WO2023207636A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202210435589.2A CN116980062A (zh) 2022-04-24 2022-04-24 一种时延补偿方法以及相关设备
CN202210435589.2 2022-04-24

Publications (1)

Publication Number Publication Date
WO2023207636A1 true WO2023207636A1 (zh) 2023-11-02

Family

ID=88473610

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/088463 WO2023207636A1 (zh) 2022-04-24 2023-04-14 一种时延补偿方法以及相关设备

Country Status (2)

Country Link
CN (1) CN116980062A (zh)
WO (1) WO2023207636A1 (zh)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102447980A (zh) * 2010-09-30 2012-05-09 中兴通讯股份有限公司 一种路由控制方法、系统及路由计算装置
CN103152118A (zh) * 2013-02-07 2013-06-12 中兴通讯股份有限公司 一种基带单元和射频单元数据业务同步方法、装置和系统
WO2016000423A1 (zh) * 2014-06-30 2016-01-07 中兴通讯股份有限公司 一种延时补偿的方法及装置
CN110858811A (zh) * 2018-08-24 2020-03-03 华为技术有限公司 测量时延的方法和网络设备
CN113630796A (zh) * 2018-08-13 2021-11-09 华为技术有限公司 服务质量监测方法、设备及系统

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102447980A (zh) * 2010-09-30 2012-05-09 中兴通讯股份有限公司 一种路由控制方法、系统及路由计算装置
CN103152118A (zh) * 2013-02-07 2013-06-12 中兴通讯股份有限公司 一种基带单元和射频单元数据业务同步方法、装置和系统
WO2016000423A1 (zh) * 2014-06-30 2016-01-07 中兴通讯股份有限公司 一种延时补偿的方法及装置
CN113630796A (zh) * 2018-08-13 2021-11-09 华为技术有限公司 服务质量监测方法、设备及系统
CN110858811A (zh) * 2018-08-24 2020-03-03 华为技术有限公司 测量时延的方法和网络设备

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
ERICSSON: "Short timestamps for User Plane Latency Control", 3GPP DRAFT; R2-1906996 - SHORT TIMESTAMPS FOR USER PLANE LATENCY CONTROL, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Reno, Nevada; 20190513 - 20190517, 2 May 2019 (2019-05-02), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP051711293 *

Also Published As

Publication number Publication date
CN116980062A (zh) 2023-10-31

Similar Documents

Publication Publication Date Title
CN102835069B (zh) 用于同步网络的装置和方法
US11082199B2 (en) Data transmission method in optical network and optical network device
EP2348691B1 (en) Service transmission method and service transmission apparatus
US11477549B2 (en) Transmission network system, data switching and transmission method, apparatus and equipment
US20110305458A1 (en) Method and device for service adaptation
KR102383297B1 (ko) 서비스 주파수를 투명하게 전송하기 위한 방법 및 디바이스
KR101573195B1 (ko) 시분할 다중화 신호들을 교환하기 위한 네트워크 요소
JP5258976B2 (ja) 時分割多重信号を交換するために分割および再組み立て（ｓａｒ）機能を用いるスケーラブルなネットワーク要素
EP2667552B1 (en) Method for service transmission over optical transport network, device and system for realizing same
WO2011057545A1 (zh) 传输多路业务的方法和装置
CN1241363C (zh) 电路业务在基于以太网的无源光网络上传输的方法
CN105306365A (zh) 一种电力通信网络及其扩容与抗毁路由路径确定方法
CN102055727A (zh) 多业务传送网中的数据封装方法、封装设备和支路单元
CN100514935C (zh) 网元设备管理信息传送方法及装置和网元设备
CN101399751B (zh) 一种通信网络中的交换系统和方法
CN101668003B (zh) 数据帧传输方法、设备及系统
WO2023207636A1 (zh) 一种时延补偿方法以及相关设备
WO2023207605A1 (zh) 一种时延测量方法以及相关设备
CN100407715C (zh) 实现网络融合的装置及其方法
Wu et al. Strategy for intercommunication of PTN and SDH
JP2002141947A (ja) リアルタイムベアラプロトコルを使用してシグナリングサーバにおいてベアラトラフィックをトランスポートするシステムおよび方法
CN103441949A (zh) 基于e1链路的以太网数据传输方法和系统
CN203466828U (zh) 一种时延可控制的基于e1链路的ethernet传输系统
CN111092689A (zh) 一种复合协议光传输系统
CN115361087A (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: 23795069

Country of ref document: EP

Kind code of ref document: A1