top button
Flag Notify
    Connect to us
      Site Registration

Site Registration

Sy interface related

+2 votes
530 views

I have a question regarding the mapping the Policy counter to Bearers.

Does Policy counter relates to subscriber or it relates to services. I mean how the OCS manages the poilicy counter..
And how it maps to bearers

Lets say we have default bearer which is used for the internet browsing and dedicated bearer for voice.

Now lets say we have Policy counter id1 for subscriber 1, which says the "service as Internet" ..And lets say APN-AMBR (for internet is 5 Mbps upto 5GB ) and 2 Mbps for more than 5GB.

Now in the OCS , we configure for
subscriber1:
Policy counterid1: status 5 Mbps upto 5GB and 2 Mbps for more than 5GB.

And on registration, CCR is sent by PGW to PCRF, which inturn sends the SLR with Policy counter id1 with session Id lets say Sysession1

Now the PCRF sends the CCA to PGW with "service type as Internet", Metering method as "volume" and Rating Group some random value. But there is no way to indicate to PGW about the details of counter like on counting 5Mb, it needs to send the CCR-U to OCS. Or lets say on every 2MB PGW indicates to OCS. The Gy session is created for each bearer ? (i.e one for default bearer here and may be another for dedicated bearer related to that..)

On reaching the 5MB limit, the OCS, sends the SNR to PCRF with the Sysession1.

And when the IP CAN is terminated, CCR-T is sent to OCS and also to PCRF by PGW. PCRF inturn sends the STR to OCS.

Now my Q is about a for 2nd APN for the same subsribers, whatabout the Gy and Sy interfaces, are they reused ?

And whatabout the dedicated bearers related to first APN, will they be using the same Gy and Sy interfaces ?

thanks a lot. Any help or any hints in this very helpful for me to correct my understanding and which will correct my code and finally test it !!!

posted Feb 26, 2016 by Pdk

Share this question
Facebook Share Button Twitter Share Button LinkedIn Share Button

1 Answer

+1 vote

Qouta management is taken care by OCS on Gy interface separately.On Sy interface policy counter status is reported to PCRF at the time of initial attach or if any previous Sy session is there and if any changes happen in the policy counter status for a given policy counter identifier.Now as per your example.when user consumed 5GB den its policy is getting changed to throttled value.It will be indicated by OCS to PCRF on Sy interface in SNR.As far as Gy interface is concerned,In the initial attach,OCS grants some CC-total Octets value and also threshold data.If that threshold data is reached than only PGW will send Update message to OCS. That 5GB may be sent as a threshold value to PGW.

For the 2nd part of your query.I think internet browsing happened on default bearer and dedicated bearer mostly include AUDIO,Video,some high speed messaging and these all things will be taken care by Offline charging System.And it is also operator dependent.Just tell me the what types of traffic is flowing on default and dedicated bearer,than it will be easy for me address Your 2nd part

answer Oct 15, 2016 by Sanjeet Singh
Similar Questions
+1 vote

I am going through the 32.299 and trying to figure out the contents of the CCR message.

Section 6.4.2 lists the AVPS in that message, I am looking for how the PCEF sends the "used bytes" to OCS. The "Multiple services credit control" looks like the one. But need some inputs and help on this AVP. Or please correct me if I am wrong.

+1 vote

Hi all,

We have complexity linked to Gy and Gx interfaces.

Let's say that we have two rules configured as static on PGW with :

Rule1= Reports RatingGroup1
Rule2= Reports RatingGroup2

When PCRF install Rule 1 on Gx, the ratingGroup reported by PGW to OCS is RatingGroup1
When PCRF uninstal Rule1 then install Rule2, the ratingGroup reported by PGW remain RatingGroup1 till a Gy trigger is reached (revalidation time, GSU consumption...).
Then the problem on our system is that when PCRF change the rules on Gx interface the PGW keep reporting the old rating group on Gy interface ie: Gx change do not lead to a Gy change similtanously. I m wondering if there is a standard behaviour for such a use case?

Thanks a lot

+4 votes

I am trying to comeout with the basic AVPs in Gx (to initiate the counting functionality in the PGW.).
- Lets say when the Default bearer is created initially (lets take ims apn as example). In this case, what information is sent to PGW so it starts to count the number of bytes used up for this bearer.
- When the multiple dedicated bearers are created for that particular user, how is this info will differentiate it from the counts the bytes different from the one for each bearers.
- what kind of counters can be implemented in PCRF. Like lets say, the counter which is applicable only for the GBR bearers etc ? (like there is a generic counter for each subscriber or at bearer level for each subscriber)
- Im also looking to comeout with the basic sequence chart ..(or may be wireshark related to mapping Gx, Gy and sy).

+1 vote

Looking at interoperability issues.
The CCRequest message sent from PGW to PCRF during attach. Does the CCA sent back from PCRF to PGW needs to have TFT info?

+4 votes

Hello,

I have been able to write a standalone basic PCRF code in our software.

I had also written them using the Gx and RX interfaces (i.e using the diameter protocol). There was no time to test this feature.

Now I find flaws in my design regarding the Diameter while testing.

Initially the SIP (i.e ike IMS) was sending the request to PGW to create the voice bearer. Now my initial implemetation of Rx i thought the TFT was calculated in the SIP and sent across in the RX, but now when revisiting the code, i feel, that there was no such parameter to pass this info to the PCRF from SIP.

Now my doubt is, how this info related to TFT is being passed across to PCRF. Is it through the "Flows".
If so how to get the TFT in the PCRF to send back to PGW...I have missed this part of the design as i was looking more into the QOS..

Any help is greatly appreciated.

thanks
pdk

...