WO2018059446A1 - 业务数据传输方法、设备和系统、存储介质 - Google Patents

业务数据传输方法、设备和系统、存储介质 Download PDF

Info

Publication number
WO2018059446A1
WO2018059446A1 PCT/CN2017/103695 CN2017103695W WO2018059446A1 WO 2018059446 A1 WO2018059446 A1 WO 2018059446A1 CN 2017103695 W CN2017103695 W CN 2017103695W WO 2018059446 A1 WO2018059446 A1 WO 2018059446A1
Authority
WO
WIPO (PCT)
Prior art keywords
service
block group
data block
received
data
Prior art date
Application number
PCT/CN2017/103695
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 EP17854896.2A priority Critical patent/EP3522465A4/en
Publication of WO2018059446A1 publication Critical patent/WO2018059446A1/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
    • H04L47/00—Traffic control in data switching networks
    • H04L47/70—Admission control; Resource allocation
    • 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
    • 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/0089—Multiplexing, e.g. coding, scrambling, SONET
    • H04J2203/0094—Virtual Concatenation

Definitions

  • the present invention relates to network communication technologies, and in particular, to a service data transmission method, device and system, and storage medium.
  • 10M unit: bit/second
  • 1G and 10G the interface bandwidth speed of 100G has been reached, and a large number of commercial 100G optical modules have been started on the market.
  • the basic content of the FLEXE protocol is to bundle multiple 100G transmission channels to form a transmission channel with greater bandwidth speed, as shown in Figure 1, through the FLEXE protocol in the MAC layer and physical coding sublayer (PCS, Physical Coding Sub- There is one more layer (FlexE Shim) between the layers, and the four 100G physical channels are bundled by FlexE Shim to form a 400G logical channel, thus solving the transmission requirement of 400G service without increasing the cost. .
  • the FLEXE protocol defines 20 time slots on a single 100G physical line, each time slot bandwidth is 5G, then 4 ⁇ 20 time slots are defined on the 4 ⁇ 100G logical channel, each time slot The bandwidth is also specified as 5G.
  • the number of time slots and the time slot bandwidth defined by the FLEXE protocol can meet the requirements of the optical transport network (OTN, Optical Transport Network).
  • OTN optical Transport Network
  • PTN Packet Transport Network
  • the embodiment of the present invention is to provide a service data transmission method, device, and system, which solves the problem that the PTN service is not applicable to the physical channel of the FlexE.
  • an embodiment of the present invention provides a service data transmission method, where the method includes:
  • the transmitting end determines a bearer slot position for carrying the service data to be transmitted
  • the transmitting end transmits the to-be-transmitted service data according to the bearer slot position and the bearer data block group location.
  • an embodiment of the present invention provides a service data transmission method, where the method includes:
  • the receiving end determines a location of the received data block group for carrying the service to be received
  • the receiving end determines, in the received data block group location, a receiving time slot position for carrying the to-be-received service, and extracts the to-be-received service by using the receiving time slot position.
  • an embodiment of the present invention provides a service data transmission method, where the method includes:
  • the transmitting end determines a bearer slot position for carrying the service data to be transmitted
  • the receiving end determines a receiving data block group location for carrying a service to be received
  • the receiving end determines, in the received data block group location, a receiving time slot position for carrying the to-be-received service, and extracts the to-be-received service by using the receiving time slot position.
  • an embodiment of the present invention provides a sending end device, where the device includes: a first determining module, a second determining module, and a transmitting module;
  • the first determining module is configured to determine a bearer slot position for carrying service data to be transmitted
  • the second determining module is configured to determine a bearer data block group location for carrying the service data to be transmitted;
  • the transmission module is configured to transmit the to-be-transmitted service data according to the bearer slot position and the bearer data block group location.
  • an embodiment of the present invention provides a receiving end device, where the device includes: a third determining module, a fourth determining module, and an extracting module;
  • the third determining module is configured to determine a received data block group location for carrying a service to be received
  • the fourth determining module is configured to determine, in the received data block group location, a receiving time slot position for carrying the to-be-received service;
  • the extracting module is configured to extract the to-be-received service by using the receiving time slot position.
  • the embodiment of the present invention provides a system for carrying a service, where the system includes: a sending end device and a receiving end device;
  • the sending end device is configured to determine a bearer slot position for carrying service data to be transmitted
  • the receiving end device is configured to determine a received data block group location for carrying a service to be received
  • a seventh aspect is a computer storage medium, wherein the computer storage medium stores computer executable instructions, and the computer executable instructions can implement the service data transmission method provided by the one or more technical solutions.
  • the embodiment of the invention provides a service data transmission method, device and system, and a storage medium.
  • the transmitting end additionally increases the configuration of the data block group based on the configuration time slot, and can also implement the The scheduling and data transmission are performed on the granularity of the data block group, so that the transmitting end can configure the transmission of the service data from multiple dimensions, thereby increasing the number of service transmission time slots of the physical channel in the FLEXE protocol, and reducing the slot granularity.
  • the FLEXE protocol meets the scenario requirements of the PTN service.
  • FIG. 1 is a schematic structural diagram of a FLEX network according to an embodiment of the present invention.
  • FIG. 2 is a schematic diagram of coverage of an overhead block according to an embodiment of the present invention.
  • FIG. 3 is a schematic diagram of data transmission of a FLEX network structure according to an embodiment of the present invention.
  • FIG. 4 is a schematic structural diagram of an overhead frame according to an embodiment of the present disclosure.
  • FIG. 5 is a schematic diagram of an overhead frame coverage according to an embodiment of the present disclosure.
  • FIG. 6 is a schematic flowchart of a method for service bearer according to an embodiment of the present disclosure
  • FIG. 7 is a schematic diagram of a FLEX network structure bearer service according to an embodiment of the present invention.
  • FIG. 8 is a schematic flowchart of another method for service bearer according to an embodiment of the present disclosure.
  • FIG. 9 is a schematic flowchart of still another method for service bearer according to an embodiment of the present disclosure.
  • FIG. 10 is a schematic structural diagram of a device at a transmitting end according to an embodiment of the present disclosure.
  • FIG. 11 is a schematic structural diagram of another sending end device according to an embodiment of the present disclosure.
  • FIG. 12 is a schematic structural diagram of a receiving end device according to an embodiment of the present disclosure.
  • FIG. 13 is a schematic structural diagram of a system for carrying a service according to an embodiment of the present invention.
  • 100G data packets are 64/66 encoded before being transmitted, that is, 64-bit data is expanded into 66-bit data blocks, and the added 2-bit data is located at the front of the 66-bit data block.
  • the start flag of the 66-bit data block then sent out from the optical port in the form of a 66-bit data block.
  • the optical port discriminates the 66-bit data block from the received data stream, then recovers the original 64-bit data from the 66-bit data block and reassembles the data message.
  • the FLEXE protocol is in the 64-bit data to 66-bit data block block conversion layer. Before transmitting a 66-bit data block, the transmitting end sorts and plans the 66-bit data block, as shown in Figure 2.
  • the white block represents a 66-bit data block. For a 100G service, every 20 66-bit data blocks are divided into one data block group, and the 20 66-bit data blocks included in each data block group represent 20 time slots. Each time slot represents the traffic speed of the 5G bandwidth.
  • each transmission completes 1023 data block groups, that is, 1023 ⁇ 20 data blocks, and a FLEXE overhead block is inserted, as shown by the black block in FIG.
  • the sender After inserting the FLEXE overhead block, the sender will continue to send data blocks. After the second 1023 ⁇ 20 data blocks are sent, the FLEXE overhead block is inserted. The data length of the FLEXE overhead block is also 66 bits, and so on.
  • the FLEXE overhead block is periodically inserted, and the interval between two adjacent FLEXE overhead blocks is 1023 ⁇ 20 data blocks.
  • a data block group is introduced, and the resource granularity corresponding to the data block group is greater than the resource granularity corresponding to the time slot. In this way, according to the current data volume and/or transmission requirements of the service data, the service data can be transmitted flexibly based on the data block group and/or the time slot.
  • the transmitting end sends all the data block groups to the physical channels of multiple small bandwidth speeds in an average polling manner, so that The data blocks on all physical channels are fully aligned at the time of transmission, and the overhead blocks are inserted at intervals of 1023 data block groups on each physical channel, thereby ensuring that the data blocks and overhead blocks on the physical channel are perfectly aligned.
  • the FLEX network structure shown in FIG. 1 as an example, when four 100G physical channels are bundled into one 400G logical channel, as shown in FIG. 3, the first data block group, that is, the first 20 data blocks.
  • Sending to the first physical channel sending the second data block group, that is, the second 20 data blocks, to the second physical channel, and the third data block group, that is, the third 20 data blocks Send to the third physical channel, send the fourth data block group, that is, the fourth 20 data blocks, to the fourth physical channel, and then the fifth data block group, that is, the fifth 20 data
  • the block is sent to the first physical channel, and so on, and all the data block groups are averaged and polled to the 4 physical channels in a manner of 4 redundancy.
  • the data blocks on the 4 physical channels are fully aligned at the time of transmission, in 4 physics
  • the channels are each 1023 data block groups, and the overhead blocks are inserted simultaneously on the four physical channels, so that the data blocks and the overhead blocks on the four physical channels are completely aligned.
  • each physical channel receives the data block separately and then determines the overhead block location.
  • Each physical channel realigns the data block groups of the four physical channels based on the overhead block position.
  • the data block groups of the four physical channels are aligned according to the position of the overhead block, and are reordered according to the inverse process of the polling allocation at the time of sending: the first data block group after the cost block is obtained from the first physical channel is first sorted. In the front, then the first data block group is sorted after the cost block is obtained from the second physical channel, and the first data block group is sorted after the cost block from the third physical channel.
  • the first data block group is sorted at the end, and then the above process is re-executed.
  • the second data block group is sorted.
  • the data block groups of the four physical channels are reordered into one large logical channel data block group.
  • the data length of a FLEXE overhead block is also 66 bits.
  • the data stream is sent, since an interval block is inserted every 1023 ⁇ 20 data blocks, the overhead block is in the entire data stream.
  • To perform the positioning function that is, to find the overhead block, you can know the location of the first data block group in the service data stream and the location of the subsequent data block group.
  • the content of the current FLEXE overhead block is shown in Figure 4.
  • eight consecutive overhead blocks form an overhead frame. Therefore, as shown in Figure 5, the coverage of an overhead frame is 8 ⁇ 1023 ⁇ 20 data blocks (represented by white blocks) and 8 overhead blocks. (indicated by a black block), in this embodiment, the data block and the overhead block are collectively referred to as an information block, and therefore, an overhead frame coverage is 8 ⁇ (1023 ⁇ 20 + 1) information blocks.
  • an overhead block is composed of a 2-bit block flag and 64-bit block contents.
  • the block flag is located in the first 2 columns, the next 64 columns are the block contents, the block flag of the first overhead block is 10, and the block flags of the following 7 overhead blocks are 01 or SS (SS indicates that the content is uncertain).
  • the contents of the first overhead block are: 0x4B (8 bits, 4B in hexadecimal), C bits (1 bit, indicating adjustment control), OMF bits (1 bit, indicating overhead frame multiframe indication), RPF bits ( 1 bit, indicating remote defect indication), RES bit (1 bit, reserved bit), FLEXE group number (20 bits, indicating the number of the bundle group), 0x5 (4 bits, 5 in hexadecimal), 000000 (28) Bits are all 0).
  • 0x4B and 0x5 are the flag indications of the first overhead block.
  • the reserved portion is a reserved field, which has not yet been defined, as shown by the diagonal block in Figure 4.
  • the other byte contents in the overhead block are not related to the technical solution of the embodiment of the present invention, and therefore will not be described.
  • the transmitting end in the process of transmitting service data, additionally increases the configuration of the data block group based on the configuration time slot, so that the sending end
  • the configuration of the service data can be configured from multiple dimensions, thereby increasing the total number of service transmissions, reducing the bandwidth of each service data, increasing the number of time slots, and reducing the granularity of the time slots.
  • the service data to be transmitted in the embodiment of the present invention may be simply referred to as: a service to be transmitted.
  • a service to be transmitted may be simply referred to as: a service to be transmitted.
  • the FLEXE network structure shown in FIG. 1 is used as an example.
  • the FLEXE network structure includes a service sending end and a receiving end.
  • the method includes:
  • the transmitting end determines a bearer slot position used to carry the service to be transmitted.
  • the sender determines a bearer data block group location for carrying the service to be transmitted.
  • the transmitting end transmits the to-be-transmitted service according to the bearer slot position and the bearer data block group location.
  • S604 The receiving end determines a location of the received data block group for carrying the service to be received.
  • the receiving end determines, in the received data block group location, a receiving time slot position for carrying the service to be received, and extracts a to-be-received service by receiving the time slot position.
  • the client service when carrying the customer service, as shown in FIG. 7, the client service is only connected to the FLEXE shim layer, and a single physical channel can only identify 20 time slots of the shim layer, each of which The time slot is 5G bandwidth.
  • the shim layer can carry up to 20 client services, and the maximum bandwidth of each client service is 5G.
  • the shim layer In a mode in which four 100G physical channels are bundled into one 400G logical channel, the shim layer has a maximum of 4 ⁇ 20 time slots, wherein each time slot has a 5G bandwidth.
  • the number of time slots and slot granularity defined by the FLEXE protocol can meet the OTN service scenario.
  • the number of customer services is large. Even if the total bandwidth of all client services does not exceed 100G, the number of all customer services is large. , reaching 1K or even tens of K customer services, far greater than the 20 time slots defined in the FLEXE protocol. Therefore, in the PTN service scenario, the bandwidth of a single service may be relatively small, and the minimum bandwidth is 10M. If a bandwidth of 5G is specified in the FLEXE protocol to deliver a 10M service data, bandwidth is wasted.
  • each block group includes 20 A 66-bit data block, that is, 20 time slots; in the FLEXE protocol, the shim layer has 20 ⁇ n time slots, where n represents the number of physical channels bound; if each data block group configures bearer service data, Equivalent to the number of time slots carrying the service from 20 ⁇ n to 1023 ⁇ 20 ⁇ n, the number of time slots is increased by 1023 times, and the granularity of each time slot is reduced from 5G to 0.004888G (5G divided by 1023 results) ), the granularity of the expanded time slot is about 4.88M, Therefore, the number of client services in the PTN service scenario is large, and the bandwidth of a single service is small.
  • the method further includes:
  • the sender numbers the time slots in the Calendar of the FLEXE protocol calendar and numbers the data block groups within the coverage of the overhead block.
  • the sending end may number 20 ⁇ n time slots in the calendar, which are referred to as slot numbers, for example, 1, 2, 3, ..., 20 ⁇ n-1, 20 ⁇ n; where n is the bound physical channel.
  • slot numbers for example, 1, 2, 3, ..., 20 ⁇ n-1, 20 ⁇ n; where n is the bound physical channel.
  • n is the bound physical channel.
  • Block group number such as 1, 2, ... 1022, 1023. It can be understood that after the time slot and the data block group are numbered, the position of the time slot and the data block group can be respectively characterized according to the time slot number and the data block group number.
  • the sending end determines the bearer time slot position for carrying the service to be transmitted, which may include:
  • the transmitting end determines, according to the service time slot configuration, a bearer slot number used for carrying the service to be transmitted;
  • the sending end determines the bearer data block group location for carrying the service to be transmitted, which may include:
  • the sender determines the bearer data block group number used to carry the service to be transmitted according to the service bandwidth configuration.
  • the transmitting end transmits the to-be-transmitted service according to the bearer slot position and the bearer data block group location, which may include:
  • the transmitting end carries the to-be-transmitted service to the FLEXE data frame according to the bearer slot number and the bearer data block group number, and sends the to-be-transmitted service along with the FLEXE data frame to the receiving end.
  • Receiving the data block group location may include:
  • the receiving end determines, according to the service bandwidth configuration, a received data block group number for transmitting the service to be received;
  • the receiving end determines, in the received data block group location, the receiving time slot position for carrying the service to be received, and extracting the to-be-received service by receiving the time slot position, which may include:
  • the receiving end determines, in the received data block group corresponding to the received data block group number, the receiving time slot number for carrying the service to be received according to the service time slot configuration, in the case that the receiving data block group number satisfies the preset receiving condition, And acquiring the service to be received from the corresponding slot position according to the receiving slot number.
  • the to-be-transmitted service sent by the transmitting end is the service to be received received by the receiving end, which is not described in this embodiment.
  • the transmitting end and the receiving end negotiate to determine the slot position and the data block group position that each service data transmits in the FLEXE frame, so that the service configuration information in the receiving direction and the sending direction are consistent. That is to say, the sending direction is transmitted according to the service configuration, and the receiving direction is also received according to the same configuration.
  • each service data is configured on the shim layer to include two latitude configuration information: the slot position and the data block group position, and the service is in the time slot group and the block group value.
  • the gap position is passed.
  • the present embodiment provides a service data transmission method.
  • the transmitting end additionally increases the configuration of the data block group based on the configured time slot, so that the transmitting end can access the service data from multiple dimensions.
  • the transmission is configured to increase the number of service transmission time slots of the physical channel in the FLEXE protocol, and reduce the granularity of the time slot, so that the FLEXE protocol satisfies the PTN. Business scenario requirements.
  • this embodiment describes the technical solutions of the foregoing embodiments by way of examples.
  • service A there are three services, namely, service A, service B, and service C.
  • the bandwidth of service A data is 2.5 G
  • the bandwidth of service B data is 7.5 G
  • the bandwidth of service C is 1.25 G.
  • the configuration performed by the transmitting end is the slot number ⁇ 1 ⁇ , and the data block group number ⁇ 1, 3, 5 and other odd number ⁇ ; that is, the transmitting end carries the data of the service A. Transmitting in the slot 1 position in the block group whose odd block number is odd, correspondingly, the receiving end also receives the data block in the slot position 1 in the block group whose odd block number is odd;
  • the location configuration value of the service data of the bearer service B to the service B includes two groups, where the configuration position of the first group is the slot number is ⁇ 1 ⁇ , and the block group number is ⁇ 2, 4, 6th even number ⁇ , the second group is configured with the slot number ⁇ 2 ⁇ , and the block group number is ⁇ 1, 2, 3...all number ⁇ .
  • the bandwidth of the first set of configuration locations is 2.5G (approximately equal to 2.5G, which is actually slightly smaller, because a total of 1023 block groups, if numbered according to 1, 2, 3, ... 1022, 1223, the odd number has There are 512, the even number is 511, the even number is slightly less than the odd number.
  • the bandwidth of the second group configuration position is 5G, and the two groups are 7.5G.
  • the location configuration value of the service data of the bearer to the bearer service C is ⁇ 3 ⁇
  • the block group number is a number of ⁇ 1, 5, 9, 13 and the numbering rule conforms to 4n+1.
  • the bandwidth of the service data carrying the service C is approximately equal to 1.25G, that is, the 5G time slot bandwidth is divided into four groups, and the service data of the service C is transmitted on the first group of time slots.
  • the coding method of the slot number may be 1, 2, 3, ... 20*n-1, 20*n, or 0, 1, 2, 3, ... 20*n-2, 20*n-1, this embodiment does not limit this;
  • the encoding method of the block group number may be 1, 2, 3, ... 1022, 1023, or 0, 1, 2, 3, ... 1021, 1022, or other regular coding methods. This embodiment does not limit this;
  • the coverage of the overhead block is 1023 data block groups, so when the number of intervals in which the FLEXE protocol inserts the overhead block is changed from 1023 to other values, The block group number within the coverage of the overhead block also corresponds to other modified values.
  • FIG. 8 a method for service bearer according to an embodiment of the present invention is shown.
  • the method may be applied to a sender in the FLEXE network structure shown in FIG. 1.
  • the method may include:
  • the transmitting end determines a bearer slot position used to carry the service to be transmitted.
  • the sender determines a bearer data block group location for carrying the service to be transmitted.
  • S803 The transmitting end transmits the to-be-transmitted service according to the bearer slot position and the bearer data block group location.
  • step S801 the method further includes:
  • the sender numbers the time slots in the Calendar of the FLEXE protocol calendar and numbers the data block groups within the coverage of the overhead block.
  • the sending end may number 20 ⁇ n time slots in the calendar, which are referred to as slot numbers, for example, 1, 2, 3, ..., 20 ⁇ n-1, 20 ⁇ n; where n is the bound physical channel.
  • slot numbers for example, 1, 2, 3, ..., 20 ⁇ n-1, 20 ⁇ n; where n is the bound physical channel.
  • n is the bound physical channel.
  • Block group number such as 1, 2, ... 1022, 1023. Understandably, in the group of time slots and data blocks After the row number, the location of the time slot and the data block group can be characterized according to the slot number and the data block group number.
  • the sending end determines the bearer time slot position for carrying the service to be transmitted, which may include:
  • the transmitting end determines, according to the service time slot configuration, a bearer slot number used for carrying the service to be transmitted;
  • the sending end determines the bearer data block group location for carrying the service to be transmitted, which may include:
  • the sender determines the bearer data block group number used to carry the service to be transmitted according to the service bandwidth configuration.
  • the transmitting end transmits the to-be-transmitted service according to the bearer slot position and the bearer data block group location, which may include:
  • the transmitting end carries the to-be-transmitted service to the FLEXE data frame according to the bearer slot number and the bearer data block group number, and sends the to-be-transmitted service along with the FLEXE data frame to the receiving end.
  • FIG. 9 a method for service bearer according to an embodiment of the present invention is shown.
  • the method may be applied to a receiving end in the FLEXE network structure shown in FIG. 1.
  • the method may include:
  • S901 The receiving end determines a location of the received data block group for carrying the service to be received.
  • the receiving end determines, in the received data block group location, a receiving time slot position for carrying the service to be received, and extracts the to-be-received service by receiving the time slot position.
  • Receiving the data block group location may include:
  • the receiving end determines, according to the service bandwidth configuration, a received data block group for transmitting the service to be received. Numbering;
  • step S902 the receiving end determines, in the received data block group location, the receiving time slot position for carrying the service to be received, and extracting the to-be-received service by receiving the time slot position, which may include:
  • the receiving end determines, in the received data block group corresponding to the received data block group number, the receiving time slot number for carrying the service to be received according to the service time slot configuration, in the case that the receiving data block group number satisfies the preset receiving condition, And acquiring the service to be received from the corresponding slot position according to the receiving slot number.
  • a transmitting end device 100 is provided according to an embodiment of the present invention.
  • the device 100 includes: a first determining module 1001, a second determining module 1002, and a transmitting module 1003.
  • the first determining module 1001 is configured to determine a bearer slot position for carrying a service to be transmitted;
  • the second determining module 1002 is configured to determine a bearer data block group location for carrying the to-be-transmitted service
  • the transmission module 1003 is configured to transmit the to-be-transmitted service according to the bearer slot position and the bearer data block group location.
  • the apparatus 100 further includes a numbering module 1004 configured to number the time slots in the calendar Calendar of the FLEXE protocol and to number the data block groups within the coverage of the overhead block.
  • the first determining module 1001 is configured to determine, according to the service slot configuration, a bearer slot number used to carry the to-be-transmitted service.
  • the second determining module 1002 is configured to be configured according to a service bandwidth. Determining a bearer data block group number for carrying the service to be transmitted.
  • the transmission module 1003 is configured to carry the to-be-transmitted service to the FLEXE data frame according to the bearer slot number and the bearer data block group number, and the to-be-transmitted service is as described
  • the FLEXE data frame is sent to the receiving end.
  • a receiving end device 120 is provided according to an embodiment of the present invention.
  • the device 120 includes: a third determining module 1201, a fourth determining module 1202, and an extracting module 1203.
  • the third determining module 1201 is configured to determine a received data block group location for carrying a service to be received
  • the fourth determining module 1202 is configured to determine, in the received data block group location, a receiving time slot position for carrying the to-be-received service;
  • the extracting module 1203 is configured to extract the to-be-received service by using the receiving time slot position.
  • the slot position and the position of the data block group are respectively characterized by a slot number and a data block group number.
  • the third determining module 1201 is configured to determine, according to the service bandwidth configuration, a received data block group number for transmitting the to-be-received service.
  • the fourth determining module 1202 is configured to, in the case that the received data block group number satisfies a preset receiving condition, in the received data block group corresponding to the received data block group number, according to The service slot configuration determines a receiving slot number used to carry the to-be-received service;
  • the extracting module 1203 is configured to acquire the to-be-received service from a corresponding slot position according to the receiving slot number.
  • FIG. 13 a system 130 for carrying a service according to an embodiment of the present invention is shown, where the system 130 includes a sender device 140 and a receiver device 150 in a FLEXE network structure;
  • the sending end device 140 is configured to determine a bearer slot position for carrying a service to be transmitted;
  • the receiving end device 150 is configured to determine a received data block group location for carrying a service to be received;
  • An embodiment of the present invention provides an electronic device, where the device may be the foregoing sending end or receiving end, and includes: a transceiver and a processor;
  • the transceiver can be used for data interaction.
  • the sender can use the transceiver to exchange data with the receiver, for example, to send the service data.
  • the processor is connected to the transceiver, for example, through a communication bus such as an integrated circuit bus, and can control data transmission of the transceiver by using instructions of computer executable instructions such as a computer program, and can implement the foregoing one or The implementation of the service data transmission method provided by the plurality of technical solutions, for example, the method shown in FIG. 6 and/or FIG.
  • the processor may be an application processor (AP), a central processing unit (CPU), a digital signal processor (DSP), or a programmable gate array (FPGA, Field Programmable). Gate Array), dedicated Integrated circuits, etc.
  • AP application processor
  • CPU central processing unit
  • DSP digital signal processor
  • FPGA programmable gate array
  • FPGA Field Programmable Gate Array
  • the embodiment of the invention further provides a computer storage medium, wherein the computer storage medium stores computer executable instructions, and the computer executable instructions are used for the one or more service data transmission methods.
  • the computer storage medium provided by the embodiment of the invention includes: a mobile storage device, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, and the like, which can store program codes. Medium.
  • the computer storage medium can be a non-transitory storage medium.
  • the non-transitory storage medium herein may also be referred to as a non-volatile storage medium.
  • embodiments of the present invention can be provided as a method, system, or computer program product. Accordingly, the present invention can take the form of a hardware embodiment, a software embodiment, or a combination of software and hardware. Moreover, the invention can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage and optical storage, etc.) including computer usable program code.
  • the computer program instructions can also be stored in a computer readable memory that can direct a computer or other programmable data processing device to operate in a particular manner, such that the instructions stored in the computer readable memory produce an article of manufacture comprising the instruction device.
  • the device is implemented in a flow chart A function specified in a block or blocks of a process or multiple processes and/or block diagrams.
  • These computer program instructions can also be loaded onto a computer or other programmable data processing device such that a series of operational steps are performed on a computer or other programmable device to produce computer-implemented processing for execution on a computer or other programmable device.
  • the instructions provide steps for implementing the functions specified in one or more of the flow or in a block or blocks of a flow diagram.
  • a data block group carrying the service data is also added; in this case, the data volume of the current service data can be flexibly and/or Or transmitting a scenario, selecting a time slot and/or a data group to carry the service data, thereby satisfying data bearing and transmission of different particles, thereby increasing flexibility of service data transmission, having positive industrial effects; and being simple to implement, It can be widely promoted in industry, so it has strong industrial applicability.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Time-Division Multiplex Systems (AREA)

Abstract

本发明实施例公开了一种业务数据传输方法、设备和系统；该方法包括：发送端确定用于承载待传输业务数据的承载时隙位置；所述发送端确定用于承载所述待传输业务数据的承载数据块组位置；所述发送端根据所述承载时隙位置和所述承载数据块组位置传输所述待传输业务数据。本发明实施例还公开了一种计算机存储介质。

Description

业务数据传输方法、设备和系统、存储介质
本申请基于申请号为201610866553.4、申请日为2016年09月29日的中国专利申请提出，并要求该中国专利申请的优先权，该中国专利申请的全部内容在此引入本申请作为参考。
技术领域
本发明涉及网络通信技术，尤其涉及一种业务数据传输方法、设备和系统、存储介质。
背景技术
网络技术的快速发展以及网络信息流量的快速增加，促使着通讯网络的传递带宽也相应地快速发展。通讯设备的接口带宽速度从10M(单位：比特/秒)提高到100M，接着又提高到1G和10G，目前已经达到100G的接口带宽速度，市场上已经开始大量商用100G的光模块。
目前已经研发出400G的光模块，但400G的光模块价格昂贵，超过了4个100G光模块的价格，导致400G光模块缺少商用的经济价值。因此，为了在100G光模块上传递400G业务，国际标准组织定义了灵活以太网(FlexE，Flexible Ethernet)协议。
FLEXE协议的基本内容是将多个100G的传输通道进行捆绑，形成一个更大带宽速度的传递通道，如图1所示，通过FLEXE协议在MAC层和物理编码子层(PCS，Physical Coding Sub-layer)之间多了一个垫层(FlexE Shim)，并通过FlexE Shim将4个100G的物理通道进行捆绑，形成一个400G的逻辑通道，从而在不增加成本的情况下解决了400G业务的传递需求。
目前FLEXE协议在单100G的物理线路上定义了20个时隙，每个时隙带宽是5G，那么在4×100G的逻辑通道上就定义了4×20个时隙，每个时隙 带宽也规定为5G。FLEXE协议定义的时隙数量和时隙带宽能够满足光传送网(OTN，Optical Transport Network)传递业务需要，但在分组传送网(PTN，Packet Transport Network)领域应用FLEXE协议时，会遇到以下问题：
1、100G的物理通道只定义了20个时隙，总时隙数量太少；2、每个时隙带宽是5G，导致单个时隙的颗粒度又过大；而在PTN业务领域，客户业务数量很多，每条业务的带宽又比较小，即时隙数量多、单个时隙带宽颗粒度小，这就导致当前FLEXE协议无法满足PTN业务的应用场景。
发明内容
本发明实施例期望提供一种业务数据传输方法、设备和系统，解决所述PTN业务不适用于FlexE的物理通道的问题。
本发明的技术方案是这样实现的：
第一方面，本发明实施例提供了一种业务数据传输方法，所述方法包括：
发送端确定用于承载待传输业务数据的承载时隙位置；
所述发送端确定用于承载所述待传输业务数据的承载数据块组位置；
所述发送端根据所述承载时隙位置和所述承载数据块组位置传输所述待传输业务数据。
第二方面，本发明实施例提供了一种业务数据传输方法，所述方法包括：
接收端确定用于承载待接收业务的接收数据块组位置；
所述接收端在所述接收数据块组位置中，确定用于承载所述待接收业务的接收时隙位置，并通过所述接收时隙位置提取所述待接收业务。
第三方面，本发明实施例提供了一种业务数据传输方法，所述方法包括：
发送端确定用于承载待传输业务数据的承载时隙位置；
所述发送端确定用于承载所述待传输业务数据的承载数据块组位置；
所述发送端根据所述承载时隙位置和所述承载数据块组位置传输所述待传输业务数据；
所述接收端确定用于承载待接收业务的接收数据块组位置；
所述接收端在所述接收数据块组位置中，确定用于承载所述待接收业务的接收时隙位置，并通过所述接收时隙位置提取所述待接收业务。
第四方面，本发明实施例提供了一种发送端装置，所述装置包括：第一确定模块、第二确定模块和传输模块；其中，
所述第一确定模块，配置为确定用于承载待传输业务数据的承载时隙位置；
所述第二确定模块，配置为确定用于承载所述待传输业务数据的承载数据块组位置；
所述传输模块，配置为根据所述承载时隙位置和所述承载数据块组位置传输所述待传输业务数据。
第五方面，本发明实施例提供了一种接收端装置，所述装置包括：第三确定模块、第四确定模块和提取模块；其中，
所述第三确定模块，配置为确定用于承载待接收业务的接收数据块组位置；
所述第四确定模块，配置为在所述接收数据块组位置中，确定用于承载所述待接收业务的接收时隙位置；
所述提取模块，配置为通过所述接收时隙位置提取所述待接收业务。
第六方面，本发明实施例提供了一种承载业务的系统，所述系统包括：发送端设备和接收端设备；其中，
所述发送端设备，配置为确定用于承载待传输业务数据的承载时隙位置；
以及，确定用于承载所述待传输业务数据的承载数据块组位置；
以及，根据所述承载时隙位置和所述承载数据块组位置传输所述待传输业务数据；
所述接收端设备，配置为确定用于承载待接收业务的接收数据块组位置；
以及，在所述接收数据块组位置中，确定用于承载所述待接收业务的接收时隙位置，并通过所述接收时隙位置提取所述待接收业务。
第七方面，一种计算机存储介质，所述计算机存储介质中存储有计算机可执行指令，所述计算机可执行指令可实现前述一个或多个技术方案提供的业务数据传输方法。
本发明实施例提供了一种业务数据传输方法、设备和系统、存储介质，发送端在发送业务数据的过程中，在配置时隙的基础上额外增加对数据块组的配置，还可以实现从数据块组的颗粒度上进行传输调度和数据传输，使得发送端能够从多个维度对业务数据的发送进行配置，从而能够增加FLEXE协议中物理通道的业务传输时隙数量，减少时隙颗粒度，使得FLEXE协议满足PTN业务的场景需求。
附图说明
图1为本发明实施例提供的一种FLEX网络结构示意图；
图2为本发明实施例提供的一个开销块的覆盖范围示意图；
图3为本发明实施例提供的一种FLEX网络结构传输数据的示意图；
图4为本发明实施例提供的一种开销帧的结构示意图；
图5为本发明实施例提供的一种开销帧覆盖范围的示意图；
图6为本发明实施例提供的一种业务承载的方法流程示意图；
图7为本发明实施例提供的一种FLEX网络结构承载业务的示意图；
图8为本发明实施例提供的另一种业务承载的方法流程示意图；
图9为本发明实施例提供的又一种业务承载的方法流程示意图；
图10为本发明实施例提供的一种发送端装置的结构示意图；
图11为本发明实施例提供的另一种发送端装置的结构示意图；
图12为本发明实施例提供的一种接收端装置的结构示意图；
图13为本发明实施例提供的一种承载业务的系统结构示意图。
实施方式
下面将结合本发明实施例中的附图，对本发明实施例中的技术方案进行清楚、完整地描述，以下所说明的优选实施例仅用于说明和解释本发明，并不用于限定本发明。
在光模块中，100G的数据报文在发送前会进行64/66编码，也就是将64比特的数据扩展为66比特的数据块，增加的2比特数据位于66比特数据块的前部，作为66比特数据块的开始标志；然后以66比特数据块的形式从光口发送出去。在接收时，光口从接收到的数据流中辨别出66比特数据块，然后从66比特数据块中恢复出原始的64比特数据，并重新组装得到数据报文。
FLEXE协议就处于64比特数据到66比特数据块块转换层。在发送66比特数据块前，发送端会对66比特数据块进行排序和规划，如图2所示， 白色块表示一个66比特数据块，对于100G业务，每20个66比特数据块划分为一个数据块组，每个数据块组中所包括的20个66比特bit数据块就代表20个时隙，每个时隙代表5G带宽的业务速度。发送端在发送66比特数据块时，每发送完成1023个数据块组，即1023×20个数据块，就会插入一个FLEXE开销块，如图2中黑色块所示。在插入FLEXE开销块后，发送端会继续发送数据块，当发送完第二个1023×20个数据块后，再插入FLEXE开销块，FLEXE开销块的数据长度也是66比特，以此类推，这样在发送数据块的过程中，会周期性地插入FLEXE开销块，相邻两个FLEXE开销块之间的间隔是1023×20个数据块。在本实施例中引入了数据块组，数据块组对应的资源颗粒度大于时隙对应的资源颗粒度。这样的话，根据当前的业务数据的数据量和/或传输需求，可以灵活的基于数据块组和/或时隙，进行业务数据的传输。
当使用FLEXE协议实现多个小带宽速度的物理通道捆绑成一个大带宽速度的逻辑通道时，发送端会将所有的数据块组平均轮询地发送到多个小带宽速度的物理通道上，使得所有物理通道上的数据块在发送时是完全对齐的，并且在每个物理通道上每间隔1023个数据块组同时插入开销块，从而保证了物理通道上的数据块和开销块是完全对齐的。以图1所示的FLEX网络结构为例，将4个100G的物理通道捆绑成一个400G的逻辑通道时，如图3所示，将第一个数据块组，即第一个20个数据块发送到第一路物理通道上，将第二个数据块组，即第二个20个数据块发送到第二路物理通道上，将第三个数据块组，即第三个20个数据块发送到第三路物理通道上，将第四个数据块组，即第四个20个数据块发送到第四路物理通道上，然后将第五个数据块组，即第五个20个数据块发送到第一路物理通道上……，以此类推，按照对4取余的方式将所有数据块组平均、轮询地发送到4个物理通道上。4个物理通道上的数据块在发送时是完全对齐的，在4个物理 通道都是每间隔1023个数据块组，在4个物理通道上同时插入开销块，这样4个物理通道上的数据块、开销块是完全对齐的。
在接收端，每个物理通道单独接收数据块，然后确定开销块位置。每个物理通道都以开销块位置为基准，重新对齐4个物理通道的数据块组。4个物理通道的数据块组以开销块位置为基准对齐后，按照发送时轮询分配的逆过程重新排序：先从第一个物理通道中取得开销块之后的第一个数据块组排序在前面，然后从第二个物理通道中取得开销块之后第一个数据块组排序在后面，再从第三个物理通道中取得开销块之后第一个数据块组排序在次后，再从第四个物理通道中取得开销块之后第一个数据块组排序在最后，然后重新执行上述过程，先从第一个物理通道中取得开销块之后的第二个数据块组排序次后，从第二个物理通道中取得开销块之后的第二个数据块组排序次后，以此类推，将四个物理通道的数据块组重新排序成一个大的逻辑通道数据块组。
通过上述方式，可以将4个物理通道捆绑起来，组成一个大的逻辑通道。对业务方面来说，用户只能感知到一个大的逻辑通道，并通过大的逻辑通道传递业务，而不需要了解底层的四个物理通道。
对于FLEXE开销块，需要说明的是，一个FLEXE开销块的数据长度也是66比特，在数据流发送时，由于每间隔1023×20个数据块插入一个开销块，因此，开销块在整个数据流中起到定位功能，也就是说找到开销块，就可以知道业务数据流中第一个数据块组的位置，以及后续的数据块组的位置。目前FLEXE开销块的内容如图4所示。在FLEXE协议中，连续8个开销块则组成一个开销帧，因此，如图5所示，一个开销帧的覆盖范围为8×1023×20个数据块(用白色块表示)和8个开销块(用黑色块表示)，在本实施例中，数据块和开销块统一称为信息块，因此，一个开销帧覆盖范围为8×(1023×20+1)个信息块。
参见图4，一个开销块由2比特的块标志和64位的块内容组成。块标志位于前2列，后面64列是块内容，第一个开销块的块标志是10，后面7个开销块的块标志是01或SS(SS表示内容不确定)。第一个开销块的内容是：0x4B(8位，十六进制的4B)、C比特(1位，指示调整控制)、OMF比特(1位，表示开销帧复帧指示)、RPF比特(1位，表示远端缺陷指示)、RES比特(1位，保留位)、FLEXE group number(20位，表示捆绑组的编号)、0x5(4位，十六进制的5)、000000(28位，都是0)。其中的0x4B和0x5是第一个开销块的标志指示，在接收时，当找到一个开销块中对应位置是0x4B和0x5，则表示该开销块是开销帧中的第一个开销块，以及该开销块与此后连续的7个开销块组成一个开销帧。在开销帧中，保留(reserved)部分是保留字段，目前尚未定义，如图4斜线块所示。开销块中其他字节内容由于与本发明实施例的技术方案无关，因此不再做说明。
基于上述FLEXE网络结构示例以及数据传输方式，本发明实施例提供的技术方案中，发送端在发送业务数据的过程中，在配置时隙的基础上额外增加对数据块组的配置，使得发送端能够从多个维度对业务数据的发送进行配置，从而能够增加业务传输的总数量，减少每条业务数据的带宽，达到增加时隙数量，降低时隙的颗粒度。
在本发明实施例中所述待传输业务数据，可以简称为：待传输业务。以下结合具体实施例和图示，给出一个或多个实施例，值得注意这些实施例为本发明技术方案的解释，但是并不是本发明实施例的限制。
实施例一
参见图6，其示出了本发明实施例提供的一种业务承载的方法，本实施例以图1所示的FLEXE网络结构为例进行说明，该FLEXE网络结构包括业务发送端和接收端，所述方法包括：
S601：发送端确定用于承载待传输业务的承载时隙位置；
S602：发送端确定用于承载待传输业务的承载数据块组位置；
S603：发送端根据承载时隙位置和承载数据块组位置传输待传输业务；
S604：接收端确定用于承载待接收业务的接收数据块组位置；
S605：接收端在接收数据块组位置中，确定用于承载待接收业务的接收时隙位置，并通过接收时隙位置提取待接收业务。
需要说明的是，对于在FLEXE协议来说，在承载客户业务时，如图7所述，客户业务只是和FLEXE shim层对接，单条物理通道只能识别到shim层的20个时隙，每个时隙是5G带宽。在单100G物理线路下，由于shim层只有20个时隙，shim层最多可以承载20个客户业务，每个客户业务最大带宽是5G。在4个100G的物理通道捆绑成一个400G的逻辑通道的模式下，shim层最多也只有4×20个时隙，其中，每个时隙5G带宽。
FLEXE协议定义的时隙数量和时隙颗粒度可以满足OTN业务的场景，但是在PTN业务场景下，客户业务数量很多，即使所有客户业务的总带宽不超过100G，但所有客户业务的数量较大，达到1K条、甚至几十K条客户业务，远大于FLEXE协议中定义的20个时隙。由此可知，在PTN业务场景下，单条业务的带宽可能比较小，最小可以10M，如果采用FLEXE协议规定的带宽为5G的时隙来传递一条10M的业务数据，会造成带宽浪费严重的现象。
对于图6所示的技术方案来说，通过对时隙配置以外，还对承载业务的数据块组进行配置，由于一个开销块所覆盖的范围有1023个数据块组，每个块组包含20个66比特数据块，也就是20个时隙；FLEXE协议中，shim层有20×n个时隙，n表示绑定物理通道的数量；如果每个数据块组都对承载业务数据进行配置，相当于将承载业务的时隙数量由20×n扩张到1023×20×n，时隙数量扩大了1023倍，同时每个时隙的颗粒度从5G减少到0.004888G(5G除以1023的结果)，扩展后的时隙的颗粒度大约是4.888M， 从而能够适应PTN业务场景下客户业务的数量较大，单条业务的带宽较小的情况。
在实现图6所示技术方案的过程中，示例性地，步骤S601之前，所述方法还包括：
发送端对FLEXE协议的日历Calendar中的时隙进行编号，并且对开销块覆盖范围内的数据块组进行编号。
可选地，发送端可以对Calendar中20×n个时隙进行编号，简称时隙编号，如1、2、3…20×n-1，20×n；其中，n为绑定的物理通道，如以太网PHY的个数；由于一个开销块覆盖范围内有1023个数据组块，每个数据组块有20×n个66bit数据块，所以发送端对数据组块进行编号，简称为数据块组编号，如1、2、……1022、1023。可以理解地，在对时隙和数据块组进行编号之后，就可以根据时隙编号和数据块组编号分别表征时隙和数据块组的位置。
相应地，当发送端对时隙和数据块组进行编号之后，对于步骤S601来说，发送端确定用于承载待传输业务的承载时隙位置，可以包括：
发送端根据业务时隙配置，确定用于承载待传输业务的承载时隙编号；
相应地，对于步骤S602来说，发送端确定用于承载待传输业务的承载数据块组位置，可以包括：
发送端根据业务带宽配置，确定用于承载待传输业务的承载数据块组编号。
可选地，对于步骤S603，发送端根据承载时隙位置和承载数据块组位置传输待传输业务，可以包括：
发送端根据承载时隙编号以及承载数据块组编号将待传输业务承载于FLEXE数据帧，并将待传输业务随FLEXE数据帧发送到接收端。
示例性地，由于可以通过时隙编号和数据块组编号来分别表征时隙和数据块组的位置，因此，对于接收端来说，步骤S604所述的接收端确定用于承载待接收业务的接收数据块组位置，可以包括：
接收端根据业务带宽配置，确定用于传输待接收业务的接收数据块组编号；
相应地，对于步骤S605来说，接收端在接收数据块组位置中，确定用于承载待接收业务的接收时隙位置，并通过接收时隙位置提取待接收业务，可以包括：
接收端在接收数据块组编号满足预设的接收条件的情况下，在接收数据块组编号对应的接收数据块组中，根据业务时隙配置确定用于承载待接收业务的接收时隙编号，并根据接收时隙编号从对应的时隙位置获取待接收业务。
可以理解地，对于上述技术方案，发送端所发送的待传输业务也就是接收端所接收的待接收业务，本实施例对此不做赘述。并且发送端和接收端会协商决定每个业务数据在FLEXE帧中所传输的时隙位置和数据块组位置，从而使得接收方向和发送方向的业务配置信息保持一致。也就是说发送方向按照业务配置来进行发送，相应地接收方向也要按照同样的配置来进行接收。
这样每条业务数据在shim层上配置时均包含有两个纬度的配置信息：时隙位置和数据块组位置，业务正在时隙值和块组值都满足要求的时隙块组中的时隙位置进行传递。
本实施例所提供了一种业务数据传输方法，发送端在发送业务数据的过程中，在配置时隙的基础上额外增加对数据块组的配置，使得发送端能够从多个维度对业务数据的发送进行配置，从而能够增加FLEXE协议中物理通道的业务传输时隙数量，减少时隙颗粒度，使得FLEXE协议满足PTN 业务的场景需求。
实施例二
基于前述实施例，本实施例通过示例对上述实施例的技术方案进行说明。
例如有三条业务，分别为业务A、业务B和业务C；其中，业务A数据的带宽为2.5G，业务B数据的带宽7.5G，业务C带宽数据的1.25G。
因此，对于业务A的业务数据，发送端进行的配置分别为时隙编号{1}，数据块组编号{1、3、5等奇数编号}；也就是说，发送端将业务A的数据承载于数据块组编号为奇数的块组中的1号时隙位置发送，相应地，接收端也会在数据块组编号为奇数的块组中的1号时隙位置对数据块进行接收；
对于业务B的业务数据，发送端对承载业务B的业务数据的位置配置值包括两组，其中，第一组的配置位置为时隙编号是{1}，块组编号是{2、4、6等偶数编号}，第二组的配置位置为时隙编号为{2}，块组编号为{1、2、3……所有编号}。可以得知，第一组配置位置的带宽是2.5G(约等于2.5G，实际稍微小点，因为总共1023块组，如果按照1、2、3、……1022、1223来编号，奇数编号有512个，偶数编号有511个，偶数编号略少于奇数编号)，第二组配置位置的带宽是5G，两组共7.5G。
对于业务C的业务数据，发送端对承载业务C的业务数据的位置配置值为时隙编号是{3}，块组编号是{1、5、9、13等编号规则符合4n+1的编号}，这样承载业务C的业务数据的带宽约等于1.25G，也就是说，5G时隙带宽被分成4组，在第一组时隙上传递业务C的业务数据。
当n个100G的物理通道捆绑成一个400G的逻辑通道的模式下，时隙数量就从20变为20×n。
可以理解地，本实施例的技术方案也可以有各类灵活改变方式，例如：
(1)、时隙编号的编码方式既可以是1、2、3、……20*n-1、20*n，也可以是0、1、2、3、……20*n-2、20*n-1，本实施例对此不做限定；
(2)、块组编号的编码方式既可以是1、2、3、……1022、1023，也可以是0、1、2、3、……1021、1022，还可以是其他规律的编码方式，本实施例对此不做限定；
(3)、由于FELXE协议目前定义是1023个数据块组插入一个开销块，开销块的覆盖范围是1023个数据块组，所以当FLEXE协议将插入开销块的间隔数量从1023修改为其他数值，则开销块覆盖范围内的块组编号也对应是修改后的其他数值。
实施例三
基于前述实施例，参见图8，其示出了本发明实施例提供的一种业务承载的方法，本方法可以应用于图1所示的FLEXE网络结构中的发送端，该方法可以包括：
S801：发送端确定用于承载待传输业务的承载时隙位置；
S802：发送端确定用于承载待传输业务的承载数据块组位置；
S803：发送端根据承载时隙位置和承载数据块组位置传输待传输业务。
示例性地，步骤S801之前，所述方法还包括：
发送端对FLEXE协议的日历Calendar中的时隙进行编号，并且对开销块覆盖范围内的数据块组进行编号。
可选地，发送端可以对Calendar中20×n个时隙进行编号，简称时隙编号，如1、2、3…20×n-1，20×n；其中，n为绑定的物理通道，如以太网PHY的个数；由于一个开销块覆盖范围内有1023个数据组块，每个数据组块有20×n个66bit数据块，所以发送端对数据组块进行编号，简称为数据块组编号，如1、2、……1022、1023。可以理解地，在对时隙和数据块组进 行编号之后，就可以根据时隙编号和数据块组编号分别表征时隙和数据块组的位置。
相应地，当发送端对时隙和数据块组进行编号之后，对于步骤S801来说，发送端确定用于承载待传输业务的承载时隙位置，可以包括：
发送端根据业务时隙配置，确定用于承载待传输业务的承载时隙编号；
相应地，对于步骤S802来说，发送端确定用于承载待传输业务的承载数据块组位置，可以包括：
发送端根据业务带宽配置，确定用于承载待传输业务的承载数据块组编号。
可选地，对于步骤S803，发送端根据承载时隙位置和承载数据块组位置传输待传输业务，可以包括：
发送端根据承载时隙编号以及承载数据块组编号将待传输业务承载于FLEXE数据帧，并将待传输业务随FLEXE数据帧发送到接收端。
实施例四
基于前述实施例，参见图9，其示出了本发明实施例提供的一种业务承载的方法，本方法可以应用于图1所示的FLEXE网络结构中的接收端，该方法可以包括：
S901：接收端确定用于承载待接收业务的接收数据块组位置；
S902：接收端在接收数据块组位置中，确定用于承载待接收业务的接收时隙位置，并通过接收时隙位置提取待接收业务。
示例性地，由于可以通过时隙编号和数据块组编号来分别表征时隙和数据块组的位置，因此，对于接收端来说，步骤S901所述的接收端确定用于承载待接收业务的接收数据块组位置，可以包括：
接收端根据业务带宽配置，确定用于传输待接收业务的接收数据块组 编号；
相应地，对于步骤S902来说，接收端在接收数据块组位置中，确定用于承载待接收业务的接收时隙位置，并通过接收时隙位置提取待接收业务，可以包括：
接收端在接收数据块组编号满足预设的接收条件的情况下，在接收数据块组编号对应的接收数据块组中，根据业务时隙配置确定用于承载待接收业务的接收时隙编号，并根据接收时隙编号从对应的时隙位置获取待接收业务。
实施例五
基于前述实施例，参见图10，其示出了本发明实施例提供的一种发送端装置100，所述装置100包括：第一确定模块1001、第二确定模块1002和传输模块1003；其中，
所述第一确定模块1001，配置为确定用于承载待传输业务的承载时隙位置；
所述第二确定模块1002，配置为确定用于承载所述待传输业务的承载数据块组位置；
所述传输模块1003，配置为根据所述承载时隙位置和所述承载数据块组位置传输所述待传输业务。
在上述方案中，参见图11，所述装置100还包括编号模块1004，配置为对FLEXE协议的日历Calendar中的时隙进行编号，并且对开销块覆盖范围内的数据块组进行编号。
在上述方案中，所述第一确定模块1001，配置为根据业务时隙配置，确定用于承载所述待传输业务的承载时隙编号。
在上述方案中，所述第二确定模块1002，配置为根据业务带宽配置， 确定用于承载所述待传输业务的承载数据块组编号。
在上述方案中，所述传输模块1003，配置为根据所述承载时隙编号以及所述承载数据块组编号将所述待传输业务承载于FLEXE数据帧，并将所述待传输业务随所述FLEXE数据帧发送到接收端。
实施例六
基于前述实施例，参见图12，其示出了本发明实施例提供的一种接收端装置120，所述装置120包括：第三确定模块1201、第四确定模块1202和提取模块1203；其中，
所述第三确定模块1201，配置为确定用于承载待接收业务的接收数据块组位置；
所述第四确定模块1202，配置为在所述接收数据块组位置中，确定用于承载所述待接收业务的接收时隙位置；
所述提取模块1203，配置为通过所述接收时隙位置提取所述待接收业务。
在上述方案中，所述时隙位置和数据块组的位置通过时隙编号和数据块组编号分别表征。
在上述方案中，所述第三确定模块1201，配置为根据业务带宽配置，确定用于传输所述待接收业务的接收数据块组编号。
在上述方案中，所述第四确定模块1202，配置为在所述接收数据块组编号满足预设的接收条件的情况下，在所述接收数据块组编号对应的接收数据块组中，根据业务时隙配置确定用于承载所述待接收业务的接收时隙编号；
所述提取模块1203，配置为根据所述接收时隙编号从对应的时隙位置获取所述待接收业务。
实施例七
基于前述实施例，参见图13，其示出了本发明实施例提供的一种承载业务的系统130，所述系统130包括FLEXE网络结构中发送端设备140和接收端设备150；其中，
所述发送端设备140，配置为确定用于承载待传输业务的承载时隙位置；
以及，确定用于承载所述待传输业务的承载数据块组位置；
以及，根据所述承载时隙位置和所述承载数据块组位置传输所述待传输业务；
所述接收端设备150，配置为确定用于承载待接收业务的接收数据块组位置；
以及，在所述接收数据块组位置中，确定用于承载所述待接收业务的接收时隙位置，并通过所述接收时隙位置提取所述待接收业务。
本发明实施例提供一种电子设备，该设备可为前述的发送端或接收端，包括：收发器及处理器；
所述收发器可以用于数据交互，例如，发送端可以利用所述收发器与接收端交互数据，例如，发送所述业务数据。
所述处理器，与所述收发器连接，例如，通过集成电路总线等通信总线连接，可以通过计算机程序等计算机可执行指令的指令，控制所述收发器的数据传输，同时可实现前述一个或多个技术方案提供的业务数据传输方法的实现，例如，可以实现图6和/或图9所示的方法。
所述处理器，可为应用处理器AP(AP，Application Processor)、中央处理器(CPU，Central Processing Unit)、数字信号处理器(DSP，Digital Signal Processor)或可编程门阵列(FPGA，Field Programmable Gate Array)、专用 集成电路等。
本发明实施例还提供一种计算机存储介质，所述计算机存储介质中存储有计算机可执行指令，所述计算机可执行指令用于前述一个或多个业务数据传输方法。
本发明实施例提供的计算机存储介质包括：移动存储设备、只读存储器(ROM，Read-Only Memory)、随机存取存储器(RAM，Random Access Memory)、磁碟或者光盘等各种可以存储程序代码的介质。可选为，所述计算机存储介质可为非瞬间存储介质。这里的非瞬间存储介质又可以称为非易失性存储介质。
本领域内的技术人员应明白，本发明的实施例可提供为方法、系统、或计算机程序产品。因此，本发明可采用硬件实施例、软件实施例、或结合软件和硬件方面的实施例的形式。而且，本发明可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器和光学存储器等)上实施的计算机程序产品的形式。
本发明是参照根据本发明实施例的方法、设备(系统)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器，使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中，使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品，该指令装置实现在流程图一个 流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上，使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理，从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
以上所述，仅为本发明的较佳实施例而已，并非用于限定本发明的保护范围。
工业实用性
本发明实施例中业务数据传输方法中，在承载业务数据的承载时隙的基础上，还增加了承载业务数据的数据块组；这样的话，可以灵活的根据当前的业务数据的数据量和/或传输场景，选择时隙和/或数据组来承载所述业务数据，从而满足不同颗粒的数据承载和传输，从而增加了业务数据传输的灵活性，具有积极的工业效果；且实现简便，在工业上可以广泛推广，故具有极强的工业实用性。

Claims (21)

  1. 一种业务数据传输方法，所述方法包括：
    发送端确定用于承载待传输业务数据的承载时隙位置；
    所述发送端确定用于承载所述待传输业务数据的承载数据块组位置；
    所述发送端根据所述承载时隙位置和所述承载数据块组位置传输所述待传输业务数据。
  2. 根据权利要求1所述的方法，其中，所述发送端确定用于承载待传输业务数据的承载时隙位置之前，所述方法还包括：
    所述发送端对灵活以太网FLEXE协议的日历Calendar中的时隙进行编号，并且对开销块覆盖范围内的数据块组进行编号。
  3. 根据权利要求2所述的方法，其中，所述发送端确定用于承载待传输业务数据的承载时隙位置包括：
    所述发送端根据业务时隙配置，确定用于承载所述待传输业务数据的承载时隙编号。
  4. 根据权利要求2所述的方法，其中，所述发送端确定用于承载待传输业务数据的承载数据块组位置包括：
    所述发送端根据业务带宽配置，确定用于承载所述待传输业务数据的承载数据块组编号。
  5. 根据权利要求2所述的方法，其中，所述发送端根据所述承载时隙位置和所述承载数据块组位置传输所述待传输业务数据包括：
    所述发送端根据所述承载时隙编号以及所述承载数据块组编号将所述待传输业务数据承载于FLEXE数据帧，并将所述待传输业务数据随所述 FLEXE数据帧发送到接收端。
  6. 一种业务数据传输方法，所述方法包括：
    接收端确定用于承载待接收业务的接收数据块组位置；
    所述接收端在所述接收数据块组位置中，确定用于承载所述待接收业务的接收时隙位置，并通过所述接收时隙位置提取所述待接收业务。
  7. 根据权利要求6所述的方法，其中，所述时隙位置通过时隙编号表征；所述数据块组的位置通过数据块组编号表征。
  8. 根据权利要求7所述的方法，其中，所述接收端确定用于承载待接收业务的接收数据块组位置包括：
    所述接收端根据业务带宽配置，确定用于传输所述待接收业务的接收数据块组编号。
  9. 根据权利要求7所述的方法，其中，所述接收端在所述接收数据块组位置中，确定用于承载所述待接收业务的接收时隙位置，并通过所述接收时隙位置提取所述待接收业务包括：
    所述接收端在所述接收数据块组编号满足预设的接收条件的情况下，在所述接收数据块组编号对应的接收数据块组中，根据业务时隙配置确定用于承载所述待接收业务的接收时隙编号，并根据所述接收时隙编号从对应的时隙位置获取所述待接收业务。
  10. 一种业务数据传输方法，所述方法包括：
    发送端确定用于承载待传输业务数据的承载时隙位置；
    所述发送端确定用于承载所述待传输业务数据的承载数据块组位置；
    所述发送端根据所述承载时隙位置和所述承载数据块组位置传输所述待传输业务数据；
    所述接收端确定用于承载待接收业务的接收数据块组位置；
    所述接收端在所述接收数据块组位置中，确定用于承载所述待接收业务的接收时隙位置，并通过所述接收时隙位置提取所述待接收业务。
  11. 一种发送端装置，所述装置包括：第一确定模块、第二确定模块和传输模块；其中，
    所述第一确定模块，配置为确定用于承载待传输业务数据的承载时隙位置；
    所述第二确定模块，配置为确定用于承载所述待传输业务数据的承载数据块组位置；
    所述传输模块，配置为根据所述承载时隙位置和所述承载数据块组位置传输所述待传输业务数据。
  12. 根据权利要求11所述的装置，其中，所述装置还包括编号模块，用于对灵活以太网FLEXE协议的日历Calendar中的时隙进行编号，并且对开销块覆盖范围内的数据块组进行编号。
  13. 根据权利要求12所述的装置，其中，所述第一确定模块，配置为根据业务时隙配置，确定用于承载所述待传输业务数据的承载时隙编号。
  14. 根据权利要求12所述的装置，其中，所述第二确定模块，配置为根据业务带宽配置，确定用于承载所述待传输业务数据的承载数据块组编号。
  15. 根据权利要求12所述的装置，其中，所述传输模块，配置为根据所述承载时隙编号以及所述承载数据块组编号将所述待传输业务数据承载于FLEXE数据帧，并将所述待传输业务数据随所述FLEXE数据帧发送到接收端。
  16. 一种接收端装置，所述装置包括：第三确定模块、第四确定模块 和提取模块；其中，
    所述第三确定模块，配置为确定用于承载待接收业务的接收数据块组位置；
    所述第四确定模块，配置为在所述接收数据块组位置中，确定用于承载所述待接收业务的接收时隙位置；
    所述提取模块，配置为通过所述接收时隙位置提取所述待接收业务。
  17. 根据权利要求16所述的装置，其中，所述时隙位置通过时隙编号表征；所述数据块组的位置通过数据块组编号表征。
  18. 根据权利要求17所述的装置，其中，所述第三确定模块，配置为根据业务带宽配置，确定用于传输所述待接收业务的接收数据块组编号。
  19. 根据权利要求17所述的装置，其中，所述第四确定模块，配置为在所述接收数据块组编号满足预设的接收条件的情况下，在所述接收数据块组编号对应的接收数据块组中，根据业务时隙配置确定用于承载所述待接收业务的接收时隙编号；
    所述提取模块，配置为根据所述接收时隙编号从对应的时隙位置获取所述待接收业务。
  20. 一种承载业务的系统，所述系统包括：发送端设备和接收端设备；其中，
    所述发送端设备，配置为确定用于承载待传输业务数据的承载时隙位置；
    以及，确定用于承载所述待传输业务数据的承载数据块组位置；
    以及，根据所述承载时隙位置和所述承载数据块组位置传输所述待传输业务数据；
    所述接收端设备，配置为确定用于承载待接收业务的接收数据块组位 置；
    以及，在所述接收数据块组位置中，确定用于承载所述待接收业务的接收时隙位置，并通过所述接收时隙位置提取所述待接收业务。
  21. 一种计算机存储介质，所述计算机存储介质中存储有计算机可执行指令，所述计算机可执行指令用于执行权利要求1至10任一项所述的方法。
PCT/CN2017/103695 2016-09-29 2017-09-27 业务数据传输方法、设备和系统、存储介质 WO2018059446A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
EP17854896.2A EP3522465A4 (en) 2016-09-29 2017-09-27 METHOD, DEVICE AND SYSTEM FOR TRANSMITTING SERVICE DATA AND STORAGE MEDIUM

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201610866553.4 2016-09-29
CN201610866553.4A CN107888516B (zh) 2016-09-29 2016-09-29 一种承载业务的方法、设备和系统

Publications (1)

Publication Number Publication Date
WO2018059446A1 true WO2018059446A1 (zh) 2018-04-05

Family

ID=61763715

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/103695 WO2018059446A1 (zh) 2016-09-29 2017-09-27 业务数据传输方法、设备和系统、存储介质

Country Status (3)

Country Link
EP (1) EP3522465A4 (zh)
CN (1) CN107888516B (zh)
WO (1) WO2018059446A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111342983A (zh) * 2018-12-18 2020-06-26 深圳市中兴微电子技术有限公司 成员动态处理方法、系统、接收端、管理实体及存储介质
CN111511022A (zh) * 2019-01-31 2020-08-07 中兴通讯股份有限公司 一种传输客户业务的方法、装置和系统

Families Citing this family (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111147181B (zh) * 2018-11-02 2022-12-09 中兴通讯股份有限公司 业务发送方法、接收方法、装置及系统、存储介质
CN111314404B (zh) * 2018-12-12 2022-08-02 深圳市中兴微电子技术有限公司 一种基于FlexE的数据处理的方法及装置、设备及存储介质
CN111585779B (zh) * 2019-02-19 2021-10-15 华为技术有限公司 一种灵活以太网通信方法及网络设备
CN111585778B (zh) 2019-02-19 2022-02-25 华为技术有限公司 一种灵活以太网通信方法及网络设备
CN112311510B (zh) * 2019-07-26 2024-04-09 华为技术有限公司 业务数据传输的方法和通信装置
CN112584259B (zh) * 2019-09-30 2022-08-09 华为技术有限公司 一种光传送网中的业务处理的方法、装置和系统
CN110856052B (zh) * 2019-11-13 2022-07-19 Ut斯达康通讯有限公司 支持多种粒度的FlexE实现方法、装置及电子设备
CN112866138A (zh) * 2019-11-26 2021-05-28 华为技术有限公司 一种资源分配方法、装置和设备
CN111917506B (zh) * 2020-07-21 2021-07-20 烽火通信科技股份有限公司 一种FlexE低速业务处理方法和装置
CN114125019A (zh) * 2020-08-31 2022-03-01 深圳市中兴微电子技术有限公司 数据传输的方法和装置、电子设备、计算机可读介质
CN115765880A (zh) * 2021-09-03 2023-03-07 华为技术有限公司 通信方法、装置及系统
CN116055016A (zh) * 2021-10-28 2023-05-02 华为技术有限公司 一种时隙协商方法及装置

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1909538A (zh) * 2005-08-04 2007-02-07 华为技术有限公司 无线接入系统中数据传送的实现方法
CN101645762A (zh) * 2008-08-08 2010-02-10 鼎桥通信技术有限公司 一种下行调度的方法
EP3013017A1 (en) * 2014-10-24 2016-04-27 Ciena Corporation Channelized oduflex systems and methods for flexible ethernet and otn multiplexing

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1791057B (zh) * 2004-12-15 2011-06-15 华为技术有限公司 在光传送网中传输数据业务的方法及其装置
EP2741454B1 (en) * 2011-08-24 2015-07-08 Huawei Technologies Co., Ltd. Method and device for transporting ultra-high-speed ethernet service
ES2673571T3 (es) * 2013-01-04 2018-06-22 Huawei Technologies Co., Ltd. Método para procesar datos en Ethernet, circuito integrado de capa física y dispositivo de Ethernet

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1909538A (zh) * 2005-08-04 2007-02-07 华为技术有限公司 无线接入系统中数据传送的实现方法
CN101645762A (zh) * 2008-08-08 2010-02-10 鼎桥通信技术有限公司 一种下行调度的方法
EP3013017A1 (en) * 2014-10-24 2016-04-27 Ciena Corporation Channelized oduflex systems and methods for flexible ethernet and otn multiplexing

Non-Patent Citations (1)

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

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111342983A (zh) * 2018-12-18 2020-06-26 深圳市中兴微电子技术有限公司 成员动态处理方法、系统、接收端、管理实体及存储介质
CN111342983B (zh) * 2018-12-18 2022-07-12 深圳市中兴微电子技术有限公司 成员动态处理方法、系统、接收端、管理实体及存储介质
CN111511022A (zh) * 2019-01-31 2020-08-07 中兴通讯股份有限公司 一种传输客户业务的方法、装置和系统
EP3920620A4 (en) * 2019-01-31 2022-11-16 ZTE Corporation METHOD, APPARATUS AND SYSTEM FOR TRANSMITTING CUSTOMER SERVICE, AND COMPUTER READABLE INFORMATION MEDIA

Also Published As

Publication number Publication date
CN107888516A (zh) 2018-04-06
EP3522465A1 (en) 2019-08-07
EP3522465A4 (en) 2020-05-27
CN107888516B (zh) 2021-05-11

Similar Documents

Publication Publication Date Title
WO2018059446A1 (zh) 业务数据传输方法、设备和系统、存储介质
WO2019174406A1 (zh) 数据传输方法及装置、网络设备及存储介质
CN106453028B9 (zh) 传输数据的方法和装置
CN111788794B (zh) 用于配置灵活以太网节点的方法和设备
US10951340B2 (en) Method and device for transmitting bit error rate information in FlexE overhead frame, and computer storage medium
WO2018059436A1 (zh) 一种误码检测的方法、设备、系统和计算机可读存储介质
WO2018130228A1 (zh) 业务传递的方法、设备和系统、存储介质
WO2017088517A1 (zh) 一种灵活以太网业务的光传送网承载方法及装置
KR102226021B1 (ko) 서비스 송신 방법과 장치, 서비스 수신 방법과 장치, 및 네트워크 시스템
WO2019085816A1 (zh) 业务数据传输方法及装置
US20230118809A1 (en) Method and apparatus for sending and receiving multiframe, device, system, and storage medium
CN111092686A (zh) 一种数据传输方法、装置、终端设备和存储介质
CN109672560B (zh) 灵活以太网管理通道扩展方法及设备
CN109257139B (zh) 一种物理层数据的发送、接收方法及其装置
CN111884899A (zh) 发送数据的方法和转发设备
CN109845217B (zh) 灵活以太网中传输数据的方法和设备
WO2019100982A1 (zh) 数据传输方法和设备
CN108988977B (zh) 一种灵活以太网协议中传递业务流的方法、装置和系统
CN110417542B (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: 17854896

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

Country of ref document: EP

Effective date: 20190429