Zone Oriented Applications, Systems and Methods

• US 20130212130A1
• Filed: 12/20/2012
• Published: 08/15/2013
• Est. Priority Date: 02/15/2012
• Status: Abandoned Application

• Current Assignee: Flybits Inc.
• Original Assignee: Flybits Inc.
• Inventors: Rahnama, Hossein
• Application Number:
  US13/722,376
• Publication Number:
  US 20130212130A1
• Time in Patent Office: Days
• US Class Current: 707/792
• 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 zone database configured to store zone objects owned by different zone owners, each

zone object representative of a zone and having;

zone context criteria defined according to zone attributes adhering to an attribute space, and

at least one zone service;

a device interface configured to communicatively coupled with an electronic device; and

a zone server coupled with the zone database and the device interface, and configured to;

allow a zone owner to instantiate a zone object as an instantiated zone from the zone database by activating the at least one service as a persistent service according the zone object'"'"'s context criteria;

obtain device attributes from the electronic device via the device interface;

derive a device context from the device attributes;

identify the persistent service as being contextually relevant to the device context by comparing the device attributes to the zone object'"'"'s zone context criteria; and

configure the electronic device to participate with the persistent service according the device context and the zone context criteria.

2. The system of claim 1, further comprising a zone management interface coupled with the zone database and configured to offer a plurality of zone management functions to the zone owners.

3. The system of claim 2, wherein the zone management interface comprise a geographical zone definition tool.

4. The system of claim 3, wherein the geographical zone definition tool comprise at least one the following:

a map, a floor plan, a topology, a political boundary, an overlay, a street, a restricted air space, an air space, an area, a volume, and an object.

5. The system of claim 2, wherein the zone server is further configured to configure substantially in real-time the electronic device to participate with the at least one service according to an updated zone criteria submitted via the zone management interface.

6. The system of claim 1, wherein the attribute space comprises at least one following types of attributes:

geo-location, time, position, orientation, identity, weather, temperature, pressure, motion, demographics, value, density, rights, regulations, relationships, resources, and news events.

7. The system of claim 1, wherein the zone context criteria comprises a zone context defined as a function of the attribute space.

8. The system of claim 7, wherein the zone object comprises a pointer to a zone context plug-in.

9. The system of claim 8, wherein the zone context plug-in comprise at least one of the following:

zone context sensor plug-in, zone inference engine plug-in, zone roles plug-in and zone rules plug-in

10. The system of claim 7, wherein the zone context comprises an a priori defined context.

11. The system of claim 1, wherein zone context criteria comprise a zone profile template.

12. The system of claim 11, wherein the zone server is further configured to instantiate the zone object by populating features of the zone profile template.

13. The system of claim 11, wherein the zone profile template comprises at least one of the following types of templates:

an airport template, a public transit template, a conference template, a social networking template, an office template, a dinning template, and a gaming template.

14. The system of claim 1, wherein the zone server is further configured to activate a service-type handler on the electronic device to be receptive to the persistent service.

15. The system of claim 14, wherein the zone server is further configured to provision a platform-specific handler as the service type handler on the electronic device to be receptive to the persistent service.

16. The system of claim 15, further comprising a device management engine coupled with the zone server, and configured to deliver the platform-specific handler.

17. The system of claim 1, wherein the persistent service comprises a zone-bounded service.

18. The system of claim 1, wherein the persistent service comprises a navigation service.

20. The system of claim 1, wherein the zone server is configured to restrict access to zone objects to zone owners according to zone owner authentication.

19. The system of claim 30, wherein the navigation service configures the electronic device to be receptive to contextual zone markers deployed within a geographical boundary of the zone.