U.S. patent application number 14/256530 was filed with the patent office on 2016-10-20 for volumetric vector node and object based multi-dimensional operating system.
This patent application is currently assigned to ATLYS, INC.. The applicant listed for this patent is ATLYS, INC.. Invention is credited to Charles Nathan Adelman.
Application Number | 20160306825 14/256530 |
Document ID | / |
Family ID | 54322179 |
Filed Date | 2016-10-20 |
United States Patent
Application |
20160306825 |
Kind Code |
A9 |
Adelman; Charles Nathan |
October 20, 2016 |
Volumetric Vector Node and Object Based Multi-Dimensional Operating
System
Abstract
A method for the visualization and addressing of data within a
volumetric container, using XYZ coordinates represented as a
vector. Whereas users build their own immersive experience,
variants, and/or representations of their respective data as
polygons nested within a virtual universe. This includes variants
such as time, space, velocity and trajectory as they relate to data
containers, and the tracking of each user's multi-dimensional
representations. This method also creates permanent threaded
connections between web data, social communities and data retrieved
from any other source, to a structured polygon based correlation
library.
Inventors: |
Adelman; Charles Nathan;
(Thousand Oaks, CA) |
|
Applicant: |
Name |
City |
State |
Country |
Type |
ATLYS, INC. |
South Jordan |
UT |
US |
|
|
Assignee: |
ATLYS, INC.
South Jordan
UT
|
Prior
Publication: |
|
Document Identifier |
Publication Date |
|
US 20150302031 A1 |
October 22, 2015 |
|
|
Family ID: |
54322179 |
Appl. No.: |
14/256530 |
Filed: |
April 18, 2014 |
Related U.S. Patent Documents
|
|
|
|
|
|
Application
Number |
Filing Date |
Patent Number |
|
|
61814177 |
Apr 19, 2013 |
|
|
|
Current U.S.
Class: |
1/1 |
Current CPC
Class: |
G06F 16/9566 20190101;
G06F 16/21 20190101; G06F 16/289 20190101; G06F 16/2237 20190101;
G06F 16/283 20190101; G06F 16/2264 20190101; G06Q 30/0277
20130101 |
International
Class: |
G06F 17/30 20060101
G06F017/30; G06Q 30/02 20060101 G06Q030/02 |
Claims
1. A volumetric vector node and object based multi-dimensional
operating system which is implemented through an immersive
volumetric operating container.
2. A volumetric vector node and object based multi-dimensional
operating system as recited in claim 1, wherein the master
operating system is volumetrically broken down by the aggregate
total space to form its total volume.
3. A volumetric vector node and object based multi-dimensional
operating system as recited in claim 1, further comprising, but not
limited to, the following core software engines: a. Sphere of
Influence: the container and volumetric calculation engine that
oversees all container specific data from the largest macro data
container perspective to the smallest container. This can also
include containers that cannot be represented visually as a pixel
based representation, but can be referenced as nano-containers. b.
Universe Engine: the database and object address specific system
that stores, manipulates and manages the vector "real estate"
aspect of the operating system and container. This includes
geo-spatial real world coordinates as they relate to real world,
third party geo-based platforms and augmented reality objects. This
engine manages linear and multi-dimensional timelines, along with
each user's core vector and any vector nodes created within the
operating container and how those vectors relate and interrelate
with each other. The methods of this engine allows for a
multi-dimensional data with forward and reverse time lookups and
manipulation, creating a forward and reverse spiral effect. c.
Immersive Corollary Library: the model oriented database array
management system that populates the operating container with
models and meta-data that form the tactile, or human interactive
objects that form the user interface. This library could connect
the operating container to multiple virtual and physical devices,
internet, extranet and any other storage or transportation of data
related entities. d. Data Visualization Engine: this is the system
that connects a specific data set or cluster of data sets into
organic looking particle effects and/or objects. This is also a
means to visualize cloud computing and organically create user
interfaces that can control cloud based data. This also shows the
computational information, or raw data, that forms any container.
e. Inter/Intra-Spatial Marketing and Product Engine: this is a
contextual object oriented system that injects, manages,
manipulates and provides user controlled advertising. This also
allows advertisers, administrators and customers a management
portal with access to the intra-spatial and inter-special
analytical values that determine the specific real-time value
snapshots of data that has been derived organically from the
connectivity of all other core engines.
4. A volumetric vector node and object based multi-dimensional
operating system as recited in claim 3a, wherein multiple
sub-control interfaces work together to form the Sphere of
Influence Engine: a. A visualization and/or multi-sensatory system
that translates the spatial relationship between two or more
virtual containers, worlds, communities, objects and/or data. b. A
sphere of control layer that specifically creates shielded or
protected areas with multi-axial three dimensional algorithms,
creating a container within a container, at which point single or
multiple vectors and/or pixels align based on the users input. This
is distinct to a virtual environment or interface. This includes
security protocols and manipulation of data, both organic and
sourced, for both ingest and push of data in and out of the
containers and/or communities within a container. c. A real-world
object based system that overlays a virtual object over a physical
object. This interface and engine can be used to create user
controlled and manipulated three-dimensional security systems that
bridge real-world objects and system, including but not limited to,
physical devices, virtual devices and/or software applications.
Users can customize any type of volumetric container, or
combination of containers, to create a distinct virtual to real
world lock combination. The system also derives real-world
coordinates through, but not limited to, global positioning
systems, compass, active and passive radio frequency, motion
capture, gyroscope, or any other current or future geo-positioning
system. The user interface can be accessed through, but not limited
to, any augmented reality, monitor, heads up display systems,
holographic technology, mobile device, optical or digital camera
system, or any other system which creates a new layer between the
viewer and the object being viewed. d. A container based protocol
dealing with the interaction between two or more Spheres of
Influence, and how their interactive states are calculated. These
states include, but are not limited to, a merge, reflect and
refract state of data containers. e. The structure of a user
container includes, but is not limited to, a; core vector point;
the secure core user container; the Terrene which represents a
visually solid container with surface; the Terrene surface which is
a mappable area in which communities and polygons are attached, and
can have sub-terrain communities, as well as unattached communities
that occupy the volume above the Terrene surface; the Sphere of
Influence which is the outermost container for each user.
5. A volumetric vector and node based multi-dimensional operating
system that re-draws current and future intranet, extranet,
internet and legacy network threads and data as a variety of
immersive tactile interfaces represented but not limited to,
planets, moons, galaxies, nebulas, and any form of a star, object
or energy that populates the known universe. This data, once
ingested into the operating container, may influence or be
influenced by other data or forces, creating a new data set,
trajectory and/velocity along both linear and multi-dimensional
timelines. Another influencing factor deals with communication
between containers and their path of data transmission, and how
that data is affected by and outside influencer.
6. A volumetric vector node and object based multi-dimensional
operating system as recited in claim 5, wherein each of these
object oriented tactile interfaces, or containers, can be redrawn,
re-skinned, remodeled and/or changed organically either by user
function, or organically generated function, of the system as a
whole or any part.
7. A volumetric vector node and object based multi-dimensional
operating system as recited in claim 5, further comprising
contextual based themes which are created from an aggregate of
related object and meta-data. An example would be field specific,
sports specific and/or industry specific data sets that relate to a
unified skinable theme.
8. A volumetric vector node and object based multi-dimensional
operating system with the process of data extraction that searches
web content, and any other internally or externally held or
available data, and parses the queried data through in initial
"ingest" filter that then "sanitizes" the data so that only the
useful data threads are then passed through to the immersive
corollary library.
9. A volumetric vector node and object based multi-dimensional
operating system with methods of creating an immersive social
universe through users having their own vector, container planet or
system that is based on distinct XYZ nodes or address. This creates
methods to calculate, create, manage, manipulate, own and/or lease,
rent, subscribe and have "power of attorney" control over
volumetric and vector based real-estate.
10. A volumetric vector node and object based multi-dimensional
operating system as recited in claim 9, wherein the method for
calculating a specific distance to a specified destination,
includes, but not limited to, the following rules: a. The absolute
center of the entire operating system is represented the vector
point (0,0,0,0) PRIME. b. A user based container is represented as
(0,0,0,0,0) or (XYZTp) where XYZ represent the vector position, (T)
represents the time signature of that vector or position, and (p)
represents the dimensional plane that the vector exists on. c. When
the operating container is visually drawn as the known universe,
the scale between the actual distance of terrestrial bodies, from
the absolute center of the Milky Way, and the exponentially smaller
scale of the immersive operating system, are always measured in
equal percentages, regardless of how much future volumetric space
is created or filled. For instance, if the future ever expanding
master container which holds the entire volumetric operating
system, it will, creating a new area of volumetric space, but the
distance from one existing vector address to another stays the
same. d. Any type of social, communal, business, personal and/or
organically generated operating system that uses stellar
coordinates by means of extracting and then assigning XYZ
coordinates for the purpose of creating a new central starting
point at which a new virtual social community, container, vector
node or virtual universe is built. e. Sub-communities within a
user's container, or Sphere of Influence, can communicate and
transfer data directly, indirectly or organically between
communities, objects or other containers. Any object, container or
community can have its own Sphere of Influence with dual or
multi-directional security features which are defined by the entity
which manages the container's security protocols.
11. A volumetric vector and node based multi-dimensional operating
system that creates a multi-directional secure peer-to-peer, and/or
unlimited multi-peer, transmission of data which is represented
visually as a transport mechanism, creating actual travel time to a
destination based on the data being exchanged through the
peer-to-peer, and/or multi-peer, connection.
12. A volumetric vector node and object based multi-dimensional
operating system as recited in claim 11, wherein the form of
transportation is rendered in three-dimensional space as through a
combination of computer generated software render engines,
including, but not limited to: a. particle emitters b. object
deformation c. object surface mapping d. immersive corollary
library
13. A volumetric vector node and object based multi-dimensional
operating system as recited in claim 11, further defining the form
of transportation which is visually drawn in three-dimensional, or
multi-dimensional, space through, but not limited to, the following
means: a. virtual warm-holes, or "warp-drive" like transit systems
that vary visually based on theme, data or content b. spacecraft c.
airplane d. roadway e. highway f. expressway g. toll bridge or
gateway h. tunnel i. train j. tram k. monorail l. boat/ship m. Any
other means of transportation that is virtual or physical, which is
currently known, or developed in the future.
14. A volumetric vector node and object based multi-dimensional
operating system as recited in claim 13, wherein advertisers can
use the following, but limited to, mechanisms to market and/or
compensate for the data: a. Wrapping a virtual and/or physical
model b. Creating virtual and/or physical billboards that the users
can virtually or physically pass when in transit to another
location or destination. c. Animated models which represent a
virtual and/or physical product. d. An entire universe and/or
container theme based on an advertised product, where the look and
feel of the environment changes. e. Changing the physics of the
environment or models, both virtually and physically, based on
available choices to advertisers. f. Creating branded containers
which include, but is not limited to, planetary or immersive social
systems and communities g. Purchase contextual specific search
terms and models by which they are included in the "redraw" or
"reskin" of virtual, and/or physical, user interface, or are
brought up with contextual meta-data that relates to the search
itself.
15. A volumetric vector and node based multi-dimensional operating
system whereas buildings or objects are either tethered to a
sphere/planet surface, extends into the volumetric space controlled
by the Spheres of Influence, and/or sub-surfaces which, in turn,
creates immersive data clusters.
16. A volumetric vector node and object based multi-dimensional
operating system as recited in claim 15, wherein each immersive
data cluster is defined with a minimum of four (4) vector points.
The four (4) points creates the simplest form of a container, or
rigid container, creating a volumetric container, all with one
central connecting data point, or the core vector of that data
cluster. Each axial vector point may move based on user input or
organic transitions that occur with spatial data shifts, thus
creating ripples of volumetric information. This data is tracked as
volumetric vector data, giving real-time, historic and/projected
immersive analytic data that reflects what has happened, is
happening, will happen or can happen.
17. A volumetric vector node and object based multi-dimensional
operating system as recited in claim 15, further ingesting user
generated data from any input device including, but not limited to,
motion or gesture control, global positioning systems (GPS), local
positioning systems, optical capture, augmented reality control,
current and future geo-locating services, tactile control surface
or any other type of input device. The data is then connected to
the vector node location, which can be where organic data is
ingested into the data containers. These containers then have a
trajectory and velocity based on the initial course the ingest
filter sets it on. When larger data clusters collide with smaller
ones, the two clusters combine, partially absorb data and move on,
based on pre-determined data flow characteristics, or completely
pass through one another with no effect on the other. If a data
cluster has a larger cubic volumetric data mass, and has data that
is set to collide and link, then the smaller cluster is absorbed
and a new data set is created. This data set then relates back to
the information ingested from the input device.
18. A volumetric vector node and object based multi-dimensional
operating system wherein the architecture, and/or process and
fundamental connecting data thread is broken down in, but not
limited to, the following manner: a. Contextual data orbit
entanglement: is a means by which data clusters in transit, which
are held within a container, have surface data which has three, or
more, total states, which can include, but is not limited to
active, inactive, pre-reactive, post-reactive and/or historical
states or processes in which preceding data points rotate in an
orbital pattern around the neutral state, which may be in any form
of activity listed above. This can be the actual data information
area of visualization. The post-reactive state, which orbits around
the main data cluster in the polar opposite side of the data
cluster, hold data connections that can and/or will happen. The
pre-reactive and post-reactive data links are what actually get
entangled and passes on short bursts of meta-data, letting the
other data cluster know quickly and simply if there are any
compatibilities between the data and/or vector based data clusters.
b. The "skin" of the data container, which is made up of the
contextual data orbit layers or Spheres of Influence, forma a
virtual shell around the data that is in transit. This not only
allows the container to be drawn as a polygon and vector based
multi-dimensional model, but also allows this data to be
permanently, temporarily and/or time specifically moved along with
the container.
19. A volumetric vector node and object based multi-dimensional
operating system wherein a three-dimensional legacy control system
creates a macro and sub-macro (automated) control standardization.
This system will control any preexisting operating system, method
to input and control operating systems, macros of commands and
controls for any preexisting operating system or software, and
standardizes the controls across all preexisting operating systems
based on connecting the commands to the immersive corollary library
which is redrawn as a three-dimensional interface.
20. A volumetric vector node and object based multi-dimensional
operating system wherein vector based containers not only have
orbits to other containers, the master operating container and/or
any other representation of data within the operating container,
but also have intra-spatial rotation which can have unique spin
rates, directions and velocity along with the trajectory of the
vector data which can evolve. This includes intra-container shifts,
clustering or repulsion of data clusters based on the data
formations inside the container.
21. A volumetric vector node and object based multi-dimensional
operating system wherein the Immersive Corollary Library may create
a tethering process which initially has, but is not limited to, two
types of connections: a. Pure Tether which is a one-to-one
relationship of meta-data to a polygon model. b. A Cluster Tether
which is the linking of meta-data from one or more sources to
multiple versions of polygons.
22. A volumetric vector node and object based multi-dimensional
operating system as recited in claim 21, wherein the tethering
process can be replaced by: a. Sub-Terrene tethering, which is any
tethering to objects or containers that occur below the Terrene
surface. b. Sub-Sphere of Influence tethering, which creates a
tether to any object that is not directly attached to the Terrene
surface, but still exists with the Sphere of Influence.
23. A volumetric vector node and object based multi-dimensional
operating system as recited in claim 21, further creates a tethered
hierarchical connection between, but not limited to, containers and
external addressing systems, such as URLs, virtual addresses, IP
addresses and physical real-world addresses. This allows for a
grouping of communities and containers, as well as objects
connected to a specific addresses, to query the Immersive Corollary
Library and populate a user's container with objects and
information. Specific domain names also have a direct relationship,
through the tethering process, to various and/or specific
communities with the operating container. Users can modify,
influence and communicate with external addresses, subscriptions,
memberships, blogs, data syndications or any other external
community cluster all from within their container.
Description
PRIOR APPLICATIONS
[0001] This application claims priority from Provisional
Application Ser. No. 61/814,177, filed Apr. 19, 2013.
BACKGROUND OF THE INVENTION
[0002] As data usage grows, and users have a myriad of ways to
control and visualize their data, including social networking,
video games and educational or other such environments, there is no
single method to consolidate data into a tactile graphical
interface which not only connects their data but connects their
relationships to each other. There are millions of applications,
programs, websites, search engines, social communities and other
related and unrelated technologies, applications, platforms and
content that are currently disparate and the only overall
connection between them is when a user manually makes a connection
via search engines or other form of social connection. With the
advancement of mobile technology and wireless data exchanges, there
is no one single point-of-entry to access all of this information
in a tactile, immersive social environment.
BRIEF SUMMARY OF THE INVENTION
[0003] In a preferred embodiment, the invention includes an overall
virtual universal container known as the master volumetric
operating container, or "SoftSpace," that sets the finite end
points, which can infinitely expand, at which virtual and visual
representations of data cannot move beyond. This immersive virtual
operating system, or operating container, ingests data from any
existing source (for example web, intranet, extranet, local,
remote, or any other form of data communication and exchange)
through an immersive corollary database that makes a one-to-one
connection between the object or meta-data as it exists in its
current incarnation, and links it to a vector based
three-dimensional model or models that correlate to the type of
object being represented.
BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWING
[0004] FIG. 1 Diagram describing the absolute volumetric operating
container as it exists within a present timeline.
[0005] FIG. 2 Flowchart diagram of the Core Software Engines: 1)
Sphere of Influence, 2) Universe Engine, 3) Immersive Corollary
Library, 4) Data Visualization Engine and the 5)
Inter/Intra-Spatial Marketing and Product Engine.
[0006] FIG. 3 is a diagram of a basic container utilizing the
Sphere of Influence engine.
[0007] FIG. 4 is a deeper nested view of how the Sphere of
Influence container is calculated from a macro to micro
perspective.
[0008] FIG. 5 Illustration of a typical user's volumetric container
including visual representation of a user's Core Vector, Core and
Node.
[0009] FIG. 6 Illustration of user's node and Sphere of Influence
volume calculations.
[0010] FIG. 7 Diagram of the Sphere of Influence container security
protocols as they relate to a parent container.
[0011] FIG. 8 Diagram of the Sphere of Influence container security
protocols as they relate to the Operating Container.
[0012] FIG. 9 Examples of the interaction between two or more
users' Sphere of Influence security protocols and the acceptance or
denial of data between any user's containers.
[0013] FIG. 10 Diagram of interaction between outside data,
including advertising, and how users can control the permeation of
information layer by layer.
[0014] FIG. 11 Diagram of container data states as they relate to
the combined state of two or more volumetric data containers.
[0015] FIG. 12 Diagram of container relationships via Vector Node
addressing on both a linear present timeline and multi-dimensional
timeline shift.
[0016] FIG. 13 Macro diagram of Universe Engine with distinct
Vector Based Addressing System based on absolute center of
(0,0,0,0) PRIME.
[0017] FIG. 14 Diagram of Parent/Child relationship between Vector
Nodes and Sphere of Influence creating a distinct meta-data wrapper
for each vector node address.
[0018] FIG. 15 Diagram of vector data with event triggers within a
single linear timeline.
[0019] FIG. 16 Diagram of Vector and Pixel Movement influenced by
other forces of data in X, Y and Z space.
[0020] FIG. 17 Diagram of usage of intersecting vector data and the
creation of new vector data and corresponding volumetric
containers.
[0021] FIG. 18 Diagram of multi-dimensional vector data with time
spirals.
[0022] FIG. 19 Diagram and calculations for inter-vector nodes
between two (2) or more containers on the same dimensional
plane.
[0023] FIG. 20 Diagram and calculations for inter-vector nodes
between two (2) or more containers on different dimensional
planes.
[0024] FIG. 21 Structure diagram of a user's typical container.
[0025] FIG. 22 Diagram of rigid containers.
[0026] FIG. 23 Diagram of rigid container relationship to Terrene
surface with clustering as communities when mapped against sphere
or container.
[0027] FIG. 24 Illustration of Terrene surface social communities
and synergistic data relationships between those communities in
both a linear timeline and multi-dimensional timeline.
[0028] FIG. 25 Illustration of intra-community data represented as
particle systems.
[0029] FIG. 26 Illustration of Sphere of Influence example when
enclosing a polygon based social community and the sub-surface
relationship to any connected rigid containers.
[0030] FIG. 27 Diagram showing threaded or "tethered" connections
through the Immersive Corollary Library engine.
[0031] FIG. 28 Diagram showing pure-tethers and cluster-tethers and
how that data is parsed through Immersive Corollary Library
(ICL).
[0032] FIG. 29 Diagram showing the connection between user's core
vectors, nodes and containers with tethered web URLs.
[0033] FIG. 30 Illustration showing the view of two respective
users' nodes and their distinct vector address.
[0034] FIG. 31 Diagram showing point-to-point methods of
transportation.
[0035] FIG. 32 Illustration example showing various advertising
embodiments during transportation.
DETAILED DESCRIPTION OF THE INVENTION
[0036] The inventive subject matter provides a means to dynamically
re-draw current and future intranet, extranet, internet, legacy
network or any other threads and data into an immersive tactile
user interface, or volumetric operating system, which can also be
represented in a number of visual formats. The master architecture
of this system, or Volumetric Operating Container, as referenced in
FIG. 1, describes the absolute container (100) which is the
outermost constantly expanding barrier in which all data is
visualized. At the absolute center of the volumetric operating
container is the Prime Vector (101), which is always represented as
an XYZ coordinate with a time (T) signature variable: [0037] (XYZT)
or (0,0,0,0) PRIME
[0038] This vector is the same on all multi-dimensional timelines.
This creates the starting point for a distinct volumetric
addressing system where three (3) coordinates and a time signature
create the address. Since the operating environment can span across
multiple visual and computed dimensions, the PRIME address always
stays the same.
[0039] FIG. 1 represents an initial dimension, or plane, where a
single layer (102) represents a simple linear time sequence of data
events. Any unused, or null (103) data is held as possible future
volumetric space to be utilized.
[0040] Initially there are five core software engines that work in
unison to form the architecture of this operating system as
referenced in FIG. 2. For example: Sphere of Influence (soi) (201),
Universe Engine (202), Immersive Corollary Library (ICL) (203),
Data Visualization Engine and the (204) Inter/Intra-Spatial
Marketing and Product Engine (205). The Volumetric Operating
Container (206) is the combined software apparatus that binds the
software engines into a unified operating system.
[0041] Much like the Volumetric Operating Container, users can
obtain an XYZ coordinate, or address, with a specific volumetric
area around their core vector (CV) known as the Sphere of
Influence. These addresses can be obtained by various methods
including, but not limited to leasing, renting, registering,
purchasing, subscribing or inheriting. FIG. 3 outlines the simplest
structure of a user's container where the Outer Sphere of Influence
(300) represents the outermost structure that holds a user's
volumetric information. This volume can be expanded based on how
much virtual space each user obtains. At the absolute center of
each user's container is the Core Vector (301), which is a distinct
address identifier. Distance (302) from a user's Core Vector (CV)
to the Outer Sphere of Influence is calculated using the three
dimensional Euclidean distance equation:
d(p,q,)= {square root over
((p.sub.1-q.sub.1).sup.2+(p.sub.2-q.sub.2).sup.2+(p.sub.3-q.sub.3).sup.2)-
}
[0042] Each distinct vector address will include additional meta
data that creates a distinct address which only that destination
will have, identified with an XYZ address where the distance to
that vector from (0,0,0,0) PRIME is calculated by: [0043] d(p,q,)=
{square root over
((p.sub.1-q.sub.1).sup.2+(p.sub.2-q.sub.2).sup.2+(p.sub.3-q.sub.3).sup.2)-
}, where "p" represents (0,0,0,0) PRIME and "q" represents a user's
Core Vector.
[0044] Multiple Spheres of Influence can exist within a user's
container. Referencing FIG. 4, Spheres of Influence nest within
each other creating a multi-layer, multi-directional hierarchical
management system which is visually implemented through spheres
and/or polygon based containers. From a data and visual control
perspective, The Outer Sphere of Influence (401) is the outermost
control layer in which user has absolute control over the
volumetric content or information within this container. The Inner
Sphere of Influence (402) is the closest in distance to the user's
Core Vector. Between these two containers are the Interim Spheres
of Influence (403) which represent all additional containers that
exist between the outer and inner spheres. Distance from a Core
Vector (404) to the surface of any Sphere of influence uses the
Euclidean distance equation as is calculated as follows: [0045]
d(p,q,)= {square root over
((p.sub.1-q.sub.1).sup.2+(p.sub.2-q.sub.2).sup.2+(p.sub.3-q.sub.3).sup.2)-
}, where "p" represents the Core Vector and "q" represents any
Interim Sphere of Influence.
[0046] FIG. 5 illustrates the visual implementation of a typical
user's volumetric container where there is an absolute center, or
Core Vector (501). From center outward, the first container is the
core (502), the most secure container which is used as a personal
data storage mechanism. The Terrene (503) is the primary physical
container which is visually represented as a solid surface. The
Terrene Surface (504) is the primary mapping surface in which a
user can place polygons or other data that is represented as
three-dimensional models. The Sphere of Influence (505) is the
outer visual container.
[0047] Since each user's container occupies a specific amount of
volumetric space, FIG. 6 illustrates calculations for the following
containers: [0048] Core Volume (601): (CV)=4/3.pi.r.sup.3 [0049]
Terrene Volume (602): (TV)=4/3.pi.r.sup.3-(CV)4/3.pi.r.sup.3 which
represents a boolean value [0050] Sphere of Influence Volume (603)
(soiV)=4/3.pi.r.sup.3-((TV)4/3.pi.r.sup.3-(CV)4/3.pi.r.sup.3) where
both (TV) and (CV) create a boolean expression from the (soiV)
volume
[0051] Each container or layer has distinct security filters and
protocols as they relate to a specific user or user's container.
Users have control over data or objects that permeate any of their
containers, or spheres, by enabling, disabling or adjusting
security protocols for each layer. FIG. 7 illustrates a
semi-spherical cross section showing different security layers,
where the path of data (701) begins outside of the containers and
then moves inward towards the Core Vector (CV). The outer security
layer (702) represents the outermost barrier for data to enter the
Sphere of Influence (soi). The interim sphere's security layers
(703) can have multiple values allowing some information to pass
through while disallowing specific data to pass. The Terrene
security layer (704) allows or denies any objects to be embedded on
the Terrene surface, which includes any advertising or outside
polygon models that are not sourced directly through the user. The
core security layer (705) is the most secure area of all of the
containers, holding sensitive or critical user data. For example:
credit card numbers, bank information, passwords and any other
sensitive data.
[0052] User containers, centered on a distinct Core Vector (CV),
inherit the operating container's security protocols outside of the
user's Sphere of Influence (soi). FIG. 8 illustrates the
relationship between the operating container (801) and the user's
container (803), as well as the operating containers security
protocols (802) which take priority over all security protocols
outside of a user's Sphere of Influence (soi).
[0053] Interaction between two (2) user's Spheres of Influence, as
illustrated in FIG. 9, can have an orbiting relationship (901)
where there is no physical collision or interactivity between the
containers. When container do intersect (902), pre-set security
protocols, as defined by user, determine how much data is accepted
or denied. In this example, user A can set their containers to
restrict encroachment of user B (903). When allowed, a combined
container (904) is created with mixed data from both users. In the
case of hierarchical control where a specific user, say a parent,
wants to limit and set security protocols for their child, they can
do this via nesting security controls within their container, or
creating a new managed security container whenever warranted.
[0054] Outside data, meaning any data that is not inherently
contained or protected within a user's Sphere of Influence (soi),
may include advertising and other forms of information that attempt
to permeate a user's container layer by layer. FIG. 10 illustrates
user controls over data that is sourced outside of their Sphere of
Influence (soi), and how advertising and products are allowed to
visually be shown and interact with user's data. Products,
advertising and services (1001) can only permeate the layers that a
user has allowed them to. Once within the sphere, outside data is
connected to a set of three-dimensional polygon models which are
visually drawn to screen. Users can allow specific products or
companies to permeate specific layers (1002). Outside data is also
given security protocols based upon what the individual wants. For
instance, a user may wish to prohibit specific advertising of
products, while at the same time, allowing data such as home
security, to permeate all the way into their core.
[0055] Multiple data states can be created depending on how two or
more containers interact. These containers can include data sources
that were generated through the operating container or through user
containers. As illustrated in FIG. 11, the combined state of data
is consistent through the entire operating container, and can
include a user's Sphere of Influence, data spheres/containers,
product data or polygons and any other volumetric container. The
merge state (1101) is where data from two or more containers
(1101.sub.1) merge, creating a new data container (1101.sub.2). An
example would be a data container of genealogy would be accepted,
in its entirety, into a person's personal container. The reflect
state (1102) is where data from two or more containers (1102.sub.1)
reflect off each other, creating a new data trajectory
(1102.sub.2). An example would be preventing specific restricted
content types from entering your child's container. The refract
state (1103) is where data from two or more containers (1103.sub.1)
partially merge, creating a new larger data container (1103.sub.2)
and a smaller residual data container (1103.sub.3) from information
that is not absorbed into the larger container. An example would be
a community data container for racecar fans and a container with
data of their favorite driver. The new larger container
(1103.sub.2) would create a more focused community of information
on the sport and the driver. Whereas the smaller residual container
(1103.sub.3) would carry any unwanted data away.
[0056] Data containers, and the visual representation of data as
three-dimensional polygons, can exist on both linear and
multi-dimensional timelines. This allows users to have multiple
sensatory representations or experiences of their data, including
visual, aural, tactile, smell and taste and any other sensatory
functions that may be discovered. FIG. 12 illustrates container
relationships and addressing on both a present linear timeline and
a multi-dimensional timeline. Either a user's core vector or vector
node (vN)(1201), which is a distinct address at the core of all
non-user containers, can have different values based on their
position both in time and space. The relationship of (0,0,0,0)
PRIME (1202), or prime vector, to the entire data container, or
vector node (vN), can change based on different states of the data
or position of the vector (1204). For example, the relationship
between the Earth and the sun over a period of time. The address
identifier string changes its time variable based on the
relationship to the container's initial position: [0057] Vector
Node Position (1205.sub.1)=(vN).sub.1(XYZTp).sub.1 with multiple
states on a single timeline where the properties of the (vN) change
with time (1205.sub.2, 1205.sub.3 and 1205.sub.4).
[0058] Containers can exist in multiple states where the XYZ
position and address is always consistent, and the planar (p), or
dimensional, view has changed. (1206.sub.1) and (1206.sub.2) show a
changed (vN) planar state to where the container exists on both a
secondary and tertiary plane: [0059] Plane 2
(1206.sub.1)=(vN).sub.1(XYZTp).sub.2, Plane 3
(1206.sub.2)=(vN).sub.1(XYZTp).sub.3
[0060] A user's core vector cannot change its position once it has
been addressed, unless the core vector is intentionally
re-positioned.
[0061] FIG. 13 illustrates the Universe Engine, which is the vector
based addressing system which manages all data points within the
operating container. (0,0,0,0) PRIME (1301) is the absolute center
of the operating container. This position of this central vector is
identical across all planar (p) or multi-dimensional views. The
distance calculation (1302) uses the three dimensional Euclidean
distance equation, d(p,q,)= {square root over
((p.sub.1-q.sub.1).sup.2+(p.sub.2-q.sub.2).sup.2+(p.sub.3-q.sub-
.3).sup.2)}, where (p) is (0,0,0,0) PRIME and (q) is the core
vector (1303) of a user or data container. Each core vector (CV),
within the operating container, is always the hierarchical parent
to all attached containers, or Spheres of Influence, when dealing
with addressing or movement of data. Null space (1304) is defined
as any unused volumetric data space outside of any user or data
container.
[0062] Vector nodes (vN), as illustrated in FIG. 14, show the
(vN)(1401) as having a child hierarchical relationship to the Core
Vector (CV) (1402). Users may have multiple vector nodes (vN)
within their Sphere of Influence (soi). Multiple vector nodes (vN)
are represented as: [0063] (vN).sub.1, (vN).sub.2, (vN).sub.3,
(vN).sub.4, . . .
[0064] Vector nodes (vN) can have either a direct node connection
(1403), in which the data path or linking of (vN) is direct to the
core vector (CV), or a secondary node connection (1404), in which
the data path or linking is between two vector nodes. These would
be represented as (vN).sub.1 and (vN).sub.2. All distances between
any (CV) and (vN) are calculated using the same Euclidean
equation:
d(p,q,)= {square root over
((p.sub.1-q.sub.1).sup.2+(p.sub.2-q.sub.2).sup.2+(p.sub.3-q.sub.3).sup.2)-
}.
[0065] Data movement, within a single dimensional timeline, can be
visually represented at different vectors points depending on event
triggers that can shift data from one position to another. All
vector nodes (vN) that have a migratory path, or any other
representations of vector and/or addressing data within the
operating container follow the parameters as set forth in FIG. 15.
Data sets will always have an initial vector data position (1501).
Once a data set begins movement, it starts an array of trans-events
(1502) where vector data migrates and from one point in time to
another, and one point in space to another, while staying on the
same dimensional plane. These vectors are directly connected to
pixel data, or a visual pixel, and are represented as transition
pixels (tp). The alternate position of the data and/or pixel is
represented as (AP). Together (tpAP) represents the transitional
identifier vector data as it relates to visual pixels. (1503)
represents the alternative data position as it relates to the
initial vector data point. When dealing with multi-dimensional or
multi-spatial migrating data sets, (1504) illustrates a transecting
data set sourced from another path. While these examples represent
pixels and visuals, the data movement can also represent any
sensatory data.
[0066] Vector and pixel movement, within a single dimensional
timeline, can be influenced by forces of data in the X, Y and Z
space. FIG. 16 illustrates vector data, as visually represented by
a pixel, as having inherent states of movement, including velocity
and trajectory. These states can be influenced by outside data,
creating new alternative vector data paths. From the initial vector
point (1601) to the vector in movement state (1602), outside data
forces (1603) can shift the intended path to have a more organic
movement that can be visually represented as pixel data. An example
would be a data container holding a specific feature film where the
outside data forces could be containers of critic's reviews.
[0067] Vectors and data sets that have migrating paths may
intersect as illustrated in FIG. 17. The intersection of vectors
(1701) pertaining to information, conversations or relay of data
between three or more users creates a new vector node (vN) with a
distinct address and tracking data (1701). Data outside of this
information, conversation or relay of data from another user or
source on a different path, can create another distinct vector node
(vN)(1702). An example would be three (3) users having a
conversation about a medical procedure and a forth (4.sup.th) user
conversation separate from the current conversation, is searching
for information about a naturopathic solution.
[0068] Within the Operating Container, vector data not only has
states of motion, but also multi-dimensional time states for both
forward and reverse data. This system uses time lookup tables,
allowing data and vectors to jump from one dimensional state to
another, as well as from one time to another with different
trajectory and velocity. FIG. 18 illustrates the concept of a time
spiral effect from future and past vector points as they relate to
multi-dimensions, and how that data is drawn through multiple
planes. When starting with actual space and time (1801), data can
migrate dimensionally by way of changing the data from the past to
represent a new future timeline (1802). This is accomplished
through reverse time lookups (1803) which begins a data loop where
meta-data is tracked and rendered to screen in a new plane or
dimensional view. This means that if the past time, as it relates
to data, is changed, then a new alternative timeline is created, in
essence creating a new dimensional view as well. For example, if a
user, within virtual space, wants to go back in data history and
discovers and inefficiency in a process, they can alter the data at
that point in time, which would create a new timeline.
[0069] When two (2) or more containers communicate or transfer data
on the same dimensional plane, an inter-vector node (iVN) is
created. As illustrated in FIG. 19, the calculation to determine
the vector address position (1902), as it relates to both the PRIME
vector (1901) and two containers (A & C) is: [0070]
Inter-vector Node (iVN)=A(XYZTp).sub.1.andgate.C(XYZTp).sub.1
[0071] The calculation for inter-vector nodes between multiple
containers is: [0072] Inter-vector Node
(iVN)=A(XYZTp).sub.1.andgate.B(XYZTp).sub.1.andgate.C(XYZTp).sub.1
[0073] When two (2) or more containers communicate or transfer data
on different dimensional planes, an inter-dimensional vector node
(idVN) is created. FIG. 20 illustrates the connections and
calculations to create an unique address identifier across multiple
planes as it relates to the PRIME vector (2001). Where the (idVN)
between containers A & C can be calculated as follows: [0074]
Inter-dimensional Vector Node
(idVN)=A(XYZTp).sub.1.andgate.C(XYZTp).sub.3 [0075] Calculation of
the (idVN) between multiple containers (A, B & C) can be
calculated as follows:
[0075]
(idVN)=A(XYZTp).sub.1.andgate.B(XYZTp).sub.2.andgate.C(XYZTp).sub-
.3
[0076] The structure of a typical user container, as illustrated in
FIG. 21, always has an absolute center point, or core vector (CV)
(2101). The core (2102) is the most central and secure user data
container. The Terrene (2103) is the user container that is
typically represented as visually solid surface. The Terrene
surface (2104) is the mappable area in which communities and
polygons are attached, which may include object anchored but not
attached to the surface. Users can also build sub-Terrene
structures, at least to the outer extent of the core, communities
or polygon based objects. The outer Sphere of Influence (2105) is
the outermost point at which a user's data is held and/or visually
represented, and can include any objects not anchored to the
Terrene surface. And the community (2106) which is the surface
level grouping of polygons that form social, business and data
related communities.
[0077] Within each Terrene container are multiple rigid containers
as illustrated in FIG. 22. Each rigid container always has a link
to the user's core vector (CV), along with a minimum of three (3)
additional surface vectors to form a simple volumetric container
(2201). Surface containers can also have additional surface points
which create more complex surface structures (2202).
[0078] Rigid containers are used to track and hold volumetric data,
in a simpler form, as it relates to the Terrene surface and user
generated communities. Surface level content, and or communities,
can either stay in a specific position (2301) or shift along the
surface (2302). For example video gamers can create one community
where they meet up to strategize, and create another game community
which tracks their exploits of the game. The second community would
move as they progress through the game.
[0079] Data can be synergistically exchanged between communities.
Users can populate their Terrene surface with as many communities
or polygon objects that will fit within the surface area and
volumetric space with the Sphere of Influence (soi) as illustrated
in FIG. 24. Meta-data information is exchanged between the
communities, creating data bridges or pertinent information that is
contextual to both, or multiple, communities and objects.
Inter-community data exchange (2401) occurs when two communities
exchange data on the same dimensional plane. Inter-object data
exchange (2402) occurs when two objects exchange data on the same
dimensional plane. Inter-dimensional community data exchange (2403)
occurs when two communities exchange data on different dimensional
planes. Inter-dimensional object data exchange (2404) occurs when
two objects exchange data on different dimensional planes.
[0080] Data can also be synergistically exchanged from within a
community or Sphere of Influence (soi). This data can be visually
represented as a particle system or other methods of visually
representing complex data arrays. FIG. 25 illustrates how data can
be visually represented by particle emitters, and how the frequency
and intensity of that data can change the particle type from one
element to another (i.e. from fire to water). Single particle
emitters (2501) can be attached to any parent polygon or object so
that the relevant particle system surrounds the data it represents.
Data can also be represented as multiple particle emitters (2502)
for more complex data sets. For example, an array of servers
creating a cloud computing environment can be visually represented
as clouds surrounding structures that represent contextual
data.
[0081] Each community, and/or object, has a Sphere of Influence
(soi) which encloses the polygon based communities. FIG. 26
illustrates the relationship of a community based Sphere of
Influence (soi) (2601) to the core vector (CV), and how the (soi)
inherits axial pivoting from the (CV) (2602) and also creates
another security barrier. Intra-object security can be placed on a
floor-by-floor and room-by-room basis. For example a user can give
the penthouse of a specific building distinct security protocols,
while the remaining building may be open to the public.
[0082] The corollary data that populates both the entire operating
container is ingested and managed by a dynamic immersive corollary
database called the Immersive Corollary Library (ICL). This unique
master database and library creates a permanent link, or tether,
between a three-dimensional object and a grouping of data,
including; images, video, audio, code and real world data (global
positioning systems, local positioning systems, motion capture
data, tactile interfaces, gesture control). FIG. 27 illustrates the
bridge (2702) between the web as it exists today (2701), gaming
consoles and any type of immersive social environment or user
interface that requires the translation of flat two-dimensional
data into three-dimensional models (2703). Data can be extracted
from a URLs, php, ajax, JSON, database or any other current or
future source of data. Modeled data can be used to populate
volumetric containers, communities or any other usage, including
devices, of polygon models that have a direct tether to web
data.
[0083] The tethering process, handled through the Immersive
Corollary Library (ICL) has two types of connections as illustrated
in FIG. 28. A Pure Tether (2801) is a one-to-one relationship of
meta-data to a polygon model. A Cluster Tether (2802) is the
linking of meta-data from one or more sources to multiple versions
of polygons.
[0084] Each model or grouping of models has unique meta-data
identifiers that create quick exchanges of data between two objects
that are within certain proximity of each other, or that are being
queried by the immersive search engine. These can be held within a
community, any container, a hybrid link between a tethered URL, or
any other addressing system, and object, or any other form of
direct or indirect bridging between databases or libraries.
[0085] Web URLs have a distinct tether hierarchy as illustrated in
FIG. 29. The Immersive Corollary Library (ICL) handles the
tethering of URL directories, or any other addressing system, and
content with vectors, containers and polygon objects. (2901)
represents a grouping or community of containers and objects
connected to a URL, any other addressing system or domain (2902).
(2903) represents a domain name to vector node (vN) tether. (2904)
represents a sub-directory to Sphere of Influence (soi) tether.
(2905) represents a content directory to secondary Sphere of
Influence (soi) tether. (2906) represents image or content
meta-data to polygon model tether.
[0086] FIG. 30 illustrates the view of two respective user
containers and their distinct vector addresses. Where (3001)
represents user A's container and (3002) represents that user's
core vector (CV). And (3003) represents user B's container with
(3004) being that user's core vector (CV).
[0087] Within the volumetric operating container, on both single
dimensional and multi-dimensional planes, there is are methods of
transportation which visually, as well as multi-sensatory,
represent point-to-point data transfers and communication. FIG. 31
describes transportation between two points, including container,
communities, vector nodes (vN) and any other vector point(s). The
visual, and/or sensatory, representations of transportation can
either be viewed as first-person or third-person transit. (3101)
and (3103) represent two distinct user containers and (3102)
represents specific modes of transportation.
[0088] Since transportation and data not only becomes a journey for
the user, but an immersive experience, advertising, and or
sensatory experiences, can be implemented during the data transfer
time between peers. FIG. 32 illustrates examples of transportation
with advertising, but not limited to, space environment (3201),
atmospheric environment (3202), community or ground environment
(3203) and water environment (3204).
[0089] A proprietary immersive search engine allows users to input
search queries by text input, a combination of gesture controls, or
model based search, or any other type of sensatory interactivity,
which is used by combining models to form a meta-data snapshot or a
three-dimensional model depth based search to where any objects
that are placed in the foreground take precedence over objects that
are placed in the background, creating a unified search based on
the type of models and their contextual meta-data, as well as their
spatial relationship to each other. Search parameters may also
include, but not limited to, time, velocity, trajectory and
texture. The search results are either represented as highlighted
objects or nodes within the backdrop of the universe, a remodeling
of the core planet to show the results as three-dimensional model
data, text and object descriptors are drawn in the volume of space
around the planet, or objects and data are overlaid against any
augmented reality viewport or display that allows the operating
system to place virtual objects with geospatial data against
real-world objects. The immersive search engine will recognize
trends and suggest buildings, objects, both visual and implied, or
sponsors that can either populate the user's container or augment
the search information through paid sponsorship, memberships or
other value-add products. All controlled by the user's sphere of
influence preferences and how they allow sponsors to permeate each
layer of their security protocol.
[0090] Any data that is visualized within this operating system
will be part of an immersive analytical system, that uses custom
algorithms that calculate the velocity of a moving vector within
any container or immersive environment, and how that velocity
correlates to the sphere of influence and other vectors. A value is
placed on the aggregate velocity of any bound data sets so that an
analytical figure can be calculated to represent the intrinsic real
world monetary value of the movement of the vector and anything
attached to it. This creates a means to advertise, and or
communicate with a user, based on organic data as well as user
sphere of influence preferences.
[0091] The more a person communicates with another, the more data
that is exchanged or contextual, the closer in proximity that other
object or user's container will appear, as if organizing into a
community of containers. This same set of boundary identifiers
allows users from the core-out management view to choose how many
spheres of influence they want, what the security protocols are for
each sphere, what data is allowed to permeate which sphere and
when, and what users are allowed to access specific data, objects
or communities. This security protocol also allows users to block
other users from encroaching on a specific neighborhood of spheres.
Once two or more spheres have begun to overlap, a new organic
volumetric data container is birthed. Through the combined
aggregate of all containers within the operating system, a spatial
volumetric cost-per-pixel algorithm calculates the actual volume of
three-dimensional pixel space surrounding a specific community or
property, which is then calculated and a dollar figure is given to
that real-estate or asset.
[0092] The volumetric operating system is cross-platform, and can
include, but not limited to pc, mobile, tablet, gaming console, and
all other current and future devices, so that applications and data
can be synced across a wide array of technology and distribution
modes, as well as giving the user a single unified visually
immersive experience.
[0093] The Data Visualization Engine is a raw data view of the
information held within the operating container. This can include,
but not limited to, algorithms, equations, vector data, polygon
data any and any other visual representation of data or math.
[0094] The Inter/Intra-Spatial Marketing and Product Engine is a
contextual object oriented system that injects advertisers and
manages the intra-spatial and inter-special analytical values that
determine the specific real-time value snapshots of data that has
been derived organically from the connectivity of all other core
engines. This engine bridges real-world data from any source,
including, but not limited to, global positioning systems, gesture
control, motion control, radio frequency motion capture, reflective
motion capture and/or any product tracking mechanism.
[0095] The entire operating container, in a dimensional embodiment,
will have a "Universe" skin which is a scaled down representation
of the known universe. Stellar data is used to create an active
volumetric skin where containers, vector nodes (vN), polygons,
objects and migrating data sets are represented as, but not limited
to, planets, moons, stars, nebulas, galaxies, wormholes, black
holes and other stellar objects.
[0096] The virtual universe model is the initial visual
implementation of the volumetric vector node and object based
multi-dimensional operating container. The total view can be
changed to fit within a business-to-business solution
infrastructure or an application specific user interface (UI).
Thus, specific embodiments and applications of the inventive
subject matter have been disclosed. It should be apparent, however,
to those skilled in the art that many more modifications besides
those already described herein are possible without departing from
the inventive concepts herein. The inventive subject matter,
therefore, is not to be restricted except in the spirit of the
appended claims.
* * * * *