Automated Experience Discovery

This is the page on which all our past work on topic of "Ad hoc Experience Discovery" has been consolidated. The first was written by Christine. Feedback from Doug and Josh is that it was too detailed. So Christine wrote another one (it is called Passive (Automatic, Staged by the User) AR Experience Discovery). Use Case 1: Continuous, Automatic, Context-based Discovery of Geospatial AR Experiences

Actors

User, Software for AR experience discovery on user’s network-accessible mobile device (has configuration preferences interface, otherwise does not have a UI), Software for AR experience presentation on user’s network-accessible mobile device, User’s mobile device hardware (e.g., display, compute, sensor), network-accessible catalog with which two publishers have registered, remote resources (e.g., AR experiences stored on publisher #1’s server,  AR experiences stored on publisher #2’s server) Description

This use case describes the process of a user’s context-aware AR-enabled device performing continuous automatic discovery of geospatial AR experiences that were recently created and provide historical information about Points of Interest found within 10 m radius of the user. Pre-conditions

Two unrelated AR Experience designers (#1 and #2) have each published 100 geospatial AR experiences to their servers. They used different AR Authoring tools and produced “CARIF compliant” URLs. The AR Experiences are composed of [text label] [ geospatial coordinate trigger] [interaction]. Each experience also has metadata indicating the developer’s affiliation, time stamp of publication, type of experience (CV or geospatial), access restrictions, keywords. One of the keywords entered in 20 of the experiences is “history.” There is a field for restrictions/conditions for access to the experience but it is empty (no key, anyone can access). The servers on which these experiences are hosted have “relationships” (could be manual or automatic) that register the experiences with a catalog service. Catalog service is on both the servers hosting the content? on another server? on the server operated by the AR authoring system? The user has previously configured the AR discovery agent (software client) on the device specifying that they would like to be receiving publicly available AR experiences published by any developer and that are triggered by the geospatial position of the user’s device, created in the past 24 hours, matching keyword “history.” The user’s device has Internet connectivity, operating GPS, compass, gyro and accelerometer. The user’s device has all necessary software to open and render AR experiences. Flow of events 

User turns on the device.

AR discovery agent establishes connection to catalog service.

AR discovery agent sends the user profile (24 hours, history, 10m) - where? Maybe sends user interest to broker to identify which catalogs are targets, and returns a list of experience catalogs

AR discovery agent sends position and context to catalogs (after requests position from the device)

Catalog service(s) return experience metadata hits to agent. AR discovery agent sends position to the catalog service.

AR catalog service queries the catalogs which contain metadata of all the AR experiences published and registered with it.

Metadata matching the user’s context and settings is found.

URLs of the experience matching the metadata is sent to the user’s AR discovery agent (should this, the receiver function, be separate from context sender function?)</li>

AR discovery agent sends requests to the URLs returned containing name (or some other identifying information) of the AR client application (hence the syntax it can use).</li>

AR Publisher #1 server sends (to which receiver?) [text label] [ geospatial coordinate trigger] [interaction] in the syntax needed for the AR client application.</li>

AR Publisher #2 server sends (to which receiver?) [text label] [ geospatial coordinate trigger] [interaction] in the syntax needed for the AR client application.</li>

AR discovery agent repeats Task 3 and 4 at 1 second intervals.</li>

AR client application receives and, if prompted by the user, opens AR experiences from two publishers.</li> </ol>

Post-conditions

AR Experiences matching the keyword “history” are presented (rendered) as the user travels along a trajectory. Use Case 2: Passive (Automatic, Staged by the User) AR Experience Discovery Actors

Numerous AR Experience Publishers who have advertised their experiences, End User Description

In this use case, there is not a user involved after having configured an agent on the mobile device to and before having an AR-assisted experience involving some geospatially-referenced data. Pre-conditions There are thousands of AR experience developers who have prepared content so that it can be retrieved based on metadata. There are catalog services that “know” about these published AR experiences. The user has a mobile device with GPS, compass and it is network connected. The user has configured an AR Discovery agent with personal profile to detect when there are new experiences available that have a historic/cultural heritage theme, pertain to any Point of Interest within 10 m radius and have been published in the recent past (24 hours). The agent is running in the background to send context and profile information to catalog services broker. Flow of events

<ol> The user puts the mobile AR-ready device in a pocket and begins walking down a busy street using a familiar route.</li>

When experiences matching the criteria are returned to the user’s device from multiple experience publishers, there is a vibration of the mobile device, similar to that which would be caused by an incoming SMS.</li>

The user opens the AR experience presentation application and scans by rotating in a clockwise direction.</li>

An arrow appears to indicate the recommended orientation to see the new experiences from multiple publishers.</li>

The user looks first at the experience published by the advertising sponsored publisher (free).</li>

Then decides to also open and interact with the second experience provided by a publisher with whom the user has a pre-existing contract.</li> </ol> Post-conditions

All interactions with the experiences are logged and returned to the experience database without any role of the discovery service.