CN101202953B - Method and system of shortcut reversion - Google Patents
Method and system of shortcut reversion Download PDFInfo
- Publication number
- CN101202953B CN101202953B CN2006101680120A CN200610168012A CN101202953B CN 101202953 B CN101202953 B CN 101202953B CN 2006101680120 A CN2006101680120 A CN 2006101680120A CN 200610168012 A CN200610168012 A CN 200610168012A CN 101202953 B CN101202953 B CN 101202953B
- Authority
- CN
- China
- Prior art keywords
- message
- quickly revert
- server
- client
- quickly
- 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
Landscapes
- Information Transfer Between Computers (AREA)
- Telephonic Communication Services (AREA)
Abstract
The invention discloses a rapid recovery method which includes that a rapid recovery message is set in a rapid recovery QA server; after a client end sends a message acquisition request to the QA server, the QA server returns the rapid recovery message to the client end according to the received message acquisition request, and the client end chooses the pre-sent rapid recovery message from the returned rapid recovery messages and sends the chosen message to the receiving end. By the invention, users can use the same rapid recovery message at different terminals. The invention also discloses a rapid recovery system, a rapid recovery server and a client end to ensure that the users can use the same rapid recovery message at different terminals and avoid that the users carry out the same operations at different terminals, such as increasing or deleting the rapid recovery messages, thus reducing the complexity degree of the operation.
Description
Technical field
The present invention relates to the messaging service carried out on mobile communications network and Ying Te (Internet) network, the method, system, the quickly revert server and client side that are specifically related to realize quickly revert.
Background technology
At present, on mobile communications network, Internet network, all carry out messaging service is arranged.Mobile communications network generally comprises second generation mobile communication system (2G) network, 3-G (Generation Three mobile communication system) (3G) network, 2G to the 2.5G of 3G transition network, and multimedia subsystem etc.
Messaging service is that the individual is to individual, individual classes of messages data service to group.For example the short message between the mobile phone is mutual, and the instant message between last each user terminal of Internet is mutual etc.In message interaction process, have some message contents and often be used.If all will import these message commonly used at every turn, make that obviously operation is easy inadequately.
The short message service that realizes with the short message communication system is an example, in existing short-message system, user terminal provides the function of storage message commonly used, and the user can set in advance some oneself message commonly used at user terminal, be called quickly revert (QA, Quick Answer) message.The user is editor during short message, can directly select the quickly revert message that sets in advance, sends as content of short message.Set up quickly revert, and adopt quickly revert message to be called quickly revert as the operation of message content.Reduced user's input like this, provide convenience for the user uses message commonly used.
But in above-mentioned existing message communication system, the set quickly revert message of user is stored in the terminal, so the user can't be convenient to use the identical quickly revert message that belongs to this user on different terminals.User's quickly revert message on a terminal has been carried out the operation that increases or delete, if this user wishes to use its up-to-date quickly revert message of upgrading on other terminal, then need on other terminal, carry out once identical increase or deletion action, operating process repetition, loaded down with trivial details again.
Summary of the invention
In view of this, first purpose of the embodiment of the invention is to provide a kind of quickly revert method, makes the user use identical quickly revert message at different terminals.
Be first aspect that achieves the above object, the invention provides a kind of quickly revert method, this method comprises:
In quickly revert QA server, quickly revert message is set;
Client is initiated message to the QA server and is obtained request;
The QA server obtains request according to described message, returns quickly revert message to this client;
Client is chosen the quickly revert message of pre-transmission from the quickly revert message of returning, set up the session Session of described client to receiving terminal, adopts message session trunk protocol MSRP SEND to send selected quickly revert message to receiving terminal.
Compared with prior art, the method of realization quickly revert provided by the present invention with the quickly revert message stores on server, when the user needs quickly revert, can obtain this user's quickly revert message from server, and be not to obtain quickly revert message from terminal in the prior art.Because quickly revert message is to be stored on the server, even the user has upgraded quickly revert message on a terminal, this user still can not carry out under the situation of repetitive operation, obtains the up-to-date quickly revert message of its renewal from server by other terminal.Therefore realized that the user can be convenient to use identical quickly revert message on different terminals.
Description of drawings
Fig. 1 is the method flow diagram of embodiment of the invention quickly revert method.
Fig. 2 is the composition frame chart of embodiment of the invention quickly revert system.
Fig. 3 is the composition frame chart of first preferred embodiment of embodiment of the invention quickly revert system.
Fig. 4 is first kind of method flow diagram of realizing the quickly revert method of the present invention's first preferred embodiment.
Fig. 5 is second kind of method flow diagram of realizing the quickly revert method of the present invention's first preferred embodiment.
Fig. 6 realizes the method flow diagram that quickly revert message is obtained for the embodiment of the invention adopts XCAP.
Fig. 7 realizes the method flow diagram of quickly revert message establishing for the embodiment of the invention adopts XCAP.
Fig. 8 realizes the method flow diagram of quickly revert message modification for the embodiment of the invention adopts XCAP.
Fig. 9 realizes the method flow diagram of quickly revert message deletion for the embodiment of the invention adopts XCAP.
Figure 10 is the composition frame chart of embodiment of the invention quickly revert system second preferred embodiment.
Figure 11 is first kind of method flow diagram of realizing the quickly revert method of the present invention's second preferred embodiment.
Figure 12 is second kind of method flow diagram of realizing the quickly revert method of the present invention's second preferred embodiment.
Figure 13 realizes the method flow diagram that quickly revert message is obtained for the embodiment of the invention adopts SIP.
Figure 14 realizes the method flow diagram of quickly revert message establishing for the embodiment of the invention adopts SIP.
Figure 15 realizes the method flow diagram of quickly revert message modification for the embodiment of the invention adopts SIP.
Figure 16 realizes the method flow diagram of quickly revert message deletion for the embodiment of the invention adopts SIP.
Embodiment
For making the purpose, technical solutions and advantages of the present invention clearer, below in conjunction with embodiment and accompanying drawing, the present invention is described in more detail.
The core concept of the embodiment of the invention is for being provided with quickly revert message in advance in the QA server, when client after the QA server is initiated message and is obtained request, the QA server obtains request according to this message, returns quickly revert message.Client is selected the pre-quickly revert message that sends from the quickly revert message of returning, and sends to receiving terminal.
The QA server is a resource management server of preserving quickly revert message.In instant message communication system, this QA server can adopt the server of realizing instant messaging to realize.In the short message communication system, this QA server can adopt the server of realizing short message service to realize.With the message system based on initial session protocol/instant message and on-site support expansion session protocol (SIP/SIMPLE) is example, this QA server can adopt instant message extension tag Language Document management (IM XDM) server to realize, also can adopt instant message initial session protocol (IM SIP) server to realize.The QA server also can be used as a module and is arranged on separately in the IM server of SIP/SIMPLE message system, perhaps is arranged on separately in the SIP/SIMPLE system as a server, as long as realize the resource relevant treatment and the management of quickly revert message.
The quickly revert message of storing in the QA server can be stored respectively according to different user, helps different user and only obtain one's own quickly revert message when obtaining quickly revert message.Also all quickly revert message can be regardless of user's storage.
The invention described above embodiment scheme is applicable to various short-message systems and instant message (IM) system in mobile communications network and the Internet network.Its principle that realizes quickly revert is identical.Below in mobile communications network, to use the embodiment of the invention to realize that quickly revert describes as example.Wherein, quickly revert message is short message, and stores respectively according to different user in the QA server.
Based on above-mentioned core concept, Fig. 1 shows the method flow diagram that the embodiment of the invention realizes the quickly revert method.As shown in Figure 1, this method specifically may further comprise the steps:
Step 101, the user creates this user's quickly revert message on the QA server.
In this step, the user can add quickly revert message by repeatedly creating.
Step 102, the user initiates message by client to the QA server and obtains request.
In this step, the message request of obtaining that client is initiated can be that initiatively to obtain also can be passive obtaining.Initiatively obtaining is user need upgrade local quickly revert message the time, under the control of user command, initiates message to the QA server and obtains request.Passive obtaining is that client is all obtained request to QA server initiation message when the user need use quickly revert message at every turn, guarantees that the quickly revert message of using is up-to-date.Perhaps client can periodically be initiated message to the QA server and obtain request.
Step 103, the QA server obtains request according to the message that client is sent, and returns this user's quickly revert message to client.
The quickly revert message of being obtained can be preserved or do not preserved to client after receiving the quickly revert message that the QA server returns.If preserved after can directly use the quickly revert message of preserving on the client, if do not preserve then when needing to carry out quickly revert, at every turn all to QA server application quickly revert message.
Step 104, the user chooses required quickly revert message and sends to receiving terminal by client from the quickly revert message of returning.
In this step, the send mode of quickly revert message has two kinds.First kind is that true content with quickly revert message is included in the message body and sends; Second kind is the message identifier (ID) that only sends quickly revert message between transmitting terminal and transmitting terminal attribution server, the transmitting terminal attribution server is received the particular content that obtains quickly revert message behind the message id again from the QA server, and the message body that comprises quickly revert message particular content is sent to receiving terminal.Adopt to send the mode of message id, can effectively reduce the offered load between transmitting terminal and the transmitting terminal server, improve the efficient when sending big quickly revert message greatly.
The quickly revert message of QA server stores can comprise message id and message content (Text).Message id is the unique identification of a quickly revert message.Message content is the particular content of quickly revert message.Quickly revert message can also comprise type of message (Type) and message semantic definition attribute informations such as (Description).Description can be used for describing the bigger quickly revert message of some volume ratios, be equivalent to keyword, the user can not browse quickly revert message particular content, and select required quickly revert message according to the Description attribute when client is used quickly revert message like this.Text is the particular content of quickly revert message.But for some Multimedia Messages, because the message volume is bigger, so only stores the message linkage of concrete quickly revert message in the Text attribute, as uniform resource address (URL).
The embodiment of the invention can also realize the management to quickly revert message on the QA server.Client sends management information to the QA server, the QA server manages operation according to this management information to each user's quickly revert message of its storage, return management processing response message to client again, client is upgraded local quickly revert message according to this management processing response message then.Bookkeeping comprises interpolation, modification and the deletion to quickly revert message on the QA server.
A, when management information is establishment information, establishment information comprises the new quickly revert message that the user creates.This new quickly revert message does not comprise message id, and message id is that the QA server is the quickly revert message establishing.
After client sent to the QA server with new quickly revert message, the QA server was new quickly revert message establishing message id, again message id is returned to client.Client can be preserved the message content of this message id and new quickly revert message together.Message id is included in the management processing response message, and expression is simultaneously created successfully.
When repeatedly creating quickly revert message, the message that the QA server returns has time-delay, therefore confusion may take place in the corresponding relation of the message content created of the message id that returns of QA server and client, therefore in the message that the QA server returns, can carry the message content and the message id of new quickly revert message simultaneously.
B, when management information is modification information, modification information comprises message content and the message id of revising back quickly revert message.
Message content and message id that client will be revised back quickly revert message send to the QA server, and the quickly revert message of its storage of QA server modifications is returned management processing response message to client again.When the management processing response message represents to be modified as merit, client is upgraded local quickly revert message.
C, when management information is deletion information, deletion information comprises the message id of pre-deletion quickly revert message.
The message id that client will be deleted quickly revert message in advance sends to the QA server, and the QA server is deleted the quickly revert message of this message id correspondence, and returns management processing response message.When the management processing response message is represented to delete successfully, upgrade local quickly revert message by client.
Be to realize the quickly revert method that the embodiment of the invention provides, the embodiment of the invention also provides a kind of quickly revert system.Fig. 2 shows the composition frame chart of embodiment of the invention quickly revert system.Referring to Fig. 2, this quickly revert system comprises client and QA server.
Wherein, client is used for obtaining request to QA server initiation user's message; Receive the quickly revert message that the QA server returns.Afterwards, the quickly revert message of the pre-transmission that client is selected from the quickly revert message of returning, and send to receiving terminal.
The QA server is stored each user's quickly revert message, is used for obtaining request according to user's message, returns this user's quickly revert message to client.
In order to realize the management to each user's of QA server stores quickly revert message, the management information that the QA server also will be sent according to client manages operation to the quickly revert message of its storage, and returns management processing response message.Client is upgraded local quickly revert message according to this management processing response message.
In mobile communications network, the general employing based on the message system of SIP/SIMPLE realized instant messaging.In message system, can adopt extension tag language configuration access agreement (XCAP) or session initiation protocol (SIP) to realize obtaining, create, revise or deleting of quickly revert message based on SIP/SIMPLE.In the transmission of specific implementation message with when receiving, according to the message transmission protocol difference that adopts, the process that message sends and receives difference slightly to some extent.Below lift preferred embodiment, adopt the specific implementation of different agreement to be illustrated to the embodiment of the invention respectively.
First preferred embodiment
In message system, can adopt XCAP or SIP to realize obtaining or managing of quickly revert message based on SIP/SIMPLE.In the present embodiment, the obtaining, create, revise or delete and all adopt XCAP of quickly revert message, the management information that adopts this mode to send can adopt orders such as the defined GET of XCAP, PUT and DELETE, the equipment that receives such order and complete successfully associative operation returns HTTP 200OK response, can comprise the concrete information content in this response.
Fig. 3 is the composition frame chart of quickly revert of the present invention system first preferred embodiment.As shown in Figure 3, this system comprises: extension tag Language Document management (XDM) client 310 and IM XDM server 300.
Wherein, XDM client 310 is used for request of obtaining to Client-initiated message or management information are sent to IM XDM server 300, receives all quickly revert message or the management processing response messages of this user that IM XDM server 300 returns.After the quickly revert message that receives this user that IM XDM server returns, the XDM client is therefrom chosen one, sends to receiving terminal.Message request of obtaining and management information that XDM client 310 sends all are the form of XCAP request.In the present embodiment, XDM client 310 is a module in the user terminal as the client in the quickly revert system.
Wherein, QA acquisition module 313, the message that is used for initiating to IM XDM server 300 users is obtained request, and receives all quickly revert message of this user that IM XDM server 300 returns, and sends QA processing module 311 to.
If XDM client 310 is not all to obtain quickly revert message from server when carrying out quickly revert at every turn, then XDM client 310 also comprises QA memory module 312.This QA memory module 312 links to each other with QA processing module 311, is used to store the user's who uses this XDM client quickly revert message.When QA processing module 311, receive the quickly revert message that QA acquisition module 313 sends after, can be with this quickly revert message stores in this QA memory module 312, in order to using later on.When QA processing module 311, receive the management processing response message that IM XDM server 300 returns after, upgrade local quickly revert message according to this management processing response message.Quickly revert message in this XDM client is to store with the form of extension tag language (XML) document.
IM XDM server 330 as the QA server, stores each user's quickly revert message; Be used for that the request of obtaining returns to XDM client 310 with this user's quickly revert message according to the user's who receives message; Perhaps according to being received from the management information of XDM client 310, the quickly revert message of its storage is managed.Quickly revert message in the IM XDM server 300 also is to store with the form of XML document.Therefore, adopt XCAP to realize information interaction between XDM client 310 and the IM XDM server 300.
This IM XDM server 330 can adopt the composition structure of quickly revert server provided by the invention.IM XDM server 330 comprises QA processing module 301 and QA memory module 302.Wherein the QA memory module 302, link to each other with QA processing module 301, are used to store each user's quickly revert message; QA processing module 301 is used for according to the message that is received from XDM client 310 request of obtaining or management information the quickly revert message in the QA memory module 302 being handled accordingly.
IM XDM server 330 also comprises IM XDM Service Processing Module in order to finish other instant messaging, is used to handle the instant messaging except that quickly revert.This module is not shown in Figure 3.If the QA server adopts other service server to realize, this QA server can comprise that this service server handles the module of former business, and for example, this module can be the short message service processing module, IM SIP Service Processing Module, multimedia messaging service, MMS processing module or the like.
Message transmission successful between XDM client and the IM XDM server all is to finish by the routing function of Aggregation Proxy.Aggregation Proxy can also carry out user identity and differentiate according to the message of client transmission.
The mode that the quickly revert system of present embodiment adopts XML document with the quickly revert message stores in IM XDM server.Provide the XML Schema grammer architecture definition of quickly revert message XML document below.
<！--The?root?element:qa-set-->
<xs:element?name＝“qa-set″>
<xs:complexType>
<xs:sequence?maxOccurs＝″unbounded″>
<xs:element?name＝“qa″type＝“qaType“minOccurs＝″0″maxOccurs＝″unbounded″/>
</xs:sequence>
<xs:attribute?name＝″uri″type＝″xs:anyURI″use＝″required″/>
</xs:complexType>
</xs:element>
<xs:complexType?name＝“qaType″>
<xs:sequence>
<xs:element?name＝“i?d″type＝“xs:string″minOccurs＝“1“maxOccurs＝“1″/>
<xs:element?name＝“type＝“xs:string″minOccurs＝“1“maxOccurs＝“1″/>
<xs:element?name＝“description″type＝“xs:string″minOccurs＝“1“maxOccurs＝“1″/>
<xs:element?name＝“text″type＝″xs:string″minOccurs＝“1“maxOccurs＝“1″/>
<xs:any?namespace＝″##other″processContents＝″lax″minOccurs＝″0″maxOccurs＝″unbounded″/>
</xs:sequence>
</xs:complexType>
Wherein, qa-set is quickly revert massage set, i.e. root element.Its uri attribute indicates the owner of this quickly revert message, promptly uses the user.A quickly revert message of qa representative of consumer has message id, type of message (Type), message semantic definition (Description) and message content (Text) attribute.Big Multimedia Message is not stored in the XML document, does not deposit the content of real quickly revert message in the message content yet, only stores a URL, can obtain real message content by URL.
Adopt XCAP as the transmission of messages mode, when the transmission common message, can adopt SIP or message session trunk protocol (MSRP), but when transmitting the bigger message of volume, can only adopt the MSRP agreement, realize by setting up session (Session).Message between client and server, server and the server all will be transmitted by session initiation protocol/Internet protocol nuclear (SIP/IP Core), has all omitted the narration of SIP/IP Core in following narration.
Fig. 4 is first kind of method flow diagram of realizing the quickly revert method of the present invention's first preferred embodiment.This method is that the XDM customer end A is obtained and selected quickly revert message, and sends to first kind of specific implementation process of customer end B.In process of transmitting, adopt the message content mode that directly sends quickly revert message.Referring to Fig. 4, this method may further comprise the steps:
Step 401 when the user wants to use quickly revert message, sends XCAP GET to IM XDM server by the XDM customer end A.XCAP GET is that message is obtained request.
Step 402 after IM XDM server is received XCAP GET, is returned HTTP 200OK, and carries all quickly revert message of initiating requesting users in HTTP 200OK.
Step 403, the XDM customer end A receives quickly revert message, and the user selects a required quickly revert message.
Step 404, the XDM customer end A adopts SIP MESSAGE or MSRP SEND, and the quickly revert message that the user is selected sends to attribution server A.The information that SIP MESSAGE message is based on Session Initiation Protocol sends message, and the information that MSRP SEND message is based on MSRP sends message.The SIP MESSAGE or the MSRP SEND that send carry the message content of quickly revert message, i.e. Text.Attribution server A is the attribution server of XDM customer end A; Attribution server B is the attribution server of customer end B.
Step 407 behind the SIP MESSAGE or MSRPSEND message of customer end B reception from attribution server B, is returned SIP 200OK/MSRP 200OK and is responded attribution server B.
Below just finished quickly revert one time.The transmission of message adopt SIP MESSAGE or MSRP SEND can, specifically adopt which kind of mode to depend on the mode that original session is adopted, being consistent with original session gets final product.Corresponding 200OK is also consistent with the mode that sends message.But when adopting SIP MESSAGE, can not directly carry bigger quickly revert message among the SIP MESSAGE, must set up session, adopt MSRP SEND to send bigger quickly revert message.
Fig. 5 is second kind of method flow diagram of realizing the quickly revert method of the present invention's first preferred embodiment.This method is that the XDM customer end A is obtained and selected quickly revert message, and sends to second kind of specific implementation process of customer end B.In process of transmitting, the method for employing SIP MESSAGE directly sends the message content of quickly revert message, and this quickly revert message body is bigger, therefore need set up Session.Referring to Fig. 5, this method may further comprise the steps:
Step 501 when the user wants to use quickly revert message, sends XCAP GET by the XDM customer end A to the IMXDM server.XCAP PUT is based on the information of XCAP and obtains order, in the present embodiment, adopts XCAP GET to obtain request as message.
Step 502 after IM XDM server is received XCAP GET, is returned HTTP 200OK, and carries all quickly revert message of initiating requesting users in HTTP 200OK.
Step 503, the XDM customer end A receives quickly revert message, and the user selects a required quickly revert message.Because message is bigger, use SIP MESSAGE not to send, so below need to set up Session use MSRP SEND and send.
The Session of XDM customer end A to customer end B set up in step 504～512.
Comprise that specifically the XDM customer end A sends invitation message SIP INVITE and carries out the foundation of Session to attribution server A, attribution server A is forwarded to attribution server B with this SIP INVITE, and attribution server B is forwarded to customer end B with this SIP INVITE.After customer end B receives SIP INVITE, send SIP 200OK and respond attribution server B, attribution server B is forwarded to attribution server A with SIP 200OK response, and attribution server A is forwarded to the XDM customer end A with SIP 200OK response.After the XDM customer end A receives SIP 200OK, send ACK to attribution server A, attribution server A transmits ACK to attribution server B, and attribution server B transmits ACK to customer end B.Since then, Session sets up successfully.
Step 513～518, the quickly revert message that the XDM customer end A adopts MSRP SEND will carry message content sends to customer end B.
Comprise that specifically the quickly revert message that the XDM customer end A adopts MSRP SEND will carry message content sends to attribution server A, attribution server A transmits MSRP SEND to attribution server B, and attribution server B transmits MSRP SEND to customer end B; After customer end B receives MSRP SEND, send MSRP 200OK and respond attribution server B, attribution server B transmits MSRP 200OK and responds attribution server A, and attribution server A transmits MSRP 200OK and responds the XDM customer end A.Since then, prove that MSRP SEND sends successfully.
Step 519～524 stop the Session of XDM customer end A to customer end B.
Comprise that specifically the XDM customer end A sends termination messages SIP BYE to attribution server A, attribution server A transmits SIP BYE and is forwarded to attribution server B, and attribution server B transmits SIP BYE to customer end B; After customer end B receives SIP BYE, send SIP 200OK and respond attribution server B, attribution server B is forwarded to attribution server A with SIP 200OK response, and attribution server A is forwarded to the XDM customer end A with SIP 200OK response.Since then, Session is terminated.
Below just finished quickly revert one time.
When the quickly revert that adopts XCAP obtains, because quickly revert message is to be stored in as in the IM XDM server of QA server, so client needs to obtain from IM XDM server end earlier the particular content of quickly revert message when using quickly revert message, as the step 501 among the step 401 among Fig. 4 and Fig. 5.Fig. 6 shows and adopts XCAP to realize the method flow diagram that quickly revert message is obtained.As shown in Figure 6, its specific implementation step is as follows:
XCAP GET request is to adopt the message of XCAP agreement to obtain request, and this XCAP GET request comprises user ID.This user ID represents that XCAP GET request requires to obtain which user's quickly revert message.Because quickly revert message corresponding different user in XML document is stored respectively.
Step 602, the Aggregation Proxy unit is differentiated XCAP GET request carrying out user identity.This step is optional.
After step 604, IM XDM server are received XCAP GET request,, obtain this user's quickly revert message according to the entrained user ID of XCAP GET request.
Carried the particular content of all quickly revert message of this user in the HTTP 200 OK response.This user's quickly revert message may be one or one or more.The particular content of quickly revert message comprises message identifier (ID), type of message (Type), message semantic definition (Description) and message content (Text) attribute.
Step 607, XDM client stores quickly revert message.This step is optionally, if client all will be obtained user's quickly revert message from IM XDM server when using and send quickly revert message at every turn, does not then need to carry out the storage of this step.
The example of above-mentioned XCAP GET request is as follows:
GET?http://xcap.example.com/Quick-Answer/users/sip:sriram@example.com/QADocHTTP/1.1
Wherein, sip:sriram@example.com is a user ID.
The example of HTTP 200OK response message is as follows:
HTTP/1.1200OK
Etag:“cdcdcdcd”
Content-Type:message/qanswer
<？xml?version＝″1.0″encoding＝″UTF-8″？>
<qa-set?uri＝″sip:sriram@example.com″>
<qa>
<id>QA76587efdky761</id>
<type>Text</type>
<description>I’m?fine！</description>
<text>I’m?fine?how?are?you</text>
</qa>
</qa-set>
Wherein, QA76587efdky761 is a message id, and Text is a type of message, I ' m fine! Be message semantic definition, I ' m fine how are you is a message content.If this user has the quickly revert message of one or more, then comprise many quickly revert message among the HTTP 200OK of IM XDM server to the client answer, separate by qa.
The user can also realize the management to the quickly revert message that is stored in IM XDM server by the operation to the XDM client.Management comprises the establishment to quickly revert message, revises and deletion.Wherein creating message and can be and create new quickly revert message under the situation that does not also have quickly revert message in IM XDM server, also can be to add more quickly revert message on the quickly revert message basis of IM XDM server stores.
Fig. 7 shows the method flow diagram that adopts XCAP to realize the quickly revert message establishing.As shown in Figure 7, its specific implementation step is as follows:
Step 700, the user creates a new quickly revert message by the XDM client-side editing.
XCAP PUT request is the quickly revert message establishing request of adopting the XCAP agreement.In the present embodiment, this XCAP PUT request comprises the particular content of user ID and new quickly revert message.Because IM XDM server carries out unified management to quickly revert message resource, so message id is new quickly revert message establishing by IM XDM server.
Step 702, the Aggregation Proxy unit is differentiated XCAP PUT request carrying out user identity.This step is optional.
Step 704, IM XDM server are message id of new quickly revert message establishing after receiving XCAP PUT request, and the particular content of the quickly revert of message id and reception is updated in the quickly revert message stores document together, i.e. XML document.Wherein, determine the position of new quickly revert message deposit according to user ID.
Step 707, the XDM client is upgraded local quickly revert message.Promptly add new quickly revert message and the message id of creating thereof in this locality.
This step is to select, if do not comprise this step, then when needs use quickly revert message, must obtain quickly revert message earlier from IM XDM server.
The example of above-mentioned XCAP PUT message is as follows:
PUT?http://xcap.example.com/Quick-Answer/users/sip:sriram@example.com/QADoc/qa-setHTTP/1.1
Content-Type:message/qanswer
Content-Length:(…)
<qa>
<type>Text</type>
<description>Busy</description>
<text>Busy?now?Will?talk?later</text>
</qa>
The example of the XML document before step 704 is upgraded is as follows:
<？xml?version＝″1.0″encoding＝″UTF-8″？>
<qa-set?uri＝″sip:sriram@example.com″>
<qa>
<id>QA76587efdky761</id>
<type>Text</type>
<description>I’m?fine！</description>
<text>I’m?fine?how?are?you</text>
</qa>
</qa-set>
The example of the XML document after step 704 is upgraded is as follows:
<？xml?version＝″1.0″encoding＝″UTF-8″？>
<qa-set?uri＝″sip:sriram@example.com″>
<qa>
<id>QA76587efdky761</id>
<type>Text</type>
<description>I’m?fine！</description>
<text>I’m?fine?how?are?you</text>
</qa>
<qa>
<id>QA76587efdky763</id>
<type>Text</type>
<description>Busy</description>
<text>Busy?now?Will?talk?later</text>
</qa>
</qa-set>
It is as follows that IM XDM server returns the example of HTTP 200OK message:
HTTP/1.1?200?OK
Etag:“cdcdcdce”
Content-Type:message/qanswer
<id>QA76587efdky763</id>
Wherein, QA76587efdky763 is the message id of the new quickly revert message of present embodiment establishment.
Fig. 8 shows the method flow diagram that adopts XCAP to realize the quickly revert message modification.As shown in Figure 8, its specific implementation step is as follows:
Step 800, the user selects and revises a quickly revert message by the XDM client.Can therefrom choose quickly revert message and modification if the XDM client stores has quickly revert message,, therefrom choose a quickly revert message again and also revise if not storage then needs to obtain quickly revert message from the QA server.
XCAP PUT request in this step is the quickly revert message modification request of adopting the XCAP agreement.Though the same with request to create, XCAP PUT request command has also been used in the request of modification, not only carry the particular content of user ID and modification back quickly revert message in this XCAP PUT request command, also carry the message id of revising back quickly revert message.
Step 802, the Aggregation Proxy unit is differentiated XCAP PUT request carrying out user identity.This step is optional.
Step 804, IM XDM server are revised message id quickly revert message particular content pointed after receiving XCAP PUT request.Revising used value is the message content of revising back quickly revert message.
Step 807, the XDM client is upgraded local quickly revert message.
The example of above-mentioned XCAP PUT message as the message modification request is as follows:
PUT?http://xcap.example.com/Quick-Answer/users/sip:sriram@example.com/QADoc/qaset/qa[id＝QA76587efdky761]HTTP/1.1
Content-Type:message/qanswer
Content-Length:(...)
<id>QA76587efdky761</id>
<type>Text</type>
<description>Greeting</description>
<text>How?are?you？</text>
Wherein, id=QA76587efdky761 is for revising the message id of quickly revert message.
The example of the XML document before step 804 is revised is as follows:
<？xml?version＝″1.0″encoding＝″UTF-8″？>
<qa-set?uri＝″sip:sriram@example.com″>
<qa>
<id>QA76587efdky761</id>
<type>Text</type>
<description>I’m?fine！</description>
<text>I’m?fine?how?are?you</text>
</qa>
</qa-set>
The example of the amended XML document of step 804 is as follows:
<？xml?version＝″1.0″encoding＝″UTF-8″？>
<qa-set?uri＝″sip:sriram@example.com″>
<qa>
<id>QA76587efdky761</id>
<type>Text</type>
<description>Greeting</description>
<text>How?are?you？</text>
</qa>
</qa-set>
It is as follows that IM XDM server returns the example of HTTP 200 OK message:
HTTP/1.1200OK
Etag:“cdcdcdce”
Fig. 9 shows the method flow diagram that adopts XCAP to realize the deletion of quickly revert message.As shown in Figure 9, its specific implementation step is as follows:
Step 900, the user selects a pre-deletion quickly revert message by the XDM client., the XDM client stores can therefrom choose a quickly revert message if having quickly revert message as pre-deletion quickly revert message; If storage does not then need to obtain quickly revert message from the QA server, therefrom choose a pre-deletion quickly revert message again.
XCAP DELETE request in this step is the quickly revert message removal request that adopts the XCAP agreement.
Step 902, the Aggregation Proxy unit is differentiated XCAP DELETE request carrying out user identity.This step is optional.
After step 904, IM XDM server are received XCAP DELETE request, the quickly revert message deletion of the message id correspondence that XCAP DELETE in the XML document is carried.
Step 907, the XDM client is upgraded local quickly revert message, promptly will delete quickly revert message in this locality in advance and delete.
The example of above-mentioned XCAP DELET message as the message modification request is as follows:
DELETE
/Quick-Answer/users/sip:sriram@example.com/QADoc/～～/qa-set/qa[id＝QA76587efdky763]HTTP/1.1
Wherein, the quickly revert message of id=QA76587efdky763 for deleting.
Step 904 deletion message id is that the example of the preceding XML document of the quickly revert message of QA76587efdky763 is as follows:
<？xml?version＝″1.0″encoding＝″UTF-8″？>
<qa-set?uri＝″sip:sriram@example.com″>
<qa>
<id>QA76587efdky761</id>
<type>Text</type>
<description>Greeting！</description>
<text>How?are?you？</text>
</qa>
<qa>
<id>QA76587efdky763</id>
<type>Text</type>
<description>Busy</description>
<text>Busy?now?Will?talk?later</text>
</qa>
</qa-set>
Step 904 deletion message id is that the example of the XML document after the quickly revert message of QA76587efdky763 is as follows:
<？xml?version＝″1.0″encoding＝″UTF-8″？>
<qa-set?uri＝″sip:sriram@example.com″>
<qa>
<id>QA76587efdky761</id>
<type>Text</type>
<description>Greeting！</description>
<text>How?are?you？</text>
</qa>
</qa-set>
It is as follows that IM XDM server returns the example of HTTP 200OK message:
HTTP/1.1200?OK
Etag:“cdcdcdce”
Second preferred embodiment
When taking to send the message id mode of quickly revert message, client sends to attribution server under the client with the message id of quickly revert message, this attribution server obtains the particular content of corresponding quickly revert message according to message id from the QA server, sends to receiving terminal again.Therefore need in the quickly revert system of the embodiment of the invention, add the QA enquiry module, after being used to receive the message id of client transmission, from the QA server, search corresponding message content according to message id, and then send the attribution server of message content to receiving terminal.This QA enquiry module can be arranged in the attribution server of transmitting terminal, also can be arranged in other servers, perhaps is provided with separately.
Figure 10 is the composition frame chart of embodiment of the invention quickly revert system second preferred embodiment.This system comprises XDM client 1010, IM XDM server 1000 and QA enquiry module 1021.
The quickly revert system similarity of this quickly revert system and first preferred embodiment, difference are that the quickly revert system of present embodiment has increased QA enquiry module 1020.This QA enquiry module 1020 is arranged among the attribution server A1020 of XDM client, be used to receive the message id that XDM client 1010 is sent, and from QA memory module 1002, find out the message content of the quickly revert message of this message id correspondence, the message content of this quickly revert message is replaced message id, be packaged into new information, B sends to customer end B via attribution server.
If it is smaller that attribution server A sends to the quickly revert message that the message of attribution server B carries, then can directly adopt SIP MESSAGE or MSRP SEND message to send.If quickly revert message is bigger, can adopt MSRP SEND directly to send, perhaps when adopting SIPMESSAGE, between the customer end B of attribution server A and receiving terminal, set up Session, realize the smooth transmission of message.
Figure 11 is first kind of method flow diagram of realizing the quickly revert method of the present invention's second preferred embodiment.This method is that the XDM customer end A realizes quickly revert, and sends to first kind of specific implementation process of customer end B.In process of transmitting, adopt the mode of the message id that sends quickly revert message.This method is used in by MSRP SEND message and sends quickly revert message, perhaps sends smaller quickly revert message by SIPMESSAGE.Referring to Figure 11, this method may further comprise the steps:
Step 1103, XDM customer end A receive user's quickly revert message, and the user selects a required quickly revert message.
Step 1105, after attribution server A receives the SIP MESSAGE/MSRPSEND that carries message id, from IM XDM server, search the message content of the quickly revert message of this message id correspondence, and message id converts the message content of quickly revert message to, sends to attribution server B after the encapsulation again.Supposing that message id is that the corresponding particular content of quickly revert message of QA76sadefd123456 is the picture of a jpeg format, is that the conversion of example is exemplified below with MSRP SEND message then:
MSRP SEND message before the conversion comprises following content,
MSRP?a786hjs2SEND
To-Path:msrp://B.ServerB.com:12763/kjhd37s2s2；tcp
From-Path:msrp://A.ServerA.com:7654/jshA7we；tcp
Message-ID:87652
Content-Type:multipart/mixed；boundary＝″boundary42″
--boundary42
Content-Type:message/QA_ID
<id>QA76sadefd123456</id>
--boundary42
Content-Type:text/plain
Hey?Bob，are?you?there？
--boundary42
-------a786hjs2$
MSRP SEND message after the conversion comprises following content,
MSRP?a786hjs2?SEND
To-Path:msrp://B.ServerB.com:12763/kjhd37s2s2；tcp
From-Path:msrp://A.ServerA.com:7654/jshA7we；tcp
Message-ID:87652
Content-Type:multipart/mixed；boundary＝″boundary42″
--boundary42
Content-Type:image/jpeg
......binary?JPEG?image......
--boundary42
Content-Type:text/plain
Hey?Bob，are?you?there？
--boundary42
-------a786hjs2$
The content of SIP MESSAGE message and MSRP SEND classes of messages are seemingly.
Below just finished quickly revert one time.Message send to adopt SIP MESSAGE or MSRPSEND can, specifically adopt which kind of mode to depend on the mode that original session is adopted, being consistent with original session gets final product.Accordingly, 200OK is also consistent with the mode that sends the message employing.
Figure 12 is second kind of method flow diagram of realizing the quickly revert method of the present invention's second preferred embodiment.This method is that quickly revert message is obtained and chosen to the XDM customer end A, and sends to second kind of specific implementation process of customer end B.In process of transmitting, adopt SIP MESSAGE message to carry the message id of quickly revert message, and the quickly revert message particular content of this message id correspondence is bigger, therefore need set up Session.Referring to Figure 12, this method may further comprise the steps:
Step 1203, the XDM customer end A receives quickly revert message, and the user selects a required quickly revert message.
Step 1205, attribution server A finds out the message content of the quickly revert message of this message id correspondence according to the entrained message id of SIP MESSAGE message that receives from IM XDM server.And the message content of finding this quickly revert message is bigger, uses SIP MESSAGE not to send, thus below need to set up Session use MSRP and send.
The Session of attribution server A to customer end B set up in step 1206～1211.
Comprise that specifically attribution server A sends invitation message SIP INVITE and carries out the foundation of Session to attribution server B, attribution server B is forwarded to customer end B with this SIP INVITE.After customer end B receives SIP INVITE, send SIP 200OK and respond attribution server B, attribution server B is forwarded to attribution server A with SIP 200OK response.After attribution server A receives SIP 200OK, send ACK to attribution server B, attribution server B transmits ACK to customer end B.Since then, Session sets up successfully.
Step 1212, attribution server A finds the message content of corresponding quickly revert message according to the message id in the SIP MESSAGE message of step 1204 reception from IM XDM server, message content is replaced message id.
Step 1213～1216, attribution server A adopts MSRP SEND that the message content of quickly revert message is sent to customer end B.
Comprise that specifically the MSRPSEND that attribution server A will carry the message content of quickly revert message sends to attribution server B, attribution server B transmits MSRP SEND to customer end B; After customer end B receives MSRP SEND, send MSRP 200OK and respond attribution server B, attribution server B transmits MSRP 200OK and responds attribution server A.
Comprise that specifically attribution server A sends termination messages SIP BYE to attribution server B, attribution server B transmits SIP BYE to customer end B; After customer end B receives SIP BYE, send SIP 200OK and respond attribution server B, attribution server B is forwarded to attribution server A with SIP 200OK response.Since then, Session is terminated.
Below just finished quickly revert one time.The 3rd preferred embodiment
Above-mentioned first and second preferred embodiments all are to adopt XCAP to realize obtaining and managing of quickly revert message.Can also adopt the SIP means of signaling to realize.In this manner, quickly revert message can be stored in the QA server by any way, for example mode such as database, file.The corresponding different user of quickly revert message is stored respectively, and the message id of quickly revert message is corresponding one by one with message content.The QA server can adopt the IM sip server to realize; The QA server also can adopt IM XDM server, and this moment, the quickly revert message stores was in the XML file.The QA server comprises the QA processing module and the QA memory module of necessary server, and the function of these two modules is identical with the function of corresponding module in the first preferred embodiment quickly revert system shown in Fig. 3.In order to finish other instant messaging, the QA server also comprises IM SIP Service Processing Module, is used to handle the instant messaging except that quickly revert.
Client also needn't be used special XDM client, and this client comprises the QA acquisition module and the QA processing module of necessary client, stores user's quickly revert message if desired, then also comprises the QA memory module of client.The function of the QA acquisition module of client, QA processing module and QA memory module is identical with the function of corresponding module in the first preferred embodiment quickly revert system shown in Fig. 3.Be that with the difference of the quickly revert system of first preferred embodiment it must be the XML file format that the storage format of user's quickly revert message stores in client QA memory module do not limit.
Realize that with above-mentioned two preferred embodiments the detailed process of quickly revert method of the present invention compares, difference only is, the present embodiment client is to adopt the SIP means of signaling when the QA server obtains all quickly revert message of user.Follow-up client selects the quickly revert information and sending to give the method for receiving terminal identical with preceding method from all quickly revert message of obtaining, also comprises the message content of direct transmission quickly revert message, perhaps sends the message id of quickly revert message.When the particular content of the quickly revert message that is sent is bigger, and when adopting SIP MESSAGE message, also need to set up Session.
Figure 13 realizes the method flow diagram that quickly revert message is obtained for adopting SIP.As shown in figure 13, its specific implementation step is as follows:
Step 1302, the quickly revert message of QA whois lookup respective user.
Step 1303, QA server are carried at the quickly revert message of respective user among the SIP MESSAGE and send to client.This moment, the content of SIP MESSAGE was the management processing response message.
After step 1304, client are received SIP MESSAGE message, send SIP 200OK and respond the QA server.
Step 1305, client will be received the quickly revert message stores.
In step 1300, the QA server also can all adopt a SIP MESSAGE to send each quickly revert message of user, and then client all will send SIP 200OK and respond the QA server after receiving each SIP MESSAGE.Dimension, step 1304 and step 1305 will repeat repeatedly, all send to client up to all quickly revert message of this user.
Figure 14 shows the method flow diagram that adopts SIP to realize the quickly revert message establishing.As shown in figure 14, its specific implementation step is as follows:
Step 1401, the user creates a new quickly revert message by client-side editing.
Step 1402～1403, customer end adopted SIP MESSAGE sends to the QA server with the quickly revert message that the user creates.The QA server returns SIP 200OK.
Step 1404, QA server are message id of new quickly revert message establishing of receiving, and new quickly revert message and message id thereof are stored in the QA memory cell of QA server.
Step 1405～1406, the QA server sends to client by SIP MESSAGE with new quickly revert message and message id thereof, and client is returned SIP 200OK.SIP MESSAGE herein is the management processing response message.
Step 1407, client are upgraded local corresponding quickly revert message.Add new quickly revert message and message id thereof to client.
Figure 15 shows the method flow diagram that adopts SIP to realize the quickly revert message modification.As shown in figure 15, its specific implementation step is as follows:
Step 1500, the user selects the quickly revert message that will revise by client, and makes amendment.
Step 1501, client sends to the QA server with quickly revert message and the message id of revising thereof by SIPMESSAGE.
Step 1502, the QA server is made amendment to the quickly revert message that is stored in QA server correspondence according to the quickly revert message and the message id thereof of the modification that receives.
In this step, the QA server finds corresponding quickly revert message according to message id, and according to message content the message content of the quickly revert message of storage is made amendment.
Step 1504, client are upgraded local corresponding quickly revert message.
Figure 16 shows the method flow diagram that adopts SIP to realize the deletion of quickly revert message.As shown in figure 16, its specific implementation step is as follows:
Step 1600, the user selects a pre-deletion quickly revert message by client.
Step 1601～1602, client sends the SIP REFER of the message id carry pre-deletion quickly revert message to DELETE Bin, and DELETE Bin returns SIP 200OK.
Deletion quickly revert message will be by the indirect deletion that realizes the quickly revert message in the QA server of DELETE Bin.Specifically can being set to of SIP REFER message: the Request-URI attribute is DELETE@hostname in the SIP REFER message, and the Refer-To attribute is the message id of pre-deletion quickly revert message, and the Method attribute is INVITE.Therefore, the SIP REFER here is as the information deletion order based on SIP.
Step 1603～1605, DELETE Bin is according to corresponding quickly revert message in the message id deletion QA server.
This step comprises that specifically DELETE Bin sends SIP INVITE to the QA server.The media mode attribute of the Session Description Protocol of this SIPINVITE message (SDP) is made as " recvonly ".The QA server returns SIP 200OK after according to SIP INVITE the quickly revert message of message id correspondence being deleted, and expression is deleted successfully.DELETE Bin sends ACK message to the QA server again.
Step 1607～1607 stop the Session that the QA server is set up between DELETE Bin.Comprise that specifically the QA server sends SIP BYE to DELELTE Bin, DELETE Bin returns SIP200OK.
Step 1608, client are upgraded local quickly revert message.This step also can be after step 1602, carries out before the step 1603.
If the SIP REFER that client sends contains the implicit information of readding surely, comprise further before the step 1603 that then DELETE Bin sends SIP NOTIFY to client, step 1605 and step 1607 that client is returned SIP 200OK response also will comprise same step afterwards.
Need to prove that the information interaction between client and the QA server all needs through SIPCore.
By the above as can be seen, the quickly revert method that the embodiment of the invention provided, system, quickly revert server and client side, can make the user on different terminals, be convenient to use identical one's own quickly revert message, avoid the user that the repetitive operation of identical quickly revert message all will be set on each terminal.If the user has carried out adding to the quickly revert message on the QA server on a terminal or has revised, this user quickly revert message that on different in addition terminals, still can use its final updating to cross so.
In addition, when sending bigger quickly revert message, transmitting terminal can only send message id, the transmitting terminal attribution server converts this message id to message content, send to receiving terminal again, the effective like this offered load that has reduced between transmitting terminal and the transmitting terminal attribution server has improved the efficient that sends big quickly revert message greatly.
In sum, more than be preferred embodiment of the present invention only, be not to be used to limit protection scope of the present invention.Within the spirit and principles in the present invention all, any modification of being done, be equal to replacement, improvement etc., all should be included within protection scope of the present invention.
Claims (13)
1. a quickly revert method is characterized in that, this method comprises:
In quickly revert QA server, quickly revert message is set;
Client is initiated message to the QA server and is obtained request;
The QA server obtains request according to described message, returns quickly revert message to this client;
Client is chosen the quickly revert message of pre-transmission from the quickly revert message of returning, set up the session Session of described client to receiving terminal, adopts message session trunk protocol MSRP SEND to send selected quickly revert message to receiving terminal.
2. the method for claim 1 is characterized in that,
The request of obtaining of described message comprises user ID ID;
Described QA server according to message the request of obtaining return quickly revert message to client and comprise: described QA server is according to described user ID, obtain the quickly revert message corresponding of storage, and return the quickly revert message of described correspondence to described client with described user ID.
3. the method for claim 1 is characterized in that, described after client is returned quickly revert message, this method further comprises:
Described client is preserved the quickly revert message of returning in this locality.
4. the method for claim 1 is characterized in that, the described selected quickly revert message that client sends comprises the message content of the quickly revert message that this is selected;
Client sends described selected quickly revert message to receiving terminal and comprises:
The attribution server of client is transmitted to described receiving terminal after receiving described message content.
5. the method for claim 1 is characterized in that,
The described selected quickly revert message that client sends comprises the message id of the quickly revert message that this is selected;
Client sends described selected quickly revert message to receiving terminal and comprises:
After the attribution server of client receives described message id, obtain the message content of described message id correspondence from the QA server, described message content is sent to described receiving terminal according to described message id.
6. the method for claim 1 is characterized in that, this method further comprises:
Client sends management information to the QA server;
Described QA server is managed the quickly revert message of its storage according to described management information.
7. method as claimed in claim 3 is characterized in that, this method further comprises:
Client sends management information to the QA server;
Described QA server is managed the quickly revert message of its storage according to described management information;
Described QA server returns management processing response information to described client;
Described client is upgraded local quickly revert message according to described management processing response message.
8. as claim 6 or 7 described methods, it is characterized in that when described management information was establishment information, this establishment information comprised the message content of the new quickly revert message that client is created;
Described client sends management information to the QA server; The quickly revert message that the QA server is managed its storage according to this management information comprises:
Client sends to the QA server with the message content of described new quickly revert message;
Described QA server is set up message id for this new quickly revert message, and stores the message content and the message id of described new quickly revert message.
9. as claim 6 or 7 described methods, it is characterized in that when described management information was modification information, this modification information comprised quickly revert message after the modification of carrying message id;
Described client sends management information to the QA server; The quickly revert message that the QA server is managed its storage according to this management information comprises:
Client with described modification of carrying message id after quickly revert message send to the QA server;
Described QA server according to described modification of carrying message id after quickly revert message, revise the quickly revert message of this message id correspondence.
10. as claim 6 or 7 described methods, it is characterized in that when described management information was deletion information, this deletion information comprised the message id of pre-deletion quickly revert message;
Described client sends management information to the QA server; The quickly revert message that the QA server is managed its storage according to this management information comprises:
Client is selected the quickly revert message of pre-deletion, and this pre-message id of deleting quickly revert message is sent to the QA server;
Described QA server is deleted corresponding quickly revert message according to the message id of described pre-deletion quickly revert message.
11. the method for claim 1 is characterized in that, described quickly revert message is short message or instant message.
12. method as claimed in claim 6 is characterized in that, described customer end adopted session initiation protocol SIP sends request of obtaining of described message and described management information to described QA server.
13. method as claimed in claim 6 is characterized in that, described customer end adopted extension tag language configuration access agreement XCAP sends request of obtaining of described message and described management information to described QA server.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2006101680120A CN101202953B (en) | 2006-12-15 | 2006-12-15 | Method and system of shortcut reversion |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2006101680120A CN101202953B (en) | 2006-12-15 | 2006-12-15 | Method and system of shortcut reversion |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN101202953A CN101202953A (en) | 2008-06-18 |
| CN101202953B true CN101202953B (en) | 2010-10-20 |
Family
ID=39517872
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN2006101680120A Active CN101202953B (en) | 2006-12-15 | 2006-12-15 | Method and system of shortcut reversion |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN101202953B (en) |
Families Citing this family (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN103117955B (en) * | 2013-01-16 | 2016-08-03 | 华为技术有限公司 | Method for message transmission and device, system |
| CN107135140B (en) * | 2016-02-29 | 2020-07-14 | 阿里巴巴集团控股有限公司 | Instant messaging method and device |
| CN106547731B (en) * | 2016-09-22 | 2020-05-19 | 广州华多网络科技有限公司 | Method and device for speaking in live broadcast room |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1194562A (en) * | 1997-02-28 | 1998-09-30 | 松下通信工业株式会社 | Mobile paging telephone with automatic recalling function |
| CN1418029A (en) * | 2001-11-09 | 2003-05-14 | 致福股份有限公司 | Setting method of refusing incoming call in cellphone |
| CN1484457A (en) * | 2002-09-20 | 2004-03-24 | ��Ϊ��������˾ | Method for realizing automatic replying short message |
| CN1633112A (en) * | 2003-12-24 | 2005-06-29 | 华为技术有限公司 | A method of automatic instant message reply |
| CN1809096A (en) * | 2005-01-21 | 2006-07-26 | 乐金电子(中国)研究开发中心有限公司 | Method of automatic answer for mobile telephone and mobile telephone |
-
2006
- 2006-12-15 CN CN2006101680120A patent/CN101202953B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1194562A (en) * | 1997-02-28 | 1998-09-30 | 松下通信工业株式会社 | Mobile paging telephone with automatic recalling function |
| CN1418029A (en) * | 2001-11-09 | 2003-05-14 | 致福股份有限公司 | Setting method of refusing incoming call in cellphone |
| CN1484457A (en) * | 2002-09-20 | 2004-03-24 | ��Ϊ��������˾ | Method for realizing automatic replying short message |
| CN1633112A (en) * | 2003-12-24 | 2005-06-29 | 华为技术有限公司 | A method of automatic instant message reply |
| CN1809096A (en) * | 2005-01-21 | 2006-07-26 | 乐金电子(中国)研究开发中心有限公司 | Method of automatic answer for mobile telephone and mobile telephone |
Also Published As
| Publication number | Publication date |
|---|---|
| CN101202953A (en) | 2008-06-18 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN101155049B (en) | Message system and its conversation history processing method | |
| CN100563196C (en) | Communication system and in communication system the method for Query Information | |
| CN101395838B (en) | Data synchronization method, system and apparatus | |
| CN1703690B (en) | Side channel for membership management within conference control | |
| CN101299829B (en) | Method and message system implementing medium content management of unification storage | |
| US20090106455A1 (en) | Method and apparatus for synchronizing messages between multiple terminals | |
| EP2345267B1 (en) | Method and apparatus for address book contact management | |
| CN101557409B (en) | Method and device for syncretic management of address book information | |
| US20090298489A1 (en) | System and method for a converged network-based address book | |
| US20080256117A1 (en) | Managing entity data in case of multiple entity identities | |
| CN103119911A (en) | System and method for synchronizing the profile of a user in social networks and the user's personal contact card (PCC) | |
| CN101127951A (en) | A network system and method for displaying service based on IMS | |
| KR100977188B1 (en) | Deleting mechanism in SIP multimedia services | |
| CN101202953B (en) | Method and system of shortcut reversion | |
| US9237206B2 (en) | Method and apparatus for updating personal information in communication system | |
| KR101498731B1 (en) | Server and method for providing converged ip messaging service to interwork with non-converged ip messaging services and system therefor | |
| CN102143126B (en) | The access method of CPM meeting history record and message storage server | |
| CN101179572B (en) | Method, device and system for copying content | |
| CN1968120B (en) | Method and system for group information management | |
| CN101547412B (en) | A wireless pre-configured service realizing method and system | |
| CN101873542A (en) | Selecting method of URI (Uniform Resource Identifiers) based on conditions, server and communication system | |
| CN102469090B (en) | The method and system of startup file transmission session and the list of acquisition file transfer session | |
| CN102469139A (en) | Method and system for ending chatting conversation and acquiring chatting conversation information | |
| CN102143125B (en) | Access method of converged internet protocol messaging (CPM) session history record and message storage server | |
| CN102469138B (en) | The method and system of a kind of reception and deleting input document |
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 | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20180427 Address after: California, USA Patentee after: Global innovation polymerization LLC Address before: London, England Patentee before: GW partnership Co.,Ltd. Effective date of registration: 20180427 Address after: London, England Patentee after: GW partnership Co.,Ltd. Address before: 518129 Bantian HUAWEI headquarters office building, Longgang District, Guangdong, Shenzhen Patentee before: HUAWEI TECHNOLOGIES Co.,Ltd. |
|
| TR01 | Transfer of patent right |