A system and method for realizing operator-specific traffic management by cloud-pipe-end

Abstract

The present invention belongs to the field of communication technology, and in particular discloses a system and method for realizing operator-specific traffic management in a cloud-pipe-end. The present invention proposes to configure a dedicated traffic billing product package on the pipe side by performing VPN proxy in the operator application software on the end side, dispatching the proxy data of the VPN proxy to a pre-planned designated IP pool on the cloud side, and separately billing the proxy data in the IP pool according to the configured dedicated traffic billing product package, thereby realizing a one-to-one mapping of the entire process from the operator application software, the call bill label, to the traffic billing product package. Moreover, the method does not require large-scale transformation of the network equipment and the billing system, nor does it require the configuration of the partner's service-side IP to the operator's wireless gateway device, which solves the problem of high construction costs and huge maintenance costs for operators existing in traditional technical means. In addition, the method proposed by the present invention does not need to rely on the cooperation of the partner, and decoupling is achieved in the technical process.

Description

Technical Field

[0001] The present invention belongs to the field of communication technology, and in particular relates to a system and method for implementing operator-specific traffic management on a cloud-pipe-end. Background Art

[0002] Carrier dedicated traffic refers to the carrier traffic data generated when users access partner applications. Dedicated traffic needs to be distinguished from other traffic to achieve separate billing of dedicated traffic. Therefore, the distinction of dedicated traffic is an important prerequisite for correct billing.

[0003] To achieve the distinction of dedicated traffic, on the one hand, it is necessary to accurately measure the traffic generated by one user using one application into one product package. This requires telecom operators to achieve one-to-one mapping of the entire process from application, call bill label, to product package through a set of technical solutions. Existing technologies either require large-scale transformation of network equipment and billing systems with the cooperation of partners; or require the configuration of the partner's server IP on the operator's wireless gateway device; or with the cooperation of partners, the partner's application is proxied to the operator's server; however, no matter which existing technology is used, it is impossible to achieve one-to-one mapping of the entire process, and there are still problems with high construction costs and huge maintenance costs for operators. In addition, existing technical solutions generally need to rely on the cooperation of partners and cannot be decoupled in terms of technical processes. Summary of the invention

[0004] The present invention is intended to provide a method, device, terminal equipment and storage medium for compensating for positioning loss to solve the deficiencies in the prior art. The technical problem to be solved by the present invention is achieved through the following technical solutions.

[0005] A system for realizing operator-specific traffic management by cloud-pipe-end, comprising an end side, a cloud side and a pipe side, wherein the end side is used for VPN proxying of operator application software; the cloud side is used for dispatching proxy data of the VPN proxy to a pre-planned designated IP pool; the pipe side is used for configuring a dedicated traffic billing product package, and separately billing the proxy data in the IP pool according to the configured dedicated traffic billing product package.

[0006] A method for implementing operator-specific traffic management by a cloud-pipe terminal, the specific implementation of which includes the following steps:

[0007] Step S1: Use the full protocol proxy to perform VPN proxy on the operator application software on the terminal side. The specific steps are as follows:

[0008] First, the operator application software applies for network traffic proxy permission from the terminal-side operating system. Specifically, the terminal-side operating system specifies the operator application software to obtain network traffic proxy permission by calling the operating system network interface protocol.

[0009] Then, the terminal operating system grants the operator's application software the authority to act as a network traffic agent and obtains the corresponding network traffic agent protocol. Then, the network agent tool repackages the obtained network traffic agent protocol and uses the repackaged network traffic agent protocol as the full protocol agent.

[0010] Finally, the full-protocol proxy performs VPN proxy on the operator's application software.

[0011] After the above steps, the IP accessed by the wireless network traffic of the operator's application software can be connected to the IP specified by the operator's application software.

[0012] Step S2, the client side sends the proxy data of the operator application software after VPN proxy to the cloud side, and the cloud side dispatches the proxy data to the pre-planned designated IP pool. The specific steps are as follows:

[0013] First, the client side sends the proxy data of the operator application software after VPN proxy to the cloud side; then, the cloud side receives the proxy data sent by the operator application software and establishes a proxy node corresponding to the network proxy tool; then, the established proxy node uniformly schedules and distributes the proxy data; finally, the bill label of the proxy data is marked as dedicated traffic, and the proxy data is scheduled to the pre-planned designated IP pool.

[0014] Through the above steps, the proxy data can be scheduled to the pre-planned designated IP pool, and the IP pool can be mapped to the corresponding call record label.

[0015] Step S3, configure a dedicated traffic billing product package on the pipe side, and separately bill the proxy data in the IP pool according to the configured dedicated traffic billing product package. The specific steps are as follows:

[0016] First, the pipe side configures a dedicated traffic billing product package based on the call record label.

[0017] Then, the proxy data in the IP pool is obtained, and the dedicated IP segment of the proxy data is read; then, based on the read dedicated IP segment, the traffic billing rules for the dedicated IP segment are formulated in the traffic billing product package; finally, the traffic billing product package implements separate billing for the proxy data of the dedicated IP segment based on the formulated traffic billing rules.

[0018] This step configures a dedicated traffic billing product package based on the call record label on the pipe side, and formulates traffic billing rules for proxy data under the dedicated IP segment based on the read dedicated IP segment, so that a dedicated call record label can be mapped to a dedicated traffic billing product package, thereby realizing separate billing of dedicated traffic for proxy data.

[0019] The present invention proposes a system and method for realizing operator-specific traffic management by cloud-pipe-end, which has the following beneficial effects compared with the existing technology:

[0020] The present invention proposes to implement VPN proxy in the operator application software on the end side, dispatch the proxy data of the VPN proxy to a pre-planned designated IP pool on the cloud side, configure a dedicated traffic billing product package on the pipe side, and separately bill the proxy data in the IP pool according to the configured dedicated traffic billing product package, thereby realizing a one-to-one mapping of the entire process from the operator application software, the call bill label, to the traffic billing product package. Moreover, the method does not require large-scale transformation of the network equipment and the billing system, nor does it require the configuration of the partner's server IP on the operator's wireless gateway device, thereby solving the problem of high construction costs and huge maintenance costs for operators existing in traditional technical means. In addition, the method proposed by the present invention does not need to rely on the cooperation of the partner, and decoupling is achieved in the technical process. BRIEF DESCRIPTION OF THE DRAWINGS

[0021] Figure 1 It is a flow chart of the method for implementing operator-specific traffic management by the cloud-pipe terminal of the present invention;

[0022] Figure 2 It is a schematic diagram of the architecture of the cloud-pipe-end implementation of the operator-specific traffic management system of the present invention. DETAILED DESCRIPTION

[0023] In order to make the purpose and features of the present invention more obvious and easy to understand, the present technical solution is described in detail below through embodiments and in conjunction with the accompanying drawings.

[0024] like Figure 2 As shown, a system for implementing operator-specific traffic management by cloud-pipe-end includes an end side, a cloud side and a pipe side, wherein the end side is used to perform VPN proxy for operator application software; the cloud side is used to schedule the proxy data of the VPN proxy to a pre-planned designated IP pool; the pipe side is used to configure a dedicated traffic billing product package, and separately bill the proxy data in the IP pool according to the configured dedicated traffic billing product package.

[0025] like Figure 1 As shown, a method for implementing operator-specific traffic management on a cloud-to-cloud end is implemented in the following steps:

[0026] Step S1: Use the full protocol proxy to perform VPN proxy on the operator application software on the terminal side. The specific steps are as follows:

[0027] First, the operator application software applies for network traffic proxy permission from the terminal-side operating system. Specifically, the terminal-side operating system specifies the operator application software to obtain network traffic proxy permission by calling the operating system network interface protocol.

[0028] In the specific implementation process, the terminal side can be a mobile phone or other mobile terminals; common operator application software include iQiyi, Tencent Video, etc.

[0029] Then, the terminal operating system grants the operator's application software the authority to act as a network traffic agent and obtains the corresponding network traffic agent protocol. Then, the network agent tool repackages the obtained network traffic agent protocol and uses the repackaged network traffic agent protocol as the full protocol agent.

[0030] Optionally, the network proxy tool can be Shadowsocks software, OpenVPN software, etc.

[0031] Finally, the full-protocol proxy performs VPN proxy on the operator's application software.

[0032] After the above steps, the IP accessed by the wireless network traffic of the operator's application software can be connected to the IP specified by the operator's application software.

[0033] Step S2, the client side sends the proxy data of the operator application software after VPN proxy to the cloud side, and the cloud side dispatches the proxy data to the pre-planned designated IP pool. The specific steps are as follows:

[0034] First, the client side sends the proxy data of the operator application software after VPN proxy to the cloud side; then, the cloud side receives the proxy data sent by the operator application software and establishes a proxy node corresponding to the network proxy tool; then, the established proxy node uniformly schedules and distributes the proxy data; finally, the bill label of the proxy data is marked as dedicated traffic, and the proxy data is scheduled to the pre-planned designated IP pool.

[0035] During the specific implementation process, these IP pools are allocated specifically for use as dedicated traffic services, and each IP in the IP pool needs to be specially configured on the operator's network equipment in advance.

[0036] Through the above steps, the proxy data can be scheduled to the pre-planned designated IP pool, and the IP pool can be mapped to the corresponding call record label.

[0037] Step S3, configure a dedicated traffic billing product package on the pipe side, and separately bill the proxy data in the IP pool according to the configured dedicated traffic billing product package. The specific steps are as follows:

[0038] First, the pipe side configures a dedicated traffic billing product package based on the call record label.

[0039] In the specific implementation process, it is necessary to configure a dedicated traffic billing product package according to the specified call bill label. For example, if the call bill label of the proxy data is marked as dedicated traffic in the above steps, the dedicated traffic can be specified to configure the dedicated traffic billing product package.

[0040] Then, the proxy data in the IP pool is obtained, and the dedicated IP segment of the proxy data is read; then, based on the read dedicated IP segment, the traffic billing rules for the dedicated IP segment are formulated in the traffic billing product package; finally, the traffic billing product package implements separate billing for the proxy data of the dedicated IP segment based on the formulated traffic billing rules.

[0041] This step configures a dedicated traffic billing product package based on the call record label on the pipe side, and formulates traffic billing rules for proxy data under the dedicated IP segment based on the read dedicated IP segment, so that a dedicated call record label can be mapped to a dedicated traffic billing product package, thereby realizing separate billing of dedicated traffic for proxy data.

[0042] So far, according to the method disclosed in the present invention, the working process of the present invention has been implemented once.

[0043] The above are only preferred embodiments of the present invention, and are not intended to limit the patent scope of the present invention. Any equivalent structure or equivalent process transformation made using the contents of the present invention specification and drawings, or directly or indirectly applied in other related technical fields, are also included in the patent protection scope of the present invention.

[0044] It should be noted that the serial numbers of the above embodiments of the present invention are only for description and do not represent the advantages and disadvantages of the embodiments. And the terms "including", "comprising" or any other variants thereof in this article are intended to cover non-exclusive inclusion, so that a process, device, article or method including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, device, article or method. In the absence of further restrictions, an element defined by the sentence "including a ..." does not exclude the presence of other identical elements in the process, device, article or method including the element.

Claims

1. A method for implementing operator-specific traffic management by a cloud-pipe terminal, characterized in that: Includes steps: Step S1, using the full protocol proxy to perform VPN proxy on the operator application software on the terminal side, specifically includes the following steps: Step S101, the operator application software applies to the terminal side operating system for network traffic proxy authority. Specifically, the terminal side operating system calls the operating system network interface protocol to specify that the operator application software obtains the network traffic proxy authority. Step S102: The terminal side operating system grants the operator application software the authority to act as a network traffic proxy, and obtains the corresponding network traffic proxy protocol; Step S103, the network proxy tool re-encapsulates the acquired network traffic proxy protocol, and uses the re-encapsulated network traffic proxy protocol as a full-protocol proxy; Step S104, the full-protocol proxy performs VPN proxy on the operator application software; Step S2, the client side sends the proxy data of the operator application software after VPN proxy to the cloud side, and the cloud side dispatches the proxy data to the pre-planned designated IP pool, which specifically includes the following steps: Step S201, the client side sends the proxy data of the operator application software after VPN proxy to the cloud side; Step S202, the cloud side receives the proxy data sent by the operator's application software and establishes a proxy node corresponding to the network proxy tool; Step S203, the established proxy node performs unified scheduling and distribution of the proxy data; Step S204, marking the bill label of the proxy data as dedicated traffic, and dispatching the proxy data to a pre-planned designated IP pool; Step S3, configuring a dedicated traffic billing product package on the pipe side, and separately billing the proxy data in the IP pool according to the configured dedicated traffic billing product package, specifically includes the following steps: Step S301, the pipe side configures a dedicated traffic billing product package according to the call bill label; Step S302, obtaining the proxy data in the IP pool, and reading the dedicated IP segment of the proxy data; Step S303, formulating a traffic billing rule for the dedicated IP segment in the traffic billing product package according to the dedicated IP segment read; Step S304: the traffic billing product package separately bills the proxy data of the dedicated IP segment according to the established traffic billing rules.

2. A system for implementing operator-specific traffic management in a cloud-pipe-end, characterized in that: The operational implementation of the system relies on the method for realizing operator-specific traffic management by cloud-pipe-end as described in claim 1. Specifically, the system includes an end side, a cloud side and a pipe side, wherein the end side is used to perform VPN proxy for operator application software; the cloud side is used to schedule the proxy data of the VPN proxy to a pre-planned designated IP pool; the pipe side is used to configure a dedicated traffic billing product package, and to separately bill the proxy data in the IP pool according to the configured dedicated traffic billing product package.

Images