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

Page 61

Java User’s Guide

8.7 Time Out Values and Result Codes

s

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: <productname>/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 pro- cedure 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 Section 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 [1]) 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.

wm_java_usersguide_v12

Page 61 of 123

2008-02-25

Confidential / Released

 

 

Image 61
Contents User’s Guide Trademark notice Java User’s GuideSoftware Platform ContentUDP Gpio MaintenanceOver The Air Provisioning Otap File Transfer to ModuleCompile and Run a Program without a Java IDE Compile and Run a Program with a Java IDEJava Security Differences to the TC45 123 Java Tutorial 113Tables Figures Java User’s Guide Preface Related Documents OverviewAbbreviation Description Terms and AbbreviationsURL System Requirements InstallationInstallation CD for AC65/AC75 and XT65/XT75 Installation CD for TC65 1.2 WTK Components Module Exchange SuiteNetBeans IDE SDK / JDKEclipse 3.2.2 IDE and Eclipse ME Plugin 1.5.5 or Eclipse 3.1.2 IDE and Eclipse ME PluginIntegrated Documentation Suite IDS GPS Evaluation SoftwareJava User’s Guide Step Installing the Standard Development Toolkit Siemens Mobility Toolkit InstallationInstalling the Smtk Environment How to use the Modify or Repair mode Installing Eclipse 3.0, Eclipse 3.1 or Eclipse Installing NetBeans IDE 5.0 / NetBeans IDEUsing Eclipse 3.0.1 or Eclipse Using Eclipse 3.1.0, Eclipse 3.1.1 or EclipseUpgrades Smtk UninstallSoftware Architecture Software PlatformGeneral Purpose I/O Interfaces 1 ASC0 Serial Device3 DAC/ADC 4 ASC17 GPS IP Networking JVM InterfacesMedia Other InterfacesData flow of a Java application running on the module Data Flow of a Java Application Running on the ModuleState 1 Default No Java Running Handling Interfaces and Data Service ResourcesModule States State 2 No Java Running, General Purpose I/O and I2C State 4 Default Java Application ActiveModule State Transitions Module State Transition DiagramIP Service MaintenancePower Saving Remote SIM AccessAlarm Airplane ModeCharging Shutdown Restart after Switch OffAutomatic Shutdown Manual ShutdownSwitching from Data Mode to Command Mode Special AT Command Set for Java ApplicationsMode Indication after MIDlet Startup Configuration of Serial InterfaceAutoExec Function Java CommandsSystem Out Serial interfaces3 UDP FileGpio Restrictions Flash File SystemJava PerformanceDuration of each loop = 600 s Data Rates on RS-232 API Pin I/OVoice Call in Parallel Plain Serial InterfaceScenarios with GPRS/EGDE Connection Upload Download Java User’s Guide System Time MIDlet Documentation MIDlet Life Cycle MIDletsApplication Management Software MIDlet Here is a sample HelloWorld program Hello World MIDletFile Transfer to Module Command Line BasedWindows Based Over the Air ProvisioningOtap Security IssuesIntroduction to Otap Over The Air Provisioning OtapOtap Overview Otap Parameters Parameters Max. Length AT Keyword SM Install/update DeleteShort Message Format Install operationDelete operation Java File Format Procedures Install/Update Delete Tips and Tricks for Otap Time Out Values and Result CodesSecurity Otap TracerHow To How To Build Results Compile and Run a Program without a Java IDERun on the Module with Manual Start CompileSwitch off Autostart Switch on AutostartUsing the graphical autoexecoff.exe tool Using the command line tool cmdautoexecoff.exeCompile and Run a Program with a Java IDE Setup a New ProjectEclipse 3.1.2 with ME Plugin Select e.g. TC65 Release 2 emulator Select Project01 and press Ctrl+N and select J2ME Midlet Modify Java source file printme.java template Java User’s Guide Data Flow of a Java Application in the Debug Environment Debug EnvironmentEmulator Java User’s Guide NetBeans IDE 5.0, NetBeans 5.5 or NetBeans Java IDENetBeans IDE 5.0 installed emulators Switching Emulator to IMP-NG EmulatorTemplates NetBeans IDE 5.0 selecting sample project Hello World Sample ExamplesStarting Debug Session without Downloading Java Files Compile and RunDisplaying Java System.out in NetBeans IDE window Eclipse Eclipse 3.0 and EclipseEclipse Display of different integrated emulators Using Eclipse with ME Plugin Switching EmulatorsAdditional Configuration of Integrated Emulator Eclipse with ME Plugin 1.5.0 J2ME platform Open menu File → Import → Existing Project into Workspace Import ExampleEclipse Create package Compile and DebugEclipse Configuration Starting Debug Session without Downloading Java Files Java User’s Guide Borland JBuilder JBuilder X JDK settingsJBuilder X Sample Projects Set the additional emulator parameter -noload and press OK JBuilder 2006 Enterprise/Developer JDK settings JBuilder 2006 Enterprise/Developer Sample Projects BreakpointsSwitching Java System.out to IDE Debug Window Important Information for Java Debugging on Windows Vista Secure Data Transfer Java SecurityMode Create a Secure Data Transfer Environment Step by Step Sign certificate request by CA Execute command Result Convert formatSecured mode Unsecured modeExecution Control Standard behavior of the moduleInsert Customer Root Certificate Change to Secured Mode ConceptConcept for the Signing the Java MIDlet Prepare MIDlet for Secured ModeApplication and Data Protection Structure and Description of the Java Security CommandsStructure of the Java Security Commands Build Java Security Command Build Java Security CommandConnect Jsec Ready Send Command Send Java Security Command to the ModuleExport X.509 Root Certificate Create Java Security CommandsCommand switch on Java Security Mode Sign a MIDlet Class ATCommand Using the AT Command APIJava Tutorial Instantiation with or without CSD SupportSending an AT Command to the Device, the send Method Data Connections Wmjavausersguidev12 116 2008-02-25 Confidential / Released Non-Blocking ATCommand.send Method ATCommandResponseListener InterfaceSynchronization ATEvents ATCommandListener InterfaceImplementation Registering a Listener with an ATCommand Instance Threads Programming the MIDletExample Java User’s Guide Differences to the TC45
Related manuals
Manual 90 pages 14.61 Kb

AC65, XT65, XT75, 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.