Linux SDK (lite-qmi)  MBPL_SDK_R25_ENG3
unpack_loc_GeofenceAddContextInd_t Struct Reference

#include <loc.h>

Data Fields

uint32_t status
 
uint32_t * pTransactionId
 
uint32_t * pGeofenceId
 
uint32_t * pContextId
 
uint16_t Tlvresult
 
swi_uint256_t ParamPresenceMask
 

Detailed Description

Contain the parameters for Geofence Add Context notification

Parameters
status
  • Status of the Add Geofence Context Request
    • Valid values:
      • eQMI_LOC_SUCCESS (0) - Request was completed successfully
      • eQMI_LOC_GENERAL_FAILURE (1) - Request failed because of a general failure
      • eQMI_LOC_UNSUPPORTED (2) - Request failed because it is not supported
      • eQMI_LOC_INVALID_PARAMETER (3) - Request failed because it contained invalid parameters
      • eQMI_LOC_ENGINE_BUSY (4) - Request failed because the engine is busy
      • eQMI_LOC_PHONE_OFFLINE (5) - Request failed because the phone is offline
      • eQMI_LOC_TIMEOUT (6) - Request failed because it has timed out
      • eQMI_LOC_CONFIG_NOT_SUPPORTED (7) - Request failed because an undefined configuration was requested
      • eQMI_LOC_INSUFFICIENT_MEMORY (8) - Request failed because the engine could not allocate sufficient memory for the request
      • eQMI_LOC_MAX_GEOFENCE_PROGRAMMED (9) - Request failed because the maximum number of Geofences are already programmed
      • eQMI_LOC_XTRA_VERSION_CHECK_FAILURE (10) - Location service failed because of an XTRA version-based file format check failure
      • eQMI_LOC_GNSS_DISABLED (11) - Request failed because the location service is disabled
  • Bit to check in ParamPresenceMask - 0x01
pTransactionId
  • Transaction ID
  • Transaction ID that was specified in the Add Geofence Context request. This parameter is always present if the status field is set to SUCCESS.
  • Bit to check in ParamPresenceMask - 0x10
pGeofenceId
  • Geofence ID
  • Geofence identifier allocated by the engine. If the client specifies the Geofence ID during the Add Geofence Context request,
  • the same ID is returned. If the client does not specify the Geofence ID during the Add Geofence Context request,
  • a new Geofence ID is created by the Geofence engine and returned.
  • Bit to check in ParamPresenceMask - 0x11
pContextId
  • Geofence context ID allocated by the engine. The context ID is generated by the Geofence engine to identify the context for a particular Geofence ID.
  • The same Geofence ID may be associated with multiple contexts.
  • Bit to check in ParamPresenceMask - 0x12
Tlvresult
  • Unpack result.

The documentation for this struct was generated from the following file: