Zone Oriented Applications, Systems and Methods

• US 20140129557A1
• Filed: 01/10/2014
• Published: 05/08/2014
• Est. Priority Date: 02/15/2012
• Status: Abandoned Application

• Current Assignee: Flybits Inc.
• Original Assignee: Flybits Inc.
• Inventors: Rahnama, Hossein
• Application Number:
  US14/152,827
• Publication Number:
  US 20140129557A1
• Time in Patent Office: Days
• US Class Current: 707/736
• CPC Class Codes: G06F 16/211 Schema design and management
• CPC Class Codes: G06F 16/23 Updating
• CPC Class Codes: G06F 16/24575 using context
• CPC Class Codes: G06Q 10/02 Reservations, e.g. for tickets, services or events
• CPC Class Codes: G06Q 30/0283 Price estimation or determination
• CPC Class Codes: G06Q 30/08 Auctions
• CPC Class Codes: H04L 41/24 using dedicated network management hardware
• CPC Class Codes: H04L 67/34 involving the movement of software or configuration parameters network booting or remote initial program loading [RIPL] G06F9/4416
• CPC Class Codes: H04L 67/52 specially adapted for the location of the user terminal
• CPC Class Codes: H04W 4/02 Services making use of location information
• CPC Class Codes: H04W 4/021 Services related to particular areas, e.g. point of interest [POI] services, venue services or geofences
• CPC Class Codes: H04W 4/21 for social networking applications
• CPC Class Codes: H04W 4/50 Service provisioning or reconfiguring

Abstract

Zone management infrastructure systems and methods are presented. A zone comprises a set of boundary conditions, which can include a geographic boundary. Zones further comprise a zone object representing the nature of the zone and the services or applications offered by the zone. Zone objects have intrinsic value based on their boundary conditions as well as the services they offer. Zone owners can allow third parties to offer services for the zone in exchange for a fee.

Claims

1. A zone management system comprising:

a database storing a plurality of zone objects, wherein each zone object comprises a context criteria comprising at least one of a condition and a requirement indicating an extent of a corresponding zone with respect to an attribute space;

a device interface communicatively coupled with an electronic device;

a zone server coupled with the database and device interface, and configured to obtain, via the device interface, device attribute data related to the electronic device;

compare the device attribute data with context criteria of a first of the plurality of zone objects to determine that the electronic device is contextually relevant to a first zone object;

instantiate the first zone object as a sensor application platform bound to the first zone, wherein the sensor application platform enables the zone server to access at least one sensor of the electronic device that is determined to be contextually relevant to the first zone object; and

collect sensor data from the at least one sensor.

2. The system of claim 1, wherein the zone server is further configured to configure a second electronic device to participate with a service according to a zone criteria of the first zone based on the collected sensor data,

3. The system of claim 2, wherein the service comprises a for-fee service.

4. The system of claim 2, wherein the service provides promotional information.

5. The system of claim 2, wherein the service includes providing access to multi-media objects.

6. The system of claim 2, wherein the service includes at least one of a web component, a map based interface, a communication component, a feedback interface, a notification, a reminder, an appointment and a sensor access.

7. The system of claim 1, wherein the zone server is configured to collect the sensor data via a push model.

8. The system of claim 1, wherein the zone server is further configured to compare the device attributes data with context criteria representing a multi-dimensional requirement to determine that the electronic device is contextually relevant to a first zone object.

9. The system of claim 1, wherein the zone server is further configured to compare the device attributes data with context criteria including a geographical boundary of a zone to determine that the electronic device is contextually relevant to a first zone object.

10. The system of claim 1, wherein the zone server is further configured to compare the device attributes data with context relating to a demographic to determine that the electronic device is contextually relevant to a first zone object.

11. The system of claim 1, wherein the zone server is further configured to compare the device attributes data with context criteria relating to a key demographic to determine that the electronic device is contextually relevant to a first zone object.

12. The system of claim 1, wherein the zone server is further configured to compare the device attributes data with context criteria relating to a relationship to determine that the electronic device is contextually relevant to a first zone object.

13. The system of claim 1, wherein the zone server is further configured to compare the device attributes data with context criteria relating to a time to determine that the electronic device is contextually relevant to a first zone object.

14. The system of claim 1, wherein the zone server is further configured to populate at least one field of a zone object template using the sensor data.

15. The system of claim 1, wherein the zone server is further configured to provide a recommendation to a zone manager based on the sensor data.

16. The system of claim 1, wherein the zone server is further configured to provide a zone management interface and sensor data acquisition capabilities to a zone manager.

17. The system of claim 1, wherein the zone server is further configured to compile a history related to the first zone using the sensor data.