Methods and systems for controlling application traffic in game acceleration scenarios
By dynamically controlling the network traffic of dependent applications in game acceleration scenarios and performing differentiated processing based on activation status, access authorization status, and usage context, the problem of inaccurate dependent application traffic control in existing technologies is solved. This achieves isolation between the normal operation of background services of dependent applications and the traffic used in the foreground, improving the reliability and security of control.
Patent Information
- Application Number
- CN202611619662.6
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2026-10-20
- Publication Date
- 2026-11-17
AI Technical Summary
Existing technologies make it difficult to differentiate network traffic for dependent applications in game acceleration scenarios, which may result in overall access being blocked, potentially affecting background services required by the game or blocking foreground applications.
By determining the activation status of the game acceleration session, the access authorization status of application usage information, and the usage context of dependent applications, the network traffic of dependent applications is dynamically controlled, allowing traffic to enter the acceleration tunnel only when preset conditions are met and the dependent application is in the background.
This achieves isolation between the normal operation of application background services and the traffic used in the foreground, improving the reliability and security of traffic control and reducing the risk of accidental traffic release.
Smart Images

Figure CN123123409A_ABST
Abstract
Description
Technical Field
[0001] This invention relates to the field of game acceleration technology, and more specifically, to a method and system for controlling the flow of application traffic in game acceleration scenarios. Background Technology
[0002] With the development of game acceleration technology, terminals can establish acceleration tunnels through virtual private network interfaces or virtual network device interfaces to direct the network traffic of the target game application to the acceleration node, thereby reducing network latency and improving network quality.
[0003] Some games rely on other applications, such as app stores, to provide background services like account login, in-app billing, update checks, push notifications, or service handshakes. Some network traffic generated by these dependent applications is related to the normal operation of the game, but these dependent applications themselves can also be used directly by users in the foreground.
[0004] Existing solutions typically employ a uniform control strategy for traffic to dependent applications based on their identity. Allowing all traffic to pass through the game acceleration tunnel could allow foreground traffic of dependent applications to enter the game acceleration tunnel, while blocking all traffic could affect background services required by the game. Therefore, existing technologies struggle to differentiate network traffic control based on the actual usage scenarios of dependent applications. Summary of the Invention
[0005] The purpose of this invention is to provide a method and system for controlling the flow of application traffic in a game acceleration scenario.
[0006] In a first aspect, embodiments of the present invention provide a method for allowing access to applications that rely on traffic in a game acceleration scenario, comprising: In response to an acceleration request for a target game application, determine the dependent applications associated with the target game application and determine the activation status of the dependent traffic control function for the current acceleration session. In the current acceleration session, network traffic to be processed is identified based on application identity information. When it is identified that the network traffic to be processed belongs to the dependent application, the access authorization status for the application usage information recorded by the terminal system is obtained. When the access authorization status is authorized, the application usage information is obtained, the recently used application is determined based on the application usage information, and the usage context of the dependent application is determined as foreground, background or unknown based on the correspondence between the recently used application and the dependent application. The pending network traffic is controlled based on the activation state, the access authorization state, and the usage context. When the activation state is activated, the access authorization state is authorized, and the usage context is in the background state, a pass result is generated and the pending network traffic is allowed to enter the acceleration tunnel. When the activation state is inactive, the access authorization state is unauthorized, or the usage context is not in the background state, a block result is generated and the pending network traffic is prevented from entering the acceleration tunnel.
[0007] In one possible implementation, determining the activation status of the current acceleration session's dependent flow control function includes: Obtain explicit activation information for the target game application, a set of application package names distributed by the server, and the terminal installation status of the dependent applications; According to the pre-configured logical relationship, the explicit activation information, whether the application package name set contains the application package name corresponding to the dependent application, and the terminal installation status are combined and judged to obtain the activation judgment result; When the activation judgment result indicates that the activation conditions of the dependent traffic control function are met, the dependent application is included in the release set of the current acceleration session and an activated state is output. When the activation judgment result indicates that the activation conditions of the dependent traffic control function are not met, an inactive state is output to obtain the activation state.
[0008] In one possible implementation, the identification of network traffic to be processed based on application identity information includes: Obtain the application identity identifier corresponding to the network traffic to be processed, wherein the application identity identifier includes the application UID; The application generating the network traffic to be processed is determined based on the application identity, and the application generating the network traffic to be processed is matched with the dependent application; When a match is successful, the network traffic to be processed is determined to belong to the dependent application, and the dependent traffic identification result is output.
[0009] In one possible implementation, the step of determining the most recently used application based on the application usage information, and determining the usage context of the dependent application as a foreground state, background state, or unknown state based on the correspondence between the most recently used application and the dependent application, includes: The terminal system's usage statistics service is invoked to obtain the application usage information, which includes the application identifier and usage time information. When the application usage information is valid, the most recently used application is determined based on the usage time information; When the most recently used application is the dependent application, the usage context is determined to be in the foreground state; When the recently used application is an application other than the dependent application, the usage context is determined to be in a background state; If no application usage information is available or the usage time information is invalid, the usage context is determined to be in an unknown state in order to obtain the usage context.
[0010] In one possible implementation, controlling the network traffic to be processed based on the activation state, the access authorization state, and the usage context includes: When the activation state is activated, the access authorization state is authorized, and the usage context is background, the pass result is output. When any of the following occurs: the activation state is inactive, the access authorization state is unauthorized, the usage context is in the foreground state, the usage context is unknown, or the usage statistics service query fails, the blocking result is output to obtain the traffic control result for the network traffic to be processed.
[0011] In one possible implementation, after the output depends on the traffic identification result, it further includes: The dependent traffic identification results are sent to the application layer via a callback interface through the data plane. The activation state and the access authorization state are obtained through the application layer, and the usage context is determined when the access authorization state is authorized. The application layer generates a flow control result based on the activation state, the access authorization state, and the usage context, and returns the flow control result to the data plane. The data plane performs either allowing or blocking of the network traffic to be processed based on the flow control results.
[0012] In one possible implementation, the method further includes: When the access authorization status is unauthorized, maintain the current acceleration session and prevent pending network traffic corresponding to the dependent application from entering the acceleration tunnel; After the current accelerated session is successfully established, an authorization bootstrapping event is sent to the host application via an event callback. The authorization bootstrapping event is a non-error type event. The host application provides a guidance entry point for accessing usage authorization and a system authorization settings page entry point based on the authorization guidance event.
[0013] In one possible implementation, the dependent application is an app store application that provides background services to the target game application, the background services including at least one of account login, in-app billing, update checking, push notifications, and service handshake; the method further includes: When the usage context of the app store application is in the background and other conditions corresponding to the release result are met, the network traffic generated by the app store application is allowed to enter the acceleration tunnel. When the app store application is in a foreground state, prevent pending network traffic generated by the app store application from entering the acceleration tunnel.
[0014] In one possible implementation, after outputting the flow control result for the network traffic to be processed, the method further includes: When pending network traffic belonging to the dependent application is identified again, the access authorization status is re-acquired, and when the re-acquired access authorization status is authorized, the application usage information is re-acquired, and the recently used application and the usage context are re-determined based on the re-acquired application usage information. When the redefined usage context switches between a foreground state and a background state relative to the previously defined usage context, the flow control result is updated according to the redefined usage context; When the redefined usage context is a foreground state, the flow control result is updated to the blocking result; when the redefined usage context is a background state, the activation state is activated, and the re-acquired access authorization state is authorized, the flow control result is updated to the allowing result.
[0015] Secondly, embodiments of the present invention provide a control system for allowing access to applications that rely on traffic in a game acceleration scenario, including at least one terminal device; The terminal device includes a storage unit and a computing unit; the storage unit is used to store program code; the computing unit is used to run the program code to execute the application traffic-dependent access control method in the game acceleration scenario described in the first aspect.
[0016] Compared to existing technologies, the beneficial effects provided by this invention include: by combining the activation state of the current acceleration session, the access authorization state of application usage information, and the usage context of dependent applications, differentiated control is applied to network traffic generated by dependent applications. Traffic is allowed to enter the acceleration tunnel only when preset conditions are met and the dependent application is in the background. This ensures the normal operation of background dependent services such as target game login and billing while preventing traffic generated when dependent applications are used in the foreground by users from entering the game acceleration tunnel. Furthermore, the blocking strategy used when authorization is missing, the status is unknown, or the query fails helps reduce the risk of mistakenly allowing dependent traffic through, improving the reliability and security of traffic control. Attached Figure Description
[0017] To more clearly illustrate the technical solutions of the embodiments of the present invention, the accompanying drawings used in the embodiments will be briefly described below. It should be understood that the following drawings only show some embodiments of the present invention and should not be considered as limiting the scope. For those skilled in the art, other related drawings can be obtained based on these drawings without creative effort.
[0018] Figure 1 A flowchart illustrating the method for controlling the passage of applications in a game acceleration scenario, as provided in an embodiment of the present invention.
[0019] Figure 2 A schematic diagram of the functional architecture of a game acceleration control system that relies on application traffic, provided in an embodiment of the present invention.
[0020] Figure 3 A schematic block diagram of the structure of a computer device provided in an embodiment of the present invention. Detailed Implementation
[0021] To make the objectives, technical solutions, and advantages of the embodiments of the present invention clearer, the technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of the present invention. The components of the embodiments of the present invention described and shown in the accompanying drawings can generally be arranged and designed in various different configurations.
[0022] The specific embodiments of the present invention will now be described in detail with reference to the accompanying drawings.
[0023] In order to solve the technical problems mentioned in the background art Figure 1 This is a flowchart illustrating the method for controlling the flow of application traffic in a game acceleration scenario provided by an embodiment of the present invention. The following is a detailed description of this method for controlling the flow of application traffic in a game acceleration scenario.
[0024] Step S201: In response to the acceleration request for the target game application, determine the dependent applications associated with the target game application, and determine the activation status of the dependent traffic control function of the current acceleration session.
[0025] Step S202: In the current acceleration session, identify the network traffic to be processed based on the application identity information. When it is identified that the network traffic to be processed belongs to the dependent application, obtain the access authorization status for the application usage information recorded by the terminal system.
[0026] Step S203: When the access authorization status is authorized, obtain the application usage information, determine the recently used application based on the application usage information, and determine the usage context of the dependent application as foreground state, background state, or unknown state based on the correspondence between the recently used application and the dependent application.
[0027] Step S204: Control the network traffic to be processed according to the activation state, the access authorization state, and the usage context. When the activation state is activated, the access authorization state is authorized, and the usage context is in the background state, generate a pass result and allow the network traffic to be processed to enter the acceleration tunnel. When the activation state is not activated, the access authorization state is not authorized, or the usage context is not in the background state, generate a block result and prevent the network traffic to be processed from entering the acceleration tunnel.
[0028] In one specific implementation, the method for controlling the passage of application traffic in the game acceleration scenario provided in this embodiment can be executed by a terminal device. Specifically, the terminal device may have a terminal acceleration SDK installed. The terminal acceleration SDK is used to respond to game acceleration requests initiated by the host application or other callers, establish a corresponding acceleration session for the target game application, and identify and process network traffic entering the virtual private network interface, TUN interface, or other virtual network interfaces.
[0029] The terminal acceleration SDK may include an application layer and a data plane. The application layer is primarily used for policy judgment and control related to the current acceleration session, including obtaining the activation status of the current acceleration session, obtaining the terminal's access authorization status for application usage information, querying application usage information recorded by the terminal system, determining the usage context of dependent applications, and generating traffic control results. The data plane is primarily used for identifying network traffic based on application identity information and performing corresponding traffic allowance or blocking operations based on the traffic control results returned by the application layer.
[0030] In addition to generating its own network traffic during operation, the target game application may also call upon or rely on background network services provided by other applications. For example, some games require app stores or related dependent applications to provide background services such as account login, in-app billing, update checks, push notifications, or service handshakes. The network traffic generated by these dependent applications is related to the normal operation of the target game, but these dependent applications themselves can be directly opened and used in the foreground by the user.
[0031] Therefore, if all network traffic of dependent applications is simply allowed to pass through based on application identity, network traffic generated when users directly use dependent applications in the foreground may also enter the acceleration tunnel corresponding to the target game; if all network traffic of dependent applications is blocked, the backend services required by the target game, such as login and billing, may not function properly.
[0032] Based on this, this embodiment does not simply implement static overall allow or block on dependent applications according to application identity. Instead, after confirming that the network traffic to be processed belongs to the dependent application corresponding to the target game, it further combines the usage context of the dependent application at the current moment or during the current network traffic generation period to perform dynamic control, thereby differentiating the network traffic generated by the same dependent application when it is used as a background dependency of the target game and when it is used as a target in the foreground by the user.
[0033] Specifically, after receiving an acceleration request for a target game application, the terminal acceleration SDK can determine one or more dependent applications corresponding to the target game application based on pre-established or acquired application association information. This application association information is used to characterize the business dependencies between the target game application and other applications.
[0034] In some implementations, the application association information may be configured at least partially by the server and sent to the terminal. For example, the server may send a set of dependent application package names configured for the target game application to the terminal acceleration SDK, and the terminal acceleration SDK determines the dependent applications associated with the target game application based on the corresponding configuration information.
[0035] The terminal acceleration SDK, while identifying dependent applications, further determines whether the dependent traffic control function corresponding to the current acceleration session is active. This active state indicates whether the current acceleration session has enabled context-based traffic control for dependent applications. This associates traffic control for dependent applications with the acceleration session corresponding to the current target game, rather than applying a fixed network processing strategy to the dependent application on the terminal.
[0036] During the current accelerated session, the terminal acceleration SDK's data plane identifies the application source of the network traffic to be processed based on application identity information. When the identified network traffic belongs to the target game itself, it can be processed according to the target game's established acceleration strategy.
[0037] When the data plane identifies that the network traffic to be processed belongs to a dependent application associated with the target game, the data plane generates a dependent traffic identification result and triggers the subsequent judgment process for the usage context of that dependent application.
[0038] After receiving the dependency traffic identification result for the dependent application, the application layer obtains the access authorization status of the terminal for the application usage information recorded by the system. The access authorization status indicates whether the terminal acceleration SDK has obtained permission to access the terminal system's application usage information.
[0039] When the access authorization status is authorized, the application layer obtains application usage information through the usage statistics service provided by the terminal system, and determines the most recently used application based on the application usage information.
[0040] The application layer further compares the recently used application with the aforementioned dependent applications to determine the current usage context of the dependent application.
[0041] When the recently used application corresponds to the dependent application, it indicates that the user currently has the characteristic of directly using the dependent application, and therefore the usage context of the dependent application is determined to be the foreground state.
[0042] When the recently used application is an application other than the dependent application, such as the target game application that is currently being accelerated, it indicates that the dependent application is not the main application that the user is currently directly operating, and the usage context of the dependent application can be determined to be in the background state.
[0043] When there is no available application usage information, the corresponding usage time information is invalid, the query using the statistics service fails, or the existing information is insufficient to form a reliable front-end / back-end judgment, the dependent application is not directly presumed to be in a background state, but its usage context is determined to be an unknown state.
[0044] The above processing can distinguish network traffic generated by the same dependent application in different usage scenarios, instead of simply allowing all traffic of the dependent application as a whole based on its application identity.
[0045] After obtaining the activation status of the current accelerated session, the access authorization status of the terminal, and the usage context of the dependent applications, the application layer combines the above information to determine the traffic control result for the network traffic to be processed.
[0046] When the current accelerated session's dependent flow control function is activated, the terminal's access authorization status for application usage information is authorized, and the dependent application's usage context is determined to be in the background state, the application layer generates a release result and returns the release result to the data plane.
[0047] Based on the release result, the data plane allows the corresponding pending network traffic to enter the acceleration tunnel corresponding to the current target game, so that when the dependent application provides account login, in-app billing or other background services for the target game in the background, the corresponding network communication can proceed normally along with the acceleration process of the target game.
[0048] Conversely, in cases where the dependent flow control function is not activated, the access authorization status is unauthorized, the usage context of the dependent application is in the foreground state, the usage context of the dependent application is unknown, or the usage context of the dependent application cannot be reliably determined, the application layer generates a blocking result and returns the blocking result to the data plane.
[0049] Based on the blocking results, the data plane prevents the corresponding network traffic to be processed from entering the acceleration tunnel corresponding to the current target game.
[0050] Through the above processing, this embodiment uses the actual usage context of the dependent application as an important factor in traffic control, and realizes differentiated control between the background service traffic of the dependent application and the foreground traffic of the dependent application itself. While ensuring the availability of the background dependent services required by the target game, it reduces the possibility that the foreground traffic of the dependent application itself will be inappropriately included in the game acceleration tunnel.
[0051] In this embodiment of the invention, determining the activation status of the current acceleration session's dependent flow control function includes: Obtain explicit activation information for the target game application, a set of application package names distributed by the server, and the terminal installation status of the dependent applications; According to the pre-configured logical relationship, the explicit activation information, whether the application package name set contains the application package name corresponding to the dependent application, and the terminal installation status are combined and judged to obtain the activation judgment result; When the activation judgment result indicates that the activation conditions of the dependent traffic control function are met, the dependent application is included in the release set of the current acceleration session and an activated state is output; when the activation judgment result indicates that the activation conditions of the dependent traffic control function are not met, an inactive state is output to obtain the activated state.
[0052] In one specific implementation, after receiving an acceleration request for a target game application and identifying the dependent applications associated with the target game application, the terminal acceleration SDK further determines whether the current acceleration session meets the activation conditions for enabling background traffic access for the dependent applications.
[0053] For example, if the target game requires an app store or other dependent applications to provide backend services such as login and billing during operation, the terminal acceleration SDK will identify the corresponding application as a dependent application.
[0054] The terminal acceleration SDK obtains explicit enabling information for the target game application. This explicit enabling information indicates whether the host application, the caller, or the current acceleration configuration has explicitly enabled the background traffic allowance capability for the dependent application when establishing an acceleration session for the target game application.
[0055] Meanwhile, the terminal acceleration SDK obtains the set of application package names issued by the server for the current target game or the current acceleration service, and determines whether the set of application package names contains the application package name corresponding to the aforementioned dependent application.
[0056] In addition, the terminal acceleration SDK also obtains the installation status of the dependent applications on the current terminal to determine whether the corresponding dependent applications have been actually installed on the current terminal.
[0057] After obtaining the above information, the terminal acceleration SDK performs a combined judgment based on pre-configured logical relationships. These logical relationships are used to limit the gating conditions that must be met for the current acceleration session to enable the traffic control-dependent function.
[0058] For example, in one implementation, when the explicit enable information for the current target game indicates that it is enabled, the set of application package names issued by the server includes the application package name corresponding to the dependent application, and the terminal installation status of the dependent application indicates that the dependent application is installed, the terminal acceleration SDK generates an activation judgment result that meets the enable conditions, includes the dependent application in the release set corresponding to the current acceleration session, and sets the activation status of the dependent flow control function to activated.
[0059] It should be noted that including a dependent application in the current acceleration session's allowable set does not mean that all network traffic generated by that dependent application will unconditionally enter the acceleration tunnel. Rather, it means that when traffic from the corresponding dependent application is subsequently identified, that traffic is eligible to further enter the usage context judgment process. Whether the corresponding pending network traffic ultimately enters the acceleration tunnel still needs to be further determined based on the access authorization status and the usage context of the dependent application.
[0060] When the above gating conditions are not met, the terminal acceleration SDK generates an activation judgment result indicating that the activation conditions are not met, and determines the dependent flow control function of the current acceleration session as inactive.
[0061] For example, if the target game application does not obtain the corresponding explicit activation information, the application package name corresponding to the dependent application does not exist in the application package name set issued by the server, or the corresponding dependent application is not installed on the terminal, the pre-configured gating conditions may not be met.
[0062] In this state, even if network traffic generated by the corresponding dependent application is subsequently identified, it will not be directly accelerated simply because the application has a business dependency relationship with the target game. Instead, a blocking result will be generated based on the inactive state to prevent the corresponding traffic from entering the acceleration tunnel corresponding to the target game.
[0063] Through the above processing, factors such as "whether the current target game has enabled this capability", "whether the server has configured the corresponding dependent application for the current business", and "whether the terminal has the corresponding dependent application environment" are jointly verified. The scope of application of the dependent traffic control function is limited from the current accelerated session establishment stage, reducing the possibility of erroneously enabling the background traffic allowance capability when there is no configuration, no activation, or no corresponding dependent application in the terminal.
[0064] In this embodiment of the invention, the identification of network traffic to be processed based on application identity information can be implemented through the following examples: Obtain the application identity identifier corresponding to the network traffic to be processed, wherein the application identity identifier includes the application UID; The application generating the network traffic to be processed is determined based on the application identity, and the application generating the network traffic to be processed is matched with the dependent application; When a match is successful, the network traffic to be processed is determined to belong to the dependent application, and the dependent traffic identification result is output.
[0065] In one specific implementation, the data plane of the terminal acceleration SDK processes the network traffic to be processed entering the virtual network interface during the current acceleration session, and identifies the actual application that generated the network traffic to be processed based on the application identity information.
[0066] In specific scenarios, when the target game is running, it needs app stores or other dependent apps to provide network services such as account login, in-app billing, or service handshake in the background. Therefore, some of the network traffic generated by the corresponding dependent apps needs to enter the subsequent dependent traffic control process.
[0067] The data plane first obtains the application identity identifier corresponding to the network traffic to be processed. This application identity identifier may include the application UID. The application UID can be assigned by the terminal system for the corresponding application and is used to represent the application entity that generated the corresponding network connection or network data.
[0068] The data plane determines the application that generated the network traffic to be processed based on the application UID corresponding to the network traffic to be processed and the application identity mapping relationship maintained in the terminal.
[0069] For example, the data plane determines that the network traffic to be processed originates from an app store based on the application UID, and the current acceleration session has already recorded that the app store is a dependent application of the target game. The data plane further matches the traffic source application determined by the application UID with the dependent application corresponding to the current acceleration session.
[0070] The matching can be based on the application package name, application identifier, the mapping relationship between the application UID and the package name, or the dependent application information maintained in the current acceleration session.
[0071] This step links the two judgment processes of "which application generated the network traffic to be processed" and "whether the application that generated the corresponding traffic belongs to the dependent application of the current target game", without having to infer whether the network traffic belongs to the dependent application based solely on the network destination address, domain name, or traffic content of the network traffic to be processed.
[0072] When the data plane confirms that the application generating the network traffic to be processed matches the dependent application in the current acceleration session, the match is determined to be successful, and the dependent traffic identification result is generated.
[0073] The dependent traffic identification results can be used to trigger the application layer to further obtain access authorization status and determine the usage context of dependent applications.
[0074] In some implementations, the dependent traffic identification result may also include the current acceleration session identifier, dependent application identifier, or relevant information corresponding to the network traffic to be processed, so that the application layer can determine the specific acceleration session and dependent application corresponding to this policy judgment.
[0075] When the data plane determines that the application generating the corresponding network traffic is not a dependent application associated with the current acceleration session, it can be processed according to other traffic processing rules corresponding to its application identity, without entering the dynamic traffic control process for dependent applications in this embodiment.
[0076] Therefore, the data plane can filter out network traffic that truly needs to be dynamically released by the application based on application identity information such as application UID at the application identity level, providing a traffic identification basis for subsequent differentiated control based on access authorization status and usage context.
[0077] In this embodiment of the invention, the step of determining the most recently used application based on the application usage information, and determining the usage context of the dependent application as a foreground state, background state, or unknown state based on the correspondence between the most recently used application and the dependent application, can be implemented through the following example:
[0078] The terminal system's usage statistics service is invoked to obtain the application usage information, which includes the application identifier and usage time information. When the application usage information is valid, the most recently used application is determined based on the usage time information; When the most recently used application is the dependent application, the usage context is determined to be in the foreground state; When the recently used application is an application other than the dependent application, the usage context is determined to be in a background state; If no application usage information is available or the usage time information is invalid, the usage context is determined to be in an unknown state in order to obtain the usage context.
[0079] In one specific implementation, after receiving the dependency traffic identification result from the data plane output in the current accelerated session and confirming that the terminal has granted the application access permission to use information, the application layer further determines the current usage context of the dependent application.
[0080] In a specific scenario, the target game needs to rely on the application to provide services such as account login and in-app billing in the background during its operation. The application layer calls the usage statistics service provided by the terminal system to obtain the application usage information recorded by the terminal system.
[0081] The application usage information may include at least an application identifier and usage time information corresponding to the application identifier. The application identifier is used to distinguish the target game application, dependent applications, and other applications on the terminal, while the usage time information reflects the time when each application was last used or entered a corresponding active state.
[0082] After obtaining the application usage information, the application layer first determines whether the application usage information is available.
[0083] If the application usage information contains an application identifier that can identify a specific application, and the usage time information corresponding to the corresponding application identifier is complete and valid, the application layer can compare the usage time of each application in chronological order, and determine the application whose usage time is closer to the current time or the most recent application as the most recently used application.
[0084] For example, if a user is currently playing a game within the target game application's interface, and the app store only handles login authentication or billing communication in the background, then the recent usage time of the target game application recorded in the terminal system is later than the recent usage time of the app store. The application layer can then identify the target game application as the most recently used application.
[0085] The application layer further compares the recently used application with the already identified dependent applications. Since the recently used application is the target game application rather than a dependent application, the usage context of the dependent application can be determined as a background state.
[0086] The background state indicates that the dependent application is not currently the main application that the user directly operates, but runs in the background, such as providing corresponding background services while the target game is running.
[0087] When a user switches from the target game app to a dependent app and directly opens the app store page, the app usage information recorded by the terminal system changes accordingly. The usage time corresponding to the dependent app becomes the most recent time among the usage times of multiple apps.
[0088] After the application layer obtains and compares the application usage information again, it determines the dependent application as the most recently used application and sets its usage context to the foreground state, indicating that the user currently has the characteristic of directly using the dependent application.
[0089] Furthermore, for situations where a reliable judgment cannot be made, this embodiment sets up an unknown state for separate handling.
[0090] For example, if the terminal system does not return available application usage information, the application identifier is missing, the usage time information is empty, there is an error or it cannot be compared, or the query using the statistics service fails, the dependent application is not directly presumed to be in the background state. Instead, its usage context is determined to be in an unknown state or it is handled according to the corresponding failure security path.
[0091] By setting foreground, background, and unknown states, it is possible to distinguish between clear foreground usage scenarios, clear background operation scenarios, and situations where the usage scenario cannot be reliably determined. This provides a state basis for subsequent actions to allow or block applications based on the usage context, and reduces the possibility of accidental approval when application usage information is unavailable.
[0092] In this embodiment of the invention, controlling the network traffic to be processed based on the activation state, the access authorization state, and the usage context can be implemented through the following examples: When the activation state is activated, the access authorization state is authorized, and the usage context is background, the pass result is output. When any of the following occurs: the activation state is inactive, the access authorization state is unauthorized, the usage context is in the foreground state, the usage context is unknown, or the usage statistics service query fails, the blocking result is output to obtain the traffic control result for the network traffic to be processed.
[0093] In one specific implementation, after the terminal acceleration SDK has identified the network traffic to be processed as belonging to the dependent application corresponding to the current target game through the data plane, the application layer further generates a traffic control result based on the activation status of the current acceleration session, the terminal's access authorization status for application usage information, and the usage context of the dependent application.
[0094] In this specific scenario, the target game relies on the app store to provide backend services such as account login and in-app billing. The terminal acceleration SDK has determined that the dependency traffic control function of the dependent application is activated based on the session configuration of the current target game, and the terminal has granted the terminal acceleration SDK the necessary usage access permissions to access the application's usage information.
[0095] The application layer determines the most recently used application as the current target game application rather than the dependent application based on the application usage information returned by the terminal system, and therefore determines the usage context of the dependent application as a background state.
[0096] At this point, the three conditions of activation, authorization, and background status are met simultaneously. The application layer generates a pass result and returns this pass result to the data plane as the flow control result for the current network traffic to be processed.
[0097] Based on the release result, the data plane allows the login authentication, billing requests, or other dependent service traffic generated by the dependent application in the background to enter the acceleration tunnel corresponding to the current target game, thereby ensuring that the target game can normally call the background network services provided by the dependent application.
[0098] If any of the above-mentioned conditions for allowing access are not met, the application layer will generate a blocking result using a failure-safe approach.
[0099] When the dependent traffic control function of the current acceleration session is inactive, the application layer generates a blocking result to prevent dependent application traffic that has not been confirmed by the current session's activation conditions from entering the acceleration tunnel.
[0100] When the terminal has not granted the application access to usage information, the application layer generates a blocking result because it cannot obtain reliable usage context information, instead of interpreting the lack of access authorization as the dependent application being in the background.
[0101] If the recently used application is determined to be a dependent application based on application usage information, the application layer determines its usage context as a foreground state and generates a blocking result. For example, when a user switches from a target game application to an app store application, the foreground access traffic generated by the app store itself will not be transmitted through the acceleration tunnel corresponding to the current target game.
[0102] When the application usage information obtained is insufficient to determine the foreground and background states of dependent applications, the corresponding usage context is determined to be an unknown state and a blocking result is generated.
[0103] When the usage statistics service on the terminal system fails to query, resulting in the inability to obtain valid application usage information, a blocking result is also generated.
[0104] Therefore, situations where the security conditions cannot be clearly met, such as inactivation, unauthorization, foreground status, unknown status, and failure to query using the statistics service, are uniformly included in the blocking path. This forms a failure security control mechanism that only allows dependent application traffic to enter the acceleration tunnel when the preset conditions are clearly met, and blocks it from entering the acceleration tunnel in other cases.
[0105] By using the above methods, while ensuring the availability of corresponding services when the dependent application is used as a background dependency of the target game, it is possible to avoid the accidental passage of traffic from the dependent application when it is used in the foreground, its status is unknown, or the system usage information is unavailable.
[0106] In this embodiment of the invention, after outputting the traffic identification result, the following example implementation can also be provided: The dependent traffic identification results are sent to the application layer via a callback interface through the data plane. The activation state and the access authorization state are obtained through the application layer, and the usage context is determined when the access authorization state is authorized. The application layer generates a flow control result based on the activation state, the access authorization state, and the usage context, and returns the flow control result to the data plane. The data plane performs either allowing or blocking of the network traffic to be processed based on the flow control results.
[0107] In one specific implementation, the terminal acceleration SDK adopts a processing architecture that separates the data plane from the application layer.
[0108] The data plane is responsible for identifying the application identity of the network traffic to be processed, and for performing operations to allow or block the corresponding traffic from entering the acceleration tunnel based on the traffic control results returned by the application layer. The application layer is responsible for making a comprehensive judgment on the current acceleration session state, access authorization state, dependent application usage context, and traffic control policy.
[0109] After determining that the network traffic to be processed is generated by a dependent application associated with the current target game based on application identity information such as application UID, the data plane generates a dependency traffic identification result and sends the dependency traffic identification result to the application layer through a pre-established callback interface.
[0110] The dependent traffic identification result can carry the current acceleration session identifier, dependent application identifier, and information related to the network traffic to be processed, enabling the application layer to determine the specific acceleration session and dependent application corresponding to this policy judgment.
[0111] After receiving the dependency traffic identification result, the application layer first obtains the activation status of the dependency traffic control function corresponding to the current acceleration session, and then obtains the terminal's access authorization status for application usage information.
[0112] When the current access authorization status is authorized, the application layer further calls the terminal system's usage statistics service to obtain application usage information, and determines the usage context of the dependent application based on the correspondence between the recently used application and the dependent application.
[0113] For example, if the target game is currently in the user's interface, while the dependent application is only performing login authentication or billing communication in the background, the application layer determines the usage context of the dependent application as a background state.
[0114] When a user switches to and directly opens a dependent application, the application layer determines its usage context as a foreground state.
[0115] When reliable application usage information cannot be obtained, the corresponding usage context will be determined as unknown.
[0116] When the current access authorization status is unauthorized, the application layer does not infer that the dependent application is in the background based on the missing application usage information, but directly enters the corresponding failure security decision path.
[0117] Subsequently, the application layer combines the activation status, access authorization status, and usage context to generate traffic control results for the network traffic to be processed.
[0118] When the current accelerated session is active, the access authorization status is authorized, and the usage context of the dependent application is in the background, the application layer generates a release result.
[0119] In cases where the application is not activated, not authorized, in a foreground state, in an unknown state, or where the usage context cannot be reliably determined, the application layer generates a blocking result.
[0120] After the application layer completes the policy judgment, it returns the flow control result to the data plane through the corresponding interface.
[0121] After receiving a pass-through result, the data plane allows the corresponding pending network traffic to enter the acceleration tunnel corresponding to the current target game; after receiving a block result, it prevents the corresponding pending network traffic from entering the acceleration tunnel corresponding to the current target game.
[0122] By using the above processing method, "identifying which application generated the network traffic to be processed" and "determining whether the corresponding network traffic to be processed can enter the acceleration tunnel" are divided into different processing levels.
[0123] The data plane does not need to handle usage access authorization queries and complex usage context judgment logic, and the application layer does not need to directly handle the underlying data forwarding processing. This forms a control closed loop that connects traffic identification, policy decision-making, and traffic execution, and facilitates subsequent independent adjustment of dependent traffic control policies without changing the underlying application traffic identification mechanism of the data plane.
[0124] In this embodiment of the invention, the following implementation methods are also provided: When the access authorization status is unauthorized, maintain the current acceleration session and prevent pending network traffic corresponding to the dependent application from entering the acceleration tunnel; After the current accelerated session is successfully established, an authorization bootstrapping event is sent to the host application via an event callback. The authorization bootstrapping event is a non-error type event. The host application provides a guidance entry point for accessing usage authorization and a system authorization settings page entry point based on the authorization guidance event.
[0125] In one specific implementation, the terminal acceleration SDK obtains the terminal's access authorization status for application usage information during the establishment and operation of the current acceleration session.
[0126] If the target game has successfully entered the acceleration state, but the terminal has not yet granted access permissions, the terminal acceleration SDK will not terminate the current acceleration session corresponding to the target game due to the lack of such permissions, nor will it treat the lack of such permissions as a failure to establish acceleration for the target game. Instead, it will continue to maintain the target game's own acceleration link, so that the target game's own network traffic can still be processed according to the established acceleration strategy.
[0127] Meanwhile, since the application layer cannot obtain reliable application usage information without the corresponding access authorization, and cannot further reliably determine whether the dependent application is currently in the foreground or background state based on the application usage information, according to the failure security policy, a blocking result is generated for the network traffic of the identified dependent applications to be processed, and the data plane is used to prevent this part of the traffic from entering the acceleration tunnel corresponding to the current target game.
[0128] Therefore, the lack of access authorization only affects the conditional passage of traffic dependent on the application, and does not affect the overall acceleration service already established for the target game.
[0129] After the current acceleration session is successfully established, the terminal acceleration SDK can further determine whether the authorization boot event has been triggered in this acceleration session.
[0130] If it is determined that the authorization boot event has not been triggered in this acceleration session, the terminal acceleration SDK sends an authorization boot event to the host application through a pre-set event callback channel.
[0131] The authorization guidance event is a non-error type event, used to indicate to the host application that the current dependent traffic control function is in a restricted state due to a lack of usage access authorization, rather than to indicate that the target game acceleration has failed, the network is abnormal, or the acceleration service has encountered an error.
[0132] Therefore, after receiving the authorization guidance event, the host application does not need to close the current acceleration session, nor does it need to treat the event as a game acceleration failure event.
[0133] In some implementations, the authorization bootstrapping event is triggered only once for the same acceleration session, thereby avoiding repeated authorization prompts that could disrupt the user's normal gaming experience when dependent applications are continuously generating network traffic.
[0134] After receiving the authorization guidance event, the host application can determine the timing and interface for displaying the authorization guidance to the user based on actual business needs, and can provide an entry point for accessing the authorization settings page of the terminal system usage status.
[0135] After entering the system settings through the corresponding portal, users can complete the access authorization for application usage information.
[0136] When the terminal acceleration SDK processes the pending network traffic corresponding to the dependent application again, it re-obtains the current access authorization status of the terminal.
[0137] If the access authorization status is still unauthorized, continue to maintain the acceleration session corresponding to the current target game and prevent dependent application traffic from entering the corresponding acceleration tunnel.
[0138] After the access authorization status has been changed to authorized, the application layer further obtains application usage information, re-determines the usage context of the dependent application based on the application usage information, and generates corresponding allow or block results based on the re-obtained activation status, access authorization status and usage context.
[0139] By adopting the above approach, a closed-loop processing mechanism is formed, which consists of "maintaining target game acceleration - blocking traffic degradation of dependent applications - one-time non-error event guidance - restoring usage context judgment after authorization". This reduces the risk of mistakenly allowing traffic to pass due to the inability to judge the usage context of dependent applications while maintaining the continuity of target game acceleration.
[0140] In this embodiment of the invention, the dependent application can be an app store application that provides background services to the target game application, and the background services include at least one of account login, in-app billing, update checking, push notifications, and service handshake.
[0141] Accordingly, the method may further include: When the usage context of the app store application is in the background and other conditions corresponding to the release result are met, the network traffic generated by the app store application is allowed to enter the acceleration tunnel. When the app store application is in a foreground state, prevent pending network traffic generated by the app store application from entering the acceleration tunnel.
[0142] In one specific implementation, the app store application that provides background network services to the target game application is identified as the dependent application.
[0143] In specific scenarios, the target game may need to call one or more background services provided by the app store during the terminal operation, such as account login, in-app billing, update check, message push, and service handshake.
[0144] Taking the example of a target game relying on Google Play for account authentication and in-app billing services, while the user keeps the target game running in the foreground, Google Play is not directly opened by the user, but background services related to Google Play may still generate network communications corresponding to account authentication, in-app billing, or other related services.
[0145] Once the terminal acceleration SDK identifies that the network traffic in the current acceleration session is generated by the corresponding dependent application of Google Play, it not only processes it based on the application's identity, but also further determines whether the network traffic meets the conditions for entering the current target game acceleration tunnel by combining the application layer with the current usage context of Google Play.
[0146] When the application layer determines that the most recently used application is the target game, rather than Google Play, based on the application usage information recorded by the terminal system, the usage context of Google Play is set to background.
[0147] At this point, the application layer further checks other allow conditions, including whether the current acceleration session's dependent flow control function is activated, and whether the terminal's access authorization status for application usage information is authorized.
[0148] When the usage context is in a background state and other allow conditions are met simultaneously, the application layer generates an allow result and returns the allow result to the data plane.
[0149] Based on the release result, the data plane allows pending network traffic generated by the corresponding dependent application of Google Play to enter the acceleration tunnel corresponding to the current target game.
[0150] Therefore, when the target game initiates account login or in-app purchase, the relevant network communication generated by the dependent application's backend can enter the corresponding acceleration tunnel, thereby avoiding login failure, billing failure, or other dependent service abnormalities caused by the overall blocking of the dependent application.
[0151] During the operation of the target game, when the user switches from the target game and directly opens Google Play, when the terminal acceleration SDK subsequently identifies the pending network traffic generated by the corresponding dependent application of Google Play again, the application layer determines that the recently used application has changed to Google Play based on the application usage information obtained again, thereby determining its usage context as the foreground state.
[0152] The application layer generates a blocking result based on the foreground state and returns the blocking result to the data plane.
[0153] Based on this, the data layer prevents pending network traffic generated by the corresponding dependent application of Google Play from entering the acceleration tunnel corresponding to the target game, so that the front-end traffic generated when the user directly browses the app store, searches for apps, or visits the app store page cannot be transmitted through the acceleration tunnel corresponding to the current target game.
[0154] In this way, the same dependent application can be allowed to pass when it is used as a background service dependency of the target game, provided that the corresponding conditions are met, but it will be blocked when it is used directly by the user as a foreground application. This achieves differentiated control of network traffic for applications with the same identity but different usage contexts.
[0155] In this embodiment of the invention, after outputting the flow control result for the network traffic to be processed, the following example implementation can also be provided: When pending network traffic belonging to the dependent application is identified again, the access authorization status is re-acquired, and when the re-acquired access authorization status is authorized, the application usage information is re-acquired, and the recently used application and the usage context are re-determined based on the re-acquired application usage information. When the redefined usage context switches between a foreground state and a background state relative to the previously defined usage context, the flow control result is updated according to the redefined usage context; When the redefined usage context is a foreground state, the flow control result is updated to the blocking result; when the redefined usage context is a background state, the activation state is activated, and the re-acquired access authorization state is authorized, the flow control result is updated to the allowing result.
[0156] In one specific implementation, after the terminal acceleration SDK has output a pass or block result for a pending network traffic of a dependent application, it does not use the result as a fixed control policy for the entire current acceleration session. Instead, when pending network traffic belonging to the same dependent application is identified again, the corresponding status judgment is re-executed to adapt to the changes in usage context caused by the user switching between the target game application and the dependent application.
[0157] For example, during the operation of the target game, the app store is relied upon to provide backend services such as account login and in-app billing for the target game.
[0158] The terminal acceleration SDK previously determined the most recently used application as the target game based on the application usage information returned by the terminal system, and set the application store's usage context to a background state.
[0159] If the current accelerated session is active and the access authorization status is authorized, the application layer generates a pass result for the corresponding app store traffic, and the data plane allows the corresponding traffic to enter the accelerated tunnel.
[0160] As the current accelerated session continues to run, when the data plane identifies new network traffic belonging to the dependent application based on the application identity information, it sends the new dependent traffic identification result to the application layer through a callback interface.
[0161] The application layer retrieves the current access authorization state of the terminal instead of directly using the previously obtained access authorization state.
[0162] If the access authorization status is still authorized after being re-acquired, the application layer obtains the latest application usage information again through the terminal system's usage statistics service, and re-determines the most recently used application based on the application identifier and usage time information in the application usage information, and then re-determines the current usage context of the dependent application.
[0163] For example, if a user has switched from the target game to the app store and is directly browsing the app store page, and the recently used application recorded by the terminal system changes from the target game to the app store, the application layer can determine that the usage context of the dependent application has changed from the previous background state to the foreground state.
[0164] When the application layer detects a switch between foreground and background states between the redefined usage context and the previously defined usage context, it updates the corresponding traffic control results based on the latest usage context.
[0165] When the app store switches from a background state to a foreground state, the application layer will update the traffic control results for subsequent applications that depend on the application's traffic to the blocking results, and return the blocking results to the data plane.
[0166] Based on this, the data layer prevents subsequent pending network traffic generated by the app store from entering the acceleration tunnel corresponding to the target game, thereby preventing users from continuing to use the previously allowed results for background dependency scenarios when directly using dependent applications.
[0167] When the user completes the app store operation and returns to the target game, the data plane, upon recognizing new network traffic to be processed generated by the dependent application again, sends the dependent traffic recognition result to the application layer once more.
[0168] The application layer regains access authorization status and the latest application usage information.
[0169] If the recently used application becomes the target game again, the application layer will redetermine the usage context of the app store from the foreground state to the background state.
[0170] While the current accelerated session is still active and the re-acquired access authorization status is still authorized, the application layer updates the corresponding flow control result to a pass result and returns the pass result to the data plane.
[0171] Based on this, the data allows the app store, as a backend dependency of the target game, to re-enter the acceleration tunnel corresponding to the current target game for login, billing, or other service traffic.
[0172] Therefore, by re-examining the access authorization status and usage context when traffic to dependent applications is subsequently re-identified, the traffic control results for dependent applications can change according to their actual usage status, rather than permanently using the existing results after a single judgment. This enables conditional access in the background, blocking in the foreground, and dynamic policy updates after switching between the foreground and background states.
[0173] To more clearly describe the technical solutions provided by the embodiments of the present invention, the following description, in conjunction with specific embodiments, further illustrates the method for controlling the passage of application-dependent traffic in game acceleration scenarios provided by the present invention.
[0174] Please refer to the following: Figure 2 , Figure 2 This is a schematic diagram of the functional architecture of a game acceleration control system that relies on application traffic, provided in an embodiment of the present invention.
[0175] This solution can be deployed in terminal devices using a terminal acceleration SDK.
[0176] The terminal acceleration SDK can include two layers: the application layer and the data plane. The application layer is used for policy judgment and control, while the data plane is used for network traffic identification and processing corresponding to VPN / TUN tunnels.
[0177] The overall approach of this solution is as follows: instead of statically allowing or blocking dependent applications based on their identity, dynamic traffic control is implemented based on "application identity + usage context" to distinguish the different traffic processing requirements when the dependent application is used as a background dependency of the target game and as a target for user use in the foreground.
[0178] Regarding application identification and session activation, the data plane identifies network traffic to be processed based on application identity information. For example, network traffic belonging to an app store or other dependent applications can be identified based on the application's UID.
[0179] Whether to enable background traffic access for the corresponding dependent applications can be determined by multiple activation conditions, including explicit enable information for the currently accelerated target game, whether the application package name set distributed by the server contains the application package name of the corresponding dependent application, and whether the corresponding dependent application has been installed on the current terminal.
[0180] Once the pre-set gating conditions are met, the dependency traffic control function of the current acceleration session is activated, and the corresponding dependent applications are included in the allow set of the current acceleration session.
[0181] If the corresponding gating conditions are not met, the dependent flow control function will not be activated, and the corresponding control will be performed as if the dependent application flow is inactive when it is subsequently identified.
[0182] In terms of front-end and back-end status determination, when the data plane identifies pending network traffic belonging to dependent applications, it notifies the application layer of the dependent traffic identification result through a callback interface.
[0183] Once the application layer has obtained authorization to access usage information, it calls the terminal system's usage statistics service to obtain application usage information and determines the most recently used application based on the application usage information.
[0184] When the most recently used application is the dependent application, it indicates that the user currently has the characteristic of directly using the dependent application in the foreground, and therefore its usage context is determined to be in the foreground state.
[0185] When the recently used application is another application, such as the target game application that is currently being accelerated, the usage context of the dependent application is determined to be in the background state.
[0186] If there is no available application usage information, the corresponding usage time information is invalid, or the query using the statistics service fails and cannot be reliably determined, the usage context of the dependent application will be determined to be unknown or the corresponding failure safety path will be entered.
[0187] In terms of flow control, this solution adopts a failure-safe strategy.
[0188] A pass result is generated only when all three conditions are met simultaneously: the current acceleration session is activated, usage access authorization has been obtained, and the usage context of the dependent application is determined to be in the background state. In this case, the data plane allows the pending network traffic generated by the corresponding dependent application to enter the acceleration tunnel corresponding to the current target game.
[0189] If any of the above conditions are not met, including if the current acceleration session is not active, if usage access authorization is not obtained, if the dependent application is determined to be in the foreground state, if the dependent application is determined to be in an unknown state, or if the query using the statistics service fails, a blocking result will be generated, and the data plane will prevent the corresponding pending network traffic from entering the acceleration tunnel corresponding to the current target game.
[0190] By employing the above methods, when access authorization is missing, usage statistics are unavailable, or the foreground / background status cannot be reliably determined, dependent applications will not be directly presumed to be in the background, nor will their network traffic be allowed to enter the acceleration tunnel by default. This forms a failure security control method that "allows traffic only when the conditions for allowing traffic are clearly met, and blocks traffic when the conditions for reliability cannot be determined."
[0191] The data plane is primarily responsible for identifying network traffic based on application identity and notifying the application layer via callback interfaces after identifying traffic from dependent applications.
[0192] The application layer obtains the current activation status, usage access authorization status, and usage context of the dependent applications of the current acceleration session, and determines the corresponding allow or block policy based on the above information, and then returns the traffic control result to the data plane.
[0193] The data plane performs corresponding allow or block operations based on the flow control results returned by the application layer.
[0194] This achieves the separation of responsibilities between data plane traffic identification and application layer policy decision-making.
[0195] If the user has not granted access permissions for usage, this solution will not interrupt the acceleration process of the current target game. Instead, it will prevent the traffic corresponding to the dependent application from entering the acceleration tunnel corresponding to the current target game, and will send an authorization guidance event to the host application through the existing event callback after the current acceleration session is successfully established.
[0196] The authorization guidance event can be a non-error type event.
[0197] After receiving the authorization guidance event, the host application can determine the timing and interface for displaying the authorization guidance to the user based on actual needs, and can provide an entry point to access the system usage access authorization settings page.
[0198] This method enables the acceleration of the target game to be uninterrupted and the traffic of dependent applications to be controlled for failures when the corresponding access permissions are lacking, and forms a closed loop of subsequent authorization through a one-time authorization guide.
[0199] The overall information processing flow of this solution may include: First, receive acceleration requests for the target game application and identify the dependent applications associated with the target game application; The system determines whether the current acceleration session meets the activation conditions based on the explicit activation information, the configuration information of dependent applications issued by the server, and the terminal installation status of the dependent applications. When the corresponding activation conditions are met, activate the dependent traffic control function for the current acceleration session; During the current accelerated session, the data plane identifies the network traffic to be processed based on application identity information such as application UID; When it is identified that the network traffic to be processed belongs to a dependent application, the dependent traffic identification result is sent to the application layer through a callback interface; The application layer obtains the usage and access authorization status. When the access authorization status is authorized, the application layer calls the terminal system's usage statistics service to obtain application usage information, and determines the usage context of recently used applications and dependent applications based on the application usage information. If the current acceleration session is already active, the access authorization status is authorized, and the dependent application is in the background, the application layer generates a pass result and returns it to the data plane, which then allows the corresponding network traffic to be processed to enter the acceleration tunnel corresponding to the target game. If the current acceleration session is not active, the access authorization status is unauthorized, the dependent application is in the foreground, the dependent application is in an unknown state, or the usage context cannot be reliably obtained, the application layer generates a blocking result and returns it to the data plane, which then blocks the corresponding network traffic to be processed from entering the acceleration tunnel corresponding to the target game.
[0200] For example, when the terminal acceleration SDK is applied to overseas game acceleration scenarios, the target game being accelerated needs to rely on Google Play related applications to provide background services such as in-app billing and account login during operation.
[0201] After the user starts the game acceleration and enables the background dependency traffic allowance, the terminal acceleration SDK obtains the dependency application configuration issued by the server for the current target game and detects that the corresponding dependency application has been installed on the current terminal.
[0202] After the corresponding gating conditions are met, the terminal acceleration SDK activates the dependent flow control function of the current acceleration session.
[0203] During game operation, the data plane identifies the pending network traffic generated by the corresponding dependent application of Google Play based on the application identity information, and sends the dependent traffic identification results back to the application layer.
[0204] The user is currently running the target game in the foreground.
[0205] Having already obtained access authorization for usage information, the application layer calls the terminal system's usage statistics service to obtain application usage information and determines that the most recently used application is the target game rather than the corresponding dependent application on Google Play. Therefore, the usage context of the corresponding dependent application on Google Play is determined to be in the background state.
[0206] With the current acceleration session already activated and usage access authorization granted, the application layer generates a release result. Based on the release result, the data plane allows background traffic generated by the corresponding dependent application of Google Play to enter the acceleration tunnel corresponding to the current target game, enabling functions such as login and billing in the target game to function normally.
[0207] When a user switches from the target game and directly opens Google Play, the data plane will notify the application layer of the new dependency traffic identification results when it subsequently identifies traffic from the corresponding dependent application.
[0208] The application layer retrieves the application usage information again and determines that the recently used application has changed to the corresponding dependent application on Google Play, thus setting its usage context as the foreground state.
[0209] The application layer generates a blocking result based on this, and the data plane uses the blocking result to prevent pending network traffic generated by the corresponding dependent application of Google Play from entering the acceleration tunnel corresponding to the current target game.
[0210] If a user does not grant usage access permissions, the acceleration session corresponding to the current target game will not be interrupted. Instead, traffic to the corresponding dependent application on Google Play will be blocked for failure. After the current acceleration session is successfully established, the user will be guided to complete the usage access authorization through a non-error type event.
[0211] By using the above methods, when a dependent application is used as a background dependency of a target game, its necessary network traffic can be allowed to enter the acceleration tunnel corresponding to the current target game under certain conditions, so as to ensure the normal use of background services such as in-game purchases and logins. When the dependent application is used directly by the user as a foreground target, its corresponding network traffic is blocked from entering the acceleration tunnel corresponding to the target game, so as to prevent foreground traffic that should not enter the corresponding acceleration tunnel from being allowed.
[0212] Meanwhile, a failure security strategy is adopted when access authorization is missing, data is unavailable, or the usage context cannot be reliably determined. The target game acceleration process is maintained even when access authorization is missing, and authorization is guided through a one-time event, thus balancing the availability of dependent services, the reliability of traffic control, and the continuity of the game acceleration process.
[0213] This invention also provides a computer device 100.
[0214] The computer device 100 can be a terminal device that executes the application traffic access control method in the aforementioned game acceleration scenario.
[0215] The computer device 100 includes a processor 112 and a memory 111 storing computer programs or computer instructions.
[0216] When the computer program or computer instructions are executed by the processor 112, the computer device 100 executes the application traffic-dependent access control method in the game acceleration scenario described in any of the foregoing embodiments.
[0217] like Figure 3 As shown, Figure 3This is a schematic diagram of the structure of a computer device 100 provided in an embodiment of the present invention. The computer device 100 may include a memory 111, a processor 112, and a communication unit 113. The memory 111, processor 112, and communication unit 113 may be directly or indirectly electrically connected to achieve data transmission or interaction. For example, the connection between the above components can be achieved through one or more communication buses or signal lines. The memory 111 may be used to store computer programs, computer instructions, and configuration data related to the current acceleration session. The processor 112 may be used to execute the computer programs or computer instructions stored in the memory 111 to achieve the aforementioned functions such as dependent application identification, access authorization status acquisition, application usage information processing, usage context judgment, and flow control. The communication unit 113 may be used for data communication between the computer device 100 and a server or other network devices, for example, receiving dependent application configuration information or a set of application package names issued by the server.
[0218] In some implementations, the aforementioned terminal acceleration SDK can run as a computer program or software functional module in the computer device 100. The terminal acceleration SDK may include an application layer functional module and a data plane functional module. The data plane functional module is used to identify network traffic to be processed based on application identity information and to perform corresponding network traffic processing according to the traffic control results generated by the application layer functional module. The application layer functional module is used to obtain the activation status and access authorization status of the current acceleration session, determine the usage context of dependent applications based on the application usage information recorded by the terminal system, and generate corresponding traffic control results based on the activation status, access authorization status, and usage context.
[0219] It should be noted that the terminal device described in the embodiments of the present invention can be an electronic device capable of running the target game application and the terminal acceleration SDK, and its specific hardware form does not constitute a limitation on the scope of protection of the present invention.
[0220] For illustrative purposes, the foregoing description has been made with reference to specific embodiments. However, the foregoing illustrative discussions are not intended to be exhaustive or to limit the present disclosure to the precise forms disclosed. Numerous modifications and variations are possible in accordance with the foregoing teachings. These embodiments were chosen and described in order to best illustrate the principles of the present disclosure and its practical application, thereby enabling those skilled in the art to best utilize the disclosure and to employ various embodiments with different modifications to suit a particular intended application.
Claims
1. A method for allowing access based on application traffic in a game acceleration scenario, characterized in that, include: In response to an acceleration request for a target game application, determine the dependent applications associated with the target game application and determine the activation status of the dependent traffic control function for the current acceleration session. In the current acceleration session, network traffic to be processed is identified based on application identity information. When it is identified that the network traffic to be processed belongs to the dependent application, the access authorization status for the application usage information recorded by the terminal system is obtained. When the access authorization status is authorized, the application usage information is obtained, the recently used application is determined based on the application usage information, and the usage context of the dependent application is determined as foreground, background or unknown based on the correspondence between the recently used application and the dependent application. The pending network traffic is controlled based on the activation state, the access authorization state, and the usage context. When the activation state is activated, the access authorization state is authorized, and the usage context is in the background state, a pass result is generated and the pending network traffic is allowed to enter the acceleration tunnel. When the activation state is inactive, the access authorization state is unauthorized, or the usage context is not in the background state, a block result is generated and the pending network traffic is prevented from entering the acceleration tunnel.
2. The method according to claim 1, characterized in that, Determining the activation status of the current acceleration session's dependent flow control functions includes: Obtain explicit activation information for the target game application, a set of application package names distributed by the server, and the terminal installation status of the dependent applications; According to the pre-configured logical relationship, the explicit activation information, whether the application package name set contains the application package name corresponding to the dependent application, and the terminal installation status are combined and judged to obtain the activation judgment result; When the activation judgment result indicates that the activation conditions of the dependent traffic control function are met, the dependent application is included in the release set of the current acceleration session and an activated state is output. When the activation judgment result indicates that the activation conditions of the dependent traffic control function are not met, an inactive state is output to obtain the activation state.
3. The method according to claim 1, characterized in that, The method of identifying network traffic to be processed based on application identity information includes: Obtain the application identity identifier corresponding to the network traffic to be processed, wherein the application identity identifier includes the application UID; The application generating the network traffic to be processed is determined based on the application identity, and the application generating the network traffic to be processed is matched with the dependent application; When a match is successful, the network traffic to be processed is determined to belong to the dependent application, and the dependent traffic identification result is output.
4. The method according to claim 1, characterized in that, The step of determining the most recently used application based on the application usage information, and determining the usage context of the dependent application as foreground, background, or unknown based on the correspondence between the most recently used application and the dependent application, includes: The terminal system's usage statistics service is invoked to obtain the application usage information, which includes the application identifier and usage time information. When the application usage information is valid, the most recently used application is determined based on the usage time information; When the most recently used application is the dependent application, the usage context is determined to be in the foreground state; When the recently used application is an application other than the dependent application, the usage context is determined to be in a background state; If no application usage information is available or the usage time information is invalid, the usage context is determined to be in an unknown state in order to obtain the usage context.
5. The method according to claim 4, characterized in that, The step of controlling the network traffic to be processed based on the activation state, the access authorization state, and the usage context includes: When the activation state is activated, the access authorization state is authorized, and the usage context is background, the pass result is output. When any of the following occurs: the activation state is inactive, the access authorization state is unauthorized, the usage context is in the foreground state, the usage context is unknown, or the usage statistics service query fails, the blocking result is output to obtain the traffic control result for the network traffic to be processed.
6. The method according to claim 3, characterized in that, Following the output of the traffic identification result, the following is also included: The dependent traffic identification results are sent to the application layer via a callback interface through the data plane. The activation state and the access authorization state are obtained through the application layer, and the usage context is determined when the access authorization state is authorized. The application layer generates a flow control result based on the activation state, the access authorization state, and the usage context, and returns the flow control result to the data plane. The data plane performs either allowing or blocking of the network traffic to be processed based on the flow control results.
7. The method according to claim 1, characterized in that, The method further includes: When the access authorization status is unauthorized, maintain the current acceleration session and prevent pending network traffic corresponding to the dependent application from entering the acceleration tunnel; After the current accelerated session is successfully established, an authorization bootstrapping event is sent to the host application via an event callback. The authorization bootstrapping event is a non-error type event. The host application provides a guidance entry point for accessing usage authorization and a system authorization settings page entry point based on the authorization guidance event.
8. The method according to claim 1, characterized in that, The dependent application is an app store application that provides background services to the target game application. The background services include at least one of account login, in-app billing, update checking, push notifications, and service handshake. The method further includes: When the usage context of the app store application is in the background and other conditions corresponding to the release result are met, the network traffic generated by the app store application is allowed to enter the acceleration tunnel. When the app store application is in a foreground state, prevent pending network traffic generated by the app store application from entering the acceleration tunnel.
9. The method according to claim 5, characterized in that, After outputting the flow control results for the network traffic to be processed, the process also includes: When pending network traffic belonging to the dependent application is identified again, the access authorization status is re-acquired, and when the re-acquired access authorization status is authorized, the application usage information is re-acquired, and the recently used application and the usage context are re-determined based on the re-acquired application usage information. When the redefined usage context switches between a foreground state and a background state relative to the previously defined usage context, the flow control result is updated according to the redefined usage context; When the redefined usage context is a foreground state, the flow control result is updated to the blocking result; when the redefined usage context is a background state, the activation state is activated, and the re-acquired access authorization state is authorized, the flow control result is updated to the allowing result.
10. A control system for allowing access based on application traffic in a game acceleration scenario, characterized in that, Includes at least one terminal device; The terminal device includes a storage unit and a computing unit; the storage unit is used to store program code; the computing unit is used to run the program code to execute the method for allowing access based on application traffic in a game acceleration scenario as described in any one of claims 1 to 9.
