CN101325740A

CN101325740A - Method, apparatus and system for implementing intercommunication of conversation initiating protocol message and short message

Info

Publication number: CN101325740A
Application number: CNA2007101261884A
Authority: CN
Inventors: 宋雪飞; 孙谦
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2007-06-15
Filing date: 2007-06-15
Publication date: 2008-12-17

Abstract

The embodiment of the invention discloses a method of sending MESSAGE message to short message (SM) client, comprising: interworking functional entity analyzing the received MESSAGE message, converting into SM and sending to the SM client through the SM server. A method of sending SM to the Session Initialization Protocol (SIP) client comprises: interworking functional entity analyzing the received SM, converting into the MESSAGE message and sending the MESSAGE message to the SIP client through the SIP message server. The embodiment of the invention further discloses a system for interworking message between the SIP message server and the SM client, a SIP message server and an interworking functional entity. Adopting the invention is able to realize the interworking between the SIP message having high practicability and low demand to the client and the short message.

Description

Realize method, the Apparatus and system of conversation initiating protocol message and short message intercommunication

Technical field

The present invention relates to the network interworking technology, particularly method, the Apparatus and system of session initiation protocol (SIP) message and short message (SM) intercommunication.

Background technology

Along with the fusion of mobile communications network and IP network and the development of next generation network, various messenger service have been emerged, for example: Short Message Service (SMS, Short Message Service), Multimedia Message service (MMS, Multimedia Message Service), based on the instant message (IM of SIP, Instant Message) service, based on semiduplex Push to talk over Cellular (PoC, Push to talkover Cellular) voice message service etc.With the corresponding message server of a certain messenger service only for the user who orders this messenger service provides service, use directly intercommunication between the user of different messages service.For example, the user's (being called for short IM user) who uses IM to serve can not be directly by IM and SM telex network.How to realize the intercommunication of IM and SM below by an example explanation prior art.

Fig. 1 realizes in the prior art that the IM client sends the method flow schematic diagram of message to the SM client.Referring to Fig. 1, subscriber equipment (UE) is IM user's a terminal, service call conversation control function (S-CSCF, Service-Call Session Control Function) and IP short messaging gateway (IP-SM-GW, Internet Protocol-Short Message-Gateway) be the functional entity in the 3G network, mobile switching centre/gateway MSC of short message intercommunication function (SMS-IWMSC/GMSC) and SMS service center (SC) are the functional entitys in second generation mobile communication (2G) network.In this example, IM user uses UE to may further comprise the steps to the method that SM user sends message:

Step 1:UE is according to IM user's indication, and the MESSAGE method by SIP sends message to IP Multimedia System (IMS).

In this step, UE can provide several optional messenger service types usually, selects the employed messenger service of message receiver by IM user.In this example, IM user will select SMS, and UE is changed to according to IM user's the selection value with content type among the MESSAGE (Content-Type) field: application/vnd.3gpp.sms, and to comprise a short message in the message body of representing this MESSAGE.

In the SMS layered protocol structure, from top to bottom be divided into successively: application layer, transport layer, relay layer and bottom, its flow chart of data processing is: the user data that comes from application layer is transmitted layer and is configured to transport layer protocol data cell (TPDU) and sends to relay layer, again by relay layer with TPDU as relay layer protocol user data (RP-User-DATA), with of the form packing of information such as sender address, address, purpose side, send by the bottom encapsulation at last with RP-DATA.Therefore, in this MESSAGE, UE address, purpose SC address and the RP-User-DATA of transmit leg need be packed with the form of RP-DATA is carried in the message body.Gou Zao SIP MESSAGE example is as follows in the manner described above:

MESSAGE?sip：TBD@TBD.net?SIP/2.0

Via：SIP/2.0/UDP[5555::aaa:bbb:ccc:ddd]:1357；comp＝sigcomp；branch＝z9hG4bKnashds7

Max-Forwards：70

Route：<sip:pcscf1.visited1.net:7531；lr；comp＝sigcomp>，<sip:orig@scscf1.home1.net；lr>

P-Preferred-Identity:″John?Doe″<sip:user1_public1@home1.net>

From：<sip:user1_public1@home1.net>；tag＝171828

To：<sip:TBD@TBD.net>

Call-ID：cb03a0s09a2sdfglkj490333

Cseq：666MESSAGE

Content-Type：application/vnd.3gPP.sms

Content-Length：(......)

Message body ...

S-CSCF among the step 2:IMS receives above-mentioned MESSAGE, and analyzes this message according to initial filter criteria (iFC, Initial Filter Criteria), determines transmit to IP-SM-GW.

When user's order/modification service order concerns, the proprietary business datum of user will be created with the form of iFC by system, comprise professional trigger condition and corresponding application server among the iFC.Wherein, professional trigger condition can comprise:

Request-unified resource sign (Request-URI), sign SIP request resource pointed; The SIP method, the type of expression SIP request; The SIP header field comprises and the relevant information of this SIP request, can be any SIP header field and header field content wherein.

In this step, the professional trigger condition of setting can comprise: Method type is that SIP MESSAGE and Content-Type are changed to: application/vnd.3gPP.sms; Corresponding application server is IP-SM-GW.So, just can analyze the message that receives, determine and give IP-SM-GW with forwards according to iFC.

Step 3:S-CSCF issues IP-SM-GW with the MESSAGE that receives.

Step 4:IP-SM-GW returns 202 Accept response messages to S-CSCF.

Usually, IP-SM-GW can preserve this user's international integrated services digital network (MSISDN) number of travelling carriage when IM user initiates the third-party registration request, and uses this Mobile Subscriber International ISDN Number sign IM user in follow-up reciprocal process.

Step 5:S-CSCF returns 202 Accept response messages to UE.

Step 6:IP-SM-GW extracts TPDU from the MESSAGE that receives.

Step 7:IP-SM-GW is packaged into relay layer-mobile initial-data (RP-MO-DATA) with the TPDU that extracts and sends to SMS-IWMSC/GMSC.

Step 8:SMS-IWMSC/GMSC sends to SC with the RP-MO-DATA that receives, and follow-up short message to be sent to the process of SM user terminal about SC identical with existing standard, repeats no more.

So far, finish to realize in the prior art method of IM and SM intercommunication.

In said method, IP-SM-GW is used for realizing the protocol interconnection between 2G network and the 3G network, its major function is: use MAP (MAP) agreement to communicate by letter with SMS-IWMSC/GMSC, use IP-based agreement and IM terminal communication, safeguard related etc. between MSISDN and the IM IP address of terminal.

The inventor finds in realizing process of the present invention: prior art is when realizing IM and SM intercommunication, the type that needs user's selection messenger service when sending message of transmission message, that is to say that what the user of requirement transmission message knew the message receiver use is any messenger service; And when the user selected SMS, needing UE to spell out the recipient by the Content-Type among the MESSAGE was SM user, and this practicality to this above-mentioned existing method exerts a certain influence.In addition, carry in the MESSAGE message body be the packing after short message, on the one hand, can not in MESSAGE, embody the characteristic of SMS, can not guarantee the unanimity user experience; On the other hand, require the IM terminal must support the related protocol stack of SMS, user data could be packaged into short message, having relatively high expectations of terminal.Therefore, in order to provide better messenger service and user experience, message intercommunication problem, the especially sip message between the needs solution different system and the intercommunication problem of short message.

Summary of the invention

In view of this, the embodiment of the invention provides a kind of MESSAGE message is sent to the method for SM client, when realizing that MESSAGE message sent to the SM client, reduces the requirement to client.

The embodiment of the invention also provides a kind of method that SM is sent to the SIP client, when realization sends to the SIP client with SM, reduces the requirement to client.

The embodiment of the invention also provides the system of a kind of SIP of realization client and the intercommunication of SM client message, a kind of sip message server and a kind of interworking function entity, for the intercommunication between sip message and the short message provides a kind of practicality height, client is required low system, sip message server and interworking function entity.

For achieving the above object, the technical scheme of the embodiment of the invention specifically is achieved in that

A kind of MESSAGE message is sent to the method for short message SM client, comprising:

Interworking function entity receives MESSAGE message;

Interworking function entity with described MESSAGE message parse, be converted to SM, by the SM server described SM is sent to the SM client.

A kind of method that SM is sent to the SIP client comprises:

Interworking function entity receives SM;

MESSAGE message is resolved, is converted to interworking function entity with described SM, by the sip message server described MESSAGE message sent to the SIP client.

A kind of system that realizes SIP client and the intercommunication of SM client message comprises:

The SIP client is used for sending MESSAGE message to the SM client, receives the MESSAGE message that comes from the SM client;

The SM client is used for sending SM to the SIP client, receives the SM that comes from the SIP client;

Interworking function entity, is converted to SM and sends to the SM server MESSAGE message parse that is used for receiving; And the SM that is used for receiving resolves, is converted to MESSAGE message and sends to the sip message server;

The SM server, the SM that is used for coming from interworking function entity sends to the SM client, and the SM that is used for coming from the SM client sends to interworking function entity;

The sip message server, the MESSAGE message that is used for coming from interworking function entity sends to the SIP client, and the MESSAGE message that is used for coming from the SIP client sends to interworking function entity.

A kind of sip message server comprises:

Communication module is used to receive the MESSAGE message that comprises recipient's user ID, and transmits described MESSAGE message according to the indication of user type judge module;

The user type judge module, be used for judging recipient's type of described MESSAGE message, and indicate described communication module that the recipient is sent to interworking function entity, the recipient is sent to the SIP client for the user's that is fit to receive SIP MESSAGE message MESSAGE message for the user's that be fit to receive SM MESSAGE message according to described recipient's user ID.

A kind of interworking function entity comprises:

The MESSAGE processing module is used to receive MESSAGE message, with described MESSAGE message parse, be converted to SM, and sends described SM;

The SM processing module is used to receive SM, described SM is resolved, is converted to MESSAGE message, and send described MESSAGE message.

As seen from the above technical solution, what the embodiment of the invention provided sends to MESSAGE message in the method for SM client, by the mode of interworking function entity by protocol conversion with the MESSAGE message parse, be converted to SM, make the SIP client need not to support any SM related protocol, only need directly in MESSAGE message body, to carry and treat that a message gets final product, when realization sends to the SM client with MESSAGE message, reduced the requirement of message intercommunication to client.

Similarly, SM being sent in the method for SIP client that the embodiment of the invention provided, because MESSAGE message is resolved, is converted to interworking function entity by the mode of protocol conversion with SM, when realization sends to the SIP client with SM message, reduced the requirement of message intercommunication to client.

In the system of realization SIP client that the embodiment of the invention provided and the intercommunication of SM client, on the one hand, the SM that receives is resolved, is converted to MESSAGE message by interworking function entity; On the other hand, by interworking function entity with the MESSAGE message parse that receives, be converted to SM, make SIP client and SM client only need realize that its corresponding protocol stack gets final product, need not to realize the protocol stack of Correspondent Node, reduced the requirement of message intercommunication client.

The sip message server that the embodiment of the invention provided, by the user type judge module recipient's type of MESSAGE is judged, can determine the route of this MESSAGE, make the SIP client need not to indicate the type of message sink end, improve the practicality of message intercommunication.

The interworking function entity that the embodiment of the invention provided, the MESSAGE message parse that the SIP client is sent by the MESSAGE processing module, be converted to the SM that the SM client can receive, and the SM that the SM client sends is resolved, is converted to the MESSAGE message that the SIP client can receive by the MS processing module, make SIP client and SM client need not to realize that the protocol stack of Correspondent Node can realize message intercommunication, so, reduced the requirement of message intercommunication to client.

Description of drawings

Fig. 1 realizes in the prior art that the IM client sends the method flow schematic diagram of message to the SM client;

Show Fig. 2 SIP client and SM client in the embodiment of the invention realize the method flow schematic diagram of message intercommunication;

Fig. 3 is a composition structural representation of realizing the system of SIP client and the intercommunication of SM client message in the embodiment of the invention;

Fig. 4 is the preferable composition structural representation of sip message server in the embodiment of the invention;

Fig. 5 is the preferable composition structural representation of interworking function entity in the embodiment of the invention;

Fig. 6 is the MO process schematic diagram that the SIP client sends message in the embodiment of the invention to the SM client;

Fig. 7 is the MT course schematic diagram that the SM client sends message in the embodiment of the invention to the SIP client.

Embodiment

For making purpose of the present invention, technical scheme and advantage clearer, below with reference to the accompanying drawing embodiment that develops simultaneously, the present invention is described in further detail.

In the embodiment of the invention, provide SIP MESSAGE message has been sent to the method for SM client and the method that SM is sent to the SIP client, by the combination of these two kinds of methods, can realize the message intercommunication of SIP client and SM client, that is: realize the intercommunication of sip message and SM.Because above-mentioned two kinds of methods relate separately to the both direction that message sends, therefore, describe below by the implementation procedure of a flow chart that comprises above-mentioned two kinds of methods to these two kinds of methods.

Show Fig. 2 SIP client and SM client in the embodiment of the invention realize the method flow schematic diagram of message intercommunication.Referring to Fig. 2, step 201～step 204 is for sending to MESSAGE message the process of SM client, and step 205～step 208 is for sending to SM the process of SIP client.Flow process shown in Figure 2 may further comprise the steps:

Step 201: interworking function entity receives MESSAGE message.

Step 202: interworking function entity with the MESSAGE message parse that receives, be converted to SM.

Step 203: interworking function entity sends to SM server, i.e. SMS service center with SM.

Step 204:SM server sends described SM to the SM client.

Step 205: interworking function entity receives SM.

Step 206: MESSAGE message is resolved, is converted to interworking function entity with the SM that receives.

Step 207: interworking function entity sends to the sip message server with MESSAGE message.

Step 208:SIP message server sends described MESSAGE message to the SIP client.

Dotted arrow shown in Figure 2 represents that described message is not the destination that is directly sent to arrow by the source end of arrow, but may pass through the forwarding of other network entities.

Before above-mentioned steps 201, can also comprise: the sip message server receives SIP client MESSAGE message that send, that comprise recipient's user ID;

The sip message server judges that according to recipient's user ID the recipient of MESSAGE message for being fit to receive the user of SM, transmits the MESSAGE message that is received to interworking function entity then.In embodiments of the present invention, the user that also will be fit to receive SM is called SM user.

In order to make the sip message server can receive the above-mentioned MESSAGE message that the SIP client sends, can set in advance corresponding iFC.For example, the professional trigger condition of this iFC can be set to as follows:

CASE?method＝″MESSAGE″AND?header＝″Accept-Contact″＝″+g.cpm.message″THEN：ROUTE?request?to?the?specified?SIP?Server?Originating?Port?Address

Above-mentioned case representation: if the SIP that receives request is MESSAGE, and Accept-Contact field of request be "+g.cpm.message ", and this business is triggered to the sip message server.Like this, the functional entity in the SIP core net as S-CSCF, receives when meeting the MESSAGE of described professional trigger condition, this MESSAGE will be triggered to the sip message server.

If sip user had determined that the other side was SM user before using SIP client transmission message, so, when sending MESSAGE message, the SIP client is the expansion field relevant with the SM characteristic in MESSAGE message directly, and the Request-URI field and the To field of MESSAGE message be changed to recipient's user ID, the Content-Type field is changed to message/general instant message (Message/CPIM that presents, Common Presence and Instant Messaging), and with the extended field relevant be carried among the MESSAGE with SM.In above-mentioned steps, recipient's user ID can be recipient's a phone unified resource sign (tel URI).

In the above-mentioned steps, the sip message server judges that whether the recipient of MESSAGE message is that SM user's method can be: the sip message server obtains the service ability of recipient's presentation information, preference setting or receiving side terminal equipment according to recipient's user ID, if the service ability of recipient's presentation information, preference setting or receiving side terminal equipment shows the recipient and preferentially uses SM to carry out message communicating that then the recipient is SM user.

The sip message server judges that whether the recipient of MESSAGE message is that SM user's method can also be: the sip message server obtains recipient's network registry information according to recipient's user ID; If network registry information shows that the recipient registers in not supporting the 2G network of Session Initiation Protocol, then described recipient is for being fit to receive the user of SM.

If in the MESSAGE message that the sip message server is received, comprise recipient member's tabulation, that is to say, when recipient's user ID is carried in recipient member's tabulation of MESSAGE message, the sip message server can obtain recipient's user ID earlier from recipient member's tabulation, then, obtain the presentation information corresponding according to each recipient member's user ID again with each recipient member, the service ability of preference setting or recipient's member terminal equipment, at last, with recipient member's presentation information, the service ability of preference setting or recipient's member terminal equipment shows: the recipient member that this recipient member preferentially uses SM to communicate is judged as the user who is fit to receive SM.

The presentation information of above-mentioned message receiver can obtain by the SUBCRIBE and the NOTIFY method of Session Initiation Protocol, concrete preparation method can be with reference to Open Mobile Alliance (OMA, Open Mobile Alliance) presents and the presence service standard that can obtain working group (PAG, Presence and Availablity Group).Preference setting can be passed through XML document management server (XDMS, the XMLDocument Management Server) acquisition of XML document configuration access agreement (XCAP, XML ConfigurationAccess Protocol) from sip application server.The content type of message body can obtain by Content-type the field value of MESSAGE.Do not use the registration of clothes device to corresponding SIP when the message receiver presentation information shows the recipient, promptly the state of this SIP application service is " close " in the presentation information; The content type of message is " text/plain "; The priority of SM was for the highest during the preference of message receiver was provided with, and the sip message server can be judged according to above-mentioned information and adopt SM and message sink side communication so.

After the sip message server judges that the recipient of MESSAGE message is SM user, can comprise: judge whether the length of the message body content of MESSAGE message exceeds the maximum length of SM, when exceeding, this message body content can be split as the sub-message body content of length smaller or equal to the SM maximum length, be the sub-MESSAGE message of a correspondence of message body content structure with each the sub-message body content that obtains again.At this moment, the MESSAGE message of transmitting to interworking function entity should be all sub-MESSAGE message of being constructed.

After message body having been carried out fractionation, can directly construct new MESSAGE message, that is: sub-MESSAGE message according to the mode of foregoing description with sub-message body content.Preferably, constructor MESSAGE message in the following manner: the Content-Type field of sub-MESSAGE message is changed to Message/CPIM, in the message body content of MESSAGE message, carry the sub-message body content of a correspondence, form sub-MESSAGE message, and in the message body of sub-MESSAGE message, carried the related information between the sub-MESSAGE message.The mode of carrying related information between the sub-MESSAG message in message body can be: the field that increases the expression related information in message body.For example, can increase information element prompt field, information element length field and information element data field;

Information element prompt field represents whether the message body of described sub-MESSAGE needs to be connected;

The information element length field, the data length in the expression information element data field;

The information element data field comprises three parameters at least, represents respectively that sequence number is quoted in the connection of current sub-MESSAGE message, is connected the sum and the sequence number of current sub-MESSAGE message in being connected sub-MESSAGE message of sub-MESSAGE message.

If in above-mentioned steps, the sip message server does not have the message body content of the MESSAGE message that exceeds the SM maximum length is split, so, in step 202, can split this message body content by interworking function entity, the mode that splits is: message body content is split as the sub-message body content of length smaller or equal to the SM maximum length, and splitting the sub-SM that resulting each sub-message body content is a correspondence of message content structure, and in each the sub-SM that is constructed, carry the related information between the sub-SM.For example, can be with the transport layer-User Data Header sign (TP-UDHI of the sub-SM of structure, Transport Protocol-User Data Head Indicator) parameter is changed to 1, the information element identification field among the TP-UDH is changed to 00, the information element length field is changed to 03, and the parameter in the information element data field is changed to corresponding value respectively.

For splitting resulting sub-SM, after SM server or SM client received, the sub-SM that will will be mutually related according to the related information among each sub-SM combined, and forms complete SM content.

Preferably, in the above-mentioned steps 203, interworking function entity with the MESSAGE message parse, be converted to SM can resolve MESSAGE message for: interworking function entity according to Session Initiation Protocol message header field and message body, extraction is used to produce the information of SM, and according to the related protocol of SM, for example third generation partner program (3GPP) standard 23040, are the value of corresponding field among the SM with the information translation of being extracted.Here, also can MESSAGE be converted to SM based on the SMPP agreement according to point-to-point short message (SMPP, Short Message Point to Point) agreement.

If in the above-mentioned steps 201, interworking function entity receives the MESSAGE message that comprises displacement (Replace) field, has been converted to SM with identification information is corresponding in this displacement field MESSAGE message and has sent to the SM server.This MESSAGE message that comprises displacement field represent needs will be before this MESSAGE message MESSAGE message that send, corresponding with identification information in the displacement field be replaced into the related content of this MESSAGE message, at this moment, the information of being extracted comprises: identification information in the displacement field and message body, and the information of other relevant fields; With the MESSAGE message parse, can take following mode when being converted to SM:

When the above-mentioned message body that comprises the MESSAGE message of displacement field is sky, can construct the deletion SM that send SM corresponding with described identification information.For example, can construct a transport layer-order-type (TP-Command-Type) parameter value and be changed to 00000010 SM, send this SM to the SM server and just can delete the previous SM that receives on the SM server.

When the message body non-NULL of the above-mentioned MESSAGE message that comprises displacement field, except that deletion of structure SM of sending SM corresponding, also need be that message content is constructed a SM with the message body of described MESSAGE message with described identification information.For example, can construct an aforesaid TP-Command-Type parameter value and be changed to 00000010 SM, and to construct one be the SM of message content with the described message body that comprises the MESSAGE of displacement field, the SM that is constructed is sent to the SM server.

When the message body non-NULL of the above-mentioned MESSAGE message that comprises displacement field, also can construct the displacement SM that send SM corresponding with described identification information.For example, can be with the described MESSAGE message parse that comprises displacement field, be converted to the replace_if_present_flag parameter value and be changed to 1 SM, SM that send, corresponding with a certain identification information before this SM represents to replace.

In actual applications, the parameter or the field that also will exist some other needs to carry out special processing in the follow-up embodiment of the present invention, will provide detailed example, for reference to implementing, do not repeat them here.

Before above-mentioned steps 205, can also comprise: the SM server receives SM client SM that send, that comprise recipient's user ID;

The SM server is determined route according to described recipient's user ID, according to described route described SM is transmitted to interworking function entity.

Above-mentioned SM server determines that the mode of route can be: send routing inquiry request to HLR/HSS, by HLR/HSS corresponding routing iinformation is sent to the SM server; Also can be: the SM server be judged number section that this Mobile Subscriber International ISDN Number is affiliated according to the recipient's Mobile Subscriber International ISDN Number that is comprised among the SM, and determines this SM is sent to which network entity according to the described section.

Preferably, in above-mentioned steps 206, interworking function entity with SM resolve, be converted to MESSAGE message mode can for: interworking function entity is resolved the value of each field among the SM according to the related protocol of SM, extraction is used to produce the information of MESSAGE message, and is the value of corresponding field in the MESSAGE message according to Session Initiation Protocol with the information translation of being extracted.

When carrying out SM to the conversion of MESSAGE, a further field of extended description SM characteristic in the CPIM of MESSAGE message content, with exist in the SM agreement and at the part or all of SM field description that does not have corresponding relation between SM agreement and the Session Initiation Protocol in CPIM field of this expansion.In the follow-up embodiment that provides of the present invention, how MESSAGE message is expanded providing detailed example explanation.

In above-mentioned steps 205, if comprise related information among the SM that interworking function entity receives, then after interworking function entity is resolved the SM that is received, can be further according to related information among the SM and/or message sender address, the message content that will comprise among the SM of related information is combined into complete content.For example, the TP-UDHI parameter is changed to 1 if interworking function entity receives, the information element identification field among the TP-UDH is changed to 00 and comprise the SM of some reference parameters, the above parameter all belongs to related information, these show that described message is association messages, should make up these association messages.Therefore, after interworking function entity is resolved the above-mentioned SM of reception, further, can be according to the reference parameter among the above-mentioned SM, message content to the identical SM of transport layer-initial address (TP-OA) makes up, or adopt other modes that the message content of SM is made up according to related information, obtain complete content; Then, with the message body content structure MESSAGE message of complete content as MESSAGE message.

Further, when the length that in the manner described above SM is made up the complete content that obtains exceeds the maximum length of MESSAGE message body, for example, according to the standard of prior art for exceeding 1300 characters, interworking function entity can connect by INVITE and SIP client, and by MSRP MESSAGE message is sent to the SIP client.

In the said method, the SIP client can be common sip terminal, also can be other entities such as application server of having realized the SIP client functionality.Similarly, the SM client can be common SM terminal, also can be other entities such as application server of having realized the SM client functionality.For example, 1860 servers can be used as a SM client and send message to certain and certain group of SM terminals.

The sip message server can be the message server based on the Session Initiation Protocol service of giving information such as amalgamation IP message service enabler (CPM Enabler), IM server.

The SM server can comprise: SC, SMS-IWMSC, GMSC.Usually above-mentioned three kinds of functional entitys are closed in the prior art and be located on the physical equipment, or SMS-IWMSC and GMSC closed establish, SC is provided with separately.In embodiments of the present invention above-mentioned three kinds of functional entitys are collectively referred to as the SM server.

More than the method that MESSAGE message is sent to the SM client that the embodiment of the invention is provided and the method that SM sends to the SIP client had been described in detail.Below the realization SIP client that the embodiment of the invention provided and system, sip message server and the interworking function entity of SM client message intercommunication are elaborated.

Fig. 3 is a composition structural representation of realizing the system of SIP client and the intercommunication of SM client message in the embodiment of the invention.Referring to Fig. 3, this system comprises:

SIP client 310 is used for sending MESSAGE message to the SM client, receives the MESSAGE message that comes from SM client 320;

SM client 320 is used for sending SM to SIP client 310, receives the SM that comes from SIP client 310;

Interworking function entity 340, is converted to SM and sends to SM server 350 the MESSAGE message parse that is used for receiving; And the SM that is used for receiving resolves, is converted to MESSAGE message and sends to sip message server 330;

SM server 350, the SM that is used for coming from interworking function entity sends to the SM client, and the SM that is used for coming from the SM client sends to interworking function entity;

Sip message server 330, the MESSAGE message that is used for coming from interworking function entity sends to the SIP client, and the MESSAGE message that is used for coming from SIP client 310 sends to interworking function entity 340.

The user ID that preferably, can comprise the recipient in the MESSAGE message that above-mentioned SIP client 310 is sent.

Preferably, SM server 350 can be determined the route of this SM according to recipient's user ID after receiving SM, particularly: when the recipient who judges described SM is SM user, send described SM to described SM client 320; When the recipient who judges described SM is sip user, send described SM to described interworking function entity 340.

Preferably, sip message server 330 when determining that according to recipient's user ID the recipient of described MESSAGE message is SM user, is transmitted described MESSAGE message to interworking function entity 340 after receiving MESSAGE message; When the recipient who judges described MESSAGE message is sip user, transmit described MESSAGE message to described SIP client 310.

Fig. 4 is the preferable composition structural representation of sip message server in the embodiment of the invention.Referring to Fig. 4, shown in the sip message server comprise:

Communication module 410 is used to receive the MESSAGE message that comprises recipient's user ID, and transmits described MESSAGE message according to the indication of user type judge module;

User type judge module 420, be used for judging recipient's type of described MESSAGE message, and indication communication module 410 sends to the recipient interworking function entity 340, the recipient is sent to SIP client 310 for the user's that is fit to receive SIP MESSAGE message MESSAGE message for the user's that be fit to receive SM MESSAGE message according to described recipient's user ID.

Preferably, can in the user type judge module 420 of sip message server shown in Figure 4, user capability acquiring unit 421 be set.This user capability acquiring unit 421 is used for obtaining according to recipient's user ID of MESSAGE message the service ability of recipient's presentation information, preference setting or receiving side terminal equipment, and provides accessed information to user type judge module 420.At this moment, user type judge module 420 can be judged recipient's type of MESSAGE according to the service ability of recipient's presentation information, preference setting or receiving side terminal equipment.

Further, can comprise in the sip message server shown in Figure 4: MESSAGE length judge module 430 and MESSAGE split module 440.

Wherein, MESSAGE length judge module 430, when user type judge module 420 is judged the recipient for after being fit to receive the user of SM, described MESSAGE length judge module 430 is used to judge whether the message body content length of MESSAGE message exceeds the SM maximum length, when exceeding the SM maximum length, notice MESSAGE splits module 440, when not exceeding the SM maximum length, and notifying communication module 410;

MESSAGE splits module 440, be used for notice according to MESSAGE length judge module 430, the recipient is split as the sub-message body content of length smaller or equal to the SM maximum length for the message body content that user, the length that is fit to reception SM exceeds the MESSAGE message of SM maximum length, and each the sub-message body content that obtains with fractionation is the sub-MESSAGE message of a correspondence of message body content structure, sends the sub-MESSAGE message of being constructed by communication module 410;

Communication module 410 is used for sending described MESSAGE message according to the notice of MESSAGE length judge module 430.

Further, MESSAGE splits module 440 when with sub-message body content being message body content constructor MESSAGE message, is used for carrying related information between the sub-MESSAGE message the message body of the sub-MESSAGE message of being constructed.

Fig. 5 is the preferable composition structural representation of interworking function entity in the embodiment of the invention.Referring to Fig. 5, this interworking function entity comprises:

MESSAGE processing module 510 is used to receive the MESSAGE message that the sip message server sends, and with the MESSAGE message parse, be converted to SM, and sends the SM that is converted to;

SM processing module 520 is used to receive the SM that the SM server sends, and SM is resolved, is converted to MESSAGE message, and sends the MESSAGE message that is converted to.

Preferably, can comprise in the MESSAGE processing module 510 shown in Figure 5:

MESSAGE receiving element 511 is used to receive the MESSAGE message that the sip message server sends;

MESSAGE resolution unit 512 is used for resolving according to Session Initiation Protocol the message header field and the message body of the MESSAGE message that described MESSAGE receiving element 511 receives, and extracts the information that is used to produce SM;

MESSAGE converting unit 513, the information translation that is used for according to the SM agreement described MESSAGE resolution unit 512 being used to of extracting being produced SM is the value of SM corresponding field;

SM transmitting element 514 is used to send the SM that described MESSAGE converting unit 513 is changed.

And, can also in MESSAGE processing module 510, further be provided with: MESSAGE length judging unit 515 and MESSAGE split cells 516.

Wherein, MESSAGE length judging unit 515, be used to receive the message body content that described MESSAGE resolution unit 512 parses, whether the length of judging described message body content exceeds the SM maximum length, when exceeding the SM maximum length, notice MESSAGE split cells 516, when not exceeding the SM maximum length, notice MESSAGE converting unit 513;

MESSAGE split cells 516, be used for notice according to MESSAGE length judging unit 515, the message body content that length is exceeded the maximum length of SM is split as the sub-message body content of length smaller or equal to the SM maximum length, will split resulting sub-message body content and send to MESSAGE converting unit 513;

MESSAGE converting unit 513 is used for the notice according to MESSAGE length judging unit 515, and the information translation that being used for of being extracted is produced SM according to the SM agreement is the value of SM corresponding field.

Further, MESSAGE converting unit 513 is used for sub-message body content constructor SM the time, carries the related information between the sub-SM in each sub-SM of described structure.

Preferably, can comprise in the SM processing module 520 shown in Figure 5:

SM receiving element 521 is used to receive the SM that the SM server sends;

SM resolution unit 522 is used for the value according to each field of SM of described SM receiving element 521 receptions of SM protocol analysis, extracts the information that is used to produce MESSAGE message;

SM converting unit 523, the information translation that is used for according to Session Initiation Protocol described SM resolution unit 522 being used to of extracting being produced MESSAGE message is the value of MESSAGE message corresponding field;

MESSAGE transmitting element 524 is used to send the MESSAGE message that described SM converting unit 523 is changed.

And, can also in SM processing module 520, further be provided with:

SM assembled unit 525 is used for resolving the information that obtains according to described SM resolution unit 522, the content of the identical SM of TP-OA is made up, and the result that will make up sends to described SM converting unit 523.

Below in conjunction with the accompanying drawings method, the Apparatus and system that the embodiment of the invention provided had been described in detail.Be the CPM service enabler with the sip message server below, interworking function entity is IWF (InterWorking Functionality), SMS-IWMSC, GMSC close and are made as SMS-IWMSC/GMSC in the SM server, SC is divided into example, by more detailed embodiment the embodiment of embodiment of the invention method, Apparatus and system is described.

In the communications field,, then be called as MT course to the process that message receiver sends message by message server if the process that message sender is initiated communication to message server is called MO process.Accordingly, SIP client of the present invention can be considered as a MO process to the process that interworking function entity sends MESSAGE message, so, interworking function entity is MT course with SM to the process that the SIP client sends.In the following description, will realize that the process of message intercommunication is divided into above-mentioned two stages and describes to SIP client and SM client, and in the following description, sip user will be called user 1, SM user will be become user 2.

Fig. 6 is the MO process schematic diagram that the SIP client sends message in the embodiment of the invention to the SM client.Referring to Fig. 6, UE shown in the figure is user 1 a terminal, and this process may further comprise the steps:

Step 601: user 1 uses UE to send message by the MESSAGE method of Session Initiation Protocol to user 2.Can in this MESSAGE, directly carry user 2 tel URI and the message that user 1 will send to user 2, and the Content-Type field needn't be changed to application/vnd.3gpp.sms.Gou Zao SIP MESSAGE example is as follows in the manner described above:

MESSAGE tel:13987654321SIP/2.0 // method, Request-URI and protocol type

Via：SIP/2.0/TCP?user1?pc.domain.com；branch＝z9hG4bK776sgdkse

The node of // transport layer protocol, process and Transaction Identifier

Max-Forwards:70 // max-forwards number

From:sip:user1@domain.com; Tag=49583 // message sender user ID

To:tel:13987654321 // message receiver user ID

Call-ID: Asd88asd77a@1.2.3.4The unique identification of // message

The sequence identification of CSeq:3MESSAGE // affairs

Content type in Content-Type:text/plain // message body

Content-length in Content-Length:18 // message body

Watson, come here. // message body

As previously mentioned, before this step, can set in advance meeting the iFC of the message trigger of certain professional trigger condition to the CPM service enabler, when professional trigger condition meets, can be with message trigger to the CPM service enabler.The CPM service enabler is the communication experiences that a kind of terminal use of being used to provides fusion, realizes the functional entity with existing service-interworking simultaneously.Here, the related content of the trigger process of message and iFC can be with reference to the associated description of 3GPP technical specification 23228.

Step 602:CPM service enabler returns the 202Accept response message to UE after receiving MESSAGE.

Step 603:CPM service enabler judges that user 2 is SM user, promptly judges and can communicate by letter with user 2 by the form of SM.

In this step, the CPM service enabler can obtain the service ability etc. of user 2 presentation information, preference setting or terminal equipment according to user 2 tel URI, and judges according to service ability of the user's 2 who is obtained presentation information, preference setting or terminal equipment etc. whether user 2 is SM user.

If the CPM service enabler receives the MESSAGE that comprises member's tabulation and message content in the message body in this step, for example, receive MESSAGE as follows:

MESSAGE?sip：list-service.example.com?SIP/2.0

Via：SIP/2.0/TCP?uac.example.com；branch＝z9hG4bKhjhs8ass83

Max-Forwards：70

To：MESSAGE?URI-list?Service<sip:list-service.example.com>

// recipient address is member's tabulation

From；Alice<sip:alice@example.com>；tag＝32331

Call-ID：d432fa84b4c76e66710

CSeq：1?MESSAGE

Require：recipient-list-message

Content-Type：multipart/mixed；boundary＝″boundary1″

Comprise a plurality of parts in the // message body, separate with boundary1 between the each several part

Content-Length：501

--boundary?1

Content-Type:text/plain // content type is a text

Hello?World！

--boundary?1

Content-Type：application/resource-lists+xml

// content type is tabulation and extend markup language (XML)

Content-Disposition：recipient-list

<？xml?version＝″1.0″encoding＝″UTF-8″？>

<resource-lists?xmlns＝″urn:ietf:params:xml:ns:resource-lists″

xmlns:cp＝″urn:ietf:params:xml:ns:copycontrol″>

＜list〉// recipient member's tabulation

＜entry uri=" tel:1392888881 "/〉 // each recipient member's tel URI

<entry?uri＝″tel：1392888882″/>

<entry?uri＝″tel：1392888883″/>

<entry?uri＝″tel：1392888884″/>

</list>

</resource-lists>

--boundary?1--

The CPM service enabler can be distributed message content according to the list information in the message body after receiving above-mentioned MESSAGE.If the CPM service enabler is judged this member according to the service ability of certain member's presentation information, preference setting or terminal equipment and can be communicated by the mode of SM when message is distributed, be that certain member is SM user, the CPM service enabler should send to IWF with this member's the MESSAGE that gives to be sent so.

In this step, after some or a plurality of recipient members in judging user 2 or member tabulation are SM user, can judge further whether the length of SIP MESSAGE message body has surpassed the maximum length of SM, when the length of judging message body has surpassed the maximum length of SM, the CPM service enabler can split the message body of this MESSAGE, produce a plurality of sub-message bodies, be message body constructor MESSAGE with each the sub-message body that is produced again, again by IWF in subsequent processes, the sub-MESSAGE after splitting is resolved, converts to SM send.Here, can split, for example, MESSAGE is split as a plurality of sub-message body of length smaller or equal to the SM maximum length according to the length of MESSAGE message body and the maximum length of SM.

For the sub-message body that fractionation obtains, present embodiment provides the mode of two kinds of constructor MESSAGE:

First kind of mode: each sub-message body is placed corresponding sub-MESSAGE as message body, the Content-Type field of sub-MESSAGE is changed to Message/CPIM, and various extended descriptions that will be relevant with SM are in an extended message field of MESSAGE message body.With message body length is that the MESSAGE of 1200 characters is an example, when SM adopts the digital coding of nothing compression GSM7 bit default character, the maximum length of SM is 153 characters, the CPM service enabler can split into 8 sub-message bodies with described MESSAGE message body, correspondingly construct 8 sub-MESSAGE, and in the message body of sub-MESSAGE, carry the related information between the sub-MESSAGE.For example, can in sub-MESSAGE message body, expand as following field:

NS：SMSFeatures<urn:ietf:params:smsFeatures>

SMSFeatures.InformationElementIndicator：00

SMSFeatures.InformationElementLength：03

SMSFeatures.InformationElementData：cshrn＝04；mnsm＝08；sncsh＝05

Wherein, NS is a NameSpace.Above-mentioned example has been expanded three stature fields, is respectively:

Information element prompt (SMSFeatures.InformationElementIndicator) field,

Information element length (SMSFeatures.InformationElementLength) field,

Information element data (SMSFeatures.InformationElementData) field, they correspond respectively to the parameter among the TP-UDH among the SM.Wherein, when the value of SMSFeatures.InformationElementIndicator is changed to 00, represent that described message is a connected message; The value of SMSFeatures.InformationElementLength is 03, data length among the expression SMSFeatures.InformationElementData is 3, three parameters are arranged among the SMSFeatures.InformationElementData, wherein, cshrn represents that current MESSAGE connects and quotes sequence number, mnsm and represent to be connected sum, the sncsh of MESSAGE and represent the sequence number of current MESSAGE in being connected MESSAGE.After IWF receives MESSAGE, can resolve the relevant parameter that obtains among the SM according to a field of these expansions:

The information element that SMSFeatures.InformationElementIndicator is corresponded among the SM identifies (IEI, Information-Element-Indicator), SMSFeatures.InformationElementLength is corresponded to information element length (IEL among the SM, Information-Element-Length), three parameters among the SMSFeatures.InformationElementData are corresponded to SM information element data (IED, Information-Element-Data) relevant parameter in respectively.According to above-mentioned corresponding relation, can obtain the value of TP-UDH relevant parameter among the SM as follows:

[01] Length of TP-UDH // User Data Header message length

[02] IEI=Concatenated short messages[00] // 00 the expression SM for being connected SM

[03] number of Length=03 // parameter

[04] Octet=04 // parameter 1

[05] Octet=08 // parameter 2

[06] Octet=05 // parameter 3

The second way: only sub-message body is carried among the new MESSAGE, MESSAGE is not expanded.Be that the SIP MESSAGE of 1200 characters is an example equally with message body length, when SM adopts the digital coding of nothing compression GSM7 bit default character, the CPM service enabler is split as 8 sub-message bodies with message body, and structure 8 the SIP MESSAGEs corresponding with described 8 sub-message bodies.Described 8 MESSAGE are used identical call identification (Call-ID) field value, and each MESSAGE passes through CSeq order of the field numbering.The example of SIP MESSAGE after the fractionation is as follows:

MESSAGE?tel：13987654321?SIP/2.0

Via：SIP/2.0/TCP?userlpc.domain.com；branch＝z9hG4bK776sgdkse

Cpmenabler.domain.com；branch＝z9hg4bkfjieuaoe9

Max-Forwards：70

From：sip:user1@domain.com；tag＝49583

To：tel：13987654321

The unique identification of Call-ID:asd88asd77a@1.2.3.4 // message

The sequence identification of CSeq:3MESSAGE // affairs

Content-Type：text/plain

Content-Length：153

... // message body

If in this step, MESSAGE message body is split, then the CPM service enabler need all send to IWF with splitting a plurality of sub-MESSAGE that is constructed after the message body.

Step 604:CPM service enabler is transmitted the described MESSAGE message of step 603 by the MESSAGE method of Session Initiation Protocol to IWF.

Step 605:IWF returns 202 Accept response messages to the CPM service enabler.

Step 606:IWF resolves, is converted to SM by the mode of protocol conversion with the SIP MESSAGE that receives.

In this step, IWF can resolve message header field and the message body of MESSAGE according to Session Initiation Protocol, extracts the information be used to produce SM, and is corresponding field among the SM according to the SM agreement with the information translation of being extracted.Below by some examples, the conversion that how to realize from MESSAGE to SM is described.For example:

Relay layer-originating address among the SM (RP-OA) is the message sender address, corresponding to the field of the From among the MESSAGE, can obtain user 1 tel URI according to the value inquiry HSS of From field, convert thereof into the RP-OA parameter value of following 3GPP standard 23040 then.

Relay layer-destination address among the SM (RP-DA) is the address of SMS service center.The SMS service center address of can be in IWF pre-configured and its intercommunication, when changing, can be with described pre-configured SMS service center address as the RP-DA parameter value.

Transport layer-destination address among the SM (TP-DA) is the message receiver address, corresponding to the field of the To among the MESSAGE, can convert To field value to follow 3GPP standard 23040 TP-DA parameter value.

Relay layer-user data among the SM (RP-UD) is the TPDU of SM, corresponding to the message body among the MESSAGE, converts the message body of MESSAGE to follow 3GPP standard 23040 TPDU.For other parameter values, IWF can use its default value according to related specifications, perhaps, if having extended field among the MESSAGE, can do corresponding conversion.After above-mentioned parsing, conversion, will obtain part SM parameter as follows:

The SME address of RP-OA:159#6262#1333* // message sender is corresponding to From

RP-DA:135#0013#5000* //address of SC

RP-UD:TPDU // user data is corresponding to MESSAGE message body

This message of TP-MTI:01 // indication sends to SC from travelling carriage (MS)

The Reply Path of SMS-DELIVER is not set among this SM of TP-RP:0 // indication

The address of TP-DA:139#8765#4321* // message receiver is corresponding to To field

The rank of TP-DCS:00010001 // this SM of indication is 1, uses the default character collection

Carrying out SM when conversion, also can MESSAGE be converted to short message based on the SMPP agreement according to point-to-point short message (SMPP, Short MessageService Point to Point) agreement, the example of each parameter value of conversion back is as follows:

Command?Length：30

Command ID:0X00000004 (Submit_sm) // this message of indication mails to SC from MS

Command_status：NULL

Sequence No:0102561 // produced by IWF is used to identify this SM

service_type：NULL

source_addr_ton：NULL

source_addr_npi：NULL

Source_addr:15962621333 // corresponding to From the field of MESSAGE

dest_addr_ton：NULL

dest_addr_npi：NULL

Destination_addr:13987654321 // corresponding to To the field of MESSAGE

esm_class：NULL

protocol?ID：NULL

priority_flag：0

schedule_delivery_time：NULL

validity_period：NULL

registered_delivery_flag：0

replace_if_present_flag：0

data_coding：0

sm_default_msg_id：NULL

Sm_length:18 // corresponding to the Content-Length among the MESSAGE

Short_message:Watson, come here. // corresponding to the message body among the MESSAGE

In the above-mentioned example, command id (Command ID) is used for representing that this is a Submit-sm, that is: the message that is sent to SC by travelling carriage; Sequence number (Sequence No) is produced by IWF, is used for identifying this SM; Source_addr parameter in the message body and destination_addr parameter can be done corresponding being converted to according to the field of the From among the SIP MESSAGE and To field; The message body of MESSAGE is as the short_message parameter value.If do not comprise other special fields among the MESSAGE that IWF receives, then, other parameters of SM can adopt the default value of SMPP agreement regulation.

If in this step, comprise displacement (Replace) field among the SIP MESSAGE that IWF receives, represent that the MESSAGE corresponding with identification information in this displacement field has been converted to SM and sent to the SM server; IWF can do following processing to this MESSAGE so:

Suppose that Replace the field contents that comprises among the MESSAGE is as follows:

Replaces：asd88asd77a@1.2.3.4；to-tag＝92321；from-tag＝49583；id＝3

Represent that then user 1 will replace the previous MESSAGE that sends with new MESSAGE.

If the message body of this MESSAGE is empty, IWF can construct a SM who sends SM that deletion is corresponding with from-tag=49583.For example, IWF can construct a TP-Command-Type parameter value and be changed to 00000010 SM, sends this SM to the SM server and just can delete the previous SM corresponding with from-tag=49583 that receives on the SM server.

If the message body non-NULL of this MESSAGE, IWF at first can construct a TP-Command-Type parameter value and be changed to 00000010 SM, delete that SC receives before going up, with the corresponding SM of MESSAGE of from-tag=49583, then, produce a new SM according to this MESSAGE and send to user 2 by SC.The message content of the new SM that is produced is the message body of described new MESSAGE.

When the message body non-NULL of this MESSAGE, this MESSAGE can also be resolved, is converted to the replace_if_present_flag parameter value and be changed to 1 SM, SM that send, corresponding with from-tag=49583 before this SM represents to replace.

Further, if also comprise inefficacy (Expire) field among the SIP MESSAGE that IWF receives, IWF can be that Expire the field value of MESSAGE realized conversion by the value that the term of validity (validity_period) field is set when MESSAGE is converted to SM so.

If in step 603, the CPM service enabler does not split the MESSAGE message body that length has surpassed the SM maximum length, and so, IWF can be in this step splits the content of MESSAGE message body, and produces a plurality of sub-SM.The TP-UDHI parameter of each SM that is produced is set to 1, also comprises TP-UDH in the user data to be illustrated in except the content of SM; Each user data header all should comprise three parameters, is respectively:

Information element sign (IEI, Information-Element-Indicator), information element length (IEL, Information-Element-Length) and the information element data (IED, Information-Element-Data).Wherein, the IEI parameter is set to 00, represents that this is one and connects short message, and the IEL parameter is set to 03, and the IED parameter comprises three parts, and expression connects the number of references of short message, the sum and the sequence number of current short message in all short messages of connection short message respectively.For the SIP MESSAGE that a message body length is 1200 characters, when adopting nothing compression GSM7 bit default character digital coding SM, the IED parameter is respectively 4,8,5, and the TP-UD example relevant with connecting short message is as follows:

[00] TP-UDL[23] // total length of user data is 23

[01] Length of TP-UDH[05] // the User Data Header message length is 5

[03] Length=03 //comprise 3 parameters in the IED field

[04]Octet＝04

[05]Octet＝08

[06]Octet＝05

+ 1Fill bits // 1 bit filler

+ 22 seven-bit character message text //content of text of SM

For each SM after splitting, IWF should guarantee to produce the TP-MR parameter value according to the order that increases progressively, and other relevant parameter values should be followed 3GPP technical specification 23040 and produce.

If in step 603, the CPM service enabler splits the MESSAGE message body that exceeds the SM maximum length, and expanded during new MESSAGE at structure and to be used to describe a field that splits message, as SMSFeatures.InformationElementIndicator etc., a field of described expansion can be corresponded among the SM, particularly so:

SMSFeatures.InformationElementIndicator field among the MESSAGE is corresponded to IEI among the SM; SMSFeatures.InformationElementLength field among the MESSSGE is corresponded to IEL among the SM; Cshrn among the SMSFeatures.InformationElementData, mnsm, sncsh are corresponded to three parameters among the IED among the SM respectively.

Further, produce in the example of a plurality of SM at above-mentioned fractionation SIP MESSAGE, if message sender customer requirements return messages delivery report, IWF should produce SIP MESSAGE to message sender return messages delivery report behind the message delivery report that receives all SM so.

If in the content of MESSAGE message body, the content that comprises non-plain text, for example, used extend markup language (XML) form, so, easier processing mode is: this message is shielded to message receiver, or described non-content of text is converted to plain text format, or the form that MESSAGE is converted to the Short Message Service (EMS, Enhanced Message Service) of enhancing sends, or only keeps the content of plain text.

Step 607:IWF sends SM by MAP to SMS-IWMSC/GMSC.

Step 608:SMS-IWMSC/GMSC sends SM by MAP to SC.

Step 609:SC is to the SMS-IWMSC/GMSC status report, i.e. Delivery Report.

Step 6010:SMS-IWMSC/GMSC is to the IWF status report.

Step 6011:IWF converts the SM status report that receives to the form of SIP MESSAGE.

Step 6012:IWF sends MESSAGE message by the MESSAGE method of Session Initiation Protocol to the CPM service enabler.

Step 6013:CPM service enabler sends MESSAGE message to user 1 UE.

Step 6014:UE returns the 200ok success response to the CPM service enabler.

Step 6015:CPM service enabler returns the 200ok success response to IWF.

So far, finish present embodiment SIP client sends MO process from message to the SM client.

As previously mentioned, if user 1 had determined that before sending message user 2 is users that only support SM, user 1 is in above-mentioned steps 601 so, can directly in the SIP MESSAGE that sends, expand the field relevant with the SM characteristic, and the tel URI that Request-URI field and the To field of MESSAGE is changed to user 2, the Content-Type field is changed to Message/CPIM, and the extended field relevant with SM is carried in MESSAGE message body.Gou Zao the MESSAGE example that has comprised SM characteristic relevant parameter is as follows in the manner described above:

MESSAGE tel:13987654321 SIP/2.0//Request-URI is changed to user 2 tel URI

Via：SIP/2.0/TCP?pc1.domain.com；branch＝z9hG4bK776sgdkse

Max-Forwards：70

From：<tel：15962621333>；tag＝49583

To:＜tel:13987654321〉//the To field is changed to user 2 tel URI

Call-ID：asd88asd77a@1.2.3.4

CSeq：1MESSAGE

Content-Type:Message/CPIM // content type is Message/CPIM

// following be the extended field relevant with SM

From:＜tel:15962621333〉// message sender tel URI

To:＜tel:13987654321〉// message receiver tel URI

DateTime:2006-12-13T13:40:01 // transmitting time

NS:SMSFeatures＜urn:ietf:params:smsFeatures〉// expansion the SM characteristics field

SMSFeatures.MessageTypeIndicatior:SMS-SUBMIT // type of message

SMSFeatures.ServiceCenterAddress:13500135000 // short message service center's number

Content-type:text/xml; Charset=utf-8 // content type, coded format

Content-ID:＜1234567890@foo.com〉// content identification

＜body〉// content

Go?shopping?this?weekend！

</body>

As seen from the above-described embodiment, the SIP client that present embodiment provides sends in the method for message to the SM client, on the one hand, by the CPM service enabler recipient's type of MESSAGE is judged, and the route of definite MESSAGE, make the SIP client only need in MESSAGE, directly to carry recipient's user ID, need not to indicate recipient's type by any field, so, improved the practicality of message intercommunication; On the other hand, by the mode of protocol conversion MESSAGE is resolved, is converted to SM by interworking function entity, make the SIP client need not to support any SM related protocol, only need directly in MESSAGE message body, to carry and treat that a message gets final product, and has reduced the requirement of message intercommunication to client.

In addition, in message body, expand the field that embodies the SM characteristic by the message body form of using the good Message/CPIM of extensibility during protocol conversion, effectively avoided a large amount of expansions SIP MESSAGE message header field; And the CPM business will realize originally and the intercommunication of various instant message IM operation systems that therefore adopting the CPIM form was to make compatible best choice as message body.

Fig. 7 is the MT course schematic diagram that the SM client sends message in the embodiment of the invention to the SIP client.Referring to Fig. 7, UE shown in the figure is user 1 a terminal, and this process may further comprise the steps:

Step 701:SC sends the SM that user 2 submits to by MAP to SMS-IWMSC/GMSC.Can in this SM, directly carry user 1 Mobile Subscriber International ISDN Number and the message that user 2 will send to user 1.It is as shown in the table to follow the example that each parameter of RP-MT-DATA of the SM of 3GPP technical specification 23040 is provided with:

Whether RP-PRI:0//prompting descends short-message sending when short message service center has comprised the MWD parameter

The address of RP-OA:135#0013#5000* // short message service center

RP-DA:159#6262#1333* // recipient's Mobile Subscriber International ISDN Number

RP-UD:TPDU //SM transport layer protocol data cell

This is a SM for RP-MTI:0 // prompting

In the above-mentioned example, the example that each parameter is provided with among the TPDU is as follows:

This SM of TP-MTI:00 // indication is the SMS-DELIVER that sends to MS from SC

There is not more SM etc. to be sent among TP-MMS:1 // indication SC

TP-RP:0 // indication is not provided with the Reply Path of SMS-DELIVER in this SM

The address of TP-OA:135#0013#5000* // indication SMS service center

This is SM for TP-PID:00000000 // indication, does not have the intercommunication with other messenger service

The rank of TP-DCS:00010001 // this SM of indication is 1, uses the character set of acquiescence

The timestamp of TP-SCTS:00000000 // indication SC

The length of TP-UDL:30 // indication TP-UD data content

"

The implication of above-mentioned each parameter can be with reference to the description in the 3GPP technical specification 23040.

Step 702:SMS-IWMSC/GMSC sends SM by MAP to IWF.

In this step, SMS-IWMSC/GMSC determines which network entity transmitting SM to can be: send routing inquiry request to HLR/HSS, by HLR/HSS corresponding routing iinformation is sent to SMS-IWMSC/GMSC; Also can be: SMS-IWMSC/GMSC judges number section that this Mobile Subscriber International ISDN Number is affiliated according to the recipient's Mobile Subscriber International ISDN Number that is comprised among the SM, and determines this SM is sent to which network entity according to the described section.

Behind the SM that step 703:IWF receives,, the content of SM is resolved, convert SIP MESSAGE form to by the mode of protocol conversion.

In this step, IWF can resolve SM according to the SM agreement, extracts the information be used to produce MESSAGE, and is corresponding field or message body among the MESSAGE according to Session Initiation Protocol with the information translation of being extracted.With the SM in the above-mentioned steps 701 is example, and the MESSAGE after the conversion is as shown in the table:

The corresponding RP-DA of MESSAGE tel:15962621333SIP/2.0//Request-URI field

Via：SIP/2.0/TCP?IWF.domain.com；branch＝z9hG4bK776sgdkse

Max-Forwards：70

From：IWF<sip:IWF@IWF.domain.com>；tag＝49583

To:＜tel:15962621333〉//the To field is corresponding to RP-DA

Call-ID：asd88asd77a@1.2.3.4

CSeq：1?MESSAGE

There is extended field in Content-Type:Message/CPIM // message body

From:＜tel:13987654321〉//the From field is corresponding to sender address

To:＜tel:15962621333〉//the To field is corresponding to RP-DA

DateTime：2006-12-13T13:40:00

NS：SMSFeatures<urn:ietf:params:smsFeatures>

SMSFeatures.MoreMessageToSend：false

SMSFeatures.MessageTypeIndicatior：SMS-Delivery

SMSFeatures.ServiceCenterAddress:13500135000 // corresponding to TP-OA

Content-type：text/xml；charset＝utf-8

Content-ID：<1234567890@foo.com>

<body>

Go?shopping?this?weekend！

</body>

In the process of above-mentioned conversion, should specify Content-type the mime type that field is Message/CPIM of MESSAGE, with the SIP URI address of IWF value, the various parameter informations relevant with SM are embodied in the message body of SIP MESSAGE as From field.

To the Context resolution of RP-MT-DATA the time, parameter information among the RP-MT-TPDU should be converted to a field information of Session Initiation Protocol, for example the recipient user's of RP-DA parametric representation MSISDN value is converted to the form of tel URI, and with the value of its To field value as Session Initiation Protocol (To:＜tel:15962621333 〉) and Ruequest-URI.

Various parameter informations for the TPDU that comprises among the RP-MT-DATA, can in the message body of SIPMESSAGE, embody, the extension header field that meets IEFT standard rfc3862 regulation can directly be changed, for can't using NameSpace＜urn:ietf:params:smsFeatures with the parameter information that the extension header field of IEFT standard rfc3862 is represented〉come a field of extended description SM characteristic.The OA parameter value that for example TP-UD is comprised converts the address of message sender to as extension header field From:＜tel:13987654321〉in message body, embody, the RP-DA parameter information that RP-MT-DATA is comprised converts recipient's address to as extension header field To:＜tel:15962621333〉in message body, embody, the time that the TP-SCTS parameter information is converted to user's readable form embodies in message body as extension header field DateTime:2006-12-13T13:40:00-08:00, the value that the TP-MMS parameter is converted to Boolean type embodies in message body as extension header field SMSFeatures.MoreMessageToSend:false, and the sign that TP-MDI is converted to user's readable form embodies in message body as extension header field SMSFeatures.MessageTypeIndicatior:SMS-Delivery.

Further, for some the characteristic recipient UE that guarantees SM can correctly understand, can in Require extension header field, specify.The function of flash message in the short message for example, promptly only on recipient UE, show and do not store, the grade of the TP-DCS parameter specify message among this SM is 0 grade, be that Class is 0, first and second bits of TP-DCS are 0, increase following extension header field in the content of SIPMESSAGE message body that so can be after conversion and represent: user 1 receives and should only show behind the SIP MESSAGE that comprises following extended message head and be not stored on the UE automatically.

Require：SMSFeatures.DataCodingScheme

SMSFeatures.DataCodingScheme：Class＝0

In this step, can support the various characteristics of SM by a field of expansion Session Initiation Protocol.Can be that read-only notifies user 1 UE only to show the SIP MESSAGE of reception for example by the value of specifying content-disposition.

Further, if TP-SRI parameter Indication message transmit leg requires the return messages delivery report in the short message that user 2 sends, then can increase following extension header field in the content of the SIP MESSAGE message body after conversion and represent:

Require：SMSFeatures.StatusReportIndicator

SMSFeatures.StatusReportIndicator：true

Its value is a Boolean type constant, represents message sender requirement return messages delivery report during for true, do not need to represent the return messages status report during for false.

Further, IWF can judge whether this SM message is a connected SM according to the prompting of TP-UDH parameter in the message body after receiving SM message, if the value of this parameter is 00 then illustrates that this is a connected SM message, content in the message body and imperfect, IWF can synthesize a complete SM according to the connected SM message groups that the TP-OA address among the TPDU of other SM message that receive subsequently and/or reference parameter will receive.Wherein, reference parameter refer to be connected short message number of references, be connected the maximum number of short message and be connected the current short message sequence number of short message.If the length of its message content surpasses the maximum length (i.e. 1300 characters) of MESSAGE message body behind the synthetic complete SM of connected SM message groups, then IWF can connect by SIP INVITE agreement and user 1, by message session trunk protocol (MSRP) message content is sent to user 1 again; If the length of its message content is less than or equal to 1300 characters behind the synthetic complete SM of connected SM message groups, IWF can carry out protocol conversion with the SM after the combination so, converts thereof into SIPMESSAGE and sends to the CPM service enabler.

The SIP MESSAGE of step 704:IWF after the CPM service enabler sends conversion.

Step 705:CPM service enabler returns the success response of 202Accept to IWF.

Step 706:CPM service enabler is judged and can be communicated by letter with user 1 by the form of SIP MESSAGE according to the service ability of user 1 presentation information, preference setting or terminal equipment, and promptly user 1 is a sip user.

Step 707:CPM service enabler sends SIP MESSAGE to user 1 UE.

Step 708:UE returns the success response of 200ok to the CPM service enabler.

According to the expansion header field that comprises in this message body, by the MESSAGE method generation message delivery report of Session Initiation Protocol, and to the transmission of CPM service enabler, the instantiation of message delivery report is as follows behind the step 709:UE reception MESSAGE:

MESSAGE?sip：IWF@IWF.domain.com?SIP/2.0

Via：SIP/2.0/TCP?IWF.domain.com；branch＝z9hG4bK776sgdkse

Max-Forwards：70

From：<tel：15962621333>；tag＝49583

To：IWF<sip：IWF@IWF.domain.com>

Call-ID：asd88asd77a@1.2.3.4

CSeq：1MESSAGE

Content-Type：Message/CPIM

From：<tel：15962621333>

To：<tel：13987654321>

DateTime：2006-12-13T13:40:01

NS：SMSFeatures<urn:ietf:params:smsF?eatures>

SMSFeatures.MessageTypeIndicatior：SMS-DELIVER-REPORT

SMSFeatures.ServiceCenterAddress：13500135000

SMSFeatures.FailureCause：81

Content-type：text/xml；charset＝utf-8

Content-ID：<1234567890@foo.com>

<body>

(error message prompting or message send prompt for successful! )

</body>

User 1 UE produces the message delivery report according to the prompting that whether will return delivery report parameter S MSFeatures.StatusReportIndicator:true that comprises in the message body after receiving SIP MESSAGE message, uses a short message feature field of expanding to represent the message delivery report that produces in the message body of the SIP of its generation MESSAGE.Wherein to indicate this message be the message delivery report to SMSFeatures.MessageTypeIndicatior extension header field, the address of SMSFeatures.ServiceCenterAddress extension header field indication SMS service center is 13500135000, and the reason that SMSFeatures.FailureCause extension header field indication short message sends failure is numbered 81 (16 system numbers).

Step 7010:CPM service enabler sends delivery report MESSAGE message to IWF.

Step 7011:IWF returns the success response of 200ok to the CPM service enabler.

Step 7012:CPM service enabler returns the success response of 200ok to user 1 UE.

Step 7013:IWF resolves the SIP MESSAGE that receives according to above-mentioned conversion method, is converted to turning in a report of short message.

Step 7014:IWF is to turning in a report that SMS-IWMSC/GMSC sends SMS message.

Step 7015:SMS-IWMSC/GMSC is sent to turning in a report that SC sends SMS message.

So far, finish present embodiment SM client sends MT course from message to the SIP client.

As seen from the above-described embodiment, the SM client that the embodiment of the invention provides sends in the method for message to the SIP client, on the one hand, by the SM server recipient's type of SM is judged, and the route of definite SM, make the SM client when sending SM, need not to indicate recipient's type, improved the practicality of message intercommunication; On the other hand, by the mode of protocol conversion SM is resolved, is converted to MESSAGE, make client need not to support the protocol stack of the other side's client, reduced the requirement of message intercommunication client by interworking function entity.

One of ordinary skill in the art will appreciate that all or part of step that realizes in the foregoing description method is to instruct relevant hardware to finish by program.

Corresponding to the method that MESSAGE message is sent to the SM client, this program comprises the steps: when carrying out

Receive MESSAGE message;

With described MESSAGE message parse, be converted to SM, by the SM server described SM is sent to the SM client.

Corresponding to the method that SM is sent to the SIP client, this program comprises the steps: when carrying out

Receive SM;

Described SM is resolved, is converted to MESSAGE message, described MESSAGE message is sent to the SIP client by the sip message server.

Described program can be stored in the computer read/write memory medium, and described storage medium can be read-only memory (ROM), random access memory (RAM), magnetic disc, CD etc.

The above is preferred embodiment of the present invention only, is not to be used to limit protection scope of the present invention.All any modifications of being done within the spirit and principles in the present invention, be equal to replacement, improvement etc., all should be included within protection scope of the present invention.

Claims

1, a kind of MESSAGE message is sent to the method for short message SM client, it is characterized in that, comprising:

Interworking function entity receives MESSAGE message;

2, method according to claim 1 is characterized in that, described MESSAGE message is specially:

Content type Content-Type field is changed to message/general and presents instant message Message/CPIM, and carries the SM extended field in message body.

3, method according to claim 1 and 2 is characterized in that, also comprises before described interworking function entity receives described MESSAGE message:

Session initiation protocol sip message server receives SIP client MESSAGE message that send, that comprise recipient's user ID;

The sip message server judges that according to described recipient's user ID the recipient of MESSAGE message for being fit to receive the user of SM, then sends to interworking function entity with described MESSAGE message.

4, method according to claim 3 is characterized in that, described sip message server judges that the recipient of MESSAGE message is specially for the user who is fit to reception SM:

The sip message server obtains the service ability of described recipient's presentation information, preference setting or receiving side terminal equipment according to recipient's user ID;

If the service ability of described recipient's presentation information, preference setting or receiving side terminal equipment shows that described recipient preferentially uses SM to carry out message communicating, then described recipient is for being fit to receive the user of SM.

5, method according to claim 3 is characterized in that, described sip message server judges that the recipient of MESSAGE message is specially for the user who is fit to reception SM:

The sip message server obtains described recipient's network registry information according to recipient's user ID;

If described network registry information shows the recipient and is not supporting the second generation mobile communications network registration of Session Initiation Protocol that then described recipient is for being fit to receive the user of SM.

6, method according to claim 3 is characterized in that, described recipient's user ID is carried in recipient member's tabulation of described MESSAGE message;

Described sip message server judges that the recipient of MESSAGE message is specially for the user who is fit to reception SM:

The sip message server obtains the service ability of each recipient member's presentation information, preference setting or recipient's member terminal equipment according to described recipient member's tabulation; If the service ability of recipient member's presentation information, preference setting or recipient's member terminal equipment shows that described recipient member preferentially uses SM to carry out message communicating, then described recipient member is for being fit to receive the user of SM;

Describedly MESSAGE message is sent to interworking function entity be specially: the sip message server will send to interworking function entity corresponding to the recipient member's who is fit to receive SM MESSAGE message.

7, method according to claim 3 is characterized in that,, further comprises for after being fit to receive the user of SM the recipient who judges MESSAGE message:

When the sip message server judges that the length of the message body content of described MESSAGE message exceeds the maximum length of SM, described message body content is split as the sub-message body content of length smaller or equal to described SM maximum length, and is the sub-MESSAGE message of a correspondence of message body content structure with described each sub-message body content;

Describedly transmit described MESSAGE message to interworking function entity and be specially: the sip message server is transmitted the sub-MESSAGE message of described structure to interworking function entity.

8, method according to claim 7 is characterized in that, described is that the sub-MESSAGE message of a correspondence of message body content structure is specially with each sub-message body content:

The Content-Type field of MESSAGE message is changed to Message/CPIM, in the message body of MESSAGE message, carry the sub-message body content of a correspondence, form a plurality of sub-MESSAGE message, and in the message body of sub-MESSAGE message, carry the related information between the sub-MESSAGE message.

9, method according to claim 1 and 2 is characterized in that, interworking function entity with described MESSAGE message parse, be converted to SM before, also comprise:

When interworking function entity judges that the length of the message body content of described MESSAGE message exceeds the maximum length of SM, described message body content is split as the sub-message body content of length smaller or equal to described SM maximum length, with described each sub-message body content is the sub-SM that message content is constructed a correspondence, and carries the related information between the sub-SM in each sub-SM of described structure.

10, method according to claim 1 and 2 is characterized in that, described interworking function entity with described MESSAGE message parse, be converted to SM and be specially:

Interworking function entity is resolved message header field and the message body of MESSAGE according to Session Initiation Protocol, extracts the information that is used to produce SM, and is the value of corresponding field among the SM according to the SM agreement with the information translation of being extracted.

11, method according to claim 10 is characterized in that, described SM agreement is: Short Message Peer to Peer SMPP or MAP MAP.

12, method according to claim 10 is characterized in that, comprises displacement field among the MESSAGE that described interworking function entity receives, and has been converted to SM with identification information is corresponding in the described displacement field MESSAGE and has sent to the SM server;

The information of described extraction comprises: identification information in the described displacement field and message body;

Described conversion is specially: when described message body is sky, and the SM that sends SM that the structure deletion is corresponding with described identification information; When described message body non-NULL, the SM that sends SM that the structure deletion is corresponding with described identification information and be the SM of message content with described message body; Or, the SM that sends SM that the transposition of structures is corresponding with described identification information.

13, a kind of short message SM is sent to the method for SIP client, it is characterized in that, comprising:

Interworking function entity receives SM;

14, method according to claim 13 is characterized in that, also comprises before described interworking function entity receives described SM:

The SM server receives SM client SM that send, that comprise recipient's user ID;

According to claim 13 or 14 described methods, it is characterized in that 15, described interworking function entity is resolved, is converted to MESSAGE message with described SM and is specially:

Interworking function entity is according to the value of each field among the SM protocol analysis SM, extraction is used to produce the information of MESSAGE message, is the value of corresponding field in the MESSAGE message according to Session Initiation Protocol with the information translation of being extracted, and the Content-Type field of MESSAGE message is changed to Message/CPIM.

16, method according to claim 15 is characterized in that, described conversion further comprises:

A field of extended description SM characteristic in the CPIM of MESSAGE message content, with among the described SM, the part or all of SM field description that does not have corresponding relation between SM agreement and the Session Initiation Protocol in the expansion CPIM field in.

17, according to claim 13 or 14 described methods, it is characterized in that, comprise related information among the SM that described interworking function entity receives;

After described interworking function entity is resolved the SM that receives, further comprise:

Interworking function entity is according to related information among the SM and/or message sender address, and the message content that will comprise among the SM of related information is combined into complete content;

Describedly SM is converted to MESSAGE message is specially: with the message body content of described complete content as described MESSAGE message.

18, method according to claim 17 is characterized in that, if the length of described complete content is greater than the maximum length of MESSAGE message body, then describedly MESSAGE message is sent to the sip message server is specially:

Interworking function entity connects by INVITE and SIP client, and by message session trunk protocol MSRP described MESSAGE message is sent to the SIP client.

19, according to claim 13 or 14 described methods, it is characterized in that, before the SIP client sends MESSAGE message, further comprise at described sip message server:

The sip message server obtains the service ability of described recipient's presentation information, preference setting or receiving side terminal equipment according to recipient's user ID in the MESSAGE message, and judges that according to the service ability of the recipient's who is obtained presentation information, preference setting or receiving side terminal equipment described recipient is for being fit to receive the user of SIP MESSAGE message.

20, a kind of system that realizes SIP client and the intercommunication of SM client message is characterized in that, comprising:

21, a kind of sip message server is characterized in that, comprising:

22, sip message server according to claim 21 is characterized in that:

Further comprise in the user type judge module: the user capability acquiring unit is used for obtaining according to recipient's user ID of MESSAGE message the service ability of recipient's presentation information, preference setting or receiving side terminal equipment;

Described user type judge module, the service ability that is used for presentation information, preference setting or receiving side terminal equipment according to described recipient is judged recipient's type of described MESSAGE.

23, according to claim 21 or 22 described sip message servers, it is characterized in that, further comprise:

MESSAGE length judge module, when the user type judge module is judged the recipient for after being fit to receive the user of SM, described MESSAGE length judge module is used to judge whether the message body content length of MESSAGE message exceeds the SM maximum length, when exceeding the SM maximum length, notice MESSAGE splits module, when not exceeding the SM maximum length, notify described communication module;

MESSAGE splits module, be used for notice according to described MESSAGE length judge module, the message body content that length is exceeded the MESSAGE message of SM maximum length is split as the sub-message body content of length smaller or equal to described SM maximum length, and, send the sub-MESSAGE message of described structure by communication module with the sub-MESSAGE message that described each sub-message body content is a correspondence of message body content structure;

Described communication module is used for sending described MESSAGE message according to the notice of described MESSAGE length judge module.

24, a kind of interworking function entity is characterized in that, comprising:

25, interworking function entity according to claim 24 is characterized in that, described MESSAGE processing module comprises:

The MESSAGE receiving element is used to receive MESSAGE message;

The MESSAGE resolution unit is used for resolving according to Session Initiation Protocol the message header field and the message body of the MESSAGE message received, extracts the information that is used to produce SM;

The MESSAGE converting unit, the information translation that is used for according to the SM agreement being used to of being extracted being produced SM is the value of SM corresponding field;

The SM transmitting element is used to send the SM that the MESSAGE converting unit is changed.

26, interworking function entity according to claim 25 is characterized in that, further comprises in the described MESSAGE processing module:

MESSAGE length judging unit, be used to receive the message body content that described MESSAGE resolution unit parses, whether the length of judging described message body content exceeds the SM maximum length, when exceeding the SM maximum length, notice MESSAGE split cells, when not exceeding the SM maximum length, notify described MESSAGE converting unit;

The MESSAGE split cells, be used for notice according to described MESSAGE length judging unit, the message body content that length is exceeded the SM maximum length is split as the sub-message body content of length smaller or equal to described SM maximum length, and described sub-message body content is sent to described MESSAGE converting unit;

Described MESSAGE converting unit is used for the notice according to described MESSAGE length judging unit, and the information translation that being used for of being extracted is produced SM according to the SM agreement is the value of SM corresponding field.

27, interworking function entity according to claim 24 is characterized in that, described SM processing module further comprises:

The SM receiving element is used to receive SM;

The SM resolution unit is used for the value of each field of SM of being received according to the SM protocol analysis, extracts the information that is used to produce MESSAGE message;

The SM converting unit, the information translation that is used for according to Session Initiation Protocol being used to of being extracted being produced MESSAGE message is the value of MESSAGE message corresponding field;

The MESSAGE transmitting element is used to send the MESSAGE message that described SM converting unit is changed.

28, interworking function entity according to claim 27 is characterized in that, described SM processing module further comprises:

The SM assembled unit is used for resolving the information that obtains according to described SM resolution unit, the content of the identical SM of transport layer protocol-originating address TP-OA is made up, and the result of described combination is sent to described SM converting unit.