Method and Apparatus for Policy based Charging during Traffic Steering and Chaining
Publication Date: 2016-Jun-08
The IP.com Prior Art Database
Redknee Inc.: OWNER [+5]
Traffic steering networks distributed across more than one domain may result in some portions of the traffic steering networks employing different network identifiers for a given client device. For example, one of the traffic steering domains may implement a NAT function, and thus downstream traffic steering functions may use a different client network ID than that assigned by the core network. Some of the client device's network identifiers may therefore not be known to the core network components (e.g. the PCRF). This disclosure sets forth a system in which the TSSF is configured to report updated network identifiers to the PCRF.
Page 01 of 12
TITLE: Method and Apparatus for Policy based Charging during Traffic Steering and Chaining
December 14, 2015 Redknee Inc.
INVENTORS: Abhishek Mishra; Pankaj Kumar; Shruti Ashok; Kalyani T. M.; Abhijith J.
Field of technology and background of the invention
Traffic steering and service chaining , is discussed as a potential use case in 3GPP defined mobile networks, where the traffic is routed through a Traffic Steering Support Function (TSSF) network available on the SGi-LAN side. The TSSF network does antimalware, parental control, DDoS protection, video optimization, etc. The TSSF network and the mobile core network can belong to same operator or can each belong to a different operator.
However, in some cases charging may be conducted incorrectly due to the different deployments of the mobile packet core and TSSF networks. This Invention disclosure offers a policy based charging solution, enabling the operator(s) charging processes to remain accurate while providing various service chains for a given IP-CAN session.
As illustrated in Figure 1, a UE is looking for a service provided by an external network. In addition to the external network, two other networks are shown in Figure 1: a Packet Core network, and a Traffic steering network. In the packet core network, the PCRF  is connected to the PGW using the Gx  interface, with TDF using Sd  interface and with OCS using Sy  interface. The OCS is connected to P-GW using Gy  and with TDF using Gyn  interface. The PCRF is connected to TSSF using the St Interface .
There is currently no 3GPP standard listing the Steering Functions (SFs) enabled in a
Page 02 of 12
given administrative domain. Hence, from the deployment point of view, a traffic steering network can be distributed across more than one domain. For example, as illustrated in Figure 1, the traffic steering network is distributed across a network address translation (NAT) domain and a value-added service (VAS) domain. The NAT domain in figure 1 consists of three SFs, namely, an Intrusion Detection System (IDS), an Anti-Malware (AM) function, and a Firewall. Similarly, the VAS domain consists of two SFs, in the form of a parental care function and a Streaming caching function.
Thus, the "Traffic Steering network" of Figure 1 is spread across two domains, the NAT domain and the VAS domain. The NAT domain has a controller TSSF-A and three SFs. The VAS domain has a controller TSSF-B and two SFs.
In this example, the user traffic session consists of Service 1 and Service 2. Service 1 is steered through SF2-A, SF3-A in the NAT domain and SF2-B in the VAS domain. Service 2, meanwhile, is steered through and SF1-A and SF3-A in the NAT domain and SF1-B in the VAS domain, before routing to the external network.
When the traffic for either or both of Service 1 and Service 2 traverses the NAT domain, traffic identifiers such as the IP Address may be altered. This may cause problems on the PCRF and OCS s...