OTA技术.ppt

* Describe the architecture following the product life cycle. 1) Design of the service by the Simgo Service Designer By the marketing service of the operatot By external content providers 2) Services provisioned in the Simgo Service Platform. 3 roles: Store information on services in the Services Database Store information on users in the User Database Deploy the services on the cards communicating with the operator SMS-C Platform independent of OTA platform or integrated (For security) according to operator requirements 3) The subscriber wants to download a service. 3 possibilities: Through the Web site Calling the Customer Care Directly from its mobile handset 4) The SSP analyses the requirement and send the service OTA to the subscriber’s card 5) The interoperable applet (Working on JavaCard 2.1 compliant cards) installs the service and executes it. * Great flexibility in the access to the catalogue of services and the downloading: Web interface: Current content of the card Catalogue of services Possibility to add / delete a service, modify the menus, classify the services in menus Customer Care: Subscriber can call the Customer Care to order the download of a service Pull from mobile phone: Download the catalogue of services in a category Order the downloading of a service from this list Delete a service locally Available from Autumn 2002 This flexibility facilitates the adoption of mobile services by the subscribers. * Simgo minimizes administrative SMS traffic: Light byte code No code duplication inside module (for instance, if a proactive is used several times in the same module) A service is composed of a module and 0, 1 or many terminal modules Terminal module factorisation: several modules can use the same terminal module (Ex: Process of SMS sending with errors management) Concatenation of administrative commands Example: In 1 SMS, Delete a service, Activate another and Order an introspection Example of the NEWS service in a standard Java applet and i