WO2010127526A1 - 向群组发送大消息模式cpm消息的方法 - Google Patents
向群组发送大消息模式cpm消息的方法 Download PDFInfo
- Publication number
- WO2010127526A1 WO2010127526A1 PCT/CN2009/073671 CN2009073671W WO2010127526A1 WO 2010127526 A1 WO2010127526 A1 WO 2010127526A1 CN 2009073671 W CN2009073671 W CN 2009073671W WO 2010127526 A1 WO2010127526 A1 WO 2010127526A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- cpm
- message
- function entity
- client
- control function
- Prior art date
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/1066—Session management
- H04L65/1101—Session protocols
- H04L65/1104—Session initiation protocol [SIP]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/06—Selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS]; Services to user groups; One-way selective calling services
- H04W4/08—User group management
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
- H04L51/56—Unified messaging, e.g. interactions between e-mail, instant messaging or converged IP messaging [CPM]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
- H04L51/04—Real-time or near real-time messaging, e.g. instant messaging [IM]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W80/00—Wireless network protocols or protocol adaptations to wireless operation
- H04W80/08—Upper layer protocols
- H04W80/10—Upper layer protocols adapted for application session management, e.g. SIP [Session Initiation Protocol]
Definitions
- the present invention relates to the field of mobile communications technologies, and in particular, to transmitting a converged IP message to a group.
- Converged IP Messaging is specifically the method of sending Large Message Mode (CPM Message) to the group. Background technique
- CPM was proposed in 2005 by the Open Mobile Architecture (OMA), which aims to achieve interoperability of multiple messaging services, provide unified messaging services, and complete a consistent and convenient messaging service experience.
- CPM integrates a variety of existing messaging services, including instant messaging (IM), push-to-talk over cellular (POC), and mobile e-mail (Mobile E-Email).
- the cartridge is called MEM), the Short Messaging Service (SMS), and the Multimedia Messaging Service (MMS).
- MEM mobile e-mail
- SMS Short Messaging Service
- MMS Multimedia Messaging Service
- OMA is developing the CPM VI.0 specification.
- the main business forms of CPM include: CPM messages based on page-mode, large message mode CPM messages based on session-mode, and other CPM session services based on session.
- the Session Initiation Protocol (CSIP) is used to send page-mode messages between the CPM client and the CPM Enabler.
- CCP Session Initiation Protocol
- 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.
- the CPM service supports a CPM Pre-defined Group and a CPM Ad-hoc Group.
- a CPM user can send a CPM paging message to a temporary group or a preset group, but when the message is large If it exceeds a certain limit, it cannot be carried by SIP MESSAGE.
- SIP MESSAGE SIP MESSAGE
- SUMMARY OF THE INVENTION The present invention has been made in view of the problem in the prior art that a CPM client cannot transmit a large message mode CPM message to a receiver in a group. To this end, the main object of the present invention is to provide an improved one.
- a method of transmitting a large message mode fused IP message CPM message to a group is provided.
- the method for transmitting a large message mode fused IP message CPM message to a group according to the present invention is used by a sender CPM client to send a large message mode CPM message to a target group, where the method includes: sending a CPM client to send a large message The message mode CPM message session invitation message, after receiving the session invitation message, the CPM control function entity sends a session invitation message for each receiver address of the group; the receiver CPM client receives the session invitation message, and performs the session invitation message with the control function entity.
- the control function entity performs media negotiation with the sender CPM client, and establishes a media transmission link between the sender CPM client and the receiver CPM client; and/or, the interworking function entity receives the session invitation message, and controls
- the functional entity performs media negotiation
- the control function entity performs media negotiation with the sender CPM client to establish a media transmission link between the sender CPM client and the control function entity; the sender CPM client transmits the medium through the media transmission link.
- the content of the message mode CPM message is sent to the receiver CPM client and/or the interworking function ; Sending CPM client or control function entity or the receiving CPM client or the interworking function entity initiating the large message mode CPM session end message flow.
- a system for transmitting a large message mode fused IP message CPM message to a group is provided.
- the system for transmitting a large message mode fused IP message CPM message to a group according to the present invention is configured to send a big message mode CPM message to a target group, where the system includes: a sender CPM client body and a destination end participating functional entity Receiver CPM client, CPM control function entity, The source side participates in the function entity, where the sender CPM client sends a session invitation message for the message mode CPM message, where the session invitation message carries the session description protocol SDP session description parameter for negotiation;
- the success response message of the session invitation message is SIP 200 OK; and is also used to establish a media transmission link; and is also used to send a media transmission request MSRP SEND based on the established media transmission link;
- the source participation functional entity that is, the participation of the sender a function entity, configured to receive and send a session invitation message; further configured to receive and send a success response message
- the success response message SIP 200 OK is also used to establish a media transmission link; is also used to receive a media transmission request MSRP SEND; and is also used to send a media transmission request to an adjacent MSRP relay node; a receiver CPM client, The receiving the session invitation message; the success response message SIP 200 OK for creating and replying to the session invitation message; also for establishing a media transmission link; and for receiving the media transmission request MSRP SEND. Further, when the CPM control function entity receives the session invitation message, it temporarily serves as the conference center.
- the CPM control function entity when receiving the session invitation message, if the receiver is a temporary group, the CPM control function entity acquires the receiver address according to the group member list carried in the message body of the session invitation message; If the recipient is a preset group, the CPM controls the function entity to obtain the recipient address from the document server. Further, the recipient address is the CPM system receiver address CPM Adress or non-CPM The system is connected to the square address non-CPMA dress. Further, when the CPM control function entity receives the session invitation message, it acts as a back-to-back user agent B2BUA. Further, after receiving the SIP 200 OK response, the CPM control function entity attaches an "isfocus" feature parameter to the SIP 200 OK response.
- the CPM control function entity After receiving the SIP 200 OK response, the CPM control function entity sends a SIP ACK final confirmation message. Further, after receiving the SIP ACK, the CPM control function entity determines the link with the adjacent node hop according to the information provided by the SDP. Further, the sender CPM client is further configured to send a BYE request, and after receiving the BYE request from the sender, the CPM control function entity sends a BYE request for each receiver address in the target group.
- the reachable reception of the CPM client in the sender CPM client and the target group is established by the session invite message sending the big message mode CPM message.
- the media transmission link between the party's CPM clients sends the content of the large message mode CPM message to the receiver CPM client.
- the non-CPM address or the non-CPM User in the group on the one hand, by establishing a control function entity (Controlling Function) CF)
- the large message mode CPM message can be sent from the sender client to the interworking function entity in real time or near real time or non-real time.
- the interworking function entity can transmit the large message mode CPM message to the non-CPM system in real time or near real time or non-real time through the media conversion and transmission interface between it and the non-CPM system (non-CPM).
- the transmission of the large message mode CPM message from the sender to the non-non-CPM system (and/or the non-CPM system user client) can be completed.
- This feature can be enabled or disabled based on user settings and carrier policies.
- FIG. 1 is a flowchart of a method for transmitting a large message mode CPM message to a group by using a reachable receiver in a CPM system in a group as an example
- FIG. 2 is an embodiment of the present invention, A schematic diagram of a media link establishment process between a sender CPM client and a receiver CPM client in a CPM system in a group;
- FIG. 1 is a flowchart of a method for transmitting a large message mode CPM message to a group by using a reachable receiver in a CPM system in a group as an example
- FIG. 2 is an embodiment of the present invention, A schematic diagram of a media link establishment process between a sender CPM client and a receiver CPM client in a CPM system in a group
- FIG. 1 is a flowchart of a method for transmitting a large message mode CPM message to a group by using a reachable receiver in a CPM system in a group as an example
- FIG. 2 is an embodiment of
- FIG. 3 is a CPM system in a group according to an embodiment of the present invention
- the reachable receiver is a flowchart of the content of the large message mode CPM message sent by the sender CPM client to the receiver CPM client.
- FIG. 4 is a schematic diagram of a reachable receiver in a CPM system in the group according to an embodiment of the present invention; For example, a fragmentation diagram of a media link in which a sender CPM client sends a large message mode CPM message to a receiver CPM client;
- FIG. 5 is a schematic diagram of a reachable receiver in a CPM system in a group according to an embodiment of the present invention;
- FIG. 4 is a schematic diagram of a reachable receiver in a CPM system in the group according to an embodiment of the present invention.
- FIG. 6 is a flow chart of control function entity signaling and media control of a large message mode CPM message to a group transmission system according to an embodiment of the present invention
- FIG. 7 is a large message mode CPM according to an embodiment of the present invention.
- Message A functional diagram of the control function entity of the transmission system to the group. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT Because the large message mode CPM message occupies a large space, it is not possible to directly use SIP messages. Line load, unlike the page-mode mode CPM message transmission mode, the large message mode CPM message transmission path is divided into a signaling path and a media path, that is, signaling is transmitted along the signaling path, and the medium is transmitted along the media path.
- the session invitation message (INVITE) of the large message mode CPM message is used to establish a session between the sender CPM client and the receiver CPM client, and the completion is completed.
- Media negotiation establishing a transmission link between the sender CPM client and the receiver CPM client, and using the message transmission protocol (Message Session Relay Protocol, called MSRP) to the above receiver through the established transmission link
- MSRP message Session Relay Protocol
- the CPM client transmits the message body of the large message mode CPM message, that is, the content of the CPM message.
- the large message mode CPM message is sent to the group.
- the group may contain multiple receiver addresses.
- the receiver address may be a CPM Receiver Address (CPM Address) or a non-CPM Receiver Address (non-CPM Address).
- CPM CPM Receiver Address
- non-CPM Address For the CPM receiver address, it may be a reachable CPM receiver address or an unreachable receiver address. Therefore, in the embodiment of the present invention, the control function entity completes centralized management and control of the group, functions as a temporary conference center, and processes the original back-to-back user agent (B2BUA) and acts as a user agent client (User Agent Client, called UAC) and User Agent Server (UAS), the role of the server, when the request is received, as a response to the server, but in order to know what response to give, a New request.
- UAC User Agent Client
- UAS User Agent Server
- the control function entity After receiving the session invitation message, the control function entity sends a session invitation message to each receiver (CPM Address and non-CPM Address) in the group, thereby controlling the function entity and each receiver client in the destination domain ( For non-CPM Address or unreachable CPM user address refers to the interworking function entity) to establish signaling and media transmission paths. Thereby, the transfer of the large message mode CPM message between the sender client and each of the recipient clients in the group is completed.
- the large message mode CPM message in the embodiment of the present invention is a CPM message whose size exceeds a preset limit (for example, 1300 bytes) in the CPM specification formulated by the OMA, and the large message mode CPM message. It cannot be carried directly using SIP messages.
- FIG. 1 is a flowchart of a method for transmitting a large message mode CPM message to a group according to an embodiment of a reachable receiver in a CPM system in a group according to an embodiment of the present invention.
- Figure 6 Large message mode CPM messages are sent to the group to the general case.
- the method for transmitting a large message mode CPM message to a group mainly includes the following steps (step S101 - step S107): Steps S101 - S104: Sender CPM client Sending a session invitation message of a large message mode CPM message to a preset group or a temporary group, the CPM control function entity receives a session invitation message, and the CPM control function entity obtains a receiver address of the preset group or the temporary group, That is, if the receiver is a temporary group, the MIME ⁇ resource-lists> carried in the message body of the session invitation message is obtained to obtain the group member list; if the receiver presets the group, the document server [OMA-XDM-Shared-Group] ] Get the group member address.
- the CPM control function entity sends a session invitation message to each recipient one by one.
- the CPM client or the interworking function entity receives the session invitation message.
- the Call-ID of the invitation message may be different, and the invitation message in the steps S101, S102, S103, and S104 may not be the same invitation message, but considering the description and the Without ambiguity, some textual expressions of the present invention do not particularly emphasize the differentiation of the SIP messages of the same method on the same transmission path in different conversations, and if there is no special description, Contextual understanding of the invention.
- Step S105 For the CPM system in the group to reach the receiver address, the receiver CPM client receives the session invitation message, negotiates with the sender CPM client, and establishes a relationship between the sender CPM client and the receiver CPM client.
- Media transmission link or, this step may be described as: after receiving the session invitation message, the receiving CPM client negotiates with a control function entity (Controlling Function, called CF) to establish a relationship between the receiver and the control function entity.
- the transmission link, the control function entity negotiates with the sender client to establish a transmission link with the sender CPM client.
- Control Function Controlling Function
- the interworking function entity receives the session invitation message, on the one hand, establishes The media transmission link between the control function entity and the sender client, and on the other hand the media transmission link between the control function entity and the interworking function entity.
- Step S106 The sender CPM client sends the content of the large message mode CPM message to the receiver client or the non-CPM system through the media transmission link.
- Step S107 the sender CPM client or the control function entity or receiver
- the CPM client or the interworking function entity initiates a big message mode CPM message session end process. Details of each of the above processes are further described below.
- Steps S101 - S104 are for the sake of the single page.
- the SIP/IP Core node is omitted in the figure.
- the signaling transmission between each two functional entities in the figure is performed through the SIP/IP core network. It is not intended to limit the invention.
- each network element may send it to the session after receiving the session invitation message.
- the network element that sent the session invitation message returns a response message (100 Trying).
- the established media transmission link between the sender CPM client and the receiver CPM client may be an MSRP protocol link, specifically, for the CPM system in the group.
- the square address the following segmented MSRP media transmission link is established: a first media transmission link between the recipient CPM client and the second participating functional entity; if there are multiple receivables belonging to the second participating functional entity in the group a party address, each recipient CPM client establishes a media transmission link with the second participating functional entity; a second media transmission link between the second participating functional entity and the control functional entity; if there are multiple The second participating functional entity and the control function entity establish a plurality of media transmission links; and the third media transmission link between the control function entity and the first participating functional entity; A fourth media transmission link between the participating functional entity and the sender CPM client.
- the following segmented MSRP media transmission link is established: a first media transmission link between the interworking function entity and the second participating functional entity; a second media transmission link between the second participating functional entity and the control function entity; a third media transmission link between the control function entity and the first participating functional entity; the first participating functional entity and the sender CPM client The fourth media transmission link between.
- the following segmented MSRP media transmission link is established: a first media transmission link between the interworking function entity and the control function entity; between the control function entity and the first participating functional entity a third media transmission link; a fourth media transmission link between the first participating functional entity and the transmitting CPM client.
- Figure 6 does not show the response message from the control function entity to the participating functional entity A session invitation message.
- the control function entity processes the back-to-back user agent (B2BUA) and acts as the temporary conference center during the big message mode session.
- the solution includes the following solutions: Solution 1: After receiving the session invitation message, the control function entity performs group shunting processing on the session invitation message, that is, obtains each receiver address of the group and goes to each group in the group one by one. The receiver sends a session invitation message. On the other hand, the control function entity responds successfully to the receiving session invitation message.
- Solution 2 After receiving the session invitation message, the control function entity performs the offloading process on the session invitation message group, and after receiving the first successful response from the destination domain, responds to the original session invitation message with a successful response.
- Solution 3 After receiving the session invitation message, the control function entity performs the offload processing on the session invitation message group. After receiving all the successful responses from the destination domain, the response response message is successfully responded to the original session invitation message.
- Step S106 After the media transmission link between the sender CPM client and the C-party client (or the interworking function entity) is established, the sender CPM client passes the established media transmission link.
- the message body of the large message mode CPM message (that is, the content of the large message mode CPM message) is sent to the receiver CPM client (or the interworking function entity).
- the processing of this step may be Includes 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 fourth media transmission link, and sends the MSRP SEND block by block according to the MSRP protocol.
- Step 2 The first participating functional entity After receiving the MSRP SEND request, the MSRP SEND request is sent to the control function entity through the third media transmission link; Step 3, the control function entity receives the MSRP SEND, and sends the MSRP SEND request to the second participating functional entity; There are multiple recipient addresses belonging to the second participating functional entity, and the MSRP SEND request is sent one by one.
- the control function entity sends the MSRP SEND request to the interworking function entity according to the established link; Step 4, the second participating function entity passes the first media transmission link
- the MSRP SEND is sent to the receiver CPM client, or if there is a CPM system unreachable user in the group, the second participating function entity sends the MSRP SEND to the interworking function entity through the first media transmission link.
- Step S107 After the sender CPM client sends the content of the large message mode CPM message to the receiver CPM client, a session end process is initiated. Specifically, the session end process may be initiated by the sender CPM client.
- the control function entity may be initiated or initiated by the receiver CPM client or by the interworking function entity, which are described separately below.
- the process of initiating the session by the sender CPM client is the same as the single page.
- the SIP/IP Core node is omitted in the figure. In fact, the signaling transmission between each two functional entities in the figure is performed through the SIP/IP core network. This omission does not constitute a limitation of the invention. Specifically, as shown in FIG. 5 and FIG.
- Step 6 the process of initiating a session by the sender CPM client mainly includes the following steps: Step 1: The sender CPM client sends an indication message indicating that the CPM message session ends, the message Routing to the first participating functional entity via the SIP/IP core network; Step 2, the first participating functional entity receives the indication message of the end of the session, and sends an indication message of the end of the session, the message is routed to the CPM control via the SIP/IP core network Functional entity; Step 3, the CPM control function entity receives the session end indication message, and receives according to the group The party address, one by one, each receiver sends a session end indication message, which is routed through the SIP/IP core network to the second participating functional entity (for the CPM receiver address) or the selected functional entity (for non-CPM recipient addresses).
- Step 4 The second participating functional entity receives the session end indication message, and sends a session end indication message, and the message is routed to the receiver CPM client via the SIP/IP core network; for the unreachable user in the CPM system, the message is routed to the interworking a functional entity;
- Step 5 The receiving CPM client receives the session end indication message, and sends a response message, and the message is routed to the second participating function via the SIP/IP core network;
- Step 6 The second participating functional entity receives and sends the response message, The message message is routed to the CPM control function entity via the SIP/IP core network;
- Step 3 - Step 6 takes a reachable receiver in a CPM system as an example.
- the session end indication message transmission path is CF ⁇ PF ⁇ ISF ⁇ IWF.
- the response path is transmitted in the opposite direction.
- the session end indication message transmission path is CF ⁇ ISF ⁇ IWF.
- the response path is transmitted in the opposite direction.
- the CPM control function entity may reply to the source domain, that is, execute in step 3. This replaces step 7.
- the end of the session is initiated by the receiver CPM client.
- the receiver sends the CPM client to start the session.
- the whole process is opposite to the process of ending the session with the sender CPM client. The difference is that if the receiver that issues the session request is issued
- the client is not the only receiver that is currently participating in the session, that is, there are other recipient clients at this time.
- the control function entity receives the end session request, it does not initiate an end session request to the source end, and the control function entity returns a final session success response to the receiver.
- the receiving end control process entity initiates the session end process control function entity to temporarily assume the role of the conference center, and can initiate a session end process to each member in the group (specifically, the address corresponding to the member) at any time.
- the large message mode CPM message transmission method in the embodiment of the present invention may send a large message mode CPM message to a receiver in the target group.
- the target group includes multiple recipient addresses, which may include the CPM system reachable recipient address, may also include the recipient address that is not reachable by the CPM system, and may also include the non-CPM system receiver address.
- the sender CPM client is CPM Client A
- the effective binding address is CPM Address A
- the first participating functional entity to which the sender belongs is Participating Function A, the target group.
- the CPM client in the CPM system up to the receiver is CPM Client B and CPM Client C
- the binding addresses are CPM Address B and CPM Address C respectively
- the second participating functional entities that can reach the receiver are Participating Function B respectively.
- the CPM control function entity corresponding to the target group is CPM Controlling Function X.
- 1 indicates that the group contains a non-CPM system receiver address, and the address is set to non-CPM Address D, and the corresponding selection function entity and interworking function are Interworking Selection Function-Y1 and Interworking. Function-Yl.
- the group has a CPM system unreachable address CPM Address D, and the corresponding selection function entity and the interworking function are Interworking Selection Function-Y2.
- the session end process is initiated by the CPM client A.
- FIG. 6 is a flowchart of the CPM client A transmitting a large message mode CPM message to the target group in the embodiment, as shown in FIG.
- the CPM client A transmits the large message mode CPM message to the target group mainly includes the following steps: Step 1: The CPM client A sends a session invitation message to a preset group or a temporary group, and the session message is sent through the SIP/IP core network. Route to Participating Function A; Step 2: Participating Function A: The session invitation message is generated and sent a session invitation message, which is routed by the SIP/IP core network to CPM Controlling Function X; Step 3, CPM Controlling Function X receives the session invitation message, According to the receiver address in the group, if the receiver is a temporary group, a session invitation message is sent to each member according to the group member list MIME ⁇ resource-lists> carried in the message body of the session invitation message.
- the group member address is obtained from the document server, such as [OMA-XDM-Shared-Group], and a session invitation message is sent to each member.
- the CPM Controlling Function X sends a session invitation request message to the CPM Address B, the CPM Address C, and the non-CPM Address D, and each request message is separately routed to the Participating Function B via the SIP/IP core network.
- the TCP transport link acts as a large message mode CPM message media transport link.
- Participating Function B sends a success response message, which is via SIP/IP.
- the core network is routed to CPM Controlling Function X.
- Steps 8 through 10 do not have a strict sequence relationship in time. That is, the Participating Function B sends a successful response to the SIP 200 OK and sends the SIPACK without a strict time sequence.
- Step 11 The CPM Controlling Function X receives the success response message, and sends a final confirmation message of the successful response, and the confirmation message is routed to the Participating Function B via the SIP/IP core network; Step 12, the Participating Function B receives the final confirmation message, and then According to the SDP information indication, establish a second media transmission link (which may be a TCP link) with the adjacent MSRP relay point, which is actually a CPM Controlling Function X; the current Party Function B and Controlling Function X There is between
- an existing TCP transmission link can also be selected as the large message mode CPM message media transmission link.
- Step 13 The media transmission link establishment process between the CPM Client C and the Participating Function C and between the Participating Function C and the Controlling Function X is similar to Step 7 - Step 12. No longer.
- Step 13 The CPM Controlling Function X sends a success response message, which is routed to the Participating Function A through the SIP/IP 4 Haixin network;
- Step 14 the Participating Function A owes the above successful response message, and sends a final confirmation message of the successful response.
- the acknowledgment message is routed to the CPM Controlling Function X via the SIP/IP core network;
- Step 15 The CPM Controlling Function X receives the final acknowledgment message, and according to the SDP information indication, establishes an adjacent MSRP relay point, that is, actually The third media transmission link (which can be a TCP link) with the CPM Participating Function A; for the same reason, the existing media transmission link between the Participating Function A and the CPM Controlling Function X can also be selected.
- Step 16 Participating Function A sends a success response message, which is routed to CPM Client A via the SIP/IP core network; Step 17, CPM Client A sends a final confirmation message of successful response, and the confirmation message is routed to the SIP/IP core network to Participating Function A; Step 18: Participating Function A receives the final acknowledgement message, and according to the SDP information indication, establishes a fourth media transmission link with the adjacent MSRP relay point, that is, actually with CPM Client A (may For the TCP link); for the same reason, the existing media transmission link of CPM Client A and Participating Function A can also be selected. This scheme divides the entire signaling path and transmission link into two parts from the CF, that is, the CPM of the source domain.
- the MSRP transmission link on the destination domain side is the interworking function entity Interworking Function-Yl Established with Controlling Function X.
- the MSRP transmission link on the side of the destination domain is between the interworking function Interworking Function-Yl and the Participating Function-D, and between the Participating Function-D and Controlling Function X. Strip link.
- Step 19 For the CPM system reachable user, the CPM Client A passes the fourth media transmission link, and the third media transmission link, the second media transmission link, and the first media transmission link will content of the large message mode CPM message. (CPM Large Message Media) is sent to the receiver CPM Client B and the receiver CPM Client C in a megabyte according to the MSRP ten protocol; for the CPM system unreachable receiver address in the group, on the destination side, along the
- Step 20 CPM Client A sends a session end instruction message SIP BYE, and the message is routed to the Participating Function A via the SIP/IP core network; Step 21, Participating Function A receives the session end instruction message BYE, and sends a BYE, and the BYE message is sent via The SIP/IP core network is routed to the CPM Controlling Function X; Step 22, Controlling Function X sends an indication message indicating the end of the session to each receiver address (CPM address and non-CPM address); Step 22, Controlling Function X sends the BYE success In response to the message, the message is routed to the Participating Function A via the SIP/IP core network; Step 23, the Participating Function A receives the success response message owed by the BYE, and the message is routed to the Client A via the SIP/IP core network; Step 22 - Step 23 An example of a BYE response given by Controlling Function X.
- Step 23 Participating Function B receives the session end indication message SIP BYE, and sends a session end indication message SIP BYE, the message SIP BYE is routed to CPM Client B via the SIP/IP core network; Step 24, CPM Client B receives the session end SIP BYE, and send a BYE success response message SIP 200 OK, the message SIP 200 OK is routed to the Participating Function B via the SIP/IP Core core network; Step 25, Participating Function B receives 4 owed session end success response message SIP 200 OK, and sends End session success response message SIP 200 OK, the message SIP 200 OK is routed to CPM Controlling Function X via the SIP/IP core network; the session end procedure between CPM Controlling Function X and CPM Client C is similar to the above steps.
- a large message mode CPM message transmission system is also provided.
- the system is used to send a large message mode CPM message to the target group.
- a large message mode CPM message transmission system mainly includes: a sender CPM client 1, a source participation function entity 2, a CPM control function entity 3 of a target group, and a destination participation function. Entity 4, Receiver CPM Client 5. a sender CPM client, a session invitation message for sending a large message mode CPM message, where the session invitation message carries a session description protocol SDP session description parameter for negotiation; and is also used for receiving a success response message of the session invitation message.
- SIP 200 OK is also used to establish a media transmission link; and is also used to send a media transmission request MSRP SEND based on the established media transmission link; the source participating functional entity, that is, the participating functional entity to which the sender belongs, for receiving and Sending a session invitation message; also for receiving and transmitting a success response message SIP 200 OK; also for establishing a media transmission link; also for receiving a media transmission request MSRP SEND; and for transmitting a media transmission request to an adjacent MSRP a relay node; a CPM control function entity, configured to receive and send a session invitation message to each receiver address in the target group; and a success response message SIP 200 OK for receiving and transmitting the session invitation message; Transmission link; also used after the MSRP SEND request is received, based on the established media transmission link, for each A recipient address are sent MSRP SEND request.
- the destination end participates in the function entity, that is, the participating function entity that the receiver belongs to, and is used to receive and send the session invitation message; and is also used to receive and send the session response message success response message SIP 200 OK; and is also used to establish a media transmission link; Also used to receive a media transmission request MSRP SEND; also for transmitting a media transmission request to an adjacent MSRP relay node.
- the receiving CPM client is configured to receive the session invitation message; and is used to create and reply to the session response message success response message SIP 200 OK; and is also used to establish a media transmission link; and is further configured to receive the media transmission request MSRP SEND.
- the CPM control function entity When the CPM control function entity receives the session invitation message, it temporarily serves as the conference center; when receiving the session invitation message, if the receiver is a temporary group, the CPM control function entity, according to the message body of the session invitation message The carried group member list obtains the recipient address; if the recipient is a preset group, the CPM control function entity acquires the recipient address from the document server. The recipient address is the CPM system receiver address CPM Adress or the non-CPM system receiver address non-CPMAdress.
- the CPM control function entity When the CPM control function entity receives the session invitation message, it acts as a back-to-back user agent B2BUA. After receiving the SIP 200 OK response, the CPM control function entity attaches the "isfocus" feature parameter to the SIP 200 OK response.
- the CPM Control Function entity Upon receiving the SIP 200 OK response, the CPM Control Function entity sends a SIP ACK Final Ack message. After receiving the SIP ACK, the CPM control function entity determines the neighboring node according to the information provided by the SDP. Hop link. After receiving the BYE request from the sender, the CPM control function entity sends a BYE request for each recipient address in the target group.
- the session invitation message of the large message mode CPM message is used to establish a transmission link between the sender and the reachable receiver of the CPM system in the target group, which is large.
- the content of the message mode CPM message is sent to each receiver 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, thereby improving the user experience.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Multimedia (AREA)
- Business, Economics & Management (AREA)
- General Business, Economics & Management (AREA)
- Telephonic Communication Services (AREA)
Description
向群组发送大消息模式 CPM消息的方法 技术领域 本发明涉及移动通信技术领域 , 尤其涉及一种向群组发送融合 IP消息
( Converged IP Messaging , 筒称为 CPM )的方法, 具体是向群组发送大消息 模式 CPM消息 ( Large Message Mode CPM Message ) 的方法。 背景技术
CPM是开放移动联盟( Open Mobile Architecture ,筒称为 OMA )于 2005 年提出的, 其目的是实现多种消息业务的互通, 提供统一消息业务, 以及完 善一致并且方便的消息业务体验。 CPM融合现有的多种消息业务, 包括即时 消息( Instant Message, 筒称为 IM )、 一键通 ( Push— To— Talk over Cellular, 筒称为 POC )、 移动电子邮件(Mobile E-Email, 筒称为 MEM )、 短消息业务 ( Short Messaging Service, 筒称为 SMS )、 彩信业务 ( Multimedia Messaging Service , 筒称为 MMS ) 等。 目前, OMA正在制定 CPM VI.0规范。 CPM的主体业务形式包括: 基 于寻呼模式 ( page-mode ) 的 CPM 消息、 基于会话模式 ( session-mode ) 的 大消息模式 CPM消息 ( Large Message Mode CPM Message )、基于 session的 其他 CPM会话业务。 在用户正常使用这些业务前, 需要注册登录到 CPM系 统, 即通常所说的 "上线"。 收发双方的 CPM客户端 ( CPM Client ) 与 CPM引擎 ( CPM Enabler ) 之间使用 ( Session Initiation Protocol, 筒称为 SIP ) 消息 ( SIP Message )传 递 page-mode消息。 当发送方终端需要发送一个大消息模式 CPM消息时 , 如果消息的大小超过了限制(例如,大于 1300字节),则不能用 SIP MESSAGE 承载。
CPM业务支持预设群组 ( CPM Pre-defined Group ) 与临时群组 ( CPM Ad-hoc Group ), CPM用户可以向某一个临时群组或者预设群组发送 CPM寻 呼消息, 但当消息大 、超过一定限额时, 则不能用 SIP MESSAGE承载。 在相关技术中,尚未有向某一个临时群组或者预设群组发送大消息模式 CPM消息的解决方案。
发明内容 针对相关技术中现有技术中 CPM客户端无法向群组中的接收方发送大 消息模式 CPM 消息的问题而提出本发明, 为此, 本发明的主要目的在于提 供一种改进的一种向群组发送大消息模式 CPM 消息的方法, 以解决上述问 题至少之一。 根据本发明的一个方面, 提供了一种向群组发送大消息模式融合 IP消 息 CPM消息的方法。 居本发明的向群组发送大消息模式融合 IP消息 CPM消息的方法, 用 于发送方 CPM客户端向目标群组发送大消息模式 CPM消息, 其中, 该方法 包括: 发送方 CPM客户端发送大消息模式 CPM消息会话邀请消息 , CPM控 制功能实体接收到会话邀请消息后, 针对群组的每一个接收方地址, 均发送 会话邀请消息; 接收方 CPM客户端接收会话邀请消息,与控制功能实体进行媒体协商, 控制功能实体与发送方 CPM客户端进行媒体协商 ,确立发送方 CPM客户端 与接收方 CPM客户端之间的媒体传输链路; 和 /或, 互通功能实体接收会话邀请消息, 与控制功能实体进行媒体协商, 控制 功能实体与发送方 CPM客户端进行媒体协商,确立发送方 CPM客户端与控 制功能实体之间的媒体传输链路; 发送方 CPM客户端通过媒体传输链路, 将大消息模式 CPM消息的内 容发送到接收方 CPM客户端和 /或互通功能实体; 发送方 CPM客户端或控制功能实体或接收方 CPM客户端或互通功能 实体发起大消息模式 CPM消息会话结束流程。 才艮据本发明的另一方面, 提供了一种向群组发送大消息模式融合 IP消 息 CPM消息的系统。 居本发明的向群组发送大消息模式融合 IP消息 CPM消息的系统,用 于向目标群组发送大消息模式 CPM消息, 其中, 该系统包括: 发送方 CPM 客户端体和目的端参与功能实体、接收方 CPM客户端、 CPM控制功能实体、
源端参与功能实体, 其中, 发送方 CPM客户端 , 用于发送大消息模式 CPM消息的会话邀请消息 , 其中, 会话邀请消息中携带有进行协商的会话描述协议 SDP会话描述参数; 还用于接收会话邀请消息的成功响应消息 SIP 200 OK; 还用于建立媒体传输 链路; 还用于基于已建立的媒体传输链路发送媒体传输请求 MSRP SEND; 源端参与功能实体, 即发送方归属的参与功能实体, 用于接收并发送会 话邀请消息; 还用于接收并发送成功响应消息 SIP 200 OK; 还用于建立媒体 传输链路; 还用于接收媒体传输请求 MSRP SEND; 还用于将媒体传输请求 发送至相邻的 MSRP中继节点; CPM控制功能实体, 用于接收并对目标群组内每一个接收方地址发送 会话邀请消息;还用于接收并发送会话邀请消息的成功响应消息 SIP 200 OK; 还用于建立媒体传输链路; 还用于在接收到 MSRP SEND请求后, 基于已建 立的媒体传输链路, 对每一个接收方地址均发送 MSRP SEND请求; 目的端参与功能实体, 即接收方归属的参与功能实体, 用于接收并发送 会话邀请消息;还用于接收并发送会话邀请消息的成功响应消息 SIP 200 OK; 还用于建立媒体传输链路; 还用于接收媒体传输请求 MSRP SEND; 还用于 将媒体传输请求发送至相邻的 MSRP中继节点; 接收方 CPM客户端, 用于接收会话邀请消息; 还用于创建并回复会话 邀请消息的成功响应消息 SIP 200 OK; 还用于建立媒体传输链路; 还用于接 收媒体传输请求 MSRP SEND。 进一步地, CPM控制功能实体接收到会话邀请消息时, 临时担任会议 中心。 进一步地 , CPM控制功能实体, 在接收到会话邀请消息时 , 如果接收方是临时群组, CPM控制功能实体, 才艮据会话邀请消息的消 息体中携带的群组成员列表获取接收方地址; 如果接收方是预设群组, CPM控制功能实体, 从文档服务器中获取接 收方地址。 进一步地, 接收方地址为 CPM系统接收方地址 CPM Adress或非 CPM
系统接^:方地址 non-CPMA dress。 进一步地, CPM控制功能实体接收到会话邀请消息时, 作为背靠背用 户代理 B2BUA。 进一步地, CPM控制功能实体当接收到 SIP 200OK响应后, CPM控制 功能实体在 SIP 200OK响应里附力口 "isfocus" 特征参数。 进一步地, 当接收到 SIP 200OK响应后, CPM控制功能实体发送 SIP ACK最终确认消息。 进一步地, CPM控制功能实体当接收到 SIPACK后, 根据 SDP提供的 信息, 确定与相邻节点 hop的链路。 进一步地, 发送方 CPM客户端还用于发送 BYE请求 , CPM控制功能 实体当接收到来自发送方的 BYE请求后, CPM控制功能实体针对目标群组 内的每一个接收方地址均发送 BYE请求。 通过本发明的上述至少一个方案,对于群组内的 CPM系统可达接收方, 通过发送大消息模式 CPM消息的会话邀请消息建立发送方 CPM客户端与目 标群组中的 CPM系统的可达接收方的 CPM客户端之间的媒体传输链路, 将 该大消息模式 CPM消息的内容发送给接收方 CPM客户端。 对于群组内的 CPM系统不可达接收方 ( not-Available CPM Address ) 或群组内的非 CPM用户接收方 ( non-CPM Address ), 一方面 , 通过建立控 制功能实体 ( Controlling Function, 筒称为 CF ) 与发送方客户端之间媒体传 输链路、 控制功能实体与互通功能实体 IWF ( Interworking Function )之间的 媒体传输链路。 基于以上链路可以将大消息模式 CPM 消息从发送方客户端 实时或准实时或非实时发送至互通功能实体。 另一方面, 互通功能实体可以 通过它与非 CPM 系统 ( non-CPM )之间的媒体转换与传输接口将大消息模 式 CPM消息实时或准实时或非实时传送到非 CPM系统中。通过以上两个步 骤, 可以完成发送方到非 non-CPM系统 (和 /或 non-CPM系统用户客户端) 的大消息模式 CPM 消息的传送。 该功能可以根据用户设置和运营商策略进 行启用与否。 通过以上方案, 可以解决现在技术中无法向群组传输大消息模式 CPM 消息的问题, 提高了用户体验。
本发明的其它特征和优点将在随后的说明书中阐述, 并且, 部分地从说 明书中变得显而易见, 或者通过实施本发明而了解。 本发明的目的和其他优 点可通过在所写的说明书、 权利要求书、 以及附图中所特别指出的结构来实 现和获得。 附图说明 附图用来提供对本发明的进一步理解, 并且构成说明书的一部分, 与本 发明的实施例一起用于解释本发明 , 并不构成对本发明的限制。 在附图中: 图 1为本发明实施例, 以群组内一个 CPM系统内可达接收方为例, 大 消息模式 CPM消息向群组发送方法流程图; 图 2为本发明实施例, 以群组内一个 CPM系统内可达接收方为例, 发 送方 CPM客户端与接收方 CPM客户端之间媒体链路建立过程示意图; 图 3为本发明实施例, 以群组内一个 CPM系统内可达接收方为例, 发 送方 CPM客户端向接收方 CPM客户端发送大消息模式 CPM消息的内容的 流程图; 图 4为本发明实施例, 以群组内一个 CPM系统内可达接收方为例, 发 送方 CPM客户端向接收方 CPM客户端发送大消息模式 CPM消息的媒体链 路的分段示意图; 图 5为本发明以群组内一个 CPM系统内可达接收方为实施例的消息流 程图; 图 6为 居本发明实施例的大消息模式 CPM消息向群组传输系统的控 制功能实体对信令及媒体控制的流程图; 图 7为根据本发明实施例的大消息模式 CPM消息向群组传输系统的控 制功能实体的功能示意图。 具体实施方式 功能相克述 由于大消息模式 CPM消息所占的空间较大, 不能直接使用 SIP消息进
行 载 , 与 page-mode模式 CPM消息传送方式不同 , 大消息模式 CPM消息 传送路径分为信令路径和媒体路径, 即信令沿信令路径传送, 媒体沿媒体路 径传送。 因此, 在本发明实施例中, 在传输大消息模式 CPM 消息时, 先使 用大消息模式 CPM消息的会话邀请消息 (INVITE ) 建立发送方 CPM客户 端与接收方 CPM客户端之间的会话 , 完成媒体协商 , 建立发送方 CPM客户 端与接收方 CPM客户端之间的传输链路, 通过建立的传输链路, 使用消息 会话中继协议 ( Message Session Relay Protocol , 筒称为 MSRP ) 向上述接收 方 CPM客户端传送该大消息模式 CPM消息的消息体,即 CPM消息的内容。 大消息模式 CPM消息向群组发送, 群组内可能包含多个接收方地址, 接收方地址可能为 CPM接收方地址( CPM Address ), 也可以为非 CPM接收 方地址( non-CPM Address )。 对于 CPM接收方地址 , 可能为可达 CPM接收 方地址, 也可能是不可达接收方地址。 因此, 本发明的实施例中, 控制功能 实体完成对群组的集中管理和控制, 担任临时会议中心角色, 并按照背靠背 用户代理( B2BUA )原贝' J处理, 同时充当用户代理客户端( User Agent Client, 筒称为 UAC ) 和用户代理服务器 (User Agent Server, 筒称为 UAS ) 两个角 色, 即当接收到请求时, 做为服务器给予响应, 但为了获知给予何种响应, 会产生一个新的请求。 控制功能实体接收到会话邀请消息后, 向群组内的每 一个接收方 ( CPM Address和 non-CPM Address ) 均发送会话邀请消息, 从 而在目的域, 控制功能实体与每一个接收方客户端 (对于 non-CPM Address 或者不可达 CPM用户地址是指互通功能实体) 建立信令和媒体传输路径。 由此, 完成发送方客户端与群组中的每一个接收方客户端之间的大消息模式 CPM消息的传送。 需要说明的是,本发明实施例中所称的大消息模式 CPM消息,为 OMA 制定的 CPM规范中其大小超过预设限制 (比如, 1300个字节) 的 CPM消 息 , 该大消息模式 CPM消息不能直接使用 SIP消息进行承载。 在不冲突的情况下, 本申请中的实施例及实施例中的特征可以相互组 合。 以下结合附图对本发明的优选实施例进行说明 , 应当理解 , 此处所描述 的优选实施例仅用于说明和解释本发明, 并不用于限定本发明。 根据本发明实施例, 首先提供了一种大消息模式 CPM消息传输方法, 该方法用于向目标群组发送大消息模式 CPM消息。
图 1为本发明实施例, 以群组内一个 CPM系统内可达接收方为例, 大 消息模式 CPM消息向群组传输方法的流程图。图 6 大消息模式 CPM消息向 群组发送到一般情况。为筒单起见,该图 1和图 6均省略了 SIP/IP Core节点, 事实上图中每两个功能实体之间的信令传输均通过 SIP/IP核心网进行,本省 略并不构成对本发明的限制。 如图 1和图 6所示, 才艮据本发明实施例的大消 息模式 CPM 消息向群组发送的方法主要包括以下步骤 (步骤 S101 -步骤 S107 ): 步骤 S101 - S104:发送方 CPM客户端向某一个预设群组或者临时群组 发送大消息模式 CPM消息的会话邀请消息, CPM控制功能实体接收会话邀 请消息, CPM控制功能实体通过获取预设群组或者临时群组的接收方地址, 即如果接收方为临时群组, 解析会话邀请消息的消息体中携带的 MIME <resource-lists>获取群组成员列表; 如果接收方预设群组, 从文档服务器 [OMA-XDM-Shared-Group]获取群组成员地址。 CPM控制功能实体逐一向每 个接收方发送会话邀请消息。 最终 , CPM客户端或者互通功能实体接收到会 话邀请消息。 在 S101、 S102、 S103、 S104 步骤中的邀请消息, 邀请消息的 Call-ID 可以不同, S101、 S102、 S103、 S104 步骤中的邀请消息可以不是同一个邀 请消息, 但考虑到筒化描述和并不产生歧义, 本发明某些文字表述中并不特 别强调同一个传输路径上的同一个方法的 SIP消息在不同对话中的消息相无念 引用的差异化, 如无特殊说明, 可才艮据发明的上下文理解。 步骤 S105: 对于群组内 CPM系统可达接收方地址, 接收方 CPM客户 端接收到会话邀请消息 , 与发送方 CPM客户端进行协商 , 确立发送方 CPM 客户端与接收方 CPM客户端之间的媒体传输链路; 或者, 本步骤可以描述 为 ,接收方 CPM客户端接收到会话邀请消息后 ,与控制功能实体( Controlling Function, 筒称为 CF )进行协商, 确立接收方与控制功能实体之间传输链路, 控制功能实体与发送方客户端进行协商, 确立与发送方 CPM客户端之间的 传输链路。 对于群组内的 CPM 系统不可达接收方地址 ( not- Available CPM Address ) 或群组内的非 CPM用户接收方地址 ( non-CPM Address ), 互通功 能实体接收到会话邀请消息, 一方面, 确立控制功能实体与发送方客户端之 间媒体传输链路, 另一方面确立控制功能实体与互通功能实体之间的媒体传 输链路。
步骤 S106: 发送方 CPM客户端通过上述媒体传输链路, 将大消息模式 CPM消息的内容发送到接收方客户端或者 non-CPM系统; 步骤 S107: 发送方 CPM客户端或控制功能实体或接收方 CPM客户端 或者互通功能实体发起大消息模式 CPM消息会话结束流程。 以下进一步描述上述各处理的细节。
(一) 步骤 S101 - S104 为筒单起见, 该图中省略了 SIP/IP Core节点, 事实上图中每两个功能 实体之间的信令传输均通过 SIP/IP核心网进行, 本省略并不构成对本发明的 限制。 在具体实施过程中, 在发送方 CPM客户端将会话邀请消息发送至接 收方 CPM客户端的过程中, 如图 5所示, 每个网元在接收到会话邀请消息 后, 都可以将给向其发送该会话邀请消息的网元返回一个响应消息 ( 100 Trying )。
(二) 步骤 S105 在具体实施过程中, 确立的发送方 CPM客户端与接收方 CPM客户端 之间的媒体传输链路可以为 MSRP协议链路, 具体地, 对于群组内 CPM系 统可达接收方地址 , 建立以下分段 MSRP媒体传输链路: 接收方 CPM客户端与第二参与功能实体之间的第一媒体传输链路; 如 果群组内有多个归属于第二参与功能实体的接收方地址,则每个接收方 CPM 客户端均与第二参与功能实体建立媒体传输链路; 第二参与功能实体与控制功能实体之间的第二媒体传输链路;如果群组 内有多个归属于第二参与功能实体的接收方地址, 则第二参与功能实体与控 制功能实体建立多条媒体传输链路; 控制功能实体与第一参与功能实体之间的第三媒体传输链路; 第一参与功能实体与发送方 CPM客户端之间的第四媒体传输链路。 对于群组内的 CPM系统不可达接收方地址, 建立以下分段 MSRP媒体 传输链路: 互通功能实体与第二参与功能实体之间第一媒体传输链路;
第二参与功能实体与控制功能实体之间的第二媒体传输链路; 控制功能实体与第一参与功能实体之间的第三媒体传输链路; 第一参与功能实体与发送方 CPM客户端之间的第四媒体传输链路。 对于群组内的非 CPM系统接收方地址 , 建立以下分段 MSRP媒体传输 链路: 互通功能实体与控制功能实体之间第一媒体传输链路; 控制功能实体与第一参与功能实体之间的第三媒体传输链路; 第一参与功能实体与发送方 CPM客户端之间的第四媒体传输链路。 图 6中并没绘出控制功能实体对来自源端即参与功能实体 A会话邀请 消息的响应消息, 控制功能实体按照背靠背用户代理 (B2BUA)处理, 在大消 息模式会话期间担任临时会议中心的角色 , 包括以下几种解决方案: 方案一: 控制功能实体接收到会话邀请消息后,一方面对会话邀请消息 进行群组分流处理, 即获取群组每一个接收方地址并逐一向群组内每一个接 收方发送会话邀请消息。 另一方面, 控制功能实体对接收会话邀请消息回成 功响应。 方案二: 控制功能实体接收到会话邀请消息后, 对会话邀请消息群组分 流处理, 当接收到来自目的域的第一个成功响应后, 再针对原会话邀请消息 回复成功响应。 方案三: 控制功能实体接收到会话邀请消息后, 对会话邀请消息群组分 流处理, 当接收到所有的来自目的域的成功响应后, 再针对原会话邀请消息 回复成功响应。
(三) 步骤 S106 在确立了发送方 CPM客户端与接^:方 CPM客户端 (或者互通功能实 体)之间的媒体传输链路后 , 发送方 CPM客户端通过确立的媒体传输链路 , 将大消息模式 CPM消息的消息体(即该大消息模式 CPM消息的内容)发送 到接收方 CPM客户端 (或互通功能实体), 具体地, 如图 3和图 6所示, 该 步骤的处理可以包括以下步骤:
步骤 1 , 发送方 CPM客户端通过上述第四媒体传输链路, 将大消息模 式 CPM 消息的内容发送到第一参与功能实体, 按照 MSRP 协议逐块发送 MSRP SEND; 步骤 2 , 第一参与功能实体接收到 MSRP SEND请求后, 通过第三媒体 传输链路, 将 MSRP SEND请求发送控制功能实体; 步骤 3 , 控制功能实体接收到 MSRP SEND , 将 MSRP SEND请求发送 到第二参与功能实体; 如果群组内有多个归属于第二参与功能实体的接收方 地址, 则逐一发送 MSRP SEND请求。 如果群组内有非 CPM系统的接收方 地址, 则控制功能实体将 MSRP SEND请求按照已建立好的链路发送到互通 功能实体; 步骤 4 , 第二参与功能实体通过第一媒体传输链路将 MSRP SEND发送 到接收方 CPM客户端, 或者, 如果群组内有 CPM系统不可达用户, 则第二 参与功能实体通过第一媒体传输链路将 MSRP SEND发送至互通功能实体。
(四) 步骤 S107 在发送方 CPM客户端将大消息模式 CPM消息的内容发送到上述接收 方 CPM客户端之后, 将发起会话结束流程, 具体地, 会话结束流程可以由 发送方 CPM客户端发起也可以控制功能实体发起也可以由接收方 CPM客户 端发起或者由互通功能实体发起, 以下分别进行描述。 由发送方 CPM客户端发起会话结束流程 为筒单起见, 该图中省略了 SIP/IP Core节点, 事实上图中每两个功能 实体之间的信令传输均通过 SIP/IP核心网进行,本省略并不构成对本发明的 限制。 具体地, 如图 5和图 6所示, 由发送方 CPM客户端发起会话结束流 程主要包括以下步骤: 步骤 1 ,发送方 CPM客户端发送指示大消息模式 CPM消息会话结束的 指示消息, 该消息经由 SIP/IP核心网路由至第一参与功能实体; 步骤 2, 第一参与功能实体接收到会话结束的指示消息, 并发送会话结 束的指示消息, 该消息经由 SIP/IP核心网路由至 CPM控制功能实体; 步骤 3 , CPM控制功能实体接收到会话结束指示消息, 按照群组接收
方地址, 逐一对每一个接收方发送会话结束指示消息, 该消息经过 SIP/IP核 心网路由至第二参与功能实体 (对于 CPM接收方地址) 或者选择功能实体 (对于非 CPM接收方地址)。 步骤 4, 第二参与功能实体接收会话结束指示消息, 发送会话结束指示 消息, 该消息经由 SIP/IP核心网路由至接收方 CPM客户端; 对于 CPM系统 内不可达用户, 该消息被路由至互通功能实体; 步骤 5 , 接收方 CPM客户端接收会话结束指示消息, 发送响应消息, 该消息经由 SIP/IP核心网路由至第二参与功能; 步骤 6 ,第二参与功能实体接收并发送响应消息,该消息消息经由 SIP/IP 核心网路由至 CPM控制功能实体; 步骤 3 -步骤 6以一个 CPM系统内可达接收方为例。 对于 CPM系统内不可达接收方地址,会话结束指示消息传输路径为 CF → PF→ISF→IWF。 响应路径则沿相反方向传输。 对于非 CPM系统接收方地址, 会话结束指示消息传输路径为 CF→ISF →IWF。 响应路径则沿相反方向传输。 步骤 7 , CPM控制功能实体发送响应消息, 该消息经由 SIP/IP核心网 路由至第一参与功能; 对于群组内多个接收方的情况, CPM控制功能实体仅 发送一个结束会话响应消息到源域; 步骤 8 , 第一参与功能实体接收并且发送响应消息, 该消息经由 SIP/IP 核心网路由至发送方 CPM客户端。 以上给出一个会话结束流程的一个实施例, CPM控制功能实体可以接 收到会话结束请求响应后, 即向源域回复响应, 即在步骤 3中执行。 从而替 代步骤 7 。 由接收方 CPM客户端发起会话结束流程 接收方发 CPM客户端起起会话结束流程, 整个过程与发送方 CPM客 户端起起会话结束流程相反, 所不同的是, 如果发出结束会话请求的接收方 客户端不是唯一个当前参与会话的接收方, 即此时具有其他接收方客户端存
在, 则控制功能实体接收到结束会话请求后, 并不向源端发起结束会话请求, 控制功能实体向该接收方返回结束会话成功响应。 由接收方控制功能实体发起会话结束流程 控制功能实体临时担任会议中心角色,可以随时向群组内的每一个成员 (具体是成员对应的地址) 发起会话结束流程。 通过本发明实施例中的上述大消息模式 CPM消息传输方法, 可以向目 标群组中接收方发送大消息模式 CPM 消息。 目标群组中包括多个接收方地 址, 这些接收方中可能包括 CPM系统可达接收方地址、 还可能包括 CPM系 统不可达的接收方地址, 还可能包括非 CPM系统接收方地址。 为进一步理解本发明实施例提供的技术方案的具体实施方式,下面通过 具体实施例进行说明。 在以下的实施例中 ,不失一般性 ,個设发送方 CPM客户端为 CPM Client A, 有效绑定地址为 CPM Address A、 发送方归属的第一参与功能实体为 Participating Function A、 目标群组内的 CPM系统可达接收方的 CPM客户端 为 CPM Client B和 CPM Client C,绑定地址分别为 CPM Address B和 CPM Address C;可达接收方归属的第二参与功能实体分别为 Participating Function B和 Participating Function C; 目标群组对应的 CPM控制功能实体为 CPM Controlling Function X。 在该实施例中, 1设群组内含有一个非 CPM系统接 收方地址, 叚设为地址为 non-CPM Address D , 对应的选择功能实体和互通 功肯 ¾实体为 Interworking Selection Function- Y1和 Interworking Function-Yl。 在该实施例中 , 再^!设群组内含有一个 CPM 系统内不可达地址 CPM Address D,個—设归属 Participating Function D, 对应的选择功能实体和互通功 肯 ¾实体为 Interworking Selection Function- Y2和 Interworking Function- Y2„ 在本实施例中, 由 CPM Client A发起会话结束流程。 图 6为本实施例中 CPM Client A向目标群组传输大消息模式 CPM消息 的流程图, 如图 6所示, CPM Client A向目标群组内传输大消息模式 CPM 消息主要包括以下步骤: 步骤 1 , CPM Client A向某个预设群组或临时群组发送会话邀请消息 , 会话消息经由 SIP/IP核心网路由至 Participating Function A;
步骤 2 , Participating Function A接^:会话邀请消息, 产生并发送会话邀 请消息, 该会话邀请消息由 SIP/IP核心网路由至 CPM Controlling Function X; 步骤 3 , CPM Controlling Function X接收到会话邀请消息, 才艮据群组内 接收方地址, 如果接收方为临时群组, 根据会话邀请消息的消息体中携带的 群组成员列表, MIME <resource-lists>, 向每个成员发送会话邀请消息。 如果接收方预设群组, 从文档服务器, 如 [OMA-XDM-Shared-Group] , 获取 群组成员地址,向每个成员发送会话邀请消息。本实施例中, CPM Controlling Function X 向接 4欠方地址 CPM Address B、 CPM Address C、 non-CPM Address D发送会话邀请请求消息 , 各个请求消息经由 SIP/IP核心网分别路 由至 Participating Function B、 Participating Function C和 Participating Function D以及 Interworking Selection Function-Yl; 步骤 4, Participating Function B接^:会话邀请消息、 产生并且发送会话 邀请消息, 会话消息经由 SIP/IP核心网路由至 CPM Client B; 步骤 5 , Participating Function C接收会话邀请消息、 产生并且发送会话 邀请消息, 会话消息经由 SIP/IP核心网路由至 CPM Client C; 步骤 6 , Interworking Selection Function-Yl接 4欠并发送会话邀请消息 , 该会话消息经由 SIP/IP核心网路由至 Interworking Function-Yl; 步骤 7, CPM Client B接收会话邀请消息, 发送成功响应, 该成功响应 经由 SIP/IP Core B向路由至 Participating Function B; 步骤 8 , Participating Function B接 4欠成功响应消息 , 并发送成功响应的 最终确认消息, 该确认消息经由 SIP/IP Core B路由至 CPM Client B; 步骤 9, CPM Client B接收该最终确认消息, 根据 SDP信息指示, 建立 与相邻的 MSRP中继点 , 即实际为与 Participating Function B之间的第一媒 体传输链路(可以为 TCP链路 ); 如果当前 CPM Client B与 Participating Function B之间存在有 TCP传输 链路 , 则也可以选择一条已有的 TCP传输链路作为大消息模式 CPM消息媒 体传输链路。 步骤 10, Participating Function B发送成功响应消息,该消息经由 SIP/IP
核心网路由至 CPM Controlling Function X。 步骤 8到步骤 10 时间上并没有严格先后时序关系, 即 Participating Function B发送成功响应 SIP 200 OK和发送 SIPACK没有严格的时间次序。 步骤 11 , CPM Controlling Function X接收成功响应消息 , 并发送成功 响应的最终确认消息, 该确认消息经由 SIP/IP 核心网路由至 Participating Function B; 步骤 12, Participating Function B接收该最终确认消息 , 才艮据 SDP信息 指示, 建立与相邻的 MSRP中继点 , 即实际为与 CPM Controlling Function X 之间的第二媒体传输链路(可以为 TCP链路 ); 口果当前 Participating Function B与 Controlling Function X之间存在有
TCP传输链路,则也可以选择一条已有的 TCP传输链路作为大消息模式 CPM 消息媒体传输链路。
CPM Client C与 Participating Function C之间以及 Participating Function C与 Controlling Function X之间的媒体传输链路建立过程与步骤 7 -步骤 12 相似。 不再赘述。 步骤 13 , CPM Controlling Function X发送成功响应消息 , 该消息经由 通过 SIP/IP 4亥心网路由至 Participating Function A; 步骤 14, Participating Function A接 4欠上述成功响应消息, 发送成功响 应的最终确认消息, 该确认消息经由 SIP/IP核心网路由至 CPM Controlling Function X; 步骤 15 , CPM Controlling Function X接收该最终确认消息 , 才艮据 SDP 信息指示, 建立与相邻的 MSRP 中继点, 即实际为与 CPM Participating Function A之间的第三媒体传输链路(可以为 TCP链路); 同理 ,也可以选择 Participating Function A与 CPM Controlling Function X 之间的现有的媒体传输链路。 步骤 11到步骤 15时间上并没有严格先后时序关系 ,即 CPM Controlling Function X发送成功响应 SIP 200 OK和发送 SIP AC 没有严格的时间次序。
步骤 16 , Participating Function A发送成功响应消息,该消息经由 SIP/IP 核心网路由至 CPM Client A; 步骤 17 , CPM Client A发送成功响应的最终确认消息, 该确认消息经 由 SIP/IP核心网路由至 Participating Function A; 步骤 18 , Participating Function A接收最终确认消息 , 才艮据 SDP信息指 示, 建立与相邻的 MSRP中继点, 即实际为与 CPM Client A之间的第四媒体 传输链路(可以为 TCP链路); 同理 , 也可以选择 CPM Client A与 Participating Function A现有的媒体 传输链路。 本方案从 CF将整个信令路径和传输链路分为 2部分, 即源域的 CPM
Client A <->Participating Function A<->Controlling Function X部分和目的域 Controlling Function X<-> Participating Function B<->CPM Client B;和 Controlling Function X<-> Participating Function C<->CPM Client C;和 Controlling Function X<-> Interworking Selection Function- Y 1 <->Interworking Function-Yl ; 对于群组内的非 CPM系统接收地址 , 目的域一侧的 MSRP传输链路为 互通功能实体 Interworking Function-Yl与 Controlling Function X之间建立。 对于群组内的 CPM不可达地址, 目的域一侧的 MSRP传输链路为互通 功肯 ¾实体 Interworking Function-Yl 与 Participating Function -D之间, 以及 Participating Function— D与 Controlling Function X之间的两条链路。 步骤 19 , 对于 CPM系统可达用户 , CPM Client A通过上述第四媒体传 输链路, 第三媒体传输链路、 第二媒体传输链路、 第一媒体传输链路将大消 息模式 CPM消息的内容 ( CPM Large Message Media )按照 MSRP十办议逐兆 发送给接收方 CPM Client B和接收方 CPM Client C; 对于群组内 CPM 系统不可达接收方地址, 则在目的侧, 沿着的
Controlling Function X 与 Participating Function — D 之间以及 Participating Function D与 Interworking Function-Yl之间的传输链路传输,最终^ 1大消息 模式 CPM消息发送至非 CPM系统。 对于群组内的非 CPM 系统接收地址, 目的 i或一侧沿着 Controlling
Function X与 Interworking Function- Yl之间传输链路传输, 最终^ 1大消息模 式 CPM消息发送至非 CPM系统。 步骤 20 , CPM Client A发送会话结束指令消息 SIP BYE , 该消息经由 SIP/IP核心网路由至 Participating Function A; 步骤 21 , Participating Function A接收到会话结束指令消息 BYE , 并发 送 BYE ,该 BYE消息经由 SIP/IP核心网路由至 CPM Controlling Function X; 步骤 22 , Controlling Function X 向每个接收方地址 ( CPM 地址和 non-CPM 地址) 发送会话结束的指示消息; 步骤 22 , Controlling Function X发送 BYE的成功响应消息 , 该消息经 由 SIP/IP核心网路由至 Participating Function A; 步骤 23 , Participating Function A接 4欠 BYE的成功响应消息, 该消息 经由 SIP/IP核心网路由至 Client A; 步骤 22 -步骤 23是由 Controlling Function X给出 BYE响应的例子。 也可以为 Controlling Function X接收到某一个接收方的 BYE成功响应消息之 后 (例如第一个 BYE响应消息) 向源 i或发送 BYE成功响应。 步骤 23 , Participating Function B接收到会话结束指示消息 SIP BYE , 并发送会话结束指示消息 SIP BYE ,该消息 SIP BYE经 SIP/IP核心网路由至 CPM Client B; 步骤 24 , CPM Client B接收会话结束 SIP BYE , 并发送 BYE成功响应 消息 SIP 200 OK , 该消息 SIP 200 OK 经由 SIP/IP Core 核心网路由至 Participating Function B; 步骤 25 , Participating Function B接 4欠会话结束成功响应消息 SIP 200 OK, 并发送结束会话成功响应消息 SIP 200 OK, 该消息 SIP 200 OK经由 SIP/IP核心网路由至 CPM Controlling Function X; 对于 CPM Controlling Function X与 CPM Client C之间的会话结束流程 与上述步骤相似。 根据本发明实施例 , 还提供了一种大消息模式 CPM消息传输系统。 该
系统用于向目标群组发送大消息模式 CPM消息。 如附图所示 , 根据本发明实施例的大消息模式 CPM消息传输系统主要 包括: 发送方 CPM客户端 1、 源端参与功能实体 2、 目标群组的 CPM控制 功能实体 3、 目的端参与功能实体 4、 接收方 CPM客户端 5。 发送方 CPM客 户端, 用于发送大消息模式 CPM 消息的会话邀请消息, 其中, 该会话邀请 消息中携带有进行协商的会话描述协议 SDP会话描述参数;还用于接收会话 邀请消息的成功响应消息 SIP 200 OK; 还用于建立媒体传输链路; 还用于基 于已建立的媒体传输链路发送媒体传输请求 MSRP SEND; 源端参与功能实 体, 即发送方归属的参与功能实体, 用于接收并发送会话邀请消息; 还用于 接收并发送成功响应消息 SIP 200 OK; 还用于建立媒体传输链路; 还用于接 收媒体传输请求 MSRP SEND; 还用于将媒体传输请求发送至相邻的 MSRP 中继节点; CPM控制功能实体, 用于接收并对目标群组内每一个接收方地址 发送会话邀请消息;还用于接收并发送会话邀请消息的成功响应消息 SIP 200 OK; 还用于建立媒体传输链路; 还用于在接收到 MSRP SEND请求后, 基于 已建立的媒体传输链路, 对每一个接收方地址均发送 MSRP SEND请求。 目 的端参与功能实体, 即接收方归属的参与功能实体, 用于接收并发送会话邀 请消息; 还用于接收并发送会话邀请消息的成功响应消息 SIP 200 OK; 还用 于建立媒体传输链路; 还用于接收媒体传输请求 MSRP SEND; 还用于将媒 体传输请求发送至相邻的 MSRP中继节点。 接收方 CPM客户端, 用于接收 会话邀请消息;还用于创建并回复会话邀请消息的成功响应消息 SIP 200 OK; 还用于建立媒体传输链路; 还用于接收媒体传输请求 MSRP SEND。
CPM控制功能实体接收到会话邀请消息时 , 临时担任会议中心; CPM 控制功能实体, 在接收到会话邀请消息时, 如果接收方是临时群组, CPM控 制功能实体, 根据会话邀请消息的消息体中携带的群组成员列表获取接收方 地址; 如果接收方是预设群组, CPM控制功能实体, 从文档服务器中获取接 收方地址。 接收方地址为 CPM系统接收方地址 CPM Adress或非 CPM系统接收方 地址 non-CPMAdress。 CPM控制功能实体接收到会话邀请消息时, 作为背靠 背用户代理 B2BUA。 CPM控制功能实体当接收到 SIP 200OK响应后 , CPM 控制功能实体在 SIP 200OK 响应里附力口 "isfocus" 特征参数。 当接收到 SIP 200OK响应后 , CPM控制功能实体发送 SIP ACK最终确认消息。 CPM控 制功能实体当接收到 SIP ACK后, 根据 SDP提供的信息, 确定与相邻节点
hop的链路。 CPM控制功能实体当接收到来自发送方的 BYE请求后, 针对 目标群组内的每一个接收方地址均发送 BYE请求。 如上所述, 借助本发明实施例提供的技术方案, 通过大消息模式 CPM 消息的会话邀请消息建立发送方与目标群组中的 CPM 系统的可达接收方之 间的传输链路, 将该大消息模式 CPM 消息的内容发送给目标群组的各个接 收方, 可以解决现在技术中无法向群组传输大消息模式 CPM 消息的问题, 提高了用户体验。 以上所述仅为本发明的优选实施例而已, 并不用于限制本发明, 对于本 领域的技术人员来说, 本发明可以有各种更改和变化。 凡在本发明的^^申和 原则之内, 所作的任何修改、 等同替换、 改进等, 均应包含在本发明的保护 范围之内。
Claims
1. 一种向群组发送大消息模式融合 IP消息 CPM消息的方法, 用于发送方 CPM客户端向目标群组发送大消息模式 CPM消息, 其特征在于, 所述 方法包括:
所述发送方 CPM客户端发送大消息模式 CPM消息会话邀请消息 , CPM控制功能实体接收到所述会话邀请消息后,针对所述群组的每一个 接收方地址, 均发送所述会话邀请消息;
接收方 CPM客户端接收所述会话邀请消息 , 与所述控制功能实体 进行媒体协商, 所述控制功能实体与所述发送方 CPM 客户端进行媒体 协商, 确立所述发送方 CPM客户端与所述接收方 CPM客户端之间的媒 体传输链路; 和 /或,
互通功能实体接收所述会话邀请消息 ,与所述控制功能实体进行媒 体协商, 所述控制功能实体与所述发送方 CPM 客户端进行媒体协商, 确立所述发送方 CPM客户端与所述控制功能实体之间的媒体传输链路; 所述发送方 CPM客户端通过所述媒体传输链路, 将所述大消息模 式 CPM消息的内容发送到所述接收方 CPM客户端和 /或互通功能实体; 所述发送方 CPM 客户端或所述控制功能实体或所述接收方 CPM 客户端或互通功能实体发起所述大消息模式 CPM消息会话结束流程。
2. 一种向群组发送大消息模式融合 IP消息 CPM消息的系统, 用于向目标 群组发送大消息模式 CPM消息,其特征在于,该系统包括:发送方 CPM 客户端、 接收方 CPM客户端、 CPM控制功能实体、 源端参与功能实体 和目的端参与功能实体, 其中,
所述发送方 CPM客户端, 用于发送大消息模式 CPM消息的会话 邀请消息, 其中, 所述会话邀请消息中携带有进行协商的会话描述协议 SDP会话描述参数; 还用于接收所述会话邀请消息的成功响应消息 SIP 200 OK; 还用于建立媒体传输链路; 还用于基于已建立的媒体传输链路 发送媒体传输请求 MSRP SEND;
所述源端参与功能实体, 即发送方归属的参与功能实体, 用于接收 并发送所述会话邀请消息;还用于接收并发送所述成功响应消息 SIP 200
OK; 还用于建立媒体传输链路; 还用于接收所述媒体传输请求 MSRP SEND; 还用于将所述媒体传输请求发送至相邻的 MSRP中继节点; 所述 CPM控制功能实体, 用于接收并对目标群组内每一个接收方 地址发送所述会话邀请消息; 还用于接收并发送所述会话邀请消息的成 功响应消息 SIP 200 OK; 还用于建立媒体传输链路; 还用于在接收到所 述 MSRP SEND请求后, 基于已建立的所述媒体传输链路, 对所述每一 个接收方地址均发送 MSRP SEND请求;
所述目的端参与功能实体, 即接收方归属的参与功能实体, 用于接 收并发送所述会话邀请消息; 还用于接收并发送会话邀请消息的所述成 功响应消息 SIP 200 OK; 还用于建立媒体传输链路; 还用于接收所述媒 体传输请求 MSRP SEND; 还用于将所述媒体传输请求发送至相邻的 MSRP中继节点;
所述接收方 CPM客户端, 用于接收所述会话邀请消息; 还用于创 建并回复所述会话邀请消息的成功响应消息 SIP 200 OK; 还用于建立媒 体传输链路; 还用于接收媒体传输请求 MSRP SEND。
3. 根据权利要求 2所述的系统, 其特征在于, 所述 CPM控制功能实体接 收到所述会话邀请消息时 , 临时担任会议中心。
4. 根据权利要求 2所述的系统, 其特征在于, 所述 CPM控制功能实体, 在接收到所述会话邀请消息时 ,
如果接收方是临时群组, 所述 CPM控制功能实体, 才艮据所述会话 邀请消息的消息体中携带的群组成员列表获取所述接收方地址;
如果接收方是预设群组, 所述 CPM控制功能实体, 从文档服务器 中获取所述接收方地址。
5. 根据权利要求 4所述的系统, 其特征在于, 所述接收方地址为 CPM 系 统接收方地址 CPM Adress或非 CPM系统接收方地址 non-CPMAdress。
6. 根据权利要求 2所述的系统, 其特征在于, 所述 CPM控制功能实体接 收到所述会话邀请消息时, 作为背靠背用户代理 B2BUA。
7. 根据权利要求 2所述的系统, 其特征在于, 所述 CPM控制功能实体当 接收到 SIP 200OK响应后 , 所述 CPM控制功能实体在所述 SIP 200OK 响应里附力口 "isfocus" 特征参数。
8. 根据权利要求 2所述的系统, 其特征在于, 当接收到 SIP 200OK响应后, 所述 CPM控制功能实体发送 SIP ACK最终确认消息。
9. 根据权利要求 2所述的系统, 其特征在于, 所述 CPM控制功能实体当 接收到 SIP ACK后,根据 SDP提供的信息,确定与相邻节点 hop的链路。
10. 根据权利要求 2所述的系统, 其特征在于, 所述发送方 CPM客户端还 用于发送 BYE 请求, 所述 CPM 控制功能实体当接收到来自发送方的 BYE请求后 , 所述 CPM控制功能实体针对所述目标群组内的每一个接 收方地址均发送 BYE请求。
Priority Applications (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US13/259,474 US20120042083A1 (en) | 2009-05-05 | 2009-09-01 | Method and system for transmitting a large message mode cpm message to group |
ES09844278T ES2709883T3 (es) | 2009-05-05 | 2009-09-01 | Método y sistema para enviar un mensaje de mensajería IP convergente en modo de mensaje grande a un grupo |
EP09844278.3A EP2429221B1 (en) | 2009-05-05 | 2009-09-01 | Method and system for sending large message mode converged ip messaging message to group |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN2009101390403A CN101883322B (zh) | 2009-05-05 | 2009-05-05 | 向群组发送大消息模式融合ip消息的方法和系统 |
CN200910139040.3 | 2009-05-05 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2010127526A1 true WO2010127526A1 (zh) | 2010-11-11 |
Family
ID=43049937
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CN2009/073671 WO2010127526A1 (zh) | 2009-05-05 | 2009-09-01 | 向群组发送大消息模式cpm消息的方法 |
Country Status (5)
Country | Link |
---|---|
US (1) | US20120042083A1 (zh) |
EP (1) | EP2429221B1 (zh) |
CN (1) | CN101883322B (zh) |
ES (1) | ES2709883T3 (zh) |
WO (1) | WO2010127526A1 (zh) |
Families Citing this family (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN102026112B (zh) * | 2009-09-21 | 2014-07-02 | 中兴通讯股份有限公司 | 一种融合ip消息的发送方法及系统 |
WO2013052964A2 (en) * | 2011-10-07 | 2013-04-11 | Interop Technologies, Llc | Non-ims rich communication suite |
CN106713308B (zh) * | 2016-12-21 | 2020-05-26 | 深圳中兴网信科技有限公司 | 媒体流实时传输的方法和装置 |
CN108234294A (zh) * | 2017-12-29 | 2018-06-29 | 中兴通讯股份有限公司 | 消息传输方法、装置、存储介质及电子装置 |
JP6912729B2 (ja) * | 2018-04-12 | 2021-08-04 | 日本電信電話株式会社 | Sipプロキシサーバ、通信方法およびsipプロキシプログラム |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2008060084A1 (en) * | 2006-11-13 | 2008-05-22 | Samsung Electronics Co., Ltd. | Method and system for establishing session for message communication between converged ip messaging service client and short messaging service client |
CN101212719A (zh) * | 2006-12-31 | 2008-07-02 | 华为技术有限公司 | 一种无线通信网络中实现融合消息业务的方法及系统 |
US20080219283A1 (en) * | 2007-03-06 | 2008-09-11 | Seoul National University Industry Foundation | File transfer method in converged ip messaging system |
Family Cites Families (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7885208B2 (en) * | 2003-09-11 | 2011-02-08 | Nokia Corporation | IP-based services for circuit-switched networks |
FI20040577A0 (fi) * | 2004-04-23 | 2004-04-23 | Nokia Corp | Tiedon toimittaminen tietoliikennejärjestelmän resurssista |
CN101257375B (zh) * | 2006-12-31 | 2012-08-08 | 华为技术有限公司 | 实现多终端的消息同步的方法及装置 |
US20080281971A1 (en) * | 2007-05-07 | 2008-11-13 | Nokia Corporation | Network multimedia communication using multiple devices |
US8099089B2 (en) * | 2008-05-13 | 2012-01-17 | Nokia Corporation | Method, user equipment and software product for media stream transfer between devices |
-
2009
- 2009-05-05 CN CN2009101390403A patent/CN101883322B/zh not_active Expired - Fee Related
- 2009-09-01 ES ES09844278T patent/ES2709883T3/es active Active
- 2009-09-01 EP EP09844278.3A patent/EP2429221B1/en not_active Not-in-force
- 2009-09-01 US US13/259,474 patent/US20120042083A1/en not_active Abandoned
- 2009-09-01 WO PCT/CN2009/073671 patent/WO2010127526A1/zh active Application Filing
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2008060084A1 (en) * | 2006-11-13 | 2008-05-22 | Samsung Electronics Co., Ltd. | Method and system for establishing session for message communication between converged ip messaging service client and short messaging service client |
CN101212719A (zh) * | 2006-12-31 | 2008-07-02 | 华为技术有限公司 | 一种无线通信网络中实现融合消息业务的方法及系统 |
US20080219283A1 (en) * | 2007-03-06 | 2008-09-11 | Seoul National University Industry Foundation | File transfer method in converged ip messaging system |
Non-Patent Citations (2)
Title |
---|
OPEN MOBILE ALLIANCE: "Converged IP Messaging Requirements", OMA-RD-CPM-V1_0-20090310-C, 10 March 2009 (2009-03-10), pages 1 - 74, XP064064785 * |
See also references of EP2429221A4 * |
Also Published As
Publication number | Publication date |
---|---|
EP2429221A4 (en) | 2012-12-26 |
ES2709883T3 (es) | 2019-04-22 |
EP2429221A1 (en) | 2012-03-14 |
CN101883322B (zh) | 2013-01-23 |
CN101883322A (zh) | 2010-11-10 |
US20120042083A1 (en) | 2012-02-16 |
EP2429221B1 (en) | 2018-11-07 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
WO2007016851A1 (fr) | Procede etablissant un canal de transmission de donnees pour dialogue en ligne afin de realiser la transmission du message | |
WO2007033549A1 (fr) | Procede de transmission de message hors ligne | |
CN102123133B (zh) | 不同消息业务平台互通时传送消息回执的方法和消息系统 | |
WO2010127526A1 (zh) | 向群组发送大消息模式cpm消息的方法 | |
US8745145B2 (en) | Method and system for transmitting large message mode CPM messages | |
EP2429256B1 (en) | Method for negotiating message session relay protocol connection parameters | |
KR101436679B1 (ko) | 대형 메시지 모드 통합 아이피 메시지 전송 방법 및 시스템 | |
CN102026112B (zh) | 一种融合ip消息的发送方法及系统 | |
KR101372385B1 (ko) | 대형 메시지 모드 통합 ip 메시지의 전송방법 및 시스템 | |
CN101925023B (zh) | 一种向群组传送大消息模式cpm消息媒体链路创建的方法 | |
KR20100057409A (ko) | 인스턴트 메시지 전송 방법 | |
CN101854599B (zh) | 大融合ip消息传输方法及系统 | |
CN101925033A (zh) | 传送大消息模式cpm消息中实现msrp参数协商的方法及系统 | |
CN101895830A (zh) | 大消息模式融合ip消息传输方法及系统 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 09844278 Country of ref document: EP Kind code of ref document: A1 |
|
WWE | Wipo information: entry into national phase |
Ref document number: 13259474 Country of ref document: US |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2009844278 Country of ref document: EP |