CN117528597A - Network element fault processing method, device, medium and electronic equipment - Google Patents

Network element fault processing method, device, medium and electronic equipment Download PDF

Info

Publication number
CN117528597A
CN117528597A CN202311684604.8A CN202311684604A CN117528597A CN 117528597 A CN117528597 A CN 117528597A CN 202311684604 A CN202311684604 A CN 202311684604A CN 117528597 A CN117528597 A CN 117528597A
Authority
CN
China
Prior art keywords
network element
management function
session management
fault
function network
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202311684604.8A
Other languages
Chinese (zh)
Inventor
陈晓宁
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Beijing Changkun Technology Co ltd
Original Assignee
Beijing Changkun Technology Co ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Beijing Changkun Technology Co ltd filed Critical Beijing Changkun Technology Co ltd
Priority to CN202311684604.8A priority Critical patent/CN117528597A/en
Publication of CN117528597A publication Critical patent/CN117528597A/en
Pending legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/04—Arrangements for maintaining operational condition
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06—Management of faults, events, alarms or notifications
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L43/00—Arrangements for monitoring or testing data switching networks
    • H04L43/10—Active monitoring, e.g. heartbeat, ping or trace-route

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Health & Medical Sciences (AREA)
  • Cardiology (AREA)
  • General Health & Medical Sciences (AREA)
  • Computer And Data Communications (AREA)

Abstract

A network element fault processing method, a device, a medium and electronic equipment relate to the technical field of networks; the stability of the network can be improved. The network element fault processing method comprises the following steps: detecting whether a session management function network element connected with an access mobility management function network element has a fault or not; when the session management function network element has a fault, adding the session management function network element into a fault network element list; according to the fault network element list, releasing network resources associated with the session management function network element in the fault network element list, and stopping releasing when the release amount of the network resources is larger than a preset release rate; and when the release amount is not greater than the release rate, continuing release.

Description

Network element fault processing method, device, medium and electronic equipment
Technical Field
The present disclosure relates to the field of network technologies, and in particular, to a method, an apparatus, a medium, and an electronic device for processing a network element failure.
Background
In the 5G core network, a protocol data unit (protocoldata unit, PDU) session provides data connectivity between the user terminal and the data network, and the user terminal should establish the PDU session before transmitting the data. The access mobility management function (access and mobility management function, AMF) network element and the session management function (session management function, SMF) network element are two main functional units in a PDU session, and network services are completed under the cooperation of a policy control function (policy control function, PCF) network element, a data management function (unifieddata management, UDM) network element, and a network storage function (NF repository function, NRF) network element.
In order to provide network quality of service, the AMF network element needs to maintain normal interactions with the SMF network element. When the PDU session has abnormal problems, the AMF network element can identify whether the PDU session is an SMF network element fault and process the fault. At present, when the 5G core network detects the failure of the SMF network element, all user resources of the corresponding session resources are released. When the session resources and the user resources released at one time are large, a large number of user accesses are easy to be caused, and the network performance is greatly influenced.
Disclosure of Invention
The application provides a network element fault processing method, a device, a medium and electronic equipment, which can improve the stability of network service.
In a first aspect, the present application provides a network element fault handling method, including: detecting whether a session management function network element connected with an access mobility management function network element has a fault or not; when the session management function network element has a fault, adding the session management function network element into a fault network element list; according to the fault network element list, releasing network resources associated with the session management function network element in the fault network element list, and stopping releasing when the release amount of the network resources is larger than a preset release rate; and when the release amount is not greater than the release rate, continuing release.
In an exemplary embodiment, based on the above method, the releasing, according to the faulty network element list, network resources associated with the session management function network element in the faulty network element list includes: and starting a target timer, and releasing network resources associated with the session management function network element in the fault network element list in a timing period of the target timer.
In an exemplary embodiment, based on the above method, after the release amount of the network resource is greater than a preset release rate, the method further includes: determining whether there are unreleased network resources; when unreleased network resources exist in the fault network element list, starting the target timer again; and circularly executing the steps, and deleting the target timer when the network resources associated with each session management function network element in the fault network list are released.
In an exemplary embodiment, based on the above method, the detecting whether a session management function network element connected to the access mobility management function network element has a failure includes: detecting whether the heartbeat of a session management function network element connected with the access mobile management function network element is abnormal, and determining that the session management function network element has faults when the abnormal heartbeat frequency exceeds a preset frequency; and when the session management function network element is detected to restart, determining that the session management function network element has faults.
In an exemplary embodiment, based on the above method, further comprising: acquiring an update session message sent by the session management function network element, wherein the update session message comprises reset time of the session management function network element; comparing the reset time with the initial reset time of the session management function network element, and if the reset time is longer than the initial reset time, determining that the session management function network element is restarted.
In an exemplary embodiment, based on the above method, further comprising: acquiring network element information and response codes sent by the network storage function network element aiming at the access mobile management function network element; when the response code is a first response code, determining whether the network element information is consistent with network element registration information; when the network element information is consistent with the network element registration information, determining whether a session management function network element corresponding to the network element information is registered in the network storage function network element; and when the session management function network element corresponding to the session management function network element information is registered in the network storage function network element, determining that the session management function network element has a fault.
In an exemplary embodiment, based on the above method, the releasing the network resource associated with the session management function network element in the faulty network element list includes: searching a session context ID associated with the session management function network element according to the session management function network element recorded in the fault network element list; releasing the session resources and user resources associated with the session context ID.
When a session management function network element (SMF network element) connected with an access mobile management function network element (hereinafter referred to as AMF network element) fails, the SMF network element is added into a failure network element list, related network resources are released according to the failure network element list, release is stopped when the release amount of the network resources is larger than a preset release rate, and release is continued when the release amount is not larger than the release rate. According to the technical scheme, network resources are released stably according to the preset release rate, the number of users accessing concurrently can be reduced, and the stability and reliability of the network are improved.
In a second aspect, the present application provides a network element fault handling device, including: the fault detection module is used for detecting whether a session management function network element connected with the access mobile management function network element has a fault or not; a fault network element determining module, configured to add the session management function network element to a fault network element list when the session management function network element has a fault; the resource release module is used for releasing network resources associated with the session management function network element in the fault network element list according to the fault network element list, and stopping releasing when the release amount of the network resources is larger than a preset release rate; and when the release amount is not greater than the release rate, continuing release.
In an exemplary embodiment, the resource release module is specifically configured to: and starting a target timer, and releasing network resources associated with the session management function network element in the fault network element list in a timing period of the target timer.
In an exemplary embodiment, the resource release module is further specifically configured to: determining whether there are unreleased network resources; when unreleased network resources exist in the network resources associated with the fault network element list, starting the target timer again; and circularly executing the steps, and deleting the target timer when the network resources associated with each session management function network element in the fault network list are released.
In an exemplary embodiment, the fault detection module specifically includes: the heartbeat detection module is used for detecting whether the heartbeat of the session management function network element connected with the access mobile management function network element is abnormal or not, and determining that the session management function network element has faults when the abnormal heartbeat frequency exceeds a preset frequency; and the restarting detection module is used for determining that the session management function network element has a fault when detecting that the session management function network element is restarted.
In an exemplary embodiment, the restart detection module further includes: a time determining module, configured to obtain an update session message sent by the session management function network element, where the update session message includes a reset time of the session management function network element; and the time comparison module is used for comparing the reset time with the initial reset time of the session management function network element, and if the reset time is larger than the initial reset time, the session management function network element is determined to be restarted.
In an exemplary embodiment, the apparatus further comprises: a response acquisition module, configured to acquire network element information and a response code sent by the network element with the network storage function for the network element with the access mobility management function; the network element information comparison module is used for determining whether the network element information is consistent with the network element registration information when the response code is a first response code; a registration determining module, configured to determine, when the network element information is consistent with the network element registration information, whether a session management function network element corresponding to the network element information is registered in the network storage function network element; and the fault determining module is used for determining that the session management function network element has faults when the session management function network element corresponding to the session management function network element information is registered in the network storage function network element.
In an exemplary embodiment, the resource release module may be specifically configured to: searching a session associated with the session management function network element in the user terminal according to the session management function network element recorded in the fault network element list; releasing session resources of the session.
In a third aspect, the present application provides an electronic device comprising a memory, one or more processors. Wherein the memory has stored therein one or more computer programs, the computer programs comprising instructions which, when executed by the processor, cause the electronic device to perform the network element failure handling method as in the first aspect.
In a fourth aspect, the present application provides a computer readable medium having instructions stored therein which, when run on an electronic device, cause the electronic device to perform a network element failure handling method as in the first aspect.
In a fifth aspect, the present application provides a computer program product which, when run on an electronic device, causes the electronic device to perform the network element failure handling method according to the first aspect.
It may be appreciated that the above-provided network element fault handling apparatus, electronic device, computer readable medium, and computer program product may refer to the advantages of the first aspect, and are not described herein.
Drawings
Fig. 1 is a flow chart of a network element fault handling method provided in an embodiment of the present application;
fig. 2 is a schematic structural diagram of a network element fault handling device provided in an embodiment of the present application;
fig. 3 is a schematic structural diagram of an electronic device according to an embodiment of the present application.
Detailed Description
In order to clearly describe the technical solutions of the embodiments of the present application, in the embodiments of the present application, the words "first", "second", etc. are used to distinguish the same item or similar items having substantially the same function and effect. For example, the first chip and the second chip are merely for distinguishing different chips, and the order of the different chips is not limited. It will be appreciated by those of skill in the art that the words "first," "second," and the like do not limit the amount and order of execution, and that the words "first," "second," and the like do not necessarily differ. It should be noted that, in the embodiments of the present application, words such as "exemplary" or "such as" are used to mean serving as an example, instance, or illustration. Any embodiment or design described herein as "exemplary" or "for example" should not be construed as preferred or advantageous over other embodiments or designs. Rather, the use of words such as "exemplary" or "such as" is intended to present related concepts in a concrete fashion. In the embodiments of the present application, "at least one" means one or more, and "a plurality" means two or more.
The term "at … …" in the embodiment of the present application may be instantaneous when a certain situation occurs, or may be a period of time after a certain situation occurs, which is not particularly limited in the embodiment of the present application.
The implementation of the present embodiment will be described in detail below with reference to the accompanying drawings.
Fig. 1 shows a flow chart of a network element fault handling method provided in an embodiment of the present application. The network element fault processing method can be applied to various electronic devices such as computers, tablet computers, notebook computers, virtual reality/augmented reality devices, wearable devices and the like, and can also be applied to servers, cloud ends, server clusters and the like, and the implementation mode is not limited in particular.
As shown in fig. 1, the network element fault handling method may include the following steps:
step S101: detecting whether a session management function network element connected with an access mobility management function network element has a fault or not;
step S102: when the session management function network element has a fault, adding the session management function network element into a fault network element list;
step S103: according to the fault network element list, releasing network resources associated with the session management function network element in the fault network element list, and stopping releasing when the release amount of the network resources is larger than a preset release rate; and when the release amount is not greater than the release rate, continuing release.
When a large amount of network resources are released at one time, a large amount of users are likely to access the network concurrently, and the network performance is greatly affected by the large concurrency, so that the risk is brought to the safe operation of the network. The technical scheme of the embodiment controls the release amount of the network resources through the release rate, and releases the network resources smoothly, so that the number of concurrent users is controlled within a certain degree, the concurrency amount is more stable, and the risk of safe operation of the network is reduced.
Specifically, in step S101, the User Equipment (UE) needs to first create a PDU session in order to connect to a Data Network (DN). The UE may send a session establishment request to the AMF, including parameters such as user ID, data network name (data network name, DNN), network slice selection assistance information (single network slice selection assistance information, S-NSSAI), data network access identity, etc.
After the AMF receives the request, the AMF may select a locally configured SMF, or match the locally cached SMF based on parameters including DNN, S-NSSAI, etc. included in the request, and if there is an SMF matching the request, send a request to create a session context to the matching SMF. If there is no result in the locally cached SMF that matches the request, the AMF may determine the corresponding SMF through the NRF.
The AMF may send a request for discovering the SMF to the NRF, and the NRF may query the SMF according to parameters carried in the request, and return SMF information to the AMF after the NRF selects an appropriate SMF. The AMF may send a request to establish PDU session message to the selected SMF. Parameters such as DNN, session ID, service AMF ID, request type, user location, etc. may be included in the message. After receiving the request, the corresponding SMF may reply a message to the AMF, indicating the session establishment result. If the establishment is successful, the ID information of the session context is returned to the AMF. And if the establishment fails, returning a corresponding response code according to the rejection reason.
The following describes the failure cases in both cases of success and failure of the SMF creation session.
When creating PDU session, SMF network element creates session successfully, the session establishment result returned to AMF network element includes context ID and reset time (recovery time), and the reset time is called initial reset time. After the UPF network element returns the first downlink data to the UE or the interface between the UPF network element and the SMF network element is modified, the SMF network element sends an update session message to the AMF network element, where the update session message refers to an update session context message, and the update session context message also includes a reset time parameter.
Specifically, an update session message sent by an SMF network element is obtained, wherein the update session message comprises reset time of the SMF network element; comparing the reset time with the initial reset time of the SMF network element, and if the reset time is longer than the initial reset time, determining that the SMF network element is restarted.
When the SMF network element fails to create the session, the network element information of the SMF network element corresponding to the AMF and the response code of the SMF network element are returned to the NRF. Specifically, acquiring network element information and response codes sent by a network element with a network storage function aiming at an access mobile management function; when the response code is the first response code, determining whether the network element information is consistent with the network element registration information; when the network element information is consistent with the network element registration information, determining whether a session management function network element corresponding to the network element information is registered in a network storage function network element; and when the session management function network element corresponding to the session management function network element information is registered in the network storage function network element, determining that the session management function network element has a fault.
For example, the response code may be "403", "400", or the like. When the response code is a first response code, the first response code is used to instruct the SMF to prohibit connection. When the SMF network element corresponding to the AMF network element returns the first response code, determining whether the network element information is consistent with the network element registration information stored in the NRF. And if so, determining whether the SMF network element corresponding to the network element information is registered in the NRF. For example, whether the SMF is registered in the NRF may be determined by a heartbeat between the NRF and the SMF, and if the heartbeat between the NRF and the SMF is normal, the SMF is determined to be registered on the NRF. Or, checking a connection state between the SMF and the NRF on the configuration environment, and determining that the SMF is registered on the NRF if the connection state is normal.
When the network element information of the SMF network element is consistent with the network element registration information in the NRF and it is determined that the SMF network element is registered in the NRF, it may be determined that the current SMF has a fault. Otherwise, the current SMF has no fault.
After the SMF is successfully registered on the NRF, the NRF can detect whether the heartbeat of the SMF network element is abnormal, and when the abnormal heartbeat frequency exceeds the preset frequency, the NRF can send a state change notification of the SMF to the AMF, and after the AMF receives the message, the SMF network element is determined to have faults; and when the AMF detects that the SMF network element connected with the AMF network element is restarted, determining that the SMF network element has a fault.
For example, if the NRF does not receive the heartbeat signal of the SMF network element within a preset period of time, it may determine that the SMF network element is abnormal in heartbeat. When the number of times of heartbeat abnormality of the SMF network element exceeds the preset number of times, the AMF receives the SMF state change notification sent by the NRF, and the SMF network element can be determined to have faults. When the reset time of the SMF network element is longer than the initial reset time, it may be determined that there is a restart of the SMF network element, that is, that the SMF network element fails.
In step S102, when a failed SMF is detected, it may be sequentially added to the failed network element list. Specifically, information such as a network element type, a network element ID, a failure occurrence time, and the like of the SMF network element may be recorded in the failure network element list.
In step S103, according to the information of the SMF network element stored in the failure network element list, the network resource associated with the SMF network element is released. Specifically, according to the SMF network element recorded in the fault network element list, searching the session ID associated with the SMF network element in the user terminal, and releasing the corresponding network resource.
The network resources may include session resources and may also include user resources. An SMF network element that will have a failure may be referred to as a failed SMF network element. According to the information of the failed SMF network element recorded in the failed network list, such as network element ID, etc., the session ID of the session associated with the network element ID of the user terminal can be queried, the session resource associated with the session ID is released, and when the user terminal has no session resource, the user resource is released at the same time.
For example, each time a preset number of network resources are released, it may be determined whether the number of released network resources within the period of time is within a preset release rate, and if the number of released network resources is within the release rate, network resources associated with the failed SMF network element that is not released in the failed network element list are continuously released.
In an exemplary embodiment, when network resources associated with a failed SMF network element are released, a timer (i.e., a target timer) may be started, and network resources associated with the failed SMF network element in the failed network element list are released within a timing period of the target timer. And adding 1 to the release amount every time one network resource is released, then determining whether the release amount is larger than the preset release rate, if not, continuing to release the next network resource, and so on until the timing time period of the target timer is reached or the release amount is larger than the preset release rate.
Illustratively, the AMF network element may establish a user context according to a registration request of the user terminal, where the user context may include information such as an ID of the user, a location of the user, a slice, and the like. The AMF network element applies for the session resource ID according to the session ID carried by the session creation request of the user terminal, and requests the SMF to generate SM context, and the AMF stores the session ID and the session refresh time in the user context.
A time period can be set through the target timer, when the target timer is started, the target timer is scanned sequentially according to the sequence of the user context, after session IDs in the user context are associated with session resource IDs, the session resource IDs can be associated with SMF IDs for creating sessions, and if the SMF IDs are matched with network element IDs in a fault network element list, and the fault occurrence time of the SMFs is longer than the session refreshing time in the user context, session resources related to the session IDs are released; and if the user terminal does not have other session resources, releasing the user resources at the same time. Each time one network resource is released, the release amount is increased by 1, and when the release amount is greater than a preset release rate, or when a timing period set in the target timer has arrived, scanning and release are stopped.
Illustratively, a user context of a user terminal currently connected to the network is obtained, and a user queue is obtained. When the target timer is started, the whole user queue is scanned from the user context pointed by the current scanning cursor, and if the session resource carried by the user is associated with the fault SMF, the session resource is released. And, the number of released users is increased by 1, and the scanning cursor moves to the next user context. Wherein the scan cursor initially points to the first user context in the user queue.
The embodiment further includes: when the release amount of the network resources is larger than a preset release rate or the timing period arrives, determining whether unreleased network resources exist; when unreleased network resources exist in the session associated with the fault network element list, starting the target timer again; and circularly executing the steps, and deleting the target timer when each network resource associated with the session management function network element in the fault network element list in the user queue is released.
After the target timer is started, the user context is scanned sequentially according to the user queue, and whether the SMF ID associated with the user session is the session ID of the failed SMF network element or not is determined. And scanning each failed SMF network element in turn according to the sequence of each failed SMF network element in the failed network element list, judging whether the SMF ID associated with each session of the user is in the failed network element list, and if so, releasing the session resources before the session refreshing time is before the SMF failure time. And stopping scanning and releasing when the timing time period of the target timer reaches or the release amount is larger than the preset rate. And determining whether the last user in the user queue is currently scanned, if the current scanning cursor points to the last user context in the user queue, ending the release, deleting the target timer, and emptying the fault network element list.
If the current scanning cursor points to a user which is not the last user when the timing time period reaches or the release amount is larger than the preset rate, starting the target timer again, and cycling the steps until the last user is scanned.
In this embodiment, by setting the timer, the release speed can be controlled, so that the network resources are cyclically released at a certain speed until the network resources are released, which can reduce the unstable condition of the released network resources and enhance the network stability.
Further, the embodiment also provides a network fault processing device, which can be used for executing the network fault processing method. As shown in fig. 2, the network failure processing apparatus 200 may include: a fault detection module 201, configured to detect whether a session management function network element connected to an access mobility management function network element has a fault; a failure network element determining module 202, configured to add the session management function network element to a failure network element list when the session management function network element has a failure; a resource release module 203, configured to release, according to the faulty network element list, network resources associated with the session management function network element in the faulty network element list, and stop release when the release amount of the network resources is greater than a preset release rate; and when the release amount is not greater than the release rate, continuing release.
In an exemplary embodiment, the resource release module 203 is specifically configured to: and starting a target timer, and releasing network resources associated with the session management function network element in the fault network element list in a timing period of the target timer.
In an exemplary embodiment, the resource release module 203 is further specifically configured to: determining whether there are unreleased network resources; when unreleased network resources exist in the network resources associated with the fault network element list, starting the target timer again; and circularly executing the steps, and deleting the target timer when the network resources associated with each session management function network element in the fault network list are released.
In an exemplary embodiment, the fault detection module 201 specifically includes: the heartbeat detection module is used for detecting whether the heartbeat of the session management function network element connected with the access mobile management function network element is abnormal or not, and determining that the session management function network element has faults when the abnormal heartbeat frequency exceeds a preset frequency; and the restarting detection module is used for determining that the session management function network element has a fault when detecting that the session management function network element is restarted.
In an exemplary embodiment, the restart detection module further includes: a time determining module, configured to obtain an update session message sent by the session management function network element, where the update session message includes a reset time of the session management function network element; and the time comparison module is used for comparing the reset time with the initial reset time of the session management function network element, and if the reset time is larger than the initial reset time, the session management function network element is determined to be restarted.
In an exemplary embodiment, the apparatus 200 further comprises: a response acquisition module, configured to acquire network element information and a response code sent by the network element with the network storage function for the network element with the access mobility management function; the network element information comparison module is used for determining whether the network element information is consistent with the network element registration information when the response code is a first response code; a registration determining module, configured to determine, when the network element information is consistent with the network element registration information, whether a session management function network element corresponding to the network element information is registered in the network storage function network element; and the fault determining module is used for determining that the session management function network element has faults when the session management function network element corresponding to the session management function network element information is registered in the network storage function network element.
In an exemplary embodiment, the resource release module 203 may be specifically configured to: searching a session associated with the session management function network element according to the session management function network element recorded in the fault network element list; releasing the session resources associated with the session.
The specific details of each module or unit in the above network element fault handling device are described in detail in the corresponding network element fault handling method, so that details are not repeated here.
The embodiment of the application also provides electronic equipment, and fig. 3 shows a schematic structural diagram of the electronic equipment suitable for implementing the embodiment of the disclosure. The electronic device 300 shown in fig. 3 is only one example and should not be construed as limiting the functionality and scope of use of the disclosed embodiments.
As shown in fig. 3, the electronic device 300 includes a Central Processing Unit (CPU) 301 that can perform various appropriate actions and processes according to a program stored in a Read Only Memory (ROM) 302 or a program loaded from a storage section 308 into a Random Access Memory (RAM) 303. In the RAM303, various programs and data required for the system operation are also stored. The CPU 301, ROM 302, and RAM303 are connected to each other through a bus 304. An input/output (I/O) interface 305 is also connected to bus 304.
The following components are connected to the I/O interface 305: an input section 306 including a keyboard, a mouse, and the like; an output portion 307 including a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), and the like, a speaker, and the like; a storage section 308 including a hard disk or the like; and a communication section 309 including a network interface card such as a LAN card, a modem, or the like. The communication section 309 performs communication processing via a network such as the internet. The drive 310 is also connected to the I/O interface 305 as needed. A removable medium 311 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is installed on the drive 310 as needed, so that a computer program read therefrom is installed into the storage section 308 as needed.
In particular, according to embodiments of the present disclosure, the processes described above with reference to flowcharts may be implemented as computer software programs. For example, embodiments of the present disclosure include a computer program product comprising a computer program embodied on a computer readable medium, the computer program comprising program code for performing the method shown in the flowcharts. In such an embodiment, the computer program may be downloaded and installed from a network via the communication portion 309, and/or installed from the removable medium 311. The above-described functions defined in the embodiments of the present application are performed when the computer program is executed by a Central Processing Unit (CPU) 301.
For example, the computer program, when executed by the Central Processing Unit (CPU) 301, may perform the following: detecting whether a session management function network element connected with an access mobility management function network element has a fault or not; when the session management function network element has a fault, adding the session management function network element into a fault network element list; according to the fault network element list, releasing network resources associated with the session management function network element in the fault network element list, and stopping releasing when the release amount of the network resources is larger than a preset release rate; and when the release amount is not greater than the release rate, continuing release.
It should be noted that the computer readable medium shown in the present disclosure may be a computer readable signal medium or a computer readable storage medium, or any combination of the two. The computer readable storage medium can be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or a combination of any of the foregoing. More specific examples of the computer-readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the context of this disclosure, a computer-readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In the present disclosure, however, the computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, with the computer-readable program code embodied therein. Such a propagated data signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination of the foregoing. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: wireless, wire, fiber optic cable, RF, etc., or any suitable combination of the foregoing.
The flowcharts and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams or flowchart illustration, and combinations of blocks in the block diagrams or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
The units involved in the embodiments of the present disclosure may be implemented by means of software, or may be implemented by means of hardware, and the described units may also be provided in a processor. Wherein the names of the units do not constitute a limitation of the units themselves in some cases.
As another aspect, the present application also provides a computer-readable medium that may be contained in the electronic device described in the above embodiment; or may exist alone without being incorporated into the electronic device. The computer readable medium carries one or more programs comprising instructions which, when executed by an electronic device, cause the electronic device to implement the methods described in the above embodiments.
It should be noted that although in the above detailed description several modules or units of a device for action execution are mentioned, such a division is not mandatory. Indeed, the features and functions of two or more modules or units described above may be embodied in one module or unit, in accordance with embodiments of the present application. Conversely, the features and functions of one module or unit described above may be further divided into a plurality of modules or units to be embodied.
The foregoing is merely a specific embodiment of the present application, but the scope of the present application is not limited thereto, and any changes or substitutions within the technical scope of the present disclosure should be covered in the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims (10)

1. A method for handling network element failures, comprising:
detecting whether a session management function network element connected with an access mobility management function network element has a fault or not;
when the session management function network element has a fault, adding the session management function network element into a fault network element list;
according to the fault network element list, releasing network resources associated with the session management function network element in the fault network element list, and stopping releasing when the release amount of the network resources is larger than a preset release rate; and when the release amount is not greater than the release rate, continuing release.
2. The network element failure handling method according to claim 1, wherein said releasing network resources associated with said session management function network element in said failed network element list according to said failed network element list comprises:
and starting a target timer, and releasing network resources associated with the session management function network element in the fault network element list in a timing period of the target timer.
3. The network failure handling method of claim 2, further comprising:
when the release amount of the network resources is larger than a preset release rate or the timing period arrives, determining whether unreleased network resources exist;
starting the target timer again when unreleased network resources exist in the network resources associated with the fault network element list;
and circularly executing the steps, and deleting the target timer when the network resources associated with each session management function network element in the fault network list are released.
4. The network failure handling method according to claim 1, wherein detecting whether a session management function network element connected to an access mobility management function network element has a failure comprises:
detecting whether the heartbeat of a session management function network element connected with the access mobile management function network element is abnormal, and determining that the session management function network element has faults when the abnormal heartbeat frequency exceeds a preset frequency;
and when the session management function network element is detected to restart, determining that the session management function network element has faults.
5. The network failure handling method of claim 4, further comprising:
acquiring an update session message sent by the session management function network element, wherein the update session message comprises reset time of the session management function network element;
comparing the reset time with the initial reset time of the session management function network element, and if the reset time is longer than the initial reset time, determining that the session management function network element is restarted.
6. The network failure handling method of claim 4, further comprising:
acquiring network element information and response codes sent by the network storage function network element aiming at the access mobile management function network element;
when the response code is a first response code, determining whether the network element information is consistent with network element registration information;
when the network element information is consistent with the network element registration information, determining whether a session management function network element corresponding to the network element information is registered in the network storage function network element;
and when the session management function network element corresponding to the session management function network element information is registered in the network storage function network element, determining that the session management function network element has a fault.
7. The network failure handling method according to claim 1, wherein the releasing network resources associated with the session management function network element in the failed network element list comprises:
and searching a session associated with the session management function network element in the user terminal according to the session management function network element recorded in the fault network element list, and releasing session resources of the session.
8. A network element failure handling apparatus, comprising:
the fault detection module is used for detecting whether a session management function network element connected with the access mobile management function network element has a fault or not;
a fault network element determining module, configured to add the session management function network element to a fault network element list when the session management function network element has a fault;
the resource release module is used for releasing network resources associated with the session management function network element in the fault network element list according to the fault network element list, and stopping releasing when the release amount of the network resources is larger than a preset release rate; and when the release amount is not greater than the release rate, continuing release.
9. A computer readable medium having instructions stored therein, which when run on an electronic device, cause the electronic device to perform the network element failure handling method of any of claims 1-7.
10. An electronic device comprising a processor and a memory, the memory having stored therein one or more computer programs, the one or more computer programs comprising instructions, which when executed by the electronic device, cause the electronic device to perform the network element failure handling method of any of claims 1-7.
CN202311684604.8A 2023-12-08 2023-12-08 Network element fault processing method, device, medium and electronic equipment Pending CN117528597A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202311684604.8A CN117528597A (en) 2023-12-08 2023-12-08 Network element fault processing method, device, medium and electronic equipment

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202311684604.8A CN117528597A (en) 2023-12-08 2023-12-08 Network element fault processing method, device, medium and electronic equipment

Publications (1)

Publication Number Publication Date
CN117528597A true CN117528597A (en) 2024-02-06

Family

ID=89749413

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202311684604.8A Pending CN117528597A (en) 2023-12-08 2023-12-08 Network element fault processing method, device, medium and electronic equipment

Country Status (1)

Country Link
CN (1) CN117528597A (en)

Similar Documents

Publication Publication Date Title
US11539579B2 (en) Method and apparatus for detection of network function failure and restart in a network environment
US20170163479A1 (en) Method, Device and System of Renewing Terminal Configuration In a Memcached System
US20170331674A1 (en) Method and Apparatus for Controlling Database Connection
CN111176803B (en) Service processing method, device, server and storage medium
US20190158626A1 (en) Method, apparatus and computer readable storage medium for processing service
CN113407383B (en) Main and standby system switching method and device, server and main and standby system
CN111181765A (en) Task processing method and device
WO2016116013A1 (en) Software upgrade method and system
CN105373563B (en) Database switching method and device
CN109828830B (en) Method and apparatus for managing containers
US20170270031A1 (en) Information processing apparatus, test execution method, and computer-readable recording medium
CN109948332A (en) A kind of physical machine login password remapping method and device
CN111506388B (en) Container performance detection method, container management platform and computer storage medium
CN111147585B (en) Equipment upgrading method, device, storage medium and system
WO2023071999A1 (en) User matching method and apparatus, and device and storage medium
US20150205675A1 (en) Method and System for Improving Reliability of a Background Page
CN111092956A (en) Resource synchronization method, device, storage medium and equipment
CN117528597A (en) Network element fault processing method, device, medium and electronic equipment
CN114610446B (en) Method, device and system for automatically injecting probe
CN115640169A (en) Method, system, device and storage medium for ensuring that a master cluster stops providing services
CN113296911B (en) Cluster calling method, cluster calling device, electronic equipment and readable storage medium
CN111885169B (en) Method, system and device for realizing high availability of cloud hard disk service
CN109101253B (en) Management method and device for host in cloud computing system
CN114844910B (en) Data transmission method, system, equipment and medium of distributed storage system
CN116347467B (en) Method and system for managing user data by UDR in 5G network

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination