CN101778056A

CN101778056A - Processing method and system for meeting history record fusing message business and

Info

Publication number: CN101778056A
Application number: CN200910247037A
Authority: CN
Inventors: 卢美莲; 李凤军; 周星; 杨栋; 曾玉冰; 张永旺
Original assignee: ZTE Corp; Beijing University of Posts and Telecommunications
Current assignee: ZTE Corp; Beijing University of Posts and Telecommunications
Priority date: 2009-12-25
Filing date: 2009-12-25
Publication date: 2010-07-14
Anticipated expiration: 2029-12-25
Also published as: CN101778056B

Abstract

The invention discloses a processing method for meeting history record fusing message business. The method comprises the following steps that: a confluent IP message (CPM) participating function server obtains the information related to the meeting from the signaling of a session initiation protocol (SIP), the information of a message session relaying protocol (MSRP) and a real-time transmission protocol (RTP) media stream in the process of realizing the meeting history record function and packages the information into the meeting history record according to the unified storage format; a message storage server (MSS) stores the meeting history record according to the united storage format; and a message storage client (MSC) visits the meeting history record according to the united storage format. The invention also discloses a processing system for meeting history record fusing message business. The invention can reveal the variation process of the conversion, and increases the analyzing efficiency of the meeting history record and the interoperability and expandability of the meeting history recording function.

Description

A kind of meeting history record processing method and system of converged message service

Technical field

The present invention relates to the message integration technology in the network service, relate in particular to a kind of meeting history record processing method and system of converged message service.

Background technology

Evolution along with network technology, the message traffic that provides on communication network presents a kind of trend of fusion, so Open Mobile Alliance (OMA, Open Mobile Alliance) tissue provides a kind of IP message enabler (CPM Enabler of fusion, Converged IP Messaging Enabler), it can cross over different Access Networks, framework is on unified IP kernel heart net, with the support terminal user one to one, one-to-many and and use between various medium types, as text, picture, the audio/video fragment, binary file, the communication of audio.

In the message communicating environment that merges, the CPM enabler is that unit provides CPM business to the user with the CPM talks, make the user carry out information interaction, the user wishes in the process of communication and the history mutual information of the CPM talks that self participated in can be write down and stored by network side, when needed can be thereby realize by send the historical intersection record information that request has access to the CPM talks that self once participated in to network side server, the overall process of the talks that once participated in reappearing user truly, and can the meeting history record information that belong to this user self of storing on the network side server be managed.The CPM message storage server provides a kind of like this function of the CPM of storage meeting history record for CPM user, CPM message stores client is by the access message storage server, the CPM meeting history record that belongs to this CPM user and relevant content are conducted interviews and manage, and resolve by the meeting history record information of obtaining from network side, show the view and the content of talks to CPM user.

The CPM talks have been described and have been utilized CPM enabler functional entity to carry out the behavior of information interaction between the communication parties, and the CPM talks are made up of outer mutual CPM message, CPM file transfer and the CPM session of the session of arbitrary number.Wherein, CPM message is the imformosome that can comprise a plurality of discrete (discontinuous) medium, as comprises text, picture, audio fragment, video segment etc.The CPM file transfer is to carry out one or more transmission courses that carry the file of content of multimedia between the participant, and recipient user must show before reception is transmitted any data of file that ground confirms receiving course.The CPM session is meant that the logic that continues for some time between two or more participants connects, and can be used for participant and exchanges continuous media in real time, also can be used for exchanging discrete media and file.CPM interacting message, CPM file transfer can be carried out in the CPM session, also can carry out outside the CPM session.It is generally acknowledged that each CPM talks only comprises a CPM session in special time, a plurality of CPM talks of participation but the user can walk abreast.

The CPM meeting history record is the storage representation of CPM talks, be authorized to the person liable and can obtain and store the information that it exchanges in CPM talks process, and these information are stored in the message storage server that the CPM service provider provides as the CPM meeting history record.At this moment, the outer mutual CPM message of CPM session is stored as a CPM Message Record, and the CPM file transfer that the CPM session is carried out outward is stored as a CPM file transfer historical record.A CPM session then is stored as a CPM conversation history record, comprises mutual data such as continuous media fragment in CPM message in the session, the interior CPM file transfer of session and the session.Therefore, on the storage representation meaning, the CPM meeting history record can be described as the set of CPM Message Record, CPM file transfer historical record and CPM conversation history record.

CPM meeting history record function is actually CPM message mutual in the CPM talks process, CPM file transfer and the CPM session carried out is carried out record.In order to realize the meeting history record function, need there be a CPM functional entity in communication process, to be positioned at simultaneously on signaling plane and the media plane at network side, as back-to-back user agent's (B2BUA, Back-to-Back User Agent) receives and sends all signaling message and media informations in the communication process, therefrom extract the information that needs record by resolving, carry out record according to certain form.CPM participates in function (CPM Participanting Function) server and finishes above-mentioned meeting history record function, and these log files are submitted to the CPM message storage server, carries out permanent storage.

The CPM Message Record, storage be CPM message mutual outside the CPM session.CPM message has two types: page-mode (Page-Mode) and big message pattern (Large Message Mode).Wherein, the CPM message of page-mode is by session initiation protocol (SIP, Session Initiation Protocol)) signaling plane transmits, and the CPM message of page-mode big or small restricted promptly can not surpass 1300 bytes; If surpass, then the content of message just can not put into SIP MESSAGE message body, and is to use the CPM message of big message pattern to send.Large message mode CPM messages is to send the CPM message that wall scroll comprises big data quantity information by message session trunk protocol (MSRP, Message Session Relay Protocol) agreement; If desired, large message mode CPM messages can also carry out segmentation and transmit, so before the CPM message that sends big message pattern, at first between the each side of communication, set up interim SIP session to consult to set up the MSRP media channel by SIP (INVITE) request of inviting, after interim SIP session is set up successfully, can send actual message content by MSRP SEND request.After this big message transmitted end, this interim SIP session will be removed immediately.

CPM file transfer historical record, storage be outside the CPM session transmission the CPM file that may carry content of multimedia, as text document, picture, audio file, video file or application program or the like.The process of transmitting of the CPM message of the transmission course of CPM file and big message pattern is similar, also is at first to set up interim SIP session by SIP INVITE request between the transmit leg of file and recipient, to consult to set up the MSRP media channel.The recipient need accept with showing or refuse the transmission request of this CPM file.If interim SIP session is set up successfully, then use MSRP SEND request message to send the actual content of CPM file; As required, also sectional transmits.After the CPM file transmitted end, this interim SIP session will be removed immediately.

CPM conversation history record, storage be interactive history information in the CPM conversation procedure, comprise four category informations: CPM session status change information, in the CPM session mutual CPM message and the media object that may comprise, the CPM file that in the CPM session, transmits, in this CPM session mutual continuous media flow object.Wherein, the CPM session state information has been described whole C PM session from being created to the whole development and change process of end, comprises following ten class session status change events information: CPM conversation establishing incident relevant information (being carried by SIP INVITE request message and associated responses message), CPM session participant leaves dialog events relevant information (being carried by SIP BYE request and associated responses message), CPM session participant is removed event information (being carried by SIP REFER request and associated responses message) from the CPM session, a CPM user joins CPM dialog events information (being carried by SIP INVITE request and associated responses message), invite other CPM session participants to add this CPM dialog events information (carrying) by SIP REFER request and associated responses message, receive in the CPM session, send CPM message (by SIP INVITE, SIP MESSAGE message is carried relevant information), receive in the CPM session, send CPM file (carrying relevant information) and CPM conversation end event information (carrying) by SIP BYE request and associated responses message by SIPINVITE message.

The CPM meeting history record is different from above-mentioned CPM Message Record, CPM file transfer historical record and CPM conversation history record as the physical file storage, it is a logical concept, in fact is exactly the storage set of the CPM file of CPM message mutual in this CPM talks, transmission and the CPM session carried out.Can see that from top analysis CPM Message Record, the message that CPM file transfer historical record is relevant comprise SIP MESSAGE, SIP INVITE, MSRP SEND and relevant response message thereof; Because the session status change events when the CPM session also comprises continuous media object mutual in the interior CPM message of session, the interior CPM file transfer of session, the session and cluster conversation, the message relevant with CPM conversation history record is then more, comprises SIP INVITE, SIP 200OK, SIP BYE, SIPREFER, SIP MESSAGE, MSRP SEND or the like.

This shows that historical in order to write down the CPM talks, CPM participates in the meeting history record function of function server need handle a large amount of different signaling planes, the message of media plane.And existing meeting history record function only to be the message that all and talks are relevant carry out that whole piece stores realizes, but in the messaging service environment that merges, because its special complexity, article one, sip request message may be represented different implications in different session context environment, and for example SIP INVITE request may be that request sends the big message of CPM, may be that request sends the CPM file, may be that request is set up the CPM session, also may is to ask to add again CPM cluster conversation or the like; Iff only writing down SIP INVITE request message, then CPM message storage server and client are when reading meeting history record information, corresponding session status incident can be understood in the semanteme that also needs to understand the SIP signaling again, and this has strengthened the complexity of reappearing the talks process.That is to say, only reuse existing mechanism, it is historical not only can't correctly to write down talks, and can resolve the meeting history record content for message storage server and message stores client and bring difficulty; Because related to difference request, the response message of various protocols, this requires message storage server and message stores client to understand the form and the details of the related command of communication protocol, has increased the complexity of parsing, processing.

In present existing messaging service, have only instant message (IM) business to have the meeting history record function, what the IM business adopted is that the method that in communication process interactive messages is intactly stored is constructed meeting history record.But in the messaging service environment that merges, the communicating medium type is complicated more, the medium type of CPM session no longer only is confined to message, but can carry out IP-based voice, video communication, especially under the situation of cluster conversation, the state variation of session is complicated more, if still according to the processing mode of IM business, only that these are relevant with session status signaling message stores, the message stores client is to understand the semanteme of its actual representative, thereby can't represent the change procedure of session.

Summary of the invention

In view of this, main purpose of the present invention is to provide a kind of meeting history record processing method and system of converged message service, to solve the problem that prior art can't represent the session change procedure in the converged message service.

For achieving the above object, technical scheme of the present invention is achieved in that

The invention provides a kind of meeting history record processing method of converged message service, this method comprises:

The IP message (CPM) that merges participates in function server in the process that realizes the meeting history record function, from session initiation protocol (SIP) signaling, message session trunk protocol (MSRP) message and real-time transport protocol (rtp) Media Stream, obtain and the relevant information of talking, and described information is encapsulated as meeting history record according to unified storage format;

Message storage server (MSS) is stored described meeting history record according to described unified storage format; Message stores client (MSC) conducts interviews to described meeting history record according to described unified storage format.

Described meeting history record is made up of CPM Message Record file, CPM file transfer history file, CPM conversation history log file.

For the CPM page message in the talks process, described obtaining and the relevant information of talking is specially:

Described CPM participates in function server and extract the Subject header field from the SIP MESSAGE message body of CPM page message, the P-Asserted-Identity header field, the CPM-Conversation-ID header field, the CPM-Contribution-ID header field, the CPM-ReplyTo-Contribution-ID header field, the value of Request-URI parameter, Content-Type is that the value and the Content-Type of application/resource-lists+xml message body part is the value of message/cpim message body.

Described the information of obtaining is encapsulated as meeting history record according to unified storage format, is specially:

In such a way the information structuring of obtaining is commented on the CPM Message Record file of the storage and uniform form of (RFC) 822 formal definitions for meeting request:

Extract current system time, as the content of the Date header field of CPM Message Record top of file;

From described Subject header field, extract the subject information of CPM page message, as the content of the Subject header field of CPM Message Record top of file;

From described P-Asserted-Identity header field, extract the CPM station address information of the transmit leg of CPM page message, as the content of the From header field of CPM Message Record top of file;

From described CPM-Conversation-ID header field, extract the CPM talks identifier information under the CPM page message, as the content of the Reference header field of CPM Message Record top of file;

From described CPM-Contribution-ID header field, extract the CPM contribution identifier information of CPM page message, as the content of the Keyword header field of CPM Message Record top of file;

From described CPM-ReplyTo-Contribution-ID header field, extract the contribution identifier information replied, as the content of the In-Repy-to header field of CPM Message Record top of file;

Determine the type of CPM page message according to the value of described Request-URI parameter, and with the value of the described Request-URI parameter content as the To header field of CPM Message Record top of file;

The value that the Content-Type header field of CPM Message Record top of file is set is message/cpim;

The value that the Content-Description header field of CPM Message Record top of file is set is CPMMessage;

Extracting the Content-Type type from described SIP MESSAGE message body is the message body content of message/cpim, as the content of CPM Message Record document text.

For the big message of the CPM in the talks process, described obtaining and the relevant information of talking is specially:

Described CPM participates in function server and extract the Subject header field from the MSRP SEND message of consulting to set up the SIP INVITE request message of MSRP media channel and transmit big message content, the CPM-Conversation-ID header field, the CPM-Contribution-ID header field, the CPM-ReplyTo-Contribution-ID header field, the P-Asserted-Identity header field, the value of Request-URI parameter, Content-Type is the value of application/resource-lists+xml message body part, and Content-Type is the value of message/cpim message body in the MSRPSEND message.

Be the CPM Message Record file that meets the storage and uniform form of RFC 822 formal definitions in such a way with the information structuring of obtaining:

Extracting the Content-Type type from MSRP SEND message is the message body content of message/cpim, as the content of CPM Message Record document text.

For the CPM file transfer in the talks process, described obtaining and the relevant information of talking is specially:

Described CPM participates in function server, and to extract Subject header field, CPM-Conversation-ID header field, CPM-Contribution-ID header field, CPM-ReplyTo-Contribution-ID header field, P-Asserted-Identity header field, the value of Request-URI parameter, Content-Type from the SIP INVITE request message of consulting to set up the MSRP media channel be the value of application/resource-lists+xml message body part, and Content-Type is the value of message/cpim message body in the MSRP SEND message.

Be the CPM file transfer history file that meets the storage and uniform form of RFC 822 formal definitions in such a way with the information structuring of obtaining:

Extract current system time, as the content of the Date header field of CPM file transfer history file head;

The value that the Content-Type header field of CPM Message Record top of file is set is Multipart/Mixed;

The value that the Content-Description header field of CPM Message Record top of file is set is CPM File;

The accessories section of the body part of described CPM file transfer history file writes down each CPM file that transmits in this CPM document transmission process, the CPM file content of each transmission all obtains from the Content-Type type of corresponding M SRP SEND message is the message body of Message/cpim, exists as an attachment content in CPM file transfer history file.

Described value according to the Request-URI parameter is determined the type of CPM page message, is specially:

If the value appointment of described Request-URI parameter is the CPM station address information of transmit leg, determine that then described CPM page message is 1-1 page message;

If the value appointment of described Request-URI parameter is the address of CPM controlled function server, determine that then described CPM page message is Ad-hoc group page message;

If the value appointment of described Request-URI parameter is the address of CPM predefine group, determine that then described CPM page message is predefine group page message.

For the CPM session, described obtaining and the relevant information of talking, and described information is encapsulated as meeting history record according to unified storage format is specially:

Described CPM participates in function server extracts relevant header field from SIP INVITE, the SIP BYE relevant with this CPM session status incident, SIP REFER, SIP MESSAGE message in conversation procedure value, the value of the relevant header field that foundation is extracted is created extending mark language (XML) document of session state information, and CPM message, CPM file, the RTP Media Stream that transmits in the session process saved as independently temporary resource file; When described CPM conversation end, the CPM conversation history log file that the XML document and the temporary resource file of session status information is encapsulated as the storage and uniform form that meets RFC 822 formal definitions.

The present invention also provides a kind of meeting history record treatment system of converged message service, and this system comprises: CPM participates in function server, MSS and MSC, wherein,

Described CPM participates in function server, be used in the process that realizes the meeting history record function, from SIP signaling, MSRP message and RTP Media Stream, obtain and the relevant information of talking, and described information is encapsulated as meeting history record according to unified storage format;

Described MSS is used for according to described unified storage format described meeting history record being stored;

Described MSC is used for according to described unified storage format described meeting history record being conducted interviews.

Described CPM participates in function server and is further used for, for CPM page message, from SIPMESSAGE message, extract the Subject header field, the CPM-Conversation-ID header field, the CPM-Contribution-ID header field, the CPM-ReplyTo-Contribution-ID header field, the P-Asserted-Identity header field, the value of Request-URI parameter, Content-Type is that the value and the Content-Type of application/resource-lists+xml message body part is the value of message/cpim message body, and structure meets the CPM Message Record file of the storage and uniform form of RFC 822 formal definitions.

Described CPM participates in function server and is further used for, for the big message of CPM, from the SIP INVITE request message of consulting to set up the MSRP media channel, extract the Subject header field, the CPM-Conversation-ID header field, the CPM-Contribution-ID header field, the CPM-ReplyTo-Contribution-ID header field, the P-Asserted-Identity header field, the value of Request-URI parameter, Content-Type is the value of application/resource-lists+xml message body part, and Content-Type is the value of message/cpim message body in the MSRPSEND message, and structure meets the CPM Message Record file of the storage and uniform form of RFC 822 formal definitions.

Described CPM participates in function server and is further used for, for the CPM file transfer, from the SIP INVITE request message of consulting to set up the MSRP media channel, extract the Subject header field, the CPM-Conversation-ID header field, the CPM-Contribution-ID header field, the CPM-ReplyTo-Contribution-ID header field, the P-Asserted-Identity header field, the value of Request-URI parameter, Content-Type is the value of application/resource-lists+xml message body part, and Content-Type is the value of message/cpim message body in the MSRPSEND message, and structure meets the CPM Message Record file of the storage and uniform form of RFC 822 formal definitions.

Described CPM participates in function server and is further used for, for the CPM session, in conversation procedure, from SIP INVITE, the SIP BYE relevant, SIP REFER, SIPMESSAGE message, extract the value of relevant header field with this CPM session status incident, the value of the relevant header field that foundation is extracted is created the XML document of session state information, and CPM message, CPM file, the RTP Media Stream that transmits in the session process saved as independently temporary resource file; When described CPM conversation end, the CPM conversation history log file that the XML document and the temporary resource file of session status information is encapsulated as the storage and uniform form that meets RFC 822 formal definitions.

The meeting history record processing method and the system of a kind of converged message service provided by the present invention, participate in function server in the process that realizes the meeting history record function by CPM, from SIP signaling, MSRP message and RTP Media Stream, obtain and the relevant information of talking, and it is packaged into unified storage format; Message storage server is according to unified storage format storage meeting history record, and CPM message stores client can be visited meeting history record according to unified storage format, thereby can represent the change procedure of session.

CPM Message Record file, CPM file transfer historical record, the CPM conversation history log file definition a kind of method of constructing unified storage format of the present invention by being comprised for the CPM meeting history record under the converged message service environment, CPM participates in function and can write down the history mutual information in the CPM talks with a kind of unification, succinct effective and efficient manner like this, and the particular content of CPM meeting history record also can be obtained, resolve to message stores client and message storage server with a kind of uniform way.Gou Zao storage and uniform form makes that the concrete signaling protocol form in CPM Message Record, CPM file transfer historical record, CPM conversation history log file and CPM message or the CPM session interaction is irrelevant according to the method, and the process that the content of concern interaction message and session status change, can reappear the evolution of CPM talks authentic and validly to the user, when mitigation system is handled complexity, increase user's experience.In addition, according to storage and uniform form of the present invention, help increasing interoperability and the extensibility of meeting history record function between different system.

Description of drawings

Fig. 1 is the flow chart of the meeting history record processing method of a kind of converged message service of the present invention;

Fig. 2 is the institutional framework schematic diagram of the XML document of CPM session state information among the present invention;

Fig. 3 is the composition structural representation of the meeting history record treatment system of a kind of converged message service of the present invention.

Embodiment

The technical solution of the present invention is further elaborated below in conjunction with the drawings and specific embodiments.

Be representing of the session change procedure in the realization converged message service, the meeting history record processing method of a kind of converged message service provided by the present invention as shown in Figure 1, may further comprise the steps:

Step 001, CPM participates in function server in the process that realizes the meeting history record function, from SIP signaling, MSRP message and RTP (RTP, Real-time Transport Protocol) obtains and the relevant information of talking in the Media Stream, and this information is encapsulated as meeting history record according to unified storage format.

For CPM page message and the big message of CPM, CPM participates in function server the information of extracting is encapsulated as CPM Message Record file according to unified storage format; For the CPM file transfer, CPM participates in function server the information of extracting is encapsulated as CPM file transfer historical record according to unified storage format; For the CPM session, CPM participates in function server the information of extracting is encapsulated as CPM conversation history log file according to unified storage format.

Step 002, message storage server (MSS, Message Storage Server) according to unified storage format, is stored meeting history record.

Step 003, message stores client (MSC, Message Storage Client) according to unified storage format, conducts interviews to meeting history record.

MSC conducts interviews to meeting history record, can realize representing the CPM conversation content.Representing of CPM conversation content by CPM Message Record file, CPM file transfer history file, CPM conversation history log file that this meeting history record comprised are resolved and presented.

At first encapsulation is elaborated to the structure of CPM Message Record file below.

Though the CPM message of page-mode adopts SIP MESSAGE message bearing, and the CPM message of big message pattern adopts MSRP to send (SEND) message bearing, but these two kinds of patterns are aimed at message transmitting procedure and distinguish, no matter be SIP MESSAGE message, or MSRP SEND message, in fact all be a kind of encapsulation, make message content to transmit by signalling path or media channel to message content.For message stores client and message storage server, it more is absorbed in the content of CPM message, as sender, recipient, theme, date, content, annex etc., rather than the transmission form of message, therefore be necessary for CPM message constructing storage and uniform form, this storage format is paid close attention to the actual content of CPM message bearing, and ignores the information such as middle route in the CPM message transmitting procedure, guarantee content intact, clear in structure, effectively succinct.It so no matter to be message storage server, still the message stores client can both be resolved CPM message with uniform way, and need not to know the details of different message transfer forms, invite (INVITE) message, MSRP SEND message or the like as SIP MESSAGE message, SIP, this can play the effect that improves treatment effeciency.

In order to satisfy the Internet Message Access Protocol edition 4 (IMAP4 that message storage server externally provides, Internet Message Access Protocol 4) demand, the storage and uniform form of CPM Message Record should meet multi-functional Internet mail and expand (MIME, Multipurpose Internet Mail Extensions) form, be similar to the form of " an envelope mail ", storage format is as shown in table 1 below:

Table 1

The storage and uniform form of the CPM Message Record shown in the above-mentioned table 1 satisfies the formal definition of request comment (RFC, Request For Comments) 822, and CPM Message Record storage format is divided into head and text two parts.Wherein, each header field information of head is extracted from the relevant header field of SIP MESSAGE message (CPM page message) or SIP INVITE (the big message of CPM); And body part extracts from " Content-Type " of SIPMESSAGE message or MSRP SEND message is the message body of " Message/CPIM ".The storage and uniform form of above-mentioned CPM Message Record has been ignored the concrete transmission means of CPM message, and pays close attention to the actual content of CPM message.The method of structure CPM Message Record storage and uniform form is as follows:

1, for CPM page message, CPM participates in function server and according to following steps SIPMESSAGE message body is resolved, and obtains relevant information and constitutes CPM message storage and uniform format record file:

Step 101, CPM participates in function server and obtains current system time, carries out record according to the form as " Wed, 15Apr2009 17:12:33+0800 ", as the content of CPM Message Record file " Date " header field;

Step 102 obtains the subject information of CPM message, as " Subject " header field content of CPM Message Record top of file from " Subject " header field of SIP MESSAGE message;

Step 103 obtains the sender's of CPM message CPM station address information from " P-Asserted-Identity " header field of SIP MESSAGE message, as the content of " From " header field of CPM Message Record top of file;

Step 104, the value of " Request-URI " parameter in the request row of inspection SIP MESSAGE message, the value of this parameter will specify this SIP MESSAGE message to be 1-1 page message or Ad-hoc group page message or predefine group page message, and will be concrete:

If the value appointment of " Request-URI " parameter is recipient CPM station address, then explanation is a 1-1 page message, obtains the value of " Request-URI " parameter, as the content of " To " header field of Message Record top of file;

If the value appointment of " Request-URI " parameter is the address of CPM controlled function talks server, then explanation is an Ad-hoc group page message, obtain the message body part of " Content-Type " type in the SIP MESSAGE message body for " application/resource-lists+xml ", and from the extending mark language (XML of recipient's station address tabulation, Extensible Markup Language) obtains the value of recipient's station address in the document fragment, with "; " separate, as the content of " To " header field of Message Record top of file;

If the value appointment of " Request-URI " parameter is the address of CPM predefine group, then explanation is a predefine group page message, CPM participates in function server will be according to the address of CPM predefine group from XML document management server (the Group XDMS of group, Group XML Document ManagementServer) obtains the information about firms of this group, and with the CPM station address of this group member uses "; " separate, as the content of " To " header field of Message Record top of file;

Step 105, from " CPM-Conversation-ID " header field of SIP MESSAGE message, obtain the affiliated CPM talks identifier information of CPM message, content as " Reference " header field of Message Record top of file, this header field is an optional header field among RFC 822 mail head, is used for storing the value of CPM talks identifier;

Step 106, from " CPM-Contribution-ID " header field of SIP MESSAGE message, obtain the CPM contribution identifier information of CPM message, content as " Keyword " header field of Message Record top of file, this header field is an optional header field among RFC 822 mail head of standard, is used for storing the contribution identifier of this CPM message;

Step 107, if there is " CPM-ReplyTo-Contribution-ID " header field in the SIP MESSAGE message, then obtain the value (the contribution identifier of being replied) of this header field, content as " In-Repy-to " header field of Message Record top of file, this header field is an optional header field among RFC 822 mail head of standard, is used for storing the contribution identifier of the answer of this CPM message;

Step 108, the value that " Content-Type " header field of Message Record top of file is set is " Message/CPIM ", the body matter of regulation CPM Message Record file is " Message/CPIM " type;

Step 109, the value that " Content-Description " header field of Message Record top of file is set is " CPMMessage ", describes this and is CPM Message Record file;

Step 110, the head and the body part of CPM Message Record file are separated by null;

Step 111 obtains the message body content of " Content-Type " type for " Message/CPIM " from SIP MESSAGE message, with its content as CPM Message Record document text part.

2, for the big message of CPM, CPM participates in function server and extract relevant information from the SIPINVITE request message of consulting the MSRP media channel and the MSRP SEND message of transmitting big message content, comprises the steps:

Step 201, CPM participates in function server and obtains current system time, carries out record according to the form as " Wed, 15Apr200917:12:33+0800 ", as the content of Message Record file " Date " header field;

Step 202 obtains the subject information of CPM message, as " Subject " header field content of Message Record top of file from " Subject " header field of SIP INVITE;

Step 203 obtains the sender's of CPM message CPM station address information from " P-Asserted-Identity " header field of SIP INVITE, as the content of " From " header field of Message Record top of file;

Step 204, check the value of " Request-URI " parameter in the SIP INVITE request message requests row, the value of this parameter will specify that this SIP INVITE request sets up is the transmission of the big message of transmission or predefine group of the big message of transmission or Ad-hoc group of the big message of 1-1, is specially:

If the value appointment of " Request-URI " parameter is recipient CPM station address, the transmission that the big message of 1-1 is set up in this INVITE request then is described, CPM participates in the value that function server is obtained " Request-URI " parameter, as the content of " To " header field of Message Record top of file;

If the value appointment of " Request-URI " parameter is the address of CPM controlled function talks server, the transmission that the big message of Ad-hoc group is set up in this INVITE request then is described, CPM participates in function server and obtains that " Content-Type " type is the message body part of " application/resource-lists+xml " in the SIP INVITE body, and from the XML document fragment of recipient's station address tabulation, obtain the value of recipient's station address, with "; " separate, as the content of " To " header field of Message Record top of file;

If the value appointment of " Request-URI " parameter is the address of CPM predefine group, the transmission that the big message of predefine group is set up in this INVITE request then is described, CPM participates in function server will obtain the information about firms of this group according to the address of CPM predefine group from the XDMS of group, and with the CPM station address of this group member uses "; " separate, as the content of " To " header field of Message Record top of file;

Step 205 obtains the CPM talks identifier information under the CPM message from " CPM-Conversation-ID " header field of SIP INVITE, as the content of " Reference " header field of Message Record top of file;

Step 206 obtains the CPM contribution identifier information of CPM message from " CPM-Contribution-ID " header field of SIP INVITE, as the content of " Keyword " header field of Message Record top of file;

Step 207 if there is " CPM-ReplyTo-Contribution-ID " header field in the SIP INVITE, then obtains the value (by the contribution identifier of being replied) of this header field, as the content of " In-Repy-to " header field of Message Record top of file;

Step 208, the value that " Content-Type " header field of Message Record top of file is set is " Message/CPIM ", the body matter of regulation CPM Message Record file is " Message/CPIM " type;

Step 209, the value that " Content-Description " header field of Message Record top of file is set is " CPMMessage ", describes this and is CPM Message Record file;

Step 210, the head and the body part of CPM Message Record file are separated by null;

Step 211, the MSRP SEND message that sends in the MSRP media channel that the INVITE request is consulted has been carried the content of the big message of CPM of actual transmissions, from MSRP SEND message, obtain the message body content of " Content-Type " type, with its content as CPM Message Record document text part for " Message/CPIM ".

Encapsulation is elaborated to the structure of CPM file transfer historical record more below.

CPM file transfer historical record, storage be outside the CPM session transmission the CPM file that may carry content of multimedia, as text document, picture, audio file, video file or application program or the like.The process of transmitting of the CPM message of the transmission course of CPM file and big message pattern is similar, also is at first to set up interim SIP session to consult to set up the MSRP media channel by SIP INVITE request between the recipient of transmission and file.The recipient need accept with showing or refuse the transmission request of this CPM file.If interim SIP session is set up successfully, then use MSRP SEND request message to send the actual content of CPM file, as required, can also segmentation transmit.After the CPM file transmitted end, this interim SIP session will be removed immediately.

In order to satisfy the demand of the IMAP4 agreement that message storage server externally provides, the storage and uniform form of CPM file transfer historical record should meet the MIME form, also is similar to the form of " an envelope mail ".Storage format is as shown in table 2 below:

The head of whole C PM file transfer history file
The head of whole C PM file transfer history file	??Date：??Subject：??From：??To：??Reference：??Keyword：??In-Reply-To：??Content-Type：Multipart/Mixed；boundary＝next??Content-Description：CPM?File

The head of whole C PM file transfer history file
The head of whole C PM file transfer history file	The body part of //CPM file transfer history file omits the specific coding content ...--next // body matter Content-Type:text/plain; Charset=utf-8 This is File Transfer--next // transfer files 1
Content-Type:application/octet-stream Content-Transfer-Encoding:base64 Content-Disposition:attachment; Filename=" ... " ... // omission specific coding content--next // transfer files 2 Content-Type:application/octet-stream Content-Transfer-Encoding:base64 Content-Disposition:attachment:filename=" ... " ... // omission specific coding content--next--

Table 2

The storage and uniform form of the CPM file transfer historical record shown in the above-mentioned table 2 satisfies the formal definition of RFC 822 equally, specifying mime type by " Content-Type " header field is " Multipart/Mixed " type, and promptly whole log file can be divided into head, text, annex three parts.Wherein, each header field information of head is extracted in the relevant header field from the SIP INVITE of consulting to set up the MSRP passage, body part provides the textual description to the log file content, accessories section is the content of the CPM file of transmission, can extract " Message/CPIM " message body from " Content-Type " of the MSRP SEND message of transmitting actual CPM file content.The storage and uniform form of above-mentioned CPM file transfer historical record is ignored the concrete transmission means of CPM file, and pays close attention to the actual content of CPM file.The method of structure CPM file transfer historical record storage and uniform form is as follows:

Step 301, CPM participates in function server and obtains current system time, carries out record according to the form as " Wed, 15Apr200917:12:33+0800 ", as the content of CPM file transfer history file head " Date " header field;

Step 302 obtains the subject information of CPM file, as " Subject " header field content of CPM file transfer history file head from " Subject " header field of SIP INVITE;

Step 303 obtains the sender's of CPM file CPM station address information from " P-Asserted-Identity " header field of SIP INVITE, as the content of " From " header field of CPM file transfer history file head;

Step 304, the value of " Request-URI " parameter in the request row of inspection SIP INVITE, what the value of this parameter will be specified this SIP INVITE request foundation is transmission or the transmission of Ad-hoc group file or the transmission of predefine group file of 1-1 file, concrete:

If the value appointment of " Request-URI " parameter is recipient CPM station address, the transmission that the 1-1 file is set up in this INVITE request then is described, CPM participates in the value that function server is obtained " Request-URI " parameter, as the content of " To " header field of CPM file transfer history file head;

If the value appointment of " Request-URI " parameter is the address of CPM controlled function talks server, the transmission that Ad-hoc group file is set up in this INVITE request then is described, CPM participates in function server and obtains that " Content-Type " type is the message body part of " application/resource-lists+xml " in the SIP INVITE body, from the XML document fragment of recipient's station address tabulation, obtain the value of recipient's station address, with "; " separate, as the content of " To " header field of CPM file transfer history file head;

If the value appointment of " Request-URI " parameter is the address of CPM predefine group, the transmission that the big message of predefine group file is set up in this INVITE request then is described, CPM participates in function server will obtain the information about firms of this group according to the address of CPM predefine group from the XDMS of group, and with the CPM station address of this group member uses "; " separate, as the content of " To " header field of CPM file transfer history file head;

Step 305 obtains the CPM talks identifier information under the CPM file that will transmit from " CPM-Conversation-ID " header field of SIP INVITE, as the content of " Reference " header field of CPM file transfer history file head;

Step 306 obtains the CPM contribution identifier information of the CPM file that will transmit from " CPM-Contribution-ID " header field of SIP INVITE, as the content of " Keyword " header field of CPM file transfer history file head;

Step 307, if there is " CPM-ReplyTo-Contribution-ID " header field in the SIP INVITE, then obtain the value (by the contribution identifier of being replied) of this header field, as the content of " In-Repy-to " header field of CPM file transfer history file head;

Step 308, the value that " Content-Type " header field of CPM file transfer history file head is set is " Multipart/Mixed ", the body part of regulation CPM file transfer history file is a mixed type, and by " boundary " parameter delimiter is set;

Step 309, the value that " Content-Description " header field of CPM file transfer history file head is set is " CPM File ", describes this and is CPM file transfer history file;

Step 310, the head and the body part of CPM file transfer history file are separated by null;

" Content-Type " that step 311, the main part of the body part of CPM file transfer history file are provided with mime type is " text/plain ", specifies one section textual description information, as " This is filetransport record... "

Step 312, the accessories section of the body part of CPM file transfer history file writes down each CPM file that transmits in this CPM document transmission process, the CPM file content of each transmission all obtains for the message body of " Message/CPIM " from " Content-Type " type of corresponding M SRP SEND message, exists as an attachment content in CPM file transfer history file.

Structure encapsulation to CPM conversation history log file is elaborated below.

Should comprise at least four category informations in the CPM conversation history record: (1) CPM session state information is used for describing whole C PM session all session status change informations from the process that is created to end; (2) mutual CPM message in this CPM session, and the media object that may comprise; (3) the CPM file that in the CPM session, transmits; (4) mutual Media Stream object in this CPM session is as the recording fragment of audio/video conversation etc.

Wherein, the record of CPM session state information is the most complicated, because session status is the meeting dynamic change in conversation procedure, leave, remove user or the like if any new user's adding, user, the relevant sip message of indication session status change events may comprise SIP INVITE, SIP 200 OK, SIP BYE, SIPREFER message and some SIP failure response message or the like, and the concrete semanteme of these message representative in a session should participate in the logic that function is understood and execution is relevant by CPM.

Use XML document with a kind of structuring, succinctly, mode organizes that to participate in the session state information that biological function explore goes out by CPM be a kind of better solution intuitively, and it is that the medium type of text/xml is encapsulated in the file of mime type that XML document can be used as Content-Type, participate in function server by the IMAP4 agreement by CPM and submit to message storage server, therefore also can be suitable for present framework and interface protocol fully.

The institutional framework of CPM session state information XML document as shown in Figure 2, wherein:

Root element＜Session-Event 〉: be the root element of the XML document of CPM session state information, comprise 1 under this element to a plurality of＜Event element, each＜Event〉element is used for writing down the incident of a session and relevant information thereof; Contingent incident comprises that session status changes relevant incident and the incident of messaging or file in conversation procedure in the CPM session.

Element＜Type 〉: the type of recording conversation incident, have 10 kinds, comprise mutual CPM message in incident that session status is relevant and the session, incidents such as transmission CPM file, therefore,＜Type value have: create session (Session-Establishment), the participant leaves session (Participant-Leave), the participant is removed from session (Remove-Participant), CPM user joins (Participant-Join) in the session, invite other CPM users to join CPM session (Invite-Join), conversation end (Session-End), receive CPM message (Receive-Message), send CPM message (Send-Message), receive CPM file (Receive-File), send CPM file (Send-File).

Element＜TimeStamp 〉: write down the temporal information that this dialog events takes place.

Element＜Initiator 〉: be used for CPM station address, as recording conversation promoter, adding session invitation person, CPM sender of the message, file sender's etc. CPM station address dissimilar dialog events recording events promoters.

Element＜Participant-List 〉: be used for dissimilar dialog events recording events participants, station address information, as the recording conversation participant, be removed the user, by the user that invited, CPM message recipient, file recipient's etc. station address information.＜Participant-List〉comprise one or more＜entry〉element, each＜entry〉element, can comprise＜display-name daughter element, wherein comprise the name that can be the session invitee that the user understands; Also can comprise＜accept〉daughter element,＜accept〉value be " yes " or " no ", whether presentation of events is accepted, for example whether session invitation is accepted, whether CPM message, file are successfully received etc.; Be under the situation of predefine group by invited party,＜Participant-List〉element should comprise " group-uri " attribute, in order to the address of indicating predetermined adopted group, can also comprise " group-display-name " attribute, the String type.

Element＜Resource 〉: comprise the quoting of session internal state change events related resource, as quoting of the CPM file blotter that transmits in CPM message blotter mutual in the session, the session.

Element＜Subject 〉: be used to describe the subject information of this CPM session, only in the session status event type is " Event " element of " Session-Establishment ", occur as daughter element.

Above-mentioned＜Session-Event 〉,＜Event 〉,＜Type〉and＜TimeStamp〉be essential element,＜Initiator 〉,＜Participant-List 〉,＜Resource 〉,＜Subject 〉,＜entry 〉,＜display-name 〉,＜accept〉be optional element.

The information difference that different session status incidents need write down, CPM participation function server is arranged in signalling path the implementation of CPM message, session is controlled, therefore CPM participates in the concrete semanteme that function server can be understood the SIP signaling according to the context environmental of talks process, and therefrom parse specific session status event type, from the header field of relevant sip message, extract necessary information then and carry out record, form the session state information XML document.

Participate in the situation that function server receives the initial SIPINVITE request of representative " establishment CPM dialog events " for CPM, idiographic flow is as follows:

Step 401, CPM participates in function server and thinks that " setting up the CPM dialog events " take place, and creates the XML document of session state information, creates root element＜Session-Event 〉, and increase by one＜Event〉element, the relevant information of record " setting up the CPM dialog events ";

Step 402, CPM participates in function server at＜Event〉element establishment＜Type down〉daughter element, and be set to " Session-Establishment ", represent to have created new CPM session;

Step 403, CPM participates in function server at＜Event〉element establishment＜TimeStamp down〉daughter element, and according to the current system time of format record as " Wed, 15Apr 200917:12:33+0800 ", as＜TimeStamp〉value, the recording conversation creation-time stabs information;

Step 404, CPM participates in function server extracts " P-Asserted-Identity " header field from SIP INVITE request value, and at＜Event〉establishment＜Initiator under the element〉daughter element, with the header field value that extracts as＜Initiator the value of daughter element, in order to record CPM session invitation initiator's CPM station address;

Step 405, CPM participates in function server at＜Event〉element establishment＜Participant-List down〉daughter element, in order to recording conversation invitation recipient's CPM address information;

Step 406, CPM participates in the value that function server is obtained " Request-URI " in the request row of SIP INVITE request, and judge that according to the value of this parameter the type of this CPM session invitation is that 1-1 session invitation or Ad-hoc cluster conversation are invited or the predefine cluster conversation is invited, concrete:

If the value appointment of " Request-URI " parameter is recipient CPM station address, illustrate that then this INVITE asks to set up the 1-1CPM session, CPM participates in the value that function server is obtained " Request-URI " parameter, and at＜Participant-List〉establishment＜entry under the element〉daughter element, in order to recorder side CPM user's address information;

If the value appointment of " Request-URI " parameter is the address of CPM controlled function talks server, illustrate that then this INVITE asks to set up the Ad-hoc cluster conversation, CPM participates in function server and obtains that " Content-Type " type is the message body part of " application/resource-lists+xml " in the SIPINVITE message body, from the XML document fragment of recipient's station address tabulation, obtain the value of each recipient CPM station address, and be this recipient's station address information at＜Participant-List〉create corresponding＜entry under the element〉daughter element, each＜entry〉recipient's of daughter element record CPM station address information;

If the value appointment of " Request-URI " parameter is the address of CPM predefine group, illustrate that then this INVITE asks to set up the CPM of predefine group session, CPM participates in function server will obtain the information about firms of this group according to the address of CPM predefine group from the XDMS of group, and be this recipient's station address information at＜Participant-List〉create corresponding＜entry under the element〉daughter element, each＜entry〉recipient's of daughter element record CPM station address information.

Participate in the situation that function server receives the SIP INVITE request of representative " CPM user initiatively adds the CPM dialog events " for CPM, idiographic flow is as follows:

Step 501, CPM participates in function server at root element＜Session-Event〉the following new＜Event of increasing〉daughter element, in order to the relevant information of record " CPM user initiatively adds the CPM dialog events ";

Step 502, CPM participates in function server at＜Event〉establishments＜Type under the daughter element〉daughter element, and be set to " Participant-Join ", represent that the participant initiatively adds the CPM session;

Step 503, CPM participates in function server at＜Event〉establishment＜TimeStamp under the daughter element〉daughter element, and according to as the form of " Wed; 15Apr 200917:12:33+0800 " write down current system time, as＜TimeStamp〉value, write down the timestamp information that this dialog events takes place;

Step 504, CPM participates in function server extracts " P-Asserted-Identity " header field from SIP INVITE request value, and at＜Event〉establishment＜Initiator under the daughter element〉daughter element, with the header field value that extracts value, initiate to add the participant's of conversation request station address in order to record as this daughter element.

Participate in the situation that function server receives the initial SIPBYE request of representative " participant leaves the CPM session " for CPM, idiographic flow is as follows:

Step 601, CPM participates in function server at root element＜Session-Event〉the following new＜Event of increasing〉daughter element, in order to the relevant information of record " participant leaves the CPM dialog events ";

Step 602, CPM participates in function server at＜Event〉Character table establishment＜Type down〉daughter element, and be set to " Participant-Leave ", represent that the participant leaves the CPM session;

Step 603, CPM participates in function server at＜Event〉establishment＜TimeStamp under the daughter element〉daughter element, and according to as the form of " Wed; 15Apr 200917:12:33+0800 " write down current system time, as＜TimeStamp〉value, write down the timestamp information that this dialog events takes place;

Step 604, CPM participates in function server extracts " P-Asserted-Identity " header field from SIP BYE request value, and at＜Event〉establishment＜Initiator under the daughter element〉daughter element, with the header field value that extracts value, initiate the participant's of the request of leaving station address in order to record as this daughter element.

Participate in function server for CPM and receive the situation that representative " removes the participant " from the CPM session SIPREFER asks, idiographic flow is as follows:

Step 701, CPM participates in function server at root element＜Session-Event〉the following new＜Event of increasing〉daughter element, in order to the relevant information of record " from the CPM session, removing participant's incident ";

Step 702, CPM participates in function server at＜Event〉establishments＜Type under the daughter element〉daughter element, and be set to " Remove-Participant ", represent from the CPM session, to remove the participant;

Step 703, CPM participates in function server at＜Event〉establishment＜TimeStamp under the daughter element〉daughter element, and according to as the form of " Wed; 15Apr 200917:12:33+0800 " write down current system time, as＜TimeStamp〉value, write down the timestamp information that this dialog events takes place;

Step 704, CPM participates in function server extracts " Referred-By " header field from SIP REFER request value, and at＜Event〉establishment＜Initiator under the daughter element〉daughter element, with the header field value that extracts value, initiate to remove the CPM station address of participant's request in order to record as this daughter element;

Step 705, CPM participates in function server at＜Event〉establishments＜Participants-List under the daughter element〉daughter element, in order to write down the participant CPM station address information that will remove;

Step 706, CPM participates in function server and obtain the CPM station address that request is removed from " Refer-To " header field of SIP BYE request, if point to URI-list in " Refer-To " header field, then CPM participates in the CPM station address that the request that obtains in the message body that function server " Content-Type " from SIP REFER request be " application/resource-lists+xml " is removed and tabulates, and the CPM user who is removed at each request is at＜Participants-List〉create one＜entry under the daughter element〉daughter element, the session participant's that will remove in order to record CPM station address.

Participate in function server for CPM and receive the situation that SIP REFER that representative " invites other users to add the CPM dialog events " asks, idiographic flow is as follows:

Step 801, CPM participates in function server at root element＜Session-Event〉the following new＜Event of increasing〉daughter element, in order to the relevant information of record " inviting other users to add the CPM dialog events ";

Step 802, CPM participates in function server at＜Event〉establishments＜Type under the daughter element〉daughter element, and be set to " Invite-Join ", expression invitation user adds the CPM dialog events;

Step 803, CPM participates in function server at＜Event〉establishment＜TimeStamp under the daughter element〉daughter element, and according to as the form of " Wed; 15Apr 200917:12:33+0800 " write down current system time, as＜TimeStamp〉value, write down the timestamp information that this dialog events takes place;

Step 804, CPM participates in function server extracts " Referred-By " header field from SIP REFER request value, and at＜Event〉establishment＜Initiator under the daughter element〉daughter element, with the header field value that extracts value, initiate to invite the participant to add the CPM station address of conversation request in order to record as this daughter element;

Step 805, CPM participates in function server at＜Event〉establishments＜Participants-List under the daughter element〉daughter element, in order to write down the participant CPM station address information that will add;

Step 806, CPM participates in function server and obtain the CPM station address that request is added from " Refer-To " header field of SIP BYE request, if point to URI-list in " Refer-To " header field, then CPM participates in the CPM station address that the request that obtains in the message body that function server " Content-Type " from the INVITE request be " application/resource-lists+xml " adds and tabulates, and the CPM user who adds at each request is at＜Participants-List〉create one＜entry under the daughter element〉daughter element, the session participant's that will add in order to record CPM station address.

Participate in the situation that function server receives the SIP REFER request of representative " conversation end incident " for CPM, idiographic flow is as follows:

Step 901, CPM participates in function server at root element＜Session-Event〉the following new＜Event of increasing〉daughter element, in order to the relevant information of record " CPM conversation end incident ";

Step 902, CPM participates in function server at＜Event〉establishments＜Type under the daughter element〉daughter element, and be set to " Session-End ", represent the CPM conversation end;

Step 903, CPM participates in function server at＜Event〉establishment＜TimeStamp under the daughter element〉daughter element, and according to as the form of " Wed; 15Apr 200917:12:33+0800 " write down current system time, as＜TimeStamp〉value, write down the timestamp information that this dialog events takes place.

Except the relevant incident of above-mentioned session status, the CPM message that receives, sends in the CPM session also is the relevant incident of session; In addition, the transmission of the file in the session also is the relevant incident of session with receiving.

At sending CPM message event (Send-Message), concrete operations are: increase new＜Event〉element, in order to the relevant information of record " Send-Message "; Increase by one＜Type〉daughter element, and be set to " Send-Message "; Increase by one＜TimeStamp〉daughter element, write down the time and date that this incident takes place; Increase by one＜Initiator〉daughter element, recording messages sender's station address; Increase by one＜Participat-List〉daughter element, recording messages recipient's station address; At＜Participat-List〉daughter element＜accept〉whether this message of record is successfully received in the daughter element; The CPM message content that sends is carried out record as temporary file.

At receiving CPM message event (Receive-Message), concrete operations are: increase new＜Event〉element, in order to the relevant information of record " Receive-Message "; Increase by one＜Type〉daughter element, and be set to " Receive-Message "; Increase by one＜TimeStamp〉daughter element, write down the time and date that this incident takes place; Increase by one＜Initiator〉daughter element, recording messages sender's station address; The CPM message content that receives is carried out record as temporary file.

At sending file event (Send-File), concrete operations are: increase new＜Event〉element, in order to the relevant information of record " Send-File "; Increase by one＜Type〉daughter element, and be set to " Send-File "; Increase by one＜TimeStamp〉daughter element, write down the time and date that this incident takes place; Increase by one＜Initiator〉daughter element, log file sender's station address; Increase by one＜Participat-List〉daughter element, log file recipient's station address; At＜Participat-List〉daughter element＜accept〉whether record this document is successfully received in the daughter element; The CPM file content that sends is carried out record as temporary file.

At receiving file event (Receive-File), concrete operations are: increase new＜Event〉element, in order to the relevant information of record " Receive-File "; Increase by one＜Type〉daughter element, and be set to " Receive-File "; Increase by one＜TimeStamp〉daughter element, write down the time and date that this incident takes place; Increase by one＜Initiator〉daughter element, log file sender's station address; The CPM file content that receives is carried out record as temporary file.

Structure encapsulation for CPM conversation history log file, in order to satisfy the action need of IMAP4 interface protocol, CPM conversation history record should be as many parts (Multipart) object storage of a MIME form, above-mentioned four category informations is encapsulated in the structure of Multipart into to store.Wherein, mutual CPM message and CPM file can be with reference to the storage and uniform form of CPM Message Record that has defined and CPM file transfer historical record in the session; The interior mutual Media Stream object of session then can be used as Content-Type and stores for the part of " Audio " or " Video ".For the record of session state information, the information in order can reasonably to write down the multiple session status incident that may occur in the CPM session and should to write down for these incidents adopts the storage format of XML document as this part information.

In sum, the storage and uniform form that can define CPM conversation history record also is the object of a MIME form, but because the information that CPM conversation history record comprises is more, therefore the form of CPM conversation history record is also more complicated, its framework is as shown in table 3 below, be similar to the form of " an envelope mail " equally, meet the organization definition of RFC822.

Table 3

As above the storage and uniform form of the record of the CPM conversation history shown in the table satisfies the formal definition of RFC 822 equally, specifying mime type by " Content-Type " header field is " Multipart/Mixed " type, and promptly whole log file can be divided into head, text, annex three parts.

The information that head comprises, it is explanatory memorandum to whole session history file content, for example this CPM session date of taking place, session theme, session initiator, participant or the like are checked or are facilitated for follow-up search, query manipulation to offer CPM user.These information can be from the XML document of session state information＜Type the daughter element value for the representative conversation establishing incident of " Session-Establishment "＜Event the value of extracting each related child elements in the daughter element obtains.

Body part is the session state information with XML document form record, because session state information has been described out the process of whole session, for example when session set up, when have the user to add, when remove who user, when received CPM message in the session, when sent CPM message in the session, when transmitted file, conversation end when, described the process of whole C PM session truly.And in the CPM session file of mutual CPM message, transmission all as the embedded file of body part, quote association by Content-ID, therefore " Content-Type " of body part is set to " Multipart/related " structure type, in this structure, the XML document of CPM session state information is as main part, and in the session mutual CPM message, the CPM file of transmission etc. all as embedded resource.

Accessories section is recorded in mutual continuous media flow object in this CPM session, as the accessories section of conversation history log file, identifies by " Content-Disposition=attachment ".

The duration of CPM session is longer, CPM participates in function server when the initial SIP INVITE that receives establishment CPM session asks, to at first create temp directory, and under this catalogue, create the XML file of new CPM session state information, in order to the corresponding session status change events information of record in the process of CPM session; Content for the CPM message of transmitting in the CPM session (page message, big message), CPM file, continuous media flow object (audio frequency, video) is kept under this temp directory as unique file.When CPM participation function server receives the SIP BYE request that finishes this CPM session, CPM participates in function server and creates new CPM conversation history log file, and from temp directory, obtain the XML file of CPM session state information and mutual CPM message, CPM file, CPM continuous media flow object log file in the CPM conversation procedure, and these resource files are packaged into CPM conversation history log file according to the definition of storage and uniform form, concrete flow process is as described below:

Step 1001, when CPM participates in function server and receives the initial SIP INVITE request message of representative " establishment CPM dialog events ", CPM participates in function server will at first create a temp directory, in order to be kept at the session state information record that produces in this CPM conversation procedure, mutual CPM message, CPM file and CPM continuous media flow object content or the like.The directory name of this temp directory can use the contribution identifier of the affiliated talks identifier of this CPM session and this CPM session to constitute, and carries out unique identification.

Step 1002, CPM participates in function server is created session state information under this temp directory XML document, is used at the CPM conversation procedure session status event information being carried out record.CPM participates in function server will carry out record to " creating the CPM dialog events " relevant information in the session state information XML document.

Step 1003, in the CPM conversation procedure, as long as variation has taken place in session status, leave session, participant as the participant and initiatively add session, invite the participant to add session, remove participant etc., all can in the XML document of CPM session state information, carry out respective record; The CPM message of transmitting in the CPM session, CPM file also need the content of these CPM message, CPM file is kept under the temp directory as resource file independently except will writing down in CPM session state information XML document.

Step 1004, transmission continuity Media Stream (as audio frequency, video etc.) carries out record by media plane in the CPM conversation procedure, and the formation log file is kept under the temp directory of this CPM session when conversation end.

Step 1005, when CPM participation function server receives the SIP BYE request message of representative " CPM conversation end incident ", CPM participates in function server will create new CPM conversation history log file, each resource file that temp directory is stored down encapsulates according to the storage and uniform form, specifically comprises:

The formation method of a, CPM conversation history log file " head " content:

A1, CPM participate in finding＜Type the XML document of the session state information of function server from temp directory under〉the daughter element value for " Session-Establishment " correspondence＜Event daughter element, this element has write down the relevant information of CPM conversation establishing incident;

A2, CPM participate in function server from this＜Event obtain＜TimeStamp under the daughter element value of daughter element, the value as CPM conversation history log file head " Date " header field writes down the creation-time of this CPM session;

A3, CPM participate in function server from this＜Event obtain＜Subject under the daughter element value of daughter element, the value as CPM conversation history log file head " Subject " header field writes down the subject information of this CPM session;

A4, CPM participate in function server from this＜Event obtain＜Initiator under the daughter element value of daughter element, as the value of CPM conversation history log file head " From " header field, write down initiator's station address information of this CPM session;

A5, CPM participate in function server from this＜Event obtain＜Participants-List under the daughter element under the daughter element each＜entry the value of daughter element, and use "; " separate, constitute recipient's station address character string, as the value of CPM conversation history log file head " To " header field, write down this CPM session by invited party station address information;

It is " Multipart/Mixed " that a6, CPM participate in function server setting " Content-Type ", and the value of " boundary " delimiter is set;

It is " CPM Session RecordFile " that a7, CPM participate in function server setting " Content-Description ", and the simple description to the log file content is provided;

The formation method of b, CPM conversation history log file " body part " content:

" Content-Type " that b1, CPM participation function server is provided with body part is " Multipart/Related " type, and the value of " boundary " delimiter is set;

B2, CPM participate in the content that function server obtains the XML of session state information under the temp directory, as the main part content of body part " Multipart/Related " structure;

B3, CPM participate in function server obtains the blotter of the CPM message transmitted the CPM conversation procedure, CPM file under temp directory content, embedded resource as body part " Multipart/Related " structure, these embedded resources represent by " Content-ID ", and in the XML document of session state information by＜Resource the value of element record " Content-ID " carries out related with embedded resource the session status incident;

The formation method of c, CPM conversation history log file " accessories section " content:

CPM participates in function server and obtain continuous media flow object log file content (for example audio sound-recording, video record file etc.) mutual in the CPM session under temp directory, with its attachment content as the conversation recording file, and setting " Content-Type " is " Audio " or " Video " type respectively, it is " Attachment " that " Content-Disposition " header field is set, and expression is handled as annex.

Further specify with the consolidation form encapsulation of specific embodiment more below meeting history record.

Embodiments of the invention one are the storage and uniform form constructed embodiment of CPM Message Record, in embodiments of the invention one, suppose that Bob user has opened the meeting history record function, then in the talks process, receive one during from the SIP MESSAGE message Bob user's session outside when the CPM for Bob user service participates in function server, the structure of message with the contents are as follows shown in:

MES SAGE sip:alice@domain.com SIP/2.0 Via:SIP/2.0/TCP user1pc.domain.com; Branch=z9hG4bK776sgdkse Max-Forwards:70 Subject:How are you! From:<sip:bob@domain.com>Tag=49583 // message sender address To:<sip:alice@domain.com>// message receiver address P-Asserted-Identity:<sip:bob@domain.com>User-agent:CPM-Service/OMA1.0 Accept-Contact:*; + g.oma.cpm.pagermsg; Require; Explicit CPM-Conversation-ID:Conversation-id CPM-Contribution-ID:Contribution-id Call-ID:asd88asd77a@1.2.3.4 CSeq:1MESSAGE Content-type:Message/CPIM // type of message Content-Length:180 // message-length // null, separate message head and message body From:Alice Huang<alice@home1.net>To:Bob Li<bob@home1.net>DateTime:2000-12-13T13:40:00-08:00 Subject:the weather will be fine today Content-type:text/xml; Charset=utf-8

??Content-ID：<1234567890@foo.com>??<body>??Here?is?the?text?of?my?message.??</body>

The CPM participation function server of serving for Bob user obtains relevant information from this SIP MESSAGE message, and is assembled into the CPM Message Record file of storage and uniform form, and the concrete example of the CPM Message Record that final structure forms is as follows:

Date:Wed, the temporal information of 15Apr 200917:09:33+0800 // this message of reception, can from the DateTime header field of Message/CPIM, obtain Subject:How are you! The theme of // this CPM message, can from the Subject header field of Message/CPIM, obtain From:sip:bob@example.com // message sender address, from SIP MESSAGE, or obtain To:sip:alice@example.com in the From header field of SIP INVITE, sip:joe@example.com // message receiver address, from SIP MESSAGE, or obtain the contribution identifier Content-Type:Message/CPIM Content-Description:CPM Message // file description of talks identifier Keywods:Contribution-id // this CPM message of talks under Reference:Conversation-id // this CPM message in the corresponding header field of SIP INVITE, represent that this is a CPM message file // null, separate message head and message body From:Bob＜sip:bob@example.com〉To:Alice＜sip:alice@example.com〉DateTime:2000-12-13T13:40:00-08:00 Subject:How are you! Content-type:text/xml; Charset=utf-8 //content of Message/CPIM carrying is

XML document Content-ID:<1234567890@foo.com><body>Here is the text of my message.</body>

As implied above, in fact the storage and uniform form of CPM message is similar to " mail " that an envelope meets the MIME form, " mail head " part is by extracting relevant header field structure in SIP MESSAGE, SIP INVITE and Message/CPIM, though certain information redundancy is arranged, but provide these information at the mail header branch, be for the ease of the summary info of CPM message being provided to the message stores client, being convenient to carry out follow-up operations such as search.

" mail body " part then can be extracted from SIP MESSAGE message or MSRP SEND message and be duplicated fully, it is not made amendment, and keeps its original MIME structure, is convenient to follow-up possible operations such as forwards.

CPM participates in function server and according to above-mentioned storage and uniform form the CPM message of page-mode or big message pattern is changed, and behind the CPM Message Record object behind the formation storage and uniform form, submits to MSS again and stores.MSS or MSC just can manage or visit CPM Message Record object according to unified storage format like this.

Embodiments of the invention two are the constructed embodiment of CPM session state information.In embodiments of the invention two, suppose that Bob user has opened the meeting history record function, when the CPM for Bob user service participates in function server receive a 1-1CPM session invitation SIP INVITE in the talks process, the structure of message and the contents are as follows shown in:

??INVITE?sip:alice@home1.net?SIP/2.0??Via：SIP/2.0/UDP?192.168.1.37：9909；rport＝9909；branch＝z9hG4bK1526941838??Route：<sip:CPMConversationSever@192.168.1.92：11101；lr>??From：<sip:bob@home?1.net>；tag＝1024535264??To：<sip:alice@home?1.net>

??Call-ID：1161603754@192.168.1.37??CSeq：20INVITE??Contact：<sip:bob@192.168.1.37：9909>??Max-forwards：70??User-agent：CPM-Service/OMA1.0??Subject：Invite?you?to?CPM?Session！??Expires：120??P-asserted-identity：<sip:alice@home1.net>??Privacy：id??Accept-Contact：*；+g.oma.cpm.session；require；explicit??Session-expires：1800；refresher＝uac??CPM-Conversation-ID：ConversationmOXUaazCH??CPM-Contribution-ID：ContributionmOXUaazCH??Content-Type：application/sdp??Content-Length：243??v＝0??o＝-20090924?20090924IN?IP4192.168.1.37??s＝-??t＝0?0??m＝audio?3458RTP/AVP?96??c＝IN?IP4192.168.1.37??a＝rtpmap：96G726-32/8000

After the CPM participation function server for Bob user's service receives SIP INVITE request as implied above, think that Bob user has initiated a new CPM session, so participating in function server, CPM will be this CPM conversation establishing temp directory, create CPM session state information XML document, and construct new＜Event〉unit usually writes down the CPM session state information, in the following example shown in:

＜Session-Event〉// root element＜Event〉// each＜Event〉element represents a session status incident

<type>Session-Establishment</Type>Incident is set up in // session<timeStamp>Wed, 15Apr 200917:09:33+0800</TimeStamp><initiator>Sip:bob@example.com</Inviter>// initiator station address<participant-List>// by the invited party address list<entry uri＝″sip:alice@example.com″><display-name>AlicePC</display-name><accept>Yes</accept>// whether accept the invitation</entry></Participant-List></Event></Session-Event>

In the process of this CPM session, CPM participates in function server and receives CPM page message in the session, and by SIP MESSAGE message bearing, the structure of this SIP MESSAGE message is as follows:

MESSAGE sip:alice@domain.com SIP/2.0 Via:SIP/2.0/TCP user1pc.domain.com; Branch=z9hG4bK776sgdkse Max-Forwards:70 Subject:How are you! From:＜sip:bob@domain.com 〉; Tag=49583 // message sender address To:＜sip:alice@domain.com 〉; Tag=8934 // message receiver address P-Asserted-Identity:＜sip:bob@domain.com〉User-agent:CPM-Service/OMA1.0 Accept-Contact:*; + g.oma.cpm.pagermsg; Require; Explicit CPM-Conversation-ID:Conversation-id CPM-Contribution-ID:Contribution-id Call-ID:asd88asd77a@1.2.3.4 CSeq:1MESSAGE Content-type:Message/CPIM // type of message Content-Length:180 // message-length

// null, separate message head and message body From:Alice Huang<alice@home1.net>To:Bob Li<bob@home1.net>DateTime:2000-12-13T13:40:00-08:00 Subject:the weather will be fine today Content-type:text/xml; Charset=utf-8 Content-ID:<1234567890@foo.com><body>Here is the text of my message.</body>

CPM participates in function server and receives after this SIP MESSAGE message, be judged as CPM page message in the session, thereby the XML document to this CPM session state information is upgraded, add new＜Event〉element, the incident that Bob user is sent CPM message in the session is carried out record, and the session state information XML document after the renewal is as follows:

<session-Event>// root element<event>// each<event>Element is represented a session status incident<type>Session-Establishment</Type>Incident is set up in // session<timeStamp>Wed, 15Apr 200917:09:33+0800</TimeStamp><initiator>Sip:bob@example.com</Inviter>// initiator station address<participant-List>// by the invited party address list<entry uri＝″sip:alice@example.com″><display-name>AlicePC</display-name><accept>Yes</accept>// whether accept the invitation</entry></Participant-List></Event><event>

<time-Stamp>Wed, 15Apr 200917:10:33+0800</Time-Stamp><type>Send-Message</Type>// transmission message event<init iator>Sip:bob@example.com</Inviter>The sender address of // message<participant-List>The tabulation of // message receiver station address<entry uri＝″sip:alice@example.com″><display-name>AlicePC</display-name><accept>Yes</accept>Whether // recipient successfully receives message</entry><resource>Cid:message1@cpm.com</Resource>// embedded the resource file quoted, cid are represented link</Event></Session-Event>

Participate in the Bob user of this CPM session and Alice user and can send SIP BYE message and finish this CPM session, when CPM participated in function server and receives SIP BYE request from Bob user, the structure of this message was as follows:

??BYE?sip：CPMTemp-SatSep262330072009over@192.168.1.92：11101SIP/2.0??Via：SIP/2.0/UDP?192.168.1.37：9909；rport＝9909；branch＝z9hG4bK2062599839??From：<sip:bob@home1.net>；tag＝1024535264??To：<sip:alice@home1.net@>；tag＝1206196857??Call-ID：1161603754@192.168.1.37??CSeq：21BYE??Contact：<sip:bob@192.168.1.37：9909>??Max-forwards：70??User-agent：CPM-Service/OMA1.0??P-asserted-identity：<sip:bob@home?1.net>??Content-Length：0

After CPM participation function server receives SIP BYE message as implied above, find corresponding CPM session by the Session ID that carries among the Request-URI, then the XML document of this CPM session state information is upgraded, add new＜Event〉element, the conversation end incident is carried out record, and the session state information XML document after the renewal is as follows:

<session-Event>// root element<event>// each<event>Element is represented a session status incident<type>Session-Establishment</Type>Incident is set up in // session<timeStamp>Wed, 15Apr 200917:09:33+0800</TimeStamp><initiator>Sip:bob@example.com</Inviter>// initiator station address<participant-List>// by the invited party address list<entry uri＝″sip:alice@example.com″><display-name>AlicePC</display-name><accept>Yes</accept>// whether accept the invitation</entry></Participant-List></Event><event><time-Stamp>Wed, 15Apr 200917:10:33+0800</Time-Stamp><type>Send-Message</Type>// transmission message event<initiator>Sip:bob@example.com</Inviter>The sender address of // message<participant-List>The tabulation of // message receiver station address<entry uri＝″sip:alice@example.com″><display-name>AlicePC</display-name><accept>Yes</accept>Whether // recipient successfully receives message</entry><resource>Cid:message 1@cpm.com</Resource>// embedded the resource file quoted, cid are represented link</Event>

<event><timeStamp>Wed, 15Apr 200917:42:33+0800</TimeStamp><type>Session-End</Type>// conversation end</Event></Session-Event>

As implied above, be the XML document of the complete session state information of this CPM session of record, the document is stored under the temp directory as the temporary information of this conversation history record, waits for that CPM participates in function server it is packaged into the conversation history log file.

Embodiments of the invention three are the constructed embodiment of CPM conversation history record.In enforcement three of the present invention, suppose that Bob user has opened the meeting history record function, the CPM conversation procedure shown in the foregoing description two continues, CPM participates in function server and will preserve session state information in the CPM conversation procedure, to the CPM message of transmitting in the session, the CPM file is preserved, transmission continuity Media Stream object in the session is preserved, receive the SIPBYE request of this CPM session of end when CPM participation function server after, CPM participation function server will scan all the temporary resource files under this CPM session temp directory, the XML file of session status change information will write down, writing down the CPM message of transmission in the session, the CPM file, the temporary file of CPM continuous media flow object is packaged into CPM conversation history log file together, finally constitutes theing contents are as follows shown in the example of CPM conversation history log file:

Date:Wed, 15Apr 200917:09:33+0800 // conversation establishing time Subject:How are you! The founder address To:sip:alice@example.com of theme From:sip:bob@example.com // this session of // this session, the contribution identifier Content-Type:multipart/mixed of talks identifier Keywods:Contribution-id // this CPM session of talks under the participant addresses Reference:Conversation-id of sip:joe@example.com // this CPM session // this CPM session; Boundary=next//whole file is the mixed form, and separator is next Content-Description:CPM Session History // file description in full, represents that this is a meeting

History file--next // full text first begins words, i.e. conversation history recorded text Part of Co ntent-Type:multipart/related; Boundary=session // first is the object of an association type, promptly have embedded resource, and separator is decided to be session--the main part of the text of session // conversation history record begins, i.e. session state information XML document Content-Type:text/xml; Charset=utf-8 Content-ID:<sessionhistory@cpm.com>Content-Description:Session Status<session-Event>// root element<event>// each<event>Element is represented a session status incident<type>Session-Establishment</Type>Incident is set up in // session<timeStamp>Wed, 15Apr 200917:09:33+0800</TimeStamp><initiator>Sip:bob@example.com</Inviter>// initiator station address<participant-List>// by the invited party address list<entry uri＝″sip:alice@example.com″><display-name>AlicePC</display-name><accept>Yes</accept>// whether accept the invitation</entry></Participant-List></Event><event><time-Stamp>Wed, 15Apr 200917:10:33+0800</Time-Stamp><type>Send-Message</Type>// transmission message event<initiator>Sip:bob@example.com</Inviter>The transmission of // message

The address, side<participant-List>The tabulation of // message receiver station address<entry uri＝″sip:alice@example.com″><display-name>AlicePC</display-name><accept>Yes</accept>Whether // recipient successfully receives message</entry><resource>Cid:message 1@cpm.com</Resource>// embedded the resource file quoted, cid are represented link</Event><event><timeStamp>Wed, 15Apr 200917:42:33+0800</TimeStamp><type>Session-End</Type>// conversation end</Event></Session-Event>--session // embedded resource 1 (i.e. the CPM message of Fa Songing) beginning Content-Type:Message/CPIMContent-Description:CPM Message // file description, represent that this is a CPM message file // null, separate message head and message body From:Bob<sip:bob@example.com>To:Alice<sip:alice@example.com>DateTime:2000-12-13T13:40:00-08:00Subject:How are you! Content-type:text/xml; Charset=utf-8 //content of Message/CPIM carrying is XML document Content-ID:<1234567890@foo.com>

<body>Here is the text of my message.</body>--annex 1 beginning of next // conversation history record, i.e. session recorded audio file Content-Type:audio/mid Content-Transfer-Encoding:base64 Content-Disposition:Attachment; Filename=" SessionAudioRecord.mid "; // audio file is set to type of attachment, can not represent immediately, need user's selection operation, the file of annex SessionAudioRecord.mid Content-Description:The audio record of CPM S ession//attachment content by name is described jiosjfiosfjioseir34u28938==043ndjf.... // annex coding, omit--annex 2 beginning, i.e. the session video file Content-Type:video/mpeg Content-Transfer-Encoding:base64 Content-Disposition:Attachment of next // conversation history record; Filename=" SessionVideoRecord.mpg "; // video file is set to type of attachment, can not represent immediately, need user's selection operation, the file of annex SessionVideoRecord.mpg Content-Description:The video record of CPM Session // attachment content by name is described jiosjfiosfjioseir34u28938==043ndjf.... // annex coding, omit--next--// full text end mark, the end of expression whole session history file

As implied above, just can intactly note the process and relevant resource of whole C PM session by so a CPM conversation history log file, CPM participates in function server and should rest on the signalling path and media channel of CPM session, relevant information in the CPM conversation procedure is carried out record, form after a CPM conversation history record object according to the definition of storage and uniform form, submit to MSS again and store.

For realizing the meeting history record processing method of above-mentioned converged message service, the present invention also provides a kind of meeting history record treatment system of converged message service, and as shown in Figure 3, this system comprises: CPM participates in function server 10, MSS 20 and MSC 30.

CPM participates in function server 10, is used for obtaining and the relevant information of talking from SIP signaling, MSRP message and RTP Media Stream, and this information being encapsulated as meeting history record according to unified storage format in the process that realizes the meeting history record function.MSS 20, are used for according to unified storage format meeting history record being stored.MSC 30, are used for according to unified storage format meeting history record being conducted interviews.

Wherein, CPM participates in function server and also is used for, for CPM page message, from SIP MESSAGE message, extract " Subject " header field, " CPM-Conversation-ID " header field, " CPM-Contribution-ID " header field, " CPM-ReplyTo-Contribution-ID " header field, " P-Asserted-Identity " header field, the value of " Request-URI " parameter, " Content-Type " is that value and " Content-Type " of " application/resource-lists+xml " message body part is the value of " message/cpim " message body, and structure meets the CPM Message Record file of the storage and uniform form of RFC 822 formal definitions;

For the big message of CPM, from the SIP INVITE request message of consulting to set up the MSRP media channel, extract " Subject " header field, " CPM-Conversation-ID " header field, " CPM-Contribution-ID " header field, " CPM-ReplyTo-Contribution-ID " header field, " P-Asserted-Identity " header field, the value of " Request-URI " parameter, " Content-Type " is the value of " application/resource-lists+xml " message body part, and " Content-Type " is the value of " message/cpim " message body in the MSRP SEND message, and structure meets the CPM Message Record file of the storage and uniform form of RFC 822 formal definitions;

For the CPM file transfer, from the SIP INVITE request message of consulting to set up the MSRP media channel, extract " Subject " header field, " CPM-Conversation-ID " header field, " CPM-Contribution-ID " header field, " CPM-ReplyTo-Contribution-ID " header field, " P-Asserted-Identity " header field, the value of " Request-URI " parameter, " Content-Type " is the value of " application/resource-lists+xml " message body part, and " Content-Type " is the value of " message/cpim " message body in the MSRP SEND message, and structure meets the CPM Message Record file of the storage and uniform form of RFC 822 formal definitions;

For the CPM session, in conversation procedure, from SIPINVITE, the SIP BYE relevant, SIP REFER, SIP MESSAGE message, extract the value of relevant header field with this CPM session status incident, the value of the relevant header field that foundation is extracted is created the XML document of session state information, and CPM message, CPM file, the RTP Media Stream that transmits in the session process saved as independently temporary resource file; When described CPM conversation end, the CPM conversation history log file that the XML document and the temporary resource file of session status information is encapsulated as the storage and uniform form that meets RFC 822 formal definitions.

The above is preferred embodiment of the present invention only, is not to be used to limit protection scope of the present invention.

Claims

1. the meeting history record processing method of a converged message service is characterized in that, this method comprises:

2. according to the meeting history record processing method of the described converged message service of claim 1, it is characterized in that described meeting history record is made up of CPM Message Record file, CPM file transfer history file, CPM conversation history log file.

3. according to the meeting history record processing method of the described converged message service of claim 2, it is characterized in that for the CPM page message in the talks process, described obtaining and the relevant information of talking is specially:

4. according to the meeting history record processing method of the described converged message service of claim 3, it is characterized in that, described the information of obtaining be encapsulated as meeting history record according to unified storage format, be specially:

5. according to the meeting history record processing method of the described converged message service of claim 2, it is characterized in that for the big message of the CPM in the talks process, described obtaining and the relevant information of talking is specially:

6. according to the meeting history record processing method of the described converged message service of claim 5, it is characterized in that, described the information of obtaining be encapsulated as meeting history record according to unified storage format, be specially:

7. according to the meeting history record processing method of the described converged message service of claim 2, it is characterized in that for the CPM file transfer in the talks process, described obtaining and the relevant information of talking is specially:

8. according to the meeting history record processing method of the described converged message service of claim 7, it is characterized in that, described the information of obtaining be encapsulated as meeting history record according to unified storage format, be specially:

9. according to the meeting history record processing method of claim 4,6 or 8 described converged message services, it is characterized in that described value according to the Request-URI parameter is determined the type of CPM page message, is specially:

10. according to the meeting history record processing method of the described converged message service of claim 2, it is characterized in that, for the CPM session, described obtaining and the relevant information of talking, and described information is encapsulated as meeting history record according to unified storage format is specially:

11. the meeting history record treatment system of a converged message service is characterized in that, this system comprises: CPM participates in function server, MSS and MSC, wherein,

12. meeting history record treatment system according to the described converged message service of claim 11, it is characterized in that, described CPM participates in function server and is further used for, for CPM page message, from SIPMESSAGE message, extract the Subject header field, the CPM-Conversation-ID header field, the CPM-Contribution-ID header field, the CPM-ReplyTo-Contribution-ID header field, the P-Asserted-Identity header field, the value of Request-URI parameter, Content-Type is that the value and the Content-Type of application/resource-lists+xml message body part is the value of message/cpim message body, and structure meets the CPM Message Record file of the storage and uniform form of RFC 822 formal definitions.

13. meeting history record treatment system according to the described converged message service of claim 11, it is characterized in that, described CPM participates in function server and is further used for, for the big message of CPM, from the SIP INVITE request message of consulting to set up the MSRP media channel, extract the Subject header field, the CPM-Conversation-ID header field, the CPM-Contribution-ID header field, the CPM-ReplyTo-Contribution-ID header field, the P-Asserted-Identity header field, the value of Request-URI parameter, Content-Type is the value of application/resource-lists+xml message body part, and Content-Type is the value of message/cpim message body in the MSRPSEND message, and structure meets the CPM Message Record file of the storage and uniform form of RFC 822 formal definitions.

14. meeting history record treatment system according to the described converged message service of claim 11, it is characterized in that, described CPM participates in function server and is further used for, for the CPM file transfer, from the SIP INVITE request message of consulting to set up the MSRP media channel, extract the Subject header field, the CPM-Conversation-ID header field, the CPM-Contribution-ID header field, the CPM-ReplyTo-Contribution-ID header field, the P-Asserted-Identity header field, the value of Request-URI parameter, Content-Type is the value of application/resource-lists+xml message body part, and Content-Type is the value of message/cpim message body in the MSRPSEND message, and structure meets the CPM Message Record file of the storage and uniform form of RFC 822 formal definitions.

15. meeting history record treatment system according to the described converged message service of claim 11, it is characterized in that, described CPM participates in function server and is further used for, for the CPM session, in conversation procedure, from SIP INVITE, the SIP BYE relevant, SIP REFER, SIPMESSAGE message, extract the value of relevant header field with this CPM session status incident, the value of the relevant header field that foundation is extracted is created the XML document of session state information, and CPM message, CPM file, the RTP Media Stream that transmits in the session process saved as independently temporary resource file; When described CPM conversation end, the CPM conversation history log file that the XML document and the temporary resource file of session status information is encapsulated as the storage and uniform form that meets RFC 822 formal definitions.