WO2023196068A1 - Système et procédé d'adaptation de débit de données client orientées paquets pour une transmission sur un réseau de transport métro (mtn) - Google Patents

Système et procédé d'adaptation de débit de données client orientées paquets pour une transmission sur un réseau de transport métro (mtn) Download PDF

Info

Publication number
WO2023196068A1
WO2023196068A1 PCT/US2023/014355 US2023014355W WO2023196068A1 WO 2023196068 A1 WO2023196068 A1 WO 2023196068A1 US 2023014355 W US2023014355 W US 2023014355W WO 2023196068 A1 WO2023196068 A1 WO 2023196068A1
Authority
WO
WIPO (PCT)
Prior art keywords
client
signal
thread
packet
mtn
Prior art date
Application number
PCT/US2023/014355
Other languages
English (en)
Inventor
Steven Scott GORSHE
Winston Mok
Original Assignee
Microchip Technology Inc.
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
Priority claimed from US18/116,293 external-priority patent/US20230318934A1/en
Application filed by Microchip Technology Inc. filed Critical Microchip Technology Inc.
Publication of WO2023196068A1 publication Critical patent/WO2023196068A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04J—MULTIPLEX COMMUNICATION
    • H04J3/00—Time-division multiplex systems
    • H04J3/16—Time-division multiplex systems in which the time allocation to individual channels within a transmission cycle is variable, e.g. to accommodate varying complexity of signals, to vary number of channels transmitted
    • H04J3/1605—Fixed allocated frame structures
    • H04J3/1652—Optical Transport Network [OTN]
    • H04J3/1658—Optical Transport Network [OTN] carrying packets or ATM cells
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04J—MULTIPLEX COMMUNICATION
    • H04J3/00—Time-division multiplex systems
    • H04J3/02—Details
    • H04J3/06—Synchronising arrangements
    • H04J3/07—Synchronising arrangements using pulse stuffing for systems with different or fluctuating information rates or bit rates
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L49/00—Packet switching elements
    • H04L49/35—Switches specially adapted for specific applications
    • H04L49/351—Switches specially adapted for specific applications for local area network [LAN], e.g. Ethernet switches
    • H04L49/352—Gigabit ethernet switching [GBPS]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • 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
    • H04J—MULTIPLEX COMMUNICATION
    • H04J2203/00—Aspects of optical multiplex systems other than those covered by H04J14/05 and H04J14/07
    • H04J2203/0001—Provisions for broadband connections in integrated services digital network using frames of the Optical Transport Network [OTN] or using synchronous transfer mode [STM], e.g. SONET, SDH
    • H04J2203/0073—Services, e.g. multimedia, GOS, QOS
    • H04J2203/0082—Interaction of SDH with non-ATM protocols
    • H04J2203/0085—Support of Ethernet

Definitions

  • a sublG packet-oriented client signal is one that can be carried over a channel within MTN that has a rate less than 1 Gbit/s (i.e., a sub 1G channel).
  • a sublG channel is referred to herein as a thread channel.
  • Both sublG CBR client signals and sublG packet-oriented client signals require a method to insert the client signals into the payload region of the thread channels of the MTN and to rate adapt the client signals to the thread channel rate, and a method to add thread path OAM (Operations, Administrations, and Maintenance) Overhead to the client stream.
  • OAM Operations, Administrations, and Maintenance
  • the rate at which the packets arrive at a source node of the MTN is variable.
  • An idle mapping procedure wherein idle blocks are inserted and/or removed within an inter-packet (IPG) region between Ethernet packets, may be used for rate adaptation of packet-oriented client signals.
  • IPG inter-packet
  • the reason why an IEEE 802.3 Clause 82 standard IMP approach is not directly applicable to sublG packet-oriented client signals is that the sublG packet-oriented client signals may utilize a line code other than 64B/66B-encoded blocks.
  • the present examples provide a system and method for mapping, including rate adaptation, of sublG Ethernet packet-oriented client data for transmission over a Metro Transport Network (MTN).
  • MTN Metro Transport Network
  • a method for performing rate adaptation of a sub 1G packet-oriented client signal for transmission over an MTN path includes, receiving a sublG packet-oriented client signal at a source node, wherein the sublG packet-oriented client signal comprises a plurality of client packets and an inter-packet gap (IPG) between respective ones of the plurality of client packets.
  • the method includes forming a 64B/66B -encoded client signal by encoding individual client packets of the plurality of client packets into a set of 64B/66B -encoded client blocks and filling the IPG between respective ones of the plurality of client packets with a set of 64B/66B idle blocks.
  • the method further includes, generating a 64B/66B -encoded client thread signal by inserting thread operations, administration and maintenance (ThOAM) overhead for the sublG packet-oriented client signal into the 64B/66B-encoded client signal.
  • ThOAM thread operations, administration and maintenance
  • the ThOAM overhead for the sublG packet-oriented client signal may be inserted as a Metro Transport Network (MTN) ordered set (OS) into the 64B/66B -encoded client signal to generate the 64B/66B-encoded client thread signal.
  • MTN Metro Transport Network
  • OS Metro Transport Network
  • the method continues by generating a rate adapted 64B/66B -encoded client thread signal by performing an idle mapping procedure (IMP) to modify a number of 64B/66B idle blocks in one or more of the sets of 64B/66B idle blocks of the 64B/66B -encoded client thread signal.
  • the method continues by generating an MTN path signal by defining a plurality of pseudo-Ethernet packets in the MTN path, defining a thread channel within the plurality of pseudoEthernet packets for carrying the sublG packet-oriented client signal, and mapping the rate adapted 64B/66B-encoded client thread signal into the defined thread channel within the plurality of pseudo-Ethernet packets.
  • IMP idle mapping procedure
  • a plurality of sublG packet-oriented client signals may be received at a source node.
  • the method includes generating a respective rate-adapted 64B/66B -encoded client thread signal for each of the plurality of sublG packet-oriented client signals, defining a respective thread channel within the plurality of pseudo-Ethernet packets for carrying respective ones of the plurality of sublG packet- oriented client signals, and mapping the respective rate-adapted 64B/66B-encoded client thread signals into the respective defined thread channel within the plurality of pseudoEthernet packets.
  • the method includes, transmitting the MTN path signal from the source node over the MTN path, receiving the MTN path signal at an ingress of a sublG-aware intermediate node of the MTN and extracting the rate adapted 64B/66B-encoded client thread signal from the plurality of pseudo-Ethernet packets of the MTN path signal.
  • the method further includes, generating a modified rate adapted 64B/66B-encoded client thread signal by performing idle mapping procedure (IMP) rate adaptation of the extracted rate adapted 64B/66B-encoded client thread signal to modify the number of 64B/66B idle blocks in one or more sets of the 64B/66B idle blocks to match an egress thread channel rate of the sublG-aware intermediate node.
  • IMP idle mapping procedure
  • the method continues by generating an egress MTN path signal by defining a plurality of pseudo-Ethernet packets in the MTN path at an egress of the subl G-aware intermediate mode, defining an egress thread channel within the plurality of pseudo-Ethernet packets for carrying the sublG packet-oriented client signal, and mapping the modified rate adapted 64B/66B-encoded client thread signal into the defined egress thread channel within the plurality of pseudo-Ethernet packets.
  • the method continues by transmitting the egress MTN path signal from the sublG-aware intermediate node to a next node of the MTN or to a sink node.
  • the method continues by extracting the sets of 64B/66B-encoded client blocks, the sets of 64B/66B idle blocks and the ThOAM from the modified rate adapted 64B/66B-encoded client thread signal and decoding respective sets of the extracted 64B/66B-encoded client blocks to recover the sub 1G packet-oriented client signal.
  • a source node for transmitting packet-oriented client data over a Metro Transport Network (MTN).
  • the source node includes circuitry to receive a sublG packet-oriented client signal at the source node, wherein the sublG packet-oriented client signal comprises a plurality of client packets and an inter-packet gap (IPG) between respective ones of the plurality of client packets.
  • the source node additionally comprises circuitry to form a 64B/66B -encoded client signal by encoding individual client packets of the plurality of client packets into a set of 64B/66B-encoded client blocks and filing the (IPG) between respective ones of the plurality of client packets with a set of 64B/66B idle blocks.
  • the source node includes circuitry to insert thread operations, administration and maintenance (ThOAM) overhead for the subl G packet-oriented client signal into the 64B/66B-encoded client signal to generate a 64B/66B-encoded client thread signal.
  • ThOAM thread operations, administration and maintenance
  • the ThOAM overhead for the sublG packet-oriented client signal may be inserted as a Metro Transport Network (MTN) ordered set (OS) into the 64B/66B-encoded client signal to generate the 64B/66B- encoded client thread signal.
  • MTN Metro Transport Network
  • OS Metro Transport Network
  • the source node further includes circuitry to perform an idle mapping procedure (IMP) to modify a number of 64B/66B idle blocks in one or more of the sets of 64B/66B-encoded idle blocks of the 64B/66B-encoded client thread signal to generate a rate adapted 64B/66B-encoded client thread signal.
  • the circuitry of the source node additionally defines a plurality of pseudo-Ethernet packets in the MTN path, defines a thread channel within the plurality of pseudo-Ethernet packets for carrying the sublG packet-oriented client signal, and maps the rate adapted 64B/66B-encoded client thread signal into the defined thread channel within the plurality of pseudo-Ethernet packets to generate an MTN path signal.
  • IMP idle mapping procedure
  • the sublG packet-oriented client signal is a 1000 Mbit/s (lOOOBASE-x) stream employing 8B/10B code blocks
  • the source node further includes circuitry to transcode the 8B/10B code blocks into 64B/66B code blocks to form the 64B/66B- encoded client signal.
  • a plurality of sublG packet-oriented client signals may be received at a source node.
  • the circuitry of the source node generates a respective rate-adapted 64B/66B-encoded client thread signal for respective ones of the plurality of sublG packet-oriented client signals, defines a respective thread channel for carrying respective ones of the plurality of sublG packet-oriented client signals and maps respective ones of the rate-adapted 64B/66B-encoded client thread signals into the respective defined thread channel within the plurality of pseudo-Ethernet packets to generate the MTN path signal.
  • FIG. 1 is an example of functional blocks for a source node, an intermediate node and a sink node for mapping a sublG packet-oriented client signal into an MTN path, performing IMP rate adaptation, and extracting the sublG packet-oriented client signal from the MTN path.
  • FIG. 2 illustrates an example block diagram of a source node for implementing IMP rate adaptation and mapping a sublG packet-oriented client signal into an MTN path.
  • FIG. 3 A illustrates an example pseudo-Ethemet packet format having rate adapted 64B/66B -encoded client thread signal mapped into a payload area of data blocks of the pseudo-Ethemet packet 64-bits at a time with each MTN path data block (/D/) carrying a single sublG packet-oriented client signal.
  • FIG. 3B illustrates an example of the pseudo-Ethernet packet format of FIG. 3 A with 962 -block packets carrying multiples of 480 multiplexed threads.
  • FIG. 4A illustrates an example pseudo-Ethernet packet format rate adapted 64B/66B- encoded client thread signal mapped into merged payload area of data blocks of the pseudo-Ethemet packet 66-bits at a time with respective 398-block pseudo-Ethernet packets carrying 64B/66B-encoded blocks from 384 of the 480 rate adapted 64B/66B- encoded client thread signals.
  • FIG. 4B illustrates an example of the pseudo-Ethernet packet format of FIG. 4A with 398-block packets for carrying 384 of the 480 multiplexed threads.
  • FIG. 5 illustrates an example pseudo-Ethernet packet format for 66-bit mapping of rate adapted 64B/66B-encoded client thread signals into merged payload areas of data blocks with respective 264-block pseudo-Ethernet packets carrying 64B/66B-encoded blocks from 254 clients of the 480 rate adapted 64B/66B-encoded client thread signals.
  • FIG. 6 illustrates an example of the pseudo-Ethernet packet format of FIG. 5 with 264- block packets for carrying 254 of 480 multiplexed threads.
  • FIG. 7 illustrates an example of 1023 -block pseudo-Ethernet packets for carrying 990 blocks of the 480 multiplexed threads.
  • FIG. 8 illustrates an example of 1091 -block pseudo-Ethernet packets for carrying 990 blocks of 480 multiplexed threads.
  • FIG. 9 illustrates an example of 545-block pseudo-Ethernet packets for carrying 526 blocks of the 480 multiplexed threads.
  • FIG. 10 is an example flow diagram illustrating a method for performing rate adaptation of packet-oriented client data for transmission over an MTN.
  • FIG. 11 A is an example flow diagram illustrating a method for performing rate adaption at a sublG-aware intermediate node of the MTN.
  • FIG. 1 IB is an example flow diagram illustrating a method for performing data extraction at a sink node of the MTN.
  • first, second, third, without limitation, may be used herein to describe various elements, components, regions, layers, and/or sections, these elements, components, regions, layers, and/or sections should not be limited by these terms. These terms are only used to distinguish one element, component, region, layer, or section from another region, layer, or section. Thus, a first element, component, region, layer, or section discussed below could be termed a second element, component, region, layer, or section without departing from the teachings of the present invention.
  • the present examples provide a novel system and method for carrying sublG packet-oriented client signals through an ITU-T G.8312 Metro Transport Network (MTN).
  • MTN Metro Transport Network
  • the present examples provide a common basis for rate adaptation and operations, administration and maintenance (0AM) overhead insertion for sublG packet- oriented client signals for transmission over a Metro Transport Network (MTN) path.
  • MTN Metro Transport Network
  • a system 100 for transmitting a sublG packet-oriented client signal over a Metro Transport Network includes a source node 105 comprising circuitry to receive a sub 1 G packet-oriented client signal 120, wherein the sub 1 G packet- oriented client signal 120 comprises a plurality of client packets and an inter-packet gap (IPG) between respective ones of the plurality of client packets.
  • MTN Metro Transport Network
  • Circuitry of the source node 105 forms a 64B/66B -encoded client signal by encoding individual client packets of the plurality of client packets into a set of 64B/66B-encoded client blocks and fdling the IPG between respective ones of the plurality of client packets with a set of 64B/66B idle blocks, 126.
  • the sublG packet-oriented client signal is a 1000 Mbit/s Ethernet (1000BASE-x/ GbE) stream employing 8B/10B code blocks.
  • the 8B/10B code blocks of the subl G packet-oriented client signal could be transcoded directly into 64B/66B code blocks in order to preserve the control code information, including ordered sets, of the sublG packet-oriented client signal.
  • Circuitry of the source node 105 additionally generates a 64B/66B-encoded client thread signal by inserting thread operations, administration and maintenance (ThOAM) overhead for the sublG packet-oriented client signal into the 64B/66B -encoded client signal, 127.
  • the ThOAM overhead for the sublG packet-oriented client signal is inserted as a Metro Transport Network (MTN) ordered set (OS) into the IPG of the 64B/66B-encoded client signal.
  • MTN Metro Transport Network
  • OS Metro Transport Network
  • the circuitry of the source node 105 generates a rate adapted 64B/66B-encoded client thread signal by performing an idle mapping procedure (IMP) to modify a number of 64B/66B idle blocks in one or more of the sets of 64B/66B idle blocks of the 64B/66B- encoded client thread signal, 130.
  • IMP idle mapping procedure
  • GMP Generic Mapping Procedure
  • the circuitry of the source node 105 generates an MTN path signal by defining a plurality of pseudo-Ethernet packets in the MTN path, defining a thread channel within the plurality of pseudo-Ethernet packets for carrying the sublG packet-oriented client thread signal, and mapping the rate adapted 64B/66B -encoded client thread signal into the defined thread channel within the plurality of pseudo-Ethernet packets, 135.
  • the plurality of pseudo-Ethernet packets include a plurality of data bytes forming a payload area and the circuitry of the source node 105 segments the payload area into a plurality of thread channel members, assigns one or more of the plurality of thread channel members to the defined thread channel and maps the rate adapted 64B/66B- encoded client thread signal into the one or more of the plurality of thread channel members of the defined thread channel within the pluralitiy of pseudo-Ethemet packets to generate the MTN path signal.
  • the rate adapted 64B/66B-encoded client thread signal is then mapped into the one or more of the plurality of thread channel members of the defined thread channel within the plurality of pseudo-Ethernet packets.
  • the client control blocks e.g., frame start or terminate, idles, or ordered sets
  • mapping the rate adapted 64B/66B-encoded client thread signal into the thread channel members of the defined thread channel adds about a 3% signal overhead, this is considered acceptable for known applications.
  • Rate adaptation of the 64B/66B-encoded client thread signal results in the rate adapted 64B/66B-encoded client thread signal filling the bandwidth provided by the defined thread channel within the plurality of pseudo-Ethernet packets in the MTN path.
  • the pseudo-Ethemet packet are “pseudo” Ethernet in the sense that they lack much of the overhead of standard Ethernet packets and may only follow the Ethernet basic physical coding sublayer (PCS) packet syntax, beginning with the /S/ start control block and ending with a /T/ terminate control block.
  • PCS physical coding sublayer
  • This syntax allows pseudo-Ethernet packet boundaries to be identified at sublG-aware and sublG-unaware nodes and ensures that a sublG- unaware intermediate MTN node implementations can correctly identify the Ethernet inter-packet gap (IPG) for idle insertion and removal rate adaptation.
  • IPG Ethernet inter-packet gap
  • the pseudo-Ethernet packets are not processed by an Ethernet MAC, they may omit, for example, the Ethernet packet MAC overhead and the 32-bit cyclic redundancy check frame check sequence (CRC-32 FCS). Also, the pseudo-Ethernet packet lengths may be made much longer than the allowable Ethernet packet size in order to provide higher bandwidth efficiency.
  • CRC-32 FCS cyclic redundancy check frame check sequence
  • the source node 105 transmits the MTN path signal over a first portion of the MTN path 140, to a sublG-aware intermediate node 115 of the MTN.
  • the sublG-aware intermediate node 115 receives the MTN path signal at an ingress.
  • the sublG-aware intermediate node 115 includes circuitry for extracting the rate adapted 64B/66B -encoded client thread signal from the plurality of pseudo-Ethernet packets of the MTN path signal, 150.
  • the sublG-aware intermediate node 115 includes circuitry to generate a modified rate adapted 64B/66B -encoded client thread signal by performing IMP rate adaptation of the extracted rate adapted 64B/66B-encoded client thread signal to modify the number of 64B/66B idle blocks in one or more sets of the 64B/66B idle blocks to match an egress thread channel rate of the sublG-aware intermediate node 115, 155.
  • the sublG-aware intermediate node 115 additionally includes circuitry to generate an egress MTN path signal by defining a plurality of pseudo-Ethernet packets in the MTN path at an egress of the sublG-aware intermediate node, defining an egress thread channel within the plurality of pseudo-Ethernet packets for carrying the sublG packet-oriented client signal, and mapping the modified rate adapted 64B/66B-encoded client thread signal into defined egress thread channel 160.
  • the sublG-aware intermediate node 115 transmits the egress MTN path signal over a second portion of the MTN path 142 from the sub 1 G-aware intermediate node 115 to a next node of the MTN or to a sink node 110.
  • the sink node 110 includes circuitry to locate the plurality of pseudo-Ethemet packets in the egress MTN path signal received from the sub 1 G-aware intermediate node, 165.
  • the sink node 110 additionally includes circuitry to extract the sets of 64B/66B -encoded client blocks, the sets of 64B/66B idle blocks and the ThOAM from the modified rate adapted 64B/66B-encoded client thread signal of the egress MTN path signal, 170.
  • the sink node 110 further includes circuitry to decode respective sets of the extracted 64B/66B -encoded client blocks to recover the sublG packet-oriented client signal, 175.
  • the sets of 64B/66B idle blocks may be discarded.
  • FIG. 2 illustrates an example block diagram of a source node, 200, such as the source node 105 in accordance with FIG. 1, wherein a rate adapted 64B/66B -encoded client thread signal is mapped into a thread channel within a plurality of pseudo-Ethernet packets for carrying the sublG packet-oriented client signal.
  • an MTN section frame reference 240 is generated by a reference generator 205 in response to a reference clock 210.
  • a sublG packet-oriented client signal 215 comprising a plurality of client packets and an inter-packet gap (IPG) between respective ones of the plurality of client packets is provided to an encoder 220.
  • the encoder 220 forms a 64B/66B -encoded client signal 217 by encoding individual client packets of the plurality of client packets into a set of 64B/66B-encoded client blocks and filling the IPG between respective ones of the plurality of client packets with a set of 64B/66B idle blocks.
  • the 64B/66B-encoded client signal is then provided to a thread OAM circuit 225 which inserts thread operations, administration and maintenance (ThOAM) overhead for the sublG packet-oriented client signal into the 64B/66B- encoded client signal to generate a 64B/66B-encoded client thread signal 219.
  • An IMP circuit 230 then performs IMP to modify a number of 64B/66B idle blocks in one or more of the sets of 64B/66B idle blocks of the 64B/66B-encoded client thread signal to generate a rate adapted 64B/66B -encoded client thread signal 221.
  • IMP circuit 230 may precede thread OAM circuit 225.
  • the rate adapted 64B/66B -encoded client thread signal 221 is provided to a first in first out (FIFO) buffer 235.
  • a pseudo-Ethernet packet maker 250 defines a plurality of pseudoEthernet packets with a /S/, a /T/ and N-2 64B/66B data blocks.
  • the data bytes of the N-2 64B/66B data blocks form a payload area.
  • a combination of the data bytes of the N-2 64B/66B data blocks and data bytes of the /T/ data block form the payload area.
  • the pseudo-Ethernet packet maker 250 defines a thread channel within the plurality of pseudo-Ethernet packets for carrying the sublG packet-oriented client signal and maps the rate adapted 64B/66B-encoded client thread signal from the FIFO buffer 235 into the defined thread channel within the plurality of pseudo-Ethernet packets to generate the MTN path signal.
  • the pseudo- Ethernet packet maker 250 segments the payload area into a plurality of thread channel members, assigns one or more of the plurality of thread channel members to the defined thread channel and maps the rate adapted 64B/66B -encoded client thread signal into the one or more of the plurality of thread channel members of the defined thread channel within the pluralitiy of pseudo-Ethernet packets to generate the MTN path signal.
  • the pseudo-Ethemet packet maker 250 provides the pseudo-Ethernet packets to a multiplexer 270, which is controlled by a multiplexer controller 255.
  • the multiplexer controller 255 is controlled by the pseudo-Ethernet packet maker 250 and the MTN section frame reference 240 to direct the multiplexer 270 to select among the pseudo-Ethemet packets from the pseudo-Ethemet packet maker 250, idle blocks in the IPG between pseudo- Ethemet packets from the MTN idle source 265, and the MTN path overhead (POH) insertion opportunities in accordance with International Telecommunication Union Telecommunication Standardization Sector (ITU-T) Rec. G.8312 MTN from the MTN POH 260.
  • the output of the multiplexer 270 is provided to the MTN path 275.
  • a sub 1G channel is arranged to effectively carry the information from a lOMbit/s 10BASE Ethernet interface, which may result in providing 480 x 10 Mbit/s channels within a 5Gbits/s MTN path.
  • a N x 5GBits/s MTN path would provide N x 480* 10 Mbit/s channels.
  • the rate adapted 64B/66B-encoded client thread signal into the MTN path in more detail.
  • a sub 1G channel is arranged to effectively carry the information from a lOMbit/s 10BASE Ethernet interface, which may result in providing 480 x 10 Mbit/s channels within a 5Gbits/s MTN path.
  • a N x 5GBits/s MTN path would provide N x 480* 10 Mbit/s channels.
  • 64B/66B -encoded client thread signal is carried as a bit stream in the thread channel members of the defined thread channel within the plurality of pseudo-Ethernet packets. Multiplexing may be performed to accommodate multiple sublG packet-oriented client signals wherein the MTN path consists of a set of pseudo-Ethernet packets into which the multiple sub 1G packet-oriented client signals are multiplexed (interleaved).
  • FIG. 3A illustrates a 962-block pseudo-Ethernet packet wherein the payload area of the pseudo-Ethernet packet is divided into a plurality of thread channel members, each 64 bits wide.
  • each thread channel member has a capacity of lOMbit/s and fits into the payload area of a ZD/ block of the pseudo-Ethernet packet.
  • the thread channel members are numbered 1 to 480 and a thread channel that is N x lOMbit/s is allocated a set of N thread channel members.
  • FIG. 3B illustrates the frame format for MTN path overhead (POH) insertion opportunities in accordance with ITU-T Rec. G.8312 MTN, wherein B, A and L are different types of POH ordered set (OS) blocks in accordance with the ITU-T Rec. G.8312 MTN standard.
  • the MTN POH frame begins with the B POH block position located in the position prior to the appearance of the A POH block position. Note that in accordance ITU-T G.8312, there may be times when no POH is transmitted in the L or A POH block positions.
  • the pair of B POH blocks provide the reference points in the MTN POH frame, with the L or A blocks inserted into their respective positions within the MTN POH frame when they are applicable. If no POH is transmitted in the A or L block positions, an idle block may occupy that position without loss of generality.
  • MTN POH blocks are nominally separated by n * 16384 64B/66B blocks, where n represents the number of MTN Section layer 5 Gbit/s calendars slots carrying the MTN Path.
  • the pseudo-Ethernet packet length may be chosen such that it makes more efficient use of the interval between MTN POH blocks and provides sufficient idle blocks for MTN Path IMP.
  • the pseudoEthernet packet length may be chosen such that an integer number of pseudo-Ethernet packets appear between each MTN POH block location. For example, a fixed number of pseudo-Ethernet packets may occupy the 16383 block positions between MTN path overhead positions.
  • the circuity 135 of the source node 105 that maps the rate adapted 64B/66B -encoded client thread signal into the defined thread channel within the plurality of pseudo-Ethernet packets comprises circuitry to map the rate adapted 64B/66B -encoded client thread signal from a single client, 64-bits at a time, into the thread channel members of the defined thread channel within the plurality of pseudo-Ethernet packets.
  • the bits of the rate adapted 64B/66B encoded client thread signal are mapped 64-bits at a time into the data blocks (ZD/) blocks of the MTN path pseudo-Ethernet packets such that an individual MTN path pseudo- Ethernet packet data blocks carries information from a single client.
  • FIG. 3A In this specific example, two data blocks per pseudo-Ethernet packet are dedicated to a specific 10 Mbit/s thread channel member.
  • the thread channel of a packet client may be allocated one or more thread channel members.
  • FIG. 3B the packet structure of FIG.
  • FIG. 3 A allows 17 pseudo-Ethernet packets and 29 idles per MTN path frame row and sufficient bandwidth to carry 480 64B/66B block- coded 10 Mbit/s sublG packet-oriented client streams.
  • FIG. 3 A also illustrates the potential use of the data bytes within the /T/ termination block for carrying overhead information, such as a multiplex structure indication (MSI).
  • MSI multiplex structure indication
  • the data bytes of the /S/ start block are similarly available if needed.
  • the circuitry 135 of the source node 105 that maps the rate adapted 64B/66B -encoded client thread signal into the defined thread channel within a plurality of pseudo-Ethernet packets of the MTN path to generate the MTN path signal comprises circuitry to map the rate adapted 64B/66B-encoded client thread signal from a single client into the at least one thread channel member of the data payload area of the plurality of pseudo-Ethernet packets of the MTN path.
  • the payload bits of the set of 64B/66B data blocks within an MTN path pseudo-Ethernet packet can be regarded as a single combined payload area rather than assigning individual 64B/66B data blocks to individual thread channel members.
  • the merged payload area is divided into chunks of 66 contiguous bits, where each chunk is assigned to a 66 bit wide thread channel member.
  • Each thread channel member accommodates an entire 64B/66B block of a rate adapted 64B/66B encoded client thread signal.
  • mapping retains 66-bit block alignment, which removes the need for recovering the 64B/66B block alignment of the rate adapted 64B/66B encoded client thread signal when it is extracted from the pseudo-Ethernet packets of the MTN path.
  • FIG. 4A An example pseudo-Ethernet packet for 66-bit mapping into the merged payload area is illustrated in FIG. 4A.
  • a 398-block pseudo-Ethernet packet carries 384 of the 480 thread channel members, where each thread channel member is 66 bits wide.
  • the pseudo-Ethernet packet in FIG. 4A is the first one in the sequence of five pseudo- Ethernet packets before the first thread channel member is once again located at the start of the pseudo-Ethemet packet.
  • FIG. 4B illustrates how the pseudo-Ethernet packet of FIG. 4A may map into an MTN path frame structure using 41 x 398-block pseudo- Ethemet packets and 65 idles per MTN path frame row.
  • a packet number alignment count (packet multiframe alignment) may be provided, as indicated in FIG. 4A.
  • the packet number alignment count could be located in bits of either the /S/, /T/ or a /D/ block.
  • FIG. 5 Other potential packet length and frame structures are illustrated in FIG. 5, FIG. 6, FIG. 7, FIG. 8 and FIG. 9.
  • the pseudo-Ethernet packets would have the same basic format as in FIG. 5.
  • FIG. 5 An example pseudo-Ethernet packet for 66-bit mapping of thread channel members into the merged payload area is illustrated in FIG. 5.
  • a 264-block pseudo- Ethemet packet carries 64B/66B-encoded blocks from 254 clients.
  • the pseudo-Ethernet packet in FIG. 5 is the first one in the sequence of 240 pseudo-Ethernet packets before the first (#1) thread channel member is once again located at the start of the pseudo- Ethemet packet. Since the 240-packet repetition period does not align to the MTN path frame, bits available for a packet number alignment count (packet multiframe alignment) may be provided, as indicated in FIG. 5. The bits available for the packet number alignment count could be located in bits of either the /S/, /T/ or a /D/ block.
  • FIG. 6 illustrates a structure with 62 pseudo-Ethernet packets, each 264 blocks long, carrying 64B/66B-encoded blocks from 254 clients as illustrated in FIG. 5.
  • This structure may represent the shortest achievable pseudo-Ethernet packet length, when the number of pseudo-Ethernet packets per MTN path frame row is an integer.
  • the repetition period before the thread channel member alignment within the pseudo-Ethernet packets repeat is 240 packets.
  • a packet number alignment field may be provided.
  • 254*(66/64) 261.9375
  • the last pseudo-Ethernet packet data block will have 4 bits that are not occupied with client information. As indicated in FIG. 5, these bits could potentially be used in combination with bits from the ZS/ or /T/ to form the required 7 -bit packet number alignment field.
  • FIG. 8 Similar to the structure of FIG. 7, the example of FIG. 8 also provides an equal integer number of occurrences in each of the 480 thread channel members per MTN path frame row, and therefore a packet alignment number field may not be required. With this structure, similar to FIG. 4A, there may be no unused data block bits in the pseudo-
  • Ethernet packet Another example packet and frame structure is shown in FIG. 9.
  • the repetition period before the thread channel member alignment within the pseudo-Ethernet packets repeats is a convenient integer number of MTN path frame rows. In this example, the period is eight rows, which corresponds to a pair of MTN path frames. If the pseudoEthernet packet beginning with data from the first thread channel member immediately follows the “B” overhead block at the beginning of the MTN path frame then only a single alignment indicator bit may be required, since this would occur in every other frame. Similar to FIG. 5, the pseudo-Ethernet packet may have bits available at the end of the last data block for the alignment bit.
  • the unused MTN path data field bits in the last data block could be located in the first data block of the pseudo-Ethernet packet with the client words shifted accordingly.
  • Other examples for which the repetition period is exactly two MTN path frames are: using 20 x 816-block pseudo-Ethernet packets per row, each carrying 789 client thread words; and 15 x 1087- block pseudo-Ethernet packets, each carrying 1052 client thread words.
  • FIG. 10 illustrates a flow diagram 1000 for an example of the method for performing rate adaptation of packet-oriented client data for transmission over a Metro Transport Network (MTN).
  • the method 1000 may be performed by a source node 105, as illustrated in FIG. 1.
  • the method 1000 begins at operation 1005 by receiving a sublG packet- oriented client signal at a source node, wherein the sublG packet-oriented client signal comprises a plurality of client packets and an inter-packet gap (IPG) between respective ones of the plurality of client packets.
  • the sublG packet-oriented client signal may be a 1000 Mbit/s Ethernet (1000BASE-x/ GbE) stream employing 8B/10B code blocks.
  • the 8B/10B code blocks of the sublG packet-oriented client stream could be transcoded directly into 64B/66B code blocks in order to preserve the control code information, including ordered sets, of the 8B/10B stream.
  • the method 1000 continues at operation 1010 by forming a 64B/66B-encoded client signal by encoding individual client packets of the plurality of client packets into a set of 64B/66B -encoded blocks and filling the IPG between respective ones of the plurality of client packets with a set of 64B/66B idle blocks.
  • the method 1000 continues by generating a 64B/66B-encoded client thread signal by inserting thread operations, administration and maintenance (ThOAM) overhead for the sublG packet-oriented client signal into the 64B/66B -encoded client signal.
  • ThOAM thread operations, administration and maintenance
  • the ThOAM is inserted as a MTN ordered set (OS) into the 64B/66B -encoded client signal.
  • the method 1000 continues at operation 1020 by generating a rate adapted 64B/66B- encoded client thread signal by performing an idle mapping procedure (IMP) to modify a number of 64B/66B idle blocks in one or more of the sets of 64B/66B idle blocks of the
  • IMP idle mapping procedure
  • a plurality of sublG packet- oriented client signals may be received at the source node and operation 1020 includes generating a respective rate adapted 64B/66B -encoded client thread signal for respective ones of the plurality of sublG packet-oriented client signals.
  • operation 1015 and operation 1020 may be performed in either order.
  • the method 1000 continues at operation 1025 by generating an MTN path signal by defining a plurality of pseudo-Ethernet packets in the MTN path, defining a thread channel within the plurality of pseudo-Ethernet packets for carrying the sublG packet- oriented client signal and mapping the rate adapted 64B/66B-encoded client thread signal into the defined thread channel within the plurality of pseudo-Ethernet packets.
  • operation 1025 includes defining a respective thread channel within the plurality of pseudo-Ethernet packet for carrying a respective one of the sublG packet-oriented client signals and mapping the respective rate adapted 64B/66B-encoded client thread signal into the respective defined thread channel within the plurality of pseudo-Ethernet packets.
  • respective ones of the plurality of pseudo-Ethernet packets in the MTN path comprise a plurality of data bytes forming a payload area and wherein generating the MTN path signal comprises segmenting the payload area into a plurality of thread channel members, defining the thread channel within the plurality of pseudo-Ethernet packets by assigning one or more of the plurality of thread channel members to the defined thread channel and mapping the rate adapted 64B/66B -encoded client thread signal into the one or more of the plurality of thead channel members assigned to the defined thread channel within the plurality of pseudo-Ethemet packets.
  • operation 1025 includes mapping the rate adapted 64B/66B -encoded client thread signal from a single sub 1G packet-oriented client signal into one or more of the plurality of thread channel members assigned to the defined thread channel within the plurality of pseudo-Ethernet packets.
  • operation 1025 includes mapping the respective rate adapted 64B/66B-encoded client thread signal from the plurality of sublG client signals into one or more of the plurality of thread channel members assigned to the the respective defined thread channel within the plurality of pseudo-Ethernet packets.
  • the method concludes at operation 1030 by transmitting the MTN path signal from the source node over the MTN path.
  • FIG. 11A illustrates a flow diagram 1100 of a method for performing rate adaptation of the MTN path signal generated at a source node 105 by a sub 1 G-aware intermediate node.
  • the method 1100 may be performed by a sub 1 G-aware intermediate node 115, as illustrated in FIG. 1.
  • the method 1100 begins at operation 1105 by receiving the MTN path signal at an ingress of the sub 1 G-aware intermediate node. [0069] At operation 1110, the method 1100 continues by extracting the rate adapted 64B/66B- encoded client thread signal from the plurality of pseudo-Ethernet packets of the MTN path signal.
  • the method 1100 continues by generating a modified rate adapted 64B/66B -encoded client thread signal by performing IMP rate adaptation of the extracted rate adapted 64B/66B-encoded client thread signal to modify the number of 64B/66B idle blocks in one or more sets of the 64B/66B idle blocks to match an egress thread channel rate of the sublG-aware intermediate node.
  • the method 1100 continues by generating an egress MTN path signal by defining a plurality of pseudo-Ethernet packets in the MTN path at an egress of the sublG-aware intermediate node, defining an egress thread channel within the plurality of pseudo-Ethernet packets to carry the sublG packet-oriented client signal and mapping the modified rate adapted 64B/66B -encoded client thread signal into the defined egress thread channel within a plurality of pseudo-Ethernet packets.
  • the method 1100 concludes at operation 1125 by transmitting the egress MTN path signal from the sublG-aware intermediate node to a next node of the MTN.
  • the next node of the MTN may be another sublG-aware intermediate node or a sink node.
  • FIG. 1 IB illustrate a flow diagram 1200 of a method for recovering the packet-oriented client data from the egress MTN path signal received at a sink node.
  • the method 1200 may be performed by a sink node 110, as illustrated in FIG. 1.
  • the method 1200 begins at operation 1205 by receiving the egress MTN path signal at the sink node.
  • the method 1200 continues at operation 1210 by extracting the sets of 64B/66B -encoded client blocks, the sets of 64B/66B idle blocks and the ThOAM from the modified rate adapted 64B/66B encoded client thread signal.
  • the method 1200 concludes at operation 1215 by decoding respective sets of extracted 64B/66B -encoded client blocks to recover the sub 1G packet-oriented client signal.
  • the various exemplary systems and methods described above provide for carrying sublG packet-oriented client streams over an MTN path.
  • the sublG packet-oriented client streams are rate adapted into an MTN thread channel rate using IMP, and thread 0AM is added to the stream.
  • the client stream, the thread 0AM and idles added to the stream are invisible to the MTN path so that they do not impact MTN path processing.
  • portions of the system of the present examples may be implemented in a Field Programmable Gate Array (FPGA) or Application Specific Integrated Circuit (ASIC).
  • FPGA Field Programmable Gate Array
  • ASIC Application Specific Integrated Circuit
  • various functions of circuit elements may also be implemented as processing steps in a software program.
  • Such software may be employed in, for example, a digital signal processor, a network processor, a microcontroller or general-purpose computer.

Abstract

Système et procédé pour effectuer une adaptation de débit de signaux clients orientés paquets sous-1G pour une transmission sur un réseau de transport métro (MTN) par formation d'un signal client codé 64B/66B à partir de paquets clients individuels du signal client orienté paquets sous-1G et des blocs inactifs dans un intervalle inter-paquets (IPG), par insertion de frais d'opérations, d'administration et de maintenance de fil (ThOAM) pour générer un signal de fil client codé 64B/66B, par réalisation d'une procédure de mappage inactif (IMP) pour générer un signal de fil client codé 64B/66B à adaptation de débit, par définition d'une pluralité de pseudo-paquets Ethernet dans un trajet MTN, par définition d'un canal de fil dans la pluralité de pseudo-paquets Ethernet et mappage du signal de fil client codé 64B/66B à adaptation de débit dans le canal de fil défini à l'intérieur de la pluralité de pseudo-paquets Ethernet pour générer un signal de trajet MTN pour une transmission à un nœud intermédiaire ou à un nœud collecteur.
PCT/US2023/014355 2022-04-04 2023-03-02 Système et procédé d'adaptation de débit de données client orientées paquets pour une transmission sur un réseau de transport métro (mtn) WO2023196068A1 (fr)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
US202263326989P 2022-04-04 2022-04-04
US63/326,989 2022-04-04
US18/116,293 US20230318934A1 (en) 2022-04-04 2023-03-01 System and method for rate adaptation of packet-oriented client data for transmission over a metro transport network (mtn)
US18/116,293 2023-03-01

Publications (1)

Publication Number Publication Date
WO2023196068A1 true WO2023196068A1 (fr) 2023-10-12

Family

ID=85772063

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2023/014355 WO2023196068A1 (fr) 2022-04-04 2023-03-02 Système et procédé d'adaptation de débit de données client orientées paquets pour une transmission sur un réseau de transport métro (mtn)

Country Status (1)

Country Link
WO (1) WO2023196068A1 (fr)

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
"Interfaces for the metro transport network;g8312", vol. 11/15, 25 November 2020 (2020-11-25), pages 1 - 21, XP044302831, Retrieved from the Internet <URL:https://www.itu.int/ifa/t/2017/sg15/exchange/wp3/q11/G.8312/g8312-lcCommentResolutions-v3.docx> [retrieved on 20201125] *
STEVE TROWBRIDGE NOKIA USA: "Sample common sub-1G TDM multiplexing and switching mechanism for use over MTN and OTN networks;C2812", vol. 11/15, 23 November 2021 (2021-11-23), pages 1 - 7, XP044322271, Retrieved from the Internet <URL:https://www-api.itu.int/ifa/t/2017/sg15/docs/c/ties/T17-SG15-C-2812!!MSW-E.docx> [retrieved on 20211123] *

Similar Documents

Publication Publication Date Title
EP3787208B1 (fr) Procédé de transmission de données et systéme de communication
CN108809901B (zh) 一种业务承载的方法、设备和系统
JP7026802B2 (ja) データ伝送方法、通信機器、および記憶媒体
US20230254389A1 (en) Method and apparatus for adapting, at a sink node, a constant bit rate client signal into the path layer of a telecom signal
EP3627736B1 (fr) Procédé de transmission de signal de service à l&#39;aide d&#39;un canal ethernet et dispositif de communications
EP2975858B1 (fr) Procédé permettant de traiter des données dans l&#39;ethernet, puce de couche physique et dispositif ethernet
US8199772B2 (en) Systems and methods for synchronous generic framing protocol mapping
US20110013690A1 (en) Signal Block Sequence Processing Method And Signal Block Sequence Processing Apparatus
WO2008092389A1 (fr) Architecture de données compatible multi-composant
CN105790883B (zh) 一种处理信号的方法及通信设备
EP2430804A1 (fr) Codage transitoire de transport de service universel
WO2021219079A1 (fr) Procédés de traitement, d&#39;échange et d&#39;extraction de données de service, dispositifs et support lisible par ordinateur
US11916662B2 (en) System and method for performing rate adaptation of constant bit rate (CBR) client data with a fixed number of idle blocks for transmission over a metro transport network (MTN)
US20230299880A1 (en) Code block identification method and apparatus
US20230318934A1 (en) System and method for rate adaptation of packet-oriented client data for transmission over a metro transport network (mtn)
US20040170166A1 (en) Compression methods for packetized sonet/sdh payloads
WO2023196068A1 (fr) Système et procédé d&#39;adaptation de débit de données client orientées paquets pour une transmission sur un réseau de transport métro (mtn)
US20130021899A1 (en) M-pair mode protection switching
CN115811388A (zh) 一种通信方法、相关装置以及存储介质
US11838111B2 (en) System and method for performing rate adaptation of constant bit rate (CBR) client data with a variable number of idle blocks for transmission over a metro transport network (MTN)
US20230006938A1 (en) System and method for performing rate adaptation and multiplexing of constant bit rate (cbr) client data for transmission over a metro transport network (mtn)
CN117203916A (zh) 用于对具有固定数量空闲块的恒定比特率（cbr）客户端数据执行速率适配以供通过城域传送网络（mtn）传输的系统和方法
CN117413472A (zh) 用于对具有可变数量空闲块的恒定比特率（cbr）客户端数据执行速率适配以供通过城域传送网络（mtn）传输的系统和方法
CN117441301A (zh) 用于对恒定比特率（cbr）客户端数据执行速率适配和复用以供通过城域传送网络（mtn）传输的系统和方法
WO2024032191A1 (fr) Procédé et dispositif de traitement de bloc de code de défaut

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

Country of ref document: EP

Kind code of ref document: A1