CN101789910B - Method and device for implementing session history record in converged message service - Google Patents

Abstract

The present invention provides a method and device for realizing conversation history recording in the integrated message service, including that the CPM participation function receives a message, and detects that the user has enabled the conversation history recording function, and parses and receives the message according to the protocol type of the received message. Received messages and perform the conversation history recording function according to the analysis results. Through the processing logic of the meeting history recording function of the CPM participation function of the present invention, the recording function of message, file transmission and session interaction history in the integrated message service environment is realized.

Description

Method and device for realizing conversation history record in converged message service

technical field

The invention relates to a converged IP message (CPM, Converged IP Messaging) service technology, in particular to a method and device for realizing conversation history records in a converged message service.

Background technique

Among the existing message services, only the instant message (IM) service has the function of conversation history recording. In the SIMPLE-based instant message communication (OMA SIMPLE IM) service specification, the conversation history function of the IM service (Conversation History Function) has been carried out. definition.

The media communication type of the IM service is relatively simple, mainly for message communication of discrete media. The message communication modes of IM include three types: paging mode, large message mode and conversation mode. in,

Paging mode means that the IM client directly sends and receives instant messages through the SIP MESSAGE request, which is suitable for separate short message communication such as short messages or announcements with confirmation information;

The large message mode refers to using the Message Session Relay Protocol (MSRP, Messaging Session Relay Protocol) to send a single IM containing a large amount of data information, such as when carrying multimedia content. In order to use the MSRP protocol to transmit data, a SIP session needs to be established;

Conversational mode refers to the initiation of MSRP channel negotiation through the SIP INVITE request. All IMs are transmitted through the MSRP channel. Conversational mode is not limited to interactive sessions suitable for text content, such as one-to-one conversations, chat groups or Meetings hosted by a single network, individual users can also join and leave sessions at any time.

In order to realize the conversation history recording function in the IM service, the conversation history recording function in the IM server needs to be located on the signaling plane and the media plane at the same time, and execute the following processing logic:

(1) Every time a SIP MESSAGE or MSRP session that needs to be stored is received, the conversation history record function in the IM server checks whether there are enough resources to store the SIP message; if not, the SIP MESSAGE or MSRP session is not recorded and sent to the system Message to the user to indicate that there is not enough space to store history records, end; if there are enough resources, then go to (4);

(2) Every time a MSRP SEND (as a part of the large message mode message) is received and stored to the IM user served by it, the conversation history record function checks whether there are enough resources to store the large message (Large message), if not, Then stop recording the Large message and discard the previously received Large message, then send a system message to the user to indicate that there is not enough space to store the historical record, end; if there are enough resources, then go to (4);

(3) Every time a MSRP SEND (as part of an IM session) is received and stored to an IM user served by it, the conversation history record function checks whether there are enough resources to store the MSRP SEND message; if not, then:

stop logging the message; if the MSRP SEND message is a fragment of a large message interaction, the talk history function should reject this message and other fragments of the large message with an MSRP 413 reply, and send a system message to the user to indicate There is not enough space to store the history record, end; if SEND is part of the conversation interaction, keep the part of the conversation that has been stored, the conversation history record function sends a BYE request to the IM server hosting the meeting to exit the meeting, and sends a system message Give the user an indication that there is not enough space to store the history, end.

If there are enough resources, go to (5);

(4) In the case of a SIP MESSAGE request, store the complete message (including message header and message body);

(5) In the case of an MSRP session, store all relevant header fields From, To, P-Asserted-Identity, Subject, Date of the historical record session establishment messages (INVITE and 200OK).

In the above processing logic, each stored message needs to be assigned a unique history record index (URI format, such as 1234mailserver.example.com); for the large message mode, store the complete MSRP SEND request (including all header fields, IM The timestamp and complete message content when the server receives the message); for session mode, store each complete MSRP SEND request (including all header fields, timestamp and complete message content when the IM server receives the message), and SIP BYE The relevant header field of the request.

Moreover, in the existing conversation history in the IM business, the history is stored in the IM user account book in the storage entity of the IM server; and the metadata is stored in the IM XDMS.

Through the above processing logic, the IM server realizes the function of recording the conversation history, and records the instant messages exchanged during the conversation, whether it is in paging mode, large message mode or conversation mode, all are completely recorded.

The type of communication media in the IM service is relatively single, and what is exchanged in the conversation is only discrete media with instant messages as the carrier (such as text, pictures, audio/video clips, etc.), the types of signaling messages involved and the types of session status information Therefore, when the IM server performs the meeting history recording function, it basically saves a complete SIP MESSAGE message or a complete MSRPSEND message, or saves the relevant header fields of SIP INVITE/SIP 200OK and other messages methods of storage, etc.

In the IM business, the actual content of the conversation history is stored in the IM server, and the metadata related to the conversation history is additionally stored in the IM XML Document Management Server (XDMS). The method of separate storage makes the IM client need to use the XCAP protocol to access the IM XDMS to obtain the corresponding information when obtaining the meeting history function, and then access the IM server through the SIP protocol to obtain the actual content of the meeting history according to the information, so that The management and operation of interview history become complicated.

With the evolution of network technology, the message communication service provided on the communication network shows a trend of convergence. Therefore, OMA organization provides a converged IP message enabler (CPM enabler, Converged IP Messaging Enabler ), the CPM enabler can span different access networks and be built on a unified IP core network to support one-to-one, one-to-many and various media types between end users and applications (such as text, images, audio/video clips, binary files, audio/video streams).

In a converged message communication environment, the CPM enabler provides CPM services to users in units of CPM talks to enable information interaction. During the communication process, users hope that the network side will record and store the historical interaction information of the CPM talks they participate in. , so that when needed, the historical interaction record information of the CPM talks that the user has participated in can be accessed by sending a request to the server on the network side, so as to truly reproduce the entire process of the talks that the user has participated in; Manage the conversation history information belonging to the user himself stored on the side server.

In this article, the server that provides CPM users with the function of storing CPM conversation history records is called a CPM message storage server, and the CPM message storage client accesses the CPM message storage server to store the CPM conversation history records and related content belonging to the CPM user. Access and manage, and display the view and content of the meeting to CPM users by analyzing the meeting history information obtained from the network side.

A CPM session describes the behavior of information exchange between communication parties using the CPM enabler functional entity. A CPM session consists of any number of CPM messages, CPM file transfers, and CPM sessions that are exchanged outside the session. Among them, a CPM message is an information body that can contain multiple discrete or discontinuous media (such as text, pictures, audio clips, video clips, etc.); The receiving user must explicitly confirm the receiving process before receiving any data of the transferred file; a CPM session is a logical connection between two or more participants that lasts for a period of time, and can be used for participants to exchange continuous information in real time Sexual media can also be used to exchange discrete media. CPM message exchange and CPM file transfer can be performed within the CPM session or outside the CPM session. It is generally believed that each CPM meeting contains only one CPM session at a specific time. Users can participate in multiple CPM sessions in parallel.

A CPM meeting history is a stored representation of a CPM meeting. Authorized persons in charge can obtain and store the information they exchanged during the CPM conversation, and store the information as a CPM conversation history record in the CPM message storage server provided by the CPM service provider. At this time, a CPM message exchanged outside the CPM session is stored as a CPM message record, a CPM file transfer outside the CPM session is stored as a CPM file transfer history record, and a CPM session is stored as a CPM session History (including data such as intra-session CPM messages, intra-session CPM file transfers, and continuous media segments of intra-session interactions). Therefore, from the perspective of storage representation, the CPM conversation history can be described as a collection of CPM message records, CPM file transfer history and CPM session history.

In the CPM service, since it provides a converged message service, it involves more types of communication media. In addition to discrete media, it can also provide IP-based voice stream and video stream communication, that is, CPM session. CPM sessions can be further divided into 1-1CPM sessions and CPM group sessions. In a group session, due to the occurrence of various session state change events such as participants being removed, invited, voluntarily joined, and voluntarily left, involving SIP INVITE, SIP REFER, SIP 200OK, SIP BYE and other SIP signaling interactions, and these SIP messages represent different semantics in different session contexts. If the conversation history recording function in the existing IM business is also used, It is impossible to truly record the state change information of the entire session only by completely saving these interaction information.

For example, for message records, if only the conversation history record function in the IM service is used to completely store a SIP MESSAGE or MSRP SEND, then when the CPM message storage client and the CPM message storage server parse the content of these conversation history records, It is also necessary to understand details such as the format of these communication protocol messages, that is to say, directly applying the conversation history recording function in the existing IM service to the CPM service has poor versatility and scalability.

The processing logic adopted by the IM conversation history record is that whenever the IM server receives an instant message, it starts to execute the recording process, and does not take into account that if the message fails to be sent (the recipient does not receive it successfully), the conversation history How the record should be updated (for example, delete the failed message record or add the failed record information). In short, the meeting history record function of the IM service is a relatively simple functional prototype, without considering the complete processing logic; and in the integrated message communication service, providing users with a complete meeting history record is a very important part of the CPM service. feature, it is required that the meeting history record function has a more complete processing logic. For example, in the CPM business, the meeting history record function and related metadata can be stored on the message storage server in a unified manner. Both the message storage client and the CPM participation function access the message storage server through the IMAP4 protocol. Therefore, the traditional IM business meeting The processing logic of the history record function cannot be directly reused in the CPM business. Based on the nature of the integrated message service provided by the CPM service and its unique protocol architecture characteristics, it is necessary to define a new and suitable for the meeting history record function of the CPM service. processing logic.

Contents of the invention

In view of this, the main purpose of the present invention is to provide a method and device for realizing conversation history recording in a converged message service, so as to realize the recording function of message, file transmission and session interaction history in a converged message service environment.

In order to achieve the above object, technical solution of the present invention is achieved in that way:

A method for implementing conversation history records in a fusion message service, comprising:

The integrated IP message CPM participation function receives a message and detects that the user has enabled the conversation history recording function, analyzes the received message according to the protocol type of the received message, and executes the conversation history recording function according to the analysis result.

When the protocol type of the received message is a SIP protocol message, the parsing the received message and executing the conversation history record function according to the parsing result includes:

Call the SIP protocol stack to analyze the received SIP protocol message, when it is resolved as SIP INVITE, process SIP INVITE message; when resolved as SIP BYE, process SIP BYE message; when resolved as SIP REFER, perform SIP REFER Message processing; when it is parsed as a SIP MESSAGE, perform SIP MESSAGE message processing.

When the protocol type of the received message is an MSRP protocol message, the function of parsing the received message and executing the conversation history recording function according to the parsing result includes:

Call the MSRP protocol stack to parse the received MSRP protocol message, and when it is parsed as MSRPSEND, process the MSRP SEND message.

If the continuous media stream packet is received and it is detected that the CPM session recording function is enabled, the method also includes:

The CPM participation function records the continuous media streams of the parties involved in the session, and enables the media mixing function to mix the media streams of the parties participating in the CPM session, and preserve the mixed media stream data;

When the CPM session is over, the CPM participation function extracts the mixed media stream data packets cached locally, encodes them according to the storage format requirements of the session history record, and then encodes and encapsulates the media stream object into the CPM session history record object.

Described SIP INVITE message processing comprises:

The CPM participation function caches the SIP INVITE message locally, waits to receive the success or failure response message returned by the receiver and caches it;

The CPM participation function checks the Accept-Contact header field of the SIP INVITE message and the CPM feature label carried in the Contact header field, and the temporary SIP session establishment request message set up for the CPM large message transmission indicated by the CPM feature label, or for The temporary SIP session establishment request message established by the CPM file transfer, or the SIP session establishment request message related to the CPM session event is processed accordingly.

The processing of the temporary SIP session establishment request message set up for the CPM large message transmission includes:

When it is judged that it is a temporary SIP session establishment request message set up for the large message transmission in the CPM session, then, find the CPM session to which the CPM large message belongs by calculating and comparing the Dialog-ID, and find the corresponding CPM session The session history record object, extract relevant information from the INVITE message to record; according to the success or failure response message of the INVITE request, record it in the CPM session history record object; wait to receive MSRP SEND at the port of the specified MSRP media channel information;

When it is judged that the temporary SIP session establishment request message is set up for the large message transmission outside the CPM session, then,

After judging that the SIP temporary session is established successfully according to the response message, the CPM participation function creates a new CPM message record object, and extracts relevant information from the SIP INVITE request message to record according to the unified storage format of the CPM message; Wait for the MSRP SEND message to be received at the port of the specified MSRP media channel.

The processing of the temporary SIP session setup request message set up for the CPM file transfer includes:

After judging that it is a temporary SIP session establishment request message established for the file transfer in the CPM session, then, by calculating and comparing the Dialog-ID, find the CPM session to which the CPM file belongs, and find the session history record of the corresponding CPM session Object, extract relevant information from the INVITE message for recording; record in the CPM session history record object according to the success or failure response message of the INVITE request; wait to receive the MSRP SEND message at the port of the specified MSRP media channel;

When it is judged that it is a temporary SIP session establishment request message established for file transfer outside the CPM session, and it is judged that the SIP temporary session is established successfully according to the response message, then,

Described CPM participation function creates a new CPM file transmission history record object, and according to the regulation of the unified storage format of CPM file transmission history record, extracts relevant information from this SIP INVITE request message and records; The port waits to receive MSRP SEND messages.

The processing of the SIP session establishment request message related to the CPM session event includes:

When it is judged that the SIP session establishment request message related to the CPM session event is a session establishment request message initiated for establishing a new CPM session, then the CPM participation function creates a new CPM session history record in the local storage space Object; According to the provisions of the storage format of the CPM session history record, extract relevant information from the SIP INVITE message and record it; according to the response message of success or failure returned by the INVITE message, perform the result of the CPM session creation event records, also as part of this CPM Session History object;

When it is judged that the SIP session establishment request message related to the CPM session event is a session join request message initiated by a CPM user to apply for joining an ongoing CPM session, then, find the SIP session identifier indicated in the Request-URI The corresponding CPM session history object; according to the storage format of the session history record, extract relevant information from the SIP INVITE message and record it; according to the success or failure response message returned to the INVITE message, add the request to CPM The results of session events are logged, also as part of the CPM Session History object.

The method further includes: checking the Request-URI of the SIP INVITE request message,

If the value of Request-URI is a CPM session identifier, then the SIP INVITE request message is a session joining request message initiated by a CPM user for applying for joining an ongoing CPM session;

If the value of Request-URI is the address of the CPM control function, and the tag parameter in the To header field is empty, then the SIP INVITE request message is a session establishment request message initiated for an ongoing Ad-hoc group CPM session ;

If the value of Request-URI is the address of the CPM user, and the tag parameter in the To header field is empty, then the SIP INVITE request message is a session establishment request message initiated for establishing a new 1-1CPM session;

If the value of Request-URI is the address of the CPM group, and the tag parameter in the To header field is empty, then the SIP INVITE request message is a session establishment request message initiated for establishing a new predefined group CPM session.

Described SIP BYE message processing comprises:

The CPM participation function caches the SIP BYE message locally, waits to receive the success or failure response message returned by the receiver and caches it, and then parses the SIP BYE message when judging that the SIP BYE message is sent successfully according to the response message ,

If the SIP BYE message is that the CPM user leaves the session, or the entire CPM session ends, or the temporary SIP session for transmitting a CPM large message ends and the transmission process of a large message within the session ends, or the temporary SIP session for transmitting a CPM file ends and is When the large message transmission process in the session ends, find the corresponding CPM session history record object;

If the SIP BYE message is the end of the temporary SIP session for transmitting the CPM large message and the end of the large message transmission process outside the session, then find the corresponding CPM message record object;

If the SIP BYE message is the end of the temporary SIP session for transferring the CPM file and the end of the file transfer process outside the session, then find the corresponding CPM file transfer history record object;

After the record object is obtained, the relevant CPM session history record object, CPM message record object or CPM file transfer history record object is updated according to the judgment result.

Described SIP REFER message processing comprises:

The CPM participation function caches the SIP REFER message locally, waits for receiving and caching the response message of success or failure returned by the receiver, judges that the SIP REFER message is successfully sent according to the response message, and carries the SIP REFER message through the Request-URI. The value of the CPM session identifier, and obtain the value of the method parameter in the Refer-To header field of the SIPREFER message:

If the value of the method parameter is BYE, write the session status event of the removed user in the CPM session history object, and extract relevant information from the SIP REFER message for recording;

If the value of the method parameter is INVITE, write the session state event inviting the user to join in the CPM session history record object, and extract relevant information from the SIP REFER message for recording.

Described SIP MESSAGE message processing comprises:

The CPM participation function buffers the SIP MESSAGE message locally, waits to receive the success or failure response message returned by the receiver and caches it, and judges that the SIPMESSAGE message is sent successfully according to the response message; parses the SIP MESSAGE message,

If there is a tag parameter in the To header field of the SIP MESSAGE message, it is determined that the SIPMESSAGE message is a CPM session message, then find the CPM session that matches the SIP MESSAGE message, and extract relevant information from the SIP MESSAGE request message. Enter the corresponding CPM session history record object; and according to the success or failure response message returned by the MESSAGE message, record the result sent by the CPM message, also as a part of the CPM session history record object;

If the tag parameter in the To header field of the SIP MESSAGE message is empty, then it is judged that it is a message outside the CPM session, then, after judging that it has been successfully sent according to the response message to the SIP MESSAGE message, the CPM participation function will create a new CPM Message record object, and extract relevant information from the SIP MESSAGE request message for recording according to the storage format of the CPM message.

The MSRP SEND message processing includes:

When the CPM participation function caches the MSRP SEND message locally, waits to receive the success or failure response message returned by the receiver and caches it, if a success response message is received,

Parse the MSRP SEND message, if the MSRP SEND message is not fragmented, find the corresponding conversation history record object through the receiving port number of the MSRP SEND message, and record the process of the CPM message corresponding to the MSRP SEND message, or CPM File transfer recording process, or CPM session history recording process for corresponding processing;

If the MSRP SEND message is a fragment, it is further judged whether the fragment is the last fragment, and it is the last fragment, and each MSRP SEND message fragment belonging to a large message is assembled to form a complete MSRP SEND large message; find the corresponding conversation history record object through the receiving port number of the MSRP SEND message, and perform corresponding actions according to the CPM message recording process, CPM file transfer recording process, or CPM session history recording process corresponding to the MSRP SEND message deal with.

The processing of the corresponding CPM message recording process is: obtain the content in the MSRP SEND message, as the content of the CPM large message transmitted outside the session, encapsulate it in the corresponding CPM message recording object, and form the final CPM message recording object;

The processing of the corresponding CPM file transmission recording process is: obtain the content in the MSRP SEND message, as the content of the CPM file transmitted outside the session, encapsulate it in the corresponding CPM file transmission history record object, and form the final CPM file transmission history object;

The processing of the corresponding CPM session history record process is: obtain the content in the MSRP SEND message, encapsulate it into the corresponding CPM session history record object as a large message or file transmitted in the CPM session, and update it.

The CPM participation function inserts itself as a SIP back-to-back user agent B2BUA on signaling and media channels.

A device for achieving conversation history recording in a fusion message service, at least including a receiving module, a judging module, and a recording module, wherein,

The receiving module is used to receive the message and output the recording module to notify the judging module;

The judging module is used to receive a notification from the receiving module, detect whether the user has enabled the conversation history recording function, and send a recording notification to the recording module when it is enabled;

The recording module is configured to receive the recording notification, analyze the received message according to the protocol type of the received message, and execute the conversation history recording function according to the analysis result.

When the protocol type of the received message is a SIP protocol message, the recording module is specifically used to:

Call the SIP protocol stack to analyze the received SIP protocol message, when it is resolved as SIP INVITE, process SIP INVITE message; when resolved as SIP BYE, process SIP BYE message; when resolved as SIP REFER, perform SIP REFER Message processing; when it is parsed as a SIP MESSAGE, perform SIP MESSAGE message processing.

When the protocol type of the received message is an MSRP protocol message, the recording module is specifically used to:

Call the MSRP protocol stack to parse the received MSRP protocol message, and when it is parsed as MSRPSEND, process the MSRP SEND message.

The received message is a continuous media stream data packet, and the judging module detects that the CPM session recording function is enabled, and the device also includes a processing module for,

Record the continuous media streams of all parties participating in the session, and enable the media mixing function to mix the media streams of all parties participating in the CPM session, and save the mixed media stream data;

When the CPM session ends, extract the mixed media stream data packet cached locally, encode according to the storage format requirements of the session history record, and then encode and encapsulate the media stream object into the CPM session history record object.

Said means is set in the CPM session history recording function.

It can be seen from the above-mentioned technical solution provided by the present invention that the CPM participation function receives a message, and detects that the user has opened the conversation history recording function, and analyzes the received message according to the protocol type of the received message and according to the analysis result Executes the conversation history function. Through the processing logic of the meeting history recording function of the CPM participation function of the present invention, the recording function of message, file transmission and session interaction history in the integrated message business environment is realized.

Description of drawings

1 is a schematic diagram of the relationship between CPM talks and CPM messages, CPM file transfers, and CPM sessions, and the relationship between CPM talk history records, CPM message records, CPM file transfer history records, and CPM session history records;

Fig. 2 is a schematic flow chart of the method for realizing the interview history record in the present invention;

Fig. 3 is the flow chart that SIP INVITE message is processed;

Fig. 4 is the implementation flowchart of step 3031 in Fig. 3;

Fig. 5 is the realization flowchart of step 3032 in Fig. 3;

Fig. 6 is the realization flowchart of step 3033 in Fig. 3;

Fig. 7 is the flowchart that SIP BYE message is processed;

Fig. 8 is the flow chart that SIP REFER message is processed;

Fig. 9 is the flow chart that SIP MESSAGE message is processed;

Fig. 10 is the flow chart that MSRP SEND message is processed;

FIG. 11 is a schematic diagram of the composition of the device for achieving meeting history recording in the present invention.

Detailed ways

Figure 1 is a schematic diagram of the relationship between CPM talks and CPM messages, CPM file transfers, and CPM sessions, as well as the relationship between CPM talk history records, CPM message records, CPM file transfer history records, and CPM session history records, as shown in Figure 1 :

The CPM meeting history recording function is actually to record the CPM messages exchanged during the CPM meeting, the CPM file transfer and the CPM session conducted. In order to realize the conversation history recording function, there needs to be a CPM functional entity on the network side that can be located on the signaling plane and the media plane at the same time during the communication process, as a back-to-back user agent (B2BUA, Back-to-Back User Agent) receiving and sending All signaling messages and media messages in the communication process are extracted from them by parsing and recorded according to a certain format: a CPM message interacted outside the CPM session is recorded as a CPM message record object, and a CPM message outside the CPM session is recorded. A transferred CPM file is recorded as a CPM file transfer history record object, and a CPM session is recorded as a CPM session history record object. The CPM participation function server completes the above-mentioned meeting history record function, and submits these record objects to the CPM message storage server for permanent storage.

The CPM message record object stores a CPM message exchanged outside the CPM session. There are two types of CPM messages: Page-Mode and Large Message Mode. Among them, the paging mode CPM message is transmitted through the SIP signaling plane using the SIP MESSAGE method defined in [RFC 3428]. That is to say, the size of the paging mode CPM message is limited, that is, it cannot exceed 1300 bytes. If If it exceeds, the content of the message will not be put into the SIP MESSAGE message body, but will be sent using the CPM message in the large message mode. The large message mode CPM message is to send a single CPM message containing a large amount of data information (such as when carrying multimedia content) through the MSRP protocol ([RFC 4975]). If necessary, it can also be transmitted in segments. Therefore, when sending a large message Before the CPM message in the mode, it is first necessary to establish a temporary SIP session through the SIP INVITE request between the communication parties to negotiate the establishment of the MSRP media channel. After the temporary SIP session is successfully established, the actual message content can be sent through the MSRP SEND request. After the large message transmission is over, the temporary SIP session will be torn down immediately.

The CPM file transmission history record object stores a CPM file that may carry multimedia content transmitted outside the CPM session, such as a text document, a picture, an audio file, a video file, or an application program. The transmission process of the CPM file is similar to the sending process of the CPM message in the large message mode. First, the sender and the receiver of the file request to establish a temporary SIP session through SIP INVITE to negotiate the establishment of an MSRP media channel. The receiver needs to explicitly accept or reject the transmission request of the CPM file. If the temporary SIP session is set up successfully, then use the MSRP SEND request message to send the actual content of the CPM file (as required, it can also be segmented). The temporary SIP session will be torn down immediately after the CPM file transfer ends.

The CPM session history record object stores the interaction history information during a CPM session, and should include four types of information: CPM session state change information, CPM messages (and possibly contained media objects) interacted in the CPM session, CPM files transmitted in a session, and continuous media streaming objects (such as audio/video call segments) interacted in the CPM session. in,

CPM session state information is used to describe the entire development and change process of the entire CPM session from creation to end, including the following six types of session state change event information: CPM session creation event related information (SIP INVITE request message and related response message), CPM session participation Event related information about the party leaving the session (SIP BYE request and related response message), CPM session participant is removed from the CPM session event information (SIP REFER request and related response message), a CPM user joins the CPM session event information (SIP INVITE request and related response messages), inviting other CPM session participants to join the CPM session event information (SIP REFER request and related response messages), and CPM session end event information (SIP BYE request and related response messages).

It can be seen that in order to form a CPM conversation history record, the CPM conversation history record function needs to process a variety of different types of messages from the signaling plane and the media plane, and understand the semantics represented by these messages according to the context of the conversation, so that Record the process of the interview. Due to the complexity of the processing logic, the function of meeting history recording cannot be achieved well only by reusing the existing mechanism. Therefore, it is necessary to provide a new and effective mechanism based on the existing mechanism to realize meeting history recording Function.

In the integrated message business communication environment, in order to record all the communication interaction processes of users participating in the talks, in the present invention, the CPM participation function is set to be located on the signaling channel and the media channel of the CPM talks at the same time, and all CPMs related to the CPM talks All messages or CPM session information pass through the CPM participation function. The CPM participation function checks these messages, executes corresponding logic functions, and completes the corresponding CPM messages and CPM files according to the different semantics represented by different messages in different contexts. Recording function for transfer history and CPM session history.

Protocol messages related to CPM conversation history mainly include: SIP INVITE request and its related response message, SIP REFER request and its related response message, SIP BYE request and its related response message, SIP MESSAGE request and its related response message message, MSRP SEND and its associated reply messages. These messages perform different functions by carrying different header fields in different contexts. For example, a SIP INVITE message can initiate a CPM session, or establish an MSRP channel for sending CPM messages in the large message mode. It is also possible to initiate a session establishment process for a certain CPM user to apply for joining an ongoing CPM session, so in the present invention, the actual semantics of the message is known by judging the relevant header fields carried by different messages, and based on this Complete the relevant message recording or session history recording function.

To perform the session history function, the CPM Participation function also inserts itself simultaneously on the signaling and media channels of the CPM session and performs the B2BUA function. For the signaling plane, whenever a signaling message is received, the CPM participation function first executes the proper CPM business processing logic, and then judges whether the user has enabled the conversation history recording function. If the user enables the conversation recording function, the CPM participation function According to the context of the conversation, it is necessary to judge the actual semantics represented by the received message during the conversation, and update the related message record object or session history record object. If the user does not enable the conversation history recording function, the CPM participation function forwards this signaling message according to the processing logic of the CPM service. For the user plane, once the user enables the meeting recording function, the CPM participation function needs to cache and record the media stream transmitted on the relevant media channel, and after the session ends, encapsulate the cached media stream into the session history object to form A copy of the full session history object.

The solution of the present invention will be described in detail below in conjunction with the embodiments.

Fig. 2 is a schematic flow chart of the method for realizing the historical records of talks in the present invention, as shown in Fig. 2 , including:

Steps 200-201: The CPM participation function receives a message, and detects whether the user has enabled the conversation history recording function, and if so, starts executing the conversation history recording function, and proceeds to step 202; otherwise, proceeds to step 207.

Step 202: Check the protocol type of the received message, if it is a SIP protocol message, go to step 203; if it is an MSRP protocol message, go to step 205.

Step 203～step 2044: call SIP protocol stack to analyze, when it is analyzed as SIP INVITE, enter step 2041 to analyze it in detail, end; when resolved as SIP BYE, enter step 2042 to analyze it in detail, end ; When parsing out as SIP REFER, enter step 2043 to carry out specific analysis to it, end; when parsing out to be SIP MESSAGE, enter step 2044 to carry out specific analysis to it, end.

Steps 205 to 206: call the MSRP protocol stack for analysis, and when the analysis is MSRP SEND, analyze it in detail and end.

Step 207: Forward the received message.

If the CPM conversation history recording function is enabled and continuous media stream packets are received, the CPM participation function will record the continuous media streams of all parties involved in the session, and enable the media mixing function to mix the media streams of all parties involved in the CPM session , save the mixed media stream data. When the CPM session ends, the CPM participation function extracts the locally cached mixed media stream data packet, encodes it according to the storage format requirements of the session history record, and then encapsulates the media stream object encoding into the CPM session history record object.

Since the processing logic of the conversation history record function in the converged message service communication environment is very complicated, and there is no mature conversation history mechanism in the existing message service for reference, the technical solution of the present invention makes up for the need for conversations in the converged message service communication environment. This gap is the processing logic of the history function.

Aiming at the method of the present invention, there is also provided a device for achieving conversation history recording in the integrated message service, as shown in Figure 11, which can be set in the CPM conversation history recording function, at least including a receiving module, a judging module, and a recording module, wherein,

The receiving module is used to receive the message and output the recording module to notify the judging module;

The judging module is used to receive a notification from the receiving module, detect whether the user has enabled the conversation history recording function, and send a recording notification to the recording module when it is enabled;

The recording module is configured to receive the recording notification, analyze the received message according to the protocol type of the received message, and execute the conversation history recording function according to the analysis result.

When the protocol type of the received message is a SIP protocol message, the recording module is specifically used to call the SIP protocol stack to parse the received SIP protocol message, and when parsing out as SIP INVITE, carry out SIP INVITE message processing; If it is parsed as SIP BYE, process the SIP BYE message; if it is parsed as SIP REFER, process the SIP REFER message; if it is parsed as SIP MESSAGE, process the SIPMESSAGE message.

When the protocol type of the received message is an MSRP protocol message, the recording module is specifically used to call the MSRP protocol stack to parse the received MSRP protocol message, and when it is parsed as MSRP SEND, perform MSRP SEND message processing.

When the received message is a continuous media stream data packet, and the judging module detects that the CPM session recording function is enabled, the device also includes a processing module, which is used to record the continuous media of all parties involved in the session stream, and enable the media mixing function to mix the media streams of all parties participating in the CPM session, and save the mixed media stream data; when the CPM session ends, extract the mixed media stream data packets cached locally, and record The requirements of the storage format are encoded, and then the media stream object is encoded and encapsulated into the CPM session history record object.

The following will analyze the above five request messages related to the session state that will appear in the CPM session, focusing on the processing logic related to the history record function of the CPM participation function, that is to say, the default CPM participation function has verified these How to complete the processing logic related to the CPM session history recording function after the message is legal and the relevant CPM business processing logic is completed, and on the premise that the CPM user has enabled the conversation history recording function.

Figure 3 is a flow chart of processing SIP INVITE, as shown in Figure 3, including:

Steps 300 to 301: When the CPM participation function receives a SIP INVITE message, it first caches the SIP INVITE message locally, waits for the response message of success or failure returned by the receiver and caches it, and then starts to execute the session history information Record function.

Steps 302 to 3033: The CPM participation function checks the CPM feature tag carried in the Accept-Contact header field and the Contact header field. If the CPM feature tag indicates that this is a temporary SIP session establishment request message established for CPM large message transmission, then Execute step 3031; If the CPM feature label indicates that this is a setup request message for setting up a temporary SIP session for CPM file transfer, then perform step 3032; if the CPM feature label indicates that this is a SIP session setup request message related to the CPM session event , then step 3033 is executed.

Fig. 4 is the implementation flowchart of step 3031 in Fig. 3, as shown in Fig. 4, including:

Step 400: judging whether it is the establishment request message of establishing a temporary SIP session for the transmission of large messages in the CPM session, or the establishment request message of establishing a temporary SIP session for the transmission of large messages outside the CPM session, if it is a large message in the CPM session , then go to step 404, otherwise go to step 401.

In this step, the method for judging is: check whether the To header field of the SIP INVITE message carries the tag parameter, if the tag parameter is carried, it indicates that the establishment request message of the temporary SIP session is set up for the large message transmission in the CPM session; if not Carrying the tag parameter indicates the establishment request message for establishing a temporary SIP session for large message transmission outside the CPM session.

Step 401: Judging whether the SIP temporary session is successfully established according to the response message, if successful, proceed to step 402; otherwise, proceed to step 403.

In this step, judge according to the response message (SIP 200OK or failure response) corresponding to the INVITE message received, if what is received is a SIP 200OK response message, it shows that the SIP session is established successfully, if what is received is a failure response , it indicates that the establishment of the SIP session failed.

Step 402: The CPM participation function creates a new CPM message record object, and extracts relevant information (From header field, To header field, etc.) from the SIP INVITE request message according to the unified storage format of the CPM message for recording. Then go to step 407.

Step 403: Do not record anything. The CPM participation function discards the INVITE message without making a record, and returns a failure response message. Finish.

Steps 404-406: Find the CPM session to which the CPM large message belongs by calculating and comparing the Dialog-ID, find the session history record object of the corresponding CPM session, and extract relevant information from the INVITE message for recording; Response messages of success or failure are recorded in the CPM session history object. Then go to step 407.

This step specifically includes: Calculate the Dialog-ID according to the relevant description in [RFC 3261] (that is, obtain the values of the Call-ID header field, the tag parameter in the From header field, and the tag parameter in the To header field), and save it with the CPM participation function Compare the Dialog-ID in each ongoing CPM session state parameter to find the CPM session to which the big message in this CPM session belongs; find the CPM session history record object corresponding to the matching CPM session, and send it from the SIP INVITE Extract relevant information from the request message and write it into the corresponding CPM session history record object; according to the successful or failed response message returned to the INVITE message, record the result of the success or failure of the SIP session establishment, which is also used as the CPM Part of the session history object.

Step 407: Wait for the MSRP SEND message to be received at the port of the specified MSRP media channel.

In this step, in order to record the conversation history, the CPM participation function needs to insert itself into the signaling and media channel as a B2BUA, that is, the CPM participation function will negotiate the media channel port with the sender on behalf of the receiver to achieve insertion into the on the media channel. Therefore, the CPM participation function will wait to receive the MSRP SEND message on the negotiated MSRP communication port to receive the CPM large message.

Fig. 5 is the implementation flowchart of step 3032 in Fig. 3, as shown in Fig. 5, including:

Step 500: judging whether to set up a request message for setting up a temporary SIP session for file transfer in a CPM session, or a request message for setting up a temporary SIP session for file transfer outside a CPM session, if it is a file transfer in a CPM session, Then go to step 504, otherwise go to step 501.

In this step, the method for judging is: check whether the To header field of the SIP INVITE message carries the tag parameter, if the tag parameter is carried, it indicates that the establishment request message of the temporary SIP session is set up for the file transfer in the CPM session; if it does not carry the The tag parameter indicates the establishment request message for establishing a temporary SIP session for file transfer outside the CPM session.

Step 501: Judging whether the SIP temporary session is established successfully according to the response message, if successful, proceed to step 502; otherwise, proceed to step 503.

In this step, judge according to the response message (SIP 200OK or failure response) corresponding to the INVITE message received, if what is received is a SIP 200OK response message, it shows that the SIP session is established successfully, if what is received is a failure response , it indicates that the establishment of the SIP session failed.

Step 502: The CPM participation function creates a new CPM file transfer history record object, and extracts relevant information (From header field, To header field, etc.) ) to record. Then go to step 507.

Step 503: Do not record anything. The CPM participation function discards the INVITE message without making a record, and returns a failure response message. Finish.

Steps 504 to 506: Find the CPM session to which the CPM file transfer belongs by calculating and comparing the Dialog-ID, find the session history record object of the corresponding CPM session, and extract relevant information from the INVITE message for recording; according to the INVITE request Response messages related to success or failure are recorded in the CPM Session History object. Then go to step 507.

This step specifically includes: Calculate the Dialog-ID according to the relevant description in [RFC 3261] (that is, obtain the values of the Call-ID header field, the tag parameter in the From header field, and the tag parameter in the To header field), and save it with the CPM participation function Compare the Dialog-ID in each of the ongoing CPM session state parameters to find the CPM session to which this CPM file transfer belongs; find the CPM session history object corresponding to the matching CPM session, and retrieve it from the SIP INVITE request message Extract relevant information and write it into the corresponding CPM session history record object; according to the success or failure response message returned to the INVITE message, record the result of the success or failure of the SIP session establishment, which is also used as the CPM session history record part of the object.

Step 507: Wait for the MSRP SEND message to be received at the port of the specified MSRP media channel.

In this step, in order to record the conversation history, the CPM participation function needs to insert itself into the signaling and media channel as a B2BUA, that is, the CPM participation function will negotiate the media channel port with the sender on behalf of the receiver to achieve insertion into the on the media channel. Therefore, the CPM participation function will wait to receive the MSRP SEND message on the negotiated MSRP communication port to receive the CPM file.

Fig. 6 is the implementation flowchart of step 3033 in Fig. 3, as shown in Fig. 4, including:

Step 600: Judging whether the SIP session establishment request message related to the CPM session event is a session establishment request message initiated for establishing a new CPM session, or initiated by a certain CPM user for applying to join an ongoing CPM session If the session join request message is the former, go to step 605; if it is the latter, go to step 601.

In this step, the method for judging is: check whether the To header field of the SIP INVITE message carries the tag parameter, if the tag parameter is carried, it indicates that the SIP session establishment request message related to the CPM session event is a request message for setting up a new CPM The session establishment request message initiated by the session; if it does not carry the tag parameter (that is, it is empty), it indicates that the SIP session establishment request message related to the CPM session event is a CPM user who applies for joining an ongoing CPM session Initiated session join request message.

Further, check the Request-URI of the SIP INVITE request message,

If the value of Request-URI is a CPM session identifier, it indicates that the SIP INVITE request message is a session joining request message initiated by a CPM user to apply for joining an ongoing CPM session;

If the value of Request-URI is the address of the CPM control function, and the tag parameter in the To header field is empty, it indicates that the SIP INVITE request message is a session establishment request message initiated for an ongoing Ad-hoc group CPM session ;

If the value of Request-URI is the address of the CPM user, and the tag parameter in the To header field is empty, it indicates that the SIP INVITE request message is a session establishment request message initiated to establish a new 1-1CPM session;

If the value of Request-URI is the address of the CPM group, and the tag parameter in the To header field is empty, it indicates that the SIP INVITE request message is a session establishment request message initiated to establish a new predefined group CPM session.

Steps 601 to 604: It is a session request message initiated by a CPM user to apply for joining an ongoing CPM session, and finds the corresponding CPM session history record object through the CPM session identifier indicated in the Request-URI; according to the session history According to the provisions of the record storage format, relevant information is extracted from the SIP INVITE message and recorded; according to the response message of success or failure returned by the INVITE message, the result of the request to join the CPM session event is recorded, which is also used as the CPM session Part of the history object. Finish.

Steps 605 to 607: are session establishment request messages initiated for establishing a new CPM session, and the CPM participation function creates a new CPM session history record object in the local storage space; according to the storage format of the CPM session history record, Extract and record relevant information from the SIP INVITE message; record the result of the CPM session creation event according to the success or failure response message returned by the INVITE message, and also serve as a part of the CPM session history record object.

Fig. 7 is a flow chart of processing the SIP BYE message, as shown in Fig. 7, including:

Step 700~Step 701: When the CPM participation function receives a SIP BYE message, it first caches the SIP BYE message locally, and waits for the success or failure response message returned by the receiver and caches it, then starts to execute the session history Information recording function.

Step 702: Judging whether the SIP BYE message is sent successfully according to the response message, if it is a SIP 200OK response message that is received, it indicates that the SIP BYE message is transmitted successfully, then continue to perform step 703; if it is a SIP failure response message that is received, it indicates that the SIP BYE message is transmitted successfully. SIP BYE message transmission fails, go to step 714.

Step 703～step 709: parse this SIP BYE message, find the SIP session associated with this SIP BYE message by calculating Dialog-ID, obtain the semantics that this SIP session represents, if the meaning of this SIP BYE message is:

The CPM user leaves the session, or the entire CPM session ends, or the temporary SIP session for transmitting CPM large messages ends and the intra-session large message transmission process ends, or the temporary SIP session for transmitting CPM files ends and the intra-session large message transmission process ends end, then enter step 712;

If the temporary SIP session for transmitting the CPM large message ends and the large message transmission process outside the session ends, then enter step 710;

If the temporary SIP session for transferring the CPM file ends and the file transfer process outside the session ends, go to step 711 .

Step 710: find the corresponding CPM message record object, and go to step 713.

Step 711: find the corresponding CPM file transfer history record object, and go to step 713.

Step 712: find the corresponding CPM session history record object, and go to step 713.

Step 713: Update the relevant CPM session history record object, CPM message record object or CPM file transfer history record object according to the judgment result. If the entire CPM session ends, the CPM participation function will also encapsulate the cached continuous media interacted during the CPM session into the relevant CPM session history object in a unified storage format, and finally complete the assembly of the CPM session history object , and submit it to the message storage server. Finish.

Step 714: Discard the SIP BYE message, and return a failure response message.

Fig. 8 is a flowchart of processing the SIP REFER message, as shown in Fig. 8, including:

Steps 800 to 801: When the CPM participation function receives a SIP REFER message, it first caches the SIP REFER message locally, waits for the success or failure response message returned by the receiver and caches it, and then starts to execute the session history Information recording function.

Step 802: Judging whether the SIP REFER message is sent successfully according to the response message, if a SIP 200OK response message is received, it indicates that the SIP REFER message is transmitted successfully, and enters step 803; if a SIP failure response message is received, it indicates that the SIP REFER message is sent successfully. REFER message transmission fails, go to step 808.

Steps 803 to 807: parse the SIP REFER message, and obtain the value of the "method" parameter in the Refer-To header field of the SIP REFER message through the value of the CPM session identifier carried in the Request-URI:

If the value of the "method" parameter is "BYE", it means that the SIP REFER message wants to remove some users from the specified CPM session, then write a session state of "remove user" in the CPM session history object event, and extract relevant information from the SIP REFER message for recording; end.

If the value of the "method" parameter is "INVITE", it means that the SIP REFER message wants to invite some users to join the specified CPM session, then write a session state event of "invite users to join" in the CPM session history object , and extract relevant information from the SIP REFER message for recording. Finish.

Step 808: Discard the message and return a failure response message.

Fig. 9 is a flow chart of processing the SIP MESSAGE message, as shown in Fig. 9, including:

Steps 900 to 901: When the CPM participation function receives a SIP MESSAGE message, it first caches the SIP MESSAGE message locally, waits for the success or failure response message returned by the receiver and caches it, and then starts to execute the session history information Record function.

Equally, judge whether this SIP MESSAGE message is sent successfully according to response message, if what receive is SIP 200OK response message, show that this SIP MESSAGE message transmits success, enter step 902; If what receive is SIP failure response message, show that this SIP MESSAGE If the message transmission fails, the message is discarded and a failure response message is returned.

Step 902: analyze whether the To header field of the SIP MESSAGE message carries the tag parameter, if the tag parameter is carried, then it is judged that the SIP MESSAGE message is a message in a CPM session, and step 903 is performed; if the tag parameter is empty, then it is judged is a CPM out-of-session message, go to step 907.

Steps 903 to 906: The SIP MESSAGE message is a CPM message in a CPM session, then calculate the Dialog-ID according to the relevant description in [RFC 3261] (that is, obtain the Call-ID header field, the tag parameter in the From header field, the To The value of the tag parameter in the header field), and compare it with the Dialog-ID in each ongoing CPM session state parameter saved by the CPM participation function, and find the CPM session to which this CPM message belongs:

If a matching CPM session is found, relevant information is extracted from the SIP MESSAGE request message and written into the corresponding CPM session history record object; The results of the send are logged, also as part of the CPM session history object; end.

If no matching CPM session is found, return an error message and end.

Step 907～step 911: this SIP MESSAGE message is a CPM message outside the CPM session, judge whether the message is successfully sent according to the response message to this SIP MESSAGE message:

If the message is successfully sent, the CPM participation function will create a new CPM message record object, and extract relevant information from the SIP MESSAGE request message for recording according to the storage format of the CPM message; if the message fails to be sent, then The CPM Participation function does not record anything, discards the message, and returns an error response.

Figure 10 is a flow chart of processing the MSRP SEND message, as shown in Figure 10, including:

Step 1000～Step 1001: When the CPM participation function receives an MSRP SEND message, it first caches the MSRP SEND message locally, waits for the response message of success or failure returned by the receiver and caches it, and then starts to execute the session history information Record function.

Step 1002: Judging whether the MSRP SEND message is sent successfully according to the response message, if the MSRP 200OK response message is received, it indicates that the MSRP SEND message is transmitted successfully, and then enters step 1003; if the MSRP failure response message is received, it indicates that the MSRP SEND message transmission fails, go to step 1012.

Steps 1003 to 1004: Analyze the MSRP SEND message, and judge whether the MSRP SEND message is segmented by checking the value of the "Byte-Range" header field according to the flow defined in [RFC 4975]. If it is segmented, Then this MSRP SEND message is a fragmentation, further judge whether this fragmentation is the last fragmentation, if it is the last fragmentation, show that all fragmentation has been received, then enter step 1005; if not the last fragmentation, then enter Step 1011.

If the MSRP SEND message is not fragmented, then the MSRP SEND message is not segmented transmission, then directly enter step 1006.

Step 1005: Assemble fragments of MSRP SEND messages belonging to one big message to form a complete big MSRP SEND message.

Step 1006: Find the corresponding session history record object through the receiving port number of the MSRP SEND message.

Step 1007: Determine whether the MSRP SEND message corresponds to a CPM message recording process, a CPM file transfer recording process, or a CPM session history recording process. If what MSRP SEND transmits is the large message outside the CPM session, then enter step 1008; If what MSRP SEND transmits is the file outside the CPM session, then enter step 1009; If what MSRP SEND transmits is the CPM large message or the CPM file in the session, then Go to step 1010.

Step 1008: Obtain the content in the MSRP SEND message, encapsulate it into the corresponding CPM message record object as the content of the CPM large message transmitted outside the session, and form the final CPM message record object; end.

Step 1009: Obtain the content in the MSRP SEND message, use it as the content of the CPM file transmitted outside the session, encapsulate it into the corresponding CPM file transmission history record object, and form the final CPM file transmission history record object; end.

Step 1010: Obtain the content in the MSRP SEND message, encapsulate it into the corresponding CPM session history record object as a large message or file transmitted in the CPM session, and update it; end.

Step 1011: continue to wait for other fragments of the remaining MSRP SEND message, return to step 1000.

Step 1012: Discard the message and return a failure response message.

By the inventive method, it can be seen that:

(1) Once the CPM participation function activates the meeting history recording function, the CPM participation function will be located on the signaling channel and the media channel at the same time, and classify and process messages related to the meeting status. CPM processes SIP INVITE, SIP REFER, SIP MESSAGE, SIP 200OK, and SIP failure response messages on the signaling plane, and judges the meaning of the messages according to the context. Extract key information and record it in a unified format, rather than just storing these messages intact.

(2) For the SIP INVITE message, since it may represent three different meeting events of sending a CPM large message, transmitting a CPM file or setting up a CPM session, the CPM participation function of the present invention is carried by analyzing the INVITE message "Accepted-Contact" header field The CPM feature tag is used to determine which type of event occurs, so as to decide whether to record CPM message or CPM file transfer or record CPM session history.

(3) The CPM participation function waits for the response message returned by the receiver, and then executes the conversation history recording function. If the message is successfully sent, execute the corresponding recording function; if the message fails to be sent and it is a message outside the session, it is directly discarded; If the message fails to be sent and it is a session-related message, the semantics represented by it are obtained and recorded in the session history.

(4) After the CPM participation function receives the SIP 200OK response message, it determines the actual semantics represented by the successful response message. If it indicates that the large message transmission media channel is established successfully, the CPM participation function starts the MSRP media plane, and prepares to receive the MSRP SEND message and Record; if it indicates that the CPM file transmission media channel is successfully established, the CPM participation function starts the corresponding media plane, prepares to receive the MSRP SEND message and records it; if it indicates that the CPM session is successfully established, the CPM participation function starts the corresponding continuous media flow plane , ready to accept continuous media streams and record after mixing the media streams of the parties involved in the session.

(5) After the CPM participation function receives the SIP REFER message, after judging whether to add a user operation or remove a user operation, record the corresponding session state change information.

(6) After the CPM participation function receives the SIP BYE message, it determines the semantics represented by the BYE message: if the CPM session ends, the CPM participation function encapsulates all the contents of the session cache into a complete session history record; if it is a session If the CPM large message outside the session or the CPM file transfer ends, the CPM participation function will encapsulate the relevant content into a complete CPM message record or CPM file transfer history record; if the CPM message or CPM file transfer in the session ends, or the CPM user If the session is left, the session state information of the corresponding CPM session is updated.

Through the processing logic of the meeting history recording function of the CPM participation function of the present invention, the recording function of message and session interaction history in the integrated message business environment is realized.

The above description is only a preferred embodiment of the present invention, and is not used to limit the protection scope of the present invention. Any modifications, equivalent replacements and improvements made within the spirit and principles of the present invention shall be included in the within the protection scope of the present invention.

Claims (16)

1. A method for implementing conversation history records in a fusion message service, characterized in that it comprises: The integrated IP message CPM participation function receives a message and detects that the user has enabled the conversation history recording function, analyzes the received message according to the protocol type of the received message, and executes the conversation history recording function according to the analysis result; When the protocol type of the received message is a SIP protocol message, the parsing the received message and executing the conversation history record function according to the parsing result includes: Call the SIP protocol stack to analyze the received SIP protocol message, when it is resolved as SIP INVITE, process SIP INVITE message; when resolved as SIP BYE, process SIP BYE message; when resolved as SIP REFER, perform SIP REFER Message processing; when it is parsed as a SIP MESSAGE, perform SIP MESSAGE message processing; or, When the protocol type of the received message is an MSRP protocol message, the function of parsing the received message and executing the conversation history recording function according to the parsing result includes: Call the MSRP protocol stack to parse the received MSRP protocol message, and when it is parsed as MSRPSEND, process the MSRP SEND message. 2. The method according to claim 1, wherein, if the continuous media stream data packet is received, and it is detected that the CPM session recording function is enabled, the method also includes: The CPM participation function records the continuous media streams of the parties involved in the session, and enables the media mixing function to mix the media streams of the parties participating in the CPM session, and preserve the mixed media stream data; When the CPM session is over, the CPM participation function extracts the mixed media stream data packets cached locally, encodes them according to the storage format requirements of the session history record, and then encodes and encapsulates the media stream object into the CPM session history record object. 3. method according to claim 1, is characterized in that, described SIP INVITE message processing comprises: The CPM participation function caches the SIP INVITE message locally, waits to receive the success or failure response message returned by the receiver and caches it; The CPM participation function checks the Accept-Contact header field of the SIP INVITE message and the CPM feature label carried in the Contact header field, and the temporary SIP session establishment request message set up for the CPM large message transmission indicated by the CPM feature label, or for The temporary SIP session establishment request message established by the CPM file transfer, or the SIP session establishment request message related to the CPM session event is processed accordingly. 4. The method according to claim 3, wherein the processing of the temporary SIP session setup request message set up for the CPM large message transmission comprises: When judging that the temporary SIP session establishment request message established for the CPM large message transmission is a temporary SIP session establishment request message established for the large message transmission in the CPM session, then, by calculating and comparing the Dialog-ID Find the CPM session to which the big CPM message belongs, find the session history record object of the corresponding CPM session, and extract relevant information from the INVITE message to record; Record; wait to receive MSRP SEND message at the port of the specified MSRP media channel; When judging that the temporary SIP session establishment request message established for the CPM large message transmission is the temporary SIP session establishment request message established for the large message transmission outside the CPM session, then, After judging that the SIP temporary session is established successfully according to the response message, the CPM participation function creates a new CPM message record object, and extracts relevant information from the SIP INVITE request message to record according to the unified storage format of the CPM message; Wait for the MSRP SEND message to be received at the port of the specified MSRP media channel. 5. The method according to claim 3, wherein the processing of the temporary SIP session setup request message set up for the CPM file transfer comprises: When judging that the temporary SIP session establishment request message established for the CPM file transfer is a temporary SIP session establishment request message established for the file transfer within the CPM session, then, find the CPM by calculating and comparing the Dialog-ID For the CPM session to which the file belongs, find the session history record object of the corresponding CPM session, extract relevant information from the INVITE message and record it; record it in the CPM session history record object according to the success or failure response message of the INVITE request; The port of the specified MSRP media channel is waiting to receive the MSRP SEND message; When judging that the temporary SIP session setup request message set up for the CPM file transfer is a temporary SIP session setup request message set up for the file transfer outside the CPM session, and judging that the SIP temporary session setup was successful according to the response message, then , Described CPM participation function creates a new CPM file transmission history record object, and according to the regulation of the unified storage format of CPM file transmission history record, extracts relevant information from this SIP INVITE request message and records; The port waits to receive MSRP SEND messages. 6. The method according to claim 3, wherein the processing of the SIP session establishment request message related to the CPM session event comprises: When it is judged that the SIP session establishment request message related to the CPM session event is a session establishment request message initiated for establishing a new CPM session, then the CPM participation function creates a new CPM session history record in the local storage space Object; According to the provisions of the storage format of the CPM session history record, extract relevant information from the SIP INVITE message and record it; according to the response message of success or failure returned by the INVITE message, perform the result of the CPM session creation event records, also as part of this CPM Session History object; When it is judged that the SIP session establishment request message related to the CPM session event is a session join request message initiated by a CPM user to apply for joining an ongoing CPM session, then, find the SIP session identifier indicated in the Request-URI The corresponding CPM session history object; according to the storage format of the session history record, extract relevant information from the SIP INVITE message and record it; according to the success or failure response message returned to the INVITE message, add the request to CPM The results of session events are logged, also as part of the CPM Session History object. 7. The method according to claim 6, characterized in that the method further comprises: checking the Request-URI of the SIP INVITE request message, If the value of Request-URI is a CPM session identifier, then the SIP INVITE request message is a session joining request message initiated by a CPM user for applying for joining an ongoing CPM session; If the value of Request-URI is the address of the CPM control function, and the tag parameter in the To header field is empty, then the SIP INVITE request message is a session establishment request message initiated for an ongoing Ad-hoc group CPM session ; If the value of Request-URI is the address of the CPM user, and the tag parameter in the To header field is empty, then the SIP INVITE request message is a session establishment request message initiated for establishing a new 1-1CPM session; If the value of Request-URI is the address of the CPM group, and the tag parameter in the To header field is empty, then the SIP INVITE request message is a session establishment request message initiated for establishing a new predefined group CPM session. 8. The method according to claim 1, wherein the processing of the SIP BYE message comprises: The CPM participation function caches the SIP BYE message locally, waits to receive the success or failure response message returned by the receiver and caches it, and then parses the SIP BYE message when judging that the SIP BYE message is sent successfully according to the response message , If the SIP BYE message is the message that the CPM user leaves the session, or the message that the entire CPM session ends, or the end of the temporary SIP session that transmits the CPM large message and the end of the large message transmission process in the session, or the message that transmits the CPM file If the temporary SIP session ends and the large message transmission process in the session ends, then find the corresponding CPM session history record object; If the SIP BYE message is the end of the temporary SIP session for transmitting the CPM large message and the end of the large message transmission process outside the session, then find the corresponding CPM message record object; If the SIP BYE message is the end of the temporary SIP session for transferring the CPM file and the end of the file transfer process outside the session, then find the corresponding CPM file transfer history record object; After the record object is obtained, the relevant CPM session history record object, CPM message record object or CPM file transfer history record object is updated according to the judgment result. 9. The method according to claim 1, wherein the SIP REFER message processing comprises: The CPM participation function caches the SIP REFER message locally, waits for receiving and caching the response message of success or failure returned by the receiver, judges that the SIP REFER message is successfully sent according to the response message, and carries the SIP REFER message through the Request-URI. The value of the CPM session identifier, and obtain the value of the method parameter in the Refer-To header field of the SIPREFER message: If the value of the method parameter is BYE, write the session status event of the removed user in the CPM session history object, and extract relevant information from the SIP REFER message for recording; If the value of the method parameter is INVITE, write the session state event inviting the user to join in the CPM session history record object, and extract relevant information from the SIP REFER message for recording. 10. The method according to claim 1, wherein the SIP MESSAGE message processing comprises: The CPM participation function buffers the SIP MESSAGE message locally, waits to receive the success or failure response message returned by the receiver and caches it, and judges that the SIPMESSAGE message is sent successfully according to the response message; parses the SIP MESSAGE message, If there is a tag parameter in the To header field of the SIP MESSAGE message, it is determined that the SIPMESSAGE message is a CPM session message, then find the CPM session that matches the SIP MESSAGE message, and extract relevant information from the SIP MESSAGE request message. Enter the corresponding CPM session history record object; and according to the success or failure response message returned by the MESSAGE message, record the result sent by the CPM message, also as a part of the CPM session history record object; If the tag parameter in the To header field of the SIP MESSAGE message is empty, then it is judged that it is a message outside the CPM session, then, after judging that it has been successfully sent according to the response message to the SIP MESSAGE message, the CPM participation function will create a new CPM Message record object, and extract relevant information from the SIP MESSAGE request message for recording according to the storage format of the CPM message. 11. The method according to claim 1, wherein the MSRP SEND message processing comprises: When the CPM participation function caches the MSRP SEND message locally, waits to receive the success or failure response message returned by the receiver and caches it, if a success response message is received, Parse the MSRP SEND message, if the MSRP SEND message is not fragmented, find the corresponding conversation history record object through the receiving port number of the MSRP SEND message, and record the process of the CPM message corresponding to the MSRP SEND message, or CPM File transfer recording process, or CPM session history recording process for corresponding processing; If the MSRP SEND message is a fragment, it is further judged whether the fragment is the last fragment, and it is the last fragment, and each MSRP SEND message fragment belonging to a large message is assembled to form a complete MSRP SEND large message; find the corresponding conversation history record object through the receiving port number of the MSRP SEND message, and perform corresponding actions according to the CPM message recording process, CPM file transfer recording process, or CPM session history recording process corresponding to the MSRP SEND message deal with. 12. The method according to claim 11, characterized in that, the processing of the corresponding CPM message recording process is: obtaining the content in the MSRP SEND message, as the content of the CPM large message transmitted outside the session, and encapsulating it into the corresponding The final CPM message record object is formed in the CPM message record object; The processing of the corresponding CPM file transmission recording process is: obtain the content in the MSRP SEND message, as the content of the CPM file transmitted outside the session, encapsulate it in the corresponding CPM file transmission history record object, and form the final CPM file transmission history object; The processing of the corresponding CPM session history record process is: obtain the content in the MSRP SEND message, encapsulate it into the corresponding CPM session history record object as a large message or file transmitted in the CPM session, and update it. 13. The method according to any one of claims 1-12, wherein the CPM participation function inserts itself as a SIP back-to-back user agent B2BUA on the signaling and media channel. 14. A device for achieving conversation history recording in a converged message service, characterized in that it includes at least a receiving module, a judging module, and a recording module, wherein, The receiving module is used to receive the message and transmit the received message to the recording module, and notify the judging module; The judging module is used to receive a notification from the receiving module, detect whether the user has enabled the conversation history recording function, and send a recording notification to the recording module when it is enabled; The recording module is used to receive the recording notification, analyze the received message according to the protocol type of the received message and execute the meeting history recording function according to the analysis result; When the protocol type of the received message is a SIP protocol message, the recording module is specifically used to call the SIP protocol stack to analyze the received SIP protocol message, and when it is resolved as SIP INVITE, carry out SIP INVITE message processing ; When it is parsed as SIP BYE, process SIP BYE message; when it is parsed as SIP REFER, process SIP REFER message; when it is parsed as SIP MESSAGE, process SIP MESSAGE message; When the protocol type of the received message is an MSRP protocol message, the recording module is specifically used to call the MSRP protocol stack to parse the received MSRP protocol message, and when it is parsed as MSRP SEND, perform MSRP SEND message processing. 15. The device according to claim 14, wherein the received message is a continuous media stream packet, and the judging module detects that the CPM session recording function is opened, and the device also includes a processing module for At, Record the continuous media streams of all parties participating in the session, and enable the media mixing function to mix the media streams of all parties participating in the CPM session, and save the mixed media stream data; When the CPM session ends, extract the mixed media stream data packet cached locally, encode according to the storage format requirements of the session history record, and then encode and encapsulate the media stream object into the CPM session history record object. 16. The device according to claim 15, characterized in that the device is set in the CPM session history recording function.

Images