Siemens TC65 manual Time Out Values and Result Codes, Tips and Tricks for Otap

Page 45

TC65 JAVA User's Guide

s

Strictly confidential / Released

 

8.7Time Out Values and Result Codes

Timeouts:

•Closedown Timeout: 10 seconds

•Safety Timeout: 10 minutes

Result Codes: Supported status codes in body of the http POST request:

•900 Success

•901 Insufficient memory in filesystem

•902 -not supported-

•903 -not supported-

•904 JAR size mismatch, given size in JAD file does not match real size of jar file

•905 Attribute mismatch, one of the mandatory attributes MIDlet-name, MIDlet-version, MIDlet-Vendor in the JAD file does not match those given in the JAR manifest

•906 invalid descriptor, something is wrong with the format of the .jad file

•907 invalid JAR, the JAR file was not available under MIDlet-Jar-URL, files could not be extracted from JAR archive, or something else is wrong with the format of the file.

•908 incompatible configuration or profile

•909 application authentication failure, signature did not match certificate

•910 application authorization failure, tried to replace signed with unsigned version

•911 -not supported-

•912 Delete Notification

All HTTP packets (GET, POST) sent by the module contain the IMEI number in the User- Agent field, e.g.

User-Agent: TC65/000012345678903 Profile/IMP-NG Configuration/CLDC-1.1

This eases device identification at the HTTP server.

8.8Tips and Tricks for OTAP

•For security reasons it is recommended that an SMS password be used. Otherwise the “delete” operation can remove entire directories without any authentication.

•For extra security, set up a private CSD/PPP Server and set its phone number as a fixed parameter. This way, applications can only be downloaded from one specific server.

•As a side effect, OTAP can be used to simply reboot the module. Simply start an OTAP procedure with a parameter set which will not really do anything, such as a delete operation on a nonexistent directory.

•If you do not want to start OTAP by SMS let your Java application do it by issuing the

at^sjotap command. This triggers an install/update operation as described in chapter 8.6.1 but without the SMS part.

Note: If a malfunctioning Java application is loaded the SM method will still be needed for another update.

•The OTAP procedure cannot be tested in the debug environment

•Be aware that the module needs to be logged into the network to do OTAP. That means that either the Java application must enter the PIN, the PIN needs to be disabled or Autopin (see AT Command Set [3]) needs be used.

•The OTAP procedure might fail due to call collision, e.g. an incoming call when OTAP tries to start a CSD connection.

TC65 JAVA User's Guide_V05

Page 45 of 90

26.09.2005

Page 44 Page 46
Image 45
Page 44 Page 46
Contents Java Users Guide TC65 Java Users Guide Document Name TC65 Java Users GuideSeptember 26 TC65 Java Users GuideV05Table of Contents 3.3.2 MaintenanceCompile and Run a Program without a Java IDE Debug EnvironmentJava Security Differences from the TC45 Java TutorialTables Sun Java Studio Mobility 6 Switching EmulatorsPreamble New solution OverviewRelated Documents Abbreviation Description Terms and AbbreviationsInstallation Installation CDSystem Requirements Module Exchange Suite Components1.2 WTK 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 Upgrades Smtk UninstallSoftware Architecture Software PlatformGeneral Purpose I/O Interfaces 1 ASC0 Serial Device3 DAC/ADC 4 ASC1IP Networking JVM InterfacesMedia Other InterfacesADC Data Flow of a Java Application Running on the ModuleModule States Handling Interfaces and Data Service ResourcesState 4 Default Java Application Active State 1 Default No Java RunningState 2 No Java Running, General Purpose I/O and I2C State 3 No Java Running, General Purpose I/O and SPIState 5 Java Application Active, General Purpose I/O and I2C Module State Transitions IP Service MaintenanceCharging Power SavingAlarm Airplane ModeShutdown Automatic ShutdownSpecial AT Command Set for Java Applications Restart after Switch OffSwitching from Data Mode to Command Mode Mode Indication after MIDlet StartupJava Commands Configuration of Serial InterfaceRestrictions Flash File System MemoryJava PerformanceFrequencyB 1 / frequencyA Duration of each loop = 600 sData Rates on RS-232 API Pin I/OVoice Call in Parallel Plain Serial InterfaceUpload Scenarios with Gprs Connection75% 63% 55% 33% 65% 55% 33% 16%Download 91% 87% 81% 73%85% 78% 58% 48% MIDlet Documentation MIDlet Life Cycle MIDletsMIDlet.destroyApp method Here is a sample HelloWorld program Hello World MIDletFile Transfer to Module Command Line BasedModule Exchange Suite Windows BasedSecurity Issues Over the Air ProvisioningOtap Over The Air Provisioning Otap Introduction to OtapOtap Overview Otap Parameters Parameters Max. Length AT Keyword SM Install/update DeleteInstall operation Short Message FormatDelete operation Java File Format Procedures Install/Update Delete Tips and Tricks for Otap Time Out Values and Result CodesSecurity Otap TracerHow To Build Results Compile and Run a Program without a Java IDECompile Run on the Module with Manual StartRun on the Module with Autostart Switch off Autostart Switch on AutostartData Flow of a Java Application in the Debug Environment Debug EnvironmentEmulator Java IDE Sun Java Studio Mobility 6 2004Q3 Switching emulators Projects Templates ExamplesCompile and run Borland JBuilder JBuilderX JDK settingsExamples TC65 Java Users Guide JBuilder2005 JDK settings Integration EclipseEclipse Plug-in installation Eclipse J2ME platform TC65 Java Users GuideV05 26.09.2005 Eclipse Project import ExampleEclipse Example Eclipse Create package Compile and debugBreakpoints Eclipse ConfigurationJava Security Mode Secure Data TransferJ a va C u r i t y c e r t i f i c a t e Asja VasecuritycertificateCreate CA and generate CA Root Certificate Create a Secure Data Transfer Environment Step by StepUnsecured mode Secured modeExecution Control Build binary data for AT command Atsjsec Change to Secured Mode ConceptGenerate key pair Generate customer root CertificateEncoded JAR-File Hash Concept for the Signing the Java MIDletApplication and Data Protection Structure and Description of the Java Security CommandsGeneral structure Structure of the Java Security CommandsHash SHA1 Build Java Security CommandATSJSEC? Send Java Security Command to the ModuleExport X.509 Root Certificate Create Java Security CommandsSign a MIDlet Command switch off module exchange functionalityClass ATCommand Using the AT Command APIJava Tutorial Instantiation with or without CSD SupportData Connections Sending an AT Command to the Device, the send MethodTC65 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.
Top Page Image Contents