Detailed Description
The method, the device and the equipment for managing the circuit domain end office resources in the embodiment of the application send a first clearing instruction to the mobile management entity by receiving a first request message sent by the first equipment so that the mobile management entity clears the user data corresponding to the identification of the target user on the first network side, then judges whether the user data corresponding to the identification of the target user exists on the second network side, if so, sends a second clearing instruction to the circuit domain end office, and the second clearing instruction is used for indicating the circuit domain end office to clear the user data. In this way, after the first clearing instruction is sent to the mobility management entity, the second clearing instruction is sent to the circuit domain end office to clear the user data stored in the second network side under the condition that the second network side has the user data corresponding to the identification of the target user, so that the problem of resource waste caused by the fact that the capacity resource of the end office is not occupied for a long time is effectively solved.
In order to make the technical solution of the present invention better understood by those skilled in the art, the technical solution of the present invention will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present invention, and it is apparent that the described embodiments are only some embodiments of the present invention, not all embodiments. All other embodiments, which can be made by those skilled in the art based on the embodiments of the invention without making any inventive effort, shall fall within the scope of the invention.
Currently, according to the existing 5G protocol specification, the interaction procedure of the 5G terminal related to the circuit domain end office (MSS/VLR) includes the following three scenarios.
The terminal opens a 5G SA switch, wherein the terminal initiates a registration request to a 5G core network, (1) under the IWF+HSS networking scheme in the initial stage of 5G development, the AMF initiates a location update request to HSS (Home Subscriber Server) through the IWF, (2) under the independent networking scheme of UDM (Unified DATA MANAGEMENT) in the middle and later stage of 5G development, the AMF initiates a location update request to UDM, and the HSS instructs the MME to delete user data according to a single domain registration principle. Meanwhile, the terminal sends an IMSI_Detach message to the 4G core network, after receiving the message, the MME sends an IMSI_Detach_indication message to MSS (Mobile Switching Subsystemr)/VLR (Visitor Location Register) through an SGs interface, and the MSS/VLR deletes SGs associated information of the user.
The terminal registers the 5G core network and then calls, namely, the terminal initiates a voice service request message to the 5G core network, and the current 5G core network does not support VO-NR, so the terminal is instructed to execute EPS Fallback flow, the terminal initiates an IMSI_attach request (joint attachment) to the 4G core network, the MME initiates Sgsap _location_update message through an SGs port, MSS/VLR creates an SGs association relationship with the user under the MME, and the MSS/VLR initiates a 2G Location Update flow.
The 5G terminal hangs up, the HSS only instructs the MME to delete the user data, and does not inform the MSS/VLR to clear the user data. The terminal does not send IMSI_Detarch information to the 4G network, and MSS/VLR side does not delete SGs associated information of the user.
From the above-mentioned interactive flow of 5G terminal and circuit domain end office (MSS/VLR), it is easy to see that after the terminal opens the 5G SA switch to register directly to the 5G core network, MSS/VLR side does not have data retention. However, when the terminal performs voice call, 2G/4G joint attachment is initiated when the 5G SA user EPS Fallback is performed, the MSS/VLR side stores user data, after the voice call is finished (VoLTE) returns to the 5G network, the HSS/UDM only instructs the 4G core network MME to delete the user data, and the MSS/VLR side user data is reserved, which results in that the MSS/VLR side retains the user data, resulting in that the MSS/VLR resource is occupied in a long-term invalid, and further, the problem of resource waste is caused. In order to solve the problem of resource waste caused by the fact that the end office capacity resources are occupied in a long-term invalid manner, the embodiment of the specification provides a method, a device and equipment for managing the circuit domain end office resources.
As shown in fig. 1, an embodiment of the present application provides a method for managing circuit domain end office resources, where an execution body of the method may be a server, where the server may be an independent server or may be a server cluster formed by a plurality of servers, and the server may be a server corresponding to an HSS under an IWF (Interworking Function ) + HSS (Home Subscriber Server) networking scheme in an early stage of 5G development. Or the server can also be a server corresponding to the UDM under the independent networking scheme of the UDM (Unified DATA MANAGEMENT) in the middle and later stages of 5G development. The method specifically comprises the following steps:
In step S102, a first request message sent by a first device is received, where the first request message includes a location update request or a user terminal context management registration request.
As an example, taking the target network corresponding to the target network side as a 5G network as an example, the first device may be an IWF device corresponding to an iwf+hss networking scenario, or may also be an AMF device corresponding to a converged UDM independent networking scenario. The above Location Update Request may be an Update-Location-Request message received by the HSS and sent by the IWF device in the 5G attach or attach phase. The above-mentioned user terminal context management Registration request may also be a Nudm _ UEContextManagement _registration message sent by the AMF and received by the UDM in the 5G attach or attach phase.
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.
As an example, taking the target network as a 5G network as an example, the first network corresponding to the first network side may be a 4G network. The mobility management entity may be the MME device. The first clearing instruction may be a Cancel-Location-Request message sent by the HSS to the MME, instructing the MME to clear user data corresponding to the identifier of the target user on the first network side. Or the UDM/HSS sends a Cancel-Location-Request message to the MME after receiving the registration Request of the AMF, and indicates the MME to clear the user data corresponding to the identification of the target user on the first network side.
In step S106, it is determined whether user data corresponding to the identifier of the target user exists on the second network side, where the communication network corresponding to the first network side and the communication network corresponding to the second network side are respectively constructed based on different radio access technologies.
The second network corresponding to the second network side may be a 2G network.
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.
The second clearing instruction may be a Cancel-Location-Request MAP message sent by the HSS to the circuit domain end office, indicating the circuit domain end office to clear the user data. Or the second clearing instruction may be a Cancel-Location-Request MAP message sent by the UDM to the circuit domain end office, indicating the circuit domain end office to clear the user data.
The following describes in detail the embodiments of the present specification with two specific examples in conjunction with the accompanying drawings.
Embodiment one:
In this embodiment, an iwf+hss networking scenario is taken as an example, as shown in fig. 2:
step D1, the UE transmits a registration request Registration Request to an AMF through a wireless network;
and step D2, after the AMF completes authentication, the AMF sends Nudm _ UEContextManagement _registration request to the IWF for registering the user.
Step D3, after the IWF receives the registration request of the AMF, the IWF returns Nudm _ UEContextManagement _ ReGistration Response message.
And D4, the IWF simulation CSCF initiates a Location-Info-Request to the HSS.
And step D5, the HSS returns a Location-Info-Answer response message.
And step D6, the IWF sends a simulated Update-Location-Request message to the HSS.
And D7, the HSS returns an Update-Location-Answer message to the IWF.
And D8, the HSS sends a cancer-Location-Request message to the MME to instruct the MME side to clear the user data.
And step D9, the HSS sends a cancer-Location-Request MAP message to the MSS/VLR to instruct the MSS/VLR side to clear the user data under the condition that the second network side is judged to be the user data corresponding to the identification of the target user.
Embodiment two:
In this embodiment, taking the fusion UDM independent networking scenario as an example, as shown in fig. 3:
step E1, the UE sends the registration request Registration Request to the AMF through the wireless network.
And E2, after the AMF completes authentication, the AMF sends Nudm _ UEContextManagement _registration request to the UDM/HSS to register the user.
And E3, after receiving the registration Request of the AMF, the UDM/HSS sends a cancer-Location-Request message to the MME to instruct the MME side to clear the user data.
And E4, under the condition that the UDM judges that the user data corresponding to the identification of the target user exists at the second network side, sending a cancer-Location-Request MAP message to the MSS, and indicating the MSS to clear the user data at the MSS/VLR side.
As can be seen from the technical solution provided in the above embodiment of the present application, in the embodiment of the present application, a first clearing instruction is sent to a mobility management entity by receiving a first request message sent by a first device, so that the mobility management entity clears user data corresponding to an identifier of a target user on a first network side, then determines whether user data corresponding to the identifier of the target user exists on a second network side, if so, sends a second clearing instruction to a circuit domain end office, where the second clearing instruction is used to instruct the circuit domain end office to clear the user data. In this way, after the first clearing instruction is sent to the mobility management entity, the second clearing instruction is sent to the circuit domain end office to clear the user data stored in the second network side under the condition that the second network side has the user data corresponding to the identification of the target user, so that the problem of resource waste caused by the fact that the capacity resource of the end office is not occupied for a long time is effectively solved.
Further, as shown in fig. 4, before determining whether the second network side has the user data corresponding to the identifier of the target user, the method may further include a processing procedure of step S110, which may be specifically referred to as a specific processing procedure of step S110.
In step S110, it is determined whether the first request message is a request sent by a target network side, where 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.
As an example, the above-mentioned interoperation may be that during a call, a network to which the terminal device is connected may fall back from the 5G network into the 4G network or the 2G network due to wireless reasons or terminal device support reasons.
If yes, executing the step of judging whether the second network side has the user data corresponding to the identification of the target user.
The target network corresponding to the target network side may be a 5G network.
In an alternative implementation manner, taking the iwf+hss networking scenario in the above embodiment one as an example, in step D6, one or more of the hostname, the device type, and the IP address information of the IWF device may be carried in the Update-Location-Request message received by the HSS. In this way, in step D9, the HSS may determine whether the first Request message is a Request sent by the target network side according to one or more of the hostname, the device type, and the IP address information of the IWF device carried in the received Update-Location-Request message, and if so, the HSS may execute a process of determining whether the second network side has user data corresponding to the identifier of the target user.
In another alternative implementation manner, taking the fusion UDM independent networking scenario as an example in the second embodiment, in the step E3, one or more of the hostname, the device type, and the IP address information of the AMF device may be carried in the Nudm _ UEContextManagement _registration request message received by the UDM. Thus, in the above step E4, the UDM may determine whether the first request message is a request sent by the target network side according to one or more of the hostname, the device type, and the IP address information of the AMF device carried in the received Nudm _ UEContextManagement _registration request message, and if so, the UDM may execute a process of determining whether the second network side has user data corresponding to the identifier of the target user.
Further, the first request message at least carries one or more of a hostname, a device type, and IP address information of the first device.
Further, the first device comprises an IWF device or an access and mobility management function device.
Further, 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.
As can be seen from the technical solution provided in the above embodiment of the present application, in the embodiment of the present application, a first clearing instruction is sent to a mobility management entity by receiving a first request message sent by a first device, so that the mobility management entity clears user data corresponding to an identifier of a target user on a first network side, then determines whether user data corresponding to the identifier of the target user exists on a second network side, if so, sends a second clearing instruction to a circuit domain end office, where the second clearing instruction is used to instruct the circuit domain end office to clear the user data. In this way, after the first clearing instruction is sent to the mobility management entity, the second clearing instruction is sent to the circuit domain end office to clear the user data stored in the second network side under the condition that the second network side has the user data corresponding to the identification of the target user, so that the problem of resource waste caused by the fact that the capacity resource of the end office is not occupied for a long time is effectively solved.
The embodiment of the present application further provides a device for managing circuit domain end office resources, based on the same technical concept, where fig. 5 is a schematic diagram of module composition of the device for managing circuit domain end office resources provided by the embodiment of the present application, where the device for managing circuit domain end office resources is used to execute the method for managing circuit domain end office resources described in fig. 1 to 4, as shown in fig. 5, where the device for managing circuit domain end office resources includes:
A receiving module 501, configured to receive a first request message sent by a first device, where the first request message includes a location update request or a user terminal context management registration request;
A sending module 502, configured to send 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;
A first determining module 503, configured to determine whether user data corresponding to the identifier of the target user exists on the second network side, where the communication network corresponding to the first network side and the communication network corresponding to the second network side are respectively constructed based on different radio access technologies;
The first processing module 504 is configured to send, if yes, a second clearing instruction 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.
Optionally, before determining whether the second network side has user data corresponding to the identifier of the target user, the method apparatus further includes:
a second judging module, configured to judge whether the first request message is a request sent by a target network side, where a target network corresponding to the target network side has interoperability with networks corresponding to the first network side and the second network side respectively;
And the second processing module is used for executing the step of judging whether the second network side has the user data corresponding to the identification of the target user if so.
Optionally, the first request message carries at least one or more of a hostname, a device type, and IP address information of the first device.
Optionally, the first device comprises an IWF device or an access and mobility management function device.
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.
As can be seen from the technical solution provided in the above embodiment of the present application, in the embodiment of the present application, a first clearing instruction is sent to a mobility management entity by receiving a first request message sent by a first device, so that the mobility management entity clears user data corresponding to an identifier of a target user on a first network side, then determines whether user data corresponding to the identifier of the target user exists on a second network side, if so, sends a second clearing instruction to a circuit domain end office, where the second clearing instruction is used to instruct the circuit domain end office to clear the user data. In this way, after the first clearing instruction is sent to the mobility management entity, the second clearing instruction is sent to the circuit domain end office to clear the user data stored in the second network side under the condition that the second network side has the user data corresponding to the identification of the target user, so that the problem of resource waste caused by the fact that the capacity resource of the end office is not occupied for a long time is effectively solved.
The device for managing the circuit domain end office resources provided by the embodiment of the application can realize each process in the embodiment corresponding to the method for managing the circuit domain end office resources, and is not repeated here for avoiding repetition.
It should be noted that, the device for managing the circuit domain end office resource provided by the embodiment of the present application and the method for managing the circuit domain end office resource provided by the embodiment of the present application are based on the same application conception, so that the implementation of the embodiment can refer to the implementation of the foregoing method for managing the circuit domain end office resource, and the repetition is omitted.
According to the method for managing the circuit domain end office resource provided in the foregoing embodiments, based on the same technical conception, the embodiment of the present application further provides an electronic device, where the device is configured to execute the method for managing the circuit domain end office resource, fig. 6 is a schematic structural diagram of an electronic device for implementing the embodiments of the present application, and as shown in fig. 6, the electronic device may have relatively large differences due to different configurations or performances, and may include one or more processors 601 and a memory 602, where the memory 602 may store one or more storage applications or data. Wherein the memory 602 may be transient storage or persistent storage. The application programs stored in the memory 602 may include one or more modules (not shown), each of which may include a series of computer-executable instructions for use in an electronic device. Still further, the processor 601 may be arranged to communicate with the memory 602 and execute a series of computer executable instructions in the memory 602 on an 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/output interfaces 605, and one or more keyboards 606.
In this embodiment, the electronic device includes a processor, a communication interface, a memory, and a communication bus, where the processor, the communication interface, and the memory complete communication with each other through the bus, the memory is configured to store a computer program, and the processor is configured to execute the program stored in the memory, to implement the following method steps:
Receiving a first request message sent by first equipment, wherein the first request message comprises a location update request or a user terminal context management registration request;
sending a first clearing instruction to the mobile management entity so that the mobile management entity clears the user data corresponding to the identification of the target user on the first network side;
Judging whether user data corresponding to the identification of the target user exists 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 respectively constructed communication networks based on different wireless access technologies;
if yes, a second clearing instruction is sent to the end office of the circuit domain, and the second clearing instruction is used for indicating the end office of the circuit domain to clear the user data.
Optionally, before determining whether the second network side has user data corresponding to the identifier of the target user, the method further includes:
judging whether the first request message is a request sent by a target network side, wherein the target network corresponding to the target network side has interoperation with networks corresponding to the first network side and the second network side respectively;
if yes, executing the step of judging whether the second network side has the user data corresponding to the identification of the target user.
Optionally, the first request message carries at least one or more of a hostname, a device type, and IP address information of the first device.
Optionally, the first device comprises an IWF device or an access and mobility management function device.
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.
The embodiment of the application also provides a computer readable storage medium, wherein the storage medium stores a computer program, and the computer program realizes the following method steps when being executed by a processor:
receiving a first request message sent by first equipment;
sending a first clearing instruction to the mobile management entity so that the mobile management entity clears the user data corresponding to the identification of the target user on the first network side;
Judging whether user data corresponding to the identification of the target user exists 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 respectively constructed communication networks based on different wireless access technologies;
if yes, a second clearing instruction is sent to the end office of the circuit domain, and the second clearing instruction is used for indicating the end office of the circuit domain to clear the user data.
Optionally, before determining whether the second network side has user data corresponding to the identifier of the target user, the method further includes:
judging whether the first request message is a request sent by a target network side, wherein the target network corresponding to the target network side has interoperation with networks corresponding to the first network side and the second network side respectively;
if yes, executing the step of judging whether the second network side has the user data corresponding to the identification of the target user.
Optionally, the first request message carries at least one or more of a hostname, a device type, and IP address information of the first device.
Optionally, the first device comprises an IWF device or an access and mobility management function device.
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.
As can be seen from the technical solution provided in the above embodiment of the present application, in the embodiment of the present application, a first clearing instruction is sent to a mobility management entity by receiving a first request message sent by a first device, so that the mobility management entity clears user data corresponding to an identifier of a target user on a first network side, then determines whether user data corresponding to the identifier of the target user exists on a second network side, if so, sends a second clearing instruction to a circuit domain end office, where the second clearing instruction is used to instruct the circuit domain end office to clear the user data. In this way, after the first clearing instruction is sent to the mobility management entity, the second clearing instruction is sent to the circuit domain end office to clear the user data stored in the second network side under the condition that the second network side has the user data corresponding to the identification of the target user, so that the problem of resource waste caused by the fact that the capacity resource of the end office is not occupied for a long time is effectively solved.
It will be apparent to those skilled in the art that embodiments of the present application may be provided as a method, apparatus, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the application. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
In one typical configuration, the electronic device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
The memory may include volatile memory in a computer-readable medium, random Access Memory (RAM) and/or nonvolatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of computer-readable media.
Computer readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of storage media for a computer 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 disc read only memory (CD-ROM), digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium, which can be used to store information that can be accessed by a computing device. Computer-readable media, as defined herein, does not include transitory computer-readable media (transmission media), such as modulated data signals and carrier waves.
It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises an element.
It will be apparent to those skilled in the art that embodiments of the present application may be provided as a method, apparatus, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The foregoing is merely exemplary of the present application and is not intended to limit the present application. Various modifications and variations of the present application will be apparent to those skilled in the art. Any modification, equivalent replacement, improvement, etc. which come within the spirit and principles of the application are to be included in the scope of the claims of the present application.