5. Glossary¶
- ADC¶
Analog-to-digital conversion
Analog-to-digital converter
- ADM¶
Application and Device Management
- AMI¶
Advanced Metering Infrastructure
- AII¶
Application Isolation Implementation
GEISA requires that platforms provide an Application Isolation Implementation that ensures GEISA applications cannot impact each other, or the platform they are running on, and that they are constrained to the resources allocated to them by the system operator. These requirements are discussed in System Architecture. Because GEISA supports different execution environments, the specification does not mandate a specific technology. On Linux Execution Environments, AII is typically provided by container technologies like cgroups and namespaces.
- API¶
Applications Programming Interface
- Application¶
A program, targeting a specific Execution Environment, typically delivered as a compiled set of binary codes and associated metadata, bundled into a standard artifact that can be transferred to a Platform Implementation for execution.
- Application Certifier¶
An organization acting in this role that may independently assess, test, and/or countersign application artifacts for validation of behaviors prior to deployment. Optional in context of this version of the Specification.
- Application Deployment Manifest¶
Operator-approved deployment manifest that defines the effective deployment parameters for a specific Edge Application in a target environment.
- Application Instance¶
An Application that has been installed on a Platform Implementation and for which that Platform Implementation can report a runtime state.
- Application Publisher¶
Organization or entity providing one or more Applications for Operator Testing, Deployment or Certification. Provides a signed package, vendor application manifest and associated collaterals.
- Application Vendor¶
Role responsible for application production and publication responsibilities in a GEISA workflow.
- CoAP¶
Constrained Applications Protocol
- COE¶
Common Operating Environment
The COE is the software platform specification which defines the software components, interfaces, and processes or tasks needed to implement a GEISA-conformant platform. The COE is designed to be flexible and modular, allowing for a variety of implementations that can meet the needs of different use cases and environmental constraints. The COE is intended to provide a common foundation for GEISA implementations, while also allowing for customization and innovation by implementers.
- Container¶
Within GEISA, applications are deployed within an Application Isolation Implementation which provides isolation and resource management capabilities. On servers and workstations running Linux, this is typically done using an Open Container Initiative (OCI) formatted container image, which is executed via a tool like Docker or Podman, relying on Linux kernel features such as cgroups and namespaces. GEISA uses its own formats for application images which are more efficient and appropriate for embedded environments. Platforms must provide an AII. The AII technology in use will vary depending on the execution environment. When this specification refers to a container or containerization, it usually is a reference to the AII provided by the EE.
- DER¶
Distributed Energy Resource
Distributed Energy Resource is a generic term that typically includes photo-voltaics coupled with a smart inverter, battery energy storage systems, electric vehicles, demand response, and other dispatchable load or generation available on the electric distribution network. DERs are typically owned by consumers or businesses, rather than utilities or wholesale energy market participants.
- DTLS¶
Data Transport Layer Security
- DNS¶
Domain Name Service
- EVSE¶
Electric Vehicle Supply Equipment
- FAN¶
Field Area Network, generally owned/operated by the Utility or Operator. Sometimes referred to as AMI network.
- Firmware¶
Firmware is the software and associated data deployed as part of an embedded GEISA device that provide the functionality required to initialize, control, and operate its hardware. Firmware is typically stored in non-volatile memory and may include a secure bootloader, OS/RTOS, device drivers, and middleware. Firmware is generally considered relatively static and is typically deployed as a versioned software image. Devices may require a reboot for a firmware update to take effect.
- EE¶
Execution Environment - one of LEE (Linux Execution Environment) or VEE (Virtual Execution Environment) which Edge Applications run on.
- EMA¶
Edge Management Agent
The EMA is the logical component of a GEISA ADM conformant platform which implements ADM capabilities on the edge device(s).
- EMS¶
Edge Management System - the central system implementing the management capabilities of the ADM Pillar, which will include the LwM2M server but may also include other software and/or capabilities.
Note: within the electric utility industry, EMS often means Energy Management System. Similarly, within the network management system EMS often means Element Management System. Within this specification EMS is used exclusively for Edge Management System.
- Edge Application¶
Workload running within a GEISA execution environment using GEISA platform services and API interfaces.
- Edge Device¶
A device running platform software that supports services conformant with the GEISA specification.
- GEISA¶
- GPIO¶
General Purpose Input/Output
- GUI¶
Graphical User Interface
- HAN¶
Home Area Network
- Hybrid Application Model¶
Processing for a function is divided between an Edge Application and one or more Vendor Application Servers. Merely using an off-edge server does not make an application hybrid.
- LAN¶
Local Area Network
- LEE¶
Linux Execution Environment
- LwM2M¶
Lightweight Machine-to-Machine
See [LwM2M]
- MQTT¶
MQTT is a light-weight publish and subscribe protocol formerly known as Message Queueing Telemetry Transport.
- OS¶
Operating System
- PII¶
Personally Indentifiable Information
PII is a term used to refer to sensitive personal information, such a person’s name, address, phone number, and government identification number. GEISA does not explicitly address PII, as policies and definitions may vary by jurisdiction, but some GEISA applications may process, store, or exchange PII.
- PKI¶
Public Key Infrastructure
- Platform¶
See Platform Implementation. In this specification, Platform refers to the Edge Device, not to a cloud platform.
- Platform Implementation¶
A combination of hardware and software which provides one or more GEISA conformant interfaces (ADM, API, EE).
- Platform Provider¶
Role responsible for supplying platform hardware, platform software, and associated platform trust material where applicable.
- POSIX¶
- RMS¶
Root Mean Square
- RTOS¶
Real Time Operating System
- Sandbox¶
The isolated space in which the VEE runs each application. Sandboxes are how the VEE provides the AII, as containers are in the LEE.
- SPI¶
Serial Peripheral Interface
- System Operator¶
Role with deployment-environment authority for approving, configuring, authorizing, deploying, and operating GEISA-managed devices and applications.
- System Owner¶
Role with the authority to set policies for a specific deployment environment. Typically, the owner of the GEISA-managed devices and applications.
- TLD¶
Top Level Domain
- Vendor Application Manifest¶
Publisher-supplied manifest for an Edge Application, provided with its application artifact as input to operator deployment decisions.
- Vendor Application Server¶
An application or service associated with an Application Vendor that operates outside the GEISA Execution Environment and communicates with one or more Edge Applications. A GEISA application may use one or more Vendor Application Servers. A Vendor Application Server may be hosted by the Application Vendor, System Operator, or another authorized party, and may run in a cloud, data center, or other non-edge environment.
- Userid¶
In context of GEISA MQTT APIs, this is a platform-local unique identifier assigned to a deployed GEISA application instance on that local device. It is used for topic routing and message correlation within a device. Implementations may map this identifier to underlying platform or application constructs such as application manifest details, container identities, or other information in order to ensure local uniqueness.
The userid is unique within the scope of a device but is not required to be globally unique (as of this specification version) and does not represent a human user.
In this version of the GEISA specification, platforms are not required to support concurrent execution of multiple instances of the same application version on a single device. Future revisions may expand this behavior.
- VEE¶
Virtual Execution Environment