WO2008141562A1 - Procédé et système de réalisation de service de messagerie, et serveur d'application de messagerie - Google Patents

Procédé et système de réalisation de service de messagerie, et serveur d'application de messagerie Download PDF

Info

Publication number
WO2008141562A1
WO2008141562A1 PCT/CN2008/070947 CN2008070947W WO2008141562A1 WO 2008141562 A1 WO2008141562 A1 WO 2008141562A1 CN 2008070947 W CN2008070947 W CN 2008070947W WO 2008141562 A1 WO2008141562 A1 WO 2008141562A1
Authority
WO
WIPO (PCT)
Prior art keywords
message
user
message body
ims domain
calling
Prior art date
Application number
PCT/CN2008/070947
Other languages
English (en)
French (fr)
Inventor
Wei Li
Lei Diao
Yahui Zhang
Lei Shi
Dijin Xie
Weili Huang
Xianqiang Luo
Dongmo Xie
Original Assignee
Huawei Technologies Co., Ltd.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Huawei Technologies Co., Ltd. filed Critical Huawei Technologies Co., Ltd.
Priority to ES08748556T priority Critical patent/ES2395997T3/es
Priority to EP08748556A priority patent/EP2146511B1/en
Publication of WO2008141562A1 publication Critical patent/WO2008141562A1/zh
Priority to US12/342,998 priority patent/US8014775B2/en

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/10—Architectures or entities
    • H04L65/1063—Application servers providing network services
    • 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
    • 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/1069—Session establishment or de-establishment
    • 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/10—Architectures or entities
    • H04L65/1016—IP multimedia subsystem [IMS]

Definitions

  • the present invention relates to the field of multimedia communication technologies, and the technical field of the Internet Protocol Multimedia Subsystem, and in particular, to a multimedia subsystem (IMS, IP Multimedia Subsystem) domain message service implementation method and system, and a message application server.
  • IMS Internet Protocol Multimedia Subsystem
  • IMS IP Multimedia Subsystem
  • MS Message Service
  • IM Instant Message
  • SMS Short Message Service
  • MMS Multi-media Message Service
  • E-mail E-mail
  • the IMS message service has an instant message mode and a store-and-forward message mode, and the two can be divided into a session-based message and a non-session-based message according to different bearer modes; wherein the session-based message is established through a session and established through the session.
  • the connection transport message body; the non-session-based message carries the message body directly in the request message, such as a MESSAGE message.
  • the multimedia subsystem IMS domain message service network reference model is shown in FIG. 1 , wherein the main network entity includes a message application server (MAS) 101, a call session control function entity (CSCF, Call Session Control Function) 102, and a user. Equipment (UE, User Equipment) 103.
  • the message application server 101 is responsible for the processing of the IMS message service; the CSCF 102 is used to provide the session control service, and provides the session control and registration service for the UE; the UE 103 can be a personal computer, a mobile phone, a telephone, or the like.
  • the calling user equipment is represented as UE1
  • the network where the calling user equipment is located is the originating network. All devices marked with 1 in the sending network represent the sending device, and the called user equipment is represented as UE2, called The network where the user is located is the receiving network, and the number in the receiving network is 2 Some devices represent the receiving device.
  • reference numeral 100 denotes a sender network
  • reference numeral 200 denotes a network of 4 squares.
  • a session-based message flow diagram in a IMS domain store-and-forward message in the prior art includes the following steps:
  • UE1 sends an INVITE request to MAS1 through CSCF1.
  • the INVITE request includes a session description of a Session Description Protocol (SDP), and the session description includes media information parameters, so that MAS1 can join the session.
  • SDP Session Description Protocol
  • MAS1 returns a 200 OK response response to UE1 through CSCF1; if MAS1 agrees to join the session, it returns a 200 OK response response, and lists a series of media parameters supported by MAS1 in the 200 OK response response SDP session description.
  • UE1 returns an ACK acknowledgement message to MAS1 through CSCF1, confirming that MAS1 has received the response response 200 OK to the INVITE request.
  • the UE1 transmits a message body to the MAS1 by using a Transmission Control Protocol (TCP) connection established in step 201206.
  • TCP Transmission Control Protocol
  • UE1 initiates a session end request and forwards it to MAS1 through CSCF1;
  • MAS1 returns an end session request response to UE1 through CSCF1;
  • MAS1 sequentially forwards the established INVITE request to MAS2 through CSCF1, CSCF2;
  • MAS2 returns 200 OK response to MAS1 through CSCF2 and CSCF1
  • MAS1 sequentially returns an ACK confirmation to MAS2 through CSCF1, CSCF2, and MAS1 transmits a message body to MAS2 through the TCP connection established in step 212220;
  • MAS2 initiates a session end request and forwards it to MAS1 through CSCF2 and CSCF1 in sequence;
  • MAS1 returns the end session request response and forwards to MAS2 through CSCF1, CSCF2 in turn; 228-229, MAS2 sends an INVITE request to UE2 through CSCF2;
  • MAS2 returns an ACK acknowledgement message to UE2 through CSCF2;
  • MAS2 transmits a message body to UE2 through the TCP connection established in steps 228 ⁇ 233; 235-236, MAS2 sends an end session request to UE2 through CSCF2;
  • UE2 returns an end session request response to MAS2 through CSCF2.
  • UE1 sends the message body to UE2 in a session-based form.
  • the above is a specific implementation process in which the message in the message forwarding mode is transmitted in the form of a session.
  • the 201 211 is a basic process for the calling user to establish a connection with the sending message application server and transmitting the message body to the sending message application server through the established connection;
  • 212-227 is the sending message application server and the receiving message application.
  • 228 238 is the basic for the receiving message application server to establish a connection with the called user and to transfer the message body from the called user to the called user Process. It can be seen that the message body sent by the calling user needs to be forwarded by the sending message application server and the receiving message application server to reach the called user, and the intermediate interaction process is required, and the message body needs to be transmitted for a long time. time.
  • instant messaging The difference between instant messaging and store-and-forward messages is that instant messages exist only for both users, and each instant message is an independent transaction.
  • the implementation of the instant messaging service also needs to be forwarded by the sending message server and the receiving message server to send the message body to the called user.
  • the intermediate interaction process and the long message body transmission time are also required.
  • the embodiment of the invention provides a message service implementation method and a message application server, so as to simplify the IMS domain information interaction process and shorten the message body transmission time.
  • a method for implementing a multimedia subsystem IMS domain message service includes: Receiving a message body sent by the calling user;
  • the embodiment of the invention provides a multimedia subsystem IMS domain message service system, which includes a message application server MAS, a call session control function entity CSCF, and a calling user equipment and a called user equipment.
  • a multimedia subsystem IMS domain message service system which includes a message application server MAS, a call session control function entity CSCF, and a calling user equipment and a called user equipment.
  • the message application server MAS determines, according to the registration information of the calling user and the called user, whether the calling user and the called user belong to the same IMS domain, and sends a message to the user equipment; the call session control function entity CSCF, For forwarding a message between the MAS and the user equipment UE;
  • the message body is directly sent to the called user through the CSCF.
  • the message body sent by the calling user is received and the message body is forwarded to the called user.
  • a user registration information storage unit configured to store user registration information
  • a receiving unit configured to receive a message body sent by the calling user
  • a first determining unit configured to determine whether the calling user and the called user belong to the same IMS domain; when the receiving unit receives the message body sent by the calling user, according to the user registration information stored in the user registration information storage unit Determine whether the calling user and the called user belong to the same IMS domain;
  • a first sending unit when the first determining unit determines that the calling user belongs to the same user as the called user In an IMS domain, the message body sent by the calling user received by the receiving unit is directly sent to the called user.
  • a user registration information storage unit configured to store user registration information
  • a first receiving unit configured to receive a session request for establishing a connection sent by the calling user
  • a second receiving unit configured to receive a message body sent by the calling user
  • a determining unit when the first receiving unit receives the session request for establishing a connection sent by the calling user, determining, according to the user registration information stored in the user registration information storage unit, whether the calling user and the called user belong to the same IMS domain ;
  • a sending unit when the determining unit determines that the calling user and the called user belong to the same IMS domain, forwarding the connection establishment session request to the called user, and receiving the connection by using the connection established by the establishing connection session request The message body sent by the user, and forwards the message body to the called user.
  • the message body since it is determined that the calling and called users are located in the same IMS domain, the message body does not need to be sent to the receiving message application server for forwarding, but directly interacts with the called user. Sending the message body directly to the called user reduces the interaction process and shortens the message body transmission time.
  • Figure 1 shows the IMS domain messaging service network reference model
  • FIG. 2 is a flow chart of implementing a session-based message service in a storage and forwarding message service in the prior art
  • FIG. 3 is a signaling flow chart of an IMS domain message service implementation method according to an embodiment of the present invention
  • FIG. 4 is another IMS domain according to an embodiment of the present invention.
  • FIG. 5 is a schematic flowchart of a method for implementing an IMS domain message service according to an embodiment of the present invention
  • FIG. 6 is a schematic structural diagram of a message application server according to an embodiment of the present invention;
  • FIG. 7 is a schematic structural diagram of another message application server according to an embodiment of the present invention.
  • FIG. 8 is a schematic structural diagram of another message application server according to an embodiment of the present invention. detailed description
  • the calling user equipment is represented as UE1
  • the network where the calling user equipment is located is the originating network. All devices marked with 1 in the sending network represent the sending device and the called user equipment.
  • the network where the called user equipment is located is the receiving network, and all devices marked with 2 in the receiving network represent the receiving device.
  • reference numeral 100 denotes a sender network
  • reference numeral 200 denotes a 4-square network.
  • the message application server MAS1 can directly send the information to the UE2 according to the locally stored registration information of the called user.
  • the following is an example of the non-session-based message transmission process in the instant message. Description. Referring to FIG. 3, it is a signaling flowchart of an implementation method of an IMS domain message service in an embodiment of the present invention, and the specific steps are as follows:
  • the UE1 sends a MESSAGE message to the call session control function entity CSCF1.
  • the Session Initiation Protocol (SIP) implements an instant message mechanism by using a MESSAGE message, and carries the address of the calling and called users and the message content in the message header field.
  • SIP Session Initiation Protocol
  • the form of the address is usually "im: user (3 ⁇ 4domain" 0 carries the content of the instant message in its request message body.
  • the content filled in the message body can be text, and can also contain multimedia clips, such as sounds and pictures.
  • the sending and receiving of instant messages is a separate process, and there is no necessary contextual connection with the processing of other messages.
  • CSCF1 forwards the MESSAGE message to MAS1;
  • CSCF1 triggers the message to MAS1 according to the service triggering principle.
  • MAS1 determines whether the primary and the called user belong to the same IMS domain according to the user registration information, when the primary and the called user belong to the same IMS domain, step 304 is performed;
  • Each MAS stores the registration information of the user in the IMS domain.
  • the MAS1 searches for the registration information of the user stored in the IMS domain. If the registration information of the called user is found, the primary and the called user belong to the same IMS domain.
  • the primary and called users do not belong to the same IMS domain, for example, they do not belong to the same service carrier.
  • MAS1 cannot find the registration information of the called user, the message is forwarded to UE2 through CSCF2 and MAS2 according to the prior art, and will not be described in detail.
  • MAS1 forwards the MESSAGE message to UE2 through CSCF1;
  • the MAS1 carries the message that the calling and called users are in the same domain in the message sent to CSCF1. According to the information, the CSCF1 judges that if the calling and called users belong to the same IMS domain, the CSCF1 directly routes the MESSAGE message to the UE2; if the primary and the called user do not belong to the same IMS domain, the CSCF1 routes the MESSAGE message first.
  • the IMS domain to which the called user belongs is forwarded to the MAS2 through the CSCF2 in the receiving network, and then the MAS2 sends the message to the UE2 through the CSCF2, that is, the flow shown in the prior art solution.
  • UE2 returns a 200 OK response to UE1 through MAS1, CSCF1 after receiving the MESSGE message.
  • UE1 When UE1 receives a 200 OK response, it indicates that the message was sent successfully.
  • the message does not need to be sent to the UE2 through the CSCF2 and the MAS2 of the receiving network, but directly The message is sent to UE2, thus avoiding multiple forwarding of the message, saving the interaction process and message transmission time.
  • Instant messages can also be session-based messages that can be established through INVITE requests.
  • UE1 needs to send an INVITE request and forward it to MAS1 through CSCF1 in the sending network.
  • MAS1 judges the main according to the user registration information. If the called user belongs to the same IMS domain, if it belongs, MAS1 sends an INVITE request and forwards it to UE2 through CSCF1. After UE2 returns a 200 OK response to UE1 according to the path requested by INVITE, UE1 requests the connection established with UE2 through INVITE.
  • the message body is forwarded to the MAS1 through the CSCF1, and the MAS1 sends the message body to the UE2 through the CSCF1, thereby avoiding the forwarding of the CSCF2 and the MAS2, thereby saving the interaction process and the message body transmission time.
  • the implementation of the store-and-forward message service is different from the instant message transmission process.
  • the message body is received by the MAS1, the message body is not directly sent out, but the message body is temporarily saved and then sent to the UE2.
  • the following describes the implementation process of the session-based message service in the store-and-forward message when the calling and called users belong to the same IMS domain.
  • FIG. 4 it is a flow chart of a signaling process for implementing an IMS domain message service according to an embodiment of the present invention. The specific steps are as follows:
  • UE1 sends an INVITE request and forwards it to MAS1 through CSCF1;
  • the UE1 initiates an INVITE request, which provides sufficient information to enable the called user to Participate in the session, including the type and format of the message body, and the called user address and port information.
  • the message body is text, voice or video, and the corresponding format.
  • the INVITE request is sent to CSCF1, which triggers the request to MAS1 according to the service triggering principle.
  • MAS 1 returns a 200 OK response after receiving the INVITE request and forwards to UE1 through CSCF1;
  • MAS1 receives the request and returns a 200 OK response to UE1 via CSCF1.
  • UE1 returns an ACK acknowledgement message after receiving the 200 OK response and forwards it to MAS1 through CSCF1;
  • CSCF1 Since CSCF1 adds a routing field to the INVITE request message, an ACK acknowledgement message is sent to MAS1 along the request path of the INVITE.
  • UE1 establishes a connection with MAS1, and UE1 can directly transmit the message body to MAS1 through the connection.
  • UE1 transmits a message body to MAS1 by using the connection established in step 401 406.
  • MAS1 initiates a termination session request BYE and forwards to UE1 through CSCF1; 410 411, UE1 returns an end session request response and forwards to MAS1 through CSCF1; the session end request may also be initiated by UE1, when either party wants to end the session When a BYE request is sent directly to the other party, the other party will send back a 200 OK response, so that the two sessions end.
  • MAS1 determines whether the primary and the called user belong to the same IMS domain, when the primary called user belongs to the same IMS domain, step 413;
  • MAS1 only stores the user registration information in the sender network. MAS1 can judge according to the locally saved user registration information. If the registration information of the called user can be found, the calling party and the called user belong to the same IMS network, that is, Belong to the same IMS domain.
  • the message body is executed according to the message body transmission process in the prior art. For details, refer to steps 213 to 238 shown in FIG.
  • MAS1 sends an INVITE request and forwards it to UE2 through CSCF1;
  • MAS1 carries the information about whether the calling and called users are in the same domain in the INVITE request sent to CSCF1. CSCF1 judges according to the information. If the calling and called users belong to the same IMS domain, CSCF1 directly forwards the INVITE request to UE2; if the calling party is not In the same IMS domain, CSCF1 forwards the INVITE request to the IMS domain to which the called user belongs, that is, forwards it to MAS2 through CSCF2 in the receiver network, and then MAS2 sends the INVITE request to UE2 through CSCF2, that is, the prior art solution. The process shown.
  • UE2 returns a 200 OK response after receiving the INVITE request and forwards to MAS 1 through CSCF1;
  • MAS1 returns an ACK acknowledgement and forwards to UE2 through CSCF1;
  • Step 413 418 is similar to step 401 406 in that a new connection is established by initiating a session request and will not be described in detail.
  • the MAS1 transmits the message body to the UE2 by using the connection established in step 413 418.
  • UE2 initiates the end session request BYE and forwards it to MAS1 through CSCF1.
  • MAS1 and MAS2 are not required to negotiate to establish a new session connection, message The body does not need to be forwarded through MAS2 and CSCF2 in the receiving network, which can save a lot of information exchange process and message body transmission time.
  • the transmitted message body is large, it may take a long time to complete the transmission, and reducing the one-time forwarding of the message body can save more message body transmission time.
  • MSRP Message Session Relay Protocol
  • TCP Transmission Control Protocol
  • SCTP Simple Control Transmission Protocol
  • TLS Transport Layer Security
  • MSRP does not limit the size of the message body.
  • Another feature of MSRP is that it works at the media level, so it does not traverse SIP proxy servers such as CSCF, such as CSCF, so that SIP proxy servers are not subject to a large amount of instant messaging. Therefore, the message body of the MSRP message is generally large, so the required transmission time is also long.
  • the MSRP message does not need to be forwarded again by the MAS2, so that more message transmission time can be saved.
  • the non-session-based message in the store-and-forward message is different from the MESSGE message in the instant message.
  • the MAS1 receives the MESSAGE message sent by the UE1 through the CSCF1, the MAS1 returns a 200 OK response to the UE1 through the CSCF1.
  • the message was sent successfully.
  • the MAS1 further determines whether the primary and the called user belong to the same IMS domain according to the user registration information. If the message belongs to the same domain, the MESSAGE message is sent and forwarded to the UE2 through the CSCF1. After the message is successfully sent, the UE2 returns a 200 OK response to the MAS1 through the CSCF1.
  • the MESSAGE message does not need to be forwarded through the MAS2 and CSCF2 in the receiving network, so that a large amount of information interaction process and message body transmission time can be saved.
  • the UE1 sends the message body to the MAS1 and is the same as steps 401 to 411 in the embodiment shown in FIG. 4, MAS2
  • the specific process of transmitting the message body to the UE2 is the same as the steps 228-238 in the prior art, and will not be described in detail. The following is only the MAS1. After receiving the message body to the message needs to be sent MAS2 body prior to the process described in detail UE2.
  • FIG. 5 is a partial signaling flow diagram of an IMS domain message service implementation method according to an embodiment of the present invention. the specific steps are as follows:
  • MAS1 determines whether the primary and the called user belong to the same IMS domain, when the primary and the called user do not belong to the same IMS domain, step 502;
  • MAS1 sends an INVITE request and forwards it to MAS2 through CSCF1 and CSCF2 in sequence;
  • MAS2 returns a 200 OK response and forwards to MAS1 through CSCF2 and CSCF1 in sequence; 508-510, MAS1 returns an ACK acknowledgment and forwards it to MAS2 through CSCF1 and CSCF2 in sequence;
  • MAS1 determines whether the sender network and the receiver network store the message body on the same physical node, when the sender network and the receiver network store the message body on the same physical node, step 512 is performed;
  • the MAS1 can be judged by storing the IP address or physical address of the message body in the receiving network carried in the message, or a special flag can be set to distinguish whether the message body is stored in the same physical node as the receiving network. For example, the MAS of the primary and the called user is the same physical node, and the MSRP message is saved. The MAS1 can determine the IP address of the MAS2 carried in the message. If the IP address of the MAS2 is the same as the IP address of the MAS1, the sender is sent. The network shares the same MAS with the receiving network, and the MSRP messages are also stored on the MAS.
  • MAS1 sends a message to MAS2 through the connection established by step 502 510; because MAS1 does not need to transmit a specific MSRP message body to MAS2 in this step, but only sends a message notification to tell MAS2 to store the specific physical address of the message body, or Tells the MAS2 message body that it has been sent, although it has not actually been sent. Since the message notification is small and the required transmission time is short, the message body transmission time can be reduced.
  • MAS1 initiates a session request BYE and forwards it to MAS2 through CSCF1 and CSCF2 in sequence;
  • MAS2 When MAS2 needs to send the message body to UE2, MAS2 initiates an INVITE request and forwards it to UE2 through CSCF2. When MAS2 returns an ACK response, the connection is established, and MAS2 transmits the message body to UE2.
  • the specific procedure is the same as step 228 in the prior art. 238 is the same and will not be described in detail.
  • MAS2 returns the end session request response 200 OK and is forwarded to MAS1 through CSCF2 and CSCF1 in sequence.
  • the sender network and the receiver network store the message body on the same physical node, for example, all are stored in the same MAS.
  • MAS1 receives the MSRP message sent by UE1, it is judged It is known that the called party also belongs to the sender network, that is, the calling party and the called party belong to the same IMS domain, and the sender network and the receiver network have the same MAS, and the message body can be directly sent to the called user.
  • the sender network and the receiver network store the message body on the same physical node, that is, the message body is sent by the MAS2 to the UE2, since the sender network and the receiver network have the same MAS, that is, the MAS1 is sent to the UE2. Therefore, when the calling party and the called party belong to the same domain, the sender network and the receiver network store the message body in the same physical node, and the message transmission process belongs to the same domain as the calling party and the called party, but the sender network and the receiver party The network also saves the message body in the same physical node.
  • the MAS1 determines that the calling party and the called party belong to the same IMS domain, it is not necessary to determine whether the sender network and the receiver network keep the message body in the same state. On the physical node, to reduce the processing flow and save the message body transmission time.
  • the above embodiments illustrate the message service implementation method.
  • the message application server provided by the embodiment of the present invention is specifically described below.
  • FIG. 6 is a schematic structural diagram of a message application server according to an embodiment of the present invention, where the message application server includes:
  • a user registration information storage unit 61 configured to store user registration information
  • the receiving unit 62 is configured to receive a message body sent by the calling user.
  • the first determining unit 63 is configured to determine, according to the user registration information stored in the user registration information storage unit 61, whether the primary and the called user belong to the same IMS domain when the receiving unit 62 receives the message body sent by the calling user.
  • the first sending unit 64 is configured to: when the first determining unit 63 finds that the calling and called users belong to the same IMS domain, send the message body sent by the calling user received by the receiving unit 62 to the called user.
  • the message application server does not indiscriminately forward all the messages sent by the calling user to the receiving network where the called user is located, and then forwards the message body, and pre-determines whether the calling party and the called user are pre-determined. If they belong to the same IMS domain, if the sender network belongs to the same IMS domain, the sender network can directly interact with the called user. Therefore, the message body can be directly sent to the called user through the sender network where the calling user is located. Therefore, the message application server can reduce the forwarding of the message body once when the calling and called users belong to the same IMS domain, thereby reducing the amount of information exchange process and message body transmission time. If the message application server is configured to process the message service in the store-and-forward mode, for example, the transmitted message body is carried by the MSRP message, the message application server described in this embodiment may be further improved, and the following is performed as another embodiment. A detailed description.
  • FIG. 7 is a schematic structural diagram of a message application server according to an embodiment of the present invention. It can be seen that the message application server further includes a second determining unit 71 and a second sending unit 72, which are different from the embodiment shown in FIG. , among them:
  • the second determining unit 71 is configured to: when the first determining unit 63 determines that the calling and called users do not belong to the same IMS domain, determine whether the sending network and the receiving network save the message body on the same physical node;
  • the second sending unit 72 is configured to notify the receiving network that the message body has been sent when the second determining unit 71 determines that the sending network and the receiving network save the message body on the same physical node.
  • the message server does not need to send the message body to the called network, but notifies the receiving The square network, because the message notification is small, the transmission time is very short, and the store-and-forward message itself is generally large, requires a long transmission time, and also wastes bandwidth resources. Therefore, the message application server can reduce the message interaction and processing flow, and save the message body transmission time.
  • the embodiment of the present invention may further provide another message application server, which is configured to receive a session-based message in an instant message.
  • FIG. 8 is a schematic diagram of a structure of a message application server according to an embodiment of the present disclosure, where the message application server includes:
  • a user registration information storage unit 81 configured to store user registration information
  • the first receiving unit 82 is configured to receive a connection establishment session request sent by the calling user
  • the second receiving unit 83 is configured to receive a message body sent by the calling user.
  • the determining unit 84 is configured to determine, according to the user registration information stored in the user registration information storage unit 81, whether the primary and the called users belong to the same one when the first receiving unit 82 receives the session request for establishing a connection sent by the calling user. IMS domain;
  • the sending unit 85 is configured to, when the determining unit 84 finds that the calling and called users belong to the same IMS domain, send a connection establishment session request to the called user, and receive the second receiving unit 83 by the established connection.
  • the message body sent by the user is sent to the called user.
  • the message server determines whether the calling party and the called user belong to the same IMS domain when receiving the request for establishing a connection session sent by the user, instead of waiting for the message body to be received. Then judge.
  • this embodiment does not need to send the message body to the receiving network where the called user is located, and then forwards the same.
  • the embodiment is the same as the embodiment shown in FIG.
  • the message application server can also reduce the information exchange process and save the message body transmission time.
  • the sender message application server determines that the calling party and the called user are located in the same IMS domain, the message body does not need to be sent to the receiver network and then forwarded, but the information is directly exchanged with the called user, and the message body is directly sent. To the called user, thereby reducing the information exchange process and the transmission time of the message body.
  • the sender network and the receiver network store the message body on the same physical node, since the sender network does not need to forward the message body but only informs the receiver network, the transmission time can be reduced, especially when When the message body is large.

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)
  • Mobile Radio Communication Systems (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Description

消息业务实现方法和系统以及消息应用服务器 本申请要求于 2007 年 05 月 17 日提交中国专利局、 申请号为 200710107045.9、发明名称为"消息业务实现方法和消息应用服务器"的中国 专利申请的优先权， 其全部内容通过引用结合在本申请中。 技术领域
本发明涉及多媒体通信技术领域， 网际协议多媒体子系统技术领域， 尤其涉及多媒体子系统 (IMS, IP Multimedia Subsystem)域消息业务实现方法 和系统以及消息应用服务器。 背景技术
消息业务 (MS, Message Service)是目前移动通信中市场较广阔的数字业 务之一， 可从一个实体向另一个实体发送消息。 消息的传递方式包括即时 消息 (IM, Instant Message)、 短消息业务 (SMS, Short Message Service), 多媒 体消息业务 (MMS, Multi-media Message Service), 电子邮件 (E-mail)等。 随着 通信技术的发展， 尤其是 IMS域的出现， 消息业务所提供的内容也日益丰 富， 例如消息体可以是文本、 图片、 音频、 视频、 游戏等。 IMS 消息业务 有即时消息模式和存储转发消息模式， 二者根据承载方式的不同又可分为 基于会话的消息和非基于会话的消息； 其中， 基于会话的消息是通过会话 建立连接并通过建立的连接传输消息体； 而非基于会话的消息则是在请求 消息中直接携带有消息体， 如 MESSAGE消息。
多媒体子系统 IMS域消息业务网络参考模型如图 1所示， 其中的主要 网络实体有消息应用服务器 (MAS, Message Application Server)101 , 呼叫会 话控制功能实体 (CSCF, Call Session Control Function)102以及用户设备 (UE, User Equipment)103。 消息应用服务器 101 负责 IMS 消息业务的处理； CSCF102用于提供会话控制服务，为 UE提供会话控制和注册服务； UE103 , 可以是个人电脑 、 手机、 电话等。
为描述方便， 将主叫用户设备表示为 UE1 , 主叫用户设备所在网络为 发方网络， 发方网络中标号为 1 的所有设备均表示发方设备， 被叫用户设 备表示为 UE2, 被叫用户所在网络为收方网络， 收方网络中标号为 2的所 有设备均表示收方设备。 图 1 中， 标号 100表示发方网络， 标号 200表示 4丈方网络。
参照图 2, 为现有技术中 IMS域存储转发消息中基于会话的消息流程 图， 具体包括以下步骤：
201 202、 UE1通过 CSCF1向 MAS1发送 INVITE请求；
该 INVITE 请求中包含一个会话描述协议 (SDP, Session Description Protocol)的会话描述，会话描述中包含媒体信息参数， 以便 MAS1能够加入 该会话。
203-204, MAS1通过 CSCF1向 UE1返回 200 OK应答响应； 如果 MAS1同意加入会话， 则返回 200 OK应答响应， 同时在 200 OK 应答响应 SDP会话描述中列出 MAS1支持的一系列媒体参数。
205-206, UE1通过 CSCF1向 MAS1返回 ACK确认消息，证实已收到 MAS1对 INVITE请求的应答响应 200 OK。
207、 UE1通过步骤 201 206所建立的传输控制协议 (TCP, Transmission Control Protocol,)连接向 MAS1传送消息体；
208 209、 UE1发起会话结束请求并通过 CSCF1转发到 MAS1 ;
210-211 , MAS1通过 CSCF1向 UE1返回结束会话请求应答；
212-214, MAS1依次通过 CSCF1、 CSCF2将建立连接的 INVITE请求 转发至 MAS2;
215-217, MAS2依次通过 CSCF2、 CSCF1向 MAS1返回 200 OK应答
218-220, MAS1依次通过 CSCF1、 CSCF2向 MAS2返回 ACK确认消 221、 MAS1通过步骤 212 220所建立的 TCP连接向 MAS2传送消息 体;
222-224, MAS2发起会话结束请求并依次通过 CSCF2、 CSCF1转发到 MAS1;
225-227 , MAS1 返回结束会话请求应答并依次通过 CSCF1、 CSCF2 转发到 MAS2; 228-229, MAS2通过 CSCF2向 UE2发送 INVITE请求；
232-233、 MAS2通过 CSCF2向 UE2返回 ACK确认消息；
234、 MAS2通过步骤 228~233所建立的 TCP连接向 UE2传送消息体； 235-236, MAS2通过 CSCF2向 UE2发送结束会话请求；
237-238, UE2通过 CSCF2向 MAS2返回结束会话请求应答。
通过以上步骤 UE1将消息体通过基于会话的形式发送到 UE2。
以上为存储转发模式的消息业务中消息以基于会话是形式传送的具体 实现流程。 其中， 201 211为主叫用户与发方消息应用服务器协商建立连接 并通过建立的连接将消息体传送到发方消息应用服务器的基本流程； 212-227 为发方消息应用服务器与收方消息应用服务器建立连接并将消息 体从发方消息应用服务器传送到收方消息应用服务器的基本流程； 228 238 为收方消息应用服务器与被叫用户建立连接并将消息体从传送到被叫用户 的基本流程。 可见， 主叫用户发送的消息体需要经过发方消息应用服务器 以及收方消息应用服务器的转发才能到达被叫用户， 中间需要经过复杂的 交互流程， 消息体到达被叫用户也需要较长的传输时间。
即时消息与存储转发消息的不同之处在于， 即时消息仅存在于双方用 户处， 且每条即时消息都是一个独立的事务。 但即时消息业务的实现也需 要通过发方消息服务器与收方消息服务器的转发才能将消息体发送到被叫 用户， 中间也需要经过复杂的交互流程以及较长的消息体传输时间。
在进行本发明创造过程中， 发明人发现不论是实现即时消息业务还是 存储转发消息业务的技术方案， 无论什么场景， 主叫用户发送的消息体都 需要经过发方消息应用服务器和收方消息应用服务器转发， 经多次交互后 才能到达被叫用户， 流程极其复杂， 且花费了较长的消息体传输时间。 发明内容
本发明实施例提供消息业务实现方法和消息应用服务器， 以简化 IMS 域信息交互流程和缩短消息体传输时间。
本发明实施例提供的一种多媒体子系统 IMS域消息业务实现方法， 包 括： 接收主叫用户发送的消息体；
根据用户注册信息判断主叫用户与被叫用户是否属于同一个 IMS域； 当所述主叫用户与被叫用户属于同一个多媒体子系统 IMS域时， 将所 述消息体直接发送给被叫用户。
本发明实施例提供一种多媒体子系统 IMS域消息业务系统， 包括消息 应用服务器 MAS、 呼叫会话控制功能实体 CSCF以及主叫用户设备和被叫 用户设备，
所述消息应用服务器 MAS, 根据主叫用户和被叫用户的注册信息， 判 断主叫用户与被叫用户是否属于同一个 IMS域，以及发送消息给用户设备； 所述呼叫会话控制功能实体 CSCF, 用于在 MAS与用户设备 UE之间 转发消息；
当所述 MAS 判定主叫用户与被叫用户属于同一个多媒体子系统 IMS 域时， 通过所述 CSCF将所述消息体直接发送给被叫用户。
本发明实施例提供的另一种多媒体子系统 IMS域消息业务实现方法， 包括：
接收主叫用户发送的建立连接会话请求；
根据用户注册信息判断主叫用户与被叫用户是否属于同一个 IMS域； 当主叫用户与被叫用户属于同一个 IMS域时， 向被叫用户转发所述建 立连接会话请求；
通过所述建立连接会话请求建立的连接， 接收主叫用户发送的消息体 并将所述消息体转发到所述被叫用户。
本发明实施例提供的一种消息应用服务器， 包括：
用户注册信息存储单元， 用于存储用户注册信息；
接收单元， 用于接收主叫用户发送的消息体；
第一判断单元，用于判断主叫用户与被叫用户是否属于同一个 IMS域； 当所述接收单元接收到主叫用户发送的消息体时， 根据用户注册信息存储 单元中存储的用户注册信息判断主叫用户与被叫用户是否属于同一个 IMS 域；
第一发送单元， 当所述第一判断单元判定主叫用户与被叫用户属于同 一个 IMS域时， 将所述接收单元接收到的主叫用户发送的消息体直接发送 给被叫用户。
本发明实施例提供的另一种消息应用服务器， 包括：
用户注册信息存储单元， 用于存储用户注册信息；
第一接收单元， 用于接收主叫用户发送的建立连接的会话请求； 第二接收单元， 用于接收主叫用户发送的消息体；
判断单元， 当所述第一接收单元接收到主叫用户发送的建立连接的会 话请求时， 根据用户注册信息存储单元中存储的用户注册信息判断主叫用 户与被叫用户是否属于同一个 IMS域；
发送单元， 当所述判断单元判定主叫用户与被叫用户属于同一个 IMS 域时， 向被叫用户转发所述建立连接会话请求， 并通过所述建立连接会话 请求建立的连接， 接收主叫用户发送的消息体， 并将所述消息体转发到所 述被叫用户。
从以上技术方案可以看出，由于当判断得知主被叫用户位于同一个 IMS 域时， 不需要将消息体发送到收方消息应用服务器再转发， 而是直接与被 叫用户进行信息交互， 将消息体直接发送到被叫用户， 从而减少了交互流 程， 缩短了消息体传输时间。 附图说明
图 1为 IMS域消息业务网络参考模型；
图 2为现有技术存储转发消息业务中基于会话的消息业务实现流程图； 图 3为一个本发明实施例 IMS域消息业务实现方法信令流程图； 图 4为另一个本发明实施例 IMS域消息业务实现方法信令流程图； 图 5为本发明实施例 IMS域消息业务实现方法部分信令流程图； 图 6为一个本发明实施例消息应用服务器结构示意图；
图 7为另一个本发明实施例消息应用服务器结构示意图；
图 8为另一个本发明实施例消息应用服务器结构示意图。 具体实施方式
为使本发明实施例的目的、 技术方案及优点更加清楚明白， 以下参照 附图， 对本发明实施例进一步详细说明。 在以下举例说明中， 为描述方便， 将主叫用户设备表示为 UE1 , 主叫 用户设备所在网络为发方网络， 发方网络中标号为 1 的所有设备均表示发 方设备， 被叫用户设备表示为 UE2 , 被叫用户设备所在网络为收方网络， 收方网络中标号为 2的所有设备均表示收方设备。 仍参照图 1所示的 IMS 域消息业务网络参考模型， 其中， 标号 100表示发方网络， 标号 200表示 4丈方网络。
当主被叫用户属于同一个 IMS域时， 消息应用服务器 MAS1可以根据 本地保存的被叫用户的注册信息将信息直接发送到 UE2 , 以下以即时消息 中非基于会话的消息的传输流程为例进行详细说明。 参照图 3 , 为本发明实 施例中 IMS域消息业务实现方法的信令流程图， 具体步骤如下：
301、 UE1向呼叫会话控制功能实体 CSCF1发送 MESSAGE消息； 基于会话发起协议 (SIP, Session Initiation Protocol)利用 MESSAGE消息 实现即时消息机制， 在消息头域中携带主叫和被叫用户的地址以及消息内 容相关说明， 地址的形式通常是" im: user(¾domain"0 在其请求消息体中携 带即时消息内容。 消息体中填充的内容可以是文本， 也可以包含多媒体片 段， 例如声音和图片。 每一条即时消息的发送和接收都是一个单独的过程， 与其他消息的处理没有必然的上下文联系。
302、 CSCF1转发 MESSAGE消息到 MAS1 ;
CSCF1根据业务触发原则将消息触发到 MAS1。
303、MAS1根据用户注册信息判断主被叫用户是否属于同一个 IMS域， 当主被叫用户属于同一个 IMS域时， 执行步骤 304;
每个 MAS会保存有本 IMS域内用户的注册信息， MAS1查找本 IMS 域保存的用户的注册信息， 如果查找到被叫用户的注册信息， 说明主被叫 用户属于同一个 IMS域。
如果主被叫用户不属于同一个 IMS域，例如不属于同一个服务运营商，
MAS1 无法查找到被叫用户的注册信息， 则按照现有技术中通过 CSCF2、 MAS2将消息转发到 UE2, 不再详细描述。
304-305 , MAS1通过 CSCF1转发 MESSAGE消息到 UE2;
MAS1在发往 CSCF1的消息中携带有主被叫用户是否在同一个域的相 关信息， CSCFl根据该信息进行判断，如果主被叫用户属于同一个 IMS域， 则 CSCF1直接将 MESSAGE消息路由到 UE2;如果主被叫用户不属于同一 个 IMS域， 则 CSCF1将 MESSAGE消息先路由到被叫用户所属 IMS域， 即通过收方网络中的 CSCF2转发到 MAS2, 再由 MAS2通过 CSCF2将消 息发送到 UE2, 即现有技术方案中所示流程。
306-308, UE2接收到 MESSGE消息后通过 MAS1、 CSCFl向 UE1返 回 200 OK应答。
当 UE1接收到 200 OK应答时， 说明消息发送成功。
可见， 与现有技术中不同的是， 当 MAS1通过保存的用户注册信息判 断主被叫用户属于同一个 IMS 域时， 不需要通过收方网络的 CSCF2 及 MAS2将消息发送到 UE2 , 而是直接将消息发送到 UE2 , 因此避免了消息 的多次转发， 节约了交互流程以及消息传输时间。
即时消息也可以是基于会话的消息， 可以通过 INVITE请求来建立连 接。 与 MESSAGE消息不同的是， 在将消息通过发方网络转发到被叫用户 之前， UE1需要发送 INVITE请求并通过发方网络中 CSCF1转发到 MAS1 , MAS1接收到 INVITE请求后，根据用户注册信息判断主被叫用户是否属于 同一个 IMS域， 如果属于， 则 MAS1发送 INVITE请求并通过 CSCF1转发 到 UE2,待 UE2按照 INVITE请求的路径向 UE1返回 200 OK应答后， UE1 再通过 INVITE请求与 UE2建立的连接将消息体通过 CSCF1转发到 MAS1 , MAS1将消息体通过 CSCF1发送到 UE2, 从而避免了 CSCF2与 MAS2的 转发， 节约了交互流程与消息体传输时间。
存储转发消息业务的实现与即时消息的传输流程有所不同， 当 MAS1 接收到消息体时， 不是直接将消息体发送出去， 而是将消息体暂时保存， 然后再发送到 UE2。 为使本领域技术人员更加清楚明了， 以下来具体说明 当主被叫用户属于同一个 IMS域时， 存储转发消息中基于会话的消息业务 的实现流程。 参照图 4, 为本发明实施例中 IMS域消息业务实现方法的信 令流程图， 具体步骤如下：
401-402, UE1发送 INVITE请求并通过 CSCF1转发到 MAS1 ;
UE1发起 INVITE请求，该请求中提供了足够的信息以便被叫用户能够 参加该会话， 包括消息体的类型和格式以及被叫用户地址和端口信息等。 例如消息体是文本、 语音还是视频， 以及对应的格式。 INVITE请求被送到 CSCF1 , CSCF1根据业务触发原则将请求触发到 MAS1。
403-404, MAS 1接收到 INVITE请求后返回 200 OK应答并通过 CSCF1 转发到 UE1；
MAS1接收该请求， 并通过 CSCF1向 UE1返回 200 OK应答。
405-406, UE1接收到 200 OK应答后返回 ACK确认消息并通过 CSCF1 转发到 MAS1 ;
由于 CSCF1在 INVITE请求消息中加入了路由字段， ACK确认消息沿 着 INVITE的请求路径发送到 MAS1。
通过步骤 401 ~ 406, UE1与 MAS1建立了连接， UE1可以通过所述连 接向 MAS1直接传送消息体。
407、 UE1通过步骤 401 406所建立的连接向 MAS1传送消息体；
408-409, MAS1发起结束会话请求 BYE并通过 CSCF1转发到 UE1 ; 410 411、 UE1返回结束会话请求应答并通过 CSCF1转发到 MAS1 ; 会话结束请求也可以由 UE1来发起， 当双方任一方想结束会话时， 会 直接发送一个 BYE请求给对方， 对方会回送一个 200 OK响应， 这样双方 会话结束。
412、 MAS1判断主被叫用户是否属于同一个 IMS域， 当主被叫用户属 于同一个 IMS域时， 执行步骤 413;
MAS1中仅保存有发方网络中用户注册信息， MAS1可以根据本地保存 的用户注册信息进行判断， 如果能够查找到被叫用户的注册信息， 则说明 主被叫用户属于同一个 IMS网络， 也即属于同一个 IMS域。
如果主被叫用户不属于同一个 IMS域， 则按照现有技术中的消息体传 输流程执行， 具体参照图 2所示的步骤 213~238。
413-414, MAS1发送 INVITE请求并通过 CSCF1转发到 UE2;
MAS1在发往 CSCF1的 INVITE请求中携带有主被叫用户是否在同一 个域的相关信息， CSCF1 根据该信息进行判断， 如果主被叫用户属于同一 个 IMS域， 则 CSCF1直接将 INVITE请求转发到 UE2; 如果主被叫用户不 属于同一个 IMS域， 则 CSCF1将 INVITE请求先转发到被叫用户所属 IMS 域， 即通过收方网络中的 CSCF2转发到 MAS2, 再由 MAS2通过 CSCF2 将 INVITE请求发送到 UE2 , 即现有技术方案中所示流程。
415-416, UE2接收到 INVITE请求后返回 200 OK应答并通过 CSCF1 转发到 MAS 1 ;
417-418, MAS1返回 ACK确认并通过 CSCF1转发到 UE2;
步骤 413 418与步骤 401 406类似， 通过发起会话请求建立一个新的 连接， 不再详细描述。
419、 MAS1通过步骤 413 418建立的连接向 UE2传送消息体；
420-421 , UE2发起结束会话请求 BYE并通过 CSCF1转发到 MAS1； 从该实施例可以看出， 当主被叫用户属于同一个 IMS 域时， 不需要 MAS1与 MAS2进行协商建立新的会话连接， 消息体也不需要经过收方网 络中 MAS2、 CSCF2的转发， 可以节约大量的信息交互流程及消息体传输 时间。 特别是当传输的消息体较大时， 可能需要经过较长的时间才能传输 完毕， 减少消息体的一次转发就可以节约较多的消息体传输时间。
基于会话的消息中较典型的是消息会话中继协议 （MSRP, Message Session Relay Protocol)消息， MSRP是一个基于文本的协议， 主要特点是它 运行在支持拥塞控制的协议之上， 如传输控制协议（TCP, Transmission Control Protocol) , 简单控制传输协议 (SCTP, Simple Control Transmission Protocol )和 TCP上的传输层安全 (TLS, Transport Layer Security)协议， 因此， MSRP不限制消息体的大小。 MSRP的另一个特点是它工作在媒体层面， 因 此不穿越 SIP代理服务器如 CSCF, 例如 CSCF, 这样 SIP代理服务器就不 会受到大量即时消息的干扰。 因此， MSRP消息的消息体一般较大， 因此需 要的传输时间也较长。 当主被叫用户属于同一个 IMS域时， MSRP消息就 不需要经过 MAS2的再次转发， 因此可以节约较多的消息传输时间。
对于存储转发消息中非基于会话的消息， 如 MESSAGE消息， 与即时 消息中 MESSGE消息不同之处在于， 当 MAS1接收到 UE1通过 CSCF1发 送的 MESSAGE消息后， MAS1通过 CSCF1向 UE1返回 200 OK应答， 表 明消息发送成功。 MAS1进而根据用户注册信息判断主被叫用户是否属于同 一个 IMS域， 如果属于同一个域， 则发送 MESSAGE消息并通过 CSCF1 转发至 UE2, 消息发送成功后， UE2通过 CSCF1向 MAS1返回 200 OK应 答。 可见， 当主被叫用户属于同一个 IMS域时， MESSAGE消息同样不需 要经过收方网络中 MAS2、 CSCF2的转发， 因此可以节约大量的信息交互 流程及消息体传输时间。
以上对主被叫用户属于同一个 IMS域的情况进行了较详细的描述， 以 下说明当主被叫用户不属于同一个 IMS域时， 本发明实施例 IMS域消息业 务实现的具体流程。
当主被叫用户不属于同一个 IMS域时， 对于较大的消息， 例如 MSRP 消息， 通常传送的为较大的文本或者语音视频， 如果发方网络与收方网络 将消息体存储在同一物理节点， 例如， 当发方网络与收方网络均将消息体 存储在 MAS上， MAS1与 MAS2是不同的逻辑节点， 但二者实质是同一个 物理节点， 或者发方网络与收方网络共用一个 MSRP服务器， 用于保存 MSRP消息， 如果仍然按照现有技术将 MSRP消息从发方网络传输到收方 网络， 则仍然需要花费较长的传输时间， 下面参照附图说明当主被叫用户 不在同一个 IMS域， 但发方网络与收方网络将消息体存储在同一个物理节 点上时消息的具体流程， 其中， UE1将消息体发送到 MAS1与图 4所示实 施例中步骤 401~411相同， MAS2将消息体传送到 UE2的具体流程与现有 技术中步骤 228-238相同， 不再详细描述， 以下仅就 MAS1接收到消息体 后至 MAS2需要将消息体发送到 UE2之前的流程进行详细描述。
参照图 5, 为本发明实施例中 IMS域消息业务实现方法的部分信令流 程图， 具体步骤如下：
501、 MAS1判断主被叫用户是否属于同一个 IMS域， 当主被叫用户不 属于同一个 IMS域时， 执行步骤 502;
502-504, MAS1发送 INVITE请求并依次通过 CSCF1、 CSCF2转发到 MAS2;
505-507, MAS2返回 200 OK应答并依次通过 CSCF2、 CSCF1转发到 MAS1 ; 508-510, MAS1 返回 ACK确认并依次通过 CSCF1、 CSCF2转发到 MAS2;
511、 MAS1判断发方网络与收方网络是否将消息体存储在同一个物理 节点上， 当发方网络与收方网络将消息体存储在同一物理节点上时， 执行 步骤 512;
MAS1可以通过消息中所携带的收方网络中存储消息体的 IP地址或者 物理地址进行判断， 也可以设置一个专门的标志， 以区别是否与收方网络 将消息体存储在同一物理节点。 例如， 主被叫用户中所在的 MAS为同一个 物理节点， 且保存 MSRP消息， MAS1可以通过消息中携带的 MAS2的 IP 地址进行判断， 如果 MAS2的 IP地址与 MAS1的 IP地址相同， 说明发方 网络与收方网络共享同一个 MAS , 且 MSRP消息也都存储在该 MAS上。
512、 MAS1通过步骤 502 510所建立的连接发送消息通知给 MAS2; 由于该步骤中 MAS1不需要向 MAS2传送具体的 MSRP消息体， 而只 是发送一个消息通知告诉 MAS2 存放消息体的具体物理地址， 或者告诉 MAS2消息体已发送， 尽管实际并没有发送。 由于消息通知很小， 所需传输 时间 艮短， 所以可以减少消息体传输时间。
513-515, MAS1发起结束会话请求 BYE并依次通过 CSCF1、 CSCF2 转发到 MAS2;
当 MAS2需要将消息体发送到 UE2时， MAS2发起 INVITE请求并通 过 CSCF2转发到 UE2, 当 MAS2返回 ACK响应后， 连接建立， MAS2将 消息体传送到 UE2, 具体流程与现有技术中步骤 228~238相同， 不再详细 描述。
516-518, MAS2返回结束会话请求应答 200 OK并依次通过 CSCF2、 CSCF1转发到 MAS1。
以上对主被叫用户不在同一个 IMS域， 但发方网络与收方网络又将消 息体保存在同一物理节点时消息业务的实现流程进行了较详细的说明。
对于 MSRP消息业务， 还有可能存在主被叫用户既属于同一个域， 发 方网络与收方网络又将消息体保存在同一物理节点的情况， 例如都保存在 同一个 MAS中。 当 MAS1接收到 UE1发送的 MSRP消息时， 由于判断得 知被叫用户也属于发方网络， 即主被叫用户属于同一个 IMS域， 发方网络 与收方网络拥有同一个 MAS, 则可以直接将消息体发送到被叫用户。 而如 果发方网络与收方网络将消息体保存在同一物理节点， 即是由 MAS2将消 息体发送到 UE2,由于发方网络与收方网络拥有同一个 MAS,也即由 MAS1 发往 UE2。 因此， 当主被叫用户即属于同一个域， 发方网络与收方网络又 将消息体保存在同一物理节点时消息传输流程与主被叫用户即属于同一个 域， 但发方网络与收方网络又将消息体保存在同一物理节点的传输流程相 同， 因此， 当 MAS1判断得知主被叫用户属于同一个 IMS域时， 不需要判 断发方网络与收方网络是否将消息体保存在同一物理节点上， 以减少处理 流程， 节约消息体传输时间。
以上各实施例说明了消息业务实现方法， 以下具体说明本发明实施例 所提供的消息应用服务器。
参照图 6, 为本发明实施例中的消息应用服务器结构示意图， 该消息应 用服务器包括：
用户注册信息存储单元 61 , 用于存储用户注册信息；
接收单元 62, 用于接收主叫用户发送的消息体；
第一判断单元 63 ,用于当所述接收单元 62接收到主叫用户发送的消息 体时， 根据用户注册信息存储单元 61中存储的用户注册信息判断主被叫用 户是否属于同一个 IMS域；
第一发送单元 64,用于当所述第一判断单元 63得出主被叫用户属于同 一个 IMS域时，将接收单元 62接收到的主叫用户发送的消息体发送到被叫 用户。
这种消息应用服务器不是不加区分地将所有接收到主叫用户发送的消 息体都转发到被叫用户所在的收方网络再转发， 而是需要发送消息体时， 预先判断主被叫用户是否属于同一个 IMS域， 如果属于同一个 IMS域， 发 方网络可以直接和被叫用户进行信息交互， 因此可以将消息体通过主叫用 户所在的发方网络直接发送到被叫用户。 所以， 釆用这种消息应用服务器， 在主被叫用户属于同一个 IMS域时， 可以减少一次消息体的转发， 进而可 以减少大量的信息交互流程与消息体传输时间。 如果所述消息应用服务器用于处理存储转发模式的消息业务， 例如传 输的消息体是通过 MSRP消息承载的， 则可以对本实施例所描述的消息应 用服务器做进一步改进， 以下作为另一实施例进行详细描述。
参照图 7 ,为本发明实施例中的消息应用服务器结构示意图，可以看出， 与图 6 所示实施例不同之处在于， 该消息应用服务器还包括第二判断单元 71与第二发送单元 72, 其中：
第二判断单元 71 ,用于当所述第一判断单元 63得出主被叫用户不属于 同一个 IMS域时， 判断发方网络与收方网络是否将消息体保存在同一物理 节点上；
第二发送单元 72,用于当所述第二判断单元 71得出发方网络与收方网 络将消息体保存在同一物理节点上时， 通知收方网络所述消息体已发送。
当主被叫用户不属于同一个 IMS域时， 但发方网络与收方网络将消息 体存储在相同的物理节点上时， 该消息服务器不需要将消息体发送到被叫 网络， 而是通知收方网络， 由于消息通知很小， 传输时间很短， 而存储转 发消息本身一般比较大， 需要较长的传输时间， 同时也浪费了带宽资源。 所以这种消息应用服务器可以减少消息交互及处理流程， 节约消息体传输 时间。
本发明实施例还可提供另一种消息应用服务器， 用于接收即时消息中 基于会话的消息， 参照图 8, 为本发明实施例中提供的消息应用服务器结构 示意图， 该消息应用服务器包括：
用户注册信息存储单元 81 , 用于存储用户注册信息；
第一接收单元 82, 用于接收主叫用户发送的建立连接会话请求； 第二接收单元 83 , 用于接收主叫用户发送的消息体；
判断单元 84 ,用于当所述第一接收单元 82接收到主叫用户发送的建立 连接的会话请求时， 根据用户注册信息存储单元 81中存储的用户注册信息 判断主被叫用户是否属于同一个 IMS域；
发送单元 85 ,用于当所述判断单元 84得出主被叫用户属于同一个 IMS 域时， 向被叫用户发送建立连接会话请求， 并通过建立的连接将第二接收 单元 83接收到的主叫用户发送的消息体发送到被叫用户。 可见， 本实施例与图 6 所示实施例不同之处在于， 该消息服务器接收 到用户发送的建立连接会话请求时即判断主被叫用户是否属于同一个 IMS 域， 而不是等到接收到消息体后再判断。 不过， 当主被叫用户属于同一个 IMS 域时， 本实施例不需要将消息体发送到被叫用户所在的收方网络再转 发， 这一点与图 6 所示实施例是相同的， 因此， 当主被叫用户属于同一个 IMS 域时， 该消息应用服务器也可减少信息交互流程， 节约消息体传输时 间。
可以看出， 以上各实施例具有如下有益效果：
由于当发方消息应用服务器判断得知主被叫用户位于同一个 IMS 域 时， 不需要将消息体发送到收方网络再转发， 而是直接与被叫用户进行信 息交互， 将消息体直接发送到被叫用户， 从而减少了信息交互流程以及消 息体的传输时间。
对于存储转发消息业务， 当发方网络与收方网络将消息体存储在同一 物理节点时， 由于发方网络不需要将消息体转发， 而只是通知收方网络， 因此可以减少传输时间， 尤其当传输的消息体较大时。
以上对本发明实施例所提供的消息业务实现方法和消息应用服务器通 过实施例进行了详细介绍， 以上实施例的说明只是用于帮助理解本发明的 方法及其思想； 同时， 对于本领域的一般技术人员， 依据本发明的思想， 在具体实施方式及应用范围上均会有改变之处， 综上所述， 本说明书内容 不应理解为对本发明的限制。

Claims

权 利 要 求
1. 一种多媒体子系统 IMS域消息业务实现方法， 其特征在于， 包括： 接收主叫用户发送的消息体；
根据用户注册信息判断主叫用户与被叫用户是否属于同一个 IMS域； 当所述主叫用户与被叫用户属于同一个多媒体子系统 IMS域时， 将所 述消息体直接发送给被叫用户。
2. 如权利要求 1所述的 IMS域消息业务实现方法， 其特征在于， 所述 消息体是通过 MESSAGE消息承载的。
3. 如权利要求 1所述的 IMS域消息业务实现方法， 其特征在于， 所述 接收主叫用户发送的消息体的步骤包括：
接收主叫用户发送的建立连接会话请求， 并通过所述建立连接会话请 求建立的连接接收所述主叫用户发送的消息体；
所述将消息体发送到被叫用户的步骤包括：
向被叫用户发送建立连接会话请求， 并通过所述建立连接会话请求建 立的连接向所述被叫用户发送所述消息体。
4. 如权利要求 3所述的 IMS域消息业务实现方法， 其特征在于， 进一 步包括：
当主叫用户与被叫用户不属于同一个 IMS域时， 判断是否与收方网络 将消息体存储在同一物理节点上；
当与收方网络将消息体存储在同一物理节点上时， 发送消息通知收方 网络的 MAS存放所述消息体的物理地址； 或通知收方网络所述消息体已发 送。
5. 一种多媒体子系统 IMS域消息业务系统， 其特征在于， 包括消息应 用服务器 MAS、 呼叫会话控制功能实体 CSCF以及主叫用户设备和被叫用 户设备，
所述消息应用服务器 MAS, 根据主叫用户和被叫用户的注册信息， 判 断主叫用户与被叫用户是否属于同一个 IMS域，以及发送消息给用户设备； 所述呼叫会话控制功能实体 CSCF, 用于在 MAS与用户设备 UE之间 转发消息； 当所述 MAS 判定主叫用户与被叫用户属于同一个多媒体子系统 IMS 域时， 通过所述 CSCF将所述消息体直接发送给被叫用户。
6. 一种多媒体子系统 IMS域消息业务实现方法， 其特征在于， 包括： 接收主叫用户发送的建立连接会话请求；
根据用户注册信息判断主叫用户与被叫用户是否属于同一个 IMS域； 当主叫用户与被叫用户属于同一个 IMS域时， 向被叫用户转发所述建 立连接会话请求；
通过所述建立连接会话请求建立的连接， 接收主叫用户发送的消息体 并将所述消息体转发到所述被叫用户。
7. 一种消息应用服务器， 其特征在于， 包括：
用户注册信息存储单元， 用于存储用户注册信息；
接收单元， 用于接收主叫用户发送的消息体；
第一判断单元，用于判断主叫用户与被叫用户是否属于同一个 IMS域； 当所述接收单元接收到主叫用户发送的消息体时， 根据用户注册信息存储 单元中存储的用户注册信息判断主叫用户与被叫用户是否属于同一个 IMS 域；
第一发送单元， 当所述第一判断单元判定主叫用户与被叫用户属于同 一个 IMS域时， 将所述接收单元接收到的主叫用户发送的消息体直接发送 给被叫用户。
8. 如权利要求 7所述的消息应用服务器， 其特征在于， 还包括： 第二判断单元， 当所述第一判断单元得出主叫用户与被叫用户不属于 同一个 IMS域时， 判断发方网络与收方网络是否将消息体保存在同一物理 节点上；
第二发送单元， 当所述第二判断单元判定发方网络与收方网络将消息 体保存在同一物理节点上时， 发送消息通知收方网络的消息应用服务器存 放所述消息体的物理地址； 或通知收方网络所述消息体已发送。
9. 一种消息应用服务器， 其特征在于， 包括：
用户注册信息存储单元， 用于存储用户注册信息；
第一接收单元， 用于接收主叫用户发送的建立连接的会话请求； 第二接收单元， 用于接收主叫用户发送的消息体；
判断单元， 当所述第一接收单元接收到主叫用户发送的建立连接的会 话请求时， 根据用户注册信息存储单元中存储的用户注册信息判断主叫用 户与被叫用户是否属于同一个 IMS域；
发送单元， 当所述判断单元判定主叫用户与被叫用户属于同一个 IMS 域时， 向被叫用户转发所述建立连接会话请求， 并通过所述建立连接会话 请求建立的连接， 接收主叫用户发送的消息体， 并将所述消息体转发到所 述被叫用户。
PCT/CN2008/070947 2007-05-17 2008-05-13 Procédé et système de réalisation de service de messagerie, et serveur d'application de messagerie WO2008141562A1 (fr)

Priority Applications (3)

Application Number Priority Date Filing Date Title
ES08748556T ES2395997T3 (es) 2007-05-17 2008-05-13 Método y sistema de realización de servicios de mensajería y servidor de aplicación de mensajería
EP08748556A EP2146511B1 (en) 2007-05-17 2008-05-13 Message service realizing method and system, and message application server
US12/342,998 US8014775B2 (en) 2007-05-17 2008-12-23 Method and system for implementing messaging services and a message application server

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CNB2007101070459A CN100512461C (zh) 2007-05-17 2007-05-17 消息业务实现方法和消息应用服务器
CN200710107045.9 2007-05-17

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US12/342,998 Continuation US8014775B2 (en) 2007-05-17 2008-12-23 Method and system for implementing messaging services and a message application server

Publications (1)

Publication Number Publication Date
WO2008141562A1 true WO2008141562A1 (fr) 2008-11-27

Family

ID=38866497

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2008/070947 WO2008141562A1 (fr) 2007-05-17 2008-05-13 Procédé et système de réalisation de service de messagerie, et serveur d'application de messagerie

Country Status (5)

Country Link
US (1) US8014775B2 (zh)
EP (1) EP2146511B1 (zh)
CN (1) CN100512461C (zh)
ES (1) ES2395997T3 (zh)
WO (1) WO2008141562A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8014775B2 (en) 2007-05-17 2011-09-06 Huawei Technologies Co., Ltd Method and system for implementing messaging services and a message application server

Families Citing this family (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8886729B2 (en) * 2009-10-30 2014-11-11 Verizon Patent And Licensing Inc. Methods, systems and computer program products for a mobile-terminated message SPAM restrictor
CN102185792A (zh) * 2011-04-25 2011-09-14 苏州阔地网络科技有限公司 一种即时通讯的文件处理通知方法及即时通讯服务器
CN102148834A (zh) * 2011-04-25 2011-08-10 苏州阔地网络科技有限公司 一种基于社区平台的区块安全同步浏览方法及系统
CN103516583B (zh) * 2012-06-28 2017-09-29 北京奇虎科技有限公司 一种用于即时通讯中进行消息交互的方法及装置
CN103905380B (zh) * 2012-12-25 2017-03-22 中国移动通信集团公司 一种业务呼叫方法、设备和系统
CN103916305A (zh) * 2012-12-31 2014-07-09 北京新媒传信科技有限公司 传送即时通讯消息的方法及终端
CN103347094A (zh) * 2013-07-22 2013-10-09 广州市交通信息中心 一种出租车智能电召系统及方法
US9769646B2 (en) * 2015-02-26 2017-09-19 T-Mobile Usa, Inc. Realm translation in an IMS network
CN104954373B (zh) * 2015-06-12 2019-01-18 广东天波信息技术股份有限公司 统一通信主动sip呼叫方法及系统
CN114070823B (zh) * 2021-11-10 2023-11-03 北京挪拉斯坦特芬通信设备有限公司 会话建立控制方法、电子设备和计算机可读存储介质

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20040148416A1 (en) 2003-01-29 2004-07-29 Jryki Aarnos Method and apparatus for messaging between a client of an sip-based network and a client of a wireless village network
CN1925450A (zh) * 2005-09-02 2007-03-07 华为技术有限公司 一种防止媒体流迂回的通信方法
US20070097879A1 (en) * 2003-12-30 2007-05-03 Peter Bleckert Method and communication system for automatically discovering the multimedia service capability
CN101060650A (zh) * 2007-05-17 2007-10-24 华为技术有限公司 消息业务实现方法和消息应用服务器

Family Cites Families (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7027433B2 (en) * 2001-06-20 2006-04-11 Nokia Corporation Routing a call between different types of networks
GB0208069D0 (en) * 2002-04-08 2002-05-22 Nokia Corp Message header for messaging service
US20040187021A1 (en) 2003-02-10 2004-09-23 Rasanen Juha A. Mobile network having IP multimedia subsystem (IMS) entities and solutions for providing simplification of operations and compatibility between different IMS entities
GB2398458B (en) * 2003-02-15 2005-05-25 Ericsson Telefon Ab L M Conversational bearer negotiation
GB0311004D0 (en) * 2003-05-13 2003-06-18 Nokia Corp Charging in communication networks
CN1758649B (zh) 2004-10-05 2010-04-28 华为技术有限公司 版本不同的网间互联协议网络互通的方法
FR2882482B1 (fr) * 2005-02-23 2007-04-20 Alcatel Sa Dispositif de controle d'acces de terminaux d'abonnes d'un domaine cs a des services d'un reseau de communication ims
WO2006111845A2 (en) * 2005-04-22 2006-10-26 Nortel Networks Limited Session initiation from application servers in an ip multimedia subsystem
US20060245391A1 (en) 2005-04-29 2006-11-02 Alcatel Interactive voice response system and method for updating presence information
US8036659B2 (en) * 2005-04-30 2011-10-11 Samsung Electronics Co., Ltd Method for requesting an unregistered UE to perform registration in the IMS
US20070149166A1 (en) * 2005-12-23 2007-06-28 Telefonaktiebolaget Lm Ericsson (Publ) Voice call continuity for emergency calls
CN100563235C (zh) * 2006-01-09 2009-11-25 华为技术有限公司 互通功能网元、csi终端与ims终端互通系统及其方法
KR100925733B1 (ko) * 2006-04-21 2009-11-11 엘지전자 주식회사 무선통신 시스템의 정보 전달방법 및 이를 지원하는무선통신 단말기
US8929360B2 (en) * 2006-12-07 2015-01-06 Cisco Technology, Inc. Systems, methods, media, and means for hiding network topology

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20040148416A1 (en) 2003-01-29 2004-07-29 Jryki Aarnos Method and apparatus for messaging between a client of an sip-based network and a client of a wireless village network
US20070097879A1 (en) * 2003-12-30 2007-05-03 Peter Bleckert Method and communication system for automatically discovering the multimedia service capability
CN1925450A (zh) * 2005-09-02 2007-03-07 华为技术有限公司 一种防止媒体流迂回的通信方法
EP1760986A1 (en) 2005-09-02 2007-03-07 Huawei Technologies Co., Ltd. Communication method and device for preventing media stream circuity (tromboning)
CN101060650A (zh) * 2007-05-17 2007-10-24 华为技术有限公司 消息业务实现方法和消息应用服务器

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See also references of EP2146511A4 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8014775B2 (en) 2007-05-17 2011-09-06 Huawei Technologies Co., Ltd Method and system for implementing messaging services and a message application server

Also Published As

Publication number Publication date
EP2146511A4 (en) 2010-07-28
CN100512461C (zh) 2009-07-08
EP2146511B1 (en) 2012-11-07
ES2395997T3 (es) 2013-02-18
US20090111430A1 (en) 2009-04-30
CN101060650A (zh) 2007-10-24
EP2146511A1 (en) 2010-01-20
US8014775B2 (en) 2011-09-06

Similar Documents

Publication Publication Date Title
WO2008141562A1 (fr) Procédé et système de réalisation de service de messagerie, et serveur d'application de messagerie
EP1665722B1 (en) Exchange protocol for combinational multimedia services
US8725802B2 (en) Method for transferring file in conference system, file transfer system and conference server
JP5606074B2 (ja) 通信ネットワークにおける動的サービストリガ
WO2007016851A1 (fr) Procede etablissant un canal de transmission de donnees pour dialogue en ligne afin de realiser la transmission du message
WO2009079954A1 (fr) Procédé, système et module d'interfonctionnement de service de message pour mettre en œuvre un interfonctionnement de service de message
WO2008131627A1 (fr) Procédé, système de traitement de session et de message
WO2007041937A1 (fr) Methode d'envoi et de reception de message hors ligne, appareil client, serveur et systeme
WO2007068209A1 (fr) Procede, systeme et dispositif d'envoi de messages instantanes ims
WO2012000347A1 (zh) 一种跨平台会议融合的方法、装置和系统
WO2008022600A1 (fr) Procédé, dispositif et système de transfert de sms en ims
WO2007009369A1 (fr) Méthode et système grâce auxquels un utilisateur de messagerie instantanée peut utiliser un chat room d’un système de messagerie instantanée auquel l’utilisateur n’appartient pas
WO2007079645A1 (fr) Procédé et système de notification mettant en oeuvre un message de blocage de messagerie instantanée
WO2008089642A1 (fr) Procédé, dispositif et système pour le transfert d'informations de terminal dans un sous-système multimédia
WO2008022596A1 (fr) Procédé, système et appareil pour la remise de sms en mode de partage dynamique
KR101397633B1 (ko) 아이엠에스 기반 인스턴트 메시지 서비스 제공 시스템 및방법
WO2008074235A1 (fr) Procédés d'interconnexion et passerelles d'interconnexion de message entre des systèmes de messagerie
WO2009155824A1 (zh) 一种彩铃、彩像业务的实现方法及系统
WO2013152702A1 (zh) 发送语音消息的方法及系统、融合消息服务器及客户端
WO2008011790A1 (fr) Procédé, système et appareil de réseau permettant d'établir une session
EP3228057B1 (en) Ims application control protocol
WO2011150705A1 (zh) 一种实现即时通信的系统及方法
WO2007019777A1 (fr) Méthode d’établissement de session et nœud de contrôle de session
WO2013152703A1 (zh) 语音留言方法及系统、融合消息服务器及客户端
WO2008080297A1 (fr) Procédé, équipement et système pour mettre en rapport une session

Legal Events

Date Code Title Description
WWE Wipo information: entry into national phase

Ref document number: 2008748556

Country of ref document: EP

121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 08748556

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE