According to at least one embodiment of the invention, a protocol for managing redundant signaling links to form a reliable signaling connection is provided. The protocol has an initialization phase, in which the availability of signaling links is determined and an available signaling link is selected and activated, followed by an operational phase in which the activated link is used for sending signaling messages for a higher-level protocol. During the operational phase both links are monitored for availability using a query and reply technique. Should either link fail, a status message is sent to the remaining available link along with an activity switchover being performed, as required, depending on whether the failed link was the active link. The higher-level protocol process running on the media gateway performs management of the links, and the media gateway controller operates as a slave, whereby it need not initiate nor control any of the activities for management of the signaling links, thereby reducing the processing burden placed upon it. However, optionally, a media gateway controller may request a link switchover, which may be used to support link maintenance activities or link congestion avoidance measures.
|
16. A method comprising the steps of:
monitoring a plurality of links between a media gateway and a media gateway controller;
monitoring a first link of the plurality of the links by transmitting an internet control message protocol (icmp) echo request over the first link and over a second link;
waiting for an icmp reply message within a predetermined period of time on each of the first and second links;
determining a failure affecting the first link;
when no reply message is received on the first link, transmitting a status message on the second link to indicate a fault on the first link;
activating the second link of the plurality of the links; and
registering the second link for communication of call control signaling information by a higher level process.
26. A method comprising the steps of:
establishing communication between a media gateway and a media gateway controller over a first link of a plurality of links;
receiving at the media gateway a switchover request from the media gateway controller;
monitoring the first link by transmitting an internet control message protocol (icmp) echo request over the first link and over a second link;
waiting for an icmp reply message within a predetermined period of time on each of the first and second links;
when no reply message is received on the first link, transmitting a status message on the second link to indicate a fault on the first link;
activating the second link of the plurality of links; and
registering the second link for communication of call control signaling information by a higher level process.
1. A method comprising the steps of:
initializing a plurality of links between a media gateway and a media gateway controller;
activating a first link of the plurality of links;
registering the first link for communication of call control signaling information by a higher level process running on the media gateway, wherein the higher level process performs management of the links, while the media gateway controller operates as a slave to the media gateway;
monitoring the first link by transmitting an internet control message protocol (icmp) echo request over the first link and over a second link;
waiting for an icmp reply message within a predetermined period of time on each of the first and second links; and
when no reply message is received on the first link, transmitting a status message on the second link to indicate a fault on the first link.
34. A method comprising the steps of:
establishing communication between a media gateway and a media gateway controller over a first link of a plurality of links during an initialization phase;
monitoring the plurality of links between a media gateway and a media gateway controller during an operational phase including monitoring the first link by transmitting an internet control message protocol (icmp) echo request over the first link and over a second link;
waiting for an icmp reply message within a predetermined period of time on each of the first and second links;
when no reply message is received on the first link, transmitting a status message on the second link to indicate a fault on the first link;
determining a failure affecting the second link of the plurality of the links; and
transmitting a link status message regarding the failure affecting the second link from the media gateway to the media gateway controller.
2. The method of
determining whether each of the plurality of links is available for use.
4. The method of
transmitting a link activation message for the first link; and
receiving a link activation acknowledgement message for the first link.
5. The method of
transmitting a service change message; and
receiving a service change reply message.
6. The method of
7. The method of
8. The method of
9. The method of
10. The method of
12. The method of
13. The method of
14. The method of
registering the first link such that the higher level process considers the plurality of links to be a single signaling connection.
15. The method of
a more populous plurality of media gateways; and
a less populous plurality of media gateway controllers, wherein, for link management, the more populous plurality of media gateways exert control over the less populous plurality of media gateway controllers according to a lower-level process, and, for bearer traffic management, the less populous plurality of media gateway controllers exert control over the more populous plurality of media gateways according to the higher-level process.
17. The method of
19. The method of
transmitting a link activation message for the second link; and
receiving a link activation acknowledgement message for the second link.
20. The method of
transmitting a service change message; and
receiving a service change reply message.
21. The method of
22. The method of
23. The method of
24. The method of
25. The method of
27. The method of
transmitting a link activation message for the second link; and
receiving a link activation acknowledgement message for the second link.
28. The method of
transmitting a service change message; and
receiving a service change reply message.
29. The method of
30. The method of
31. The method of
32. The method of
33. The method of
35. The method of
sending H.248 signaling messages over the first link during the operational phase.
36. The method of
37. The method of
38. The method of
|
Applicant hereby claims the benefit under 35 U.S.C. 119(e) of U.S. provisional application No. 60/368,094, filed Mar. 27, 2002, entitled “Method and Apparatus for Redundant Signaling Links.”
The present invention relates generally to communication technologies and more particularly to call signaling technologies.
Multimedia communications systems typically include several components, for example, terminals, gateways, gatekeepers, multipoint controllers, multipoint processors, and multipoint control units. For proper operation, various components need to communicate reliably with various other components. A link is typically provided between a media gateway (MG) and its media gateway controller (MGC), which may be referred to as a call server, to allow communication between the MG and the MGC. Such a link carries signaling messages, for example, H.248 signaling messages complying with International Telecommunication Union Telecommunication Standardization Sector/Internet Engineering Task Force (ITU-T/IETF) Recommendation H.248, between an H.248 call control process in the MG and a call control process in the MGC. Such a link is typically configured as internet protocol (IP) over an asynchronous transfer mode (ATM) connection, for example, an ATM permanent virtual connection (PVC) and/or soft permanent virtual connection (SPVC). The H.248 signaling includes messages that are transported via the user datagram protocol (UDP). Each link is terminated at one end by a logical link termination in the MG and at the other end by an ATM network interface card installed in a signaling node of the MGC. The MGC may support large numbers (e.g., hundreds or thousands) of MGs and would therefore comprise several signaling nodes for this purpose.
One approach to H.248 signaling using the above signaling connection is for the MGC to select one link to an MG and to send H.248 messages over that link. The H.248 layer, which is a relatively high-level layer, is used to detect any message failures. The MGC has a threshold to which the count of failed messages would be compared, and when that threshold is crossed, the MGC starts using another link to the MG.
One problem with detecting message failures in the H.248 layer is that such detection occurs relatively slowly at the H.248 layer. Furthermore, in some cases the H.248 application at one end or the other, rather than faults on the signaling links, could cause the failures. Since the failure detection mechanism would not be able to distinguish these types of failures from link failures, recovery from them would occur even more slowly.
Other problems also complicate the development of a reliable signaling connection. For instance, the one-to-many relationship of the MGC to the MGs and the nature of H.248 signaling impose unique constraints on the signaling connection. Specifically, since the MGC may support hundreds of MGs, the resources of the MGC should be used as efficiently as possible. Therefore, the management of signaling connections to the MGs should require minimal MGC resources. Furthermore, sending duplicate messages on both links of a signaling connection to provide link redundancy, for example, as in 1+1 protection schemes, is not a viable option since it uses signaling node (SN) resources in the MGC inefficiently. Additionally, since H.248 signaling may be transported over an underlying protocol which is not guaranteed to be reliable, for example, UDP, there is not necessarily an assurance of end-end transmission as there might be with a reliable protocol, such as TCP. However, even a reliable protocol, such as TCP, can do nothing by itself to provide redundancy for reliable communication in the event that the underlying physical link were to fail.
Therefore, an efficient protocol to manage redundant links forming a reliable connection for signaling is needed.
According to at least one embodiment of the invention, a protocol for managing redundant signaling links to form a reliable signaling connection is provided. The protocol has an initialization phase, in which the availability of signaling links is determined and an available signaling link is selected and activated, followed by an operational phase in which the activated link is used for sending signaling messages for a higher-level protocol, for example, H.248 signaling messages. During the operational phase both links are monitored for availability using a query and reply technique, for example, Internet Control Message Protocol (ICMP) echo and reply messages. Should either link fail, a status message is sent to the remaining available link along with an activity switchover being performed, as required, depending on whether the failed link was the active link. The higher-level protocol process, for example, an H.248 call control process, running on the media gateway performs management of the links, and the media gateway controller operates as a slave, whereby it need not initiate nor control any of the activities for management of the signaling links, thereby reducing the processing burden placed upon it. However, optionally, a media gateway controller may request a link switchover, which may be used to support link maintenance activities or link congestion avoidance measures.
Embodiments of the present invention may be practiced with systems having asymmetric numbers of one type of device coupled to another type of device. For example, many (quite possibly hundreds or thousands) of MGs may be coupled to one or a small number of MGCs. Thus, embodiments of the invention may be practiced so as to minimize the processing burden placed on a device such as an MGC, thereby allowing maximal scaling of asymmetric numbers of devices coupled to one another. In accordance with at least one embodiment of the invention, responsibility for link management, which may, for example, include verification of link integrity and control of link redundancy is assigned to a more populous type of device (e.g., MGs), which can fulfill this responsibility using a lower-level process (e.g., ICMP echo and reply messages), while responsibility for control of bearer traffic (e.g., multimedia information) among devices of the more populous type of device can be assigned to one or more devices of the less populous type (e.g., MGCs). For example, an MGC may use H.248 signaling to control bearer traffic among multiple MGs. Such bearer traffic may include specific types of information, such as audio traffic, including voice traffic (which may include various grades of traffic, such as telephone-grade, broadcast-grade, high-fidelity grade, etc.), image traffic, such as video or motion-picture traffic and facsimile traffic, and may include multimedia forms of information that may, for example, include combinations of more than one type of information selected from the following types of information: audio, image, telemetry, data, control (including interactive control information), etc. While terms such as call server and call control can be readily understood in the context of signaling for voice telephone calls, the term “call” is not intended to imply limitation to voice traffic or other traffic traditionally carried over telephone lines, but can be understood to refer to a communication session established for the exchange of any type of bearer traffic.
Thus, while one or a relatively few number of devices of the less populous type can be used to control bearer traffic over a large number of devices of the more populous type, the devices of the less populous type do not need to bear the burden of controlling link management between the devices of the less populous type and the devices of the more populous type. Rather, the devices of the more populous type control the link management for links between themselves and their corresponding one or more devices of the less populous type. For the purposes of link management, the devices of the less populous type can simply reply to queries received from the devices of the more populous type without the need to initiate link management operations, wait for responses from other devices, determine the adequacy and/or timeliness of the responses, or determine what action should be taken in the presence or absence of timely responses.
Therefore, at least one embodiment of the invention provides a unique configuration wherein control at different levels is performed by different types of devices in a system comprising asymmetric numbers of these different types of devices. For link management, control is exerted in a many-over-few manner (e.g., many MGs exerting control over few MGCs) according to one or more lower-level process, while, for bearer traffic management, control is exerted in a few-over-many manner (e.g., few MGCs exerting control over many MGs) according to one or more higher-level processes. Thus, one unique attribute of at least one embodiment of the invention is that a device at one end of a signaling links, for example, a MG, is responsible for administrative functions relating to monitoring the status of the signaling links, allowing it provide redundant signaling capability, while a device at another end of the signaling links, for example, a MGC, is responsible for administrative functions relating to a higher level protocol, for example, H.248.
In media gateway 101, call control block 104 is selectably coupled to link A termination 105 or link B termination 106 via coupling 110. Link A termination 105 is coupled to signaling node A 107 via link A 111, which passes through network 103. Link B termination 106 is coupled to signaling node B 108 via link B 112, which passes through network 103. In media gateway controller 102, call control block 109 is selectably coupled to signaling node A 107 or signaling node B 108 via coupling 113. Link A 111 and link B 112 are preferably routed over physically diverse paths to minimize the likelihood that some stimulus adversely affecting (e.g., interrupting) communications along either of link A 111 or link B 112 will also adversely affect communications along the other of those links.
In step 209, a reply, such as an ICMP reply, is sent from signaling node A 107, which is represented by line 204, to link A termination 105, which is represented by line 202. In step 210, a reply, such as an ICMP reply, is sent from signaling node B 108, which is represented by line 205, to link B termination 106, which is represented by line 203. If a reply matching (e.g., having a sequence number corresponding to) the most recent query or a previous query (which need not be the query immediately preceding the most recent query, but may be an earlier query) is received over a link then the link is deemed available. Next, the first link deemed available is selected for activation. In the illustrated example, link A is selected for activation since the link A termination receives a reply before the link B termination does. In step 211, an activation message, preferably including a sequence number, is sent from link A termination 105, which is represented by line 202, to signaling node A 107, which is represented by line 204, and a timer is started. If an activation acknowledgement message matching (e.g., having a sequence number corresponding to) the activation message is received before the timer expires, then the link has been successfully activated. Otherwise, activation of the link has failed, and another link will be selected for activation if it is available. In step 212, an activation acknowledgement message is sent from signaling node A 107, which is represented by line 204, to link A termination 105, which is represented by line 202.
Upon successful activation of a link, the initialization phase is complete and the link is ready to be used for signaling by a higher-level process (e.g., a call control process in accordance with the H.248 protocol). In step 213, a service change message is sent from media gateway 101, which is represented by line 201, to media gateway controller 103, which is represented by line 206. In step 214, a service change reply is sent from media gateway controller 103, which is represented by line 206, to media gateway 101, which is represented by line 201. In this example, a service change message (preferably, an H.248 service change request) is sent, over Link A, from the call control process at the MG to the call control process at the MGC. Upon granting of the request by the call control process of the MGC, the MG is registered with the MGC, the confirmation of which is sent to the call control process of the MG in the form of a service change reply (preferably, an H.248 service change reply).
Several situations may occur during the operational phase of the links. Methods in accordance with embodiments of the invention are provided to accommodate such situations.
In step 309, a reply, such as an ICMP reply, is sent from signaling node B 108, which is represented by line 205, to link B termination 106, which is represented by line 203. In step 310, while link A termination 105 awaits a reply, such as an ICMP reply, from signaling node A 107, which is represented by line 204, such a reply is not received at link A termination 105 within a reasonable time. Thus, link A 111 is determined to be faulty.
In step 311, an activation message is sent from link B termination 106, which is represented by line 203, to signaling node B 108, which is represented by line 205. In step 315, routing tables for MGC 102 are updated, which may, for example, effectively result in coupling 113 being moved so as to couple signaling node B 108 to call control block 109. In step 312, an activation acknowledgement message is sent from signaling node B 108, which is represented by line 205, to link B termination 106, which is represented by line 203. In step 316, routing tables for MG 101 are updated, which may, for example, effectively result in coupling 110 being moved so as to couple link B termination 106 to call control block 104.
In step 313, a service change message is sent from media gateway 101, which is represented by line 201, to media gateway controller 103, which is represented by line 206. In step 314, a service change reply is sent from media gateway controller 103, which is represented by line 206, to media gateway 101, which is represented by line 201.
Thus, a failure on the active link (in this example, link A) is detected when a reply to a query is not received in a timely manner. That is, either no reply is received, or no reply matching (e.g., corresponding to the sequence number of) either the most recent query or a previous query (which need not be the query immediately preceding the most recent query, but may be an earlier query) is received. When this condition occurs, activity is switched to another link, which may be referred to as a standby link (in this example, link B), which is understood to be available according to the ongoing monitoring of the standby link via query and reply messages (e.g., ICMP echo and reply messages). An exchange of activation and activation acknowledgement messages between the link B termination 106 and the signaling node B 108 is used to activate the link. The newly active link, link B, is now ready to carry higher-level process messages (e.g., H.248 signaling messages), which may, for example, begin with a service change request to the media gateway controller.
At this point, the steps of the lower-level process for processing the switchover request have been completed, and the link is ready to carry higher-level process communications, for example, H.248 signaling messages, which preferably begin with an H.248 service change request and reply exchange between the call control processes in the media gateway and the media gateway controller. In step 410, a service change message is sent from media gateway 101, which is represented by line 201, to media gateway controller 103, which is represented by line 206. In step 411, a service change reply is sent from media gateway controller 103, which is represented by line 206, to media gateway 101, which is represented by line 201.
MONITOR LINK B 512 comprises steps 507 and 508. SEND LINK STATUS 513 comprises step 509. CONTINUE TO MONITOR LINKS 514 comprises steps 510 and 511.
Thus, at least one embodiment of the invention provides the ability to send a status message over the active link (e.g. link A) when the monitoring of the standby link (e.g. link B) detects that the standby link is no longer available. This condition can be detected in a manner described previously with reference
While several examples have been described in the context of two links (e.g., link A and link B), it should be understood that any number of links between a device of a more populous type and a device of a less populous type may be provided to further enhance redundancy. Regardless of the number of such links implemented, such links may be considered as a single signaling connection by a higher-level process. No more than one such link need be active at any time, thereby providing efficient use of signaling bandwidth available between the devices.
At least one embodiment of the invention minimizes overhead (both in terms of processing burden and communications bandwidth) used to provide link management capability for redundant signaling links. Much of the overhead can be limited to the initialization phase, with very minimal resources needed to perform continued monitoring of the links over time. Thus, redundant signaling links can be efficiently provided and utilized.
In accordance with one or more embodiments of the invention, MGs continue to send periodic queries to continue to monitor status of connections. For example, MGs set timers for each MGC and send queries when the timers elapse. If MGC had to perform these administrative functions, it would have to set timers for hundreds or thousands of MGs. The MGs are responsible for the administrative functions relating to monitoring the status of the signaling links. These functions include determining which MGCs to query, when to query them, over which signaling links to those MGCs the queries should be sent, how long to wait for a reply from the MGCs, what action is to be taken if a reply is or is not received within the designated period for the reply.
One or more embodiments of the invention may be used to communicate other signaling protocols over redundant links. For example, signaling protocols such as tone signaling, (integrated service digital network) ISDN, global system for mobile communications (GSM), or (signaling system #7) SS7 or successors thereto may be communicated. As an example of one context in which communication of signaling information of different signaling protocols is useful is signaling transport, which may be referred to as SigTran. For signaling transport of an ISDN D-channel, a MG can send ISDN D-channel signaling information to a MGC over a signaling link, and the MGC can send H.248 signaling information corresponding to ISDN B-channels over the signaling link, or in the event the signaling link is unavailable, over a second signaling link provided for redundancy.
Bearer traffic is preferably communicated over ATM connections (e.g., voice connections are preferably communicated as voice over ATM), while signaling messages are preferably communicated preferably H.248 over ATM or alternatively as H.248 over IP over ATM. Thus, one or more embodiments of the invention are able to provide greater efficiency for the communication of bearer traffic by communicating it over circuit-switched connections, while providing the flexibility to communicate signaling information over either circuit-switched connections or as packet-switched traffic over circuit-switched connections.
Technologies such as voice over IP (VoIP) and Voice over ATM are likely to become more prevalent as service providers move to converged networks. In accordance with one or more embodiments of the invention, the H.248 signaling protocol can be used to control call setup in such networks. The invention may be practiced so as to enable reliable H.248 signaling, the reliability of which will be a critical need for carrier-grade VoIP and Voice over ATM services.
While it would be possible to provide signaling links using protocols that provide some abilities to detect and accommodate link faults, such as IP or ATM SPVCs, reliance on such abilities can lead to slower response to link faults, allowing more disruption of communications over a longer period of time. Moreover, implementations of protocols that provide such abilities typically involve additional cost and complexity. Therefore, while embodiments of the present invention may be practiced in conjunction with such protocols, the ability of embodiments of the present invention to provide faster response to link faults and, consequently, less disruption of communications, as well as to avoid the need for additional cost and complexity, allows such embodiments to provide superior performance.
Accordingly, a method and apparatus for redundant call signaling has been described. It should be understood that the implementation of other variations and modifications of the invention in its various aspects will be apparent to those of ordinary skill in the art, and that the invention is not limited by the specific embodiments described. It is therefore contemplated to cover by the present invention, any and all modifications, variations, or equivalents that fall within the spirit and scope of the basic underlying principles disclosed and claimed herein.
Roberts, Michael, Vandette, Henri R., Alladi, Suryaram, Karlsen, Glenn Arne, Gettala, Balachandar S., Jhu, Michael, Hurd, Jim, Dubois, Gerry, Stanton, Jr., James A.
Patent | Priority | Assignee | Title |
Patent | Priority | Assignee | Title |
4071908, | Mar 17 1977 | Bell Telephone Laboratories, Incorporated | Adaptive polling technique |
5521902, | Dec 06 1993 | Agilent Technologies Inc | Location identification in a communications signalling network |
5844895, | Jun 30 1995 | Siemens Aktiengesellschaft | ATM communications network |
6614781, | Nov 20 1998 | Level 3 Communications, LLC | Voice over data telecommunications network architecture |
6650621, | Jun 28 1999 | FORCEPOINT FEDERAL HOLDINGS LLC; Forcepoint LLC | Load balancing routing algorithm based upon predefined criteria |
6674713, | Feb 23 1999 | Cisco Technology, Inc | Method and apparatus for providing continuous voice and call communications between a data network and a telephony network |
6680952, | Jun 01 1999 | Cisco Technology, Inc | Method and apparatus for backhaul of telecommunications signaling protocols over packet-switching networks |
6707820, | Dec 16 1999 | VENATA DECALGOMME | Virtual circuit network dynamic channel management |
6738343, | May 26 1999 | UNIFY, INC | System and method for utilizing direct user signaling to enhance fault tolerant H.323 systems |
6775373, | Jun 14 2001 | Ericsson Inc | System for and method of channel associated signaling backhaul in a routing system |
6839344, | Dec 19 2000 | RPX CLEARINGHOUSE LLC | Transport mechanism for ISDN backhaul over IP |
6859614, | Jun 24 1996 | SAMSUNG ELECTRONICS CO , LTD | Apparatus and method for controlling priority order of access to memory |
6882653, | May 22 2000 | GOOGLE LLC | Gateway system having controller and signal processor for interconnecting IP network and telephone network and method for controlling alternative routing at the time of fault of gateway system |
6992974, | Oct 10 2000 | HEWLETT-PACKARD DEVELOPMENT COMPANY, L P | System and method for providing fault tolerance in a network telephony system |
7007092, | Oct 05 2000 | Juniper Networks, Inc | Connection management system and method |
7023794, | Feb 11 2002 | NET2PHONE, INC | Method and architecture for redundant SS7 deployment in a voice over IP environment |
7055173, | Dec 19 1997 | Citrix Systems, Inc | Firewall pooling in a network flowswitch |
7065041, | Dec 14 2001 | NOKIA SIEMENS NETWORKS GMBH & CO KG | Method for resilient call setup through ATM networks for Softswitch applications |
7103002, | Jul 12 2000 | Telefonktiebolaget LM Ericsson (publ); TELEFONAKTIEBOLAGET L M ERICSSON PUBL | Communication management in networks having split control planes and user planes |
20010036173, | |||
20020009072, | |||
20020042828, | |||
20020141352, | |||
20020172188, | |||
20030145108, | |||
20050058061, | |||
20050132062, | |||
EP1109368, | |||
GB2355362, |
Executed on | Assignor | Assignee | Conveyance | Frame | Reel | Doc |
Mar 26 2003 | Alcatel Lucent | (assignment on the face of the patent) | / | |||
Jul 17 2003 | KARLSEN, GLENN ARNE | Alcatel | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 014632 | /0793 | |
Jul 18 2003 | ALLADI, SURYARAM | Alcatel | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 014632 | /0793 | |
Jul 22 2003 | JHU, MICHAEL | Alcatel | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 014632 | /0793 | |
Jul 22 2003 | ROBERTS, MICHAEL | Alcatel | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 014632 | /0793 | |
Jul 23 2003 | VANDETTE, HENRI R | Alcatel | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 014632 | /0793 | |
Jul 24 2003 | HURD, JIM | Alcatel | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 014632 | /0793 | |
Aug 12 2003 | DUBOIS, GERRY | Alcatel | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 014632 | /0793 | |
Aug 13 2003 | STANTON, JAMES A | Alcatel | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 014632 | /0793 | |
Aug 24 2003 | GETTALA, BALACHANDAR | Alcatel | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 014632 | /0793 | |
Nov 30 2006 | Alcatel | Alcatel Lucent | CHANGE OF NAME SEE DOCUMENT FOR DETAILS | 033549 | /0689 | |
Jan 30 2013 | Alcatel-Lucent Canada Inc | CREDIT SUISSE AG | SECURITY INTEREST SEE DOCUMENT FOR DETAILS | 029826 | /0927 | |
Aug 19 2014 | CREDIT SUISSE AG | Alcatel-Lucent Canada Inc | RELEASE OF SECURITY INTEREST | 033686 | /0798 | |
Jul 22 2017 | Alcatel Lucent | WSOU Investments, LLC | ASSIGNMENT OF ASSIGNORS INTEREST SEE DOCUMENT FOR DETAILS | 044000 | /0053 | |
Aug 22 2017 | WSOU Investments, LLC | OMEGA CREDIT OPPORTUNITIES MASTER FUND, LP | SECURITY INTEREST SEE DOCUMENT FOR DETAILS | 043966 | /0574 | |
May 16 2019 | OCO OPPORTUNITIES MASTER FUND, L P F K A OMEGA CREDIT OPPORTUNITIES MASTER FUND LP | WSOU Investments, LLC | RELEASE BY SECURED PARTY SEE DOCUMENT FOR DETAILS | 049246 | /0405 | |
May 16 2019 | WSOU Investments, LLC | BP FUNDING TRUST, SERIES SPL-VI | SECURITY INTEREST SEE DOCUMENT FOR DETAILS | 049235 | /0068 | |
May 28 2021 | TERRIER SSC, LLC | WSOU Investments, LLC | RELEASE BY SECURED PARTY SEE DOCUMENT FOR DETAILS | 056526 | /0093 | |
May 28 2021 | WSOU Investments, LLC | OT WSOU TERRIER HOLDINGS, LLC | SECURITY INTEREST SEE DOCUMENT FOR DETAILS | 056990 | /0081 |
Date | Maintenance Fee Events |
Nov 04 2019 | M1551: Payment of Maintenance Fee, 4th Year, Large Entity. |
Dec 25 2023 | REM: Maintenance Fee Reminder Mailed. |
Apr 29 2024 | M1552: Payment of Maintenance Fee, 8th Year, Large Entity. |
Apr 29 2024 | M1555: 7.5 yr surcharge - late pmt w/in 6 mo, Large Entity. |
Date | Maintenance Schedule |
May 03 2019 | 4 years fee payment window open |
Nov 03 2019 | 6 months grace period start (w surcharge) |
May 03 2020 | patent expiry (for year 4) |
May 03 2022 | 2 years to revive unintentionally abandoned end. (for year 4) |
May 03 2023 | 8 years fee payment window open |
Nov 03 2023 | 6 months grace period start (w surcharge) |
May 03 2024 | patent expiry (for year 8) |
May 03 2026 | 2 years to revive unintentionally abandoned end. (for year 8) |
May 03 2027 | 12 years fee payment window open |
Nov 03 2027 | 6 months grace period start (w surcharge) |
May 03 2028 | patent expiry (for year 12) |
May 03 2030 | 2 years to revive unintentionally abandoned end. (for year 12) |