Proposal v2: identifying modems and mobile broadband cards

[Dan Williams]

On Mon, 2008-02-11 at 18:21 +0100, Marcel Holtmann wrote:
> Hi Dan,
> 
> > - An interface that has the "serial" capability acquires the 'modem'
> > capability if the serial interface is indeed known to have a modem on
> > the other side
> > 
> > - An interface with the 'modem' capability may also acquire the property
> > 'modem.at_command_sets', which is a string array of supported command
> > sets, denoted by their abbreviated standards name. If the property is
> > present, it is assumed the modem supports rudimentary Hayes-compatible
> > AT commands.  The key may contain _one or more_ of the following values:
> > 
> >    a) IS-707-A  (for CDMA supporting cards)
> >    b) GSM-07-07  (for GSM supporting cards)
> >    c) GSM-07-05  (for GSM supporting cards)
> 
> I would say we use modem.command_sets then we could specific non-AT
> command sets if needed.

Yep, had just sent mail changing that.

> I think its is clear IS-* and GSM-* imply basic Hayes-compatible
> commands. At least for GSM I know it is part of the specification.

> Can we use the ETSI document numbers instead of calling it GSM. It is no
> longer GSM only. Nowadays they cover also UMTS. For GPRS/EDGE and UMTS
> the commands are actually the same.

I could only find ETSI doc #s for 07.07 (ETS-300-682).  Any idea what
07.05 is?  However, most references are still to GSM 07.07 and GSM
07.05...  If there aren't any additional AT commands that
GPRS/EDGE/UMTS/HSPA support, then it's still really a GSM standard that
they implement.  I don't really care one way or the other though, simply
that there's a good way to ID these things.

> Other than that. I am all for it. It is simple enough. Which is good.

Will post a v3 proposal with these changes then once I figure out the
document naming.

Dan