[go: up one dir, main page]

WO2025092592A1 - 网络分析方法和装置 - Google Patents

网络分析方法和装置 Download PDF

Info

Publication number
WO2025092592A1
WO2025092592A1 PCT/CN2024/127346 CN2024127346W WO2025092592A1 WO 2025092592 A1 WO2025092592 A1 WO 2025092592A1 CN 2024127346 W CN2024127346 W CN 2024127346W WO 2025092592 A1 WO2025092592 A1 WO 2025092592A1
Authority
WO
WIPO (PCT)
Prior art keywords
network
signaling
network element
request
indicate
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
PCT/CN2024/127346
Other languages
English (en)
French (fr)
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.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies 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 Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Publication of WO2025092592A1 publication Critical patent/WO2025092592A1/zh
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • 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/14—Network analysis or design
    • H04L41/147—Network analysis or design for predicting network behaviour
    • 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/06—Generation of reports
    • 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/08—Monitoring or testing based on specific metrics, e.g. QoS, energy consumption or environmental parameters
    • H04L43/0876—Network utilisation, e.g. volume of load or congestion level
    • 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/16—Threshold monitoring

Definitions

  • the present application relates to the field of communication technology, and more specifically, to a network analysis method and device.
  • Signaling storm refers to the situation where the signaling requests received by the network system from terminal devices exceed the signaling processing capacity of the network system, causing network congestion or even avalanche effect, resulting in network unavailability.
  • the present application provides a network analysis method and device, which can predict the occurrence of signaling storms.
  • the method includes: the first device receives a first request from a second device, the first request is used to request the first device to determine whether there is a signaling storm event, the signaling storm event is used to indicate that the network has a risk of a signaling storm; the first device obtains a network threshold, the network threshold is used to indicate the number of signaling that the network can support; the first device determines a first report based on the network threshold and the current number of signaling of the network, the first report is used to indicate the existence of the signaling storm event.
  • the first device may be a service provider (service producer) of a management data analytics service (MDAS), or the first device may be a management data analytics function (MDAF).
  • service producer service provider
  • MDAF management data analytics function
  • the first device can determine that the network has the risk of a signaling storm according to the signaling quantity that the network can support and the current signaling quantity of the network, thereby being able to predict the occurrence of a signaling storm.
  • the first report includes at least one of abnormal network element information, type information, cause information, ratio information or duration information, wherein the abnormal network element information is used to indicate the network element with abnormal traffic when the signaling storm event occurs, the type information is used to indicate that the event type is a signaling storm, the cause information is used to indicate the cause of the signaling storm event, the ratio information is used to indicate the ratio of the current signaling amount to the historical signaling amount of the network, and the duration information is used to indicate the predicted duration of the signaling storm event.
  • the abnormal network element information is used to indicate the network element with abnormal traffic when the signaling storm event occurs
  • the type information is used to indicate that the event type is a signaling storm
  • the cause information is used to indicate the cause of the signaling storm event
  • the ratio information is used to indicate the ratio of the current signaling amount to the historical signaling amount of the network
  • the duration information is used to indicate the predicted duration of the signaling storm event.
  • the second device can improve the network according to the information in the first report, thereby helping the second device to prevent the occurrence of signaling storms.
  • the first device obtains the network threshold, including: the first device receives the network threshold from the second device.
  • the network threshold can be sent by the second device to the first device, so that the first device can predict whether a signaling storm event exists based on the network threshold required by the second device, thereby achieving the second device's desired goal of preventing signaling storms.
  • the method further includes: the first device sends a maximum signaling quantity that the network can support to the second device.
  • the first device can send the maximum signaling quantity that the network can support to the second device, so that the second device can obtain the maximum signaling quantity that the network can support.
  • the second device can improve the network according to the maximum signaling quantity that the network can support, thereby helping the second device to prevent the occurrence of signaling storms.
  • the network threshold is less than a maximum signaling quantity that the network can support.
  • the network threshold is less than the maximum number of signaling that the network can support, so that the first device generates a signaling storm in the network. Furthermore, the above scheme enables the second device to improve the network when the risk of signaling storm is small, thereby improving the effect of preventing signaling storm.
  • the method also includes: the first device determines the maximum number of signaling that the network can support based on availability parameters of multiple network elements in the network, wherein the multiple network elements in the network include a first network element, and the availability parameter of the first network element is the performance management data of the first network element under a first preset signaling number.
  • the first device can determine the maximum signaling quantity that the network can support, so that the second device can obtain the maximum signaling quantity that the network can support.
  • the second device can improve the network according to the maximum signaling quantity that the network can support, thereby helping the second device to prevent the occurrence of signaling storms.
  • the method also includes: the first device obtains performance management data of the first network element and virtual resource usage information of the first network element; the first device determines the availability parameters of the first network element based on the performance management data of the first network element and the virtual resource usage information of the first network element.
  • the first device can determine the availability parameter of the network element.
  • the availability parameter is the performance management data of the network element under a preset signaling quantity. Therefore, the availability parameter of the network element can describe the availability of the network element under signaling impact, which helps to prevent the occurrence of signaling storms.
  • the method further includes: the first device sending an availability parameter of the first network element to the second device.
  • the first device can send the availability parameter of the network element to the second device.
  • the availability parameter is the performance management data of the network element under the preset signaling quantity. Therefore, the availability parameter of the network element can describe the availability of the network element under the signaling impact, which helps the second device to prevent the occurrence of signaling storms.
  • the method further includes: the first device receives a second request from the second device, the second request being used to request the first device to determine availability parameters of multiple network elements in the network.
  • the first device can request the second device to determine the availability parameter of the network element.
  • the availability parameter is the performance management data of the network element under the preset signaling quantity, and the availability parameter of the network element can describe the availability of the network element under the signaling impact. Therefore, the above solution helps to achieve the desired goal of the second device to prevent signaling storms.
  • the multiple network elements in the network also include a second network element
  • the method also includes: the first device obtains an availability parameter of the second network element, the availability parameter of the second network element is performance management data of the second network element under a second preset signaling quantity, wherein, when the signaling storm occurs, the availability parameter of the second network element does not meet the expected target; the first device determines a second report based on the availability parameter of the second network element, wherein the second report is used to indicate capacity expansion of the second network element.
  • the first device can suggest the second device to expand the capacity of the second network element to prevent the occurrence of a signaling storm.
  • the expected goal includes an expected duration for resolving a signaling storm and/or a maximum number of users that the network can support.
  • the expected target may include the expected duration of resolving the signaling storm and/or the maximum number of users that the network can support.
  • the second device provides improvement suggestions for the network element according to the above expected target, so that the network element can meet the expected duration and the maximum number of users in the expected target, thereby enhancing the availability of the network.
  • the method also includes: the first device receives a third request from the second device, the third request is used to request the first device to provide suggestions for network elements in the network, wherein the third request includes the desired target.
  • the first device can request the second device to provide improvement suggestions for the network element, and the request can carry the expected goal, thereby helping to achieve the second device's expected goal of preventing signaling storms.
  • the method also includes: the first device registers a first management data analysis service MDAS and a second MDAS, wherein the capability information in the registration parameters corresponding to the first MDAS is used to indicate that the first MDAS is capable of determining whether the signaling storm event exists, and the capability information in the registration parameters corresponding to the second MDAS is used to indicate that the second MDAS is capable of providing recommendations for network elements in the network.
  • the second device can access the access address of the first MDAS or the second MDAS as needed, avoiding the delay caused by the first device identifying the intention of the second device and calling the corresponding MDAS, thereby improving the efficiency of network analysis.
  • a network analysis method is provided, which can be executed by a second device, or by a component (e.g., a processor, a chip, or a chip system) in the second device, or by a logic module or software that can implement all or part of the functions of the second device.
  • the method includes: a second device sends a first request to a first device, the first request is used to request the first device to determine whether there is a signaling storm event, the signaling storm event is used to indicate that the network has a risk of a signaling storm; the second device receives a first report from the first device, the first report is used to indicate the existence of the signaling storm event.
  • the second device may be a requester, or an operations support system (OSS).
  • the second device may be other devices.
  • the first device can determine that the network has the risk of a signaling storm according to the signaling quantity that the network can support and the current signaling quantity of the network, thereby being able to predict the occurrence of a signaling storm.
  • the method further includes: the second device sending a network threshold to the first device, where the network threshold is used to indicate the amount of signaling that the network can support.
  • the network threshold can be sent by the second device to the first device, so that the first device can predict whether a signaling storm event exists based on the network threshold required by the second device, thereby achieving the second device's desired goal of preventing signaling storms.
  • the method further includes: the second device receives the maximum number of signaling that the network can support from the first device; and the second device determines the network threshold based on the maximum number of signaling that the network can support.
  • the second device can determine the network threshold according to the maximum signaling quantity that the network can support. In this way, the first device can predict whether a signaling storm event exists according to the network threshold required by the second device, thereby achieving the second device's desired goal of preventing signaling storms.
  • the network threshold is less than a maximum signaling quantity or a maximum signaling multiple that the network can support.
  • the network threshold is less than the maximum number of signalings that the network can support, so that the first device determines that a signaling storm event exists when the risk of a signaling storm occurring in the network is low. Furthermore, the above solution enables the second device to improve the network when the risk of a signaling storm is low, thereby improving the effect of preventing a signaling storm.
  • the multiple network elements in the network include a first network element
  • the method further includes: the second device receives an availability parameter of the first network element from the first device, the availability parameter of the first network element being performance management data of the first network element under a first preset signaling quantity; and the second device configures the first network element according to the availability parameter of the first network element.
  • the second device can configure the availability parameter on the network element.
  • the availability parameter is the performance management data of the network element under the preset signaling quantity. Therefore, the availability parameter of the network element can describe the availability of the network element under the signaling impact, which helps the network element prevent the occurrence of signaling storms.
  • the method further includes: the second device sends a second request to the first device, where the second request is used to request the first device to determine availability parameters of multiple network elements in the network.
  • the first device can request the second device to determine the availability parameter of the network element.
  • the availability parameter is the performance management data of the network element under the preset signaling quantity, and the availability parameter of the network element can describe the availability of the network element under the signaling impact. Therefore, the above solution helps to achieve the desired goal of the second device to prevent signaling storms.
  • the multiple network elements in the network also include a second network element, wherein the method also includes: the second device receives a second report from the first device, the second report is used to indicate capacity expansion of the second network element, wherein, when the signaling storm occurs, the availability parameters of the second network element do not meet the expected targets.
  • the first device can suggest the second device to expand the capacity of the second network element to prevent the occurrence of a signaling storm.
  • the expected goal includes an expected duration for resolving a signaling storm and/or a maximum number of users that the network can support.
  • the expected target may include the expected duration of resolving the signaling storm and/or the maximum number of users that the network can support.
  • the second device provides improvement suggestions for the network element according to the above expected target, so that the network element can meet the expected duration and the maximum number of users in the expected target, thereby enhancing the availability of the network.
  • the third request includes the desired target, and the third request is used to request the first device to provide suggestions for network elements in the network, wherein the method also includes: the second device sends the third request to the first device.
  • the first device can request the second device to provide improvement suggestions for the network element, and the request can carry the expected goal, thereby helping to achieve the second device's expected goal of preventing signaling storms.
  • the method further includes: the second device queries the registration of the first device Parameters; the second device receives the registration parameters of the first management data analysis service MDAS and the registration parameters of the second MDAS, the capability information in the registration parameters corresponding to the first MDAS is used to indicate that the first MDAS can determine whether the signaling storm event exists, and the capability information in the registration parameters corresponding to the second MDAS is used to indicate that the second MDAS can provide suggestions for network elements in the network.
  • the second device can access the access address of the first MDAS or the second MDAS as needed, avoiding the delay caused by the first device identifying the intention of the second device and calling the corresponding MDAS, thereby improving the efficiency of network analysis.
  • a communication device comprising a processor, wherein the processor is used to enable the communication device to execute the first aspect and any possible method of the first aspect, or to enable the communication device to execute the first aspect and any possible method of the second aspect, by executing a computer program or instruction, or by a processing circuit.
  • the communication device further includes a memory for storing the computer program or instruction.
  • the processor is specifically used to call and run the computer program or computer instruction stored in the memory, so that the processor implements any one of the implementations in the first aspect or the second aspect.
  • the communication device further includes a transceiver (also referred to as a communication interface), the transceiver being used to input and/or output signals through the communication interface.
  • the processor is used to control the transceiver to transmit and receive signals.
  • a communication device comprising a processing circuit (also referred to as a processor) and an input/output interface (also referred to as an interface circuit), the input/output interface being used to input and/or output signals, the processing circuit being used to execute the first aspect and any possible method of the first aspect; or the processing circuit being used to execute the second aspect and any possible method of the second aspect.
  • a processing circuit also referred to as a processor
  • an input/output interface also referred to as an interface circuit
  • the processor is used to communicate with other devices through the interface circuit and execute any one of the implementations in the first aspect or any one of the implementations in the second aspect.
  • the processor includes one or more.
  • a communication device may be a first device, or a device or module for performing the function of the first device; the communication device may be a second device, or a device or module for performing the function of the second device.
  • the communication device may include a module or unit corresponding to each of the methods/operations/steps/actions described in the first aspect.
  • the module or unit may be a hardware circuit, software, or a combination of a hardware circuit and software.
  • the communication device may include a module or unit corresponding to the method/operation/step/action described in the second aspect, and the module or unit may be a hardware circuit, or software, or a combination of hardware circuit and software.
  • a computer-readable storage medium on which a computer program or instruction is stored.
  • the computer program or the instruction is run on a computer, the first aspect and any possible method of the first aspect are executed; or, the second aspect and any possible method of the second aspect are executed.
  • a computer program product comprising a computer program or instructions, which, when executed on a computer, causes the first aspect and any possible method of the first aspect to be executed; or causes the second aspect and any possible method of the second aspect to be executed.
  • a communication device comprising a processor, connected to a memory, and used to call a program stored in the memory to execute any possible method of the first aspect or any possible method of the second aspect.
  • the memory may be located inside the communication device or outside the communication device.
  • the processor may include one or more.
  • the communication device of the third aspect, fourth aspect, and fifth aspect may be a chip or a chip system.
  • a chip device comprising a processor for calling a computer program or computer instruction in a memory so that the processor executes any one of the implementations in the first aspect or any one of the implementations in the second aspect.
  • the processor is coupled to the memory via an interface.
  • a communication system which includes a first device and a second device; the first device is used to execute the method shown in the first aspect, and the second device is used to execute the method shown in the second aspect.
  • a communication method is provided, which is applied to a first device and a second device, wherein the method includes: the first device executes the method shown in the first aspect; the second device executes the method shown in the second aspect.
  • FIG1 is a schematic diagram of a network architecture of a communication system applicable to an embodiment of the present application.
  • FIG2 is a schematic flow chart of a signaling process.
  • FIG3 is a schematic block diagram of a communication system provided in an embodiment of the present application.
  • FIG4 is a schematic flowchart of a network analysis method provided in an embodiment of the present application.
  • FIG5 is a schematic flowchart of a registration method provided in an embodiment of the present application.
  • FIG6 is a schematic flowchart of a registration parameter query method provided in an embodiment of the present application.
  • FIG. 7 is a schematic flowchart of a network element capability evaluation method provided in an embodiment of the present application.
  • FIG8 is a schematic flowchart of a network capability evaluation method provided in an embodiment of the present application.
  • FIG. 9 is a schematic flowchart of a signaling storm event discovery method provided in an embodiment of the present application.
  • FIG. 10 is a schematic flowchart of a signaling storm event analysis method provided in an embodiment of the present application.
  • FIG. 11 is a schematic flowchart of another network analysis method provided in an embodiment of the present application.
  • FIG. 12 is a schematic block diagram of a communication device according to an embodiment of the present application.
  • FIG13 is a schematic block diagram of another communication device according to an embodiment of the present application.
  • FIG14 is a schematic block diagram of a communication system according to an embodiment of the present application.
  • the technical solution provided in this application can be applied to various communication systems, such as: the fifth generation ( 5th generation, 5G) or new radio (new radio, NR) system, long term evolution (long term evolution, LTE) system, LTE frequency division duplex (frequency division duplex, FDD) system, LTE time division duplex (time division duplex, TDD) system, etc.
  • the technical solution provided in this application can also be applied to future communication systems, such as the sixth generation ( 6th generation, 6G) mobile communication system.
  • the technical solution provided in this application can also be applied to device to device (D2D) communication, vehicle to everything (V2X) communication, machine to machine (M2M) communication, machine type communication (MTC), and Internet of things (IoT) communication system or other communication systems.
  • D2D device to device
  • V2X vehicle to everything
  • M2M machine to machine
  • MTC machine type communication
  • IoT Internet of things
  • FIG1 shows a schematic diagram of a network architecture of a communication system applicable to an embodiment of the present application, wherein the network architecture includes terminal equipment, access network equipment, access and mobility management network element, session management network element, user plane function network element, policy control network element, network slice selection network element, network warehouse function network element, network data analysis network element, unified data management network element, unified data storage network element, authentication service function network element, network capability exposure network element, application function network element, and a data network (DN) connected to an operator network.
  • the terminal equipment can send service data to the data network through the access network equipment and the user plane function network element, and receive service data from the data network.
  • a terminal device is a device with wireless transceiver function, which can be deployed on land, including indoors or outdoors, handheld, wearable or vehicle-mounted; it can also be deployed on the water (such as ships, etc.); it can also be deployed in the air (such as airplanes, balloons and satellites, etc.).
  • the terminal device can communicate with the core network via the radio access network (RAN) and exchange voice and/or data with the RAN.
  • RAN radio access network
  • the terminal device can be a mobile phone, a tablet computer (Pad), a computer with wireless transceiver function, a mobile Internet device (MID), a wearable device, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, Wireless terminals in industrial control, wireless terminals in self-driving, wireless terminals in remote medical, wireless terminals in smart grid, wireless terminals in transportation safety, wireless terminals in smart city, wireless terminals in smart home, drones, drone controllers, etc.
  • Terminal devices are sometimes also called user equipment (UE), mobile stations, and remote stations.
  • the embodiments of this application do not limit the specific technology, device form, and name used by the terminal devices.
  • Access network equipment is a device in the network used to connect terminal devices to the wireless network.
  • Access network equipment can be a node in the wireless access network, which can also be called a base station, or a radio access network (RAN) node (or device).
  • RAN can also be equivalent to the next generation radio access network (NG-RAN) in the layer 3 relay architecture.
  • NG-RAN next generation radio access network
  • RAN is sometimes used below to refer to access network equipment. It is understandable that RAN can also be AN.
  • the access network equipment may include an evolved base station (NodeB or eNB or e-NodeB, evolutionary Node B) in a long term evolution (LTE) system or an evolved LTE system (LTE-Advanced, LTE-A), such as a traditional macro base station eNB and a micro base station eNB in a heterogeneous network scenario, or may also include a next generation node B (next generation node B, gNB) in a 5G or NR system, or may also include a radio network controller (radio network controller, RNC), a node B (Node B, NB), a base station controller (base station controller, BSC), a base transceiver station (base transceiver station, BTS), a transmission reception point (transmission reception point, TRP), a home base station (for example, home evolved NodeB, or home Node B, HNB), Baseband unit (BBU), baseband pool BBU pool, or WiFi access point (AP), etc., or may also include
  • CU supports radio resource control (RRC), packet data convergence protocol (PDCP), service data adaptation protocol (SDAP) and other protocols;
  • RRC radio resource control
  • PDCP packet data convergence protocol
  • SDAP service data adaptation protocol
  • DU mainly supports radio link control layer (RLC), media access control layer (MAC) and physical layer protocols.
  • the access and mobility management network element is mainly used for the attachment and tracking area update process of the terminal in the mobile network.
  • the access and mobility management network element can provide non-access stratum (NAS) messages, complete registration management, connection management, reachability management, assign tracking area list (TA list), legal monitoring, access authorization, authentication and mobility management, etc., and transparently route session management (SM) messages to the session management network element.
  • NAS non-access stratum
  • TA list assign tracking area list
  • SM session management
  • the access and mobility management network element can be the access and mobility management function (AMF).
  • AMF access and mobility management function
  • future communication systems such as 6G communication systems
  • the mobility management network element can still be the AMF network element, or it can have other names, which is not limited by this application.
  • the session management network element is mainly used for session and bearer management in mobile networks, such as session establishment, modification, and release. Specific functions include allocating Internet Protocol (IP) addresses to terminals, selecting user plane function network elements that provide message forwarding functions, etc.
  • IP Internet Protocol
  • the session management network element can be a session management function (SMF).
  • SMF session management function
  • future communication systems such as 6G communication systems
  • the session management network element can still be an SMF network element, or it can have other names, which are not limited in this application.
  • the user plane function network element is mainly used to process user messages, such as forwarding, billing, legal monitoring, etc.
  • the user plane function network element can be used for routing forwarding, threshold control, traffic monitoring, verification and other functions of user plane data.
  • the user plane function network element can also be used for the management of UE IP addresses, the management of core network (CN) tunnel information, etc.
  • the user plane function network element can also be called a protocol data unit (PDU) session anchor (PSA).
  • PDU protocol data unit
  • PSA protocol data unit
  • the user plane function network element can be a user plane function (UPF).
  • UPF user plane function
  • future communication systems such as 6G communication systems
  • the user plane function network element can still be a UPF network element, or it can have other names, which is not limited in this application.
  • the policy control network element includes user subscription data management function, policy control function, charging policy control function QoS control, etc.
  • the policy control network element may be a policy control function (PCF).
  • PCF policy control function
  • future communication systems such as 6G communication systems
  • the policy control network element may still be a PCF network element, or may have other names, which are not limited in this application.
  • the network slice selection function network element is mainly used to select a suitable network slice for the service of the terminal device.
  • the network slice selection network element may be a network slice selection function (NSSF) network element.
  • the network slice selection network element may still be an NSSF network element, or may have other names, which is not limited in this application.
  • the network repository function network element is mainly used to provide registration and discovery functions for network elements or services provided by network elements.
  • the network repository function network element may be a network repository function (NRF).
  • NRF network repository function
  • future communication systems such as 6G communication systems
  • the network repository function network element may still be an NRF network element, or may have other names, which is not limited in this application.
  • the network data analysis network element can collect data from various network functions (NF), such as policy control network elements, session management network elements, user plane function network elements, access and mobility management network elements, and application function network elements (through network capability exposure function network elements), and perform analysis and prediction.
  • NF network functions
  • the network data analysis network element can be a network data analysis function (NWDAF).
  • NWDAF network data analysis function
  • future communication systems such as 6G communication systems
  • the network data analysis network element can still be an NWDAF network element, or it can have other names, which is not limited by this application.
  • the unified data management network element is mainly used to manage the contract information of the terminal device.
  • the unified data management network element can be unified data management (UDM).
  • the unified data management network element can still be the UDM network element, or it can have other names, which is not limited by this application.
  • the unified data storage network element is mainly used to store structured data information, including contract information, policy information, and network data or business data defined in a standard format.
  • the unified data storage network element can be a unified data repository (UDR).
  • the unified data storage network element can still be a UDR network element, or it can have other names, which is not limited by this application.
  • the authentication service function network element is mainly used to perform security authentication on terminal devices.
  • the authentication service function network element can be the authentication server function (AUSF).
  • AUSF authentication server function
  • the authentication service function network element may still be the AUSF network element, or may have other names, which is not limited in this application.
  • a network capability exposure network element can expose some functions of the network to applications in a controlled manner.
  • a network capability exposure network element can be a network capability exposure function (NEF).
  • NEF network capability exposure function
  • a network capability exposure network element can still be a NEF network element, or it can have other names, which are not limited in this application.
  • the application function network element can provide service data of various applications to the control plane network elements of the operator's communication network, or obtain network data information and control information from the control plane network elements of the communication network.
  • the application function network element can be an application function (AF).
  • AF application function
  • future communication systems such as 6G communication systems
  • the application function network element can still be an AF network element, or it can have other names, which is not limited by this application.
  • the application function network element can also be called an application server or a service server.
  • the application function network element can be deployed by the operator network or by a third party.
  • Data network is mainly used to provide data transmission services for terminal devices.
  • Data network can be a private network, such as a local area network, or a public data network (PDN) network, such as the Internet, or a proprietary network jointly deployed by operators, such as the configured IP multimedia core network subsystem (IMS) service.
  • Data network can also come from a third party.
  • PDN public data network
  • IMS IP multimedia core network subsystem
  • the above network element or function can be a network element in a hardware device, a software function running on dedicated hardware, or a virtualized function instantiated on a platform (e.g., a cloud platform).
  • a platform e.g., a cloud platform
  • the above network element or function can be implemented by one device, or by multiple devices together, or by a functional module in one device, which is not specifically limited in the embodiments of the present application.
  • the network elements other than the terminal device in Figure 1 are referred to as the network system below.
  • the terminal device sends signaling to the network system, and the network system receives the signaling from the terminal device and processes the signaling through multiple network elements in the network system. It can be understood that the signaling processing capability of each network element is limited, and the signaling processing capability of the entire network system is limited by the signaling processing capability of each network element.
  • FIG2 is a schematic flow chart of signaling processing.
  • the UE sends multiple signalings to the network system, and processing these signalings requires calling the access network device, AMF, SMF, IMS and UDM network elements in sequence.
  • the front end of the UDM access network device, AMF, SMF and IMS
  • the front end will receive and process a large amount of signaling, and then send a signaling processing request to the UDM, which is used to request the UDM to further process the signaling from the UE.
  • the UDM may not be able to process all signaling processing requests in a timely manner, so the UDM needs to take flow control measures. For example, the UDM may refuse to receive the signaling processing request, or not process the signaling processing request for a long time. If the signaling from the UE is rejected by the network system, the UDM front end will not work on the signaling processing, and the UE needs to resend the signaling to the network system. Alternatively, if the signaling sent by the UE has not been processed by the network system for a long time, the UE may resend the signaling to the network system. In this case, a large number of UEs will resend signaling to the network system.
  • the network system has not yet processed the signaling sent by the UE before, and the newly sent signaling by the UE is processed by the front end of the UDM, so that the UDM receives new signaling processing requests.
  • This will cause the UDM to accumulate a large number of pending signaling processing requests, and the number of pending signaling processing requests continues to increase.
  • a signaling storm will occur. The signaling storm will cause long-term congestion in the network system, resulting in unavailable services of the network system.
  • the signaling from the UE may be processed by more or fewer network elements.
  • the signaling from the UE may be processed by other network elements other than the access network equipment, AMF, SMF, IMS and UDM.
  • AMF access network equipment
  • SMF mobility management entity
  • IMS IMS
  • UDM UDM
  • MME mobility management entity
  • SMF packet data network gateway
  • PGW packet data network gateway
  • HSS home subscriber server
  • the reason why the signaling storm occurs is that the signaling received by the network system from the terminal device exceeds the network system's signaling processing capacity.
  • the reason may be The reason is that the terminal equipment sends a large amount of signaling in a short period of time, the network element in the network system fails, the network system fails, the wireless access network fails, the bearer network fails, or other sudden disasters occur.
  • FIG3 is a schematic block diagram of a communication system 300 provided in an embodiment of the present application.
  • OSS 310 may interact with MDAF 320.
  • MDAF 320 may provide MDAS services, and OSS 310 may request MDAF 320 to predict signaling storms or analyze a network system or a network element in the network system through the MDAS services provided by MDAF 320.
  • MDAF 320 may predict signaling storms or analyze a network system or a network element in the network system based on the request received from OSS 310, and send a prediction or analysis report to OSS 310.
  • the MDAF 320 may send a request message to the network element 330 to request information such as performance management data (PM).
  • PM performance management data
  • VNF virtual network function
  • the MDAF 320 may send a request message to the network function virtualization (NFV) management and orchestration (MANO) 340 to request information such as PM and virtual resource usage information.
  • the MDAF 320 may predict a signaling storm or analyze a network system or a network element in the network system based on the information obtained.
  • FIG4 is a schematic flow chart of a network analysis method 400 provided in an embodiment of the present application.
  • the method 400 can predict the occurrence of a signaling storm.
  • the method 400 is described below in conjunction with FIG4 .
  • a first device receives a first request from a second device, the first request being used to request the first device to determine whether a signaling storm event exists, the signaling storm event being used to indicate that a network has a risk of a signaling storm occurring. Accordingly, the second device sends the first request to the first device.
  • the first device may be a service provider of the MDAS, or the first device may be the MDAF 320.
  • the present application is not limited to this, and the first device may also be other devices.
  • the second device may be a requester, or the OSS 310. Alternatively, the second device may be other devices.
  • the first request may be any request, and the first request may be carried in any message.
  • the first request may also have other names, such as a signaling storm event discovery request, etc., which is not limited in the present application.
  • a signaling storm event is used to indicate that the network is at risk of a signaling storm.
  • the network in method 400 may be the aforementioned network system, and the network may include multiple network elements, and the multiple network elements may be core network elements, access network devices, bearer network elements, etc.
  • the existence of a signaling storm event indicates that the network is at risk of a signaling storm. It is understandable that the existence of a signaling storm event does not mean that a signaling storm has occurred, nor does it mean that a fault (fault or failure) has occurred.
  • the existence of a signaling storm event may also be expressed in other ways, such as the occurrence of a signaling storm event, the appearance of a signaling storm event, etc., which is not limited in this application.
  • signaling storm and failure are two different concepts. When a signaling storm occurs, there may be no failure. Some time after the signaling storm occurs, a failure may occur due to the continuous accumulation of signaling in a network element in the network. However, handling the failure at this time requires a lot of resources, and the failure has already caused business losses. It can be seen that signaling storm and failure are concepts at different levels.
  • MDAF can predict that the network has not failed or has failed. Alternatively, MDAF can determine that the network has not failed or has failed. Alternatively, the network has not failed or has failed. It can be understood that an alarm does not mean that a failure has occurred. The alarm may just be an anomaly in the network, which can be recovered through the network's self-healing mechanism and will not affect the network.
  • the first device obtains a network threshold, where the network threshold is used to indicate the amount of signaling that the network can support.
  • the number of signaling can be a specific number or a relative number.
  • the number of signaling can be 1000.
  • the number of signaling is a relative value, the number of signaling can be 10 times a certain benchmark.
  • the above-mentioned benchmark can be set manually, for example, set to 100.
  • the above-mentioned benchmark can also be the specific number of signaling received by the network during the last signaling storm, signaling storm event or failure.
  • the above-mentioned benchmark can also be the specific number of signaling received by the network at a certain point in time.
  • the above-mentioned time point can be a specific time point, such as a moment in the past, or a relative time point, such as a time point a period of time (for example, 30 days) ago from the time point of executing S420.
  • the above-mentioned time length can be pre-configured. It should be noted that the present application does not limit the benchmark, and the benchmark can also be set in other ways.
  • the network has a maximum number of signaling that can be supported. For example, when the registration success rate is 80% and the single-user registration duration is 10 seconds, there is a maximum number of user registration requests that the network can support.
  • the network threshold is used to indicate the number of signaling that the network can process while achieving the performance requirement.
  • the network threshold is used to indicate the number of signaling that the network can process under performance conditions. The desired target can be determined by the second device or other devices.
  • the network threshold can be used to indicate the maximum amount of signaling that the network can support, or it can be used to indicate the maximum amount of signaling that the network can support.
  • Small signaling quantity For example, the maximum number of signalings that the network can support is 1000, and the network threshold can be 1000 or any value less than 1000.
  • the maximum number of signalings that the network can support is 10 times, and the network threshold can be 10 times or any value less than 10 times.
  • the maximum number of signaling requests that the network can support can also be called the maximum increase in the number of signaling requests, or the maximum signaling impact that the entire network can support, or the maximum increase in the key performance indicator (KPI) (for example, the maximum number of sessions that the network can support, or the maximum number of user registration requests that the network can support).
  • KPI key performance indicator
  • S420 includes: the first device receives the network threshold from the second device.
  • the network threshold may be carried in the first request.
  • the first request may include the network threshold.
  • the first device may determine the network threshold according to the first request.
  • the first device may obtain the network threshold from the first request.
  • the present application does not limit the specific manner in which the first device receives the network threshold.
  • the network threshold may also be carried in other messages.
  • other messages may include the network threshold.
  • the first device may determine the network threshold based on other messages.
  • the first device may obtain the network threshold from other messages.
  • the first device receiving the network threshold from the second device can be understood as the first device receiving information indicating the network threshold.
  • the network threshold can be sent by the second device to the first device, so that the first device can predict whether a signaling storm event exists based on the network threshold required by the second device, thereby achieving the second device's desired goal of preventing signaling storms.
  • S420 includes: the first device determines the network threshold according to availability parameters of multiple network elements in the network.
  • the availability parameter may also be referred to as an availability index.
  • the plurality of network elements include a first network element, a second network element, and a third network element.
  • the availability parameter of the first network element may be the performance management data of the first network element under a first preset signaling quantity.
  • the availability parameter of the second network element may be the performance management data of the second network element under a second preset signaling quantity.
  • the availability parameter of the third network element may be the performance management data of the third network element under a third preset signaling quantity.
  • the first preset signaling quantity, the second preset signaling quantity and the third preset signaling quantity can be specific quantities or relative quantities.
  • the meanings of the specific quantity and the relative quantity refer to the embodiment of S420 above.
  • the first preset signaling quantity, the second preset signaling quantity and the third preset signaling quantity can be all the same, partially the same or all different.
  • the embodiments of the second preset signaling quantity and the third preset signaling quantity can refer to the embodiment of the first preset signaling quantity.
  • the first preset signaling quantity can be set to one or more.
  • the availability parameter of the first network element can be one or more.
  • the availability parameter of the first network element can be used to indicate the performance management data or KPI of the first network element under different signaling impacts.
  • the maximum number of signalings that each network element in multiple network elements can theoretically support.
  • the first preset signaling quantity can be the maximum number of signalings that the first network element can support, or it can be a signaling quantity smaller than the maximum number of signalings that can be supported.
  • the maximum number of signalings that the first network element can support is 500
  • the first preset signaling quantity can be 500, or it can be any value less than 500.
  • the maximum number of signalings that the first network element can support is 5 times
  • the first preset signaling quantity can be 5 times, or it can be any value less than 5 times.
  • the multiple network elements include the first network element, the second network element and the third network element, and the present application does not limit this.
  • the multiple network elements may include more or fewer network elements.
  • the performance management data may be PM.
  • the performance management data of the first network element may be the number of registered users, the registration success rate, the registration duration of a single user, the maximum registration duration, etc. It is understandable that the performance management data may also include other parameters. For example, the average registration duration of multiple users, the maximum registration duration of multiple users, the number of registration failures, etc.
  • the lower the availability parameter of a network element the lower the number of signalings that the network element can support.
  • the higher the availability parameter of a network element the higher the number of signalings that the network element can support. In other words, when the number of signalings is high, the availability parameter of a network element is low, indicating that the network element may not meet the expected target. When the number of signalings is high, the availability parameter of a network element is high, indicating that the network element may meet the expected target.
  • the first device comprehensively analyzes the availability parameters of multiple network elements in the network to determine the number of signaling that the network can support, that is, the network threshold.
  • This application does not limit the specific method of determining the network threshold based on the availability parameters, for example, it can be based on an artificial intelligence (AI) algorithm or other algorithms.
  • AI artificial intelligence
  • the first device determines a first report according to the network threshold and the current signaling amount of the network, where the first report is used to indicate the existence of the signaling storm event.
  • the current signaling quantity is a concept relative to the historical signaling quantity.
  • the current signaling quantity can be the signaling quantity when S430 is executed, or It is the number of signaling when executing S410 or S420.
  • the number of historical signaling is the number of signaling in the past period of time.
  • the number of historical signaling can be a "benchmark" for the relative number of signaling. That is to say, the above-mentioned benchmark can also be the specific number of signaling received by the network during the last signaling storm, signaling storm event or failure.
  • the number of historical signaling can be the specific number of signaling received by the network at a certain point in time.
  • the above-mentioned time point can be a specific time point, such as a certain moment in the past, or it can be a relative time point, such as a time point some time ago (for example, 30 days) from the time point of executing S430.
  • the above-mentioned time length can be pre-configured. It should be noted that the present application does not limit the benchmark, and the benchmark can also be set in other ways.
  • the network threshold is a specific number of signaling that the network can support, wherein S430 includes: when the current signaling number is greater than or equal to the network threshold, the first device determines that the signaling storm event exists.
  • the network threshold is a relative amount of signaling that the network can support
  • S430 includes: the first device obtains the historical signaling amount of the network. When the current signaling amount relative to the historical signaling amount is greater than or equal to the network threshold, the first device determines that the signaling storm event exists.
  • the current signaling quantity may include the quantity of user registration request signaling, the quantity of sessions, etc. This application does not limit this.
  • the present application does not limit the specific method of determining the first report, and in addition to the above two examples, other methods may be used to determine the first report.
  • other methods may be used to determine the first report.
  • an AI algorithm or other algorithms may be used to determine the first report.
  • the present application does not limit the specific name of the first report, and the first report may also have other names, such as indication information, report information, feedback information, feedback list, etc.
  • the first report is a name of a type of information.
  • the first report may indicate that the signaling storm event exists. Alternatively, the first report may indicate that the signaling storm event occurs or appears. Alternatively, the first report may indicate that the network has a risk of a signaling storm occurring.
  • method 400 may include: the first device determines another report according to the network threshold and the current signaling amount of the network, the other report is used to indicate that the signaling storm event does not exist.
  • the first device determines another report according to the network threshold and the current signaling amount of the network, the other report is used to indicate that the signaling storm event does not exist.
  • the first device can determine that the network has the risk of a signaling storm according to the signaling quantity that the network can support and the current signaling quantity of the network, thereby being able to predict the occurrence of a signaling storm.
  • the method 430 further includes: the first device sends a first report to the second device.
  • the second device receives the first report from the first device.
  • the first device sending the first report to the second device can be understood as the first device sending information indicating the first report to the second device.
  • the first report can be carried in any message. This application does not limit the specific name of the first report, and the first report can also have other names, such as indication information, report information, feedback information, feedback list, etc.
  • the first report is the name of a type of information.
  • the first report includes at least one of abnormal network element information, type information, cause information, ratio information or duration information, wherein the abnormal network element information is used to indicate the network element with abnormal traffic when the signaling storm event occurs, the type information is used to indicate that the event type is a signaling storm, the cause information is used to indicate the cause of the signaling storm event, the ratio information is used to indicate the ratio of the current signaling amount to the historical signaling amount of the network, and the duration information is used to indicate the predicted duration of the signaling storm event.
  • the abnormal network element information is used to indicate the network element with abnormal traffic when the signaling storm event occurs
  • the type information is used to indicate that the event type is a signaling storm
  • the cause information is used to indicate the cause of the signaling storm event
  • the ratio information is used to indicate the ratio of the current signaling amount to the historical signaling amount of the network
  • the duration information is used to indicate the predicted duration of the signaling storm event.
  • the first device may determine at least one of abnormal network element information, type information, cause information, ratio information, or duration information based on PM data such as KPI, for example, through an AI algorithm or other algorithms.
  • Table 1 shows an embodiment of the first report. It should be noted that Table 1 is only an example and does not constitute a limitation on the present application.
  • the first report may include more or less information than Table 1.
  • the first report may replace any information in Table 1 with other information.
  • Abnormal network element information can be carried in the field corresponding to the fault prediction target.
  • the fault prediction target can indicate the network element with abnormal traffic when the signaling storm event occurs.
  • the availability parameter of the network element with abnormal traffic when the signaling storm event occurs is lower than the preset threshold.
  • the availability parameters of multiple network elements in the network are sorted from high to low when a signaling storm event occurs, and the network element with abnormal traffic is the network element with the lower ranking.
  • the type information may be carried in a field corresponding to the potential fault type.
  • the potential fault type may be used to indicate that the event type is a signaling storm.
  • the second device may determine (or know) that a signaling storm event has occurred.
  • the type information may be used to indicate that a signaling storm event has occurred or occurred.
  • the type information may be used to indicate that a signaling storm event exists.
  • Potential fault types may also be used to indicate other types, such as equipment alarm, software or processing error alarm, quality of service alarm, or security service or mechanism violation.
  • the time of event occurrence can be used to indicate the time or time point of occurrence of the signaling storm event.
  • the first device determines that a signaling storm event occurs at time A, and the time of event occurrence can be used to indicate time A.
  • the event identifier can be used to indicate the identifier of the signaling storm event.
  • the perceived severity can be used to indicate the severity of the signaling storm event. For example, the perceived severity can be divided into three levels: high, medium, and low, where the perceived severity is high, indicating that the severity of the signaling storm event is high.
  • the cause information may be carried in a field corresponding to the root cause of the signaling storm.
  • the cause information may indicate the cause of the signaling storm, such as network interruption, disaster or failure.
  • the ratio information may be carried in the field corresponding to the KPI change. For example, if the ratio of the current signaling amount to the historical signaling amount is 10, or the current signaling amount is 10 times the historical signaling amount, the ratio information or KPI change may be used to indicate 10.
  • the duration information may be carried in the field corresponding to the duration of the signaling storm.
  • the duration information may indicate 1000 minutes, indicating that the duration of the signaling storm event is 1000 minutes.
  • the self-healing mechanism of the signaling storm often takes a long time, so it is necessary to prevent the occurrence of the signaling storm.
  • the present application does not limit the specific name of the first report, and the first report may also have other names, such as indication information, report information, feedback information, feedback list, etc.
  • the first report is a name of a type of information.
  • the first device may determine the maximum number of signalings that the network can support based on the availability parameters of multiple network elements in the network.
  • This application does not limit the specific method of determining the maximum number of signalings that the network can support, for example, it may be determined by an AI algorithm or other algorithms.
  • the first device sends the maximum signaling quantity that the network can support to the second device, which can be understood as the first device sending information to the second device for indicating the maximum signaling quantity that the network can support.
  • the method 400 further includes: the second device determines the network threshold according to the maximum number of signaling that the network can support.
  • the second device may determine the network threshold as the maximum signaling quantity that the network can support. As another example, the second device may determine a signaling quantity that is smaller than the maximum signaling quantity that the network can support as the network threshold.
  • the second device can determine the network threshold according to the maximum signaling quantity that the network can support. In this way, the first device can predict whether a signaling storm event exists according to the network threshold required by the second device, thereby achieving the second device's desired goal of preventing signaling storms.
  • the network threshold is less than the maximum number of signalings that the network can support.
  • the maximum number of signalings that the network can support is 1000, and the network threshold may be 800.
  • the maximum number of signalings that the network can support is 10 times, and the network threshold may be 8 times.
  • the network threshold is equal to the maximum number of signaling that the network can support, then when the current number of signaling is close to the maximum number of signaling that the network can support, the first device can determine that a signaling storm event exists. In this case, the risk of a signaling storm occurring in the network is high, and a failure may even occur. If the network threshold is less than the maximum number of signaling that the network can support, then when the current number of signaling is less than the maximum number of signaling that the network can support, the first device can determine that a signaling storm event exists. In this case, the risk of a signaling storm occurring in the network is low, and the risk of a failure is even lower, thereby improving the effect of preventing signaling storms.
  • the network threshold is less than the maximum number of signalings that the network can support, so that the first device determines that a signaling storm event exists when the risk of a signaling storm occurring in the network is low. Furthermore, the above solution enables the second device to improve the network when the risk of a signaling storm is low, thereby improving the effect of preventing a signaling storm.
  • the method 400 also includes: the first device determines the maximum number of signaling that the network can support based on availability parameters of multiple network elements in the network, wherein the multiple network elements in the network include a first network element, and the availability parameter of the first network element is the performance management data of the first network element under a first preset signaling number.
  • the availability parameter may also be referred to as an availability index.
  • the first preset signaling quantity may be a specific quantity or a relative quantity. The meaning of the specific quantity and the relative quantity refer to the embodiment of S420 above.
  • the first preset signaling quantity may be the maximum signaling quantity that the first network element can support, or may be a signaling quantity that is smaller than the maximum signaling quantity that can be supported. For example, if the maximum signaling quantity that the first network element can support is 500, the first preset signaling quantity may be 500, or may be any value less than 500. For example, if the maximum signaling quantity that the first network element can support is 5 times, the first preset signaling quantity may be 5 times, or may be any value less than 5 times.
  • the performance management data may be PM.
  • the performance management data of the first network element may be the number of registered users, the registration success rate, the registration duration of a single user, the maximum registration duration, etc. It is understandable that the performance management data may also include other parameters. For example, the average registration duration of multiple users, the maximum registration duration of multiple users, the number of registration failures, etc.
  • the lower the availability parameter of a network element the lower the number of signalings that the network element can support.
  • the higher the availability parameter of a network element the higher the number of signalings that the network element can support. In other words, when the number of signalings is high, the availability parameter of a network element is low, indicating that the network element may not meet the expected target. When the number of signalings is high, the availability parameter of a network element is high, indicating that the network element may meet the expected target.
  • the first device comprehensively analyzes the availability parameters of multiple network elements in the network to determine the maximum number of signaling that the network can support.
  • This application does not limit the specific method of determining the maximum number of signaling that the network can support based on the availability parameters, for example, it can be based on an AI algorithm or other algorithms.
  • the first device can determine the maximum signaling quantity that the network can support, so that the second device can obtain the maximum signaling quantity that the network can support.
  • the second device can improve the network according to the maximum signaling quantity that the network can support, thereby helping the second device to prevent the occurrence of signaling storms.
  • the method 400 also includes: the first device obtains the performance management data of the first network element and the virtual resource usage information of the first network element; the first device determines the availability parameters of the first network element based on the performance management data of the first network element and the virtual resource usage information of the first network element.
  • the first device may obtain the performance management data and virtual resource usage information of the first network element from the NFV MANO 340.
  • the first device may send a request message to the NFV MANO 340 to request to obtain the performance management data and virtual resource usage information of the first network element.
  • the NFV MANO 340 may send the performance management data and virtual resource usage information of the first network element to the first network element according to the request message.
  • the performance management data may be PM.
  • the performance management data of the first network element may be the number of registered users, the registration success rate, the registration duration of a single user, the maximum registration duration, etc. It is understandable that the performance management data may also include other parameters. For example, the average registration duration of multiple users, the maximum registration duration of multiple users, the number of registration failures, etc.
  • the virtual resource usage information may be used to indicate the usage of the virtual resources.
  • the virtual resources may include at least one of a virtual processor, a virtual memory, or a virtual disk.
  • the virtual resources may also include other resources.
  • the virtual resource usage information may include virtual processor utilization, virtual memory utilization, virtual disk utilization, etc.
  • the virtual resource usage information may also include other information.
  • the present application does not limit the specific method of determining the availability parameters based on the performance management data and the virtual resource usage information. For example, it can be based on an AI algorithm or other algorithms. It should be noted that the above only takes the first network element as an example.
  • the embodiments of the present application can also determine the availability parameters of other network elements.
  • the first device can determine the availability parameters of the second network element based on the performance management data of the second network element and the virtual resource usage information of the second network element.
  • the first device can determine the availability parameter of the network element.
  • the availability parameter is the performance management data of the network element under a preset signaling quantity. Therefore, the availability parameter of the network element can describe the availability of the network element under signaling impact, which helps to prevent the occurrence of signaling storms.
  • the method 400 further includes: the first device sends an availability parameter of the first network element to the second device. Accordingly, the second device receives the availability parameter of the first network element from the first device, where the availability parameter of the first network element is performance management data of the first network element under a first preset signaling quantity.
  • the first device can send the availability parameter of the network element to the second device.
  • the availability parameter is the performance management data of the network element under the preset signaling quantity. Therefore, the availability parameter of the network element can describe the availability of the network element under the signaling impact, which helps the second device prevent the occurrence of signaling storms.
  • the method 400 further includes: the second device configuring the first network element according to the availability parameter of the first network element.
  • the second device may send configuration information to the first network element, where the configuration information includes an availability parameter of the first network element.
  • the second device can configure the availability parameter on the network element.
  • the availability parameter is the performance management data of the network element under the preset signaling quantity. Therefore, the availability parameter of the network element can describe the availability of the network element under the signaling impact, which helps the network element prevent the occurrence of signaling storms.
  • the method 400 further includes: the first device receives a second request from the second device, the second request being used to request the first device to determine availability parameters of multiple network elements in the network. Accordingly, the second device sends the second request to the first device.
  • the second request may include a network element identifier (or network element type) and a target signaling type.
  • the second request includes an identifier of the AMF and a registration request, so that the first device can determine the availability parameters of the AMF under a certain number of registration requests based on the second request.
  • the second request may be any request, and the second request may be carried in any message.
  • the second request may also have other names, such as a network element capability evaluation request or a network element availability evaluation request, etc., which is not limited in the present application.
  • the second request may be triggered by an event, such as a holiday event, a network upgrade event, etc.
  • an event such as a holiday event, a network upgrade event, etc.
  • the second device may send the second request to the first device.
  • the second request may also be actively sent by the second device, in other words, the second device sending the second request does not depend on the triggering of other events.
  • the first device can request the second device to determine the availability parameter of the network element.
  • the availability parameter is the performance management data of the network element under the preset signaling quantity, and the availability parameter of the network element can describe the availability of the network element under the signaling impact. Therefore, the above solution helps to achieve the desired goal of the second device to prevent signaling storms.
  • the multiple network elements in the network also include a second network element
  • the method 400 further includes: the first device obtains an availability parameter of the second network element, the availability parameter of the second network element is the performance management data of the second network element under a second preset signaling quantity, the second network element is a bottleneck network element, wherein when the signaling storm occurs, the availability parameter of the second network element does not meet the expected target; the first device determines a second report according to the availability parameter of the second network element, wherein the second report is used to indicate capacity expansion of the second network element. Accordingly, the second device receives the second report from the first device.
  • the first device may determine the availability parameter of the second network element based on the performance management data of the second network element and the virtual resource usage information of the second network element, thereby enabling the first device to obtain the availability parameter of the second network element.
  • the first device may obtain the availability parameter of the second network element from NFV MANO 340 or the second device.
  • the second network element may have been configured with the availability parameter, so that the first device may send a request message to NFV MANO 340 or the second device to request NFV MANO 340 or the second device to feedback the availability parameter of the second network element.
  • NFV MANO 340 or the second device queries the configuration information of the second network element to obtain the availability parameter of the second network element, and sends the availability parameter of the second network element to the first device.
  • the first device receives the availability parameter of the second network element from NFV MANO 340 or the second device, thereby enabling the first device to obtain the availability parameter of the second network element.
  • the first device may determine that the second network element is a bottleneck network element according to the availability parameters of multiple network elements in the network. For example, if the availability parameter of the second network element is less than the availability parameters of other network elements, the second network element may be determined to be a bottleneck network element.
  • the bottleneck network element may be one or more network elements.
  • the desired goal includes a desired duration for resolving a signaling storm and/or a maximum number of users that the network can support.
  • the expected target may include the expected duration of resolving the signaling storm and/or the maximum number of users that the network can support.
  • the second device provides improvement suggestions for the network element according to the above expected target, so that the network element can meet the expected duration and the maximum number of users in the expected target, thereby enhancing the availability of the network.
  • a network element whose availability parameter does not meet the expected target can be called a bottleneck network element.
  • a bottleneck network element is a network element with weak resistance to signaling impact among multiple network elements in the network.
  • the availability parameter of the bottleneck network element does not meet the expected target. Therefore, the bottleneck network element cannot meet the expected time to resolve the signaling storm, or cannot meet the maximum number of users required to be supported by the network. In this way, taking other measures such as flow control on the bottleneck network element cannot make the bottleneck network element meet the expected target. At this time, expanding the capacity of the bottleneck network element can avoid the occurrence of signaling storms.
  • the capacity expansion of the second network element can be understood as increasing the virtual resources of the second network element, such as increasing the input of the virtual processor of the second network element. Outputs the upper limit, the capacity of virtual memory, or the capacity of virtual disk.
  • the first device determines the second report based on the availability parameter and the desired target of the second network element.
  • the first device may determine the second report based on the availability parameter and convergence information of the second network element, wherein the convergence information is used to indicate the expected time length for the network to process the signaling received by the network within a preset time window after a signaling storm occurs.
  • the preset event window may be 180 seconds.
  • the network receives multiple connection requests from terminal devices, and the convergence information may indicate that the network takes 200 seconds to process these connection requests.
  • the expected duration indicated by the convergence information may be calculated from the start time of the preset time window, in other words, from the time the signaling storm occurs.
  • the first device may suggest that the second device expand the capacity of the second network element in order to enable the network to more quickly achieve the expected duration that the second device expects to resolve the signaling storm.
  • the duration threshold may be set in advance.
  • the first device may determine the second report based on the availability parameter, user number information, and convergence information of the second network element.
  • the user number information is used to indicate the number of user online requests received by the network within a preset time window that the network can process after the signaling storm occurs. That is, the user number information can be used to indicate the maximum number of users that the network can support.
  • the network receives multiple user online requests from the terminal device, and the second network element expects the network to process 100 user upper limit requests within 200 seconds.
  • the number of users information may be from the second device. That is, in some embodiments, the second device sends the number of users information to the first device, and correspondingly, the first device receives the number of users information from the second device. Therefore, the number of users information belongs to the expected target of the second device.
  • the suggestion for expanding the capacity of the second network element indicated in the first report may be referred to as a scaling recommendation.
  • the second report, convergence information, and user number information may also have other names, which are not limited in this application.
  • the first device can suggest the second device to expand the capacity of the second network element, so as to prevent the occurrence of a signaling storm.
  • the second report may also include a flow control recommendation.
  • the flow control recommendation may indicate configuring a new flow control parameter for the third network element.
  • Table 2 is an example of a recommendation report.
  • the recommendation information indicating the flow control configuration of the third network element can be carried in the flow control configuration recommendation of the flow control network element, and the recommendation information indicating the capacity expansion of the second network element can be carried in the capacity expansion recommendation for the bottleneck network element.
  • the method 400 further includes: the first device receives a third request from the second device, wherein the third request includes the desired target, and the third request is used to request the first device to provide suggestions for the network element in the network. Accordingly, the second device sends the third request to the first device.
  • the third request may be any request, and the third request may be carried in any message.
  • the third request may also have other names, such as a signaling storm event analysis request, etc., which is not limited in this application.
  • the third request may also carry an availability parameter of a network element.
  • the first device can request the second device to provide improvement suggestions for the network element, and the request can carry the expected goal, thereby helping to achieve the second device's expected goal of preventing signaling storms.
  • the method 400 also includes: the first device registers a first MDAS and a second MDAS, wherein the capability information in the registration parameters corresponding to the first MDAS is used to indicate that the first MDAS is capable of determining whether the signaling storm event exists, and the capability information in the registration parameters corresponding to the second MDAS is used to indicate that the second MDAS is capable of providing recommendations for network elements in the network.
  • the first device may send a request message to a management service registration (MnS) registration network element, requesting to create registration parameters of the first MDAS and registration parameters of the second MDAS.
  • MnS management service registration
  • the management service registration network element After receiving the request message, creates the registration parameters of the first MDAS and the registration parameters of the second MDAS according to the request message.
  • Table 3 shows the registration parameters of the first MDAS or the second MDAS.
  • the label may indicate the identifier of the first MDAS or the second MDAS.
  • the type may include MDAS, and the type is used to indicate that the service type of the first MDAS or the second MDAS is MDAS.
  • the access address may indicate the access address of the first MDAS or the second MDAS.
  • the management scope indicates the management scope of the first MDAS or the second MDAS, for example, the management scope corresponds to the identifier of the subnetwork that the first MDAS can manage.
  • the support capabilities may include fault management, signaling analysis, preventive evaluation, etc. The support capabilities may be used to indicate the capability information supported by the MDAS.
  • fault management may be used to indicate that the capability of the MDAS supports determining whether the signaling storm event exists
  • signaling analysis may be used to indicate that the capability of the MDAS supports providing suggestions for network elements in the network.
  • fault management capabilities it can be further subdivided, for example, it can be divided into faults that support signaling congestion types and faults that do not support signaling congestion types.
  • the capability information in the registration parameters is carried in the supported capability field.
  • the supported capability of the first MDAS may be fault management, and support signaling congestion type faults.
  • the supported capability of the second MDAS may be signaling analysis.
  • the second device can access the access address of the first MDAS or the second MDAS as needed, avoiding the delay caused by the first device identifying the intention of the second device and calling the corresponding MDAS, thereby improving the efficiency of network analysis.
  • the method 400 also includes: the second device queries the registration parameters of the first device; the second device receives the registration parameters of the first management data analysis service MDAS and the registration parameters of the second MDAS, the capability information in the registration parameters corresponding to the first MDAS is used to indicate that the first MDAS can determine whether the signaling storm event exists, and the capability information in the registration parameters corresponding to the second MDAS is used to indicate that the second MDAS can provide suggestions for network elements in the network.
  • the second device can access the access address of the first MDAS or the second MDAS as needed, avoiding the delay caused by the first device identifying the intention of the second device and calling the corresponding MDAS, thereby improving the efficiency of network analysis.
  • Fig. 5 is a schematic flow chart of a registration method 500 provided in an embodiment of the present application. The method 500 is described below in conjunction with Fig. 5 .
  • MDAF 320 sends a request message to the MnS registration network element, where the request message is used to request the creation of registration parameters.
  • the MnS registration network element receives the request message from MDAF 320.
  • the MDAF 320 may be a first device.
  • the registration parameter may be a registration parameter of a first MDAS or a second MDAS.
  • the registration parameter may also be referred to as MnS information (Info).
  • the MnS registration network element creates registration parameters to complete the registration.
  • the registration parameter may be a registration parameter of the first MDAS or the second MDAS.
  • the registration parameter may include at least one of a label, a type, a version, an access address, a management scope, and a support capability, and see the embodiment related to Table 3 for details.
  • Fig. 6 is a schematic flow chart of a registration parameter query method 600 provided in an embodiment of the present application. The method 600 is described below in conjunction with Fig. 6 .
  • OSS 310 sends a query message to the MnS registration network element, where the query message is used to request to query the registration parameters.
  • the MnS registration network element receives the query message from OSS 310.
  • OSS 310 can be the second device.
  • the MnS registration network element sends registration parameters to the OSS 310.
  • the OSS 310 receives the registration parameters from the MnS registration network element.
  • the registration parameters may include the registration parameters of the first MDAS and/or the second MDAS.
  • the registration parameters may include at least one of a label, a type, a version, an access address, a management scope, and a support capability, for details, see the relevant embodiments of Table 3.
  • the registration parameters may also include registration parameters of other services, which are not limited in this application.
  • Fig. 7 is a schematic flow chart of a network element capability evaluation method 700 provided in an embodiment of the present application. The method 700 is described below in conjunction with Fig. 7 .
  • OSS 310 sends a second request to MDAF 320, where the second request is used to request MDAF 320 to determine availability parameters of multiple network elements in the network.
  • the second request may include a network element identifier (or network element type) and a target signaling type.
  • the second request includes an identifier and a registration signaling of the AMF, so that the first device can determine the availability parameters of the AMF under a certain number of registration signalings based on the second request.
  • the second request may be any request, and the second request may be carried in any message.
  • the second request may also have other names, such as a network element capability assessment request or a network element availability assessment request, etc., which are not limited in this application.
  • the second request may be triggered by an event, such as a holiday event, a network upgrade event, etc. In other words, when an event occurs, OSS 310 may execute S710.
  • the second request may also be actively sent by OSS 310. In other words, OSS 310 may actively execute S710 without relying on the triggering of other events.
  • MDAF 320 receives performance management data and virtual resource usage information from NFV MANO 340. Accordingly, NFV MANO 340 sends performance management data and virtual resource usage information to MDAF 320.
  • the performance management data may be PM.
  • the performance management data of the first network element may include The number of registrations, the registration success rate, the registration duration of a single user, etc. It is understandable that the performance management data may also include other parameters, such as the average registration duration of multiple users, the maximum registration duration of multiple users, the number of registration failures, etc.
  • the virtual resource usage information may be used to indicate the usage of the virtual resource.
  • the virtual resource may include at least one of a virtual processor, a virtual memory, or a virtual disk.
  • the virtual resource may also include other resources.
  • the virtual resource usage information may include virtual processor utilization, virtual memory utilization, virtual disk utilization, etc.
  • the virtual resource usage information may also include other information.
  • the method 700 further includes: the NFV MANO 340 receives a request message from the MDAF 320, the request message being used to request performance management data and virtual resource usage information. Accordingly, the MDAF 320 sends a request message to the NFV MANO 340.
  • MDAF 320 determines the availability parameters of network elements based on performance management data and virtual resource usage information.
  • the availability parameter of a network element is the performance management data of the network element under the preset signaling quantity.
  • the availability parameter can also be called an availability index.
  • the preset signaling quantity can be a specific quantity or a relative quantity.
  • MDAF 320 sends the availability parameters of the network elements to OSS 310.
  • OSS 310 receives the availability parameters of the network elements from MDAF 320.
  • OSS 310 may configure network elements according to availability parameters of the network elements.
  • Fig. 8 is a schematic flow chart of a network capability evaluation method 800 provided in an embodiment of the present application. The method 800 is described below in conjunction with Fig. 8 .
  • OSS 310 sends a fourth request to MDAF 320, where the fourth request is used to request to determine the maximum number of signaling and bottleneck network elements that the network can support.
  • the fourth request may include a network scope identifier and a target signaling type, wherein the network scope identifier may be a subnetwork ID or identifiers of multiple network elements, or specific subnet location information.
  • the fourth request may be any request, and the fourth request may be carried in any message.
  • the fourth request may also have other names, such as a network capability evaluation request or a network availability evaluation request, etc., which is not limited in this application.
  • the fourth request may be triggered by an event, such as a holiday event, a network upgrade event, etc.
  • an event such as a holiday event, a network upgrade event, etc.
  • OSS 310 may execute S810.
  • the fourth request may also be actively sent by OSS 310, in other words, OSS 310 may actively execute S810 without relying on the triggering of other events.
  • MDAF 320 obtains the availability parameters of multiple network elements in the network.
  • MDAF 320 may obtain the availability parameter of the network element from the configuration information of the network element. For example, MDAF 320 may send a request message to NFV MANO 340 or OSS 330, requesting NFV MANO 340 or OSS 330 to feedback the availability parameter of the second network element. NFV MANO 340 or OSS 330 queries the configuration information of the second network element, thereby obtaining the availability parameter of the second network element, and sends the availability parameter of the second network element to MDAF 320. MDAF 320 receives the availability parameter of the second network element from NFV MANO 340 or OSS 330, thereby enabling MDAF 320 to obtain the availability parameter of the second network element.
  • S720 and S730 may be executed to determine the availability parameter.
  • MDAF 320 may determine the availability parameter of the network element based on the performance management data and virtual resource usage information of the network element, thereby enabling the acquisition of the availability parameters of each network element.
  • MDAF 320 determines the bottleneck network element and the maximum number of signaling that the network can support based on the availability parameters of multiple network elements in the network.
  • MDAF 320 sends the maximum signaling quantity that the network can support to OSS 310.
  • OSS 310 receives the maximum signaling quantity that the network can support from MDAF 320.
  • the method 800 further includes: the MDAF 320 sends information of the bottleneck network element to the OSS 310. Accordingly, the OSS 310 receives the information of the bottleneck network element from the MDAF 320.
  • Fig. 9 is a schematic flow chart of a signaling storm event discovery method 900 provided in an embodiment of the present application. The method 900 is described below in conjunction with Fig. 9 .
  • OSS 310 sends a first request to the first MDAS, the first request is used to request the first MDAS to determine whether there is a signaling storm event, the signaling storm event is used to indicate that the network has a risk of a signaling storm.
  • the signaling storm event is used to indicate that the network has a risk of a signaling storm.
  • the first request may carry a network threshold.
  • the maximum number of signalings that OSS 310 can support from the network of MDAF 320 is 10 times, and the network threshold in the first request sent by OSS 310 may be 8 times. It should be noted that the above is only an example and does not constitute a limitation of this application.
  • the first MDAS receives the current signaling quantity of the network from the NFV MANO 340. Accordingly, the NFV MANO 340 sends the current signaling quantity of the network to the first MDAS.
  • the method 900 further includes: the NFV MANO 340 receives a request message from the first MDAS, the request message being used to request the current signaling quantity of the network. Accordingly, the first MDAS sends a request message to the NFV MANO 340.
  • the first MDAS determines a first report according to the current signaling amount of the network and the network threshold, where the first report is used to indicate the existence of a signaling storm event.
  • the first MDAS sends a first report to the OSS 310. Accordingly, the OSS 310 receives the first report from the first MDAS.
  • Fig. 10 is a schematic flow chart of a signaling storm event analysis method 1000 provided in an embodiment of the present application. The method 1000 is described below in conjunction with Fig. 10 .
  • OSS 310 sends a third request to the second MDAS, where the third request is used to request the second MDAS to provide suggestions for network elements in the network.
  • the second MDAS receives the performance management data and virtual resource usage information from the NFV MANO 340. Accordingly, the NFV MANO 340 sends the performance management data and virtual resource usage information to the second MDAS.
  • the performance management data may be PM.
  • the performance management data of the first network element may include the number of registrations, the registration success rate, the registration duration of a single user, etc. It is understandable that the performance management data may also include other parameters. For example, the average registration duration of multiple users, the maximum registration duration of multiple users, the number of registration failures, etc.
  • the virtual resource usage information may be used to indicate the usage of the virtual resource.
  • the virtual resource may include at least one of a virtual processor, a virtual memory, or a virtual disk.
  • the virtual resource may also include other resources.
  • the virtual resource usage information may include virtual processor utilization, virtual memory utilization, virtual disk utilization, etc.
  • the virtual resource usage information may also include other information.
  • the method 1000 further includes: the NFV MANO 340 receives a request message from the second MDAS, the request message being used to request performance management data and virtual resource usage information. Accordingly, the second MDAS sends a request message to the NFV MANO 340.
  • the second MDAS determines a second report according to the performance management data and the virtual resource usage information.
  • the second report is used to indicate capacity expansion of the network element.
  • the second MDAS sends a second report to the OSS 310. Accordingly, the OSS 310 receives the second report from the second MDAS.
  • FIG11 is a schematic flow chart of another network analysis method 1100 provided in an embodiment of the present application.
  • Method 1100 may be a combination of method 900 and method 1000, except that method 1100 does not distinguish between the first MDAS and the second MDAS, and merges the first MDAS and the second MDAS into MDAF 320.
  • Method 1100 is described below in conjunction with FIG11.
  • OSS 310 sends a first request to MDAF 320, the first request is used to request MDAF 320 to determine whether there is a signaling storm event, the signaling storm event is used to indicate that the network has a risk of a signaling storm.
  • the signaling storm event is used to indicate that the network has a risk of a signaling storm.
  • the first request may carry a network threshold.
  • the maximum number of signalings that OSS 310 can support from the network of MDAF 320 is 10 times, and the network threshold in the first request sent by OSS 310 may be 8 times. It should be noted that the above is only an example and does not constitute a limitation of this application.
  • MDAF 320 receives the current signaling quantity of the network from NFV MANO 340. Accordingly, NFV MANO 340 sends the current signaling quantity of the network to MDAF 320.
  • method 1100 before S1120, further includes: NFV MANO 340 receives a request message from MDAF 320, the request message being used to request the current signaling quantity of the network. Accordingly, MDAF 320 sends a request message to NFV MANO 340.
  • MDAF 320 determines a first report based on the current signaling amount of the network and the network threshold, where the first report is used to indicate the presence of a signaling storm event.
  • MDAF 320 sends a first report to OSS 310. Accordingly, OSS 310 receives the first report from MDAF 320.
  • OSS 310 sends a third request to MDAF 320, where the third request is used to request MDAF 320 to provide suggestions for network elements in the network.
  • MDAF 320 receives performance management data and virtual resource usage information from NFV MANO 340. Accordingly, NFV MANO 340 sends performance management data and virtual resource usage information to MDAF 320.
  • the performance management data may be PM.
  • the performance management data of the first network element may include the number of registrations, the registration success rate, the registration duration of a single user, etc. It is understandable that the performance management data may also include other parameters. For example, the average registration duration of multiple users, the maximum registration duration of multiple users, the number of registration failures, etc.
  • the virtual resource usage information may be used to indicate the usage of the virtual resources.
  • the virtual resources may include at least one of a virtual processor, a virtual memory, or a virtual disk.
  • the virtual resources may also include other resources.
  • the virtual resource usage information may include virtual processor utilization, Virtual memory utilization, virtual disk utilization, etc. Virtual resource usage information may also include other information.
  • the method 1100 further includes: the NFV MANO 340 receives a request message from the MDAF 320, the request message being used to request performance management data and virtual resource usage information. Accordingly, the MDAF 320 sends a request message to the NFV MANO 340.
  • MDAF 320 determines a second report based on the performance management data and the virtual resource usage information.
  • the second report is used to indicate capacity expansion of the network element.
  • MDAF 320 sends a second report to OSS 310. Accordingly, OSS 310 receives the second report from MDAF 320.
  • the terminal device and the network device may include a hardware structure and/or a software module, and implement the above functions in the form of a hardware structure, a software module, or a hardware structure plus a software module. Whether one of the above functions is executed in the form of a hardware structure, a software module, or a hardware structure plus a software module depends on the specific application and design constraints of the technical solution.
  • the communication device 1200 includes a processor 1210 and a transceiver 1220, and the processor 1210 and the transceiver 1220 may be interconnected via a bus 1230.
  • the communication device 1200 may be a first device or a second device.
  • the communication device 1200 may further include a memory 1240.
  • the memory 1240 includes, but is not limited to, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM), or a portable read-only memory (CD-ROM), and the memory 1240 is used for related instructions and data.
  • RAM random access memory
  • ROM read-only memory
  • EPROM erasable programmable read-only memory
  • CD-ROM portable read-only memory
  • the processor 1210 may be one or more central processing units (CPUs). When the processor 1210 is a CPU, the CPU may be a single-core CPU or a multi-core CPU.
  • the processor 1210 may be a signal processor, a chip, or other integrated circuit that can implement the method of the present application, or a portion of the circuit used for processing functions in the aforementioned processor, chip, or integrated circuit.
  • the transceiver 1220 may also be referred to as an input-output interface or a communication interface.
  • the transceiver 1220 is used for input or output of signals or data, and may also be an input-output circuit.
  • the communication device 1200 When the communication device 1200 is a first device, exemplarily, the communication device 1200 includes a processor 1210 and a transceiver 1220.
  • the transceiver 1220 is used to receive a first request from a second device, the first request is used to request the first device to determine whether there is a signaling storm event, the signaling storm event is used to indicate that the network has a risk of a signaling storm;
  • the processor 1210 is used to obtain a network threshold, the network threshold is used to indicate the number of signalings that the network can support, and is used to determine a first report according to the network threshold and the current number of signalings of the network, the first report is used to indicate the existence of the signaling storm event.
  • the communication device 1200 When the communication device 1200 is the second device, illustratively, the communication device 1200 includes a transceiver 1220.
  • the transceiver 1220 is used to send a first request to the first device, the first request is used to request the first device to determine whether there is a signaling storm event, the signaling storm event is used to indicate that the network has a risk of a signaling storm, and is used to receive a first report from the first device, the first report is used to indicate the presence of the signaling storm event.
  • FIG13 is a schematic block diagram of another communication device 1300 according to an embodiment of the present application.
  • the communication device 1300 may be a first device or a second device, or a chip or module in the first device or the second device, for implementing the method involved in the above embodiment.
  • the communication device 1300 includes a transceiver unit 1310.
  • the transceiver unit 1310 is exemplarily introduced below.
  • the transceiver unit 1310 may include a transmitting unit and a receiving unit.
  • the transmitting unit is used to perform a transmitting action of the communication device
  • the receiving unit is used to perform a receiving action of the communication device.
  • the embodiment of the present application combines the transmitting unit and the receiving unit into one transceiver unit. A unified description is given here, and no further description is given later.
  • the transceiver unit 1310 is configured to receive a first request from a second device.
  • the communication device 1300 may further include a processing unit 1320, which is used to execute the content of the first device involving processing, coordination and other steps.
  • a processing unit 1320 which is used to execute the content of the first device involving processing, coordination and other steps.
  • the transceiver unit 1310 is configured to send a first request to the first device.
  • the communication device 1300 may further include a processing unit 1320, which is used to execute the content of the steps involving processing, coordination, etc. of the second device.
  • a processing unit 1320 which is used to execute the content of the steps involving processing, coordination, etc. of the second device.
  • the communication device 1300 is the first device or the second device, it will be responsible for executing the methods or steps related to the first device or the second device in the above method embodiments.
  • the communication device 1300 further includes a storage unit 1330, and the storage unit 1330 is used to store a program or code for executing the aforementioned method.
  • the device embodiments shown in Figures 12 and 13 are used to implement the embodiments in Figures 3 to 11.
  • the specific execution steps and methods of the devices shown in Figures 12 and 13 can refer to the contents of the aforementioned method embodiments.
  • Fig. 14 is a schematic block diagram of a communication system 1400 according to an embodiment of the present application.
  • the communication system 1400 includes a first device and a second device, and the first device and the second device are used to implement the embodiments of Figs. 3 to 11 above.
  • the present application also provides a chip, including a processor, for calling and executing instructions stored in a memory from the memory, so that a communication device equipped with the chip executes the methods in the above examples.
  • the present application also provides another chip, including: an input interface, an output interface, and a processor, wherein the input interface, the output interface, and the processor are connected via an internal connection path, and the processor is used to execute the code in the memory, and when the code is executed, the processor is used to execute the method in each of the above examples.
  • the chip also includes a memory, and the memory is used to store computer programs or codes.
  • the present application also provides a processor, which is coupled to a memory and is used to execute the method and function involving the first device or the second device in any of the above embodiments.
  • a computer program product including instructions is provided.
  • the method of the above embodiment is implemented.
  • the present application also provides a computer program.
  • the computer program is executed in a computer, the method of the above embodiment is implemented.
  • a computer-readable storage medium stores a computer program, and when the computer program is executed by a computer, the method described in the above embodiment is implemented.
  • the disclosed systems, devices and methods can be implemented in other ways.
  • the device embodiments described above are only schematic.
  • the division of the units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed.
  • Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.
  • the units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
  • each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.
  • the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium.
  • the technical solution of the present application can be essentially or partly embodied in the form of a software product that contributes to the prior art.
  • the computer software product is stored in a storage medium and includes several instructions for a computer device (which can be a personal computer, server, or network device, etc.) to perform all or part of the steps of the methods described in each embodiment of the present application.
  • the aforementioned storage media include: U disk, mobile hard disk, read-only memory (ROM), random access memory (RAM), disk or optical disk, and other media that can store program codes.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Environmental & Geological Engineering (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本申请提供了一种网络分析方法和装置，涉及通信技术领域，该方法包括：第一装置接收来自第二装置的第一请求，该第一请求用于请求该第一装置确定是否存在信令风暴事件，该信令风暴事件用于指示网络具有发生信令风暴的风险；该第一装置获取网络阈值，该网络阈值用于指示该网络能够支持的信令数量；该第一装置根据该网络阈值和该网络的当前信令数量，确定第一报告，该第一报告用于指示存在该信令风暴事件。基于上述方案，第一装置可以根据网络能够支持的信令数量和网络的当前信令数量，确定网络具有发生信令风暴的风险，从而能够预测信令风暴的发生。

Description

网络分析方法和装置
本申请要求在2023年11月3日提交中国国家知识产权局、申请号为202311464433.8、发明名称为“网络分析方法和装置”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及通信技术领域，并且更具体地，涉及一种网络分析方法和装置。
背景技术
随着运营商业务和网络架构向着多元化发展，越发繁重的业务流量给信令网络带来越发巨大的压力，高压也预示着事故的频发。信令风暴是指由于网络系统收到的来自终端设备的信令请求超过了网络系统的处理信令能力，引发网络拥塞甚至雪崩效应，导致网络不可用。
因此，如何预测信令风暴的发生，是亟待解决的问题。
发明内容
本申请提供一种网络分析方法和装置，能够预测信令风暴的发生。
第一方面，提供了一种网络分析方法，该方法可以由第一装置执行，或者由第一装置中的组件(例如，处理器、芯片、或芯片系统等)执行，或者由能实现全部或部分第一装置功能的逻辑模块或软件执行。该方法包括：第一装置接收来自第二装置的第一请求，该第一请求用于请求该第一装置确定是否存在信令风暴事件，该信令风暴事件用于指示网络具有发生信令风暴的风险；该第一装置获取网络阈值，该网络阈值用于指示该网络能够支持的信令数量；该第一装置根据该网络阈值和该网络的当前信令数量，确定第一报告，该第一报告用于指示存在该信令风暴事件。
示例性地，第一装置可以是管理数据分析业务(management data analytics service，MDAS)的服务提供方(service producer)，或者，第一装置可以是管理数据分析功能(management data analytics function，MDAF)。
基于上述方案，第一装置可以根据网络能够支持的信令数量和网络的当前信令数量，确定网络具有发生信令风暴的风险，从而能够预测信令风暴的发生。
结合第一方面，在第一方面的某些实现方式中，该第一报告包括异常网元信息、类型信息、原因信息、比值信息或持续时间信息中的至少一项，其中，该异常网元信息用于指示该信令风暴事件发生时流量异常的网元，该类型信息用于指示事件类型为信令风暴，该原因信息用于指示该信令风暴事件的产生原因，该比值信息用于指示该网络的当前信令数量与历史信令数量的比值，该持续时间信息用于指示该信令风暴事件的预测的持续时间。
基于上述方案，第二装置可以根据第一报告中的信息对网络进行改进，从而有助于第二装置预防信令风暴的发生。
结合第一方面，在第一方面的某些实现方式中，该第一装置获取网络阈值，包括：该第一装置接收来自该第二装置的该网络阈值。
基于上述方案，网络阈值可以是第二装置发送给第一装置的，这样，第一装置可以根据第二装置需求的网络阈值预测信令风暴事件是否存在，从而达成第二装置对预防信令风暴的期望目标。
结合第一方面，在第一方面的某些实现方式中，该方法还包括：该第一装置向该第二装置发送该网络能够支持的最大信令数量。
基于上述方案，第一装置可以向第二装置发送网络能够支持的最大信令数量，使得第二装置能够获取网络能够支持的最大信令数量。第二装置可以根据网络能够支持的最大信令数量对网络进行改进，从而有助于第二装置预防信令风暴的发生。
结合第一方面，在第一方面的某些实现方式中，该网络阈值小于该网络能够支持的最大信令数量。
基于上述方案，网络阈值小于该网络能够支持的最大信令数量，使得第一装置在网络发生信令风暴 的风险较小的情况下，确定信令风暴事件存在。进而，上述方案使得第二装置在信令风暴的风险较小的情况下可以对网络进行改进，从而提高预防信令风暴的效果。
结合第一方面，在第一方面的某些实现方式中，该方法还包括：该第一装置根据该网络中的多个网元的可用性参数，确定该网络能够支持的最大信令数量，其中，该网络中的多个网元包括第一网元，该第一网元的可用性参数是在第一预设信令数量下的该第一网元的性能管理数据。
基于上述方案，第一装置可以确定该网络能够支持的最大信令数量，使得第二装置能够获取网络能够支持的最大信令数量。第二装置可以根据网络能够支持的最大信令数量对网络进行改进，从而有助于第二装置预防信令风暴的发生。
结合第一方面，在第一方面的某些实现方式中，该方法还包括：该第一装置获取该第一网元的性能管理数据和该第一网元的虚拟资源使用信息；该第一装置根据该第一网元的性能管理数据和该第一网元的虚拟资源使用信息，确定该第一网元的可用性参数。
基于上述方案，第一装置可以确定网元的可用性参数。可用性参数是网元在预设信令数量下的性能管理数据，因此，网元的可用性参数能够描述网元在信令冲击下的可用性，有助于预防信令风暴的发生。
结合第一方面，在第一方面的某些实现方式中，该方法还包括：该第一装置向该第二装置发送该第一网元的可用性参数。
基于上述方案，第一装置可以将网元的可用性参数发送给第二装置。可用性参数是网元在预设信令数量下的性能管理数据，因此，网元的可用性参数能够描述网元在信令冲击下的可用性，有助于第二装置预防信令风暴的发生。
结合第一方面，在第一方面的某些实现方式中，该方法还包括：该第一装置接收来自该第二装置的第二请求，该第二请求用于请求该第一装置确定该网络中的多个网元的可用性参数。
基于上述方案，第一装置可以请求第二装置确定网元的可用性参数。可用性参数是网元在预设信令数量下的性能管理数据，网元的可用性参数能够描述网元在信令冲击下的可用性。因此，上述方案有助于达成第二装置对预防信令风暴的期望目标。
结合第一方面，在第一方面的某些实现方式中，该网络中的多个网元还包括第二网元，其中，该方法还包括：该第一装置获取该第二网元的可用性参数，该第二网元的可用性参数是在第二预设信令数量下的该第二网元的性能管理数据，其中，在该信令风暴发生时，该第二网元的可用性参数不满足期望目标；该第一装置根据该第二网元的可用性参数确定第二报告，其中，该第二报告用于指示对该第二网元扩容。
基于上述方案，在第二网元的可用性参数不满足期望目标的情况下，第一装置可以建议第二装置对第二网元进行扩容，从而预防信令风暴的发生。
结合第一方面，在第一方面的某些实现方式中，该期望目标包括解决信令风暴的期望时长和/或网络能够支持的最大用户数。
基于上述方案，期望目标可以包括解决信令风暴的期望时长和/或网络能够支持的最大用户数。第二装置根据上述期望目标为网元提供改进建议，使得网元能够满足期望目标中的期望时长和最大用户数，从而增强了网络的可用性。
结合第一方面，在第一方面的某些实现方式中，该方法还包括：该第一装置接收来自该第二装置的第三请求，该第三请求用于请求该第一装置为该网络中的网元提供建议，其中，该第三请求包括该期望目标。
基于上述方案，第一装置可以请求第二装置为网元提供改进建议，并且，请求中可以携带期望目标，从而有助于达成第二装置对预防信令风暴的期望目标。
结合第一方面，在第一方面的某些实现方式中，该方法还包括：该第一装置注册第一管理数据分析服务MDAS和第二MDAS，其中，该第一MDAS对应的注册参数中的能力信息用于指示该第一MDAS能够确定是否存在该信令风暴事件，该第二MDAS对应的注册参数中的能力信息用于指示该第二MDAS能够为该网络中的网元提供建议。
基于上述方案，第二装置可以按照需求访问第一MDAS或第二MDAS的访问地址，避免第一装置识别第二装置的意图和调用相应的MDAS所造成的时延，提高了网络分析的效率。
第二方面，提供了一种网络分析方法，该方法可以由第二装置执行，或者由第二装置中的组件(例如，处理器、芯片、或芯片系统等)执行，或者由能实现全部或部分第二装置功能的逻辑模块或软件执 行。该方法包括：第二装置向第一装置发送第一请求，该第一请求用于请求该第一装置确定是否存在信令风暴事件，该信令风暴事件用于指示网络具有发生信令风暴的风险；该第二装置接收来自该第一装置的第一报告，该第一报告用于指示存在该信令风暴事件。
示例性地，第二装置可以是请求方，或者运营支撑系统(operations support system，OSS)。或者，第二装置可以是其他装置。
基于上述方案，第一装置可以根据网络能够支持的信令数量和网络的当前信令数量，确定网络具有发生信令风暴的风险，从而能够预测信令风暴的发生。
结合第二方面，在第二方面的某些实现方式中，该方法还包括：该第二装置向该第一装置发送网络阈值，该网络阈值用于指示该网络能够支持的信令数量。
基于上述方案，网络阈值可以是第二装置发送给第一装置的，这样，第一装置可以根据第二装置需求的网络阈值预测信令风暴事件是否存在，从而达成第二装置对预防信令风暴的期望目标。
结合第二方面，在第二方面的某些实现方式中，该方法还包括：该第二装置接收来自该第一装置的该网络能够支持的最大信令数量；该第二装置根据该网络能够支持的最大信令数量，确定该网络阈值。
基于上述方案，第二装置可以根据网络能够支持的最大信令数量确定网络阈值。这样，第一装置可以根据第二装置需求的网络阈值预测信令风暴事件是否存在，从而达成第二装置对预防信令风暴的期望目标。
结合第二方面，在第二方面的某些实现方式中，该网络阈值小于该网络能够支持的最大信令数量或最大信令倍数。
基于上述方案，网络阈值小于该网络能够支持的最大信令数量，使得第一装置在网络发生信令风暴的风险较小的情况下，确定信令风暴事件存在。进而，上述方案使得第二装置在信令风暴的风险较小的情况下可以对网络进行改进，从而提高预防信令风暴的效果。
结合第二方面，在第二方面的某些实现方式中，该网络中的多个网元包括第一网元，其中，该方法还包括：该第二装置接收来自该第一装置的该第一网元的可用性参数，该第一网元的可用性参数是在第一预设信令数量下的该第一网元的性能管理数据；该第二装置根据该第一网元的可用性参数，配置该第一网元。
基于上述方案，第二装置可以将可用性参数配置到网元上。可用性参数是网元在预设信令数量下的性能管理数据，因此，网元的可用性参数能够描述网元在信令冲击下的可用性，有助于网元预防信令风暴的发生。
结合第二方面，在第二方面的某些实现方式中，该方法还包括：该第二装置向该第一装置发送第二请求，该第二请求用于请求该第一装置确定该网络中的多个网元的可用性参数。
基于上述方案，第一装置可以请求第二装置确定网元的可用性参数。可用性参数是网元在预设信令数量下的性能管理数据，网元的可用性参数能够描述网元在信令冲击下的可用性。因此，上述方案有助于达成第二装置对预防信令风暴的期望目标。
结合第二方面，在第二方面的某些实现方式中，该网络中的多个网元还包括第二网元，其中，该方法还包括：该第二装置接收来自该第一装置的第二报告，该第二报告用于指示对该第二网元扩容，其中，在该信令风暴发生时，该第二网元的可用性参数不满足期望目标。
基于上述方案，在第二网元的可用性参数不满足期望目标的情况下，第一装置可以建议第二装置对第二网元进行扩容，从而预防信令风暴的发生。
结合第二方面，在第二方面的某些实现方式中，该期望目标包括解决信令风暴的期望时长和/或网络能够支持的最大用户数。
基于上述方案，期望目标可以包括解决信令风暴的期望时长和/或网络能够支持的最大用户数。第二装置根据上述期望目标为网元提供改进建议，使得网元能够满足期望目标中的期望时长和最大用户数，从而增强了网络的可用性。
结合第二方面，在第二方面的某些实现方式中，第三请求包括该期望目标，该第三请求用于请求该第一装置为该网络中的网元提供建议，其中，该方法还包括：该第二装置向该第一装置发送该第三请求。
基于上述方案，第一装置可以请求第二装置为网元提供改进建议，并且，请求中可以携带期望目标，从而有助于达成第二装置对预防信令风暴的期望目标。
结合第二方面，在第二方面的某些实现方式中，该方法还包括：该第二装置查询该第一装置的注册 参数；该第二装置接收第一管理数据分析服务MDAS的注册参数和第二MDAS的注册参数，该第一MDAS对应的注册参数中的能力信息用于指示该第一MDAS能够确定是否存在该信令风暴事件，该第二MDAS对应的注册参数中的能力信息用于指示该第二MDAS能够为该网络中的网元提供建议。
基于上述方案，第二装置可以按照需求访问第一MDAS或第二MDAS的访问地址，避免第一装置识别第二装置的意图和调用相应的MDAS所造成的时延，提高了网络分析的效率。
第三方面，提供了一种通信装置，包括处理器，该处理器用于，通过执行计算机程序或指令，或者，通过处理电路，使得该通信装置执行第一方面以及第一方面的任一种可能的方法，或者，使得该通信装置执行第一方面以及第二方面的任一种可能的方法。
一种可能的实现方式中，该通信装置还包括存储器，其用于存储该计算机程序或指令。进一步地，处理器具体用于调用并运行该存储器中存储的计算机程序或计算机指令，使得处理器实现如第一方面或第二方面中的任意一种实现方式。
一种可能的实现方式中，该通信装置还包括收发器(也可以称为通信接口)，收发器用于通过通信接口输入和/或输出信号。该处理器用于控制该收发器收发信号。
第四方面，提供了一种通信装置，包括处理电路(也可以称为处理器)和输入输出接口(也可以称为接口电路)，该输入输出接口用于输入和/或输出信号，该处理电路用于执行第一方面以及第一方面的任一种可能的方法；或者该处理电路用于执行第二方面以及第二方面的任一种可能的方法。
一种可能的实现方式中，处理器用于通过接口电路与其它装置通信，并执行上述第一方面中的任意一种实现方式或第二方面中的任意一种实现方式。该处理器包括一个或多个。
第五方面，提供了一种通信装置。该通信装置可以是第一装置，也可以为用于执行第一装置功能的设备或者模块等；该通信装置可以是第二装置，也可以为用于执行第二装置功能的设备或者模块等。
一种可能的实现中，该通信装置可以包括用于执行第一方面所描述的方法/操作/步骤/动作所一一对应的模块或单元，该模块或单元可以是硬件电路，也可是软件，也可以是硬件电路结合软件实现。
另一种可能的实现中，该通信装置可以包括用于执行第二方面所描述的方法/操作/步骤/动作所一一对应的模块或单元，该模块或单元可以是硬件电路，也可是软件，也可以是硬件电路结合软件实现。
第六方面，提供了一种计算机可读存储介质，该计算机可读存储介质上存储有计算机程序或指令，当该计算机程序或该指令在计算机上运行时，使得第一方面以及第一方面的任一种可能的方法被执行；或者，使得第二方面以及第二方面的任一种可能述的方法被执行。
第七方面，提供了一种计算机程序产品，包含计算机程序或指令，当该计算机程序或指令在计算机上运行时，使得第一方面以及第一方面的任一种可能的方法被执行；或者，使得第二方面以及第二方面的任一种可能的方法被执行。
第八方面，提供一种通信装置，包括处理器，用于与存储器相连，用于调用该存储器中存储的程序，以执行上述第一方面的任一种可能的方法或第二方面的任一种可能的方法。该存储器可以位于该通信装置之内，也可以位于该通信装置之外。且该处理器包括一个或多个。
在一种实现方式中，上述第三方面、第四方面、第五方面的通信装置，可以是芯片或芯片系统。
第九方面，提供一种芯片装置，包括处理器，用于调用存储器中的计算机程序或计算机指令，以使得该处理器执行上述第一方面中的任一种实现方式或第二方面中的任一种实现方式。
可选的，该处理器通过接口与该存储器耦合。
第十方面，提供一种通信系统，该通信系统包括第一装置和第二装置；第一装置用于执行第一方面所示的方法，第二装置用于执行如第二方面所示的方法。
第十一方面，提供一种通信方法，该方法应用于第一装置和第二装置，其中，该方法包括：该第一装置执行如第一方面所示的方法；该第二装置执行如第二方面所示的方法。
关于第三方面至第十一方面等中任一方面的有益效果的描述可以参照第一方面或第二方面的有益效果的描述。
附图说明
图1是本申请实施例适用的一种通信系统的网络架构示意图。
图2是一种信令处理的示意性流程图。
图3是本申请实施例提供的一种通信系统的示意性框图。
图4是本申请实施例提供的一种网络分析方法的示意性流程图。
图5是本申请实施例提供的一种注册方法的示意性流程图。
图6是本申请实施例提供的一种注册参数查询方法的示意性流程图。
图7是本申请实施例提供的一种网元能力评估方法的示意性流程图。
图8是本申请实施例提供的一种网络能力评估方法的示意性流程图。
图9是本申请实施例提供的一种信令风暴事件发现方法的示意性流程图。
图10是本申请实施例提供的一种信令风暴事件分析方法的示意性流程图。
图11是本申请实施例提供的另一种网络分析方法的示意性流程图。
图12是本申请实施例的一种通信装置的示意框图。
图13是本申请实施例的另一种通信装置的示意框图。
图14是本申请实施例的一种通信系统的示意框图。
具体实施方式
下面将结合附图，对本申请中的技术方案进行描述。
本申请提供的技术方案可以应用于各种通信系统，例如：第五代(5th generation，5G)或新无线(new radio，NR)系统、长期演进(long term evolution，LTE)系统、LTE频分双工(frequency division duplex，FDD)系统、LTE时分双工(time division duplex，TDD)系统等。本申请提供的技术方案还可以应用于未来的通信系统，如第六代(6th generation，6G)移动通信系统。本申请提供的技术方案还可以应用于设备到设备(device to device，D2D)通信、车到万物(vehicle-to-everything，V2X)通信、机器到机器(machine to machine，M2M)通信、机器类型通信(machine type communication，MTC)、以及物联网(internet of things，IoT)通信系统或者其他通信系统。
图1示出了本申请实施例适用的一种通信系统的网络架构示意图，该网络架构中包括终端设备、接入网设备、接入与移动性管理网元、会话管理网元、用户面功能网元、策略控制网元、网络切片选择网元、网络仓库功能网元、网络数据分析网元、统一数据管理网元、统一数据存储网元、认证服务功能网元、网络能力开放网元、应用功能网元，以及连接运营商网络的数据网络(data network，DN)。终端设备可通过接入网设备、用户面功能网元向数据网络发送业务数据，以及从数据网络接收业务数据。
终端设备是一种具有无线收发功能的设备，可以部署在陆地上，包括室内或室外、手持、穿戴或车载；也可以部署在水面上(如轮船等)；还可以部署在空中(例如飞机、气球和卫星上等。该终端设备可以经无线接入网(radio access network，RAN)与核心网进行通信，与RAN交换语音和/或数据。该终端设备可以是手机(mobile phone)、平板电脑(Pad)、带无线收发功能的电脑、移动互联网设备(mobile internet device，MID)、可穿戴设备、虚拟现实(virtual reality，VR)终端设备、增强现实(augmented reality，AR)终端设备、工业控制(industrial control)中的无线终端、无人驾驶(self driving)中的无线终端、远程医疗(remote medical)中的无线终端、智能电网(smart grid)中的无线终端、运输安全(transportation safety)中的无线终端、智慧城市(smart city)中的无线终端、智慧家庭(smart home)中的无线终端、无人机、无人机控制器等等。本申请的实施例对应用场景不做限定。终端设备有时也可以称为用户设备(user equipment，UE)、移动台和远方站等，本申请的实施例对终端设备所采用的具体技术、设备形态以及名称不做限定。
接入网设备是网络中用于将终端设备接入到无线网络的设备。接入网设备可以为无线接入网中的节点，又可以称为基站，还可以称为无线接入网(radioaccess network，RAN)节点(或设备)。另外，RAN也可以与layer3中继(relay)架构中的下一代无线接入网(next generation radio access network，NG-RAN)等价，换言之，RAN可以是NG-RAN。为便于描述，下面有时会用RAN来指代接入网设备，可以理解的是，RAN也可以是AN。
接入网设备可以包括长期演进(long term evolution，LTE)系统或演进的LTE系统(LTE-Advanced，LTE-A)中的演进型基站(NodeB或eNB或e-NodeB，evolutional Node B)，如传统的宏基站eNB和异构网络场景下的微基站eNB，或者也可以包括5G或NR系统中的下一代节点B(next generation node B，gNB)，或者还可以包括无线网络控制器(radio network controller，RNC)、节点B(Node B，NB)、基站控制器(base station controller，BSC)、基站收发台(base transceiver station，BTS)、传输接收点(transmission reception point，TRP)、家庭基站(例如，home evolved NodeB，或home Node B，HNB)、 基带单元(base band unit，BBU)、基带池BBU pool，或WiFi接入点(access point，AP)等，再或者还可以包括云接入网(cloud radio access network，CloudRAN)系统中的集中式单元(centralized unit，CU)和分布式单元(distributed unit，DU)，本申请实施例并不限定。在接入网设备包括CU和DU的分离部署场景中，CU支持无线资源控制(radio resource control，RRC)、分组数据汇聚协议(packet data convergence protocol，PDCP)、业务数据适配协议(service data adaptation protocol，SDAP)等协议；DU主要支持无线链路控制层(radio link control，RLC)、媒体接入控制层(media access control，MAC)和物理层协议。
接入与移动性管理网元，主要用于移动网络中的终端的附着、跟踪区更新流程，接入与移动性管理网元可以提供非接入层(non access stratum，NAS)消息、完成注册管理、连接管理、可达性管理、分配跟踪区域列表(track area list，TA list)、合法监听、接入授权、鉴权以及移动性管理等，并且透明路由会话管理(session management，SM)消息到会话管理网元。在第五代(5th generation，5G)通信系统中，接入与移动性管理网元可以是接入与移动性管理功能(access and mobility management function，AMF)，在未来的通信系统(如6G通信系统)中，移动性管理网元可以仍是AMF网元，或者也可以具有其它名称，本申请并不限定。
会话管理网元主要用于移动网络中的会话和承载管理，如会话建立、修改、释放。具体功能如为终端分配互联网协议(internet protocol，IP)地址、选择提供报文转发功能的用户面功能网元等。在5G通信系统中，会话管理网元可以是会话管理功能(session management function，SMF)，在未来的通信系统(如6G通信系统)中，会话管理网元可以仍是SMF网元，或者也可以具有其它名称，本申请并不限定。
用户面功能网元，主要用于对用户报文进行处理，如转发、计费、合法监听等。并且，用户面功能网元可以用于用户面数据的路由转发、门限控制、流量监测、验证等功能。用户面功能网元还可以用于UE IP地址的管理、核心网(core network，CN)隧道信息的管理等。用户面功能网元也可以称为协议数据单元(protocol data unit，PDU)会话锚点(PDU session anchor，PSA)。在5G通信系统中，用户面功能网元可以是用户面功能(user plane function，UPF)，在未来的通信系统(如6G通信系统)中，用户面功能网元可以仍是UPF网元，或者也可以具有其它名称，本申请并不限定。
策略控制网元，包含用户签约数据管理功能、策略控制功能、计费策略控制功能QoS控制等。在5G通信系统中，策略控制网元可以是策略控制功能(policy control function，PCF)，在未来的通信系统(如6G通信系统)中，策略控制网元可以仍是PCF网元，或者也可以具有其它名称，本申请并不限定。
网络切片选择功能网元，主要用于为终端设备的业务选择合适的网络切片。在5G通信系统中，网络切片选择网元可以是网络切片选择功能(network slice selection function，NSSF)网元，在未来的通信系统(如6G通信系统)中，网络切片选择网元可以仍是NSSF网元，或者也可以具有其它名称，本申请并不限定。
网络仓库功能网元，主要用于提供网元或网元所提供服务的注册和发现功能。在5G通信系统中，网络仓库功能网元可以是网络仓库功能(network repository function，NRF)，在未来的通信系统(如6G通信系统)中，网络仓库功能网元可以仍是NRF网元，或者也可以具有其它名称，本申请并不限定。
网络数据分析网元，可以从各个网络功能(network function，NF)，例如策略控制网元、会话管理网元、用户面功能网元、接入与移动性管理网元、应用功能网元(通过网络能力开放功能网元)收集数据，并进行分析和预测。在5G通信系统中，网络数据分析网元可以是网络数据分析功能(network data analytics function，NWDAF)，在未来的通信系统(如6G通信系统)中，网络数据分析网元可以仍是NWDAF网元，或者也可以具有其它名称，本申请并不限定。
统一数据管理网元，主要用于管理终端设备的签约信息。在5G通信系统中，统一数据管理网元可以是统一数据管理(unified data management，UDM)，在未来的通信系统(如6G通信系统)中，统一数据管理网元可以仍是UDM网元，或者也可以具有其它名称，本申请并不限定。
统一数据存储网元，主要用于存储结构化的数据信息，其中包括签约信息、策略信息，以及有标准格式定义的网络数据或业务数据。在5G通信系统中，统一数据存储网元可以是统一数据存储(unified data repository，UDR)，在未来的通信系统(如6G通信系统)中，统一数据存储网元可以仍是UDR网元，或者也可以具有其它名称，本申请并不限定。
认证服务功能网元，主要用于对终端设备进行安全认证。在5G通信系统中，认证服务功能网元可以是认证服务器功能(authentication server function，AUSF)，在未来的通信系统(如6G通信系统)中， 认证服务功能网元可以仍是AUSF网元，或者也可以具有其它名称，本申请并不限定。
网络能力开放网元，可以将网络的部分功能有控制地暴露给应用。在5G通信系统中，网络能力开放网元可以是网络能力开放功能(network exposure function，NEF)，在未来的通信系统(如6G通信系统)中，网络能力开放网元可以仍是NEF网元，或者也可以具有其它名称，本申请并不限定。
应用功能网元，可以向运营商的通信网络的控制面网元提供各类应用的服务数据，或者从通信网络的控制面网元获得网络的数据信息和控制信息。在5G通信系统中，应用功能网元可以是应用功能(application function，AF)，在未来的通信系统(如6G通信系统)中，应用功能网元可以仍是AF网元，或者也可以具有其它名称，本申请并不限定。例如，应用功能网元也可以称为应用服务器或业务服务器。另外，应用功能网元可以是运营商网络部署的，也可以是第三方部署的。
数据网络，主要用于为终端设备提供数据传输服务。数据网络可以是私有网络，如局域网，也可以是公用数据网(public data network，PDN)网络，如因特网(Internet)，还可以是运营商共同部署的专有网络，如配置的IP多媒体网络子系统(IP multimedia core network subsystem，IMS)服务。数据网络还可以来自第三方。
应理解，上述网元或者功能既可以是硬件设备中的网络元件，也可以是在专用硬件上运行的软件功能，或者是平台(例如，云平台)上实例化的虚拟化功能。可选地，上述网元或者功能可以由一个设备实现，也可以由多个设备共同实现，还可以是一个设备内的一个功能模块，本申请实施例对此不作具体限定。
还应理解，上述命名仅为便于区分不同的功能而定义，不应对本申请构成任何限定。本申请并不排除在5G网络以及未来其他的网络中采用其他命名的可能。例如，在6G网络中，上述各个网络中的部分或全部可以沿用5G中的术语，也可能采用其他名称等。图1中的各个网元之间的接口名称只是一个示例，具体实现中接口的名称可能为其他的名称，本申请对此不作具体限定。此外，上述各个网元之间所传输的消息(或信令)的名称也仅仅是一个示例，对消息本身的功能不构成任何限定。
需要说明的是，上述“网元”也可以称为实体、设备、装置或模块等，本申请并未特别限定。并且，在本申请中，为了便于理解和说明，在对部分描述中省略“网元”这一描述，例如，将PCF网元简称PCF，此情况下，该“PCF”应理解为PCF网元或PCF实体，以下，省略对相同或相似情况的说明。
为便于描述，下面将图1中除终端设备以外的网元称为网络系统。终端设备向网络系统发送信令(signaling)，网络系统接收来自终端设备的信令，并通过网络系统中的多个网元对信令进行处理。可以理解的是，每个网元对信令的处理能力都是有限的，整个网络系统对信令的处理能力受限于各个网元对信令的处理能力。
图2是一种信令处理的示意性流程图。参见图2，UE向网络系统发送多个信令，处理这些信令需要先后调用接入网设备、AMF、SMF、IMS和UDM这些网元。假设UDM的前端(接入网设备、AMF、SMF和IMS)按照正常的流程处理来自UE的信令，前端会接收并处理大量的信令，然后向UDM发送信令处理请求，该信令处理请求用于请求UDM针对来自UE的信令进行进一步处理。在UDM接收过多的信令处理请求的情况下，UDM可能不能及时处理所有的信令处理请求，因此，UDM需要采取流控措施。例如，UDM可以拒绝接收信令处理请求，或者长时间不对信令处理请求进行处理。如果来自UE的信令被网络系统拒绝处理，那么UDM的前端对信令的处理也没有作用，UE需要向网络系统重新发送信令。或者，如果UE发送的信令在很长时间没有被网络系统处理，那么UE可能会向网络系统重新发送信令。在这种情况下，会有大量的UE向网络系统重新发送信令。与此同时，网络系统还没有处理UE在之前发送的信令，UE新发送的信令又被UDM的前端处理，使得UDM接收到新的信令处理请求。这会导致UDM堆积了大量待处理的信令处理请求，并且待处理的信令处理请求的数量还在持续增加。在上述过程发展到一定的规模的情况下(例如大量用户在1个小时内不能获得网络系统的服务)，信令风暴(signaling storm)就会发生。信令风暴会引发网络系统长时间的拥塞，导致网络系统的服务不可用。
需要说明的是，图2仅仅是示例，不构成对本申请的限定。例如，可以由更多或更少的网元处理来自UE的信令。又例如，可以由接入网设备、AMF、SMF、IMS和UDM以外的其他网元处理来自UE的信令。另外，上述AMF也可以替换为移动管理实体(mobility management entity，MME)，上述SMF也可以替换为包数据网络网管(packet data network gateway，PGW)，上述UDM也可以替换为归属签约用户服务器(home subscriber server，HSS)。
信令风暴发生的原因在于网络系统收到的来自终端设备的信令超过了网络系统的处理信令能力。导致网络系统收到的来自终端设备的信令超过了网络系统的处理信令能力的原因有多种，例如，原因可能 在于，终端设备在短时间内发送了大量的信令，网络系统中的网元发生故障，网络系统发生故障，无线接入网侧发生故障，承载网侧发生故障，或者发生了其他突发灾害等。
因此，如何预测信令风暴的发生，是亟待解决的问题。
图3是本申请实施例提供的一种通信系统300的示意性框图。
参见图3，OSS 310可以与MDAF 320进行交互，例如，MDAF 320可以提供MDAS服务，OSS 310可以通过MDAF 320提供的MDAS服务向MDAF 320请求预测信令风暴，或分析网络系统或网络系统中的网元。MDAF 320可以根据接收到的来自OSS 310的请求预测信令风暴，或分析网络系统或网络系统中的网元，并向OSS 310发送预测或分析的报告。
在网元330以物理网络功能(physical network function，PNF)的情况下，MDAF 320可以向网元330发送请求消息，请求获取性能管理数据(performance management，PM)等信息。在网元330以虚拟网络功能(virtual network function，VNF)的情况下，MDAF 320可以向网络功能虚拟化(network function virtualization，NFV)管理与编排(management and orchestration，MANO)340发送请求消息，请求获取PM、虚拟资源使用信息等信息。MDAF 320可以根据获取到的信息预测信令风暴，或分析网络系统或网络系统中的网元。
图4是本申请实施例提供的一种网络分析方法400的示意性流程图。方法400能够预测信令风暴的发生。下面结合图4介绍方法400。
S410，第一装置接收来自第二装置的第一请求，该第一请求用于请求该第一装置确定是否存在信令风暴事件，该信令风暴事件用于指示网络具有发生信令风暴的风险。相应地，第二装置向第一装置发送第一请求。
示例性地，第一装置可以是MDAS的服务提供方，或者，第一装置可以是MDAF 320。但是本申请对此不限定，第一装置还可以是其他装置。第二装置可以是请求方，或者OSS 310。或者，第二装置可以是其他装置。
第一请求可以是任意请求，第一请求可以承载于任意消息中。第一请求还可以有其他名称，例如信令风暴事件发现请求等，本申请对此不限定。
信令风暴事件用于指示网络具有发生信令风暴的风险。其中，方法400中的网络可以是前述网络系统，网络可以包括多个网元，多个网元可以是核心网网元、接入网设备、承载网网元等。信令风暴事件存在，表明网络具有发生信令风暴的风险。可以理解的是，信令风暴事件存在，不意味着信令风暴已经发生，也不意味着故障(fault或failure)已经发生。信令风暴事件存在还可以有其他表述，例如信令风暴事件发生、信令风暴事件出现等，本申请对此不限定。
需要说明的是，信令风暴与故障是不同的两个概念。在信令风暴发生时，可能没有出现故障。在信令风暴发生后的一段时间，由于信令不断堆积在网络中的某个网元中，可能造成故障。但是，这时再对故障进行处理，需要消耗大量的资源，并且故障已经造成了业务损失。可见，信令风暴与故障是不同层次的概念。在一些实施例中，MDAF可以预测该网络未发生或出现故障。或者，MDAF可以确定该网络未发生或出现故障。或者，该网络未发生或出现故障。可以理解的是，告警不意味着故障发生，告警可能只是网络中存在异常，可以通过网络的自愈机制恢复，不会对网络造成影响。
S420，该第一装置获取网络阈值，该网络阈值用于指示该网络能够支持的信令数量。
信令数量可以是具体数量，也可以是相对数量。作为信令数量是具体数量的一个示例，信令数量可以为1000个。作为信令数量是相对值的一个示例，信令数量可以为某一基准的10倍。其中，上述基准可以是人工设置的，例如设置为100个。上述基准也可以是上一次信令风暴、信令风暴事件或故障发生时网络接收的信令的具体数量。上述基准也可以是某个时间点网络接收的信令的具体数量。上述时间点可以是具体时间点，例如过去的某个时刻，也可以是相对时间点，例如在执行S420的时间点起，一段时长(例如30天)以前的时间点。上述时长可以预先配置。需要说明的是，本申请对基准不做限定，还可以通过其他方式设置基准。
可以理解的是，在某个性能要求下，网络具有能够支持的最大信令数量。例如，在注册成功率为80％、单用户注册时长为10秒的情况下，网络能够支持的用户注册请求存在最大数量。在另一种表述中，网络阈值用于指示该网络在实现性能要求的情况下，能够处理的信令数量。或者，网络阈值用于指示该网络在性能条件下，能够处理的信令数量。其中，期望目标可以由第二装置或其他装置确定。
网络阈值可以用于指示网络能够支持的最大信令数量，也可以用于指示比网络能够支持的最大信令 数量小的信令数量。例如，网络能够支持的最大信令数量为1000个，网络阈值可以是1000个，也可以是小于1000个的任意数值。例如，网络能够支持的最大信令数量为10倍，网络阈值可以是10倍，也可以是小于10倍的任意数值。
网络能够支持的最大信令数量，也可以称为信令数量上升最大值，或者称为整网能够支持的最大信令冲击量，或者称为关键性能指标(key performance indicator，KPI)上升最大值(例如，网络能够支持的最大会话数，或者网络能够支持的最大用户注册请求数)。
可选地，在上述实施例的另一实施场景中，S420包括：该第一装置接收来自该第二装置的该网络阈值。
网络阈值可以携带在第一请求中，换言之，第一请求可以包括网络阈值。这样，第一装置可以根据第一请求确定网络阈值。或者说，第一装置可以从第一请求中获取网络阈值。
但是本申请不限定第一装置接收网络阈值的具体方式，例如，网络阈值还可以携带在其他消息中，换言之，其他消息可以包括网络阈值。这样，第一装置可以根据其他消息确定网络阈值。或者说，第一装置可以从其他消息中获取网络阈值。
第一装置接收来自该第二装置的该网络阈值，可以理解为第一装置接收用于指示该网络阈值的信息。
基于上述方案，网络阈值可以是第二装置发送给第一装置的，这样，第一装置可以根据第二装置需求的网络阈值预测信令风暴事件是否存在，从而达成第二装置对预防信令风暴的期望目标。
可选地，在上述实施例的另一实施场景中，S420包括：该第一装置根据网络中的多个网元的可用性(availability)参数，确定该网络阈值。
可用性参数也可以称为可用性指标。例如，多个网元包括第一网元、第二网元和第三网元。第一网元的可用性参数可以是在第一预设信令数量下的该第一网元的性能管理数据。第二网元的可用性参数可以是在第二预设信令数量下的该第二网元的性能管理数据。第三网元的可用性参数可以是在第三预设信令数量下的该第三网元的性能管理数据。
其中，第一预设信令数量、第二预设信令数量和第三预设信令数量可以是具体数量，也可以是相对数量。具体数量和相对数量的含义参见上面S420的实施例。第一预设信令数量、第二预设信令数量和第三预设信令数量可以全部相同、部分相同或全部不同。下面以第一预设信令数量为例，第二预设信令数量和第三预设信令数量的实施例可以参见第一预设信令数量的实施例。
第一预设信令数量可以设置为一个，也可以设置为多个。从而，第一网元的可用性参数可以是一个，也可以是多个。在第一网元的可用性参数是多个的情况下，第一网元的可用性参数可以用于指示第一网元在不同信令冲击下的性能管理数据或KPI。多个网元中的每个网元在理论上能够支持的最大信令数量。第一预设信令数量可以是第一网元能够支持的最大信令数量，也可以是比能够支持的最大信令数量小的信令数量。例如，第一网元能够支持的最大信令数量为500，第一预设信令数量可以是500，也可以是小于500的任意数值。例如，第一网元能够支持的最大信令数量为5倍，第一预设信令数量可以是5倍，也可以是小于5倍的任意数值。
上面仅以多个网元包括第一网元、第二网元和第三网元举例，本申请对此不限定。例如，多个网元可以包括更多或更少的网元。
性能管理数据可以是PM。例如，在第一网元为AMF的情况下，第一网元的性能管理数据可以是注册用户数、注册成功率、单个用户的注册时长、最大注册时长等。可以理解的是，性能管理数据还可以包括其他参数。例如，多个用户的平均注册时长、多个用户的最大注册时长、注册失败数等。
一个网元的可用性参数越低，表明该网元能够支持的信令数量越低。一个网元的可用性参数越高，表明该网元能够支持的信令数量越高。或者说，一个网元在信令数量较高的情况下，可用性参数较低，表明该网元可能不能满足期望目标。一个网元在信令数量较高的情况下，可用性参数较高，表明该网元可能满足期望目标。
第一装置综合分析网络中的多个网元的可用性参数，可以确定网络能够支持的信令数量，即网络阈值。本申请对根据可用性参数确定网络阈值的具体方式不做限定，例如可以根据人工智能(artificial intelligent，AI)算法，也可以根据其他算法。
S430，该第一装置根据该网络阈值和该网络的当前信令数量，确定第一报告，该第一报告用于指示存在该信令风暴事件。
当前信令数量是相对于历史信令数量的概念。当前信令数量可以是执行S430时的信令数量，也可以 是执行S410或S420时的信令数量。历史信令数量是过去一段时间的信令数量，例如，历史信令数量可以是信令的相对数量的“基准”。也就是说，上述基准也可以是上一次信令风暴、信令风暴事件或故障发生时网络接收的信令的具体数量。历史信令数量可以是某个时间点网络接收的信令的具体数量。上述时间点可以是具体时间点，例如过去的某个时刻，也可以是相对时间点，例如在执行S430的时间点起，一段时长(例如30天)以前的时间点。上述时长可以预先配置。需要说明的是，本申请对基准不做限定，还可以通过其他方式设置基准。
作为一个示例，该网络阈值是该网络能够支持的信令的具体数量，其中，S430包括：在该当前信令数量大于或等于该网络阈值的情况下，该第一装置确定存在该信令风暴事件。
作为另一个示例，该网络阈值是该网络能够支持的信令的相对数量，其中，S430包括：该第一装置获取该网络的历史信令数量。在该当前信令数量相对于该历史信令数量的倍数大于或等于该网络阈值的情况下，该第一装置确定存在该信令风暴事件。
当前信令数量可以包括用户注册请求信令的数量、会话(session)的数量等。本申请对此不限定。
需要说明的是，本申请不限定确定第一报告的具体方式，除了上述两个举例，还可以采用其他方式确定第一报告。例如，可以采用AI算法或其他算法确定第一报告。
另外，本申请不限定第一报告的具体名称，第一报告也可以有其他名称，例如指示信息、报告信息、反馈信息、反馈列表等。第一报告是一种信息的名称。
第一报告可以指示存在该信令风暴事件。或者，第一报告可以指示信令风暴事件发生或出现。或者，第一报告可以指示该网络具有发生信令风暴的风险。
作为S430的一个替换，方法400可以包括：该第一装置根据该网络阈值和该网络的当前信令数量，确定另一个报告，该另一个报告用于指示不存在该信令风暴事件。该实施例的具体细节与对S430相关的实施例的描述相反。
基于上述方案，第一装置可以根据网络能够支持的信令数量和网络的当前信令数量，确定网络具有发生信令风暴的风险，从而能够预测信令风暴的发生。
可选地，在上述实施例的另一实施场景中，该方法430还包括：该第一装置向该第一装置发送第一报告。相应地，该第二装置接收来自该第一装置的第一报告。
第一装置向该第二装置发送第一报告，可以理解为第一装置向该第二装置发送用于指示该第一报告的信息。第一报告可以承载于任意消息中。本申请不限定第一报告的具体名称，第一报告也可以有其他名称，例如指示信息、报告信息、反馈信息、反馈列表等。第一报告是一种信息的名称。
可选地，在上述实施例的另一实施场景中，该第一报告包括异常网元信息、类型信息、原因信息、比值信息或持续时间信息中的至少一项，其中，该异常网元信息用于指示该信令风暴事件发生时流量异常的网元，该类型信息用于指示事件类型为信令风暴，该原因信息用于指示该信令风暴事件的产生原因，该比值信息用于指示该网络的当前信令数量与历史信令数量的比值，该持续时间信息用于指示该信令风暴事件的预测的持续时间。
第一装置可以根据KPI等PM数据确定异常网元信息、类型信息、原因信息、比值信息或持续时间信息中的至少一项。例如，可以通过AI算法或其他算法。
表1示出了第一报告的一个实施例。需要说明的是，表1仅是举例，不构成对本申请的限定。例如，第一报告可以包括比表1更多或更少的信息。又例如，第一报告可以用其他信息替换表1中的任意信息。
表1第一报告的信元(information element，IE)
异常网元信息可以承载于故障预测目标对应的字段。例如，故障预测目标可以指示信令风暴事件发生时流量异常的网元。其中，流量异常的网元在信令风暴事件发生时的可用性参数低于预设阈值。或者， 对网络中的多个网元在信令风暴事件发生时的可用性参数按照从高到低进行排序，流量异常的网元是其中排序中较低的网元。
类型信息可以承载于潜在故障类型对应的字段。这样，潜在故障类型可以用于指示事件类型为信令风暴。根据类型信息，第二装置能够确定(或者说知道)信令风暴事件发生。换言之，类型信息可以用于指示信令风暴事件发生或出现。或者说，类型信息可以用于指示信令风暴事件存在。潜在故障类型还可以用于指示其他类型，例如设备故障(equipment alarm)、软件或处理故障(processing error alarm)、服务质量下降类型的故障(quality of service alarm)或安全攻击类型的故障(security service or mechanism violation)等。
事件发生时刻可以用于指示信令风暴事件的发生时刻或时间点。例如，第一装置在A时刻确定信令风暴事件发生，事件发生时刻可以用于指示A时刻。事件标识可以用于指示信令风暴事件的标识。感知严重性可以用于指示信令风暴事件的严重程度。例如，感知严重性可以分为高、中、低三个层次，其中，感知严重性为高指示信令风暴事件的严重程度较高。
原因信息可以承载于信令风暴的根本原因对应的字段。例如，原因信息可以指示网络中断、灾害或故障等信令风暴的发生原因。
比值信息可以承载于KPI变化对应的字段。例如，当前信令数量与历史信令数量的比值为10，或者说，当前信令数量相对于历史信令数量的倍数为10倍，则比值信息或KPI变化可以用于指示10。
持续时间信息可以承载于信令风暴持续时间对应的字段。例如，持续时间信息可以指示1000分钟，表明信令风暴事件的持续时间是1000分钟。信令风暴的自愈机制往往需要较长时间，因此需要预防信令风暴的发生。
本申请不限定第一报告的具体名称，第一报告也可以有其他名称，例如指示信息、报告信息、反馈信息、反馈列表等。第一报告是一种信息的名称。
基于上述方案，第二装置可以根据第一报告中的信息对网络进行改进，从而有助于第二装置预防信令风暴的发生。
可选地，在上述实施例的另一实施场景中，该方法400还包括：该第一装置向该第二装置发送该网络能够支持的最大信令数量。相应地，该第二装置接收来自该第一装置的该网络能够支持的最大信令数量。
例如，第一装置可以根据网络中的多个网元的可用性参数，确定网络能够支持的最大信令数量。本申请不限定确定网络能够支持的最大信令数量的具体方式，例如可以通过AI算法，也可以通过其他算法。
第一装置向二装置发送网络能够支持的最大信令数量，可以理解为第一装置向二装置发送用于指示网络能够支持的最大信令数量的信息。
基于上述方案，第一装置可以向第二装置发送网络能够支持的最大信令数量，使得第二装置能够获取网络能够支持的最大信令数量。第二装置可以根据网络能够支持的最大信令数量对网络进行改进，从而有助于第二装置预防信令风暴的发生。
可选地，在上述实施例的另一实施场景中，该方法400还包括：该第二装置根据该网络能够支持的最大信令数量，确定该网络阈值。
作为一个示例，第二装置可以确定网络阈值为网络能够支持的最大信令数量。作为另一个示例，第二装置可以确定比网络能够支持的最大信令数量小的信令数量作为网络阈值。
基于上述方案，第二装置可以根据网络能够支持的最大信令数量确定网络阈值。这样，第一装置可以根据第二装置需求的网络阈值预测信令风暴事件是否存在，从而达成第二装置对预防信令风暴的期望目标。
可选地，在上述实施例的另一实施场景中，该网络阈值小于该网络能够支持的最大信令数量。
例如，网络能够支持的最大信令数量为1000个，网络阈值可以是800个。又例如，网络能够支持的最大信令数量为10倍，网络阈值可以是8倍。
可以理解的是，如果网络阈值等于网络能够支持的最大信令数量，那么在当前信令数量接近网络能够支持的最大信令数量的情况下，第一装置可以确定信令风暴事件存在。在这种情况下，网络发生信令风暴的风险较大，甚至可能发生故障。如果网络阈值小于该网络能够支持的最大信令数量，那么在当前信令数量小于网络能够支持的最大信令数量的情况下，第一装置可以确定信令风暴事件存在。在这种情况下，网络发生信令风暴的风险较小，发生故障的风险更小，从而提高预防信令风暴的效果。
基于上述方案，网络阈值小于该网络能够支持的最大信令数量，使得第一装置在网络发生信令风暴的风险较小的情况下，确定信令风暴事件存在。进而，上述方案使得第二装置在信令风暴的风险较小的情况下可以对网络进行改进，从而提高预防信令风暴的效果。
可选地，在上述实施例的另一实施场景中，该方法400还包括：该第一装置根据该网络中的多个网元的可用性参数，确定该网络能够支持的最大信令数量，其中，该网络中的多个网元包括第一网元，该第一网元的可用性参数是在第一预设信令数量下的该第一网元的性能管理数据。
可用性参数也可以称为可用性指标。第一预设信令数量可以是具体数量，也可以是相对数量。具体数量和相对数量的含义参见上面S420的实施例。
第一预设信令数量可以是第一网元能够支持的最大信令数量，也可以是比能够支持的最大信令数量小的信令数量。例如，第一网元能够支持的最大信令数量为500，第一预设信令数量可以是500，也可以是小于500的任意数值。例如，第一网元能够支持的最大信令数量为5倍，第一预设信令数量可以是5倍，也可以是小于5倍的任意数值。
性能管理数据可以是PM。例如，在第一网元为AMF的情况下，第一网元的性能管理数据可以是注册用户数、注册成功率、单个用户的注册时长、最大注册时长等。可以理解的是，性能管理数据还可以包括其他参数。例如，多个用户的平均注册时长、多个用户的最大注册时长、注册失败数等。
一个网元的可用性参数越低，表明该网元能够支持的信令数量越低。一个网元的可用性参数越高，表明该网元能够支持的信令数量越高。或者说，一个网元在信令数量较高的情况下，可用性参数较低，表明该网元可能不能满足期望目标。一个网元在信令数量较高的情况下，可用性参数较高，表明该网元可能满足期望目标。
第一装置综合分析网络中的多个网元的可用性参数，可以确定网络能够支持的最大信令数量。本申请对根据可用性参数确定该网络能够支持的最大信令数量的具体方式不做限定，例如可以根据AI算法，也可以根据其他算法。
基于上述方案，第一装置可以确定该网络能够支持的最大信令数量，使得第二装置能够获取网络能够支持的最大信令数量。第二装置可以根据网络能够支持的最大信令数量对网络进行改进，从而有助于第二装置预防信令风暴的发生。
可选地，在上述实施例的另一实施场景中，该方法400还包括：该第一装置获取该第一网元的性能管理数据和该第一网元的虚拟资源使用信息；该第一装置根据该第一网元的性能管理数据和该第一网元的虚拟资源使用信息，确定该第一网元的可用性参数。
示例性地，第一装置可以从NFV MANO 340获取第一网元的性能管理数据和虚拟资源使用信息。例如，第一装置可以向NFV MANO 340发送请求消息，请求获取第一网元的性能管理数据和虚拟资源使用信息。NFV MANO 340可以根据请求消息，向第一网元发送第一网元的性能管理数据和虚拟资源使用信息。
性能管理数据可以是PM。例如，在第一网元为AMF的情况下，第一网元的性能管理数据可以是注册用户数、注册成功率、单个用户的注册时长、最大注册时长等。可以理解的是，性能管理数据还可以包括其他参数。例如，多个用户的平均注册时长、多个用户的最大注册时长、注册失败数等。
虚拟资源使用信息可以用于指示虚拟资源的使用情况。虚拟资源可以包括虚拟处理器(virtual processor)、虚拟内存(virtual memory)或虚拟磁盘(virtual disk)中的至少一项。虚拟资源还可以包括其他资源。虚拟资源使用信息可以包括虚拟处理器利用率、虚拟内存利用率、虚拟磁盘利用率等。虚拟资源使用信息还可以包括其他信息。
本申请对根据性能管理数据和虚拟资源使用信息确定可用性参数的具体方式不做限定，例如可以根据AI算法，也可以根据其他算法。需要说明的是，上面仅以第一网元为例，本申请实施例还可以确定其他网元的可用性参数。例如，第一装置可以根据第二网元的性能管理数据和第二网元的虚拟资源使用信息，确定该第二网元的可用性参数。
基于上述方案，第一装置可以确定网元的可用性参数。可用性参数是网元在预设信令数量下的性能管理数据，因此，网元的可用性参数能够描述网元在信令冲击下的可用性，有助于预防信令风暴的发生。
可选地，在上述实施例的另一实施场景中，该方法400还包括：该第一装置向该第二装置发送该第一网元的可用性参数。相应地，该第二装置接收来自该第一装置的该第一网元的可用性参数，该第一网元的可用性参数是在第一预设信令数量下的该第一网元的性能管理数据。
基于上述方案，第一装置可以将网元的可用性参数发送给第二装置。可用性参数是网元在预设信令数量下的性能管理数据，因此，网元的可用性参数能够描述网元在信令冲击下的可用性，有助于第二装置预防信令风暴的发生。
可选地，在上述实施例的另一实施场景中，该方法400还包括：该第二装置根据该第一网元的可用性参数，配置该第一网元。
例如，第二装置可以向第一网元发送配置信息，该配置信息包括第一网元的可用性参数。
基于上述方案，第二装置可以将可用性参数配置到网元上。可用性参数是网元在预设信令数量下的性能管理数据，因此，网元的可用性参数能够描述网元在信令冲击下的可用性，有助于网元预防信令风暴的发生。
可选地，在上述实施例的另一实施场景中，该方法400还包括：该第一装置接收来自该第二装置的第二请求，该第二请求用于请求该第一装置确定该网络中的多个网元的可用性参数。相应地，该第二装置向该第一装置发送第二请求。
示例性地，第二请求可以包括网元标识(或称为网元类型)和目标信令类型。例如，第二请求包括AMF的标识和注册请求，这样，第一装置可以根据该第二请求确定AMF在一定数量的注册请求下的可用性参数。
第二请求可以是任意请求，第二请求可以承载于任意消息中。第二请求还可以有其他名称，例如网元能力评估请求或网元可用性评估请求等，本申请对此不限定。
第二请求可以是由某个事件触发的，例如节假日事件、网络升级事件等。换言之，在某个事件发生时，第二装置可以向第一装置发送第二请求。第二请求也可以是第二装置主动发送的，换言之，第二装置发送第二请求不依赖其他事件的触发。
基于上述方案，第一装置可以请求第二装置确定网元的可用性参数。可用性参数是网元在预设信令数量下的性能管理数据，网元的可用性参数能够描述网元在信令冲击下的可用性。因此，上述方案有助于达成第二装置对预防信令风暴的期望目标。
可选地，在上述实施例的另一实施场景中，该网络中的多个网元还包括第二网元，其中，该方法400还包括：该第一装置获取该第二网元的可用性参数，该第二网元的可用性参数是在第二预设信令数量下的该第二网元的性能管理数据，该第二网元为瓶颈网元，其中，在该信令风暴发生时，该第二网元的可用性参数不满足期望目标；该第一装置根据该第二网元的可用性参数确定第二报告，其中，该第二报告用于指示对该第二网元扩容。相应地，该第二装置接收来自该第一装置的该第二报告。
作为一个示例，第一装置可以根据第二网元的性能管理数据和第二网元的虚拟资源使用信息，确定该第二网元的可用性参数，从而实现了第一装置获取第二网元的可用性参数。作为另一个示例，第一装置可以从NFV MANO 340或第二装置获取第二网元的可用性参数。第二网元可能已经配置了可用性参数，这样，第一装置可以向NFV MANO 340或第二装置发送请求消息，请求NFV MANO 340或第二装置反馈第二网元的可用性参数。NFV MANO 340或第二装置查询第二网元的配置信息，从而获取第二网元的可用性参数，并将该第二网元的可用性参数向第一装置发送。第一装置接收来自NFV MANO 340或第二装置的第二网元的可用性参数，从而实现了第一装置获取第二网元的可用性参数。
第一装置可以根据网络中的多个网元的可用性参数确定第二网元为瓶颈网元。例如，若第二网元的可用性参数小于其他网元的可用性参数，则可以确定第二网元为瓶颈网元。其中，瓶颈网元可以是一个或多个网元。
在一些实施例中，期望目标包括解决信令风暴的期望时长和/或网络能够支持的最大用户数。
基于上述方案，期望目标可以包括解决信令风暴的期望时长和/或网络能够支持的最大用户数。第二装置根据上述期望目标为网元提供改进建议，使得网元能够满足期望目标中的期望时长和最大用户数，从而增强了网络的可用性。
对于可用性参数不满足期望目标的网元，可以称为瓶颈网元，瓶颈网元是网络的多个网元中抵抗信令冲击较弱的网元。在信令风暴发生时，瓶颈网元的可用性参数不满足期望目标。因此，瓶颈网元不能满足解决信令风暴的期望时长，或者不能满足要求网络支持的最大用户数。这样，对瓶颈网元进行采取流量控制等其他手段，并不能使得瓶颈网元满足期望目标。此时，对瓶颈网元进行扩容可以避免信令风暴的发生。
对该第二网元扩容，可以理解为增加第二网元的虚拟资源，例如增加第二网元的虚拟处理器的输入 输出上限、虚拟内存的容量或虚拟磁盘的容量。
在一些实施例中，第一装置根据该第二网元的可用性参数和期望目标确定第二报告。
作为一个示例，第一装置可以根据该第二网元的可用性参数和收敛信息确定第二报告。其中，收敛信息用于指示信令风暴发生后，网络处理完该网络在预设时间窗内接收到的信令的期望时长。
例如，预设事件窗可以是180秒，在信令风暴发生后的180秒内，网络接收到了来自终端设备的多个连接请求，收敛信息可以指示网络处理完这些连接请求所花费的时长为200秒。收敛信息指示的期望时长可以在预设时间窗的开始时刻起算，换言之，可以在信令风暴发生的时刻起算。例如，在收敛信息指示的期望时长小于或等于时长阈值时，第一装置为了使网络更快地达成第二装置期望解决信令风暴的期望时长，可以建议第二装置对第二网元进行扩容。其中，时长阈值可以预先设定。
作为另一个示例，第一装置可以根据该第二网元的可用性参数、用户数信息和收敛信息确定第二报告。其中，用户数信息用于指示信令风暴发生后，网络能够处理的该网络在预设时间窗内接收到的用户上线请求的数量。即，用户数信息可以用于指示网络能够支持的最大用户数。
作为将用户数信息和收敛信息结合的举例，在信令风暴发生后的180秒内，网络接收到了来自终端设备的多个用户上线请求，第二网元期望网络能够在200秒内处理完100个用户上限请求。可以理解的是，用户数信息可以是来自第二装置的。也就是说，在一些实施例中，第二装置向第一装置发送用户数信息，相应地，第一装置接收来自第二装置的用户数信息。因此，用户数信息属于第二装置的期望目标。
第一报告指示的对该第二网元扩容的建议可以称为扩容建议(scaling recommendation)。需要说明的是，第二报告、收敛信息、用户数信息还可以有其他名称，本申请对此不限定。
基于上述方案，在第二网元为瓶颈网元的情况下，第一装置可以建议第二装置对第二网元进行扩容，从而预防信令风暴的发生。
在另一些实施例中，第二报告还可以包括流控建议(flow control recommendation)。例如，流控建议可以指示为第三网元配置新的流量控制参数。表2是建议报告的一种举例。
表2建议报告的IE
其中，指示对第三网元进行流控配置的建议信息可以承载于流控网元的流控配置建议中，指示对第二网元进行扩容的建议信息可以承载于对瓶颈网元的扩容建议中。
可选地，在上述实施例的另一实施场景中，该方法400还包括：该第一装置接收来自该第二装置的第三请求，其中，该第三请求包括该期望目标，该第三请求用于请求该第一装置为该网络中的网元提供建议。相应地，该第二装置向该第一装置发送第三请求。
第三请求可以是任意请求，第三请求可以承载于任意消息中。第三请求还可以有其他名称，例如信令风暴事件分析请求等，本申请对此不限定。作为一个示例，第三请求还可以携带网元的可用性参数。
基于上述方案，第一装置可以请求第二装置为网元提供改进建议，并且，请求中可以携带期望目标，从而有助于达成第二装置对预防信令风暴的期望目标。
可选地，在上述实施例的另一实施场景中，该方法400还包括：该第一装置注册第一MDAS和第二MDAS，其中，该第一MDAS对应的注册参数中的能力信息用于指示该第一MDAS能够确定是否存在该信令风暴事件，该第二MDAS对应的注册参数中的能力信息用于指示该第二MDAS能够为该网络中的网元提供建议。
第一装置可以向管理服务注册(management service，MnS)注册(registry)网元发送请求消息，请求创建第一MDAS的注册参数和第二MDAS的注册参数。管理服务注册网元接收请求消息后，根据请求消息创建第一MDAS的注册参数和第二MDAS的注册参数。表3示出了第一MDAS或第二MDAS的注册参数。
表3第一MDAS或第二MDAS的注册参数

其中，标签可以指示第一MDAS或第二MDAS的标识。类型可以包括MDAS，类型用于指示第一MDAS或第二MDAS的服务类型是MDAS。访问地址可以指示第一MDAS或第二MDAS的访问地址。管理范围指示第一MDAS或第二MDAS的管理范围，例如，管理范围对应于第一MDAS可以管理的子网(subnetwork)的标识。支持能力可以包括故障管理(fault management)、信令分析(signaling analysis)、预防评估等。支持能力可以用于指示MDAS所支持的能力信息。其中，故障管理可以用于指示该MDAS的能力支持确定是否存在该信令风暴事件，信令分析可以用于指示该MDAS的能力支持为该网络中的网元提供建议。对于故障管理能力，还可以进一步细分，例如可以分为支持信令拥塞类型的故障和不支持信令拥塞类型的故障。
注册参数中的能力信息承载于支持能力的字段中。例如，第一MDAS的支持能力可以为故障管理，并且支持信令拥塞类型的故障。第二MDAS的支持能力可以为信令分析。
基于上述方案，第二装置可以按照需求访问第一MDAS或第二MDAS的访问地址，避免第一装置识别第二装置的意图和调用相应的MDAS所造成的时延，提高了网络分析的效率。
可选地，在上述实施例的另一实施场景中，该方法400还包括：该第二装置查询该第一装置的注册参数；该第二装置接收第一管理数据分析服务MDAS的注册参数和第二MDAS的注册参数，该第一MDAS对应的注册参数中的能力信息用于指示该第一MDAS能够确定是否存在该信令风暴事件，该第二MDAS对应的注册参数中的能力信息用于指示该第二MDAS能够为该网络中的网元提供建议。
基于上述方案，第二装置可以按照需求访问第一MDAS或第二MDAS的访问地址，避免第一装置识别第二装置的意图和调用相应的MDAS所造成的时延，提高了网络分析的效率。
图5是本申请实施例提供的一种注册方法500的示意性流程图。下面结合图5描述方法500。
S510，MDAF 320向MnS注册网元发送请求消息，请求消息用于请求创建注册参数。相应地，MnS注册网元接收来自MDAF 320的请求消息。
其中，MDAF 320可以是第一装置。注册参数可以是第一MDAS或第二MDAS的注册参数。注册参数也可以称为MnS信息(information，Info)。
S520，MnS注册网元创建注册参数，以完成注册。
例如，注册参数可以是第一MDAS或第二MDAS的注册参数。注册参数可以包括标签、类型、版本、访问地址、管理范围、支持能力中的至少一项，具体参见表3相关的实施例。
图6是本申请实施例提供的一种注册参数查询方法600的示意性流程图。下面结合图6描述方法600。
S610，OSS 310向MnS注册网元发送查询消息，该查询消息用于请求查询注册参数。相应地，MnS注册网元接收来自OSS 310的查询消息。
其中，OSS 310可以是第二装置。
S620，MnS注册网元向OSS 310发送注册参数。相应地，OSS 310接收来自MnS注册网元的注册参数。
示例性地，注册参数可以包括第一MDAS和/或第二MDAS的注册参数。注册参数可以包括标签、类型、版本、访问地址、管理范围、支持能力中的至少一项，具体参见表3相关的实施例。注册参数还可以包括其他服务的注册参数，本申请不限定。
图7是本申请实施例提供的一种网元能力评估方法700的示意性流程图。下面结合图7描述方法700。
S710，OSS 310向MDAF 320发送第二请求，该第二请求用于请求MDAF 320确定网络中的多个网元的可用性参数。
示例性地，第二请求可以包括网元标识(或称为网元类型)和目标信令类型。例如，第二请求包括AMF的标识和注册信令，这样，第一装置可以根据该第二请求确定AMF在一定数量的注册信令下的可用性参数。第二请求可以是任意请求，第二请求可以承载于任意消息中。第二请求还可以有其他名称，例如网元能力评估请求或网元可用性评估请求等，本申请对此不限定。第二请求可以是由某个事件触发的，例如节假日事件、网络升级事件等。换言之，在某个事件发生时，OSS 310可以执行S710。第二请求也可以是OSS 310主动发送的，换言之，OSS 310可以主动执行S710，并不依赖其他事件的触发。
S720，MDAF 320接收来自NFV MANO 340的性能管理数据和虚拟资源使用信息。相应地，NFV MANO 340向MDAF 320发送性能管理数据和虚拟资源使用信息。
性能管理数据可以是PM，例如，在第一网元为AMF的情况下，第一网元的性能管理数据可以包括 注册数、注册成功率、单个用户的注册时长等。可以理解的是，性能管理数据还可以包括其他参数。例如，多个用户的平均注册时长、多个用户的最大注册时长、注册失败数等。
虚拟资源使用信息可以用于指示虚拟资源的使用情况。虚拟资源可以包括虚拟处理器、虚拟内存或虚拟磁盘中的至少一项。虚拟资源还可以包括其他资源。虚拟资源使用信息可以包括虚拟处理器利用率、虚拟内存利用率、虚拟磁盘利用率等。虚拟资源使用信息还可以包括其他信息。
在一些实施例中，在S720之前，方法700还包括：NFV MANO 340接收来自MDAF 320请求消息，该请求消息用于请求性能管理数据和虚拟资源使用信息。相应地，MDAF 320向NFV MANO 340发送请求消息。
S730，MDAF 320根据性能管理数据和虚拟资源使用信息，确定网元的可用性参数。
网元的可用性参数是在预设信令数量下的该网元的性能管理数据。可用性参数也可以称为可用性指标。预设信令数量可以是具体数量，也可以是相对数量。
S740，MDAF 320向OSS 310发送网元的可用性参数。相应地，OSS 310接收来自MDAF 320的网元的可用性参数。
进一步地，OSS 310可以根据网元的可用性参数对网元进行配置。
图8是本申请实施例提供的一种网络能力评估方法800的示意性流程图。下面结合图8描述方法800。
S810，OSS 310向MDAF 320发送第四请求，该第四请求用于请求确定网络能够支持的最大信令数量和瓶颈网元。
示例性地，第四请求可以包括网络范围标识和目标信令类型。其中，网络范围标识可以是子网标识(subnetwork ID)或多个网元的标识。或者是具体的子网位置信息。
第四请求可以是任意请求，第四请求可以承载于任意消息中。第四请求还可以有其他名称，例如网络能力评估请求或网络可用性评估请求等，本申请对此不限定。
第四请求可以是由某个事件触发的，例如节假日事件、网络升级事件等。换言之，在某个事件发生时，OSS 310可以执行S810。第四请求也可以是OSS 310主动发送的，换言之，OSS 310可以主动执行S810，并不依赖其他事件的触发。
S820，MDAF 320获取网络中的多个网元的可用性参数。
在一些实施例中，MDAF 320可以在网元的配置信息中获取该网元的可用性参数。例如，MDAF 320可以向NFV MANO 340或OSS 330发送请求消息，请求NFV MANO 340或OSS 330反馈第二网元的可用性参数。NFV MANO 340或OSS 330查询第二网元的配置信息，从而获取第二网元的可用性参数，并将该第二网元的可用性参数向MDAF 320发送。MDAF 320接收来自NFV MANO 340或OSS 330的第二网元的可用性参数，从而实现了MDAF 320获取第二网元的可用性参数。如果网元没有配置可用性参数，可以执行S720和S730，确定可用性参数。又例如，MDAF 320可以根据网元的性能管理数据和虚拟资源使用信息，确定网元的可用性参数，从而实现了获取各个网元的可用性参数。
S830，MDAF 320根据网络中的多个网元的可用性参数，确定瓶颈网元和网络能够支持的最大信令数量。
S840，MDAF 320向OSS 310发送网络能够支持的最大信令数量。相应地，OSS 310接收来自MDAF 320的网络能够支持的最大信令数量。
在一些实施例中，方法800还包括：MDAF 320向OSS 310发送瓶颈网元的信息。相应地，OSS 310接收来自MDAF 320的瓶颈网元的信息。
图9是本申请实施例提供的一种信令风暴事件发现方法900的示意性流程图。下面结合图9描述方法900。
S910，OSS 310向第一MDAS发送第一请求，第一请求用于请求第一MDAS确定是否存在信令风暴事件，该信令风暴事件用于指示网络具有发生信令风暴的风险。具体可以参见S410的实施例，此处不赘述。
第一请求可以携带网络阈值。例如，S830中，OSS 310接收来自MDAF 320的网络能够支持的最大信令数量为10倍，OSS 310发送的第一请求中的网络阈值可以为8倍。需要说明的是，以上仅仅是举例，不构成对本申请的限定。
S920，第一MDAS接收来自NFV MANO 340的网络的当前信令数量。相应地，NFV MANO 340向第一MDAS发送网络的当前信令数量。
在一些实施例中，在S920之前，方法900还包括：NFV MANO 340接收来自第一MDAS的请求消息，该请求消息用于请求网络的当前信令数量。相应地，第一MDAS向NFV MANO 340发送请求消息。
S930，第一MDAS根据网络的当前信令数量和网络阈值，确定第一报告，该第一报告用于指示存在信令风暴事件。
S940，第一MDAS向OSS 310发送第一报告。相应地，OSS 310接收来自第一MDAS的第一报告。
图10是本申请实施例提供的一种信令风暴事件分析方法1000的示意性流程图。下面结合图10描述方法1000。
S1010，OSS 310向第二MDAS发送第三请求，该第三请求用于请求第二MDAS为该网络中的网元提供建议。
S1020，第二MDAS接收来自NFV MANO 340的性能管理数据和虚拟资源使用信息。相应地，NFV MANO 340向第二MDAS发送性能管理数据和虚拟资源使用信息。
性能管理数据可以是PM，例如，在第一网元为AMF的情况下，第一网元的性能管理数据可以包括注册数、注册成功率、单个用户的注册时长等。可以理解的是，性能管理数据还可以包括其他参数。例如，多个用户的平均注册时长、多个用户的最大注册时长、注册失败数等。
虚拟资源使用信息可以用于指示虚拟资源的使用情况。虚拟资源可以包括虚拟处理器、虚拟内存或虚拟磁盘中的至少一项。虚拟资源还可以包括其他资源。虚拟资源使用信息可以包括虚拟处理器利用率、虚拟内存利用率、虚拟磁盘利用率等。虚拟资源使用信息还可以包括其他信息。
在一些实施例中，在S1020之前，方法1000还包括：NFV MANO 340接收来自第二MDAS请求消息，该请求消息用于请求性能管理数据和虚拟资源使用信息。相应地，第二MDAS向NFV MANO 340发送请求消息。
S1030，第二MDAS根据性能管理数据和虚拟资源使用信息，确定第二报告。第二报告用于指示对网元扩容。
S1040，第二MDAS向OSS 310发送第二报告。相应地，OSS 310接收来自第二MDAS的第二报告。
图11是本申请实施例提供的另一种网络分析方法1100的示意性流程图。方法1100可以是方法900和方法1000的结合，不同之处在于，方法1100不区分第一MDAS和第二MDAS，将第一MDAS和第二MDAS合并为MDAF 320。下面结合图11描述方法1100。
S1110，OSS 310向MDAF 320发送第一请求，第一请求用于请求MDAF 320确定是否存在信令风暴事件，该信令风暴事件用于指示网络具有发生信令风暴的风险。具体可以参见S410的实施例，此处不赘述。
第一请求可以携带网络阈值。例如，S830中，OSS 310接收来自MDAF 320的网络能够支持的最大信令数量为10倍，OSS 310发送的第一请求中的网络阈值可以为8倍。需要说明的是，以上仅仅是举例，不构成对本申请的限定。
S1120，MDAF 320接收来自NFV MANO 340的网络的当前信令数量。相应地，NFV MANO 340向MDAF 320发送网络的当前信令数量。
在一些实施例中，在S1120之前，方法1100还包括：NFV MANO 340接收来自MDAF 320的请求消息，该请求消息用于请求网络的当前信令数量。相应地，MDAF 320向NFV MANO 340发送请求消息。
S1130，MDAF 320根据网络的当前信令数量和网络阈值，确定第一报告，该第一报告用于指示存在信令风暴事件。
S1140，MDAF 320向OSS 310发送第一报告。相应地，OSS 310接收来自MDAF 320的第一报告。
S1150，OSS 310向MDAF 320发送第三请求，该第三请求用于请求MDAF 320为该网络中的网元提供建议。
S1160，MDAF 320接收来自NFV MANO 340的性能管理数据和虚拟资源使用信息。相应地，NFV MANO 340向MDAF 320发送性能管理数据和虚拟资源使用信息。
性能管理数据可以是PM，例如，在第一网元为AMF的情况下，第一网元的性能管理数据可以包括注册数、注册成功率、单个用户的注册时长等。可以理解的是，性能管理数据还可以包括其他参数。例如，多个用户的平均注册时长、多个用户的最大注册时长、注册失败数等。
虚拟资源使用信息可以用于指示虚拟资源的使用情况。虚拟资源可以包括虚拟处理器、虚拟内存或虚拟磁盘中的至少一项。虚拟资源还可以包括其他资源。虚拟资源使用信息可以包括虚拟处理器利用率、 虚拟内存利用率、虚拟磁盘利用率等。虚拟资源使用信息还可以包括其他信息。
在一些实施例中，在S1160之前，方法1100还包括：NFV MANO 340接收来自MDAF 320请求消息，该请求消息用于请求性能管理数据和虚拟资源使用信息。相应地，MDAF 320向NFV MANO 340发送请求消息。
S1170，MDAF 320根据性能管理数据和虚拟资源使用信息，确定第二报告。第二报告用于指示对网元扩容。
S1180，MDAF 320向OSS 310发送第二报告。相应地，OSS 310接收来自MDAF 320的第二报告。
下文对本申请方法实施例对应的装置实施例进行介绍。下文仅对装置做简要介绍，方案具体实现步骤和细节可参考前文方法实施例。
为了实现本申请提供的方法中的各功能，终端设备、网络设备均可以包括硬件结构和/或软件模块，以硬件结构、软件模块、或硬件结构加软件模块的形式来实现上述各功能。上述各功能中的某个功能以硬件结构、软件模块、还是硬件结构加软件模块的方式来执行，取决于技术方案的特定应用和设计约束条件。
图12是本申请实施例的一种通信装置1200的示意框图。通信装置1200包括处理器1210和收发器1220，处理器1210和收发器1220可以通过总线1230相互连接。通信装置1200可以是第一装置，也可以是第二装置。
可选地，通信装置1200还可以包括存储器1240。存储器1240包括但不限于是随机存储记忆体(random access memory，RAM)、只读存储器(read-only memory，ROM)、可擦除可编程只读存储器(erasable programmable read only memory，EPROM)、或便携式只读存储器(compact disc read-only memory，CD-ROM)，该存储器1240用于相关指令及数据。
处理器1210可以是一个或多个中央处理器(central processing unit，CPU)。在处理器1210是一个CPU的情况下，该CPU可以是单核CPU，也可以是多核CPU。其中，处理器1210可以是信号处理器、芯片，或其他可以实现本申请方法的集成电路，或者前述处理器、芯片或集成电路中的用于处理功能的部分电路。另外，收发器1220也可以称为输入输出接口或通信接口，收发器1220用于信号或数据的输入或输出，也可以是输入输出电路。
当通信装置1200是第一装置时，示例性地，通信装置1200包括处理器1210和收发器1220。其中，收发器1220用于接收来自第二装置的第一请求，该第一请求用于请求该第一装置确定是否存在信令风暴事件，该信令风暴事件用于指示网络具有发生信令风暴的风险；处理器1210用于获取网络阈值，该网络阈值用于指示该网络能够支持的信令数量，以及用于根据该网络阈值和该网络的当前信令数量，确定第一报告，该第一报告用于指示存在该信令风暴事件。
当通信装置1200是第二装置时，示例性地，通信装置1200包括收发器1220。其中，收发器1220用于向第一装置发送第一请求，该第一请求用于请求该第一装置确定是否存在信令风暴事件，该信令风暴事件用于指示网络具有发生信令风暴的风险，以及用于接收来自该第一装置的第一报告，该第一报告用于指示存在该信令风暴事件。
上述描述仅是示例性描述。具体内容可以参见上述方法实施例所示的内容。图6中的各个操作的实现还可以对应参照图3至图11所示的方法实施例的相应描述。
图13是本申请实施例的另一种通信装置1300的示意框图。通信装置1300可以为第一装置或第二装置，也可以为第一装置或第二装置中的芯片或模块，用于实现上述实施例涉及的方法。通信装置1300包括收发单元1310。下面对该收发单元1310进行示例性地介绍。
收发单元1310可以包括发送单元和接收单元。发送单元用于执行通信装置的发送动作，接收单元用于执行通信装置的接收动作。为便于描述，本申请实施例将发送单元与接收单元合为一个收发单元。在此做统一说明，后文不再赘述。
当通信装置1300是第一装置，示例性地，收发单元1310用于接收来自第二装置的第一请求。
可选地，通信装置1300还可以包括处理单元1320，其用于执行第一装置涉及处理、协调等步骤的内容。
当通信装置1300是第二装置，示例性地，该收发单元1310用于向第一装置发送第一请求。
可选地，通信装置1300还可以包括处理单元1320，其用于执行第二装置涉及处理、协调等步骤的内容。
上述所述内容仅作为示例性描述。通信装置1300是第一装置或者第二装置时，其将负责执行前述方法实施例中与第一装置或者第二装置相关的方法或者步骤。
可选地，通信装置1300还包括存储单元1330，该存储单元1330用于存储用于执行前述方法的程序或者代码。
图12和图13所示的装置实施例是用于实现图3至图11中的实施例。图12和图13所示装置的具体执行步骤与方法可以参见前述方法实施例的内容。
图14是本申请实施例的一种通信系统1400的示意框图。该通信系统1400包括第一装置和第二装置，第一装置和第二装置用于实现前述图3至图11的实施例。
本申请还提供了一种芯片，包括处理器，用于从存储器中调用并运行所述存储器中存储的指令，使得安装有所述芯片的通信装置执行上述各示例中的方法。
本申请还提供另一种芯片，包括：输入接口、输出接口、处理器，所述输入接口、输出接口以及所述处理器之间通过内部连接通路相连，所述处理器用于执行存储器中的代码，当所述代码被执行时，所述处理器用于执行上述各示例中的方法。可选地，该芯片还包括存储器，该存储器用于存储计算机程序或者代码。
本申请还提供了一种处理器，用于与存储器耦合，用于执行上述各实施例中任一实施例中涉及第一装置或者第二装置的方法和功能。
在本申请的另一实施例中提供一种包含指令的计算机程序产品，当该计算机程序产品在计算机上运行时，前述实施例的方法得以实现。
本申请还提供一种计算机程序，当该计算机程序在计算机中被运行时，前述实施例的方法得以实现。
在本申请的另一实施例中提供一种计算机可读存储介质，该计算机可读存储介质存储有计算机程序，该计算机程序被计算机执行时实现前述实施例所述的方法。
本领域普通技术人员可以意识到，结合本文中所公开的实施例描述的各示例的单元及算法步骤，能够以电子硬件、或者计算机软件和电子硬件的结合来实现。这些功能究竟以硬件还是软件方式来执行，取决于技术方案的特定应用和设计约束条件。专业技术人员可以对每个特定的应用来使用不同方法来实现所描述的功能，但是这种实现不应认为超出本申请的范围。
所属领域的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
在本申请所提供的几个实施例中，应该理解到，所揭露的系统、装置和方法，可以通过其它的方式实现。例如，以上所描述的装置实施例仅仅是示意性的，例如，所述单元的划分，仅仅为一种逻辑功能划分，实际实现时可以有另外的划分方式，例如多个单元或组件可以结合或者可以集成到另一个系统，或一些特征可以忽略，或不执行。另一点，所显示或讨论的相互之间的耦合或直接耦合或通信连接可以是通过一些接口，装置或单元的间接耦合或通信连接，可以是电性，机械或其它的形式。
所述作为分离部件说明的单元可以是或者也可以不是物理上分开的，作为单元显示的部件可以是或者也可以不是物理单元，即可以位于一个地方，或者也可以分布到多个网络单元上。可以根据实际的需要选择其中的部分或者全部单元来实现本实施例方案的目的。
另外，在本申请各个实施例中的各功能单元可以集成在一个处理单元中，也可以是各个单元单独物理存在，也可以两个或两个以上单元集成在一个单元中。
所述功能如果以软件功能单元的形式实现并作为独立的产品销售或使用时，可以存储在一个计算机可读取存储介质中。基于这样的理解，本申请的技术方案本质上或者说对现有技术做出贡献的部分或者该技术方案的部分可以以软件产品的形式体现出来，该计算机软件产品存储在一个存储介质中，包括若干指令用以使得一台计算机设备(可以是个人计算机，服务器，或者网络设备等)执行本申请各个实施例所述方法的全部或部分步骤。而前述的存储介质包括：U盘、移动硬盘、只读存储器(Read-Only Memory，ROM)、随机存取存储器(Random Access Memory，RAM)、磁碟或者光盘等各种可以存储程序代码的介质。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领域的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以所述权利要求的保护范围为准。

Claims (29)

  1. 一种网络分析方法，其特征在于，包括：
    第一装置接收来自第二装置的第一请求，所述第一请求用于请求所述第一装置确定是否存在信令风暴事件，所述信令风暴事件用于指示网络具有发生信令风暴的风险；
    所述第一装置获取网络阈值，所述网络阈值用于指示所述网络能够支持的信令数量；
    所述第一装置根据所述网络阈值和所述网络的当前信令数量，确定第一报告，所述第一报告用于指示存在所述信令风暴事件。
  2. 根据权利要求1所述的方法，其特征在于，所述第一报告包括异常网元信息、类型信息、原因信息、比值信息或持续时间信息中的至少一项，其中，所述异常网元信息用于指示所述信令风暴事件发生时流量异常的网元，所述类型信息用于指示事件类型为信令风暴，所述原因信息用于指示所述信令风暴事件的产生原因，所述比值信息用于指示所述网络的当前信令数量与历史信令数量的比值，所述持续时间信息用于指示所述信令风暴事件的预测的持续时间。
  3. 根据权利要求1或2所述的方法，其特征在于，所述第一装置获取网络阈值，包括：
    所述第一装置接收来自所述第二装置的所述网络阈值。
  4. 根据权利要求3所述的方法，其特征在于，还包括：
    所述第一装置向所述第二装置发送所述网络能够支持的最大信令数量。
  5. 根据权利要求4所述的方法，其特征在于，所述网络阈值小于所述网络能够支持的最大信令数量。
  6. 根据权利要求4或5所述的方法，其特征在于，还包括：
    所述第一装置根据所述网络中的多个网元的可用性参数，确定所述网络能够支持的最大信令数量，其中，所述网络中的多个网元包括第一网元，所述第一网元的可用性参数是在第一预设信令数量下的所述第一网元的性能管理数据。
  7. 根据权利要求6所述的方法，其特征在于，还包括：
    所述第一装置获取所述第一网元的性能管理数据和所述第一网元的虚拟资源使用信息；
    所述第一装置根据所述第一网元的性能管理数据和所述第一网元的虚拟资源使用信息，确定所述第一网元的可用性参数。
  8. 根据权利要求7所述的方法，其特征在于，还包括：
    所述第一装置向所述第二装置发送所述第一网元的可用性参数。
  9. 根据权利要求7或8所述的方法，其特征在于，还包括：
    所述第一装置接收来自所述第二装置的第二请求，所述第二请求用于请求所述第一装置确定所述网络中的多个网元的可用性参数。
  10. 根据权利要求1至9中任一项所述的方法，其特征在于，所述网络中的多个网元还包括第二网元，其中，所述方法还包括：
    所述第一装置获取所述第二网元的可用性参数，所述第二网元的可用性参数是在第二预设信令数量下的所述第二网元的性能管理数据，其中，在所述信令风暴发生时，所述第二网元的可用性参数不满足期望目标；
    所述第一装置根据所述第二网元的可用性参数确定第二报告，其中，所述第二报告用于指示对所述第二网元扩容。
  11. 根据权利要求10所述的方法，其特征在于，所述期望目标包括解决所述信令风暴的期望时长和/或所述网络能够支持的最大用户数。
  12. 根据权利要求10或11所述的方法，其特征在于，还包括：
    所述第一装置接收来自所述第二装置的第三请求，所述第三请求用于请求所述第一装置为所述网络中的网元提供建议，其中，所述第三请求包括所述期望目标。
  13. 根据权利要求10至12中任一项所述的方法，其特征在于，还包括：
    所述第一装置注册第一管理数据分析服务MDAS和第二MDAS，其中，所述第一MDAS对应的注册参数中的能力信息用于指示所述第一MDAS能够确定是否存在所述信令风暴事件，所述第二MDAS对应的注册参数中的能力信息用于指示所述第二MDAS能够为所述网络中的网元提供建议。
  14. 一种网络分析方法，其特征在于，包括：
    第二装置向第一装置发送第一请求，所述第一请求用于请求所述第一装置确定是否存在信令风暴事件，所述信令风暴事件用于指示网络具有发生信令风暴的风险；所述第二装置接收来自所述第一装置的第一报告，所述第一报告用于指示存在所述信令风暴事件。
  15. 根据权利要求14所述的方法，其特征在于，还包括：
    所述第二装置向所述第一装置发送网络阈值，所述网络阈值用于指示所述网络能够支持的信令数量。
  16. 根据权利要求15所述的方法，其特征在于，还包括：
    所述第二装置接收来自所述第一装置的所述网络能够支持的最大信令数量；
    所述第二装置根据所述网络能够支持的最大信令数量，确定所述网络阈值。
  17. 根据权利要求16所述的方法，其特征在于，所述网络阈值小于所述网络能够支持的最大信令数量或最大信令倍数。
  18. 根据权利要求14至17中任一项所述的方法，其特征在于，所述网络中的多个网元包括第一网元，其中，所述方法还包括：
    所述第二装置接收来自所述第一装置的所述第一网元的可用性参数，所述第一网元的可用性参数是在第一预设信令数量下的所述第一网元的性能管理数据；
    所述第二装置根据所述第一网元的可用性参数，配置所述第一网元。
  19. 根据权利要求18所述的方法，其特征在于，还包括：
    所述第二装置向所述第一装置发送第二请求，所述第二请求用于请求所述第一装置确定所述网络中的多个网元的可用性参数。
  20. 根据权利要求14至19中任一项所述的方法，其特征在于，所述网络中的多个网元还包括第二网元，其中，所述方法还包括：
    所述第二装置接收来自所述第一装置的第二报告，所述第二报告用于指示对所述第二网元扩容，其中，在所述信令风暴发生时，所述第二网元的可用性参数不满足期望目标。
  21. 根据权利要求20所述的方法，其特征在于，所述期望目标包括解决所述信令风暴的期望时长和/或所述网络能够支持的最大用户数。
  22. 根据权利要求20或21所述的方法，其特征在于，第三请求包括所述期望目标，所述第三请求用于请求所述第一装置为所述网络中的网元提供建议，其中，所述方法还包括：
    所述第二装置向所述第一装置发送所述第三请求。
  23. 根据权利要求20至22中任一项所述的方法，其特征在于，还包括：
    所述第二装置查询所述第一装置的注册参数；
    所述第二装置接收第一管理数据分析服务MDAS的注册参数和第二MDAS的注册参数，所述第一MDAS对应的注册参数中的能力信息用于指示所述第一MDAS能够确定是否存在所述信令风暴事件，所述第二MDAS对应的注册参数中的能力信息用于指示所述第二MDAS能够为所述网络中的网元提供建议。
  24. 一种通信装置，其特征在于，包括至少一个模块，所述至少一个模块用于执行如权利要求1至13中任意一项所述的方法，或者，所述至少一个模块用于执行如权利要求14至23中任意一项所述的方法。
  25. 一种通信系统，其特征在于，包括第一装置和第二装置，其中，所述第一装置用于执行如权利要求1至13中任意一项所述的方法，所述第二装置用于执行如权利要求14至23中任意一项所述的方法。
  26. 一种通信装置，其特征在于，包括处理电路和输入输出接口，所述输入输出接口用于输入和/或输出信号，所述处理电路用于执行权利要求1至13中任一项所述的方法，或者，所述处理电路用于执行权利要求14至23中任一项所述的方法。
  27. 一种计算机可读存储介质，其特征在于，所述计算机可读存储介质上存储有计算机程序或指令，当所述计算机程序或所述指令在计算机上运行时，使得权利要求1至13中任一项所述的方法被执行，或者，使得权利要求14至23中任一项所述的方法被执行。
  28. 一种通信方法，其特征在于，所述方法应用于第一装置和第二装置，其中，所述方法包括：
    所述第一装置执行如权利要求1至13中任意一项所述的方法；所述第二装置执行如权利要求14至23中任意一项所述的方法。
  29. 一种计算机程序产品，其特征在于，所述计算机程序产品存储有计算机可读指令，当所述计算机 可读指令在计算机上运行时，使得计算机执行如权利要求1至23中任一项所述的方法。
PCT/CN2024/127346 2023-11-03 2024-10-25 网络分析方法和装置 Pending WO2025092592A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202311464433.8A CN119945920A (zh) 2023-11-03 2023-11-03 网络分析方法和装置
CN202311464433.8 2023-11-03

Publications (1)

Publication Number Publication Date
WO2025092592A1 true WO2025092592A1 (zh) 2025-05-08

Family

ID=95547408

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2024/127346 Pending WO2025092592A1 (zh) 2023-11-03 2024-10-25 网络分析方法和装置

Country Status (2)

Country Link
CN (1) CN119945920A (zh)
WO (1) WO2025092592A1 (zh)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
GB2638339A (en) * 2024-02-15 2025-08-20 Samsung Electronics Co Ltd Handling network abnormal behaviour

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115150034A (zh) * 2021-03-15 2022-10-04 中国移动通信集团福建有限公司 一种信令风暴的预警方法、装置及电子设备
US20230065199A1 (en) * 2021-08-19 2023-03-02 Nokia Technologies Oy Method, apparatus and computer program
US20230136287A1 (en) * 2021-10-29 2023-05-04 Nokia Technologies Oy Security enhancements for cellular communication systems
CN116158113A (zh) * 2020-09-11 2023-05-23 联想（新加坡）私人有限公司 确定网络系统问题
WO2023098341A1 (zh) * 2021-11-30 2023-06-08 中兴通讯股份有限公司 异常信令的管控方法、装置、电子设备和存储介质

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116158113A (zh) * 2020-09-11 2023-05-23 联想（新加坡）私人有限公司 确定网络系统问题
CN115150034A (zh) * 2021-03-15 2022-10-04 中国移动通信集团福建有限公司 一种信令风暴的预警方法、装置及电子设备
US20230065199A1 (en) * 2021-08-19 2023-03-02 Nokia Technologies Oy Method, apparatus and computer program
US20230136287A1 (en) * 2021-10-29 2023-05-04 Nokia Technologies Oy Security enhancements for cellular communication systems
WO2023098341A1 (zh) * 2021-11-30 2023-06-08 中兴通讯股份有限公司 异常信令的管控方法、装置、电子设备和存储介质

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
GB2638339A (en) * 2024-02-15 2025-08-20 Samsung Electronics Co Ltd Handling network abnormal behaviour

Also Published As

Publication number Publication date
CN119945920A (zh) 2025-05-06

Similar Documents

Publication Publication Date Title
US12207344B2 (en) Communications method and apparatus
KR102469191B1 (ko) 정보 전송방법 및 장치, 컴퓨터 판독가능 저장 매체
US11558813B2 (en) Apparatus and method for network automation in wireless communication system
US12483476B2 (en) Slice control method and apparatus
US20230070712A1 (en) Communication method, apparatus, and system
KR20200139771A (ko) 5g 네트워크에서의 로컬 영역 데이터 네트워크(ladn)에 대한 접속들을 관리하는 방법들
WO2022041285A1 (zh) 一种模型数据传输方法及通信装置
EP3962157B1 (en) Mdbv determining methods and apparatuses
KR20210054923A (ko) 이동통신 네트워크에서 rfsp 인덱스 선택을 위한 네트워크 분석 정보 제공하는 방법 및 장치
WO2022161148A1 (zh) 一种服务质量的控制方法和装置
EP4044659B1 (en) Network resource acquisition method, device, and system
WO2023213177A1 (zh) 一种通信方法及装置
US20250350997A1 (en) Communication method, apparatus, and system
US11864026B2 (en) Systems and methods for access barring based on slice information
CN114079934B (zh) 一种中继通信方法及通信装置
WO2025092592A1 (zh) 网络分析方法和装置
US12185422B2 (en) Communication method and apparatus
CN115913904A (zh) 基于流控制传输协议的数据通信方法、装置及设备
US20250024312A1 (en) Enhanced quality of service support for mobile wireless networks
WO2025139640A1 (zh) 信息处理方法和装置
HK40070489B (zh) 获取网络资源的方法、设备及系统
HK40070489A (zh) 获取网络资源的方法、设备及系统
WO2025098105A1 (zh) 一种边缘应用服务器发现方法及装置
WO2025209296A1 (zh) 通信方法、装置和系统
WO2023185496A1 (zh) 冗余传输请求方法及装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 24884595

Country of ref document: EP

Kind code of ref document: A1