Advanced contact identification system

A system and method of 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.

BACKGROUND OF THE INVENTION

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.

SUMMARY OF THE INVENTION

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.

DETAILED DESCRIPTION

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.

FIG. 1illustrates a general method in accordance with the present invention. At step202, a subscriber joins the system by providing account creation information. At step202, the user may establish an account using a user name, a secure password, and provide other configuration information. This step may be performed via a phone based interface or via a web based interface, or any other suitable interface means.

At step204, 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 table206, 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 step204is 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 step208, 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 inFIGS. 4 and 5may be offered to the unlinked user giving them the opportunity to subscribe to the system and establish a true link with the inviter. “True”—or “direct” linked users exist when both users have each other's contact information in their mobile device's phone book. These users have established some level of relationship outside of the service provided by the enterprise service provider or via system's “Invitation” function, and will automatically exchange and maintain any information each user has configured. Within a context of the foregoing description a “buddy” is any user who has established a true link with an individual user. For privacy as well as practicality, information exchange in the system occurs only between true linked users. Users who possess only a half-link to one another may invite the half-linked user to join the system and establish a true link.

When the user provides their own personification information to the service host at step204, step208may 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 step208, 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 step210, 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 step212.

Optionally, at step214, 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 process216transmits 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 step218, 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 users210and 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 step220, 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).

FIG. 2shows the method of the present invention once a subscriber has established a relationship with the enterprise service provider in accordance with the present invention and installed the application140on the user's phone100. At step500, when a Subscriber b receives a call from another member (subscriber A) who has downloaded the user's information into the user's phone, advanced caller identification features can provide a member's information at step506on the user's phone.

In one aspect, the system supports controlling both the calling user's phone and the called user's phone. At step501, 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 step501, 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 alert503may be provided to Subscriber A.

At step502, if the call is initiated by subscriber A and received by subscriber B, optionally, at step504, the receiving user can configure the phone to prevent calls during a specific period of time. Hence, at step504the 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 step512. 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 step508, if the member has chosen to provide the member's GPS information, at step508the GPS can be provided in a notification at step510provided 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 phone100at step506. Step501indicates 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 client140with 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.

FIG. 3illustrates a general overview of a system for implementing the present invention. As shown inFIG. 3, a wireless communication device, such as a phone100, is connected to a wireless communications link, such as a cellular network150, to transmit voice and data communications to other devices coupling to the wireless network. It will be understood that the wireless link may be a wireless internet link or a cellular network maintained by a cellular carrier, a GSM or CDMA network, or some other wireless communications link. The carrier may comprise the enterprise service provider or may be separate from the enterprise service provider. Data may be transmitted over the network in any number of known formats.

An advanced ID service server160is also provided which communicates with the telephone via wireless network150directly over a data connection or via a SyncML server195. Various embodiments of a system for implementing the advanced ID service are discussed herein. InFIG. 3, the ID server160communicates directly with the phone100. In alternative embodiments, discussed below, the ID system is implemented on top of a synchronization system such as that described in U.S. Pat. No. 6,671,757, 6,694,336 or 6,757,696.

Phone100may be provided with a system application or agent140. System agent140can include a SyncML communication client designed to interact with a SyncML server195in accordance with approved and proposed versions of the SyncML OMA DS specification, including proposed extensions, (available at http://www.openmobilealliance.org). Alternatively, agent140can be an application designed to communicate with server160using 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 server160via another protocol, including a proprietary protocol. In one embodiment, the agent140is a fully implemented SyncML client and server160includes a SyncML server. In another embodiment, the application140is a client application device sync agent such as that disclosed in U.S. Pat. No. 6,671,757. Various embodiments of the client application140are set forth below.

In accordance with the present invention, a phone100includes a system memory122which may further include an operating system124having operating system service including telephony and linking services, networking services, multimedia and graphics display services all provided to a user interface120. OS125my 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 services135and an operating system kernel may also be provided. The operating system may additionally provide an SMS client145built into the operating system allowing short messages to be provided across the wireless communications line150to other users. Still further, a SyncML client132may be provided and supported by the operating system services124. The phone100includes a native phone data store170which 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 phone100, the space allowed in the system memory, and the services provided by the operating system124.

A client application140, various embodiments of which are discussed herein, is also loaded into phone100. As will be well understood by one of average skill in the art, client application140can 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 services124, selects the application from offerings provided by the service provider or carrier who maintains the wireless communications line150, or an enterprise service provider who maintains the system server160, and installs the application onto phone100. In an alternative embodiment, agent140is 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 base510.

Client100includes at least a user interface120, the application140having a communication or sync engine and data store manager, a SyncML client132and a local database150. The client application140provides an appropriate graphical user interface to UI120which 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 server180. 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 server160is a centralized storage location for all system service information, including buddy, persona, relationship, and user data. Clients140can 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 server160, webserver180or SyncML server195includes a processor114, memory104, nonvolatile storage device106, portable storage device110, network interface112and I/O device(s)116. The choice of processor is not critical as long as a suitable processor with sufficient speed is chosen. Memory104could be any conventional computer memory known in the art. Nonvolatile storage device106could include a hard drive, CDROM, CDRW, flash memory card, or any other nonvolatile storage device. Portable storage108could include a floppy disk drive or another portable storage device. The computing system may include one or more network interfaces102. An example of a network interface includes a network card connected to an Ethernet or other type of LAN. I/O device(s)116can 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 memory104which include nonvolatile storage and volatile memory as well as, portable storage media110.

The computing system also includes a database106. In alternative embodiments, database106is stored in memory104, portable storage110or another storage device that is part of the system ofFIG. 3or is in communication with the system ofFIG. 3. Other alternative architectures can also be used that are different from that depicted inFIG. 3. Various embodiments, versions and modifications of systems ofFIG. 3can be used to implement a computing device that performs all or part of the present invention. Examples of suitable computing devices include a personal computer, computer workstation, mainframe computer, handheld computer, personal digital assistant, pager, cellular telephone, smart appliance or multiple computers, a storage area network, a server farm, or any other suitable computing device. There may be any number of servers160n, n+1 managed by a system administrator providing a back up service in accordance with the present invention.

Also provided on server160is a system data store310. The System data store is provided in the non-volatile memory space of server160. 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 server195and web sever180need not require that such servers be provided on different physical hardware than the System server160.

The system ofFIG. 2illustrates one server and client system suitable for use in the present invention. In an alternative embodiment of the invention, the advanced ID system can be constructed using a synchronization server described in U.S. Pat. No. 6,671,757, 6,694,336 or 6,757,696.

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 server850at 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 object920to 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 inFIG. 3is a server-side application ID service controller application170which includes a persona management component162, a buddy management component164, a user interface166, and a digital rights manager168. It will be understood in various implementations of the present invention, the functional components operating within the service-side application170can come in one case, push information maintained by the system of the present invention directly into phone100via a SyncML server195interacting with a fully robust SyncML client. Optionally, certain aspects of the control are handled by either the server-side application170or the client-side application140, as described herein.

In accordance with the invention, application agent140communicates personification information and changes made to the personification information stored in the data store of the telephone100to server160via the wireless network. Communication of user data from the device may take several forms. Where the client utilized SyncML communications with the server160, 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 server160. 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 server180. Description of this interface is shown below.

The server160stores user data in the personification store150in 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 server180allowing a user on a computer or other device190having a web browser may optionally be provided to allow a user to configure aspects of the system of the invention. Server180may have a hardware configuration similar to computer160and may comprise one or more physical computers. Additionally, web server180may be integrated with server160.

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 server180via the user device190.

FIG. 4one process for implementing an invitation (step212) from a subscriber to a non-subscriber or participant. At step302, a non-subscriber may receive an SMS message from another subscriber. The SMS message may contain all the information necessary for the user to publish the information into their current data book. In one aspect, this can include all persona information itself in a format which can be read by a native or non-native application such as a SyncML client, a vCard parser, or other application and incorporated into the local data store of the phone. If the user accepts the information at step304, the information can be populated into the user's data book and the next time the subscriber calls, information will be displayed on the user's phone.

In another embodiment, shown inFIG. 5, a user may receive an SMS message from a subscriber, at step404and at step406, the user can select a link stored in the SMS message to connect the user's phone with a server side data store which sends the subscriber's information directly to the phone. At step408, the user's phone downloads the information from the subscriber to the local data store in the phone.

FIG. 6illustrates the concept of different personas for different groups of users.FIG. 6shows a linkage example of different users linked to a central user600. User600“Bob” has a mobile phone which is linked to other users604,606, and602. For each group of users602,604, and606, user600can establish a different persona. A friend's persona may show Bob's personal address and home phone number and provide a first type of ringtone. A co-worker's persona604provides a more formalized name setting, a work e-mail address, and a work phone number with an undefined ringtone, a client's persona606shows an even more formal name, and includes different work and mobile phone numbers as well as a different ringtone more suitable to provide to Bob's clients.

As shown inFIG. 6, people usually have distinct groups with whom which they communicate including friends, co-workers, and clients. The establishment of different personas allows the publication of different information to each individual. As illustrated inFIG. 1, personas can include names, e-mail addresses, phone numbers, physical addresses, corporate information, a picture, ringtones, URLs, personal physical characteristics (eye/hair color, et al) and birthday information. This information handling is flexible and extensible and can accommodate any additional permanent as well as transient information such as a current time zone, digital certificates, a physical location, including GPS coordinates, and availability.

FIG. 7depicts a static structure of the records maintained for an individual user and the server of the present invention. For an individual user account700, each account will include a system ID, a plan ID (indicating a service level description), a mobile device ID, a published ID, a contact name, a contact e-mail address, and a user security pin. The user account will also contain a buddy's persona list710, a buddy list720, and an alert list730. The persona list will define a number of personas712, each including, for example, a personal ID, a name, a mobile phone, a home phone, work phone and other information as specified above with respect toFIG. 1. Other information can include a buddy image, contact list allowed settings, and ringtone information. The ringtone information740may be a list of information which links to specific ringtone records745. Each buddy in buddy list720has a buddy list record722which includes a published identifier, a last update date (indicating when the buddy record was last updated), a personal identifier, a status identifier724, and information726. Buddy information726includes a name, address book identifier, phone list numbers, e-mail address lists, and ringtone information.

FIG. 8is a sequence diagram illustrating how a new user can sign up for the system service provided by an enterprise service provider in accordance with the present invention.FIG. 8shows the sequence of steps which occur on a phone100and on the server160. Upon initialization of the application at step802, an account creation message is generated at step804. A create account message is sent to the server and at step810, an account validation process begins. The account creation step occurs at step812, and basic records are generated at step814. The account creation step804will prompt the user at step810to provide certain basic information such as name and e-mail contact information to the phone system. The account validation step810will acquire required information from the user via the phone interface, and an account will be created at step812once the required information is provided. Basic account records, including for example, base persona's from the information provided in the validation step810, are created at step814. Once the account creation step is finished, at step816, an account created message will be sent to the user's phone. At step820, contacts in the user's phone which are present in the user's native address book are collected at step820, and at step822an add contacts message or data transmission will be sent to the server160. These contacts will be checked and evaluated at step830to determine links between known users in the system already, and users who are not linked in the system. A contact list is created at step832, and the list of potential true links generated at step834. Note that true links can be created and maintained automatically, without user intervention or approval. However, in this embodiment, at step834, this list is returned to the user and presented to the user at step840. The user can then select which of those contacts the user wishes to establish links with, and these links will be established at step850. Optionally the system can establish links with any user who has already established themselves with the system service as a subscriber, who already appears in the new subscriber's local address book.

FIG. 9is an alternative method for establishing an account with the enterprise service provider wherein a synchronization system of U.S. Pat. No. 6,671,757, 6,694,336 or 6,757,696 is used. This sequence illustrates that account creation for such a system requires creation of an underlying sync account with the synchronization server, but such account can be created through the advanced ID interface.

At step902, an account creation step is initiated on the server160. Server160will also create an account with the application server185at step904. Server160will provide provisioning information906to the client140, which will then upload its address book at step908to server160. Server will attempt to establish whether direct links are present at step910and return those true links to the user at step912. Concurrently, the system will attempt to perform a synchronization with the user's contact information on the synchronization server185. At step916, the user's public persona is synced to each user's synchronization account and if there's any problem with the synchronization at step918an out of sync notification message is returned to the client140. At step920, records are retrieved regarding the records representing the buddy's personas at step920. Persona records are thereafter synced as other records are synced in accordance with the description in U.S. Pat. No. 6,671,757.

FIG. 10is a sequence diagram illustrating the establishment of a new subscriber account on server160via the server's user interface provided via the web server180. At the initialization step1000in the user interface192, account creation interface1010is provided to the server user interface192. The user provides information into the interface and the information is transmitted via a create account message to the server160. An account validation step will occur at step1012after the user has provided sufficient information to establish an account with the enterprise service provider. Once this occurs, an account creation will occur at step1014and base records will be created at step1016. When the account has been established at step1018, an account created message will be returned to the user offering the user the opportunity to create personas and providing the user with a set of default personas at step1020. The user will be provided with an initial opportunity to add images and multimedia at step1022. Next, at step1024, the user will be provided with the opportunity to check “buddies” which have been created during the contact link establishment steps208. Once the user has selected which contacts the user wishes to establish connection with, a contact list will be created at step1026. The list will be sent back to the user at step1028and may be used to initialize SMS invitations to those users who are not already established as subscribers with the enterprise service provider.

FIG. 11illustrates the interaction between a phone client and the server application in a situation where a subscriber may have lost their phone but already has an existing account with the system. Hence, the user merely needs to reestablish connection with the account using the user's new phone. At the initialization step1102, an account creation routine run on the phone application140at step1104will send an account creation message to the server160. When the account attempts to validate the user information at step1106, a determination that the account already exists will occur at step1108. This will prompt a message returning to the phone application to ask the user at step1110whether the account which has been entered is in fact the user's account. Once the user selects a prompt indicating that it is the same account at step1112, message will be returned to the server and the account will be updated at step1114with the user's new device information. The system may be utilized to restore information to the user's new phone by creating a restored data set at step1116, which may be returned to the user at step1118, and the data restored in the phone device at step1120. This restores the user's information in the user's new phone to the state it was when the user last updated the user's information on the system's server.

As noted above, the client application140and server application180provide the user with a number of functions to create and manage accounts with the ESP and the advanced ID system.

FIG. 12illustrates functional use cases for a particular subscriber. A user1200can install the application1202, such as for example by downloading the application to the phone via the phone interface, and create accounts at1204in accordance with the foregoing description. Likewise, the user can uninstall the application1206delete accounts with the enterprise service provider. The user can also use the application to upgrade accounts at1210, downgrade accounts at1214, and change account settings at1216in order to modify an account1218.

FIG. 13illustrates the functions a user1200can implement to perform tasks linking to other subscribers. The user can review a buddy list1302, requiring the buddy list to be retrieved at1304. Likewise, the user change a particular buddy's persona assignment at1305, view a mapping of buddy and personas1306, override the buddy's published information1308in their own phonebook, such as, for example, where a “buddy” had downloaded a ringtone which is not desired to user1200, remove the buddy from the list of buddies at step1310, add a buddy by performing a search function at1312, or invite another person who is not a subscriber to be the user's buddy by subscribing to the system.

FIG. 14illustrates use cases for the subscriber1200with respect to persona manipulation. The user can create persona1402, edit personas1404(which results in a modify persona1405) delete a persona at1408, or view a persona list at1410. Other instances which result in modifying a persona included assign a buddy to a persona at1412, removing a buddy from a persona at1414, assigning a ringtone to a persona at1416or assigning an image to a persona at1418. Assigning a ringtone or image also gives rise to the modification of the digital content at1420, illustrated inFIG. 15.

FIG. 15illustrates the use cases for an application user1200interacting with multimedia content. The user can record a user's own ringtone at1502, or browse system ringtones provides by a value added service provider via the enterprise service provider at1504. Recording a ringtone at1402results in a ringtone being added to the user's account at1506. The user can also browse system hosted ringtones at1508and may choose to purchase premium ringtones at1510. The user can also preview ringtones at1512, and browse system provided images at1514. The user is allowed to upload images1516to and from the user's phone when, for example, the user's phone supports taking pictures, and adding the phone to the user's account at1518. The user can also choose to select system hosted images at1520and purchase premium value added images at1522. Where a user has purchased a ringtone, at1524, the user may choose to share this ringtone with buddies. When a buddy selects the ringtone, digital rights management provider rights in the ringtone may require that the second user utilizing the ringtone purchase a license to use that ringtone for themselves. Step1524allows a prompt where the system asks the user requesting a buddy's ringtone for their own use to purchase the ringtone from the enterprise service provider. Likewise at1526, a buddy's image can be utilized by the subscriber1200, and if such image is premium content, a prompt requiring the user to purchase the image is provided at1526, at1528, the user is allowed to change digital content settings in their own phone. If for example a buddy has provided an image and/or ringtone that are unsuitable for the user1200, the user is allowed to override those settings in their own phone using the application interface.

FIGS. 16,17, and18illustrate different aspects of an advanced caller ID function as displayed on a phone100. Once the subscriber information for other users is downloaded to phone100, displays such as those set forth inFIGS. 16,17, and18may appear.

FIG. 16shows a first example of a subscriber display. When a calling subscriber “Richard” phones device100, a display1600of the user's name and an image that Richard has provided is displayed on the phone. Even if the native display of the phone100includes only support for a thumbnail image (or an image that does not occupy the entire display area of the phone) client140can cause the OS services in the phone100to display a full screen image along with soft-key enabled function menus1602,1604. The display can include an icon1606indicating additional information for the user. In this example, a birthday cake indicates it is Richard's birthday. As will be understood by those of average skill in the art, many phones include “soft-keys” which activate variable commands in a menu display in a phone. Selection of the soft keys (generally directly under an interface screen) in the example ofFIG. 16provide ignore prompt1602and a quiet prompt1604.

FIG. 17shows a depiction of a movie display1702on a phone device100with a text message1704displayed underneath. It will be understood that the image inFIG. 16is, for example, an AVI, MPEG, QuickTime, or other sample video image supported by the playback features of phone100.

FIG. 18is another example of a display for “Richard” wherein additional meta data is provided. This information is depicted in a text message at the bottom portion1802of the screen, and includes location information as well as information indicating that today is Richard's birthday.

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.

FIG. 19is a depiction of a user interface1900which may be provided by server160via web browser180to a client device190. A typical web browser1910includes the menu bar1905having a number of standard features well recognized to those of average skill in the art. Likewise a menu bar1910which includes navigation features for the world wide web is provided. User interface1900may be accessed via URL supplied by web server180. Interface1900includes a menu bar1950having a “caller ID” “home” menu option1952, a contacts menu option2000, a personals menu option2100, a my images menu option220, a my ringtones menu option2300and a my details menu option2400. The welcome screen includes a logout account and help link and displays a welcome message to a user based on the user's telephone number. The my device window1940displays the system's understanding of the user's current type of device at1942, status information1944including the number of contacts the user has specified as direct link contacts “caller ID 2.0 contacts”, the number of total contacts the user has, the number of personas the user has, the number of pictures the user has, and the number of ringtones the user has. An additional section labeled “What's hot” can be utilized by a value added reseller to display digital content such as picture1946and music1948which allow the user to download this information from the value added service provider and provided to the user's account. A My Personas window1920includes a depiction of an address card for the user John Smith and the user's general information in the form of a contact card. A recently added contact section1930displays links to user's contacts as hyperlinks1932along with a graphic depiction associated with that user's contact. It will be understood that each of the terms on the page highlighted by underlining can provide a hyperlink to more detailed information about the links content.

Selection of the contacts link2000on the menu bar1950gives rise to the user interface2000shown inFIG. 20awhich is suitable to allow the user to manage user's contacts in the system of the present invention. Contacts interface2000includes a contact display20/20which provides a user a number of options for listing and editing contacts. A user can choose from any of a number of different types of use via a drop down box2022. The view shown inFIG. 20ais that of a list view for a series of contact1040. Each contacts includes a photo depiction in column2042, a name display in column2044, a nickname field in column2046, the ringtone associated with that user in column2048, the assigned persona which may be selected via drop down boxes in column2050. Likewise, each user is associated with an invite link in column2041and tick boxes in column2052allow the user to select one or more contacts for immediate deletion via selection of the delete icon2054. Selection of one of the hyperlinks of a user contact will cause the server180to render an edit page allowing the user to edit information associated with that contact.

The functionality associated with the user interface inFIG. 20aon a web browser can likewise be provided on a screen on a phone.FIGS. 20b-20mdepict the contact interface which is displayed on a user phone.

FIG. 20bshown 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 inFIG. 20a. Options provided to the user at this point by soft-key menu items allow the user to initiate a sync at2062, or select different options at2064.

FIG. 20Cshows a menu2066resulting from selection of the “options” link inFIG. 20ballowing the user to select a contacts interface a personas interface, a sync now instruction, or more detailed settings.

AtFIG. 20D, if the user has selected contacts inFIG. 20c, a list of contacts2068is displayed. The user can use the soft keys and any other input device on the phone to highlight a user in the display for selection. Selection of a contact opens a record for that contact. Optionally an options menu2070is displayed depending on whether the contact is an advanced ID contact or not.

AtFIG. 20E, the user may display an options menu2072for an advanced ID contact by selecting the options button2064inFIG. 20D. This menu allows the user to open a contact, assign a persona to the contact, invite the contact into subscription with the system of the present invention, or disable caller ID for that particular contact.FIG. 20Fshows the options interface if a contact which has been selected inFIG. 20Dis not an advanced ID enabled contact. The only two options available for the user inFIG. 20Fare to open the contact, or invite the contact into subscription with the system.

If an advanced ID contact is opened (fromFIG. 20E), the screen ofFIG. 20gis displayed. The depiction ofFIG. 20gshows that for a particular contact and Anna K, she is a member of the co-workers persona, has a picture assigned entitled “Anna in NYC,” is assigned the moonstar midi (moonstar.mid) ringtone, as a nickname “Anna” and has a work number and a home number associated with her contact information. Each of these items is selectable by moving a selection input on the phone and depressing an entry button. For example, pressing the Anna in NYC selection will result in the display shown inFIG. 20Hwherein a graphic image associated with the contact is displayed. Selecting the moonstar midi ringtone will result in playing the ringtone in the depiction shown inFIG. 20I. Selecting the nickname will allow the user to change the nickname via an interface20J displayed on the phone.

Selecting the persona brings up a change persona menu as shown inFIG. 20K. A change persona menu will display current personas which are associated with the user and allow the user to select one or more personas to change the particular user to. If the user selects, for example, the co-worker persona, a message such as that shown inFIG. 20Lwill be displayed indicating to the user that the co-worker persona has been assigned to Anna K. Finally, if the user selects to disable caller ID from the user, a warning message is displayed such as that shown inFIG. 20M.

As shown inFIG. 21A, the persona screen displays a number of personas2110and2112,2114,2116,2118, and2120which provide the user with a short display of name of the persona, the number of users to whom the persona is assigned in parentheses, and the image the user is displaying in the persona to others, the name the user's displaying to others and the ringtone the user is displaying to others. It should be recognized that components of the interface include additional components of the persona, or less components of the persona depending on the real estate available on the user interface on the web page.

FIGS. 21B-21Nillustrate the same functionality provided in the interface2100on a phone device.

FIG. 21Bshows a personas menu2130which includes links to each of the defined personas for a given user. InFIG. 21Bthese are “default” friends, co-worker, family, girlfriend, and blocked caller. Selection of the options soft key menu gives rise to a menu shown inFIG. 21Callowing the user to open, create a new persona, edit a current persona, or delete a current persona. If a user selects to open a persona such as the default persona, the display shown inFIG. 21Dis shown. The display inFIG. 21Dshows that for a given “default” persona, the name of the persona is displayed, the associated image “F1 logo” is displayed, the ringtone “moonstar.mid” is displayed, the nickname associated with the persona is displayed and a work number and home number associated with the persona is displayed. Selection of the persona name by navigating to the name and selecting using a phone input selection mechanism results in the display shown inFIG. 21Eoffering the user a selection changing the soft keys to “ok” and “assign.” Selection of the assigned soft key results in the display shown inFIG. 21F, showing the users which have been assigned to this particular persona by the user. Current returning toFIG. 21C, selection of the “new” menu item results in a template shown inFIG. 21D. All the items in the template are blank, allowing the user to add via a soft menu selection button, the items for each of the entries depicted inFIG. 21D. The only menu entry which is pre-populated is the user's phone number as shown inFIG. 21G. Depressing the add name selection inFIG. 21Dresults in the display inFIG. 21H, allowing the user to enter via the phone's text entry method the name of the persona.FIG. 21Ishows at selection of the “multitap” soft key at the base of theFIG. 21Hallows the user several input methods for text such as multitap, numbers, T9 word entry, or symbols. Once the name has been specified inFIG. 21Hthe display ofFIG. 21Jillustrating the name of the persona is displayed.FIG. 21Kresults when the user has selected the add soft key inFIG. 21Jand the associated entry with a selection to add a graphic.FIG. 21Kdisplays those graphical or image entries which are “on the phone” and allows the user to select one of the displayed entries. If the user selects the “bird” entry the image that's displayed is shown inFIG. 21L. Likewise,FIG. 21Mdisplays a list of ringtones available for the user, andFIG. 21Mdisplays a user's availability to delete the ringtone.

FIG. 22is a graphical user interface displayed in web browser allowing the user to manage images in accordance with the present invention. Images available to the user are displayed in a column22/20, along with an associated nickname in column22/40, and an edit function hyperlink in column22/50. A default image for the user2110is displayed such that should the user create personas, the default image will be used. A upload interface2212including a browse selection button and a submit button2216are provided allowing the user to upload various images to their account. A premium downloads section2660offers the user links to value added service provider content to be downloaded and utilized by the user in accordance with the terms of the value added service provider.

FIG. 23illustrates an interface for managing ringtones in accordance with the present invention which provided in a user-interface and web browser by the web server180. A My Ringtones window2310includes a list of ringtones2320which have been uploaded or are available to the user via their account. The name of the ringtone is displayed in column2320, the artist in column2330and a preview in hyperlink2340. Likewise, default ringtone for the user is displayed at2312and an upload interface provided as in a manner somewhere to the image upload interface. Again, a value added download section2350can be provided to allow a digital content provider to provide value-added content downloadable by the user via this interface. An upload interface2314including a browse button2315and submit button2316allow a user to add to the ringtone selections for his account In a well known manner.

FIG. 24displays a My Details interface2400upon selection of link2400in bar1950ofFIG. 19. The interface2400allows the user to manage information associated with the user's account. A personal information section2412allows the user to input and change the user's first, middle and last name, as well as the user's nickname and detailed personal information, such as their birthday, anniversary and spouse's name. A home information and business information section2420and2430allow the user to specify a number of contact points and contact numbers for the user which are then used to allow the user to create personas in accordance with the foregoing description.

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 inFIG. 3may be present.FIG. 25is block diagram illustrating how the integration between a number of users and the synchronization server2550implemented in accordance with U.S. Pat. No. 6,671,757, 6,694,336 or 6,757,696 as used in to the present invention. An advanced ID management server2510may comprise a server160or a sub-set of the elements of server160, but including at least a management application170and a user info store2520to a persona database2520containing subscriber records2522. The synchronization server2550is provided with sync account records2524,2528,2530for a number of buddies of a subscriber100-1. Synch server2550communicates the synchronization mechanism disclosed in U.S. Pat. No. 6,671,757, 6,694,336 or 6,757,696 with buddy users100-3,100-4, and100-5. Rather than directly communicating changes via a download and upload of data, the transaction data packages as disclosed in U.S. Pat. No. 6,671,757, 6,694,336 or 6,757,696 communicate persona information by distributing changed logs to the client100-3-100-5. The user communicates with the system server2510via the phone interface or web interfaces as previously described.

FIG. 26is a block diagram depicting a more detailed alternative configuration of a sync server system, advanced ID server and client system for implementing the present invention. InFIG. 2, the server system is depicted as a stand-alone device communicating with a client such as a phone100. InFIG. 26a phone100-6is depicted as including an application client140as well as synchronization client2610, such as that described with respect to U.S. Pat. No. 6,671,757. An advanced ID system server2640includes a database510having a user content records2646, which include personas stored for subscribers as previously described. Server2640also includes a web server2660providing the web based interface screens disclosed in the foregoing figures. A client listener engine2650communicates with the client application2675to allow the user to input changes directly to the server side of the system2640. A change log adapter engine2640allows communication of changes to and from the synchronization server2650. A synchronization server2620is also provided. The synchronization server communicates with the synchronization client2610via a SyncMO server2626and with the Advanced ID server2640via a data protocol adapter2628. A management server2622as described in U.S. Pat. No. 6,671,757 communicates with a synchronization engine2624to control synchronization data packages stored in data store2632. The system allows the user's information to be stored across any number of multiple devices, and allows users having accounts with the synchronization server to have their information incorporated into the subscriber's advanced ID system. Each user account with the advanced ID service in the present invention requires the creation of corresponding synchronization account of the user. The synchronization account is used to synchronize the user's contents between the device and the system server2640. The system server2640modifies the appropriate contact in the user's persona and information.

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 engine2640, advanced ID engine2642collects 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 server2650contacts the system server2640, the system server tracks which persona a given buddy is assigned to by adding a field to the contact record. Device100-6incorporates a device sync client2610which syncs with the device's address book with change logs provided by the synchronization server2650. Both the native database150and the application ID database2602may be used to store records for the advanced ID system in accordance with the present invention.

FIG. 27depicts a client side application including a number of subsystems. A client2700includes user interface2710, an SMS listener2712, integrated call management2714, an entity manager2716, a application database2718, a synchronization layer2720, (if utilized with the technology of U.S. Pat. No. 6,671,757, a settings manager2722, and an application settings data store2724. Client2700includes a user interface which displays the interface screens of the present invention as previously described. In various configurations, portions of the phone's native address book150and an application specific, secondary data store2718store advanced ID information on the device. As noted above, when a subscriber contacts phone100-6, the application2700accepts the inbound call and depending on the robustness of the supported device and displays a custom user interface, including for example, the full screen image overlay with meta data, or a video clip. Integrated call management2714allows the user a variety of options to dispense with the call, such as answering, sending it to voice mail, or blocking the call to automatically populate the address book with the caller's public information. The entity manager maintains persona and buddy information on the client itself, as discussed below. The Sync layer2720supports synchronization with a sync server such as that described in U.S. Pat. No. 6,671,757. The settings manager2722maintains the user's preferences with respect to the application (such as application defaults and when the user may not want to be disturbed), which are stored in application settings store2724.

FIG. 28is a static illustration of the fundamental client objects utilized in the client database2718alone or in conjunction with a native database150. As shown inFIG. 28, for each instance2810of content information for a user, the instance may include email information2812, phone number information2814, address information2816and other content information2822such as a local ID2822and global ID. Each contact instance2810is associated with a persona2820and each persona identified by an identifier associated with the user. Buddy records2830include a buddy identifier, an assigned persona, what type of buddy they are (link type) and a filed indicating when the buddy information was last updated. Likewise, the e-mail information includes e-mail type enumeration2824, phone number information2814includes phone number enumerations2826, address information2816includes address enumerations2832(for work or home addresses), and content information2822includes for digital content, whether it is free or licensed information2834.

FIG. 29is a depiction of the entity manager2716shown inFIG. 27. Personas and buddies are collectively referred to as entities and are handled by the entity manager2900. As noted above, very few available devices support sufficiently robust address book data required for the implementation of the system in the present invention. To support the new data types required for this system, extended database2718depicted inFIG. 27may be required. Entity manager2900controls the use of these two data stores. Due to the peculiarities at the particular platform in question, entity manager2900serializes the buddy and persona objections from the system address book and its additional databases. Entity manager2900gathers the serialization code in a central place and allows expansion of the data set to include additional fields. Entity manager2900manager creates a serialized a buddy and persona records2830,2820, respectively and uses the system address book, the user interface2710and business logic, which is then created by the user at2912.

FIGS. 30,31,32,33, and34illustrate alternative configurations for the client shown inFIG. 27. An optimal configuration3002is shown inFIG. 30wherein a native robust address book3010, a robust SyncML client3020, and a robust synchronization server3030are provided. In this configuration, there may be very little for the client application3002to do, other than managing multimedia content presenting user interface. Most of the management and push of persona information occurs on the server3030.

Since most current clients do not include native robust address books and SyncML clients,FIG. 21presents an alternative configuration allowing a client3102to communicate with an advanced ID server160. The server160communicates with client3102via a shared communications protocol as shown inFIG. 31. Client3102includes a protocol engine3110being an address book proxy3120and utilizes both the limited native address book150and supporting database2718. An address book proxy3120(such as entity manager2900or some other form of proxy mechanism) manages communications and storage of information between the respective stores2718and150.

Yet another alternative configuration is shown inFIG. 32. InFIG. 32, a robust SyncML server communicates with a robust SyncML client3020, but utilizes an address book proxy3120to split information between the database2718and address book150.

InFIG. 33, a limited SyncML server provides support for some synchronization information required for the persona, but not all the necessary information required. Likewise the phone's SyncML client may only support limited synchronization or field support. For example, the server160may support address and phone number synchronization but not downloading of movies and ringtones. In this embodiment, server3310cooperates with the systems server160to communicate certain information via a limited SyncML client3130, while other information is communicated directly to phone's proxy3312. Multimedia information can be provided via the support applications3310and3130, while more basic information is provided to proxy3312. An address book proxy3120to split information between the database2718and address book150.

InFIG. 34, the client is equivalent toFIG. 33except that information is stored in a robust native address book3402.

FIG. 35illustrates a Media manager3505and the records associated with a piece of media information. The system supports digital rights media management. The MediaManger object provides an interface to the other client components which allows media uploading, media downloading, and retrieval of media information. Since each device has different capabilities, transcoding media objects from their original format is often required in order to support them on different devices. Transcoding refers to a process by which media in one format on one type of device or phone can be made available to other types of phones. For example, if a first user's phone creates pictures in JPG format, but a receiving user's phone only supports GIF, the system server can automatically convert the format of the image based on the server's knowledge of the receiving user's phone. This same process may be used to change the resolution of an image to fit properly on the target device's display, given its characteristics.

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).

FIG. 35illustrates the digital rights media record format utilized in the client application and present invention. Media manager3505determines whether or not the information in any media utilized in the device, whether a jpeg, mp3 movie, or the like. This determines first determining whether the media is a locally implemented piece of media or media from a value added provider. The media manager maintains records of the media location, whether it is downloadable or up-loadable and the like.

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 record3510which contains a media record type (local or nor) and identifier, size, hash value, a formula identifier, and a location. The media format3512can be any of an image format3514, a ringer format3516, a video format3518. The image format type includes jpegs, pngs and gifs, as indicated at3520. 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.