|Publication number||US7512098 B2|
|Application number||US 11/503,301|
|Publication date||Mar 31, 2009|
|Filing date||Aug 14, 2006|
|Priority date||Aug 17, 2000|
|Also published as||US7092370, US20020057678, US20060276196, WO2002015519A2, WO2002015519A3|
|Publication number||11503301, 503301, US 7512098 B2, US 7512098B2, US-B2-7512098, US7512098 B2, US7512098B2|
|Inventors||Yuen Jun Jiang, Hisso M. Chang|
|Original Assignee||Roamware, Inc.|
|Export Citation||BiBTeX, EndNote, RefMan|
|Patent Citations (110), Non-Patent Citations (39), Referenced by (37), Classifications (54), Legal Events (6)|
|External Links: USPTO, USPTO Assignment, Espacenet|
This is a Continuation of application Ser. No. 09/932,439 filed Aug. 16, 2001 now U.S. Pat. No. 7,092,370. The disclosure of the prior application is hereby incorporated by reference herein in its entirety.
This application claims priority from the following U.S. Provisional Patent Applications: Ser. No. 60/226,255, entitled Method and Apparatus for Integrated Data Management, filed Aug. 17, 2000; Ser. No. 60/226,363, entitled Method and Apparatus for Integrated Data Management, filed Aug. 18, 2000; Ser. No. 60/226,855, entitled Method and Apparatus for Integrated Data Management, filed Aug. 22, 2000; Ser. No. 60/242,730, entitled Wireless Location Proxy, filed Oct. 23, 2000; Ser. No. 60/253,978, entitled Wireless Device Registration, filed Nov. 29, 2000; and Ser. No. 60/261,572 entitled Smart Wireless Applications, filed Jan. 12, 2001, all of which are incorporated herein by reference.
Disclosed embodiments of the invention are in the field of wireless communication devices and associated software applications.
Access to data and services through electronic networks has become a necessary part of everyday personal and business life. Especially since the Internet became widely accessible, many people increasingly rely on accessing Internet data and services through a variety of devices. Businesses, or enterprises, also use networks to make specific data and services available to employees, partners, and customers. Traditionally, the devices used to access networks were wired to the network. Examples include wired computers and wired telephones. Increasingly, however, people want to be able to access network data and services anywhere using portable, wireless devices such as wireless telephones and hand-held personal data assistants (PDAs). Enterprises now seek the ability to provide wireless access to data and services that is just as complete and easy as wired access. The arrival of wireless Internet telephone devices makes it possible to integrate voice and data services that combine the advantages of either access method. Integration of multiple communication channels such as voice and wireless data has, however, proven challenging.
Traditional multi-channel integration approaches to, for example, customer relations management (CRM), only involve computer telephone integration/interactive voice response (CTI/IVR), web, email, chat, and voice over Internet protocol (IP). Existing integration approaches have the disadvantage of sharing multiple data sources that at best facilitate one channel process (e.g., voice channel with screen pops for a call agent). The lack of channel integration in traditional approaches hinders a satisfactory solution to wireless access to enterprise data and applications, or services.
Without effective integration, accessing a wireless applications protocol (WAP) site for the first time is difficult for several reasons. A standard web browser with a keyboard makes it relatively easy to locate a new web site or directly enter a uniform resource locator (URL). Mobile wireless devices have limited input and user interface capability, however, compared to a computer with a standard web browser. A WAP telephone, for example, doesn't easily allow the typical hyperlinking, searching, bookmarking, or URL entry required to effectively navigate. This creates a significant barrier to the use of a WAP site.
Another disadvantage of traditional techniques for accessing WAP sites is that access to homepages is complicated and inefficient. Typically, homepages in the WAP/HDTP world are controlled by the carrier or must to be manually entered by the user on a wireless device. In the former case, which is characteristic in the United States, to go to a URL for an enterprise site not on carrier's homepage, the user must go through the inconvenience of finding the “goto place” and entering the URL. To avoid this, a large enterprise (e.g. America Online™) might have to pay to be on the carrier's homepage. In the latter case, the user has to enter the URL using the awkward wireless device configuration. In either case, a new URL change results in an awkward data entry process.
Another disadvantage of traditional techniques for accessing WAP sites is inferior device location technology. For many applications, the current location of the wireless device is important. For example, map services or yellow page services may be keyed to the location of the wireless user in order to provide only pertinent information. While multiple location technologies exist, not all are expected to be available and operational in every network, for every device, and at each location within the network. Furthermore, the position measurements retrieved from the location networks may require further processing to obtain the desired data format or related information (e.g., directions to a site). Besides location processing, there is also a need to obtain proper authorization for locating a mobile device. Current approaches lack the ability to mediate among network entities, preferences, authorizations, and related functions.
Another disadvantage of traditional techniques for accessing WAP sites is a cumbersome method for handling sign-on processes for multiple, disparate applications. Some “single sign-on” services exist for providing a more uniform user experience when signing on to different applications. Existing single-sign-on services, however, typically impose a single authentication scheme to which all participating applications must conform.
Another disadvantage of traditional techniques for accessing WAP sites is the difficulty of moving between sites and managing the wireless sessions on each site. Existing systems may not allow a wireless user to maintain multiple sessions, including leaving one site for another, and returning to the original location at the original site.
Traditional techniques for accessing WAP sites rely on desktop-based or client-based cookie management. Some network-based cookie systems provide only cookie store and deliver mechanisms, but do not provide privacy management and security management. Current network-based cookie systems do not support multiple devices of the same user.
Current methods for registering a wireless device with a web site have several disadvantages. For example, to verify the phone number of the device entered by a user at registration, current methods send a short message service (SMS) message containing a code to the device. The user must enter the code in the registration process to continue. This verification process requires the user to switch between wireless device modes of WAP browsing and the wireless device's internal SMS message application. This increases the number of steps involved in completing the registration. On many wireless devices, the WAP browser will not maintain its state while the SMS message is being accessed. Therefore, the user must re-enter the WAP registration application to supply the code. Because use of the registration application in most cases will require the manual entry of a URL into a wireless device, re-entry involves repeating that manual entry, thus imposing a major barrier to use of the application.
Many wireless device users choose to receive messages and alerts of many different kinds on their devices. Existing wireless alert systems usually integrate the delivery of alerts with the generation of alerts. The delivery mechanism is normally one-way based and does not deal with two-way based actionable alerts. Furthermore, existing wireless alert systems do not handle escalation, which may be desirable when a message is not responded to within some time period.
The present invention overcomes the limitations of the prior art and provides additional benefits. A brief summary of some embodiments and aspects of the invention are first presented. Some simplifications and omissions may be made in the following summary; the summary is intended to highlight and introduce some aspects of the disclosed embodiments, but not to limit the scope of the invention. Thereafter, a detailed description of illustrated embodiments is presented, which will permit one skilled in the relevant art to make and use aspects of the invention. One skilled in the relevant art can obtain a full appreciation of aspects of the invention from the subsequent detailed description, read together with the Figures, and from the claims.
A system and method for integrating wireless data and voice calls that explores the advantages of both access methods are described. Embodiments include computer telephony integration/interactive voice response (CTI/IVR) integration including a wireless data and wireless voice channel that is wireless protocol independent. The CTI/IVR integration includes protocols with which voice calls can be triggered in a wireless data session and with which data sessions can be triggered by a voice call or by an actionable alert. Actionable data from the actionable alert allows the control of navigation from a wireless channel to a voice channel and vice versa during a communication session. Significantly, session data is shared between the voice channel and the data channel during a communication session. Voice data can trigger a data session in a push action or a pull action. Similarly, data can trigger a voice session in a push action or a pull action. One embodiment includes initiating a wireless applications protocol (WAP) session from a voice call, thus removing the problems that a traditional wireless user would have in navigating to a WAP site. A WAP session is presented to the user as a result of placing a normal telephone call. In one embodiment, initiating the wireless data WAP session comprises sending a message to a device, and receiving from the device a selection of a uniform resource locator (URL) within the message. In response to receiving the selection of the URL, a data session is initiated to a web server. In one embodiment, the message is a short message service (SMS) message.
One embodiment includes a central gateway through which wireless device users access multiple applications. These accessible applications could be hosted locally (in the same physical location or the same administration domain as the gateway), in the same Intranet behind the firewall, or anywhere on the Internet. In one embodiment, an apparatus architecture includes a tiered topology that supports large-scale, high performance, mission-critical wireless applications on a variety of devices. The method and system integrate various wireless applications with existing wireless network infrastructure, including wireless Internet infrastructure. The method and system further integrate multiple wired and wireless devices with the network, including providing a consistent user interface across multiple wireless devices. The method and system include numerous wireless applications that facilitate the wireless devices user's access to network services. One embodiment includes computer telephony integration/interactive voice response (CTI/IVR) integration. The CTI/IVR integration adds a wireless protocol independent wireless channel. The CTI/IVR integration presents actionable data that allows the control of navigation from a wireless channel to a voice channel and vice versa.
IVR applications typically run on an IVR system with appropriate hardware components that interface with wireline or wireless telephone networks.
The CTI/IVR service 500 controls navigation from a wireless data channel to a voice channel and vice versa. In one embodiment, the CTI/IVR service 500 operates where telephone calls can be triggered in a wireless data session. Automatic number identification (ANI) data, dialed number identification service (DNIS) data, and unique identifier (UID) data is sent to a workflow-based decision system 522 and a work agent 524, and is processed by a history and action aggregator 514. A session management service 510 publishes data to an XML-based messaging bus 512, which subscribes to the history and action aggregator 514. The history and action aggregator uses the subscription information to access a customer layer 536. The customer layer 536 includes ecommerce transactions 526, chat history/data 528, email history/data 530, voice over Internet protocol (IP) history/data 532, and legacy and other data 534.
The CTI/IVR service 500 coordinates the wireless data transactions with voice channel-based transactions and vice versa. It allows wireless data sessions to control, guide and trigger voice channel sessions and vice versa.
Wireless data transactions are published and stored on the messaging platform to guide voice channels. These transactions can in particular be actions to control the interactions with the caller in the voice channel. Similarly, voice channel transactions are published and stored on the messaging platform to guide wireless data channels. These transactions can in particular be actions to control the interactions with the wireless device user. In both cases, the actionable data can be pushed or pulled by a channel.
In the case of pulling actionable data using the CTI/IVR service 500, a user can click a link (e.g. “Listen to Movie Review”) on a wireless data session to trigger a call to the IVR system 518 that is to be controlled by the actionable data. By examining the voice channel data, such as the DNIS and ANI, the wireless session data, the voice call can be guided to execute the requested action, such as playing the Dinosaur movie review.
As a push example, suppose that a user clicks a link (e.g. “Fax the Document”) on a wireless data session to register actionable data with the messaging platform. This actionable data is picked up by a fax listener 538, which is registered with the messaging platform to listen for fax actions. The session data (e.g. telephone number, or document) will guide the fax listener 538 to deliver the document as a fax.
Similarly, the CTI/IVR service 500 can be used to request to send a uniform resource locator (URL) to a wireless data wireless device to trigger a wireless session. In this case, the actionable data from the voice session is being used to control the wireless data action. Here, the actionable data is registered with the messaging platform to be picked up by a WAP alert listener registered with the messaging platform to listen for the WAP alert actions.
These examples illustrate that the CTI/IVR service 500 allows the actionable data to be executed by the destination channel at the current point of the menu structure instead of having to start from the top of the menu structure to reach the intended target of the actionable data.
The CTI/IVR service 500 does not require that the wireless device 506 support simultaneous voice channel and wireless data channel as long as it supports concurrent voice channel and wireless data channel. It allows a user to toggle between a voice session and a data session. The CTI/IVR service 500 can involve two different devices for voice and wireless data, for example, providing a speech recognition interface to a telephone so as to send a URL or other data to a WAP wireless device in response to a spoken request. A user can use a telephone to do a transaction and have the receipt sent via a WAP alert to a WAP device or emailed to another device, such as a RIM™ device.
In one embodiment, the actionable data is represented as XML data on the messaging platform. The action type can either be a push action (e.g., WAP alert or outfax call) or a pull action (e.g., the voice channel queries the messaging platform whether there is a registered action such as “play the movie review of Dinosaur”).
A VoiceXML gateway 608 receives calls from wireless devices 606 or from wired device 607. VoiceXML gateways are Internet based telephony platforms over which a user can submit a VoiceXML document and initiate an audio dialog with the document over standard telephony channels. VoiceXML is a standard designed by the World Wide Web Consortium (W3C) to create audio dialogs that feature synthesized speech, digitized audio, recognition of spoken and DTMF key input, recording of spoken input, telephony, and mixed-initiative conversations.
Internet protocol (IP) data is sent to software 610. In one embodiment, the software 610 is a data voice telephony (DVT)-VoiceXML application engine, which includes automatic speech recognition and a text-to-speech (TTS) interface. For example, Nuance™, Speechworks™, and Fonix™ can be used. The software 610 also includes a hypertext transfer protocol (HTTP) directory client, dynamic grammar generation, a domain/personalization manager, an audio content manager, and an instant messaging and notification hierarchy. The software 610 is in communication with a web server 612. Referring to
Customer applications 602 initiate XML-based content trigger via the integration interface 620 to a DVT-VoiceXML application engine 610. The DVT-VoiceXML application engine 610 uses the audio content manager and transcoder to parse the XML content dialog file. Based on the parsing, a voice menu is constructed using the dynamic grammar generation module. The DVT-VoiceXML application engine 610 then generates a VoiceXML document and stores it in a local storage for expected callers. When an expected caller dials into the system (from a manual dial or from a data session), the domain personalization/manager recognizes the DNIS/ANI associated with the call and retrieves an appropriate VoiceXML document waiting for the caller. The DVT-VoiceXML application engine 610 sends the VoiceXML document to the VoiceXML gateway 608 that executes the document controlling the voice session dialog. When the caller enters a response via voice or DTMF, the DVT-VoiceXML application engine 610 activates the instant messaging and notification hierarchy module and sends the user response to a back-end application. During the voice session, the DVT-VoiceXML application engine 610 can activate the HTTP directory client to provide directory service if needed.
As an example of a wireless data session initiated by a voice call, consider a telephone company customer calling her wireless provider's “wireless web customer service” number to check the remaining minutes on her account. When the call is received the ANI, or calling telephone number, is used to generate an email/SMS message that is sent to the caller, and the voice session terminates. When the subscriber accesses the URL within the message, a session is started connecting the provider's customer care WAP site, and the customer accesses her account information.
As another example, a wireless web customer or a wireless telephone service provider wants to reserve tickets for an upcoming concert and purchase the tickets from a ticketing company. The ticketing company is not on the service provider's portal. The customer calls an appropriate toll free telephone number, and navigates a menu to “concerts”. The customer then chooses the IVR option “wireless ticketing”. An email is sent to the customer's wireless device with the initial page being “upcoming concerts”. The email is already tuned to the location of the caller. The customer can navigate the page to find information, price, and times, and purchase via the WAP application. The significant advantage to the ticketing company is that it easier to move the customer to a lower cost channel, and the cost of being on the service provider's portal is avoided.
In both of the examples a significant benefit is the ability of an end user to easily gain access to the relevant wireless data site without having to navigate multiple menus or enter a string of characters on the wireless device. This is a benefit to both the user and the company that wishes to have customers access company information over a wireless channel. Many applications benefit from initiation of a wireless data session by a voice call. They include customer service, direction finding, package tracking, movies, banking, gambling, and virtually any other interactive voice response (IVR) application.
This functionality does not require the wireless device to support simultaneous voice channel and wireless data channel. The voice channel can be terminated and the data channel can be opened later by the message that was sent to the wireless device.
One embodiment includes a call service that enables a customer application 602 to manage the sending of audio messages to a user and receive the user's touch tone response. The call service includes various components and software agents, including a call agent. The call service includes an incall service and an outcall service which include an incall agent and an outcall agent. A call service IVR receives a call from an end user and is ready with the appropriate sound files to play to the caller. After the audio files are played, the caller may hear a menu with choices or a transfer option, or a prompt asking for a multidigit string.
Before the call comes in, the customer application must send an XML file specifying which audio to play to which expected callers. Once the call is done, the call service will send the status of the call and the choice that the user selected from the menu to the response URL or the customer application so that the appropriate action can be taken.
The call agent 701 allows the customer application 702 to present information to mobile users that is not suited for the small screens typical of WAP-enabled mobile devices such as wireless device 706. This information is presented to the user via audio over the user's wireless device 706. Playing the audio includes checking to ensure that all audio is in an acceptable format, playing the content, playing the choices, and collecting a touch tone response from the caller.
The IVR service 718 handles the call with the end user. The call agent 701 sits between the IVR service 718 and the customer application 702 and manages the communication between the two. The customer application 702 provides an XML file that specifies, among other things, the audio file that the caller hears as well as any menu choices or transfer information for the call. This XML file also specifies any authentication necessary for the caller to receive the information.
A conversion component of the call agent 701 verifies that the audio requested by the customer application 702 is correctly formatted, and converts the audio content to a .wav file if necessary. The customer application 702 may specify audio in one of three ways: by specifying the URL of a valid .wav file; by specifying the URL of a text files; or by using text.
If the URL points to a .wav file, the conversion component checks the header to verify that the file type is supported. If the file has the RIFF header, it is accepted. RIFF is a Microsoft™ file format used for .wav, or WAV files. WAV is a sound format developed by Microsoft™. If the file has a national institute of standards and technology (NIST) header, it is re-written with a RIFF header. If the .wav file does not have a RIFF or NIST header, it is rejected. It is also rejected if it is empty or does not exist.
If the audio input is provided as a .txt file, the text is given to a text-to-speech (TTS) module for conversion to a .wav file.
A content player plays the content to the end user. Through a user interface, it provides the user with functions similar to those of a cassette player, including play, pause, fast forward, fast backward. These functions allow the user to repeat or skip portions of the message. The content player also has additional help functions built in.
The call agent further includes a menu selector. The menu selector is a self-contained object that handles the presentation of choices and their selection by the caller. The menu selector provides a single level of choices based on input from the customer application. All prompts pertinent to the menu, such as user input, caller selection, flow, and error handling are handled by the menu selector.
The menu selector receives prompts and choices from the customer application 702 via an XML file. The menu selector plays the prompts in the order in which they were provided. In one embodiment, each prompt is preceded by a prerecorded .wav file containing a phrase such as “If you would like . . . ”, and is followed by the phrase “ . . . press <number>”, where <number> is the corresponding value for that choice as specified in the XML file. For each choice, the value is the DTMF code expected when the caller makes the given choice.
The menu selector returns the value of a choice ID corresponding to the choice value selected by the user. If the call was dropped, it returns the status, “dropped call” to the call agent 701.
If the interaction contains a transfer, “0” is reserved for the transfer choice value. If the interaction does not contain a transfer, “0” may be one of the menu choice values.
In one embodiment, the call agent interfaces with the Dialogic™ board and software via the Dialogic™ applications programming interface (API).
The call agent 701 accepts the XML file from the customer application 702 via an HTTP request. The XML file is different for the incall agent and the outcall agent. The incall agent and the outcall agent will be described more fully below. The incall agent and the outcall agent communicate with the customer application 702 via HTTP. In one embodiment, the format for the request from the customer application 702 is as follows:
hostname is the name of the server where the XML file exists
nnn (ID) is the customer specified ID for the call
aaa.xml (xml) is the XML file name
The incall agent and the outcall agent each perform the following functions:
1. Get the request ID and XML file with the standard format from the customer application's HTTP request. The request from the customer application should be of the format:
2. The agent replies immediately to the customer application by transmitting a text file containing a numeric code and an explanation of the code. The standard HTTP status code of 200 should be present in the header, regardless of the contents of the text file returned.
If the request was well formed, the agent returns “0 accepted”. If the request was ill-formed, the agent returns “<nnn> <plain-text explanation>”.
If the reply was anything other than “0 accepted”, there will be no further reply from the agent regarding the failed request.
3. Check the XML file format (using the standard XML parser). If the XML file was ill-formed, send the ill-formed status to the customer application.
4. Check user license and appropriate permissions.
5. Check for the existence of .wav and text files specified in the XML file. Also check extensions and file size. The audio for the interaction can be specified in any of several ways, including: text is inside of content tag; wave file in the URL; and text file in the URL.
6. If the audio is not an acceptable file type, the agent will send a message to the customer application indicating so:
7. Pass the XML file to the IVR with request ID.
The menu selector provides a single level of choices for the user. It receives a set of prompt contents in text or wav format, and plays them in the order in which they were provided. Each prompt is preceded by a prerecorded wav file containing the phrase “If you would like . . . ”, and is followed by the phrase “ . . . press <number>”, where <number> corresponds to the position of the current choice in the list. The value returned by the menu selector is a number between −1 and 9, where −1 indicates that the call was dropped, and the values 0 through 9 indicate that the user entered a valid choice. If the user enters a number that was not assigned to any choice, the menu selector will play an error message, and play the choices again from the beginning. This process is repeated until the user either hangs up or enters a valid choice, but the customer software may provide a “timeout” value that indicates the maximum number of cycles.
The incall service and incall agent will now be discussed in more detail with examples. The incall agent, in one embodiment, is a user-initiated voice channel content delivery and actionable response system. Users can reach the system either through direct dialing or from a WAP data session using the wireless telephony application (WTA) “make call” capability. The in-bound call can be user and/or session specific (but need not be), with built-in optional authentication capabilities. The content can be recorded audio or text presented using built-in text-to-speech. A single layer menu may be presented to the caller after the content has been played. The incall agent responds to an XML document or URL link request from a customer application, and provides status and response information to that application through HTTP.
An incoming call may be initiated from a data session to deliver information that is not conducive to the small screen on a web-enabled telephone. The incall agent can be used when context persistence when switching modes (from data to voice) is important. In this case, a call is triggered by a data session and the context of the data session is transferred to the voice call. On the other hand, the incall agent can be used for context-independent or user-independent audio content. In this case, any person who calls from any telephone device can hear a message.
In one embodiment, a standards-based VoiceXML gateway installation is supported in addition to a Dialogic D41/ESC based analog telephony platform. For the VoiceXML gateway configuration, the IVR component is served by a qualified VoiceXML gateway platform.
Two system configurations for an incall service including the incall agent will be described. Many more configurations are possible. The two configurations are referred to as option A (a Dialogic™ D41/ESC based IVR platform), and option B (a VoiceXML gateway based IVR). Suitable components for both configurations are listed below:
Option A: Dialogic™ D41/ESC Based Call Service
Option B: VoiceXML Version of Call Service
Option B includes a content manager software module. In the Dialogic™ D41/ESC based configuration (Option A), most functions performed by this software module are a part of the C++ based IVR component. The VoiceXML configuration does not have any C++ based platform to serve this module, and a set of Java classes take over this function. These Java classes reside on an application server of the architecture platform and perform various functions for both the incall agent (the main servlet) and the dialog manager (written in VoiceXML codes and Java server pages (JSP)).
System requirements for one embodiment of the incall agent of option A are:
Windows 2000, Service pack 2;
128 MB of RAM required, 256 MB recommended for T1 card;
Pentium III 733 MHz required, 1 GHz recommended for better Text-to-Speech performance;
Disk space for audio content caching: about 30 MB per hour of audio;
One or two Dialogic D/41-ESC cards (4 channels each) or single Dialogic D/240 (T-1); and
Adequate network bandwidth for downloading audio content (LAN, DSL or T1).
The T-1 (or T1) carrier is the most commonly used digital line in the United States, Canada, and Japan. In these countries, it carries 24 pulse code modulation (PCM) signals using time-division multiplexing (TDM) at an overall rate of 1.544 million bits per second (Mbps).
Option B is a VoiceXML configuration. For option B, the system should include a Nuance™ voice web server and a VoiceXML gateway, such as VoiceGenie™. The VoiceXML gateway should be configured to associate one or more incoming voice ports with a DNIS (which is the number the user calls to access desired content) and URL. The URL is the root VoiceXML document for the incall agent. As an alternative to installing the VoiceXML gateway, the VoiceXML gateway can be hosted.
Performance of the incall agent on a T1 line is acceptable with separate machines handling the databases and servers. The central processing unit (CPU) overhead is relatively small. Dialogic™ supports this setup with an architecture designed to span multiple boards in multiple chassis. In this case the entire array appears as a single node with a large number of channels and resources.
Performance approximations for a T1 line are as follows: the incall agent can support 691 one-minute incoming calls per busy hour with a blocking factor of 0.001; 868 calls with a blocking factor of 0.010; 1000 calls with a blocking factor of 0.030; or 1244 calls with a blocking factor of 0.1. Where blocking factor is a measure of switch efficiency.
For failover handling in option A, the incall agent stores the XML files as they are given to it. In this case they do not need to be queued. Multiple IVRs are available to handle failover.
For failover handling in option B, failover is handled differently depending on the particular customer setup. If the customer is using a remote hosted VoiceXML gateway, failover management is built into the architecture of the hosting party. In this case, an incoming call is routed to one of several working machines. If the customer chooses to host their own VoiceXML gateway, failover is not provided, and the recovery process is reduced to manually restarting the VoiceXML gateway service on the platform after an incall agent failure, power outage, or other fatal system error. During this period, the system cannot accept a call. Such a recovery process takes approximately 15 minutes.
The incall agent can be scaled to a T3 line. A single T3 circuit has 28 DS-1 circuits for a total of 672 voice, or bearer channels. If primary rate ISDN (PRI) signaling is used, a few of the bearer channels are used to carry the signaling on a D-channel. PRI service is provided over a channelized T-1 facility. Twenty-three bearer channels (B-channels) are used to carry voice or customer data circuits. The twenty-fourth channel (D-channel) is used for out of band signaling to control the twenty-three bearer channels. Each B-channel has 64 k bits per second of throughput. At most one D-channel per T1 is used, but if the telephone company supports it, the customer can use non facility associated signaling (NFAS), where a single D-channel on one T1 span carries the signaling of several other T1 spans. The minimum voice channels in a T3 would be approximately 644 in the case of PRI with no NFAS, and the maximum would be approximately 672 (in the case of robbed bit signaling). With T3, the incall agent supports approximately 35,000 one-minute incoming calls per hour, with one percent of the callers getting a busy signal.
For NFAS, multiple PRI circuits to the same customer premises are bonded together so that the D-channel of one PRI can control multiple PRIs. This frees up the D-channels on the bonded trunks to be used as additional B-channels. Normally a second D-channel is assigned to be a backup to the primary D-channel for redundancy.
For Option B, the run-time environment of the VoiceXML based IVR component is provided by the VoiceXML gateway 832 which can be either co-located on the same LAN with the architecture platform 804, or located in a remote hosting environment managed by a VoiceXML gateway operator such as VoiceGenie™, BeVocal™, Tellme™, HeyAnita™. The incall agent is thus independent from the telephony component of the VoiceXML 832.
Typically, the incall agent resides on the architecture platform and supports one of the two configuration options described above. For both option A and option B, the incall agent 801 sits on the architecture platform 804, as shown in
In the alternate call flow, shown in
In one embodiment, the incall agent 801 is a Java class. The content manager 842 is an XML parser that is a Java class module that supports VoiceXML configuration. Configuration 846 is part of an administrative web site, and defines installation and configuration parameters, such as prompt language and file directories. The IVR/DTNF dialog manager 840 is a VoiceXML document that defines the DTMF-based IVR dialog (without voice recognition). This document is managed by the web server of the architecture platform 804 with a pre-defined URL for the VoiceXML gateway 832 to fetch.
In this VoiceXML based system configuration, option B essentially runs on two computers or groups of computers: the architecture platform 804, and a VoiceXML gateway 832 which could be hosted through a third party VoiceXML gateway 832 operator. An advantage of option B is that it could require only the installation of the architecture platform 804 without any other telephony infrastructure at the customer premise. The following describes how the data flows through the system shown in
The customer application 802 sends an HTTP request to the incall agent 801. One of the arguments to the HTTP request is a URL for the XML document defining the request details. The incall agent 801 checks the access permision for the requesting host and the arguments to the HTTP request, and then passes the XML file to content manager 842. The content manager 842 parses the XML file, processes related audio files, and stores the relates audio files at a proper location for one or more expected callers (ANI) calling into one or more specified numbers (DNIS).
When a call arrives at a particular voice port (DNIS) on the VoiceXML gateway 832, the VoiceXML gateway 832 sends an HTTP request to the architecture platform 804 asking for a pre-defined VoiceXML root document associated with that DNIS. If the caller's ANI is also delivered to the gateway 832, the gateway 832 will store the ANI at a location for the VoiceXML root document to use if desired.
The VoiceXML root document, after arriving at the VoiceXML gateway, will initate the IVR/DTMF dialog manager with DNIS and ANI if it is available.
IVR dialog manager 840 (written in JSP and VoiceXML) will contact the content manager for the initial opening prompts associated with that DNIS such as branding or service name defined in the XML document from the customer application 802.
If ANI is not available, the IVR dialog manager 840 will ask the caller to enter their ANI in DTMF. With DNIS and ANI, the IVR dialog manager 840 will retrieve relevant information about this call from the content manager 842 and carry on the dialog with the caller.
After obtaining a user response (if required) in DTMF, the IVR dialog manager 840 will send the user response to the incall agent 801 along with various status codes in the form of an HTTP request.
The incall agent 801 will then contact the content manager 842 to determine if there is a response URL defined in the XML document from the customer application 802. If there is, the incall agent 801 will send the user response to that response URL. If there is no response URL, or if the call is not successful, the incall agent 801 will send the user response to the customer application 802 if requested (via an argument to the original HTTP request from the customer application).
The user interface for the incall service includes prompts that can be constructed from pre-recorded prompts, customer supplied audio files, or text-to-speech. The user interfaces for both option A and option B can be identical. However, limitations of VoiceXML may dictate some differences in the interfaces.
The basic user flow for the incall agent 801 is illustrated in
The customer must supply the XML file that drives incall agent. The customer may build this XML file in any way, but for the purposes of this document, we assume that the XML file is built through some sort of automated application (e.g., a customer application). This customer application then sends the XML file to the incall agent via an HTTP request. The formats for the XML file and for the request are detailed below.
For a VoiceXML-based configuration, the VoiceXML gateway chosen to provide the run-time environment for the IVR/DTMF dialog manager (written in VoiceXML and JSP) is considered to be an external component even if such a VoiceXML gateway platform is on the same LAN as the architecture platform. The interface between such a VoiceXML gateway and the incall agent is an HTTP request. For each inbound voice port on the VoiceXML gateway there is a corresponding URL that points to a VoiceXML root document stored on the web server of the architecture platform. This URL must be reachable from the VoiceXML gateway, for instance:
This root document URL is typically provisioned via an administrative interface on the VoiceXML gateway using standard web browsers or some type of graphical user interface (GUI) or text file entries. Table 1 shows the logic entries in such a provisioning table.
The database provisioning for incall services specifies which hosts may illustrated in Table 2, a table in a services database contains the following data for each host provisioned:
Unique id (primary record key)
R for requesting host, A for answering host,
v for a VoiceXML gateway
Yes/No for current availability/authorization
Only those hosts with R purpose and Yes permission can submit requests for incall agent services. Only those hosts with D or V purpose and Yes permission will be assigned requests for answering an incoming call to the incall agent IVR host (Dialogic D41/ESC based or VoiceXML gateway based). The host for the response URL and the host for the machine storing the XML must be provisioned in addition to the IVR host and the requesting host. For option B, the following additions are made to the incall agent provisioning table. These items are specified per DNIS:
Document Root directory;
Install type—either US/Canada or Europe (default is US/Canada);
Language for the prompts;
Input mode—voice or DTMF; and
Audio Playback Skip Interval (go back or forward by N seconds).
For each item, a default is predetermined.
In one embodiment, the incall agent is a Java servlet based software module that acts as a link between the customer application and the IVR component. The incall agent uses the standard Internet HTTP protocol to communicate with the IVR, as well as to return status codes to the customer application. The incall agent also verifies that incall requests emanate from known authorized hosts, and manages assignment of requests to available hosts.
In one embodiment, the IVR is the component responsible for interacting with the end user. It interacts with the incall agent to receive the XML that feeds the dialog with the end user. After the voice channel based dialog with the end user, the IVR sends back a report in XML to the incall agent. The report contains the status of the call (e.g., success or failure) and the user response in DTMF, if required. The incall agent assembles a response message in XML and sends it to the response URL specified in the original XML file from the customer application. If no response URL is specified, the incall agent will discard the status report from the IVR. If the response URL returns a VoiceXML document in the case of VoiceXML configuration for this service, the VoiceXML document will be sent to the VoiceXML gateway. This will allow the user to conduct further interactions via the voice channel.
In one embodiment, for options A and B, the incall agent sends a post-call response either to the customer application or to the response URL. If the call is not successful, for example user input was desired but none was obtained, or the user disconnected before the end of the content message, the incall agent returns a status code indicating the nature of the call to the customer application. If the call was successful, for example user input was obtained, or no user input was desired and the listener heard the entire content message, the incall agent sends the call status along with the user input (if it exists) to the response URL.
Any file or text to be played to the end user is specified as a .wav file, a .txt file, or text in double quotes.
The incall agent uses the standard Internet HTTP protocol to communicate with either the incall service IVR running on a Dialogic™ D41/ESC based telephony platform or the incall service IVR/DTMF dialog manager implemented as a set of VoiceXML documents which reside on the web server of the architecture platform. In addition, the incall agent sends the appropriate response messages to the response URL (if specified) that may or may not be a part of the customer application requesting the incall service. Specifically, the incall agent performs the following tasks:
The incall agent acts as a link between the customer application and the IVR component in both option A and option B. The format for the request from the customer application is
hostname is the name of the server where the incall agent resides;
ID (abc) is the customer specified ID for the call;
xml (aaa.xml) is the XML file name; and
acknowledge is true or false for returning acknowledgement to the customer application.
The incall agent responds to the customer application with HTTP requests, first to indicate the immediate feedback from receiving a request, and then with the result from the call. The immediate response consists of XML containing status and message in the following format:
where the status is 200 for a success and 400 for HTTP request not valid.
Once a call comes in and is completed, the incall agent responds either to the customer application or the response URL, depending upon the status of the call. If the call is successful, the incall agent responds to the customer application. If the call was not successful and the acknowledge parameter is set to true in the original HTTP request from the customer application, the incall agent sends the status code back to the customer application. If the acknowledge parameter is set to false, the incall agent does not send a status code back to the customer application.
Table 3 lists 2-digit status codes returned from the incall service IVR to the incall agent under various conditions.
[xx . . . xx]
The incall service IVR sends this status code to the incall agent using a standard HTTP POST request as follows:
where the <resp_URL> (optional) came from the XML data received earlier from the incall agent. The XML specifying the response is as follows:
If there is no input (e.g., in the case of a hang-up, or when no choices are specified in the XML), the input tag is absent.
Based upon a “Purpose” configuration for the answering hosts provisioned at an administrative screen of a user interface, the incall agent knows if an answering host is a Dialogic D41/ESC-based IVR platform (Option A) or a VoiceXML gateway (Option B). In case of option A (Purpose=A), the incall agent communicates with the IVR component via an HTTP POST, with an attached XML body, as follows:
where the attached XML body is strictly copied from the original XML file submitted by the customer application.
In case of option B, the incall agent will pass this XML file to a Java-based content manager, which parses the XML file and processes individual XML elements accordingly. For either configuration option, if the XML file fails to parse (e.g., because it is missing the <Service> element), the incall agent sends proper status codes and related error messages to the customer application if acknowledge=true. Because both the incall agent and the content manager are implemented in Java classes and reside on the same architecture platform, they can communicate with each other using either http requests or Java class based services.
The incall agent keeps a list of requests that have been submitted. An HTTP request of the form http://<hostname>/servlet/Incall?pending will return a list of request IDs not yet reported as completed, along with their time of submission.
This Java based software module resides on an application server of the architecture platform. Its primary function is to parse the XML received from the incall agent, process audio content, and store it as various URLs for the IVR/DTMF dialog manager (VoiceXML document) to use. In one embodiment of option A, this set of functions are performed by a C++ based module residing on the Dialogic™ D41/ESC based telephony platform.
One of the variables the content manager must know is the location of the root directory for all the audio content files and system prompt files. Like the initial login page for the web administration of the architecture platform (e.g., http://<hostname>/html/Welcome.isp), the underlying JSP document is stored in a pre-defined system folder. Similarly, the content manager must obtain this root directory location information from a data source. In one embodiment, this interface is implemented by introducing a new field on an incall service administrative page to associate the default web document folder for the web server with the actual reachable local folder name.
In one embodiment of option A, the installation will copy the system prompts for the incall service into a location that is not designed for constructing a URL path. For example, the actual system prompt files are copied from the release compact disc (CD) into a typical local folder.
In one embodiment of option B (VoiceXML version), all system prompt files are also copied into an appropriate webclient folder. For example, if these system prompt files are copied into the webclient folder, they are reachable later by a VoiceXML document.
For example, a Welcome.wav audio file stored there can be referenced by the following URL:
The directory structure for managing audio content is designed to handle both broadcasting mode, in which the same audio message could be accessed by millions of different end users, and personal mode, in which one audio message is only for one particular end user. The overall audio content directory tree is structured to support four mutually related branches under the root directory: DNIS, Service, ANI, and Audio. The following example directory tree is constructed by the content manager based on an XML file describing one DNIS entry, two ANI entries, one audio content file with a URL path, and a three-choice menu with each menu choice represented by a URL path pointing to an audio file of proper file format (.wav). To support fast-forward or fast-rewind while playing a long audio file, the content manager constructs five overlapping audio files from the original audio file. In the example of Table 4, it is assumed that the audio content is presented by a text file divided into three text files for support of playback options.
Every XML file requires a service name element, such as <Service name=“some text”>. Because the name attribute does not have any limit on text strings, the content manager maps each name string into a unique service ID using some algorithm. For example, a name string “movie sales online store” may be mapped into “moviesale1404”, which is the first two words plus a 4-digit sequence number.
The content manager provides an API as illustrated in Table 5 for the IVR dialog manager or the incall agent to retrieve context information about a specific call.
cm( ).authDescription (could be
cm( ).authCode (could be null)
cm( ).NaudioSeg (1 to N)
cm( ).prefix (e.g., <time-stamp>
cm( ).suffix (e.g., “.wav”)
cm( ).NmenuChoices (1 to 9),
cm( ).menu[I].type =
“txt”, “wav”, “url”
Acm( ).responseURL (could be null)
For option A, the telephone number collection component uses the telephone number class as previously defined. In one embodiment, the DTMFTelephoneNumberClass is used. For option B, the telephone number collection component is implemented in VoiceXML. In one embodiment, telephone number collection is always turned on, because MIN may not be reliable across a VoiceXML gateway.
The behavior of the authentication component is the same for option A and option B. If the XML contains non-empty strings for the authentication description and authentication code, this component plays a phrase such as, “If you are $expected_caller, please enter your <authentication_description> followed by the pound sign”. The authentication component accepts a string of DTMF tones. If the string matches the expected authentication code, the authentication component returns “true”, otherwise it repeats the above procedure up to a configurable number of times. If the user has not entered the correct code the authentication component plays a final error message, drops the call, and returns “false”.
If the XML contains no authentication codes, the component returns “true”. An empty authentication description or an empty authentication code indicates that authentication is not necessary for this interaction and therefore should be skipped in the dialog.
The following use cases are examples that describe the user experience with the incall service, including the interaction on a data session with the application, the call initiated from the data session, the interaction with the IVR, and subsequent actions. The incall service handles the portion of this experience that dictates the interaction between the user and the IVR.
In a first case, Jane follows Company WX and other wireless infrastructure companies closely. She subscribes to a service from Epoch Partners™ that provides her with an analyst's comments every Tuesday morning. When she turns on her cellular telephone on Tuesday morning, typically there is already an alert message from Epoch Partners™ waiting for her. Once she has gotten her daily 30-minute commute to work underway, she views the alert message. The message offers Jane the option to listen to the report. Jane presses the “CallIn” softkey, puts the handset to her ear, and waits to hear the analyst report.
The content in the report is specific to Jane, and therefore requires her telephone number as well as an authorization code. If Jane's telephone number does not come through on CallerID, the IVR will ask her for it. Jane uses the “fast forward”, “rewind”, and “pause” functions to facilitate reviewing the material. When Jane gets to the end of the message, she can choose an action such as faxing or emailing the document.
If Jane's call drops, she uses her telephone's “redial” function to get back in. She uses the “fast forward” function to get back to the portion she was last listening to.
In a second case, John wants to see a movie at a theatre tonight, but doesn't know what is playing. He accesses the Fandango™ site from his cellular telephone. John has previously allowed that site to categorize the zip code he lives in as well as his movie preferences. John loves action films and never wants to hear about romances. Today, he can see that there are two interesting looking films playing nearby. John selects one of the films and presses a softkey that invites him to listen to a movie review. He then puts the handset to his ear. When the call connects, he hears the movie review. After the review is completed, he is offered the option to purchase a ticket. Instead, John just hangs up and browses to the next film, to hear that review.
The movie review must be queued up for John when he requests it. While it is a public piece of material, it is one of many available. Therefore, if John's CallerID had not come through, he would have been asked to key in his telephone number. However, because this is not secure material, John will never be asked for an authorization code of any kind. John can take advantage of the “fast forward”, “rewind”, and “pause” functions to navigate through the material.
Because the “actions” on this material are optional, hanging up is an option for John. John just goes back to where his browser left off. Many telephones cache the last page. For telephones that do not cache the last page, and “action” can allow the user to return to a previous location in a data session. If John elects to purchase a ticket, a browser alert is sent to allow him to navigate easily to the appropriate point in the data site.
The outcall service and outcall agent will now be discussed in more detail. In one embodiment, the outcall service enables a customer application to send a voice alert to an end user by making an outgoing call and playing audio messages to the person called. The outcall service then either plays a single-tier menu or plays a prompt asking for multidigit input, and accept a response.
The outcall service initiates a call to an end user which may or may not be an actionable call. The customer application specifies that the IVR send a voice alert by calling an end user. Once the end user answers and authenticates (if necessary), the specified voice files are played, choices are presented, or an input string is asked for, and a response is accepted. The XML file sent by the customer application can specify the phone number to call and the audio file(s) to be played as well as the authentication information, menu choices or value input prompt, and transfer information.
In one embodiment, the outcall service requires the following system setup:
Digital trunks require different call control signaling than the analog lines. The two most common signaling schemes for T1 lines in North America are Robbed Bit Signaling (RBS) and Primary Rate ISDN (PRI). For RBS, a non-ISDN digital trunk is provided over a channelized T-1 facility. 24 channels are available for voice or customer data circuits. Signaling is in-band in that a few bits from each T-1 super-frame are “robbed” to serve as status bits for the 24 channels. Each channel ends up with only 56 k bits per second of real throughput. Digits are sent as DTMF or MF tones in-band during call setup.
In various embodiments, different protocols may or may not be supported for RBS and PRI. For example, for one embodiment using PRI, only National ISDN 2 (NI2) protocol is supported.
One embodiment of the outcall service supports a T-1 line based Dialogic™ digital telephony platform with a single T-1 interface card (D240). With a T-1 line, the outcall service can support 1380 outgoing one-minute calls per busy hour, at 100% capacity. To handle failover, the outcall service keeps the XML files sent by the customer application. In a worst-case scenario, the end user could receive more calls than the ensure completion value indicates. However, this case is expected to be extremely rare and the consequences acceptable. The outcall service allows multiple active IVR hosts to be provisioned, therefore, if one IVR host is down, another can complete the calls. A switch to a new IVR can be manual or automatic.
Typically, the outcall agent 1101 resides on the architecture platform 1104 as shown in
Various implementation details for embodiments of the outcall service will now be discussed. The implementation details refer to two of the software components that work together to provide the functionality of the outcall service. The first component is a Java-based outcall agent. The second component is a C++ based software component, the outcall IVR, which interfaces directly to a Dialogic™ telephony platform.
The customer must supply the XML file that drives outcall service. The customer may build this XML file in any way, but for the purposes of this document, we assume that the XML file is built through some sort of automated application (e.g., a customer application). This application then sends the XML file to the outcall service via an HTTP request. The tags for the XML file are detailed in
The outcall agent makes standard requests of the product provisioning and configuration tables that are stored in a database of the architecture platform. This set of tables can be organized as a single web page for all voice products. The outcall agent has its own web page to provision various run-time parameters. In addition, the outcall agent is integrated with other services to deliver “voice” alerts in addition to other types of alerts such as WAP, SMS, etc.
The database provisioning for the outcall services specifies which hosts may make requests, and which hosts are available to serve those requests. A MOBHOSTPERMISSION table in a services database contains the data shown in Table 6 for each host provisioned.
IP address or domain name such as www.ml.com
Request or IVR
Yes/No for current availability/authorization
Only those hosts with host type Request and permission Yes can submit requests for outcall services. Only those hosts with host type IVR and permission Yes will be assigned requests for dialing. In the case of a WAP browser making the request of the outcall service, the host on which the attached XML file can be found must be provisioned.
The outcall agent checks licensing issues and interacts with the customer application and the IVRs. One task of the outcall agent is determining which provisioned IVR to send an XML file to. The outcall agent uses a load balancing algorithm to determine the IVR that has been contacted least. However, the outcall agent must send all HTTP requests with the same ID to the same IVR so that M-files and their corresponding P-files go to the same IVR. The outcall agent also determines if/where to send a response based on the outcome of a call.
The outcall agent accepts an XML file from the customer application via an HTTP request. The request may be either a POST or GET request. If the customer chooses to utilize a GET request, the format for the request from the customer application is as follows:
The format for a POST request is as follows:
In order for the outcall agent to support multiple customer applications and multiple IVRs, the ID for an M-file and all corresponding P-files must match. An M-file is one that contains a MULTICALL tag and possibly a PERCALL tag. A P-file is one that contains only a PERCALL tag and no MULTICALL tag. The calls specified in a P-file use tag values specified in a previous M-file.
The outcall agent responds immediately to the customer application with an HTTP request to indicate the immediate feedback from receiving a request. This immediate response consists of XML containing the status and a message in the following format:
where the status is 200 for success, or 400 for HTTP request not valid.
After the outcall IVR completes a call, either successfully (e.g., by reaching the number specified in the XML file), or unsuccessfully (e.g., by reaching a point at which it cannot fulfill the request for any reason), it sends a final status code to the outcall agent.
The 2-digit status codes shown in Table 7 are returned from the outcall IVR to the outcall agent under various conditions.
The outcall IVR sends this status code to the outcall agent using a standard HTTP POST request as follows:
where the <resp_URL> (optional) came from the XML data received earlier from the Agent. The XML specifying the response is as follows:
If there is no input (e.g., in the case of a hang-up or if no choices are specified in the XML), the INPUT tag is absent.
After the outcall agent receives a final response from the outcall IVR, the outcall agent will reply to the response URL of the customer application, or not at all, depending on the status of the call and the value of the acknowledge parameter in the original HTTP request. If the call is successful (status code 0) the outcall agent will form an HTTP request to be sent to the response URL with the following format:
where “NN” is the 2-digit status code from outcall IVR, “input” is the user's input, and “message” is the corresponding message. For example, if the status code is 0, the input 1, the message will be “Menu Selection 1”.
If the status code is not 0, the outcall agent will determine where to send the result based on the acknowledge parameter sent with the original HTTP request from the customer application. If the acknowledge parameter is set to True, the outcall agent will send the result of an unsuccessful call back to the customer application. If the acknowledge parameter is False, the outcall agent will not respond to the customer application with the result of the call. The default for the acknowledge parameter is True.
The outcall IVR keeps a list of requests that have been submitted, but have not yet been completed. An HTTP request of the proper form will return the number of pending calls for the specified service.
An HTTP request with a reset tag set in an XML tag will cancel the values for that tag and any of its child tags. Only certain tags, such as service and call tags, may be specified for reset.
In one embodiment, the outcall agent and the outcall IVR use the VPLSecurityLock™ software to ensure that the request to the outcall IVR is coming from a known source.
The outcall IVR interfaces with the Dialogic™ board and software via the Dialogic™ API. The Dialogic™ channel encapsulation provides a method for placing an outbound call and determining the outcome of the call (voice connection, busy, no answer, etc.), using Dialogic™ call analysis. The dialing component is configured to retry the call a specified number of times, or to send a status message back to the outcall agent. These behaviors should vary according to the result of the dialing attempt.
The “cache” is a module used by the outcall IVR. Cache is a class that maintains a map of audio data specifiers, such as a URL, a disk file name, or literal text, and the corresponding path to a local disk file. It provides methods to add entries or arrays of entries, transparently invoking TTS code or web client code to process literal text or URLs. Audio content should be added to the cache before a call is placed or received, to avoid delays associated with TTS or downloading.
The “ACR menu” is another module used by the outcall IVR. The ACR menu is a class that presents a set of choices to the user, requests confirmation once a choice has been made, presents the choices two more times if no choice is made, and finally returns a status code. This codes may be the ordinal of the selected menu item, TRANSFER if the user entered zero, HANGUP if the call was dropped, NOTHING if the user allowed the dialog to time out three times, or REPLAY if the user pressed the star key to request that the content be played again.
“LiveDocument” is another module used by the outcall IVR. LiveDocument is a class that provides support for loading audio content into memory so that it may be accessed randomly to support fast forward, fast backward, and GOTO functionality. LiveDocument contains the code that creates a local disk file for caching purposes, if the content is specified as literal text or a URL. LiveDocument also provides support for resizing the audio buffer so that live input can be appended to pre-existing recorded content.
“Dialogic™” is another module used by the outcall IVR. Dialogic™ is a class that encapsulates one Dialogic™ channel. It provides facilities for opening or closing a channel, setting the termination conditions for I/O operations, and carrying out I/O operations such as playing a file or buffer, recording, getting DTMF digits, etc.
“ACR” is another module used by the outcall IVR. ACR is a class that is derived from the Dialogic™ class. It provides higher-level methods, similar to the controls on an audio cassette recorder: play, record, goto, fast forward, fast backward. The ACR class uses the LiveDocument class to keep audio data in memory and support random access to content.
“WebReader” is another module used by the outcall IVR. WebReader is a class that is based on Microsof™ sample web client code. It is used to send an HTTP “GET” request. This is done when content is provided as a URL beginning with “http:”, and at the end of each call, to send the final status or menu selection to the outcall agent.
At configuration the outcall IVR learns what type of Dialogic™ board is installed, so the outcall IVR does not need to automatically detect it. An additional thread may be needed in some embodiments to detect unexpected call drops, because the audio I/O functions will not be interrupted if the call is placed on a digital line. The “dx” family of I/O APIs can be interrupted by a loop current drop on an analog line, but there is no corresponding termination condition for a digital line. One solution, in the case of robbed-bit T1 signaling, is to use a separate thread that detects events involving the A and B signaling bits, issues a dx_stopch call to stop the I/O operation in progress, and makes the channel available for another call.
An authentication component ensures that the person who answers the phone is indeed the desired audience for the audio message. Authentication is optional, as not every application will require the end user to be known. The authentication module asks the user for a code of some sort (e.g., an account number or social security code) and then compares it against the value known for the desired person. If no authentication is required, this component asks the called party to enter a single digit in order to determine that the answering party is a person and not an answering machine or voice mailbox. The authentication component then returns true or false.
The following use cases illustrate the outcall service. The outcall service initiates a call to an end user when instructed to do so by a customer application. The customer application, at a scheduled interval, requests the outcall service to make an outbound call to the end user and play a specified message. For instance, this message may be a daily analyst report or the traffic and weather report. The outcall service can be used to escalate message service. Because browser alerts, email alerts, and SMS alerts may not reach a roaming user, a customer may wish to contact an end user with the outcall service if attempts at sending other types of alerts have failed.
Not all targeted end users may have a WAP-enabled telephone, but an outcall service message can be sent to any type of telephone. The outcall service may also be used for security/authentication. The outcall service provides a more reliable way to confirm the correctness of a telephone number than CallerID. An application can ask the user for his telephone number, give him a security code to enter during the outcall service, and make a call to the number given by the user. The user then enters the security code given to him during the data session for authentication.
The capability of the outcall service to ask the end user for input in the form of a menu choice or multidigit input can enhance any of these use cases. An application can use an escalated call to get the input it would have with a browser alert, or it could get daily feedback from an end user with a scheduled call.
Because the outcall service initiates a call to an end user, the outcall service must ensure that when the telephone is answered, there is a person on the other end, and not an answering machine or voice mail. The outcall service will ask for a DTMF input when the telephone is answered to ensure that there is a person on the other end. The DTMF asked for will depend on the parameters sent in the XML file from the customer application. If an authentication code is specified, the code input will serve as proof that there is a person on the line. If no authentication code is specified, the person answering will hear a prompt asking them to press a key in order to continue.
Another feature of the outcall service is the ability to call back should a call be dropped. The outcall service determines when to call a user back after a call is dropped based on an “Ensure Completion” parameter, and whether the call was dropped prior to confirmation of the end user.
Voice channel homepage provisioning as shown in
According to one embodiment, a voice call number is provided to the WAP/HDTP user. This number is called using the WAP/HDTP wireless device 1406. The homepage provisioning service 1402 receives the call, extracts the caller ID (e.g., telephone number), and terminates the call. The homepage provisioning service uses the caller ID of the wireless device 1406 to find a corresponding homepage URL. In one embodiment, the homepage provisioning table 1410 is queried for the corresponding URL. The homepage URL is sent to the homepage provisioning service 1402, and forwarded to the messaging service 1404. The messaging service sends an actionable alert with an embedded URL for that user's homepage to the user's wireless device 1406. By responding to the alert, the user immediately enters a data session directly with their homepage. The user can bookmark the homepage for later use. The end-user interface 1408 is used to manage the display of homepage entries.
The voice channel homepage provisioning service, in one embodiment, is voice-activated using speech recognition and voice short cuts, such as, “send homepage to my WAP wireless device”, or “send 800-flower homepage to my WAP wireless device”, etc. The homepage provisioning service can also be an 800 number based service. In this case, the service immediately terminates the call upon receiving the caller ID in order to avoid incurring the call cost. Once the caller ID is received, the service can immediately register a push actionable alert embedded with the URL to, for example, the CTI/IVR service 500 of
One advantage of the voice activated approach is that it can additionally allow users to use voice short cuts to go to URLs that are not necessarily homepage URLs. The 800 number on the other hand, avoids telephone costs to the service provider. As an alternative to using voice short-cuts, URLs can be bookmarks on the homepage URL menu.
Another process provided in the method and system is a wireless location service as illustrated in
The positioning of a mobile device provides the basis for so-called location services. Location services provide information based on the location of certain mobile devices. Examples include enhanced directory assistance, roadside emergency service, fleet management, asset tracking, and others. In one embodiment, the wireless location service is a proxy that provides a single point of interface to one or more applications and one or more location networks for location management using an open protocol. The location service processes position measurements to assure that they are in the required format, and obtains the required authorization for locating a mobile device. The location service manages mediation among network entities, preferences, authorization, and related functions. Mediation is provided among nodes that are logical peers but do not support the same interfaces. The location service includes a gateway that may be physically installed and operated by different entities. For example, the location service may be co-located with the application server, WAP gateway, location gateway, or hosted independently.
The location service combines location management with other services, such as session management, alerts, device management, and caching to provide a comprehensive solution for location sensitive applications. The interface to the architecture (for example, architecture 104 of
The interaction of location services 1612 with the services and entities shown allows various functions to be provided transparently. For example, the following functions are performed: auditing, including measuring use (in peg counts) in categories based upon subscriber, application, network, etc., for purposes such as billing, feature customization, usage tracking, etc; managing position data formats; and storing the last known location (for example, for retrieval after temporary loss of GPS coverage, which avoids GPS warm-up delay).
The architecture (as shown, for example, in
The single sign-on service greatly reduces the involvement of the user in signing on to individual customer applications. The single sign-on service 1710 does not impose a single authentication scheme on all participating applications. It accommodates diverse application security requirements concurrently within a single deployment environment.
In one embodiment, a relatively passive approach to managing access to customer applications is used. In this approach, the single sign-on service maintains very limited knowledge of the applications accessible to its users. For example, the single sign-on service maintains the identification of applications, and how to reach their sign-on page. The single sign-on service does not need to know the specific authentication requirement of the application. The single sign-on service forwards the sign-on request to the application, and it is then up to the application to proceed appropriately.
Another embodiment includes a relatively more active approach, assuming more responsibility in registering, administering and managing applications it allows its users to access. In addition to the identification of the applications and the address of their sign-on pages, the single sign-on service is also aware of the authentication requirements of each. The single sign-on service optimizes the communication flow between itself and the applications, and also participates in enforcing authentication requirements.
The low-level single sign-on service of
The single sign-on services 1710, 1810, and 1910 provide requested services to the customer application during the process of application sign-on. The customer application may request the SSO password of a user (in the case of the mid-level security model), or store a security token for a user (in the case of the high-level security model). The single sign-on services include servlets with a predefined request and response data stream format. Each customer application requiring any of these services is assigned an application ID. Single sign-on services implement an authorization scheme based on the application ID, and validate each service request using this authorization scheme.
Session management records both the requesting URL and the post data associated with it and its response for a domain. If the response is recorded at a domain for the last request, then when the user resumes a session at the domain, the URL does not get posted or requested again to avoid duplicated and side effect transactions. However if the response is not recorded, e.g. due to a network failure on the application side, session resume will cause a re-post or re-get request.
As shown in
Another feature of the session management service is the network-side autofill of a form. This saves the user the trouble of typing in form field data again when the user returns to a form previously filled. The data used for autofill is form data previously entered by the user, and can be data in the user's electronic wallet. Each field of a form is intelligently recognized and classified to allow future autofill of the field of the same classification. For example, an email address that is recognized for an email field on a form can be used to fill in email fields of any forms. To ensure security and privacy, the autofill is based upon user preferences and application domain settings so that certain form data will not be autofilled. The autofill is particularly helpful when used across multiple devices. For example, a user can fill in a form using a device with relatively “better” keyboard interface, such as a PC, and then the form can be autofilled when accessed by a wireless device with a relatively “worse” keyboard interface.
The network-side autofill is either session-based or persistency-based. In the session-based case, the form is only autofilled within a given session time. In the case of persistency-based, the form data persists across multiple sessions.
In one embodiment, the session management service publishes data from the wireless data session of a user to a messaging platform. This platform provides data about the user on the wireless channel. The messaging platform can be subscribed to by, for example, customer relationship management (CRM) systems for integrating data and transactions associated with a user from multiple channels such as CTI/IVR, web, and email. The session management service is the wireless channel in this case.
The navigation and presentation services provide platform-independence, data-source-independence, a high degree of personalization, and a distributed implementation that can be hosted anywhere. In one embodiment, the navigation and presentation services act as a WAP front-end to customer legacy systems. They can also be used as a stand-alone application, as well as integrated with the entire suite of enhanced services (as shown in
The cookie management service supports multiple interfaces to the wireless gateways (e.g. HTTP proxy, XML, etc). The cookie management service supports multiple domains and can be run as a service hub or as a data center. The cookie management service need not be physically located with the wireless gateways. With the cookie management service, multiple devices have access to the same cookies. This is particularly useful when a user wants to fill out a form with a more user-friendly keyboard, and then use the cookies generated from the desktop interface via the wireless device.
In one embodiment, the cookie management service is deployed as a proxy-based value added service with features such as cookie session management, navigation, profiling, preferences etc. The cookie management service is positioned on the back-end of the WAP gateway in carrier, or alternatively on the back-end of the enterprise, or customer system. Alternatively, the cookie management service is positioned on the front-end of the enterprise applications. In either case, the cookie management service can be a plug and play “middleware” hardware and software application.
The cookie management service 2202 provides enhanced security, in part because the cookie management service intercepts cookies which will be sent to the client destination side rather than caching cookies. The cookie management service allows the user to have only session cookies, which provides additional security, privacy control and convenience to the user. The user can operate within a session as if the cookies are stored, but as soon as the session is timed out, cookies will not be in (or will be removed from) the database.
The cookie management service provides secure encryption between itself and the enterprise application. When the cookie management service is positioned on the front-end of the enterprise using the security and privacy management environment of the enterprise, there is no dependency on the carrier infrastructure or wireless device capability. The user can use any device to lock cookies. This is particularly useful if the user's accessing device is stolen. It is also possible for a user to delegate some cookies to other users without compromising undelegated cookies. For example, a user can lend a wireless device for others to check stock quotes, but not for reading email. This is achieved by locking email cookies.
In addition to cookies, the cookie management service also handles advertisements and promotions. Because the cookie management service supports an XML interface, it can off-load some processing power of the gateways in a client server. Cookie processing is only passed on based upon needs of the gateways.
In one embodiment of device registration, the user initiates a data session to register a device. The user is prompted for a previously assigned user name and password, and the user is asked to enter their telephone number. After entering the telephone number, the user is immediately presented with a personal identification (PIN) number. The unique device ID is automatically captured during this data session. The device registration service then makes a voice call to the phone number (by using the outcall service described above). When the user answers the call, he is prompted to enter the PIN. The phone number is automatically related to the device's unique data identifier.
Voice verification is superior to prior methods such as short messaging, in part because the user does not have to key in any characters. Other advantages of voice verification include the reduced waiting time realized by eliminating switching between WAP sessions and voice sessions, and the fact that the user does not need to read, understand, or remember a written code.
The user communicates with the navigation service 2408, which communicates with the device management service 2402. The device management service 2402 includes a device entry database, and a user entry database. An entry in the device entry database is accessed for the calling device 2406, or if there is no entry one is created using a login and password. The device management service 2402 communicates with other services, such as the session management service 2410, the cookie management service 2412, and the single sign-on service 2414.
In one embodiment, when messages are sent to a telephone number belonging to a wireless device 2406, the web identifier to which the message should go is already known. When the user registers for a data session in the wireless device 2406, they enter their telephone number and a page is returned to that device just as in a normal data sessions action. This is in contrast to the traditional method of sending an alert message, including a code, to the calling device. There is a telephone number in the return pages part of the link. The user clicks that link to make a telephone call into the system. When the telephone call is made, the caller identification (ID) is captured and mapped to the user's telephone number. If the number matches what the user entered, an association is made between the telephone number and the device ID from the device or from the registration service.
In another embodiment, the user speaks a special code. In either case (whether the user speaks a code or the code is placed beneath the link) that special code is typed in automatically and transparently to the user. In this way the wireless device's telephone number is verified as being correct. The wireless device's identifier has already been obtained through the data session, so that the telephone number can then be mapped through the caller ID or through the telephone number that the user entered.
To summarize, the user simply enters the data session using the telephone number and the call is returned to the calling device with a link for coding the caller ID. Then that caller ID is mapped with the user telephone number. In the process of verifying the telephone number, transparently to the user, a mapping between the telephone number and the data session is established by mapping the code identifier to the caller ID.
Sometimes the caller ID is not obtainable through a telephone call. In that case, one course of action is to code the wireless device and require the user to say a particular password to verify the code. Alternatively, a message is sent directly to the wireless device and the wireless device enters the code to continue processing.
In one embodiment, the device management service 2402 includes a set of methods which use a voice channel telephone call to verify the mobile telephone number (mTN) associated with a device's SubnoID, or with the cookie, or with state variables generated from the registration service. After a device's SubnoID has been collected by a WAP site and the user has claimed a mTN, the wireless application protocol (WAP) site facilitates the connection of a voice call between that device and a voice extensible markup language (VoiceXML) or proprietary telephony platform. This connection provides primary verification of the claimed mTN. The WAP site waits a predetermined amount of time to receive the verification from the telephony platform. To improve scalability and security, secondary verification in the form of a shared code can also be provided.
The device management service 2402 is implemented either with the device placing a call to the telephony platform, or with the telephony platform placing a call to the device. In the former implementation, the automatic number identification (ANI) feature of the public switched telephone network (PSTN) is used for primary verification. The WAP site uses a wireless telephony application interface (WTAI) function to assist the user in placing a call to the telephony platform. The telephony platform sends a message to the WAP site indicating the ANI of the caller. In the latter implementation, the WAP site provides the user with a code. The site then sends a message to the telephony platform directing it to place a call to the mTN claimed by the user. If the user answers the call, they are directed to provide the code. The telephony platform then sends a message to the WAP site with the provided code.
Secondary verification methods depend upon whether the device places or receives the telephone call. If the device places the telephone call, three methods are available. In one method, the WAP site can dial one of several telephone numbers to reach the telephony platform, and the platform sends a message to the WAP site containing both the ANI as well as information as to which telephone number was dialed. Alternatively, the WAP site can use the WTAI “SEND DIGITS” function to send a code to the telephony platform as part of the call by the device. In another alternative method, the WAP site can provide the user with a code. The telephony platform asks the user for the code. The telephony platform provides both the ANI and information about the code it received in the message it sends to the WAP site. This code could be numeric or it could be a name, word, phrase, or any other form of information that can be recognized by the telephony platform.
If the device receives the call from the telephony platform, the user must provide the code. Again, the WAP site provides the user with a code. The telephony platform asks the user for the code. The telephony platform provides both the ANI as well as information about the code that it received in the message it sends to the WAP site. Again, this code could be numeric or it could be a name, word, phrase, or any other form of information that can be recognized by the telephony platform.
The telephony platform may be implemented, for example, as a VoiceXML script. As the traffic for this management application is negligible, the cost for providing this service is significantly reduced in a hosted environment.
Alerts allow an application to notify users of relevant events, and provide the mechanism for users to respond accordingly. The messaging service 2502 shown in
The messaging service 2502 is an action-oriented wireless alert management service that supports unlimited levels of escalation. It is used to manage the wireless delivery of alerts and responses to alerts, as well as the escalation process. The messaging service 2502 does not generate alerts. The generation of alerts is done by any higher level application that uses the messaging service 2502 as a subrate system. Examples of such applications include stock alerts, calendar alerts, etc. The messaging service 2502 provides the wireless network interfaces required to deliver alerts via SMS, WAP, IVR etc. The messaging service 2502 supports guaranteed and scheduled delivery, email support, broadcasting, multicasting with acknowledgement, and an unlimited escalation process. Each alert can be acknowledged via an acknowledge URL registered by the application. Multicasting allows the response URL and acknowledgement URL to track whether each user in the multicasting list (e.g. in a marketing survey or poll) has received and/or responded to the message. Time-based actions are invoked in the event that the intended recipient of an alert does not respond to it. These time-based actions are URL driven and can provide additional network-based requests. The network-based requests can, in turn, interface with the messaging service 2502, causing unlimited escalation. For example, if there is no response to a WAP message within two minutes, the message is resent to SMS, email, and pager.
The messaging service 2502 separates alert management and delivery from alert generation with an open XML over HTTP interface. This allows remote alert management as well as the support of multiple applications from multiple domains on the same messaging service 2502 platform. The messaging service 2502 is augmented with carrier network knowledge, such as which telephone number belongs to which carrier using which WAP identifier, which WAP push gateway is used to push WAP alerts, and which a short message service center (SMSC) is used to receive SMS messages. This allows applications to concentrate on delivering alerts to telephone numbers without having to handle network issues, such as choosing a network to send messages to.
The final style-sheets are used by the presentation service (as shown in
Previous tools usually focus on transforming one data format into another data format. The transformation process is often guided by internal style-sheets that are built into the process. In contrast, the template generator 2602 takes the source data format and the destination format as input and produces the style-sheets externally. The external style-sheet approach allows modularization between the tool and the presentation service. Any change of wireless device (e.g. new telephone size or new telephone UI) or display format (e.g. WML 2.0 or XHTML) will not affect the presentation service, but only the style-sheet generator. To use the template generator 2602 in one embodiment, the user selects a display type, such as PALM™ or NOKIA™, and a form type, such as “list”. The user may view a simulated screen to determine whether the style-sheet is satisfactory.
As part of the wireless network communication architecture 104, The XSL style-sheet template generator is part of an application development platform (e.g. presentation services, application editor/navigation-modeler, transcoder etc). It can be used with the transcoder to produce design-time style-sheets for the transcoded XML data source from hypertext markup language (HTML). These style-sheets can then be used by the presentation service for run-time transformation based upon device characteristics.
A more usable approach is to allow end users to select from their own previous inputs. The additional use of earlier web-based inputs extends this approach to encompass more of the user's previous inputs and allows WAP/HDTP sites to effectively support additional functionality in a usable manner. As shown in
In one embodiment, the prefill service 2710 is a service added to existing applications without affecting the user interface design of the existing application. The user is presented with multiple input selections to choose from. The user selections are placed in a separate “deck” to avoid any deck size limitation. Companion web site inputs can be used to populate the input fields in a WAP site.
In one embodiment, the prefill application tracks user inputs in the wireless environment and uses the inputs to prefill input fields in a WAP/HDTP application. If an input field had a previous entry, a “prefill select card” is dynamically created directly preceding the original input card. The prefill select card lists all of the values that have previously been used with that field. If a prefill is selected, the input card is skipped and the user goes directly to a results card. An option to directly enter a value (labeled “other”) is included at the top of the prefill select card. Selecting “other” goes to the standard input card.
Entries are listed in the order of occurrence. The most recent input is listed first, the second most recent is listed second, etc. Some prefills have a time value associated with them. For example, flight numbers and package tracking numbers are only meaningful for a certain period of time. Using recency for prefill ordering is very effective for this class of prefill.
Many WAP/HDTP based applications act as an additional channel for existing web sites. In one embodiment, inputs are mapped from a web site into a companion WAP/HDTP application. This requires a web site to which the user must log on. Examples include portals, stock brokers, travel sites, and banks. Preferably, an input field in the web site is associated with an input field in the WAP/HDTP site. When the user is identified, their previous inputs to the web site are displayed in the prefill select card of the WAP/HDTP site. Depending upon deck size, the prefill select cards can be separated from a long input deck and prefetched as a separate deck. In one embodiment, prefetching is done using either HDML or WML 1.1 with UP.Browser 4.x or later, using known extensions, such as OpenWave™ extensions. This allows navigation between the input deck and the prefill select cards without significant degradation in response times.
Another application that enhances the experience of the wireless device user is the password management service 2802 illustrated in
In the corporate environment, employees often have multiple passwords that are used to access different systems. These passwords often have specific restrictions on their format to reduce the probability of them being guessed or cracked by an automated password-guessing program. Restrictions vary between and within companies but passwords often involve a minimum of eight characters with one or more “special” characters. This presents a significant usability obstacle to accessing corporate applications over the wireless web. Input using a WAP telephone browser is difficult because characters and particularly special symbols take a long time to type and errors are often introduced.
The password management service 2802 provides a security method that makes it easy for employees to use their own passwords in an easier form for input using a wireless device. Security is maintained by using information about the device that is attempting to access the corporate application. In a sense, the wireless device acts as a physical key that, when combined with a simplified password, allows secure access in much the same way as a bankcard and a personal identification number (PIN).
In addition, maintaining passwords is a critical requirement for highly secure businesses. Many corporations require that passwords be changed on a regular basis. Using a PIN code that is based on a password makes the PIN code easy to remember. Even if passwords change frequently, this method does not impose any additional difficulty for the end user to remember additional passwords. The password management service 2802 allows an entire class of corporate applications to be accessed securely and efficiently.
It is also possible to integrate the password management service 2802 with message or email alerts to enable an end user to be alerted when repeated attempts are made to access their account. These alerts occur in real time and require an appropriate response (e.g., a full length password) within a set amount of time or the SubNo.ID is automatically deactivated. The actionable alert also has the option to immediately lock a device that is attempting to gain entry.
In one embodiment, the first four to eight characters of the standard password for a user/application are used with the characters transformed into the matching digits on the telephone keypad. The digits, along with the SubNo.ID are used to control access. Though it is possible to fake the SubNo.ID, this would require the attacker to discover the SubNo.ID of the employee, and also discover the short form of the password. If the wireless device is lost, the SubNo.ID could be deactivated through the use of the device management service 2402 (
In one embodiment, the password management service 2802 is an enhanced application of the single sign-on service previously described. It is an additional service that is specifically developed to assist employees of corporations that have stringent security requirements. The password management service 2802 requires integration with the password database that is currently being used by a corporation.
An embodiment of an integrated wireless data and fax method and system, or fax service 2900 is illustrated in
In one pull case, an end user is looking for information from a customer application (at a customer public WML site). After seeing an abstract of desired information, the end user requests a fax. At this point, the end user specifies the destination fax number or confirms/edits a number already in their profile, and optionally specifies cover page information.
In another pull case, an end user receives an alert (e.g., a browser alert, SMS alert, email alert, or voice) from a customer application. After reading the abstracted information, the end user requests a fax. At this point, the end user specifies the destination fax number or confirms/edits a number already in their profile, and optionally specifies cover page information.
In another pull case, an end user that is an employee of a customer locates important information on the customer's internal WML site and chooses to have that information faxed to another end user. The employee then specifies the destination fax number or confirms/edits a number already in their profile, and optionally specifies cover page information.
In one push case, a customer application sends a fax, typically at a scheduled time. The customer application faxes information to an arbitrary end user as part of an escalation process. Alternatively, the customer application faxes information to arbitrary end users as part of normally scheduled information transmission.
The fax service 2900 is based upon the WAP standards. The fax service 2900 consists of a set of software and hardware modules that allow the users of WAP-enabled mobile devices to request that a fax be sent while engaged in a WAP data session. The fax service 2900 converts a web document into image files of TIFF format and then faxes the image files using a built-in fax server or sends the image files as email attachments to an external fax server/service via a simple mail transfer protocol (SMTP) interface. If a default fax number has been pre-defined and is accessible from the user's profile data (known as “the cookie), the user may employ a one-click-to-fax method for sending the fax. Otherwise, the user may specify any G3-based fax number or select it from a telephone book entry. The fax service 2900 can be used in conjunction with other applications or services described herein, such as the single sign-on service. The fax service 2900 can also be effectively used as a stand-alone application that is part of a larger WAP-based platform.
The IVR/FAX server 2910 is further illustrated in
In one embodiment, if the user has a default fax number stored in the user's profile data (the cookie), the device management service 2907 (
The overall flow of the fax service, the user interface, and the implementation of the fax service will now be discussed in more detail with reference to
A customer (e.g., a large corporation or a provider of a specific Internet service) provides a customer application that sends the fax agent the required parameters via an HTTP request. For instance, this application could be WML software for the callers who use their services. The software can allow the callers to traverse menus on their handset, and select a document to send to a specified fax number. When the caller presses a fax softkey, the HTTP request is sent to the fax agent.
In one embodiment, a WebFax™ component of the fax service uses Microsoft Internet Explorer Automation™ to navigate to the requested URL and prints the page through the Peernet™ Doc-to-Fax printer driver, which creates a TIFF file suitable for faxing through GammaLink™ API calls.
The fax agent acts as a link between the customer application and the WebFax™ component. The fax agent uses the standard Internet HTTP protocol to communicate with WebFax™, as well as to return status codes to the customer application. WebFax™ is the component responsible for sending the fax itself. It acts as an HTTP server and is activated when it receives a request that a document be faxed to a given number. Legal documents are documents that can be displayed with a web browser not using any special plug-in (such as Acrobat™ reader).
In one embodiment, the fax service operates on a Windows 2000 Professional™ system with the GammaLink™ fax system from Dialogic™. The third party software required includes Dialogic™ software “System Release v5.01” with SDK option, and Blackice™ Monochrome Printer Driver for NT 4.0 and Win2000.
In one embodiment, the fax service requires a Pentium III personal computer with 256M RAM. The fax service operates with a GammaLink™ CPi/400 PCI 4-channel board, or a CPi/200 PCI two channel board.
The fax service provides a SMTP option to route the fax documents requested to an external fax server/service instead of using the GammaLink™ based fax capability. The SMTP option of the fax service requires an SMTP server running on the installed system and an SMTP client program running such as Microsoft Outlook™. The SMTP option of the fax service requires the interfacing external fax server/service to extract the fax number from a subject line and to support email attachments of TIFF file format.
The fax service accepts HTTP requests from the customer application. The WebFax™ component of the fax service accepts HTTP requests of a similar format. The HTTP request must contain the required parameters and may contain optional parameters. A minimal request from the customer application to the fax agent has the form:
The corresponding request from the fax agent to WebFax™ has the following format:
The underlined fields are specific to a user request. This example also shows the required syntax.
The faxnum argument, the phone number of the target fax machine, must be first and occurs after a question mark. The other arguments can be given in any order and must be separated by ampersands.
The URL argument contains any legal URL. The request may contain one or more URL arguments for a single fax transaction, but there must be at least one. If there is more than one, they will be processed sequentially. The customer may use the first URL as a cover sheet and subsequent URLs as content.
The spqr argument specifies a security code. WebFax™ and the fax agent both calculate a value, a VPLSecurityLock object. If the values match, WebFax™ accepts the request.
The ID argument specifies a request ID that is included in the final success or failure reply from WebFax™ to the fax agent. This ID is the request ID sent by the customer application to the fax agent. The fax agent, once it gets the ID back from WebFax, can return this ID to the customer application so that the application can make a request of the messaging service to send the status alert to the correct user.
Optional arguments include:
URL syntax requires encoding of special characters. The fax agent returns the status of a fax to the customer application via standard HTTP request.
Several fax-related fields, to be used as default values, must be accessible in a database. These fax related fields include: the priority, retry duration, retry interval, notafax retry duration, and notafax retry interval. These fields can be defaults, but if the client software allows the caller to specify these values, then the specified values will override the system values.
The fax agent acts as a link between the customer application and the WebFax™ component. It uses the standard internet HTTP protocol to communicate with WebFax, as well as to return status codes to the customer application.
Except in the event of system failure or network errors, WebFax™ will always respond to the fax agent, and the agent will always transmit a message to the customer application indicating fax status.
When the fax agent receives a request from the customer application, it verifies license currency, and then packages the information received from the application into a request to WebFax™.
The faxnum, URL, and ID fields are sent as received from the application. The servlet validates the customer's security code, and computes a second security code, sent as the spqr parameter.
WebFax™ will examine the fax request and respond with a status code and message. If the status code indicates an error, the fax agent will notify the customer application of the error, and that will end the transaction. If the status indicates that WebFax™ successfully accepted the request, the fax agent takes no further action at that time.
If the request to WebFax™ cannot be completed (e.g., due to host shutdown or network problems), a message will be sent to the customer application indicating that the request failed for system reasons, not because it was a malformed request.
When the fax is finally transmitted, or cannot be successfully transmitted, WebFax™ will send an http request, and the status and message will be relayed to the customer application. That concludes the fax transaction.
WebFax™ replies immediately to the fax agent by transmitting a text file containing a numeric code and an explanation of the code. The standard HTTP status code of 200 should be present in the header, regardless of the contents of the text file returned. If the fax request was well formed, WebFax™ returns a file, fax service.html, containing:
If the reply was anything other than “0 accepted”, there will be no further reply from WebFax™ regarding the failed request. If the request is accepted, WebFax™ will send one final completion or failure message to the IP address of the fax agent, in the form of:
The transmitted fax consists of the contents of the Internet Explorer™ windows in which the web documents were rendered. If any document is longer than the window, the entire document will nonetheless be converted to a TIFF file and faxed. If a web document contains frames, each frame will be appended sequentially to the TIFF file as if it were a separate document; the original layout of the web page is not preserved. All such TIFF files will be sent within one fax session.
A VPLSecurityLock object is used for enhanced security for fax service. WebFax™ accepts requests via HTTP, making it vulnerable to spurious hits. Therefore, each request from customer software provides a security code, calculated using the VPLSecurityLock object. The fax agent will verify this code's validity. Each request from the fax agent to WebFax™ contains a security code that is validated by WebFax™. These two codes will probably never be the same.
A mobile wallet service 3002 is illustrated in
The mobile wallet service 3002 is secure. If an application tries to use the mobile wallet service 3002, it must provide a previously assigned ID and password, ID and password signature, or ID and encrypted password.
Unlike traditional mobile wallet services, the mobile wallet service 3002 is an extensible system. In one embodiment, the mobile wallet service 3002 requires the partnership of ecommerce sites operated by merchants such as ebusinesses 3012, 3014, and 3016. In one embodiment, the mobile wallet service 3002 is integrated with the single sign-on service previously described. The user of the wireless device 3006 accesses the mobile wallet service 3002 through the device management service 3008 and the single sign-on service 3010. The user presents wallet information on request to the partnered sites of ebusinesses 3012, 3014, and 3016. New types of wallet information can be easily defined in the mobile wallet service 3002. This enables the support of many different application domains. The mobile wallet service 3002 also supports multiple data formats. Wallet information can be formatted in HTML, WML or XML. The wallet information is sent to requesters in either HTML or data stream.
In one embodiment, the wallet information consists of one or more wallet entities. These entities are generalized into categories, such as address, card etc. For example, a driver license contains information on the driver license card, and the address of the driver. The information is associated with types. A type is defined by: an attribute, such as banking, driving, shipping, etc.; usage, such as business, personal, etc.; and form, such as address, card, coupon, etc. This modeling of wallet information allows flexible use of the mobile wallet service 3002 in many different business domains. For example, an address can be a billing address, a shipping address, a credit card address or a health club card address. A card can be a banking card, a driver's license, or a health club card. The user can also define new wallet entity types to enable the mobile wallet service 3002 in new business domains. This modeling reduces the effort required to maintain wallet data. For example, multiple cards can share an address.
Wallet information can be presented in multiple formats upon retrieval, such as HTML, WML, or XML. This allows the user to manage wallet information using different devices and allows business providers to easily retrieve and use wallet data.
The mobile wallet service 3002 provides multiple levels of access control. Using password signature to validate a requester prevents illegal attempts to retrieve wallet information by people who know the password of that requester. Using an encrypted password to validate a requester prevents illegal attempts to retrieve wallet data by people who are able to obtain request data over a network. The mobile wallet service 3002 system also provides secure wallet data transportation in secure sockets layer (SSL) or encrypted version over hypertext transfer protocol (HTTP).
The directory search method uses the directory service 3102 to retrieve most frequently called numbers or a short-term history list (last N calls). In one embodiment front-page listings are based upon an external location-gateway-based service. Each network-based call log entry is tagged for location identifiers such as city names or area codes. The messaging service (see
The directory service 3102 can be used, for example, to enable Fortune 1000 companies to provide unique WAP-based directory access to their corporate directories. The directory service 3102 provides visual access to server-side directories on both WAP-enabled terminals and non-WAP terminals. These directories can contain corporate entries, personal entries, or white pages. The entries can be telephone numbers, FAX numbers, and/or email addresses. The directory service 3102 entries can be managed (add/delete/change) either from the desktop PC 3118, or from the WAP enabled wireless device 3106. To secure these entries, access to the WAP directory can be protected by pass code. Further the WAP directory service enables services like call service, instant messaging, follow-me applications, and collaborative services like chat and conferencing.
Through the user interface 3120, names can be accessed or managed through “T9”-like syntax in which a single key click is used to represent a single letter. For example, the key sequence for “CHANG” would be “24264”. The possible matches in the telephone book are presented to the user as links with soft-keys for “Call” and “Cancel”. When a name is found, it is presented to the user. The user pushes “Call” to place the call. Frequently selected names are stored in the outgoing call log in a server so that when the same name is requested, that name will be presented first. This is especially useful for names that have several possible matches. Also, the name is added to the user's frequently called list. This automated option allows the user to construct a telephone book without actually having to program the entries.
In one embodiment, when a call is placed, for example by pressing the “Call” key, a URL link from the voice channel homepage provisioning service (see
In one embodiment, the directory service 3102 menu has a numbered list to display entries for the frequently called list, “spell it”, etc. The list contains directory numbers that are most frequently called by the user. If the current location of the user is available to the directory service, the list may be further sorted based on location. For example, if the user is from Austin and is now traveling in Pleasanton, directory entries that contain the area code for Pleasanton will be displayed first. When the user selects the call list option, a list of links is returned. Each link corresponds to a name. To place a call, the user clicks on one of these links.
Another feature of the WAP-based directory service 3102 allows the user to spell the name of the person he wants to call. Several possible names with their associated links are returned in the WML page that is returned to the user. The user selects one of the names. The WTA server 3112 logs the outgoing call. In various embodiments, the user may enter the name in one or more ways, such as: entering a T9-like syntax to represent name, e.g. 24264 for CHANG; a three character list (e.g., ABC, DEF, etc) such that the user picks an entry and the last names that are contained in the three alphabet list are returned to the user; and for a non-WAP terminal, speech recognition access is provided.
When the appropriate name is returned to the user, an option is provided to display or not to display the associated telephone number. Each name that is displayed is associated with a URL link. The user is provided with the option to place the call, or cancel. If the user chooses to place the call, a WML card with a “WTAI make call” is re-directed to the WTA server 3112. The call originated at the client completes to the CTI/IVR. The WTA server 3112, with the help of the CTI/IVR, actually places the call to the called party. The WTA server 3112 logs information of the outgoing call in the user's call log. Various enhancements include group lists and most frequently called lists maintained on a per-user basis, and selective synchronization between the WAP client and the server telephone books.
Another enhanced service in one embodiment of the architecture (see
In one embodiment, the method for creating new user interfaces allows the user to change the state of an item in a select list. The select list, with the addition of either a text symbol or a graphical symbol, is used to display the item. Items can be selected by scrolling down and pressing a softkey or by pressing a number on the wireless device. When an item is selected, its state is toggled. In the case of a radio button display, the state of the item that was originally selected is also toggled. For the text version the symbol is enclosed in brackets or parentheses and the symbol is presented when the item is selected. When the item is not selected, the brackets or parentheses have a space character instead of the text symbol. For the graphical version, a box is used for the multiple select list. When an item is selected the box changes to a box with an “x” through it. For radio buttons there is an empty circle graphic for non-selected items and a filled circle for selected items.
The method uses non-displaying cards and variables to create primitive logical manipulations. The state of each item is tracked by a variable, and based upon the state of the item, the deck branches to one of several non-displaying cards that toggles the state of the variable. After changing the values of the variables, the original “display” card is presented to the user. To the user it simply appears that the display is toggling between values.
Another feature is the embedding of heading titles into a select list to make it appear that there are multiple lists on a single WML page. This is done by using a carriage return on the last select item in a section of the page and appending the title of the next heading onto the end of that select list item. This appears visually as a separate heading, when in reality it is part of the last select item. This is useful for breaking up a card so that multiple, independent items can be presented. A card can be made up of a multiple select list and a set of radio buttons. The multiple select list and the set of radio buttons behave to the user as if they were separate “items”, but they are all part of the same WML select list.
In one embodiment, the method for creating new user interfaces is an enhancement to XML based template generation (see
Unless the context clearly requires otherwise, throughout the description and the claims, the words “comprise,” “comprising,” and the like are to be construed in an inclusive sense as opposed to an exclusive or exhaustive sense; that is to say, in a sense of “including, but not limited to.” Words using the singular or plural number also include the plural or singular number respectively. Additionally, the words “herein,” “hereunder,” and words of similar import, when used in this application, shall refer to this application as a whole and not to any particular portions of this application.
The above description of illustrated embodiments of the invention is not intended to be exhaustive or to limit the invention to the precise form disclosed. While specific embodiments of, and examples for, the invention are described herein for illustrative purposes, various equivalent modifications are possible within the scope of the invention, as those skilled in the relevant art will recognize. The teachings of the invention provided herein can be applied to other communications systems, not only for the system described above.
The elements and acts of the various embodiments described above can be combined to provide further embodiments. Aspects of the invention can be modified, if necessary, to employ the systems, functions and concepts of the various patents and applications described above to provide yet further embodiments of the invention.
These and other changes can be made to the invention in light of the above detailed description. In general, the terms used in the following claims should not be construed to limit the invention to the specific embodiments disclosed in the specification, unless the above description explicitly defines such terms. Accordingly, the actual scope of the invention encompasses the disclosed embodiments and all equivalent ways of practicing or implementing the invention under the claims.
While certain aspects of the invention are presented below in certain claim forms, the inventors contemplate the various aspects of the invention in any number of claim forms. For example, while only one aspect of the invention is recited as embodied in a computer-readable medium, other aspects may likewise be embodied in a computer-readable medium. Accordingly, the inventors reserve the right to add additional claims after filing the application to pursue such additional claim forms for other aspects of the invention.
|Cited Patent||Filing date||Publication date||Applicant||Title|
|US3701851 *||Dec 9, 1970||Oct 31, 1972||Bell Telephone Labor Inc||Switching voice and data communications simultaneously over a common path|
|US5353328||Feb 3, 1993||Oct 4, 1994||Nokia Mobile Phones Ltd.||Data adapter for a radiotelephone|
|US5586166||Aug 18, 1995||Dec 17, 1996||Alcatel N.V||Chip card|
|US5742910||May 23, 1995||Apr 21, 1998||Mci Corporation||Teleadministration of subscriber ID modules|
|US5818824||Aug 30, 1996||Oct 6, 1998||Interwave Communications International, Ltd.||Private multiplexing cellular network|
|US5854982||Aug 21, 1995||Dec 29, 1998||Motorola, Inc.||Communication system architecture and method of routing therefor|
|US5901359||Jan 3, 1997||May 4, 1999||U S West, Inc.||System and method for a wireline-wireless network interface|
|US5903832||Dec 21, 1995||May 11, 1999||Nokia Mobile Phones Llimited||Mobile terminal having enhanced system selection capability|
|US5930701||Oct 17, 1996||Jul 27, 1999||Telefonaktiebolaget L M Ericsson (Publ)||Providing caller ID within a mobile telecommunications network|
|US5940490||Aug 23, 1995||Aug 17, 1999||Stratus Computer Corporation||Call processing to provide number portability|
|US5943620||Dec 9, 1996||Aug 24, 1999||Ericsson Inc.||Method for associating one directory number with two mobile stations within a mobile telecommunications network|
|US5987318||Jul 31, 1996||Nov 16, 1999||Ericsson Inc.||Call conference within a home zone|
|US5987323||Jul 17, 1995||Nov 16, 1999||Nokia Telecommunications Oy||Starting a short message transmission in a cellular communication system|
|US5987325||May 19, 1997||Nov 16, 1999||Motorola, Inc.||Multiple smart card phone and method|
|US6009325 *||Feb 1, 1995||Dec 28, 1999||Motorola, Inc.||Method of and apparatus for operating a cellular phone in one of two modes|
|US6014561||May 6, 1996||Jan 11, 2000||Ericsson Inc.||Method and apparatus for over the air activation of a multiple mode/band radio telephone handset|
|US6052604||Oct 3, 1997||Apr 18, 2000||Motorola, Inc.||Exchange which controls M SIMs and N transceivers and method therefor|
|US6055441 *||Apr 30, 1996||Apr 25, 2000||International Business Machines Corporation||Systems and methods for facsimile communication over a cellular radiotelephone communications link|
|US6058309||Aug 9, 1996||May 2, 2000||Nortel Networks Corporation||Network directed system selection for cellular and PCS enhanced roaming|
|US6075855||Feb 9, 1998||Jun 13, 2000||Ag Communication Systems Corporation||Method of accessing a SCP in an ISUP network with partial release|
|US6085084||Sep 24, 1997||Jul 4, 2000||Christmas; Christian||Automated creation of a list of disallowed network points for use in connection blocking|
|US6138005||Jan 22, 1998||Oct 24, 2000||Samsung Electronics Co., Ltd.||Method for verifying personalization in mobile radio terminal|
|US6138009||Jun 16, 1998||Oct 24, 2000||Telefonaktiebolaget Lm Ericsson||System and method for customizing wireless communication units|
|US6148197||Mar 6, 1998||Nov 14, 2000||Sbc Technology Resources, Inc.||Intelligent roaming system with over the air programming|
|US6163701||Jul 25, 1997||Dec 19, 2000||Motorola, Inc.||System and method for providing location information of a mobile station in a communication system|
|US6185295||Feb 18, 1998||Feb 6, 2001||Nokia Mobile Phones Limited||Phone number database for a phone|
|US6185436||Mar 27, 1997||Feb 6, 2001||Siemens Information And Communication Networks, Inc.||Wireless communication system|
|US6192255||Dec 15, 1992||Feb 20, 2001||Texas Instruments Incorporated||Communication system and methods for enhanced information transfer|
|US6195532||Jun 28, 1996||Feb 27, 2001||At&T Wireless Srcs. Inc.||Method for categorization of multiple providers in a wireless communications service environment|
|US6208864||Dec 30, 1998||Mar 27, 2001||Telcordia Technologies, Inc.||Establishing calls and processing on-going calls in fixes and cellular networks|
|US6356756||Aug 26, 1998||Mar 12, 2002||Bellsouth Corporation||Method and system for routing calls to a wireless telecommunications services platform|
|US6424945 *||Dec 15, 1999||Jul 23, 2002||Nokia Corporation||Voice packet data network browsing for mobile terminals system and method using a dual-mode wireless connection|
|US6456845||Oct 27, 2000||Sep 24, 2002||Tekelec||Methods and systems for observing, analyzing and correlating multi-protocol signaling message traffic in a mobile telecommunications network|
|US6456859||Mar 2, 1994||Sep 24, 2002||Alcatel Radiotelephone||Method of delivering a telephone number associated with a telephone subscription, and telephone sets and mobile telephones implementing the method|
|US6463298||Sep 29, 1997||Oct 8, 2002||Qualcomm Incorporated||Method of acquiring an alternate communication system upon failure of reverse link communications|
|US6466786||Dec 4, 1997||Oct 15, 2002||Nokia Telecommunications Oy||Call set-up in mobile communications system|
|US6505050||Oct 12, 2000||Jan 7, 2003||Lucent Technologies Inc.||Method and apparatus for suppressing route request messages for wireless gateway applications|
|US6574481||Jul 11, 2000||Jun 3, 2003||Alcatel Usa Sourcing, L.P.||System and method for application location register routing in a telecommunications network|
|US6603761||Jan 7, 2000||Aug 5, 2003||Lucent Technologies Inc.||Using internet and internet protocols to bypass PSTN, GSM map, and ANSI-41 networks for wireless telephone call delivery|
|US6603968||Jun 22, 2001||Aug 5, 2003||Level Z, L.L.C.||Roaming in wireless networks with dynamic modification of subscriber identification|
|US6611516||Jun 21, 1999||Aug 26, 2003||Nokia Telecommunications Oyj||Short message service support over a packet-switched telephony network|
|US6628934||Jul 12, 2001||Sep 30, 2003||Earthlink, Inc.||Systems and methods for automatically provisioning wireless services on a wireless device|
|US6671523||Oct 2, 2000||Dec 30, 2003||Siemens Aktiengesellschaft||Method for operating a communication terminal|
|US6684073||Aug 31, 1999||Jan 27, 2004||Swisscom Mobile Ag||Signalling method and conversion device for telecommunications networks|
|US6693586||Aug 10, 2002||Feb 17, 2004||Garmin Ltd.||Navigation apparatus for coupling with an expansion slot of a portable, handheld computing device|
|US6725031 *||Dec 10, 2001||Apr 20, 2004||Telemac Corporation||Method and system for data rating for wireless devices|
|US6738622||Mar 29, 1999||May 18, 2004||Swisscom Ag||Roaming method and devices appropriate therefor|
|US6738636||Apr 12, 2001||May 18, 2004||Microsoft Corporation||Method for providing access to data|
|US6764003||May 9, 2000||Jul 20, 2004||Swisscom Mobile Ag||Transaction method and selling system|
|US6782264||Jul 18, 2001||Aug 24, 2004||Trueposition, Inc.||Monitoring of call information in a wireless location system|
|US6795444||Oct 26, 1999||Sep 21, 2004||Telefonaktiebolaget L M Ericsson (Publ)||System and method for providing wireless telephony over a packet-switched network|
|US6856818||Jan 19, 1998||Feb 15, 2005||Orange Personal Communications Services Ltd.||Data store for mobile radio station|
|US6876860||Sep 6, 2000||Apr 5, 2005||Siemens Aktiengesellschaft||Method for implementing a call-back service in a mobile radio network|
|US6920487||Dec 20, 2000||Jul 19, 2005||Starhome Gmbh||System and methods for global access to services for mobile telephone subscribers|
|US6925299||May 5, 1999||Aug 2, 2005||Starhome Gmbh||System and method for providing access to value added services for roaming users of mobile telephones|
|US6947738 *||Dec 21, 2001||Sep 20, 2005||Telefonaktiebolaget Lm Ericsson (Publ)||Multimedia messaging service routing system and method|
|US6961559||Aug 2, 2000||Nov 1, 2005||At&T Corp.||Distributed network voice messaging for wireless centrex telephony|
|US6963543||Jun 29, 2001||Nov 8, 2005||Qualcomm Incorporated||Method and system for group call service|
|US6968383||Jul 17, 1998||Nov 22, 2005||Swisscom Mobile Ag||Method for broadcasting addressed data to a plurality of users|
|US6975852||Mar 16, 2000||Dec 13, 2005||Starhome Gmbh||System and method for roaming for prepaid mobile telephone service|
|US6978156||Mar 6, 1999||Dec 20, 2005||Giesecke & Devrient Gmbh||Mobile radio telephone system having an identity which can be dynamically changed|
|US7020479||May 14, 2002||Mar 28, 2006||Swisscom Mobile Ag||Method and system for preparing and transmitting SMS messages in a mobile radio network|
|US7139570||Mar 23, 2004||Nov 21, 2006||Starhome Gmbh||Preferred network selection|
|US7184764||Feb 7, 2002||Feb 27, 2007||Starhome Gmbh||Method and apparatus for supporting cellular data communication to roaming mobile telephony devices|
|US7231431||Apr 4, 2005||Jun 12, 2007||Starhome Gmbh||System and methods for global access to services for mobile telephone subscribers|
|US20010034225 *||Feb 12, 2001||Oct 25, 2001||Ash Gupte||One-touch method and system for providing email to a wireless communication device|
|US20020009199||Jun 29, 2001||Jan 24, 2002||Juha Ala-Laurila||Arranging data ciphering in a wireless telecommunication system|
|US20020012351||Dec 20, 2000||Jan 31, 2002||Carmel Sofer||System and methods for global access to services for mobile telephone subscribers|
|US20020019246 *||Jun 14, 2001||Feb 14, 2002||Forte Stephen P.||Method and apparatus for communicating via virtual office telephone extensions|
|US20020037708||Sep 24, 2001||Mar 28, 2002||Roke Manor Research Limited||Access authentication system|
|US20020055350 *||Jul 20, 2001||May 9, 2002||Ash Gupte||Apparatus and method of toggling between text messages and voice messages with a wireless communication device|
|US20020087631||Jan 2, 2002||Jul 4, 2002||Vikrant Sharma||Email-based advertising system|
|US20020099799 *||Jun 19, 2001||Jul 25, 2002||Kolsky Amir D.||Method and system for universal and transparent access to heterogeneous resources|
|US20020101858||Jan 31, 2001||Aug 1, 2002||Stuart Thro W.||Communication services through multiple service providers|
|US20020101859||Feb 1, 2001||Aug 1, 2002||Maclean Ian B.||Communicating between nodes in different wireless networks|
|US20020160763||Apr 27, 2001||Oct 31, 2002||Gaurav Mittal||Apparatus, and an associated method, by which to provide operation parameters to a mobile station|
|US20020187780||May 15, 2001||Dec 12, 2002||Novatel Wireless, Inc.||Systems and methods for intelligent inter-system handoff|
|US20020191575||Jun 17, 2002||Dec 19, 2002||Broadwave, Inc.||Method and apparatus for converging local area and wide area wireless data networks|
|US20020196775||Jun 20, 2001||Dec 26, 2002||Markku Tuohino||Routing a call between different types of networks|
|US20030017843||Dec 27, 2000||Jan 23, 2003||Gerard Noblins||Method for multple use of a radiotelephone, and radiotelephone system corresponding subscriber identification module and presence detecting device|
|US20030050047||Sep 12, 2002||Mar 13, 2003||Sonera Oyj||Changing a first subscriber identifier to a second identifier|
|US20030051041||Aug 6, 2002||Mar 13, 2003||Tatara Systems, Inc.||Method and apparatus for integrating billing and authentication functions in local area and wide area wireless data networks|
|US20030064723||Oct 2, 2001||Apr 3, 2003||Kaushal Thakker||Local subscriber number and services for non-local wireless subscribers|
|US20030069922||May 23, 2001||Apr 10, 2003||Lakshmi Arunachalam||Network transaction portal to control multi-service provider transactions|
|US20030129991||Jan 10, 2002||Jul 10, 2003||Allison Rick L.||Methods and systems for providing mobile location management services in a network routing node|
|US20030133421||Jan 17, 2002||Jul 17, 2003||Rangamani Sundar||Method, system and apparatus for providing WWAN services to a mobile station serviced by a WLAN|
|US20030139180||Apr 19, 2002||Jul 24, 2003||Mcintosh Chris P.||Private cellular network with a public network interface and a wireless local area network extension|
|US20030208560||Mar 19, 2001||Nov 6, 2003||Casio Computer Co., Ltd.||System and method for distributing advertisements|
|US20030224795||Jun 16, 2003||Dec 4, 2003||Bridgeport Networks, Inc.||Circuit switched cellular network to internet calling with internet antennas|
|US20030229791||Jun 5, 2002||Dec 11, 2003||Sun Microsystems, Inc. A Delaware Corporation||Method for private personal identification number management|
|US20040053610||Sep 4, 2003||Mar 18, 2004||Lg Electronics Inc.||Method and system for mobile number portability service|
|US20040087305||Aug 5, 2003||May 6, 2004||Jiang Yue Jun John||Method and system for cellular network traffic redirection|
|US20040120552||Dec 19, 2002||Jun 24, 2004||Frank Borngraber||Mobile communication terminal with built-in camera|
|US20040131023||Jan 3, 2003||Jul 8, 2004||Otso Auterinen||Communications system and method|
|US20040132449||Jun 6, 2001||Jul 8, 2004||Benjamin Kowarsch||Method and apparatus for permitting a mobile station to operate in a visited network|
|US20040196858||Apr 26, 2004||Oct 7, 2004||Kirk Tsai||Intermediary network system and method for facilitating message exchange between wireless networks|
|US20040229601||May 15, 2003||Nov 18, 2004||Zabawskyj Bohdan Konstantyn||Method and system allowing for one mobile phone number (MSISDN) to be associated with a plurality of wireless devices ('Multi-SIM')|
|US20040236836||Jun 10, 2004||Nov 25, 2004||Barry Appelman||Recipient control of source audio identifiers for digital communications|
|US20050021834||Jun 19, 2003||Jan 27, 2005||Nokia Corporation||System for rendering multimedia messages by providing, in a multimedia message, URL for downloadable software to a receiving terminal|
|US20050047378||May 17, 2002||Mar 3, 2005||Martin Wuschke||Method, device,and software programs for correlating data sets|
|US20050064883||Sep 22, 2003||Mar 24, 2005||Heck John Frederick||Unified messaging server and method bridges multimedia messaging service functions with legacy handsets|
|US20050186939||Feb 14, 2005||Aug 25, 2005||Alon Barnea||Monitoring and management of roaming users|
|US20050186979||Apr 22, 2005||Aug 25, 2005||Tekelec||Methods and systems for providing short message gateway functionality in a telecommunications network|
|US20050215250||May 26, 2005||Sep 29, 2005||Venkatesh Chava||Intermediary network system and method for facilitating message exchange between wireless networks|
|US20050232282||Apr 10, 2003||Oct 20, 2005||Spatial Communications Technologies, Inc||Internet audio gateway|
|US20050250493||Nov 15, 2004||Nov 10, 2005||Shany Elkarat||Terminated call control for roaming cellular telephony|
|US20060003775||Jun 10, 2005||Jan 5, 2006||Bull Jeffrey F||Advanced triggers for location-based service applications in a wireless location system|
|US20060009204||Nov 2, 2004||Jan 12, 2006||Starhome Gmbh||Telephone functionality for generic applications in a mobile handset|
|US20060025129||Jul 28, 2005||Feb 2, 2006||Shlomo Wolfman||Cellular network infrastructure as support for inbound roaming users|
|US20070044010 *||Aug 14, 2006||Feb 22, 2007||Sanghoon Sull||System and method for indexing, searching, identifying, and editing multimedia files|
|1||"Digital Cellular Telecommunications system (Phase 2+); Universal Mobile Telecommunications system (UMTS); General Packet Radio Service (GPRS) Service description; Stage 2 (3GPP TS 23.060 Version 5.4.0 Release 5)" ETSI TS 123 060 V5.4.0, Dec. 2002, pp. 1-207 (XP-014007573).|
|2||"Digital Cellular Telecommunications system (Phase 2+); Universal Mobile Telecommunications system (UMTS); General Packet Radio Service (GPRS); GPRS Tunnelling Protocol (GTP) across the Gn and Gp Interface (3GPP TS 29.060 version 5.4.0 Release 5)" ETSI TS 129 060 V5.4.0, Dec. 2002. pp. 1-102 (XP-002298277).|
|3||3 GPP 29010; 3 GPP TS 29.010 V3.10.0 (Dec. 2002); Technical Specification; 3rd Generation Partnership Project; Technical Specification Group Core Network; Information element mapping between Mobile Station-Base Station System (MS-BSS) and Base Station System-Mobile-services Switching Centre (BSS-MSC).|
|4||3G TS 22.078 version 3.2.0 Release 1999 UMTS CAMEL.|
|5||3G TS 23.278 version 6.0.0. Release 6 UMTS CAMEL-IMS interworking.|
|6||Digital cellular telecommunications system (Phase 2+); Specification of the SIM Application Toolkit for the Subscriber Identity Module-Mobile Equipment (SIM-ME) Interface (GSM 11, 14 version 8.3.0 Release 1999) STSI TS 101 267 V8.3.0, XX, XX, Aug. 2000, pp. 1-69 and pp. 114-115 (XP-002222021).|
|7||GMS 408 on radio interface layer 3; Digital cellular telecommunications system (Phase 2+); Mobile radio interface layer 3 specification (GSM 04.08 version 7.4.2 Release 1998).|
|8||GSM 1111 SIM and Mobile Interface, Aug. 2006.|
|9||GSM 1114 SIM Toolkit, Aug. 2006.|
|10||GSM 22011 service accessibility; 3 GPP TS 22.011 V3.8.0 (Sep. 2002) Technical Specification; 3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Service accessibility (Release 1999).|
|11||GSM 23012 Location Update , Aug. 2006.|
|12||GSM 23060 GPRS, Aug. 2006.|
|13||GSM 23119 Gateway Location Register, Aug. 2006.|
|14||GSM 23122 Mobile Station Procedure, Aug. 2006.|
|15||GSM 23122 network selection 3GPP TS 23.122 V3.9.0 (Dec. 2002) Technical Specification; 3rd Generation Partnership Project; Technical Specification Group Core Network; NAS Functions related to Mobile Station (MS) in idle mode (release 1999).|
|16||GSM 24008 Mobile Radio Interface Network Layer, Aug. 2006.|
|17||GSM 25304 Idle Mode Selection, Aug. 2006.|
|18||GSM 29002 MAP Protocol, Aug. 2006.|
|19||GSM 29010 Error Network Mapping, Aug. 2006.|
|20||GSM 29060 GPRS Tunneling Protocol, Aug. 2006.|
|21||GSM 31048 Security and OTA, Aug. 2006.|
|22||GSM 318 on CAMEL Basic Call Handling; Digital cellular telecommunications system (Phase 2+) Basic call handling; Technical realization (GSM 03.18 version 6.6.0 Release 1997).|
|23||GSM 322 network selection Digital cellular telecommunications system (Phase 2+); functions related to Mobile Station (MS) in idle mode and group receive mode (GSM 03.22 version 8.3.0 Release 1999).|
|24||GSM 348 Security and OTA, Aug. 2006.|
|25||GSM 360 GPRS, Aug. 2006.|
|26||GSM 379 on CAMEL Digital cellular telecommunications system (Phase 2+); Customized Applications for Mobile network Enhanced Logic (CAMEL); CAMEL Application Part (CAP) specification (GSM 09.78 version 7.1.0 Release 1998).|
|27||GSM 408 Mobile Radio Interface Network Layer, Aug. 2006.|
|28||GSM 960 GPRS Tunneling Protocol, Aug. 2006.|
|29||IR 7320 Steering of Roaming, Aug. 2006.|
|30||ITU-T Recommendation Q. 765 (1998), Signaling system No. 7-Application transport mechanism.|
|31||ITU-T Recommendation Q. 766 (1993), Performance objectives in the integrated services digital network application.|
|32||ITU-T Recommendation Q. 769.1 (1999), Signaling system No. 7-ISDN user part enhancements for the support of Number Portability.|
|33||Q1214-Q1218 on Intelligent Networks IMS architectures, 3GPP, and 3GPP2.|
|34||Q701-705 on SS7 MTP, Aug. 2006.|
|35||Q771-775X TCAP, Aug. 2006.|
|36||Signaling procedure and the Mobile Application Part (MAP) (Release 1999).|
|37||SMPP Forum: SMPP Protocol Document Version:-Oct. 12, 1999 Issue 1.2.|
|38||Technical Specification3rd Generation Partnership Project; Technical Specification Group Services and System Aspects; Service accessibility (Release 1999).|
|39||Universal Mobile Telecommunications System (UMTS); Multimedia Messaging Service (MMS), Functional description; Stage 2 (3GPP TS 23. 140 version 4.2.0 Release 4).|
|Citing Patent||Filing date||Publication date||Applicant||Title|
|US7653383 *||Feb 28, 2003||Jan 26, 2010||Motorola, Inc.||Method and apparatus for remote data access in a mobile communication device|
|US7747281||Jan 7, 2008||Jun 29, 2010||Airbiquity Inc.||Method for in-band signaling of data over digital wireless telecommunications networks|
|US7848763||Feb 12, 2009||Dec 7, 2010||Airbiquity Inc.||Method for pulling geographic location data from a remote wireless telecommunications mobile unit|
|US7924934||May 26, 2006||Apr 12, 2011||Airbiquity, Inc.||Time diversity voice channel data communications|
|US7979095||Oct 20, 2008||Jul 12, 2011||Airbiquity, Inc.||Wireless in-band signaling with in-vehicle systems|
|US7983310||Jul 19, 2011||Airbiquity Inc.||Methods for in-band signaling through enhanced variable-rate codecs|
|US8036201||Apr 20, 2010||Oct 11, 2011||Airbiquity, Inc.||Voice channel control of wireless packet data communications|
|US8036600||Apr 1, 2010||Oct 11, 2011||Airbiquity, Inc.||Using a bluetooth capable mobile phone to access a remote network|
|US8068792||Oct 22, 2007||Nov 29, 2011||Airbiquity Inc.||In-band signaling for data communications over digital wireless telecommunications networks|
|US8073440||Apr 1, 2010||Dec 6, 2011||Airbiquity, Inc.||Automatic gain control in a personal navigation device|
|US8195093||Aug 29, 2011||Jun 5, 2012||Darrin Garrett||Using a bluetooth capable mobile phone to access a remote network|
|US8196092 *||Jun 14, 2007||Jun 5, 2012||Verizon Patent And Licensing Inc.||XSL dialog modules|
|US8249865||Oct 13, 2010||Aug 21, 2012||Airbiquity Inc.||Adaptive data transmission for a digital in-band modem operating over a voice channel|
|US8346227||Oct 25, 2011||Jan 1, 2013||Airbiquity Inc.||Automatic gain control in a navigation device|
|US8358620 *||Jan 11, 2011||Jan 22, 2013||Sprint Communications Company L.P.||Voice session and data session coordination in a communication device|
|US8369393||May 9, 2011||Feb 5, 2013||Airbiquity Inc.||Wireless in-band signaling with in-vehicle systems|
|US8418039||Jul 13, 2010||Apr 9, 2013||Airbiquity Inc.||Efficient error correction scheme for data transmission in a wireless in-band signaling system|
|US8452247||Nov 28, 2012||May 28, 2013||Airbiquity Inc.||Automatic gain control|
|US8538845||May 30, 2012||Sep 17, 2013||Mozido, Llc||Monetary transaction system|
|US8594138||Jul 18, 2011||Nov 26, 2013||Airbiquity Inc.||Methods for in-band signaling through enhanced variable-rate codecs|
|US8848825||Sep 22, 2011||Sep 30, 2014||Airbiquity Inc.||Echo cancellation in wireless inband signaling modem|
|US8879703||May 31, 2012||Nov 4, 2014||Tal Lavian||System method and device for providing tailored services when call is on-hold|
|US8903073 *||Jul 20, 2011||Dec 2, 2014||Zvi Or-Bach||Systems and methods for visual presentation and selection of IVR menu|
|US8977554 *||Dec 23, 2013||Mar 10, 2015||Amazon Technologies, Inc.||Assisted shopping server|
|US9148280 *||Sep 29, 2011||Sep 29, 2015||Verizon Patent And Licensing Inc.||Method and system for providing secure, modular multimedia interaction|
|US9195980||Oct 30, 2009||Nov 24, 2015||Nokia Technologies Oy||Method and apparatus for recovery during authentication|
|US9208488||Nov 19, 2012||Dec 8, 2015||Mozido, Inc.||Using a mobile wallet infrastructure to support multiple mobile wallet providers|
|US20040171370 *||Feb 28, 2003||Sep 2, 2004||Vimalkaushik Natarajan||Method and apparatus for remote data access in a mobile communication device|
|US20070230676 *||Jun 12, 2007||Oct 4, 2007||Sony Ericsson Mobile Communications Ab||Technique for delivering caller-originated alert signals in ip-based communication sessions|
|US20080313606 *||Jun 14, 2007||Dec 18, 2008||Verizon Data Services Inc.||Xsl dialog modules|
|US20090094531 *||Oct 5, 2007||Apr 9, 2009||Microsoft Corporation||Telephone call as rendezvous mechanism for data sharing between users|
|US20100121958 *||Nov 7, 2008||May 13, 2010||Nokia Corporation||Input-sensitive interface selection for posting|
|US20110106709 *||May 5, 2011||Nokia Corporation||Method and apparatus for recovery during authentication|
|US20110113143 *||May 12, 2011||Sprint Communications Company L.P.||Voice session and data session coordination in a communication device|
|US20120117510 *||May 10, 2012||Xerox Corporation||System and method for automatically establishing a concurrent data connection with respect to the voice dial features of a communications device|
|US20130022191 *||Jul 20, 2011||Jan 24, 2013||Zvi Or-Bach||Systems and methods for visual presentation and selection of ivr menu|
|US20130086633 *||Apr 4, 2013||Verizon Patent And Licensing Inc.||Method and system for providing secure, modular multimedia interaction|
|U.S. Classification||370/329, 455/464, 370/352, 455/450|
|International Classification||H04L12/28, H04W80/00, H04W76/02, H04W4/00, H04W80/10, H04L12/58, H04W88/06, H04W4/20, H04L29/08, H04L12/66|
|Cooperative Classification||H04L67/2823, H04L67/28, H04L67/04, H04L67/02, H04L67/14, H04L67/2819, H04L67/2838, H04L67/26, H04L67/2833, H04W76/02, H04W76/025, H04L29/12103, H04L61/1535, H04W80/00, H04W4/00, H04M3/4938, H04L51/38, H04M3/5322, H04M2207/18, H04W80/10, H04W88/06, H04L12/66, H04M2201/40, H04W4/20, H04L12/5895, H04M7/0024|
|European Classification||H04L61/15B, H04L12/58W, H04L29/12A2B, H04L29/08N3, H04L29/08N1, H04L29/08N13, H04M7/00D, H04L29/08N27, H04W4/00, H04L29/08N25, H04L12/66, H04L29/08N27F, H04L29/08N27G, H04W76/02M|
|May 21, 2009||AS||Assignment|
Owner name: ROAMWARE, INC., CALIFORNIA
Free format text: CHANGE OF NAME;ASSIGNOR:MOBILEUM, INC.;REEL/FRAME:022722/0274
Effective date: 20020816
Owner name: MOBILEUM, INC., CALIFORNIA
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:JIANG, YUEN JUN;CHANG, HISAO M.;REEL/FRAME:022722/0284
Effective date: 20011115
|Nov 12, 2012||REMI||Maintenance fee reminder mailed|
|Apr 1, 2013||FPAY||Fee payment|
Year of fee payment: 4
|Apr 1, 2013||SULP||Surcharge for late payment|
|Oct 31, 2014||AS||Assignment|
Owner name: PARTNERS FOR GROWTH IV, L.P., CALIFORNIA
Free format text: SECURITY INTEREST;ASSIGNOR:MOBILEUM, INC.;REEL/FRAME:034114/0742
Effective date: 20141031
|May 11, 2015||AS||Assignment|
Owner name: SILICON VALLEY BANK, CALIFORNIA
Free format text: SECURITY INTEREST;ASSIGNOR:ROAMWARE, INC.;REEL/FRAME:035624/0478
Effective date: 20070208