CN114422964A - Method, system, and storage medium for messaging between 5G messaging users/VoLTE users - Google Patents

Method, system, and storage medium for messaging between 5G messaging users/VoLTE users Download PDF

Info

Publication number
CN114422964A
CN114422964A CN202011175435.1A CN202011175435A CN114422964A CN 114422964 A CN114422964 A CN 114422964A CN 202011175435 A CN202011175435 A CN 202011175435A CN 114422964 A CN114422964 A CN 114422964A
Authority
CN
China
Prior art keywords
called user
message center
user
message
called
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202011175435.1A
Other languages
Chinese (zh)
Inventor
张冬梅
毛安平
章磊
黄美华
吴永梅
陈尚干
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
China Telecom Corp Ltd
Original Assignee
China Telecom Corp Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by China Telecom Corp Ltd filed Critical China Telecom Corp Ltd
Priority to CN202011175435.1A priority Critical patent/CN114422964A/en
Publication of CN114422964A publication Critical patent/CN114422964A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/12—Messaging; Mailboxes; Announcements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/02—Terminal devices
    • H04W88/022—Selective call receivers
    • H04W88/023—Selective call receivers with message or information receiving capability
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/18—Service support devices; Network management devices
    • H04W88/184—Messaging devices, e.g. message centre

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Telephonic Communication Services (AREA)

Abstract

The present disclosure presents methods, systems, and storage media for messaging between 5G messaging users/VoLTE users. The method comprises the following steps: a message center at a calling user side receives a message which is sent to a called user from a calling user; the message center of the calling subscriber side obtains the domain name of the home domain of the called subscriber from an ENUM server through NAPTR query; the message center of the calling user side obtains the host name of the message center of the home domain of the called user corresponding to the domain name of the home domain of the called user from DNS through SRV query; and the message center of the calling user side routes the message to the message center of the home domain of the called user according to the host name of the message center of the home domain of the called user, so that the message is sent to the called user.

Description

Method, system, and storage medium for messaging between 5G messaging users/VoLTE users
Technical Field
The present disclosure relates generally to message transmission in a mobile communication network, and more particularly, to a method, system, and storage medium for message transmission between 5G message users/VoLTE (Voice over Long-Term Evolution) users in a mobile communication network.
Background
In current mobile communication networks, a 5G messaging subscriber can send messages to either a 5G messaging subscriber or a VoLTE subscriber. However, in a case where a 5G message subscriber sends a message to a 5G subscriber and the 5G message subscriber as a called subscriber is not online, or in a case where the 5G message subscriber sends a message to a VoLTE subscriber, the 5G message center on the calling subscriber side needs to convert the message into a conventional short message and send the conventional short message to the called subscriber. Specifically, the 5G message center of the calling user side forwards the converted traditional short message to the short message service gateway, and the short message service gateway forwards the traditional short message to the short message center of the called user side after analyzing the number of the called user, so that the traditional short message is finally sent to the called user. The above processing method of sending the message to the called user after the message conversion is performed by the 5G message center on the calling user side may not be the optimal method.
More importantly, when a VoLTE user wants to send a message to a 5G message user, the short message center of the calling user side cannot determine whether the called user is the 5G message user at present, which results in that the short message center cannot forward the message to the 5G message center of the called user side to send the message to the called user.
Disclosure of Invention
The present disclosure presents methods, systems, and storage media for messaging between 5G messaging users/VoLTE users in a mobile communication network.
According to an aspect of the present disclosure, a method for message transmission between 5G message users/VoLTE users in a mobile communication network is proposed, the method comprising: a message center of a calling party side receives a message which is from a calling party and is sent to a called party, wherein the calling party is a 5G message user or a VoLTE user, the called party is a 5G message user or a VoLTE user, the message center of the calling party side is the 5G message center under the condition that the calling party is the 5G message user, and the message center of the calling party side is a short message center under the condition that the calling party is the VoLTE user; the message center of the calling subscriber side obtains the domain name of the home domain of the called subscriber from an ENUM server through NAPTR query; the message center of the calling user side obtains a host name of the message center of the home domain of the called user corresponding to the domain name of the home domain of the called user from a DNS through SRV inquiry, wherein the message center of the home domain of the called user is a 5G message center under the condition that the called user is a 5G message user, and the message center of the home domain of the called user is a short message center under the condition that the called user is a VoLTE user; and the message center of the calling user side routes the message to the message center of the home domain of the called user according to the host name of the message center of the home domain of the called user, so that the message is sent to the called user.
According to another aspect of the present disclosure, a method for message transmission between 5G message users/VoLTE users in a mobile communication network is proposed, the method comprising: the IBCF receives a message which is from a calling user and is further 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 comprises a fallback identifier; the IBCF obtains the domain name of the home domain of the called user from an ENUM server through NAPTR query; the IBCF obtains a host name of a short message center of a called user side corresponding to a domain name of a home domain of the called user from a DNS through SRV inquiry, wherein the short message center of the called user side is positioned in a domain different from the home domain of the called user; and the IBCF routes the message to the short message center of the called user side according to the host name of the short message center of the called user side, so that the message is sent to the called user.
According to yet another aspect of the present disclosure, a system for messaging between 5G messaging users/VoLTE users in a mobile communication network is presented, the system comprising means configured to perform a method for messaging between 5G messaging users/VoLTE users in a mobile communication network according to the present disclosure.
According to yet another aspect of the present disclosure, a computer-readable storage medium is presented, which stores a program that, when executed by a processor, implements a method for messaging between 5G messaging users/VoLTE users in a mobile communication network according to the present disclosure.
The foregoing has outlined rather broadly the present disclosure in order to provide a basic understanding of some aspects of the disclosure. However, it should be understood that this summary is not an exhaustive overview of the disclosure. It is not intended to identify key or critical elements of the disclosure or to delineate the scope of the disclosure. Its sole purpose is to present some concepts of the disclosure in a simplified form as a prelude to the more detailed description that is presented later.
Other features of the present disclosure and advantages thereof will become more apparent from the following detailed description of various embodiments of the present disclosure with reference to the accompanying drawings.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate various embodiments of the disclosure and together with the description, serve to explain the principles of the disclosure.
Fig. 1 shows a basic flow of a method for messaging between 5G message users/VoLTE users according to an embodiment of the present disclosure.
Fig. 2 shows a basic flow of another method for messaging between 5G message users/VoLTE users according to an embodiment of the present disclosure.
Fig. 3 shows a first example of messaging between 5G message users/VoLTE users according to an embodiment of the present disclosure.
Fig. 4 shows a second example of messaging between 5G message users/VoLTE users according to an embodiment of the present disclosure.
Fig. 5 shows a third example of messaging between 5G message users/VoLTE users according to an embodiment of the present disclosure.
Fig. 6 shows a fourth example of messaging between 5G message users/VoLTE users according to an embodiment of the present disclosure.
Fig. 7 shows a fifth example of messaging between 5G message users/VoLTE users according to an embodiment of the disclosure.
Fig. 8 shows a sixth example of messaging between 5G message users/VoLTE users according to an embodiment of the disclosure.
Detailed Description
Hereinafter, various embodiments of the present disclosure will be described in detail with reference to the accompanying drawings.
It should be noted that in the following detailed description, numerous specific details are set forth in order to provide a thorough understanding of the described embodiments. It will be apparent, however, to one skilled in the art, that the described embodiments may be practiced without some or all of these specific details. Additionally, in the described embodiments, some well-known matters have not been described in detail in order to avoid unnecessarily obscuring the concepts of the present disclosure, and should be considered part of the specification where appropriate.
Further, the steps of the methods presented in this disclosure are illustrative. In some embodiments, the methods may have one or more additional steps not described herein and/or omit one or more steps already described herein. Moreover, the order in which the steps of the methods are illustrated and described is not intended to be limiting.
In general, the scheme proposed by the present disclosure for message transmission between 5G message users/VoLTE users in a mobile communication network introduces an ENUM (e.164number URI Mapping) server and a dns (domain Name system) and corresponding naptr (Name Authority pointer) query and srv (session) query, which is a completely new message transmission scheme, and improves on the existing message transmission scheme. In particular, this messaging scheme solves the problem of the prior art that VoLTE users cannot send messages to 5G messaging users.
In the following, an overview of the ENUM server and DNS and the corresponding NAPTR queries and SRV queries involved in the present disclosure will be presented.
First, with respect to ENUM server and NAPTR queries: in the present disclosure, in the process of sending a message to a called user, by performing NAPTR query to an ENUM server, a domain name of a home domain of the called user can be obtained.
More specifically, in the present disclosure, two tables (hereinafter, referred to as a first table and a second table) may be stored in the ENUM server, the first table corresponding to a domain name of a home domain of a 5G message subscriber and in which a plurality of 5G message subscribers are registered, and the second table corresponding to a domain name of a home domain of a VoLTE subscriber and in which a plurality of VoLTE subscribers are registered. In other words, a plurality of 5G message users whose domain names of the home domain are the same are registered in the first table, and a plurality of VoLTE users whose domain names of the home domain are the same are registered in the second table. When NAPTR inquiry is carried out, the called user can be searched in the two tables, and when the called user is searched in the first table or the second table, the domain name of the home domain of the called user can be obtained. Further, when the called users are searched in the two tables, the priority of the search can be set. For example, the called user is first looked up in the first table, and if the called user is not found in the first table, the look-up is continued in the second table. The searching sequence 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 preferentially obtained as the domain name of the home domain of the called user.
Second, with respect to DNS and SRV queries: in the present disclosure, in the process of sending a message to a called user, after obtaining a domain name of a home domain of the called user by performing NAPTR query to an ENUM server, a host name of a message center of a called user side corresponding to the domain name of the home domain of the called user can be obtained by performing SRV query to a DNS.
More specifically, in the present disclosure, SRV queries are divided into two query types. In one query type (hereinafter referred to as a first query type), the host name of the message center of the home domain of the called user corresponding to the domain name of the home domain of the called user can be obtained, and in another query type (hereinafter referred to as a second query type), the host name of the short message center of the called user side corresponding to the domain name of the home domain of the called user can be obtained, and the short message center of the called user side is located in a domain different from the home domain of the called user. The two query types may be indicated by respective query type identifications (hereinafter referred to as a first query type identification, a second query type identification, respectively).
The ENUM servers and DNS referred to in this disclosure, and the corresponding NAPTR queries and SRV queries, have been introduced generally above. These and other general aspects of the invention will be more clearly understood from the following detailed description. Here, it should be noted that, regarding the ENUM server and DNS and the corresponding NAPTR query and SRV query, only the contents that are closely related to the present disclosure are described herein, and the contents that should be well known to those skilled in the art are not described herein.
Next, a method for message transmission between 5G message users/VoLTE users in a mobile communication network proposed by the present disclosure will be described. Fig. 1 shows a basic flow of a method for messaging between 5G message users/VoLTE users according to an embodiment of the present disclosure.
First, in step S101, the message center on the calling subscriber side receives a message from the calling subscriber and sent to the called subscriber.
When the calling user sends a message to the called user, the message is first routed to the message center of the calling user side, that is, the message center of the calling user side in step S101 receives the message. As already mentioned above, the present disclosure is directed to messaging between 5G messaging users/VoLTE users. Therefore, the calling subscriber in step S101 is a 5G message subscriber or a VoLTE subscriber, and the called subscriber is also a 5G message subscriber or a VoLTE subscriber. In addition, as one skilled in the art should appreciate, in the case that the calling user is a 5G message user, the message center of the calling user side specifically refers to a 5G message center, and in the case that the calling user is a VoLTE user, the message center of the calling user side specifically refers to a short message center. Incidentally, here, the "5G message user" mentioned herein refers to a user who has opened a 5G message service and the "VoLTE user" refers to a user who has opened a VoLTE service, which should be well known to those skilled in the art, and thus will not be described in detail herein.
Next, in step S102, the message center on the calling subscriber side obtains the domain name of the home domain of the called subscriber from the ENUM server through NAPTR query.
As already mentioned above, in the solution proposed by the present disclosure for messaging between 5G message subscribers/VoLTE subscribers an ENUM server and a corresponding NAPTR query is introduced. Step S102 embodies this. Specifically, after the message center on the calling subscriber side receives the message in step S101, the message center needs to obtain the domain name of the home domain of the called subscriber from the ENUM server through NAPTR query in step S102.
In some implementations, step S102 may be accomplished by the transmission and reception of a query request and a query response between the message center of the calling subscriber side and the ENUM server. Specifically, the message center of the calling subscriber side may send an NAPTR query request for querying a domain name of a home domain of the called subscriber to the ENUM server, and the ENUM server obtains the domain name of the home domain of the called subscriber according to the NAPTR query request and returns an NAPTR query response to the message center of the calling subscriber side, where the NAPTR query response carries the domain name of the home domain of the called subscriber.
Further, in some implementations, in step S101, the message received by the message center of the calling subscriber side may carry a number in a TEL URL format of the called subscriber, where the number in the TEL URL format of the called subscriber may be carried in a NAPTR query request sent by the message center of the calling subscriber side to the ENUM server to query a domain name of a home domain of the called subscriber, and a NAPTR query response returned by the ENUM server to the message center of the calling subscriber side may carry a number in a SIP URL format of the called subscriber, where the number in the SIP URL format of the called subscriber includes the domain name of the home domain of the called subscriber.
Further, in some implementations, as already mentioned above, the ENUM server may store therein a first table of domain names corresponding to the home domain of 5G message subscribers and a second table of domain names corresponding to the home domain of VoLTE subscribers for looking up the called subscriber to obtain the domain name of his home domain, and may set a priority order of the look-up. Therefore, the obtaining, by the ENUM server, the domain name of the home domain of the called subscriber according to the NAPTR query request may include: the ENUM server firstly 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 can obtain the corresponding domain name of the home domain under the condition that the called user is searched in the first table, wherein the domain name of the home domain of the called user is contained in the SIP URL format number of the called user; and under the condition that the called user is not found in the first table, the ENUM server continues to find the called user in the second table according to the TEL URL format number of the called user, and under the condition that the called user is found in the second table, the domain name of the corresponding home domain can be obtained, and the domain name of the home domain of the called user is contained in the SIP URL format number of the called user.
Returning now to fig. 1, after step S102 is performed, step S103 is then performed. In step S103, the message center on the calling subscriber side obtains the host name of the message center in the home domain of the called subscriber corresponding to the domain name in the home domain of the called subscriber through SRV query from the DNS.
As already mentioned above, DNS and corresponding SRV queries are also introduced in the solution proposed in the present disclosure for messaging between 5G message users/VoLTE users. Step S103 embodies this. Specifically, after the message center on the calling subscriber side obtains the domain name of the home domain of the called subscriber in step S102, in step S103, the message center needs to obtain the host name of the message center of the home domain of the called subscriber corresponding to the domain name of the home domain of the called subscriber obtained in step S102 from the DNS through SRV query. Here, as a person skilled in the art should also appreciate, in the case that the called user is a 5G message user, the message center of the home domain of the called user is specifically referred to as a 5G message center, and in the case that the called user is a VoLTE user, the message center of the home domain of the called user is specifically referred to as a short message center.
Similar to step S102, in some implementations, step S103 may be accomplished by the transmission and reception of query requests and query responses between the DNS and the message center on the calling user side. Specifically, the message center of the calling user side may send, to the DNS, an SRV query request for querying the host name of the message center of the home domain of the called user, and the DNS obtains the host name of the message center of the home domain of the called user according to the SRV query request, and returns an SRV query response to the message center of the calling user side, where the SRV query response carries the host name of the message center of the home domain of the called user.
As already 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 may be indicated by respective query type identifications. The SRV query in step S103 belongs to a first query type. In some implementations, the SRV query request in step S103 may carry a domain name of the home domain of the called user and a first query type identifier, where the first query type identifier is used to indicate that the message center on the user side needs to query the host name of the message center in the home domain of the called user.
Returning now to fig. 1 again, after step S103 is performed, step S104 is then performed. In step S104, the message center of the calling subscriber side routes the message to the message center of the home domain of the called subscriber according to the host name of the message center of the home domain of the called subscriber, so that the message is sent to the called subscriber.
Specifically, after the host name of the message center of the home domain of the called subscriber is obtained in step S103, the message center of the calling subscriber side routes the message received in step S101 to the message center of the home domain of the called subscriber according to the host name of the message center obtained in step S103 in step S104. In this way, the message can finally be sent to the called subscriber via the message center of the home domain of the called subscriber.
The above steps S101-S104 mainly relate to the procedure of receiving a message from the message center of the calling subscriber side to the message center where the message is sent to the home domain of the called subscriber.
In the case that the called subscriber is a 5G message subscriber and the called subscriber is not online, after performing step S104, the following steps may be further performed: at the moment, the 5G message center serving as the message center of the home domain of the called user obtains the host name of the short message center of the called user side corresponding to the domain name of the home domain of the called user from DNS through SRV query, wherein the short message center of the called user side is positioned in a domain different from the home domain of the called user; and the 5G message center routes the message to the short message center of the called user side according to the host name of the short message center of the called user side, so that the message is sent to the called user.
Specifically, when the message center of the home domain of the called user side receives the message to be sent to the called user, it may query whether the called user is online. In the present disclosure, in case that the called user is a 5G message user and the message center of the home domain of 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 conventional short message, which means that the message will be finally sent to the called user via the corresponding short message center instead of the 5G message center. At this time, the 5G message center obtains the host name of the short message center of the called user side from DNS through SRV query. After obtaining the host name of the short message center, the 5G message center routes the received message to the short message center according to the host name of the short message center. Thus, the message is sent to the called user via the short message center. Here, it should be noted that the above refers to "fall back" of the message, which is well known to those skilled in the art and will not be described in detail here.
Similar to step S103, in some implementations, in the case that the called user is a 5G message user and the called user is not online, the obtaining of the host name of the short message center on the called user side may be accomplished by sending and receiving a query request and a query response between the DNS and the 5G message center as the message center of the home domain of the called user. Specifically, the 5G message center may send an SRV query request for querying a host name of the short message center of the called user side to the DNS, the DNS obtains the host name of the short message center of the called user side according to the SRV query request, and returns an SRV query response to the 5G message center, where the SRV query response carries the host name of the short message center of the called user side.
As already 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 may be indicated by respective query type identifications. The SRV query for obtaining the host name of the short message center at the called subscriber side belongs to a second query type. In some implementations, the SRV query request may carry a domain name of a home domain of the called user and a second query type identifier, where the second query type identifier is used to indicate that the 5G message center needs to query the host name of the short message center at the called user side.
The method proposed by the present disclosure for messaging between 5G message users/VoLTE users has been introduced above. To understand this method more clearly, a specific example of messaging between 5G message users/VoLTE users will be given below. Fig. 3-7 show first to fifth examples of messaging between 5G message users/VoLTE users according to embodiments of the present disclosure.
First example
Next, a first example shown in fig. 3 will be described. In this example, user a (shown as "UE a" in fig. 3), which is a 5G message user, sends a message to user B (shown as "UE B" in fig. 3), which is a 5G message user, and user B is online. In addition, as will be readily appreciated from the following description, the user a, 5G message center a, user B, and 5G message center B referred to in this example correspond to the above-mentioned message centers of the home domains of the calling user, the calling user side, the called user, and the called user, respectively.
First, in step S1, user a routes a message carrying a number in the TEL URL format of user B (shown as "B-number" in fig. 3) to 5G message center a.
Next, in step S2, 5G message center a transmits, to the ENUM server, a NAPTR query request for obtaining the domain name of the home domain of user B, the NAPTR query request carrying the number of user B in TEL URL format.
Next, in step S3, the ENUM server returns a NAPTR query response to 5G message center a, which carries a SIP URL-formatted number of user B (shown as "B-number @ B home domain name" in fig. 3), where the "B home domain name" indicates the domain name of the home domain of user B.
Specifically, a first table corresponding to a domain name of a home domain of a 5G message subscriber and in which a plurality of 5G message subscribers are registered and a second table corresponding to a domain name of a home domain of a VoLTE subscriber and in which a plurality of VoLTE subscribers are registered are stored in the ENUM server, which have been mentioned in the above description. After the ENUM server receives the NAPTR query request, first, user B is looked up 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 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 TEL URL-formatted number of the user B and the obtained domain name of the home domain of the user B form a SIP URL-formatted number of the user B (i.e., "B-number @ B home domain name") are carried in a NAPTR query response to be returned to the 5G message center a.
Next, in step S4, the 5G message center a sends, to the DNS, an SRV query request for obtaining the host name of the 5G message center B, where the SRV query request carries the domain name of the home domain of the user B and the first query type identifier.
Specifically, after 5G message center a obtains the domain name of the home domain of user B from the ENUM server, it sends to the DNS an SRV query request for obtaining 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, which is indicated by the first query type identifier.
Next, in step S5, the DNS returns an SRV query response to 5G message center a, where the SRV query response carries the host name of 5G message center B.
Specifically, after receiving the SRV query request, the DNS obtains the host name of the 5G message center B according to the domain name of the home domain of the user B and the first query type identifier carried in the SRV query request. The obtained host name for 5G message center B is carried in the SRV query response for return to 5G message center a.
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 above in the description of step S1, the message carries the number of user B.
Next, in step S7, the 5G message center B inquires that the user B is online according to the number of the user B carried in the received message.
Finally, in step S8, the 5G message center B transmits a message to the user B.
Second example
Next, a second example shown in fig. 4 will be described. In this example, user a, which is a 5G messaging user, sends a message to user B, which is a VoLTE user, and user B is online. In addition, as will be readily appreciated from the following description, the user a, the 5G message center a, the user B, and the short message center B referred to in this example correspond to the above-mentioned message centers of the calling user, the calling user side, the called user, and the home domain of the called user, respectively.
First, step S1 in fig. 4 is similar to step S1 in fig. 3 and will not be described in detail here.
Next, step S2 in fig. 4 is similar to step S2 in fig. 3, and is not described in detail here.
Next, in step S3, the ENUM server returns a NAPTR query response carrying a SIP URL-formatted number of the user B (shown as "B-number @ B home domain name" in fig. 4), where the "B home domain name" indicates a domain name of the home domain of the user B, to the 5G message center a.
Specifically, as already mentioned above, a first table and a second table are stored in the ENUM server. After the ENUM server receives the NAPTR query request, first, user B is looked up in the first table according to the TEL URL format number 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, user B continues to be looked up in the second table. After user B is found in the second table, the domain name of its home domain may then be obtained. Then, the number in tel URL format of the user B and the obtained domain name of the home domain of the user B form a number in SIP URL format of the user B (i.e., "B-number @ B home domain name") are carried in the NAPTR query response to be returned to the 5G message center a.
As can be seen from the comparison of step S3 in fig. 4 and step S3 in fig. 3, since user B is a VoLTE user and a 5G message user in fig. 4 and 3, respectively, the domain name of the home domain of user B obtained in step S3 in fig. 4 is actually the domain name of the home domain of the VoLTE user, and the domain name of the home domain of user B obtained in step S3 in fig. 3 is actually the domain name of the home domain of the 5G message user.
Next, in step S4, the 5G message center a sends, to the DNS, an SRV query request for obtaining the host name of the short message center B, where the SRV query request carries the domain name of the home domain of the user B and the first query type identifier.
Specifically, after the 5G message center a obtains the domain name of the home domain of the user B from the ENUM server, it sends, to the DNS, an SRV query request for obtaining the host name (which is indicated by the first query type identifier) of the message center of the home domain of the user B (i.e., short message center B) corresponding to the domain name of the home domain of the user B.
Next, in step S5, the DNS returns an SRV query response to the 5G message center a, where the SRV query response carries the host name of the short message center B.
Specifically, after receiving the SRV query request, the DNS obtains the host name of the short message center B according to the domain name of the home domain of the user B and the first query type identifier carried in the SRV query request. The obtained host name of the short message center B is carried in an SRV inquiry response to be returned to the 5G message center A.
Finally, steps S6-S8 in FIG. 4 are similar to steps S6-S8 in FIG. 3 and are not described in detail herein.
Third example
Next, a third example shown in fig. 5 will be described. 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, as will be readily appreciated from the following description, the user a, the short message center a, the user B, and the 5G message center B referred to in this example correspond to the above-mentioned message centers of the calling user, the calling user side, the called user, and the home domain of the called user, respectively.
First, step S1 in fig. 5 is similar to step S1 in fig. 3 and will not be described in detail here.
Next, steps S2-S5 in FIG. 5 are similar to steps S2-S5 in FIG. 3 and are not described in detail herein.
Finally, steps S6-S8 in FIG. 5 are similar to steps S6-S8 in FIG. 3 and are not described in detail herein.
Here, as can be seen from a comparison between fig. 5 and fig. 3, the rest of the parts are the same except that the calling subscriber a in fig. 5 is a VoLTE subscriber (the corresponding message center on the calling subscriber side is a short message center a), and the calling subscriber a in fig. 3 is a 5G message subscriber (the corresponding message center on the calling subscriber side is a 5G message center a). Therefore, although the steps S1-S8 in fig. 5 are not described in detail above, the message transmission process in the third example in fig. 5 should be easily known to those skilled in the art based on the above description of the message transmission process in the first example in fig. 3.
Fourth example
Next, a fourth example shown in fig. 6 will be described. 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, as will be readily appreciated from the following description, the user a, the short message center a, the user B, and the short message center B referred to in this example correspond to the above-mentioned message centers of the calling user, the calling user side, the called user, and the home domain of the called user, respectively.
First, step S1 in fig. 6 is similar to step S1 in fig. 4, and is not described in detail here.
Next, steps S2-S5 in FIG. 6 are similar to steps S2-S5 in FIG. 4 and will not be described in detail herein.
Finally, steps S6-S8 in FIG. 6 are similar to steps S6-S8 in FIG. 4 and are not described in detail herein.
Here, as can be seen from a comparison between fig. 6 and fig. 4, the rest of the parts are the same except that the calling subscriber a in fig. 6 is a VoLTE subscriber (the corresponding message center on the calling subscriber side is a short message center a), and the calling subscriber a in fig. 4 is a 5G message subscriber (the corresponding message center on the calling subscriber side is a 5G message center a). Therefore, although the steps S1-S8 in fig. 6 are not described in detail above, the message transmission process in the fourth example in fig. 6 should be easily known to those skilled in the art based on the above description of the message transmission process in the second example in fig. 4.
Fifth example
Next, a fifth example shown in fig. 7 will be described. In the above first to fourth examples, the called users are all online. The fifth example mainly relates to a scenario where the called user is a 5G message user and the called user is not online. Specifically, the flow shown in fig. 7 is a flow to be continuously executed in a case where it is determined in step S7 in fig. 3 and 5 that the user B is not online. In view of this, in fig. 7, steps S1-S6 in fig. 3 and 5 are not shown, but only a flow starting from the judgment that the 5G message center B is not online. Incidentally, the flow to be executed in the case where it is determined in step S7 in fig. 4 and 6 that user B is not online is a flow in the related art, which is not a point of interest of the present disclosure and will not be described here.
First, in step S1, the 5G message center B inquires that the user B is not online according to the number of the user B carried in the received message. At this time, the message will fall back to the conventional short message, which means that it will be sent to the user B via the short message center of the user B side (i.e., the short message center B in fig. 7).
Next, in step S2, the 5G message center B sends, to the DNS, an SRV query request for obtaining the host name of the short message center B, where the SRV query request carries the domain name of the home domain of the user B and the second query type identifier.
Specifically, after the 5G message center B inquires that the user B is not online, an SRV inquiry request for obtaining a host name (which is indicated by the second inquiry type identifier) of the short message center (i.e., short message center B) on the user B side corresponding to the domain name of the home domain of the user B is sent to the DNS.
Next, in step S3, the DNS returns an SRV query response to the 5G message center B, where the SRV query response carries the host name of the short message center B.
Specifically, after receiving the SRV query request, the DNS obtains the host name of the short message center B according to the domain name of the home domain of the user B and the second query type identifier carried in the SRV query request. The obtained host name of the short message center B is carried in an SRV inquiry response to be returned to the 5G message center B.
Next, in step S4, the 5G message center B routes the message to the short message center B according to the host name of the short message center B, where the message carries the B number and the fallback identifier. Here, the fallback flag is intended to inform the short message center B that the message is a message subject to fallback.
Finally, in step S5, the short message center B sends the message to the user B.
The above is the message transmission 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.
In particular, the above description introduces the message sending process in the scenario where the called user is a 5G message user and the called user is not online. In the above message sending process, the called user is judged whether to be on line or not at the called user side. The disclosure further provides a message sending method in a scene that the called user is a 5G message user and the calling user side has judged that the called user is not online.
More specifically, the above message sending method involved in determining whether the called user is online at the called user side mainly aims at message sending between users in the same network (i.e., the calling user and the called user belong to the same mobile communication network), while the message sending method described 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 mainly aims at message sending between users in different networks (i.e., the calling user and the called user belong to different mobile communication networks). Next, this method will be described in detail with reference to fig. 2.
First, in step S201, an ibcf (interconnection Border Control function) receives a message from a calling user and further sent to a called user.
When the message transmission between the different network users is involved, the message sent by the calling user will be routed to the IBCF (i.e., the IBCF receives the message in step S201), and then routed to the called user via the IBCF. It should be noted that the network element IBCF herein should be well known to those skilled in the art and will not be described in detail herein. Here, the calling subscriber in step S201 is a 5G message subscriber or a VoLTE subscriber, and the called subscriber is a 5G message subscriber. In addition, the message in step S201 carries a fallback flag. By this identification, the IBCF can realize that the received message will fall back to the legacy sms, which means that the message will be sent to the called subscriber via the sms center on the called subscriber side, rather than via the message center of its home domain (i.e., the 5G message center). As already mentioned above, the meaning of "fallback" is well known to the person skilled in the art and will not be described in detail here.
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. Step S202 is similar to step S102 in fig. 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.
Likewise, in some implementations, step S202 may be completed by sending and receiving a query request and a query response between the IBCF and the ENUM server, specifically, the IBCF may send a NAPTR query request for querying a domain name of a home domain of a called user to the ENUM server, 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, where the NAPTR query response carries the domain name of the home domain of the called user.
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, where 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 to query a domain name of a home domain of the called user, and a NAPTR query response returned by the ENUM server to the IBCF may carry a number in a SIP URL format of the called user, where the number in the SIP URL format of the called user includes the domain name of the home domain of the called user.
Further, in some implementations, as already mentioned above, the ENUM server has stored therein a first table of domain names corresponding to the home domain of 5G message subscribers and a second table of domain names corresponding to the home domain of VoLTE subscribers for looking up the called subscriber to obtain the domain name of his home domain. Therefore, in the case where the called subscriber discussed herein is limited to a 5G message subscriber, the obtaining, by the ENUM server, the domain name of the home domain of the called subscriber according to the NAPTR query request may include: the ENUM server searches the called user in the first table according to the TEL URL format number of the called user carried in the NAPTR query request, and can obtain the corresponding domain name of the home domain of the called user under the condition that the called user is found in the first table, wherein the domain name of the home domain of the called user is contained in the SIP URL format number of the called user.
Returning now to fig. 2, after step S202 is performed, step S203 is next performed. In step S203, the IBCF obtains the host name of the short message center of the called user side corresponding to the domain name of the home domain of the called user from the DNS through SRV query, where the short message center of the called user side is located in a domain different from the home domain of the called user.
Specifically, as mentioned above, in the case that the calling user side has determined that the called user is not online, the message received by the IBCF will fall back to the conventional short message, i.e. the message will be sent to the called user via the short message center of 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 host name of the short message center of the corresponding called user side through SRV query from the DNS in step S203.
Likewise, in some implementations, the obtaining of the host name of the short message center on the called user side may be performed by sending and receiving a query request and a query response between the IBCF and the DNS. Specifically, the IBCF may send an SRV query request for querying a host name of the short message center of the called user side to the DNS, the DNS obtains the host name of the short message center of the called user side according to the SRV query request, and returns an SRV query response to the IBCF, where the SRV query response carries the host name of the short message center of the called user side.
Likewise, the SRV query for obtaining the host name of the short message center on the called subscriber side belongs to the second query type. In some implementations, the SRV query request may carry a domain name of a home domain of the called user and a second query type identifier, where the second query type identifier is used to indicate that the IBCF needs to query the host name of the short message center on the called user side.
Returning now to fig. 2 again, after step S203 is performed, step S204 is next performed. In step S204, the IBCF routes the message to the short message center of the called party side according to the host name of the short message center of the called party side, so that the message is sent to the called party.
Specifically, after the host name of the short message center of the called user side is obtained in step S203, in step S204, the IBCF routes the message received in step S201 to the short message center of the called user side according to the host name of the short message center obtained in step S203. Thus, the message can be finally sent to the called user through the short message center at the called user side.
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 not online has been introduced above. Also, in order to more clearly understand this method, specific examples thereof will be given below. Fig. 8 shows a sixth example of messaging between 5G message users/VoLTE users according to an embodiment of the disclosure.
Next, a sixth example shown in fig. 8 will be described. In this example, user a, which is a 5G messaging user or VoLTE user, sends a message to user B, which is a 5G messaging user, and user B is not online.
First, in step S1, the IBCF receives a message from user a, which carries a TEL URL format number (shown as "B-number" in fig. 8) and a fallback identity for user B.
Next, in step S2, the IBCF transmits to the ENUM server a NAPTR query request for obtaining the domain name of the home domain of the user B, the NAPTR query request carrying a number in TEL URL format of the user B.
Next, in step S3, the ENUM server returns a NAPTR query response to the IBCF, the NAPTR query response carrying a SIP URL-formatted number of the user B (shown as "B-number @ B home domain name" in fig. 8), where the "B home domain name" indicates a domain name of the home domain of the user B.
Specifically, a first table corresponding to a domain name of a home domain of a 5G message subscriber and in which a plurality of 5G message subscribers are registered and a second table corresponding to a domain name of a home domain of a VoLTE subscriber and in which a plurality of VoLTE subscribers are registered are stored in the ENUM server, which have been mentioned in the above description. After the ENUM server receives the NAPTR query request, the user B is searched in the first table according to the number in the TEL URL format of the user B carried in the NAPTR query request, and then the domain name of its home domain is obtained. Next, the TEL URL formatted number of the user B and the obtained domain name of the home domain of the user B form a SIP URL formatted number of the user B (i.e., "B-number @ B home domain name") which is carried in a NAPTR query response to be returned to the IBCF.
Next, in step S4, the IBCF sends, to the DNS, an SRV query request for obtaining the host name of the short message center B, where the SRV query request carries the domain name of the home domain of the user B and the second query type identifier.
Specifically, in the case that the user B is not online, the IBCF sends, to the DNS, an SRV query request for obtaining a host name (which is indicated by the second query type identifier) of the short message center (i.e., the short message center B) on the user B side corresponding to the domain name of the home domain of the user B.
Next, in step S5, the DNS returns an SRV query response to the IBCF, where the SRV query response carries the host name of short message center B.
Specifically, after receiving the SRV query request, the DNS obtains the host name of the short message center B according to the domain name of the home domain of the user B and the second query type identifier carried in the SRV query request. The obtained host name of the short message center B is carried in the SRV query response to be returned to the IBCF.
Next, in step S6, the IBCF routes a message to the short message center B according to the host name of the short message center B, where the message carries the B number and the fallback identifier. Here, the fallback flag is intended to inform the short message center B that the message is a message subject to fallback.
Finally, in step S7, the short message center B sends the message to the user B.
The above is a message sending process between 5G message users and VoLTE users, specifically, a calling user is a 5G message user or VoLTE user, a called user is a 5G message user, and the calling user side has determined that the called user is not online.
So far, the message transmission method between 5G message users/VoLTE users proposed by the present disclosure has been fully described above. As already mentioned above, the messaging method proposed by the present disclosure introduces an ENUM and DNS query mechanism, which is a completely new messaging method that improves on existing messaging methods. For example, the message sending method of the present disclosure does not require the 5G message center on the calling subscriber side to convert the 5G message into a conventional short message to send to the called subscriber in some cases, as in the prior art. In particular, the message sending method of the present disclosure well solves the problem in the prior art that VoLTE users cannot send messages to 5G message users.
The present disclosure may also be implemented by a communication system. In particular, the present disclosure also proposes a system for messaging between 5G messaging users/VoLTE users, comprising means configured to perform the previously described method for messaging between 5G messaging users/VoLTE users. The methods proposed by the present disclosure for message transmission between 5G message users/VoLTE users have been described in detail above, and those skilled in the art should readily appreciate that these methods can be implemented by corresponding means. In view of this, these means and the functions performed by them will not be described in detail herein.
The present disclosure may also be implemented by a computer program. For example, the program may be stored in a memory of a computer apparatus, which when executed by a processor of the computer apparatus implements the method for encoding of capabilities of a CPE and the method for decoding of capabilities of a CPE of the present disclosure. Alternatively, the program may be stored in a computer readable storage medium, which when executed by a processor implements a method for encoding of capabilities of a CPE and a method for decoding of capabilities of a CPE.
A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of the computer-readable storage medium may include: a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of apparatus, methods and the like according to various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of instructions, which comprises one or more executable instructions for implementing the specified logical function(s). In some alternative implementations, the processes noted in the blocks may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. The order of operations may be adjusted as desired by those skilled in the art. Those skilled in the art may also add more operations or omit some of them as desired.
Any feature described in this specification may, unless stated otherwise, be replaced by alternative features serving the same, equivalent or similar purpose. That is, unless expressly stated otherwise, each feature is only an example of a generic series of equivalent or similar features.
Moreover, although the description of the present disclosure has included description of one or more embodiments, configurations, or aspects, other variations, modifications, and combinations are also within the scope of the present disclosure. The disclosure is intended to obtain rights which include alternative embodiments, configurations, or aspects to the extent permitted, and which include interchangeable, alternative, and/or equivalent structures, functions, or steps to those claimed, whether or not such interchangeable, alternative, and/or equivalent structures, functions, or steps are specifically described in this specification.

Claims (19)

1. A method for messaging between 5G messaging users/VoLTE users in a mobile communication network, the method comprising:
a message center of a calling party side receives a message which comes from a calling party and is to be sent to a called party, wherein the calling party is a 5G message user or a VoLTE user, the called party is the 5G message user or the VoLTE user, the message center of the calling party side is the 5G message center under the condition that the calling party is the 5G message user, and the message center of the calling party side is a short message center under the condition that the calling party is the VoLTE user;
the message center of the calling subscriber side obtains the domain name of the home domain of the called subscriber from an ENUM server through NAPTR query;
the message center of the calling user side obtains a host name of the message center of the home domain of the called user corresponding to the domain name of the home domain of the called user from a DNS through SRV inquiry, wherein the message center of the home domain of the called user is a 5G message center under the condition that the called user is a 5G message user, and the message center of the home domain of the called user is a short message center under the condition that the called user is a VoLTE user; and
and the message center of the calling user side routes the message to the message center of the home domain of the called user according to the host name of the message center of the home domain of the called user, so that the message is sent to the called user.
2. The method of claim 1, wherein the obtaining, by the message center of the calling subscriber side from an ENUM server through NAPTR query, the domain name of the home domain of the called subscriber comprises:
the message center of the calling subscriber side sends a first NAPTR query request for querying a domain name of a home domain of the called subscriber to the ENUM server; and
and the ENUM server acquires 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 of the calling user side, wherein the domain name of the home domain of the called user is carried in the first NAPTR query response.
3. The method according to claim 2, wherein the message received by the message center of the calling subscriber side carries a TEL URL formatted number of the called subscriber, the TEL URL formatted number of the called subscriber is carried in the first NAPTR query request for querying a domain name of the home domain of the called subscriber, the first NAPTR query response carries a SIP URL formatted number of the called subscriber, and the domain name of the home domain of the called subscriber is included in the SIP URL formatted number of the called subscriber.
4. The method of claim 3, wherein a first table corresponding to a domain name of a home domain of 5G message subscribers and registered with a plurality of 5G message subscribers and a second table corresponding to a domain name of a home domain of VoLTE subscribers and registered with a plurality of VoLTE subscribers are stored in the ENUM server, and the obtaining of the domain name of the home domain of the called subscriber by the ENUM server according to the first NAPTR query request comprises:
the ENUM server searches the called user in the first table according to the TEL URL format number of the called user carried in the first NAPTR query request, and obtains the domain name of the corresponding home domain to be contained in the SIP URL format number of the called user under the condition that the called user is found in the first table; and
and when the called user is not found in the first table, the ENUM server searches the called user in the second table according to the number in the TEL URL format 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 number in the SIP URL format of the called user.
5. The method according to any of claims 1-4, wherein the obtaining, by the message center of the calling user side from the DNS through an SRV query, the hostname of the message center of the home domain of the called user comprises:
the message center of the calling user side sends a first SRV query request for querying a host name of the message center of the home domain of the called user to the DNS; and
and the DNS obtains the host name of the message center of the home domain of the called user according to the first SRV query request, and returns a first SRV query response to the message center of the calling user side, wherein the first SRV query response carries the host name of the message center of the home domain of the called user.
6. The method according to claim 5, wherein the first SRV query request carries a domain name of the home domain of the called user and a 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 a host name of the message center of the home domain of the called user.
7. The method of claim 6, in the case that the called user is a 5G messaging user and the called user is not online, further comprising:
the 5G message center serving as the message center of the home domain of the called user obtains the host name of the short message center of the called user side corresponding to the domain name of the home domain of the called user from DNS through SRV query, wherein the short message center of the called user side is positioned in a domain different from the home domain of the called user; and
and the 5G message center routes the message to the short message center of the called user side according to the host name of the short message center of the called user side, so that the message is sent to the called user.
8. The method of claim 7, wherein the 5G message center obtaining the host name of the short message center of the called user side from the DNS through SRV query comprises:
the 5G message center sends a second SRV query request for querying the host name of the short message center of the called user side to the DNS; and
and the DNS acquires the host name of the short message center of the called user side according to the second SRV query request, and returns a second SRV query response to the 5G message center, wherein the host name of the short message center of the called user side is carried in the second SRV query response.
9. The method according to claim 8, wherein the second SRV query request carries a domain name of the home domain of the called user 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 short message center of the called user side.
10. A method for messaging between 5G messaging users/VoLTE users in a mobile communication network, the method comprising:
the IBCF receives a message which is from a calling user and is 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 comprises a fallback identifier;
the IBCF obtains the domain name of the home domain of the called user from an ENUM server through NAPTR query;
the IBCF obtains a host name of a short message center of a called user side corresponding to a domain name of a home domain of the called user from a DNS through SRV inquiry, wherein the short message center of the called user side is positioned in a domain different from the home domain of the called user; and
and the IBCF routes the message to the short message center of the called user side according to the host name of the short message center of the called user side, so that the message is sent to the called user.
11. The method of claim 10, wherein the IBCF obtaining the domain name of the called user's home domain from an ENUM server through NAPTR queries comprises:
the IBCF sends NAPTR query request for querying the domain name of the home domain of the called user to the ENUM server; and
and the ENUM server acquires 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.
12. The method of claim 11, wherein the message received by the IBCF carries a TEL URL formatted number of the called user in the message, the TEL URL formatted number of the called user being carried in the NAPTR query request for querying a domain name of the home domain of the called user, the NAPTR query response carrying a SIP URL formatted number of the called user, the domain name of the home domain of the called user being included in the SIP URL formatted number of the called user.
13. The method of claim 12, wherein a first table corresponding to a domain name of a home domain of a 5G message subscriber and in which a plurality of 5G message subscribers are registered and a second table corresponding to a domain name of a home domain of a VoLTE subscriber and in which a plurality of VoLTE subscribers are registered are stored in the ENUM server, and the obtaining, by the ENUM server, the domain name of the home domain of the called subscriber according to the NAPTR query request comprises:
the ENUM server searches the called user in the first table 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 contained in the SIP URL format number of the called user under the condition that the called user is found in the first table.
14. The method of any one of claims 10-13, wherein the IBCF obtaining the hostname of the short message center of the called user side from DNS through SRV query comprises:
the IBCF sends an SRV query request for querying the host name of the short message center of the called user side to the DNS; and
and the DNS acquires the host name of the short message center of 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 short message center of the called user side.
15. The method according to claim 14, wherein the SRV query request carries a domain name of a 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 a host name of a short message center of the called user side.
16. A system for messaging between 5G messaging users/VoLTE users in a mobile communication network, the system comprising means configured to perform the method according to any one of claims 1-9.
17. A system for messaging between 5G messaging users/VoLTE users in a mobile communication network, the system comprising means configured to perform the method according to any one of claims 10-15.
18. A computer-readable storage medium storing a program which, when executed by a processor, implements an apparatus of the method of any one of claims 1-9.
19. A computer-readable storage medium storing a program which, when executed by a processor, implements an apparatus of the method of any one of claims 10-15.
CN202011175435.1A 2020-10-28 2020-10-28 Method, system, and storage medium for messaging between 5G messaging users/VoLTE users Pending CN114422964A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202011175435.1A CN114422964A (en) 2020-10-28 2020-10-28 Method, system, and storage medium for messaging between 5G messaging users/VoLTE users

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202011175435.1A CN114422964A (en) 2020-10-28 2020-10-28 Method, system, and storage medium for messaging between 5G messaging users/VoLTE users

Publications (1)

Publication Number Publication Date
CN114422964A true CN114422964A (en) 2022-04-29

Family

ID=81260223

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202011175435.1A Pending CN114422964A (en) 2020-10-28 2020-10-28 Method, system, and storage medium for messaging between 5G messaging users/VoLTE users

Country Status (1)

Country Link
CN (1) CN114422964A (en)

Citations (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20070243876A1 (en) * 2005-04-29 2007-10-18 Huawei Technologies Co., Ltd. Method and System for Implementing a Message Service Based on IP Multimedia Subsystem
CN101420657A (en) * 2007-10-22 2009-04-29 华为技术有限公司 Method for message transmission between heterogeneous networks and apparatus thereof
CN101699813A (en) * 2009-11-16 2010-04-28 中兴通讯股份有限公司 Domain name processing method and domain name server
CN102474469A (en) * 2009-06-30 2012-05-23 阿尔卡特朗讯 A method and system for interworking between instant messaging service and short message service
EP3094059A1 (en) * 2015-05-15 2016-11-16 Vodafone GmbH Routing voice over lte call invites in a terminating ims
US20170339740A1 (en) * 2016-05-19 2017-11-23 United States Cellular Corporation Media resource reservation request failure handling for voice over mobile wireless network
US20180124124A1 (en) * 2016-11-02 2018-05-03 T-Mobile Usa, Inc. Network routing based on terminal's media path
CN108712516A (en) * 2018-05-21 2018-10-26 平安科技（深圳）有限公司 Obtain method, apparatus, equipment and the storage medium of sip server address
CN109873795A (en) * 2017-12-05 2019-06-11 中国电信股份有限公司 Gateway exchange call connection method, gateway exchange and computer readable storage medium
CN109936827A (en) * 2017-12-19 2019-06-25 中国电信股份有限公司 Short message method for routing and system, caller sms center and domain name system
CN110677844A (en) * 2018-07-03 2020-01-10 中国电信股份有限公司 Calling method, information interaction method, communication equipment and interaction platform
CN111245967A (en) * 2018-11-28 2020-06-05 中国电信股份有限公司 DNS query method, DNS server and domain name resolution system
US20200314702A1 (en) * 2019-04-01 2020-10-01 T-Mobile Usa, Inc. Communication fallback in 5g systems and methods
CN115150451A (en) * 2021-03-15 2022-10-04 中国电信股份有限公司 Method and device for internetworking, computer readable medium and electronic equipment

Patent Citations (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20070243876A1 (en) * 2005-04-29 2007-10-18 Huawei Technologies Co., Ltd. Method and System for Implementing a Message Service Based on IP Multimedia Subsystem
CN101420657A (en) * 2007-10-22 2009-04-29 华为技术有限公司 Method for message transmission between heterogeneous networks and apparatus thereof
CN102474469A (en) * 2009-06-30 2012-05-23 阿尔卡特朗讯 A method and system for interworking between instant messaging service and short message service
CN101699813A (en) * 2009-11-16 2010-04-28 中兴通讯股份有限公司 Domain name processing method and domain name server
EP3094059A1 (en) * 2015-05-15 2016-11-16 Vodafone GmbH Routing voice over lte call invites in a terminating ims
US20170339740A1 (en) * 2016-05-19 2017-11-23 United States Cellular Corporation Media resource reservation request failure handling for voice over mobile wireless network
US20180124124A1 (en) * 2016-11-02 2018-05-03 T-Mobile Usa, Inc. Network routing based on terminal's media path
CN109873795A (en) * 2017-12-05 2019-06-11 中国电信股份有限公司 Gateway exchange call connection method, gateway exchange and computer readable storage medium
CN109936827A (en) * 2017-12-19 2019-06-25 中国电信股份有限公司 Short message method for routing and system, caller sms center and domain name system
CN108712516A (en) * 2018-05-21 2018-10-26 平安科技（深圳）有限公司 Obtain method, apparatus, equipment and the storage medium of sip server address
CN110677844A (en) * 2018-07-03 2020-01-10 中国电信股份有限公司 Calling method, information interaction method, communication equipment and interaction platform
CN111245967A (en) * 2018-11-28 2020-06-05 中国电信股份有限公司 DNS query method, DNS server and domain name resolution system
US20200314702A1 (en) * 2019-04-01 2020-10-01 T-Mobile Usa, Inc. Communication fallback in 5g systems and methods
CN115150451A (en) * 2021-03-15 2022-10-04 中国电信股份有限公司 Method and device for internetworking, computer readable medium and electronic equipment

Similar Documents

Publication Publication Date Title
US20210329442A1 (en) Mobile Gateway
EP1839421B1 (en) A method and apparatus for handling emergency calls in a packet switched radio access network
US7260207B2 (en) Methods, systems, and computer program products for providing presence-qualified E.164 number mapping (ENUM) service in a communications network
US7996541B2 (en) Methods, systems, and computer program products for identifying a serving home subscriber server (HSS) in a communications network
US7948967B2 (en) Methods, systems, and computer program products for enabling non-IMS queries of a common telephone number mapping system
US8165063B2 (en) System and method for performing location management using home subscriber server in VoIP service
US8571015B2 (en) Methods, systems, and computer program products for enabling non-IMS queries of a common telephone number mapping system
US20100157977A1 (en) Methods, systems, and computer program products for providing intra-carrier ip-based connections using a common telephone number mapping architecture
CN101828376A (en) Shared dns domain handling
WO2011057526A1 (en) Domain name processing method and domain name server
CN101043526B (en) Method, apparatus and system for processing message in IMS network
CN104168289A (en) User data query method and device based on IMS network
US8547965B2 (en) Methods, apparatus and articles of manufacture to provide uniform resource identifier portability
CN107645568B (en) Method, device and system for realizing remote network access of IMS (IP multimedia subsystem) network
CN114422964A (en) Method, system, and storage medium for messaging between 5G messaging users/VoLTE users
EP3094059B1 (en) Routing voice over lte call invites in a terminating ims
CN112752260B (en) Equipment and method for number-carrying network-transfer transmitting end inquiry
US20110211684A1 (en) Method, device and system for judging call type
US10277421B2 (en) Route lookup resolution
EP3337118B1 (en) Method for an enhanced control function selection in a communication network, communication network, home subscriber server, program and computer program product
WO2019011442A1 (en) Transit layer computer system and method for providing telecommunication services with local user experience
EP1271987A2 (en) A name server for positioning objects
KR20150081380A (en) Calling Information Display Supporting System, Server and Method

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination