Directed traffic flow free-flow method, device, terminal, server and storage medium

Abstract

The application provides a method, device, terminal, server and storage medium for targeted traffic flow exemption. The method comprises the following steps: monitoring whether an application program triggers a traffic data access request by using a software development kit (SDK) embedded in the application program; if yes, generating a targeted traffic data access request when a source address corresponding to the traffic data access request is determined as a targeted traffic whitelist address by using the SDK, and sending the targeted traffic data access request to a proxy server corresponding to the SDK, so that the proxy server sends the targeted traffic data access request to a first server corresponding to the source address when the targeted traffic data access request meets a preset traffic flow exemption access condition. The method of the application determines whether to allow traffic flow exemption through the embedded SDK and re-authenticates through the proxy server, and does not need to configure the IP address of the application program of the targeted traffic flow through the GGSN, so that the demand for a large amount of targeted traffic flow can be met, and a relatively complex configuration process is avoided.

Description

TECHNICAL FIELD

[0001] The present application relates to the communication technology field, in particular to a directional traffic flow exemption method and device, terminal, server and storage medium. BACKGROUND

[0002] The directional traffic flow refers to the traffic flow package for one or more specified applications, when the directional traffic flow is used, the traffic flow consumed by the specified application will be deducted from the directional traffic flow package, and will not consume the national traffic flow or provincial traffic flow in the mobile phone monthly package.

[0003] The directional traffic flow service implementation is mainly based on service identification, and at present, the IP scheme is directly configured in the gateway GPRS direct node (GGSN) to achieve the implementation, the IP address of the application program of the directional traffic flow and the corresponding service ID are configured through the GGSN. When the user accesses the specified application program or content, the GGSN counts the traffic flow information of the user using the service ID based on the corresponding relationship of the configured IP address and the service ID, so as to perform a specific charging strategy or exemption flow.

[0004] However, this method needs to pre-configure the IP address, but when the number of configured IP addresses is large, the configuration efficiency is low, and the GGSN does not support configuring too many IP addresses, and the configuration steps are also complex, which cannot meet the demand of a large number of directional traffic flows. SUMMARY

[0005] The present application provides a directional traffic flow exemption method, device, terminal, server and storage medium, to solve the problem that the existing flow exemption method of pre-configuring the IP address of the application program through the GGSN is not applicable.

[0006] In a first aspect, the present application provides a directional traffic flow exemption method, comprising:

[0007] The software development kit (SDK) embedded in the application program is used to monitor whether the application program triggers a traffic data access request;

[0008] If yes, the SDK is used to determine that the source address corresponding to the traffic data access request is a directional traffic flow whitelist address, to generate a directional traffic data access request, and send the directional traffic data access request to the proxy server corresponding to the SDK, so that the proxy server determines that the directional traffic data access request is sent to the first server corresponding to the source address when the pre-set flow exemption access condition is met.

[0009] In a second aspect, the present application provides a directional traffic flow exemption method, comprising:

[0010] receive a directional traffic data access request sent by the user terminal, the directional traffic data access request being generated by the user terminal using a software development kit (SDK) embedded in an application program when it is determined that the source address corresponding to the traffic data access request is a directional traffic whitelist address after monitoring the traffic data access request;

[0011] determine whether the directional traffic data access request meets a preset flow-free access condition;

[0012] if yes, send the directional traffic data access request to a first server corresponding to the source address.

[0013] In a third aspect, the present application provides a directional traffic flow-free device, comprising:

[0014] a monitoring unit configured to monitor whether an application program triggers a traffic data access request using a software development kit (SDK) embedded in the application program;

[0015] a first sending unit configured to generate a directional traffic data access request if the application program triggers the traffic data access request using the SDK when it is determined that the source address corresponding to the traffic data access request is a directional traffic whitelist address, and send the directional traffic data access request to a proxy server corresponding to the SDK, so that the proxy server sends the directional traffic data access request to a first server corresponding to the source address when it is determined that the directional traffic data access request meets a preset flow-free access condition.

[0016] In a fourth aspect, the present application provides a directional traffic flow-free device, comprising:

[0017] a receiving module configured to receive a directional traffic data access request sent by the user terminal, the directional traffic data access request being generated by the user terminal using a software development kit (SDK) embedded in an application program when it is determined that the source address corresponding to the traffic data access request is a directional traffic whitelist address after monitoring the traffic data access request;

[0018] a determining unit configured to determine whether the directional traffic data access request meets a preset flow-free access condition;

[0019] a second sending unit configured to send the directional traffic data access request to a first server corresponding to the source address if yes.

[0020] In a fifth aspect, the present application provides a user terminal, comprising a processor, a memory and a transceiver;

[0021] The processor, the memory and the transceiver are interconnected;

[0022] The memory stores computer execution instructions;

[0023] a transceiver for transmitting and receiving data and requests;

[0024] The processor executes computer-executed instructions stored in the memory, so that the processor executes the method of the first aspect.

[0025] In a sixth aspect, the present application provides a proxy server, comprising: a processor, a memory and a transceiver;

[0026] The processor, the memory and the transceiver circuit are interconnected;

[0027] The memory stores computer-executed instructions;

[0028] a transceiver for transmitting and receiving data and requests;

[0029] The processor executes computer-executed instructions stored in the memory, so that the processor executes the method of the second aspect.

[0030] In a seventh aspect, the present application provides a computer-readable storage medium, the computer-readable storage medium stores computer-executed instructions, and the computer-executed instructions are executed by the processor to implement the method of the first aspect or the second aspect.

[0031] The application provides a targeted traffic flow exemption method and device, a terminal, a server and a storage medium. The SDK corresponding to the proxy server is embedded in the application in advance. The SDK is used to monitor whether the application triggers a traffic data access request. If yes, the SDK is used to determine whether the source address corresponding to the traffic data access request is a targeted exemption flow whitelist address. If yes, a targeted traffic data access request is generated. The targeted traffic data access request is sent to the proxy server. The proxy server determines whether the targeted traffic data access request meets a preset exemption flow access condition. If yes, the targeted traffic data access request is sent to a first server corresponding to the source address. Data corresponding to the targeted traffic data access request is obtained from the first server. The proxy server interacts with the user terminal and the first server. The targeted traffic flow is used to realize exemption flow and additional charging is not performed. In the method, the embedded SDK is used to determine whether exemption flow is allowed and the proxy server is used for re-authentication. The IP address of the application of the targeted traffic flow does not need to be configured through the GGSN. A large number of targeted traffic flow requirements can be met, and a relatively complex configuration process is avoided. BRIEF DESCRIPTION OF DRAWINGS

[0032] The accompanying drawings, which are incorporated herein and constitute part of the specification, illustrate embodiments consistent with the application and, together with the description, serve to explain the principles of the application.

[0033] Figure 1 is a network architecture schematic diagram of the targeted traffic flow exemption method provided by the application;

[0034] Figure 2is a flowchart of a targeted traffic free-flow method provided by an embodiment of the present application;

[0035] Figure 3 is a flowchart of a targeted traffic free-flow method provided by an embodiment of the present application;

[0036] Figure 4 is a flowchart of a targeted traffic free-flow method provided by an embodiment of the present application;

[0037] Figure 5 is a flowchart of a targeted traffic free-flow method provided by an embodiment of the present application;

[0038] Figure 6 is a structural diagram of a targeted traffic free-flow device provided by an embodiment of the present application;

[0039] Figure 7 is a structural diagram of a targeted traffic free-flow device provided by another embodiment of the present application;

[0040] Figure 8 is a block diagram of a user terminal for implementing a targeted traffic free-flow method of an embodiment of the present application;

[0041] Figure 9 is a block diagram of a proxy server for implementing a targeted traffic free-flow method of an embodiment of the present application.

[0042] The specific embodiments of the present application have been shown through the above-described drawings, and will be described in more detail hereinafter. The drawings and the written description are not intended to restrict the scope of the present application by any means, but to illustrate the concept of the present application to those skilled in the art by referring to specific embodiments. DETAILED DESCRIPTION

[0043] The exemplary embodiments will be described in detail with reference to the accompanying drawings. The following description is presented with reference to the accompanying drawings, in which a similar reference can indicate similar elements throughout the several drawings. The embodiments described in the following exemplary embodiments are not meant to represent all implementations consistent with the present application. Rather, they are merely examples of apparatus and methods consistent with some aspects of the present application as detailed in the appended claims.

[0044] In order to clearly understand the technical solutions of the present application, the prior art solutions are first described in detail.

[0045] Targeted traffic refers to traffic packets for one or more specified applications, and when the targeted traffic is used, the traffic consumed by the specified applications is deducted from the targeted traffic packets, and will not consume the nationwide traffic or provincial traffic in the mobile phone monthly package.

[0046] In the prior art, the IP or uniform resource locator (URL) scheme is directly configured in a gateway GPRS support node (GGSN) to realize the method, the IP address of the application program of the directed traffic and the corresponding service ID are configured in the GGSN, or the URL and the corresponding service ID are configured. When a user accesses a specified application program or content, the GGSN counts the traffic information of the service ID based on the correspondence between the configured IP address and the service ID, or the correspondence between the URL and the service ID, so as to perform a specific charging policy or flow exemption.

[0047] However, the method needs to pre-configure the IP address or the URL, but when the number of configured IP addresses or URLs is large, the configuration efficiency is low, the GGSN does not support configuring too many IP addresses, the configuration steps are complex, and the demand for a large number of directed traffic cannot be met.

[0048] Therefore, in order to solve the problem that the flow exemption method of pre-configuring the IP address of the application program through the GGSN in the prior art is not applicable, the inventors have found, through research, that the SDK corresponding to the proxy server is embedded in the application program in advance, the SDK is used to monitor whether the application program triggers a traffic data access request, if yes, the SDK is used to determine whether the source address corresponding to the traffic data access request is a directed flow exemption whitelist address, the directed traffic data access request is generated when the directed flow exemption access condition is met, the directed traffic data access request is sent to the proxy server, the proxy server determines whether the directed traffic data access request is sent to the first server corresponding to the source address, the data corresponding to the directed traffic data access request is obtained from the first server, the proxy server interacts with the user terminal and the first server, the directed traffic is used, the flow exemption is realized, and no additional charge is performed. In the method, the SDK is embedded to determine whether the flow exemption is allowed and the proxy server is used for re-authentication, the IP address of the application program of the directed traffic does not need to be configured through the GGSN, the demand for a large number of directed traffic can be met, and the complex configuration process is avoided.

[0049] Therefore, based on the above creative findings, the inventors propose the technical scheme of the embodiments of the present application. The network architecture and application scenarios of the directed traffic flow exemption method provided by the embodiments of the present application are introduced below.

[0050] As Figure 1As shown, the network architecture corresponding to the direct flow free flow method provided by the embodiment of the application comprises: a user terminal 1, a proxy server 2 and a first server 3. The user terminal 1 is in communication connection with the proxy server 2, and the proxy server 2 is in communication connection with the first server 3. The user terminal 1 has a client for playing a video pre-installed therein. The user clicks a play button on the operation interface of the client, thereby triggering a flow data access request. The user terminal 1 uses a software development kit (SDK) embedded in an application program to monitor whether the application program triggers the flow data access request. If yes, the SDK is used to determine that the source address corresponding to the flow data access request is a direct flow whitelist address, and a direct flow data access request is generated. The user terminal 1 sends the direct flow data access request to the proxy server 2 corresponding to the SDK. The proxy server 2 determines that the direct flow data access request meets preset free flow access conditions, and sends the direct flow data access request to the first server 3 corresponding to the source address. The first server 3 parses the direct flow data access request, obtains video data corresponding to the direct flow data access request, and sends the corresponding video data to the proxy server 2. The proxy server 2 sends the corresponding video data to the user terminal 1. The user terminal 1 further plays the video data, thereby realizing free flow. The direct flow of the user is used in the process of data transmission. Whether the free flow is allowed is determined by the embedded SDK, and re-authentication is performed by the proxy server. The IP address of the application program of the direct flow does not need to be configured through the GGSN, a large number of direct flow requirements can be met, and a relatively complex configuration process is avoided.

[0051] Hereinafter, the embodiments of the application will be described in detail with reference to the accompanying drawings.

[0052] Embodiment one

[0053] Figure 2 is a flowchart of the direct flow free flow method provided by the embodiment one of the application, as Figure 2 shown, the execution subject of the direct flow free flow method provided by the embodiment is a direct flow free flow device, and the direct flow free flow device is located in a user terminal. Therefore, the direct flow free flow method provided by the embodiment comprises the following steps:

[0054] In step 101, a software development kit (SDK) embedded in an application program is used to monitor whether the application program triggers a flow data access request.

[0055] In this embodiment, the software development kit (SDK) is pre-embedded in the corresponding application, and the SDK is matched with the proxy server. The SDK is used to monitor whether the application triggers a traffic data access request. The user terminal pre-embeds the application according to the application. The application pre-embeds the SDK matched with the proxy server. For example, the user clicks a certain video app. The app pre-embeds the SDK matched with the proxy server. When the user clicks to play the video, the traffic data access request is triggered. At this time, the SDK monitors that the application triggers the traffic data access request. The SDK determines whether the request meets the conditions.

[0056] The software development kit (Software Development Kit, SDK) is generally a collection of development tools used by software engineers to develop application software for a specific software package, software framework, hardware platform, operating system, etc. It can simply provide some files of application program interface for a certain programming language, but it can also include complex hardware that can communicate with some embedded systems.

[0057] In step 102, if yes, the SDK is used to determine that the source address corresponding to the traffic data access request is a directed traffic whitelist address to generate a directed traffic data access request. The directed traffic data access request is sent to the proxy server corresponding to the SDK, so that the proxy server determines that the directed traffic data access request is sent to the first server corresponding to the source address when the directed traffic data access request meets the preset flow-free access condition.

[0058] In this embodiment, the SDK is also used to determine whether the source address corresponding to the traffic data access request is a directed traffic whitelist address. If yes, the SDK generates a directed traffic data access request according to the traffic data access request. The user terminal sends the directed traffic data access request to the proxy server corresponding to the SDK.

[0059] Optionally, determining whether the corresponding source address is a directed traffic whitelist address according to the traffic data access request comprises: obtaining a pre-stored directed traffic whitelist address, performing authentication by using an SDK, parsing the traffic data access request, obtaining the source address corresponding to the traffic data access request, matching the source address with the directed traffic whitelist address, if the source address matches the directed traffic whitelist address, not allowing the user to perform free flow access, then determining that the source address corresponding to the traffic data access request is not a directed traffic whitelist address; if the source address matches the directed traffic whitelist address, allowing the user to perform free flow access, then determining that the source address corresponding to the traffic data access request is a directed traffic whitelist address. Wherein, when the SDK determines that the source address corresponding to the traffic data access request is a directed traffic whitelist address, a directed traffic data access request is generated, the user is allowed to perform free flow access, and the user terminal further sends the directed traffic data access request to the proxy server corresponding to the SDK.

[0060] In the embodiment, the proxy server performs re-authentication. Specifically, the proxy server determines whether the directed traffic data access request meets a preset free flow access condition, and sends the directed traffic data access request to the first server corresponding to the source address when it is determined that the preset free flow access condition is met. The first server corresponding to the source address parses the directed traffic data access request after receiving the directed traffic data access request, obtains data corresponding to the directed traffic data access request, and sends the corresponding data to the proxy server, which then sends the corresponding data to the user terminal, thereby realizing free flow, and the user's directed traffic is used in the process of data transmission.

[0061] It should be noted that if the source address corresponding to the traffic data access request matches the directed traffic whitelist address, the user is not allowed to perform free flow access. At this time, the mobile terminal obtains the data corresponding to the traffic data access request from the first server corresponding to the source address through the source address, the first server sends the corresponding data to the user terminal, at this time, the mobile terminal and the first server interact without passing through the proxy server, at this time, free flow is not realized, and the user's general traffic is used, which includes intraprovincial traffic and interprovincial traffic.

[0062] In the embodiment, the SDK corresponding to the proxy server is embedded in the application in advance, the SDK is used to monitor whether the application triggers the traffic data access request, if yes, the SDK is used to determine whether the source address corresponding to the targeted traffic data access request is the targeted flow-free whitelist address, the targeted traffic data access request is generated when the targeted flow-free whitelist address is determined, the targeted traffic data access request is sent to the proxy server, the proxy server determines that the targeted traffic data access request is sent to the first server corresponding to the source address when the preset flow-free access condition is met, the data corresponding to the targeted traffic data access request is obtained from the first server, the proxy server interacts with the user terminal and the first server, the targeted traffic is used, the flow-free is realized, no additional charge is performed, in the method, whether the flow-free is allowed is determined through the embedded SDK and the proxy server is authenticated again, the IP address of the application of the targeted traffic does not need to be configured through the GGSN, a large number of targeted traffic demands can be met, and a relatively complex configuration process is avoided.

[0063] Embodiment two

[0064] Figure 3 is a flowchart of a targeted traffic flow-free method provided by the embodiment two of the application, as shown in Figure 3 based on the targeted traffic flow-free method provided by the embodiment one of the application, the following steps are further included before step 101:

[0065] Step 1011, monitoring whether the application triggers a targeted traffic subscription request.

[0066] In the embodiment, the user terminal monitors whether the application triggers a targeted traffic subscription request, specifically, the user clicks to subscribe to the targeted traffic on the application operation interface, thereby triggering the targeted traffic subscription request.

[0067] Step 1012, if yes, obtaining the user terminal identifier and generating targeted traffic subscription information according to the user terminal identifier and the targeted traffic subscription request.

[0068] In the embodiment, if it is monitored that the application triggers the targeted traffic subscription request, the user terminal identifier of the user terminal is further obtained, and the targeted traffic subscription information is generated according to the user terminal identifier and the targeted traffic subscription request.

[0069] Optionally, the user terminal identifier corresponding to the user terminal is obtained, specifically, the user terminal identifier is obtained from the local cache information, if the obtaining fails, the API interface is called to perform a number taking operation, and the API interface is called to obtain the user terminal identifier through a number taking platform.

[0070] Step 1013, sending the targeted traffic subscription information to the corresponding second server, so that the second server feeds back payment information according to the targeted traffic subscription information.

[0071] In the embodiment, the directional traffic subscription information is sent to a corresponding second server, the second server is a server corresponding to the directional traffic subscription request, and the second server feeds back payment information after receiving the directional traffic subscription information.

[0072] In step 1014, a payment page corresponding to the payment information is displayed, and a payment request based on the payment page is received.

[0073] In the embodiment, the user terminal receives the payment information, displays a payment page corresponding to the payment information, and triggers a payment request by clicking the payment page. The payment request based on the payment page is received.

[0074] In step 1015, a payment operation is performed according to the payment request, and after the payment is completed, the directional traffic subscription information is sent to the proxy server, so that the proxy server determines whether the directional traffic data access request meets the preset free access condition according to the traffic subscription information.

[0075] In the embodiment, a payment operation is performed according to the payment request, the payment is completed, and after the payment is completed, the directional traffic subscription information is sent to the proxy server. The proxy server determines whether the traffic data access request meets the preset free access condition according to the traffic subscription information. Specifically, the proxy server determines whether the traffic data access request meets the preset free access condition according to the traffic subscription information and the user terminal identifier corresponding to the user terminal. If the proxy server determines that the traffic data access request meets the preset free access condition, the proxy server sends the traffic data access request to the first server.

[0076] Embodiment three

[0077] On the basis of the directional traffic free method provided in the first embodiment of the application, after step 101, the following steps are further included:

[0078] In step 101a, directional traffic prompt information fed back by the proxy server is received. The directional traffic prompt information is generated by the proxy server according to the used directional traffic determined according to the user terminal identifier.

[0079] In the embodiment, the directional traffic prompt information sent by the proxy server is received, and the user terminal further displays the directional traffic prompt information on the display interface. The user can view the directional traffic prompt information to understand the current directional traffic usage.

[0080] The directional traffic prompt information is generated by the proxy server according to the used directional traffic determined according to the user terminal identifier, and is used to prompt the user about the remaining directional traffic.

[0081] In the method, whether to allow flow-free is determined through the embedded SDK, and re-authentication is performed through the proxy server, without configuring the IP address of the application of the directed flow through the GGSN, the requirement of a large number of directed flows can be met, and the complex configuration process is avoided.

[0082] Embodiment four

[0083] Figure 4 is a flowchart of a directed flow-free method provided by the embodiment four of the application, as shown in the figure, the execution subject of the directed flow-free method provided by the embodiment is a directed flow-free device, the directed flow-free device is located in a proxy server, and then the directed flow-free method provided by the embodiment includes the following steps. Figure 4

[0084] Step 201, receiving a directed flow data access request sent by a user terminal, the directed flow data access request is a directed flow data access request generated by the user terminal when the software development kit (SDK) embedded in an application program determines that a source address corresponding to a flow data access request monitored by the SDK is a directed flow whitelist address.

[0085] In the embodiment, the directed flow data access request sent by the user terminal is generated by the software development kit (SDK) embedded in the application program, the SDK is pre-integrated in the application program, the SDK is used to monitor whether the application program triggers a flow data access request, if the SDK monitors the flow data access request, the SDK determines whether a source address corresponding to the flow data access request is a directed flow whitelist address, if yes, a directed flow data access request is further generated according to the flow data access request, and the user terminal sends the flow data access request to a proxy server corresponding to the SDK.

[0086] Optionally, the SDK determines whether the source address corresponding to the flow data access request is the directed flow whitelist address, specifically, the SDK parses the flow data access request to obtain the source address corresponding to the flow data access request, matches the source address with the directed flow whitelist address, if the source address matches the directed flow whitelist address, the user is not allowed to access flow-free, and then it is determined that the source address corresponding to the flow data access request is not the directed flow whitelist address; if the source address matches the directed flow whitelist address, the user is allowed to access flow-free, and then it is determined that the source address corresponding to the flow data access request is the directed flow whitelist address. When the SDK determines that the source address corresponding to the flow data access request is the directed flow whitelist address, the directed flow data access request is generated, the user is allowed to access flow-free, and the user terminal further sends the directed flow data access request to the proxy server corresponding to the SDK.

[0087] ​Step 202, determining whether the directional traffic data access request meets the preset free flow access condition.

[0088] In the embodiment, the proxy server determines again whether the directional traffic data access request meets the free flow condition, and if it is determined that the directional traffic data access request does not meet the preset free flow access condition, the directional traffic data access request will not be sent to the first proxy server corresponding to the SDK, in which case the directional traffic cannot be used, and the proxy server can feed back a prompt information that the directional traffic cannot be used to the user terminal, and the user terminal displays the prompt information on the display interface to prompt the user that the general traffic needs to be used for this time access.

[0089] Step 203, if yes, the directional traffic data access request is sent to the first server corresponding to the source address.

[0090] In the embodiment, if it is determined that the directional traffic data access request meets the preset free flow access condition, the directional traffic data access request is sent to the first server corresponding to the source address, the first server parses the directional traffic data access request, obtains the data corresponding to the directional traffic data access request, and the first server sends the corresponding data to the proxy server, and the proxy server sends the corresponding data to the user terminal, so as to realize free flow, and the user's directional traffic is used in the process of data transmission.

[0091] It should be noted that if it is determined that the directional traffic data access request meets the preset free flow access condition, the proxy server feeds back a prompt information that the directional traffic cannot be used to the user terminal, and after the user terminal receives the prompt information, the user terminal sends the traffic data access request to the first server corresponding to the source address, the first server sends the data corresponding to the traffic data access request to the user terminal, and the mobile terminal interacts with the first server, at this time, the free flow is not realized, and the user's general traffic is used, and the general traffic includes the intraprovincial traffic and the interprovincial traffic.

[0092] Embodiment five

[0093] Figure 5 is a flowchart of the directional traffic free flow method provided by the embodiment five of the application, as shown in Figure 5 Based on the directional traffic free flow method provided by the embodiment four of the application, step 202 is further refined, and specifically includes the following steps:

[0094] Step 2021, parsing the directional traffic data access request to obtain the user terminal identifier corresponding to the user terminal.

[0095] In the embodiment, the directional traffic data access request is parsed to obtain the user terminal identifier corresponding to the user terminal, and the user terminal identifier can be a user mobile phone number.

[0096] In step 2022, the local traffic subscription information is acquired, and it is determined whether the targeted traffic data access request meets the preset free access condition according to the local traffic subscription information and the user terminal identifier.

[0097] In this embodiment, the proxy server locally stores the traffic subscription information, acquires the locally stored traffic subscription information, and determines whether the targeted traffic data access request meets the preset free access condition according to the locally stored traffic subscription information and the user terminal identifier, so that the targeted traffic data access request is sent to the first server corresponding to the source address when the free condition is met.

[0098] Embodiment six

[0099] On the basis of the targeted traffic free method provided in Embodiment five, the step of determining whether the targeted traffic data access request meets the preset free access condition according to the local traffic subscription information and the user terminal identifier in step 2022 is further refined, and specifically includes the following steps:

[0100] In step 2022a, the purchased user terminal identifiers in the local traffic subscription information are acquired, and the user terminal identifier is matched with the purchased user terminal identifiers.

[0101] In this embodiment, a plurality of purchased user terminal identifiers in the local traffic subscription information are acquired, wherein the purchased user terminal identifier refers to the identifier corresponding to the user terminal that has subscribed to the targeted traffic, the user terminal identifier obtained by parsing the targeted traffic data access request is matched with the purchased user terminal identifiers, and it is determined that the targeted traffic data access request meets the preset free access condition according to the matching result.

[0102] In step 2022b, if the user terminal identifier matches the purchased user terminal identifier, it is determined that the targeted traffic data access request meets the preset free access condition.

[0103] In this embodiment, if the user terminal identifier matches the purchased user terminal identifier, it indicates that the user has purchased the corresponding targeted traffic, and it is determined that the targeted traffic data access request meets the preset free access condition.

[0104] In step 2022c, if the user terminal identifier does not match the purchased user terminal identifier, it is determined that the targeted traffic data access request does not meet the preset free access condition.

[0105] In this embodiment, if the user terminal identifier does not match the purchased user terminal identifier, it indicates that the user has not purchased the corresponding targeted traffic, and it is determined that the targeted traffic data access request does not meet the preset free access condition.

[0106] Embodiment seven

[0107] On the basis of the targeted traffic free-flow method provided in Embodiment Four of the present application, Step 202 is further refined, and specifically includes the following steps:

[0108] In Step A2021, the targeted traffic data access request is parsed to obtain the corresponding application program identifier and the user terminal identifier corresponding to the user terminal.

[0109] In this embodiment, the targeted traffic data access request is parsed to obtain the application program identifier corresponding to the targeted traffic data access request and the user terminal identifier corresponding to the user terminal, wherein the user terminal identifier can be a user mobile phone number.

[0110] In Step A2022, the local traffic subscription information is obtained, and the local traffic subscription information, the application program identifier corresponding to the targeted traffic data access request, and the user terminal identifier are used to determine whether the targeted traffic data access request meets the preset free-flow access condition.

[0111] In this embodiment, the proxy server locally stores the traffic subscription information, the locally stored traffic subscription information is obtained, and the locally stored traffic subscription information, the application program identifier corresponding to the targeted traffic data access request, and the user terminal identifier are used to determine whether the targeted traffic data access request meets the preset free-flow access condition, so that the targeted traffic data access request is sent to the first server corresponding to the source address when the free-flow condition is met.

[0112] Optionally, Step A2022 in which the local traffic subscription information, the application program identifier corresponding to the targeted traffic data access request, and the user terminal identifier are used to determine whether the targeted traffic data access request meets the preset free-flow access condition is further refined, and specifically includes the following steps:

[0113] In Step A2022a, the purchased user terminal identifiers in the local traffic subscription information and the application program identifiers corresponding to the purchased user terminal identifiers are obtained, and the user terminal identifier is matched with the purchased user terminal identifiers.

[0114] In this embodiment, multiple purchased user terminal identifiers in the local traffic subscription information are obtained, wherein the purchased user terminal identifier refers to an identifier corresponding to a user terminal that has subscribed to targeted traffic, the user terminal identifier obtained by parsing the targeted traffic data access request is matched with the purchased user terminal identifiers, and if the user terminal identifier does not match the purchased user terminal identifiers, it is determined that the user has not purchased the corresponding targeted traffic, and it is determined that the targeted traffic data access request does not meet the preset free-flow access condition.

[0115] In Step A2022b, if the user terminal identifier matches the purchased user terminal identifier, the application program identifier corresponding to the purchased user terminal identifier is matched with the application program identifier corresponding to the targeted traffic data access request.

[0116] In this embodiment, if the user terminal identifier matches the purchased user terminal identifier, it is further determined whether the application identifier corresponding to the purchased user terminal identifier matches the application identifier corresponding to the targeted traffic data access request, and the targeted traffic data access request is determined to satisfy the preset free flow access condition according to the matching result. Wherein, the user terminal can subscribe to corresponding targeted traffic for different applications according to its own needs, and the application identifier is matched to determine whether the application identifier corresponds to the corresponding targeted traffic.

[0117] Step A2022c, if matched, it is determined that the targeted traffic data access request satisfies the preset free flow access condition.

[0118] In this embodiment, if the application identifier corresponding to the purchased user terminal identifier matches the application identifier corresponding to the targeted traffic data access request, it indicates that the user has purchased corresponding targeted traffic for the application, and it is determined that the targeted traffic data access request satisfies the preset free flow access condition.

[0119] Step A2022d, if not matched, it is determined that the targeted traffic data access request does not satisfy the preset free flow access condition.

[0120] In this embodiment, if the application identifier corresponding to the purchased user terminal identifier does not match the application identifier corresponding to the targeted traffic data access request, it indicates that the user has not purchased corresponding targeted traffic for the application, and it is determined that the targeted traffic data access request does not satisfy the preset free flow access condition.

[0121] Embodiment eight

[0122] On the basis of the targeted traffic free flow method provided in Embodiment Four of the present application, step 202 is further refined, which specifically includes the following steps:

[0123] Step B2021, the current time is obtained, and it is determined whether the current time belongs to the preset free flow access time range.

[0124] In this embodiment, the current time is obtained, and the current time is compared with the preset free flow access time range, and it is determined whether the preset free flow access condition is satisfied according to the comparison result.

[0125] Step B2022, if yes, it is determined that the targeted traffic data access request satisfies the preset free flow access condition.

[0126] In this embodiment, if the current time belongs to the preset free flow access time range, it indicates that the current time period allows free flow, and it is determined that the targeted traffic data access request satisfies the preset free flow access condition.

[0127] Step B2023, if no, it is determined that the directional traffic data access request does not meet the preset free access condition.

[0128] In the embodiment, if the current time does not belong to the preset free access time range, it is indicated that the current time period does not allow free flow, and it is determined that the directional traffic data access request meets the preset free access condition.

[0129] Optionally, whether the preset free access condition is met can also be determined according to the network state of the user terminal, specifically, the proxy server acquires the network state of the user terminal, if the network state of the user terminal is a preset network state, for example, a preset network state 2G or 3G, it is determined that the directional traffic data access request meets the preset free access condition; if the network state of the user terminal is not a preset network state, it is determined that the directional traffic data access request meets the preset free access condition.

[0130] Optionally, whether the preset free access condition is met can also be determined according to the location information of the user terminal, specifically, the proxy server acquires the location information corresponding to the user terminal, if the location information corresponding to the user terminal is a preset location information, it is determined that the directional traffic data access request meets the preset free access condition; if the location information corresponding to the user terminal is not a preset location information, it is determined that the directional traffic data access request meets the preset free access condition.

[0131] Embodiment Nine

[0132] On the basis of the directional traffic free flow method provided in Embodiment Four of the application, after step 201, the following steps are further included:

[0133] Step 201a, determining the used directional traffic according to the user terminal identifier corresponding to the user terminal.

[0134] In the embodiment, the used directional traffic of the user is determined according to the user terminal identifier corresponding to the user terminal, specifically, the user terminal sends access information to the proxy server at a preset time interval, the proxy server parses the access information to obtain the corresponding access source address, the used directional traffic of the current user is counted according to the access source address, that is, the number of bytes used by the access source address, and the used directional traffic of the current user is accumulated with the used directional traffic of the historical user to determine the used directional traffic.

[0135] Step 201b, generating directional traffic prompt information according to the used directional traffic, and sending the directional traffic prompt information to the user terminal.

[0136] In this embodiment, the used directional traffic is used to generate directional traffic prompt information, wherein the directional traffic prompt information comprises the used directional traffic and / or unused directional traffic, and the directional traffic prompt information is further sent to the user terminal, so that the user can know the remaining situation of the directional traffic in time.

[0137] Figure 6 is a structural schematic diagram of the directional traffic free flow device provided by an embodiment of the application, as Figure 6 shown, the directional traffic free flow device 200 provided by this embodiment comprises a monitoring unit 201 and a first sending unit 202.

[0138] The monitoring unit 201 is configured to monitor whether an application program triggers a traffic data access request by using a software development kit (SDK) embedded in the application program. The first sending unit 202 is configured to generate a directional traffic data access request if the application program triggers the traffic data access request, and determine that a source address corresponding to the traffic data access request is a directional traffic whitelist address by using the SDK, and send the directional traffic data access request to a proxy server corresponding to the SDK, so that the proxy server sends the directional traffic data access request to a first server corresponding to the source address when the directional traffic data access request meets preset free flow access conditions.

[0139] Optionally, the management unit is configured to monitor whether the application program triggers a directional traffic subscription request, obtain a user terminal identifier if the application program triggers the directional traffic subscription request, generate directional traffic subscription information according to the user terminal identifier and the directional traffic subscription request, send the directional traffic subscription information to a second server corresponding to the directional traffic subscription information, so that the second server feeds back payment information according to the directional traffic subscription information, display a payment page corresponding to the payment information, receive a payment request based on the payment page, perform a payment operation according to the payment request, and send the directional traffic subscription information to the proxy server after the payment is completed, so that the proxy server determines whether the directional traffic data access request meets the preset free flow access conditions according to the traffic subscription information.

[0140] Optionally, the directional traffic free flow device further comprises a display unit.

[0141] The display unit is configured to receive directional traffic prompt information fed back by the proxy server, wherein the directional traffic prompt information is generated by the proxy server according to used directional traffic and the used directional traffic.

[0142] Figure 7 is a structural schematic diagram of the directional traffic free flow device provided by another embodiment of the application, as Figure 7 shown, the directional traffic free flow device 300 provided by this embodiment comprises a receiving module 301, a determination unit 302 and a second sending unit 303.

[0143] The receiving module 301 is configured to receive a directional traffic data access request sent by a user terminal, wherein the directional traffic data access request is generated by the user terminal when the user terminal determines that a source address corresponding to a traffic data access request is a directional traffic whitelist address after monitoring the traffic data access request by using a software development kit (SDK) embedded in an application program.

[0144] Optionally, the determining unit is further configured to parse the directional traffic data access request to obtain a user terminal identifier corresponding to the user terminal, obtain local traffic subscription information, and determine whether the directional traffic data access request meets the preset free flow access condition according to the local traffic subscription information and the user terminal identifier.

[0145] Optionally, the determining unit is further configured to obtain a purchased user terminal identifier in the local traffic subscription information, match the user terminal identifier with the purchased user terminal identifier, determine that the directional traffic data access request meets the preset free flow access condition if the user terminal identifier matches the purchased user terminal identifier, and determine that the directional traffic data access request does not meet the preset free flow access condition if the user terminal identifier does not match the purchased user terminal identifier.

[0146] Optionally, the directional traffic free flow apparatus further includes a directional traffic monitoring unit.

[0147] The directional traffic monitoring unit is further configured to determine used directional traffic according to a user terminal identifier corresponding to the user terminal, generate directional traffic prompt information according to the used directional traffic, and send the directional traffic prompt information to the user terminal.

[0148] Figure 8 A block diagram of a user terminal for implementing the directional traffic free flow method according to an embodiment of the present application is shown in FIG. 4. Figure 8 The user terminal 400 includes a memory 401, a processor 402, and a transceiver 403.

[0149] The processor 402, the memory 401, and the transceiver 403 are electrically connected to each other.

[0150] The transceiver 403 is configured to receive and send data and requests.

[0151] The memory 401 stores computer execution instructions.

[0152] The processor 402 executes the computer execution instructions stored in the memory 401, so that the processor executes the method provided in any one of the above embodiments.

[0153] Figure 9 is a block diagram of a proxy server for implementing the method of the application, as Figure 9 shown, the proxy server 500 comprises a memory 501, a processor 502 and a transceiver 503.

[0154] The processor 502, the memory 501 and the transceiver 503 are electrically connected;

[0155] The transceiver 503 is configured to receive and transmit data and requests.

[0156] The memory 501 stores computer-executable instructions.

[0157] The processor 502 executes the computer-executable instructions stored in the memory 501, so that the processor performs the method provided in any one of the above embodiments.

[0158] In an exemplary embodiment, a computer-readable storage medium is also provided, and the computer-readable storage medium stores computer-executable instructions, and the computer-executable instructions are executed by the processor to perform the method in any one of the above embodiments.

[0159] In an exemplary embodiment, a computer program product is also provided, and the computer program product comprises a computer program, and the computer program is executed by the processor to perform the method in any one of the above embodiments.

[0160] Other embodiments of the application will be apparent to those skilled in the art from consideration of the specification and practice of the application disclosed herein. It is intended that the application be limited only by the scope of the claims, which will be construed in accordance with the principles of patent law including 35 U.S.C. § 112(f). All references cited herein are incorporated by reference in their entirety and for all purposes.

[0161] It should be understood that the application is not limited to the precise construction that has been described above and shown in the accompanying drawings, and that various modifications and changes can be made by those skilled in the art without departing from the scope of the application. The scope of the application is to be defined by the claims appended hereto.

Claims

1. A method for targeted data usage exemption, characterized in that, Applied to user terminals, the methods include: The software development kit (SDK) embedded in the application is used to monitor whether the application triggers traffic data access requests; If so, the SDK determines that the source address corresponding to the traffic data access request is a whitelisted address for targeted traffic, generates a targeted traffic data access request, and sends the targeted traffic data access request to the proxy server corresponding to the SDK. The proxy server parses the targeted traffic data access request to obtain the user terminal identifier and the application identifier; it also obtains the purchased user terminal identifier and the corresponding application identifier from the local traffic subscription information, and matches the user terminal identifier with the purchased user terminal identifier; if the user terminal identifier matches the purchased user terminal identifier, it matches the application identifier corresponding to the purchased user terminal identifier with the application identifier corresponding to the targeted traffic data access request; if they match, it determines that the targeted traffic data access request meets the preset free traffic access conditions, and sends the targeted traffic data access request to the first server corresponding to the source address; Before using a software development kit (SDK) embedded in the application to monitor whether the application triggers traffic data access requests, the following steps are also included: Monitor whether the application triggers a targeted traffic subscription request; If so, obtain the user terminal identifier and generate targeted traffic subscription information based on the user terminal identifier and the targeted traffic subscription request; The targeted traffic order information is sent to the corresponding second server, so that the second server can provide payment information based on the targeted traffic order information; Display the payment page corresponding to the payment information and receive payment requests based on the payment page; The payment operation is performed according to the payment request, and the targeted traffic subscription information is sent to the proxy server after the payment is completed, so that the proxy server can determine whether the targeted traffic data access request meets the preset free traffic access conditions based on the traffic subscription information. After using a software development kit (SDK) embedded in the application to monitor whether the application triggers traffic data access requests, it also includes: Receive targeted traffic alert information from the proxy server. The targeted traffic alert information is generated by the proxy server based on the user terminal identifier to determine the targeted traffic that has been used.

2. A method for targeted data usage exemption, characterized in that, Applied to proxy servers, the methods include: Receive a targeted traffic data access request sent by the user terminal. The targeted traffic data access request is generated by the user terminal using the software development kit (SDK) embedded in the application after detecting the traffic data access request and determining that the source address corresponding to the traffic data access request is a targeted traffic whitelist address. Determine whether the targeted traffic data access request meets the preset free data access conditions; If so, the targeted traffic data access request will be sent to the first server corresponding to the source address; The step of determining whether a targeted traffic data access request meets the preset free traffic access conditions includes: Parse the targeted traffic data access request to obtain the user terminal identifier corresponding to the user terminal; Obtain local data traffic subscription information, and obtain the purchased user terminal identifier and the application identifier corresponding to the purchased user terminal identifier from the local data traffic subscription information, and match the user terminal identifier with the purchased user terminal identifier; If the user terminal identifier matches the purchased user terminal identifier, then the application identifier corresponding to the purchased user terminal identifier is matched with the application identifier corresponding to the targeted traffic data access request; if they match, then the targeted traffic data access request is determined to meet the preset free traffic access conditions. If the user terminal identifier does not match the purchased user terminal identifier, it is determined that the targeted traffic data access request does not meet the preset free traffic access conditions. The method for storing targeted traffic subscription information in the proxy server includes: The traffic subscription information is generated through monitoring on the user terminal and sent to the proxy server for storage. Specifically, the traffic subscription information is generated by monitoring whether the application on the user terminal triggers a targeted traffic subscription request. If so, the user terminal identifier is obtained, and targeted traffic subscription information is generated based on the user terminal identifier and the targeted traffic subscription request. The targeted traffic subscription information is sent to the corresponding second server, which then provides payment information based on the targeted traffic subscription information. A payment page corresponding to the payment information is displayed, and a payment request based on the payment page is received. The payment operation is performed according to the payment request, and the targeted traffic subscription information is sent to the proxy server after the payment is completed. After receiving a targeted traffic data access request sent by a user terminal, the process includes: The used targeted traffic is determined based on the user terminal identifier corresponding to the user terminal; Based on the used targeted traffic, a targeted traffic alert message is generated and sent to the user's terminal.

3. A directional flow-free device, characterized in that, Located in the user terminal, the device includes: The monitoring unit is used to monitor whether the application triggers traffic data access requests using a software development kit (SDK) embedded in the application. The first sending unit is configured to, if the source address corresponding to the traffic data access request is determined to be a whitelisted address for targeted traffic using the SDK, generate a targeted traffic data access request and send the targeted traffic data access request to the proxy server corresponding to the SDK. The proxy server parses the targeted traffic data access request, obtains the user terminal identifier and the application identifier, and obtains the purchased user terminal identifier and the application identifier corresponding to the purchased user terminal identifier from the local traffic subscription information. The user terminal identifier is matched with the purchased user terminal identifier. If the user terminal identifier matches the purchased user terminal identifier, the application identifier corresponding to the purchased user terminal identifier is matched with the application identifier corresponding to the targeted traffic data access request. If they match, the targeted traffic data access request is determined to meet the preset free traffic access conditions, and the targeted traffic data access request is sent to the first server corresponding to the source address. The management unit monitors whether the application triggers a targeted traffic subscription request. If so, it obtains the user terminal identifier and generates targeted traffic subscription information based on the user terminal identifier and the targeted traffic subscription request. It then sends the targeted traffic subscription information to the corresponding second server, which provides payment information based on the targeted traffic subscription information. The unit displays the payment page corresponding to the payment information and receives payment requests based on the payment page. It performs payment operations based on the payment requests and sends the targeted traffic subscription information to the proxy server after payment is completed, so that the proxy server can determine whether the targeted traffic data access request meets the preset free traffic access conditions based on the traffic subscription information. The display unit is used to receive targeted traffic prompt information from the proxy server. The targeted traffic prompt information is generated by the proxy server based on the user terminal identifier to determine the used targeted traffic.

4. A directional flow-free device, characterized in that, Located within the proxy server, the device includes: The receiving module is used to receive the targeted traffic data access request sent by the user terminal. The targeted traffic data access request is generated by the user terminal using the software development kit (SDK) embedded in the application after detecting the traffic data access request and determining that the source address corresponding to the traffic data access request is a targeted traffic whitelist address. The determining unit is used to determine whether a targeted traffic data access request meets the preset free traffic access conditions; The second sending unit is used to send the directed traffic data access request to the first server corresponding to the source address if the condition is met. The determining unit is specifically used to parse the targeted data access request and obtain the user terminal identifier corresponding to the user terminal; obtain local data subscription information, and obtain the purchased user terminal identifier and the application identifier corresponding to the purchased user terminal identifier from the local data subscription information; match the user terminal identifier with the purchased user terminal identifier; if the user terminal identifier matches the purchased user terminal identifier, then match the application identifier corresponding to the purchased user terminal identifier with the application identifier corresponding to the targeted data access request; if they match, then determine that the targeted data access request meets the preset free data access conditions; if the user terminal identifier does not match the purchased user terminal identifier, then determine that the targeted data access request does not meet the preset free data access conditions; wherein, the The method for storing targeted traffic subscription information in a proxy server includes: the traffic subscription information is generated by monitoring a user terminal and sent to the proxy server for storage; wherein, the traffic subscription information is generated by monitoring whether an application triggers a targeted traffic subscription request on the user terminal; if so, the user terminal identifier is obtained, and targeted traffic subscription information is generated based on the user terminal identifier and the targeted traffic subscription request; the targeted traffic subscription information is sent to a corresponding second server, so that the second server can provide payment information based on the targeted traffic subscription information; a payment page corresponding to the payment information is displayed, and a payment request based on the payment page is received; a payment operation is performed according to the payment request, and the targeted traffic subscription information is sent to the proxy server after the payment is completed; The targeted traffic monitoring unit is used to determine the used targeted traffic based on the user terminal identifier corresponding to the user terminal; generate targeted traffic prompt information based on the used targeted traffic; and send the targeted traffic prompt information to the user terminal.

5. A user terminal, comprising: Processor, memory, and transceiver; Interconnection of processor, memory, and transceiver circuits; The memory stores the instructions that the computer executes; A transceiver is used to send and receive data and requests. The processor executes computer execution instructions stored in memory to implement the method as described in claim 1.

6. A proxy server, comprising: Processor, memory, and transceiver; Interconnection of processor, memory, and transceiver circuits; The memory stores the instructions that the computer executes; A transceiver is used to send and receive data and requests. The processor executes computer execution instructions stored in memory to implement the method as described in claim 2.

7. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-executable instructions that, when executed by a processor, are used to implement the method as described in any one of claims 1 or 2.

8. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the method described in any one of claims 1 or 2.

Images