Method, system, and storage medium for message transmission between 5G message users / VoLTE users

Abstract

The present disclosure proposes a method, system, and storage medium for message transmission between 5G message users / VoLTE users. The method includes: the message center on the calling user side receives a message from the calling user to be sent to the called user; the message center on the calling user side obtains the domain name of the called user's home domain from the ENUM server through NAPTR query; the message center on the calling user side obtains the host name of the message center of the called user's home domain corresponding to the domain name of the called user's home domain from the DNS through SRV query; and the message center on the calling user side routes the message to the message center of the called user's home domain according to the host name of the message center of the called user's home domain, so that the message is sent to the called user.

Description

Technical Field

[0001] The present disclosure generally relates to message sending in a mobile communication network, and more specifically to a method, system, and storage medium for message sending between 5G message users / Voice over Long-Term Evolution (VoLTE) users in a mobile communication network. Background Art

[0002] In the current mobile communication network, a 5G message user can send messages to a 5G message user or a VoLTE user. However, when a 5G message user sends a message to a 5G user and the 5G message user who is the called user is not online, or when a 5G message user sends a message to a VoLTE user, the 5G message center on the calling user side needs to convert the message into a traditional SMS and then send it to the called user. Specifically, the 5G message center on the calling user side forwards the converted traditional SMS to the SMS service gateway, and the SMS service gateway analyzes the called user's number and then forwards the traditional SMS to the SMS center on the called user side, so that the traditional SMS is finally sent to the called user. The above-mentioned processing method in which the 5G message center on the calling user side converts the message and sends it to the called user may not be the optimal method.

[0003] More importantly, when a VoLTE user wants to send a message to a 5G message user, the SMS center on the calling user side cannot currently determine whether the called user is a 5G message user, which results in the SMS center being unable to forward the message to the 5G message center on the called user side to send it to the called user. Summary of the invention

[0004] The present disclosure proposes a method, system, and storage medium for sending messages between 5G message users / VoLTE users in a mobile communication network.

[0005] According to one aspect of the present disclosure, a method for sending messages between 5G message users / VoLTE users in a mobile communication network is proposed, the method comprising: a message center on a calling user side receives a message from the calling user and is sent to a called user, wherein the calling user is a 5G message user or a VoLTE user, and the called user is a 5G message user or a VoLTE user, and when the calling user is a 5G message user, the message center on the calling user side is a 5G message center, and when the calling user is a VoLTE user, the message center on the calling user side is a short message center; the message center on the calling user side obtains the domain name of the called user's home domain from an ENUM server through a NAPTR query; the message center on the calling user side obtains the host name of the message center of the called user's home domain corresponding to the domain name of the called user's home domain from a DNS through an SRV query, wherein when the called user is a 5G message user, the message center of the called user's home domain is a 5G message center, and when the called user is a VoLTE user, the message center of the called user's home domain is a 5G message center. In the case of a calling user, the message center of the called user's home domain is a short message center; and the message center on the calling user side routes the message to the message center of the called user's home domain according to the host name of the message center of the called user's home domain, so that the message is sent to the called user.

[0006] According to another aspect of the present disclosure, a method for sending messages between 5G message users / VoLTE users in a mobile communication network is proposed, the method comprising: IBCF receiving a message from a calling user to be sent to a called user, wherein the calling user is a 5G message user or a VoLTE user, the called user is a 5G message user, and the message contains a fallback identifier; the IBCF obtains the domain name of the called user's home domain from an ENUM server through a NAPTR query; the IBCF obtains the host name of a short message center on the called user side corresponding to the domain name of the called user's home domain from a DNS through an SRV query, wherein the short message center on the called user side is located in a domain different from the called user's home domain; and the IBCF routes the message to the short message center on the called user side according to the host name of the short message center on the called user side, so that the message is sent to the called user.

[0007] According to another aspect of the present disclosure, a system for sending messages between 5G message users / VoLTE users in a mobile communication network is proposed, and the system includes a device configured to execute the method for sending messages between 5G message users / VoLTE users in a mobile communication network according to the present disclosure.

[0008] According to another aspect of the present disclosure, a computer-readable storage medium is proposed, which stores a program, and when the program is executed by a processor, the program implements the method for sending messages between 5G message users / VoLTE users in a mobile communication network according to the present disclosure.

[0009] 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.

[0010] 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

[0011] 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.

[0012] Figure 1 The basic process of the method for sending messages between 5G message users / VoLTE users according to an embodiment of the present disclosure is shown.

[0013] Figure 2 The basic process of another method for sending messages between 5G message users / VoLTE users according to an embodiment of the present disclosure is shown.

[0014] Figure 3 A first example of message transmission between 5G message users / VoLTE users according to an embodiment of the present disclosure is shown.

[0015] Figure 4 A second example of message transmission between 5G message users / VoLTE users according to an embodiment of the present disclosure is shown.

[0016] Figure 5 A third example of message transmission between 5G message users / VoLTE users according to an embodiment of the present disclosure is shown.

[0017] Figure 6 A fourth example of message transmission between 5G message users / VoLTE users according to an embodiment of the present disclosure is shown.

[0018] Figure 7 A fifth example of message transmission between 5G message users / VoLTE users according to an embodiment of the present disclosure is shown.

[0019] Figure 8 A sixth example of message sending between 5G message users / VoLTE users according to an embodiment of the present disclosure is shown. DETAILED DESCRIPTION

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

[0021] 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.

[0022] 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.

[0023] In general, the scheme for sending messages between 5G message users / VoLTE users in a mobile communication network proposed in the present disclosure introduces ENUM (E.164 Number URI Mapping) server and DNS (Domain Name System) and corresponding NAPTR (Naming Authority Pointer) query and SRV (SeRVice) query, which is a new message sending scheme and improves the existing message sending scheme. In particular, this message sending scheme solves the problem in the prior art that VoLTE users cannot send messages to 5G message users.

[0024] The following is an overview of the ENUM server and DNS involved in the present disclosure and the corresponding NAPTR query and SRV query.

[0025] First, regarding the ENUM server and NAPTR query: In the present disclosure, in the process of sending a message to the called user, the domain name of the home domain of the called user can be obtained by performing a NAPTR query on the ENUM server.

[0026] More specifically, in the present disclosure, two tables (hereinafter referred to as the first table and the second table) may be stored in the ENUM server, the first table corresponding to the domain name of the home domain of the 5G message user and multiple 5G message users are registered therein, and the second table corresponds to the domain name of the home domain of the VoLTE user and multiple VoLTE users are registered therein. In other words, multiple 5G message users with the same domain name of the home domain are registered in the first table, and multiple VoLTE users with the same domain name of the home domain are registered in the second table. When performing a NAPTR query, the called user can be searched in these two tables, and when the called user is found in the first table or the second table, the domain name of the home domain of the called user can be obtained. Further, when searching for the called user in these two tables, the search priority can be set. For example, the called user is first searched in the first table, and if the called user is not found in the first table, the search continues in the second table. Such a search order can ensure that when the same called user is registered in the first table and the second table at the same time, the domain name of the home domain of the 5G message user corresponding to the first table is obtained as the domain name of the home domain of the called user.

[0027] Secondly, regarding DNS and SRV queries: In the present disclosure, in the process of sending a message to a called user, after obtaining the domain name of the called user's home domain by performing a NAPTR query on the ENUM server, the host name of the message center on the called user side corresponding to the domain name of the called user's home domain can be obtained by performing an SRV query on the DNS.

[0028] More specifically, in the present disclosure, SRV queries are divided into two query types. In one query type (hereinafter referred to as the first query type), the host name of the message center of the called user's home domain corresponding to the domain name of the called user's home domain can be obtained, and in another query type (hereinafter referred to as the second query type), the host name of the SMS center on the called user side corresponding to the domain name of the called user's home domain can be obtained, and the SMS center on the called user side is located in a domain different from the called user's home domain. These two query types can be indicated by corresponding query type identifiers (hereinafter referred to as the first query type identifier and the second query type identifier, respectively).

[0029] The above has been briefly introduced about the ENUM server and DNS and the corresponding NAPTR query and SRV query involved in the present disclosure. The above summary contents can be more clearly understood through the following detailed description. Here, it should be noted that, with respect to the ENUM server and DNS and the corresponding NAPTR query and SRV query, only the contents closely related to the present disclosure are introduced in this document, and the contents that should be well known to those skilled in the art will not be introduced in this document.

[0030] Next, the method proposed in the present disclosure for sending messages between 5G message users / VoLTE users in a mobile communication network will be described. Figure 1 The basic process of the method for sending messages between 5G message users / VoLTE users according to an embodiment of the present disclosure is shown.

[0031] First, in step S101, a message center at the calling user side receives a message from the calling user and further sent to the called user.

[0032] When the calling user sends a message to the called user, the message will first be routed to the message center on the calling user side, that is, the message center on the calling user side in step S101 receives the message. As mentioned above, the present disclosure is directed to message transmission between 5G message users / VoLTE users. Therefore, the calling user in step S101 is a 5G message user or a VoLTE user, and the called user is also a 5G message user or a VoLTE user. In addition, as a person skilled in the art should be aware that, when the calling user is a 5G message user, the message center on the calling user side specifically refers to the 5G message center, and when the calling user is a VoLTE user, the message center on the calling user side specifically refers to the SMS center. Here, it is noted that the "5G message user" mentioned in this article refers to a user who has activated the 5G message service and the "VoLTE user" refers to a user who has activated the VoLTE service, which should be well known to those skilled in the art, so it will not be introduced in detail in this article.

[0033] Next, in step S102, the message center at the calling user side obtains the domain name of the home domain of the called user from the ENUM server through NAPTR query.

[0034] As mentioned above, the scheme for sending messages between 5G message users / VoLTE users proposed in the present disclosure introduces an ENUM server and a corresponding NAPTR query. Step S102 reflects this. Specifically, after the message center on the calling user side receives the message in step S101, the message center needs to obtain the domain name of the called user's home domain from the ENUM server through a NAPTR query in step S102.

[0035] In some implementations, step S102 can be completed by sending and receiving a query request and a query response between a message center on the calling user side and an ENUM server. Specifically, the message center on the calling user side can send a NAPTR query request for querying the domain name of the home domain of the called user to the ENUM server, and the ENUM server obtains the domain name of the home domain of the called user according to the NAPTR query request, and returns a NAPTR query response to the message center on the calling user side, and the NAPTR query response carries the domain name of the home domain of the called user.

[0036] Furthermore, in some implementations, the message received by the message center on the calling user side in step S101 may carry a number in a TEL URL format of the called user, and the number in the TEL URL format of the called user may be carried in a NAPTR query request sent by the message center on the calling user side to the ENUM server for querying the domain name of the called user's home domain. The NAPTR query response returned by the ENUM server to the message center on the calling user side may carry a number in a SIP URL format of the called user, and the number in the SIP URL format of the called user includes the domain name of the called user's home domain.

[0037] Furthermore, in some implementations, as mentioned above, the ENUM server may store a first table of domain names corresponding to the home domains of 5G message users and a second table of domain names corresponding to the home domains of VoLTE users for searching the called user to obtain the domain name of its home domain, and a search priority order may be set. Therefore, the ENUM server obtaining the domain name of the home domain of the called user according to the NAPTR query request may include: the ENUM server first searches the called user in the first table according to the TELURL format number of the called user carried in the NAPTR query request, and when the called user is found in the first table, the corresponding domain name of the home domain can be obtained, and the domain name of the home domain of the called user will be included in the SIP URL format number of the called user; and when the called user is not found in the first table, the ENUM server continues to search the called user in the second table according to the TEL URL format number of the called user, and when the called user is found in the second table, the corresponding domain name of the home domain can be obtained, and the domain name of the home domain of the called user will be included in the SIP URL format number of the called user.

[0038] Now return to Figure 1 After executing step S102, step S103 is then executed. In step S103, the message center on the calling user side obtains the host name of the message center in the home domain of the called user corresponding to the domain name of the home domain of the called user from the DNS through SRV query.

[0039] As mentioned above, DNS and corresponding SRV queries are also introduced in the scheme for sending messages between 5G message users / VoLTE users proposed in the present disclosure. Step S103 reflects this. Specifically, after the message center on the calling user side obtains the domain name of the called user's home domain in step S102, the message center needs to obtain the host name of the message center of the called user's home domain corresponding to the domain name of the called user's home domain obtained in step S102 from the DNS through an SRV query in step S103. Here, as a person skilled in the art, it should also be appreciated that, in the case where the called user is a 5G message user, the message center of the called user's home domain specifically refers to the 5G message center, and in the case where the called user is a VoLTE user, the message center of the called user's home domain specifically refers to the SMS center.

[0040] Similar to step S102, in some implementations, step S103 can be completed by sending and receiving query requests and query responses between the message center on the calling user side and the DNS. Specifically, the message center on the calling user side can send an SRV query request to the DNS for querying the host name of the message center in the home domain of the called user, and the DNS obtains the host name of the message center in the home domain of the called user according to the SRV query request, and returns an SRV query response to the message center on the calling user side, and the SRV query response carries the host name of the message center in the home domain of the called user.

[0041] As mentioned above, in the present disclosure, SRV queries are divided into a first query type and a second query type, and these two query types can be indicated by corresponding query type identifiers. The SRV query in step S103 belongs to the first query type. In some implementations, the SRV query request in step S103 may carry the domain name of the home domain of the called user and the first query type identifier, and the first query type identifier is used to indicate that the message center on the user side is to query the host name of the message center of the home domain of the called user.

[0042] Now return to Figure 1 After executing step S103, step S104 is then executed. In step S104, the message center on the calling user side routes the message to the message center of the called user's home domain according to the host name of the message center of the called user's home domain, so that the message is sent to the called user.

[0043] Specifically, after obtaining the host name of the message center of the called user's home domain in step S103, in step S104, the message center on the calling user side routes the message received in step S101 to the message center of the called user's home domain according to the host name of the message center obtained in step S103. In this way, the message can be finally sent to the called user via the message center of the called user's home domain.

[0044] The above steps S101-S104 mainly involve the process from receiving a message at the message center at the calling user side to sending the message to the message center at the home domain of the called user.

[0045] When the called user is a 5G message user and the called user is not online, after executing step S104, the following steps can be further performed: at this time, the 5G message center, which is the message center of the called user's home domain, obtains the host name of the SMS center on the called user side corresponding to the domain name of the called user's home domain from the DNS through SRV query, and the SMS center on the called user side is located in a domain different from the called user's home domain; and the 5G message center routes the message to the SMS center on the called user side according to the host name of the SMS center on the called user side, so that the message is sent to the called user.

[0046] Specifically, when the message center of the home domain on the called user side receives a message to be sent to the called user, it can be queried whether the called user is online. In the present disclosure, when the called user is a 5G message user and the message center of the home domain on the called user side (i.e., the 5G message center) inquires that the called user is not online, the message will fall back to the traditional SMS, which means that the message will eventually be sent to the called user via the corresponding SMS center instead of the 5G message center. At this time, the 5G message center will obtain the host name of the SMS center on the called user side from the DNS through an SRV query. After obtaining the host name of the SMS center, the 5G message center routes the received message to the SMS center according to the host name of the SMS center. In this way, the message will be sent to the called user via the SMS center. Here, it should be noted that the "fallback" of the message is mentioned above, which is well known to those skilled in the art and will not be introduced in detail here.

[0047] Similar to step S103, in some implementations, when the called user is a 5G message user and the called user is not online, the host name of the SMS center on the called user side can be obtained by sending and receiving query requests and query responses between the 5G message center, which is the message center of the called user's home domain, and the DNS. Specifically, the 5G message center can send an SRV query request to the DNS for querying the host name of the SMS center on the called user side, and the DNS obtains the host name of the SMS center on the called user side according to the SRV query request, and returns an SRV query response to the 5G message center, and the SRV query response carries the host name of the SMS center on the called user side.

[0048] As mentioned above, in the present disclosure, SRV queries are divided into a first query type and a second query type, and these two query types can be indicated by corresponding query type identifiers. The above-mentioned SRV query for obtaining the host name of the SMS center on the called user side belongs to the second query type. In some implementations, the above-mentioned SRV query request may carry the domain name of the called user's home domain and a second query type identifier, and the second query type identifier is used to indicate that the 5G message center is to query the host name of the SMS center on the called user side.

[0049] The method for sending messages between 5G message users / VoLTE users proposed in the present disclosure has been introduced above. In order to understand this method more clearly, a specific example of sending messages between 5G message users / VoLTE users will be given below. Figure 3-7 The first to fifth examples of message transmission between 5G message users / VoLTE users according to an embodiment of the present disclosure are shown.

[0050] First example

[0051] Next, we will describe Figure 3 In the first example shown in FIG. In this example, user A ( Figure 3 In the example, a user A (shown as "UE A" in FIG. 3 ) sends a message to a user B (shown as "UE B" in FIG. 3 ) who is a 5G message user and the user B is online. In addition, it is easy to realize from the following description that the user A, 5G message center A, user B, and 5G message center B involved in this example correspond to the calling user, the message center on the calling user side, the called user, and the message center of the called user's home domain mentioned above, respectively.

[0052] First, in step S1, user A routes a message to 5G message center A, which carries user B's number in the TEL URL format ( Figure 3 (shown as “B number” in the figure).

[0053] Then, in step S2, 5G message center A sends a NAPTR query request to the ENUM server to obtain the domain name of user B's home domain. The NAPTR query request carries user B's number in the TEL URL format.

[0054] Next, in step S3, the ENUM server returns a NAPTR query response to the 5G message center A, and the NAPTR query response carries the number of user B in the SIP URL format ( Figure 3 In the figure, it is shown as "B number@B home domain domain name"), where "B home domain domain name" represents the domain name of user B's home domain.

[0055] Specifically, a first table and a second table are stored in the ENUM server, the first table corresponds to the domain name of the home domain of the 5G message user and multiple 5G message users are registered therein, and the second table corresponds to the domain name of the home domain of the VoLTE user and multiple VoLTE users are registered therein, which has been mentioned in the above description. After the ENUM server receives the NAPTR query request, it first searches for user B in the first table according to the number in the TELURL format of user B carried in the NAPTR query request. Since user B is a 5G message user, user B can be found in the first table, and then the domain name of its home domain can be obtained. Then, the number in the TEL URL format of user B and the domain name of the home domain of user B obtained form the number in the SIP URL format of user B (ie, "B number @ B home domain domain name") and are carried in the NAPTR query response to be returned to the 5G message center A.

[0056] Then, in step S4, 5G message center A sends an SRV query request to DNS for obtaining the host name of 5G message center B. The SRV query request carries the domain name of user B's home domain and a first query type identifier.

[0057] Specifically, after 5G message center A obtains the domain name of user B's home domain from the ENUM server, it sends an SRV query request to the DNS to obtain the host name of the message center of user B's home domain (i.e., 5G message center B) corresponding to the domain name of user B's home domain (this is indicated by the first query type identifier).

[0058] Then, in step S5, DNS returns an SRV query response to 5G message center A, and the SRV query response carries the host name of 5G message center B.

[0059] Specifically, after the DNS receives the SRV query request, the host name of the 5G message center B is obtained according to the domain name of the home domain of user B carried in the SRV query request and the first query type identifier. The obtained host name of the 5G message center B is carried in the SRV query response to be returned to the 5G message center A.

[0060] Next, in step S6, 5G message center A routes the message to 5G message center B according to the host name of 5G message center B. As mentioned in the above description of step S1, the message carries the number of user B.

[0061] Then, in step S7, 5G message center B queries whether user B is online based on the number of user B carried in the received message.

[0062] Finally, in step S8, 5G message center B sends the message to user B.

[0063] Second example

[0064] Next, we will describe Figure 4 The second example is shown in FIG. In this example, user A, which is a 5G message user, sends a message to user B, which is a VoLTE user, and user B is online. In addition, it is easy to realize from the following description that user A, 5G message center A, user B, and SMS center B involved in this example correspond to the calling user, the message center on the calling user side, the called user, and the message center of the called user's home domain mentioned above, respectively.

[0065] first, Figure 4 Step S1 in Figure 3 The process is similar to step S1 in , and will not be described in detail here.

[0066] then, Figure 4 Step S2 in Figure 3 The process is similar to step S2 in , and will not be described in detail here.

[0067] Next, in step S3, the ENUM server returns a NAPTR query response to the 5G message center A, and the NAPTR query response carries the number of user B in the SIP URL format ( Figure 4 In the figure, it is shown as "B number@B home domain domain name"), where "B home domain domain name" represents the domain name of user B's home domain.

[0068] Specifically, as mentioned above, a first table and a second table are stored in the ENUM server. After the ENUM server receives the NAPTR query request, it first searches for user B in the first table according to the number in the TEL URL format of user B carried in the NAPTR query request. Since user B is a VoLTE user, user B is not found in the first table. In this case, continue to search for user B in the second table. After user B is found in the second table, the domain name of its home domain can be obtained. Then, the number in the TELURL format of user B and the domain name of the home domain of user B obtained form the number in the SIP URL format of user B (ie, "B number @ B home domain domain name") and are carried in the NAPTR query response to be returned to the 5G message center A.

[0069] from Figure 4 Step S3 and Figure 3 From the comparison of step S3, it can be seen that due to Figure 4 and Figure 3 The users B in the example are VoLTE users and 5G message users. Figure 4The domain name of the home domain of user B obtained in step S3 is actually the domain name of the home domain of the VoLTE user. Figure 3 The domain name of user B's home domain obtained in step S3 is actually the domain name of the 5G message user's home domain.

[0070] Then, in step S4, 5G message center A sends an SRV query request to DNS to obtain the host name of SMS center B. The SRV query request carries the domain name of user B's home domain and a first query type identifier.

[0071] Specifically, after 5G message center A obtains the domain name of user B's home domain from the ENUM server, it sends an SRV query request to the DNS to obtain the host name of the message center of user B's home domain (i.e., SMS center B) corresponding to the domain name of user B's home domain (this is indicated by the first query type identifier).

[0072] Then, in step S5, DNS returns an SRV query response to 5G message center A, and the SRV query response carries the host name of SMS center B.

[0073] Specifically, after the DNS receives the SRV query request, the host name of the SMS center B is obtained according to the domain name of the home domain of user B carried in the SRV query request and the first query type identifier. The obtained host name of the SMS center B is carried in the SRV query response to be returned to the 5G message center A.

[0074] at last, Figure 4 Steps S6-S8 in Figure 3 The steps S6-S8 in are similar and will not be described in detail here.

[0075] Third Example

[0076] Next, we will describe Figure 5 The third example is shown in FIG. In this example, user A, which is a VoLTE user, sends a message to user B, which is a 5G message user, and user B is online. In addition, it is easy to realize from the following description that user A, SMS center A, user B, and 5G message center B involved in this example correspond to the calling user, the message center on the calling user side, the called user, and the message center of the called user's home domain mentioned above, respectively.

[0077] first, Figure 5 Step S1 in Figure 3 The process is similar to step S1 in , and will not be described in detail here.

[0078] then, Figure 5 Steps S2-S5 in Figure 3The steps S2-S5 in are similar and will not be described in detail here.

[0079] at last, Figure 5 Steps S6-S8 in Figure 3 The steps S6-S8 in are similar and will not be described in detail here.

[0080] Here, it should be noted that Figure 5 and Figure 3 From the comparison, we can see that except Figure 5 The calling user A in the example is a VoLTE user (the corresponding message center on the calling user side is SMS center A), and Figure 3 Except that the calling user A in the example is a 5G message user (the corresponding message center on the calling user side is 5G message center A), the rest are the same. Figure 5 Steps S1-S8 in are described in detail, but based on the above Figure 3 The description of the message sending process in the first example in FIG. 1 should be easily known to those skilled in the art. Figure 5 The message sending process in the third example.

[0081] Fourth Example

[0082] Next, we will describe Figure 6 The fourth example is shown in FIG. In this example, user A, which is a VoLTE user, sends a message to user B, which is a VoLTE user, and user B is online. In addition, it is easy to realize from the following description that user A, SMS center A, user B, and SMS center B involved in this example correspond to the calling user, the message center on the calling user side, the called user, and the message center of the called user's home domain mentioned above, respectively.

[0083] first, Figure 6 Step S1 in Figure 4 The process is similar to step S1 in , and will not be described in detail here.

[0084] then, Figure 6 Steps S2-S5 in Figure 4 The steps S2-S5 in are similar and will not be described in detail here.

[0085] at last, Figure 6 Steps S6-S8 in Figure 4 The steps S6-S8 in are similar and will not be described in detail here.

[0086] Here, it should be noted that Figure 6 and Figure 4 From the comparison, we can see that except Figure 6The calling user A in the example is a VoLTE user (the corresponding message center on the calling user side is SMS center A), and Figure 4 Except that the calling user A in the example is a 5G message user (the corresponding message center on the calling user side is 5G message center A), the rest are the same. Figure 6 Steps S1-S8 in are described in detail, but based on the above Figure 4 The description of the message sending process in the second example in FIG. 1 should be easily known by those skilled in the art. Figure 6 The message sending process in the fourth example.

[0087] Fifth example

[0088] Next, we will describe Figure 7 The fifth example shown in . In the first to fourth examples above, the called user is online. The fifth example mainly involves the scenario where the called user is a 5G message user and the called user is not online. Specifically, Figure 7 The process shown in Figure 3 and Figure 5 In step S7 of FIG. 1 , if it is determined that user B is not online, the process to be continued is performed. In view of this, Figure 7 middle, Figure 3 and Figure 5 Steps S1-S6 in are no longer shown, and only the process from when the 5G message center B determines that user B is not online is shown. Figure 4 and Figure 6 The process to be executed when it is determined in step S7 that user B is not online is a process in the prior art, which is not the focus of this disclosure and will not be introduced here.

[0089] First, in step S1, 5G message center B checks the number of user B carried in the received message and finds that user B is not online. At this time, the message will fall back to traditional SMS, which means that it will be sent via the SMS center on user B's side (i.e., Figure 7 SMS center B) sends it to user B.

[0090] Then, in step S2, 5G message center B sends an SRV query request to DNS to obtain the host name of SMS center B. The SRV query request carries the domain name of user B's home domain and a second query type identifier.

[0091] Specifically, after 5G message center B queries and finds that user B is not online, it sends an SRV query request to DNS to obtain the host name of the SMS center on user B's side (i.e., SMS center B) corresponding to the domain name of user B's home domain (this is indicated by the second query type identifier).

[0092] Then, in step S3, DNS returns an SRV query response to 5G message center B, which carries the host name of SMS center B.

[0093] Specifically, after the DNS receives the SRV query request, the host name of the SMS center B is obtained according to the domain name of the home domain of user B and the second query type identifier carried in the SRV query request. The obtained host name of the SMS center B is carried in the SRV query response to be returned to the 5G message center B.

[0094] Then, in step S4, 5G message center B routes the message to SMS center B according to the host name of SMS center B, and the message carries B number and fallback flag. Here, the fallback flag is intended to inform SMS center B that the message is a message that has experienced fallback.

[0095] Finally, in step S5, SMS center B sends the message to user B.

[0096] The above is the message sending process between 5G message users / VoLTE users, specifically, between 5G message users and 5G message users, between 5G message users and VoLTE users, and between VoLTE users and VoLTE users.

[0097] In particular, the above description introduces the message sending process in a scenario where the called user is a 5G message user and the called user is not online. In the above message sending process, the judgment of whether the called user is online or not is performed on the called user side. The present disclosure further proposes a message sending method in a scenario where the called user is a 5G message user and the calling user side has determined that the called user is not online.

[0098] More specifically, the above message sending method for determining whether the called user is online on the called user side is mainly aimed at the message sending between users on the same network (that is, the calling user and the called user belong to the same mobile communication network), while the message sending method to be introduced below in the scenario where the called user is a 5G message user and the calling user side has determined that the called user is not online is mainly aimed at the message sending between users on different networks (that is, the calling user and the called user belong to different mobile communication networks). Figure 2 This method is described in detail.

[0099] First, in step S201, the IBCF (Interconnection Border Control Function) receives a message from the calling user and further sent to the called user.

[0100] When it comes to sending messages between users of different networks, the message sent by the calling user will be routed to IBCF (i.e., IBCF receives the message in step S201), and then routed to the called user via IBCF. It should be noted that the network element IBCF here should be well known to those skilled in the art and will not be introduced in detail here. Here, the calling user in step S201 is a 5G message user or a VoLTE user, and the called user is a 5G message user. In addition, the message in step S201 carries a fallback identifier. Through this identifier, IBCF can realize that the received message will fall back to traditional SMS, which means that the message will be sent to the called user via the SMS center on the called user side, rather than via the message center of its home domain (i.e., 5G message center). As mentioned above, the meaning of "fallback" is well known to those skilled in the art and will not be introduced in detail here.

[0101] Next, in step S202, the IBCF obtains the domain name of the home domain of the called user from the ENUM server through NAPTR query. Figure 1 That is, after the IBCF receives the message in step S201, the IBCF needs to obtain the domain name of the home domain of the called user from the ENUM server through NAPTR query.

[0102] Similarly, in some implementations, step S202 can be completed by sending and receiving a query request and a query response between the IBCF and the ENUM server. Specifically, the IBCF can send a NAPTR query request to the ENUM server for querying the domain name of the called user's home domain. The ENUM server obtains the domain name of the called user's home domain based on the NAPTR query request, and returns a NAPTR query response to the IBCF, where the NAPTR query response carries the domain name of the called user's home domain.

[0103] Further, in some implementations, the message received by the IBCF in step S201 may carry a number in a TEL URL format of the called user, and the number in the TEL URL format of the called user may be carried in a NAPTR query request sent by the IBCF to the ENUM server for querying the domain name of the called user's home domain. The NAPTR query response returned by the ENUM server to the IBCF may carry a number in a SIP URL format of the called user, and the number in the SIP URL format of the called user includes the domain name of the called user's home domain.

[0104] Furthermore, in some implementations, as mentioned above, the ENUM server stores a first table of domain names corresponding to the home domains of 5G message users and a second table of domain names corresponding to the home domains of VoLTE users for searching the called user to obtain the domain name of its home domain. Therefore, in the case where the called user discussed here is limited to the 5G message user, the ENUM server obtains the domain name of the home domain of the called user according to the NAPTR query request, which may include: The ENUM server searches for the called user in the first table according to the TEL URL format number of the called user carried in the NAPTR query request. When the called user is found in the first table, the corresponding domain name of the home domain can be obtained, and the domain name of the home domain of the called user will be included in the SIP URL format number of the called user.

[0105] Now return to Figure 2 After executing step S202, step S203 is then executed. In step S203, IBCF obtains the host name of the SMS center on the called user side corresponding to the domain name of the called user's home domain from the DNS through SRV query, and the SMS center on the called user side is located in a domain different from the called user's home domain.

[0106] Specifically, as mentioned above, when the calling user side has determined that the called user is not online, the message received by the IBCF will fall back to the traditional SMS, that is, the message will be sent to the called user via the SMS center on the called user side. Therefore, after the IBCF obtains the domain name of the home domain of the called user from the ENUM server in step S202, the IBCF obtains the corresponding host name of the SMS center on the called user side from the DNS through SRV query in step S203.

[0107] Similarly, in some implementations, the host name of the SMS center on the called user side can be obtained by sending and receiving query requests and query responses between IBCF and DNS. Specifically, IBCF can send an SRV query request to the DNS for querying the host name of the SMS center on the called user side, and the DNS obtains the host name of the SMS center on the called user side according to the SRV query request, and returns an SRV query response to the IBCF, and the SRV query response carries the host name of the SMS center on the called user side.

[0108] Similarly, the SRV query for obtaining the host name of the SMS center on the called user side belongs to the second query type. In some implementations, the SRV query request may carry the domain name of the called user's home domain and a second query type identifier, which is used to indicate that the IBCF is to query the host name of the SMS center on the called user side.

[0109] Now return to Figure 2 After executing step S203, step S204 is then executed. In step S204, IBCF routes the message to the SMS center of the called user according to the host name of the SMS center of the called user, so that the message is sent to the called user.

[0110] Specifically, after obtaining the host name of the SMS center on the called user side in step S203, in step S204, the IBCF routes the message received in step S201 to the SMS center on the called user side according to the host name of the SMS center obtained in step S203. In this way, the message can be finally sent to the called user via the SMS center on the called user side.

[0111] The message sending method proposed by the present disclosure in the scenario where the called user is a 5G message user and the calling user side has determined that the called user is offline has been introduced above. Similarly, in order to understand this method more clearly, a specific example will be given below. Figure 8 A sixth example of message sending between 5G message users / VoLTE users according to an embodiment of the present disclosure is shown.

[0112] Next, we will describe Figure 8 The sixth example shown in FIG. In this example, user A, which is a 5G message user or a VoLTE user, sends a message to user B, which is a 5G message user, and user B is not online.

[0113] First, in step S1, the IBCF receives a message from user A, which carries the number of user B in the TEL URL format ( Figure 8 "B number" in the figure) and the fallback mark.

[0114] Next, in step S2, the IBCF sends a NAPTR query request for obtaining the domain name of the home domain of user B to the ENUM server. The NAPTR query request carries the number of user B in the TEL URL format.

[0115] Next, in step S3, the ENUM server returns a NAPTR query response to the IBCF, and the NAPTR query response carries the number of user B in the SIP URL format ( Figure 8 In the figure, it is shown as "B number@B home domain domain name"), where "B home domain domain name" represents the domain name of user B's home domain.

[0116] Specifically, a first table and a second table are stored in the ENUM server, the first table corresponds to the domain name of the home domain of the 5G message user and multiple 5G message users are registered therein, and the second table corresponds to the domain name of the home domain of the VoLTE user and multiple VoLTE users are registered therein, which has been mentioned in the above description. After the ENUM server receives the NAPTR query request, user B is found in the first table according to the number of user B in the TEL URL format carried in the NAPTR query request, and then the domain name of its home domain is obtained. Then, the number of user B in the TEL URL format and the obtained domain name of user B's home domain form the number of user B in the SIP URL format (that is, "B number @ B home domain domain name") and are carried in the NAPTR query response to be returned to the IBCF.

[0117] Next, in step S4, the IBCF sends an SRV query request for obtaining the host name of the SMS center B to the DNS. The SRV query request carries the domain name of the home domain of user B and the second query type identifier.

[0118] Specifically, when user B is offline, IBCF sends an SRV query request to the DNS for obtaining the host name of the SMS center on user B's side (ie, SMS center B) corresponding to the domain name of user B's home domain (this is indicated by the second query type identifier).

[0119] Next, in step S5, the DNS returns an SRV query response to the IBCF, where the SRV query response carries the host name of the SMS center B.

[0120] Specifically, after the DNS receives the SRV query request, it obtains the host name of SMS center B according to the domain name of user B's home domain and the second query type identifier carried in the SRV query request. The obtained host name of SMS center B is carried in the SRV query response and returned to IBCF.

[0121] Next, in step S6, IBCF routes the message to SMS center B according to the host name of SMS center B. The message carries B number and fallback flag. Here, the fallback flag is intended to inform SMS center B that the message is a message that has experienced fallback.

[0122] Finally, in step S7, SMS center B sends the message to user B.

[0123] The above is the message sending process between 5G message users / VoLTE users, specifically, the calling user is a 5G message user or a VoLTE user, the called user is a 5G message user, and the calling user side has determined that the called user is not online.

[0124] So far, the message sending method between 5G message users / VoLTE users proposed in the present disclosure has been fully introduced above. As mentioned above, the message sending method proposed in the present disclosure introduces ENUM and DNS query mechanisms, which is a brand-new message sending method that improves the existing message sending method. For example, the message sending method of the present disclosure does not require the 5G message center on the calling user side to convert the 5G message into a traditional SMS to send to the called user in some cases as in the prior art. In particular, this message sending method of the present disclosure solves the problem in the prior art that VoLTE users cannot send messages to 5G message users.

[0125] The present disclosure can also be implemented through a communication system. Specifically, the present disclosure also proposes a system for sending messages between 5G message users / VoLTE users, which includes a device configured to execute the method for sending messages between 5G message users / VoLTE users described above. The method for sending messages between 5G message users / VoLTE users proposed in the present disclosure has been described in detail above, and those skilled in the art should easily realize that these methods can be implemented by corresponding devices. In view of this, these devices and the functions they perform are no longer described in detail herein.

[0126] 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.

[0127] The computer readable storage medium may 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 may 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.

[0128] 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.

[0129] 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.

[0130] 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 sending messages between 5G message users / VoLTE users in a mobile communication network, the method comprising: The message center on the calling user side receives a message from the calling user to be sent to the called user, wherein the calling user is a 5G message user or a VoLTE user, the called user is a 5G message user or a VoLTE user, and when the calling user is a 5G message user, the message center on the calling user side is a 5G message center, and when the calling user is a VoLTE user, the message center on the calling user side is a short message center; The message center at the calling user side obtains the domain name of the home domain of the called user from the ENUM server through NAPTR query; The message center on the calling user side obtains the host name of the message center of the called user's home domain corresponding to the domain name of the called user's home domain from the DNS through SRV query, wherein, when the called user is a 5G message user, the message center of the called user's home domain is the 5G message center, and when the called user is a VoLTE user, the message center of the called user's home domain is the SMS center; and The message center at the calling user side routes the message to the message center at the home domain of the called user according to the host name of the message center at the home domain of the called user, so that the message is sent to the called user; Wherein, when the called user is a 5G message user and the called user is not online, the 5G message center, which is the message center of the called user's home domain, obtains the host name of the SMS center on the called user side corresponding to the domain name of the called user's home domain from the DNS through SRV query, wherein the SMS center on the called user side is located in a domain different from the home domain of the called user; and the 5G message center routes the message to the SMS center on the called user side according to the host name of the SMS center on the called user side, so that the message is sent to the called user; Among them, when the calling user is a 5G message user, the called user is a VoLTE user and the called user is online, the 5G message center on the calling user side obtains the host name of the SMS center on the called user side corresponding to the domain name of the called user's home domain from the DNS through SRV query; the 5G message center on the calling user side directly routes the message to the SMS center on the called user side according to the host name of the SMS center on the called user side, so that the message is sent to the called user.

2. The method according to claim 1, wherein: The message center at the calling user side obtains the domain name of the home domain of the called user from the ENUM server through NAPTR query, including: The message center at the calling user side sends a first NAPTR query request for querying the domain name of the home domain of the called user to the ENUM server; and The ENUM server obtains the domain name of the home domain of the called user according to the first NAPTR query request, and returns a first NAPTR query response to the message center on the calling user side, wherein the first NAPTR query response carries the domain name of the home domain of the called user.

3. The method according to claim 2, wherein: The message received by the message center on the calling user side carries the number of the called user in TEL URL format, the number of the called user in TEL URL format is carried in the first NAPTR query request for querying the domain name of the called user's home domain, the first NAPTR query response carries the number of the called user in SIP URL format, and the domain name of the called user's home domain is included in the number of the called user in SIP URL format.

4. The method according to claim 3, wherein: A first table and a second table are stored in the ENUM server, the first table corresponds to the domain name of the home domain of the 5G message user and multiple 5G message users are registered, the second table corresponds to the domain name of the home domain of the VoLTE user and multiple VoLTE users are registered, and the ENUM server obtains the domain name of the home domain of the called user according to the first NAPTR query request, including: The ENUM server searches the first table for the called user according to the number in the TEL URL format of the called user carried in the first NAPTR query request, and obtains the domain name of the corresponding home domain to be included in the number in the SIP URL format of the called user when the called user is found in the first table; and When the called user is not found in the first table, the ENUM server searches for the called user in the second table according to the TEL URL format number of the called user carried in the first NAPTR query request, and when the called user is found in the second table, obtains the domain name of the corresponding home domain to be included in the SIP URL format number of the called user.

5. The method according to any one of claims 1 to 4, wherein: The message center at the calling user side sends a first SRV query request for querying the host name of the message center of the home domain of the called user to the DNS; and The DNS obtains the host name of the message center of the called user's home domain according to the first SRV query request, and returns a first SRV query response to the message center on the calling user side, wherein the first SRV query response carries the host name of the message center of the called user's home domain.

6. The method according to claim 5, wherein: The first SRV query request carries the domain name of the called user's home domain and a first query type identifier, where the first query type identifier is used to indicate that the message center on the user side is to query the host name of the message center in the called user's home domain.

7. The method according to any one of claims 1 to 6, wherein: The 5G message center on the calling user side sends a second SRV query request to the DNS for querying the host name of the SMS center on the called user side; and The DNS obtains the host name of the SMS center on the called user side according to the second SRV query request, and returns a second SRV query response to the 5G message center on the calling user side, wherein the second SRV query response carries the host name of the SMS center on the called user side.

8. The method according to claim 7, wherein: The second SRV query request carries the domain name of the called user's home domain and a second query type identifier, and the second query type identifier is used to indicate that the 5G message center on the calling user side wants to query the host name of the SMS center on the called user side.

9. A method for sending messages between 5G message users / VoLTE users in a mobile communication network, applied to a scenario where the called user is not online, the method comprising: The IBCF receives a message from a calling user to be sent to a called user, wherein the calling user is a 5G message user or a VoLTE user, the called user is a 5G message user, and the message includes a fallback identifier; The IBCF obtains the domain name of the home domain of the called user from the ENUM server through NAPTR query; The IBCF obtains the host name of the SMS center on the called user side corresponding to the domain name of the home domain of the called user from the DNS through SRV query, wherein the SMS center on the called user side is located in a domain different from the home domain of the called user; and The IBCF directly routes the message to the SMS center on the called user side according to the host name of the SMS center on the called user side, so that the message is sent to the called user.

10. The method according to claim 9, wherein: The IBCF obtains the domain name of the home domain of the called user from the ENUM server through NAPTR query, including: The IBCF sends a NAPTR query request for querying the domain name of the home domain of the called user to the ENUM server; as well as The ENUM server obtains the domain name of the home domain of the called user according to the NAPTR query request, and returns a NAPTR query response to the IBCF, wherein the NAPTR query response carries the domain name of the home domain of the called user.

11. The method according to claim 10, wherein: The message received by the IBCF carries the number of the called user in TEL URL format, the number of the called user in TEL URL format is carried in the NAPTR query request for querying the domain name of the called user's home domain, the NAPTR query response carries the number of the called user in SIP URL format, and the domain name of the called user's home domain is included in the number of the called user in SIP URL format.

12. The method according to claim 11, wherein: A first table and a second table are stored in the ENUM server, the first table corresponds to the domain name of the home domain of the 5G message user and multiple 5G message users are registered, the second table corresponds to the domain name of the home domain of the VoLTE user and multiple VoLTE users are registered, and the ENUM server obtains the domain name of the home domain of the called user according to the NAPTR query request, including: The ENUM server searches the first table for the called user according to the TEL URL format number of the called user carried in the NAPTR query request, and obtains the domain name of the corresponding home domain to be included in the SIP URL format number of the called user when the called user is found in the first table.

13. The method according to any one of claims 9 to 12, wherein: The IBCF obtains the host name of the SMS center on the called user side from the DNS through SRV query, including: The IBCF sends an SRV query request for querying the host name of the SMS center on the called user side to the DNS; and The DNS obtains the host name of the SMS center on the called user side according to the SRV query request, and returns an SRV query response to the IBCF, wherein the SRV query response carries the host name of the SMS center on the called user side.

14. The method according to claim 13, wherein: The SRV query request carries the domain name of the home domain of the called user and a query type identifier, and the query type identifier is used to indicate that the IBCF is to query the host name of the SMS center on the called user side.

15. A system for sending messages between 5G message users / VoLTE users in a mobile communication network, the system comprising an apparatus configured to execute the method according to any one of claims 1-8.

16. A system for sending messages between 5G message users / VoLTE users in a mobile communication network, the system comprising an apparatus configured to execute the method according to any one of claims 9-14.

17. A computer-readable storage medium storing a program, wherein the program, when executed by a processor, implements the apparatus of the method according to any one of claims 1 to 8.

18. A computer-readable storage medium storing a program, which, when executed by a processor, implements the apparatus of the method according to any one of claims 9 to 14.

Images