Smart Spots are devices which provide the technology which allows users to get access to smart points of interaction so that they can obtain extra information (infotainment, etc.), provide suggestions (suggestions mailbox, etc.) or generate new content (co-creation, etc.). The data model contains resources to configure the interaction service such as the broadcasted URL (typically shortened), the period between broadcasts, the availability of the service, transmission power depending on the area to be covered, etc.

In addition to the presented data model, this entity type inherits from the Device entity type. This means that by hierarchy, the SmartSpot entity type is a subtype of Device and as a result it can be the subject of any of the properties that an entity of type Device may have.

Data Model

The data model is defined as shown below:

  • id : Unique identifier.

  • type : Entity type. It must be equal to SmartSpot.

  • source : A sequence of characters giving the source of the entity data.

    • Attribute type: Text or URL
    • Optional
  • dataProvider : Specifies the URL to information about the provider of this information

    • Attribute type: URL
    • Optional
  • announcedUrl : URL broadcasted by the device.

    • Attribute type: URL
    • Mandatory
  • signalStrength : Signal strength to adjust the announcement range.

    • Attribute type: Text
    • Allowed values: "lowest", "medium" or "highest".
    • Mandatory
  • bluetoothChannel : Bluetooth channels where to transmit the announcement.

    • Attribute type: Text
    • Allowed values: "37", "38", "39", "37,38", "38,39", "37,39" or "37,38,39".
    • Mandatory
  • coverageRadius : Radius of the spot coverage area in meters.

    • Attribute Type: Number
    • Default unit: Meters.
    • Optional
  • announcementPeriod : Period between announcements.

    • Attribute Type: Number
    • Default unit: Milliseconds.
    • Mandatory
  • availability: Specifies the functionality intervals in which the announcements will be sent. The syntax must be conformant with openingHours specification. For instance, a service which is only active on dayweeks will be encoded as "availability": "Mo,Tu,We,Th,Fr,Sa 09:00-20:00".

    • Attribute type: Text
    • Mandatory. It can be null.
  • refSmartPointOfInteraction : Reference to the Smart Point of Interaction which includes this Smart Spot.

Note: JSON Schemas only capture the NGSI simplified representation, this means that to test the JSON schema examples with a FIWARE NGSI version 2 API implementation, you need to use the keyValues mode (options=keyValues).

Examples of use

    "id": "SSPOT-F94C51A295D9",
    "type": "SmartSpot",
    "announcedUrl": "",
    "signalStrength": "high",
    "bluetoothChannel": "37-38-39",
    "coverageRadius": 30,
    "announcementPeriod": 500,
    "availability": "Tu,Th 16:00-20:00",
    "refSmartPointOfInteraction": "SPOI-ES-4326"

Use it with a real service