WO2012122494A1 - Systèmes et procédés de communication - Google Patents

Systèmes et procédés de communication Download PDF

Info

Publication number
WO2012122494A1
WO2012122494A1 PCT/US2012/028531 US2012028531W WO2012122494A1 WO 2012122494 A1 WO2012122494 A1 WO 2012122494A1 US 2012028531 W US2012028531 W US 2012028531W WO 2012122494 A1 WO2012122494 A1 WO 2012122494A1
Authority
WO
WIPO (PCT)
Prior art keywords
user
communication
voicemail
interaction history
interaction
Prior art date
Application number
PCT/US2012/028531
Other languages
English (en)
Inventor
Donald R. Steul
Henry M. VOGEL
Brian J. Chisholm
Kavinder S. DHALIWAL
Yongjiang ZHANG
Ravichandran RAJAMIYER
Jeffrey T. BECKER
Aleksandar Dukic
Original Assignee
Apptera, Inc.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Apptera, Inc. filed Critical Apptera, Inc.
Publication of WO2012122494A1 publication Critical patent/WO2012122494A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/14—Session management
    • H04L67/146—Markers for unambiguous identification of a particular session, e.g. session cookie or URL-encoding
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/535—Tracking the activity of the user
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/75—Indicating network or usage conditions on the user display

Definitions

  • the present disclosure generally relates to data processing techniques and, more specifically, to communication systems and methods.
  • FIG. 1 illustrates an example environment in which the systems and methods discussed herein can be applied.
  • FIG. 2 is a block diagram illustrating various components of an example mobile device.
  • FIG. 3 is a block diagram illustrating various components of an example server.
  • Fig. 4 is a flow diagram illustrating an embodiment of a procedure for launching a communication application.
  • Fig. 5 is a flow diagram illustrating an embodiment of a procedure for initiating a communication session with another device.
  • Fig. 6 is a flow diagram illustrating an embodiment of a procedure for maintaining an interaction history between users.
  • Fig. 7 is a flow diagram illustrating an embodiment of a procedure for establishing a communication session between two devices.
  • FIGs. 8A and 8B illustrate a flow diagram of an embodiment of a procedure for configuring a communication application.
  • Fig. 9 is a flow diagram illustrating an embodiment of a procedure for initiating a communication session with another user.
  • Fig. 10 is a flow diagram illustrating an embodiment of a procedure for prioritizing voice calls and associating additional information with a voice call.
  • Fig. 11 is a flow diagram illustrating an embodiment of a procedure for configuring a merchant communication account.
  • Fig. 12 is a flow diagram illustrating an embodiment of a procedure for handling merchant calls during non-business hours.
  • Fig. 13 is a flow diagram illustrating an embodiment of a procedure for handling merchant calls during business hours.
  • Figs. 14A - 14D illustrate example screen displays generated during a particular communication session between a customer and a merchant.
  • Fig. 15 is a flow diagram illustrating an embodiment of a procedure for mobile purchasing and service enrollment.
  • the systems and methods described herein allow users to communicate with one another using, for example, mobile devices. Users may communicate via a data channel and/or a voice channel. In certain situations, two users may communicate via a data channel and a voice channel simultaneously.
  • the described systems and methods allow users to assign a priority to, and associate other data with, a voice call, thereby allowing the voice call recipient to understand the nature of the call prior to answering the call. Additionally, the systems and methods described herein allow merchants to automatically provide offers, forms, and other merchant-related information to customers during business and non-business hours.
  • a "user” is also referred to as a
  • caller an "initiator” or a “recipient”.
  • a mobile device such as a cellular phone, smart phone, and the like.
  • the systems and methods discussed herein can be used with any type of device capable of performing the described procedures and operations.
  • FIG. 1 illustrates an example environment 100 in which the systems and methods discussed herein can be applied.
  • Environment 100 illustrates two mobile devices 102 and 104 capable of communicating via a cellular communication network 106 and/or a data communication network 108.
  • Cellular communication network 106 may utilize any communication protocol and any number of components, systems and communication links.
  • Data communication network 108 may utilize any communication protocol and any type of communication medium.
  • data communication network 108 is the Internet.
  • data communication network 108 is a combination of two or more networks coupled to one another.
  • a server 110 is coupled to data communication network 108 and capable of communicating with mobile devices 102 and 104.
  • Server 110 is capable of performing various communication-related functions as described herein.
  • Server 110 communicates with various data sources and data storage devices to obtain information, such as data source 112 and user/device data 114.
  • Example information includes user profile data, user configuration settings, interaction histories between various users, and the like.
  • An advertising management system 116 is coupled to data communication network 108, user/device data 114, and an advertisement database 118.
  • Advertising management system 116 performs various advertisement-related functions, such as creating and editing advertisements, selection and ranking of advertisements based on various factors, and communicating advertisements to server 110 and/or mobile devices 102 and 104.
  • Advertisement database 118 contains various advertisements and information associated with those advertisements. Advertisement database 112 may also contain campaign history data used for reporting, generating new advertising campaigns, and so forth. Additional details regarding the communication of advertisements are provided below.
  • FIG. 2 is a block diagram illustrating various components of example mobile device 102.
  • Mobile device 102 includes a communication module 202, a processor 204, and a memory 206.
  • Communication module 202 allows mobile device 102 to communicate with other devices, such as communication networks, other mobile devices, computer systems, and so on.
  • Processor 204 executes various instructions to implement the functionality provided by mobile device 102.
  • Memory 206 stores these instructions as well as other data used by processor 204 and other modules contained in mobile device 102.
  • Mobile device 102 also includes a visual display 208 that presents information to a user of the mobile device.
  • visual display 208 is a touch screen that is capable of displaying information as well as receiving input from the device user.
  • Mobile device 102 has a basic dialer application 210 as well as an enhanced communication application 212.
  • basic dialer application 210 is provided by the manufacturer of the device and includes basic voice call functions, such as initiating a voice call and searching for phone numbers in a contact list.
  • Enhanced communication application 212 provides additional features not contained in basic dialer application 210. For example, enhanced
  • communication application 212 may support communication between mobile device 102 and another mobile device having a similar enhanced communication application.
  • the additional features may include simultaneous data
  • the additional features also include associating a call priority or other information with a voice call and communicating that priority or information to a call recipient.
  • Other features supported by enhanced communication application 212 are discussed herein.
  • Mobile device 102 also includes a user input mechanism 214, such as buttons, switches, touch pads, touch screens and the like. User input mechanism 214 may also receive voice commands or any other input/command from a user of mobile device 102. Mobile device 102 stores various user input mechanism 214, such as buttons, switches, touch pads, touch screens and the like. User input mechanism 214 may also receive voice commands or any other input/command from a user of mobile device 102. Mobile device 102 stores various
  • information cache 216 is integrated with memory 206.
  • Fig. 3 is a block diagram illustrating various components of example server 110.
  • Server 110 may be used to perform various procedures, such as those discussed herein.
  • the components shown in Fig. 3 can function as a server, as described herein, or any other computing entity.
  • Server 110 can be any of a wide variety of computing devices, such as a desktop computer, a notebook computer, a server computer, a handheld computer, and the like.
  • Server 110 includes one or more processor(s) 302, one or more memory device(s) 304, one or more interface(s) 306, one or more mass storage device(s) 308, and one or more Input/Output (I/O) device(s) 310, all of which are coupled to a bus 312.
  • Processor(s) 302 include one or more processors or controllers that execute instructions stored in memory device(s) 304 and/or mass storage device(s) 308.
  • Processor(s) 302 may also include various types of computer-readable media, such as cache memory.
  • Memory device(s) 304 include various computer-readable media, such as volatile memory (e.g., random access memory (RAM)) and/or nonvolatile memory (e.g., read-only memory (ROM)). Memory device(s) 304 may also include rewritable ROM, such as Flash memory.
  • volatile memory e.g., random access memory (RAM)
  • ROM read-only memory
  • Memory device(s) 304 may also include rewritable ROM, such as Flash memory.
  • Mass storage device(s) 308 include various computer readable media, such as magnetic tapes, magnetic disks, optical disks, solid state memory (e.g., Flash memory), and so forth. Various drives may also be included in mass storage device(s) 308 to enable reading from and/or writing to the various computer readable media. Mass storage device(s) 308 include removable media and/or non-removable media.
  • I/O device(s) 310 include various devices that allow data and/or other information to be input to or retrieved from server 110.
  • Example I O device(s) 310 include cursor control devices, keyboards, keypads, microphones, monitors or other display devices, speakers, printers, network interface cards, modems, lenses, charge-coupled devices (CCDs) or other image capture devices, and the like.
  • Interface(s) 306 include various interfaces that allow server 110 to interact with other systems, devices, or computing environments.
  • Example interface(s) 306 include any number of different network interfaces, such as interfaces to local area networks (LANs), wide area networks (WANs), wireless networks, and the Internet.
  • LANs local area networks
  • WANs wide area networks
  • wireless networks such as Wi-Fi
  • Bus 312 allows processor(s) 302, memory device(s) 304, interface(s) 306, mass storage device(s) 308, and I/O device(s) 310 to communicate with one another, as well as other devices or components coupled to bus 312.
  • Bus 312 represents one or more of several types of bus structures, such as a system bus, Peripheral Component Interconnect (PCI) bus, IEEE 1394 bus, Universal Serial Bus (USB), and so forth.
  • PCI Peripheral Component Interconnect
  • USB Universal Serial Bus
  • programs and other executable program components are shown herein as discrete blocks, although it is understood that such programs and components may reside at various times in different storage components of server 110, and are executed by processor(s) 302.
  • the systems and procedures described herein can be implemented in hardware, or a combination of hardware, software, and/or firmware.
  • one or more application-specific integrated circuits (ASICs) can be programmed to carry out one or more of the systems and procedures described herein.
  • Fig. 4 is a flow diagram illustrating an embodiment of a procedure 400 for launching a communication application.
  • a device user launches a communication application on the device at 402, such as enhanced communication application 212 discussed above with respect to Fig. 2.
  • the communication application identifies a most recently displayed screen format (e.g., the display format when the user last terminated the application) at 406. That screen format is used as the starting screen format during the next launch of the communication application.
  • the communication application displays the last contact with which the user communicated as well as an interaction history associated with that last contact.
  • the communication application requests information from the device user via a registration screen at 408. This information may include the user's name, phone number, email address, mailing address, display preferences, communication preferences, and so forth.
  • the communication application receives the requested information and
  • a server such as server 110 discussed above with respect to Fig. 1, at 410.
  • the server registers the device and the user based on a phone number associated with the device at 412. After the server completes registration of the user, it sends a registration confirmation message to the communication application executing on the device. Upon receipt of this registration confirmation message at 414, the communication application displays a user profile screen (or other display page) on the device at 416.
  • Fig. 5 is a flow diagram illustrating an embodiment of a procedure 500 for initiating a communication session with another device.
  • the procedure begins when a user (also referred to as “the initiator") selects a person to contact (also referred to as “the recipient") via a communication application executing on a first device (e.g., the initiator's device) at 502.
  • the initiator selects a person to contact (also referred to as "the recipient”
  • the communication application executing on a first device (e.g., the initiator's device) at 502.
  • the communication application identifies a second device associated with the recipient via a web-based server or other system at 504.
  • the web-based server maintains information about other devices using similar communication applications.
  • the web-based server is capable of determining whether the second device has a similar communication application at 506.
  • the communication application first determines whether information associated with the second device is already cached on the first device.
  • the communication application may still retrieve updated recipient information from the web-based server, or the communication application may use the information cached on the first device.
  • the first device displays a user profile and interaction history associated with the recipient at 510.
  • the user profile may include a picture of the recipient, a geographic location associated with the recipient based on the recipient's phone number, and the like. Additionally, the first device presents the initiator with options to communicate with the recipient by voice call or text message, also at 510.
  • the first device establishes a communication session with the second device at 512.
  • the first device identifies a display page to present to the user of the first device at 514. This display page is selected by the user of the second device, thereby allowing the user of the second device to control what is displayed on the first device when the first and second devices are
  • the first device then identifies a status associated with the second device, such as busy, on another call, or available at 516.
  • a status associated with the second device is determined before a communication session is established.
  • the first device displays the status information and available communication options using the identified display page at 518. For example, if the status is
  • the communication options may include initiating a voice call, sending a text message, and the like.
  • Fig. 6 is a flow diagram illustrating an embodiment of a procedure 600 for maintaining an interaction history between users.
  • a server e.g., a web-based server
  • the first and second devices exchange voice data, text data and other information during the communication session at 604.
  • the server records an interaction history between the two devices, including both data and voice interactions at 606.
  • the interaction history may include an identification of the data communicated, the devices or users involved in the communication, date, time, and other information associated with the communication session.
  • the first device and/or the second device may retrieve the interaction history from the server for display on the device at 608. For example, if a first user establishes a communication session with a second user, the communication application executing on the first user's device may retrieve interaction history for previous communication sessions with the same two users. This allows the first user to see previous communications with the second user and information about those communications. Additionally, the first device and/or the second device may cache all or a portion of the retrieved interaction history information for faster retrieval at a future time at 610. For example, a device may cache interaction history information associated with commonly called friends/contacts.
  • each interaction event is tagged with additional information, such as a contact identifier (e.g., name and/or phone number), start date/time, duration of communication session (if appropriate), and a current status.
  • a contact identifier e.g., name and/or phone number
  • start date/time e.g., start date/time
  • duration of communication session if appropriate
  • current status e.g., current status
  • Incoming and outgoing voice calls including voicemail messages with transcripts of the messages. Related information may include the day and time the message was sent or received, a caller ID associated with the caller, and the length of the voicemail message.
  • the interaction status indicates whether a voicemail message was an incoming voicemail message or an outgoing voicemail message.
  • Incoming and outgoing text messages such as SMS, MMS and IM messages.
  • the interaction status indicates whether the text message was an incoming text message or an outgoing text message.
  • Offers such as coupons, daily specials, and special events.
  • the interaction status will indicate whether the coupon is available, expired, or already used.
  • the interaction status will indicate whether the survey has been received. If a response to the survey is generated, the interaction status may also indicate the response.
  • Third party network history such as social media entries/communications (e.g., Facebook® updates and Tweets on Twitter®), online reservation systems, online merchant reviews, online restaurant reviews, and so forth.
  • social media entries/communications e.g., Facebook® updates and Tweets on Twitter®
  • online reservation systems e.g., Facebook® updates and Tweets on Twitter®
  • online merchant reviews e.g., online restaurant reviews, and so forth.
  • Fig. 7 is a flow diagram illustrating an embodiment of a procedure 700 for establishing a communication session between two devices.
  • a user the communication initiator selects a person to contact (the
  • the first device communicates information regarding the initiator to a server, such as a web-based server, at 704.
  • the first device may communicate with the server using any communication medium and any communication protocol.
  • the first device may communicate with the server via a data communication network, a cellular communication network, and so forth.
  • the first device communicates information associated with the first device (e.g., phone number and user profile information) as well as information identifying the communication recipient and, if applicable, a message to communicate to the recipient.
  • the server Upon receipt of the information from the communication initiator, the server identifies a user profile associated with a second device used by the communication recipient at 706.
  • the user profile may include a phone number, IP (Internet Protocol) address, or other unique identifier associated with the second device.
  • the server determines a current status associated with the second device at 708. In a particular implementation, the current status associated with the second device is determined before a communication session is established. In one embodiment, the server communicates a "push
  • the push notification may also include a message from the initiator.
  • the server determines a display page to present to the initiator via the first device at 710.
  • the display page presented on the first device is defined (or selected) by the second user.
  • the second user controls the particular display page (and corresponding information on that page) shown to the initiator on the first device.
  • the server communicates the selected display page and the current status of the second device to the first device at 712. In particular embodiments, the current status is contained within (or inserted into) the selected display page.
  • the first device displays the current status of the second device using the identified display page at 714.
  • the first device may also display various options to the communication initiator, such as initiating a voice call, sending a text message, and the like.
  • Figs. 8A and 8B illustrate a flow diagram of an embodiment of a procedure 800 for configuring a communication application.
  • a user downloads and installs a communication application into a device, such as a mobile device, at 802 of Fig. 8A.
  • the user executes (e.g., launches) the communication application on the device at 804, causing the communication application to display a registration screen pre-populated with the user's phone number and other information, such as user name, geographic location, and the like, at 806.
  • the user may enter additional information on the registration screen to supplement the pre-populated information.
  • the user submits the registration information at 808 by activating a "submit” button or similar element displayed on the device.
  • the registration information is then communicated to a web-based server, also at 808.
  • the server generates a verification message at 810 to ensure that the registration information was received from the identified device and not generated by a user or device "pretending" to be the identified device (e.g., an unauthorized user generating false registrations). If the verification is not successful at 812, the server discards the received registration information and cancels the registration of the device at 814. If the verification was successful at 812, the communication application synchronizes contact information stored in the device with the web- based server at 816.
  • the user continues configuration of the communication application by uploading a first image to the device for use with their default display page at 818 of Fig. 8B.
  • the user also defines a second display page containing different information than the default display page at 820.
  • the user identifies one or more contacts (e.g., from contact information already stored in the device) to receive the second display page during a communication session at 822.
  • the second display page and its associated contacts are synchronized with the web-based server at 824.
  • the user may also define additional display pages and associate other contacts with those display pages. Any contact not associated with a specific display page will be associated with the default display page.
  • the user may also associate specific display pages with a user status or device status. For example, the user may identify a first display page to present when the user is available to communicate, but identifies a different display page for presentation when the user is busy or otherwise unavailable. Additionally, the user can associate specific display pages with different parameters, such as time of day, day of week, geographic location (e.g., at home, at work, or another location), and the like.
  • Particular embodiments allow a user to provide a variety of user profile information and other settings, such as user contact and personal information, and current status (e.g., driving, in a meeting, on a call, eating dinner, etc.) - this status information can be set manually or automatically (e.g., via the user's calendar or other application).
  • Other user profile information includes payment information, contact associations, and so forth.
  • the user can define a custom audio ring-back tone that is played to the person who is calling the user.
  • the user can define a default audio ring-back tone as well as one or more specific audio ring-back tones associated with specific contacts or contact groups.
  • a user can also set a ringtone to be played on a contact's mobile device when the user calls that contact. This ringtone overrides the default ringtone set by the contact and may indicate an urgency or priority associated with the call (such as a siren sound for urgent calls).
  • Fig. 9 is a flow diagram illustrating an embodiment of a procedure 900 for initiating a communication session with another user.
  • a user executes a communication application on a first device at 902.
  • the communication application obtains a status associated with at least a portion of the user's contacts (e.g., from a web-based server discussed herein) at 904.
  • the communication application displays the status of the user's contacts for which status information was obtained at 906.
  • the user selects one of the contacts to initiate a communication session at 908.
  • the communication application retrieves (e.g., from a web-based server) a display page defined by the selected contact from the first device's cache at 910. Alternatively, the display page may be retrieved from a web-based server or other data source.
  • the display page includes the contact's geographic location, which may be displayed on a map or presented textually (e.g., I'm at the coffee shop at 5th and Maple).
  • the communication application displays on the first device a map showing the geographic location of both the user and the selected contact at 912.
  • the map may show a driving route, distance, and travel time between the user and the selected contact.
  • the user may choose to share their geographic location with the contact via the communication application at 914. If the user chooses to share their location, the communication application communicates the user's geographic location (determined, for example, by a GPS contained in the first device) to the contact's device. Additionally, the user may send a text message or other information to the contact's device for display to the contact.
  • a communication application on the contact's device retrieves a display page defined by the user from the contact device's cache (or from the web-based server) at 916. The communication application on the contact's device then displays the user's text message as well as a map showing the geographic location of both the user and the contact.
  • Fig. 10 is a flow diagram illustrating an embodiment of a procedure 1000 for prioritizing voice calls and associating additional information with a voice call.
  • Communication applications executing on a first device and a second device establish a communication session between the two devices at 1002.
  • the communication session is established and maintained with the support of a web-based server or similar system coupled to both devices.
  • a user of the first device initiates a voice call function within the communication application at 1004.
  • the user of the first device identifies a priority associated with the voice call at 1006, such as a high priority (or an urgent priority).
  • the user of the first device may also provide additional information associated with the call at 1008, such as the reason for the call or the reason for the priority associated with the call.
  • the web-based server determines at 1010 an optimal voice channel method; i.e., the best communication method for establishing a voice-based communication link between the two devices.
  • the communication application on the first device initiates an appropriate voice channel (based on the server's determination) between the first device and the second device at 1012.
  • the second device receives the voice call (or voice channel setup request) from the first device and displays the priority associated with the voice call as well as any additional data associated with the voice call at 1014.
  • the user of the second device then decides whether to accept the received voice call at 1016.
  • the priority associated with the voice call can be represented in a variety of ways, such as a text notice "Urgent Call”, a red “Accept Urgent Call” button, a flashing "Accept Call” button, an audible sound indicating a priority call, and the like.
  • different color codes are used to visually indicate a call priority, such as red for urgent calls, yellow for important calls, and green for normal calls.
  • Fig. 11 is a flow diagram illustrating an embodiment of a procedure 1100 for configuring a merchant communication account.
  • a merchant establishes an account via a web-based server or other system at 1102.
  • Establishing the account includes, for example, defining a profile associated with the merchant's business, uploading photos related to the merchant's business
  • the merchant uploads a first image to the web-based server for use in the merchant's default display page at 1104.
  • the merchant also uploads additional images to the web-based server for use in other display pages or to provide more images for a customer to scroll through on the default display page at 1106.
  • the merchant also defines business hours, business location
  • the merchant is a restaurant or other business that accepts reservations from customers.
  • the merchant activates a reservation request form and defines when to present that form to customers calling or otherwise communicating with the merchant at 1110. Additionally, the merchant can define customer offers, daily specials, coupons, and other incentives for presentation to customers contacting the merchant at 1112.
  • a merchant may define other forms that automate the interaction process with the merchant's customers (and potential customers).
  • Example forms include delivery requests, a product/service order form, an offsite service request, and the like. These forms may capture the customer's name, phone number, address, email address, payment information, and other information automatically and pre-fill those portions of the form, thereby simplifying the form- filling procedure for the customer.
  • Fig. 12 is a flow diagram illustrating an embodiment of a procedure 1200 for handling merchant calls during non-business hours.
  • a mobile device user calls a merchant during non-business hours by activating a phone number link (or other button/link) in a mobile search application, such as a web browser application, at 1202.
  • a mobile search application such as a web browser application
  • a communication application is launched on the mobile device at 1204.
  • the communication application determines whether information regarding the merchant is cached on the mobile device at 1206. If the information is not cached at 1208, the communication application obtains the merchant's profile information from a web-based server or other system at 1210.
  • the communication application displays an offer, form or other information associated with the merchant (e.g., the information obtained from the cache or from the web-based server) on the mobile device at 1212.
  • the user responds to the offer, completes the form or requests additional information via the communication application at 1214.
  • the displayed information includes a reservation request form that allows the mobile device user to request a dining reservation at a particular day and time, and for a particular number of people.
  • the merchant can quickly respond to multiple reservation requests using the merchant's communication application. Thus, rather than attempting to call each customer who submitted a reservation request, the merchant can respond by clicking a "confirm
  • reservation button or similar button/link in the communication application.
  • the customer then receives a text message in their own communication application confirming the reservation.
  • the customer's communication application may include a reservation status indicator (e.g., reservation request sent to merchant, reservation request received by merchant, and reservation confirmed).
  • the reservation status indicator may be displayed as a visual indicator/icon, as a textual entry, or any other graphical or audio indicator.
  • a status indicator associated with the reservation request shown in the interaction history is changed to "reservation confirmed”.
  • a new entry may be inserted into the interaction history indicating the confirmation of the reservation.
  • An example reservation request form and confirmation response from the merchant are shown in Figs. 14A-14B.
  • Fig. 13 is a flow diagram illustrating an embodiment of a procedure 1300 for handling merchant calls during business hours.
  • a mobile device user calls a merchant during business hours by activating a phone number link (or other button/link) in a mobile search application at 1302.
  • a phone number link or other button/link
  • the communication application is then launched on the mobile device at 1304.
  • the communication application establishes a communication session between the user and the merchant at 1306. If the merchant is busy at 1308, the merchant's communication application provides an offer, form or other information to the mobile device user at 1312. Additionally, the user may receive an indication that the merchant is unable to currently answer the user's call. If, when the user initiates the call, the merchant is not busy at 1308, the merchant's
  • the communication application When a customer interacts with a merchant, the communication application automatically detects that the communication recipient is a merchant and tags that contact as a "merchant contact" in the customer's contact list. This allows the user to have their own “merchant contact list", which can be viewed separately from the user's personal contacts.
  • the user's communication application maintains the interaction history with each merchant, including past orders, past reservations, and so forth. This interaction history allows a user to easily locate and repeat previous orders or purchases.
  • Figs. 14A - 14D illustrate example screen displays generated during a particular communication session between a customer and a merchant.
  • Fig. 14A shows an initial merchant display page after the customer has selected the merchant from a contact list or activated a link/button in a mobile search application.
  • This display page shows a default image as well as a "special offer" button.
  • the display page includes a scroll function that allows a customer to navigate through multiple images.
  • the images can be arranged in any manner such that the user scrolls vertically, horizontally, or in any other orientation.
  • the multiple images are arranged in a manner that simulates a rotating carousel of images.
  • the additional images may include pictures of the restaurant, pictures of favorite menu items, a picture of the menu, and so forth.
  • Fig. 14B shows a reservation form that allows the customer to request a reservation at the restaurant.
  • Fig. 14C shows the merchant display page after the customer's reservation request has been confirmed. The reservation confirmation is shown as an entry in the interaction history displayed in the bottom portion of the display page.
  • Fig. 14D shows an updated merchant display page after the customer has received a coupon from the merchant. The interaction history is updated to include the recently received coupon.
  • Fig. 15 is a flow diagram illustrating an embodiment of a procedure 1500 for mobile purchasing and service enrollment.
  • a user purchases a product or service through the communication application on a first device (e.g., the user's mobile device) at 1502.
  • the purchase may be the result of an advertisement displayed on the first device or as a result of a contact initiated by the user with the merchant.
  • the user is presented with an offer to receive additional information about the purchased product or service at 1504. This additional information includes future product updates, product operating tips, recall notices, periodic newsletter, and additional products or services that complement the originally purchased product or service.
  • the communication application on the first device requests a second verification from the user at 1508, which may be referred to as "double verification".
  • the communication application may display instructions requesting the user to touch a specific button or a sequence of buttons displayed on the first device.
  • the communication application may ask the user to speak a phrase that is displayed on the first device.
  • the spoken phrase is recorded and stored in the first device and/or communicated to a server for storage.
  • the user is enrolled to receive additional information about the purchased product or service at 1512. If the user does not provide the requested second verification, or provides incorrect verification (e.g., does not press the proper buttons in the requested sequence), the user is not enrolled to receive additional information.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Hardware Design (AREA)
  • General Engineering & Computer Science (AREA)
  • Telephonic Communication Services (AREA)

Abstract

L'invention porte sur des systèmes et sur des procédés de communication qui prennent en charge une communication entre de multiples dispositifs. Dans certains modes de réalisation, un procédé déclenche une session de communication entre un premier dispositif et un second dispositif par l'intermédiaire d'un serveur. Le procédé identifie un premier utilisateur associé au premier dispositif et identifie un second utilisateur associé au second dispositif. Il est possible d'accéder à un historique d'interaction entre le premier utilisateur et le second utilisateur par le serveur et de communiquer celui-ci au premier dispositif pour un affichage sur le premier dispositif.
PCT/US2012/028531 2011-03-09 2012-03-09 Systèmes et procédés de communication WO2012122494A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US201161451067P 2011-03-09 2011-03-09
US61/451,067 2011-03-09

Publications (1)

Publication Number Publication Date
WO2012122494A1 true WO2012122494A1 (fr) 2012-09-13

Family

ID=46798575

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2012/028531 WO2012122494A1 (fr) 2011-03-09 2012-03-09 Systèmes et procédés de communication

Country Status (1)

Country Link
WO (1) WO2012122494A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2016205888A1 (fr) * 2015-06-24 2016-12-29 Vonex Ltd Système et procédé permettant d'établir des communications sur une pluralité de plateformes de communication

Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20030187990A1 (en) * 2002-03-29 2003-10-02 Knauerhase Robert C. Intelligent scheme for seamlessly maintaining communication sessions while switching devices
US20040221309A1 (en) * 2002-06-18 2004-11-04 Microsoft Corporation Shared online experience history capture and provision system and method
US20080019522A1 (en) * 2006-06-21 2008-01-24 Motorola, Inc. Method For Managing A Communication Session in a Communication Network
US20090061827A1 (en) * 2007-08-29 2009-03-05 Bulgin Scott E Voicemail system for a handheld device
US20090305679A1 (en) * 2008-06-04 2009-12-10 Pantech & Curitel Communications, Inc. Mobile communication terminal having a direct dial function using call history and method for performing the function
US7711848B2 (en) * 2006-06-15 2010-05-04 Oracle International Corporation System using session initiation protocol for seamless network switching in a media streaming session
US20100130128A1 (en) * 2008-11-24 2010-05-27 Verizon Data Services Llc Social interaction tracking

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20030187990A1 (en) * 2002-03-29 2003-10-02 Knauerhase Robert C. Intelligent scheme for seamlessly maintaining communication sessions while switching devices
US20040221309A1 (en) * 2002-06-18 2004-11-04 Microsoft Corporation Shared online experience history capture and provision system and method
US7711848B2 (en) * 2006-06-15 2010-05-04 Oracle International Corporation System using session initiation protocol for seamless network switching in a media streaming session
US20080019522A1 (en) * 2006-06-21 2008-01-24 Motorola, Inc. Method For Managing A Communication Session in a Communication Network
US20090061827A1 (en) * 2007-08-29 2009-03-05 Bulgin Scott E Voicemail system for a handheld device
US20090305679A1 (en) * 2008-06-04 2009-12-10 Pantech & Curitel Communications, Inc. Mobile communication terminal having a direct dial function using call history and method for performing the function
US20100130128A1 (en) * 2008-11-24 2010-05-27 Verizon Data Services Llc Social interaction tracking

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2016205888A1 (fr) * 2015-06-24 2016-12-29 Vonex Ltd Système et procédé permettant d'établir des communications sur une pluralité de plateformes de communication
US10554815B2 (en) 2015-06-24 2020-02-04 Vonex Ltd. System and method for establishing communications over a plurality of communications platforms
RU2721825C2 (ru) * 2015-06-24 2020-05-22 Вонекс Лтд Система и способ установления связи по множеству платформ связи
US10887460B2 (en) 2015-06-24 2021-01-05 Vonex Ltd System and method for establishing communications over a plurality of communications platforms

Similar Documents

Publication Publication Date Title
US9119054B2 (en) Communication systems and methods
US10341490B2 (en) Real-time communications-based internet advertising
US9794422B2 (en) Method and apparatus for content presentation in association with a telephone call
US9838541B2 (en) Method and apparatus for content presentation in association with a communication connection
US10198741B2 (en) Method and apparatus for content presentation in association with a communication connection
US9578474B2 (en) Method and apparatus for content presentation in association with a telephone call
US8345835B1 (en) Systems and methods for visual presentation and selection of IVR menu
US8687777B1 (en) Systems and methods for visual presentation and selection of IVR menu
US8929517B1 (en) Systems and methods for visual presentation and selection of IVR menu
US8406388B2 (en) Systems and methods for visual presentation and selection of IVR menu
US8681951B1 (en) Systems and methods for visual presentation and selection of IVR menu
US8817959B1 (en) System for handling messages and distributing information
WO2021205240A1 (fr) Différents types de services d'appels textuels, applications centralisées de dialogue en direct et différents types de supports de communication pour l'appelant et l'appelé ou les participants à la communication
JP2015517286A (ja) マルチモード非同期通信の装置及び方法
US9667810B1 (en) Method and apparatus for content presentation in association with a telephone call
US20190082043A1 (en) Systems and methods for visual presentation and selection of ivr menu
US8879703B1 (en) System method and device for providing tailored services when call is on-hold
US20170289332A1 (en) Systems and Methods for Visual Presentation and Selection of IVR Menu
US9143884B2 (en) Enhancing information delivery to a called party
US11394822B2 (en) Incentivising answering call in smartphone lockscreen
US11394824B2 (en) Adjusting presentation on smart phone lockscreen of visual content associated with metadata of incoming call
US11451659B2 (en) Dynamic rewardable activity value determination and allocation
US11394821B2 (en) Curated search of entities from dial pad selections
US20120295593A1 (en) Method and system for playing a media file and targeted advertisements upon receipt of a phone call
WO2012122494A1 (fr) Systèmes et procédés de communication

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 12754840

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 12754840

Country of ref document: EP

Kind code of ref document: A1