A method, device and system for determining a fallback mobility management entity MME

Abstract

The present application discloses a method, device, and system for determining a fallback mobility management entity (MME), which is applied to the DNS in the fallback mobility management entity (MME) determination system. The method includes: receiving a request message sent by a first device to instruct a query for a fallback MME, the request message including an identity identifier of a target base station; determining a first MME set corresponding to the identity identifier of the target base station from a pre-acquired MME paging table based on the identity identifier of the target base station; matching the first MME set with the second MME set to determine a third MME set, the second MME set being a set of MMEs determined by Internet Protocol addresses resolved according to preset domain name resolution rules; and sending the third MME set to the first device so that the first device determines the fallback target MME from the third MME set. The method for determining the fallback mobility management entity (MME) according to the embodiment of the present application can ensure that the selected target MME is connected to the target base station, so that the user equipment can successfully complete voice switching.

Description

Technical Field

[0001] The present application relates to the field of wireless communication technology, and in particular to a method, device, and system for determining a fallback mobility management entity (MME). Background Art

[0002] At present, in the early stage of the construction of the fifth generation mobile communication technology (5G), 5G signals have not yet been widely covered. Therefore, when there is no 5G signal coverage and the user equipment uses voice services on the 5G network, the user equipment can be switched from the 5G network to the fourth generation mobile communication technology (4G) network through the Evolved Packet System fallback (EPS fallback) process, and voice services can be used through the 4G network.

[0003] In the existing EPS fallback process, when selecting the fallback Mobility Management Entity (MME), the Domain Name Server (DNS) returns a list of MMEs based on the resolution rules, and then the Access and Mobility Management Function (AMF) selects the best MME as the target MME based on "order" and "preference".

[0004] However, in the existing EPS fallback process, the selected target fallback MME may not be connected to the target base station, so that the user equipment cannot switch from the 5G network to the 4G network, resulting in EPS fallback failure. Summary of the Invention

[0005] The embodiments of the present application provide a method, device and system for determining a fallback mobility management entity MME, which can ensure that the selected target MME is connected to the target base station, so that the user equipment can successfully switch from the 5G network to the 4G network, avoiding the failure of the EPS fallback process.

[0006] In a first aspect, an embodiment of the present application provides a method for determining a fallback mobility management entity MME, which is applied to a domain name server DNS in a system for determining the fallback mobility management entity MME. The system for determining the fallback mobility management entity MME further includes a first device, where the first device is an access and mobility management function AMF or an MME before fallback. The method includes:

[0007] Receiving a request message sent by the first device for instructing to query the fallback MME, wherein the request message includes an identity of a target base station;

[0008] Determining, according to the identity of the target base station, a first MME set corresponding to the identity of the target base station from a pre-acquired MME paging table, wherein the MME paging table includes multiple MMEs, each MME in the MME paging table corresponds to the identity of at least one base station, and each MME in the first MME set and the target base station corresponding to the identity of the target base station are in a connected state;

[0009] Matching the first MME set and the second MME set to determine a third MME set, wherein the second MME set is a set of MMEs determined by Internet Protocol addresses resolved according to a preset domain name resolution rule;

[0010] The third MME set is sent to the first device, so that the first device determines a target MME for fallback from the third MME set.

[0011] In a second aspect, an embodiment of the present application provides a method for determining a fallback mobility management entity MME, which is applied to a first device in a system for determining a fallback mobility management entity MME, wherein the first device is an access and mobility management function AMF or an MME before fallback, and the fallback mobility management entity MME determination system further includes a domain name server DNS, and the method includes:

[0012] Sending a request message for instructing to query the fallback MME to the DNS, the request message including the identity of the target base station, so that the DNS determines, based on the identity of the target base station, a first MME set corresponding to the identity of the target base station from a pre-acquired MME paging table, matches the first MME set with a second MME set determined by an Internet Protocol address resolved according to a preset domain name resolution rule, determines the third MME set, and sends the third MME set to the first device;

[0013] receiving the third MME set sent by the DNS, wherein each MME in the third MME set and the target base station corresponding to the identity of the target base station are in a connected state;

[0014] Based on a preset selection rule, a target MME for fallback is determined from the third MME set.

[0015] In a third aspect, an embodiment of the present application provides a device for determining a fallback mobility management entity MME, characterized in that a domain name server DNS is applied to a system for determining a fallback mobility management entity MME, and the system for determining the fallback mobility management entity MME further includes a first device, the first device being an access and mobility management function AMF or an MME before fallback, and the device includes:

[0016] A receiving module, configured to receive a request message sent by the first device for instructing to query the fallback MME, wherein the request message includes an identity of a target base station;

[0017] a verification module, configured to determine, based on the identity of the target base station, a first MME set corresponding to the identity of the target base station from a pre-acquired MME paging table, wherein the MME paging table includes a plurality of MMEs, each MME in the MME paging table corresponds to the identity of at least one base station, and each MME in the first MME set and the target base station corresponding to the identity of the target base station are in a connected state;

[0018] a matching module, configured to match the first MME set and the second MME set to determine a third MME set, wherein the second MME set is a set of MMEs determined by Internet Protocol addresses resolved according to a preset domain name resolution rule;

[0019] The sending module is configured to send the third MME set to the first device, so that the first device determines a target MME to fall back to from the third MME set.

[0020] In a fourth aspect, an embodiment of the present application provides a device for determining a fallback mobility management entity MME, characterized in that it is applied to a first device in a system for determining a fallback mobility management entity MME, the first device being an access and mobility management function AMF or an MME before fallback, the system for determining the fallback mobility management entity MME further including a domain name server DNS, and the device including:

[0021] a sending module, configured to send a request message for instructing to query a fallback MME to the DNS, the request message including an identity of a target base station, so that the DNS determines, based on the identity of the target base station, a first MME set corresponding to the identity of the target base station from a pre-acquired MME paging table, matches the first MME set with a second MME set determined by an Internet Protocol address resolved according to a preset domain name resolution rule, determines the third MME set, and sends the third MME set to the first device;

[0022] a receiving module, configured to receive the third MME set sent by the DNS, wherein each MME in the third MME set and the target base station corresponding to the identity of the target base station are in a connected state;

[0023] The determination module is configured to determine a target MME to fall back to from the third MME set based on a preset selection rule.

[0024] In a fifth aspect, an embodiment of the present application provides a system for determining a fallback mobility management entity MME, characterized in that the system for determining a fallback mobility management entity MME includes a first device, a domain name server DNS,

[0025] and a verification module, the first device being an access and mobility management function AMF or an MME before fallback, and the verification module being connected to the DNS;

[0026] The first device is configured to send a request message for instructing to query a fallback MME to the DNS, the request message including an identity of a target base station; and further configured to receive the third MME set sent by the DNS, and determine a fallback target MME from the third MME set based on a preset selection rule;

[0027] The DNS is configured to send the identity of the target base station to the verification module; and is further configured to determine a second MME set according to the Internet Protocol address resolved according to a preset domain name resolution rule, match the first MME set with the second MME set, determine a third MME set, and send the third MME set to the first device;

[0028] The verification module is used to determine, based on the identity of the target base station, a first MME set corresponding to the identity of the target base station from a pre-acquired MME paging table, and send the first MME set to the DNS, wherein the MME paging table includes multiple MMEs, each MME in the MME paging table corresponds to the identity of at least one base station, and each MME in the first MME set and the target base station corresponding to the identity of the target base station are in a connected state.

[0029] In a sixth aspect, an embodiment of the present application provides a device for determining a fallback mobility management entity MME, the device including:

[0030] a processor and a memory storing computer program instructions;

[0031] When the processor executes the computer program instructions, the method for determining the fallback mobility management entity MME as described in any one of the above embodiments is implemented.

[0032] In a seventh aspect, an embodiment of the present application provides a computer storage medium having computer program instructions stored thereon. When the computer program instructions are executed by a processor, the method for determining the fallback mobility management entity MME described in any one of the above embodiments is implemented.

[0033] The method, apparatus, and system for determining a fallback mobility management entity (MME) according to embodiments of the present application are applied to a fallback mobility management entity (MME) determination system. The fallback mobility management entity (MME) determination system includes a domain name server (DNS) and a first device. When the first device sends a request message including the identity of a target base station to the DNS, a verification module in the DNS matches the identity of the target base station with an MME paging table to determine a first MME set corresponding to the identity of the target base station, thereby ensuring that each MME in the first MME set is connected to the target base station. The DNS then matches a second MME set determined by a preset domain name resolution rule with the first MME set to obtain a third MME set, thereby ensuring that each MME in the obtained third MME set is connected to the target base station. The DNS then sends the third MME set to the first device, which then determines a fallback target MME from the third MME set according to a preset selection rule. Thus, the fallback mobility management entity (MME) determination method of the present application ensures that the selected target MME is connected to the target base station, thereby effectively avoiding voice handover failures caused by the selected target MME and the target base station not being connected. BRIEF DESCRIPTION OF THE DRAWINGS

[0034] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the following is a brief introduction to the drawings required for use in the embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without any creative work.

[0035] Figure 1 This is a schematic diagram of the signaling process for selecting the target MME in the existing EPS fallback process;

[0036] Figure 2 This is a schematic diagram of the structure of the existing EPS fallback process switching failure;

[0037] Figure 3 This is a system architecture diagram of a system for determining a fallback mobility management entity MME provided by an embodiment of the present application;

[0038] Figure 4 This is a system architecture diagram of a fallback mobility management entity MME determination system provided by another embodiment of the present application.

[0039] Figure 5 This is a schematic diagram of the signaling interaction flow of a system for determining a fallback mobility management entity MME provided by an embodiment of the present application;

[0040] Figure 6 This is a flowchart of a method for selecting a fallback mobility management entity MME provided by an embodiment of the present application;

[0041] Figure 7 1 is a flow chart of a method for selecting a fallback mobility management entity MME provided in another embodiment of the present application;

[0042] Figure 8 This is a schematic diagram of the signaling interaction flow of a system for determining a fallback mobility management entity MME provided by another embodiment of the present application;

[0043] Figure 9 This is a structural diagram of a device for determining a fallback mobility management entity MME provided by an embodiment of the present application;

[0044] Figure 10 1 is a structural diagram of a device for determining a fallback mobility management entity MME provided in another embodiment of the present application;

[0045] Figure 11 This is a structural diagram of a device for determining a fallback mobility management entity MME provided in one embodiment of the present application. DETAILED DESCRIPTION

[0046] The features and exemplary embodiments of various aspects of the present application will be described in detail below. In order to make the purpose, technical solutions and advantages of the present application clearer, the present application will be further described in detail below in conjunction with the accompanying drawings and specific embodiments. It should be understood that the specific embodiments described herein are only intended to explain the present application, rather than to limit the present application. For those skilled in the art, the present application can be implemented without the need for some of these specific details. The following description of the embodiments is merely to provide a better understanding of the present application by illustrating the examples of the present application.

[0047] It should be noted that, in this document, relational terms such as first and second, etc., are used only to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any actual relationship or order between these entities or operations. Moreover, the terms "comprises," "comprising," or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article, or device comprising a series of elements includes not only those elements, but also other elements not explicitly listed, or elements inherent to such process, method, article, or device. In the absence of further limitations, the elements defined by the phrase "comprising..." do not exclude the presence of other identical elements in the process, method, article, or device comprising the elements.

[0048] In order to explain in detail the technical solution of a method for determining a fallback mobility management entity MME of the present application, a brief description will be given below of the existing technical solution for selecting a fallback mobility management entity MME.

[0049] First, when the user equipment switches from the 5G network to the 4G network, it can be achieved through the EPS fallback process. Figure 1 The signaling flow chart for selecting the fallback MME in the existing EPS fallback process is shown as follows: Figure 1 As shown, Figure 1 11 in the figure is for selecting the target MME for fallback. AMF sends a request to DNS to obtain the request information of the fallback MME. DNS selects a set of MME lists as shown in Table 1 according to the domain name resolution rules and sends it to AMF. Then AMF selects a set of optimal MMEs as the fallback target MMEs from the MME list shown in Table 1 according to the "order" and "preference" rules. However, if Figure 2 As shown in the figure, the link between MME01 and base station LTE01 fails. When MME01 is selected as the fallback MME through the existing EPS fallback process, due to the link failure between MME01 and base station LTE01, the handover will fail when the AMF switches to MME01. Therefore, the EPS fallback process fails.

[0050] Table 1 List of MMEs resolved by existing DNS resolution rules

[0051] order preference MME 01 10 50 MME 02 10 50 … … … MME N 20 60

[0052] Secondly, in 4G networks, if the Long Term Evolution (LTE) base station (eNodeB) is not fully interconnected with the MME pool (MME POOL), it will not affect fixed-point calls. However, voice calls may fail when switching between pools. However, the probability of this happening is lower in 4G than in 5G.

[0053] It's important to note that an MME pool is composed of multiple MMEs, and a base station can connect to multiple MMEs within the pool. Each MME in the pool can serve the wireless area covered by the pool. Therefore, in a 4G network, if you're handing off within the same pool, even if the base station isn't fully connected to the MME pool, it won't affect fixed-point calls. However, when handing off between pools, if the target MME isn't connected to the target base station, voice calls may fail.

[0054] Therefore, according to the above description, in the existing voice switching process, the reason for the switching failure may be that when selecting the target MME for fallback, the connection status of the target MME and the target base station (target eNodeB) is not verified. When the selected fallback target MME and the target base station (target eNodeB) are not connected, the switching failure will occur.

[0055] In response to the above technical problems, an embodiment of the present application provides a system for determining the fallback mobility management entity MME. A verification module is newly added to the system, through which the connection status of the MME and the target base station can be verified to ensure that the target MME and target base station finally selected for fallback are in a connected state.

[0056] It should be noted that the determination system for falling back to the mobility management entity MME may include a domain name server DNS and a first device, wherein the verification module may be a built-in module of the DNS or an external device connected to the DNS.

[0057] As an example, when the verification module is a built-in module of DNS, Figure 3 A system architecture diagram of a fallback mobility management entity MME determination system 300 provided in an embodiment of the present application is shown.

[0058] like Figure 3 As shown, a system 300 for determining a fallback mobility management entity MME may include a first device 301 and a domain name server DNS 302 .

[0059] The first device 301 may be an access and mobility management function (AMF) or an MME before fallback, connected to a DNS, and configured to send a request message to the DNS indicating a query for a fallback MME; and further configured to determine a fallback target MME from the MME set sent by the DNS;

[0060] DNS 302 has a built-in verification module 3021 for verifying the connection status between the MME and the target base station. The DNS verifies the connection status between the MME and the target base station using the built-in verification module. After the verification passes, a set of MMEs can be obtained. The DNS is also used to select an MME set to fall back to based on existing DNS resolution rules, and to intersect the MME set obtained by the verification module with the MME set selected to fall back based on the DNS resolution rules, and send the MME intersection to the first device.

[0061] As another example, in the case where the verification module is an external device connected to the DNS, Figure 4 A system architecture diagram of a fallback mobility management entity MME determination system 400 provided in an embodiment of the present application is shown.

[0062] like Figure 4 As shown, a system 400 for determining a fallback mobility management entity MME may include a first device 401 , a domain name server DNS 402 , and a verification module 403 .

[0063] The first device 401 may be an access and mobility management function (AMF) or an MME before fallback, connected to a DNS, and configured to send a request message instructing the DNS to query a fallback MME, and further configured to determine a fallback target MME from the MME set sent by the DNS;

[0064] DNS 402 is connected to the verification module and is used to receive the verified MME set sent by the verification module; and DNS is also used to select the MME set to fall back to according to the existing DNS resolution rules, and match the MME set sent by the verification module with the MME set selected to fall back to according to the DNS resolution rules to obtain a matched MME set, and send the matched MME set to the first device.

[0065] The verification module 403 is configured to obtain the identity of the target base station sent by the DNS, verify the connection status between the MME and the target base station according to the identity of the target base station, and send the MME set that passes the verification to the DNS.

[0066] The system for determining the fallback mobility management entity MME provided in the embodiment of the present application can verify the connection status of the MME and the target base station through the verification module in the DNS before selecting the target MME for fallback, and match the MME set that has passed the verification with the MME set selected under the existing resolution rules, and select the target MME for fallback from the matching MME set, which can not only meet the existing rules, but also ensure that the selected target MME and the target base station are in a connected state, effectively avoiding the call switching failure problem caused by the selected target MME and the target base station being not connected.

[0067] In the embodiment of the present application, when the verification module is a DNS built-in module, based on the above-mentioned fallback mobility management entity MME determination system 300, Figure 5 The figure shows a signaling interaction flow chart in a system for determining a fallback mobility management entity MME.

[0068] like Figure 5 As shown, the signaling interaction process may include the following steps:

[0069] S501: A first device sends a request message to a DNS to instruct the DNS to query a fallback MME, wherein the request message includes an identity of a target base station.

[0070] In the embodiment of the present application, since the network currently connected to the user equipment may be different, the first device may be an AMF or an MME before fallback. Specifically, when the user equipment is currently on a 5G network and needs to switch from the 5G network to a 4G network, the first device may be an AMF; when the user equipment is currently on a 4G network and needs to switch from the 4G network across an MMEPOOL, the first device may be an MME before fallback (i.e., the MME currently connected to the user equipment).

[0071] It should be noted that the identity of the above-mentioned target base station can be obtained by querying the tracking area identity (TAI) code of the user equipment. The TAI code is used to identify the location of the user equipment, and the location of the base station corresponding to the user equipment can be determined based on the location of the user equipment. Specifically, the target base station to which the paging message needs to be sent can be determined based on the TAI code, and then the identity of the target base station can be obtained.

[0072] For example, the AMF (ie, the first device) sends a DNS_query message (ie, request information) to the DNS, and adds the target eNodeB ID=151993 field (ie, the identity of the target base station) to the message.

[0073] S502: The verification module in the DNS obtains the identity of the target base station, and determines the first MME set corresponding to the identity of the target base station from the pre-acquired MME paging table according to the identity of the target base station.

[0074] In an embodiment of the present application, the above-mentioned MME paging table may be an MME paging table pre-stored in the DNS locally, and the MME paging table may include information of multiple MMEs, each MME may correspond to the identity of at least one base station, wherein the multiple MMEs in the MME paging table may be MMEs in the same MME POOL.

[0075] In addition, if an MME does not have the corresponding base station ID in the MME paging table, it may indicate that the MME is disconnected or not connected to the base station. Therefore, the verification module in the DNS can determine whether each MME is connected to the target base station by querying the MME paging table for the target base station ID.

[0076] For example, in the MME paging table shown in Table 2, there are N MMEs in total, and "ENodeB ID" is the identity of the base station. According to Table 2, ENodeB ID = 151993 does not exist under MME 01, but exists in MME 02-MME N. Therefore, it can be considered that: ENodeB ID = 151993 is disconnected or not interconnected with MME 01.

[0077] Table 2 MME paging table

[0078]

[0079]

[0080] In the embodiment of the present application, since the first MME set is the MME set determined by the verification module, it can be determined that each MME in the first MME set and the target base station corresponding to the identity of the target base station are in a connected state.

[0081] It should be noted that, since some base stations may not be interconnected with all MMEs in the MME POOL in the initial stage of project construction, or there may be configuration errors after the base station upgrade and configuration adjustment during routine maintenance, resulting in some base stations not connecting to all MMEs under the MME POOL, it is necessary to update the connection status of the MME and the base station in the MME paging table regularly or before matching the MME set through the MME paging table to ensure the real-time and accuracy of the information in the MME paging table.

[0082] Specifically, the DNS updates the MME paging table, which may include the following steps:

[0083] Step A: obtaining information of each MME in the MME pool, wherein the information of each MME includes a real-time connection relationship between each MME and at least one base station;

[0084] Step B: Based on the connection relationship between each MME and at least one base station, the MME and the corresponding base station identity in the MME paging table are updated.

[0085] S503: The DNS matches the second MME set determined by the Internet Protocol address resolved by the preset domain name resolution rule with the first MME set to determine a third MME set.

[0086] In the embodiment of the present application, the above-mentioned domain name resolution rules may be domain name resolution rules in the prior art. Therefore, the above-mentioned set of second MMEs may be a fallback MME set selected by the DNS according to the existing domain name resolution rules.

[0087] In addition, the above matching of the second MME set and the first MME set to determine the third MME set may be to determine the intersection of the second MME set and the first MME set as the third MME set.

[0088] Therefore, since each MME in the above-mentioned first MME set and the target base station corresponding to the identity identifier are in a connected state, it can be ensured that each MME in the third MME set and the target base station are in a connected state, and it can also be ensured that the third MME set meets the existing rules for selecting the fallback MME.

[0089] S504, the DNS sends the third MME set to the first device;

[0090] S505: The first device determines a target MME for fallback from the third MME set based on a preset selection rule.

[0091] In the embodiment of the present application, the above-mentioned preset selection rules can be selection rules of preset "order" and "preference" factors, or can be selection rules set according to specific needs, which are not limited here.

[0092] Based on this, when the first device sends a request message including the identity of the target base station to the DNS, the verification module in the DNS determines the first MME set corresponding to the identity of the target base station by matching the identity of the target base station with the MME paging table, thereby ensuring that each MME in the first MME set and the target base station are in a connected state; then, the DNS matches the second MME set determined by the preset domain name resolution rule with the first MME set to obtain a third MME set, thereby ensuring that each MME in the obtained third MME set and the target base station are in a connected state, and sends the third MME set to the first device, and the first device determines the target MME to fall back to from the third MME set according to the preset selection rule. In this way, through the method for determining the fallback mobility management entity MME of the present application, it can be ensured that the selected target MME and the target base station are in a connected state, thereby effectively avoiding the problem of voice switching failure caused by the selected target MME and the target base station not being connected.

[0093] like Figure 6 As shown, the embodiment of the present application further provides a method for determining a fallback mobility management entity MME, which is applied to a domain name server DNS in a system 300 for determining a fallback mobility management entity MME. The method may include the following steps:

[0094] Step 601: receiving a request message sent by the first device for instructing to query a fallback MME, wherein the request message includes an identity of a target base station;

[0095] Step 602: Determine, based on the identity of the target base station, a first MME set corresponding to the identity of the target base station from a pre-acquired MME paging table, wherein the MME paging table includes multiple MMEs, each MME in the MME paging table corresponds to the identity of at least one base station, and each MME in the first MME set is in a connected state with the target base station corresponding to the identity of the target base station;

[0096] Step 603: Match the first MME set and the second MME set to determine a third MME set, wherein the second MME set is a set of MMEs determined by Internet Protocol addresses resolved according to a preset domain name resolution rule;

[0097] Step 604: Send the third MME set to the first device, so that the first device determines a target MME to fall back to from the third MME set.

[0098] Based on this, when the first device sends a request message including the identity of the target base station to the DNS, the verification module in the DNS determines the first MME set corresponding to the identity of the target base station by matching the identity of the target base station with the MME paging table, thereby ensuring that each MME in the first MME set and the target base station are in a connected state; then, the DNS matches the second MME set determined by the preset domain name resolution rule with the first MME set to obtain a third MME set, thereby ensuring that each MME in the obtained third MME set and the target base station are in a connected state, and sends the third MME set to the first device, and the first device determines the target MME to fall back to from the third MME set according to the preset selection rule. In this way, through the method for determining the fallback mobility management entity MME of the present application, it can be ensured that the selected target MME and the target base station are in a connected state, thereby effectively avoiding the problem of voice switching failure caused by the selected target MME and the target base station not being connected.

[0099] Optionally, before determining, according to the identity of the target base station, from a pre-acquired MME paging table, the first MME set corresponding to the identity of the target base station, the method may further include:

[0100] Obtaining information of each MME in an MME pool, where the MME pool includes a plurality of pre-defined MMEs, and the information of each MME includes a connection relationship between each MME and at least one base station;

[0101] Based on the connection relationship between each MME and at least one base station, the MME and the corresponding base station identity in the MME paging table are updated.

[0102] Based on this, before matching the identity of the target base station with the MME paging table, the MME paging table is updated by obtaining the latest connection status information of each MME and base station from the MME pool. This can ensure that the information in the MME paging table is real-time connection information, thereby making the selected target MME and target base station in a state of mutual connection, which can improve the switching success rate.

[0103] Optionally, matching the first MME set and the second MME set to determine a third MME set may specifically include:

[0104] Determine an intersection of the first MME set and the second MME set;

[0105] The intersection is determined as a third MME set.

[0106] Based on this, by determining the intersection of the first MME set and the second MME set as the third MME set, it can not only meet the existing rules for selecting the target MME for fallback, but also ensure that each MME in the final third MME set is in a connected state with the target base station, which can effectively avoid the problem of voice switching failure caused by the final selected fallback target MME not being connected to the target base station.

[0107] The relevant descriptions of the embodiments of the present application can refer to the relevant descriptions of the aforementioned embodiments, and can achieve the same technical effects. To avoid repetition, they will not be described in detail.

[0108] like Figure 7 As shown, the embodiment of the present application further provides a method for determining a fallback mobility management entity MME, which is applied to a first device in a system 300 for determining a fallback mobility management entity MME. The method may include the following steps:

[0109] Step 701: Send a request message for instructing to query a fallback MME to the DNS, where the request message includes an identity of a target base station, so that the DNS determines, based on the identity of the target base station, a first MME set corresponding to the identity of the target base station from a pre-acquired MME paging table, matches the first MME set with a second MME set determined by an Internet Protocol address resolved according to a preset domain name resolution rule, determines the third MME set, and sends the third MME set to the first device.

[0110] Step 702: Receive the third MME set sent by the DNS, wherein each MME in the third MME set and the target base station corresponding to the identity of the target base station are in a connected state;

[0111] Step 703: Determine a target MME for fallback from the third MME set based on a preset selection rule.

[0112] Based on this, when the first device sends a request message including the identity of the target base station to the DNS, the verification module in the DNS determines the first MME set corresponding to the identity of the target base station by matching the identity of the target base station with the MME paging table, thereby ensuring that each MME in the first MME set and the target base station are in a connected state; then, the DNS matches the second MME set determined by the preset domain name resolution rule with the first MME set to obtain a third MME set, thereby ensuring that each MME in the obtained third MME set and the target base station are in a connected state, and sends the third MME set to the first device, and the first device determines the target MME to fall back to from the third MME set according to the preset selection rule. In this way, through the method for determining the fallback mobility management entity MME of the present application, it can be ensured that the selected target MME and the target base station are in a connected state, thereby effectively avoiding the problem of voice switching failure caused by the selected target MME and the target base station not being connected.

[0113] The relevant descriptions of the embodiments of the present application can refer to the relevant descriptions of the aforementioned embodiments, and can achieve the same technical effects. To avoid repetition, they will not be described in detail.

[0114] In the embodiment of the present application, when the verification module is an external device connected to the DNS, based on the above-mentioned fallback mobility management entity MME determination system 400, Figure 8 A signaling interaction flow chart of another fallback Mobility Management Entity MME determination system is shown.

[0115] like Figure 8 As shown, the signaling interaction process may include the following steps:

[0116] S801, the first device 401 sends a request message to the DNS 402 to instruct it to query the fallback MME, where the request message includes an identity of a target base station;

[0117] S802, DNS 402 sends the identity of the target base station to verification module 403;

[0118] S803, the verification module 403 determines the first MME set corresponding to the identity of the target base station from the pre-acquired MME paging table according to the identity of the target base station,

[0119] S804, the verification module 403 sends the first MME set to the DNS 402;

[0120] S805, DNS 402 determines a second MME set based on the Internet Protocol address resolved according to the preset domain name resolution rule, and matches the first MME set with the second MME set to determine a third MME set.

[0121] S806, DNS 402 sends the third MME set to the first device 401;

[0122] S807: The first device 401 receives the third MME set sent by the DNS, and determines a fallback target MME from the third MME set based on a preset selection rule.

[0123] Based on this, when the first device sends a request message including the identity of the target base station to the DNS, the verification module in the DNS determines the first MME set corresponding to the identity of the target base station by matching the identity of the target base station with the MME paging table, thereby ensuring that each MME in the first MME set and the target base station are in a connected state; then, the DNS matches the second MME set determined by the preset domain name resolution rule with the first MME set to obtain a third MME set, thereby ensuring that each MME in the obtained third MME set and the target base station are in a connected state, and sends the third MME set to the first device, and the first device determines the target MME to fall back to from the third MME set according to the preset selection rule. In this way, through the method for determining the fallback mobility management entity MME of the present application, it can be ensured that the selected target MME and the target base station are in a connected state, thereby effectively avoiding the problem of voice switching failure caused by the selected target MME and the target base station not being connected.

[0124] The relevant descriptions of the embodiments of the present application can refer to the relevant descriptions of the aforementioned embodiments, and can achieve the same technical effects. To avoid repetition, they will not be described in detail.

[0125] It should be noted that the method for determining the fallback mobility management entity MME in the embodiment of the present application can also be applied to the first device 401, DNS 402 and verification module 403 in the fallback mobility management entity MME determination system 400. To avoid repetition, they are not described here.

[0126] Figure 9 A structural diagram of a device for determining a fallback mobility management entity MME provided in an embodiment of the present application is shown.

[0127] like Figure 9 As shown, the apparatus 900 for determining the fallback mobility management entity MME is applied to the domain name server DNS 302 in the system 300 for determining the fallback mobility management entity MME. The system for determining the fallback mobility management entity MME further includes a first device 301, which is an access and mobility management function AMF or an MME before fallback. The apparatus 900 may include:

[0128] The receiving module 901 is configured to receive a request message sent by the first device to instruct to query the fallback MME, wherein the request message includes an identity of a target base station;

[0129] A verification module 902 is configured to determine, based on the identity of the target base station, a first MME set corresponding to the identity of the target base station from a pre-acquired MME paging table, wherein the MME paging table includes multiple MMEs, each MME in the MME paging table corresponds to the identity of at least one base station, and each MME in the first MME set and the target base station corresponding to the identity of the target base station are in a connected state;

[0130] a matching module 903 configured to match the first MME set and the second MME set to determine a third MME set, wherein the second MME set is a set of MMEs determined by Internet Protocol addresses resolved according to a preset domain name resolution rule;

[0131] The sending module 904 is configured to send the third MME set to the first device, so that the first device determines a target MME to fall back to from the third MME set.

[0132] An embodiment of the present application provides a device for determining a fallback mobility management entity (MME). When a first device sends a request message including the identity of a target base station to a DNS, a verification module in the DNS matches the identity of the target base station with an MME paging table to determine a first MME set corresponding to the identity of the target base station, thereby ensuring that each MME in the first MME set is connected to the target base station. The DNS then matches a second MME set determined by a preset domain name resolution rule with the first MME set to obtain a third MME set, thereby ensuring that each MME in the obtained third MME set is connected to the target base station. The DNS then sends the third MME set to the first device, and the first device determines the target MME to fall back to from the third MME set according to a preset selection rule. In this way, the method for determining a fallback mobility management entity (MME) of the present application ensures that the selected target MME is connected to the target base station, thereby effectively avoiding voice handover failures caused by the selected target MME and the target base station not being connected.

[0133] Optionally, the apparatus 900 further includes:

[0134] an acquisition module, configured to acquire information of each MME in an MME pool, the MME pool including a plurality of pre-set MMEs, the information of each MME including a connection relationship between each MME and at least one base station;

[0135] The updating module is configured to update the MME and the corresponding base station identity in the MME paging table based on the connection relationship between each MME and at least one base station.

[0136] Based on this, before matching the identity of the target base station with the MME paging table, the MME paging table is updated by obtaining the latest connection status information of each MME and base station from the MME pool. This can ensure that the information in the MME paging table is real-time connection information, thereby making the selected target MME and target base station in a state of mutual connection, which can improve the switching success rate.

[0137] Optionally, the matching module 903 is specifically configured to:

[0138] Determine an intersection of the first MME set and the second MME set;

[0139] The intersection is determined as a third MME set.

[0140] Based on this, by determining the intersection of the first MME set and the second MME set as the third MME set, it can not only meet the existing rules for selecting the target MME for fallback, but also ensure that each MME in the final third MME set is in a connected state with the target base station, which can effectively avoid the problem of voice switching failure caused by the final selected fallback target MME not being connected to the target base station.

[0141] The apparatus 900 for determining the fallback mobility management entity MME provided in the embodiment of the present application can achieve Figure 6 Methods and Figure 3 To avoid repetition, the various processes of the system embodiment will not be described here.

[0142] Figure 10 A structural diagram of a device for determining a fallback mobility management entity MME provided in an embodiment of the present application is shown.

[0143] like Figure 10 As shown, the apparatus 1000 for determining a fallback mobility management entity MME is applied to a first device 301 in a system 300 for determining a fallback mobility management entity MME, wherein the first device is an access and mobility management function AMF or an MME before fallback. The system for determining the fallback mobility management entity MME further includes a domain name server DNS 302. The apparatus 1000 may include:

[0144] A sending module 1001 is configured to send a request message for instructing to query a fallback MME to the DNS, where the request message includes an identity of a target base station, so that the DNS determines, based on the identity of the target base station, a first MME set corresponding to the identity of the target base station from a pre-acquired MME paging table, matches the first MME set with a second MME set determined by an Internet Protocol address resolved according to a preset domain name resolution rule, determines the third MME set, and sends the third MME set to the first device;

[0145] The receiving module 1002 is configured to receive the third MME set sent by the DNS, wherein each MME in the third MME set and the target base station corresponding to the identity of the target base station are in a connected state;

[0146] The determination module 1003 is configured to determine a target MME for fallback from the third MME set based on a preset selection rule.

[0147] Based on this, when the first device sends a request message including the identity of the target base station to the DNS, the verification module in the DNS determines the first MME set corresponding to the identity of the target base station by matching the identity of the target base station with the MME paging table, thereby ensuring that each MME in the first MME set and the target base station are in a connected state; then, the DNS matches the second MME set determined by the preset domain name resolution rule with the first MME set to obtain a third MME set, thereby ensuring that each MME in the obtained third MME set and the target base station are in a connected state, and sends the third MME set to the first device, and the first device determines the target MME to fall back to from the third MME set according to the preset selection rule. In this way, through the method for determining the fallback mobility management entity MME of the present application, it can be ensured that the selected target MME and the target base station are in a connected state, thereby effectively avoiding the problem of voice switching failure caused by the selected target MME and the target base station not being connected.

[0148] The embodiment of the present application provides a method 1000 for determining a fallback mobility management entity MME. Figure 7 Methods and Figure 3 To avoid repetition, the various processes of the embodiment of the system are not described here.

[0149] Figure 11 A schematic diagram of the hardware structure of a device for determining a fallback mobility management entity MME provided in an embodiment of the present application is shown.

[0150] The device for determining the fallback mobility management entity MME may include a processor 1101 and a memory 1102 storing computer program instructions.

[0151] Specifically, the processor 1101 may include a central processing unit (CPU), or an application specific integrated circuit (ASIC), or may be configured to implement one or more integrated circuits of the embodiments of the present application.

[0152] Memory 1102 may include a large capacity memory for data or instructions. By way of example and not limitation, memory 1102 may include a hard disk drive (HDD), a floppy disk drive, a flash memory, an optical disk, a magneto-optical disk, a magnetic tape, or a universal serial bus (USB) drive, or a combination of two or more of these. Where appropriate, memory 1102 may include removable or non-removable (or fixed) media. Where appropriate, memory 1102 may be inside or outside the integrated gateway disaster recovery device. In a specific embodiment, memory 1102 is a non-volatile solid-state memory.

[0153] The memory may include read-only memory (ROM), random access memory (RAM), magnetic disk storage media devices, optical storage media devices, flash memory devices, electrical, optical or other physical / tangible memory storage devices. Thus, generally, the memory includes one or more tangible (non-transitory) computer-readable storage media (e.g., memory devices) encoded with software including computer-executable instructions, and when the software is executed (e.g., by one or more processors), it is operable to perform the operations described with reference to the method according to an aspect of the present application.

[0154] The processor 1101 reads and executes computer program instructions stored in the memory 1102 to implement any one of the methods for determining the fallback mobility management entity MME in the foregoing embodiments.

[0155] In one example, the device for determining the fallback mobility management entity MME may further include a communication interface 1103 and a bus 1110. Figure 11 As shown, the processor 1101 , the memory 1102 , and the communication interface 1103 are connected via a bus 1010 and communicate with each other.

[0156] The communication interface 1103 is mainly used to implement communication between various modules, devices, units and / or equipment in the embodiments of the present application.

[0157] Bus 1110 includes hardware, software or both, and the parts of the determination equipment of falling back mobility management entity MME are coupled to each other. For example, and not limitation, bus can include accelerated graphics port (AGP) or other graphics bus, enhanced industry standard architecture (EISA) bus, front side bus (FSB), hypertransport (HT) interconnection, industry standard architecture (ISA) bus, infinite bandwidth interconnection, low pin count (LPC) bus, memory bus, micro channel architecture (MCA) bus, peripheral component interconnection (PCI) bus, PCI-Express (PCI-X) bus, serial advanced technology attachment (SATA) bus, video electronics standard association local (VLB) bus or other suitable bus or two or more of these combinations. In the appropriate case, bus 1110 can include one or more buses. Although the present application embodiment describes and shows specific bus, the application considers any suitable bus or interconnection.

[0158] The fallback mobility management entity MME determination device can verify the connection status of the target MME and the target base station by the verification module, and then execute the fallback mobility management entity MME determination method in the embodiment of the present application, thereby realizing the combination Figure 5 、 Figure 6 、 Figure 7 、 Figure 9 and Figure 10 The invention describes a system, method and device for determining a fallback mobility management entity MME.

[0159] In addition, in conjunction with the method for determining a fallback mobility management entity (MME) in the above embodiments, embodiments of the present application may provide a computer storage medium for implementation. The computer storage medium stores computer program instructions; when the computer program instructions are executed by a processor, the method for determining a fallback mobility management entity (MME) in any of the above embodiments is implemented.

[0160] It should be understood that the present application is not limited to the specific configurations and processes described above and illustrated in the figures. For the sake of brevity, a detailed description of known methods is omitted here. In the above embodiments, several specific steps are described and illustrated as examples. However, the method process of the present application is not limited to the specific steps described and illustrated. Those skilled in the art can make various changes, modifications, and additions, or change the order of the steps after understanding the spirit of the present application.

[0161] The functional blocks shown in the above-described block diagram can be implemented as hardware, software, firmware or a combination thereof. When implemented in hardware, they can be, for example, electronic circuits, application specific integrated circuits (ASICs), appropriate firmware, plug-ins, function cards, etc. When implemented in software, the elements of the present application are programs or code segments that are used to perform the required tasks. The program or code segment can be stored in a machine-readable medium, or transmitted on a transmission medium or a communication link by a data signal carried in a carrier wave. "Machine-readable medium" can include any medium that can store or transmit information. Examples of machine-readable media include electronic circuits, semiconductor memory devices, ROMs, flash memories, erasable ROMs (EROMs), floppy disks, CD-ROMs, optical disks, hard disks, optical fiber media, radio frequency (RF) links, etc. The code segment can be downloaded via a computer network such as the Internet, an intranet, etc.

[0162] It should also be noted that the exemplary embodiments mentioned in this application describe some methods or systems based on a series of steps or devices. However, this application is not limited to the order of the above steps. In other words, the steps can be performed in the order mentioned in the embodiments, or in a different order, or several steps can be performed simultaneously.

[0163] Aspects of the present application have been described above with reference to the flowcharts and / or block diagrams of the methods, devices (systems) and computer program products according to the embodiments of the present application. It should be understood that each box in the flowchart and / or block diagram and the combination of each box in the flowchart and / or block diagram can be implemented by computer program instructions. These computer program instructions can be provided to the processor of a general-purpose computer, a special-purpose computer or other programmable data processing device to produce a machine so that these instructions executed via the processor of the computer or other programmable data processing device enable the implementation of the function / action specified in one or more boxes of the flowchart and / or block diagram. This processor can be, but is not limited to, a general-purpose processor, a special-purpose processor, a special application processor or a field programmable logic circuit. It is also understood that each box in the block diagram and / or the flowchart and the combination of the boxes in the block diagram and / or the flowchart can also be implemented by the dedicated hardware that performs the specified function or action, or can be implemented by the combination of dedicated hardware and computer instructions.

[0164] The above description is only a specific embodiment of the present application. Those skilled in the art will clearly understand that for the convenience and brevity of description, the specific working processes of the systems, modules and units described above can refer to the corresponding processes in the aforementioned method embodiments, and will not be repeated here. It should be understood that the scope of protection of the present application is not limited thereto. Any person skilled in the art can easily think of various equivalent modifications or replacements within the technical scope disclosed in the present application, and these modifications or replacements should be included in the scope of protection of the present application.

Claims

1. A method for determining a fallback mobility management entity MME, characterized in that: A domain name server DNS is applied to a system for determining a fallback mobility management entity MME, wherein the system for determining the fallback mobility management entity MME further includes a first device, wherein the first device is an access and mobility management function AMF or an MME before fallback, and the method includes: Receiving a request message sent by the first device for instructing to query the fallback MME, wherein the request message includes an identity of a target base station; Determining, according to the identity of the target base station, a first MME set corresponding to the identity of the target base station from a pre-acquired MME paging table, wherein the MME paging table includes multiple MMEs, each MME in the MME paging table corresponds to the identity of at least one base station, and each MME in the first MME set and the target base station corresponding to the identity of the target base station are in a connected state; Determine an intersection of the first MME set and the second MME set, and determine the intersection as a third MME set, wherein the second MME set is a set of MMEs determined by Internet Protocol addresses resolved according to a preset domain name resolution rule; The third MME set is sent to the first device, so that the first device determines a target MME for fallback from the third MME set.

2. The method for determining the fallback mobility management entity MME according to claim 1, wherein: Before determining the first MME set corresponding to the identity of the target base station from a pre-acquired MME paging table according to the identity of the target base station, the method further includes: Obtaining information of each MME in an MME pool, where the MME pool includes a plurality of pre-set MMEs, and the information of each MME includes a connection relationship between each MME and at least one base station; Based on the connection relationship between each MME and at least one base station, the MME and the corresponding base station identity in the MME paging table are updated.

3. A method for determining a fallback mobility management entity MME, characterized in that: A first device is applied to a system for determining a fallback mobility management entity MME, the first device being an access and mobility management function AMF or an MME before fallback, the system for determining the fallback mobility management entity MME further comprising a domain name server DNS, and the method comprising: Sending a request message for instructing to query the fallback MME to the DNS, the request message including the identity of the target base station, so that the DNS determines, based on the identity of the target base station, a first MME set corresponding to the identity of the target base station from a pre-acquired MME paging table, and after determining an intersection of the first MME set and a second MME set determined by an Internet Protocol address resolved according to a preset domain name resolution rule as a third MME set, sending the third MME set to the first device; receiving the third MME set sent by the DNS, wherein each MME in the third MME set and the target base station corresponding to the identity of the target base station are in a connected state; Based on a preset selection rule, a target MME for fallback is determined from the third MME set.

4. A device for determining a fallback mobility management entity MME, characterized in that: A domain name server DNS is applied to a system for determining a fallback mobility management entity MME, wherein the system for determining the fallback mobility management entity MME further includes a first device, wherein the first device is an access and mobility management function AMF or an MME before fallback, and the device includes: A receiving module, configured to receive a request message sent by the first device for instructing to query the fallback MME, wherein the request message includes an identity of a target base station; a verification module, configured to determine, based on the identity of the target base station, a first MME set corresponding to the identity of the target base station from a pre-acquired MME paging table, wherein the MME paging table includes a plurality of MMEs, each MME in the MME paging table corresponds to the identity of at least one base station, and each MME in the first MME set and the target base station corresponding to the identity of the target base station are in a connected state; a matching module, configured to determine an intersection of the first MME set and the second MME set, and determine the intersection as a third MME set, wherein the second MME set is a set of MMEs determined by Internet Protocol addresses resolved according to a preset domain name resolution rule; The sending module is configured to send the third MME set to the first device, so that the first device determines a target MME to fall back to from the third MME set.

5. The device for determining a fallback mobility management entity MME according to claim 4, wherein: The device further comprises: an acquisition module, configured to acquire information of each MME in an MME pool, the MME pool including a plurality of pre-set MMEs, the information of each MME including a connection relationship between each MME and at least one base station; The updating module is configured to update the MME and the corresponding base station identity in the MME paging table based on the connection relationship between each MME and at least one base station.

6. A device for determining a fallback mobility management entity MME, characterized in that: A first device applied to a system for determining a fallback mobility management entity MME, the first device being an access and mobility management function AMF or an MME before fallback, the system for determining the fallback mobility management entity MME further comprising a domain name server DNS, the apparatus comprising: a sending module, configured to send request information for instructing to query a fallback MME to the DNS, the request information including an identity of a target base station, so that the DNS determines, based on the identity of the target base station, a first MME set corresponding to the identity of the target base station from a pre-acquired MME paging table, and after determining an intersection of the first MME set and a second MME set determined by an Internet Protocol address resolved according to a preset domain name resolution rule as a third MME set, send the third MME set to the first device; a receiving module, configured to receive the third MME set sent by the DNS, wherein each MME in the third MME set and the target base station corresponding to the identity of the target base station are in a connected state; The determination module is configured to determine a target MME to fall back to from the third MME set based on a preset selection rule.

7. A system for determining a fallback mobility management entity MME, characterized in that: The fallback mobility management entity MME determination system includes a first device, a domain name server DNS and a verification module, the first device is an access and mobility management function AMF or an MME before fallback, and the verification module is connected to the DNS; The first device is configured to send a request message for instructing to query a fallback MME to the DNS, the request message including an identity of a target base station; and further configured to receive a third MME set sent by the DNS, and determine a fallback target MME from the third MME set based on a preset selection rule; The DNS is configured to send the identity of the target base station to the verification module; further configured to determine a second MME set according to an Internet Protocol address resolved according to a preset domain name resolution rule; further configured to receive the first MME set sent by the verification module; further configured to determine an intersection of the first MME set and the second MME set, and determine the intersection as a third MME set; and further configured to send the third MME set to the first device; The verification module is used to determine, based on the identity of the target base station, a first MME set corresponding to the identity of the target base station from a pre-acquired MME paging table, and send the first MME set to the DNS, wherein the MME paging table includes multiple MMEs, each MME in the MME paging table corresponds to the identity of at least one base station, and each MME in the first MME set and the target base station corresponding to the identity of the target base station are in a connected state.

8. A device for determining a fallback mobility management entity MME, characterized in that: The device includes: a processor and a memory storing computer program instructions; When the processor executes the computer program instructions, the method for determining the fallback mobility management entity MME according to any one of claims 1 to 3 is implemented.

9. A computer storage medium, characterized in that The computer storage medium stores computer program instructions, and when the computer program instructions are executed by a processor, the method for determining a fallback mobility management entity MME according to any one of claims 1 to 3 is implemented.

Images