JP5636113B2 - Distinct processing of data traffic using adaptation of network address lookup - Google Patents

Description

  The present invention relates to a method for different processing of network traffic, and to a corresponding network device and network system.

  In a communication network, differentiated processing of data traffic may be used to distinguish different classes of data traffic. For example, the data packet forwarding process, i.e. the method of forwarding data packets on their way to the destination, may be controlled to provide a specific quality of service (QoS) level depending on the class of traffic. In other examples, the processing of data traffic may also be distinguished with respect to billing. That is, one traffic class may be charged differently than another traffic class. Usually, traffic class classification rules (eg, packet class classification rules) are defined to implement various classes of data traffic.

  For example, in a mobile communication network, data traffic associated with a particular service may be directed to a bearer that provides a particular QoS level. In this respect, bearers are considered information transmission contexts or paths with defined characteristics (eg capacity, delay or bit error rate or combinations thereof). Typically, many bearers will be established between a mobile communication network gateway and a user equipment (UE), for example a mobile phone or other type of mobile terminal. The bearer carries downlink (DL) data traffic in the direction from the network to the user equipment and carries data traffic in the uplink (UL) direction from the user equipment to the network. In a gateway and user equipment, data traffic including multiple IP data packets (IP: “Internet Protocol”, IP version 4 also referred to as IPv4 or IP version 6 also referred to as IPv6) can be, for example, an IP 5-tuple packet Filtered using a filter, whereby the IP data packet is directed to the desired bearer. According to 3GPP (Third Generation Partnership Project) Technical Specifications (TS) 23.060 and 24.301, a set of packet filters used to direct data traffic to a specific bearer is a traffic flow template (TFT). ). In this context, TFT is considered an example of a packet class classification rule.

  The differentiated processing of data traffic is also useful in other types of communication network environments that use fixed access technologies such as DSL (digital subscriber line), fiber optic access or coaxial cable access.

  In addition, it may be desirable to apply differentiated processing to data traffic associated with specific network resources. For example, data traffic associated with a particular network resource that is a particular Internet service or a particular content provider may be known to require a particular QoS level. However, in some examples, it may be difficult to determine the required processing based on the data traffic itself. On the other hand, differentiated processing can be similarly implemented based on known network addresses used by these specific network resources. However, this creates problems when it is necessary to handle many specific network resources that may use a variety of different network addresses. Therefore, fairly complex traffic class classification rules need to be defined to take into account many arbitrary network addresses. This is particularly problematic when considering the limitations on the complexity of traffic classification rules in some communication network environments. For example, 3GPP TS limits the maximum number of packet filters that can be installed in a UE's TFT.

  Therefore, there is a need for techniques that allow for efficient and differentiated processing of network traffic associated with specific network resources.

  According to one embodiment of the present invention, a method for differentiated processing of data traffic is provided. Data traffic is associated with a network resource and is preceded by a lookup procedure that obtains the network address of the network resource. According to this method, the search procedure message is processed to adapt the search procedure. Depending on the adaptation, the search procedure returns the network address of the alternative network resource. The alternative network resource can be an alternative to the network resource in communication of data packets of data traffic. Based on the network address of the alternative network resource, differentiated processing of the data packet in the communication with the alternative network resource is achieved.

  According to a further embodiment of the invention, a network device is provided. The network device includes an interface for receiving a search procedure message for obtaining a network address of a network resource. Further, the network device includes a processor. The processor is configured to process the received message to adapt the search procedure to return the network address of the alternative network resource. The alternative network resource can be an alternative to the network resource in data packet communication. Based on the network address of the alternative network resource, differentiated processing of the data packet in the communication with the alternative network resource is achieved.

  According to a further embodiment of the present invention, a network system is provided. The network system includes an alternative network resource, a network device, and at least one communication device. The alternative network resource can be an alternative to the network resource in data packet communication. The network device is configured to process a search procedure message to obtain a network address of a network resource. With this process, the search procedure is adapted to return the network address of the alternative network resource. At least one communication device is configured to achieve differentiated processing of data packets in the communication with the alternative network resource based on the network address of the alternative network resource.

  According to further embodiments, another method, apparatus or computer program for implementing the method is provided.

FIG. 1 is a diagram schematically showing a communication network environment in which a concept according to an embodiment of the present invention is realized. FIG. 2 is a signaling diagram illustrating an exemplary example in which differentiated processing of data traffic is applicable according to an embodiment of the present invention. FIG. 3 is a signaling diagram illustrating a further exemplary example in which differentiated processing of data traffic is applicable according to an embodiment of the present invention. FIG. 4 is a diagram schematically illustrating a network device according to an embodiment of the present invention. FIG. 5 is a flowchart illustrating a method according to an embodiment of the present invention.

  In the following, the invention will be described in more detail with reference to exemplary embodiments and the accompanying drawings. The illustrated embodiment relates to the concept for differentiated processing of network traffic. As shown in FIG. 1, this concept is applied in a mobile communication network according to 3GPP TS. However, it should be understood that the concepts shown apply equally in other types of communication networks using fixed access technologies such as DSL, fiber optic access or coaxial cable access.

  FIG. 1 schematically shows a communication network environment to which the concept according to the embodiment of the present invention is applicable.

  The communication network environment includes a UE 10, also called a terminal, and a number of network components 22, 24, 26, 30. Among these network components is a radio access network (RAN) 22. The RAN 22 is, for example, GSM (pan-European digital mobile communication system), EDGE (high-speed data for extension of GSM), UMTS (universal mobile communication system), wideband code division multiple access (WCDMA), or LTE (Long Term Evolution) 1 Based on one or more specific types of radio access technologies. Although RAN 22 is shown as a single node, it should be understood that RAN 22 may actually be formed from a number of components that are not further described herein. The RAN 22 is coupled to a transport node 24, which is coupled to a gateway (GW) 26. In this case, it should be understood that two or more transport nodes 24 may alternatively be coupled between the RAN 22 and the gateway 26, or the RAN 22 may be coupled directly to the gateway 26. The gateway 26 may be a gateway GPRS support node (GGSN) that provides a connection from a GPRS based service to one or more external packet data networks. The gateway 26 may be a system architecture evolution gateway (SAE GW) according to 3GPP TS.

  Furthermore, the mobile communication network includes a policy controller 30 implemented as a policy / charging rule function (PCRF) according to 3GPP TS. Policy controller 30 is implemented with dedicated hardware and / or includes software functions executed by a processor. The gateway 26 and policy controller 30 are generally considered as components of the core network. Policy controller 30 communicates with gateway 26 via signaling path 6, which may be implemented using a Gx interface according to 3GPP TS. The policy controller 30 is a subscriber database 32, for example a home location register (HLR) or a home subscriber server (HSS) according to 3GPP TS, via a signaling path 8 implemented using, for example, an Sp interface according to 3GPP TS. And the service policy database 34. Accordingly, the policy controller 30 receives policy data associated with a particular user or associated with a particular service available in a mobile communication network, eg, a mobile TV, or both. The policy controller 30 further communicates with other network functions using the control signaling path 5 implemented using the Rx interface according to 3GPP TS.

  Among other functions, the policy controller 30 may include a filter generator 35. The filter generator 35 is configured to specify a packet filter used in the UE 10 and the gateway 26. This is accomplished based on subscription data from subscription database 32, service policy from service policy database 34, and control data received via signaling path 5. A packet filter is an example of a packet class classification rule that is used to provide different QoS service levels depending on the type of traffic in the example shown. In other examples, packet filters or other packet classification rules are used to distinguish between different billing methods, to selectively block specific traffic types, also called gating, or to selectively redirect specific traffic types. Is done.

  As further shown, data traffic between the network and user equipment 10 is carried by a number of bearers 52, 54 established over the radio interface between UE 10 and RAN 22. Data traffic relates to one or more client / peer applications 12 that typically run on the UE 10 and relate to specific network resources that are, for example, Internet service or content providers. Bearers 52 and 54 are established between the user equipment 10 and the gateway 26. The bearers 52 and 54 carry data traffic in both the DL direction and the UL direction. That is, it is further considered that the bearers 52 and 54 are formed of DL bearers and UL bearers. In order to support bi-directional communication at the bearers 52, 54, the UE 10 has a corresponding interface 15 that enables reception of input data packets from the bearers 52, 54 and transmission of output data packets on the bearers 52, 54. Prepare. Similarly, the gateway 26 includes a corresponding interface 25 that allows reception of input data packets from the bearers 52, 54 and transmission of output data packets on the bearers 52, 54. The bearers 52, 54 are typically a default bearer 52 that is established to provide packet utilization services to the user equipment 10, and one or more dedicated bearers having a QoS level that is different from the default bearer, for example, a higher or lower QoS level. A bearer 54. The default bearer 52 is typically established when the UE 10 connects to the gateway 26 and receives its IP address and IP connectivity. The dedicated bearer 54 is typically established on demand, such as when a data packet that requires a particular QoS level needs to be transmitted. However, in some embodiments, a dedicated bearer may be pre-established, such as when connecting to the gateway 26 of the UE 10. Each bearer 52, 54 is associated with a corresponding QoS profile. The QoS profile includes a QoS class identifier (QCI), an ARP (Allocation / Retention Priority), a THP (Traffic Handling Priority), a maximum bit rate (MBR), an overall maximum bit rate (AMBR), and a guaranteed bit rate (GBR). It is defined through parameters such as combinations. Thus, by assigning a data packet to the corresponding one of the bearers 52, 54, a specific QoS level is provided for data packet communication between the UE 10 and the gateway 26.

  In the UE 10, the data packets are routed to the desired bearers 52, 54 in the form of UL packet filters 62, 64 using correspondingly configured packet class classification rules. At the gateway 26, the data packets are routed in the form of DL packet filters 72, 74 to the desired bearers 52, 54 using correspondingly configured packet class classification rules. In accordance with the 3GPP example shown, a set of filters 62, 64, 72, 74 that operate to direct data packets to corresponding bearers may be referred to as TFTs. The parameters of the QoS profile are signaled from the policy controller 30 to the gateway 26 using the signaling path 6. Similarly, DL packet filters 72 and 74 used in the gateway 26 are signaled from the policy controller 30 to the gateway 26 via the signaling path 6. Regarding the UL packet filters 62, 64 used in the UE 10, these are signaled from the policy controller 30 via the gateway 26. In some embodiments, at least some of the UL packet filters 62, 64 are pre-configured at the UE 10, or some of the DL packet filters are pre-configured at the gateway 26, or both are pre-configured. . Further, in some embodiments, the UL packet filter is pre-configured at the gateway 26 and signaled to the UE 10 when the UE 10 connects to the gateway 26 or when the corresponding bearers 52, 54 are established. In such embodiments that use preconfigured packet filters at the UE 10 and / or the gateway 26, the policy controller 30 and / or the filter generator 35 of the policy controller 30 may be omitted. In some embodiments, UL packet filters and / or DL packet filters are similarly pre-configured in the policy controller 30, eg, when the UE 10 connects to the gateway 26 or upon establishment of the corresponding bearers 52, 54. Or signaled to the UE 10 or both.

  In the following, a concept according to an embodiment of the present invention will be described that allows efficient processing of data traffic related to one or more specific network resources. In this regard, the term “network resource” is intended to include various structures, content or services that are accessible in the network. In some examples, the network resource is a server that hosts a service or content, eg, according to a uniform resource identifier (URI), or a uniform resource identifier. In some examples, the same server hosts different network resources. In the example of FIG. 1, these concepts apply with respect to providing a specific QoS level. This is accomplished by routing data packets to bearers 52, 54 using packet filters 62, 64, 72, 74 at UE 10 and gateway 26. However, it should be understood that these concepts are further applicable to other types of distinctions, for example with respect to billing, selective blocking of data traffic, also referred to as redirection, or selective redirection of data traffic.

  The differentiated processing is achieved based on packet classification rules that are applied by one or more communication devices, which are UE 10 and gateway 26 in the example of FIG. In the example of FIG. 1, the packet class classification rule is realized by packet filters 62, 64, 72 and 74. The packet filters 62, 64, 72, 74 are generally configured to operate based on the network address included in each protocol header of the data packet. The network address is in particular an IP address. For example, when using Transmission Control Protocol (TCP) or User Datagram Protocol (UDP) to implement the transmission of data via data packets, the protocol header is a filter defined in packet filters 62, 64, 72, 74. It includes IP addresses that define the source and destination network addresses of data packets that are used separately or in combination as criteria for matching the pattern. Furthermore, the above example of protocol headers indicate source port numbers and destination port numbers used separately or in combination as criteria for matching the filter pattern defined in packet filters 62, 64, 72, 74. Define further. In some embodiments, the packet filters 62, 64, 72, 74 are IP5 tuples (source IP address, destination IP address, source port number, destination port number, protocol above IP protocol ID of the data packet. ) Based on the pattern that matches. Further, the packet filter may operate in a filter pattern where the IP address is combined with a prefix mask and / or the port number is specified as a port range. The filter pattern may be extended by service type (TOS) (IPv4) / traffic type (IPv6) and mask. The filter pattern is further determined from the destination IP address, protocol above IP protocol ID, service type (TOS) (IP version 4) / traffic type (IP version 6) and mask, and IPSec security parameter index (SPI). It is configurable. The filter pattern can be further configured from a destination IP address, a service type (TOS) (IPv4) / traffic type (IPv6) and mask, and a flow label (IPv6). In some embodiments, the values not specified in the filter pattern of packet filters 62, 64, 72, 74 match some value of the corresponding information in the data packet, ie, a wild card is defined.

  To reduce the complexity of the packet class classification rules, eg, packet filters 62, 64, 72, 74 required to achieve the desired differentiated processing, the embodiments of the present invention described below are described. Such a concept is based on adaptation of a search procedure to obtain the network address of a specific network resource for which a differentiated process is realized. This adaptation is achieved by processing one or more messages of the search procedure. This process includes receiving a query for the network address of the network resource and responding to the query using the network address of the alternative network resource. In addition, the process may include receiving a response to the query for the network address of the network resource and changing the response by replacing the network address of the network resource with the network address of the alternative network resource. Further, the process may further include redirecting a query for the network address of the network resource. In the example shown, the search procedure is based on the Domain Name System (DNS) and the adaptation is achieved by processing one or more DNS messages that are, for example, a DNS query or a response to a DNS query. In other examples, other search procedures, such as a NetBIOS search procedure, can be used as well.

  More particularly, the concept shown applies to an example where a search procedure is performed to obtain the network address of a network resource prior to data traffic associated with the particular network resource. The search procedure is adapted by processing one or more messages of the search procedure to return a network address of an alternative network resource that can be substituted for the network resource in the communication of data packets. For example, the alternative network resource is configured to have the function by operating as a proxy node for the network resource. The alternative network resource may further cache content provided by the network resource. In some embodiments, the alternative network resource may be a cache server or a tunnel edge server for distributing the contents of the network resource.

  In that case, communication of the data packet is established for the alternative network resource, and the differentiated processing of the data packet is performed based on the network address of the alternative network resource. Thus, the differentiated processing of data packets is facilitated by appropriate selection of network addresses for alternative network resources. For this purpose, the alternative network resource is located in the same local network as the communication device, for example the UE 10, with which communication is established. Thus, the network operator of the local network appropriately assigns network addresses to alternative network resources. For example, the network address is selected from a range of private network addresses defined, for example, in RFC 1918, RFC 4193, or RFC 5735. However, the network address may be further selected, for example, from a specific range of public network addresses assigned to the network operator.

  For example, the network address of the alternative network resource is selected from a range of network addresses corresponding to the subnet. In this case, the packet class classification rule that operates based on the network address has a simple structure. For example, the filter pattern used by one or more of the packet filters 62, 64, 72, 74 may be defined as a network address that is matched by using wildcards, thereby defining all network addresses in the subnet. To match the filter pattern. As will be appreciated, therefore, packet class classification rules can be efficiently defined that provide the same processing for all network addresses from that subnet. This can be used to provide specific processing for these network resources by assigning network addresses from the same subnet to alternative network resources for many specific network resources. According to a further example, the differentiation of data traffic of different network resources can be similarly realized by respectively selecting the network address of the corresponding alternative network resource from the range of different networks corresponding to the subnet. Corresponding packet classification rules may be defined for each subnet, so that the corresponding processing of the associated data traffic can be defined individually. Thus, in some embodiments, the network address of the alternative network address is selected according to the traffic type of the data traffic associated with the network resource. In particular, each traffic type may be assigned to a range of corresponding network addresses, eg, a subnet, and the network address of the alternative network resource is the network address corresponding to the traffic type of the data traffic associated with the network resource. It may be selected from a range.

  To implement the above concept, the communication system of FIG. 1 further includes a search adaptation device (LAD) 100. Typically, the search adaptation device 100 receives a search message related to data traffic associated with a particular network resource. In some embodiments, the search adaptation device 100 is arranged such that search messages related to the data traffic of the UE 10 are routed through the search adaptation device 100. For example, this is accomplished by placing the search adaptation device 100 in the data path between the gateway 26 and a local DNS server (not shown in FIG. 1). In some embodiments, search adaptation device 100 is part of gateway 26. In some embodiments, the search adaptation device 100 is part of a local DNS server. According to a further embodiment, the search adaptation device is placed in the data path between the local DNS server and the external DNS server. Further, in some embodiments, the search adaptation device 100 is part of an external DNS server. The search adaptation device 100 may be implemented in another network device such as the gateway 26 or a local DNS server, or may be implemented as a stand-alone network device. The functionality of the search adaptation device 100 is implemented in software by having a processor (not shown in FIG. 1) of the search adaptation device 100 execute appropriately configured program code and using appropriately configured search adaptation data. It may be realized. As an alternative, the search adaptation device 100 may be implemented at least in part by dedicated hardware.

  In some embodiments, the network address of the alternative network resource is selected to match a pre-configured packet class classification rule that operates based on the network address. In this way, a separate procedure for generating packet signaling rules and / or signaling is not required. For example, in the mobile communication network environment of FIG. 1, packet filters 62, 64 may be pre-configured at UE 10, or packet filters 72, 74 may be pre-configured at gateway 26, or both. . Further, the packet filters 62 and 64 may be signaled to the UE 10 after being preset in the gateway 26. Furthermore, the packet filters 62, 64, 72, 74 may be pre-configured in the policy controller 30 and signaled to the gateway 26 or the UE 10 or both. The pre-configuration provides a maintenance procedure to provide these packet class classification rules together with, for example, the communication device operating software that performs differentiated processing based on the packet class classification rules, or to provide the communication device with the packet class classification rules. Can be obtained by using In some embodiments, such pre-configured packet classification rules are updated in response to inspection of data packets, such as different data traffic associated with the same network resource, or the same alternative network, for example. It can improve the differentiation of data traffic related to different network resources that use the resource.

  In some embodiments, a packet class classification rule that operates based on the network address of the alternative network resource may be dynamically generated in response to the selection of the network address of the alternative network resource, or an existing packet class Classification rules may be changed in response to selection of network addresses for alternative network resources. In the example of FIG. 1, the search adaptation device uses the signaling path 9 to the policy controller 30 to initiate the generation of a new packet filter used by the UE 10 and / or the gateway 26, or the existing The change of the packet filters 62, 64, 72, 74 is started. In each example, this is accomplished by the filter generator 35 of the policy controller 30.

  As further shown, the communication system of FIG. 1 further includes a packet tester 40. In some embodiments, the packet inspector 40 determines the type of traffic in the data traffic associated with the same network resource, for example, different applications of the same Internet service or different types of content from the same content provider. Used to further distinguish. Alternatively or additionally, the packet inspector 40 is further used to distinguish data traffic associated with different network resources that use the same alternative network resource.

  The packet inspector 40 is operable to determine the type of data packet traffic in the UL traffic or DL traffic. For this purpose, the packet inspector 40 analyzes the data packet of UL traffic or DL traffic for information after the protocol header of the data packet, for example. For example, the packet inspector 40 analyzes the data packet with respect to the host name, uniform resource identifier (URI), uniform resource locator (URL) or network address included in the payload portion of the data packet. For example, such information is found in the HTTP request, eg, in the request header of the HTTP request. The information obtained by the packet inspector 40 can be used to update a packet classification rule that is one or more of the packet filters 62, 64, 72, 74, for example. In the example of FIG. 1, the update is initiated by the packet inspector 40 using the signaling path 5 to the policy controller 30. The filter generator 35 of the policy controller 30 generates updated filters that are used in the gateway 26 and / or the UE 10.

  FIG. 2 is a signaling diagram illustrating an exemplary example in which differentiated processing of data traffic is provided by adapting a search procedure according to the concepts described above. The signaling diagram of FIG. 2 shows UE 10, local DNS server 50, alternative server 60 and server 80. The above functionality of the search adaptation device is realized in the local DNS server 50. That is, the search adaptation device 100 in FIG. 1 may be a part of the local DNS server 50.

  In the example of FIG. 2, the server 80 represents an example of a specific network resource on which processing differentiated by data traffic related in communication to the UE 10 is executed. For example, the server 80 may provide one or more specific Internet services, or may be part of a content distribution system that is used for efficient distribution of content. As described in connection with FIG. 1, this distinct processing has the purpose of providing a specific QoS level for the data traffic, which is one of the bearers 52, 54, in particular the dedicated bearer 54. Is obtained by routing the data packet of the data traffic to the corresponding bearer. The alternative server 60 functions as an alternative network resource for the server 80. The alternative server 60 can be an alternative to the server 80 in communication with the UE 10. In particular, the alternative server 60 can respond to requests from the UE 10 in the same way as the server 80. For this purpose, the alternative server 60 may operate a proxy node for the server 80, for example by relaying the request to the server 80 and forwarding the response from the server 80 to the UE 10, or provided by the server 80. Content may be cached, or both. In some examples, an accelerated tunnel is provided for communication between alternate server 60 and server 80. In such an example, the alternate server functions as a tunnel edge server, eg, encapsulating data packets sent to server 80 via an accelerated tunnel and decapsulating data packets received from server 80 via an accelerated tunnel. I do. In some embodiments, the proxy server operation of the alternate server 60, the cache server operation and the tunnel edge server operation are combined.

  Furthermore, the UE 10 is connected to the mobile communication network using radio access technology, for example as shown in FIG. 1, and the local DNS server 50 and the alternative server 60 are part of this mobile communication network, ie by the same network operator. Assume that it is controlled. The network operator has assigned a specific range of network addresses, for example a range of private network addresses used by the alternative network resource, and the alternative server 60 has a network address selected from this range.

  In step 201, a bearer, for example a dedicated bearer 54, used by data traffic associated with the server 80 is established. Bearers are established to allow data traffic to be handled as premium traffic or trash traffic, for example, by providing a specific QoS level. The bearer may be already established when the UE 10 is connected to the mobile communication network. Alternatively, the bearer may be established in response to first detecting data traffic associated with the server 80 using, for example, the packet inspector 40. The packet filter used to route data traffic to the bearer is configured to operate based on the network address assigned to the alternate server 60. In particular, the UL packet filter used in the UE 10 is configured to route a UL data packet directed to the network address of the alternative server to the bearer and is used in a gateway to which the UE 10 is connected, for example, the gateway 26 of FIG. The DL packet filter configured is configured to route DL data packets input from the network address of the alternative server to the bearer. Packet filters are preconfigured at the UE 10 or gateway, and the network address of the alternative server 60 is selected to match these preconfigured packet filters. Alternatively, the packet filter is generated in response to selection of an alternative server network address. In each example, the signaling required to establish a bearer is limited. In addition, the network addresses of other alternative servers corresponding to other servers are assigned to obtain a simple filter structure.

  As shown at 202, the server 80 transmits data to the alternative server 60. Depending on the operation of the alternative server 60, this is accomplished at some appropriate time. For example, transmission is triggered by a request for new data or data by another client that is made available at server 80. Such a request is initially received by the alternate server 60 and if the data is not available locally, the alternate server 60 forwards the request to the server 80. The alternate server 60 stores the received data for use to respond to subsequent requests. For example, in the operation of the proxy node as a tunnel edge server, the transmission of data from the server 80 to the alternative server 60 is triggered by a request from the UE 10 that is relayed to the server 80 by the alternative server 60.

  When the UE 10 needs to access the server 80, the UE 10 first issues a DNS query 203 to the local DNS server 50. The DNS query 203 specifies a host name or URI associated with the server 80 in order to request the network address of the server 80. Thereafter, the local DNS server 50 including the search adaptation functionality performs an adaptation step 204 before responding to the DNS query with message 205. Through adaptation step 204, DNS query 203 is processed so that message 205 indicates the network address of alternative server 60. Thus, according to the adaptation step 204, the search procedure returns the network address of the alternative server 60. The adaptation step 204 is realized by a corresponding configuration of resource records for the host name or URI associated with the server 80 stored by the local DNS server 50. The configuration of the resource record may be based on appropriately configured search adaptation data that associates the host name associated with the server 80 and / or the URI with the network address of the alternative server 60.

  Thereafter, the UE 10 sends a request 206 to the alternative server to request data, and the alternative server 60 sends a response 207 with the requested data to the UE 10. The data packet of request 206 is directed to the bearer established in step 201 by the UL packet filter of UE 10 to indicate the network address of alternative server 60 as the destination address. Similarly, the data packet of the response 207 indicates the network address of the alternative server 60 as a destination address, and is established in step 201 by the DL packet filter of the gateway to which the UE 10 is connected and is directed to the bearer.

  As long as the network address of the alternative server 60 is cached by the UE 10 for subsequent data traffic associated with the server 80, a new DNS query by the UE 10 is not required. Such traffic is routed directly to the alternative server 60.

  It should be understood that the search procedure of FIG. 2 can be modified in various ways. For example, the DNS query 203 is redirected by the local DNS server 50 to, for example, an external DNS server that is a DNS server having authority over the domain of the server 80. This redirection is done in one or more steps. In that case, the adaptation of step 204 is also achieved by an external DNS server. However, this external DNS server may be hosted by a network operator of the mobile communication network. In such a case, the search procedure can further include a further step of optimizing the distribution of content, for example selecting a cache cluster or cache server.

  In some examples, the search procedure of FIG. 2 is iterative. In such an example, the local DNS server 50 responds to the UE 10 with a message indicating an additional DNS server that needs to send a DNS query in the next step. Thereafter, the UE 10 sends a DNS query to a further DNS server, and obtains information on the requested network address or another DNS server that sends the DNS query in the next step. This is repeated until the DNS query arrives at the DNS server that responds to the DNS query using the alternative server 60 network address. The DNS server that sends the final response to the query may be, for example, an external DNS server that is a DNS server having authority over the domain of the server 80. However, this external DNS server may be hosted by a network operator of the mobile communication network.

  In addition, the message 205 returned to the UE 10 may further indicate not only the network address of the alternative server 60 but also an additional network address associated with the alternative server or a further alternative server. For these further alternative servers, the corresponding network address is assigned to match the bearer packet filter established in step 201. Further, the DNS query 203 and the message 205 returned to the UE in response to the DNS query 203 are generated by generating a bearer packet filter that matches all data packets indicating the port number 53 as a source or destination port. , Routed to the bearer established in step 201.

  FIG. 3 is a signaling diagram illustrating a further illustrative example in which differentiated processing of data traffic is provided by adapting a search procedure according to the concepts described above. In this example, adaptation is based on the interception of messages sent in response to DNS queries. The signaling diagram of FIG. 3 shows the UE 10, the search adaptation device 100, the local DNS server 50, the alternative server 60, the external DNS server and the server 80. The search adaptation device 100 is shown as being located between the UE 10 and the local DNS server 50. For example, the search adaptation apparatus 100 is realized in a gateway, for example, the gateway 26 of FIG.

  In the example of FIG. 3, the server 80 represents an example of a specific network resource on which processing differentiated by data traffic related in communication to the UE 10 is executed. For example, the server 80 may provide one or more specific Internet services, or may be part of a content distribution system that is used for efficient distribution of content. As described in connection with FIG. 1, this distinct processing has the purpose of providing a specific QoS level for the data traffic, which is one of the bearers 52, 54, in particular the dedicated bearer 54. Is obtained by routing the data packet of the data traffic to the corresponding bearer. The alternative server 60 functions as an alternative network resource for the server 80. The alternative server 60 can be an alternative to the server 80 in communication with the UE 10. In particular, the alternative server 60 can respond to requests from the UE 10 in the same way as the server 80. For this purpose, the alternative server 60 may act as a proxy node for the server 80, for example by relaying the request to the server 80 and forwarding the response from the server 80 to the UE 10, or provided by the server 80. Content may be cached, or both. In some examples, an accelerated tunnel is provided for communication between alternate server 60 and server 80. In such an example, the alternate server functions as a tunnel edge server, eg, encapsulating data packets sent to server 80 via an accelerated tunnel and decapsulating data packets received from server 80 via an accelerated tunnel. To achieve. In some embodiments, the proxy server operation of the alternate server 60, the cache server operation and the tunnel edge server operation are combined.

  Furthermore, the UE 10 is connected to the mobile communication network using radio access technology, for example as shown in FIG. 1, and the local DNS server 50 and the alternative server 60 are part of this mobile communication network, ie by the same network operator. Assume that it is controlled. The network operator has assigned a specific range of network addresses, for example a range of private network addresses used by the alternative network resource, and the alternative server 60 has a network address selected from this range. The external DNS server 70 is a DNS server having authority over the domain of the server 80, for example.

  In step 301, a bearer, for example a dedicated bearer 54, used by data traffic associated with the server 80 is established. Bearers are established to allow data traffic to be treated as, for example, premium (premium) traffic or trash traffic by providing a specific QoS level. The bearer may already be established when the UE 10 is connected to the mobile communication network. Alternatively, the bearer may be established in response to first detecting data traffic associated with the server 80, for example using the packet inspector 40. The packet filter used to route data traffic to the bearer is configured to operate based on the network address assigned to the alternate server 60. In particular, the UL packet filter used in the UE 10 is configured to route a UL data packet directed to the network address of the alternative server to the bearer and is used in a gateway to which the UE 10 is connected, for example, the gateway 26 of FIG. The DL packet filter configured is configured to route DL data packets input from the network address of the alternative server to the bearer. Packet filters may be preconfigured at the UE 10 or gateway, and the network address of the alternative server 60 is selected to match these preconfigured packet filters. Alternatively, the packet filter is generated in response to selection of an alternative server network address. In each example, the signaling required to establish a bearer is limited. In addition, other network addresses of other alternative servers corresponding to other servers are assigned to obtain a simple filter structure.

  As shown at 302, the server 80 transmits data to the alternative server 60. Depending on the operation of the alternative server 60, this is accomplished at some appropriate time. For example, transmission is triggered by a request for new data or data by another client that is made available at server 80. Such a request is initially received by the alternate server 60 and if the data is not available locally, the alternate server 60 forwards the request to the server 80. The alternate server 60 stores the received data for use to respond to subsequent requests. For example, in the operation of the proxy node as a tunnel edge server, the transmission of data from the server 80 to the alternative server 60 is triggered by a request from the UE 10 that is relayed to the server 80 by the alternative server 60.

  When the UE 10 needs to access the server 80, the UE 10 first issues a DNS query 303 to the local DNS server 50. DNS query 303 specifies a host name or URI associated with server 80 to request the network address of server 80. In this example, since the local DNS server 50 cannot respond to the DNS query 303, it is assumed that a further DNS query 304 is issued to the external DNS server 70. The external DNS server 70 responds to the local DNS server 50 using a message 305 indicating the network address of the server 80. Thereafter, the local DNS server 50 issues a message 306 indicating the network address of the server 80 to the UE 10. The message 306 is intercepted by the search adaptation device 100 and changed by replacing the network address of the server 80 with the network address of the alternative server 60 in an adaptation step 307. The search adaptation apparatus 100 transfers the changed message 308 to the UE 10. Due to the adaptation step 307, the search procedure returns the network address of the alternative server 60. The adaptation step 307 is realized by providing the search adaptation device 100 with appropriately configured search adaptation data that associates the network address, host name and / or URI associated with the server 80 with the network resources of the alternative server 60. The

  Thereafter, the UE 10 sends a request 309 to the alternative server 60 to request data, and the alternative server 60 sends a response 310 with the requested data to the UE 10. The data packet of the request 309 is directed to the bearer established in step 301 by the UL packet filter of the UE 10 to indicate the network address of the alternative server as the destination address. Similarly, the data packet of the response 310 is established in step 301 by the DL packet filter of the gateway to which the UE 10 is connected and directed to the bearer to indicate the network address of the alternative server as the destination address.

  As long as the network address of the alternative server 60 is cached by the UE 10 for subsequent data traffic associated with the server 80, a new DNS query by the UE 10 is not required. Such traffic is routed directly to the alternative server 60.

  It should be understood that the search procedure of FIG. 3 can be modified in various ways. For example, redirecting a DNS query to an external DNS server can include one or more additional redirect processes. Furthermore, the search procedure may further comprise a further step of optimizing the distribution of content, for example selecting a cache cluster or a cache server. In addition, the search adaptation device 100 can intercept responses to the DNS query at different positions. For example, the search adaptation device 100 may be arranged between the local DNS server 50 and the external DNS server 70 to intercept the message 305.

  In some examples, the search procedure of FIG. 3 is iterative. In such an example, the local DNS server 50 responds to the UE 10 with a message indicating an additional DNS server that needs to send a DNS query in the next step. Thereafter, the UE 10 sends a DNS query to a further DNS server, and obtains information on the requested network address or another DNS server that sends the DNS query in the next step. This is repeated until the DNS query arrives at the DNS server that responds to the DNS query using the server 80 network address. This final response is then intercepted by the search adaptation device 100 and modified as described for the adaptation step 307.

  Also, the message 308 returned to the UE 10 may further indicate not only the network address of the alternative server 60 but also an additional network address associated with the alternative server or a further alternative server. These additional alternative servers are assigned network addresses that match the bearer packet filter established in step 301. In addition, the DNS query 303 and the message 308 returned to the UE in response to the DNS query 303 generate a bearer packet filter that matches all data packets indicating the port number 53 as the source or destination port. , Routed to the bearer established in step 301.

  In the example of FIGS. 2 and 3, the step of establishing a bearer may depend on further conditions. For example, a bearer may be established only for a specific type of UE, for example based on the UE 10's IMEI (International Mobile Identification Number). Furthermore, bearers may be established only for specific subscribers, for example based on information in the subscriber database 32 of FIG. Furthermore, bearers may be established only in certain parts of the network, for example based on the location of the UE 10. Furthermore, bearers may be established only for specific radio access technologies used by the UE 10 to connect to the mobile communication network, for example based on the type of RAN 22 of FIG. If the bearer is not established, the data traffic may be processed in a general manner, for example routed to the default bearer 52.

  In the above concept, the distinguished processing can be realized in various ways. For example, data traffic associated with a plurality of different network resources provides an alternative network resource corresponding to each network resource, and the packet classification rules operating at the network address of the alternative network resource have a simple structure, for example, the same By selecting a network address of an alternative network resource by selecting a network address from a plurality of subnets or a continuous range of network addresses, it is processed in the same manner.

  Also, the data traffic associated with the first network resource set provides alternative network resources corresponding to each network resource, and the packet class classification rules operating at the network address of the alternative network resource have a simple structure. For example, the alternative network resource by selecting the network address of the alternative network resource corresponding to the first set from a different subnet or a different continuous range of network addresses than the network address of the alternative network resource corresponding to the second network resource set Can be handled differently than the data traffic associated with the second set of network resources. In that case, different packet class classification rules are usually defined for the first set and the second set. For example, a different set of packet filters may be defined to route data traffic associated with the first set to another bearer, eg, a dedicated bearer separate from the data traffic associated with the second set. For example, these two bearers are dedicated bearers with different QoS levels. However, this further includes the possibility that no clear packet classification rules are provided for one set of network resources and corresponding alternative network resources. In the example of FIG. 1, then the data traffic associated with this set is routed to the default bearer.

  In some embodiments, the same alternative network resource is used to provide two or more different data traffic handling methods. This is achieved, for example, by assigning two or more network addresses, each selected from a range associated with different data traffic handling methods, for example in different subnets, to the same alternative network resource. In some embodiments, two or more network addresses of the same alternative network resource are further used to distinguish data traffic each associated with a different network resource associated with the same alternative network resource.

  Furthermore, it should be understood that the above concept may be further applied to differentiated processing for other features other than QoS. In some embodiments, packet classification rules or packet filters are used to differentiate data packets for different charging methods. For example, a specific charging method such as no charge for traffic is applied to a specific content provider or Internet service. This means that traffic associated with these content providers or Internet services need not be considered in the subscriber's prepaid or postpaid account for billing purposes. According to another example, a corresponding charging rate is defined for each network resource.

  FIG. 4 further schematically shows an example of the structure of a network device for realizing the search adaptation device 100.

  In the illustrated implementation, the search adaptation device 100 includes a first interface 130 configured to receive a DNS query or a search procedure message that is a response to a DNS query, for example. Further, the search adaptation device 100 further includes a second interface 135 configured to send a search procedure message, for example, sending or forwarding a DNS query or sending a response to a DNS query. In some embodiments, the first interface 130 and the second interface 135 can be further implemented with a single bidirectional interface.

  In addition, the search adaptation device 100 initiates the creation or update of packet filters, for example by signaling to the policy controller 30 and / or the gateway 26, or for example changes or establishments or both of the bearers 52, 54. It further comprises a control interface 140 that can be used to initiate control processing for the data packet transfer procedure, or to provide instructions to other entities for both. In the 3GPP example shown, the control interface 140 is implemented as an Rx interface according to 3GPP TS. Further, the interface 140 may be further used to obtain search adaptation data and / or other data from which the search adaptation data is derived. In some embodiments, the control interface 140 is implemented with a single interface along with the first interface 130 and the second interface 135.

  Further, search adaptation apparatus 100 includes a processor 150 coupled to interfaces 130, 135, 140 and a memory 160 coupled to processor 150. The memory 160 is, for example, a read-only memory (ROM) that is a flash ROM, a random access memory (RAM) that is a dynamic RAM (DRAM) or a static RAM (SRAM), or a mass storage device that is a hard disk or a solid disk, for example. including. The memory 160 includes suitably configured program code that is executed by the processor 150 to implement the functionality of the search adaptation device 100 described above. More specifically, the memory 160 includes a search adaptation module 170 for implementing the above-described mechanism for adapting the search procedure, and search adaptation data 180 used in the process of adapting the search procedure.

  It should be understood that the structure shown in FIG. 4 is only schematic, and in fact, the search adaptation device 100 may include additional components that are not shown, eg, additional interfaces, for clarity. It should also be understood that the memory 150 may include additional types of program code modules not shown. According to some embodiments, there is further provided a computer program that is a computer readable medium storing program code and / or search adaptation data, eg, stored in memory 160, to implement the concepts according to embodiments of the present invention. Is done.

  FIG. 5 is a flowchart schematically illustrating a method 500 of differentiated processing of data traffic according to an embodiment of the present invention. The method is used to implement the above concept, for example by using the search adaptation device 100 in the mobile communication network of FIG. In some embodiments, method 500 uses a network system that includes a search adaptation device, at least one communication device, eg, UE 10 and / or gateway 26, and an alternative network resource, eg, alternative server 60. To further implement the above concept. In some embodiments, the network system includes a further component, for example a packet tester 40. As described above, the method 500 assumes that a search procedure is performed in which data traffic is associated with a network resource, eg, an Internet service or content provider, and the network address of the network resource is obtained prior to the data traffic. based on.

  In step 510, a search procedure message is received using, for example, the interface 130 of the search adaptation device 100 shown in FIG. The message is, for example, a DNS query or a DNS message that is a response to the DNS query.

  In step 520, the message is processed to adapt the search procedure. Depending on the adaptation, the search procedure returns the network address of the alternative network resource which is an alternative server 60, for example a cache server or a tunnel edge server. The alternative network resource can be an alternative to the network resource in communication of data packets of data traffic. For this purpose, the alternative network resource caches the content provided by the network resource and / or acts as a proxy node for the network resource.

  In step 530, differentiated processing of the data packet is achieved based on the network address of the alternative network resource. For this purpose, a packet class classification rule is defined that operates based on the network address of the alternative network resource. For example, in a mobile communication network environment as shown in FIG. 1, these packet classification rules are realized by a packet filter in which a filter pattern that matches the network address of the alternative network resource is defined. In that case, the packet filter is used to route the data packet to the bearer that provides the desired QoS level. For example, by properly selecting the network address of the alternative network resource from the range of private IP addresses, a simple structure of packet class classification rules is achieved. For example, the total range from which network addresses of alternative networks are selected is organized into sub-ranges corresponding to different traffic types. In that case, the subranges correspond to different subnets. Such organization solves different examples of differentiated processing. For example, in the case of different network resources where the associated data traffic is processed in the same way, the network address of the corresponding alternative network resource is selected from the same subrange. In contrast, for different network resources where the associated data traffic is handled differently, the network address of the corresponding alternative network resource is selected from different subranges.

  As will be appreciated, by using the concepts described above, differentiated processing of data traffic associated with one or more specific network resources can be achieved in a very efficient manner.

  It should be understood that the examples and embodiments described above are illustrative only and various modifications can be made. For example, the concept can be used in other types of communication networks that benefit from the differentiated processing of data traffic associated with a particular network resource, eg, a general IP-based network. In such other types of communication networks, other mechanisms besides bearer allocation may be used to adapt the QoS level. For example, in an IP using network, the Differentiated Services Code Point field of a data packet may be set to adapt the QoS level. The concept may also be applied to any number of different traffic types. Furthermore, differentiated processing may be further achieved for charging, gating or redirecting data packets. Furthermore, it should be understood that the above concepts may be implemented using correspondingly designed software within existing network devices or using dedicated network device hardware. .

Claims (18)

A method of differentiated processing of data traffic associated with the network resource, wherein a search procedure to obtain a network address of the network resource (80) is preceded, comprising:
Processing the search procedure message to adapt the search procedure to return a network address of an alternative network resource (60) that may be substituted for the network resource (80) in the communication of data packets. And
A network address of the alternative network resource is selected according to a traffic class of data traffic related to the network resource;
The differentiated processing of the data packet in the communication with the alternative network resource (60) is performed using a packet class classification rule that operates based on the network address of the alternative network resource (60). Feature method. The processing of the message is
Receiving a query (203) for the network address of the network resource (80);
The method of claim 1, comprising responding to the query (203) using the network address of the alternative network resource (60). The processing of the message is
Receiving a response (305) to a query (304) for the network address of the network resource;
The method of claim 1, comprising changing the response (305) by replacing the network address of the network resource (80) with the network address of the alternative network resource (60). .   4. A method according to any one of the preceding claims, wherein the processing of the message comprises redirecting a query (203, 304) for the network address of the network resource. The method according to any one of claims 1 to 4, wherein the packet class classification rules are preset .   The method of claim 5, wherein the network address of the alternative network resource (60) is selected from a range of network addresses that match the packet class classification rules. Inspecting the data packet;
The method according to claim 5 or 6, further comprising updating the packet class classification rule based on the inspection.   The method according to any one of the preceding claims, wherein the differentiated process comprises routing the data packet to a bearer (52, 54) established over a radio interface.   The data packet is routed to the bearer (52, 54) by a packet filter (62, 64, 72, 74) that operates based on the network address of the alternative network resource (60). Item 9. The method according to Item 8.   The bearer (52, 54) is established between the user equipment (10) and the gateway (26) when the user equipment (10) is connected to the gateway (26). The method according to 8 or 9. A plurality of alternative network resources (60) are provided to distinguish data traffic associated with corresponding network resources (80);
11. A method according to any one of the preceding claims, wherein the network address of the alternative network resource (60) is each selected from a range of different network addresses corresponding to a subnet. Wherein the alternative network resource (60) A method according to any one of claims 1 to 11, characterized in that it comprises a cache server or tunnel edge server.
  The method according to any one of claims 1 to 12, wherein the alternative network resource (60) acts as a proxy node for the network resource. An interface for receiving a message of a search procedure for obtaining a network address of the network resource (80);
It returns the network address of the alternate network resource (60) in the communication of data packets can become a substitute for the network resource, and the network address of the alternate network resources according to the traffic class of data traffic for the network resource A processor (150) configured to process the message to adapt the search procedure to select ;
Thereby, the differentiated processing of the data packet in the communication with the alternative network resource (60) is performed using a packet class classification rule that operates based on the network address of the alternative network resource (60). A network device (100) characterized by making it possible .   15. The network device (100) of claim 14, wherein the network device (100) is configured to operate according to the method defined in any one of claims 1 to 13. An alternative network resource (60) that can be an alternative to the network resource ( 80 ) in the communication of data packets;
Configured to process a message of a search procedure for obtaining a network address of the network resource (80), wherein the search procedure returns a network address of the alternative network resource (60) and data relating to the network resource. A network device (100) adapted to select the network address of the alternative network resource according to a traffic class of traffic;
Using the packet class classification rule that operates based on the network address of the alternative network resource (60), the differentiated processing of the data packet in the communication with the alternative network resource (60) (60) at least one network device (10, 26) configured to perform based on the network address.   The network system according to claim 16, wherein the network system is configured to operate according to the method defined in any one of claims 1 to 13.   14. A computer program comprising data processed by a processor of a network device (100) and for operating the network device (100) according to the method defined in any one of claims 1-13.

Images