WO2018219323A1 - 灵活以太网协议中传递业务流的方法、装置和系统 - Google Patents

灵活以太网协议中传递业务流的方法、装置和系统 Download PDF

Info

Publication number
WO2018219323A1
WO2018219323A1 PCT/CN2018/089243 CN2018089243W WO2018219323A1 WO 2018219323 A1 WO2018219323 A1 WO 2018219323A1 CN 2018089243 W CN2018089243 W CN 2018089243W WO 2018219323 A1 WO2018219323 A1 WO 2018219323A1
Authority
WO
WIPO (PCT)
Prior art keywords
customer service
information block
predetermined
service flow
control information
Prior art date
Application number
PCT/CN2018/089243
Other languages
English (en)
French (fr)
Inventor
刘峰
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Priority to KR1020197038918A priority Critical patent/KR102266603B1/ko
Priority to JP2019558771A priority patent/JP7027449B2/ja
Priority to EP18809832.1A priority patent/EP3633887B1/en
Publication of WO2018219323A1 publication Critical patent/WO2018219323A1/zh

Links

Images

Classifications

    • 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/0001—Systems modifying transmission characteristics according to link quality, e.g. power backoff
    • H04L1/0002—Systems modifying transmission characteristics according to link quality, e.g. power backoff by adapting the transmission rate
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L49/00—Packet switching elements
    • H04L49/35—Switches specially adapted for specific applications
    • H04L49/351—Switches specially adapted for specific applications for local area network [LAN], e.g. Ethernet switches
    • H04L49/352—Gigabit ethernet switching [GBPS]
    • 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

  • the present disclosure relates to the field of communications technologies, for example, to a method, apparatus, and system for delivering traffic flows in a flexible Ethernet protocol.
  • the rapid increase of user network information traffic has promoted the rapid development of communication network information transmission bandwidth.
  • the interface bandwidth speed of communication equipment has increased from 10 megabytes (M) (unit: bit/second, the same as below) to 100M, and increased to 1 Gigabit (G), 10G, and 100G bandwidth speeds.
  • M megabytes
  • G gigabit
  • 10G 10G
  • 100G 100G optical modules
  • 400G optical modules have also been developed.
  • 400G optical modules are expensive and exceed the price of four 100G optical modules, resulting in the lack of commercial economic value of 400G optical modules.
  • the International Standards Organization has defined the Flex Ethernet (FLEXE) protocol.
  • the FLEXE protocol bundles multiple 100G optical modules to form a large speed transfer channel.
  • four 100G optical modules are bundled by the FLEXE protocol and connected to the FLEXE shim layer to form a 400G transfer channel, equivalent to the transfer speed of a 400G optical module. It not only meets the transmission requirements of 400G services, but also solves the economic value of business delivery without increasing costs.
  • the FLEXE When the customer service data is loaded on the FLEXE shim layer, the FLEXE usually carries some control information blocks with idle bits, which is wasteful.
  • the present application provides a method, device, and system for delivering a service flow in a flexible Ethernet protocol, which can improve utilization of a delivery channel, thereby improving service delivery efficiency.
  • the present application provides a method for delivering a service flow in a flexible Ethernet FLEXE protocol, the method comprising:
  • the sender encapsulates the predetermined customer service flow
  • the transmitting end inserts the encapsulated predetermined customer service flow into a predetermined type of control information block in the FLEXE service time slot, and transmits the predetermined type of control information block.
  • the application also provides a method for delivering a service flow in a flexible Ethernet FLEXE protocol, the method comprising:
  • the receiving end acquires a predetermined customer service flow according to the extracted information content.
  • the application also provides a device for delivering a service flow in a flexible Ethernet FLEXE protocol, the device comprising:
  • the encapsulation module is configured to: encapsulate a predetermined customer service flow
  • the delivery module is configured to: insert the encapsulated predetermined customer service flow into a predetermined type of control information block in the FLEXE service time slot, and send the predetermined type of control information block.
  • the application also provides a device for delivering a service flow in a flexible Ethernet FLEXE protocol, the device comprising:
  • An extraction module configured to: extract information content in a predetermined type of control information block in a FLEXE service time slot;
  • the obtaining module is configured to: obtain a predetermined customer service flow according to the extracted information content.
  • the present application also provides an apparatus for delivering a service flow in a flexible Ethernet FLEXE protocol, the apparatus comprising: a first memory and a first processor; wherein
  • the first memory is configured to: save executable instructions; the first processor is configured to: execute the executable instructions, and implement the following operations:
  • the encapsulated predetermined customer service flow is inserted into a predetermined type of control information block in the FLEXE service time slot, and the predetermined type of control information block is transmitted.
  • the present application also provides a device for delivering a service flow in a flexible Ethernet FLEXE protocol, the device comprising: a second memory and a second processor; wherein
  • the second memory is configured to: save executable instructions; the second processor is configured to: execute the executable instructions, and implement the following operations:
  • the predetermined customer service flow is obtained according to the extracted information content.
  • the present application also provides a system for delivering a service flow in a flexible Ethernet FLEXE protocol, the system comprising: a sender device and a receiver device; wherein
  • the sending end device is configured to: encapsulate a predetermined customer service flow; insert the encapsulated predetermined customer service flow into a predetermined type of control information block in the FLEXE service time slot, and send the predetermined type of control information block Giving the receiving device
  • the receiving end device is configured to: extract information content in the predetermined type of control information block in the FLEXE service time slot; and acquire a predetermined customer service flow according to the extracted information content.
  • the application also provides a computer readable storage medium storing computer executable instructions for performing the above method.
  • the embodiment of the present application can transmit part of the customer service flow by using the control information block without affecting the normal service delivery of the FLEXE, thereby improving the utilization rate of the delivery channel, thereby improving the service delivery efficiency.
  • FIG. 1 is a schematic diagram of application of a FLEXE protocol according to an embodiment of the present application
  • FIG. 2 is a schematic diagram of a FLEXE protocol overhead block and a data block arrangement position according to an embodiment of the present application
  • FIG. 3 is a schematic diagram of allocation of a FLEXE protocol service on a multiple physical channel according to an embodiment of the present application
  • FIG. 4 is a schematic diagram of a FLEXE protocol carrying a client service according to an embodiment of the present application
  • FIG. 5 is a schematic diagram of inserting an idle information block into a FLEXE layer according to an embodiment of the present application
  • FIG. 6 is a schematic diagram of a 64/66 coding principle of a client service according to an embodiment of the present application.
  • FIG. 7 is a schematic structural diagram of an idle information block according to an embodiment of the present application.
  • FIG. 8 is a flowchart of a method for delivering a service flow in a FLEXE protocol according to an embodiment of the present application
  • FIG. 9 is a flowchart of a method for delivering a service flow in a FLEXE protocol according to another embodiment of the present application.
  • FIG. 10 is a schematic diagram of a sending end transmitting a background client service flow through an idle information block according to an embodiment of the present application
  • FIG. 11 is a schematic diagram of a receiving end recovering a background service flow from an idle information block according to an embodiment of the present application
  • FIG. 12 is a schematic diagram of delivering four background client service flows in an idle information block according to an embodiment of the present application.
  • FIG. 13 is a schematic diagram of delivering a background client service flow in a member's idle information block according to an embodiment of the present application
  • FIG. 14 is a schematic diagram of delivering a background client service flow in idle information blocks of multiple members according to an embodiment of the present application
  • 15 is a schematic diagram of an apparatus for transmitting a service flow in a FLEXE protocol according to an embodiment of the present application
  • 16 is a schematic diagram of an apparatus for transmitting a service flow in a FLEXE protocol according to another embodiment of the present application.
  • 17 is a schematic diagram of an apparatus for transmitting a service flow in a FLEXE protocol according to another embodiment of the present application.
  • FIG. 18 is a schematic diagram of an apparatus for transmitting a service flow in a FLEXE protocol according to another embodiment of the present application.
  • FIG. 19 is a schematic diagram of a system for delivering a service flow in a FLEXE protocol according to an embodiment of the present application.
  • FIG. 1 is a schematic diagram of an application of a FLEXE protocol according to an embodiment of the present application.
  • the FLEXE shim layer and the four 100G optical modules on the left side of Figure 1 can be regarded as the transmitting end, and the four 100G optical modules and the FLEXE shim layer on the right side can be regarded as the receiving end.
  • the customer service flow selects a fixed number of slots on the FLEXE, it is a rigid pipeline.
  • the idle information block is inserted for the adaptation speed, resulting in The utilization of the transfer channel is low and wastes.
  • the FLEXE protocol is defined by the physical layer 100G rate.
  • the data packet is 64/66 encoded, that is, the 64-bit data is expanded into a 66-bit information block, and the added 2 bits are located at 66 bits.
  • the top of the information block is used as the start flag of the 66-bit information block, and then transmitted from the optical port as a 66-bit information block.
  • the optical port discriminates the 66-bit information block from the received data stream, and then recovers the original 64-bit data from the 66-bit information block, and reassembles the data message.
  • the FLEXE protocol is in the translation layer of 64-bit data to 66-bit information blocks, and the 66-bit information blocks are sorted and planned before the 66-bit information block is transmitted.
  • every 20 66-bit information blocks are divided into one information block group, and each 66-bit information block represents one time slot, that is, one information block group is included. 20 time slots; each time slot represents the service speed of 5G bandwidth.
  • a FLEXE overhead block (such as a block filled with diagonal lines in Fig. 2) is inserted for every 1023 block groups (1023 x 20 blocks).
  • the information block is continuously sent, after the second 1023 ⁇ 20 information blocks are sent, the overhead block is inserted, and so on, so that the overhead block is periodically inserted during the process of transmitting the information block.
  • the interval between two adjacent overhead blocks is 1023 ⁇ 20 information blocks.
  • each information block group is allocated to different physical channels in turn, for example, As shown in FIG. 3, each of the four information block groups is allocated to four physical layers of 100G. Each physical layer still forms an information block group for every 20 information blocks, and each 1023 information block group is inserted into an overhead block for transmission.
  • the overhead block plays a role in positioning, and four members (each 100G physical layer can be called a member) are positioned and sorted based on the overhead block to restore the service.
  • each time slot bandwidth is 5G, a total of 400G service delivery bandwidth.
  • the process of the FLEXE protocol carrying the customer service is as follows: First, the client service is 64/66 encoded, as shown in FIG. 4, and the service streams of the clients 1 to n are respectively 64/66 encoded. After 64/66 encoding, the service rate can be adapted, and the idle information block is inserted to ensure that the adapted speed matches the FLEXE bearer speed. Determine which time slots in each customer service flow are carried by the FLEXE shim layer. If carried by one slot, the bearer speed is 5G (bits per second, bit/s). If it is carried by m time slots, it is the bearer speed of m ⁇ 5G. After determining the number of time slots and the time slot position, the adapted service stream is inserted into the corresponding position in the FLEXE shim layer and sent out.
  • the customer service flow may not be continuous, but for a period of time, for example, the customer service is an Ethernet message, and an individual message has an interval between the messages.
  • the traffic is divided into segments of data, and the starting position and termination of the traffic can be determined.
  • free information blocks can be inserted between each data stream, and the idle information blocks function as speed adaptation. When the customer service flow speed is large, the inserted idle information block is less; when the customer service flow speed is small, the inserted idle information block is more, so that after inserting the idle information block, the speed of the service flow is completely matched with the bearer of the FLEXE shim layer. Speed requirements are sent out by the FLEXE shim layer.
  • the FLEXE shim layer Since the customer service stream has inserted free information blocks, in the FLEXE shim layer, some slot positions carry idle information blocks instead of real valid data, as shown in Figure 5, where the horizontal line filled blocks are idle. Information block. The smaller the customer's business speed, the more free information blocks.
  • the FLEXE shim layer carries idle information blocks, which is actually a loss (or waste).
  • the length of the 64/66 encoded information block is 66 bits, wherein the first two bits are information block attribute indication bits for indicating information block attributes.
  • the first two bits are information block attribute indication bits for indicating information block attributes.
  • the bit content 01
  • the last 64 bits (8 bytes) in the information block are all customer data information
  • the client of 8 bytes length Data information from byte D0 to byte D7.
  • two information block attributes indicate that the bit content is: 10
  • the information block attribute indicates that the bit content is 10, and the content of the first byte is 0x78 (78 in hexadecimal), indicating that the information block is the first data block of a data message.
  • Start block the meaning of the information block is S0D1D2D3D4D5D6D7, S represents the start block, the start flag is on the first byte, and the last 7 bytes are the customer data information.
  • the information block attribute indicates that the bit content is 10, and the first byte content is 0xFF (hexadecimal FF), indicating that the information block is the last data block (termination block) of the data message, and the information
  • the meaning of the block is D0D1D2D3D4D5D6T7, T is the termination flag, the termination flag is on the eighth byte, the first 7 bytes are the client data information;
  • the information block attribute indicates that the bit content is 10, and the first byte content is 0xAA (sixteen AA) indicates that the information block is the last data block (termination block) of a data message.
  • the meaning of the information block is D0D1T2C3C4C5C6C7, T is the termination flag, and the termination flag is on the third byte.
  • the section is the customer data information, the last 5 bytes (C3 ⁇ C7) is the ancillary information, do not care; the information block attribute indicates that the bit content is 10, the first byte content is 0x87 (87 in hexadecimal), indicating The information block is the last data block (termination block) of a data message.
  • the meaning of the information block is T0C1C2C3C4C5C6C7, T is the termination flag, the termination flag is on the first byte, and the last 7 bytes are (C1 to C7). Is ancillary information, don't care, the letter The block is only used to indicate that a customer message is terminated and does not carry any customer data.
  • the information block attribute indicates that the bit content is 10, and the first byte content is 0x1E (1E in hexadecimal), indicating that the information block is an idle information block (which may be called an idle block).
  • the first byte represents the free information block, and the last 7 bytes are the ancillary information, so don't care.
  • the idle information block is only used to adjust the speed of the customer service flow, and does not carry any customer service data. When the customer service rate becomes small, it is necessary to insert more idle information blocks for speed adjustment.
  • This embodiment provides a method for delivering a service flow in a FLEXE protocol. As shown in Figure 8, the method includes the following steps.
  • Step 110 The sending end encapsulates a predetermined customer service flow.
  • Step 120 The sending end inserts the encapsulated predetermined customer service flow into a predetermined type of control information block in the FLEXE service time slot for transmission.
  • control information block is utilized to carry additional service flows, which improves the carrying efficiency of the FLEXE shim layer and generates additional economic value.
  • control information block may refer to an information block whose information block attribute indicates that the bit content is 10; the type of the control information block may be determined by the content of the first byte of the control information block.
  • the predetermined customer service flow may be one or more.
  • different predetermined customer service flows can be distinguished by different identifiers.
  • both steps 110 and 120 may be a continuous process, and the two steps may be performed in parallel, for example, while continuously encapsulating a predetermined customer service flow, while continuously monitoring a predetermined type of control information block in the FLEXE service time slot, Once the predetermined type of control information block is found, the already encapsulated predetermined customer service stream is inserted into the control information block.
  • the predetermined type of control information block may include one or more types, and the bytes of the different types of control information blocks carrying the predetermined customer service flow (or may be inserted into the encapsulated predetermined customer service flow) The number and location can be determined based on this type.
  • the encapsulation may be in any of the following modes: a 64/66-encoded encapsulation, an Ethernet packet encapsulation, and a high-level data link control (HDLC) packet format encapsulation.
  • the sender can agree with the receiver or the default encapsulation mode.
  • the predetermined type of control information block may be, but is not limited to, an idle information block.
  • the predetermined type of control information block may refer to a control information block in which the first byte content is 0x1E (1E in hexadecimal).
  • part or all of the last 7 bytes of the free information block may be utilized to deliver a predetermined customer service flow, thereby avoiding bandwidth waste and improving transmission efficiency.
  • control information blocks may also be employed as the predetermined type of control information block.
  • the sending end inserts the encapsulated predetermined customer service flow into a predetermined type of control information block in the FLEXE service time slot, which may include:
  • the transmitting end determines a time slot in the FLEXE service time slot that carries the predetermined customer service flow
  • the slot position used to carry the predetermined customer service flow may be determined according to a predetermined rule. For example, when there is only one predetermined customer service flow, all time slot positions in the FLEXE shim layer can be determined as the time slot position carrying the predetermined customer service flow. For example, when there are 4 members and 2 scheduled customer service flows, the first 40 time slot positions in the FLEXE shim layer can be determined as the time slot position carrying the first predetermined customer service flow, and the last 40 time slot positions are determined. To carry the second slot location of the predetermined customer traffic flow.
  • a predetermined rule For example, when there is only one predetermined customer service flow, all time slot positions in the FLEXE shim layer can be determined as the time slot position carrying the predetermined customer service flow. For example, when there are 4 members and 2 scheduled customer service flows, the first 40 time slot positions in the FLEXE shim layer can be determined as the time slot position carrying the first predetermined customer service flow, and the last 40 time slot positions are determined.
  • the time slot carrying the predetermined customer traffic flow may be a time slot of one or more FLEXE members.
  • the encapsulated predetermined customer service flow may be carried on all or part of the time slots
  • the encapsulated plurality of predetermined customer service flows may be carried on different time slots.
  • the time slot location used to carry the predetermined customer traffic flow may also be pre-stored at the transmitting end.
  • the predetermined customer service flow may be, but is not limited to, the lowest priority customer service flow.
  • One type of customer service is a low priority and non-guaranteed bandwidth service. This type of service has the lowest priority and does not require guaranteed bandwidth (no guarantee of timely delivery). When the network bandwidth is congested, such services are stopped, and the network bandwidth is given to high-priority services; when the network bandwidth is idle, such services are delivered.
  • This type of business is referred to as the background customer business in the following.
  • the predetermined customer service flow may be, but is not limited to, a background customer service flow.
  • the predetermined customer service flow may also include other customer service flows.
  • the sending end inserts the encapsulated predetermined customer service flow into a predetermined type of control information block in the FLEXE service time slot, which may include:
  • the transmitting end performs speed adjustment on the encapsulated scheduled customer service flow according to the number of predetermined types of control information blocks in the FLEXE service time slot per unit time;
  • the transmitting end inserts the speed-adjusted predetermined customer service flow into a predetermined type of control information block in the FLEXE service time slot.
  • the number of units per unit time may refer to the number of unit time detected at the current time, or may be the statistics of historical data of a certain length, and the average number of unit time obtained. number.
  • the speed adjustment of the encapsulated predetermined customer service flow may include:
  • the idle information may be a bit sequence or the like of a predetermined format
  • the insertion location may be before or after the data of the predetermined customer service stream, or a specified location.
  • a higher transmission speed may be provided, and if the speed of the predetermined customer service flow itself is lower than the transmission speed, the idle information may be inserted or only a predetermined type may be used. Controlling the manner in which the partial bytes are transmitted in the information block to match the speed of the predetermined customer service stream with the above transmission speed; when the predetermined type of control information block is relatively large, if the provided transmission speed is lower than the speed of the predetermined customer service flow itself Then, the speed of the predetermined customer service flow can be matched with the above transmission speed by buffering a predetermined customer service flow or adding a predetermined type of control information block.
  • the sending end inserts the encapsulated predetermined customer service flow into a predetermined type of control information block in the FLEXE service time slot, which may include:
  • the transmitting end inserts the encapsulated predetermined customer service stream into all or part of the last seven bytes of the predetermined type of control information block in the FLEXE service time slot.
  • a byte for inserting (or for carrying) the encapsulated predetermined customer service flow is according to the control information block.
  • Type is determined.
  • the idle information block can be used to carry the predetermined customer service flow after the last 7 bytes; for example, the first byte content is 0xAA (hexadecimal AA) control information block, which can be used for the next 5 bytes. Carry a predetermined customer service flow.
  • This embodiment provides a method for delivering a service flow in a FLEXE protocol. As shown in FIG. 9, the method includes:
  • Step 210 The receiving end extracts information content in a predetermined type of control information block in the FLEXE service time slot.
  • Step 220 The receiving end acquires a predetermined customer service flow according to the extracted information content.
  • control information block is utilized to carry additional service flows, which improves the carrying efficiency of the FLEXE shim layer and generates additional economic value.
  • control information block may refer to an information block whose information block attribute indicates that the bit content is 10; the type of the control information block may be determined by the content of the first byte of the control information block.
  • the obtaining the predetermined customer service flow according to the extracted information content may include performing reverse processing of the adaptation work performed by the sending end on the extracted information content, such as deleting idle information inserted during speed adjustment. Block and decapsulate it by default or by way of agreement with the sender.
  • the predetermined customer service flow may be one or more.
  • both steps 210 and 220 can be a continuous process.
  • the predetermined type of control information block may be, but is not limited to, an idle information block.
  • the predetermined type of control information block refers to a control information block in which the first byte content is 0x1E (1E in hexadecimal).
  • control information blocks may also be employed as the predetermined type of control information block.
  • the method may further include:
  • the receiving end determines a slot location that carries a predetermined customer service in a FLEXE service slot.
  • the slot position used to carry the predetermined customer traffic flow may be determined according to a predetermined rule.
  • the time slot position for carrying the predetermined customer service flow may be pre-stored at the receiving end or the time slot position of the predetermined customer service flow may be notified by the transmitting end to the receiving end.
  • the predetermined customer service flow may be, but is not limited to, the lowest priority customer service flow.
  • the predetermined customer service flow may be, but is not limited to, a background customer service flow.
  • the predetermined customer service flow may also include other customer service flows.
  • the receiving end acquires a predetermined customer service flow according to the extracted information content, and may include:
  • the receiving end decapsulates the information content, and splicing the decapsulated information content according to the identifier of the predetermined customer service flow to obtain at least one of the predetermined customer service flows.
  • the predetermined customer service flow carries an identifier of the service flow, and the identifier receiving end can distinguish different predetermined customer service flows; and the extracted information content belonging to the same predetermined customer service flow is spliced , can restore the scheduled customer business flow.
  • the start and end of the predetermined customer service flow may be represented by a designated identification so that the receiving end recognizes the starting position and the ending position.
  • the method may further include:
  • the receiving end discards idle information inserted into the predetermined customer service flow.
  • the receiving end extracts the information content in the control information block of the predetermined type in the FLEXE service time slot, which may include:
  • the receiving end determines a time slot in the FLEXE service time slot that carries the predetermined customer service flow
  • the receiving end extracts information content from the predetermined type of control information block in a case where the control information block in the time slot carrying the predetermined customer service flow is a predetermined type of control information block.
  • the time slot carrying the predetermined customer traffic flow may be a time slot of one or more FLEXE members.
  • the encapsulated predetermined customer service flow may be carried on all or part of the time slots
  • the encapsulated plurality of predetermined customer service flows may be carried on different time slots.
  • the receiving end extracts the information content in the control information block of the predetermined type in the FLEXE service time slot, which may include:
  • the receiving end extracts information content from all or part of the last seven bytes of the predetermined type of control information block in the FLEXE service time slot.
  • the byte used to extract the information content may be determined according to the type of the control information block.
  • the idle information block can be used to carry the predetermined customer service flow after the last 7 bytes; for example, the first byte content is 0xAA (hexadecimal AA) control information block, which can be used for the next 5 bytes. Carry a predetermined customer service flow.
  • the predetermined customer service flow is a background customer service flow; the predetermined type of control information block is an idle information block.
  • the background customer service flow is adapted, and the adaptation is to process the background customer service flow to meet the requirement of inserting into the idle information block, and the adaptation includes the encapsulation and speed adjustment of the background service flow (ie, speed adaptation). .
  • the background client service flow may be one or more types and one or more speed data, it cannot be directly inserted into the idle information block (ie, the horizontal line filled block in FIG. 10),
  • the background client service flow needs to be encapsulated first, and may be a 64/66-encoded encapsulation, an Ethernet packet encapsulation, or an HDLC packet format encapsulation.
  • the packaged traffic flow can be adjusted to meet the speed requirement for insertion into the idle information block.
  • the speed adjustment inserts some idle information into the background customer service flow, and the speed adjustment adjusts the insertion speed requirement at the FLEXE shim layer. Since the number of idle information blocks in the FLEXE shim layer is dynamically changed, the number of idle information blocks in a certain instant is large, and the number of idle information blocks in a certain instant is small. Therefore, the speed adjustment is required to be dynamically changed in time.
  • time slot positions in the FLEXE shim layer are used to carry the background customer service flow, and then it is determined whether the information blocks of the time slot positions are idle information blocks. If it is an idle block, the adapted background customer traffic is inserted into the next 7 bytes of the free block. There is 7 bytes in the back of an idle information block, which can carry 7 bytes of background client traffic at a time. According to the same method, each time slot position that can carry the background customer service flow is detected, and it is detected whether the time slot position is an idle information block. If yes, it carries 7 bytes of background client service flow. When all the idle information blocks are inserted into the background client service flow in the 4 information block groups, the FLEXE shim layer can send out.
  • the receiving end it is determined which slot positions in the FLEXE shim layer can carry the background customer service flow, and then it is determined whether the slot position is an idle information block (ie, the horizontal line filled block in FIG. 11). If it is an idle information block, the background customer service flow is extracted from the last 7 byte positions in the free information block. By analogy, the background customer service flow is extracted from all the idle information blocks of the time slot location carrying the background client service, and the extraction work is completed. The recovery operation of the extracted background customer service flow: the idle information inserted during the speed adjustment is discarded, and then the package is decapsulated to restore the original background customer service flow.
  • an idle information block ie, the horizontal line filled block in FIG. 11
  • FIGS. 10 and 11 are schematic diagrams of a transmitting end and a receiving end, respectively, in the case where one background customer service flow is transmitted through time slots of the FLEXE shim layer (ie, time slots of all members).
  • the background client service flow may have one background client service flow, or may have multiple background customer service flows.
  • Background Customer traffic can be inserted on the FLEXE shim layer or on each member of the FLEXE.
  • the background customer service flow may be transmitted on the idle information block, or may be transmitted on other control information blocks (such as one or more types of control information blocks such as an o code information block or a customized control information block).
  • the background customer traffic can be delivered at all time slot locations or at some time slot locations.
  • a background customer service flow can occupy all time slot locations, or multiple background customer service flows can occupy different time slot locations.
  • background customer service flows background client 1 service flow to background customer 4 service flow in FIG. 12
  • first background customer service flow is carried by the first 20 time slot positions in the FLEXE shim layer.
  • the second background customer service flow is carried by the 21st to 40th time slot positions in the FLEXE shim layer;
  • the third background customer service flow is carried by the 41st to 60th time slot positions in the FLEXE shim layer;
  • the traffic is carried by the last 20 slot locations in the FLEXE shim layer.
  • Figure 12 shows the practice of the sender and receiver, where the service adaptation is the sender's practice, the downward arrow indicates the sender's processing flow; the service extraction is the receiver's practice, and the upward arrow indicates the receiver's processing flow.
  • the block filled with the horizontal line in FIG. 12 is an idle information block, and the transmitting end inserts the background customer service flow in the idle information block of the first 20 slots, and inserts the background client service in the idle information block of the 21st to 40th slots.
  • the receiving end is idle from the first 20 slots Extracting the background customer service flow from the information block, extracting the background customer service flow from the idle information blocks of the 21st to 40th time slots, and extracting the background customer service flow 3 from the idle information blocks of the 41st to 60th time slots.
  • the background customer service stream 4 is extracted from the idle information block of the last 20 slots.
  • the background customer traffic is passed directly on a member of the FLEXE.
  • the flow, background client traffic flow at the sender's insertion location and the receiver's extraction location are the slot locations of one member of the FLEXE (ie, the first lane in Figure 13).
  • the background traffic is passed on all members of the FLEXE.
  • it is detected whether each information block of all members of the FLEXE is a free information block (ie, a horizontal line filled block in FIG. 14), and if it is a free information block, a 7-byte background is inserted in the free information block.
  • the customer service flow, the insertion position of the background customer service flow at the transmitting end and the extraction position at the receiving end are the slot positions of all members of the FLEXE.
  • This embodiment provides an apparatus for delivering a service flow in a flexible Ethernet FLEXE protocol.
  • the device includes:
  • the encapsulating module 31 is configured to: encapsulate a predetermined customer service flow
  • the delivery module 32 is configured to insert the encapsulated predetermined customer service flow into a predetermined type of control information block in the FLEXE service time slot, and send the predetermined type of control information block.
  • the predetermined type of control information block may be, but is not limited to, an idle information block.
  • the predetermined customer service flow may be, but is not limited to, the lowest priority customer service flow.
  • the delivery module 32 is configured to insert the encapsulated predetermined customer service flow into a predetermined type of control information block in the FLEXE service time slot by:
  • the speed adjusted predetermined customer traffic is inserted into a predetermined type of control information block in the FLEXE service time slot.
  • the delivery module 32 is configured to speed adjust the encapsulated predetermined customer service flow by:
  • the delivery module 32 is configured to insert the encapsulated predetermined customer service flow into a predetermined type of control information block in the FLEXE service time slot by:
  • the time slot carrying the predetermined customer traffic flow may be a time slot of one or more FLEXE members.
  • the encapsulated predetermined customer service flow may be carried on all or part of the time slots
  • the encapsulated plurality of predetermined customer service flows are carried on different time slots.
  • the delivery module 32 is configured to insert the encapsulated predetermined customer service flow into a predetermined type of control information block in the FLEXE service time slot by:
  • the encapsulated predetermined customer traffic is inserted into all or part of the last seven bytes of the predetermined type of control information block in the FLEXE service slot.
  • a byte for inserting the encapsulated predetermined customer service stream in the last seven bytes of the predetermined type of control information block may be determined according to the type of the control information block.
  • This embodiment provides an apparatus for delivering a service flow in a flexible Ethernet FLEXE protocol.
  • the device includes:
  • the extracting module 41 is configured to: extract information content in a predetermined type of control information block in the FLEXE service time slot;
  • the obtaining module 42 is configured to: acquire a predetermined customer service flow according to the extracted information content.
  • the predetermined type of control information block may be, but is not limited to, an idle information block.
  • the predetermined customer service flow may be, but is not limited to, the lowest priority customer service flow.
  • the obtaining module 42 is configured to:
  • the apparatus further includes a discarding module configured to discard idle information inserted into the predetermined customer service stream before the obtaining module decapsulates the information content.
  • the extraction module 41 is configured to:
  • control information block in the time slot carrying the predetermined customer service flow is a predetermined type of control information block
  • the information content is extracted from the predetermined type of control information block.
  • the time slot carrying the predetermined customer traffic flow may be a time slot of one or more FLEXE members.
  • the encapsulated predetermined customer service flow may be carried on all or part of the time slots
  • the encapsulated plurality of predetermined customer service flows may be carried on different time slots.
  • the extraction module 41 is configured to:
  • the information content is extracted from all or part of the bytes of the last seven bytes of the predetermined type of control information block in the FLEXE service time slot.
  • the byte for extracting the information content may be determined according to the type of the control information block.
  • This embodiment provides an apparatus for delivering a service flow in a flexible Ethernet FLEXE protocol.
  • the device includes:
  • the first memory 51 is configured to: save executable instructions
  • the first processor 51 is configured to execute the executable instruction and implement the following operations:
  • the encapsulated predetermined customer service stream is inserted into a predetermined type of control information block in the FLEXE service time slot, and a predetermined type of control information block is transmitted.
  • the predetermined type of control information block may be, but is not limited to, an idle information block.
  • the predetermined customer service flow may be, but is not limited to, the lowest priority customer service flow.
  • the inserting the encapsulated predetermined customer service flow into the predetermined type of control information block in the FLEXE service time slot may include:
  • the speed adjusted predetermined customer traffic is inserted into a predetermined type of control information block in the FLEXE service time slot.
  • the speed adjustment of the encapsulated predetermined customer service flow may include:
  • the inserting the encapsulated predetermined customer service flow into the predetermined type of control information block in the FLEXE service time slot may include:
  • the time slot carrying the predetermined customer traffic flow may be a time slot of one or more FLEXE members.
  • the encapsulated predetermined customer service flow may be carried on all or part of the time slots
  • the encapsulated plurality of predetermined customer service flows may be carried on different time slots.
  • the inserting the encapsulated predetermined customer service flow into the predetermined type of control information block in the FLEXE service time slot may include:
  • the byte for inserting the predetermined customer service stream may be determined according to the type of the control information block.
  • This embodiment provides an apparatus for delivering a service flow in a flexible Ethernet FLEXE protocol.
  • the device includes:
  • the second memory 61 is configured to: save executable instructions
  • the second processor 62 is configured to execute the executable instruction and implement the following operations:
  • the predetermined customer service flow is obtained according to the extracted information content.
  • the predetermined type of control information block may be, but is not limited to, an idle information block.
  • the predetermined customer service flow may be, but is not limited to, the lowest priority customer service flow.
  • the obtaining the predetermined customer service flow according to the extracted information content may include:
  • the decapsulating the information content may further include:
  • the idle information inserted into the predetermined customer service flow is discarded.
  • the extracting the information content in the predetermined type of control information block in the FLEXE service time slot may include:
  • control information block in the determined time slot is a predetermined type of control information block
  • the information content is extracted from the predetermined type of control information block.
  • the time slot carrying the predetermined customer traffic flow may be a time slot of one or more FLEXE members.
  • the encapsulated predetermined customer service flow may be carried on all or part of the time slots
  • the encapsulated plurality of predetermined customer service flows may be carried on different time slots.
  • the extracting the information content in the predetermined type of control information block in the FLEXE service time slot may include:
  • the information content is extracted from all or part of the bytes of the last seven bytes of the predetermined type of control information block in the FLEXE service time slot.
  • the byte for extracting the information content may be determined according to the type of the control information block.
  • This embodiment provides a system for delivering a service flow using a flexible Ethernet protocol. As shown in Figure 19, the system includes:
  • the sending end device 71 is configured to: encapsulate a predetermined customer service flow; insert the encapsulated predetermined customer service flow into a predetermined type of control information block in the FLEXE service time slot, and set the predetermined type of control information block Send to the receiving device 72;
  • the receiving end device 72 is configured to: extract information content in a predetermined type of control information block in the FLEXE service time slot; and acquire the predetermined customer service flow according to the extracted information content.
  • transmitting device refers to the first, third, and fifth embodiments.
  • receiving device refer to the second, fourth, and sixth embodiments.
  • the embodiment provides a computer storage medium storing computer executable instructions.
  • the computer executable instructions are executed by the processor, the method in any one of the implementation manners of the first embodiment or the first embodiment is implemented.
  • the embodiment provides a computer storage medium, where the computer executable instructions are stored; and when the computer executable instructions are executed by the processor, the method in any one of the second embodiment or the second embodiment is implemented.
  • the disclosure can transmit part of the customer service flow by using the control information block without affecting the normal service delivery of the FLEXE, and can improve the utilization rate of the delivery channel, thereby improving the service delivery efficiency.

Landscapes

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

Abstract

一种灵活以太网协议中传递业务流的方法、装置和系统。其中，灵活以太网FLEXE协议中传递业务流的方法包括：发送端对预定客户业务流进行封装；所述发送端将封装后的预定客户业务流插入到FLEXE业务时隙中预定类型的控制信息块中，并发送所述预定类型的控制信息块。

Description

灵活以太网协议中传递业务流的方法、装置和系统 技术领域
本公开涉及通信技术领域，例如涉及一种灵活以太网协议中传递业务流的方法、装置和系统。
背景技术
用户网络信息流量的快速增加，促使着通讯网络信息传递带宽的快速发展，通讯设备的接口带宽速度从10兆(M)(单位：比特/秒，后文相同)提高到100M，又提高到1千兆(G)、10G以及100G的带宽速度。市场上已经开始大量商用100G光模块，也研发出了400G光模块。但是，400G光模块价格昂贵，超过了4个100G光模块的价格，导致400G光模块缺少商用的经济价值。为了在100G光模块上传递400G业务，国际标准组织定义了灵活以太网(Flex Ethernet，FLEXE)协议。FLEXE协议将多个100G光模块捆绑起来，形成一个大速度的传递通道。例如，通过FLEXE协议将4个100G光模块捆绑起来，连接到FLEXE垫片(shim)层上，能够形成一个400G的传递通道，等效于1个400G光模块的传递速度。在不增加成本的情况下既满足了400G业务的传递需求，也解决了业务传递的经济价值问题。
客户业务数据在装载到FLEXE shim层上进行承载时，FLEXE上通常会承载一些具有空闲比特(bit)的控制信息块，造成浪费。
发明内容
本申请提供一种灵活以太网协议中传递业务流的方法、装置和系统，能够提高传递通道的利用率，从而提高业务传递效率。
本申请提供一种灵活以太网FLEXE协议中传递业务流的方法，该方法包括：
发送端对预定客户业务流进行封装；
所述发送端将封装后的预定客户业务流插入到FLEXE业务时隙中预定类型的控制信息块中，并发送所述预定类型的控制信息块。
本申请还提供了一种灵活以太网FLEXE协议中传递业务流的方法，该方法包括：
接收端提取FLEXE业务时隙中预定类型的控制信息块中的信息内容；
所述接收端根据所提取的信息内容获取预定客户业务流。
本申请还提供了一种灵活以太网FLEXE协议中传递业务流的装置，该装置包括：
封装模块，设置为：对预定客户业务流进行封装；
传递模块，设置为：将封装后的预定客户业务流插入到FLEXE业务时隙中预定类型的控制信息块中，并发送所述预定类型的控制信息块。
本申请还提供了一种灵活以太网FLEXE协议中传递业务流的装置，该装置包括：
提取模块，设置为：提取FLEXE业务时隙中预定类型的控制信息块中的信息内容；
获取模块，设置为：根据所提取的信息内容获取预定客户业务流。
本申请还提供了一种灵活以太网FLEXE协议中传递业务流的装置，该装置包括：第一存储器和第一处理器；其中，
所述第一存储器设置为：保存可执行指令；所述第一处理器设置为：执行所述可执行指令，并实现如下操作：
对预定客户业务流进行封装；
将封装后的预定客户业务流插入到FLEXE业务时隙中预定类型的控制信息块中，并发送所述预定类型的控制信息块。
本申请还提供了一种灵活以太网FLEXE协议中传递业务流的装置，该装置包括：第二存储器和第二处理器；其中，
所述第二存储器设置为：保存可执行指令；所述第二处理器设置为：执行所述可执行指令，并实现如下操作：
提取FLEXE业务时隙中预定类型的控制信息块中的信息内容；
根据所提取的信息内容获取预定客户业务流。
本申请还提供了一种灵活以太网FLEXE协议中传递业务流的系统，该系统包括：发送端设备和接收端设备；其中，
所述发送端设备设置为：对预定客户业务流进行封装；将封装后的预定客户业务流插入到FLEXE业务时隙中预定类型的控制信息块中，并将所述预定类型的控制信息块发送给所述接收端设备；
所述接收端设备设置为：提取所述FLEXE业务时隙中所述预定类型的控制 信息块中的信息内容；根据所提取的信息内容获取预定客户业务流。
本申请还提供了一种计算机可读存储介质，存储有计算机可执行指令，所述计算机可执行指令用于执行上述方法。
本申请的实施例可以在不影响FLEXE正常业务传递的情况下，利用控制信息块传递部分客户业务流，能够提高传递通道的利用率，从而提高业务传递效率。
本申请的其它特征和优点将在随后的说明书中阐述，并且，部分地从说明书中变得显而易见，或者通过实施本申请而了解。本申请的目的和其他优点可通过在说明书、权利要求书以及附图中所指出的结构来实现和获得。
附图说明
图1是本申请一实施例提供的FLEXE协议应用示意图；
图2是本申请一实施例提供的FLEXE协议开销块和数据块排列位置示意图；
图3是本申请一实施例提供的FLEXE协议业务在多物理通道上分配示意图；
图4是本申请一实施例提供的FLEXE协议承载客户业务的示意图；
图5是本申请一实施例提供的FLEXE层中插入空闲信息块的示意图；
图6是本申请一实施例提供的客户业务64/66编码原理示意图；
图7是本申请一实施例提供的空闲信息块结构示意图；
图8是本申请一实施例提供的FLEXE协议中传递业务流的方法的流程图；
图9是本申请另一实施例提供的FLEXE协议中传递业务流的方法的流程图；
图10是本申请一实施例提供的发送端通过空闲信息块传递一条背景客户业务流的示意图；
图11是本申请一实施例提供的接收端从空闲信息块中恢复背景业务流的示意图；
图12是本申请一实施例提供的在空闲信息块中传递4条背景客户业务流的示意图；
图13是本申请一实施例提供的在一个成员的空闲信息块中传递背景客户业务流的示意图；
图14是本申请一实施例提供的在多个成员的空闲信息块中传递背景客户业务流的示意图；
图15是本申请一实施例提供的FLEXE协议中传递业务流的装置的示意图；
图16是本申请另一实施例提供的FLEXE协议中传递业务流的装置的示意图；
图17是本申请另一实施例提供的FLEXE协议中传递业务流的装置的示意图；
图18是本申请另一实施例提供的FLEXE协议中传递业务流的装置的示意图；
图19是本申请一实施例提供的FLEXE协议中传递业务流的系统的示意图。
具体实施方式
下文中将结合附图对本申请的实施例进行说明。
在附图的流程图示出的步骤可以在诸如一组计算机可执行指令的计算机系统中执行。并且，虽然在流程图中示出了逻辑顺序，但是在某些情况下，可以以不同于此处的顺序执行所示出或描述的步骤。
图1是本申请一实施例提供的FLEXE协议应用示意图。图1中左边的FLEXE shim层和4个100G光模块可以看成是发送端，右边的4个100G光模块和FLEXE shim层可以看成是接收端。由于客户业务流在FLEXE上选择固定时隙数，是一种刚性管道，当客户流量变小时，由于客户业务流独占FLEXE shim层上的时隙，为了适配速度，会插入空闲信息块，造成传递通道的利用率低，形成浪费。
首先简单介绍一下FLEXE协议。
FLEXE协议按照物理层100G速率来定义。在光模块中，在发送100G的数据报文前，是将数据报文进行64/66编码，即：将64比特(bit)的数据扩展成66比特的信息块，增加的2比特位于66比特的信息块的最前面，作为66比特的信息块的开始标志，然后以66比特的信息块的方式从光口发送出去。在接收 时，光口从接收到的数据流中辨别出66比特的信息块，然后从66比特的信息块中恢复出原始的64比特的数据，重新组装出数据报文来。
FLEXE协议处于64比特数据到66比特的信息块的转换层，在发送66比特的信息块前，对66比特的信息块进行排序和规划。如图2所示，对于100G带宽速度的业务，每20个66比特的信息块划分为一个信息块组，每个66比特的信息块分别代表1个时隙，即：一个信息块组中包含20个时隙；每个时隙代表5G带宽的业务速度。发送66比特的信息块时，每发送完1023个信息块组(1023×20个信息块)，插入一个FLEXE开销块(如图2中斜线填充的块)。插入开销块后，继续发送信息块，发送完第二个1023×20个信息块后，再插入开销块，以此类推，这样在发送信息块的过程中，会周期性地插入开销块，相邻两个开销块的间隔是1023×20个信息块。
当4路100G的物理层捆绑成一个400G的逻辑业务带宽时，如图3所示，按信息块组(20个信息块)进行分割，每个信息块组轮流分配到不同物理通道，比如图3所示，每4个信息块组分别分配到4路100G的物理层。每个物理层仍按照每20个信息块分别组成一个信息块组，每1023个信息块组插入一个开销块的方式进行发送。开销块起到定位作用，4个成员(每个100G的物理层可以称为一个成员)以开销块为基准进行定位和排序，来恢复业务。在FLEXE协议的shim层，4路20个信息块拼装成一个由80个信息块组成的信息块组，信息块组中有80个时隙。客户业务在这80个时隙中进行传递，每个时隙带宽是5G，共400G的业务传递带宽。
FLEXE协议承载客户业务的过程如下：首先对客户业务进行64/66编码，如图4所示，分别对客户1～n的业务流进行64/66编码。64/66编码后，可以对业务速率进行适配，插入空闲信息块来保证适配后的速度和FLEXE的承载速度相吻合。确定每个客户业务流由FLEXE shim层中哪些时隙进行承载。如果由一个时隙承载，则承载速度就是5G(比特/秒，bit/s)。如果由m个时隙承载，则是m×5G的承载速度，确定承载的时隙数量和时隙位置后，将适配后的业务流插入到FLEXE shim层中对应位置发送出去。
由于客户业务流可能不是连续的，而是一段一段的，例如客户业务是以太网报文，一个个独立的报文，报文之间有间隔。经过64/66编码，将业务流分成一段一段的数据流，可以确定业务流的起始位置和终止。经过64/66编码后，可 以在每段数据流之间插入空闲信息块，空闲信息块起到速度适配功能。当客户业务流速度大时，插入的空闲信息块少些；当客户业务流速度小时，插入的空闲信息块多些，这样插入空闲信息块后，保证业务流的速度完全吻合FLEXE shim层的承载速度要求，由FLEXE shim层发送出去。
由于客户业务流中插入有空闲信息块，这样在FLEXE shim层中，有些时隙位置承载的是空闲信息块，而非真正的有效数据，如图5所示，其中横线填充的块就是空闲信息块。当客户业务速度越小，空闲信息块就越多。FLEXE shim层中承载空闲信息块，实际就是一种损耗(或浪费)。
客户业务进行64/66编码的编码规则见图6。如图6所示，64/66编码后信息块的长度是66bit，其中前面两个bit是信息块属性指示比特，用于指示信息块属性。当两个信息块属性指示比特内容为：01时，表示该信息块是一个纯数据块，信息块中后面64个比特(8个字节)全部是客户数据信息，8个字节长度的客户数据信息，从字节D0到字节D7。当两个信息块属性指示比特内容为：10时，表示该信息块是一个控制信息块，具体是哪种控制信息块，则由信息块中第一个字节的内容来决定。如图6中第三行：信息块属性指示比特内容为10，第一个字节的内容是0x78(十六进制的78)，表示该信息块是一个数据报文的第一个数据块(起始块)，信息块含义是S0D1D2D3D4D5D6D7，S表示起始块，起始标志在第一个字节上，后面7个字节是客户数据信息。以此类推：信息块属性指示比特内容为10，第一个字节内容是0xFF(十六进制的FF)，表示该信息块是一个数据报文的最后一个数据块(终止块)，信息块含义是D0D1D2D3D4D5D6T7，T是终止标志，终止标志在第八个字节上，前面7个字节是客户数据信息；信息块属性指示比特内容为10，第一个字节内容是0xAA(十六进制的AA)，表示该信息块是一个数据报文的最后一个数据块(终止块)，信息块含义是D0D1T2C3C4C5C6C7，T是终止标志，终止标志在第三个字节上，前面2个字节是客户数据信息，后面5个字节(C3～C7)是附属信息，不用关心；信息块属性指示比特内容为10，第一个字节内容是0x87(十六进制的87)，表示该信息块是一个数据报文的最后一个数据块(终止块)，信息块含义是T0C1C2C3C4C5C6C7，T是终止标志，终止标志在第一个字节上，后面7个字节是(C1～C7)是附属信息，不用关心，该信息块只是用来指示一个客户信息终止，不携带任何客户数据。
有个特殊的信息块，信息块属性指示比特内容为10，第一个字节内容是0x1E(十六进制的1E)，表示该信息块是一个空闲信息块(可称为idle块)，第一个字节表示空闲信息块，后面7个字节是附属信息，不用关心。如图7所示，该空闲信息块只是用来调整客户业务流的速度，不携带任何客户业务数据。当客户业务速率变小时，就需要多插入空闲信息块进行速度调整。
实施例一
本实施例提供一种FLEXE协议中传递业务流的方法。如图8所示，该方法包括以下步骤。
步骤110、发送端对预定客户业务流进行封装。
步骤120、所述发送端将封装后的预定客户业务流插入到FLEXE业务时隙中预定类型的控制信息块中发送。
本实施例将控制信息块利用起来，用来承载额外的业务流，提高了FLEXE shim层的承载效率，产生了额外经济价值。
本实施例中，控制信息块可以是指信息块属性指示比特内容为10的信息块；控制信息块的类型可以由该控制信息块第一个字节的内容确定。
本实施例中，所述预定客户业务流可以是一条或多条。当有多条预定客户业务流时，可以通过不同的标识来区别不同的预定客户业务流。
本实施例中，步骤110和120都可以是一个持续的过程，两个步骤可并行执行，比如一边持续对预定客户业务流进行封装，一边持续监视FLEXE业务时隙中预定类型的控制信息块，一旦发现预定类型的控制信息块就将已经封装的预定客户业务流插入该控制信息块中。
本实施例中，预定类型的控制信息块可以包括一个或多个类型，不同类型的控制信息块中，承载所述预定客户业务流(或者说可以插入封装好的预定客户业务流)的字节的个数和位置可以根据该类型确定。
本实施例中，封装可以采用以下任一种方式：64/66编码的封装、以太网报文方式的封装以及高级数据链路控制(High-Level Data Link Control，HDLC)报文格式的封装。发送端可以和接收端约定封装方式，或默认封装方式。
在一实施例中，所述预定类型的控制信息块可以但不限于为空闲信息块。
在一实施例中，所述预定类型的控制信息块可以是指第一个字节内容是 0x1E(十六进制的1E)的控制信息块。
在一实施例中，可以利用空闲信息块的后面7个字节中部分或全部字节来传递预定客户业务流，避免了带宽浪费，提高了传递效率。
在一实施例中，也可以采用其它类型的控制信息块，作为所述预定类型的控制信息块。
在一实施例中，所述发送端将封装后的预定客户业务流插入到FLEXE业务时隙中预定类型的控制信息块中，可以包括：
所述发送端确定FLEXE业务时隙中承载所述预定客户业务流的时隙；
所述发送端判断所述承载所述预定客户业务流的时隙中的控制信息块是否是预定类型的控制信息块；
所述发送端在所述承载所述预定客户业务流的时隙中是预定类型的控制信息块的情况下，将所述封装后的预定客户业务流插入到所述预定类型的控制信息块中。
本实施例中，可以根据预定规则确定用来承载所述预定客户业务流的时隙位置。比如当只有1条预定客户业务流时，可以将FLEXE shim层中所有时隙位置都确定为承载所述预定客户业务流的时隙位置。再比如当有4个成员，2条预定客户业务流时，可以将FLEXE shim层中前40个时隙位置确定为承载第一条预定客户业务流的时隙位置，后40个时隙位置确定为承载第二条预定客户业务流的时隙位置。这里只是给出了一种可行的范例，实际应用中不限于此，可自行设置上述预定规则。
在一实施例中，所述承载预定客户业务流的时隙可以为一个或多个FLEXE成员的时隙。
在一实施例中，当所述预定客户业务流为一条时，所述封装后的预定客户业务流可以承载在全部或部分时隙上；
当所述预定客户业务流为多条时，封装后的多条预定客户业务流可以承载在不同时隙上。
在一实施例中，也可以在发送端预存用来承载所述预定客户业务流的时隙位置。
在一实施例中，所述预定客户业务流可以但不限于是优先级最低的客户业务流。
有一种客户业务是低优先级且非保证带宽的业务，这类业务优先级最低，并且不需要保证带宽(不保证及时传送)。当网络带宽拥塞时，就会停止传递这类业务，将网络带宽让位给高优先级业务；当网络带宽空闲时，传递这类业务。在后文中将这类业务称为背景客户业务。
在一实施例中，所述预定客户业务流可以但不限于是背景客户业务流。
在一实施例中，所述预定客户业务流也可以包含其它客户业务流。
在一实施例中，所述发送端将封装后的预定客户业务流插入到FLEXE业务时隙中预定类型的控制信息块中，可以包括：
所述发送端根据单位时间内FLEXE业务时隙中预定类型的控制信息块的个数，对封装后的预定客户业务流进行速度调整；
所述发送端将速度调整后的预定客户业务流插入到FLEXE业务时隙中预定类型的控制信息块中。
在一实施例中，单位时间内的个数可以是指当前时刻所检测到的单位时间内的个数，也可以是指对一定长度的历史数据进行统计，所得到的单位时间内的平均个数。
在一实施例中，所述对封装后的预定客户业务流进行速度调整，可以包括：
通过在封装后的预定客户业务流中插入空闲信息，对所述封装后的预定客户业务流进行速度调整。
在一实施例中，空闲信息可以是预定格式的比特序列等，且插入位置可以在预定客户业务流的数据之前或之后，或指定位置。
在一实施例中，当预定类型的控制信息块比较多时，可以提供较高的传输速度，如果预定客户业务流本身的速度低于该传输速度，则可以通过插入空闲信息或只使用预定类型的控制信息块中部分字节传输的方式，来使预定客户业务流的速度和上述传输速度匹配；当预定类型的控制信息块比较多时，如果所提供的传输速度低于预定客户业务流本身的速度，则可以通过缓存预定客户业务流或增加预定类型的控制信息块等方式，来使预定客户业务流的速度和上述传输速度匹配。
在一实施例中，所述发送端将封装后的预定客户业务流插入到FLEXE业务时隙中预定类型的控制信息块中，可以包括：
所述发送端将封装后的预定客户业务流插入到FLEXE业务时隙中预定类型 的控制信息块的后七个字节的全部或部分字节里。
在一实施例中，所述预定类型的控制信息块的后七个字节中，用于插入(或者说用于承载)所述封装后的预定客户业务流的字节根据该控制信息块的类型确定。比如空闲信息块可以后7个字节都用于承载预定客户业务流；再比如第一个字节内容是0xAA(十六进制的AA)的控制信息块，可以后面5个字节用于承载预定客户业务流。
实施例二
本实施例提供一种FLEXE协议中传递业务流的方法。如图9所示，该方法包括：
步骤210、接收端提取FLEXE业务时隙中预定类型的控制信息块中的信息内容。
步骤220、所述接收端根据所提取的信息内容获取预定客户业务流。
本实施例将控制信息块利用起来，用来承载额外的业务流，提高了FLEXE shim层的承载效率，产生了额外经济价值。
本实施例中，控制信息块可以是指信息块属性指示比特内容为10的信息块；控制信息块的类型可以由该控制信息块第一个字节的内容确定。
本实施例中，根据所提取的信息内容获取所述预定客户业务流可以包括：对所提取的信息内容进行发送端所进行的适配工作的反向处理，比如删除速度调整时插入的空闲信息块，并按照默认方式或者和发送端约定的方式进行解封装。
本实施例中，所述预定客户业务流可以是一条或多条。
本实施例中，步骤210和220都可以是一个持续的过程。
在一实施例中，所述预定类型的控制信息块可以但不限于为空闲信息块。
在一实施例中，所述预定类型的控制信息块是指第一个字节内容是0x1E(十六进制的1E)的控制信息块。
在一实施例中，也可以采用其它类型的控制信息块，作为所述预定类型的控制信息块。
在一实施例中，在所述步骤210之前，还可以包括：
所述接收端确定在FLEXE业务时隙中承载预定客户业务的时隙位置。
在一实施例中，可以根据预定规则确定用来承载所述预定客户业务流的时隙位置。
在一实施例中，也可以在接收端预存用来承载所述预定客户业务流的时隙位置或由发送端告知接收端承载所述预定客户业务流的时隙位置。
在一实施例中，所述预定客户业务流可以但不限于是优先级最低的客户业务流。
本实施例中，所述预定客户业务流可以但不限于是背景客户业务流。
在一实施例中，所述预定客户业务流也可以包含其它客户业务流。
在一实施例中，所述接收端根据所提取的信息内容获取预定客户业务流，可以包括：
所述接收端解封装所述信息内容，将解封装后的信息内容按照预定客户业务流的标识进行拼接，得到至少一个所述预定客户业务流。
在一实施例中，预定客户业务流中携带有本业务流的标识，通过该标识接收端可以区分开不同的预定客户业务流；将所提取的属于同一个预定客户业务流的信息内容进行拼接，可以恢复出预定客户业务流。
在一实施例中，预定客户业务流的起始和结束可以用指定标识表示，以便接收端识别出起始位置和结束位置。
在一实施例中，在所述接收端解封装所述信息内容之前，还可以包括：
所述接收端丢弃插入所述预定客户业务流的空闲信息。
在一实施例中，所述接收端提取FLEXE业务时隙中预定类型的控制信息块中的信息内容，可以包括：
接收端确定FLEXE业务时隙中承载所述预定客户业务流的时隙；
所述接收端判断所述承载所述预定客户业务流的时隙中的控制信息块是否是预定类型的控制信息块；
所述接收端在所述承载所述预定客户业务流的时隙中的控制信息块是预定类型的控制信息块的情况下，从所述预定类型的控制信息块中提取信息内容。
在一实施例中，所述承载预定客户业务流的时隙可以为一个或多个FLEXE成员的时隙。
在一实施例中，当所述预定客户业务流为一条时，所述封装后的预定客户业务流可以承载在全部或部分时隙上；
当所述预定客户业务流为多条时，封装后的多条预定客户业务流可以承载在不同时隙上。
在一实施例中，所述接收端提取FLEXE业务时隙中预定类型的控制信息块中的信息内容，可以包括：
所述接收端从FLEXE业务时隙中预定类型的控制信息块的后七个字节的全部或部分字节里提取信息内容。
在一实施例中，所述预定类型的控制信息块中，用于提取信息内容的字节(即用于承载预定客户业务流的字节)可以根据该控制信息块的类型确定。比如空闲信息块可以后7个字节都用于承载预定客户业务流；再比如第一个字节内容是0xAA(十六进制的AA)的控制信息块，可以后面5个字节用于承载预定客户业务流。
下面用三个实施示例来说明上述实施例。这三个实施示例中，预定客户业务流为背景客户业务流；预定类型的控制信息块是空闲信息块。
实施示例1
在发送端，对背景客户业务流进行适配，适配是将背景客户业务流进行处理，满足插入到空闲信息块的需要，适配包括背景业务流的封装和速度调整(即速度适配)。
如图10所示，由于背景客户业务流可能是一种或多种类型以及一种或多种速度的数据，无法直接插入到空闲信息块(即图10中横线填充的块)中，因此需要对背景客户业务流先进行封装，可以是64/66编码的封装，也可以是以太网报文方式的封装，或HDLC报文格式的封装。
经过封装后，就可以对封装的业务流进行速度调整，满足插入到空闲信息块的速度要求。速度调整就在背景客户业务流中插入一些空闲信息，速度调整后就满足在FLEXE shim层的插入速度需求。由于FLEXE shim层的空闲信息块的数量是动态变化，某个瞬时刻空闲信息块的数量多，某个瞬时刻空闲信息块的数量少，因此要求速度调整也要及时动态变化。
对背景客户业务流进行适配后，确定FLEXE shim层中哪些时隙位置用来承载背景客户业务流，然后判断这些时隙位置的信息块是否是空闲信息块。如果是空闲信息块，则将适配后的背景客户业务流插入到空闲信息块中后面7个字 节中。一个空闲信息块中后面有7个字节，一次可以承载7个字节的背景客户业务流。按照同样的方法，检测每个可以承载背景客户业务流的时隙位置，检测该时隙位置是否是空闲信息块。如果是则承载7个字节的背景客户业务流，当4个信息块组中，所有空闲信息块都插入承载背景客户业务流后，FLEXE shim层就可以发送出去。
在接收端，如图11所示，确定FLEXE shim层中哪些时隙位置可以承载背景客户业务流，然后判断该时隙位置是否是空闲信息块(即图11中横线填充的块)。如果是空闲信息块，则从空闲信息块中后7个字节位置中提取出背景客户业务流。以此类推，从所有承载背景客户业务的时隙位置的空闲信息块中提取背景客户业务流，完成提取工作。对提取的背景客户业务流进行恢复操作：丢掉速度调整时插入的空闲信息，然后解封装，恢复出原始的背景客户业务流。
图10和图11分别是在通过FLEXE shim层的时隙(即所有成员的时隙)传递1条背景客户业务流的情况下，发送端和接收端的示意图。而在本实施例中，背景客户业务流可能有1条背景客户业务流，也可能有多条背景客户业务流。背景客户业务流可以在FLEXE shim层上插入，也可以在FLEXE每个成员上插入。背景客户业务流可以在空闲信息块上进行传递，也可以在其他控制信息块(如o码信息块或自定义的控制信息块等一类或多类控制信息块)上传递。
在FLEXE shim层有多个时隙，背景客户业务流可以在所有时隙位置进行传递，也可以在部分时隙位置进行传递。一条背景客户业务流可以占用所有时隙位置，也可以是多条背景客户业务流分别占有不同时隙位置。
实施示例2
如图12所示，有4条背景客户业务流(图12中的背景客户1业务流～背景客户4业务流)，第1条背景客户业务流由FLEXE shim层中前20个时隙位置承载；第2条背景客户业务流由FLEXE shim层中第21～40个时隙位置承载；第3条背景客户业务流由FLEXE shim层中第41～60个时隙位置承载；第4条背景客户业务流由FLEXE shim层中后20个时隙位置承载。
图12展示了发送端和接收端的做法，其中业务适配是发送端的做法，朝下的箭头表示的是发送端的处理流程；业务提取是接收端的做法，朝上的箭头表示的是接收端的处理流程。图12中横线填充的块为空闲信息块，发送端在前20 个时隙的空闲信息块中插入背景客户业务流1、在第21～40个时隙的空闲信息块中插入背景客户业务流2、在第41～60个时隙的空闲信息块中插入背景客户业务流3以及在最后20个时隙的空闲信息块中插入背景客户业务流4；接收端从前20个时隙的空闲信息块中提取背景客户业务流1、从第21～40个时隙的空闲信息块中提取背景客户业务流2、从第41～60个时隙的空闲信息块中提取背景客户业务流3以及从最后20个时隙的空闲信息块中提取背景客户业务流4。
实施示例3
如图13所示，背景客户业务流直接在FLEXE的一个成员上进行传递。在实现时，检测FLEXE成员中每个信息块是否是空闲信息块(即图13中横线填充的块)，如果是空闲信息块，则在空闲信息块中插入7个字节的背景客户业务流，背景客户业务流在发送端的插入位置和在接收端的提取位置为FLEXE一个成员(即图13中的第一路)的时隙位置。
实施示例4
如图14所示，背景业务流在FLEXE的所有成员上进行传递。在实现时，检测FLEXE的所有成员中每个信息块是否是空闲信息块(即图14中横线填充的块)，如果是空闲信息块，则在空闲信息块中插入7个字节的背景客户业务流，背景客户业务流在发送端的插入位置和在接收端的提取位置为FLEXE所有成员的时隙位置。
实施例三
本实施例提供一种灵活以太网FLEXE协议中传递业务流的装置。如图15所示，该装置包括：
封装模块31，设置为：对预定客户业务流进行封装；
传递模块32，设置为：将封装后的预定客户业务流插入到FLEXE业务时隙中预定类型的控制信息块中，并发送所述预定类型的控制信息块。
在一实施例中，所述预定类型的控制信息块可以但不限于为空闲信息块。
在一实施例中，所述预定客户业务流可以但不限于是优先级最低的客户业 务流。
在一实施例中，所述传递模块32是设置为通过如下方式将封装后的预定客户业务流插入到FLEXE业务时隙中预定类型的控制信息块中：
根据单位时间内FLEXE业务时隙中预定类型的控制信息块的个数，对封装后的预定客户业务流进行速度调整；
将速度调整后的预定客户业务流插入到FLEXE业务时隙中预定类型的控制信息块中。
在一实施例中，所述传递模块32是设置为通过如下方式对封装后的预定客户业务流进行速度调整：
通过在封装后的预定客户业务流中插入空闲信息，对所述封装后的预定客户业务流进行速度调整。
在一实施例中，所述传递模块32是设置为通过如下方式将封装后的预定客户业务流插入到FLEXE业务时隙中预定类型的控制信息块中：
确定FLEXE业务时隙中承载所述预定客户业务流的时隙；
判断所述承载所述预定客户业务流的时隙中的控制信息块是否是预定类型的控制信息块；
在所述承载所述预定客户业务流的时隙中的控制信息块是预定类型的控制信息块的情况下，将所述封装后的预定客户业务流插入到所述预定类型的控制信息块中。
在一实施例中，所述承载所述预定客户业务流的时隙可以为一个或多个FLEXE成员的时隙。
在一实施例中，当所述预定客户业务流为一条时，所述封装后的预定客户业务流可以承载在全部或部分时隙上；
当所述预定客户业务流为多条时，封装后的多条预定客户业务流承载在不同时隙上。
在一实施例中，所述传递模块32是设置为通过如下方式将封装后的预定客户业务流插入到FLEXE业务时隙中预定类型的控制信息块中：
将封装后的预定客户业务流插入到FLEXE业务时隙中预定类型的控制信息块的后七个字节的全部或部分字节里。
在一实施例中，所述预定类型的控制信息块后七个字节中，用于插入所述 封装后的预定客户业务流的字节可以根据该控制信息块的类型确定。
其它实现细节可参见上述任意实施例。
实施例四
本实施例提供一种灵活以太网FLEXE协议中传递业务流的装置。如图16所示，该装置包括：
提取模块41，设置为：提取FLEXE业务时隙中预定类型的控制信息块中的信息内容；
获取模块42，设置为：根据所提取的信息内容获取预定客户业务流。
在一实施例中，所述预定类型的控制信息块可以但不限于为空闲信息块。
在一实施例中，所述预定客户业务流可以但不限于是优先级最低的客户业务流。
在一实施例中，所述获取模块42是设置为：
解封装所述信息内容，将解封装后的信息内容按照预定客户业务流的标识进行拼接，得到至少一个所述预定客户业务流。
在一实施例中，所述装置还包括丢弃模块，设置为在获取模块解封装所述信息内容前，丢弃插入所述预定客户业务流的空闲信息。
在一实施例中，所述提取模块41是设置为：
确定FLEXE业务时隙中承载所述预定客户业务流的时隙；
判断所述承载所述预定客户业务流的时隙中的控制信息块是否是预定类型的控制信息块；
在所述承载所述预定客户业务流的时隙中的控制信息块是预定类型的控制信息块的情况下，从所述预定类型的控制信息块中提取信息内容。
在一实施例中，所述承载预定客户业务流的时隙可以为一个或多个FLEXE成员的时隙。
在一实施例中，当所述预定客户业务流为一条时，所述封装后的预定客户业务流可以承载在全部或部分时隙上；
当所述预定客户业务流为多条时，封装后的多条预定客户业务流可以承载在不同时隙上。
在一实施例中，所述提取模块41是设置为：
从FLEXE业务时隙中预定类型的控制信息块的后七个字节的全部或部分字节里提取信息内容。
在一实施例中，所述预定类型的控制信息块中，用于提取信息内容的字节可以根据该控制信息块的类型确定。
其它实现细节可参见上述任意实施例。
实施例五
本实施例提供一种灵活以太网FLEXE协议中传递业务流的装置。如图17所示，该装置包括：
第一存储器51和第一处理器52；其中，
所述第一存储器51设置为：保存可执行指令；
所述第一处理器51设置为：执行所述可执行指令，并实现如下操作：
对预定客户业务流进行封装；
将封装后的预定客户业务流插入到FLEXE业务时隙中预定类型的控制信息块中，并发送预定类型的控制信息块。
在一实施例中，所述预定类型的控制信息块可以但不限于为空闲信息块。
在一实施例中，所述预定客户业务流可以但不限于是优先级最低的客户业务流。
在一实施例中，所述将封装后的预定客户业务流插入到FLEXE业务时隙中预定类型的控制信息块中，可以包括：
根据单位时间内FLEXE业务时隙中预定类型的控制信息块的个数，对封装后的预定客户业务流进行速度调整；
将速度调整后的预定客户业务流插入到FLEXE业务时隙中预定类型的控制信息块中。
在一实施例中，所述对封装后的预定客户业务流进行速度调整可以包括：
通过在封装后的预定客户业务流中插入空闲信息，对所述封装后的预定客户业务流进行速度调整。
在一实施例中，所述将封装后的预定客户业务流插入到FLEXE业务时隙中预定类型的控制信息块中，可以包括：
确定FLEXE业务时隙中承载所述预定客户业务流的时隙；
判断所述承载所述预定客户业务流的时隙中的控制信息块是否是预定类型的控制信息块；
在所述承载所述预定客户业务流的时隙中的控制信息块是预定类型的控制信息块的情况下，将所述封装后的预定客户业务流插入到所述预定类型的控制信息块中。
在一实施例中，所述承载预定客户业务流的时隙可以为一个或多个FLEXE成员的时隙。
在一实施例中，当所述预定客户业务流为一条时，所述封装后的预定客户业务流可以承载在全部或部分时隙上；
当所述预定客户业务流为多条时，封装后的多条预定客户业务流可以承载在不同时隙上。
在一实施例中，所述将封装后的预定客户业务流插入到FLEXE业务时隙中预定类型的控制信息块中，可以包括：
所述将封装后的预定客户业务流插入到FLEXE业务时隙中预定类型的控制信息块的后七个字节的全部或部分字节里。
在一实施例中，所述预定类型的控制信息块后七个字节中，用于插入所述预定客户业务流的字节可以根据该控制信息块的类型确定。
其它实现细节可参见上述任意实施例。
实施例六
本实施例提供一种灵活以太网FLEXE协议中传递业务流的装置。如图18所示，该装置包括：
第二存储器61和第二处理器62；其中
所述第二存储器61设置为：保存可执行指令；
所述第二处理器62设置为：执行所述可执行指令，并实现如下操作：
提取FLEXE业务时隙中预定类型的控制信息块中的信息内容；
根据所提取的信息内容获取预定客户业务流。
在一实施例中，所述预定类型的控制信息块可以但不限于为空闲信息块。
在一实施例中，所述预定客户业务流可以但不限于是优先级最低的客户业务流。
在一实施例中，所述根据所提取的信息内容获取所述预定客户业务流，可以包括：
解封装所述信息内容，将解封装后的信息内容按照预定客户业务流的标识进行拼接，得到所述预定客户业务流。
在一实施例中，所述解封装所述信息内容前还可以包括：
丢弃插入所述预定客户业务流的空闲信息。
在一实施例中，所述提取FLEXE业务时隙中预定类型的控制信息块中的信息内容，可以包括：
确定FLEXE业务时隙中承载所述预定客户业务流的时隙；
在所确定的时隙中的控制信息块是预定类型的控制信息块的情况下，从所述预定类型的控制信息块中提取信息内容。
在一实施例中，所述承载预定客户业务流的时隙可以为一个或多个FLEXE成员的时隙。
在一实施例中，当所述预定客户业务流为一条时，所述封装后的预定客户业务流可以承载在全部或部分时隙上；
在一实施例中，当所述预定客户业务流为多条时，封装后的多条预定客户业务流可以承载在不同时隙上。
在一实施例中，所述提取FLEXE业务时隙中预定类型的控制信息块中的信息内容，可以包括：
从FLEXE业务时隙中预定类型的控制信息块的后七个字节的全部或部分字节里提取信息内容。
在一实施例中，所述预定类型的控制信息块中，用于提取信息内容的字节可以根据该控制信息块的类型确定。
其它实现细节可参见上述任意实施例。
实施例七
本实施例提供一种利用灵活以太网协议传递业务流的系统。如图19所示，该系统包括：
发送端设备71和接收端设备72；
所述发送端设备71设置为：对预定客户业务流进行封装；将封装后的预定 客户业务流插入到FLEXE业务时隙中预定类型的控制信息块中，并将所述预定类型的控制信息块发送给所述接收端设备72；
所述接收端设备72设置为：提取所述FLEXE业务时隙中预定类型的控制信息块中的信息内容；根据所提取的信息内容获取所述预定客户业务流。
本实施例中，发送端设备的其它实现细节可参见实施例一、三以及五；接收端设备的其它实现细节可参见实施例二、四以及六。
实施例八
本实施例提供一种计算机存储介质，存储有计算机可执行指令；所述计算机可执行指令被处理器执行时实现上述实施例一或实施例一中的任一实现方式中的方法。
实施例九
本实施例提供一种计算机存储介质，存储有计算机可执行指令；所述计算机可执行指令被处理器执行时实现上述实施例二或实施例二中的任一实现方式中的方法。
虽然本申请所揭露的实施方式如上，但所述的内容仅为便于理解本申请而采用的实施方式，并非用以限定本申请。
工业实用性
本公开可以在不影响FLEXE正常业务传递的情况下，利用控制信息块传递部分客户业务流，能够提高传递通道的利用率，从而提高业务传递效率。

Claims (24)

  1. 一种灵活以太网FLEXE协议中传递业务流的方法，包括：
    发送端对预定客户业务流进行封装；
    所述发送端将封装后的预定客户业务流插入到FLEXE业务时隙中预定类型的控制信息块中，并发送所述预定类型的控制信息块。
  2. 如权利要求1所述的方法，其中，所述预定类型的控制信息块为空闲信息块。
  3. 如权利要求1或2所述的方法，其中，所述预定客户业务流是优先级最低的客户业务流。
  4. 如权利要求1、2或3所述的方法，其中，所述发送端将封装后的预定客户业务流插入到FLEXE业务时隙中预定类型的控制信息块中，包括：
    所述发送端根据单位时间内所述FLEXE业务时隙中所述预定类型的控制信息块的个数，对封装后的预定客户业务流进行速度调整；
    所述发送端将速度调整后的预定客户业务流插入到所述FLEXE业务时隙中所述预定类型的控制信息块中。
  5. 如权利要求4所述的方法，其中，所述对封装后的预定客户业务流进行速度调整，包括：
    通过在所述封装后的预定客户业务流中插入空闲信息，对所述封装后的预定客户业务流进行速度调整。
  6. 如权利要求1所述的方法，其中，所述发送端将封装后的预定客户业务流插入到FLEXE业务时隙中预定类型的控制信息块中，包括：
    所述发送端确定所述FLEXE业务时隙中承载所述预定客户业务流的时隙；
    所述发送端判断所述承载所述预定客户业务流的时隙中的控制信息块是否是预定类型的控制信息块；
    所述发送端在所述承载所述预定客户业务流的时隙中的控制信息块是预定类型的控制信息块的情况下，将所述封装后的预定客户业务流插入到所述预定类型的控制信息块中。
  7. 如权利要求6所述的方法，其中，所述承载所述预定客户业务流的时隙为一个或多个FLEXE成员的时隙。
  8. 如权利要求6所述的方法，其中，
    当所述预定客户业务流为一条时，所述封装后的预定客户业务流承载在全部或部分时隙上；
    当所述预定客户业务流为多条时，封装后的多条预定客户业务流承载在不同时隙上。
  9. 如权利要求1所述的方法，其中，所述发送端将封装后的预定客户业务流插入到FLEXE业务时隙中预定类型的控制信息块中，包括：
    所述发送端将封装后的预定客户业务流插入到FLEXE业务时隙中预定类型的控制信息块的后七个字节的全部或部分字节里。
  10. 如权利要求9所述的方法，其中，所述预定类型的控制信息块的后七个字节中，用于插入所述封装后的预定客户业务流的字节根据所述控制信息块的类型确定。
  11. 一种灵活以太网FLEXE协议中传递业务流的方法，包括：
    接收端提取FLEXE业务时隙中预定类型的控制信息块中的信息内容；
    所述接收端根据所提取的信息内容获取预定客户业务流。
  12. 如权利要求11所述的方法，其中，所述预定类型的控制信息块为空闲信息块。
  13. 如权利要求11或12所述的方法，其中，所述预定客户业务流是优先级最低的客户业务流。
  14. 如权利要求11、12或13所述的方法，其中，所述接收端根据所提取的信息内容获取预定客户业务流，包括：
    所述接收端解封装所述信息内容，将解封装后的信息内容按照所述预定客户业务流的标识进行拼接，得到至少一个所述预定客户业务流。
  15. 如权利要求14所述的方法，其中，在所述接收端解封装所述信息内容之前，还包括：
    所述接收端丢弃插入所述预定客户业务流的空闲信息。
  16. 如权利要求11所述的方法，其中，所述接收端提取FLEXE业务时隙中预定类型的控制信息块中的信息内容，包括：
    接收端确定FLEXE业务时隙中承载所述预定客户业务流的时隙；
    所述接收端判断所述承载所述预定客户业务流的时隙中的控制信息块是否是预定类型的控制信息块；
    所述接收端在所述承载所述预定客户业务流的时隙中的控制信息块是预定类型的控制信息块的情况下，从所述预定类型的控制信息块中提取所述信息内容。
  17. 如权利要求16所述的方法，其中，所述承载所述预定客户业务流的时隙为一个或多个FLEXE成员的时隙。
  18. 如权利要求16所述的方法，其中，
    当所述预定客户业务流为一条时，所述封装后的预定客户业务流承载在全部或部分时隙上；
    当所述预定客户业务流为多条时，封装后的多条预定客户业务流承载在不同时隙上。
  19. 如权利要求11所述的方法，其中，所述接收端提取FLEXE业务时隙中预定类型的控制信息块中的信息内容，包括：
    所述接收端从FLEXE业务时隙中预定类型的控制信息块的后七个字节的全部或部分字节里提取所述信息内容。
  20. 如权利要求19所述的方法，其中，所述预定类型的控制信息块中，用于提取所述信息内容的字节根据所述控制信息块的类型确定。
  21. 一种灵活以太网FLEXE协议中传递业务流的装置，包括：
    封装模块，设置为：对预定客户业务流进行封装；
    传递模块，设置为：将封装后的预定客户业务流插入到FLEXE业务时隙中预定类型的控制信息块中，并发送所述预定类型的控制信息块。
  22. 一种灵活以太网FLEXE协议中传递业务流的装置，包括：
    提取模块，设置为：提取FLEXE业务时隙中预定类型的控制信息块中的信息内容；
    获取模块，设置为：根据所提取的信息内容获取预定客户业务流。
  23. 一种灵活以太网FLEXE协议中传递业务流的系统，包括：发送端设备和接收端设备；其中，
    所述发送端设备设置为：对预定客户业务流进行封装；将封装后的预定客户业务流插入到FLEXE业务时隙中预定类型的控制信息块中，并将所述预定类型的控制信息块发送给所述接收端设备；
    所述接收端设备设置为：提取所述FLEXE业务时隙中所述预定类型的控制信息块中的信息内容；根据所提取的信息内容获取所述预定客户业务流。
  24. 一种计算机可读存储介质，存储有计算机可执行指令，所述计算机可执行指令用于执行权利要求1-20任一项的方法。
PCT/CN2018/089243 2017-05-31 2018-05-31 灵活以太网协议中传递业务流的方法、装置和系统 WO2018219323A1 (zh)

Priority Applications (3)

Application Number Priority Date Filing Date Title
KR1020197038918A KR102266603B1 (ko) 2017-05-31 2018-05-31 플렉시블 이더넷 프로토콜에서 트래픽 플로우를 전달하는 방법, 장치 및 시스템
JP2019558771A JP7027449B2 (ja) 2017-05-31 2018-05-31 フレックスイーサネットプロトコルにおいてトラヒックを伝送する方法、装置及びシステム
EP18809832.1A EP3633887B1 (en) 2017-05-31 2018-05-31 Method, apparatus for delivering traffic flow in flexible ethernet protocol

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710399609.4A CN108988977B (zh) 2017-05-31 2017-05-31 一种灵活以太网协议中传递业务流的方法、装置和系统
CN201710399609.4 2017-05-31

Publications (1)

Publication Number Publication Date
WO2018219323A1 true WO2018219323A1 (zh) 2018-12-06

Family

ID=64454406

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/089243 WO2018219323A1 (zh) 2017-05-31 2018-05-31 灵活以太网协议中传递业务流的方法、装置和系统

Country Status (5)

Country Link
EP (1) EP3633887B1 (zh)
JP (1) JP7027449B2 (zh)
KR (1) KR102266603B1 (zh)
CN (1) CN108988977B (zh)
WO (1) WO2018219323A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112822125A (zh) * 2020-04-08 2021-05-18 中兴通讯股份有限公司 一种业务流的传输方法、装置、设备及存储介质

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111342983B (zh) * 2018-12-18 2022-07-12 深圳市中兴微电子技术有限公司 成员动态处理方法、系统、接收端、管理实体及存储介质
CN109450544B (zh) * 2018-12-27 2020-10-16 中国移动通信集团江苏有限公司 光线路终端olt设备、无源光网络pon数据传送方法

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101605354A (zh) * 2008-06-10 2009-12-16 大唐移动通信设备有限公司 一种上报业务缓存数据量的方法和用户设备
CN101959069A (zh) * 2009-07-20 2011-01-26 中兴通讯股份有限公司 一种利用复用帧传送业务信息及获取业务信息的方法
US20170005949A1 (en) * 2015-06-30 2017-01-05 Ciena Corporation Flexible ethernet client multi-service and timing transparency systems and methods
CN106411454A (zh) * 2015-07-30 2017-02-15 华为技术有限公司 用于数据传输的方法、发送机和接收机

Family Cites Families (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
SE511344C2 (sv) 1996-10-01 1999-09-13 Ericsson Telefon Ab L M Anordning och förfarande avseende hantering av information i ett kommunikationsnät och ett kommunikationsnät innefattande en dylik anordning
US7787502B1 (en) * 2006-06-30 2010-08-31 Cortina Systems Inc. Port multiplexing apparatus and methods
US8340101B2 (en) * 2006-09-25 2012-12-25 Futurewei Technologies, Inc. Multiplexed data stream payload format
US8588209B2 (en) * 2006-09-25 2013-11-19 Futurewei Technologies, Inc. Multi-network compatible data architecture
US8416770B2 (en) * 2009-07-20 2013-04-09 Futurewei Technologies, Inc. Universal service transport transitional encoding
US9609400B2 (en) * 2013-08-22 2017-03-28 Nec Corporation Reconfigurable and variable-rate shared multi-transponder architecture for flexible ethernet-based optical networks
CN106506110B (zh) * 2015-09-06 2020-05-29 中兴通讯股份有限公司 统计复用光传送网方法及装置

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101605354A (zh) * 2008-06-10 2009-12-16 大唐移动通信设备有限公司 一种上报业务缓存数据量的方法和用户设备
CN101959069A (zh) * 2009-07-20 2011-01-26 中兴通讯股份有限公司 一种利用复用帧传送业务信息及获取业务信息的方法
US20170005949A1 (en) * 2015-06-30 2017-01-05 Ciena Corporation Flexible ethernet client multi-service and timing transparency systems and methods
CN106411454A (zh) * 2015-07-30 2017-02-15 华为技术有限公司 用于数据传输的方法、发送机和接收机

Non-Patent Citations (1)

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

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112822125A (zh) * 2020-04-08 2021-05-18 中兴通讯股份有限公司 一种业务流的传输方法、装置、设备及存储介质
CN112822125B (zh) * 2020-04-08 2023-08-01 中兴通讯股份有限公司 一种业务流的传输方法、装置、设备及存储介质

Also Published As

Publication number Publication date
KR20200012974A (ko) 2020-02-05
CN108988977A (zh) 2018-12-11
JP7027449B2 (ja) 2022-03-01
EP3633887A4 (en) 2021-03-10
CN108988977B (zh) 2021-06-08
KR102266603B1 (ko) 2021-06-21
EP3633887B1 (en) 2024-07-17
JP2020519100A (ja) 2020-06-25
EP3633887A1 (en) 2020-04-08

Similar Documents

Publication Publication Date Title
US12074643B2 (en) Data transmission method and apparatus, terminal device and storage medium
CA2382271C (en) Circuit emulation service over an internet protocol network
CN1166246C (zh) 支持有线与无线通信的可变带宽异步传送模式网络接入的系统
US10270696B2 (en) Transmission of data packets of different priority levels using pre-emption
CN100355248C (zh) 一种基于以太网无源光网络的多业务实现方法
WO2018219323A1 (zh) 灵活以太网协议中传递业务流的方法、装置和系统
KR102633193B1 (ko) 메시지 처리 방법 및 관련 장치
US7912078B2 (en) Credit based flow control in an asymmetric channel environment
RU2009134729A (ru) Устройство и способ для управления потоком на основе ограничения скорости для устройства mstp
WO2022267882A1 (zh) 业务处理方法及业务处理设备
WO2006032413A1 (en) Data packet encapsulation protocol
EP4106283A1 (en) Time-sensitive transmission of ethernet traffic between endpoint network nodes
EP1339183B1 (en) Method and device for transporting ethernet frames over a transport SDH/SONET network
WO2020207429A1 (zh) 报文处理方法、装置及计算机可读存储介质
CN101873247B (zh) 一种控制数据传输的管理方法及系统
CN1273745A (zh) 分配系统
WO2023165222A1 (zh) 待映射内容的映射方法、装置、存储介质及电子装置
WO2024032297A1 (zh) 业务信息的处理方法、网络设备及存储介质
CN110417542B (zh) 一种传输客户业务的方法、装置和系统
CN117938738A (zh) 一种通信方法及装置
CN116566542A (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: 18809832

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2019558771

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 20197038918

Country of ref document: KR

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 2018809832

Country of ref document: EP

Effective date: 20200102