CN114584936A - Method, system and storage medium for realizing short message intercommunication between private network terminal and public network terminal - Google Patents

Abstract

The disclosure proposes a method, system, and storage medium for implementing short message interworking between a private network terminal and a public network terminal. The method comprises the following steps: after the private network terminal registers to the private network HSS, the private network S-CSCF receives a registration request from the private network terminal and forwards the registration request to the public network SMSC for the private network terminal to register to the public network SMSC; after receiving the registration request, the public network SMSC inquires registration information of the private network terminal from a public network HSS; and after the public network HSS does not inquire the registration information of the private network terminal, the public network SMSC acquires the registration information of the private network terminal from the private network HSS so as to complete the registration of the private network terminal to the public network SMSC.

Description

Method, system and storage medium for realizing short message intercommunication between private network terminal and public network terminal

Technical Field

The present disclosure relates generally to data communication in private and public networks, and more particularly, to a method, system, and storage medium for implementing short message interworking between private and public network terminals.

Background

At present, a private communication network (hereinafter, referred to as a private network) is established for each enterprise for communication in a specific area (for example, a coal mine, a railway, and the like) which cannot be covered by a public communication network (hereinafter, referred to as a public network) provided by a network operator (for example, china telecommunications and the like). However, these private networks can only transmit and receive short messages within the network, and cannot achieve the interworking of short messages with the public network. For example, when a terminal enters a private network from a public network, the terminal in the private network (hereinafter referred to as a private network terminal) completes registration in the private network. However, since the registered data of the private network terminal in the private network is not intercommunicated with the public network, the private network terminal can only transmit and receive short messages with other private network terminals in the private network, but cannot transmit and receive short messages with a terminal in the public network (hereinafter referred to as a public network terminal), that is, the private network terminal cannot receive short messages (especially some verification codes, notification of emergency events, etc.) from the public network terminal or transmit short messages to the public network terminal, which brings great inconvenience to users. Therefore, the barrier between the private network and the public network needs to be broken to implement the short message interworking between the private network terminal and the public network terminal.

Disclosure of Invention

The disclosure provides a method, a system, and a storage medium for implementing short message interworking between a private network terminal and a public network terminal.

According to an aspect of the present disclosure, a method for implementing short message interworking between a private network terminal and a public network terminal is provided, including: after the private network terminal registers to the private network HSS, the private network S-CSCF receives a registration request from the private network terminal and forwards the registration request to the public network SMSC for the private network terminal to register to the public network SMSC; after receiving the registration request, the public network SMSC inquires registration information of the private network terminal from a public network HSS; and after the public network HSS does not inquire the registration information of the private network terminal, the public network SMSC acquires the registration information of the private network terminal from the private network HSS so as to complete the registration of the private network terminal to the public network SMSC.

In some embodiments, the public network SMSC is configured with information of a plurality of private network HSSs, each of the plurality of private network HSSs corresponding to a number segment of a corresponding private network, and the public network SMSC acquiring the registration information of the private network terminal from the private network HSS includes: determining a private network HSS corresponding to a number segment to which the number of the private network terminal belongs from the plurality of private network HSSs as a private network HSS to which the private network terminal is registered; and acquiring the registration information of the private network terminal from the determined private network HSS.

In some embodiments, the public network SMSC obtains registration information for the private network terminal by sending a User Data Request (UDR) to the determined private network HSS.

In some embodiments, the above method further comprises: the private network S-CSCF forwards the registration request to the private network SMSC for the private network terminal to register with the private network SMSC.

In some embodiments, the above method further comprises: the private network S-CSCF receives a short message from the private network terminal to be sent to the called terminal and forwards the short message to the private network SMSC; under the condition that the private network SMSC determines that the called terminal is not registered in the private network SMSC, the private network S-CSCF forwards the short message to the public network SMSC; and the public network SMSC sends the short message to the called terminal under the condition that the called terminal is determined to be the public network terminal registered in the public network SMSC.

In some embodiments, the above method further comprises: the public network SMSC receives a short message from a public network terminal to be transmitted to a called terminal; the public network SMSC forwards the short message to a private network S-CSCF based on the registration information of the called terminal on the public network SMSC under the condition that the called terminal is determined to be a private network terminal registered in the public network SMSC; and the private network S-CSCF sends the short message to the called terminal.

In some embodiments, the registration information of the called terminal on the public network SMSC includes information of the private network S-CSCF which sends the short message to the called terminal.

In some embodiments, the private network terminal and the public network terminal are VoLTE terminals.

According to another aspect of the present disclosure, a system for implementing short message interworking between a private network terminal and a public network terminal is proposed, the system comprising a private network S-CSCF and a public network SMSC configured to perform the above method.

According to yet another aspect of the disclosure, a computer-readable storage medium is presented, which stores a program, which when executed by a processor, implements the above-described method.

The foregoing has outlined rather broadly the present disclosure in order to provide a basic understanding of some aspects of the disclosure. However, it should be understood that this summary is not an exhaustive overview of the disclosure. It is not intended to identify key or critical elements of the disclosure or to delineate the scope of the disclosure. Its sole purpose is to present some concepts of the disclosure in a simplified form as a prelude to the more detailed description that is presented later.

Other features of the present disclosure and advantages thereof will become more apparent from the following detailed description of various embodiments of the present disclosure with reference to the accompanying drawings.

Drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate various embodiments of the disclosure and together with the description, serve to explain the principles of the disclosure.

Fig. 1 shows a basic flow of a private network terminal registering with a public network SMSC according to an embodiment of the present disclosure.

Fig. 2 shows a basic flow of sending a short message from a private network terminal to a public network terminal according to an embodiment of the present disclosure.

Fig. 3 shows a basic flow of sending a short message from a public network terminal to a private network terminal according to an embodiment of the present disclosure.

Fig. 4 shows an example of a detailed procedure for registering a private network terminal with a public network SMSC according to an embodiment of the present disclosure.

Fig. 5 shows an example of a detailed procedure in which a private network terminal transmits a short message to a public network terminal according to an embodiment of the present disclosure.

Fig. 6 shows an example of a detailed procedure in which a public network terminal transmits a short message to a private network terminal according to an embodiment of the present disclosure.

Fig. 7 shows a structure of a system for implementing short message interworking between a private network terminal and a public network terminal according to an embodiment of the present disclosure.

Detailed Description

Hereinafter, various embodiments of the present disclosure will be described in detail with reference to the accompanying drawings.

It should be noted that in the following detailed description, numerous specific details are set forth in order to provide a thorough understanding of the described embodiments. It will be apparent, however, to one skilled in the art, that the described embodiments may be practiced without some or all of these specific details. Additionally, in the described embodiments, some well-known matters have not been described in detail in order to avoid unnecessarily obscuring the concepts of the present disclosure, and should be considered part of the specification where appropriate.

Further, the steps of the methods presented in this disclosure are illustrative. In some embodiments, the methods may have one or more additional steps not described herein and/or omit one or more steps already described herein. Moreover, the order in which the steps of the methods are illustrated and described is not intended to be limiting.

Generally, the present disclosure provides a solution to the problem that short message interworking cannot be achieved between a current private network terminal and a public network terminal. The scheme realizes the short message intercommunication between the private network terminal and the public network terminal. More specifically, the solution improves the existing registration process of the terminal in the network, the process of the terminal sending a message, and the like, and is a new solution.

Before explaining the solution proposed by the present disclosure in detail, it should be noted that the following description will refer to various network elements, i.e., an S-CSCF (Serving-Call Session Control Function), an HSS (Home Subscriber Server), an SMSC (Short Message Service Center), which are network elements in an IMS (IP Multimedia Subsystem). These network elements should be well known to those skilled in the art and will not be described in detail herein. As can be appreciated from the foregoing description and the following description, private network S-CSCF, private network HSS, private network SMSC, and public network S-CSCF, public network HSS, public network SMSC herein represent network elements S-CSCF, HSS, SMSC of the private network and the public network, respectively.

Furthermore, it should be appreciated by those skilled in the art that the terminals referred to herein may be, for example, VoLTE (Voice over Long-terminal Evolution) terminals, 5G terminals, and any other type of terminal that can be adapted to the solution of the present disclosure. Similarly, as can be appreciated from the foregoing description and the following description, private network terminals and public network terminals herein represent terminals in a private network and a public network, respectively, and in particular, a private network terminal may be a terminal that roams from a public network into a private network.

In addition, as already mentioned above in the background, the public network herein represents a public communication network provided by a network operator (e.g., chinese telecommunications, etc.), and the private network is a concept opposite to the public network, which represents a non-public (i.e., private) communication network, which is generally built by an enterprise (e.g., a coal mine, a railroad enterprise, etc.) itself.

As mentioned above, the solution of the present disclosure improves the existing registration procedure of a terminal in a network. More specifically, the solution of the present disclosure enables registration of private network terminals to a public network SMSC. Fig. 1 shows a basic flow of a private network terminal registering with a public network SMSC according to an embodiment of the present disclosure. This flow will be described in detail below.

First, after a private network terminal registers with a private network HSS, a private network S-CSCF receives a registration request from the private network terminal and forwards the registration request to a public network SMSC for the private network terminal to register with the public network SMSC in step S101.

As known to those skilled in the art, a terminal in a private network (i.e., a private network terminal) registers with a private network HSS, and after the registration is completed, the private network HSS stores therein information (i.e., registration information) of the private network terminal. After the registration with the private network HSS is completed, the private network terminal may send a registration request (Register message) to initiate registration with the SMSC.

In the prior art, after receiving a registration request from a private network terminal, a private network CSCF forwards the registration request to a private network SMSC so that the private network terminal registers with the private network SMSC, and at this time, the private network CSCF does not forward the registration request to a public network SMSC. However, in the present disclosure, after the private network CSCF receives the registration request, the registration request is forwarded to the public network SMSC in addition to being forwarded to the private network SMSC. In this way, the private network terminal can register with the public network SMSC.

Next, in step S102, the public network SMSC queries the public network HSS for registration information of the private network terminal after receiving the registration request.

After the public network SMSC receives the registration request forwarded by the private network CSCF in step S101, the public network SMSC queries the public network HSS for registration information of the terminal requesting registration. For example, the public network SMSC may transmit a udr (user Data request) message to the public network HSS to request to acquire registration information of the terminal, and the public network HSS queries its registration information based on the number of the terminal and returns the query result (i.e., the registration information) to the public network SMSC through a uda (user Data answer) message.

Finally, in step S103, after the registration information of the private network terminal is not queried from the public network HSS, the public network SMSC obtains the registration information of the private network terminal from the private network HSS to complete the registration of the private network terminal with the public network SMSC.

Since the registration information stored in the public network HSS is the registration information of the public network terminal, and the registration information of the private network terminal is to be queried in step S102, the query in step S102 fails, that is, the public network SMSC does not query the registration information of the private network terminal from the public network HSS. Therefore, in step S103, the public network SMSC acquires registration information of the private network terminal from the private network HSS. As mentioned in the description for step S101, the private network terminal has already registered with the private network HSS, and therefore the private network HSS holds the registration information of the private network terminal. After the registration information of the private network terminal is acquired from the private network HSS, the registration of the private network terminal to the public network SMSC can be completed by using the acquired registration information.

In some embodiments, the public network SMSC is configured with information of a plurality of private network HSS, each of the plurality of private network HSS corresponding to a number segment of a respective private network. Thus, the public network SMSC obtaining the registration information of the private network terminal from the private network HSS may include: determining a private network HSS corresponding to a number segment to which the number of the private network terminal belongs from a plurality of private network HSSs as a private network HSS to which the private network terminal is registered; and acquiring the registration information of the private network terminal from the determined private network HSS. In some embodiments, the public network SMSC may obtain the registration information of the private network terminal by sending a UDR message to the determined HSS, similar to the public network SMSC may obtain the registration information by sending a UDR message to the public network HSS as mentioned above in the description of step S102, and the description is not repeated here. Those skilled in the art should appreciate that the manner in which the public network SMSC obtains the registration information of the private terminal from the private network HSS is not limited to the above manner. That is, the public network SMSC may determine a private network HSS to which the private network terminal is registered in another manner, and then acquire registration information from the determined private network HSS.

As can be understood from the above steps S101, S103, in the present disclosure, the private network CSCF forwards the registration request to the public network SMSC and the public network SMSC acquires the registration information of the private network terminal from the private network HSS, which opens the link between the private network S-CSCF and the public network SMSC and the link between the public network SMSC and the private network HSS, so that the public network SMSC can acquire the state (i.e., the registration information) of the private network terminal in the private network, thereby providing a guarantee for short message interworking between the private network terminal and the public network terminal. The method eliminates the symptom that the private network terminal and the public network terminal can not realize the short message intercommunication in the prior art, namely, the registration data of the private network terminal in the private network is not intercommunicated with the public network, so that the public network can not acquire the registration data of the private network terminal in the private network.

To facilitate a clearer understanding of the process of registering a private network terminal with a public network SMSC, a specific example of this process is given below. Fig. 4 illustrates an example of a detailed procedure of registration of a private network terminal with a public network SMSC according to an embodiment of the present disclosure. The detailed process is performed as follows.

First, in step 1, the private network terminal a sends a Register message to the private network S-CSCF.

Here, as mentioned in the above description with respect to step S101 of fig. 1, after the private network terminal a registers with the private network HSS, the private network terminal a may issue a Register message (i.e., a registration request) to Register with the SMSC, the Register message being routed to the private network S-CSCF.

Next, in step 2, the private network S-CSCF forwards the received Register message to the public network SMSC.

Here, as mentioned in the above description for step S101 of fig. 1, after the private network S-CSCF receives the Register message, the Register message is forwarded to the public network SMSC to Register with the public network SMSC in addition to being forwarded to the private network SMSC. In contrast, in the prior art, the private network S-CSCF forwards only the Register message to the private network SMSC, and does not forward the Register message to the public network SMSC.

Next, in step 3, the public network SMSC transmits a UDR message to the public network HSS after receiving the Register message to query the registration information of the private network terminal a.

Here, as mentioned in the above description for step S102 of fig. 1, the public network SMSC, after receiving the Register message of terminal a, first queries the public network HSS for the registration information of terminal a, which can be achieved by sending a UDR message to the public network HSS.

Next, in step 4, the public network HSS sends a UDA message to the public network SMSC to return a query result for the registration information of the private network terminal a.

Here, as mentioned in the above description of steps S102, S103 of fig. 1, the public network HSS that received the UDR message queries its registration information based on the number of the private network terminal a, and since the private network terminal a is not registered in the public network HSS, the registration information of the private network terminal a cannot be queried in the public network HSS, and this query result (i.e., query failure) is returned to the public network SMSC through the UDA message.

Next, in step 5, the public network SMSC determines the private network HSS corresponding to the number segment to which the number of the private network terminal a belongs.

Here, as mentioned in the above description for step S103 of fig. 1, information of a plurality of private network HSSs, each corresponding to a number segment of a corresponding private network, may be configured in the public network SMSC. After the public network SMSC does not inquire the registration information of the private network terminal A from the public network HSS, the public network SMSC determines a private network HSS corresponding to the number segment to which the number of the private network terminal A belongs in the plurality of private network HSSs, and the determined private network HSS is the private network HSS to which the private network terminal A is registered in the private network.

Next, in step 6, the public network SMSC sends a UDR message to the determined private network HSS to query the private network terminal a for registration information.

Here, as mentioned in the above description with respect to step S103 of fig. 1, after the public network SMSC has not queried the registration information of the private network terminal a from the public network HSS, the public network SMSC queries the private network HSS in which the private network terminal is registered (i.e., the private network HSS determined in step 5) for the registration information of the private network terminal a, which may be implemented by sending a UDR message to the determined private network HSS.

Next, in step 7, the private network HSS sends a UDA message to the public network SMSC to return the query result for the registration information of the private network terminal a.

Here, as mentioned in the above description with respect to step S103 of fig. 1, since the private network terminal a has already registered with the private network HSS, the registration information of the private network terminal a can be queried in the private network HSS, and this query result (i.e., registration information) is returned to the public network SMSC through the UDA message.

Then, in step 8, the registration of the private network terminal in the public network SMSC is completed using the registration information from the private network HSS.

Here, after the public network SMSC acquires the registration information from the private network HSS, the registration of the private network terminal in the public network SMSC can be completed. In this way, the public network SMSC (e.g., DCache node) stores registration information of the private network terminal, which includes information of the private network S-CSCF (e.g., hostname, IP address, port, etc. of the private network S-CSCF), etc., and the stored registration information can be used, for example, when sending a short message to the private network terminal.

Next, in step 9, the public network SMSC returns a 200OK response to the private network S-CSCF, which has informed that the registration with the public network SMSC was successful.

Finally, in step 10, the private network S-CSCF forwards the received 200OK response to the private network terminal a.

Here, it should be noted that the response message 200OK appearing in the above steps 9-10 is well known to those skilled in the art and will not be described in detail here.

So far, the registration of the private network terminal to the public network SMSC has been completed.

It should be further specifically noted that what is shown in fig. 4 is only one example of the process of registering the private network terminal with the public network SMSC, which is only used for illustration and not for limitation, and the registration of the private network terminal with the public network SMSC proposed by the present disclosure is not strictly limited to the process shown in fig. 4. In particular, some details are presented in fig. 4, which may be immaterial or not essential to the solution of the present disclosure.

Those skilled in the art will appreciate that various modifications, such as additions, combinations, deletions, substitutions and the like, may be made in the arrangement of fig. 4 without departing from the spirit and scope of the disclosure. In addition, it should be further noted that fig. 4 is intended to highlight the process of registering the private network terminal with the public network SMSC, and it does not show the processes such as the registration of the private network terminal with the private network HSS and the registration of the private network terminal with the private network SMSC, which are not shown and should be well known to those skilled in the art.

As mentioned above, the solution of the present disclosure also improves the existing procedure of sending short messages by a terminal. After the registration process of the private network terminal to the public network SMSC is introduced, a short message sending process between the private network terminal and the public network terminal will be introduced, and the process includes a process of sending a short message from the private network terminal to the public network terminal and a process of sending a short message from the public network terminal to the private network terminal. Next, a process of sending a short message from a private network terminal to a public network terminal will be described first.

Fig. 2 shows a basic flow of sending a short message from a private network terminal to a public network terminal according to an embodiment of the present disclosure. This flow will be described in detail below.

First, in step S201, the private network S-CSCF receives a short message to be transmitted to a called terminal from a private network terminal and forwards the short message to a private network SMSC.

When a private network terminal (i.e. a calling terminal) sends a short message to a called terminal, the short message is routed to a private network S-CSCF, which forwards the short message to a private network SMSC after it has been received.

Next, in step S202, in case that the private network SMSC determines that the called terminal is not registered in the private network SMSC, the private network S-CSCF forwards the short message to the public network SMSC.

After the private network SMSC receives the short message forwarded by the private network S-CSCF, the private network SMSC determines whether the called terminal is registered in the private network (private network SMSC). When the private network SMSC determines that the called terminal is not registered in the private network, which would result in a delivery failure of the short message via the private network SMSC, the private network S-CSCF will be informed of the delivery failure of the short message (e.g. a return failure status code).

In the prior art, after the private network SMSC returns the result of the short message delivery failure to the private network S-CSCF, the private network S-CSCF does not perform other processing on the short message, and the sending of the short message is terminated in failure. However, in the present disclosure, after learning that the delivery of the short message failed, the private network S-CSCF forwards (i.e., secondary routing) the short message again to the public network SMSC. This enables short messages to reach the public network.

Incidentally, here, for the case where the private network SMSC determines that the called terminal is registered in the private network, this is the sending of the short message inside the private network, and is not a focus of the present disclosure, and is not described in detail here.

Finally, in step S203, the public network SMSC transmits a short message to the called terminal in the case where it is determined that the called terminal is a public network terminal registered in the public network SMSC.

After the public network SMSC receives the short message forwarded by the private network S-CSCF, the public network SMSC will determine whether the called terminal is registered in the public network (public network SMSC). And when the called terminal is determined to be registered in the public network, the public network SMSC sends the short message to the called terminal. The process of sending a short message to a called terminal (public network terminal) by a public network SMSC is well known to those skilled in the art and will not be described in detail here.

As can be appreciated from step S202 above, in the present disclosure, when the called terminal is determined not to be registered in the private network (i.e., not to be a private network terminal), the private network S-CSCF forwards the short message to the public network SMSC, which opens a link between the private network S-CSCF and the public network SMSC, which enables those short messages from the private network terminal that are to be sent to the public network terminal to be eventually successfully sent to the destination. In contrast, according to the related art, those short messages from private network terminals to be transmitted to public network terminals cannot be transmitted to destinations.

In order to facilitate a clearer understanding of the process of sending a short message from a private network terminal to a public network terminal, a specific example of the process is given below. Fig. 5 shows an example of a detailed procedure in which a private network terminal transmits a short message to a public network terminal according to an embodiment of the present disclosure.

In fig. 5, a private network terminal a (calling terminal) will send a short message to a public network terminal B (called terminal), where the public network terminal B has registered in a public network SMSC. The detailed procedure of the short message transmission is performed as follows.

First, in step 1, the private network terminal a sends a short Message to be sent to the public network terminal B to the private network S-CSCF via a Message (RP-MO-DATA) Message.

The private network S-CSCF then forwards the received Message (RP-MO-DATA) Message to the private network SMSC in step 2.

Next, in step 3, the private network SMSC returns a 202 Accepted response to the private network S-CSCF after receiving the Message (RP-MO-DATA) Message.

Next, in step 4, the private network S-CSCF forwards the 202 Accepted response to the private network terminal a.

The above steps 1-4 are the procedures that the short message goes through from the private network terminal to the private network SMSC.

Next, in step 5, the private network SMSC determines that the public network terminal B is not registered in the private network, and informs the private network S-CSCF of the short message delivery failure.

Next, in step 6, the private network S-CSCF forwards the short Message (i.e. Message (RP-MO-DATA) Message) to the public network SMSC after learning that the delivery of the short Message via the private network SMSC failed.

As mentioned above in the description of step S202 of fig. 2, in the present disclosure, in the case where the private network SMSC determines that the public network terminal B is not registered in the private network (which results in a failure in delivery of the short message via the private network SMSC), the private network S-CSCF forwards the short message to the public network SMSC, which opens a link between the private network S-CSCF and the public network SMSC, thereby ensuring that the short message sent by the private network terminal to the public network terminal can be finally sent to the destination, solving the problem in the prior art that the private network terminal cannot send the short message to the public network terminal.

Then, in step 7, the public network SMSC returns a 202 Accepted response to the private network S-CSCF after receiving the Message (RP-MO-DATA) Message.

Next, in step 8, the private network S-CSCF forwards the 202 Accepted response to the private network terminal a.

Next, in step 9, the public network SMSC performs origination processing.

Next, in step 10, the public network SMSC sends a Message (RP-ACK) acknowledge Message to the private network S-CSCF after the call initiation is successful.

Next, in step 11, the private network S-CSCF forwards the Message (RP-ACK) acknowledge Message to the private network terminal a.

Next, in step 12, the private network terminal a returns a 200OK response to the private network S-CSCF.

The private network S-CSCF then forwards the 200OK response to the public network SMSC in step 13.

Steps 9-13 above are the entire origination process.

Next, in step 14, the public network SMSC determines that terminal B is registered in the public network and inquires registration information of terminal B.

After the origination process is finished, the public network SMSC determines whether the called terminal (i.e., terminal B) is registered. Since the terminal B is a public network terminal and is registered in a public network (public network SMSC), the public network SMSC determines that the public network terminal B is registered and inquires its registration information (e.g., information of a public network S-CSCF registered by the public network terminal B) for forwarding of the short message.

Next, in step 15, the public network SMSC sends the short Message to the public network S-CSCF via a Message (RP-MT-DATA) Message.

The public network S-CSCF then forwards the received Message (RP-MT-DATA) Message to the public network terminal B in step 16.

Then, in step 17, the public network terminal B returns a 200OK response to the public network S-CSCF after receiving the Message (RP-MT-DATA) Message.

The public network S-CSCF then forwards the 200OK response to the public network SMSC in step 18.

Then, in step 19, the public network terminal B sends a Message (RP-ACK) acknowledge Message to the public network S-CSCF.

The public network S-CSCF then forwards the Message (RP-ACK) acknowledge Message to the public network SMSC in step 20.

Next, in step 21, the public network SMSC returns a 200OK response to the public network S-CSCF.

Finally, in step 22, the public network S-CSCF forwards the 200OK response to the public network terminal B.

The above steps 15-22 are the procedures that the short message goes through from the public network SMSC to the public network terminal B.

So far, the process of sending the short message from the private network terminal to the public network terminal is completed.

Here, it should be noted that various types of messages appearing in the above steps 1 to 22, i.e., Message (RP-MO-DATA), Message (RP-MT-DATA), Message (RP-ACK), 202 Accepted, 200OK, etc., are well known to those skilled in the art and will not be described in detail here.

It should be noted that what is shown in fig. 5 is only one example of a process of sending a short message from a private network terminal to a public network terminal, and this is for illustrative and non-limiting purposes, and the sending of a short message from a private network terminal to a public network terminal proposed in this disclosure is not strictly limited to the process shown in fig. 5. In particular, some details are presented in fig. 5, which may be immaterial or not essential to the solution of the present disclosure.

Further, those skilled in the art will appreciate that various modifications, such as additions, combinations, deletions, substitutions and the like, may be made in the arrangement of fig. 5 without departing from the spirit and scope of the disclosure. It should be noted that fig. 5 is intended to highlight the process of sending a short message from a private network terminal to a public network terminal, and some other processes may not be shown, and these not shown processes should be well known to those skilled in the art.

Next, a procedure of sending a short message from the public network terminal to the private network terminal will be described.

Fig. 3 shows a basic flow of sending a short message from a public network terminal to a private network terminal according to an embodiment of the present disclosure. This flow will be described in detail below.

First, in step S301, the public network SMSC receives a short message to be transmitted to the called terminal from the public network terminal.

When a public network terminal (i.e. a calling terminal) sends a short message to a called terminal, the short message is routed to the public network SMSC (e.g. via the public network S-CSCF).

Next, in step S302, in case that the public network SMSC determines that the called terminal is a private network terminal registered in the public network SMSC, the public network SMSC forwards the short message to the private network S-CSCF based on the registration information of the called terminal on the public network SMSC.

After the public network SMSC receives the short message from the public network terminal, the public network SMSC determines whether the called terminal is registered in the public network (public network SMSC). As described above, the solution proposed by the present disclosure enables a private network terminal to register with a public network SMSC, i.e., the public network SMSC holds therein registration information of the private network terminal. Therefore, when the public network terminal transmits a short message to the private network terminal as a called terminal, the public network SMSC can determine whether the private network terminal is registered in the public network SMSC. When the public network SMSC determines that the private network terminal is registered in the public network SMSC, the short message is forwarded to the private network S-CSCF based on the registration information (for example, the information of the private network S-CSCF) of the private network terminal in the public network SMSC. This enables short messages to reach the private network.

Finally, in step S303, the private network S-CSCF sends the short message to the called terminal.

After receiving the short message forwarded by public network SMSC, the private network S-CSCF sends the short message to the called terminal.

As can be understood from the above step S302, in the present disclosure, when the called terminal is determined to be a private network terminal that has been registered in the public network SMSC, the public network SMSC forwards the short message to the private network S-CSCF, which opens a link between the public network SMSC and the private network S-CSCF, which enables those short messages from the public network terminal that are to be sent to the private network terminal to be finally successfully sent to the destination. In contrast, according to the related art, those short messages from the public network terminal to be transmitted to the private network terminal cannot be transmitted to the destination.

In order to facilitate a clearer understanding of the process of sending a short message from a public network terminal to a private network terminal, a specific example of the process is given below. Fig. 6 shows an example of a detailed procedure in which a public network terminal transmits a short message to a private network terminal according to an embodiment of the present disclosure.

In fig. 6, a public network terminal B (calling terminal) will send a short message to a private network terminal a (called terminal), where the private network terminal a has registered in a public network SMSC according to the procedure of registration of the private network terminal to the public network SMSC proposed by the present disclosure. The detailed procedure of the short message transmission is performed as follows.

First, in step 1, the public network terminal B sends a short Message to be sent to the private network terminal a to the public network S-CSCF via a Message (RP-MO-DATA) Message.

The public network S-CSCF then forwards the received Message (RP-MO-DATA) Message to the public network SMSC in step 2.

Then, in step 3, the public network SMSC returns a 202 Accepted response to the public network S-CSCF after receiving the Message (RP-MO-DATA) Message.

Then, in step 4, the public network S-CSCF forwards the 202 Accepted response to the public network terminal B.

The above steps 1-4 are the process that the short message goes through from the public network terminal to the public network SMSC.

Next, in step 5, the public network SMSC performs origination processing.

Next, in step 6, the public network SMSC sends a Message (RP-ACK) acknowledge Message to the public network S-CSCF after the call initiation is successful.

Then, in step 7, the public network S-CSCF forwards the Message (RP-ACK) acknowledge Message to the public network terminal B.

Then, in step 8, the public network terminal B returns a 200OK response to the public network S-CSCF.

The public network S-CSCF then forwards the 200OK response to the public network SMSC in step 9.

Steps 5-9 above are the entire origination process.

Next, in step 10, the public network SMSC determines that terminal a is registered in the public network and inquires registration information of terminal a.

After the origination process is finished, the public network SMSC determines whether the called terminal (i.e., terminal a) is registered. As described above, according to the present disclosure, a private network terminal can register with a public network SMSC. When the terminal a has registered in the public network SMSC, the public network SMSC determines that the terminal a has registered and inquires its registration information (e.g., information of a private network S-CSCF with which the terminal a is registered) for forwarding of the short message.

Next, in step 11, the public network SMSC sends the short Message to the private network S-CSCF via a Message (RP-MT-DATA) Message.

As mentioned above in the description of step S302 of fig. 3, in the present disclosure, in the case where the private network terminal a has been registered in the public network SMSC, the public network SMSC forwards the short message to the private network S-CSCF, which opens a link between the public network SMSC and the private network S-CSCF, thereby ensuring that the short message sent by the public network terminal to the private network terminal can be finally sent to the destination, solving the problem in the prior art that the public network terminal cannot send the short message to the private network terminal.

The private network S-CSCF then forwards the received Message (RP-MT-DATA) Message to the private network terminal a in step 12.

Next, in step 13, the private network terminal a returns a 200OK response to the private network S-CSCF after receiving the Message (RP-MT-DATA) Message.

Next, in step 14, the private network S-CSCF forwards the 200OK response to the public network SMSC.

Next, in step 15, the private network terminal a sends a Message (RP-ACK) acknowledge Message to the private network S-CSCF.

The private network S-CSCF then forwards the Message (RP-ACK) acknowledge Message to the public network SMSC in step 16.

Next, in step 17, the public network SMSC returns a 200OK response to the private network S-CSCF.

Finally, in step 18, the private network S-CSCF forwards the 200OK response to the private network terminal a.

The above steps 11-18 are the process that the short message goes through from the public network SMSC to the private network terminal a.

So far, the process of sending the short message from the public network terminal to the private network terminal is completed.

Here, it should be noted that, for the various types of messages appearing in the above steps 1 to 18, i.e., Message (RP-MO-DATA), Message (RP-MT-DATA), Message (RP-ACK), 202 Accepted, 200OK, etc., are well known to those skilled in the art and will not be described in detail here.

It should be noted that what is shown in fig. 6 is only one example of a process of sending a short message from a public network terminal to a private network terminal, and this is for illustrative and non-limiting purposes, and the sending of a short message from a public network terminal to a private network terminal proposed in this disclosure is not strictly limited to the process shown in fig. 6. In particular, some details are presented in fig. 6, which may be immaterial or not essential to the solution of the present disclosure.

Further, those skilled in the art will appreciate that various modifications, such as additions, combinations, deletions, substitutions and the like, may be made in the arrangement of fig. 6 without departing from the spirit and scope of the disclosure. It should be noted that fig. 6 is intended to highlight the process of sending a short message from a public network terminal to a private network terminal, and some other processes may not be shown, and these not shown processes should be well known to those skilled in the art.

So far, the method for implementing short message interworking between a private network terminal and a public network terminal proposed by the present disclosure has been fully described above. As mentioned above, the method for short message interworking proposed by the present disclosure improves the existing registration process of the terminal in the network, the process of the terminal sending the message, and the like, and is a new solution, which implements the short message interworking between the private network terminal and the public network terminal.

The disclosure may also be implemented by a corresponding system. Specifically, the present disclosure further provides a system for implementing short message interworking between a private network terminal and a public network terminal. This system will be briefly described below. Fig. 7 shows a structure of a system for implementing short message interworking between a private network terminal and a public network terminal according to an embodiment of the present disclosure.

As shown in fig. 7, the system 700 includes an S-CSCF 701 and an SMSC702, where the S-CSCF 701 can act as a private network S-CSCF and the SMSC702 can act as a public network SMSC. The S-CSCF 701 and SMSC702 may be configured to perform the above-described method for implementing short message interworking between a private network terminal and a public network terminal. More specifically, S-CSCF 701 may be configured to perform processing performed by a private network S-CSCF in the above-described method, and SMSC702 may be configured to perform processing performed by a public network SMSC in the above-described method. The above description has introduced in detail the method for implementing short message interworking between private network terminal and public network terminal proposed by the present disclosure, wherein the processing performed by the private network S-CSCF and the public network SMSC is clear and clear. Thus, the processing performed by each of the S-CSCF 701, which acts as a private network S-CSCF, and the SMSC702, which acts as a public network SMSC, in the system 700 is also explicit and clear. In view of this, in order to avoid repetitive descriptions, the processes performed by the S-CSCF 701 and the SMSC702 will not be described in detail here.

The present disclosure may also be implemented by a computer program. For example, the program may be stored in a memory of a computer device, which when executed by a processor of the computer device implements the method for encoding of capabilities of a CPE and the method for decoding of capabilities of a CPE of the present disclosure. Alternatively, the program may be stored in a computer readable storage medium, which when executed by a processor implements a method for encoding of capabilities of a CPE and a method for decoding of capabilities of a CPE.

A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of the computer-readable storage medium may include: a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of apparatus, methods and the like according to various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of instructions, which comprises one or more executable instructions for implementing the specified logical function(s). In some alternative implementations, the processes noted in the blocks may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. The order of operations may be adjusted as desired by those skilled in the art. Those skilled in the art may also add more or omit some of these operations as desired.

Any feature described in this specification may, unless stated otherwise, be replaced by alternative features serving the same, equivalent or similar purpose. That is, unless expressly stated otherwise, each feature is only an example of a generic series of equivalent or similar features.

Moreover, although the description of the present disclosure has included description of one or more embodiments, configurations, or aspects, other variations, modifications, and combinations are also within the scope of the present disclosure. The disclosure is intended to obtain rights which include alternative embodiments, configurations, or aspects to the extent permitted, and which include interchangeable, alternate, and/or equivalent structures, functions, or steps to those claimed, whether or not such interchangeable, alternate, and/or equivalent structures, functions, or steps are specifically described in this specification.

Claims (10)

1. A method for realizing short message intercommunication between private network terminal and public network terminal includes:

after the private network terminal registers to the private network HSS, the private network S-CSCF receives a registration request from the private network terminal and forwards the registration request to the public network SMSC for the private network terminal to register to the public network SMSC;

after receiving the registration request, the public network SMSC inquires registration information of the private network terminal from a public network HSS; and

after the public network HSS does not inquire the registration information of the private network terminal, the public network SMSC acquires the registration information of the private network terminal from the private network HSS so as to complete the registration of the private network terminal to the public network SMSC.

2. The method of claim 1, wherein the public network SMSC has information of a plurality of private network HSSs configured therein, each of the plurality of private network HSSs corresponding to a number segment of a corresponding private network, and the public network SMSC acquiring the registration information of the private network terminal from the private network HSS comprises:

determining a private network HSS corresponding to a number segment to which the number of the private network terminal belongs from the plurality of private network HSSs as a private network HSS to which the private network terminal is registered; and

and acquiring the registration information of the private network terminal from the determined private network HSS.

3. The method of claim 2, wherein the public network SMSC obtains the registration information of the private network terminal by sending a User Data Request (UDR) to the determined private network HSS.

4. The method of claim 1, further comprising:

the private network S-CSCF forwards the registration request to the private network SMSC for the private network terminal to register with the private network SMSC.

5. The method of claim 4, further comprising:

the private network S-CSCF receives a short message from the private network terminal to be sent to the called terminal and forwards the short message to the private network SMSC;

under the condition that the private network SMSC determines that the called terminal is not registered in the private network SMSC, the private network S-CSCF forwards the short message to the public network SMSC; and

and the public network SMSC sends the short message to the called terminal under the condition that the called terminal is determined to be the public network terminal registered in the public network SMSC.

6. The method of claim 1, further comprising:

the public network SMSC receives a short message from a public network terminal to be transmitted to a called terminal;

the public network SMSC forwards the short message to a private network S-CSCF based on the registration information of the called terminal on the public network SMSC under the condition that the called terminal is determined to be a private network terminal registered in the public network SMSC; and

and the private network S-CSCF sends the short message to the called terminal.

7. The method as claimed in claim 6, wherein the registration information of the called terminal on the public network SMSC includes information of sending the short message to a private network S-CSCF of the called terminal.

8. The method according to any of claims 1-7, wherein the private network terminals and the public network terminals are VoLTE terminals.

9. A system for implementing short message interworking between private network terminals and public network terminals, the system comprising a private network S-CSCF and a public network SMSC configured to perform the method of any of claims 1-8.

10. A computer-readable storage medium storing a program which, when executed by a processor, implements the method of any one of claims 1-8.

Images