TRANSPORT INTERFACE FOR PERFORMING PROTECTION SWITCHING OF TELECOMMUNICATIONS TRAFFIC

Abstract: A transport interface (10) provides add drop multiplex functionality and termination requirements for the transportation of network traffic. The transport interface (10) includes high speed units (12), broadband interfaces (16), and SONET formatters (18). Each high speed unit (12), broadband interface (16), and SONET formatter has redundant protection pairs (A and B). The high speed units (12), broadband interfaces (16), and SONET formatters (18) communicate with each other by in-band datalinks (40). The redundant protection pairs (A and B) communicate with one another by protection pair datalinks (42). The in-band datalinks (40) and the protection pair datalinks (42) provide an effective means for performing protection switching within the transport interface (10) in the event of component failure. The in-band datalinks (40) are generated out of available or consumed bytes within either a section overhead (32) or a line overhead (34) of SONET OC-N frame (30). The protection pair datalinks (42) provide communication capability over a common control communications interface. The in-band datalinks (40) and the protection pair datalinks (42) work together to provide a smooth transition from one component to another in the event of a protection switch.

Description: TRANSPORT INTERFACE FOR PERFORMING PROTECTION SWITCHING OF TELECOMMUNICATIONS TRAFFIC TECHNICAL FIELD OF THE INVENTION The present invention relates in general to telecommunication information transportation and more particularly to a transport interface for performing protection switching of telecommunications traffic. BACKGROUND OF THE INVENTION In SONET based add drop multiplex telecommunication equipment, it is common to have a transport system composed of multiple printed circuit assemblies requiring a variety of hard wired signaling communication channels between assemblies. Popular uses of hard wired inter-assembly signaling communications include card provisioning, status checking, performance monitoring, and protection switching. Hard wired signaling communication connections increase the expense and size of the assemblies and the transport system. Therefore, it is desirable to reduce the necessity of hard wired signaling communications connections in a transport system of a telecommunications network. SUMMARY OF THE INVENTION From the foregoing, it may be appreciated that a need has arisen for a transport system in a telecommunications network that is less dependent on hard wired signaling communication connections among its various components. In accordance with the present invention, a transport interface for performing protection switching of telecommunications traffic is provided that substantially eliminates or reduces disadvantages and problems associated with conventional add drop multiplex telecommunication equipment. According to an embodiment of the present invention, there is provided a transport interface for performing protection switching of telecommunications traffic that includes first and second high speed unit pairs where each of the first and second high speed unit pairs have a main unit and a protection unit coupled to each other by first and second protection pair datalinks. The first and second high speed unit pairs are coupled together by a first m- band datalmk. A broadband interface pair couples to the first and second high speed unit pairs by second and third m-band datalinks. The broadband interface pair includes a main unit and a protection unit coupled to each other by a second protection pair datalmk. A SONET formatter pair is coupled to the first and second high speed unit pairs by fourth and fifth m-band datalinks. The SONET formatter pair includes a mam unit and a protection unit. The first, second, third, fourth, and fifth m-band datalinks provide protection switching status and processor operability status for the first and second high speed unit pairs, the broadband interface pair, and the SONET formatter pair conjunction with the various protection pair datalinks. The present mvention provides various technical advantages over conventional add drop multiplex telecommunication equipment. For example, one technical advantage is to eliminate a need for dedicated hard wired signaling communication connections. Another technical advantage is to provide protection switching signaling over unused portions of frame overhead. Yet another technical advantage is to provide each component in a transport interface with status information concerning the operability of all other components. Other technical advantages are readily apparent to one skilled in the art from the following figures, description, and claims. BRIEF DESCRIPTION OF THE DRAWINGS For a more complete understanding of the present invention and the advantages thereof, reference is now made to the following description taken in conjunction with the accompanying drawings wherein like reference numerals represent like parts, in which: FIGURE 1 illustrates a block diagram of a transport interface used in a telecommunication network; FIGURE 2 illustrates a structure for a SONET OC-N frame transported through the transport interface; FIGURE 3 illustrates a block diagram of communication links between components in the transport interface; FIGURES 4A-C show examples of protection configurations available in the transport interface; FIGURES 5A-B show examples of span switch and ring switch protection switches of the transport interface; FIGURE 6 shows an example of a component protection switch within the transport interface; and FIGURE 7 illustrates an in-band datalink driver to create the message structure. DETAILED DESCRIPTION OF THE INVENTION FIGURE 1 shows a block diagram of a transport interface 10 for use in a telecommunications network. Transport interface 10 provides appropriate add drop multiplex functionality and termination requirements for the transportation of network traffic. Transport interface 10 includes east and west high speed units 12 that interface with fiber optic connections 14 operating at illustrated example rates of OC-3, OC-12, or OC-48 for carrier terminations. Transport interface 10 also includes a broadband interface 16 and a Synchronous Optical Network (SONET) formatter 18 for service terminations. Broadband interface 16 provides for the transportation of signals at rates higher than wideband DS-1 rates to include DS-3, OC- 3, and STS-1 signal rates. SONET formatter 18 provides for the transportation of wideband DS-1 and narrowband DS-0 signals for cross-connection to and from subscribers. On the receive side, east and west high speed units 12 perform optical to electrical conversion of SONET signals to Synchronous Transport Signals, SONET section and line overhead terminations, full Synchronous Transport Signal cross-connections, system timing alignment, and distribution of Synchronous Transport Signals to broadband interface 16, SONET formatter 18, and other high speed units 12. On the transmit side, east and west high speed units 12 perform multiplexing of Synchronous Transport Signals from broadband interface 16, SONET formatter 18, and other high speed units 12. East and west high speed units 12 also provide full Synchronous Transport Signal cross-connections, SONET section and line overhead generation, and electrical to optical conversion of Synchronous Transport Signals to SONET signals. Payload transport typically occurs between east and west high speed units 12 as through traffic and among east and west high speed units 12, broadband interface 16, and SONET formatter 18 as dropped traffic. Broadband interface 16 performs line termination and origination of DS-3, STS-1, and OC-3 signals. Broadband interface 16 also performs path termination, origination, and performance monitoring of STS-1 paths. Broadband interface 16 is shown with a DS-3 unit 20, an OC-3 unit 22, and an STS-1 unit 24. SONET formatter 18 performs path termination of STS-1 signals, derives constituent Virtual Tributaries, and either pass through or drop Virtual Tributaries on a path by path basis. Virtual Tributaries that are dropped have their path overhead terminated and constituent DS-0 signals are placed onto space busses to the subscribers. FIGURE 2 shows a structure of a SONET OC-N frame 30. SONET OC-N frame 30 is a 9 row by 90 column by N phase 125 microsecond frame. SONET OC-N frame 30 includes a section overhead 32, a line overhead 34, a path overhead 36, and a Synchronous Payload Envelope 38. For an OC-3 signal, SONET OC-N frame 30 would be repeated three times for each STS-1 portion of the OC-3 signal m order to provide an STS-3 signal. Section overhead 32, line overhead 34, and path overhead 36 are separated into a plurality of specific bytes to transport signaling information associated with synchronous payload envelope 38. Appendix 1 delineates each signaling byte withm SONET OC-N frame 30. FIGURE 3 shows m-band datalinks 40 and protection pair datalinks 42 withm transport interface 10 having redundant protection pairs. Each redundant protection pair has two components, a main unit and a protection unit. The main unit is the component that is active at a given point in time. Datalinks allow components withm transport interface 10 to communicate among each other. In-band datalinks 40 provide communication capability between redundant protection pairs and every other redundant protection pair withm transport interface 10 over a backplane bus interconnection. Protection pair datalinks 42 provide communication capability between redundant protection pair components over a common control communications interface bus. In-band datalinks 40 and protection pair datalinks 42 work together to provide a technique for performing protection switching functions a bidirectional, as well as a unidirectional, manner. The mam and protection units of SONET formatter 18 may not cause their own protection switch and thus may not be coupled by a protection pair datalmk 42. FIGURES 4A-C show the protection ring configurations available in transport interface 10. FIGURE 4A shows a unidirectional path switched ring (UPSR) configuration 100. UPSR fiber configuration 100 uses two unidirectional transport rings 102 and 104 coupling separate transport interfaces 10 shown as nodes 1-4. Traffic is inserted and bridged onto both rings and carried simultaneously in each direction. Redundant copies of the traffic are available at the destination from either direction of reception. One copy is selected based on the quality of the received signal . FIGURE 4B shows a 4 fiber bidirectional line switched ring (BLSR) configuration 110 operating as a span switch. Span switching occurs when a failure affects the mam connection between two transport interfaces 10. Traffic is switched from the mam connection to the protection connection only for that span with no changes made to other span connections between nodes. FIGURE 4C shows a 4 fiber BLSR configuration 120 operating as a ring switch. Ring switching occurs when a failure affects both the mam and protection connections between two transport interfaces 10. Traffic is looped around and placed on the protection connections and intermediate nodes are placed in a pass through state to allow the traffic to pass through unaltered. Alternatively, a 2 fiber configuration may be used where half the payload is reserved for working traffic and the other half of the payload is used for protection traffic. Span switching would not be available m the 2 fiber configuration. FIGURES 5A-B show examples of how protection switches are performed between main and protection fibers. In FIGURE 5A, a span switch is performed from a ma unit to a protection unit of east high speed unit 12. The mam unit A informs the protection unit B over protection pair datalmk 42 that a failure was detected on the ma fiber. The protection unit B compares a priority of the detected failure with a current protection switch priority. If the current priority is greater than the detected failure priority, the protection switch is denied. If the protection switch is allowed, protection unit B signals ma unit A through protection pair datalmk 42 and broadband interfaces 16 and SONET formatter 18 through m- band datalinks 40 to perform the protection switch. Broadband interfaces 16 and SONET formatter 18 select their traffic from protection unit B instead of mam unit A. Broadband interfaces 16 and SONET formatter 18 send their new protection status over in-band datalinks 40. In FIGURE 5C a ring switch is performed by looping traffic away from the failure. The main unit A of west high speed unit 12 detects a main fiber failure and sends a message over protection pair datalink 42 to its corresponding protection unit B. Protection unit B also sees a failure and, along with the message from main unit A, determines that a ring switch is necessary. Protection unit B sends a message to broadband interfaces 16, SONET formatter 18, and east high speed unit 12 over appropriate m-band datalinks 40 to request a ring switch. Protection unit B also sends a message to mam unit A over its protection pair datalink 42 to inform of the request for a ring switch. Broadband interfaces 16 and SONET formatter 18 switch their received traffic from main unit A of west high speed unit 12 to protection unit B of east high speed unit 12 and broadcast their new protection status over appropriate m-band datalinks 40. Protection unit B of east high speed unit 12 sends out its new state on m-band datalinks 40 and routes outgoing traffic onto its fibers. FIGURE 6 shows an example of a protection switch for a broadband interface 16. The mam unit A of broadband interface 16 detects a failure on either the incoming facility or with its own equipment. Mam unit A sends a message over its protection pair datalmk 42 to its protection unit B to request a switch. Protection unit B determines if the switch should occur based on its status. If the protection switch is allowed, protection unit B sends a message over m-band datalinks 40 to east and west high speed units 12. Protection unit B also sends a message over protection pair datalinks 42 to inform main unit A of the requested switch. East and west high speed units 12 select their traffic from protection unit B instead of mam unit A. East and west high speed units 12 send a message indicating their change in protection status to the other components withm transport interface 10 over m-band datalinks 12. In-band datalinks 40 are generated out of available bandwidth in section overhead 32 and line overhead 34 of SONET OC-N frame 30. East and west high speed units 12 terminate section overhead 32 and line overhead 34, consuming multiple byte locations and thus making time slots m the data stream available for use. Specific bytes of section overhead 32 or line overhead 34 can be designated to carry messages containing information concerning the protection capability. The information contained m these messages includes protection switch information that informs other protection pairs which of the protection pair components is bemg listened to and which protection pair component to listen to. The messages also provide physical and processor status information for feedback on how components withm transport interface 10 perceive the operating health of other components and feedback on the functionality of processors on the components . Table 1 shows an example of a message structure X sent from east or west high speed units 12 to broadband interface 16 and SONET formatter 18. Message structure X in this example is placed into the KI and K2 bytes of line overhead 34. Bits 0, 1, and 2 of message structure X provide the protection switch information for each broadband interface 16 wherein a zero indicates the A component is selected and a one indicates the B component is selected. Bits 3 and 4 provide the protection switch status and request for east or west high speed unit 12 protection pairs. Bits 5-12 provide the functional status of each component withm transport interface 10. Each component may be detected as functional or not present, nonfunctional, or not sane. Bits 13 and 14 provide alternating validation for the processor on the active east or west high speed unit 12 protection pair component. Bit 15 provides the status of the east or west high speed unit 12 protection pair based on the status indicated by protection pair datalmk 42. TABLE 1. MESSAGE STRUCTURE X KI byte K2 byte 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 PP PP PP SFD SFD BB3 BB3 BB2 BB2 BB1 BB1 Rng A/B BB BB BB Stat 1 0 B A B A B A B A 3 2 1 Bits 0-2 Which of the BBx (x=l, 2, or 3) Protection Pair the HSU is listening to. 0 - A 1 - B Bit 3 Which of the HSUs the drop cards should be listening to. 0 - A 1 - B Bit 4 When set along with a change m state of bit 3, defines a ring switch request. 1 - Ring Switch Request Bits 5-12 Status of drop card as seen by HSU. 1 - Failed Bits 13-14 Ping-Pong values for processor sanity. Alternate 11 and 01 patterns. 10 - For future use. 00 - Holdoff processing IBD messages (used during upgrades) Bit 15 Protection Pair Status 1 - Failed Validation of messages sent on m-band datalinks 40 and protection pair datalinks 42 is used to avoid interpreting garbage information as valid protection switch requests. The alternating validation bits provide a technique of checking the processor functionality of a component. The alternating validation bits swap between 11 and 01 every four milliseconds to show that the processor of the active east or west high speed unit 12 protection pair component is operating properly. The content of message structure 50 is updated during each change of the alternating validation bits. Two consecutive samples of a protection switch information, physical status information, and processor status information are received before such information is considered valid. Each component withm transport interface 10 samples m-band datalinks 40 and protection pair datalinks 42 every two milliseconds. If the alternating validation bits do not change or a validated message is not received within a desired time interval, then a failure is reported for the specified component. Table 2 shows an example of a message structure Y sent from broadband interface 16 and SONET formatter 18 to east or west high speed units 12. Message structure Y in this example is placed into the KI and K2 bytes of line overhead 34 and of the second STS-1 signal withm the STS-3 set. Bits 0 and 1 provide the protection switch information about each high speed unit 12 pair. By providing this information back to high speed units 12, discrepancies in databases between components of transport interface 10 can be determined. Bit 3 provides the switch request and status for the protection pair generating message structure Y. The mam unit may source this message directly if the protection unit is not present or not operating. Bits 5-8 provide the status information for each high speed unit 12. This information is helpful in isolating failures within the system and reducing unnecessary protection switches. Bits 9 and 10 provide the status of the selected path when transport interface 10 is operating in a path protected switched ring configuration. Bits 13 and 14 provide the alternating validation technique for the processor of the component sending message structure Y. Bit 15 provides the status of the protection pair based on the protection pair datalink status. This bit provides a method to evaluate a message from a protection pair when the main and protection units are sending conflicting requests. Bits 2, 4, 11, and 12 are reserved for future use. Table 3 shows an example of a message structure Z sent from east high speed unit 12 pairs to west high speed unit 12 pairs, or vice versa. Message structure Z m th s example is also placed into the KI and K2 bytes of line overhead 34 of the second STS-1 signal with the STS-3 set. Bit 0 provides the protection switch information for the opposite high speed unit 12 pair. Bits 3 and 4 provide the switch request and status for the high speed unit 12 pair. When the protection high speed unit 12 determines that a protection switch is necessary, bits 3 and 4 will be set to reflect the requested change. Bit 3 indicates which one of the protection pair should be used and bit 4 is set when a ring switch is required while operating in the bidirectional line switched ring configuration. If the protection unit is not present or not operating, then the mam unit of the protection pair may source this message directly but only regarding a switch back to itself. Bits 5 and 6 provide the status information of each opposite high speed unit 12. This information is helpful isolating failures withm the system and reducing unnecessary protection switches. Bits 7, 8, and 9 are used only during bidirectional line switched ring configuration operation for requesting appropriate pass through states. Partial KI and K2 bytes or full KI and K2 bytes may be passed through in the APS bytes with the option of also passing through the signal. Bits 13 and 14 provide the alternating validation technique for the processor of the high speed unit 12 that sends message structure Z. Bit 15 provides the status of the protection pair based on the protection pa r datalink status. This bit provides a method of evaluating a message from the protection pair when the mam and protection units are sending conflicting requests. Bits 1, 2, 10, 11, and 12 are reserved for future use. TABLE 3. MESSAGE STRUCTURE Z KI byte K2 byte 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 PP PP PP Und Und Und Und Prot Full Part Stat Stat A/B Und Und Rev Stat 1 0 (0) (0) (0) (0) Ch K K B A (0) (0) A/B B ts 0-1 Which of the HSUs Protection Pair from the other side th s HSU is listening. 0 - A 1 - B Bit 3 Which of the HSUs the opposite side should be listening to. 0 - A 1 - B Bit 4 When set along with a change in state of bit 3, defines a ring switch request. 1 - Ring Switch Request Bits 5-6 Status of HSUs on the opposite s de as seen from this HSU. 1 - Failed Bit 7 Pass KI byte and bit 5 of K2 byte through (BLSR only) . Bit 8 Pass Full APS bytes through (BLSR only) . Bit 9 Pass the protection channel through. Bits 13-14 Ping-Pong values for processor sanity. Alternate 11 and 01 patterns. 10 - For future use 00 - Holdoff processing IBDL messages (used during upgrades) Bit 15 Protection Pair Status 1 - Failed Bits 1-2, 10-12 For future use, set to 0. FIGURE 7 shows how messages are placed into the KI and K2 byte locations of line overhead 34. A message is transmitted continuously until a new message is provisioned. A double buffered in-band datalink driver 60 design used in each component of transport interface 10 provides the means for changing and sending messages. In- band datalink driver 60 includes a 16-bit transmit register 62 that supplies the information to the KI and K2 byte locations of line overhead 34. Two 8-bit new message registers 64 and 66 are able to receive changes for the KI and K2 byte locations. A processor 68 of the particular component writes new message information into the two 8-bit new message registers 64 and 66 without affecting the outgoing data from the 16-bit transmit register 62. A transmit new message signal 70 from processor 68 causes information in the two 8-bit new message registers 64 and 66 to be stored into the 16-bit transmit register 62. A message is continuously sent until the next assertion of the transmit new message signal 70. In-band datalink driver 60 minimizes software timing requirements. Data transfer from transmit register 62 to the KI and K2 byte timeslots occurs every 125 microseconds. Transmit new message signal 70 causes the load of new data from 8-bit new message registers 64 and 66 into transmit register 62 at the next frame boundary. Transmit new message signal 70 is then cleared until a new data load is desired. The process of storing data into transmit register 62 for placement onto the KI and K2 byte timeslots may take up to 125 microseconds, corresponding to a frame length and size, to complete. Table 4 shows an example of a message structure W for protection pair datalink 42. Message structure W is sent protection pair datal k 42 between a mam unit and a protection unit withm a protection pair to inform each other that a protection switch is needed. Message structure W works much the same way as the message structures for m-band datalmk 40. Bits 1 and 2 provide the switch request and status for the appropriate unit of the protection pair. Bit 1 indicates the unit in the protection pair that should now be used. Bit 2 is set when a ring switch is required while operating in the bidirectional line switch ring configuration. When the main unit sends message structure W to the protection unit, the message structure must first be evaluated by the protection unit before it is considered valid. If the protection switch request cannot be honored, then the protection un t returns a message that says it received a request to switch to the protection unit but operation is still affective on the ma unit. This w ll cause the main unit to no longer request the switch. If the protection switch request is validated by the protection unit, then it shall send back its change of state to the ma unit as well as sending the appropriate m-band datalmk message to other components withm transport interface 10. Bit 3 provides the status of the other unit of the protection pair. Bits 4 and 5 provide the alternating validation technique for the processor of the unit of the protection pair sending message structure W. Bits 0, β, and 7 are reserved for future use. TABLE . MESSAGE STRUCTURE W B2 BYTE 7 6 5 4 3 2 1 0 Fail-1 Fail-0 PP-1 PP-0 Rev Ring A/B Rev Fail A/B Bit 1 Which card this member of the protection pair is on. 0 - A 1 - B Bit 2 When set along with a change in state of bit 1, defines a ring switch request. 1 - Ring Switch Request Bit 3 Status of the other member of the protection pair that we detect. 1 - Failed Bits 4-5 Ping-Pong values for processor sanity. Alternate 11 and 01 patterns. 10 - For future use 00 - Holdoff processing IBDL messages (used during upgrades) Bits 0, 6, 7 Reserved for future use. Upon installation of a main or protection unit within transport interface 10, inadvertent protection switching must be avoided when power is applied to a newly installed unit. Once power is applied to a new unit, in-band datalinks 40 and protection pair datalink 42 become active and the unit sends an all zeros message on both datalinks. To the other units within transport interface 10, the message will be received as a failure since the alternating validation bits will not be changing state. As the new unit begins to be provisioned, the message sent on both datalinks is changed to all zeros except for the alternating validation bits which are both set to zero to indicate that the datalinks should be ignored until these bits begin alternating. Once the new unit has been fully provisioned, it begins operation on the datalinks by first checking received information from m-band datalmk 40 and protection pair datalink 42. In this manner the unit can determine the protection state of transport interface 10. This information determines what is sourced on both datalinks to allow the new unit to configure itself to the appropriate protection state. Conflicting messages may occur over m-band datalmk 40 and protection pair datalink 42 which fall into three categories - a receiver unit on a datalink is not listening to the same unit as the sender requested, switch requests differ on a datalink between two units in transport interface 10, and status differs between two units and a protection pair. Where a receiver unit is not listening to the same unit as requested by the sending unit, the handling is different between protection pair datalmk 42 and m-band datalmk 40. On protection pair datalmk 42 this situation may arise when a protection unit decides to decline a protection request from the ma unit. This would indicate to the mam unit that it should no longer state that it is on protection. For all other cases on protection pair datal k 42 and m-band datalmk 40, this would indicate that a software or hardware failure has occurred. When switch requests differ over in-band datalink 40 from two units of transport interface 10, this may indicate the beginning of a switch request or a failure of a unit with transport interface 10. In the case where a switch request has 3ust begun, the switch status the message structure would differ for less than a predefined validation time out period so both units of transport interface 10 would be sourc g the same protection status. When the switch request exceeds the predefined validation time out period, then that would imply a failure of a unit withm transport interface 10. A failure of one unit to talk to another unit within transport interface 10 would be indicated by the protection pair status bit m the message structure of m-band datal k 40. When a receiving unit sees the protection pair status bit set on one of the conflicting messages, then it shall use that message as the true request. This provides a technique for determining when to use a ma unit's message over a protection unit's message. If a determination cannot be made based on the above criteria, then no switch shall occur and a failure message will be sent indicating that a software failure occurred and it cannot be isolated. When a status differs between units of a protection pair, it implies that a failure has occurred either on the backplane or on a device on one of the boards. This failure will be reported with, if possible, a determination where the failure is likely to have originated. In-band datalinks 40 also provides a local bus monitor function. The local bus monitor message is contained in the KI and K2 bytes of the third STS-1 signal in the STS-3 set. The local bus monitor is used by other units to determine if a card is present, failed, or absent. The sending unit sends out a recurring pattern, HEX55AA, which is sent on all m-band data links 40. When a receiving detects the pattern as absent, the hardware alerts the software of that fact. Another use for m-band datalinks 40 is in forwarding path maintenance signals from high speed units 12 to broadband interfaces 16 and SONET formatters 18. Under Bellcores specifications, a Remote Defect Indication (RDI-P) signal is required to be generated by path terminating equipment, such as broadband interfaces 16 and SONET formatters 18 on detection of one of the following defects - Loss of Signal (LOS) , Loss of Frame (LOF), Line Alarm Indication (AIS-L) , Loss of Pointer (LOP-P) , and Path Alarm Indication Signal (AIS-P) . LOS, LOF, and AIS-L defects are detected by line terminating equipment, such as high speed units 12. LOP-P and AIS-P defects are detected by path terminating equipment and also by line terminating equipment that contain STS payload pointer interpreters such as east and west high speed units 12. Line terminating equipment must immediately notify downstream path terminating equipment. Typically, defects are forwarded by generating downstream alarm indication signals (AIS-L or AIS-P) on dedicated hardware lines which take at least three 125 microsecond frames before the defect is detected. By using m-band datalinks 40, path maintenance signals containing the status of defects can be placed into consumed bytes of section overhead 32 or line overhead 34 and decoded without the delay normally associated with downstream detection. Table 5 shows an example of path maintenance signal placement withm the B2 byte of line overhead 34. Bit 8 holds the AIS-P defect information for passing to path processmg units. Upon AIS-P detection, an all-ones pattern is generated in the appropriate STS payload pointer bytes and all appropriate SPE bytes are overwritten with all-ones. Bit 7 holds the LOP-P defect. Bit 6 holds elastic store overruns forwarded to downstream path processmg units. Bit 5 holds a Line Failure signal that is a result of logically ORing the LOS, LOF, and AIS-L defects. The notification of these defects to downstream path terminating equipment provides for the generation of the RDI-P signal. Bit 4 holds an all-ones pointer to ensure that there is no more than one frame of delay m regenerating an all-ones pattern. TABLE 5. DEFECT NOTIFICATION MESSAGE 1 2 3 4 5 6 7 8 All-Is Line Elastic LOP-P Received Pointer Failure Store AIS-P Overrun In summary, in-band data links are created through the overhead signaling of a SONET structure between components in a transport interface. Proprietary protection datalinks are established between redundant protection pair components for fault isolation and avoidance purposes. Thus, it is apparent that there has been provided, in accordance with the present invention, a transport interface for performing protection switching of telecommunication traffic that satisfies the advantages set forth above. Although the present invention has been described in detail, it should be understood that various changes, substitutions, and alterations can be made herein. For example, though the present invention is discussed in terms of SONET formatters, and SONET frames and SONET structures, it may also apply to other types of protocols, including international protocol techniques. Other examples are readily ascertainable to those skilled in the art and may be made without departing from the spirit and scope of the present invention as defined by the following claims. APPENDIX 1 Overhead Byte Al, A2 Bl C l Dl, D2, D3 El Fl Definition and Usage Date Communication Framing Section Parity Section Trace Channel Order Wire User Bytes Bytes SONLT Begins each BIP-8, Bit Section Trace Section DCC 7 iΛcal Voice Optional SECTION STS-1 interleaved (Formerly layer OS I stack Channel for OVERHEAD parity even Section ID) using CMISE defined only SONET, Computed from message format for STS- 1 # 1 defined previous STS-N Used for of an STS-N only for after control, Signaling is STS-1 #1 scrambling monitor, alarm, undefined of an Placed in STS- 1 and other STS-N Ul only communication between Section terminating equipment Overhead B2 D4-D12 E2 H1, H2, H3 1. K2 ZI (SI ) Z2 (M2) Byte Definition Automatic and Usage Express Payload Protection Far End Line Line DCC Orderwire Pointer Switching Synch Block Error Parity Status SONET Line BIP- Line DCC Optional H1 & H2 Provides Used for Used for LINE 8 Line 7 layer OSI Express point to the Automatic synchromza STS-3C OVERHE error stack using orderwire start of the Protection tion status and AD momtoπn CMISE between line SPE. H3 Switching messages STS- 12c in each message equipments used for (APS) (Bits 5-8) FEBE for STS-1 of format for Defined only pointer signaling B-ISDN an OAM&P for STS- 1 »1 justification between line STS-N between of an STS-N level entities Calculate line Defined only d from all terminating for STS- 1 #1 line equipments of an STS-N overhead Defined bytes and only for payload STS-1 #1 bytes of an STS-N Overhead B3 C2 F2 GI H4 Jl Z3. Z4 75 Byte Definition and Usage Path Error Signal Path Multiffame Future Tandem Monitoring bel User Path Status Indicator Path Trace Growth Monitor Channel SONET BIP-8 Even One byte User One byte Multiframe 64 byte Growth Bits 1 -4 used PATH Panty used to commun used to pavload fixed length Byte for incoming OVER¬ identity ication indicate the indicator string to error HEAD the between status of the Currently verify monitoring constructi Path Far End used only for connection Bits 5-8 used on of the elements Terminating VT between as SPE Any Equipment structured path communicatio value Allows the payloads transmitting ns channel other than full duplex equipment "0" Path to be and path indicates monitored at receiving an either end or equipment equipped at any point condition along the Path

Claims: WHAT IS CLAIMED IS: 1. A transport interface for performing protection switching of telecommunications traffic, comprising: first and second high speed unit pairs operable to receive and transmit telecommunications traffic, the first and second high speed units coupled together by a first in- band datalink, each of the first and second high speed unit pairs being a main unit and a protection unit coupled by first and second protection pair datalinks, respectively; a broadband interface pair coupled to the first and second high speed unit pairs by second and third in-band datalinks, the broadband interface pair being a main unit and a protection unit coupled by a third protection pair datalink; a SONET formatter pair coupled to the first and second high speed unit pairs by fourth and fifth in-band datalinks, the SONET formatter pair being a main unit and a protection unit coupled by a fourth protection pair datalink, wherein each protection pair datalink carries a message to inform associated main and protection units when a protection switch is required, each protection pair datalink being implemented in time slots of a common control communications interface bus, and wherein each in- band datalink carries an associated message to inform each pair of required/requested protection switches, protection status, and associated processor operability, each in-band datalink being implemented in the telecommunications traffic . 2. The transport interface of Claim 1, wherein each in-band datalink is implemented in a line overhead of the telecommunications traffic. 3. The transport interface of Claim 2, wherein each in-band datalink is implemented in KI and K2 bytes of the line overhead. 4. The transport interface of Claim 1, wherein each protection pair datalink and each in-band datalink continuously sends its associated message until a respective new message is provisioned. 5. The transport interface of Claim 1, wherein each in-band datalink carries processor bits in its associated message, the processor bits alternating between a first state and a second state to indicate valid associated processor operability, wherein an associated processor is determined to be inoperable when the processor bits are not alternating between the first state and the second state. 6. The transport interface of Claim 5, wherein each main unit and protection unit samples its associated protection pair datalink and in-band datalink at a first clock rate, the protection bits alternating at half the first clock rate. 7. The transport interface of Claim 6, wherein associated messages on each protection pair datalink and each in-band datalink are valid after two consecutive identical samples are obtained by the main and protection units. 8. The transport interface of Claim 1, wherein each in-band datalink provides a local traffic bus monitor function to determine a presence or failure status of traffic busses between associated main and protection units through the associated messages, the associated messages including a recurring bit pattern transmitted by a sending main or protection unit that is monitored by a receiving main or protection unit, absence of the recurring bit pattern indicating a traffic bus failure between sending and receiving main and protection units. 9. The transport interface of Claim 8, wherein the recurring bit pattern is placed into KI and K2 bytes of a line overhead of the telecommunication traffic. 10. The transport interface of Claim 1, wherein each in-band datalink provides a defect notification function. 11. A method of performing protection switching of telecommunication traffic, comprising the steps of: generating a protection switch message indicating protection status and switch request information for the telecommunications traffic; placing the protection switch message in available overhead bytes of the telecommunications traffic; transporting the protection switch message within the telecommunications traffic. 12. The method of Claim 11, further comprising the step of: alternating processor validation bits within the protection switch message between a first state and a second state, the alternating processor validation bits indicating a valid operation of a processor associated with the processor validation bits. 13. The method of Claim 11, wherein the protection switch message is placed in KI and K2 bytes of line overhead of the telecommunications traffic. 14. The method of Claim 11, further comprising the step of : continuously transporting the protection switch message in the telecommunications traffic until a new protection switch message is generated. 15. The method of Claim 11, further comprising the step of : performing a protection switch in response to two consecutive protection switch messages containing a request for a protection switch.

Inventors: HOWSON R DOUGLAS JR, POTTER THOMAS A, ROBERTS MARTIN, HOWSON, R., DOUGLAS, JR., POTTER, THOMAS, A., ROBERTS, MARTIN
Applicants: DSC COMMUNICATIONS, DSC COMMUNICATIONS CORPORATION
Application year: 1997
Main classification: H04J3
IPC codes: H04J3, H04Q11