Method, network-side device, and system for implementing SGS interface location update

Abstract

The present application provides a method, network-side equipment and system for implementing SGS interface location update. In the method, all 4G base stations whose tracking area code TAC is a first TAC are counted, wherein the first TAC is the TAC to be modified; the TAC of all 4G base stations is modified to a second TAC to trigger all 4G users under the first TAC to perform tracking area location update TAU, thereby implementing SGS interface location update; wherein the second TAC is different from the first TAC. The present application can batch modify the TAC values ​​of 4G base stations in the target TAC area, such as Evolved Node B (ENB), to other TACs, simulating a scenario where a mobile phone terminal moves from one TAC to another, prompting the user to trigger a TAU location update, thereby completing the SGS interface location update.

Description

Technical Field

[0001] The present application relates to the field of core network technology, and in particular to a method, network-side equipment, and system for implementing SGS interface location update. Background Art

[0002] The SGS interface is the interface between the Mobility Management Entity (MME) of a 4G network element and the server of the Mobile Switching Center (MSC) of a 2G / 3G network element. Timely updates of the SGS interface location are crucial to the proper functioning of user equipment (UE) and the user experience. Currently, combined attach and tracking area updating (TAU) rely on user behavior and are not suitable for direct network-side use. Whether periodic TAU location updates can simultaneously perform SGS interface location updates remains to be determined.

[0003] The 3GPP TS23.272 document describes the circuit switched fallback (CSFB) SGS interface location update, calling and calling parties, and short messaging service (SMS) services. However, the description of location update, especially periodic location update, is overly brief. The document states that if a CSFB user does not perform periodic location updates, the MME will clear the relevant connections, place the UE in an implicit shutdown state, and release the CSFB interface connection. The MSC Server will continue to retain user data such as the International Mobile Subscriber Identification Number (IMSI) and Location Area (LA). However, it does not specify whether the MME will notify the MSC Server of the UE's periodic TAU location updates.

[0004] To test whether periodic TAU location updates trigger SGS interface location updates, a test number was cleared from the MSC server but still registered with the MME. The test number was unable to make calls or send text messages, and signaling tracking was performed simultaneously on both the MME and the MSC server. After 200 tests, it was found that although the UE regularly initiated periodic TAU location updates to the MME, the MME did not send SGS interface location updates to the MSC server. This proves that periodic TAU location updates do not trigger SGS interface location updates.

[0005] Therefore, it is currently difficult to implement large-scale SGS interface position updates. Summary of the Invention

[0006] The present application provides a method, network-side device, and system for implementing SGS interface location update, so as to solve the problem of large-scale SGS interface location update requirements.

[0007] In a first aspect, the present application provides a method for implementing an SGS interface location update, which is applied to a network-side device and includes:

[0008] Counting all 4G base stations whose tracking area code (TAC) is a first TAC, where the first TAC is the TAC to be modified;

[0009] The TAC values ​​of all 4G base stations are modified to a second TAC to trigger a Tracking Area Location Update (TAU) for all 4G users under the first TAC, thereby implementing an SGS interface location update. The second TAC is different from the first TAC. This method batch modifies the TAC values ​​of 4G base stations in the target TAC area, such as Evolved Node Bs (ENBs), to other TACs. This simulates a scenario where a mobile terminal moves from one TAC to another, prompting users to trigger a TAU location update, thereby completing an SGS interface location update.

[0010] In a possible implementation, modifying the TACs of all 4G base stations to the second TAC includes:

[0011] The TAC of all the 4G base stations is modified to the second TAC in the same MSC Pool.

[0012] In a possible implementation, modifying the TACs of all 4G base stations to the second TAC includes:

[0013] The TAC of all the 4G base stations is modified to the second TAC in the target MSC Pool, where the target MSC Pool is different from the MSC Pool where the first TAC is located.

[0014] In a possible implementation, after the TACs of all 4G base stations are modified to the second TAC, the method further includes:

[0015] After confirming that the SGS interface is updated, the TAC of all 4G base stations is changed from the second TAC back to the original TAC.

[0016] In a second aspect, the present application provides a network-side device, comprising: a processor; the processor executing the following steps:

[0017] Counting all 4G base stations whose tracking area code (TAC) is a first TAC, where the first TAC is the TAC to be modified;

[0018] The TAC of all 4G base stations is modified to the second TAC to trigger all 4G users under the first TAC to perform tracking area location update TAU to achieve SGS interface location update; wherein, the second TAC is different from the first TAC.

[0019] In a possible implementation, modifying the TACs of all 4G base stations to the second TAC includes:

[0020] The TAC of all the 4G base stations is modified to the second TAC in the same MSC Pool.

[0021] In a possible implementation, modifying the TACs of all 4G base stations to the second TAC includes:

[0022] The TAC of all the 4G base stations is modified to the second TAC in the target MSC Pool, where the target MSC Pool is different from the MSC Pool where the first TAC is located.

[0023] In a possible implementation, after the TACs of all 4G base stations are modified to the second TAC, the method further includes:

[0024] After confirming that the SGS interface is updated, the TAC of all 4G base stations is changed from the second TAC back to the original TAC.

[0025] In a third aspect, the present application provides a chip system for executing any method of the first aspect.

[0026] In a fourth aspect, the present application provides a computer-readable storage medium, in which a computer program is stored. When the computer-readable storage medium is run on a computer, the computer executes the method of the first aspect. BRIEF DESCRIPTION OF THE DRAWINGS

[0027] Figure 1A flowchart of a method for implementing SGS interface location update provided in an embodiment of the present application;

[0028] Figure 2 Screenshot of MME signaling tracing provided for the embodiment of this application;

[0029] Figure 3 This is an application diagram of the embodiment of the present application in scenario 1;

[0030] Figure 4 This is a schematic diagram of a second scenario to be applied in the embodiment of the present application;

[0031] Figure 5 This is a flowchart of an embodiment of the present application applied to scenario 2. DETAILED DESCRIPTION

[0032] The terms used in the implementation section of this application are only used to explain the specific embodiments of this application and are not intended to limit this application.

[0033] At present, regardless of whether the 4G user voice solution is Voice over Long-Term Evolution (VoLTE) or CSFB, forcing all 4G users under TAC to update the SGS interface location has a large number of applications: when the MSC Server fails, there may be a user double registration problem, that is, the user is registered on two MSCServers at the same time, and the user cannot be called. At this time, it is necessary to force the SGS interface location update of the 4G CSFB user to restore the service; when the Base Station Controller (BSC) performs cross-MSC pool (Pool) cutover, the 4G user SGS port location must be updated synchronously, otherwise it will cause 4G CSFB users within the BSC coverage area to be unable to call.

[0034] To this end, the embodiment of the present application provides a method for implementing SGS interface location update, which is applied to network side devices such as base station management devices, network management platform devices, etc., including the following: Figure 1 The method flow shown:

[0035] Step 101: Count all 4G base stations whose Tracking Area Code (TAC) is the first TAC, including all Time Division Duplex (TDD) 4G base stations and Frequency Division Duplex (FDD) 4G base stations. In other words, the 4G base stations counted are TDD and FDD, as long as their TAC is the first TAC. The first TAC is the TAC to be modified.

[0036] Step 102: Modify the TAC of all 4G base stations counted in step 101 to a second TAC to trigger a tracking area location update (TAU) for all 4G users under the first TAC, thereby implementing an SGS interface location update. The first TAC is different from the second TAC.

[0037] When the TAC of a base station is changed to the second TAC, it will be discovered by 4G users under the first TAC. When a 4G user under the first TAC discovers that the base station TAC has changed, it triggers a TAU location update. This is similar to the TAU location update triggered by a user moving from the first TAC area to the second TAC area. Change the TAC of all 4G base stations to the temporary second TAC, observe for 5-10 minutes, and confirm it through signaling tracking on the MME. The MME will report the second TAC and other information to the MSC through the SGS interface location update. Figure 2 In the MME signaling tracking screenshot shown, the MME signaling "Uplink NAS Transport, Tracking area update request" in the wireframe indicates that the uplink signaling has sent a tracking area update request, and the MME signaling "DownLink NAS Transport, Tracking area update accept" indicates that the MME has received a response to the tracking area update. When the user updates the SGS interface location and the 4G base station and MME signaling loads are within the normal range, the TAC of the 4G base station can be changed back to the first TAC. During the process of changing the 4G base station's TAC to the second TAC and then changing the second TAC back to the first TAC, the user's calling and called parties are not affected.

[0038] Furthermore, verification revealed that even after the test number's data was cleared from the MSC server, it remained registered with the MME, rendering it unable to make calls or send text messages. After changing the TAC of the 4G base station where the test number resided to the secondary TAC, the test number's registration data reappeared on the MSC server, indicating that the MME had updated the SGS interface location with the MSC server. This was verified 200 times, with consistent results.

[0039] To issue an SGS interface location update command for all 4G users under a TAC on the MME, the signaling monitoring platform must first retrieve the most recent 4G user details for the TAC. Then, a command must be issued to all MMEs to force a location update. Using an Ericsson MME as an example, the command to force a user location update is: gsh delete_subscriber-imsi XXXX-dettype reattach_required. XXXX is the IMSI of the specific user. However, the MME does not support direct location updates for all 4G users under a specific TAC. It only supports location updates for individual users or users on a specific MSCServer. This requires pre-retrieval of user details from the signaling monitoring platform and batch execution on all MMEs. Furthermore, because retrieving user details, creating scripts, and executing them on the MMEs takes time, the user details executed on the MMEs are often several hours old, making real-time updates impossible. Furthermore, executing hundreds of thousands of scripts on the MMEs significantly consumes MME processing capacity, potentially leading to serious consequences.

[0040] Therefore, the method for implementing SGS interface location update provided by the embodiment of the present application has the advantages of high real-time performance, no risk of MME batch operation of users, no impact on services, and wide applicability.

[0041] The method provided by the present invention is further described below through two application scenario embodiments.

[0042] Scenario 1: When an MSC Server fails, a user double registration problem may occur. That is, the user is registered on two MSC Servers at the same time, and calls to the user cannot be connected. The SGS interface location update of the 4G CSFB user must be forced to restore the service. Figure 3 The process of modifying the TAC of one of the 4G base station Evolved Node B (ENB) under MSC Pool 1 to implement the location update of the 4G user SGS interface is given.

[0043] like Figure 3 As shown, in the case where a user equipment registered under MSC Pool 1 is double-registered, the process of implementing the SGS interface location update includes the following steps.

[0044] Step 301: The TAC of the 4G base station ENB is changed from the first TAC to the second TAC, and the user equipment triggers a TAU location update. The first TAC and the second TAC are in the same MSC Pool.

[0045] The TAC of the 4G base station ENB is modified from the first TAC to the second TAC by the method provided in the embodiment of the present application. Specifically:

[0046] First, all 4G base stations under the first TAC can be counted through network-side devices such as 4G network management devices. In this scenario embodiment, it is necessary to modify the TACs corresponding to all BSCs in the MSC Pool1 where the failed MSC Server is located, that is, it is necessary to update the SGS interface locations of all users under the MSC Pool1. There are multiple BSCs in an MSC Pool, and each BSC corresponds to multiple TACs. If all TACs are modified at once, it may have a huge impact on the network's operational processing and affect the normal operation of the network. Therefore, consider modifying the 4G base stations under all TACs in the MSC Pool in batches. If Figure 3 As shown, there are 7 BSCs in MSCPool1, and each BSC has 3 TACs. The TACs in the MSC Pool are TAC1, TAC2...TAC21. Assume that the modification is divided into four times, for example, the first modification is TAC1-TAC5, the second modification is TAC5-10, the third modification is TAC11-TAC15, and the fourth modification is TAC15-TAC21. Then, during the first modification, the target TAC in this step is TAC1-TAC5, and all 4G base stations under TAC1-TAC5 can be counted through the network-side equipment such as the 4G network management. During the second modification, the target TAC in this step is TAC5-TAC10, and all 4G base stations under TAC5-TAC10 can be counted through the network-side equipment through the network management. Similarly, during the fourth modification, the target TAC in this step is TAC15-TAC21, and all 4G base stations under TAC15-TAC21 can be counted through the network management. In addition, the second modification must be made after the 4G user has updated the SGS interface location and the TAC of the 4G base station has been changed back after the first modification; the third modification must be made after the 4G user has updated the SGS interface location and the TAC of the 4G base station has been changed back after the second modification; the fourth modification must be made after the 4G user has updated the SGS interface location and the TAC of the 4G base station has been changed back after the third modification.

[0047] Next, use network-side devices such as 4G network management devices to modify the TACs of all counted 4G base stations to the second TAC. The second TAC cannot be assigned arbitrarily; it and the target TAC must be in the same MSC Pool, MSC Pool 1. Otherwise, CSFB calls will fail. Assuming the target TACs are TAC1-TAC5, temporarily select a TAC from TAC6-TAC21, such as TAC10, as the second TAC. The TACs of all previously counted 4G base stations under TAC1-TAC5 are modified to TAC10.

[0048] When the second modification is performed, the first TAC is TAC6-TAC10, and the second TAC is any TAC from TAC1-TAC5 and TAC11-TAC21. When the third modification is performed, the first TAC is TAC11-TAC15, and the second TAC is any TAC from TAC1-TAC10 and TAC16-TAC21. When the third modification is performed, the first TAC is TAC16-TAC21, and the second TAC is any TAC from TAC1-TAC15.

[0049] Step 302: 4G user TAU location update. During the first modification, 4G users under TAC1-TAC5 discover that the base station TAC has changed, triggering a TAU location update. During the second modification, 4G users under TAC6-TAC10 discover that the base station TAC has changed, triggering a TAU location update. During the third modification, 4G users under TAC11-TAC15 discover that the base station TAC has changed, triggering a TAU location update. During the fourth modification, 4G users under TAC16-TAC21 discover that the base station TAC has changed, triggering a TAU location update.

[0050] Step 303: MME performs SGS interface location update and reports the second TAC and other information to MSC. Afterwards, MSC sends a location update request to the Home Subscriber Server (HSS), and HSS deletes the previously retained erroneous MSC Server according to the location update request. Afterwards, the TAC is changed to TAC10 for all 4G base stations, and its TAC is changed back to the previous TAC. For example, during the first modification, the 4G base station whose TAC was previously TAC1 is still changed back to TAC1, and the 4G base station whose TAC was previously TAC2 is still changed back to TAC2, and so on, the 4G base station whose TAC was previously TAC5 is still changed back to TAC5. The second modification to the fourth modification is similar, and the 4G base station whose TAC has been modified is changed back to the previous TAC.

[0051] After the four modifications are completed in step 303 and the 4G base station is changed back to the original TAC, all 4G users in MSC Pool 1 have their SGS interface locations updated, solving the double registration problem for all users in the MSC Pool.

[0052] The method provided in this scenario embodiment batch modifies the TAC value of the 4G base station ENB in ​​the target TAC (i.e., the first TAC) area to other TACs in the Pool, simulating the scenario where the mobile terminal moves from one TAC to another TAC, prompting the user to trigger the TAU location update, thereby completing the SGS interface location update.

[0053] Scenario 2: BSC A port cutover scenario. Figure 4 As shown, in the BSC A port cutover scenario, the BSC is cutovered from MSC Pool 2 to MSC Pool 1. Generally, only the data corresponding to the cutover Location Area Code (LAC) / Tracking Area Code (TAC) and MSC Pool 1 is added to the MME, while other LAC / TAC data remains unchanged. In addition, it usually includes:

[0054] Step 41: The MME sets all MSCs in MSC Pool 2 to offline.

[0055] Step 42: The MME issues a command to execute user migration, with the target being MSC Pool 1. In other words, user migration is executed with the target being MSC Pool 1.

[0056] Step 43: The user registered in MSC Pool 2 requests to reattach.

[0057] Step 44: The MME only adds the data for migrating the LAC / TAC to Pool 1. Users in the migrating LAC / TAC are migrated to the Pool 1 MSC, while users in other LAC / TACs are not migrated. Because the LAC / TAC migration adds data pointing to MSC Pool 1, 4G users in the migrating TAC are forced to perform location updates and migrate to MSC Pool 1. However, 4G users in other TACs do not have data pointing to MSC Pool 1 and therefore do not perform location updates and are not migrated.

[0058] Afterwards, all 4G users in the target LAC / TAC perform location updates and migrate to MSC Pool 1. The MME deletes the mapping data between the target LAC / TAC and MSC Pool 2. The MME cancels the MSC offline setting in MSC Pool 2.

[0059] If the MSC in MSC Pool 2 is set to offline, new users will not be able to connect to the 4G network, which will seriously affect the service. Figure 4 The SGS interface location update method in the scenario shown is only suitable for cross-Pool A port cutover scenarios and is not suitable for user MSC dual registration and other scenarios.

[0060] against Figure 4In the scenario shown, when a BSC is cut over across MSC Pools and the location update of the 4G user's SGS port needs to be synchronized, it is assumed that there are 6 BSCs under a certain MSC Pool 2: BSC1, BSC2, ... BSC6, among which BSC3 needs to be cut over across MSC Pools to MSC Pool 1. There are three TACs under BSC3: TAC1-TAC3, where TAC1-TAC3 is the first TAC.

[0061] At this time, the network side device performs the following Figure 5 The processing flow shown is used to implement SGS interface location update.

[0062] Step 501: Count all 4G base stations under TAC1-TAC3. Some of these 4G base stations have TAC1, some have TAC2, and some have TAC3.

[0063] Step 502: The TACs of all 4G base stations counted in step 501 are modified to the second TAC. Regardless of whether the TACs of these 4G base stations are TAC1, TAC2, or TAC3, they are all modified to the second TAC. The second TAC can be a TAC temporarily selected from the TACs in MSC Pool 1. After the SGS interface location of the 4G users in TAC1-TAC3 is updated, the TACs of the changed 4G base stations are restored to their original TACs.

[0064] Changing TAC1-TAC3 to a TAC in MSC Pool 1 creates a new mobile TAU location update environment, enabling 4G users to perform TAU location updates. This in turn triggers the MME to report the second TAC and other information to the MSC via the SGS interface location update, thus implementing the SGS interface location update. All 4G users associated with TAC1-TAC3 are then migrated to MSC Pool 1. Furthermore, if the user performs an SGS interface location update and the 4G base station and MME signaling are within normal ranges, the TACs for all 4G base stations counted in step 501 can be restored.

[0065] Relative to Figure 4 The common practice in the scenario shown, the method for implementing the SGS interface location update provided in the embodiment of the present application, can update the SGS interface location without affecting services and implement BSC A-port cutover. Moreover, the method for implementing the SGS interface location update provided in the embodiment of the present application is not only applicable to cross-Pool A-port cutover scenarios, but also to other scenarios such as user MSC dual registration, and has a wider range of applications.

[0066] The network side device provided in the embodiment of the present application includes a processor, which can execute the above Figure 1-Figure 3 and Figure 5The method for implementing the SGS interface location update in the illustrated embodiment.

[0067] The above-mentioned embodiments of the present application are, firstly, easy to implement and have good real-time performance. TAC can be modified in batches through script instructions on 4G network management equipment. From the actual operation process, 500 4G base stations under one TAC can be modified in about half an hour. After the base station TAC is modified, all users immediately trigger TAU location update and SGS interface location update without any delay. However, it is difficult for the MME to issue instructions to 4G users under the TAC to update the SGS interface location, which includes all users and has poor real-time performance. There is also a considerable risk for the MME to execute large batches of instructions. Secondly, it has a wide range of applicable scenarios and the operation process does not affect the service. Batch modification of the TAC value of 4G base stations ENB in ​​the target TAC area to other TACs can be used for cross-MSC Pool A port cutover and can also be used to solve the problem of users double-registering MSC. Furthermore, when the TAC of the 4G base station is modified to other TACs in the Pool, since the temporary TAC is also a TAC in the Pool, the called and calling services are not affected during the modification process.

[0068] It is understood that some or all of the steps or operations in the above embodiments are merely examples, and the present application embodiments may also perform other operations or variations of various operations. In addition, the various steps may be performed in a different order than those presented in the above embodiments, and it is possible that not all of the operations in the above embodiments need to be performed.

[0069] The present application also provides an electronic device, comprising: one or more processors; a memory; and one or more computer programs, wherein the one or more computer programs are stored in the memory, and the one or more computer programs include instructions, which, when executed by the device, cause the device to execute Figure 1-Figure 3 and Figure 5 The method for implementing the SGS interface location update in the illustrated embodiment.

[0070] The embodiment of the present application also provides a computer-readable storage medium, which stores a computer program, which, when executed on a computer, enables the computer to execute the present application. Figure 1-Figure 3 and Figure 5 The method for implementing the SGS interface location update in the illustrated embodiment.

[0071] The present invention also provides a computer program product, which includes a computer program that, when executed on a computer, enables the computer to execute the present invention. Figure 1-Figure 3 and Figure 5 The method for implementing the SGS interface location update in the illustrated embodiment.

[0072] Those skilled in the art will appreciate that the various units and algorithm steps described in the embodiments disclosed herein can be implemented using a combination of electronic hardware, computer software, and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professionals and technicians can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0073] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0074] In the several embodiments provided in this application, if any function is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, or the part that contributes to the prior art, or the part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions for enabling a computer device (which can be a personal computer, server, or network device, etc.) to execute all or part of the steps of the method described in each embodiment of this application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (Read-Only Memory; hereinafter referred to as: ROM), random access memory (Random Access Memory; hereinafter referred to as: RAM), magnetic disk or optical disk, and other media that can store program code.

[0075] The above description is merely a specific embodiment of the present application. Any person skilled in the art may easily conceive of variations or substitutions within the technical scope disclosed in this application, and such variations or substitutions shall be within the scope of protection of this application. The scope of protection of this application shall be subject to the scope of protection of the claims.

Claims

1. A method for implementing SGS interface location update, characterized in that: Applicable to network-side devices, including: Counting all 4G base stations whose tracking area code (TAC) is a first TAC, where the first TAC is the TAC to be modified; Modifying the TAC of all 4G base stations to a second TAC to trigger a tracking area location update (TAU) for all 4G users under the first TAC, thereby implementing an SGS interface location update; wherein the second TAC is different from the first TAC; Modifying the TACs of all the 4G base stations to the second TAC includes: The TAC of all the 4G base stations is modified to the second TAC in the same mobile switching center pool MSC Pool.

2. The method according to any one of claim 1, characterized in that After the TACs of all the 4G base stations are modified to the second TAC, the method further includes: After confirming that the SGS interface is updated, the TAC of all 4G base stations is changed from the second TAC back to the original TAC.

3. A network side device, characterized in that: include: processor; The processor performs the following steps: Counting all 4G base stations whose tracking area code (TAC) is a first TAC, where the first TAC is the TAC to be modified; Modifying the TAC of all 4G base stations to a second TAC to trigger a tracking area location update (TAU) for all 4G users under the first TAC, thereby implementing an SGS interface location update; wherein the second TAC is different from the first TAC; Modifying the TACs of all the 4G base stations to the second TAC includes: The TAC of all the 4G base stations is modified to the second TAC in the same MSC Pool.

4. The device according to any one of claim 3, characterized in that After the TACs of all the 4G base stations are modified to the second TAC, the method further includes: After confirming that the SGS interface is updated, the TAC of all 4G base stations is changed from the second TAC back to the original TAC.

5. A computer-readable storage medium, characterized in that The computer-readable storage medium stores a computer program, which, when executed on a computer, enables the computer to execute the method according to any one of claims 1 to 2.

Images