CN101247589B - Mobile terminal data conversion/backup method, device and system - Google Patents
Mobile terminal data conversion/backup method, device and system Download PDFInfo
- Publication number
- CN101247589B CN101247589B CN2007101229751A CN200710122975A CN101247589B CN 101247589 B CN101247589 B CN 101247589B CN 2007101229751 A CN2007101229751 A CN 2007101229751A CN 200710122975 A CN200710122975 A CN 200710122975A CN 101247589 B CN101247589 B CN 101247589B
- Authority
- CN
- China
- Prior art keywords
- data
- mobile terminal
- terminal device
- intermediate file
- specified entry
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Abstract
The invention relates to the data transmission technique, in particular to the data transmission technique between mobile terminal device and the data copy technique of mobile terminal device. The embodiment of the invention provides technical plan which converts initial data to intermediate file with prescribed format by using a format conversion unit; the intermediate file wit prescribed format comprises specified entry of initial data and corresponding data field; according to the prescribed format of intermediate file, the format conversion unit can read data filed form the intermediate file, so as to produce target data corresponding to the initial data; since the intermediate file with prescribed format comprises the specified entry which is the shared information field stored on various mobile terminal devices, the intermediate file can be transmitted between various mobile terminal devices, so as to accomplish data transmission; and, the intermediate file can be viewed as copy file of the initial data, so as to enhance reliability of the initial data.
Description
Technical field
The present invention relates to data transmission technology, particularly the data backup technology of data conversion technique between the mobile terminal device and mobile terminal device.
Background technology
Transfer of data between the mobile terminal device is meant that mainly the initial data of storage in the middle of the mobile terminal device will transfer in the middle of the other mobile terminal device, the original data type of transmission comprises: phone directory, schedule, SMS (Short Message Service, short message) record, MMS (MultimeidaMessage Services, Multimedia Message) record or mail (Email) record etc.
Mobile terminal device at present commonly used is generally phone, realize data transmission manner mainly be phone to server (Phone To Server), perhaps phone is to the mode of phone (Phone To Phone).The mode of PhoneTo Server just is meant the mode of phone by data link, with the mode of mobile terminal device canned data according to the server defined, utilizes special host-host protocol to send to server, and stores on server.When mobile terminal device need transmit these data, also utilize this communication mode of mobile terminal device and server to finish the transmission work of data, this mode can conveniently realize the backup of phone data file on server.Certainly can also transfer data to phone to the mode of phone (Server ToPhone) by server, thereby reach the purpose of transmission data between phone.
The mode of Phone To Phone generally is meant the local concatenation ability of utilizing mobile terminal device, as infrared or bluetooth data is transmitted between different mobile terminal devices.In general, the mobile terminal device that this mode only is only applicable to same mobile terminal device manufacturer perhaps carries out the transmission of data between the mobile terminal device of same model.
The implementation method of transfer of data is primarily aimed at the phone directory data file now, the phone directory data file comprises Vcard (ecommerce card) and Vcalendar (ecommerce schedule), IMC (Internet MailConsortium) has stipulated that the uniform data form of Vcard and Vcalendar is used for storing user's telephone directory information and calendar information, wherein comprise the plurality of data field, the all corresponding again clauses and subclauses of each data field, for example the clauses and subclauses that comprise among the Vcard have: name, address, Mobile Directory Number, fixed telephone number etc.
Mobile terminal device is according to IMC specified standard version and form, the related data of corresponding Vcard of storage and uniform and Vcalendar, in the middle of the process of the transmission of carrying out data, only the Vcard and the directly transmission between different mobile terminal devices of Vcalendar data of this machine inside just can need be reached the function that different mobile terminal devices is discerned these data.
But because the difference of mobile terminal device disposal ability, format conversion unit hardware system structure, the storage mode of message datas such as SMS, the MMS on the existing mobile terminal device, Email is different, can't utilize the transmission means of similar phone directory data to realize the transmission of data such as SMS, MMS, Email between the mobile terminal device.
To sum up, the prerequisite of carrying out transfer of data between the existing mobile terminal device is two mobile terminal device internal support uniform data format, and the data of oneself are organized according to so a kind of form.After finishing the tissue of local data, if need to carry out the transmission of data file between the mobile terminal device, can finish the transmission course of data so by the mode of Phone To Phone or Phone To Server and Server To Phone.
In fact, the operating system of each producer's mobile terminal device and the realization of bottom all are relative closures and independently, each producer is for separately data format, and the transmission of data format all has the regulation of oneself, so just caused between the various mobile terminal devices that different manufacturers produces in addition different model mobile terminal device that same producer generates between the difficulty of transfer of data.
Summary of the invention
The embodiment of the invention provides a kind of data transfer device, equipment and system of mobile terminal device, is used to realize the transfer of data between the mobile terminal device.
The embodiment of the invention also provides a kind of data back up method, equipment and system of mobile terminal device, is used to realize the data backup on the mobile terminal device.
The conversion method of a kind of mobile terminal device data that the embodiment of the invention provides comprises:
Generate the intermediate file of form up to specification, the data field that comprises at least one specified entry and each specified entry correspondence in the described intermediate file, the data field of described each specified entry correspondence are to obtain from the initial data that first mobile terminal device is preserved;
According to the prescribed form of described intermediate file, from described intermediate file, obtain the data field of each specified entry correspondence, and the data field of each specified entry correspondence is saved as target data according to the form of the second mobile terminal device support.
The converting system of a kind of mobile terminal device data that the embodiment of the invention provides comprises:
First format conversion unit, be used to generate the intermediate file of form up to specification, the data field that comprises specified entry and each specified entry correspondence in the described intermediate file, the data field of described each specified entry correspondence are to obtain from the initial data that first mobile terminal device is preserved;
Second format conversion unit, be used for prescribed form according to the intermediate file of described first format conversion unit generation, from described intermediate file, obtain the data field of each specified entry correspondence, and the data field of each specified entry correspondence is saved as target data according to the form of the second mobile terminal device support.
A kind of mobile terminal device that the embodiment of the invention provides comprises:
The transfer instruction receiving element is used to receive data transfer instruction;
Original data storage unit, the first storage control unit and first format conversion unit, the original data transmissions instruction that described first format conversion unit receives according to the transfer instruction receiving element, from the original data storage unit, obtain the data field of specified entry correspondence by the described first storage control unit, and generate the intermediate file of form up to specification, comprise the data field of specified entry and each specified entry correspondence in the described intermediate file;
The intermediate file transmitting element is used for described intermediate file is sent to other mobile terminal device.
A kind of mobile terminal device that the embodiment of the invention provides comprises:
The intermediate file receiving element, be used to receive the intermediate file that other mobile terminal device sends, the data field that comprises specified entry and each specified entry correspondence in the described intermediate file, the data field of described each specified entry correspondence are to obtain from the initial data that described other mobile terminal device is preserved;
Second format conversion unit, the second storage control unit and target data memory cell, described second format conversion unit is obtained the data field of each specified entry correspondence from the intermediate file that middle file receiving element receives, and by the form of the described second storage control unit according to the mobile terminal device support, the data field with each specified entry correspondence in described target data memory cell saves as target data.
The backup method of a kind of mobile terminal device data that the embodiment of the invention provides comprises:
From the initial data that mobile terminal device is preserved, obtain the data field of specified entry correspondence;
Generate the intermediate file of form up to specification, comprise the data field of specified entry and each specified entry correspondence in the described intermediate file;
Described intermediate file is saved as the backup file of corresponding described initial data.
The data backup system of a kind of mobile terminal device that the embodiment of the invention provides comprises:
The storage control unit and first format conversion unit, described first format conversion unit is obtained the data field of specified entry correspondence from the initial data of mobile terminal device by described storage control unit, generate the intermediate file of form up to specification, comprise the data field of specified entry and each specified entry correspondence in the described intermediate file;
The intermediate file memory cell, the intermediate file corresponding stored that is used for described first format conversion unit is generated is the backup file of described initial data.
The technical scheme that the embodiment of the invention provides utilizes format conversion unit initial data to be converted to the intermediate file of prescribed form, the specified entry and the corresponding data field that comprise initial data in the intermediate file of prescribed form, prescribed form according to intermediate file, format conversion unit can also read data field wherein from middle file, thereby generates the target data of initial data correspondence.
Description of drawings
Fig. 1 is when directly transmitting data between the described mobile terminal device of the embodiment of the invention, the handling process schematic diagram of transmitting terminal;
Fig. 2 is when directly transmitting data between the described mobile terminal device of the embodiment of the invention, the handling process schematic diagram of receiving terminal;
The converting system structural representation of transmission data between the mobile terminal device that Fig. 3 provides for the embodiment of the invention;
Fig. 4, Fig. 5, Fig. 6 are respectively a kind of mobile terminal device structural representation that the embodiment of the invention provides;
A kind of system configuration schematic diagram that utilizes third party device to realize the mobile terminal device transfer of data that Fig. 7 provides for the embodiment of the invention.
Embodiment
The embodiment of the invention is for realizing the transfer of data between the various mobile terminal devices, a kind of conversion method of mobile terminal device data is provided, initial data to the each type on the existing various mobile terminal devices, analyze total clauses and subclauses wherein, the specified entry that clauses and subclauses must be transmitted as the type initial data will be had, and be the intermediate file of the initial data setting prescribed form of each type, intermediate file is converted according to unified prescribed form, each specified entry that wherein comprises and corresponding data field, if intermediate file sends to receiving terminal, receiving terminal is according to the prescribed form identification intermediate file of correspondence, and therefrom obtain the data field of each specified entry correspondence, the form of supporting according to this locality saves as target data with the data field of each specified entry correspondence, thereby utilizes the intermediate file of prescribed form to realize total data information transmission between the mobile terminal device.If intermediate file as the backup file of initial data, then can therefrom obtain the total field information of initial data.
Carrying out transfer of data with first mobile terminal device between second mobile terminal device below is that example is elaborated.
As shown in Figure 1, first mobile terminal device comprises the steps: the processing of data
S101, the specified entry that comprises in the intermediate file of form are according to the rules preserved the data field that obtains each specified entry correspondence from initial data from this terminal equipment;
S102, generation intermediate file, described intermediate file form up to specification is comprising the data field of each specified entry and each specified entry correspondence;
The intermediate file of S103, transmission form up to specification.
As shown in Figure 2, the processing of second mobile terminal device mainly comprises the steps:
The intermediate file of S201, reception form up to specification comprises each specified entry and corresponding data field in the described intermediate file;
S202, each specified entry that comprises in the form are according to the rules obtained the data field of each specified entry correspondence from middle file;
S203, generate the target data that this terminal is supported, comprise the data field of each specified entry correspondence in the target data.
Because the form of intermediate file is pre-specified, therefore in the technical scheme that the embodiment of the invention provides, only the conversion equipment that carries out data transaction need be set on mobile terminal device, first mobile terminal device utilizes this device that format conversion unit is set can be converted to specified entry and corresponding data intermediate file, second mobile terminal device utilizes this conversion equipment to obtain the data field of each specified entry correspondence from the intermediate file of form up to specification, and according to the form of the second mobile terminal device support data field of each specified entry correspondence is saved as target data.
First mobile terminal device and second mobile terminal device conversion equipment separately can also be arranged on the third party device, for example on the computer, after first mobile terminal device and second mobile terminal device are connected to third party device by bus respectively, connect by the intercommunication interface between the conversion equipment of first mobile terminal device and second mobile terminal device, the conversion equipment of first mobile terminal device obtains the data of specified entry and generates the intermediate file of form up to specification from first mobile terminal device by bus, intermediate file is sent to the conversion equipment of second mobile terminal device by internal interface, after the conversion equipment of second mobile terminal device generates target data, target data is sent to second mobile device, thereby finish the transfer of data between the mobile terminal device.
In fact, owing to comprise the most information in the initial data in the intermediate file, so can be used as the backup file of initial data preserves, if on first mobile terminal device, generate during intermediate file, then intermediate file can be kept in the storage area on first mobile terminal device, if generate on third party device, then intermediate file can be kept in the storage area of third party device.
Initial data on the mobile terminal device comprises all kinds, and for example: classes of messages data, phone directory class data or mail class data, classes of messages data further comprise SMS classes of messages data, IM classes of messages data or MMS class data etc. again.Therefore be all kinds of initial data of identification, can also set corresponding type identification, the corresponding separately different type identification of inhomogeneity initial data, all kinds of initial data of use pattern sign difference in intermediate file for the initial data of each type.
In the technical scheme that the embodiment of the invention provides, can set various transmission modes flexibly, the user can be by different data transfer instruction selection a kind of patterns wherein, for example transmit a SMS message at every turn, perhaps transmit many SMS message simultaneously, at this moment need coded message be set in intermediate file, be used to distinguish the specified entry and the data field breath of SMS message correspondence; Can also transmit dissimilar initial data simultaneously, for example phone directory class data and classes of messages data be transmitted etc. together.
As shown in Figure 3, the embodiment of the invention provides a kind of converting system of mobile terminal device data, comprise between first mobile terminal device 31 and second mobile terminal device, 32, the first mobile terminal devices 31 and second mobile terminal device 32 connecting by infrared or blue teeth wireless, wherein:
As shown in Figure 4, first mobile terminal device 31 comprises:
Transfer instruction receiving element 311 is used to receive data transfer instruction;
Original data storage unit 312, the first storage control unit 313 and first format conversion unit 314, the original data transmissions instruction that described first format conversion unit 314 receives according to transfer instruction receiving element 311, from original data storage unit 312, obtain the data field of specified entry correspondence by the described first storage control unit 313, and generate the intermediate file of form up to specification, comprise the data field of specified entry and each specified entry correspondence in the described intermediate file;
Intermediate file transmitting element 315 is used for described intermediate file is sent to second mobile terminal device 32.
As shown in Figure 5, second mobile terminal device 32 comprises:
Intermediate file receiving element 321 is used to receive the intermediate file that first mobile terminal device 31 sends;
Second format conversion unit 322, the second storage control unit 323 and target data memory cell 324, described second format conversion unit 322 is obtained the data field of each specified entry correspondence from the intermediate file that middle file receiving element 321 receives, and by the form of the described second storage control unit 323 according to the mobile terminal device support, 324 data fields with each specified entry correspondence save as target data in described target data memory cell.
Further as shown in Figure 6, if desired intermediate file is saved as the backup file of initial data, then also comprises on first mobile terminal device:
Intermediate file memory cell 316 is used to store the intermediate file that described first format conversion unit 314 generates.
Because the transfer of data between the portable terminal is normally two-way, the intermediate file receiving element and second converting unit also can be set on first mobile terminal device, be used for receiving intermediate file and being converted to the target data that first mobile terminal device is supported from second mobile terminal device.Transfer instruction receiving element, original data storage unit, storage control unit and first format conversion unit also can be set on second mobile terminal device, be used to generate intermediate file and send to first mobile terminal device.At this moment, first format conversion unit and second format conversion unit that are positioned on the same mobile terminal device merge setting, and intermediate file transmitting element and intermediate file receiving element merge setting.
As shown in Figure 7, in the embodiment of the invention, on first mobile terminal device 31 except that other functional unit, first format conversion unit 314 is arranged on the third party device, on second mobile terminal device 32 except that other functional unit, second format conversion unit 322 also is arranged on the third party device, first format conversion unit 314 is connected by the intercommunication interface with second format conversion unit 322, first mobile terminal device 31 is connected third party device by bus respectively with second mobile terminal device 32, realizes transfer of data between first mobile terminal device 31 and second mobile terminal device 32 by third party device like this.
Certainly, first format conversion unit 314 also can be separately positioned on the different third party devices with second format conversion unit 322, transmits intermediate file by a flash memory device between format conversion unit.
Consult shown in Figure 6ly, the first storage control unit, first format conversion unit and intermediate file memory cell have formed the data backup system of mobile terminal device.Even first format conversion unit is set on the third party device, still can carry out the backup of initial data for mobile terminal device.Backup functionality can be controlled by user instruction, also can be regular automatically perform, the embodiment of the invention does not limit concrete trigger mechanism.
As seen, the technical scheme that the embodiment of the invention provides does not need the data memory format on the unified mobile terminal device, just can conveniently realize the transmission of data between the mobile terminal device and interconnects.
Those skilled in the art should be appreciated that, the format conversion unit that the embodiment of the invention provides or other functional unit, all or part of is to finish by the relevant hardware of program command, this program can be stored in the read/write memory medium, and read/write memory medium is random asccess memory, disk, CD etc. for example.After this program is by computer run, can realize transfer of data and backup between the mobile terminal device.
In the embodiment of the invention, intermediate file can adopt txt file or XML file, and wherein: the form of XML file can use DTD (Document Type Difinition, DTD)/document format Schema to describe.When format conversion unit generates intermediate file, need to resolve the prescribed form of corresponding described original data type, determine each specified entry that comprises in the described prescribed form; According to each specified entry that comprises in the described prescribed form, from described initial data, obtain the data field of each specified entry correspondence respectively then.When format conversion unit is obtained the data field of each specified entry correspondence from middle file, also need to resolve the prescribed form of corresponding described original data type, determine each specified entry that comprises in the described prescribed form; According to each specified entry that comprises in the described prescribed form, from described intermediate file, obtain the data field of each specified entry correspondence then.
Directly transmit data instance with mobile terminal device below, describe technical solution of the present invention in detail.
Transmission SMS data between embodiment one, the mobile terminal device
At present, the SMS data of mobile terminal device storage comprise: the SMS data that the SMS data that mobile terminal device is received from network side, mobile terminal device send, the SMS data rough draft and the received special SMS data such as transmission report of mobile terminal device of writing at mobile terminal device.These SMS data form the SMS data file, are stored on the mobile terminal device according to the form of determining (perhaps user select form), use for the SMS of this locality, can read the SMS data as the inbox of SMS, and successfully present to the user.Because the location mode of each mobile terminal device file system and operating system, application program and data is different, so the mode of the SMS that each mobile terminal device is deposited may be incomplete same.
Present embodiment is by being provided with the transmission that format conversion unit realizes the SMS data at mobile terminal device, the source mobile terminal device is finished the storage of SMS data in mobile terminal device this locality, source, when transfer of data, the format conversion unit that is arranged on the mobile terminal device of source reads specified entry in the local SMS data of storing, and be generated as the intermediate file format of transfer of data defined, send this intermediate file to the purpose mobile terminal device, after the format conversion unit that is provided with on the purpose mobile terminal device is resolved intermediate file, obtain the data that need and be stored as the initial data that this mobile terminal device is supported, be stored in destination mobile terminal equipment this locality then.
The total information field that SMS need preserve mainly comprises:
Source address field mainly is meant the address of the transmit leg of SMS;
Destination address field (DAF) mainly is meant SMS recipient's address;
Data (Data) field mainly is meant the main contents of SMS, may be literal, also can be binary content;
Temporal information (TimeStamp) field mainly is meant the temporal information of SMS;
Type (Type) field mainly is meant to comprise the type of SMS: the message of reception, the message of transmission, draft, Push message, contents such as status report.
Should can be used as specified entry by total information field, need be included in the intermediate file.
The mode that generates intermediate file has a lot, for example:
Mode one, XML (Extensible Markup Language, extend markup language) mode.Its core is to finish the function of corresponding data transaction with the mode of SGML.Each mark is specified entry.Define a kind of storage of rule and the general format and the scheme of transmission because the XML mode is one, utilize the mode of XML, can realize transfer of data very easily.And, under the situation that data element changes, only need the result after specific DTD of modification or Schema just can allow the format conversion unit adaptation change, and do not need again format conversion unit to be made amendment, have adaptive capacity significantly.
Process that XML realizes and text mode are relatively more corresponding, and the form and the rule of data that different are define according to DTD and Schema.Below be an example of being correlated with:
A kind of form that may adopt of the DTD of SMS data intermediate file, comprising each specified entry, for example: ELEMENT Orignal_Address is the sender address of SMS etc.:
<？xml?version＝″1.0″encoding＝″UTF-8″？>
<！ELEMENT?SMS_Bakup(Orignal_Address*，Destination_Address*，Date+，TimeStamp+，Type+)>
＜!--form of the DTD of the backup of SMS--〉
<！ELEMENT?Orignal_Address(#PCDATA)>
＜!--mainly be meant the sender address of SMS.-->
<！ELEMENT?Destination_Address(#PCDATA)>
＜!--mainly be meant SMS recipient's address.-->
<！ELEMENT?Date(#PCDATA)>
＜!--mainly being meant the main contents of SMS, may be literal, also can be binary content.-->
<！ELEMENT?TimeStamp(#PCDATA)>
＜!--mainly be meant the temporal information of SMS.-->
<！ELEMENT?Type(MT_SMS？|MO_SMS？|Draft_SMS？|Delivery_Report？)>
＜!--mainly be meant the type of SMS, mainly comprise 4 classes at present.-->
<！ELEMENT?MT_SMS(#PCDATA)>
＜!--SMS type that mobile terminal device receives--〉
<！ELEMENT?MO_SMS(#PCDATA)>
＜!--the SMS type that mobile terminal device sends.-->
<！ELEMENT?Draft_SMS(#PCDATA)>
＜!--the rough draft SMS type that write mobile terminal device this locality.-->
<！ELEMENT?Delivery_Report(#PCDATA)>
＜!--the Report Type that mobile terminal device receives about SMS.-->
Above DTD in the middle of, mainly stipulated the form of the specified entry that SMS in the middle of the different mobile terminal equipment is total, this comprising:
Sender's address information, in the middle of reality, only there are one in sender's address information and addressee's address information, in the middle of this example, sender and addressee's address information can be sky, also can be one or more, the data based concrete demand of specific address information and deciding.
Addressee's address information, in the middle of reality, only there are one in sender's address information and addressee's address information, in the middle of this example, sender and addressee's address information can be sky, also can be one or more, the data based concrete demand of specific address information and deciding.
The main information of SMS is the body matter of SMS, and just the main entrained information of SMS may be literal, also may be the content of other form.For long SMS, this part content be not confined to 140 bytes, and can be the content of the long SMS after the mobile terminal device splicing is finished;
The temporal information of SMS mainly comprises the date here, and with concrete hour, minute and second information;
Information such as the type of SMS, here, main SMS according to different purposes classifies, and the main SMS that still stores according to mobile terminal device this locality of these classification distinguishes.Such as, the transmission report of the SMS of the rough draft SMS of the SMS that sends from mobile terminal device, the SMS that mobile terminal device receives, the local storage of mobile terminal device, mobile terminal device storage etc., in intermediate file, can set corresponding identification information for the SMS of difference classification.
The initial data that mobile terminal device A goes up SMS leaves in the memory cell on the mobile terminal device with following logical form:
A_Original_Address＝123456789
A_Destination_Address＝987654321
A_Data＝How?Are?You？
A_TimeStamp＝2007/6/19?GMT?00:00
A_SMS_Type＝Received?SMS
A_Squene＝001
A_Status＝Read
The intermediate file that comprises the specified entry data field of mobile terminal device A output, the mode of employing XML forms the form as the document of next XML:
<？xml?version＝″1.0″encoding＝″UTF-8″？>
<！DOCTYPE?SMS_Bakup?xmls＝″http://www.sample.com/DTD/SMS-Bakup.dtd″>
<SMS_Bakup>
<Original_Address>123456789</Original_Address>
<Destination_Address>987654321</Destination_Address>
<Date>How?Are?You？</Date>
<TimeStamp>2007/6/19GMT?00:00</TimeStamp>
<SMS_Type>Received?SMS</SMS_Type>
</SMS_Bakup>
Above-mentioned data are documents of an XML.Its document name may be SMS_Bakup.xml.
If transmit initial data of the same type, the intermediate file format that intermediate file that mobile terminal device B generates and mobile terminal device A are generated is identical, is that concrete data are variant.
Mobile terminal device B generates the target data structure of the mobile terminal device B support of following form from the intermediate file of mobile terminal device A reception XML document form according to the data field of each specified entry behind the parsing intermediate file:
B_Original_Address＝123456789
B_Destination_Address＝987654321
B_Data＝How?Are?You？
B_TimeStamp＝2007/6/19?GMT?00:00
B_SMS_Type＝Received?SMS
B_Message_Type＝SMS
By above-mentioned mode, just finished the transmission of SMS data between different mobile terminal devices.
Mode two, wherein, the form of XML document intermediate file can also adopt the mode that is packaged into binary data packets, and then corresponding DTD is as follows, and wherein specified entry is for example: ELEMENT Received_SMS represents the type of short message etc.:
<？xml?version＝″1.0″encoding＝″UTF-8″？>
<！ELEMENT?SMS_Bakup_alternative(Sequence，SMS_Type，Data)>
<！ELEMENT?Data(#PCDATA)>
<！ELEMENT?Sequence(#PCDATA)>
<！ELEMENT?SMS_Type(Received_SMS？|Delivery_SMS？|Draft_SMS？|
Delivery_Report？)>
<！ELEMENT?Received_SMS(#PCDATA)>
<！ELEMENT?Delivery_SMS(#PCDATA)>
<！ELEMENT?Draft_SMS(#PCDATA)>
<！ELEMENT?Delivery_Report(#PCDATA)>
Based on the mode of above-mentioned DTD, the intermediate file of the XML document form that mobile terminal device A generates is as follows:
<？xml?version＝″1.0″encoding＝″UTF-8″？>
<！DOCTYPE SMS_Bakup_alternative
xmls＝″http://www.sample.com/DTD/SMS-Bakup-Alternative.dtd″>
<SMS_Bakup_alternative>
<Sequence>001</Sequence>
<SMS_Type>
<Received_SMS>1</Received_SMS>
</SMS_Type>
<Data>0010101101010100000111111010101000000111111111111110101000000000001
111111111</Data>
</SMS_Bakup_alternative>
Wherein:
The content of " 00,101,011,010,101,000,001,111,110,101,010,000,001,111,111,111,111,101,010 00000000001111111111 " representative then is the binary form of a SMS of use in the middle of this enforcement, has wherein comprised all information and the content of SMS.
After mobile terminal device B receives intermediate file, resolve intermediate file and be converted into local data of storing.
Mode three: the mode of text.As the mode of similar files such as txt, provide the form that certain information is formed in advance, format conversion unit form according to the rules generates the file of text mode.When format conversion unit need read related data, read and resolve according to the rule of the text of realizing providing, and parsing is finished after, extract the data of being correlated with and store accordingly, thereby finish the process of conversion.
The mode of text not only is confined to the mode of txt, can also adopt the scheme of other text formatting, also can adopt the mode of self-defined extension name.Below be an example:
The initial data that is stored in the SMS on the mobile terminal device A may adopt following organizational form:
A_Original_Address＝123456789
A_Destination_Address＝987654321
A_Data＝How?Are?You？
A_TimeStamp＝2007/6/19?GMT?00:00
A_SMS_Type＝Received?SMS
A_Squene＝001
A_Status＝Read
In order to carry out the transfer of data between the mobile terminal device, need to generate intermediate file, in the present embodiment, adopt the good rule of predefined to generate the corresponding text file, and in the middle of text file, preserve the data and the relevant entry of SMS specified entry.
Intermediate file is for example:
SMS?Data?Bakup?Version?1.0
Begin:
Original?Address＝123456789
Destination?Address＝987654321
Data＝How?Are?You？
TimeStamp＝2007/6/19?GMT?00:00
SMS?Type＝Received?SMS
End
If this intermediate file is the document of a txt, then can called after SMS.txt.
The intermediate file of mobile terminal device B mobile terminal receive device A, obtain related data after the parsing, will read in the corresponding storage control module of SMS of mobile terminal device, be stored as the target data that mobile terminal device B supports, thereby finish the process of a conversion from the external data to the internal data.
After finishing conversion, the logical form that mobile terminal device B is used to be stored in the target data on the local mobile terminal equipment may be:
B_Original_Address＝123456789
B_Destination_Address＝987654321
B_Data＝How?Are?You？
B_TimeStamp＝2007/6/19?GMT?00:00
B_SMS_Type＝Received?SMS
B_Message_Type＝SMS
So far mobile terminal device A finishes to the transfer of data of mobile terminal device B, and mobile terminal device B is identical to the transfer of data of mobile terminal device A.By above-mentioned process, can realize freely exchanging of SMS data between the different mobile terminal devices, provide function corresponding thereby needn't consider mobile terminal device itself made amendment.
To sum up, by the mode that is adopted in the middle of the present embodiment, after the SMS data are transformed by the mobile terminal device format conversion unit, between different mobile terminal device format conversion unit, carry out the transmission of SMS data, utilize the function of mobile terminal device format conversion unit then, the method that the SMS data conversion is become the SMS data that this mobile terminal device can discern can realize the transmission of SMS data between different mobile terminal devices effectively, this mode has changed the huge transformation of traditional approach to mobile terminal device, and the efficient that can greatly improve transfer of data reduces cost.
The transmission of embodiment two, propelling movement (Push) classes of messages initial data
Push message is for the server triggers mobile terminal device goes to obtain relevant information on the server, thereby the information of part is issued to the message of mobile terminal device by the mode of Push.Push message can be by the mode of a variety of carryings, and main message can be divided into two classes, and a class is SI (Services Indication, a professional indication) message, and a class is SL (Services Loading, a service downloading) message.By analyzing the difference of SI message and SL message, and on the more present mobile terminal device to the storage mode of SI and SL message, earlier the part that has relatively in the middle of the Push message is summarized.For the substance of complete expression Push message, and finish the transmission of Push message data between the mobile terminal device, need to come the information of complete expression Push message at least by following field.These fields comprise:
Instruction content (Indication) field.
The information content (Infomation) field.
Wherein, the content that comprises of Indication field mainly contains:
The Indication field is meant mainly how this Push message moves, and where points to.
The Infomation field mainly is meant the purposes of this Push message is described.
Hyperlink index (href) field, optional, mainly be meant the URI address that this SI is pointed
SI identifies (si-id) field, and is optional, mainly is meant the ID message of this SI
Founder (created) field, optional, mainly be meant the creation-time of this SI message
The SI term of validity (si-expires) field, optional, mainly be meant out-of-service time of this SI message
Action (action) field, optional, the action that mainly is meant this SI and is taked
Its value can comprise, signal-none, signal-low, signal-medium, signal-high, delete.The value of acquiescence is " sighal-medium ".
The data that comprise in the middle of the Information field mainly contain:
Content (item) field is described, essential, mainly be meant the descriptor of this SI.
Classification grade (class) field, essential, mainly be meant the significance level of this Information.
The class value is NMTOKEN
Data field in the middle of the SL also comprises:
Hyperlink index (href) field, essential, mainly be meant the hyperlink address that SL is pointed,
Action (action) field, essential, mainly be meant the action of adopting at SL,
The Action value is execute-low, execute-high, and a kind of in the middle of the cache, the value of acquiescence is " execute-low ".
Be the public field information that is extracted for the Push message that complete expression mobile terminal device is stored above, these total field informations can be used as the data field of specified entry, are included in the intermediate file and transmit.Because different mobile terminal equipment is for the method difference of Push Message Processing, the mobile terminal device of part also may increase the supplementary of part based on the consideration that realizes, this supplementary does not influence the concrete enforcement of the embodiment of the invention.
Below for the example of a Push message, how simple explanation carries out the transmission of Push message data between the not exclusively compatible mobile terminal device of two data process.
At first, suppose two mobile terminal devices of existence, mobile terminal device A and mobile terminal device B.The effect of mobile terminal device mainly provides the storage of data in this locality, for make data between the mobile terminal device can be between A and B mobile terminal device transmission successfully, need utilize the mobile terminal device format conversion unit to carry out the conversion work between the data and intermediate file in the middle of mobile terminal device A and the B.
The Push message data that is stored on the mobile terminal device A may adopt following data organization form.
A->indication->description＝“You?have?4?new?emails”
A->indication->href＝“http://www.xyz.com/email/123/abc.wml”
A->indication->created＝″2001-07-31T10:13:00Z″
A->indication->si-expires＝″2001-08-07T10:13:00Z″
In order to realize data with Push message by method proposed by the invention, intermediate file can adopt following several possible mode:
Mode one: XML document form
For example, a kind of form that may adopt of the DTD of Push message data transmission:
<？xml?version＝″1.0″encoding＝″UTF-8″？>
<！ELEMENT?Push_Message_Bakup(si？，sl？)>
<！ELEMENT?si(indication，info？)>
<！ELEMENT?indication(#PCDATA)>
<！ATTLIST?indication
href％URI；#IMPLIED
si-id?CDATA#IMPLIED
created?％Datetime；#IMPLIED
si-expires?％Datetime；#IMPLIED
action(signal-none|signal-low|signal-medium|signal-high|delete)″signal-medium″
>
<！ELEMENT?info(item+)>
<！ELEMENT?item(#PCDATA)>
<！ATTLIST?item
class?NMTOKEN#REQUIRED
>
<！ELEMENT?sl?EMPTY>
<！ATTLIST?sl
href％URI；#REQUIRED
action(execute-low|execute-high|cache)″execute-low″
>
<！ENTITY％?Datetime″CDATA″>
<！ENTITY％?URI″CDATA″>
In the middle of the top DTD, mainly stipulated the central specified entry of different mobile terminal equipment, comprising:
The Indication of SI, comprising: the action that the date created of the chained address of SI, the message id of SI, SI, the Expiration Date of SI, the required mobile terminal device of SI are taked;
The Information of SI, comprising: the information description of SI and the significance level of SI;
The attribute information of SL is comprising: the hyperlink address of SL, at required action of taking of SL and action;
The mobile terminal device format conversion unit forms the intermediate file of an XML document form according to the Push message initial data of A:
<？xml?version＝″1.0″encoding＝″UTF-8″？>
<！DOCTYPE Push_Message_Bakup
xmls＝″http://www.sample.com/DTD/Push-Bakup.dtd″>
<Push_Message_Bakup>
<si>
<indication?href＝″′http://www.xyz.com/email/123/abc.wml″′
created＝′created＝″2001-07-31T10:13:00Z″′
si-expires＝″′2001-08-07T10:13:00Z″′>
You?have?4?new?emails
</indication>
</si>
</Push_Message_Bakup>
Above-mentioned file is the document of an XML, and its document name may be Push_Bakup.xml.
Because Push message has two kinds of SI and SL.Above-mentioned example is the example of a SI, mainly is example with SI in the middle of the present embodiment, and the example of SL is as follows:
<？xml?version＝″1.0″encoding＝″UTF-8″？>
<！DOCTYPE Push_Message_Bakup
xmls＝″http://www.sample.com/DTD/Push-Bakup.dtd″>
<Push_Message_Bakup>
<sl?href＝″′http://www.xyz.com/ppaid/123/abc.wml″′/>
</Push_Message_Bakup>
Still be example below with SI, the Push Bakup.xml that utilizes A to generate carries out the transfer of data of Push message, mobile terminal device B resolves the intermediate file that obtains, and generation mobile terminal device B is used to be stored in the data on the local mobile terminal equipment, and its form can be as follows:
B->Push->SI->indication->description＝“You?have?4?new?emails”
B->Push->SI->indication->href＝“http://www.xyz.com/email/123/abc.wml”
B->Push->SI->indication->created＝″2001-07-31T10:13:00Z″
B->Push->SI->indication->si-expires＝″2001-08-07T10:13:00Z″
B->Push->Message_Type＝Push_SI
By above-mentioned mode, just finished the process of the transmission of data in the middle of different mobile terminal devices of Push message.
The form of mode two, XML document intermediate file can also adopt the mode that is packaged into binary data packets, and DTD that can reference can be referring to following mode:
<？xml?version＝″1.0″encoding＝″UTF-8″？>
<！ELEMENT?Push_Message_Bakup(Message_Type，Sequence，Data)>
＜!--be used for DTD--that Push message is backed up 〉
<！ELEMENT?Message_Type(SI？，SL？)>
<！ELEMENT?SI(#PCDATA)>
＜!--the SI--in the local storage of mobile terminal device of encapsulation 〉
<！ELEMENT?SL(#PCDATA)>
＜!--the SL--in the local storage of mobile terminal device of encapsulation 〉
<！ELEMENT?Sequence(#PCDATA)>
＜!--sequence number of the message that is transformed--〉
<！ELEMENT?Data(#PCDATA)>
＜!--data of encapsulation--〉in the local Push message of storing of mobile terminal device
Suppose that Push message is a binary mode in the storage of mobile terminal device, then utilize mobile terminal device A and mobile terminal device format conversion unit, the data that mobile terminal device A is stored encapsulate according to the DTD of the XML document that is used for carrying out transfer of data, have formed following intermediate file:
<？xml?version＝″1.0″encoding＝″UTF-8″？>
<！DOCTYPE Push_Message_Bakup
xmls＝″http://www.sample.com/DTD/Push-Bakup-Alternative.dtd″>
<Push_Message_Bakup>
<Message_Type>
<SI>1</SI>
</Message_Type>
<Sequence>001</Sequence>
<Data>01000011110101010000001111111101001111111111111111100001111111111111
11111111</Data>
</Push_Message_Bakup>
Wherein:
" 01,000,011,110,101,010,000,001,111,111,101,001,111,111,111,111,111,100,001 11111111111111111111 " are the binary file layout of SI part in the middle of mobile terminal device A of Push message in the middle of the embodiment.
Mobile terminal device B can be with parsing by format conversion unit behind the intermediate file that gets access to mobile terminal device A, and forms mobile terminal device B and can discern and formats stored, and the result after it transforms is as follows:
B->Push->SI->indication->description＝“You?have?4?new?emails”
B->Push->SI->indication->href＝“http://www.xyz.com/email/123/abc.wml”
B->Push->SI->indication->created＝″2001-07-31T10:13:00Z″
B->Push->SI->indication->si-expires＝″2001-08-07T10:13:00Z″
B->Push->Message_Type＝Push_SI
Can also adopt the mode of text, specific implementation is referring to shown in the embodiment one.
The transmission of embodiment three, Email initial data
The total information field that analysis Email need preserve mainly comprises:
Date (Date) field mainly comprises the temporal information of Email.
Sender (From) field mainly comprises Email sender's relevant information.
Theme (Subject) field mainly comprises the subject information of Email.
Recipient (To) field mainly comprises Email addressee's relevant information.
Return address (Reply-to) field mainly comprises the return address information of this Email.
The multipurpose internet mail is expanded (MIME) version (MIME-version) field, mainly comprises the version number of the MIME of Email.
Reverse-path (Return-Path) field mainly is that sign is connected to the route that destination server adopts.General just sender address shows that mail directly sends destination server to.
Transmission information (Delivered-To) field mainly is that the explanation mail is sent to that mailbox.
Reception information (Received) field, the information that this head part is represented respectively comprises:
From hostname (obtaining) from host;
By hostname (collecting) by host;
Via physical-path (by what path---mail server);
With protocol (using what agreement);
Id message-id (message id number);
For final destination (message destination address);
Time (time mark).
The message that each mail server is all received to each bar is added an own new Received field.Can see that this envelope mail has two Received fields.
The address (CC field) of making a copy for mainly is meant address, the side of making a copy for.
The close address (BCC field) of sending mainly is meant and secretly destroies the address.
Message identifier (Message-ID) field mainly is meant the identification id that message is unique.
Content delivery coded system information (Content-Transfer-Encoding) field is meant mainly how the binary data that is embedded in the message is encoded into the ASCII text.
Content description (Content-Description) field is meant that mainly being used for the ASCII of in the text of email message identification data describes.
Contents attribute (Content-Disposition) field mainly is the content ownership of Content.
Content identification (Content-ID) field mainly is meant to be used for going to identify a MIME session with a unique authentication code under the situation of using many directory contents.
Content type (Content-type) field, this field are the places of action beginning, have identified the data that encapsulate in MIME message.
Content rating (Content-class) field mainly is meant the rank of Content.
Character set (Charset) field mainly is meant the coded system of character.
Content-data (Data) field mainly is the specific coding that is used for comprising the Content content.
Annex name (Name) field mainly is the name that is used for describing Content.
Attachment files name (Filename) field mainly is the filename that is used for describing annex.
Above-mentioned main information field as specified entry, need be included in the intermediate file, and intermediate file can adopt XML mode etc.Those skilled in the art can be not described in detail here referring to the DTD and the XML document of embodiment one or embodiment two acquisition XML files.
Mode one, XML mode
A kind of form that may adopt of the DTD of Email transfer of data.
<？xml?version＝″1.0″encoding＝″UTF-8″？>
<！ELEMENT?Email_Bakup(Return-Path？，Delivered-To*，Received*，Date+，CC？，BCC？，
Message-ID*，From+，Subject*，To+，Reply-to*，MIME-version+，Content+)>
<！ELEMENT?Content?(Content-type*，charset*，Data*，Name*，Filename*，
Content-Transfer-Encoding*，Content-Description*，Content-Disposition*，Content-ID*，
Content-class*)>
<！ELEMENT?Return-Path(#PCDATA)>
<！ELEMENT?Delivered-To(#PCDATA)>
<！ELEMENT?Received(#PCDATA)>
<！ELEMENT?Date(#PCDATA)>
<！ELEMENT?CC(#PCDATA)>
<！ELEMENT?BCC(#PCDATA)>
<！ELEMENT?Message-ID(#PCDATA)>
<！ELEMENT?From(#PCDATA)>
<！ELEMENT?Subject(#PCDATA)>
<！ELEMENT?To(#PCDATA)>
<！ELEMENT?Reply-to(#PCDATA)>
<！ELEMENT?MIME-version(#PCDATA)>
<！ELEMENT?Content-Transfer-Encoding(#PCDATA)>
<！ELEMENT?Content-Description(#PCDATA)>
<！ELEMENT?Content-Disposition(#PCDATA)>
<！ELEMENT?Content-ID(#PCDATA)>
<！ELEMENT?Content-type(#PCDATA)>
<！ELEMENT?Content-class(#PCDATA)>
<！ELEMENT?charset(#PCDATA)>
<！ELEMENT?Data(#PCDATA)>
<！ELEMENT?Name(#PCDATA)>
<！ELEMENT?Filename(#PCDATA)>
Above DTD in the middle of, mainly stipulated the common relevant information format of Email in the middle of the different mobile terminal equipment, this comprising:
The temporal information of Email;
Email sender's relevant information;
The subject information of Email;
Email addressee's relevant information;
The return address information of Email;
The version number information of the MIME of Email;
Email is sent to the information of which mailbox;
The Email side of making a copy for address information;
Email secretly copies address information;
The information relevant such as identification id information that Email message is unique with Email.
Mode below the logical form of the initial data of Email on mobile terminal device A can adopt:
A_From＝Alice<Alice@sample.com>
A_To＝Bob@sample.com
A_Cc＝Mike@sample.com
A_Subject＝FYI
A_Date＝Tue，26?Jun?2007?14:15:16?+0800
A_MIME-Version＝1.0
A_Content-Type＝multipart/mixed
A_Type＝Received?Email
A_Squene＝001
A_Status＝Read
A_Attachement＝Yes
A_AttacheNumber＝2
A_AttachFileName＝Email/Attachment/FYI.html
A_AttachFileName＝Email/Attachment/Attachment.txt
Except about the relevant descriptor of Email, also has the information of the relevant annex of Email.The annex of Email should be a file one by one, and it mainly leaves in the middle of the relevant memory cell of mobile terminal device.
FYI.html file and Attachment.txt file all are placed in the middle of the memory cell, and store accordingly.
The intermediate file of mobile terminal device A output XML document form, for example:
<？xml?version＝″1.0″encoding＝″UTF-8″？>
<！DOCTYPE?Email_Bakup?xmls＝″http://www.sample.com/DTD/Email-Bakup-Final.dtd″>
<Email_Bakup>
<From>″Alice<Alice@sample.com>″</From>
<To>″Alice@sample.com″</To>
<Cc>″Alice@sample.com″</Cc>
<Subject>″FYI″</Subject>
<date>″Tue，26?Jun?2007?14:15:16?+0800″</date>
<MIME-Version>″1.0″</MIME-Version>
<Content-Type>″multipart/mixe?d″</Content-Type>
<content>
<Content-Type>text/plain</content-Type>
<charset>″gb2312″</charset>
<Content-Transfer-Encoding>base64</Content-Transfer-Encoding>
<Data>
″RllJDQoNCg0KDQpDaGVuIEd1b3FpYW8gs8K5+sfHICBSJkQgRW5naW5lZXINCk
1vYmlsZSBUZXJt
aW5hbCBEZXAuDQpIdWF3ZWkgVGVjaG5vbG9naWVzIENvLixMdGQuDQpIdWEg
V2VpIEJsZC4sTm8u
MyBYaW54aSBSZC4sU2hhbmctRGkgSW5mb3JtYXRpb24gDQpJbmR1c3RyeSBCYX
NlLEhhaS1EaWFu
IERpc3RyaWN0IEJlaWppbmcgUC5SLkNoaW5hIA0KWklQo7oxMDAwODUgIA0KV
GVsOiArODYtMTAt
ODI4MzYzNjYNCkZBWKO6Kzg2LTEwLTgyODM2MTMzDQpFbWFpbDogY2hlbm
d1b3FpYW9AaHVhd2Vp
LmNvbQ＝＝″
</Data>
</Content>
<Content>
<Content-Type>text/html<content-Type>
<charset>″gb2312″</charset>
<Content-Transfer-Encoding>″base64″</Content-Transfer-Encoding>
<data>
″PCFET0NUWVBFIEhUTUwgUFVCTElDICItLy9XM0MvL0RURCBIVE1MIDQuMCBU
cmFuc2l0aW9uYWwv
L0VOIj4NCjxIVE1MPjxIRUFEPg0KPE1FVEEgaHR0cC1lcXVpdj1Db250ZW50LVR5cGU
gY29udGVu
dD0idGV4dC9odG1sOyBjaGFyc2V0PWdiMjMxMiI+DQo8TUVUQSBjb250ZW50PSJNU0
hUTUwgNi4w
MC4yODAwLjE1NjEiIG5hbWU9R0VORVJBVE9SPg0KPFNUWUxFPjwvU1RZTEU+DQ
o8L0hFQUQ+DQo8
Qk9EWSBiZ0NvbG9yPSNjY2U4Y2Y+DQo8RElWPjxGT05UIHNpemU9Mj5GWUk8L0Z
PTlQ+PC9ESVY+
DQo8RElWPjxGT05UIHNpemU9Mj48L0ZPTlQ+Jm5ic3A7PC9ESVY+DQo8RElWPjxGT
05UIHNpemU9
Mj48L0ZPTlQ+Jm5ic3A7PC9ESVY+DQo8RElWPiZuYnNwOzwvRElWPg0KPERJVj48R
k9OVCBzaXpl
PTI+Q2hlbiBHdW9xaWFvILPCufrHxyZuYnNwOyBSJmFtcDtEIEVuZ2luZWVyPEJSPk1v
YmlsZSBU
ZXJtaW5hbCANCkRlcC48QlI+SHVhd2VpIFRlY2hub2xvZ2llcyBDby4sTHRkLjxCUj5IdW
EgV2Vp
IEJsZC4sTm8uMyBYaW54aSBSZC4sU2hhbmctRGkgDQpJbmZvcm1hdGlvbiA8QlI+SW5
kdXN0cnkg
QmFzZSxIYWktRGlhbiBEaXN0cm1jdCBCZWlqaW5nIFAuUi5DaGluYSANCjxCUj5aSVC
jujEwMDA4
NSZuYnNwOyA8QlI+VGVsOiArODYtMTAtODI4MzYzNjY8QlI+RkFYo7orODYtMTAtO
DI4MzYxMzM8
QlI+RW1haWw6IA0KPEEgDQpocmVmPSJtYWlsdG86Y2hlbmd1b3FpYW9AaHVhd2VpL
mNvbSI+Y2hl
bmd1b3FpYW9AaHVhd2VpLmNvbTwvQT48L0ZPTlQ+PC9ESVY+PC9CT0RZPjwvSFR
NTD4NCg＝＝″
</data>
</Content>
<Content>
<Content-Type>″text/plain″</Content-Type>
<name>″attachment.txt″<name>
<Content-Transfer-Encoding>″7bit″</Content-Transfer-Encoding>
<Content-Disposition>attachment</Content-Disposition>
<filename>″attachment.txt″</filename>
<data>
″just?test.″
</data>
</content>
</Email_Bakup>
The document name of XML document may be Email_Bakup.xml.
The intermediate file that mobile terminal device B obtains is exactly the document of the XML that generated of mobile terminal device A, for example Email_Bakup.xml.
Mobile terminal device B resolves intermediate file and is stored in local mobile terminal equipment by format conversion unit, initial data for example:
B->Email->To＝Bob@sample.com
B->Email->Cc＝Mike@sample.com
B->Email->Subject＝FYI
B->Email->Date＝Tue，26?Jun?2007?14:15:16?+0800
B->Email->MIME-Version＝1.0
B->Email->Content-Type＝multipart/mixed
B->Email->Type＝Received?Email
B->Email->Attachement＝Yes
B->Email->AttacheNumber＝2
B->Email->AttachFile_1->Name＝Email/Attachment/FYI.html
B->Email->AttachFile_2->Name＝Email/Attachment/Attachment.txt
By above-mentioned mode, just finished the transmission of Email data between different mobile terminal devices.
Wherein, the form of passable mode of the content of Email or text.
Mode two, XML adopt the form that is packaged into packet fully
DTD that can reference can be referring to following mode:
<？xml?version＝″1.0″encoding＝″UTF-8″？>
<！ELEMENT?Email_Bakup(Message_Type，Sequence，Data)>
＜!--be used for DTD--that Email message is backed up 〉
<！ELEMENT?Message_Type(Send_Email？，Received_Email？，Draft_Email？)>
<！ELEMENT?Send_Email(#PCDATA)>
＜!--the Email--in the local transmission of storing of mobile terminal device of encapsulation 〉
<！ELEMENT?Received_Email(#PCDATA)>
＜!--the Email--in the local reception of storing of mobile terminal device of encapsulation 〉
<！ELEMENT?Draft_Email(#PCDATA)>
＜!--the Email--at the local rough draft of storing of mobile terminal device of encapsulation 〉
<！ELEMENT?Sequence(#PCDATA)>
＜!--sequence number of the message that is transformed--〉
<！ELEMENT?Data(#PCDATA)>
＜!--data of encapsulation--〉at the local Email that stores of mobile terminal device
The intermediate file of the XML document form that is transformed by the mobile terminal device format conversion unit is as follows:
<？xml?version＝″1.0″encoding＝″UTF-8″？>
<！DOCTYPE Email_Bakup xmls＝″http://www.sample.com/DTD/
Email-Bakup-Alternative.dtd″>
<Email_Message_Bakup>
<Message_Type>
<Received_Email>1</Received_Email>
</Message_Type>
<Sequence>001</Sequence>
<Data>”0100001111010101000000111111110100111111111111111110000111111111111
111111010111101010101010101111111111111111111100000111111111000101010101010101010
1001010101010101011111111000011011111010111111111111111111111111111111111111111111
11111000010101011111111111111111111111111111111111111111111000000010111111111111111
111111111111111111111111111111111111111111111111111111111111111111110000000000010111
11111111111110111111100000000000000000000000000000000000000000000000000000000000
00000000001111”</Data>
</Email_Message_Bakup>
Wherein:
" 01,000,011,110,101,010,000,001,111,111,101,001,111,111,111,111,111,100,001 11,111,111,111,111,111,010,111,101,010,101,010,101,111,111,111,111,111,111 10,000,011,111,111,100,010,101,010,101,010,101,010,010,101,010,101,010,111 11,111,000,011,011,111,010,111,111,111,111,111,111,111,111,111,111,111,111 11,111,111,111,000,010,101,011,111,111,111,111,111,111,111,111,111,111,111 11,111,111,100,000,001,011,111,111,111,111,111,111,111,111,111,111,111,111 11,111,111,111,111,111,111,111,111,111,111,111,111,111,111,100,000,000,000 10,111,111,111,111,111,101,111,111,000,000,000,000,000,000,000,000,000,000 0000000000000000000000000000000000000001111 " are the binary file layout of Email message in the middle of mobile terminal device A in the middle of the embodiment.
The result of mobile terminal device B after obtaining intermediate file and conversion is as follows:
B->Email->To＝Bob@sample.com
B->Email->Cc＝Mike@sample.com
B->Email->Subject＝FYI
B->Email->Date＝Tue，26?Jun?2007?14:15:16?+0800
B->Email->MIME-Version＝1.0
B->Email->Content-Type＝multipart/mixed
B->Email->Type＝Received?Email
B->Email->Attachement＝Yes
B->Email->AttacheNumber＝2
B->Email->AttachFile_1->Name＝Email/Attachment/FYI.html
B->Email->AttachFile_2->Name＝Email/Attachment/Attachment.txt
By above-mentioned mode, just finished the process of the transmission of Email data in the middle of different mobile terminal devices.
The transmission of embodiment four, MMS message initial data
According to the MMS business features, the total information field that MMS need be preserved mainly comprises:
Type of message (Message_Type) field mainly is the type of identification message, as MM1_retrieve.RES.
Multimedia Message version information (MMS_Version) field mainly is the version information of sign MMS message.
Message identifier (Message_ID) field mainly is the message id of sign MM.
Sender address (Sender_address) field mainly is the address of representing to handle recently the mobile terminal device of MM (that is, submitting or transmitted MM to).If the originators mobile terminal device has asked the recipient is hidden its address, then its address can not offer the recipient.
Content type (Content_type) field mainly is the content type of expression MM content.
Recipient address (Recipient_address) field mainly is expression MM recipient's address.May there be a plurality of addresses.
Message grade (Message_class) field mainly is the classification (for example, individual service, advertising service and information service) of expression message.
Time of Day (Date_and_time) field mainly is the time and date that the expression mobile terminal device is handled (that is, submit to or transmit) MM recently.
Priority (Priority) field mainly is the priority (importance) (if the originators mobile terminal device is specified) of expression message.
Theme (Subject) field mainly is the title (if the originators mobile terminal device of MM is specified) of expression whole multimedia message.
Message status (MM_State) field mainly is an expression MM state.Incoming MM may lack this state, and there is this state in the MM of persistent storage.
Content (Content) field mainly is the content (the originators mobile terminal device by MM is specified) of expression Multimedia Message.
Total information field can be used as specified entry, and corresponding data field and items for information need comprise in the intermediate file, and the form of intermediate file can be an XML mode etc.
Mode one
For example, a kind of form that may adopt of the DTD of MMS exchanges data:
<？xml?version＝″1.0″encoding＝″UTF-8″？>
<！ELEMENT?MMS_Bakup(Message_Type+，MMS_Version+，Message_ID+，
Sender_address*，Content_type+，Recipient_address*，Message_class*，Date_and_time+，
Priority*，Subject*，MM_State*，Content*)>
<！ELEMENT?Message_Type(#PCDATA)>
＜!--with this message identifier is MM1_retrieve.RES.-->
<！ELEMENT?MMS_Version(#PCDATA)>
＜!--the version of sign MMSRelay/Server institute supporting interface.-->
<！ELEMENT?Message_ID(#PCDATA)>
＜!--the message id of MM.-->
<！ELEMENT?Sender_address(#PCDATA)>
＜!--handled the mobile terminal device of MM (that is, submitting or transmitted MM to) recently
The address.If the originators mobile terminal device has asked the recipient is hidden its ground
The location, then its address can not offer the recipient.-->
<！ELEMENT?Content_type(#PCDATA)>
＜!--the content type of MM content.-->
<！ELEMENT?Recipient_address(#PCDATA)>
＜!--MM recipient's address.May there be a plurality of addresses.-->
<！ELEMENT?Message_class(#PCDATA)>
＜!--classification of message (for example, individual service, advertising service and information service)--〉
<！ELEMENT?Date_and_time(#PCDATA)>
＜!--mobile terminal device is handled the time and date of (that is, submit to or transmit) MM recently.-->
<！ELEMENT?Priority(#PCDATA)>
＜!--the priority (importance) (if the originators mobile terminal device is specified) of message.-->
<！ELEMENT?Subject(#PCDATA)>
＜!--the title of whole multimedia message is (if the originators mobile terminal device of MM refers to
Fixed).-->
<！ELEMENT?MM_State(#PCDATA)>
＜!--the MM state.Incoming MM may lack this state, persistent storage
There is this state in MM.-->
<！ELEMENT?Content(charset，Content-Transfer_Encoding，Content-Location，Data)>
＜!--the content (the originators mobile terminal device by MM is specified) of Multimedia Message.-->
<！ELEMENT?charset(#PCDATA)>
<！ELEMENT?Content-Transfer-Encoding(#PCDATA)>
<！ELEMENT?Content-Location(#PCDATA)>
<！ELEMENT?Data(#PCDATA)>
Above DTD in the middle of, mainly stipulated the common relevant information format of MMS in the middle of the different mobile terminal equipment, this comprising:
The type information of MMS message;
The version information of MMS message;
The message id information of MMS;
The address information of MMS Originator;
The content information of MMS content;
MMS recipient's address;
The classification information of MMS message;
The time and date information of MMS;
The priority of MMS message (importance) information;
The heading message of MMS message;
The state information of MMS;
Contents such as the particular content information of MMS.
As previously mentioned, the logical form of information initial data on mobile terminal device A of MMS leaves in the memory cell on the mobile terminal device:
A_Message_Type＝MM1_retrieve.RES
A_MMS_Version＝1.2
A_Message_ID＝060717544991000009318
A_Sender_address＝
+8613910111111@mmsc-bj-rsv.monternet.com
A_Content_type＝Multipart/Related
A_Recipient_address＝Alice@sample.com
A_Message_class＝Personal
A_Date_and_time＝Wed，07?Jun?2006?17:54:49?+0800
A_Priority＝Normal
A_Subject＝Hello
A_MM_State＝Retrieved
Except needing in the middle of the data structure to comprise the above-mentioned content, also need data content that MMS is comprised corresponding with the message of top MMS.Therefore, can increase following content:
A_AttachFile＝MMS/S.smil
A_AttachFile＝MMS/8712df01.asc
S.smil data and 8712df01.asc data all leave in below the MMS file of mobile terminal device in the mode of file.
The intermediate file that mobile terminal device A forms the XML document form by format conversion unit is for example:
<？xml?version＝″1.0″encoding＝″UTF-8″？>
<！DOCTYPE?MMS_Bakup?xmls＝″http://www.sample.com/DTD/MMS-Bakup.dtd″>
<MMS_Bakup>
<Message_Type>″MM1_retrieve.RES″</Message_Type>
＜!--essential--〉
＜!--with this message identifier is MM1_retrieve.RES.-->
<MMS_Version>″1.2″</MMS_Version>
＜!--essential--〉
＜!--the version of sign MMSRelay/Server institute supporting interface.-->
<Message_ID>″060717544991000009318″</Message_ID>
＜!--essential--〉
＜!--the message id of MM.-->
<Sender_address>″+8613910111111@mmsc-bj-rsv.monternet.com″</Sender_address>
＜!--optional--〉
＜!--handled the address of the mobile terminal device of MM (that is, submitting or transmitted MM to) recently.If the beginning
The originating party mobile terminal device has asked the recipient is hidden its address, and then its address can not offer the recipient.-->
<Content_type>
<type>″Multipart/Related″</type>
<start>″s.smil″</start>
<type>″application/smil″</start>
</Content_type>
＜!--essential--〉
＜!--the content type of MM content.-->
<Recipient_address>″Alice@sample.com″</Recipient_address>
＜!--optional--〉
＜!--MM recipient's address.May there be a plurality of addresses.-->
<Message_class>″Personal″</Message_class>
＜!--optional--〉
＜!--classification of message (for example, individual service, advertising service and information service)--〉
<Date_and_time>″Wed，07?Jun?2006?17:54:49?+0800″</Date_and_time>
＜!--essential--〉
＜!--mobile terminal device is handled the time and date of (that is, submit to or transmit) MM recently.-->
<Priority>″Normal″</Priority>
＜!--optional--〉
＜!--the priority (importance) (if the originators mobile terminal device is specified) of message.-->
<Subject>″Hello″</Subject>
＜!--optional--〉
＜!--the title (if the originators mobile terminal device of MM is specified) of whole multimedia message.-->
<MM_State>″Retrieve?d″</MM_State>
＜!--optional--〉
＜!--the MM state.Incoming MM may lack this state, and there is this state in the MM of persistent storage.-->
<Content>
＜!--optional--〉
<Content-Type>″text/plain″</Content-Type>
<charset>″utf-8″</charset>
<Content-Transfer-Encoding>″Base64″</Content-Transfer-Encoding>
<Content-Location>″8712df01.asc″</Content-Location>
<Data>″MDblubQ25pyINuaXpeaYr+S4qjY25aSn6aG655qE5ZCJ56Wl5pel5a2Q44CC5Zyo
6L+Z5Liq
576O5aW955qE5pe25Yi777yM56Wd5oKo5bm456aP5ZCJ56Wl77yM5LqL5Lia6aG66aG65
Yip
5Yip77yM55Sf5rS75byA5byA5b+D5b+D77yBAA＝＝″
</Data>
</Content>
<Content>
＜!--optional--〉
<Content-Type>″application/smil″</Content-Type>
<charset>″utf-8″</charset>
<Content-Transfer-Encoding>″Base64″</Content-Transfer-Encoding>
<Content-Location>″s.smil″</Content-Location>
<Data>″PHNtaWw+CjxoZWFkPgo8bGF5b3V0Pgo8cm9vdClsYXlvdXQgd2lkdGg9IjI0MC
IgaGVpZ2h0
PSIyNzQiLz4KPHJlZ2lvbiBpZD0iSW1hZ2UiIHdpZHRoPSIxMDAlIiBoZWlnaHQ9IjEwM
CUi
IGxlZnQ9IjAlIiB0b3A9IjAlIiAvPgo8cmVnaW9uIGlkPSJUZXh0IiB3aWR0aD0iMTAwJSIg
aGVpZ2h0PSIxMDAlIiBsZWZ0PSIwJSIgdG9wPSIwJSIgLz4KPC9sYXlvdXQ+CjwvaGVh
ZD4K
PGJvZHk+CjxwYXIgZHVyPSI3MDAwbXMiPgo8dGV4dCBzcmM9Ijg3MTJkZjAxLmFzY
yIgcmVn
aW9uPSJUZXh0IiBkdXI9IjcwMDBtcyIgLz4KPC9wYXI+CjwvYm9keT4KPC9zbWlsPgo＝
″</Data>
</Content>
＜!--the content (the originators mobile terminal device by MM is specified) of Multimedia Message.-->
</MMS_Bakup>
The document name of XML document may be MMS_Bakup.xml.
Mobile terminal device B resolves the intermediate file of mobile terminal device A, is stored on the local mobile terminal equipment:
B->MMS->Message_Type＝MM1_retrieve.RES
B->MMS->MMS_Version＝1.2
B->MMS->Message_ID＝060717544991000009318
B->MMS->Sender_address＝
+86139111111@mmsc-bj-rsv.monternet.com
B->MMS->Content_type＝Multipart/Related
B->MMS->Recipient_address＝Alice@sample.com
B->MMS->Message_class＝Personal
B->MMS->Date_and_time＝Wed，07?Jun?2006?17:54:49+0800
B->MMS->Priority＝Normal
B->MMS->Subject＝Hello
B->MMS->MM_State＝Retrieved
B->MMS->AttachFile_1＝MMS/Attachment/S.smil
B->MMS->AttachFile_2＝MMS/Attachment/8712df01.asc
The data content that MMS comprised needs corresponding with the message of top MMS, can be stored under the MMS/Attachment/ file of mobile terminal device.
By above-mentioned mode, just finished the process of the exchanges of MMS data in the middle of different mobile terminal devices.
Certainly, the content of MMS can be to adopt the mode of this DTD, also can adopt the mode that the MMS data are packaged into packet fully to store.So following DTD is the mode of another possibility.
Mode two, XML encapsulate the memory contents of Push message at mobile terminal device.It can reference DTD can participate in following mode:
<？xml?version＝″1.0″encoding＝″UTF-8″？>
<！ELEMENT?Email_Bakup(Message_Type，Sequence，Data)>
＜!--be used for DTD--that Email message is backed up 〉
<！ELEMENT?Message_Type(Send_Email？，Received_Email？，Draft_Email？)>
<！ELEMENT?Send_Email(#PCDATA)>
＜!--the Email--in the local transmission of storing of mobile terminal device of encapsulation 〉
<！ELEMENT?Received_Email(#PCDATA)>
＜!--the Email--in the local reception of storing of mobile terminal device of encapsulation 〉
<！ELEMENT?Draft_Email(#PCDATA)>
＜!--the Email--at the local rough draft of storing of mobile terminal device of encapsulation 〉
<！ELEMENT?Sequence(#PCDATA)>
＜!--sequence number of the message that is transformed--〉
<！ELEMENT?Data(#PCDATA)>
＜!--data of encapsulation--〉at the local Email that stores of mobile terminal device
Suppose that Email message is a binary mode in the storage of mobile terminal device.Utilize mobile terminal device A and format conversion unit, the data that mobile terminal device A is stored encapsulate according to the DTD of the XML document that is used for carrying out exchanges data, and the XML document form intermediate file that format conversion unit transforms is as follows:
<？xml?version＝″1.0″encoding＝″UTF-8″？>
<！DOCTYPE?MMS_Bakup?xmls＝″http://www.sample.com/DTD/
MMS-Bakup-Alternative.dtd″>
<MMS_Message_Bakup>
<Message_Type>
<Received_MMS>1</Received_MMS>
</Message_Type>
<Sequence>001</Sequence>
<Data>”11111111110000101010111111111111111111111111111111111111111111110000
000101111111111111111111111111111111111111111111111111111111111111111111111111111111
111111100000000000101111111111111111011111110000010110000100001001000011100001111
0001100000001111100001000001110001000101000100100100010100000010011110100001111
010101000000111111110100111111111111111110010011111111111111111101011000000000000
000110101010101010111111111111111111110000011111111100010101010111101010101010010
10101010101011111111000011011111010111111111111111111111111111111111111”</Data>
</MMS_Message_Bakup>
”111111111100001010101111111111111111111111111111111111111111111100000001011111
11111111111111111111111111111111111111111111111111111111111111111111111111111111111000
00000000101111111111111111011111110000010110000100001001000011100001111000110000
0001111100001000001110001000101000100100100010100000010011110100001111010101000
0001111111101001111111111111111100100111111111111111111010110000000000000001101010
101010101111111111111111111100000111111111000101010101111010101010100101010101010
1011111111000011011111010111111111111111111111111111111111111”
Mobile terminal device B is after getting access to this intermediate file, these data can be extracted the binary storage content of MMS message in the middle of the XML by format conversion unit, and form mobile terminal device B and can discern and formats stored, the result after it transforms is as follows:
B->MMS->Message_Type＝MM1_retrieve.RES
B->MMS->MMS_Version＝1.2
B->MMS->Message_ID＝060717544991000009318
B->MMS->Sender_address＝
+86139111111@mmsc-bj-rsv.monternet.com
B->MMS->Content_type＝Multipart/Related
B->MMS->Recipient_address＝Alice@sample.com
B->MMS->Message_class＝Personal
B->MMS->Date_and_time＝Wed，07?Jun?2006?17:54:49?+0800
B->MMS->Priority＝Normal
B->MMS->Subject＝Hello
B->MMS->MM_State＝Retrieved
B->MMS->AttachFile_1＝MMS/Attachment/S.smil
B->MMS->AttachFile_2＝MMS/Attachment/8712df01.asc
By above-mentioned mode, just finished the process of the exchanges of MMS data in the middle of different mobile terminal devices.The annex of MMS should be a file one by one, and it mainly leaves in the middle of the relevant memory cell of mobile terminal device.
S.smil file and 8712df01.asc file all are placed in the memory cell to be stored accordingly.
The transmission of embodiment five, IM data
Analyze the IM data, the total information field that the IM data need be preserved mainly comprises:
Sender URI (universal resource identifier, Universal Resource Identifier) is field (From), mainly is meant the URI of the transmit leg of IM.
Addressee URI (To) field mainly is meant IM recipient's URI.
Data (Data) field mainly is meant the main contents of IM, may be literal, also can be binary content.
Transmitting time (Time) field mainly is meant the transmitting time of IM.
Content type (Content-Type) field mainly is meant the content type of IM.
Medium type (Type) field mainly is meant the type of IM.
The UA field mainly is meant the information of the UserAgent of IM
Above-mentioned total field can be used as specified entry, need transmit in intermediate file, and the form of intermediate file can adopt XML mode etc.
Mode one, XML mode
A kind of form that may adopt of DTD is for example:
<？xml?version＝″1.0″encoding＝″UTF-8″？>
<！ELEMENT?IM_Bakup(From，To，Subject，Date，Time，Message_Type，UA)>
<！ELEMENT?From(#PCDATA)>
<！ELEMENT?To(#PCDATA)>
<！ELEMENT?Content-Type(#PCDATA)>
<！ELEMENT?Data(#PCDATA)>
<！ELEMENT?Time(#PCDATA)>
<！ELEMENT?Message-Type(#PCDATA)>
<！ELEMENT?UA(#PCDATA)>
Above DTD in the middle of, mainly stipulated the common relevant information format of IM in the middle of the different mobile terminal equipment, this comprising:
Sender's URI;
Addressee's URI;
The key data content of IM;
The time that IM sends;
The medium type of IM
Information such as the type of IM;
The information that is used for agency (User Agent) of IM format conversion unit.
The initial data of IM is stored in the memory cell with following logical form on mobile terminal device A:
A_From＝Alice@sample.com
A_To＝Bob@sample.com
A_Content_Type＝text/plain
A_Data＝How?Are?You？
A_Time＝Wed，07?Jun?2006?17:54:49?+0800
A_Type＝Received?IM
A_UA＝Microsoft?MSN?V?7.0
A_Squene＝001
A_Status＝Read
The intermediate file that forms the XML document form is for example:
<？xml?version＝″1.0″encoding＝″UTF-8″？>
<！DOCTYPE?IM_Bakup?xmls＝″http://www.sample.com/DTD/IM-Bakup.dtd″>
<IM_Bakup>
<From>”Alice@sample.com”</From>
<To>”Bob@sample.com”</To>
<Content-Type>”text/plain”</Content-Type>
<Date>How?Are?You？</Date>
<Time>Wed，07?Jun?2006?17:54:49?+080</Time>
<Type>Received?IM</Type>
<UA>”Microsoft?MSN?V?7.0”</UA>
</IM_Bakup>
Above-mentioned file is the document of an XML, and its document name may be IM_Bakup.xml.
Mobile terminal device B obtains intermediate file, and it is the document of the XML that generated of mobile terminal device A in fact that the native format converting unit is resolved.
Mobile terminal device B is used to be stored in the data on the local mobile terminal equipment:
B->IM->From＝Alice@sample.com
B->IM->To＝Bob@sample.com
B->IM->Content_Type＝text/plain
B->IM->Subject＝How?Are?You？
B->IM->Data＝How?Are?You？
B->IM->Time＝Wed，07?Jun?2006?17:54:49?+0800
B->IM->Type＝Received?IM
B->IM->UerAgent＝Microsoft?MSN?V?7.0
B->IM->Squene＝001
B->IM->Status＝Read
By above-mentioned mode, just finished the transmission of IM data in the middle of different mobile terminal devices.
Wherein, the content of IM can be to adopt the mode of this DTD, also can adopt the mode that the IM data is packaged into fully packet.
Mode two, XML encapsulation IM message initial data
DTD can be referring to following mode:
<？xml?version＝″1.0″encoding＝″UTF-8″？>
<！ELEMENT?IM_Message_Bakup(Message_Type，Sequence，Data)>
＜!--be used for DTD--that IM message is backed up 〉
<！ELEMENT?Message_Type(Send_IM？，Received_IM？，Draft_IM？)>
<！ELEMENT?Send_IM(#PCDATA)>
＜!--the IM--in the local transmission of storing of mobile terminal device of encapsulation 〉
<！ELEMENT?Received_IM(#PCDATA)>
＜!--the IM--in the local reception of storing of mobile terminal device of encapsulation 〉
<！ELEMENT?Draft_IM(#PCDATA)>
＜!--the rough draft IM--in the local storage of mobile terminal device of encapsulation 〉
<！ELEMENT?Sequence(#PCDATA)>
＜!--sequence number of the message that is transformed--〉
<！ELEMENT?Data(#PCDATA)>
＜!--data of encapsulation--〉in the local Push message of storing of mobile terminal device
The intermediate file that is transformed by format conversion unit is for example:
<？xml?version＝″1.0″encoding＝″UTF-8″？>
<！DOCTYPE IM_Message_Bakup
xmls＝″http://www.sample.com/DTD/IM-Bakup-Alternative.dtd″>
<Push_Message_Bakup>
<Message_Type>
<Received>1</Received>
</Message_Type>
<Sequence>001</Sequence>
<Data>01000011110101010000001111111101001111111111111111100001111111111111
11111111</Data>
</Push_Message_Bakup>
Wherein:
" 01,000,011,110,101,010,000,001,111,111,101,001,111,111,111,111,111,100,001 11111111111111111111 " are the binary file layout of SI part in the middle of mobile terminal device A of IM message in the middle of the embodiment.
Mobile terminal device B forms mobile terminal device B according to intermediate file and can discern and formats stored, and the result after it transforms is as follows:
B->IM->From＝Alice@sample.com
B->IM->To＝Bob@sample.com
B->IM->Content_Type＝text/plain
B->IM->Subject＝How?Are?You？
B->IM->Data＝How?Are?You？
B->IM->Time＝Wed，07?Jun?2006?17:54:49?+0800
B->IM->Type＝Received?IM
B->IM->UerAgent＝Microsoft?MSN?V?7.0
B->IM->Squene＝001
B->IM->Status＝Read
Embodiment six
The main purpose of present embodiment is to be to realize the seamless exchange of mobile terminal device related data between mobile terminal device.In the middle of the process of exchange, simple as much as possible in order to make whole system, can construct a unified intermediate file format, realize exchange and storage to all mobile terminal device data.In order to finish uniform data exchange, the form of the data that exchange between the being useful on mobile terminal device need be carried out unified regulation.These data have very big scope, such as, data such as SMS, Vcard, Vcalendar, Email, MMS, Picture.The prescribed manner of the main describing message of present embodiment (Message) data format, the processing of the data of other type and classes of messages data is similar fully.In the middle of the process that the data of classes of messages are unified to handle, the information field that needs to preserve mainly comprises:
The Message-Type field, the original data type sign is used for distinguishing different type of messages, such as, SMS, MMS, Email etc.(essential)
The Status field mainly is meant the state of Message.(optional)
The Squence field mainly refers to the sequence number of Message.
The Message field mainly is to be used for storing different Message types.
When adopting the XML mode, a kind of form that may adopt of the DTD of Message exchanges data.
<？xml?version＝″1.0″encoding＝″UTF-8″？>
<！ELEMENT?Message_Bakup(Message_Type*，Status*，Squence*，(SMS_Bakup|
Push_Message_Bakup|MMS_Bakup|Email_Bakup|IM_Message_Bakup))+>
<！ELEMENT?SMS_Bakup(SMS_Orignal_Address*，SMS_Destination_Address*，
SMS_Date+，SMS_TimeStamp+，SMS_Type+)>
＜!--form of the DTD of the backup of SMS--〉
<！ELEMENT?SMS_Orignal_Address(#PCDATA)>
＜!--mainly be meant the sender address of SMS.-->
<！ELEMENT?SMS_Destination_Address(#PCDATA)>
＜!--mainly be meant SMS recipient's address.-->
<！ELEMENT?SMS_Date(#PCDATA)>
＜!--mainly being meant the main contents of SMS, may be literal, also can be binary content.-->
<！ELEMENT?SMS_TimeStamp(#PCDATA)>
＜!--mainly be meant the temporal information of SMS.-->
<！ELEMENT?SMS_Type(SMS_MT？|SMS_MO？|SMS_Draft？|
SMS_Delivery_Report？)>
＜!--mainly be meant the type of SMS, mainly comprise 4 classes at present.-->
<！ELEMENT?SMS_MT(#PCDATA)>
＜!--SMS type that mobile terminal device receives--〉
<！ELEMENT?SMS_MO(#PCDATA)>
＜!--the SMS type that mobile terminal device sends.-->
<！ELEMENT?SMS_Draft(#PCDATA)>
＜!--the rough draft SMS type that write mobile terminal device this locality.-->
<！ELEMENT?SMS_Delivery_Report(#PCDATA)>
＜!--the Report Type that mobile terminal device receives about SMS.-->
<！ELEMENT?MMS_Bakup(MMS_MessageType+，MMS_Version+，MMS_Message_ID+，
MMS_Sender_address*，MMS_Content_type+，MMS_Recipient_address*，
MMS_Message_class*，MMS_Date_and_time+，MMS_Priority*，MMS_Subject*，MMS_State*，
MMS_Content*)>
<！ELEMENT?MMS_Message_Type(#PCDATA)>
＜!--with this message identifier is MM1_retrieve.RES.-->
<！ELEMENT?MMS_Version(#PCDATA)>
＜!--the version of sign MMSRelay/Server institute supporting interface.-->
<！ELEMENT?MMS_Messag_ID(#PCDATA)>
＜!--the message id of MM.-->
<！ELEMENT?MMS_Sender_address(#PCDATA)>
＜!--handled the address of the mobile terminal device of MM (that is, submitting or transmitted MM to) recently.If originators
Mobile terminal device has asked the recipient is hidden its address, and then its address can not offer the recipient.-->
<！ELEMENT?MMS_Content_type(#PCDATA)>
＜!--the content type of MM content.-->
<！ELEMENT?MMS_Recipient_address(#PCDATA)>
＜!--MM recipient's address.May there be a plurality of addresses.-->
<！ELEMENT?MMS_Message_class(#PCDATA)>
＜!--classification of message (for example, individual service, advertising service and information service)--〉
<！ELEMENT?MMS_Date_and_time(#PPCDATA)>
＜!--mobile terminal device is handled the time and date of (that is, submit to or transmit) MM recently.-->
<！ELEMENT?MMS_Priority(#PCDATA)>
＜!--the priority (importance) (if the originators mobile terminal device is specified) of message.-->
<！ELEMENT?MMS_Subject(#PCDATA)>
＜!--the title of whole multimedia message is (if the originators mobile terminal device of MM refers to
Fixed).-->
<！ELEMENT?MMS_State(#PCDATA)>
＜!--the MM state.Incoming MM may lack this state, persistent storage
There is this state in MM.-->
<！ELEMENT?MMS_Content(MMS_charset，MMS_Content-Transfer-Encoding，
MMS_Content-Location，MMS_Data)>
＜!--the content (the originators mobile terminal device by MM is specified) of Multimedia Message.-->
<！ELEMENT?MMS_charset(#PCDATA)>
<！ELEMENT?MMS_Content-Transfer-Encoding(#PCDATA)>
<！ELEMENT?MMS_Content-Location(#PCDATA)>
<！ELEMENT?MMS_Data(#PCDATA)>
<！ELEMENT?Push_Message_Bakup(Push_si？，Push_sl？)>
<！ELEMENT?Push_si(Push_indication，Push_info？)>
<！ELEMENT?Push_indication(#PCDATA)>
<！ATTLIST?Push_indication
Push_href％URI；#IMPLIED
Push_si-id?CDATA#IMPLIED
Push_created?％Datetime；#IMPLIED
Push_si-expires?％Datetime；#IMPLIED
Push_action(Push_signal-none|Push_signal-low|Push_signal-medium|
Push_signal-high|Push_delete)″Push_signal-medium″
>
<！ELEMENT?Push_info(Push_item+)>
<！ELEMENT?Push_item(#PCDATA)>
<！ATTLIST?Push_item
Push_class?NMTOKEN#REQUIRED
>
<！ELEMENT?Push_sl?EMPTY>
<！ATTLIST?Push_sl
Push_href％URI；#REQUIRED
Push_action(Push_execute-low|Push_execute-high|Push_cache)″Push_execute-low″
>
<！ENTITY％?Datetime″CDATA″>
<！ENTITY％?URI″CDATA″>
<！ELEMENT?Email_Bakup(Push_Return-Path？，Push_Delivered-To*，Push_Received*，
Push_Date+，Push_CC？，Push_BCC？，Push_Message-ID*，Push_From+，Push_Subject*，
Push_To+，Push_Reply-to*，Push_MIME-version+，Push_Content+)>
<！ELEMENT?Push_Content(Push_Content-type*，Push_charset*，Push_Data*，
Push_Name*，Push_Filename*，Push_Content-Transfer-Encoding*，Push_Content-Description*，
Push_Content-Disposition*，Push_Content-ID*，Push_Content-class*)>
<！ELEMENT?Push_Return-Path(#PCDATA)>
<！ELEMENT?Push_Delivered-To(#PCDATA)>
<！ELEMENT?Push_Received(#PCDATA)>
<！ELEMENT?Push_Date(#PCDATA)>
<！ELEMENT?Push_CC(#PCDATA)>
<！ELEMENT?Push_BCC(#PCDATA)>
<！ELEMENT?Push_Message-ID(#PCDATA)>
<！ELEMENT?Push_From(#PCDATA)>
<！ELEMENT?Push_Subject(#PCDATA)>
<！ELEMENT?Push_To(#PCDATA)>
<！ELEMENT?Push_Reply-to(#PCDATA)>
<！ELEMENT?Push_MIME-version(#PCDATA)>
<！ELEMENT?Push_Content-Transfer-Encoding(#PCDATA)>
<！ELEMENT?Push_Content-Description(#PCDATA)>
<！ELEMENT?Push_Content-Disposition(#PCDATA)>
<！ELEMENT?Push_Content-ID(#PCDATA)>
<！ELEMENT?Push_Content-type(#PCDATA)>
<！ELEMENT?Push_Content-class(#PCDATA)>
<！ELEMENT?Push_charset(#PCDATA)>
<！ELEMENT?Push_Data(#PCDATA)>
<！ELEMENT?Push_Name(#PCDATA)>
<！ELEMENT?Push_Filename(#PCDATA)>
<！ELEMENT?IM_Message_Bakup(IM_Message_Type，IM_Sequence，IM_Data)>
＜!--be used for DTD--that IM message is backed up 〉
<！ELEMENT?IM_Message_Type(IM_Send？，IM_Received？，IM_Draft？)>
<！ELEMENT?IM_Send(#PCDATA)>
＜!--the IM--in the local transmission of storing of mobile terminal device of encapsulation 〉
<！ELEMENT?IM_Received(#PCDATA)>
＜!--the IM--in the local reception of storing of mobile terminal device of encapsulation 〉
<！ELEMENT?IM_Draft(#PCDATA)>
＜!--the rough draft IM--in the local storage of mobile terminal device of encapsulation 〉
<！ELEMENT?IM_Sequence(#PCDATA)>
＜!--sequence number of the message that is transformed--〉
<！ELEMENT?IM_Data(#PCDATA)>
＜!--data of encapsulation--〉in the local Push message of storing of mobile terminal device
Above DTD in the middle of, mainly stipulated the common relevant information format of IM in the middle of the different mobile terminal equipment, this comprising:
The Message-Type field mainly is to be used for distinguishing different message, such as, SMS, MMS, Email etc.
The Status field mainly is meant the state of Message.
The Squence field mainly refers to the sequence number of Message.
The Message field mainly is to be used for storing different Message types.
This example is one all message is merged embodiment in the middle of an XML.Its method that adopts is more similar with the method for employing in the middle of the embodiment of front, and the mode that data format transforms can be finished with reference to the DTD document of above-mentioned XML, and concrete implementation procedure is just tired no longer here have been stated.
A mode in addition is exactly with the binary system of different Message or the document behind a package Data part as Message_Bakup.Concrete DTD can be with reference to as follows:
<？xml?version＝″1.0″encoding＝″UTF-8″？>
<！ELEMENT?Message_Bakup(Message_Type*，Status*，Squence*，Data+>
<！ELEMENT?Message_Type(#PCDATA)>
<！ELEMENT?Status(#PCDATA)>
<！ELEMENT?Squence(#PCDATA)>
<！ELEMENT?Data(#PCDATA)>
Wherein the Data data division can encapsulate the data of other message.
Concrete mode can be with reference to the implementation of foregoing embodiment.
The initial data of embodiment seven, transmission Vcard and Vcalendar
Wherein: the specified entry of Vcard comprises: name (N), Mobile Directory Number (TEL; Cell), office telephone number (TEL; Work), home number (TEL; Home), fixed telephone number (TEL), fax number (TEL; FAX), Email (EMAIL) address.In addition, can also comprise clauses and subclauses such as home address, mailing address.
The specified entry of Vcalendar comprises at least: zero-time (Start Time) information, concluding time (Stop Time) information, description (Description) information, cyclical patterns (Recur Type) incident, content (Body), alerting pattern (Notify Type), ring mode (Ringer Type) and duration (Duration) etc.
Be in the consideration of the situation of present realization, when utilizing XML that Vcard and Vcalendar are encapsulated, mainly all the elements of the specified entry of Vcard and Vcalendar Data unit as XML is encapsulated, thereby realize function with XML packaging V card and Vcalendar.When the mode packaging V card of XML and the data field of Vcalendar specified entry, the description of DTD can be as follows:
<？xml?version＝″1.0″encoding＝″UTF-8″？>
<！ELEMENT?Vcard_Bakup(Squence*，Data+>
<！ELEMENT?Squence(#PCDATA)>
<！ELEMENT?Data(#PCDATA)>
The implementation of Vcalendar is as follows:
<？xml?version＝″1.0″encoding＝″UTF-8″？>
<！ELEMENT?Vcard_Bakup(Squence*，Data+>
<！ELEMENT?Squence(#PCDATA)>
<！ELEMENT?Data(#PCDATA)>
In the middle of above-mentioned scheme, each Vcard and each Vcalendar are the elements (Element) of an XML, a plurality of Vcard and a plurality of Vcalendar can be encapsulated in the middle of the document of an XML, help large-scale exchanges data like this, avoid the inconvenience that is brought when operating at single Vcard or Vcalendar.Be that the mode of Vcard is carried out a simple XML explanation below:
<？xml?version＝″1.0″encoding＝″UTF-8″？>
<！DOCTYPE?Vcard_Bakup?xmls＝″http://www.sample.com/DTD/Vcard-Bakup.dtd″>
<Vcard_Bakup>
<Squence>001</Squence>
<Data>”BEGIN:VCARD
VERSION:2.1
N:Marks；Bennett
FN:Bennett?Marks
ORG:Nokia；Standardization?&?Industry?Relations
TITLE:Senior?Architect
TEL；WORK；VOICE:+1(781)993-3932
TEL；HOME；VOICE:+1(978)371-0970
TEL；CELL；VOICE:+1(781)308-6556
TEL；WORK；FAX:+1(781)993-1822
ADR；WORK:；；5?Wayside?Road；Burlingyon；MA；01803；United?States?of
America
LABEL；WORK；ENCODING＝QUOTED-PRINTABLE:5 Wayside
Road＝0D＝0ABurlington，MA01803＝0D＝0AUnited?States?of?America
ADR；HOME:；；439?Bedford?Rd.；Carlisle；Mass.；01741；United?States?of?America
LABEL；HOME；ENCODING＝QUOTED-PRINTABLE:439 Bedford
Rd.＝0D＝0ACarlisle，Mass.01741＝0D＝0AUnited?States?of?America
URL；WORK:http://www.nokia.com
EMAIL；PREF；INTERNET:Bennett.Marks@nokia.com
REV:20070629T071729Z
END:VCARD”
</Data>
</Vcard_Bakup>
Be that the mode of Vcalendar is carried out a simple XML explanation below:
<？xml?version＝″1.0″encoding＝″UTF-8″？>
<！DOCTYPE Vcalendar_Bakup
xmls＝″http://www.sample.com/DTD/Vcalendar-Bakup.dtd″>
<Vcalendar_Bakup>
<Squence>001</Squence>
<Data>”
BEGIN:VCALENDAR
PRODID:-//Microsoft?Corporation//Outlook?11.0?MIMEDIR//EN
VERSION:1.0
BEGIN:VEVENT
DTSTART:20070703T000000Z
DTEND:20070703T020000Z
LOCATION；ENCODING＝QUOTED-PRINTABLE:A110?Room
UID:040000008200E00074C5B7101A82E0080000000070E833055BBDC7010
000000000000000100
000009E0D91D28D7A8E4B8C9EF47F7D8AEAA5
DESCRIPTION；ENCODING＝QUOTED-PRINTABLE:FYI＝0D＝0A
SUMMARY；ENCODING＝QUOTED-PRINTABLE:Meeting
PRIORITY:3
END:VEVENT
END:VCALENDAR”
</Data>
</Vcalenar_Bakup>
As seen, the technical scheme that the embodiment of the invention provides utilizes format conversion unit initial data to be converted to the intermediate file of prescribed form, the specified entry and the corresponding data field that comprise initial data in the intermediate file of prescribed form, prescribed form according to intermediate file, format conversion unit can also read data field wherein from middle file, thereby generates the target data of initial data correspondence.Because the specified entry that comprises in the intermediate file of prescribed form is the total information field that initial data is stored on various mobile terminal devices, so intermediate file can transmit between each mobile terminal device, reaches the purpose of transfer of data.Simultaneously, intermediate file can also improve the reliability of initial data as original backup along certificate.The embodiment of the invention also provides the implementation when on third party device converting unit being set.
Obviously, those skilled in the art can carry out various changes and modification to the embodiment of the invention and not break away from the spirit and scope of the present invention.Like this, if of the present invention these are revised and modification belongs within the scope of claim of the present invention and equivalent technologies thereof, then the present invention also is intended to comprise these changes and modification interior.
Claims (14)
1. the conversion method of mobile terminal device data is characterized in that, comprising:
The specified entry that first mobile terminal device comprises in the intermediate file of form is according to the rules obtained the data field of each specified entry correspondence from the initial data that this terminal equipment is preserved; Wherein, specified entry is to realize the total clauses and subclauses of every type of initial data of the transfer of data between the various mobile terminal devices;
Set the intermediate file of prescribed form for every type initial data, generate the intermediate file of form up to specification, comprise at least one specified entry in the described intermediate file, the data field of each specified entry correspondence, and the identification information that is used to distinguish different original data types;
First mobile terminal device sends to second mobile terminal device with described intermediate file;
Second mobile terminal device is according to the prescribed form of described intermediate file, from described intermediate file, obtain the data field of each specified entry correspondence, and the data field of each specified entry correspondence is saved as target data according to the form of the second mobile terminal device support.
2. the method for claim 1 is characterized in that, the generation method of described intermediate file comprises:
Resolve the prescribed form of corresponding described original data type, determine each specified entry that comprises in the described prescribed form;
According to each specified entry that comprises in the described prescribed form, from described initial data, obtain the data field of each specified entry correspondence respectively;
Generate the intermediate file of described form up to specification.
3. the method for claim 1 is characterized in that, the method for obtaining the data field of each specified entry correspondence from described intermediate file comprises:
Resolve the prescribed form of corresponding described original data type, determine each specified entry that comprises in the described prescribed form;
According to each specified entry that comprises in the described prescribed form, from described intermediate file, obtain the data field of each specified entry correspondence.
4. the method for claim 1 is characterized in that, it is one of following that described original data type comprises at least: classes of messages data, phone directory class data, schedule class data or mail class data.
5. method as claimed in claim 4 is characterized in that:
Specified entry in the prescribed form of described phone directory class data comprises at least: name, Mobile Directory Number, office telephone number, home number, fixed telephone number, fax number and e-mail address;
Specified entry in the prescribed form of described schedule class data comprises at least: start time information, concluding time information, descriptor, cyclical patterns incident, content, alerting pattern, ring mode and duration; And/or
Specified entry in the prescribed form of described mail class data comprises at least: date, sender, theme, recipient, return address, multipurpose internet mail expansion MIME version, reverse-path, transmission information, reception information, the address of making a copy for, close address, message identifier, content delivery coded system information, content description, contents attribute, content identification, content type, content rating, character set, content-data, annex name, the attachment files name sent.
6. method as claimed in claim 4 is characterized in that, described classes of messages data comprise short message class data, PUSH message class data, instant message class data and Multimedia Message class data.
7. method as claimed in claim 6 is characterized in that:
Specified entry in the prescribed form of described short message class data comprises at least: source address, destination address, data, temporal information and type;
Specified entry in the prescribed form of described PUSH message class data comprises at least: every indication information of service indication message, every content information of service downloading message;
Specified entry in the prescribed form of described instant message class data comprises at least: sender's universal resource identifier URI, addressee URI, data, transmitting time, content type, medium type; And/or
Specified entry in the prescribed form of described Multimedia Message class data comprises at least: type of message, Multimedia Message version information, message identifier, sender address, content type, recipient address, message grade, Time of Day, priority, theme, message status, content.
8. the method for claim 1 is characterized in that, described intermediate file type comprises txt file or XML file.
9. the converting system of mobile terminal device data is characterized in that, comprising:
First format conversion unit is used to generate the intermediate file of form up to specification, comprises at least one specified entry in the described intermediate file, the data field of each specified entry correspondence, and the identification information that is used to distinguish different original data types; Wherein, specified entry is to realize the total clauses and subclauses of every type of initial data of the transfer of data between the various mobile terminal devices, and the data field of described each specified entry correspondence is to obtain from the initial data that first mobile terminal device is preserved;
Second format conversion unit, be used for prescribed form according to the intermediate file of described first format conversion unit generation, from described intermediate file, obtain the data field of each specified entry correspondence, and the data field of each specified entry correspondence is saved as target data according to the form of the second mobile terminal device support;
Described first format conversion unit is arranged on first mobile terminal device;
Described second format conversion unit is arranged on second mobile terminal device;
Described first mobile terminal device and the second mobile terminal device wireless connections.
10. a mobile terminal device is characterized in that, comprising:
The transfer instruction receiving element is used to receive data transfer instruction;
Original data storage unit, the first storage control unit and first format conversion unit, the original data transmissions instruction that described first format conversion unit receives according to the transfer instruction receiving element, from the original data storage unit, obtain the data field of specified entry correspondence by the described first storage control unit, and generate the intermediate file of form up to specification, comprise at least one specified entry in the described intermediate file, the data field of each specified entry correspondence, and the identification information that is used to distinguish different original data types; Wherein, specified entry is to realize the total clauses and subclauses of every type of initial data of the transfer of data between the various mobile terminal devices;
The intermediate file transmitting element is used for described intermediate file is sent to other mobile terminal device.
11. equipment as claimed in claim 10 is characterized in that, also comprises:
The intermediate file memory cell is used to store the intermediate file that described first format conversion unit generates.
12. equipment as claimed in claim 11 is characterized in that, also comprises:
The intermediate file receiving element is used to receive the intermediate file that other mobile terminal device sends;
Second format conversion unit and target data memory cell, obtain the data field of each specified entry correspondence in the intermediate file of preserving intermediate file that described second format conversion unit receives from middle file receiving element and/or the described intermediate file memory cell, and by the form of the described first storage control unit according to the mobile terminal device support, the data field with each specified entry correspondence in described target data memory cell saves as target data.
13. equipment as claimed in claim 11 is characterized in that:
Described first format conversion unit and second format conversion unit merge setting; And/or
Described intermediate file transmitting element and intermediate file receiving element merge setting.
14. a mobile terminal device is characterized in that, comprising:
The intermediate file receiving element is used to receive the intermediate file that other mobile terminal device sends, and comprises at least one specified entry in the described intermediate file, the data field of each specified entry correspondence, and the identification information that is used to distinguish different original data types; Wherein, specified entry is to realize the total clauses and subclauses of every type of initial data of the transfer of data between the various mobile terminal devices, and the data field of described each specified entry correspondence is to obtain from the initial data that described other mobile terminal device is preserved;
Second format conversion unit, the second storage control unit and target data memory cell, described second format conversion unit is obtained the data field of each specified entry correspondence from the intermediate file that middle file receiving element receives, and by the form of the described second storage control unit according to the mobile terminal device support, the data field with each specified entry correspondence in described target data memory cell saves as target data.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2007101229751A CN101247589B (en) | 2007-07-04 | 2007-07-04 | Mobile terminal data conversion/backup method, device and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2007101229751A CN101247589B (en) | 2007-07-04 | 2007-07-04 | Mobile terminal data conversion/backup method, device and system |
Related Child Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201010277057.8A Division CN101917520B (en) | 2007-07-04 | 2007-07-04 | Conversion/backup method, equipment and system for mobile terminal data |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN101247589A CN101247589A (en) | 2008-08-20 |
| CN101247589B true CN101247589B (en) | 2010-09-08 |
Family
ID=39947737
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN2007101229751A Active CN101247589B (en) | 2007-07-04 | 2007-07-04 | Mobile terminal data conversion/backup method, device and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN101247589B (en) |
Families Citing this family (24)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101799890B (en) * | 2009-02-06 | 2012-07-18 | 北京数政科技有限公司 | Certificate data processing method and system |
| CN101795237A (en) * | 2010-03-25 | 2010-08-04 | 国网电力科学研究院 | Workflow integration method and device based on data exchange |
| CN101853184A (en) * | 2010-05-21 | 2010-10-06 | 中兴通讯股份有限公司 | Management method and device for application program and terminal |
| CN102480335B (en) * | 2010-11-30 | 2015-08-05 | 金蝶软件（中国）有限公司 | A kind of sending method of business datum and system |
| CN102665179A (en) * | 2012-05-03 | 2012-09-12 | 广东欧珀移动通信有限公司 | Method for backing up and recovering MMS (multimedia messaging service) of mobile phone |
| CN103853775A (en) * | 2012-12-04 | 2014-06-11 | 中山大学深圳研究院 | Method for converting data storage format based on multimedia data |
| CN103412765A (en) * | 2013-09-04 | 2013-11-27 | 广东全通教育股份有限公司 | Method for realizing universality of data exporting interface |
| CN104980904A (en) * | 2014-04-11 | 2015-10-14 | 华为技术有限公司 | Address list information transmission method, device and system |
| CN105187360A (en) * | 2014-06-17 | 2015-12-23 | 中兴通讯股份有限公司 | Document conference sharing method and device |
| CN104050059A (en) * | 2014-06-30 | 2014-09-17 | 珠海市君天电子科技有限公司 | Method and system for data backup and recovery |
| CN104243561B (en) * | 2014-09-02 | 2018-08-10 | 联想(北京)有限公司 | A kind of electronic equipment, information processing method and information transmission system |
| JP6686306B2 (en) * | 2015-02-25 | 2020-04-22 | ヤマハ株式会社 | Information providing apparatus and information providing method |
| CN106708491A (en) * | 2015-11-17 | 2017-05-24 | 北京国双科技有限公司 | Html-format mail generation method and device |
| CN106909570B (en) * | 2015-12-23 | 2020-12-15 | 创新先进技术有限公司 | Data conversion method and device |
| CN106169988B (en) * | 2016-02-26 | 2019-10-15 | 北京元心科技有限公司 | The method of data is transmitted in cruising inspection system |
| CN105975624B (en) * | 2016-05-27 | 2019-07-30 | 苏州佳世达电通有限公司 | A kind of data transmission method, equipment and system |
| CN106209575B (en) * | 2016-06-23 | 2019-09-24 | 厦门黑镜科技有限公司 | Method for sending information, acquisition methods, device and interface system |
| CN106649428A (en) * | 2016-08-09 | 2017-05-10 | 广州视睿电子科技有限公司 | Analyzing method and apparatus of storage files |
| CN106446240A (en) * | 2016-10-11 | 2017-02-22 | 北京小米移动软件有限公司 | Note format switching method and device |
| CN106357812A (en) * | 2016-10-26 | 2017-01-25 | 京东方科技集团股份有限公司 | Method for transmitting data among Android devices, data transmission device and Bluetooth device |
| CN107643926A (en) * | 2017-09-29 | 2018-01-30 | 北京酷我科技有限公司 | A kind of object type turns database type method |
| CN108167023A (en) * | 2017-12-27 | 2018-06-15 | 天地（常州）自动化股份有限公司 | Data organization and method for uploading in a kind of coal mine safety monitoring system polling period |
| CN108959438A (en) * | 2018-06-12 | 2018-12-07 | 北京杰控科技有限公司 | A kind of collecting method and system, a kind of server |
| CN110248232B (en) * | 2019-05-29 | 2021-08-03 | 广州视琨电子科技有限公司 | Data pushing method and device, storage medium and processor |
Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1787665A (en) * | 2004-12-08 | 2006-06-14 | 华为技术有限公司 | Method and apparatus for preventing personal data losing in mobile terminal |
-
2007
- 2007-07-04 CN CN2007101229751A patent/CN101247589B/en active Active
Patent Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1787665A (en) * | 2004-12-08 | 2006-06-14 | 华为技术有限公司 | Method and apparatus for preventing personal data losing in mobile terminal |
Also Published As
| Publication number | Publication date |
|---|---|
| CN101247589A (en) | 2008-08-20 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN101247589B (en) | Mobile terminal data conversion/backup method, device and system | |
| CN101917520B (en) | Conversion/backup method, equipment and system for mobile terminal data | |
| CN101330662B (en) | Business content information inquiry method, system and service provider platform | |
| CN101212721B (en) | Information processing method, system, and information consolidation device | |
| CN101098313B (en) | Mail transmitting method and system | |
| US7664824B2 (en) | System for transmission/reception of e-mail with attached files | |
| CN101366016B (en) | Schema hierarchy for electronic messages | |
| US20060235931A1 (en) | System for two-way exchange of personal data over mobile telephone networks | |
| CN101640718B (en) | Mobile communication device having fast replying function of advertising short message and method | |
| US20030014492A1 (en) | System and method for communicating messages between a host computer and a designated device | |
| US20080294729A1 (en) | Email object for open mobile alliance data synchronization usage | |
| CN101763566A (en) | Contact information management system and method thereof | |
| US20020052922A1 (en) | Information providing system and apparatus and methods therefor | |
| CN100433867C (en) | Method and apparatus for preventing personal data losing in mobile terminal | |
| CN101478730B (en) | Data exchanging method, system and device | |
| CN102014345B (en) | Message conversion method, system and equipment | |
| CN101193337A (en) | MMS coding device | |
| US6690775B2 (en) | Delivery-information management method and delivery-information management program | |
| US8626840B2 (en) | Method and system for generating a referencing secondary electronic mail message from a primary electronic mail message | |
| CN101651869B (en) | Mobile communication device and advertisement short message service reply method thereof | |
| CN1971595B (en) | System and method for merging e-mails | |
| CN101193338A (en) | MMS coding and transmission system | |
| CN1953423A (en) | A method to forward the designated information at paper media via operating the mobile terminal | |
| CN102137341B (en) | Method, system and equipment for realizing interaction based on multimedia message (MMS) | |
| KR20000036881A (en) | Methodology of managing multimedia e-mail service using XML |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant |