Telephone call handling system
A telephone call handling system includes a sendings receiver configured to receive sendings sent from the telephones of other party's via a telephone service. A sendings registry automatically inventories each received sending and forwards the inventoried sending to a storage where the sending is stored. Subsequently, a delivery trigger is triggered. The triggered trigger initiates a sendings provider to provide one or more of the inventoried and stored sendings to a deliverer. The deliverer then delivers the provided sending or sendings to one or more of: a speaker, a display, a text message display, an image display, a video display, an email delivery, an web-site poster, a service provider delivery, a delivery port, a ring-back delivery, a ring-back forward delivery and a ring-tone.
This is a continuation in part of co-pending U.S. patent application Ser. No. 13/136,520 filed Aug. 3, 2011 which is hereby incorporated by reference herein in it's entirety. U.S. patent application Ser. No. 13/136,520 filed Aug. 3, 2011 is a continuation in part of co-pending U.S. patent application Ser. No. 12/802,685 filed Jun. 12, 2010, Publication No. US-2011-0190012-A1, Publication Date: Aug. 4, 2011, which is hereby incorporated by reference herein in it's entirety. U.S. patent application Ser. No. 12/802,685 filed Jun. 12, 2010 is a continuation in part of co-pending U.S. patent application Ser. No. 12/658,475 filed Feb. 4, 2010, Publication No. US-2011-0188645-A1, Publication Date: Aug. 4, 2011 which is hereby incorporated by reference herein in it's entirety.
BACKGROUNDA call screening service commonly known as “Caller I.D.” is widely utilized by present-day telephone users. Caller I.D. is a service provided to users by the telephone service providers via telephones typically fitted with a display. For calls from landline phones, the caller I.D. information typically displayed includes the telephone number of the landline phone a caller is calling from and the subscriber name documented to that number. For calls from mobile phones, the information typically displayed includes the telephone number of the mobile phone a caller is calling from and whatever name the mobile phone owner happens to program into his phone (or not).
Present-day, telephone users having caller I.D. typically first respond to an incoming telephone call by looking at the display. They then consider that information along with their encumbrances of that moment and mood at that moment, and decide whether to answer the call or not. If not, typically after a set number of additional rings, the incoming call is automatically transferred to a voice mail service (or answering machine for many landline phones) where the caller may leave a message to be reviewed by the user at some later time.
SUMMARY OF THE INVENTIONThe present disclosure provides for a telephone call handling system, certain embodiments of which achieve improved utilization of caller I.D. information (improved beyond a user receiving caller I.D. information and therefrom simply deciding whether to answer the phone or not). In a first example description of one embodiment, at the onset of an incoming call, caller I.D. information is provided to the user (i.e. the party being called). From the information, the user is able to essentially determine the identity of the caller and, thus, able to surmise based on the determined identity that the subject matter to be discussed may be of a nature where recording the conversation would be advantageous.
As an example of operation of this first example, the user's telephone is rung by an incoming ring signal. Delivered with the ring signal is caller I.D. information. The information is provided on a display. The user recognizes the phone number (or caller identification) on the display; i.e. the user essentially knows who's calling. The user determines that this person is someone whose conversations should be recorded (perhaps a client calling to give instructions to a professional). Accordingly, the user presses a control button. An interface responds to the pressed button by going off-hook and an out-going message sender responds to the pressed button by sending a message to the caller such as “This conversation may be recorded”. The caller hears the message and understands that any subsequent telephonic conversation with the user may be recorded.
As can be seen for this first example description of one embodiment, caller I.D. information is initially utilized to enable the user to decide whether to answer the incoming call or not. If the user decides to answer, based on the caller I.D. information the user can then decide whether or not to record the ensuing telephone conversation (or, in the alternative, based on a lack of caller I.D. information).
In a second example description of one embodiment, at the onset of an incoming call, caller I.D. information is provided to the user (i.e. the party being called). From the information, the user is able to essentially determine the identity of the caller and, thus, based on the determined identity is able to decide whether or not to pick content for delivery to the user and/or delivery to the caller. If the user decides to pick content, based on the determined identity the user is able to decide what content to pick from a plurality of content choices.
As an example of operation of this second example, at some date (or dates) prior to a telephone call between an-other party and the user, the other party sends content from his phone to the user's phone such as audio clips, text messages, images and videos. Such sendings can be received, inventoried and stored. Subsequently, the other party calls the user. Prior to answering, the user views caller I.D. information provided on a display. A plurality of icons are provided on a touch-screen. Each icon represents a received sending received prior from, and inventoried to, the calling telephone. Each icon can include the date that sending was received and the sending type, i.e. audio type, text message type, image type, video type. For this example, based on the provided caller I.D information the user decides to touch a text message type icon. In response to the touched icon, the inventoried text message sending represented by the icon is obtained from storage and dispatched to two deliverers. One of the deliverers displays the text message for the user to view. The other deliverer delivers the text message to the caller via the telephone service provider. Consequently, the text message received from the calling telephone at some date prior to the incoming call is now displayed at the user's phone for the user to view and displayed at the caller's phone for the caller to view.
As can be seen for this second example description of one embodiment, caller I.D. information is initially utilized to enable the user to decide whether or not to answer the incoming call. If the user decides to answer, based on the caller I.D. information, the user can then decide whether or nor to pick content for delivery to the user and/or to a caller (or, in the alternative, based on a lack of caller I.D. information). If the user decides not to answer, based on the caller I.D. information, the user can then decide whether or not to pick content for delivery to the user and/or to a caller (or, in the alternative, based on a lack of caller I.D. information).
The present disclosure provides for a telephone call handling system, certain embodiments of which can receive, inventory, and store sendings, said sendings subsequently delivered to the system user and/or to a caller and/or via email and/or to the internet and/or via an external port and/or as a ring-back to a caller. In an example description of one embodiment, at some date (or dates) prior to a telephone call between and other party and the user, the user has made a request to the other party. Could you send me some content? Any content would be good. Maybe a song clip or a picture of yourself or a video clip you like of perhaps your favorite poem or a good joke. I want to put you in my universe”. In response to the request, the other party sends content from his phone to the user's phone. Each of these “sendings” is received, inventoried and stored. Subsequently, a call occurs between user and other party. Upon the user dialing the other party's telephone number, the dialed telephone number is registered or upon receipt of the incoming call from the other party the calling telephone's number obtained from caller I.D. information is registered. An icon array with each icon representative of a sending inventoried to the registered telephone number (other party's number) is displayed on a touch-screen. For this example, the call is answered (either by other party or by user). While conversing, the user decides to touch one of the displayed icons, as an example, an icon comprising the date Nov. 20, 2011 and a miniature of a picture (the miniature being a reduction of the actual image stored). In response to the touched icon, the image sending represented by the icon and, thus, inventoried to the other party's telephone number, is provided, for this example, to two deliverers. The first deliverer displays the image to the user. The second deliverer delivers the image to the other party's telephone via the telephone service provider.
A form of the invention is illustrated in the accompanying drawings in which:
FIG 1c is a block diagrammatic view depicting the examples of
Examples provided herein describe certain functionality, structure and components for the purpose of facilitating understanding of how the various disclosed embodiments can operate. However, it will be understood that the functionality, structure and components described in the examples is exemplary only, and should not be considered as limiting the scope of the embodiment to which the example applies.
The present invention pertains to telephone calls. Accordingly, a general description of telephone service is appropriate. For decades, telephone service in the U.S. was provided by an entity commonly known as “the phone company”, “Ma Bell” and “AT&T”. Deregulation broke up the giant telephone service provider into a network of service providers then commonly referred to as “the baby bells”. For this discussion, the present-day network of service providers including the circuitry they employ is referred to as a telephone service provider 121.
One example of circuitry that can be employed in the routing of a telephone call by service provider 121, a local switching station 120, is depicted in
In another example of operation of the example circuitry, the user places a call from the user's telephone 27. That call is received at local switching station 120 (received via the air-waves if telephone 27 comprises mobile phone 165, received via telephone line 11 if telephone 27 comprises a landline telephone). Station 120 then sends the call over a long distance network to a local switching station. The local switching station provides the call to the called telephone. If the call is answered, the local switching station communicably connects the user's telephone 27 with the called telephone. (If the call is a local call, station 120 would then received the call from the user's telephone 27 and then provide a signal that rings the called telephone.)
Examples of the present invention, referred to herein as telephone call handling system 10, are illustrated in the accompanying
Telephone 27 can comprise a mobile phone 165. Beyond providing the functionality of telephone 27, mobile phone 165 can function to facilitate the selection of content for play as a music player and/or for a ring-back and/or for a user-selected sending. Mobile phone 165 can further function to facilitate delivery of the ring-back to a caller. An exemplary mobile phone 165 is depicted in
Example handling system 10bb comprises a caller I.D. circuitry 20. Caller I.D. circuitry 20 functions to provide caller I.D. information to a user. An exemplary caller I.D. is depicted in
Example handling systems 10ee through 10nn comprise a graphical user interface 210. Graphical user interface 210 can function to receive instruction from a user and can function to display information to a user. An exemplary graphical user interface 210 is depicted in
It will be appreciated that the apparatus of the present disclosures has been described by examples (
A first embodiment of telephone call handling system 10 is illustrated in
Message-then-record circuitry 310 functions to deliver a message to a caller and then record a conversation. An exemplary message-then-record circuitry 310 is depicted in
Interface 31 functions to control connection and release operations. An exemplary interface 31 is depicted in
Out-going message sender 32 functions to send stored information to a caller. An exemplary message sender 32 is depicted in
Recorder 323 functions to record a conversation. An exemplary recorder 323 is depicted in
Commencer 325 functions to receive instruction from a user to commence message-then-record circuitry 310. An exemplary commencer 325 is depicted in
A first example of this first embodiment is illustrated as system 10aa in
Further for this example, UI 99 of commencer 325 is configured to receive instruction from a user via a control button 330, button 330 electrically connected to (or connectable to) line 11a and located at telephone 27aa. When pressed, button 330 sends a control signal to UI 99. UI 99 responds by sending a signal to interface 31 and, after a two-second delay, sending a signal to sender 32. Interface 31 responds by going off-hook. Sender 32 responds by sending record message A 321 to the caller. (Button 330 can be part of commencer 325.)
A first example of operation of this first example of this first embodiment will now be given (
When the user answers, the off-hook condition of telephone 27aa is detected by interface 31. Interface 31 responds by discontinuing the off-hook condition. (If the caller hangs up prior to the user answering, interface 31 can respond by discontinuing the off-hook condition.) Circuitry 310 responds to discontinuance of the off-hook condition (and provided the caller has not terminated the call) by engaging recorder 323. (Circuitry 310 is configured to determine the following conditions in order to engage recorder 323: (i) that button 330 has been pressed to send the “record” message; (ii) that the off-hook condition has been terminated; (iii) that the call has not been terminated; and (iv) that the user has not subsequently signaled the circuitry to terminate the recording. Circuitry 310 can alternately be configured to maintain the recorder 323 in the engaged condition following termination of the call by the caller so that the user can record verbal information relating to the call, such as the date, time and identity of the caller, and any other notes the user wishes to record. The recorder can then be disengaged by the user by signaling circuitry 310 (e.g., via button 330) to disengage the recorder. Also, in one version, message-then-record circuitry 310 is configured such that the recorder 323 also records the playing of the record-message.) Recorder 323 remains engaged until circuitry 310 determines that (i) the incoming call has been terminated (i.e., no incoming call signal detected), (ii) the user disengages the recorder 323 during the conversation (e.g., by pressing button 330 again), or the user disengages the recorder after the caller has terminated the call. Thus, button 330 can act as a multi-function button, serving to: (i) send the “record” message R.M. A 321 (if circuitry 310 determines that there is an unanswered incoming call); (ii) act as an “on-off” toggle for the recorder 323 during a conversation (if circuitry 310 determines that there is an ongoing connected call); and (iii) to enable playback of the last-recorded conversation (if circuitry 310 determines that there is currently no incoming or ongoing call). Phone 27aa can also use common message playback features (e.g., “play”, “repeat”, “delete”) 327 to manage conversations recorded by the recorder 323.
“Record” message R.M. A (321) can either be provided as a standard default message supplied by a service provider or a telephone manufacturer, or as a user customized message. In the latter instance the user can customize the “record” message R.M. A (321) by pressing button 330 (when no call is incoming or in progress), and then speaking the desired customized “record” message into the microphone (a standard feature for any telephone, and thus not depicted in
A second example of operation of this first example of this first embodiment will now be given (
A third example of operation of this first example of this first embodiment will now be given (
A second example of the first embodiment is illustrated as telephone call handling system 10bb in
An example of operation of this second example of this first embodiment will now be given (
As with phone 27aa of
A third example of the first embodiment is illustrated as telephone call handling system 10cc in
An example of operation of this third example of this first embodiment will now be given (
As with phone 27aa of
“Record” messages (321) can either be provided as standard default messages supplied by a service provider or a telephone manufacturer, or as a user customized messages. In the latter instance the user can customize the “record” messages (321) by pressing one of buttons 330a, 330b or 330c (when no call is incoming or in progress), and then speaking the desired customized “record” message into the microphone (a standard feature for any telephone, and thus not depicted in
In one variation, in order to assist the user in selecting the appropriate “record” message to be sent to a caller, once the user presses any one of buttons 330a, 330b or 330c during an incoming call, the corresponding “record” message can be announced to the user via the telephone speaker (a feature common to all telephones). If the message is the one desired, the user can then press the button a second time in order to cause the selected “record” message to be sent to the caller. However, if the initially selected “record” message is not the message the user desires to send to the caller, then the user can press a different button (330a, 330b or 330c) and repeat the process. As an alternative, rather than announcing the entire “record” message to the user, the user can store “shorthand” descriptions for each “record” message. (These “shorthand” descriptions can be stored in a memory device located in circuitry 310, in phone 27cc, or at a service provider.) For example: for a generic “record message R.M. A (321a) of “This message may be recorded”, the shorthand verbal clue can be “generic”; for a customized “record message R.M. B (321b) of “This message may be recorded to protect our legal rights”, the shorthand verbal clue can be “legal”; and for a customized “record message R.M. C (321c) of “This message may be recorded in order to ensure the quality of your order “, the shorthand verbal clue can be “customer”.
In yet another variation, the user can store text equivalents (or shorthand text notes) for each “record” message in a memory device located in circuitry 310, in phone 27cc, or at a service provider. Then, once any one of buttons 330a, 330b or 330c is pressed during an incoming call, the corresponding text description for the associated “record” message can be displayed on display 21. If the displayed text indicates that the desired message has been selected, the user can press the button again (or, if display 21 is a touch screen, by merely tapping the screen).
A fourth example of the first embodiment is illustrated as telephone call handling system 10dd in
An example of operation of this fourth example of this first embodiment will now be given (
Another example of operation of this fourth example of this first embodiment will now be given (
The apparatus of this fourth example can be configured to allow the user to terminate recording of the conversation at any time via the user interface 31, as well as to pause recording and restart recording during a conversation. The apparatus can also be configured to provide the user with a choice of record messages and enable the user the user to pick one of the messages (the apparatus can employ picker 329, picker 329 shown in
Message management feature 327 (described prior) can be enabled to display a recorded conversation manager menu option to the user. Exemplary high-level options in the recorded conversation manager can include: (i) a sort option to sort recorded conversations; (ii) a find option to find recorded conversations (based on selected criteria, as discussed more fully below); and a (iii) an organize option to allow a user to organize recorded conversations (also as discussed more fully below). As indicated above, the recorder 323 can be configured to allow time-stamp information to be provided with each recorded conversation. Accordingly, a default method for organizing recorded conversations is by date and time, with the most recent recorded conversation being the first recorded conversation shown in a list of all recorded conversations. Accordingly, using the sort option, a user can sort by date (earliest first, or oldest first), as well as by caller ID. Further, the indicated organize option can allow a user to create folders for recorded conversations, assign tags or names to recorded conversations, move recorded conversations between folders, delete and edit recorded conversations, send copies of recorded conversations by e-mail, convert audio (voice) files of recorded conversations to text using voice recognition software. The indicated find option can be used to find recorded conversations based on date, time, other party identity information (for example telephone number), user assigned name (e.g., file name or tag), specific words (e.g., using word-matching voice software or voice-to-text conversion software). A conversation or group of conversations can be found based on date, other party telephone number, user assigned name or other and the specific words option can be employed to the found conversation or group. As another example, the specific words option can be employed to an entire inventory of conversations. (Other party telephone number can be obtained during an incoming call from caller I.D. information and during an outgoing call from obtaining the dialed number.)
(In one variation, the fourth example of this first embodiment can operate without message sender 32 sending a record message to the other party. Upon detector 311 sending a signal to UI 99, UI 99 responds by sending a signal to recorder 323. Recorder 323 commences to record the conversation.)
This first embodiment can be enhanced with a message selector 68. Message selector 68 functions to enable a user to select an audio message. An exemplary message selector 68 is shown in
A second embodiment of telephone call handling system 10 is illustrated in
The term “sending” (as used as a noun in this second embodiment) includes content configured to be sent electronically from one party to another. For example, content can be sent by an-other party to a user of system 10. The content of a sending can be included in an electronic file. A sending can also comprise an electronic file and wherein the file contains the content. A sending can include one or more of: audio content; text message content; image content; video content and combinations thereof. As one example, a sending can be a picture/image received from a person with whom the user communicates over the telephone. As another example, a sending can be a favorite audio clip received from a person with whom the user communicates over the telephone.
This second embodiment includes a sendings receiver 340. Sendings receiver 340 functions to receive sendings. An exemplary sendings receiver 340 is depicted in
Sendings receiver 340 can include one or more of: a telephone provider receiver 344, an email receiver 351 and an internet receiver 409. Telephone provider receiver 344 functions to receive sendings delivered via telephone service. An exemplary telephone provider receiver 344 is depicted in
Typically delivered along with a sending is sending origin identity information, for example the telephone number of the dispatching telephone. Along with the sending, telephone provider receiver 344 can receive said identity information, for example said telephone number. Receiver 344 can then forward the received sending and identity information (telephone number) to one of sendings registry 350 or sendings identifier 345. If forwarded to registry 350, registry 350 can then register the sending to the (identity information) telephone number and include the registered sending in an inventory. If forwarded to identifier 345, identifier 345 can then determine whether or not the sending constitutes a distinguished sending. If so, identifier 345 can forward the sending and identity information to registry 350. Registry 350 can then register the sending to the identity information (telephone number) and include the registered sending in an inventory.
Typically delivered along with a sending is sending type information, for example, the type of content contained in the sending. Content types include (without limitation): audio, text message, image, video and audio/video. Along with the sending and identity information, telephone provider receiver 344 can receive said type information. Along with the sending and identity information, receiver 344 can forward the received type information to one of sendings registry 350 or sendings identifier 345. If forwarded to registry 350, registry 350 can then register the sending to the type information (along with registering to the identity information) and can include the registered sending in inventory 324. If forwarded to identifier 345, if the sending is identified, identifier 345 can forward the type information along with the sending and identity information to registry 350 to be inventied.
Sendings receiver 340 can include an email receiver 351. Email receiver 351 functions to receive sendings delivered via an email service. An exemplary email receiver 351 is depicted in
Typically delivered along with an email sending is sending origin identity information, for example the email account address from where the email was dispatched. Along with the delivered sending, email receiver 351 can receive said identity information, for example said email account address. Receiver 351 can then forward the received sending and identity information to one of sendings registry 350 or sendings identifier 345. If forwarded to registry 350, registry 350 can then register the sending to the identity information and can include the registered sending in an inventory, for example inventory 324. If forwarded to identifier 345, identifier 345 can then identify the sending or not. If the sending can be identified, identifier 345 can forward the sending and identity information to registry 350. Registry 350 can then register the sending to the identity information and include the registered sending inventory 324. Email receiver 351 can employ matcher 353 described below to transfer/convert identity information received via email service to identity information employed in telephone service.
Typically delivered along with an email sending is sending type information, for example, said sending type information comprising the type of content contained in the sending. Content types can include: audio, text message, image, video and combined audio and video. Along with the delivered sending and identity information, email receiver 351 can receive said sending type information. Along with the sending and identity information receiver 351 can forward the received type information to one of sendings registry 350 or sendings identifier 345. If forwarded to registry 350, registry 350 can then register the sending to the type information (along with registering to the identity information) and can include the registered sending in inventory 324. If forwarded to identifier 345, if the sending is identified, identifier 345 can forward the type information with the sending and identity information to registry 350. Registry 350 can the inventory the information. Email receiver 351 can be configured to transfer/convert type information received via email service to type information employed in telephone service.
Sendings receiver 340 can include an internet receiver 409. Internet receiver 409 functions to receive sendings delivered via an internet service. An exemplary internet receiver 409 is depicted in
Typically delivered along with a sending file is sending type information, for example, said sending type information comprising the type of content contained in the file. Content types can include: audio, text message, image, video and combined audio and video. Along with the delivered sending and identity information, internet receiver 409 can receive said sending type information. Along with the sending and identity information receiver 409 can forward the received type information to one of sendings registry 350 or sendings identifier 345. If forwarded to registry 350, registry 350 can then register the sending to the type information (along with registering to the identity information) and can include the registered sending in an inventory. Internet receiver 409 can be configured to transfer/convert type information received via internet service to type information employed in telephone service or other.
Sendings receiver 340 can include a matcher 353. Matcher 353 functions to match sending identity information. An exemplary matcher 353 is depicted in
This second embodiment includes a sendings registry 350. Sendings registry 350 functions to inventory sendings. An exemplary sendings registry 350 is depicted in
(Presently practiced, a sending party addresses a sending to the user's telephone number and sends the sending. The sending is sent from the sending party's telephone (cell phone) and is delivered by a service provider. The service provider delivers the sending to the user's telephone (cell phone). The user's telephone stores the sending and provides a sending description in an inbox, the sending description representative of the sending. The user can then visit the inbox, view a list of sending descriptions and click on a description serving to open the associated sending file. Typically included with the delivered sending is sending origin identity information. The user's telephone provides the identity information in the sending description. As examples, the identity information can comprise the telephone number of a telephone from where the sending originated and/or can comprise a name registered to said telephone number and/or can comprise other sending identifying information. The identity information provided in the sending description enables the user to ascertain the sending's origin. In addition to the identity information, typically included with the delivered sending is sending type information. The user's telephone provides said sending type information in the sending description. Sending type can be: audio type, text message type, image type, video type, or some other type. Also presently practiced, a sending can be sent from an email account to an email account accessible to the user. Said sending description information is then typically provided at the inbox of said email account, said inbox accessible by the user.)
Registry 350 can include an automatic register 401. Automatic register 401 functions to automatically register sendings. An exemplary automatic register 401 is depicted in
The registering of origin identity, time of receipt, sending type, and sending class by automatic register 401 will now be described:
Automatic register 401 can include an origin register 358. Origin register 358 functions to register a sending by origin. An exemplary origin register 358 is depicted in
Origin register 358 can include a telephone number register 359 shown as TNR 359. Telephone number register 359 functions to register a sending by telephone number. As one example of telephone number register 359, register 359 can include circuitry and/or programming to obtain the telephone number of the telephone from where a sending originated. Register 359 can obtain said telephone number from identity information included along with the received sending (for example, presently provided in the above-described sending description). Register 359 can then register the obtained telephone number. Registry 350 can compile a registration number for the sending inclusive of the register 359 obtained telephone number as a component. Registry 350 can add the registration number to an inventory, for example inventory 324, and can forward the inventoried sending to be stored in storage 370.
As an example, the telephone number included along with a sending forwarded to registry 350 can be 5095346666. Telephone number register 359 can register the telephone number. Registry 350 can compile a registration number for the sending inclusive of the registered telephone number 5095346666 as a component. Registry 350 can list the registration number in inventory 324 and can forward the inventoried sending to be stored in storage 370. The stored sending can be found by searching inventory 324 identifiable by the 5095346666 component of the registration number. Subsequently, a sendings request to registry 350 can be made by, for example, sendings provider 375 (provider 375 described later, or by some other component). The request can be, for example, to provide all sendings registered to the telephone number 5095346666. Registry 350 can respond to said request by searching inventory 324 for registration numbers having the telephone number 5095346666 as a component. For each registration number found, registry 350 can then provide the sending from storage 370 to the requester. (The exemplary origin register 358 can register alternative obtained origin identity information. Said alternative obtained identity information can be, for example, a last name, a first name and/or some other identity information. For example, the above example sending registered by 5095346666 can instead be registered by a last name provided in said obtained identity information. If the identity information included a last name of Williams (for example), then the sending can be registered as, for example, WILLIAMS.)
Automatic register 401 can include a time register 371. Time register 371 functions to register a sending by time. An exemplary time register 371 is depicted in
Subsequently, a sendings request to registry 350 can be made by, for example, a prioritizer 341 of sendings provider 375 (prioritizer 341 described below, or can be made by some other component). Prioritizer 341 can request registry 350 provide the registration numbers for all sendings iregistered to the telephone number 5095346666. Registry 350 can respond to said request by searching inventory 324 for all registration numbers having a 5095346666 component and by providing all found registration numbers having the 5095346666 component to prioritizer 341. (Said registration numbers provided would include the above example 5095346666-10/03/2011.) Prioritizer 341 can then, for example, determine from the date-received information included in the registration numbers the last sending registered and can then request from registry 350 said last sending registered by providing the registration number to registry 350. Registry 350 can then provide the sending from storage 370, for example to dispatcher 336. (As another example of time register 371, registry 350 can list sendings in inventory 324 in the order received. In other words, the first inventoried sending would then constitute the first on the list and the last inventoried sending would then constitute the last on the list. Registry 350 inventorying sendings in the order received acts as time register 371 by in effect registering sendings by time.)
Sendings registry 350 can include a sendings type register 372. Sendings type register 372 functions to register a sending by type. An exemplary sendings type register 372 is depicted in
Sendings type register 372 can include an audio type register 388 shown as ATR 388. Audio type register 388 functions to register at least one sending by audio type (e.g. an audio type sending can comprise music, voice, sound effects, sounds of nature etc.) As one example of audio type register 388, register 388 can obtain sending type information included along with a received sending. For this example, type register 388 can recognize from sending type information that the sending constitutes an audio sending. Register 388 can then register audio type to the sending. Register 350 can compile a registration number inclusive of the registered audio type as a component by including AU in the registration number. Registry 350 can add the registration number to inventory 324 and forward the inventoried sending to be stored in storage 370. For example, the sending can be the above example sending assigned the registration number 5095346666-10/03/2011. Registry 350 can include AU in the registration number. The registration number can then be, as an example for this example, 5095346666-10/03/2011-AU. Registry 350 can add the registration number to inventory 324 and forward the inventoried sending to be stored in storage 370. Registry 350 can find the sending in inventory 324 identifiable by the entire registration number, identifiable by the 5346666 component, identifiable by the 10/03/2011 component and identifiable by the AU component. Subsequently, a sendings request to registry 350 can be made by, for example, sendings provider 375 or by some other hardware to provide, for example, all audio sendings inventoried. Registry 350 can respond to said request by searching inventory 324 for registration numbers inclusive of AU. For each registration number found, registry 350 can then provide from storage 370 to the requester the audio sending having the assigned registration number.
Sendings type register 372 can include a text message type register 382 shown as TMTR 382. Text message type register 382 functions to register at least one sending by text message type (e.g. a text message type sending can comprise a poem, a joke, a saying, a motto, a theme, a title etc.). As one example of text message type register 382, register 382 can obtain sending type information included along with a received sending. For this example, type register 382 can recognize from sending type information that the sending constitutes a text message sending. Register 382 can then register text message type to the sending. Register 350 can compile a registration number inclusive of the registered text message type as a component by including TM in the registration number. Registry 350 can add the registration number to inventory 324 and forward the inventoried sending to be stored in storage 370. For example, the sending can be the above example sending assigned the registration number 5095346666-10/03/2011. Registry 350 can include TM in the registration number. The registration number can then be, as an example for this example, 5095346666-10/03/2011-TM. Registry 350 can add the registration number to inventory 324 and forward the inventoried sending to be stored in storage 370. Registry 350 can find the sending in inventory 324 identifiable by the entire registration number, identifiable by the 5346666 component, identifiable by the 10/03/2011 component and identifiable by the TM component. Subsequently, a sendings request to registry 350 can be made by, for example, sendings provider 375 or by some other hardware to provide, for example, all text message sendings inventoried. Registry 350 can respond to said request by searching inventory 324 for registration numbers inclusive of TM. For each registration number found, registry 350 can then provide from storage 370 to the requester the text message sending having the assigned registration number.
Sendings type register 372 can include an image type register 383 shown as ITR 383. Image type register 383 functions to register at least one sending by image type (e.g. an image type sending can comprise a picture of an-other party who the user converses with via provider 121, a favorite picture of an-other party, an-other party's worst nightmare, a design, a map etc.). As one example of image type register 383, register 383 can obtain sending type information included along with a received sending. For this example, type register 383 can recognize from sending type information that the sending constitutes an image sending. Register 383 can then register image type to the sending. Register 350 can compile a registration number inclusive of the registered image type as a component by including IM in the registration number. Registry 350 can add the registration number to inventory 324 and forward the inventoried sending to be stored in storage 370. For example, the sending can be the above example sending assigned the registration number 5095346666-10/03/2011. Registry 350 can include IM in the registration number. The registration number can then be, as an example for this example, 5095346666-10/03/2011-IM. Registry 350 can add the registration number to inventory 324 and forward the inventoried sending to be stored in storage 370. Registry 350 can find the sending in inventory 324 identifiable by the entire registration number, identifiable by the 5346666 component, identifiable by the 10/03/2011 component and identifiable by the IM component. Subsequently, a sendings request to registry 350 can be made by, for example, sendings provider 375 or by some other hardware to provide, for example, all image sendings inventoried. Registry 350 can respond to said request by searching inventory 324 for registration numbers inclusive of IM. For each registration number found, registry 350 can then provide from storage 370 to the requester the image sending having the assigned registration number.
Sendings type register 372 can include a video type register 384 shown as VTR 384. Video type register 384 functions to register at least one sending by video type (e.g. a video type sending can comprise a video starring an-other party whom the user converses with, a favorite video of an-other party, a movie clip, a internet posted video clip, a commercial, an infomercial etc.). As one example of video type register 384, register 384 can obtain sending type information included along with a received sending. For this example, type register 384 can recognize from sending type information that the sending constitutes a video sending. Register 384 can then register video type to the sending. Register 350 can compile a registration number inclusive of the registered video type as a component by including VD in the registration number. Registry 350 can add the registration number to inventory 324 and forward the inventoried sending to be stored in storage 370. For example, the sending can be the above example sending assigned the registration number 5095346666-10/03/2011. Registry 350 can include VD in the registration number. The registration number can then be, as an example for this example, 5095346666-10/03/2011-VD. Registry 350 can add the registration number to inventory 324 and forward the inventoried sending to be stored in storage 370. Registry 350 can find the sending in inventory 324 identifiable by the entire registration number, identifiable by the 5346666 component, identifiable by the 10/03/2011 component and identifiable by the VD component. Subsequently, a sendings request to registry 350 can be made by, for example, sendings provider 375 or by some other hardware to provide, for example, all video sendings inventoried. Registry 350 can respond to said request by searching inventory 324 for registration numbers inclusive of VD. For each registration number found, registry 350 can then provide from storage 370 to the requester the video sending having the assigned registration number.
Sendings registry 350 can include a sending class register 326. Class register 326 functions to register a sending by sending class. An exemplary class register 326 is depicted in
Sendings class register 326 can include a received class register 328, depicted in
Sendings class register 326 can include an identified class register 322, depicted in
Sendings class register 326 can include a non-identified class register 327, depicted in
This second embodiment includes a storage 370. Storage 370 functions to store sendings. The storage of sendings in storage 370, including the subsequent locating, reading, copying and deleting can be accomplished in any manner as presently practiced in the electronic storage of a data file. A stored sending can comprise a stored file containing the sending. An exemplary storage 370 is depicted in
Storage 370 can store any sending type sending: audio message type, audio content type, text message type, image type, video type. Storage 370 can be a storage component dedicated solely to storing received sendings and/or received identified sendings. Conversely, storage 370 can be a storage component that stores received sendings and/or received identified sendings and also stores, for example, user-selected sendings. Storage 370 can be a storage component that stores received sendings and/or received identified sendings and also stores, for example, non-related files. Storage 370 can be a storage that stores received sendings and/or received identified sendings across multiple storage components. (Storage 370 can comprise a conventional component or components and, therefore, has not been discussed in detail.)
This second embodiment includes a sendings provider 375. Sendings provider 375 functions to provide sendings. An exemplary sendings provider 375 is depicted in
Sendings provider 375 can operate as an audio sendings provider 331. Audio sendings provider 331 functions to obtain and to dispatch at least one audio sending. Provider 331 can provide an audio sending by obtaining and dispatching the sending. The exemplary provider 375 can operate as a text message sendings provider 332. Text message sendings provider 332 functions to provide at least one text message sending. Provider 332 can provide a text message sending by obtaining and dispatching the sending. The exemplary provider 375 can operate as an image sendings provider 333. Image sendings provider 333 functions to provide at least one image sending. Provider 333 can provide an image sending by obtaining and dispatching the sending. The exemplary provider 375 can operate as a video sendings provider 334. Video sendings provider 334 functions to provide at least one video sending. Provider 334 can provide a video sending by obtaining and dispatching the sending. (Provider 375 can employ one circuitry to provide for the operation of one or more of providers 331, 332, 333 and 334. Conversely, provider 375 can employ a plurality of circuitry to provide for the operation of more than one of providers 331, 332, 333 and 334.)
Exemplary sendings provider 375 includes a sendings obtainer 335 and a sendings dispatcher 336. Sendings obtainer 335 functions to obtain a sending. An exemplary sendings obtainer 335 is depicted in
Obtainer 335 can include a sendings prioritizer 341. Sendings prioritizer 341 functions to prioritize one or more sendings. An exemplary prioritizer 341 is depicted in
As one example of this exemplary prioritizer 341, obtainer 335 can request prioritizer 341 choose a last stored sending. As an example, a sending of a given type from a given telephone number is inventoried by registry 350 and stored in storage 370. At some later date, a next/last sending of the same type from the same telephone number is inventoried by registry 350 and stored in storage 370. Subsequently, for example, provider 375 is triggered by receipt of an incoming call to obtain and dispatch a sending. For this example, obtainer 335 (of provider 375) is configured to obtain the last audio sending received from the calling telephone (the given telephone number). In response to the triggering, obtainer 335 employs prioritizer 341 to determine the last audio sending received from the given/calling telephone number. Prioritizer 341 instructs registry 350 to provide the registration numbers of all image sendings inventoried to the given/calling telephone number. Registry 350 provides, as an example, five registration numbers to prioritizer 341. Included in each registration number is the time/date of registration (registered by time register 371). Prioritizer 341 determines from the time of registration for each of the five registration numbers the last audio sending received and requests registry 350 provide said last audio sending received to sendings dispatcher 336.
As another example of prioritizer 341, prioritizer 341 can in effect prioritize a sending by deleting a prior stored sending upon the arrival of a next sending. For example, from inventory information provided by registry 350, prioritizer 341 can respond to each sending received/registered by registry 350 by searching said inventory information to locate any sendings received prior of the same type and of the same identity information. Prioritizer 341 can employ time registered by time registry 371 to determine a sending received prior. Responsive to locating any of said sending received prior, prioritizer 341 can request registry 350 delete said sending received prior.
As another example of prioritizer 341, prioritizer 341 can be configured to prioritize a sending by requesting registry 350 periodically delete all sendings. For example, prioritizer 341 can request registry 350 delete all sendings at the conclusion to each telephone call or delete all sendings at the conclusion to each calendar day or delete all sendings at the conclusion to each calendar month or delete all sendings at some other event or for some reason. (Said all sendings can be all sendings stored of a given type or can be all sendings stored, can be all sendings inventoried to the same identity information, can be all sendings of a given sending type inventoried to the same identity information or can be other.
As another example of prioritizer 341, prioritizer 341 can be configured to prioritize a sending by randomly choosing a sending from a plurality of stored sendings (said randomly chosen sending subsequently provided by registry 350 for example to dispatcher 336). As one example, prioritizer 341 can employ inventory information from registry 350 to randomly choose a sending from a plurality of sendings inventoried to the same type and same identity information. As another example, prioritizer 341 can employ inventory information from registry 350 to randomly choose a sending from all sendings stored inventoried to the same identity information. As another example, prioritizer 341 can employ inventory information from registry 350 to randomly choose one sending from all sendings stored.
As another example of prioritizer 341, prioritizer 341 can in effect prioritize a sending by requesting registry 350 not inventory and store a sending if a sending has been stored prior inventoried to the same type and same identity information. As another example of prioritizer 341, prioritizer 341 can be configured to prioritize a sending by, for example, requesting registry 350 provide a user-selected sending as a default sending if no received sending is found inventoried to a given identity information. As another example of prioritizer 341, prioritizer 341 can in effect prioritize one or more sendings by requesting registry 350 provide the first sending or sendings found in an inventory, as an example, the first found in an inventory being of a given type and/or of a given identity. (Prioritizer 341 can be located at registry 350. In other words, registry 350 can include for example programming to provide the above-described functionality of prioritizer 341. As examples, registry 350 can be configured to store a sending and delete any prior stored sending, can be configured to periodically delete sendings, can be configured to randomly choose sendings, can be configured to provide the first sending or sendings found in an inventory or can do other.)
This second embodiment can include an-other party address register 357. Other party address register 357 functions to obtain an address of an-other party. An exemplary address register 357 is depicted in
As another example, for a call outgoing from the user, register 357 can stored the telephone number dialed by the user. Register 357 can include circuitry and/or programming for obtaining the telephone number dialed by a user when placing a telephone call. Register 357 can store the obtained called (dialed) telephone number, for this example, at storage Out Number 318, hereafter referred to and shown in
Upon receipt of an incoming call or upon the user dialing a telephone number, register 357 can store the number of the other party's telephone at IN #319 or at OUT #318, respectively. Upon receipt of an incoming call or upon the user dialing a telephone number, register 357 can delete any prior stored telephone number whether located at IN #319 or at OUT #318.
As a first example of provider 375 employing address register 357, during a telephone call, obtainer 335 (of sendings provider 375) can respond to a delivery trigger 390 (trigger 390 described later) by requesting registry 350 provide sendings inventoried registered to the other party's address stored by register 357 in whichever of IN #319 or OUT #318 that contains a newly registered telephone number. Registry 350 can forward sendings found to dispatcher 336.
As a second example of provider 375 employing address register 357, during a telephone call, sendings dispatcher 336 can dispatch a sending to a service provider delivery 369. As one example, said sending dispatched can be a sending file and a file dispatcher 347 of dispatcher 336 (both dispatchers described below) can dispatch the sending file to service provider delivery 369. Along with the sending file, dispatcher 347 can obtain from register 357 the address (for example the telephone number) stored by register 357 and dispatch said address to delivery 369. Delivery 369 can then deliver the sending to a service provider addressed to the address obtained from register 357. The service provider can then deliver the sending to the obtained address. (The above said “during a telephone call” can include the period from when a call is first placed until the call is answered, can include the period of the conversation, can include the period after hang-up of the telephone call, can include the period after hang-up until receipt of a next call and can include the period after hang-up until dialing by the user of a next call. Also, address register 357 can be located elsewhere, for example between provider 375 and deliverer 360. In that configuration, delivery 369 can be electrically connected directly to register 357 and, thus can obtain an address directly from register 357 instead of via dispatcher 347 as disclosed above.) Exemplary sendings provider 375 includes a sendings dispatcher 336. Dispatcher 336 functions to dispatch sendings. An exemplary sendings dispatcher 336 is depicted in
Sendings dispatcher 336 can include an arranger 337. Arranger 337 functions to arrange sendings. An exemplary sendings arranger 337 is depicted in
Arranger 337 can include a gallery arranger 342. Gallery arranger 342 functions to arrange a gallery. An exemplary gallery arranger 342 is depicted in
As another example of this first example, gallery arranger 342 can be configured to arrange the last given number of images inventoried into said one gallery image. For example, arranger 342 can arrange the last six images received registered to the same identity information. Obtainer 335 can employ prioritizer 341 to request registry 350 provide the registration numbers of all image sendings inventoried to the same identity information. For this example, registry 350 provides the registration numbers for ten images to prioritizer 341. Included in each registration number is the time/date of receipt (time/date registered by time register 371). Prioritizer 341 determines from the time/date of receipt of each of the ten images the last six images received. Prioritizer 341 then supplies the registration numbers of said last six images to registry 350 and requests registry 350 provide said last six images to arranger 342. Arranger 342 then arranges the six images onto one gallery image for dispatch to a deliverer 360 (for example to an image display 367 described later). (As another example, gallery arranger 342 can be configured to arrange a given number of randomly selected images, for example employing prioritizer 341, into said one gallery image.)
As a second example of this exemplary gallery arranger 342, arranger 342 can arrange a plurality of text messages. As an example, gallery arranger 342 can be configured to arrange a plurality of text message sendings onto one gallery image (arranged, for example, in rows of text message sendings), said one gallery image for dispatch to a deliverer 360 for delivery. Arranger 342 can arrange any prioritization of text message sendings and in any arrangement as described above in the first example of arranger 342 (arranging image sendings) or can arrange text message sendings otherwise.
As a third example of this exemplary gallery arranger 342, arranger 342 can arrange a plurality of videos. As an example, arranger 342 can be configured to arrange a plurality of videos by taking a frame out of each video and arranging the frames/images into rows arranged to fit onto one gallery image, said one gallery image for dispatch to a deliverer 360 (for example video display 368 described later). As another example, arranger 342 can be configured to arrange a plurality of videos by arranging the frame size of each video to fit onto one gallery image, said one gallery image for dispatch to a deliverer 360 for delivery. (For example arranging the frame sizes into rows arranged to fit onto said gallery image.) The plurality of videos can then be played simultaneously and all arranged playing videos can thus be viewed simultaneously on one display (for example video display 368). (The video can be a video clip and can be played from the beginning of the clip and, when the playing clip reaches it's end, the clip can be replayed.) (Said plurality of videos can be all inventoried videos, can be all videos inventoried to the same identity information, can be all videos inventoried during a given time period, can be all videos inventoried to the same subject or action and registered to the same identity information, can be the last given number of videos received, can be the last given number of videos received inventoried to the same identity information, can be a random selection of a given number of videos or can be other.)
Arranger 337 can include a sendings sequencer 378. Sendings sequencer 378 functions to arrange sequential dispatch. An exemplary sendings sequencer 378 is depicted in
Sequencer 378 can include a timer and can time a duration, for example a five-second duration (or can detect the end of an audio clip, or other). When the five-second duration has expired, sequencer 378 can instruct obtainer 335 to provide registry 350 with a second of the registration numbers corresponding to a second audio sending and instruct registry 350 to read the corresponding file and to forward the read to sequencer 378. Sequencer 378 forwards the read of said second audio sending to be dispatched (for example, forwarded to audio player 338 for dispatching). Arranger 342 can again time a five-second duration. When the five-second duration has expired, sequencer 378 can instruct obtainer 335 to provide registry 350 with a third of the registration numbers corresponding to a third audio sending and can instruct registry 350 to read the file corresponding to said third sending and to forward the read to sequencer 378, and so on. (When the five-second duration for the last audio sending has expired, sequencer 378 can be configured to loop back to obtainment and dispatch of the first audio sending. Also, sequencer 378 can operate similarly to sequentially arrange all audio sendings registered to a given telephone number, for example the telephone number of the other party of a telephone call as stored by register 357. Also, sequencer 378 can operate similarly and additionally can employ prioritizer 341 to arrange a given number out of all audio sendings inventoried for sequential dispatch, i.e. arrange the last given number of audio sendings inventoried, the last given number of audio sendings inventoried registered to a given telephone number or other.)
As a second example of this exemplary sendings sequencer 378, sequencer 378 can arrange text message sendings for sequential dispatch. As an example, sequencer 378 can be configured to sequentially forward for dispatch all text message sendings found in an inventory of registry 350. Sequencer 378 can instruct obtainer 335 to obtain from registry 350 the registration numbers of all text message sendings inventoried and to then provide registry 350 with a first of the registration numbers corresponding to a first text message sending and to instruct registry 350 to read corresponding file and to forward the read to sequencer 378. (Obtainer 335 can employ prioritizer 341 and prioritizer 341 can randomly determine said first sending or can determine the first sending inventoried to be said first sending or other.) Sequencer 378 forwards the read of said first text message sending to be dispatched (for example forwarded to text message feed 339 for dispatching, feed 339 described below).
Sequencer 378 can include a timer and can time a duration, for example a six-second duration (time adequate for the message to be reviewed). When the six-second duration has expired, sequencer 378 can instruct obtainer 335 to provide registry 350 with a second of the registration numbers corresponding to a second text message sending and instruct registry 350 to read the corresponding file and to forward the read to sequencer 378. Sequencer 378 forwards the read of said second text message sending to be dispatched (for example, forwarded to text message feed 339 for dispatching). Arranger 342 can again time a six-second duration. When the six-second duration has expired, sequencer 378 can instruct obtainer 335 to provide registry 350 with a third of the registration numbers corresponding to a third text message sending and instruct registry 350 to read the corresponding file and to forward the read to sequencer 378, and so on. (When the six-second duration for the last text message sending has expired, sequencer 378 can be configured to loop back to obtainment and dispatch of the first text message sending. Also, sequencer 378 can operate similarly to sequentially arrange all text message sendings registered to a given telephone number, for example the telephone number of the other party of a telephone call in progress as stored by register 357. Also, sequencer 378 can operate similarly and additionally can employ prioritizer 341 to arrange a given number out of all text message sendings inventoried for sequential dispatch, i.e. arrange the last given number of text message sendings inventoried, the last given number of text message sendings inventoried registered to a given telephone number or other.)
As a third example of this exemplary sendings sequencer 378, sequencer 378 arrange image sendings for sequential dispatch. As an example, sequencer 378 can be configured to sequentially forward for dispatch all image sendings found in an inventory of registry 350. Sequencer 378 can sequentially forward image sendings in a manner similar to that described in the above given example of sequencer 378 sequentially forwarding text message sendings for dispatch with the exception that image sendings can be forwarded to and dispatched by an image feed (for example image feed 343, feed 343 described below). (Sequencer 378 can sequentially forward all image sendings otherwise.)
(As suggested in the above example for sequencer 378 when configured to sequentially dispatch text message sendings, sequencer 378 can be configured to, upon completion of forwarding a last image sending, loop back to obtainment and dispatch of a first image sending. Also, sequencer 378 can operate similarly as described above for text message sendings, to arrange all image sendings registered to a given telephone number for sequential dispatch, for example the telephone number of the other party of a telephone call in progress. Sequencer 378 can operate similarly as described above for text message sendings and additionally can employ prioritizer 341 to arrange a given number out of all image sendings stored for sequential dispatch, i.e. arrange the last given number of image sendings inventoried, the last given number of image sendings inventoried registered to a given telephone number or other.)
As a fourth example of this exemplary sendings sequencer 378, sequencer 378 can arrange video sendings for sequential dispatch. As an example, sequencer 378 can be configured to sequentially forward for dispatch all video sendings found in an inventory of registry 350. Sequencer 378 can sequentially forward video sendings in a manner similar to that described in the above given example of sequencer 378 sequentially forwarding audio sendings for dispatch with the exception that video sendings can be forwarded to and dispatched by a video player (for example video player 346, player 346 described below). (Sequencer 378 can sequentially forward all video sendings otherwise. Also, Iin an alternate version, a frame can be taken out of each video and the frames/images can be sequentially forwarded to a feed for dispatch, for example image feed 343.)
(As suggested in the above example for sequencer 378 when configured to sequentially dispatch audio messages, sequencer 378 can be configured to loop back to obtainment and dispatch of the first video sending. Also, sequencer 378 can operate, similarly as described above for audio sendings, to sequentially arrange all video sendings registered to a given telephone number, for example the telephone number of the other party of a telephone call in progress, for sequential dispatch. Sequencer 378 can operate similarly as described above for audio sendings and in addition can employ prioritizer 341 to sequentially arrange a given number out of all video sendings inventoried for sequential dispatch, i.e. arrange the last given number of video sendings inventoried, the last given number of video sendings inventoried registered to a given telephone number or other.)
Arranger 337 can include a sendings repeater 392. Sendings repeater 392 functions to arrange repeated dispatch. An exemplary sendings repeater 392 is depicted in
Dispatcher 336 can include an audio player 338. Audio player 338 functions to provide an audio feed. An exemplary audio player 338 is depicted in
Dispatcher 336 can include a text message feed 339. Text message feed 339 functions to provide a text message feed. An exemplary text message feed is depicted in
Dispatcher 336 can include an image feed 343. Image feed 343 functions to provide an image feed. An exemplary text message feed is depicted in
Dispatcher 336 can include a video player 346. Video player 346 functions provide a video feed. An exemplary video player 346 is depicted in
Dispatcher 336 can include a file dispatcher 347. File dispatcher 347 functions to dispatch a sending file. An exemplary file dispatcher 347 is depicted in
This second embodiment includes a deliverer 360. Deliverer 360 functions to deliver sendings. An exemplary deliverer 360 is depicted in
Deliverer 360 can include a speaker 362. Speaker 362 functions to deliver audio. An exemplary speaker 362 is depicted in
Deliverer 360 can include a display 361. Display 361 functions to display at least one sending. An exemplary display 361 is depicted in
Deliverer 360 can include a plurality of display 361. For example, present-day cell phones employ a two-display flip open type of cell phone. The phone when closed sports an outer display and flipping the phone open to converse yields an inner display. Display 361 can comprise said outer display. Display 361 can comprise said inner display. Also, display 361 can function as the prior described caller I.D. display 21. GUI 210 can function as the prior described caller I.D. display 21.
Deliverer 360 can include an email delivery 363. Email delivery 363 functions to deliver sendings for receipt at an email account. An exemplary email delivery 363 is depicted in
Email delivery 363 includes an email delivery addresser 379. Email delivery addresser 379 functions provide an email address. An exemplary email delivery addresser 379 is depicted in
Deliverer 360 can include a web-site poster 374. Web-site poster 374 functions to post sendings to an internet web-site. An exemplary web-site poster 374 is depicted in
Web-site poster 374 includes a web-site poster addresser 381. Web-site poster addresser 381 functions to provide an internet web-site address. An exemplary web-site poster addresser 381 is depicted in
As another example of the exemplary addresser 381, addresser 381 can be supplied an internet address by a telephone manufacturer said internet address can be an address programmed into telephone 27. As another example, addresser 381 can be supplied an internet address by service provider 121. For example, said address supplied can be that of a social media web-site.
Web-site poster 374 can include a manual poster 453. Manual poster 453 functions to enable a user to post a sending to a web-site. An exemplary manual poster 453 is depicted in
Web-site poster 374 can include an auto poster 454. Auto poster 454 functions to automatically post a sending to a web-site. An exemplary auto poster 454 is depicted in
Deliverer 360 can include a telephone service provider delivery 369. Service provider delivery 369 functions to deliver sendings to a telephone service provider. An exemplary service provider delivery 369 is depicted in
Service provider delivery 369 includes a service provider delivery addresser 386. Service provider delivery addresser 386 functions to provide an address. An exemplary service provider delivery addresser 386 is depicted in
Deliverer 360 can include a delivery port 364. Delivery port 364 functions to enable delivery of sendings to an external device. An exemplary delivery port 364 is depicted in
Deliverer 360 can include a ring-back delivery 391. Ring-back delivery 391 functions to deliver a ring-back. An exemplary ring-back delivery 391 is depicted in
Deliverer 360 can include a ring-back forward delivery 433. Ring-back forward delivery 433 functions to deliver a sending as a ring-back to the user. An exemplary ring-back forward delivery 433 is depicted in
Deliverer 360 can include a ring-tone delivery 434. Ring-tone delivery 434 functions to deliver a received sending as a ring-tone. An exemplary ring-tone delivery 391 is depicted in
(Also, the described-prior origin identity information can be delivered by deliverer 360 along with a sending. Said identity information can be obtained by obtainer 335 and forwarded from registry 350 to dispatcher 336 Dispatcher 336 can dispatch said identity information to, for example, display 361 an/or speaker 362. Speaker 362 can then announce said identity information and/or display 361 can then display said identity information.)
This second embodiment includes a delivery trigger 390. Delivery trigger 390 functions to initiate the providing of a sending. An exemplary delivery trigger 390 is depicted in
Exemplary delivery trigger 390 can include a linked trigger 393. Linked trigger 393 functions to initiate the providing of a sending linked to an activity. An exemplary linked trigger 393 is depicted in
For this exemplary linked trigger 393, said activity can be (for example): receipt of a sending from the other party; receipt of a sending from the other party during or after a telephone call; the user's deployment of an audio message; the user's deployment of an audio content; the user's deployment of an image (picture); the user's deployment of a video; or can be other.
For this exemplary linked trigger 393, said activity can be a telephone event (for example): a receipt/detection of an incoming call; an answering of an incoming call; a user hang-up; a caller hang-up; a receipt of an incoming call placed from a specific telephone; a timed duration subsequent to or prior to a telephone event; a completion of dialing a telephone number; and any other telephone event.
As an example of operation, linked trigger 393 can initiate the providing of a sending linked to detection of an incoming call. As an example, system 10 can include circuitry to detect an incoming call (activity). Said detection is signaled to trigger 393. Trigger 393 responds by signaling obtainer 335 of provider 375. Obtainer 335 responds to the signal from trigger 393 by requesting registry 350 forward to dispatcher 336 a sending (or sendings) inventoried to the calling party's telephone number stored in other party address register 357. Dispatcher 336 can then dispatch the sending to deliverer 360. Deliverer 360 can then deliver the sending to the calling party's telephone number stored in other party address register 357. (Trigger 393 is depicted in figures herein comprising a diagrammatic block. Trigger 393 can comprise circuitry and/or programming. Conversely, trigger 393 can merely be an electrical connection between, for example, two components. As an example, in the above example, said detection of an incoming call is described as being signaled to trigger 393 and trigger 393 then signals obtainer 335. Said detection of an incoming call can in actuality be signaled directly to obtainer 335. For this example, trigger 393 comprises the electrical connection between said circuitry to detect an incoming call and said obtainer 335.)
A first example of this second embodiment is illustrated as system 10ee in
For this first example, sendings receiver 340 includes at least one of telephone receiver 344, email receiver 351 and internet receiver 409. Sendings registry 350 includes automatic register 401 and inventory 324. Sendings provider 375 includes sendings obtainer 335 and sendings dispatcher 336. Deliverer 360 includes one or more of: speaker 362; display 361; text message display 366; image display 367; video display 368; email delivery 363; internet delivery 374; service provider delivery 369; delivery port 364; ring-back delivery 391; ring-back forward delivery 433 and ring-tone delivery 434. Telephone 27ee comprises mobile phone 165.
(Registry 350 can include user-selected default 410. Obtainer 335 can include prioritizer 341. Sendings dispatcher 336 can include arranger 337. Arranger 337 can include one or more of: gallery 342; sequencer 348; and repeater 392. Delivery trigger 390 can include user-deploy trigger 394. Provider 375 can include sendings call-up 396. Sendings identifier 345 can include one or more of: universal identifier 349; special address identifier 437; manual identifier 403; requested sendings identifier 355; and auto-requester 365. Configurator 395 can include one or more of: a configuration selector 389; an enabler 373; and a data entry 407. System 10ee can include telephone 27ee and, thus, can include phone 165. System 10ee can include the prior-described caller I.D. circuitry 20. System 10ee can include GUI 210 and GUI 210 can operate as one or more of: addresser 386, addresser 379 and addresser 381.)
For this first example, sendings receiver 340 can be electrically connected to (or connectable to) sendings registry 350. Sendings registry 350 can be electrically connected to (or connectable to) storage 370. Sendings provider 375 can be electrically connected to (or connectable to) sendings registry 350 and can be electrically connected to (or connectable to) deliverer 360. Linked trigger 393 can be electrically connected to (or connectable to) sendings provider 375.
For this first example, system 10ee can include other party address register 357. Other party address register 357 obtains the telephone number of an-other party. Register 357 can also store the obtained telephone number. Register 357 includes circuitry and/or programming to obtain from caller I.D. information the telephone number of the calling telephone. Register 357 can store the obtained telephone number at storage IN #319. Obtainer 335 can employ the telephone number stored at IN #319 to request one or more sendings from registry 350. Service provider delivery 369 can employ the telephone number stored at IN #319 to designate, to provider 121 for example, where a sending is to be delivered. Provider 121 can then deliver the sending to the telephone (other party's) of the telephone number stored at IN #319. Register 357 includes circuitry and/or programming for obtaining the telephone number dialed by a user when placing a telephone call. Register 357 can store the obtained called (dialed) telephone number at OUT #318. Obtainer 335 can then employ the telephone number stored at OUT #318 to request one or more sendings from registry 350. Service provider delivery 369 can employ the telephone number stored in OUT #318 to designate to provider 121 where a sending is to be delivered. Provider 121 can then deliver the sending to the telephone (other party's) of the telephone number stored at OUT #318. Upon receipt of an incoming call or upon the user dialing a telephone number, register 357 can store the number of the other party's telephone at IN #319 or at OUT #318, respectively. Upon receipt of an incoming call or upon the user dialing a telephone number, register 357 deletes any prior stored telephone number whether located at IN #319 or at OUT #318 (or at both of them).
For this first example, delivery trigger 390 comprises linked trigger 393. Trigger 393 initiates the providing of a sending linked to an activity. The occurrence of an activity sends a signal (triggers) linked trigger 393. Trigger 393 responds by sending a signal to obtainer 335 of provider 375. Obtainer 335 responds by requesting registry 350 forward a sending or sendings. The sending or sendings can be registered to a telephone number stored in other party address register 357. Registry 350 responds by forwarding said sending or sendings to dispatcher 336. Dispatcher 336 dispatches said sending or sendings to deliverer 360. Deliverer 360 delivers said sending or sendings.
ONE EXAMPLE OF OPERATION of receiving and inventorying sendings will now be given. Sendings received and inventoried as per this example can subsequently be provided by provider 375. For the following examples of operation for this first example of this second embodiment, sendings provider 375 provides sendings received and inventoried as per this example. For the first through eighth examples of this second embodiment, sendings provider 375 can provide sendings received and inventoried as per this example.
At some point in time, whether over the phone, or in person, or in an email, or via a text message, or via a prior user-selected and stored message deployed by the user during a telephone conversation with an-other party, or in some other manner, the user asks the other party whom the user anticipates conversing with over the telephone in the future to provide the user with sendings. For this ONE EXAMPLE OF OPERATION, the user requests two sendings from the other party: a favorite audio clip (of the other party); and a picture of or representative of himself (the other party). The other party has a favorite audio clip stored in his cell phone. He supplies the audio clip (sending) by telephone mailing the audio clip from his cell phone along with a telephone delivery address comprising the user's telephone 27. A telephone service provider (provider 121) delivers the audio clip to the user's telephone 27. Delivered by the service provider (provider 121) along with the audio clip (sending) is origin identity information and sending type information, for this example the telephone number of the dispatching telephone and audio type respectively. Telephone provider receiver 344 receives the audio clip (sending) and also receives said origin identity information and sending type information (telephone number of dispatching telephone, audio type). Receiver 344 forwards the received audio sending origin identity information and sending type information to sendings registry 350. Registry 350 employs origin register 358 to register the audio clip sending to the received identity information (for this example, said origin identity information comprises the telephone number of the other party's telephone and telephone number register 359 of origin register 358 registers said the audio sending under the telephone number). Registry 350 employs audio type register 388 of type register 372 to register the audio clip sending to the received sending type information. (For this example, said sending type information comprises a representation of audio type and audio type register 388 registers the sending under audio type). Registry 350 compiles the registered identity information and the registered sending type information into a registration number to represent the audio sending and includes the registration number in inventory 324. Registry 350 forwards the audio sending to storage 370. (For a received text message sending, text message type register 382 of type register 372 registers the sending under text message type. For a received image sending, image type register 383 of type register 372 registers the sending under image type. For a received video sending, video type register 384 of type register 372 registers the sending under video type. Said received video sending can comprise a video with audio sending or register 372 can include a video with audio register.)
To furnish the second requested sending, said other party has an image of himself stored on his PC. He supplies the image by including the image in an email and addressing the email for delivery to the user's email account. Email service delivers the email to said user's email account. Delivered along with the image (sending) is origin identity information, for this example the other party's cell phone telephone number included by the other party with the return address of the email. Also delivered along with the image (sending) is sending type information. Email receiver 351 receives the delivered email from said user's email account and also receives said identity information and said sending type information. Matcher 353 of receiver 351 obtains said telephone number included with the return address. Receiver 351 forwards the received image sending, obtained telephone number and received sending type information to sendings registry 350. Origin register 358 of registry 350 registers the image sending to the identity information (in this case telephone number register 359 of origin register 358 registers the sending under the obtained telephone number). Registry 350 also registers the image sending to the received sending type information (in this case image register 383 of type register 372 registers the sending under image type). Registry 350 compiles the registered identity information and the registered sending type information into a registration number to represent the image sending and includes the registration number in inventory 324. Registry 350 forwards the image sending to storage 370. (For a received audio sending, image type register 388 of type register 372 registers the sending under audio. For a received text message sending, text message type register 382 of type register 372 registers the sending under text message type. For a received video sending, video type register 384 of type register 372 registers the sending under video type.)
This first example (system 10ee) can be configured to respond to initiation by trigger 393 by one or more of: a) providing an audio sending dispatched by audio player 338 to speaker 362, b) providing an audio sending dispatched by audio player 338 to ring-back delivery 391, c) providing a text message sending dispatched by text message feed 339 to text message display 366, d) providing an image sending dispatched by image feed 343 to image display 367, e) providing a video sending dispatched by video player 346 to video display 368, providing one or more of: f) an audio sending, g) a text message sending, h) an image sending and i) video sending, said providing one or more of dispatched by file dispatcher 347 to one or more of deliverers: j) email delivery 363, k) internet delivery 374, 1) service provider delivery 369 and m) delivery port 364.
Responses “a” through “e” can be combined 24 different ways: a, b, c, d, e, ab, ac, ad, ae, bc, bd, be, cd, ce abc, abd, abe, bcd, bce, abcd, abce, acde, bcde, abcde.
Responses “f”, “g” “h”, and “i” can be combined with deliverers “j”, “k”, “l”, and “m” different ways: fj, fk, fl, fm, gj, gk, gl, gm, hj, hk, hl, hm, ij, ik, il, im, fgj, fgk, fgl, fgm, ghj, ghk, ghl, ghm, hij, hik, hil, him, fghj, fghk, fghl, fghm, ghij, ghik, ghil, ghim, fghij, fghik, fghil, fghim, fjk, fjl, fjm, gjk, gkl, gkm, hjk, hjl, hjm, ijk, iji, ijm, fkl, flm, gkl, gkm, hkl, hkm, flm, glm, hlm, ilm, fjkl, fklm, gjkl, gklm, hjkl, hklm, ijkl, iklm, fjklm, gjklm, hjklm, ijkln, fgjk, fgjl, fgjm, fgkl, fgkm, fglm, fhjk, fhjl, fhjm, fhkm, fhkm, fhlm, fijk, fijl, fijm, fikl, fikm, film, ghik, ghil, ghim, ghkl, ghkm, ghlm, ghjk, ghjl, ghjm, ghkl, ghkm,ghlm, gijk, gijl, gijm, gikl, gikm, gilm, hijk, hijl, hijm, hikl, hikm, hilm, fghjk, fghjl, fghjm, fghkl, fghkm, fghlm, ghijk, ghijl, ghijm, ghikl, ghikm, ghilm, fghijk, fghijl, fghijm, fghikl, fghikm, fghilm, fjkl, fjkm, fjlm, fklm, gjkl, gjkm, gjlm, gklm, hjkl, hjlm, hjlm, hklm, ijkl, ijkm, ijlm, iklm, fgjkl, fgjkm, fgjlm, fgklm, fhjkl, fhjkm, fhjlm, fhklm, fijkl, fijkm, fikjlm,fiklm, ghjkl, ghjkm, ghjlm, ghklm, gijkl, gijkm, gijlm, giklm, hijkl, hijkm, hijlm, hikim, fghjkl, fghjkm, fghjlm, fghklm, fhijkl, fhijkm, fhijlm, fhiklm, ghijkl, ghijkm, ghijlm, ghiklm, fghijkl, fghijkm, fghijlm, fghiklm, fgjklm, fhjklm, fijklm, ghjklm, gijklm, hijklm, fghjklm, fgijklm, fhijklm, ghijklm, fghijklm, and permutations thereof.
The 24 combinations of “a” through “e” responses can be combined with the 203 combinations of “f”, “g” “h”, “i” combined with deliverers “j”, “k”, “l”, “m” responses, in other words 203 totaling 4872 combinations.
The 24 combinations of “a” through “e” responses+the 204 combinations of “f”, “g”, “h”, “i” combined with deliverers T, “k”, “l”, “m” responses+the 4848 combinations=5098 total combinations. In other words, this first example (system 10ee) can be configured to provide at least 5098 different response combinations. (In addition to the above “a” through “e”, system 10ee can be further configured to respond to initiation by trigger 393 by providing an audio sending dispatched by audio player 338 to ring-back forward delivery 433 and by providing an audio sending dispatched by audio player 338 to ring-tone delivery 434.) In addition to said 5098 different response combinations, system 10ee can be configured to provide a given plurality of responses in a cadence rather than merely all responses simultaneously. As an example of a cadence, an audio sending is delivered as a ring-back by ring-back delivery 391, three seconds later an image sending is delivered by image display 367, five seconds later a video sending is delivered by video display 367 and four seconds later an image sending is delivered by provider delivery 369. Further, system 10ee can be configured to provide a plurality of cadences relative to a given plurality of responses, the cadence employed dependent for example on circumstances related to the telephone call. In summary, system 10ee can be configured to respond to linked trigger 393 in thousands of unique ways. (System 10ee can also be configured to respond to a plurality of initiations by trigger 393. As an example, a first response to an initiation triggered by receipt of an incoming call or completion of dialing an outgoing call, a second response to an initiation triggered by answering of the call by user or by other party and a third response to an initiation triggered by hang up of the call by user or by other party. For each of said plurality of initiations, the same sending or combination of sendings can be provided. For each of said plurality of initiations, a unique sending or unique combination of sendings can be provided.)
Operation of but two examples of the thousands of unique ways system 10ee can respond to linked trigger 393 will now be discussed in greater detail.
A first example of operation for this first example (system 10ee) of this second embodiment will now be given (1EX1:). For this example, provider 375 initiated by trigger 393 provides one or more sendings. For this example, said provided sendings are sendings registered to the telephone number (address) of an-other party's telephone, said telephone number obtained by other party address register 357. Provider 375 provides said sendings to deliverer 360 and deliverer 360 delivers said sendings. This example is a continuation from the above-given “ONE EXAMPLE OF OPERATION of receiving and inventorying sendings”:
Said audio sending and said image sending supplied by said other party have been received, inventoried and stored. (Also stored can be many other sendings from parties in addition to said other party, said many other sendings also received, inventoried and stored.) Some time later, the user places a call to said other party by dialing the telephone number of said other party's telephone. Other party address register 357 obtains and stores the dialed telephone number in storage OUT #318. A signal indicating the completion of dialing the telephone number (activity) triggers linked trigger 393. Trigger 393 responds by signaling obtainer 335 of provider 375. For this example, obtainer 335 is configured to respond to the signal by requesting registry 350 forward all sendings stored in storage 370 registered to the telephone number stored by other party address register 357 in storage OUT #318. Registry 350 responds by forwarding said sending or sendings to dispatcher 336 (for this example registry 350 responds by forwarding the audio sending and image sending supplied by said other party and received, inventoried and stored). Dispatcher 336 dispatches said sending or sendings to deliverer 360. Deliverer 360 delivers said sending or sendings.
For this first example of operation, dispatcher 336 employs audio player 338. Audio player 338 plays the audio sending and dispatches an audio feed of the playing audio sending to speaker 362 of deliverer 360. In one configuration, speaker 362 comprises a broadcasting type speaker and the audio is broadcast therefrom. The user listens to the ring-back tone from provider 121 indicating that the other party's telephone is being rung and, at the same time, listens to the playing audio sending out of the broadcasting type speaker. In another configuration, audio player 338 dispatches the audio feed to ring-back forward delivery 433. Ring-back forward delivery 433 plays the audio to the user via the telephone receiver of telephone 27ee as the ring-back tone indicating that the other party's telephone is being rung. (In another configuration, player 338 dispatches to both speaker 362 and delivery 433.)
For this first example of operation, dispatcher 336 employs image feed 343. Image feed 343 dispatches a feed of the read image sending (read by registry 350) to image display 367 of deliverer 360. While the other party's telephone is being rung, the image sending is displayed on display 367 for the user to view. When the other party answers, feed 343 can continue or discontinue display of the image.
For this first example of operation, dispatcher 336 also employs file dispatcher 347. Dispatcher 347 dispatches the file containing the image sending (copied and forwarded from registry 350) to service provider delivery 369 of deliverer 360. Delivery 369 delivers the image sending file to service provider 121 along with the other party's telephone number, said telephone number from storage OUT #318. Subsequently, provider 121 delivers the sending to the other party's telephone. The other party's telephone can display the image for the other party to view while their telephone is being rung and after they answer etc.
A second example of operation for this first example (system 10ee) of this second embodiment will now be given (1EX2:). For this example, provider 375 initiated by trigger 393 provides one or more sendings. For this example, said provided sendings are sendings registered to the telephone number (address) of an-other party's telephone, said telephone number obtained by other party address register 357. Provider 375 provides said sendings to deliverer 360 and deliverer 360 delivers said sendings. This example is a continuation from the above-given “ONE EXAMPLE OF OPERATION of receiving and inventorying sendings”:
Said audio sending and image sending supplied by said other party have been received, inventoried and stored. Some time later, a telephone call is received from said other party. Other party address register 357 obtains, from caller I.D. information, the other party's telephone's number and stores the telephone number in storage IN #319. The incoming call is detected (activity) and a signal representing said detection triggers linked trigger 393. Trigger 393 responds by signaling obtainer 335 of provider 375. For this example, obtainer 335 is configured to respond to the signal by requesting registry 350 forward all sendings stored in storage 370 registered to the telephone number stored by address register 357 in storage IN #319. Registry 350 responds by forwarding said sending or sendings to dispatcher 336 (for this example registry 350 responds by forwarding the audio sending and image sending supplied by said other party and received, inventoried and stored). Dispatcher 336 dispatches said sending or sendings to deliverer 360. Deliverer 360 delivers said sending or sendings.
For this second example of operation, dispatcher 336 employs audio player 338. Audio player 338 plays the audio sending and dispatches an audio feed of the playing audio sending to speaker 362 of deliverer 360. In one configuration, speaker 362 comprises a broadcasting type speaker and the audio is broadcast therefrom. The user listens to the ring-back from provider 121 indicating the unanswered incoming telephone and, at the same time, listens to the playing audio sending out of the broadcasting type speaker. In another configuration, dispatcher 338 dispatches the audio feed to ring-tone delivery 434. Ring-tone delivery 434 delivers the playing audio to the user via the receiver of telephone 27ee indicating that the other party's telephone is being rung. (In another configuration, player 338 dispatches to both speaker 362 and delivery 434.)
For this second example of operation, dispatcher 336 further employs audio player 338. Audio player 338 plays the audio sending and dispatches an audio feed of the playing audio sending to ring-back delivery 391. Delivery 391 includes answering circuitry to detect and answer the incoming call and to deliver the playing audio to the caller, the audio to entertain the caller and inform the caller that the user is being alerted.
For this second example of operation, dispatcher 336 employs image feed 343. Image feed 343 dispatches a feed of the read image sending (read by registry 350) to image display 367 of deliverer 360. For this example, image display 367 comprises the outer display of a two-display flip open type of cell phone 165. While the user's telephone is being rung indicating the unanswered incoming call, the image sending is displayed on said outer display. The user views the image and from the image can decide if he cares to converse with this caller. For this example, the image sending is also displayed on the inner display of the two-display flip open cell phone 165. If the user flips open the two-display flip open type of cell phone 165 to answer the call, the user can continue to admire the image sending. When the user answers the call, feed 343 can continue or to discontinue display of the image on one or both of outer and inner display or some combination of continued or discontinued thereof.
For this second example of operation, dispatcher 336 also employs file dispatcher 347. Dispatcher 347 dispatches the file containing the image sending (copied and forwarded from registry 350) to service provider delivery 369 of deliverer 360. Delivery 369 delivers the image sending file to service provider 121 along with the other party's telephone number, said telephone number from storage IN #319. Provider 121 delivers the sending to the other party's telephone. The other party's telephone can display the image for the other party to view while they wait for the user to answer and after the user answers etc.
A brief description of operation of additional examples of the thousands of unique ways to respond to linked trigger 393 will now be given. With respect to system 10ee of
Example 1EX3: Triggered by user or caller answering. Last stored audio sending delivered by broadcasting type of speaker 362. User hears sending and other party hears in background.
Example 1EX4: Triggered by user or caller hang up. Last stored video sending delivered by service provider delivery 369 to other party's telephone. Other party can watch video.
Example 1EX5: An audio sending and a text message sending furnished by an other party are repeatedly provided to the user when the user dials the other party
Example 1EX6: An audio sending and an image sending furnished by an-other party are provided to the user when the user dials the other party's phone.
Example 1EX7: Triggered by receipt of a sending to inventory, store the sending and send the sending back to the sender.
Example 1EX8: Triggered by user or other party answering. On Christmas, a text message greeting is provided to the user and to the other party.
In one variation, a sending received by receiver 340 can be immediately delivered by deliverer 360. (In one example, the identifying of a sending can comprise an activity that triggers trigger 393 to initiate provider 375 to provide the sending to deliverer 360.) As one example, a received sending can be forwarded to registry 350. Registry 350 can determine from sending type information included with the sending the appropriate dispatcher to dispatch the determined type. Registry 350 can then forward the sending to the dispatcher and the dispatcher can dispatch the sending to a deliverer (registry 350 can also inventory and store the sending). As an example, the sending type is determined by registry 350 to be text message type. Registry 350 forwards the text message sending to text message feed 339. Feed 343 is configured to dispatch the sending to text message display 366. Display 366 displays the dispatched text message sending. As another example, the sending type is determined by registry 350 to be video. Registry 350 forwards the video sending to file dispatcher 347. Dispatcher 347 dispatches the video sending to internet delivery 374. Delivery 374 posts the video on an internet social media website, for example, You Tube. (The prior described identity information can also be immediately delivered.)
Delivery trigger 390 can include a user-deploy trigger 394. User-deploy trigger 394 functions to enable a user to trigger the providing of at least one sending. An exemplary user-deploy trigger 394 is depicted in
As an example of operation, user-deploy trigger 394 can enable a user to trigger the providing of a sending during receipt of a telephone call. As an example, during receipt of an incoming call, after viewing caller I.D. information and prior to answering, the user decides to deploy sendings registered to the calling party's telephone. To do so, the user touches deploy trigger icon 398 provided by GUI 210. GUI 210 responds to the touched trigger icon 398 by signaling provider 375. Provider 375 responds by employing obtainer 335 to obtain all sendings registered to the calling party's telephone number. (For this example, obtainer 375 is configured to obtain all sendings registered to the telephone number obtained by other party address register 357.) Obtainer 335 responds by requesting registry 350 provide all sendings registered to the caller's telephone number stored by other party address register 357 to dispatcher 336. Registry 350 responds by providing the requested all sendings to dispatcher 336. Dispatcher 336 forwards the provided all sendings to deliverer 360. Deliverer 360 then delivers the sendings. (As one example, dispatcher 336 can be configured to dispatch all sendings via file dispatcher 347. Said all sendings dispatched by dispatcher 347 can then be delivered by service provider delivery 369 of deliverer 360 to the caller's telephone. Also, in one variation delivery trigger 390 can include an-other party deploy trigger. Said other party deploy trigger can function to enable an-other party, for example an-other party of a telephone call with the user, to trigger the providing of at least one sending. As an example, provider 375 can be configured to respond to a pressing of the pound key on the other party's telephone, for example when said other party phone and the user's phone are communicably connected, by obtaining and dispatching a sending to deliverer 360. Deliver 360 then delivers the sending.)
A second example of this second embodiment is illustrated as system 10ff in
For this second example, sendings receiver 340 includes at least one of telephone receiver 344, email receiver 351 and internet receiver 409. Sendings registry 350 includes automatic register 401 and inventory 324. Sendings provider 375 includes sendings obtainer 335 and sendings dispatcher 336. Deliverer 360 includes one or more of: speaker 362; display 361; text message display 366; image display 367; video display 368; email delivery 363; internet delivery 374; service provider delivery 369; delivery port 364; ring-back delivery 391; ring-back forward delivery 433; and ring-tone delivery 434. Delivery trigger 390 includes user-deploy trigger 394. System 10ff can include the prior-described caller I.D. circuitry 20. Circuitry 20 employs GUI 210 to serve as display 21 to display caller I.D. information to the user. Telephone 27ff can comprise mobile phone 165.
(Registry 350 can include user-selected default 410. Obtainer 335 can include prioritizer 341. Dispatcher 336 can include arranger 337. Arranger 337 can include one or more of: gallery 342; sequencer 348; and repeater 392. Trigger 390 can include linked trigger 393. Sendings identifier 345 can include one or more of universal identifier 349; special address identifier 437; manual identifier 403; requested sendings identifier 355; and auto-requester 365. Configurator 395 can include one or more of: a configuration selector 389; an enabler 373; and a data entry 407. System 10ff can include telephone 27ff and, thus, can include phone 165.)
For this second example, sendings receiver 340 can be electrically connected to (or connectable to) sendings registry 350. Sendings registry 350 can be electrically connected to (or connectable to) storage 370. Sendings provider 375 can be electrically connected to (or connectable to) sendings registry 350 and can be electrically connected to (or connectable to) deliverer 360. To operate as user-deploy trigger 394, GUI 210 can be electrically connected to (or connectable to) sendings provider 375.
For this second example, system 10ff can include other party address register 357. Other party address register 357 obtains the telephone number of an-other party. Register 357 can also store the obtained telephone number. Register 357 includes circuitry and/or programming to obtain from caller I.D. information the telephone number of the calling telephone. Register 357 can store the obtained telephone number at storage IN #319. Obtainer 335 can employ the telephone number stored at IN #319 to request one or more sendings from registry 350. Service provider delivery 369 can employ the telephone number stored at IN #319 to designate, to provider 121 for example, where a sending is to be delivered. Provider 121 can then deliver the sending to the telephone (other party's) of the telephone number stored at IN #319. Register 357 includes circuitry and/or programming for obtaining the telephone number dialed by a user when placing a telephone call. Register 357 can store the obtained called (dialed) telephone number at OUT #318. Obtainer 335 can then employ the telephone number stored at OUT #318 to request one or more sendings from registry 350. Service provider delivery 369 can employ the telephone number stored in OUT #318 to designate to provider 121 where a sending is to be delivered. Provider 121 can then deliver the sending to the telephone (other party's) of the telephone number stored at OUT #318. Upon receipt of an incoming call or upon the user dialing a telephone number, register 357 can store the number of the other party's telephone at IN #319 or at OUT #318, respectively. Upon receipt of an incoming call or upon the user dialing a telephone number, register 357 deletes any prior stored telephone number whether located at IN #319 or at OUT #318.
For this second example, delivery trigger 390 comprises user-deploy trigger 394. Trigger 394 initiates the providing of a sending. User-deploy trigger includes GUI 210. GUI 210 displays deploy trigger icon 398. A touched deploy trigger icon 398 causes GUI 210 to send a signal to obtainer 335 of provider 375. Obtainer 335 responds by requesting registry 350 forward a sending or sendings. The sending or sendings can be registered to a telephone number stored in other party address register 357. Registry 350 responds by forwarding said sending or sendings to dispatcher 336. Dispatcher 336 dispatches said sending or sendings to deliverer 360. Deliverer 360 delivers said sending or sendings.
This second example can be configured to respond to deployed trigger 394 in a like manner as disclosed for the first example responding to trigger 393. In other words, this second example can respond by one or more of: a) providing an audio sending dispatched by audio player 338 to speaker 362, b) providing an audio sending dispatched by audio player 338 to ring-back delivery 391, c) providing a text message sending dispatched by text message feed 339 to text message display 366, d) providing an image sending dispatched by image feed 343 to image display 367, e) providing a video sending dispatched by video player 346 to video display 368, providing one or more of: f) an audio sending, g) a text message sending, h) an image sending and i) video sending, said providing one or more of dispatched by file dispatcher 347 to one or more of deliverers: j) email delivery 363, k) internet delivery 374, l) service provider delivery 369 and m) delivery port 364.
As with the responses disclosed for the first example (system 10ee), for this second example (system 10ff) responses “a” through “e” can be combined 24 different ways. Responses “f”, “g” “h”, and “i” can be combined with deliverers “j”, “k”, “l”, and “m” 203 different ways: The 24 combinations of “a” through “e” responses can be combined with the 203 combinations of “f”, “g” “h”, “i” combined with deliverers “j”, “k”, “l”, “m” responses, in other words 24 multiplied by 203 totaling 4872 combinations. The 24 combinations of “a” through “e” responses +the 204 combinations of “f”, “g”, “h”, “i” combined with deliverers “j”, “k”, “l”, “m” responses+the 4848 combinations=5098 total combinations. In other words, this second example (system 10ff) can be configured at least 5098 different ways to respond to deploy trigger 394.
In addition, as discussed for system 10ee, system 10ff can also be configured to provide a given plurality of responses in a cadence rather than merely all responses simultaneously and can be configured to provide a plurality of cadences relative to a given plurality of responses (and can be configured to respond to a plurality of initiations by trigger 394). In summary, like system 10ee system 10ff can be configured to respond to deploy trigger 394 in thousands of unique ways.
Out of the thousands of ways to respond to deploy trigger 394, two detailed examples of operation of system 10ff will now be given.
A first example of operation for this second example (system 10ff) of this second embodiment will now be given (2EX1:). For this example, provider 375 initiated by trigger 394 provides one or more sendings. For this example, said provided sendings are sendings registered to the telephone number (address) of an-other party's telephone, said telephone number obtained by other party address register 357. Provider 375 provides said sendings to deliverer 360 and deliverer 360 delivers said sendings. This example is a continuation from the above-given “ONE EXAMPLE OF OPERATION of receiving and inventorying sendings”:
Said audio sending and said image sending supplied by said other party have been received, inventoried and stored. (Also stored can be many many other sendings from parties in addition to said other party, said sendings also received, inventoried and stored.) Some time later, the user places a call to said other party by dialing the telephone number of said other party's telephone. Other party address register 357 of system 10ff obtains and stores the dialed telephone number in storage OUT #318. At the completion of dialing the telephone number, the user touches deploy trigger icon 398 displayed on GUI 210. GUI 210 responds to touched icon 398 by signaling obtainer 335 of provider 375. For this example, obtainer 335 is configured to respond to the signal by requesting registry 350 forward all sendings stored in storage 370 registered to the telephone number stored by other party address register 357 in OUT #318. Registry 350 responds by forwarding said sending or sendings to dispatcher 336 (for this example the audio sending and image sending supplied by said other party and received, inventoried and stored). Dispatcher 336 dispatches said sending or sendings to deliverer 360. Deliverer 360 delivers said sending or sendings.
For this first example of operation, dispatcher 336 employs audio player 338. Audio player 338 plays the audio sending and dispatches an audio feed of the playing audio sending to speaker 362 of deliverer 360. In one configuration, speaker 362 comprises a broadcasting type speaker and the audio is broadcast therefrom. The user listens to the ring-back tone from provider 121 indicating that the other party's telephone is being rung and, at the same time, listens to the playing audio sending out of the broadcasting type speaker. In another configuration, audio player 338 dispatches the audio feed to ring-back forward 433. Ring-back forward 433 plays the audio to the user via the telephone receiver of telephone 27ff as the ring-back tone indicating that the other party's telephone is being rung. (In another configuration, player 338 dispatches to both speaker 362 and the telephone receiver of telephone 27ff.)
For this first example of operation, dispatcher 336 also employs image feed 343. Image feed 343 dispatches a feed of the read image sending (read by registry 350) to image display 367 of deliverer 360. For this example, image display 367 comprises the bottom one-third of the display of GUI 210, said bottom one-third of GUI 210 dedicated as display 367. While the other party's telephone is being rung, the image sending is displayed on said bottom one-third of the display of GUI 210 for the user to view. When the other party answers, feed 343 can continue or discontinue display of the image.
For this first example of operation, dispatcher 336 also employs file dispatcher 347. Dispatcher 347 dispatches the file containing the image sending (copied and forwarded from registry 350) to service provider delivery 369 of deliverer 360. Delivery 369 delivers the image sending file to service provider 121 along with the other party's (dialed) telephone number from address register 357 storage OUT #318. Provider 121 delivers the sending to the other party's telephone. The other party's telephone can display the image for the other party to view while their telephone is being rung and after they answer etc.
For this first example of operation, dispatcher 336 further employs file dispatcher 347. Dispatcher 347 dispatches the file containing the image sending (copied and forwarded from registry 350) to internet delivery 374 of deliverer 360. The sending file, inclusive of an internet address supplied prior by the user, is delivered by delivery 374 to an internet service provider, for example to Microsoft Internet Explorer. MS Explorer delivers the sending file to the included internet address, for this example the social media website Facebook. For this example, the image is posted on Facebook to the user's account under a heading “Recently Called”.
A second example of operation for this second example (system 10ff) of this second embodiment will now be given (Example 2EX2:). For this example, provider 375 initiated by trigger 394 provides one or more sendings. For this example, said provided sendings are sendings registered to the telephone number (address) of an-other party's telephone, said telephone number obtained by other party address register 357. Provider 375 provides said sendings to deliverer 360 and deliverer 360 delivers said sendings. For this example, system 10ff includes caller I.D. circuitry 20. This example is a continuation from the above-given “ONE EXAMPLE OF OPERATION of receiving and inventorying sendings”:
Said audio sending and image sending supplied by said other party have been received, inventoried and stored. Some time later, a telephone call is received from said other party. Other party address register 357 of system 10ff obtains, from caller I.D. information, the other party's telephone's number and stores the telephone number in storage IN #319. GUI 210 displays deploy trigger icon 398 of deploy trigger 394 and displays caller I.D. information (acting as caller I.D. display 21). The incoming call causes telephone 27 to be rung. The user responds to the ringing telephone by viewing the displayed caller I.D. information. The user recognizes the calling telephone number and based on the recognized number decides to deploy sendings registered to that number by touching deploy trigger icon 398. GUI 210 (acting as trigger 394) responds by signaling obtainer 335 of provider 375. For this example, obtainer 335 is configured to respond to the signal by requesting registry 350 forward all sendings stored in storage 370 registered to the telephone number stored in other party address register 357 storage IN #319. Registry 350 responds by forwarding said sending or sendings to dispatcher 336 (for this example the audio sending and image sending supplied by said other party and received, inventoried and stored). Dispatcher 336 dispatches said sending or sendings to deliverer 360. Deliverer 360 delivers said sending or sendings.
For this second example of operation, dispatcher 336 employs audio player 338. Audio player 338 plays the audio sending and dispatches an audio feed of the playing audio sending to speaker 362 of deliverer 360. In one configuration, speaker 362 comprises a broadcasting type speaker and the audio is broadcast therefrom. The user listens to the ring-tone from provider 121 indicating the unanswered incoming telephone and, at the same time, listens to the playing audio sending out of the broadcasting type speaker. In another configuration, dispatcher 338 dispatches the audio feed to ring-tone delivery 434. Ring-tone delivery 434 delivers the playing audio to the user via the receiver of telephone 27ff indicating that the other party's telephone is being rung. (In another configuration, player 338 dispatches to both speaker 362 and delivery 434.)
For this second example of operation, dispatcher 336 further employs audio player 338. Audio player 338 plays the audio sending and dispatches an audio feed of the playing audio sending to ring-back delivery 391. Delivery 391 includes answering circuitry. The answering circuitry responds to the signal from GUI 210 (touched icon 398) by answering the incoming call and delivering the playing audio to the caller. In other words, provider 121 provides a ring-back to the caller until the user touches icon 398. Subsequently provider 121 discontinues the ring-back when delivery 391 answers the call and delivery 391 then provides the audio sending as the ring-back.
For this second example of operation, dispatcher 336 also employs image feed 343. Image feed 343 dispatches a feed of the read image sending (read by registry 350) to image display 367 of deliverer 360. For this example, the display of GUI 210 acts as image display 367. While the user's telephone is being rung indicating the unanswered incoming call, the image sending is displayed on image display 367. The user views the image, the image helping the user decide if he really cares to converse with this caller. Upon the user answering the call, feed 343 can continue or discontinue display of the image.
For this second example of operation, dispatcher 336 also employs file dispatcher 347. Dispatcher 347 dispatches the file containing the image sending (copied and forwarded from registry 350) to service provider delivery 369 of deliverer 360. Delivery 369 delivers the image sending file to service provider 121 along with the other party's telephone number from storage IN #319. Provider 121 delivers the sending to the other party's telephone. The other party's telephone can display the image for the other party to view while they wait for the user to answer and after the user answers etc.
A brief description of operation of additional examples of said many many thousands of unique ways to respond to deploy trigger 394 will now be given. System 10ff additional Inventor Favorites:
Example 2EX3: Upon an-other party answering a call, the user deploys audio, text message, image and video sendings to the other party's telephone.
Example 2EX4: Upon an-other party not answering a call, the user deploys a text message to the other party's telephone.
Example 2EX5: Upon an-other party saying something kind to the user, the user deploys a text message valentine and an image of a heart.
This second embodiment can include a sendings picker 385. Sendings picker 385 functions to enable a user to pick a sending from a plurality of sendings to pick from. An exemplary sendings picker 385 is depicted in
In another configuration, registry 350 can forward to GUI 210 other than registration numbers of sendings registered to the obtained telephone number, for example registration numbers of all sendings found or of all sendings of a particular type or of all sending of a particular class or, for example, a particular group of user-selected sendings or of other. GUI 210 can display an icon representing each sending and can store the forwarded registration numbers.
An icon representing a sending can comprise the time and/or date and/or year received (registered to a sending by time register 371); the sending type (registered to a sending by type register 372); the sending class (registered to a sending by class register 326); or other. (As examples, an icon representing an audio message sending can be a music note with the date the sending was received included below the note, an icon representing a text message sending can be the date the sending was received written in an antique font, an icon representing an image sending can be a miniature of the actual image stored with the date the sending was received included below the image and an icon representing a video can be a miniature of a frame taken from the actual video with the date the sending was received included below the frame.)
GUI 210 can be configured to respond to a touched one of the plurality of icons in array 352 by signaling linked trigger 393 and by forwarding to trigger 393 the registration number of the sending represented by the touched icon. Trigger 393 can then wait for a signal indicating an activity and upon receipt of said signal can forward to provider 375 the registration number and instruct provider 375 to obtain and dispatch the sending. Provider 375 can respond by obtaining and dispatching the sending to deliverer 360.
GUI 210 can be configured to respond to a touched one of the plurality of icons in array 352 by triggering the providing of a sending (thus functioning as deploy trigger 394). GUI 210 can respond to a touched icon by forwarding the registration number of the sending represented by the touched icon to provider 375 and by instructing provider 375 to obtain and dispatch the sending. Provider 375 can respond by obtaining and dispatching the sending to deliverer 360.
(GUI 210 can be configured to respond to a touched icon by signaling linked trigger 393 only, can be configured to respond to a touched icon by functioning as deployed trigger 394 only or can be configured to respond to a touched icon by both signaling trigger 393 and functioning as trigger 394. When said configured to respond by both, GUI 210 can be configured to respond by both during a telephone call or to respond to one or the other during a telephone call depending, for example, on user instruction. GUI 210 can be programmed to enable a user to implement said instruction.)
As can be appreciated from the above disclosure, GUI 210 (acting as picker 385) can display numerous pluralities of sendings for the user to pick from. As examples of said pluralities of sendings, GUI 210 can be configured to display: one received class sending of each sending type to pick from (sending types, for example, audio message, audio content, text message, image/picture, video (with audio) or other; said one of each type, for example, chosen randomly from all received class sendings registered to that sending type); a plurality of random received class sendings to pick from (said random sendings selected randomly from all received class sendings stored; a plurality of received class sendings to pick from, said plurality selected prior by the user comprising, for example, user favorites; a plurality of user-selected class sendings to pick from, said plurality selected prior by the user comprising, for example, user favorites; all sendings registered to a telephone number stored by other party address register 357; one sending of each sending type registered to a telephone number stored by address register 357; a plurality of randomly selected sendings registered to a telephone number stored by address register 357; all of a given type of sendings registered to a telephone number stored by address register 357; all sendings registered to a telephone number provided by a sendings call-up 396 described later; one sending of each sending type registered to a telephone number provided by call-up 396; a plurality of randomly selected sendings registered to a telephone number provided by call-up 396; all of a given type of sendings registered to a telephone number provided by call-up 396; three pluralities of sendings, one plurality received class sendings, one plurality identified class sendings and one plurality user-selected class sendings; all sendings registered during a specified period of time. (For any of the examples given herein this application comprising a video sending, said video sending can include audio.)
Sendings picker 385 can include a sendings type picker 354. Sendings type picker 354 functions to enable a user to pick a sending type from a plurality of sending types to pick from. An exemplary sendings type picker 354 is depicted in
As an example of operation, to operate as picker 354, GUI 210 can display one icon for each of a plurality of sending types. Upon the user touching one of the representative icons, GUI 210 can instruct registry 350 forward inventory information regarding the sending type to GUI 210. As an example, the user touches an icon representing image type sendings. GUI 210 responds by requesting registry 350 forward the registration numbers of all image type sendings found in inventory 324. Registry 350 responds by forwarding said registration numbers to GUI 210. GUI 210 displays an icon to represent each image type sending found (the icon can comprise the date received). The user can then pick one of the image sendings by touching the representative icon. GUI 210 responds by providing the registration number of the picked sending to obtainer 335 and by instructing obtainer 335 to obtain the sending. Obtainer 335 responds by requesting registry 350 forward the sending associated with the provided registration number to dispatcher 336. Dispatcher 336 can then dispatch the sending to deliverer 360. Deliverer 360 can then deliver the sending.
Sendings picker 385 can include a sendings class picker 406. Sendings class picker 406 functions to enable a user to pick a sendings class from a plurality of sendings classes to pick from. An exemplary sendings class picker 406 is depicted in
A third example of this second embodiment is illustrated as system 10gg in
For this third example, sendings receiver 340 includes at least one of telephone receiver 344, email receiver 351 and internet receiver 409. Sendings registry 350 includes automatic register 401. Sendings provider 375 includes sendings obtainer 335 and sendings dispatcher 336. Sendings picker 385 employs GUI 210. Deliverer 360 includes one or more of: speaker 362; display 361; text message display 366; image display 367; video display 368; email delivery 363; internet delivery 374; service provider delivery 369; delivery port 364; ring-back delivery 391; ring-back forward delivery 433; and ring-tone delivery 434. Delivery trigger 390 includes at least one of linked trigger 393 and user-deploy trigger 394. Telephone 27gg comprises mobile phone 165.
(Registry 350 can include user-selected default 410. Obtainer 335 can include prioritizer 341. Dispatcher 336 can include arranger 337. Arranger 337 can include one or more of: gallery 342; sequencer 348; and repeater 392. Sendings identifier 345 can include one or more of: universal identifier 349; special address identifier 437; manual identifier 403; requested sendings identifier 355; and auto-requester 365. Configurator 395 can include one or more of: a configuration selector 389; an enabler 373; and a data entry 407. System 10gg can include telephone 27gg and, thus, can include phone 165. System 10gg can include caller I.D. circuitry 20. Circuitry 20 can include GUI 210 to serve as display 21 to display caller I.D. information to the user.)
For this third example, sendings receiver 340 can be electrically connected to (or connectable to) sendings registry 350. Sendings registry 350 can be electrically connected to (or connectable to) storage 370. Sendings provider 375 can be electrically connected to (or connectable to) sendings registry 350 and can be electrically connected to (or connectable to) deliverer 360. Linked trigger 393 can be electrically connected to (or connectable to) provider 375. GUI 210, operating as user-deploy trigger 394, can be electrically connected to (or connectable to) provider 375. To operate as picker 385, GUI 210 can be electrically connected to (or connectable to) registry 350, can be electrically connected to (or connectable to) delivery trigger 390 (linked trigger 393) and can be electrically connected to (or connectable to) sendings provider 375. For this third example, sendings obtained by provider 375 can be sendings received and inventoried as described prior in “ONE EXAMPLE OF OPERATION of receiving and inventorying sendings”.
For this third example, sendings picker 385 employs GUI 210. To operate as picker 385, GUI 210 GUI 210 is configured to be capable of being placed in electronic communication with circuitry and/or programming to enable a user to pick a sending from a plurality of sendings to pick from. GUI 210 provides sendings icon array 352. Upon the user completing the dialing of a telephone number, address register 357 can obtain the dialed telephone number. Upon receipt of an incoming telephone call, address register 357 can obtain the telephone number of the calling telephone from caller I.D. information. Upon obtaining a telephone number, register 357 provides the number to registry 350 and registry 350 responds by forwarding to GUI 210 the registration number of each sending registered to that number found in inventory 324. GUI 210 displays an icon representing each sending and stores the registration number forwarded from registry 350. For this example, the icon comprises the date received (from time register 371) and comprises the sending type (from type register 372).
For this example, GUI 210 can respond to the user touching one of the plurality of icons by signaling (triggering) linked trigger 393 and by forwarding to trigger 393 the registration number of the picked sending. Trigger 393 then waits for a signal indicating an activity and upon receipt of said signal forwards to provider 375 the registration number and instructs provider 375 to obtain and dispatch the sending. Provider 375 responds by obtaining and dispatching the sending to deliverer 360.
For this example, GUI 210 can respond to the user touching one of the plurality of icons by initiating the providing of a sending (thus functioning as deploy trigger 394). GUI 210 can respond to the user touching one of the plurality of icons by forwarding the registration number of the picked sending to provider 375 and by instructing provider 375 to obtain and dispatch the sending. Provider 375 responds by obtaining and dispatching the sending to deliverer 360.
For this example, sendings picker 385 can include type picker 354. Picker 354 employs GUI 210. To operate as picker 354, GUI 210 is configured to be capable of being placed in electronic communication with circuitry and/or programming to enable a user to pick a sending type from a plurality of sending types to pick from. GUI 210 is configured to display an icon to represent each of the following sending types: audio message type, audio content type, text message type, image type, video type. Upon the user picking a sending type, GUI 210 then acts as picker 385 by providing the user with a choice of sendings registered to that type to pick from.
A first example of operation of this third example of the second embodiment (system 10gg) will now be given (3EX1). This first example comprises system 10ee and further configured to include sendings picker 385. (In other words, this first example comprises linked trigger 393.) For this example, to operate as sendings picker 385 GUI 210 is configured to display all received class sendings found in inventory 324 registered to a telephone number obtained by other party address register 357.
Upon the user completing the dialing of a telephone number or upon receipt of an incoming telephone call, other party address register 357 obtains the dialed telephone number or the calling telephone's number from caller I.D. information, respectively. Register 357 provides the obtained number to registry 350 and registry 350 responds by forwarding the registration number to GUI 210 of each sending found in inventory 324 registered to that telephone number. GUI 210 then displays icon array 352, array 352 comprising one icon representing each forwarded registration number. Each icon comprises the sending's date received and a representation of the sending's type. For this example, the call is answered (either by called party or by user). While conversing, the user decides to touch one of the displayed icons, as an example, an icon comprising the date Nov. 20, 2011 and a miniature of a picture (the miniature being a reduction of the actual image stored). GUI 210 responds to the user touching the date and image icon by forwarding to trigger 393 the registration number of the picked sending. Trigger 393 waits for a signal indicating an activity, as an example for this example, a hang up by the user or by the caller. Upon receiving said signal, trigger 393 forwards to provider 375 the forwarded registration number and instructs provider 375 obtain and dispatch the associated sending. Provider 375 responds by obtaining and dispatching the image sending to deliverer 360. (As an example for this example, provider 375 dispatches the image to delivery 369 and to image display 367. Delivery 369 delivers the image to the other party's telephone via provider 121, display 367 delivers the image to the user.)
A second example of operation of this third example of the second embodiment (system 10gg) will now be given (3EX2). This second example comprises system 10ff and further configured to include sendings picker 385. (In other words, this second example comprises user-deploy trigger 394.) For this example, to operate as sendings picker 385 GUI 210 is configured to display all received class sendings found in inventory 324 registered to a telephone number obtained by other party address register 357. For this example, system 10gg includes caller I.D. circuitry 20.
Upon the user completing the dialing of a telephone number or upon receipt of an incoming telephone call, other party address register 357 obtains the dialed telephone number or the calling telephone's number from caller I.D. information, respectively. Register 357 provides the obtained number to registry 350 and registry 350 responds by forwarding the registration number to GUI 210 of each sending found in inventory 324 registered to that telephone number. GUI 210 then displays icon array 352, array 352 comprising one icon representing each forwarded registration number. Each icon comprises the date received and a representation of the sending type. For this example, the telephone call is unanswered and incoming to the user. The user views caller I.D. information displayed on GUI 210 and from the information touches two icons displayed on GUI 210, an audio icon and a text message icon. GUI 210 responds to the user touching the two icons by initiating the providing of the associated two sendings (thus GUI 210 functions as deploy trigger 394). GUI 210 initiates the providing by forwarding the registration number of each of the two picked sendings to provider 375 and by instructing provider 375 to obtain and dispatch each of the sendings. Provider 375 responds by obtaining and dispatching the sendings represented by the touched icons. (As an example for this example, provider 375 dispatches the audio sending to ring-back delivery 391 and the text message sending to provider delivery 369. Delivery 391 delivers the audio sending to the other party as the ring-back. Delivery 369 delivers the image sending to the other party's telephone via provider 121.)
A third example of operation of this third example of the second embodiment (system 10gg) will now be given (3EX3). This third example comprises a combining of system 10ee and system 10ff and further configured to include sendings picker 385. Picker 385 is further configured to include sendings type picker 354. Picker 385 is further configured to include sendings class picker 406. The user touching an icon in icon array 352 functions as deploy trigger 394 to initiate provider 375. The user touching and holding for two seconds or more an icon in icon array 352 functions to signal linked trigger 393. Trigger 393 waits for a signal indicating an activity and responds by initiating provider 375. For this example, system 10gg includes caller I.D. circuitry 20.
Upon the user completing the dialing of a telephone number or upon receipt of an incoming telephone call, other party address register 357 obtains the dialed telephone number or the calling telephone's number from caller I.D. information, respectively. Register 357 provides the obtained number to registry 350 and registry 350 responds by forwarding the registration number of each sending found in inventory 324 registered to that number to GUI 210. GUI 210 determines from the forwarded registration numbers what types of sendings have been registered. For this example, GUI 210 acting as sendings type picker 354, determines that four types have been registered and, so, GUI 210 displays four icons, one icon represent each of the types found registered to the number obtained by register 357. GUI 210 displays a music note representing audio type, displays the word TEXT written in an antique font representing text message type, displays a miniature picture representing image type and displays a drawing depicting a video camera representing video type.
For this example, the telephone call is unanswered and incoming to the user. The user views caller I.D. information displayed on GUI 210 and from the information touches the TEXT icon. GUI 210 responds to the touched TEXT icon by determining from the registration numbers all text message sendings found in inventory 324 registered to the number obtained by register 357. For this example for example, GUI 210 determines that three text message sendings have been registered to the number. GUI 210 provides icon array 352 and displays three icons, one icon representing each of the three text message sendings (each icon comprising the date that sending was received written in an antique font). For this example, the user touches one of the icons. GUI 210 responds to the touched icon by functioning as deploy trigger 394 and, thus, by initiating provider 375. Provider 375 obtains and dispatches the text message sending (for example dispatches to text message display 366).
GUI 210, again acting as sendings type picker 354, displays the four type icons, one icon representing each of the determined four types of sendings registered to the other party's telephone number. For this example, the user then answers the incoming call. While conversing, the user touches the music note representing audio type. GUI 210 responds to the touched audio type icon by determining from the registration numbers all audio sendings found in inventory 324 registered to the number obtained by register 357. For this example for example, GUI 210 determines that five audio sendings have been registered to the number. GUI 210 provides icon array 352 and displays five icons, one icon representing each of the five audio sendings (each icon comprising a song title with the date that sending was received included below the song title). For this example, the user touches one of the audio icons for more than two seconds. GUI 210 responds to the touched for duration icon by forwarding to trigger 393 the registration number of the picked audio sending. Trigger 393 waits for a signal indicating an activity, for this example, the next received incoming call from the number obtained by register 357. Responsive to said next call from the other party's telephone, a signal indicating this activity is sent to trigger 393. Trigger 393 responds to the signal by forwarding to provider 375 the registration number of the picked audio sending and by instructing provider 375 obtain and dispatch the sending. Provider 375 responds by obtaining and dispatching the audio sending to deliverer 360. (As an example for this example, provider 375 employs audio player 338 to play the sending and to dispatch the playing audio to ring-back delivery 391. Delivery 391 delivers the playing audio sending to the other party as the ring-back.
A fourth example of operation of this third example of the second embodiment (system 10gg) will now be given (3EX4). This fourth example comprises system 10kk and further configured to include sendings picker 385. (In other words, this first example comprises user-selected sendings supplier 380.) For this example, to operate as sendings picker 385 GUI 210 is configured to display an array of icons representing the last ten received class image sendings registered and an array of icons representing the last ten user-selected class image sendings registered. System 10kk is configured to respond to a touched icon in either of the two arrays by displaying the represented image on the display of GUI 210.
Any time day or night whether on the phone or not, GUI 210 provides an icon representing sendings on an opening display. Any time day or night whether on the phone or not the user can touch the icon and GUI 210 responds to the touched icon by displaying the array of icons representing the last ten received class image sendings registered along with the array of icons representing the last ten user-selected class sendings registered. Upon the user touching the icon, GUI 210 responds by displaying the represented image on the display of GUI 210. (Deliverer picker 377, described below, can be employed. Subsequent to picking a sending, the user picks a deliverer, for example email delivery 363. Delivery addresser 379 can also be employed. The user supplies an address. The picked image is dispatched to delivery 363. Delivery 363 delivers the image sending to the internet for delivery to the supplied address. Also, it will be appreciated in the above examples, and in following examples, that statements along the lines of “GUI 210 responds”, “GUI 210 provides”, or other action verbs associated with the GUI 210, that this is intended to mean that the GUI 210 interacts with circuitry and/or programming in order for the indicated action (or actions) to be performed, and which may include: (i) displaying results via the GUI; (ii) receiving user inputs via the GUI; and (iii) prompting user inputs via the GUI.)
This second embodiment can include a deliverer picker 377. Deliverer picker 377 functions to enable a user to pick a deliverer. An exemplary deliverer picker 377 is depicted in
To operate as deliverer picker 377, GUI 210 can include programming to receive and to respond to instruction from the user via the user touching an icon, said touched icon, for example, one of the plurality of icons in deliverer icon array 376. GUI 210 can respond to a user touched icon in array 376 by signaling provider 375. Provider 375 can respond by instructing dispatcher 336 dispatch a sending to the deliverer picked by the user. If the user touches a deliverer icon that is not available for the sending type being provided, as an example GUI 210 can blink the icon indicating to the user to pick a different deliverer. Said plurality of deliverers to pick from can include two or more of: speaker 362, display 361, GUI 210 providing the functionality of display 361, text message display 366, image display 367, video display 368, email delivery 363, internet delivery 374, service provider delivery 369, delivery port 364 and ring-back delivery 391. (As examples of icon representation: speaker 362 can be a depiction of a speaker, display 361 can be a depiction of a display, text message display 366 can be a depiction of text on a display, image display 367 can be a depiction of an image on a display, video display 367 can be a depiction of a video camera on a display, email delivery 363 can be the word EMAIL, internet delivery 374 can be then word NET, service provider delivery 369 can be a depiction of a telephone, delivery port 364 can be the word PORT, ring-back delivery 391 can be a depiction of bells.)
A fourth example of this second embodiment is illustrated as system 10hh in
For this fourth example, sendings receiver 340 includes at least one of telephone receiver 344, email receiver 351 and internet receiver 409. Sendings registry 350 includes automatic register 401. Sendings provider 375 includes sendings obtainer 335 and sendings dispatcher 336. Deliverer 360 includes one or more of: speaker 362; display 361; text message display 366; image display 367; video display 368; email delivery 363; internet delivery 374; service provider delivery 369; delivery port 364; ring-back delivery 391; ring-back forward delivery 433; and ring-tone delivery 434. Delivery trigger 390 includes at least one of linked trigger 393 and user-deploy trigger 394. Telephone 27hh comprises mobile phone 165.
(Registry 350 can include user-selected default 410. Obtainer 335 can include prioritizer 341. Dispatcher 336 can include arranger 337. Arranger 337 can include one or more of: gallery 342; sequencer 348; and repeater 392. Sendings identifier 345 can include one or more of: universal identifier 349; special address identifier 437; manual identifier 403; requested sendings identifier 355; and auto-requester 365. Configurator 395 can include one or more of: a configuration selector 389; an enabler 373; and a data entry 407. System 10hh can include telephone 27hh and, thus, can phone 165. System 10hh can include caller I.D. circuitry 20. Circuitry 20 can include GUI 210 to serve as display 21.)
For this fourth example, sendings receiver 340 can be electrically connected to (or connectable to) sendings registry 350. Sendings registry 350 can be electrically connected to (or connectable to) storage 370. Sendings provider 375 can be electrically connected to (or connectable to) sendings registry 350 and can be electrically connected to (or connectable to) deliverer 360. Linked trigger 393 can be electrically connected to (or connectable to) provider 375. GUI 210, operating as user-deploy trigger 394, can be electrically connected to (or connectable to) provider 375. To operate as deliverer picker 377, GUI 210 can be electrically connected to (or connectable to) sendings provider 375, can be electrically connected to (or connectable to) registry 350 and can be electrically connected to (or connectable to) trigger 390.
For this fourth example, deliverer picker 377 includes GUI 210. To operate as picker 377, GUI 210 GUI 210 is configured to be capable of being placed in electronic communication with circuitry and/or programming to enable a user to pick a deliverer. GUI 210 is configured to display a deliverer icon array 376. Array 376 includes a plurality of icons, each icon representative of a deliverer. To operate as deliverer picker 377, GUI 210 includes programming to receive and to respond to instruction from the user via the user touching an icon, said touched icon, for example, one of the plurality of icons in deliverer icon array 376. GUI 210 responds to said user touching an icon in array 376 by signaling provider 375. Provider 375 responds by instructing dispatcher 336 dispatch a sending to the deliverer picked by the user and represented by the touched icon.
A first example of operation of this fourth example of the second embodiment (system 10hh) will now be given (4EX1). This first example comprises system 10ee and further configured to include deliverer picker 377. (In other words, this first example comprises linked trigger 393.) For this example, to operate as deliverer picker 377, GUI 210 is configured to display icon array 376 with array 376 comprising the following icons: a depiction of a speaker representing speaker 362, a depiction of text on a display represents text message display 366, a depiction of an image on a display represents image display 367, a depiction of a video camera represents video display 367, the word EDEL represents email delivery 363, the word NET represents internet delivery 374, a depiction of a telephone represents service provider delivery 369, the word PORT represents external port 364 and a depiction of bells represents ring-back delivery 391. For this example, provider 375 is configured to obtain and dispatch the last registered text message sending found in inventory 324 registered to a telephone number obtained by address registry 357 and the last registered image sending found in inventory 324 and registered to the telephone number obtained by address registry 357. (Said last registered text message and image sendings obtained by obtainer 335 employing prioritizer 341. Also, provider 375 can be configured to obtain and dispatch a default user-selected text message or a default user-selected image if a text message sending or an image sending, respectively, is not found in inventory 324 registered to said telephone number. User-selected default 410, described later, can be employed to supply said user-selected default text message and/or said user-selected image message.)
A text message sending and an image sending supplied by an-other party have been received, registered, inventoried and stored (and any other sendings said other party may have supplied). Some time later, the user places a call to said other party by dialing the telephone number of said other party's telephone. Other party address register 357 obtains and stores the dialed telephone number. The completion of the dialing is detected. Said detection instructs GUI 210 to display icon array 376.
The other party answers the call and while the two parties converse the user touches the icon depicting text on a display representing text display 366. GUI 210 responds to the touched icon by determining to instruct that the last registered text message sending (registered to the number obtained by register 357) be dispatched to text message display 366. GUI 210 forwards said instruction to linked trigger 393. Later in the conversation, the user touches the icon depicting a telephone representing service provider delivery 369. GUI 210 responds to the touched icon by determining that either of the last registered text message sending or the last registered image sending (registered to the number obtained by register 357) can be delivered by service provider delivery 369. Consequently, GUI 210 displays an icon representing text message sending and an icon representing image sending. The user understands to touch one or the other to instruct GUI 210 that the sending represented by that touched icon is to be dispatched to delivery 369. For this example, the user touches the icon representing image sending. GUI 210 responds to the touched icon by forwarding to linked trigger 393 instruction that the last registered image sending is to be dispatched to delivery 369. Subsequently, user or other party hang up. The hang up (activity) is detected and signaled to linked trigger 393. Trigger 393 responds by instructing provider 375 to obtain and dispatch to display 366 the last registered text message sending registered to the number obtained by register 357. Trigger 393 further responds by instructing provider 375 to obtain and dispatch to delivery 369 the last registered image sending registered to the number obtained by register 357. Provider 375 obtains the text message sending and employs text message feed 339 to dispatch the sending to text message display 366 for the user to view. Provider 375 obtains the image sending and employs file dispatcher 347 to dispatch the sending to service provider delivery 369 for receipt at the other party's telephone via provider 121.
A second example of operation of this fourth example of the second embodiment (system 10hh) will now be given (4EX2). This second example comprises system 10ff and further configured to include deliverer picker 377. (In other words, this second example comprises deploy trigger 394.) For this example, to operate as deliverer picker 377, GUI 210 is configured to display icon array 376. For this example, provider 375 is configured to obtain and dispatch a gallery comprising all text message sendings registered to a telephone number obtained by address register 357 and the last registered (received) video sending registered to the telephone number obtained by address register 357 (said gallery arranged by gallery arranger 342 and said last registered obtained employing prioritizer 341). (Provider 375 can be configured to obtain and dispatch a default user-selected text message sending or default user-selected image sending if a text message sending or an image sending, respectively, is not found in inventory 324 registered to said telephone number obtained by register 357. User-selected default 410, described later, can be employed to supply said default text message and/or said image message.)
Audio sendings, text message sendings, image sendings and video sendings supplied by an-other party have been received, registered, inventoried and stored. Some time later, the user places a call to said other party by dialing the telephone number of said other party's telephone. Other party address register 357 obtains and stores the dialed telephone number. The completion of the dialing is detected. Said detection instructs GUI 210 to display icon array 376. For this example, array 376 includes an icon depicting a speaker representing speaker 362, an icon depicting text on a display representing text display 366, an icon depicting an image on a display representing image display 367, an icon depicting a video camera representing video display 368, an icon comprising the word EDEL representing email delivery 363, an icon comprising the word NET representing internet delivery 374, an icon depicting a telephone representing service provider delivery 369, an icon comprising the word PORT representing external port 364 and an icon depicting bells representing ring-back delivery 391.
The other party answers the call and while the two parties converse the user touches the icon depicting a telephone representing service provider delivery 369. GUI 210 responds to the touched icon by determining that either of the text message gallery of sendings or the video sending can be delivered by service provider delivery 369. Consequently, GUI 210 displays an icon representing text message and an icon representing video sending. The user understands to touch one or the other to instruct GUI 210 that the sending represented by that touched icon is to be dispatched to delivery 369. For this example, the user touches the icon representing image sending. GUI 210 responds by operating as deploy trigger 394 and instructing provider 375 to dispatch to delivery 369 a gallery of text message sendings comprising all text message sendings found in inventory 324 registered to the number obtained by registry 357. Obtainer 335 requests the text message sendings from registry 350. Registry 350 forwards the sendings to gallery arranger 342. Arranger 342 arranges the text message sendings into a gallery image and forwards the image to file dispatcher 347. Dispatcher 347 dispatches the gallery image to service provider delivery 369 for receipt at the other party's telephone via provider 121.
Later in the conversation, the user touches the icon comprising the word PORT representing external port 364. GUI 210 responds to the touched icon by determining that either of the text message gallery of sendings or the video sending can be delivered by external port 364. Consequently, GUI 210 displays an icon representing text message and an icon representing video sending. The user understands to touch one or the other to instruct GUI 210 that the sending represented by that touched icon is to be dispatched to external port 364. For this example, the user touches the icon representing video sending. GUI 210 responds by operating as deploy trigger 394 and instructing provider 375 to dispatch to port 364 the last registered video sending found in inventory 324 registered to the number obtained by register 357. Obtainer 335 (of provider 375) employs prioritizer 341 to obtain said last registered video sending from registry 350. Registry 350 forwards a read of the video sending to video player 346. Player 346 plays the forwarded read and dispatches a video feed of the playing video sending to port 364. The user has previously connected a TV to port 364. The playing video is displayed on the TV for the user to view. Subsequently, user or the other party hang up. Responsive to the hang up, system 10hh can be configured to continue or discontinue the video feed of the playing video sending dispatched to port 364.
A third example of operation of this fourth example of the second embodiment (system 10hh) will now be given (4EX3). This fourth example comprises system 10gg and further configured to include deliverer picker 376. (In other words, this third example comprises sendings picker 385.) The user touching an icon in icon array 352 (of sendings picker 385) functions as deploy trigger 394 to initiate provider 375. The user touching and holding for two seconds or more an icon in icon array 352 functions to signal linked trigger 393. For this example, picker 385 is further configured to include sendings type picker 354. For this example, to operate as deliverer picker 377, GUI 210 is configured to display icon array 376. For this example, system 10hh includes caller I.D. circuitry 20.
Sendings supplied by an-other party have been received, registered, inventoried and stored. Some time later, upon the user completing the dialing of a telephone number or upon receipt of an incoming telephone call, other party address register 357 obtains the dialed telephone number or the calling telephone's number from caller I.D. information, respectively. Upon obtaining the telephone number, register 357 provides the number to registry 350 and registry 350 responds by forwarding the registration number of each sending found in inventory 324 registered to that number to GUI 210. GUI 210, acting as type picker 354, determines from the forwarded registration numbers the types of sendings that have been registered to said telephone number. For this example, GUI 210 determines that four types have been registered and, so, GUI 210 displays four icons. One icon represents each type found in inventory 324 registered to the number obtained by register 357. GUI 210 displays a music note representing audio type, displays the word TEXT written in an antique font representing text message type, displays a miniature picture representing image type and displays a drawing depicting a video camera representing video type.
For this example, the telephone call is unanswered and incoming to the user. The user views caller I.D. information displayed on GUI 210 and from the information touches the TEXT icon. GUI 210 responds to the touched TEXT icon by determining from the registration numbers all text message sendings registered to the number obtained by register 357. For this example for example, GUI 210 determines that three text message sendings have been registered. GUI 210 provides icon array 352 and displays three icons, one icon representing each of the three text message sendings (each icon comprising the date that sending was received written in an antique font). GUI 210 also provides icon array 376. For this example, array 376 displays icons representing deliverers that can be employed for delivering a text message. Array 376 displays an icon depicting text on a display representing text display 366, an icon comprising the word EDEL representing email delivery 363, an icon comprising the word NET representing internet delivery 374, an icon depicting a telephone representing service provider delivery 369 and an icon comprising the word PORT representing external port delivery 364.
The user touches one of the icons from array 352 followed by one of the icons from array 376 (or can touch an icon from array 376 followed by an icon from array 352). GUI 210 responds to the touched icons by functioning as deploy trigger 394 to initiate provider 375 and by instructing provider 375 to dispatch the sending to the deliverer represented by the touched icon. Provider 375 obtains and dispatches the text message sending to the represented deliverer. As an example for this example, the user touches the word EDEL and subsequently touches one of the three icons representing the text messages. GUI 210 responds by initiating provider 375 obtain and dispatch the text message sending represented by the touched icon and by instructing provider 375 to employ file dispatcher 347 to dispatch the text message sending to email delivery 363. (In one configuration, email delivery 363 can deliver the sending inclusive of a pre-supplied email address for receipt at an email account. In another configuration, the prior-described email delivery addresser 379 can be employed. As an example, upon the user touching the EDEL icon, GUI 210 can provide a keypad and enable the user to supply an email address. GUI 210 can forward the entered address to email delivery 363. Delivery 363 can deliver the sending inclusive of the user-entered email address for receipt at an email account.)
GUI 210 again acting as type picker 354 displays the four type icons (one icon representing each of the determined four types of sendings registered). For this example, the user then answers the incoming call. While conversing, the user touches the miniature picture representing image type. GUI 210 responds to the touched image type icon by determining from the registration numbers all image sendings registered to the number obtained by register 357. For this example, GUI 210 determines that four image sendings have been registered. GUI 210 provides icon array 352 and displays four icons, one icon representing each of the four image sendings (each icon comprising a miniature of the picture stored with the date that sending was received included below the miniature). GUI 210 also provides icon array 376. For this example, array 376 displays icons representing deliverers that can be employed for delivering an image sending. Array 376 displays an icon depicting an image on a display representing image display 367, an icon comprising the word EDEL representing email delivery 363, an icon comprising the word NET representing internet delivery 374, an icon depicting a telephone representing service provider delivery 369 and an icon comprising the word PORT representing external port 364.
The user touches the icon depicting an image on a display (image display 367), the icon comprising the word NET (internet delivery 374), the icon depicting a telephone (service provider delivery 369) and one of the four image representing icons. GUI 210 responds to the touched one of the four image representing icons by functioning as deploy trigger 394 to initiate provider 375. GUI 210 responds to the touched image on a display icon, the touched word NET icon and the icon depicting a telephone by instructing provider 375 to dispatch the sending to image display 367, internet delivery 374 and service provider delivery 369, respectively. Obtainer 335 of provider 375 requests registry 350 forward the sending to dispatcher 336. Dispatcher 336 employs image feed 343 to dispatch the image sending to image display 367 and employs file dispatcher 347 to dispatch the image sending to internet deliver 374 and to service provider delivery 369. (In one configuration, internet delivery 374 can deliver the sending inclusive of a pre-supplied internet address for receipt at an Internet website. In another configuration, the prior-described internet delivery addresser 381 can be employed. As one example, upon the user touching the NET icon, GUI 210 can provide the user with a keypad enabling the user to enter an internet address. GUI 210 can forward the entered address to internet delivery 374. Delivery 374 can deliver the sending inclusive of the user-entered address for receipt at an internet website. In one configuration, service provider delivery 369 can employ the telephone number obtained by address register 357 and can deliver the image sending along with the telephone number to telephone service provider 121. Provider 121 can deliver the sending to the telephone having that telephone number. In another configuration, the prior-described provider delivery addresser 386 can be employed. As an example, upon the user touching the icon depicting a telephone, GUI 210 can provide a keypad and enable the user to supply a telephone number. GUI 210 can forward the entered telephone number to service provider delivery 369. Delivery 369 can deliver the sending inclusive of the user-entered address for receipt at the entered address.)
GUI 210 once again acting as type picker 354 displays the four type icons, one icon representing each of the determined four types of sendings registered. While further conversing, the user touches the music note representing audio type. GUI 210 responds to the touched audio type icon by determining from the registration numbers all audio sendings registered to the number obtained by register 357. For this example for example, GUI 210 determines that five audio sendings have been registered. GUI 210 provides icon array 352 and displays five icons, one icon representing each of the five audio sendings (each icon comprising a song title with the date that sending was received included below the song title). GUI 210 also provides icon array 376. For this example, array 376 displays icons representing deliverers that can be employed for delivering an audio sending. Array 376 displays an icon depicting a speaker representing speaker 362, an icon comprising the word EDEL representing email delivery 363, an icon comprising the word NET representing internet delivery 374, an icon depicting a telephone representing service provider delivery 369, an icon comprising the word PORT representing external port delivery 364 and an icon depicting bells representing ring-back delivery 391.
For this example, the user touches one of the audio icons for more than two seconds and touches the icon depicting bells representing ring-back delivery 391. GUI 210 responds to the user touching the icon for duration by signaling linked trigger 393 and by forwarding to trigger 393 the registration number of the picked audio sending and the instruction to dispatch the audio sending to ring-back delivery 391. Trigger 393 then waits for a signal indicating an activity, for this example, a user or other party hang up. For this example, the user hangs up. A signal indicating detection of the user hang up is sent to trigger 393. Trigger 393 responds to the signal by forwarding to provider 375 the registration number of the picked audio sending and by instructing provider 375 obtain and dispatch the sending to ring-back delivery 391. Provider 375 responds by obtaining the sending and by employing audio player 338 to dispatch the audio sending to delivery 391. Delivery 391 maintains an off-hook condition and delivers the playing audio sending to the other party until the other party hangs up. (They get to hear their favorite song clip! Also, as another example of operation of system 10hh, an opening menu on GUI 210 displays icons representing deliverers that can be employed with sendings. Upon the user touching one of said deliverer icon, GUI 210 displays, for example all sendings found in inventory 324 that can be delivered via the represented deliverer. Also, as another example of operation of system 10hh, picker 377 can comprise GUI 210 displaying only one icon, said one icon representing one deliverer and GUI 210 can respond to the user touching said one icon by signaling provider 375. Provider 375 can respond by signaling dispatcher 336 to dispatch a sending to that deliverer.)
This second embodiment can include a sendings call-up 396. Sendings call-up 396 functions to enable a user to call up a (one or more) sending. An exemplary sendings call-up 396 is depicted in
In a first example, operating as call-up 396, GUI 210 can be configured to respond to an entered telephone number by requesting obtainer 335 request registry 350 forward, for example, one or more sendings of one or more types (audio, register 388; text message, register 382; image, register 383; video, register 384 or other) of one or more classes (received, register 328; identified, register 322; non-identified, register 327; user-selected, register 387), said requested sendings registered to the entered telephone number. (As examples, GUI 210 can be configured to request: one sending, five sendings, one image sending, three video sendings, one received class audio sending, four identified class text message sendings, etc., said requested sendings registered to the entered telephone number.) Registry 350 can respond to the request by forwarding the requested sending or sendings to dispatcher 336. Dispatcher 336 can dispatch the sending or sendings to deliverer 360. Deliverer 360 can deliver the sending or sendings.
In a second example, operating as call-up 396 GUI 210 can be configured to respond to an entered telephone number by requesting registry 350 forward, for example, the registration number for each of one or more sendings of one or more types (audio, register 388; text message, register 382; image, register 383; video, register 384 or other) of one or more classes (received, register 328; identified, register 322; non-identified, register 327; user-selected, register 387), said requested sendings registered to the entered telephone number. (As examples, GUI 210 can be configured to request: one sending, ten sendings, one video sending, three audio sendings, one non-identified class audio sending, six user-selected class text message sendings, etc., said requested sendings registered to the entered telephone number.) Registry 350 can respond to the request by forwarding the requested registration numbers to, for example, GUI 210. GUI 210 can display an icon representing each registration number found enabling the user to pick one (or more) of the sendings (for example, operating as sendings picker 385). (GUI 210 can also operate as deliverer picker 377 enabling the user to pick a deliverer.) The user touching one (or more) of the icons can serve to pick the represented sending. GUI 210 can then forward the registration number of the picked sending to obtainer 335. Obtainer 335 can request registry 350 forward the sending to dispatcher 336. Registry 350 can forward the sending to dispatcher 336. Dispatcher 336 can then dispatch the sending to deliverer 360. Deliverer 360 can then deliver the sending.
Said one or more sendings (first example above) or said one or more sending registration numbers (second example above) can comprise, for example: the last sending registered to the entered number, all sendings registered to the entered number; a given number of sendings registered to the entered number; the last sending of a given type registered to the entered number, all of a given type of sendings registered to the entered number; a given number of a given type of sendings registered to the entered number or can be other.
A fifth example of this second embodiment is illustrated as system 10ii in
For this fifth example, sendings receiver 340 includes at least one of telephone receiver 344, email receiver 351 and internet receiver 409. Sendings registry 350 includes automatic register 401. Sendings provider 375 includes sendings obtainer 335 and sendings dispatcher 336 and can include other party address register 357. Deliverer 360 includes one or more of: speaker 362; display 361; text message display 366; image display 367; video display 368; email delivery 363; internet delivery 374; service provider delivery 369; delivery port 364; ring-back delivery 391; ring-back forward delivery 433; and ring-tone delivery 434. Delivery trigger 390 includes at least one of linked trigger 393 and user-deploy trigger 394. Telephone 27ii comprises mobile phone 165.
(System 10ii can include address register 357. Registry 350 can include user-selected default 410. Obtainer 335 can include prioritizer 341. Dispatcher 336 can include arranger 337. Arranger 337 can include one or more of: gallery 342; sequencer 348; and repeater 392. Identifier 345 can include one or more of: universal identifier 349; special address identifier 437; manual identifier 403; requested sendings identifier 355; and auto-requester 365. Configurator 395 can include one or more of: a configuration selector 389; an enabler 373; and a data entry 407. System 10ii can include telephone 27ii and, thus, can include phone 165. System 10ii can include the caller I.D. circuitry 20. Circuitry 20 can include GUI 210 to serve as display 21.)
For this fifth example, sendings receiver 340 can be electrically connected to (or connectable to) sendings registry 350. Sendings registry 350 can be electrically connected to (or connectable to) storage 370. Sendings provider 375 can be electrically connected to (or connectable to) sendings registry 350 and can be electrically connected to (or connectable to) deliverer 360. Linked trigger 393 can be electrically connected to (or connectable to) provider 375. GUI 210, operating as user-deploy trigger 394, can be electrically connected to (or connectable to) provider 375. To operate as call-up 396, GUI 210 can be electrically connected to (or connectable to) registry 350 and can be electrically connected to (or connectable to) sendings provider 375. For this fifth example, sendings obtained by provider 375 can be sendings received and inventoried as described prior in “ONE EXAMPLE OF OPERATION of receiving and inventorying sendings”.
For this fifth example, sendings call-up 396 includes GUI 210. To operate as call-up 396, GUI 210 GUI 210 is configured to be capable of being placed in electronic communication with circuitry and/or programming to enable a user to call-up one or more sendings registered to a telephone number. GUI 210 provides the user with a keypad to enable the user to enter a telephone number. The user employs the provided keypad to enter a telephone number.
In a first example, GUI 210 is configured to respond to an entered telephone number by requesting obtainer 335 request registry 350 forward one or more sendings of one or more types of one or more classes, said requested sendings registered to the entered telephone number. Registry 350 responds to the request by forwarding the requested sending or sendings to dispatcher 336. Dispatcher 336 dispatches the sending or sendings to deliverer 360. Deliverer 360 delivers the sending or sendings.
In a second example, GUI 210 is configured to respond to an entered telephone number by requesting registry 350 forward the registration number for each of one or more sendings of one or more types of one or more classes, said requested sendings registered to the entered telephone number. Registry 350 forwards said registration numbers found to GUI 210. GUI 210 displays an icon for each of said registration numbers found enabling the user to pick one (or more) of the sendings. The user touching one (or more) of the icons serves to pick the represented sending. GUI 210 forwards the registration number of the picked sending to obtainer 335 (of provider 336). Obtainer 335 requests registry 350 forward the sending to dispatcher 336. Registry 350 forwards the sending to dispatcher 336. Dispatcher 336 dispatches the sending to deliverer 360. Deliverer 360 delivers the sending.
A first example of operation of this fifth example of the second embodiment (system 10ii) will now be given (5EX1). This first example comprises system 10ee and further configured to include sendings call-up 396. (In other words, this first example comprises linked trigger 393.) For this first example, system 10ii includes address register 357. GUI 210 is configured to respond to an entered telephone number by requesting obtainer 335 request registry 350 forward all sendings found registered to the entered telephone number.
Sendings supplied by other parties have been received, registered, inventoried and stored. Some time later, the user places a call to an-other party or an-other party calls the user. Upon the placing of the call or receipt of the call, address register 357 obtains the telephone number of the other party's telephone and, operating as call-up 396, GUI 210 provides the user with a keypad enabling the user to enter a telephone number. The call is answered and while the user and other party converse the user employs the provided keypad and enters a telephone number. GUI 210 forwards the entered telephone number to linked trigger 393 along with the request that obtainer 335 request registry 350 forward all sendings found registered to the entered telephone number. Subsequently, user or other party hang up. A signal representing the detected hang up is sent to 350 forward all sendings found registered to the entered telephone number to obtainer 335. Obtainer 335 requests registry 350 forward said all sendings found registered to the entered telephone number. Registry 350 responds by forwarding the requested all sending found to dispatcher 336. Dispatcher 336 dispatches the sending or sendings to deliverer 360. Deliverer 360 delivers the sending or sendings. For this example for example, dispatcher 336 employs dispatcher 347 to dispatch said all sendings found to service provider delivery 369. Delivery 369 delivers said all sendings found to the number obtained by address register 357. In other words, said all sendings found registered to the entered telephone number are delivered to the other party's telephone via provider 121. (If system 10 does not include address register 357, GUI 210 can supply addresser 386 enabling the user to enter an-other party's telephone number.)
A second example of operation of this fifth example of the second embodiment (system 10ii) will now be given (5EX2). This second example comprises system 10ff and further configured to include sendings call-up 396. (In other words, this second example comprises deploy trigger 394. Trigger 394 employs GUI 210 to provide deploy trigger icon 398.) For this example, system 10ii can include address register 357. GUI 210 is configured to respond to an entered telephone number by requesting obtainer 335 request registry 350 forward all image sendings found registered to the entered telephone number.
Sendings supplied by other parties have been received, registered, inventoried and stored. Some time later, the user places a call to an-other party or an-other party calls the user. Upon the placing of the call or receipt of the call, operating as call-up 396, GUI 210 provides the user with a keypad enabling the user to enter a telephone number. The call is answered and while the user and other party converse the user employs the provided keypad and enters a telephone number. The user then touches deploy trigger icon 398. GUI 210 responds to the touched icon 398 by forwarding the entered telephone number to obtainer 335 and requests obtainer 335 request registry 350 forward all image sendings found registered to the entered telephone number. Obtainer 335 requests registry 350 forward said all image sendings found. Registry 350 responds to the request by forwarding the requested all image sending found to dispatcher 336. Dispatcher 336 dispatches the sending or sendings to deliverer 360. Deliverer 360 delivers the sending or sendings. For this example for example, dispatcher 336 employs gallery arranger 342 to arrange the images into a gallery and employs image feed 343 to dispatch the gallery of image sendings to image display 367. Dispatcher 336 also employs file dispatcher 347 to dispatch said all image sendings found to service provider delivery 369. Delivery 369 delivers said all sendings found (via provider 121). (If address register 357 is employed, delivery 369 addresses the sendings to the number obtained by register 357. If address register 357 is not employed, GUI 210 can supply delivery addresser 386 to enable the user to enter an-other party's telephone number.)
A third example of operation of this fifth example of the second embodiment (system 10ii) will now be given (5EX3). This third example comprises system 10gg and further configured to include sendings call-up 396. (In other words, this third example comprises sendings picker 385.) For this example, system 10ii can include address register 357. GUI 210 is configured to respond to an entered telephone number by requesting obtainer 335 request registry 350 forward the registration number for each audio, text message and image sending found registered to the entered telephone number.
Sendings supplied by other parties have been received, registered, inventoried and stored. Some time later, the user places a call to an-other party or an-other party calls the user. The call is answered and the user and other party converse. Upon the call being answered, operating as call-up 396 GUI 210 provides the user with a keypad to enable the user to enter a telephone number. During the conversation, the user employs the provided keypad and enters a telephone number. GUI 210 forwards the entered telephone number to registry 350 and requests registry 350 forward the registration number for each audio, text message and image sending found registered to the entered telephone number. Registry 350 responds by forwarding the registration number of each sending found in inventory 324 registered to the entered telephone number to GUI 210. GUI 210, acting as sendings picker 385, displays an icon for each of said registration number of each sending found enabling the user to pick one (or more) of the sendings. The user touching one (or more) of the icons serves to pick the represented sending (or sendings). GUI 210 forwards the registration number of the picked sending to obtainer 335. Obtainer 335 requests registry 350 forward the sending to dispatcher 336. Registry 350 forwards the sending to dispatcher 336. Dispatcher 336 dispatches the sending to deliverer 360. Deliverer 360 delivers the sending. For this example for example, the picked sending comprises an audio sending. Dispatcher 336 employs audio player 338 to play the audio sending and to dispatch the playing sending to speaker 362. For this example, speaker 362 comprises a broadcasting type speaker enabling the user to hear the playing audio sending and the other party to hear the sending in the background as they converse.
A fourth example of operation of this fifth example of the second embodiment (system 10ii) will now be given (5EX4). This fourth example comprises system 10gg and further configured to include sendings call-up 396. (In other words, this fourth example comprises sendings picker 385.) For this example, system 10ii includes caller I.D. circuitry 20 and includes address register 357. GUI 210 is configured to respond to an entered telephone number by requesting obtainer 335 request registry 350 forward the registration number for each of all sendings found registered to the entered telephone number.
Sendings supplied by other parties have been received, registered, inventoried and stored. Some time later, the user places a call to an-other party or an-other party calls the user. Upon the user completing the dialing of a telephone number or upon receipt of an incoming telephone call, other party address register 357 obtains the dialed telephone number or the calling telephone's number from caller I.D. information, respectively. Register 357 provides the number to registry 350 and, for this example, registry 350 responds by forwarding the registration number of each sending registered to that telephone number to GUI 210. GUI 210 then displays icon array 352, array 352 comprising one icon representing each forwarded registered sending. For this example, the telephone call is unanswered and incoming to the user and the user views caller I.D. information displayed on GUI 210. Based on the information the user decides to touch a text message icon displayed in array 352. GUI 210, functioning as deploy trigger 394, responds to the touched icon by initiating the providing of the text message sending. GUI 210 forwards the registration number of the text message sending to provider 375 and instructs provider 375 obtain and dispatch the sending. Provider 375 responds by obtaining and dispatching the sending to deliverer 360. (As an example for this example, provider 375 employs file dispatcher 347 and dispatches the text message sending file to provider delivery 369. Delivery 369 employs the telephone number obtained by register 357 and delivers the text message sending to the other party's telephone via provider 121. Provider 375 also employs text message feed 338 and employs text message feed 339 to dispatch the sending to message display 366.)
Subsequently, the call is answered. Operating as call-up 396, GUI 210 responds to said answered call by providing the user with a keypad enabling the user to enter a telephone number (in addition to continuing to display icon array 352). During the ensuing conversation the user employs the provided keypad and enters a telephone number. GUI 210 forwards the entered telephone number to registry 350 and requests registry 350 forward the registration number for each of all sendings found registered to the entered telephone number. Registry 350 responds by forwarding the registration numbers of each sending found inventory 324 registered to the entered telephone number to GUI 210. GUI 210, operating as sendings picker 385, displays an icon for each of said registration numbers found enabling the user to pick one (or more) of the sendings. The user touching one (or more) of the icons serves to pick the represented sending (or sendings). GUI 210 forwards the registration number of the picked sending to obtainer 335. Obtainer 335 forwards the registration number to registry 350 and requests registry 350 forward the sending. Registry 350 forwards the sending to dispatcher 336. Dispatcher 336 dispatches the sending to deliverer 360. Deliverer 360 delivers the sending.
A fifth example of operation of this fifth example of the second embodiment (system 10ii) will now be given (5EX5). This fifth example comprises system 10hh and further configured to include sendings call-up 396. (In other words, this third example comprises deliverer picker 377.) For this example, system 10ii can include address register 357. GUI 210 is configured to respond to an entered telephone number by requesting obtainer 335 request registry 350 forward the registration number for each of all sendings found registered to the entered telephone number.
Sendings supplied by other parties have been received, registered, inventoried and stored. Some time later, the user places a call to an-other party or an-other party calls the user. The call is answered and the user and other party converse. Upon the call being answered, operating as call-up 396, GUI 210 provides the user with a keypad enabling the user to enter a telephone number. During the conversation, the user employs the provided keypad and enters a telephone number. GUI 210 provides the entered telephone number to registry 350 and requests registry 350 forward the registration number for each of all sendings found registered to the entered telephone number. Registry 350 forwards a registration number for each of all sendings found in inventory 324 registered to the entered telephone number to GUI 210. Operating as sendings picker 385, GUI 210 displays an icon for each of said all registration numbers found enabling the user to pick one (or more) of the sendings. The user touching one (or more) of the icons serves to pick the represented sending (or sendings). For this example, the user touches an icon representing a text message sending. Operating as deliverer picker 377, GUI 210 provides icon array 376. For this example, array 376 displays icons representing deliverers that can be employed for delivering a text message. Array 376 displays an icon depicting text on a display representing text display 366, an icon comprising the word EDEL representing email delivery 363, an icon comprising the word NET representing internet delivery 374, an icon depicting a telephone representing service provider delivery 369 and an icon comprising the word PORT representing external port delivery 364. The user touches one of the icons of array 376. Operating as deploy trigger 394, GUI 210 responds to the touched icon by initiating provider 375 and by instructing provider 375 to dispatch the sending to the deliverer represented by the touched icon. Provider 375 obtains and dispatches the text message sending to the represented deliverer. If the deliverer is provider delivery 369 and system 10ii includes address register 357, the text message sending, for this example, is delivered to the other party's telephone. Conversely, if system 10ii does not include register 357, system 10ii can supply the prior-described provider delivery addresser 386 enabling the user to furnish a telephone number of a desired telephone destination.
For the above five examples of operation for system 10ii, operating as call-up 396, GUI 210 has been configured to respond to the user entering a telephone number by calling-up sendings registered to the entered telephone number. However, operating as call-up 396, GUI 210 can be configured many many different ways to call-up a sending or sendings. For example, operating as call-up 396, GUI 210 can be configured to call-up sendings in response to the user entering one or more of: an address, a telephone number, an identity, a sending type, a sending class, a time period of receipt or some other information.
This second embodiment can include a sendings identifier 345. Sendings identifier 345 functions to identify a sending. An exemplary sendings identifier 345 is depicted in
In one variation, a sending detected to include said distinguishing feature can be identified by identifier 345 and immediately delivered by deliverer 360. (In one example, the identifying of a sending can comprise an activity that triggers trigger 393 to initiate provider 375 to provide the sending to deliverer 360.) As an example, an identified sending can be forwarded to registry 350. Registry 350 can determine from sending type information included with the sending the appropriate dispatcher to dispatch the determined type. Registry 350 can then forward the sending to the appropriate dispatcher and the dispatcher can dispatch the sending to a deliverer. As an example, the sending type is determined by registry 350 to be image. Registry 350 forwards the image sending to image feed 343. Feed 343 is configured to dispatch the sending to GUI 210, GUI 210 having a portion of it's display dedicated to displaying a feed 343 dispatched image. As another example, the sending type is determined by registry 350 to be video. Registry 350 forwards the video sending to file dispatcher 347. Dispatcher 347 dispatches the video sending to internet delivery 374. Delivery 374 posts the video on an internet social media website, for example, My Space. (Non-identified sendings can be immediately delivered. Also, the prior described identity information can be immediately delivered.)
Sendings identifier 345 can include a universal identifier 349. Universal identifier 349 functions to identify a universal distinguishing feature. An exemplary universal identifier 349 is depicted in
A distinguishing feature can be a signal marker sent along with a sending. However, a sending telephone requires specialized hardware and/or programming to implement the signal marker and, thus, the signal marker is not a universal distinguishing feature. Three examples of a universal distinguishing feature are described below: a telephone call time window 422, a matching addresses 397 and a time of day time window 399.
Universal identifier 349 can include a telephone call time window identifier 422 (shown as TCTW 422 in
Universal identifier 349 can include a matching addresses identifier 397 (shown as MAI 397 in
Universal identifier 349 can include a time of day time window identifier 399 (shown as TDTW 399 in
Alternately, sendings identifier 345 can be an identifier other than universal identifier 349 (above-given examples of identifier 349: identifiers 422, 397 and 399). For example, identifier 345 can be an identifier that detects for some other distinguishing feature (or features), for example: a signal marker sent with the sending, a mark on the sending, a sending density range, a sending file size range, a frequency range or any feature that distinguishes the sending relative to other sendings. However, these distinguishing features require that the other party's telephone comprise specialized hardware.
Sendings identifier 345 can include a special address identifier 437. Special address identifier 437 functions to identify a special address. An exemplary special address identifier 437 is depicted in
Sendings identifier 345 can include a manual identifier 403. Manual identifier 403 functions to enable a user to identify a sending. An exemplary manual identifier 403 is depicted in
Sendings identifier 345 can include a requested sendings identifier 355. Requested sending identifier 355 functions to identify a requested sending. An exemplary sendings requester 355 is depicted in
As one example of operation of identifier 355, the user can be engaged in a telephone call with an-other party. The user can convey to the other party, for example. “Send me some content, I'll make you a star in my universe”. Upon making the request, the user touches request sendings icon 404. Identifier 355 responds to the touched icon by storing the other party's telephone number. Subsequently, any sendings received from said other party's telephone number are identified as comprising requested sendings and are registered accordingly. As another example of operation of identifier 355, during a telephone call (including from when the call is first received or first place until after hang-up and, for example, before receipt or placing of a next telephone call) the user can touch icon 404. Touched icon 404 instructs GUI 210 to deploy a stored user-selected text message to the other party's telephone, the message requesting the other party provide content. (The touched icon instructs GUI 210 to send a signal to sendings provider 375. Provider 375 responds by dispatching said user-selected text message to delivery 369. Subsequently, delivery 369 sends the text message to the other party's telephone. Alternately, provider 375 can respond by providing a video message or an audio message or an image message or other.) Touched icon 404 also sends a signal to identifier 355. Identifier 355 responds to the signal by storing the other party's telephone number. Subsequently, any sendings received from said other party's telephone number are identified as comprising requested sendings and are registered accordingly. As another example of operation of identifier 355, identifier 355 can be configured to enable the user to request sendings at any time, on the phone or not. Identifier 355 can enable the user to address a sendings request message. The user touched icon 404 can instruct GUI 210 to deploy said sendings request message (message can be text, audio, image video or other). The user-touched icon 404 can instruct identifier 355 to store the user-supplied address (telephone number) to subsequently match the number with that of sendings received. (The prior-described matcher 353 can be employed by identifier 355 to match sendings identity information. Also, as can be seen from the above examples of operation of requested sendings identifier 355, identifier 355 can function absent any specialized other party telephone hardware or other party special addressing. Thus universal identifier 349 can include identifier 355.)
Requested sendings identifier 355 can include a request picker 411. Picker 411 functions to enable a user to pick a request message from a plurality of request messages. An exemplary picker 411 is depicted in
Requested sendings identifier 355 can include a deliverer picker 412. Picker 412 functions to enable a user to pick a deliverer to route a (one or more) requested sending to the picked deliverer. An exemplary picker 412 is depicted in
In one configuration, upon a received sending or sendings being forwarded to identifier 345, identifier 355 can then obtain the sending origin telephone number delivered with the sending and can compare the telephone number with the stored other party telephone number. If the numbers match, identifier 355 can identify the sending or sendings as comprising a deliverer picker requested sending and can forward the sending or sendings to registry 350. Registry 350 can employ, for example, a deliverer identified class register to register the sending according to the deliverer represented by the touched icon. Subsequently, for example, when obtainer 335 requests a sending from registry 350 registered to the subject other party's telephone number, registry 350 can provide the sending and can instruct dispatcher 336 to employ the appropriate dispatcher to dispatch the sending to the deliverer registry 350 has registered the sending to. In other words, as an example of operation, if the user employs picker 412 and touches an icon representing display 361, sendings received from the other party are registered by registry 350 in a class register representing display 361. Subsequently, when registry 350 forwards a sending registered to the class register representing display 361, registry 350 instructs dispatcher 336 to dispatch the sending to display 361.
In another configuration, upon a sending or sendings being forwarded to identifier 345, identifier 355 can then obtain the origin telephone number delivered with the sending and can compare the origin telephone number with the stored other party telephone number. If the numbers match, identifier 355 can identify the sending or sendings as comprising a deliverer picker requested sending and can forward the sending or sendings to the deliverer represented by the touched icon. (Picker 312 can be configured to operate in conjunction with request picker 411.)
Sendings identifier 345 can include an auto-requester 365. Auto-requester 365 functions to automatically request sendings. An exemplary auto-requester is depicted in
Auto-requester 365 can operate in conjunction with requested sending identifier 355. As an example, the address to where auto-requester 365 sends a message requesting content can be stored by identifier 355. Subsequently, identifier 355 can match the stored number with the telephone number from where a received sending has been sent. When the stored number matches the telephone number, identifier 355 identifies the sending and registry 350 can then register the sending, for example under identified class or under a auto-requested class or under other.
A sixth example of this second embodiment is illustrated as system 10jj in
For this sixth example, sendings receiver 340 includes at least one of telephone receiver 344, email receiver 351 and internet receiver 409. Sendings registry 350 includes automatic register 401 and inventory 324. Sendings provider 375 includes sendings obtainer 335 and sendings dispatcher. Deliverer 360 includes one or more of: speaker 362; display 361; text message display 366; image display 367; video display 368; email delivery 363; internet delivery 374; service provider delivery 369; delivery port 364; ring-back delivery 391; ring-back forward delivery 433; and ring-tone delivery 434. Delivery trigger 390 includes at least one of linked trigger 393 and user-deploy trigger 394. Telephone 27jj comprises mobile phone 165.
(Registry 350 can include user-selected default 410. Obtainer 335 can include prioritizer 341. Dispatcher 336 can include arranger 337. Arranger 337 can include one or more of: gallery 342; sequencer 348; and repeater 392. System 10jj can include telephone 27jj and, thus, can include phone 165. System 10jj can include caller I.D. circuitry 20. Circuitry 20 can include GUI 210 to serve as display 21. Configurator 395 can include one or more of: a configuration selector 389; an enabler 373; and a data entry 407.
For this sixth example, sendings receiver 340 can be electrically connected to (or connectable to) sendings identifier 345. Sendings identifier 345 can be electrically connected to (or connectable to) sendings registry 350. Sendings registry 350 can be electrically connected to (or connectable to) storage 370. Sendings provider 375 can be electrically connected to (or connectable to) sendings registry 350 and can be electrically connected to (or connectable to) deliverer 360. Linked trigger 393 can be electrically connected to (or connectable to) provider 375. GUI 210, operating as user-deploy trigger 394, can be electrically connected to (or connectable to) provider 375. GUI 210 can be electrically connected to (or connectable to) identifier 345.
For this sixth example, sendings identifier 345 includes circuitry and/or programming to identify a sending. Identifier 345 detects for a distinguishing feature identifying a sending. For this example, a sending received by sendings receiver 340 is forwarded to identifier 345. If identifier 345 can identify said distinguishing feature, identifier 345 forwards the identified sending to registry 350. Registry 350 employs identified class register 322 to register the sending under identified class. Registry 350 then compiles a registration number for the sending and includes the registration number in inventory 324. If identifier 345 cannot detect said distinguishing feature, identifier 345 can be configured to forward the sending to registry 350 or can be configured to ignore the sending. If the sending is forwarded to registry 350, for this example registry 350 employs non-identified class register 327 to register the sending under non-identified class. Registry 350 then compiles a registration number for the sending and includes the number in inventory 324. Said sendings registered under identified class and included in inventory 324 can subsequently be provided by sendings provider 375. For example, obtainer 335 can request registry 350 provide a sending (or sendings) registered under identified class to dispatcher 336. Dispatcher 336 can dispatch said sending registered under identified class to deliverer 360, Deliverer 360 can deliver said sending registered under identified class.
In a first example, sendings forwarded from receiver 340 can be identified by identifier 345 and register 322 (of registry 350) registers the identified sendings under identified class. For sendings forwarded from receiver 340 that identifier 345 fails to identify, identifier 345 can be configured to ignore or delete them. Provider 375 can then obtain and dispatch the identified class sendings.
In a second example, sendings forwarded from receiver 340 can be identified by identifier 345 and identified class register 322 (of registry 350) registers the identified sendings under identified class. For sendings forwarded from receiver 340 that identifier 345 fails to identify, identifier 345 can forward the sendings and non-identified class register 327 (of registry 350) can register these non-identified sendings under non-identified class. Provider 375 can then obtain and dispatch the identified class sendings under certain circumstances and can obtain and dispatch the non-identified class sendings under other circumstances. (System 10 can be configured having receiver 340 electrically connected to (or connectable to) identifier 340 and is also electrically connected to (or connectable to) registry 350. For this configuration, receiver 340 can forward certain sendings to identifier 345 and can forward other sendings to registry 350, thus bypassing identifier 345. In other words, registry 350 can employ identified class register 322, non-identified class register 327 and received class register 328.)
In the prior-given examples of operation for the first, second, third, fourth and fifth examples of this second embodiment, sendings received by sendings receiver 340 were forwarded to registry 350, registered by received class register 328, included in inventory 324 and, subsequently, provided by provider 375 and delivered by deliverer 360.
In prior-given examples of the first, second, third, fourth and fifth examples of this second embodiment, a sending received by receiver 340 was forwarded to received class register 328, registered, included in inventory 324 and, subsequently, provided by provider 375 to deliverer 360. Sendings identifier 345 can be employed in any or all of said prior-given examples. As shown, identifier 345 can be located between sendings receiver 340 and registry 350. A sendings previously forwarded to registry 350 (register 328) in said prior-given examples can instead be forwarded to identifier 345. Identifier 345 can identify the sending (or not) and can then forward the identified sending to registry 350. Identified class sendings can be employed anywhere received class sendings can be employed. (Also, non-identified class sendings can be employed anywhere received class sendings can be employed and, the to-be-described user-selected class sendings can be employed anywhere received class sendings can be employed). Identified class sendings can be linked trigger deployed for example employing linked trigger 393. Identified class sendings can be user-deploy trigger deployed for example employing deploy trigger 394. Identified sendings can be picked, for example employing sendings picker 385. Identified sendings can be called up, for example employing sendings call-up 396. This second embodiment can employ one or more of: received class sendings, identified class sendings, non-identified class sendings and user-selected class sendings.
This second embodiment can include a user-selected sendings supplier 380. User-selected sendings supplier 380 functions to enable employment of user-selected sendings. An exemplary user-selected sendings supplier 380 is depicted in
The exemplary user-selected sendings supplier 380 includes sendings selector 425. Sendings selector 425 functions to enable a user to select a sending. An exemplary sendings selector 425 is depicted in
Sending selector 425 can include a port 423. Port 423 functions to enable sendings to be selected from an external source. An exemplary port 423 is depicted in
Sending selector 425 can include internet access 424. Internet access 424 functions to enable sendings to be selected from the internet. An exemplary internet access 424 is depicted in
Sending selector 425 can include an audio recorder 426. Audio recorder 426 functions to enable the recording of audio sendings. An exemplary recorder 426 is depicted in
Sending selector 425 can include a text entry 427. Text entry 427 functions to enable the entry of a text message sending. An exemplary entry 427 is depicted in
Sending selector 425 can include a still camera 428. Still camera 428 functions to enable the making of an image sending. An exemplary camera 428 is depicted in
Sending selector 425 can include a video camera 429. Video camera 429 functions to enable the making of a video sending. An exemplary camera 429 is depicted in
Sending selector 425 can include a memory access 431. Memory access 431 functions to enable access to memory to select sendings. An exemplary access 431 is depicted in
Sending selector 425 can include a service provider access 432. Provider access 432 functions to enable access to a service provider to select sendings. An exemplary access 432 is depicted in
The exemplary user-selected sendings supplier 380 includes a user-selected registry 405. User-selected registry 405 functions to register user-selected sendings. An exemplary user-selected registry 405 is depicted in
The user can employ sendings selector 425 to select a sending. Selector 425 can forward the selected sending to registry 405. As a first example, registry 405 can detect the forwarded sending and can supply the sending to registry 350 and instruct registry 350 to employ user-selected class register 387 (of registry 350) to register the sending under user-selected class. (Alternately, selector 425 can forward the sending directly to registry 350. Registry 350 can be configured to respond to receipt of a sending from selector 425 by employing user-selected class register 387 to register the sending under user-selected class. In other words, for this example, registry 350 can provide the functionality of registry 405.)
As a second example, registry 405 can detect the forwarded sending and can supply the sending to registry 350 and can instruct registry 350 to employ one or more of: time register 371, type register 372 and user-selected class register 387. Registry 350 can employ time register 371 to register the time the registering of the sending takes place. Registry 350 can employ type register 372 to register the type the sending comprises. Registry 350 can employ user-selected class register 387 to register the sending under user-selected class. (Alternately, selector 425 can forward the sending directly to registry 350. Registry 350 can be configured to respond to receipt of a sending from selector 425 by employing one or more of: time register 371, type register 372 and user-selected class register 387. In other words, for this example, registry 350 can provide the functionality of registry 405. Also, register 372 can obtain type information included with the supplied sending to register the sending under type. For example, the sending can comprise type information included with file addressing.)
As a third example, registry 405 can detect the forwarded sending and can enable the user to provide one or more of: address information, time registered, sending type, sending class or some other trait or relevant information (as an example the name of an-other party). Registry 405 can include GUI 210, US Registry 405 shown located at GUI 210 in
As a fourth example, registry 405 can detect the forwarded sending and can enable the user to provide the above-described address information. Registry 405 can employ GUI 210. GUI 210 can provide a keypad to enable the user to enter the address information (for example a telephone number). GUI 210 can forward the user's entry (for example an entered telephone number) to registry 405. Registry 405 can register the user's entry to the sending as a registration number component and can forward the sending and component to registry 350. Registry 350 can employ one or more of: time register 371, type register 372 and user-selected class register 387. Registry 350 can employ time register 371 to register the time registering the sending takes place. Registry 350 can employ type register 372 to register the type the sending comprises. (Register 372 can obtain type information included with the supplied sending to register the sending under type.) Registry 350 can employ user-selected class register 387 to register the sending under user-selected.)
For each selected sending forwarded from selector 425, register 350 can compile a registration number inclusive of each component or components registered by user-selected registry 405 and/or time register 371 and/or type register 372 and/or user-selected class register 387. Registry 350 can list the registration number in inventory 324 and can forward the inventoried sending to be stored in storage 370.
(Registry 405 can be configured to enable the user to delete, for example, to remove a sending from inventory 324 and/or from storage 370. Registry 405 can enable the user to delete a sending of any registered origin, registered type, registered time or registered class. Registry 405 can enable the user to re-register a sending.)
The exemplary user-selected sendings supplier 380 can include a user-selected default 410. User-selected default 410 functions to provide default sendings. An exemplary user-selected default 410 is depicted in
A seventh example of this second embodiment is illustrated as system 10kk in
For this seventh example, sendings receiver 340 includes at least one of telephone receiver 344, email receiver 351 and internet receiver 409. Sendings registry 350 can include inventory 324 and can include automatic register 401. Sendings provider 375 includes sendings obtainer 335 and sendings dispatcher 336. Deliverer 360 includes one or more of: speaker 362; display 361; text message display 366; image display 367; video display 368; email delivery 363; internet delivery 374; service provider delivery 369; delivery port 364; ring-back delivery 391; ring-back forward delivery 433; and ring-tone delivery 434. Delivery trigger 390 includes at least one of linked trigger 393 and user-deploy trigger 394. Telephone 27kk comprises mobile phone 165.
(Registry 350 can include user-selected default 410. Obtainer 335 can include prioritizer 341. Dispatcher 336 can include arranger 337. Arranger 337 can include one or more of: gallery 342; sequencer 348; and repeater 392. Identifier 345 can include one or more of: universal identifier 349; special address identifier 437; manual identifier 403; requested sendings identifier 355; and auto-requester 365. Configurator 395 can include one or more of: a configuration selector 389; an enabler 373; and a data entry 407. System 10kk can include telephone 27kk and, thus, can include phone 165. System 10kk can include caller I.D. circuitry 20. Circuitry 20 can include GUI 210 to serve as display 21 to display caller I.D. information to the user.)
For this seventh example, sendings receiver 340 can be electrically connected to (or connectable to) sendings registry 350. Registry 350 can be electrically connected to (or connectable to) storage 370. Sendings provider 375 can be electrically connected to (or connectable to) sendings registry 350 and can be electrically connected to (or connectable to) deliverer 360. Delivery trigger 390 can be electrically connected to (or connectable to) sendings provider 375. User-selected sendings supplier 380 can be electrically connected to (or connectable to) sendings registry 350.
For this seventh example, user-selected sendings supplier 380 includes circuitry and/or programming to enable employment of user-selected sendings. Supplier 380 includes sendings selector 425 and user-selected registry 405 and can include user-selected default 410. Selector 425 includes circuitry and/or programming to enable the user to select a sending. Selector 425 enables the user to select one or more of: audio sendings, text message sendings, image/picture sendings, video sendings or combined audio and video sendings. Selector 425 includes one or more of: a port 423, an internet access, 424; an audio recorder 426; a data entry 427; a still camera 428, a video camera 429, a memory access 431, a service provider access 432, and/or some other source for sendings.
For this seventh example, user-selected registry 405 includes circuitry and/or programming to register user-selected sendings. Registry 405 registers a trait (or traits) of a sending to be a component (or components) of a registration number. Registry 405 forwards the registered user-selected sending to registry 350. Registry 350 compiles said component or components into said registration number and lists said compiled registration number in inventory 324. Subsequently, the sending can be located by registry 350 searching inventory 324 for the registration number or for one or more of said components of the registration number.
For this seventh example, user-selected default 410 includes circuitry and/or programming to provide default sendings. Default 410 provides one or more user-selected sendings when other sendings are not available. As an example, registry 350 can search inventory 324 for a requested sending. Upon failing to locate the requested sending, default 410 can respond by supplying a user-selected sending found in inventory 324 to act as the requested sending. Registry 350 can forward the supplied default sending to dispatcher 336.
In prior-given examples of the first, second, third, fourth and fifth examples of this second embodiment, a sending received by receiver 340 was forwarded to received class register 328, registered, included in inventory 324 and, subsequently, provided by provider 375 to deliverer 360. In prior-given examples of the sixth example of this second embodiment, a sending received by receiver 340 was forwarded to identifier 345, identified and forwarded to identified class register 322 (or non-identified class register 327), registered, included in inventory 324 and, subsequently, provided by provider 375 to deliverer 360 and delivered by deliver 360. In the employment of user-selected sendings supplier 380, a sending selected by the user employing selector 425 can be forwarded from selector 425 to user-selected class registry 387, registered, included in inventory 324 and, subsequently, provided by provider 375 to deliverer 360 and delivered by deliverer 360. Accordingly, user-selected sendings as supplied by sendings supplier 380 can be provided and delivered wherever sendings received by receiver 340 can be provided and delivered.
User-selected class sendings can be linked trigger deployed for example employing linked trigger 393 (system 10ee, a mix of user-selected and receiver 340 received sendings can be link trigger deployed). User-selected class sendings can be user-deploy trigger deployed for example employing deploy trigger 394 (system 10ff, a mix of user-selected and receiver 340 and received sendings can be user deployed). User-selected class sendings can be picked, for example employing sendings picker 385 (a mix of sendings supplier 380 supplied sendings and receiver 340 received sendings can be provided to pick from). User-selected class sendings can be called up, for example employing sendings call-up 396 (a mix of user-selected and receiver 340 received sendings can be called up). (Sendings received by receiver 340 that provider 375 can provide include: received class sendings, identified class sendings, non-identified class sendings.)
(In one variation, system 10 can be configured to provide and deliver user-selected sendings stand-alone, i.e. not configured to also provide and deliver receiver 340 received sendings. As one example, system 10 can be configured to include registry 350, storage 370, provider 375, deliverer 360, delivery trigger 390 and user-selected sendings supplier 380. Supplier 380 supplies sendings to registry 350. Registry 350 inventories each sending supplied, includes the sending in inventory 324 and forwards the sending to storage 370. Subsequently, provider 375 can provide one or more of the user-selected sendings and deliver 360 can deliver each of the provided sendings. Trigger 390 can comprise any of the herein examples given in the triggering of provider 375. This example of the variation can include one or more of: deliverer picker 377, sendings picker 385, sendings call-up 396, sendings poster supplier 440 and configurator 395.)
This second embodiment can include an inventory review poster 440. Inventory review poster 440 functions to enable review and selection of inventoried sendings and to post selections. An exemplary inventory review poster 440 is depicted in
The exemplary inventory review poster 440 includes a post trigger 444. Post trigger 444 functions to enable a user to trigger the posting of a sending. An exemplary post trigger 444 is depicted in
The exemplary inventory review poster 440 includes an inventoried sending reviewer 447. Inventoried sending reviewer 447 functions to provide a review of an inventoried sending. An exemplary sending review 441 is depicted in
Inventoried sending reviewer 447 can include a delivery trigger provided review 448. Delivery trigger provided review 448 functions to operate in conjunction with a delivery trigger to provide a review of a sending. An exemplary delivery trigger provided review 448 is depicted in
As a first example of reviewer 448, reviewer 448 can operate in conjunction with delivery trigger 390 with delivery trigger 390 comprising linked trigger 393. As one example of operation, a telephone call is received from an-other party (or the other party is dialed). Other party address register 357 obtains the other party's telephone's number. A signal representing detection of the incoming call (or of the dialed number) triggers linked trigger 393. Trigger 393 signals obtainer 335. Obtainer 335 requests registry 350 forward all sendings registered to the obtained telephone number. Registry 350 forwards said sendings to dispatcher 336. For this example, registry 350 forwards an audio sending and image sending. Dispatcher 336 employs audio player 338 to dispatch the audio sending to speaker 362 of deliverer 360. Speaker 362 broadcasts the audio sending enabling the user to review the sending and decide whether to select the sending for posting to a web-site. Dispatcher 336 also employs image feed 343 to dispatch the image sending to image display 367 of deliverer 360. Display 367 displays the image sending enabling the user to review the sending and decide whether to select the sending for posting. To select a sending, the user triggers post trigger 444 by touching post trigger icon 442. Acting as trigger 444, GUI 210 responds to the touched icon by displaying icons representing the sendings delivered for review, for this example an audio icon and an image icon. The user desires to post the audio sending and, so, touches the audio icon. GUI 210 responds by instructing provider 375 to provide the audio sending. Provider 375 responds by dispatching the selected audio sending to web-site poster 374.
As a second example of reviewer 448, reviewer 448 can operate in conjunction with delivery trigger 390 with delivery trigger 390 comprising deploy trigger 394. As one example of operation, a telephone call is received from an-other party. Other party address register 357 obtains the other party's telephone's number. Either prior to answering, while conversing or after hang-up, the user triggers deploy trigger 394. System 10 responds to trigger 394 as described-above in response to trigger 393. One or more sendings are delivered. The delivered sendings provide a review for the user. From the review, the user can decide to trigger post trigger 444 to select one (or more) of the one or more reviewed sendings for posting. GUI 210 can respond to a sending selection by instructing provider 375 to provide the selected sending to web-site poster 374.
Inventoried sending reviewer 447 can include a picker provided review 449. Picker provided review 449 functions to operate in conjunction with a picker to provide a review of a sending. An exemplary picker provided review 449 is depicted in
As an example of operation, reviewer 448 can operate in conjunction with sendings picker 385. As one example of operation, a telephone call is received from an-other party (or the other party is dialed). Other party address register 357 obtains the other party's telephone's number. Responsive to a signal representing detection of the incoming call (or of the dialed number), register 357 provides the obtained number to registry 350 and registry 350 responds by forwarding the registration number to GUI 210 of each sending found in inventory 324 registered to that telephone number. GUI 210 then employs the registration number information to display picker 385 icon array 352, array 352 comprising one icon representing each forwarded registration number. The icons displayed can comprise the date registered and a representation of the represented sending. The representation can be a miniature of the image sending, a frame from the video, the title of the song (audio), the beginning words of the text message etc. For this example, the call is answered (either by called party or by user).
In a first example, while conversing, from viewing the displayed icons the user decides to post one of the sendings represented by one of the displayed icons. The user touches post trigger icon 442 followed by the icon representing the selected sending. Acting as trigger 444, GUI 210 responds to the touched icon 442 followed by the touch picker 385 icon by forwarding the registration number of the sending to provider 375 and instructing provider 375 to provide the sending. Provider 375 responds by obtaining and dispatching the sending to web-site poster 374.
In a second example, while conversing, from viewing the displayed icons the user decides he'd like a more in-depth review of a particular icon represented sending. The user touches post trigger icon 442 twice followed by touching the particular icon. GUI 210 responds to the twice touched icon 442 followed by the touch icon of picker 385 by forwarding the registration number of the selected sending to provider 375 and instructing provider 375 to obtain and dispatch the sending. Provider 375 responds by obtaining and dispatching the sending to a delivery available to the user. For example, if the sending is audio, provider 375 can dispatch the sending to speaker 362. For the speaker 362 example, the user is enabled to listen to the audio sending. The user decides to post the sending. To do so, the user again twice touches icon 442. GUI 210 responds to the twice-touched icon 442 by forwarding the registration number of the more in-depth reviewed sending to provider 375 and instructing provider 375 to provide the sending. Provider 375 responds by obtaining and dispatching the sending to web-site poster 374.
Inventoried sending reviewer 447 can include a call-up provided review 451. Call-up provided review 451 functions to employ a call-up to provide a review of a sending. An exemplary call-up provided review 451 is depicted in
As an example of operation, reviewer 448 can operate in conjunction with sendings call-up 396. As one example of operation, the user employs sendings call-up 396 by entering a telephone number, for example of a familiar party. Call-up 396 requests from registry 350 the registration numbers of all sendings found in inventory 324 registered to the entered number. Registry 350 provides the requested registration numbers. GUI 210 then employs the registration number information to display one icon to represent each forwarded registration number. The icons displayed can comprise the date registered and a representation of the represented sending. The representation can be a miniature of the image sending, a frame from the video, the title of the song (audio), the beginning words of the text message etc. For this example, the call is answered (either by called party or by user).
In a first example, from viewing the displayed icons the user decides to post one of the sendings represented by one of the displayed icons. The user touches post trigger icon 442 followed by the icon representing the selected sending. Acting as trigger 444, GUI 210 responds to the touched icon 442 followed by the touch call-up 396 icon by forwarding the registration number of the sending to provider 375 and instructing provider 375 to provide the sending. Provider 375 responds by obtaining and dispatching the sending to web-site poster 374.
In a second example, from viewing the displayed icons the user decides he'd like a more in-depth review of a particular icon represented sending. The user touches post trigger icon 442 twice followed by touching the particular icon. GUI 210 responds to the twice-touched icon 442 followed by the touch call-up 396 icon by forwarding the registration number of the selected sending to provider 375 and instructing provider 375 to obtain and dispatch the sending. Provider 375 responds by obtaining and dispatching the sending to a delivery available to the user. For example, if the sending is a video, provider 375 can dispatch the sending to video display 368. For the display 368 example, the user is enabled to view/watch the video for a duration to make his posting decision. The user decides to post the sending. The user again twice touches icon 442. GUI 210 responds to the twice-touched icon 442 by forwarding the registration number of the more in-depth reviewed sending to provider 375 and instructing provider 375 to provide the sending. Provider 375 responds by obtaining and dispatching the sending to web-site poster 374.
The exemplary inventory review poster 440 includes web-site poster 374 (described prior). Web-site poster 374 functions to post sendings to an internet web-site. An exemplary post trigger 444 is depicted in
An eighth example of this second embodiment is illustrated as system 10ll in
For this eighth example, sendings receiver 340 includes at least one of telephone receiver 344, email receiver 351 and internet receiver 409. Sendings registry 350 includes inventory 324 and includes automatic register 401 and inventory 324. Sendings provider 375 includes sendings obtainer 335 and sendings dispatcher. Deliverer 360 includes one or more of: speaker 362; display 361; text message display 366; image display 367; video display 368; email delivery 363; web-site poster 374; service provider delivery 369; delivery port 364; ring-back delivery 391; ring-back forward delivery 433; and ring-tone delivery 434. Delivery trigger 390 can include at least one of linked trigger 393 and user-deploy trigger 394. Telephone 27jj comprises mobile phone 165.
(Registry 350 can include user-selected default 410. Obtainer 335 can include prioritizer 341. Dispatcher 336 can include arranger 337. Arranger 337 can include one or more of: gallery 342; sequencer 348; and repeater 392. Identifier 345 can include one or more of: universal identifier 349; special address identifier 437; manual identifier 403; requested sendings identifier 355; and auto-requester 365. System 10ll can include telephone 27ll and, thus, can include phone 165. System 10ll can include caller I.D. circuitry 20. Circuitry 20 can include GUI 210 to serve as display 21 to display caller I.D. information to the user.)
For this eighth example, sendings receiver 340 can be electrically connected to (or connectable to) sendings registry 350. Sendings registry 350 can be electrically connected to (or connectable to) storage 370. Sendings provider 375 can be electrically connected to (or connectable to) sendings registry 350 and can be electrically connected to (or connectable to) deliverer 360. Delivery trigger 390 can be electrically connected to (or connectable to) sendings provider 375. Operating as trigger 444, GUI 210 can be electrically connected to (or connectable to) sendings provider 375.
For this eighth example, inventory review poster 440 includes circuitry and/or programming to enable review and posting of inventoried sendings. Poster 440 enables the user to review inventoried sendings, for example sendings found in inventory 324, enables the user to select a reviewed sending and posts the selected sending to a web-site. Poster 440 includes post trigger 444, inventoried sending reviewer 447 and web-site poster 374.
This second embodiment can include a configurator 395. Configurator 395 functions to enable a user to configure operation. An exemplary configurator 395 is depicted in
Configurator 395 can include a configuration selector 389. Configuration selector 389 functions to enable a user to select a configuration. An exemplary selector 389 is depicted in
Selector 389 can provide a plurality of configurations, for example, by varying: the components employed in the system, operating routines, the cadence (timing) of the interaction of components, mathematics variables employed, and duration lengths. The following are examples of varying the components employed. Configurator 395 can vary employment combinations of: picker 377, picker 385, call-up 396, identifier 345 and supplier 380 seventeen different ways (seventeen combinations); receiver 340 components: telephone receiver 344, email receiver 351 and Internet receiver 409 (seven combinations); identifier 345 components: identifiers 422, 399 and 397; and, triggers 393 and 394. Configurator 395 can vary the operating routines of one or more of (components employed by the above components): receiver 340; identifier 345; registry 350; sendings supplier 380; storage 370; sendings provider 375; deliverer 360; delivery trigger 390; sendings picker 385; deliverer picker 377; call-up 396; identifier 345; supplier 380; and configurator 395. Configurator 395 can vary the operating routines of one or more of: GUI 210; requested identifier 355; automatic register 401; user-selected default 410; sendings selector 425; sendings registry 405; linked trigger 393; deploy trigger 394; prioritizer 341; arrangers 342 and 348; dispatchers 338, 339, 343, 346 and 347; displays 366, 367 and 368; deliverers 362, 391, 364, 369, 374, 363, 433 and 434; type picker 354; class picker 406; message picker 411; deliverer picker 412; configurator selector 425; enabler 373; and data entry 407.
An example to illustrate the large number of configurations that configurator 395 could provide for the user to choose from will now be given. An embodiment of system 10 includes sendings receiver 340, sendings registry 350, storage 370, sendings provider 375, deliverer 360 and delivery trigger 390 and can include deliverer picker 377, sendings picker 385, sendings call-up 396, sendings identifier 345 and sendings supplier 380. “Included” components can be combined to the “can include” components in 26 different configurations. (Configuration examples: the includes plus picker 377, the includes plus picker 385, the includes plus picker 377 plus call-up 396, etc.) A system comprising just the includes can be configured to provide at least 5098 different response combinations as discussed prior for system 10ee. Multiplying the 26 different configurations by 5098 different responses suggests 131,448 different overall configurations that configurator 395 can provide (without figuring in cadence, mathematics variables and duration lengths). These 131,448 combinations represent the combining of only the major system components. In other words, this second embodiment can be configured tens of thousands of ways.
Configurator 395 can include an enabler 373. Enabler 373 functions to enable a user to enable and/or disable functionality. An exemplary enabler 373 is depicted in
Enabler 373 can enable a user to enable and/or disable and/or to enable/disable program routines employed by, for example: receiver 340, identifier 345, registry 350, sendings supplier 380, storage 370, sendings provider 375, deliverer 360, delivery trigger 390, sendings picker 385, deliverer picker 377, call-up 396, identifier 345, supplier 380, configurator 395. The following are examples of components employed by the above components that enabler 373 can enable a user to enable and/or disable and/or to enable/disable program routines employed by: GUI 210, requested identifier 355, automatic register 401, user-selected default 410, sendings selector 425, sendings registry 405, linked trigger 393, deploy trigger 394, prioritizer 341, arrangers 342 and 348, dispatchers 338, 339, 343, 346 and 347, displays 366, 367 and 368, deliverers 362, 391, 364, 369, 374, 363, 433 and 434, type picker 354, class picker 406, message picker 411, deliverer picker 412, configurator selector 425, enabler 373 and data entry 407.
Configurator 395 can include a data entry 407. Data entry 407 functions to enable a user to enter information. An exemplary data entry 407 is depicted in
Data entry 407 can enable a user to enter, for example, one or more of: beginning and end times for telephone call time window 422; beginning and end times and/or dates for time of day time window 399; addressing codes for special identifier 437; addressing for one or more of addressers 386, 381 and 379; system cadence parameters; mathematics variables; and duration lengths.
An example of GUI 210 operating as selector 387, enabler 373 and entry 407 will now be given. A “configurator” option is included on an opening display on GUI 210. The user touches the “configurator” icon. A next screen presents three options: “selector”, “enabler” and “data entry”. As a first example, the user touches the “selector” icon. A next screen presents a plurality of operation configurations for the user to pick from. The user picks (touches) one of the configuration icons. GUI 210 engages the components and/or programming to implement the picked configuration.
As a second example, the user touches the “enabler” icon. A next screen presents components and operation routines available for the user to enable and/or disable and presents the present status of each. The user picks (touches) one of the component icons or operation routine icons. GUI 210 responds by changing the status of the component or routine accordingly (e.g. if on, GUI 210 changes to off).
As a third example, the user touches the “data entry” icon. A next screen presents routines that employ user-entered variables. For example the next screen can present: “telephone call time window”, “time of day time window”, “special identifier”, “provider delivery addresser”, “web-site poster addresser” and “email delivery addresser”. For this example, the user touches the “provider delivery addresser” icon. A next screen presents prior-entered existing information (e.g. last telephone number entered) and a keyboard for the user to enter addressing (e.g. a telephone number). The user enters a number. Subsequently, GUI 210 employs the entered number to address a sending for delivery by service provider 121.
A ninth example of this second embodiment is illustrated as system 10mm in
For this ninth example, sendings receiver 340 includes at least one of telephone receiver 344, email receiver 351 and internet receiver 409. Sendings registry 350 includes inventory 324 and can include automatic register 401. Sendings provider 375 includes sendings obtainer 335 and sendings dispatcher. Deliverer 360 includes one or more of: speaker 362; display 361; text message display 366; image display 367; video display 368; email delivery 363; web-site poster 374; service provider delivery 369; delivery port 364; ring-back delivery 391; ring-back forward delivery 433; and ring-tone delivery 434. Delivery trigger 390 can include at least one of linked trigger 393 and user-deploy trigger 394. Telephone 27jj comprises mobile phone 165.
(Registry 350 can include user-selected default 410. Obtainer 335 can include prioritizer 341. Dispatcher 336 can include arranger 337. Arranger 337 can include one or more of gallery 342; sequencer 348; and repeater 392. Identifier 345 can include one or more of: universal identifier 349; special address identifier 437; manual identifier 403; requested sendings identifier 355; and auto-requester 365. System 10mm can include telephone 27mm and, thus, can include phone 165. System 10mm can include caller I.D. circuitry 20. Circuitry 20 can include GUI 210 to serve as display 21 to display caller I.D. information to the user.)
For this ninth example, sendings receiver 340 can be electrically connected to (or connectable to) sendings registry 350. Sendings registry 350 can be electrically connected to (or connectable to) storage 370. Sendings provider 375 can be electrically connected to (or connectable to) sendings registry 350 and can be electrically connected to (or connectable to) deliverer 360. Delivery trigger 390 can be electrically connected to (or connectable to) sendings provider 375. Operating as configurator 395, GUI 210 can be electrically connected to (or connectable to) sendings receiver 340, sendings registry 350, storage 370, sendings provider 375, deliverer 360 and delivery trigger 390 and to one or more of picker 377, picker 385, call-up 396, identifier 345 and supplier 380.
For this ninth example, configurator 395 includes one or more of: a configuration selector 389; an enabler 373; and a data entry 407. Configurator 395 provides a user with options to select from to configure system operation. Configurator 395 includes GUI 210. To operate as configurator 395, GUI 210 includes circuitry and/or programming to enable a user to configure operation. GUI 210 operates as one or more of configuration selector 389, enabler 373 and data entry 407.
A first example of operation of this ninth example of the second embodiment (system 10mm) will now be given. This example comprises a combining of the first, second, third, fourth and fifth examples and further configured to include configurator 395. For this example, configurator 395 includes configuration selector 389, enabler 373 and data entry 407.
A “configurator” option is included on an opening display on GUI 210. The user touches the “configurator” icon. A next screen presents three options: “selector”, “enabler” and “data entry”. The user touches the “selector” icon. A next screen presents a plurality of configurations for the user to pick from. The plurality of configurations comprises the prior-given examples of operation of this second embodiment: 1EX1, 1EX2, 1EX3, 1EX4, 1EX5, 1EX6, 1EX7, 1EX8, 2EX1, 2EX2, 2EX3, 2EX4, 2EX5, 3EX1, 3EX2, 3EX3, 4EX1, 4EX2, 4EX3, 5EX1, 5EX2, 5EX3, 5EX4 and 5EX5. The user picks (touches) one of the configuration icons. For example, the user picks 2EX2. GUI 210 responds to the user pick by engaging the components and/or programming to implement 2EX2, in other words to implement the second example of operation for the second example (system 10ff) of this second embodiment. Subsequently, sendings are provided and delivered as described in the second example of operation for the second example.
A second example of operation of this ninth example of the second embodiment (system 10mm) will now be given. For this example, system 10mm can comprise the first, second, third, fourth, fifth, sixth or seventh example (and can comprise a combining of the first, second, third, fourth, fifth, sixth and/or seventh examples), and further configured to include configurator 395. For this example, configurator 395 includes configuration selector 389, enabler 373 and data entry 407.
A “configurator” option is included on an opening display on GUI 210. The user touches the “configurator” icon. A next screen presents three options: “selector”, “enabler” and “data entry”. The user touches the “selector” icon. A next screen presents a plurality of configurations for the user to pick from. The plurality of configurations can comprise, for example: a first icon representing a basic configuration including receiver 340, registry 350, storage 370, provider 375, deliverer 360, delivery trigger 390 and configurator 395; a second icon representing the basic configuration plus register 357; a third icon representing basic plus picker 385, a fourth icon representing basic plus call-up 396, a fifth icon representing basic plus identifier 345, a sixth icon representing basic plus supplier 380, a seventh icon representing basic plus poster 440, eighth icon—basic plus register 357 plus picker 385, ninth icon—basic plus register 357 plus call-up 396, etc.
The user selects (touches) one of the configuration icons. For example, the user selects the third icon. GUI 210 responds by implementing a component configuration comprising receiver 340, registry 350, storage 370, provider 375, deliverer 360, delivery trigger 390, configurator 395 and picker 385 and by presenting a next screen. In the next screen, GUI 210 presents a plurality of enabler options available for incorporation with the selected third icon configuration. The plurality of enabler options can comprise icons, for example: “identifier”, “link trigger”, “user trigger”, “speaker type”, “display”, “ring-back delivery”, “port”, “web-site poster”, “ring-back forward delivery”, “type picker”, “class picker” and “Finished”.
The user selects (touches) one of the enabler option icons. For example, the user selects “web-site poster”. GUI 210 responds by enabling ring-back delivery. GUI 210 presents a next screen. In the next screen, GUI 210 again presents the plurality of enabler options available for incorporation with the selected third icon configuration (along with indication that web-site poster has been enabled). The user selects (touches) one of the enabler option icons. For example, the user selects “Finished”. In a next screen, GUI 210 presents data entry options available for incorporation with the selected third icon configuration and the selected web-site poster. The data entry options can be, for example: “web-site poster addressing” and finished. For example, the user selects “web-site poster addressing”. GUI 210 presents a next screen comprising a keypad and a “Finished” icon. The user can employ the keypad to enter an address when completed can touch “Finished” GUI 210 stores the entered address and presents a next screen presenting “Thank You!”. Subsequently, provider 375 can dispatch sendings to web-site poster 374 addressed to the entered address.
A tenth example of this second embodiment is illustrated as system 10nn in
In summary, the second embodiment (
Commencer 325 has been depicted in
Described prior sendings supplied by user-selected sendings supplier 425 can be inventoried and stored. Said information can be re-selected and again supplied by user-selected sendings supplier 425 to be inventoried and stored, re-selecting to include selecting a new/next/subsequent choice of sending. A user can select sendings from any number of sources such as: libraries on the internet via a computer or a WiFi connection (if system 10 is WiFi enabled) or provider 121, a music player, a recording device, libraries stored in handling system 10 itself, libraries stored in mobile phone 165, libraries stored at service provider 121. (Said libraries on the internet may be found on a service provider web site, a telephone manufacturer web site, a music web site or other. The stored information can also be stored on one or more memory devices which can be made accessible to the user via a service provider. The stored information can be stored elsewhere, for example, elsewhere at system 10 or elsewhere at telephone 27, or other.)
Handling systems 10aa through 10nn can reside with and as the property of the telephone user as illustrated in
The embodiments of telephone call handling system 10 herein disclosed in
Additionally, system 10 can be located otherwise. For example, system 10 can be located at service provider 121 with control buttons and display 21 (and/or GUI 210) located at telephone 27. For example, one or more of the components of system 10 can be located at provider 121 with the remainder of the components located at telephone 27 with control buttons and display 21 (and/or GUI 210) located at telephone 27. For example, system 10 can be located in-part at the base of a cordless telephone and in-part at the cordless telephone itself. For example, system 10 can be located in-part at a service provider 121, in-part located between service provider 121 and telephone 27 and with control buttons and display 21 (and/or GUI 210) located at telephone 27. For example, system 10 can be located in-part at a service provider 121 and in-part located between service provider 121 and telephone 27, with control buttons and display 21 (and/or GUI 210) located between service provider 121 and telephone 27 and with control buttons and display (and/or GUI 210) located at telephone 27. For example, system 10 can be located in-part at a service provider 121, in-part located between service provider 121 and telephone 27, in-part at telephone 27 and with control buttons and display 21 (and/or GUI 210) located at telephone 27. For example, service provider 121 can provide phone service along with cable television service. A television screen can then comprise display 21 and system 10 can be located, for example, at telephone 27 (or at a cable control box or at other). Telephone 27 can be electrically connected to (or connectable to) a cable control box (user's home) and control buttons (and/or GUI 210) can be located at telephone 27 and/or can be located on a remote control associated with the cable box and/or can be located at the cable box (or other cable/phone configurations).
Telephone 27 can comprise a corded landline telephone, a cellular telephone, a cordless landline phone, or other. Any embodiment herein disclosed employing (or operating in conjunction with) a landline telephone can be configured to employ (or to operate in conjunction) with a cellular telephone. Any embodiment herein disclosed employing (or operating in conjunction) with a cellular telephone can be configured to employ (or operate in conjunction) with a landline telephone.
It is understood that the above examples of the various embodiments provided for herein can be implemented using alternative means and structures to provided essentially equivalent functionality, and that the scope of the present invention is not to be limited by these examples. As an example, the specific content of messages which can be provided to a caller by the systems described herein can vary from the given examples, without varying from the general scope of a respective embodiment. Further, the functionality provided by the interface 31 (i.e., of generating an off-hook signal in order to enable outgoing transmissions of information to the caller) can be accomplished using other known circuitry and/or software implementations. In general, the systems described herein include circuitry and/or software implementations to enable information to be sent to a caller telephone without necessarily placing the called phone in a call-answered condition.
Claims
1. A telephone call handling system, the system comprising:
- a sendings receiver configured to receive sendings sent from an other party's telephone via a telephone service; a sendings registry configured to automatically inventory the received sendings; a storage configured to store the inventoried sendings; a sendings provider configured to provide at least one of the inventoried sendings; a deliverer configured to deliver the provided sendings; and a delivery trigger configured to initiate the provider to provide the at least one of the inventoried and stored sendings.
2. The telephone system of claim 1 and wherein the delivery trigger is further configured to be triggered by a user.
3. The telephone system of claim 1 and wherein the system further includes caller I.D. circuitry to provide caller I.D. information to the user and the user can trigger the trigger based on the caller I.D. information.
4. The telephone system of claim 1 and wherein the delivery trigger is further configured to be triggered linked to an activity.
5. The telephone system of claim 1 and wherein the sendings provider comprises a prioritizer to prioritize the providing of at least one of the inventoried sendings.
6. The telephone system of claim 1 and wherein the system further comprises a sending review poster to supply sendings for posting at an internet website.
7. The telephone system of claim 1 and wherein the system further comprises at least one of: a sendings picker, a deliverer picker, a sendings call-up, a sendings identifier, a user-selected sendings supplier, a inventory review poster and a configurator.
8. The telephone system of claim 7 and wherein the sendings identifier comprises a universal identifier to identify a feature that can be employed absent any specialized hardware and/or programming at the sending device.
9. The telephone system of claim 7 and wherein the sendings identifier comprises a requested sendings identifier to identify a requested sending.
10. The telephone system of claim 7 and wherein the sendings picker comprises at least one of: a sendings type picker and a sendings class picker.
11. A method for delivering sendings, the method comprising:
- receiving sendings sent from an other party's telephone via a telephone service;
- inventorying the received sendings automatically;
- storing the inventoried sendings;
- providing at least one of the inventoried sendings, said providing initiated by a trigger; and
- delivering the provided sending or sendings.
12. The method of claim 11 and wherein the providing at least one of the inventoried sendings, said providing initiated by a trigger further comprises enabling a user to trigger the trigger.
13. The method of claim 11 and wherein the method further comprise providing caller I.D. information to the user enabling the user to trigger the trigger based on the caller I.D. information.
14. The method of claim 11 and wherein the providing at least one of the inventoried sendings, said providing initiated by a trigger further comprises triggering the trigger linked to an activity.
15. The method of claim 11 and wherein the providing of at least one of the inventoried sendings is prioritized.
16. The method of claim 11 and wherein the method further comprises supplying sendings for posting on an internet website.
17. The method of claim 11 and further comprising at least one of: enabling a user to pick a sending from a plurality of sendings to pick from; enabling a user to call up a sending; identifying a sending; enabling employment of user-selected sendings; and, enabling a user to configure operation.
18. The method of claim 17 and wherein identifying a sending further comprises identifying a feature that can be employed absent any specialized hardware and/or programming at the sending device.
19. The method of claim 17 and wherein identifying a sending further comprises identifying a requested sending.
20. The telephone system of claim 17 and wherein enabling a user to pick a sending further comprises at least one of: enabling a user to pick a type of sending and enabling a user to pick a class of sending.
Type: Application
Filed: Dec 28, 2011
Publication Date: May 24, 2012
Inventor: Christopher Guy Williams (Spokane, WA)
Application Number: 13/374,419
International Classification: H04M 11/06 (20060101);