Siemens TC65 manual Java File Format

Page 42

TC65 JAVA User's Guide

s

Strictly confidential / Released

 

The values of APPDIR, BEARER and START are used internally and must be lower case. The password (PWD) is case sensitive. The case sensitivity of the other parameter values depends on the server application or the network. It is likely that not all parameters can be sent in one SM. They can be distributed over several SMs. Every SM needs to contain the identifying first line (OTAP_IMPNG) and the PWD parameter if a mandatory password has been enabled. OTAP is started when the keyword START, possibly with a parameter, is contained in the SM and the parameter set is valid for the requested operation. It always ends with a reboot, either when the operation is completed, an error occurred, or the safety timer expired. This also means that all parameters previously set by SM are gone.

Apart from the first and the last line in this example, these are the parameters described in the previous section. Possible parameters for the START keyword are: “install”, “delete” or nothing. In the last case, an install operation is done by default.

The network does not guarantee the order of SMs. So when using multiple SMs to start an OTAP operation their order on the receiving side might be different from the order in which they were sent. This could lead to trouble because the OTAP operation might start before all parameters are received. If you discover such problems, try waiting a few seconds between each SM.

8.5Java File Format

In general, all Java files have to comply with the IMP-NG and TC65 specifications. There are certain components of the JAD file that the developer must pay attention to when using OTAP:

MIDlet-Jar-URL: make sure that this parameter points to a location on the network where your latest JAR files will be located, e.g. http://192.168.1.3/datafiles/mytest.jar, not in the filesystem like file://a:/java/mytest/mytest.jar. Otherwise this JAD file is useless for OTAP.

MIDlet-Install-Notify: this is an optional entry specifying a URL to which the result of an update/install operation is posted. That is the only way to get any feedback about the outcome of an install/update operation. The format of the posted URL complies with the IMP-NG OTA Provisioning specification. In contrast to the jar and jad file this URL must not be protected by basic authentication.

MIDlet-Delete-Notify: this is an optional entry specifying a URL to which the result of a delete operation is posted. That is the only way to get any feedback about the outcome of a delete operation. The format of the posted URL complies with the IMP-NG OTA Provisioning specification. In contrast to the jar and jad file this URL must not be protected by basic authentication.

MIDlet-Name, MIDlet-Version, MIDlet-Vendor: are mandatory entries in the JAD and Manifest file. Both files must contain equal values, otherwise result 905 (see 8.7) is returned.

MIDlet-Jar-Size must contain the correct size of the jar file, otherwise result 904 (see 8.7) is returned.

TC65 JAVA User's Guide_V05

Page 42 of 90

26.09.2005

Image 42
Contents Java Users Guide September 26 Document Name TC65 Java Users GuideTC65 Java Users Guide TC65 Java Users GuideV05Table of Contents Maintenance 3.3.2Compile and Run a Program without a Java IDE Debug EnvironmentJava Security Java Tutorial Differences from the TC45Sun Java Studio Mobility 6 Switching Emulators TablesPreamble New solution OverviewRelated Documents Terms and Abbreviations Abbreviation DescriptionInstallation Installation CDSystem Requirements 1.2 WTK ComponentsModule Exchange Suite SDK and Java StudioSiemens Mobility Toolkit Installation Installing the Standard Development ToolkitInstalling the Smtk Environment Installing Sun Java Studio Mobility Installing Eclipse Installing Borland JBuilder XInstalling Module Exchange Suite MES Smtk Uninstall UpgradesSoftware Platform Software Architecture3 DAC/ADC Interfaces 1 ASC0 Serial DeviceGeneral Purpose I/O 4 ASC1Media JVM InterfacesIP Networking Other InterfacesData Flow of a Java Application Running on the Module ADCHandling Interfaces and Data Service Resources Module StatesState 2 No Java Running, General Purpose I/O and I2C State 1 Default No Java RunningState 4 Default Java Application Active State 3 No Java Running, General Purpose I/O and SPIState 5 Java Application Active, General Purpose I/O and I2C Module State Transitions Maintenance IP ServicePower Saving ChargingShutdown Airplane ModeAlarm Automatic ShutdownSwitching from Data Mode to Command Mode Restart after Switch OffSpecial AT Command Set for Java Applications Mode Indication after MIDlet StartupRestrictions Flash File System Configuration of Serial InterfaceJava Commands MemoryFrequencyB 1 / frequencyA PerformanceJava Duration of each loop = 600 sPin I/O Data Rates on RS-232 APIPlain Serial Interface Voice Call in Parallel75% 63% 55% 33% Scenarios with Gprs ConnectionUpload 65% 55% 33% 16%Download 91% 87% 81% 73%85% 78% 58% 48% MIDlets MIDlet Documentation MIDlet Life CycleMIDlet.destroyApp method Hello World MIDlet Here is a sample HelloWorld programModule Exchange Suite Command Line BasedFile Transfer to Module Windows BasedSecurity Issues Over the Air ProvisioningOtap Over The Air Provisioning Otap Introduction to OtapOtap Overview Parameters Max. Length AT Keyword SM Install/update Delete Otap ParametersInstall operation Short Message FormatDelete operation Java File Format Procedures Install/Update Delete Time Out Values and Result Codes Tips and Tricks for OtapOtap Tracer SecurityHow To Compile and Run a Program without a Java IDE Build ResultsCompile Run on the Module with Manual StartRun on the Module with Autostart Switch on Autostart Switch off AutostartDebug Environment Data Flow of a Java Application in the Debug EnvironmentEmulator Java IDE Sun Java Studio Mobility 6 2004Q3 Switching emulators Projects Templates ExamplesCompile and run JBuilderX JDK settings Borland JBuilderExamples TC65 Java Users Guide JBuilder2005 JDK settings Eclipse IntegrationEclipse Plug-in installation Eclipse J2ME platform TC65 Java Users GuideV05 26.09.2005 Example Eclipse Project importEclipse Example Compile and debug Eclipse Create packageEclipse Configuration BreakpointsJava Security Secure Data Transfer ModeAsja Vasecuritycertificate J a va C u r i t y c e r t i f i c a t eCreate a Secure Data Transfer Environment Step by Step Create CA and generate CA Root CertificateUnsecured mode Secured modeExecution Control Generate key pair Change to Secured Mode ConceptBuild binary data for AT command Atsjsec Generate customer root CertificateConcept for the Signing the Java MIDlet Encoded JAR-File HashStructure and Description of the Java Security Commands Application and Data ProtectionStructure of the Java Security Commands General structureBuild Java Security Command Hash SHA1Send Java Security Command to the Module ATSJSEC?Create Java Security Commands Export X.509 Root CertificateCommand switch off module exchange functionality Sign a MIDletJava Tutorial Using the AT Command APIClass ATCommand Instantiation with or without CSD SupportSending an AT Command to the Device, the send Method Data ConnectionsTC65 Java Users Guide ATCommandResponseListener Interface Non-blocking ATCommand.send MethodSynchronization ATCommandListener Interface ATEventsImplementation Registering a Listener with an ATCommand Instance Programming the MIDlet ThreadsExample TC65 Java Users Guide Differences from the TC45
Related manuals
Manual 123 pages 53.3 Kb

TC65 specifications

The Siemens TC65 is a compact and powerful GSM/GPRS module designed for a wide range of mobile communication applications. With its robust features, the TC65 perfectly meets the growing demands for connectivity in various industries, including automotive, telematics, and industrial automation.

A standout feature of the TC65 is its compact size, allowing it to be easily integrated into various devices without compromising on performance. The module supports GSM (Global System for Mobile Communications) and GPRS (General Packet Radio Service), providing reliable and efficient voice and data transmission.

One of the key technologies incorporated in the TC65 is its integrated TCP/IP stack, which allows for seamless internet connectivity and enables application developers to create IoT solutions with ease. This capability is essential for remote monitoring, data logging, and other applications that require continuous data exchange.

The TC65 also boasts extensive multimedia capabilities, including support for SMS, MMS, and voice calls. This makes it suitable for applications that require not only data transmission but also communication features. Additionally, it supports various codecs for voice compression, ensuring high-quality audio in voice applications.

Enhanced security features are another highlight of the TC65. It incorporates comprehensive security protocols to safeguard data transmission, making it suitable for sensitive applications in finance, healthcare, and other critical sectors. The module also includes an integrated SIM application toolbox that supports the development of secure and customizable applications.

For developers, the TC65 offers an easy-to-use software development kit (SDK), simplifying the process of application development. This means that businesses can quickly create and deploy solutions tailored to their specific needs.

The module operates across a wide voltage range and is designed to tolerate challenging environmental conditions, making it ideal for industrial use. It supports various interfaces, including UART, GPIO, and I2C, enabling it to connect with a variety of peripherals and sensors, thus expanding its usability.

In summary, the Siemens TC65 combines compact design, versatile communication capabilities, advanced security features, and developer-friendly resources, making it an excellent choice for anyone looking to implement reliable and sophisticated GSM/GPRS communication in their applications. The TC65 is a valuable asset in the evolving landscape of connected devices and IoT solutions.