Clever Geek Handbook

GPRS Information - Mobile

I have almost the worst spec in the world. An application that exists and is used to work. My goal is to recreate this application and make it work.

This is a very simple way and only displays the following information:

  • ARFCN - Absolute RF channel number
  • LAC - Cell Location Area Code (unique in PLMN)
  • RAC - Cell Routing Area Identifier (unique in PLMN)
  • MNC / MCC - Mobile Network Code / Cellular Country Code
  • NCellInfo1-6 -?
  • Rx quality -
  • Frequency hopping -
  • Last registered network
  • TMSI -?
  • Periodic location update
  • Group
  • Channel used
  • RSSI 1 - indication of the received signal strength
  • The reason for the last call.

I hope I can get some of this information through the OpenNETCF networking information, maybe some P /'s are calling somewhere or (worst case scenario) some custom SDK I need to find for the device (and its niche, so I hope , it is not so).

However, wanting to use Stackoverflow permissions, I wondered if someone could point me in the right direction to have this data removed from the device. Does anyone know of any libraries that specifically provide such information?

0


source to share


2 answers


I can't speak for all this information, but you can get most of it from RIL (Radio Interface Layer).

http://msdn.microsoft.com/en-us/library/aa920475.aspx



I'm not sure if you will be able to use C # to access the RIL layer since you have to provide C function callbacks.

You get the information about the cell from the RIL_GetCellTowerInfo function and the signal quality information from the RIL_GetSignalQuality function. Check out the MSDN documentation for the information you want.

+1


source


The OpenNETCF NetworkInformation namespace won't help - it's a wrapper around NDIS and WZC, which isn't very telephony friendly. In terms of sensing, there is a Telephony API (TAPI) here , although I doubt even TAPI is going to provide all of this information (it has been a while since I fought with TAPI).



I assume you will be able to get some information via TAPI, but I probably got a lot of it via the native API provided by the radio vendor, and without information about that API (from the radio vendor or OEM device), you are probably out of luck ...

+2


source






More articles:


All Articles