Interrupt perception identification method and device, electronic equipment, storage medium and product

Abstract

The invention provides an interrupt perception recognition method and device, electronic equipment, a storage medium and a product. The method comprises the following steps: acquiring a target user set, wherein the target user set comprises at least one target user; obtaining a first flow rate of each target user in the target user set at an interruption moment and a first port recovery number of each target user in the target user set at the interruption moment; and if the first flow rate of the target user at the interruption moment is not less than the first preset flow rate or the first port recovery number of the target user at the interruption moment is not less than the first preset port number, determining the target user as an interruption sensing user.

Description

Technical Field

[0001] The present disclosure relates to the technical field of interrupt perception and recognition, and in particular to an interrupt perception and recognition method, device, electronic device, storage medium and product. Background Art

[0002] In related interruption perception recognition schemes, whether the target user perceives the interruption is judged only by the frequency of the interruption, resulting in low accuracy of interruption perception recognition of the target user. Summary of the invention

[0003] The present disclosure provides an interruption perception and identification method, device, electronic device, storage medium and product to solve the problems in the related art.

[0004] A first aspect of the present disclosure provides an interruption perception recognition method, the method comprising:

[0005] Acquire a target user set, where the target user set includes at least one target user;

[0006] Acquire a first flow rate of each target user in the target user set at the interruption time and a first port recovery number of each target user in the target user set at the interruption time;

[0007] If the first flow rate of the target user at the interruption time is not less than the first preset flow rate or the first port recovery number of the target user at the interruption time is not less than the first preset port number, the target user is determined to be an interruption-aware user.

[0008] In one embodiment, obtaining a target user set includes:

[0009] Obtain the message records of each user in the Radius server, where one user corresponds to at least one message record, and each message record contains the message type, message timestamp, and the user name corresponding to the message;

[0010] Filter out the Radius message records whose message type is the first message type from the message records of the Radius server, and obtain all the Radius message records whose message type is the first message type;

[0011] Determine a first user set based on user names corresponding to messages in all Radius message records whose message types are the first message type;

[0012] Filtering message records with message timestamps within a first preset time interval from the first user set to obtain a second user set, wherein the first preset time interval is used to indicate a non-network change operation time interval;

[0013] Based on the second user set, a target user set is determined, wherein a user name corresponding to a message in the target user set corresponds to at least a message timestamp.

[0014] In one embodiment, obtaining the first flow rate of each target user in the target user set at the interruption time includes:

[0015] According to the user name and message timestamp corresponding to the message in the second user set, searching the message record of the Radius server for the previous message record corresponding to the user name and message timestamp corresponding to the message;

[0016] Obtain the first online time and the first flow of the target user in the message record of the second user set; and obtain the second online time and the second flow of the target user in the previous message record;

[0017] Determine an online time difference of a target user based on the first online time and the second online time; and determine a flow rate difference of the target user based on the first flow rate and the second flow rate;

[0018] The flow difference is compared with the online time difference to obtain a first flow rate of the target user at the interruption moment.

[0019] In one embodiment, before obtaining the first online time and the first flow of the target user's message record in the second user set; and obtaining the second online time and the second flow of the target user's previous message record, the method provided by the present disclosure further includes:

[0020] Merging the message record in the second user set and the previous message record to obtain a third user set;

[0021] Grouping the message records in the third user set according to the user name corresponding to the message to obtain message records of each target user with different message timestamps;

[0022] According to the order of the message timestamps from small to large, the message records of each target user with different message timestamps are sorted to obtain the message records of each target user sorted from small to large message timestamps.

[0023] In one embodiment, obtaining the number of first port reclaims of each target user in the target user set at the interruption time includes:

[0024] According to the user name corresponding to the target user set message, filter out the message record of the Radius server corresponding to the user name from the message record of the Radius server;

[0025] Determine the NAT public network port segment change value of the message record of each type of Radius server corresponding to the user name;

[0026] Sum the NAT public network port segment change values ​​of the message records of each type of Radius server corresponding to the user name to obtain the number of NAT public network address ports corresponding to the user name, wherein the number of NAT public network address ports corresponding to the user name at least includes the number of NAT public network address ports corresponding to the user name at the time of interruption and the number of NAT public network address ports corresponding to the user name at the time before interruption;

[0027] The number of NAT public network address ports corresponding to the user name at the time of interruption is subtracted from the number of NAT public network address ports corresponding to the user name at the time before interruption to obtain the first port recovery number of the target user at the time of interruption.

[0028] In one embodiment, determining the NAT public network port segment change value of the message record of each type of Radius server corresponding to the user name includes:

[0029] Determine a message record containing a second message type from the message record of the Radius server corresponding to the user name, and obtain a fourth user set;

[0030] Grouping the fourth user set according to a first preset rule to obtain at least two fifth user sets, wherein the fifth user set includes a message type and a reason type for billing termination for each message record;

[0031] Determine, based on the message type of each message record in the fifth user set and the type of the reason for billing termination, a message identifier and a type identifier of the reason for billing termination for each message record in the fifth user set;

[0032] Based on the message identifier of each message record in the fifth user set, the billing termination reason type identifier and the second preset rule, the NAT public network port segment change value of the message record of each type of Radius server corresponding to the user name in the fifth user set is determined.

[0033] A second aspect of the present disclosure provides an interruption perception and recognition device, the device comprising:

[0034] A first acquisition unit, configured to acquire a target user set, wherein the target user set includes at least one target user;

[0035] A second acquisition unit is used to acquire a first flow rate of each target user in the target user set at the interruption time and a first port recovery number of each target user in the target user set at the interruption time;

[0036] The determination unit is used to determine that the target user is an interruption-aware user if the first flow rate of the target user at the interruption time is not less than the first preset flow rate or the first port recovery number of the target user at the interruption time is not less than the first preset port number.

[0037] A third aspect of the present disclosure provides an electronic device, including:

[0038] At least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can execute the method described in the embodiment of the first aspect of the present disclosure.

[0039] The fourth aspect embodiment of the present disclosure proposes a non-transitory computer-readable storage medium storing computer instructions, wherein the computer instructions are used to enable a computer to execute the method described in the first aspect embodiment of the present disclosure.

[0040] The fifth aspect embodiment of the present disclosure provides a computer program product, including a computer program, which implements the method described in the first aspect embodiment of the present disclosure when executed by a processor.

[0041] In summary, the present disclosure proposes an interruption-aware identification method, which includes: obtaining a target user set, wherein the target user set includes at least one target user; obtaining a first flow rate of each target user in the target user set at the interruption moment and a first port recovery number of each target user in the target user set at the interruption moment; if the first flow rate of the target user at the interruption moment is not less than a first preset flow rate or the first port recovery number of the target user at the interruption moment is not less than a first preset port number, determining that the target user is an interruption-aware user.

[0042] According to the scheme provided by the present disclosure, a target user set is obtained, wherein the target user set includes at least one target user; a first flow rate of each target user in the target user set at an interruption time and a first port recovery number of each target user in the target user set at an interruption time are obtained; if the first flow rate of the target user at the interruption time is not less than a first preset flow rate or the first port recovery number of the target user at the interruption time is not less than a first preset port number, the target user is determined to be an interruption-aware user, and whether the target user perceives the interruption can be judged in combination with the first flow rate of the target user at the interruption time and the first port recovery number of the target user at the interruption time, thereby improving the recognition accuracy of the target user who perceives the interruption.

[0043] It is to be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0044] The drawings herein are incorporated into and constitute a part of the specification, illustrate embodiments consistent with the present disclosure, and together with the description are used to explain the principles of the present disclosure, and do not constitute improper limitations on the present disclosure.

[0045] Figure 1 A flowchart of an interruption perception and identification method provided in an embodiment of the present disclosure;

[0046] Figure 2 A flowchart of a method for obtaining a target user set provided in an embodiment of the present disclosure;

[0047] Figure 3 A flowchart of a method for obtaining a first flow rate of a target user at an interruption time provided by an embodiment of the present disclosure;

[0048] Figure 4 A flowchart of a method for obtaining message records of each target user whose message timestamps are sorted from small to large provided by an embodiment of the present disclosure;

[0049] Figure 5 A flow chart of a method for obtaining the number of first port reclaims of a target user at the time of interruption provided by an embodiment of the present disclosure;

[0050] Figure 6 A flow chart of a method for determining a NAT public network port segment change value of a message record of each type of Radius server corresponding to a user name in a fifth user set provided by an embodiment of the present disclosure;

[0051] Figure 7 A flowchart of an interruption perception and identification method provided for an application example of the present disclosure;

[0052] Figure 8 A schematic diagram of the structure of an interruption perception and recognition device provided in an embodiment of the present disclosure;

[0053] Fig. 9 A schematic diagram of the hardware structure of an electronic device provided in an embodiment of the present disclosure. DETAILED DESCRIPTION

[0054] Embodiments of the present disclosure are described in detail below, and examples of the embodiments are shown in the accompanying drawings, wherein the same or similar reference numerals throughout represent the same or similar elements or elements having the same or similar functions. The embodiments described below with reference to the accompanying drawings are exemplary and are intended to be used to explain the present disclosure, and should not be construed as limiting the present disclosure.

[0055] In order to help those skilled in the art to better understand the technical solutions described in the embodiments of the present disclosure, the technical terms in the embodiments of the present disclosure are explained as follows before introducing the embodiments of the present disclosure.

[0056] Home broadband access and offline process: Home broadband dial-up online process: The PPP protocol over Ethernet (Point-to-Point Protocol over Ethernet, PPPoE) client is the home broadband optical network unit (Optical Network Unit, ONU), the PPPoE server / access server is the IP metropolitan area network border network gateway (Broadband Network Gateway, BNG) device, and the AAA server is the Radius server. The PPPoE protocol process runs between the ONU and BNG, and the Radius protocol process runs between the BNG and the Radius server. Among them, the PPPoE client sends a PADI message to the PPPoE server device to start PPPoE access; the PPPoE server sends a PADO message to the client; the client initiates a PADR request to the PPPoE server based on the response; the PPPoE server generates a Session ID and sends it to the client through PADS; the client and the PPPoE server negotiate the PPP Link Control Protocol (LCP) to establish link layer communication; the PPPoE server sends a Challenge message to the authentication client and provides a 128-bit Challenge; after receiving the Challenge message, the client performs the MD5 algorithm on the password and Challenge, and sends it to the PPPoE server in the Response message; the PPPoE server sends the Challenge, Challenge-Password and user name together to the Radius user authentication server, which authenticates it; the Radius user authentication server determines whether the user is legitimate based on the user information, and then responds to the PPPoE server with an authentication success / failure message. If successful, it carries the negotiation parameters and the user's related business attributes to authorize the user. If the authentication fails, the process ends here; the PPPoE server returns the authentication result to the client; the user performs NCP (such as IPCP) negotiation and obtains the planned IP address and other parameters through the PPPoE server; if the authentication is successful, the PPPoE server initiates a billing start request to the Radius user authentication server; the RADIUS user authentication server responds with a billing start request message; the user is now authenticated and has obtained legal authority, and can carry out network services normally. When the user wants to terminate the network service, he can disconnect the network connection through PPPoE.

[0057] The process of home broadband offline: The process of PPPoE user offline includes two situations: user active offline and abnormal offline. In normal offline, the user actively sends a Terminate-Request to the PPPoE server through the PPPoE client; the PPPoE server returns a Terminate-Ack message to the PPPoE client; the PPPoE server sends a billing stop request message to the AAA server; the AAA server responds to the billing stop request message to the authentication point; in abnormal offline, the PPPoE server generally detects the PPPoE client. When it is found that the PPPoE client has no response, the PPPoE server will think that the user is offline and actively send a billing stop request to the AAA server.

[0058] Radius authentication protocol: Radius authentication protocol is a protocol based on a client / server structure. Its client is initially a network access server (Net Access Server, NAS). Any computer running Radius client software can become a Radius client. Radius message types include authentication request class, authorization class and billing class. Commonly used ones are request access, receive access, deny access, billing request and billing response. The Radius protocol authentication mechanism is flexible and can adopt multiple methods such as PAP, CHAP or Unix login authentication. Radius is an extensible protocol. All its work is based on the vector of Attribute-Length-Value. Because the Radius protocol is simple, clear and extensible, it has been widely used, including ordinary telephone Internet access, ADSL Internet access, community broadband Internet access, IP phone, virtual private dialup network services (Virtual Private Dialup Networks, VPDN) based on dial-up users, mobile phone prepaid services, etc.

[0059] Network Address Translation (NAT): A technology used to convert private addresses used in local networks to global IP addresses when connecting to the Internet, mainly to solve the problem of IPv4 address shortage. NAT includes three implementation methods: static translation, dynamic translation, and Network Address Port Translation (NAPT). Currently, NAT translation in IP metropolitan area networks is actually NAPT, which can map multiple internal addresses to a legal public network address, but with different protocol port numbers corresponding to different internal addresses. In this way, one-to-many mapping of public and private addresses can be achieved, effectively improving the utilization rate of public addresses.

[0060] Deep packet inspection (DPI): DPI is a traffic detection and control technology based on the application layer, which can be used to identify Internet services and user behaviors. The so-called "depth" is compared with the ordinary message analysis level. Ordinary message detection only analyzes the content below the 4th layer of the IP packet, including the source address, destination address, source port, destination port and protocol type. The DPI system can view the content of the 2nd to 7th layers of the Open System Interconnect (OSI) model, perform deep detection on different network application layer loads (such as HTTP, DNS, etc.), and can find, identify and classify data packets containing specific data or code payloads. By detecting and analyzing the traffic and message content at key points of the network, the DPI device can filter and control the detected traffic according to pre-defined policies, and can complete the refined identification of the services of the link, business traffic flow direction analysis, business traffic proportion statistics, business proportion shaping, application layer denial of service attacks, filtering of viruses and Trojans, and control of P2P abuse.

[0061] In related interruption perception recognition schemes, whether the target user perceives the interruption is judged only by the frequency of the interruption, resulting in low accuracy of interruption perception recognition of the target user.

[0062] In order to ensure and improve the quality of use of home broadband users, operators will evaluate and analyze the quality of use of users. When conducting user use quality evaluation and analysis, there are two main aspects: one is the quality of the Internet access process, such as whether the access speed is high, whether the access success rate is high, etc.; the other is to evaluate whether there is an interruption during use. In the existing technology, the situation of home broadband dial-up authentication offline is often used to represent the interruption of its network, so as to represent the situation of user perception of network interruption, which is used as an important indicator for user perception analysis and evaluation.

[0063] The following briefly introduces two solutions related to the method for identifying interruption perception of home broadband users in related technologies:

[0064] Solution A: Solution A identifies the interruption of the user's Internet access through the interruption record of the authentication protocol. This judgment is mainly based on the protocol information between the dial-up terminal and the authentication server, but it does not determine whether the user is using it when the interruption occurs. Therefore, it can only identify the interruption, but not the interruption perception.

[0065] Solution B: Solution B determines whether the user is using the service by combining changes in user traffic and then identifies whether the user has sensed the interruption. In addition to identifying connection protocol interruptions, this type of technology also identifies interruption perception by combining changes in user traffic near the time of the interruption.

[0066] In general, in the relevant technology, the offline reasons and offline frequency in the user broadband authentication protocol Radius offline records are mainly used to identify the interruption of broadband access. This is used to represent the user perception of interruption. It needs to be used in conjunction with other quality perception indicators to evaluate the user's network usage quality and perception.

[0067] The above solution has the following defects:

[0068] The interruption of user Internet access is identified through the interruption record of the authentication protocol, but whether the user's actual use is actually interrupted is ignored.

[0069] In related technologies, the change in user traffic is used to determine whether the user is using the service and whether the user has sensed interruption. However, the existing collection technology requires the deployment of a large number of server computing and storage resources, and the large amount of data requires a long processing time. Currently, there are two main methods for collecting user traffic:

[0070] 1. You can collect traffic of a single user in the access network. Collecting user traffic in the access network is mainly done through traffic monitoring of the ONU. It is necessary to deploy traffic collection tasks for each ONU on the network management. This traffic collection method requires additional deployment of a large amount of storage and computing resources.

[0071] 2. Use DPI records to count user traffic. The DPI equipment deployed at the IP metropolitan area network egress can distinguish the traffic and business composition of each home broadband user, but DPI will generate 70G data records per 10G egress bandwidth on average every day, about 90 million rows of data. For a metropolitan area network with a T-level egress, DPI needs to consume a lot of storage resources; the user-level calculation time is at the hour level, and the calculation time is too long; in addition, DPI can only collect and record the traffic reaching the metropolitan area network egress, and cannot record the traffic within the network, so there is an incomplete situation in the judgment of the traffic usage of a single user.

[0072] In addition, in the IP metropolitan area network related technologies, due to the shortage of IPv4 public network addresses, NAT technology has been introduced to meet the business needs of users. For each home broadband user, during the period of access to the Internet, BNG will allocate one or more new public network address port segments to the user according to the usage of each user's NAT public network address port resources, or recycle the idle public network address port segments that the user no longer uses. The allocation and recovery of these public network address port segments can be obtained by using the intermediate billing message of Radius, as long as the relevant configuration is turned on on the BNG device.

[0073] In order to solve the defects in the related art, the present disclosure obtains a target user set, wherein the target user set includes at least one target user; obtains a first flow rate of each target user in the target user set at an interruption time and a first port recovery number of each target user in the target user set at an interruption time; if the first flow rate of the target user at the interruption time is not less than a first preset flow rate or the first port recovery number of the target user at the interruption time is not less than a first preset port number, the target user is determined to be an interruption-aware user, and the first flow rate of the target user at the interruption time and the first port recovery number of the target user at the interruption time can be combined to determine whether the target user perceives the interruption, thereby improving the recognition accuracy of the target user who perceives the interruption.

[0074] The present disclosure is further described in detail below with reference to the accompanying drawings and specific embodiments.

[0075] like Figure 1 As shown, Figure 1 A flowchart of an interrupt perception and identification method provided in an embodiment of the present disclosure. The interrupt perception and identification method provided in an embodiment of the present disclosure comprises the following steps:

[0076] Step 101, obtaining a target user set, wherein the target user set includes at least one target user;

[0077] In one embodiment, the target user refers to a user who has experienced an interruption.

[0078] In one embodiment, the target user may be a user who has experienced one interruption, or a user who has experienced multiple interruptions.

[0079] In one embodiment, the target user set may be directly obtained from the interruption record, or the target user set may be filtered out from the interruption record.

[0080] Step 102, obtaining a first flow rate of each target user in the target user set at the interruption time and a first port recovery number of each target user in the target user set at the interruption time;

[0081] In one embodiment, the first flow rate is used to indicate the average flow rate of the user at the time of the interruption.

[0082] In one embodiment, since the flow rate when a user is surfing the Internet is significantly different from the flow rate when the user is interrupted, by obtaining the first flow rate of each target user in the target user set at the time of interruption, the target user range can be further narrowed and the recognition accuracy of the interrupted user perception can be improved.

[0083] In one embodiment, the first port reclaim number is used to determine whether the user is in an active Internet access state.

[0084] In one embodiment, when judging whether the target user perceives the interruption based on the first flow rate of the target user at the interruption time, there may be underreporting due to the low first flow rate. Therefore, by obtaining the first port recovery number of each target user in the target user set at the interruption time, the recognition accuracy of the interrupted user perception can be further improved.

[0085] In one embodiment, since each target user may have multiple interruption moments, the first flow rate of each target user in the target user set at each interruption moment and the first port recovery number of each target user in the target user set at each interruption moment may be obtained.

[0086] Step 103: If the first flow rate of the target user at the interruption time is not less than the first preset flow rate or the first port recovery number of the target user at the interruption time is not less than the first preset port number, the target user is determined to be an interruption-aware user.

[0087] In one embodiment, the first preset flow rate is generally an average value of the first flow rate when the user is actively surfing the Internet. For example, the first preset flow rate may be 1 Mbps. The specific value of the first preset flow rate is not limited in the present disclosure.

[0088] In one embodiment, the first preset port number is generally an average of the first port recycling numbers. For example, the first preset port number may be 512. The present disclosure does not limit the specific value of the first preset port number.

[0089] In one embodiment, a regression algorithm or a baseline learning algorithm may be used to optimize the first preset flow rate and the first preset number of ports to obtain a more accurate first preset flow rate and the first preset number of ports, thereby improving the recognition accuracy of interruption-aware users.

[0090] In one embodiment, the above-mentioned interruption perception identification method can be applied to the mining of poor quality users who have been disconnected. After actively revisiting the mined users, the proportion of users who reported problems with Internet access among the successfully revisited users reached 50%, which is a 28% increase compared to the 22% hit rate of users mined based solely on the frequency of offline.

[0091] In one embodiment, if Figure 2 As shown, obtain the target user set, including:

[0092] Step 201, obtaining the message record of each user in the Radius server, wherein one user corresponds to at least one message record, and each message record includes a message type, a message timestamp, and a user name corresponding to the message;

[0093] In one embodiment, the message types of the message record include a billing start message type, a billing end message type, and an intermediate billing message type.

[0094] In one embodiment, the message timestamp is used to indicate the time of the message.

[0095] In one embodiment, each message record corresponding to a user has a different message timestamp.

[0096] In one embodiment, the message timestamps of the message records corresponding to multiple users may be the same or different.

[0097] In one embodiment, the Radius server can be configured to send logs to one or more destinations, such as a local file system, a syslog log server, or a database. That is, if the log is sent to the local file system, the message record of each user on the Radius server can be obtained from the local file system; if the log is sent to the syslog log server, the message record of each user on the Radius server can be obtained from the syslog log server; if the log is sent to the database, the message record of each user on the Radius server can be obtained from the Radius message record database.

[0098] Step 202, filtering out the Radius message records whose message type is the first message type from the message records of the Radius server, and obtaining all the Radius message records whose message type is the first message type;

[0099] In one embodiment, the first message type refers to a charging end message type.

[0100] In one embodiment, by filtering out the Radius message records whose message type is the first message type from the message records of the Radius server, all Radius message records whose message type is the first message type are obtained, thereby preliminarily screening the users corresponding to the billing end messages in the Radius server.

[0101] Step 203, determining a first user set based on user names corresponding to messages in all Radius message records whose message types are the first message type;

[0102] In one embodiment, based on user names corresponding to messages in all Radius message records whose message types are the first message type, a set consisting of users indicated by the user names is determined as the first user set.

[0103] Step 204, filtering out message records whose message timestamps are within a first preset time interval from the first user set to obtain a second user set, wherein the first preset time interval is used to indicate a non-network change operation time interval;

[0104] In one embodiment, the network change operation time interval refers to a time period during which the network is adjusted, such as a network update operation time interval and a network structure adjustment operation time interval.

[0105] In one embodiment, the time interval with the lowest Internet traffic may be determined to be the network change operation time interval, such as 1:00 a.m. to 6:00 a.m.

[0106] In one embodiment, by filtering out the message records whose message timestamps are within the first preset time interval from the first user set, users whose interruptions are caused by network change operations can be eliminated from the first user set, thereby reducing the misidentification of users who are interrupted when using the network and reducing the false alarm rate.

[0107] Step 205: determine a target user set based on the second user set, wherein a user name corresponding to a message in the target user set corresponds to at least a message timestamp.

[0108] In one embodiment, the centralized message record of the second user includes the user name corresponding to the message, the message timestamp, the reason for termination of message billing, the online time of the message, and the uplink and downlink traffic during the online period.

[0109] In one embodiment, the target user centralized message record only includes the user name corresponding to the message and the message timestamp.

[0110] In one embodiment, the user name corresponding to a message in the target user set corresponds to at least one message timestamp, which means that the same user may be interrupted once or multiple times.

[0111] In one embodiment, if Figure 3 As shown, obtaining the first flow rate of each target user in the target user set at the interruption time includes:

[0112] Step 301, according to the user name and message timestamp corresponding to the message in the second user set, searching the message records of the Radius server for the previous message record corresponding to the user name and message timestamp corresponding to the message;

[0113] In one embodiment, the previous message record corresponding to the user name and message timestamp corresponding to the message refers to a message record having the same user name and a message timestamp that is adjacent to the previous one.

[0114] Step 302, obtaining a first online time and a first flow of a target user in a message record in a second user set; and obtaining a second online time and a second flow of a target user in a previous message record;

[0115] In one embodiment, the first online time refers to the online time of the target user in the second user set.

[0116] In one embodiment, the first traffic refers to the uplink and downlink traffic of the target user during the period when the second users are mostly online.

[0117] In one embodiment, the second online time refers to the target user's online time in the previous message record.

[0118] In one embodiment, the second traffic refers to the uplink and downlink traffic of the target user during the period when the target user is online in the previous message record.

[0119] In one embodiment, the first online time and the first traffic of the target user can be directly obtained from the target user's message record in the second user set, and the second online time and the second traffic of the target user can be obtained from the target user's previous message record.

[0120] Step 303: determining the online time difference of the target user based on the first online time and the second online time; and determining the flow rate difference of the target user based on the first flow rate and the second flow rate;

[0121] In one embodiment, the first online time is subtracted from the second online time to obtain the online time difference of the target user, and the first flow rate is subtracted from the second flow rate to obtain the flow difference of the target user.

[0122] In one embodiment, the traffic difference of the target user reflects the traffic change of the same user at adjacent message timestamps.

[0123] Step 304: compare the flow difference with the online time difference to obtain a first flow rate of the target user at the interruption time.

[0124] In one embodiment, the first flow rate refers to an average flow rate of the target user at adjacent message timestamps.

[0125] In one embodiment, by comparing the flow difference with the online time difference, a first flow rate of the target user at the interruption time is obtained, and whether the target user uses the network can be determined based on the size of the first flow rate.

[0126] In one embodiment, since the traffic collection in the related scheme adopts a special traffic collection system, it consumes a lot of resources. However, in this application, the traffic size of the target user is determined based on the message record of the Radius server, without adding additional equipment, thereby reducing resource consumption.

[0127] In one embodiment, if Figure 4 As shown, before obtaining the first online time and the first flow of the target user's message record in the second user set; and obtaining the second online time and the second flow of the target user's previous message record, the interruption identification method also includes:

[0128] Step 401, merging the message records in the second user set and the previous message record to obtain a third user set;

[0129] In one embodiment, the message record in the third user set includes the user name corresponding to the message, the message timestamp, the message billing termination reason, the message online time, and the uplink and downlink traffic during the online period.

[0130] Step 402, grouping the message records in the third user set according to the user name corresponding to the message, and obtaining the message records of each target user at different message timestamps;

[0131] Step 403 , sorting the message records of each target user with different message timestamps in the order of the message timestamps from small to large, to obtain the message records of each target user sorted in the order of the message timestamps from small to large.

[0132] In one embodiment, through the aforementioned steps 402 and 403, the first online time, the second online time, the first flow, and the second flow can be directly obtained from two adjacent message records of the same user.

[0133] In one embodiment, if Figure 5 As shown, obtaining the first port recovery number of each target user in the target user set at the interruption time includes:

[0134] Step 501, according to the user name corresponding to the target user set message, filter out the Radius server message record corresponding to the user name from the Radius server message record;

[0135] In one embodiment, the message types of the Radius server message records corresponding to the user name are filtered out from the Radius server message records, including authentication request message type, authentication success message type, authentication rejection message type, billing start message type, intermediate billing message type and billing end message type.

[0136] Step 502, determining the NAT public network port segment change value of the message record of each type of Radius server corresponding to the user name;

[0137] In one embodiment, the NAT public network port segment change value of the message record of each type of Radius server corresponding to the user name can be determined according to a preset rule.

[0138] In one embodiment, the NAT public network port segment change value of the message record of each type of Radius server corresponding to the user name may also be determined according to a preset value.

[0139] Step 503, summing the NAT public network port segment change values ​​of the message records of each type of Radius server corresponding to the user name, to obtain the number of NAT public network address ports corresponding to the user name, wherein the number of NAT public network address ports corresponding to the user name at least includes the number of NAT public network address ports corresponding to the user name at the time of interruption and the number of NAT public network address ports corresponding to the user name at the time before interruption;

[0140] In one embodiment, by summing up the NAT public network port segment change values ​​of the message records of each type of Radius server corresponding to the user name, the number of NAT public network address ports corresponding to the user name is obtained, and the number of NAT public network address ports of all message records corresponding to the user name can be obtained, and then the number of NAT public network address ports corresponding to the user name up to each message timestamp can be obtained.

[0141] In one embodiment, since there may be multiple NAT public address port numbers corresponding to the user name at the time of interruption, the NAT public address port number corresponding to the user name may include multiple NAT public address port numbers corresponding to the user name at the time of interruption and the NAT public address port number corresponding to the user name at the time before the interruption.

[0142] Step 504: Subtract the number of NAT public network address ports corresponding to the user name at the time of interruption from the number of NAT public network address ports corresponding to the user name before the interruption to obtain the first port recovery number of the target user at the time of interruption.

[0143] In one embodiment, the first port refers to a NAT public network port.

[0144] In one embodiment, the number of first ports recovered of the NAT public network address of the target user at the time of the interruption refers to the number of first ports recovered due to the interruption.

[0145] In one embodiment, by subtracting the number of NAT public network address ports corresponding to the user name at the time of interruption from the number of NAT public network address ports corresponding to the user name at the time before the interruption, the first port recovery number of the target user at the time of interruption is obtained, which can reflect whether the target user is in an online state.

[0146] In one embodiment, if Figure 6 As shown, the NAT public network port segment change value of the message record of each type of Radius server corresponding to the user name is determined, including:

[0147] Step 601, determining a message record containing a second message type from the message record of the Radius server corresponding to the user name, and obtaining a fourth user set;

[0148] In one embodiment, the second message type refers to a message type that carries a NAT public network port segment.

[0149] In one embodiment, the second message type includes a charging start message type, a charging end message type, and an intermediate charging message type carrying a NAT public network port segment.

[0150] Step 602: Group the fourth user set according to a first preset rule to obtain at least two fifth user sets, wherein the fifth user set includes a message type and a reason type for billing termination for each message record;

[0151] In one embodiment, grouping the fourth user set according to the first preset rule means grouping the fourth user set according to the user name corresponding to the message, the public network address specified in the message, the starting public network port number specified in the message, and the ending public network port number specified in the message.

[0152] In one embodiment, the user name corresponding to the message in the same fifth user set message record, the public network address specified in the message, the starting public network port specified in the message and the ending public network port specified in the message are all the same.

[0153] In one embodiment, the user names corresponding to the messages in different fifth user set message records, the public network addresses specified in the messages, the starting public network ports specified in the messages and the ending public network ports specified in the messages are all different or not completely the same.

[0154] In one embodiment, the reason types for billing termination include normal termination type and abnormal termination type.

[0155] In one embodiment, after the fourth user set is grouped according to the first preset rule, the messages in each group may be sorted in ascending order of message timestamps to obtain the message record of the target user in the time stream.

[0156] Step 603, determining a message identifier and a billing termination reason type identifier of each message record in the fifth user set based on the message type and the billing termination reason type of each message record in the fifth user set;

[0157] In one embodiment, based on the message type of each message record in the fifth user set and the type of reason for billing termination, different English letters may be used to determine the message identifier and the type identifier of the reason for billing termination of each message record in the fifth user set.

[0158] In one embodiment, based on the message type of each message record in the fifth user set and the type of reason for billing termination, different numbers may be used to determine the message identifier and the type identifier of the reason for billing termination of each message record in the fifth user set.

[0159] Specifically,

[0160] In one embodiment, if the message type of the concentrated message record of the fifth user is a billing start message type, it can be determined that the message identifier is 2.

[0161] In one embodiment, if the message type of the concentrated message record of the fifth user is a charging end message type, it can be determined that the message identifier is 1.

[0162] In one embodiment, if the reason type of billing termination is an abnormal termination type, the reason type identifier of billing termination can be determined to be a number greater than 0; if the reason type of billing termination is a normal termination type, the reason type identifier of billing termination can be determined to be 0.

[0163] In one embodiment, if the message type of the fifth user concentrated message record is an intermediate billing message type and the reason type for billing termination is an abnormal termination type, it can be determined that the message identifier is 2.

[0164] In one embodiment, if the message type of the fifth user concentrated message record is an intermediate billing message type and the reason type for billing termination is a normal termination type, it can be determined that the message identifier is 1.

[0165] Step 604: Determine the NAT public network port segment change value of the message record of each type of Radius server corresponding to the user name in the fifth user set based on the message identifier of each message record in the fifth user set, the reason type identifier for billing termination, and the second preset rule.

[0166] In one embodiment, if the message type of the first message record in the fifth user set is an intermediate billing message type and the reason type for billing termination is an abnormal termination type, the NAT public network port segment change value of the first message record in the fifth user set is determined to be 0.

[0167] In one embodiment, if the message type other than the first message record in the fifth user set is an intermediate billing message type and the reason type for billing termination is an abnormal termination type, then the NAT public network port segment change value of the first message record in the fifth user set is determined to be the difference between the starting public network port number specified in the message and the ending public network port number specified in the message.

[0168] In one embodiment, if the message type in the fifth user set is an intermediate billing message type and the reason type for billing termination is a normal termination type, the NAT public network port segment change value of the first message record in the fifth user set is determined to be the difference between the number of ending public network ports specified in the message and the number of starting public network ports specified in the message.

[0169] In one embodiment, after determining the message identifier and the type identifier of the reason for billing termination for each message record in the fifth user set based on the message type and the type of the reason for billing termination for each message record in the fifth user set, the interruption perception identification method further includes:

[0170] Sorting the messages in the fifth user set in ascending order of message timestamps to obtain a sorted fifth user set;

[0171] In one embodiment, the sorted message records in the fifth user set are message records of the same target user in the time stream.

[0172] Deleting message records that meet a third preset rule from the message records in the fifth user set to obtain a sixth user set;

[0173] In one embodiment, the third preset rule refers to a preset rule for removing duplicates.

[0174] In one embodiment, the third preset rule may also include message records with incomplete key information.

[0175] In one embodiment, deleting message records that meet the third preset rule from the message records of the fifth user set to obtain the sixth user set specifically includes: deleting message records that meet the message type of the intermediate billing message type, the reason type of the billing termination is the normal termination type and the message identifier is 1 from the message records of the fifth user set to obtain the sixth user set; deleting message records whose message identifiers and the reason type of the billing termination of two adjacent message records are the same and the message identifier is 2 from the message records of the fifth user set to obtain the sixth user set.

[0176] Based on the message identifier of each message record in the sixth user set, the billing termination reason type identifier and the second preset rule, the NAT public network port segment change value of the message record of each type of Radius server corresponding to the user name in the sixth user set is determined.

[0177] In one embodiment, by determining the NAT public port segment change value of the message record of each type of Radius server corresponding to the user name in the sixth user set based on the message identifier of each message record in the sixth user set, the reason type identifier for billing termination, and the second preset rule, the number of message records involved in the calculation can be reduced, thereby achieving cleaning of the message records.

[0178] In one embodiment, determining the NAT public network port segment change value of the message record of each type of Radius server corresponding to the user name includes:

[0179] Determine a message record containing a third message type from the message record of the Radius server corresponding to the user name, and obtain a seventh user set;

[0180] In one embodiment, the third message type refers to a message type that does not carry a NAT public network port segment.

[0181] In one embodiment, the third message type includes an authentication request message type, an authentication success message type, an authentication rejection message type, and an intermediate billing message type that does not carry a NAT public network port segment.

[0182] Determine that the NAT public network port segment change value of the message record of each type of Radius server corresponding to the user name in the seventh user set is a first preset value.

[0183] In one embodiment, since the first preset value is the NAT public network port segment change value, the message type in the message record of each type of Radius server corresponding to the user name in the seventh user set is a message type that does not carry the NAT public network port segment, so the first preset value is usually 0.

[0184] In one embodiment, after determining that the NAT public network port segment change value of the message record of each type of Radius server corresponding to the user name in the seventh user set is a first preset value, the interruption perception identification method also includes merging the NAT public network port segment change value of the message record of each type of Radius server corresponding to the user name in the fifth user set with the NAT public network port segment change value of the message record of each type of Radius server corresponding to the user name in the seventh user set, which is the first preset value, to obtain an eighth user set.

[0185] In one embodiment, since the allocated NAT public network port segment may change over time, it is also necessary to group the eighth user set according to the user name corresponding to the message, and sort the grouped eighth user set in ascending order of message timestamps.

[0186] In one embodiment, the concentrated message records of the eighth user are screened to select message records whose message type is a billing end message type and whose billing end reason type is a non-Host Request type.

[0187] In summary, the solution provided by the present disclosure is:

[0188] First, a target user set is obtained, wherein the target user set includes at least one target user; a first flow rate of each target user in the target user set at an interruption time and a first port recovery number of each target user in the target user set at an interruption time are obtained; if the first flow rate of the target user at the interruption time is not less than a first preset flow rate or the first port recovery number of the target user at the interruption time is not less than a first preset port number, the target user is determined to be an interruption-aware user, and whether the target user is aware of the interruption can be judged in combination with the first flow rate of the target user at the interruption time and the first port recovery number of the target user at the interruption time, thereby improving the recognition accuracy of the target user who is aware of the interruption.

[0189] Secondly, by filtering out the message records whose message timestamps are within the first preset time interval from the first user set, users whose interruptions are caused by network change operations can be eliminated from the first user set, thereby reducing the misidentification of users who are interrupted when using the network and reducing the false alarm rate.

[0190] Thirdly, the traffic size of the target user can be determined based on the message records of the Radius server, without adding additional equipment, thereby reducing resource consumption.

[0191] Again, by subtracting the number of NAT public network address ports corresponding to the user name at the time of interruption from the number of NAT public network address ports corresponding to the user name before the interruption, the first port recovery number of the target user at the time of interruption is obtained, which can reflect whether the target user is online.

[0192] Again, by determining the NAT public port segment change value of the message record of each type of Radius server corresponding to the user name in the sixth user set based on the message identifier of each message record in the sixth user set, the reason type identifier for billing termination and the second preset rule, the number of message records involved in the calculation can be reduced, thereby achieving the cleaning of the message records.

[0193] The interruption perception and recognition method provided by the present disclosure is further described below with an application example:

[0194] like Figure 7 As shown, Figure 7A flowchart of an interrupt perception identification method provided by an application example of the present disclosure. The interrupt perception identification method provided by an application example of the present disclosure comprises the following steps:

[0195] Step 701, obtaining the message record of each user in the Radius server, wherein one user corresponds to at least one message record, and each message record includes a message type, a message timestamp, and a user name corresponding to the message;

[0196] Step 702, filtering out the Radius message records whose message type is the first message type from the message records of the Radius server, and obtaining all the Radius message records whose message type is the first message type;

[0197] Step 703, determining a first user set based on user names corresponding to messages in all Radius message records whose message types are the first message type;

[0198] Step 704: Filter out message records whose message timestamps are within a first preset time interval from the first user set to obtain a second user set, where the first preset time interval is used to indicate a non-network change operation time interval;

[0199] Step 705: determining a target user set based on the second user set, wherein a user name corresponding to a message in the target user set corresponds to at least a message timestamp;

[0200] Step 706, according to the user name and message timestamp corresponding to the message in the second user set, searching the message records of the Radius server for the previous message record corresponding to the user name and message timestamp corresponding to the message;

[0201] In one embodiment, before obtaining the first online time and the first flow of the target user in the message record of the second user set; and obtaining the second online time and the second flow of the target user in the previous message record, the interruption perception identification method further includes:

[0202] Merging the message record in the second user set and the previous message record to obtain a third user set;

[0203] Grouping the message records in the third user set according to the user name corresponding to the message to obtain message records of each target user with different message timestamps;

[0204] According to the order of the message timestamps from small to large, the message records of each target user with different message timestamps are sorted to obtain the message records of each target user sorted from small to large message timestamps.

[0205] Step 707, obtaining the first online time and the first flow of the target user in the message record of the second user set; and obtaining the second online time and the second flow of the target user in the previous message record;

[0206] Step 708, determining the online time difference of the target user based on the first online time and the second online time; and determining the flow difference of the target user based on the first flow and the second flow;

[0207] Step 709, comparing the flow difference with the online time difference to obtain a first flow rate of the target user at the interruption time;

[0208] Step 710, according to the user name corresponding to the target user set message, filter out the Radius server message record corresponding to the user name from the Radius server message record;

[0209] Step 711, determining a message record containing a second message type from the message record of the Radius server corresponding to the user name, and obtaining a fourth user set;

[0210] Step 712: grouping the fourth user set according to the first preset rule to obtain at least two fifth user sets, wherein the fifth user set includes a message type and a reason type for billing termination for each message record;

[0211] Step 713, determining a message identifier and a billing termination reason type identifier of each message record in the fifth user set based on the message type and the billing termination reason type of each message record in the fifth user set;

[0212] Step 714, based on the message identifier of each message record in the fifth user set, the type identifier of the reason for billing termination, and the second preset rule, determine the NAT public network port segment change value of the message record of each type of Radius server corresponding to the user name in the fifth user set;

[0213] Step 715, summing the NAT public network port segment change values ​​of the message records of each type of Radius server corresponding to the user name to obtain the number of NAT public network address ports corresponding to the user name;

[0214] In one embodiment, the NAT public network address port number corresponding to the user name includes at least the NAT public network address port number corresponding to the user name at the interruption time and the NAT public network address port number corresponding to the user name before the interruption time.

[0215] Step 716, subtract the number of NAT public network address ports corresponding to the user name at the time of interruption from the number of NAT public network address ports corresponding to the user name at the time before interruption to obtain the first port recovery number of the target user at the time of interruption;

[0216] Step 717: If the first flow rate of the target user at the interruption time is not less than the first preset flow rate or the first port recovery number of the target user at the interruption time is not less than the first preset port number, the target user is determined to be an interruption-aware user.

[0217] In order to implement the interruption perception and recognition method provided by the embodiment of the present disclosure, the embodiment of the present disclosure also provides an interruption perception and recognition device, such as Figure 8 shown. Figure 8 The schematic diagram of the structure of the interruption perception and recognition device provided in the embodiment of the present disclosure is as follows. The interruption perception and recognition device 800 includes:

[0218] A first acquisition unit 801 is used to acquire a target user set, where the target user set includes at least one target user;

[0219] The second acquisition unit 802 is used to acquire a first flow rate of each target user in the target user set at the interruption time and a first port recovery number of each target user in the target user set at the interruption time;

[0220] The determination unit 803 is configured to determine that the target user is an interruption-aware user if the first flow rate of the target user at the interruption time is not less than the first preset flow rate or the first port recovery number of the target user at the interruption time is not less than the first preset port number.

[0221] In one embodiment, the first acquisition unit 801 is specifically configured to:

[0222] Obtain the message records of each user in the Radius server, where one user corresponds to at least one message record, and each message record contains the message type, message timestamp, and the user name corresponding to the message;

[0223] Filter out the Radius message records whose message type is the first message type from the message records of the Radius server, and obtain all the Radius message records whose message type is the first message type;

[0224] Determine a first user set based on user names corresponding to messages in all Radius message records whose message types are the first message type;

[0225] Filtering message records with message timestamps within a first preset time interval from the first user set to obtain a second user set, wherein the first preset time interval is used to indicate a non-network change operation time interval;

[0226] Based on the second user set, a target user set is determined, wherein a user name corresponding to a message in the target user set corresponds to at least a message timestamp.

[0227] In one embodiment, the second obtaining unit 802 is specifically configured to:

[0228] According to the user name and message timestamp corresponding to the message in the second user set, searching the message record of the Radius server for the previous message record corresponding to the user name and message timestamp corresponding to the message;

[0229] Obtain the first online time and the first flow of the target user in the message record of the second user set; and obtain the second online time and the second flow of the target user in the previous message record;

[0230] Determine an online time difference of a target user based on the first online time and the second online time; and determine a flow rate difference of the target user based on the first flow rate and the second flow rate;

[0231] The flow difference is compared with the online time difference to obtain a first flow rate of the target user at the interruption moment.

[0232] In one embodiment, the interruption perception and recognition device 800 further includes a sorting unit, which is used to:

[0233] Merging the message record in the second user set and the previous message record to obtain a third user set;

[0234] Grouping the message records in the third user set according to the user name corresponding to the message to obtain message records of each target user with different message timestamps;

[0235] According to the order of the message timestamps from small to large, the message records of each target user with different message timestamps are sorted to obtain the message records of each target user sorted from small to large message timestamps.

[0236] In one embodiment, the second obtaining unit 802 is specifically configured to:

[0237] According to the user name corresponding to the target user set message, filter out the message record of the Radius server corresponding to the user name from the message record of the Radius server;

[0238] Determine the NAT public network port segment change value of the message record of each type of Radius server corresponding to the user name;

[0239] Sum the NAT public network port segment change values ​​of the message records of each type of Radius server corresponding to the user name to obtain the number of NAT public network address ports corresponding to the user name, wherein the number of NAT public network address ports corresponding to the user name at least includes the number of NAT public network address ports corresponding to the user name at the time of interruption and the number of NAT public network address ports corresponding to the user name at the time before interruption;

[0240] The number of NAT public network address ports corresponding to the user name at the time of interruption is subtracted from the number of NAT public network address ports corresponding to the user name at the time before interruption to obtain the first port recovery number of the target user at the time of interruption.

[0241] In one embodiment, the second obtaining unit 802 is specifically configured to:

[0242] Determine a message record containing a second message type from the message record of the Radius server corresponding to the user name, and obtain a fourth user set;

[0243] Grouping the fourth user set according to a first preset rule to obtain at least two fifth user sets, wherein the fifth user set includes a message type and a reason type for billing termination for each message record;

[0244] Determine, based on the message type of each message record in the fifth user set and the type of the reason for billing termination, a message identifier and a type identifier of the reason for billing termination for each message record in the fifth user set;

[0245] Based on the message identifier of each message record in the fifth user set, the billing termination reason type identifier and the second preset rule, the NAT public network port segment change value of the message record of each type of Radius server corresponding to the user name in the fifth user set is determined.

[0246] It should be noted that: when the interrupt perception and recognition device provided in the above embodiment performs interrupt perception and recognition, only the division of the above program modules is used as an example. In actual applications, the above processing can be assigned to different program modules as needed, that is, the internal structure of the interrupt perception and recognition device is divided into different program modules to complete all or part of the processing described above. In addition, the interrupt perception and recognition device provided in the above embodiment and the interrupt perception and recognition method embodiment provided in the embodiment of the present disclosure belong to the same concept. The specific implementation process is detailed in the method embodiment and will not be repeated here.

[0247] Fig. 9A schematic diagram of the hardware structure of an electronic device provided in an embodiment of the present disclosure is shown in FIG. Fig. 9 As shown, the electronic device 900 includes at least one processor 902; and a memory 901 that is communicatively connected to the at least one processor 902; wherein the memory 901 stores instructions that can be executed by the at least one processor 902, and the instructions are executed by the at least one processor 902 to implement the steps of the interrupt perception identification method of the embodiment of the present disclosure.

[0248] Optionally, the electronic device may specifically be the interruption perception and recognition device of the embodiment of the present application, and the electronic device may implement the corresponding processes implemented by the interruption perception and recognition device in each method of the embodiment of the present application, which will not be described in detail here for the sake of brevity.

[0249] It is understood that the electronic device also includes a communication interface 903. The various components in the electronic device are coupled together through a bus system 904. It is understood that the bus system 904 is used to realize the connection and communication between these components. In addition to the data bus, the bus system 904 also includes a power bus, a control bus, and a status signal bus. However, for the sake of clarity, Fig. 9 Various buses are labeled as bus system 904.

[0250] It can be understood that the memory 901 can be a volatile memory or a non-volatile memory, and can also include both volatile and non-volatile memories. Among them, the non-volatile memory can be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), a magnetic random access memory (FRAM), a flash memory, a magnetic surface memory, an optical disc, or a compact disc read-only memory (CD-ROM); the magnetic surface memory can be a disk memory or a tape memory. The volatile memory can be a random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as static random access memory (SRAM), synchronous static random access memory (SSRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDRSDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM, SyncLink Dynamic Random Access Memory), and direct RAMbus random access memory (DRRAM, Direct Rambus Random Access Memory).The memory 901 described in the embodiment of the present invention is intended to include but is not limited to these and any other suitable types of memories.

[0251] The method disclosed in the above embodiment of the present disclosure can be applied to the processor 902, or implemented by the processor 902. The processor 902 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method can be completed by an integrated logic circuit of hardware in the processor 902 or an instruction in the form of software. The above processor 902 may be a general-purpose processor, a DSP, or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components, etc. The processor 902 can implement or execute the various methods, steps and logic block diagrams disclosed in the embodiments of the present invention. The general-purpose processor may be a microprocessor or any conventional processor, etc. In combination with the steps of the method disclosed in the embodiment of the present invention, it can be directly embodied as a hardware decoding processor to execute, or it can be executed by a combination of hardware and software modules in the decoding processor. The software module can be located in a storage medium, which is located in the memory 901, and the processor 902 reads the information in the memory 901 and completes the steps of the above method in combination with its hardware.

[0252] In an exemplary embodiment, the electronic device may be implemented by one or more application specific integrated circuits (ASICs), DSPs, programmable logic devices (PLDs), complex programmable logic devices (CPLDs), FPGAs, general purpose processors, controllers, MCUs, microprocessors, or other electronic components to execute the aforementioned method.

[0253] The disclosed embodiment also provides a non-transitory computer-readable storage medium storing computer instructions, where the computer instructions are used to enable a computer to implement the steps of the interruption awareness and recognition method of the embodiment of the present invention when executed.

[0254] Optionally, the computer-readable storage medium can be applied to the interrupt perception and identification device in the embodiments of the present application, and the computer instructions enable the computer to execute the corresponding processes implemented by the interrupt perception and identification device in the various methods of the embodiments of the present application. For the sake of brevity, they are not repeated here.

[0255] The embodiment of the present disclosure also provides a computer program product, including a computer program, which implements the steps of the interrupt perception and identification method provided by the embodiment of the present invention when executed by a processor.

[0256] In the several embodiments provided in the present application, it should be understood that the disclosed devices and methods can be implemented in other ways. The device embodiments described above are only schematic. For example, the division of 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 can be integrated into another system, or some features can be ignored or not executed. In addition, the coupling, direct coupling, or communication connection between the components shown or discussed can be through some interfaces, and the indirect coupling or communication connection of devices or units can be electrical, mechanical or other forms.

[0257] The units described above as separate components may or may not be physically separated, and the components displayed 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 present embodiment.

[0258] In addition, all functional units in the embodiments of the present invention may be integrated into one processing unit, or each unit may be separately used as a unit, or two or more units may be integrated into one unit; the above-mentioned integrated units may be implemented in the form of hardware or in the form of hardware plus software functional units.

[0259] A person of ordinary skill in the art can understand that: all or part of the steps of implementing the above-mentioned method embodiment can be completed by hardware related to program instructions, and the aforementioned program can be stored in a computer-readable storage medium, which, when executed, executes the steps of the above-mentioned method embodiment; and the aforementioned storage medium includes: various media that can store program codes, such as mobile storage devices, ROM, RAM, disks or optical disks.

[0260] Alternatively, if the above-mentioned integrated unit of the present invention is implemented in the form of a software function module and sold or used as an independent product, it can also be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the embodiment of the present invention can be essentially or partly reflected 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, a server, or a network device, etc.) to execute all or part of the methods of each embodiment of the present invention. The aforementioned storage medium includes: various media that can store program codes, such as mobile storage devices, ROM, RAM, magnetic disks or optical disks.

[0261] The above is only a specific embodiment of the present invention, but the protection scope of the present invention is not limited thereto. Any person skilled in the art can easily think of changes or substitutions within the technical scope disclosed by the present invention, which should be included in the protection scope of the present invention. Therefore, the protection scope of the present invention should be based on the protection scope of the claims.

Claims

1. A method for interruption perception and recognition, characterized in that: include: Acquire a target user set, where the target user set includes at least one target user; Acquire a first flow rate of each target user in the target user set at the interruption time and a first port recovery number of each target user in the target user set at the interruption time; If the first flow rate of the target user at the interruption time is not less than the first preset flow rate or the first port recovery number of the target user at the interruption time is not less than the first preset port number, the target user is determined to be an interruption-aware user.

2. The method according to claim 1, characterized in that The step of obtaining the target user set includes: Obtain the message records of each user in the Radius server, where one user corresponds to at least one message record, and each message record contains the message type, message timestamp, and the user name corresponding to the message; Filter out the Radius message records whose message type is the first message type from the message records of the Radius server, and obtain all the Radius message records whose message type is the first message type; Determine a first user set based on user names corresponding to messages in all Radius message records whose message types are the first message type; Filtering message records with message timestamps within a first preset time interval from the first user set to obtain a second user set, wherein the first preset time interval is used to indicate a non-network change operation time interval; Based on the second user set, a target user set is determined, wherein a user name corresponding to a message in the target user set corresponds to at least a message timestamp.

3. The method according to claim 1, characterized in that The obtaining of the first flow rate of each target user in the target user set at the interruption time includes: According to the user name and message timestamp corresponding to the message in the second user set, searching the message record of the Radius server for the previous message record corresponding to the user name and message timestamp corresponding to the message; Obtain the first online time and the first flow of the target user in the message record of the second user set; and obtain the second online time and the second flow of the target user in the previous message record; Determine an online time difference of a target user based on the first online time and the second online time; and determine a flow rate difference of the target user based on the first flow rate and the second flow rate; The flow difference is compared with the online time difference to obtain a first flow rate of the target user at the interruption moment.

4. The method according to claim 3, characterized in that The step of obtaining a first online time and a first flow of a message record of a target user in a second user set; Before obtaining the second online time and the second flow of the target user in the previous message record, the method further includes: Merging the message record in the second user set and the previous message record to obtain a third user set; Grouping the message records in the third user set according to the user name corresponding to the message to obtain message records of each target user with different message timestamps; The message records of each target user with different message timestamps are sorted in ascending order of the message timestamps to obtain the message records of each target user sorted in ascending order of the message timestamps.

5. The method according to claim 1, characterized in that The obtaining of the first port recovery number of each target user in the target user set at the interruption time includes: According to the user name corresponding to the target user set message, filter out the message record of the Radius server corresponding to the user name from the message record of the Radius server; Determine the NAT public network port segment change value of the message record of each type of Radius server corresponding to the user name; Sum the NAT public network port segment change values ​​of the message records of each type of Radius server corresponding to the user name to obtain the number of NAT public network address ports corresponding to the user name, wherein the number of NAT public network address ports corresponding to the user name at least includes the number of NAT public network address ports corresponding to the user name at the time of interruption and the number of NAT public network address ports corresponding to the user name at the time before interruption; The number of NAT public network address ports corresponding to the user name at the time of interruption is subtracted from the number of NAT public network address ports corresponding to the user name at the time before interruption to obtain the first port recovery number of the target user at the time of interruption.

6. The method according to claim 5, characterized in that The step of determining the NAT public network port segment change value of the message record of each type of Radius server corresponding to the user name includes: Determine a message record containing a second message type from the message record of the Radius server corresponding to the user name, and obtain a fourth user set; Grouping the fourth user set according to a first preset rule to obtain at least two fifth user sets, wherein the fifth user set includes a message type and a reason type for billing termination for each message record; Determine, based on the message type of each message record in the fifth user set and the type of the reason for billing termination, a message identifier and a type identifier of the reason for billing termination for each message record in the fifth user set; Based on the message identifier of each message record in the fifth user set, the billing termination reason type identifier and the second preset rule, the NAT public network port segment change value of the message record of each type of Radius server corresponding to the user name in the fifth user set is determined.

7. An interruption perception and recognition device, characterized in that: include: A first acquisition unit, configured to acquire a target user set, wherein the target user set includes at least one target user; A second acquisition unit is used to acquire a first flow rate of each target user in the target user set at the interruption time and a first port recovery number of each target user in the target user set at the interruption time; The determination unit is used to determine that the target user is an interruption-aware user if the first flow rate of the target user at the interruption time is not less than the first preset flow rate or the first port recovery number of the target user at the interruption time is not less than the first preset port number.

8. An electronic device, characterized in that: include: at least one processor; as well as a memory communicatively connected to the at least one processor; wherein, The memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to perform the method according to any one of claims 1 to 6.

9. A non-transitory computer-readable storage medium storing computer instructions, characterized in that: The computer instructions are used to cause the computer to execute the method according to any one of claims 1 to 6.

10. A computer program product, comprising a computer program, wherein the computer program implements the method according to any one of claims 1 to 6 when executed by a processor.

Images