Open5GS Traffic Accounting

Spencer Sevilla sevilla at cs.washington.edu
Wed Mar 11 17:22:09 UTC 2020


Our migration is *almost* done. We had to rewrite a lot of database code because we used to integrate with OAI, but now have moved our systems over to open5gs. I’ll respond back to this thread once we’ve finally migrated everything (should be by the end of the week).

> On Mar 11, 2020, at 10:05, Romeu Medeiros <medeiros at medeiros.eng.br> wrote:
> 
> Hello Spencer, Harald and all.
> 
> 
> I really appreciated all infos, this saves me a lot of time!
> 
> Spencer, I'm seeing your tool, I think that is exactly like I need. My environment is small (10 endbs).  
> 
> I will try to use your tool here, In our github page you inform that the code is migrating to open5gs. It's working with the open5gs?
> 
> Thanks
> 
> Romeu Medeiros
> 
> On Wed, Mar 11, 2020 at 1:39 PM Spencer Sevilla <sevilla at cs.washington.edu <mailto:sevilla at cs.washington.edu>> wrote:
> +1 to Harald. Doing traffic accounting at the PGW and then reporting these statistics over Diameter is probably the most architecturally correct way to do this. I'm definitely a fan of using IPTables for this kind of stuff, since it’s all just packets anyways.
> 
> For our networks, we wrote a completely separate tool called haulage (https://github.com/uw-ictd/haulage <https://github.com/uw-ictd/haulage>) that uses IPTables and does something very similar. Basically logs packets that are forwarded from the virtual interface, draws them down against a user’s prepaid quota, and cuts them off when they hit zero. We wrote this as a separate app (in go) mainly to keep things simpler and let us move faster.
> 
> Spencer
> 
> > On Mar 11, 2020, at 09:26, <david at ispsupplies.com <mailto:david at ispsupplies.com>> <david at ispsupplies.com <mailto:david at ispsupplies.com>> wrote:
> > 
> > Sorry yeah I meant the EPC.  I am not sure if the Open5GS software supports
> > it but Freediameter would be the Accounting portion in AAA from what I can
> > tell.  
> > 
> > 
> > 
> > David Peterson
> > Senior Engineer
> > 855-947-7776 ext. 9214
> > c 419-706-7355
> > d 979-314-1305
> > https://www.ispsupplies.com <https://www.ispsupplies.com/>   
> > 
> > 
> > -----Original Message-----
> > From: Harald Welte <laforge at osmocom.org <mailto:laforge at osmocom.org>> 
> > Sent: Wednesday, March 11, 2020 11:53 AM
> > To: david at ispsupplies.com <mailto:david at ispsupplies.com>
> > Cc: 'Romeu Medeiros' <medeiros at medeiros.eng.br <mailto:medeiros at medeiros.eng.br>>; nextepc at lists.osmocom.org <mailto:nextepc at lists.osmocom.org>
> > Subject: Re: Open5GS Traffic Accounting
> > 
> > Hi David,
> > 
> > On Tue, Mar 10, 2020 at 07:56:06PM -0400, david at ispsupplies.com <mailto:david at ispsupplies.com> wrote:
> >> Freediameter should be able to provide accounting so long as the ENB
> > supports it.
> > 
> > in which way is the eNB involved in traffic accounting in LTE?  
> > 
> > Normally, AFAICT, accounting is implemented within the P-GW, potentially
> > interacting via Radios/Diameter or some other protocol with some external
> > entity that decides whether or not there is credit/budget remaining or not.
> > If not, the PGW would stop firwarding packets of the related
> > session/subscriber.
> > 
> > -- 
> > - Harald Welte <laforge at osmocom.org <mailto:laforge at osmocom.org>>
> > https://linkprotect.cudasvc.com/url?a=http%3a%2f%2flaforge.gnumonks.org%2f&c <https://linkprotect.cudasvc.com/url?a=http%3a%2f%2flaforge.gnumonks.org%2f&c>
> > =E,1,yb6SFWcoxXKtp0qClHpv4V936cQS_cFUx9dFgqORnwJ6yRCOhax7GulxJjjPLVsGkCe2ioB
> > ew6hlBJnFYR1mBgD0-WojRnKxjbM4dQK9xQ,,&typo=1
> > ============================================================================
> > "Privacy in residential applications is a desirable marketing option."
> >                                                  (ETSI EN 300 175-7 Ch. A6)
> > 
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/nextepc/attachments/20200311/0da75bec/attachment-0001.htm>


More information about the nextepc mailing list