Top |
This section defines enumerations and types that are used in the ModemManager interface.
Type of context (2G/3G) or bearer (4G).
Unknown bearer. |
||
Primary context (2G/3G) or default bearer (4G), defined by the user of the API. |
||
The initial default bearer established during LTE attach procedure, automatically connected as long as the device is regitered in the LTE network. |
||
Secondary context (2G/3G) or dedicated bearer (4G), defined by the user of the API. These bearers use the same IP address used by a primary context or default bearer and provide a dedicated flow for specific traffic with different QoS settings. |
Since: 1.10
Type of IP method configuration to be used in a given Bearer.
Unknown method. |
||
Use PPP to get IP addresses and DNS information. For IPv6, use PPP to retrieve the 64-bit Interface Identifier, use the IID to construct an IPv6 link-local address by following RFC 5072, and then run DHCP over the PPP link to retrieve DNS settings. |
||
Use the provided static IP configuration given by the modem to configure the IP data interface. Note that DNS servers may not be provided by the network or modem firmware. |
||
Begin DHCP or IPv6 SLAAC on the data interface to obtain any necessary IP configuration details that are not already provided by the IP configuration. For IPv4 bearers DHCP should be used. For IPv6 bearers SLAAC should be used, and the IP configuration may already contain a link-local address that should be assigned to the interface before SLAAC is started to obtain the rest of the configuration. |
Since: 1.0
Allowed authentication methods when authenticating with the network.
Since: 1.0
Multiplex support requested by the user.
Unknown. |
||
No multiplex support should be used. |
||
If available, multiplex support should be used. |
||
Multiplex support must be used or otherwise the connection attempt will fail. |
Since: 1.18
Purpose of the APN used in a given Bearer.
This information may be stored in the device configuration (e.g. if carrier specific configurations have been enabled for the SIM in use), or provided explicitly by the user.
If the mask of types includes MM_BEARER_APN_TYPE_DEFAULT
, it is expected
that the connection manager will include a default route through the specific
bearer connection to the public Internet.
For any other mask type, it is expected that the connection manager will
not setup a default route and will therefore require additional custom
routing rules to provide access to the different services. E.g. a bearer
connected with MM_BEARER_APN_TYPE_MMS
will probably require an explicit
additional route in the host to access the MMSC server at the address
specified by the operator. If this address relies on a domain name instead
of a fixed IP address, the name resolution should be performed using the
DNS servers specified in the corresponding bearer connection settings.
If not explicitly specified during a connection attempt, the connection
manager should be free to treat it with its own logic. E.g. a good default
could be to treat the first connection as MM_BEARER_APN_TYPE_DEFAULT
(with
a default route) and any other additional connection as
MM_BEARER_APN_TYPE_PRIVATE
(without a default route).
Unknown or unsupported. |
||
APN used for the initial attach procedure. |
||
Default connection APN providing access to the Internet. |
||
APN providing access to IMS services. |
||
APN providing access to MMS services. |
||
APN providing access to over-the-air device management procedures. |
||
APN providing access to voice-over-IP services. |
||
APN providing access to emergency services. |
||
APN providing access to private networks. |
||
APN providing access to over-the-air activation sites. Since 1.20. |
||
APN providing access to video sharing service. Since 1.20. |
||
APN providing access to a local connection with the device. Since 1.20. |
||
APN providing access to certain applications allowed by mobile operators. Since 1.20. |
||
APN providing access to XCAP provisioning on IMS services. Since 1.20. |
||
APN providing access to mobile hotspot tethering. Since 1.20. |
Since: 1.18
5G network access type preference, such as 3GPP (NR, E-UTRA) or non-3GPP (untrusted WiFi, trusted WiFi, wireline).
No access type preference, or unknown. |
||
3GPP access type only. |
||
All access types allowed but 3GPP preferred. |
||
Non-3GPP access type only. |
Since: 1.20
Bitmask specifying roaming allowance rules for different network types.
Since: 1.20
Value specifying how a given context was created, mostly for informative purposes.
Unknown. |
||
Profile created by an enterprise IT admin from the OS. |
||
Profile created by the user. |
||
Profile created by the operator through OMA-DM or similar. |
||
Profile created by the OEM that was included with the modem firmware. |
||
Profile created by the OS APN database. |
Since: 1.20
State of Call.
default state for a new outgoing call. |
||
outgoing call started. Wait for free channel. |
||
outgoing call attached to GSM network, waiting for an answer. |
||
incoming call is waiting for an answer. |
||
call is active between two peers. |
||
held call (by +CHLD AT command). |
||
waiting call (by +CCWA AT command). |
||
call is terminated. |
Since: 1.6
Reason for the state change in the call.
Default value for a new outgoing call. |
||
Outgoing call is started. |
||
Received a new incoming call. |
||
Dialing or Ringing call is accepted. |
||
Call is correctly terminated. |
||
Remote peer is busy or refused call. |
||
Wrong number or generic network error. |
||
Error setting up audio channel. Since 1.10. |
||
Call has been transferred. Since 1.12. |
||
Call has been deflected to a new number. Since 1.12. |
Since: 1.6
A bitfield describing which facilities have a lock enabled, i.e., requires a pin or unlock code. The facilities include the personalizations (device locks) described in 3GPP spec TS 22.022, and the PIN and PIN2 locks, which are SIM locks.
No facility. |
||
SIM lock. |
||
Fixed dialing (PIN2) SIM lock. |
||
Device is locked to a specific SIM. |
||
Device is locked to first SIM inserted. |
||
Network personalization. |
||
Network subset personalization. |
||
Service provider personalization. |
||
Corporate personalization. |
Since: 1.0
Network availability status as defined in 3GPP TS 27.007 section 7.3.
Since: 1.0
Describes the current subscription status of the SIM. This value is only available after the modem attempts to register with the network.
The subscription state is unknown. |
||
The account is unprovisioned. |
||
The account is provisioned and has data available. |
||
The account is provisioned but there is no data left. |
Since: 1.2
GSM registration code as defined in 3GPP TS 27.007.
Not registered, not searching for new operator to register. |
||
Registered on home network. |
||
Not registered, searching for new operator to register with. |
||
Registration denied. |
||
Unknown registration status. |
||
Registered on a roaming network. |
||
Registered for "SMS only", home network (applicable only when on LTE). Since 1.8. |
||
Registered for "SMS only", roaming network (applicable only when on LTE). Since 1.8. |
||
Emergency services only. Since 1.8. |
||
Registered for "CSFB not preferred", home network (applicable only when on LTE). Since 1.8. |
||
Registered for "CSFB not preferred", roaming network (applicable only when on LTE). Since 1.8. |
||
Attached for access to Restricted Local Operator Services (applicable only when on LTE). Since 1.14. |
Since: 1.0
State of a USSD session.
Unknown state. |
||
No active session. |
||
A session is active and the mobile is waiting for a response. |
||
The network is waiting for the client's response. |
Since: 1.0
UE mode of operation for EPS, as per 3GPP TS 24.301.
Unknown or not applicable. |
||
PS mode 1 of operation: EPS only, voice-centric. |
||
PS mode 2 of operation: EPS only, data-centric. |
||
CS/PS mode 1 of operation: EPS and non-EPS, voice-centric. |
||
CS/PS mode 2 of operation: EPS and non-EPS, data-centric. |
Since: 1.8
Mobile Initiated Connection Only (MICO) mode.
This is a 5G-specific registration setting.
Since: 1.20
Describes various access technologies that a device uses when registered with or connected to a network.
The access technology used is unknown. |
||
Analog wireline telephone. |
||
GSM. |
||
Compact GSM. |
||
GPRS. |
||
EDGE (ETSI 27.007: "GSM w/EGPRS"). |
||
UMTS (ETSI 27.007: "UTRAN"). |
||
HSDPA (ETSI 27.007: "UTRAN w/HSDPA"). |
||
HSUPA (ETSI 27.007: "UTRAN w/HSUPA"). |
||
HSPA (ETSI 27.007: "UTRAN w/HSDPA and HSUPA"). |
||
HSPA+ (ETSI 27.007: "UTRAN w/HSPA+"). |
||
CDMA2000 1xRTT. |
||
CDMA2000 EVDO revision 0. |
||
CDMA2000 EVDO revision A. |
||
CDMA2000 EVDO revision B. |
||
LTE (ETSI 27.007: "E-UTRAN") |
||
5GNR (ETSI 27.007: "NG-RAN"). Since 1.14. |
||
Cat-M (ETSI 23.401: LTE Category M1/M2). Since 1.20. |
||
NB IoT (ETSI 23.401: LTE Category NB1/NB2). Since 1.20. |
||
Mask specifying all access technologies. |
Since: 1.0
Radio bands supported by the device when connecting to a mobile network.
Unknown or invalid band. |
||
GSM/GPRS/EDGE 900 MHz. |
||
GSM/GPRS/EDGE 1800 MHz. |
||
GSM/GPRS/EDGE 1900 MHz. |
||
GSM/GPRS/EDGE 850 MHz. |
||
UMTS 2100 MHz (IMT, UTRAN band 1). Since 1.8. |
||
UMTS 1800 MHz (DCS, UTRAN band 3). Since 1.8. |
||
UMTS 1700 MHz (AWS A-F, UTRAN band 4). Since 1.8. |
||
UMTS 800 MHz (UTRAN band 6). Since 1.8. |
||
UMTS 850 MHz (CLR, UTRAN band 5). Since 1.8. |
||
UMTS 900 MHz (E-GSM, UTRAN band 8). Since 1.8. |
||
UMTS 1700 MHz (UTRAN band 9). Since 1.8. |
||
UMTS 1900 MHz (PCS A-F, UTRAN band 2). Since 1.8. |
||
UMTS 2600 MHz (IMT-E, UTRAN band 7). Since 1.8. |
||
GSM/GPRS/EDGE 450 MHz. |
||
GSM/GPRS/EDGE 480 MHz. |
||
GSM/GPRS/EDGE 750 MHz. |
||
GSM/GPRS/EDGE 380 MHz. |
||
GSM/GPRS/EDGE 410 MHz. |
||
GSM/GPRS/EDGE 710 MHz. |
||
GSM/GPRS/EDGE 810 MHz. |
||
E-UTRAN band 1. Since 1.8. |
||
E-UTRAN band 2. Since 1.8. |
||
E-UTRAN band 3. Since 1.8. |
||
E-UTRAN band 4. Since 1.8. |
||
E-UTRAN band 5. Since 1.8. |
||
E-UTRAN band 6. Since 1.8. |
||
E-UTRAN band 7. Since 1.8. |
||
E-UTRAN band 8. Since 1.8. |
||
E-UTRAN band 9. Since 1.8. |
||
E-UTRAN band 10. Since 1.8. |
||
E-UTRAN band 11. Since 1.8. |
||
E-UTRAN band 12. Since 1.8. |
||
E-UTRAN band 13. Since 1.8. |
||
E-UTRAN band 14. Since 1.8. |
||
E-UTRAN band 17. Since 1.8. |
||
E-UTRAN band 18. Since 1.8. |
||
E-UTRAN band 19. Since 1.8. |
||
E-UTRAN band 20. Since 1.8. |
||
E-UTRAN band 21. Since 1.8. |
||
E-UTRAN band 22. Since 1.8. |
||
E-UTRAN band 23. Since 1.8. |
||
E-UTRAN band 24. Since 1.8. |
||
E-UTRAN band 25. Since 1.8. |
||
E-UTRAN band 26. Since 1.8. |
||
E-UTRAN band 27. Since 1.8. |
||
E-UTRAN band 28. Since 1.8. |
||
E-UTRAN band 29. Since 1.8. |
||
E-UTRAN band 30. Since 1.8. |
||
E-UTRAN band 31. Since 1.8. |
||
E-UTRAN band 32. Since 1.8. |
||
E-UTRAN band 33. Since 1.8. |
||
E-UTRAN band 34. Since 1.8. |
||
E-UTRAN band 35. Since 1.8. |
||
E-UTRAN band 36. Since 1.8. |
||
E-UTRAN band 37. Since 1.8. |
||
E-UTRAN band 38. Since 1.8. |
||
E-UTRAN band 39. Since 1.8. |
||
E-UTRAN band 40. Since 1.8. |
||
E-UTRAN band 41. Since 1.8. |
||
E-UTRAN band 42. Since 1.8. |
||
E-UTRAN band 43. Since 1.8. |
||
E-UTRAN band 44. Since 1.8. |
||
E-UTRAN band 45. Since 1.8. |
||
E-UTRAN band 46. Since 1.8. |
||
E-UTRAN band 47. Since 1.8. |
||
E-UTRAN band 48. Since 1.8. |
||
E-UTRAN band 49. Since 1.10. |
||
E-UTRAN band 50. Since 1.10. |
||
E-UTRAN band 51. Since 1.10. |
||
E-UTRAN band 52. Since 1.10. |
||
E-UTRAN band 53. Since 1.10. |
||
E-UTRAN band 54. Since 1.10. |
||
E-UTRAN band 55. Since 1.10. |
||
E-UTRAN band 56. Since 1.10. |
||
E-UTRAN band 57. Since 1.10. |
||
E-UTRAN band 58. Since 1.10. |
||
E-UTRAN band 59. Since 1.10. |
||
E-UTRAN band 60. Since 1.10. |
||
E-UTRAN band 61. Since 1.10. |
||
E-UTRAN band 62. Since 1.10. |
||
E-UTRAN band 63. Since 1.10. |
||
E-UTRAN band 64. Since 1.10. |
||
E-UTRAN band 65. Since 1.8. |
||
E-UTRAN band 66. Since 1.8. |
||
E-UTRAN band 67. Since 1.8. |
||
E-UTRAN band 68. Since 1.8. |
||
E-UTRAN band 69. Since 1.8. |
||
E-UTRAN band 70. Since 1.8. |
||
E-UTRAN band 71. Since 1.8. |
||
E-UTRAN band 85. Since 1.20. |
||
CDMA Band Class 0 (US Cellular 850MHz). Since 1.8. |
||
CDMA Band Class 1 (US PCS 1900MHz). Since 1.8. |
||
CDMA Band Class 2 (UK TACS 900MHz). Since 1.8. |
||
CDMA Band Class 3 (Japanese TACS). Since 1.8. |
||
CDMA Band Class 4 (Korean PCS). Since 1.8. |
||
CDMA Band Class 5 (NMT 450MHz). Since 1.8. |
||
CDMA Band Class 6 (IMT2000 2100MHz). Since 1.8. |
||
CDMA Band Class 7 (Cellular 700MHz). Since 1.8. |
||
CDMA Band Class 8 (1800MHz). Since 1.8. |
||
CDMA Band Class 9 (900MHz). Since 1.8. |
||
CDMA Band Class 10 (US Secondary 800). Since 1.8. |
||
CDMA Band Class 11 (European PAMR 400MHz). Since 1.8. |
||
CDMA Band Class 12 (PAMR 800MHz). Since 1.8. |
||
CDMA Band Class 13 (IMT2000 2500MHz Expansion). Since 1.8. |
||
CDMA Band Class 14 (More US PCS 1900MHz). Since 1.8. |
||
CDMA Band Class 15 (AWS 1700MHz). Since 1.8. |
||
CDMA Band Class 16 (US 2500MHz). Since 1.8. |
||
CDMA Band Class 17 (US 2500MHz Forward Link Only). Since 1.8. |
||
CDMA Band Class 18 (US 700MHz Public Safety). Since 1.8. |
||
CDMA Band Class 19 (US Lower 700MHz). Since 1.8. |
||
UMTS 1700 MHz (EAWS A-G, UTRAN band 10). Since 1.8. |
||
UMTS 1500 MHz (LPDC, UTRAN band 11). Since 1.8. |
||
UMTS 700 MHz (LSMH A/B/C, UTRAN band 12). Since 1.8. |
||
UMTS 700 MHz (USMH C, UTRAN band 13). Since 1.8. |
||
UMTS 700 MHz (USMH D, UTRAN band 14). Since 1.8. |
||
UMTS 800 MHz (UTRAN band 19). Since 1.8. |
||
UMTS 800 MHz (EUDD, UTRAN band 20). Since 1.8. |
||
UMTS 1500 MHz (UPDC, UTRAN band 21). Since 1.8. |
||
UMTS 3500 MHz (UTRAN band 22). Since 1.8. |
||
UMTS 1900 MHz (EPCS A-G, UTRAN band 25). Since 1.8. |
||
UMTS 850 MHz (ECLR, UTRAN band 26). Since 1.8. |
||
UMTS 1500 MHz (L-band, UTRAN band 32). Since 1.8. |
||
For certain operations, allow the modem to select a band automatically. |
||
NGRAN band 1. Since 1.20. |
||
NGRAN band 2. Since 1.20. |
||
NGRAN band 3. Since 1.20. |
||
NGRAN band 5. Since 1.20. |
||
NGRAN band 7. Since 1.20. |
||
NGRAN band 8. Since 1.20. |
||
NGRAN band 12. Since 1.20. |
||
NGRAN band 13. Since 1.20. |
||
NGRAN band 14. Since 1.20. |
||
NGRAN band 18. Since 1.20. |
||
NGRAN band 20. Since 1.20. |
||
NGRAN band 25. Since 1.20. |
||
NGRAN band 26. Since 1.20. |
||
NGRAN band 28. Since 1.20. |
||
NGRAN band 29. Since 1.20. |
||
NGRAN band 30. Since 1.20. |
||
NGRAN band 34. Since 1.20. |
||
NGRAN band 38. Since 1.20. |
||
NGRAN band 39. Since 1.20. |
||
NGRAN band 40. Since 1.20. |
||
NGRAN band 41. Since 1.20. |
||
NGRAN band 48. Since 1.20. |
||
NGRAN band 50. Since 1.20. |
||
NGRAN band 51. Since 1.20. |
||
NGRAN band 53. Since 1.20. |
||
NGRAN band 65. Since 1.20. |
||
NGRAN band 66. Since 1.20. |
||
NGRAN band 70. Since 1.20. |
||
NGRAN band 71. Since 1.20. |
||
NGRAN band 74. Since 1.20. |
||
NGRAN band 75. Since 1.20. |
||
NGRAN band 76. Since 1.20. |
||
NGRAN band 77. Since 1.20. |
||
NGRAN band 78. Since 1.20. |
||
NGRAN band 79. Since 1.20. |
||
NGRAN band 80. Since 1.20. |
||
NGRAN band 81. Since 1.20. |
||
NGRAN band 82. Since 1.20. |
||
NGRAN band 83. Since 1.20. |
||
NGRAN band 84. Since 1.20. |
||
NGRAN band 86. Since 1.20. |
||
NGRAN band 89. Since 1.20. |
||
NGRAN band 90. Since 1.20. |
||
NGRAN band 91. Since 1.20. |
||
NGRAN band 92. Since 1.20. |
||
NGRAN band 93. Since 1.20. |
||
NGRAN band 94. Since 1.20. |
||
NGRAN band 95. Since 1.20. |
||
NGRAN band 257. Since 1.20. |
||
NGRAN band 258. Since 1.20. |
||
NGRAN band 260. Since 1.20. |
||
NGRAN band 261. Since 1.20. |
Since: 1.0
Flags describing one or more of the general access technology families that a modem supports.
Modem has no capabilities. |
||
Modem supports the analog wired telephone network (ie 56k dialup) and does not have wireless/cellular capabilities. |
||
Modem supports at least one of CDMA 1xRTT, EVDO revision 0, EVDO revision A, or EVDO revision B. |
||
Modem supports at least one of GSM, GPRS, EDGE, UMTS, HSDPA, HSUPA, or HSPA+ packet switched data capability. |
||
Modem has LTE data capability. |
||
Modem has Iridium capabilities. |
||
Modem has 5GNR capabilities. Since 1.14. |
||
Modem has TDS capabilties. Since 1.20. |
||
Mask specifying all capabilities. |
Since: 1.0
Activation state of a CDMA modem.
Unknown activation state. |
||
Device is not activated |
||
Device is activating |
||
Device is partially activated; carrier-specific steps required to continue. |
||
Device is ready for use. |
Since: 1.0
Registration state of a CDMA modem.
Registration status is unknown or the device is not registered. |
||
Registered, but roaming status is unknown or cannot be provided by the device. The device may or may not be roaming. |
||
Currently registered on the home network. |
||
Currently registered on a roaming network. |
Since: 1.0
Protocol of the Rm interface in modems with CDMA capabilities.
Unknown protocol. |
||
Asynchronous data or fax. |
||
Packet data service, Relay Layer Rm interface. |
||
Packet data service, Network Layer Rm interface, PPP. |
||
Packet data service, Network Layer Rm interface, SLIP. |
||
STU-III service. |
Since: 1.0
Specifies different storage locations for contact information.
Since: 1.0
Sources of location information supported by the modem.
None. |
||
Location Area Code and Cell ID. |
||
GPS location given by predefined keys. |
||
GPS location given as NMEA traces. |
||
CDMA base station position. |
||
No location given, just GPS module setup. Since 1.4. |
||
Mobile Station Assisted A-GPS location requested. Since 1.12. |
||
Mobile Station Based A-GPS location requested. Since 1.12. |
Since: 1.0
Type of assistance data that may be injected to the GNSS module.
Since: 1.10
Enumeration of possible lock reasons.
Lock reason unknown. |
||
Modem is unlocked. |
||
SIM requires the PIN code. |
||
SIM requires the PIN2 code. |
||
SIM requires the PUK code. |
||
SIM requires the PUK2 code. |
||
Modem requires the service provider PIN code. |
||
Modem requires the service provider PUK code. |
||
Modem requires the network PIN code. |
||
Modem requires the network PUK code. |
||
Modem requires the PIN code. |
||
Modem requires the corporate PIN code. |
||
Modem requires the corporate PUK code. |
||
Modem requires the PH-FSIM PIN code. |
||
Modem requires the PH-FSIM PUK code. |
||
Modem requires the network subset PIN code. |
||
Modem requires the network subset PUK code. |
Since: 1.0
Bitfield to indicate which access modes are supported, allowed or preferred in a given device.
Since: 1.0
Enumeration of possible modem states.
The modem is unusable. |
||
State unknown or not reportable. |
||
The modem is currently being initialized. |
||
The modem needs to be unlocked. |
||
The modem is not enabled and is powered down. |
||
The modem is currently transitioning to the |
||
The modem is currently transitioning to the |
||
The modem is enabled and powered on but not registered with a network provider and not available for data connections. |
||
The modem is searching for a network provider to register with. |
||
The modem is registered with a network provider, and data connections and messaging may be available for use. |
||
The modem is disconnecting and deactivating the last active packet data bearer. This state will not be entered if more than one packet data bearer is active and one of the active bearers is deactivated. |
||
The modem is activating and connecting the first packet data bearer. Subsequent bearer activations when another bearer is already active do not cause this state to be entered. |
||
One or more packet data bearers is active and connected. |
Since: 1.0
Enumeration of possible errors when the modem is in MM_MODEM_STATE_FAILED
.
No error. |
||
Unknown error. |
||
SIM is required but missing. |
||
SIM is available, but unusable (e.g. permanently locked). |
||
Unknown modem capabilities. Since 1.20. |
||
eSIM is not initialized. Since 1.20. |
Since: 1.0
Enumeration of possible reasons to have changed the modem state.
Reason unknown or not reportable. |
||
State change was requested by an interface user. |
||
State change was caused by a system suspend. |
||
State change was caused by an unrecoverable error. |
Since: 1.0
Type of modem port.
Unknown. |
||
Net port. |
||
AT port. |
||
QCDM port. |
||
GPS port. |
||
QMI port. |
||
MBIM port. |
||
Audio port. Since 1.12. |
||
Ignored port. Since 1.16. |
Since: 1.0
Type of firmware update method supported by the module.
No method specified. |
||
Device supports fastboot-based update. |
||
Device supports QMI PDC based update. |
||
Device supports MBIM QDU based update. Since 1.18. |
||
Device supports Firehose based update. Since 1.18. |
||
Device supports Sahara protocol. Usually used in combination with Firehose. Since 1.20. |
Since: 1.10
Features that can be enabled or disabled in the OMA device management support.
Since: 1.2
State of the OMA device management session.
Failed. |
||
Unknown. |
||
Started. |
||
Retrying. |
||
Connecting. |
||
Connected. |
||
Authenticated. |
||
MDN downloaded. |
||
MSID downloaded. |
||
PRL downloaded. |
||
MIP profile downloaded. |
||
Session completed. |
Since: 1.2
Reason of failure in the OMA device management session.
No reason or unknown. |
||
Network unavailable. |
||
Server unavailable. |
||
Authentication failed. |
||
Maximum retries exceeded. |
||
Session cancelled. |
Since: 1.2
Type of OMA device management session.
Unknown session type. |
||
Client-initiated device configure. |
||
Client-initiated PRL update. |
||
Client-initiated hands free activation. |
||
Network-initiated device configure. |
||
Network-initiated PRL update. |
||
Device-initiated PRL update. |
||
Device-initiated hands free activation. |
Since: 1.2
Type of PDUs used in the SMS.
Unknown type. |
||
3GPP Mobile-Terminated (MT) message. |
||
3GPP Mobile-Originated (MO) message. |
||
3GPP status report (MT). |
||
3GPP2 Mobile-Terminated (MT) message. Since 1.2. |
||
3GPP2 Mobile-Originated (MO) message. Since 1.2. |
||
3GPP2 Cancellation (MO) message. Since 1.2. |
||
3GPP2 Delivery Acknowledgement (MT) message. Since 1.2. |
||
3GPP2 User Acknowledgement (MT or MO) message. Since 1.2. |
||
3GPP2 Read Acknowledgement (MT or MO) message. Since 1.2. |
Since: 1.0
State of a given SMS.
State unknown or not reportable. |
||
The message has been neither received nor yet sent. |
||
The message is being received but is not yet complete. |
||
The message has been completely received. |
||
The message is queued for delivery. |
||
The message was successfully sent. |
Since: 1.0
Enumeration of known SMS delivery states as defined in 3GPP TS 03.40 and 3GPP2 N.S0005-O, section 6.5.2.125.
States out of the known ranges may also be valid (either reserved or SC-specific).
Since: 1.0
Storage for SMS messages.
Storage unknown. |
||
SIM card storage area. |
||
Mobile equipment storage area. |
||
Sum of SIM and Mobile equipment storages |
||
Status report message storage area. |
||
Broadcast message storage area. |
||
Terminal adaptor message storage area. |
Since: 1.0
Teleservice IDs supported for CDMA SMS, as defined in 3GPP2 X.S0004-550-E (section 2.256) and 3GPP2 C.S0015-B (section 3.4.3.1).
Unknown. |
||
IS-91 Extended Protocol Enhanced Services. |
||
Wireless Paging Teleservice. |
||
Wireless Messaging Teleservice. |
||
Voice Mail Notification. |
||
Wireless Application Protocol. |
||
Wireless Enhanced Messaging Teleservice. |
||
Service Category Programming Teleservice. |
||
Card Application Toolkit Protocol Teleservice. |
Since: 1.2
Service category for CDMA SMS, as defined in 3GPP2 C.R1001-D (section 9.3).
Since: 1.2
Indicates the frequency information provided belongs to which serving cell.
Unknown. |
||
In LTE CA, this refers to the primary cell. In ENDC case, this is the primary cell of MCS. In 5G SA, this refers to primary cell of NR. |
||
In LTE CA, this refers to the secondary cell. In ENDC case, this is the secondary cell of MCS. In 5G SA, this refers to secondary cell of NR. |
||
Refers to primary cell of secondary cell group (SCG). |
||
Refers to secondary cell of secondary cell group (SCG). |
||
Indicates that the radio is off, all other values are invalid. |
Since: 1.22