Method and Apparatus for Transmitting Messages between Heterogeneous Networks

• US 20100205268A1
• Filed: 04/21/2010
• Published: 08/12/2010
• Est. Priority Date: 10/22/2007
• Status: Active Grant

• Current Assignee: Huawei Technologies Co., Ltd. (Huawei Investment & Holding Co., Ltd.)
• Original Assignee: Huawei Technologies Co., Ltd. (Huawei Investment & Holding Co., Ltd.)
• Inventors: LIANG, Wenyong, GAO, Yanfeng, ZHOU, Riming, ZHU, Ake
• Granted Patent: US 8,370,427 B2
• Time in Patent Office: Days
• US Class Current: 709/206
• CPC Class Codes: H04L 51/066 Format adaptation, e.g. format conversion or compression
• CPC Class Codes: H04L 51/58 Message adaptation for wireless communication
• CPC Class Codes: H04L 65/1016 IP multimedia subsystem [IMS]
• CPC Class Codes: H04L 69/18 Multiprotocol handlers, e.g. single devices capable of handling multiple protocols

Abstract

A method and apparatus for transmitting messages between heterogeneous networks are disclosed. The method includes: receiving an IP multimedia subsystem (IMS) message from an IMS network; converting the format of the IMS message into the format of a non-IMS message and converting the sender terminal ID of the IMS message into the sender terminal ID of the non-IMS message; and sending the non-IMS message that includes the content and sender terminal ID of the non-IMS message to a receiver terminal of the non-IMS message through the home network of the non-IMS message. The disclosure can implement message interworking between an IMS user terminal and a non-IMS user terminal.

Claims

1. A method for transmitting messages between heterogeneous networks, comprising:

receiving an IP multimedia subsystem (IMS) message from an IMS network;

converting a content format of the IMS message into a content format of a non-IMS message, and converting a sender terminal ID of an IMS message into a sender terminal ID of a non-IMS message; and

sending the non-IMS message that comprises the non-IMS message content and the sender terminal ID of the non-IMS message to a receiver terminal of the non-IMS message through a home network of the non-IMS message.

2. The method of claim 1, further comprising:

receiving, by a home messaging application server (AS) corresponding to the sender terminal of the IMS message, the IMS message from the IMS network;

converting, by the home messaging AS corresponding to the sender terminal of the IMS message, the sender terminal ID of the IMS message into the sender terminal ID of the non-IMS message;

sending, by the home messaging AS corresponding to the sender terminal of the IMS message, the IMS message content, the sender terminal ID of the non-IMS message, and a receiver terminal ID to a proxy; and

by the proxy, generating the non-IMS message according to the IMS message content, the sender terminal ID of the non-IMS message and the receiver terminal ID, and sending the non-IMS message to the receiver terminal of the non-IMS message through the home network of the non-IMS message.

3. The method of claim 1, further comprising:

receiving, by a home messaging application server (AS) corresponding to the sender terminal of the IMS message, the IMS message from the IMS network;

sending, by the home messaging AS corresponding to the sender terminal of the IMS message, the IMS message to a message gateway (IM-MGW); and

by the IM-MGW, parsing the IMS message, converting the sender terminal ID of the IMS message into the sender terminal ID of the non-IMS message, generating the non-IMS message according to the IMS message content, the sender terminal ID of the non-IMS message and the receiver terminal ID, and sending the non-IMS message to the receiver terminal of the non-IMS message through the home network of the non-IMS message.

4. The method of claim 1, further comprising:

adding a record ID and a route ID to the sender terminal ID of the non-IMS message.

5. The method of claim 1, wherein the step of converting the sender terminal ID of the IMS message into the sender terminal ID of the non-IMS message comprises:

obtaining a user ID from a sender terminal SIPURI address of the IMS message, and adding a route ID to the user ID to obtain the sender terminal ID of the non-IMS message, wherein the route ID points to an entity that converts the IMS message.

6. The method of claim 1, further comprising a step of converting the receiver terminal ID of the IMS message into the receiver terminal ID of the non-IMS message, wherein the step comprises:

obtaining a user ID that is bound to a receiver terminal SIPURI address of the IMS message, wherein the user ID is set for the receiver terminal of the IMS message in the home network corresponding to the non-IMS message.

7. The method of claim 1, wherein the step of converting the sender terminal ID of the IMS message into the sender terminal ID of the non-IMS message further comprises:

adding an anonymous ID to the ID of the sender terminal of the non-IMS message.

8. A method for transmitting messages between heterogeneous networks, comprising:

receiving a non IP multimedia subsystem (IMS) message from an IMS network;

converting a content format of the non-IMS message into a content format of an IMS message;

converting a receiver terminal ID of a non-IMS message into a receiver terminal ID of an IMS message; and

sending the IMS message that comprises the IMS message content and the receiver terminal ID of the IMS message to the receiver terminal of the IMS message through the IMS network.

9. The method of claim 8, comprising:

receiving, by a proxy, the non-IMS message that comprises a route ID of a home messaging application server (AS) of the non-IMS message receiver terminal from the non-IMS message sender terminal through a non-IMS network;

sending, by the proxy, an obtained non-IMS message content, the sender terminal ID of the non-IMS message and the receiver terminal ID of the non-IMS message to the home messaging AS corresponding to the receiver terminal of the non-IMS message according to the route ID;

converting, by the home messaging AS corresponding to the receiver terminal of the non-IMS message, the receiver terminal ID of the IMS message into the receiver terminal ID of the non-IMS message; and

by the home messaging AS corresponding to the receiver terminal of the non-IMS message, generating the IMS message according to the IMS message content and the sender terminal ID and the receiver terminal ID of the IMS message, and sending the IMS message to the receiver terminal of the IMS message through a home network of the IMS message.

10. The method of claim 8, comprising:

receiving, by a message gateway (IM-MGW), the non-IMS message that the sender terminal of the non-IMS message sends through a non-IMS network according to a route ID of the IM-MGW carried in the non-IMS message; and

by the IM-MGW, parsing the non-IMS message, converting the receiver terminal ID of the non-IMS message into the receiver terminal ID of the IMS message, generating the IMS message according to the non-IMS message content and the sender terminal ID, and the receiver terminal of the IMS message, and sending the IMS message to the receiver terminal of the IMS message through a home messaging application server (AS) corresponding to the receiver terminal of the IMS message.

11. The method of claim 8, comprising:

receiving, by a home messaging application server (AS) corresponding to the receiver terminal, the non-IMS message comprising a preset record ID that reflects a mapping between an IMS domain name and a sender terminal forwarding ID from a non-IMS network according to a route ID in the non-IMS message, wherein the IMS domain name associated with the record ID is a home domain name of the receiver terminal of the non-IMS message and the sender terminal forwarding ID indicates whether the receiver terminal of the non-IMS message and the home messaging AS corresponding to the receiver terminal that converts the content format of the non-IMS message belong to a same IMS domain;

by the home messaging AS corresponding to the receiver terminal, converting the content format of the non-IMS message into the content format of the IMS message, obtaining the domain name of the receiver terminal according to the record ID, generating an IMS message address according to the receiver terminal ID of the non-IMS message, and constructing the IMS message according to the address and message content of the IMS message; and

if the sender terminal forwarding ID indicates that the receiver terminal is a user in a local domain, sending, by the home messaging AS corresponding to the receiver terminal, the IMS message to the receiver terminal of the IMS message through a home IMS network of the messaging AS;

if the sender terminal forwarding ID indicates that the receiver terminal may not be a user in the local domain, forwarding, by the home messaging AS corresponding to the receiver terminal, the IMS message to the home messaging AS corresponding to the receiver terminal; and

sending, by the messaging AS, the IMS message to the receiver terminal of the IMS message.

12. The method of claim 8, wherein the step of converting the receiver terminal ID of the non-IMS message into the receiver terminal ID of the IMS message comprises:

deleting the route ID from the receiver terminal ID of the non-IMS message to obtain a user ID, and adding the user ID to the domain name of the home IMS network corresponding to the receiver terminal to obtain the receiver terminal address of the IMS message.

13. A message conversion apparatus, comprising:

a receiving module, adapted to receive an IP multimedia subsystem (IMS) message from an IMS network;

a converting module, adapted to convert the IMS message into a non-IMS message; and

a sending module, adapted to send the non-IMS message to a home network of the non-IMS message, wherein the home network sends the non-IMS message to a receiver terminal of the non-IMS message;

wherein;

the converting module comprises;

a content converting submodule, adapted to convert a content format of the IMS message into a content format of the non-IMS message; and

a sender terminal ID converting submodule, adapted to convert a sender terminal ID of the IMS message into a sender terminal ID of a non-IMS message.

14. The message conversion apparatus of claim 13, wherein:

the IMS message received by the receiving module is associated with a message forwarding policy, wherein the message forwarding policy converts the IMS message into the non-IMS message and sends the non-IMS message; and

the converting module is further adapted to convert the IMS message into the non-IMS message according to the message forwarding policy.

15. The message conversion apparatus of claim 13, wherein the sender terminal ID converting submodule comprises at least one of a first converting unit and a second converting unit, wherein:

the first converting unit is adapted to;

obtain a user ID from the sender terminal address of the IMS message, and add a route ID to the user ID to obtain a sender terminal ID of the non-IMS message, wherein the route ID points to the message conversion apparatus; and

the second conversion unit is adapted to;

obtain a user ID that is bound to the sender terminal address of the IMS message, and add a route ID to the user ID to obtain a sender terminal ID of the non-IMS message, where the route ID points to the message conversion apparatus.

16. The message conversion apparatus of claim 13, wherein the converting module further comprises:

a receiver terminal ID converting submodule, adapted to convert a receiver terminal ID of an IMS message into a receiver terminal ID of a non-IMS message.

17. The message conversion apparatus of claim 13, wherein the sender terminal ID converting submodule is further adapted to add a record ID and a route ID to the sender terminal ID of the non-IMS message.

18. A message conversion apparatus, comprising:

a receiving module, adapted to receive a non IP multimedia subsystem (IMS) message from a non-IMS network;

a converting module, adapted to convert the non-IMS message into an IMS message; and

a sending module, adapted to send the IMS message to an IMS network, wherein the IMS network sends the IMS message to a receiver terminal of the IMS message;

wherein;

the converting module comprises;

a content converting submodule, adapted to convert a content format of the non-IMS message into a content format of the IMS message; and

a receiver terminal ID converting submodule, adapted to convert a receiver terminal ID of the non-IMS message into an ID of a receiver terminal of the IMS message.

19. The message conversion apparatus of claim 18, wherein the non-IMS message received by the receiving module is sent by the non-IMS network according to at least one of a route ID carried in the non-IMS message and route information associated with the message conversion apparatus that is stored in the non-IMS network.

20. The message conversion apparatus of claim 18, wherein:

the receiver terminal ID converting submodule is further adapted to query for an IMS domain name that is associated with a record ID carried in the non-IMS message in a mapping between a preset IMS domain name and a sender terminal forwarding ID, and convert the receiver terminal ID of the non-IMS message into a receiver terminal SIPURI address of the IMS message according to the IMS domain name; and

the sending module comprises;

an obtaining submodule, adapted to obtain the sender terminal forwarding ID from the mapping according to the record ID; and

a sending submodule, adapted to send the IMS message to the receiver terminal of the IMS message when the sender terminal forwarding ID indicates that a messaging application server (AS) integrated with the message conversion apparatus and the receiver terminal of the IMS message belong to a same IMS network; and

send the IMS message to the receiver terminal of the IMS message through a messaging AS associated with the IMS domain name when the sender terminal forwarding ID indicates that the messaging AS integrated with the message conversion apparatus and the receiver terminal of the IMS message belong to different IMS networks.