User offloading methods, devices, equipment, media, and program products

Abstract

This application provides a user traffic offloading method, apparatus, device, medium, and program product, relating to the field of network technology, for improving the efficiency of user traffic offloading. The specific technical solution is as follows: acquiring the cumulative traffic data of each user under a first PON port; calculating the traffic share of each user based on the cumulative traffic data; determining the users under the first PON port who need traffic offloading based on the traffic share of each user; determining at least one candidate PON port from the PON port list for the users who need traffic offloading under the first PON port based on the network topology information of the first PON port; determining the target PON port from the at least one candidate PON port based on the load information of each candidate PON port, and assigning the users who need traffic offloading under the first PON port to the target PON port. This application is applied to user traffic offloading scenarios.

Description

Technical Field

[0001] This application relates to the field of network technology, and in particular to a user traffic offloading method, apparatus, device, medium, and program product. Background Technology

[0002] With the rapid development of communication technology, Passive Optical Networks (PON) have been widely used in the broadband access field due to their advantages such as high bandwidth, low cost, and easy maintenance. The user base continues to expand, and the requirements for network service quality are also increasing.

[0003] In the daily operation and maintenance of PON, when a PON port experiences continuous high load leading to network congestion, in order to ensure service quality, existing technologies usually make traffic distribution decisions based on the user acceptance rate (i.e., contracted bandwidth), prioritizing the migration of "high bandwidth package users" to other idle PON ports.

[0004] However, allocating traffic based on contracted bandwidth may mistakenly select high-bandwidth, low-traffic users while overlooking truly high-traffic users, rendering congestion relief ineffective after traffic offloading. This results in low efficiency for user traffic offloading. Summary of the Invention

[0005] This application provides a user traffic splitting method, apparatus, device, medium, and program product for improving the efficiency of user traffic splitting.

[0006] In a first aspect, embodiments of this application provide a user traffic offloading method, the method comprising: acquiring cumulative traffic data of each user under a first PON port; calculating the traffic percentage of each user based on the cumulative traffic data; determining the users who need to be offloaded under the first PON port based on the traffic percentage of each user; determining at least one candidate PON port for the users who need to be offloaded under the first PON port from a list of PON ports based on the network topology information of the first PON port; determining a target PON port from the at least one candidate PON port based on the load information of each candidate PON port, and assigning the users who need to be offloaded under the first PON port to the target PON port.

[0007] The technical solution provided in this application offers at least the following advantages: Since the traffic share of each user can be calculated based on the cumulative traffic data of each user under the first PON port, and then the users requiring traffic offloading under the first PON port are determined based on their traffic share, and then at least one candidate PON port is identified for the users requiring traffic offloading based on the network topology information of the first PON port, the target PON port is further determined from the at least one candidate PON port by combining the load information of each candidate PON port, and the users requiring traffic offloading under the first PON port are assigned to the target PON port. In other words, the actual traffic data generated by the user is used as the direct basis for selecting users for traffic offloading, and the final target PON port for traffic offloading is determined based on the load information of the candidate PON ports. Therefore, the problem of ineffective congestion relief after traffic offloading is avoided, and traffic offloading efficiency is improved.

[0008] One possible implementation is that the network topology information mentioned above includes at least one of the following: the optical distribution network (ODN) to which the first PON port belongs; the optical line terminal (OLT) of the first PON port; and the splitter group to which the first PON port is located.

[0009] Another possible implementation method, based on the cumulative traffic data, calculates the traffic share of each user, including: adding the cumulative traffic data of each user to calculate the total traffic of the first PON port; and using the ratio of the cumulative traffic data of each user to the total traffic of the first PON port as the traffic share of each user.

[0010] Another possible implementation, based on the traffic share of each user, determines the users who need to be traffic-splittered under the first PON port, including: when the traffic share of each user under the first PON port is less than the first threshold, sorting each user according to their traffic share; identifying users whose sorting number under the first PON port is less than the first threshold as users who need to be traffic-splittered under the first PON port; or, identifying at least one first user under the first PON port as a user who needs to be traffic-splittered under the first PON port, wherein the sorting number of at least one first user is less than the sorting number of other users under the first PON port, and the total traffic share of at least one first user is greater than or equal to the second threshold.

[0011] Another possible implementation involves determining at least one candidate PON port for users requiring traffic splitting under the first PON port from the PON port list based on the network topology information of the first PON port. This includes: determining M PON ports from the PON port list based on the network topology information of the first PON port; and selecting the PON ports other than the first PON port from the M PON ports as at least one candidate PON port. The M PON ports include any of the following: PON ports associated with the first ODN to which the first PON port belongs; PON ports in the first optical splitter group under the first OLT, where the first OLT is the OLT of the first PON port and the first optical splitter group is the optical splitter group to which the first PON port is located; and all PON ports under the first OLT.

[0012] Another possible implementation is that the load information mentioned above includes the current real-time load of each candidate PON port; the determination of the target PON port from at least one candidate PON port based on the load information of each candidate PON port includes: subtracting the total bandwidth capacity of each candidate PON port from the current real-time load to calculate the remaining available capacity of each candidate PON port; multiplying the remaining available capacity of each candidate PON port by a security factor to calculate the secure reception capacity of each candidate PON port; and selecting the candidate PON port whose secure reception capacity is greater than or equal to a first traffic percentage as the target PON port, where the first traffic percentage is the traffic percentage of users that need to be diverted under the first PON port.

[0013] Another possible implementation involves the following: the load information includes the expected load of each candidate PON port, calculated based on the traffic share of users requiring offloading under the first PON port; determining the target PON port from at least one candidate PON port based on the load information of each candidate PON port includes selecting the candidate PON port with the lowest expected load from the at least one candidate PON port as the target PON port.

[0014] Secondly, embodiments of this application provide a user traffic splitting device, which includes: an acquisition module, a processing module, and a determination module. The acquisition module is used to acquire the cumulative traffic data of each user under a first PON port. The processing module is used to calculate the traffic share of each user based on the cumulative traffic data. The determination module is used to determine the users under the first PON port who need traffic splitting based on the traffic share of each user; determine at least one candidate PON port for the users who need traffic splitting under the first PON port from a list of PON ports based on the network topology information of the first PON port; and determine a target PON port from the at least one candidate PON port based on the load information of each candidate PON port. The processing module is further used to assign the users under the first PON port who need traffic splitting to the target PON port determined by the determination module.

[0015] One possible implementation is that the network topology information mentioned above includes at least one of the following: the ODN to which the first PON port belongs; the optical line terminal (OLT) of the first PON port; and the splitter group to which the first PON port is located.

[0016] Another possible implementation is that the aforementioned processing module is specifically used to add up the cumulative traffic data of each user to calculate the total traffic of the first PON port; and to use the ratio of the cumulative traffic data of each user to the total traffic of the first PON port as the traffic percentage of each user.

[0017] Another possible implementation is that the aforementioned determining module is specifically used to sort each user according to their traffic share when the traffic share of each user under the first PON port is less than the first threshold; users whose sorting number under the first PON port is less than the first threshold are identified as users who need to be traffic-splittered under the first PON port; or, at least one first user under the first PON port is identified as a user who needs to be traffic-splittered under the first PON port, wherein the sorting number of at least one first user is less than the sorting number of other users under the first PON port, and the total traffic share of at least one first user is greater than or equal to the second threshold.

[0018] Another possible implementation is that the aforementioned determining module is specifically used to determine M PON ports from the PON port list based on the network topology information of the first PON port; and to take the PON ports other than the first PON port among the M PON ports as at least one candidate PON port; wherein the M PON ports include any of the following: PON ports associated with the first ODN to which the first PON port belongs; PON ports in the first optical splitter group under the first OLT, where the first OLT is the OLT of the first PON port and the first optical splitter group is the optical splitter group to which the first PON port is located; and all PON ports under the first OLT.

[0019] Another possible implementation is that the load information mentioned above includes the current real-time load of each candidate PON port; the determination module is specifically used to subtract the total bandwidth capacity of each candidate PON port from the current real-time load to calculate the remaining available capacity of each candidate PON port; multiply the remaining available capacity of each candidate PON port by a security factor to calculate the secure reception capacity of each candidate PON port; and select at least one candidate PON port whose secure reception capacity is greater than or equal to a first traffic percentage as the target PON port, where the first traffic percentage is the traffic percentage of users that need to be diverted under the first PON port.

[0020] Another possible implementation involves the load information including the expected load of each candidate PON port, calculated based on the traffic share of users requiring offloading under the first PON port. Specifically, the determining module is used to select the candidate PON port with the lowest expected load from at least one candidate PON port as the target PON port.

[0021] Thirdly, this application provides an electronic device comprising: a processor and a memory; the memory stores a program or instructions executable on the processor, wherein the program or instructions, when executed by the processor, implement the method of the first aspect described above.

[0022] Fourthly, this application provides a readable storage medium on which a program or instructions are stored, which, when executed by a computer, implement the method of the first aspect described above.

[0023] Fifthly, this application provides a computer program product stored in a storage medium, which, when executed by a computer, implements the method described in the first aspect.

[0024] In a sixth aspect, embodiments of this application provide a chip including a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run programs or instructions to implement the method described in the first aspect.

[0025] The beneficial effects of the second to sixth aspects mentioned above are described in the corresponding description of the first aspect and will not be repeated here. Attached Figure Description

[0026] Figure 1 A schematic diagram of the network architecture for a user traffic splitting method provided in an embodiment of this application;

[0027] Figure 2 A flowchart illustrating a user traffic splitting method provided in an embodiment of this application;

[0028] Figure 3 A flowchart illustrating another user traffic splitting method provided in an embodiment of this application;

[0029] Figure 4 A flowchart illustrating yet another user traffic splitting method provided in an embodiment of this application;

[0030] Figure 5 A flowchart illustrating yet another user traffic splitting method provided in an embodiment of this application;

[0031] Figure 6 A flowchart illustrating yet another user traffic splitting method provided in an embodiment of this application;

[0032] Figure 7 A flowchart illustrating yet another user traffic splitting method provided in an embodiment of this application;

[0033] Figure 8 A flowchart illustrating the implementation process of a user traffic splitting method provided in this application embodiment;

[0034] Figure 9 This application provides a schematic diagram of a user traffic splitting scheme generation interface.

[0035] Figure 10 This is a schematic diagram of the structure of a user diversion device provided in an embodiment of this application;

[0036] Figure 11 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Detailed Implementation

[0037] The technical solutions of the embodiments of this application will be clearly described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of this application. All other embodiments obtained by those skilled in the art based on the embodiments of this application are within the scope of protection of this application.

[0038] The terms "first," "second," etc., used in the specification and claims of this application are used to distinguish similar objects and not to describe a specific order or sequence. It should be understood that such use of data can be interchanged where appropriate so that embodiments of this application can be implemented in orders other than those illustrated or described herein, and the objects distinguished by "first," "second," etc., are generally of the same class and the number of objects is not limited; for example, a first object can be one or more. Furthermore, in the specification and claims, "and / or" indicates at least one of the connected objects, and the character " / " generally indicates that the preceding and following objects are in an "or" relationship.

[0039] The terms "at least one," "at least one of," etc., used in the specification and claims of this application refer to any one, any two, or a combination of two or more of the included items. For example, at least one of a, b, and c can mean: "a," "b," "c," "a and b," "a and c," "b and c," and "a, b, and c," where a, b, and c can be single or multiple. Similarly, "at least two" refers to two or more items, and its meaning is similar to that of "at least one."

[0040] In the description of this application, unless otherwise stated, "a plurality of" means two or more.

[0041] The user traffic splitting method, apparatus, device, medium, and program product provided in this application embodiment can be applied to user traffic splitting scenarios.

[0042] In existing technologies, during the routine operation and maintenance of PON, when a PON port experiences sustained high load leading to network congestion, operators need to migrate (distribute) some users to other idle PON ports to ensure service quality. Traditional traffic distribution strategies typically make decisions based on the user's subscription rate (i.e., contracted bandwidth), prioritizing "high-bandwidth package users." However, this strategy has a significant drawback: a user's contracted bandwidth only represents their maximum potential available bandwidth and does not equate to actual network resource consumption. A user with gigabit broadband but only uses it for web browsing may generate far less traffic than a user with 100 Mbps broadband but continuously streams high-definition video or downloads large files. Therefore, traffic distribution based on "subscription rate" often fails to accurately identify the true "high-traffic consumers," resulting in low distribution efficiency, unresolved congestion issues, and potentially even harming high-value, low-occupancy users.

[0043] Specifically, in the prior art, those skilled in the art generally believe that "high-bandwidth package users" are the main cause of network congestion, and therefore, a traffic offloading strategy based on contracted bandwidth has been adopted for a long time. However, this application, through extensive data statistical analysis, found that there is no strong correlation between a user's actual traffic consumption and their contracted bandwidth. Specifically, through sampling analysis of 100 high-load PON ports of a certain operator, on average, only 3 out of the top 10 users offloaded according to contracted bandwidth actually entered the top 10 in traffic consumption; while on average, 8 out of the top 10 users offloaded according to actual traffic consumption were truly high-traffic users. This finding breaks the long-standing technical bias in the field—that "high-bandwidth package users equal high-traffic users."

[0044] Furthermore, existing solutions only address the question of "who to offload traffic to," failing to resolve the issues of "where to offload to" and "how much to offload." In engineering practice, the PON ports a user can migrate to are not arbitrarily chosen but are subject to strict physical constraints imposed by the ODN topology. Users can only migrate to other PON ports that share the same ODN backbone fiber as their current PON port. Existing solutions lack the ability to automatically identify and match this physical constraint.

[0045] The shortcomings of existing technologies include: 1. Disconnection between traffic offloading target selection and the actual causes of congestion: Traffic offloading based on "acceptance rate" incorrectly equates the potential maximum bandwidth with actual consumption, leading to the misselection of high-bandwidth, low-volume users while truly high-volume users are not selected, rendering congestion relief ineffective after offloading. 2. Lack of quantitative assessment of users' actual traffic contribution: Without historical traffic statistics and analysis, maintenance personnel cannot know the specific contribution ratio of each user to the total load of the PON port, making decision-making a "blind" operation. 3. Lack of automatic identification of optical path physical constraints: Existing solutions do not consider ODN topology constraints, resulting in recommended offloading target PON ports being unreachable in the actual optical path, making the offloading solution unenforceable. 4. Lack of a user-to-target PON port matching algorithm: Only a list of users to be offloaded is output, failing to address the issues of "which specific PON port each user should be migrated to" and "whether the target PON port will be overloaded after migration." In summary, this leads to low efficiency in user offloading.

[0046] To address the aforementioned technical problems, this application provides a user traffic offloading method, apparatus, device, medium, and program product. In this solution, the traffic share of each user under the first PON port can be calculated based on the cumulative traffic data of each user. Then, based on the traffic share of each user, the users requiring traffic offloading under the first PON port are determined. Next, based on the network topology information of the first PON port, at least one candidate PON port is determined for the users requiring traffic offloading. Finally, by combining the load information of each candidate PON port, a target PON port is determined from the at least one candidate PON port, and the users requiring traffic offloading under the first PON port are assigned to the target PON port. In other words, the actual traffic data generated by the user is used as the direct basis for selecting users requiring traffic offloading, and the final target PON port for traffic offloading is determined based on the load information of the candidate PON ports. Therefore, the problem of ineffective congestion relief after traffic offloading is avoided, and traffic offloading efficiency is improved.

[0047] The user offloading method, apparatus, device, medium, and program products provided in the embodiments of this application will be described in detail below with reference to the accompanying drawings.

[0048] Figure 1 This illustration shows a network architecture for a user traffic splitting method provided in an embodiment of this application. For example... Figure 1 As shown, the network architecture includes a user traffic splitting device 101 and a terminal device 102. The user traffic splitting device 101 and the terminal device 102 are interconnected.

[0049] In some embodiments, the user traffic splitting device 101 may be a server, a computer, or a processor or processing unit within a server or computer. The server may be a single server or a server cluster consisting of multiple servers. It should be noted that the embodiments of this application do not limit the specific device form of the user traffic splitting device 101. Figure 1 The example shown is a user distribution device 101, which is a single server.

[0050] In some embodiments, the terminal device may be a mobile phone, tablet computer, laptop computer, handheld computer, in-vehicle electronic device, mobile internet device (MID), augmented reality (AR) / virtual reality (VR) device, robot, wearable device, personal computer (PC), ultra-mobile personal computer (UMPC), netbook, or personal digital assistant (PDA), etc., and the embodiments of this application do not specifically limit it. Figure 1 The example shown is a mobile phone, with terminal device 102 as an example.

[0051] In some embodiments, each terminal device 102 under the first PON port (i.e., each user under the first PON port) sends cumulative traffic data to the user splitting device 101. The user splitting device 101 can receive the cumulative traffic data of each terminal device 102 under the first PON port and calculate the traffic percentage of each terminal device 102 based on the cumulative traffic data.

[0052] It should be noted that the network architecture described in the embodiments of this application is for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and does not constitute a limitation on the technical solutions provided in the embodiments of this application. As network architectures evolve, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.

[0053] See Figure 2 This is a flowchart illustrating a user traffic splitting method provided in an embodiment of this application. Figure 2 As shown, the user diversion method provided in this application embodiment can be implemented by the above-mentioned user diversion device, specifically including the following steps 201 to 205.

[0054] Step 201: The user distribution device acquires the cumulative traffic data of each user under the first PON port.

[0055] In some embodiments, the first PON port is any PON port in the PON list.

[0056] In some embodiments, the above PON list can be a PON list input from the front end.

[0057] For example, the user distribution device can provide a World Wide Web (Web) interactive interface, where maintenance personnel can enter or paste a list of PON ports to be analyzed in batches in the text boxes of the interface. Then, the front end can encapsulate the PON port list entered by the maintenance personnel and submit it to the back end service.

[0058] For example, each row of the above PON port list contains one PON port, in the format of "OLT Internet Protocol (IP) address" followed by "Tab key" followed by "PON port number".

[0059] For example: 10.1.1.100 (Tab) PON-1; 10.1.1.100 (Tab) PON-2; 10.1.2.200 (Tab) PON-1.

[0060] In some embodiments, for each user under the first PON port, the user traffic splitting device can query the monthly traffic summary table based on the user identifier of each user to obtain the cumulative traffic data of each user.

[0061] In some embodiments, the user splitting device can query the line resource database to obtain the user identifier list corresponding to the first PON port, which includes the user identifiers of all users under the first PON port.

[0062] In some embodiments, the user diversion device can query a monthly traffic summary table to calculate the cumulative traffic data of each user within a preset historical period (e.g., 3 months).

[0063] For example, when the user traffic distribution device queries the monthly traffic summary table to calculate the cumulative traffic data for each user, it can use the most recent three calendar months as the statistical period. Using a three-month period can smooth out the impact of sudden traffic spikes in a single month and better reflect the user's long-term behavior patterns. For new users, if the user has at least one month of historical traffic data, the actual monthly average traffic data is converted to an equivalent value for three months. When a user has no historical traffic data (e.g., a new account opened in the current month), the average traffic data of other similar users under the user's subscription plan is queried as an estimate. If the estimate still cannot be obtained, the user is marked as "insufficient data, not to be distributed temporarily" and is not included in the automatic traffic distribution candidate list, requiring manual processing.

[0064] In some embodiments, for users with "insufficient data" as described above, the "recommendation priority" column for such users will display "insufficient data" in the final output statistics, and the user triage device will not automatically list them as triage targets.

[0065] In some embodiments, the user traffic splitting device can automatically collect all original detailed billing records of all users accessing the network on the previous day from the operator's 3A (Authentication, Billing, Auditing) system during the daily off-peak business period (e.g., 2:00 AM). Then, based on the original detailed billing records, the user traffic splitting device can perform cumulative calculations on the user's daily incremental data using "user account" and "year and month" (e.g., 202405) as the combination key to obtain the user's monthly traffic summary result. The user traffic splitting device can then write the monthly traffic summary result into the monthly traffic summary table.

[0066] Specifically, the user traffic splitting device can add up the downlink data volume of the same user for each day in the same month to obtain the user's total downlink traffic for that month; similarly, after obtaining the total uplink traffic, it can also count the number of times the user dials in that month (counted by different dates) to obtain the user's monthly traffic summary result.

[0067] For example, the original detailed record may include: user account, session start time, uplink data volume (bytes), downlink data volume (bytes), etc.

[0068] For example, the structure of the above monthly traffic summary table can include the following fields: user account, statistical month (format YYYYMM), total downlink traffic (GB), total uplink traffic (GB), number of dial-ups, and last update time. This monthly traffic summary table uses "user account" and "statistical month" as a composite primary key.

[0069] For example, the amount of data in the monthly traffic summary table is significantly reduced compared to the amount of data in the original detailed record, which is the key to achieving subsequent second-level query response.

[0070] Step 202: The user traffic distribution device calculates the traffic share of each user based on the cumulative traffic data.

[0071] In some embodiments, the cumulative traffic data of the aforementioned user may include at least one of the following: total downlink traffic and total uplink traffic.

[0072] Thus, since the user traffic percentage is calculated based on the user's actual cumulative traffic data and the actual total traffic of the first PON port, the accuracy of the user's actual traffic percentage is improved.

[0073] In some embodiments, combined with Figure 2 ,like Figure 3As shown, step 202 above can be implemented through steps 202a and 202b.

[0074] Step 202a: The user traffic splitting device adds up the cumulative traffic data of each user to calculate the total traffic of the first PON port.

[0075] Step 202b: The user traffic splitting device uses the ratio of each user's cumulative traffic data to the total traffic of the first PON port as the traffic percentage for each user.

[0076] For example, for each user, the user traffic splitting device can divide its cumulative traffic data by the total traffic of the first PON port, and then multiply by 100% to obtain the traffic percentage of each user.

[0077] Thus, since the traffic share of each user can be determined based on the actual cumulative traffic data of each user, the users who need to be traffic-splitting under the first PON port can be identified, thereby improving the accuracy of identifying the users who need to be traffic-splitting under the PON port.

[0078] Step 203: The user traffic splitting device determines the users that need to be split under the first PON port based on the traffic ratio of each user.

[0079] In some embodiments, combined with Figure 2 ,like Figure 4 As shown, step 203 can be implemented through steps 203a and 203b, or through steps 203a and 203c.

[0080] Step 203a: When the traffic share of each user under the first PON port is less than the first threshold, the user traffic splitting device sorts each user according to the traffic share of each user.

[0081] In some embodiments, the first threshold can be a high traffic percentage threshold preset by the user traffic splitting device (e.g., the default value of the threshold can be 40%, which can be dynamically adjusted through the web interface).

[0082] It is understandable that the user traffic splitting device can iterate through the traffic share of each user under the first PON port, check whether there is a user whose traffic share exceeds the first threshold. If there is no super user under the first PON port whose traffic share exceeds the first threshold, the users under the first PON port are sorted in descending order of traffic share to form the "traffic contribution ranking list" of the first PON port, so as to determine the users under the first PON port who need to be split.

[0083] Step 203b: The user distribution device determines the users whose serial numbers under the first PON port are less than the first threshold as the users who need to be distributed under the first PON port.

[0084] In some embodiments, the higher a user's traffic share, the lower the user's ranking number.

[0085] It is understandable that the user traffic splitting device identifies the top-ranked users (e.g., the top 5 users) as suggested traffic splitting targets, i.e., the users that need to be split under the first PON port, according to the traffic share of each user under the first PON port from high to low.

[0086] Step 203c: The user splitting device determines at least one first user under the first PON port as the user that needs to be split under the first PON port.

[0087] In some embodiments, the sequence number of at least one first user is less than the sequence number of other users under the first PON port, and the total traffic share of at least one first user is greater than or equal to the second threshold.

[0088] Specifically, maintenance personnel can input the target value of the traffic to be released (e.g., 1000GB) through the web interface, which is the second threshold mentioned above. The user traffic splitting device can sort the users and start from the users with the highest traffic share, and then accumulate the traffic share of each user in turn until the accumulated value reaches or exceeds the process target value. The users that are accumulated are the suggested traffic splitting targets, that is, the users that need to be split under the first PON port.

[0089] In some embodiments, if the maintenance personnel do not input a target value, the user traffic splitting device may default to recommending the top 3 users with the highest percentage as the users who need to be split under the first PON port.

[0090] In this way, since users under the first PON port can be sorted by the traffic share of each user under the first PON port, and then the users that need to be diverted under the first PON port can be determined based on the sorting results, the accurate positioning of diverted users is achieved, thus improving the efficiency of user diversion.

[0091] In some embodiments, if a user's traffic share under the first PON port is greater than or equal to a first threshold, the user traffic splitting device can mark that user as a super user and generate an early warning message.

[0092] In some embodiments, the aforementioned warning information may include at least one of the following: user account, current percentage value, and suggested handling method.

[0093] For example, the suggested solutions mentioned above could be separate capacity expansion or business negotiation.

[0094] Understandably, since a particular user's traffic share is greater than or equal to the first threshold, that user will not be included in the regular traffic diversion suggestion list. The process ends or awaits manual intervention.

[0095] It is understood that this application determines users who need to be routed in the following order: A (process proportion sorting) → B (first threshold judgment) → C (generating user route list). If the order A→C→B (sorting first, generating list first, then judgment) is used: then super users have already been included in the route list, the warning is meaningless, and they may have already been routed, causing secondary congestion. 2. If the order B→A→C (first threshold judgment, then sorting, then generating list) is used: then there is no sorting result when judging the first threshold, and it is impossible to determine which user exceeds the first threshold.

[0096] Step 204: Based on the network topology information of the first PON port, the user traffic splitting device determines at least one candidate PON port from the PON port list for users who need to be split under the first PON port.

[0097] In some embodiments, the network topology information described above includes at least one of the following:

[0098] The ODN to which the first PON port belongs;

[0099] OLT of the first PON port;

[0100] The first PON port is located in the optical splitter group.

[0101] Specifically, for each user who needs to be traffic-splitting under the first PON port, the user traffic splitting device can determine at least one candidate PON port for each user who needs to be traffic-splitting from the PON port list based on the network topology information of the first PON port, and then determine a target PON port from the at least one candidate PON port corresponding to each user who needs to be traffic-splitting.

[0102] In some embodiments, combined with Figure 2 ,like Figure 5 As shown, step 204 above can be implemented through steps 204a and 204b.

[0103] Step 204a: The user distribution device determines M PON ports from the PON port list based on the network topology information of the first PON port.

[0104] In some embodiments, the above M PON ports include any one of the following A1 to A3:

[0105] A1. The PON port associated with the first ODN to which the first PON port belongs;

[0106] In some embodiments, the user routing device can determine the first ODN to which the user to be routed belongs based on the user account of the user to be routed, and then obtain the PON port associated with the first ODN.

[0107] For example, the PON ports associated with the first ODN can be all PON ports marked as "can be used as backup" under the first ODN.

[0108] In some embodiments, the first ODN to which the user requiring traffic splitting under the first PON port belongs is the first ODN to which the first PON port belongs.

[0109] In some embodiments, the user traffic splitting device can query a first association table (“User and ODN Association Table”) based on the user account of the user who needs to be split, obtain the ODN identifier associated with the user who needs to be split, and then query a second association table (“PON Port and ODN Association Table”) based on the ODN identifier to obtain a list of all PON ports marked “can be used as backup” under the first ODN indicated by the ODN identifier. The PON port list includes the aforementioned M PON ports.

[0110] In some embodiments, the first association table records the PON port and ODN to which each user requiring traffic splitting is currently located.

[0111] In some embodiments, the second association table records the ODN to which each PON port belongs, and whether the PON port can be used as a backup target.

[0112] A2. The PON port in the first splitter group under the first OLT, where the first OLT is the OLT of the first PON port and the first splitter group is the splitter group where the first PON port is located.

[0113] In some embodiments, when the network topology information is incomplete and only the relationship between the OLT and the splitter is known, the user splitter can filter other PON ports under the first OLT that are in the same splitter group as the first PON port, and use them as the aforementioned M PON ports.

[0114] A3. All PON ports under the first OLT.

[0115] In some embodiments, when only OLT information is known, the user distribution device can filter all other PON ports under the first OLT as the aforementioned M PON ports.

[0116] In some embodiments, the network topology information described above can be understood as ODN topology information.

[0117] In some embodiments, when the ODN topology information is complete, the user splitter can use the above-described method A1 to determine the M PON ports; when the ODN topology information is incomplete, and only the relationship between the first OLT and the splitter is known, the user splitter can use the above-described method A2 to determine the M PON ports; when only the information of the first OLT is known, the user splitter can use the above-described method A3 to determine the M PON ports.

[0118] In some embodiments, in the absence of any network topology information, the user routing device can return an empty list, prompting maintenance personnel to manually enter the topology or manually select it.

[0119] In a PON network, the optical path for a user is as follows: the user's Optical Network Unit (ONU) connects to a splitter, which in turn connects to the PON port of the OLT via a backbone fiber. The user can only migrate to another PON port that shares the same ODN (Optical Distribution Network) backbone fiber with their current PON port. In other words, whether two PON ports can serve as backups for each other depends on whether they are connected to the same splitter or the same backbone fiber.

[0120] Step 204b: The user distribution device selects at least one PON port from the M PON ports, excluding the first PON port.

[0121] In some embodiments, the user offloading device excludes the PON port where the user is currently located from the above M PON ports to obtain a candidate PON port list, which includes at least one candidate PON port.

[0122] Thus, since the candidate PON ports are determined for users who need to be offloaded based on the actual network topology information of the first PON port, and the target PON port is further determined from the candidate PON ports, the target PON port for offloading is reachable in the actual optical path, thereby improving the efficiency of offloading.

[0123] Step 205: Based on the load information of each candidate PON port, the user traffic splitting device determines the target PON port from at least one candidate PON port and assigns the users who need to be split under the first PON port to the target PON port.

[0124] In some embodiments, the user load distribution device can obtain the load information of each candidate PON port from the network management performance library.

[0125] In some embodiments, the user load distribution device can sort the candidate PON ports from low to high according to the load information of each candidate PON port, and then select the PON port with the lowest load as the target PON.

[0126] In some embodiments, combined with Figure 2 ,like Figure 6 As shown, the load information mentioned above includes the current real-time load of each candidate PON port; step 205 can be implemented in detail through steps 205a to 205c.

[0127] Step 205a: The user traffic splitting device subtracts the total bandwidth capacity of each candidate PON port from the current real-time load to calculate the remaining available capacity of each candidate PON port.

[0128] In some embodiments, the user traffic splitting device can obtain the total bandwidth capacity (e.g., 2.5Gbps) and current real-time load (real-time value or average value over the last 15 minutes) of each candidate PON port from the network management performance library.

[0129] It is understandable that when there are multiple users who need to be traffic split, for each user, the user splitting device can subtract the total bandwidth capacity of at least one candidate PON port corresponding to the user from the current real-time load to calculate the remaining available capacity of each candidate PON port. Then, the remaining available capacity of each candidate PON port is multiplied by the security factor to calculate the secure receiving capacity of each candidate PON port. Then, the user splitting device can select the candidate PON port whose secure receiving capacity is greater than or equal to the traffic proportion of the user who needs to be split (i.e., the first traffic proportion) as the target PON port for that user.

[0130] Step 205b: The user distribution device multiplies the remaining available capacity of each candidate PON port by the security factor to calculate the secure reception capacity of each candidate PON port.

[0131] For example, the default value of the above security factor can be 0.8, which means reserving a buffer of 20%.

[0132] Step 205c: The user traffic splitting device selects at least one candidate PON port whose secure receiving capacity is greater than or equal to the first traffic percentage as the target PON port.

[0133] In some embodiments, the first traffic percentage is the traffic percentage of users who need to be offloaded under the first PON port.

[0134] It is understandable that when there are multiple users who need to be traffic split, for each user who needs to be traffic split, the user traffic splitting device can compare the secure receiving capacity of at least one candidate PON port corresponding to the user with the current user's traffic ratio, and then take the candidate PON port whose secure receiving capacity is greater than or equal to the current user's traffic ratio as the target PON port.

[0135] In some embodiments, the user offloading device may use a greedy matching algorithm to sequentially select the target PON ports for users that need to be offloaded under the first PON port.

[0136] Specifically, the user traffic splitting device can sort all users to be split under the first PON port according to their traffic proportion from largest to smallest, and then determine the target PON port for each user in turn according to the sorting results.

[0137] In some embodiments, when there are multiple candidate PON ports with a secure receiving capacity greater than or equal to a first traffic percentage, the user traffic splitting device may use the candidate PON port with the largest secure receiving capacity or the candidate PON port with the lowest load among the multiple candidate PON ports as the target PON port.

[0138] In some embodiments, after assigning users who need to be offloaded under the first PON port to the target PON port, the user offloading device can update the remaining capacity of the target PON port.

[0139] In some embodiments, if there is no candidate PON port with a secure receive capacity greater than or equal to the first traffic percentage among at least one candidate PON port, the user traffic offloading device can mark the user as "temporarily unable to be automatically offloaded" and enter the manual processing queue for a user who needs to be offloaded.

[0140] In this way, since the target PON port can be selected based on the secure receive capacity of at least one candidate PON port, the problem of network congestion after user traffic is diverted is avoided.

[0141] In some embodiments, combined with Figure 2 ,like Figure 7 As shown, the above load information includes the expected load of each candidate PON port. The expected load of each candidate PON port is calculated based on the traffic ratio of users who need to be diverted under the first PON port. The above step 205 can be implemented in detail through the following step 205d.

[0142] Step 205d: The user distribution device selects the candidate PON port with the lowest expected load from at least one candidate PON port as the target PON port.

[0143] In some embodiments, when there are multiple users who need to be traffic-splitting, for any user who needs to be traffic-splitting, the user traffic-splitting device can calculate the expected load of each candidate PON port after allocating the user who needs to be traffic-splitting to at least one corresponding candidate PON port based on the traffic ratio of any user who needs to be traffic-splitting, and then take the candidate PON port with the lowest expected load as the target PON port.

[0144] In some embodiments, the user offloading device may use the method of minimizing the maximum load to select the target PON port for the user who needs to be offloaded under the first PON port.

[0145] Specifically, the user traffic offloading device can initialize the current load of all candidate PON ports. Then, it sorts the users requiring traffic offloading in descending order of their traffic share. For each user requiring offloading, it calculates the expected load rate after assigning them to each candidate PON port, and then selects the PON port with the lowest expected load rate after allocation as the target PON port. This process is repeated until all users have been allocated traffic.

[0146] In this way, since the target PON port can be selected for users who need to be traffic-splitting under the first PON port based on the expected load of each candidate PON port, the final load rate of all target PON ports is made as balanced as possible.

[0147] The user traffic offloading method provided in this application calculates the traffic share of each user based on the cumulative traffic data of each user under the first PON port. Then, based on the traffic share of each user, it identifies the users under the first PON port who need traffic offloading. Next, based on the network topology information of the first PON port, it determines at least one candidate PON port for the users who need traffic offloading. Finally, it combines the load information of each candidate PON port to determine the target PON port from at least one candidate PON port, and assigns the users under the first PON port who need traffic offloading to the target PON port. In other words, it uses the actual traffic data generated by the user as the direct basis for selecting offloading users, and determines the final target PON port for traffic offloading based on the load information of the candidate PON ports. Therefore, it avoids the problem of ineffective congestion relief after traffic offloading and improves traffic offloading efficiency.

[0148] In some embodiments, the user offloading device may also generate an offloading scheme report for each offloaded user, the offloading scheme report may include at least one of the following:

[0149] Source PON port: Identifier of the currently congested PON port;

[0150] Users to be relocated: User accounts recommended for migration;

[0151] Current user traffic: This user's historical average monthly traffic (GB);

[0152] Target PON port: The identifier of the PON port to be migrated to;

[0153] Target PON port load rate before migration: load percentage before migration;

[0154] Load rate of target PON port after migration: the percentage of load after migration (predicted value);

[0155] Will a warning be triggered: Will the migration exceed the safety threshold?

[0156] Optical path reachability: Results based on ODN topology verification (“reachable” or “unreachable”);

[0157] Execution priority: Recommended execution order (high, medium, low).

[0158] In some embodiments, the user distribution device can generate analysis results for all PON ports and return all analysis results to the web frontend. The frontend can then display the analysis results of all PON ports side-by-side on a single interface. This interface supports exporting the analysis results to CSV or Excel files.

[0159] In some embodiments, the analysis results of the PON port may include at least one of the following: user traffic contribution ranking table, super user early warning information, complete traffic offloading scheme (source-to-target mapping), and load prediction results.

[0160] The user traffic splitting method of this application will be described below through specific embodiments.

[0161] This application consists of two major collaborative parts: a data preprocessing subsystem (back-end automation) and a core traffic analysis engine (online interactive), forming a complete decision-making loop from "who to traffic", to "where to traffic", to "how much to traffic".

[0162] The following are detailed embodiments and steps, such as Figure 8 As shown;

[0163] Part 1, Data Preprocessing Subsystem: Runs daily at set times, extracts raw internet access details from the 3A system, aggregates them by user and month, and stores them in the monthly traffic summary table. The steps are shown in P1 to P3 below.

[0164] P1. Timed Source Data Extraction: Every day at 2:00 AM (off-peak business period), the system automatically collects all original detailed transaction records from the operator's 3A (Authentication, Billing, Audit) system for all users accessing the internet on the previous day. Extracted fields include: user account, session start time, uplink data volume (bytes), and downlink data volume (bytes).

[0165] P2. Data Aggregation Processing: The system uses an aggregation calculation module to perform cumulative calculations on daily incremental data, using "user account" and "year / month" (e.g., 202405) as the key. Specifically, it adds up the downlink data volume for each day within the same month for the same user to obtain the user's total downlink traffic for that month; similarly, it obtains the total uplink traffic. It also counts the number of dial-ups made by the user in that month (counted by different dates).

[0166] P3. Aggregation Result Persistence: The system writes the calculation results to a dedicated "Monthly Traffic Summary Table". This table contains the following fields: User Account, Statistical Month (format YYYYMM), Total Downlink Traffic (GB), Total Uplink Traffic (GB), Number of Dial-ups, and Last Update Time. The table uses "User Account" and "Statistical Month" as a composite primary key. This table contains approximately one-thousandth the amount of data in the original detailed traffic record, making it crucial for achieving sub-second query response times.

[0167] Part Two: Core Traffic Splitting Analysis Engine: Responds to operations and maintenance personnel's actions on the Web interface, completes analysis using preprocessed data, and calls the ODN topology database and PON port performance library to generate a complete traffic splitting solution. The steps are shown in C1 to C11 below.

[0168] C1. Receive the list of PON ports to be analyzed: The system provides a web-based interactive interface. Maintenance personnel can input or paste a list of high-load PON ports to be analyzed in batches into the text boxes on the interface. Each line contains one PON port, formatted as "OLT IP address" followed by a "Tab key" and then the "PON port number".

[0169] For example:

[0170] 1. 10.1.1.100 (Tab) PON-1

[0171] 2. 10.1.1.100 (Tab) PON-2

[0172] 3. 10.1.2.200 (Tab) PON-1

[0173] The frontend encapsulates the list of user input and submits it to the backend service;

[0174] C2. Related Query of User and Traffic Data: Based on the received PON port list, the backend service first queries the line resource library to obtain a list of all user identifiers connected to these PON ports.

[0175] Then, based on the user identifier list, query the monthly traffic summary table generated by the preprocessing subsystem to obtain the cumulative traffic data of these users.

[0176] Statistical period and rules for handling insufficient data:

[0177] 1. Statistical Period: This solution uses the most recent three calendar months as the statistical period. For example, if the current month is April 2026, then the data for January, February, and March 2026 will be used. Using a three-month period can smooth out the impact of sudden surges in traffic in a single month and better reflect users' long-term behavioral patterns.

[0178] 2. New User Processing:

[0179] 1) If a user has at least one month of historical data, the actual monthly average traffic will be converted to an equivalent value of three months.

[0180] 2) If a user has no historical data (e.g., a new account opened in the current month), query the average data usage of other users with similar subscription plans under that user's subscription plan as an estimate.

[0181] 3) If the estimated value still cannot be obtained, the user will be marked as "Insufficient data, not to be distributed temporarily" and will not be included in the candidate list for automatic distribution, and will be handled manually.

[0182] 3. Identification of users with insufficient data: In the final output, the "Recommendation Priority" column for such users will display "Insufficient Data," and the system will not automatically list them as referral targets;

[0183] C3. Traffic Share Calculation and Sorting: For each PON port, the system can perform the following calculations through the traffic share calculation and sorting module:

[0184] The first step is to sum the historical total traffic of all users under the PON port to obtain the total traffic of the PON port.

[0185] The second step is to divide each user's total historical traffic by the total traffic of the PON port they are on, and then multiply that by 100% to get the user's "traffic share".

[0186] The third step is to sort the users under each PON port according to their traffic contribution ratio from high to low, forming a "traffic contribution ranking list" for that PON port;

[0187] C4. Super User Judgment: The system presets a high traffic share threshold (default value is 40%, this threshold can be dynamically adjusted via the web interface). The system can use the user identification module to traverse the traffic contribution ranking list of each PON port to check if any user's traffic share exceeds this threshold;

[0188] C5. Super User Warning Handling: If a user's traffic share exceeds the threshold, the user identification module will mark the user as a "super user" and generate a warning message. The warning message includes: user account, current traffic share value, and suggested handling methods (such as individual capacity expansion, business negotiation, etc.). This user will not be included in the regular traffic diversion suggestion list. The process ends or awaits manual intervention.

[0189] C6. Regular Traffic Offloading Recommendation Generation: If there are no super users under a certain PON port, the traffic offloading user identification module will identify the top-ranked users as recommended traffic offloading targets in descending order of traffic share. Maintenance personnel can input the target traffic value to be released (e.g., 1000GB) through the web interface. The traffic offloading user identification module will then increment the value sequentially from the users with the highest traffic share until the accumulated value reaches or exceeds the target value; the users added to this value are the recommended traffic offloading targets. If the maintenance personnel do not input a target value, the system will default to recommending the top 3 users with the highest traffic share, resulting in a final list of users to be offloaded.

[0190] Part Three: Target PON Port Matching and Splitting Scheme Generation (Solving the problems of "where to split the traffic" and "how much to split")

[0191] C7. Candidate PON Port Screening Based on ODN Topology: This is one of the key technical features of this application. In a PON network, the user's optical path is as follows: the ONU device in the user's home connects to the splitter, and the splitter connects to the PON port of the OLT via the backbone fiber. The user can only migrate to another PON port that shares the same ODN backbone fiber with its current PON port. In other words, whether two PON ports can serve as backups for each other depends on whether they are connected to the same splitter or the same backbone fiber.

[0192] Data Foundation – ODN Topology Database:

[0193] To achieve automated filtering, the system needs to pre-create and maintain the following three tables:

[0194] The first table is the "ODN Topology Master Table," which records the unique identifier of each ODN, the backbone fiber identifier, the splitter identifier, and the list of PON ports covered by that ODN.

[0195] The second table is the "PON Port and ODN Association Table", which records the ODN to which each PON port belongs, and whether the PON port can be used as a backup target.

[0196] The third table is the "User and ODN Association Table", which records the PON port where each user is currently located and the ODN to which they belong.

[0197] Filtering algorithm steps:

[0198] The first step is for the system to use the ODN topology query module to query the "User and ODN Association Table" based on the user account and obtain the ODN identifier to which the user belongs.

[0199] The second step is for the system to use the ODN topology query module to query the "PON port and ODN association table" based on the ODN identifier obtained in the first step, and obtain a list of all PON ports marked as "can be used as backup" under this ODN.

[0200] Third, the system can use the ODN topology query module to exclude the user's current PON port from the list and obtain a list of candidate PON ports for each user.

[0201] In some embodiments, the ODN topology query module can obtain the above information by querying the ODN topology database.

[0202] Fourth, the system can obtain the current load rate of each candidate PON port from the network management performance library (PON performance library) through the target PON port load assessment module, sort the candidate PON ports from low to high load rate, and recommend the PON port with the lowest load as the first choice.

[0203] Downgrade strategy:

[0204] When ODN topology data is incomplete, the system adopts the following degradation strategy:

[0205] 1. First level (optimal): The ODN topology data is complete and is accurately filtered according to the above algorithm.

[0206] 2. Second level (suboptimal): If only the relationship between the OLT and the splitter is known, then other PON ports under the same OLT and the same splitter group are selected.

[0207] 3. Third level (fallback): If only OLT information is known, then all other PON ports under the same OLT are filtered.

[0208] 4. Level 4 (Manual): If there is no topology data, an empty list will be returned, prompting the operations and maintenance personnel to manually enter the topology or select it manually.

[0209] C8. Candidate PON Port Load Assessment and Receive Capacity Calculation: For each candidate PON port, the system obtains the following information from the network management performance library: the total bandwidth capacity of the PON port (e.g., 2.5Gbps) and the current load (real-time value or average value over the past 15 minutes).

[0210] The system then calculates: 1. Remaining available capacity = Total bandwidth capacity minus current load; 2. Secure reception capacity = Remaining available capacity multiplied by the security factor (default value is 0.8, i.e., reserving 20% ​​buffer).

[0211] C9. Matching algorithm from user to target PON port: This is a combinatorial optimization problem under multiple constraints. This application provides two optional algorithm implementations:

[0212] Algorithm A: Greedy matching method (practical in engineering, fast calculation speed)

[0213] The system first sorts all users awaiting traffic offloading by traffic volume from highest to lowest. Then, it processes each user sequentially: for the current user, it filters the candidate PON ports to find one with a secure receive capacity greater than the user's traffic volume. If multiple feasible PON ports exist, it selects the one with the largest secure receive capacity (or the one with the lowest load). The user is assigned to the selected PON port, and the remaining capacity of that PON port is updated (minus the user's traffic volume). If no feasible PON ports exist, the user is marked as "not automatically offloading available" and added to the manual processing queue. This process is repeated until all users have been processed.

[0214] Algorithm B: Minimize maximum load method (better, slightly more computationally complex)

[0215] The goal of this algorithm is to distribute all users to target PON ports as evenly as possible, ensuring a balanced final load rate across all target PON ports. Specifically, the system first initializes the current load of all candidate PON ports. Then, it sorts the users to be distributed by traffic volume from highest to lowest. For each user, it calculates the expected load rate after distributing them to each candidate PON port and selects the PON port that minimizes the global maximum load rate after distribution. This process is repeated until all users have been distributed.

[0216] C10. Generate a complete traffic splitting scheme report: The system outputs a complete scheme containing the following information:

[0217] 1. Source PON port: Identifier of the currently congested PON port.

[0218] 2. Users to be migrated: User accounts recommended for migration.

[0219] 3. Current user data usage: This user's historical average monthly data usage (GB)

[0220] 4. Target PON port: The identifier of the PON port to be migrated to.

[0221] 5. Load rate of target PON port before migration: percentage of load before migration

[0222] 6. Load rate after target PON port migration: The percentage of load after migration (predicted value)

[0223] 7. Will an alert be triggered: Will the migration exceed the safety threshold?

[0224] 8. Optical path reachability: Results based on ODN topology verification ("reachable" or "unreachable")

[0225] 9. Execution Priority: Recommended execution order (high, medium, low);

[0226] C11. Result Visualization Output: The system returns all analysis results to the web frontend. The frontend displays the analysis results of all PON ports side-by-side on the same interface, including: a user traffic contribution ranking table, super user warning information, a complete traffic splitting scheme (source-to-target mapping), and load prediction results. The interface supports exporting the results to CSV or Excel files. Figure 9 As shown, the web interface clearly displays the entire process from entering the PON port list to the final load splitting solution. Operations personnel can intuitively see which target PON port each user to be split should be migrated to, as well as the load forecast after migration.

[0227] For example, the overall layout of the web interface can be as shown in Table 1 below:

[0228] Table 1

[0229]

[0230] For example, the traffic splitting scheme can be as shown in Table 2 below:

[0231] Table 2

[0232]

[0233] For example, the interface functions can be described as shown in Table 3 below:

[0234] Table 3

[0235]

[0236] Thus, 1. **Decision-Making Accuracy:** The system shifts from blindly allocating traffic based on "subscribed rate" to precisely targeting traffic based on "actual traffic percentage," significantly improving the efficiency of single-time traffic offloading in alleviating congestion. 2. **Physical Feasibility:** Automatically selecting candidate PON ports based on ODN topology ensures that the offloading solution is physically reachable on the optical path, avoiding the problem of "recommended but unusable" solutions common in traditional methods. 3. **Global Optimization:** Through a matching algorithm under multiple constraints, the system automatically generates the optimal mapping from users to the target PON port, balancing source PON port congestion relief and target PON port load balancing. 4. **Risk Control:** The super-user early warning mechanism effectively identifies and prevents secondary network congestion risks that may arise from simple traffic offloading. 5. **Efficient Operation and Maintenance:** Batch and automated analysis is achieved through a web interface, with highly visualized results, significantly reducing the operational complexity for maintenance personnel.

[0237] It should be noted that the descriptions of each step in this embodiment can be found in the above embodiments, and will not be repeated here.

[0238] In this application, the technical contribution lies in the first-time identification of the long-neglected technical problem of "discrepancy between contracted bandwidth and actual traffic," and the targeted proposal of a solution based on the proportion of actual traffic. This addresses the following issues: 1. The problem of inaccurate traffic allocation decisions based on "acceptance rate" is solved by establishing a traffic allocation target selection mechanism based on users' actual historical traffic data. 2. The problem of the lack of objective quantitative basis for traffic allocation decisions is addressed by providing a method for automatically calculating the proportion of user traffic contribution. 3. The problem of the potential for secondary congestion risks from allocating traffic to "super users" is addressed by designing an automatic identification and early warning mechanism. 4. The problem of traffic allocation schemes being unenforceable due to optical path constraints is addressed by providing an automatic candidate PON port selection method based on ODN topology. This solves the decision-making problems of "where to allocate traffic" and "how much traffic to allocate," providing an optimal matching algorithm for users to target PON ports under multiple constraints.

[0239] In this application embodiment, to ensure the robustness of the solution under various boundary conditions, the following extreme scenario processing logic is defined: Scenario 1 (All candidate PON ports lack sufficient capacity): The system marks all users awaiting traffic offloading as "cannot be automatically offloaded temporarily" and generates an alarm, suggesting that maintenance personnel consider capacity expansion or service optimization. Scenario 2 (Multiple PON ports are congested simultaneously and are candidates for each other): The system uses a minimum maximum load algorithm to disperse and migrate users to multiple target PON ports, avoiding the centralized migration of users from multiple source PON ports to the same target PON port. Scenario 3 (Users appear simultaneously in the offloading lists of multiple source PON ports): The system determines the user's affiliation based on the PON port the user is currently on, avoiding duplicate migration. Scenario 4 (ODN topology data is missing): The system automatically downgrades to L2 / L3 policy and marks "Candidate PON ports are generated based on the downgrade policy, manual review is recommended".

[0240] In this application, the basis for identifying the traffic splitting target is based on the actual historical traffic ratio (dynamic), while the prior art is based on the contracted bandwidth (static). Regarding the target PON port selection method, this application uses automated screening based on ODN topology, while the prior art relies on manual experience or arbitrary selection. For constraint considerations, this application considers optical path topology constraints, capacity constraints, and security thresholds. For the matching algorithm, this application considers greedy matching or a maximum load minimization algorithm. Regarding the completeness of the output scheme, this application is based on the complete mapping of users to the target PON port and load prediction, while the prior art only relies on the user list.

[0241] In this embodiment, the application achieves three major synergistic effects through the integration of a specific execution order and multi-dimensional constraints: Synergistic Effect 1: The involved steps are data preprocessing and online analysis. Individual execution has drawbacks: preprocessing alone cannot dynamically calculate the proportion of traffic on any PON port; online querying of raw data alone will time out. The synergistic effect of this combination is: second-level response plus flexible calculation of the traffic proportion of any PON port. Synergistic Effect 2: The involved steps are proportion sorting plus relative threshold warning. Individual execution has drawbacks: sorting alone may recommend super users, leading to secondary congestion; absolute threshold alarms alone have a high false alarm rate. The synergistic effect of this combination is: accurately locating high-traffic users while avoiding the risk of secondary congestion. Synergistic Effect 3: The involved steps are ODN topology constraints plus load assessment plus matching algorithm. Individual execution has drawbacks: only identifying users does not know which PON port to migrate to; manual matching is inefficient and prone to errors. The synergistic effect of this combination is: automatically generating physically feasible and load-balanced optimal traffic distribution schemes.

[0242] It should be noted that the above-described method embodiments, or the various possible implementations of the method embodiments, can be executed individually, or, provided there is no conflict, they can be combined with each other. The specific implementation can be determined according to actual usage requirements, and this application embodiment does not impose any restrictions on this.

[0243] The feasibility and practical value of the technical solution proposed in this application can be summarized as follows: Technical feasibility: The technology stack adopted (data processing ETL, web front-end and back-end development, database query) are all mature and widely used technologies with no implementation barriers. The "offline preprocessing plus online analysis" architecture adopted by the solution pre-aggregates massive traffic data through scheduled tasks, ensuring second-level response for online queries and perfectly solving the performance bottleneck.

[0244] Data Feasibility: The core data required for implementation includes: line information (user-to-PON port mapping), 3A internet access details (user traffic data), ODN topology data (optical path physical constraints), and PON port performance data (real-time load). All of this data is existing production data from the operator, resulting in low resource acquisition costs. The entire system operates in a closed loop internally, without relying on any external services.

[0245] Actual verification results: Actual operational data shows that the system can accurately locate high-traffic users, automatically filter candidate PON ports based on ODN topology, and generate feasible user-to-target PON port mapping schemes. It has achieved significant and quantifiable improvements in alleviating PON port congestion and optimizing network load, proving its engineering practicality and business value.

[0246] This application embodiment can divide the user diversion device into functional modules according to the above method example. For example, each function can be divided into a separate functional module, or two or more functions can be integrated into one processing module. The integrated module can be implemented in hardware or as a software functional module. Optionally, the module division in this application embodiment is illustrative and only represents one logical functional division; other division methods may be used in actual implementation.

[0247] In some embodiments, this application also provides a user traffic splitting device. This user traffic splitting device may include one or more functional modules for implementing the user traffic splitting method of the above method embodiments.

[0248] For example, Figure 10 This is a schematic diagram of a user traffic splitting device provided in an embodiment of this application. Figure 10 As shown, the user diversion device 900 includes: an acquisition module 901, a processing module 902, and a determination module 903.

[0249] The acquisition module 901 is used to acquire the cumulative traffic data of each user under the first PON port. The processing module 902 is used to calculate the traffic share of each user based on the cumulative traffic data. The determination module 903 is used to determine the users who need to be traffic-splittered under the first PON port based on the traffic share of each user; determine at least one candidate PON port for the users who need to be traffic-splittered under the first PON port from the PON port list based on the network topology information of the first PON port; and determine the target PON port from the at least one candidate PON port based on the load information of each candidate PON port. The processing module 902 is also used to assign the users who need to be traffic-splittered under the first PON port to the target PON port determined by the determination module.

[0250] The user traffic offloading device provided in this application calculates the traffic share of each user based on the cumulative traffic data of each user under the first PON port. Then, based on the traffic share of each user, it determines the users under the first PON port who need traffic offloading. Next, based on the network topology information of the first PON port, it determines at least one candidate PON port for the users who need traffic offloading. Finally, it combines the load information of each candidate PON port to determine the target PON port from at least one candidate PON port, and assigns the users who need traffic offloading under the first PON port to the target PON port. In other words, it uses the actual traffic data generated by the user as the direct basis for selecting offloading users, and determines the final target PON port for traffic offloading based on the load information of the candidate PON ports. Therefore, it avoids the problem of ineffective congestion relief after traffic offloading and improves traffic offloading efficiency.

[0251] In some embodiments, the network topology information includes at least one of the following: the ODN to which the first PON port belongs; the optical line terminal (OLT) of the first PON port; and the splitter group to which the first PON port is located.

[0252] In other embodiments, the processing module 902 is specifically used to add up the cumulative traffic data of each user to calculate the total traffic of the first PON port; and to use the ratio of the cumulative traffic data of each user to the total traffic of the first PON port as the traffic percentage of each user.

[0253] In some other embodiments, the determining module 903 is specifically used to sort each user according to their traffic share when the traffic share of each user under the first PON port is less than the first threshold; and to determine the users whose sorting number under the first PON port is less than the first threshold as users who need to be traffic-splitting under the first PON port; or, to determine at least one first user under the first PON port as a user who needs to be traffic-splitting under the first PON port, wherein the sorting number of at least one first user is less than the sorting number of other users under the first PON port, and the total traffic share of at least one first user is greater than or equal to the second threshold.

[0254] In some other embodiments, the determining module 903 is specifically used to determine M PON ports from the PON port list based on the network topology information of the first PON port; and to take the PON ports other than the first PON port among the M PON ports as at least one candidate PON port; wherein the M PON ports include any of the following: PON ports associated with the first ODN to which the first PON port belongs; PON ports in the first optical splitter group under the first OLT, where the first OLT is the OLT of the first PON port and the first optical splitter group is the optical splitter group to which the first PON port is located; and all PON ports under the first OLT.

[0255] In some other embodiments, the load information includes the current real-time load of each candidate PON port; the determining module 903 is specifically used to subtract the total bandwidth capacity of each candidate PON port from the current real-time load to calculate the remaining available capacity of each candidate PON port; multiply the remaining available capacity of each candidate PON port by a security factor to calculate the secure receiving capacity of each candidate PON port; and select at least one candidate PON port whose secure receiving capacity is greater than or equal to a first traffic percentage as the target PON port, where the first traffic percentage is the traffic percentage of users that need to be diverted under the first PON port.

[0256] In some other embodiments, the load information includes the expected load of each candidate PON port, which is calculated based on the traffic share of users requiring traffic offloading under the first PON port; the determining module 903 is specifically used to select the candidate PON port with the lowest expected load among at least one candidate PON port as the target PON port.

[0257] It should be noted that the user diversion device can implement all the processes implemented in the above method embodiments and achieve the same beneficial effects. To avoid repetition, it will not be described again here.

[0258] In the case where the functions of the integrated modules described above are implemented in hardware, this application provides a possible structural schematic diagram of the electronic device involved in the above embodiments. For example... Figure 11 As shown, the electronic device 90 includes: a processor 92, a communication interface 93, and a bus 94. Optionally, the electronic device 90 may also include a memory 91.

[0259] Processor 92 may implement or execute various exemplary logic blocks, modules, and circuits described in conjunction with the disclosure of this application. Processor 92 may be a central processing unit, a general-purpose processor, a digital signal processor, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. It may implement or execute various exemplary logic blocks, modules, and circuits described in conjunction with the disclosure of this application. Processor 92 may also be a combination that implements computational functions, such as including one or more microprocessor combinations, a combination of a DSP and a microprocessor, etc.

[0260] Communication interface 93 is used to connect with other devices via a communication network. This communication network can be Ethernet, wireless access network, wireless local area network (WLAN), etc.

[0261] The memory 91 may be a read-only memory (ROM) or other type of static storage device capable of storing static information and instructions, random access memory (RAM) or other type of dynamic storage device capable of storing information and instructions, or electrically erasable programmable read-only memory (EEPROM), disk storage media or other magnetic storage devices, or any other medium capable of carrying or storing desired program code in the form of instructions or data structures and accessible by a computer, but is not limited thereto.

[0262] As one possible implementation, the memory 91 can exist independently of the processor 92. The memory 91 can be connected to the processor 92 via a bus 94 and is used to store instructions or program code. When the processor 92 calls and executes the instructions or program code stored in the memory 91, it can implement the user offloading method provided in the embodiments of this application.

[0263] In another possible implementation, memory 91 can also be integrated with processor 92.

[0264] Bus 94 can be an Extended Industry Standard Architecture (EISA) bus, etc. Bus 94 can be divided into address bus, data bus, control bus, etc. For ease of representation, Figure 11 The bus is represented by a single thick line, but this does not mean that there is only one bus or one type of bus.

[0265] Through the above description of the implementation methods, those skilled in the art can clearly understand that, for the sake of convenience and brevity, only the division of the above functional modules is used as an example. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the service calling device can be divided into different functional modules to complete all or part of the functions described above.

[0266] This application embodiment also provides a chip, which includes a processor and a communication interface. The communication interface is coupled to the processor. The processor is used to run programs or instructions to implement the various processes of the above-described user traffic splitting method embodiments and can achieve the same technical effect. To avoid repetition, it will not be described again here.

[0267] It should be understood that the chip mentioned in the embodiments of this application may also be referred to as a system-on-a-chip, system chip, chip system, or system-on-a-chip, etc.

[0268] This application also provides a readable storage medium storing a program or instructions that, when executed by a computer, implement the user routing method provided in the above embodiments. It is understood that all or part of the processes in the above method embodiments can be executed by computer instructions instructing related hardware; the readable storage medium can be any of the foregoing embodiments or memory; the readable storage medium can also be an external storage device of the service invocation device, such as a pluggable hard drive, Smart MediaCard (SMC), Secure Digital (SD) card, flash card, etc., equipped on the service invocation device. Further, the readable storage medium can include both internal storage units of the service invocation device and external storage devices. The readable storage medium is used to store the computer program and other programs and data required by the service invocation device. The readable storage medium can also be used to temporarily store data that has been output or will be output.

[0269] This application also provides a computer program product, which is stored in a storage medium and implements the user traffic splitting method provided in the above embodiments when the computer program product is executed by a computer.

[0270] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element. Furthermore, it should be noted that the scope of the methods and apparatuses in the embodiments of this application is not limited to performing functions in the order shown or discussed, but may also include performing functions substantially simultaneously or in the reverse order, depending on the functions involved. For example, the described methods may be performed in a different order than described, and various steps may be added, omitted, or combined. Additionally, features described with reference to certain examples may be combined in other examples.

[0271] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a computer software product. This computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk) and includes several instructions to cause a terminal (which may be a mobile phone, computer, server, or network device, etc.) to execute the methods described in the various embodiments of this application.

[0272] The embodiments of this application have been described above with reference to the accompanying drawings. However, this application is not limited to the specific embodiments described above. The specific embodiments described above are merely illustrative and not restrictive. Those skilled in the art can make many other forms under the guidance of this application without departing from the spirit and scope of the claims, and all of these forms are within the protection scope of this application.

Claims

1. A user traffic splitting method, characterized in that, The method includes: Obtain the cumulative traffic data for each user under the first passive optical network (PON) port; Based on the cumulative traffic data, the traffic share of each user is calculated; Based on the traffic share of each user, determine the users who need to be diverted under the first PON port; Based on the network topology information of the first PON port, at least one candidate PON port is determined from the PON port list for users who need to be traffic-splitting under the first PON port. Based on the load information of each candidate PON port, a target PON port is determined from the at least one candidate PON port, and users who need to be offloaded under the first PON port are assigned to the target PON port.

2. The user traffic splitting method according to claim 1, characterized in that, The network topology information includes at least one of the following: The optical distribution network (ODN) to which the first PON port belongs; The first PON port's optical line terminal (OLT); The splitter group where the first PON port is located.

3. The user traffic splitting method according to claim 1, characterized in that, The step of calculating the traffic share of each user based on the cumulative traffic data includes: The total traffic of the first PON port is calculated by adding up the cumulative traffic data of each user. The ratio of each user's cumulative traffic data to the total traffic of the first PON port is taken as the traffic percentage of each user.

4. The user traffic splitting method according to claim 1, characterized in that, The process of determining the users who need to be traffic-splittered under the first PON port based on the traffic share of each user includes: If the traffic share of each user under the first PON port is less than the first threshold, then each user is sorted according to the traffic share of each user. Users whose sequence number under the first PON port is less than the first threshold are identified as users who need to be offloaded under the first PON port; or... At least one first user under the first PON port is identified as a user that needs to be traffic-splitting under the first PON port. The sequence number of the at least one first user is less than the sequence number of other users under the first PON port, and the total traffic share of the at least one first user is greater than or equal to the second threshold.

5. The user traffic splitting method according to claim 1, characterized in that, Based on the network topology information of the first PON port, at least one candidate PON port is determined from the PON port list for users who need traffic offloading under the first PON port, including: Based on the network topology information of the first PON port, M PON ports are determined from the PON port list; The PON ports other than the first PON port among the M PON ports are regarded as at least one candidate PON port; The M PON ports include any one of the following: The PON port associated with the first ODN to which the first PON port belongs; The PON port in the first splitter group under the first OLT, where the first OLT is the OLT of the first PON port and the first splitter group is the splitter group where the first PON port is located. All PON ports under the first OLT.

6. The user traffic splitting method according to claim 1, characterized in that, The load information includes the current real-time load of each candidate PON port; determining the target PON port from the at least one candidate PON port based on the load information of each candidate PON port includes: The remaining available capacity of each candidate PON port is calculated by subtracting the total bandwidth capacity of each candidate PON port from the current real-time load. The remaining available capacity of each candidate PON port is multiplied by the security factor to calculate the secure reception capacity of each candidate PON port. The candidate PON port whose secure reception capacity is greater than or equal to the first traffic percentage among the at least one candidate PON port shall be used as the target PON port, where the first traffic percentage is the traffic percentage of the users who need to be offloaded under the first PON port.

7. The user traffic splitting method according to claim 1, characterized in that, The load information includes the expected load of each candidate PON port, and the expected load of each candidate PON port is calculated based on the traffic proportion of users who need to be diverted under the first PON port. The step of determining the target PON port from the at least one candidate PON port based on the load information of each candidate PON port includes: The candidate PON port with the lowest expected load among the at least one candidate PON ports shall be selected as the target PON port.

8. A user diversion device, characterized in that, include: Acquisition module, processing module, determination module; The acquisition module is used to acquire the cumulative traffic data of each user under the first PON port; The processing module is used to calculate the traffic percentage of each user based on the cumulative traffic data obtained by the acquisition module; The determining module is used to determine the users who need to be traffic-splitting under the first PON port based on the traffic ratio of each user calculated by the processing module. Based on the network topology information of the first PON port, at least one candidate PON port is determined from the PON port list for users who need to be traffic-splitting under the first PON port. And based on the load information of each candidate PON port, the target PON port is determined from the at least one candidate PON port; The processing module is further configured to assign users who need to be routed under the first PON port to the target PON port determined by the determining module.

9. An electronic device, characterized in that, It includes a processor and a memory, the memory storing programs or instructions that can run on the processor, the programs or instructions being executed by the processor to implement the user offloading method as described in any one of claims 1-7.

10. A readable storage medium, characterized in that, The readable storage medium stores a program or instructions that, when executed by a computer, implement the user routing method as described in any one of claims 1-7.

11. A computer program product, characterized in that, The computer program product is stored in a storage medium, and when executed by a computer, the computer program product implements the user routing method as described in any one of claims 1-7.

Images