I finally figured out the problem, why didn't the Cellid of the WCDMA base station obtained by Google map mobile edition, MobileTrack, and FieldTest of network optimization be the CellTrack91 or the number in the base station table... This problem is very difficult to say. I have known it before, but I have never studied it in depth, because it does not affect my use. But I was bored lying in bed before I went to bed last night. I opened FieldTest to study the disconnection problem of the base station near the daytime. Then I suddenly found the Cellid rules of the WCDMA base station ............
In the past 2g, when using base station software, the obtained LAC and CELL are both 4-digit 16 numbers. For example, the 2G base station I connected here is: LAC: 1E8CCELL: 335F, their conversion is LAC = 7820, CELL = 13511, many base station software will automatically convert to 10 hexadecimal display for everyone. OK. Use this parameter to search by Google to obtain the returned longitude and latitude. However, in a WCDMA base station, many people obtain the following base station numbers from the base station software, such as CellTrack91 ("base station positioning" or "base station information"): LAC: DC10CELL: 2A2C is converted to LAC = 56336, CELL = 10796. The problem is that the CELL and LAC cannot be used to query any latitude and longitude data from Google. However, FieldTest, Google Map, and MobileTrack can be used to obtain the LAC and CELL of another WCDMA group, they are: LAC = 56336, CELL = 190130732. You can use this set of data to check the longitude and latitude data!
But why ?! Before last night, this problem had plagued me all the time, but because it did not affect me to find the base station I needed, I did not go into this issue, it was not until last night that we put the base64-coded WCDMA base station obtained by CellTrack91 together with the base64-coded base station obtained by FieldTest ...... Eyes !!! It was so simple !! Do you still not understand? Haha ...... Let me reproduce what I saw last night ...... The WCDMA base station obtained by CellTrack91: LAC = DC10CELL = 2A2CFieldTest: LAC = DC10CELL = B552A2C ...... Still don't understand? Let's take a look! Yes! The WCDMA base station obtained by FieldTest is a 7-bit hexadecimal code! Base station software, including Google Maps and MobileTrack, can obtain the complete 7-bit hexadecimal code in the WCDMA network and convert it to a 10-digit code. Our carrier engineering team did not know whether it was a convenient map or another reason when they built the foundation station. They only recorded the last 4 hexadecimal codes! Besides, the well-known Base Station Software CellTrack91 and some other tools may be due to the habit of the 2G era or other reasons, only the 4-digit hexadecimal code is recorded and converted into a 10-digit code! As a result, the CellTrack91 and base station tables can correspond one to one, but the base station tables cannot match Google and Fieldtest! Because the same number is not calculated at all !!~ When I found this problem last night ...... It's really awesome ...... Such a simple question ...... It took so long to figure it out !!...... Through this question, we should understand that Google and MobileTrack support China Unicom's WCDMA base station positioning, but we cannot use the numbers on the base station table to query the geographical location on this site, because the number is wrong. If you want to query the location of the WCDMA base station, you still need to obtain the complete code of the 7-bit hexadecimal base station, and then convert it to the 10-digit base station for query. After all, this problem has plagued me for so long, and I often find interfaces to comfort others. "It doesn't affect your use ~", Now I have found the cause of the problem, which is a knot in my mind.
Some of my friends may have known the reason for this long ago, but I have been ignorant of it. I am so sorry. After all, I have answered my confusion and shared it with other friends I don't know.
From: http://lainzy.oicp.net/post/121.html
