Internet traffic controlling system and operating method thereof

Abstract

An operating method for a network traffic control system includes receiving first data; sorting the first data and generating a sequence; detecting parameters of a website page and generating a first quantity based on the parameters; and sequentially importing the first data corresponding to the sequence into the website page according to the first quantity, wherein the number of first data imported into the website page is equal to the first quantity.

Description

Technical Field

[0001] This disclosure relates to a network traffic control system and its operation method. Prior Technology

[0002] Internet service providers (ISPs) that require traffic control have implemented mechanisms such as increasing the number of servers and using caching to prevent a surge of users from overloading their websites. However, when the number of users exceeds the server's capacity, a large influx of users can still overload the website. Furthermore, ISPs also use relational databases to address website load issues. However, relational databases are limited by the fact that they are already operational online and store a large amount of customer, transaction, and operational data, thus preventing real-time performance improvements. Summary of the Invention

[0003] This disclosure includes an operation method for a network traffic control system, comprising: receiving a plurality of first data; sorting each of the first data and generating a sequence; detecting a plurality of parameters of a website page and generating a first quantity based on the parameters; and sequentially importing the corresponding first data in the sequence into the website page according to the first quantity, wherein the number of first data imported into the website page is equal to the first quantity.

[0004] This disclosure includes a network traffic control system, comprising: a first module for receiving a plurality of first data and further sorting each of the first data to generate a sequence; a second module for detecting a plurality of parameters of a website page and generating a first quantity based on the parameters; and a third module for sequentially importing the first data into the website page according to the first quantity. The number of first data imported into the website page is equal to the first quantity. Simple Explanation of the Diagram

[0005] The nature of this disclosure is best understood when read in conjunction with the accompanying drawings in the following detailed description. It should be noted that, in accordance with industry standard practice, the various features are not drawn to scale. In fact, for clarity of discussion, the dimensions of the various features may be arbitrarily increased or decreased. Figure 1 is a schematic diagram illustrating a network traffic control system according to some embodiments of the present disclosure. Figure 2 is a schematic diagram of a traffic detection module according to some embodiments of the present disclosure. Figure 3 is a block diagram illustrating the operation of a network traffic control system according to some embodiments of the present disclosure. Figure 4 is an operation flowchart of a network traffic control system according to some embodiments of the present disclosure. Figure 5 is an operation flowchart of a network traffic control system according to some embodiments of the present disclosure. Figure 6 is a schematic diagram illustrating the application of a network traffic control system according to some embodiments of the present disclosure. Figure 7 is a schematic diagram illustrating the application of a network traffic control system according to some embodiments of the present disclosure. Figure 8 is a schematic diagram illustrating the application of a network traffic control system according to some embodiments of the present disclosure. Implementation

[0006] In this document, when an element is referred to as a "connection" or "coupled," it may mean an "electrical connection" or "electrical coupling." "Connection" or "coupled" can also be used to indicate the operation or interaction between two or more elements. Furthermore, although terms such as "first," "second," etc., are used herein to describe different elements, these terms are merely used to distinguish elements or operations described using the same technical terms. Unless the context clearly indicates otherwise, these terms do not specifically refer to or imply any order or sequence, nor are they intended to limit the invention.

[0007] Unless otherwise defined, all terms used herein (including technical and scientific terms) have the same meaning as commonly understood by one of ordinary skill in the art to which this invention pertains. It will be further understood that terms such as those defined in commonly used dictionaries should be interpreted as having meanings consistent with their meanings in the context of the relevant technology and this invention, and will not be interpreted as having idealized or overly formal meanings unless expressly defined herein.

[0008] The terminology used herein is for the purpose of describing particular embodiments only and is not restrictive. As used herein, unless the content clearly indicates otherwise, the singular forms "a," "an," and "the" are intended to include the plural forms, including "at least one." "Or" means "and / or." As used herein, the term "and / or" includes any and all combinations of one or more of the associated listed items. It should also be understood that, when used in this specification, the terms "comprising" and / or "including" specify the presence of the stated features, areas, integrals, steps, operations, elements, and / or components, but do not exclude the presence or addition of one or more other features, areas, integrals, steps, operations, elements, components, and / or combinations thereof.

[0009] The following diagrams will disclose several embodiments of this invention. For clarity, many practical details will be described in the following description. However, it should be understood that these practical details should not be used to limit this invention. That is, these practical details are not necessary in the embodiments disclosed herein. Furthermore, for the sake of simplicity, some conventional structures and components will be shown in the diagrams in a simple schematic manner.

[0010] Figure 1 is a schematic diagram illustrating a network traffic control system 100 according to some embodiments of the present disclosure. In some embodiments, the network traffic control system 100 may be implemented using a processor, memory, and a display. As shown in Figure 1, the network traffic control system 100 includes a queuing module 110, a traffic detection module 120, a passage module 130, and a destination page 102. The queuing module 110 is used to store queuing sequences 111.

[0011] In Figure 1, queuing module 110 receives queuing data 101. Traffic detection module 120 is connected to queuing module 110 for data exchange. Release module 130 is connected to queuing module 110 for data exchange. Queuing module 110 further transmits data to destination page 102. Destination page 102 connects to destination website 103.

[0012] In some embodiments, the network traffic control system 100 further includes an Identifier URL (IDR) (not shown in the figures). When queuing data 101 is imported into the destination page 102 via the release module 130, the Identifier URL IDR is used to provide information identifying the destination page 102. Implementation details of the network traffic control system 100 and the application of the Identifier URL IDR are described in detail in Figures 3 through 5 and their corresponding paragraphs.

[0013] In some embodiments, the network traffic control system 100 may be implemented using a Uniform Resource Locator (URL) or a Shortened URL, and may be located on a server and / or cloud computing platform. In some embodiments, the queuing sequence 111 may be implemented using memory, and queuing data 101 may be stored sequentially using memory bit sequences. In some embodiments, the destination page 102 may be implemented using a cloud computing platform and / or server and a display, and the destination page 102 and the destination website 103 may be displayed on the display.

[0014] In some embodiments, the network traffic control system 100 can be applied to online shopping, ticketing systems, membership services, or network service providers that require traffic control to prevent a large influx of users from overwhelming the website. The destination website 103 may include, but is not limited to, websites corresponding to the aforementioned online shopping, ticketing systems, membership services, or other similar website pages. The network traffic control system 100 uses a queuing module 110 to sequentially arrange the information of a large number of users, and uses a release module 130 to sequentially import the information of some users into the destination page 102 based on the traffic data detected by the traffic detection module 120. When a large number of users simultaneously enter a specific website, the network traffic control system 100 can effectively control user traffic to avoid network congestion.

[0015] Figure 2 is a schematic diagram of a traffic detection module 120 according to one embodiment of the present disclosure.

[0016] As shown in Figure 2, the traffic detection module 120 further receives the device parameters 210 and website parameters 220 of the destination page 102 through signals S1 and S2.

[0017] In some embodiments, the traffic detection module 120 performs traffic control settings based on the device parameters 210 and website parameters 220 of the destination page 102, and generates a number of controlled users N. The traffic detection module 120 further transmits the number of controlled users N to the queuing module 110.

[0018] In some embodiments, device parameter 210 includes at least one of the central processing unit (CPU) load rate R1 and the number of web sessions R2, but this disclosure is not limited thereto. In some embodiments, website parameter 220 includes at least the response time R3 of the target page, but this disclosure is not limited thereto. The response time R3 may include, but is not limited to, the average response time of the webpage and the delay in seconds. Details regarding the traffic control settings of device parameter 210 and website parameter 220 are described in detail in Figure 3 below and the corresponding paragraph.

[0019] In some embodiments, the load factor R1 can be expressed as a percentage, such as 80% of the maximum load. The number of web page connections R2 can be expressed as connections per minute, such as 450 connections / minute. The response time R3 can be expressed in milliseconds, such as 500 milliseconds.

[0020] Figure 3 is a block diagram 300 illustrating the operation of a network traffic control system 100 according to some embodiments of the present disclosure. As shown in Figure 3, block diagram 300 includes blocks 301-311.

[0021] In blocks 301 and 302, queuing module 110 receives queuing data 101. Queuing module 110 encodes the queuing data 101 to generate a code C, and further indicates the time T at which the queuing data 101 was input into queuing module 110. In addition, when queuing data 101 is received by queuing module 110, queuing module 110 inputs the identification URL (IDR) of network traffic control system 100 into the queuing data 101.

[0022] In some embodiments, queuing data 101 may be one or more queuing data, and the one or more queuing data 101 may correspond to one or more codes C, one or more times T and one or more user information U1 respectively.

[0023] In some embodiments, queuing data 101 may include user information U1, which includes an identification information ID, an Internet Protocol address (IPA), an identification URL (IDR), and the URL of the destination website 103. The identification information ID includes the user UE's account, phone number, or other information that can identify the user UE, but this disclosure is not limited to this. In some embodiments, the destination page 102 imports the user information U1 into the destination website 103 based on the URL of the destination website 103.

[0024] In some embodiments, when there are multiple queue data 101, the queuing module 110 receives each of the multiple queue data 101 at different times T. In some embodiments, code C may be implemented by means of a website's digital stub (cookie) and included in code C. In other embodiments, code C may be implemented by encoding identification information ID in the queue data 101. When there are multiple queue data 101, the multiple codes C have different digital stub cookies and / or identification information IDs.

[0025] In some embodiments, code C is used to provide the user UE's digital stub cookie and / or identification information ID to the destination page 102. The destination page 102 verifies code C to identify whether the user information U1 is queued through the network traffic control system 100. The specific verification method is described in detail in block 308.

[0026] In block 303, queuing module 110 sorts the queuing data 101 from first to last according to time T and generates queuing sequence 111. For example, when there are 8 users A~H and corresponding to 8 sets of queuing data 101, the queuing data 101 corresponds to the time T_A~T_H for each user A~H when the information is input to queuing module 110. Queuing module 110 arranges user information AE~HE in chronological order according to time T_A~T_H and generates queuing sequence 111. Queuing sequence 111 includes user information AE, user information BE, user information CE, user information DE, user information EE, user information FE, user information GE, and user information HE arranged in sequence.

[0027] Returning to block 302, queuing module 110 further checks whether user information U1 already exists in queue sequence 111 using code C. If user information U1 does not exist in queue sequence 111, queuing module 110 adds queued data 101 sequentially to queue sequence 111 according to time T. If user information U1 already exists in queue sequence 111, queuing module 110 imports the user information U1 corresponding to code C to the end page of block 310. For example, when code C_A corresponding to user A already exists in queue sequence 111, queuing module 110 imports user information AE to the end page. When code C_A corresponding to user A does not exist in queue sequence 111, queuing module 110 adds user information AE to queue sequence 111 according to time T.

[0028] In block 304, the traffic detection module 120 detects the device parameters 210 and website parameters 220 of the destination page 102. Specifically, the traffic detection module 120 detects the load rate R1, the number of web page connections R2, and the response time R3 of the destination page 102.

[0029] In block 305, the traffic detection module 120 sets the traffic control settings according to the device parameters 210 and the web page parameters 220, and generates the number of controllers N.

[0030] Specifically, the traffic detection module 120 detects the load rate R1, the number of web page connections R2, and the response time R3 of the target page 102, and sets the number of controllers N based on the load rate R1, the number of web page connections R2, and the response time R3.

[0031] In some embodiments, when at least one of the load rate R1, the number of web page connections R2, and the response time R3 increases, the traffic detection module 120 reduces the number of controllers N. When at least one of the load rate R1, the number of web page connections R2, and the response time R3 decreases, the traffic detection module 120 increases the number of controllers N.

[0032] In other embodiments, the traffic detection module 120 adjusts the number of controllers N in stages according to the upper limits of load rate RL1, upper limit of web page connection RL2, and upper limit of response time RL3 corresponding to load rate R1, web page connection number R2, and response time R3, respectively.

[0033] For example, in some scenarios, the load factor cap RL1 is 90%, the maximum number of web page connections RL2 is 500, the maximum response time RL3 is 1000, and the number of administrators N is 1000. When the load factor R1 is higher than 90% of the load factor cap RL1, that is, when the load factor R1 is higher than 81%, the number of administrators N is reduced by 10%, that is, reduced by 100. At this time, the number of administrators N is 900.

[0034] Continuing with the previous example, in other scenarios, when the number of webpage connections R2 is higher than 90% of the upper limit RL2, that is, when the number of webpage connections R2 is higher than 450, the number of people under control N decreases by 10%, that is, by 100 people. At this time, the number of people under control N is 900.

[0035] Continuing with the previous example, in other scenarios, when the response time R3 is 50% higher than the maximum response time limit RL3, that is, when the response time R3 is higher than 500, the number of people under control N is reduced by 20%, that is, reduced by 200 people. At this time, the number of people under control N is 800.

[0036] For another example, in some scenarios, the load factor cap RL1 is 90%, the maximum number of web page connections RL2 is 500, the maximum response time RL3 is 1000, and the number of administrators N is 1000. When the load factor R1 falls below 80% of the load factor cap RL1, i.e., when the load factor R1 is below 72%, the number of administrators N increases by 10%, or 100. At this point, the number of administrators N is 1100.

[0037] Continuing with the previous example, in other scenarios, when the number of webpage connections R2 is less than 80% of the upper limit RL2, that is, when the number of webpage connections R2 is less than 400, the number of people under control N increases by 10%, that is, by 100 people. At this time, the number of people under control N is 1100.

[0038] Continuing with the previous example, in other scenarios, when the response time R3 is less than 50% of the maximum response time limit RL3, that is, when the response time R3 is less than 500, the number of people under control N increases by 10%, that is, by 100 people. At this time, the number of people under control N is 1100.

[0039] In some embodiments, the number of people controlled N can be indicated as the number of people allowed to enter the destination page 102, or as the number of people allowed to enter per minute, but this disclosure is not limited thereto. For example, the number of people controlled N can be indicated as 2 people / minute, that is, two user information U1 can be imported into the destination page 102 from the queue sequence 111 per minute.

[0040] In some embodiments, load factor R1 is the utilization level of a core in the central processing unit (CPU) of the hardware device, expressed as a percentage. Webpage connections R2 is defined as a single session representing a set of interactions generated by a visitor within the website. Therefore, as the number of visitors and interactions increases, the webpage connections R2 increases accordingly. Response time R3 is the time elapsed for a webpage to generate a response when an action is performed on it.

[0041] In block 306, the release module 130 imports user U1 in queue sequence 111 and the corresponding queue data 101 into the destination page 102 according to the flow control settings in block 305.

[0042] Specifically, the release module 130 imports the user information U1 and the corresponding queuing data 101 in the queue sequence 111 into the destination page 102 in sequence according to the number of controlled users N generated by the traffic detection module 120, and imports each of the other user information U1 in the queue sequence 111 that has not been imported into the destination page 102 into the waiting page of block 311.

[0043] For example, when queue 111 contains user information AE, BE, CE, DE, EE, FE, GE, and HE arranged in sequence, and the controlled number of users N is 2 people / minute, the release module 130 imports user information AE and BE from queue 111, along with their corresponding codes C_A and C_B, into destination page 102. Next, the release module 130 imports the remaining user information CE, DE, EE, FE, GE, and HE from queue 111 into the waiting page in block 311. Further, based on the controlled number of users N, the release module 130 imports user information CE and DE, along with their corresponding codes C_C and C_D, into destination page 102 after one minute, and so on.

[0044] In block 307, the destination page 102 is included, and the user UE code C imported by the access module 130 is verified via the destination page 102. In some embodiments, before the user information U1 enters the website on page 102, the user UE code C must be verified via the destination page 102. The verification method will be shown in the following block 308.

[0045] In block 308, destination page 102 verifies code C. Specifically, destination page 102 decodes the encoded code C to obtain a digital stub cookie and / or identification information ID and identification URL IDR, and further verifies the identification URL IDR. When destination page 102 verifies that the decoded identification URL is the identification URL IDR from network traffic control system 100, destination page 102 determines that user information U1 has been verified and imports user information U1 into destination website 103 in block 309. When destination page 102 verifies that the decoded identification URL is not the identification URL IDR from network traffic control system 100, destination page 102 determines that user information U1 has failed to be verified and imports user information U1 into queuing module 110 in block 302 for re-queuing.

[0046] In some embodiments, the destination page 102 uses a digital stub cookie to identify the user UE and uses the digital stub cookie to indicate whether the user information U1 has been verified.

[0047] In some embodiments, destination page 102 is used to provide a verification page before the user UE enters destination website 103, and destination page 102 is included in network traffic control system 100.

[0048] Figure 4 is a flowchart illustrating an operation method 400 of a network traffic control system 100 according to some embodiments of the present disclosure. As shown in Figure 4, the operation method 400 includes operations 401 to 408. Referring also to Figures 4 and 3, operations 401 to 408 correspond to the operation steps of blocks 301 to 311 in block diagram 300.

[0049] In some embodiments, the operation method 400 corresponds to a scenario where the queuing data 101 of the user UE does not have an identification information ID. When the queuing data 101 does not have an identification information ID, the network traffic control system 100 assigns a digital stub cookie to the user information U1 and includes it in the queuing data 101.

[0050] Operation 401 corresponds to block 301. In operation 401, the queuing module 110 in the network traffic control system 100 receives one or more queuing data 101. The queuing data 101 corresponds to one or more user information U1. After completing operation 401, the network traffic control system 100 performs operation 402.

[0051] Operation 402 corresponds to block 302. In operation 402, queuing module 110 encodes a code C into queuing data 101. Code C contains a digit stub cookie and an identifier URL (IDR). Network traffic control system 100 performs operation 403 after completing operation 402.

[0052] Operation 403 corresponds to blocks 302, 303, and 310. In operation 403, queuing module 110 determines whether user information U1 is already in queue sequence 111 based on code C. If user information U1 is already in queue sequence 111, queuing module 110 imports user information U1 to the end page. If user information U1 is not in queue sequence 111, queuing module 110 imports user information U1 into queue sequence 111. After completing operation 403, network traffic control system 100 performs operation 404.

[0053] Operation 404 corresponds to blocks 304-306 and 311. In operation 404, the access module 130 sequentially imports user information U1 into the destination page 102 according to the number of controlled users N. The network traffic control system 100 performs operation 405 after completing operation 404.

[0054] Specifically, the access module 130 detects the device parameters 210 and website parameters 220 of the destination page 102 and generates a controlled number of users N. Then, the access module 130 further imports a portion of the user information U1 in the queue sequence 111 into the destination page 102 according to the controlled number of users N, and imports another portion of the user information U1 into the waiting screen.

[0055] In the embodiments disclosed herein, the device parameters 210 and website parameters 220 include at least each of the load rate R1, the number of web page connections R2, and the response time R3 of the target page 102, but the content of this disclosure is not limited to these parameters.

[0056] In some embodiments, operations 405 and 406 correspond to blocks 307-309 and 302.

[0057] In operation 405, the destination page 102 decodes the code C corresponding to the user UE to obtain the user UE's digital stub cookie and identification URL IDR. The network traffic control system 100 performs operation 406 after completing operation 405.

[0058] In operation 406, the destination page 102 further verifies the decoded code C and determines whether the verification passes. If the destination page 102 determines that the verification passes, the network traffic control system 100 performs operation 407 after completing operation 406. If the destination page 102 determines that the verification fails, the network traffic control system 100 performs operation 408 after completing operation 406.

[0059] Specifically, destination page 102 further verifies the user UE's digital stub cookie and identification URL IDR. When destination page 102 verifies that the decoded identification URL is from the network traffic control system 100's identification URL IDR, destination page 102 determines that the user information U1 verification is successful. When destination page 102 verifies that the decoded identification URL is not from the network traffic control system 100's identification URL IDR, destination page 102 determines that the user information U1 verification is unsuccessful.

[0060] In operation 407, when the destination page 102 determines that the user information U1 has been verified, the destination page 102 imports the user information U1 into the destination website 103 and completes the operation method 400 of the network traffic control system 100.

[0061] In operation 408, when the destination page 102 determines that the user information U1 fails verification, the destination page 102 imports the user information U1 into the queuing module 110 and re-queues it. In other words, the network traffic control system 100 repeats operations 401 to 406.

[0062] Figure 5 is a flowchart illustrating an operation method 500 of a network traffic control system 100 according to some embodiments of the present disclosure. As shown in Figure 5, the operation method 500 includes operations 501 to 508. Referring also to Figures 5 and 3, operations 501 to 508 correspond to the operation steps of blocks 301 to 311 in block diagram 300.

[0063] In some embodiments, the operation method 500 corresponds to a scenario where the queuing data 101 of the user UE has an identification information ID. When the queuing data 101 has an identification information ID, the network traffic control system 100 identifies the user UE based on the identification information ID.

[0064] Operation 501 corresponds to block 301. In operation 501, the queuing module 110 in the network traffic control system 100 receives one or more queuing data 101. The queuing data 101 corresponds to one or more user information U1. After completing operation 501, the network traffic control system 100 performs operation 502.

[0065] Operation 502 corresponds to block 302. In operation 502, queuing module 110 encodes a code C into queuing data 101, where code C contains identification information ID and identification URL IDR. Network traffic control system 100 performs operation 503 after completing operation 502.

[0066] Operation 503 corresponds to blocks 302, 303, and 310. In operation 503, queuing module 110 determines whether user information U1 is already in queue sequence 111 based on code C. If user information U1 is already in queue sequence 111, queuing module 110 imports user information U1 to the end page. If user information U1 is not in queue sequence 111, queuing module 110 imports user information U1 into queue sequence 111. After completing operation 503, network traffic control system 100 performs operation 504.

[0067] Operation 504 corresponds to blocks 304-306 and 311. In operation 504, the access module 130 sequentially imports user information U1 into the destination page 102 according to the number of controlled users N. The network traffic control system 100 performs operation 505 after completing operation 404.

[0068] Specifically, the access module 130 detects the device parameters 210 and website parameters 220 of the destination page 102 and generates a controlled number of users N. Next, the access module 130 further imports a portion of the user information U1 from the queue sequence 111 into the destination page 102 according to the controlled number of users N, and imports another portion of the user information U1 into the waiting screen. The device parameters 210 and website parameters 220 include at least one of the following: the load rate R1 of the destination page 102, the number of web page connections R2, and the response time R3; however, this disclosure is not limited to these parameters.

[0069] In some embodiments, operations 505 and 506 correspond to blocks 307-309 and 302.

[0070] In operation 505, the destination page 102 decodes the code C corresponding to the user UE to obtain the user UE's identification information ID and identification URL IDR. The network traffic control system 100 performs operation 506 after completing operation 505.

[0071] In operation 506, the destination page 102 further verifies the decoded code C and determines whether the verification passes. If the destination page 102 determines that the verification passes, the network traffic control system 100 performs operation 507 after completing operation 506. If the destination page 102 determines that the verification fails, the network traffic control system 100 performs operation 508 after completing operation 506.

[0072] Specifically, destination page 102 further verifies the user UE's identification information ID and identification URL IDR. When destination page 102 verifies that the decoded identification URL is from the network traffic control system 100's identification URL IDR, destination page 102 determines that the user information U1 verification is successful. When destination page 102 verifies that the decoded identification URL is not from the network traffic control system 100's identification URL IDR, destination page 102 determines that the user information U1 verification is unsuccessful.

[0073] In operation 507, when the destination page 102 determines that the user information U1 has been verified, the destination page 102 imports the user information U1 into the destination website 103 and completes the operation method 500 of the network traffic control system 100.

[0074] In operation 508, when the destination page 102 determines that the user information U1 fails verification, the destination page 102 imports the user information U1 into the queuing module 110 and re-queues it. In other words, the network traffic control system 100 repeats operations 501 to 506.

[0075] Figure 6 is a schematic diagram 600 illustrating the application of a network traffic control system 100 according to some embodiments of the present disclosure. Schematic diagram 600 illustrates one application of the network traffic control system 100. As shown in Figure 6, schematic diagram 600 includes a network traffic control system 100A and multiple destination websites W1, W2, W3, and W4.

[0076] Referring to Figures 6 and 3, the network traffic control system 100A can import user information U1 into multiple destination websites W1, W2, W3 and W4.

[0077] Specifically, as in blocks 307-309, destination page 102 decodes and verifies the user's (UE) code C. When the user information U1 is verified, destination page 102 imports the user information U1 into one of the corresponding destination websites W1, W2, W3, and W4.

[0078] In some embodiments, when there are multiple destination websites W1, W2, W3 and W4, the queuing data 101 may include the URLs corresponding to the destination websites W1, W2, W3 and W4 that the user UE wants to visit.

[0079] Figure 7 is a schematic diagram 700 illustrating the application of a network traffic control system 100 according to some embodiments of the present disclosure. Schematic diagram 700 illustrates one application of the network traffic control system 100. As shown in Figure 7, schematic diagram 700 includes network traffic control systems 100A, 100B, 100C and multiple destination websites W1, W2, W3 and W4.

[0080] Referring to Figures 7 and 3, the network traffic control systems 100A, 100B, and 100C can import multiple user information U1 into multiple destination websites W1, W2, W3, and W4.

[0081] Specifically, as in blocks 307-309, destination page 102 decodes and verifies the user UE's code C. When user U1 is successfully verified, destination page 102 of each of network traffic control systems 100A and 100B imports user information U1 into destination websites W1 and W2 respectively, and destination page 102 of network traffic control system 100C imports user information U1 into one of destination websites W3 and W4 respectively.

[0082] In some scenarios, the network traffic control system 100 may correspond to a destination website 103. For example, the network traffic control system 100A is used to queue user information U1 and sequentially import it into the destination website W1, and the network traffic control system 100B is used to queue user information U1 and sequentially import it into the destination website W2.

[0083] In other scenarios, similar to the schematic diagram 600 in Figure 6, the network traffic control system 100 may correspond to multiple destination websites 103. For example, the network traffic control system 100C is used to queue user information U1 and sequentially import it into destination websites W3 or W4.

[0084] In schematic diagram 700, network traffic control systems 100A, 100B, and 100C can simultaneously correspond to one or more destination websites W1, W2, W3, and W4. Multiple network traffic control systems 100A, 100B, and 100C can operate simultaneously, each corresponding to one destination website W1 or W2 (e.g., network traffic control systems 100A and 100B), and each corresponding to multiple destination websites W3 and W4 (e.g., network traffic control system 100C).

[0085] Figure 8 is a schematic diagram 800 illustrating the application of a network traffic control system 100 according to some embodiments of the present disclosure. Schematic diagram 800 illustrates one application of the network traffic control system 100. As shown in Figure 8, schematic diagram 800 includes network traffic control systems 100A, 100B, 100C, 100D and multiple destination websites W1, W2, W3, and W4.

[0086] Referring to Figures 8 and 3, the network traffic control systems 100A, 100B, 100C, and 100D can import multiple user information U1 into multiple destination websites W1, W2, W3, and W4 respectively.

[0087] Specifically, as in blocks 307-309, destination page 102 decodes and verifies the user UE's code C. When the user information U1 is verified, the destination page 102 of each of the network traffic control systems 100A, 100B, 100C, and 100D imports the user information U1 into multiple destination websites W1, W2, W3, and W4 respectively.

[0088] In some scenarios, such as schematic diagram 700 in Figure 7, network traffic control systems 100A and 100B can correspond to one destination website W1 and W2 respectively, and network traffic control system 100C can correspond to multiple destination websites W3 and W4.

[0089] In other scenarios, relative to schematic diagram 700, each of the network traffic control systems 100A, 100B, 100C, and 100D in schematic diagram 800 can correspond to multiple destination websites W1, W2, W3, and W4, respectively. The network traffic control systems 100A, 100B, 100C, and 100D can operate simultaneously, directing multiple users U1 to one of the multiple destination websites W1, W2, W3, and W4.

[0090] In some embodiments disclosed herein, the term "import" also means to transmit data. For example, "the destination page 102 imports the user corresponding to user information U1 into the queuing module 110" means that the destination page 102 transmits the data of the user corresponding to user information U1 to the queuing module 110.

[0091] In some embodiments, the number of destination pages 103 that the network traffic control system 100 corresponds to is determined based on the computing performance and memory of the cloud service platform and / or server on which the network traffic control system 100 is applied. The higher the computing performance and memory of the cloud service platform and / or server, the higher the number of destination pages 103 that the network traffic control system 100 can correspond to. Conversely, the lower the computing performance and memory of the cloud service platform and / or server, the lower the number of destination pages 103 that the network traffic control system 100 can correspond to. However, this disclosure is not limited to applying the network traffic control system 100 to a cloud service platform and / or server.

[0092] In some methods, network service providers that require traffic control expand the number of servers and implement caching and traffic splitting mechanisms to prevent a large influx of users (UEs) from overloading the website. However, when the number of users exceeds the server's load capacity, the large number of users will still overload the website and cannot effectively solve the problem.

[0093] In other approaches, internet service providers employ relational databases, commonly used in information systems, to address website load issues. However, relational databases are limited by the fact that they are already operational online and store large amounts of customer, transaction, and operational data, thus preventing real-time performance improvements. Furthermore, using commercial database software is costly and not cost-effective.

[0094] In the embodiments disclosed herein, the network traffic control system 100 can sequentially arrange a large amount of user information U1 through the queuing module 110, and sequentially import some of the user information U1 into the destination page 102 through the release module 130 based on the traffic data detected by the traffic detection module 120. Furthermore, the network traffic control system 100 can, as shown in the schematic diagrams 600, 700, and 800 of Figures 6 to 8, address the needs of different network service providers and resolve website load issues by corresponding to one or more destination websites 103.

[0095] The foregoing outlines the features of several embodiments, enabling those skilled in the art to better understand the nature of this disclosure. Those skilled in the art will understand that they can readily use this disclosure as a basis for designing or modifying other processes and structures for implementing the same purpose and / or achieving the advantages of the embodiments described herein. Those skilled in the art will also recognize that such equivalent constructions do not depart from the spirit and scope of this disclosure, and that various changes, substitutions, and modifications can be made herein without departing from the spirit and scope of this disclosure.

[0096] 100, 100A, 100B, 100C, 100D: Network Traffic Control System 101: Queue Information 102: Destination Page 103: Target Website 110: Queue Module 111: Queuing sequence 120: Traffic Detection Module 130: Release Module 210: Device Parameters 220: Website Parameters 300: Flowchart Blocks 301-311 400: Operating Instructions 401~408: Operation 500: Operating Instructions 501~508: Operation 600: Schematic diagram 700: Schematic diagram 800: Schematic diagram A, B, C, D, E, F, G, H: Users AE, BE, CE, DE, EE, FE, GE, HE: User Information C, C_A, C_B, C_C, C_D: Code Cookie: Digital Stub ID: Identify Information IDR: Identify URL N: Number of people under control R1: Load Rate R2: Number of web page connections [] R3: Response Time RL1: Maximum load rate RL2: Maximum number of web page connections RL3: Maximum response time S1, S2: Signals T, T_A, T_B, T_C, T_D, T_E, T_F, T_G, T_H: time U1: User Information UE: User W1~W4: Destination Website

[0097] Domestic storage information (please note in order of storage institution, date, and number) none Overseas storage information (please note in the order of storage country, institution, date, and number) none

Claims

1. A method for operating a network traffic control system, comprising: The method includes: receiving a plurality of first data; sorting each of the first data and generating a sequence; detecting a plurality of parameters of a website page and generating a first quantity based on the parameters; and sequentially importing the corresponding first data in the sequence into the website page according to the first quantity, wherein the number of first data imported into the website page is equal to the first quantity. The method further includes: performing a verification based on a first code and a second code when the first data are sequentially imported into the website page, wherein each of the first data includes the first code, and the website page includes the second code; wherein performing the verification further includes: comparing the first code and the second code; importing the first data into the website page when the first code and the second code are the same; and importing the first data into a first module when the first code and the second code are different, wherein the first module is used to receive the first data and reorder each of the first data to generate a rearranged sequence.

2. The operating method as described in claim 1, wherein the parameters include a load rate, the first quantity decreases when the load rate increases, and the first quantity increases when the load rate decreases.

3. The method of operation as described in claim 1, wherein the parameters include a number of connections, wherein the first quantity decreases when the number of connections increases, and the first quantity increases when the number of connections decreases.

4. The method of operation as described in Request 1, wherein the parameters include a response time, wherein the first quantity decreases when the response time increases, and the first quantity increases when the response time decreases.

5. A network traffic control system, comprising: A first module is configured to receive a plurality of first data and further sort each of the first data to generate a sequence; A second module is configured to detect a plurality of parameters of a website page and generate a first quantity based on the parameters; and a third module is configured to sequentially import the first data into the website page according to the first quantity, wherein the number of the first data imported into the website page is equal to the first quantity, wherein each of the first data includes a first code, the website page includes a second code, and when the first data is sequentially imported into the website page, a verification is performed based on the first code and the second code, wherein the verification includes: comparing the first code and the second code; when the first code and the second code are the same, importing the first data into the website page; and when the first code and the second code are different, importing the first data into the first module, wherein the first module is configured to receive the first data and reorder each of the first data to generate a rearranged sequence.

6. The network traffic control system as claimed in claim 5, wherein the parameters include a load rate, a number of connections, and a response time, wherein the first quantity decreases when any of the load rate, the number of connections, and the response time increases, and the first quantity increases when any of the load rate, the number of connections, and the response time decreases.

Images