US7483369B2

Method and apparatus for migrating to an alternate call controller

Summary by NHIP

Call State Migration Method

The method maintains call signaling information by storing generated call state files on a client endpoint. Upon losing the signaling channel, the client provides these stored files to a second call controller to restore features.

Claim Score by NHIP

Read claim 11, the broadest

Abstract

The present invention is directed to the maintenance of call signaling information in connection with realtime communications established using a packet data network. According to the present invention, call state information related to a realtime communication is provided by a call controller to an interconnected client. The client stores the call state information. In the event of a failure of a call signaling channel between the call controller and the client or in the event of a failure of the call controller, the client may establish contact with an alternate call controller, and may provide the call state information that has been stored on the client to the alternate call controller. The alternate call controller may then restore call features associated with the realtime communication.

US7483369B2, drawing sheet 1 — Sheet 1 of 4

Term

Term ended

Expired 3 January 2026, 0.7 years ago.

18 claims: 6 independent, 12 dependent

1
A method for maintaining call state information, comprising:generating in a first call controller first call state information;creating at least a first file containing a representation of at least some of said generated first call state information;providing said at least a first file to a first client;storing said at least a first file on said first client, wherein said first client is a communication endpoint participating in a call to which said first call state information pertains;establishing a call signaling channel between said first call controller and said first client;losing said call signaling channel;generating in said first client a request for service from a second call controller;and after losing said call signaling channel, providing said at least a first file from said first client to said second call controller.
5
A method for maintaining call state information, comprising:generating in a first call controller first call state information;creating at least a first file containing a representation of at least some of said generated first call state information;providing said at least a first file to a first client;storing said at least a first file on said first client, wherein said first client is a communication endpoint participating in a call to which said first call state information pertains;establishing a call signaling channel between said first call controller and said first client;losing said call signaling channel;generating in said first client a request for service from a second call controller;and providing said at least a first file from said first client to said second call controller, wherein said providing said at least a first file to said second call controller is performed after receiving at said first client a query from said second call controller for said at least a first file.
6
A system for providing redundant call state information, comprising:a first communication endpoint, including first data storage;a first call controller in communication with said first communication endpoint, wherein call state information is provided by said first call controller to said first communication endpoint, and wherein said call state information for a call between said first communication endpoint and another device is stored in at least said first data storage of said first communication endpoint;a second call controller in communication with said first communication endpoint, wherein said call state information is provided by said first communication endpoint to said second call controller after a failure of said first call controller.
11
Broadest claimClaim Score 77, broad(NHIP)A method for providing redundant signaling information, comprising:generating in a first call controller first call state information;providing said first call state information to a first communication endpoint;storing said first call state information on said first communication endpoint;and in response to a requirement to switch service from said first call controller to a second call controller, providing said first call state information from said first communication endpoint to said second call controller.
17
A method for providing redundant signaling information, comprising:generating in a first call controller first call state information;providing said first call state information to a first communication endpoint;storing said first call state information on said first communication endpoint;in response to a requirement to switch service from said first call controller to a second call controller, generating a request to said second call controller for service;and providing said first call state information from said first communication endpoint to said second call controller, wherein said providing said first call state information to said second call controller is performed in response to a request from said second call controller for call state information.
18
A system for providing redundant signaling information, comprising:first means for controlling features associated with a first communication channel;first communication client means, wherein said first communication client means is a communication endpoint;means for interconnecting said first means for controlling features associated with a first communication channel to said first communication client means;and means for storing in said first communication client means first communication channel state information related to said first communication channel, wherein said first communication channel state information related to said first communication channel is stored in said means for storing in said first communication client means, wherein said first communication channel state information is generated by said first means for controlling features associated with a first communication channel, and wherein said first communication channel interconnects said first communication client means to a second communication client means;second means for controlling features associated with a first communication channel, wherein in response to a loss of a call signaling channel between said first means for controlling features associated with a first communication channel and said first communication client means said first communication channel state information is provided from said first communication client means to said second means for controlling features associated with a first communication channel.

Independent claims6

25 paragraphs in 5 sections, as filed

FIELD OF THE INVENTION

0001The present invention is directed to realtime data transmission over a packet data network. In particular, the present invention is directed to maintaining call state information when migrating between call controllers by storing call state information on communication endpoints.

BACKGROUND OF THE INVENTION

0002Packet data networks are increasingly used for the exchange of realtime audio, video and data communications. Various protocols, including the H.323 protocol, require the establishment of a call signaling channel that is separate from the bearer channel. The call signaling channel is used to exchange signaling messages, such as call setup, tear down, address translation and messages related to billing.

0003In connection with realtime communications over packet data networks, or IP telephony, a signaling channel is usually established over the IP network between a client (such as media gateways and IP endpoints) and a call controller for basic call service and for various call feature support. Failure of the IP network or the call controller such that the call signaling channel is lost will lead to a service outage at the media gateway or IP endpoint. In order to prevent a loss of service under such circumstances, alternate call controllers are typically provided. However, when a media gateway or IP endpoint migrates to a new call controller, the existing calls (i.e., the bearer channels) may get torn down. Even if they are not torn down, it is likely that no call features will be available to the media gateway or IP endpoint, since the alternate call controller has no knowledge of the call state information associated with the calls. In particular, preservation of call features in addition to bearer connections requires that the alternate controller be supplied with call state information.

0004In order to provide call state information to an alternate controller, such information can be stored in a database that can be accessed by all primary and alternate call controllers. However, establishing a common, redundant database can be expensive. In addition, such databases can create a data bottleneck, especially when a large number of controllers are accessing the database. Furthermore, such a solution is not very robust, as network failures can prevent call controllers from accessing the common database.

0005Another approach to providing call state information to alternate call controllers dynamically updates available alternate call controllers with call state information. That is, as call state information is generated or updated, that information is provided to the alternate call controller or controllers that would be contacted by the client if the primary call controller were lost. However, this approach adds overhead and complexity, particularly as the number of call controllers available on a system increases. In addition, the alternate call controllers must be updated with call state information regarding all of the calls on the main controller. This can result in network congestion. In addition, the solution is not very robust, as network failures can prevent controllers from communicating with one another.

SUMMARY OF THE INVENTION

0006The present invention is directed to solving these and other problems and disadvantages of the prior art. According to the present invention, call state information is provided from the primary call controller to the client. The client stores the state information provided by the primary call controller. If the state of the call changes, updated call state information is provided to the client. In the event of a failure of the call controller or the signaling channel, the client may provide an alternate call controller with the call state information, thus allowing the alternate call controller to provide the call features that had been provided by the primary call controller. The state information need not be in a format that the client understands and processes.

0007In accordance with an embodiment of the present invention, the file containing the call state information may be provided to the alternate call controller in response to a query to the client made by the alternate call controller. In accordance with another embodiment of the invention, the file containing the call state information may be pushed from the client to the alternate call controller.

BRIEF DESCRIPTION OF THE DRAWINGS

<figref idref="DRAWINGS">FIG. 1</figref> depicts a realtime communication arrangement in accordance with an embodiment of the present invention;

<figref idref="DRAWINGS">FIG. 2</figref> depicts the relationship of clients and call controllers in accordance with an embodiment of the present invention; and

<figref idref="DRAWINGS">FIG. 3</figref> is a flow diagram illustrating the operation of a system in accordance with an embodiment of the present invention.

DETAILED DESCRIPTION

0011With reference now to <figref idref="DRAWINGS">FIG. 1</figref>, a realtime communication arrangement 100 in accordance with an embodiment of the present invention is illustrated. In general, the communication arrangement 100 involves a number of communication terminals 104a-n interconnected to one another by a communication network 108. As can be appreciated by one of skill in the art, the communication network 108 may form the communication channel between two or more communication terminals 104 in communication with one another. Furthermore, it should be appreciated that a portion or portions of the communication network 108 may comprise analog and/or switched circuit networks, such as the public switched telephone network (PSTN), and that at least a portion of the communication network 108 comprises an IP communication network. As can also be appreciated by one of skill in the art, where an Internet protocol (IP) communication network 108 comprises a portion of a communication link proximate to a communication terminal 104, such a communication terminal 104 may comprise an IP telephone, video phone or computer.

0012With reference now to <figref idref="DRAWINGS">FIG. 2</figref>, the relationships between various clients 204 and call controllers 208 associated with an IP protocol communication network 200 are illustrated. In particular, as shown in <figref idref="DRAWINGS">FIG. 2</figref>, the clients 204 are generally interconnected to the call controllers 208 through the IP protocol communication network 200. As can be appreciated by one of skill in the art, the IP protocol communication network 200 may comprise all or part of the communication network 108, and thus the arrangement depicted in <figref idref="DRAWINGS">FIG. 2</figref> may comprise all or a portion of the system 100 illustrated in <figref idref="DRAWINGS">FIG. 1</figref>. Communications between clients 204 across the IP protocol communication network 200 may be in accordance with various communication protocols, including the H.323 protocol.

0013The clients 204 may be of various types. For example, as illustrated in <figref idref="DRAWINGS">FIG. 2</figref>, clients 204 may comprise one or more gateways 212. In general, a client 204 comprising a gateway 212 provides for an interconnection between a communication endpoint 104 (or to a non-IP protocol network) that is not capable of direct interconnection to the IP protocol communication network 108. Furthermore, the connection between a gateway 212 and a non-IP protocol communication endpoint 104 may be made through a direct interconnection, such as may be established over a switched circuit network.

0014A client 204 may additionally or alternatively comprise a communication terminal 104 capable of directly interconnecting to the IP communication network, referred to herein as an Internet protocol (IP) communication endpoint 216. In general, an IP communication endpoint 216 is capable of direct interconnection to the IP protocol communication network 108. Accordingly, examples of IP communication endpoints 216 include IP telephones or video phones, implemented either as hardware (e.g., an IP telephone) or as software (e.g., a soft phone) running in connection with a general purpose computer, computers that are operable to provide real-time audio, video, and/or data communications, or any other data endpoint.

0015The call controllers 208 are network nodes that function to facilitate or enable communications between clients 204 of the IP protocol communication network 200 to which the controllers 208 and clients 204 are interconnected. In particular, the call controllers 208 maintain call state information. Examples of call state information includes SIP and H.323 call state information generated in connection with real-time communications over an IP protocol communication network 200. For instance, call state information may include call setup, tear down, address translation, and billing information. The call controllers 208 also function to control access to the IP protocol communication network 200. As can be appreciated by one of skill in the art, in a typical arrangement, a call controller 208 may function or be assigned as a primary call controller with respect to one or more clients 204. Alternatively or in addition, a call controller 208 can function as an alternate call controller for a number of communication endpoints 204.

0016With reference now to <figref idref="DRAWINGS">FIG. 3</figref>, the operation of a system in accordance with an embodiment of the present invention is illustrated. Initially, at step 300, a call signaling channel is established between a client 204 and a call controller 208. For example, a user associated with a first communication endpoint 104 comprising an IP communication endpoint 216 may request that a communication channel (i.e., a call) be established with a second communication endpoint 104. In connection with the request for a communication channel, the call signaling channel will be established between the client 204 and the call controller (e.g., first call controller 208a).

0017At step 304, a determination is made as to whether call state information is available. In general, call state information may comprise any information related to the communication channel itself, or to peripheral data associated with the communication channel. For example, call state information may identify the various endpoints associated with the communication channel, whether a communication endpoint 104 has been placed on hook, and call timer information. If no call state information is available, the system may idle at step 304. If call state information is available, a call state information file is generated using the most recent call state information (step 308). The call state information file is then sent to the client 204 (step 312). In general, the call state information file is sent to each client 204 that has established a call signaling channel with the call controller 208 and that is associated with the communication channel in connection with which the call state information has been generated. As can be appreciated by one of skill in the art, while a communication channel is being set up or established, call state information may exist that is not associated with an established communication channel. However, such information may be maintained in a call information file in accordance with the present invention, in order to facilitate establishment of a requested communication channel should the client 204 become disconnected from an assigned controller 208. As can also be appreciated by one of skill in the art, the call controller 208 may, in addition to providing a file containing call state information to the client 204, maintain call state information conventionally. Examples of such state information include coverage timers, forwarding status, login status, previous connections to other parties, override code used on the call, call park information. In general any feature related information to the user on the call is stored, as well as any call specific information on what happened to the call or is allowed to happen to the call.

0018At step 316, the call state information file is stored on the client 204. Accordingly, a copy of the call state information, as represented by the call state information file, is directly accessible to the client 204. However, it should be appreciated that the client 204 is not required to maintain any awareness of the format or contents of the call state information file.

0019At step 320, a determination is made as to whether updated call state information is available. If updated call state information is available, the system returns to step 308. If updated call state information is not available, a determination is made as to whether the call signaling channel between the client 204 and the call controller 208 has been terminated (step 324). If the call signaling channel has not been terminated, the system returns to step 320. If the call signaling channel has been terminated, a determination is next made as to whether the termination of that call signaling channel is valid (step 328). If the termination is determined to be valid, the procedure ends. An example of a valid termination is after the client 204 has gone on hook and the associated communication channel has been torn down.

0020If the termination of the call signaling channel was determined at step 328 to be invalid, an alternate call controller is selected (step 336). For example, the client 204 may select an alternate call controller 208 from a list of valid alternate call controllers 208 maintained on the client 204 or accessible to the client 204 over the IP protocol communication network 108. As can be appreciated by one of skill in the art, if the alternate call controller 208 that is initially selected is not available, a next call controller 208 may be selected. As a further example, the client 204 may broadcast a request for a call controller 208, and may select a responding call controller 208 as an alternate-call controller 208. At step 340, the client 204 contacts the alternate call controller 208. The call state information file is then passed from the client 204 to the alternate call controller 208 (step 344). The call state information file may be passed to the alternate call controller 208 by the client 204 as part of or in connection with establishing contact with the alternate call controller 208. Furthermore, the call state information file may be pushed to the alternate call controller 208 by the client 204. Alternatively, the call state information file may be provided to the alternate call controller 208 in response to a query for that file made by the alternate call controller 208.

0021After the call state information has been provided to the alternate call controller 208, the system may return to step 320. Furthermore, provided that information concerning all of the applicable call features in effect immediately prior to the loss of the call signaling channel with the primary or prior call controller 208 is contained in the call information file, all of those features may be maintained, even though the call has migrated from the primary call controller 208 to an alternate call controller 208.

0022Although the discussion provided herein has primarily described the use of call state information files to maintain call features associated with communication channels where a call signaling channel is lost, it should be appreciated that the present invention is not so limited. For example, the present invention may also be used to maintain call features applicable to a communication channel where a connection between a client 204 and a call controller 208 is intentionally brought down. For instance, the present invention may be used to maintain call features associated with communication channels in existence at the time that a call controller 208 is removed from service for maintenance or upgrading.

0023Furthermore, it should be appreciated that the present invention may be applied in connection with any IP real-time transfer protocol (RTP) stream. Therefore, although the description provided herein refers to calls and to the use of call controllers, it should be appreciated that the present invention is not limited to voice telephony applications.

0024The present invention, by applying a “cookie” type technique in order to save call state information increases the natural network reliability by distributing such information. In addition, the disclosed invention is highly scalable, as clients 204 store their own call state information, avoiding the need for sending updated call information to a central database or to alternate call controllers. Further, call state information is only sent to alternate controllers when such information is needed. In addition, the disclosed invention is simple to implement and requires relatively few resources. Also, because embodiments of the present invention do not require that clients 204 be capable of recognizing the content of call state information files, changes can be made to the structure and content of these files, without requiring changes to the clients 204. Instead, only call controllers 208 need to be capable of reading the content of the call state information files.

0025The foregoing discussion of the invention has been presented for purposes of illustration and description. Further, the description is not intended to limit the invention to the form disclosed herein. Consequently, variations and modifications commensurate with the above teachings, within the skill and knowledge of the relevant art, are within the scope of the present invention. The embodiments described hereinabove are further intended to explain the best mode presently known of practicing the invention and to enable others skilled in the art to utilize the invention in such or in other embodiments and with various modifications required by their particular application or use of the invention. It is intended that the appended claims be construed to include the alternative embodiments to the extent permitted by the prior art.

Contents5

Every citation, both ways

Citations
Document	Relation	Office	Cited during
US10742800B2	Cited by	United States of America	Applicant
US9500913B2	Cited by	United States of America	Applicant
US8209421B2	Cited by	United States of America	Search report
US10469655B2	Cited by	United States of America	Applicant
US2010121933A1	Cited by	United States of America	Pre-grant
US9075257B2	Cited by	United States of America	Applicant
US2008317060A1	Cited by	United States of America	Pre-grant
US8089872B2	Cited by	United States of America	Applicant
WO0072536A1	Cites	World Intellectual Property Organization (WIPO)	Applicant
WO0072560A1	Cites	World Intellectual Property Organization (WIPO)	Applicant
WO0165808A2	Cites	World Intellectual Property Organization (WIPO)	Applicant
EP0805576A2	Cites	European Patent Office (EPO)	Applicant
EP0920176A2	Cites	European Patent Office (EPO)	Applicant
EP0964563A2	Cites	European Patent Office (EPO)	Applicant
EP1250023A1	Cites	European Patent Office (EPO)	Applicant
EP1677569A1	Cites	European Patent Office (EPO)	Applicant
EP1677570A1	Cites	European Patent Office (EPO)	Applicant
US2001055382A1	Cites	United States of America	Applicant
JP2002237896A	Cites	Japan	Applicant
US2003031137A1	Cites	United States of America	Applicant
US2003091024A1	Cites	United States of America	Applicant
JP2003244204A	Cites	Japan	Applicant
JP2003514439A	Cites	Japan	Applicant
US2004028199A1	Cites	United States of America	Applicant
US2004101119A1	Cites	United States of America	Applicant
US2004143665A1	Cites	United States of America	Applicant
US2004252676A1	Cites	United States of America	Applicant
US2005281216A1	Cites	United States of America	Applicant
US2006034297A1	Cites	United States of America	Applicant
US2006092919A1	Cites	United States of America	Applicant
US2006146799A1	Cites	United States of America	Applicant
US2006146859A1	Cites	United States of America	Applicant
US2006168326A1	Cites	United States of America	Applicant
US5206903A	Cites	United States of America	Applicant
US5280561A	Cites	United States of America	Applicant
US5828747A	Cites	United States of America	Applicant
US5905793A	Cites	United States of America	Applicant
US5974114A	Cites	United States of America	Applicant
US5982873A	Cites	United States of America	Applicant
US6163607A	Cites	United States of America	Applicant
US6173053B1	Cites	United States of America	Applicant
US6192122B1	Cites	United States of America	Applicant
US6282192B1	Cites	United States of America	Applicant
US6292463B1	Cites	United States of America	Applicant
US6314114B1	Cites	United States of America	Applicant
US6317596B1	Cites	United States of America	Search report
US6434226B1	Cites	United States of America	Applicant
US6504922B1	Cites	United States of America	Search report
US6574469B1	Cites	United States of America	Applicant
US6665375B1	Cites	United States of America	Search report
US6671262B1	Cites	United States of America	Applicant
US6721712B1	Cites	United States of America	Applicant
US6731734B1	Cites	United States of America	Applicant
US6738343B1	Cites	United States of America	Search report
US6801612B2	Cites	United States of America	Applicant
US6925076B1	Cites	United States of America	Search report
US6937873B2	Cites	United States of America	Search report
US6950874B2	Cites	United States of America	Applicant
US6968382B2	Cites	United States of America	Applicant
US6973506B2	Cites	United States of America	Applicant
US6999478B2	Cites	United States of America	Applicant
US7145900B2	Cites	United States of America	Search report
US7161897B1	Cites	United States of America	Applicant
US7215643B2	Cites	United States of America	Applicant
US7227927B1	Cites	United States of America	Search report
US7243142B2	Cites	United States of America	Applicant
JPH08320800A	Cites	Japan	Applicant
JPH10164240A	Cites	Japan	Applicant
ITU-T Recommendation H.248, “Series H: Audiovisual and Multimedia Systems,” International Telecommunication Union (Jun. 2000), pp. 1-121.	Non-patent	–	Third party observation
Kristol and Montulli, “HTTP State Management Mechanism,” Oct. 2000, pp. 1-22, available at http://www.cse.ohio-state.edu/cgi-bin/rfc/rfc2965.html, printed Feb. 3, 2005.	Non-patent	–	Third party observation
European Search Report for Application No. EP 04 25 5375 dated Feb. 8, 2005.	Non-patent	–	Third party observation
L. Gavrilovska Bozinovski et al., “Fault-tolerant SIP-based call control system,” <i>Electronic Letters</i>, vol. 29, No. 2 (Jan. 23, 2003), pp. 254-256.	Non-patent	–	Third party observation
U.S. Appl. No. 11/080,763, filed Mar. 14, 2005, Coughlan et al.	Non-patent	–	Third party observation
European Examination Report for EP Application No. 04255375.0 (Jun. 28, 2006).	Non-patent	–	Third party observation
Clark, William J.; “Multipoint Multimedia Conferencing”; IEEE Communications Magazine; May 1992; pp. 44-50.	Non-patent	–	Third party observation
Cisco Systems Overview—Cisco IOS Telephony Services: Survival Remote Site Telephony, Copyright 2001, Cisco Systems, Inc., pp. 1-4.	Non-patent	–	Third party observation
Cisco Systems Solutions Guide—“Survivable Remote Site Telephony Cisco 2600/3600 Voice Technical Marketing” Copyright 1992-2001, Cisco Systems, Inc., pp. 1-19.	Non-patent	–	Third party observation
Cisco Systems IOS Release 12.2(8)T—Survivable Remote Site Telephony, pp. 1-74 (undated).	Non-patent	–	Third party observation
Cisco Solutions Guide, Copyright 1992-2001, Cisco Systems, Inc., http://www.cisco.com/warp/public/cc/pd/unco/srstl/tech/demha<sub>—</sub>sg.htm (21 pages).	Non-patent	–	Third party observation
Cisco Systems—Survivable Remote Site IP Telephony, Copyright 1992-2003, Cisco Systems, Inc., http://www.cisco.com/warp/public/cc/pd/unco/srstl, 1 page.	Non-patent	–	Third party observation
Cisco Systems White Paper, Copyright 1992-2005, Cisco Systems, Inc., http://www.cisco.comlen/us/products/sw/voicesw/ps2169/products<sub>—</sub>white<sub>—</sub>paper09186a008 . . . (5 pages).	Non-patent	–	Third party observation
Cisco IP Telephony Solution Reference Network Design, Dial Plan, #9562230403, Chapter 8, pp. 1-70 (undated).	Non-patent	–	Third party observation
Lucent Technologies Merlin Legend Communications Syst, Release 6.1, Network Reference, 555-661-150 Comcode 108289703; Issue 1, Aug. 1998; 360 pages (3 parts).	Non-patent	–	Third party observation
“Separation of Bearer and Signaling for Avaya™ Communication Manager,” Avaya, Issue 1 (May 2003) pp. 1-42.	Non-patent	–	Third party observation
Carroll Communications, Inc. Automatic Route Selection (ARS) Feature, at http://www.carrollcommunications.com/merlinmagix/AutomaticRouteSelection.html, 2 pages.	Non-patent	–	Third party observation
KXTD System—ISDN—Basic and Primary Rate Interfaces, at http://www.thetelephoneexchange.co.uk/Teleweb<sub>—</sub>files/kxtd.html, 5 pages.	Non-patent	–	Third party observation
Definition—automatic route selection (ARS) at http://www.atisorg/tg2k/automatic<sub>—</sub>selection<sub>—</sub>route.html, 1 page.	Non-patent	–	Third party observation
Acronym Finder—ARS at http://www.auditmypc.com/acronym/ARS.asp, 2 pages.	Non-patent	–	Third party observation
WestNet Learning—glossary for UDP, at http://glossary.westnet.com/term.php?termld=2213, 1 page.	Non-patent	–	Third party observation
Declaration of Michael Gruen Under 37 CFR Section 1.98; 3 pages.	Non-patent	–	Third party observation
European Application No. 04255375.0; Notice of Allowance dated May 31, 2007 (18 pages).	Non-patent	–	Third party observation
Examiner Chan, Examiner's Report for Canadian Patent Application No. 2,478,361, mailed Oct. 30, 2007, 3 pages.	Non-patent	–	Third party observation
ITU-T Recommendation H.248, "Series H: Audiovisual and Multimedia Systems," International Telecommunication Union (Jun. 2000), pp. 1-121.	Non-patent	–	Applicant
Kristol and Montulli, "HTTP State Management Mechanism," Oct. 2000, pp. 1-22, available at http://www.cse.ohio-state.edu/cgi-bin/rfc/rfc2965.html, printed Feb. 3, 2005.	Non-patent	–	Applicant
European Search Report for Application No. EP 04 25 5375 dated Feb. 8, 2005.	Non-patent	–	Applicant
L. Gavrilovska Bozinovski et al., "Fault-tolerant SIP-based call control system," Electronic Letters, vol. 29, No. 2 (Jan. 23, 2003), pp. 254-256.	Non-patent	–	Applicant
U.S. Appl. No. 11/080,763, filed Mar. 14, 2005, Coughlan et al.	Non-patent	–	Applicant
European Examination Report for EP Application No. 04255375.0 (Jun. 28, 2006).	Non-patent	–	Applicant
Clark, William J.; "Multipoint Multimedia Conferencing"; IEEE Communications Magazine; May 1992; pp. 44-50.	Non-patent	–	Applicant
Cisco Systems Overview-Cisco IOS Telephony Services: Survival Remote Site Telephony, Copyright 2001, Cisco Systems, Inc., pp. 1-4.	Non-patent	–	Applicant

Showing 100 of 116

10 members in 5 offices

This recordMember, by publication datePriority claim

Priority claims2

Priority claims
Document	Office	Kind	Date
67665903	United States of America	A	2003-09-30
US20030676659	–	–	–

Members10

Family members, oldest first
Document	Office	Kind
CA2478361A1	Canada	A1	2005-03-30
US2005068889A1	United States of America	A1	2005-03-31
EP1521424A1	European Patent Office (EPO)	A1	2005-04-06
JP2005110260A	Japan	A	2005-04-21
EP1521424B1	European Patent Office (EPO)	B1	2007-11-28
DE602004010345D1	Germany	D1	2008-01-10
DE602004010345T2	Germany	T2	2008-10-02
US7483369B2This record	United States of America	B2	2009-01-27
CA2478361C	Canada	C	2011-02-01
JP5185491B2	Japan	B2	2013-04-17

80 transactions on the USPTO file

Allowed after 3 non-final rejections and 1 final rejection.

Non-final rejections: 3
Final rejections: 1
RCEs: 0
Appeals: 0

Over time

Point at a mark for the transaction

Transactions

Prosecution transactions, newest first
	Event	Code
2020-07-20	Payment of Maintenance Fee, 12th Year, Large EntityM1553	M1553
2009-02-05	Correspondence Address ChangeC.AD	C.AD
2009-01-27	Recordation of Patent Grant MailedPGM/	PGM/
2009-01-27	Patent Issue Date Used in PTA CalculationAllowedPTAC	PTAC
2009-01-07	Issue Notification MailedAllowedWPIR	WPIR
2009-01-07	Workflow - Informational Disclosure Statement - FinishFIDS	FIDS
2008-12-24	Information Disclosure Statement (IDS) FiledWIDS	WIDS
2008-12-18	Dispatch to FDCD1935	D1935
2008-12-17	Application Is Considered Ready for IssuePILS	PILS
2008-12-16	Issue Fee Payment VerifiedN084	N084
2008-12-16	Issue Fee Payment ReceivedIFEE	IFEE
2008-10-20	Mail Miscellaneous Communication to ApplicantMM327	MM327
2008-10-14	Miscellaneous Communication to Applicant - No Action CountM327	M327
2008-10-02	Information Disclosure Statement consideredIDSC	IDSC
2008-10-02	Information Disclosure Statement consideredIDSC	IDSC
2008-10-02	Information Disclosure Statement (IDS) FiledM844	M844
2008-10-02	Information Disclosure Statement (IDS) FiledWIDS	WIDS
2008-10-02	Information Disclosure Statement (IDS) FiledWIDS	WIDS
2008-10-01	Mail Notice of AllowanceAllowedMN/=.	MN/=.
2008-09-26	Notice of Allowance Data Verification CompletedAllowedN/=.	N/=.
2008-09-12	Miscellaneous Incoming LetterLET.	LET.
2008-07-27	Date Forwarded to ExaminerFWDX	FWDX
2008-06-25	Response after Non-Final ActionA...	A...
2008-05-20	Information Disclosure Statement consideredIDSC	IDSC
2008-05-20	Information Disclosure Statement (IDS) FiledM844	M844
2008-05-20	Reference capture on IDSRCAP	RCAP
2008-05-20	Information Disclosure Statement (IDS) FiledWIDS	WIDS
2008-03-26	Mail Non-Final RejectionNon-final rejectionMCTNF	MCTNF
2008-03-20	Non-Final RejectionNon-final rejectionCTNF	CTNF
2008-01-30	Information Disclosure Statement consideredIDSC	IDSC
2008-01-30	Information Disclosure Statement (IDS) FiledWIDS	WIDS
2008-01-30	Electronic Information Disclosure StatementEIDS.	EIDS.
2008-01-29	Date Forwarded to ExaminerFWDX	FWDX
2008-01-25	Response after Non-Final ActionA...	A...
2008-01-21	Information Disclosure Statement consideredIDSC	IDSC
2008-01-21	Electronic Information Disclosure StatementEIDS.	EIDS.
2008-01-21	Information Disclosure Statement (IDS) FiledWIDS	WIDS
2007-11-05	Mail Non-Final RejectionNon-final rejectionMCTNF	MCTNF
2007-11-02	Non-Final RejectionNon-final rejectionCTNF	CTNF
2007-10-24	Date Forwarded to ExaminerFWDX	FWDX
2007-10-23	Response after Final ActionA.NE	A.NE
2007-09-05	Information Disclosure Statement consideredIDSC	IDSC
2007-09-05	Information Disclosure Statement (IDS) FiledM844	M844
2007-09-05	Information Disclosure Statement (IDS) FiledWIDS	WIDS
2007-08-23	Mail Final Rejection (PTOL - 326)Final rejectionMCTFR	MCTFR
2007-08-21	Final RejectionFinal rejectionCTFR	CTFR
2007-06-25	Date Forwarded to ExaminerFWDX	FWDX
2007-06-19	Response after Non-Final ActionA...	A...
2007-05-01	Information Disclosure Statement consideredIDSC	IDSC
2007-05-01	Reference capture on IDSRCAP	RCAP
2007-05-01	Information Disclosure Statement (IDS) FiledM844	M844
2007-05-01	Information Disclosure Statement (IDS) FiledWIDS	WIDS
2007-03-22	Mail Non-Final RejectionNon-final rejectionMCTNF	MCTNF
2007-03-19	Non-Final RejectionNon-final rejectionCTNF	CTNF
2007-03-13	Case Docketed to Examiner in GAUDOCK	DOCK
2007-01-18	Case Docketed to Examiner in GAUDOCK	DOCK
2006-11-16	Case Docketed to Examiner in GAUDOCK	DOCK
2006-07-28	Case Docketed to Examiner in GAUDOCK	DOCK
2006-03-21	Case Docketed to Examiner in GAUDOCK	DOCK
2005-04-08	Information Disclosure Statement consideredIDSC	IDSC
2005-04-08	Information Disclosure Statement (IDS) FiledM844	M844
2005-04-08	Information Disclosure Statement (IDS) FiledWIDS	WIDS
2005-04-08	Reference capture on IDSRCAP	RCAP
2005-02-25	Information Disclosure Statement consideredIDSC	IDSC
2005-02-25	Information Disclosure Statement (IDS) FiledM844	M844
2005-02-25	Information Disclosure Statement (IDS) FiledWIDS	WIDS
2004-12-13	Correspondence Address ChangeC.ADB	C.ADB
2004-08-24	Information Disclosure Statement consideredIDSC	IDSC
2004-08-24	Information Disclosure Statement (IDS) FiledM844	M844
2004-08-24	Information Disclosure Statement (IDS) FiledWIDS	WIDS
2004-04-22	IFW TSS Processing by Tech Center CompleteTSSCOMP	TSSCOMP
2004-04-22	Case Docketed to Examiner in GAUDOCK	DOCK
2004-01-30	New or Additional Drawing FiledC614	C614
2003-12-19	Application Return from OIPEWROIPE	WROIPE
2003-12-19	Application Return TO OIPEROIPE	ROIPE
2003-12-19	Application Dispatched from OIPEOIPE	OIPE
2003-12-19	Application Is Now CompleteCOMP	COMP
2003-12-11	Cleared by OIPE CSRL194	L194
2003-11-15	IFW Scan & PACR Auto Security ReviewSCAN	SCAN
2003-09-30	Initial Exam Team nnIEXX	IEXX

67 legal events, as the office reported them to INPADOC

Over the term

Point at a mark for the event

Events

Legal events, newest first
	Event	Code
2023-09-21	AssignmentAS	AS
2023-05-18	AssignmentAS	AS
2023-05-18	AssignmentAS	AS
2023-05-18	AssignmentAS	AS
2023-05-18	AssignmentAS	AS
2023-05-18	AssignmentAS	AS
2023-05-18	AssignmentAS	AS
2023-05-18	AssignmentAS	AS
2023-05-18	AssignmentAS	AS
2023-05-18	AssignmentAS	AS
2023-05-18	AssignmentAS	AS
2023-05-18	AssignmentAS	AS
2023-05-18	AssignmentAS	AS
2023-05-18	AssignmentAS	AS
2023-05-18	AssignmentAS	AS
2023-05-18	AssignmentAS	AS
2023-05-18	AssignmentAS	AS
2023-05-18	AssignmentAS	AS
2023-05-18	AssignmentAS	AS
2023-05-04	AssignmentAS	AS
2023-05-03	AssignmentAS	AS
2023-04-26	AssignmentAS	AS
2023-04-26	AssignmentAS	AS
2023-04-26	AssignmentAS	AS
2023-04-26	AssignmentAS	AS
2022-08-05	AssignmentAS	AS
2022-07-25	AssignmentAS	AS
2022-07-25	AssignmentAS	AS
2022-07-25	AssignmentAS	AS
2022-07-25	AssignmentAS	AS
2020-09-25	AssignmentAS	AS
2020-07-20	Maintenance fee paymentMAFP	MAFP
2018-01-23	AssignmentAS	AS
2018-01-10	AssignmentAS	AS
2018-01-10	AssignmentAS	AS
2018-01-09	AssignmentAS	AS
2018-01-09	AssignmentAS	AS
2018-01-09	AssignmentAS	AS
2018-01-09	AssignmentAS	AS
2018-01-09	AssignmentAS	AS
2017-12-15	AssignmentAS	AS
2017-12-15	AssignmentAS	AS
2017-12-15	AssignmentAS	AS
2017-12-15	AssignmentAS	AS
2017-12-15	AssignmentAS	AS
2017-12-15	AssignmentAS	AS
2017-12-15	AssignmentAS	AS
2017-12-15	AssignmentAS	AS
2017-01-27	AssignmentAS	AS
2016-07-14	Fee paymentFPAY	FPAY
2013-03-13	AssignmentAS	AS
2013-03-13	AssignmentAS	AS
2012-06-27	Fee paymentFPAY	FPAY
2011-02-22	AssignmentAS	AS
2011-02-22	AssignmentAS	AS
2009-05-12	AssignmentAS	AS
2009-05-12	AssignmentAS	AS
2009-01-07	Information on status: patent grantGrantedPATENTED CASESTCF	STCF
2008-12-02	Fee payment procedurePAYOR NUMBER ASSIGNED (ORIGINAL EVENT CODE: ASPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITYFEPP	FEPP
2008-06-26	AssignmentAS	AS
2008-06-26	AssignmentAS	AS
2007-11-28	AssignmentAS	AS
2007-11-28	AssignmentAS	AS
2007-11-28	AssignmentAS	AS
2007-11-27	AssignmentAS	AS
2007-11-27	AssignmentAS	AS
2003-09-30	AssignmentAS	AS