How do Networks track mobile data vs tethered mobile data?

[eske]

Just how do the networks track (and bill) what data is used on a phone when used as a hotspot and what's used by the phone itself? Is it through spyware on branded phones?

I found out the hard way that my network (vodafone Ireland) bills differently for mobile data used by the handset itself (browser, podcast downloades etc) and mobile data when tethered to the handset.

I though data was data

my old network didn't make the distinction - I had 8gb of data to use as I pleased - use the phone as a hotspot or browse from it (what's the difference)

So I'm wondering if this isn't an issue on unbranded phones as there isn't the same bloat/spyware installed on them?

 

[Slug]

By examining the header of every data packet traversing their network, a carrier can pretty accurately determine both the type of data contained within it and its origin. This is routinely done to maintain network QOS and ensure efficient routing of time-sensitive data such as VOIP.

Attitudes to tethering vary by carrier. Some prohibit it outright, others turn a blind eye provided customers remain within their allocated "bundle", and some openly allow it. Published T&C often only tell part of the story.

 

[Perch_44]

I have read that that data packets get an "identifier" added to the header when using the tether feature.

My Droid Inc, I did the hack so that tethered data us supposedly masked as regular phone data. I have never had an issue using it, but I also only use it maybe once a month.

 

[IOWA]

There are a variety of methods, from TTL reading to DPI. If you want the long complicated response I'll be glad to share later.

Bottom line, carriers know everything that travels across their networks.

 

[scythefwd]

I'm betting most phones dont NAT tethered traffic. It could be as simple as the source IP in the packet header being different than the IP the phone has (most tethering programs use private IP space, so it's even easier to tell). If you NAT, most carriers wont actually catch you tethering.

NAT just translates from one IP to another. To keep traffic straight, the connection is tracked by port numbers the request comes in on. Since a request is usually sent out on a random, high numbered port (somewhere over 1024 if I'm remembering correctly) with a specific port as the destination (80 for http, 8080 for http, 443 for ssl, 23, 21, all common ports), the high numbered port that the NAT'ed connection is using to track the connection back to the tethered device is usually ignored.

 

[eske]

Thanks guys,
I guess I'm hosed - I thought it may have been spyware on branded phones (or maybe something to do with APN settings)
There is a provider that allows a high monthly allowance (which I'd be happy to pay for ) but the reception on their network is brutal where I live.
It is annoying as this distinction in billing screams out as a way of protecting the operators business in selling MiFi stlye dongles.

 

[Demache]

Thanks guys,
I guess I'm hosed - I thought it may have been spyware on branded phones (or maybe something to do with APN settings)
There is a provider that allows a high monthly allowance (which I'd be happy to pay for ) but the reception on their network is brutal where I live.
It is annoying as this distinction in billing screams out as a way of protecting the operators business in selling MiFi stlye dongles.

Back when I had my Eris, I noticed in some system settings, there was a seperate APN for tethered data. At least that's what I think it was.

 

[danaj]

I just changed the user agent string on my laptop to match the one on my phone, and now they can't tell if I am tethering...