Working Principle of J2ME Applications with GPS Module


J2ME applications are embedded on mobile devices can utilize existing technology to him. J2ME can use GPRS technology to build an Internet-based applications. Applications on a user (mobile users) can also be enriched with animated graphics, animated interesting by offering ever-increasing user interaction.
Applications built using the J2ME profile MIDP (Mobile Information Device Profile) is known by the name of the MIDlet. MIDP is specifically used on the handset itself with the CPU, memory, keyboard and the screen is limited eg mobile phones, PDAs and so forth. GPS module for tracking devices can be connected with J2ME-based applications, it is necessary configuration. General configuration is as follows.




J2ME-based applications access the GPS receiver built-in. Once the position information is obtained, then the data is transmitted periodically through GPRS connection to the server with the HTTP protocol GPS Tracking.
The working principle own J2ME applications we simplify as follows:
  1. Initialization data.
  2. Read data from GPS and wait until the GPS position data has been obtained.
  3. If the GPS data has been obtained and the data transmission period (eg every 1 minute) has been reached then open the GPRS connection and send data over HTTP to format the URL as above.
  4. Repeat step 2, and so on, this process is performed once every 1 second.
  5. Implementation of the above will be looping with timer facilities that already exist in J2ME.


Keywords you can use to search for this article

Know the J2ME Technology as the Application of GPS Support

J2ME is a combination that exists between a set of Java interfaces that are often referred to as the Java API (Application Programming Interface) with JVM (Java Virtual Machine) designed specifically for the instrument, namely the JVM with limited space. The combination is then used to perform manufacturing applications that run on mobile devices.
J2ME itself basically consists of 3 parts, namely the configuration, profiles, and packages are optional packages. Here's an explanation of the three parts of J2ME :


Configuration is the part that contains the JVM and some other class library. There are 2 pieces of configuration that is provided by SUN Microsystems, the CLDC (Connected Limited Device Configuration) and CDC (Connected Device Configuration). The target device from the CLDC configuration is the small tools, such as cellular phones, PDAs, and pagers. While the CDC is a superset of CLDC, so all the classes are defined in CLDC will exist also in the CDC. Configuration has been provided by the company's tools and placed in the relevant instrument that is ready for use.


Profile is part of the configuration expansion. That is, besides a set of classes contained in the configuration, there are also specific classes are defined again in the profile. The profile is very popular is its use of artificial profiles Sun Microsystems, namely MIDP (Mobile Information Device Profile). Profiles are provided by the company's tools and placed in the relevant instrument that is ready for use.

Optional packages are additional packages required by the application so that when the deployment process for those packages need to be distributed also some part of the application concerned. In contrast to the configuration and profile, if the optional packages are not provided by the companies concerned.

Keywords you can use to search for this article