Source: http://www.google.com/patents/US20070232322?dq=7,181,690
Timestamp: 2017-05-28 05:05:02
Document Index: 671712317

Matched Legal Cases: ['art 20', 'art 20', 'art 20', 'art 30', 'art 30', 'art 30', 'art 40', 'art 40', 'art 40']

Patent US20070232322 - Processing location information among multiple networks - Google PatentsSearch Images Maps Play YouTube News Gmail Drive More »Sign inPatentsGathering location information from a first wireless network to determine whether to anchor a communication session in a second wireless network, a mobile node capable of communicating with both the first wireless network and the second wireless network, includes receiving location information from the...http://www.google.com/patents/US20070232322?utm_source=gb-gplus-sharePatent US20070232322 - Processing location information among multiple networksAdvanced Patent SearchTry the new Google Patents, with machine-classified Google Scholar results, and Japanese and South Korean patents.Publication numberUS20070232322 A1Publication typeApplicationApplication numberUS 11/392,408Publication dateOct 4, 2007Filing dateMar 28, 2006Priority dateMar 28, 2006Also published asEP1999974A1, EP1999974A4, US7593722, US7877086, US20090325582, WO2007126420A1Publication number11392408, 392408, US 2007/0232322 A1, US 2007/232322 A1, US 20070232322 A1, US 20070232322A1, US 2007232322 A1, US 2007232322A1, US-A1-20070232322, US-A1-2007232322, US2007/0232322A1, US2007/232322A1, US20070232322 A1, US20070232322A1, US2007232322 A1, US2007232322A1InventorsRamanathan Jagadeesan, Andrew Chung, Steven Donovan, Mark Grayson, Bich Nguyen, Christopher PearceOriginal AssigneeCisco Technology, Inc.Export CitationBiBTeX, EndNote, RefManPatent Citations (11), Referenced by (22), Classifications (5), Legal Events (4) External Links: USPTO, USPTO Assignment, EspacenetProcessing location information among multiple networks
US 20070232322 A1Abstract
Gathering location information from a first wireless network to determine whether to anchor a communication session in a second wireless network, a mobile node capable of communicating with both the first wireless network and the second wireless network, includes receiving location information from the first wireless network as the mobile node moves through one or more service areas of the first wireless network. It is determined whether a triggering event occurs. If the triggering event occurs, the location information is stored to determine whether to anchor a session in the second wireless network. Images(4) Claims(27)
TECHNICAL FIELD [0001] This invention relates generally to the field of telecommunications and more specifically to processing location information among multiple networks. BACKGROUND [0002] A communication session for a mobile node is typically anchored at an anchor point of a communication network. The anchor point processes the communication session while the node is involved in a handoff process. In certain cases, a node may be operable to communicate with different types of networks. For example, a node may communicate with a Wireless Fidelity (WiFi) system of an Internet Protocol (IP) network and with a cell site of a cellular network. Known techniques for anchoring a communication session for such a node are not efficient in certain situations. For example, unnecessarily anchoring a communication in the IP network can result in long distance charges applying to a local communication. SUMMARY OF THE DISCLOSURE [0003] In accordance with the present invention, disadvantages and problems associated with previous techniques for anchoring communication sessions may be reduced or eliminated. [0004] According to one embodiment of the present invention, gathering location information from a first wireless network to determine whether to anchor a communication session in a second wireless network, a mobile node capable of communicating with both the first wireless network and the second wireless network, includes receiving location information from the first wireless network as the mobile node moves through one or more service areas of the first wireless network. It is determined whether a triggering event occurs. If the triggering event occurs, the location information is stored to determine whether to anchor a session in the second wireless network. [0005] According to another embodiment, analyzing location information from a first wireless network to determine whether to anchor a communication session in a second wireless network, a mobile node capable of communicating with both the first wireless network and the second wireless network includes receiving location information for a time interval as the mobile node moves through the first wireless network. A prediction is developed based on the location information. The prediction includes whether the mobile node will move into the second wireless network during the communication session initiated at a particular location in the first wireless network. [0006] According to yet another embodiment, determining whether to anchor a communication session in a second wireless network, a mobile node capable of communicating with both a first wireless network and the second wireless network includes initiating a communication session in the first wireless network. A current location of the mobile node in the first wireless network is determined. Prediction information generated from location information previously gathered as mobile node moves through one or more services in the first wireless network is retrieved, and it is determined whether to anchor the communication session in a second network according to the prediction information. [0007] Certain embodiments of the invention may provide one or more technical advantages. A technical advantage of one embodiment includes gathering location information of a mobile node to determine an anchor point to use for a communication session. Using the location information to determine an anchor point provides for efficiently using network resources during the communication session. Another technical advantage of one embodiment includes learning the location information to determine the anchor point to use for the communication session without manually configuring location information and without attempting to access proprietary geo-coded location databases of cellular service providers. Another technical advantage of one embodiment includes learning usage patterns of the mobile node, and using the usage patterns to select the anchor point for the communication session. Therefore, a communication session can be anchored more efficiently using network resources. [0008] Certain embodiments of the invention may include none, some, or all of the above technical advantages. One or more other technical advantages may be readily apparent to one skilled in the art from the figures, descriptions, and claims included herein. BRIEF DESCRIPTION OF THE DRAWINGS [0009] For a more complete understanding of the present invention and its features and advantages, reference is now made to the following description, taken in conjunction with the accompanying drawings, in which: [0010] FIG. 1 is a block diagram illustrating a system for processing location information to anchor a communication session; [0011] FIG. 2 is a flowchart for gathering the location information; [0012] FIG. 3 is a flowchart for processing the location information to generate prediction information; and [0013] FIG. 4 is a flowchart for determining whether to anchor the communication session according to the gathered location information. DETAILED DESCRIPTION OF THE DRAWINGS [0014] Embodiments of the present invention and its advantages are best understood by referring to FIGS. 1 through 4 of the drawings, like numerals being used for like and corresponding parts of the various drawings. [0015] FIG. 1 is a block diagram illustrating a system for processing location information to anchor a communication session. According to an embodiment, the system anchors a communication session for a mobile node in a network if there is an access point that can provide the mobile node access to the network. Anchoring is based on the location information gathered by the mobile node over a time interval or based on a usage pattern. The location information includes any suitable information, such as cellular identifiers or power measures that provide information about the location of the mobile node in a cellular network. [0016] According to the illustrated embodiment, system 10 operates to provide services, such as communication sessions, to endpoints, such as devices 128 and mobile node 100. Devices 128 may be any combination of hardware and/or software that provide communication services to a user. Devices 128 may include analog, digital, or Internet Protocol (IP) telephones, a personal computer such as a laptop or a desktop, a personal computer running a telephony application, a personal digital assistant, or any suitable device operable to communicate with system 10, particularly network 110 and/or PSTN 112. [0017] A communication session, or call, may refer to an active communication between endpoints, measured from endpoint to endpoint. Information is communicated during a communication session. Information may refer to voice, data, text, audio, video, multimedia, control, signaling, other information, or any combination of the preceding. System 10 may communicate information in packets or any other format or protocol. A packet may comprise a bundle of data organized in a specific way for transmission, and a frame may comprise the payload of one or more packets organized in a specific way for transmission. A packet-based communication protocol, such as IP, may be used to communicate the packets. [0018] Mobile node 100 represents any suitable device operable to communicate with a communication network via a wireless link. Mobile node 100 collects location information of cell sites 102 and reports the information to server 114 of network 110. Information may be cellular identifiers, power measures, latitude and/or longitudinal coordinates, time information, or any other information provided by cell sites 102 either as data in communications or the nature and strength of radio frequency signals from cell sites 102. Mobile node 100 collects the information during a communication session or when mobile node 100 is idle. Mobile node 100 includes any suitable arrangement of components operable to form the operations of mobile node 100, and may comprise logic, an interface, memory, other component, or any suitable combination of the preceding. Mobile node 100 may comprise, for example, a personal digital assistant, a computer such as a laptop, a cellular telephone, a mobile handset, or any other device operable to communicate with system 10. According to one embodiment, mobile node 100 may be operable to communicate with different types of networks. As an example, mobile node 100 may be operable to communicate with a cellular network and an IP wireless local area network (WLAN), such as a WiFi network. [0019] System 10 includes communication networks. A communication network allows devices, such as mobile node 100, to communicate with other devices. A communication network may comprise all or a portion of a public switched telephone network (PSTN), a public or private data network, a local area network (LAN), a metropolitan area network (MAN), a wide area network (WAN), a local, regional, or global communication or computer network, such as the Internet, a wireline or wireless network, an enterprise intranet, other suitable communication link, or any combination of the preceding. [0020] According to one embodiment, system 10 includes networks of different network types. A network type may be designated in accordance with the communication protocols and technologies used for the network. Examples of networks of different network types include cellular networks, WLANs, voice over IP (VOIP) networks, network types involving other communication protocols or technologies, or any combination of the preceding. The elements of system 10 can operate to permit mobile node 100 to maintain a communication session that is handed off between network types. For example, mobile node 100 can have a communication session that is handed off between a cellular network and a WLAN. [0021] A cellular network provides communication services for mobile node 100 using any suitable cellular protocol and technology. The cellular network may use various cellular protocols and technologies, including but not limited to global system for mobile communications (GSM), code division multiple access (CDMA), and any other appropriate analog or digital wireless protocol or technology. Furthermore, the cellular network may utilize signaling system 7 (SS7) protocol for signaling purposes. In the illustrated embodiment, the cellular network includes a series of overlapping cell sites 102. A cell site 102 may comprise any suitable element operable to provide cellular wireless services to mobile nodes 100 present in the service area of cell site 102. Even though cell site 102 is represented in a circular configuration, cell site 102 may provide service in any suitable configuration and/or geographic area. In one embodiment, cell site 102 includes a base transceiver station (BTS) 104 coupled to base station controller (BSC) 106, which covers a geographic region and communicates with mobile node 100 present in the service area of cell site 102. BTS 104 communicates signals to and from mobile node 100 through a wireless link, which is typically a radio frequency link. BSCs 106 communicate with each other and with a mobile switching center (MSC) 108. BSC 106 manages the operation of BTS 104. BSCs 106 and MSC 108 provide switch and intra-cellular soft handoff functionality for mobile node 100 traveling through the different coverage areas of cell sites 102. The cellular network includes any suitable number of BTSs 104, BSCs 106, MSCs 108, and other appropriate communication elements. [0022] A WLAN 126 provides communication services for mobile node 100 using any suitable wireless protocol and technology. WLAN 126 utilizes wireless standards, such as the 802.11 family of wireless standards, to provide wireless telephony services to mobile node 100. The 802.11 family of wireless standards includes, among others, 802.11a, 802.11b, and 802.11g. WLAN 126 provides communication services to mobile node 100 present in a service area of WLAN 126. WLAN 126 includes a WLAN access point 118, which covers a geographic region and communicates with mobile node 100 present in the service area of WLAN 126. Access point 118 communicates signals to and from mobile node 100 anchored with access point 118. Access point 118 represents a communication element, including hardware and any appropriate controlling logic, for providing wireless access to WLAN 126. Access point 118 uses any appropriate wireless standard or protocol. [0023] Communication network 110 represents any suitable network that provides communication services for mobile node 100 using any suitable wireline or wireless protocol. For example, network 110 utilizes circuit-switched and/or packet-based communication protocols to provide for wireline telephony services, such as IP. Network 110 may include a local area network (LAN), a metropolitan area network (MAN), a wide area network (WAN), a public land mobile network (PLMN), a network-based call signaling (NCS) network, a session initiation protocol (SIP) peer network, any other public or private data network, a local, regional, or global communication network such as the Internet, an enterprise intranet, other suitable wireline or wireless communication link, or any combination of the preceding. Network 110 may include any combination of network elements, such as gateways, routers, hubs, switches, and any other hardware and/or software that may implement any suitable protocol or communication. [0024] Public switched telephone network (PSTN) 112 represents communications equipment, including hardware and any appropriate controlling logic, through which any suitable network may communicate. PSTN 112 may include switches, wireline and wireless communication devices, and any other appropriate equipment for interconnecting PSTN 112 with other networks. PSTN 112 may include portions of public and private networks providing network transport services between various geographic areas and networks. In an embodiment, a gateway may facilitate the interaction between PSTN 112 and other networks, such as network 110, by converting communications between different communication protocols. [0025] In the illustrated embodiment, network 110 includes a server 114 that facilitates receiving and processing location information. Server 114 includes an information database 116 that stores location information. Location information represents information about cell sites 102, such as a unique identification. The unique identification may include a cellular identification, a carrier identification, a system identification, or any suitable identification that enumerates the geographical area for which mobile node 100 collects the information. The location information includes information collected by mobile node 100 to learn location information of various carriers in the vicinity of network 110 and, in one embodiment, the usage pattern of mobile node 100. To learn location information conventionally, server 114 may probe databases of cellular service providers or use a geographic mapping of wireless areas. However, the conventional method requires retrieving proprietary information of cellular service providers or conducting substantial work to generate a geographic mapping. In an embodiment, server 114 receives gathered location information without having to access the databases of cellular service providers. Location information may also represent a vector of information that provides different parameters of cell site 102 and/or mobile node 100. For example, the vector of location information may include a cellular identifier, the time of day the identifier was collected, and/or any suitable parameter. [0026] Server 114 processes the received location information into reports 120 that represent the collected location information. Reports 120 include location information received from one or more mobile nodes 100. Reports 120 may represent the location information in any suitable manner. For example, each mobile node 100 may have an associated report 120. As another example, server 114 may consolidate the location information received from mobile nodes 100 and store a consolidated report 120 that does not include duplicate location information. Reports 120 may also represent vectors that include location information, duration of a call, or other suitable parameters that provide for predicting a pattern of mobile node 100. [0027] Server 114 also includes prediction table 124 that allows server 114, using a prediction-developer 122, to predict whether to anchor mobile node 100 with access point 118 before mobile node 100 enters WLAN 126. Based on the location information of cell sites 102, server 114 uses a prediction-developer 122 to build prediction table 124 for use in making anchoring decisions. Prediction table 124 includes the cellular identifiers received in the location information, a determination of whether to anchor a call, and an associated anchor point to anchor with if the call is to be anchored. For example, each cellular identifier is associated with a prediction of whether to anchor a communication session with access point 118. Some cellular identifiers indicate anchoring is not required and do not have an associated anchor point, while other cellular identifiers have a prediction that includes an associated WLAN 126. In an embodiment, prediction table 124 does not include entries for cellular identifiers that do not have an associated anchor point. In this embodiment, mobile node 100 may determine whether its current cellular identifier is in prediction table 124. If prediction table 124 includes the cellular identifier, the call is anchored with the associated anchor point listed in prediction table 124. On the other hand, if prediction table 124 does not include the cellular identifier, the call is not anchored. Server 114 includes any suitable arrangement of components operable to receive location information and build prediction table 124, and may comprise logic, an interface, memory, other component, or any suitable combination of the proceeding. [0028] In an embodiment, server 114 uses the location information to intelligently determine which access point 118 to anchor mobile node 100 before mobile node 100 moves into the service area of WLAN 126. Server 114 may distribute the location information associated with mobile node 100 to mobile node 100. Therefore, mobile node 100 locally determines whether to anchor a communication session when a communication session begins. In another embodiment, server 114 uses classification and prediction techniques, in addition to the location information, to select an anchor point for mobile node 100. For example, mobile node 100 collects statistics on the parameters at the start of each call and reports the statistics to server 114. The collection may be in two classes: calls remaining active as mobile node 100 moves into WLAN 126 and calls terminated in the cellular network. Server 114 applies learning algorithms, such as Bayesian classifiers, to the reported data to build prediction table 124. As mobile node 100 collects the location information, server 114 learns the patterns of mobile node 100 and may predict the usage of mobile node 100. Because server 114 has learned the usage patterns of mobile node 100, server 114 predicts whether and when calls of mobile node 100 handoff to WLAN 126. In an embodiment, the prediction information is represented in prediction table 124 that provides a prediction identifying WLAN 126 in which to anchor the communication session. Prediction table 124 associates the prediction with each cellular identifier received from mobile node 100. Prediction table 124 takes any suitable form, such as being indexed by cellular identifier or cellular system. In an embodiment, mobile node 100 downloads its associated prediction information from the prediction table 124 and uses it to determine whether and where to anchor a new call. [0029] A communication session of mobile node 100 may be anchored at an anchor point of a network. Anchoring a communication session at the anchor point refers to having the anchor point process signaling of the communication session. A communication session is typically anchored during call setup, a first leg of a communication session, and mobile node 100 is re-attached to the anchor point during a handoff procedure, using a second leg of the communication session. Anchoring the communication session may reduce efficiency, especially in cases where a handoff to the network may not or cannot occur. For example, mobile node 100 may have a home IP network in the United States. If mobile node 100 visits an IP network in Singapore, and if the communication session is anchored in the United States, the communication session would require two international call legs. Accordingly, if handoff to the home IP network may not or cannot occur, then anchoring the communication session in the home IP network reduces efficiency. [0030] According to one embodiment, a communication session beginning in a first network is anchored in the second network if there is a likelihood of handoff to the second network as determined from location information processed into prediction information. The decision to anchor the session is made when the session begins for an outgoing and incoming call. For example, mobile node 100 initiates a communication session in cell site 102. Based on location information collected according to the usage pattern of mobile node 100, there is a likelihood the session will be handed off to WLAN 126. Therefore, the session is anchored with access point 118 at the start of the communication session, which provides for an efficient use of resources. [0031] In operation, mobile node 100 gathers location information as it travels through cell sites 102. Mobile node 100 gathers the location information within a configurable time interval or according to usage patterns of mobile node 100. For example, mobile node 100 gathers the location information over fifteen-minute intervals. Using time units as a triggering event provides for determining the boundary of interest adjacent to WLAN 126 by comparing the expected duration of an active session that may need to be handed off. As another example, mobile node 100 gathers the location information from the start of a call until mobile node 100 moves into the service area of WLAN 126. In this example, mobile node 100 gathers the location information even if it is outside the configured reporting interval and provides a vector of information to server 114. As yet another example, the usage pattern of mobile node 100 is based on presence information of mobile node 100. Mobile node 100 may report location information gathered for the full duration of the call. Gathering information in this way allows location server 112 to learn patterns of mobile node 100. A triggering event causes mobile node 110 to create a list of the location information seen and to send the list to server 114. The triggering event may include mobile node 100 roaming into network 110 with or without an active call, server 114 requesting the location information from mobile node 100, expiration of a time interval, or any other suitable event to cause server 114 to receive the location information. [0032] Server 114 stores the received location information in database 116 and uses prediction-developer 122 to build a prediction table 124. Server 114 uses the location information to build a predictor that includes whether calls handoff to WLAN 126. Server 114 instructs mobile node 100 whether to anchor the call initiated in a particular cell site 102 with access point 118 in WLAN 126. In another embodiment, mobile node 100 uses the prediction to determine whether to anchor an initiated call based on its current location. [0033] Mobile node 100 initiates a communication session. Server 114 determines the current location of mobile node 100. For example, mobile node 100 may be in cell site 102 a or WLAN 126 a. If mobile node 100 is in WLAN 126 a, the session is anchored with access point 118 a. If mobile node 100 is in cell site 102 a, server 114 determines whether to anchor the session with WLAN 126 based on information in prediction table 124. If cell site 102 a has an associated WLAN 126, according to information in prediction table 124, server 114 anchors the call with WLAN 126. However, if cell site 102 a does not have an associated WLAN 126, the session remains in the cellular network. The network in which the session is anchored, the cellular network or WLAN 126, completes the call to destination device 128 or destination mobile node 100. [0034] Modifications, additions, or omissions may be made to system 10. For example, mobile node 100 or server 114 may perform and implement the prediction. As another example, mobile node 100 may include the functionality to perform the operation of server 114, such as using the location information to build prediction table 124. The components of system 10 may be integrated or separated according to particular needs. For example, system 10 may include other suitable devices, such as a gateway, a home agent, a foreign agent, an authorization server, other device, or any combination of the preceding. A gateway represents any suitable device operable to interconnect with a network, and may convert communications between different communication protocols. A home agent of mobile node 100 refers to an agent that maintains the address of mobile node 100 and forwards data to mobile node 100. A foreign agent of mobile node 100 refers to an agent that provides the home agent of mobile node 100 with an address to which data for mobile node 100 may be forwarded. Moreover, the operations of system 10 may be performed by more, fewer, or other modules. Additionally, operations of system 10 may be performed using any suitable logic. [0035] FIG. 2 is a flowchart 20 for gathering the location information. At step 200, mobile node 100 monitors cell sites 102. Mobile node 100 monitors cell sites 102 during a communication session and when it is idle. From the monitoring, mobile node 100 collects location information from cell sites 102 at step 202. In an embodiment, mobile node 100 collects the location information from cell site 102 in which mobile node 100 is present. In another embodiment, mobile node 100 collects the location information from cell sites 102 that mobile node 100 does not enter. Mobile node 100 collects the location information through any suitable communication link, such as a radio frequency link or other wireless link. As discussed above, mobile node 100 may collect the location information as a vector of parameters illustrating the usage pattern of mobile node 100 or as identification information of cell site 102 that mobile node 100 enters during a time interval. In an embodiment, mobile node 100 collects the location information of cell site 102 while in the service area of cell site 102. [0036] At step 204, it is determined whether a triggering event occurs. A triggering event includes any suitable occurrence to initiate reporting the location information to server 114. For example, a triggering event includes a time interval expiring, roaming into a different network type, ending a communication session, or configuring the triggering event to occur at a particular time. At step 206, the location information is processed. At step 208, mobile node 100 determines whether to process the information locally or send the information to server 114 for remote processing. If mobile node 100 processes the information locally, mobile node 100 stores the location information at step 210. If mobile node 100 does not process the information locally, mobile node 100 sends the information to server 114 for processing at step 212. [0037] Modifications, additions, or omissions may be made to flowchart 20. Flowchart 20 may include more, fewer, or other steps. For example, mobile node 100 may automatically report collected location information when it is collected rather than waiting for a triggering event to occur to report the information. Additionally, steps may be performed in any suitable order. [0038] FIG. 3 is a flowchart 30 for processing the location information to generate prediction information. At step 300, server 114 receives the location information from mobile node 100. Server 114 analyzes the location information at step 302 to generate prediction information. For example, server 114 consolidates duplicate location information into report 120. In an embodiment, server 114 uses the received location information of mobile node 100 to determine whether to anchor sessions of mobile node 100 with WLAN 126 before anchoring is actually needed, and which WLAN 126 to anchor the session. Therefore, server 114 may anchor sessions of mobile node 100 with the appropriate WLAN 126 before mobile node 100 reaches its final service area. [0039] At step 304, server 114 determines whether the information was processed at mobile node 100. If server 114 determines that mobile node 100 processed the information, mobile node 100 stores the information at step 306. If server 114 determines that mobile node 100 did not process the information, server 114 stores the information at step 308. In an embodiment, database 116 in server 114 stores the information in reports 120. At step 310, location server 112 provides the location information to mobile node 100. Mobile node 100 may use the information to determine whether to anchor the call and where to anchor the call. [0040] Modifications, additions, or omissions may be made to flowchart 30. For example, mobile node 100 analyzes the gathered location information and generates the prediction information. Flowchart 30 may include more, fewer, or other steps. Additionally, steps may be performed in any suitable order. [0041] FIG. 4 is a flowchart 40 illustrating one embodiment of a method for determining whether to anchor the communication session according to the gathered location information. Mobile node 100 initiates a communication session at step 400. At step 402, it is determined whether the session is in WLAN 126. If the session is in WLAN 126, server 114 anchors the session with access point 118 at step 412. If the session is not in WLAN 126, server 114 receives the current location of mobile node 100 at step 404. [0042] At step 406, server 114 retrieves prediction information corresponding to the current location of mobile node 100. Prediction table 124 includes cellular identifiers, one of which identifies the current location of mobile node 100, and an associated WLAN 126 if the session is to be anchored in WLAN 126. From the information in prediction table 124, server 114 determines whether to anchor the session with WLAN 126 at step 408. If the cellular identifier identifying the current location of mobile node 100 does not have an associated WLAN 126 in prediction table 124, server 114 anchors the session with cellular network at step 410. If the cellular identifier identifying the current location has an associated WLAN 126, server 114 anchors the session with access point 118 at step 412. [0043] Modifications, additions, or omissions may be made to flowchart 40. For example, mobile node 100 includes prediction table 124 that has cellular identifiers and corresponding WLANs 126. In this example, mobile node 100 determines its current location and determines whether to anchor the session according to the location information in prediction table 124. Mobile node 100 does or does not anchor the session based on the information in prediction table 124. Flowchart 40 may include more, fewer, or other steps. Additionally, steps may be performed in any suitable order without departing from the scope of the invention. [0044] Although the present invention has been described in several embodiments, a myriad of changes, variations, alterations, transformations, and modifications may be suggested to one skilled in the art, and it is intended that the present invention encompass such changes, variations, alterations, transformations, and modifications as fall within the scope of the appended claims. Patent CitationsCited PatentFiling datePublication dateApplicantTitleUS6466556 *Dec 16, 1999Oct 15, 2002Nortel Networks LimitedMethod of accomplishing handover of packet data flows in a wireless telecommunications systemUS6490451 *Dec 17, 1999Dec 3, 2002Nortel Networks LimitedSystem and method for providing packet-switched telephonyUS6496691 *Dec 23, 1999Dec 17, 2002Bellsouth Intellectual Property CorporationEnhanced call return in a wireless telephone networkUS6721565 *Aug 7, 2000Apr 13, 2004Lucent Technologies Inc.Handover of wireless calls between systems supporting circuit and packet call modelsUS6973608 *Jul 3, 2002Dec 6, 2005Agere Systems Inc.Fault tolerant operation of field programmable gate arraysUS6980535 *Aug 28, 2003Dec 27, 2005Motorola, Inc.Passive probing for handover in a local area networkUS6980808 *Nov 27, 2001Dec 27, 2005Cisco Technology, Inc.Communication system with floating physical channelUS7016690 *Aug 13, 2003Mar 21, 2006Flarion Technologies, Inc.Methods and apparatus for updating mobile node location informationUS20030174688 *Jan 15, 2003Sep 18, 2003Lucent Technologies Inc.Subnetwork layer for a multimedia mobile networkUS20040235477 *May 22, 2003Nov 25, 2004Lucent Technologies Inc.Wireless handover using anchor terminationUS20040249915 *May 20, 2003Dec 9, 2004Russell Jesse E.Advanced multi-network client device for wideband multimedia access to private and public wireless networks* Cited by examinerReferenced byCiting PatentFiling datePublication dateApplicantTitleUS7706811 *Sep 19, 2006Apr 27, 2010Broadphone LlcSignal comparison-based location determining methodUS7877086 *Sep 8, 2009Jan 25, 2011Cisco Technology, Inc.Processing location information among multiple networksUS8125911Nov 26, 2008Feb 28, 2012Cisco Technology, Inc.First-hop domain reliability measurement and load balancing in a computer networkUS8170583Mar 9, 2010May 1, 2012Broadphone, LLCSignal comparison-based location determining methodUS8644828 *Feb 18, 2012Feb 4, 2014Wefi Inc.Method and system for selecting a wireless networkUS8762519 *Sep 18, 2009Jun 24, 2014Andrew LlcSystem and method for providing location services for multiple access networks from a single location serverUS9064275 *Jul 25, 2008Jun 23, 2015At&T Intellectual Property I, L.P.Systems and methods for charging and billing in converged communications networksUS9332486Dec 24, 2013May 3, 2016Wefi, Inc.Method and system for selecting a wireless networkUS9350442 *Jul 23, 2009May 24, 2016Alcatel LucentSystem architecture for providing communications in a wireless communication networkUS9629075 *Jul 22, 2015Apr 18, 2017Intel CorporationDistributed mobility anchoring for wireless networksUS20080070572 *Sep 19, 2006Mar 20, 2008Roy ShkediSignal Comparison-Based Location Determining MethodUS20090046678 *Aug 17, 2007Feb 19, 2009Industry-Academic Cooperation Foundation Of Kyung Hee UniversityMethod for predicting the mobility in mobile ad hoc networksUS20090325582 *Sep 8, 2009Dec 31, 2009Cisco Technology, Inc.Processing Location Information Among Multiple NetworksUS20100015926 *Jul 17, 2009Jan 21, 2010Luff Robert ASystem and methods to monitor and analyze events on wireless devices to predict wireless network resource usageUS20100106774 *Sep 18, 2009Apr 29, 2010Andrew LlcSystem and method for providing location services for multiple access networks from a single location serverUS20100128606 *Nov 26, 2008May 27, 2010Patel Rahul GFirst-hop domain reliability measurement and load balancing in a computer networkUS20100128635 *Oct 15, 2009May 27, 2010Buffmire Andrew WSystem, method and device for segregated and independent command and control of wireless service selection, routing, transport and/or deliveryUS20100159951 *Mar 9, 2010Jun 24, 2010Roy ShkediSignal Comparison-Based Location Determining MethodUS20120238287 *Feb 18, 2012Sep 20, 2012Wefi, Inc.Method and System for Selecting A Wireless NetworkUS20120281672 *Jul 23, 2009Nov 8, 2012Michael OhmSystem architecture for providing communications in a wireless communication networkEP2274883A2 *Apr 14, 2009Jan 19, 2011Agito Networks, Inc.Dynamic call anchoringEP2274883A4 *Apr 14, 2009Mar 19, 2014Shoretel IncDynamic call anchoring* Cited by examinerClassifications U.S. Classification455/456.1International ClassificationH04W64/00, H04W8/02Cooperative ClassificationH04W8/12European ClassificationH04W8/12Legal EventsDateCodeEventDescriptionMar 28, 2006ASAssignmentOwner name: CISCO TECHNOLOGY, INC., CALIFORNIAFree format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:JAGADEESAN, RAMANATHAN T.;CHUNG, ANDREW C.;DONOVAN, STEVEN R.;AND OTHERS;REEL/FRAME:017745/0699;SIGNING DATES FROM 20060222 TO 20060327Sep 28, 2010CCCertificate of correctionMar 18, 2013FPAYFee paymentYear of fee payment: 4Mar 22, 2017FPAYFee paymentYear of fee payment: 8RotateOriginal ImageGoogle Home - Sitemap - USPTO Bulk Downloads - Privacy Policy - Terms of Service - About Google Patents - Send FeedbackData provided by IFI CLAIMS Patent Services