WO2020107298A1 - Dispositif et procédé de codage transitoire de transport de service universel - Google Patents

Dispositif et procédé de codage transitoire de transport de service universel Download PDF

Info

Publication number
WO2020107298A1
WO2020107298A1 PCT/CN2018/118034 CN2018118034W WO2020107298A1 WO 2020107298 A1 WO2020107298 A1 WO 2020107298A1 CN 2018118034 W CN2018118034 W CN 2018118034W WO 2020107298 A1 WO2020107298 A1 WO 2020107298A1
Authority
WO
WIPO (PCT)
Prior art keywords
service
flow
ustm
state
services
Prior art date
Application number
PCT/CN2018/118034
Other languages
English (en)
Chinese (zh)
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 PCT/CN2018/118034 priority Critical patent/WO2020107298A1/fr
Publication of WO2020107298A1 publication Critical patent/WO2020107298A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/64—Hybrid switching systems

Definitions

  • Ethernet has become the preferred protocol for many networks because of its flexibility, decentralization, and scalability.
  • Ethernet includes a series of frame-based computer networking technologies for local area networks (LANs) and addresses the common addressing format and media access control at the physical layer and data link layer of the Open System Interconnection (OSI) networking model (MAC) defines numerous wiring and signaling standards.
  • OSI Open System Interconnection
  • MAC Open System Interconnection
  • Synchronous Optical Networking SONET
  • SDH Synchronous Digital Hierarchy
  • SONET/SDH is a standardized multiplexing protocol that transmits multiple digital bit streams via optical fibers or electrical interfaces. Due to the neutrality and transmission-oriented characteristics of the SONET/SDH protocol, SONET/SDH is used to transmit substantially large numbers of telephone calls and data services via the same optical fiber or wire without synchronization issues.
  • the SONET/SDH network transmission standard is based on time division multiplexing (TDM).
  • TDM is a technology in which two or more signals or bit streams are transmitted simultaneously on the surface as sub-channels in a communication channel, but physically transmitted in turn on the channel. This is achieved by dividing the time domain into, for example, multiple recurring time slots with approximately the same length, where each sub-channel uses one time slot. Thus, for each sub-channel, one TDM frame corresponds to one time slot.
  • the present invention includes an apparatus for transmitting universal service transmission transformation codes, the apparatus including an apparatus including a switching structure coupled to a plurality of interfaces and configured to Multiple Universal Service Transmission (UST) Multiplexing (USTM) data streams are exchanged between them, wherein the USTM data stream includes packet-switched services, circuit-switched services, and instructions between the packet-switched services and the circuit-switched services Transition signaling for state changes, where the transition signaling does not indicate the status of each octet of the USTM data stream.
  • UST Multiple Universal Service Transmission
  • M Multiplexing
  • the invention includes a network component that includes at least one processor coupled to a memory and configured to: receive data corresponding to a flow; use a flow graph to Identify the flow; determine whether the flow state has changed; if the flow state has changed, send transition signaling indicating the state of the flow on the USTM data flow; and send the data on the USTM data flow.
  • a network component that includes at least one processor coupled to a memory and configured to: receive data corresponding to a flow; use a flow graph to Identify the flow; determine whether the flow state has changed; if the flow state has changed, send transition signaling indicating the state of the flow on the USTM data flow; and send the data on the USTM data flow.
  • the present invention includes a method for transmitting universal service transmission transformation codes, the method comprising: receiving a USTM data stream including TDM services and Ethernet services; Multiple timeslots of Ethernet services are demultiplexed; multiple operation codes are obtained from the transition information in the timeslots; the operation codes are used to separate the TDM service and the Ethernet service; and The TDM service is exchanged in a switch and the Ethernet service is exchanged in a second switch.
  • Figure 1 is a schematic diagram of multiple different business types.
  • FIG. 2A is a schematic diagram of an embodiment of a universal service transmission multiplexing/demultiplexing architecture.
  • Figure 2B is a schematic diagram of an embodiment of a transmitted service.
  • Figure 3 is a schematic diagram of an embodiment of an UST switching device.
  • FIG. 4 is a schematic diagram of an embodiment of a multi-part opcode signaling unit (SU).
  • 5A is a schematic diagram of an embodiment of an encoding block.
  • 5B is a schematic diagram of another embodiment of an encoding block.
  • Fig. 6 is a schematic diagram of an embodiment of a coding SU.
  • FIG. 7 is a schematic diagram of another embodiment of the encoding SU.
  • Figure 8 is a diagram of an embodiment of multiple control symbols.
  • FIG. 9 is a schematic diagram of an embodiment of a flow diagram.
  • FIG. 10 is a flowchart of an embodiment of the UST signaling method.
  • FIG. 11 is a schematic diagram of an embodiment of a general-purpose computer system
  • UST is a centralized transmission and switching technology.
  • the UST scheme can be used to map packet-switched (or connectionless) services and/or circuit-switched (or connection-oriented) services into a single stream, which can be transmitted on a link.
  • UST technology can provide centralized packet switching and circuit switching service transmission on a single link, and supports both packet switching and circuit switching, end-to-end network clock synchronization capability, and within existing protocols that can support circuit switching service emulation Built to work with each other.
  • the UST may be compatible with existing SDH/SONET networks and deployed as part of current or emerging packet-based networks, such as Ethernet-based networks.
  • the system and method include multiple UST conversion coding schemes that can be used to support UST, for example for SDH/SONET networks and/or Ethernet-based networks.
  • the UST transition coding scheme can be used to improve, for example, the mapping of TDM services and/or Ethernet services in the UST transmission link based on the USTM protocol by adding service transition information without adding substantial overhead to the transmission link/stream.
  • TDM services and Ethernet services can be multiplexed into multiple time slots and transmitted on the link.
  • the TDM service and Ethernet service can be demultiplexed from the transmitted USTM stream.
  • the UST transition coding scheme can provide improved UST signaling in the USTM service, for example, to indicate the transition of different TDM services and/or Ethernet services in the USTM stream without using substantial link bandwidth, and thus can reduce the chain Road utilization or capacity.
  • multiple operation codes can be used in the USTM stream to provide different UST signaling indications, for example, to indicate transitions between different services in the stream.
  • FIG. 1 illustrates one embodiment of multiple different service types 100 that can be multiplexed and transmitted using UST.
  • Different service types 100 may include TDM service 102 and Ethernet service 104.
  • the TDM service 102 may correspond to a SONET/SDH network
  • the Ethernet service 104 may correspond to an Ethernet-based network.
  • a portion of the TDM service 102 and the Ethernet service 104 may correspond to the connection-oriented service 106.
  • connection-oriented services 106 can be transmitted in a network via multiple configured or calculated paths, for example, using multiple network switches.
  • Another part of the Ethernet service 104 may correspond to the connectionless service 108.
  • connectionless services 108 can be transmitted between network nodes, for example using network bridges, based on the destination address (DA), source address (SA), or both in the service.
  • DA destination address
  • SA source address
  • connectionless traffic 108 can be forwarded hop-by-hop with minimal processing at each node.
  • the connectionless service 108 may have a lower priority than the connection-oriented service 106.
  • the UST scheme can be used to provide transmission, exchange, and synchronization of different service types 100.
  • a switch may implement the USTM protocol to transfer different traffic types 100 from the source node to the destination node.
  • the switch can also exchange different service types 100 between multiple source nodes and multiple destination nodes and synchronize their transmission. Therefore, the switch can receive different service types 100 from the source node and multiplex them.
  • the received services may include the TDM service 102 and/or the Ethernet service 104.
  • the TDM service 102 and/or the Ethernet service 104 may be multiplexed into a TDM service 110, a high-performance streaming (HPF) service 112, and a best effort package ( BEP) business 114 or a combination thereof.
  • HPF high-performance streaming
  • BEP best effort package
  • the TDM service 110, HPF service 112, and/or BEP service 114 may then be transmitted to the second switch using its TDM scheme, for example via a link/stream, in its original format (or mode) without further encapsulation or encapsulation.
  • the second switch may then demultiplex the service into the originally sent TDM service 102 and/or Ethernet service 104 using, for example, the USTM protocol, and send the TDM service 102 and/or Ethernet service 104 to its corresponding destination Ground node.
  • the TDM service 110 and the HPF service 112 may correspond to the connection-oriented service 106, and may have a higher priority than the BEP service 114 that may correspond to the connectionless service 108.
  • connection-oriented services 106 and connectionless services 108 can be multiplexed and transmitted from the source node to the destination node in a single link/stream.
  • the UST scheme can provide quality of service (QoS) for high-priority connection-based services, traditional network compatibility (for example, for SONET/SDH and Ethernet systems), and substantial high-quality network clock distribution and Synchronize.
  • QoS quality of service
  • FIG. 2A illustrates an embodiment of the UST multiplexing/demultiplexing architecture 200.
  • the UST multiplexing/demultiplexing architecture 200 may be used to transmit and/or exchange different service types 100.
  • the UST multiplexing/demultiplexing architecture 200 may be based on the USTM protocol and implemented in, for example, a switch located between a source (or incoming) node and a destination (or outgoing) node.
  • the UST multiplexing/demultiplexing architecture 200 can be used to transmit services for various networks/technologies such as Ethernet, SONET/SDH, optical fiber transmission network (OTN), or other networks.
  • the UST multiplexing/demultiplexing architecture 200 can provide transmission, switching and clock synchronization for different networks/technology in a seamless manner.
  • the UST multiplexing/demultiplexing architecture 200 can also provide frequency, absolute phase, and absolute time transmission and synchronization for different networks/technology.
  • the switch may receive TDM service 202 and/or Ethernet service 204 from the source node.
  • the Ethernet service 204 can be demultiplexed (for example, using a demultiplexer (Demux)/Routing Agent (RA)) into a high priority packet (HPP) service 205 and a low priority packet (LPP) service 206.
  • the HPP service 205 may include a connection-oriented service, and may be converted into an HPF service 207 (for example, using an HPF adapter).
  • the LPP service 206 can include connectionless services and optionally connection-oriented services, and can be converted into a combined packet flow (CPF) service 208 (eg, using a CPF adapter).
  • CPF packet flow
  • the CPF service 208 can be demultiplexed (eg, using Demux) to obtain a first part that can include any connection-oriented service with relatively high priority and a second part that can include connectionless service with relatively low priority .
  • the first part of the CPF service 208 may be multiplexed together with the HPF service 207, and the second part of the CPF service corresponds to the BEP service.
  • the HPF service 207 (containing the first part of the CPF service 208, if any) and the TDM service 202 can be multiplexed (eg, using a multiplexer (Mux)) to the USTM service 210, and therefore via Single link/streaming.
  • the BEP service may also be multiplexed in the USTM service 210 along with the TDM service 202 and HPF service 207 based on available bandwidth.
  • the USTM service 210 can be processed in the opposite way to obtain the original TDM service 202 and the Ethernet service 204.
  • the USTM service 210 may first be demultiplexed (for example, using Demux) to return to the TDM service 202, HPF service 207, and BEP service. This can be done by multiplexing the first part of the CPF service 208 in the HPF service 207 (if any) (eg, using Mux) and multiplexing the second part of the CPF service 208 in the BEP service ( For example, Mux is used to obtain the original CPF service 208.
  • the HPF service 207 and the CPF service 208 can then be converted back to the HPP service 205 and the LPP service 206, respectively.
  • the HPP service 205 and the LPP service 206 can then be multiplexed to obtain the original Ethernet service 204 (for example, using Mux/ RA).
  • the TDM service 202 and the HPF service 207 can be transmitted by mapping this service to multiple provided time slots within a periodic time window that can be equal to approximately 125 microseconds ( ⁇ s), for example .
  • the TDM service 202 and the HPF service 207 may have a relatively high priority and/or be allocated with guaranteed transmission bandwidth.
  • the periodic time window may include a plurality of separate reserved time slots that may be allocated to the TDM service 202 and the HPF service 207.
  • the TDM service 202 can be mapped into the corresponding time slot in the original format.
  • the TDM service 202 may not support dynamic bandwidth reuse or allocation like the HPF service 207.
  • the TDM service 202 may not be redistributed into additional or different time slots in the periodic window that are different from the originally assigned time slots of the TDM service 202.
  • the TDM service 202 may be rate-adapted to the HPF service 207 and/or the TDM service 202 may be mapped to the HPF service 207.
  • the TDM service 202 and the HPF service 207 can be mapped to the same amount of time slots and/or the same time slots in the periodic window.
  • the TDM service 202 can support dynamic bandwidth reuse.
  • the HPF service 207 and similarly the TDM service 202 can support dynamic rate adaptation.
  • lower priority BEP traffic may be mapped into any remaining time slots, which may correspond to the remaining or available transmission bandwidth after the TDM service 202 and the HPF service 207 are allocated.
  • the remaining time slots may include unassigned time slots (indicated by blank boxes), where TDM service 202 and HPF service 207 are not transmitted and/or allocated bandwidth.
  • the remaining time slots may also include idle HPF service time slots (indicated by diagonal boxes), where HPF service transmission is idle.
  • BEP traffic can be mapped to the remaining time slots in the periodic window dynamically or byte by byte.
  • BEP service transmission can be interrupted to transmit other higher priority packets, such as HPF service 207 and/or TDM service 202, by reallocating certain time slots of the BEP service to higher priority services.
  • the BEP service can support dynamic rate adaptation.
  • the TDM service 202, HPF allocated to the time slot in the periodic window may be transmitted in any combination and via any number of links/flows between the ingress node and the egress node, for example, in the switch fabric Business 207 and BEP business.
  • the three types of traffic can be transmitted via three separate buses within their allocated time slots in the periodic window.
  • the TDM service 202 and the HPF service 207 may be transmitted via the first bus in their allocated time slots
  • the BEP service may be transmitted via the second bus in their allocated time slots.
  • the USTM service 210 may also include a UST transition code to indicate different transitions between different services in the USTM service 210.
  • the UST transition code may provide UST signaling, which may indicate the start and/or end of different service flows in the USTM service 210, such as TDM service, HPF service, and/or BEP service.
  • UST conversion coding can improve the transmission, exchange and/or synchronization of different service types in the transport stream.
  • UST transcoding can be used to indicate different types of services in a transport stream without using the substantial bandwidth of the transport stream, for example, without using a substantial number of time slots in a periodic time window Shift between. Therefore, multiple UST conversion coding schemes can be used to provide improved UST signaling in the USTM service and improve link utilization or capacity.
  • UST signaling can be embedded in the UST service to provide the control information for the multiplexed HPF and BEP services in the transport stream.
  • UST signaling may provide functionality similar to that provided by the Ethernet physical layer, for example to indicate or identify packet boundaries.
  • UST transition codes can be provided in the transport stream to indicate or signal different traffic types and/or transitions between streams in the stream, and therefore track the activity or idleness of each of the streams status.
  • the logical flow in the transmitted service may correspond to a continuous example of logical HPF virtual connection or BEP service. Indicating a transition between service types and/or flows instead of signaling more detailed information about different service activities may reduce the amount of control information that may be exchanged, and thus reduce the additional overhead on the link.
  • the circuit switched or connection-oriented service such as the TDM service
  • the circuit switched or connection-oriented service can be frequency or Rate adaptation.
  • TDM control information such as operation, management and maintenance (OAM) information
  • OAM operation, management and maintenance
  • the received TDM traffic may be allocated additional time slots in a periodic time window to add UST transition codes, and thus signal the control information.
  • FIG. 3 illustrates an embodiment of the UST switching device 300, which can provide transmission, switching, and synchronization for different service types such as TDM, HPF, and/or BEP services.
  • the UST switching device may include a switching structure 310 that is coupled to a plurality of first Ethernet links 320 via a tributary interface 330 and is coupled to a plurality of second Ethernet links 340 via a line interface 350.
  • the first Ethernet link 320 may be coupled to a plurality of first nodes (not shown), and the second Ethernet link 340 may be coupled to a plurality of second nodes (not shown).
  • the first node and the second node may be located in the same network such as Ethernet or in different networks.
  • services can pass from any one of the first nodes through the first Ethernet link 320, the tributary interface 330, the switch fabric 310, the line interface 350, and the subsequent second Ethernet link 340. Transmission to any of the second nodes. Additionally or alternatively, traffic may be transmitted from the second node to the first node via the second Ethernet link 340, the line interface 350, the switch fabric 310, the branch interface 330, and the subsequent first Ethernet link 320.
  • the tributary interface 330 may be configured to receive and/or forward different service types via the first link 320, for example, in the original form or format of the service.
  • the tributary interface 330 may receive the USTM service and/or BEP service and/or the USTM from the switch fabric 310 via, for example, a 10G additional unit interface (XAUI), a 40G additional unit interface (XLAUI), or other interfaces such as a BEP only interface
  • XAUI 10G additional unit interface
  • XLAUI 40G additional unit interface
  • the service and/or BEP service is sent to the switch fabric 310.
  • a T6xb encoding scheme may be used to map the USTM service transmitted via XLAUI, which may be based on a 64b/66b encoding format, as described below.
  • a T10b encoding scheme may be used to map the USTM service transmitted via XAUI, which may be based on the 8b/10b encoding format, as shown below.
  • the tributary interface 330 may also include a flow graph 332, a flow state table 334, and a time slot (TS) state table 330, which may be used to track the state of the flow and time slots, as described in detail below.
  • TS time slot
  • the switching fabric 310 may be configured to receive and exchange different traffic types from any of the first link 320 and/or the second link 340, and in the second link 340 and/or the first link 320 Forwarding business on any of them.
  • the traffic may be received and forwarded via the tributary interface 330 and/or the line interface 350.
  • the first link 320 and the second link 340 may correspond to a 100 Gigabit (G) Ethernet system, a 40G Ethernet and/or a 10G Ethernet system, and the Ethernet in any of the links Services can be encoded based on different schemes or formats (eg, 64b/66b, 8b/10b, 4b/5b, T6xb, and/or T10b). In other embodiments, other arrangements may be used for switch fabric 310, tributary interface 330, line interface 350, and/or subcomponents thereof.
  • the switch fabric 310 may include a USTM demultiplexer 316, a flow switch 312 including a connection diagram 315, and a packet switch 314.
  • the USTM demultiplexer 316 may be configured to receive USTM services from the tributary interface 330 and/or line interface 350, demultiplex the services into TDM services, HPF services, and/or BEP services, and divide the The traffic is forwarded to the flow switch 312 and/or the packet switch 314.
  • the flow switch 312 may be configured to receive USTM traffic that may include TDM traffic and/or HPF traffic and exchange the traffic between the first link 320 and the second link 340.
  • the connection diagram 315 may be used to support time-based exchanges for TDM services, for example.
  • the packet switch 314 may be configured to receive BEP traffic and exchange the traffic between the first link 320 and the second link 340.
  • the USTM demultiplexer 316 may then receive the exchanged TDM service, HPF service, and/or BEP service from the flow switch 312 and/or packet switch 314, multiplex the service into the USTM service, and The USTM service is forwarded to the tributary interface 330 and/or the line interface 350.
  • the line interface 350 may be configured to receive and/or forward different service types via the second link 340, and may receive the USTM service and/or BEP service from the switch fabric 310 and/or convert the USTM service and /Or BEP service is sent to the switch fabric 310.
  • the interface 340 may carry the USTM service via various encoding schemes shown in FIG. 3.
  • the line interface 350 may include a flow graph 352, a flow state table 354, and a time slot (TS) state table 356, which may be used to track the state of the flow and time slots.
  • TS time slot
  • control symbols may be used in the USTM stream, for example for padding and/or OAM support to provide UST transition coding.
  • the control symbol may include multiple single operation codes for different control functions, which may be used in time slots in the time window.
  • Multi-part opcodes can also be used to provide additional or continuous UST signaling in time slots, for example to provide additional or more advanced control functions.
  • multiple multi-part opcodes can be used in time windows or time slots to provide additional UST signaling.
  • the operation code and the multi-part operation code may be encoded using 64b/66b encoding format.
  • Table 1 shows the UST transition signaling used for different transition types in the USTM service.
  • the UST transition signaling may correspond to the T6xb coding scheme, which is described in detail below.
  • a set of UST transition signals can be used for each of the HPF, BEP, and TDM services, for example, for each time slot, each stream, or each UST frame.
  • a single opcode can be used for each transition type to provide UST transition signaling, which can include invalidation/padding, start of UST frame, HPF activity, HPF idle, BEP activity, BEP idle, continuity check ( CC) and multipart opcode start. Invalid/padding opcodes or signals can be used in any of the slot-based HPF, BEP and TDM services.
  • the CC opcode can be used in any of the stream-based HPF, BEP, and TDM services.
  • the UST frame start opcode can be used for each UST frame. For example, multiple consecutive UST frame start control symbols can be used to implement link-level error propagation.
  • HPF active and idle opcodes can be used in flow-based HPF services.
  • BEP active and idle opcodes can be used in any of the stream-based BEP and HPF services.
  • Multi-part opcodes can be used in any of the time slot-based HPF, BEP, and TDM services, where multiple opcodes can be used to indicate the continuation of signaling information.
  • Table 1 UST transition signaling.
  • FIG. 4 illustrates an embodiment of the multi-part opcode SU400, which can be used to provide connection or additional signaling information in the USTM service.
  • the multi-part opcode SU400 may include octets transmitted in one time slot.
  • the octet may include a signaling field 410, a continuation field 420, and a parity field 430.
  • the signaling field 410 may include an operation code or a multi-part operation code, and may include approximately six bits (eg, bits 0 to 5) that may specify signaling information.
  • the splice field 420 may include approximately one bit (eg, bit 6) and may be used to indicate whether the multipart opcode SU400 includes the last multipart opcode including splice signaling information or whether there is a subsequent octet that includes more signaling information Section.
  • bit 6 may be set to about 0 to indicate that the multipart opcode SU400 includes the last multipart opcode of the signaling information, or to about 1 to indicate that the signaling information is, for example, the same or subsequent There is another multi-part opcode connection in the subsequent octet in the slot.
  • the parity field 430 may include approximately one bit (eg, bit 7), and may be used to detect errors in the transmitted data.
  • the signaling information in the multi-part opcode SU400 can be used to indicate service flow settings, flow disassembly, increased flow bandwidth, decreased flow bandwidth, and/or other service-related information.
  • multiple multipart opcodes may signal additional operations in each time slot, for example, in a periodic time window (e.g., about 125 ⁇ s time window) after the initial opcode.
  • the information in the multi-part opcode may include a stream number that indicates the same stream for all multi-part opcodes in the time slot.
  • the information in the multi-part opcode SU400 may include information about the destination of the transmitted traffic or the outgoing node, which can then be used to determine the next hop.
  • the multi-part opcodes in multiple multi-part opcode signaling blocks can be used to provide logical stream-oriented OAM operations, which can be mapped to marked BEP and/or HPF packets in the transport stream in.
  • the T6xb coding scheme can be used to multiplex TDM services, HPF services, BEP services, or a combination thereof, for example, by mapping every approximately 66 bits in the stream to approximately 64 bits using the 64b/66b coding format.
  • the 64b/66b encoding format can be used for Ethernet, for example for about 10G Ethernet, about 40G Ethernet or about 100G Ethernet systems.
  • the T6xb coding scheme can be used to signal a transition in the USTM service, for example, to maintain the status of each stream of HPF and/or BEP services, and thus track the active and idle state of each stream.
  • the encoding block 500 may include up to about eight octets corresponding to 64b/66b blocks, for example, in the USTM service.
  • the octet may include TDM, HPF and/or BEP services without transition signals or information.
  • the encoding block 500 may be preceded by a synchronization value indicating that there is no transition information in the encoding block 500 (eg, in the transport stream).
  • the synchronization value may be set to about one or "01" to indicate that no transition signaling is provided in the subsequent encoding block 500.
  • at least one octet (eg, octet 1) in the encoding block 500 may include transition signaling, as shown in FIG.
  • the encoding block 500 may be preceded by a synchronization value indicating that there is transition information in the encoding block 500 (eg, about 10).
  • a synchronization value indicating that there is transition information in the encoding block 500 (eg, about 10).
  • transition information may be located in front of the encoding block 500, for example, in the first octet of the encoding block 500, as described below.
  • the encoding block 500 may include at least a first octet (for example, from bit 0 to bit 7), the first octet includes an opcode field 510, a position field 512, a connection field 520 ⁇ parity field 530 ⁇
  • the opcode field 510 may include about three bits (for example, bits 0 to 2), and may indicate a transition signal, for example, as shown in Table 1 or Table 2 below.
  • the location field 512 may include approximately three bits (eg, from bit 3 to bit 5), and may indicate the location of the transition in the traffic. For example, the three bits can indicate the location of the service transition in the 64b/66b block with bytes.
  • the three bits may indicate an integer value from about zero bytes to about seven bytes.
  • the continuation field 520 may include approximately one bit (eg, bit 6), which may be used to indicate whether the transition signaling octet is the last one in the encoding block 500.
  • bit 6 may be set to about 0 to indicate that the next octet in the 64b/66b block includes TDM, HPF, and/or BEP traffic without transitions, or set to about 1 to indicate
  • the next octet includes additional signaling information.
  • the next octet in encoding block 500 may correspond to multi-part opcode signaling block 500.
  • the parity field 530 may include approximately one bit (eg, bit 7), and may be used to detect errors in the transmitted data.
  • Table 2 shows another UST transition signaling based on the T6xb coding scheme.
  • the opcode field 510 may be used in the encoding block 500 to provide UST transition signaling.
  • the opcode field 510 may be used to indicate a set of UST transition signals, which may include idle state, UST frame start, HPF packet start, HPF packet end, BEP packet start, BEP packet end, CC, and multipart opcode start.
  • the idle state can be indicated by an opcode value of about 0, and can be used in any of the slot-based HPF, BEP, and TDM services.
  • the start of the UST frame can be indicated by an opcode value of about 1, and can be used for each UST frame.
  • the start and end of an HPF frame can be indicated by opcode values of about 2 and about 3, respectively, and can be used in stream-based HPF services.
  • the BEP frame start and frame end can be indicated by opcode values of about 4 and about 5, respectively, and can be used in any of the stream-based BEP and HPF services.
  • the CC can be indicated by an opcode value of about 6, and can be used in any of flow-based HPF, BEP, and TDM services.
  • the multipart start can be indicated by an opcode value of about 7, and can be used in any of the slot-based HPF, BEP, and TDM services.
  • Table 2 UST transition signaling using T6xb encoding.
  • At least one octet in the 64b/66b block may include signaling information to replace the actual traffic transmitted.
  • the actual traffic can be offset by the number of bytes corresponding to the number of octets used for signaling. Therefore, the octets that include TDM, HPF, and/or BEP services after the signaling octet in the 64b/66b block can be offset by at least about one byte, and by up to about seven words Section.
  • the corresponding octet can be restored to its corresponding position (eg, relative to the transmission time window) before further processing.
  • the originally transmitted traffic can be shifted by up to about seven octets, and is located within a single 64b/66b block.
  • a relatively small amount of buffering may be required to realign the flow at the destination node. For example, a buffer size of approximately 8 octets may be sufficient, which does not add substantial latency or delay in the data stream.
  • FIG. 6 illustrates an embodiment of a coded SU600, which can be used to transmit USTM services or provide transition signaling.
  • the encoding SU600 may correspond to the T9b encoding format, which may include approximately eight bits and one additional signaling bit later, and may be used in a data path that is approximately nine bits wide.
  • the T9b encoding format can be used in field programmable gate array (FPGA) or application specific integrated circuit (ASIC) switching components.
  • the T9b coding format can be used instead of the 64b/66b coding format to provide more signaling information in each block, for example, and thus reduce lookup information or control structures (eg, lookup tables) and/or handle signaling in the USTM service The amount of resources that the information may require.
  • the encoded SU600 may have a bandwidth of about 64 kilobytes per second (Kb/s) based on a time window of about 125 ⁇ s, for example.
  • the encoding SU600 may include USTM service or transition information. Specifically, the encoding SU600 may include about nine bits, where the first part 602 may include about eight bits (eg, B0 to B8), and the second part 604 may include the remaining signaling bits (eg, Bs).
  • the first part 602 may include TDM, HPF or BEP services. Alternatively, the first part 602 may include signaling and other information similar to the opcode field 510, location field 512, and connection field 520 in the encoding block 500.
  • the second part 604 may include approximately one parity bit (eg, bit 7), and may be used to detect errors in the transmitted data.
  • the parity bits can be used to implement parity checking of the remaining bits in the first portion 602.
  • the parity bit can be used to check whether the encoded SU600 includes service data or signaling (or control) information. For example, if the number of "1" bits including parity bits Bs in the encoding SU600 is an odd number, the encoding SU600 may be data SU. Otherwise, the code SU600 may be the control SU.
  • the first part 602 may include any one of a plurality of operation codes indicating transition signals in Table 1 or Table 2.
  • the first part 602 may also use other operation codes to indicate other transition information. Since a relatively small number of opcodes, such as approximately eight opcodes, can be used in the first part 602, the T9b encoding format can provide additional codes that can be used to encode SU600, for example, to provide effective error detection.
  • the opcodes or bit codes in the code that can be used in the first part 602 can be selected or determined so that a sufficient distance between bit sequences or codes is provided. Therefore, the detection ability using parity bits can be improved.
  • FIG. 7 illustrates an embodiment of encoding SU700, which may correspond to the T10b encoding scheme.
  • the T10b coding scheme can be used to multiplex TDM services, HPF services, BEP services, or a combination thereof, for example, by mapping every approximately 10 bits in the stream to approximately 8 bits using the 8b/10b coding format.
  • the 8b/10b encoding format can be used in Gigabit Ethernet systems or 10 Gigabit XAUI, which can be used to transmit Ethernet data in the back.
  • the T10b coding scheme can be used to signal changes in the USTM service.
  • the T10b encoding format can be used instead of the 64b/66b encoding format and the T9b encoding format, for example, to provide more signaling information in each block, and thus reduce the amount of control structure and/or resources in the switch.
  • the encoding SU700 may include service data or control (eg, transition or signaling) operation codes.
  • the encoding SU700 may include approximately 10 bits, which may be used to indicate service data or control operation codes, such as transition signals in Table 1, Table 2, or Table 3 below.
  • at least some of the standard 8b/10b data symbols may be used to encode the service data in the encoded SU700, and a specified set of 8b/10b control symbols may be used to encode the control opcode.
  • FIG. 8 and Table 3 show examples of a set of 8b/10b control symbols 800 that can be used as control opcodes in the encoding SU700.
  • Figure 8 shows a set of suitable control opcodes that can be selected from multiple 8b/10b control symbols 800 to indicate different transition types.
  • the selected control operation code may correspond to about eight code groups that can be used as indicated by the shaded blocks (e.g., K28.1, K28.2, K28.3, K28.4, K28.5, K28. 6. K29.7 and K30.7).
  • Table 3 summarizes the types of transitions that can be indicated by the selected control opcode. 8 and Table 3 illustrate a set of control opcodes that can be selected from 8b/10b control symbols 800 to indicate different transition types, but other sets including other control opcodes from 8b/10b control symbols 800 can be used in other embodiments .
  • Table 3 UST transition signaling using T10b encoding.
  • the switch may maintain a control structure, such as a flow graph and/or time slot (TS) status table, for example, in a memory component or database storage device.
  • the control structure can be used to track the status of the service flow or time slot in the USTM data stream, for example, to allow the time slot allocated to the HPF to be reused by the BEP service when the HPF service is idle.
  • the control structure may support the establishment of data streams, disassembly of data streams, increase of stream bandwidth and/or decrease of bandwidth.
  • the control structure can also be used to remember and recall the previous state of the stream when interrupted by an idle symbol (or opcode).
  • FIG. 9 illustrates an embodiment of a flow diagram 900, which may be a control structure for handling USTM traffic.
  • the flow graph 900 may include multiple entries that map multiple time slots, for example, in a periodic time window.
  • the flow graph 900 may include approximately N entries (N is an integer), which corresponds to approximately N time slots in a periodic time window.
  • Each entry in the flow graph 900 may include: a flow number field 902, which may include a flow identifier (ID) indicating the flow in the USTM data flow; and a parity field 904, which may be used to check parity.
  • the stream number field 902 may include approximately 17 bits (eg, from bit 0 to bit 16), and the parity field 904 may include approximately one bit (eg, bit 7).
  • the flow graph 900 can support approximately 128,000 flows in the data flow, which may be sufficient to support approximately 100G Ethernet systems. If necessary, the length of the stream number field 902 may be increased (eg, in terms of number of bits) to support a larger number of streams.
  • the flow may correspond to an HPF service flow or a BEP service flow.
  • Table 4 shows a flow numbering scheme that includes a set of flow numbers or IDs that can be used to indicate different types (eg, assignments) of traffic flows in the data flow.
  • Different types of service flows may include unassigned services (eg, BEP services), unused (DNU) services, and HPF/TDM services. Some stream numbers may not be used and/or may be reserved for future use.
  • the flow graph 900 may be updated locally, for example, using software, or dynamically by sending OAM signaling embedded in a time slot.
  • a multi-part opcode eg, multi-part opcode SU400
  • Table 5 illustrates an embodiment of an entry in the TS status table, which may be another control structure for handling USTM traffic.
  • the TS status table can be used to specify the status of each time slot in the data stream, and can include entries for each time slot.
  • the entry may include approximately two bits (eg, bit 0 and bit 1), and the two bits may each be assigned one of two values to indicate different TS states and different types of traffic.
  • bit 0 can be set to about 0 to indicate the default TS state, or set to about 1 to indicate the OAM pending state.
  • bit 1 may be set to about 0 to indicate packet-based services, or set to bit 1 to indicate TDM-based services.
  • the information in Table 5 or Table 5 may be included in the flow graph 900 and/or Table 4.
  • Table 5 TS state table entries.
  • Table 6 shows an embodiment of a stream state table, which can be used to keep track of the state of each stream in the data stream.
  • the flow state table may include an entry for each flow to indicate its corresponding state.
  • each entry may include a flow number and flow status value identifying the flow.
  • About two bits (eg, bit 0 and bit 1) can be used to indicate the flow state value.
  • Table 7 illustrates the different flow status values that can be used to indicate the flow, such as idle, bearer packet activity, OAM packet activity, and reserved/standby.
  • the USTM service may have a granularity equal to about 64Kb/s, for example, where the smallest data block size may be equal to about 64Kb/s. However, in other embodiments, the granularity of the USTM service may be equal to an integer multiple of about 64Kb/s.
  • the time slots in the data stream may have the granularity of SONET/SDH columns, for example, about 9 bytes per 125 ⁇ s time window. Thus, the same two bits can be used approximately 9 times within the 125 ⁇ s time window. This granular configuration can reduce the logical size, and therefore the cost of implementing flow and time slot maps and/or other control structures.
  • Table 6 Flow state table.
  • the USTM switching system may support floating time windows (eg, about 125 ⁇ s) and insertion of idle traffic or time slots to provide rate adaptation for different traffic types.
  • rate adaptation may be implemented in line interface cards, such as tributary interface 330, line interface 350, and/or other network interfaces.
  • the floating time window can support link-level inter-node frequency adaptation.
  • idle cycles or time slots
  • Idle cycles can be inserted for TDM, HPF and/or BEP services, for example, within or between packets.
  • the UST switching system may support periodic time windows (eg, about 125 ⁇ s), hardware-supported flow graphs and TS status updates, and synchronization mechanisms to provide collision-free dynamic bandwidth management.
  • OAM codes can be used to implement bandwidth management, stream establishment, and stream disassembly, as described above.
  • a node may, for example, transmit a multi-part opcode to the switch based on each time slot, which may indicate the operation to be performed and the associated flow number. After transmitting the stream number and other parameters, the stream number can be loaded on the next time window, for example on the next 125 ⁇ s boundary.
  • an acknowledgment may be generated and sent by the switch in response to receiving the flow number and other parameters.
  • FIG. 10 illustrates an embodiment of a UST signaling method 1000 that can be used to transmit data in the USTM data stream and provide transition information in the transmitted USTM data stream.
  • the data transmitted in the USTM data stream may correspond to multiple streams and/or service types that can be forwarded from at least one source node.
  • the UST signaling method 1000 can be implemented by a UST switching system, such as the UST switching device 300, wherein the different steps in the method 1000 can be implemented by any of the components of the device 300.
  • Method 1000 may begin at block 1002, where data in a stream may be received.
  • the tributary interface 330 may receive data in a stream from one of the first links 320, such as 100G Ethernet data based on a 64b/66b encoding format. Additionally or alternatively, the tributary interface 330 may receive, for example, TDM service data from the SONET/SDH network.
  • a flow graph may be used to identify the flow. For example, the tributary interface 330 may obtain the flow ID indicating the flow of the received data from the data. The flow ID or number may match the entry in the flow graph 332.
  • the method 1000 may determine whether the state of the stream has changed. If the state of the flow has changed, for example from idle to active, then the method 1000 may proceed to block 1010. Otherwise, the method 1000 may proceed to block 1014.
  • transition signaling may be sent in the USTM data stream.
  • the transition signaling can be added to the USTM stream, for example, based on any of the UST encoding schemes described above using operation codes.
  • Transition signaling may specify the type of transition that has occurred in the stream of received data.
  • the flow state table and/or TS state table may be updated. For example, an entry in the flow state table (eg, Table 6) corresponding to the flow of data, for example, including the same flow ID data, may be updated to indicate the current changed state of the flow. Additionally or alternatively, an entry in the TS status table (eg, Table 5) corresponding to the time slot allocated for the data may be updated to indicate the currently changed status.
  • the data may be sent to the switch fabric (eg, switch fabric 310) in the USTM data stream, such as in a single link.
  • the tributary interface 330 may send data in the allocated time slots in the USTM stream via the XLAUI or XAUI interface.
  • the method 1000 may determine whether to continue, for example, if there is still data to receive. If the reception of data continues, the method 1000 may return to block 1002. Otherwise, the method 1000 may end.
  • FIG. 11 illustrates a typical general network component 1100 suitable for implementing one or more embodiments of the components disclosed herein.
  • the network component 1100 may include a processor 1102 (which may be referred to as a central processing unit or CPU).
  • the processor 1102 communicates with any memory device including a secondary storage device 1104, a read only memory (ROM) 1106, a random Access memory (RAM) 1108, input/output (I/O) device 1110, and network connectivity device 1112, or a combination thereof.
  • the processor 1102 may be implemented as one or more CPU chips, or may be part of one or more ASICs.
  • the secondary storage device 1104 usually includes one or more disk drives or other storage devices, and is used for non-volatile storage of data, and acts as an overflow data storage device when the RAM 1108 is not large enough to hold all working data.
  • the secondary storage device 1104 may be used to store programs, where when such programs are selected for execution, the programs are loaded into the RAM 1108.
  • the ROM 1106 is used to store instructions and possible data read during program execution.
  • the ROM 1106 is a non-volatile memory device, which generally has a smaller memory capacity relative to the larger memory capacity of the secondary storage device 1104.
  • RAM 1108 is used to store volatile data and possibly instructions. Access to both ROM 1106 and RAM 1108 is generally faster than access to secondary storage device 1104.
  • R Rl+k*(Ru-Rl)
  • k is a variable ranging from 1 percent to 100 percent, with a percentage increase
  • k is 1, 2%, 3%, 4%, 5%, ..., 50%, 51%, 52%, ... , 95 percent, 96 percent, 97 percent, 98 percent, 99 percent, or 100 percent.
  • any numerical range defined by the two R numbers as defined above is also specifically disclosed.
  • the use of the term "optionally" with respect to any element of the claim means that the element is needed or the element is not needed, and both alternatives fall within the scope of the claim.

Landscapes

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

Abstract

L'invention concerne un dispositif. Le dispositif comprend une structure de commutation couplée à de multiples interfaces et configurée pour commuter de multiples flux de données de multiplexage (USTM) de transport de service universel (UST) entre les multiples interfaces. Les flux de données USTM comprennent un trafic à commutation de paquets, un trafic à commutation de circuits et une signalisation transitoire qui indique le changement d'état entre le trafic à commutation de paquets et le trafic à commutation de circuits. La signalisation transitoire n'indique pas l'état de chaque octet des flux de données USTM. L'invention concerne également un composant de réseau. Le composant de réseau comprend au moins un processeur couplé à une mémoire et configuré pour : recevoir des données correspondant à un flux ; identifier le flux en utilisant une carte de flux ; déterminer si l'état du flux a changé ; si l'état du flux a changé, transmettre la signalisation transitoire indiquant l'état du flux sur le flux de données USTM ; et transmettre les données sur le flux de données USTM.
PCT/CN2018/118034 2018-11-29 2018-11-29 Dispositif et procédé de codage transitoire de transport de service universel WO2020107298A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2018/118034 WO2020107298A1 (fr) 2018-11-29 2018-11-29 Dispositif et procédé de codage transitoire de transport de service universel

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2018/118034 WO2020107298A1 (fr) 2018-11-29 2018-11-29 Dispositif et procédé de codage transitoire de transport de service universel

Publications (1)

Publication Number Publication Date
WO2020107298A1 true WO2020107298A1 (fr) 2020-06-04

Family

ID=70854441

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/118034 WO2020107298A1 (fr) 2018-11-29 2018-11-29 Dispositif et procédé de codage transitoire de transport de service universel

Country Status (1)

Country Link
WO (1) WO2020107298A1 (fr)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6999450B2 (en) * 2001-04-25 2006-02-14 Occam Networks Ethernet based TDM switch
CN1859382A (zh) * 2005-12-16 2006-11-08 华为技术有限公司 支持多业务的通信设备及其方法
CN101212424A (zh) * 2006-12-28 2008-07-02 杭州华三通信技术有限公司 融合了电路交换和分组交换的以太网交换方法与设备
CN101299649A (zh) * 2008-06-19 2008-11-05 中兴通讯股份有限公司 基于通用成帧规程的多业务混合汇聚方法和装置
CN102439923A (zh) * 2009-07-20 2012-05-02 华为技术有限公司 传输通用服务传输转变编码

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6999450B2 (en) * 2001-04-25 2006-02-14 Occam Networks Ethernet based TDM switch
CN1859382A (zh) * 2005-12-16 2006-11-08 华为技术有限公司 支持多业务的通信设备及其方法
CN101212424A (zh) * 2006-12-28 2008-07-02 杭州华三通信技术有限公司 融合了电路交换和分组交换的以太网交换方法与设备
CN101299649A (zh) * 2008-06-19 2008-11-05 中兴通讯股份有限公司 基于通用成帧规程的多业务混合汇聚方法和装置
CN102439923A (zh) * 2009-07-20 2012-05-02 华为技术有限公司 传输通用服务传输转变编码

Similar Documents

Publication Publication Date Title
EP2430804B1 (fr) Codage transitoire de transport de service universel
KR100567326B1 (ko) Ｓｏｎｅｔ／ｓｄｈ, ｐｄｈ, 그리고 이더넷 신호의 통합스위칭/전달 장치 및 그 방법
US7583664B2 (en) Techniques for transmitting and receiving traffic over advanced switching compatible switch fabrics
US6847644B1 (en) Hybrid data transport scheme over optical networks
CN107438028B (zh) 一种客户业务处理的方法和设备
US6771663B1 (en) Hybrid data transport scheme over optical networks
US11477549B2 (en) Transmission network system, data switching and transmission method, apparatus and equipment
WO2018090856A1 (fr) Procédé et dispositif de construction de groupe ethernet flexible
US7006525B1 (en) Hybrid data transport scheme over optical networks
US20020176450A1 (en) System and methods for selectively transmitting ethernet traffic over SONET/SDH optical network
US20040184450A1 (en) Method and system for transport and routing of packets over frame-based networks
US20040252688A1 (en) Routing packets in frame-based data communication networks
US9380363B2 (en) Network element for switching time division multiplex signals
US8374177B2 (en) Network element for switching time division multiplex signals
JP2002198994A (ja) Ｇｆｐフレーム転送装置およびｇｆｐフレーム転送方法
JP2002208903A (ja) 光回線データを広域／都市域リンクに伝送するためのフレキシブルなマルチプレクサ／デマルチプレクサ及び方法
JP2008042731A (ja) 伝送装置
US20220158938A1 (en) Routing flexe data in a network
WO2009021376A1 (fr) Dispositif ethernet et procédé de traitement d'affaire ethernet basé sur l hiérarchie numérique synchrone (sdh)
US20060140226A1 (en) Techniques for processing traffic transmitted over advanced switching compatible switch fabrics
EP4287544A1 (fr) Procédé de détermination d'un intervalle de temps de transmission, et appareil associé
US7573898B2 (en) Method and apparatus to double LAN service unit bandwidth
EP1701495B1 (fr) Commutateur hybride numérique pour commuter le trafic de données par circuit et par paquets
WO2017181675A1 (fr) Procédé, dispositif et système de traitement de données sur ethernet
Bernstein et al. VCAT-LCAS in a clamshell

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 18941577

Country of ref document: EP

Kind code of ref document: A1