Open Source Telephony
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: ofono@ofono.org
Subject: Re: UIM manager atom APIs review request
Date: Wed, 18 Aug 2010 18:55:03 +0200	[thread overview]
Message-ID: <1282150503.23399.154.camel@localhost.localdomain> (raw)
In-Reply-To: <D87B22B1FE8C0F479CA9BEAD6C25AAE8055DC99D@ism-mail03.corp.ad.wrs.com>

[-- Attachment #1: Type: text/plain, Size: 2104 bytes --]

Hi Caiwen,

> I am going to implement an UIM manager atom for CDMA extension. Its APIs will be almost the same as 
> current SIM manger atom's APIs.  But I suggest maybe will can do some changes:
> 
> 	1. Add PIN remain retry count support
> 	2. replace properties 'Present' 'PinRequired' and 'LockedPins' with a new add property 'Status'
> 
> Properties	string Status [readonly]
> 			
> 			Contains the string type of the status of the SIM.  
> 			The possible values are:
> 			"ready" - Not waiting for a password
> 			"pin" - SIM PIN is required
> 			"phone" - Phone-to-SIM PIN is required  [GSM only]
> 			"firstphone" - Phone-to-very-first SIM
> 						PIN is required  [GSM only]
> 			"pin2" - SIM PIN2 is required
> 			"network" - Network Personalization password is
> 						required  [GSM only]
> 			"netsub" - Network subset personalization
> 						password is required  [GSM only]
> 			"service" - Service Provider personalization
> 						password is required  [GSM only]
> 			"corp" - Corporate personalization password
> 						is required  [GSM only]
> 			"puk" - SIM PUK is required
> 			"firstphonepuk" - Phone-to-very-first SIM PUK is
> 						required  [GSM only]
> 			"puk2" - SIM PUK2 is required
> 			"networkpuk" - Network personalization unblocking
> 						password is required  [GSM only]
> 			"netsubpuk" - Network subset personalization
> 						unblocking password is required  [GSM only]
> 			"servicepuk" - Service provider personalization
> 						unblocking password is required  [GSM only]
> 			"corppuk" - Corporate personalization unblocking
> 						password is required  [GSM only]
> 			"absent" - No SIM inserted

why? What is wrong with the current properties? I like to see this from
the UI point of view (and ConnMan as one user) why we should change it.

> 		array{uint8} PinRetryCount [readonly]
> 		
> 			 Contains the remain retry count of PIN,PIN2,PUK and PUK2

Only uint8 is needed here. The UI doesn't care about the retries other
PINs. I only care about the current one it needs to enter.

Regards

Marcel



  reply	other threads:[~2010-08-18 16:55 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-18 16:03 UIM manager atom APIs review request Zhang, Caiwen
2010-08-18 16:55 ` Marcel Holtmann [this message]
2010-08-19  6:32 ` Kalle Valo
2010-08-19  8:15   ` Marcel Holtmann
2010-08-19  9:48     ` Zhang, Caiwen
2010-08-19 10:57       ` Marcel Holtmann
2010-08-20  3:12         ` Zhang, Caiwen
2010-08-20  8:26           ` Marcel Holtmann
  -- strict thread matches above, loose matches on Subject: below --
2010-08-19  3:46 Zhang, Caiwen
2010-08-20 14:13 ` andrzej zaborowski
2010-08-23  2:27   ` Zhang, Caiwen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1282150503.23399.154.camel@localhost.localdomain \
    --to=marcel@holtmann.org \
    --cc=ofono@ofono.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox