api: add new LTE constant to the MM_ACCESS_TECHs
The 10.4 version of TS27.007 extends the range of values possible from AT+COPS? The range of values are as follows: 3GPP TS 27.007 V10.4.0, +COPS <AcT>: integer type; access technology selected 0 GSM 1 GSM Compact 2 UTRAN 3 GSM w/EGPRS 4 UTRAN w/HSDPA 5 UTRAN w/HSUPA 6 UTRAN w/HSDPA and HSUPA 7 E-UTRAN All but the LTE (E-UTRAN) value can be represented in MM 0.5, this patch adds a new constant to correct that, until the MM API is redesigned later for 0.6. Signed-off-by: Andrew Bird <ajb@spheresystems.co.uk>
This commit is contained in:

committed by
Dan Williams

parent
b0a2c76907
commit
2db79a8b54
@@ -163,6 +163,9 @@
|
|||||||
<tp:enumvalue suffix="HSPA_PLUS" value="9">
|
<tp:enumvalue suffix="HSPA_PLUS" value="9">
|
||||||
<tp:docstring>HSPA+ (ETSI 27.007: "UTRAN w/HSPA+")</tp:docstring>
|
<tp:docstring>HSPA+ (ETSI 27.007: "UTRAN w/HSPA+")</tp:docstring>
|
||||||
</tp:enumvalue>
|
</tp:enumvalue>
|
||||||
|
<tp:enumvalue suffix="LTE" value="10">
|
||||||
|
<tp:docstring>LTE (ETSI 27.007: "E-UTRAN")</tp:docstring>
|
||||||
|
</tp:enumvalue>
|
||||||
</tp:enum>
|
</tp:enum>
|
||||||
|
|
||||||
</interface>
|
</interface>
|
||||||
|
Reference in New Issue
Block a user