CN101483611B - System, method and apparatus for implementing message service interconnection - Google Patents

Abstract

The embodiment of the invention discloses a system, method and equipment for realizing message service interworking. In the embodiment of the present invention, a message server is set in the access network supporting the MIH protocol, and the message server and the terminal in the access network where it is located perform service message transmission through the MIH protocol, and the store-and-forward server communicates with the store-and-forward server through the network where the store-and-forward server is located. Supported protocols for business message transmission, and a technical solution for converting business messages between the MIH protocol format and the message format supported by the network where the store-and-forward server is located, so that the access network supporting the MIH protocol can realize the transmission of business messages .

Description

A system, method and device for realizing message service interworking

technical field

The invention relates to the technical field of network communication, in particular to a system, method and device for realizing message service intercommunication.

Background technique

The IEEE 802.21 working group has developed a standard framework for Media Independent Handover (MIH, Media Independent Handover) between wired and wireless and wireless and wireless access technologies. The access technologies involved include: corresponding to LAN (local area network) ), 802.11 corresponding to Wireless Local Area Network (WLAN, Wireless Local Area Network), 802.16 corresponding to Wireless Metropolitan Area Network (WMAN, Wireless Metropolitan Area Network), corresponding to Wireless Personal Area Network (WPAN, Wireless Personal Area Network) 802.15 and 3GPP/3GPP2 2G and 3G networks.

FIG. 1 is a schematic diagram of a standard framework of media independent switching. As shown in Figure 1, the IEEE 802.21 working group introduces a media independent handover function (MIHF, Media Independent Handover Function) logic layer, which is between the upper layer and the lower layer. The upper layer includes: IP, MIP, SIP, HIP, transport layer and Application layer, etc., the bottom layer includes the data link layer. In Figure 1, the MIHF entity communicates with the media independent event service (MIES, Media Independent Event Service), media independent command service (MICS, Media Independent Command Service) and media independent information service (MIIS, Media Independent Information Service) The interaction between different bottom access technologies and the communication with the peer MIHF shield the heterogeneity of the bottom access technologies, so that the upper layer does not need to understand the differences of the bottom access technologies, and simplifies the operation and management of the network. The MIHF identifier (ID) defined in IEEE802.21 uniquely identifies an MIHF entity when peer MIHF entities interact. The MIHF ID is configured when the network management system initializes the MIHF. It can be the fully qualified domain name (FQDN, Fully Qualified Domain Name) number or the network access identifier (NAI, Network Access Identifier) of the device where the MIHF entity is located.

There are various message services in the existing communication network, such as: Short Message Service (SMS, Short Message Service), Enhanced Short Message Service (EMS, Enhanced Messaging Service), Unified Message Service (UMS, Unified Message Service) ), multimedia message service (MMS, Multimedia Message Service), unstructured supplementary data service (USSD, Unstructured Supplementary Service Data) service, extended weather forecast message service and advertisement message service, etc.

When a terminal supporting multiple access technologies moves in a heterogeneous network environment, the problem of intercommunication of message services is brought about, that is, the intercommunication of message services cannot be realized between access networks of different access technologies.

Contents of the invention

The embodiment of the present invention provides a system for realizing message service interworking, and the system enables all access networks supporting the MIH protocol to realize the transmission of service messages.

The embodiment of the present invention provides a method for realizing message service intercommunication, which enables all access networks supporting the MIH protocol to realize the transmission of service messages.

The embodiment of the present invention also provides a message server and terminal, which enable the access network where the message server and terminal are located and which supports the MIH protocol to realize the transmission of service messages.

In order to achieve the above object, the technical solution of the present invention is specifically realized in the following way:

The embodiment of the present invention discloses a system for realizing message service intercommunication. The system includes: a store-and-forward server and a message server set in an access network supporting the Media Independent Handover (MIH) protocol, wherein,

The message server includes: a media independent switching module, a format conversion module and a transceiver module;

The media independent switching module is used to receive the service message in MIH format sent by the terminal, and send the service message in MIH format from the terminal to the format conversion module; send the service message in MIH format from the format conversion module to the terminal;

The format conversion module is used to receive the business message of the MIH format sent by the media independent switching module, and send the business message of the MIH format to the transceiver module in a message format supported by the network where the storage and forwarding server is located; A service message, and send the service message sent by the transceiver module to the media independent switching module in MIH format;

The transceiver module is used to receive the service message sent by the store-and-forward server, send the service message from the store-and-forward server to the format conversion module; send the service message from the format conversion module to the store-and-forward server;

The store-and-forward server is configured to receive the service message, and send the service message according to the receiver routing information of the service message.

The embodiment of the present invention discloses a method for realizing message service interworking, which is characterized in that the method includes:

Receiving the service message in MIH format sent by the terminal, determining the corresponding store-and-forward server according to the service message in MIH format, and sending the service message in MIH format to the store-and-forward server in a message format supported by the network where the store-and-forward server is located server.

The embodiment of the present invention discloses a message server, the message server includes: a media independent switching module, a format conversion module and a sending and receiving module, wherein,

The media independent switching module is used to receive the service message in MIH format sent by the terminal, and send the service message in MIH format from the terminal to the format conversion module; send the service message in MIH format from the format conversion module to the terminal;

The format conversion module is used to receive the business message of the MIH format sent by the media independent switching module, and send the business message of the MIH format to the transceiver module in the message format supported by the network where the storage and forwarding server is located; receive the business message sent by the transceiver module , and sending the service message sent by the transceiver module to the media independent switching module in MIH format;

The transceiver module is used to receive the service message sent by the store-and-forward server, send the service message from the store-and-forward server to the format conversion module, and send the service message from the format conversion module to the store-and-forward server.

The embodiment of the present invention also discloses a terminal, which includes: a media independent switching module;

The media independent switching module is used to send the service message in MIH format to the message server; and receive the service message in MIH format sent by the message server.

It can be seen from the above technical solution that in the embodiment of the present invention, a message server is set in the access network supporting the MIH protocol; the message server and the terminal in the access network where it is located carry out service message transmission through the MIH protocol, and store and forward server Transmit business messages through the protocol supported by the network where the store-and-forward server is located, and convert business messages between the MIH protocol format and the protocol format supported by the network where the store-and-forward server is located, so as to support the access of the MIH protocol The network can realize the transmission of business messages.

Description of drawings

FIG. 1 is a schematic diagram of the principle of a standard framework for media-independent switching in the prior art;

FIG. 2 is an architecture diagram of a first embodiment of a system for realizing message service interworking according to the present invention;

Fig. 3 is a schematic diagram of the protocol architecture of terminals belonging to the same access network and MS Server in Fig. 4;

FIG. 4 is a flow chart of a terminal subscribing to a message service according to an embodiment of the present invention;

FIG. 5 is a flowchart of a terminal sending a service message according to an embodiment of the present invention;

FIG. 6 is a flowchart of a terminal receiving a service message according to an embodiment of the present invention;

FIG. 7 is a flow chart of unsubscribing initiated by a terminal according to an embodiment of the present invention;

Fig. 8 is the flow chart of canceling the subscription that MS Server initiates in the embodiment of the present invention;

FIG. 9 is a structure diagram of a second embodiment of a system for realizing message service interworking according to the present invention;

FIG. 10 is a block diagram of a system structure for realizing short message service interworking according to an embodiment of the present invention;

FIG. 11 is a flowchart of UE1 sending a short message in FIG. 10;

FIG. 12 is a flowchart of UE1 receiving a short message in FIG. 10;

13 is a block diagram of a system structure for implementing message service interworking between an access network supporting MIH and an IP network according to an embodiment of the present invention;

FIG. 14 is a flow chart of sending a service message by UE1 in FIG. 13;

FIG. 15 is a flowchart of UE1 receiving a service message in FIG. 13;

Fig. 16 is a structural block diagram of a message server according to an embodiment of the present invention;

Fig. 17 is a structural block diagram of a terminal according to an embodiment of the present invention.

Detailed ways

As mentioned in the background art, the IEEE 802.21 working group has formulated a standard framework for media-independent handover between wired and wireless, and wireless and wireless access technologies. In this framework, the IEEE 802.21 working group introduces a MIHF logic layer, which is between the high-level and the bottom layer, provides a unified interface for the high-level layer, shields the heterogeneity of the bottom-layer access technology, and makes the high-level layer do not need to understand the bottom layer Differences in access technology. At the same time, for networks that support the IEEE 802.21 protocol, regardless of whether the access technology is the same, they can interact based on MIHF.

Therefore, the inventor of the present application proposed an interworking system architecture for message services based on the MIHF network architecture of IEEE 802.21, and provided a general solution for the problem of supporting message interworking in the current heterogeneous environment, making it possible to support IEEE 802.21 The MIH protocol developed by the working group can directly send business messages in the heterogeneous network environment.

In order to make the object, technical solution and advantages of the present invention clearer, the present invention will be further described in detail below with reference to the accompanying drawings and preferred embodiments.

Fig. 2 is a structure diagram of the first embodiment of a system for implementing message service interworking according to the present invention. As shown in Figure 2, the system includes: a store-and-forward server, a routing information server, a message server (MS Server) set in different access networks supporting the MIH protocol, and a terminal supporting the MIH protocol. Here, the access network supporting the MIH protocol means that the access network can enable the MS Server and the terminal to communicate using the MIH protocol. In this embodiment, the different access networks involved are described by taking wireless local area network (802.11), wireless metropolitan area network (802.16), wireless personal area network (802.15) and 3GPP/3GPP2 network as examples.

In the system shown in Figure 2:

The terminals in each access network use the MIH protocol to communicate with the MS server of the access network where they are located, so as to register their own MIHF ID to the MS Server, subscribe to the MS Server for specific message services, and cancel specific message services Subscribe to and receive and send messages in MIH format.

MS Server, supports terminal registration and deregistration, and supports terminal message service subscription and unsubscription; registers the routing information of the network terminal with the routing information server; according to the network where the store and forward server is located, MIH from the network terminal Format messages are converted and sent to the store-and-forward server; messages from the store-and-forward server are converted into MIH format and then sent to the network terminal. MS Server can be an independent network device, or it can be integrated in some network devices of other existing networks, such as gateway devices.

The store-and-forward server is used to receive and store messages from the MS Server; query the routing information server for the destination routing information of the messages stored by itself; send the stored messages according to the queried routing information.

The routing information server supports MS Server terminal routing information registration, and adds the registration information to its own routing table; supports storing and forwarding server routing query requests, and returns query results.

The store-and-forward server and the routing information server are located in the core network. Different access networks may have the same core network, or may have their own core networks. When different access networks have different core networks, the store-and-forward server and routing information server can be located in any one of the core networks; There are store-and-forward servers and routing information servers in each core network, and service messages need to be transmitted between multiple store-and-forward servers at this time. In addition, the number of store-and-forward servers and routing information servers can be configured arbitrarily according to specific network environments and specific services.

In Fig. 2, according to the network where the store-and-forward server is located, the MS Server converts and processes the message in MIH format from the network terminal and then sends it to the store-and-forward server. Use the MIHF ID to identify the MS Server and the terminal. For example, the MIHF ID of the MS Server is the FQDN or NAI number of the MS Server, and the MIHF ID of the terminal is the FQDN or NAI number of the terminal. As the terminal moves, the MIHFID of the terminal remains unchanged in the network supporting MIH. When registering, the terminal sends its own MIHF ID in the network and its identity in the network where the store-and-forward server is located to the MS Server. For the convenience of description, the identifier of the terminal in the network where the store-and-forward server is located will be referred to as the service network identifier of the terminal hereinafter. The MS Server saves the relationship between the MIHF ID of the terminal and the service network identifier. When subscribing or unsubscribing a message, the terminal subscribes or unsubscribes a specific message service to the MS Server. When the MS Server receives the message in MIH format from the terminal, it queries the corresponding service network identifier according to the MIHF ID of the terminal carried in the message, obtains the network type of the store-and-forward server according to the service network identifier, and transfers the received message in MIH format Convert it into a message format supported by the network where the store-and-forward server is located, and then send it to the store-and-forward server.

Fig. 3 is a schematic diagram of the protocol architecture of the terminal and the MS Server belonging to the same access network in Fig. 2 . As shown in Figure 3, the terminal includes: message application layer (MAL, Message Application Layer) and media independent handover function (MIHF); MS Server includes: media independent handover function (MIHF), message relay layer (MRL, Message Relay Layer ) and message link layer (MLL, Message LinkLayer). in:

The MAL of the terminal is used to interact with the peer-to-peer MAL to realize the message service function, that is, adding application layer information to the message sent by the terminal, and analyzing the application layer information in the message received by the terminal.

The MIHF of the terminal is used to interact with the MIHF in the MS Server through the MIH protocol, realize the subscription and unsubscription of the message service, send the message to the MIHF in the MS Server in MIH format, and receive the message sent from the MIHF of the MS Server.

The MIHF of MS Server is used for MIHF interaction on the terminal side, receiving subscription and unsubscription of message services, sending error responses, sending messages in MIH format from the terminal to MRL, and sending messages from MRL to MIHF of the terminal.

The MRL of MS Server realizes the conversion of message format, that is, the message in MIH format is converted into the message supported by the network where the store-and-forward server is located, and the message sent by the store-and-forward server is converted into MIH format.

The MLL of MS Server sends the message converted by MRL, and sends the received message to MRL for conversion processing.

In the embodiment of the present invention, using the MIH protocol to realize the subscription and unsubscription of the message service refers to using the message format of the MIH protocol to complete the function of subscribing and unsubscribing the message service. Here, subscribing to a message service means that after a successful subscription, the terminal can send and receive messages related to the subscribed message service. Using the MIH protocol to send and receive messages refers to encapsulating message content and corresponding parameters or error responses into MIH messages, or defining options corresponding to message messages in MIH messages. The function of MRL to complete message format conversion means that MRL reads the content of the message sent using the MIH protocol, encapsulates the corresponding content into the format of the network message where the store-and-forward server is located, and sends it out, that is, the header of the message sent by MRL according to the MIH protocol Obtain the source MIHF ID of the message and the service type information of the message and encapsulate the content of the message in the data part of the message, find its identifier in the network where the store-and-forward server is located according to the MIHF ID, and according to the information in the network where the store-and-forward server is located The ID of the message or the service type information of the message encapsulates the content of the message into a format supported by the network where the store-and-forward server is located, and its source address uses the ID corresponding to the source MIHF ID of the message in the network where the store-and-forward server is located; MRL reads The content of the message sent by the network where the store-and-forward server is located encapsulates the corresponding content into the format of the MIH protocol message and sends it out, that is, the MRL reads the destination address of the message sent by the network where the store-and-forward server is located, the service type information and According to the content of the message, look up its MIHF ID in the MIH network according to the destination address of the message, encapsulate the message into the format of the MIH message, use the MIHF ID corresponding to the destination address of the message in the MIH network as the destination address, and set The information is encapsulated into the header of the format of the MIH message, and other contents of the message are encapsulated into the data part of the message.

In the embodiment of the present invention, after the terminal enters an access network, there are many methods for discovering the MSServer in the access network, for example: the address of the MS server is pre-configured in the terminal, and no specific discovery mechanism is required at this time; or , configure the address of the MS server in the first hop (PoA or PoS) of the access network, and the terminal can obtain the address of the MS server when it accesses the network; or, set a directory to save the address information of the MS server in the network The server and the terminal obtain the address of the MS server by querying the directory server; or, the MS server is located in a specific multicast domain, and the terminal obtains the addresses of one or more MS servers by sending multicast. The address information of the MS Server can be the MIHF ID of the MS Server.

After the terminal discovers the MS Server, it registers its own MIHF ID with the MS Server; after the MS Server accepts the terminal's registration, it returns a registration success message to the terminal. At any time after the terminal registers with the MS Server, it can subscribe to the message service with the MS Server.

FIG. 4 is a flowchart of a terminal subscribing to a message service according to an embodiment of the present invention. As shown in Figure 4, the following steps are included:

Step 401, the terminal sends a subscription request message to the message server MS Server.

In this step, the subscription request message sent by the terminal is a message in MIH format, and includes: the MIHF ID (source MIHF identification) of the terminal, the MIHF ID (target MIHF identification) of the MS Server, the service network identification of the terminal, and the requested Information such as the business type of the subscribed message service.

Step 402, the MS Server sends a registration request message to the routing information server, which carries the terminal's service network identifier and the terminal's current routing information.

In this step, the current routing information of the terminal may specifically be the address of the MS Server. This is because the terminal is currently in the network managed by MS Server, if a message needs to be sent to the terminal, the message will be routed to MS Server first.

Step 403, the routing information server saves the service network identifier of the terminal, and correspondingly saves the current routing information of the terminal, and then returns a registration success message to the MS Server.

Step 404, after receiving the successful registration message, the MS Server saves the MIHF ID of the terminal, and correspondingly saves the service network identifier of the terminal.

MS Server can also save the MIHF ID of the terminal at any time after receiving the subscription request message from the terminal.

In step 405, the MS Server returns a subscription confirmation message to the terminal.

In this step, the subscription confirmation message returned by the MS Server to the terminal is a message in MIH format.

In the above process shown in Figure 4, if the subscription process fails due to an error, the MS Server returns a subscription failure message to the terminal in step 405, and the subscription failure message carries the error code or error reason information and the Ms server MIHF ID (source MIHF identification) and terminal MIHF ID (destination MIHF identification) and other content.

After the terminal subscribes to the message service through the process shown in Figure 4, it can receive and send the subscribed service message.

Fig. 5 is a flowchart of a terminal sending a service message according to an embodiment of the present invention. As shown in Figure 5, it includes the following steps:

Step 501, the terminal sends a message to the MS Server.

In this step, what the terminal sent was a service message in MIH format, which included: the MIHF ID (source MIHF identification) of the terminal, the MIHF ID (destination MIHF identification) of the MS Server, the business type of the message and the main content of the message and the reception of the service message Party ID. The identifier of the service message receiver is the service network identifier of the service message receiver.

Step 502, after the MS Server receives the service message sent by the terminal, it searches out the service network identifier of the terminal from the content saved by itself according to the terminal MIHF ID carried in the service message, and compares the received service network identifier according to the service type or service network identifier of the message Business messages are format converted.

In this step, MS Server converts the format of the received service message according to the service network identifier as follows: MS Server determines the type of network where the store-and-forward server is located according to the service network identifier of the terminal, and transforms the received service message according to the service type of the message The format is converted into the format of the service message supported by the network where the store-and-forward server is located.

In step 503, the MS Server sends the format-converted service message to the store-and-forward server, and the service message carries the service network identifier of the terminal and the service network identifier of the recipient of the service message.

In this step, the MS Server carries the service network identifier of the terminal as the identifier of the sender of the service message in the sent service message.

Step 504, the store and forward server returns the status report message to the MS Server after sending the received service message to the destination according to the service network identifier of the service message receiver.

In this step, the status report message returned by the MS Server carries the service network identifier of the service message sending terminal.

Step 505: After receiving the status report message, the MS Server searches out the corresponding MIHF ID according to the service network identifier of the service message sending terminal therein, and converts the status report message into MIH format.

In step 506, the MS Server sends the status report message in MIH format to the terminal identified by the queried MIHF ID, that is, the terminal that sends the service message.

In this step, the status report message includes: the MIHF ID (source MIHF identification) of MS Server, the MIHF ID (destination MIHF identification) of the terminal, the service type of the message and the sending status information of the message. If there is an error sending the message, it also includes the error code and the reason for the error.

Fig. 6 is a flowchart of a terminal receiving a service message according to an embodiment of the present invention. As shown in Figure 7, the following steps are included:

Step 601, the store-and-forward server receives and stores the service message from the service message sender, and then uses the service network identifier of the service message receiving terminal carried in the service message to query the routing information of the terminal from the routing information server, and the routing information server forwards the service message to the store and forward The server returns routing information corresponding to the service network identifier of the service message receiving terminal.

In this step, the routing information returned by the routing information server is the address of the MSServer currently registered by the terminal.

Step 602, the store-and-forward server forwards the stored service message to the MS Server according to the routing information returned by the routing information server.

Step 603, after the MS Server receives the service message, it retrieves the MIHF ID corresponding to the service network identifier of the receiving terminal carried in the message from the associated information of the MIHF ID and the service network identifier saved by itself, and sends the received service message Convert messages into MIH format.

Step 604, the MS Server sends the format-converted service message to the terminal identified by the retrieved MIHFID.

In this step, the message sent by the MS Server to the terminal includes: the MIHF ID (source MIHF identification) of the MS Server, the MIHF ID (destination MIHF identification) of the terminal, the service type of the message and the main content of the service message, etc.

Step 605, the terminal returns a status report message in MIH format to the MS Server.

In this step, the status report message returned by the terminal to the MS Server includes: the MIHF ID (source MIHF identification) of the terminal, the MIHF ID (destination MIHF identification) of the MS Server, the service type of the message and the sending status information of the message. If there is an error in sending, it also includes information such as the error code and the cause of the error.

Step 606, MS Server finds out the service network identifier of the terminal from the content saved by itself according to the terminal MIHF ID carried in the status report message, and performs format conversion processing on the received status report message according to the service network identifier and the service type of the message.

In this step, MS Server converts the format of the status report message according to the service network identifier as follows: MS Server determines the type of network where the store-and-forward server is located according to the service network identifier of the terminal, and converts the received status report message according to the service type of the message into a message format supported by the network where the store-and-forward server resides.

Step 607, MS Server sends the status report message after the format conversion to the store and forward server.

So far, the process of receiving service messages by the terminal is completed.

In the embodiments shown in FIG. 5 and FIG. 6 , the flow of the terminal sending the service message and the flow of the terminal receiving the service message are given respectively. When the service message sent by the terminal in FIG. 5 is sent to the terminal in FIG. 6 , it is sufficient to perform steps 601 to 607 after steps 501 to 503 , and then to perform steps 504 to 506 . And at this time, if the store-and-forward server in FIG. 5 and the store-and-forward server in FIG. 6 are two different devices, the following steps need to be performed between step 503 and step 601: the store-and-forward server in FIG. 5 will The service message is sent to the store-and-forward server in FIG. 6 . The store-and-forward server in FIG. 5 first queries the store-and-forward server in FIG. 6 according to the service network identifier of the receiver of the service message, and then sends the service message. If the store-and-forward server in FIG. 5 and the store-and-forward server in FIG. 6 are located in different networks, the formats of the business messages supported by them are also different, and at this time, the store-and-forward server in FIG. 5 converts the format of the business messages Then send it to the store-and-forward server in Figure 6.

After the terminal subscribes to the message service through the process shown in Figure 4, it can cancel the subscription at any time. The process of unsubscribing can be initiated by the terminal itself or by MS Server.

Fig. 7 is a flow chart of unsubscribing initiated by a terminal according to an embodiment of the present invention. As shown in Figure 7, the following steps are included:

Step 701, the terminal sends an unsubscribe message to the MS Server.

In this step, the unsubscribe message sent by the terminal is a message in MIH format, and includes: the MIHF ID (source MIHF identification) of the terminal, the MIHF ID (target MIHF identification) of the MS Server, and the type of message service to request unsubscription and the reason for unsubscribing.

Step 702, after the MS Server receives the unsubscribe message, cancel the subscription of such messages according to the business type of the message service, judge whether the terminal has other types of message services according to the MIHF ID of the terminal, otherwise delete the MIHF ID of the terminal saved by itself and service network identifier, if yes, do not perform this operation, skip step 703 and step 704 and directly execute step 705.

Step 703, the MS Server sends a deregistration message carrying the service network identifier of the terminal to the routing information server to inform the routing information server that the terminal corresponding to the service network identifier is no longer in charge of the MS Server.

Step 704, after the routing information server deletes the routing information corresponding to the service network identifier in the deregistration message, it returns a deregistration confirmation message to the MS Server.

Step 705, MS Server sends an unsubscribe confirmation message to the terminal.

In this step, the unsubscribing confirmation message that MS Server sends to terminal is a message in MIH format, including: the MIHF ID (source MIHF identification) of Ms server, the MIHF ID (purpose MIHF identification) of terminal, the service type of message and Unsubscribe from things like status messages.

Fig. 8 is a flow chart of unsubscribing initiated by MS Server in the embodiment of the present invention. As shown in Figure 8, the following steps are included:

Step 801, the MS Server sends a deregistration message carrying the service network identifier of the terminal to the routing information server to inform the routing information server that the terminal corresponding to the service network identifier is no longer in charge of the MS Server.

Step 802, the routing information server returns a deregistration confirmation message to the MS Server.

Step 803, MS Server deletes the MIHF ID and service network identifier of the terminal saved by itself.

In step 804, the MS Server sends an unsubscribe message to the terminal to inform the terminal that its message service on the MS Server has been cancelled.

In this step, the unsubscribe message sent by the MS Server to the terminal includes: the MIHF ID (source MIHF identifier) of the Ms server, the MIHF ID (destination MIHF identifier) of the terminal, and the unsubscribe request and reason. In this step, the default is to unsubscribe from all message services that the terminal has subscribed to.

Step 805, after receiving the unsubscribe message from the MS Server, the terminal returns an unsubscribe confirmation message to the MS Server.

In this step, the cancellation confirmation message returned by the terminal to the MS Server includes: the MIHF ID (source MIHF identification) of the terminal, the MIHF ID (target MIHF identification) of the MS Server, and unsubscribe status information.

In the above implementation, the network architecture and the transmission mode of the service message are given to realize the intercommunication of the message service between the access networks supporting the MIH protocol. Considering that there may be some access networks that do not support the MIH protocol in practice, a technical solution for interworking of message services between the access network that supports the MIH protocol and the access network that does not support the MIH protocol is given in the present invention.

FIG. 9 is a structure diagram of a second embodiment of a system for implementing message service interworking according to the present invention. As shown in Figure 9, the system includes: a store-and-forward server, a routing information server, an MS Server set in each access network supporting the MIH protocol, a gateway set in each access network not supporting the MIH protocol, and each access network into the terminal under the network. In this embodiment, an IP network, a SIP network, and a public land mobile network (PLMN) network are used as examples for the involved access networks that do not support the MIH protocol; for the involved networks that support the MIH protocol, use The 802.16 network is used as an example for illustration. Of course, in this system, the number of access networks that support the MIH protocol and the number of access networks that do not support the MIH protocol can be arbitrary.

In the system shown in Figure 9:

The MS Server and terminal in 802.16 are the same as those in the system shown in Figure 2.

Terminals in each access network that does not support the MIH protocol are used to communicate with the gateway of the access network using the scheme supported by the access network to realize registration, subscription, unsubscription, reception and transmission of message services business news.

The gateways in the access networks that do not support the MIH protocol support the subscription and unsubscription of terminal message services; register the routing information of the network terminal with the routing information server; according to the network where the store-and-forward server is located, After the business message is converted and processed, it is sent to the store-and-forward server; after the message from the store-and-forward server is converted into a format supported by the local network, it is sent to the network terminal.

The store-and-forward server is used to receive and store messages from the MS Server and the gateway; query the route information server for the destination routing information of the messages stored by itself; send the stored messages according to the queried routing information.

The routing information server supports MS Server and GW terminal routing information registration, and adds the registration information to its own routing table; supports storing and forwarding the routing query request of the server, and returns the query result.

The store-and-forward server and the routing information server are located in the core network of any network. For example, when the store-and-forward server and routing information server are located in the core network of the PLMN network, the message format conversion performed by the gateway in Figure 9 is the conversion between the message format supported by its own network and the MAP protocol format supported by the PLMN network , obviously, the gateway in the PLMN network does not need to perform format conversion processing on the message.

The system architecture shown in FIG. 9 is further described below by taking the intercommunication of the short message service between the GSM network that does not support the MIH protocol and the network that supports the MIH protocol as an example.

FIG. 10 is a structural block diagram of a system for implementing short message service interworking according to an embodiment of the present invention. As shown in Figure 10, the system includes: Short Message Service Center SMSC, Gateway Mobile Switching Center GMSC/Interworking Mobile Switching Center I-WMSC, Home Subscriber Server HSS/Home Location Register HLR, set in the access network supporting the MIH protocol The message server MS Server, the mobile switching center MSC, and the terminals (UE1 and UE2) and GSM terminal (UE3) supporting the MIH protocol.

In Figure 10, SMSC and GMSC/I-WMSC are equivalent to the store-and-forward server in Figure 9, HSS/HLR is equivalent to the routing information server in Figure 9, and MSC is equivalent to the access network in Figure 9 that does not support the MIH protocol gateway, and the store-and-forward server (SMSC and GMSC/I-WMSC) and routing information server (HSS/HLR) are located in the GSM network where the MSC is located. MS Server needs to convert business messages between MIH format and MAP format. And the service network identifier of the terminal is the MSISDN number.

In FIG. 10 , the flow of UE1 and UE2 subscribing to the short message service is the same as that shown in FIG. 4 , and will not be repeated here. Next, taking UE1 and UE3 as examples to illustrate the process of receiving and sending short messages by terminals in the access network supporting the MIH protocol in the scenario shown in FIG. 10 .

FIG. 11 is a flow chart of sending a short message by UE1 in FIG. 10 . As shown in Figure 11, the following steps are included:

Step 1101, UE1 sends a short message in MIH format to MS Server.

In this step, the short message sent by UE1 includes: the MIHF ID (source MIHF identification) of UE1, the MIHF ID (destination MIHF identification) of MS Server, the service type of the message and the main content of the short message and the service of the message receiver UE3 Network ID. Since the SMSC and GMSC/I-WMSC implementing the store-and-forward server function and the HSS/HLR implementing the routing information server function in this embodiment are located in the GSM network, the service network identifier of UE3 is the MSISDN number of UE3.

Step 1102, after the short message sent by UE1 received by the MS Server, according to the MIHF ID of UE1 carried in the short message, find out the MSISDN number corresponding to the MIHF ID of UE1 from the association information between the MIHF ID and the MSISDN number saved by itself, according to The type of the message carried in the short message is a short message type, and the received short message in MIH format is converted into a short message in MAP format.

Step 1103, MS Server sends the converted short message in MAP format to I-WMSC, and the message carries the MSISDN number of UE1 and the MSISDN number of UE3.

Step 1104, I-WMSC forwards the received short message to SMSC.

Step 1105, the SMSC sends the received short message to the destination according to the IMISDN number of the recipient UE3, and then returns a status report message to the I-WMSC, which carries the MSISDN number of UE1.

In this step, the SMSC sends the received short message to UE3 according to the IMISDN number of the receiver UE3. The sending MSC, and then the MSC sends the short message to UE3, which will not be described in detail here.

Step 1106, the I-WMSC forwards the status report message to the MS Server.

Step 1107, after receiving the status report message, the MS Server searches out the corresponding MIHF ID according to the MSISDN number therein, and converts the status report message into MIH format.

Step 1108, the MS Server sends the status report message in MIH format to the terminal UE1 identified by the queried MIHF ID.

In this step, the status report message includes: the MIHF ID (source MIHF identification) of MS Server, the MIHF ID (destination MIHF identification) of the terminal, the service type of the message and the sending status information of the message. If there is an error sending the message, it also includes the error code and the reason for the error.

Fig. 12 is a flowchart of UE 1 receiving a short message in Fig. 10. As shown in Figure 12, the following steps are included:

Step 1201, SMSC sends the short message to GMSC after receiving the short message in MAP format sent by UE3 to UE1.

In this step, the process of SMSC receiving the short message sent by UE3 to UE1, that is, the process of UE3 sending the short message to SMSC is the existing process of the GSM network, mainly including: UE3 sends the short message to MSC, and MSC sends the short message Send to the I-WMSC, and the I-WMSC sends the short message to the SMSC, which will not be described in detail here.

Step 1202, GMSC uses the MSISDN number of UE1 carried in the short message to query the routing information of UE1 from HSS/HLR, and HSS/HLR returns the address of the MS Server where UE1 is currently located to GMSC.

Step 1203, GMSC sends the short message to MS Server.

Step 1204, after the MS Server receives the short message, retrieve the MIHF ID corresponding to the MSISDN of the receiving end carried in the short message from the associated information of the MIHF ID and MSISDN saved by itself, and send the received message according to the type of the message Convert short messages into MIH format messages.

Step 1205, the MS Server sends the format-converted short message to the terminal UE1 identified by the retrieved MIHFID.

Step 1206, UE1 returns a status report message in MIH format to the MS Server.

In this step, the status report message returned by UE1 to the MS Server includes: the MIHF ID of the terminal (source MIHF identification), the MIHF ID of the MS Server (destination MIHF identification), the service type of the message and the sending status information of the message. If there is an error in sending, it also includes information such as the error code and the cause of the error.

Step 1207, MS Server finds out the corresponding MSISDN from the content saved by itself according to the MIHF ID of UE1 carried in the status report message, and converts the status report message into MAP format according to the message type being a short message.

Step 1208, MS Server sends the status report message after format conversion to GMSC.

Step 1209, GMSC forwards the status report message to SMSC.

The system architecture shown in FIG. 9 is further described below by taking the intercommunication of message services between an IP network that does not support the MIH protocol and a network that supports the MIH protocol as an example.

FIG. 13 is a structural block diagram of a system for implementing message service interworking between an access network supporting MIH and an IP network according to an embodiment of the present invention. As shown in Figure 13, the system includes: a store-and-forward server, a routing information server, a message server MS Server set in an access network supporting the MIH protocol, a gateway set in an IP network, a UE1 supporting the MIH protocol, and an IP Protocol UE2.

In Figure 13, if the store-and-forward server and routing information server are located in a network that supports MIH, then MS Server does not need to perform format conversion processing when forwarding messages, and GW needs to perform format conversion between MIH format and IP format when forwarding messages Conversion processing; if the store-and-forward server and routing information server are located in the IP network, then the MS Server performs conversion processing between the MIH format and the IP format when forwarding the message, and the GW does not need to perform format conversion processing when forwarding the message; if the store When the forwarding server and routing information server are located in the GSM network, the MSServer performs conversion processing between the MIH format and the MAP format when forwarding the message, and the GW performs conversion processing between the IP format and the MAP format when forwarding the message. The following takes the above-mentioned second case as an example to illustrate the process of UE1 sending and receiving service messages.

FIG. 14 is a flow chart of UE1 in FIG. 13 sending a service message. As shown in Figure 14, the following steps are included:

Step 1401, UE1 sends a service message in MIH format to MS Server.

In this step, the short message sent by UE1 includes: the MIHF ID (source MIHF identification) of UE1, the MIHF ID (destination MIHF identification) of MS Server, the service type of the message and the main content of the short message and the service of the message receiver UE2 Network ID. Since the store-and-forward server and the routing information server are located in the IP network in this embodiment, the service network identifier of UE2 is the IP address of UE2.

Step 1402, after the service message sent by UE1 received by MS Server, according to the MIHF ID of UE1 carried in the service message, find out the IP address corresponding to the MIHF ID of UE1 from the association information of the MIHF ID and IP address saved by itself, according to The type of the message is a short message. The received service message in the MIH format is converted into a service short message in the IP format.

In step 1403, the MS Server sends the converted service message in IP format to the store-and-forward server, and the message carries the IP address of UE1 and the IP address of UE2.

Step 1404, the store-and-forward server sends the received service message to the destination according to the IP address of the recipient UE2, and then returns a status report message in IP format to the MS Server, which carries the IP address of UE1.

In this step, the process for the store-and-forward server to send the received service message to UE2 is an existing process, which mainly includes: the store-and-forward server sends the service message to GW, and GW then sends the service message to UE2, which will not be described in detail here .

Step 1405, after receiving the status report message, the MS Server searches out the corresponding MIHF ID according to the IP address therein, and converts the status report message into MIH format.

Step 1406, the MS Server sends the status report message in MIH format to the terminal UE1 identified by the queried MIHF ID.

In this step, the status report message includes: the MIHF ID (source MIHF identification) of MS Server, the MIHF ID (destination MIHF identification) of the terminal, the service type of the message and the sending status information of the message. If there is an error sending the message, it also includes the error code and the reason for the error.

FIG. 15 is a flowchart of UE1 in FIG. 13 receiving a service message. As shown in Figure 15, the following steps are included:

Step 1501: After the store-and-forward server receives the service message in IP format sent by UE2 to UE1, it uses the IP address of UE1 carried in the service message to query the routing information of UE1 from the routing information server, and the routing information server returns UE1's current status to the store-and-forward server. The address of the MSServer where it is located.

Step 1502, the store and forward server sends the received service message to MS Server.

Step 1503, after the MS Server receives the short message, it retrieves the MIHF ID corresponding to the IP address of UE1 carried in the service message from the associated information of the MIHF ID and IP address saved by itself, and sends the received service message in IP format Convert business messages into MIH format.

Step 1504, the MS Server sends the format-converted service message to the terminal UE1 identified by the retrieved MIHF ID.

Step 1505, UE1 returns a status report message in MIH format to the MS Server.

In this step, the status report message returned by UE1 to the MS Server includes: the MIHF ID of the terminal (source MIHF identification), the MIHF ID of the MS Server (destination MIHF identification), the service type of the message and the sending status information of the message. If there is an error in sending, it also includes information such as the error code and the cause of the error.

Step 1506, MS Server finds out the corresponding IP address from the content saved by itself according to the MIHF ID of UE1 carried in the status report message, and converts the format of the status report message into the service type of IP format according to the service type of the message.

Step 1507, MS Server sends the status report message after format conversion to the store and forward server.

UE1 in FIG. 13 can send and receive service messages in a network supporting the MIH protocol through the processes shown in FIG. 14 and FIG. 15 .

Based on the above-mentioned embodiments, a structural block diagram of a message server and a terminal in an embodiment of the present invention is given next.

Fig. 16 is a structural block diagram of a message server according to an embodiment of the present invention. As shown in FIG. 16 , the message server includes: a media independent switching module 1601 , a format converting module 1602 and a sending and receiving module 1603 .

In FIG. 16 , the media independent switching module 1601 is configured to send the service message in the MIH format from the terminal to the format conversion module 1602; send the service message in the MIH format from the format conversion module 1602 to the terminal 1603;

The format conversion module 1602 is used to receive the business message sent by the media independent switching module 1601, and send it to the transceiver module 1603 after performing format conversion processing; receive the business message sent by the transceiver module 1603, and convert it into MIH format before sending it to refer to the media independent switching Module 1601;

The transceiver module 1603 is configured to send the service message from the format conversion module 1602 to the store-and-forward server; and send the service message from the store-and-forward server to the format conversion module 1602 .

The message server shown in FIG. 16 may also include a storage module 1604, configured to store the correspondence between the MIHF ID of the terminal and the service network identifier. At this time, the media independent switching module 1601 is used to query the corresponding MIHF ID from the storage module according to the service network identification of the message receiving terminal carried in the service message after receiving the service message sent by the format conversion module 1602, and The service message is sent to the terminal corresponding to the MIHF ID that is inquired out; Format conversion module 1602 is used for after receiving the service message sent by the media independent switching module 1601, according to the MIHF ID of the terminal carried in the service message from storage The corresponding service network ID is found in the module, and the message format supported by the network where the store-and-forward server is located is determined according to the service network ID or the service type of the message, and the service message is converted into a message of a corresponding format and then sent to the transceiver module 1603.

In FIG. 16, the media independent switching module 1601 is further configured to send the MIHF ID and the service network identification sent by the terminal to the storage module 1604 for storage, and send the service network identification to the The transceiver module 1603; the transceiver module 1603 is further configured to send the service network identifier of the terminal and the address of the message server where the terminal is located to the routing information server.

Fig. 17 is a structural block diagram of a terminal according to an embodiment of the present invention. As shown in FIG. 17, the terminal includes: a media independent switching module 1701, configured to send a service message in MIH format to a message server, and receive a service message in MIH format sent by the message server.

In Fig. 17, the media independent switching module 1701 is further configured to send the MIHF ID and service network identification of the terminal where itself is located to the message server.

To sum up, in the embodiment of the present invention, a message server is set in the access network supporting the MIH protocol; the message server and the terminal in the access network where it is located carry out service message transmission through the MIH protocol, and the store-and-forward server through The protocol supported by the network where the store-and-forward server is located transmits business messages, and the technical solution for converting business messages between the MIH protocol format and the protocol format supported by the network where the store-and-forward server is located makes the access network that supports the MIH protocol It can realize the transmission of business information.

The above is only a preferred embodiment of the present invention, and is not used to limit the protection scope of the present invention. Any modification, equivalent replacement, improvement, etc. made within the spirit and principles of the present invention shall include Within the protection scope of the present invention.

Claims (16)

1. a system that realizes message service interconnection is characterized in that, this system comprises: storage forwarding server and be arranged at support media and independently switch message server in the access network of MIH agreement, wherein,

Described message server comprises: media independent handovers module, format converting module and transceiver module;

Described media independent handovers module is used for the service message of the MIH form that receiving terminal sends, and the service message of the MIH form of self terminal sends to format converting module in the future; To send to terminal from the service message of the MIH form of format converting module;

Described format converting module is used for the service message of the MIH form that receiving media independence handover module sends, and the service message of described MIH form is sent to transceiver module with the message format of storage forwarding server place network support; Receive the service message that transceiver module sends, and the service message that described transceiver module is sent is sent to the media independent handovers module with the MIH form;

Described transceiver module is used to receive the service message that the storage forwarding server sends, and will send to format converting module from the service message of storage forwarding server; To send to the storage forwarding server from the service message of format converting module;

Described storage forwarding server is used to receive service message, and according to recipient's routing iinformation of described service message service message is sent.

2. the system as claimed in claim 1 is characterized in that, this system further comprises: the routing iinformation server is used to preserve routing iinformation;

Described storage forwarding server also is used for the sign according to the recipient of the service message that receives, from recipient's routing iinformation of the service message of the described reception of described routing iinformation server lookup.

3. system as claimed in claim 2 is characterized in that,

Described message server further comprises: memory module is used to preserve the media independent handovers entity identification MIHF ID of terminal and the corresponding relation between the service network identification;

Described transceiver module also is used for the routing iinformation to described routing iinformation server transmission terminal; The routing iinformation of described terminal comprises the service network identification of terminal and the address of message server self.

4. system as claimed in claim 3 is characterized in that,

Described media independent handovers module, be used for behind the service message that receives the format converting module transmission, service network identification according to the message sink terminal of carrying in this service message inquires corresponding MIHF ID from memory module, and service message is sent to and the corresponding terminal of MIHF ID that is inquired;

Described format converting module, be used for behind the service message that receives the transmission of media independent handovers module, MIHF ID according to the terminal of carrying in this service message inquires corresponding service network identification from memory module, determine the message format of storage forwarding server place network support according to the traffic type information of carrying in service network identification or this service message, be sent to transceiver module after service message being converted to the message of corresponding format.

5. system as claimed in claim 3 is characterized in that,

Described storage forwarding server, be used for after receiving service message, service network identification according to the message receiver that wherein carries goes out corresponding message server address from the routing iinformation server lookup, and the service message that is received is sent to and the corresponding message server in message server address that is inquired.

6. as each described system in the claim 1 to 5, it is characterized in that this system further comprises: be arranged at the gateway in the access network of not supporting the MIH agreement;

Described gateway after being used for converting the service message that the terminal of self place access network sends the message format of storage forwarding server place network support to, sends to the storage forwarding server; After will converting the message format that self place access network supported from the service message of storage forwarding server to, send to the terminal in self place access network.

7. a method that realizes message service interconnection is characterized in that, this method comprises:

Be arranged at support media and independently switch the service message of the MIH form that the message server receiving terminal in the access network of MIH agreement sends, service message according to described MIH form is determined corresponding storage forwarding server, with the service message of described MIH form message format, send to described storage forwarding server with the place network support of storage forwarding server;

This message server comprises: media independent handovers module, format converting module and transceiver module, wherein,

The media independent handovers module is used for the service message of the MIH form that receiving terminal sends, and the service message of the MIH form of self terminal sends to format converting module in the future; To send to terminal from the service message of the MIH form of format converting module;

Format converting module is used for the service message of the MIH form that receiving media independence handover module sends, and the service message of described MIH form is sent to transceiver module with the message format of storage forwarding server place network support; Receive the service message that transceiver module sends, and the service message that described transceiver module is sent is sent to the media independent handovers module with the MIH form;

Transceiver module is used to receive the service message that the storage forwarding server sends, and will send to format converting module from the service message of storage forwarding server; To send to the storage forwarding server from the service message of format converting module.

8. method as claimed in claim 7 is characterized in that, this method also comprises:

Receive and store the service message that forwarding server sends, determine corresponding terminal, the service message of described storage forwarding server transmission is sent to the terminal of described correspondence with the MIH form according to the service message that described storage forwarding server sends.

9. method as claimed in claim 7, it is characterized in that, described service message according to described MIH form is determined corresponding storage forwarding server, with the service message of the described MIH form message format with the place network support of storage forwarding server, sends to described storage forwarding server and is:

The MIHF sign of the terminal of carrying in the service message according to described MIH form, the MIHF sign of the terminal that inquiry is preserved and the corresponding relation of service network identification, the MIHF that obtains described terminal of carrying identifies corresponding service network identification;

The traffic type information of carrying in the service message according to the service network identification of described correspondence or described MIH form is determined the message format of storage forwarding server place network support;

When the message format of described storage forwarding server place network support does not comprise the MIH form, the service message of described MIH form is converted to the message format of storage forwarding server place network support after, send to described storage forwarding server; Or, when the message format of described storage forwarding server place network support comprises the MIH form, the service message of described MIH form is directly sent to described storage forwarding server.

10. method as claimed in claim 8 is characterized in that, the described service message that sends according to described storage forwarding server is determined corresponding terminal, and the service message that described storage forwarding server is sent with the terminal that the MIH form sends to described correspondence is:

The network services identification of the terminal of carrying in the service message according to described storage forwarding server transmission, the MIHF sign of the terminal that inquiry is preserved and the corresponding relation of service network identification, the MIHF that obtains the service network identification correspondence of described terminal of carrying identifies;

When the service message of described storage forwarding server transmission was the MIH form, according to the MIHF sign of described terminal, directly the service message that described storage forwarding server is sent sent to described terminal; Or, when the service message of described storage forwarding server transmission is not the MIH form, after the service message that described storage forwarding server is sent converts the MIH form to, according to the MIHF sign of described terminal, with the service message of the MIH form after changing send to described terminal.

11. method as claimed in claim 10, it is characterized in that, before the service message of the MIH form that described receiving terminal sends, or before the described service message that will store the forwarding server transmission sent to the terminal of described correspondence with the MIH form, this method further comprised:

The service message subscribe request that receiving terminal sends, described service message subscribe request comprise the MIHF sign and the service network identification of described terminal in the network of storage forwarding server place of described terminal;

Preserve the MIHF sign of described terminal and the corresponding relation of service network identification, and sending the routing iinformation of described terminal to the routing iinformation server, described routing iinformation comprises the address of the message server of the service network identification of described terminal and described terminal correspondence.

12. method as claimed in claim 11 is characterized in that, before the service message subscribe request that described receiving terminal sends, this method further comprises:

Receive the registration message that described terminal sends, described registration message comprises the MIHF sign of described terminal; Preserve the MIHF sign of described terminal.

13. method as claimed in claim 11 is characterized in that, in any moment after the service message of accepting described terminal is subscribed to, this method further comprises:

Receive the request of cancelling subscriptions of carrying described terminal self MIHF sign that described terminal sends; According to MIHF ID and the traffic type information in the described request of cancelling subscriptions, judge whether terminal has also subscribed to other messaging service, otherwise the corresponding relation of the MIHF of the described terminal that deletion is preserved sign and service network identification, and sending the cancellation route messages of the service network identification of carried terminal to the routing iinformation server, described cancellation route messages is used for informing deletion of routing iinformation server and the corresponding routing iinformation of service network identification of cancelling route messages; Perhaps

Send the cancellation route messages of the service network identification of carried terminal to the routing iinformation server, described cancellation route messages is used for informing deletion of routing iinformation server and the corresponding routing iinformation of service network identification of cancelling route messages, and sending the notice that cancels subscriptions to terminal, the MIHF of the described terminal that deletion is preserved identifies and the corresponding relation of service network identification.

14. a message server is characterized in that, this message server comprises: media independent handovers module, format converting module and transceiver module, wherein,

The media independent handovers module is used for the service message of the MIH form that receiving terminal sends, and the service message of the MIH form of self terminal sends to format converting module in the future; To send to terminal from the service message of the MIH form of format converting module;

Format converting module is used for the service message of the MIH form that receiving media independence handover module sends, and the service message of described MIH form is sent to transceiver module with the message format of storage forwarding server place network support; Receive the service message that transceiver module sends, and the service message that described transceiver module is sent is sent to the media independent handovers module with the MIH form;

Transceiver module is used to receive the service message that the storage forwarding server sends, and will send to format converting module from the service message of storage forwarding server; To send to the storage forwarding server from the service message of format converting module.

15. message server as claimed in claim 14 is characterized in that, this message server further comprises memory module, is used to preserve the MIHF ID of terminal and the corresponding relation of service network identification;

Described media independent handovers module, be used for behind the service message that receives the format converting module transmission, service network identification according to the message sink terminal of carrying in this service message inquires corresponding MIHF ID from memory module, and service message is sent to and the corresponding terminal of MIHF ID that is inquired;

Described format converting module, be used for behind the service message that receives the transmission of media independent handovers module, MIHF ID according to the terminal of carrying in this service message inquires corresponding service network identification from memory module, determine the message format of storage forwarding server place network support according to the traffic type information of carrying in service network identification or this service message, be sent to transceiver module after service message being converted to the message of corresponding format.

16. as claim 14 or 15 described message servers, it is characterized in that, described media independent handovers module, be further used for behind the MIHF ID and service network identification that receive the terminal transmission, send to memory module and preserve, and described service network identification is sent to transceiver module by format converting module;

Described transceiver module is further used for the service network identification of terminal and the address of self place message server are sent to the routing iinformation server.

Images