WO2021219079A1 - 业务数据处理、交换、提取方法及设备、计算机可读介质 - Google Patents

业务数据处理、交换、提取方法及设备、计算机可读介质 Download PDF

Info

Publication number
WO2021219079A1
WO2021219079A1 PCT/CN2021/090977 CN2021090977W WO2021219079A1 WO 2021219079 A1 WO2021219079 A1 WO 2021219079A1 CN 2021090977 W CN2021090977 W CN 2021090977W WO 2021219079 A1 WO2021219079 A1 WO 2021219079A1
Authority
WO
WIPO (PCT)
Prior art keywords
service
block
ssf
frame
customer
Prior art date
Application number
PCT/CN2021/090977
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 EP21795880.0A priority Critical patent/EP4145788A4/en
Priority to US17/922,296 priority patent/US20230164624A1/en
Priority to JP2022566074A priority patent/JP2023523462A/ja
Publication of WO2021219079A1 publication Critical patent/WO2021219079A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/06—Notations for structuring of protocol data, e.g. abstract syntax notation one [ASN.1]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/06—Optimizing the usage of the radio link, e.g. header compression, information sizing, discarding information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/08—Protocols for interworking; Protocol conversion
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/22—Parsing or analysis of headers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/26—Special purpose or proprietary protocols or architectures
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/30—Definitions, standards or architectural aspects of layered protocol stacks
    • H04L69/32—Architecture of open systems interconnection [OSI] 7-layer type protocol stacks, e.g. the interfaces between the data link level and the physical level
    • H04L69/322—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions
    • H04L69/324—Intralayer communication protocols among peer entities or protocol data unit [PDU] definitions in the data link layer [OSI layer 2], e.g. HDLC
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04J—MULTIPLEX COMMUNICATION
    • H04J14/00—Optical multiplex systems
    • H04J14/08—Time-division multiplex systems

Definitions

  • the embodiments of the present disclosure relate to, but are not limited to, the field of communication technology
  • Flexible Ethernet Flexible Ethernet
  • OIF International Organization for Standardization OIF
  • Optical Internetworking Forum Optical Internetworking Forum
  • Optical Internetworking Forum Optical Internetworking Forum
  • Flexible Ethernet technology provides a general mechanism to transmit a series of services with different media access control (MAC, Media Access Control) rates. It can be a service with a relatively large MAC rate or multiple MAC services with a relatively low rate. The collection of services is no longer limited to services with a single MAC rate.
  • MAC media access control
  • the embodiments of the present disclosure provide a service data processing method, a service data exchange method, a service data extraction method, an operator edge device, an operator switching device, and a computer-readable medium.
  • the embodiments of the present disclosure provide a business data processing method, including: generating business blocks of each of the customer services according to the business data of multiple customer services; and mapping the business blocks of each of the customer services to at least one The payload area of the sub-slice frame SSF; the overhead area field of each SSF frame is configured to obtain the at least one SSF frame, wherein each SSF frame carries multiple service blocks of different customer services.
  • the embodiments of the present disclosure provide a service data exchange method, including: determining the outgoing port of each service block in the incoming SSF frame received by the incoming port, wherein each incoming SSF frame carries There are multiple service blocks for different customer services; the service blocks corresponding to the same outbound port are mapped to at least one outbound SSF frame, wherein each of the outbound SSF frames carries multiple service blocks for different client services; The port transmits the outbound SSF frame.
  • embodiments of the present disclosure provide a method for extracting service data, including: extracting service blocks of a predetermined customer service from at least one SSF frame, wherein each SSF frame carries services of multiple different customer services Block; decode the business block of the predetermined customer service, and extract the business data of the predetermined customer service.
  • an embodiment of the present disclosure provides an operator edge device PE, including: one or more processors; a storage device, on which one or more programs are stored, when the one or more programs are One or more processors execute, so that the one or more processors implement any one of the foregoing business data processing methods or any one of the foregoing business data extraction methods; one or more I/O interfaces are connected to the The processor and the memory are configured to implement information interaction between the processor and the memory.
  • embodiments of the present disclosure provide an operator switching device, including: one or more processors; a storage device, on which one or more programs are stored, when the one or more programs are Or multiple processors, so that the one or more processors implement any one of the foregoing business data exchange methods; one or more I/O interfaces are connected between the processor and the memory, and are configured to implement all The information interaction between the processor and the memory.
  • the embodiments of the present disclosure provide a computer-readable medium on which a computer program is stored, and when the program is executed by a processor, any one of the foregoing business data processing methods or any of the foregoing business data exchange methods is implemented , Or any of the above business data extraction methods.
  • FIG. 1 is a flowchart of a business data processing method provided by an embodiment of the disclosure
  • FIG. 2 is a schematic diagram of service bearer levels in an embodiment of the disclosure
  • FIG. 3 is a flowchart of some steps in another service data processing method provided by an embodiment of the disclosure.
  • FIG. 4 is a schematic diagram of mapping client services to corresponding SSC time slots in an embodiment of the disclosure
  • Figure 5 is a schematic diagram of the format of a 64/66B block
  • FIG. 6 is a schematic diagram of an implementation manner of a termination block in an embodiment of the disclosure.
  • FIG. 7 is a schematic diagram of an implementation manner of SSF frame structure and time slot division in an embodiment of the disclosure.
  • FIG. 8 is a schematic diagram of an implementation manner of an SSMF multiframe structure and time slot division in an embodiment of the disclosure.
  • FIG. 9 is a schematic diagram of another implementation manner of SSF frame structure and time slot division in an embodiment of the disclosure.
  • FIG. 10 is a flowchart of some steps in another service data processing method provided by an embodiment of the disclosure.
  • FIG. 11 is a flowchart of some steps in yet another service data processing method provided by an embodiment of the disclosure.
  • FIG. 12 is a schematic diagram of an implementation manner of overhead in an SSF frame in an embodiment of the disclosure.
  • FIG. 13 is a flowchart of some steps in yet another service data processing method provided by an embodiment of the disclosure.
  • FIG. 14 is a flowchart of some steps in another service data processing method provided by an embodiment of the disclosure.
  • 15 is a schematic diagram of specific field definitions of overhead in an SSF frame in an embodiment of the disclosure.
  • FIG. 16 is a flowchart of some steps in yet another service data processing method provided by an embodiment of the disclosure.
  • FIG. 17 is a flowchart of some steps in yet another service data processing method provided by an embodiment of the disclosure.
  • FIG. 18 is a flowchart of some steps in still another business data processing method provided by an embodiment of the disclosure.
  • FIG. 19 is a schematic diagram of an implementation manner of an SSC channel data stream in an embodiment of the disclosure.
  • FIG. 20 is a flowchart of some steps in yet another service data processing method provided by an embodiment of the disclosure.
  • FIG. 21 is a flowchart of a service data exchange method provided by an embodiment of the disclosure.
  • FIG. 22 is a flowchart of some steps in another service data exchange method provided by an embodiment of the disclosure.
  • FIG. 23 is a schematic diagram of an implementation manner of time slot interleaving in an embodiment of the disclosure.
  • FIG. 24 is a flowchart of some steps in another method for exchanging service data provided by an embodiment of the disclosure.
  • FIG. 25 is a flowchart of some steps in another service data exchange method provided by an embodiment of the disclosure.
  • FIG. 26 is a flowchart of some steps in another service data exchange method provided by an embodiment of the disclosure.
  • FIG. 27 is a flowchart of a method for extracting service data according to an embodiment of the disclosure.
  • FIG. 28 is a flowchart of some steps in another service data extraction method provided by an embodiment of the disclosure.
  • FIG. 29 is a flowchart of some steps in yet another service data extraction method provided by an embodiment of the disclosure.
  • FIG. 30 is a schematic diagram of an implementation manner of constructing an SSC channel in an embodiment of the disclosure.
  • FIG. 31 is a schematic diagram of another implementation manner for constructing an SSC channel in an embodiment of the disclosure.
  • FIG. 32 is a schematic diagram of an implementation manner of SCL crossing in an embodiment of the disclosure.
  • FIG. 33 is a block diagram of an operator's edge device provided by an embodiment of the present disclosure.
  • FIG. 34 is a block diagram of the composition of an operator switching device provided by an embodiment of the disclosure.
  • FIG. 35 is a block diagram of a computer-readable medium provided by an embodiment of the disclosure.
  • SPN Slicing Packet Network
  • MTN Metro Transport Network
  • FlexE the service layer to implement an end-to-end business rigid channel
  • OTN optical transport network
  • the inventors of the present disclosure have discovered through research that the prior art methods for supporting small-grain customer services are all improved on the time slots of the original 5G particles of FlexE.
  • the main problems are as follows: (1) There is still business granularity. Restrictions, for example, require business granularity not less than 1Gb/s, and do not support small granular services such as 10Mb/s or 100Mb/s; (2) Low flexibility, although the transmitted service is no longer limited to a single MAC rate service , But it is difficult to support the mixed transmission of small-grain customer services of different granularities in a 5G time slot; (3) Lack of compatibility, incompatible with current Ethernet, FlexE, SPN, MTN standards, and unable to interoperate with existing equipment, such as Cannot pass through the P (Provider) node of the standard SPN device.
  • an embodiment of the present disclosure provides a business data processing method, including: in step S110, generating business blocks of each of the customer services according to the business data of multiple customer services; In step S120, the service block of each of the client services is mapped to the payload area of at least one sub-slice frame SSF; in step S130, the overhead area field of each SSF frame is configured to obtain the at least one SSF frame, Wherein, each SSF frame carries multiple service blocks of different client services.
  • a sub-slicing frame (SSF, Sub Slicing Frame) is proposed.
  • the SSF frame includes an overhead area and a payload area, and the payload area of the SSF frame can carry at least one client service.
  • Each customer service corresponds to a sub-slicing channel (SSC, Sub Slicing Channel), and the SSC channels of all customer services constitute a sub-slicing channel layer (SSCL, SSC Layer).
  • SSC sub-slicing channel
  • SSCL sub-slicing channel layer
  • the SSC channel is a logical channel established on the service layer channel
  • the SSCL is a logical channel sublayer established on the service layer.
  • the SSCL is located in IEEE802.3
  • PCS Physical Coding Sublayer
  • MAC Media Access Control
  • the embodiments of the present disclosure do not specifically limit the service layer. For example, as shown in FIG.
  • the service layer may be a slicing channel layer (SCL, Slicing Channel Layer) of the SPN, corresponding to the SPN slicing channel (SPN Slicing Channel) ; It can be the Path layer of MTN (Path Layer), corresponding to the MTN Path channel; it can also be FlexE; it can also be the Ethernet port physical layer (PHY, Physical), that is, the IEEE 802.3 PHY in Figure 2; in addition, the service The layer can also be an Optical Transport Network (OTN).
  • SCL Slicing Channel Layer
  • MTN Packet Layer
  • FlexE corresponding to the MTN Path channel
  • PHY Physical
  • the service The layer can also be an Optical Transport Network (OTN).
  • OTN Optical Transport Network
  • a frame structure is predefined for the SSF frame, and the present disclosure does not specifically limit the predefined frame structure.
  • PE Provider Edge
  • the service data of different customer services are encapsulated and coded according to a predetermined format, and a service block conforming to the predefined frame structure of the SSF frame is generated. It is understandable that the format and size of the service blocks of different client services conforming to the predefined frame structure of the SSF frame are the same.
  • the service blocks of each customer service are assembled through a predetermined mapping method, and in step S130, the overhead area field of each SSF frame is configured to generate at least one SSF frame conforming to the predefined frame structure .
  • step S130 relative to step S110 and step S120 is not limited.
  • the SSF can be configured before the service block of each customer service is mapped to at least one SSF frame.
  • the overhead area field of the frame it is also possible to configure the overhead area field of the SSF frame after the service block of each customer service is mapped to at least one SSF frame.
  • the client service may be an Ethernet service (Ethernet Service), or it may be a time-division multiplexing with a fixed rate. Use (TDM, Time Division Multiplexing) business (TDM Service).
  • the granularity of the customer service is not particularly limited.
  • the customer service may be a service smaller than 5G granularity.
  • the granularity of the customer service is 1Gb/s, 100Mb/s. , 10Mb/s, etc.; it can also be a 5G granular service, that is, the granularity of the customer service is 5Gb/s; it can also be a service larger than 5G granular, for example, the granularity of the customer service is 6Gb/s, 8Gb /s etc.
  • each SSF frame carries multiple different client services, that is, each SSF frame is composed of multiple service blocks of different client services.
  • the service blocks of multiple client services can be assembled into the same SSF frame, or two or more adjacent SSF frames can be combined into sub-frames.
  • Slicing Multi-Frame SSMF, Sub Slicing Multi-Frame
  • mapping multiple client services into the SSMF multi-frame The embodiments of the present disclosure do not specifically limit this. For example, according to the predefined frame length of the SSF frame, the number and granularity of each customer service, it is determined to map multiple customer services into one SSF frame or into an SSMF multiframe composed of multiple SSF frames.
  • the granularities of the multiple client services may be different.
  • the client services of different granularities have different numbers of service blocks mapped to the SSF frame or SSMF multiframe, thereby achieving SSC channels of different bandwidths capable of carrying different granular customer services. It is understandable that through step S110 to step S130, an SSC channel of any bandwidth can be realized, that is, the embodiment of the present disclosure no longer limits the granularity of customer services.
  • the SSF frame generated by the source PE node also includes other data constituting the SSF frame, such as operation and maintenance management (OAM, Operation Administration and Maintenance) information, etc. This is not done in the embodiment of the present disclosure. Special restrictions.
  • OAM Operation Administration and Maintenance
  • the service data processing method provided by the embodiments of the present disclosure proposes an SSF frame, each SSF frame can carry multiple different client services, and multiple SSF frames can form an SSMF multiframe.
  • multiple customer services are encapsulated and coded according to the format of a predefined SSF frame to generate service blocks for different customer services, and a corresponding number of service blocks are mapped to SSF according to the granularity of different customer services
  • the frame or SSMF multiframe composes the SSF frame or SSMF multiframe to realize the simultaneous transmission of client services of different granularities.
  • the service data processing method provided by the embodiments of the present disclosure realizes the transmission of flexible granular services in rigid pipes, and meets the transmission requirements of low delay, low jitter, hard isolation, and flexible bandwidth, without being affected by existing standards such as FlexE, SPN, MTN, etc. Restriction on the granularity of the smallest customer service; it can support multiple Ethernet services, or/and TDM services at the same time, with flexible service rates; in addition, it can also use any one of SPN, MTN, Ethernet, OTN, etc. as the service layer
  • the transmission of SSF frames realizes good compatibility with existing standard systems such as Ethernet, FlexE, SPN, MTN, and OTN.
  • the embodiment of the present disclosure does not specifically limit the mapping manner of mapping the service blocks of each of the client services to the payload area of at least one sub-slice frame SSF in step S120.
  • the service blocks of different client services are mapped into SSF frames or SSMF multiframes by means of time slot scheduling.
  • the payload area of the SSF frame or the SSMF multiframe is divided into fixed-length time slots, so as to ensure that the SSF frame provides fixed-rate bandwidth and rigid isolation for different client services carried.
  • step S120 specifically includes: in step S121, dividing the payload area of the at least one SSF frame into multiple time slots; in step S122, dividing each of the The service blocks of the customer service are respectively mapped to different time slots of the multiple time slots, wherein the time slots corresponding to the different customer services constitute sub-slice channels SSC that respectively carry each of the customer services.
  • step S121 the payload area of a single SSF frame is divided to obtain multiple time slots.
  • an SSMF multiframe is composed of two or more SSF frames, and the payload area of the SSMF multiframe is divided to obtain multiple time slots.
  • the size of the time slot obtained by dividing the payload area of the SSF frame or the SSMF multiframe is not particularly limited.
  • the size of the time slot can be made equal to the size of the service block in step S110. If the service block is a 64/66B block conforming to the IEEE 802.3 coding specification, the size of the time slot is 66 bits;
  • the granularity of each customer service determines the size of the time slot. Further, for example, the granularity of the client service with the smallest granularity among multiple customer services can be determined as the size of the time slot.
  • the common divisor of the granularity of client services determines the size of the time slot.
  • the length of the SSF frame is also predefined, that is, the length of the SSF frame is fixed.
  • the SSF frame is divided into multiple time slots according to the determined time slot size, and the rate of each time slot satisfies formula (1):
  • Rateofslot (Sizeofslot/Sizeofssf) ⁇ Rateofserver (1)
  • Rateofslot is the rate of the time slot
  • Sizeofslot is the size of the time slot
  • Sizeofssf is the length of the SSF frame
  • Rateofserver is the rate of the service layer channel.
  • step S122 according to the granularity of each customer service and the rate of the time slot determined by formula (1), the service blocks of each customer service are respectively mapped to different time slots of the multiple time slots.
  • RateofSSC Rateofslot ⁇ Amountofslot (2)
  • RateofSSC is the rate of the SSC channel that carries customer services
  • Rateofslot is the rate of each time slot
  • Amountofslot is the number of time slots constituting the SSC channel.
  • the service block of the same customer service can be mapped to several adjacent time slots, or can be mapped to several non-adjacent time slots, which is not particularly limited in the embodiment of the present disclosure. It is understandable that the time slot that carries the customer service can be regarded as the SSC channel that carries the customer service. The time slots that constitute the SSC channel that carries different customer services are different, and the bandwidth of the SSC channel that carries different customer services is also different, and the same customer The service can be seen as a continuous stream in the time slot carrying the client service.
  • the SSF frame includes but is not limited to overhead (OH, overhead) and payload (Payload).
  • the payload of the SSF frame is divided into m time slots of the same size, slot 1 to slot m.
  • Slot 1 and slot 2 constitute the SSC A channel that carries the client service Client A
  • slot i constitutes the SSC B channel that carries the client service Client B.
  • the bandwidth of the SSC A channel is equal to the sum of the rate of slot 1 and the rate of slot 2
  • the bandwidth of the SSC B channel is equal to the rate of slot i.
  • each customer service is carried by the SSC channel formed by the corresponding time slot in slot 1 to slot m in Figure 4, which carries different customer services.
  • the bandwidth of the SSC channel can be different.
  • the structure of the SSF frame is defined.
  • the S block, D block, and T block are 66B blocks that comply with the IEEE 802.3 PCS 64/66B coding specification.
  • Figure 5 shows the format of the 64/66B block specified in IEEE 802.3.
  • the first two bits of block 66B are sync headers, which are used to distinguish between control blocks and data blocks.
  • 10 represents Control Block
  • 01 represents Data Block.
  • S block and T block belong to Control Block
  • D block belongs to Data Block.
  • the first byte after the synchronization header indicates the Block Type.
  • the block type of the first block (S block) of the SSF frame is 0x78
  • the block type of the last block (T block) of the SSF frame is 0xFF.
  • the block type of the T block is D0. ⁇ D6 bytes (bit10 ⁇ 65) are payload data.
  • the D blocks and T blocks of the SSF frame are used to carry the payload, and different client services are encapsulated and coded in the format of D blocks or T blocks, and D blocks or T blocks are generated as the service blocks.
  • the S block and the first D block of the SSF frame are extended to carry overhead.
  • Fig. 7 is a schematic diagram of dividing a single SSF frame into multiple time slots in the second embodiment. As shown in Figure 7, the payloads carried by the second to nth D blocks and T blocks of the SSF frame are divided to obtain m time slots slot 1 to slot m of the same size.
  • Fig. 8 is a schematic diagram of dividing an SSMF multiframe into multiple time slots in the second embodiment.
  • the k SSF frames that make up the SSMF multiframe are divided in the same way, that is, the payloads carried by the second to nth D blocks and T blocks of each SSF frame are divided into the same
  • the size of m time slots slot 1 ⁇ slot m, a total of m ⁇ k time slots are obtained.
  • the structure of the SSF frame is defined.
  • the definitions of the S block, D block, and T block constituting the SSF frame are as described in the second embodiment.
  • the SSF frame includes 1 S block, 495 D blocks, and 1 T block.
  • the length of the SSF frame is 32,802 bits; the first 7 blocks of the first D block are used.
  • a total of 56 bits of bytes carry overhead, and the payload size of the SSF frame is 31680 bits; the payload of the SSF frame is divided into a total of 480 time slots of 66 bits.
  • the rate of the service layer channel Rateofserver is 5Gb/s.
  • the rate of each time slot, Rateofslot, is 10.06Mb/s.
  • step S122 specifically includes: in step S1221, determining the positions and numbers of time slots carrying different customer services in the multiple time slots according to the granularity of different customer services; In step S1222, the service blocks of different customer services are mapped to corresponding time slots according to the positions and numbers of time slots that carry different customer services.
  • the bandwidths of the SSC channels formed by different numbers of time slots are also different.
  • the number of time slots constituting the SSC channel carrying each client service is different.
  • the granularity of the client service Client A is twice that of the client service Client B.
  • the SSC A channel that carries the client service Client A is composed of slot 1 and slot 2, and carries the client service Client.
  • the SSC B channel of B is composed of slot i, and the bandwidth of the SSC A channel is twice the bandwidth of the SSC B channel.
  • the positions of the time slots that constitute the SSC channels that carry different client services in the SSF frame or the SSMF frame there are no special restrictions on how to determine the positions of the time slots that constitute the SSC channels that carry different client services in the SSF frame or the SSMF frame. For example, for each customer service, several consecutive time slots in the SSF frame or SSMF frame are selected to form the SSC channel carrying the customer service; or for each customer service, adjacent or non-correlated in the SSF frame or SSMF frame Select several time slots to form the SSC channel carrying the customer service; or in a uniformly distributed manner, select several time slots in the SSF frame or SSMF frame to form the SSC channel carrying the customer service.
  • step S130 specifically includes: in step S131, in the overhead area of the at least one SSF frame, the correspondence between each of the customer services and the time slots that respectively carry each of the customer services is configured. Relationship; in step S132, configure other overhead fields of the at least one SSF frame, so as to obtain the at least one SSF frame.
  • the structure of the SSF frame is defined.
  • the definitions of the S block, D block, and T block constituting the SSF frame are as described in the second embodiment.
  • the D1 to D7 bytes (bits 10 to 65) of the extended S block are used to store overhead.
  • the structure of the SSF frame is defined.
  • the definitions of the S block, D block, and T block constituting the SSF frame are as described in the second embodiment.
  • the S block and D block are extended to store overhead.
  • the S block and the first D block in the SSF frame are extended to store the overhead.
  • the S block and the first D block of each SSF frame constituting the SSMF multiframe are extended to store the overhead.
  • the location and size of the overhead in the S block, T block, and D block of the SSF frame or SSMF multiframe are not particularly limited.
  • the first embodiment, the second embodiment, the third embodiment, the fourth embodiment, and the fifth embodiment are only exemplary descriptions of using S blocks, T blocks, or D blocks to carry overhead, and do not constitute a limitation to the embodiments of the present disclosure.
  • each SSC channel has a channel identifier SSCID, which determines the time slot that constitutes the SSC channel , It also determines the corresponding relationship between customer services and time slots.
  • step S131 specifically includes: in step S1311, configuring the time slot information carrying the customer service in the time slot identifier field of the overhead area; in step S1312, The channel identification field of the overhead area is configured with SSC channel information that carries client services.
  • time slot identification field is used to identify the time slot that carries the customer service
  • channel identification field is used to identify the SSC channel that carries the customer service.
  • the time slot identifier is a time slot number. It should be noted that when the SSF frame is divided to obtain multiple time slots in step S121, the time slots in the SSF frame are numbered to obtain the time slot number of each time slot as the time slot identifier; when step S121 When the SSMF multiframe composed of multiple SSF frames is divided to obtain multiple time slots, the time slots in all the SSF frames constituting the SSMF multiframe are numbered to obtain the time slot number of each time slot.
  • step S131 in addition to the above steps S1311 to S1312, further includes: in step S1313, the multiframe indication in the overhead area
  • the position information of the SSF frame in the SSMF multiframe composed of multiple SSF frames is configured in the field.
  • other overhead fields of the SSF frame include: a frame type field, which is used to indicate the structure of the SSF frame; a fault indication field, which is used to indicate service layer channel failure; a service type field, which is used to identify a client Type of business; check field, used to store check information.
  • the structure of the SSF frame is defined.
  • the definitions of the S block, D block, and T block constituting the SSF frame are as described in the second embodiment.
  • the first 7 bytes of the first D block are used to carry the overhead in a total of 56 bits.
  • the overhead in the sixth embodiment includes the following fields:
  • RPF/RDI (1bit): If the service layer is Ethernet PHY, it is used to indicate RPF (Remote PHY Fault); if the service layer is SCL/MTN channel, it is used to indicate RDI (Remote Defect Indication); as a In an optional implementation manner, if the local service layer is faulty, the RPF/RDI field is set to 1; if the local service layer is not faulty, the RPF/RDI field is set to 0;
  • Channel identification field SSCMap (20bit): indicates the SSCID number of the SSC channel to which the time slot belongs, and the time slot is indicated by MultiFrameSN;
  • CS_TypeMap (4bit): indicates the type of service loaded in the time slot, and the time slot is indicated by MultiFrameSN; as an optional implementation, the value of CS_TypeMap is agreed as follows: 0000b means not loaded customer service, 0001b means loaded customer service It is an Ethernet service, 0010b indicates that the loaded client service is a TDM service;
  • CRC4 (4bit): CRC4 check information checks the first 52 bits (excluding CRC4) in the overhead; the algorithm polynomial is: X4+X+1, the initial value is 0; the high bit of the CRC check result is stored in bit53, The lowest bit is stored in bit56; CRC4 can also be used to identify SSF frames.
  • the service data processing method further includes: in step S140, inserting operation maintenance management in the service block code stream composed of service blocks of the same customer service OAM block.
  • the service block and OAM block of the customer service are mapped to the SSF frame or SSMF multiframe in step S120.
  • the structure of the SSF frame is defined.
  • the definitions of the S block, D block, and T block constituting the SSF frame are as described in the second embodiment.
  • the 64/66B block code stream is generated after the client service is encapsulated and encoded, and the OAM block can be inserted at the inter-frame gap (IPG, Inter Packet Gap) position of the service code stream in the SSC channel.
  • the OAM block insertion/extraction mechanism and the definition of the OAM block can directly use the SPN SCL OAM (or MTN Path OAM) mechanism and definition, that is, the service code stream in the SSC channel is regarded as low-speed Service code stream in SPN SCL (or MTN Path).
  • the service data processing method further includes: in step S150, inserting a service idle Idle in a service block code stream composed of service blocks of the same customer service Piece.
  • the service Idle block is a service block that is not loaded with customer services.
  • the service Idle block can be added or deleted to adapt the customer service rate and the time slot rate.
  • the service block and the service Idle block of the client service are mapped to the SSF frame or the SSMF multiframe in step S120.
  • the service data processing method further includes: in step S160, according to the rate of the SSF frame and the service layer port rate, in the adjacent SSF frame Insert an Idle block between frames.
  • the structure of the SSF frame is defined.
  • the definitions of the S block, D block, and T block constituting the SSF frame are as described in the second embodiment.
  • the S block + D block + T block conforming to the definition of the SSF frame structure is called the SSF block.
  • the data stream in the SSC channel consists of SSF blocks and frames. Idle block structure.
  • the I block is the inter frame Idle block.
  • the block type of the inter Idle block is 0x1E, and there may be zero or more inter Idle blocks between the SSF blocks.
  • the SSF frame rate and the service layer rate can be adapted by adding or deleting the interframe Idle block in the SSC channel.
  • the SSF frame in the embodiments of the present disclosure is composed of 64/66B blocks that comply with the IEEE 802.3 coding specification.
  • the SSF frame includes a start block, at least one data block, and an end block, and the frame length of the SSF frame is fixed.
  • the service data processing method further includes: carrying the payload of the SSF frame in the data block and/or in the termination block; , At least one of the termination blocks carries the overhead of the SSF frame.
  • the customer service may be an Ethernet service or a TDM service.
  • the customer service includes an Ethernet service.
  • the 64/66B block in the code stream of the Ethernet service is directly used as the service block described in step S110, and in step S120, the Ethernet service blocks of different customer services are mapped to at least one In the SSF frame.
  • step S110 the Ethernet service block of the customer service is compressed and transcoded to generate the service block.
  • 256/257B encoding is used to compress and transcode the 64/66B block of the Ethernet service to generate the service block of the Ethernet service.
  • the transcoding method from 64/66B encoding to 256/257B encoding follows the IEEE 802.3 standard, that is, four 64/66B blocks are transcoded and compressed into one 256/257B block.
  • 65B encoding is used to compress and transcode the 64/66B block of the Ethernet service to generate the service block of the Ethernet service.
  • the 2 bits of the sync header of the 64/66B block are compressed into 1 bit. For example, you can only take the first bit of the sync header of the 64/66B block and delete the second bit; or you can only take the second bit of the sync header of the 64/66B block and delete the first bit.
  • the customer service includes a time division multiplexed TDM service.
  • the TDM service is mapped and encapsulated into the Ethernet message; the Ethernet message encapsulated with the TDM service is generated according to the ninth or tenth embodiment to generate the service block of the TDM service.
  • the bit stream of the constant rate TDM service is directly encapsulated and coded according to service bytes or bits, and a 64/66B block conforming to the IEEE 802.3 coding specification is generated as the service block of the TDM service.
  • the service data processing method further includes: in step S170, performing service layer processing on the SSF frame for transmission through the service layer The SSF frame.
  • the service layer includes any one of IEEE 802.3 Ethernet port physical layer Ethernet PHY, slice packet network SPN, metropolitan area transport network MTN, flexible Ethernet FlexE, and optical transport network OTN.
  • step S170 specifically includes that the SSF frame passes through IEEE 802.3 in the form of 64/66B blocks.
  • the scrambling code and block distribution of the physical coding sublayer (PCS, Physical Coding Sublayer), the physical medium adaptation layer (PMA) and the physical medium association layer interface (PMD) are then sent out from the Ethernet port.
  • the service layer is a slice packet network SPN, a metropolitan area transport network MTN, a flexible Ethernet FlexE, or an optical transport network OTN
  • the SSF frame is sent after being processed by the corresponding service layer.
  • an embodiment of the present disclosure provides a service data exchange method, including: in step S210, determining the outgoing port of each service block in the incoming SSF frame received by the incoming port, where each One incoming SSF frame carries service blocks of multiple different client services; in step S220, the service blocks corresponding to the same outgoing port are mapped to at least one outgoing SSF frame, wherein each of the outgoing SSF frames Both bear multiple service blocks of different client services; in step S230, the outbound SSF frame is transmitted through the outbound port.
  • the port that receives the SSF frame is the inbound port, and the port that sends out the SSF frame is the outbound port.
  • the SSF frame received by the inbound port is an inbound SSF frame, and the SSF frame sent by the outbound port is an outbound SSF frame.
  • the inbound SSF frame received by the inbound port of the P node carries multiple service blocks of different client services, and different client services correspond to different outbound ports.
  • the service block of each customer service in the incoming SSF frame is transmitted to the corresponding outgoing port, and at the outgoing port, the service blocks of different customer services are remapped and assembled into the outgoing SSF frame to get from the outgoing port Send the outgoing SSF frame. It is understandable that each outbound SSF frame carries different client services.
  • what the incoming port receives can also be an incoming SSMF multiframe composed of multiple incoming SSF frames; at the outgoing port, it can also be composed of multiple outgoing SSF frames and an outgoing SSMF multiframe is different.
  • the service block of the customer service is mapped into the SSMF multiframe.
  • the service data exchange method provided by the embodiments of the present disclosure is based on SSF frames capable of carrying multiple different client services or SSMF multiframes composed of multiple SSF frames, and performs different client services between the inbound port and the outbound port of the P node. Exchange between them, thereby establishing SSC channels carrying different customer services, which can transmit customer services of different granularities at the same time.
  • the service data exchange method provided by the embodiments of the present disclosure realizes the transmission of flexible granular services in rigid pipes, and meets the transmission requirements of low delay, low jitter, hard isolation, and flexible bandwidth, and is no longer subject to existing standards such as FlexE, SPN, and MTN.
  • SSF frames realizes good compatibility with existing standard systems such as Ethernet, FlexE, SPN, MTN, and OTN.
  • the time slot in the incoming SSF frame to the time slot in the outgoing SSF frame, or the incoming SSMF multiplexing is performed in the P node by way of time slot scheduling.
  • the time slot in the frame crosses the time slot of the time slot in the outgoing SSMF multiframe.
  • step S210 specifically includes: in step S211, determining the outbound port of the service block in different inbound time slots received by the inbound port, where the inbound time slot is at least one inbound The time slot in the SSF frame; and, step S220 specifically includes: in step S221, the service blocks in different inbound time slots corresponding to the same outbound port are respectively mapped to different outbound time slots, wherein the outbound time slot The slot is at least one time slot in the outbound SSF frame.
  • FIG. 23 shows an alternative implementation of time slot interleaving at the P node.
  • the P node has two incoming ports SSC SI 1 and SSC SI 2, and two outgoing ports SSC SI 3 and SSC SI 4.
  • Some time slots in the incoming SSF frame received by SSC SI 1 correspond to some time slots in the outgoing SSF frame in SSC SI 3, and some time slots correspond to some time slots in the outgoing SSF frame in SSC SI 4; similarly, Part of the time slots in the incoming SSF frame received by SSC SI 2 corresponds to part of the time slots in the outgoing SSF frame in SSC SI 3, and some time slots correspond to part of the time slots in the outgoing SSF frame in SSC SI 4.
  • the P node stores the time slots of the inbound SSF frame or the inbound SSMF frame in different inbound ports, and the outbound SSF frame or the outbound SSMF in different outbound ports are stored in the P node. Correspondence of the time slots of the frame.
  • step S211 specifically includes: in step S2111, according to the time slot cross configuration table, determine the outgoing ports of the service blocks in different incoming time slots received by the incoming port, Wherein, the time slot cross configuration table stores the correspondence between each incoming time slot and each outgoing time slot.
  • the time slot cross configuration table may be pre-configured by a network management, a software defined network (SDN, Software Defined Network) controller, or a dynamic protocol.
  • SDN Software Defined Network
  • each outgoing port there may be a slight rate difference (not greater than 200 ppm) between each outgoing port and each incoming port of the P node.
  • SSF frames or SSMF can be transmitted in the sending direction.
  • the service Idle block in each time slot of the multiframe is added and deleted, so as to realize the rate adaptation from the time slot of each inbound port to the time slot of each outbound port.
  • the service data exchange method further includes: in step S241, according to the local system clock and the rate of the outgoing time slot, compare the same outgoing time
  • the service Idle block in the service block code stream composed of the service blocks in the slot is added/deleted, and/or, in step S242, according to the local system clock and the rate of the incoming time slot, the same incoming time slot is The business Idle block in the business block code stream composed of business blocks is added/deleted.
  • step S241 may be performed without performing step S242; or only step S242 may be performed without performing step S241; and step S241 and step S242 may also be performed at the same time.
  • step S241 is executed; when it is necessary to adapt the client service rate in the incoming time slot to the rate of the incoming time slot.
  • step S242 When the time allocation is performed, step S242 is executed; when it is necessary to adapt the client service rate in the inbound time slot with the rate in the inbound time slot, the client service rate in the outbound time slot, and the rate in the outbound time slot, simultaneously Step S241 and step S242 are executed.
  • the present disclosure does not specifically limit the order of performing step S241 and/or step S242.
  • an inter-frame Idle block is inserted between the SSF frames to perform the SSF frame rate and the service layer rate. Rate adaptation.
  • the service data exchange method further includes: in step S251, according to the local system clock and the rate of the outgoing port, the same outgoing port
  • the Idle block between the outbound SSF frames is added/deleted, and/or, in step S252, according to the local system clock and the rate of the inbound port, the inbound SSF frames in the same inbound port are added/deleted. Add/delete processing for the Idle block between frames.
  • step S251 may be performed without performing step S252; or only step S252 may be performed without performing step S251; and step S251 and step S252 may also be performed at the same time.
  • step S251 is executed; when the rate of the SSF frame in the inbound port and the server rate of the inbound port need to be adjusted When adapting, perform step S252; when it is necessary to adapt the rate of the SSF frame of the inbound port and the server rate of the inbound port, the rate of the SSF frame in the outbound port, and the server rate of the outbound port.
  • step S251 and step S252 are performed at the same time.
  • the present disclosure does not specifically limit the order of performing step S251 and/or step S252.
  • the inbound port and/or the outbound port include any one of an Ethernet port, a slice channel layer SCL port, an MTN Path channel port, a FlexE Client port, and an ODUk interface of OTN.
  • an embodiment of the present disclosure provides a service data extraction method, including: in step S310, extracting a service block of a predetermined customer service from at least one SSF frame, wherein each SSF frame is A service block carrying multiple different customer services; in step S320, the service block of the predetermined customer service is decoded, and the service data of the predetermined customer service is extracted.
  • the predetermined customer service is the customer service sent by the source PE node to the current sink PE node.
  • the sink PE node After receiving the SSF frame or SSMF multiframe, the sink PE node extracts the service block of the predetermined customer service from the SSF frame or SSMF multiframe, and decodes the service block of the predetermined customer service, thereby extracting the customer Business data of the business.
  • the decoding of the service block of the predetermined customer service in the sink PE node is an inverse process of generating the service block according to the customer service in the source PE node.
  • the service data extraction method provided by the embodiments of the present disclosure extracts a predetermined customer service from an SSF frame capable of carrying multiple different customer services or an SSMF multiframe composed of multiple SSF frames, and establishes a connection from the source PE node to the sink PE For the node SSC channel, the bandwidth of the SSC channel corresponding to different granular customer services is different.
  • the service data extraction method provided by the embodiments of the present disclosure realizes the transmission of flexible granular services in rigid pipes, and meets the transmission requirements of low delay, low jitter, hard isolation, and flexible bandwidth, and is no longer subject to existing standards such as FlexE, SPN, and MTN.
  • SSF frames realizes good compatibility with existing standard systems such as Ethernet, FlexE, SPN, MTN, and OTN.
  • the sink PE node extracts the service block of the predetermined customer service from the time slot of the SSF frame or the SSMF multiframe by way of time slot scheduling.
  • step S310 specifically includes: in step S311, extracting the service block of the predetermined customer service from the predetermined time slot of the SSF frame, wherein the predetermined time slot is at least A time slot carrying the predetermined client service in an SSF frame.
  • the service data extraction method further includes: in step S312, stripping the OAM block extracted from the predetermined time slot.
  • the predetermined customer service may be an Ethernet service or a TDM service.
  • the predetermined customer service includes an Ethernet service.
  • the source PE node directly uses the 64/66B block in the code stream of the Ethernet service as the service block of the predetermined service. Then, in step S320, the code for the predetermined customer service conforms to the IEEE 802.3 coding standard The 64/66B Ethernet service block is decoded, and the service data of the predetermined customer service is extracted.
  • the source PE node compresses and transcodes the Ethernet service block of the scheduled customer service to generate the service block of the scheduled customer service.
  • the service block of the scheduled customer service needs to be decompressed into A 64/66B Ethernet service block conforming to the IEEE 802.3 coding standard, and the 64/66B Ethernet service block is decoded to extract the service data of the predetermined customer service.
  • the source PE node uses 256/257B encoding to compress and transcode the 64/66B block of the Ethernet service to generate the service block of the predetermined customer service; correspondingly, at the sink PE node, use 256/ The 257B encoding decompresses the service block of the predetermined customer service into the 64/66B Ethernet service block.
  • the transcoding method from 256/257B encoding to 64/66B encoding follows the IEEE 802.3 standard, that is, one 256/257B block is decompressed and transcoded into 4 64/66B blocks.
  • the source PE node uses 65B encoding to compress and transcode the 64/66B block of the Ethernet service to generate the service block of the predetermined customer service; accordingly, in the sink PE node, the 65B encoding is used to The service block of the predetermined customer service is decompressed into the 64/66B Ethernet service block.
  • the source PE node deletes the first bit in the synchronization header of the 64/66B block when compressing and transcoding the 64/66B block into a 65B block
  • the fourteenth embodiment in the 65B block Before the first bit of the sync header of the block, a new bit is added; if the source PE node compresses and transcodes the 64/66B block into a 65B block, deletes the second bit in the sync header of the 64/66B block, Then in the fourteenth embodiment, after the first bit of the sync header of the 65B block, a new bit is added.
  • the predetermined customer service includes a time-division multiplexed TDM service.
  • the source PE node is based on the standard "MEF 8 Implementation Agreement for the Emulation of PDH Circuits over Metro Ethernet Networks" published by the Metro Ethernet Forum (MEF, the Metro Ethernet Forum), which is a standard organization.
  • Circuit Emulation Services (CESoETH, Circuit Emulation Services over Ethernet), which maps and encapsulates TDM services into Ethernet packets, and generates the service block of the predetermined customer service in the ninth or tenth embodiment; accordingly, the destination PE The node demaps the service block of the predetermined customer service service into a TDM service code stream according to CESoETH, and extracts the service data of the predetermined customer service from the TDM service code stream.
  • the source PE node directly encapsulates and encodes the bit stream of the constant rate TDM service according to service bytes or bits, and generates 64/66B blocks conforming to the IEEE 802.3 coding specification as the service of the predetermined customer service
  • the 64/66B block is decoded into a TDM service code stream according to the IEEE 802.3 coding specification, and the service data of the predetermined customer service is extracted from the TDM service code stream.
  • the service layer is Ethernet
  • the end-to-end SSC channel that can carry flexible granular services is established through the intersection of the Ethernet link and the time slot of the SSC layer of the P node. That is, the Sub Slicing Channel in Figure 30.
  • between the source PE node and the P node, and between the sink PE node and the P node are standard Ethernet connections (such as 10GE).
  • the customer services carried in these two Ethernet connections are in the P Nodes cross through SSC time slots to form an end-to-end SSC channel from the PE source node to the PE sink node.
  • the service layer is SPN
  • the Slicing Channel provided by the SPN is connected with the time slot of the SSC layer of the P3 node to establish an end-to-end SSC channel that can carry flexible granular services. , That is, Sub Slicing Channel 1-5 in Figure 31.
  • the service layer channels Slicing Channel 1-3 and Slicing Channel 3-5 of the SSC channel are formed.
  • These two SCL channels carry the client service Client Service A's SSC channel
  • the time slot is crossed at the P3 node to form an end-to-end SSC channel carrying Client Service A from the PE1 node to the PE5 node, that is, Sub Slicing Channel 1-5 in Figure 31.
  • the SSF frame is the service data for the SCL (or MTN Path), and the SCL (or MTN Path) does not need to perceive the SSF Frame, directly complete the SCL (or MTN Path) layer cross.
  • the SCL (or MTN Path) crossover method of the P2 node or P4 node is shown in Figure 32.
  • the fourteenth embodiment is also a scenario in which a device supporting an SSC channel communicates with a traditional SPN device.
  • an embodiment of the present disclosure provides an operator edge device PE, including: one or more processors 101; a storage device 102, on which one or more programs are stored, when the one or more Multiple programs are executed by the one or more processors, so that the one or more processors implement any one of the foregoing business data processing methods or any one of the foregoing business data extraction methods; one or more I/Os
  • the interface 103 is connected between the processor and the memory, and is configured to implement information interaction between the processor and the memory.
  • the processor 101 is a device with data processing capabilities, including but not limited to a central processing unit (CPU), etc.
  • the memory 102 is a device with data storage capabilities, including but not limited to random access memory (RAM, more specifically Such as SDRAM, DDR, etc.), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory (FLASH); I/O interface (read and write interface) 103 is connected between processor 101 and memory 102 , Can realize the information interaction between the processor 101 and the memory 102, which includes but is not limited to a data bus (Bus) and the like.
  • RAM random access memory
  • ROM read-only memory
  • EEPROM electrically erasable programmable read-only memory
  • FLASH flash memory
  • I/O interface (read and write interface) 103 is connected between processor 101 and memory 102 , Can realize the information interaction between the processor 101 and the memory 102, which includes but is not limited to a data bus (Bus) and the like.
  • the processor 101, the memory 102, and the I/O interface 103 are connected to each other through the bus 104, and further connected to other components of the computing device.
  • the PE device when the PE device sends data, the PE device serves as a source PE node; when the PE device receives data, the PE device serves as a sink PE node.
  • an embodiment of the present disclosure provides an operator switching device, including: one or more processors 201; a storage device 202, on which one or more programs are stored, when the one or more One program is executed by the one or more processors, so that the one or more processors implement any one of the foregoing business data exchange methods; one or more I/O interfaces 203 are connected to the processor and the memory In between, it is configured to realize the information interaction between the processor and the memory.
  • the processor 201 is a device with data processing capabilities, including but not limited to a central processing unit (CPU), etc.
  • the memory 202 is a device with data storage capabilities, including but not limited to random access memory (RAM, more specifically Such as SDRAM, DDR, etc.), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory (FLASH); I/O interface (read and write interface) 203 is connected between processor 201 and memory 202 , Can realize the information interaction between the processor 201 and the memory 202, which includes but is not limited to a data bus (Bus) and the like.
  • RAM random access memory
  • ROM read-only memory
  • EEPROM electrically erasable programmable read-only memory
  • FLASH flash memory
  • I/O interface (read and write interface) 203 is connected between processor 201 and memory 202 , Can realize the information interaction between the processor 201 and the memory 202, which includes but is not limited to a data bus (Bus) and the
  • the processor 201, the memory 202, and the I/O interface 203 are connected to each other through the bus 204, and further connected to other components of the computing device.
  • an embodiment of the present disclosure provides a computer-readable medium on which a computer program is stored, and when the program is executed by a processor, any one of the foregoing business data processing methods, or any one of the foregoing Business data exchange method, or any of the above-mentioned business data extraction methods.
  • the computer-readable medium includes, but is not limited to, random access memory (RAM, more specifically SDRAM, DDR, etc.), read-only memory (ROM), charged erasable programmable read-only memory (EEPROM), flash memory (FLASH)
  • Such software may be distributed on a computer-readable medium, and the computer-readable medium may include a computer storage medium (or a non-transitory medium) and a communication medium (or a transitory medium).
  • the term computer storage medium includes volatile and non-volatile memory implemented in any method or technology for storing information (such as computer-readable instructions, data structures, program modules, or other data). Sexual, removable and non-removable media.
  • Computer storage media include but are not limited to RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disk (DVD) or other optical disk storage, magnetic cassette, tape, magnetic disk storage or other magnetic storage device, or Any other medium used to store desired information and that can be accessed by a computer.
  • a communication medium usually contains computer-readable instructions, data structures, program modules, or other data in a modulated data signal such as a carrier wave or other transmission mechanism, and may include any information delivery medium. .

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Computing Systems (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Time-Division Multiplex Systems (AREA)

Abstract

本申请提供了一种业务数据处理方法，所述业务数据处理方法包括：根据多个客户业务的业务数据分别生成各个所述客户业务的业务块；将各个所述客户业务的业务块映射到到至少一个子切片帧SSF的净荷区；配置各个SSF帧的开销区字段，以获得所述至少一个SSF帧，其中，每一个所述SSF帧都承载有多个不同客户业务的业务块。本申请还提供一种业务数据交换方法、一种业务数据提取方法、一种运营商边缘设备、一种运营商交换设备、一种计算机可读介质。

Description

业务数据处理、交换、提取方法及设备、计算机可读介质 技术领域
本公开实施例涉及但不限于通信技术领域
背景技术
灵活以太网(FlexE，Flexible Ethernet)技术是由国际标准化组织OIF(光互联网论坛，Optical Internetworking Forum)于2015年3月发起研究、并于2016年3月正式表决通过相关的技术标准。灵活以太网技术提供一种通用的机制来传送一系列不同媒体存取控制(MAC，Media Access Control)速率的业务，可以是单个MAC速率比较大的业务，也可以是多个MAC速率比较小的业务的集合，不再限定为单一MAC速率的业务。
发明内容
本公开实施例提供一种业务数据处理方法、一种业务数据交换方法、一种业务数据提取方法、一种运营商边缘设备、一种运营商交换设备、一种计算机可读介质。
第一方面，本公开实施例提供一种业务数据处理方法，包括：根据多个客户业务的业务数据分别生成各个所述客户业务的业务块；将各个所述客户业务的业务块映射到至少一个子切片帧SSF的净荷区；配置各个SSF帧的开销区字段，以获得所述至少一个SSF帧，其中，每一个所述SSF帧都承载有多个不同客户业务的业务块。
第二方面，本公开实施例提供一种业务数据交换方法，包括：确定入向端口接收到的入向SSF帧中的各个业务块的出向端口，其中，每一个所述入向SSF帧都承载有多个不同客户业务的业务块；将对应同一出向端口的业务块映射到至少一个出向SSF帧中，其中，每一个所述出向SSF帧都承载有多个不同客户业务的业务块；通过出向端口传输所述出向SSF帧。
第三方面，本公开实施例提供一种业务数据提取方法，包括： 从至少一个SSF帧中提取预定客户业务的业务块，其中，每一个所述SSF帧都承载有多个不同客户业务的业务块；对所述预定客户业务的业务块进行解码，提取所述预定客户业务的业务数据。
第四方面，本公开实施例提供一种运营商边缘设备PE，包括：一个或多个处理器；存储装置，其上存储有一个或多个程序，当所述一个或多个程序被所述一个或多个处理器执行，使得所述一个或多个处理器实现上述任意一种业务数据处理方法，或上述任意一种业务数据提取方法；一个或多个I/O接口，连接在所述处理器与存储器之间，配置为实现所述处理器与存储器的信息交互。
第五方面，本公开实施例提供一种运营商交换设备，包括：一个或多个处理器；存储装置，其上存储有一个或多个程序，当所述一个或多个程序被所述一个或多个处理器执行，使得所述一个或多个处理器实现上述任意一种业务数据交换方法；一个或多个I/O接口，连接在所述处理器与存储器之间，配置为实现所述处理器与存储器的信息交互。
第六方面，本公开实施例提供一种计算机可读介质，其上存储有计算机程序，所述程序被处理器执行时实现上述任意一种业务数据处理方法，或上述任意一种业务数据交换方法，或上述任意一种业务数据提取方法。
附图说明
附图用来提供对本公开实施例的进一步理解，并且构成说明书的一部分，与本公开的实施例一起用于解释本公开，并不构成对本公开的限制。通过参考附图对详细示例实施例进行描述，以上和其它特征和优点对本领域技术人员将变得更加显而易见，在附图中：
图1为本公开实施例提供的一种业务数据处理方法的流程图；
图2为本公开实施例中业务承载层次示意图；
图3为本公开实施例提供的另一种业务数据处理方法中部分步骤的流程图；
图4为本公开实施例中客户业务到相应SSC时隙的映射示意图；
图5为64/66B块的格式示意图；
图6为本公开实施例中终止块的一种实施方式的示意图；
图7为本公开实施例中SSF帧结构及时隙划分的一种实施方式的示意图；
图8为本公开实施例中SSMF复帧结构及时隙划分的一种实施方式的示意图；
图9为本公开实施例中SSF帧结构及时隙划分的另一种实施方式的示意图；
图10为本公开实施例提供的又一种业务数据处理方法中部分步骤的流程图；
图11为本公开实施例提供的再一种业务数据处理方法中部分步骤的流程图；
图12为本公开实施例中SSF帧中开销的一种实施方式的示意图；
图13为本公开实施例提供的再一种业务数据处理方法中部分步骤的流程图；
图14为本公开实施例提供的再一种业务数据处理方法中部分步骤的流程图；
图15为本公开实施例中SSF帧中开销的具体字段定义的示意图；
图16为本公开实施例提供的再一种业务数据处理方法中部分步骤的流程图；
图17为本公开实施例提供的再一种业务数据处理方法中部分步骤的流程图；
图18为本公开实施例提供的再一种业务数据处理方法中部分步骤的流程图；
图19为本公开实施例中SSC通道数据流的一种实施方式的示意图；
图20为本公开实施例提供的再一种业务数据处理方法中部分步骤的流程图；
图21为本公开实施例提供的一种业务数据交换方法的流程图；
图22为本公开实施例提供的另一种业务数据交换方法中部分步 骤的流程图；
图23为本公开实施例中时隙交叉的一种实施方式的示意图；
图24为本公开实施例提供的又一种业务数据交换方法中部分步骤的流程图；
图25为本公开实施例提供的再一种业务数据交换方法中部分步骤的流程图；
图26为本公开实施例提供的再一种业务数据交换方法中部分步骤的流程图；
图27为本公开实施例提供的一种业务数据提取方法的流程图；
图28为本公开实施例提供的另一种业务数据提取方法中部分步骤的流程图；
图29为本公开实施例提供的又一种业务数据提取方法中部分步骤的流程图；
图30为本公开实施例中构建SSC通道的一种实施方式的示意图；
图31为本公开实施例中构建SSC通道的另一种实施方式的示意图；
图32为本公开实施例中SCL交叉的一种实施方式的示意图；
图33为本公开实施例提供的一种运营商边缘设备的组成框图；
图34为本公开实施例提供的一种运营商交换设备的组成框图；
图35为本公开实施例提供的一种计算机可读介质的组成框图。
具体实施方式
为使本领域的技术人员更好地理解本公开的技术方案，下面结合附图对本公开提供的业务数据处理方法、业务数据交换方法、业务数据提取方法、运营商边缘设备、运营商交换设备、计算机可读介质进行详细描述。
在下文中将参考附图更充分地描述示例实施例，但是所述示例实施例可以以不同形式来体现且不应当被解释为限于本文阐述的实施例。反之，提供这些实施例的目的在于使本公开透彻和完整，并将使本领域技术人员充分理解本公开的范围。
在不冲突的情况下，本公开各实施例及实施例中的各特征可相互组合。
如本文所使用的，术语“和/或”包括一个或多个相关列举条目的任何和所有组合。
本文所使用的术语仅用于描述特定实施例，且不意欲限制本公开。如本文所使用的，单数形式“一个”和“该”也意欲包括复数形式，除非上下文另外清楚指出。还将理解的是，当本说明书中使用术语“包括”和/或“由……制成”时，指定存在所述特征、整体、步骤、操作、元件和/或组件，但不排除存在或添加一个或多个其它特征、整体、步骤、操作、元件、组件和/或其群组。
除非另外限定，否则本文所用的所有术语(包括技术和科学术语)的含义与本领域普通技术人员通常理解的含义相同。还将理解，诸如那些在常用字典中限定的那些术语应当被解释为具有与其在相关技术以及本公开的背景下的含义一致的含义，且将不解释为具有理想化或过度形式上的含义，除非本文明确如此限定。
切片分组网(SPN，Slicing Packet Network)、城域传送网(MTN，Metro Transport Network)以FlexE作为服务层，实现了端到端的业务刚性管道(Channel)。但是，目前FlexE、SPN、MTN标准所支持承载的最小客户业务粒度为5Gb/s，不支持小于5Gb/s业务的硬隔离及刚性管道；此外，光传送网(OTN，Optical Transport Network)技术支持的最小业务颗粒度是1.25Gb/s，尚不支持小于1.25Gb/s的业务。经本公开的发明人研究发现，现有技术中支持小颗粒客户业务的方法，都是在FlexE原有5G颗粒的时隙上去做改进，主要存在以下问题：(1)对业务颗粒度仍有限制，例如，要求业务颗粒度不小于1Gb/s，不支持10Mb/s或100Mb/s等小颗粒度业务；(2)灵活度较低，虽然传送的业务不再限定为单一MAC速率的业务，但是很难支持不同颗粒度的小颗粒客户业务在一个5G时隙进行混合传送；(3)缺乏兼容性，不能兼容当前以太网、FlexE、SPN、MTN标准，无法和现有设备互通，例如无法穿通标准SPN设备的P(Provider)节点。
有鉴于此，第一方面，参照图1，本公开实施例提供一种业务数 据处理方法，包括：在步骤S110中，根据多个客户业务的业务数据分别生成各个所述客户业务的业务块；在步骤S120中，将各个所述客户业务的业务块映射到至少一个子切片帧SSF的净荷区；在步骤S130中，配置各个SSF帧的开销区字段，以获得所述至少一个SSF帧，其中，每一个所述SSF帧都承载有多个不同客户业务的业务块。
在本公开实施例中，提出了一种子切片帧(SSF，Sub Slicing Frame)，所述SSF帧包括开销区和净荷区，所述SSF帧的净荷区能够承载至少一个客户业务。每一个客户业务对应一个子切片通道(SSC，Sub Slicing Channel)，所有客户业务的SSC通道构成子切片通道层(SSCL，SSC Layer)。
需要说明的是，在本公开实施例中，所述SSC通道是建立在服务层通道上的逻辑通道，所述SSCL是建立在服务层上的逻辑通道子层，例如，SSCL是位于IEEE802.3的物理编码子层(PCS，Physical Coding Sublayer)与媒体介入控制层(MAC，Medium Access Control)之间的通道子层。本公开实施例对所述服务层不做特殊限定，例如，如图2所示，所述服务层可以是SPN的切片通道层(SCL，Slicing Channel Layer)，对应SPN切片通道(SPN Slicing Channel)；可以是MTN的Path层(Path Layer)，对应MTN Path通道；也可以是FlexE；还可以是以太网端口物理层(PHY，Physical)，即图2中的IEEE 802.3 PHY；此外，所述服务层还可以是光传输网(OTN，Optical Transport Network)。
在本公开实施例中，为所述SSF帧预定义了帧结构，本公开对所述预定义的帧结构不做特殊限定。在源运营商边缘(PE，Provider Edge)节点中，通过步骤S110，将不同客户业务的业务数据按照预定格式进行封装、编码，生成符合所述SSF帧预定义的帧结构的业务块。可以理解的是，符合所述SSF帧预定义的帧结构的不同客户业务的业务块，块的格式和大小均相同。在步骤S120中，通过预定的映射方式，将各个客户业务的业务块进行组装，并在步骤S130中，配置各个SSF帧的开销区字段，生成符合所述预定义的帧结构的至少一个SSF帧。需要说明的是，本公开实施例中，对步骤S130相对 于步骤S110、步骤S120的执行顺序不做限定，例如，可以在将各个客户业务的业务块映射到至少一个SSF帧中之前，配置SSF帧的开销区字段；也可以在将各个客户业务的业务块映射到至少一个SSF帧中之后，配置SSF帧的开销区字段。
本公开实施例对所述客户业务的类型不做特殊限定，例如，如图2所示，所述客户业务(Client)可以是以太网业务(Ethernet Service)，也可以是具有固定速率的时分复用(TDM，Time Division Multiplexing)业务(TDM Service)。进一步地，在步骤S110中，所述多个客户业务可以是N个以太网业务，也可以是N个TDM业务，还可以是M个以太网业务和L个TDM业务，其中，M+L＝N，其中N为正整数，L和M为自然数。本公开实施例对此不做特殊限定。
在本公开实施例中，对所述客户业务的颗粒度也不做特殊限定，所述客户业务可以是小于5G颗粒的业务，例如，所述客户业务的颗粒度为1Gb/s、100Mb/s、10Mb/s等；也可以是5G颗粒业务，即所述客户业务的颗粒度为5Gb/s；还可以是大于5G颗粒的业务，例如，所述客户业务的颗粒度为6Gb/s、8Gb/s等。
需要说明的是，在本公开实施例中，每个SSF帧都承载有多个不同的客户业务，即，每个SSF帧都由多个不同客户业务的业务块组成。在本公开实施例中，当存在多个客户业务时，可以将多个客户业务的业务块都组装到同一个SSF帧中，也可以将相邻的两个或两个以上的SSF帧组成子切片复帧(SSMF，Sub Slicing Multi-Frame)，并将多个客户业务映射到所述SSMF复帧中。本公开实施例对此不做特殊限定。例如，根据SSF帧预定义的帧长度、各个客户业务的数量及颗粒度，确定将多个客户业务映射到一个SSF帧中，或映射到由多个SSF帧组成的SSMF复帧中。
在本公开实施例中，所述多个客户业务的颗粒度可以不同，在步骤S120中，不同颗粒度的客户业务，映射到SSF帧或SSMF复帧中的业务块的数量不同，从而实现了能够承载不同颗粒度的客户业务的不同带宽的SSC通道。可以理解的是，通过步骤S110到步骤S130，能够实现任意带宽的SSC通道，即，本公开实施例对客户业务的颗 粒度不再限制。
还需要说明的是，在源PE节点生成的SSF帧中，还包括构成所述SSF帧的其他数据，例如操作维护管理(OAM，Operation Administration and Maintenance)信息等，本公开实施例对此不做特殊限定。
本公开实施例提供的业务数据处理方法，提出了一种SSF帧，每一个SSF帧能够承载多个不同的客户业务，多个SSF帧可组成SSMF复帧。在本公开实施例中，将多个客户业务按照预定义的SSF帧的格式进行封装、编码，生成不同客户业务的业务块，并根据不同客户业务的颗粒度将相应数量的业务块映射到SSF帧或SSMF复帧中组成SSF帧或SSMF复帧，实现了同时对不同颗粒度的客户业务进行传输。本公开实施例提供的业务数据处理方法实现了灵活颗粒业务在刚性管道传输，满足低时延、低抖动、硬隔离、灵活带宽的传输需求，而不再受现有FlexE、SPN、MTN等标准对最小客户业务颗粒度的限制；能够同时支持多个以太网业务，或/和TDM业务，业务速率灵活；此外，还能够以SPN、MTN、以太网、OTN等中的任意一者作为服务层传输SSF帧，实现了对现有的以太网、FlexE、SPN、MTN、OTN等标准体系的良好兼容。
本公开实施例对步骤S120中，将各个所述客户业务的业务块映射到至少一个子切片帧SSF的净荷区的映射方式不做特殊限定。作为一种可选的实施方式，采用时隙调度的方式将不同客户业务的业务块映射到SSF帧或SSMF复帧中。具体来说，对SSF帧或SSMF复帧的净荷区进行定长时隙划分，从而确保SSF帧为承载的不同客户业务提供固定速率带宽及刚性隔离。
相应地，参照图3，在一些实施例中，步骤S120具体包括：在步骤S121中，将所述至少一个SSF帧的净荷区划分为多个时隙；在步骤S122中，将各个所述客户业务的业务块分别映射到所述多个时隙中的不同时隙中，其中，不同的所述客户业务对应的时隙构成分别承载各个所述客户业务的子切片通道SSC。
在本公开实施例中，作为一种可选的实施方式，在步骤S121中， 对单个SSF帧的净荷区进行划分，得到多个时隙。
作为另一种可选的实施方式，在步骤S121中，由两个或两个以上SSF帧组成SSMF复帧，并将所述SSMF复帧的净荷区进行划分，得到多个时隙。
在本公开实施例中，对将SSF帧或SSMF复帧的净荷区进行划分得到的时隙大小不做特殊限定。例如，可以使所述时隙的大小等于步骤S110中的业务块的大小，若所述业务块为符合IEEE 802.3编码规范的64/66B块，则所述时隙的大小为66bit；也可以根据各个客户业务的颗粒度确定所述时隙的大小，进一步地，例如，可以将多个客户业务中颗粒度最小的客户业务的颗粒度大小确定为所述时隙的大小，还可以根据多个客户业务的颗粒度的公约数确定所述时隙的大小。
需要说明的是，在本公开中，在预定义SSF帧时，同时预定义SSF帧的长度，即所述SSF帧的长度固定。在步骤S121中，按照确定的时隙大小将SSF帧划分为多个时隙，每个时隙的速率满足公式(1)：
Rateofslot＝(Sizeofslot/Sizeofssf)×Rateofserver    (1)
其中，Rateofslot为时隙的速率，Sizeofslot为时隙的大小，Sizeofssf为SSF帧的长度，Rateofserver为服务层通道的速率。
在步骤S122中，根据各个客户业务的颗粒度和通过公式(1)确定的时隙的速率，将各个所述客户业务的业务块分别映射到所述多个时隙中的不同时隙中。
承载客户业务的SSC通道的速率与时隙的速率的关系满足公式(2)：
RateofSSC＝Rateofslot×Amountofslot     (2)
其中，RateofSSC为承载客户业务的SSC通道的速率，Rateofslot为每一个时隙的速率，Amountofslot为构成所述SSC通道的时隙的数量。
需要说明的是，同一客户业务的业务块可以映射到相邻的若干个时隙中，也可以映射到不相邻的若干个时隙中，本公开实施例对此不做特殊限定。可以理解的是，承载客户业务的时隙可以看作承载该 客户业务的SSC通道，构成承载不同客户业务的SSC通道的时隙不同，承载不同客户业务的SSC通道的带宽也不同，而同一客户业务在承载该客户业务的时隙中可看做连续的码流。
实施例一
在本实施例一中，如图4所示，SSF帧包括但不限于开销(OH，overhead)和净荷(Payload)。
在图4中，将SSF帧的净荷划分为相同大小的m个时隙slot 1～slot m。slot 1和slot 2构成了承载客户业务Client A的SSC A通道，slot i构成了承载客户业务ClientB的SSC B通道。SSC A通道的带宽等于slot 1的速率与slot 2的速率的和，SSC B通道的带宽等于slot i的速率。
可以理解的是，在本实施例一中，还可以有其他不同的客户业务，每一个客户业务都由图4中slot 1～slot m中的相应时隙构成的SSC通道承载，承载不同客户业务的SSC通道的带宽可以不同。
实施例二
在本实施例二中，基于IEEE 802.3的PCS层64/66B编码规范，定义了SSF帧的结构。
构成SSF帧的64/66B块有三种类型：一个起始块(Start Block，也称作S块)、n个数据块(Data Block，也称作D块)和一个终止块(Terminate Block，也称作T块)。SSF帧长度为(n+2)*66bit。其中，n可以根据不同设计进行取值，即，SSF帧也可以是其他固定长度，例如，取n＝495，则SSF帧长度为32802 bit。
在本实施例二中，S块、D块、T块是符合IEEE 802.3 PCS 64/66B编码规范的66B块。图5示出了IEEE 802.3中规范的64/66B块的格式。如图5所示，66B块的前两个比特是同步头(sync header)，用于区分控制块(Control Block)和数据块(Data Block)。在图5中，10表示Control Block，01表示Data Block。其中，S块和T块属于Control Block，D块属于Data Block。对于Control Block，同步头之后的第一个字节表示块类型(Block Type)。在本实施例二中，SSF帧的第一个块(S块)的块类型为0x78，SSF帧的最后一个块(T块) 的块类型为0xFF，如图6所示，T块的D0～D6字节(bit10～65)为净荷数据。
在本实施例二中，SSF帧的D块和T块用于承载净荷，不同客户业务通过D块或T块的格式进行封装、编码，生成D块或T块作为所述业务块。SSF帧的S块和第一个D块扩展用于承载开销。
图7为在本实施例二中将单个SSF帧划分为多个时隙的示意图。如图7所示，将SSF帧的第2至第n个D块和T块所承载的净荷进行划分，得到相同大小的m个时隙slot 1～slot m。
图8为本实施例二中将SSMF复帧划分为多个时隙的示意图。如图8所示，对组成SSMF复帧的k个SSF帧按照相同的方式进行划分，即，将每一个SSF帧的第2至第n个D块和T块所承载的净荷划分为相同大小的m个时隙slot 1～slot m，共得到m×k个时隙。
实施例三
在本实施例三中，基于IEEE 802.3的PCS层64/66B编码规范，定义了SSF帧的结构。构成SSF帧的S块、D块、T块的定义如实施例二中所述。
在本实施例三中，如图9所示，所述SSF帧包括1个S块、495个D块、1个T块，SSF帧长度为32802 bit；用第一个D块的前7个字节共56bit承载开销，SSF帧的净荷大小为31680bit；将SSF帧的净荷划分为大小为66bit的共480个时隙。在本实施例三中，服务层通道的速率Rateofserver为5Gb/s。
根据公式(1)可得，每个时隙的速率Rateofslot为10.06Mb/s。
在一些实施例中，参照图10，步骤S122具体包括：在步骤S1221中，根据不同客户业务的颗粒度确定所述多个时隙中，分别承载不同客户业务的时隙的位置和数量；在步骤S1222中，根据承载不同客户业务的时隙的位置和数量，将不同客户业务的业务块映射到对应的时隙中。
本公开实施例中，在通过步骤S121将SSF帧或SSMF复帧的净荷区划分为多个相同大小的时隙的情况下，不同数量的时隙构成的SSC通道的带宽也不同。相应地，对于颗粒度不同的客户业务，构成 承载各个客户业务的SSC通道的时隙数量不同。例如，在图4中，客户业务Client A的颗粒度是客户业务Client B的颗粒度的两倍，相应地，承载客户业务Client A的SSC A通道由slot 1和slot 2构成，承载客户业务Client B的SSC B通道由slot i构成，SSC A通道的带宽是SSC B通道的带宽的两倍。
在本公开实施例中，对于如何确定SSF帧或SSMF帧中，构成承载不同客户业务的SSC通道的时隙的位置不做特殊限定。例如，对于每个客户业务都选择SSF帧或SSMF帧中连续的若干个时隙，构成承载该客户业务的SSC通道；或对于每个客户业务，在SSF帧或SSMF帧中相邻或不相邻选择若干个时隙，构成承载该客户业务的SSC通道；或按照均匀分布的方式，在SSF帧或SSMF帧中选择若干个时隙，构成承载客户业务的SSC通道。
在一些实施例中，参照图11，步骤S130具体包括：在步骤S131中，在所述至少一个SSF帧的开销区中配置各个所述客户业务与分别承载各个所述客户业务的时隙的对应关系；在步骤S132中，配置所述至少一个SSF帧的其它开销字段，从而获得所述至少一个SSF帧。
实施例四
在本实施例四中，基于IEEE 802.3的PCS层64/66B编码规范，定义了SSF帧的结构。构成SSF帧的S块、D块、T块的定义如实施例二中所述。
在本实施例四中，如图12所示，扩展S块的D1～D7字节(bit10～65)，用于存放开销。
实施例五
在本实施例五中，基于IEEE 802.3的PCS层64/66B编码规范，定义了SSF帧的结构。构成SSF帧的S块、D块、T块的定义如实施例二中所述。在本实施例五中，扩展S块和D块，用于存放开销。
如图7所示，在本实施例五中，将SSF帧中的S块和第一个D块扩展用于存放开销。
如图8所示，在本实施例五中，将SSMF复帧中，组成该SSMF 复帧的每一个SSF帧的S块和第一个D块扩展用于存放开销。
需要说明的是，在本公开实施例中，对于开销在SSF帧或SSMF复帧的S块、T块、D块中位置及大小不做特殊限定。实施例一、实施例二、实施例三、实施例四和实施例五仅是对用S块、T块或D块承载开销的示例性说明，不构成对本公开实施例的限制。
在本公开实施例中，不同的客户业务与承载客户业务的SSC通道一一对应，作为一种可选的实施方式，每一个SSC通道都有一个通道标识SSCID，确定了构成SSC通道的时隙，也就确定了客户业务与时隙的对应关系。
相应地，在一些实施例中，参照图13，步骤S131具体包括：在步骤S1311中，在所述开销区的时隙标识字段中配置承载客户业务的时隙信息；在步骤S1312中，在所述开销区的通道标识字段中配置承载客户业务的SSC通道信息。
需要说明的是，所述时隙标识字段用于标识承载客户业务的时隙；所述通道标识字段用于标识承载客户业务的SSC通道。
在本公开实施例中，作为一种可选的实施方式，时隙标识为时隙号。需要说明的是，当步骤S121中，对SSF帧进行划分得到多个时隙时，对SSF帧中的时隙进行编号得到各个时隙的时隙号，作为所述时隙标识；当步骤S121中，对由多个SSF帧组成的SSMF复帧进行划分得到多个时隙时，对组成SSMF复帧的所有SSF帧中的时隙进行编号，得到各个时隙的时隙号。
在一些实施例中，当由多个SSF帧组成SSMF复帧时，参照图14，步骤S131除了上述步骤S1311至步骤S1312以外，还包括：在步骤S1313中，在所述开销区的复帧指示字段中配置所述SSF帧在由多个SSF帧组成的SSMF复帧中的位置信息。
在一些实施例中，所述SSF帧的其他开销字段包括：帧类型字段，用于指示所述SSF帧结构；故障指示字段，用于指示服务层通道故障情况；业务类型字段，用于标识客户业务的类型；校验字段，用于存储校验信息。
实施例六
在本实施例六中，基于IEEE 802.3的PCS层64/66B编码规范，定义了SSF帧的结构。构成SSF帧的S块、D块、T块的定义如实施例二中所述。
在本实施例六中，用第一个D块的前7个字节共56bit承载开销。如图15所示，本实施例六中开销包括以下字段：
帧类型字段FrameType(4bit)：用于表示不同的SSF帧结构定义，例如将SSF帧结构定义为FrameType＝0x1；其它FrameType类型的SSF帧结构可根据实际情况扩展定义；
故障指示字段RPF/RDI(1bit)：若服务层是Ethernet PHY，则用于表示RPF(Remote PHY Fault)；若服务层是SCL/MTN通道，则用于表示RDI(Remote Defect Indication)；作为一种可选的实施方式，本地服务层有故障，则将RPF/RDI字段置为1；本地服务层无故障，则将RPF/RDI字段置为0；
复帧指示字段MultiFrameSN(10bit)：表示SSF位于复帧的顺序号，从1递增、循环；作为一种可选的实施方式，MultiFrameSN用于指示SSCMap和CS_TypeMap对应的时隙号，即，时隙号＝MultiFrameSN，在此可选实施方式中，复帧中SSF帧的数量等于时隙数量；
通道标识字段SSCMap(20bit)：指示时隙所属的SSC通道的SSCID号，时隙由MultiFrameSN指示；
业务类型字段CS_TypeMap(4bit)：指示时隙装载的业务类型，时隙由MultiFrameSN指示；作为一种可选的实施方式，CS_TypeMap的值约定如下：0000b表示未装载客户业务，0001b表示装载的客户业务为以太网业务，0010b表示装载的客户业务为TDM业务；
Reserved(13bit)：保留，全0；
校验字段CRC4(4bit)：CRC4校验信息对开销中前52bit(不含CRC4)进行校验；算法多项式为：X4+X+1，初始值为0；CRC校验结果高位存放在bit53，最低位存放在bit56；CRC4还可用于SSF帧的识别。
在一些实施例中，参照图16，在步骤S110之后，所述业务数据 处理方法还包括：在步骤S140中，在由同一种客户业务的业务块组成的业务块码流中，***操作维护管理OAM块。
需要说明的是，在业务块码流中***OAM块后，在步骤S120中将客户业务的业务块和OAM块映射到SSF帧或SSMF复帧中。
实施例七
在本实施例七中，基于IEEE 802.3的PCS层64/66B编码规范，定义了SSF帧的结构。构成SSF帧的S块、D块、T块的定义如实施例二中所述。
在本实施例七中，客户业务封装、编码后生成64/66B块码流，可以在SSC通道中业务码流的帧间间距(IPG，Inter Packet Gap)位置***OAM块。在本实施例七中，OAM块***/提取机制及OAM块的定义可直接利用SPN的SCL OAM(或MTN的Path OAM)机制和定义，即，将SSC通道中的业务码流当做是低速的SPN SCL(或MTN Path)中的业务码流。
在一些实施例中，参照图17，在步骤S110之后，所述业务数据处理方法还包括：在步骤S150中，在由同一种客户业务的业务块组成的业务块码流中，***业务空闲Idle块。
需要说明的是，所述业务Idle块为未装载客户业务的业务块，在本公开实施例中，所述业务Idle块可以增删，以进行客户业务速率与时隙速率的适配。
还需要说明的是，在业务块码流中***业务Idle块后，在步骤S120中将客户业务的业务块和业务Idle块映射到SSF帧或SSMF复帧中。
在一些实施例中，参照图18，在步骤S130之后，所述业务数据处理方法还包括：在步骤S160中，根据所述SSF帧的速率与服务层端口速率，在相邻的所述SSF帧之间***帧间Idle块。
实施例八
在本实施例八中，基于IEEE 802.3的PCS层64/66B编码规范，定义了SSF帧的结构。构成SSF帧的S块、D块、T块的定义如实施例二中所述。
在本实施例八中，符合SSF帧结构定义的S块+D块+T块称为SSF块，如图19所示，在本实施例八中，SSC通道中的数据流由SSF块和帧间Idle块构成。在图19中，I块即帧间Idle块。在本实施例八中，帧间Idle块的块类型为0x1E，SSF块之间可以有0个或多个帧间Idle块。可以通过增加或删除SSC通道中的帧间Idle块进行SSF帧速率与服务层速率的适配。
在一些实施例中，本公开实施例中所述SSF帧由符合IEEE 802.3编码规范的64/66B块构成。
在一些实施例中，所述SSF帧包括起始块、至少一个数据块、终止块，且所述SSF帧的帧长度固定。
对于SSF帧和SSF帧中的起始块、数据块、终止块等的定义参照实施例二，此处不再赘述。
在一些实施例中，所述业务数据处理方法还包括：在所述数据块，和/或，所述终止块中承载所述SSF帧的净荷；在所述起始块、所述数据块、所述终止块中的至少一者中承载所述SSF帧的开销。
在所述起始块、所述数据块、所述终止块中的至少一者中承载所述SSF帧的开销的具体实施方式参照实施例二至实施例五，此处不再赘述。
如前文所述，本公开实施例中，客户业务可以是以太网业务，也可以是TDM业务。
相应地，在一些实施例中，所述客户业务包括以太网业务。
需要说明的是，对于以太网业务，当经过IEEE 802.3的PCS编码后，就形成64/66B块的码流。
在一些实施例中，将以太网业务的码流中的64/66B块直接作为步骤S110中所述的业务块，并在步骤S120中，将不同客户业务的以太网业务块映射到至少一个所述SSF帧中。
在一些实施例中，在步骤S110中，将客户业务的以太网业务块进行压缩转码生成所述业务块。
实施例九
在本实施例九中，利用256/257B编码将以太网业务的64/66B 块压缩转码，生成以太网业务的业务块。
在本实施例九中，从64/66B编码到256/257B编码的转码方式遵循IEEE 802.3标准，即4个64/66B块转码压缩为1个256/257B块。
实施例十
在本实施例十中，利用65B编码将以太网业务的64/66B块压缩转码，生成以太网业务的业务块。
在本实施例十中，将64/66B块压缩转码为65B块时，将64/66B块的同步头的2个bit压缩为1bit。例如，可以只取64/66B块的同步头第1个bit、删除第2个bit；也可以只取64/66B块的同步头第2个bit、删除第1个bit。
在一些实施例中，所述客户业务包括时分复用TDM业务。
实施例十一
根据标准组织城域以太网论坛(MEF，Metro Ethernet Forum)发布的标准“MEF 8 Implementation Agreement for the Emulation of PDH Circuits over Metro Ethernet Networks”中规范的以太网电路仿真服务(CESoETH，Circuit Emulation Services over Ethernet)，将TDM业务映射、封装到以太网报文中；将封装了TDM业务的以太网报文根据实施例九或实施例十生成TDM业务的业务块。
实施例十二
将恒定速率的TDM业务的比特流按照业务字节或比特直接封装编码，生成符合IEEE 802.3编码规范的64/66B块，作为TDM业务的业务块。
在一些实施例中，参照图20，在上述步骤S110至步骤S130以外，所述业务数据处理方法还包括：在步骤S170中，对所述SSF帧进行服务层处理，以通过所述服务层传输所述SSF帧。
在一些实施例中，所述服务层包括IEEE 802.3以太网端口物理层Ethernet PHY、切片分组网SPN、城域传送网MTN、灵活以太网FlexE、光传送网OTN中的任意一者。
当所述服务层为IEEE 802.3以太网端口物理层(PHY，Pyhsical)， 即在源PE节点，通过IEEE 802.3 Ethernet PHY发送数据时，步骤S170具体包括SSF帧以64/66B块的形式经过IEEE 802.3物理编码子层(PCS，Physical Coding Sublayer)的扰码、块分发，以及物理媒介适配层(PMA)、物理介质关联层接口(PMD)，然后从以太网端口发送出去。
当所述服务层为切片分组网SPN、城域传送网MTN、灵活以太网FlexE或光传送网OTN时，则在步骤S170中，将SSF帧经过相应服务层处理后发送。
第二方面，参照图21，本公开实施例提供一种业务数据交换方法，包括：在步骤S210中，确定入向端口接收到的入向SSF帧中的各个业务块的出向端口，其中，每一个所述入向SSF帧都承载有多个不同客户业务的业务块；在步骤S220中，将对应同一出向端口的业务块映射到至少一个出向SSF帧中，其中，每一个所述出向SSF帧都承载有多个不同客户业务的业务块；在步骤S230中，通过出向端口传输所述出向SSF帧。
需要说明的是，在运营商交换设备(provider)或称为P节点中，接收SSF帧的端口为入向端口，发出SSF帧的端口为出向端口。相应地，所述入向端口接收到的SSF帧为入向SSF帧，所述出向端口发出的SSF帧为出向SSF帧。
在本公开实施例中，P节点的入向端口接收到的入向SSF帧中承载有多个不同客户业务的业务块，不同客户业务对应不同的出向端口。在P节点中将入向SSF帧中各个客户业务的业务块传输到对应的出向端口，并在出向端口，将不同客户业务的业务块重新映射、组装到出向SSF帧中，以从该出向端口发送所述出向SSF帧。可以理解的是，每一个出向SSF帧都承载不同的客户业务。
需要说明的是，入向端口接收到的也可以是由多个入向SSF帧组成的入向SSMF复帧；在出向端口，也可以由多个出向SSF帧组成出向SSMF复帧，并将不同客户业务的业务块映射到SSMF复帧中。
本公开实施例提供的业务数据交换方法，基于能够承载多个不同的客户业务的SSF帧或由多个SSF帧组成的SSMF复帧，对不同 客户业务在P节点的入向端口和出向端口之间进行交换，从而建立了承载不同客户业务的SSC通道，能够同时对不同颗粒度的客户业务进行传输。本公开实施例提供的业务数据交换方法实现了灵活颗粒业务在刚性管道传输，满足低时延、低抖动、硬隔离、灵活带宽的传输需求，而不再受现有FlexE、SPN、MTN等标准对最小客户业务颗粒度的限制；能够同时支持多个以太网业务，或/和TDM业务，业务速率灵活；此外，还能够以SPN、MTN、以太网、OTN等中的任意一者作为服务层传输SSF帧，实现了对现有的以太网、FlexE、SPN、MTN、OTN等标准体系的良好兼容。
作为一种可选的实施方式，在本公开实施例中，通过时隙调度的方式在P节点中进行由入向SSF帧中的时隙到出向SSF帧中的时隙，或入向SSMF复帧中的时隙到出向SSMF复帧中的时隙的时隙交叉。
相应地，参照图22，步骤S210具体包括：在步骤S211中，确定入向端口接收到的不同入向时隙中的业务块的出向端口，其中，所述入向时隙为至少一个入向SSF帧中的时隙；并且，步骤S220具体包括：在步骤S221中，将对应同一出向端口的不同入向时隙中的业务块分别映射到不同的出向时隙中，其中，所述出向时隙为至少一个出向SSF帧中的时隙。
图23示出了在P节点进行时隙交叉一种可选的实施方式。
在图23中，P节点有两个入向端口SSC SI 1和SSC SI 2，有两个出向端口SSC SI 3和SSC SI 4。SSC SI 1接收到的入向SSF帧中的部分时隙对应于SSC SI 3中出向SSF帧的部分时隙，还有部分时隙对应于SSC SI 4中出向SSF帧的部分时隙；同样，SSC SI 2接收到的入向SSF帧中的部分时隙对应于SSC SI 3中出向SSF帧的部分时隙，还有部分时隙对应于SSC SI 4中出向SSF帧的部分时隙。
作为一种可选的实施方式，在本公开实施例中，P节点中存储有不同入向端口中入向SSF帧或入向SSMF帧的时隙，与不同出向端口中出向SSF帧或出向SSMF帧的时隙的对应关系。
相应地，在一些实施例中，参照图24，步骤S211具体包括：在 步骤S2111中，根据时隙交叉配置表，确定入向端口接收到的不同入向时隙中的业务块的出向端口，其中，所述时隙交叉配置表存储有各个入向时隙与各个出向时隙的对应关系。
需要说明的是，在本公开实施例中，所述时隙交叉配置表可以由网管、软件定义网络(SDN，Software Defined Network)控制器或动态协议完成预配置。
在本公开实施例中，P节点的各个出向端口与各个入向端口之间可能存在微小的速率差异(不大于200ppm)，作为一种可选的实施方式，在发送方向可以对SSF帧或SSMF复帧的各个时隙中的业务Idle块进行增删处理，从而实现各入向端口的时隙到各出向端口的时隙的速率适配。
相应地，在一些实施例中，参照图25，在步骤S211至步骤S221以外，所述业务数据交换方法还包括：在步骤S241中，根据本地***时钟和出向时隙的速率，对同一出向时隙中的业务块组成的业务块码流中的业务Idle块进行增/删处理，和/或，在步骤S242中，根据本地***时钟和入向时隙的速率，对同一入向时隙中的业务块组成的业务块码流中的业务Idle块进行增/删处理。
需要说明的是，在本公开实施例中，可以只执行步骤S241，不执行步骤S242；也可以只执行步骤S242，不执行步骤S241；还可以同时执行步骤S241和步骤S242。例如，当需要对出向时隙中的客户业务速率与出向时隙的速率进行适配时，则执行步骤S241；当需要对入向时隙中的客户业务速率与入向时隙的速率进行适配时，则执行步骤S242；当需要对入向时隙中的客户业务速率与入向时隙的速率、出向时隙中的客户业务速率和出向时隙的速率都进行适配时，则同时执行步骤S241和步骤S242。此外，本公开对执行步骤S241和/或步骤S242的顺序不做特殊限定。
在本公开实施例中，出向SSF帧的速率与出向端口的速率也可能存在微小差异，作为一种可选的实施方式，在SSF帧之间***帧间Idle块，进行SSF帧速率与服务层速率的适配。
相应地，在一些实施例中，参照图26，在步骤S211至步骤S221 以外，所述业务数据交换方法还包括：在步骤S251中，根据本地***时钟和出向端口的速率，对同一出向端口中的出向SSF帧之间的帧间Idle块进行增/删处理，和/或，在步骤S252中，根据本地***时钟和入向端口的速率，对同一入向端口中的入向SSF帧之间的帧间Idle块进行增/删处理。
需要说明的是，在本公开实施例中，可以只执行步骤S251，不执行步骤S252；也可以只执行步骤S252，不执行步骤S251；还可以同时执行步骤S251和步骤S252。例如，当需要对出向端口中的SSF帧的速率与出向端口的服务层速率进行适配时，则执行步骤S251；当需要对入向端口中的SSF帧的速率与入向端口的服务层速率进行适配时，则执行步骤S252；当需要对入向端口的SSF帧的速率与入向端口的服务层速率、出向端口中的SSF帧的速率和出向端口的服务层速率都进行适配时，则同时执行步骤S251和步骤S252。此外，本公开对执行步骤S251和/或步骤S252的顺序不做特殊限定。
在一些实施例中，所述入向端口，和/或，所述出向端口包括以太网端口、切片通道层SCL端口、MTN Path通道端口、FlexE Client端口、OTN的ODUk接口中的任意一者。
第三方面，参照图27，本公开实施例提供一种业务数据提取方法，包括：在步骤S310中，从至少一个SSF帧中提取预定客户业务的业务块，其中，每一个所述SSF帧都承载有多个不同客户业务的业务块；在步骤S320中，对所述预定客户业务的业务块进行解码，提取所述预定客户业务的业务数据。
需要说明的是，在本公开实施例中，所述预定客户业务即源PE节点发送给当前宿PE节点的客户业务。宿PE节点接收到SSF帧或SSMF复帧后，会从SSF帧或SSMF复帧中提取所述预定客户业务的业务块，并将所述预定客户业务的业务块进行解码，从而提取出该客户业务的业务数据。
还需要说明的是，在宿PE节点中对预定客户业务的业务块进行解码，是在源PE节点中根据客户业务生成业务块的逆过程。
本公开实施例提供的业务数据提取方法，从能够承载多个不同 的客户业务的SSF帧或由多个SSF帧组成的SSMF复帧中提取预定客户业务，建立起了从源PE节点到宿PE节点SSC通道，不同颗粒度的客户业务对应的SSC通道的带宽不同。本公开实施例提供的业务数据提取方法实现了灵活颗粒业务在刚性管道传输，满足低时延、低抖动、硬隔离、灵活带宽的传输需求，而不再受现有FlexE、SPN、MTN等标准对最小客户业务颗粒度的限制；能够同时支持多个以太网业务，或/和TDM业务，业务速率灵活；此外，还能够以SPN、MTN、以太网、OTN等中的任意一者作为服务层传输SSF帧，实现了对现有的以太网、FlexE、SPN、MTN、OTN等标准体系的良好兼容。
作为一种可选的实施方式，本公开实施例中，宿PE节点通过时隙调度的方式，从SSF帧或SSMF复帧的时隙中提取预定客户业务的业务块。
相应地，在一些实施例中，参照图28，步骤S310具体包括：在步骤S311中，从SSF帧的预定时隙中提取所述预定客户业务的业务块，其中，所述预定时隙为至少一个SSF帧中承载所述预定客户业务的时隙。
在一些实施例中，参照图29，在步骤S311之后，所述业务数据提取方法还包括：在步骤S312中，将从所述预定时隙中提取的OAM块剥离。
如前文所述，本公开实施例中，所述预定客户业务可以是以太网业务，也可以是TDM业务。
相应地，在一些实施例中，所述预定客户业务包括以太网业务。
在一些实施例中，源PE节点将以太网业务的码流中的64/66B块直接作为所述预定业务的业务块，则在步骤S320中，对所述预定客户业务的符合IEEE 802.3编码规范的64/66B以太网业务块进行解码，提取所述预定客户业务的业务数据。
在一些实施例中，源PE节点将所述预定客户业务的以太网业务块进行压缩转码生成所述预定客户业务的业务块，此时，需要将所述预定客户业务的业务块解压缩为符合IEEE 802.3编码规范的64/66B 以太网业务块，并对所述64/66B以太网业务块进行解码，提取所述预定客户业务的业务数据。
实施例十三
在本实施例十三中，源PE节点利用256/257B编码将以太网业务的64/66B块压缩转码，生成所述预定客户业务的业务块；相应地，在宿PE节点，利用256/257B编码将所述预定客户业务的业务块解压缩为所述64/66B以太网业务块。
从256/257B编码到64/66B编码的转码方式遵循IEEE 802.3标准，即1个256/257B块解压缩转码为4个64/66B块。
实施例十四
在本实施例十四中，源PE节点利用65B编码将以太网业务的64/66B块压缩转码，生成所述预定客户业务的业务块；相应地，在宿PE节点中，利用65B编码将所述预定客户业务的业务块解压缩为所述64/66B以太网业务块。
需要说明的是，若源PE节点在将64/66B块压缩转码为65B块时，删除了64/66B块的同步头中的第一个比特，则在本实施例十四中，在65B块的同步头的第一个比特之前，新增一个比特；若源PE节点在将64/66B块压缩转码为65B块时，删除了64/66B块的同步头中的第二个比特，则在本实施例十四中，在65B块的同步头的第一个比特之后，新增一个比特。
在一些实施例中，所述预定客户业务包括时分复用TDM业务。
实施例十五
在本实施例十五中，源PE节点根据标准组织城域以太网论坛(MEF，Metro Ethernet Forum)发布的标准“MEF 8 Implementation Agreement for the Emulation of PDH Circuits over Metro Ethernet Networks”中规范的以太网电路仿真服务(CESoETH，Circuit Emulation Services over Ethernet)，将TDM业务映射、封装到以太网报文中，并实施例九或实施例十生成所述预定客户业务的业务块；相应地，在宿PE节点，根据CESoETH将所述预定客户业务业务的业务块解映射为TDM业务码流，从所述TDM业务码流中提取所述 预定客户业务的业务数据。
实施例十六
在本实施例十六中，源PE节点将恒定速率的TDM业务的比特流按照业务字节或比特直接封装编码，生成符合IEEE 802.3编码规范的64/66B块，作为所述预定客户业务的业务块；相应地，在宿PE节点中，根据IEEE 802.3编码规范将所述64/66B块解码为TDM业务码流，从所述TDM业务码流中提取所述预定客户业务的业务数据。
实施例十七
在本实施例十七中，如图30所示，服务层为以太网，通过以太网链路及P节点SSC层的时隙交叉，从而建立起可承载灵活颗粒业务的端到端SSC通道，即图30中的Sub Slicing Channel。如图30所示,在源PE节点和P节点之间、以及宿PE节点和P节点之间都是标准的以太网连接(例如10GE)，这两条以太网连接中承载的客户业务在P节点通过SSC时隙交叉，从而形成从PE源节点到PE宿节点的一条端到端SSC通道。
实施例十八
在本实施例十八中，如图31所示，服务层为SPN，通过SPN提供的Slicing Channel连接及P3节点SSC层的时隙交叉，从而建立起可承载灵活颗粒业务的端到端SSC通道，即图31中的Sub Slicing Channel 1-5。如图31所示,通过P节点P2、P4的SCL交叉，形成SSC通道的服务层通道Slicing Channel 1-3和Slicing Channel 3-5，这两条SCL通道中承载客户业务Client Service A的SSC通道在P3节点通过时隙交叉，从而形成从PE1节点到PE5节点承载Client Service A的一条端到端SSC通道，即图31中的Sub Slicing Channel 1-5。
对于P2节点和P4节点SPN SCL层的SCL交叉，由于SSF帧是标准的S+D+T结构，对SCL(或MTN Path)而言SSF帧就是业务数据，SCL(或MTN Path)无需感知SSF帧，直接完成SCL(或MTN Path)层交叉。P2节点或P4节点的SCL(或MTN Path)交叉方式如图32所示。
此外，因为P2节点和P4节点只是完成SCL(或MTN Path)交 叉，无需感知SSF帧，因此P2和P4可以是传统的SPN设备，而PE1节点、P3节点、PE5节点是支持SSC通道的设备。因此，本实施例十四也是一种支持SSC通道的设备和传统的SPN设备互通的场景。
第四方面，参照图33，本公开实施例提供一种运营商边缘设备PE，包括：一个或多个处理器101；存储装置102，其上存储有一个或多个程序，当所述一个或多个程序被所述一个或多个处理器执行，使得所述一个或多个处理器实现上述任意一种业务数据处理方法，或上述任意一种业务数据提取方法；一个或多个I/O接口103，连接在所述处理器与存储器之间，配置为实现所述处理器与存储器的信息交互。
其中，处理器101为具有数据处理能力的器件，其包括但不限于中央处理器(CPU)等；存储器102为具有数据存储能力的器件，其包括但不限于随机存取存储器(RAM，更具体如SDRAM、DDR等)、只读存储器(ROM)、带电可擦可编程只读存储器(EEPROM)、闪存(FLASH)；I/O接口(读写接口)103连接在处理器101与存储器102间，能实现处理器101与存储器102的信息交互，其包括但不限于数据总线(Bus)等。
在一些实施例中，处理器101、存储器102和I/O接口103通过总线104相互连接，进而与计算设备的其它组件连接。
需要说明的是，当所述PE设备发送数据时，所述PE设备作为源PE节点；当所述PE设备接收数据时，所述PE设备作为宿PE节点。
上文已经对所述业务数据处理方法和所述业务数据提取方法进行了详细描述，此处不再赘述。
第五方面，参照图34，本公开实施例提供一种运营商交换设备，包括：一个或多个处理器201；存储装置202，其上存储有一个或多个程序，当所述一个或多个程序被所述一个或多个处理器执行，使得所述一个或多个处理器实现上述任意一种业务数据交换方法；一个或多个I/O接口203，连接在所述处理器与存储器之间，配置为实现所述处理器与存储器的信息交互。
其中，处理器201为具有数据处理能力的器件，其包括但不限于中央处理器(CPU)等；存储器202为具有数据存储能力的器件，其包括但不限于随机存取存储器(RAM，更具体如SDRAM、DDR等)、只读存储器(ROM)、带电可擦可编程只读存储器(EEPROM)、闪存(FLASH)；I/O接口(读写接口)203连接在处理器201与存储器202间，能实现处理器201与存储器202的信息交互，其包括但不限于数据总线(Bus)等。
在一些实施例中，处理器201、存储器202和I/O接口203通过总线204相互连接，进而与计算设备的其它组件连接。
上文已经对所述业务数据交换方法进行了详细描述，此处不再赘述。
第六方面，参照图35，本公开实施例提供一种计算机可读介质，其上存储有计算机程序，所述程序被处理器执行时实现上述任意一种业务数据处理方法，或上述任意一种业务数据交换方法，或上述任意一种业务数据提取方法。所述计算机可读介质包括但不限于随机存取存储器(RAM，更具体如SDRAM、DDR等)、只读存储器(ROM)、带电可擦可编程只读存储器(EEPROM)、闪存(FLASH)
上文已经对所述业务数据处理方法、所述业务数据提取方法和所述业务数据交换方法进行了详细描述，此处不再赘述。
本领域普通技术人员可以理解，上文中所公开方法中的全部或某些步骤、***、装置中的功能模块/单元可以被实施为软件、固件、硬件及其适当的组合。在硬件实施方式中，在以上描述中提及的功能模块/单元之间的划分不一定对应于物理组件的划分；例如，一个物理组件可以具有多个功能，或者一个功能或步骤可以由若干物理组件合作执行。某些物理组件或所有物理组件可以被实施为由处理器，如中央处理器、数字信号处理器或微处理器执行的软件，或者被实施为硬件，或者被实施为集成电路，如专用集成电路。这样的软件可以分布在计算机可读介质上，计算机可读介质可以包括计算机存储介质(或非暂时性介质)和通信介质(或暂时性介质)。如本领域普通技术人员公知的，术语计算机存储介质包括在用于存储信息(诸如计算 机可读指令、数据结构、程序模块或其它数据)的任何方法或技术中实施的易失性和非易失性、可移除和不可移除介质。计算机存储介质包括但不限于RAM、ROM、EEPROM、闪存或其它存储器技术、CD-ROM、数字多功能盘(DVD)或其它光盘存储、磁盒、磁带、磁盘存储或其它磁存储装置、或者可以用于存储期望的信息并且可以被计算机访问的任何其它的介质。此外，本领域普通技术人员公知的是，通信介质通常包含计算机可读指令、数据结构、程序模块或者诸如载波或其它传输机制之类的调制数据信号中的其它数据，并且可包括任何信息递送介质。
本文已经公开了示例实施例，并且虽然采用了具体术语，但它们仅用于并仅应当被解释为一般说明性含义，并且不用于限制的目的。在一些实例中，对本领域技术人员显而易见的是，除非另外明确指出，否则可单独使用与特定实施例相结合描述的特征、特性和/或元素，或可与其它实施例相结合描述的特征、特性和/或元件组合使用。因此，本领域技术人员将理解，在不脱离由所附的权利要求阐明的本公开的范围的情况下，可进行各种形式和细节上的改变。

Claims (45)

  1. 一种业务数据处理方法，包括：
    根据多个客户业务的业务数据分别生成各个所述客户业务的业务块；
    将各个所述客户业务的业务块映射到至少一个子切片帧SSF的净荷区；
    配置各个SSF帧的开销区字段，以获得所述至少一个SSF帧，其中，每一个所述SSF帧都承载有多个不同客户业务的业务块。
  2. 根据权利要求1所述的业务数据处理方法，其中，将各个所述客户业务的业务块映射至少一个子切片帧SSF的净荷区中的步骤包括：
    将所述至少一个SSF帧的净荷区划分为多个时隙；
    将各个所述客户业务的业务块分别映射到所述多个时隙中的不同时隙中，其中，不同的所述客户业务对应的时隙构成分别承载各个所述客户业务的子切片通道SSC。
  3. 根据权利要求2所述的业务数据处理方法，其中，在将各个所述客户业务的业务块映射到至少一个子切片帧SSF的净荷区中的步骤中，将各个所述客户业务的业务块映射到多个SSF帧的净荷区；
    将所述至少一个SSF帧的净荷区划分为多个时隙的步骤，包括：
    将包括多个所述SSF帧的子切片复帧SSMF的净荷区划分为所述多个时隙。
  4. 根据权利要求2或3所述的业务数据处理方法，其中，所述SSC通道的速率与所述时隙的速率的关系如下：
    RateofSSC＝Rateofslot×Amountofslot
    其中，RateofSSC为承载客户业务的SSC通道的速率，Rateofslot为每一个时隙的速率，Amountofslot为构成所述SSC通道的时隙的 数量。
  5. 根据权利要求2或3所述的业务数据处理方法，其中，将各个所述客户业务的业务块分别映射到所述多个时隙中的不同时隙的步骤包括：
    根据不同客户业务的颗粒度确定所述多个时隙中，分别承载不同客户业务的时隙的位置和数量；
    根据承载不同客户业务的时隙的位置和数量，将不同客户业务的业务块映射到对应的时隙中。
  6. 根据权利要求2所述的业务数据处理方法，其中，配置各个SSF帧的开销区字段，以获得所述至少一个SSF帧的步骤包括：
    在所述至少一个SSF帧的开销区中配置各个所述客户业务与分别承载各个所述客户业务的时隙的对应关系；
    配置所述至少一个SSF帧的其它开销字段，从而获得所述至少一个SSF帧。
  7. 根据权利要求6所述的业务数据处理方法，其中，在所述至少一个SSF帧的开销区中配置各个所述客户业务与分别承载各个所述客户业务的时隙的对应关系的步骤包括：
    在所述开销区的时隙标识字段中配置承载客户业务的时隙信息；
    在所述开销区的通道标识字段中配置承载客户业务的SSC通道信息。
  8. 根据权利要求7所述的业务数据处理方法，其中，在将所述至少一个SSF帧的净荷区划分为多个时隙的步骤中，将多个SSF帧的净荷区划分为多个时隙；
    在所述至少一个SSF帧的开销区中配置各个所述客户业务与分别承载各个所述客户业务的时隙的对应关系的步骤还包括：
    在所述开销区的复帧指示字段中配置所述SSF帧在由多个SSF 帧组成的SSMF复帧中的位置信息。
  9. 根据权利要求6至8中任意一项所述的业务数据处理方法，其中，所述SSF帧的其他开销字段包括：
    帧类型字段，用于指示所述SSF帧结构；
    故障指示字段，用于指示服务层通道故障情况；
    业务类型字段，用于标识客户业务的类型；
    校验字段，用于存储校验信息。
  10. 根据权利要求1所述的业务数据处理方法，其中，根据多个客户业务的业务数据分别生成各个所述客户业务的业务块的步骤之后，所述业务数据处理方法还包括：
    在由同一种客户业务的业务块组成的业务块码流中，***操作维护管理OAM块。
  11. 根据权利要求1所述的业务数据处理方法，其中，根据多个客户业务的业务数据分别生成各个所述客户业务的业务块的步骤之后，所述业务数据处理方法还包括：
    在由同一种客户业务的业务块组成的业务块码流中，***业务空闲块。
  12. 根据权利要求1所述的业务数据处理方法，其中，配置各个SSF帧的开销区字段，以获得所述至少一个子切片帧SSF的步骤之后，所述业务数据处理方法还包括：
    根据所述SSF帧的速率与服务层端口速率，在相邻的所述SSF帧之间***帧间空闲块。
  13. 根据权利要求1所述的业务数据处理方法，其中，所述SSF帧由符合IEEE 802.3编码规范的64/66B块构成。
  14. 根据权利要求13所述的业务数据处理方法，其中，所述SSF帧包括起始块、至少一个数据块、终止块，且所述SSF帧的帧长度固定。
  15. 根据权利要求14所述的业务数据处理方法，其中，所述业务数据处理方法还包括：
    在所述数据块，和/或，所述终止块中承载所述SSF帧的净荷；
    在所述起始块、所述数据块、所述终止块中的至少一者中承载所述SSF帧的开销。
  16. 根据权利要求13所述的业务数据处理方法，其中，所述客户业务包括以太网业务。
  17. 根据权利要求16所述的业务数据处理方法，其中，在根据多个客户业务的业务数据分别生成各个所述客户业务的业务块的步骤中，将客户业务的符合IEEE 802.3编码规范的64/66B以太网业务块当做所述业务块。
  18. 根据权利要求16所述的业务数据处理方法，其中，根据多个客户业务的业务数据分别生成各个所述客户业务的业务块的步骤包括：
    将客户业务的符合IEEE 802.3编码规范的64/66B以太网业务块进行压缩转码生成所述业务块。
  19. 根据权利要求18所述的业务数据处理方法，其中，将客户业务的符合IEEE 802.3编码规范的64/66B以太网业务块进行压缩转码生成所述业务块的步骤包括：
    利用256/257B编码将所述64/66B以太网业务块压缩转码为符合IEEE 802.3标准的256/257B块。
  20. 根据权利要求18所述的业务数据处理方法，其中，将客户业务的符合IEEE 802.3编码规范的64/66B以太网业务块进行压缩转码生成所述业务块的步骤包括：
    利用65B编码将所述64/66B以太网业务块压缩转码为65B块。
  21. 根据权利要求20所述的业务数据处理方法，其中，利用65B编码将所述64/66B以太网业务块压缩转码为65B块的步骤包括：
    按照预定规则删除所述64/66B以太网业务块的同步头中的一个比特，获得所述65B块，所述预定规则包括删除所述同步头中的第一个比特，或删除所述同步头中的第二个比特。
  22. 根据权利要求13所述的业务数据处理方法，其中，所述客户业务包括时分复用TDM业务。
  23. 根据权利要求22所述的业务数据处理方法，其中，根据多个客户业务的业务数据分别生成各个所述客户业务的业务块的步骤包括：
    根据以太网电路仿真服务CESoETH将所述TDM业务的业务码流映射到以太网业务码流中，生成以太网业务块。
  24. 根据权利要求22所述的业务数据处理方法，其中，根据多个客户业务的业务数据分别生成多个业务块的步骤包括：
    将TDM业务的业务码流进行编码，生成符合IEEE 802.3编码规范的64/66B块。
  25. 根据权利要求1至3、6至8、10至24中任意一项所述的业务数据处理方法，其中，所述业务数据处理方法还包括：
    对所述SSF帧进行服务层处理，以通过所述服务层传输所述SSF帧。
  26. 一种业务数据交换方法，包括：
    确定入向端口接收到的入向SSF帧中的各个业务块的出向端口，其中，每一个所述入向SSF帧都承载有多个不同客户业务的业务块；
    将对应同一出向端口的业务块映射到至少一个出向SSF帧中，其中，每一个所述出向SSF帧都承载有多个不同客户业务的业务块；
    通过出向端口传输所述出向SSF帧。
  27. 根据权利要求26所述的业务数据交换方法，其中，确定入向端口接收到的入向SSF帧中的各个业务块的出向端口的步骤包括：
    确定入向端口接收到的不同入向时隙中的业务块的出向端口，其中，所述入向时隙为至少一个入向SSF帧中的时隙；
    将对应同一出向端口的业务块映射到至少一个出向SSF帧中的步骤包括：
    将对应同一出向端口的不同入向时隙中的业务块分别映射到不同的出向时隙中，其中，所述出向时隙为至少一个出向SSF帧中的时隙。
  28. 根据权利要求27所述的业务数据交换方法，其中，确定入向端口接收到的不同入向时隙中的业务块的出向端口的步骤包括：
    根据时隙交叉配置表，确定入向端口接收到的不同入向时隙中的业务块的出向端口，其中，所述时隙交叉配置表存储有各个入向时隙与各个出向时隙的对应关系。
  29. 根据权利要求27或28所述的业务数据交换方法，其中，所述业务数据交换方法还包括：
    根据本地***时钟和出向时隙的速率，对同一出向时隙中的业务块组成的业务块码流中的业务空闲块进行增/删处理；和/或，
    根据本地***时钟和入向时隙的速率，对同一入向时隙中的业务块组成的业务块码流中的业务空闲块进行增/删处理。
  30. 根据权利要求27或28所述的业务数据交换方法，其中，所述业务数据交换方法还包括：
    根据本地***时钟和出向端口的速率，对同一出向端口中的出向SSF帧之间的帧间空闲块进行增/删处理；和/或，
    根据本地***时钟和入向端口的速率，对同一入向端口中的入向SSF帧之间的帧间空闲块进行增/删处理。
  31. 一种业务数据提取方法，包括：
    从至少一个SSF帧中提取预定客户业务的业务块，其中，每一个所述SSF帧都承载有多个不同客户业务的业务块；
    对所述预定客户业务的业务块进行解码，提取所述预定客户业务的业务数据。
  32. 根据权利要求31所述的业务数据提取方法，其中，从至少一个SSF帧中提取预定客户业务的业务块的步骤包括：
    从至少一个所述SSF帧的预定时隙中提取所述预定客户业务的业务块，其中，所述预定时隙为至少一个SSF帧中承载所述预定客户业务的时隙。
  33. 根据权利要求32所述的业务数据提取方法，其中，从至少一个所述SSF帧的预定时隙中提取所述预定客户业务的业务块的步骤之后，所述业务数据提取方法还包括：
    将从所述预定时隙中提取的OAM块剥离。
  34. 根据权利要求31至33中任意一项所述的业务数据提取方法，其中，所述预定客户业务包括以太网业务。
  35. 根据权利要求34所述的业务数据提取方法，其中，对所述预定客户业务的业务块进行解码，提取所述预定客户业务的业务数据的步骤包括：
    对所述预定客户业务的符合IEEE 802.3编码规范的64/66B以太网业务块进行解码，提取所述预定客户业务的业务数据。
  36. 根据权利要求34所述的业务数据提取方法，其中，所述预定客户业务的业务块为经过压缩转码生成的业务块；
    对所述预定客户业务的业务块进行解码，提取所述预定客户业务的业务数据的步骤包括：
    将所述预定客户业务的业务块解压缩为符合IEEE 802.3编码规范的64/66B以太网业务块；
    对所述64/66B以太网业务块进行解码，提取所述预定客户业务的业务数据。
  37. 根据权利要求36所述的业务数据提取方法，其中，所述预定客户业务的业务块为利用256/257B编码压缩转码生成的256/257B块；
    将所述预定客户业务的业务块解压缩为符合IEEE 802.3编码规范的64/66B以太网业务块的步骤包括：
    利用256/257B编码将所述预定客户业务的业务块解压缩为所述64/66B以太网业务块。
  38. 根据权利要求36所述的业务数据提取方法，其中，所述预定客户业务的业务块为利用65B编码压缩转码生成的65B块；
    将所述预定客户业务的业务块解压缩为符合IEEE 802.3编码规范的64/66B以太网业务块的步骤包括：
    利用65B编码将所述预定客户业务的业务块解压缩为所述64/66B以太网业务块。
  39. 根据权利要求38所述的业务数据提取方法，其中，利用65B编码将所述预定客户业务的业务块解压缩为所述64/66B以太网业务块的步骤包括：
    按照预定规则在所述65B块的同步头中增加一个比特，获得所述64/66B以太网业务块，所述预定规则包括在所述同步头的第一个比特前增加一个比特，或在所述同步头的第一个比特后增加一个比特。
  40. 根据权利要求31至33中任意一项所述的业务数据提取方法，其中，所述预定客户业务包括时分复用TDM业务。
  41. 根据权利要求40所述的业务数据提取方法，其中，所述预定客户业务的业务块是根据CESoETH将TDM业务码流映射到以太网业务码流中生成的以太网业务块；
    对所述预定客户业务的业务块进行解码，提取所述预定客户业务的业务数据的步骤包括：
    根据CESoETH将所述预定客户业务的业务块解映射为TDM业务码流，从所述TDM业务码流中提取所述预定客户业务的业务数据。
  42. 根据权利要求40所述的业务数据提取方法，其中，所述预定客户业务的业务块是根据IEEE 802.3编码规范对TDM业务码流进行编码生成的64/66B块；
    对所述预定客户业务的业务块进行解码，提取所述预定客户业务的业务数据的步骤包括：
    根据IEEE 802.3编码规范将所述64/66B块解码为TDM业务码流，从所述TDM业务码流中提取所述预定客户业务的业务数据。
  43. 一种运营商边缘设备，包括：
    一个或多个处理器；
    存储装置，其上存储有一个或多个程序，当所述一个或多个程序被所述一个或多个处理器执行，使得所述一个或多个处理器实现根据权利要求1至25中任意一项所述的业务数据处理方法，或根据权利要求31至42中任意一项所述的业务数据提取方法；
    一个或多个输入输出(I/O)接口，连接在所述处理器与存储器 之间，配置为实现所述处理器与存储器的信息交互。
  44. 一种运营商交换设备，包括：
    一个或多个处理器；
    存储装置，其上存储有一个或多个程序，当所述一个或多个程序被所述一个或多个处理器执行，使得所述一个或多个处理器实现根据权利要求26至30中任意一项所述的业务数据交换方法；
    一个或多个I/O接口，连接在所述处理器与存储器之间，配置为实现所述处理器与存储器的信息交互。
  45. 一种计算机可读介质，其上存储有计算机程序，所述程序被处理器执行时实现根据权利要求1至25中任意一项所述的业务数据处理方法，或权利要求26至30中任意一项所述的业务数据交换方法，或根据权利要求31至42中任意一项所述的业务数据提取方法。
PCT/CN2021/090977 2020-04-30 2021-04-29 业务数据处理、交换、提取方法及设备、计算机可读介质 WO2021219079A1 (zh)

Priority Applications (3)

Application Number Priority Date Filing Date Title
EP21795880.0A EP4145788A4 (en) 2020-04-30 2021-04-29 SERVICE DATA PROCESSING, EXCHANGE AND EXTRACTION METHODS, DEVICES AND COMPUTER-READABLE MEDIUM
US17/922,296 US20230164624A1 (en) 2020-04-30 2021-04-29 Service data processing, exchange and extraction methods, devices, and computer-readable medium
JP2022566074A JP2023523462A (ja) 2020-04-30 2021-04-29 サービスデータ処理方法、サービスデータ交換方法、サービスデータ抽出方法およびコンピュータ可読媒体

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202010367821.4A CN113595965A (zh) 2020-04-30 2020-04-30 业务数据处理、交换、提取方法及设备、计算机可读介质
CN202010367821.4 2020-04-30

Publications (1)

Publication Number Publication Date
WO2021219079A1 true WO2021219079A1 (zh) 2021-11-04

Family

ID=78237017

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/090977 WO2021219079A1 (zh) 2020-04-30 2021-04-29 业务数据处理、交换、提取方法及设备、计算机可读介质

Country Status (5)

Country Link
US (1) US20230164624A1 (zh)
EP (1) EP4145788A4 (zh)
JP (1) JP2023523462A (zh)
CN (1) CN113595965A (zh)
WO (1) WO2021219079A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2024068973A1 (en) * 2022-09-30 2024-04-04 Telefonaktiebolaget Lm Ericsson (Publ) Flexible framing for fronthaul

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116566542A (zh) * 2022-01-29 2023-08-08 中兴通讯股份有限公司 业务数据承载方法、承载帧结构及业务处理设备
CN117354159A (zh) * 2022-06-28 2024-01-05 中兴通讯股份有限公司 切片方法、业务处理方法、通信节点及存储介质
CN117891414A (zh) * 2024-03-14 2024-04-16 支付宝(杭州)信息技术有限公司 一种基于完美哈希的数据存储方法及相关设备

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20030048813A1 (en) * 2001-09-05 2003-03-13 Optix Networks Inc. Method for mapping and multiplexing constant bit rate signals into an optical transport network frame
CN1791057A (zh) * 2004-12-15 2006-06-21 华为技术有限公司 在光传送网中传输数据业务的方法及其装置
CN101051879A (zh) * 2007-04-06 2007-10-10 华为技术有限公司 低速业务复用及解复用的方法和装置
CN109478941A (zh) * 2016-07-22 2019-03-15 华为技术有限公司 一种多路业务传送、接收方法及装置

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109600188B (zh) * 2017-09-30 2020-04-28 华为技术有限公司 数据传输方法、传输设备和传输***

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20030048813A1 (en) * 2001-09-05 2003-03-13 Optix Networks Inc. Method for mapping and multiplexing constant bit rate signals into an optical transport network frame
CN1791057A (zh) * 2004-12-15 2006-06-21 华为技术有限公司 在光传送网中传输数据业务的方法及其装置
CN101051879A (zh) * 2007-04-06 2007-10-10 华为技术有限公司 低速业务复用及解复用的方法和装置
CN109478941A (zh) * 2016-07-22 2019-03-15 华为技术有限公司 一种多路业务传送、接收方法及装置

Non-Patent Citations (1)

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

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2024068973A1 (en) * 2022-09-30 2024-04-04 Telefonaktiebolaget Lm Ericsson (Publ) Flexible framing for fronthaul

Also Published As

Publication number Publication date
EP4145788A4 (en) 2024-04-24
CN113595965A (zh) 2021-11-02
JP2023523462A (ja) 2023-06-05
EP4145788A1 (en) 2023-03-08
US20230164624A1 (en) 2023-05-25

Similar Documents

Publication Publication Date Title
WO2021219079A1 (zh) 业务数据处理、交换、提取方法及设备、计算机可读介质
US11252098B2 (en) Data transmission method, transmitter, and receiver
US20210203588A1 (en) Data forwarding method and device
JP7026802B2 (ja) データ伝送方法、通信機器、および記憶媒体
CN107786320B (zh) 一种发送和接收业务的方法、装置和网络***
US9954644B2 (en) Ethernet data processing method, physical layer chip and Ethernet equipment
CN113972997A (zh) 一种传输数据的方法和设备
US11381338B2 (en) Data transmission method, communications device, and storage medium
WO2019029419A1 (zh) 透传业务频率的方法和设备
WO2020156642A1 (en) Cpri data block transmission method and apparatus
WO2021196753A1 (zh) 一种业务承载方法、数据交换方法、业务提取方法、pe设备、运营商交换设备及存储介质
JP7167345B2 (ja) データ伝送方法、通信機器、および記憶媒体
WO2024001220A1 (zh) 切片方法、业务处理方法、通信节点及存储介质
WO2019011003A1 (zh) 一种光网络中光监控信道处理的方法和装置
WO2023124551A1 (zh) 分组信号的发送方法、装置、存储介质以及电子装置
WO2020114084A1 (zh) 一种报文转发方法和装置
WO2018121223A1 (zh) 一种信号传送方法、装置和***
CN117938738A (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: 21795880

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2022566074

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

Country of ref document: EP

Effective date: 20221130