Source: http://www.google.com/patents/US20080188227?ie=ISO-8859-1
Timestamp: 2016-02-11 04:02:29
Document Index: 134329059

Matched Legal Cases: ['Application No. 60', 'Application No. 60', 'Application No. 60', 'Application No. 60', 'Application No. 60', 'Application No. 60', 'Application No. 60', 'Application No. 60', 'Application No. 60', 'Application No. 60']

Patent US20080188227 - Methods and systems of processing mobile calls - Google PatentsSearch Images Maps Play YouTube News Gmail Drive More »Sign inPatentsA method of optimizing call dialing may include receiving a first call including one or more of a session identification number, a contact identification number, a contact name and a direct inward dialing number, determining a caller provider and a callee provider based on the first call, determining...http://www.google.com/patents/US20080188227?utm_source=gb-gplus-sharePatent US20080188227 - Methods and systems of processing mobile callsAdvanced Patent SearchPublication numberUS20080188227 A1Publication typeApplicationApplication numberUS 11/970,944Publication dateAug 7, 2008Filing dateJan 8, 2008Priority dateJan 8, 2007Also published asUS8805325, US9100500, US9167101, US9232076, US20080166999, US20080167019, US20080167020, US20080167039, US20150381805, WO2008085614A2, WO2008085614A3, WO2008085614A8, WO2008086350A2, WO2008086350A3Publication number11970944, 970944, US 2008/0188227 A1, US 2008/188227 A1, US 20080188227 A1, US 20080188227A1, US 2008188227 A1, US 2008188227A1, US-A1-20080188227, US-A1-2008188227, US2008/0188227A1, US2008/188227A1, US20080188227 A1, US20080188227A1, US2008188227 A1, US2008188227A1InventorsJacob Guedalia, Isaac David GuedaliaOriginal AssigneeJacob Guedalia, Isaac David GuedaliaExport CitationBiBTeX, EndNote, RefManPatent Citations (99), Referenced by (31), Classifications (16), Legal Events (6) External Links: USPTO, USPTO Assignment, EspacenetMethods and systems of processing mobile calls
US 20080188227 A1Abstract
receiving a first call comprising one or more of a session identification number, a contact identification number, a contact name and a direct inward dialing number; determining a caller provider and a callee provider based on the first call; determining cost information associated with one or more numbers corresponding to a callee; and routing a second call between the caller and the callee based on one or more of the caller provider, the callee provider and the cost information. 2. The method of clam 1, wherein receiving a first call comprises receiving a first call from a mobile device.
determining whether the caller provider is the same as the callee provider; if so, automatically dialing the direct inward dialing number; and if not, transmitting an access number to the caller. 4. The method of claim 1, wherein determining cost information comprises mapping at least a portion of the cost information to one or more numbers associated with the callee using one or more pre-defined rules.
a processor for optimizing call dialing by processing one or more of a session identification number, a contact identification number, a contact name and a direct inward dialing number to determine provider information associated with one or more of a caller and a callee. 6. The system of claim 5, further comprising:
a mapper for mapping cost information associated with calling the callee based on the determined provider information. 7. A method of determining an origin of an incoming cat the method comprising:
receiving, by a callee gateway, a call from a mobile device associated with a caller, wherein the call is transmitted over a network via a caller gateway; identifying an origin of the call; determining whether to accept or reject the call based on the origin; if the call is accepted, processing the call; and if the call is rejected, alerting the caller that the call cannot be completed. 8. The method of claim 7, wherein identifying an origin of the call comprises:
creating a first communication channel to bridge the call; creating a second communications channel that communicates with a plurality of servers; and transmitting an HTTP request to one or more of the plurality of servers, wherein the HTTP request comprises an indication of the origin of the call. 9. The method of claim 7, wherein identifying an origin of the call comprises:
decoding one or more DTMF tones that have been encoded to represent the origin of the call. 10. The method of claim 7, wherein identifying an origin of the call comprises:
receiving information associated with the origin via a data channel. 11. The method of claim 7, wherein the caller gateway and the callee gateway are located in different countries.
a caller gateway in communication with at least one mobile device; and a callee gateway in communication with at least one mobile device and the caller gateway, wherein the callee gateway receives information pertaining to a call wherein the callee gateway determines an origin of the call based on at least a portion of the received information. 13. A method of ascertaining information associated with a callee, the method comprising:
receiving a direct inward dialing number associated with a callee; comparing the direct inward dialing number to one or more entries in a consolidated general registry, wherein each entry comprises contact information; and if an entry having the direct dialing number is found, transmitting at least a portion of the contact information to the caller. 14. The method of claim 13, wherein the contact information comprises one or more of a telephone number, a screen name and an email address.
automatically connecting the call using one or more predetermined rules. 16. The method of claim 13, wherein transmitting at least a portion of the contact information to the caller comprises:
downloading a portion of the contact information in one or more stages such that image quality associated with the downloaded portion in each stages progressively improves. 17. A system for ascertaining information associated with a callee comprising:
one or more mobile devices; a processor in communication with the one or more mobile devices; and a central general registry in communication with at least one of the one or more mobile devices. 18. A method of filtering one or more contacts in an address book on a mobile device, the method comprising:
identifying one or more contacts in an address book associated with a mobile device; automatically filtering the one or more contacts in real time based on one or more predetermined criteria, wherein each predetermined criterion corresponds to a tab; and displaying the filtered contacts to the user on a mobile device, wherein the tab corresponding to each predetermined criterion includes the contacts associated with the predetermined criterion. 19. The method of claim 18, wherein automatically filtering the one or more contacts comprises filtering the one or more contacts based on one or more of the following:
whether a contact has a landline telephone number; whether a contact has a wireless telephone number; whether a contact belongs to the same carrier as the mobile device user; whether a contact has recently called the mobile device user; and whether the mobile device user has recently called a contact. Description
[0001] This application claims priority under 35 U.S.C. � 119(e) to U.S. Provisional Application No. 60/883,841, filed Jan. 8, 2007, U.S. Provisional Application No. 60/884,045 filed Jan. 9, 2007, U.S. Provisional Application No. 60/889,305, filed Feb. 12, 2007, U.S. Provisional Application No. 60/889,959, filed Feb. 15, 2007, U.S. Provisional Application No. 60/896,003, filed Mar. 21, 2007, U.S. Provisional Application No. 60/908,726, filed Mar. 29, 2007, U.S. Provisional Application No. 60/940,758, filed May 30, 2007, U.S. Provisional Application No. 60/942,557, filed Jun. 7, 2007, U.S. Provisional Application No. 60/945,931, filed Jun. 24, 2007, and U.S. Provisional Application No. 60/947,963, filed Jul. 4, 2007, the entireties of which are incorporated by reference herein.
[0002] As the mobile telecommunication industry grows, mobile subscribers are becoming increasingly more aware of their leverage in the market. They carefully compare service providers and call plans, and make educated choices before subscribing to a carrier and a service. Subscribers also continuously seek new and improved features to integrate into their mobile service such as enhanced chat, long distance service options, customized graphical user interfaces and the like.
[0003] Despite being informed consumers, mobile subscribers are often disadvantaged in the mobile market. For example, although a subscriber may be knowledgeable about their own calling plan subscription, subscribers are usually unaware of the cost per minute of a call to the calling destination. This puts a mobile subscriber at a disadvantage in making educated and economical calling choices.
[0004] Mobile subscribers would also welcome more long distance service options. A subscriber to a telecommunication carrier service typically needs a local access number to utilize the service. This usually involves selecting a number from a list of regional or area numbers, such as a preprinted list on a calling card, to find the access number closest to the subscriber's current location. The subscriber dials the local access number and is usually connected to a long distance service provider via a telephony network. Typically, the subscriber can then enter a target long distance telephone number, and the long distance service provider will route the call to a subscriber-specified number. The current approach has many disadvantages, however, such as having to purchase a phone care and locating a local access number. In addition, a subscriber who accidentally places a call using a non-local access number may incur long distance charges.
[0005] It is common for a subscriber to experience a significant delay after powering on his mobile device before he is able to access updated contact information in his address book. This is because the mobile device must contact and retrieve an updated contact list from a server. As such, subscribers may desire to access his address book while the contact information is being updated.
[0006] To keep pace with the constant evolution of mobile telephony, mobile subscribers are treated to a variety of applications designed to optimize their mobile communication experience. For example, subscribers can access the Internet with the mobile device, send chat messages to their contacts and the like. Subscribers can glean relevant and up-to-date information about their contacts in their address books by viewing presence-statuses, away messages, sometimes referred to as status messages, mood messages or the like. However, it is common for a subscriber's status message to read the same regardless of which contact views it. As such, a subscriber cannot customize his status message based on the contact who is viewing it.
[0007] A mobile subscriber may have one or more contacts in an address book that belong to different networks than the subscriber. It is often difficult for a subscriber to determine which network a contact is subscribed to, which precludes the subscriber from making informed decisions about how to optimally call the contact. As such, a subscriber would like to ascertain to which network a contact belongs so that the subscriber can optimize call-dialing to this contact.
[0008] It is often difficult to determine the origin of a Voice over IP call because the call usually does not contain typical country code identifiers. As such, service providers would like to determine the origin of incoming calls to determine whether to accept or reject the call.
[0009] A mobile subscriber may only have limited contact information for a callee. A subscriber may want to obtain further information associated with the callee in order to decide how best to contact the callee.
SUMMARY [0010] Before the present methods are described, it is to be understood that this invention is not limited to the particular systems, methodologies or protocols described, as these may vary. It is also to be understood that the terminology used herein is for the purpose of describing particular embodiments only, and is not intended to limit the scope of the present disclosure which will be limited only by the appended claims.
[0011] In an embodiment, a method of optimizing call dialing may include receiving a first call including one or more of a session identification number, a contact identification number, a contact name and a direct inward dialing number, determining a caller provider and a callee provider based on the first call, determining cost information associated with one or more numbers corresponding to a callee and routing a second call between the caller and the callee based on one or more of the caller provider, the callee provider and the cost information.
[0012] In an embodiment, a system for optimizing call dialing may include a processor for optimizing call dialing by processing one or more of a session identification number, a contact identification number, a contact name and a direct inward dialing number to determine provider information associated with one or more of a caller and a callee.
[0013] In an embodiment, a method of determining an origin of an incoming call may include receiving, by a callee gateway, a call from a mobile device associated with a caller, where the call is transmitted over a network via a caller gateway, identifying an origin of the call and determining whether to accept or reject the call based on the origin. If the call is accepted, the call may be processed. If the call is rejected, the caller may be alerted that the call cannot be completed.
[0014] In an embodiment, a system for determining an origin of an incoming call may include a caller gateway in communication with at least one mobile device and a callee gateway in communication with at least one mobile device and the caller gateway. The callee gateway, may receive information pertaining to a call, and may determine an origin of the call based on at least a portion of the received information.
[0015] In an embodiment, a method of ascertaining information associated with a callee may include receiving a direct inward dialing number associated with a callee, comparing the direct inward dialing number to one or more entries in a consolidated general registry, where each entry comprises contact information and if an entry having the direct dialing number is found, transmitting at least a portion of the contact information to the caller.
[0016] In an embodiment, a system of ascertaining information associated with a callee may include one or more mobile devices, a processor in communication with the one or more mobile devices and a central general registry in communication with at least one of the one or more mobile devices.
[0017] In an embodiment, a method of filtering one or more contacts in an address book on a mobile device may include identifying one or more contacts in an address book associated with a mobile device, automatically filtering the one or more contacts in real nine based on one or more predetermined criteria, where each predetermined criterion corresponds to a tab and displaying the filtered contacts to the user on a mobile device, where the tab corresponding to each predetermined criterion includes the contacts associated with the predetermined criterion.
[0018] FIG. 1 depicts a flow chart for implementing an exemplary call-cost feature on a mobile device.
[0019] FIG. 2 depicts a mobile device display of exemplar cost information according to an embodiment.
[0020] FIG. 3 depicts an exemplary system of providing cost information according to an embodiment.
[0021] FIG. 4 depicts an exemplary system of providing cost information according to an embodiment.
[0022] FIG. 5 illustrates flow chart for assigning an exemplary local access number according to an embodiment.
[0023] FIG. 6 illustrates a method of placing an exemplary long distance call using a local access number according to an embodiment.
[0024] FIG. 7 illustrates a flow chart for an exemplary method of accessing contact information on a subscriber's mobile device according to an embodiment.
[0025] FIG. 8 illustrates an exemplary system for implementing mobile address book interaction according to an embodiment.
[0026] FIG. 9 illustrates an exemplary method of providing contact information according to an embodiment.
[0027] FIG. 10 illustrates a diagram depicting a call originating in one country and terminating in a different country according to an embodiment.
[0028] FIG. 11 depicts a flow chart of an exemplary method of determining a call's point of origin according to an embodiment.
[0029] FIG. 12 illustrates a flow chart of an exemplary method of determining information associated with a callee according to an embodiment.
[0030] FIG. 13 illustrates an exemplary diagram of determining information associated with a callee according to an embodiment.
[0031] FIG. 14 illustrates a flow chart for an exemplary method of optimizing call dialing according to an embodiment.
[0032] FIG. 15 illustrates an exemplary graphical user interface illustrating a filter according to an embodiment.
[0033] FIG. 1 illustrates a flow chart for implementing an exemplary call-cost feature on a mobile device. A mobile device may include mobile or portable devices such as cellular phones, PDAs, media players or the like. A mobile device may have a processor and a processor-readable storage medium in communication with the processor.
[0034] As illustrated by FIG. 1, a price table database may receive 100 cost information from a price feed. A price feed provides real time pricing information for a product or service. For example, stock prices may be available to an online trader via a price feed.
[0035] In an embodiment, the price table database may be housed on a computing device, such as a server, and the cost information may include the cost per minute for a plurality of calling destinations or the like. Table 1 illustrates an exemplary price table database according to an embodiment.
Calling Destination
$0.33/minute
$0.56/minute
[0036] The price table database may receive 100 cost information from the price feed on a regular basis. In an embodiment, the price feed may include a rate sheet provided by a telephone service provider.
[0037] In an embodiment, at least a portion of the received cost information may be stored 105 in the price table database. For example, the price table database may receive a cost-per-minute for calling Canada. If the price table database does not currently include a cost-per-minute for Canada, the cost information may be added to the price table database. If the price table database includes a different cost-per-minute for Canada, the stored cost information may be replaced with the cost information from the price feed. In an embodiment, if the received cost information associated with a calling destination is less than the stored cost information associated with the calling destination, an alert may be generated. The alert may be used to notify a subscriber of the price discount associated with the particular calling destination. In an embodiment, the server may transmit the alert to a subscriber's mobile device to notify the subscriber of the price discount.
[0038] A mapper may use the cost information contained in the price table database to map 110 cost information to one or more phone numbers in a subscriber's address book. In an embodiment, the mapper may utilize pre-defined rules to map 110 cost information to a contact number. A contact is an entry in an address book that is accessible by a mobile device. A contact number is a mobile device number associated with a contact. In an embodiment, the mapper may map 110 cost information to one or more contact numbers using pre-defined rules. The pre-defined rules may be used to determine, for example, a calling destination, whether the phone number belongs to a landline or a mobile device, or the like. For example, in Israel, landlines are provisioned with the country code +972 followed by an area code ranging from ‘1’ to ‘9’, with the exception of ‘5.’ Mobile phone numbers typically begin with ‘5.’ If a subscriber has the phone number “972-2-5388-0234” in his address book, the mapper may use one or more pre defined rules to determine the contact number is a landline number is Israel. The mapper may use this information to map the corresponding cost per minute to one or more contact numbers in a subscriber's address book.
[0039] In an embodiment, the mapped cost information may be transmitted to the subscriber's mobile device for display to the subscriber. FIG. 2 depicts a mobile phone display of exemplary cost information according to an embodiment. As illustrated, the cost to call one or more contacts in a subscriber's address book may be displayed. For example, calling Jim on has mobile phone costs $0.0136/minute 200, whereas calling Jim on his landline phone costs $0.017/minute 205. The subscriber may use this information to make an informed calling decision regarding which number to call.
[0040] In an embodiment, cost information may be provided based on associated calling plans. As illustrated by FIG. 3, the price table database may include cost information such as mobile providers' calling plans 300, a cost-per-minute value 305 associated with the calling plans, a dialing prefix 310 provisioned for each calling plan and/or the like. In an embodiment, the price table database may receive this cost information from the price feed on a regularly updated basis.
[0041] In an embodiment, the mapper may map a contact's number with the subscriber's calling plan and the corresponding cost information may be displayed to a subscriber. One or more contacts in a subscriber's address book may be displayed with cost information based on the subscriber's and/or the contact's calling plan. For example, FIG. 3 illustrates exemplary information that may be displayed on a mobile device. A contact's number 315 may be listed with a cost-per-minute value 320 and a calling plan 325 associated with the number 315.
[0042] In an embodiment, the mapper may use a contact's phone number to determine calling destination information such as a contact's locale, whether the contact's number corresponds to a landline or a mobile phone or the like. After calling destination information is determined, the mapper may map at least a portion of the calling destination information to the subscriber's calling plan. For example, a subscriber may want to call a contact who has two numbers. The first number may be a landline in Israel while the second number may be a mobile phone in Israel. The mapper may match the subscriber's calling plan with the destination information to determine that cost information associated with calling the two numbers.
[0043] In an embodiment, multiple service providers may be used to place a call. In such an embodiment, the mapper may map cost information associated with all necessary providers so that a combined price may be displayed to a subscriber. For example, if a subscriber calls an overseas contact using a long-distance service provider, the cost-per-minute may reflect both the long distance provider's charges as well as the local mobile carrier's airtime charges.
[0044] FIG. 4 depicts an environment suitable for practicing the illustrative embodiments. A processor, such as a server 400 may include a mapper 405 and/or a price table database 410. The server 400 may be in communication with a price feed 415 and one or more mobile devices 420 via a network 425. The server 400 may be implemented on a stand-alone computer system or may be implemented by distributed components such as separate electronic devices.
[0045] In an embodiment, a subscriber may use a local access number to place a long distance call. A local access number is a local telephone number a subscriber may employ to connect to a certain long distance service provider. FIG. 5 illustrates an exemplary flow chart of a method for assigning a local access number according to an embodiment. A subscriber's locale information may be received 500 by a server. In an embodiment, a subscriber may use a mobile device to subscribe to a telecommunication service via a data line. For example, a subscriber may access a browser to transmit an HTTP request. Upon registration, a subscriber may provide locale information such as an area code and a telephone number, a zip code or the like corresponding to the subscriber's current location. The locale information may be communicated to a server.
[0046] In another embodiment, locale information may be automatically received 500 by a server. For example, the locale information may be transmitted via an HTTP browser to a server where it may be processed by a service delivery framework (SDF). The SDF may be aware of the subscriber locale information, such as a Mobile Systems International Subscriber Identity Number (MSISDN), and may insert such information into an HTTP header. The header may be transmitted to the server where the mapper may extract the locale information.
[0047] In an embodiment, the mapper may map 510 the locale information to a database of available access numbers. A local access number may be identified 520 based on the subscriber's current location and the identified local access number may be transmitted 530 to the subscriber's mobile device.
[0048] In an embodiment, the mapper may generate a list of long distance service providers having local access numbers corresponding to the subscriber's locale. The server may transmit the list via a data line to the subscriber's mobile device. The subscriber may select a long distance service provider, and may receive the corresponding local access number on his mobile device.
[0049] In an embodiment, the subscriber may use the local access number to connect to a chosen long distance service provider. The subscriber may manually input the local access number, followed by the desired long-distance phone number. Alternatively, the subscriber may employ an application, such as an address book, to automate this process. For example, a mobile device's address book may include a long-distance automatic dialing feature that allows for quick-dialing of a previously entered local access code.
[0050] In an embodiment, an existing address book may be populated with the local access number for future retrieval. In an embodiment, as a subscriber travels, his mobile device may receive and store new local access numbers based on his current location.
[0051] FIG. 6 illustrates a method of placing a long distance call using a local access number according to an embodiment. For example, subscriber who wants to make a third-party long distance call may register 600 for a long distance service using a browser on his mobile device. Upon registration, the subscriber may be asked to provide 605 locale information, such as a local telephone number with an area code. The locale information may be processed 610 by the server, and the subscriber may receive 615 a list of one or more long distance service providers. The subscriber may select 620 a long distance service provider and may receive 625 a local access number based on the selected long distance provider on his mobile device. The subscriber may employ the local access number for as long as he remains in his current location. If the subscriber's address book is equipped with a long distance auto-dial feature, it may be automatically populated with the local access number when the server transmits it to the mobile device. If the subscriber changes locations, he may access his account on the subscription site, enter a new telephone number and area code, and receive a new local access number. The subscriber's old access number may be stored for later use.
[0052] In an embodiment, a local access number may be automatically dialed for the subscriber, and may or may not require subscriber confirmation. As such, the subscriber may only need to specify the preferred long distance number to call. For example, a subscriber may select or input the preferred long distance number to call, and an application on the mobile device may place the call by automatically dialing the access code local to the subscriber's local information. As described above, the locale information may be ascertained based on the telephone number provided by the subscriber at sign-up or by extracting the subscriber locale information from an HTTP header.
[0053] For example, a mobile user who wants to place a long distance call may select a contact from his address book to call. The subscriber's long distance subscription service may ascertain the subscriber's location by extracting locale information from an HTTP header transmitted by the subscriber's phone or by the locale information the subscriber provided at sign-up. The server may map the subscriber's location to an appropriate local access number which may be sent to the subscriber's mobile device. The subscriber may make one or more selections to dial the received local access number. Alternatively, the service may auto-dial the local access number and connect the call without the subscriber being aware that a local access number has been dialed.
[0054] FIG. 7 illustrates a flow chart for an exemplary method of accessing contact information on a subscriber's mobile device according to an embodiment. When a subscriber first accesses a server-based mobile address book application, the subscriber may experience a significant delay while the address book attempts to retrieve the subscriber's address book from the server. In an embodiment, a cache of the address book may be created 700 before the subscriber's mobile device is powered off. The cache may include contact information stored in the subscriber's address book during the last application session. For example, the cache may include a contact's name, one or more telephone numbers associated with the contact, a status message associated with the contact and/or the like.
[0055] In an embodiment, a status message indicates whether the contact is online, offline or the like. A status message includes information relating to a status or state of a subscriber, and can be presented automatically to anyone who attempts to contact the subscriber. The status message may provide further information regarding the subscriber. In an embodiment, exemplary status messages may include “Having a bad day,” “In a meeting,” “At the gym,” or the like.
[0056] In an embodiment, the cache may be stored 710 on the subscriber's mobile device. When a subscriber powers on his mobile device, at least a portion of the cache may be displayed 720 to a subscriber until a fresh upload of contact information can be obtained from the server. For example, when a subscriber accesses an address book application after powering on his mobile device, the subscriber may be presented with a cached version of his address book that may include contacts' names, telephone numbers, status message and/or the like which were stored in the cache prior to tie mobile device being powered off.
[0057] In an embodiment, because the server may take a significant amount of time to upload a complete fresh address book, contacts may be updated in a particular order according to an embodiment. For example, the first several contacts that appear in a subscriber's mobile device display may have their information updated first. Alternatively, priority may be given to one or more predetermined contacts.
[0058] A problem may arise when a subscriber attempts to call a contact's telephone number using a cached address book. In an embodiment, the cached information may include a contact identification number associated with a contact and/or a unique session identification number. A contact identification number is a unique identifier associated with a certain contact in an address book. A session identification number is a unique identifier associated with a calling period. The unique session identification number may remain valid for the length of an entire calling period, which, in an embodiment, may be the period of time from when the application is powered up and connected until the time that the application is powered down. A contact identification number may be assigned to each contact, and may remain valid for the duration of a calling period. In an embodiment, the unique session identification number and the contact identification numbers may expire after the calling period has closed, thus rendering them invalid for subsequent calling sessions. As such, when a subscriber attempts to call a contact with stale status information, the application may attempt to dial in with an expired session identification number and/or reference an expired contact identification number, which may result in call failure. While a delay may exist while the server refreshes and updates a subscriber's contact information, a service provider may want to give a subscriber a feeling of being logged onto the network as soon as the subscriber's mobile device is powered on.
[0059] For example, in an embodiment, if a subscriber selects a contact from the cached address book having expired status information, the contact's phone number may not be immediately dialed. Instead, the subscriber's mobile device may dial a server and may dispatch the name of the desired callee across a network. The server may send back a session identification number to be utilized during the calling period and/or a contact information number that references the callee. In an embodiment, the server may also send a local access number to be used to contact the callee. Alternatively, the call may be completed without the use of a local access number.
[0060] In an embodiment, if a subscriber selects a contact from the cached contact list having stale status information, a prepare call may be sent to the server. The prepare call may include a session identification number, a callee's contact identification number, a callee's contact name and the like. The server may send back a new session identification number for the subscriber, a contact information number that references the callee, a local access number to be used to contact the callee and/or the like.
[0061] In an embodiment, if a subscriber selects a contact from the cached contact list having stale status information, a direct inward dialing (DID) number of the callee may be directly dialed, and the dual-tone multi-frequency (DTMF) tones of the caller may be appended to a dial-string associated with the call. A DID number is a feature offered by telephone companies for use with customer's private branch exchange. A telephone company may allocate a range of numbers all connected to the customers' PBX. As the PBX receives calls, the number that the caller dialed may also be presented so the PBX can route the call to the target callee. For example, DID numbers may be obtained by administrators of a VoIP network and assigned to a gateway in the network. The gateway may route incoming calls from the network to appropriate VoIP subscribers.
[0062] In an embodiment, a set of DIDs may be assigned to a gateway. The gateway may then reassign the DIDs to a particular mapping of caller-callee. For example, Caller A may have ten contacts, A-K. Each contact may be assigned a unique DID number. When Caller A selects a contact from his cached contact list, Caller A is, in effect, selecting the DID number associated with the contact.
[0063] In an embodiment, if a subscriber selects a contact from the cached contact list having expired status information, a callee's DID number may be directly dialed, and the DID number and the identification number of the caller may appear within the dial-string.
[0064] In an embodiment, a subscriber may use an address book on the subscriber's mobile device to call one or more contacts stored in the address book. The subscriber may communicate with these contacts by dialing the contact directly, by sending chat messages or the like. FIG. 8 illustrates an exemplary system for implementing mobile address book interaction according to an embodiment. In addition to being stored locally on a mobile device 800, the contact information in a subscriber's address book 805 may also be cached on a server 810 which may regularly update the address book information. The server may send information about the subscriber's contacts to the subscriber's mobile device 800 as it become available. In an embodiment, the subscriber's mobile device 800 may poll the server at specified intervals to receive updates about the subscriber's contacts. Updated information may be integrated into the subscriber's mobile address book 805 for the subscriber to access. In an embodiment, contact information may include a status message or the like.
[0065] As FIG. 8 illustrates, bi-directional communication 815 may exist between the server, the subscriber's mobile device and the contacts 820 who appear in the subscriber's address book. In an embodiment, the server may push information, such as a status message associated with the subscriber, to the contacts 820. The server may also pull information from the contacts 820 for transmission to the subscriber's mobile device.
[0066] For example, if the subscriber wishes to change his status message, the subscriber may set a new status message using his mobile device. The new status message may then be sent to the server to be propagated to the subscriber's contacts. When the server receives and processes the new status message, the server may send the new status message to all of the subscriber's contacts.
[0067] FIG. 9 illustrates a method of providing contact information according to an embodiment. A server may receive 900 one or more status messages, such as a holographic message, from a subscriber's mobile device. A holographic message relates to customized messages that differ based on which contact inquires about the subscriber's status. That is, different contacts may be presented with different messages depending on the identity of the contact. The present discussion is intended to comprehend a one-to-one correspondence between messages and contacts, but is not so limited, and also includes messages directed to subsets of more than one contact. For example, a subscriber's holographic message may read “I'm in a meeting” to work colleagues, but may read “I'm unavailable” to all other contacts.
[0068] In an embodiment, a subscriber may set a holographic message using the subscriber's mobile phone. The subscriber may identify a message for a specific contact. For example, a subscriber may set a holographic message that reads “I'll be home at 6:30 pm” to his wife. The subscriber may also set a holographic message for a specific contact group. For example, a subscriber may set a holographic message that reads “At the beach” to his friends.
[0069] In an embodiment, the holographic messages set by a subscriber may be sent to the server to be transmitted to the contacts in the subscriber's contact book. The server may store 910 a holographic message and corresponding contact or contact group. The server may transmit 920 the holographic message to the mobile phones of the appropriate contacts based on the contact's name, the contacts group or the like. In an embodiment, the server may integrate 930 the holographic message into an address book associated with a contact. The server may transmit one or more instructions to a contact's mobile device instructing the mobile device to display the holographic message.
[0070] In an embodiment, a list of most-recently called contacts may be kept. For example, the list may reflect the last ten contacts a subscriber called, chatted with, changed a status message for, or the like. Typically, a subscriber's address book is stored on a server, and a push presence technique is utilized to access contact information, such as a status message or the like. In an embodiment, the push presence technique requires a subscriber to retrieve the latest contact information from the server. However, a subscriber who as many contacts must access the server numerous times in order to view contact information, which may drain the battery of the subscriber's mobile device. As such, a list of most-recently called contacts may be kept. This list may be stored on a subscriber's mobile device or on the server. If the list is stored on the server, the server must only push the contact information associated with the contacts in the most-recently called list instead of the contact information for every contact in the subscriber's address book.
[0071] In an embodiment, a gateway may decide to accept or reject a call based on the call's point of origin. For example, a call may originate in one country and terminate in a different country. FIG. 10 illustrates a diagram depicting a call originating in one country and terminating in a different country according to an embodiment. FIG. 11 depicts a flow chart of an exemplary method of determining a call's point of origin according to an embodiment.
[0072] In an embodiment, a caller may select 1100 a contact to call via the caller's mobile device. As illustrated by FIG. 10, the caller 1000 may be located in the United Kingdom, while the callee 1005 may be located in Germany. The call may be sent from the caller's mobile device 1010 and received 1105 by a caller gateway 1015, or a gateway associated with the caller's location. In an embodiment, the caller gateway may reside on a server. In the example illustrated by FIG. 10, the callee gateway 1015 is a UK Gateway 1015. The call may be transmitted 1110 over a network 1020, and may be received 1115 by a callee gateway 1025, or a gateway associated with the callee's location. In an embodiment, the callee gateway may reside of a server. In the example illustrated by FIG. 10, the callee gateway is a Germany Gateway 1025. In an embodiment, the callee gateway 1025 may process the call as a mobile-terminated call to the callee's mobile device 1030.
[0073] In an embodiment, a callee gateway may determine 1120 whether to accept or reject a call based on the origin of the call. In an embodiment, out of band signaling may be employed 1125 to make this determination. In an embodiment, a first communication channel may be created to bridge the call. The first communication channel may be a standard communication channel. In an embodiment, the first communication channel may be HTTP. In an embodiment a second communication may be created. The second communication channel may serve as a communication channel between a plurality of servers. In an embodiment, before a call is transmitted, an HTTP request may be transmitted to one or more servers on the second communication channel alerting the servers of the origin of the call. For example, in the example illustrated by FIG. 10, a caller may select a contact from an address book. Before the call is transmitted, an HTTP request may be transmitted to one or more servers on the communication channel alerting the servers that the call about to be processed is originating from the United Kingdom. As such, the alerted servers will be notified as to the call's country of origin before the call reaches its final destination.
[0074] In an embodiment, in-band signaling audio may be employed 1130 to identify the origin of a call. In an embodiment, one or more DTMF tones may be used to identify the origin of the call. Before a call is connected to a callee, one or more DTMF tones may be inserted into the call. These tones may be heard by the callee as a series of pings. In an embodiment, the DTMF tones may be encoded to represent the country of origin. The server that receives the call may interpret the DTMF tones to ascertain the country of origin. An indication of the country of origin may be transmitted to the callee gateway, which may determine whether to accept or reject the call
[0075] In an embodiment, in-band signaling non-audio may be employed 1135 to determine the origin of a call. In an embodiment, the network may employ an audio channel and a data channel. The data channel may be used for sending data as well as a protocol for allowing the caller gateway and callee gateway to communicate with each other. In an embodiment, information associated with the call origin may be sent to the callee gateway via the data channel. In an embodiment, the origin information may be sent in a text message, in a data message or the like. In an embodiment, a data message may include a data protocol or the like.
[0076] In an embodiment, after the country of origin is ascertained from an incoming call, the callee gateway may use this information to decide 1120 whether to accept or refuse a call. If the call is accepted, the call may be routed 1140 through the callee gateway to the callee's mobile device. If the call is refused, the callee may be alerted 1145 that the call could not be completed,
[0077] In an embodiment, a caller may use a portion of information regarding a callee to ascertain other information pertaining to the callee. For example, a caller may know a DID number corresponding a contact, however, the caller may be unaware of the contact's screen name, account name, email address or the like. If the caller directly dials the contact's DID number, he may incur long distance charges that he may not incur if he contacts the callee via the callee's screen name.
[0078] FIG. 12 illustrates a flow chart of an exemplary method of determining information associated with a callee according to an embodiment. FIG. 13 illustrates an exemplary diagram of determining information associated with a callee according to an embodiment.
[0079] In an embodiment, a caller 1230 may dial 1200 a DID number associated with a callee 1235. The DID number may be received 1205 by a server which may compare 1210 the DID number to one or more entries in a consolidated general registry 1240. In an embodiment, a consolidated general registry 1240 may include contact information associated with a subscriber, such as the subscriber's telephone number, screen name, email address and/or the like and may reside on a server. The server may use a portion of information transmitted from a caller to identify 1215 other information corresponding to the callee 1235. For example, if a caller 230 dials a callee's DID number, the consolidated general registry 14 may use the DID number to determine that the callee 1235 also has a screen name. In an embodiment, at least a portion of the contact information may be transmitted to the caller. In an embodiment, one or more images, such as the transmitted contact information, may be downloaded to a mobile device in one or more stages. In an embodiment, an images may be downloaded progressively in one or more stages as the user continues to use the mobile device. In an embodiment, an image may be displayed in low resolution in a first stage, but with each subsequent stage, the image quality associated with the image may progressively improve. For example, when a user first powers on his mobile device, the user's address book may appear in low resolution. After a certain period of time, the resolution and image quality may improve. After a certain period of time, the image quality and resolution may further improve.
[0080] Table 2 illustrates an exemplary entry in the consolidated general registry according to an embodiment.
3024562786
isapr25
isapr25@aol.com
isapr25@gmail.com
[0081] For example, if a caller 1230 wants to contact the callee 1235 identified by Table 2, he may dial the callee's DID number because this is the only contact information he has regarding the callee 1235. The server may match the received DID number to the screen name isapr25 as illustrated by Table 2. The callee's screen name may be transmitted 1220 back to the caller 1230 and the caller 1230 may be provided the option of contacting the callee 1235 using her screen name. In an embodiment, the call may automatically be completed 1225 using a predetermined method. For example, the call may be completed using the least expensive method. In an embodiment, the call may be transmitted through a gateway 1245 which may connect the call to the callee 1235.
[0082] In an embodiment, call dialing may be optimized so that a call is processed more efficiently. Optimization may involve identifying to which provider a caller and a callee belong, and deciding how to route a call between the two based on at least the provider information and cost information.
[0083] FIG. 14 illustrates a flow chart for an exemplary method of optimizing call dialing according to an embodiment. In an embodiment, a caller may select 1300 a contact from an address book. A first call, such as a prepare call, may be sent 1305 to a server. In an embodiment, the first call may include one or more of a session identification number, a callee's contact identification number, a callee's contact name, a DID number and the like. In an embodiment, a DID number may include one or more of a country code and a unique identifier associated with the mobile provider.
[0084] In an embodiment, the server may use the information contained in the first call to determine how to best optimize call dialing. For example, the server may determine 1310 a provider associated with the caller and a provider associated with the callee. In an embodiment, if a caller and a callee are subscribers to the same provider, the server may connect a second call using direct dial. In an embodiment, the second call may be a voice call. For example, if the caller is a subscriber to Provider A, and the callee also belongs to Provider A's network, the server may automatically connect the caller to the callee's number.
[0085] In an embodiment, if a caller belongs to a different network than the callee, the server may provide an access number that may serve as a gateway through which to connect to a third party provider network, such as a third party VoIP provider network. In an embodiment, an access number may be returned to the caller. The caller may dial the access number to reach the callee. Routing the second call through a third party network may reduce the charges incurred and the call may be processed more quickly and efficiently.
[0086] In an embodiment, a mapper, such as that illustrated by FIG. 1, may use the cost information contained in the price table database to map 1315 cost information to the callee's phone number. For example, if a caller dials a callee that has two possible phone numbers, the server may determine 1320 how to optimize call dialing by determining whether the callee is a subscriber of the callee's network for either phone number and the cost information associated with the callee's phone numbers. The server may use this information to call 1325 the callee.
[0087] In an embodiment, a mobile device may include a filter that sorts one or more contacts in an address book based on certain criteria. FIG. 15 illustrates an exemplary graphical user interface illustrating a filter according to an embodiment.
[0088] In an embodiment, one or more contacts from an address book 1430 on a mobile device 1435 may be automatically filtered in real-time. In an embodiment, filtered contacts may be displayed under one or more tabs for increased accessibility. FIG. 15 illustrates exemplary tabs 1400 such as “landline,” 1405 “Wireless,” 1410 “My Carrier,” 1415 “Recent Received” 1420 and “Recent Called” 1425.
[0089] In an embodiment, the “Landline” tab 1405 may include one or more contacts having landline telephone numbers and/or their landline telephone numbers. The “Wireless” tab 1410 may include one or more contacts having wireless telephone numbers, and their corresponding wireless telephone numbers. The “My Carrier” tab 1415 may include one or more contacts that belong to the same carrier or provider as the user. In an embodiment, one or more contacts may be filtered through auto-detection of a user's network based on the user's phone number. In an embodiment, the user's phone number may include an identifier string that is unique to the cellular provider.
[0090] In an embodiment, the “Recent Received” tab 1420 may include one or more contacts that have recently called the user. In an embodiment, this tab 1420 may include one or more contacts that have called the user within a predefined period of time. For example, only the contacts that have called the user within the past twenty-four hours may be displayed. Alternatively, this tab 1420 may include one or more predefined number of contacts. For example, only the last ten contacts that have called the user may be displayed.
[0091] In an embodiment, the “Recent Called” 1425 tab may include one or more contacts that the user has recently called. In an embodiment, this tab 1425 may include one or more contacts that the user has called within a predefined period of time. For example, only the contacts that the user has called within the past twenty-four hours may be displayed. Alternatively, this tab 1425 may include one or more predefined number of contacts. For example, only the last ten contacts that the user has called may be displayed. Additional and/or alternate tabs may be used within the scope of this disclosure.
[0092] It will be appreciated that various of the above-disclosed and other features and functions, or alternatives thereof, may be desirably combined into many other different systems or applications. Also that various presently unforeseen or unanticipated alternatives, modifications, variations or improvements therein may be subsequently made by those skilled in the art which are also intended to be encompassed by the following claims.
Patent CitationsCited PatentFiling datePublication dateApplicantTitleUS4751728 *Mar 27, 1987Jun 14, 1988Treat John MTelephone call monitoring, metering and selection deviceUS4799253 *Jul 20, 1987Jan 17, 1989Motorola, Inc.Colocated cellular radiotelephone systemsUS5570417 *Mar 28, 1995Oct 29, 1996Lucent Technologies Inc.System for automatically providing customer access to alternative telephony service providersUS5577100 *Jan 30, 1995Nov 19, 1996Telemac Cellular CorporationMobile phone with internal accountingUS5635940 *Feb 2, 1994Jun 3, 1997Hickman; Paul L.Communication configurator and method for implementing sameUS5848128 *Feb 29, 1996Dec 8, 1998Lucent Technologies Inc.Telecommunications call preservation in the presence of control failureUS5878122 *Feb 7, 1997Mar 2, 1999Northern Telecom LimitedLong distance service bureauUS5946618 *Apr 10, 1997Aug 31, 1999Qualcomm IncorporatedMethod and apparatus for performing position-based call processing in a mobile telephone system using multiple location mapping schemesUS6044263 *Dec 18, 1996Mar 28, 2000Ericsson Inc.Method for providing a location independent dialing procedure within a mobile telecommunications networkUS6188762 *Dec 1, 1997Feb 13, 2001Stephen ShoosterWeb call center/PSTN to TCPIP internet networkUS6205126 *Sep 30, 1997Mar 20, 2001Ericsson Inc.Method and apparatus for automatically determining an ISP local access number based on device locationUS6333931 *Dec 28, 1998Dec 25, 2001Cisco Technology, Inc.Method and apparatus for interconnecting a circuit-switched telephony network and a packet-switched data network, and applications thereofUS6564261 *May 9, 2000May 13, 2003Telefonaktiebolaget Lm Ericsson (Publ)Distributed system to intelligently establish sessions between anonymous users over various networksUS6618590 *Dec 10, 1999Sep 9, 2003Gte Wireless Service CorporationUse of mobile unit to provide delivery path optimization to land-based unitUS6678364 *Jun 7, 2001Jan 13, 2004Bellsouth Intellectual Property CorporationSystem and method for cost estimation of a long distance callUS6687362 *Feb 11, 2000Feb 3, 2004Hallmark Cards, IncorporatedAutomatic address book update systemUS6697858 *Aug 14, 2000Feb 24, 2004Telephony@WorkCall centerUS6707811 *Jan 30, 2001Mar 16, 2004Estara, Inc.Internet telephony for ecommerceUS6775375 *Mar 20, 2002Aug 10, 2004At&T Corp.Service and information management system for determining, replicating or correcting failed calls in a telecommunications networkUS6850762 *Jun 22, 2000Feb 1, 2005Sonera OyjProcedure and system for setting up a telecommunication connectionUS6917610 *Dec 30, 1999Jul 12, 2005At&T Corp.Activity log for improved call efficiencyUS7085260 *Aug 22, 2001Aug 1, 2006Lucent Technologies Inc.Internet protocol based wireless call processingUS7110772 *Jun 25, 1999Sep 19, 2006Avaya Technology Corp.System for providing location independent uniform service access for communication subscribersUS7280652 *Sep 13, 2004Oct 9, 2007Research In Motion LimitedHandheld electronic device having improved phone call log, and associated methodUS7369650 *Jun 4, 2004May 6, 2008At&T Corp.Service and information management system for a telecommunications networkUS7471692 *Jan 17, 2002Dec 30, 2008Utstarcom, Inc.Method and apparatus for maximizing call connect rate in a remote access applicationUS7480723 *Apr 8, 2003Jan 20, 20093Com CorporationMethod and system for providing directory based servicesUS7620404 *Dec 22, 2005Nov 17, 2009Pascal ChesnaisMethods and apparatus for organizing and presenting contact information in a mobile communication systemUS7634509 *Nov 7, 2003Dec 15, 2009Fusionone, Inc.Personal information space management system and methodUS20010038624 *Jan 30, 2001Nov 8, 2001Greenberg Jeffrey DouglasInternet telephony for ecommerceUS20020013163 *May 23, 2001Jan 31, 2002O'prey GerryCellular communications deviceUS20020099670 *Jan 25, 2001Jul 25, 2002Jakobsson Bjorn MarkusCall originator access control through user-specified pricing mechanism in a communication networkUS20020129103 *Oct 9, 2001Sep 12, 2002Birkler J?Ouml;RgenInstant messaging presence service protocolUS20020169984 *May 9, 2001Nov 14, 2002Kumar Gopikrishna T.Session management for wireless E-commerceUS20020193107 *Feb 15, 2002Dec 19, 2002Nascimento Oswaldo L. DoWireless/wireline communicationUS20030046405 *Mar 26, 2001Mar 6, 2003O'neill Alan WProcessing network address identifiersUS20030060211 *Aug 27, 1999Mar 27, 2003Vincent ChernLocation-based information retrieval system for wireless communication deviceUS20030091024 *Sep 27, 2001May 15, 2003Siemens Information And Communications Networks, Inc.Transparent interchangeable network (TIN)US20030115138 *Dec 17, 2001Jun 19, 2003International Business Machines CorporationBilling for use of a telephony deviceUS20030118175 *Nov 26, 2002Jun 26, 2003Ayman HaririUniversal point of contact identifier system calling device and methodUS20030148790 *Feb 1, 2002Aug 7, 2003Microsoft CorporationMethod and system for managing changes to a contact databaseUS20030190025 *Feb 19, 2003Oct 9, 2003Koji OkamuraCommunication apparatus, information display method, incoming call display method, incoming call history display method, programs for implementing the methods, and storage medium in which the program is storedUS20040019539 *Dec 17, 2002Jan 29, 20043Com CorporationPrepaid billing system for wireless data networksUS20040037396 *Aug 1, 2003Feb 26, 2004Gray Thomas A.Generation of availability indicators from call control policies for presence enabled telephony systemUS20040044771 *Aug 15, 2002Mar 4, 2004Embrace Networks, Inc.Method and apparatus for a client connection managerUS20040156394 *Jan 16, 2004Aug 12, 2004Ilkka WestmanHandling of user identityUS20040165714 *Feb 19, 2004Aug 26, 2004AlcatelDevice for the management of communications by the selection of terminals and the communication mediumUS20040202117 *Dec 30, 2003Oct 14, 2004Wilson Christopher Robert DaleMethod, system and apparatus for messaging between wireless mobile terminals and networked computersUS20040203643 *Jun 13, 2002Oct 14, 2004Bhogal Kulvir SinghCommunication device interaction with a personal information managerUS20040213209 *Apr 22, 2003Oct 28, 2004O'connor NeilProcessing of communication session request messagesUS20040229644 *Dec 11, 2000Nov 18, 2004Anders HeieMethod and apparatus for changing phone number information in an electronic phonebookUS20050025043 *Jul 29, 2003Feb 3, 2005Harry MussmanSystem and method for providing alternate routing in a networkUS20050027867 *Jul 29, 2003Feb 3, 2005Sbc Knowledge Ventures, L.P.Presence enhanced telephony service architectureUS20050033852 *Jul 14, 2003Feb 10, 2005Jouko TenhunenSystem, apparatus, and method for providing presence boosted message service reportsUS20050036597 *Aug 14, 2003Feb 17, 2005International Business Machines CorporationTelecommunications system for minimizing fees paid to telecommunications service providers by selecting the optimum provider for each telephone call from a group of available providers based upon tracked measurements of different sets of conditions determining providers' feesUS20050059418 *Sep 17, 2003Mar 17, 2005Sony Ericsson Mobile Communications AbSystem and Method of Sharing a Contact List Among Mobile PhonesUS20050070230 *Sep 26, 2003Mar 31, 2005Das Kamala PrasadMethod for management of voice-over IP communications of various relative priority levelsUS20050102257 *Nov 7, 2003May 12, 2005Onyon Richard M.Personal information space management system and methodUS20050138571 *Dec 18, 2003Jun 23, 2005Keskar Dhananjay V.Dynamic detection of device characteristicsUS20050157858 *Nov 24, 2003Jul 21, 2005Mahesh RajagopalanMethods and systems for contact managementUS20050163065 *Apr 11, 2003Jul 28, 2005Koninklijke Philips Electroics N.V.Telecommunication system with message based controlUS20050182798 *Feb 12, 2004Aug 18, 2005Microsoft CorporationRecent contacts and itemsUS20050198031 *Mar 4, 2004Sep 8, 2005Peter PezarisMethod and system for controlling access to user information in a social networking environmentUS20050198172 *Dec 20, 2004Sep 8, 2005Barry AppelmanOrganizing entries in participant lists based on communications strengthsUS20050221847 *Apr 1, 2004Oct 6, 2005Matthias BrehlerNetworked wireless communications device programmed to identify and eliminate probable multipath errors to enhance accuracy in correcting sleep clock for thermally induced errorsUS20050273512 *Jun 7, 2005Dec 8, 2005Lg Electronics Inc.Method for reestablishing session of client in mobile terminalUS20060023701 *Jul 19, 2005Feb 2, 2006Matsushita Electric Industrial Co., Ltd.IP telephone system, IP telephone apparatus and method for identifying destination userUS20060031368 *Jun 16, 2004Feb 9, 2006Decone Ian DPresence management in a push to talk systemUS20060159456 *Jan 18, 2005Jul 20, 2006Fujitsu LimitedSystem and method for conserving resources in an optical storage area networkUS20060168326 *Sep 19, 2005Jul 27, 2006Avaya Technology Corp.Dial plan transparency for fragmented networksUS20060173961 *Feb 1, 2005Aug 3, 2006Microsoft CorporationPeople-centric view of emailUS20060205400 *Mar 17, 2005Sep 14, 2006Kabushiki Kaisha ToshibaCommunication system and mobile station thereforUS20060209690 *Mar 17, 2005Sep 21, 2006Microsoft CorporationSystem and method for generating a dynamic prioritized contact listUS20060236388 *Apr 14, 2005Oct 19, 2006Sbc Knowledge Ventures, L.P.Method and apparatus for voice over internet protocol telephony using a virtual private networkUS20060246877 *Apr 29, 2005Nov 2, 2006Siemens Communications, Inc.Cellular telephone network with record keeping for missed callsUS20060248146 *Apr 27, 2005Nov 2, 2006Wilk Tomasz FMethod and system for status reportingUS20070005776 *Jun 30, 2006Jan 4, 2007Irontrack Technology, Inc.Method and system to use a telephone extension number to identify a session, such as an internet session that browses real estate informationUS20070016682 *Jul 26, 2005Jan 18, 2007Research In Motion Ltd.Method and system for coordinating device setting between a communications client and its host deviceUS20070060100 *Sep 14, 2005Mar 15, 2007Telemac CorporationSystems and methods for mobile station service controlUS20070064607 *Aug 17, 2006Mar 22, 2007Moon Jang WNetwork operator brokering system and telephone system for providing optimal routing path for voice call using the same and providing method thereofUS20070071006 *Sep 26, 2005Mar 29, 2007Peter BoschDelivery of communications services in developing regionsUS20070112964 *May 15, 2006May 17, 2007Jacob GuedaliaCaller-callee association of a plurality of networked devicesUS20070143397 *Feb 27, 2007Jun 21, 2007Iskoot, Inc.Caller-Callee Association of a Plurality of Networked Devices with Direct Dial Through Thin ClientUS20070281676 *Jun 1, 2006Dec 6, 2007Motorola, Inc.Multi model address bookUS20080037524 *Aug 17, 2007Feb 14, 2008Koch Robert ARemote Control Telephone Dialing System and MethodUS20080056235 *Aug 31, 2006Mar 6, 2008Syniverse Technologies, Inc.Cellular-to-VoIP call establishment systems, methods, devices, and computer softwareUS20080070579 *Sep 14, 2006Mar 20, 2008Pankaj KankarMethod and a system for minimizing roaming cost in a mobile communication networkUS20080076409 *Aug 31, 2006Mar 27, 2008Skype LimitedWireless device for voice communicationUS20080159261 *Dec 28, 2006Jul 3, 2008Lucent Technologies Inc.SYSTEM AND METHOD FOR PROCESSING CALLS TO VoIP DEVICES USING THE CALLED PARTY'S EMAIL ADDRESSUS20080166999 *Nov 30, 2007Jul 10, 2008Jacob GuedaliaMethods and systems of implementing call-cost features on a mobile deviceUS20080167019 *Nov 30, 2007Jul 10, 2008Jacob GuedaliaMethods and systems of providing status message calling featuresUS20080167020 *Nov 30, 2007Jul 10, 2008Jacob GuedaliaMethods and systems of accessing contact information on a mobile deviceUS20080167039 *Nov 30, 2007Jul 10, 2008Jacob GuedaliaMethods and systems of providing local access number calling featuresUS20080181165 *Jan 9, 2008Jul 31, 2008Jacob GuedaliaMethod and system for transmitting audio data between computing devicesUS20080192910 *Feb 12, 2008Aug 14, 2008Jacob GuedaliaMethods and systems for performing authentication and authorization in a user-device environmentUS20080244023 *Mar 31, 2008Oct 2, 2008Iskoot Inc.Methods and systems for performing server-based mobile chatUS20080263170 *Aug 30, 2006Oct 23, 2008Alain CaronMethod and System for Communicating Message Notifications to Mobile DevicesUS20080305782 *Jun 9, 2008Dec 11, 2008Isaac David GuedaliaTelecommunication Call Support for Mobile Devices with Presence FeaturesUS20090190738 *Jul 30, 2009Iskoot, Inc.Methods and systems for propagating information across a network* Cited by examinerReferenced byCiting PatentFiling datePublication dateApplicantTitleUS7925265 *Oct 14, 2005Apr 12, 2011Novatel Wireless, Inc.Method and apparatus for routing voice traffic over a residential gatewayUS8391848Jun 9, 2008Mar 5, 2013Qualcomm Iskoot, Inc.Telecommunication call support for mobile devices with presence featuresUS8494506 *Feb 11, 2010Jul 23, 2013Research In Motion LimitedCall destination number mapping methods, devices and systemsUS8611894 *Aug 9, 2009Dec 17, 2013Qualcomm IncorporatedApparatus and method for destination phone number string creationUS8649762 *Sep 30, 2011Feb 11, 2014Cox Communications, Inc.Carrier network determination for providing real-time customer feedback of call informationUS8660564Apr 5, 2011Feb 25, 2014Novatel Wireless, Inc.Method and apparatus for routing voice traffic over a residential gatewayUS8805325Nov 30, 2007Aug 12, 2014Qualcomm Connected Experiences, Inc.Methods and systems of implementing call-cost features on a mobile deviceUS8805356Jan 25, 2013Aug 12, 2014Qualcomm Connected Experiences, Inc.Telecommunication call support for mobile devices with presence featuresUS8942670Feb 10, 2014Jan 27, 2015Cox Communications, Inc.Carrier network determination for providing real-time customer feedback of call informationUS9088641Jan 9, 2008Jul 21, 2015Qualcomm IncorporatedMethod and system for transmitting audio data between computing devicesUS9100500Nov 30, 2007Aug 4, 2015Qualcomm IncorporatedMethods and systems of providing local access number calling featuresUS9100501Feb 12, 2008Aug 4, 2015Qualcomm IncorporatedMethods and systems for performing authentication and authorization in a user-device environmentUS9137385Sep 17, 2013Sep 15, 2015Digifonica (International) LimitedDetermining a time to permit a communications session to be conductedUS9143608Apr 15, 2013Sep 22, 2015Digifonica (International) LimitedIntercepting voice over IP communications and other data communicationsUS9154417Nov 27, 2013Oct 6, 2015Digifonica (International) LimitedUninterrupted transmission of internet protocol transmissions during endpoint changesUS9179005Aug 13, 2013Nov 3, 2015Digifonica (International) LimitedProducing routing messages for voice over IP communicationsUS9232076Nov 30, 2007Jan 5, 2016Qualcomm IncorporatedMethods and systems of providing status message callingUS20060109867 *Oct 14, 2005May 25, 2006Novatel Wireless, Inc.Method and apparatus for routing voice traffic over a residential gatewayUS20080166999 *Nov 30, 2007Jul 10, 2008Jacob GuedaliaMethods and systems of implementing call-cost features on a mobile deviceUS20080167019 *Nov 30, 2007Jul 10, 2008Jacob GuedaliaMethods and systems of providing status message calling featuresUS20080167020 *Nov 30, 2007Jul 10, 2008Jacob GuedaliaMethods and systems of accessing contact information on a mobile deviceUS20080167039 *Nov 30, 2007Jul 10, 2008Jacob GuedaliaMethods and systems of providing local access number calling featuresUS20080181165 *Jan 9, 2008Jul 31, 2008Jacob GuedaliaMethod and system for transmitting audio data between computing devicesUS20080192910 *Feb 12, 2008Aug 14, 2008Jacob GuedaliaMethods and systems for performing authentication and authorization in a user-device environmentUS20080244023 *Mar 31, 2008Oct 2, 2008Iskoot Inc.Methods and systems for performing server-based mobile chatUS20090190738 *Jul 30, 2009Iskoot, Inc.Methods and systems for propagating information across a networkUS20110034167 *Aug 9, 2009Feb 10, 2011Ben-Shaul ItayApparatus and method for destination phone number string creationUS20110085527 *Feb 11, 2010Apr 14, 2011Research In Motion LimitedCall destination number mapping methods, devices and systemsUS20110091027 *Apr 21, 2011Microsoft CorporationDiscovering and using phone number location informationUS20110182297 *Jul 28, 2011Novatel Wireless, Inc.Method and apparatus for routing voice traffic over a residential gatewayWO2011050093A2 *Oct 20, 2010Apr 28, 2011Microsoft CorporationDiscovering and using phone number location information* Cited by examinerClassifications U.S. Classification455/445, 455/456.3, 455/415International ClassificationH04M3/436, H04M3/58, H04W48/08, H04W8/26Cooperative ClassificationH04M3/4365, H04W4/16, H04W64/006, H04M15/00, H04M3/42068, H04M3/42093, H04W48/08, H04W8/26European ClassificationH04M15/00Legal EventsDateCodeEventDescriptionApr 21, 2008ASAssignmentOwner name: ISKOOT, INC., MASSACHUSETTSFree format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:GUEDALIA, JACOB;GUEDALIA, ISAAC DAVID;REEL/FRAME:020833/0012;SIGNING DATES FROM 20080218 TO 20080319Owner name: ISKOOT, INC., MASSACHUSETTSFree format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:GUEDALIA, JACOB;GUEDALIA, ISAAC DAVID;SIGNING DATES FROM20080218 TO 20080319;REEL/FRAME:020833/0012Oct 23, 2009ASAssignmentOwner name: COMPASS HORIZON FUNDING COMPANY LLC,CONNECTICUTFree format text: SECURITY AGREEMENT;ASSIGNOR:ISKOOT, INC.;REEL/FRAME:023421/0198Effective date: 20091015Nov 1, 2010ASAssignmentOwner name: QUALCOMM ISKOOT, INC., CALIFORNIAFree format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:ISKOOT, INC.;REEL/FRAME:025225/0387Effective date: 20101011Aug 12, 2013ASAssignmentOwner name: QUALCOMM CONNECTED EXPERIENCES, INC., CALIFORNIAFree format text: CHANGE OF NAME;ASSIGNOR:QUALCOMM ISKOOT, INC.;REEL/FRAME:031003/0982Effective date: 20130607Aug 22, 2014ASAssignmentOwner name: QUALCOMM INCORPORATED, CALIFORNIAFree format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:QUALCOMM CONNECTED EXPERIENCE, INC.;REEL/FRAME:033590/0581Effective date: 20140814Sep 2, 2014ASAssignmentOwner name: QUALCOMM INCORPORATED, CALIFORNIAFree format text: CORRECTIVE ASSIGNMENT TO REMOVE THE APPLICATION NUMBER 60942559 PREVIOUSLY RECORDED AT REEL: 033590FRAME: 0581. ASSIGNOR(S) HEREBY CONFIRMS THE ASSIGNMENT;ASSIGNOR:QUALCOMM CONNECTED EXPERIENCES, INC.;REEL/FRAME:033677/0311Effective date: 20140814RotateOriginal ImageGoogle Home - Sitemap - USPTO Bulk Downloads - Privacy Policy - Terms of Service - About Google Patents - Send FeedbackData provided by IFI CLAIMS Patent Services