Re: Adding the MCC/MNC codes to m-b-p-i



<country="foo" mcc="000">
 <provider mnc="00">
   <name>Foo Provider</name>
   <cdma />
 </provider>
</country>

Yes that would work.

The example in 27.007 is:


AT+COPS=3,2;+COPS?;+COPS=3,0;+COPS?

+COPS: 0,2,"24405"        (get the country...

+COPS: 0,0,"RADIOLINJA"      ...and operator name)


Where the command AT+COPS=<mode>, <format>

<mode>:

0    automatic (<oper> field is ignored)

1    manual (<oper> field shall be present, and <AcT> optionally)

2    deregister from network

3    set only <format> (for read command +COPS?), do not attempt registration/deregistration (<oper> and < AcT> fields are ignored); this value is not applicable in read command response

4    manual/automatic (<oper> field shall be present); if manual selection fails, automatic mode (<mode>=0) is entered

<format>:

0    long format alphanumeric <oper>

1    short format alphanumeric <oper>

2    numeric <oper>

<oper>: string type; <format> indicates if the format is alphanumeric or numeric; long alphanumeric format can be upto 16 characters long and short format up to 8 characters (refer GSM MoU SE.13 [9]); numeric format is the GSM Location Area Identification number (refer TS 24.008 [8] subclause 10.5.1.3) which consists of a three BCD digit country code coded as in ITU‑T E.212 Annex A [10], plus a two BCD digit network code, which is administration specific; returned <oper> shall not be in BCD format, but in IRA characters converted from BCD; hence the number has structure: (country code digit 3)(country code digit 2)(country code digit 1)(network code digit 3)(network code digit 2)(network code digit 1)

The <opr> alphanumeric name will be as programmed into the handset and may vary. whereas the numeric format will be consistent and parseable.

-- Stuart


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]