The subject matter regarded as the invention is particularly pointed out and distinctly claimed in the concluding portion of the specification. The invention, however, both as to organization and method of operation, together with objects, features, and advantages thereof, may best be understood by reference to the following detailed description when read with the accompanying drawings in which:
It will be appreciated that for simplicity and clarity of illustration, elements shown in the figures have not necessarily been drawn to scale. For example, the dimensions of some of the elements may be exaggerated relative to other elements for clarity. Further, where considered appropriate, reference numerals may be repeated among the figures to indicate corresponding or analogous elements.
In the following detailed description, numerous specific details are set forth in order to provide a thorough understanding of the invention. However, it will be understood by those skilled in the art that the present invention may be practiced without these specific details. In other instances, well-known methods, procedures, and components have not been described in detail so as not to obscure the present invention.
Unless specifically stated otherwise, as apparent from the following discussions, it is appreciated that, throughout the specification, discussions utilizing terms such as “processing,” “computing,” “calculating,” “determining,” or the like, refer to the action and/or processes of a computer, computing system, or similar electronic computing device that manipulates and/or transforms data represented as physical, such as electronic, quantities within the computing system's registers and/or memories into other data similarly represented as physical quantities within the computing system's memories, registers or other such information storage, transmission or display devices.
The present invention may provide web-based dialing for mobile communications devices. Thus, a user may view a web page from his mobile device, click on a desired telephone number and the mobile device may dial the selected telephone number.
This may enable the user to maintain a web-based contact list which may be edited and organized in any desired format, such as HTML, etc. It may enable organizations to maintain contact list(s) for their employees, associates, etc. Since the contact list(s) may exist only on the web, losing a mobile communications device may no longer mean leaking the contact list to others, nor may it require reentering the numbers into a new mobile device. Furthermore, web servers may refuse to respond to lost telephones, thereby further increasing security.
It will be appreciated that the present invention may provide mobile access to telephone numbers. Wherever a user may be, he may connect to the web and find a desired telephone number, which his mobile device may then dial. For example, while on the train, a user may search the web for a restaurant. When he reaches the relevant web page, he may click on the telephone number and his mobile device may connect him to the restaurant.
It will be appreciated that the present invention is applicable to all mobile communications devices that can connect to the web. Such devices include, in addition to high end cellular telephones: Blackberries, commercially available from Research in Motion of Canada; and computer phones on mobile devices, such as iPAQs, commercially available from Hewlett-Packard of the US, and other hand-held devices.
Reference is now made to
The user may use web browser 12 to access a web page 20 at, for example, “website.com”. Web page 20 may include a list 22 of names, each linked (as noted by the underlining) to a separate file. When the user clicks (within browser 12) on one of the names, for example, on “Joe”, a file 24, which may include a telephone number associated with the clicked name, may be downloaded to telephone 10. DPND 16 may parse the downloaded telephone number and may activate dialer 14 to dial at least one of the numbers listed in file 24.
Reference is now made to
MIME type table 31 may form a part of operating system 30 and may list MIME (multi-purpose internet mail extensions) types known by operating system 30, where a MIME type may describe both the type of the file (text, XML, .pdf, etc.) and the type of application which may open it. In accordance with a preferred embodiment of the present invention, the present invention may define a new MIME type and associated file extension, for example “.fcp”, and may register DPND 16 as the handler for it.
DPND 16 may have associated with it an AEF (access control enforcement function) file 33 which may define the MIME type to be associated with parser 32, in this case, the new MIME type. Upon installation of DPND 16 into mobile device 10, operating system 30 may read AEF file 33 and may associate DPND 16 with its MIME type (for example, *.fcp) in MIME type table 31.
When browser 12 may request file 24, the server of web page 20 may provide file 24, together with an indication of its MIME type. In response, browser 12 may call operating system 30 to open the appropriate application for file 24. System 30 may access table 31 to check the application associated with the MIME type of file 24 and, using the output of table 31, may open DPND 16 on top of browser 12. Parser 32 may then parse file 24 to determine the phone number to be dialed. Parser 32 may then invoke wrapper 34 to dial the received phone number, typically by invoking a dialing API (application programming interface) of mobile device 10, which, in turn, may activate dialing mechanism 14.
It will be appreciated that file 24 may contain the phone number to be dialed and/or logic describing how to reach the person with whom the file is associated.
File 24A may contain just the phone number, for example 212-xxx-yyyy. Alternatively, it might contain some code for which parser 32 might search, such as “//:PHONENUMBER://”, followed by the phone number.
File 24B might contain some logic describing which phone number to utilize. For example, there might be one phone number for late in the evening (after 8 pm) and a different phone number for the afternoon (after 2 pm). It will be appreciated that any type of logic may be written. The choice might be among times, or as a function of the calling phone number (i.e. a different number to call depending on who calls), or as a function of the region of the calling number (i.e. a different number for different parts of the country), or of the presence status (online, busy, away, etc.) of the called party, etc.
In an alternative embodiment, shown in
For this embodiment, web page 20′ may include a telephony URL linked (as noted by the underlining) to each person listed on the page. The telephony URL may read:
href=“tel:+1 212 xxx yyyy”
When the user clicks (within browser 12′) on one of the names, for example, on “Joe”, web page 20′ may provide the telephony URL “tel:212-xxx-yyyy” to browser 12′. Browser 12′ may then provide the telephone number “212-xxx-yyyy” to dialing mechanism 14.
It will be appreciated that the web-based contact list may be generated in any suitable way. For commercial websites, there may only be a few listed phone numbers, placed when designing the website. For company intranets or Wikis, the contact list may be generated by the employees, as each employee adds or edits the phone numbers he utilizes. Alternatively, it may be the province of a particular employee or department.
The contact list may be organized and/or reorganized in any desired manner. As described hereinabove, there may be a separate file 24 for each contact in the contact list or a separate telephony URL for each contact.
It will be appreciated that editing the contact list may be fairly simple since it is a web-based list.
It will also be appreciated that other content may be listed on web page 20. For example, other contact information (such as address, name, title, etc.) may be listed.
Reference is now made to
The system shown in
When browser 12′ of device 10 accesses contact management system 32, it does so by first contacting its web server 30 which, in turn, connects to contact management system 32. Web server 30 collects (arrow 34) contact information from contact management system 32 and then activates a number format processor 36 to convert any telephone numbers forming part of the contact information to one of the formats described hereinabove. Web server 30 then generates web page 20′ from the contact information from system 32 and the telephone formats of number format processor 36.
Number format processor 36 may scan the contact information, looking for telephone numbers in any known format. Number format processor 36 may have stored therein the multiplicity of formats for telephone numbers known throughout the world and may utilize such to find telephone numbers on webpage 34. When processor 36 may find a telephone number, it may either generate telephony URLs, as described hereinabove or it may link a file 24 to it, also as described hereinabove.
In the alternative embodiment shown in
For one format change, number format processor 36 may include cheap dialing means which may receive the special codes that various telephone services require for inexpensive service. For example, Orange Israel offers a callback service which requires the user to dial the telephone number in the form it would be dialed domestically in Israel, but prefixed with “*00*” and followed by “#”. For example, the number +972 2 123-4567″ would be dialed as “*00*021234567#”. This triggers a callback service and greatly reduced calling rates.
Number format processor 36 may add the prefix and suffix codes to the telephone numbers found in web page 34 before generating telephony URLs, as described hereinabove or adding the link to file 24 to it, also as described hereinabove.
Reference is now made to
Prior patent applications U.S. 60/771,883 and 60/772,564, now incorporated into U.S. patent application Ser. No. 11/544,938, assigned to the common assignee of the present application and incorporated herein by reference, disclose a community server, an Internet-based server that allows users to choose media clips to be distributed to their buddies. These patent applications discuss a variety of opportunities to display a user's media clip to his buddy. For example, when the user and his buddy have or attempt to have a phone conversation. In addition, at the end of a call between two mobile devices, each might see video clip: one chosen by the user of that device, or one chosen by the user of the other device, or one chosen by the community server.
In accordance with an alternative preferred embodiment of the present invention, each member of the community may be issued a private web page 40, protected either by username/password, by a randomly-generated long URL, or by any other suitable means, as is clear to one skilled in the art. Page 40 may present a view of each of the user's buddies; offering the option to call each buddy (using the techniques described hereinabove), to play his latest media clip, or to view other information about him. These pages may also offer inexpensive dialing and the other options discussed in the previous embodiments.
While certain features of the invention have been illustrated and described herein, many modifications, substitutions, changes, and equivalents will now occur to those of ordinary skill in the art. It is, therefore, to be understood that the appended claims are intended to cover all such modifications and changes as fall within the true spirit of the invention.
This application claims benefit from U.S. Provisional Patent Application 60/819,394, filed Jul. 10, 2006, which is hereby incorporated in its entirety by reference.
| Number | Date | Country | |
|---|---|---|---|
| 60819394 | Jul 2006 | US |