Method, system, and storage medium for realizing short message intercommunication between private network terminals and public network terminals
By establishing a registration link between the private network terminal and the public network SMSC, the problem of inability to communicate between the private network terminal and the public network terminal is solved, and the interoperability of short messages is achieved to ensure that the messages can be successfully transmitted between the two.
Patent Information
- Application Number
- CN202011377122.4
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2020-11-30
- Publication Date
- 2024-11-05
- Estimated Expiration
- 2040-11-30
AI Technical Summary
Existing private network terminals cannot achieve short message interoperability with public network terminals, resulting in users being unable to receive or send short messages on public network terminals, especially verification codes and emergency notifications.
After registering with the private network HSS on the private network terminal, the private network S-CSCF forwards the registration request to the public network SMSC. The public network SMSC query and obtains the registration information of the private network terminal to realize the registration of the private network terminal to the public network SMSC. And when sending a short message, if the called terminal does not register in the private network SMSC, it is forwarded to the public network SMSC to ensure message delivery.
The short message interoperability between the private network terminal and the public network terminal is realized, and the problem that the existing technology of the private network terminal and the public network terminal cannot be communicated, ensuring that the short message can be successfully sent and received.
Smart Images

Figure CN114584936B_ABST
Abstract
Description
Technical Field
[0001] The present disclosure generally relates to data communication in private networks and public networks, and more specifically to a method, system, and storage medium for implementing short message intercommunication between private network terminals and public network terminals. Background Art
[0002] At present, for the communication of some specific areas (for example, coal mines, mines, railways, etc.) that cannot be covered by the public communication network (hereinafter referred to as the public network) provided by network operators (for example, China Telecom, etc.), various enterprises have built proprietary communication networks (hereinafter referred to as private networks). However, at present, these private networks can only realize the sending and receiving of short messages within the network, but cannot realize the intercommunication of short messages with the public network. For example, after a terminal enters the private network from the public network, the terminal in the private network (hereinafter referred to as the private network terminal) completes the registration in the private network. However, since the registration data of the private network terminal in the private network is not interoperable with the public network, the private network terminal can only send and receive short messages with other private network terminals in the private network, but cannot send and receive short messages with terminals in the public network (hereinafter referred to as public network terminals). That is, at present, the private network terminal can neither receive short messages (especially some verification codes, notifications of urgent matters, etc.) from the public network terminal, nor send short messages to the public network terminal, which brings great inconvenience to users. Therefore, it is necessary to break down the barriers between private networks and public networks to achieve short message intercommunication between private network terminals and public network terminals. Summary of the invention
[0003] The present disclosure proposes a method, a system, and a storage medium for realizing short message intercommunication between a private network terminal and a public network terminal.
[0004] According to one aspect of the present disclosure, a method for realizing short message intercommunication between a private network terminal and a public network terminal is proposed, comprising: after the private network terminal registers with 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 with the public network SMSC; after receiving the registration request, the public network SMSC queries the public network HSS for registration information of the private network terminal; and after failing to query the registration information of the private network terminal 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.
[0005] In some embodiments, the public network SMSC is configured with information of multiple private network HSSs, each of the multiple private network HSSs corresponds to a number segment of a corresponding private network, and the public network SMSC obtains the registration information of the private network terminal from the private network HSS, including: determining the private network HSS corresponding to the number segment to which the number of the private network terminal belongs from the multiple private network HSSs as the private network HSS to which the private network terminal is registered; and obtaining the registration information of the private network terminal from the determined private network HSS.
[0006] In some embodiments, 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.
[0007] In some embodiments, the above method further includes: the private network S-CSCF forwarding the registration request to the private network SMSC for the private network terminal to register with the private network SMSC.
[0008] In some embodiments, the above method also includes: the private network S-CSCF receives a short message from a private network terminal to be sent to a called terminal, and forwards the short message to a private network SMSC; when 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 a public network SMSC; and when the public network SMSC determines that the called terminal is a public network terminal that has been registered in the public network SMSC, the public network SMSC sends the short message to the called terminal.
[0009] In some embodiments, the above method also includes: the public network SMSC receives a short message from a public network terminal to be sent to a called terminal; when 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; and the private network S-CSCF sends the short message to the called terminal.
[0010] In some embodiments, the registration information of the called terminal on the public network SMSC includes information for sending the short message to the private network S-CSCF of the called terminal.
[0011] In some embodiments, the private network terminal and the public network terminal are VoLTE terminals.
[0012] According to another aspect of the present disclosure, a system for implementing short message intercommunication between a private network terminal and a public network terminal is proposed. The system includes a private network S-CSCF and a public network SMSC configured to execute the above method.
[0013] According to another aspect of the present disclosure, a computer-readable storage medium is provided, wherein the computer-readable storage medium stores a program, and the program implements the above method when executed by a processor.
[0014] A brief overview of the disclosure is given above in order to provide a basic understanding of some aspects of the disclosure. However, it should be understood that this overview is not an exhaustive overview of the disclosure. It is not intended to be used to identify the key or important parts of the disclosure, nor is it intended to be used to limit the scope of the disclosure. Its purpose is merely to give some concepts about the disclosure in a simplified form as a prelude to a more detailed description given later.
[0015] Other features and advantages of the present disclosure will become more apparent from the following detailed description of various embodiments of the present disclosure with reference to the accompanying drawings. BRIEF DESCRIPTION OF THE DRAWINGS
[0016] The accompanying drawings, which constitute a part of this specification, illustrate various embodiments of the present disclosure and, together with the description, serve to explain the principles of the present disclosure.
[0017] Figure 1 The basic process of registering a private network terminal with a public network SMSC according to an embodiment of the present disclosure is shown.
[0018] Figure 2 The basic process of sending a short message from a private network terminal to a public network terminal according to an embodiment of the present disclosure is shown.
[0019] Figure 3 The basic process of sending a short message from a public network terminal to a private network terminal according to an embodiment of the present disclosure is shown.
[0020] Figure 4 An example of a detailed process of registering a private network terminal with a public network SMSC according to an embodiment of the present disclosure is shown.
[0021] Figure 5 An example of a detailed process of a private network terminal sending a short message to a public network terminal according to an embodiment of the present disclosure is shown.
[0022] Figure 6 An example of a detailed process of a public network terminal sending a short message to a private network terminal according to an embodiment of the present disclosure is shown.
[0023] Figure 7 The structure of a system for implementing short message intercommunication between a private network terminal and a public network terminal according to an embodiment of the present disclosure is shown. DETAILED DESCRIPTION
[0024] Hereinafter, various embodiments of the present disclosure will be described in detail with reference to the accompanying drawings.
[0025] It should be noted that in the following detailed description, many specific details are set forth to provide a thorough understanding of the described embodiments. However, it should be clear to those skilled in the art that the described embodiments can be implemented without some or all of these specific details. In addition, in the described embodiments, in order to avoid unnecessarily obscuring the concepts of the present disclosure, some well-known contents are not described in detail, and where appropriate, these contents should be considered as part of the specification.
[0026] In addition, the steps of the methods presented in this disclosure are illustrative. In some embodiments, these methods may have one or more additional steps not described herein and / or omit one or more steps described herein. Moreover, the order in which the steps of these methods are illustrated and described is not restrictive.
[0027] In general, the present disclosure proposes a solution to the problem that short message intercommunication between private network terminals and public network terminals is currently impossible. The solution realizes short message intercommunication between private network terminals and public network terminals. More specifically, the solution improves the existing terminal registration process in the network and the process of terminal sending messages, and is a new solution.
[0028] Before introducing the solution proposed in the present disclosure in detail, it should be noted that the following description will involve various network elements, namely, S-CSCF (Serving-Call Session Control Function), HSS (Home Subscriber Server), SMSC (Short Message Service Center), which are network elements in IMS (IP Multimedia Subsystem). For those skilled in the art, these network elements should be well known, and they will not be introduced in detail in this article. As can be appreciated from the previous description and the subsequent description, the private network S-CSCF, private network HSS, private network SMSC, and public network S-CSCF, public network HSS, and public network SMSC in this article represent the network elements S-CSCF, HSS, and SMSC of the private network and the public network, respectively.
[0029] In addition, those skilled in the art should be able to appreciate that the terminal involved in this document may be, for example, a VoLTE (Voice over Long-Term Evolution) terminal, a 5G terminal, and any other type of terminal that can be applied to the solution of the present disclosure. Similarly, as can be appreciated from the previous description and the subsequent description, the private network terminal and the public network terminal in this document represent terminals in the private network and the public network, respectively, and in particular, the private network terminal may be a terminal that roams from the public network into the private network.
[0030] In addition, as mentioned above in the background technology, the public network in this article represents a public communication network provided by network operators (for example, China Telecom, etc.), and the private network is a concept relative to the public network, which represents a non-public (i.e., private) communication network. These networks are generally built by enterprises themselves (for example, coal mines, mines, railway enterprises, etc.).
[0031] As mentioned above, the solution of the present disclosure improves the existing registration process of a terminal in a network. More specifically, the solution of the present disclosure implements the registration of a private network terminal to a public network SMSC. Figure 1 The basic process of a private network terminal registering with a public network SMSC according to an embodiment of the present disclosure is shown. This process will be described in detail below.
[0032] First, in step S101, after the private network terminal registers with 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 with the public network SMSC.
[0033] As known to those skilled in the art, a terminal in a private network (i.e., a private network terminal) will register with the private network HSS, and after the registration is completed, the private network HSS will store the information of the private network terminal (i.e., registration information). After the registration with the private network HSS is completed, the private network terminal will send a registration request (Register message) to initiate registration with the SMSC.
[0034] In the prior art, after receiving a registration request from a private network terminal, the private network CSCF forwards the registration request to the private network SMSC so that the private network terminal registers with the private network SMSC. At this time, the private network CSCF does not forward the registration request to the public network SMSC. However, in the present disclosure, after receiving a registration request, the private network CSCF not only forwards the registration request to the private network SMSC, but also forwards the registration request to the public network SMSC. In this way, the private network terminal can register with the public network SMSC.
[0035] Next, in step S102, after receiving the registration request, the public network SMSC queries the public network HSS for registration information of the private network terminal.
[0036] After the public network SMSC receives the registration request forwarded by the private network CSCF in step S101, the public network SMSC will query the registration information of the terminal requested for registration from the public network HSS. For example, the public network SMSC can send a UDR (User Data Request) message to the public network HSS to request the registration information of the terminal. The public network HSS queries the registration information based on the terminal number and returns the query result (i.e., registration information) to the public network SMSC through a UDA (User Data Answer) message.
[0037] Finally, in step S103, after failing to query the registration information of the private network terminal 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.
[0038] Since the registration information stored in the public network HSS is the registration information of the public network terminal, and what is to be queried in step S102 is the registration information of the private network terminal, 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 obtains the registration information of the private network terminal from the private network HSS. As mentioned in the description of step S101, the private network terminal has registered with the private network HSS, so the registration information of the private network terminal is stored in the private network HSS. After obtaining the registration information of the private network terminal from the private network HSS, the registration of the private network terminal to the public network SMSC can be completed using the obtained registration information.
[0039] In some embodiments, the public network SMSC is configured with information of multiple private network HSSs, and each of the multiple private network HSSs corresponds to the number segment of the corresponding private network. In this way, the public network SMSC may obtain the registration information of the private network terminal from the private network HSS, including: determining the private network HSS corresponding to the number segment to which the number of the private network terminal belongs from the multiple private network HSSs as the private network HSS to which the private network terminal is registered; and obtaining 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, which is similar to the public network SMSC mentioned in the description of step S102 that can obtain the registration information by sending a UDR message to the public network HSS, and the description is not repeated here. Those skilled in the art should be able to appreciate that the way in which the public network SMSC obtains the registration information of the private network terminal from the private network HSS is not limited to the above-mentioned way. That is, the public network SMSC may determine the private network HSS to which the private network terminal is registered by other means, and then obtain the registration information from the determined private network HSS.
[0040] As can be understood from the above steps S101 and S103, in the present disclosure, the private network CSCF forwards the registration request to the public network SMSC and the public network SMSC obtains the registration information of the private network terminal from the private network HSS, which opens up 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 obtain the state of the private network terminal in the private network (i.e., registration information), thereby providing a guarantee for the short message intercommunication between the private network terminal and the public network terminal. This eliminates the problem in the prior art that the private network terminal and the public network terminal cannot realize the short message intercommunication, that is, the registration data of the private network terminal in the private network is not intercommunication with the public network, resulting in the public network being unable to obtain the registration data of the private network terminal in the private network.
[0041] In order to more clearly understand the process of a private network terminal registering with a public network SMSC, a specific example of this process is given below. Figure 4 An example of a detailed process of a private network terminal registering with a public network SMSC according to an embodiment of the present disclosure is shown. The detailed process is performed according to the following steps.
[0042] First, in step 1, private network terminal A sends a Register message to the private network S-CSCF.
[0043] Here, as in the above Figure 1 As mentioned in the description of step S101, after the private network terminal A registers with the private network HSS, the private network terminal A will send a Register message (ie, a registration request) to register with the SMSC, and the Register message is routed to the private network S-CSCF.
[0044] Next, in step 2, the private network S-CSCF forwards the received Register message to the public network SMSC.
[0045] Here, as in the above Figure 1 As mentioned in the description of step S101, after the private network S-CSCF receives the Register message, in addition to forwarding the Register message to the private network SMSC, the Register message is also forwarded to the public network SMSC to register with the public network SMSC. In contrast, in the prior art, the private network S-CSCF only forwards the Register message to the private network SMSC, and does not forward the Register message to the public network SMSC.
[0046] Next, in step 3, after receiving the Register message, the public network SMSC sends a UDR message to the public network HSS to query the registration information of the private network terminal A.
[0047] Here, as in the above Figure 1As mentioned in the description of step S102, after receiving the Register message from terminal A, the public network SMSC will first query 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.
[0048] Next, in step 4, the public network HSS sends a UDA message to the public network SMSC to return the query result of the registration information of the private network terminal A.
[0049] Here, as in the above Figure 1 As mentioned in the description of steps S102 and S103, the public network HSS that receives the UDR message queries the registration information of the private network terminal A based on the number of the private network terminal A. 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. This query result (i.e., query failure) is returned to the public network SMSC through the UDA message.
[0050] 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.
[0051] Here, as in the above Figure 1 As mentioned in the description of step S103, the public network SMSC may be configured with information of multiple private network HSSs, and each private network HSS corresponds to the number segment of the corresponding private network. After the public network SMSC fails to query the registration information of the private network terminal A from the public network HSS, 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 among the multiple 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.
[0052] Next, in step 6, the public network SMSC sends a UDR message to the determined private network HSS to query the registration information of the private network terminal A.
[0053] Here, as in the above Figure 1 As mentioned in the description of step S103, after the public network SMSC fails to query the registration information of the private network terminal A from the public network HSS, the public network SMSC queries the registration information of the private network terminal A from the private network HSS where the private network terminal is registered in the private network (i.e., the private network HSS determined in step 5), which can be achieved by sending a UDR message to the determined private network HSS.
[0054] Next, in step 7, the private network HSS sends a UDA message to the public network SMSC to return the query result of the registration information of the private network terminal A.
[0055] Here, as in the above Figure 1As mentioned in the description of step S103, since the private network terminal A has 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 (ie, registration information) is returned to the public network SMSC via a UDA message.
[0056] Next, in step 8, the registration information from the private network HSS is used to complete the registration of the private network terminal in the public network SMSC.
[0057] Here, after the public network SMSC obtains the registration information from the private network HSS, the private network terminal can complete the registration of the public network SMSC. In this way, the public network SMSC (for example, DCache node) saves the registration information of the private network terminal, which includes the information of the private network S-CSCF (for example, the host name, IP address, port, etc. of the private network S-CSCF), etc. The saved registration information can be used, for example, when sending a short message to the private network terminal.
[0058] Next, in step 9, the public network SMSC returns a 200 OK response to the private network S-CSCF, notifying that the registration with the public network SMSC is successful.
[0059] Finally, in step 10, the private network S-CSCF forwards the received 200 OK response to private network terminal A.
[0060] It should be noted here that the response message 200OK in the above steps 9-10 is well known to those skilled in the art and will not be described in detail here.
[0061] So far, the registration of the private network terminal to the public network SMSC has been completed.
[0062] In addition, it is necessary to point out that Figure 4 The content shown in the figure is only an example of the process of registering a private network terminal with a public network SMSC, which is only for the purpose of illustration and not limitation. The registration of a private network terminal with a public network SMSC proposed in the present disclosure does not need to be strictly limited to Figure 4 In particular, Figure 4 Some details are presented in the embodiment, which may be immaterial and not essential to the solution of the present disclosure.
[0063] Those skilled in the art will be able to appreciate that, without departing from the subject and spirit of the present disclosure, Figure 4 Various modifications can be made based on the above, such as adding, merging, deleting, replacing, etc. In addition, it should be noted that Figure 4It aims to highlight the process of private network terminal registering with public network SMSC. It does not show processes such as the registration of private network terminal with private network HSS and the registration of private network terminal with private network SMSC. These processes not shown should be well known to those skilled in the art.
[0064] As mentioned above, the solution disclosed in the present invention also improves the existing process of sending short messages from a terminal. After introducing the registration process of a private network terminal to a public network SMSC, the process of sending short messages between a private network terminal and a public network terminal will be introduced next. This process includes the process of a private network terminal sending a short message to a public network terminal and the process of a public network terminal sending a short message to a private network terminal. Below, the process of sending a short message from a private network terminal to a public network terminal is first introduced.
[0065] Figure 2 The basic process of a private network terminal sending a short message to a public network terminal according to an embodiment of the present disclosure is shown. This process will be described in detail below.
[0066] First, in step S201, the private network S-CSCF receives a short message from a private network terminal to be sent to a called terminal, and forwards the short message to a private network SMSC.
[0067] When a private network terminal (ie, a calling terminal) sends a short message to a called terminal, the short message is routed to the private network S-CSCF. After receiving the short message, the private network S-CSCF forwards it to the private network SMSC.
[0068] Next, in step S202, when 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.
[0069] After the private network SMSC receives the short message forwarded by the private network S-CSCF, the private network SMSC will determine 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 will cause the delivery failure of the short message via the private network SMSC), it will inform the private network S-CSCF of the failure of the delivery of the short message (for example, return a failure status code).
[0070] 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 any other processing on the short message, and the sending of the short message ends in failure. However, in the present disclosure, after learning that the delivery failure of the short message is known, the private network S-CSCF forwards the short message again (i.e., secondary routing) to the public network SMSC. This allows the short message to reach the public network.
[0071] Here, it is mentioned in passing that, for the case where the private network SMSC determines that the called terminal is registered in the private network, this belongs to the sending of short messages within the private network, which is not the focus of this disclosure and will not be described in detail here.
[0072] Finally, in step S203, when the public network SMSC determines that the called terminal is a public network terminal that has been registered in the public network SMSC, the public network SMSC sends the short message to the called terminal.
[0073] 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). When it is determined that the called terminal is registered in the public network, the public network SMSC sends the short message to the called terminal. The process of the public network SMSC sending the short message to the called terminal (public network terminal) is well known to those skilled in the art and will not be described in detail here.
[0074] As can be understood from the above step S202, in the present disclosure, when the called terminal is determined not to be registered in the private network (i.e., not a private network terminal), the private network S-CSCF forwards the short message to the public network SMSC, which opens up the link between the private network S-CSCF and the public network SMSC, so that those short messages from the private network terminal to be sent to the public network terminal can finally be successfully sent to the destination. In contrast, according to the prior art, those short messages from the private network terminal to be sent to the public network terminal cannot be sent to the destination.
[0075] In order to more clearly understand the process of a private network terminal sending a short message to a public network terminal, a specific example of this process is given below. Figure 5 An example of a detailed process of a private network terminal sending a short message to a public network terminal according to an embodiment of the present disclosure is shown.
[0076] exist Figure 5 In the example, private network terminal A (calling terminal) will send a short message to public network terminal B (called terminal), where public network terminal B has been registered in the public network SMSC. The detailed process of sending a short message is performed according to the following steps.
[0077] First, in step 1, the private network terminal A sends the short message to be sent to the public network terminal B to the private network S-CSCF via the Message (RP-MO-DATA) message.
[0078] Next, in step 2, the private network S-CSCF forwards the received Message (RP-MO-DATA) to the private network SMSC.
[0079] Next, in step 3, after receiving the Message (RP-MO-DATA) message, the private network SMSC returns a 202 Accepted response to the private network S-CSCF.
[0080] Next, in step 4, the private network S-CSCF forwards the 202 Accepted response to the private network terminal A.
[0081] The above steps 1-4 are the processes that the short message goes through from the private network terminal to the private network SMSC.
[0082] 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.
[0083] Next, in step 6, after learning that the delivery of the short message via the private network SMSC fails, the private network S-CSCF forwards the short message (ie, Message (RP-MO-DATA) message) to the public network SMSC.
[0084] As mentioned above, Figure 2 As mentioned in the description of step S202, in the present disclosure, when the private network SMSC determines that the public network terminal B is not registered in the private network (which causes the failure of 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 up the link between the private network S-CSCF and the public network SMSC, thereby ensuring that the short messages sent from the private network terminal to the public network terminal can eventually be sent to the destination, solving the problem in the prior art that the private network terminal cannot send short messages to the public network terminal.
[0085] Next, in step 7, after receiving the Message (RP-MO-DATA) message, the public network SMSC returns a 202 Accepted response to the private network S-CSCF.
[0086] Next, in step 8, the private network S-CSCF forwards the 202 Accepted response to the private network terminal A.
[0087] Next, in step 9, the public network SMSC performs call initiation processing.
[0088] Next, in step 10, after the call is successfully initiated, the public network SMSC sends a confirmation message (RP-ACK) to the private network S-CSCF.
[0089] Next, in step 11, the private network S-CSCF forwards the Message (RP-ACK) confirmation message to the private network terminal A.
[0090] Next, in step 12, the private network terminal A returns a 200 OK response to the private network S-CSCF.
[0091] Next, in step 13, the private network S-CSCF forwards the 200 OK response to the public network SMSC.
[0092] The above steps 9-13 are the entire call processing process.
[0093] Next, in step 14, the public network SMSC determines that terminal B is registered in the public network and queries terminal B's registration information.
[0094] After the call origination process is completed, the public network SMSC determines whether the called terminal (i.e., terminal B) is registered. Since terminal B is a public network terminal and has been registered in the public network (public network SMSC), the public network SMSC determines that public network terminal B has been registered and queries its registration information (e.g., information of the public network S-CSCF where public network terminal B is registered) to forward the short message.
[0095] Next, in step 15, the public network SMSC sends the short message to the public network S-CSCF via the Message (RP-MT-DATA) message.
[0096] Next, in step 16, the public network S-CSCF forwards the received Message (RP-MT-DATA) to the public network terminal B.
[0097] Next, in step 17, after receiving the Message (RP-MT-DATA), the public network terminal B returns a 200 OK response to the public network S-CSCF.
[0098] Next, in step 18, the public network S-CSCF forwards the 200 OK response to the public network SMSC.
[0099] Next, in step 19, the public network terminal B sends a Message (RP-ACK) confirmation message to the public network S-CSCF.
[0100] Next, in step 20, the public network S-CSCF forwards the Message (RP-ACK) confirmation message to the public network SMSC.
[0101] Next, in step 21, the public network SMSC returns a 200 OK response to the public network S-CSCF.
[0102] Finally, in step 22, the public network S-CSCF forwards the 200 OK response to the public network terminal B.
[0103] The above steps 15-22 are the processes that the short message goes through from the public network SMSC to the public network terminal B.
[0104] So far, the process of sending short messages from the private network terminal to the public network terminal has been completed.
[0105] It should be noted here that various types of messages appearing in the above steps 1-22, namely, Message (RP-MO-DATA), Message (RP-MT-DATA), Message (RP-ACK), 202 Accepted, 200 OK, etc., are well known to those skilled in the art and will not be introduced in detail here.
[0106] In addition, it is necessary to point out that Figure 5 The content shown in the figure is only an example of the process of sending a short message from a private network terminal to a public network terminal, which is only for the purpose of illustration and not limitation. The sending of short messages from a private network terminal to a public network terminal proposed in the present disclosure does not need to be strictly limited to Figure 5 In particular, Figure 5 Some details are presented in the embodiment, which may be immaterial and not essential to the solution of the present disclosure.
[0107] In addition, those skilled in the art should be able to appreciate that without departing from the subject and spirit of the present disclosure, Figure 5 Various modifications can be made based on the above, such as adding, merging, deleting, replacing, etc. In addition, it should be noted that Figure 5 The purpose is to highlight the process of a private network terminal sending a short message to a public network terminal. Some other processes may not be shown, and these processes not shown should be well known to those skilled in the art.
[0108] Next, the process of sending short messages from a public network terminal to a private network terminal will be introduced.
[0109] Figure 3 The basic process of a public network terminal sending a short message to a private network terminal according to an embodiment of the present disclosure is shown. This process will be described in detail below.
[0110] First, in step S301, the public network SMSC receives a short message from a public network terminal to be sent to a called terminal.
[0111] When a public network terminal (ie, a calling terminal) sends a short message to a called terminal, the short message is routed to a public network SMSC (eg, via a public network S-CSCF).
[0112] Next, in step S302, when 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 in the public network SMSC.
[0113] After the public network SMSC receives the short message from the public network terminal, the public network SMSC will determine whether the called terminal is registered in the public network (public network SMSC). As described above, the solution proposed by the present disclosure enables the private network terminal to register with the public network SMSC, that is, the registration information of the private network terminal is stored in the public network SMSC. Therefore, when the public network terminal sends a short message to the private network terminal as the 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 has registered in the public network SMSC, the short message will be forwarded to the private network S-CSCF based on the registration information of the private network terminal in the public network SMSC (for example, the information of the private network S-CSCF). This enables the short message to reach the private network.
[0114] Finally, in step S303, the private network S-CSCF sends the short message to the called terminal.
[0115] After receiving the short message forwarded by the public network SMSC, the private network S-CSCF sends the short message to the called terminal.
[0116] 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 up the link between the public network SMSC and the private network S-CSCF, so that those short messages from the public network terminal to be sent to the private network terminal can finally be successfully sent to the destination. In contrast, according to the prior art, those short messages from the public network terminal to be sent to the private network terminal cannot be sent to the destination.
[0117] In order to more clearly understand the process of a public network terminal sending a short message to a private network terminal, a specific example of this process is given below. Figure 6 An example of a detailed process of a public network terminal sending a short message to a private network terminal according to an embodiment of the present disclosure is shown.
[0118] exist Figure 6 In the example, the public network terminal B (calling terminal) will send a short message to the private network terminal A (called terminal), where the private network terminal A has registered with the public network SMSC according to the process of registering the private network terminal with the public network SMSC proposed in the present disclosure. The detailed process of sending the short message is performed according to the following steps.
[0119] First, in step 1, the public network terminal B sends the short message to be sent to the private network terminal A to the public network S-CSCF via the Message (RP-MO-DATA) message.
[0120] Next, in step 2, the public network S-CSCF forwards the received Message (RP-MO-DATA) to the public network SMSC.
[0121] Next, in step 3, after receiving the Message (RP-MO-DATA) message, the public network SMSC returns a 202 Accepted response to the public network S-CSCF.
[0122] Next, in step 4, the public network S-CSCF forwards the 202 Accepted response to the public network terminal B.
[0123] The above steps 1-4 are the processes that the short message goes through from the public network terminal to the public network SMSC.
[0124] Next, in step 5, the public network SMSC performs call initiation processing.
[0125] Next, in step 6, the public network SMSC sends a confirmation message (RP-ACK) to the public network S-CSCF after the call is successfully initiated.
[0126] Next, in step 7, the public network S-CSCF forwards the Message (RP-ACK) confirmation message to the public network terminal B.
[0127] Next, in step 8, the public network terminal B returns a 200 OK response to the public network S-CSCF.
[0128] Next, in step 9, the public network S-CSCF forwards the 200 OK response to the public network SMSC.
[0129] The above steps 5-9 are the entire call processing process.
[0130] Next, in step 10, the public network SMSC determines that terminal A is registered in the public network and queries the registration information of terminal A.
[0131] After the call initiation process is completed, the public network SMSC determines whether the called terminal (i.e., terminal A) is registered. As described above, according to the present disclosure, the private network terminal can register with the public network SMSC. When terminal A has registered in the public network SMSC, the public network SMSC determines that terminal A has registered and queries its registration information (e.g., information of the private network S-CSCF where terminal A is registered) to forward the short message.
[0132] Next, in step 11, the public network SMSC sends the short message to the private network S-CSCF via the Message (RP-MT-DATA) message.
[0133] As mentioned above, Figure 3 As mentioned in the description of step S302, in the present disclosure, when 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 up the link between the public network SMSC and the private network S-CSCF, thereby ensuring that the short messages sent from the public network terminal to the private network terminal can eventually be sent to the destination, solving the problem in the prior art that the public network terminal cannot send short messages to the private network terminal.
[0134] Next, in step 12, the private network S-CSCF forwards the received Message (RP-MT-DATA) to the private network terminal A.
[0135] Next, in step 13, after receiving the Message (RP-MT-DATA), the private network terminal A returns a 200 OK response to the private network S-CSCF.
[0136] Next, in step 14, the private network S-CSCF forwards the 200 OK response to the public network SMSC.
[0137] Next, in step 15, the private network terminal A sends a Message (RP-ACK) confirmation message to the private network S-CSCF.
[0138] Next, in step 16, the private network S-CSCF forwards the Message (RP-ACK) confirmation message to the public network SMSC.
[0139] Next, in step 17, the public network SMSC returns a 200 OK response to the private network S-CSCF.
[0140] Finally, in step 18, the private network S-CSCF forwards the 200 OK response to the private network terminal A.
[0141] The above steps 11-18 are the processes that the short message goes through from the public network SMSC to the private network terminal A.
[0142] So far, the process of sending short messages from the public network terminal to the private network terminal has been completed.
[0143] It should be noted here that various types of messages appearing in the above steps 1-18, namely, Message (RP-MO-DATA), Message (RP-MT-DATA), Message (RP-ACK), 202 Accepted, 200 OK, etc., are well known to those skilled in the art and will not be introduced in detail here.
[0144] In addition, it is necessary to point out that Figure 6 The content shown in the figure is only an example of the process of a public network terminal sending a short message to a private network terminal, which is only for the purpose of illustration and not limitation. The sending of short messages from a public network terminal to a private network terminal proposed in the present disclosure does not need to be strictly limited to Figure 6 In particular, Figure 6 Some details are presented in the embodiment, which may be immaterial and not essential to the solution of the present disclosure.
[0145] In addition, those skilled in the art should be able to appreciate that without departing from the subject and spirit of the present disclosure, Figure 6 Various modifications can be made based on the above, such as adding, merging, deleting, replacing, etc. In addition, it should be noted that Figure 6 The purpose is to highlight the process of a public network terminal sending a short message to a private network terminal. Some other processes may not be shown, and these processes not shown should be well known to those skilled in the art.
[0146] So far, the method for realizing short message intercommunication between private network terminals and public network terminals proposed in the present disclosure has been fully introduced. As mentioned above, the method for short message intercommunication proposed in the present disclosure improves the existing terminal registration process in the network and the process of terminal sending messages, and is a new solution that realizes short message intercommunication between private network terminals and public network terminals.
[0147] The present disclosure can also be implemented through a corresponding system. Specifically, the present disclosure also proposes a system for implementing short message intercommunication between a private network terminal and a public network terminal. This system will be briefly introduced below. Figure 7 The structure of a system for implementing short message intercommunication between a private network terminal and a public network terminal according to an embodiment of the present disclosure is shown.
[0148] like Figure 7As shown in , the system 700 includes an S-CSCF 701 and an SMSC 702, wherein the S-CSCF 701 can act as a private network S-CSCF, and the SMSC 702 can act as a public network SMSC. The S-CSCF 701 and the SMSC 702 can be configured to execute the above-described method for realizing short message intercommunication between a private network terminal and a public network terminal. More specifically, the S-CSCF 701 can be configured to execute the processing performed by the private network S-CSCF in the above-described method, and the SMSC 702 can be configured to execute the processing performed by the public network SMSC in the above-described method. The above description has introduced in detail the method for realizing short message intercommunication between a private network terminal and a public network terminal proposed in the present disclosure, wherein the processing performed by the private network S-CSCF and the public network SMSC is clear and explicit. Therefore, the processing performed by the S-CSCF 701 acting as the private network S-CSCF and the SMSC 702 acting as the public network SMSC in the system 700 is also clear and explicit. In view of this, in order to avoid repeated description, the processing performed by S-CSCF 701 and SMSC 702 will not be described in detail here.
[0149] 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 implements the method for encoding the capabilities of a CPE and the method for decoding the capabilities of a CPE of the present disclosure when executed by a processor of the computer device. Alternatively, the program may be stored in a computer-readable storage medium, which implements the method for encoding the capabilities of a CPE and the method for decoding the capabilities of a CPE when executed by a processor.
[0150] The computer readable storage medium can be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared or semiconductor system, device or apparatus, or any suitable combination of the foregoing. More specific examples of computer readable storage media can include: a portable computer disk, 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 disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
[0151] The flowcharts and block diagrams in the accompanying drawings illustrate possible architectures, functions, and operations of the devices, methods, etc. according to various embodiments of the present disclosure. In this regard, each box in the flowchart or block diagram may represent a portion of a module, segment, or instruction, which includes one or more executable instructions for implementing one or more specified logical functions. In some alternative implementations, the processing marked in the box may also occur in an order different from that marked in the accompanying drawings. For example, depending on the functions involved, two consecutive boxes may actually be executed substantially in parallel, or the boxes may sometimes be executed in reverse order. Those skilled in the art may adjust the order of operations as needed. Those skilled in the art may also add more operations or omit some of the operations as needed.
[0152] Any feature described in this specification, unless otherwise specified, can be replaced by other equivalent or alternative features with similar purposes. That is, unless otherwise specified, each feature is only an example in a series of equivalent or similar features.
[0153] In addition, although the description of the present disclosure has included descriptions of one or more embodiments, configurations, or aspects, other variations, modifications, and combinations are also within the scope of the present disclosure. The present disclosure is intended to obtain rights, which should include alternative embodiments, configurations, or aspects within the permitted scope, and including structures, functions, or steps that are interchangeable, alternative, and / or equivalent to those structures, functions, or steps claimed, regardless of whether these interchangeable, alternative, and / or equivalent structures, functions, or steps are specifically described in this specification.
Claims
1. A method for implementing short message intercommunication between a private network terminal and a public network terminal, comprising: After the private network terminal registers with the private network HSS, the private network S-CSCF receives the registration request from the private network terminal and forwards the registration request to the public network SMSC for the private network terminal to register with the public network SMSC; After receiving the registration request, the public network SMSC queries the public network HSS for the registration information of the private network terminal; as well as After failing to query the registration information of the private network terminal 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.
2. The method according to claim 1, wherein: The public network SMSC is configured with information of multiple private network HSSs, each of the multiple private network HSSs corresponds to a number segment of a corresponding private network, and the public network SMSC obtains registration information of a private network terminal from the private network HSS, including: Determine, from the multiple private network HSSs, the private network HSS corresponding to the number segment to which the number of the private network terminal belongs as the private network HSS to which the private network terminal is registered; and The registration information of the private network terminal is obtained from the determined private network HSS.
3. The method according to 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 according to claim 1, further comprising: The private network S-CSCF forwards the registration request to the private network SMSC so that the private network terminal can register with the private network SMSC.
5. The method according to 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; When 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; as well as When the public network SMSC determines that the called terminal is a public network terminal that has been registered in the public network SMSC, the public network SMSC sends the short message to the called terminal.
6. The method according to claim 1, further comprising: The public network SMSC receives the short message from the public network terminal to be sent to the called terminal; When the public network SMSC determines that the called terminal is a private network terminal that has 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; as well as The private network S-CSCF sends the short message to the called terminal.
7. The method according to claim 6, wherein: The registration information of the called terminal on the public network SMSC includes information for sending the short message to the private network S-CSCF of the called terminal.
8. The method according to any one of claims 1 to 7, wherein: Private network terminals and public network terminals are VoLTE terminals.
9. A system for implementing short message intercommunication between a private network terminal and a public network terminal, the system comprising a private network S-CSCF and a public network SMSC configured to execute the method described in any one of claims 1 to 8.
10. A computer-readable storage medium storing a program, which, when executed by a processor, implements the method according to any one of claims 1 to 8.
Citation Information
Patent Citations
2G / 3G core network interworking method and system in condition that terminal roams to 4G special network
CN105636006A
Method and system for intercommunication of 3G special network and public network
CN105848084A
Method for disrupting numbers of private network subscribers based on call forwarding service
CN106375974A
Realization method and device for public network user accessing private network
CN109561430A
Method for short message communication between private network and public network
CN110896527A
