Patent Grant
8611873
1. Field of the Invention
The invention relates to a system for allowing users to provide other individuals with a personalized representation of the user in a network environment, such as a cellular telephone network.
2. Description of the Related Art
Wireless telephones have become more powerful with the inclusion of such features as cameras, address books, calendars and games. Many now include microprocessors, operating systems and memory which allow developers to provide limited applications for the phones. Phones now include the ability to play multimedia files including polyphonic ringtones, MP3 files, MPEG, AVI and QuickTime movies, and the like, in addition to displaying pictures taken on or downloaded to the phone.
Wireless phones have long been able to access the Internet via a Wireless Access Protocol (WAP) browser, and receive messages via SMS. A user on a wireless telephone connects via the wireless network to a server which enables the phone to read WAP enabled content. Most providers enable a user to access an email message account via the WAP browser, and/or provide short message service (SMS) messages directly to the user's phone. SMS allows users to receive abbreviated text messaging directly on the phone. Messages can actually be stored on the phone, but the storage available is limited to a very small amount of memory. In addition, no provision for handling attachments in SMS is available.
More recently, phones themselves have become powerful enough to utilize data connections over a carrier's network to manipulate data. For example, users of a carrier's network can download multimedia content to their phone, shop and download phone specific applications, and send and receive more robust messaging. Devices which have been combined with wireless phones, such as Research In Motion's Blackberry device, provide a user with enhanced message capabilities and attachment handling. These devices are specifically configured to provide contact and message applications over a wireless network.
Still, the majority of phones provide limited native address and contact data storage, and only SMS messaging capability. Some phones do allow users to associate images and specific ringtones with users in their phone's address book. Most wireless phones support caller ID, which displays the number of an incoming caller. Using this information, phones having imaging and multiple ringtone capabilities display an incoming caller's address book associated picture (if available) when the incoming call is received, and play a specially designated ringtone (if specified).
With the numerous different types of wireless phones and other communications devices available, a system which will enable a user to provide a personalized representation of themselves on other user's phones would be useful in allowing the user to identify themselves to other users.
The present invention, roughly described, pertains to a System and method which allows advanced identification information to be created and distributed to users of wireless communication devices, such as mobile phones. Subscribers can define their own personas as collections of information which define the users. Subscribers can then publish their persona(s) to their friends' and associates' mobile phones, and update the others' address books with the subscriber's contact information. Users can specify different personas to be presented to different users.
In one embodiment, the invention is a system for providing personification information to users of a wireless phone.
In another embodiment, the invention is a method of identifying a service subscriber on a wireless device. The method may include the steps of: establishing a subscriber persona comprising information identifying a user to other users; and displaying at least a portion of the persona on a device when a call or other type of contact such as SMS, Push-To-Talk message, email, voiceclip, et al to the device is received from another subscriber whose personalization information has been provided to the user.
In another embodiment, the invention is a method of providing an advanced caller identification service. In this embodiment, the invention includes: maintaining a store of subscriber persona information provided by users, the persona information identifying the user to other users; and distributing persona information to others based on an established relationship between subscribers.
A still further embodiment of the invention includes an application on a subscriber phone. The application includes a store of personification information for at least one other subscriber; and a display interface providing personification information to a phone interface and an interface for managing the user's own personalization information, as well as any system or account preferences.
In another embodiment, the invention is an application server for a communication system. The sever includes a store of personification information for a plurality of subscribers; and a distribution system management application.
The present invention can be accomplished using hardware, software, or a combination of both hardware and software. The software used for the present invention is stored on one or more processor readable storage media including hard disk drives, CD-ROMs, DVDs, optical disks, floppy disks, tape drives, RAM, ROM or other suitable storage devices. In alternative embodiments, some or all of the software can be replaced by dedicated hardware including custom integrated circuits, gate arrays, FPGAs, PLDs, and special purpose computers.
These and other objects and advantages of the present invention will appear more clearly from the following description in which the preferred embodiment of the invention has been set forth in conjunction with the drawings.
The present invention allows advanced identification features to be provided to a phone or other mobile device by allowing user to provide personification information for other users of advanced wireless communication devices. Each user can create one or more individualized representations of themselves and push this information to other users. The service is generally enabled by an enterprise service provider or cellular network carrier via one or more servers. Users can subscribe to the service, allowing them to create and distribute sub-sets of personification information or “personas”, or merely participate in the system, receiving personification information from subscribers. Since devices have different capabilities, the system will vary in its ability to provide personification information to each device, and in one embodiment, the type of user device and its capabilities are stored for each member of the system. The method and implementing systems and applications of the present invention provided by the enterprise service provider may be subject to a service fee to maintain the personification information in the data store, and provide functionality associated with the system.
In general, a user creates a personification of themselves which may include the user's contact information, signature, photo, multimedia information and a specific ringtone identifying them to other phone users. Many cellular phones include the ability to download specific ringtones and use them to identify incoming callers by associating the ringtone and picture with the contact information in the phone and triggering it using caller ID functions. The system of the present invention allows the user to specify their own ringtone and picture, and use it to identify them to other users. In addition to the static information in the personification information a user may provide dynamic information such as GPS location, timezone, availability, and event-relevant information (e.g., a reminder it's the caller's birthday, or a summary of calendar events or tasks assigned to or by the caller) or control information to other users or participants.
At step 204, the user may set the user's own personification information. This is referred to in Figures occasionally as creating or updating “me”. As shown at table 206, the user personification data may include the user's name, address, phone number and any other contact information, a picture of the user, a specific ringtone for the user, and a schedule of available times that the user may be contacted in various manners. In addition, the user may input user location information. Location information may be of varying specificity, and may initially input manually or through a connection with a GPS system in a GPS enabled phone. Information in the location section of a user's system may be updated by an agent on the phone using the phone's GPS agent. The ringtone may be uploaded by the user or may be selected from tones provided by the system administrator as part of the service, or the user may use the device's microphone (if equipped) to author a new audio clip which will be used as a ringtone. Optionally, a value added media distributor may provide phones, and digital rights management incorporated in the system to ensure proper control of copyrighted material within the system of the present invention. The phone manufacturer, the mobile phone carrier, or another entity may add DRM functionality as well, which may determine which protected content may be redistributed (and how). It should be recognized that step 204 is optional, and a user may decide not to provide personification information, but only participate in the system to acquire personification information of others. In another embodiment, subscription to the advanced ID service provided by the ESP is not required to receive personification information.
As discussed in further detail below, different sets (or “personas”) of personification information may be provided for different groups of individuals in the users' contact information. For example, a user may wish one group of contacts to receive one set of personification information (such as business contacts), while another set (such as personal friends) to receive a different set of information. The group definition allows the user to define recipients who receive the particular version of contact information. The user may assign one or more users to a particular group using an interface provided on the mobile device, or alternatively via some other interface, such as a webpage or an administrative configuration console. Additionally, the user can specify a “public” persona which anyone may download (and will be automatically assigned to new contacts in the user's devices). The system or agent maintains group assignments in persistent storage. The system or agent transmits the information appropriate for each group to the members of the group using the above described techniques. An enterprise service provider can allow a user to have a default persona upon establishing an account with the system. For example, the system can establish default public friends, family, co-workers, business associates, and blacklist persona templates, allowing the user to input certain information and have established personas once the user joins the system. The blacklisted persona is intended to be assigned to buddies to whom the user does not want to publish information.
At step 208, the new subscriber's contact records are provided to the ESP in one of a number of ways, and relationships detected between the subscriber's contact records and other subscribers. This input may be as simple as downloading phone numbers that the user has stored in his phone, or may include additional contact information which allows the system to determine whether individuals are members of the system. In addition, the subscriber may manually input contacts during account creation, or download contact information from another source, such as a personal information manager on a personal computer or personal digital assistant. A search mechanism may also be provided, allowing the user to input information on individuals to determine whether an individual is part of the system. For example, if a user does not have a stored resource of personal information, the user may, via the web browser, access a form provided by the system administration which provides name and other contact fields which the system can use to search for other users participating in the system. Once, found, this information can then be provided to the user.
In accordance with the system of the present invention, different types of links may be established between users. Generally, a user's contact list is found in the user address book in the datastore of the phone. Due to the nature of human communication, it is likely that a contact in a person's address book can likewise be found in that contact's own address book. For example, assuming Bob and Alice are both friends, they will likely have each other's contact information in their respective address books. This reciprocal link between people can be utilized to recognize and distinguish different types of links. In accordance with the invention “half” linked users occur when one user has the other user's contact information in their address book, but the other user does not reciprocate. These users are not connected for purposes of data exchange and the invitation functions provided in
When the user provides their own personification information to the service host at step 204, step 208 may include a step of detecting links between users by examining the contents of their address books which are provided to the server. In order to identify each user from the pool of all users of the system, the system uses telephone numbers and in one embodiment e-mail addresses as unique keys. In a further embodiment, the system of the present invention can use telephone number equivalence algorithms to match phone numbers regardless of formatting, country and area codes.
Users who wish to remove their information and “unlink another user” simply remove that user from their mobile device's address book. Using the rules of the system, the two users are no longer linked and no further updated information between them occurs. No information is deleted from the unlinked party's address book in this process. To accomplish this, instead of unlinking users may wish to assign another user to a “blacklisted” persona.
At step 208, once the contacts have in acquired, relationships between the subscriber's contracts and other subscribers are established. This can occur automatically by an algorithm run by the ESP, may be set manually by the user, or may occur by some combination of the two.
Optionally, at step 210, the subscriber may be offered the opportunity to invite other people to become subscribers. The user may be prompted to determine if the user wishes to invite contacts stored in the users phone to become subscribes to obtain additional benefits attributable to subscription. If the user wishes to invite others, an invite process is performed at step 212.
Optionally, at step 214, the subscriber may be given the option to allow their persona to be provided to non subscribers. If the user desires their information to be delivered, a delivery process 216 transmits personification information to non-subscriber users. This may occur in any number of ways, such as for example via SyncML, or via SMS messages, as described below.
At step 218, personification information from other subscribers in the subscriber's contact list are delivered to the new subscriber, and the new subscriber's information sent to other subscribers. As discussed below, contacts who are also subscribers are true-linked users 210 and automatically populate the new subscriber's phone. The information may be transmitted to the user in a data stream directly to the agent, which then populates the user's phone data. Alternatively, the information may be provided in a series of messages. Preferentially, the information will be transmitted via SyncML.
Included in persona information is whether the subscriber's contacts should be alerted to the subscriber's location based on system subscriber's GPS or manually entered location information in their own record. Also included may be, for example, the level of granularity available to the subscriber's contact. For example, one may be allowed to know the country, city or a more specific location. Once received, the receiving member may further configure the subscriber's persona information based on the information received. For example, suppose another member provides location information in their member record. The user may specify that the user wishes to be notified when the member with location information moves to a particular location or within a particular distance from the specifying member. Other criteria may also be configured, such as group information. For example, the user may specify which groups each member belongs to so that if such member requests personification information about the specifying user, the correct group information is provided to the requesting member.
Finally, at step 220, the new subscriber may update information in their persona. When the new subscriber does so, the information is re-transmitted to true linked subscribers and, if enabled, non-subscriber participants in the system. Updates may be started on the device by the client application as a result of data changes on the device. This may occur because of user interaction with the device, or changing transient information such as time zone. Updates can occur in one of two ways. Server-initiated updates are triggered by time intervals, or a change in data which is to be sent to the user's device. Server-initiated updates are handled via direct socket connection to the client or via SMS messages sent from the server to the client application on the device. Each advanced ID account supports a configurable “server initiated sync on/off” setting which controls whether SMS messages are automatically sent when a client is out of date. The SMS message from the server may be sent to the text port (or configured data port, if appropriate).
In one aspect, the system supports controlling both the calling user's phone and the called user's phone. At step 501, if subscriber B has configured his persona (which is downloaded to subscriber A) to prevent calls during a certain period of time, the client application on the calling user's phone can prevent subscriber A from connecting to subscriber B during this period. Hence at step 501, the method may check (on subscriber A's phone) whether a call to Subscriber B is allowed based on Subscriber B's configuration. If not, an alert 503 may be provided to Subscriber A.
At step 502, if the call is initiated by subscriber A and received by subscriber B, optionally, at step 504, the receiving user can configure the phone to prevent calls during a specific period of time. Hence, at step 504 the method may check to determine whether a call is allowed during a specific period by the receiving user. If the call is not allowed, the method may block the call at step 512. If the call is not blocked, the user's advanced ID information (persona) is displayed on the receiving caller's phone. If the call is blocked, it may be directed to the receiver's voicemail system. The advanced ID or persona is a collection of information which defines the user, such as a phone number, e-mail address, picture, geo location information and other data. This allows subscribers to manage their own “personal brand” controlling how they are represented on other user's phones specifying a ringtone or the picture associated with their contact. As discussed herein, one can have a “friends” persona and a “co-workers” persona which contain different information or different sets of information. Additional features such as geo location information provided by GPS information capable phones is also provided, as is information about the caller which is transient in nature—such as whether it's the caller's birthday or anniversary, or information concerning phone calls, meetings, or tasks assigned to or by the caller. The system may be implemented by using a direct push system from a server via a SyncML server to a SyncML client, or may be operated on by a specific client application resident in the phone which communicates with the service-side implementation. SyncML is an Extensible Markup Language (XML) protocol under development as an open standard for the universal synchronization of data between devices. Synchronization of data allows changes made to data on one device (such as a smartphone or a laptop computer) to be instantly reflected in data on another device (such as a networked computer).
Optionally, at step 508, if the member has chosen to provide the member's GPS information, at step 508 the GPS can be provided in a notification at step 510 provided to show that the user is at or near a specific location.
The present invention supports two different types of data: static and dynamic. Static data can include a user's ringtone, name and image. The static info is provided by the calling subscriber to the receiving subscriber's client on phone 100 at step 506. Step 501 indicates a feature of the present invention which allows subscribers to define their own personification information to control another user's phone—this dynamic or “active control” information can be updated more often than the static persona information. Dynamic information such as GPS or timezone information is updated regularly based on the needs of the sending subscriber. Due to the interaction of the client 140 with the phone, the subscriber may actually prevent (or merely warn) a calling subscriber from calling a receiving subscriber's phone and may instead provide them a user-configurable message which may direct the caller to use some other mechanism to contact the intended receiving subscriber (e.g., SMS, email, etc). As with all other similar information, this preferred availability information is stored users' personas.
An advanced ID service server 160 is also provided which communicates with the telephone via wireless network 150 directly over a data connection or via a SyncML server 195. Various embodiments of a system for implementing the advanced ID service are discussed herein. In
Phone 100 may be provided with a system application or agent 140. System agent 140 can include a SyncML communication client designed to interact with a SyncML server 195 in accordance with approved and proposed versions of the SyncML OMA DS specification, including proposed extensions, (available at http://www.openmobilealliance.org). Alternatively, agent 140 can be an application designed to communicate with server 160 using an existing SyncML client on the phone provided by the phone's manufacturer (as well as any custom extensions supported by such client), or an application specifically designed to communicate with server 160 via another protocol, including a proprietary protocol. In one embodiment, the agent 140 is a fully implemented SyncML client and server 160 includes a SyncML server. In another embodiment, the application 140 is a client application device sync agent such as that disclosed in U.S. Pat. No. 6,671,757. Various embodiments of the client application 140 are set forth below.
In accordance with the present invention, a phone 100 includes a system memory 122 which may further include an operating system 124 having operating system service including telephony and linking services, networking services, multimedia and graphics display services all provided to a user interface 120. OS 125 my be the phone's proprietary OS, BREW, or any other device or operating system suitable for a phone (such as the Symbian Operating system). Additional base services 135 and an operating system kernel may also be provided. The operating system may additionally provide an SMS client 145 built into the operating system allowing short messages to be provided across the wireless communications line 150 to other users. Still further, a SyncML client 132 may be provided and supported by the operating system services 124. The phone 100 includes a native phone data store 170 which contains address book contact and other information which may be provided by a subscriber. Such information can further include ringtones, pictures, sounds, and movies, all dependent on the functional capabilities of the phone 100, the space allowed in the system memory, and the services provided by the operating system 124.
A client application 140, various embodiments of which are discussed herein, is also loaded into phone 100. As will be well understood by one of average skill in the art, client application 140 can be provided by the phone manufacturer or downloaded by a user at a later time. To download and install the application, the user selects a download area of the phone operating system services 124, selects the application from offerings provided by the service provider or carrier who maintains the wireless communications line 150, or an enterprise service provider who maintains the system server 160, and installs the application onto phone 100. In an alternative embodiment, agent 140 is a self-supporting application designed to run as a JAVA or BREW agent, or any other device or operating system specific agent (such as an agent operable on the Symbian Operating system). This agent can either include its own SyncML client, or interact with an existing SyncML client on the telephone. Changes can occur at field level or byte level. Alternative embodiments can communicate via alternative protocols via the wireless communications link to store information on the System data base 510.
Client 100 includes at least a user interface 120, the application 140 having a communication or sync engine and data store manager, a SyncML client 132 and a local database 150. The client application 140 provides an appropriate graphical user interface to UI 120 which provides the user an alternative point of interaction with the system and service provided by the enterprise service provider. The user interface allows the user to define and manage personas and buddies as well as other tasks as specified in the case definition described herein. Interaction with the system can be via this client user interface or via the server user interface provided by the web server 180. The engine and data store manager is responsible for maintaining the user settings and options in the device's persistent storage as well as automatically pushing and retrieving changes to those object to the system server. The client datastore includes account information, persona data, buddy information, data for other users who have true links with the subscriber, and multimedia content
The storage server 160 is a centralized storage location for all system service information, including buddy, persona, relationship, and user data. Clients 140 can connect to and synchronized with the server information to update their local copy of this data as well as publish any changed information or retrieve any new available information from the server. In the mobile device, the persona information belonging to a user's buddy is primarily stored in the native address book or a separate address book provided by the client. As some devices will not support all the published buddy information including the extended information such as geo location and presence information, the client can store this information in a local database and provide access to it via the phone interface.
In general, a hardware structure suitable for implementing server 160, webserver 180 or SyncML server 195 includes a processor 114, memory 104, nonvolatile storage device 106, portable storage device 110, network interface 112 and I/O device(s) 116. The choice of processor is not critical as long as a suitable processor with sufficient speed is chosen. Memory 104 could be any conventional computer memory known in the art. Nonvolatile storage device 106 could include a hard drive, CDROM, CDRW, flash memory card, or any other nonvolatile storage device. Portable storage 108 could include a floppy disk drive or another portable storage device. The computing system may include one or more network interfaces 102. An example of a network interface includes a network card connected to an Ethernet or other type of LAN. I/O device(s) 116 can include one or more of the following: keyboard, mouse, monitor, display, printer, modem, etc. Software used to perform the methods of the present invention are likely to be stored in memory 104 which include nonvolatile storage and volatile memory as well as, portable storage media 110.
The computing system also includes a database 106. In alternative embodiments, database 106 is stored in memory 104, portable storage 110 or another storage device that is part of the system of
Also provided on server 160 is a system data store 310. The System data store is provided in the non-volatile memory space of server 160. While only one System data store computer is shown, it should be recognized that the store may be replicated to or stored over a plurality of computers to ensure that the data thereon is protected from accidental loss. It should be understood that the representation of the SyncML server 195 and web sever 180 need not require that such servers be provided on different physical hardware than the System server 160.
The system of
A synchronization system described with respect to U.S. Pat. No. 6,671,757, 6,694,336 or 6,757,696 comprises client software which provides the functions of a differencing transmitter/receiver/engine, and differencing synchronizer in the form of a device engine. The device engine may include at least one component particular to the type of device on which the device engine runs, which enables extraction of information from the device and conversion of the information to difference information, and transmission of the difference information to the storage server. The storage servers utilized in the may be any type of storage server, such as an Internet server or an FTP server, and may be provided from any source, such as any Internet service provider. In a key aspect of the sync system, the Internet connection between the devices or between the devices and a server, need not exist at the same point in time. In addition, only those changes to the information which are required to be forwarded to other systems on the system of the present invention are transmitted to enable fast response times.
Data from each of the sync client devices is coupled with a storage server. In one embodiment, each device engine implements all processing required to keep all the systems fully synchronized. Only one device engine needs to be coupled to the sync server at one particular point in time. This permits synchronization of multiple systems in a disconnected fashion. Each device engine will download all transactions encapsulating changes that have occurred since the last synchronization from the server and apply them to the particular device. The change or difference information (termed a “data package” or “change log”) is provided in one or more data packages. Each data package describes changes to any and all transfer information across all device engines, including but not limited to application data, files, folders, application settings, and the like. Each device engine can control the download of data packages that include classes of information that apply to the specified local device. For example, contact names and phone numbers while another needs only changes to e-mail, changes to document files.
Compression and encryption of the data packages may be optionally provided. Each device engine performs mapping and translation steps necessary for applying the data packages to the local format required for that type of information in the application data stores. The device engine also includes components which allow it to track ambiguous updates in cases where users have changed data to a particular data field on two different systems simultaneously since the last update. The output of the device engine comprises a data package which is output to sync server database. As noted above, only one device engine need be connected to the storage server 850 at a given time. The data package can be stored on the storage server until a request is made to a particular location of the storage server by another device engine. Access to areas of the storage server is controlled by a management server (MS). In one embodiment, each sync operation requires that the device engine for each device login to the management server to authenticate the device and provide the device engine with the location of the individual device's data packages on the storage server.
When data is returned to the delta module from the storage server, the delta module returns differenced data to the application object for the particular application which then translates the delta information into the particular interface utilized for application. Once a device engine has been fully applied all data packages from an input stream, it generates a series of data packages that describe the changes made on the local system. The device engine uses the local application object 920 to keep track of the last synchronized version of each application's actual data, which is then used for the next data comparison by the delta module on the next sync request. Generated data packages can include operations and encode changes generated from resolving ambiguous cases as described above.
The sync server uses the concept of a universal data record in its internal sync differencing engine and when sending data to and retrieving from external
The management server supports an authentication interface that requires each device engine to authenticate with the management server before performing synchronization. Certain storage server implementations may utilize locking semantics to control read and write access to storage for multiple device engines. For example, in a generic FTP request, if two device engines attempt to connect to the same data at the same time, there must be some form of locking control to prevent device engines accessing the same data at the same time. In this instance, the management server controls the device engine acquisition, renewal, and releasing of locks against data stored in the network.
Each device engine is uniquely identified and tracked by the management server. This allows for tailoring behavior between the management server and specific types of storage systems and device engine components. All device engine components are tagged and version stamped for management via the management server.
Also shown in
In accordance with the invention, application agent 140 communicates personification information and changes made to the personification information stored in the data store of the telephone 100 to server 160 via the wireless network. Communication of user data from the device may take several forms. Where the client utilized SyncML communications with the server 160, communication may take place using the standards set forth in the SyncML specification. Changes are transmitted on a record-by-record basis or field-by-field basis. Alternatively, communication may occur via another protocol. The SyncML client is utilized to update the phone's native address book with buddy published information as well as to retrieve persona and link information from the server. Information can be exchanged via the SyncML protocol, or via a direct data link with the server 160. The system server stores and maintains each user account, link personal and buddy information as well as multimedia content, both system provided and user created. The server is a stand alone server and may be incorporated with the features of a synchronization system such as that described in U.S. Pat. No. 6,671,757. Details of this integration are described in further detail below. As noted above, a management interface is provided via the web server 180. Description of this interface is shown below.
The server 160 stores user data in the personification store 150 in a manner which associates the data with the user of the phone. In one embodiment the data is stored in bulk—that is all records and information for the user are stored in simple text form, (or binary form, depending on the type of data in use). This information is stored in the data store using a unique identifier (UID) associating the personification data with the individual user. The identifier may be any randomly selected identifier, so long as the user is uniquely identified, and the data is associated with the user. In a further aspect, this user UID may be a universally unique identifier (UUID), created in a manner described in the aforementioned U.S. Pat. No. 6,671,757, 6,694,336 or 6,757,696 or other manners to create a single ID for a given user. In yet another embodiment, user data and changes to the user data are stored in a change logs in a manner described in the aforementioned U.S. Pat. No. 6,671,757, 6,694,336 or 6,757,696.
A web server 180 allowing a user on a computer or other device 190 having a web browser may optionally be provided to allow a user to configure aspects of the system of the invention. Server 180 may have a hardware configuration similar to computer 160 and may comprise one or more physical computers. Additionally, web server 180 may be integrated with server 160.
In one embodiment, aspects of the system of the present invention are configured via a phone interface. The system can alternatively be configured by a user via a web interface provided by the web server 180 via the user device 190.
In another embodiment, shown in
As shown in
At step 902, an account creation step is initiated on the server 160. Server 160 will also create an account with the application server 185 at step 904. Server 160 will provide provisioning information 906 to the client 140, which will then upload its address book at step 908 to server 160. Server will attempt to establish whether direct links are present at step 910 and return those true links to the user at step 912. Concurrently, the system will attempt to perform a synchronization with the user's contact information on the synchronization server 185. At step 916, the user's public persona is synced to each user's synchronization account and if there's any problem with the synchronization at step 918 an out of sync notification message is returned to the client 140. At step 920, records are retrieved regarding the records representing the buddy's personas at step 920. Persona records are thereafter synced as other records are synced in accordance with the description in U.S. Pat. No. 6,671,757.
As noted above, the client application 140 and server application 180 provide the user with a number of functions to create and manage accounts with the ESP and the advanced ID system.
In a further embodiment, a subscriber display may be provided which incorporates data from sources other than the address book. If, for example, the user has populated a phone's native calendar with information concerning meetings with a contact, the client application can extract this information and display, for example, the user's last or future meetings with the contact. Alternatively, this information can be extracted from a sync user account when a synchronization server is utilized as described herein.
Selection of the contacts link 2000 on the menu bar 1950 gives rise to the user interface 2000 shown in
The functionality associated with the user interface in
b shown an initial start-up screen displaying a “last successful synchronization” that the user has made, as well as status information, (all contacts, Advanced ID contacts, personas, images and ringtones) such as that depicted in
At
At
If an advanced ID contact is opened (from
Selecting the persona brings up a change persona menu as shown in
Pressing the “persona” menu item 2100 in menu bar 1950 in
As shown in
As noted above, when the system is implemented in accordance with a synchronization system as shown and described with respect to U.S. Pat. No. 6,671,757, 6,694,336 or 6,757,696, additional elements other than those shown in
The personal records may be represented in the synchronization system's content records by a specially added contact record field. When a change log describing a persona arrives at the listener engine 2640, advanced ID engine 2642 collects the affected buddies, finds the corresponding synchronization server record, and provides the contact modified transaction change log containing the new persona information back to the synchronization server. The synchronization server adds these modified transactions in accordance with the description of U.S. Pat. No. 6,671,757, 6,694,336 or 6,757,696 to the directly linked buddies' synchronization accounts. On such buddies' next synch, each party retrieves the updated contact record representing the persona that the user has assigned it to. Once the synchronization server 2650 contacts the system server 2640, the system server tracks which persona a given buddy is assigned to by adding a field to the contact record. Device 100-6 incorporates a device sync client 2610 which syncs with the device's address book with change logs provided by the synchronization server 2650. Both the native database 150 and the application ID database 2602 may be used to store records for the advanced ID system in accordance with the present invention.
Since most current clients do not include native robust address books and SyncML clients,
Yet another alternative configuration is shown in
In
In
Transcoding can involve an actual conversion or may involve simply selecting an alternative version of the media it already knows about. For example, a value added service provider may supply ringtones in two or more formats, and selection of the appropriate format can be made and distributed to the receiving user. When requesting media requires the media object, the transcoding will be performed by the server; the transcoded media will be transmitted to the device automatically. Clients may query information related to the media they are about to download using a function supplied in the communications protocol. This function will return relevant information concerning the transcoded media available to the client. The server may also provide transcode-on-demand support for clients which need multiple formats of the same media (e.g., image) in different sizes (e.g., a thumbnail for the contact in the addressbook and a full screen picture).
The system supports digital rights management contained in the native applications, allowing value added providers to check any media uploaded or downloaded to or from the server or client device to determine whether the information contained therein is subject to digitalized management. The media record 3510 which contains a media record type (local or nor) and identifier, size, hash value, a formula identifier, and a location. The media format 3512 can be any of an image format 3514, a ringer format 3516, a video format 3518. The image format type includes jpegs, pngs and gifs, as indicated at 3520. The ringtone format can be a midi-type or an mp3 wav or a special awp format. The video format can be an mpeg, wmp file, quicktime, or an avi. Additional formats for images, ringers, and videoclips may be easily added without requiring significant system modification.
The foregoing detailed description of the invention has been presented for purposes of illustration and description. It is not intended to be exhaustive or to limit the invention to the precise form disclosed. Many modifications and variations are possible in light of the above teaching. The described embodiments were chosen in order to best explain the principles of the invention and its practical application to thereby enable others skilled in the art to best utilize the invention in various embodiments and with various modifications as are suited to the particular use contemplated. It is intended that the scope of the invention be defined by the claims appended hereto.
This application claims priority to U.S. Provisional Application No. 60/570,409, filed May 12, 2004, entitled “Communication Network Identification System,” which is incorporated herein by reference.
| Number | Name | Date | Kind |
|---|---|---|---|
| 4887212 | Zamora et al. | Dec 1989 | A |
| 5111398 | Nunberg et al. | May 1992 | A |
| 5115466 | Presttun | May 1992 | A |
| 5130993 | Gutman et al. | Jul 1992 | A |
| 5146221 | Whiting et al. | Sep 1992 | A |
| 5204902 | Reeds et al. | Apr 1993 | A |
| 5329619 | Page et al. | Jul 1994 | A |
| 5392390 | Crozier | Feb 1995 | A |
| 5418854 | Kaufman et al. | May 1995 | A |
| 5418908 | Keller et al. | May 1995 | A |
| 5425079 | Noda et al. | Jun 1995 | A |
| 5483352 | Fukuyama et al. | Jan 1996 | A |
| 5485161 | Vaughn | Jan 1996 | A |
| 5509070 | Schull | Apr 1996 | A |
| 5519433 | Lappington et al. | May 1996 | A |
| 5519606 | Frid-Nielsen et al. | May 1996 | A |
| 5543789 | Behr et al. | Aug 1996 | A |
| 5544061 | Morimoto et al. | Aug 1996 | A |
| 5561446 | Montlick | Oct 1996 | A |
| 5574906 | Morris | Nov 1996 | A |
| 5579489 | Dornier et al. | Nov 1996 | A |
| 5588009 | Will | Dec 1996 | A |
| 5592470 | Rudrapatna et al. | Jan 1997 | A |
| 5623406 | Ichbiah | Apr 1997 | A |
| 5623661 | Hon | Apr 1997 | A |
| 5628005 | Hurvig | May 1997 | A |
| 5630081 | Rybicki et al. | May 1997 | A |
| 5638508 | Kanai et al. | Jun 1997 | A |
| 5640577 | Scharmer | Jun 1997 | A |
| 5644709 | Austin | Jul 1997 | A |
| 5647002 | Brunson | Jul 1997 | A |
| 5649195 | Scott et al. | Jul 1997 | A |
| 5650800 | Benson | Jul 1997 | A |
| 5657372 | Ahlberg | Aug 1997 | A |
| 5666397 | Lamons et al. | Sep 1997 | A |
| 5666553 | Crozier | Sep 1997 | A |
| 5682524 | Freund et al. | Oct 1997 | A |
| 5684990 | Boothby | Nov 1997 | A |
| 5694596 | Campbell | Dec 1997 | A |
| 5699255 | Ellis et al. | Dec 1997 | A |
| 5701423 | Crozier | Dec 1997 | A |
| 5706509 | Man-Hak Tso | Jan 1998 | A |
| 5710922 | Alley et al. | Jan 1998 | A |
| 5727202 | Kucala | Mar 1998 | A |
| 5727950 | Cook et al. | Mar 1998 | A |
| 5729735 | Meyering | Mar 1998 | A |
| 5729739 | Cantin et al. | Mar 1998 | A |
| 5729743 | Squibb | Mar 1998 | A |
| 5742792 | Yanai et al. | Apr 1998 | A |
| 5745750 | Porcaro | Apr 1998 | A |
| 5745906 | Squibb | Apr 1998 | A |
| 5757920 | Misra et al. | May 1998 | A |
| 5758150 | Bell et al. | May 1998 | A |
| 5758354 | Huang et al. | May 1998 | A |
| 5758355 | Buchanan | May 1998 | A |
| 5764899 | Eggleston et al. | Jun 1998 | A |
| 5768480 | Crawford, Jr. et al. | Jun 1998 | A |
| 5768597 | Simm | Jun 1998 | A |
| 5771354 | Crawford | Jun 1998 | A |
| 5778346 | Frid-Nielsen et al. | Jul 1998 | A |
| 5778361 | Nanjo et al. | Jul 1998 | A |
| 5778367 | Wesinger et al. | Jul 1998 | A |
| 5778388 | Kawamura et al. | Jul 1998 | A |
| 5781901 | Kuzma | Jul 1998 | A |
| 5787247 | Norin et al. | Jul 1998 | A |
| 5787262 | Shakib et al. | Jul 1998 | A |
| 5794228 | French et al. | Aug 1998 | A |
| 5804803 | Cragun et al. | Sep 1998 | A |
| 5809497 | Freund et al. | Sep 1998 | A |
| 5812773 | Norin | Sep 1998 | A |
| 5812793 | Shakib et al. | Sep 1998 | A |
| 5818437 | Grover et al. | Oct 1998 | A |
| 5826245 | Sandberg-Diment | Oct 1998 | A |
| 5828376 | Solimene et al. | Oct 1998 | A |
| 5832489 | Kucala | Nov 1998 | A |
| 5832518 | Mastors | Nov 1998 | A |
| 5832519 | Bowen et al. | Nov 1998 | A |
| 5832520 | Miller | Nov 1998 | A |
| 5845283 | Williams et al. | Dec 1998 | A |
| 5859973 | Carpenter | Jan 1999 | A |
| 5864864 | Lerner | Jan 1999 | A |
| 5875296 | Shi et al. | Feb 1999 | A |
| 5884323 | Hawkins et al. | Mar 1999 | A |
| 5884325 | Bauer et al. | Mar 1999 | A |
| 5893119 | Squibb | Apr 1999 | A |
| 5896321 | Miller | Apr 1999 | A |
| 5897640 | Veghte et al. | Apr 1999 | A |
| 5897642 | Capossela et al. | Apr 1999 | A |
| 5903723 | Beck et al. | May 1999 | A |
| 5907793 | Reams | May 1999 | A |
| 5909568 | Nason | Jun 1999 | A |
| 5923756 | Shambroom | Jul 1999 | A |
| 5923848 | Goodhand et al. | Jul 1999 | A |
| 5926816 | Bauer et al. | Jul 1999 | A |
| 5933653 | Ofek | Aug 1999 | A |
| 5933778 | Buhrmann et al. | Aug 1999 | A |
| 5933816 | Zeanah et al. | Aug 1999 | A |
| 5935262 | Barrett et al. | Aug 1999 | A |
| 5937405 | Campbell | Aug 1999 | A |
| 5941944 | Messerly | Aug 1999 | A |
| 5943676 | Boothby | Aug 1999 | A |
| 5944787 | Zoken | Aug 1999 | A |
| 5946615 | Holmes et al. | Aug 1999 | A |
| 5948066 | Whalen et al. | Sep 1999 | A |
| 5950193 | Kulkarni | Sep 1999 | A |
| 5951636 | Zerber | Sep 1999 | A |
| 5961572 | Craport et al. | Oct 1999 | A |
| 5961590 | Mendez et al. | Oct 1999 | A |
| 5966717 | Sass | Oct 1999 | A |
| 5968131 | Mendez et al. | Oct 1999 | A |
| 5970149 | Johnson | Oct 1999 | A |
| 5970490 | Morgenstern | Oct 1999 | A |
| 5971277 | Cragun et al. | Oct 1999 | A |
| 5974238 | Chase, Jr. | Oct 1999 | A |
| 5974563 | Beeler, Jr. | Oct 1999 | A |
| 5987381 | Oshizawa | Nov 1999 | A |
| 5987609 | Hasebe | Nov 1999 | A |
| 5995118 | Masuda | Nov 1999 | A |
| 6000000 | Hawkins et al. | Dec 1999 | A |
| 6006215 | Retallick | Dec 1999 | A |
| 6006274 | Hawkins et al. | Dec 1999 | A |
| 6009462 | Birrell et al. | Dec 1999 | A |
| 6012063 | Bodnar | Jan 2000 | A |
| 6012088 | Li et al. | Jan 2000 | A |
| 6014695 | Yamashita et al. | Jan 2000 | A |
| 6016394 | Walker | Jan 2000 | A |
| 6016478 | Zhang et al. | Jan 2000 | A |
| 6023620 | Harisson | Feb 2000 | A |
| 6023708 | Mendez et al. | Feb 2000 | A |
| 6023723 | McCormick et al. | Feb 2000 | A |
| 6026414 | Anglin | Feb 2000 | A |
| 6034621 | Kaufman | Mar 2000 | A |
| 6038665 | Bolt et al. | Mar 2000 | A |
| 6044381 | Boothby et al. | Mar 2000 | A |
| 6049776 | Donnelly et al. | Apr 2000 | A |
| 6052735 | Ulrich et al. | Apr 2000 | A |
| 6058399 | Morag et al. | May 2000 | A |
| 6061790 | Bodnar | May 2000 | A |
| 6061796 | Chen et al. | May 2000 | A |
| 6063134 | Peters et al. | May 2000 | A |
| 6064880 | Alanara | May 2000 | A |
| 6065018 | Beier et al. | May 2000 | A |
| 6067582 | Smith et al. | May 2000 | A |
| 6073133 | Chrabaszcz | Jun 2000 | A |
| 6076109 | Kikinis | Jun 2000 | A |
| 6078960 | Ballard | Jun 2000 | A |
| 6081900 | Subramaniam et al. | Jun 2000 | A |
| 6094618 | Harada | Jul 2000 | A |
| 6101480 | Conmy et al. | Aug 2000 | A |
| 6108330 | Bhatia et al. | Aug 2000 | A |
| 6108703 | Leighton et al. | Aug 2000 | A |
| 6112024 | Almond et al. | Aug 2000 | A |
| 6115797 | Kanda et al. | Sep 2000 | A |
| 6131096 | Ng et al. | Oct 2000 | A |
| 6131116 | Riggins et al. | Oct 2000 | A |
| 6141011 | Bodnar et al. | Oct 2000 | A |
| 6141621 | Piwowarski et al. | Oct 2000 | A |
| 6141659 | Barker et al. | Oct 2000 | A |
| 6141664 | Boothby | Oct 2000 | A |
| 6145088 | Stevens | Nov 2000 | A |
| 6148260 | Musk et al. | Nov 2000 | A |
| 6151606 | Mendez | Nov 2000 | A |
| 6157630 | Adler et al. | Dec 2000 | A |
| 6163773 | Kishi | Dec 2000 | A |
| 6163779 | Mantha et al. | Dec 2000 | A |
| 6163844 | Duncan et al. | Dec 2000 | A |
| 6167120 | Kikinis | Dec 2000 | A |
| 6173310 | Yost et al. | Jan 2001 | B1 |
| 6173311 | Hassett et al. | Jan 2001 | B1 |
| 6182117 | Christie et al. | Jan 2001 | B1 |
| 6182141 | Blum et al. | Jan 2001 | B1 |
| 6185598 | Farber et al. | Feb 2001 | B1 |
| 6189030 | Kirsch et al. | Feb 2001 | B1 |
| 6189096 | Haverty | Feb 2001 | B1 |
| 6195695 | Cheston et al. | Feb 2001 | B1 |
| 6195794 | Buxton | Feb 2001 | B1 |
| 6202085 | Benson et al. | Mar 2001 | B1 |
| 6205448 | Kruglikov et al. | Mar 2001 | B1 |
| 6209034 | Gladwin et al. | Mar 2001 | B1 |
| 6212529 | Boothby et al. | Apr 2001 | B1 |
| 6212556 | Arunachalam | Apr 2001 | B1 |
| 6216131 | Liu et al. | Apr 2001 | B1 |
| 6219680 | Bernardo et al. | Apr 2001 | B1 |
| 6219694 | Lazaridis et al. | Apr 2001 | B1 |
| 6223187 | Boothby et al. | Apr 2001 | B1 |
| 6226650 | Mahajan et al. | May 2001 | B1 |
| 6233565 | Lewis et al. | May 2001 | B1 |
| 6233589 | Balcha et al. | May 2001 | B1 |
| 6243760 | Armbruster et al. | Jun 2001 | B1 |
| 6246889 | Boltz | Jun 2001 | B1 |
| 6247048 | Greer et al. | Jun 2001 | B1 |
| 6247135 | Feague | Jun 2001 | B1 |
| 6249690 | Mashiko | Jun 2001 | B1 |
| 6252547 | Perry et al. | Jun 2001 | B1 |
| 6255989 | Munson et al. | Jul 2001 | B1 |
| 6256750 | Takeda | Jul 2001 | B1 |
| 6260124 | Crockett et al. | Jul 2001 | B1 |
| 6272545 | Flanagin et al. | Aug 2001 | B1 |
| 6275831 | Bodnar et al. | Aug 2001 | B1 |
| 6278941 | Yokoyama | Aug 2001 | B1 |
| 6282435 | Wagner et al. | Aug 2001 | B1 |
| 6282698 | Baker et al. | Aug 2001 | B1 |
| 6285889 | Nykanen et al. | Sep 2001 | B1 |
| 6286029 | Delph | Sep 2001 | B1 |
| 6286053 | Van Peursem et al. | Sep 2001 | B1 |
| 6286085 | Jouenne et al. | Sep 2001 | B1 |
| 6289212 | Stein et al. | Sep 2001 | B1 |
| 6292743 | Pu et al. | Sep 2001 | B1 |
| 6292905 | Wallach et al. | Sep 2001 | B1 |
| 6295502 | Hancock et al. | Sep 2001 | B1 |
| 6295541 | Bodnar et al. | Sep 2001 | B1 |
| 6304881 | Halim et al. | Oct 2001 | B1 |
| 6317755 | Rakers et al. | Nov 2001 | B1 |
| 6321236 | Zollinger et al. | Nov 2001 | B1 |
| 6324467 | Machii et al. | Nov 2001 | B1 |
| 6324526 | D'Agostino | Nov 2001 | B1 |
| 6324544 | Alam et al. | Nov 2001 | B1 |
| 6327533 | Chou | Dec 2001 | B1 |
| 6329680 | Yoshida et al. | Dec 2001 | B1 |
| 6330568 | Boothby et al. | Dec 2001 | B1 |
| 6332158 | Risley et al. | Dec 2001 | B1 |
| 6333973 | Smith et al. | Dec 2001 | B1 |
| 6338096 | Ukelson | Jan 2002 | B1 |
| 6339710 | Suzuki | Jan 2002 | B1 |
| 6341316 | Kloba et al. | Jan 2002 | B1 |
| 6345308 | Abe | Feb 2002 | B1 |
| 6349336 | Sit et al. | Feb 2002 | B1 |
| 6353448 | Scarborough et al. | Mar 2002 | B1 |
| 6356910 | Zellweger | Mar 2002 | B1 |
| 6356961 | Oprescu-Surcobe | Mar 2002 | B1 |
| 6360252 | Rudy et al. | Mar 2002 | B1 |
| 6360330 | Mutalik et al. | Mar 2002 | B1 |
| 6363249 | Nordeman et al. | Mar 2002 | B1 |
| 6363412 | Niwa et al. | Mar 2002 | B1 |
| 6374250 | Ajtai et al. | Apr 2002 | B2 |
| 6381700 | Yoshida | Apr 2002 | B1 |
| 6389462 | Cohen et al. | May 2002 | B1 |
| 6396482 | Griffin et al. | May 2002 | B1 |
| 6397307 | Ohran | May 2002 | B2 |
| 6397351 | Miller et al. | May 2002 | B1 |
| 6401104 | LaRue et al. | Jun 2002 | B1 |
| 6405218 | Boothby | Jun 2002 | B1 |
| 6418309 | Moon et al. | Jul 2002 | B1 |
| 6430289 | Liffick | Aug 2002 | B1 |
| 6434627 | Millet et al. | Aug 2002 | B1 |
| 6437818 | Ludwig et al. | Aug 2002 | B1 |
| 6449622 | LaRue et al. | Sep 2002 | B1 |
| 6453392 | Flynn, Jr. | Sep 2002 | B1 |
| 6457062 | Pivowar et al. | Sep 2002 | B1 |
| 6460036 | Herz | Oct 2002 | B1 |
| 6462644 | Howell et al. | Oct 2002 | B1 |
| 6463464 | Lazaridis et al. | Oct 2002 | B1 |
| 6466967 | Landsman et al. | Oct 2002 | B2 |
| 6473621 | Heie | Oct 2002 | B1 |
| 6480896 | Brown et al. | Nov 2002 | B1 |
| 6484143 | Swildens et al. | Nov 2002 | B1 |
| 6487560 | LaRue et al. | Nov 2002 | B1 |
| 6490655 | Kershaw | Dec 2002 | B1 |
| 6496944 | Hsiao et al. | Dec 2002 | B1 |
| 6499108 | Johnson | Dec 2002 | B1 |
| 6505216 | Schutzman et al. | Jan 2003 | B1 |
| 6507891 | Challenger et al. | Jan 2003 | B1 |
| 6516314 | Birkler et al. | Feb 2003 | B1 |
| 6516327 | Zondervan et al. | Feb 2003 | B1 |
| 6519452 | Agostino et al. | Feb 2003 | B1 |
| 6523063 | Hanson | Feb 2003 | B1 |
| 6523079 | Kikinis et al. | Feb 2003 | B2 |
| 6532588 | Porter | Mar 2003 | B1 |
| 6535743 | Kennedy et al. | Mar 2003 | B1 |
| 6535949 | Parker | Mar 2003 | B1 |
| 6539494 | Abramson et al. | Mar 2003 | B1 |
| 6542933 | Durst, Jr. et al. | Apr 2003 | B1 |
| 6546425 | Hanson et al. | Apr 2003 | B1 |
| 6549933 | Barrett et al. | Apr 2003 | B1 |
| 6553375 | Huang et al. | Apr 2003 | B1 |
| 6553410 | Kikinis | Apr 2003 | B2 |
| 6553413 | Lewin et al. | Apr 2003 | B1 |
| 6564336 | Majkowski | May 2003 | B1 |
| 6567850 | Freishtat et al. | May 2003 | B1 |
| 6567857 | Gupta et al. | May 2003 | B1 |
| 6581065 | Rodkin et al. | Jun 2003 | B1 |
| 6584454 | Hummel et al. | Jun 2003 | B1 |
| 6589290 | Maxwell et al. | Jul 2003 | B1 |
| 6591266 | Li et al. | Jul 2003 | B1 |
| 6591306 | Redlich | Jul 2003 | B1 |
| 6591362 | Li | Jul 2003 | B1 |
| 6597700 | Golikeri et al. | Jul 2003 | B2 |
| 6601143 | Lamparter | Jul 2003 | B1 |
| 6609005 | Chern | Aug 2003 | B1 |
| 6628194 | Hellebust et al. | Sep 2003 | B1 |
| 6636894 | Short et al. | Oct 2003 | B1 |
| 6640302 | Subramaniam et al. | Oct 2003 | B1 |
| 6643707 | Booth | Nov 2003 | B1 |
| 6647399 | Zaremba | Nov 2003 | B2 |
| 6654746 | Wong et al. | Nov 2003 | B1 |
| 6662212 | Chandhok et al. | Dec 2003 | B1 |
| 6665721 | Hind et al. | Dec 2003 | B1 |
| 6668254 | Matson et al. | Dec 2003 | B2 |
| 6671724 | Pandya et al. | Dec 2003 | B1 |
| 6671757 | Multer et al. | Dec 2003 | B1 |
| 6684206 | Chen et al. | Jan 2004 | B2 |
| 6684302 | Kershaw | Jan 2004 | B2 |
| 6694335 | Hopmann et al. | Feb 2004 | B1 |
| 6694336 | Multer et al. | Feb 2004 | B1 |
| 6701316 | Li et al. | Mar 2004 | B1 |
| 6704849 | Steegmans | Mar 2004 | B2 |
| 6714987 | Amin et al. | Mar 2004 | B1 |
| 6718336 | Saffer et al. | Apr 2004 | B1 |
| 6718348 | Novak et al. | Apr 2004 | B1 |
| 6718390 | Still et al. | Apr 2004 | B1 |
| 6725239 | Sherman et al. | Apr 2004 | B2 |
| 6728530 | Heinonen et al. | Apr 2004 | B1 |
| 6732101 | Cook | May 2004 | B1 |
| 6732264 | Sun et al. | May 2004 | B1 |
| 6738789 | Multer et al. | May 2004 | B2 |
| 6741851 | Lee et al. | May 2004 | B1 |
| 6745040 | Zimmerman | Jun 2004 | B2 |
| 6757696 | Multer et al. | Jun 2004 | B2 |
| 6757698 | Davidson et al. | Jun 2004 | B2 |
| 6757712 | Bastian et al. | Jun 2004 | B1 |
| 6781575 | Hawkins et al. | Aug 2004 | B1 |
| 6795848 | Border et al. | Sep 2004 | B1 |
| 6799214 | Li | Sep 2004 | B1 |
| 6804690 | Dysert et al. | Oct 2004 | B1 |
| 6804783 | Wesinger, Jr. et al. | Oct 2004 | B1 |
| 6810411 | Coughlin et al. | Oct 2004 | B1 |
| 6812961 | Parulski et al. | Nov 2004 | B1 |
| 6813487 | Trommelen | Nov 2004 | B1 |
| 6816481 | Adams et al. | Nov 2004 | B1 |
| 6829654 | Jungck | Dec 2004 | B1 |
| 6836657 | Ji et al. | Dec 2004 | B2 |
| 6836765 | Sussman | Dec 2004 | B1 |
| 6839022 | Benco et al. | Jan 2005 | B1 |
| 6839568 | Suzuki | Jan 2005 | B2 |
| 6842695 | Tu et al. | Jan 2005 | B1 |
| 6850944 | MacCall et al. | Feb 2005 | B1 |
| 6868451 | Peacock | Mar 2005 | B1 |
| 6870921 | Elsey et al. | Mar 2005 | B1 |
| 6886013 | Beranek | Apr 2005 | B1 |
| 6892225 | Tu et al. | May 2005 | B1 |
| 6892245 | Crump et al. | May 2005 | B1 |
| 6904449 | Quinones | Jun 2005 | B1 |
| 6904460 | Raciborski et al. | Jun 2005 | B1 |
| 6920488 | Le Pennec et al. | Jul 2005 | B1 |
| 6925476 | Multer | Aug 2005 | B1 |
| 6925477 | Champagne et al. | Aug 2005 | B1 |
| 6934767 | Jellinek | Aug 2005 | B1 |
| 6944651 | Onyon et al. | Sep 2005 | B2 |
| 6944676 | Armbruster et al. | Sep 2005 | B1 |
| 6954660 | Aoyama | Oct 2005 | B2 |
| 6954783 | Bodwell et al. | Oct 2005 | B1 |
| 6959331 | Traversat et al. | Oct 2005 | B1 |
| 6963914 | Breitbart et al. | Nov 2005 | B1 |
| 6973299 | Apfel | Dec 2005 | B2 |
| 6975709 | Wullert, II | Dec 2005 | B2 |
| 6996617 | Aiken, Jr. et al. | Feb 2006 | B1 |
| 6996631 | Aiken, Jr. et al. | Feb 2006 | B1 |
| 7003555 | Jungck | Feb 2006 | B1 |
| 7003668 | Berson et al. | Feb 2006 | B2 |
| 7007041 | Multer et al. | Feb 2006 | B2 |
| 7010578 | Lewin et al. | Mar 2006 | B1 |
| 7016964 | Still et al. | Mar 2006 | B1 |
| 7023868 | Rabenko et al. | Apr 2006 | B2 |
| 7024491 | Hanmann et al. | Apr 2006 | B1 |
| 7030730 | Zondervan | Apr 2006 | B1 |
| 7035878 | Multer et al. | Apr 2006 | B1 |
| 7039656 | Tsai et al. | May 2006 | B1 |
| 7051275 | Gupta et al. | May 2006 | B2 |
| 7054594 | Bloch et al. | May 2006 | B2 |
| 7054952 | Schwerdtfeger et al. | May 2006 | B1 |
| 7082476 | Cohen et al. | Jul 2006 | B1 |
| 7085817 | Tock et al. | Aug 2006 | B1 |
| 7096418 | Singhal et al. | Aug 2006 | B1 |
| 7099915 | Tenereillo et al. | Aug 2006 | B1 |
| 7103794 | Malcolm et al. | Sep 2006 | B2 |
| 7107043 | Aoyama | Sep 2006 | B2 |
| 7110954 | Yung et al. | Sep 2006 | B2 |
| 7116681 | Hovell et al. | Oct 2006 | B1 |
| 7133503 | Revisky | Nov 2006 | B2 |
| 7146161 | Chou | Dec 2006 | B2 |
| 7158805 | Park et al. | Jan 2007 | B1 |
| 7159032 | Jim et al. | Jan 2007 | B2 |
| 7162494 | Arellano | Jan 2007 | B2 |
| 7167728 | Wagner et al. | Jan 2007 | B1 |
| 7181628 | Sato et al. | Feb 2007 | B2 |
| 7197574 | Ishiyama | Mar 2007 | B1 |
| 7233791 | Gilbert et al. | Jun 2007 | B2 |
| 7237027 | Raccah et al. | Jun 2007 | B1 |
| 7249175 | Donaldson | Jul 2007 | B1 |
| 7269433 | Vargas et al. | Sep 2007 | B2 |
| 7284051 | Okano et al. | Oct 2007 | B1 |
| 7289964 | Bowman-Amuah | Oct 2007 | B1 |
| 7293074 | Jellinek et al. | Nov 2007 | B1 |
| 7308651 | Kling et al. | Dec 2007 | B2 |
| 7315826 | Guheen et al. | Jan 2008 | B1 |
| 7317907 | Linkert et al. | Jan 2008 | B2 |
| 7328341 | Eun et al. | Feb 2008 | B1 |
| 7343568 | Jiang et al. | Mar 2008 | B2 |
| 7349719 | Buniatyan | Mar 2008 | B2 |
| 7356559 | Jacobs et al. | Apr 2008 | B1 |
| 7363233 | Levine | Apr 2008 | B1 |
| 7383061 | Hawkins | Jun 2008 | B1 |
| 7392034 | Westman et al. | Jun 2008 | B2 |
| 7415486 | Multer et al. | Aug 2008 | B2 |
| 7440746 | Swan | Oct 2008 | B1 |
| 7447743 | Jordan, Jr. | Nov 2008 | B1 |
| 7454500 | Hsu et al. | Nov 2008 | B1 |
| 7499888 | Tu et al. | Mar 2009 | B1 |
| 7505762 | Onyon et al. | Mar 2009 | B2 |
| 7519702 | Allan | Apr 2009 | B1 |
| 7539697 | Akella et al. | May 2009 | B1 |
| 7587398 | Fredricksen et al. | Sep 2009 | B1 |
| 7596609 | Refuah et al. | Sep 2009 | B1 |
| 7663652 | Reese | Feb 2010 | B1 |
| 7707150 | Sundararajan et al. | Apr 2010 | B2 |
| 7853664 | Wang et al. | Dec 2010 | B1 |
| 8010095 | Natsuno et al. | Aug 2011 | B2 |
| 8073954 | Tu et al. | Dec 2011 | B1 |
| 8224308 | Gavrylyako et al. | Jul 2012 | B1 |
| 20010014893 | Boothby | Aug 2001 | A1 |
| 20010028363 | Nomoto et al. | Oct 2001 | A1 |
| 20010034737 | Cane et al. | Oct 2001 | A1 |
| 20010044805 | Multer et al. | Nov 2001 | A1 |
| 20010047471 | Johnson | Nov 2001 | A1 |
| 20010051920 | Joao et al. | Dec 2001 | A1 |
| 20010056473 | Arneson et al. | Dec 2001 | A1 |
| 20020007303 | Brookler et al. | Jan 2002 | A1 |
| 20020010868 | Nakashima et al. | Jan 2002 | A1 |
| 20020016818 | Kirani et al. | Feb 2002 | A1 |
| 20020016912 | Johnson | Feb 2002 | A1 |
| 20020023136 | Silver et al. | Feb 2002 | A1 |
| 20020032751 | Bharadwaj | Mar 2002 | A1 |
| 20020040369 | Multer et al. | Apr 2002 | A1 |
| 20020049852 | Lee et al. | Apr 2002 | A1 |
| 20020055909 | Fung et al. | May 2002 | A1 |
| 20020056011 | Nardone et al. | May 2002 | A1 |
| 20020059116 | Bulatovic et al. | May 2002 | A1 |
| 20020062365 | Nishikawa et al. | May 2002 | A1 |
| 20020067816 | Bushnell | Jun 2002 | A1 |
| 20020069178 | Hoffman | Jun 2002 | A1 |
| 20020072350 | Fukuzato | Jun 2002 | A1 |
| 20020073212 | Sokol et al. | Jun 2002 | A1 |
| 20020078075 | Colson et al. | Jun 2002 | A1 |
| 20020082995 | Christie | Jun 2002 | A1 |
| 20020083325 | Mediratta et al. | Jun 2002 | A1 |
| 20020087588 | McBride et al. | Jul 2002 | A1 |
| 20020091785 | Ohlenbusch et al. | Jul 2002 | A1 |
| 20020116444 | Chaudhri et al. | Aug 2002 | A1 |
| 20020118192 | Couckuyt et al. | Aug 2002 | A1 |
| 20020120600 | Schiavone et al. | Aug 2002 | A1 |
| 20020126814 | Awada et al. | Sep 2002 | A1 |
| 20020128908 | Levin et al. | Sep 2002 | A1 |
| 20020138582 | Chandra et al. | Sep 2002 | A1 |
| 20020138765 | Fishman et al. | Sep 2002 | A1 |
| 20020152278 | Pontenzone et al. | Oct 2002 | A1 |
| 20020162011 | Tanaka et al. | Oct 2002 | A1 |
| 20020168964 | Kraft | Nov 2002 | A1 |
| 20020168975 | Gresham et al. | Nov 2002 | A1 |
| 20020194196 | Weinberg et al. | Dec 2002 | A1 |
| 20030021274 | Siikaniemi et al. | Jan 2003 | A1 |
| 20030028451 | Ananian | Feb 2003 | A1 |
| 20030028554 | Koskimies et al. | Feb 2003 | A1 |
| 20030028603 | Aktas et al. | Feb 2003 | A1 |
| 20030028647 | Grosu | Feb 2003 | A1 |
| 20030037020 | Novak et al. | Feb 2003 | A1 |
| 20030043195 | Kling et al. | Mar 2003 | A1 |
| 20030046433 | Luzzatti et al. | Mar 2003 | A1 |
| 20030061163 | Durfield | Mar 2003 | A1 |
| 20030065934 | Angelo et al. | Apr 2003 | A1 |
| 20030069874 | Hertzog et al. | Apr 2003 | A1 |
| 20030084121 | De Boor et al. | May 2003 | A1 |
| 20030093797 | Bazzaz | May 2003 | A1 |
| 20030110280 | Hinchliffe et al. | Jun 2003 | A1 |
| 20030115240 | Cho | Jun 2003 | A1 |
| 20030134625 | Choi | Jul 2003 | A1 |
| 20030135463 | Brown et al. | Jul 2003 | A1 |
| 20030139172 | Lampela et al. | Jul 2003 | A1 |
| 20030158960 | Engberg | Aug 2003 | A1 |
| 20030163483 | Zingher et al. | Aug 2003 | A1 |
| 20030172236 | Iyengar et al. | Sep 2003 | A1 |
| 20030204568 | Bhargava et al. | Oct 2003 | A1 |
| 20030208546 | DeSalvo et al. | Nov 2003 | A1 |
| 20030217181 | Kiiskinen | Nov 2003 | A1 |
| 20030224760 | Day | Dec 2003 | A1 |
| 20030229723 | Kangas et al. | Dec 2003 | A1 |
| 20030229898 | Babu et al. | Dec 2003 | A1 |
| 20030233383 | Koskimies | Dec 2003 | A1 |
| 20030236933 | Shigeta et al. | Dec 2003 | A1 |
| 20040003390 | Canter et al. | Jan 2004 | A1 |
| 20040054746 | Shibata | Mar 2004 | A1 |
| 20040058673 | Irlam et al. | Mar 2004 | A1 |
| 20040093317 | Swan | May 2004 | A1 |
| 20040093342 | Arbo et al. | May 2004 | A1 |
| 20040093385 | Yamagata | May 2004 | A1 |
| 20040110497 | Little | Jun 2004 | A1 |
| 20040111465 | Chuang et al. | Jun 2004 | A1 |
| 20040120477 | Nguyen et al. | Jun 2004 | A1 |
| 20040128324 | Sheynman et al. | Jul 2004 | A1 |
| 20040132428 | Mulligan | Jul 2004 | A1 |
| 20040142711 | Mahonen et al. | Jul 2004 | A1 |
| 20040146150 | Barnes | Jul 2004 | A1 |
| 20040148408 | Nadarajah | Jul 2004 | A1 |
| 20040162830 | Shirwadkar et al. | Aug 2004 | A1 |
| 20040192260 | Sugimoto et al. | Sep 2004 | A1 |
| 20040192282 | Vasudevan | Sep 2004 | A1 |
| 20040193953 | Callahan et al. | Sep 2004 | A1 |
| 20040204120 | Jiles | Oct 2004 | A1 |
| 20040224665 | Kokubo | Nov 2004 | A1 |
| 20040235523 | Schrire et al. | Nov 2004 | A1 |
| 20040267390 | Ben-Yaacov et al. | Dec 2004 | A1 |
| 20040267676 | Feng et al. | Dec 2004 | A1 |
| 20040267944 | Britt | Dec 2004 | A1 |
| 20050021571 | East | Jan 2005 | A1 |
| 20050032527 | Sheha et al. | Feb 2005 | A1 |
| 20050038863 | Onyon et al. | Feb 2005 | A1 |
| 20050044404 | Bhansali et al. | Feb 2005 | A1 |
| 20050050117 | Seo et al. | Mar 2005 | A1 |
| 20050054354 | Roman et al. | Mar 2005 | A1 |
| 20050060392 | Goring et al. | Mar 2005 | A1 |
| 20050064859 | Kotzin et al. | Mar 2005 | A1 |
| 20050081152 | Commarford | Apr 2005 | A1 |
| 20050086296 | Chi et al. | Apr 2005 | A1 |
| 20050086318 | Aubault | Apr 2005 | A1 |
| 20050090253 | Kim et al. | Apr 2005 | A1 |
| 20050096975 | Moshe | May 2005 | A1 |
| 20050100150 | Dhara et al. | May 2005 | A1 |
| 20050102257 | Onyon et al. | May 2005 | A1 |
| 20050102328 | Ring et al. | May 2005 | A1 |
| 20050114470 | Bal | May 2005 | A1 |
| 20050131990 | Jewell | Jun 2005 | A1 |
| 20050144200 | Hesselink et al. | Jun 2005 | A1 |
| 20050144251 | Slate | Jun 2005 | A1 |
| 20050157858 | Rajagopalan | Jul 2005 | A1 |
| 20050191998 | Onyon et al. | Sep 2005 | A1 |
| 20050203971 | Koskimies et al. | Sep 2005 | A1 |
| 20050203992 | Tanaka et al. | Sep 2005 | A1 |
| 20050204001 | Stein et al. | Sep 2005 | A1 |
| 20050210101 | Janik | Sep 2005 | A1 |
| 20050216300 | Appelman et al. | Sep 2005 | A1 |
| 20050227674 | Kopra et al. | Oct 2005 | A1 |
| 20050233800 | Jones | Oct 2005 | A1 |
| 20050240494 | Cue et al. | Oct 2005 | A1 |
| 20050246325 | Pettinati | Nov 2005 | A1 |
| 20050273632 | Kawakami | Dec 2005 | A1 |
| 20050283741 | Balabanovic et al. | Dec 2005 | A1 |
| 20060021059 | Brown et al. | Jan 2006 | A1 |
| 20060035647 | Eisner et al. | Feb 2006 | A1 |
| 20060095397 | Torres et al. | May 2006 | A1 |
| 20060129627 | Phillips et al. | Jun 2006 | A1 |
| 20060190626 | Bhogal et al. | Aug 2006 | A1 |
| 20060199599 | Gupta et al. | Sep 2006 | A1 |
| 20060212482 | Celik | Sep 2006 | A1 |
| 20060233335 | Pfleging et al. | Oct 2006 | A1 |
| 20060268842 | Takahashi et al. | Nov 2006 | A1 |
| 20060288112 | Soelberg | Dec 2006 | A1 |
| 20070005504 | Chen et al. | Jan 2007 | A1 |
| 20070022469 | Cooper et al. | Jan 2007 | A1 |
| 20070043739 | Takai et al. | Feb 2007 | A1 |
| 20070047533 | Criddle et al. | Mar 2007 | A1 |
| 20070050734 | Busey | Mar 2007 | A1 |
| 20070061331 | Ramer et al. | Mar 2007 | A1 |
| 20070082668 | Silver et al. | Apr 2007 | A1 |
| 20070094042 | Ramer et al. | Apr 2007 | A1 |
| 20070127597 | Ammer et al. | Jun 2007 | A1 |
| 20070214149 | Bodin et al. | Sep 2007 | A1 |
| 20070220419 | Stibel et al. | Sep 2007 | A1 |
| 20070226272 | Huang et al. | Sep 2007 | A1 |
| 20070226783 | Mimlitsch | Sep 2007 | A1 |
| 20080005080 | Xiques et al. | Jan 2008 | A1 |
| 20080005282 | Gaedcke | Jan 2008 | A1 |
| 20080009268 | Ramer et al. | Jan 2008 | A1 |
| 20080022220 | Cheah | Jan 2008 | A1 |
| 20080027826 | Popick et al. | Jan 2008 | A1 |
| 20080039020 | Eskin | Feb 2008 | A1 |
| 20080051071 | Vishwanathan et al. | Feb 2008 | A1 |
| 20080051117 | Khare et al. | Feb 2008 | A1 |
| 20080059897 | Dilorenzo | Mar 2008 | A1 |
| 20080064378 | Kahan et al. | Mar 2008 | A1 |
| 20080089299 | Lindsley | Apr 2008 | A1 |
| 20080104442 | Diao et al. | May 2008 | A1 |
| 20080120199 | Pirnack et al. | May 2008 | A1 |
| 20080127289 | Julia et al. | May 2008 | A1 |
| 20080208617 | Onyon et al. | Aug 2008 | A1 |
| 20080214167 | Natsuno et al. | Sep 2008 | A1 |
| 20080268823 | Shalev et al. | Oct 2008 | A1 |
| 20080270805 | Kean | Oct 2008 | A1 |
| 20080294768 | Sampson et al. | Nov 2008 | A1 |
| 20090012940 | Ives et al. | Jan 2009 | A1 |
| 20090037828 | Waite et al. | Feb 2009 | A1 |
| 20090138546 | Cruzada | May 2009 | A1 |
| 20090327305 | Roberts et al. | Dec 2009 | A1 |
| 20100205448 | Tarhan et al. | Aug 2010 | A1 |
| 20100251230 | O'Farrell et al. | Sep 2010 | A1 |
| 20110107203 | Nash et al. | May 2011 | A1 |
| 20110269424 | Multer et al. | Nov 2011 | A1 |
| 20120151346 | McClements, IV | Jun 2012 | A1 |
| Number | Date | Country |
|---|---|---|
| 1202662 | Dec 1998 | CN |
| 1455522 | Nov 2003 | CN |
| 1313697 | Feb 2005 | CN |
| 2003-122958 | Jul 2006 | CN |
| 0801487 | Oct 1997 | EP |
| 0 836 131 | Apr 1998 | EP |
| 0836301 | Apr 1998 | EP |
| 0924917 | Jun 1999 | EP |
| 0930593 | Jul 1999 | EP |
| 1024441 | Feb 2000 | EP |
| 0986225 | Mar 2000 | EP |
| 1139608 | Oct 2001 | EP |
| 1180890 | Feb 2002 | EP |
| 1263244 | Apr 2002 | EP |
| 1998-106683 | Apr 1998 | FR |
| 2366050 | Jun 2001 | GB |
| 7303146 | Nov 1995 | JP |
| 10191453 | Jul 1998 | JP |
| 11242620 | Sep 1999 | JP |
| 11242677 | Sep 1999 | JP |
| 2000232680 | Aug 2000 | JP |
| 2000316053 | Nov 2000 | JP |
| 2002142254 | May 2002 | JP |
| 2002185575 | Jun 2002 | JP |
| 2002247144 | Aug 2002 | JP |
| 2002314689 | Oct 2002 | JP |
| 2003259011 | Sep 2003 | JP |
| WO 9704391 | Feb 1997 | WO |
| WO 9739564 | Oct 1997 | WO |
| WO 9741520 | Nov 1997 | WO |
| WO 9803005 | Jan 1998 | WO |
| WO 9821648 | May 1998 | WO |
| WO 9829994 | Jul 1998 | WO |
| WO 9854662 | Dec 1998 | WO |
| WO 9856159 | Dec 1998 | WO |
| WO 9905813 | Feb 1999 | WO |
| WO 9906900 | Feb 1999 | WO |
| WO 9936870 | Jul 1999 | WO |
| WO 9940514 | Aug 1999 | WO |
| WO 9945451 | Sep 1999 | WO |
| WO 9945484 | Sep 1999 | WO |
| WO 9946701 | Sep 1999 | WO |
| WO 9950761 | Oct 1999 | WO |
| WO 9965256 | Dec 1999 | WO |
| WO 0011832 | Mar 2000 | WO |
| WO 0016222 | Mar 2000 | WO |
| WO 0029998 | May 2000 | WO |
| 0133874 | May 2001 | WO |
| WO 0171539 | Sep 2001 | WO |
| WO 0180535 | Sep 2001 | WO |
| 0217140 | Feb 2002 | WO |
| 03056789 | Jul 2003 | WO |
| 03-083716 | Oct 2003 | WO |
| WO 2005112586 | Dec 2005 | WO |
| Entry |
|---|
| Final Office Action mailed Mar. 9, 2010 in U.S. Appl. No. 11/437,554, 20 pgs. |
| Rou et al., “Online File Storage System,” 2002 Student Conference on Research and Development Proceedings, Shah Alam, Malaysia, Nov. 7, 2002, IEEE, pp. 83-86. |
| Agarwal et al., “On the Scalability of Data Synchronization Protocols for PDAs and Mobile Devices,” Jul. 2002, IEEE Network, pp. 22-28. |
| Anonymous: “Download filter for MMS”, Research Disclosure, Mason Publications, Hampshire, GB, vol. 457, No. 28, May 1, 2002, XP007130322, ISSN: 0374-4353. |
| Intellisync Email Accelerator, A detailed guide to functionality—Product functionality paper, Mar. 2004, pp. 1-18. |
| Lee et al, “Monitoring Data Archives for Grid Environments,” Jul. 2002, 10 pgs. |
| Batista et al. “Mining Web Access Logs of an On-line Newspaper” Jul. 2002, 8 pgs http://ectrl.itc.it/rpec/. |
| Internet Mail Consortium: :vCard Overview, Oct. 13, 1998, 3 pages, Retrieved from the Internet: www.imc.org/pdi/vcardoverview. |
| Internet Mail Consortium: :vCard The Electronic Business Card, Jan. 1, 1997, 5 pages, Retrieved from the Internet: www.imc.org/pdi/vcardwhite.html. |
| Jennings, J. “SyncML DM: A SyncML Protocol for Device Management,” slide presentation, downloaded from www.openalliance.org/tech/affiliates/syncml/syncmldm—28jan02—james—jennings.pdf, Jan. 28, 2002, 23 pgs. |
| Torio, T. “The SyncML Road Ahead—Application Development and Device Management,” slide presentation, downloaded from www.openalliance.org/tech/affiliates/syncml/syncmldm—30jan02—teemu—Toroi.pdf, Jan. 30, 2002. |
| Sheha, M.A.et al. “Specification and Drawings of U.S. Appl. No. 60/493,704,” filed Aug. 8, 2003. |
| FusionOne “FusionOne Unveils Integrated Carrier Product Suite to Deliver Mobility Solutions to Individuals and the Enterprise,” Press Release, Mar. 18, 2002, 3 pgs. |
| FusionOne “FusionOne Unveils Mighty Phone™ Wireless Service,” Press Release,Nov. 18, 2002, 3 pgs. |
| Business Wire, “SyncML Announces 18 New Compliant Products, SyncML DM Engineering Event Held; 99 Devices No Certified-SyncML Compliant,” Press Release, Sep. 25, 2002. |
| Reed, Benjamin C., et al.,“Authenticating Network-Attached Storage,”IEEE, Jan.-Feb. 2000, pp. 49-57. |
| Gaskin, J.E.:Messaging-Instant Enterprise—Once a Novelty item, IM is Becoming a More Serious Tool for Business Users, InternetWeek, No. 810, Apr. 24, 2000, p. 55. |
| BusinessWire, “FusionOne Partners with WhitePages.com to Deliver Automatic Synchronization for Online Subscriber,” press release, Oct. 11, 2000. |
| Pabla, C.“SyncML Intensive,” downloaded from www-128.ibm.com/developerworks/wireless/library/we-syncml2, Apr. 1, 2002. |
| Malone, et al., Semi-Structured Messages are Surprisingly Useful for Computer-Supported Coordination, Proceedings of the Conference on Computer-Supported Cooperative Work, Austin, Texas, Dec. 3-5, 1986, pp. 1-26. |
| Patel et al.,“The Multimedia Fax-MIME Gateway,” 8440 IEEE MultiMedia No. 4, Jan. 1994, 7 pgs. |
| Lamb et al.,“LAN-Based Office for the Enterprise, A Case Study,” Advantis Company, White Plains, NY 10605, Jan. 1994 IEEE, pp. 440-447. |
| Starfish, “TrueSync Data Synchronization,” Software, http://www.starfishsoftware.com/solutions/data/data.html, Jan. 2003. |
| Office Action mailed Jul. 8, 2010, U.S. Appl. No. 11/437,554, pp. 1-20. |
| U.S. Appl. No. 11/437,554, Advisory Action mailed Jul. 8, 2009, pp. 2-3. |
| Non-final Office Action mailed Sep. 22, 2009, in U.S. Appl. No. 11/437,554, pp. 1-18. |
| Japanese Office Action, Nov. 1, 2010, Application No. 2007-513357, pp. 4-7. |
| European Patent Office, Office Action mailed May 19, 2011, for European Application No. 05748340.6, Ref No. P041781EPIRH, 6 pgs. |
| Chinese Office Action, Aug. 3, 2010, Application No. 200580020480.7, pp. 1-11. |
| Finnigan, Anne, “The Safe Way to Shop Online,” Sep. 1998, p. 162, Good Housekeeping, v. 227 No. 3. |
| Chase, Larry, “Taking Transactions Online,”Oct. 1998, pp. 124-132, Target Marketing, v.21 No. 10. |
| Gong, Li; “Increasing Availability and Security of an Authentication Service,” Jun. 1993, pp. 657-662, IEEE Journal on Selected Areas in Communications, v. 11 No. 5. |
| DeMaio, Harry B., “My Mips Are Sealed,” Sep./Oct. 1993, pp. 46-51, Chief Information Officer Journal, v. 5 iss.7. |
| Final Office Action dated Dec. 13, 2011, U.S. Appl. No. 11/906,586, filed Oct. 2, 2007, Richard Onyon. |
| Non-final Office Action dated Sep. 13, 2011, U.S. Appl. No. 12/319,087, filed Dec. 30, 2008, Richard Onyon. |
| Office Action mailed Jan. 29, 2013, U.S. Appl. No. 13/479,216, filed May 23, 2012, Richard Onyon et al. |
| Number | Date | Country | |
|---|---|---|---|
| 20060052091 A1 | Mar 2006 | US |
| Number | Date | Country | |
|---|---|---|---|
| 60570409 | May 2004 | US |
