CA2129083A1 - Management interface method - Google Patents
Management interface methodInfo
- Publication number
- CA2129083A1 CA2129083A1 CA002129083A CA2129083A CA2129083A1 CA 2129083 A1 CA2129083 A1 CA 2129083A1 CA 002129083 A CA002129083 A CA 002129083A CA 2129083 A CA2129083 A CA 2129083A CA 2129083 A1 CA2129083 A1 CA 2129083A1
- Authority
- CA
- Canada
- Prior art keywords
- status
- message
- pvc
- pipe
- subset
- Prior art date
- Legal status (The legal status 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 status listed.)
- Abandoned
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F13/00—Interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units
- G06F13/38—Information transfer, e.g. on bus
- G06F13/382—Information transfer, e.g. on bus using universal interface adapter
- G06F13/387—Information transfer, e.g. on bus using universal interface adapter for adaptation of different data processing systems to different peripheral devices, e.g. protocol converters for incompatible systems, open system
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10—TECHNICAL SUBJECTS COVERED BY FORMER USPC
- Y10S—TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10S370/00—Multiplex communications
- Y10S370/901—Wide area network
- Y10S370/902—Packet switching
- Y10S370/903—Osi compliant network
- Y10S370/906—Fiber data distribution interface, FDDI
Abstract
A method of managing an interface to an internal message pipe, such as an FDDI bus, comprises sending a status enquiry message to request the status of each PVC
having a DCLI in a specified range, receiving a subset status message containing sequence exchange numbers corresponding to the last status message sent out, updating the contents of a station's PVC's in response to the received subset status message, and propagating PVC status changes between entities on the pipe.
having a DCLI in a specified range, receiving a subset status message containing sequence exchange numbers corresponding to the last status message sent out, updating the contents of a station's PVC's in response to the received subset status message, and propagating PVC status changes between entities on the pipe.
Description
~~ 2129083 BACKGROUND OF THE lNv~ lON
This invention relates to method of managing a communications interface, such as a frame relay interface.
Frame relay is a technology for access to wide area 5 networks. The frame relay protocol operates at a æublayer of the data link layer, which provides the m; n; mllm functionality needed to take advantage of the statistical properties of the communication. I~nlike preexisting protocol suites in use in general topology subnetworks, it also 10 performs relaying, and multiplexing at thiæ sublayer. Other data link layer functions are provided only in systems connected to the edges of the frame relay subnetwork.
Frame Relay presently uses ANSI T1.617 Annex D, or the very similar CCITT Q.933 Annex A protocol, to provide the 15 status signaling protocol requirements between Frame Relay devices.
The Newbridge Networks Corporation Mainstreet~ 36120 switch is a single unit frame switch, with ports providing the correct status signaling protocol to external devices.
20 In particular, it can include FRE (Frame Relay Engine) cards via a wiring hub known as a FASTbus. The FRE card is a multi-processor card with a 68340 general purpose control processor and two 68EC040 processors used for frame switching and I/O.
There is a need to provide status signaling between F~Es in addition to external Frame Relay devices.
Annex D cannot maintain the status of the required number of inter-FRE 36120 connections due to its close coupling with management frame size; elements which-describe the present signaling status of all connections on a link must fit inside of a single frame. Since the FASTBus is based on ~DDI technology and is therefore limited to a maximum frame size of 4500 octets, this also limits the nllr~r of information e~ements per frame.
Annex D also provides for an 'Asynchronous STATus' message frame, which allows a Frame Relay device to inform its connected device of a change in signaling status outside of the normal, regular interval poll and response messaging.
One management frame must be used for each connection's change of state. Unfortunately, a simultaneous change in the state of a link with multiple connections can result in hundreds of management frames being exchanged.
An object of the invention is to overcome this problem.
SUMMARY OF THE lN V~N l'lON
Accordingly the present invention provides a method of managing an interface to an internal message pipe interconnecting communications entities in a packetized co~lln;cations system wherein permanent virtual connections (PVCs) are established in said pipe, the method comprising sending from a transmitting entity a subset status enquiry message to request the status of each PVC in the pipe having a DCLI in a specified range, receiving a subset status message containing sequence exchange numbers corresponding to the last status message sent out, updating an entity's - 21290~3 PVC~s in response to said received subset status message, and propagating PVC status changes between the communicating entities on said pipe.
The interface may be a ~rame relay interface and the message pipe an FDDI bus, in which case the entities are frame relay engines, i.e. devices for implementing frame relay switching operations. The invention is also applicable to other protocols, such as ATM, for example.
In the preferred embodiment, the method is designed to minimize the time required to determine initial PVC status, the time required to propagate PVC status changes, the bandwidth utilized on the message pipe, and the processor overhead required to implement the method.
Each station on the pipe operates an instance of the method between itself and every other reachable station.
The method is a thus a modified version of the LMI and ANSI Annex D protocols which are used to propagate PVC
status information between frame relay network switching elements. These protocols also contain procedures which monitor the WAN link integrity between the switches. Since the FDP monitors the logical link integrity between stations on the message pipe, these procedures can be omitted. Once established, links are considered to be in service until the discovery Protocol declares the far end unreachable.
Until a target station is detected by the FDP (FASTbus Discovery Protocol), all PVC's connected to that station are considered inactive. Upon detection of a target station via 21290~3 the FDP, the station starts a link with that target station.
The protocol enters the initialization state at startup.
The protocol does not allow more than one outst~n~;ng message at any given time. After sending a message, a reæponse must be received or a time-out must occur before a subsequent message may be sent. Sequence numbers are used to ensure that responses to timed-out messages are ignored. A
meRsage will be ignored if the sequence exchange number of an ;n~o~;ng m~QAge doe~ not match the number transmitted in the last outgoing message.
The method in accordance with the invention operates over DLCI O, which is the st~n~rd sign~l;ng DLCI ~Data Link Connection Identifier).
BRIEF DESCRIPTION OF THE DRAWINGS
The invention will now ~e described in more detail, by way of example only, with reference to the accompanying drawings, in which:-Figure 1 shows one embodiment of a frame relay system in which the method according to the invention is implemented;
Figure 2 shows the format of a status enquiry message;
Figure 3 shows the DCLI range;
Figure 4 shows the format of the report status message;
and Figure 5 shows an asynch status report message.
21290X~
DESCRIPTION OF THE PREFERRED EMBODIMENTS
In Figure 1, the system comprises a wiring hub 1 comprising a dual FDDI ring 2 consisting of shielded twisted pair wires. Ring 2 implements the standard FDDI protocol.
Frame relay engine cards 3, mounted in the backplane of a Newbridge Network~ M~int~treet~ 36120 switch and performing a frame relay switching function are connected in the ring aæ shown. The wiring hub 1, by providing an FDDI lin~
between the FRE cards 3, thus permits e~r~n~ion of the Mainstreet~ 36120 switch.
When the system starts it immediately enters the initialization state. The purpose of this state is to learn the status of each PVC configured at the far end of the link. The procedures for this state will now be described.
First, the station sends a Subset Status Enquiry message to request the status of each PVC having its DLCI in the specified range. The range is chosen in such a way that the resulting Subset Status message will fit in a single FASTBus frame.
If a Subset Status message with the correct sequence numbers is not received within nTl seconds, the station re-transmits the Subset Status Enquiry message (after incrementing the sequence num~er). If the nT1 time-outs persist, the station continues transmitting Subset Status Enquiry messages for the same DLCI range indefinitely.
Upon receipt of a Subset Status message cont~; n; ng sequence exchange numbers corresponding to the last Subset Status Enquiry message sent, the station will parse the Subset Status message and update the status's of its PVC's accordingly.
The station then transmits a Subset Status Enquiry message for the next DLCI range which may be contained in a single FASTBus frame. The station continues transmitting Subset Status Enquiry messages until the complete range of DLCI's has been queried.
After the Subset Status message for the last DLCI range has been parsed the link enters the post-initialization state of the protocol.
In this ætate, the protocol propagates status changes to the far end of the link. This includes information about new and deleted PVC's. Periodic subset status polling is also performed at regular intervals for robustness. The procedures are as follows:
When a PVC is created or deleted or the status of an existing PVC changes (due to incoming Status messages or link failures on the WAN side of the connection) the station transmits an Asynch Status message to propagate the change to the target station.
If the sending station has not received an Asynch.
Status Ack message with the correct sequence number within nTlAck seconds it will re-transmit the Asynch Status message (after incrementing the appropriate sequence number). If the nT1 time-outs persist, the station will continue transmitting the Asynch Status message indefinitely.
Zl29o83 When a station receives an Asynch Status message, it transmits an Asynch Status Ack in response. The Asynch Status Ack contains a PVC status IE for any configured PVC~s that had their new bit set in the Asynch Status message.
S Upon receipt of an Asynch Status Ac~ message cont~;n;ng sequence exchange numbers corresponding to the last Asynch Status message sent, the station will parse any PVC status IE's that may be cont,ained in the message and it will consider the status change to have been propagated successfully.
Every nN1 nTlAck intervals the station sends a Subset Status Enquiry message to the far end of the FMI link.
No retransmission occurs if a Subset Status message with the correct sequence numbers is not received within nTlAck seconds.
Upon receipt of a Subset Status message cont~; n; ng sequence exchange numbers corresponding to the last Subset Status Enquiry message sent, the station parses the Subset Status message and updates the status's of its PVC's accordingly.
If the FDP detects that a target station has been removed from the bus, all PVC~s connected to that station are declared inactive and the the system ceases the transmission of messages to that station.
The message formats are based on the messages defined in ANSI T1.617 Annex D, and are described in more detail below. The message format was designed so that size of the PVC Status IE field is small.
The status enquiry message is shown in Figure 2 and comprises a Frame Control Byte, Dst MAC Address, Src MAC
(Media Access Control) Address, Protocol Id and FCS fields.
The Address field is the 3-~yte LAPF address format.
The Control, Protocol Discriminator, Call Reference and Message Type fields are as defined in Annex D referred to above. The Report Type IE field IE is as defined in Annex D.
The protocol uses only Subset Status messages, so the value of the Report Type is $03. The Sequence Exchange IE is also as defined in Annex D. The DLCI ~ange IE field is shown in more detail in Figure 3.
The format of the Status message is shown in Figure 4.
It also includes a Frame Control Byte, Dst MAC Address, Src MAC Address, Protocol Id and FCS. The Address field is the 3-~yte LAPF address format.
The Control, Protocol Discriminator, Call Reference and Message Type fields are as also as defined in Annex D. The ~eport Type IE is also as defined in Annex D. The protocol uses only Subset Status messages, so the value of the Report Type is $03.
The PVC Status IE is as defined in Annex D. One PVC
Status IE will be present for each PVC configured between the two stations. The Sequence Exchange IE is as defined in Annex D.
The format of the asynchronous Update Status message is shown in Figure 5. The Frame Control Byte, Dst MAC Address, Src MAC Address, Protocol Id and FCS fields are as~defined above. The Address field is the 3-byte LAPF address format.
S The Control, Protocol Discriminator, Call Reference and Message Type fields are as defined in Annex D. The Report Type IE is also as defined in Annex D. For an asynchronous Update_Status meS~ge~ the value of the Report Type 1S $02.
The Sequence ~h~nge IE is as defined in Annex D. The PVC Status IE is as defined in Annex D. One PVC Status IE
will be present for each PVC which has undergone a status change. Note that allowing multiple PVC Status IE's within an asynchronous Update Status message is a violation of the Annex D specification. However, the overhead associated with lS sending a single message for each PVC would be excessive.
The format of the Update Status Ack message is also as shown in Figure 4. The Frame Control Byte, Dst MAC Address, Src MAC Address, Protocol Id and FCS fields are as defined above. The Address field is the 3-byte LAPF address format.
The Control, Protocol Discriminator, Call Reference and Message Type fields are as defined in Annex D. The Report Type IE is as defined in Annex D. For an Update_Status_Ack message, the value of the Report Type is $82.
The Sequence Exchange IF is as defined in Annex D.
2S The PVC Status IE is as defined in Annex D. One PVC
Status IE is present for each PVC which had its new bit set in the corresponding Asynch Status message.
The following parameters are used by the method according to the invention:
nTl: length of time, in seconds, that a station will wait for a subset status message after sending a subset status S enquiry in the initialization state.
nTlAck: length of time, in seconds, that a station will wait for a response to a message in the post-initialization state.
nNl: the number of nTlAck intervals between Subset Status Requests in the post-initialization state.
. .
Distinct time-out values exist for each state to allow more tolerance during initialization.
The default values, which are user configurable, are as follows:
nT1: 5 seconds nTlAck: 1 second nNl: 20 In the method in accordance with the invention, a DLCI Range Information Element (IE) is provided so that frame size does not limit the number of connections supported; and eac~
message is with respect to a range of connections with several messages providing coverage of the full range. Also, more than one Asynchronous STATus IE is pac~ed into each Asynchronous STATus message.
This invention relates to method of managing a communications interface, such as a frame relay interface.
Frame relay is a technology for access to wide area 5 networks. The frame relay protocol operates at a æublayer of the data link layer, which provides the m; n; mllm functionality needed to take advantage of the statistical properties of the communication. I~nlike preexisting protocol suites in use in general topology subnetworks, it also 10 performs relaying, and multiplexing at thiæ sublayer. Other data link layer functions are provided only in systems connected to the edges of the frame relay subnetwork.
Frame Relay presently uses ANSI T1.617 Annex D, or the very similar CCITT Q.933 Annex A protocol, to provide the 15 status signaling protocol requirements between Frame Relay devices.
The Newbridge Networks Corporation Mainstreet~ 36120 switch is a single unit frame switch, with ports providing the correct status signaling protocol to external devices.
20 In particular, it can include FRE (Frame Relay Engine) cards via a wiring hub known as a FASTbus. The FRE card is a multi-processor card with a 68340 general purpose control processor and two 68EC040 processors used for frame switching and I/O.
There is a need to provide status signaling between F~Es in addition to external Frame Relay devices.
Annex D cannot maintain the status of the required number of inter-FRE 36120 connections due to its close coupling with management frame size; elements which-describe the present signaling status of all connections on a link must fit inside of a single frame. Since the FASTBus is based on ~DDI technology and is therefore limited to a maximum frame size of 4500 octets, this also limits the nllr~r of information e~ements per frame.
Annex D also provides for an 'Asynchronous STATus' message frame, which allows a Frame Relay device to inform its connected device of a change in signaling status outside of the normal, regular interval poll and response messaging.
One management frame must be used for each connection's change of state. Unfortunately, a simultaneous change in the state of a link with multiple connections can result in hundreds of management frames being exchanged.
An object of the invention is to overcome this problem.
SUMMARY OF THE lN V~N l'lON
Accordingly the present invention provides a method of managing an interface to an internal message pipe interconnecting communications entities in a packetized co~lln;cations system wherein permanent virtual connections (PVCs) are established in said pipe, the method comprising sending from a transmitting entity a subset status enquiry message to request the status of each PVC in the pipe having a DCLI in a specified range, receiving a subset status message containing sequence exchange numbers corresponding to the last status message sent out, updating an entity's - 21290~3 PVC~s in response to said received subset status message, and propagating PVC status changes between the communicating entities on said pipe.
The interface may be a ~rame relay interface and the message pipe an FDDI bus, in which case the entities are frame relay engines, i.e. devices for implementing frame relay switching operations. The invention is also applicable to other protocols, such as ATM, for example.
In the preferred embodiment, the method is designed to minimize the time required to determine initial PVC status, the time required to propagate PVC status changes, the bandwidth utilized on the message pipe, and the processor overhead required to implement the method.
Each station on the pipe operates an instance of the method between itself and every other reachable station.
The method is a thus a modified version of the LMI and ANSI Annex D protocols which are used to propagate PVC
status information between frame relay network switching elements. These protocols also contain procedures which monitor the WAN link integrity between the switches. Since the FDP monitors the logical link integrity between stations on the message pipe, these procedures can be omitted. Once established, links are considered to be in service until the discovery Protocol declares the far end unreachable.
Until a target station is detected by the FDP (FASTbus Discovery Protocol), all PVC's connected to that station are considered inactive. Upon detection of a target station via 21290~3 the FDP, the station starts a link with that target station.
The protocol enters the initialization state at startup.
The protocol does not allow more than one outst~n~;ng message at any given time. After sending a message, a reæponse must be received or a time-out must occur before a subsequent message may be sent. Sequence numbers are used to ensure that responses to timed-out messages are ignored. A
meRsage will be ignored if the sequence exchange number of an ;n~o~;ng m~QAge doe~ not match the number transmitted in the last outgoing message.
The method in accordance with the invention operates over DLCI O, which is the st~n~rd sign~l;ng DLCI ~Data Link Connection Identifier).
BRIEF DESCRIPTION OF THE DRAWINGS
The invention will now ~e described in more detail, by way of example only, with reference to the accompanying drawings, in which:-Figure 1 shows one embodiment of a frame relay system in which the method according to the invention is implemented;
Figure 2 shows the format of a status enquiry message;
Figure 3 shows the DCLI range;
Figure 4 shows the format of the report status message;
and Figure 5 shows an asynch status report message.
21290X~
DESCRIPTION OF THE PREFERRED EMBODIMENTS
In Figure 1, the system comprises a wiring hub 1 comprising a dual FDDI ring 2 consisting of shielded twisted pair wires. Ring 2 implements the standard FDDI protocol.
Frame relay engine cards 3, mounted in the backplane of a Newbridge Network~ M~int~treet~ 36120 switch and performing a frame relay switching function are connected in the ring aæ shown. The wiring hub 1, by providing an FDDI lin~
between the FRE cards 3, thus permits e~r~n~ion of the Mainstreet~ 36120 switch.
When the system starts it immediately enters the initialization state. The purpose of this state is to learn the status of each PVC configured at the far end of the link. The procedures for this state will now be described.
First, the station sends a Subset Status Enquiry message to request the status of each PVC having its DLCI in the specified range. The range is chosen in such a way that the resulting Subset Status message will fit in a single FASTBus frame.
If a Subset Status message with the correct sequence numbers is not received within nTl seconds, the station re-transmits the Subset Status Enquiry message (after incrementing the sequence num~er). If the nT1 time-outs persist, the station continues transmitting Subset Status Enquiry messages for the same DLCI range indefinitely.
Upon receipt of a Subset Status message cont~; n; ng sequence exchange numbers corresponding to the last Subset Status Enquiry message sent, the station will parse the Subset Status message and update the status's of its PVC's accordingly.
The station then transmits a Subset Status Enquiry message for the next DLCI range which may be contained in a single FASTBus frame. The station continues transmitting Subset Status Enquiry messages until the complete range of DLCI's has been queried.
After the Subset Status message for the last DLCI range has been parsed the link enters the post-initialization state of the protocol.
In this ætate, the protocol propagates status changes to the far end of the link. This includes information about new and deleted PVC's. Periodic subset status polling is also performed at regular intervals for robustness. The procedures are as follows:
When a PVC is created or deleted or the status of an existing PVC changes (due to incoming Status messages or link failures on the WAN side of the connection) the station transmits an Asynch Status message to propagate the change to the target station.
If the sending station has not received an Asynch.
Status Ack message with the correct sequence number within nTlAck seconds it will re-transmit the Asynch Status message (after incrementing the appropriate sequence number). If the nT1 time-outs persist, the station will continue transmitting the Asynch Status message indefinitely.
Zl29o83 When a station receives an Asynch Status message, it transmits an Asynch Status Ack in response. The Asynch Status Ack contains a PVC status IE for any configured PVC~s that had their new bit set in the Asynch Status message.
S Upon receipt of an Asynch Status Ac~ message cont~;n;ng sequence exchange numbers corresponding to the last Asynch Status message sent, the station will parse any PVC status IE's that may be cont,ained in the message and it will consider the status change to have been propagated successfully.
Every nN1 nTlAck intervals the station sends a Subset Status Enquiry message to the far end of the FMI link.
No retransmission occurs if a Subset Status message with the correct sequence numbers is not received within nTlAck seconds.
Upon receipt of a Subset Status message cont~; n; ng sequence exchange numbers corresponding to the last Subset Status Enquiry message sent, the station parses the Subset Status message and updates the status's of its PVC's accordingly.
If the FDP detects that a target station has been removed from the bus, all PVC~s connected to that station are declared inactive and the the system ceases the transmission of messages to that station.
The message formats are based on the messages defined in ANSI T1.617 Annex D, and are described in more detail below. The message format was designed so that size of the PVC Status IE field is small.
The status enquiry message is shown in Figure 2 and comprises a Frame Control Byte, Dst MAC Address, Src MAC
(Media Access Control) Address, Protocol Id and FCS fields.
The Address field is the 3-~yte LAPF address format.
The Control, Protocol Discriminator, Call Reference and Message Type fields are as defined in Annex D referred to above. The Report Type IE field IE is as defined in Annex D.
The protocol uses only Subset Status messages, so the value of the Report Type is $03. The Sequence Exchange IE is also as defined in Annex D. The DLCI ~ange IE field is shown in more detail in Figure 3.
The format of the Status message is shown in Figure 4.
It also includes a Frame Control Byte, Dst MAC Address, Src MAC Address, Protocol Id and FCS. The Address field is the 3-~yte LAPF address format.
The Control, Protocol Discriminator, Call Reference and Message Type fields are as also as defined in Annex D. The ~eport Type IE is also as defined in Annex D. The protocol uses only Subset Status messages, so the value of the Report Type is $03.
The PVC Status IE is as defined in Annex D. One PVC
Status IE will be present for each PVC configured between the two stations. The Sequence Exchange IE is as defined in Annex D.
The format of the asynchronous Update Status message is shown in Figure 5. The Frame Control Byte, Dst MAC Address, Src MAC Address, Protocol Id and FCS fields are as~defined above. The Address field is the 3-byte LAPF address format.
S The Control, Protocol Discriminator, Call Reference and Message Type fields are as defined in Annex D. The Report Type IE is also as defined in Annex D. For an asynchronous Update_Status meS~ge~ the value of the Report Type 1S $02.
The Sequence ~h~nge IE is as defined in Annex D. The PVC Status IE is as defined in Annex D. One PVC Status IE
will be present for each PVC which has undergone a status change. Note that allowing multiple PVC Status IE's within an asynchronous Update Status message is a violation of the Annex D specification. However, the overhead associated with lS sending a single message for each PVC would be excessive.
The format of the Update Status Ack message is also as shown in Figure 4. The Frame Control Byte, Dst MAC Address, Src MAC Address, Protocol Id and FCS fields are as defined above. The Address field is the 3-byte LAPF address format.
The Control, Protocol Discriminator, Call Reference and Message Type fields are as defined in Annex D. The Report Type IE is as defined in Annex D. For an Update_Status_Ack message, the value of the Report Type is $82.
The Sequence Exchange IF is as defined in Annex D.
2S The PVC Status IE is as defined in Annex D. One PVC
Status IE is present for each PVC which had its new bit set in the corresponding Asynch Status message.
The following parameters are used by the method according to the invention:
nTl: length of time, in seconds, that a station will wait for a subset status message after sending a subset status S enquiry in the initialization state.
nTlAck: length of time, in seconds, that a station will wait for a response to a message in the post-initialization state.
nNl: the number of nTlAck intervals between Subset Status Requests in the post-initialization state.
. .
Distinct time-out values exist for each state to allow more tolerance during initialization.
The default values, which are user configurable, are as follows:
nT1: 5 seconds nTlAck: 1 second nNl: 20 In the method in accordance with the invention, a DLCI Range Information Element (IE) is provided so that frame size does not limit the number of connections supported; and eac~
message is with respect to a range of connections with several messages providing coverage of the full range. Also, more than one Asynchronous STATus IE is pac~ed into each Asynchronous STATus message.
Claims (7)
1. A method of managing an interface to an internal message pipe interconnecting communications entities in a packetized communications system wherein permanent virtual connections (PVCs) are established in said message pipe, said method comprising sending from a transmitting entity a subset status enquiry message to request the status of each PVC in the pipe having a DCLI in a specified range, receiving a subset status message containing sequence exchange numbers corresponding to the last status message sent out, updating an entity's PVC's in response to said received subset status message, and propagating PVC status changes between the communicating entities on said pipe.
2. A method as claimed in claim 1, wherein said entities are frame relay engines.
3. A method as claimed in claim 2, wherein said pipe is an FDDI bus.
4. A method as claimed in claim 1, wherein said pipe is an ATM bus.
5. A method as claimed in claim 1, wherein said enquiry messages are sent over a DCLI 0 link.
6. A method as claimed in claim 1, wherein more than one Asynchronous status IE is packed into each Asynchronous status message.
7. A method as claimed in claim 1, wherein lost asynch status updates are recovered from update status acknowledge messages.
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US08/278,492 US5539734A (en) | 1994-07-21 | 1994-07-21 | Method of maintaining PVC status packetized communication system |
CA002129083A CA2129083A1 (en) | 1994-07-21 | 1994-07-28 | Management interface method |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US08/278,492 US5539734A (en) | 1994-07-21 | 1994-07-21 | Method of maintaining PVC status packetized communication system |
CA002129083A CA2129083A1 (en) | 1994-07-21 | 1994-07-28 | Management interface method |
Publications (1)
Publication Number | Publication Date |
---|---|
CA2129083A1 true CA2129083A1 (en) | 1996-01-29 |
Family
ID=25677401
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CA002129083A Abandoned CA2129083A1 (en) | 1994-07-21 | 1994-07-28 | Management interface method |
Country Status (2)
Country | Link |
---|---|
US (1) | US5539734A (en) |
CA (1) | CA2129083A1 (en) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
DE19713036B4 (en) * | 1996-03-29 | 2006-11-30 | Mitel Knowledge Corp., Kanata | Integrated telephone and data network |
Families Citing this family (56)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5758257A (en) | 1994-11-29 | 1998-05-26 | Herz; Frederick | System and method for scheduling broadcast of and access to video programs and other data using customer profiles |
US6460036B1 (en) | 1994-11-29 | 2002-10-01 | Pinpoint Incorporated | System and method for providing customized electronic newspapers and target advertisements |
US6515968B1 (en) | 1995-03-17 | 2003-02-04 | Worldcom, Inc. | Integrated interface for real time web based viewing of telecommunications network call traffic |
US6097718A (en) | 1996-01-02 | 2000-08-01 | Cisco Technology, Inc. | Snapshot routing with route aging |
US6147996A (en) | 1995-08-04 | 2000-11-14 | Cisco Technology, Inc. | Pipelined multiple issue packet switch |
US6182224B1 (en) | 1995-09-29 | 2001-01-30 | Cisco Systems, Inc. | Enhanced network services using a subnetwork of communicating processors |
GB9603582D0 (en) | 1996-02-20 | 1996-04-17 | Hewlett Packard Co | Method of accessing service resource items that are for use in a telecommunications system |
US6091725A (en) | 1995-12-29 | 2000-07-18 | Cisco Systems, Inc. | Method for traffic management, traffic prioritization, access control, and packet forwarding in a datagram computer network |
US6859783B2 (en) | 1995-12-29 | 2005-02-22 | Worldcom, Inc. | Integrated interface for web based customer care and trouble management |
US6035105A (en) | 1996-01-02 | 2000-03-07 | Cisco Technology, Inc. | Multiple VLAN architecture system |
US6308148B1 (en) | 1996-05-28 | 2001-10-23 | Cisco Technology, Inc. | Network flow data export |
US6243667B1 (en) | 1996-05-28 | 2001-06-05 | Cisco Systems, Inc. | Network flow switching and flow data export |
US6212182B1 (en) | 1996-06-27 | 2001-04-03 | Cisco Technology, Inc. | Combined unicast and multicast scheduling |
US6434120B1 (en) | 1998-08-25 | 2002-08-13 | Cisco Technology, Inc. | Autosensing LMI protocols in frame relay networks |
US6463477B1 (en) * | 1996-09-27 | 2002-10-08 | Mci Communications Corporation | Detection of presence of multiprotocol encapsulation in a data packet |
US6304546B1 (en) | 1996-12-19 | 2001-10-16 | Cisco Technology, Inc. | End-to-end bidirectional keep-alive using virtual circuits |
US6356530B1 (en) | 1997-05-23 | 2002-03-12 | Cisco Technology, Inc. | Next hop selection in ATM networks |
US6122272A (en) | 1997-05-23 | 2000-09-19 | Cisco Technology, Inc. | Call size feedback on PNNI operation |
US6862284B1 (en) | 1997-06-17 | 2005-03-01 | Cisco Technology, Inc. | Format for automatic generation of unique ATM addresses used for PNNI |
US6078590A (en) | 1997-07-14 | 2000-06-20 | Cisco Technology, Inc. | Hierarchical routing knowledge for multicast packet routing |
US6055364A (en) * | 1997-07-31 | 2000-04-25 | Cisco Technology, Inc. | Content-based filtering of multicast information |
US6330599B1 (en) | 1997-08-05 | 2001-12-11 | Cisco Technology, Inc. | Virtual interfaces with dynamic binding |
US6157641A (en) | 1997-08-22 | 2000-12-05 | Cisco Technology, Inc. | Multiprotocol packet recognition and switching |
US6512766B2 (en) | 1997-08-22 | 2003-01-28 | Cisco Systems, Inc. | Enhanced internet packet routing lookup |
US6212183B1 (en) | 1997-08-22 | 2001-04-03 | Cisco Technology, Inc. | Multiple parallel packet routing lookup |
US6473407B1 (en) | 1997-09-05 | 2002-10-29 | Worldcom, Inc. | Integrated proxy interface for web based alarm management tools |
US6745229B1 (en) | 1997-09-26 | 2004-06-01 | Worldcom, Inc. | Web based integrated customer interface for invoice reporting |
US6574661B1 (en) * | 1997-09-26 | 2003-06-03 | Mci Communications Corporation | Integrated proxy interface for web based telecommunication toll-free network management using a network manager for downloading a call routing tree to client |
US6714979B1 (en) | 1997-09-26 | 2004-03-30 | Worldcom, Inc. | Data warehousing infrastructure for web based reporting tool |
US7225249B1 (en) | 1997-09-26 | 2007-05-29 | Mci, Llc | Integrated systems for providing communications network management services and interactive generating invoice documents |
US6763376B1 (en) | 1997-09-26 | 2004-07-13 | Mci Communications Corporation | Integrated customer interface system for communications network management |
US7058600B1 (en) * | 1997-09-26 | 2006-06-06 | Mci, Inc. | Integrated proxy interface for web based data management reports |
US6343072B1 (en) | 1997-10-01 | 2002-01-29 | Cisco Technology, Inc. | Single-chip architecture for shared-memory router |
US6144669A (en) * | 1997-12-12 | 2000-11-07 | Newbridge Networks Corporation | Prioritized PVC management queues for improved frame processing capabilities |
US6111877A (en) | 1997-12-31 | 2000-08-29 | Cisco Technology, Inc. | Load sharing across flows |
US6263016B1 (en) | 1998-02-04 | 2001-07-17 | 3Com Corporation | Methods for interfacing a subscriber link to digital networks |
US6151336A (en) * | 1998-02-11 | 2000-11-21 | Sorrento Networks, Inc. | Time division multiplexing expansion subsystem |
US6400478B1 (en) | 1998-04-02 | 2002-06-04 | Sorrento Networks, Inc. | Wavelength-division-multiplexed optical transmission system with expanded bidirectional transmission capacity over a single fiber |
US6278708B1 (en) * | 1998-04-10 | 2001-08-21 | Cisco Technology, Inc. | Frame relay access device with user-configurable virtual circuit bundling |
US6292495B1 (en) * | 1998-04-10 | 2001-09-18 | Cisco Technology, Inc. | Segmented permanent virtual circuits |
US6298103B1 (en) | 1998-06-16 | 2001-10-02 | Sorrento Networks Corporation | Flexible clock and data recovery module for a DWDM optical communication system with multiple clock rates |
US6370121B1 (en) | 1998-06-29 | 2002-04-09 | Cisco Technology, Inc. | Method and system for shortcut trunking of LAN bridges |
US6377577B1 (en) | 1998-06-30 | 2002-04-23 | Cisco Technology, Inc. | Access control list processing in hardware |
US6363051B1 (en) * | 1998-06-30 | 2002-03-26 | At&T Corp. | Method and apparatus for achieving fast reconnection of permanent virtal channels in a frame relay network |
US6182147B1 (en) | 1998-07-31 | 2001-01-30 | Cisco Technology, Inc. | Multicast group routing using unidirectional links |
US6308219B1 (en) | 1998-07-31 | 2001-10-23 | Cisco Technology, Inc. | Routing table lookup implemented using M-trie having nodes duplicated in multiple memory banks |
US6389506B1 (en) | 1998-08-07 | 2002-05-14 | Cisco Technology, Inc. | Block mask ternary cam |
US6101115A (en) | 1998-08-07 | 2000-08-08 | Cisco Technology, Inc. | CAM match line precharge |
US6771642B1 (en) | 1999-01-08 | 2004-08-03 | Cisco Technology, Inc. | Method and apparatus for scheduling packets in a packet switch |
US6757791B1 (en) | 1999-03-30 | 2004-06-29 | Cisco Technology, Inc. | Method and apparatus for reordering packet data units in storage queues for reading and writing memory |
US6603772B1 (en) | 1999-03-31 | 2003-08-05 | Cisco Technology, Inc. | Multicast routing with multicast virtual output queues and shortest queue first allocation |
US6760331B1 (en) | 1999-03-31 | 2004-07-06 | Cisco Technology, Inc. | Multicast routing with nearest queue first allocation and dynamic and static vector quantization |
US6785239B1 (en) | 1999-06-01 | 2004-08-31 | Cisco Technology, Inc. | Reducing delays in a communication network using a re-fragmentation pipeline |
US7801021B1 (en) * | 2002-07-01 | 2010-09-21 | Cisco Technology, Inc. | Generic routing encapsulation tunnel keepalives |
EP1608112B1 (en) * | 2004-06-14 | 2011-02-23 | Broadcom Corporation | Differential delay compensation and measurement in bonded systems |
US8238538B2 (en) | 2009-05-28 | 2012-08-07 | Comcast Cable Communications, Llc | Stateful home phone service |
-
1994
- 1994-07-21 US US08/278,492 patent/US5539734A/en not_active Expired - Fee Related
- 1994-07-28 CA CA002129083A patent/CA2129083A1/en not_active Abandoned
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
DE19713036B4 (en) * | 1996-03-29 | 2006-11-30 | Mitel Knowledge Corp., Kanata | Integrated telephone and data network |
Also Published As
Publication number | Publication date |
---|---|
US5539734A (en) | 1996-07-23 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US5539734A (en) | Method of maintaining PVC status packetized communication system | |
US5553075A (en) | Packet data protocol for wireless communication | |
CA2216110A1 (en) | Lan bridging redundancy | |
US5285199A (en) | Method and apparatus for in-band data transmission | |
JP2960818B2 (en) | Processor reset method | |
Cisco | X.25 Configuration and Management | |
Cisco | D4 Carrier Cisco 90i - IDSL Channel Unit (Practice) | |
Cisco | D4 Carrier Cisco 90i - IDSL Channel Unit (Practice) | |
Cisco | Configuring X.25 and X.3 | |
Cisco | X.25 Configuration and Management | |
Cisco | X.25 Configuration and Management | |
Cisco | X.25 Configuration and Management | |
Cisco | X.25 Configuration and Management | |
Cisco | X.25 Configuration and Management | |
Cisco | X.25 Configuration and Management | |
Cisco | X.25 Configuration and Management | |
Cisco | X.25 Configuration and Management | |
Cisco | Interface Commands | |
Cisco | Interface Commands | |
US7088682B1 (en) | Reducing overhead when using loopback cells for fault detection in bi-directional virtual circuits | |
Cisco | X.25 Configuration and Management | |
Cisco | Interface Commands | |
Cisco | X.25 Configuration and Management | |
Cisco | Configuring X.25 and X.3 | |
KR100314582B1 (en) | Method of managing control messages for extending the number of subscriber boards of digital subscriber line access multiplexor |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
EEER | Examination request | ||
FZDE | Discontinued |