Performance statistics reporting system and method, SPS network element equipment and storage medium

Abstract

The embodiment of the invention provides a performance statistics reporting system and method, SPS network element equipment and a storage medium. The system comprises a performance master control module deployed on a global board of the SPS network element equipment, and performance acquisition modules deployed on each application of the SPS network element equipment, the performance acquisition module is used for acquiring counting information of a local counter to generate a measurement CDL event file and reporting the measurement CDL event file to the performance main control module; and the performance master control module is used for summarizing the measurement CDL event files reported by the performance acquisition modules according to the association relationship between the performance task configuration and the measurement CDL event files to generate performance files, and reporting the performance files to the OMC. Therefore, the workload of the application is greatly reduced, the processing efficiency of the SPS network element equipment is improved, and more accurate network equipment performance data can be more concisely acquired.

Description

Technical Field

[0001] The present application relates to the field of wireless communication technology, and in particular to a performance statistics reporting system, method, SPS network element device and storage medium. Background Art

[0002] In the communication network, through the measurement and collection tasks, performance indicator counters are collected from the relevant units of the signaling processing subsystem (SPS) network element equipment, and reported to the operation and maintenance center (OMC) for presentation. The implementation scheme for each SPS network element equipment to collect and timely report the original performance data is generally as follows: the OM adapter (operations & maintenance adapter) on each application of the equipment reports the Call Detail Log (CDL) file, the OM agent (operations & maintenance agent) parses the CDL message in the CDL file and reports the corresponding counter items to the OM master control (operations & maintenance control), and the OM master control performs summary processing to form a performance file and report it to the network management OMC.

[0003] The current implementation scheme for reporting performance statistics of SPS network element equipment is based on reporting performance statistics CDL messages. This requires that all message interactions of the network element must have corresponding performance statistics CDL message definitions and adapt the interface reporting when they occur. This adds a lot of extra workload to each application beyond the business work, affecting the processing capacity of the entire device.

[0004] Moreover, in the prior art, the application (APP) is responsible for reporting the performance statistics CDL message, and the OM agent parses the CDL message to complete the counter statistics. Since the meaning of the specific counter is strongly related to the business, and the OM agent R&D is not familiar with the business, the statistics are prone to ambiguity and inaccuracy, which affects the accuracy of the network performance indicators. Summary of the invention

[0005] In view of the problems existing in the prior art, the embodiments of the present application provide a performance statistics reporting system, method, SPS network element device and storage medium.

[0006] In a first aspect, an embodiment of the present application provides a performance statistics reporting system, which is applied to a signaling processing subsystem SPS network element device, including:

[0007] A performance master control module deployed on the global board of the SPS network element device, and a performance collection module deployed on each application of the SPS network element device;

[0008] The performance acquisition module is used to obtain the counting information of the local counter to generate a measurement call detail log CDL event file, and report the measurement CDL event file to the performance main control module; wherein each of the measurement CDL event files contains a group of counting information of the local counters associated with a measurement CDL event;

[0009] The performance main control module is used to aggregate the measurement CDL event files reported by each performance collection module according to the association between the performance task configuration and the measurement CDL event file to generate a performance file, and report the performance file to the operation and maintenance center OMC.

[0010] In some embodiments, the local counter comprises a message counter for problem localization.

[0011] In some embodiments, the performance collection module reports the measured CDL event file at a period of 5 minutes.

[0012] In some embodiments, the measuring CDL event comprises a network element attachment and detachment process message measurement event;

[0013] The group of local counters associated with the network element attachment and detachment process message measurement event includes at least one of the following:

[0014] A counter used to count the number of times the network element receives an attachment request ATTACH;

[0015] A counter used to count the number of times the network element sends authentication information request AIR;

[0016] A counter used to count the number of times the network element successfully receives the authentication information response AIA;

[0017] A counter used to count the number of times a network element fails to receive AIA;

[0018] A counter used to count the number of times the network element sends an authentication request AUTH REQ;

[0019] A counter used to count the number of times the network element receives the authentication response AUTH REP;

[0020] A counter used to count the number of times the network element receives the authentication failure message AUTH FAIL;

[0021] A counter used to count the number of times the network element sends the security mode command SMC CMD;

[0022] A counter used to count the number of times the network element receives the security mode command completion message SMC CMP;

[0023] A counter used to count the number of times the network element sends an update location request ULR;

[0024] A counter used to count the number of successful reception of update location responses (ULAs) by network elements;

[0025] A counter used to count the number of times a network element fails to receive ULA;

[0026] A counter used to count the number of times the network element sends a create session request Crt Session Req;

[0027] A counter used to count the number of times the network element successfully receives the create session response Crt Session Rep;

[0028] A counter used to count the number of times the network element fails to receive Crt Session Rep;

[0029] A counter used to count the number of times the network element sends an initial context setup request INIT CTX SETUP REQ;

[0030] A counter used to count the number of times the network element sends the attach accept message ATTACH ACCEPT;

[0031] A counter used to count the number of times the network element receives the initial context setup response INIT CTX SETUP REP;

[0032] A counter used to count the number of times the network element fails to receive INIT CTX SETUP REP;

[0033] A counter used to count the number of times the network element receives the attach complete message ATTACH COMPLETE;

[0034] A counter used to count the number of times the network element sends a modify bearer request MOD BEAR REQ;

[0035] A counter used to count the number of times the network element successfully receives a MOD BEAR REP response;

[0036] A counter used to count the number of times the network element fails to receive MOD BEAR REP;

[0037] A counter used to count the number of times a network element receives a detach request DETACH;

[0038] A counter used to count the number of times a network element sends a delete session request DEL SESSION REQ;

[0039] A counter used to count the number of times the network element successfully receives a delete session response DEL SESSION REP;

[0040] A counter used to count the number of times the network element fails to receive the DEL SESSION REP;

[0041] A counter used to count the number of times a network element sends a detach accept message DETACH ACCEPT.

[0042] In some embodiments, the measured CDL event includes a network element load information event;

[0043] The set of local counters associated with the network element load information event includes at least one of the following:

[0044] A counter for counting the average number of bearers of a network element;

[0045] A counter for counting the average number of dedicated bearers of a network element;

[0046] A counter used to count the average number of default bearers of network elements;

[0047] A counter used to count the maximum number of bearers in a network element;

[0048] A counter for counting the maximum number of dedicated bearers of a network element;

[0049] A counter used to count the maximum default bearer number of network elements;

[0050] A counter used to count the average number of idle users of a network element;

[0051] A counter used to count the maximum number of idle users of a network element;

[0052] A counter used to count the average number of users in the connected state of the network element;

[0053] A counter used to count the maximum number of users in the connected state of a network element;

[0054] A counter used to count the average number of users attached to a network element;

[0055] A counter used to count the maximum number of users attached to a network element;

[0056] A counter for counting the number of DNS resolution attempts of the network element;

[0057] A counter used to count the number of successful DNS resolutions of network elements;

[0058] A counter for counting the number of paging attempts of a network element;

[0059] A counter used to count the number of successful paging of a network element;

[0060] A counter used to count the average guaranteed bit rate (GBR) bearer number of a network element;

[0061] A counter for counting the average number of non-GBR bearers in a network element;

[0062] A counter for counting the maximum GBR bearer number of a network element;

[0063] A counter for counting the maximum number of non-GBR bearers in a network element;

[0064] A counter used to count the number of secondary paging responses of an NE.

[0065] In some embodiments, the measured CDL event includes a network element tracking area load information event;

[0066] The set of local counters associated with the network element tracking area load information event includes at least one of the following:

[0067] A counter for counting the number of idle users in each tracking area of ​​a network element;

[0068] A counter for counting the number of connected users in each tracking area of ​​a network element;

[0069] A counter for counting the number of paging requests per tracking area of ​​a network element;

[0070] A counter for counting paging responses per tracking area of ​​a network element;

[0071] A counter used to count the number of secondary paging responses per tracking area of ​​a network element.

[0072] In a second aspect, an embodiment of the present application further provides a performance statistics reporting method implemented by the performance statistics reporting system according to the first aspect, including:

[0073] The performance acquisition module obtains the counting information of the local counter to generate the measurement CDL event file, and reports the measurement CDL event file to the performance main control module;

[0074] The performance main control module aggregates and processes the measurement CDL event files reported by the performance acquisition module according to the association relationship between the performance task configuration and the measurement CDL event files to generate a performance file, and reports the performance file to the OMC.

[0075] In a third aspect, an embodiment of the present application further provides a signaling processing subsystem SPS network element device, including a memory, a transceiver, and a processor;

[0076] A memory for storing computer programs; a transceiver for sending and receiving data under the control of the processor; and a processor for reading the computer program in the memory and executing the performance statistics reporting method as described in the second aspect.

[0077] In a fourth aspect, an embodiment of the present application further provides a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, and the computer program is used to enable a computer to execute the performance statistics reporting method described in the second aspect as described above.

[0078] In a fifth aspect, an embodiment of the present application further provides a communication device, in which a computer program is stored, and the computer program is used to enable the communication device to execute the performance statistics reporting method described in the second aspect as described above.

[0079] In a sixth aspect, an embodiment of the present application further provides a processor-readable storage medium, wherein the processor-readable storage medium stores a computer program, and the computer program is used to enable the processor to execute the performance statistics reporting method described in the second aspect as described above.

[0080] In a seventh aspect, an embodiment of the present application further provides a chip product, wherein a computer program is stored in the chip product, and the computer program is used to enable the chip product to execute the performance statistics reporting method described in the second aspect as described above.

[0081] The performance statistics reporting system, method, SPS network element device and storage medium provided in the embodiments of the present application are optimized in implementation into two levels: a performance collection module and a performance main control module. The performance collection module directly obtains the counting information of the application local counter to generate a measurement CDL event file and reports it to the performance main control module, which greatly reduces the workload of the application and improves the processing efficiency of the SPS network element device. The performance statistics will not be affected by the inaccurate collection of the OM agent, so that more accurate network equipment performance data can be collected more concisely. BRIEF DESCRIPTION OF THE DRAWINGS

[0082] In order to more clearly illustrate the technical solutions in the embodiments of the present application or the related technologies, the following is a brief introduction to the drawings required for use in the embodiments or the related technical descriptions. Obviously, the drawings described below are some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0083] Figure 1 A schematic diagram of the implementation scheme of performance statistics provided for related technologies;

[0084] Figure 2 A schematic diagram of a performance statistics reporting system provided in an embodiment of the present application;

[0085] Figure 3 A flowchart of a performance statistics reporting method provided in an embodiment of the present application;

[0086] Figure 4 An example diagram of a performance statistics reporting method provided in an embodiment of the present application;

[0087] Figure 5 A schematic diagram of the structure of the SPS network element device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0088] In the embodiments of the present application, the term "and / or" describes the association relationship of the associated objects, indicating that three relationships may exist. For example, A and / or B may represent: A exists alone, A and B exist at the same time, and B exists alone. The character " / " generally indicates that the associated objects before and after are in an "or" relationship.

[0089] In the embodiments of the present application, the term "plurality" refers to two or more than two, and other quantifiers are similar.

[0090] In the embodiments of the present application, the terms "first", "second", etc. are used to distinguish similar objects, and are not used to describe a specific order or sequence. It should be understood that the terms used in this way can be interchangeable under appropriate circumstances, so that the embodiments of the present application can be implemented in an order other than those illustrated or described here, and the objects distinguished by "first" and "second" are generally of the same type, and the number of objects is not limited. For example, the first object can be one or more.

[0091] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0092] In order to facilitate a clearer understanding of the technical solutions of the embodiments of the present application, some technical contents related to the embodiments of the present application are first introduced.

[0093] The core network network equipment includes access and mobility management function (Access and Mobility Management Function, AMF), session management function (Session Management Function, SMF), user plane function (UserPlane Function, UPF), unified data management (Unified Data Management, UDM), network storage function (Network Repository Function, NRF), network slice selection function (Network Slice Selection Function, NSSF), authentication server function (Authentication Server Function, AUSF), policy control function (Policy Control Function, PCF), etc., collectively referred to as SPS network element equipment in this application.

[0094] In the field of communications, performance statistics of network equipment refers to performance monitoring through networks and equipment, collecting relevant statistical data, evaluating the effectiveness and status of network or equipment units, supporting network planning and analysis, thereby improving network performance and efficiency, and enhancing operators' operational capabilities and service quality.

[0095] Traditional performance statistics methods include: object configuration, task creation and synchronization, data collection, data reporting and storage, and data presentation. The process is carried out by the unified network management OMC and network equipment. OMC is responsible for the distribution of measurement tasks, data collection, storage, and presentation, while network equipment is responsible for the counting and reporting of related measurement items of monitoring objects. Since the accuracy of performance statistics directly determines the effectiveness of network analysis, the measurement and reporting mechanism of performance statistics data is particularly critical.

[0096] Figure 1 Schematic diagram of the implementation scheme of performance statistics provided for related technologies, such as Figure 1 As shown in the figure, the relevant components (or modules) of performance statistics include three categories: performance master (OmPMMngr, i.e. OM master), performance agent (OmPMAgt, i.e. OM agent), and performance adapter (OmPMAdapter, i.e. OM adapter). Among them, the OM master is deployed on the global board, the OM agent is deployed on each single board, and the OM adapter is directly deployed on the APP.

[0097] SPS network element equipment needs to provide centralized management functions for various performance indicators of APP. The OM master in the global board provides management of performance statistics tasks, collection, aggregation (including multi-board aggregation) and reporting of performance statistics results. The OM agent and the OM adapter deployed on the APP complete the counting, recording and periodic reporting of the original data. The performance data that each network element needs to provide varies depending on its function.

[0098] After the OM agent is started, it first registers with the OM master. After successful registration, the OM agent initiates a performance task synchronization request to the OM master, and the response sent by the OM master to the OM agent carries the performance task information.

[0099] The following is a brief introduction Figure 1 The process of reporting performance statistics of SPS network element equipment in the solution shown.

[0100] After the SPS of the device is started, the CDL file is sent to the OM agent on the same board every second or when the buffer is full (32KByte). The OM agent extracts counters from the performance statistics-level CDL file and sends the counter results to the OM master every 5 minutes. The OM master merges and accumulates the counters reported by each board / takes the maximum and minimum / period average, and sends them to the network management according to the measurement cycle configured by the network management.

[0101] P1-1: The OM adapter in the application writes the performance statistics CDL message into the CDL file in real time every second or when the buffer is full (32KByte) according to the CDL interface definition. The performance statistics CDL message is similar to a signaling event (for example, a non-access stratum (NAS) registration request will trigger a registration request event message), which is used to identify the key information of all interactive messages. The OM agent starts a 30s collection timer. When the collection timer times out, the corresponding counter results are refreshed in real time (such as accumulation, averaging) according to the association between the performance task configuration and the counter group, and the database is updated.

[0102] P1-2: When the reporting opportunity is met (an integer multiple of 5 minutes. The reporting granularity is 5 minutes, and this period is fixed), confirm whether there is counter information that needs to be reported (when the device network element performance statistics switch is turned off, it will not be reported. It is allowed to be set to off in the device stress test scenario). If so, the OM agent starts to report the counter information to the OM master. The reporting content has already performed accumulation, averaging or difference processing on the counter of this unit for this 5-minute period. After reporting, the cache is cleared and the next 5-minute period is entered. Since the measurement objects corresponding to the counters are diverse (such as Stream Control Transmission Protocol (SCTP) link, Tracking area (TA) location area, Data Network Name (DNN) network identifier, network slice (ns), central processing unit (CPU), etc.), the report is performed in units of counter groups, and the measurement objects of the counter groups are uniquely determined.

[0103] The OM master starts a 2-minute timer to generate a performance file. After receiving the counter information, it performs counter accumulation, average calculation, maximum / minimum value calculation, and other processing according to the counter type, and caches the counter group information.

[0104] P1-3: When the performance file reporting opportunity is met (the performance file timer comes from the data reporting granularity issued by the network management measurement task, which may be 5 minutes, 15 minutes, 30 minutes, 60 minutes, 24 hours, etc.), that is, when the performance file reporting timer times out, the OM master counts and organizes the counter information cached during this timer (for example: adding the results from 5 minutes to 15 minutes; or merging a COUNTER reported by each board into a COUNTER of the device), generates a performance file in the format required by performance statistics, starts the file upload process, and clears the cache.

[0105] The process of the above performance measurement and reporting scheme is relatively complicated, and at the same time, a large amount of additional workload is added to each application in addition to the business work, affecting the processing capacity of the entire device. Therefore, each embodiment of the present application simplifies the above performance measurement and reporting scheme, and can collect more accurate network equipment performance data more concisely, which is conducive to the overall planning of the network.

[0106] Figure 2 A schematic diagram of a performance statistics reporting system provided in an embodiment of the present application, such as Figure 2 As shown, the system can be applied to SPS network element equipment, including:

[0107] A performance master control module 210 deployed on the global board of the SPS network element device, and a performance collection module 220 deployed on each application of the SPS network element device;

[0108] The performance collection module 220 is used to obtain the counting information of the local counter to generate a measurement CDL event file, and report the measurement CDL event file to the performance main control module 210; wherein each measurement CDL event file contains the counting information of a group of local counters associated with a measurement CDL event;

[0109] The performance main control module 210 is used to aggregate the measurement CDL event files reported by each performance collection module according to the association relationship between the performance task configuration and the measurement CDL event file to generate a performance file, and report the performance file to the OMC.

[0110] Specifically, this application Figure 1 On the basis of the scheme shown, the performance statistics reporting scheme of SPS network element equipment is simplified, which can collect more accurate network equipment performance data more concisely. The reporting implementation is optimized into two levels, removing the OM agent environment, and directly completing the reporting of the original counter by the performance collection module deployed on the APP (also called OM collection or OmPMCollect). It is no longer necessary for the application to process the corresponding association between the performance statistics CDL message and the counter. It only needs to use the counting information of the local counter to report the measurement CDL event file according to the reporting timing, which greatly reduces the workload of the application and improves the processing efficiency of the SPS network element equipment; and the counting report is performed by each application or the bottom layer itself, which will not be affected by the inaccurate collection of the OM agent, and the statistics are relatively more accurate.

[0111] The performance collection module can directly obtain the counting information of the local counter (ie, the original counter on the application), and generate the corresponding measurement CDL event file according to the association between the measurement CDL event and the local counter. The accuracy of the measurement CDL event reporting is guaranteed by the network element.

[0112] In some embodiments, different measurement CDL events can be predefined according to the needs of performance statistics, and the association between the measurement CDL events and the counter groups can be defined, that is, one measurement CDL event corresponds to a group of counters. Therefore, the performance collection module can generate a measurement CDL event file corresponding to a measurement CDL event based on the counting information of a group of counters associated with a certain measurement CDL event.

[0113] Performance master module (also called OM master or OmPMMngr) and Figure 1The functions of the OM master in the illustrated scheme are basically the same, such as providing management of performance statistics tasks, collection, aggregation (including multi-board aggregation) and reporting of performance statistics results, etc.

[0114] In some embodiments, the association relationship between the performance task configuration and the measurement CDL event file can be predefined, such as predefining the measurement CDL event file / measurement CDL event associated with each performance task (or performance statistics task, measurement task, etc.), and each performance task (or performance task configuration) may be associated with one or more measurement CDL event files / measurement CDL events. Therefore, the performance main control module can summarize one or more measurement CDL event files associated with a certain performance task (extract the counting information in these measurement CDL event files and perform processing such as merging and accumulating, taking the maximum and minimum, and periodic averaging), obtain the performance statistics result corresponding to the performance task, and finally generate a performance file according to the performance statistics result corresponding to each performance task in the format required by the performance statistics.

[0115] In the embodiment of the present application, the performance statistics OM can be decoupled from the business application, and adding a counter group does not require modifying the platform OM, and only the association between the counter and the measurement CDL event needs to be matched.

[0116] The performance statistics reporting system provided in the embodiment of the present application is optimized in implementation into two levels: a performance collection module and a performance main control module. The performance collection module directly obtains the counting information of the application local counter to generate a measurement CDL event file and reports it to the performance main control module, which greatly reduces the workload of the application and improves the processing efficiency of the SPS network element equipment. The performance statistics will not be affected by the inaccurate collection of the OM agent, so that more accurate network equipment performance data can be collected more concisely.

[0117] In some embodiments, the local counters include message counters for problem location.

[0118] Specifically, each network element device generally has detailed message count-related content in the business processing code for problem location. Therefore, the counting information of these message counters used for problem location can be directly used for performance statistics reporting. There is no need to define reporting counters specifically for the device network key performance indicators (Key Performance Indicator, KPI), which further simplifies the performance statistics reporting solution.

[0119] In addition, the implementation of the solution in this embodiment also brings consistency between the network element device problem location count, performance counter, and device network KPI. Network KPI monitoring is a means. If the network element device can quickly and accurately identify and solve the problem when the indicators are poor, it is what the network element should pay more attention to. Therefore, defining counters from the perspective of problem location will make network element performance statistics more detailed and comprehensive.

[0120] In some embodiments, the performance collection module reports the measurement CDL event file at a period of 5 minutes.

[0121] Specifically, the network element application reports the standard measurement CDL event file every 5 minutes based on the CDL interface. Compared with the traditional performance statistics CDL message reporting, the number of CDL messages and files is greatly reduced. At the same time, the amount of internal message interaction of the network element is also reduced exponentially, which improves the processing efficiency of the network element equipment.

[0122] In addition, the period for the performance collection module to report the measurement CDL event file is set to 5 minutes, which can more conveniently use the existing OM master control and reduce the workload of modifying the OM master control.

[0123] Several typical measurement CDL events are introduced below. It should be noted that the measurement CDL events in this application are not limited to the following, and the counters associated with the measurement CDL events are not limited to the contents in the following embodiments. Those skilled in the art can flexibly define the measurement CDL events and the counters associated with the measurement CDL events according to the relevant technical knowledge in this field and the needs of actual performance statistics.

[0124] In some embodiments, measuring the CDL event includes a network element attachment and detachment process message measurement event;

[0125] The set of local counters associated with the network element attachment and detachment process message measurement event includes at least one of the following:

[0126] A counter used to count the number of times the network element receives an attach request (ATTACH);

[0127] A counter used to count the number of times a network element sends an authentication information request (Authentication Information Request, AIR);

[0128] A counter used to count the number of successful Authentication Information Answer (AIA) received by the network element;

[0129] A counter used to count the number of times a network element fails to receive AIA;

[0130] A counter used to count the number of times a network element sends an authentication request (Authentication Request, AUTH REQ);

[0131] A counter used to count the number of times the network element receives an authentication response (Authentication Response, AUTH REP);

[0132] A counter used to count the number of times the network element receives authentication failure messages (Authentication Fail, AUTH FAIL);

[0133] A counter used to count the number of times a network element sends a security mode command (Security Mode Command, SMC CMD);

[0134] A counter used to count the number of times a network element receives a Security Mode Command Complete (SMC CMP) message;

[0135] A counter used to count the number of times a network element sends an Update Location Request (ULR);

[0136] A counter used to count the number of successful reception of Update Location Answer (ULA) by the network element;

[0137] A counter used to count the number of times a network element fails to receive ULA;

[0138] A counter used to count the number of times a network element sends a create session request (Create Session Request, Crt Session Req);

[0139] A counter used to count the number of times a network element successfully receives a create session response (Create Session Response, Crt Session Rep);

[0140] A counter used to count the number of times the network element fails to receive Crt Session Rep;

[0141] A counter used to count the number of times the network element sends an initial context setup request (INITCTX SETUP REQ);

[0142] A counter used to count the number of times a network element sends an ATTACH ACCEPT message;

[0143] A counter used to count the number of times the network element receives an initial context setup response (INIT CTX SETUP REP);

[0144] A counter used to count the number of times the network element fails to receive INIT CTX SETUP REP;

[0145] A counter used to count the number of times the network element receives an attach complete message (ATTACH COMPLETE);

[0146] A counter used to count the number of times a network element sends a Modify Bear Request (MOD BEAR REQ);

[0147] A counter used to count the number of times the network element successfully receives a Modify Bear Response (MOD BEAR REP);

[0148] A counter used to count the number of times the network element fails to receive MOD BEAR REP;

[0149] A counter used to count the number of times a network element receives a detach request (DETACH);

[0150] A counter used to count the number of times a network element sends a delete session request (Delete Session Request, DEL SESSION REQ);

[0151] A counter used to count the number of times the network element successfully receives a delete session response (Delete Session Response, DEL SESSION REP);

[0152] A counter used to count the number of times the network element fails to receive the DEL SESSION REP;

[0153] A counter used to count the number of times a network element sends a detach accept message (DETACH ACCEPT).

[0154] For example, the format of the measurement CDL event file corresponding to the event of the mobility management entity (MME) attachment and detachment process message measurement (mme Attach detach ProcMsgMeasure) can be shown in Table 1. In Table 1, mmeAttrecvattach, mmeAttsendair, ..., mmeDttsenddetachaccept, etc. are all identifiers or names of counters, and the corresponding third column content is the definition of the corresponding counter. For example: mmeAttrecvattach represents the counter of the number of times the MME receives the attach request.

[0155] Table 1 Measurement CDL event file format corresponding to the measurement event of the MME attachment and detachment process message

[0156]

[0157]

[0158] In some embodiments, the measured CDL event includes a network element load information event;

[0159] The set of local counters associated with the network element load information event includes at least one of the following:

[0160] A counter for counting the average number of bearers of a network element;

[0161] A counter for counting the average number of dedicated bearers of a network element;

[0162] A counter used to count the average number of default bearers of network elements;

[0163] A counter used to count the maximum number of bearers in a network element;

[0164] A counter for counting the maximum number of dedicated bearers of a network element;

[0165] A counter used to count the maximum default bearer number of network elements;

[0166] A counter used to count the average number of users in the idle state (such as ECM-IDLE state) of the network element;

[0167] A counter used to count the maximum number of idle users of a network element;

[0168] A counter used to count the average number of users in the connected state (such as ECM-CONNECTED state) of the network element;

[0169] A counter used to count the maximum number of users in the connected state of a network element;

[0170] A counter used to count the average number of users attached to a network element;

[0171] A counter used to count the maximum number of users attached to a network element;

[0172] A counter for counting the number of Domain Name System (DNS) resolution attempts of the network element;

[0173] A counter used to count the number of successful DNS resolutions of network elements;

[0174] A counter for counting the number of paging attempts of a network element;

[0175] A counter used to count the number of successful paging of a network element;

[0176] A counter used to count the average guaranteed bit rate (GBR) bearer number of network elements;

[0177] A counter for counting the average number of non-GBR bearers in a network element;

[0178] A counter for counting the maximum GBR bearer number of a network element;

[0179] A counter for counting the maximum number of non-GBR bearers in a network element;

[0180] A counter used to count the number of secondary paging responses of an NE.

[0181] For example, the format of the measurement CDL event file corresponding to the MME load information (mme equipment load info) event can be shown in Table 2. In Table 2, MeanNbrActBearerMME, MeanNbrActBearerMME.dedicated, ..., SecondPagingSucc, etc. are all counter identifiers or names, and the corresponding third column content is the definition of the corresponding counter. For example: MeanNbrActBearerMME represents the counter of the average bearer number of MME.

[0182] Table 2 Measurement CDL event file format corresponding to MME load information event

[0183]

[0184]

[0185] In some embodiments, measuring CDL events includes network element tracking area load information events;

[0186] The set of local counters associated with the network element tracking area load information event includes at least one of the following:

[0187] A counter for counting the number of idle users in each tracking area of ​​a network element;

[0188] A counter for counting the number of connected users in each tracking area of ​​a network element;

[0189] A counter for counting the number of paging requests per tracking area of ​​a network element;

[0190] A counter for counting paging responses per tracking area of ​​a network element;

[0191] A counter used to count the number of secondary paging responses per tracking area of ​​a network element.

[0192] For example, the format of the measurement CDL event file corresponding to the MME tracking area load information (mme Tac load info) event can be shown in Table 3. In Table 3, NbrSubEcmIdle.TAC, NbrSubEcmConnected.TAC, ..., SecondPagingSucc.TAC, etc. are all counter identifiers or names, and the corresponding third column content is the definition of the corresponding counter. For example: NbrSubEcmIdle.TAC represents the counter of the number of idle users of MME in each tracking area. The NbrSubEcmIdle.TAC under a certain TAC counts the number of idle users of MME in the tracking area corresponding to the TAC.

[0193] Table 3 Measurement CDL event file format corresponding to MME tracking area load information event

[0194] Equipment Description 1 Byte 0xb Event Type 1 Byte 2: mme Tac load info Length 2Byte Time 2Byte Sub_TANum(TA number) 1 Byte The number of records in this CDL, up to 100 >TAC(TA code) 2Byte TA Code >NbrSubEcmIdle.TAC 4Byte Number of MME idle users per tracking area >NbrSubEcmConnected.TAC 4Byte Number of MME connected users per tracking area >PagAtt.TAC 4Byte Number of paging requests per tracking area >FirstPagingSucc.TAC 4Byte One paging response per tracking area >SecondPagingSucc.TAC 4Byte Second paging response times per tracking area

[0195] Figure 3 The flowchart of the performance statistics reporting method provided in the embodiment of the present application is shown in FIG. 1 , which is implemented based on the performance statistics reporting system described in the above embodiments. Figure 3 As shown, the method comprises the following steps:

[0196] Step 300: The performance collection module obtains the counting information of the local counter to generate a measurement CDL event file, and reports the measurement CDL event file to the performance main control module.

[0197] Step 301: The performance main control module aggregates the measurement CDL event files reported by the performance collection module according to the association between the performance task configuration and the measurement CDL event files to generate a performance file, and reports the performance file to the OMC.

[0198] Specifically, the performance statistics reporting system provided in the embodiment of the present application includes two levels: a performance master control module deployed on the global board, and a performance collection module deployed on each single-board application. Among them, the performance master control module in the global board mainly provides functions such as management of performance statistics tasks, collection, aggregation (including multi-board aggregation) and reporting of performance statistics results; the performance collection module mainly completes the counting, recording and periodic reporting of raw data.

[0199] Based on the above performance statistics reporting system, the performance task synchronization process is no longer required. The performance collection module on the application does not need to pay attention to whether there are performance tasks, and can report the measurement CDL event file regularly (for example, every 5 minutes by default). The number of messages in the optimized measurement CDL event file is very small, and the impact on the business is negligible. In addition, the content of the measurement CDL event file itself is the problem location level counting information, so there is no need to set the reporting switch, and it is always reported by default.

[0200] Figure 4 An example diagram of the performance statistics reporting method provided in the embodiment of the present application, such as Figure 4 As shown in the figure, the process of reporting performance statistics of SPS network element equipment mainly includes:

[0201] After the SPS of the device is started, the board application locally records the data related to the measurement of CDL events and sends the counter results to the performance control module every 5 minutes. The performance control module merges and accumulates the counters reported by each board / takes the maximum and minimum / period average, and sends them to the network management according to the measurement cycle configured by the network management.

[0202] P2-1: The performance collection module on the application starts a 30s timer. When the collection timer times out, the relevant data of the CDL event is collected and measured according to the CDL interface definition, and the data is cached.

[0203] When the reporting opportunity is met (an integer multiple of 5 minutes. The reporting granularity is 5 minutes, and this cycle is fixed), the measurement CDL event file is reported to the performance main control module. After reporting, the cache is cleared and the next 5-minute cycle is entered.

[0204] P2-2: The performance main control module starts a 2-minute timer. When the timer times out, the corresponding counter results are refreshed in real time according to the association between the performance task configuration and the measured CDL event file, such as accumulating the counters, calculating the average, calculating the maximum and minimum values, etc. according to the counter type, and updating the database.

[0205] When the performance file reporting opportunity is met (the performance file timer comes from the data reporting granularity issued by the network management measurement task, which may be 5 minutes, 15 minutes, 30 minutes, 60 minutes, 24 hours, etc.), that is, when the performance file reporting timer times out, the performance main control module counts and organizes the counter information cached during this timer (for example: adding the results from 5 minutes to 15 minutes; or merging a COUNTER reported by each board into a COUNTER of the device), generates a performance file in the format required by performance statistics, starts the file upload process, and clears the cache.

[0206] The various embodiments of the present application are based on the same application concept, so the various embodiments can refer to each other and the repeated parts will not be repeated.

[0207] Figure 5 A schematic diagram of the structure of the SPS network element device provided in the embodiment of the present application, such as Figure 5 As shown, the SPS network element device includes a memory 520, a transceiver 510 and a processor 500; wherein the processor 500 and the memory 520 may also be arranged physically separately.

[0208] The memory 520 is used to store computer programs; the transceiver 510 is used to send and receive data under the control of the processor 500.

[0209] Specifically, the transceiver 510 is used to receive and send data under the control of the processor 500 .

[0210] Among them, Figure 5 In the embodiment, the bus architecture may include any number of interconnected buses and bridges, specifically linking various circuits of one or more processors represented by processor 500 and memory represented by memory 520. The bus architecture may also link various other circuits such as peripherals, voltage regulators, and power management circuits, which are well known in the art and are therefore not further described in this application. The bus interface provides an interface. The transceiver 510 may be a plurality of components, namely, a transmitter and a receiver, providing a unit for communicating with various other devices on a transmission medium, which may include a wireless channel, a wired channel, an optical cable, and other transmission media.

[0211] The processor 500 is responsible for managing the bus architecture and general processing, and the memory 520 can store data used by the processor 500 when performing operations.

[0212] The processor 500 may be a central processing unit (CPU), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or a complex programmable logic device (CPLD). The processor may also adopt a multi-core architecture.

[0213] The processor 500 calls the computer program stored in the memory 520 to execute any of the methods provided in the embodiments of the present application according to the obtained executable instructions, for example: the performance acquisition module obtains the counting information of the local counter to generate a measurement CDL event file, and reports the measurement CDL event file to the performance main control module; the performance main control module summarizes the measurement CDL event file reported by the performance acquisition module according to the association between the performance task configuration and the measurement CDL event file, generates a performance file, and reports the performance file to the OMC.

[0214] It should be noted here that the above-mentioned SPS network element device provided in the embodiment of the present application can implement all the method steps implemented in the above-mentioned method embodiment, and can achieve the same technical effect. The parts and beneficial effects that are the same as the method embodiment in this embodiment will not be described in detail here.

[0215] It should be noted that the division of modules (or units) in the embodiments of the present application is schematic and is only a logical function division. There may be other division methods in actual implementation. In addition, each functional module (or unit) in each embodiment of the present application may be integrated in a processing unit, or each module (or unit) may exist physically separately, or two or more modules (or units) may be integrated in one unit. The above-mentioned integrated modules (or units) may be implemented in the form of hardware or in the form of software functional modules (or units).

[0216] If the integrated module (or unit) is implemented in the form of a software function module (or unit) and sold or used as an independent product, it can be stored in a processor-readable storage medium. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions to enable a computer device (which can be a personal computer, a server, or a network device, etc.) or a processor (processor) to perform all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (Read-Only Memory, ROM), random access memory (Random Access Memory, RAM), disk or optical disk and other media that can store program code.

[0217] On the other hand, an embodiment of the present application further provides a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, and the computer program is used to enable a computer to execute the performance statistics reporting method provided in the above embodiments.

[0218] It should be noted here that the computer-readable storage medium provided in the embodiment of the present application can implement all the method steps implemented in the above-mentioned method embodiment and can achieve the same technical effect. The parts and beneficial effects of this embodiment that are the same as those in the method embodiment will not be described in detail here.

[0219] The computer-readable storage medium can be any available medium or data storage device that can be accessed by a computer, including but not limited to magnetic storage (such as floppy disks, hard disks, magnetic tapes, magneto-optical disks (MO), etc.), optical storage (such as CD, DVD, BD, HVD, etc.), and semiconductor storage (such as ROM, EPROM, EEPROM, non-volatile memory (NANDFLASH), solid-state drive (SSD)), etc.

[0220] The technical solution provided in the embodiment of the present application can be applicable to a variety of systems, especially 5G systems. For example, the applicable system can be a global system of mobile communication (GSM) system, a code division multiple access (CDMA) system, a wideband code division multiple access (WCDMA) general packet radio service (GPRS) system, a long term evolution (LTE) system, a LTE frequency division duplex (FDD) system, a LTE time division duplex (TDD) system, an advanced long term evolution (LTE-A) system, a universal mobile telecommunication system (UMTS), a world-wide interoperability for microwave access (WiMAX) system, a 5G new air interface (NR) system, etc. These various systems include terminal equipment and network equipment. The system may also include a core network part, such as an evolved packet system (EPS), a 5G system (5GS), etc.

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

[0222] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer executable instructions. These computer executable instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

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

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

[0225] Obviously, those skilled in the art can make various changes and modifications to the present application without departing from the spirit and scope of the present application. Thus, if these modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is also intended to include these modifications and variations.

Claims

1. A performance statistics reporting system, characterized in that: Applicable to the signaling processing subsystem SPS network element equipment, including: A performance master control module deployed on the global board of the SPS network element device, and a performance collection module deployed on each application of the SPS network element device; The performance acquisition module is used to obtain the counting information of the local counter to generate a measurement call detail log CDL event file, and report the measurement CDL event file to the performance main control module; wherein each of the measurement CDL event files contains a group of counting information of the local counters associated with a measurement CDL event; The performance main control module is used to aggregate the measurement CDL event files reported by each performance collection module according to the association between the performance task configuration and the measurement CDL event file to generate a performance file, and report the performance file to the operation and maintenance center OMC.

2. The performance statistics reporting system according to claim 1, characterized in that: The local counters include message counters used for problem location.

3. The performance statistics reporting system according to claim 1, characterized in that: The performance collection module reports the measured CDL event file at a period of 5 minutes.

4. The performance statistics reporting system according to any one of claims 1 to 3, characterized in that: The measured CDL event includes a network element attachment and detachment process message measurement event; The group of local counters associated with the network element attachment and detachment process message measurement event includes at least one of the following: A counter used to count the number of times the network element receives an attachment request ATTACH; A counter used to count the number of times the network element sends authentication information request AIR; A counter used to count the number of times the network element successfully receives the authentication information response AIA; A counter used to count the number of times a network element fails to receive AIA; A counter used to count the number of times the network element sends an authentication request AUTH REQ; A counter used to count the number of times the network element receives the authentication response AUTH REP; A counter used to count the number of times the network element receives the authentication failure message AUTH FAIL; A counter used to count the number of times the network element sends the security mode command SMC CMD; A counter used to count the number of times the network element receives the security mode command completion message SMC CMP; A counter used to count the number of times the network element sends an update location request ULR; A counter used to count the number of successful reception of update location responses (ULAs) by network elements; A counter used to count the number of times a network element fails to receive ULA; A counter used to count the number of times the network element sends a create session request Crt Session Req; A counter used to count the number of times the network element successfully receives the create session response Crt Session Rep; A counter used to count the number of times the network element fails to receive Crt Session Rep; A counter used to count the number of times the network element sends an initial context setup request INIT CTX SETUP REQ; A counter used to count the number of times the network element sends the attach accept message ATTACH ACCEPT; A counter used to count the number of times the network element receives the initial context setup response INIT CTX SETUP REP; A counter used to count the number of times the network element fails to receive INIT CTX SETUP REP; A counter used to count the number of times the network element receives the attach complete message ATTACH COMPLETE; A counter used to count the number of times the network element sends a modify bearer request MOD BEAR REQ; A counter used to count the number of times the network element successfully receives a MOD BEAR REP response; A counter used to count the number of times the network element fails to receive MOD BEAR REP; A counter used to count the number of times a network element receives a detach request DETACH; A counter used to count the number of times a network element sends a delete session request DEL SESSION REQ; A counter used to count the number of times the network element successfully receives a delete session response DEL SESSION REP; A counter used to count the number of times the network element fails to receive the DEL SESSION REP; A counter used to count the number of times a network element sends a detach accept message DETACH ACCEPT.

5. The performance statistics reporting system according to any one of claims 1 to 3, characterized in that: The measured CDL event includes a network element load information event; The set of local counters associated with the network element load information event includes at least one of the following: A counter for counting the average number of bearers of a network element; A counter for counting the average number of dedicated bearers of a network element; A counter used to count the average number of default bearers of network elements; A counter used to count the maximum number of bearers in a network element; A counter for counting the maximum number of dedicated bearers of a network element; A counter used to count the maximum default bearer number of network elements; A counter used to count the average number of idle users of a network element; A counter used to count the maximum number of idle users of a network element; A counter used to count the average number of users in the connected state of the network element; A counter used to count the maximum number of users in the connected state of a network element; A counter used to count the average number of users attached to a network element; A counter used to count the maximum number of users attached to a network element; A counter for counting the number of DNS resolution attempts of the network element; A counter used to count the number of successful DNS resolutions of network elements; A counter for counting the number of paging attempts of a network element; A counter used to count the number of successful paging of a network element; A counter used to count the average guaranteed bit rate (GBR) bearer number of a network element; A counter for counting the average number of non-GBR bearers in a network element; A counter for counting the maximum GBR bearer number of a network element; A counter for counting the maximum number of non-GBR bearers in a network element; A counter used to count the number of secondary paging responses of an NE.

6. The performance statistics reporting system according to any one of claims 1 to 3, characterized in that: The measured CDL event includes a network element tracking area load information event; The set of local counters associated with the network element tracking area load information event includes at least one of the following: A counter for counting the number of idle users in each tracking area of ​​a network element; A counter for counting the number of connected users in each tracking area of ​​a network element; A counter for counting the number of paging requests per tracking area of ​​a network element; A counter for counting paging responses per tracking area of ​​a network element; A counter used to count the number of secondary paging responses per tracking area of ​​a network element.

7. A performance statistics reporting method implemented by the performance statistics reporting system according to any one of claims 1 to 6, characterized in that: include: The performance acquisition module obtains the counting information of the local counter to generate the measurement CDL event file, and reports the measurement CDL event file to the performance main control module; The performance main control module aggregates and processes the measurement CDL event files reported by the performance acquisition module according to the association relationship between the performance task configuration and the measurement CDL event files to generate a performance file, and reports the performance file to the OMC.

8. A signaling processing subsystem SPS network element device, characterized in that: Including memory, transceiver, processor; Memory for storing computer programs; a transceiver, for transmitting and receiving data under the control of the processor; A processor is used to read the computer program in the memory and execute the performance statistics reporting method as described in claim 7.

9. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and the computer program is used to enable a computer to execute the performance statistics reporting method according to claim 7.

Images