Functional Specifications for “On Demand Assistant” Application

Phase I: Basic Application Functions

Note: It is assumed that an NFC-enabled smartphone is being used.

  1. Format NFC Tags;
  2. Create recordings, using the smart phone, which are then stored locally on the smartphone;
  3. Associate local recordings with formatted NFC tags;
  4. Touch smartphone to an associated NFC tag. This triggers the playing of the local recording. No internet connectivity is required for this function.

Phase II: Extended Application Functions-1

Note: It is assumed that an audio file has been created and saved to phone using above procedure.

  1. The recording can be “Saved to cloud as Personal” and “Saved to cloud as Public.”  If saved to the cloud, a recording is saved to a database using the phone’s unique id, the tag’s id, and a [personal] or [public] flag.
  2. Touch any NFC-enabled smart phone to the NFC tags. Application sends phone unique ID and tag ID to the cloud to find an audio file that matches.
    2A. If the file is public, and the tag ID matches a CBAF, it is returned.
    2B. If it is personal and the Phone ID   AND  the Tag ID match a CBAF it is returned
  3. Any returned CBAF plays;

Implementation Phase I:

Note: It is assumed that a custom configuration application (CCA) has already been created, saved to the cloud, and an NFC tag has been programmed to provide a URL and a configuration code (which is already associated with the CCA).

  1. Touch any NFC-enabled smart phone to the associated NFC tags.
  2. The Preference Code is sent to the URL (essentially the NFC URL with parameter is just sent)
  3. A CCA is returned as part of a name-value pair in a JavaScript Object Notation (JSON) document. A JSON is a lightweight data-interchange format. It is easy for humans to read and write. It is easy for machines to parse and generate.
  4. The CCA is extracted and executed on the smartphone