CN109996201A - A kind of Network Access Method and the network equipment - Google Patents

Abstract

The present invention provides a network access method and network equipment. The method includes: detecting whether an IP address exists in a header field of a service request sent by a user terminal; if so, extracting the IP address, and when a preset condition is met, Determine that the service request is a redirection request; restore the redirection request to an initial service request according to the IP address; and determine whether the target service requested by the initial service request is a charging service according to a preset charging matching rule. The network device of the present invention detects whether there is an IP address in the header field of the service request of the user terminal, and if so, identifies the redirection request according to the IP address. The network device can also restore the redirection request to the initial service request, and then determine whether the target service is a charging service according to the initial service request, so as to solve the charging matching problem of the redirected service request, ensure the correct matching of the redirected service request, and The current charging matching rules can be used to avoid traffic fraud.

Description

A network access method and network device

technical field

The present invention relates to the field of communication technologies, and in particular, to a network access method and network equipment.

Background technique

Service charging is one of the core functions of the operator's core network gateway. The gateway entities with charging functions include: Packet Data Network Gateway (PGW) entity and General Packet Radio Service (General Packet Radio Service, GPRS) gateway support node (Gateway GPRS Support Node, GGSN) entity. Service billing is initially applied to the reduction of the operator's own service traffic, that is, the self-service traffic is exempted, so as to improve the attractiveness and competitiveness of the operator's own service. In recent years, in order to increase the value of traffic, operators have launched many special services such as directional traffic packages (such as: let me see, etc.), and unified payment of traffic (such as: content providers pay for user traffic). Such services need to identify users The service category is differentiated for charging, and the content charging function of the operator's core network gateway is used.

The service charging function is implemented based on the deep packet inspection (Deep Packet Inspection, DPI) capability of the gateway. Specifically, the DPI technology can extract the uniform resource locator (Uniform Resource Locator, URL) field in the Hyper Text Transfer Protocol (Hyper Text Transfer Protocol, HTTP) header in the seven-layer protocol of the service data packet, and match it with the pre-defined service URL rules. Matching is performed to realize the identification of business types. Take the traffic backward unified payment service as an example: Assuming that Sina Sports conducts business promotion, users can visit the Sina Sports page without traffic. The URL rule of this service is: "sports.sina.com.cn/*", and the core network gateway parses the user In the URL field in the HTTP header of the data packet, when the user's URL can match "sports.sina.com.cn/*", the core network gateway will identify the service data flow as Sina Sports' traffic and then pay for it in the unified payment service. The data flow bill (the core network gateway is responsible for generating the traffic bill) identifies a specific service ID (service ID). After receiving the bill, the Business&Operation Support System (BOSS) system processes the user traffic according to the Service ID. Free, generate traffic bills to Sina.

In order to prevent illegal websites from constructing URLs to defraud free/third-party paid traffic, for example, if the URL rule for backward billing is: "*sports.sina.com.cn*", when the URL for accessing services is: "http:/ /www.fakesite.com/fakedir/sports.sina.com.cn/fakecontent” can also match the above-mentioned backward billing rules. In order to avoid this situation, the charging rule matching method is as follows: the HOST part in the URL cannot be replaced with the wildcard "*", and the wildcard "*" in the HOST cannot be wildcarded with "/" to avoid the service request URL. The content in the path matches the keyword in the URL HOST in the content billing rule.

Further, in order to improve the access speed of users accessing network content, the core network stores the network content that users need to access frequently in network nodes that are closer to the user and have faster access speeds, wherein the cache (cache) server is used to store frequently accessed network content. content server. Content Delivery Network (CDN) relies on edge servers deployed in various places, through the load balancing, content distribution, scheduling and other functional modules of the central platform, so that users can obtain the required content nearby, reduce network congestion, and improve user access response speed and hit rate. The basic principle of CDN is to widely use various cache servers, distribute these cache servers to regions or networks where user access is relatively concentrated, and use global load technology to direct users' access to the nearest working cache when users visit a website. On the server, there is a cache server that directly responds to user requests.

Among them, the cache or CDN of video traffic usually redirects the user's access request to the nearest cache server or CDN node by means of redirection. The redirect URL after. The modification method of the redirection URL is to keep the original URL and add the IP address of the cache server or CDN node at the beginning of the URL. Assuming that the original URL used for the request is: "http://apk.r1.market.hiapk.com/data/upload/apkres/2017/6_28/12/com.hnzx.hnrb_122813.apk", then the modified The redirect URL is: "http://112.17.27.140/apk.r1.market.hiapk.com/data/upload/apkres/2017/6_28/12/com.hnzx.hnrb_122813.apk?wsiphost=local", in the original "112.17.27.140/" is added before the URL. This IP address is the IP address of the cache server or CDN node. After the cache server or CDN node receives the redirection request, it will return the cached content required by the user according to the URL after the IP address. .

When the billing URL rule is "apk.r1.market.hiapk.com/*.apk", the original URL can be correctly matched, but the modified URL redirected by the cache server or CDN node is "http://112.17. 27.140/apk.r1.market.hiapk.com/data/upload/apkres/2017/6_28/12/com.hnzx.hnrb_122813.apk?wsiphost=local" does not match correctly. If the billing URL rule is modified to "*/apk.r1.market.hiapk.com/*.apk", the redirected URL can be correctly matched, but traffic fraud cannot be avoided, and the HOST part of the URL that does not match cannot be used with "" *" alternative billing match rule. Therefore, there is an urgent need for a new charging matching method that can not only ensure the correct matching of redirection URLs, but also avoid traffic fraud.

SUMMARY OF THE INVENTION

The present invention provides a network access method and network equipment, which solve the problem of matching redirection URL identification and charging in the prior art.

An embodiment of the present invention provides a network access method, including:

Detect whether there is an IP address in the header field of the service request sent by the user terminal;

If it exists, extract the IP address, and when the IP address meets the preset condition, determine that the service request is a redirection request;

According to the IP address, the redirection request is restored to the original service request;

According to the preset charging matching rule, it is determined whether the target service requested by the initial service request is a charging service.

Wherein, the step of detecting whether there is an IP address in the header field of the service request sent by the user terminal includes:

Receive the service request requesting the target service sent by the user terminal;

Check whether there is an indicator character indicating an IP address in the header field of the service request.

Wherein, after the step of detecting whether there is an IP address in the header field of the service request sent by the user terminal, the method further includes:

If it does not exist, the service request is forwarded.

Wherein, when the IP address meets the preset condition, the step of determining that the service request is a redirection request includes:

Detecting whether the IP address exists in the preset IP address list; wherein, the preset IP address list includes the IP addresses of all cache servers and/or CDN nodes of the content distribution network;

If so, the service request is determined to be a redirection request; otherwise, the service request is forwarded.

Wherein, before the step of detecting whether the IP address exists in the preset IP address list, the method further includes:

Obtain the IP address of each cache server and/or CDN node;

A preset IP address list is generated according to the IP addresses of the cache servers and/or CDN nodes.

Wherein, according to the IP address, the steps of restoring the redirection request to the initial service request include:

Determine the parameter information of the target cache server and/or the target CDN node corresponding to the redirection request according to the preset correspondence between the IP addresses of the cache servers and/or CDN nodes and the parameter information; wherein, one cache server in the preset correspondence Or the IP address of the CDN node corresponds to the parameter information of the same cache server or CDN node;

Detecting whether the redirection request carries a parameter field indicating the parameter information of the target cache server and/or the target CDN node;

If the parameter field is carried, the header field and parameter field of the redirection request are removed to obtain the initial service request.

Wherein, before the step of determining the parameter information of the target cache server and/or the target CDN node corresponding to the redirection request according to the preset correspondence between the IP address of the cache server and/or the CDN node and the parameter information, the method further includes:

Obtain the IP address and parameter information of each cache server and/or CDN node;

According to the IP address and parameter information of the cache server and/or the CDN node, a preset corresponding relationship between the IP address and the parameter information is generated.

Wherein, according to the preset charging matching rule, the step of determining whether the target service requested by the initial service request is a charging service includes:

Detecting whether there is a charging flag field defined by the preset charging matching rule in the initial service request;

If it exists, it is determined whether the target service requested by the initial service request is a charging service; otherwise, it is determined whether the target service requested by the initial service request is a free service.

An embodiment of the present invention also provides a network device, including:

The first detection module is used to detect whether there is an IP address in the header field of the service request sent by the user terminal;

a first processing module, configured to extract the IP address if it exists, and determine that the service request is a redirection request when the IP address meets a preset condition;

The recovery module is used to restore the redirection request to the initial service request according to the IP address;

The charging module is configured to determine whether the target service requested by the initial service request is a charging service according to a preset charging matching rule.

Wherein, the first detection module includes:

a first receiving sub-module, configured to receive a service request requesting a target service sent by a user terminal;

The first detection submodule is used for detecting whether there is an indicator character indicating an IP address in the header field of the service request.

Among them, the network equipment also includes:

The first forwarding module is configured to forward the service request if it does not exist.

Wherein, the first processing module includes:

The second detection sub-module is used to detect whether the IP address exists in the preset IP address list; wherein, the preset IP address list includes the IP addresses of all cache servers and/or content distribution network CDN nodes;

The first processing submodule is configured to determine that the service request is a redirection request if yes; otherwise, forward the service request.

Wherein, the first processing module further includes:

The first obtaining submodule is used to obtain the IP addresses of each cache server and/or CDN node;

The first generating sub-module is configured to generate a preset IP address list according to the IP addresses of the cache server and/or the CDN node.

Among them, the recovery module includes:

The second processing sub-module is configured to determine the parameter information of the target cache server and/or the target CDN node corresponding to the redirection request according to the preset correspondence between the IP address of the cache server and/or the CDN node and the parameter information; wherein, The IP address of a cache server or CDN node in the preset corresponding relationship corresponds to the parameter information of the same cache server or CDN node;

A third detection submodule, configured to detect whether the redirection request carries a parameter field indicating parameter information of the target cache server and/or the target CDN node;

The recovery submodule is used to remove the header field and the parameter field of the redirection request if the parameter field is carried to obtain the initial service request.

Among them, the recovery module also includes:

The second acquisition sub-module is used to acquire the IP address and parameter information of each cache server and/or CDN node;

The second generating sub-module is configured to generate a preset corresponding relationship between the IP address and the parameter information according to the IP address and parameter information of the cache server and/or the CDN node.

Among them, the billing module includes:

a fourth detection submodule, configured to detect whether there is a charging flag field defined by a preset charging matching rule in the initial service request;

The charging sub-module is configured to determine whether the target service requested by the initial service request is a charging service if it exists; otherwise, determine whether the target service requested by the initial service request is a free service.

An embodiment of the present invention also provides a network device, comprising: a processor; a memory connected to the processor, and a transceiver connected to the processor; wherein the processor is used to call and execute a program stored in the memory and data to implement the steps of the above-mentioned network access method.

The beneficial effects of the above technical solutions of the present invention are: after receiving the service request, the network device detects whether there is an IP address in the header field of the service request of the user terminal, and when there is an IP address in the header field of the service request, according to The IP address determines whether the service request is a redirection request, so as to realize the identification of the redirection request. In addition, the network device can restore the redirection request to the initial service request, and then determine whether the requested target service is a charging service according to the initial service request, solve the charging matching problem of the redirection service request, and ensure the correctness of the redirection service request. If it matches, the current charging matching rules can be used to avoid traffic fraud.

Description of drawings

1 shows a schematic flowchart of a network access method according to an embodiment of the present invention;

2 is a schematic diagram of a module of a network device according to an embodiment of the present invention;

FIG. 3 shows a block diagram of a network device according to an embodiment of the present invention.

Detailed ways

In order to make the technical problems, technical solutions and advantages to be solved by the present invention more clear, the following will be described in detail with reference to the accompanying drawings and specific embodiments. In the following description, specific details such as specific configurations and components are provided merely to assist in a comprehensive understanding of embodiments of the present invention. Accordingly, it should be apparent to those skilled in the art that various changes and modifications of the embodiments described herein can be made without departing from the scope and spirit of the invention. Also, descriptions of well-known functions and constructions are omitted for clarity and conciseness.

It is to be understood that reference throughout the specification to "one embodiment" or "an embodiment" means that a particular feature, structure or characteristic associated with the embodiment is included in at least one embodiment of the present invention. Thus, appearances of "in one embodiment" or "in an embodiment" in various places throughout this specification are not necessarily necessarily referring to the same embodiment. Furthermore, the particular features, structures or characteristics may be combined in any suitable manner in one or more embodiments.

In various embodiments of the present invention, it should be understood that the size of the sequence numbers of the following processes does not mean the sequence of execution, and the execution sequence of each process should be determined by its functions and internal logic, rather than the implementation of the present invention The implementation of the examples constitutes no limitation.

Additionally, the terms "system" and "network" are often used interchangeably herein.

In the embodiments provided in this application, it should be understood that "B corresponding to A" means that B is associated with A, and B can be determined according to A. However, it should also be understood that determining B according to A does not mean that B is only determined according to A, and B may also be determined according to A and/or other information.

As shown in FIG. 1, an embodiment of the present invention provides a network access method, which specifically includes the following steps:

Step 11: Detect whether there is an IP address in the header field of the service request sent by the user terminal.

Wherein, this refers to that when the network device receives the service request sent by the user terminal, it detects whether there is an IP address in the header field of the service request. The network device especially refers to a GGSN entity or a P-GW entity with a charging function. The service request mentioned here is parsed by the GGSN entity or the P-GW entity to obtain the Uniform Resource Locator URL. When the user terminal has a service request, especially when an HTTP request occurs, the GGSN entity or the P-GW entity analyzes the URL. The seven-layer URL is used to obtain the URL of the target access address of the HTTP request. According to the target access address, it is possible to determine which type of service the HTTP request belongs to, and classify it into the corresponding chargeable service or free service. In this embodiment of the present invention, the GGSN entity or the P-GW entity is capable of detecting whether there is an IP address in a character IP address format in the HOST field (header field) of the URL in addition to the above-mentioned parsing capability.

Step 12: If it exists, extract the IP address, and when the IP address meets the preset condition, determine that the service request is a redirection request.

If it exists, the identification function of the redirection request is triggered. If it does not exist, the charging matching is performed directly according to the preset charging matching rules, that is, according to the preset charging matching rules, it is determined whether the target service requested by the service request is billing service, and forward the service request. The redirection request identification process is as follows: the GGSN entity or the P-GW entity extracts the IP address in the HOST field in the URL, and determines the service request as a redirection request when the IP address meets a preset condition.

Step 13: Restore the redirection request to the original service request according to the IP address.

Here, it means that, in addition to the redirection request identification function, the network device also has the recovery function of restoring the redirection request to the original service request. Specifically, the GGSN entity or the P-GW entity extracts the IP address from the redirection request, and restores the redirection request to the initial service request.

Step 14: According to the preset charging matching rule, determine whether the target service requested by the initial service request is a charging service.

The preset charging matching rule is a matching rule with anti-traffic fraud. For example, as mentioned in the background art, the HOST field in the URL cannot be replaced with the wildcard "*", and the wildcard "*" in the HOST cannot be wildcarded "/" to avoid the situation where the content in the path of the service request URL matches the keyword in the URL HOST in the content charging rule. According to the preset charging matching rule, the initial service request of the redirection request is matched to determine whether the service requested by the redirection request is a charging service.

Specifically, step 11 specifically includes: receiving a service request requesting a target service sent by a user terminal; and detecting whether an indicator character indicating an IP address exists in a header field of the service request. When the user terminal has a service request, especially when an HTTP request occurs, the GGSN entity or the P-GW entity receives the TTTP request sent by the user terminal, and obtains the URL of the target access address of the HTTP request by parsing the seven-layer URL, The GGSN entity or the P-GW entity further detects whether there is an IP address in a character IP address format in the HOST field (header field) of the URL. If it exists, the redirection request identification function is triggered, and if it does not exist, the normal charging matching function is triggered.

Specifically, step 12 includes: detecting whether the IP address exists in the preset IP address list; if so, determining that the service request is a redirection request; otherwise, forwarding the service request. The preset IP address list includes the IP addresses of all cache servers and/or CDN nodes of the content distribution network. That is to say, when the GGSN entity or the P-GW entity detects that there is an IP address in the format of a character IP address in the HOST field of the URL, it extracts the character IP address in the HOST of the URL, and communicates with the CACHE server and/or after processing. Or the preset IP address list of the CDN node is compared. If the IP address is not in the list, the normal charging matching function is triggered; if the IP address is in the list, it means that the URL is the URL after CACHE/CDN redirection. The recovery function of the initial service request is triggered, that is, the URL recovery function is called.

Among them, it is worth pointing out that before the step of detecting whether the IP address exists in the preset IP address list, the step further includes: obtaining the IP addresses of each cache server and/or CDN node; according to the IP address of the cache server and/or CDN node to generate a list of preset IP addresses. That is, the content charging gateway entity, that is, the GGSN entity or the P-GW entity, sets the preset IP address list of the CACHE server and the CDN node, and the preset IP address list is updated in real time according to the address list of the CACHE server and the CDN node.

Trigger the restoration function of the initial service request, that is, after calling the URL restoration function, the GGSN entity or the P-GW entity restores the redirection request to the initial service request according to the IP address. Specifically, step 14 includes: determining the parameter information of the target cache server and/or the target CDN node corresponding to the redirection request according to the preset correspondence between the IP addresses of the cache server and/or the CDN node and the parameter information; detecting the redirection Whether the request carries the parameter field indicating the parameter information of the target cache server and/or the target CDN node; if it carries the parameter field, remove the header field and parameter field of the redirection request to obtain the initial service request, otherwise it will repeat the request. The header field of the directional request is removed to obtain the initial service request. Wherein, the IP address of one cache server or CDN node in the preset correspondence relationship corresponds to the parameter information of the same cache server or CDN node.

Specifically, in order to better match the cache server and/or the CDN node, a parameter field indicating the parameter information of the target cache server and/or the target CDN node is added to the redirection request. A CACHE server or CDN node has a unique IP address, in addition, a CACHE server or CDN node may also have at least one parameter information. There is a preset correspondence between the IP address of a CACHE server or CDN node and the parameter information, that is, the IP address of one cache server or CDN node corresponds to the parameter information of the same cache server or CDN node. In the initial service request recovery process, the GGSN entity or the P-GW entity determines the parameter information that may be carried in the redirection request according to the preset correspondence between the IP address and the parameter information; it is only the parameter that detects whether the received redirection request exists. The parameter field of the information; if it exists, remove the header field indicating the IP address and the parameter field indicating the parameter information in the redirection request to obtain the initial service request; if it does not exist, only the header indicating the IP address in the redirection request will be removed. Part field removal to get the initial service request.

Wherein, before the step of determining the parameter information of the target cache server and/or the target CDN node corresponding to the redirection request according to the preset correspondence between the IP addresses of the cache server and/or the CDN nodes and the parameter information, the step further includes: acquiring each cache The IP address and parameter information of the server and/or the CDN node; according to the IP address and parameter information of the cache server and/or the CDN node, a preset corresponding relationship between the IP address and the parameter information is generated. That is to say, the content charging gateway entity, that is, the GGSN entity or the P-GW entity, sets a preset correspondence between the IP addresses of the CACHE server and the CDN node and the parameter information, and the preset correspondence is based on the CACHE server and the CDN node. The address list is updated in real time.

Step 14 specifically includes: detecting whether there is a charging flag field defined by the preset charging matching rule in the initial service request; if there is, determining whether the target service requested by the initial service request is a charging service, otherwise determining the initial service request Whether the requested target service is a free service. Assume that the preset charging matching rules are: the HOST field in the URL of the service request cannot be replaced with the wildcard "*", and the wildcard "*" in the HOST cannot be wildcarded with "/", and the billing mark field will be billed later. is "sports.sina.com.cn*", when the URL for accessing the business is: "http://www.fakesite.com/fakedir/sports.sina.com.cn/fakecontent", the above backward system cannot be matched The payment charging rule avoids the situation that the content in the path of the service request URL matches the keyword in the URL HOST in the content charging rule.

In the network access method of the present invention, after receiving the service request, the network device detects whether an IP address exists in the header field of the service request of the user terminal, and when there is an IP address in the header field of the service request, it is determined according to the IP address. Whether the service request is a redirection request, so as to realize the identification of the redirection request. In addition, the network device can restore the redirection request to the initial service request, and then determine whether the requested target service is a charging service according to the initial service request, solve the charging matching problem of the redirection service request, and ensure the correctness of the redirection service request. If it matches, the current charging matching rules can be used to avoid traffic fraud.

The above embodiments respectively introduce the network access method of the present invention, and the corresponding network device will be further described in this embodiment with reference to the accompanying drawings below.

Specifically, as shown in FIG. 2 , the network device 200 according to the embodiment of the present invention includes:

The first detection module 210 is used to detect whether there is an IP address in the header field of the service request sent by the user terminal;

The first processing module 220 is configured to extract the IP address if it exists, and determine that the service request is a redirection request when the IP address meets a preset condition;

Restoring module 230, configured to restore the redirection request to the initial service request according to the IP address;

The charging module 240 is configured to determine whether the target service requested by the initial service request is a charging service according to a preset charging matching rule.

Wherein, the first detection module 210 includes:

a first receiving sub-module, configured to receive a service request requesting a target service sent by a user terminal;

The first detection submodule is used for detecting whether there is an indicator character indicating an IP address in the header field of the service request.

Wherein, the network device 200 further includes:

The first forwarding module is configured to forward the service request if there is no IP address in the header field of the service request.

Wherein, the first processing module 220 includes:

The second detection sub-module is used to detect whether the IP address exists in the preset IP address list; wherein, the preset IP address list includes the IP addresses of all cache servers and/or content distribution network CDN nodes;

The first processing submodule is configured to determine that the service request is a redirection request if yes; otherwise, forward the service request.

Wherein, the first processing module 220 further includes:

The first obtaining submodule is used to obtain the IP addresses of each cache server and/or CDN node;

The first generating sub-module is configured to generate a preset IP address list according to the IP addresses of the cache server and/or the CDN node.

Wherein, the recovery module 230 includes:

The second processing sub-module is configured to determine the parameter information of the target cache server and/or the target CDN node corresponding to the redirection request according to the preset correspondence between the IP address of the cache server and/or the CDN node and the parameter information; wherein, The IP address of a cache server or CDN node in the preset corresponding relationship corresponds to the parameter information of the same cache server or CDN node;

A third detection submodule, configured to detect whether the redirection request carries a parameter field indicating parameter information of the target cache server and/or the target CDN node;

The recovery submodule is used to remove the header field and the parameter field of the redirection request if the parameter field is carried to obtain the initial service request.

Wherein, the recovery module 230 further includes:

The second acquisition sub-module is used to acquire the IP address and parameter information of each cache server and/or CDN node;

The second generating sub-module is configured to generate a preset corresponding relationship between the IP address and the parameter information according to the IP address and parameter information of the cache server and/or the CDN node.

Wherein, the charging module 240 includes:

a fourth detection submodule, configured to detect whether there is a charging flag field defined by a preset charging matching rule in the initial service request;

The charging sub-module is configured to determine whether the target service requested by the initial service request is a charging service if it exists; otherwise, determine whether the target service requested by the initial service request is a free service.

The network device embodiments of the present invention correspond to the foregoing method embodiments, and all implementation means in the foregoing method embodiments are applicable to the network device embodiments, and the same technical effects can also be achieved. After receiving the service request, the network device detects whether there is an IP address in the header field of the service request of the user terminal, and when there is an IP address in the header field of the service request, determines whether the service request is a redirection according to the IP address request to enable the identification of redirected requests. In addition, the network device can restore the redirection request to the initial service request, and then determine whether the requested target service is a charging service according to the initial service request, solve the charging matching problem of the redirection service request, and ensure the correctness of the redirection service request. If it matches, the current charging matching rules can be used to avoid traffic fraud.

In order to better achieve the above purpose, as shown in FIG. 3, an embodiment of the present invention further provides a network device, the network device includes: a processor 300; a memory 320 connected to the processor 300 through a bus interface , and a transceiver 310 connected to the processor 300 through a bus interface; the memory 320 is used to store programs and data used by the processor when performing operations; data information or pilot frequencies are sent through the transceiver 310 , and also receive the uplink control channel through the transceiver 310; when the processor 300 calls and executes the program and data stored in the memory 320, the following functions are implemented:

The processor 300 is configured to read the program in the memory 320, and perform the following process: detect whether there is an IP address in the header field of the service request sent by the user terminal;

If it exists, extract the IP address, and when the IP address meets the preset condition, determine that the service request is a redirection request;

According to the IP address, the redirection request is restored to the original service request;

According to the preset charging matching rule, it is determined whether the target service requested by the initial service request is a charging service.

The transceiver 310 is used for receiving and transmitting data under the control of the processor 300 .

Specifically, the transceiver 310 is configured to receive and send data under the control of the processor 300, and is specifically configured to: receive a service request for a target service sent by a user terminal;

The processor 300 is further configured to: detect whether there is an indicator character indicating the IP address in the header field of the service request.

Specifically, the processor 300 is further configured to: forward the service request if the IP address does not exist in the header field of the service request.

Specifically, the processor 300 is further configured to: detect whether the IP address exists in the preset IP address list; wherein, the preset IP address list includes the IP addresses of all cache servers and/or content distribution network CDN nodes;

If so, the service request is determined to be a redirection request; otherwise, the service request is forwarded.

Specifically, the processor 300 is further configured to: obtain the IP addresses of each cache server and/or CDN node;

A preset IP address list is generated according to the IP addresses of the cache servers and/or CDN nodes.

Specifically, the processor 300 is further configured to: determine the parameter information of the target cache server and/or the target CDN node corresponding to the redirection request according to the preset correspondence between the IP address of the cache server and/or the CDN node and the parameter information; Wherein, the IP address of a cache server or CDN node in the preset corresponding relationship corresponds to the parameter information of the same cache server or CDN node;

Detecting whether the redirection request carries a parameter field indicating the parameter information of the target cache server and/or the target CDN node;

If the parameter field is carried, the header field and parameter field of the redirection request are removed to obtain the initial service request.

Specifically, the processor 300 is further configured to: obtain the IP addresses and parameter information of each cache server and/or CDN node;

According to the IP address and parameter information of the cache server and/or the CDN node, a preset corresponding relationship between the IP address and the parameter information is generated.

Specifically, the processor 300 is further configured to: detect whether there is a charging flag field defined by a preset charging matching rule in the initial service request;

If it exists, it is determined whether the target service requested by the initial service request is a charging service; otherwise, it is determined whether the target service requested by the initial service request is a free service.

3, the bus architecture may include any number of interconnected buses and bridges, specifically one or more processors represented by processor 300 and various circuits of memory represented by memory 320 are linked together. The bus architecture may also link together various other circuits, such as peripherals, voltage regulators, and power management circuits, which are well known in the art and, therefore, will not be described further herein. The bus interface provides the interface. Transceiver 310 may be a number of elements, including a transmitter and a transceiver, providing a means for communicating with various other devices over a transmission medium. The processor 300 is responsible for managing the bus architecture and general processing, and the memory 320 may store data used by the processor 300 in performing operations.

Those skilled in the art can understand that all or part of the steps of implementing the above embodiments can be completed by hardware, or can be completed by instructing relevant hardware through a computer program, where the computer program includes instructions for executing part or all of the steps of the above method ; and the computer program can be stored in a readable storage medium, and the storage medium can be any form of storage medium.

In addition, it should be pointed out that, in the apparatus and method of the present invention, obviously, each component or each step can be decomposed and/or recombined. These disaggregations and/or recombinations should be considered as equivalents of the present invention. Also, the steps of performing the above-mentioned series of processes can naturally be performed in chronological order in the order described, but need not necessarily be performed in chronological order, and some steps can be performed in parallel or independently of each other. Those of ordinary skill in the art can understand that all or any steps or components of the method and device of the present invention can be implemented in any computing device (including a processor, storage medium, etc.) or a network of computing devices in hardware, firmware, etc. , software or a combination thereof, which can be realized by those of ordinary skill in the art using their basic programming skills after reading the description of the present invention.

Accordingly, the objects of the present invention can also be achieved by running a program or set of programs on any computing device. The computing device may be a known general purpose device. Therefore, the object of the present invention can also be achieved only by providing a program product containing program code for implementing the method or apparatus. That is, such a program product also constitutes the present invention, and a storage medium storing such a program product also constitutes the present invention. Obviously, the storage medium can be any known storage medium or any storage medium developed in the future. It should also be pointed out that, in the device and method of the present invention, obviously, each component or each step can be decomposed and/or recombined. These disaggregations and/or recombinations should be considered as equivalents of the present invention. Also, the steps of executing the above-described series of processes can naturally be executed in chronological order in the order described, but need not necessarily be executed in chronological order. Certain steps may be performed in parallel or independently of each other.

The above are the preferred embodiments of the present invention. It should be pointed out that for those skilled in the art, without departing from the principles of the present invention, several improvements and modifications can be made. It should be regarded as the protection scope of the present invention.

Claims (17)

1. a kind of Network Access Method characterized by comprising

It detects and whether there is IP address in the header fields for the service request that user terminal is sent；

If it exists, then the IP address is extracted, and when the IP address meets preset condition, determines that the service request is attached most importance to Orientation request；

According to the IP address, the redirection request is reverted into initial service request；

According to default charging matching rule, determine whether the requested target service of the initial service request is call charge service.

2. Network Access Method according to claim 1, which is characterized in that the business that the detection user terminal is sent is asked The step of whether there is IP address in the header fields asked, comprising:

Receive the service request for the request target business that user terminal is sent；

It detects in the header fields of the service request with the presence or absence of the pointing character of instruction IP address.

3. Network Access Method according to claim 1, which is characterized in that the business that the detection user terminal is sent is asked After the step of whether there is IP address in the header fields asked, further includes:

If it does not exist, then the service request is forwarded.

4. Network Access Method according to claim 1, which is characterized in that when the IP address meets preset condition, Determine the step of service request is redirection request, comprising:

Detecting the IP address whether there is in preset IP address list；Wherein, comprising complete in the preset IP address list The IP address of portion's cache server and/or content distributing network CDN node；

If so, determining that the service request is redirection request；Otherwise the service request is forwarded.

5. Network Access Method according to claim 4, which is characterized in that the detection IP address whether there is in Before step in preset IP address list, further includes:

Obtain the IP address of each cache server and/or CDN node；

According to the cache server and/or the IP address of CDN node, preset IP address list is generated.

6. Network Access Method according to claim 1, which is characterized in that it is described according to the IP address, it will be described heavy The step of orientation request reverts to initial service request, comprising:

According to the default corresponding relationship of the IP address and parameter information of cache server and/or CDN node, the redirection is determined The parameter information of the corresponding target cache server of request and/or target CDN node；Wherein, in the default corresponding relationship The IP address of one cache server or CDN node corresponds to the parameter information of same cache server or CDN node；

The parameter letter that instruction target cache server and/or target CDN node whether are carried in the redirection request detected The parameter field of breath；

If carrying parameter field, the header fields of the redirection request and parameter field are removed, initial service is obtained Request.

7. Network Access Method according to claim 6, which is characterized in that described to be saved according to cache server and/or CDN The IP address of point and the default corresponding relationship of parameter information, determine target cache server corresponding to the redirection request And/or target CDN node parameter information the step of before, further includes:

Obtain the IP address and parameter information of each cache server and/or CDN node；

According to the cache server and/or the IP address and parameter information of CDN node, the pre- of IP address and parameter information is generated If corresponding relationship.

8. Network Access Method according to claim 1, which is characterized in that the basis presets charging matching rule, really The step of whether fixed requested target service of initial service request is call charge service, comprising:

It detects in the initial service request with the presence or absence of the billing flag field defined with the default charging matching rule；

If it exists, it is determined that whether the requested target service of initial service request is call charge service, otherwise determine described in Whether the requested target service of initial service request is coin free service.

9. a kind of network equipment characterized by comprising

First detection module, with the presence or absence of IP address in the header fields of the service request for detecting user terminal transmission；

First processing module, for if it exists, then extracting the IP address, and when the IP address meets preset condition, really The fixed service request is redirection request；

Recovery module, for according to the IP address, the redirection request to be reverted to initial service request；

Accounting module, for determining that the requested target service of the initial service request is according to charging matching rule is preset No is call charge service.

10. the network equipment according to claim 9, which is characterized in that the first detection module includes:

First receiving submodule, the service request of the request target business for receiving user terminal transmission；

First detection sub-module, with the presence or absence of the instruction word of instruction IP address in the header fields for detecting the service request Symbol.

11. the network equipment according to claim 9, which is characterized in that the network equipment further include:

First forwarding module, if forwarding the business to ask for IP address to be not present in the header fields of the service request It asks.

12. the network equipment according to claim 9, which is characterized in that first processing module includes:

Second detection sub-module whether there is in preset IP address list for detecting the IP address；Wherein, described default IP address in IP address list comprising whole cache servers and/or content distributing network CDN node；

First processing submodule is used for if so, determining that the service request is redirection request；Otherwise the business is forwarded to ask It asks.

13. the network equipment according to claim 12, which is characterized in that the first processing module further include:

First acquisition submodule, for obtaining the IP address of each cache server and/or CDN node；

First generates submodule, for the IP address according to the cache server and/or CDN node, generates preset IP address List.

14. the network equipment according to claim 9, which is characterized in that the recovery module includes:

Second processing submodule, for according to the default corresponding of the IP address of cache server and/or CDN node and parameter information Relationship determines target cache server and/or the parameter information of target CDN node corresponding to the redirection request；Wherein, The IP address of a cache server or CDN node corresponds to same cache server or CDN node in the default corresponding relationship Parameter information；

Third detection sub-module, for detect whether carried in the redirection request instruction target cache server and/or The parameter field of the parameter information of target CDN node；

Restore submodule, if removing the header fields of the redirection request and parameter field for carrying parameter field It removes, obtains initial service request.

15. the network equipment according to claim 14, which is characterized in that the recovery module further include:

Second acquisition submodule, for obtaining the IP address and parameter information of each cache server and/or CDN node；

Second generates submodule, for the IP address and parameter information according to the cache server and/or CDN node, generates The default corresponding relationship of IP address and parameter information.

16. the network equipment according to claim 9, which is characterized in that the accounting module includes:

4th detection sub-module, for detecting in the initial service request with the presence or absence of fixed with the default charging matching rule The billing flag field of justice；

Charging submodule, for if it exists, it is determined that whether the requested target service of initial service request is charging industry Business, otherwise determines whether the requested target service of the initial service request is coin free service.

17. a kind of network equipment characterized by comprising processor；The memory being connected with the processor, Yi Jiyu The transceiver that processor is connected；Wherein, the processor be used to call and execute the program that is stored in the memory and Data, the step of realizing Network Access Method as claimed in any one of claims 1 to 8.