The essentials
POI-based playback shows location-specific content when a robot reaches a point of interest or enters its area. Start by designing location detection, event delivery, and screen transitions as separate functions. The following is a design proposal for evaluation; it does not establish that a particular AI Cube product has implemented these features.
Key takeaways
- A point of interest (POI) links a location to a specific information or playback action.
- Assign separate responsibilities for robot movement control and screen content playback.
- Test duplicate, delayed, and missing events as well as normal entry.
What information belongs in a location event?
For an exhibition guide, an event might specify the exhibit identifier, entry or exit, occurrence time, and validity period. Also decide whether repeated events near a boundary should restart content or leave the current playback running.
Match screen transitions to entry and exit
For each content type, decide whether a new event should interrupt current playback, wait until it ends, or return the screen to default information. Keep safety-related robot actions in a separate control system that does not depend on screen playback results.
Define behavior for exceptions
The following are example rules to consider in a PoC. Agree on actual behavior with the site operator and robot supplier.
| Situation | Behavior to consider | Records to keep |
|---|---|---|
| Repeated event | Decide whether to apply the same event only once | Event ID and duplicate status |
| Delayed event | Ignore events past their validity period | Occurrence and receipt times |
| Missing content file | Return to the default information screen | Missing file and recovery result |
What changes and where it applies
Making a scheduled screen respond to location requires additional rules for location events and exceptional conditions.
AI Cube’s perspective
For robot guidance screens, examine both the arrival of location information and the resulting content transition. The product team must confirm any integration scope with CubeSignP5. Support for this proposal and PoC results have not been verified.
Technical considerations
Agree on the event format, time reference, and error-handling responsibilities between the location system and the player. Both systems need to interpret the same situation consistently.
Business and operations
Separate the roles of content operators and robot operators, and define the guidance scenarios used to evaluate success. This connects demonstration scenes with actual operating requirements.
Related products and solutions
Frequently asked questions
Must POI events use MQTT?
Choose a communication method that fits the robot supplier’s interface and the site environment. This article uses the MQTT standard as a reference for message delivery conditions.
Sources and reference dates
- MQTT Version 5.0 — reference for message delivery and expiry rules ↗OASIS · Source date 2019-03-07 · Accessed 2026-09-10
Evaluating a deployment?
Tell us about your installation and operating conditions so we can discuss relevant products and the scope of a PoC.
Technical and PoC inquiries ↗