How to Understand External Servers and Services Accessed by Firmware: Difference between revisions

Latest revision as of 08:42, 7 April 2024

Please visit new link of same subject:

https://smartpossdk.gitbook.io/cloudpossdk/faq/firmware/understand-firmware-external-access

We're making a move! Our site's content is migrating to a new URL, to provide you with an enhanced browsing experience. Please update your bookmarks accordingly. Thank you for your continuous support!

@@ Line 1: / Line 1: @@
-Some of the system service in the firmware usually will access some external services:
+{{Migrating|https://smartpossdk.gitbook.io/cloudpossdk/faq/firmware/understand-firmware-external-access}}
-{| class="wikitable"
-|-
-! Service !! Domain Name or IPs || Description
-|-
-| TMS (wizarview) || www.wizarview.com || The major TMS server
-|-
-| 204 Pages || connectivitycheck.gstatic.com <br> www.google.com <br> www.wizarview.cn (old firmware) || Android system will touch an empty 204 HTTP page from those location to check the internet connectivity.<br> For example: [http://connectivitycheck.gstatic.com/generate_204]
-|-
-| A-GPS Location Services || location.services.mozilla.com <br> locprod2-elb-us-west-2.prod.mozaws.net <br> xtrapath2.xboxprod.izatcloud.net || TMS agent will use these service to get the GPS information.
-|-
-| NTP Services || asia.pool.ntp.org || Android system will use these server to automaticly adjustment time, when the system is set as "AutoTime".
-|}