Downlink message passing domain selection execution system and method and medium

Abstract

The invention provides a downlink message passing domain selection execution system, a downlink message passing domain selection execution method and a medium. The HSS module registers the first mobile management entity information to the UDM module when the mobile terminal completes the attachment registration of the first network domain, thereby breaking through the limitation of a 3GPP TS 29503 protocol, and enabling the UDM module to store two types of mobile management entity information of a 4G core network and a second network domain at the same time. And when the UDM module responds to the routing information acquisition request, the two types of information are sent to the IP message gateway together, so that the defects of the 3GPP TS 29577 protocol are made up, and complete multi-domain position data are obtained. And the IP message gateway flexibly selects the target transmission domain according to the target transmission domain, thereby avoiding a single transmission path and switching to another network domain when one network domain fails in transmission, ensuring the comprehensiveness and reliability of downlink short message transmission, and solving the problem of insufficient transmission integrity in the past.

Description

Technical Field

[0001] This application relates to the field of transmission domain selection technology, and in particular to a downlink message transmission domain selection execution system, method and medium. Background Technology

[0002] In short message delivery scenarios, after receiving an uplink short message from an MO (Mobile Originated, the mobile terminal initiating the short message), the SMS center needs to forward the message to an MT (Mobile Terminated, the called mobile terminal receiving the short message). During message forwarding, the SMS center needs to obtain the MT's location information and perform network domain selection through an IP-SM-GW (IP-Short-Message-Gateway). In the existing process, the SMS center can query the MT's location through either an HSS (Home Subscriber Server) or a UDM (Unified Data Management) network element. However, in the current processing flow, when the SMS center looks up the routing information of the MT through the UDM and the IP-SM-GW transmits the downlink SMS, due to the limitation of the 3GPP TS 29503 protocol, the HSS cannot register the MME (Mobility Management Entity) information of the 4G core network where the MT is located to the UDM; and the service interface of the IP-SM-GW specified by the 3GPP TS29577 protocol causes the UDM to be unable to send the 4G core network location information to the IP-SM-GW, which ultimately makes it impossible for the IP-SM-GW to perform the domain selection of the 4G core network, affecting the integrity of the downlink SMS transmission. Summary of the Invention

[0003] To address the aforementioned issues and improve the integrity of downlink short message transmission, this application provides a downlink message transmission domain selection execution system, method, and medium.

[0004] The embodiments of this application disclose the following technical solutions: In a first aspect, embodiments of this application provide a downlink message passing domain selection execution system, including: an HSS module, a text messaging center, a UDM module, and an IP message gateway; The HSS module is used to register the first mobility management entity information of the mobile terminal in the first network domain to the UDM module when the mobile terminal completes the attachment registration of the network domain; the first network domain is the registration mode network domain of the HSS module. The SMS center is used to determine the corresponding called mobile terminal when it receives a message transmission request from a mobile terminal, and send a routing information acquisition request for the called mobile terminal to the UDM module. The UDM module is used to respond to the routing information acquisition request and send the first mobility management entity information and the second mobility management entity information of the called mobile terminal to the IP message gateway; the second mobility management entity information is uploaded to the UDM module by the network element in the second network domain when the called mobile terminal completes the attachment registration in the second network domain. The IP message gateway is configured to perform a delivery domain selection task based on the first mobility management entity information and the second mobility management entity information to obtain a target delivery domain, and then transmit a target downlink message to the called mobile terminal through the target delivery domain.

[0005] In one possible implementation, the first network domain includes a first message service network element, and the second network domain includes a second message service element; the IP message gateway includes a domain selection execution module, which is specifically used for: Based on the second mobility management entity information, the target downlink message is sent to the second message service network element, and the message transmission result is received from the second message service network element. If the message transmission result is successful, the second network domain is determined as the target transmission domain, and the target downlink message is transmitted to the called mobile terminal through the second message service network element; If the message transmission result is a transmission failure, the first network domain is determined as the target transmission domain, and the target downlink message is transmitted to the called mobile terminal through the first message service network element.

[0006] In one possible implementation, the IP message gateway includes: an information feedback module, which is specifically used for: In response to the first mobility management entity information and the second mobility management entity information transmitted from the UDM module, routing information for the called mobile terminal is generated; The routing information of the called mobile terminal and the identity information of its own gateway are fed back to the UDM module, so that the UDM module feeds back the routing information and the identity information to the SMS center.

[0007] In one possible implementation, the UDM module includes: an information sending unit, which is specifically used for: The first mobility management entity information and the second mobility management entity information are sent to the IP message gateway via a preset information transmission URL; The preset information transmission URL includes the Uniform Resource Identifier root path, IP Message Gateway-Message Service, version identifier, target downlink information, and general public user identifier.

[0008] In one possible implementation, the HSS module includes: an information registration unit, which is specifically used for: Based on a preset unified resource identifier, the first mobility management entity information is registered to the UDM module via the PUT method; the preset unified resource identifier includes the unified resource identifier root path, unified data management-user equipment context management, resource interface version identifier, the identifier of the mobile terminal, registration information, and mobility management entity.

[0009] In one possible implementation, the mobility management entity information includes at least one of a mobility management entity address, a mobility management entity IPv4 address, a mobility management entity IPv6 address, and a mobility management entity fully qualified domain name.

[0010] In one possible implementation, the first network domain is a 4G core network, and the first message service element is an MME element; the second network domain is a 5G core network, and the second message service element is an SMSF element.

[0011] Secondly, embodiments of this application provide a downlink message passing domain selection execution method, applied to a domain selection execution system, the domain selection execution system including an HSS module, a short message center, a UDM module, and an IP message gateway; the method includes: When a mobile terminal completes its attachment registration to a network domain, the HSS module registers the mobile terminal's first mobility management entity information within the first network domain to the UDM module; the first network domain is the registration mode network domain of the HSS module. When a message transmission request is received from a mobile terminal through the SMS center, the corresponding called mobile terminal is determined, and a routing information acquisition request for the called mobile terminal is sent to the UDM module. The UDM module responds to the routing information acquisition request by sending the first mobility management entity information and the second mobility management entity information of the called mobile terminal to the IP message gateway; the second mobility management entity information is uploaded to the UDM module by the network element in the second network domain when the called mobile terminal completes the attachment registration in the second network domain. The IP message gateway performs a delivery domain selection task based on the first mobility management entity information and the second mobility management entity information to obtain the target delivery domain, and then transmits the target downlink message to the called mobile terminal through the target delivery domain.

[0012] In one possible implementation, the first network domain includes a first message service network element, and the second network domain includes a second message service network element; The step of performing a transport domain selection task through the IP message gateway based on the first mobility management entity information and the second mobility management entity information to obtain a target transport domain, and then transmitting a target downlink message to the called mobile terminal through the target transport domain, includes: Based on the second mobility management entity information, the target downlink message is sent to the second message service network element, and the message transmission result is received from the second message service network element. If the message transmission result is successful, the second network domain is determined as the target transmission domain, and the target downlink message is transmitted to the called mobile terminal through the second message service network element; If the message transmission result is a transmission failure, the first network domain is determined as the target transmission domain, and the target downlink message is transmitted to the called mobile terminal through the first message service network element.

[0013] Thirdly, embodiments of this application provide a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements any possible downlink message passing domain selection execution method in the first aspect.

[0014] Compared to existing technologies, this application offers the following advantages: This application provides a downlink message passing domain selection execution system, method, and medium. In this method, when a mobile terminal completes its first domain attachment registration, the HSS module registers the corresponding first Mobility Management Entity (MME) information with the UDM module. This overcomes the limitation of the 3GPP TS 29503 protocol on the HSS registering 4G core network MME information with the UDM, enabling the UDM module to simultaneously store the called mobile terminal's first MME information in the 4G core network and its second MME information in the second domain. When the UDM module responds to a routing information acquisition request, it sends both types of MME information to the IP message gateway, compensating for the deficiency under the 3GPP TS 29577 protocol that the UDM cannot transmit 4G core network location information to the IP-SM-GW, allowing the IP message gateway to obtain complete multi-domain location data. Based on this, the IP message gateway performs the transmission domain selection task according to two types of entity information, and can flexibly select the target transmission domain from the first network domain and the second network domain. This avoids the problem of a single transmission path caused by the inability to perform 4G core network domain selection in the past. Even if the transmission in one network domain fails, the downlink message transmission can still be completed through another network domain, ensuring the comprehensiveness and reliability of downlink short message transmission and solving the problem of insufficient integrity of downlink short message transmission in previous technologies. Attached Figure Description

[0015] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0016] Figure 1 This application provides a schematic diagram of the structure of a downlink message passing domain selection execution system according to an embodiment of the present application. Figure 2 A flowchart illustrating a domain selection execution method provided in an embodiment of this application; Figure 3 This application provides an example of an interactive signaling diagram illustrating a domain selection execution process. Figure 4 This application provides a schematic diagram of signaling interaction during the routing information flow process. Figure 5 This is a flowchart illustrating a downlink message passing domain selection execution method provided in an embodiment of this application. Detailed Implementation

[0017] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with specific embodiments and accompanying drawings. It should be particularly noted that the embodiments described in this application are only a part of the embodiments of this application, and not all of them. All other embodiments obtained by those skilled in the art based on the embodiments of this application without creative effort are within the scope of protection of this application.

[0018] It should be noted that, unless otherwise defined, the technical or scientific terms used in the embodiments of this application should have the ordinary meaning understood by one of ordinary skill in the art to which this application pertains. The terms "first," "second," and similar terms used in the embodiments of this application do not indicate any order, quantity, or importance, but are merely used to distinguish different components. Terms such as "comprising" or "including" mean that the element or object preceding the word encompasses the elements or objects listed after the word and their equivalents, without excluding other elements or objects. Terms such as "connected" or "linked" are not limited to physical or mechanical connections, but can include electrical connections, whether direct or indirect. Terms such as "upper," "lower," "left," and "right" are only used to indicate relative positional relationships; when the absolute position of the described object changes, the relative positional relationship may also change accordingly.

[0019] As described above, in the current processing flow, when the SMS center looks up the routing information of the MT through the UDM and the IP-SM-GW transmits the downlink short message, due to the limitation of the 3GPP TS 29503 protocol, the HSS cannot register the MME information of the 4G core network where the MT is located to the UDM; and the service interface of the IP-SM-GW specified by the 3GPP TS 29577 protocol prevents the UDM from sending the location information of the 4G core network to the IP-SM-GW, ultimately making it impossible for the IP-SM-GW to perform the domain selection of the 4G core network, affecting the integrity of the downlink short message transmission.

[0020] Based on this, embodiments of this application provide a downlink message passing domain selection execution system, method, and medium. In this method, when the mobile terminal completes the first domain attachment registration, the HSS module registers the corresponding first mobility management entity information to the UDM module. This overcomes the limitation of the 3GPP TS 29503 protocol on the HSS registering 4G core network MME information to the UDM, enabling the UDM module to simultaneously store the called mobile terminal's first mobility management entity information in the 4G core network and the second mobility management entity information in the second domain. When the UDM module responds to a routing information acquisition request, it sends both types of mobility management entity information to the IP message gateway, compensating for the deficiency under the 3GPP TS 29577 protocol that the UDM cannot transmit 4G core network location information to the IP-SM-GW, allowing the IP message gateway to obtain complete multi-domain location data. Based on this, the IP message gateway performs the transmission domain selection task according to two types of entity information, and can flexibly select the target transmission domain from the first network domain and the second network domain. This avoids the problem of a single transmission path caused by the inability to perform 4G core network domain selection in the past. Even if the transmission in one network domain fails, the downlink message transmission can still be completed through another network domain, ensuring the comprehensiveness and reliability of downlink short message transmission and solving the problem of insufficient integrity of downlink short message transmission in previous technologies.

[0021] To enable those skilled in the art to better understand the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present application, and not all embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of the present application.

[0022] See Figure 1 The figure is a schematic diagram of the structure of a downlink message passing domain selection execution system provided in an embodiment of this application, which specifically includes the following modules: The HSS module 100 is used to register the first mobility management entity information of the mobile terminal in the first network domain to the UDM module when the mobile terminal completes the attachment registration of the network domain; the first network domain is the registration mode network domain of the HSS module.

[0023] In this embodiment, the HSS module, as the core network element responsible for managing user subscription information and location information in the communication network, operates primarily around the domain attachment registration scenario of mobile terminals. When a mobile terminal initiates a network access request and completes domain attachment registration, it signifies that the terminal has successfully established a connection with the target network, completed identity authentication and location registration. At this time, the HSS module synchronously captures the terminal's key network entity association information within the corresponding domain, namely the First Mobility Management Entity (MME). The MME is the core node for the terminal's mobility management, session establishment, and maintenance within the domain. Its information includes key data such as the specific location identifier of the terminal accessing the network and communication link parameters. This data is the foundation for accurate downlink message transmission. When the mobile terminal completes domain attachment registration, the HSS module proactively registers this MME information to the UDM module through a standardized interface and data format. This breaks the limitation of traditional solutions where the HSS cannot synchronize specific domain MME information to the UDM, ensuring that the UDM module can centrally store the terminal's core routing data in the corresponding domain, providing data support for cross-domain message transmission.

[0024] The first network domain is the registration mode network domain of the HSS module. In the current common 4G / 5G core network collaborative communication environment, the registration mode network domain of the HSS module usually corresponds to its natively supported core network domain (such as the 4G core network). Within this network domain, the HSS module has mature user context management capabilities and can reliably capture the attachment status of the mobile terminal and the association information of the mobility management entity. Using this network domain as the first network domain ensures the accuracy and real-time performance of the HSS module in obtaining the first mobility management entity information, while complying with the network protocol's definition of the HSS functional boundaries and avoiding potential compatibility issues arising from cross-network domain data collection.

[0025] On the other hand, mobility management entity information includes at least one of the following: mobility management entity address, mobility management entity IPv4 address, mobility management entity IPv6 address, and fully qualified domain name (WQD). These parameters provide support for communication and positioning between network elements from different dimensions. The mobility management entity address adopts the E164 international standard numbering format, adapting to network scenarios that support the MAP protocol and ensuring address compatibility across protocol architectures. The IPv4 and IPv6 addresses correspond to different network layer protocol environments, flexibly providing address identification based on the IP protocol version deployed by the network element, ensuring network layer adaptability of data transmission. The WQD uses a domain name resolution mechanism to achieve logical positioning of the mobility management entity, adapting to the domain name-based resource access requirements in the core network service architecture.

[0026] Specifically, the process by which the HSS module registers the first mobility management entity information with the UDM module is mainly achieved through the information registration unit configured within the HSS module. The information registration unit performs the following steps to complete the information registration: Step 1: Based on a preset Uniform Resource Identifier (URI), register the first Mobility Management Entity (MMI) information to the UDM module via the PUT method; the preset URI includes the URI root path, Uniform Data Management - User Equipment Context Management, Resource Interface Version Identifier, the identifier of the mobile terminal, registration information, and Mobility Management Entity.

[0027] In this embodiment, the operation logic of the information registration unit revolves around a preset unified resource identifier and a standardized data transmission method. This unit explicitly uses the PUT method to perform the registration operation. As a standardized method for resource creation or updating in network communication, the PUT method ensures that the first mobility management entity information is accurately stored or updated in the UDM module. When the relevant registration information corresponding to the mobile terminal does not exist in the UDM module, the PUT request will directly create a new resource record; if historical information already exists, it will be overwritten and updated based on the newly transmitted data, avoiding information redundancy or inconsistency issues and providing a data foundation for subsequent routing information queries.

[0028] On the other hand, the pre-defined Uniform Resource Identifier (URI) covers key components such as the URI root path, unified data management - user device context management, resource interface version identifier, mobile terminal identifier, registration information, and mobile management entity. Its specific URL definition is as follows: {apiRoot} / nudm-uecm / v1 / {ueId} / registrations / mme; This embodiment follows the resource definition specifications of service interfaces in the 3GPP protocol for the design of the preset Uniform Resource Identifier (URI). Specifically, the URI root path provides the basic access entry point for registration requests, the Unified Data Management - User Equipment Context Management (UDM) clarifies the core service domain to which the data belongs, the resource interface version identifier ensures compatibility between different network element versions, the mobile terminal identifier enables precise binding of registration information to specific terminals, and the explicit labeling of registration information with the Mobility Management Entity (MME) directly points to the target data resource. Through the structured preset URI, the information registration unit can accurately locate the target resource node in the UDM module used to store the first MME information, ensuring rapid processing of registration requests. This addresses the technical bottleneck in traditional solutions where the HSS cannot register 4G core network MME information with the UDM.

[0029] The SMS center 200 is used to determine the corresponding called mobile terminal when it receives a message transmission request from a mobile terminal, and send a routing information acquisition request for the called mobile terminal to the UDM module.

[0030] The SMS center is the triggering node for the downlink SMS transmission process. When the SMS center receives a message transmission request from a mobile terminal (i.e., the calling mobile terminal, MO), it means that the calling terminal has completed the uplink SMS sending operation. At this time, the SMS center needs to first complete basic request parsing and target location. The message transmission request contains key information such as the calling terminal identifier, the called terminal identifier, and the SMS content. By parsing this information, the SMS center determines the corresponding called mobile terminal (MT) and clarifies the final recipient of the SMS.

[0031] After identifying the called mobile terminal, the SMS center initiates a routing information retrieval request. This request is explicitly addressed to the UDM module, which centrally stores key data such as user subscription information and location information, providing routing data support for the SMS center. The routing information retrieval request sent by the SMS center to the UDM module uses a standardized message format (such as the Nudm_UECM_SendRoutingInfoForSM message) to ensure communication compatibility and data transmission accuracy. The request carries key parameters such as the unique identifier of the called mobile terminal, enabling the UDM module to quickly retrieve the corresponding user data. Through this operation, the SMS center delegates the core task of routing information querying to the UDM module, fully utilizing the UDM module's data management advantages while simplifying the SMS center's functional logic and providing necessary routing data for subsequent domain selection by the IP message gateway.

[0032] The UDM module 300 is used to respond to the routing information acquisition request and send the first mobility management entity information and the second mobility management entity information of the called mobile terminal to the IP message gateway; the second mobility management entity information is uploaded to the UDM module by the network element in the second network domain when the called mobile terminal completes the attachment registration in the second network domain.

[0033] In this embodiment, the UDM module, as the core network element responsible for unified management of user data, plays a crucial role in responding to routing information retrieval requests initiated by the SMS center, providing routing data support for downlink SMS transmission. Upon receiving a routing information retrieval request (such as a Nudm_UECM_SendRoutingInfoForSM message) from the SMS center, the UDM module immediately initiates a data retrieval and integration process. The routing information retrieval request carries the unique identifier of the called mobile terminal. Based on this identifier, the UDM module quickly locates the user data file corresponding to the terminal and extracts the first and second mobility management entity information. Unlike traditional solutions where the UDM module can only provide partial network domain routing information, the UDM module in this solution achieves centralized storage of multi-domain mobility management entity information through a prior data registration and upload mechanism. This ensures that complete routing data can be output at once when responding to a request, avoiding the problem of limited domain selection due to missing information. Subsequently, the UDM module encapsulates the first and second mobility management entity information into a standardized message format (such as the Nipsmgw_SMService_RoutingInfo message) through a standardized service interface and sends it to the IP message gateway to ensure the compatibility and accuracy of data transmission.

[0034] The second Mobility Management Entity (MMI) information corresponds to the attached registration data of the called mobile terminal in the second network domain. When the terminal successfully accesses the second network domain (such as the 5G core network) and completes the attached registration process, the dedicated network elements within the second network domain (such as the AMF network elements in the 5G core network) will actively capture the MMI association information of the terminal in that network domain, including the network node identifier, communication link parameters, and location area information. This data is uploaded to the UDM module through the standardized interface between the second network domain and the UDM module. The UDM module stores and manages this data according to a unified data format, forming an association mapping with the first MMI information registered with the HSS module. In this way, the problem of isolated storage of data from different network domains in traditional solutions can be overcome, enabling the stored data in the UDM module to cover routing information from multiple network domains. When responding to a request, the UDM module simultaneously sends both types of information to the IP message gateway, which solves the technical bottleneck that the UDM cannot transmit the 4G core network (corresponding to the first network domain) location information to the IP-SM-GW gateway under the 3GPP TS 29577 protocol. This allows the IP message gateway to simultaneously obtain the complete location data of the called mobile terminal in different network domains, providing a comprehensive decision-making basis for cross-network domain selection, thereby improving the flexibility and reliability of downlink short message transmission.

[0035] Specifically, the process of the UDM module sending the first and second mobility management entity information to the IP message gateway is mainly accomplished by the information sending unit built into the UDM module. This information sending unit primarily completes the transmission of the two types of mobility management entity information through the following steps: Step 1: Send the first mobility management entity information and the second mobility management entity information to the IP message gateway via a preset information transmission URL; The preset information transmission URL includes the Uniform Resource Identifier root path, IP Message Gateway-Message Service, version identifier, target downlink information, and general public user identifier.

[0036] After the UDM module completes the routing information retrieval and integration, the information sending unit synchronously sends the first and second Mobility Management Entity (MMI) information of the called mobile terminal to the IP message gateway. The preset information transmission URL serves as the core positioning basis for data transmission. Through structured design, it ensures that the information sending unit accurately locates the target receiving resource in the IP message gateway, avoiding path deviations or reception errors during data transmission.

[0037] The pre-defined message delivery URL has clearly defined functional components, covering key parts such as the Uniform Resource Identifier root path, IP message gateway-message service, version identifier, target downlink information, and General Public User Identifier (GPSI). Its specific URL definition is as follows: {apiRoot} / nipsmgw-smsevice / <apiversion> / mt-sm-infos / {gpsi}; The Uniform Resource Identifier (URI) root path provides the basic access entry for transmission requests. The IP Message Gateway-Message Service clarifies the core service type to which the data belongs. The version identifier ensures data interaction compatibility between different versions of network elements, avoiding information parsing failures due to interface version differences. The target downlink information field is directly associated with the short message-related identifier to be transmitted, while the general public user identifier ensures the unique binding of information to the called mobile terminal, ensuring that the IP Message Gateway can match the received entity information with the downlink message transmission requirements of the specific terminal. The information sending unit initiates a data transmission request through this URL, encapsulating the two types of mobility management entity information into a message format conforming to the 3GPP TS 29577 protocol specification. This overcomes the technical limitation in traditional solutions where the UDM cannot transmit 4G core network location information to the IP-SM-GW, allowing the IP Message Gateway to obtain complete multi-domain routing data at once, thereby enabling flexible execution of network domain selection.

[0038] The IP message gateway 400 is configured to perform a delivery domain selection task based on the first mobility management entity information and the second mobility management entity information to obtain a target delivery domain, and then transmit a target downlink message to the called mobile terminal through the target delivery domain.

[0039] As mentioned above, the first and second Mobility Management Entity (MMI) information comprehensively covers the location and access status data of the called mobile terminal in different network domains. Based on this information, the IP message gateway performs a delivery domain selection task according to a preset strategy. Combining factors such as network domain signal quality, terminal registration status, and service compatibility, it selects the optimal or available target delivery domain from the two network domains, thus overcoming the limitation of traditional solutions where core network domain selection cannot be effectively performed due to missing information. After determining the target delivery domain, the IP message gateway accurately delivers the target downlink message to the called mobile terminal through the network link corresponding to that domain. This ensures both the targeting and efficiency of message delivery and avoids message loss caused by the failure of delivery in a single network domain, significantly improving the integrity and reliability of downlink short message delivery.

[0040] Specifically, the IP message gateway mainly executes the domain selection process through its built-in domain selection execution module. The following section will introduce the specific domain selection execution process in conjunction with the specific implementation diagram.

[0041] See Figure 2 and Figure 3 , Figure 2 This is a flowchart illustrating a domain selection execution method provided in an embodiment of this application. Figure 3 This application provides an example of an interactive signaling diagram of a domain selection execution process. (See attached diagram.) Figure 2 Specifically, it includes the following steps: S1041: Based on the second mobility management entity information, send the target downlink message to the second message service network element, and receive the message transmission result fed back by the second message service network element.

[0042] In this embodiment, the first network domain and the second network domain are each configured with dedicated message service network elements. The first message service network element adapts to the protocol specifications and transmission characteristics of the first network domain (such as the MME network element in a 4G core network), while the second message service network element matches the technical architecture of the second network domain (such as the SMSF network element in a 5G core network). Both types of network elements serve as key forwarding nodes for short message transmission within their respective network domains, responsible for connecting the IP message gateway and the called mobile terminal to ensure compliant message transmission and delivery within the network domain. The IP message gateway, as the core of domain selection decision-making, has a built-in domain selection execution module that undertakes the dynamic filtering and execution functions of multi-domain message transmission paths.

[0043] The domain selection execution module begins its domain selection task execution in this step. First, it parses the second mobility management entity information sent by the UDM module. This information includes key data such as the identifier and interface parameters of the mobility management entity within the second network domain. Based on this data, the second message service network element can be accurately located, and a communication link can be established with that network element. Subsequently, the module encapsulates the target downlink message according to the protocol specifications of the second network domain and sends it to the second message service network element through the established communication link, while simultaneously initiating a message delivery status monitoring mechanism. After receiving the message, the second message service network element attempts to initiate a delivery operation to the called mobile terminal and generates a message delivery result based on factors such as the terminal response status and network link quality. This result is fed back to the domain selection execution module of the IP message gateway in the form of a standardized signaling message, providing a basis for subsequent domain selection decisions.

[0044] S1042: Determine whether the message transmission result is successful; S1043: If the message transmission result is successful, the second network domain is determined as the target transmission domain, and the target downlink message is transmitted to the called mobile terminal through the second message service network element; S1044: If the message transmission result is a transmission failure, the first network domain is determined as the target transmission domain, and the target downlink message is transmitted to the called mobile terminal through the first message service network element.

[0045] After obtaining the message delivery result, the domain selection execution module completes the status judgment through step S1042, forming a binary domain selection branch logic. When the judgment result is successful, step S1043 is executed to confirm that the second network domain has effective message delivery capability and designates it as the target delivery domain. At this time, the second message service network element continues to use the established communication link to complete the delivery of the target downlink message to the called mobile terminal, making full use of the technical advantages of the second network domain to ensure delivery efficiency. When the judgment result is failure, it indicates that there are abnormal situations such as unregistered terminals or link interruptions in the second network domain. At this time, the redundancy switching mechanism in step S1044 is triggered, and the first network domain is designated as the target delivery domain. The module then calls the first mobility management entity information, locates the first message service network element, and initiates message delivery through the protocol interface and transmission path corresponding to the network element, using the coverage capability of the first network domain to compensate for the delivery defects of the second network domain. In this way, the dual-network redundancy design solves the message loss problem caused by the failure of a single network domain, thereby improving the integrity and reliability of downlink short message delivery.

[0046] On the other hand, in one possible implementation, the IP message gateway in this embodiment of the application is further provided with an information feedback module. This information feedback module is used to feed back the routing information of the called mobile terminal and the identity information of its own gateway to the SMS center, specifically through the following two steps: Step 1: In response to the first mobility management entity information and the second mobility management entity information transmitted from the UDM module, generate routing information for the called mobile terminal; Step 2: Feed back the routing information of the called mobile terminal and the identity information of its own gateway to the UDM module, so that the UDM module will feed back the routing information and the identity information to the SMS center.

[0047] See Figure 4 This figure illustrates the signaling interaction of a routing information flow process according to an embodiment of this application. As shown in the figure, when the information feedback module within the IP message gateway receives the first and second mobility management entity information sent by the UDM module, it immediately initiates the data parsing and routing information generation process. The module extracts core fields from the two types of entity information, including network element identifiers, location area information, interface parameters, and other key data, and integrates them with its stored network topology and routing strategies to generate complete routing information for the called mobile terminal. This routing information clarifies the transmission path, adaptation protocol, and target network element of the short message in different network domains, providing data support for the subsequent confirmation of the transmission link by the SMS center.

[0048] After generating the routing information, the information feedback module performs a feedback operation, encapsulating the generated called mobile terminal routing information and its own gateway's identity information, and feeding it back to the UDM module through a standardized response message format. Upon receiving this feedback, the UDM module further forwards it to the SMS center, enabling the SMS center to understand the called terminal's routing status and the identity of the IP message gateway responsible for transmission, providing a complete information foundation for the initiation and monitoring of subsequent SMS transmissions. This ensures the effective flow of multi-domain routing information and improves the efficiency and accuracy of cross-network element collaboration through a standardized feedback mechanism.

[0049] This application provides a downlink messaging domain selection execution system, method, and medium. In this method, when a mobile terminal completes its first domain attachment registration, the HSS module registers the corresponding first Mobility Management Entity (MME) information with the UDM module. This overcomes the limitation of the 3GPP TS 29503 protocol on the HSS registering 4G core network MME information with the UDM, enabling the UDM module to simultaneously store the called mobile terminal's first MME information in the 4G core network and its second MME information in the second domain. When the UDM module responds to a routing information acquisition request, it sends both types of MME information to the IP message gateway, compensating for the deficiency under the 3GPP TS 29577 protocol that the UDM cannot transmit 4G core network location information to the IP-SM-GW, allowing the IP message gateway to obtain complete multi-domain location data. Based on this, the IP message gateway performs the transmission domain selection task according to two types of entity information, and can flexibly select the target transmission domain from the first network domain and the second network domain. This avoids the problem of a single transmission path caused by the inability to perform 4G core network domain selection in the past. Even if the transmission in one network domain fails, the downlink message transmission can still be completed through another network domain, ensuring the comprehensiveness and reliability of downlink short message transmission and solving the problem of insufficient integrity of downlink short message transmission in previous technologies.

[0050] The following describes a downlink message passing domain selection execution method provided by an embodiment of this application. The downlink message passing domain selection execution method described below can be referred to in correspondence with the downlink message passing domain selection execution system described above.

[0051] See Figure 5 The figure is a flowchart illustrating a downlink message passing domain selection execution method provided in an embodiment of this application, specifically including the following steps: S101: When the mobile terminal completes the attachment registration of the network domain through the HSS module, the first mobility management entity information of the mobile terminal in the first network domain is registered to the UDM module; the first network domain is the registration mode network domain of the HSS module. S102: When a message transmission request is received from a mobile terminal through the SMS center, the corresponding called mobile terminal is determined, and a routing information acquisition request for the called mobile terminal is sent to the UDM module. S103: The UDM module responds to the routing information acquisition request and sends the first mobility management entity information and the second mobility management entity information of the called mobile terminal to the IP message gateway; the second mobility management entity information is uploaded to the UDM module by the network element in the second network domain when the called mobile terminal completes the attachment registration in the second network domain. S104: Through the IP message gateway, a delivery domain selection task is performed based on the first mobility management entity information and the second mobility management entity information to obtain the target delivery domain, and the target downlink message is transmitted to the called mobile terminal through the target delivery domain.

[0052] In one possible implementation, the first network domain includes a first message service network element, and the second network domain includes a second message service network element; The step of performing a transport domain selection task through the IP message gateway based on the first mobility management entity information and the second mobility management entity information to obtain a target transport domain, and then transmitting a target downlink message to the called mobile terminal through the target transport domain, includes: Based on the second mobility management entity information, the target downlink message is sent to the second message service network element, and the message transmission result is received from the second message service network element. If the message transmission result is successful, the second network domain is determined as the target transmission domain, and the target downlink message is transmitted to the called mobile terminal through the second message service network element; If the message transmission result is a transmission failure, the first network domain is determined as the target transmission domain, and the target downlink message is transmitted to the called mobile terminal through the first message service network element.

[0053] Based on the same inventive concept, corresponding to the methods of any of the above embodiments, this application also provides a computer-readable storage medium storing computer instructions for causing the computer to execute the downlink message passing domain selection execution method as described in any of the above embodiments.

[0054] The computer-readable media in this application embodiment includes permanent and non-permanent, removable and non-removable media, and information storage can be implemented by any method or technology. Information can be computer-readable instructions, data structures, program modules, or other data. Examples of computer storage media include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, CD-ROM, digital versatile optical disc (DVD) or other optical storage, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other non-transfer medium that can be used to store information accessible by a computing device.

[0055] The computer instructions stored in the storage medium of the above embodiments are used to cause the computer to execute the downlink message passing domain selection execution method as described in any of the above embodiments, and have the beneficial effects of the corresponding method embodiments, which will not be repeated here.

[0056] It should be noted that the various embodiments in this specification are described in a progressive manner, and the same or similar parts between the various embodiments can be referred to mutually. Each embodiment focuses on describing the differences from other embodiments. In particular, for the system, method, and medium embodiments, since they are basically similar to the method embodiments, the description is relatively simple, and the relevant parts can be referred to the description of the method embodiments. The system, method, and medium embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate, and the components indicated as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of the solution in this embodiment according to actual needs. Those skilled in the art can understand and implement this without creative effort.

[0057] The above description is merely one specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the technical scope disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.< / apiversion>

Claims

1. A downlink message passing domain selection execution system, characterized in that, include: HSS module, SMS center, UDM module, and IP message gateway; The HSS module is used to register the first mobility management entity information of the mobile terminal in the first network domain to the UDM module when the mobile terminal completes the attachment registration of the network domain. The first domain is the registration mode domain of the HSS module; The SMS center is used to determine the corresponding called mobile terminal when it receives a message transmission request from a mobile terminal, and send a routing information acquisition request for the called mobile terminal to the UDM module. The UDM module is used to respond to the routing information acquisition request and send the first mobility management entity information and the second mobility management entity information of the called mobile terminal to the IP message gateway. The second mobility management entity information is uploaded to the UDM module by the network element in the second network domain when the called mobile terminal completes the attachment registration in the second network domain; The IP message gateway is configured to perform a delivery domain selection task based on the first mobility management entity information and the second mobility management entity information to obtain a target delivery domain, and then transmit a target downlink message to the called mobile terminal through the target delivery domain.

2. The system according to claim 1, characterized in that, The first network domain includes a first message service network element, and the second network domain includes a second message service element; the IP message gateway includes a domain selection execution module, which is specifically used for: Based on the second mobility management entity information, the target downlink message is sent to the second message service network element, and the message transmission result is received from the second message service network element. If the message transmission result is successful, the second network domain is determined as the target transmission domain, and the target downlink message is transmitted to the called mobile terminal through the second message service network element; If the message transmission result is a transmission failure, the first network domain is determined as the target transmission domain, and the target downlink message is transmitted to the called mobile terminal through the first message service network element.

3. The system according to claim 1, characterized in that, The IP message gateway includes an information feedback module, which is specifically used for: In response to the first mobility management entity information and the second mobility management entity information transmitted from the UDM module, routing information for the called mobile terminal is generated; The routing information of the called mobile terminal and the identity information of its own gateway are fed back to the UDM module, so that the UDM module feeds back the routing information and the identity information to the SMS center.

4. The system according to claim 1, characterized in that, The UDM module includes: an information sending unit, which is specifically used for: The first mobility management entity information and the second mobility management entity information are sent to the IP message gateway via a preset information transmission URL; The preset information transmission URL includes the Uniform Resource Identifier root path, IP Message Gateway-Message Service, version identifier, target downlink information, and general public user identifier.

5. The system according to claim 1, characterized in that, The HSS module includes an information registration unit, which is specifically used for: Based on a preset unified resource identifier, the first mobility management entity information is registered to the UDM module via the PUT method; the preset unified resource identifier includes the unified resource identifier root path, unified data management-user equipment context management, resource interface version identifier, the identifier of the mobile terminal, registration information, and mobility management entity.

6. The system according to claim 1, characterized in that, The mobility management entity information includes at least one of the following: mobility management entity address, mobility management entity IPv4 address, mobility management entity IPv6 address, and mobility management entity fully qualified domain name.

7. The system according to claim 2, characterized in that, The first network domain is a 4G core network, and the first message service network element is an MME network element; the second network domain is a 5G core network, and the second message service network element is an SMSF network element.

8. A method for executing downlink message passing domain selection, characterized in that, The method is applied to a domain selection execution system, which includes an HSS module, a short message center, a UDM module, and an IP message gateway; the method includes: When a mobile terminal completes its attachment registration to a network domain, the HSS module registers the mobile terminal's first mobility management entity information within the first network domain to the UDM module; the first network domain is the registration mode network domain of the HSS module. When a message transmission request is received from a mobile terminal through the SMS center, the corresponding called mobile terminal is determined, and a routing information acquisition request for the called mobile terminal is sent to the UDM module. The UDM module responds to the routing information acquisition request by sending the first mobility management entity information and the second mobility management entity information of the called mobile terminal to the IP message gateway; the second mobility management entity information is uploaded to the UDM module by the network element in the second network domain when the called mobile terminal completes the attachment registration in the second network domain. The IP message gateway performs a delivery domain selection task based on the first mobility management entity information and the second mobility management entity information to obtain the target delivery domain, and then transmits the target downlink message to the called mobile terminal through the target delivery domain.

9. The method according to claim 8, characterized in that, The first network domain includes a first message service network element, and the second network domain includes a second message service network element; The step of performing a transport domain selection task through the IP message gateway based on the first mobility management entity information and the second mobility management entity information to obtain a target transport domain, and then transmitting a target downlink message to the called mobile terminal through the target transport domain, includes: Based on the second mobility management entity information, the target downlink message is sent to the second message service network element, and the message transmission result is received from the second message service network element. If the message transmission result is successful, the second network domain is determined as the target transmission domain, and the target downlink message is transmitted to the called mobile terminal through the second message service network element; If the message transmission result is a transmission failure, the first network domain is determined as the target transmission domain, and the target downlink message is transmitted to the called mobile terminal through the first message service network element.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the program is executed by the processor, it implements the downlink message passing domain selection execution method as described in any one of claims 8-9.

Images