All of lore.kernel.org
 help / color / mirror / Atom feed
From: Zhang, Caiwen <Caiwen.Zhang@windriver.com>
To: ofono@ofono.org
Subject: RE: UIM manager atom APIs review request
Date: Mon, 23 Aug 2010 04:27:45 +0200	[thread overview]
Message-ID: <D87B22B1FE8C0F479CA9BEAD6C25AAE8055DD09E@ism-mail03.corp.ad.wrs.com> (raw)
In-Reply-To: <AANLkTikoQ4wWNqDboq7fx1_81_A+HjUmQhL_VkHzc61t@mail.gmail.com>

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

Hi andrzej,

> -----Original Message-----
> From: ofono-bounces(a)ofono.org [mailto:ofono-bounces(a)ofono.org] On
> Behalf Of andrzej zaborowski
> Sent: Friday, August 20, 2010 10:14 PM
> To: ofono(a)ofono.org
> Subject: Re: UIM manager atom APIs review request
> 
> Hi Caiwen,
> 
> On 19 August 2010 05:46, Zhang, Caiwen <Caiwen.Zhang@windriver.com>
> wrote:
> > Hi all,
> >
> > 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
> 
> This API does not convey the information that LockedPINs conveys.
> LockedPINs can be useful if you wanted a settings application that can
> enable and disable PIN authentication.
> 

Sorry, I misunderstand 'LockedPINs' property's meaning. 

If so, we should initialize its value at the first time SIM is ready. I see 
currently, its value is initialized with the result of +CPIN?
If it is used as the purpose that you said, it should be +CLCK=<pin type>,2

Besides, the possible values of this property are: "pin","phone","firstphone"
"pin2","network","netsub","service","corp". It can't be other puk relative values.
	

Maybe we can use a method to replace this property. Such as:
	Boolean GetPinLock(string type) 
If the return value is TURE, means PIN authentication is enabled, otherwise,
Means PIN authentication is disabled.


Thanks!

Best regards,
Caiwen


  reply	other threads:[~2010-08-23  2:27 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-19  3:46 UIM manager atom APIs review request Zhang, Caiwen
2010-08-20 14:13 ` andrzej zaborowski
2010-08-23  2:27   ` Zhang, Caiwen [this message]
  -- strict thread matches above, loose matches on Subject: below --
2010-08-18 16:03 Zhang, Caiwen
2010-08-18 16:55 ` Marcel Holtmann
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

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=D87B22B1FE8C0F479CA9BEAD6C25AAE8055DD09E@ism-mail03.corp.ad.wrs.com \
    --to=caiwen.zhang@windriver.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.