A method, device and equipment for managing circuit domain terminal resources

Abstract

The embodiment of the present application provides a method, device and equipment for managing circuit domain terminal resources. By receiving a first request message sent by a first device, a first clear instruction is sent to a mobile management entity, and then, it is determined whether there is user data corresponding to the identifier of the target user on the second network side. If so, a second clear instruction is sent to the circuit domain terminal, and the second clear instruction is used to instruct the circuit domain terminal to clear the user data. In this way, after sending the first clear instruction to the mobile management entity, when it is determined that there is user data corresponding to the identifier of the target user on the second network side, a second clear instruction is sent to the above-mentioned circuit domain terminal to clear the user data stored on the second network side, which effectively solves the problem of resource waste caused by the long-term invalid occupation of terminal capacity resources.

Description

Technical Field

[0001] The present invention relates to the field of mobile communication technology, and in particular to a method, device and equipment for managing circuit domain terminal resources. Background Art

[0002] Currently, when a user uses a terminal to make a voice call, the 5G SA user terminal will initiate a 2G / 4G joint attachment when initiating EPS Fallback, and the circuit domain terminal (MSS / VLR) side will store the user data.

[0003] However, for 5G users registered on the 5G network, since their service processing process does not interact with MSS / VLR for signaling, a large amount of user data is stored in the circuit domain terminal, causing the above-mentioned circuit domain terminal resources to be ineffectively occupied for a long time, thereby causing the problem of resource waste. Summary of the invention

[0004] The purpose of the embodiments of the present invention is to provide a method, device and equipment for managing circuit domain terminal office resources, so as to solve the technical problem of resource waste caused by long-term invalid occupation of terminal office capacity resources.

[0005] In order to solve the above technical problems, the embodiment of the present invention is implemented as follows:

[0006] In a first aspect, an embodiment of the present invention provides a method for managing circuit domain end office resources, comprising:

[0007] Receiving a first request message sent by a first device, wherein the first request message includes a location update request or a user terminal context management registration request;

[0008] Sending a first clearing instruction to the mobility management entity so that the mobility management entity clears the user data corresponding to the identifier of the target user on the first network side;

[0009] Determine whether there is user data corresponding to the identifier of the target user on the second network side, wherein the communication network corresponding to the first network side and the communication network corresponding to the second network side are communication networks constructed based on different wireless access technologies respectively;

[0010] If yes, a second clearing instruction is sent to the circuit domain end office, where the second clearing instruction is used to instruct the circuit domain end office to clear the user data.

[0011] In a second aspect, an embodiment of the present invention provides a circuit domain terminal office resource management device, including:

[0012] A receiving module, configured to receive a first request message sent by a first device, wherein the first request message includes a location update request or a user terminal context management registration request;

[0013] A sending module, sending a first clearing instruction to the mobility management entity, so that the mobility management entity clears the user data corresponding to the identifier of the target user on the first network side;

[0014] A first judgment module is used to judge whether there is user data corresponding to the identifier of the target user on the second network side, wherein the communication network corresponding to the first network side and the communication network corresponding to the second network side are communication networks constructed based on different wireless access technologies respectively;

[0015] The first processing module is used for sending a second clearing instruction to the circuit domain end office if yes, where the second clearing instruction is used for instructing the circuit domain end office to clear the user data.

[0016] In a third aspect, an embodiment of the present application provides an electronic device, comprising: a processor, a communication interface, a memory and a communication bus; wherein the processor, the communication interface and the memory communicate with each other through the bus; the memory is used to store computer programs; the processor is used to execute the programs stored in the memory, and implement the steps of the circuit domain terminal office resource management method as in the first aspect.

[0017] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, the steps of the method for managing circuit domain terminal resources as described in the first aspect are implemented.

[0018] The method, apparatus and device for managing the resources of the circuit domain terminal office in the embodiment of the present application, by receiving the first request message sent by the first device, sends a first clearing instruction to the mobile management entity, so that the mobile management entity clears the user data corresponding to the identifier of the target user on the first network side, and then determines whether the user data corresponding to the identifier of the target user exists on the second network side. If so, a second clearing instruction is sent to the circuit domain terminal office, and the second clearing instruction is used to instruct the circuit domain terminal office to clear the user data. In this way, after sending the first clearing instruction to the mobile management entity, when it is determined that the user data corresponding to the identifier of the target user exists on the second network side, the second clearing instruction is sent to the above-mentioned circuit domain terminal office to clear the user data stored on the second network side, which effectively solves the problem of resource waste caused by the long-term invalid occupation of the terminal office capacity resources. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments recorded in the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative labor.

[0020] Figure 1 A schematic diagram of a first flow chart of a method for managing circuit domain end office resources provided in an embodiment of the present application;

[0021] Figure 2 A schematic diagram of a first application scenario of the method for managing circuit domain end office resources provided in an embodiment of the present application.

[0022] Figure 3 A schematic diagram of a second application scenario of the method for managing circuit domain end office resources provided in an embodiment of the present application.

[0023] Figure 4 A second flow chart of the method for managing circuit domain end office resources provided in an embodiment of the present application;

[0024] Figure 5 A schematic diagram of the module composition of a circuit domain terminal office resource management device provided in an embodiment of the present application;

[0025] Figure 6 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0026] The method, apparatus and device for managing the resources of the circuit domain terminal office in the embodiment of the present application, by receiving the first request message sent by the first device, sends a first clearing instruction to the mobile management entity, so that the mobile management entity clears the user data corresponding to the identifier of the target user on the first network side, and then determines whether the user data corresponding to the identifier of the target user exists on the second network side. If so, a second clearing instruction is sent to the circuit domain terminal office, and the second clearing instruction is used to instruct the circuit domain terminal office to clear the user data. In this way, after sending the first clearing instruction to the mobile management entity, when it is determined that the user data corresponding to the identifier of the target user exists on the second network side, the second clearing instruction is sent to the above-mentioned circuit domain terminal office to clear the user data stored on the second network side, which effectively solves the problem of resource waste caused by the long-term invalid occupation of the terminal office capacity resources.

[0027] In order to enable those skilled in the art to better understand the technical solutions in the present invention, the technical solutions in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of the present invention.

[0028] At present, according to the existing 5G protocol specifications, the interaction process between 5G terminals and circuit domain terminals (MSS / VLR) includes the following three scenarios.

[0029] The terminal turns on the 5G SA switch: The terminal initiates a registration request to the 5G core network. (1) In the early stage of 5G development, under the IWF+HSS networking solution, AMF initiates a location update request to HSS (Home Subscriber Server) through IWF. (2) In the middle and late stages of 5G development, under the UDM (Unified Data Management) independent networking solution, AMF initiates a location update request to UDM. According to the single domain registration principle, HSS will send a message to MME to instruct MME to delete user data. At the same time, the terminal will send an IMSI_Detach message to the 4G core network. After receiving the message, MME will send an IMSI_Detach_Indication message to MSS (Mobile Switching Subsystemr) / VLR (Visitor Location Register) through the SGs interface, and MSS / VLR will delete the user's SGs association information.

[0030] After the terminal registers with the 5G core network, it makes a call: the terminal initiates a voice service request message to the 5G core network. Since the current 5G core network does not support VO-NR, the terminal is instructed to execute the EPS Fallback process. The terminal initiates an IMSI_Attach request (joint attachment) to the 4G core network. The MME initiates an Sgsap_Location_Update message through the SGs port. The MSS / VLR creates an SGs association relationship with this user under the MME. At the same time, the MSS / VLR initiates a 2G location update process.

[0031] 5G terminal hangs up the call: HSS only instructs MME to delete user data, and does not notify MSS / VLR to clear user data. The terminal does not send IMSI_Detach message to the 4G network, and the MSS / VLR side does not delete the user's SGs association information.

[0032] It is not difficult to see from the above-mentioned interaction process between the 5G terminal and the circuit domain terminal (MSS / VLR) that after the terminal turns on the 5G SA switch and directly registers to the 5G core network, no user data is retained on the MSS / VLR side. However, when the terminal makes a voice call, due to the EPS Fallback of the 5GSA user, a 2G / 4G joint attachment will be initiated, and the MSS / VLR side will store the user data. After the voice call ends (VoLTE) and returns to the 5G network, the HSS / UDM only instructs the 4G core network MME to delete the user data, while the user data on the MSS / VLR side is retained. This results in residual user data on the MSS / VLR side, resulting in the MSS / VLR resources being occupied ineffectively for a long time, thereby causing the problem of resource waste. In order to solve the problem of resource waste caused by the long-term invalid occupation of the terminal capacity resources mentioned above, the embodiments of this specification provide a method, device and equipment for managing circuit domain terminal resources.

[0033] like Figure 1 As shown, an embodiment of the present application provides a method for managing circuit domain terminal resources, and the execution subject of the method can be a server, wherein the server can be an independent server or a server cluster composed of multiple servers, and the server can be a server corresponding to HSS under the IWF (Interworking Function) + HSS (Home Subscriber Server) networking solution in the early stage of 5G development. Alternatively, the above-mentioned server can also be a server corresponding to UDM (Unified Data Management) under the independent networking solution of UDM (Unified Data Management) in the middle and late stages of 5G development. The method can specifically include the following steps:

[0034] In step S102, a first request message sent by a first device is received, wherein the first request message includes a location update request or a user terminal context management registration request.

[0035] As an example, taking the target network corresponding to the target network side as a 5G network, the above-mentioned first device can be the IWF device corresponding to the IWF+HSS networking scenario, or it can also be the AMF device corresponding to the integrated UDM independent networking scenario. The above-mentioned location update request can be a simulated Update-Location-Request request message sent by the IWF device and received by the HSS during the 5G attachment or hang-up stage. The above-mentioned user terminal context management registration request can also be a Nudm_UEContextManagement_Registration message sent by the AMF and received by the UDM during the 5G attachment or hang-up stage.

[0036] In step S104, a first clearing instruction is sent to the mobility management entity, so that the mobility management entity clears the user data corresponding to the identifier of the target user on the first network side.

[0037] As an example, taking the above-mentioned target network as a 5G network, the first network corresponding to the above-mentioned first network side may be a 4G network. Among them, the above-mentioned mobile management entity may be the above-mentioned MME device. The above-mentioned first clearing instruction may be a Cancel-Location-Request message sent by HSS to MME, instructing MME to clear the user data corresponding to the identifier of the target user on the first network side. Alternatively, after UDM / HSS receives the registration request from AMF, it may send a Cancel-Location-Request message to MME, instructing MME to clear the user data corresponding to the identifier of the target user on the first network side.

[0038] In step S106, it is determined whether there is user data corresponding to the identifier of the target user on the second network side, wherein the communication network corresponding to the first network side and the communication network corresponding to the second network side are communication networks constructed based on different wireless access technologies.

[0039] Among them, the second network corresponding to the above-mentioned second network side can be a 2G network.

[0040] In step S108, if yes, a second clearing instruction is sent to the circuit domain end office, where the second clearing instruction is used to instruct the circuit domain end office to clear the user data.

[0041] The second clearing instruction may be a Cancel-Location-Request MAP message sent by the HSS to the circuit domain terminal office, instructing the circuit domain terminal office to clear the user data. Alternatively, the second clearing instruction may be a Cancel-Location-Request MAP message sent by the UDM to the circuit domain terminal office, instructing the circuit domain terminal office to clear the user data.

[0042] The specific implementation of this specification is described in detail below with reference to two specific embodiments in conjunction with the accompanying drawings.

[0043] Embodiment 1:

[0044] In this embodiment, the IWF+HSS networking scenario is taken as an example. Figure 2 As shown:

[0045] Step D1: The UE sends a Registration Request to the AMF via the wireless network;

[0046] Step D2: After AMF completes authentication, it sends a Nudm_UEContextManagement_Registration request to IWF to register the user.

[0047] Step D3: After receiving the registration request from AMF, IWF returns Nudm_UEContextManagement_Registration Response message.

[0048] Step D4: The IWF simulates the CSCF to initiate a Location-Info-Request request to the HSS.

[0049] Step D5: HSS returns a Location-Info-Answer response message.

[0050] Step D6: The IWF sends a simulated Update-Location-Request message to the HSS.

[0051] Step D7: HSS returns an Update-Location-Answer message to the IWF.

[0052] Step D8: HSS sends a Cancel-Location-Request message to MME, instructing the MME to clear user data.

[0053] Step D9: When the HSS determines that the second network side has user data corresponding to the identifier of the target user, it sends a Cancel-Location-Request MAP message to the MSS / VLR to instruct the MSS / VLR to clear the user data.

[0054] Embodiment 2:

[0055] In this embodiment, the UDM independent networking scenario is taken as an example. Figure 3 As shown:

[0056] Step E1: The UE sends a Registration Request to the AMF via the wireless network.

[0057] Step E2: After AMF completes authentication, it sends a Nudm_UEContextManagement_Registration request to UDM / HSS to register the user.

[0058] Step E3: After receiving the registration request from AMF, UDM / HSS sends a Cancel-Location-Request message to MME, instructing the MME to clear the user data.

[0059] Step E4: When the UDM determines that the second network side has user data corresponding to the identifier of the target user, it sends a Cancel-Location-Request MAP message to the MSS, instructing the MSS to clear the user data on the MSS / VLR side.

[0060] It can be seen from the technical solution provided by the above embodiment of the present application that the embodiment of the present application sends a first clearing instruction to the mobile management entity by receiving a first request message sent by the first device, so that the mobile management entity clears the user data corresponding to the identifier of the target user on the first network side, and then determines whether there is user data corresponding to the identifier of the target user on the second network side. If so, a second clearing instruction is sent to the circuit domain terminal office, and the second clearing instruction is used to instruct the circuit domain terminal office to clear the user data. In this way, after sending the first clearing instruction to the mobile management entity, when it is determined that there is user data corresponding to the identifier of the target user on the second network side, a second clearing instruction is sent to the above circuit domain terminal office to clear the user data stored on the second network side, which effectively solves the problem of resource waste caused by the long-term invalid occupation of terminal office capacity resources.

[0061] Further, such as Figure 4 As shown, before determining whether there is user data corresponding to the identifier of the target user on the second network side, the method may further include the processing of the following step S110 , for details, please refer to the specific processing of the following step S110 .

[0062] In step S110, it is determined whether the first request message is a request sent by the target network side, wherein the target network corresponding to the target network side is interoperable with the networks corresponding to the first network side and the second network side, respectively.

[0063] As an example, the above interoperability may be that during a call, due to wireless reasons or terminal device support reasons, the network to which the terminal device is connected may fall back from the 5G network to the 4G network or the 2G network.

[0064] If so, execute the step of determining whether there is user data corresponding to the identifier of the target user on the second network side.

[0065] Among them, the target network corresponding to the above-mentioned target network side can be a 5G network.

[0066] In an optional implementation, as an example, taking the IWF+HSS networking scenario in the above-mentioned embodiment 1 as an example, in step D6, the Update-Location-Request request message received by the HSS may carry one or more of the host name, device type, and IP address information of the IWF device. In this way, in the above-mentioned step D9, the HSS can determine whether the above-mentioned first request message is a request issued by the target network side based on one or more of the host name, device type, and IP address information of the IWF device carried in the received Update-Location-Request request message. If the judgment result is yes, the HSS can execute the processing process of determining whether there is user data corresponding to the identifier of the target user on the second network side.

[0067] In another optional implementation, as an example, taking the independent networking scenario of integrated UDM in the above-mentioned embodiment 2 as an example, in the above-mentioned step E3, the Nudm_UEContextManagement_Registration registration request message received by the UDM may carry one or more of the host name, device type, and IP address information of the above-mentioned AMF device. In this way, in the above-mentioned step E4, the UDM can determine whether the above-mentioned first request message is a request issued by the target network side based on one or more of the host name, device type, and IP address information of the AMF device carried in the received Nudm_UEContextManagement_Registration request message. If the judgment result is yes, the UDM can execute the processing process of determining whether there is user data corresponding to the identifier of the target user on the second network side.

[0068] Furthermore, the first request message carries at least one or more of the host name, device type, and IP address information of the first device.

[0069] Furthermore, the above-mentioned first device includes: an IWF device or an access and mobility management function device.

[0070] Furthermore, the communication network corresponding to the above-mentioned target network side is a 5G network, the communication network corresponding to the above-mentioned first network side is a 4G network, and the communication network corresponding to the above-mentioned second network side is a 2G network.

[0071] It can be seen from the technical solution provided by the above embodiment of the present application that the embodiment of the present application sends a first clearing instruction to the mobile management entity by receiving a first request message sent by the first device, so that the mobile management entity clears the user data corresponding to the identifier of the target user on the first network side, and then determines whether there is user data corresponding to the identifier of the target user on the second network side. If so, a second clearing instruction is sent to the circuit domain terminal office, and the second clearing instruction is used to instruct the circuit domain terminal office to clear the user data. In this way, after sending the first clearing instruction to the mobile management entity, when it is determined that there is user data corresponding to the identifier of the target user on the second network side, a second clearing instruction is sent to the above circuit domain terminal office to clear the user data stored on the second network side, which effectively solves the problem of resource waste caused by the long-term invalid occupation of terminal office capacity resources.

[0072] Corresponding to the method for managing circuit domain end office resources provided in the above embodiment, based on the same technical concept, the embodiment of the present application also provides a device for managing circuit domain end office resources. Figure 5 A schematic diagram of the module composition of a circuit domain terminal office resource management device provided in an embodiment of the present application, wherein the circuit domain terminal office resource management device is used to execute Figures 1 to 4 The management method of the circuit domain terminal resources described in Figure 5 As shown, the circuit domain terminal office resource management device includes:

[0073] The receiving module 501 is configured to receive a first request message sent by a first device, wherein the first request message includes a location update request or a user terminal context management registration request;

[0074] The sending module 502 sends a first clearing instruction to the mobility management entity, so that the mobility management entity clears the user data corresponding to the identifier of the target user on the first network side;

[0075] A first judgment module 503 is used to judge whether there is user data corresponding to the identifier of the target user on the second network side, wherein the communication network corresponding to the first network side and the communication network corresponding to the second network side are communication networks constructed based on different wireless access technologies respectively;

[0076] The first processing module 504 is configured to send a second clearing instruction to the circuit domain end office if yes, where the second clearing instruction is used to instruct the circuit domain end office to clear the user data.

[0077] Optionally, before determining whether the second network side has user data corresponding to the identifier of the target user, the method device further includes:

[0078] A second judgment module is used to judge whether the first request message is a request sent by a target network side, wherein a target network corresponding to the target network side is interoperable with networks corresponding to the first network side and the second network side respectively;

[0079] The second processing module is configured to, if yes, execute the step of determining whether there is user data corresponding to the identifier of the target user on the second network side.

[0080] Optionally, the first request message carries at least one or more of the host name, device type, and IP address information of the first device.

[0081] Optionally, the first device includes: an IWF device or an access and mobility management function device.

[0082] Optionally, the communication network corresponding to the target network side is a 5G network, the communication network corresponding to the first network side is a 4G network, and the communication network corresponding to the second network side is a 2G network.

[0083] It can be seen from the technical solution provided by the above embodiment of the present application that the embodiment of the present application sends a first clearing instruction to the mobile management entity by receiving a first request message sent by the first device, so that the mobile management entity clears the user data corresponding to the identifier of the target user on the first network side, and then determines whether there is user data corresponding to the identifier of the target user on the second network side. If so, a second clearing instruction is sent to the circuit domain terminal office, and the second clearing instruction is used to instruct the circuit domain terminal office to clear the user data. In this way, after sending the first clearing instruction to the mobile management entity, when it is determined that there is user data corresponding to the identifier of the target user on the second network side, a second clearing instruction is sent to the above circuit domain terminal office to clear the user data stored on the second network side, which effectively solves the problem of resource waste caused by the long-term invalid occupation of terminal office capacity resources.

[0084] The circuit domain terminal office resource management device provided in the embodiment of the present application can implement each process in the embodiment corresponding to the circuit domain terminal office resource management method described above, and will not be described again here to avoid repetition.

[0085] It should be noted that the circuit domain terminal office resource management device provided in the embodiment of the present application and the circuit domain terminal office resource management method provided in the embodiment of the present application are based on the same application concept, so the specific implementation of this embodiment can refer to the implementation of the aforementioned circuit domain terminal office resource management method, and the repeated parts will not be repeated.

[0086] Corresponding to the circuit domain terminal office resource management method provided in the above embodiment, based on the same technical concept, the embodiment of the present application also provides an electronic device, which is used to execute the above circuit domain terminal office resource management method. Figure 6 A schematic diagram of the structure of an electronic device for implementing each embodiment of the present application is shown in FIG. Figure 6 As shown, the electronic device may have relatively large differences due to different configurations or performances, and may include one or more processors 601 and memory 602, and the memory 602 may store one or more storage applications or data. Among them, the memory 602 can be a short-term storage or a persistent storage. The application stored in the memory 602 may include one or more modules (not shown in the figure), and each module may include a series of computer executable instructions in the electronic device. Furthermore, the processor 601 can be configured to communicate with the memory 602 to execute a series of computer executable instructions in the memory 602 on the electronic device. The electronic device may also include one or more power supplies 603, one or more wired or wireless network interfaces 604, one or more input and output interfaces 605, and one or more keyboards 606.

[0087] Specifically in this embodiment, the electronic device includes a processor, a communication interface, a memory and a communication bus; wherein the processor, the communication interface and the memory communicate with each other through the bus; the memory is used to store computer programs; the processor is used to execute the programs stored in the memory to implement the following method steps:

[0088] Receiving a first request message sent by a first device, wherein the first request message includes a location update request or a user terminal context management registration request;

[0089] Sending a first clearing instruction to the mobility management entity so that the mobility management entity clears the user data corresponding to the identifier of the target user on the first network side;

[0090] Determine whether there is user data corresponding to the identifier of the target user on the second network side, wherein the communication network corresponding to the first network side and the communication network corresponding to the second network side are communication networks constructed based on different wireless access technologies respectively;

[0091] If yes, a second clearing instruction is sent to the circuit domain end office, where the second clearing instruction is used to instruct the circuit domain end office to clear the user data.

[0092] Optionally, before determining whether there is user data corresponding to the identifier of the target user on the second network side, the method further includes:

[0093] Determining whether the first request message is a request sent by a target network side, wherein a target network corresponding to the target network side is interoperable with networks corresponding to the first network side and the second network side, respectively;

[0094] If so, execute the step of determining whether there is user data corresponding to the identifier of the target user on the second network side.

[0095] Optionally, the first request message carries at least one or more of the host name, device type, and IP address information of the first device.

[0096] Optionally, the first device includes: an IWF device or an access and mobility management function device.

[0097] Optionally, the communication network corresponding to the target network side is a 5G network, the communication network corresponding to the first network side is a 4G network, and the communication network corresponding to the second network side is a 2G network.

[0098] The present application also provides a computer-readable storage medium, in which a computer program is stored. When the computer program is executed by a processor, the following method steps are implemented:

[0099] Receiving a first request message sent by a first device;

[0100] Sending a first clearing instruction to the mobility management entity so that the mobility management entity clears the user data corresponding to the identifier of the target user on the first network side;

[0101] Determine whether there is user data corresponding to the identifier of the target user on the second network side, wherein the communication network corresponding to the first network side and the communication network corresponding to the second network side are communication networks constructed based on different wireless access technologies respectively;

[0102] If yes, a second clearing instruction is sent to the circuit domain end office, where the second clearing instruction is used to instruct the circuit domain end office to clear the user data.

[0103] Optionally, before determining whether there is user data corresponding to the identifier of the target user on the second network side, the method further includes:

[0104] Determining whether the first request message is a request sent by a target network side, wherein a target network corresponding to the target network side is interoperable with networks corresponding to the first network side and the second network side, respectively;

[0105] If so, execute the step of determining whether there is user data corresponding to the identifier of the target user on the second network side.

[0106] Optionally, the first request message carries at least one or more of the host name, device type, and IP address information of the first device.

[0107] Optionally, the first device includes: an IWF device or an access and mobility management function device.

[0108] Optionally, the communication network corresponding to the target network side is a 5G network, the communication network corresponding to the first network side is a 4G network, and the communication network corresponding to the second network side is a 2G network.

[0109] It can be seen from the technical solution provided by the above embodiment of the present application that the embodiment of the present application sends a first clearing instruction to the mobile management entity by receiving a first request message sent by the first device, so that the mobile management entity clears the user data corresponding to the identifier of the target user on the first network side, and then determines whether there is user data corresponding to the identifier of the target user on the second network side. If so, a second clearing instruction is sent to the circuit domain terminal office, and the second clearing instruction is used to instruct the circuit domain terminal office to clear the user data. In this way, after sending the first clearing instruction to the mobile management entity, when it is determined that there is user data corresponding to the identifier of the target user on the second network side, a second clearing instruction is sent to the above circuit domain terminal office to clear the user data stored on the second network side, which effectively solves the problem of resource waste caused by the long-term invalid occupation of terminal office capacity resources.

[0110] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, devices, or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the present application may adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) that contain computer-usable program code.

[0111] The present application is described 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 process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0112] These computer program instructions may also be stored in a computer readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer readable memory produce an article of manufacture including an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1A function specified in one or more boxes.

[0113] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process in the computer or other programmable device. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0114] In a typical configuration, an electronic device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.

[0115] The memory may include non-permanent storage in a computer-readable medium, random access memory (RAM) and / or non-volatile memory in the form of read-only memory (ROM) or flash RAM. The memory is an example of a computer-readable medium.

[0116] Computer readable media include permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information. Information can be computer readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer readable media does not include temporary computer readable media (transitory media), such as modulated data signals and carrier waves.

[0117] It should also be noted that the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, commodity or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, commodity or device. In the absence of more restrictions, the elements defined by the sentence "comprises a ..." do not exclude the existence of other identical elements in the process, method, commodity or device including the elements.

[0118] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, devices or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment or an embodiment combining software and hardware. Moreover, the present application may adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program codes.

[0119] The above are only embodiments of the present application and are not intended to limit the present application. For those skilled in the art, the present application may have various changes and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included within the scope of the claims of the present application.

Claims

1. A method for managing circuit domain end office resources, characterized in that: The method comprises: Receiving a first request message sent by a first device, wherein the first request message includes a location update request or a user terminal context management registration request; Sending a first clearing instruction to a mobility management entity so that the mobility management entity clears user data corresponding to the identifier of the target user on the first network side; Determine whether the first request message is a request sent by the target network side, and if so, determine whether there is user data corresponding to the identifier of the target user on the second network side, wherein the communication network corresponding to the first network side and the communication network corresponding to the second network side are communication networks constructed based on different wireless access technologies, respectively, and the target network corresponding to the target network side has interoperability with the networks corresponding to the first network side and the second network side, respectively; If so, a second clearing instruction is sent to the circuit domain end office, where the second clearing instruction is used to instruct the circuit domain end office to clear the user data.

2. The method according to claim 1, characterized in that: The first request message carries at least one or more of the host name, device type, and IP address information of the first device.

3. The method according to claim 1, characterized in that: The first device includes: an IWF device or an access and mobility management function device.

4. The method according to claim 1, characterized in that: The communication network corresponding to the target network side is a 5G network, the communication network corresponding to the first network side is a 4G network, and the communication network corresponding to the second network side is a 2G network.

5. A circuit domain terminal office resource management device, characterized in that: The device comprises: A receiving module, configured to receive a first request message sent by a first device, wherein the first request message includes a location update request or a user terminal context management registration request; A sending module, sending a first clearing instruction to a mobility management entity, so that the mobility management entity clears user data corresponding to the identifier of the target user on the first network side; A first judgment module is used to judge whether there is user data corresponding to the identifier of the target user on the second network side, wherein the communication network corresponding to the first network side and the communication network corresponding to the second network side are communication networks constructed based on different wireless access technologies respectively; A first processing module, configured to send a second clearing instruction to the circuit domain end office if yes, wherein the second clearing instruction is used to instruct the circuit domain end office to clear the user data; The device also includes: A second judgment module is used to judge whether the first request message is a request sent by a target network side, wherein a target network corresponding to the target network side is interoperable with networks corresponding to the first network side and the second network side respectively; The second processing module is configured to, if yes, execute the step of determining whether there is user data corresponding to the identifier of the target user on the second network side.

6. The device according to claim 5, characterized in that The first request message carries at least one or more of the host name, device type, and IP address information of the first device.

7. An electronic device, characterized in that: It comprises a processor, a communication interface, a memory and a communication bus; wherein the processor, the communication interface and the memory communicate with each other via the bus; the memory is used to store computer programs; the processor is used to execute the programs stored in the memory to implement the steps of the circuit domain terminal office resource management method as described in any one of claims 1 to 4.

8. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps of the method for managing circuit domain end office resources according to any one of claims 1 to 4 are implemented.

Images