WO2007006235A1 - Procédé et système pour convertir un message - Google Patents

Procédé et système pour convertir un message Download PDF

Info

Publication number
WO2007006235A1
WO2007006235A1 PCT/CN2006/001661 CN2006001661W WO2007006235A1 WO 2007006235 A1 WO2007006235 A1 WO 2007006235A1 CN 2006001661 W CN2006001661 W CN 2006001661W WO 2007006235 A1 WO2007006235 A1 WO 2007006235A1
Authority
WO
WIPO (PCT)
Prior art keywords
message
ims
format
user
sip
Prior art date
Application number
PCT/CN2006/001661
Other languages
English (en)
French (fr)
Inventor
Chengzhen Sun
Xiaoqin Duan
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 JP2008520697A priority Critical patent/JP5080465B2/ja
Priority to EP06761414A priority patent/EP1903724A4/en
Publication of WO2007006235A1 publication Critical patent/WO2007006235A1/zh

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M7/00—Arrangements for interconnection between switching centres
    • H04M7/12—Arrangements for interconnection between switching centres for working between exchanges having different types of switching equipment, e.g. power-driven and step by step or decimal and non-decimal
    • H04M7/1205—Arrangements for interconnection between switching centres for working between exchanges having different types of switching equipment, e.g. power-driven and step by step or decimal and non-decimal where the types of switching equipement comprises PSTN/ISDN equipment and switching equipment of networks other than PSTN/ISDN, e.g. Internet Protocol networks
    • H04M7/126—Interworking of session control protocols
    • H04M7/127—Interworking of session control protocols where the session control protocols comprise SIP and SS7
    • 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/60—Network streaming of media packets
    • H04L65/75—Media network packet handling
    • H04L65/756—Media network packet handling adapting media to device capabilities
    • 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/80—Responding to QoS
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/08—Protocols for interworking; Protocol conversion
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M7/00—Arrangements for interconnection between switching centres
    • H04M7/12—Arrangements for interconnection between switching centres for working between exchanges having different types of switching equipment, e.g. power-driven and step by step or decimal and non-decimal
    • H04M7/1205—Arrangements for interconnection between switching centres for working between exchanges having different types of switching equipment, e.g. power-driven and step by step or decimal and non-decimal where the types of switching equipement comprises PSTN/ISDN equipment and switching equipment of networks other than PSTN/ISDN, e.g. Internet Protocol networks
    • H04M7/1225—Details of core network interconnection arrangements
    • H04M7/123—Details of core network interconnection arrangements where the packet-switched network is an Internet Protocol Multimedia System-type network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M7/00—Arrangements for interconnection between switching centres
    • H04M7/12—Arrangements for interconnection between switching centres for working between exchanges having different types of switching equipment, e.g. power-driven and step by step or decimal and non-decimal
    • H04M7/1205—Arrangements for interconnection between switching centres for working between exchanges having different types of switching equipment, e.g. power-driven and step by step or decimal and non-decimal where the types of switching equipement comprises PSTN/ISDN equipment and switching equipment of networks other than PSTN/ISDN, e.g. Internet Protocol networks
    • H04M7/1225—Details of core network interconnection arrangements
    • H04M7/1235—Details of core network interconnection arrangements where one of the core networks is a wireless network
    • 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
    • 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/06—Message adaptation to terminal or network requirements
    • H04L51/066—Format adaptation, e.g. format conversion or compression
    • 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/58—Message adaptation for wireless communication
    • 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]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04Q—SELECTING
    • H04Q2213/00—Indexing scheme relating to selecting arrangements in general and for multiplex systems
    • H04Q2213/13097—Numbering, addressing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04Q—SELECTING
    • H04Q2213/00—Indexing scheme relating to selecting arrangements in general and for multiplex systems
    • H04Q2213/13176—Common channel signaling, CCS7
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04Q—SELECTING
    • H04Q2213/00—Indexing scheme relating to selecting arrangements in general and for multiplex systems
    • H04Q2213/13196—Connection circuit/link/trunk/junction, bridge, router, gateway
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04Q—SELECTING
    • H04Q2213/00—Indexing scheme relating to selecting arrangements in general and for multiplex systems
    • H04Q2213/13204—Protocols
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04Q—SELECTING
    • H04Q2213/00—Indexing scheme relating to selecting arrangements in general and for multiplex systems
    • H04Q2213/13248—Multimedia
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04Q—SELECTING
    • H04Q2213/00—Indexing scheme relating to selecting arrangements in general and for multiplex systems
    • H04Q2213/13336—Store & forward, messaging systems
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04Q—SELECTING
    • H04Q2213/00—Indexing scheme relating to selecting arrangements in general and for multiplex systems
    • H04Q2213/13348—Channel/line reservation
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04Q—SELECTING
    • H04Q2213/00—Indexing scheme relating to selecting arrangements in general and for multiplex systems
    • H04Q2213/13389—LAN, internet
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/18—Information format or content conversion, e.g. adaptation by the network of the transmitted or received information for the purpose of wireless delivery to users or terminals

Definitions

  • the present invention relates to the field of mobile communications, and more particularly to a method and system for communicating messages using an IP Multimedia System (IMS) message and a user terminal using a non-IMS message.
  • IMS IP Multimedia System
  • IP-based mobile network services With the rise and development of various IP access technologies, how to make existing mobile network services become the services that IP terminals can provide has become a target of the 3rd Generation Partnership Project (3GPP) standardization organization.
  • 3GPP 3rd Generation Partnership Project
  • networks based on IP access methods are becoming more and more popular, such as WLAN networks, NGN networks, etc., for various IP terminals, or multimode terminals supporting IP access methods and mobile network access methods, such as WLAN and WCDMA/ GSM multimode terminals
  • how to reuse existing mobile network service functional entities and protocols as much as possible, and access to the mobile core network through IP-based access networks are common concerns of operators.
  • the IMS format is used for message transmission.
  • the users of the primary and the called party cannot use the IMS service at the same time (including the user not registering the IMS service, or the user is temporarily only registered to the other network and not registered to the IMS network)
  • there may be other ways of interworking such as A user who signs up for IMS travels to other places, and there is no IMS network in the place.
  • Users can only register to other types of networks, such as users can only register to circuit domain (CS), packet domain (PS) or wireless local area network.
  • the IMS format message needs to be converted into a non-IMS format message; or a traditional CS, PS user to the IMS user Sending a message, in order to ensure that the message can be transmitted to the called user, the non-IMS message and the IMS message need to be formatted with each other.
  • a user ID that is only processed by a CS-capable terminal can only be in the E.164 format, and the user identifier in the E.164 format cannot be routed in the IMS network, and the format based on the MAP message is the same as the SIP-based message.
  • the invention provides a message conversion method and system, which realizes message intercommunication when a calling party and a called user cannot simultaneously use an IMS service.
  • the method of the invention comprises:
  • the network When the network receives the IMS message sent by the calling user to the called user, if it is determined that the called user cannot currently receive the IMS message, the IMS message sent by the calling user is converted into a non-IMS that the called user can currently receive.
  • the message format is sent to the called user;
  • the network When the network receives the non-IMS message sent by the calling user to the called user, if it is determined that the called user can currently receive the IMS message, the non-IMS message sent by the calling user is converted into an IMS message format and sent to the called party. user.
  • the network responds to the message returned by the called user, and converts it into a format message that the calling user can receive and sends it back to the calling user.
  • the SIP format message sent by the calling user is converted into a non-IMS format message that the called user can receive, and the specific method is :
  • the SIP format message sent by the calling user is used as the message body of the non-IMS message, and is encapsulated in the non-IMS message as a whole; or the SIP format message sent by the calling user is split into a message header and a message body, and the split message is split.
  • the header is converted into a message header of a non-IMS message, and the split message body is converted into a message body of the non-IMS message, and the converted message is re-encapsulated.
  • the length of the SIP message sent by the calling user exceeds the maximum length specified by the non-IMS message, then 61.
  • the message receiving end combines the split plurality of non-IMS messages into one message according to the flag.
  • the method converts the non-IMS message sent by the calling user into an IMS message format, and the specific method is: extracting the non-IMS message calling party and the called user identity, and converting into a SIP URI format that the SIP message system can recognize, as the converted SIP.
  • the non-IMS message sent by the calling user is used as the message body of the SIP message, and is encapsulated in the SIP message as a whole; or the non-IMS message sent by the calling user is split into a message header and a message body, and the split message header is transformed.
  • the split message body is converted into the message body of the SIP message, and the converted message is re-encapsulated.
  • the non-IMS message is split into multiple SIP messages according to the length specified by the SIP message, and the non-last message of the split SIP message is The set message does not transmit a full tag or the corresponding sequence number, and sets the transfer complete tag in the last message.
  • the message receiving end combines the split plurality of SIP messages into one message according to the flag.
  • the IMS message and the non-IMS message format conversion are implemented by a separately set message application server; or by a functional module provided in an IP message gateway or a short message center.
  • the returned status report is converted by the message application server or the function module into a format message that the user can receive, and Obtain the calling and called user IDs, and convert to the corresponding user ID format according to the network type registered by the calling user.
  • Translating the status report into a format message that the user can receive the specific method is: defining a new SIP response message to respond to the SIP message, the new SIP response message
  • the carried parameter refers to a parameter definition of a mobile application part (MAP) message; the message application server or function module extracts the transfer status related data returned by the called user, converts it into a corresponding MAP message parameter, and converts the new SIP response.
  • the message is converted into a MAP format status report message; or the status report data of the MAP format returned by the called user is extracted into the new SIP response message parameter, and the MAP format message response is converted into the new SIP response message.
  • the state 4 advertisement is converted into a format message that the user can receive, and the specific method may also be: using an existing SIP message, and setting an identifier, using the SIP message with the setting identifier as a status report message;
  • the terminal carries information related to the status report parameter of the MAP format in the SIP message body with the setting identifier, and the message application server or the function module extracts the SIP message content with the setting identifier, and converts the content according to the message content into The status report message of the MAP format carrying the corresponding parameter; or extracting the status report data of the MAP format returned by the called user into the SIP message content with the setting identifier.
  • the status report data of the MAP format is extracted by the message application server or the function module, and converted into an existing SIP response corresponding to the status. Message.
  • the present invention further provides a message conversion system, including: a message receiving and judging device and a message application server;
  • the message receiving and judging device is connected to the message sending/receiving entity of the calling side network, receives the calling message of the calling side, and determines whether the message format conversion is needed according to the message format that the called user can receive; Format conversion, the call message is forwarded to the message application server for processing;
  • the message application server is connected to the message sending/receiving entity of the called side network, and implements IMS format message and non-IMS format message conversion, and forwards the formatted call message to the message sending/receiving entity of the called side network.
  • the called party is received; and the sending status report message returned by the called party is received, and after the corresponding format conversion, the message receiving and determining entity and the message sending/receiving entity of the calling side network are returned to the calling party.
  • the message application server includes: a message format conversion module and a message transmission/status report reception Module
  • the message format conversion module is respectively connected to the message receiving and determining device and the message sending/status report receiving module to implement IMS format message and non-IMS format message conversion;
  • the message sending/status report receiving module is connected to the message sending/receiving entity of the called side network, and sends the format converted call message to the message sending/receiving entity of the called side network, and is sent by the message of the called side network.
  • the receiving entity forwards the call message to the called party; and receives the sending status report message returned by the called party, and forwards the message to the message format conversion module for message format conversion, and then transmits the message through the message receiving and determining device and the calling side network/ The receiving entity returns to the calling party.
  • the message application server is an independently set network entity
  • the IMS message can be converted into a non-IMS message format, sent to the user, or converted into an IMS message and sent to the user; and at the same time, the non-IMS message response returned by the called user is converted into an IMS.
  • the format message is returned to the calling party, or the IMS message response returned by the called user is converted into a message format that the calling party can receive, so that the calling and called user can also implement message intercommunication when the IMS service cannot be used at the same time.
  • Figure la and Figure 1b are signal flow diagrams of the calling user initiating a call according to the present invention.
  • FIG. 2 is a flow chart showing steps of an application server parsing a called identifier
  • 3 is a flow chart showing the processing steps of the application server receiving the status report message
  • FIG. 4 is a flow chart of message conversion and transmission after the called side network receives the IMS message
  • FIG. 5 is a second flow chart of message conversion and transmission after the called side network receives the IMS message
  • FIG. 8 is a message conversion and transmission flow chart of the called side network after receiving the non-IMS message
  • FIG. 8 is a message conversion of the present invention
  • the message conversion method provided by the present invention is applied to message intercommunication using an IMS message and a user terminal using a non-IMS message.
  • the method of the invention comprises:
  • the network When the network receives the IMS message sent by the calling user to the called party, if it is determined that the called user is currently unable to receive the IMS message, the IMS message sent by the calling user is converted into a non-IMS message format that the called user can currently receive. , sent to the called user;
  • the network When the network receives the non-IMS message sent by the calling user to the called user, if it is determined that the called user can currently receive the IMS message, the non-IMS message sent by the calling user is converted into an IMS message format and sent to the called party. user.
  • the IMS message and the non-IMS message format conversion are implemented by an independently set message application server; or by a functional module disposed in an IP message gateway or a short message center.
  • the returned status report is converted by the message application server or the function module into a format that the user can receive.
  • the SIP message format message sent by the calling user is used as the message body of the non-IMS message, and is encapsulated in the non-IMS message, and the primary and called user identifiers are extracted, and converted into a non-IMS message system according to the registered network type.
  • the identified user identification format of the E.164 or NAI (Network Access Identity) and the like suitable for the user registration network is used as the primary and called user identification of the non-IMS message.
  • the length of the IMS message is split into SIP message messages and converted into multiple non-IMS messages.
  • the message is not transmitted with the full tag or the corresponding sequence number, indicating that the message has not yet been sent.
  • Full transfer, and subsequent messages and set the transfer complete flag in the last message to indicate that the message has been transmitted.
  • the message receiving terminal can merge the messages into one message according to the setting of the transmission complete tag in the untransmitted full tag and the last new encapsulated message, if possible.
  • Converting a non-IMS format message into a SIP message format message includes: (1) using a non-IMS message as a message body of the SIP message message, encapsulating the message in the SIP message, and extracting the non-IMS message master and the The user ID is converted into the SIP URI format that the SIP Message message system can recognize as the primary and called user identifier of the SIP Message.
  • the non-IMS message is split according to the length specified by the SIP message, and is converted into multiple SIP Message messages, and the message is not set in the non-last message of the newly encapsulated message.
  • Sending a full tag or a corresponding sequence number indicates that the message has not been fully transmitted, and that there is a subsequent message, and setting the transfer complete flag in the last new encapsulated message indicates that the message has been transmitted.
  • the message receiving terminal can merge the messages into one message according to the setting of the transmission complete tag in the untransmitted full tag and the last new encapsulated message, if possible.
  • the status report can be converted as follows:
  • a new SIP message as a response message, the parameter carried by the new SIP response message being referenced by a parameter definition of a mobile application part (MAP) message; the message application server or function module extracting a transmission returned by the called user Status related data, converted to corresponding MAP message parameters, and converted the new SIP response message into a MAP format status report message; or extracting the called party
  • the status report data of the MAP format returned by the user is converted into the new SIP response message parameter, and the MAP format message response is converted into a new SIP response message.
  • the called user terminal carries the status report parameter related to the MAP format in the SIP message body with the setting identifier
  • the message application server or the function module extracts the SIP message content with the setting identifier, and converts the message content into a MAP format status report message carrying the corresponding parameter according to the message content; or extracts the MAP format returned by the called user.
  • the status report data is converted to the SIP message content with the setup ID.
  • the status report data of the MAP format is extracted by the message application server or the function module, and converted into an existing SIP response message corresponding to the status.
  • the network processing flow after sending the IMS message to the calling user includes:
  • UE1 generates an instant message to be sent and sends a SIP message to the service-call session control function entity (S-CSCF1); S-CSCF1 performs service control to determine the called user identity, if the called user is a SIP URI (unified The resource location identifier format is used to perform the normal IMS MESSAGE transmission process; if the called user identity is in the TEL URI format, the SIP message is forwarded to the application server IP message gateway (IP-Message-GW); the application server IP-Message -GW parses the called identity with ENUM (porting to URI mapping), as shown in Figure 2, converting the called user identity to the SIP URI format:
  • S-CSCF1 service-call session control function entity
  • the conversion is successful, the message converting the called user ID to the SIP URI format is returned to the S-CSCF1, and the S-CSCF1 addresses the called IMS network according to the called user SIP URI and forwards the message to the called IMS. Network, steps 1-8 as shown in Figure la. Forwarding the SIP message to the called IMS network by the S-CSCF1 is the same as the prior art, and will not be described in detail here;
  • the application server IP-Message-GW receives the status report returned by the called party
  • the message is a non-IMS message type. For example, if the SMS message is sent in the MAP format, the returned message is reported as a MAP delivery report message, and the application server IP-Message-GW determines whether it needs to be returned to the UE1 through the IMS message. As shown in FIG. 3, if necessary, the report message in the non-IMS format is converted into a status report applicable to the IMS, and sent to the S-CSCF1 registered by the UE1, otherwise the other processing is performed.
  • the message termination process is the prior art IMS instant message flow; when the called user registers with other non- For the IMS network, and the message needs to be transmitted through the called subscriber registration network, the conversion between the IMS message format and the non-IMS message format is required to ensure that the called user can correctly receive the message.
  • the format conversion function of the message may be located on the message application server of the unregistered service or on the IP message gateway. The specific process is described in the flow of Figure 4 and Figure 5, respectively.
  • the message transmission process when the message format conversion function is located on the message application server of the unregistered service includes the following steps:
  • I-CSCF inquiry-call session control function entity
  • the I-CSCF sends a Cx Location Request (Cx-LocQuery) to the Home Subscriber Server (HSS) to request the S-CSCF of the called UE2; if the HSS queries that the UE2 is an IMS user but is not registered to the IMS network, And the user registers the unregistered service (status), and according to the user's request to register the location and the Cx-LocQueiy request, the HSS returns the S-CSCF registered by the user to the I-CSCF to register or meet the Cx-LocQuery request.
  • An S-CSCF set the I-CSCF selects an appropriate S-CSCF2 according to the S-CSCF or S-CSCF set before registration by the user sent by the HSS;
  • the I-CSCF forwards the SIP Message to the selected S-CSCF2.
  • S-CSCF2 After receiving the message, S-CSCF2 sends Cx-Put/Cx-Pull (carrying the public user ID, 06 001661
  • the S-CSCF name is given to the HSS, the HSS saves the S-CSCF2 name of the unregistered public user identifier; the HSS returns Cx-Put Resp/Cx-Pull Resp (with user information) to the S-CSCF2, and the S-CSCF2 saves the public of the user.
  • User information such as user identification;
  • the S-CSCF2 invokes a service logic suitable for the unregistered service of the user
  • the S-CSCF2 forwards the message to the message application server of the unregistered service
  • the message application server of the unregistered service determines whether the message needs to be forwarded by other means. If forwarding is not required, the message is stored, and the user is notified to register the IMS.
  • the unregistered service message application server initiates a route query request to the HSS to extract routing information, and in the route query request, indicates a message transmission form supported by the message application server, such as receiving and processing CS, PS, and/or WLAN.
  • IP-based messaging if the called user is registered on another network (CS domain, PS domain, I-WLAN or Wimax, etc.), the HLR/HSS returns the prioritized user registration to the message application server according to the indication capability.
  • a list of network addresses which may include a Mobile Services Switching Center (MSC), a Serving GPRS Support Node (SGSN), and/or an IP-MESSAGE-GW address;
  • the unregistered service message application server selects the corresponding transport network according to the user registration network address list, converts the SIP message format message into a corresponding message format, and converts the user ID of the called user to E according to the registered network type. 164 or a network access identifier (NAI), etc., suitable for the user to register the corresponding user identity format of the network, and re-encapsulate the message;
  • NAI network access identifier
  • the message application server of the unregistered service sends a message to the message network element registered by the called user, such as MSC, SGSN or IP-MESSAGE-GW;
  • the message network element registered by the called user forwards the message to the called user terminal UE2;
  • the called user terminal UE2 returns a reception success status report after receiving the message
  • the message network element registered by the called user returns a reception success status report to the message application server.
  • the message application server of the unregistered service After receiving the status report, the message application server of the unregistered service converts the status report into an appropriate SIP acknowledgment response message;
  • the S-CSCF2 returns an appropriate acknowledgment response message to the I-CSCF2;
  • Step 13-15 may also return an acknowledgment response message after the message server receives the S-CSCF2 message.
  • the message transmission process when the message format conversion function is located on the IP message gateway includes the following steps:
  • the IP message gateway converts the SIP message format message into a corresponding message format of the called network currently registered, and converts the user identifier of the called user to a user registration network according to the registered network type, such as E.164 or NAI.
  • the corresponding user identification format re-encapsulating the message;
  • the IP message gateway forwards the converted message to the called user.
  • the called user terminal UE2 returns a reception success status report after receiving the message
  • the IP message gateway After receiving the message status, the IP message gateway converts the status report into a SIP confirmation response message
  • the IP message gateway returns a converted SIP acknowledgement response message to the message application server of the unregistered service
  • the message application server of the unregistered service returns an acknowledgement response message to the S-CSCF2;
  • the S-CSCF2 returns an acknowledgement response message to the I-CSCF2.
  • the I-CSCF2 returns an acknowledgement response message to the calling network.
  • Step 14-16 may also return an acknowledgement response message after the message application server receives the S-CSCF2 message.
  • the application server IP-MESSSAGE-GW If the called user ID is in the TEL URI format and the application server IP-MESSSAGE-GW performs the ENUM query and cannot convert the TEL URI into the SIP URI format during the call originating service call, the application server IP-MESSSAGE-GW will be The user ID is converted into the E.164 format for the TEL URI format, and the message format is converted into an SMS or MMS message format according to the content carried in the message to be re-encapsulated, and then the converted message is forwarded to the traditional short message or MMS message.
  • the center is processed according to the transmission process of short messages or multimedia messages in the prior art.
  • the initiated message is a traditional short message or MMS message in the MAP format, in order to ensure that the message is successfully sent to the called party.
  • the user needs to convert the traditional short message or MMS message of the MAP format into an IMS message format that the called user can receive.
  • the format conversion function may be located on the message application server, or may be located on the IP-MESSAGE-GW, the message The transmission processing flow is shown in Figure 6 and Figure 7.
  • Figure 6 shows that the message format conversion function is located on a message application server, and the message transmission process includes:
  • the user performs a normal registration/re-registration process
  • SMS-SC short message service center
  • SMS-GMSC mobile switching center gateway
  • the SMS-GMSC When the SMS-GMSC extracts routing information from the HLR/HSS, it shall instruct the SMS-GMSC to support the IP message; if the called user registers the IMS service, the HLR/HSS returns the application server address to the SMS-GMSC according to the indication capability;
  • the SMS-GMSC sends a short message to the application server, and the short message is sent in the same manner as the short message sent by the MSC or the SGSN, and carries the MSISDN of the target UE (the mobile station international ISDN number:);
  • the application server converts the MSISDN of the target UE into the SIP URI of the UE by using a local database (or querying other databases or conversion devices, etc.), and converts the short message into a SIP MESSAGE format;
  • the application server sends the converted message to the S-CSCF through the SIP MESSAGE;
  • the S-CSCF forwards the SIP MESSAGE to the UE
  • the UE returns a 200 OK response to the S-CSCF.
  • the S-CSCF returns a 200 OK response to the application server.
  • the UE sends a SIP MESSGAE message sending status report to the S-CSCF.
  • the S-CSCF sends a status report to the application server.
  • the application server returns a 200 OK confirmation message transmission report to the S-CSCF;
  • the S-CSCF returns a 200 OK confirmation message transmission report to the UE; 14.
  • the application server transmits the status report content according to the SIP MESSGAE message, and converts to a MAP message transmission status report;
  • the application server sends the converted MAP message transmission report to the SMS-GMSC;
  • SMS-GMSC sends a message delivery status report to the HSS
  • SMS-GMSC sends a message delivery report to the short message
  • the application server in the above process may be a separate functional entity or a functional module of other application servers.
  • Figure 7 shows the message format conversion function on the IP-MESSAGE-GW.
  • the message transmission process includes:
  • the user terminal performs a normal registration/re-registration process
  • the short message service center forwards the short message of the called user to the SMS-GMSC;
  • the SMS-GMSC When the SMS-GMSC extracts routing information from the HLR/HSS, it shall instruct the SMS-GMSC to support the IP message; if the called user registers the IMS service, the HLR/HSS returns the IP-MESSAGE-GW address to the SMS-GMSC according to the indication capability;
  • the SMS-GMSC sends a short message to the IP-MESSAGE-GW in the same manner as the short message sent by the MSC or the SGSN, carrying the MSISDN of the target UE;
  • IP-MESSAGE-GW uses the local database to convert the MSISDN of the target UE into the SIP URI of the UE, and converts the short message into the SIP MESSAGE format;
  • the IP-MESSAGE-GW sends the converted message to the S-CSCF through the SIP MESSAGE.
  • the S-CSCF forwards the SIP MESSAGE to the UE
  • the UE returns a 200 OK response to the S-CSCF
  • the S-CSCF returns a 200 OK response to the IP-MESSAGE-GW;
  • the UE sends a SIP MESSGAE message sending status report to the S-CSCF;
  • the S-CSCF sends a status report to the IP-MESSAGE-GW;
  • IP-MESSAGE-GW returns a 200 OK confirmation message transmission report to the S-CSCF;
  • the S-CSCF returns a 200 OK confirmation message delivery report to the UE; 14.
  • the IP-MESSAGE-GW converts the content report status to the MAP message transmission status report according to the SIP MESSGAE message delivery status report;
  • the IP-MESSAGE-GW sends the converted MAP message transmission report to the SMS-GMSC;
  • the SMS-GMSC reports the status of the messaging report to the HSS
  • the SMS-GMSC sends a message delivery report to the short message center.
  • the present invention further provides a message conversion system, as shown in FIG. 8, comprising: a message receiving and determining device and a message application server;
  • the message receiving judging device is connected to a message transmitting/receiving entity of the calling side network, and receives a call message of the calling side.
  • the message sending/receiving entity of the calling side network may be an S-CSCF or an I-CSCF; if the calling network is a PS or a CS network, the message sending/receiving entity may be short.
  • SMS-GMSC Message Service - Mobile Switching Center Gateway
  • the message receiving and judging device judges whether the message format conversion needs to be performed according to the message format that the called user can receive; if the message format conversion is required, the call message is forwarded to the message application server for processing. Specifically include:
  • the message receiving and judging device When the message receiving and judging device receives the IMS message sent by the calling side, if it is determined that the called user cannot currently receive the IMS message, the IMS message is sent to the message application server for message format conversion, and is converted into the called user currently receiving. Message format;
  • the message receiving judging device When the message receiving judging device receives the non-IMS message sent by the calling user to the called user, if it is determined that the called user can currently receive the IMS message, the non-IMS message is sent to the message application server and converted into an IMS format message.
  • the message application server is connected to the message sending/receiving entity of the called side network, and implements IMS format message and non-IMS format message conversion, and forwards the formatted call message to the message sending/receiving entity of the called side network.
  • the message sending/receiving entity may be an S-CSCF or an I-CSCF; if the called network is a PS or CS network, the message sending/receiving entity may be short.
  • SMS-GMSC Message Service - Mobile Switching Center Gateway
  • the message application server may further include: a message format conversion module and a message transmission/status report receiving module.
  • the message format conversion module is respectively connected with the message receiving and judging device and the message sending/status report receiving module to implement IMS message format and non-IMS message format conversion.
  • the message sending/status report receiving module is connected to the message sending/receiving entity of the called side network, and sends the format converted call message to the message sending/receiving entity of the called side network, and the message is sent/received by the called side network.
  • the entity forwards the call message to the called party; and receives the sending status report message returned by the called party, and forwards the message to the message format conversion module for message format conversion, and returns the message to the message sending/receiving entity by the message receiving and determining device and the calling side network The caller.
  • the message application server is an independently set network entity; or a function module set in an IP message gateway or a short message center.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Multimedia (AREA)
  • Computer Security & Cryptography (AREA)
  • Telephonic Communication Services (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Computer And Data Communications (AREA)

Description

一种消息转换方法与系统 技术领域
本发明涉及移动通信领域， 尤指一种使用 IP多媒体子系统（IP Multimedia System , IMS ) 消息和使用非 IMS消息的用户终端进行消息互通的方法与系 统。 背景技术
随着各种 IP接入技术的兴起和发展， 如何将现有的移动网业务， 成为 IP 终端所能提供的业务， 已成为第三代合作伙伴计划 （3GPP )标准化组织的一 个目标。 考虑到基于 IP接入方式的网络越来越普遍， 如 WLAN网络、 NGN 网络等， 对各种 IP终端、 或支持 IP接入方式与移动网接入方式的多模终端， 如 WLAN与 WCDMA/GSM多模终端， 如何尽可能重用现有的移动网业务功 能实体和协议， 并通过基于 IP的接入网接入到移动核心网， 是各运营商普遍 关注的问题。
在现有规范中， 要求能够使用 IMS消息时， 尽量使用 IMS格式进行消息传 送。 但是， 当主、 被叫双方用户不能同时使用 IMS业务时（包括用户没有注册 IMS业务， 或者用户暂时只登记到其它网络而没有登记到 IMS网絡中）， 可能存 在通过其它方式进行消息的互通，例如，一个签约 IMS的用户出差到其他地方， 而该地没有 IMS网络， 用户只能登记到其他类型的网络中， 如用户只能登记到 电路域（CS )、 分组域（PS )或者无线局域网络（WLAN ) 中， 此时， 为了能够 将 IMS主叫用户发送的 IMS消息及时发送给被叫用户 , 需要将 IMS格式消息转换 为非 IMS格式消息； 或者， 一个传统的 CS、 PS用户向 IMS用户发送消息， 为了 保证消息能够传送给被叫用户， 需要非 IMS的消息同 IMS消息之间进行相互格 式转换。 这是因为， 例如： 一个只具有 CS能力的终端处理的用户标识只能是 E. 164格式， 而 E. 164格式的用户标识不能在 IMS网络中路由， 而且基于 MAP消 息的格式同基于 SIP消息的格式存在差异， 如果不进行消息格式转换， 将导致 由于网络不支持消息格式、 被叫或主叫用户标识而使消息发送失败。 因此， 要保证接入不同网络类型的用户终端之间实现消息互通， 就必须对传送的消 息格式进行转换， 而现有技术中没有定义格式转换的具体方法。 发明内容
本发明提供一种消息转换方法与系统，实现主被叫用户不能同时使用 IMS 业务时的消息互通。
本发明方法包括：
当网 矣收到主叫用户向被叫用户发送的 IMS消息时， 若判断出被叫用 户当前不能接收 IMS消息， 则将主叫用户发送的 IMS消息转换为被叫用户当 前能接收的非 IMS消息格式， 发送给被叫用户；
当网络接收到主叫用户向被叫用户发送的非 IMS消息时， 若判断出被叫 用户当前能接收 IMS消息，则将主叫用户发送的非 IMS消息转换为 IMS消息 格式， 发送给被叫用户。
根据本发明的上述方法， 网络将被叫用户返回的消息响应， 转换成主叫 用户能接收的格式消息发返回给主叫用户。
根据本发明的上述方法， 若主叫用户发送的 IMS消息格式采用会话初始 协议 SIP消息格式， 则将主叫用户发送的 SIP格式消息转换为被叫用户能接 收的非 IMS格式消息， 具体方法为：
提取 SIP格式消息中的主叫和被叫用户标识， 根据被叫用户注册的网络 类型转换为相应的用户标识格式， 作为转换后非 IMS消息的主叫和被叫用户 标识；
将主叫用户发送的 SIP格式消息作为非 IMS消息的消息体， 整体封装在 非 IMS消息内；或者将主叫用户发送的 SIP格式消息拆分成消息头和消息体， 将拆分后的消息头转换为非 IMS消息的消息头， 将拆分后的消息体转换为非 IMS消息的消息体， 重新对转换后的消息进行封装。
如果主叫用户发送的 SIP消息长度超出非 IMS消息规定的最大长度， 则 61 根据非 IMS消息规定的长度将 SIP消息拆分成多条非 IMS消息， 在拆分的多 条非 IMS消息的非最后一条消息中设置消息未传送完全标记或相应的顺序号 码， 并在最后一条消息中设置传送完全标记。
根据本发明的上述方法，消息接收端根据所述标记，将拆分的多条非 IMS 消息合并为一条消息。
所述将主叫用户发送的非 IMS消息转换为 IMS消息格式， 具体方法为： 提取非 IMS消息主叫和被叫用户标识， 并转换为 SIP消息系统可以识别 的 SIP URI格式， 作为转换后 SIP 消息的主叫和被叫用户标识；
将主叫用户发送的非 IMS消息作为 SIP消息的消息体，整体封装在 SIP消 息内； 或将主叫用户发送的非 IMS消息拆分成消息头和消息体， 将拆分后的 消息头转化为 SIP消息的消息头， 将拆分后的消息体转换为 SIP 消息的消息 体， 重新对转换后的消息进行封装。
如果主叫用户发送的非 IMS消息长度超出 SIP消息规定的最大长度， 则 根据 SIP消息规定的长度将非 IMS消息拆分成多条 SIP消息， 在拆分的多条 SIP消息的非最后一条消息中设置消息未传送完全标记或相应的顺序号码，并 在最后一条消息中设置传送完全标记。
根据本发明的上述方法， 消息接收端根据所述标记， 将拆分的多条 SIP 消息合并为一条消息。
根据本发明的上述方法， 所述 IMS消息和非 IMS消息格式转换由一个独 立设置的消息应用服务器实现； 或者由设置于 IP消息网关或短消息中心的一 个功能模块实现。
根据本发明的上述方法， 在发送消息进行格式转换后， 若被叫用户返回 状态报告， 则通过所述消息应用服务器或功能模块将返回的状态报告转换为 主叫用户能接收的格式消息， 并获取主叫和被叫用户标识， 根据主叫用户注 册的网络类型转换为相应的用户标识格式。
所述将状态报告转换为主叫用户能接收的格式消息， 具体方法为： 定义一条新的 SIP响应消息对 SIP消息进行响应， 该新的 SIP响应消息 所携带的参数参照移动应用部分（MAP ) 消息的参数定义； 所述消息应用服 务器或功能模块提取被叫用户返回的传送状态相关数据， 转换为相应的 MAP 消息参数， 并将该新的 SIP响应消息转换为 MAP格式状态报告消息； 或提取 被叫用户返回的 MAP格式的状态报告数据转换为该新的 SIP响应消息参数， 并将 MAP格式消息响应转换为该新的 SIP响应消息。
所述将状态 4艮告转换为主叫用户能接收的格式消息， 具体方法还可以是： 使用现有 SIP消息， 并设置标识， 将带有设置标识的 SIP消息作为状态 报告消息； 被叫用户终端在带有该设置标识的 SIP消息体中携带与 MAP格式 的状态报告参数相关的信息， 所述消息应用服务器或功能模块提取该带有设 置标识的 SIP消息内容， 并根据该消息内容转换为携带相应参数的 MAP格式 的状态报告消息； 或提取被叫用户返回的 MAP格式的状态报告数据转换为带 有设置标识的 SIP消息内容。
根据本发明的上述方法， 若被叫用户返回的状态报告为 MAP格式， 则由 所述消息应用服务器或功能模块提取该 MAP格式的状态报告数据， 转换为与 之状态相对应的现有 SIP响应消息。
本发明另提供一种消息转换系统， 包括： 消息接收判断装置和消息应用 服务器；
所述消息接收判断装置与主叫侧网络的消息发送 /接收实体相连接， 接收 主叫侧的呼叫消息， 并根据被叫用户能接收的消息格式判断是否需要进行消 息格式转换； 若需要进行消息格式转换， 则将该呼叫消息转发到消息应用服 务器处理；
所述消息应用服务器与被叫侧网络的消息发送 /接收实体相连接， 实现 IMS格式消息和非 IMS格式消息转换，将进行格式转换后的呼叫消息通过被叫 侧网络的消息发送 /接收实体转发给被叫； 并接收被叫返回的发送状态报告消 息， 进行相应格式转换后， 通过消息接收判断装置和主叫侧网络的消息发送 / 接收实体返回给主叫。
所述消息应用服务器包括： 消息格式转换模块和消息发送 /状态报告接收 模块；
所述消息格式转换模块与所述消息接收判断装置和消息发送 /状态报告 接收模块分别连接， 实现 IMS格式消息和非 IMS格式消息转换；
所述消息发送 /状态报告接收模块与被叫侧网络的消息发送 /接收实体相 连接， 发送格式转换后的呼叫消息到被叫侧网络的消息发送 /接收实体， 由被 叫侧网络的消息发送 /接收实体将呼叫消息转发给被叫； 并接收被叫返回的发 送状态报告消息， 转发到消息格式转换模块进行消息格式转换后， 通过所述 消息接收判断装置和主叫侧网络的消息发送 /接收实体返回给主叫。
所述消息应用服务器为一个独立设置的网络实体； 或者
为设置于 IP消息网关或短消息中心的一个功能模块。
本发明有益效果如下：
根据本发明提供的方法， 能将 IMS消息转换成非 IMS消息格式， 发送给 用户， 或将非 IMS消息转换成 IMS消息发送给用户； 同时， 实现被叫用户返 回的非 IMS消息响应转换成 IMS格式消息返回给主叫， 或将被叫用户返回的 IMS 消息响应转换成主叫能接收的消息格式， 使主被叫用户在不能同时使用 IMS业务时， 也能实现消息互通。 附图说明
图 la、 图 lb为本发明主叫用户发起呼叫的信令流程图；
图 2为应用服务器对被叫标识进行解析的步骤流程图；
图 3为应用服务器接收到状态报告消息的处理步骤流程图；
图 4为被叫侧网络接收到 IMS消息后的消息转换及传送流程图之一； 图 5为被叫侧网 矣收到 IMS消息后的消息转换及传送流程图之二； 图 6为被叫侧网络接收到非 IMS消息后的消息转换及传送流程图之一； 图 Ί为被叫侧网 矣收到非 IMS消息后的消息转换及传送流程图之二； 图 8为本发明的消息转换系统结构示意图。 具体实施方式
本发明提供的消息转换方法， 应用于使用 IMS消息和使用非 IMS消息的 用户终端进行消息互通。 本发明方法包括：
当网络接收到主叫用户向被叫发送的 IMS消息时， 若判断出被叫用户当 前不能接收 IMS消息， 则将主叫用户发送的 IMS消息转换为被叫用户当前能 接收的非 IMS消息格式， 发送给被叫用户；
当网络接收到主叫用户向被叫用户发送的非 IMS消息时， 若判断出被叫 用户当前能接收 IMS消息，则将主叫用户发送的非 IMS消息转换为 IMS消息 格式， 发送给被叫用户。
所述 IMS消息和非 IMS消息格式转换由一个独立设置的消息应用服务器 实现； 或者由设置于 IP消息网关或短消息中心的一个功能模块实现。
在发送消息进行格式转换后， 若被叫用户返回状态 4艮告， 则通过所述消 息应用服务器或功能模块将返回的状态报告转换为主叫用户能接收的格式消
IMS消息同非 IMS消息互通时格式相互转换方式如下：
1. 将 SIP Message格式消息转换为非 IMS格式消息，具体转换方式包括：
( 1 )将主叫用户发送的 SIP Message格式消息作为非 IMS消息的消息体， 整体封装在非 IMS消息内， 并提取主、 被叫用户标识， 根据登记的网络类型 转化为非 IMS消息系统可以识别的 E.164或 NAI (网络接入标识）等适合用 户登记网络相应的用户标识格式作为非 IMS消息的主、 被叫用户标识。
( 2 )将 SIP Message拆分， 提取消息头和消息体， 重新对消息进行转化 封装： 将 SIP Message消息头转化为非 IMS消息头， SIP Message消息体转换 为非 IMS消息体。并将主、被叫用户标识，根据登记的网絡类型转化为非 IMS 消息系统可以识别的 E.164或 NAI (网络接入标识）等适合用户登记网络相应 的用户标识格式作为非 IMS消息的主、 被叫用户标识。
如果 SIP Message消息长度超出非 IMS消息规定的最大长度， 则根据非 IMS消息规定的长度将 SIP Message消息拆分， 转化成多条非 IMS消息， 在 拆分的多条非 IMS消息的非最后一条消息中设置消息未传送完全标记或相应 的顺序号码， 表示消息尚未完全传送， 还有后续消息， 并在最后一条消息中 设置传送完全标记表示消息传送完毕。 消息接收终端在可能的情况下可以根 据未传送完全标记和最后一条新封装消息中设置传送完全标记将消息合并为 一条消息。
2.将非 IMS格式消息转换为 SIP Message格式消息，具体转换方式包括： ( 1 )、 将非 IMS消息作为 SIP Message消息的消息体， 整体封装在 SIP Message内， 并提取非 IMS消息主、 被叫用户标识， 转化为 SIP Message消息 系统可以识别的 SIP URI格式作为 SIP Message的主、 被叫用户标识。
( 2 )、 将非 IMS消息拆分， 提取消息头和消息体， 重新对消息进行转化 封装：将非 IMS消息头转化为 SIP Message消息头，非 IMS消息体转换为 SIP Message消息体。 并提取非 IMS消息主、 被叫用户标识， 转化为 SIP Message 消息系统可以识别的 SIP UR [格式作为 SIP Message的主、 被叫用户标识。
如果非 IMS消息长度超出 SIP Message消息规定的最大长度， 则根据 SIP Message消息规定的长度将非 IMS消息拆分， 转化成多条 SIP Message消息， 在新封装消息的非最后一条消息中设置消息未传送完全标记或相应的顺序号 码， 表示消息尚未完全传送， 还有后续消息， 并在最后一条新封装消息中设 置传送完全标记表示消息传送完毕。 消息接收终端在可能的情况下可以根据 未传送完全标记和最后一条新封装消息中设置传送完全标记将消息合并为一 条消息。
在 IMS消息同非 IMS消息互通过程中， 状态报告的转换可以采用如下方 式：
( 1 )定义一条新的 SIP消息作为响应消息， 该新的 SIP响应消息所携带 的参数参照移动应用部分（MAP ) 消息的参数定义； 所述消息应用服务器或 功能模块提取被叫用户返回的传送状态相关数据， 转换为相应的 MAP 消息参 数， 并将该新的 SIP响应消息转换为 MAP格式状态报告消息； 或提取被叫用 户返回的 MAP格式的状态报告数据转换为该新的 SIP响应消息参数， 并将该 MAP格式消息响应转换为新的 SIP响应消息。
( 2 )使用现有 SIP消息， 并设置标识， 将带有设置标识的 SIP消息作为 状态报告消息； 被叫用户终端在带有该设置标识的 SIP 消息体中携带与 MAP 格式的状态报告参数相关的信息， 所述消息应用服务器或功能模块提取该带 有设置标识的 SIP 消息内容， 并根据该消息内容转换为携带相应参数的 MAP 格式的状态报告消息； 或提取被叫用户返回的 MAP格式的状态报告数据转换 为带有设置标识的 SIP消息内容。
( 3 )若被叫用户返回的状态报告为 MAP格式， 则由所述消息应用服务 器或功能模块提取该 MAP格式的状态报告数据， 转换为与之状态相对应的现 有 SIP响应消息。
下面结合附图， 对本发明提供的上述方法加以详细描述。
如图 la、 图 lb所示， 为主叫用户发送 IMS消息后的网络处理流程， 包 括：
UE1生成待发送的即时消息并向服务-呼叫会话控制功能实体（S-CSCF1 ) 发送 SIP Message消息； S-CSCF1进行业务控制， 对被叫用户标识进行判断， 若被叫用户为 SIP URI (统一资源定位标识） 格式， 则进行正常的 IMS MESSAGE发送过程； 若被叫用户标识为 TEL URI格式， 则将 SIP Message 消息转发至应用服务器 IP 消息网关 （ IP-Message-GW ) ; 应用服务器 IP-Message-GW对被叫标识进行 ENUM (电话号码到 URI的映射）解析， 如 图 2所示， 将被叫用户标识转换为 SIP URI格式：
a. 若转化成功， 则将被叫用户标识转换为 SIP URI格式的消息返回给 S-CSCF1 , S-CSCF1根据被叫用户 SIP URI寻址到被叫的 IMS网络并将消息 转发至被叫 IMS网络， 如图 la所示的步驟 1-8。 由 S-CSCF1将 SIP消息转发 至被叫 IMS网络与现有技术相同， 这里不再详细介绍；
b. 否则， 将被叫用户标识为 TEL URI格式转换为 E.164格式， 并根据消 息中携带的内容将 Message格式转换为短消息业务（ SMS )或多媒体消息业 务（MMS ) 消息格式进行重新封装， 然后将转换后的消息转发至传统的短消 息中心或 MMS消息中心， 如图 lb所示； 若应用服务器 IP-Message-GW接收 到被叫返回的状态报告消息为非 IMS消息类型， 例如， 发送的是 MAP格式 的 SMS消息， 则返回的消息报告为 MAP的传送报告 ( delivery report )消息， 应用服务器 IP-Message-GW判断是否需要通过 IMS消息返回给 UE1 , 如图 3 所示，如果需要，则将非 IMS格式的报告消息转化成适用于 IMS的状态报告， 并发送给 UE1注册的 S-CSCF1 , 否则 #文其它处理。
通过以上描述， 在主叫通过 IMS即时消息发送方式发送消息时， 若被叫 用户能够通过 IMS网络正常接收消息， 消息终止流程为现有技术的 IMS即时 消息流程； 当被叫用户登记在其它非 IMS网络， 且消息需要通过被叫用户登 记网络传送时， 则需要进行 IMS消息格式同非 IMS消息格式间的转换， 以保 证被叫用户能够正确接收到消息。 消息的格式转换功能可能位于未注册业务 的消息应用服务器上， 也可能位于 IP消息网关上， 具体过程分别由图 4和图 5流程描述。
如图 4所示， 为消息格式转换功能位于未注册业务的消息应用服务器上 时的消息传送过程， 包括下列步骤：
1、 查询-呼叫会话控制功能实体 （I-CSCF )接收到主叫侧发送的 SIP MESSAGE消息；
2、 I-CSCF 向归属签约用户服务器 （ HSS ) 发送 Cx 位置请求 ( Cx-LocQuery ),请求被叫用户 UE2的 S-CSCF;如果 HSS查询出 UE2是 IMS 用户， 但没有注册到 IMS网络中， 且该用户登记了未注册业务（状态）， 则根 据用户去注册前的位置和 Cx-LocQueiy请求中的要求， HSS向 I-CSCF返回用 户去注册前登记的 S-CSCF或符合 Cx-LocQuery请求的一个 S-CSCF 集； I-CSCF根据 HSS发来的用户去注册前的 S-CSCF或 S-CSCF集， 选择一个适 当的 S-CSCF2;
3、 I-CSCF将 SIP Message消息转发给选定的 S-CSCF2;
4、 S-CSCF2接收到消息后， 发送 Cx-Put/Cx-Pull (携带公共用户标识， 06 001661
S-CSCF名称）给 HSS, HSS保存未登记公共用户标识的 S-CSCF2名称； HSS 向 S-CSCF2返回 Cx-Put Resp/Cx-Pull Resp (携带用户信息）， S-CSCF2保存 该用户的公共用户标识等用户信息；
5、 S-CSCF2调用适合于该用户未注册业务的业务逻辑；
6、 S-CSCF2将消息转发给未注册业务的消息应用服务器；
7、 未注册业务的消息应用服务器判断是否需要通过其它方式转发消息， 如果不需要转发， 则存储消息， 等待用户注册 IMS的通知；
如果需要转发，未注册业务的消息应用服务器向 HSS发起路由查询请求， 提取路由信息， 在路由查询请求中指示消息应用服务器支持的消息发送形式， 如可以接收到并处理 CS、 PS和 /或 WLAN等基于 IP的消息传送； 若被叫用 户在其它网络上（CS域、 PS域、 I-WLAN或 Wimax等）注册， 则 HLR/HSS 根据指示能力向消息应用服务器返回以优先级排序的用户注册网络地址列 表， 其中可能包括移动业务交换中心（MSC )、 服务 GPRS支持节点（SGSN ) 和 /或 IP-MESSAGE-GW地址；
8、 未注册业务的消息应用服务器根据用户注册网络地址列表， 选择相应 的传输网络， 将 SIP Message格式消息转换为相应的消息格式， 将被叫用户的 用户标识根据登记的网络类型转换为 E.164或网络接入标识（NAI )等适合用 户登记网络相应的用户标识格式， 对消息进行重新封装；
9、 未注册业务的消息应用服务器将消息发送给被叫用户登记的消息网 元， 如 MSC、 SGSN或 IP-MESSAGE-GW;
10、 被叫用户登记的消息网元将消息转发给被叫用户终端 UE2;
11、 被叫用户终端 UE2接收到消息后返回接收成功状态报告；
12、 被叫用户登记的消息网元向消息应用服务器返回接收成功状态报告；
13、 未注册业务的消息应用服务器接收到状态报告后， 将该状态报告转 换为适当的 SIP确认响应消息；
14、 S-CSCF2向 I-CSCF2返回适当的确认响应消息；
15、 I-CSCF2向主叫网络返回适当的确认响应消息。 其中， 步驟 13-15也可能是在消息应 服务器接收 S-CSCF2消息后就返 回确认响应消息。
如图 5所示，为消息格式转换功能位于 IP消息网关上时的消息传送过程， 包括下列步骤：
1—7、 与图 4的 1-7步骤相同， 不重述；
8、如果未注册业务的消息应用服务器选择通过 IP消息网关进行消息的转 发， 则将消息直接转发至 IP消息网关；
9、 IP消息网关将 SIP Message格式消息转换为被叫当前注册网络的相应 的消息格式， 并将被叫用户的用户标识才艮据注册的网络类型转换为 E.164或 NAI等适合用户注册网络的相应用户标识格式， 对消息进行重新封装；
10、 IP消息网关将转换后的消息转发给被叫用户；
11、 被叫用户终端 UE2接收到消息后返回接收成功状态报告;
12、 IP消息网关接收到消息状态才艮告后， 将该状态报告转换为 SIP确认 响应消息；
13、 IP消息网关向未注册业务的消息应用服务器返回转换后的 SIP确认 响应消息；
14、 未注册业务的消息应用^^务器向 S-CSCF2返回确认响应消息；
15、 S-CSCF2向 I-CSCF2返回确认响应消息;
16、 I-CSCF2向主叫网络返回确认响应消息。
其中， 步骤 14-16也可能是在消息应用服务器接收 S-CSCF2消息后就返 回确认响应消息。
如果在主叫发起业务呼叫过程中， 被叫的用户标识为 TEL URI格式且应 用服务器 IP-MESSSAGE-GW进行 ENUM查询无法将 TEL URI转换为 SIP URI格式， 则应用服务器 IP-MESSSAGE-GW将被叫用户标识为 TEL URI格 式转换为 E.164格式， 并根据消息中携带的内容将消息格式转换为 SMS或 MMS 消息格式进行重新封装， 然后将转换后的消息转发至传统的短消息或 MMS消息中心， 按现有技术中的短消息或多媒体消息的传送流程处理。 若消息的被叫用户是 IMS注册终端， 而消息发起的主叫用户为非 IMS用 户， 如 CS域用户， 发起的消息为 MAP格式传统的短消息或 MMS消息， 为 了保证消息顺利发送给被叫用户， 需要将 MAP格式传统的短消息或 MMS消 息转换为被叫用户可以接收的 IMS消息格式， 这种格式转换的功能可能位于 消息应用服务器上， 也可能位于 IP-MESSAGE-GW上， 消息的传输处理流程 如图 6、 图 7所示。
图 6为消息格式转换功能位于一个消息应用服务器上， 其消息传送流程 包括：
1、 用户 端进行正常的注册 /重注册过程；
2、 短消息业务中心 （SM-SC )将被叫用户的短消息转发给短消息业务- 移动交换中心网关 （SMS-GMSC );
3、 SMS-GMSC向 HLR/HSS提取路由信息时应指示 SMS-GMSC支持 IP 消息； 如果被叫用户登记 IMS业务， HLR/HSS根据指示能力向 SMS-GMSC 返回应用 良务器地址；
4、 SMS-GMSC向应用服务器发送短消息， 短消息发送形式同向 MSC或 SGSN传送短消息相同， 携带目标 UE的 MSISDN (移动台国际 ISDN号码：)；
5、 应用服务器利用本地数据库（或者查询其它数据库或转换设备等）将 目标 UE的 MSISDN转换为 UE的 SIP URI,并将短消息转换为 SIP MESSAGE 格式；
6、 应用服务器将转换后的消息通过 SIP MESSAGE发送给 S-CSCF;
7、 S-CSCF将 SIP MESSAGE转发给 UE;
8、 UE向 S-CSCF返回 200 OK响应；
9、 S-CSCF向应用服务器返回 200 OK响应；
10、 UE向 S-CSCF发送 SIP MESSGAE消息发送状态报告；
11、 S-CSCF向应用服务器发送状态报告；
12、 应用服务器向 S-CSCF返回 200 OK确认消息传送报告；
13、 S-CSCF向 UE返回 200 OK确认消息传送报告； 14、应用服务器根据 SIP MESSGAE消息传送状态报告内容，转换为 MAP 消息传输状态报告；
15、 应用服务器将转换后的 MAP消息传输艮告发送给 SMS-GMSC;
16 SMS-GMSC将消息传送状态报告发送给 HSS;
17 SMS-GMSC将消息传送报告发送给短消息中
上述流程中的应用服务器可能为一个独立的功能实体， 也可能是其它应 用服务器的一个功能模块。
图 7为消息格式转换功能位于 IP-MESSAGE-GW上， 其消息传送流程包 括：
1、 用户终端进行正常的注册 /重注册过程；
2、 短消息业务中心将被叫用户的短消息转发给 SMS-GMSC;
3 SMS-GMSC向 HLR/HSS提取路由信息时应指示 SMS-GMSC支持 IP 消息； 如果被叫用户登记 IMS业务， HLR/HSS根据指示能力向 SMS-GMSC 返回 IP-MESSAGE-GW地址；
4 SMS-GMSC向 IP-MESSAGE-GW发送短消息，形式同向 MSC或 SGSN 传送短消息相同， 携带目标 UE的 MSISDN;
5 IP-MESSAGE-GW利用本地数据库将目标 UE的 MSISDN转换为 UE 的 SIP URI, 并将短消息转换为 SIP MESSAGE格式；
6、 IP-MESSAGE-GW 将转换后的消息通过 SIP MESSAGE 发送给 S-CSCF;
7 S-CSCF将 SIP MESSAGE转发给 UE;
8 UE向 S-CSCF返回 200 OK响应；
9 S-CSCF向 IP-MESSAGE-GW返回 200 OK响应；
10 UE向 S-CSCF发送 SIP MESSGAE消息发送状态艮告；
11 S-CSCF向 IP-MESSAGE-GW发送状态报告；
12 IP-MESSAGE-GW向 S-CSCF返回 200 OK确认消息传送报告；
13 S-CSCF向 UE返回 200 OK确认消息传送报告； 14、 IP-MESSAGE-GW根据 SIP MESSGAE消息传送状态报告内容， 转 换为 MAP消息传输状态报告；
15、 IP-MESSAGE-GW 将转换后的 MAP 消息传输报告发送给 SMS-GMSC;
16、 SMS-GMSC将消息传送报告状态报告给 HSS;
17、 SMS-GMSC将消息传送报告发送给短消息中心。
根据本发明的上述方法， 本发明另提供一种消息转换系统， 如图 8所示， 包括： 消息接收判断装置和消息应用服务器；
所述消息接收判断装置与主叫侧网络的消息发送 /接收实体相连接， 接收 主叫侧的呼叫消息。 若主叫所在网络为 IMS网络， 则主叫侧网絡的消息发送 / 接收实体可以是 S-CSCF或 I - CSCF; 若主叫所在网络为 PS或 CS网络， 则消息 发送 /接收实体可以是短消息业务 -移动交换中心网关（SMS-GMSC )等。
消息接收判断装置根据被叫用户能接收的消息格式判断是否需要进行消 息格式转换； 若需要进行消息格式转换， 则将该呼叫消息转发到消息应用服 务器处理。 具体包括：
消息接收判断装置接收到主叫侧发送的 IMS消息时， 若判断出被叫用户 当前不能接收 IMS消息， 则将该 IMS消息发送到消息应用服务器进行消息格 式转换， 转换成被叫用户当前能接收的消息格式；
消息接收判断装置接收到主叫用户向被叫用户发送的非 IMS消息时， 若 判断出被叫用户当前能接收 IMS消息， 则将该非 IMS消息发送到消息应用服 务器， 转换成 IMS格式消息。
所述消息应用服务器与被叫侧网络的消息发送 /接收实体相连接， 实现 IMS格式消息和非 IMS格式消息转换，将进行格式转换后的呼叫消息通过被叫 侧网络的消息发送 /接收实体转发给被叫； 若被叫所在网络为 IMS网络， 则其 消息发送 /接收实体可以是 S-CSCF或 I-CSCF; 若被叫所在网络为 PS或 CS网 络， 则消息发送 /接收实体可以是短消息业务-移动交换中心网关 ( SMS-GMSC )等。 消息应用服务器还接收被叫返回的发送状态报告消息， 进行相应格式转 换后， 通过消息接收判断装置和主叫侧网络的消息发送 /接收实体返回给主 叫。
消息应用服务器可以进一步包括： 消息格式转换模块和消息发送 /状态报 告接收模块。
消息格式转换模块与消息接收判断装置和消息发送 /状态报告接收模块 分别连接， 实现 IMS消息格式和非 IMS消息格式转换。
消息发送 /状态报告接收模块与被叫侧网絡的消息发送 /接收实体相连 接， 发送格式转换后的呼叫消息到被叫侧网絡的消息发送 /接收实体， 由被叫 侧网络的消息发送 /接收实体将呼叫消息转发给被叫； 并接收被叫返回的发送 状态报告消息， 转发到消息格式转换模块进行消息格式转换后， 通过消息接 收判断装置和主叫侧网络的消息发送 /接收实体返回给主叫。
所述消息应用服务器为一个独立设置的网络实体； 或者为设置于 IP消息 网关或短消息中心的一个功能模块。
显然， 本领域的技术人员可以对本发明进行各种改动和变型而不脱离本 发明的精神和范围。 这样， 倘若本发明的这些修改和变型属于本发明权利要 求及其等同技术的范围之内， 则本发明也意图包含这些改动和变型在内。

Claims

权 利 要 求
1、 一种消息转换方法， 其特征在于包括：
当网络接收到主叫用户向被叫用户发送的 IMS消息时， 若判断出被叫用 户当前不能接收 IMS消息， 则将主叫用户发送的 IMS消息转换为被叫用户当 前能接收的非 IMS消息格式， 发送给被叫用户； 或者
当网络接收到主叫用户向被叫用户发送的非 IMS消息时， 若判断出被叫 用户当前能接收 IMS消息，则将主叫用户发送的非 IMS消息转换为 IMS消息 格式， 发送给被叫用户。
2、 如权利要求 1所述的方法， 其特征在于， 网络将被叫用户返回的消息 响应， 转换成主叫用户能接收的格式消息发返回给主叫用户。
3、 如权利要求 1所述的方法， 其特征在于， 若主叫用户发送的 IMS消息 格式采用会话初始协议 SIP消息格式， 则将主叫用户发送的 SIP格式消息转 换为被叫用户能接收的非 IMS格式消息， 具体方法为：
提取 SIP格式消息中的主叫和被叫用户标识， 根据被叫用户注册的网络 类型转换为相应的用户标识格式， 作为转换后非 IMS消息的主叫和被叫用户 标识；
将主叫用户发送的 SIP格式消息作为非 IMS消息的消息体， 整体封装在 非 IMS消息内；或者将主叫用户发送的 SIP格式消息拆分成消息头和消息体， 将拆分后的消息头转换为非 IMS消息的消息头， 将拆分后的消息体转换为非 IMS消息的消息体， 重新对转换后的消息进行封装。
4、 如权利要求 3所述的方法， 其特征在于， 如果主叫用户发送的 SIP消 息长度超出非 IMS消息规定的最大长度，则根据非 IMS消息规定的长度将 SIP 消息拆分成多条非 IMS消息， 在拆分的多条非 IMS消息的非最后一条消息中 设置消息未传送完全标记或相应的顺序号码， 并在最后一条消息中设置传送 完全标记。
5、 如权利要求 4所述的方法， 其特征在于， 还包括： 消息接收端根据所 述标记， 将拆分的多条非 IMS消息合并为一条消息。
6、如权利要求 1所述的方法，其特征在于，所述将主叫用户发送的非 IMS 消息转换为 IMS消息格式， 具体方法为：
提取非 IMS消息主叫和被叫用户标识， 并转换为 SIP消息系统可以识别 的 SIP U I格式， 作为转换后 SIP 消息的主叫和被叫用户标识；
将主叫用户发送的非 IMS消息作为 SIP消息的消息体，整体封装在 SIP 消 息内； 或将主叫用户发送的非 IMS消息拆分成消息头和消息体， 将拆分后的 消息头转化为 SIP消息的消息头， 将拆分后的消息体转换为 SIP 消息的消息 体， 重新对转换后的消息进行封装。
7、 如权利要求 6所述的方法， 其特征在于， 如果主叫用户发送的非 IMS 消息长度超出 SIP消息规定的最大长度,则根据 SIP消息规定的长度将非 IMS 消息拆分成多条 SIP消息，在拆分的多条 SIP消息的非最后一条消息中设置消 息未传送完全标记或相应的顺序号码， 并在最后一条消息中设置传送完全标 记。
8、 如权利要求 7所述的方法， 其特征在于， 还包括： 消息接收端根据所 述标记， 将拆分的多条 SIP消息合并为一条消息。
9、 如权利要求 1-8所述任意权项所述的方法， 其特征在于， 所述 IMS消 息和非 IMS消息格式转换由一个独立设置的消息应用服务器实现； 或者
由设置于 IP消息网关或短消息中心的一个功能模块实现。
10、 如权利要求 9所述的方法， 其特征在于， 在发送消息进行格式转换 后， 若被叫用户返回状态报告， 则通过所述消息应用服务器或功能模块将返 回的状态报告转换为主叫用户能接收的格式消息， 并获取主叫和被叫用户标 识， 根据主叫用户注册的网络类型转换为相应的用户标识格式。
11、 如权利要求 10所述的方法， 其特征在于， 所述将状态报告转换为主 叫用户能接收的格式消息， 具体方法为：
定义一条新的 SIP响应消息对 SIP消息进行响应， 该新的 SIP响应消息 所携带的参数参照移动应用部分（MAP ) 消息的参数定义； 所述消息应用服 务器或功能模块提取被叫用户返回的传送状态相关数据， 转换为相应的 MAP 消息参数， 并将该新的 SIP响应消息转换为 MAP格式状态艮告消息； 或提取 被叫用户返回的 MAP格式的状态报告数据转换为该新的 SIP响应消息参数， 并将 MAP格式消息响应转换为该新的 SIP响应消息。
12、 如权利要求 10所述的方法， 其特征在于， 所述将状态报告转换为主 叫用户能接收的格式消息， 具体方法为：
使用现有 SIP消息， 并设置标识， 将带有设置标识的 SIP消息作为状态 报告消息； 被叫用户终端在带有该设置标识的 SIP消息体中携带与 MAP格式 的状态报告参数相关的信息， 所述消息应用服务器或功能模块提取该带有设 置标识的 SIP消息内容， 并根据该消息内容转换为携带相应参数的 MAP格式 的状态 4艮告消息； 或提取被叫用户返回的 MAP格式的状态报告数据转换为带 有设置标识的 SIP消息内容。
13、 如权利要求 10所述的方法， 其特征在于， 若被叫用户返回的状态报 告为 MAP格式，则由所述消息应用服务器或功能模块提取该 MAP格式的状态 报告数据， 转换为与之状态相对应的现有 SIP响应消息。
14、 一种消息转换系统， 其特征在于， 包括： 消息接收判断装置和消息 应用服务器；
所述消息接收判断装置与主叫侧网络的消息发送 /接收实体相连接， 接收 主叫侧的呼叫消息， 并根据被叫用户能接收的消息格式判断是否需要进行消 息格式转换； 若需要进行消息格式转换， 则将该呼叫消息转发到消息应用服 务器处理；
所述消息应用服务器与被叫侧网络的消息发送 /接收实体相连接， 实现 IMS格式消息和非 IMS格式消息转换，将进行格式转换后的呼叫消息通过被叫 侧网络的消息发送 /接收实体转发给被叫； 并接收被叫返回的发送状态报告消 息， 进行相应格式转换后， 通过消息接收判断装置和主叫侧网络的消息发送 / 接收实体返回给主叫。
15、如权利要求 14所述的系统，其特征在于， 所述消息应用服务器包括： 消息格式转换模块和消息发送 /状态报告接收模块；
所述消息格式转换模块与所述消息接收判断装置和消息发送 /状态报告 接收模块分别连接， 实现 IMS格式消息和非 IMS格式消息转换；
所述消息发送 /状态报告接收模块与被叫侧网络的消息发送 /接收实体相 连接， 发送格式转换后的呼叫消息到被叫侧网络的消息发送 /接收实体， 由被 叫侧网络的消息发送 /接收实体将呼叫消息转发给被叫； 并接收被叫返回的发 送状态报告消息， 转发到消息格式转换模块进行消息格式转换后， 通过所述 消息接收判断装置和主叫侧网络的消息发送 /接收实体返回给主叫。
16、 如权利要求 14所述的系统， 其特征在于： 所述消息应用服务器为一 个独立设置的网络实体； 或者为设置于 IP消息网关或短消息中心的一个功能 模块。
PCT/CN2006/001661 2005-07-14 2006-07-13 Procédé et système pour convertir un message WO2007006235A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
JP2008520697A JP5080465B2 (ja) 2005-07-14 2006-07-13 メッセージを変換するための方法及びシステム
EP06761414A EP1903724A4 (en) 2005-07-14 2006-07-13 METHOD AND SYSTEM FOR CONVERTING A MESSAGE

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CNA2005100839436A CN1897578A (zh) 2005-07-14 2005-07-14 一种消息转换方法与系统
CN200510083943.6 2005-07-14

Publications (1)

Publication Number Publication Date
WO2007006235A1 true WO2007006235A1 (fr) 2007-01-18

Family

ID=37609955

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2006/001661 WO2007006235A1 (fr) 2005-07-14 2006-07-13 Procédé et système pour convertir un message

Country Status (4)

Country Link
EP (1) EP1903724A4 (zh)
JP (1) JP5080465B2 (zh)
CN (1) CN1897578A (zh)
WO (1) WO2007006235A1 (zh)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2008120161A2 (en) * 2007-03-30 2008-10-09 Telefonaktiebolaget L M Ericsson (Publ) Apparatus and method for interfacing mms and ims messaging systems
EP2154846A1 (en) * 2007-10-22 2010-02-17 Huawei Technologies Co., Ltd. Method and apparatus for transferring message between heterogeneous networks
CN111404875A (zh) * 2020-02-19 2020-07-10 广州广哈通信股份有限公司 Sip调度终端的协议增强方法、装置和调度系统

Families Citing this family (28)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2081348A4 (en) * 2006-11-15 2009-12-09 Huawei Tech Co Ltd MESSAGE INTERFUNCTION METHOD, SYSTEM, ENTITY AND METHOD OF MESSAGE DISTRIBUTION REPORT PROCESSING, SYSTEM, ENTITY, TERMINAL FOR MESSAGE INTERFUNCTION
CN101291274B (zh) * 2007-04-16 2012-03-21 华为技术有限公司 一种确定路由网关的方法、网络及装置
CN101316435B (zh) 2007-05-31 2012-08-08 华为技术有限公司 呼叫控制的方法和ims的电路交换控制装置及终端设备
CN101370172B (zh) * 2007-08-13 2012-04-25 华为技术有限公司 不同类型的消息业务通信的处理方法、系统和设备
CN101374118B (zh) * 2007-08-23 2015-07-29 华为技术有限公司 一种消息互连的方法、系统及装置
CN100596238C (zh) * 2007-09-12 2010-03-24 华为技术有限公司 多媒体通信方法及网元设备
CN101409861B (zh) * 2007-10-08 2010-09-22 华为技术有限公司 特征和寻址子系统及用户登记方法、呼叫方法和漫游方法
CN101483581A (zh) * 2008-01-09 2009-07-15 华为技术有限公司 一种访问非sip资源的方法、系统和设备
US8831032B2 (en) * 2008-03-05 2014-09-09 Telefonaktiebolaget L M Ericsson (Publ) SIP-HTTP application correlator
CN101552721B (zh) * 2008-04-03 2013-02-27 中兴通讯股份有限公司 一种融合业务系统及其业务实现方法
JP5063530B2 (ja) * 2008-08-22 2012-10-31 Ｋｄｄｉ株式会社 Ｉｍｓネットワークを介したｓｉｐ非対応サーバへのアクセス方法及びシステム
KR101008429B1 (ko) 2008-11-26 2011-01-14 주식회사 케이티 메시지 포맷 변환 방법 및 그 장치
US20100331021A1 (en) * 2009-06-30 2010-12-30 Bushnell William J Method and system for interworking between instant messaging service and short message service
JP5568348B2 (ja) * 2010-03-24 2014-08-06 株式会社 ネクストジェン 通信制御装置及び通信制御システム
US20110319075A1 (en) * 2010-06-25 2011-12-29 Alok Sharma Universal mobile manager interworking for short message service feature parity
JP5682176B2 (ja) * 2010-08-16 2015-03-11 沖電気工業株式会社 呼制御信号送信装置、プログラム及び方法
US8935413B2 (en) * 2010-10-26 2015-01-13 Alcatel Lucent Delivery report for text messages in SIP communications
JP5614257B2 (ja) * 2010-11-22 2014-10-29 株式会社リコー 通信装置
CN103067883B (zh) * 2011-10-20 2015-08-19 中国移动通信集团设计院有限公司 一种融合消息业务处理方法、设备以及系统
CN105024908A (zh) * 2014-04-22 2015-11-04 中国电信股份有限公司 一种推送im信息的方法和系统、服务器以及平台
CN105024907A (zh) * 2014-04-22 2015-11-04 中国电信股份有限公司 一种推送im信息的方法和系统、服务器以及平台
CN105207882A (zh) * 2014-06-26 2015-12-30 中兴通讯股份有限公司 消息处理方法及装置
DE102015012569A1 (de) * 2014-10-31 2016-05-04 Intel Corporation Vorrichtung, System und Verfahren zur Unterscheidung zwischen einer IMS-Verbindung und einer Nicht-IMS-Verbindung
CN106211105B (zh) * 2015-04-30 2019-09-06 中国电信股份有限公司 处理短信的方法和系统、及应用服务器
RU2761577C2 (ru) 2015-05-19 2021-12-10 Телефонактиеболагет Л М Эрикссон (Пабл) Способ и система информирования о местоположении сообщения в сети связи
CN106612248A (zh) * 2015-10-21 2017-05-03 深圳市中兴微电子技术有限公司 一种终端的会话方法及装置
CN108024216B (zh) * 2016-10-31 2021-04-23 中国电信股份有限公司 Scef场景下实现信息互通的方法、装置和系统
CN113542512B (zh) * 2021-06-30 2022-12-02 荣耀终端有限公司 呼叫处理系统、方法、电子设备及存储介质

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1267415A (zh) * 1997-08-14 2000-09-20 诺基亚网络有限公司 通信设备的集中管理
US20040054970A1 (en) * 2002-09-16 2004-03-18 International Business Machines Corporation System and method for facilitating XML transactions with MFS-based IMS applications
CN1558689A (zh) * 2004-01-15 2004-12-29 中兴通讯股份有限公司 基于软交换系统的短消息和即时消息业务互通的系统和方法

Family Cites Families (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2002252668A (ja) * 2001-02-23 2002-09-06 Victor Co Of Japan Ltd 通信システム
JP2002354144A (ja) * 2001-05-24 2002-12-06 Victor Co Of Japan Ltd ゲートウェイ及びルータ
WO2003003653A2 (en) * 2001-06-26 2003-01-09 Versada Networks, Inc. Transcoding sms-based streamed messages to sip-based ip signals in wireless and wireline networks
JP2003218936A (ja) * 2002-01-18 2003-07-31 Nissan Motor Co Ltd 可変長メッセージの送受信方法および送受信装置
EP1504620B1 (en) * 2002-05-13 2010-08-25 Markport Limited Control of plmn messaging services in ip domains
US7974295B2 (en) * 2002-07-16 2011-07-05 Nokia Corporation Optimized routing between communication networks
JP2004222156A (ja) * 2003-01-17 2004-08-05 Victor Co Of Japan Ltd 電話システム
US7274943B2 (en) * 2003-01-31 2007-09-25 Nokia Corporation Service subscription in a communication system
GB2398969B (en) * 2003-02-27 2006-07-05 Ericsson Telefon Ab L M Message management
GB2406999A (en) * 2003-10-08 2005-04-13 Orange Personal Comm Serv Ltd SMS telecommunication system
US7761571B2 (en) * 2003-11-25 2010-07-20 Panasonic Corporation SIP service for home network device and service mobility

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1267415A (zh) * 1997-08-14 2000-09-20 诺基亚网络有限公司 通信设备的集中管理
US20040054970A1 (en) * 2002-09-16 2004-03-18 International Business Machines Corporation System and method for facilitating XML transactions with MFS-based IMS applications
CN1558689A (zh) * 2004-01-15 2004-12-29 中兴通讯股份有限公司 基于软交换系统的短消息和即时消息业务互通的系统和方法

Non-Patent Citations (1)

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

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2008120161A2 (en) * 2007-03-30 2008-10-09 Telefonaktiebolaget L M Ericsson (Publ) Apparatus and method for interfacing mms and ims messaging systems
WO2008120161A3 (en) * 2007-03-30 2008-11-27 Ericsson Telefon Ab L M Apparatus and method for interfacing mms and ims messaging systems
EP2154846A1 (en) * 2007-10-22 2010-02-17 Huawei Technologies Co., Ltd. Method and apparatus for transferring message between heterogeneous networks
EP2154846A4 (en) * 2007-10-22 2010-06-30 Huawei Tech Co Ltd METHOD AND APPARATUS FOR MESSAGE TRANSFER BETWEEN HETEROGENEOUS NETWORKS
US8370427B2 (en) 2007-10-22 2013-02-05 Huawei Technologies Co., Ltd. Method and apparatus for transmitting messages between heterogeneous networks
CN111404875A (zh) * 2020-02-19 2020-07-10 广州广哈通信股份有限公司 Sip调度终端的协议增强方法、装置和调度系统

Also Published As

Publication number Publication date
JP5080465B2 (ja) 2012-11-21
EP1903724A1 (en) 2008-03-26
JP2009500973A (ja) 2009-01-08
CN1897578A (zh) 2007-01-17
EP1903724A4 (en) 2008-11-05

Similar Documents

Publication Publication Date Title
WO2007006235A1 (fr) Procédé et système pour convertir un message
TWI411333B (zh) 網際網路協定多媒體系統（ｉｍｓ）及電路交換（ｃｓ）網路中訊息路由的系統及方法
EP1798933B1 (en) A method of realizing message service based on ip network multimedia subsystem
EP2081348A1 (en) Message interworking method, system, entity and message delivery report processing method, system, the entity, terminal for message interworking
US20090075684A1 (en) Apparatus and method for routing message service
US8051208B2 (en) Method, system and apparatus for transferring short messages in an IMS
EP2695457B1 (en) Messaging over a network
EP1863236A2 (en) Method and apparatus for combining voice and multimedia services between CSI terminal and IMS terminal
US20100087215A1 (en) Method, system, and message service interworking module for implementing message service interworking
WO2007128221A1 (fr) Procédé et système d'acheminement et d'adressage de message court
WO2007143924A1 (fr) Procédé et système de délivrance de données de services de messagerie
WO2008022596A1 (fr) Procédé, système et appareil pour la remise de sms en mode de partage dynamique
WO2008025257A1 (fr) Procédé d'intercommunication et système de communication entre différents réseaux
WO2013044882A1 (zh) 一种短消息处理方法和相关系统
WO2008017235A1 (fr) Système, périphérique et procédé de routage sms
WO2007000110A1 (fr) Procede de transmission de message par protocole ip a base de protocole de transfert de message
KR100862744B1 (ko) 이동통신망에서 멀티미디어 서비스 방법 및 이를 실행하는프로그램이 기록된 기록매체
EP2149243A1 (en) Ip multimedia subsystem (ims) and method for routing an http message via an ims
WO2009021453A1 (fr) Procédé, système et dispositif de traitement pour réaliser une communication de service de différents types de messages
WO2007006234A1 (fr) Procédé et appareil de transmission de message
WO2011143985A1 (zh) 紧急消息的实现方法、装置及系统
EP1944945A1 (en) Communication system with transparent subscriber mobility based on group registration
WO2009065362A1 (fr) Procédé, système et dispositif pour le routage d'un message selon un protocole sip dans un réseau traditionnel
CN1941774B (zh) 在网络中实现公共用户标识携带的方法及系统
KR101191601B1 (ko) Ｉｍｓ망 기반의 호 세션 처리를 위한 통신 방법 및 이를 구현한 장치

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application
NENP Non-entry into the national phase

Ref country code: DE

WWE Wipo information: entry into national phase

Ref document number: 2008520697

Country of ref document: JP

WWW Wipo information: withdrawn in national office

Ref document number: DE

WWE Wipo information: entry into national phase

Ref document number: 2006761414

Country of ref document: EP

Ref document number: 356/KOLNP/2008

Country of ref document: IN

WWP Wipo information: published in national office

Ref document number: 2006761414

Country of ref document: EP