A user flow log processing method

Abstract

This application provides a user flow log processing method. The method is applied to the iBRAS front-end and includes: sampling user service traffic through an APA board; generating user flow logs including application identifiers and / or URL information based on the sampling results; for each user flow log, matching a corresponding priority based on the application identifier or URL information in the log to obtain the priority of each log; and transmitting the user flow logs to the iBRAS back-end according to priority order, so that the iBRAS back-end can perform QoE analysis on the logs and obtain the QoE analysis results. This method ensures that flow logs of key applications are processed first, guaranteeing the integrity and timeliness of key application data, thereby making data analysis more accurate and effective.

Description

Technical Field

[0001] This application relates to the field of network communication technology, and in particular to a method for processing user flow logs. Background Technology

[0002] iBRAS (Intelligent Broadband Remote Access Server) is a network device / solution that integrates AI computing power and service awareness capabilities on the basis of traditional BRAS (Broadband Remote Access Server). It is used in large-scale broadband access scenarios and can perform fine-grained identification of different services of massive users, differentiated service quality assurance and traffic management, helping operators achieve precise operation.

[0003] iBRAS service awareness is a function within iBRAS that focuses on service identification, scheduling, and QoS (Quality of Service) assurance. Its basic architecture includes the iBRAS front-end and the iBRAS back-end. After enabling QoE (Quality of Experience), the iBRAS front-end generates user flow logs and sends them to the iBRAS back-end for analysis. However, in high-concurrency scenarios such as metropolitan area networks with millions of home broadband users and enterprise leased lines, performance bottlenecks exist in both the iBRAS front-end and back-end, easily leading to missing or delayed application data, resulting in inaccurate data analysis. Summary of the Invention

[0004] This application provides a user flow log processing method to ensure the integrity and timeliness of key application data in the iBRAS business-aware QoE function, thereby making data analysis more accurate and effective.

[0005] Specifically, this application provides the following technical solution: In a first aspect, this application provides a user stream log processing method, which is applied to the iBRAS front end, and the method includes: The user's business traffic is sampled through the APA board, and user flow logs including application identifiers and / or URL information are generated based on the sampling results. For each user stream log, the priority of each user stream log is obtained by matching the corresponding priority based on the application identifier or URL information in the user stream log. User flow logs are transmitted to the iBRAS backend in order of priority so that the iBRAS backend can perform QoE analysis on the user flow logs and obtain the QoE analysis results.

[0006] Secondly, this application provides a user stream log processing method, which is applied to the iBRAS backend, and the method includes: Receive user flow logs transmitted by the iBRAS front end in priority order. The user flow logs include application identifiers and / or URL information. The priority is obtained by the iBRAS front end matching the user flow logs based on the application identifiers or URL information in the user flow logs. Perform QoE analysis on user flow logs to obtain QoE analysis results.

[0007] Thirdly, this application provides an iBRAS front-end for performing the methods described above.

[0008] Fourthly, this application provides an iBRAS backend for performing the methods described above.

[0009] Fifthly, this application provides an iBRAS service awareness system, which includes the iBRAS front-end as described above, and also includes the iBRAS back-end as described above.

[0010] Sixthly, this application provides an electronic device, comprising: A memory, one or more processors; the memory is coupled to the processors; wherein the memory stores computer program code, the computer program code including computer instructions, and when the computer instructions are executed by the processor, the electronic device performs the method described above.

[0011] In a seventh aspect, this application provides a computer-readable storage medium including computer instructions that, when executed on an electronic device, cause the electronic device to perform the method described above.

[0012] Eighthly, this application provides a computer program product that, when run on a computer, causes the computer to perform the method described above.

[0013] The technical solution provided in this application has the following beneficial effects: This application pre-configures priorities for different applications and / or URLs, with different priorities corresponding to different levels of business importance and QoE assurance. During the processing of user flow logs, the application identifier or URL information carried in the user flow logs is matched with the corresponding priority, and the user flow logs are scheduled for transmission according to the priority order to achieve priority processing and assurance of important business QoE information.

[0014] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and do not limit this application. Attached Figure Description

[0015] The accompanying drawings, which are incorporated in and form part of this application, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application.

[0016] Figure 1 A flowchart illustrating a user flow log processing method applied to the iBRAS front end, as provided in an embodiment of this application; Figure 2 A flowchart illustrating a user flow log processing method applied to the iBRAS backend, provided in an embodiment of this application; Figure 3 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Detailed Implementation

[0017] The technical solution of this application will be clearly and completely described below with reference to the accompanying drawings and specific embodiments. It should be understood that the drawings and embodiments of this application are for illustrative purposes only and are not intended to limit the scope of protection of this application. This application can be implemented in many different forms and should not be construed as limited to the embodiments described herein.

[0018] The iBRAS service awareness system includes an iBRAS front-end and an iBRAS back-end. In this application, the iBRAS front-end is implemented by an APA (Application Aware) board on the BRAS device. The iBRAS back-end, as a multi-functional service platform, is implemented by a controller and interconnects with the iBRAS front-end via a north-south interface.

[0019] After enabling the QoE function on the iBRAS front-end APA board, the APA board will sample user business traffic, generate user flow logs, and send the user flow logs to the iBRAS backend. The iBRAS backend is responsible for performing QoE analysis on user business traffic based on the user flow logs and presenting the QoE analysis results through a visual interface.

[0020] For scenarios where QoE is enabled in iBRAS service awareness scenarios, this application provides a user flow log processing solution. The core of this solution is to effectively prioritize user flow logs during transmission and analysis, prioritizing the transmission and analysis of user flow logs for key applications. This ensures the integrity and timeliness of data for key applications, thereby making data analysis more accurate and effective.

[0021] The technical solution and its beneficial effects of this application will be described in detail below through specific embodiments.

[0022] This embodiment provides a user flow log processing method applied to the iBRAS front end. For example... Figure 1 As shown, the user flow log processing method in this embodiment may include the following steps: S110. Sample user business traffic through the APA board and generate user flow logs including application identifiers and / or URL information based on the sampling results.

[0023] When the QoE function of the iBRAS front-end APA board is enabled, the APA board samples user service traffic. User service traffic refers to the total network transmission data generated when a user uses a specific service (such as VoIP calls, video calls, web browsing, online video, etc.), specifically including user signaling packets and user data packets.

[0024] User signaling messages refer to control messages used for business session control, connection establishment, negotiation, maintenance and release, such as session establishment request messages, capability negotiation messages, heartbeat maintenance messages, session termination messages, etc.; user data messages refer to data messages used to carry the actual content of the business, such as voice data messages, video data messages, web page content data messages, etc.

[0025] Specifically, during the sampling process, the APA board identifies and filters the user service traffic flowing through it. Based on a preset sampling strategy, it extracts and parses the corresponding user signaling and data packets from the user service traffic. For user signaling packets, it parses information such as session identifier, user identifier, application identifier, URL information, service type, session establishment time, and signaling interaction latency. For user data packets, it parses information such as the 5-tuple, packet timestamp, packet length, transmission latency, jitter, and packet loss.

[0026] Based on the information obtained from the above analysis, the APA board organizes the data into a structured format according to a preset log format to generate user flow logs. These user flow logs are structured data reflecting the characteristics and quality of user service traffic, providing the raw data foundation for subsequent QoE analysis by the iBRAS backend according to preset priorities.

[0027] It is worth mentioning that, in this application, the user flow logs generated by the APA board include at least application identifiers and / or URL information to identify the specific application or access address corresponding to the current user service traffic. In addition, the user flow logs may also include any one or more of the following: user identifier, service type, session identifier, flow identifier, timestamp, signaling-related information, and data packet transmission quality indicators.

[0028] S120. For each user stream log, match the corresponding priority for the user stream log based on the application identifier or URL information in the user stream log to obtain the priority of each user stream log.

[0029] S130. Transmit user flow logs to the iBRAS backend according to priority order, so that the iBRAS backend can perform QoE analysis on the user flow logs and obtain the QoE analysis results.

[0030] Specifically, the APA board queries the preset priority configuration and accurately matches the corresponding preset priority based on the application identifier and / or URL information carried in the user flow logs. Then, following the principle of "higher priority logs are transmitted first, and logs of the same priority are transmitted in order of generation time from earliest to latest," the user flow logs are transmitted one by one to the iBRAS backend via the southbound interface. This avoids low-priority logs consuming transmission resources and ensures that user flow logs for high-priority services are delivered to the iBRAS backend quickly and with priority.

[0031] In this application, different applications / URLs correspond to different levels of business importance and QoE assurance levels in the priority configuration. The priority configuration is pre-stored locally on the APA board and can be updated remotely by the backend.

[0032] Optionally, this application implements the above priority configuration through the APA board feature library. Specifically, the feature library includes a predefined feature library and a custom feature library. The iBRAS backend loads the feature library onto the APA board through the northbound interface with the iBRAS frontend and realizes remote management of the feature library on the APA board.

[0033] Optionally, this application also includes the following steps: receiving deployment instructions from the iBRAS backend via the northbound interface, and loading the feature library containing priority configuration into the APA board according to the deployment instructions.

[0034] Optionally, this application also includes the following steps: receiving update instructions from the iBRAS backend through the northbound interface, and performing corresponding update operations on the local priority configuration according to the update instructions, specifically performing corresponding update operations on the feature library.

[0035] After receiving the user flow logs, the iBRAS backend performs QoE analysis on the user flow logs and obtains the QoE analysis results.

[0036] Optionally, the iBRAS backend determines the analysis priority of the user flow logs based on the application identifier or URL information in the user flow logs, performs QoE analysis on the user flow logs according to the analysis priority order, and obtains the QoE analysis results.

[0037] As a specific implementation, the priority order used by the iBRAS front-end when transmitting user flow logs can be the same as the priority order used by the iBRAS back-end when analyzing user flow logs. In other words, the iBRAS front-end and back-end can share a set of priority configurations, and both can match user flow logs to the same priority based on the application identifier or URL information in the user flow logs.

[0038] As another specific implementation, since the transmission and analysis processes of user flow logs consume different network and computing resources, the priority order used by the iBRAS front-end when transmitting user flow logs can differ from the priority order used by the iBRAS back-end when analyzing user flow logs. In this case, the iBRAS front-end and back-end use different priority configurations, matching different priorities to the user flow logs based on the application identifier or URL information in the logs; these priorities are referred to as transmission priority and analysis priority, respectively. For example: For each generated user stream log, the iBRAS front end matches the corresponding priority for the user stream log in the first priority configuration based on the application identifier or URL information in the user stream log, and obtains the transmission priority of each user stream log. Then, the user stream logs are transmitted to the iBRAS back end in order of transmission priority. For each received user flow log, the iBRAS front end matches the corresponding priority for that user flow log in the second priority configuration based on the application identifier or URL information in the user flow log, and obtains the analysis priority of each user flow log. Then, QoE analysis is performed on the user flow logs according to the analysis priority order.

[0039] Furthermore, the iBRAS backend categorizes analysis priorities into three levels: high, medium, and low. For different analysis priorities, the iBRAS backend employs different analysis strategies. For example, it uses a real-time parsing mode to perform QoE analysis on high-priority user flow logs, and a batch parsing mode to perform QoE analysis on medium- and low-priority user flow logs.

[0040] In this application, different priorities are pre-configured for different applications and / or URLs, with different applications or URLs corresponding to different levels of business importance and QoE protection. During the transmission of user stream logs, the corresponding preset priorities are matched based on the application identifiers and / or URL information carried in the user stream logs, and the transmission of user stream logs is scheduled according to the preset priority order to achieve priority processing and protection of important business QoE information.

[0041] As can be seen from the above technical solutions, the method of this embodiment can achieve the following beneficial effects: By enabling QoE functionality, prioritizing different applications / URLs and transmitting and analyzing user flow logs according to priority, we can achieve priority processing of important business QoE information, thereby improving the execution efficiency and protection effectiveness of QoE functionality.

[0042] Accordingly, this embodiment provides a user flow log processing method applied to the iBRAS backend. For example... Figure 2 As shown, the user flow log processing method in this embodiment may include the following steps: S210. Receive user flow logs transmitted by the iBRAS front end in priority order, wherein the user flow logs include application identifiers and / or URL information, and the priority is obtained by the iBRAS front end by matching the application identifiers or URL information in the user flow logs.

[0043] Optionally, the iBRAS backend sends a deployment command to the iBRAS frontend, deploying the feature library containing priority configurations to the APA board of the iBRAS frontend. Subsequently, the iBRAS frontend loads the feature library containing priority configurations into the APA board. In subsequent processes, the APA board is used to sample user service traffic, and user flow logs, including application identifiers and / or URL information, are generated based on the sampling results. For each user flow log, the iBRAS frontend matches the corresponding priority to the application identifier or URL information in the log, obtaining the priority of each user flow log. Finally, the user flow logs are transmitted to the iBRAS backend in priority order.

[0044] Afterwards, the iBRAS backend receives user flow logs transmitted by the iBRAS frontend in priority order via the southbound interface.

[0045] S220. Perform QoE analysis on the user flow logs to obtain the QoE analysis results.

[0046] Optionally, the iBRAS backend identifies the application identifier and / or URL information in each user flow log, matches the corresponding analysis priority, and performs QoE analysis on the user flow logs according to the analysis priority order. Specifically, high-priority user flow logs are given priority for QoE analysis, including data extraction, quality indicator calculation and analysis, and then medium and low-priority user flow logs are processed in sequence.

[0047] Specifically, for each received user stream log, the iBRAS backend queries the preset priority configuration and matches the corresponding analysis priority to the user stream log based on the application identifier or URL information in the log. This priority configuration can be implemented through the feature library of the APA board, including predefined and custom feature libraries. The iBRAS backend can remotely manage this feature library, such as deploying it to the APA board or updating it.

[0048] Furthermore, high-priority user flow logs can be analyzed using real-time parsing mode to quickly calculate core indicators such as latency, jitter, and packet loss rate, and generate quality feedback in a timely manner; medium- and low-priority user flow logs can be analyzed using batch parsing mode, thereby completing the analysis without affecting the processing efficiency of high-priority services.

[0049] Optionally, this application adds a priority customization configuration item to the custom feature library. The method may also include the following steps: setting the corresponding priority for the target application identifier or target URL information according to the configuration instructions for the custom feature library.

[0050] This embodiment introduces the concept of priority into the feature library, adding priority markers to applications or URLs in both predefined and custom feature libraries. The iBRAS front-end and back-end send and analyze stream logs based on priority, ensuring the integrity and timeliness of key application data, thereby making data analysis more accurate and effective.

[0051] Based on the same inventive concept, this embodiment provides an iBRAS front-end, which is used to execute the user flow log processing method applied to the iBRAS front-end as described above.

[0052] This embodiment provides an iBRAS backend, which is used to execute the user flow log processing method applied to the iBRAS backend as described above.

[0053] This embodiment provides an iBRAS service awareness system, which includes the iBRAS front-end as described above, and the iBRAS back-end as described above.

[0054] The iBRAS front-end, iBRAS back-end, and iBRAS service awareness system provided in this embodiment are used to execute the corresponding methods described above. Therefore, the beneficial effects they can achieve can be referred to in the beneficial effects of the corresponding methods described above, and will not be repeated here.

[0055] This embodiment provides an electronic device that may include a memory and one or more processors. The memory stores computer program code, which includes computer instructions. When the processor executes the computer instructions, the electronic device can perform various functions or steps of the method embodiments described above.

[0056] The structure of this electronic device can be referenced. Figure 3 The structure of the electronic device 100 shown.

[0057] For example, the processor mentioned above can be a general-purpose processor, including a central processing unit (CPU), a network processor (NP), etc.; it can also be a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components.

[0058] This embodiment provides a computer-readable storage medium including computer instructions that, when executed on an electronic device, cause the electronic device to perform various functions or steps of the above method embodiments.

[0059] The aforementioned computer-readable storage media include, but are not limited to, any of the following: USB flash drive, portable hard drive, read-only memory (ROM), random access memory (RAM), magnetic disk or optical disk, and other media capable of storing program code.

[0060] This application provides a computer program product that, when run on a computer, causes the computer to perform various functions or steps of the above-described method embodiments.

[0061] The aforementioned electronic devices, computer-readable storage media, and computer program product embodiments are all used to execute the corresponding methods provided above. Therefore, the beneficial effects they can achieve can be referred to the beneficial effects of the corresponding methods provided above, and will not be repeated here.

[0062] The above are merely specific embodiments of this application and are not intended to limit the scope of protection of this application. For those skilled in the art, the technical solutions of this application can have various variations or substitutions. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the scope of the claims of this application.

Claims

1. A method for processing user stream logs, characterized in that, The method is applied to the iBRAS front end, and the method includes: The user's business traffic is sampled through the APA board, and user flow logs including application identifiers and / or URL information are generated based on the sampling results. For each user stream log, the priority of each user stream log is obtained by matching the corresponding priority based on the application identifier or URL information in the user stream log. User flow logs are transmitted to the iBRAS backend in order of priority so that the iBRAS backend can perform QoE analysis on the user flow logs and obtain the QoE analysis results.

2. The method according to claim 1, characterized in that, The method specifically transmits user flow logs to the iBRAS backend in priority order as follows: User stream logs are transmitted to the iBRAS backend according to the principle of transmitting high-priority logs first, and transmitting logs of the same priority in order of generation time from earliest to latest.

3. The method according to claim 1, characterized in that, The method specifically matches the corresponding priority for the user flow log based on the application identifier or URL information in the user flow log in the following way: By querying the preset priority configuration, the system matches the corresponding priority for the user flow log based on the application identifier or URL information in the user flow log.

4. The method according to claim 3, characterized in that, The priority configuration is recorded in the feature library of the APA board, which includes a predefined feature library and a custom feature library.

5. The method according to claim 4, characterized in that, The method further includes: In response to deployment instructions from the iBRAS backend, the feature library containing priority configurations is loaded into the APA board.

6. The method according to claim 3, characterized in that, The method further includes: Based on the update instructions from the iBRAS backend, perform the corresponding update operation on the priority configuration.

7. The method according to claim 1, characterized in that, The process of transmitting user flow logs to the iBRAS backend according to priority, so that the iBRAS backend can perform QoE analysis on the user flow logs and obtain the QoE analysis results, includes: User flow logs are transmitted to the iBRAS backend in order of priority. The iBRAS backend determines the analysis priority of the user flow logs based on the application identifier or URL information in the logs, performs QoE analysis on the logs according to the priority, and obtains the QoE analysis results.

8. A method for processing user flow logs, characterized in that, The method is applied to the iBRAS backend, and the method includes: Receive user flow logs transmitted by the iBRAS front end in priority order. The user flow logs include application identifiers and / or URL information. The priority is obtained by the iBRAS front end matching the user flow logs based on the application identifiers or URL information in the user flow logs. Perform QoE analysis on user flow logs to obtain QoE analysis results.

9. The method according to claim 8, characterized in that, The method specifically performs QoE analysis on user flow logs in the following ways: For each received user stream log, the corresponding priority is matched according to the application identifier or URL information in the user stream log to obtain the analysis priority of each user stream log. Perform QoE analysis on user flow logs according to the analysis priority order.

10. The method according to claim 9, characterized in that, The analysis priority includes high priority, medium priority, and low priority. The method specifically performs QoE analysis on user flow logs in the following ways: A real-time parsing mode is used to perform QoE analysis on high-priority user flow logs; A batch parsing mode is used to perform QoE analysis on medium-priority and low-priority user flow logs.

11. An iBRAS front-end, characterized in that, The iBRAS foreground is used to perform the method as described in any one of claims 1-7.

12. An iBRAS backend, characterized in that, The iBRAS backend is used to perform the method as described in any one of claims 8-10.

13. An iBRAS service awareness system, characterized in that, The iBRAS service awareness system includes the iBRAS front-end as described in claim 11, and also includes the iBRAS back-end as described in claim 12.

14. An electronic device, characterized in that, include: A memory, one or more processors; the memory is coupled to the processors; wherein the memory stores computer program code, the computer program code including computer instructions, and when the computer instructions are executed by the processor, the electronic device performs the method as described in any one of claims 1-10.

15. A computer-readable storage medium comprising computer instructions, characterized in that, When the computer instructions are executed on the electronic device, the electronic device causes the electronic device to perform the method as described in any one of claims 1-10.

16. A computer program product, characterized in that, When the computer program product is run on a computer, it causes the computer to perform the method as described in any one of claims 1-10.

Images