WO2020088674A1 - 业务发送方法、接收方法、装置及系统、存储介质 - Google Patents

业务发送方法、接收方法、装置及系统、存储介质 Download PDF

Info

Publication number
WO2020088674A1
WO2020088674A1 PCT/CN2019/115143 CN2019115143W WO2020088674A1 WO 2020088674 A1 WO2020088674 A1 WO 2020088674A1 CN 2019115143 W CN2019115143 W CN 2019115143W WO 2020088674 A1 WO2020088674 A1 WO 2020088674A1
Authority
WO
WIPO (PCT)
Prior art keywords
block
service
target information
information block
service flow
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/CN2019/115143
Other languages
English (en)
French (fr)
Inventor
刘峰
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
ZTE Corp
Original Assignee
ZTE Corp
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 ZTE Corp filed Critical ZTE Corp
Priority to EP19880135.9A priority Critical patent/EP3876443A4/en
Priority to US17/290,339 priority patent/US12040981B2/en
Publication of WO2020088674A1 publication Critical patent/WO2020088674A1/zh
Anticipated expiration legal-status Critical
Priority to US18/673,227 priority patent/US20240314079A1/en
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/0078—Avoidance of errors by organising the transmitted data in a format specifically designed to deal with errors, e.g. location
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04J—MULTIPLEX COMMUNICATION
    • H04J3/00—Time-division multiplex systems
    • H04J3/02—Details
    • H04J3/06—Synchronising arrangements
    • H04J3/07—Synchronising arrangements using pulse stuffing for systems with different or fluctuating information rates or bit rates
    • 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
    • H04J3/1605—Fixed allocated frame structures
    • H04J3/1652—Optical Transport Network [OTN]
    • H04J3/1658—Optical Transport Network [OTN] carrying packets or ATM cells
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/0078—Avoidance of errors by organising the transmitted data in a format specifically designed to deal with errors, e.g. location
    • H04L1/0079—Formats for control data
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/0078—Avoidance of errors by organising the transmitted data in a format specifically designed to deal with errors, e.g. location
    • H04L1/009—Avoidance of errors by organising the transmitted data in a format specifically designed to deal with errors, e.g. location arrangements specific to transmitters
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/0078—Avoidance of errors by organising the transmitted data in a format specifically designed to deal with errors, e.g. location
    • H04L1/0091—Avoidance of errors by organising the transmitted data in a format specifically designed to deal with errors, e.g. location arrangements specific to receivers, e.g. format detection
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L25/00—Baseband systems
    • H04L25/02—Details ; arrangements for supplying electrical power along data transmission lines
    • H04L25/14—Channel dividing arrangements, i.e. in which a single bit stream is divided between several baseband channels and reassembled at the receiver
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/24—Traffic characterised by specific attributes, e.g. priority or QoS
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04J—MULTIPLEX COMMUNICATION
    • H04J2203/00—Aspects of optical multiplex systems other than those covered by H04J14/05 and H04J14/07
    • H04J2203/0001—Provisions for broadband connections in integrated services digital network using frames of the Optical Transport Network [OTN] or using synchronous transfer mode [STM], e.g. SONET, SDH
    • H04J2203/0073—Services, e.g. multimedia, GOS, QOS
    • H04J2203/0082—Interaction of SDH with non-ATM protocols
    • H04J2203/0085—Support of Ethernet

Definitions

  • Embodiments of the present application relate to a service sending method and device, a service receiving method and device, a service transmission system, and a computer-readable storage medium.
  • Ethernet is an asynchronous network, which does not require the same frequency of the clocks between the devices on the network, and allows the deviation of the positive and negative 100PPM (1PPM is one millionth) between the clock frequencies of the devices.
  • 1PPM is one millionth
  • some devices are allowed to operate at a frequency of 0.9999G / bit / s, which is -100PPM for standard frequency; some devices are operated at 1.001G / bit / s, which is + 100PPM for standard frequency.
  • the data packets are not continuous, and there is a gap between the packets: the frame gap.
  • the Ethernet standard stipulates that the frame gap reference length between messages is 12 bytes (more than 8 bytes is acceptable).
  • adjust the size of the frame gap between packets to adjust the speed of the service flow to ensure that the speed of the service flow matches the clock frequency of the network physical interface to ensure the service The flow will not be interrupted.
  • Flexible Ethernet (FlexE) technology combines the technical characteristics of Ethernet and SDH networks.
  • the network formed by flexible Ethernet technology still has the technical characteristics of Ethernet on the physical interface.
  • the clock frequency deviation between network devices is added or deleted by customer services.
  • the number of IDLE blocks is used to achieve frequency adaptation.
  • the equipment on the transmission network adds or deletes IDLE blocks, destroying the original clock and phase information of the customer service flow, resulting in that only the original customer service can be restored at the destination Information content, but the clock information cannot be recovered.
  • At least one embodiment of the present application provides a service sending method and device, a service receiving method and device, a service transmission system, and a computer-readable storage medium to implement transmission of clock information of a service stream.
  • a service sending method including: a sending end sends a service flow, and a target information block of the service flow carries location information, and the location information is used to indicate that the target information block is in the service The relative position in the stream.
  • At least one embodiment of the present application provides a service receiving method, including: a receiving end receives a service flow, determines a relative position of a received target information block in the received service flow, and according to the relative position and the target information block The location information carried in to restore the service flow.
  • a service sending apparatus in at least one embodiment of the present application includes a memory and a processor, and the memory stores a program, and when the program is read and executed by the processor, the service sending method according to any embodiment is implemented .
  • At least one embodiment of the present application provides a computer-readable storage medium, where the computer-readable storage medium stores at least one program, and the at least one program can be executed by at least one processor to implement the program described in any of the embodiments Business delivery method.
  • At least one embodiment of the present application provides a service receiving apparatus, including a memory and a processor, where the memory stores a program, and when the program is read and executed by the processor, the service receiving described in any embodiment is implemented method.
  • At least one embodiment of the present application provides a computer-readable storage medium, where the computer-readable storage medium stores at least one program, and the at least one program can be executed by at least one processor to implement the program described in any of the embodiments Business receiving method.
  • At least one embodiment of the present application provides a service transmission system, including the service sending device described in any embodiment and the service receiving device described in any embodiment.
  • FIG. 1 is a schematic diagram of the Ethernet message processing process
  • FIG. 2 is a schematic diagram of Ethernet technology network transmission services
  • Figure 3 is a schematic diagram of the process of deleting free blocks in a service flow
  • FIG. 4 is a schematic diagram of a process of adding a free block in a service flow
  • FIG. 5 is a flowchart of a service sending method provided by an embodiment of the present application.
  • FIG. 6 is a schematic diagram of relative position identification of information blocks in a service flow provided by an embodiment of the present application.
  • FIG. 7 is a schematic diagram of the S block structure in the Ethernet standard
  • FIG. 8 is a schematic diagram of S block carrying position information provided by an embodiment of the present application.
  • FIG. 10 is a schematic diagram of O code block carrying position information provided by an embodiment of the present application.
  • FIG. 11 is a schematic diagram of a custom information block provided by an embodiment of the present application.
  • FIG. 12 is a schematic diagram of the location information carried by the custom information block provided by an embodiment of the present application.
  • FIG. 13 is a schematic diagram of position label values provided by an embodiment of the present application.
  • 14a is a schematic diagram of the location tag value carried by the S block according to an embodiment of the present application.
  • FIG. 14b is a schematic diagram of the location tag value carried by the O code block provided by an embodiment of the present application.
  • 14c is a schematic diagram of the location tag value carried by the custom information block provided by an embodiment of the present application.
  • 16 is a schematic diagram of the receiving end receiving count provided by an embodiment of the present application.
  • 17 is a flowchart of service sending and receiving provided by an embodiment of the present application.
  • FIG. 18 is a block diagram of a service sending apparatus provided by an embodiment of the present application.
  • FIG. 19 is a block diagram of a computer-readable storage medium provided by an embodiment of the present application.
  • 20 is a block diagram of a service receiving device provided by an embodiment of the present application.
  • 21 is a block diagram of a computer-readable storage medium provided by an embodiment of the present application.
  • 22 is a block diagram of a service transmission system provided by an embodiment of the present application.
  • FIG. 23 is a block diagram of a service sending apparatus provided by another embodiment of the present application.
  • 24 is a block diagram of a service receiving apparatus provided by another embodiment of the present application.
  • Ethernet technology can be formed into a synchronous network, all devices are synchronized to the same clock source, but the clock frequency between customer services and the network is different, and the clock frequency between all customer services is also different. The difference is qualified within the range of plus or minus 100PPM of the standard frequency. For example, for the Ethernet of 1G interface, the working frequency of customer service is qualified between 0.9999G bit / s (standard frequency -100PPM) to 1.0001G bit / s (standard frequency + 100PPM).
  • Flexible Ethernet (FlexE) technology combines the technical characteristics of Ethernet, Optical Transport Network (OTN), and SDH networks to expand Ethernet technology and bundle multiple Ethernet interfaces into a large physical pipe.
  • the equipment using the FlexE technology interface forms a transmission network.
  • the FlexE interface is used between the two devices, and the physical code of the service flow from the Media Access Control (MAC) layer to the physical layer Layer (Physical Coding Sublayer, PCS), then to Physical Medium Dependent (PMD) sub-layer / Physical Medium Connection (PMA) sub-layer, receiving customer services from one direction within the device at the PCS layer Directly cross the other direction to send out, because the clock frequency of the receiving direction and the sending direction are inconsistent, it is necessary to adjust the size of the frame gap between the packets to adapt to the network physical interface clock frequency of different frequencies to ensure that customer services are not interrupted.
  • MAC Media Access Control
  • PCS Physical Coding Sublayer
  • PMD Physical Medium Dependent
  • PMA Physical Medium Connection
  • the device adjusts the rate of the service flow to adapt to changes in the clock frequency of the device interface.
  • the S block is the first block of the message
  • the D block is the data block of the message
  • the T block is the tail block of the message
  • the IDLE block is an idle information block. There are 3 idle information blocks between the first message and the second message, and 1 idle information block between the second message and the third message.
  • the rate of the service flow needs to be reduced, by deleting an appropriate amount of idle blocks in the service flow, as shown in the idle information blocks in the service flow 302 and the service flow 301 in FIG. Quantity change, from 3 idle information blocks to 2 idle information blocks between the first packet and the second packet; when the device's sending service clock is greater than the receiving service clock, the service flow needs to be improved
  • the rate is achieved by adding an appropriate amount of idle blocks to the service flow, as shown in Figure 4 for the change in the number of idle information blocks in the service flow 303 and the service flow 301, between the second packet and the third packet
  • One free information block becomes two free information blocks.
  • the message is first converted into a 66-bit byte information block.
  • the information block includes two types: data block (D block, first two bits Is "01") and the control block (the first two bits are "10").
  • the control block is divided into many types, and the type of the control block is determined according to the content of the bit values at positions 2-9 of the block, such as O code block (fault information block), idle information block, S block (first message block flag), T block (trailer block flag), etc.
  • the message header is converted to S block
  • the message content is converted to D block
  • the message tail is converted to T block
  • the frame gap part of the message is converted to an idle information block (IDLE block)
  • each IDLE block is equivalent to 8
  • the free position of the byte in the case where the frame interval is less than one complete IDLE block, the accumulated frame interval reaches 8 bytes and is converted to an IDLE block).
  • the 66-bit information block is then converted to a 0 or 1 bit stream and sent out through the physical interface.
  • the customer information is required to pass
  • the fronthaul network needs to ensure all the information characteristics of the original service flow. In addition to ensuring the correct content of the information, it must also ensure the clock information and calculate the transmission delay time of the customer information.
  • the network formed by Ethernet and FlexE technology cannot fully guarantee the clock information of all customers, and cannot meet the technical requirements of the 5G fronthaul service.
  • the positional relationship between the information blocks in the service flow is disordered, and the original clock information of the customer service flow cannot be correctly restored at the receiving end.
  • the original client service flow can be completely restored at the receiving end, thereby recovering the client clock information.
  • an embodiment of the present application provides a service sending method, including step 501.
  • Step 501 The sending end sends a service flow, and the target information block of the service flow carries position information, and the position information is used to indicate the relative position of the target information block in the service flow.
  • the location information is the value of the sending counter of the sending end, and the sending counter is set to count the information blocks in the service flow; or, the location information is the sending time of the target information block.
  • a counter such as a loop counter, counting from 0 to 0xffff in hexadecimal
  • This is only an example, and may be other types of counters.
  • the timer values corresponding to the information blocks are 00, 01, 02, ..., according to the timer value can determine the information block in the business
  • the relative position in the stream The target information block of the service flow carries the counter value corresponding to the target information block, so that the relative position relationship of the information block can be determined at the receiving end.
  • the counter value carried by the target information block can identify the addition and deletion of free information blocks, and then reverse deletion and addition operations can restore the original business flow.
  • the counter value is incremented every time an information block is added.
  • FIG. 6 is only an example, and the counter may be an up counter or a down counter.
  • the counting unit of the counter can be 1, can also be 2, 3 and other types of values.
  • the value of the counter can be a meaningless pure digital value, or it can be a value representing the meaning of a certain parameter, such as a value representing a time parameter.
  • the transmission time of the information block may also be used as its location information.
  • the initial value of the counter can be set as required.
  • the number of target information blocks carrying location information in the service flow can be set as required. For example, each message has a target information block, or there is a target information block in multiple messages, and so on.
  • the target information block includes at least one of the following: an S block, a T block, an O code block, or a custom information block.
  • One type of information block can be used to carry location information in the same service flow, or multiple types of information blocks can be used to carry location information.
  • the target information block is an S block or a T block
  • the sending end sends a service flow
  • it further includes: replacing part of the bytes of the S block or the T block in the service flow with the location information content.
  • customer messages are composed of one S block, several D blocks, and one T block, which are consecutive information blocks that cannot be divided.
  • the idle information block can only be between two messages, that is, after the previous T block and before the next S block.
  • the D block is customer effective data
  • the T block is the message tail block
  • the content of the D block is uncertain
  • part of the content of different types of T blocks is fixed.
  • the S block in the message is used to indicate the length of the message
  • the content is a fixed value, as shown in FIG. 7. Since the content of the S block is a constant value, some bytes can be opened in the S block to carry position information. As shown in FIG.
  • 3 bytes in the S block are used to carry position information. It should be noted that this is only an example, and more or less bytes may be used to carry position information as needed, or other bytes in the S block may be used to carry position information.
  • Each S block in the service flow may carry location information, or some of the S blocks may carry location information.
  • O code blocks and custom information blocks In addition to the location information that can be carried on the S block, it can also be transmitted using O code blocks and custom information blocks.
  • the format of the O code defined in the Ethernet standard is shown in FIG. 9.
  • the 66 bits of the O code block start with “10” bits, and the first byte after that is 0x4B, indicating an O code block.
  • the 34-37 bit position is the type of O code block, and currently four types are defined: 0x0, 0x1, 0x5, 0xf.
  • the 38-65 bit positions are all 0, and the 10-33 bit is the information content carried.
  • a custom information block may also be used to carry the position counter value, as long as it conforms to relevant specifications, such as the Ethernet specification. As shown in Figure 11, it is a custom information block, starting with "10" bits, followed by 0xff, indicating that it is a custom information block used to carry location information. Carrying location information on a custom information block, as shown in FIG. 12, uses 34-57 bits to carry location information. It should be noted that this is only an example, and other bits can be used to carry location information.
  • the target information block also carries verification information generated according to the location information, and the verification information is used to verify whether the location information is valid. For example, one byte in the target information block is used to carry check information.
  • a location information verification information (or verification value), and the location information to form a location tag value, as shown in the figure 13 is shown.
  • the verification information is calculated from the location information through a preset verification algorithm.
  • the verification information may be calculated using a cyclic redundancy check (Cyclic Redundancy Check, CRC) check algorithm, or may be calculated using other check algorithms such as parity check.
  • CRC Cyclic Redundancy Check
  • the receiving end After obtaining the location information, the same verification algorithm is used to calculate the verification verification value, and the verification verification value calculated by the receiving end is compared with the verification information carried, and it can be known whether the carried location information is correct. Only carry the location information when it is correct.
  • the receiving end restores the target information block to the original information block that does not carry the location information and the verification information. For example, when the S block is used to carry position information and check information, the receiving end restores the content of 0x55 bytes at the corresponding position in the S block, and restores the original S block data byte structure.
  • FIG. 14a is a schematic diagram of using S blocks to carry position label values. As shown in FIG. 14a, the 26-49 bits of the S block are used to carry position information, and the 50-57 bits are used to carry check information. It should be noted that this is only an example, and other bits may be used to carry position information and check information as needed. The order of the two can also be interchanged.
  • FIG. 14b is a schematic diagram of using O code blocks to carry position label values. As shown in FIG. 14b, 10-25 bits of the O code block are used to carry position information, and 26-33 bits are used to carry check information. It should be noted that this is only an example, and other bits may be used to carry position information and check information as needed. The order of the two can also be interchanged.
  • FIG. 14c is a schematic diagram of using a custom information block to carry a location tag value.
  • the 34-57 bits of the custom information block are used to carry position information
  • the 58-65 bits are used to carry check information. It should be noted that this is only an example, and other bits may be used to carry position information and check information as needed. The order of the two can also be interchanged.
  • an embodiment of the present application provides a service receiving method, including step 1501 and step 1502.
  • Step 1501 The receiving end receives the service flow, and determines the relative position of the received target information block in the received service flow.
  • Step 1502 Restore the service flow according to the relative position and the position information carried in the target information block. Exemplarily, the original service flow at the sending end is restored.
  • the target information block includes at least one of the following: an S block, a T block, an O code block, or a custom information block. It should be noted that this is only an example, and other information blocks may also be used to carry location information as needed.
  • determining the relative position of the received target information block in the received service flow includes: the receiving end uses a reception counter to count the information blocks in the received service flow , Determine the relative position of the received target information block in the received service flow according to the value of the reception counter.
  • the reception counter receives the information block, it counts, and the relative position of the information block can be determined according to the count value of the reception counter.
  • the reception counter is incremented every time an information block is received. It should be noted that FIG. 16 is only an example.
  • the reception counter may be an up counter or a down counter.
  • the counting unit of the counter can be 1, can also be 2, 3 and other types of values.
  • the value of the counter can be a meaningless pure digital value, or it can be a value representing the meaning of a certain parameter, such as a value representing a time parameter.
  • Both the receiving counter and the sending counter can be an addition counter or a subtraction counter. Of course, one can be an addition counter and a subtraction counter.
  • the counting unit of the sending end and the receiving end can be the same or different. Of course, subsequent recovery For service flow, it needs to be calculated separately according to the conditions of the counters at the sending end and the receiving end. In an embodiment, the counting method of the sending counter of the sending end and the receiving counter of the receiving end are the same (the counting unit is the same and the same direction (the same is the up counter or the same is the down counter)).
  • the relative position of the service flow can also be determined according to the reception time, that is, the time when the information block is recorded, and then the relative position of the received information block in the received service flow can be determined .
  • the restoring the service flow according to the relative position and the position information carried in the target information block includes: determining according to the relative position and the position information carried in the target information block The difference between the relative position of the target information block in the received service flow and the relative position in the sending service flow (that is, the service flow sent by the sending end), and recovering the service flow according to the difference.
  • the idle information block when the difference indicates that an idle information block is added during transmission, the idle information block is deleted in the received service flow; when the difference indicates that the idle information block is deleted during transmission Next, add idle information blocks to the received service flow.
  • the description is as follows: using addition counting, in the case where the reception counter value corresponding to the target information block is greater than the position information extracted from the target information block, or using subtraction counting, in the target information block If the corresponding reception counter value is less than the location information extracted from the target information block, delete the free information block in the service flow; using addition counting, the reception counter value corresponding to the target information block is less than the extraction from the target information block In the case of the location information, or using subtraction counting, in the case that the reception counter value corresponding to the target information block is greater than the location information extracted from the target information block, the idle information block is added to the service flow.
  • the number of free blocks added or deleted is equal to the number of free information blocks equivalent to the difference. For example, when the counting unit is 1 and the difference is 1, it is equivalent to an idle information block.
  • the service flow may be interrupted, in one embodiment, in the case where the difference is within a preset range, reverse addition and deletion of idle information blocks is performed in the received service flow according to the difference.
  • the preset range can be set as needed, for example, the absolute value of the difference is less than or equal to 100. It should be noted that 100 is only an example and can be set as required.
  • the location information value carried in the target information block is assigned to the reception counter as the reception counter value corresponding to the target information block.
  • the reception counter and the transmission counter are re-synchronized, and the reception counter at the receiving end is restarted based on the new count value.
  • the difference between determining the relative position of the target information block in the received service flow and the relative position in the sending service flow includes: the target information block that the receiving end will receive for the first time
  • the location information carried in is used as the initial value of the receiving counter of the receiving end
  • the difference between the received counter value corresponding to the received target information block and the location information value carried in the target information block is taken as the target
  • the sending end may mark an information block as the starting information block for counting. After receiving the starting information block, the receiving end starts counting (the starting value is consistent with the sending counter) to realize the sending end and the receiving end. Synchronization, so that the difference between the reception counter value corresponding to the target information block and the position information carried in the target information block is the difference in relative position.
  • the initial value of the receiving counter instead of setting the initial value of the receiving counter at the receiving end to the position information carried in the target information block received for the first time, the initial value of the receiving counter can be arbitrarily set.
  • the counter value carried by the first target information block is M1
  • the counter value carried by the second target information block is M2
  • the reception counter value corresponding to the first target information block is N1
  • the counter value corresponding to the second target information block is N2
  • the difference in relative position at this time is: N2-N1- (M2-M1).
  • the restoring the service flow according to the relative position and the position information carried in the target information block includes: when the target information block is an O code block or a custom information block , Restore the target information block to an idle information block. Because the sending end replaces the idle information block with an O code block or a custom information block, it is restored at the receiving end.
  • the restoring the service flow according to the relative position and the location information carried in the target information block includes: when the target information block is an S block or a T block, restoring the location
  • the target information block is the original S block or T block.
  • the original S block or T block is the S block and the T block when they do not carry position information (or, position information and check information).
  • the method before restoring the service flow according to the relative position and the position information carried in the target information block, the method further includes: calculating a verification check value according to the position information carried in the target information block, In the case where the verification check value is the same as the verification information carried in the target information block, the position information carried in the target information block is valid; in the verification check value and the target information block When the verification information carried is not the same, the location information carried in the target information block is discarded.
  • the check algorithm for calculating the check verification value at the receiving end is consistent with the sending end.
  • the verification algorithm is, for example, CRC verification, which is not limited in this application, and can be set as required.
  • an embodiment of the present application provides a method for sending and receiving services, including steps 1701 to 1706.
  • Step 1701 Set a sending counter at the sending end to determine the relative position value of each information block in the service flow.
  • Step 1702 Calculate the value of the location tag at the sending end and insert it into the target information block in the service flow to send to the far end.
  • the position label value includes a transmission counter value and a verification value calculated according to a certain verification algorithm according to the transmission counter value.
  • Step 1703 Set a reception counter at the receiving end to determine the relative position of all information blocks in the received service flow.
  • Step 1704 Extract the transmission counter value carried on the target information block in the received service flow, and compare the transmission counter value carried on the target information block in the received service flow with the reception counter value corresponding to the target information block. If the difference between the transmission counter value carried in the target information block and the reception counter value corresponding to the target information block is within a preset range, step 1705 is executed to send the transmission counter value carried on the target information block in the received service flow If the difference of the reception counter value corresponding to the target information block is not within the preset range, step 1706 is executed.
  • the comparison also includes: calculating the verification check value according to the transmission counter value carried on the target information block. Compare the carried verification value with the calculated verification verification value. If the carried verification value is the same as the calculated verification verification value, the value of the transmission counter on the target information block is valid. If the verification value is different from the calculated verification verification value, the carried transmission counter value is discarded.
  • Step 1705 according to the difference between the transmission counter value carried on the target information block in the reception service flow and the reception counter value corresponding to the target information block, the reverse addition and deletion of the idle information block in the reception service flow ends.
  • addition counting is used, in the case where the reception counter value corresponding to the target information block is greater than the location information extracted from the target information block, or subtraction counting is used, and the reception counter value corresponding to the target information block is less than In the case of the location information extracted from the target information block, the idle information block is deleted in the service flow; addition counting is used, in the case where the reception counter value corresponding to the target information block is smaller than the location information extracted from the target information block, Or using subtraction counting, in the case where the value of the reception counter corresponding to the target information block is greater than the location information extracted from the target information block, an idle information block is added to the service flow.
  • the number of free blocks added or deleted is equal to the number of free information blocks equivalent to the difference.
  • step 1706 the reception counter value is revised according to the extracted transmission counter value, that is, the transmission counter value extracted from the target information block is used as the value of the reception counter corresponding to the target information block. At this time, the addition and deletion of idle information blocks are not performed, and the process ends.
  • an embodiment of the present application provides a service sending apparatus 180, including a memory 1801 and a processor 1802.
  • the memory 1801 stores a program, and when the program is read and executed by the processor 1802, Implement the service sending method described in any embodiment.
  • an embodiment of the present application provides a computer-readable storage medium 190.
  • the computer-readable storage medium 190 stores at least one program 191, and the at least one program 191 can be executed by at least one processor.
  • the service sending method described in any embodiment In order to implement the service sending method described in any embodiment.
  • an embodiment of the present application provides a service receiving apparatus 200, which includes a memory 2001 and a processor 2002.
  • the memory 2001 stores a program.
  • the program is read and executed by the processor 2002, Implement the service receiving method described in any embodiment.
  • an embodiment of the present application provides a computer-readable storage medium 210.
  • the computer-readable storage medium 210 stores at least one program 211, and the at least one program 211 can be executed by at least one processor. In order to implement the service receiving method described in any embodiment.
  • an embodiment of the present application provides a service transmission system, including the foregoing service sending device 180 and service receiving device 200.
  • the service sending device includes: a position information generating module 2301, a position information inserting module 2302, and a sending module 2303.
  • the position information generating module 2301 is configured to determine the relative position of the information block in the service flow and generate position information.
  • the position information insertion module 2302 is configured to insert the position information of the target information block into the target information block.
  • the sending module 2303 is configured to send the service flow.
  • the network-side service flow is received through the PMD, PMA, and PCS on the network interface side, and the relative position of the received target information block in the received service flow is determined, according to the relative position and the target
  • the location information carried in the information block after restoring the service flow, outputs the original service flow to the user through the PMD, PMA and PCS of the customer interface.
  • the service receiving apparatus includes a receiving module 2401, a position determination module 2402, a position extraction module 2403, and a service flow recovery module 2404.
  • the receiving module 2401 is configured to receive the service flow.
  • the position determination module 2402 is configured to determine the relative position of the received target information block in the received service flow.
  • the location extraction module 2403 is configured to extract location information carried in the target information block.
  • the service flow restoration module 2404 is configured to restore the service flow according to the relative position and the location information carried in the target information block.
  • the position determination module 2402 determining the relative position of the received target information block in the received service flow includes: using a reception counter to count the information blocks in the received service flow, according to the reception counter The value of determines the relative position of the received target information block in the received service flow.
  • the service flow restoration module 2404 restoring the service flow according to the relative position and the location information carried in the target information block includes:
  • the relative position and the position information carried in the target information block determine the difference between the relative position of the target information block in the received service flow and the relative position in the sending service flow, according to the difference Value to restore the service flow.
  • the service flow restoration module 2404 restoring the service flow according to the difference includes: in the case where the difference is within a preset range, according to the difference in the received service flow Reverse addition and deletion of idle information blocks is performed in the process; when the difference is outside the preset range, the location information value carried in the target information block is assigned to the receiving counter as the corresponding target information block The reception counter value.
  • the service flow restoration module 2404 determines that the difference between the relative position of the target information block in the received service flow and the relative position in the transmitted service flow includes: the first received target information The location information carried in the block is used as the initial value of the receiving counter at the receiving end, and the difference between the received counter value corresponding to the received target information block and the location information value carried in the target information block is obtained as the The difference between the relative position of the target information block in the received service flow and the relative position in the sent service flow.
  • the service flow restoration module 2404 restores the service flow according to the relative position and the location information carried in the target information block includes: when the target information block is an O code block or a custom In the case of an information block, the target information block is restored as an idle information block; in the case where the target information block is an S block or T block, the target information block is restored as the original S block or T block.
  • the position extraction module 2403 is further configured to: calculate a verification check value according to the position information carried in the target information block, and calibrate the verification check value with the target information block When the verification information is the same, the location information carried in the target information block is valid; when the verification verification value is different from the verification information carried in the target information block, the target information block is discarded The location information carried in.
  • computer storage media includes both volatile and nonvolatile implemented in any method or technology for storing information such as computer readable instructions, data structures, program modules, or other data Sex, removable and non-removable media.
  • Computer storage media include but are not limited to Random Access (RAM), Read-Only Memory (ROM), Erasable Programmable Read-Only Memory (Electrically), Programmable Read Only Memory (EEPROM), flash memory or Other memory technologies, compact disc read-only memory (Compact Disc Read-Only Memory, CD-ROM), digital versatile disc (Digital Video Disc, DVD) or other optical disc storage, magnetic box, magnetic tape, magnetic disk storage or other magnetic storage devices, Or any other medium that can be used to store desired information and can be accessed by a computer.
  • the communication medium generally contains computer readable instructions, data structures, program modules, or other data in a modulated data signal such as a carrier wave or other transmission mechanism, and may include any information delivery medium .
  • the relative position of the information block in the service flow is carried to realize the transmission of the clock information of the service flow, which is convenient for the receiver to recover the clock of the service flow.

Landscapes

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

Abstract

本申请公开了一种业务发送方法、接收方法、装置及系统、存储介质，该业务发送方法包括：发送端发送业务流，所述业务流的目标信息块中携带位置信息，所述位置信息用于指示所述目标信息块在所述业务流中的相对位置。

Description

业务发送方法、接收方法、装置及系统、存储介质
本申请要求在2018年11月2日提交中国专利局、申请号为201811299296.6的中国专利申请的优先权，该申请的全部内容通过引用结合在本申请中。
技术领域
本申请实施例涉及一种业务发送方法及装置、一种业务接收方法及装置、业务传输系统和计算机可读存储介质。
背景技术
随着互联网技术的蓬勃发展，信息主要内容从话音业务转为数据业务，通讯网络从适应话音业务的同步数字体系(Synchronous Digital Hierarchy，SDH)网络转为以太网网络。以太网是异步网络，不要求网上设备之间时钟同频，允许设备时钟频率之间有正负100PPM(1PPM是百万份之一)范围内偏差。例如，对于1G接口的以太网，允许有的设备工作频率为：0.9999G bit/s，为标准频率的-100PPM；有的设备工作频率为：1.0001G bit/s，为标准频率的+100PPM。在以太网上传输数据的情况下，数据报文之间并不是连续的，报文之间存在间隔：帧间隙。以太网标准规定报文之间的帧间隙参考长度是12个字节(大于8个字节以上都可以)。在以太网设备之间工作时钟频率存在偏差的情况下，通过调整报文之间的帧间隙大小，从而调整业务流的速度大小，以保证业务流的速度匹配网络物理接口的时钟频率，保证业务流不会发生中断。
灵活以太网(FlexE)技术结合了以太网、SDH网络的技术特点，灵活以太网技术组建的网络，物理接口仍具备以太网的技术特点，网络设备之间时钟频率偏差是通过增删客户业务中的IDLE块(空闲信息块)数量来实现频率适配的，传送网络上的设备增删IDLE块，破坏了客户业务流原有的时钟和相位信息，导致在目的点只能恢复出原有客户业务的信息内容，但无法恢复出时钟信息。
发明内容
本申请至少一实施例提供了一种业务发送方法及装置，业务接收方法及装置，业务传输系统以及计算机可读存储介质，实现业务流的时钟信息的传输。 本申请至少一实施例提供一种业务发送方法，包括：发送端发送业务流，所述业务流的目标信息块中携带位置信息，所述位置信息用于指示所述目标信息块在所述业务流中的相对位置。
本申请至少一实施例提供一种业务接收方法，包括：接收端接收业务流，确定接收到的目标信息块在接收到的业务流中的相对位置，根据所述相对位置和所述目标信息块中携带的位置信息，恢复所述业务流。
本申请至少一实施例一种业务发送装置，包括存储器和处理器，所述存储器存储有程序，所述程序在被所述处理器读取执行时，实现任一实施例所述的业务发送方法。
本申请至少一实施例提供一种计算机可读存储介质，所述计算机可读存储介质存储有至少一个程序，所述至少一个程序可被至少一个处理器执行，以实现任一实施例所述的业务发送方法。
本申请至少一实施例提供一种业务接收装置，包括存储器和处理器，所述存储器存储有程序，所述程序在被所述处理器读取执行时，实现任一实施例所述的业务接收方法。
本申请至少一实施例提供一种计算机可读存储介质，所述计算机可读存储介质存储有至少一个程序，所述至少一个程序可被至少一个处理器执行，以实现任一实施例所述的业务接收方法。
本申请至少一实施例提供一种业务传输系统，包括任一实施例所述的业务发送装置和任一实施例所述的业务接收装置。
附图说明
图1是以太网报文处理过程示意图；
图2是以太网技术网络传输业务示意图；
图3是业务流中删除空闲块的过程示意图；
图4是业务流中增加空闲块的过程示意图；
图5是本申请一实施例提供的业务发送方法流程图；
图6是本申请一实施例提供的业务流中信息块相对位置标识示意图；
图7是以太网标准中S块结构示意图；
图8是本申请一实施例提供的S块携带位置信息示意图；
图9是以太网标准中O码块结构示意图；
图10是本申请一实施例提供的O码块携带位置信息示意图；
图11是本申请一实施例提供的自定义信息块示意图；
图12是本申请一实施例提供的自定义信息块携带位置信息示意图；
图13是本申请一实施例提供的位置标签值示意图；
图14a是本申请一实施例提供的S块携带位置标签值示意图；
图14b是本申请一实施例提供的O码块携带位置标签值示意图；
图14c是本申请一实施例提供的自定义信息块携带位置标签值示意图；
图15是本申请一实施例提供的业务接收方法流程图；
图16是本申请一实施例提供的接收端接收计数示意图；
图17是本申请一实施例提供的业务发送和接收流程图；
图18是本申请一实施例提供的业务发送装置框图；
图19是本申请一实施例提供的计算机可读存储介质框图；
图20是本申请一实施例提供的业务接收装置框图；
图21是本申请一实施例提供的计算机可读存储介质框图；
图22是本申请一实施例提供的业务传输系统框图；
图23是本申请另一实施例提供的业务发送装置框图；
图24是本申请另一实施例提供的业务接收装置框图。
具体实施方式
在附图的流程图示出的步骤可以在诸如一组计算机可执行指令的计算机系统中执行。并且，虽然在流程图中示出了逻辑顺序，但是在某些情况下，可以以不同于此处的顺序执行所示出或描述的步骤。
虽然以太网技术可以组建成同步网络，所有设备同步于同一个时钟源，但客户业务和网络之间的时钟频率是有差异的，所有客户业务之间的时钟频率之间也是有差异的，频率差异在标准频率的正负100PPM范围之内都是合格的。例如，对于1G接口的以太网，客户业务的工作频率在0.9999G bit/s(标准频率的-100PPM)到1.0001G bit/s(标准频率的+100PPM)之间都是合格的。灵活以太网(FlexE)技术结合了以太网、光传送网(Optical Transport Network，OTN)、SDH网络的技术特点，对以太网技术进行扩展，将多个以太网接口捆绑成一个大的物理管道，实现大容量、子管道、通道化的功能，可以实现低延迟、大带宽、带宽灵活调度的需求，技术优势明显。采用FlexE技术接口的设备组成传送 网络，如图1及图2所示，两个设备之间采用FlexE接口，业务流从媒体接入控制(Media Access Control，MAC)层到物理层的物理编码子层(Physical Coding Sublayer，PCS)，再到物理介质相关(Physical Medium Dependent，PMD)子层/物理介质连接(Physical Medium Attachment，PMA)子层，在设备内部从一个方向接收到客户业务在PCS层直接交叉到另外一个方向发送出去，由于接收方向和发送方向的时钟频率不一致，需要调整报文之间的帧间隙大小，以适应不同频率的网络物理接口时钟频率，保证客户业务不会中断。MAC层和物理层的PMD子层、PMA子层例如，对于10G业务，PCS层处理的业务流是66比特块，帧间隙、空闲时刻用IDLE块指示，每个IDLE块等价于8个字节的空闲时间。设备通过增加或删除业务流中IDLE块的数量，调整业务流的速率，适应设备接口时钟频率的变化。在图3中所示的业务流301中，S块是报文的首块，D块是报文的数据块，T块是报文尾块，IDLE块是空闲信息块。在第一个报文和第二个报文之间有3个空闲信息块，第二个报文和第三个报文之间有1个空闲信息块。在设备的发送业务时钟小于接收业务时钟的情况下，需要降低业务流的速率，通过在业务流中删除适量的空闲块来实现，如图3中业务流302和业务流301中的空闲信息块数量变动情况，在第一个报文和第二个报文之间从3个空闲信息块变为2个空闲信息块；在设备的发送业务时钟大于接收业务时钟的情况下，需要提高业务流的速率，通过在业务流中增加适量的空闲块来实现，如图4中业务流303和业务流301中的空闲信息块数量变动情况，第二个报文和第三个报文之间由1个空闲信息块变为2个空闲信息块。
在以太网设备在传递客户报文信息的情况下，例如10G的物理接口，首先将报文转换为66比特字节的信息块，信息块包括两类：数据块(D块，前两个比特为“01”)和控制块(前两个比特为“10”)。控制块又分成许多种类，根据块中第2-9位置上的比特值内容决定控制块的类型，例如O码块(故障信息块)、空闲信息块、S块(报文首块标志)、T块(报文尾块标志)等。报文头部转为S块，报文内容转为D块，报文尾转为T块，报文的帧间隙部分转为空闲信息块(IDLE块)，每个IDLE块等价于8个字节的空闲位置(在帧间隔不足一个完整的IDLE块的情况下，累计帧间隔达到8个字节后转为一个IDLE块)。66比特长的信息块然后转为0或1的比特流通过物理接口发送出去。在网络设备之间因为时钟频率不一致需要调整业务流速度的情况下，通过增加或删除IDLE块的数量，调整业务流的速率，满足设备接口时钟频率的要求。
业务的空闲信息块数量增加或删除后，报文内容不受影响，但业务流的速率发生变化，无法恢复出原始客户业务流的时钟信息，在5G前传业务的承载需求中，要求客户信息通过前传网络时需要保证原始业务流的所有信息特征，除了保证信息内容正确，也要保证时钟信息，计算客户信息的传输延迟时间。目前以太网和FlexE技术组建的网络无法完全保证所有客户的时钟信息，无法满足5G前传业务的技术要求。
增删空闲信息块后导致业务流中信息块之间的位置关系发生错乱，在接收端无法正确地恢复客户业务流的原始时钟信息。在信息流中携带信息块之间的位置关系信息的情况下，在接收端可以完整地恢复原始客户业务流，从而恢复客户时钟信息。
如图5所示，本申请一实施例提供一种业务发送方法，包括步骤501。
步骤501，发送端发送业务流，所述业务流的目标信息块中携带位置信息，所述位置信息用于指示所述目标信息块在所述业务流中的相对位置。
其中，所述位置信息为所述发送端的发送计数器的值，所述发送计数器设置为对所述业务流中的信息块进行计数；或者，所述位置信息为所述目标信息块的发送时间。
本申请一实施例中，在发送端发送业务流的情况下，生成一个计数器(如循环计数器，从0计数到十六进制的0xffff，此处仅为示例，可以是其他类型的计数器)用来标注信息块之间的位置关系，如图6所示，从左至右，信息块对应的计时器值分别为00,01,02，…，根据该计时器值即可确定信息块在业务流中的相对位置。在业务流的目标信息块中携带该目标信息块对应的计数器值，这样在接收端就可以确定信息块的相对位置关系。在发生空闲块增删的情况下，通过目标信息块携带的计数器值可以辨别出空闲信息块的增加和删除情况，然后进行反向删除和增加操作，就可以恢复出原始的业务流。图6中，每增加一个信息块，计数器值加1。需要说明的是，图6仅为示例，所述计数器可以是加法计数器，也可以是减法计数器。计数器计数单位可以是1，也可以是2、3等各类值。计数器的数值可以是无含义的纯数字值，也可以是代表一定参数含义的数值，比如代表时间参数的数值。在业务流的发送速率固定的情况下，也可以将信息块的发送时刻作为其位置信息。计数器的初始值可以根据需要设定。
其中，业务流中携带位置信息的目标信息块的数量可以根据需要设定。比如，每个报文均有一个目标信息块，或者，多个报文中存在一个目标信息块， 等等。
其中，所述目标信息块包括以下至少之一：S块、T块、O码块或自定义信息块。同一业务流中可以使用其中一种信息块携带位置信息，也可以使用其中多种信息块携带位置信息。使用S块、T块、O码块或自定义信息块的部分字节携带位置信息。
其中，在所述目标信息块为S块或T块的情况下，所述发送端发送业务流前，还包括：使用所述位置信息替换所述业务流中S块或T块的部分字节内容。
在客户信息块流中，客户报文是由一个S块、若干个D块、一个T块组成，是连续不能分割的连续信息块。空闲信息块只能在两个报文之间，也就是在前一个T块之后，下一个S块之前。其中，D块是客户有效数据，T块是报文尾块，D块内容是不确定，不同种类的T块中有部分内容是固定的。报文中S块用于指示报文长度，内容是恒定不变的固定值，如图7所示。由于S块内容是恒定值，可以在S块中开辟部分字节用来携带位置信息。如图8所示，本申请一实施例中，使用S块中的3个字节携带位置信息。需要说明的是，此处仅为示例，可以根据需要使用更多或更少字节携带位置信息，或者使用S块中的其他字节携带位置信息。可以在业务流中的每个S块均携带位置信息，也可以在其中部分S块携带位置信息。
除了S块上可以携带位置信息外，也可以用O码块、自定义信息块来传递。以太网标准中定义O码格式如图9所示，O码块的66个比特中以“10”比特开始，其后第一个字节是0x4B，表示是一个O码块。34-37比特位置是O码块的类型，目前定义了四种类型：0x0、0x1、0x5、0xf。38-65比特位置全部为0，10-33比特是携带的信息内容。可以定义一个新O码块类型，如0xc(此处仅为示例，可以根据需要使用其他值)，用来指示O码块中携带位置信息，如图10所示，使用10-25比特携带位置信息。需要说明的是，图10仅为示例，可以根据需要使用其他比特携带位置信息。
在其他实施例中，也可以用自定义信息块携带位置计数器值，符合相关规范即可，比如以太网规范。如图11所示是一个自定义信息块，以“10”比特开始，后面字节是0xff，表示是一个用于携带位置信息的自定义信息块。在自定义信息块上携带位置信息，如图12所示，使用34-57比特携带位置信息，需要说明的是，此处仅为示例，可以使用其他比特携带位置信息。
其中，在使用O码块或自定义信息块携带位置信息的情况下，在发送端， 用携带位置信息的O码块(或自定义信息块)替换业务流中的空闲信息块，将位置信息带到接收端。在接收端，将携带位置信息的O码块(或自定义信息块)还原成空闲信息块，然后再进行反向增删空闲信息块，这样就恢复出原始的客户信息流块。当然，也可以进行直接进行反向增删空闲信息块(包括O码块和自定义信息块)，增删完毕后，在业务流中还有携带位置信息的O码块和自定义信息块的情况下，将其替换成空闲信息块。在一实施例中，所述目标信息块中还携带根据所述位置信息生成的校验信息，该校验信息用于校验所述位置信息是否有效。比如，使用目标信息块中的一个字节携带校验信息。为了防止在传递过程中出现误码错误，导致位置信息出现错误，从而恢复出错误的时钟，增加一个位置信息的校验信息(或称校验值)，和位置信息组成位置标签值，如图13所示。校验信息由位置信息通过预设校验算法计算获得。其中，校验信息可以采用循环冗余校验(Cyclic Redundancy Check，CRC)校验算法计算，也可以采用奇偶校验等其他校验算法计算。在接收端，获取位置信息后，采用同样的校验算法算出核验校验值，将接收端计算的核验校验值和携带的校验信息进行比较，可以知道携带的位置信息是否正确，只有在正确情况下才采用携带的位置信息。接收端在提取出位置信息和校验信息后，重新恢复该目标信息块为未携带位置信息和校验信息的原始信息块。比如，在使用S块携带位置信息和校验信息的情况下，接收端恢复S块中对应位置的0x55字节内容，还原出原始的S块数据字节结构。
图14a为使用S块携带位置标签值的示意图。如图14a所示，使用S块的26-49比特携带位置信息，使用50-57比特携带校验信息。需要说明的是，此处仅为示例，可以根据需要使用其他比特携带位置信息和校验信息。二者次序也可互换。
图14b为使用O码块携带位置标签值的示意图。如图14b所示，使用O码块的10-25比特携带位置信息，使用26-33比特携带校验信息。需要说明的是，此处仅为示例，可以根据需要使用其他比特携带位置信息和校验信息。二者次序也可互换。
图14c为使用自定义信息块携带位置标签值的示意图。如图14c所示，使用自定义信息块的34-57比特携带位置信息，使用58-65比特携带校验信息。需要说明的是，此处仅为示例，可以根据需要使用其他比特携带位置信息和校验信息。二者次序也可互换。
如图15所示，本申请一实施例提供一种业务接收方法，包括步骤1501和步骤1502。
步骤1501，接收端接收业务流，确定接收到的目标信息块在接收到的业务流中的相对位置。
步骤1502，根据所述相对位置和所述目标信息块中携带的位置信息，恢复所述业务流。示例性的，恢复为发送端的原始业务流。
在一实施例中，所述目标信息块包括以下至少之一：S块、T块、O码块或自定义信息块。需要说明的是，此处仅为示例，也可根据需要使用其他信息块携带位置信息。
在一实施例中，所述步骤1501中，确定接收到的目标信息块在接收到的业务流中的相对位置包括：所述接收端使用接收计数器对接收到的业务流中的信息块进行计数，根据接收计数器的值确定接收到的目标信息块在接收到的业务流中的相对位置。如图16所示，接收计数器接收到信息块时，进行计数，根据接收计数器的计数值即可确定信息块的相对位置。图16中，每接收到一个信息块接收计数器加1。需要说明的是，图16仅为示例。所述接收计数器可以是加法计数器，也可以是减法计数器。计数器计数单位可以是1，也可以是2、3等各类值。计数器的数值可以是无含义的纯数字值，也可以是代表一定参数含义的数值，比如代表时间参数的数值。接收计数器和发送计数器可以都是加法计数器，也可以都是减法计数器，当然，也可以一个是加法计数器，一个是减法计数器，发送端和接收端的计数单位可以相同也可以不相同，当然，后续恢复业务流时，需要根据发送端和接收端的计数器的情况分别进行计算。在一实施例中，发送端的发送计数器和接收端的接收计数器的计数方式一致(计数单位相同，且同向(同为加法计数器，或者，同为减法计数器))。
当然，在业务流的传输速率固定的情况下，也可以根据接收时刻确定业务流的相对位置，即记录接收信息块的时刻，进而确定接收到的信息块在接收到的业务流中的相对位置。
在一实施例中，所述根据所述相对位置和所述目标信息块中携带的位置信息，恢复所述业务流包括：根据所述相对位置和所述目标信息块中携带的位置信息，确定所述目标信息块在接收到的业务流中的相对位置与在发送业务流(即发送端发送的业务流)中的相对位置的差值，根据所述差值恢复业务流。
在所述目标信息块在接收到的业务流中的相对位置与在发送业务流中的相 对位置存在差值的情况下，说明信息块在传递过程中出现了增删空闲信息块的现象，增删了若干个信息块。接收端进行反向增删，在目标信息块之前删除或增加同样数量的空闲信息块，这样接收端目标信息块的相对位置和发送端保持一致。在一实施例中，在目标信息块之前没有空闲信息块，或空闲信息块的数量比较少的情况下，记录本次删除的数量。在后续的接收中遇到空闲信息块时，继续执行删除空闲信息块的动作，直到删除了等价数量的空闲信息块。
在一实施例中，在该差值指示传输过程中增加了空闲信息块的情况下，在接收到的业务流中删除空闲信息块；在该差值指示传输过程中删除了空闲信息块的情况下，在接收到的业务流中增加空闲信息块。
以采用计数器的实施例为例，进行说明如下：采用加法计数，在目标信息块对应的接收计数器值大于从该目标信息块中提取的位置信息的情况下，或采用减法计数，在目标信息块对应的接收计数器值小于从该目标信息块中提取的位置信息的情况下，在业务流中删除空闲信息块；采用加法计数，在目标信息块对应的接收计数器值小于从该目标信息块中提取的位置信息的情况下，或采用减法计数，在目标信息块对应的接收计数器值大于从该目标信息块中提取的位置信息的情况下，在业务流中增加空闲信息块。
其中，增加或删除空闲块的数量等于与所述差值等价的空闲信息块数量。比如，在计数单位为1，差值为1的情况下，相当于一个空闲信息块。
当然，在二者相同(差值为0)的情况下，无需增删信息块。
由于业务流可能发生中断，因此，在一实施例中，在所述差值在预设范围内的情况下，根据所述差值在接收到的业务流中进行空闲信息块的反向增删。预设范围可以根据需要设定，比如，差值的绝对值小于或者等于100。需要说明的是，100仅为示例，可以根据需要设定。在所述差值在预设范围外的情况下，将所述目标信息块中携带的位置信息值赋给所述接收计数器，作为所述目标信息块对应的接收计数器值。在差值比较大(预设范围外)的情况下，认为业务流出现了中断，此时，重新对接收计数器和发送计数器进行同步，让接收端的接收计数器在新计数值的基础上重新工作。
其中，确定目标信息块在接收到的业务流中的相对位置与在发送业务流中的相对位置的差值的方法可以有多种。在一实施例中，所述确定所述目标信息块在接收到的业务流中的相对位置与在发送业务流中的相对位置的差值包括：所述接收端将首次接收到的目标信息块中携带的位置信息作为所述接收端的接 收计数器的初始值，获取所述接收到的目标信息块对应的接收计数器值与所述目标信息块中携带的位置信息值的差值，作为所述目标信息块在所述接收业务流中的相对位置与在发送业务流中的相对位置的差值。即将接收端的接收计数器和发送端的发送计数器进行同步后，目标信息块对应的接收计数器值和目标信息块中携带的位置信息的差值即为相对位置的差值。
在另一实施例中，发送端可以标记一信息块作为计数的起始信息块，接收端接收到起始信息块后，开始计数(起始值和发送计数器一致)，实现发送端和接收端的同步，从而目标信息块对应的接收计数器值和目标信息块中携带的位置信息的差值即为相对位置的差值。
需要说明的是，也可以不进行同步。比如，不将接收端的接收计数器初始值设置为首次接收到的目标信息块中携带的位置信息，接收计数器的初始值可以任意设定。此时，计算相对位置的差值时需要使用相邻的目标信息块的对应的计数器值。比如，第一个目标信息块携带的计数器值为M1，第二个目标信息块携带的计数器值为M2，第一个目标信息块对应的接收计数器值为N1，第二个目标信息块对应的接收计数器值为N2，则此时相对位置的差值为：N2-N1-(M2-M1)。
在一实施例中，所述根据所述相对位置和所述目标信息块中携带的位置信息，恢复所述业务流包括：在所述目标信息块为O码块或自定义信息块的情况下，还原所述目标信息块为空闲信息块。因为发送端使用O码块或自定义信息块替换了空闲信息块，因此，在接收端进行还原。
在一实施例中，所述根据所述相对位置和所述目标信息块中携带的位置信息，恢复所述业务流包括：在所述目标信息块为S块或T块的情况下，还原所述目标信息块为原始的S块或T块。原始的S块或T块即未携带位置信息(或者，位置信息和校验信息)时的S块和T块。
在一实施例中，根据所述相对位置和所述目标信息块中携带的位置信息，恢复所述业务流前，还包括：根据所述目标信息块中携带的位置信息计算核验校验值，在所述核验校验值与所述目标信息块中携带的校验信息相同的情况下，所述目标信息块中携带的位置信息有效；在所述核验校验值与所述目标信息块中携带的校验信息不相同的情况下，放弃所述目标信息块中携带的位置信息。其中，接收端计算校验核验值的校验算法与发送端一致。校验算法比如为CRC校验等，本申请对此不作限定，可以根据需要设置。
下面通过一实施例进一步说明本申请。
如图17所示，本申请一实施例提供一种发送和接收业务的方法，包括步骤1701至步骤1706。
步骤1701：在发送端设置发送计数器，确定业务流中每个信息块的相对位置值。
步骤1702：在发送端计算出位置标签值并插入到业务流中目标信息块上发送到远端。
其中，位置标签值包括发送计数器值和根据发送计数器值经过某种校验算法计算出的校验值。
步骤1703：在接收端设置接收计数器，确定接收业务流中所有信息块的相对位置。
步骤1704：提取接收业务流中目标信息块上携带的发送计数器值，并将接收业务流中目标信息块上携带的发送计数器值和该目标信息块对应的接收计数器值进行比较，在接收业务流中目标信息块上携带的发送计数器值和该目标信息块对应的接收计数器值的差值在预设范围内的情况下，执行步骤1705，在接收业务流中目标信息块上携带的发送计数器值和该目标信息块对应的接收计数器值的差值不在预设范围内的情况下，执行步骤1706。
其中，进行比较之前，还包括：根据目标信息块上携带的发送计数器值计算出核验校验值。比较携带的校验值和计算出的核验校验值，在携带的校验值与计算出的核验校验值相同的情况下，所述目标信息块上的发送计数器值有效，在携带的校验值与计算出的核验校验值不相同的情况下，丢弃携带的发送计数器值。
步骤1705，根据接收业务流中目标信息块上携带的发送计数器值和该目标信息块对应的接收计数器值的差值在接收业务流中进行空闲信息块的反向增删，结束。
在一实施例中，采用加法计数，在目标信息块对应的接收计数器值大于从该目标信息块中提取的位置信息的情况下，或采用减法计数，在目标信息块对应的接收计数器值小于从该目标信息块中提取的位置信息的情况下，在业务流中删除空闲信息块；采用加法计数，在目标信息块对应的接收计数器值小于从该目标信息块中提取的位置信息的情况下，或采用减法计数，在目标信息块对应的接收计数器值大于从该目标信息块中提取的位置信息的情况下，在业务流 中增加空闲信息块。
其中，增加或删除空闲块的数量等于与所述差值等价的空闲信息块数量。
步骤1706，根据提取的发送计数器值来修订接收计数器值，即将目标信息块中提取的发送计数器值作为该目标信息块对应的接收计数器的值。此时不进行空闲信息块的增删，结束。
如图18所示，本申请一实施例提供一种业务发送装置180，包括存储器1801和处理器1802，所述存储器1801存储有程序，所述程序在被所述处理器1802读取执行时，实现任一实施例所述的业务发送方法。
如图19所示，本申请一实施例提供一种计算机可读存储介质190，所述计算机可读存储介质190存储有至少一个程序191，所述至少一个程序191可被至少一个处理器执行，以实现任一实施例所述的业务发送方法。
如图20所示，本申请一实施例提供一种业务接收装置200，包括存储器2001和处理器2002，所述存储器2001存储有程序，所述程序在被所述处理器2002读取执行时，实现任一实施例所述的业务接收方法。
如图21所示，本申请一实施例提供一种计算机可读存储介质210，所述计算机可读存储介质210存储有至少一个程序211，所述至少一个程序211可被至少一个处理器执行，以实现任一实施例所述的业务接收方法。
如图22所示，本申请一实施例提供一种业务传输系统，包括上述业务发送装置180和业务接收装置200。
如图23所示，在发送端，通过客户接口侧的PMD子层、PMA子层和PCS接收到来自用户的业务流，在其中插入位置信息，通过网络接口侧的PCS、PMA和PMD发送出去。业务发送装置包括：位置信息生成模块2301、位置信息插入模块2302和发送模块2303。
所述位置信息生成模块2301设置为，确定业务流中信息块的相对位置，生成位置信息。
所述位置信息插入模块2302设置为，将目标信息块的位置信息插入到所述目标信息块中。
所述发送模块2303设置为，发送所述业务流。
如图24所示，通过网络接口侧的PMD、PMA和PCS接收到网络侧业务流，确定接收到的目标信息块在接收到的业务流中的相对位置，根据所述相对位置和所述目标信息块中携带的位置信息，恢复所述业务流后，通过客户接口的PMD、 PMA和PCS输出原始业务流至用户。
如图24所示，业务接收装置包括接收模块2401，位置确定模块2402，位置提取模块2403和业务流恢复模块2404。
其中，所述接收模块2401设置为，接收业务流。
所述位置确定模块2402设置为，确定接收到的目标信息块在接收到的业务流中的相对位置。
所述位置提取模块2403设置为，提取所述目标信息块中携带的位置信息。
所述业务流恢复模块2404设置为，根据所述相对位置和所述目标信息块中携带的位置信息，恢复所述业务流。
在一实施例中，所述位置确定模块2402确定接收到的目标信息块在接收到的业务流中的相对位置包括：使用接收计数器对接收到的业务流中的信息块进行计数，根据接收计数器的值确定接收到的目标信息块在接收到的业务流中的相对位置。
在一实施例中，所述业务流恢复模块2404根据所述相对位置和所述目标信息块中携带的位置信息，恢复所述业务流包括：
根据所述相对位置和所述目标信息块中携带的位置信息，确定所述目标信息块在接收到的业务流中的相对位置与在发送业务流中的相对位置的差值，根据所述差值恢复所述业务流。
在一实施例中，所述业务流恢复模块2404根据所述差值恢复所述业务流包括：在所述差值在预设范围内的情况下，根据所述差值在接收到的业务流中进行空闲信息块的反向增删；在所述差值在预设范围外的情况下，将所述目标信息块中携带的位置信息值赋给所述接收计数器，作为所述目标信息块对应的接收计数器值。
在一实施例中，所述业务流恢复模块2404确定所述目标信息块在所述接收业务流中的相对位置与在发送业务流中的相对位置的差值包括：将首次接收到的目标信息块中携带的位置信息作为所述接收端的接收计数器的初始值，获取所述接收到的目标信息块对应的接收计数器值与所述目标信息块中携带的位置信息值的差值，作为所述目标信息块在接收到的业务流中的相对位置与在发送业务流中的相对位置的差值。
在一实施例中，所述业务流恢复模块2404根据所述相对位置和所述目标信息块中携带的位置信息，恢复所述业务流包括：在所述目标信息块为O码块或 自定义信息块的情况下，还原所述目标信息块为空闲信息块；在所述目标信息块为S块或T块的情况下，还原所述目标信息块为原始的S块或T块。
在一实施例中，所述位置提取模块2403还设置为：根据所述目标信息块中携带的位置信息计算核验校验值，在所述核验校验值与所述目标信息块中携带的校验信息相同的情况下，所述目标信息块中携带的位置信息有效；在所述核验校验值与所述目标信息块中携带的校验信息不相同的情况下，放弃所述目标信息块中携带的位置信息。
以上方案只是给出申请示例，可以有各种具体实现，例如，可以是其他类型的信息块来传递位置信息。
本领域普通技术人员可以理解，上文中所公开方法中的全部或某些步骤、系统、装置中的功能模块/单元可以被实施为软件、固件、硬件及其适当的组合。在硬件实施方式中，在以上描述中提及的功能模块/单元之间的划分不一定对应于物理组件的划分；例如，一个物理组件可以具有多个功能，或者一个功能或步骤可以由若干物理组件合作执行。某些组件或所有组件可以被实施为由处理器，如数字信号处理器或微处理器执行的软件，或者被实施为硬件，或者被实施为集成电路，如专用集成电路。这样的软件可以分布在计算机可读介质上，计算机可读介质可以包括计算机存储介质(或非暂时性介质)和通信介质(或暂时性介质)。如本领域普通技术人员公知的，术语计算机存储介质包括在用于存储信息(诸如计算机可读指令、数据结构、程序模块或其他数据)的任何方法或技术中实施的易失性和非易失性、可移除和不可移除介质。计算机存储介质包括但不限随机存储器(Random Access Memory，RAM)、只读存储器(Read-Only Memory，ROM)、带电可擦可编程只读存储器(Electrically Erasable Programmable read only memory，EEPROM)、闪存或其他存储器技术、光盘只读存储器(Compact Disc Read-Only Memory，CD-ROM)、数字多功能盘(Digital Video Disc，DVD)或其他光盘存储、磁盒、磁带、磁盘存储或其他磁存储装置、或者可以用于存储期望的信息并且可以被计算机访问的任何其他的介质。此外，本领域普通技术人员公知的是，通信介质通常包含计算机可读指令、数据结构、程序模块或者诸如载波或其他传输机制之类的调制数据信号中的其他数据，并且可包括任何信息递送介质。
与相关技术相比，本申请至少一实施例中，发送业务流时，携带信息块在业务流中的相对位置，实现了业务流的时钟信息的传送，便于接收端恢复业务 流的时钟。

Claims (21)

  1. 一种业务发送方法，包括：
    发送端发送业务流，所述业务流的目标信息块中携带位置信息，所述位置信息用于指示所述目标信息块在所述业务流中的相对位置。
  2. 根据权利要求1所述的业务发送方法，其中，所述位置信息为所述发送端的发送计数器的值，所述发送计数器设置为对所述业务流中的信息块进行计数；或者，所述位置信息为所述目标信息块的发送时间。
  3. 根据权利要求1所述的业务发送方法，其中，所述目标信息块为以下至少之一：S块、T块、O码块或自定义信息块。
  4. 根据权利要求3所述的业务发送方法，其中，在所述目标信息块为S块或T块的情况下，所述发送端发送业务流前，还包括：使用所述位置信息替换所述业务流中S块或T块的部分字节内容。
  5. 根据权利要求3所述的业务发送方法，其中，在所述目标信息块为O码块或自定义信息块的情况下，所述发送端发送业务流前，还包括：使用所述目标信息块替换所述业务流中的空闲信息块。
  6. 根据权利要求1至5任一项所述的业务发送方法，其中，所述目标信息块中还携带根据所述位置信息生成的校验信息。
  7. 一种业务接收方法，包括：
    接收端接收业务流，并确定接收到的目标信息块在接收到的业务流中的相对位置；
    根据所述相对位置和所述目标信息块中携带的位置信息，恢复所述业务流。
  8. 根据权利要求7所述的业务接收方法，其中，所述目标信息块包括以下至少之一：S块、T块、O码块或自定义信息块。
  9. 根据权利要求7所述的业务接收方法，其中，所述确定接收到的目标信息块在接收到的业务流中的相对位置，包括：
    所述接收端使用接收计数器对接收到的业务流中的信息块进行计数；
    根据所述接收计数器的值确定接收到的目标信息块在接收到的业务流中的相对位置。
  10. 根据权利要求9所述的业务接收方法，其中，所述根据所述相对位置和所述目标信息块中携带的位置信息，恢复所述业务流，包括：
    根据所述相对位置和所述目标信息块中携带的位置信息，确定所述目标信息块在接收到的业务流中的相对位置与在发送业务流中的相对位置的差值；
    根据所述差值恢复所述业务流。
  11. 根据权利要求10所述的业务接收方法，其中，所述根据所述差值恢复所述业务流包括：
    在所述差值在预设范围内的情况下，根据所述差值在接收到的业务流中进行空闲信息块的反向增删。
  12. 根据权利要求10所述的业务接收方法，其中，所述根据所述差值恢复所述业务流包括：在所述差值在预设范围外的情况下，将所述目标信息块中携带的位置信息赋给所述接收计数器，作为所述目标信息块对应的接收计数器值。
  13. 根据权利要求10所述的业务接收方法，其中，所述确定所述目标信息块在接收到的业务流中的相对位置与在发送业务流中的相对位置的差值包括：所述接收端将首次接收到的目标信息块中携带的位置信息作为所述接收端的接收计数器的初始值，获取所述接收到的目标信息块对应的接收计数器值与所述目标信息块中携带的位置信息值的差值，作为所述目标信息块在接收到的业务流中的相对位置与在发送业务流中的相对位置的差值。
  14. 根据权利要求7至13任一项所述的业务接收方法，其中，所述根据所述相对位置和所述目标信息块中携带的位置信息，恢复所述业务流，包括：在所述目标信息块为O码块或自定义信息块的情况下，还原所述目标信息块为空闲信息块。
  15. 根据权利要求7至13任一项所述的业务接收方法，其中，所述根据所述相对位置和所述目标信息块中携带的位置信息，恢复所述业务流，包括：在所述目标信息块为S块或T块的情况下，还原所述目标信息块为原始的S块或T块。
  16. 根据权利要求7至13任一项所述的业务接收方法，根据所述相对位置和所述目标信息块中携带的位置信息，恢复所述业务流前，还包括：根据所述目标信息块中携带的位置信息计算核验校验值，在所述核验校验值与所述目标信息块中携带的校验信息相同的情况下，所述目标信息块中携带的位置信息有效；在所述核验校验值与所述目标信息块中携带的校验信息不相同的情况下，放弃所述目标信息块中携带的位置信息。
  17. 一种业务发送装置，包括存储器和处理器，所述存储器存储有程序，所述程序在被所述处理器读取执行时，实现如权利要求1至6任一项所述的业务发送方法。
  18. 一种计算机可读存储介质，所述计算机可读存储介质存储有至少一个程序，所述至少一个程序可被至少一个处理器执行，以实现如权利要求1至6任一项所述的业务发送方法。
  19. 一种业务接收装置，包括存储器和处理器，所述存储器存储有程序，所述程序在被所述处理器读取执行时，实现如权利要求7至16任一项所述的业务接收方法。
  20. 一种计算机可读存储介质，所述计算机可读存储介质存储有至少一个程序，所述至少一个程序可被至少一个处理器执行，以实现如权利要求7至16任一项所述的业务接收方法。
  21. 一种业务传输系统，包括如权利要求17所述的业务发送装置和如权利要求19所述的业务接收装置。
PCT/CN2019/115143 2018-11-02 2019-11-01 业务发送方法、接收方法、装置及系统、存储介质 Ceased WO2020088674A1 (zh)

Priority Applications (3)

Application Number Priority Date Filing Date Title
EP19880135.9A EP3876443A4 (en) 2018-11-02 2019-11-01 SERVICE TRANSMITTING METHOD AND APPARATUS, SERVICE RECEIVING METHOD AND APPARATUS, AND STORAGE SYSTEM AND MEDIUM
US17/290,339 US12040981B2 (en) 2018-11-02 2019-11-01 Service receiving methods, device, system and storage medium
US18/673,227 US20240314079A1 (en) 2018-11-02 2024-05-23 Service sending and receiving methods, device, system and storage medium

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201811299296.6A CN111147181B (zh) 2018-11-02 2018-11-02 业务发送方法、接收方法、装置及系统、存储介质
CN201811299296.6 2018-11-02

Related Child Applications (2)

Application Number Title Priority Date Filing Date
US17/290,339 A-371-Of-International US12040981B2 (en) 2018-11-02 2019-11-01 Service receiving methods, device, system and storage medium
US18/673,227 Division US20240314079A1 (en) 2018-11-02 2024-05-23 Service sending and receiving methods, device, system and storage medium

Publications (1)

Publication Number Publication Date
WO2020088674A1 true WO2020088674A1 (zh) 2020-05-07

Family

ID=70462431

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/115143 Ceased WO2020088674A1 (zh) 2018-11-02 2019-11-01 业务发送方法、接收方法、装置及系统、存储介质

Country Status (4)

Country Link
US (2) US12040981B2 (zh)
EP (1) EP3876443A4 (zh)
CN (1) CN111147181B (zh)
WO (1) WO2020088674A1 (zh)

Families Citing this family (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN119892749A (zh) * 2020-04-30 2025-04-25 中兴通讯股份有限公司 信元流特征值调整方法、装置、系统和存储介质
CN112511266A (zh) * 2020-07-01 2021-03-16 中兴通讯股份有限公司 传输方法、检测方法及装置、获取方法、网络设备及系统
CN114979837A (zh) * 2021-02-22 2022-08-30 中兴通讯股份有限公司 Oam信息块的接收方法及装置
CN115811388A (zh) * 2021-09-13 2023-03-17 华为技术有限公司 一种通信方法、相关装置以及存储介质
WO2024067959A1 (en) * 2022-09-28 2024-04-04 Telefonaktiebolaget Lm Ericsson (Publ) Methods and apparatus of communicating in a physical coding sublayer
CN117834383A (zh) * 2022-09-28 2024-04-05 中兴通讯股份有限公司 时间基准位置的传递方法、报文位置确定方法、通信设备

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107786299A (zh) * 2016-08-25 2018-03-09 华为技术有限公司 一种发送和接收业务的方法、装置和网络系统
CN107888516A (zh) * 2016-09-29 2018-04-06 中兴通讯股份有限公司 一种承载业务的方法、设备和系统
CN107888345A (zh) * 2016-09-29 2018-04-06 中兴通讯股份有限公司 一种信息传输的方法和设备
EP3306839A1 (en) * 2016-10-06 2018-04-11 Alcatel Lucent Flexible ethernet client mapping procedure
CN108092739A (zh) * 2016-11-23 2018-05-29 华为技术有限公司 业务的传输方法和装置

Family Cites Families (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPH05103041A (ja) * 1991-10-04 1993-04-23 Nec Corp データ処理装置およびその故障検出方法
CN106301678B (zh) * 2015-06-08 2020-02-14 华为技术有限公司 一种数据处理的方法、通信设备及通信系统
CN107438028B (zh) * 2016-05-25 2020-10-09 华为技术有限公司 一种客户业务处理的方法和设备
CN113162853A (zh) * 2016-05-27 2021-07-23 华为技术有限公司 转发数据的方法和设备
CN107566075B (zh) * 2016-07-01 2019-10-25 华为技术有限公司 一种发送和接收业务的方法、装置和网络系统
CN107786320B (zh) * 2016-08-25 2021-06-22 华为技术有限公司 一种发送和接收业务的方法、装置和网络系统
CN108242969B (zh) * 2016-12-23 2021-04-20 华为技术有限公司 一种传输速率的调整方法及网络设备
CN108347317B (zh) * 2017-01-22 2020-11-10 华为技术有限公司 一种业务的传输方法、网络设备及网络系统
CN106911426B (zh) * 2017-02-16 2020-07-28 华为技术有限公司 一种灵活以太网中传输数据的方法及设备
CN109995455B (zh) * 2017-12-29 2020-07-07 华为技术有限公司 一种数据传输方法、通信设备及存储介质
CN110830152B (zh) * 2018-08-07 2021-04-09 华为技术有限公司 接收码块流的方法、发送码块流的方法和通信装置

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107786299A (zh) * 2016-08-25 2018-03-09 华为技术有限公司 一种发送和接收业务的方法、装置和网络系统
CN107888516A (zh) * 2016-09-29 2018-04-06 中兴通讯股份有限公司 一种承载业务的方法、设备和系统
CN107888345A (zh) * 2016-09-29 2018-04-06 中兴通讯股份有限公司 一种信息传输的方法和设备
EP3306839A1 (en) * 2016-10-06 2018-04-11 Alcatel Lucent Flexible ethernet client mapping procedure
CN108092739A (zh) * 2016-11-23 2018-05-29 华为技术有限公司 业务的传输方法和装置

Also Published As

Publication number Publication date
US20220006745A1 (en) 2022-01-06
EP3876443A1 (en) 2021-09-08
CN111147181A (zh) 2020-05-12
US12040981B2 (en) 2024-07-16
US20240314079A1 (en) 2024-09-19
CN111147181B (zh) 2022-12-09
EP3876443A4 (en) 2022-09-07

Similar Documents

Publication Publication Date Title
CN111147181B (zh) 业务发送方法、接收方法、装置及系统、存储介质
US20220416895A1 (en) Data transmission method and apparatus, terminal device and storage medium
US11539607B2 (en) Detection block sending and receiving method, and network device and system
US20120158990A1 (en) Transporting a CBR Data Stream Over a Packet Switched Network
CN107786320A (zh) 一种发送和接收业务的方法、装置和网络系统
CN113765619B (zh) 64b/66b码流发送方法、64b/66b码流接收方法及设备
CN110858790B (zh) 一种数据包的传输方法、装置、存储介质及电子装置
CN107786299A (zh) 一种发送和接收业务的方法、装置和网络系统
WO2021129578A1 (zh) 同步信息的配置方法、装置、网络设备和存储介质
US6731654B1 (en) Communication system overhead channel
CN111385049B (zh) 一种时间校正方法、装置、系统及存储介质
CN101803254B (zh) 用于时钟恢复的网络节点和反向时间戳方法
WO2022001124A1 (zh) 传输方法、检测方法及装置、获取方法、网络设备及系统
CN102318324A (zh) 用于线路卡冗余的分组序列号同步
WO2019015462A1 (zh) 一种检测块发送和接收的方法、网络设备和系统
EP4175210A1 (en) Rate adaptation method and apparatus
US8644347B2 (en) Transporting optical data units in an optical transport network
WO2021082468A1 (zh) 一种通信方法、设备及存储介质
WO2024001230A1 (zh) 承载方法、通信设备以及存储介质
CN107925557B (zh) 用于数据流的速率适配版本的识别码字
WO2022218048A1 (zh) 无源光网络传输方法、装置和系统
CN116599621B (zh) 基于跨板传递并再生恢复时钟方法、设备及装置
EP4568214A1 (en) Service information processing method, network device, and storage medium
WO2010043128A1 (zh) 发送和接收映射开销的方法、装置
WO2025112535A1 (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: 19880135

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2019880135

Country of ref document: EP

Effective date: 20210602