US8948190B2

Alternate routing of voice communication in a packet-based network

Summary by NHIP

Directory Gatekeeper Routing

The directory gatekeeper selects routes from a stored list to direct data sessions through resource management gatekeepers. It advances to a second route only when the first zone lacks resources or fails to respond to the request.

Claim Score by NHIP

Read claim 1, the broadest

Abstract

A method for performing alternate and therefore least cost routing in distributed H.323 Voice over IP (VoIP) networks is provided. With this method, the VoIP network consists of a hierarchy of gatekeeper (GK) functions to provide alternate routing, network element redundancy, and scalability. The alternate routing function is performed by a directory gatekeeper with route selection advancing from a first route to a second route by either of two conditions: (1) there are no resources available to terminate the call in the first zone; and (2) a lack of response to the directory GK request for such resources.

US8948190B2, drawing sheet 1 — Sheet 1 of 8

Term

Term ended

Expired 1 March 2023, 3.6 years ago.

Parties

Owner: GENUITY INC
Assignee: Level 3 Communications, LLC
Inventors and applicants: David Frederick McGuigan, Sudbury, United States of America
Harry Edward Mussman, Bedford, United States of America
John Joseph McCabe, Billerica, United States of America
Robert Kellar Israel, Westford, United States of America
and 1 more inventorsShow fewer
Eric Richard Sporel, Marlborough, United States of America

Examination

Examiner: Donald Mills, art unit 2462
Filing to grant: 4.7 years
Office actions: Allowed after 1 non-final rejection, 2 final rejections and 1 appeal.⁠

Reach

Cited by: 3 later patents⁠
Cites: 75 earlier patents, 6 other works⁠
Family: 27 members in 9 offices⁠US13WO4AT2CA2EP2AUDEES+1

Classification

CPC: H04M15/00H04M7/006H04L65/104H04L29/06027H04L65/1069H04L65/103+3 more
IPC: H04L12 28H04M15 00H04L29 06H04M7 00H04L65 1106

7 claims: 1 independent, 6 dependent

1
Broadest claimClaim Score 55, average(NHIP)A directory gatekeeper for routing calls through a network comprising:a processor;a memory storing a list of routes, wherein each route is associated with at least one of a plurality of resource management gatekeepers;wherein the directory gatekeeper is communicably coupled to an inbound gatekeeper, the inbound gatekeeper operable to receive requests to setup data sessions and issue routing requests for determining routes for the requested data session;wherein the directory gatekeeper is associated with a plurality of resource zones, each resource zone having an associated resource management gatekeeper and a plurality of outbound gateway resources configured to terminate data sessions received by the inbound gatekeeper;and wherein the directory gatekeeper is operable to receive routing requests from the inbound gatekeeper for determining routes for the requested data session.

45 paragraphs in 6 sections, as filed

0001This application is a continuation of U.S. patent application Ser. No. 12/017,321, entitled “Alternate Routing of Voice Communication in a Packet-Based Network,” filed Jan. 21, 2008, now U.S. Pat. No. 7,720,084 which is incorporated herein by reference in its entirety. Application Ser. No. 12/017,321 is a continuation of U.S. patent application Ser. No. 09/827,352, entitled “Alternate Routing of Voice Communication in a Packet-Based Network,” filed Apr. 6, 2001, now U.S. Pat. No. 7,339,934 which is incorporated herein by reference in its entirety.

TECHNICAL FIELD

0002This invention relates to call routing in packet-based networks, and more particularly to alternate routing (e.g., least cost routing) of calls in a packet-based voice transmission system, for example, Voice over Internet Protocol (VoIP).

BACKGROUND

0003For many years, the Public Switched Telephone Network (PSTN) has provided a reliable mechanism for transmitting voice communications. However, the reliability of conventional telephone networks comes at high cost. Each established communication link in a conventional telephone network, reserves a bandwidth of 64 kbps for the duration, regardless of the bandwidth actually needed for the communications. A conventional telephone communication link uses a bandwidth of 64 kbps for all transmissions.

0004In contrast, conventional data communication networks are packet-based with no guarantee of reliability. In such a network, bandwidth is available on a first-come, first-serve basis. In a conventional packet-based network, voice communications may be broken into multiple packets. Packets are transmitted and then reassembled at the destination. Because packets may be lost or may arrive out of sequence, the quality of voice communications may suffer.

0005In the last few years, efforts have been made to converge data, voice, and video communications in a single network. For example, the International Telecommunication Union Telecommunication Standardization Section (ITU-T) released the H.323 specification for transmitting audio, video, and data across an Internet Protocol (IP) network.

SUMMARY

0006A directory gatekeeper is provided for performing alternate routing of calls through gateway resources in a distributed network (e.g., H.323 Voice over IP). The directory gatekeeper includes one or more communication devices providing access to resource management gatekeepers. Each resource management gatekeeper is associated with one or more gateway resources. A memory device accessible by the directory gatekeeper stores a list of routes where each route is associated with one of the resource management gatekeepers. A processor receives a request through one of the communication devices, and performs alternate routing by selecting a route from the list of routes using the corresponding resource management gatekeeper to determine resource availability.

0007In some implementations, the communication devices provide access to networks such as a packet-based network (e.g., an Internet protocol (IP) network), and the public switched telephone network (PSTN).

0008In some implementations, the directory gatekeeper performs alternate routing of calls by identifying one or more candidate routes based on a received request. Then, for each of the candidate routes, selecting a candidate route, determining if the selected candidate route is available, and sending a response to the received request indicating the available route or if the request can not be satisfied.

0009A route may be selected from the list of candidate routes in several ways. For example, the least cost route may be selected as the candidate route or candidate routes may be selected at a predetermined ratio. The predetermined ratio can be selected such that the likelihood of choosing each of the candidate routes is substantially equal.

0010The details of one or more implementations are set forth in the accompanying drawings and the description below. Other features and advantages will be apparent from the description and drawings, and from the claims.

DESCRIPTION OF DRAWINGS

0011<figref idref="DRAWINGS">FIG. 1</figref> is a block diagram of a hybrid communication network providing connectivity between a Public Switched Telephone Network (PSTN) and a packet-based network.

0012<figref idref="DRAWINGS">FIG. 2</figref> is a block diagram of an H.323 implementation of a hybrid communication network such as that shown in <figref idref="DRAWINGS">FIG. 1</figref>.

0013<figref idref="DRAWINGS">FIG. 3</figref> is a block diagram of a gatekeeper hierarchy showing the relationship between an inbound gatekeeper, a directory gatekeeper, a resource management gatekeeper, and various gateway resources.

0014<figref idref="DRAWINGS">FIG. 4</figref> is a block diagram describing an implementation of least cost routing using a hierarchical gatekeeper configuration such as that shown in <figref idref="DRAWINGS">FIG. 3</figref>.

0015<figref idref="DRAWINGS">FIG. 5</figref> is a diagram of an exemplary call sequence showing the interactions between the various zones shown in <figref idref="DRAWINGS">FIG. 4</figref>.

0016<figref idref="DRAWINGS">FIG. 6</figref> is a block flowchart of the operation of call setup in a hierarchical gatekeeper configuration.

DETAILED DESCRIPTION

0017Voice over Internet Protocol (VoIP) networks provide one mechanism to transmit voice communication over packet-based networks. The International Telecommunication Union Telecommunication Standardization Sector (ITU-T) has published the H.323 standard for implementing VoIP systems. VoIP networks may be integrated with the Public Switched Telephone Network (PSTN) to provide connectivity between VoIP terminals and traditional telephones connected to the PSTN.

0018Referring to <figref idref="DRAWINGS">FIG. 1</figref>, terminals 1010 and 1020 connect to PSTN 1030 through a communication link, for example, one or more wires, a wireless link, and/or a fiber optic cable. Terminals 1010 and 1020 may transmit data across the communication link using analog or digital signals. Generally, a terminal is connected to the PSTN 1030 through analog, Integrated Services Digital Network (ISDN), or through a T1 carrier.

0019Packet network 1040 connects to PSTN 1030 through gateway 1050. Terminals 1060 and 1070 connect to packet network 1040 using any networking technology, for example, Ethernet, Asynchronous Transfer Mode (ATM), wireless network connection, and/or modem. Terminals 1060 and 1070 may be implemented using any device capable of sending and receiving audio, for example, as telephones, computers, personal digital assistant (PDA), laptop computer, and/or cellular phone.

0020The configuration shown in <figref idref="DRAWINGS">FIG. 1</figref> permits voice communication between any of the terminals 1010, 1020, 1060, and 1070. Thus, voice communication may be transmitted from terminal 1010 to terminal 1060 across PSTN 1030 through gateway 1050 to packet network 1040.

0021Referring to <figref idref="DRAWINGS">FIG. 2</figref>, an H.323 implementation of the network described in <figref idref="DRAWINGS">FIG. 1</figref> includes a H.323 network 2000 connected to PSTN 1030 through gateway 1050. The H.323 network 2000 includes terminals 1060 and 1070, Packet Network 1040, and gateway 1050 as described above with reference to <figref idref="DRAWINGS">FIG. 1</figref>. In addition, H.323 network 2000 includes gatekeeper 2010 to provide pre-call and call-level control services to H.323 terminals. The H.323 standard defines call signaling and control, multimedia transport and control, and bandwidth control for point-to-point and multipoint conferences.

0022Gatekeeper 2010 provides pre-call and call-level control services. For example, one implementation of gatekeeper 2010 provides the following services: (1) address translation to resolve endpoint. IP addresses from aliases or standard phone numbers; (2) admissions control to restrict access to terminals or gateways; (3) bandwidth control to manage endpoint bandwidth requirements; (4) zone management capabilities for terminals, gateways, and other devices within a H.323 zone; and (5) call management capabilities, for example, maintaining a list of active calls so that the gatekeeper can determine if a terminal or endpoint is busy.

0023The demands of gatekeeper 2010 grow as the number of endpoints or terminals increases. At some point, it becomes impracticable to implement the pre-call and call-level control services on a single gatekeeper 2010. One way to overcome the limitations of a single gatekeeper 2010 is to distribute the functionality across multiple devices.

0024A distributed network architecture increases the ability to scale H.323 VoIP networks for large-scale deployments. In large networks, it may be advantageous to provide alternate routing between two terminals. For example, it may be desirable to route communications across the least expensive link, to balance load across multiple links, or to provide redundant communication paths. In one distributed gatekeeper implementation there is no central repository of current resource availability in an H.323 network (i.e., knowing which circuits in a group (or zone) are busy or idle, and therefore whether there is an idle circuit in the group).

0025Referring to <figref idref="DRAWINGS">FIG. 3</figref>, a hierarchical distributed implementation splits the resource management functionality from the other gatekeeper functions discussed above. The implementation includes an inbound gatekeeper 3010, a directory gatekeeper 3020, a redundant directory level gatekeeper 3025, one or more resource management gatekeepers 3030, and one or more gateway resources 3040.

0026The directory gatekeeper 3020 manages the desired routing tables for calls. Some implementation the directory gatekeeper 3020 manages least cost routing information. In these implementations, call attempts are sent to directory gatekeeper 3020 for resolution of the appropriate least cost routing information. Based on the desired route selection order, directory gatekeeper 3020 sends a request to a resource management gatekeeper 3030 managing specific outbound gateway resources 3040. If there are gateway resources 3040 available to terminate the call attempt, the resource management gatekeeper 3030 acknowledges the directory gatekeeper 3020 request with the applicable gateway to forward the call to. If there are no gateway resources 3040 available, the resource management, gatekeeper 3030 will reject the directory gatekeeper 3020 request. The directory gatekeeper 3020 will then advance the route selection index and send a request to the next resource management gatekeeper 3030 and the process repeats.

0027If the directory gatekeeper 3020 does not receive a response from the desired resource management gatekeeper 3030, the directory gatekeeper 3020 will also advance to the next resource management gatekeeper 3030, thus providing network redundancy for failure of any individual resource management gatekeeper 3030.

0028The inbound gatekeeper 3010 interfaces with the source of calls, and sends a routing request to the appropriate directory gatekeeper 3020. If there are gateway resources 3040 available to terminate the call attempt, the resource management gatekeeper 3030 acknowledges the directory gatekeeper 3020 request with the applicable gateway to forward the call to, and this in turn forwarded to the inbound gatekeeper 3010. If the inbound gatekeeper 3010 does not receive a response from the directory gatekeeper 3020, the inbound gatekeeper will advance to the alternate directory gatekeeper 3025, thus providing network redundancy for failure of a directory gatekeeper 3020.

0029As noted above, the resource management gatekeeper 3030 checks its knowledge of available gateway resources 3040 and acknowledges the directory gatekeeper 3020 request with the applicable gateway to forward the call to. To maintain a current view of gateway resources 3040, the various gateways periodically report their used and available resources to the resource management gatekeeper 3030. This can be done with detailed counts, or simply an indication that the resources in a zone are above or below a given threshold. When a resource management gatekeeper 3030 checks resources, it typically considers all of the gateway resources 3040 in a zone. However, it is sometimes advantageous to exclude certain gateways, and not consider them as candidates for carrying an outbound call. This is advantageous when, for example, the zone contains gateways associated with a given carrier, but where certain calls (say to the 212 area code) should be excluded from certain gateways (say those in New York) to avoid higher intra-state charges. This process may create “holes” in the routing.

0030Calls are initiated using the H.323 registration, admission, and status (RAS) protocol. In this protocol, a call is initiated by inbound gatekeeper 3010 by sending a location request (LRQ) message to the directory gatekeeper 3020. If the inbound gatekeeper 3010 does not receive a location confirmation message within a predefined time, the inbound gatekeeper 3010 sends another LRQ message to the redundant directory gatekeeper 3025.

0031Upon receiving a LRQ message from the inbound gatekeeper 3010, the directory gatekeeper 3020 selects the first route of several possible networks capable of terminating Voice over Internet Protocol (VoIP) calls. The directory gatekeeper 3020 issues a location request to the first resource management gatekeeper 3030. If the resource management gatekeeper has knowledge of a gateway resource 3040 that is capable of terminating the VoIP call attempt, the resource management gatekeeper 3030 responds to the directory gatekeeper 3020 with a location confirmation (LCF) message indicating the gateway resource 3040 where the call is to be terminated.

0032During the lifetime of a call, the resource management gatekeeper 3030 and the gateway resources 3040 provide resource availability information to each other. This resource availability information is required by the resource management gatekeeper 3030 to maintain the appropriate availability information required to properly respond to location requests received by the directory gatekeeper 3020.

0033If the resource management gatekeeper 3030 does not have knowledge of an available gateway resource 3040 to terminate the call attempt, the resource management gatekeeper 3030 responds to the location request from the directory gatekeeper 3020 with a location reject (LRJ) message indicating the lack of available resources.

0034If the directory gatekeeper 3020 receives a LRJ message or does not get a response from the resource management gatekeeper 3030 within a specified interval, the directory gatekeeper 3020 will advance to the next route and issue a new location request to a different resource management gatekeeper 3030. The process of sending location requests repeats until no additional routes are available. If no routes are available, the directory gatekeeper 3020 rejects the call request by sending an LRJ message to the inbound gatekeeper 3010.

0035Referring to <figref idref="DRAWINGS">FIG. 4</figref>, a terminal 4010 connects to ingress zone 4100. Ingress zone 4100 provides access to three egress zones 4210, 4220, and 4230 each having an associated cost or priority. In this example, egress zone 4210 provides access across a private network at the lowest cost; therefore, this zone is given the highest priority. Egress zone 4220 routes calls across another network at a higher cost than egress zone 4210. Finally, egress zone 4230 routes calls across the most expensive network and is therefore given the lowest priority.

0036<figref idref="DRAWINGS">FIG. 5</figref> describes an exemplary call sequence that may occur in the network described above with reference to <figref idref="DRAWINGS">FIG. 4</figref>. Terminal 4010 sends an admission request (ARQ) message to ingress zone 4100. A gatekeeper in ingress zone 4100 receives the request and sends a location request (LRQ) message to the least cost zone, egress zone 4210. This LRQ message (designated. LRQ1) times out after a predetermined amount of time.

0037The gatekeeper in ingress zone 4100 then sends an LRQ message to the next highest priority zone, egress zone 4220. Egress zone 4220 determines that resources are unavailable for terminal 4010 to complete a call through egress zone 4210 and so returns a location reject (LRJ) message (designated LRJ2 in <figref idref="DRAWINGS">FIG. 5</figref>). A gatekeeper in an egress zone may be implemented as a resource management gatekeeper 3030 as described above with reference to <figref idref="DRAWINGS">FIG. 3</figref>. Resource management gatekeepers 3030 may reject LRQ messages for the same reasons that location requests are rejected in conventional, single-gatekeeper implementations, for example, insufficient resources are available or the terminal has insufficient authorization.

0038After receiving LRJ2 from egress zone 4220, the gatekeeper in ingress zone 4100 sends a LRQ message (designated LRQ3) to the next zone on its list, egress zone 4230. The gatekeeper in egress zone 4230 responds to LRQ3 with a location confirmation (LCF) message. When ingress zone 4100 receives LCF3, an admission confirm (ACF) message is sent to terminal 4010. Calls then continue as in a single gatekeeper implementation. In this manner, least cost and alternate routing may be implemented in a structure providing increased reliability and scalability.

0039Referring to <figref idref="DRAWINGS">FIG. 6</figref>, an endpoint device (e.g., telephone, computer, cellular phone) attempting to complete a call to another endpoint device sends an admission request (ARQ) message to a directory gatekeeper (step 6010). The directory gatekeeper maintains a list of available routes. The list may be based on portions of identifications of called endpoint devices. For example, if the called endpoint device is 212-555-1212, the directory gatekeeper may maintain a list of numbering plan areas (NPAs) with corresponding routes. In one implementation, a directory gatekeeper maintains multiple routes to the NPA 212. In some implementation, these routes are maintained by manually configuring the directory gatekeeper; however, other implementations include the ability for a directory gatekeeper to dynamically create routing lists by receiving communications from various resource management gatekeepers.

0040The directory gatekeeper determines if routes are available (step 6020). If so, the directory gatekeeper sends a location request (LRQ) message to a resource management gatekeeper corresponding to that route (step 6020). Routes may be selected by any criteria. For example, in some implementations, the directory gatekeeper selects the least cost route.

0041In some implementations, the directory gatekeeper balances the load across multiple routes based on some metric. For example, calls may routed across the first available, randomly-selected route, across the lowest cost available route, and calls may be distributed across two routes at a predetermined frequency (e.g., 40% of calls across one route and 60% across another, first 100 calls per day across one route and the remaining across another).

0042If no routes are available, the directory gatekeeper cannot terminate the call and sends an admission reject (ARJ) message back to the endpoint (step 6030), thus ending the process.

0043If routes are available, the directory gatekeeper sends a location request (LRQ) message to the gatekeeper corresponding to the selected route (step 6040). If no response is received before a predetermined timeout interval, then the gatekeeper determines if additional routes are available (step 6020).

0044If a response is received, the directory gatekeeper determines if the response is a location confirm (LCF) message (step 6060). If so, the directory gatekeeper sends an admission confirm (ACF) message for the available route (step 6070). If confirmation is not received (e.g., a location reject (LRJ) message is received), the directory gatekeeper checks to see if additional routes are available (step 6020). Using the process described in <figref idref="DRAWINGS">FIG. 6</figref>, a hierarchical gatekeeper system provides a mechanism for implementing alternate routing.

0045A number of implementations have been described. Nevertheless, it will be understood that various modifications may be made without departing from the spirit and scope of the invention. Accordingly, other implementations are within the scope of the following claims.

Contents6

Every citation, both ways

Citations
Document	Relation	Office	Cited during
US11232655B2	Cited by	United States of America	Applicant
US9185142B2	Cited by	United States of America	Applicant
US10650621B1	Cited by	United States of America	Applicant
WO0075744A2	Cites	World Intellectual Property Organization (WIPO)	Applicant
WO0105115A2	Cites	World Intellectual Property Organization (WIPO)	Applicant
EP0966145A2	Cites	European Patent Office (EPO)	Applicant
EP1014633B1	Cites	European Patent Office (EPO)	Applicant
EP1035719A2	Cites	European Patent Office (EPO)	Applicant
EP1089535A2	Cites	European Patent Office (EPO)	Applicant
US2001003522A1	Cites	United States of America	Applicant
US2002101860A1	Cites	United States of America	Applicant
US2002122547A1	Cites	United States of America	Applicant
US2002136206A1	Cites	United States of America	Applicant
US2003046400A1	Cites	United States of America	Applicant
US2003059005A1	Cites	United States of America	Applicant
US2003091024A1	Cites	United States of America	Applicant
US2003095541A1	Cites	United States of America	Applicant
US2003095542A1	Cites	United States of America	Applicant
US2003118006A1	Cites	United States of America	Applicant
US2003123436A1	Cites	United States of America	Applicant
US2003161458A1	Cites	United States of America	Applicant
US2004179515A1	Cites	United States of America	Applicant
US2010157983A1	Cites	United States of America	Applicant
US4284852A	Cites	United States of America	Applicant
US4679186A	Cites	United States of America	Applicant
US4991204A	Cites	United States of America	Applicant
US5058105A	Cites	United States of America	Applicant
US5956339A	Cites	United States of America	Applicant
US6067545A	Cites	United States of America	Applicant
US6122255A	Cites	United States of America	Applicant
US6141345A	Cites	United States of America	Applicant
US6157636A	Cites	United States of America	Applicant
US6275574B1	Cites	United States of America	Applicant
US6363065B1	Cites	United States of America	Applicant
US6366576B1	Cites	United States of America	Applicant
US6430282B1	Cites	United States of America	Applicant
US6452922B1	Cites	United States of America	Applicant
US6510219B1	Cites	United States of America	Applicant
US6574216B1	Cites	United States of America	Applicant
US6581104B1	Cites	United States of America	Applicant
US6628617B1	Cites	United States of America	Applicant
US6714535B1	Cites	United States of America	Search report
US6754181B1	Cites	United States of America	Applicant
US6771640B2	Cites	United States of America	Applicant
US6798786B1	Cites	United States of America	Applicant
US6826272B1	Cites	United States of America	Applicant
US6940849B2	Cites	United States of America	Applicant
US6973504B2	Cites	United States of America	Applicant
US6996093B2	Cites	United States of America	Search report
US7002970B1	Cites	United States of America	Applicant
US7031450B2	Cites	United States of America	Search report
US7113500B1	Cites	United States of America	Applicant
US7145898B1	Cites	United States of America	Applicant
US7203956B2	Cites	United States of America	Search report
US7239629B1	Cites	United States of America	Search report
US7283519B2	Cites	United States of America	Applicant
US7330463B1	Cites	United States of America	Applicant
US7379471B2	Cites	United States of America	Applicant
US7570632B2	Cites	United States of America	Applicant
WO9914931A2	Cites	World Intellectual Property Organization (WIPO)	Applicant
US20010003522A1	Cites	United States of America	Applicant
US20020101860A1	Cites	United States of America	Applicant
US20020122547A1	Cites	United States of America	Applicant
US20020136206A1	Cites	United States of America	Applicant
US20030046400A1	Cites	United States of America	Applicant
US20030059005A1	Cites	United States of America	Applicant
US20030091024A1	Cites	United States of America	Applicant
US20030095541A1	Cites	United States of America	Applicant
US20030095542A1	Cites	United States of America	Applicant
US20030118006A1	Cites	United States of America	Applicant
US20030123436A1	Cites	United States of America	Applicant
US20030161458A1	Cites	United States of America	Applicant
US20040179515A1	Cites	United States of America	Applicant
US20100157983A1	Cites	United States of America	Applicant
EP966145A2	Cites	European Patent Office (EPO)	Applicant
WO9914931A2	Cites	World Intellectual Property Organization (WIPO)	Applicant
WO0075744A2	Cites	World Intellectual Property Organization (WIPO)	Applicant
WO0105115A2	Cites	World Intellectual Property Organization (WIPO)	Applicant
Loa, et al., “Enhanced H.323 Gateway with IVR Agent and H.323 Gatekeepers”, MotorolaTechnical Developments; Motorola Inc., Schaumburg, II., vol. 39, Sep. 1999 , 120-123.	Non-patent	–	Applicant
Pearlman, et al., “Alternate Path Routing in Mobile Ad:Hoc Networks”, IEEE MILCOM; Los Angeles, CA Oct. 2000 , 1-6.	Non-patent	–	Applicant
“Canadian Office Action dated Dec. 15, 2010,”, counterpart Canadian App. No. 2443097 filed Apr. 8, 2002, 3 pgs.	Non-patent	–	Applicant
Loa, et al., "Enhanced H.323 Gateway with IVR Agent and H.323 Gatekeepers", MotorolaTechnical Developments; Motorola Inc., Schaumburg, II., vol. 39, Sep. 1999 , 120-123.	Non-patent	–	Applicant
Pearlman, et al., "Alternate Path Routing in Mobile Ad:Hoc Networks", IEEE MILCOM; Los Angeles, CA Oct. 2000 , 1-6.	Non-patent	–	Applicant
"Canadian Office Action dated Dec. 15, 2010,", counterpart Canadian App. No. 2443097 filed Apr. 8, 2002, 3 pgs.	Non-patent	–	Applicant

27 members in 9 offices

This recordMember, by publication datePriority claim

Priority claims2

Priority claims
Document	Office	Kind	Date
82735201	United States of America	A	2001-04-06
1732108	United States of America	A	2008-01-21

Members27

Family members, oldest first
Document	Office	Kind
CA2443097A1	Canada	A1	2002-10-17
WO02082722A2	World Intellectual Property Organization (WIPO)	A2	2002-10-17
AU2002311807A1	Australia	A1	2002-10-21
US2003012178A1	United States of America	A1	2003-01-16
WO02082722A3	World Intellectual Property Organization (WIPO)	A3	2003-11-27
EP1386469A2	European Patent Office (EPO)	A2	2004-02-04
MXPA03009118A	Mexico	A	2004-11-22
US2005025043A1	United States of America	A1	2005-02-03
WO2005013541A2	World Intellectual Property Organization (WIPO)	A2	2005-02-10
WO2005013541A3	World Intellectual Property Organization (WIPO)	A3	2005-05-26
US7215643B2	United States of America	B2	2007-05-08
US2007165607A1	United States of America	A1	2007-07-19
EP1386469B1	European Patent Office (EPO)	B1	2007-09-12
AT373375T	Austria	T	2007-09-15
ATE373375T1	Austria	T1	2007-09-15
DE60222400D1	Germany	D1	2007-10-25
US7339934B2	United States of America	B2	2008-03-04
ES2292769T3	Spain	T3	2008-03-16
US2008112327A1	United States of America	A1	2008-05-15
US7570632B2	United States of America	B2	2009-08-04
US7720084B2	United States of America	B2	2010-05-18
US2010157983A1	United States of America	A1	2010-06-24
US2010226363A1	United States of America	A1	2010-09-09
CA2443097C	Canada	C	2012-06-05
US8948190B2This record	United States of America	B2	2015-02-03
US2015304504A1	United States of America	A1	2015-10-22
US9185142B2	United States of America	B2	2015-11-10

82 transactions on the USPTO file

Allowed after 1 non-final rejection, 2 final rejections and 1 appeal.

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

Over time

Point at a mark for the transaction

Transactions

Prosecution transactions, newest first
	Event	Code
2022-08-02	Payment of Maintenance Fee, 8th Year, Large EntityM1552	M1552
2018-07-19	Payment of Maintenance Fee, 4th Year, Large EntityM1551	M1551
2015-02-03	Recordation of Patent Grant MailedPGM/	PGM/
2015-02-03	Patent Issue Date Used in PTA CalculationAllowedPTAC	PTAC
2015-01-15	Email NotificationEML_NTR	EML_NTR
2015-01-14	Issue Notification MailedAllowedWPIR	WPIR
2015-01-05	Dispatch to FDCD1935	D1935
2014-12-04	Application Is Considered Ready for IssuePILS	PILS
2014-11-26	Issue Fee Payment VerifiedN084	N084
2014-11-26	Issue Fee Payment ReceivedIFEE	IFEE
2014-11-21	Electronic ReviewELC_RVW	ELC_RVW
2014-11-21	Email NotificationEML_NTF	EML_NTF
2014-11-21	Mail Notice of AllowanceAllowedMN/=.	MN/=.
2014-11-18	Notice of Allowance Data Verification CompletedAllowedN/=.	N/=.
2014-11-06	Paralegal or electronic terminal disclaimer approvedP574	P574
2014-11-05	Date Forwarded to ExaminerFWDX	FWDX
2014-10-30	Terminal Disclaimer FiledDIST	DIST
2014-10-30	Response after Final ActionA.NE	A.NE
2014-07-30	Electronic ReviewELC_RVW	ELC_RVW
2014-07-30	Email NotificationEML_NTF	EML_NTF
2014-07-30	Mail Final Rejection (PTOL - 326)Final rejectionMCTFR	MCTFR
2014-07-25	Final RejectionFinal rejectionCTFR	CTFR
2014-06-10	Email NotificationEML_NTR	EML_NTR
2014-06-10	Change in Power of Attorney (May Include Associate POA)PA..	PA..
2014-04-16	Date Forwarded to ExaminerFWDX	FWDX
2014-04-10	Appeal Brief Review CompleteAPBR	APBR
2014-04-09	track 1 OFFT1OFF	T1OFF
2014-04-09	Appeal Brief FiledAP.B	AP.B
2014-04-09	Request for Extension of Time - GrantedXT/G	XT/G
2014-01-09	Notice of Appeal FiledN/AP	N/AP
2013-10-09	Electronic ReviewELC_RVW	ELC_RVW
2013-10-09	Email NotificationEML_NTF	EML_NTF
2013-10-09	Mail Final Rejection (PTOL - 326)Final rejectionMCTFR	MCTFR
2013-10-01	Final RejectionFinal rejectionCTFR	CTFR
2013-06-28	Date Forwarded to ExaminerFWDX	FWDX
2013-06-21	Response after Non-Final ActionA...	A...
2013-06-21	Request for Extension of Time - GrantedXT/G	XT/G
2013-03-21	Email NotificationEML_NTR	EML_NTR
2013-03-21	Mail Notice of Informal or Non-Responsive AmendmentNINA	NINA
2013-01-15	Information Disclosure Statement consideredIDSC	IDSC
2013-01-15	Reference capture on IDSRCAP	RCAP
2013-01-15	Information Disclosure Statement (IDS) FiledM844	M844
2013-01-15	Information Disclosure Statement (IDS) FiledWIDS	WIDS
2013-01-07	Date Forwarded to ExaminerFWDX	FWDX
2012-12-21	Informal or Non-Responsive Amendment after Examiner ActionA.I.	A.I.
2012-12-21	Response after Non-Final ActionA...	A...
2012-12-21	Request for Extension of Time - GrantedXT/G	XT/G
2012-06-21	Electronic ReviewELC_RVW	ELC_RVW
2012-06-21	Email NotificationEML_NTF	EML_NTF
2012-06-21	Mail Non-Final RejectionNon-final rejectionMCTNF	MCTNF
2012-06-13	Non-Final RejectionNon-final rejectionCTNF	CTNF
2012-05-21	Case Docketed to Examiner in GAUDOCK	DOCK
2012-02-21	Case Docketed to Examiner in GAUDOCK	DOCK
2012-02-07	Information Disclosure Statement consideredIDSC	IDSC
2012-02-07	Reference capture on IDSRCAP	RCAP
2012-02-07	Information Disclosure Statement (IDS) FiledM844	M844
2012-02-07	Information Disclosure Statement (IDS) FiledWIDS	WIDS
2011-08-16	Information Disclosure Statement consideredIDSC	IDSC
2011-08-16	Reference capture on IDSRCAP	RCAP
2011-08-16	Information Disclosure Statement (IDS) FiledM844	M844
2011-08-16	Information Disclosure Statement (IDS) FiledWIDS	WIDS
2011-03-29	Case Docketed to Examiner in GAUDOCK	DOCK
2011-03-15	Information Disclosure Statement consideredIDSC	IDSC
2011-03-15	Information Disclosure Statement (IDS) FiledM844	M844
2011-03-15	Information Disclosure Statement (IDS) FiledWIDS	WIDS
2011-02-09	Information Disclosure Statement consideredIDSC	IDSC
2011-02-09	Reference capture on IDSRCAP	RCAP
2011-02-09	Information Disclosure Statement (IDS) FiledM844	M844
2011-02-09	Information Disclosure Statement (IDS) FiledWIDS	WIDS
2011-02-09	Case Docketed to Examiner in GAUDOCK	DOCK
2010-09-26	Case Docketed to Examiner in GAUDOCK	DOCK
2010-09-13	Preliminary AmendmentA.PE	A.PE
2010-09-10	Email NotificationEML_NTR	EML_NTR
2010-09-09	PG-Pub Issue NotificationPG-ISSUE	PG-ISSUE
2010-06-24	Application Dispatched from OIPEOIPE	OIPE
2010-06-01	Application Is Now CompleteCOMP	COMP
2010-06-01	Email NotificationEML_NTR	EML_NTR
2010-06-01	Filing ReceiptFLRCPT.O	FLRCPT.O
2010-05-28	Sent to Classification ContractorPGPC	PGPC
2010-05-18	Cleared by OIPE CSRL194	L194
2010-05-17	IFW Scan & PACR Auto Security ReviewSCAN	SCAN
2010-05-17	Initial Exam Team nnIEXX	IEXX

7 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
2022-08-02	Maintenance fee paymentMAFP	MAFP
2018-07-19	Maintenance fee paymentMAFP	MAFP
2015-01-14	Information on status: patent grantGrantedPATENTED CASESTCF	STCF
2014-05-20	AssignmentAS	AS
2014-05-20	AssignmentAS	AS
2011-05-04	AssignmentAS	AS
2011-04-26	AssignmentAS	AS

Alternate routing of voice communication in a packet-based network

Summary by NHIP

Claim Score by NHIP

Abstract