Translation of information between database formats understood by different user equipment components for download of the information from network storage component

TECHNICAL FIELD

[0001] The invention relates generally to information storage and more particularly to network based data backup.

BACKGROUND

[0002] Mobile telephones, personal digital assistants (“PDAs”), and personal computers comprise examples of equipment that users employ to communicate, store, and retrieve information. The user equipment comprises an internal database. The user stores in the internal database personal information, for example, telephone numbers, contact information, and buddy lists. As one shortcoming, if the user equipment breaks or is lost, then the user loses that record of the personal information. As another shortcoming, if the user equipment requires replacement, then to avoid loss of the record of the personal information the user must manually reenter the personal information into an internal database of replacement user equipment.

[0003] The user equipment may upload/download information to/from a network based storage device. The network based storage device allows the user equipment to transmit information for storage on a remote network via wireless communication. The network based storage device is able to transfer the information in a single format, between user equipment of a single manufacturer, and within the coverage of a single service provider. However, the network based storage device is unable to transfer the information between different formats, different user equipment manufacturers, and different service providers.

[0004] As one shortcoming, the user equipment of a first format, manufacturer, or service provider cannot transfer information through the network based storage device to user equipment of a second format, manufacturer, or service provider that is incompatible with the first format, manufacturer, or service provider.

[0005] Thus, a need exists for enhanced database format handling for user equipment information employed with a network based storage device. A further need exists for enhanced storage and retrieval of user equipment information on a network based storage device.

SUMMARY

[0006] The invention in one embodiment encompasses a method. Information that is based on a database portion of a first user equipment component is translated from a first database format to a second database format for a download of the information from a network storage component to a second user equipment component. The first database format is understood by the first user equipment component. The second database format is understood by the second user equipment component. The first database format is not understood by the second user equipment component.

[0007] Another embodiment of the invention encompasses an apparatus. The apparatus comprises a network storage component and a translation component. The network storage component stores information that is based on one or more database portions of one or more user equipment components. The one or more user equipment components comprise a first user equipment component and a second user equipment component. The translation component communicatively couples the network storage component with one or more of the one or more database portions of the one or more user equipment components. The one or more database portions of the one or more user equipment components comprise a database portion of the first user equipment component. The information that is based on the one or more database portions of the one or more user equipment components comprises first information that is based on the database portion of the first user equipment component. The translation component converts the first information from a first database format to a second database format for a download of the first information from the network storage component to the second user equipment component. The first database format is understood by the first user equipment component. The second database format is understood by the second user equipment component. The first database format is not understood by the second user equipment component.

[0008] Yet another embodiment of the invention encompasses an article. The article comprises one or more computer-readable signal-bearing media. The article includes means in the one or more media for translating information that is based on a database portion of a first user equipment component from a first database format to a second database format for a download of the information from a network storage component to a second user equipment component. The first database format is understood by the first user equipment component. The second database format is understood by the second user equipment component. The first database format is not understood by the second user equipment component.

DESCRIPTION OF THE DRAWINGS

[0009] Features of exemplary implementations of the invention will become apparent from the description, the claims, and the accompanying drawings in which:

[0010]FIG. 1 is a representation of an exemplary implementation of an apparatus that comprises one or more application servers, one or more network storage components, one or more data nodes, one or more user profile databases, one or more networks, and one or more user equipment components.

[0011]FIG. 2 is a representation of one exemplary message flow between one of the application servers and one of the user equipment components of the apparatus of FIG. 1, illustrating a manually initiated upload of information based on a database portion of the user equipment component to one of the network storage components.

[0012]FIG. 3 is a representation of another exemplary message flow between one of the application servers and one of the user equipment components of the apparatus of FIG. 1, illustrating an automatically initiated upload of information based on a database portion of the user equipment component to one of the network storage components.

[0013]FIG. 4 is a representation of yet another exemplary message flow between one of the application servers and one of the user equipment components of the apparatus of FIG. 1, illustrating a download of information based on a database portion of one of the user equipment components from one of the network storage components.

DETAILED DESCRIPTION

[0014] Turning to FIG. 1, an apparatus <b>100</b> in one example comprises a plurality of components such as computer software and/or hardware components. A number of such components can be combined or divided in the apparatus <b>100</b>. An exemplary component of the apparatus <b>100</b> employs and/or comprises a set and/or series of computer instructions written in or implemented with any of a number of programming languages, as will be appreciated by those skilled in the art.

[0015] The apparatus <b>100</b> in one example comprises one or more networks <b>110</b> and one or more user equipment components <b>112</b> and/or <b>114</b>. The user equipment components <b>112</b> and <b>114</b> in one example are operable by one or more users. The users of the user equipment components <b>112</b> and <b>114</b> in one example comprise human operators.

[0016] The network <b>110</b> in one example provides a database backup service for one or more of the user equipment components <b>112</b> and <b>114</b>. The user equipment components <b>112</b> and <b>114</b> comprise respective internal databases stored in respective instances of a recordable data storage medium <b>101</b>, as described herein. The database backup service of the network <b>110</b> in one example allows the user equipment component <b>112</b> to upload a portion of the internal database of the user equipment component <b>112</b> to a network storage component <b>104</b>. The portion of the internal database comprises all or one or more subportions of the internal database of the user equipment component <b>112</b>. The internal database of the user equipment component <b>112</b> stores personal information (e.g., phone books, address books, buddy lists, presence lists, birthday lists, and internet bookmarks) of a user of the user equipment component <b>112</b>.

[0017] In another example, the database backup service of the network <b>110</b> allows a user to employ the user equipment component <b>114</b> to download the portion of the internal database from the network storage component <b>104</b>. The user equipment component <b>114</b> may populate a portion of the internal database of the user equipment component <b>114</b> with the portion of the internal database downloaded from the network storage component <b>104</b>. The user equipment component <b>114</b> populates the portion of the internal database of the user equipment component <b>114</b> by storing the portion of the internal database downloaded from the network storage component <b>104</b> in the portion of the internal database of the user equipment component <b>114</b>.

[0018] The network <b>110</b> in one example comprises one or more application servers <b>102</b>, one or more network storage components <b>104</b>, one or more data nodes <b>106</b>, and one or more user profile databases <b>108</b>. In one example, the application server <b>102</b>, the network storage component <b>104</b>, the data node <b>106</b>, and the user profile database <b>108</b> comprise one or more of computer software, computer hardware, and/or telecommunications network components. The network <b>110</b> in one example serves to provide a medium to transmit messages between the application server <b>102</b>, the network storage component <b>104</b>, the data node <b>106</b>, the user profile database <b>108</b>, and the user equipment components <b>112</b> and <b>114</b>.

[0019] The application server <b>102</b> in one example communicatively couples the network storage component <b>104</b> with the user equipment components <b>112</b> and <b>114</b>. For example, the application server <b>102</b> processes and forwards messages between the network storage component <b>104</b> and the user equipment components <b>112</b> and <b>114</b> to communicatively couple the network storage component <b>104</b> with the user equipment components <b>112</b> and <b>114</b>. The application server <b>102</b> comprises a distributor component and/or a translator component, for example, located in an instance of the recordable data storage medium <b>101</b>.

[0020] In one example, the application server <b>102</b> comprises a distributor component that controls storage and retrieval of information with respect to the network storage component <b>104</b>. For example, the application server <b>102</b> may communicate information from the user equipment component <b>112</b> to the network storage component <b>104</b>. The application server <b>102</b> may also communicate the information from the network storage component <b>104</b> to the user equipment component <b>114</b>.

[0021] In a further example, the application server <b>102</b> comprises a translator component that converts information from a database format (e.g., a first database language) of the user equipment component <b>112</b> to a database format (e.g., a second database language) of the user equipment component <b>114</b>. Exemplary situations exist where the application server <b>102</b> may make a conversion between the database format of the user equipment component <b>112</b> and the database format of the user equipment component <b>114</b>. For example, the user equipment components <b>112</b> and <b>114</b> may be made by different manufacturers that employ different database formats. In another example, the user equipment components <b>112</b> and <b>114</b> may be made by a same manufacturer but employ different database formats. In yet another example, the user equipment components <b>112</b> and <b>114</b> may be supported by different service providers. In still yet another example, the user equipment components <b>112</b> and <b>114</b> may employ different air interface technologies.

[0022] In one example, the network storage component <b>104</b> serves to store information forwarded from the application server <b>102</b> that is based on one or more portions of the internal database of one or more user equipment components (e.g., the user equipment components <b>112</b> and <b>114</b>). The information that is based on the one or more portions of the internal database in one example comprises a copy of the portion of the internal database of the user equipment component <b>112</b>. The information that is based on the one or more portions of the internal database in another example comprises a translation of the portion of the internal database of the user equipment component <b>112</b>.

[0023] The network storage component <b>104</b> comprises a database with one or more entries. The entries in one example correspond to personal information of the internal databases of the user equipment components <b>112</b> and <b>114</b>. The entries store information that is representative of the phone books, the address books, the buddy lists, the presence lists, the birthday lists, and the internet bookmarks of the internal databases of the user equipment components <b>112</b> and <b>114</b>.

[0024] In one example, the network storage component <b>104</b> stores the one or more entries in one or more database formats. In one example, the network storage component <b>104</b> may store entries in one or more native database formats for one of the user equipment components <b>112</b> and <b>114</b>. In another example, the network storage component <b>104</b> may store entries in a universal database format common to the user equipment components <b>112</b> and <b>114</b>. In one example, the network storage component <b>104</b> is integrated into the application server <b>102</b>. In another example, the network storage component <b>104</b> is integrated into the user profile database <b>108</b>. In yet another example, the network storage component <b>104</b> comprises a standalone database operating within the network <b>110</b>.

[0025] In one example, the data node <b>106</b> serves to receive, process, and/or forward messages between the application server component <b>102</b> and the user equipment components <b>112</b> and <b>114</b>. In a further example, the data node <b>106</b> checks the user profile from the user profile database <b>108</b> of the user equipment components <b>112</b> and <b>114</b> for an indication of a subscription to the database backup service. The data node <b>106</b> comprises one or more of a Serving General Packet Radio Service (“GPRS”) Support Node (“SGSN”), a Gateway GPRS Support Node (“GGSN”), a Packet Data Serving Node (“PDSN”), a short message service center (“SMSC”), and a call state control function (“CSCF”) component.

[0026] The data node <b>106</b> queries the user profile database <b>108</b> to retrieve stored user profiles of the user equipment components <b>112</b> and <b>114</b>. The user profile database <b>108</b> comprises a home location register (“HLR”). The user profile database <b>108</b> processes one or more user profile query messages from the data node <b>106</b>. Upon receipt of one of the user profile query messages from the data node <b>106</b>, the user profile database <b>108</b> returns the user profile which corresponds to the user equipment components <b>112</b> and <b>114</b> requested by the data node <b>106</b>. For example, the user profile database <b>108</b> sends the user profile of the user equipment component <b>112</b> to the data node <b>106</b>. The user profile indicates to the data node <b>106</b> whether the user equipment component <b>112</b> subscribes to the database backup service and therefore whether the user equipment component <b>112</b> may employ the database backup service. The user profile comprises information regarding services available to the user, for example, database backup service subscription information, permissions, conference call services, voice mail, and/or data and voice communications.

[0027] The user equipment components <b>112</b> and <b>114</b> in one example serve to initiate an upload or a download of information with the network storage component <b>104</b>. The user equipment components <b>112</b> and <b>114</b> communicate via the network <b>110</b>. For example, the user equipment components <b>112</b> and <b>114</b> engage in mobile telephone communication, for example, calls, voice mail, and short messaging services (“SMS”), via the network <b>110</b>. The user equipment components <b>112</b> and <b>114</b> in one example comprise one or more of handheld devices, mobile telephones, cellular phones, mobile computers, personal digital assistants (“PDAs”), and personal computers.

[0028] In one example, the user equipment components <b>112</b> and <b>114</b> comprise respective translator components stored in respective instances of the recordable data storage medium <b>101</b>. The translator component of the user equipment component <b>112</b> and/or <b>114</b> translates information from a native database format for that user equipment component <b>112</b> and/or <b>114</b> to the universal database format for storage in the network storage component <b>104</b>.

[0029] The user of the user equipment component <b>112</b> in one example employs a user interface of the user equipment component <b>112</b> to initiate a call to the user equipment component <b>114</b>. In another example, the user of the user equipment component <b>112</b> employs the user interface to initiate an upload of the information stored in the internal database of the user equipment component <b>112</b> to the network storage component <b>104</b>. To initiate the upload, the user of the user equipment component <b>112</b> in one example activates a backup database function of the user interface. In yet another example, the user of the user equipment component <b>112</b> employs the user interface to initiate a download of the information from the network storage component <b>104</b>. To initiate the download, the user of the user equipment component <b>112</b> in one example activates a retrieve database function of the user interface.

[0030] An illustrative description of exemplary operation of the apparatus <b>100</b> is presented, for explanatory purposes. The user equipment component <b>112</b> uploads information that is based on a portion of the internal database of the user equipment component <b>112</b> to the application server <b>102</b> for storage in the network storage component <b>104</b>. For example, the portion of the internal database comprises a representation of the phone book and the address book of the internal database of the user equipment component <b>112</b>. The application server <b>102</b> may serve as an information translator and/or an information distributor. In one example, the application server <b>102</b> translates the information from a first database format to a second database format before storage in the network storage component <b>104</b>. In another example, the application server <b>102</b> distributes the information without change to the network storage component <b>104</b>. The network storage component <b>104</b> stores the information and awaits a request for retrieval of the information.

[0031] Either of the user equipment components <b>112</b> and <b>114</b> may download the information that is based on the portion of the internal database from the network storage component <b>104</b>. For example, the user equipment component <b>114</b> sends the request for retrieval to the network <b>110</b> to download the information from the network storage component <b>104</b>. The application server <b>102</b> accesses the information from the network storage component <b>104</b>. The application server <b>102</b> determines from the user profile of the user equipment component <b>114</b> a database format that is understood by the user equipment component <b>114</b>. For example, the database format that is understood by the user equipment component <b>114</b> is a database format that the user equipment component <b>114</b> employs or is a database format that the user equipment component <b>114</b> can translate to the database format that the user equipment component <b>114</b> employs.

[0032] If a translation is necessary before the download, then the application server <b>102</b> translates the information to the database format that is understood by the user equipment component <b>114</b>. The application server <b>102</b> sends the information in the database format that is understood by the user equipment component <b>114</b> to the data node <b>106</b>. The data node <b>106</b> forwards the information to the user equipment component <b>114</b>. The user equipment component <b>114</b> populates a portion of the internal database of the user equipment component <b>114</b> with the information. For example, after the population of the internal database of the user equipment component <b>114</b>, the phone book and the address book of the internal database of the user equipment component <b>114</b> comprise a representation of the phone book and the address book of the internal database of the user equipment component <b>112</b>.

[0033] Exemplary situations exist that may motivate the user equipment component <b>114</b> to populate the portion of the internal database of the user equipment component <b>114</b> with the information of the internal database of the user equipment component <b>112</b>. In one example, a user of the user equipment component <b>112</b> wishes to employ a different user equipment component (e.g., the user equipment component <b>114</b>). For example, the user wants to upgrade to a new user equipment component, the user equipment component <b>112</b> is lost, stolen, or broken, or the user changes to a service provider that is not compatible with the user equipment component <b>112</b>.

[0034] The user at one time programmed the internal database of the user equipment component <b>112</b> to store the phone book and the address book. Therefore, when the user begins employment of the user equipment component <b>114</b>, the user wants the internal database of the user equipment component <b>114</b> to store the phone book and the address book previously stored in the user equipment component <b>112</b>. However, the user does not want to program the internal database of the user equipment component <b>114</b> to store the phone book and the address book. Therefore, the user employs the database backup service to populate the internal database of the user equipment component <b>114</b> to store the phone book and the address book of the user equipment component <b>112</b> in the user equipment component <b>114</b>.

[0035] Turning to FIG. 2, a message flow <b>201</b> represents an exemplary registration of the user equipment component <b>112</b> and an exemplary upload of information that is based on a portion of the internal database of the user equipment component <b>112</b> from the user equipment component <b>112</b> to the network storage component <b>104</b>. The message flow <b>201</b> illustrates one example of the user of the user equipment component <b>112</b> manually initiating the upload of the information.

[0036] To register the user equipment component <b>112</b> with the network <b>110</b> (FIG. 1), the user equipment component <b>112</b> sends a registration message <b>202</b> to the data node <b>106</b>. “REGISTRATION” in one example serves to represent the registration message <b>202</b>. Upon receipt of the registration message <b>202</b>, the data node <b>106</b> sends a query message <b>204</b> to the user profile database <b>108</b>. “QUERY (USER)” in one example serves to represent the query message <b>206</b>. “USER” in one example serves to represent an indication of the user equipment component <b>112</b>. The query message <b>206</b> initiates a download of the user profile of the user equipment component <b>112</b> from the user profile database <b>108</b>.

[0037] Upon receipt of the query message <b>206</b>, the user profile database <b>108</b> in one example sends a response message <b>206</b> to the data node <b>106</b>. “RESPOND (PROFILE)” in one example serves to represent the response message <b>206</b>. “PROFILE” in one example serves to represent an indication of the user profile of the user equipment component <b>112</b>. The user profile of the user equipment component <b>112</b> in one example comprises database backup service information of the user equipment component <b>112</b>, for example, whether the user equipment component <b>112</b> subscribes to the database backup service.

[0038] To begin the upload of the information to the network storage component <b>104</b>, the user equipment component <b>112</b> sends an upload initiation message <b>208</b> to the data node <b>106</b>. “DB UPLOAD REQUEST (DATA)” in one example serves to represent the upload initiation message <b>208</b>. “DATA” in one example serves to represent the information for upload to the network storage component <b>104</b>. The “DATA” of the upload initiation message <b>208</b> in one example comprises the entire contents of the information that is based on the portion of the internal database. The “DATA” of the upload initiation message <b>208</b> in another example comprises a portion of the entire contents of the information that is based on the portion of the internal database (e.g., a first block of data). The “DATA” of the upload initiation message <b>208</b> in yet another example comprises a header that comprises an indication of the size of the information that is based on the portion of the internal database. The “DATA” of the upload initiation message <b>208</b> in still yet another example is empty.

[0039] Upon receipt of the upload initiation message <b>208</b>, the data node <b>106</b> checks the user profile of the user equipment component <b>112</b> for an indication of a subscription to the database backup service. If the user equipment component <b>112</b> subscribes to the database backup service, then the data node <b>106</b> sends an upload data message <b>210</b> to the application server <b>102</b>. “UPLOAD DATA (USER, DATA)” in one example serves to represent the upload data message <b>210</b>. “USER” the in one example serves to represent an indication of the user equipment component <b>112</b>. “DATA” in one example serves to represent the information that corresponds to the “DATA” of the upload initiation message <b>208</b>. Upon receipt of the upload data message <b>210</b>, the application server <b>102</b> sends an acknowledgement message <b>212</b> to the data node <b>106</b>. The acknowledgement message <b>212</b> indicates to the data node <b>106</b> that the application server <b>102</b> is ready for any additional data in connection with the “DATA” of the upload data message <b>210</b>.

[0040] Upon receipt of the acknowledgement message <b>212</b>, the data node <b>106</b> initiates an upload conversation <b>214</b> between the user equipment component <b>112</b> and the application server <b>102</b>. “DB UPLOAD CONVERSATION (DATA)” in one example serves to represent the upload conversation <b>214</b>. “DATA” in one example serves to represent the additional data in connection with the “DATA” of the upload data message <b>210</b>. The upload conversation <b>214</b> between the user equipment component <b>112</b> and the application server <b>102</b> physically passes through the data node <b>106</b>. For example, the upload conversation <b>214</b> comprises one or more individual messages sent from the user equipment component <b>112</b> to the data node <b>106</b> and then forwarded to the application server <b>102</b>. The one or more individual messages comprise one or more blocks of the entire contents of the information for upload to the network storage component <b>104</b>.

[0041] In one example, the application server <b>102</b> sends the information to the network storage component <b>104</b> for storage in the network storage component <b>104</b> in the database format (e.g., database language) of the user equipment component <b>112</b>. In another example, the application server <b>102</b> translates the information to a database format common to the user equipment components <b>112</b> and <b>114</b> for storage in the network storage component <b>104</b>. In a further example, the application server <b>102</b> translates the information to the universal database format common to the user equipment components <b>112</b> and <b>114</b> (e.g., all user equipment components) for storage in the network storage component <b>104</b>.

[0042] The application server <b>102</b> sends the information to the network storage component <b>104</b> during storage conversation <b>216</b>. “STORE (DATA)” in one example serves to represent the storage conversation <b>216</b>. Upon completion of the upload conversation <b>214</b> and the storage conversation <b>216</b>, the upload is ended with termination message <b>218</b>.

[0043] Turning to FIG. 3, a message flow <b>301</b> represents an exemplary registration of the user equipment component <b>112</b> and an exemplary upload of information that is based on a portion of the internal database of the user equipment component <b>112</b> from the user equipment component <b>112</b> to the network storage component <b>104</b>. The message flow <b>301</b> illustrates one example of the upload of the information automatically initiated at some predefined time or upon expiration of a predefined time interval. A provider of the database backup service may set the time and/or time interval (e.g., automatically initiated on a weekly basis).

[0044] The registration of the user equipment component <b>112</b> with the network <b>110</b> (FIG. 1), the retrieval of the user profile from the user profile database <b>108</b>, and checking the user profile for the indication of the subscription to the database backup service are accomplished in the message flow <b>301</b> as described in the message flow <b>201</b>. The user profile of the user equipment component <b>112</b> in one example comprises automatic database backup service information of the user equipment component <b>112</b> (e.g., whether the user equipment component <b>112</b> subscribes to the automatic database backup service). In the message flow <b>301</b>, during the step of checking the user profile for the indication of the subscription to the database backup service, the data node <b>106</b> additionally checks for an indication whether the user equipment component <b>112</b> subscribes to the automatic upload feature of the database backup service.

[0045] In one example, at the predefined time or upon the expiration of the predefined time interval, the data node <b>106</b> initiates the automatic upload of the information to the network storage component <b>104</b>. The data node <b>106</b> sends an upload initiation message <b>302</b> to the application server <b>102</b>. “AUTO UPLOAD (USER)” in one example serves to represent the upload initiation message <b>302</b>. “USER” in one example serves to represent an indication of the user equipment component <b>112</b>.

[0046] In another example, the data node <b>106</b> sends an automatic upload message to the application server <b>102</b> (e.g., upon registration of the user equipment component <b>112</b>). Upon receipt of the automatic upload message, the application server <b>102</b> determines if the predefined time or upon the expiration of the predefined time interval has occurred. If the predefined time has been reached or if the time interval has expiration, then the data node <b>106</b> initiates upload conversation <b>214</b> between the user equipment component <b>112</b> and the application server <b>102</b> as described in the message flow <b>201</b>. The remainder of the upload is accomplished in the message flow <b>301</b> as described in the message flow <b>201</b>.

[0047] Turning to FIG. 4, a message flow <b>401</b> represents an exemplary registration of the user equipment component <b>114</b> and an exemplary download of the information that is based on the portion of the internal database of the user equipment component <b>112</b> from the network storage component <b>104</b> to the user equipment component <b>114</b>. The registration of the user equipment component <b>114</b> with the network <b>110</b> (FIG. 1), the retrieval of the user profile from the user profile database <b>108</b>, and checking the user profile for the indication of the subscription to the database backup service are accomplished in the message flow <b>401</b> as described in the message flow <b>201</b>.

[0048] To begin the download of the information from the network storage component <b>104</b>, the user equipment component <b>114</b> sends a download initiation message <b>402</b> to the data node <b>106</b>. “DB DOWNLOAD REQUEST (USER)” in one example serves to represent the download initiation message <b>402</b>. In one example, “USER” serves to represent an indication of the user equipment component <b>114</b>. In another example, “USER” serves to represent an indication of any other user equipment component (e.g., the user equipment component <b>112</b>) that has a portion of the internal database stored in the network storage component <b>104</b>. The download initiation message <b>402</b> requests the portion of the internal database that corresponds to the user equipment component indicated by “USER.”

[0049] Upon receipt of the download initiation message <b>402</b>, the data node <b>106</b> sends an download data message <b>404</b> to the application server <b>102</b>. “DOWNLOAD DATA (USER)” in one example serves to represent the download data message <b>404</b>. Upon receipt of the download data message <b>404</b>, the application server <b>102</b> sends an acknowledgement message <b>406</b> to the data node <b>106</b>. The application server <b>102</b> then begins a database retrieval conversation <b>408</b> with the network storage component <b>104</b> to retrieve the information that is based on the portion of the internal database of the user equipment component indicated by “USER.” “GET (USER, DATA)” in one example serves to represent the database retrieval conversation <b>408</b>. “DATA” in one example serves to represent the information that is based on the portion of the internal database of the user equipment component indicated by “USER.”

[0050] The application server <b>102</b> employs the user profile of the user equipment component <b>114</b> to determine which database format is understood by the user equipment component <b>114</b>, for example, a native database format for the user equipment component <b>114</b>. The application server <b>102</b> translates the information that is based on the portion of the internal database of the user equipment component indicated by “USER” to the database format that is understood by the user equipment component <b>114</b>. For example, the application server <b>102</b> generates a database in the database format that is understood by the user equipment component <b>114</b> based on the information of the portion of the internal database of the user equipment component indicated by “USER.” In another example, the user equipment component <b>114</b> translates the information based on the portion of the internal database of the user equipment component indicated by “USER” to the database format that is understood by the user equipment component <b>114</b>.

[0051] Once the application server <b>102</b> translates the information, then the application server <b>102</b> begins a download conversation <b>410</b> with the user equipment component <b>114</b>. “DB DOWNLOAD CONVERSATION (DATA)” in one example serves to represent the download conversation <b>410</b>. “DATA” in one example serves to represent the information in the database format that is understood by the user equipment component <b>114</b>. The download conversation <b>410</b> between the user equipment component <b>114</b> and the application server <b>102</b> physically passes through the data node <b>106</b>. For example, the download conversation <b>410</b> comprises one or more individual messages sent from the application server <b>102</b> to the data node <b>106</b> and then forwarded to the user equipment component <b>114</b>. The one or more individual messages comprise one or more blocks of the entire contents of the information in the database format that is understood by the user equipment component <b>114</b> for download to the user equipment component <b>114</b>. Upon completion of the download conversation <b>410</b>, the download is ended with termination message <b>412</b>.

[0052] The apparatus <b>100</b> in one example employs one or more computer-readable signal-bearing media. Examples of a computer-readable signal-bearing medium for the apparatus <b>100</b> comprise the recordable data storage medium <b>101</b> of the application server <b>102</b>, the recordable data storage medium <b>101</b> of the user equipment component <b>112</b>, and the recordable data storage medium <b>101</b> of the user equipment component <b>114</b>. For example, the computer-readable signal-bearing medium for the apparatus <b>100</b> comprises one or more of a magnetic, electrical, optical, biological, and atomic data storage medium. In one example, the computer-readable signal-bearing medium comprises a modulated carrier signal transmitted over a network comprising or coupled with the apparatus <b>100</b>, for instance, one or more of a telephone network, a local area network (“LAN”), the internet, and a wireless network.

[0053] The steps or operations described herein are just exemplary. There may be many variations to these steps or operations without departing from the spirit of the invention. For instance, the steps may be performed in a differing order, or steps may be added, deleted, or modified.

[0054] Although exemplary implementations of the invention have been depicted and described in detail herein, it will be apparent to those skilled in the relevant art that various modifications, additions, substitutions, and the like can be made without departing from the spirit of the invention and these are therefore considered to be within the scope of the invention as defined in the following claims.