CN101854599B - Transmission method and system of large fusion IP (Internet Protocol) message - Google Patents

Abstract

The invention provides a CPM message transmission method and system in a large message mode. The method is used to send a large message mode CPM message to a target group. For the receivers reachable by the CPM system in the target group, the method includes: the sender CPM client sends a session invitation message of a large message mode CPM message, and the session The invitation message arrives at the receiver's CPM client via the CPM control functional entity of the target group; the receiver's CPM client receives the session invitation message, and establishes a media transmission link between the sender's CPM client and the receiver's CPM client; the sender The CPM client sends the content of the large message mode CPM message to the receiving party CPM client through the above media transmission link; the sending party CPM client or the receiving party CPM client initiates the large message mode CPM message session termination process. Through the present invention, the large message mode CPM message can be sent to the target group.

Description

Big converged IP message transmission method and system

technical field

The present invention relates to the technical field of mobile communication, in particular to a Converged IP Messaging (CPM for short) transmission method and system.

Background technique

CPM was proposed by the Open Mobile Architecture (OMA) in 2005. Its purpose is to realize the intercommunication of various message services, provide unified message services, and improve consistent and convenient message service experience. CPM integrates various existing messaging services, including instant messaging (Instant Message, referred to as IM), push-to-talk (Push-To-Talk over Cellular, referred to as POC), mobile e-mail (Mobile E-Email, referred to as MEM), short message service (Short Messaging Service, referred to as SMS), multimedia message service (Multimedia Messaging Service, referred to as MMS), etc.

Currently, OMA is developing the CPM V1.0 specification. The business form of CPM includes: CPM message based on paging mode (page-mode), large message mode CPM message (Large Message Mode CPMMessage) based on session-mode (session-mode), and other CPM conversation services based on session. Before users normally use these services, they need to register and log in to the CPM system, which is commonly referred to as "going online".

The session initiation protocol (Session Initiation Protocol, referred to as SIP) message (SIP Message) is used to transmit page-mode messages between the CPM Client (CPM Client) and the CPM Engine (CPMEnabler) of the sending and receiving parties. When the sender terminal needs to send a large message mode CPM message, if the size of the message exceeds the limit (for example, greater than 1300 bytes), it cannot be carried by SIP MESSAGE.

CPM service supports preset group (CPM Pre-defined Group) and temporary group (CPM Ad-hoc Group). CPM users can send CPM paging messages to a certain temporary group or preset group, but when the message size When it exceeds a certain limit, it cannot be carried by SIP MESSAGE.

In the existing specification, there is no solution for sending a large CPM paging message to a certain temporary group or preset group.

Contents of the invention

In view of this, the present invention provides a large converged IP message transmission method and system to solve the problem in the prior art that the CPM client cannot send large message mode CPM messages to receivers in the group.

According to one aspect of the present invention, a large message mode CPM message transmission method is provided, and the method is used for a sender CPM client to send a large message mode CPM message to a target group.

According to the large message mode CPM message transmission method of the present invention, the sending party CPM client sends the session invitation message of the large message mode CPM message, and the session invitation message arrives at the receiving party CPM client via the CPM control function entity of the target group; The party CPM client receives the above session invitation message, negotiates with the sender CPM client, and establishes the media transmission link between the sender CPM client and the receiver CPM client; the sender CPM client passes the above media transmission link , sending the content of the large message mode CPM message to the receiver CPM client; the sender CPM client or the receiver CPM client initiates the above large message mode CPM message session termination process.

According to another aspect of the present invention, another large message mode CPM message transmission method is provided, the method is used to send a large message mode CPM message to a target group, if the target group includes a recipient that is reachable by the CPM system , the large message mode CPM message transmission method is adopted to transmit the large message mode CPM message.

According to yet another aspect of the present invention, a CPM message transmission system in large message mode is provided, and the system is used for sending CPM message in large message mode to a target group.

The large message mode CPM message transmission system according to the present invention includes: a sender CPM client, a receiver CPM client, a CPM control functional entity, a source participating functional entity and a destination participating functional entity. Wherein, the sender CPM client is used to send a session invitation message of a large message mode CPM message, wherein the session invitation message carries the session description protocol SDP session description parameter for negotiation; The participating functional entity of the receiver is used to receive and send the above-mentioned session invitation message; the CPM control functional entity is used to receive and send the above-mentioned session invitation message; A session invitation message; the recipient CPM client is used to receive the above session invitation message.

Through at least one solution of the present invention, the transmission link between the CPM client of the sender and the CPM client of the reachable receiver of the CPM system in the target group is established through the session invitation message of the large message mode CPM message, and the The content of the CPM message in the large message mode is sent to the receiving party's CPM client, which can solve the problem that the CPM message in the large message mode cannot be transmitted to the group in the current technology, and improves user experience.

Additional features and advantages of the invention will be set forth in the description which follows, and in part will be apparent from the description, or may be learned by practice of the invention. The objectives and other advantages of the invention may be realized and attained by the structure particularly pointed out in the written description and claims hereof as well as the appended drawings.

Description of drawings

The accompanying drawings are used to provide a further understanding of the present invention, and constitute a part of the description, and are used together with the embodiments of the present invention to explain the present invention, and do not constitute a limitation to the present invention. In the attached picture:

Fig. 1 is a flowchart of a method for transmitting a CPM message in a large message mode according to an embodiment of the present invention;

Fig. 2 is the specific flow chart of session invitation message sending in the embodiment of the present invention;

FIG. 3 is a flowchart of a first media transmission path method in an embodiment of the present invention;

FIG. 4 is a flowchart of a second media transmission path method in an embodiment of the present invention;

Fig. 5 is the flow chart of sending the content of the CPM message of large message mode to the receiving party CPM client by sending party CPM client in the embodiment of the present invention;

FIG. 6 is a flow chart of a session termination process initiated by a sender CPM client in an embodiment of the present invention;

FIG. 7 is a flow chart of a session termination process initiated by a recipient CPM client in an embodiment of the present invention;

Fig. 8 is the flowchart of embodiment one;

Fig. 9 is the flow chart of embodiment two;

Fig. 10 is the flow chart of embodiment three;

Fig. 11 is the flow chart of embodiment four;

Fig. 12 is a schematic structural diagram of a CPM message transmission system in a large message mode according to an embodiment of the present invention.

Detailed ways

Functional Overview

Due to the large space occupied by CPM messages in the large message mode, SIP messages cannot be directly used for carrying them. Different from the transmission method of CPM messages in page-mode mode, the transmission paths of CPM messages in large message mode are divided into signaling paths and media paths. Commands are transmitted along the signaling path, and media are transmitted along the media path. Therefore, in the embodiment of the present invention, when transmitting the large message mode CPM message to the group, first use the session invitation message (INVITE) of the large message mode CPM message to carry out media negotiation with the reachable recipients of the CPM system in the group , establish a transmission link between the sending party CPM client and the receiving party CPM client, through the established transmission link, use the message session relay protocol (TheMessage Session Relay Protocol, referred to as MSRP) protocol to the above receiving party CPM client The terminal transmits the message body of the CPM message in the large message mode, that is, the content of the CPM message.

It should be noted that the large message mode CPM message referred to in the embodiment of the present invention is a CPM message whose size exceeds a preset limit (for example, 300KB) in the CPM specification formulated by OMA, and the large message mode CPM message cannot be used directly. SIP messages are carried.

In the case of no conflict, the embodiments in the present application and the features in the embodiments can be combined with each other.

The preferred embodiments of the present invention will be described below in conjunction with the accompanying drawings. It should be understood that the preferred embodiments described here are only used to illustrate and explain the present invention, and are not intended to limit the present invention.

According to an embodiment of the present invention, a method for transmitting a large message mode CPM message is firstly provided, the method is used to send a large message mode CPM message to a target group, and in the embodiment of the present invention, the receiver is a CPM in the target group The reachable recipients of the system.

Fig. 1 is the flowchart of the CPM message transmission method according to the large message mode of the embodiment of the present invention, as shown in Fig. 1, for the reachable receiver of the CPM system in the target group, according to the large message mode CPM of the embodiment of the present invention Message transmission method mainly comprises the following steps (step S101-step S107):

Step S101: the sender's CPM client sends a session invitation message of a large message mode CPM message, and the session invitation message reaches the receiver's CPM client via the CPM control functional entity of the target group;

Step S103: the receiver CPM client receives the above session invitation message, negotiates with the sender CPM client, and establishes a media transmission link between the sender CPM client and the receiver CPM client;

Step S105: the sender CPM client sends the content of the large message mode CPM message to the receiver CPM client through the above media transmission link;

Step S107: The CPM client of the sending party or the CPM client of the receiving party initiates the process of ending the CPM message session in the large message mode.

The details of each of the above processes are further described below.

(1) Step S101

The above session invitation message received by the CPM control functional entity is sent by the CPM client of the sender, and the session invitation message is first sent to the first participating functional entity to which the sender belongs via the first SIP/IP core network belonging to the sender, and then, the second A participating function entity then sends the session invitation message to the CPM control function entity via the first SIP/IP core network and a third SIP/IP core network associated with the CPM control function entity.

Specifically, as shown in Figure 2, the process may include the following two steps:

Step 1, the CPM client of the sender sends the above session invitation message to the first participating functional entity to which the sender belongs via the first SIP/IP core network to which the sender belongs;

Step 2, the first participating functional entity sends the session invitation message to the CPM control functional entity via the first SIP/IP core network and the third SIP/IP core network.

After receiving the session invitation message, the CPM control function entity sends the session invitation message to the recipient CPM client. Specifically, as shown in Figure 2, the path for the CPM control function entity to send the session invitation message to the recipient CPM client is: CPM control function entity -> the third SIP/IP core network -> the second SIP/IP core network -> Second Participating Functional Entity -> Second SIP/IP Core Network -> Receiver CPM Client. Specifically, the following steps may be included:

Step 1, the CPM control function entity sends the above-mentioned session invitation message to the third SIP/IP core network;

Step 2, the third SIP/IP core network forwards the received session invitation message to the second SIP/IP core network;

Step 3, the second SIP/IP core network forwards the received session invitation message to the second participating functional entity;

Step 4, the second participating functional entity sends the received session invitation message to the second SIP/IP core network;

Step 5, the second SIP/IP core network forwards the received session invitation message to the above-mentioned receiving party CPM client.

In the specific implementation process, when the sender CPM client sends the session invitation message to the receiver CPM client, as shown in Figure 2, each network element will send the session invitation message to it after receiving the session invitation message. The network element of the session invitation message returns a response message (100 Trying).

(2) Step S103

In the specific implementation process, the established media transmission link between the sender's CPM client and the receiver's CPM client can be an MSRP protocol link. Specifically, there are two methods for establishing the media transmission link. The following are respectively These two methods are introduced.

method one

Specifically, as shown in FIG. 3, establishing a media transmission link between the sender CPM client and the receiver CPM client in the method may include the following steps:

Step 1, the recipient CPM client returns the successful response message (200OK) to the second participating functional entity via the second SIP/IP core network, and receives the final confirmation message sent by the second participating functional entity, and establishes or selects to connect with the second participating functional entity. a first media transport link between functional entities;

Specifically, the first media transmission link between the recipient CPM client and the second participating functional entity may be established, or the media transmission link between the current recipient CPM client and the second participating functional entity may be selected as the second media transmission link. a media transmission link;

Step 2, the second participating functional entity sends a successful response message to the CPM control functional entity via the second SIP/IP core network and the third SIP/IP core network;

Step 3, the CPM control functional entity sends a success response message to the first participating functional entity via the third SIP/IP core network and the first SIP/IP core network;

Step 4, the first participating functional entity returns an acknowledgment message (ACK) to the CPM control functional entity via the first SIP/IP core network and the third SIP/IP core network;

Step 5, the second participating functional entity receives the return confirmation message from the CPM control functional entity via the third SIP/IP core network and the second SIP/IP core network, and establishes or selects the second media transmission with the first participating functional entity link;

Step 6, the first participating functional entity sends a successful response message to the sender CPM client via the first SIP/IP core network;

Step 7: The first participating function entity receives the confirmation message returned by the sender's CPM client via the first SIP/IP core network, and establishes or selects a third media transmission link with the sender.

Method Two

In this method, the network entity between the receiver CPM client and the sender CPM client first forwards the success response message returned by the receiver CPM client to the sender CPM client, and returns the final confirmation to the sender CPM client. When a message is sent, a media transmission path is established. Specifically, as shown in FIG. 4, establishing a media transmission link between the sender CPM client and the receiver CPM client in the method may include the following steps:

Step 1, the success response message (200OK) returned by the receiver's CPM client to the second participating functional entity via the second SIP/IP core network;

Step 2, the second participating functional entity sends a successful response message to the CPM control functional entity via the second SIP/IP core network and the third SIP/IP core network;

Step 3, the CPM control functional entity sends a success response message to the first participating functional entity via the third SIP/IP core network and the first SIP/IP core network;

Step 4, the first participating functional entity sends a CPM client success response message to the sender via the first SIP/IP core network;

Step 5, the sender's CPM client receives the successful response message, and establishes or selects the acknowledgment message (ACK) returned to the first participating functional entity via the first SIP/IP core network to establish or select the communication between the first participating functional entity and the sending party. a third media transmission link;

Similarly, a new media transmission link may be established between the sender CPM client and the first participating functional entity, or a currently existing media transmission link between the sender CPM client and the first participating functional entity may be selected.

Step 6, the first participating functional entity sends a confirmation message via the first SIP/IP core network and the third SIP/IP core network and the CPM control functional entity;

Step 7, the second participating functional entity receives the confirmation message sent by the third SIP/IP core network and the second SIP/IP core network of the CPM control functional entity, and establishes or selects the second media transmission link with the first participating functional entity road;

Step 8: The receiver CPM client receives the confirmation message sent by the second participating functional entity via the second SIP/IP core network, and establishes or selects the first media transmission link with the second participating functional entity.

(3) Step S105

After establishing the media transmission link between the CPM client of the sending party and the CPM client of the receiving party, the CPM client of the sending party transmits the message body of the CPM message in the large message mode (that is, the large message) through the established media transmission link. The content of mode CPM message) is sent to receiver CPM client, specifically, as shown in Figure 5, the processing of this step can comprise the following steps:

Step 1, the sender CPM client sends the content of the large message mode CPM message to the first participating functional entity through the above-mentioned third media transmission link;

Step 2, the first participating functional entity sends the content to the second participating functional entity through the second media transmission link;

In step 3, the second participating function entity forwards the content to the recipient CPM client through the first media transmission link.

(4) Step S107

After the sender CPM client sends the content of the large message mode CPM message to the receiver CPM client, it will initiate the session end process. Specifically, the session end process can be initiated by the sender CPM client or by the receiver CPM client. Initiated by the client, described below.

The session end process is initiated by the sender CPM client

Specifically, as shown in Figure 6, the process of initiating the session end process by the sender CPM client mainly includes the following steps:

Step 1, the sender CPM client sends an indication message indicating the end of the large message mode CPM message transmission to the first participating functional entity via the first SIP/IP core network;

Step 2, the first participating functional entity sends an indication message to the CPM control functional entity via the first SIP/IP core network and the third SIP/IP core network;

Step 3, the CPM control functional entity sends the instruction message to the second participating functional entity through the third SIP/IP core network and the second SIP/IP core network;

Step 4, the second participating functional entity sends an indication message to the recipient CPM client via the second SIP/IP core network;

Step 5, the recipient CPM client receives the indication message, and sends a response message to the second participating functional entity via the second SIP/IP core network;

Step 6, the second participating functional entity sends a response message to the CPM control functional entity via the second SIP/IP core network and the third SIP/IP core network;

Step 7, the CPM control function entity sends the response message to the first participating function via the third SIP/IP core network and the first SIP/IP core network;

Step 8, the first participating function entity sends a response message to the sender via the first SIP/IP core network.

The session end process is initiated by the recipient CPM client

Specifically, as shown in FIG. 7 , the session termination process initiated by the recipient CPM client mainly includes the following steps:

Step 1, the recipient CPM client sends an indication message indicating the end of the large message mode CPM message transmission to the second participating functional entity via the second SIP/IP core network;

Step 2, the second participating functional entity sends the indication message to the CPM control functional entity via the second SIP/IP core network and the third SIP/IP core network;

Step 3, the CPM control functional entity sends the indication message to the first participating functional entity via the third SIP/IP core network and the first SIP/IP core network;

Step 4, the first participating functional entity sends an indication message to the sender CPM client via the first SIP/IP core network;

Step 5, the sender CPM client receives the indication message, and sends a response message of the indication message to the first participating functional entity via the first SIP/IP core network;

Step 6, the first participating functional entity returns a response message to the CPM control functional entity via the first SIP/IP core network and the third SIP/IP core network;

Step 7, the CPM control function entity returns a response message to the second participating function via the third SIP/IP core network and the second SIP/IP core network;

In step 8, the second participating function entity sends a response message to the recipient CPM client via the second SIP/IP core network.

Through the above-mentioned CPM message transmission method in the large message mode in the embodiment of the present invention, the CPM message in the large message mode can be sent to the reachable recipients of the CPM system in the target group.

In the specific implementation process, the target group includes multiple receivers, and these receivers may include receivers reachable by the CPM system, and may also include receivers unreachable by the CPM system. When the sender sends a large message to the target group For a CPM message, as long as the target group includes a reachable receiver of the CPM system, the above method can be used to transmit the CPM message in the large message mode.

In order to further understand the specific implementation manners of the technical solutions provided by the embodiments of the present invention, specific examples will be used below to illustrate.

In the following embodiments, the sender's CPM client is CPM Client A, the first participating functional entity that the sender belongs to is Participating Function A, and the CPM system within the target group can reach the receiver's CPM client as CPM Client B , the second participating functional entity belonging to the recipient is Participating Function B, the first SIP/IP core network belonging to the sender is SIP/IP Core A, and the CPM control functional entity corresponding to the target group is CPM Controlling Function X, The third SIP/IP core network corresponding to the CPM control function entity is SIP/IP Core X, and the second SIP/IP core network to which the reachable receiver belongs is SIP/IP Core B.

Embodiment one

In this embodiment, the media transmission link between CPM Client A and CPM Client B is implemented using the first method above, and the session termination process is initiated by CPM Client B.

Fig. 8 is the flowchart of CPM Client A transmitting large message mode CPM message to CPM Client B in the target group in the present embodiment, as shown in Fig. 8, CPM Client A transmits large message to CPM Client B in the target group The mode CPM message mainly includes the following steps:

Step 1, CPM Client A sends a session invitation message (CPM LargeMessage Invitation) of a large message mode CPM message to ParticipatingFunction A via SIP/IP Core A;

Step 2, Participating Function A forwards the session invitation message to CPM Controlling Function X via SIP/IP Core A and SIP/IPCore X;

Step 3, CPM Controlling Function X sends SIP/IP Core B session invitation message to Participating Function B via SIP/IP Core X and SIP/IP Core B;

Step 4, Participating Function B sends the session invitation message to CPM Client B through SIP/IP Core B;

Step 5, CPM Client B receives the above session invitation message, and sends a successful response message to Participating Function B via SIP/IP CoreB;

Specifically, CPM Client B sends the above successful response message to the SIP/IP Core B to which it belongs, and after receiving the successful response message, SIP/IP Core B forwards the successful response message to the Participating Function B to which the receiver belongs.

Step 6, Participating Function B returns the final confirmation message to CPMClient B via SIP/IP Core B;

Specifically, Participating Function B first sends the above-mentioned final confirmation message (ACK) to SIP/IP Core B, and after receiving the final confirmation message, SIP/IP Core B forwards the final confirmation message to CPM Client B;

Step 7, CPM Client B receives this final confirmation message, establishes the first media transmission link (can be MSRP link) between ParticipatingFunction B;

If there is a media transmission link between CPM Client B and Participating Function B, an existing media transmission link can also be selected as the CPM message media transmission link in the large message mode.

Step 8, Participating Function B sends a successful response message to CPM Controlling Function X through SIP/IP Core B and SIP/IPCore X, and CPM Controlling Function X sends a successful response message to Participating via SIP/IP Core X and SIP/IP Core A Function A;

The execution of this step is carried out simultaneously with the step 6 above.

Specifically, Participating Function B first sends the successful response message to SIP/IP Core B, and after receiving the successful response message, SIP/IP Core B forwards the successful response message to SIP/IP Core X, and SIP/IP Core X Forward the received successful response message to CPM Controlling Function X, and CPM Controlling Function X sends the successful response message to SIP/IP Core X, and then SIP/IPCore X sends the successful response message to SIP/IP Core A, SIP /IP Core A then forwards the received successful response message to Participating Function A;

Step 9, Participating Function A sends a final confirmation message to Participating Function B through SIP/IP Core A, SIP/IP CoreX and SIP/IP Core B;

Specifically, Participating Function A first sends the above-mentioned final confirmation message to SIP/IP Core A, and after receiving the final confirmation message, SIP/IP Core A forwards the final confirmation message to SIP/IP Core X, and SIP/IP Core X then forwards the received final confirmation message to Participating Function B through SIP/IP Core B.

Step 10, Participating Function B receives the above-mentioned final confirmation message, and establishes a second media transmission link (may be an MSRP link) with Participating Function A;

Similarly, the existing media transmission link between Participating Function B and Participating Function A can also be selected.

Step 11, Participating Function A returns a successful response message to CPMClient A via SIP/IP Core A;

This step is carried out simultaneously with the above step 9.

Specifically, Participating Function A first sends a successful response message to SIP/IP Core A; then, SIP/IP Core A forwards the received successful response message to CPM ClientA;

Step 12, CPM Client A sends a final confirmation message to its belonging Participating Function A;

Specifically, CPM Client A first returns the final confirmation message to SIP/IP core network A; then, SIP/IP core network A forwards the final confirmation message to ParticipatingFunction A;

Step 13, Participating Function A receives the above-mentioned final confirmation message, and establishes a third media transmission link (may be an MSRP link) between CPM Client A and Participating Function A;

Similarly, the existing media transmission link between CPM Client A and Participating Function A can also be selected.

Step 14, CPM Client A sends the content of the CPM message in the large message mode (CPM Large Message Media) to Participating Function A through the above-mentioned third media transmission link;

Step 15, Participating Function A sends the content of the large message mode CPM message to the participating function entity ParticipatingFunction B to which the above-mentioned CPM Client B belongs in the target group through the second media transmission link between it and Participating Function B;

Step 16, Participating Function B sends the content of the received large CPM message to CPMClient B through the first media transmission link between it and CPM Client B;

Step 17, CPM Client B sends a successful response message (200OK) to Participating Function B through the first media transmission link between it and Participating Function B;

Step 18, Participating Function B sends the above success response message to Participating Function A through the second media transmission link between it and Participating Function A to which the sender belongs;

Step 19, Participating Function A returns a successful response message to CPMClientA through the third media transmission link;

Step 20, CPM Client B sends an indication message (BYE) indicating the end of transmission to ParticipatingFunction B through SIP/IP Core B;

Step 21, Participating Function B sends an instruction message to CPM Controlling Function X through SIP/IP Core B and SIP/IPCore X, and CPM Controlling Function X sends an instruction message to Parcipating Function A through SIP/IP Core X and SIP/IP Core A;

Specifically, Participating Function B sends an indication message to SIP/IP Core B, SIP/IP Core B forwards the received indication message to SIP/IP Core X, and SIP/IP Core X sends the received indication message to CPM Controlling Function X, CPMControlling Function X sends the instruction message to SIP/IP Core X, SIP/IPCore X forwards the received instruction message to SIP/IP Core A, and SIP/IP Core A forwards the received instruction message to Participating Function A.

Step 22, Participating Function A returns the indication message to CPM Client A via SI/IP Core A;

Specifically, first, Participating Function A sends the indication message to SIP/IPCore A, and then SIP/IP Core A forwards the indication message to CPM Client A.

Step 23, CPM Client A sends a response message (200OK) to the above indication message to ParticipatingFunction A via SIP/IP Core A;

Step 24, Participating Function A sends the above response message to CPM Controlling Function X via SIP/IP Core A and SIP/IPCore X;

Specifically, Participating Function A first sends the above response message to SIP/IP Core A, then SIP/IP Core A forwards the above response message to SIP/IP Core X, and SIP/IP Core X forwards the above response message to CPM ControllingFunction X.

Step 25, CPM Controlling Function X sends the above response message to Participating Function B via SIP/IPCore X and SIP/IP Core B;

Specifically, CPM Controlling Function X first forwards the above response message to SIP/IP Core X, SIP/IP Core X forwards the above response message to SIP/IP Core B, and then SIP/IP Core B forwards the above response message To ParticipatingFunction B.

Step 26, Participating Function B sends the above response message to CPM Client B via SIP/IP CoreB.

Specifically, Participating Function B first forwards the above response message to SIP/IP Core B, and then SIP/IP Core B forwards the above response message to CPMClient B.

Embodiment two

In this embodiment, the media transmission link between CPM Client A and CPM Client B is implemented using the first method above, and CPM Client A initiates the session end process.

Fig. 9 is the flowchart of CPM Client A transmitting large message mode CPM message to CPM Client B in the target group in the present embodiment, as shown in Fig. 9, CPM Client A transmits large message to CPM Client B in the target group The mode CPM message mainly includes the following steps:

Step 1, CPM Client A sends a session invitation message (CPM LargeMessage Invitation) of a large message mode CPM message to ParticipatingFunction A via SIP/IP Core A;

Step 2, Participating Function A forwards the session invitation message to CPM Controlling Function X via SIP/IP Core A and SIP/IPCore X;

Step 3, CPM Controlling Function X sends SIP/IP Core B session invitation message to Participating Function B via SIP/IP Core X and SIP/IP Core B;

Step 4, Participating Function B sends the session invitation message to CPM Client B through SIP/IP Core B;

Step 5, CPM Client B receives the above session invitation message, and sends a successful response message to Participating Function B via SIP/IP CoreB;

Specifically, CPM Client B sends the above successful response message to the SIP/IP Core B to which it belongs, and after receiving the successful response message, SIP/IP Core B forwards the successful response message to the Participating Function B to which the receiver belongs.

Step 6, Participating Function B returns the final confirmation message to CPMClient B via SIP/IP Core B;

Specifically, Participating Function B first sends the above-mentioned final confirmation message (ACK) to SIP/IP Core B, and after receiving the final confirmation message, SIP/IP Core B forwards the final confirmation message to CPM Client B;

Step 7, CPM Client B receives this final confirmation message, establishes the first media transmission link (can be MSRP link) between ParticipatingFunction B;

If there is a media transmission link between CPM Client B and Participating Function B, an existing media transmission link can also be selected as the CPM message media transmission link in the large message mode.

Step 8, Participating Function B sends a successful response message to CPM Controlling Function X through SIP/IP Core B and SIP/IPCore X, and CPM Controlling Function X sends a successful response message to Participating via SIP/IP Core X and SIP/IP Core A Function A;

The execution of this step is carried out simultaneously with the step 6 above.

Specifically, Participating Function B first sends the successful response message to SIP/IP Core B, and after receiving the successful response message, SIP/IP Core B forwards the successful response message to SIP/IP Core X, and SIP/IP Core X Forward the received successful response message to CPM Controlling Function X, and CPM Controlling Function X sends the successful response message to SIP/IP Core X, and then SIP/IPCore X sends the successful response message to SIP/IP Core A, SIP /IP Core A then forwards the received successful response message to Participating Function A;

Step 9, Participating Function A sends a final confirmation message to Participating Function B through SIP/IP Core A, SIP/IP CoreX and SIP/IP Core B;

Specifically, Participating Function A first sends the above-mentioned final confirmation message to SIP/IP Core A, and after receiving the final confirmation message, SIP/IP Core A forwards the final confirmation message to SIP/IP Core X, and SIP/IP Core X then forwards the received final confirmation message to Participating Function B through SIP/IP Core B.

Step 10, Participating Function B receives the above-mentioned final confirmation message, and establishes a second media transmission link (may be an MSRP link) with Participating Function A;

Similarly, the existing media transmission link between Participating Function B and Participating Function A can also be selected.

Step 11, Participating Function A returns a successful response message to CPMClientA via SIP/IP Core A;

This step is carried out simultaneously with the above step 9.

Specifically, Participating Function A first sends a successful response message to SIP/IP Core A; then, SIP/IP Core A forwards the received successful response message to CPM Client A;

Step 12, CPM Client A sends a final confirmation message to its belonging Participating Function A;

Specifically, CPM Client A first returns the final confirmation message to SIP/IP core network A; then, SIP/IP core network A forwards the final confirmation message to ParticipatingFunction A;

Step 13, Participating Function A receives the above-mentioned final confirmation message, and establishes a third media transmission link (may be an MSRP link) between CPM Client A and Participating Function A;

Similarly, the existing media transmission link between CPM Client A and Participating Function A can also be selected.

Step 14, CPM Client A sends the content of the CPM message in the large message mode (CPM Large Message Media) to Participating Function A through the above-mentioned third media transmission link;

Step 15, Participating Function A sends the content of the large message mode CPM message to the participating function entity ParticipatingFunction B to which the above-mentioned CPM Client B belongs in the target group through the second media transmission link between it and Participating Function B;

Step 16, Participating Function B sends the content of the received large CPM message to CPMClient B through the first media transmission link between it and CPM Client B;

Step 17, CPM Client B sends a successful response message (200OK) to Participating Function B through the first media transmission link between it and Participating Function B;

Step 18, Participating Function B sends the above success response message to Participating Function A through the second media transmission link between it and Participating Function A to which the sender belongs;

Step 19, Participating Function A returns a successful response message to CPMClientA through the third media transmission link;

Step 20, CPM Client A sends an indication message (BYE) indicating the end of the transmission to ParticipatingFunction A through SIP/IP Core A;

Step 21, Participating Function A sends an instruction message through SIP/IP Core A, SIP/IPCore X, and CPM Controlling Function X, and CPM Controlling Function X sends an instruction message to Participating Function B through SIP/IP Core X and SIP/IP Core B;

Specifically, Participating Function A sends an indication message to SIP/IP Core A, SIP/IP Core A forwards the received indication message to SIP/IP Core X, and SIP/IP Core X sends the received indication message to CPM Controlling Function X, CPMControlling Function X sends the indication message to SIP/IP Core X, SIP/IP Core X forwards the received indication message to SIP/IP Core B, and SIP/IP Core B forwards the received indication message to Participating Function B.

Step 22, Participating Function B returns the indication message to CPM Client B via SIP/IP Core B;

Specifically, first, Participating Function B sends the indication message to SIP/IPCore B, and then SIP/IP Core B forwards the indication message to CPM Client B.

Step 23, CPM Client B sends a response message (200OK) to the above indication message to ParticipatingFunction B via SIP/IP Core B;

Step 24, Participating Function B sends the above response message to CPM Controlling Function X via SIP/IP Core B and SIP/IPCore X;

Specifically, Participating Function B first sends the above response message to SIP/IP Core B, then SIP/IP Core B forwards the above response message to SIP/IP Core X, and SIP/IP Core X forwards the above response message to CPM ControllingFunction X.

Step 25, CPM Controlling Function X sends the above response message to Participating Function A via SIP/IPCore X and SIP/IP Core A;

Specifically, CPM Controlling Function X first forwards the above response message to SIP/IP Core X, SIP/IP Core X forwards the above response message to SIP/IP Core A, and then SIP/IP Core A forwards the above response message to ParticipatingFunction A.

Step 26, Participating Function A sends the above response message to CPM Client A via SIP/IP CoreA.

Specifically, Participating Function A first forwards the above response message to SIP/IP Core A, and then SIP/IP Core A forwards the above response message to CPMClient A.

Embodiment three

In this embodiment, the media transmission link between CPM Client A and CPM Client B is implemented using the second method above, and the session termination process is initiated by CPM Client B.

Fig. 10 is the flow chart of CPM Client A transmitting large message mode CPM message to CPM ClientB in the target group in the present embodiment, as shown in Fig. 10, CPM Client A transmits large message mode to CPM Client B in the target group The CPM message mainly includes the following steps:

Step 1, CPM Client A sends a session invitation message (CPM LargeMessage Invitation) of a large message mode CPM message to ParticipatingFunction A via SIP/IP Core A;

Step 2, Participating Function A forwards the session invitation message to CPM Controlling Function X via SIP/IP Core A and SIP/IPCore X;

Step 3, CPM Controlling Function X sends SIP/IP Core B session invitation message to Participating Function B via SIP/IP Core X and SIP/IP Core B;

Step 4, Participating Function B sends the session invitation message to CPM Client B through SIP/IP Core B;

Step 5, CPM Client B receives the above session invitation message, and sends a successful response message to Participating Function B via SIP/IP CoreB;

Specifically, CPM Client B sends the above successful response message to the SIP/IP Core B to which it belongs, and after receiving the successful response message, SIP/IP Core B forwards the successful response message to the Participating Function B to which the receiver belongs.

Step 6, Participating Function B sends a successful response message to CPM Controlling Function X through SIP/IP Core B and SIP/IPCore X, and CPM Controlling Function X sends a successful response message to Participating via SIP/IP Core X and SIP/IP Core A Function A;

Specifically, Participating Function B first sends the successful response message to SIP/IP Core B, and after receiving the successful response message, SIP/IP Core B forwards the successful response message to SIP/IP Core X, and SIP/IP Core X Forward the received successful response message to CPM Controlling Function X, and CPM Controlling Function X sends the successful response message to SIP/IP Core X, and then SIP/IPCore X sends the successful response message to SIP/IP Core A, SIP /IP Core A then forwards the received successful response message to Participating Function A;

Step 7, Participating Function A returns a successful response message to CPMClient A via SIP/IP Core A;

Specifically, Participating Function A first sends a successful response message to SIP/IP Core A; then, SIP/IP Core A forwards the received successful response message to CPM Client A;

Step 8, CPM Client A sends a final confirmation message to its belonging Participating Function A via SIP/IP Core A;

Specifically, CPM Client A first returns the final confirmation message to SIP/IP core network A; then, SIP/IP core network A forwards the final confirmation message to ParticipatingFunction A;

Step 9, Participating Function A receives the above-mentioned final confirmation message, and establishes a third media transmission link (may be an MSRP link) between CPM Client A and Participating Function A;

If there is a media transmission link between CPM Client A and Participating Function A, an existing media transmission link can also be selected as the CPM message media transmission link in the large message mode.

Step 10, Participating Function A sends a final confirmation message to CPM Controlling Function X through SIP/IP Core A and SIP/IPCore X, and CPM Controlling Function X sends a final confirmation message to Participating Function B through SIP/IP Core X and SIP/IP Core B ;

Specifically, Participating Function A first sends the above-mentioned final confirmation message to SIP/IP Core A, and after receiving the final confirmation message, SIP/IP Core A forwards the final confirmation message to SIP/IP Core X, and SIP/IP Core X then sends the received final confirmation message to CPM Controlling Function X, and CPM Controlling Function X sends the successful response message to SIP/IP Core X, and then SIP/IPCore X forwards it to Participating Function B through SIP/IP Core B .

Step 11, Participating Function B receives the above-mentioned final confirmation message, and establishes a second media transmission link (may be an MSRP link) with Participating Function A;

Similarly, the existing media transmission link between Participating Function B and Participating Function A can also be selected.

Step 12, Participating Function B returns the final confirmation message to CPMClient B via SIP/IP Core B;

Specifically, Participating Function B first sends the above-mentioned final confirmation message (ACK) to SIP/IP Core B, and after receiving the final confirmation message, SIP/IP Core B forwards the final confirmation message to CPM Client B;

Step 13, CPM Client B receives this final confirmation message, establishes the first media transmission link (can be MSRP link) between Participating Function B;

Similarly, the existing media transmission link between CPM Client B and Participating Function B can also be selected.

Step 14, CPM Client A sends the content of the CPM message in the large message mode (CPM Large Message Media) to Participating Function A through the above-mentioned third media transmission link;

Step 15, Participating Function A sends the content of the large message mode CPM message to the participating function entity ParticipatingFunction B to which the above-mentioned CPM Client B belongs in the target group through the second media transmission link between it and Participating Function B;

Step 16, Participating Function B sends the content of the received large CPM message to CPMClient B through the first media transmission link between it and CPM Client B;

Step 17, CPM Client B sends a successful response message (200OK) to Participating Function B through the first media transmission link between it and Participating Function B;

Step 18, Participating Function B sends the above success response message to Participating Function A through the second media transmission link between it and Participating Function A to which the sender belongs;

Step 19, Participating Function A returns a successful response message to CPMClientA through the third media transmission link;

Step 20, CPM Client B sends an indication message (BYE) indicating the end of transmission to ParticipatingFunction B through SIP/IP Core B;

Step 21, Participating Function B sends an instruction message to CPM Controlling Function X through SIP/IP Core B and SIP/IPCore X, and CPM Controlling Function X sends an instruction message to Participating Function A through SIP/IP Core X and SIP/IP Core A;

Specifically, Participating Function B sends an indication message to SIP/IP Core B, SIP/IP Core B forwards the received indication message to SIP/IP Core X, and SIP/IP Core X sends the received indication message to CPM Controlling Function X, CPMControlling Function X sends the instruction message to SIP/IP Core X, SIP/IPCore X forwards the received instruction message to SIP/IP Core A, and SIP/IP Core A forwards the received instruction message to Participating Function A.

Step 22, Participating Function A returns the indication message to CPM Client A via SIP/IP Core A;

Specifically, first, Participating Function A sends the indication message to SIP/IPCore A, and then SIP/IP Core A forwards the indication message to CPM Client A.

Step 23, CPM Client A sends a response message (200OK) to the above indication message to ParticipatingFunction A via SIP/IP Core A;

Step 24, Participating Function A sends the above response message to CPM Controlling Function X via SIP/IP Core A and SIP/IPCore X;

Specifically, Participating Function A first sends the above response message to SIP/IP Core A, then SIP/IP Core A forwards the above response message to SIP/IP Core X, and SIP/IP Core X forwards the above response message to CPM ControllingFunction X.

Step 25, CPM Controlling Function X sends the above response message to Participating Function B via SIP/IPCore X and SIP/IP Core B;

Specifically, CPM Controlling Function X first forwards the above response message to SIP/IP Core X, SIP/IP Core X forwards the above response message to SIP/IP Core B, and then SIP/IP Core B forwards the above response message To ParticipatingFunction B.

Step 26, Participating Function B sends the above response message to CPM Client B via SIP/IP CoreB.

Specifically, Participating Function B first forwards the above response message to SIP/IP Core B, and then SIP/IP Core B forwards the above response message to CPMClient B.

Embodiment Four

In this embodiment, the media transmission link between CPM Client A and CPM Client B is implemented using the second method above, and CPM Client A initiates the session termination process.

Fig. 11 is the flow chart of CPM Client A transmitting large message mode CPM news to CPM ClientB in the target group in the present embodiment, as shown in Figure 11, CPM Client A transmits large message mode to CPM Client B in the target group The CPM message mainly includes the following steps:

Step 1, CPM Client A sends a session invitation message (CPM LargeMessage InVitation) of a large message mode CPM message to ParticipatingFunction A via SIP/IP Core A;

Step 2, Participating Function A forwards the session invitation message to CPM Controlling Function X via SIP/IP Core A and SIP/IPCore X;

Step 3, CPM Controlling Function X sends SIP/IP Core B session invitation message to Participating Function B via SIP/IP Core X and SIP/IP Core B;

Step 4, Participating Function B sends the session invitation message to CPM Client B through SIP/IP Core B;

Step 5, CPM Client B receives the above session invitation message, and sends a successful response message to Participating Function B via SIP/IP CoreB;

Specifically, CPM Client B sends the above successful response message to the SIP/IP Core B to which it belongs, and after receiving the successful response message, SIP/IP Core B forwards the successful response message to the Participating Function B to which the receiver belongs.

Step 6, Participating Function B sends a successful response message to CPM Controlling Function X through SIP/IP Core B and SIP/IPCore X, and CPM Controlling Function X sends a successful response message to Participating via SIP/IP Core X and SIP/IP Core A Function A;

Specifically, Participating Function B first sends the successful response message to SIP/IP Core B, and after receiving the successful response message, SIP/IP Core B forwards the successful response message to SIP/IP Core X, and SIP/IP Core X Forward the received successful response message to CPM Controlling Function X, and CPM Controlling Function X sends the successful response message to SIP/IP Core X, and then SIP/IPCore X sends the successful response message to SIP/IP Core A, SIP /IP Core A then forwards the received successful response message to Participating Function A;

Step 7, Participating Function A returns a successful response message to CPMClientA via SIP/IP Core A;

Specifically, Participating Function A first sends a successful response message to SIP/IP Core A; then, SIP/IP Core A forwards the received successful response message to CPM Client A;

Step 8, CPM Client A sends a final confirmation message to its belonging Participating Function A via SIP/IP Core A;

Specifically, CPM ClientA first returns the final confirmation message to SIP/IP core network A; then, SIP/IP core network A forwards the final confirmation message to ParticipatingFunction A;

Step 9, Participating Function A receives the above-mentioned final confirmation message, and establishes a third media transmission link (may be an MSRP link) between CPM Client A and Participating Function A;

If there is a media transmission link between CPM Client A and Participating Function A, an existing media transmission link can also be selected as the CPM message media transmission link in the large message mode.

Step 10, Participating Function A sends a final confirmation message to CPM Controlling Function X through SIP/IP Core A and SIP/IPCore X, and CPM Controlling Function X sends a final confirmation message to Participating Function B through SIP/IP Core X and SIP/IP Core B ;

Specifically, Participating Function A first sends the above-mentioned final confirmation message to SIP/IP Core A, and after receiving the final confirmation message, SIP/IP Core A forwards the final confirmation message to SIP/IP Core X, and SIP/IP Core X then sends the received final confirmation message to CPM Controlling Function X, and CPM Controlling Function X sends the successful response message to SIP/IP Core X, and then SIP/IPCore X forwards it to Participating Function B through SIP/IP Core B .

Step 11, Participating Function B receives the above-mentioned final confirmation message, and establishes a second media transmission link (may be an MSRP link) with Participating Function A;

Similarly, the existing media transmission link between Participating Function B and Participating Function A can also be selected.

Step 12, Participating Function B returns the final confirmation message to CPMClient B via SIP/IP Core B;

Specifically, Participating Function B first sends the above-mentioned final confirmation message (ACK) to SIP/IP Core B, and after receiving the final confirmation message, SIP/IP Core B forwards the final confirmation message to CPM Client B;

Step 13, CPM Client B receives this final confirmation message, establishes the first media transmission link (can be MSRP link) between Participating Function B;

Similarly, the existing media transmission link between CPM Client B and Participating Function B can also be selected.

Step 14, CPM Client A sends the content of the CPM message in the large message mode (CPM Large Message Media) to Participating Function A through the above-mentioned third media transmission link;

Step 15, Participating Function A sends the content of the large message mode CPM message to the participating function entity ParticipatingFunction B to which the above-mentioned CPM Client B belongs in the target group through the second media transmission link between it and Participating Function B;

Step 16, Participating Function B sends the content of the received large CPM message to CPMClient B through the first media transmission link between it and CPM Client B;

Step 17, CPM Client B sends a successful response message (200OK) to Participating Function B through the first media transmission link between it and Participating Function B;

Step 18, Participating Function B sends the above success response message to Participating Function A through the second media transmission link between it and Participating Function A to which the sender belongs;

Step 19, Participating Function A returns a successful response message to CPMClient A through the third media transmission link;

Step 20, CPM Client A sends an indication message (BYE) indicating the end of the transmission to ParticipatingFunction A through SIP/IP Core A;

Step 21, Participating Function A sends an instruction message through SIP/IP Core A, SIP/IPCore X, and CPM Controlling Function X, and CPM Controlling Function X sends an instruction message to Participating Function B through SIP/IP Core X and SIP/IP Core B;

Specifically, Participating Function A sends an indication message to SIP/IP Core A, SIP/IP Core A forwards the received indication message to SIP/IP Core X, and SIP/IP Core X sends the received indication message to CPM Controlling Function X, CPMControlling Function X sends the indication message to SIP/IP Core X, SIP/IP Core X forwards the received indication message to SIP/IP Core B, and SIP/IP Core B forwards the received indication message to Participating Function B.

Step 22, Participating Function B returns the indication message to CPM Client B via SIP/IP Core B;

Specifically, first, Participating Function B sends the indication message to SIP/IPCore B, and then SIP/IP Core B forwards the indication message to CPM Client B.

Step 23, CPM Client B sends a response message (200OK) to the above indication message to ParticipatingFunction B via SIP/IP Core B;

Step 24, Participating Function B sends the above response message to CPM Controlling Function X via SIP/IP Core B and SIP/IPCore X;

Specifically, Participating Function B first sends the above response message to SIP/IP Core B, then SIP/IP Core B forwards the above response message to SIP/IP Core X, and SIP/IP Core X forwards the above response message to CPM ControllingFunction X.

Step 25, CPM Controlling Function X sends the above response message to Participating Function A via SIP/IPCore X and SIP/IP Core A;

Specifically, CPM Controlling Function X first forwards the above response message to SIP/IP Core X, SIP/IP Core X forwards the above response message to SIP/IP Core A, and then SIP/IP Core A forwards the above response message to ParticipatingFunction A.

Step 26, Participating Function A sends the above response message to CPM Client A via SIP/IP CoreA.

Specifically, Participating Function A first forwards the above response message to SIP/IP Core A, and then SIP/IP Core A forwards the above response message to CPMClient A.

According to an embodiment of the present invention, a large message mode CPM message transmission system is also provided. The system is used to send large message mode CPM messages to target groups.

Fig. 12 is a schematic structural diagram of a CPM message transmission system in a large message mode according to an embodiment of the present invention. As shown in Fig. 12 , the CPM message transmission system in a large message mode according to an embodiment of the present invention mainly includes: a sender CPM client 1, a source The terminal participation function entity 2, the CPM control function entity 3 of the target group, the destination terminal participation function entity 4 and the receiver CPM client 5.

Wherein, the sender CPM client 1 is used to send a session invitation message of a large message mode CPM message, and receives a successful response message, wherein the session invitation message carries a session description protocol (Session Description Protocol, referred to as SDP for short) for negotiation ) session description parameters, used to negotiate with the receiver CPM client 5, and establish a media transmission link for transmitting the content of the CPM message in the large message mode; the source participates in the functional entity 2, connects with the sender CPM client 1, and the sender The belonging participation function entity is used to receive and send the above session invitation message; the CPM control function entity 3 is connected to the source participation function entity 2, and is used to receive and send the above session invitation message; the destination end participation function entity 4 is connected to the CPM The control function entity 3 is connected, and the participating function entity belonging to the recipient is used to receive and send the above-mentioned session invitation message; the recipient CPM client 5 is connected to the destination participating function entity 4, and is used to receive the above-mentioned session invitation message.

Further, the above session invitation message also carries service indication information for distinguishing CPM messages in the large message mode. Specifically, the service indication information may be carried by the CPM Feature Tag parameter in the Accept-Contact field of the session invitation message.

The receiver CPM client 5 is further configured to send a success response message after receiving the above session invitation message. The success response message first arrives at the destination participating function entity 4, then the destination participating function entity 4 is also used to receive the above successful response message and send the received success response message, and the success response message first arrives at the CPM control function entity 3 , therefore, the CPM control function entity 3 is also used to receive and send a success response message; the success response message sent by the CPM control function entity 3 reaches the source-end participating function entity 2, therefore, the source-end participating function entity 2 is also used to receive and send Send the above successful response message; the above successful response message sent by the source participating function entity 2 reaches the sender CPM client 1, therefore, the sender CPM client 1 is also used to receive the above success response message.

Further, after receiving the above successful response message, the sender CPM client 1 is used to also send the final confirmation message of the above session invitation message.

Further, the sender CPM client 1 can also be used to select or establish a media transmission link for transmitting the content of the above-mentioned large message mode CPM message;

In addition, after the media transmission link is selected or established, the sender CPM client 1 is further configured to send the content of the CPM message in the large message mode through the media transmission link.

Further, the source participating function entity 2 is also configured to receive the final confirmation message of the session invitation message of the large message mode CPM message, and select or establish a media transmission link for transmitting the content of the large message mode CPM message. In addition, the source participating function entity 2 is also configured to send the received final confirmation message.

Moreover, the source participating function entity 2 can also be used to transmit the content of the received large message mode CPM message (from the sender CPM client 1 ) through the above-mentioned selected or established media transmission link.

Further, the above-mentioned CPM control function entity 3 is also configured to receive and send the final confirmation message of the session invitation message of the above-mentioned large message mode CPM message.

Further, the destination participating function entity 4 is further configured to receive a final confirmation message of the session invitation message of the large message mode CPM message, and select or establish a media transmission link.

Moreover, the participating function entity 4 at the destination end may also be used to transmit the content of the received large message mode CPM message (from the participating function entity 2 at the source end) through the above-mentioned selection or establishment of a media transmission link.

Further, the receiver CPM client 5 is further configured to receive the final confirmation message of the session invitation message of the CPM message in the large message mode, and select or establish a media transmission link.

Moreover, the recipient CPM client 5 is also configured to receive the content of the CPM message in the large message mode through the above-mentioned media transmission link.

In the actual application process, the source participating functional entity 2 receives and sends the final confirmation message from the above session invitation message from the sender CPM client 1, and the final confirmation message reaches the CPM control functional entity 3, and the CPM control functional entity will receive The final confirmation message is sent; the destination participating function entity 4 receives and sends the final confirmation message from the CPM control function entity, and the final confirmation message reaches the recipient CPM client 5 .

In addition, the source participating function entity 2 receives the content of the large message mode CPM message through the media transmission link with the sender CPM client 1, and sends the content of the large message mode CPM message to the destination participating function entity through it. 4 through the media transmission link between 4, the purpose participating function entity 4 receives the content of the CPM message in large message mode, and sends the content of the CPM message in large message mode through the media link between it and the recipient CPM client To the recipient CPM client 5.

Further, after the content transmission of the large message mode CPM message ends, or after the sender CPM client receives the success response message of the last MSRP transmission packet (SEND) sent by it, the sender CPM client 1 is also used to send Indication message indicating the end of the CPM message session in large message mode. The recipient CPM client is further configured to receive the above indication message indicating the end of the large message mode CPM message session, and send a response message to the indication message.

Or, after the content transmission of the above-mentioned large message mode CPM message ends, the receiver CPM client 2 is also used to send an indication message indicating the end of the large message CPM message session; correspondingly, the sender CPM client is also used to receive the indication message In the message mode, the CPM message indicates the above-mentioned indication message that the session ends, and sends a response message to the above-mentioned indication message.

Wherein, as shown in FIG. 12 , the establishment of the media transmission link between the sender CPM client 1 and the receiver CPM client 2 can be three media links: the sender CPM client 1 and the source participating function entity 2 , the media link between the source participating function entity 2 and the destination participating function entity 4 , and the media link between the destination participating function entity 4 and the receiving CPM client 2 .

Further, the target group for sending the large message mode CPM message by the sender's CPM client can be a temporary group (Ad-hoc group) or a preset group (Pre-defined group). When the target group When it is an Ad-hoc group, the session invitation message sent by the sender CPM client 1 carries the list information of each receiver in the target group, and/or, the header of the session invitation message sent by the sender CPM client 1 The value of the field Request-URI is the address of the CPM control function entity; when the target group is a Pre-defined group, the value of the header field Request-URI of the session invitation message sent by the sender CPM client 1 is the preset group The address of the group.

Further, if the target group is an Ad-hoc group, the CPM control function entity 3 is also configured to analyze the list information of each recipient in the target group carried in the received session invitation message, Receiver's address, send a session invitation message to each receiver one by one; if the target group is a Pre-defined group, the CPM control function entity is also used to, according to the preset group address carried in the received session invitation message, The address information of each recipient in the preset group is obtained, and a session invitation message is sent to each recipient one by one according to the address of each recipient.

As mentioned above, with the help of the technical solution provided by the embodiment of the present invention, the transmission link between the sender and the reachable receiver of the CPM system in the target group is established through the session invitation message of the CPM message in the large message mode, and the large The content of the message mode CPM message is sent to each recipient of the target group, which can solve the problem that the large message mode CPM message cannot be transmitted to the group in the current technology, and improves user experience.

The above descriptions are only preferred embodiments of the present invention, and are not intended to limit the present invention. For those skilled in the art, the present invention may have various modifications and changes. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of the present invention shall be included within the protection scope of the present invention.

Claims (25)

1. a big message pattern fused with IP message transmission method, send big message pattern fused with IP message CPM for transmit leg CPM client to target group, it is characterized in that, for the recipient that the CPM system in described target group can reach, described method comprises:

Described transmit leg CPM client sends the session invitation message of described large message mode CPM messages, and described session invitation message arrives described recipient CPM client via the CPM controlling functions entity of described target group;

Described recipient CPM client receives described session invitation message, holds consultation with described transmit leg CPM client, establishes the media transport link between described transmit leg CPM client and described recipient CPM client;

The content of described large message mode CPM messages, by described media transport link, is sent to described recipient CPM client by described transmit leg CPM client;

Described transmit leg CPM client or described recipient CPM client initiate described large message mode CPM messages conversation end flow process.

2. ask method described in 1 according to right, its feature sends described session invitation message in, described transmit leg CPM client and arrives described recipient CPM client and comprise:

Described transmit leg CPM client sends described session invitation message by SIP/IP core net, and described session invitation message arrives transmit leg ownership first and participates in functional entity;

Described first participates in functional entity sends described session invitation message by SIP/IP core net, and described session invitation message arrives described CPM controlling functions entity;

Described CPM controlling functions entity sends described session invitation message by SIP/IP core net, and described session invitation message arrives second of described recipient ownership and participates in functional entity;

Described second participates in functional entity sends described session invitation message by SIP/IP core net, and described session invitation message arrives described recipient CPM client.

3. method according to claim 2, is characterized in that,

Described session invitation message arrives transmit leg ownership first participation functional entity and comprises:

The SIP/IP core net that described transmit leg CPM client is belonged to by transmit leg sends described session invitation message, and described session invitation message arrives described first and participates in functional entity; And/or,

Described session invitation message arrives described CPM controlling functions entity and comprises:

Described first participates in functional entity sends described session invitation message by a described SIP/IP core net, and described session invitation message arrives described CPM controlling functions entity via Three S's IP/IP core net; And/or,

The second participation functional entity that described session invitation message arrives described recipient ownership comprises:

Described CPM controlling functions entity sends described session invitation message by Three S's IP/IP core net, and described session invitation message arrives described second via the 2nd SIP/IP core net and participates in functional entity; And/or,

Described session invitation message arrives described recipient CPM client and comprises:

Described second participates in the described session invitation message of functional entity by the 2nd SIP/IP core net transmission, and described session invitation message arrives described recipient CPM client.

4. method according to claim 2, is characterized in that, described media transport link comprises:

Described recipient CPM client and described second participates in the first media transport link between functional entity;

Described second participation functional entity and described first participates in the second media transport link between functional entity;

Described first participates in the 3rd media transport link between functional entity and described transmit leg CPM client.

5. method according to claim 4, is characterized in that, establishes described media transport link and comprises:

Described recipient CPM client sends the success response message of described session invitation message, and receives final acknowledge message, establishes described and the described second the first media transport link participating between functional entity;

Described second participates in functional entity receives and sends described success response message, and receives final acknowledge message, and establishment and described first participates in the second media transport link between functional entity;

Described first participates in functional entity sends described success response message, and receives final acknowledge message, establishes the 3rd media transport link between described transmit leg CPM client; And/or

The success response message that described recipient CPM client sends;

Described second participates in functional entity receives and sends described success response message;

Described CPM controlling functions entity receives and sends described success response message;

Described first participates in functional entity receives and sends described success response message;

Described transmit leg CPM client receives described success response message, send final acknowledge message, described final acknowledge message arrives described first and participates in functional entity, sets up or selects described 3rd media transport link between described first participation functional entity and described transmit leg CPM client;

Described first participates in functional entity sends final acknowledge message;

Described second participates in functional entity receives described final acknowledge message, and foundation or selection and described first participate in described second media transport link between functional entity;

Described recipient CPM client receives described final acknowledge message, and foundation or selection and described second participate in described first media transport link between functional entity.

6. the method according to claim 4 or 5, is characterized in that, the content of described large message mode CPM messages is sent to described recipient CPM client and comprises by described transmit leg CPM client:

The content of described large message mode CPM messages, by described 3rd media transport link, is sent to described first and participates in functional entity by described transmit leg CPM client;

Described first participates in functional entity by described second media transport link, described content is sent described second and participates in functional entity;

Described second participates in functional entity is forwarded to described recipient CPM client by described first media transport link by described content.

7. the method according to claim 4 or 5, is characterized in that, described first media transport link, described second media transport link and described 3rd media transport link are message session trunk protocol MSRP link.

8. method according to any one of claim 1 to 5, is characterized in that, described transmit leg CPM client is initiated described conversation end flow process and comprised:

Described transmit leg CPM client sends the Indication message of the described large message mode CPM messages conversation end of instruction;

First of transmit leg ownership participates in functional entity and receives and send described Indication message;

Described CPM controlling functions entity receives and sends described Indication message;

Second of described recipient's ownership participates in functional entity and receives and send described Indication message;

Described recipient CPM client receives described Indication message, and sends response message;

Described second participates in functional entity receives and sends described response message;

Described CPM controlling functions entity receives and sends described response message;

Described first participates in functional entity receives and sends described response message;

Described transmit leg CPM client receives described response message.

9. method according to claim 8, is characterized in that, described transmit leg is initiated described conversation end flow process and comprised:

Described transmit leg sends the Indication message of the described large message mode CPM messages end of transmission of instruction via a described SIP/IP core net;

Described first participates in functional entity receives described Indication message, and sends described Indication message via the Three S's IP/IP core net of a described SIP/IP core net and described CPM controlling functions entity associated;

Described CPM controlling functions entity receives described Indication message, and sends described Indication message by described Three S's IP/IP core net and described 2nd SIP/IP core net;

Described second participates in functional entity receives described Indication message, and sends described Indication message via described 2nd SIP/IP core net;

Described recipient CPM client receives described Indication message, and sends response message via described 2nd SIP/IP core net;

Described second participates in functional entity receives described response message, sends described response message via described 2nd SIP/IP core net and described Three S's IP/IP core net;

Described CPM controlling functions entity receives described response message, sends described response message via described Three S's IP/IP core net and a described SIP/IP core net;

Described first participates in functional entity receives described response message, and sends described response message via a described SIP/IP core net, and described transmit leg CPM client receives described response message.

10. the method according to any one of claim 2 to 5, is characterized in that, described recipient CPM client is initiated described conversation end flow process and comprised:

Described recipient's client sends the Indication message of the described large message mode CPM messages conversation end of instruction;

Described second participates in functional entity receives and sends described Indication message;

Described CPM controlling functions entity receives and sends described Indication message;

Described first participates in functional entity receives and sends described Indication message;

Described transmit leg CPM client receives described Indication message, and participates in described first the response message that functional entity sends described Indication message;

Described first participates in functional entity returns described response message to described CPM controlling functions entity;

Described CPM controlling functions entity participates in function to described second and returns described response message;

Described second participates in functional entity sends described response message to described recipient CPM client.

11. methods according to claim 10, is characterized in that, described recipient CPM client is initiated described conversation end flow process and comprised:

Described recipient CPM client sends the Indication message of the described large message mode CPM messages conversation end of instruction via the 2nd SIP/IP core net;

Described second participates in functional entity receives described Indication message, sends described Indication message via described 2nd SIP/IP core net and Three S's IP/IP core net;

Described CPM controlling functions entity receives described Indication message, sends described Indication message via described Three S's IP/IP core net and a SIP/IP core net;

Described first participates in functional entity receives described Indication message, and sends described Indication message via a described SIP/IP core net;

Described transmit leg CPM client receives described Indication message, and sends the response message of described Indication message via a described SIP/IP core net;

Described first participates in functional entity receives described response message, and sends described response message via a described SIP/IP core net and described Three S's IP/IP core net;

Described CPM controlling functions entity receives described response message, sends described response message via described Three S's IP/IP core net and described 2nd SIP/IP core net;

Described second participates in functional entity receives described response message, sends described response message via described 2nd SIP/IP core net;

Described recipient CPM client receives described response message.

12. 1 kinds of big message pattern fused with IP message transmission methods, for sending big message pattern fused with IP message to target group, it is characterized in that, if described target group comprises the recipient that CPM system can reach, then adopt big message pattern fused with IP message as described in method transmission according to any one of claim 1 to 11.

13. 1 kinds of big message pattern fused with IP message transmission systems, for sending big message pattern fused with IP message CPM to target group, it is characterized in that, comprise: transmit leg CPM client, recipient CPM client, CPM controlling functions entity, source participate in functional entity and destination participates in functional entity, wherein

Described transmit leg CPM client, for sending the session invitation message of large message mode CPM messages, wherein, carries the Session Description Protocol SDP conversation description parameter of holding consultation in described session invitation message;

Described source participates in functional entity, is the participation functional entity of transmit leg ownership, for receiving and sending described session invitation message;

Described CPM controlling functions entity, for receiving and sending described session invitation message;

Described destination participates in functional entity, is the participation functional entity of recipient's ownership, for receiving and sending described session invitation message;

Described recipient CPM client, for receiving described session invitation message.

14. systems according to claim 13, is characterized in that, after receiving described session invitation message,

Described recipient CPM client is also for sending success response message;

Described destination participates in functional entity also for receiving and sending described success response message;

Described CPM controlling functions entity is also for receiving and sending described success response message;

Described source participates in functional entity also for receiving and sending described success response message;

Described transmit leg CPM client is also for receiving described success response message.

15. systems according to claim 13, is characterized in that, after receiving the success response message of described session invitation message,

Described transmit leg CPM client is also for sending the final acknowledge message of described session invitation message; And/or,

Described transmit leg CPM client is also for selecting or set up the media transport link of the content for transmitting large message mode CPM messages; And/or,

Described transmit leg CPM client is also for sending the content of described large message mode CPM messages by media transport link.

16. systems according to claim 13, is characterized in that, described recipient CPM client, also for receiving the final acknowledge message of the described session invitation message of large message mode CPM messages, being selected or setting up media transport link.

17. systems according to claim 13, is characterized in that,

Described source participates in functional entity also for receiving the final acknowledge message of the described session invitation message of large message mode CPM messages, selects or sets up media transport link; And/or,

Described source participates in functional entity also for being sent the content of large message mode CPM messages by described media transport link.

18. systems according to claim 13, is characterized in that, described CPM controlling functions entity is also for receiving and sending the final acknowledge message of the described session invitation message of large message mode CPM messages.

19. systems according to claim 13, is characterized in that,

Described destination participates in functional entity also for receiving the final acknowledge message of the described session invitation message of large message mode CPM messages; And/or,

Described destination participates in functional entity also for selecting or setting up media transport link; And/or,

Described destination participates in functional entity also for being sent the content of large message mode CPM messages by media transport link.

20. systems according to claim 13, is characterized in that,

After the content delivery of large message mode CPM messages terminates, or receive last MSRP transmit bag SEND success response message after, described transmit leg CPM client is also for sending the Indication message indicating described large message mode CPM messages conversation end; And/or,

Described recipient CPM client is also for receiving the described Indication message indicating described large message mode CPM messages conversation end; And/or,

After described recipient CPM client receives described conversation end Indication message, send the response message of described Indication message.

21. systems according to claim 13, is characterized in that,

After the content delivery of large message mode CPM messages terminates, described recipient CPM client is also for sending the Indication message indicating described large message mode CPM messages conversation end; And/or,

After the content delivery of large message mode CPM messages terminates, described transmit leg CPM client also for receiving the described Indication message indicating described large message mode CPM messages conversation end, and sends the response message of described Indication message.

22. systems according to claim 13, is characterized in that, also carry the business indication information of the CPM message for distinguishing big message pattern in the session invitation message that described transmit leg CPM client sends.

23. systems according to claim 22, is characterized in that, described business indication information is carried by the CPMFeature Tag parameter in the Accept-Contact field of described session invitation message.

24. systems according to claim 13, is characterized in that:

If described target group is Ad-hoc group of interim group, then carry the list information of each recipient in described target group in the session invitation message that described transmit leg CPM client sends; And/or,

The value of the head field Request-URI of described session invitation message is the address of described CPM controlling functions entity; And/or,

If described target group is for presetting Pre-defined group of group, then the value of the head field Request-URI of the session invitation message of described transmit leg CPM client transmission is the address of described default group.

25. systems according to claim 13, is characterized in that,

If described target group is Ad-hoc group of interim group, then described CPM controlling functions entity is also for by resolving recipient's list of carrying in the described session invitation message that receives, obtain each recipient address in described target group, according to the address of each recipient in recipient's list, send session invitation message to each recipient described one by one; And/or,

If described target group is for presetting Pre-defined group of group, then described CPM controlling functions entity is also for according to the default group address carried in the described session invitation message that receives, obtain the address information of each recipient in described default group, and according to the address of each recipient, send described session invitation message to each recipient described one by one.