(click here for Part I)
In a previous article, I talked about how IMS, 3G and WiMAX fit together at a conceptual level. As promised, in this article, let’s delve a bit into what it means to interwork IMS and WiMAX. I wanted to get this article out by end this year, so that we have some ‘meat’ to this thread before I forget all about this in 2007.
Note: as usual, click on images to make them larger
What needs to be interworked ?
At a macro level, we know that IMS is a session control layer, while the Wimax forum’s NWG efforts stop at IP-Connectivity. So when we think of interworking, we need to focus on
- Policy – how will one enforce that network policies such as QoS, admission control, etc. are enforced uniformly ?
- Security – how does one ensure that a subscriber is authenticated at the WiMAX and at the IMS layer, since they both provide different levels of services ? (for example, a UE may connect to a WiMAX network , but may not be allowed to place a call via IMS due to call barring)
- Charging – how will one ensure that voice/video/data related access in the WiMAX network propagate to the IMS charging and policy specification
- Session continuity – when a WiMAX UE moves between BTSs (micro-mobility) or ASNs (macro-mobility), what changes need to occur at the IMS level to ensure that an existing session is continuous ?
- Service continuity - when a WiMAX UE side handover occurs, what effect does it have on the ‘service’ being executed -a notch up from the ‘session’ in the previous point. For example, assume that the UE is in a video conference and switches to another WiMAX ASN which has lesser bandwidth support than the previously connected ASN, which would result in loss of video and downgrade to a lower codec rate. To ensure service continuity, the centralized Application Server hosting the conference would need to be notified of this change, and this change may need to be propagated to other participants.
But what is the model of interworking ?
Before we figure out an approach, we need to answer some key questions. For example:
- Who owns the WiMAX network and who owns the IMS network ? This is a very important question. If Sprint-Nextel went the WiMAX way and Verizon went the IMS+3G way, there are going to be business rules that govern which edge nodes of each network will get to talk to each other. Infact, ownership is one of the biggest challenges of interworking. I’ve spoken to countless enterprise companies who are considering IMS interworking, but are paranoid about exposing their corporate data to a centralized carrier’s HSS, for instance.
- What is the relationship model ? Master-slave or Peer-Peer ? For example, we can consider a situation, where say, a Cingular own both 3G and WiMAX spectrum and deploys and end-end cross-bred solution. In this situation, since it is all owned by one operator, one could deploy a ‘Policy Control point’ (the guy who says ‘Hey buddy – reduce QoS to 128kbps’) in one and a ‘Policy Enforcement Point’ (they guy who says ‘Okey Dokey ! Let me act on that asap’) in another. Howevever, If you assume as case where two competitive operators just want to offer interworking, but not yeild control, it may be necessary to deploy both the Control and Enforcement nodes independantly in each network, and define a ‘peer’ protocol between the Policy control nodes.
A simple model
As I mentioned earlier, the business and technical permutations to this solution make it an extremely wide area. For simplicity, let us assume the following:
(Don't ask me why I selected 'Mo' - I wanted to be more innovative than saying 'X' and this is the level of my creativity...)
- Operator ‘Mo’ owns both 3G and WiMAX neworks
- Operator ‘Mo’ decides to make IMS the ‘Master’ control layer and decides to deploy WiMAX as yet another access stratum, under control and direction from the IMS layer.
Understanding Policy Interworking and PCC
In previous releases of IMS, the P-CSCF and the GGSN would often play roles of the ‘Policy Definition Function’ (PDF) and the ‘Policy Enforcement Point’ (PEF), where the P-CSCF would set policy and control based on the network and user profile, while the GGSN would allow/disallow media PDP context and flows based on those instructions. The 3GPP group then felt that the Policy functions were too closely tied to the core elements and there was a need to separate the concept of ‘Policy’ away. Also, it was important to isolate charging and tie it to policy in a way that lends itself to a heterogenous network (i.e. make it IP-CAN independent). This is exactly what the SA2 group of 3GPP was tasked with, and is specified in TS 23.203 “Policy and Charging Control architecture”. This was a better evolution of the older PEF and PDF. In this new model, the following important nodes are defined:
- PCRF (Policy and Charging Rules Function) – This is a logical node that creates ‘rules’ for setting both policy and charging. These rules could be set using a combination of parameters (example, User Joe is only allowed voice and video’ and network X can have a max bandwith of 256kbps – so when User Joe connects from network X, both attributes are combined and apply to arrive at ‘User Joe is only allowed voice and video at 256kbps while connected to X’
- PCEF (Policy and Charging Enforcement Function) that acts on the rules from PCRF and enforces the same. The protocol between PCRF and PCEF happens to be Diameter (mapped to Gx interface)
It is not possible to define all the differences and enhancements that PCC brings over older pre-PCC releases in this blog note, but in short, it attempts to specify specific charging rules, charging models, concept of a service data flow ,more fine grained QoS control and explicit interfaces to other key nodes that participate in a service flow, like the Charging system, Application Servers, CSCFs and HSS) while ensuring that ideally the PCC should be able to be generic enough to adapt to any IP-CAN.
This is what the PCC architecture looks like (credit:taken from 3GPP TS 23.203)
Mapping to WiMAX Network Reference Model
Now that we understand how PCC works, let us take a look at the WiMAX NRM (Credit: Wimax forum Stage 2 NRM)
In short, the ASN (or Access Service Network) provides the access l
ayer connectivity and QoS to the Mobile Station (or UE). The CSN (Connectivity Service Network) provides connectivity services – usually AAA, IP Address allocation, Security (NAT/Firewalls) etc. are part of the CSN. Not shown in this diagram, is that WiMAX already specified a QoS Framework Service management and enforcement points in the ASN for access QoS and management. They are called the SFM (Service Flow Manager) and SFA (Service Flow Auth.). So it would make sense to use them as an interace with IMS’ PCC.
Remember that we assumed, for simplicity, that there is only one owner and there are no federation & sharing issues. Taking this forward then:
- We assume that the WiMAX ‘CSN’ is replaced with ‘IMS for session control, DHCP+Home Agent for IP-CAN allocation)
- The PCRF can then reside in the CSN of WiMAX. And since IMS is part of CSN, the PCRF can effectively talk to the HSS, CSCFs and App. Servers for interacting will all of them for service flow interactions
- The PCEF will also be part of the CSN, and will communicate to the PCRF via Gx (Diameter)
- The PCEF will then possibly talk to the WiMAX ASN SFA for enforcing rules in the WiMAX ASN
The last point may be confusing. Why can’t PCEF be a part of the ASN ? Well, it sure can, and like I said, there are multiple ways to slice and dice. But in this way, the PCEF can act as a ‘mediator’ between the ASN and the PCRF. The WiMAX ASN SFA does not understand how to interact with PCRFs and it uses a different mechanism for QoS enforcement. Therefore, the CSN hosted PCEF can receive requests from the PCRF, and translate to the SFA expected interface and vice versa. This also results in lesser re-engineering at the ASN. Ofcourse, that means that the interface between the PCEF and SFA is “new”. The IMS-Wimax interworking folks call this Gx’ (i.e. think of it as Gx, but modified to work in WiMAX). So the final diagram comes out to:
There goes. A simplified approach, at a 10,000 feet level. In the next few articles, I will talk about the other aspects of security interworking, session interworking, service interworking