Multicast group attributes

tip

In ThingPark's user interface, editable fields are displayed with grey background.

General attributes

Attribute	Definition
Name	Friendly name of your multicast group. It is given during the initial declaration of the multicast group on ThingPark, but can be changed any time from the multicast group's detailed dashboard. You may search multicast groups by their name on ThingPark's user interface. The multicast group name is reported to third party applications in the multicast summary report, alongside the DevEUI and the DevAddr.
Domains	If the segregation based on domains has been enabled by an administrator, the Domains attribute contains the list of domains associated with the multicast group. If your user account has domain restrictions, the domains you associate with your multicast group must match your domain restrictions without any domain prefix (only full domains can be assigned to resources). See About domains for more details.
DevEUI	Globally-unique identifier of the multicast group. A DevEUI is composed of 32 hexadecimal digits (0 to 9, and A to F). Example: F0-3D-29-00-0B-B1-7A-AA
Device address	The device address (DevAddr) consists of 8 hexadecimal digits, acting as a short identifier in the LoRaWAN® network. This is the address configured in all devices belonging to the multicast group, then set in ThingPark when the multicast group is added to the system. The most significant bits of the address identify the LoRaWAN® network ID (NwkID), which is derived from the operator's NetID. Example: 00-AB-C4-89
Connectivity plan	A connectivity plan (CP) defines a set of parameters associated with each multicast group and determining its service profile, such as the multicast settings, like the maximum number of base stations which can be added in the scope of the multicast group Each ThingPark Enterprise subscription is associated with a system-default multicast connectivity plan. TPE-SaaS subscriptions support 2 modes: Implicit (basic) mode: this is the default mode, whereby the connectivity plan is hidden. Explicit (advanced) mode: this mode is available only for subscriptions that are configured to use customized connectivity plans besides the default one. This mode is required only for customers having specific deployment use cases that require fine-tuning of the technical LoRaWAN settings included in the connectivity plan. Self-hosted TPE use exclusively the implicit/basic CP mode, hence the connectivity plan is hidden in the user interface.
Connections	List of connections used to route the multicast summary reports to external Application Servers. It may be edited at any time by the device manager. A multicast group may be associated with multiple connections (up to 5 by default). If the multicast group is not associated with any connection, its multicast summary reports are only visible in the multicast group dashboard and in Wireless Logger, without being routed to any external Application Server. To learn more about the different connection types, see Connecting an application.
LoRaWAN version	LoRaWAN version implemented by the devices within the multicast group. Supported LoRaWAN versions are 1.0.x and 1.1.
NwkSKey	Network Session Key, relevant only for LoRaWAN 1.0. Composed of 32 hexadecimal digits (0 to 9, and A to F). It is used in data integrity. This key is configured in all devices belonging to the multicast group, then set in ThingPark when the multicast group is added to the system.
SNwkSIntKey	Serving Network Session Integrity Key, relevant only for LoRaWAN 1.1. Composed of 32 hexadecimal digits (0 to 9, and A to F). It provides integrity protection, through the Message Integrity Code (MIC). This key is configured in all devices belonging to the multicast group, then set in ThingPark when the multicast group is added to the system.
AppSKey	Application Session Key, relevant for all LoRaWAN versions. Composed of 32 hexadecimal digits (0 to 9 and A to F). It is used to encrypt the application payload over the air. This key is configured in all devices belonging to the multicast group, then set in ThingPark when the multicast group is added to the system.
Base station tags	The base station tags define the list of base stations transmitting downlinks sent to the multicast group.
Class type	LoRaWAN class implemented by the devices within the multicast group: only B and C can be used for multicast transmission. See Device classes for more details.
Ping-slot period	Periodicity of multicast reception window expressed in seconds. Only applicable when Class B is selected. Possible values are 1, 2, 4, 8, 16, 32, 64, and 128.
Downlink frequency	Frequency in MHz used to transmit multicast downlink packets. Only downlink frequencies supported by the associated base stations are available. Hence at least one base station tag must be selected to configure this attribute.
Downlink data rate	LoRaWAN data rate used to transmit multicast downlink packets. Only downlink data rates supported by the associated base stations are available. Hence at least one base station tag must be selected to configure this attribute.
Additional information	Any useful administrative information related to the multicast group (free text). It may be changed anytime by the device manager.
Added	Date/time of the multicast group addition to your ThingPark account.

Dynamic attributes (related to multicast group activity)

Attribute	Definition
Active alarms	Number of alarms - split by severity - currently raised on this multicast group and not yet acknowledged. To learn more, see Device alarms. Tip Click on a colored alarm badge to access the list of corresponding active and not-acked alarms.
Last downlink	Timestamp of the last downlink packet sent to the multicast group.
Downlink packets for the last 24 hours	Aggregated count of distinct downlink packets sent to the multicast group over the last 24 hours.
Number of base stations	Number of base stations associated with the multicast group through base station tags.