From: Petteri Tikander <petteri.tikander@ixonos.com>
To: ofono@ofono.org
Subject: Re: Handling of Fixed Dialing
Date: Thu, 07 Oct 2010 18:28:04 +0300 [thread overview]
Message-ID: <201010071828.04248.petteri.tikander@ixonos.com> (raw)
In-Reply-To: <B668883EB5DD7144ADFC248A72176EA802AF618B@fioues07.ebgroup.elektrobit.com>
[-- Attachment #1: Type: text/plain, Size: 2339 bytes --]
Hi Jeevaka and Denis,
and thanks for the comments.
I checked the invalidated-flag of EFadn (from file status-byte of GET RESPONSE)
and it actually changed according to FDN-enabling/disabling. But for some
reason I didn't got any change in EFsst for FDN/ADN-services. Could it be a
good idea to add also reading of EFadn in the SIM-initialization routine,
check invalidated-flag, and make decision of continuing initialization routine
based on that?
The other issue was that selection of service table (SIM/USIM) based on
EFphase. So SIM returns '3' in my tests. But the SIM-card seems to be of type
SIM (not USIM), because I accessed some USIM-type elementary files (EFest,
EFpbr) and those returned only error-codes. Like phase (3g) wouldn't actually
be exactly the same thing than USIM-type. What about doing the next change in
the SIM-init routine (not trusting to EFphase response when accessing the
correct service tables):
- read first EFest
- if EFest-access gives a valid response, read EFust
- if EFest-access doesn't give a valid response, read EFsst
Br, Petteri
>
> I had a discussion with Denis today about both FDN and BDN status.
>
> GSM SIM Card:(EFsst)
>
> In this case, FDN service status depends on the bits in EFsst and
> EFadn invalidation information.( invalidation information is part of the
> "Get RESPONSE" response data)
>
> EFsst - FDN is allocated and activated in the SIM:
>
> FDN is enabled - When EFadn is invalidated or not activated.
> FDN is disabled - When EFadn is validated.
>
> EFsst - FDN is not allocated or not activated in the SIM:
> FDN is disabled
>
> Note: This information can be found in the 3GPP 11.11 specification
> section 11.5.1. Paragraph starts with "FDN capability request".
> Invalidation information bits information can be found in the 3GPP
> 51.011 specification section 9.2.1(Response parameters/data in case of
> an EF:) and section 9.3
>
> USIM Card:(EFust, EFest)
>
> In USIM case, FDN enabled/disabled dependents on the bits in the EFust
> and EFest.
>
> Let me know if something is unclear
>
> Thanks and Regards,
> jeevaka
> _______________________________________________
> ofono mailing list
> ofono(a)ofono.org
> http://lists.ofono.org/listinfo/ofono
>
next prev parent reply other threads:[~2010-10-07 15:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-06 14:17 Handling of Fixed Dialing Petteri Tikander
2010-10-06 14:17 ` [RFC PATCH 1/3] sim: check if Fixed Dialing is enabled in the SIM-card Petteri Tikander
2010-10-06 14:17 ` [RFC PATCH 2/3] modem: some debugs added for indicating modem state change Petteri Tikander
2010-10-06 14:17 ` [RFC PATCH 3/3] sim: ensure existence of imsi-code when handling sim_get_properties Petteri Tikander
2010-10-06 15:29 ` Handling of Fixed Dialing Marcel Holtmann
2010-10-06 15:36 ` Jeevaka.Badrappan
2010-10-07 15:28 ` Petteri Tikander [this message]
2010-10-07 15:31 ` Marcel Holtmann
2010-10-07 16:40 ` Jeevaka.Badrappan
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=201010071828.04248.petteri.tikander@ixonos.com \
--to=petteri.tikander@ixonos.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox