Expand description
Data structures used by operation inputs/outputs.
Modules§
Structs§
- AbpV11
ABP device object for LoRaWAN specification v1.1
- AbpV10X
ABP device object for LoRaWAN specification v1.0.x
- Accuracy
The accuracy of the estimated position in meters. An empty value indicates that no position data is available. A value of ‘0.0’ value indicates that position data is available. This data corresponds to the position information that you specified instead of the position computed by solver.
- Application
Config LoRaWAN application configuration, which can be used to perform geolocation.
- Beaconing
Beaconing parameters for configuring the wireless gateways.
- Cdma
Local Id CDMA local ID information, which corresponds to the local identification parameters of a CDMA cell.
- Cdma
NmrObj CDMA object for network measurement reports.
- CdmaObj
CDMA (Code-division multiple access) object.
- Cell
Towers The cell towers that were used to perform the measurements.
- Certificate
List List of sidewalk certificates.
- Connection
Status Event Configuration Connection status event configuration object for enabling or disabling topic.
- Connection
Status Resource Type Event Configuration Connection status resource type event configuration object for enabling or disabling topic.
- DakCertificate
Metadata The device attestation key (DAK) information.
- Destinations
Describes a destination.
- Device
Profile Describes a device profile.
- Device
Registration State Event Configuration Device registration state event configuration object for enabling and disabling relevant topics.
- Device
Registration State Resource Type Event Configuration Device registration state resource type event configuration object for enabling or disabling topic.
- Dimension
The required list of dimensions for the metric.
- Downlink
Queue Message The message in the downlink queue.
- Event
Configuration Item Event configuration object for a single resource.
- Event
Notification Item Configurations Object of all event configurations and the status of the event topics.
- FPorts
List of FPort assigned for different LoRaWAN application packages to use
- Fuota
Task A FUOTA task.
- Fuota
Task Event LogOption The log options for a FUOTA task event and can be used to set log levels for a specific FUOTA task event.
For a LoRaWAN FUOTA task, the only possible event for a log message is
Fuota
.- Fuota
Task LogOption The log options for FUOTA tasks and can be used to set log levels for a specific type of FUOTA task.
- Gateway
List Item Gateway list item object that specifies the frequency and list of gateways for which the downlink message should be sent.
- Global
Identity Global identity information.
- Gnss
Global navigation satellite system (GNSS) object used for positioning.
- GsmLocal
Id GSM local ID information, which corresponds to the local identification parameters of a GSM cell.
- GsmNmr
Obj GSM object for network measurement reports.
- GsmObj
GSM object.
- Imported
Sidewalk Device Information about a Sidewalk device that has been added to an import task.
- Imported
Wireless Device Information about a wireless device that has been added to an import task.
- Ip
IP address used for resolving device location.
- Join
Event Configuration Join event configuration object for enabling or disabling topic.
- Join
Resource Type Event Configuration Join resource type event configuration object for enabling or disabling topic.
- LoRa
WanConnection Status Event Notification Configurations Object for LoRaWAN connection status resource type event configuration.
- LoRa
WanConnection Status Resource Type Event Configuration Object for LoRaWAN connection status resource type event configuration.
- LoRa
WanDevice LoRaWAN object for create functions.
- LoRa
WanDevice Metadata LoRaWAN device metatdata.
- LoRa
WanDevice Profile LoRaWANDeviceProfile object.
- LoRa
WanFuota Task The LoRaWAN information used with a FUOTA task.
- LoRa
WanFuota Task GetInfo The LoRaWAN information returned from getting a FUOTA task.
- LoRa
WanGateway LoRaWANGateway object.
- LoRa
WanGateway Current Version LoRaWANGatewayCurrentVersion object.
- LoRa
WanGateway Metadata LoRaWAN gateway metatdata.
- LoRa
WanGateway Version LoRaWANGatewayVersion object.
- LoRa
WanGet Service Profile Info LoRaWANGetServiceProfileInfo object.
- LoRa
WanJoin Event Notification Configurations Object for LoRaWAN join resource type event configuration.
- LoRa
WanJoin Resource Type Event Configuration Object for LoRaWAN join resource type event configuration.
- LoRa
WanList Device LoRaWAN object for list functions.
- LoRa
WanMulticast The LoRaWAN information that is to be used with the multicast group.
- LoRa
WanMulticast Get The LoRaWAN information that is to be returned from getting multicast group information.
- LoRa
WanMulticast Metadata The metadata information of the LoRaWAN multicast group.
- LoRa
WanMulticast Session The LoRaWAN information used with the multicast session.
- LoRa
WanPublic Gateway Metadata LoRaWAN public gateway metadata.
- LoRa
WanSend Data ToDevice LoRaWAN router info.
- LoRa
WanService Profile LoRaWANServiceProfile object.
- LoRa
WanStart Fuota Task The LoRaWAN information used to start a FUOTA task.
- LoRa
WanUpdate Device LoRaWAN object for update functions.
- LoRa
WanUpdate Gateway Task Create LoRaWANUpdateGatewayTaskCreate object.
- LoRa
WanUpdate Gateway Task Entry LoRaWANUpdateGatewayTaskEntry object.
- LteLocal
Id LTE local identification (local ID) information.
- LteNmr
Obj LTE object for network measurement reports.
- LteObj
LTE object.
- Message
Delivery Status Event Configuration Message delivery status event configuration object for enabling and disabling relevant topics.
- Message
Delivery Status Resource Type Event Configuration Message delivery status resource type event configuration object for enabling or disabling relevant topic.
- Metric
Query Value The aggregated values of the metric.
- Multicast
Group A multicast group.
- Multicast
Group ByFuota Task A multicast group that is associated with a FUOTA task.
- Multicast
Wireless Metadata Wireless metadata that is to be sent to multicast group.
- Network
Analyzer Configurations Network analyzer configurations.
- OtaaV11
OTAA device object for v1.1
- Otaa
V10X OTAA device object for v1.0.x
- Participating
Gateways Specify the list of gateways to which you want to send downlink data traffic when the wireless device is running in class B or class C mode.
- Participating
Gateways Multicast Specify the list of gateways to which you want to send the multicast downlink messages. The multicast message will be sent to each gateway in the list, with the transmission interval as the time interval between each message.
- Position
Configuration Item The wrapper for a position configuration.
- Position
Solver Configurations The wrapper for position solver configurations.
- Position
Solver Details The wrapper for position solver details.
- Positioning
The FPorts for the position information.
- Proximity
Event Configuration Proximity event configuration object for enabling and disabling relevant topics.
- Proximity
Resource Type Event Configuration Proximity resource type event configuration object for enabling or disabling topic.
- Semtech
Gnss Configuration Information about the Semtech GNSS solver configuration.
- Semtech
Gnss Detail Details of the Semtech GNSS solver object.
- Service
Profile Information about a service profile.
- Session
Keys AbpV11 Session keys for ABP v1.1
- Session
Keys AbpV10X Session keys for ABP v1.1
- Sidewalk
Account Info Information about a Sidewalk account.
- Sidewalk
Account Info With Fingerprint Information about a Sidewalk account.
- Sidewalk
Create Device Profile Sidewalk object for creating a device profile.
- Sidewalk
Create Wireless Device Sidewalk object for creating a wireless device.
- Sidewalk
Device Sidewalk device object.
- Sidewalk
Device Metadata MetaData for Sidewalk device.
- Sidewalk
Event Notification Configurations SidewalkEventNotificationConfigurations
object, which is the event configuration object for Sidewalk-related event topics.- Sidewalk
GetDevice Profile Gets information about a Sidewalk device profile.
- Sidewalk
GetStart Import Info Sidewalk-related information for devices in an import task that are being onboarded.
- Sidewalk
List Device Sidewalk object used by list functions.
- Sidewalk
Resource Type Event Configuration Sidewalk resource type event configuration object for enabling or disabling topic.
- Sidewalk
Send Data ToDevice Information about a Sidewalk router.
- Sidewalk
Single Start Import Info Information about an import task created for an individual Sidewalk device.
- Sidewalk
Start Import Info Information about an import task created for bulk provisioning.
- Sidewalk
Update Account Sidewalk update.
- Sidewalk
Update Import Info Sidewalk object information for updating an import task.
- Summary
Metric Configuration The configuration of summary metrics.
- Summary
Metric Query The summary metric query object.
- Summary
Metric Query Result The result of the summary metrics aggregation operation.
- Tag
A simple label consisting of a customer-defined key-value pair
- Tdscdma
Local Id TD-SCDMA local identification (local Id) information.
- Tdscdma
NmrObj TD-SCDMA object for network measurement reports.
- Tdscdma
Obj TD-SCDMA object.
- Trace
Content Trace content for your wireless devices, gateways, and multicast groups.
- Update
AbpV11 ABP device object for LoRaWAN specification v1.1
- Update
AbpV10X ABP device object for LoRaWAN specification v1.0.x
- UpdateF
Ports Object for updating the FPorts information.
- Update
Wireless Gateway Task Create UpdateWirelessGatewayTaskCreate object.
- Update
Wireless Gateway Task Entry UpdateWirelessGatewayTaskEntry object.
- Wcdma
Local Id WCDMA local identification (local ID) information.
- Wcdma
NmrObj Network Measurement Reports.
- Wcdma
Obj WCDMA.
- WiFi
Access Point Wi-Fi access point.
- Wireless
Device Event LogOption The log options for a wireless device event and can be used to set log levels for a specific wireless device event.
For a LoRaWAN device, possible events for a log messsage are:
Join
,Rejoin
,Downlink_Data
, andUplink_Data
. For a Sidewalk device, possible events for a log message areRegistration
,Downlink_Data
, andUplink_Data
.- Wireless
Device Import Task Information about an import task for wireless devices.
- Wireless
Device LogOption The log options for wireless devices and can be used to set log levels for a specific type of wireless device.
- Wireless
Device Statistics Information about a wireless device's operation.
- Wireless
Gateway Event LogOption The log options for a wireless gateway event and can be used to set log levels for a specific wireless gateway event.
For a LoRaWAN gateway, possible events for a log message are
CUPS_Request
andCertificate
.- Wireless
Gateway LogOption The log options for wireless gateways and can be used to set log levels for a specific type of wireless gateway.
- Wireless
Gateway Statistics Information about a wireless gateway's operation.
- Wireless
Metadata WirelessMetadata object.
Enums§
- Aggregation
Period - When writing a match expression against
AggregationPeriod
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Application
Config Type - When writing a match expression against
ApplicationConfigType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Battery
Level - When writing a match expression against
BatteryLevel
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Connection
Status - When writing a match expression against
ConnectionStatus
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Device
Profile Type - When writing a match expression against
DeviceProfileType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Device
State - When writing a match expression against
DeviceState
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Dimension
Name - When writing a match expression against
DimensionName
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - DlClass
- When writing a match expression against
DlClass
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Downlink
Mode - When writing a match expression against
DownlinkMode
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Event
- When writing a match expression against
Event
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Event
Notification Partner Type - When writing a match expression against
EventNotificationPartnerType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Event
Notification Resource Type - When writing a match expression against
EventNotificationResourceType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Event
Notification Topic Status - When writing a match expression against
EventNotificationTopicStatus
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Expression
Type - When writing a match expression against
ExpressionType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Fuota
Device Status - When writing a match expression against
FuotaDeviceStatus
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Fuota
Task Event - When writing a match expression against
FuotaTaskEvent
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Fuota
Task Status - When writing a match expression against
FuotaTaskStatus
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Fuota
Task Type - When writing a match expression against
FuotaTaskType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Identifier
Type - When writing a match expression against
IdentifierType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Import
Task Status - When writing a match expression against
ImportTaskStatus
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - LogLevel
- When writing a match expression against
LogLevel
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Message
Type - When writing a match expression against
MessageType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Metric
Name - When writing a match expression against
MetricName
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Metric
Query Status - When writing a match expression against
MetricQueryStatus
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Multicast
Frame Info - When writing a match expression against
MulticastFrameInfo
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Onboard
Status - When writing a match expression against
OnboardStatus
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Partner
Type - When writing a match expression against
PartnerType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Position
Configuration Fec - When writing a match expression against
PositionConfigurationFec
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Position
Configuration Status - When writing a match expression against
PositionConfigurationStatus
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Position
Resource Type - When writing a match expression against
PositionResourceType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Position
Solver Provider - When writing a match expression against
PositionSolverProvider
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Position
Solver Type - When writing a match expression against
PositionSolverType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Positioning
Config Status - When writing a match expression against
PositioningConfigStatus
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Signing
Alg - When writing a match expression against
SigningAlg
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Summary
Metric Configuration Status - When writing a match expression against
SummaryMetricConfigurationStatus
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Supported
RfRegion - When writing a match expression against
SupportedRfRegion
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Wireless
Device Event - When writing a match expression against
WirelessDeviceEvent
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Wireless
Device Frame Info - When writing a match expression against
WirelessDeviceFrameInfo
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Wireless
Device IdType - When writing a match expression against
WirelessDeviceIdType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Wireless
Device Sidewalk Status - When writing a match expression against
WirelessDeviceSidewalkStatus
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Wireless
Device Type - When writing a match expression against
WirelessDeviceType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Wireless
Gateway Event - When writing a match expression against
WirelessGatewayEvent
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Wireless
Gateway IdType - When writing a match expression against
WirelessGatewayIdType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Wireless
Gateway Service Type - When writing a match expression against
WirelessGatewayServiceType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Wireless
Gateway Task Definition Type - When writing a match expression against
WirelessGatewayTaskDefinitionType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Wireless
Gateway Task Status - When writing a match expression against
WirelessGatewayTaskStatus
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature. - Wireless
Gateway Type - When writing a match expression against
WirelessGatewayType
, it is important to ensure your code is forward-compatible. That is, if a match arm handles a case for a feature that is supported by the service but has not been represented as an enum variant in a current version of SDK, your code should continue to work when you upgrade SDK to a future version in which the enum does include a variant for that feature.