WO2007053999A1

WO2007053999A1 - A method and system for realizing short message function of sip terminal

Info

Publication number: WO2007053999A1
Application number: PCT/CN2006/002306
Authority: WO
Inventors: Yong Yang; Yilin Cao; Mingshi Huang; Xiaodong Gong; Weifeng Huang; Tianyun Guan
Original assignee: Zte Corporation
Priority date: 2005-11-11
Filing date: 2006-09-07
Publication date: 2007-05-18
Also published as: CN1964513A

Abstract

A method for realizing short message function of SIP terminal includes the steps step 1 a SIP terminal transmits a short message data to a soft switch step 2 the soft switch transmits the short message data to a SIP-based application server step 3 the application server transmits the short message data to a short message proxy entity step 4 the short message proxy entity transmits the short message data to a short message center or a short message gateway. Present invention realizes the short message function of SIP terminal enhances the telecommunication service ability of the SIP terminal and utilizes sufficiently the available NGN network resource thus the system construction is simple and reliable, and the operation flow is clear and normative.

Description

Method and system for realizing SIP terminal short message function

The present invention relates to the field of softswitch value-added services, and in particular, to a method and system for implementing a Session Initiation Protocol (SIP) terminal short message function on a Next Generation Network (NGN). Background technique

Softswitch is a technical system that provides carrier-class services to users by separating services from call control and call control and bearers. It has become a SIP-based multi-user with Internet (Internet) architecture. Multimedia open business system. At present, the softswitch business development capability has evolved from a simple telephony service and an intelligent network service expansion to an application-driven softswitch system with multimedia service capabilities that can be customized according to requirements.

The implementation of softswitch value-added services usually relies on the application server to complete. The application server is responsible for the logic generation and management of various value-added services, and also provides various open application programming interfaces (APIs) to provide a platform for the development of third-party services. The application server is an independent entity, which has nothing to do with the softswitch of the control layer, thus realizing the separation of service and call control, which is conducive to the introduction of new services. Currently, the application server provides a powerful business capability that not only supports traditional telephony services, but also provides value-added services such as SMS, MMS, and positioning. Thus, the application server has become one of the core devices in the NGN network.

However, for the SIP terminals (including the soft terminal and the hard terminal) registered on the softswitch device, the basic telecommunication service capability is mainly concentrated on the telecommunication service of the call class. Currently, the related SIP terminal short message function has not been retrieved. system. Invention disclosure

The object of the present invention is to provide a method and system for implementing a SIP terminal short message function on a SIP-based application server, and realizing the short message function of the SIP terminal by using the existing NGN network device. SIP terminals registered on the softswitch can not only send text messages but also receive text messages through softswitches, application servers and extended SMS entities.

In order to achieve the above object, the present invention provides a method for implementing a short message function of a SIP terminal, the package Including the following steps:

Step 1, the SIP terminal sends the short message data to the softswitch;

Step 2, the softswitch sends the short message data to the SIP-based application server; Step 3, the application server sends the short message data to the short message proxy entity; Step 4, the short message proxy entity will The short message data is sent to the SMS center or the SMS gateway.

The method for implementing the short message function of the SIP terminal is characterized in that the short message data transmitted between the SIP terminal and the softswitch and the softswitch and the application server are

The SIP-Message source language is encapsulated.

The method for implementing the SIP terminal short message function is characterized in that the application server adapts the short message data into internal interface data and sends the short message data to the short message proxy entity.

The method for implementing the SIP terminal short message function is characterized in that the short message proxy entity adapts the internal short message data into standard short message protocol data and sends the data to the short message center or the short message gateway.

The method for implementing the short message function of the SIP terminal is characterized in that after the short message data is received by the short message center or the short message gateway, the method further includes the step of replying the result response to the SIP terminal. Specifically include:

Step 51: The short message center or the short message gateway replies to the short message request response of the standard short message protocol to the short message proxy entity;

Step 52: The short message proxy entity adapts the response to internal interface data and sends the data to the application server.

Step 53: The application server adapts the internal interface data to a SIP-Message message and sends the message to the softswitch.

Step 54: The softswitch sends the SIP message to the SIP terminal.

The method for implementing the short message function of the SIP terminal is characterized in that, when the length of the short message submitted by the SIP terminal exceeds the number of characters specified by the short message protocol, the following steps are also included:

Step 61: After the application server finds that the content of the short message in the short message data exceeds the length specified by the short message protocol, the application server splits the short message data into multiple internal messages, and passes the internal An interface, the packet is sent to the short message proxy entity;

Step 62: The short message proxy entity receives the short message data received from the application server. Forming the standard short message protocol data, and sending the packet to the short message center or the short message gateway; Step 63, the short message center or the short message gateway starts to send a response of the short message data submitted by the standard short message protocol to the short message proxy entity ;

Step 64: The short message proxy entity receives the response submitted by the short message of the short message center or the short message gateway one by one, and adapts the group response to internal interface data, and the packet is sent to the application server.

Step 65: The server receives all the short message submission responses, determines whether all the responses are successful, and if yes, sends a successfully responding SIP message to the softswitch, and if not, or receives a timeout, sends a SIP message with a failed response. Give the softswitch.

Step 66: The softswitch transmits the successful or failed SIP message to the SIP terminal. The foregoing method for implementing the short message function of the SIP terminal is characterized in that the method further includes: the step of receiving the short message data by the SIP terminal, which specifically includes:

Step 71: The short message center or the short message gateway sends the standard short message protocol short message data to the short message proxy entity.

Step 72: The short message proxy entity adapts the standard short message protocol short message data to internal interface data and sends the data to the application server.

Step 73: The application server sends the internal interface data as a SIP-Message message to the softswitch.

Step 74: The softswitch transmits the SIP message to a SIP terminal.

Step 75: The SIP terminal receives and processes successfully, and sends a SIP message that successfully responds to the softswitch. Otherwise, sends an error response SIP message to the softswitch.

Step 76: The softswitch sends the responding SIP message to the application server. Step 77: The application server adapts the responding SIP message to internal interface data, and sends the SIP message to the short message proxy entity.

Step 78: The short message proxy entity adapts the internal corresponding data to a standard short message protocol data reply to the short message center or the short message gateway.

The method for implementing the short message function of the SIP terminal is characterized in that the application server interfaces with the short message center or the short message gateway of different types of short message protocols through the short message proxy entity.

The method for implementing the short message function of the SIP terminal is characterized in that the SIP terminal comprises a SIP soft terminal and a SIP hard terminal. The method for implementing the SMS function of the SIP terminal is characterized in that the SMS center or the SMS gateway sends the short message data to a short message proxy entity other than the short message proxy entity.

In order to achieve the above object, the present invention further provides a system for implementing a short message function of a SIP terminal, which is characterized in that it comprises: a SIP terminal, a softswitch, an application server, a short message proxy entity, and a short message center or a short message gateway, wherein

The SIP terminal is configured to send short message data to the softswitch and receive short message data from the softswitch;

The softswitch is configured to send short message data to the SIP terminal and the application server, and receive short message data from the SIP terminal and the application server;

The application server is configured to send short message data to the softswitch and the short message proxy entity, and receive short message data from the softswitch and the short message proxy entity;

The short message proxy entity is configured to send short message data to the application server and the short message center or the short message gateway, and receive short message data from the application server and the short message center or the short message gateway;

The short message center or the short message gateway is configured to send short message data to the short message proxy entity and receive short message data from the short message proxy entity;

The above system is characterized in that the short message data transmitted between the SIP terminal and the softswitch and the softswitch and the application server are encapsulated in a SIP-Message source language.

The above system is characterized in that the application server adapts the short message data into internal interface data and sends the short message data to the short message data, and the application server adapts the short message data to SIP protocol data to send The soft exchange.

The above system is characterized in that the short message proxy entity adapts the short message data into standard short message protocol data and sends the short message data to the short message center or the short message gateway, and the short message proxy entity adapts the short message data The internal interface data is sent to the application server.

The above system is characterized in that, after the application server finds that the content of the short message in the short message data exceeds the length specified by the short message protocol, the application server splits the short message data into multiple internal messages and passes the The internal interface, the packet is sent to the short message proxy entity.

The above system is characterized in that the SIP terminal comprises a SIP soft terminal and a SIP hard terminal. The above system is characterized in that the application server interfaces with a short message center or a short message gateway of various different types of short message protocols through the short message proxy entity. The above system is characterized in that the SMS center or the SMS gateway is further connected to a short message proxy entity other than the short message proxy entity.

The invention realizes the short message function of the SIP terminal and enhances the telecommunication service capability of the SIP terminal on the basis of the core device softswitch of the next generation network NGN and the SIP-based application server and the short message proxy. The invention fully utilizes the existing NGN network resources, and the system composition is simple and reliable, and the business process is clear and standardized. In the meantime, the present invention can be flexibly set up to meet the needs of different operators, considering the strong SMS protocol adaptation capability of the application server in the present invention. BRIEF DESCRIPTION OF THE DRAWINGS

Figure 1 is a system structure of the present invention;

2 is an uplink flow of a general non-super long message according to the present invention;

3 is an uplink process of the ultra long message of the present invention;

4 is a flow chart of the downlink message of the present invention.

Among them, the reference mark:

101—SIP soft terminal/hard terminal

102—softswitch

103—Application Server

104—SMS agent

105—SMS Center/SMS Gateway

106—Other SMS Agents

107—Interface 1

Lanyi interface two

109—Interface 3

110 - Interface 4 The best way to implement the present invention

Figure 1 shows the structure of the system. As shown in Figure 1, each interface is described as follows:

Interface one 107: an interface between the SIP soft terminal/hard terminal 101 and the soft switch 102. The standard SIP protocol is used in between. The registration, voice call, and message forwarding of the SIP terminal are implemented through the interface; Interface two 108: An interface between the softswitch 102 and the application server 103. The softswitch 102 only communicates with the SIP adapter of the application server 103, so that they adopt the standard SIP protocol between them; interface three 109: the interface between the application server 103 and the short message proxy 104, using the internal interface of the present invention, the internal interface There is currently no specific standard format, and each manufacturer defines itself according to the specific device model;

Interface 4: The short message proxy 104, other short message proxy 106 and the SMS center / SMS gateway 105 interface, using a standard SMS protocol.

Figure 2 shows the upstream process of ordinary non-long text messages. As shown in the figure, the following steps are included: Step S201: The SIP terminal 101 encapsulates the short message request in the SIP-Message source language and sends it to the soft switch 102.

Step S202, the softswitch 102 sends the SIP message to the application server 103;

Step S203, the application server 103 adapts the SIP message to the internal interface data, and sends it to the short message proxy entity 104;

Step S204, the short message proxy entity 104 adapts the internal short message request data into standard short message protocol data and sends it to the short message center or the short message gateway 105;

Step S205, the short message center 105 responds to the standard short message request response to the short message proxy entity 104; step S206, the short message proxy entity 104 adapts the response to the internal interface and sends it to the application server 103;

Step S207, the application server 103 adapts the internal interface data to the SIP-Message message and sends it to the soft switch 102. If the sending succeeds, the 202 is received to the soft switch 102, otherwise the other error-responding SIP message is returned to the soft switch 102.

Step S208, the softswitch transparently transmits the SIP message to the SIP terminal.

Figure 3 shows the upstream process of a very long message. As shown in FIG. 3, the process includes the following steps: Step S301, the SIP terminal 101 encapsulates the short message request in the SIP-Message source language, and sends the short message request to the soft switch 102;

Step S302, the softswitch 102 sends the SIP message to the application server 103 to start a short message "transaction";

Step S303, the application server 103 finds that the content of the short message in the short message request exceeds the length specified by the short message protocol, and then the application server 103 splits and adapts the short message data into multiple internal interface short message data, and starts to use the internal interface to send the short message one by one. The proxy entity 104 sends Step S304, the short message proxy entity 104 receives all the internal interface data, and is adapted to the message data of the standard short message protocol, and then submitted to the short message center or the short message gateway 105 one by one;

Step S305, the short message center or the short message gateway 105 starts to send the response submitted by the short message to the short message proxy entity 104 one by one;

Step S306, the short message proxy entity 104 receives the response of the short message submission by the short message center or the short message gateway 105 one by one, and adapts the short message submission response to the internal interface, and starts to send to the application server 103; Step S307, the application server 104 receives all the short message submissions. The response, based on the session number, is determined until all responses in the "transaction" are received. If the timeout is received, the failure response is sent back to the softswitch 102. If all the responses are successful responses, the application server will 202 accept to the softswitch 102, otherwise reply to the other error response SIP message to the softswitch 102;

Step S308, the softswitch 102 transparently transmits the SIP message to the SIP terminal 101;

Figure 4 shows the downstream SMS process. As shown, the process includes the following steps:

Step S401, the short message center or the short message gateway 105 sends a short message request to the short message proxy entity 104; step S402, the short message proxy entity 104 adapts the response to the internal interface and sends it to the application server 103;

Step S403, the application server 103 adapts the internal interface data to a SIP-Message message and sends it to the softswitch 102.

Step S404, the softswitch 102 transparently transmits the SIP message to the SIP terminal 101;

Step S405, the SIP terminal 101 receives and processes successfully, then returns 202 to the softswitch 102, and otherwise replies to the SIP message of other error response to the softswitch 102;

Step S406, the softswitch 102 sends the SIP message to the application server 103;

Step S407, the application server 103 adapts the SIP message to an internal interface, and sends it to the short message proxy entity 104;

Step S408, the short message proxy entity 104 adapts the internal response to the standard short message protocol data and replies to the short message center or the short message gateway 105;

In summary, the present invention has the following advantages: The present invention fully utilizes the existing NGN network resources, and implements the SIP terminal 101 based on the softswitch 102 and the SIP-based application server 103 in combination with the short message proxy in the present invention. The short message function enhances the telecommunications service capability of the SIP terminal. The system is simple and reliable, and the business process is clear and standardized.

In the present invention, the length of the short message submitted by the SIP terminal 101 can far exceed the length of the short message protocol. The number of characters. The long message will be split by the application server 103, and then sent as a multiple session in a "transaction" to the short message agent to ensure that the long message is sent correctly and completely. When receiving the short message submission response, it is judged according to the session number, and after receiving all the responses in the "transaction", the SIP message is returned to the softswitch 102, which fully ensures that the long message is correctly submitted to the short message center or the short message gateway. 105. Industrial applicability

The networking of the invention is simple and convenient, and the system has good practicability and flexible adaptability. In the present invention, the application server has a strong SMS protocol adaptation capability, and can cooperate with a short message center or a short message gateway of different protocols to adapt to different networking requirements by cooperating with a short message proxy supporting different protocols.

Claims

Claim

A method for implementing a short message function of a SIP terminal, comprising the following steps: Step 1, the SIP terminal sends the short message data to the softswitch;

The method for implementing the short message function of the SIP terminal according to claim 1, wherein the short message data transmitted between the SIP terminal and the softswitch and the softswitch and the application server is SIP - Message source is encapsulated.

The method for implementing the SIP terminal short message function according to claim 1, wherein the application server adapts the short message data into internal interface data and sends the short message data to the short message proxy entity.

The method for implementing the short message function of the SIP terminal according to claim 1, wherein the short message proxy entity adapts the internal short message data into standard short message protocol data and sends the data to the short message center or the short message gateway.

The method for implementing the SIP terminal short message function according to claim 1, 2, 3, and 4, wherein after the short message data is received and submitted by the short message center or the short message gateway, the method further includes The step of responding to the reply to the SIP terminal includes:

Step 54: The softswitch sends the SIP message to the SIP terminal.

The method for implementing the short message function of the SIP terminal according to claim 1, 2, 3, and 4, wherein when the length of the short message submitted by the SIP terminal exceeds the number of characters specified by the short message protocol, Includes the following steps: Step 61: After the application server finds that the content of the short message in the short message data exceeds the length specified by the short message protocol, the application server splits the short message data into multiple internal messages, and passes the internal An interface, the packet is sent to the short message proxy entity;

Step 62: The short message proxy entity adapts the short message data received from the application server to standard short message protocol data, and sends the packet to the short message center or the short message gateway.

Step 63: The short message center or the short message gateway starts to send a response of the short message data submitted by the standard short message protocol to the short message proxy entity;

Step 66: The softswitch transmits the successful or failed SIP message to the SIP terminal.

The method for implementing the SIP terminal short message function according to claim 1, 2, 3, and 4, wherein the method further includes: the step of receiving the short message data by the SIP terminal, specifically:

Step 73: The application server sends the internal interface data to the softswitch as a SIP-Message message.

Step 74: The softswitch transmits the SIP message to a SIP terminal.

The method for implementing the short message function of the SIP terminal according to claim 1, wherein the application server interfaces with the short message center or the short message gateway of different types of short message protocols by using the short message proxy entity.

The method for implementing the short message function of the SIP terminal according to claim 1, wherein the SIP terminal comprises a SIP soft terminal and a SIP hard terminal.

The method for implementing the SIP terminal short message function according to claim 1, further comprising the short message center or the short message gateway sending the short message data to a short message proxy entity other than the short message proxy entity.

A system for implementing a short message function of a SIP terminal, comprising: a SIP terminal, a softswitch, an application server, a short message proxy entity, and a short message center or a short message gateway, wherein

The system according to claim 11, wherein the short message data transmitted between the SIP terminal and the softswitch and the softswitch and the application server are encapsulated in a SIP-Message source language. .

The system according to claim 11, wherein the application server adapts the short message data into internal interface data and sends the short message data to the short message data. The SIP protocol data is sent to the softswitch.

The system according to claim 11, wherein the short message proxy entity adapts the short message data to standard short message protocol data and sends the short message protocol data to the short message center or the short message gateway, and the short message proxy entity Adapting the short message data into internal interface data and transmitting the data to the application service Server.

The system according to claim 11, wherein, after the application server finds that the content of the short message in the short message data exceeds the length specified by the short message protocol, the application server splits the short message data into a plurality of internal messages, and the packets are sent to the short message proxy entity through the internal interface.

The system according to claim 11, wherein the SIP terminal comprises a SIP soft terminal and a SIP hard terminal.

The system according to claim 11, wherein the application server interfaces with a short message center or a short message gateway of various different types of short message protocols through the short message proxy entity.

The system according to claim 11, further comprising the short message center or the short message gateway being connected to a short message proxy entity other than the short message proxy entity.