Ticket #322 (closed enhancement: wontfix)

Opened 6 years ago

Last modified 6 years ago

gsmd phonebook cache and OTA updates to ADN/FDN/SDN

Reported by: eric@… Owned by: tick@…
Priority: high Milestone:
Component: GSM Modem Version: unspecified
Severity: minor Keywords:
Cc: buglog@…, jserv@… Blocked By:
Blocking: Estimated Completion (week):
HasPatchForReview: PatchReviewResult:
Reproducible:

Description

If gsmd employs a cache to avoid repeated accesses to the SIM addressbooks there
is a danger that it will not be up-to-date if the SIM has had an OTA update.

In such circumstances the SIM should issue a REFRESH command to the GSM modem so
that it will be aware of the change. I am not familiar enough with 07.10 and GSM
modems to know if this REFRESH would be propogated to gsmd. If it is then we
should ensure that gsmd handles it and refreshes the cache.

Notes:

1) Some operators provide a web interface to allow subscribers to send such OTA
updates to the addressbooks.

2) Older Nokia handsets had a mechanism which would read directly from the SIM
(ie pressing "1#" to read ADN record 1). Otherwise the handset uses its cached
version which would differ following an OTA on Phase 2 handsets which don't
support REFRESH. Maybe a similar approach should be adopted so the API allows
the cached version to be used or can force the entry to be read from the SIM.

Change History

comment:1 Changed 6 years ago by laforge@…

this is related to SIM toolkit, which we actually don't want to support for
security reasons. Anything that happens within the modem we can't
affect/prevent, at least not easily.

Anything that requires host support for STK will most likely not be implemented.

STK is often used to take away user control over the phone and give the operator
access to data owned by the user. this is evil.

comment:2 Changed 6 years ago by jserv@…

  • Cc jserv.tw@… added

comment:3 Changed 6 years ago by jserv@…

  • Owner changed from sean_chiang@… to tick@…

comment:4 Changed 6 years ago by tick@…

  • Status changed from new to closed
  • Resolution set to wontfix
  1. phonebook cache will not be in gsmd.

We will keep gsmd as a simple as possible.
We leave phonebook cache to service layer (dbus) or AP layer.
. Phonebook backup and update are STK issues

  1. STK will not be supported.


Note: See TracTickets for help on using tickets.