U.S. patent application number 16/734512 was filed with the patent office on 2020-06-11 for systems and methods for controlling an aerial vehicle using lateral propulsion and vertical movement.
The applicant listed for this patent is LOON LLC. Invention is credited to Cyrus Behroozi, C.O. Lee Boyce, JR., Sergey Vichik.
Application Number | 20200183398 16/734512 |
Document ID | / |
Family ID | 65719296 |
Filed Date | 2020-06-11 |
United States Patent
Application |
20200183398 |
Kind Code |
A1 |
Vichik; Sergey ; et
al. |
June 11, 2020 |
SYSTEMS AND METHODS FOR CONTROLLING AN AERIAL VEHICLE USING LATERAL
PROPULSION AND VERTICAL MOVEMENT
Abstract
An aerial vehicle control system includes an aerial vehicle and
a computing device. The aerial vehicle includes an altitude
controller and a lateral propulsion controller. The computing
device includes a processor and a memory. The memory stores
instructions that, when executed by the processor, cause the
computing device to obtain location data corresponding to a
location of the aerial vehicle; obtain wind data; determine an
altitude command, a latitude command, and a longitude command based
on at least one of the location data or the wind data; cause the
altitude controller to implement at least one of the altitude
command, the latitude command, or the longitude command; and cause
the lateral propulsion controller to implement at least one of the
altitude command, the latitude command, or the longitude
command.
Inventors: |
Vichik; Sergey; (Palo Alto,
CA) ; Behroozi; Cyrus; (Menlo Park, CA) ;
Boyce, JR.; C.O. Lee; (Mountain View, CA) |
|
Applicant: |
Name |
City |
State |
Country |
Type |
LOON LLC |
Mountain View |
CA |
US |
|
|
Family ID: |
65719296 |
Appl. No.: |
16/734512 |
Filed: |
January 6, 2020 |
Related U.S. Patent Documents
|
|
|
|
|
|
Application
Number |
Filing Date |
Patent Number |
|
|
15711003 |
Sep 21, 2017 |
10558219 |
|
|
16734512 |
|
|
|
|
Current U.S.
Class: |
1/1 |
Current CPC
Class: |
G05D 1/102 20130101;
G05D 1/101 20130101; G05D 1/0204 20130101; B64B 1/02 20130101; B64B
1/62 20130101; G05D 1/046 20130101; B64C 19/02 20130101 |
International
Class: |
G05D 1/02 20060101
G05D001/02; G05D 1/10 20060101 G05D001/10; G05D 1/04 20060101
G05D001/04; B64C 19/02 20060101 B64C019/02 |
Claims
1. A lighter-than-air vehicle, comprising: an outer envelope
configured to be filled with lifting gas for floating the
lighter-than-air vehicle in the atmosphere; a gondola configured to
receive one or more pieces of equipment, the gondola being coupled
to the outer envelope, the gondola being configured for suspension
beneath the outer envelope while floating in the atmosphere; an
altitude controller received by the gondola, the altitude
controller being configured to alter a float altitude of the
lighter-than-air vehicle via buoyancy adjustments; a propeller
configured to effect lateral direction changes for the
lighter-than-air vehicle; an arm member coupled to the propeller;
and a lateral propulsion controller received by the gondola, the
lateral propulsion controller being configured to control at least
one of the propeller and the arm member in order to manage at least
one of a location or lateral movement of the lighter-than-air
vehicle during flight.
2. The lighter-than-air vehicle of claim 1, wherein the arm member
is coupled between the propeller and the gondola.
3. The lighter-than-air vehicle of claim 1, wherein the
lighter-than-air vehicle is configured for operation in the
stratosphere.
4. The lighter-than-air vehicle of claim 1, wherein the arm member
is configured to articulate.
5. The lighter-than-air vehicle of claim 4, wherein the lateral
propulsion controller is configured to control articulation of the
arm member to cause the lighter-than-air vehicle to move in a
selected lateral direction.
6. The lighter-than-air vehicle of claim 1, further comprising: a
ballonet received within the outer envelope, the ballonet being
configured to control buoyancy of the lighter-than-air vehicle;
wherein the altitude controller is configured to adjust the
buoyancy of the lighter-than-air vehicle by modifying a state of
the ballonet.
7. The lighter-than-air vehicle of claim 1, further comprising: one
or more location sensors configured to output location data of the
lighter-than-air vehicle; wherein the altitude controller is
configured to alter the float altitude based on the output location
data, and the lateral propulsion controller is configured to manage
at least one of the location or movement of the lighter-than-air
vehicle based on the output location data.
8. The lighter-than-air vehicle of claim 7, wherein the altitude
controller is configured to: compare a current altitude of the
lighter-than-air vehicle based on the output location data to a
desired altitude; determine, based on the comparison, whether an
altitude adjustment is needed; and effect the altitude adjustment
based on the determination.
9. The lighter-than-air vehicle of claim 8, wherein the desired
altitude is based on a received navigation command.
10. The lighter-than-air vehicle of claim 8, wherein the
determination of whether the altitude adjustment is needed includes
a determination of whether the current altitude falls within a
tolerance band of matching the desired altitude.
11. The lighter-than-air vehicle of claim 7, wherein the lateral
propulsion controller is configured to: compare a current lateral
position of the lighter-than-air vehicle based on the output
location data to a desired lateral position; determine, based on
the comparison, whether a lateral position adjustment is needed;
and effect the lateral position adjustment based on the
determination.
12. The lighter-than-air vehicle of claim 11, wherein the desired
lateral position is based on a received navigation command.
13. The lighter-than-air vehicle of claim 11, wherein the
determination of whether the lateral position adjustment is needed
includes a determination of whether the current lateral position
falls within a tolerance band for the desired lateral position.
14. The lighter-than-air vehicle of claim 11, wherein the lateral
propulsion controller is configured to effect the lateral position
adjustment by computing a propulsion command to control at least
one of the propeller and the arm member.
15. The lighter-than-air vehicle of claim 14, wherein the lateral
propulsion command includes an amount of propulsion for the
propeller.
16. The lighter-than-air vehicle of claim 14, wherein the lateral
propulsion command includes a direction in which at least one of
the propeller or the arm member are to propel the lighter-than-air
vehicle.
17. The lighter-than-air vehicle of claim 1, further comprising one
or more motors configured to drive the propeller.
18. The lighter-than-air vehicle of claim 1, wherein the
lighter-than-air vehicle comprises a balloon.
19. The lighter-than-air vehicle of claim 1, wherein the one or
more pieces of equipment received by the gondola include a
communication transceiver configured for wireless communication
with one or more ground-based computing devices.
20. The lighter-than-air vehicle of claim 1, wherein the one or
more pieces of equipment received by the gondola include a
telecommunication module configured to provide Long-Term Evolution
(LTE) service.
Description
CROSS-REFERENCE TO RELATED APPLICATIONS
[0001] The present application is a continuation of U.S.
application Ser. No. 15/711,003, filed Sep. 21, 2017, the entire
disclosure of which is incorporated by reference herein.
BACKGROUND
[0002] A conventional airship, to maintain its position within the
air or to move to a new position, requires a capability of
propelling itself at an airspeed that is at least equal in
magnitude to that of the experienced wind speed. However, because
airship size, power, and cost are proportional to the cube of
airspeed, a conventional airship may not be cost-effective for
certain applications. Other aerial vehicles, such as balloons, can
move vertically to exploit various wind directions to maintain its
position within the air or to move to a new position. However, in
some instances, the ability of such an aerial vehicle to maintain
or move its position based on wind may be limited owing to wind
characteristics associated with geographical zones or seasons.
SUMMARY
[0003] In one aspect, this disclosure describes an aerial vehicle
control system including an aerial vehicle and a computing device.
The aerial vehicle includes an altitude controller and a lateral
propulsion controller. The computing device includes a processor
and a memory. The memory stores instructions that, when executed by
the processor, cause the computing device to: obtain location data
corresponding to a location of the aerial vehicle; obtain wind
data; determine an altitude command, a latitude command, and a
longitude command based on at least one of the location data or the
wind data; cause the altitude controller to implement at least one
of the altitude command, the latitude command, or the longitude
command; and cause the lateral propulsion controller to implement
at least one of the altitude command, the latitude command, or the
longitude command.
[0004] In embodiments, the memory stores further instructions that,
when executed by the processor, cause the computing device to
obtain a navigation command corresponding to at least one of a
desired altitude of the aerial vehicle, a desired latitude
coordinate of the aerial vehicle, or a desired longitude coordinate
of the aerial vehicle. The determining of the altitude command, the
latitude command, and the longitude command is further based on the
navigation command.
[0005] In embodiments, the altitude command is implemented by the
altitude controller so that the aerial vehicle is positioned at the
desired altitude, within a tolerance threshold, and the latitude
command and the longitude command are implemented by the lateral
propulsion controller so that the aerial vehicle is positioned at
the desired latitude coordinate and the desired longitude
coordinate, within a tolerance threshold.
[0006] In embodiments, the location data includes at least one of:
altitude data corresponding to an altitude of the aerial vehicle,
latitude data corresponding to a latitude coordinate of the aerial
vehicle, or longitude data corresponding to a longitude coordinate
of the aerial vehicle, and wherein the determining of the altitude
command, the latitude command, and the longitude command is further
based on at least one of the altitude data, the latitude data, or
the longitude data.
[0007] In embodiments, the computing device is communicatively
coupled to the aerial vehicle by way of a wireless communication
link, and the memory stores further instructions that, when
executed by the processor, cause the computing device to transmit
the altitude command, the latitude command, and the longitude
command to the aerial vehicle via the wireless communication link,
to cause the altitude controller to implement at least one of the
altitude command, the latitude command, or the longitude command,
and to cause the lateral propulsion controller to implement at
least one of the altitude command, the latitude command, or the
longitude command.
[0008] In embodiments, the aerial vehicle further includes a
sensor, and the memory stores further instructions that, when
executed by the processor, cause the computing device to obtain the
location data from the sensor by way of the wireless communication
link.
[0009] In embodiments, the wind data corresponds to wind at or near
at least one of the location of the aerial vehicle or the altitude
of the aerial vehicle.
[0010] In embodiments, the wind data is obtained from a data source
including at least one of a publicly available weather data source
or a data source including data aggregated from a plurality of
aerial vehicles.
[0011] In embodiments, the aerial vehicle further includes an
air-gas altitude control system; and a propeller. The memory stores
further instructions that, when executed by the processor, cause
the computing device to: cause the altitude controller to implement
at least one of the altitude command, the latitude command, or the
longitude command by causing the altitude controller to actuate the
air-gas altitude control system based on at least one of the
altitude command, the latitude command, or the longitude command;
and cause the lateral propulsion controller to implement at least
one of the altitude command, the latitude command, or the longitude
command by causing the lateral propulsion controller to actuate the
propeller based on at least one of the altitude command, the
latitude command, or the longitude command.
[0012] In embodiments, the determining of the altitude command, the
latitude command, and the longitude command is performed at least
in part by determining, based on at least one of the location data
or the wind data and an amount of power of the aerial vehicle that
is associated with executing the altitude command, the latitude
command, and the longitude command.
[0013] In another aspect, the present disclosure describes an
aerial vehicle control method. The method includes obtaining
location data corresponding to a location of the aerial vehicle;
obtaining wind data from a wind data source; determining an
altitude command, a latitude command, and a longitude command based
on at least one of the location data or the wind data; causing an
altitude controller of the aerial vehicle to implement at least one
of the altitude command, the latitude command, or the longitude
command; and causing a lateral propulsion controller of the aerial
vehicle to implement at least one of the altitude command, the
latitude command, or the longitude command.
[0014] In embodiments, method further includes obtaining a
navigation command corresponding to at least one of a desired
altitude of the aerial vehicle, a desired latitude coordinate of
the aerial vehicle, or a desired longitude coordinate of the aerial
vehicle, and the determining of the altitude command, the latitude
command, and the longitude command is further based on the
navigation command.
[0015] In embodiments, the altitude command is implemented by the
altitude controller so that the aerial vehicle is positioned at the
desired altitude, within a tolerance threshold, and the latitude
command and the longitude command are implemented by the lateral
propulsion controller so that the aerial vehicle is positioned at
the desired latitude coordinate and the desired longitude
coordinate, within a tolerance threshold.
[0016] In embodiments, the location data includes at least one of
altitude data corresponding to an altitude of the aerial vehicle,
latitude data corresponding to a latitude coordinate of the aerial
vehicle, or longitude data corresponding to a longitude coordinate
of the aerial vehicle, and the determining of the altitude command,
the latitude command, and the longitude command is further based on
at least one of the altitude data, the latitude data, or the
longitude data.
[0017] In embodiments, the causing the altitude controller to
implement at least one of the altitude command, the latitude
command, or the longitude command includes transmitting, from a
computing device to the aerial vehicle by way of a wireless
communication link, the altitude command, the latitude command, and
the longitude command, and the causing the lateral propulsion
controller to implement at least one of the altitude command, the
latitude command, or the longitude command includes transmitting,
from the computing device to the aerial vehicle by way of the
wireless communication link, the altitude command, the latitude
command, and the longitude command.
[0018] In embodiments, the location data corresponding to the
location of the aerial vehicle is obtained by the computing device
from a sensor of the aerial vehicle by way of the wireless
communication link.
[0019] In embodiments, the wind data corresponds to wind at or near
at least one of the location of the aerial vehicle or the altitude
of the aerial vehicle, and the wind data source includes at least
one of a publicly available weather data source or a data source
including data aggregated from a plurality of aerial vehicles.
[0020] In embodiments, the causing the altitude controller to
implement at least one of the altitude command, the latitude
command, or the longitude command includes causing the altitude
controller to actuate an air-gas altitude control system of the
aerial vehicle based on at least one of the altitude command, the
latitude command, or the longitude command, and the causing the
lateral propulsion controller to implement at least one of the
altitude command, the latitude command, or the longitude command
includes causing the lateral propulsion controller to actuate a
propeller of the aerial vehicle based on at least one of the
altitude command, the latitude command, or the longitude
command.
[0021] In embodiments, the determining of the altitude command, the
latitude command, and the longitude command is performed at least
in part by determining, based on at least one of the location data
or the wind data and an amount of power of the aerial vehicle that
is associated with executing the altitude command, the latitude
command, and the longitude command.
[0022] In another aspect, the present disclosure describes a
computer-readable medium that has sequences of instructions stored
thereon. The instructions, when executed by a processor, cause the
processor to: obtain location data corresponding to a location of
an aerial vehicle; obtain wind data from a wind data source;
determine an altitude command, a latitude command, and a longitude
command based on at least one of the location data or the wind
data; cause an altitude controller of the aerial vehicle to
implement at least one of the altitude command, the latitude
command, or the longitude command; and cause a lateral propulsion
controller of the aerial vehicle to implement at least one of the
altitude command, the latitude command, or the longitude
command.
BRIEF DESCRIPTION OF THE DRAWINGS
[0023] Various aspects and features of the present systems and
methods for controlling an aerial vehicle are described herein
below with references to the drawings, wherein:
[0024] FIG. 1 is a schematic diagram of an illustrative aerial
vehicle system, in accordance with an embodiment of the present
disclosure;
[0025] FIG. 2 is a schematic diagram showing additional aspects of
the aerial vehicle system of FIG. 1, in accordance with an
embodiment of the present disclosure;
[0026] FIG. 3 is a schematic block diagram of an illustrative
embodiment of a computing device that may be employed in various
embodiments of the present system, for instance, as part of the
system or components of FIG. 1 or 2, in accordance with an
embodiment of the present disclosure;
[0027] FIG. 4 is a flowchart showing an illustrative method for
controlling an aerial vehicle from the perspective of a computing
device of FIG. 1, in accordance with an embodiment of the present
disclosure; and
[0028] FIG. 5 is a flowchart showing an illustrative method for
controlling an aerial vehicle from the perspective of the aerial
vehicle of FIG. 1, in accordance with an embodiment of the present
disclosure.
DETAILED DESCRIPTION
[0029] The present disclosure is directed to systems and methods
for controlling an aerial vehicle using a combination of vertical
movement, for instance, by way of a buoyancy control mechanism
(such as an air-gas altitude control system), and lateral
propulsion, for instance, by way of a propeller. In one aspect, the
systems and methods of the present disclosure enable an aerial
vehicle to maintain its position within the air or to move to a new
position in a cost-effective manner, without requiring a propulsion
power at an airspeed that is at least equal in magnitude to that of
the experienced wind speed, and in a manner that is not limited by
wind characteristics, such as those associated with geographical
zones or seasons. The systems and methods of the present
disclosure, in some aspects, combine a vertical balloon-style
movement with a relatively low-speed lateral propulsion, one or
both of which are controlled based on aggregated data, such as wind
data, aerial vehicle location data, and/or the like, to optimize
the amount of power consumption. In some examples, the aerial
vehicle control of the present disclosure applies relatively small
lateral corrections to any remaining drift after a combined effect
of vertical maneuvers.
[0030] With reference to FIG. 1, an illustrative aerial vehicle
system 100 includes an aerial vehicle 102, one or more computing
devices 104, and one or more data sources 106, not drawn to scale.
The aerial vehicle 102 and the computing devices 104 are
communicatively coupled to one another by way of a first wireless
communication link 108, and the computing devices 104 and the data
sources 106 are communicatively coupled to one another by way of a
second wireless communication link 110. Although not separately
shown in FIG. 1, the communication links 108 and/or 110 may include
satellite links and/or other intervening devices, links, and/or
networks. In some aspects, the aerial vehicle 102 is configured to
be launched into and moved about the atmosphere, and the computing
devices 104 cooperate as a ground-based distributed array to
perform their functions described herein. The data sources 106 may
include airborne data sources, such as airborne weather balloons,
additional airborne aerial vehicles 102, satellite data sources,
and/or the like, and/or ground-based data sources, such as publicly
available and/or proprietary databases. Although the present
disclosure is provided in the context of an embodiment where the
system 100 includes multiple computing devices 104 and multiple
data sources 106, in other embodiments the system 100 may include a
single computing device 104 and a single data source 106. Further,
although FIG. 1 shows a single aerial vehicle 102, in various
embodiments the system 100 includes a fleet of multiple aerial
vehicles 102 that are positioned at different locations throughout
the atmosphere and that are configured to communicate with the
computing devices 104, the data sources 106, and/or one another by
way of the communication links 108 and/or 110.
[0031] In various embodiments, the aerial vehicle 102 may be
configured to perform a variety of functions or provide a variety
of services, such as, for instance, telecommunication services
(e.g., long term evolution (LTE) service), hurricane monitoring
services, ship tracking services, services relating to imaging,
astronomy, radar, ecology, conservation, and/or other types of
functions or services. In general, the systems and methods of the
present disclosure provide techniques for controlling the position
(also referred to as location) and/or movement of the aerial
vehicles 102 throughout the atmosphere or beyond, to facilitate
effective and efficient performance of their functions or provision
of their services, as the case may be. As described in further
detail herein, the computing devices 104 are configured to obtain a
variety of types of data from a variety of sources and, based on
the obtained data, communicate messages to the aerial vehicle 102
to control its position and/or movement during flight.
[0032] With continued reference to FIG. 1, the aerial vehicle 102
includes an outer envelope 112 and a gondola 114, which is
suspended beneath the outer envelope 112 while the aerial vehicle
102 is in flight. The outer envelope 112 includes one or more
ballonets 116 which, as described in further detail below, are used
to control the buoyancy, and in turn the altitude, of the aerial
vehicle 102 in flight. In some aspects, the ballonets 116 include
air and the outer envelope 112 includes a lifting gas that is
lighter than air. The altitude controller 126 controls a pump and a
valve (neither of which is shown in FIG. 1) to pump air into the
ballonets 116 (from air outside the aerial vehicle 102) to increase
the mass of the aerial vehicle 102 and lower its altitude, or to
release air from the ballonets 116 (into the atmosphere outside the
aerial vehicle 102) to decrease the mass of the aerial vehicle 102
and increase its altitude. The combination of the altitude
controller 126, the outer envelope 112, the ballonets 116, and the
valves and pumps (not shown in FIG. 1) may be referred to as an
air-gas altitude control system, however other types of buoyancy
control mechanisms are contemplated as well.
[0033] The outer envelope 112 also has one or more solar panels 134
affixed to its upper portion that absorb sunlight, when available,
and generate electrical energy from the absorbed sunlight. The
solar panels 134 provide, by way of power paths such as power path
136, the generated electrical energy to the various components of
the aerial vehicle 102, such as components housed within the
gondola 114, for utilization during flight.
[0034] The gondola 114 includes a variety of components, some of
which may or may not be included, depending upon the application
and/or needs. Although not expressly shown in FIG. 1, the various
components of the aerial vehicle 102 in general, and/or of the
gondola 114 in particular, may be coupled to one another for
communication of power, data, and/or other signals or information.
The example gondola 114 shown in FIG. 1 includes a propulsion
controller 120, one or more sensors 128, an energy storage module
124, a power plant 122, an altitude controller 126, a transceiver
132, and other on-board equipment 130. The transceiver 132 is
configured to wirelessly communicate data between the aerial
vehicle 132 and the computing devices 104 and/or data sources 106
by way of the wireless communication link 108 and/or the
communication link 110, respectively.
[0035] The gondola 114 also has a propeller 118 affixed to either
of its ends by way of an articulable arm member 138. The propulsion
controller 120 controls the propeller 118 to provide propulsion,
such as lateral propulsion, to propel the aerial vehicle 102 to
assist in controlling its position and/or movement during flight.
As described below in further detail, in various embodiments the
propulsion controller 120 is configured to control the propeller
118 based at least in part upon a propulsion command that is
generated by, and received from, the computing devices 104 by way
of the wireless communication link 108 and the transceiver 132. In
some aspects, the propulsion controller 120 implements the
propulsion command by causing the actuation of the propeller 118
based on the propulsion command. The configuration of the propeller
118 and the articulable arm member 138 shown in FIG. 1 is provided
by way of example and not limitation. Other configurations of
propulsion are contemplated. For instance, in other embodiments,
the aerial vehicle 102 may include multiple propellers 118 affixed
to corresponding portions of the gondola 114, or may include an arm
member that is inarticulable in contrast to the articulable arm
member 138, or may include alternative methods of propulsion known
in the art. The propeller 118 and/or the articulable arm member 138
may be employed to propel the aerial vehicle 102 in a lateral
direction (in which case, the propulsion controller 120 may be
referred to as a lateral propulsion controller) and/or in a
vertical direction.
[0036] In some embodiments, the sensors 128 include a global
position satellite (GPS) sensor that senses and outputs location
data, such as latitude, longitude, and/or altitude data
corresponding to a latitude, longitude, and/or altitude of the
aerial vehicle 102 in the earth's atmosphere. The sensors 128 are
configured to provide the location data to the computing devices
104 by way of the wireless transceiver 132 and the wireless
communication link 108 for use in controlling the aerial vehicle
102, as described in further detail below.
[0037] The energy storage module 124 includes one or more batteries
or one or more other energy storage devices, such as one or more
fuel cells, that store electrical energy provided by the solar
panels 134 for use by the various components of the aerial vehicle
102. The power plant 122 obtains electrical energy stored by the
energy storage module 124 and converts and/or conditions the
electrical energy to a form suitable for use by the various
components of the aerial vehicle 102. In some embodiments, the
power plant 122 also includes one or more motors (not shown in FIG.
1) configured to drive the propeller 118.
[0038] The altitude controller 126 is configured to control the
ballonets 116 to adjust the buoyancy of the aerial vehicle 102 to
assist in controlling its position and/or movement during flight.
As described below in further detail, in various embodiments the
altitude controller 126 is configured to control the ballonets 116
based at least in part upon an altitude command that is generated
by, and received from, the computing devices 104 by way of the
wireless communication link 108 and the transceiver 132. In some
examples, the altitude controller 126 is configured to implement
the altitude command by causing the actuation of the air-gas
altitude control system based on the altitude command.
[0039] The on-board equipment 130 may include a variety of types of
equipment, depending upon the application or needs, as outlined
above. For example, the on-board equipment 130 may include LTE
transmitters and/or receivers, weather sensors, imaging equipment,
and/or any other suitable type of equipment.
[0040] Having provided an overview of the aerial vehicle system 100
in the context of FIG. 1, reference is now made to FIG. 2, which
shows certain portions of the aerial vehicle system 100, in
accordance with an embodiment of the present disclosure. In
particular, FIG. 2 illustrates an example embodiment of how
functionality and corresponding components are allocated among the
aerial vehicle 102, the computing devices 104, and/or the data
sources 106, to control a position and/or movement of the aerial
vehicle 102. Although more detailed aspects of how the system 100
implements control of the aerial vehicle 102 are provided below in
the context of FIG. 4, FIG. 2 provides an overview of the
functionality and component allocation. The arrangement of
components depicted in FIG. 2 is provided by way of example and not
limitation. Other arrangements of components and allocations of
functionality are contemplated, for instance, with the aerial
vehicle 102 including components that implement functionality shown
in FIG. 2 as being implemented by the computing devices 104, or
vice versa. However, in the example shown in FIG. 2, a majority of
components and functionality are allocated to the computing devices
104 instead of to the aerial vehicle 102, which decreases the
amount of energy required to operate the components of the aerial
vehicle 102 and thus enables the components of the aerial vehicle
102 to utilize a greater portion of the available energy than would
be possible if more components and functionality were allocated to
the aerial vehicle 102. This increases the capabilities of the
aerial vehicle 102 for implementing functionality and/or providing
services for a given amount of available energy.
[0041] In addition to certain components that were introduced above
in connection with FIG. 1, FIG. 2 shows a wind mixer module 202, a
navigation module 204, and a maneuver automation module 206 that
are included within the computing devices 104. Once the aerial
vehicle 102 is in flight in the atmosphere, the sensors 128 are
configured to periodically transmit to the wind mixer module 202,
by way of the transceiver 132 and the wireless communication link
108, location data, such as timestamped GPS positions of the aerial
vehicle 102 at corresponding times, and measured wind data. The
wind mixer module 202 utilizes the location data and measured wind
data obtained from the sensors 128 and, in some instances, wind
pattern data obtained from other data sources 106 (such as National
Oceanic and Atmospheric Administration (NOAA) data sources,
European Centre for Medium-Range Weather Forecasts (ECMWF) data
sources, and/or the like) to infer or estimate the winds in which
the aerial vehicle 102 is flying or is expected to be flying. In
particular, wind points are stored in the wind mixer module 202,
which constructs a kernel function, such as a Gaussian Process
kernel function that assists the navigation module 204 in
determining how to navigate the aerial vehicle 102 based on the
inferred or estimated winds, according to one or more predetermined
navigation algorithms. Examples of types of navigation algorithms
that may be implemented by the navigation module 204 are described
in U.S. patent application Ser. Nos. 15/662,940; 15/662,968;
15/663,000; and 15/663,030; each entitled SYSTEMS AND METHODS FOR
CONTROLLING AERIAL VEHICLES and each filed on Jul. 28, 2017; and in
U.S. patent application Ser. No. 15/663,117, entitled SYSTEM AND
METHODS FOR SIMULATING WIND NOISE MODELS and filed on Jul. 28,
2017, each application of which is hereby incorporated by reference
herein in its entirety. For instance, aerial vehicles may travel at
very high altitudes, including up to approximately 20 kilometers
above the Earth's surface in the stratosphere, which is well above
the altitudes of airplanes, wildlife, and weather events. In the
stratosphere, winds are stratified, and each layer of wind may vary
in speed and/or direction. The aerial vehicles may be moved using
such winds, and a direction and/or speed of movement of the aerial
vehicles may be controlled based on the winds in the various layers
of the stratosphere. However, reliance on predicted weather data
alone may be undesirable in planning and/or controlling flight
paths of the aerial vehicles, because predicted weather data may be
locally inaccurate and/or outdated. Thus, planning a flight path or
course of an aerial vehicle may be based on prevailing wind
patterns, and seeking an optimal altitude for the aerial vehicle to
move along a desired heading and/or at a desired speed, based on
uncertainty in the prevailing wind patterns. Depending upon the
navigation algorithm being implemented, the navigation module 204
generates a maneuver plan, which includes one or more navigation
commands that define how the aerial vehicle 102 is to move or
remain stationary, and registers the maneuver plan with the
maneuver automation module 206.
[0042] In various embodiments, the navigation module 204 may
generate various types of maneuver plans that include various types
of navigation commands. For example, a coordinate-based maneuver
plan may include one or more coordinate-based navigation commands,
and a vector-based maneuver plan may include one or more
vector-based navigation commands. In particular, a coordinate-based
maneuver plan may include as a coordinate-based navigation command
an item of location data that defines a location that the aerial
vehicle 102 should attempt to attain and/or maintain. The item of
location data of the coordinate-based navigation command may
include two subcomponents: (1) a vertical navigation command, which
defines a vertical geographical position or altitude that the
aerial vehicle 102 should attempt to attain and/or maintain and
which may be represented by a barometric pressure, and (2) a
horizontal navigation command, which may be a combination of a
latitude coordinate and a longitude coordinate and which defines a
horizontal geographic position (e.g., latitude coordinate and a
longitude coordinate) that the aerial vehicle 102 should attempt to
attain and/or maintain. As described further herein, in some
embodiments, based upon the vertical navigation command and/or
horizontal navigation command received from the computing devices
104, the aerial vehicle 102 generates an appropriate altitude
command and/or propulsion command by which the altitude controller
126 and propulsion controller 120 are actuated to effect the
overall navigation command or maneuver plan. In other embodiments,
for instance as described in connection with FIG. 4 and FIG. 5, the
computing device 104 generates the appropriate altitude command
and/or propulsion command and communicates the altitude command
and/or propulsion command to the aerial vehicle 102 as the
navigation command.
[0043] A vector-based maneuver plan may include as a vector-based
navigation command an item of navigational vector data which
includes a directional navigation command and a velocity navigation
command (or a force command, an acceleration command, or any other
type of magnitude-based command). The directional navigation
command defines a direction in which the aerial vehicle 102 should
attempt to move and the velocity navigation command (or other
magnitude-based command) defines a velocity (or force,
acceleration, or other magnitude) at which the aerial vehicle 102
should attempt to move in the defined direction. The directional
navigation command may be defined as a combination of a
cardinal-based direction and/or an elevational direction (e.g.,
north, south, east, west, elevate, descend, and/or the like), or
may be defined in terms of any reference coordinate system. The
directional navigation command may include two subcomponents: (1) a
vertical navigation command that defines how the aerial vehicle 102
should move, if at all, in a vertical direction (e.g., ascend,
descend, or maintain current altitude) and (2) a horizontal
navigation command that defines how the aerial vehicle 102 should
move, if at all, in a horizontal direction (e.g., north, south,
east, west, and/or the like). As described further herein, in some
embodiments, based upon the vertical navigation command and/or
horizontal navigation command received from the computing devices
104, the aerial vehicle 102 generates an appropriate altitude
command and/or propulsion command by which the altitude controller
126 and propulsion controller 120 are actuated to effect the
overall navigation command or maneuver plan. In other embodiments,
for instance as described in connection with FIG. 4 and FIG. 5, the
computing device 104 generates the appropriate altitude command
and/or propulsion command and communicates the altitude command
and/or propulsion command to the aerial vehicle 102 as the
navigation command.
[0044] Additionally, the maneuver plan may include a single
navigation command (e.g., a single item of location data or a
single item of navigational vector data) that defines a single
position or motion (e.g, a single geographical location or a single
direction and velocity pair) that the aerial vehicle 102 should
attempt to attain or maintain until instructed otherwise.
Alternatively, or additionally, the maneuver plan may be time-based
and include multiple navigation commands (e.g., multiple items of
location data or multiple items of navigational vector data) that
define multiple positions or motions (e.g., a series of locations
or a series of direction and velocity pairs) that the aerial
vehicle 102 should attempt to attain or maintain at corresponding
times. In some embodiments the time-based maneuver plan may be
represented as a table stored in a memory of the computing devices
104 and/or communicated to the aerial vehicle 102.
[0045] The maneuver automation module 206 sequentially transfers
the generated maneuver plan, or more specifically, the one or more
navigation commands (e.g., coordinate-based navigation commands or
vector-based navigation commands) that are included in the maneuver
plan, to the altitude controller 126 and/or the propulsion
controller 120 for implementation. In particular, in one example
for a coordinate-based maneuver plan, the maneuver automation
module 206 transmits to the transceiver 132, by way of the wireless
communication link 108, an altitude command (for example, which may
be specified as a barometric pressure, which may be equivalent to
pressure altitude, and which indicates a desired altitude for the
aerial vehicle 102 to maintain within some tolerance band) and a
propulsion command (for example, which indicates a desired
propulsion amount and/or direction for the aerial vehicle 102 to
maintain within some tolerance band). The altitude controller 126
and the propulsion controller 120 are configured to execute
altitude and propulsion loops, respectively, whereby the altitude
controller 126 and the propulsion controller 120 periodically
receive the altitude command and the propulsion command from the
computing devices 104, and execute those commands to control the
position (e.g., latitude, longitude, altitude) and/or movement of
the aerial vehicle 102.
[0046] In various embodiments, a feedback loop may be implemented
in a variety of ways in an effort to ensure that the aerial vehicle
102 attaining or maintaining the desired location and/or movement
according to the maneuver plan. For example, in some embodiments,
the aerial vehicle 102 is configured to actuate its altitude
controller 126 and/or propulsion controller 120 based on the
navigation command(s) received from the computing devices 104 and
provide feedback, such as location data, to the computing devices
104. The computing devices 104 use the location data feedback to
verify that the aerial vehicle 102 is attaining or maintaining the
desired location and/or movement according to the maneuver plan,
and, if necessary, adjust the maneuver plan accordingly and
communicate updated navigation commands to the aerial vehicle 102
for implementation. In other embodiments, for instance as
illustrated in FIG. 5 (described below), the aerial vehicle 102 is
configured to analyze location data from its sensors 128 to ensure
that the aerial vehicle 102 attaining or maintaining the desired
location and/or movement according to the maneuver plan and, if
necessary, adjust the actuation of its altitude controller 126
and/or its propulsion controller 120 accordingly.
[0047] FIG. 3 is a schematic block diagram of a computing device
300 that may be employed in accordance with various embodiments
herein. Although not explicitly shown in FIG. 1 or FIG. 2, in some
embodiments, the computing device 300, or one or more of the
components thereof, may further represent one or more components
(e.g., the computing device 104, components of the gondola 114, the
data sources 106, and/or the like) of the system 100. The computing
device 300 may, in various embodiments, include one or more
memories 302, processors 304, display devices 306, network
interfaces 308, input devices 310, and/or output modules 312. The
memory 302 includes non-transitory computer-readable storage media
for storing data and/or software that is executable by the
processor 304 and which controls the operation of the computing
device 300. In embodiments, the memory 302 may include one or more
solid-state storage devices such as flash memory chips.
Alternatively, or in addition to the one or more solid-state
storage devices, the memory 302 may include one or more mass
storage devices connected to the processor 304 through a mass
storage controller (not shown in FIG. 3) and a communications bus
(not shown in FIG. 3). Although the description of computer
readable media contained herein refers to a solid-state storage, it
should be appreciated by those skilled in the art that
computer-readable storage media can be any available media that can
be accessed by the processor 304. That is, computer readable
storage media includes non-transitory, volatile and non-volatile,
removable and non-removable media implemented in any method or
technology for storage of information such as computer-readable
instructions, data structures, program modules or other data.
Examples of computer-readable storage media include RAM, ROM,
EPROM, EEPROM, flash memory or other solid state memory technology,
CD-ROM, DVD, Blu-Ray or other optical storage, magnetic cassettes,
magnetic tape, magnetic disk storage or other magnetic storage
devices, or any other medium which can be used to store the desired
information and which can be accessed by computing device 300.
[0048] In some embodiments, the memory 302 stores data 314 and/or
an application 316. In some aspects the application 316 includes a
user interface component 318 that, when executed by the processor
304, causes the display device 306 to present a user interface (not
shown in FIG. 3). The network interface 308, in some embodiments,
is configured to couple the computing device 300 and/or individual
components thereof to a network, such as a wired network, a
wireless network, a local area network (LAN), a wide area network
(WAN), a wireless mobile network, a Bluetooth network, the
Internet, and/or another type of network. The input device 310 may
be any device by means of which a user may interact with the
computing device 300. Examples of the input device 310 include
without limitation a mouse, a keyboard, a touch screen, a voice
interface, and/or the like. The output module 312 may, in various
embodiments, include any connectivity port or bus, such as, for
example, a parallel port, a serial port, a universal serial bus
(USB), or any other similar connectivity port known to those
skilled in the art.
[0049] FIG. 4 is a flowchart showing an illustrative method 400 for
controlling an aerial vehicle from the perspective of the computing
devices 104 of the system 100, in accordance with an embodiment of
the present disclosure. At block 402, the wind mixer module 202
obtains, from the sensors 128 of the aerial vehicle 102 by way of
the transceiver 132 and the wireless communication link 108,
location data that is periodically transmitted by the aerial
vehicle 102. The location data is timestamped and indicates a
location, such as a latitude coordinate, a longitude coordinate,
and/or an altitude of the aerial vehicle 102 at a corresponding
time.
[0050] At block 404, the wind mixer module 202 obtains wind data,
such as wind pattern data, from a variety of sources, such as the
data sources 106, sensors 128 of the aerial vehicle 102, sensors
128 of other aerial vehicle 102 that are airborne, or were
previously airborne, and/or the like. At block 406, the wind mixer
module 202 utilizes the location data obtained at block 402 from
the sensors 128 and the wind data obtained at block 404 from the
data sources 106 to determine or estimate the winds in which the
aerial vehicle 102 is flying or is expected to be flying. Based on
the determined or estimated winds, the wind mixer module 202
constructs a wind model (e.g., including a kernel function as
described above), and forwards the wind model to the navigation
module 204.
[0051] At block 408, the navigation module 204 uses the wind model
provided at block 406 to determine how to navigate the aerial
vehicle 102, in view of the determined and/or estimated winds,
according to one or more predetermined navigation algorithms, as
described above. Based upon the particular navigation algorithm
being implemented, the navigation module 204 generates a maneuver
plan, which, in some embodiments, indicates one or more locations
(e.g., altitudes, latitude coordinates, and/or longitude
coordinates) that the aerial vehicle 102 should attempt to attain
or maintain at corresponding times, in accordance with the
navigation algorithm. The maneuver plan, in some instances, may
take the form of a table, such as the table 409 shown in FIG. 4
that matches times with corresponding locations. If a prior
maneuver plan has already been generated prior to the instant
iteration of block 408, then at block 408, the navigation module
204 determines whether the maneuver plan is to be updated based on
new or updated data, such as location data obtained at block 402
and/or wind data obtained at block 404. The navigation module 204
registers the generated or updated maneuver plan with the maneuver
automation module 206 for implementation.
[0052] At block 410, the maneuver automation module 206 determines
whether a navigation command is to be transmitted to the aerial
vehicle 102, based on the navigation algorithm executed at block
408. A navigation command may take a variety of forms as described
above, and in some embodiments includes location data that
indicates to the aerial vehicle 102 one or more desired locations
(e.g., latitude coordinates, longitude coordinates, and/or
altitudes) that the aerial vehicle 102 is to attempt to attain or
maintain at one or more corresponding times. The navigation command
may include a single location that the aerial vehicle 102 is to
attempt to attain immediately upon receipt, or the navigation
command may include multiple times and corresponding locations that
the aerial vehicle 102 is to attempt to attain or maintain at those
times. In some instances, the navigation command may include the
maneuver plan table 409 generated at block 408. In various
embodiments, the maneuver automation module 206 may transmit
navigation command items sequentially one at a time or may transmit
navigation command items in a batch, such as by way of the maneuver
plan table 409. The determination at block 410 as to whether the
maneuver automation module 206 is to transmit the navigation
command to the aerial vehicle 102 may be based on whether the
maneuver plan generated at block 408 is new or has already been
provided to the aerial vehicle 102 as the navigation command. If
the maneuver plan generated at block 408 is new and has not been
provided to the aerial vehicle 102, then it may be determined at
block 410 that the maneuver automation module 206 is to transmit
the plan location data (e.g., the maneuver plan table) to the
aerial vehicle 102. If the maneuver plan generated at block 408 is
not new and has already been provided to the aerial vehicle 102,
then it may be determined at block 410 that the maneuver automation
module 206 is not to transmit the navigation command to the aerial
vehicle 102. If the maneuver automation module 206 determines at
block 410 not to transmit the navigation command to the aerial
vehicle 102 ("NO" at block 410), then control passes back to block
402 to obtain additional or more up-to-date location data as
described above. If the maneuver automation module 206 determines
at block 410 to transmit the navigation command to the aerial
vehicle 102 ("YES" at block 410), then control block 412.
[0053] At block 412, the maneuver automation module 206 transmits
the navigation command to the aerial vehicle 102, particularly the
altitude controller 126 and/or propulsion controller 120 thereof,
by way of the wireless communication link 108 and the transceiver
132, in one or more of the manners described above, for
implementation according to the maneuver plan generated at block
408. In particular, the maneuver automation module 206 transmits to
the transceiver 132, by way of the wireless communication link 108,
an altitude command (for example, which may be specified as a
barometric pressure, which may be equivalent to pressure altitude,
and which indicates a desired altitude for the aerial vehicle 102
to maintain within some tolerance band), a latitude command (for
example, which may indicate a desired latitude coordinate), and/or
a longitude command (for example, which may indicate a desired
longitude coordinate) for the aerial vehicle 102 to attain or
maintain within some tolerance band. In some embodiments, in lieu
of specifying a location (e.g., altitude, latitude, and longitude),
the maneuver automation module 206 specifies to the aerial vehicle
102 a desired vector or direction of travel in the atmosphere.
[0054] As described in further detail below in connection with FIG.
5, in some embodiments, the altitude controller 126 and the
propulsion controller 120 are configured to execute altitude and
propulsion loops, respectively, whereby the altitude controller 126
and the propulsion controller 120 periodically receive the altitude
command and the propulsion command from the computing devices 104,
and execute those commands to control the position (e.g., latitude,
longitude, altitude) and/or movement of the aerial vehicle 102.
Although the altitude controller 126 is generally employed to
control the altitude of the aerial vehicle 102 and the propulsion
controller 120 is generally employed to control the latitude and
longitude coordinates of the aerial vehicle 102, in some
embodiments, the altitude controller 126 may also or alternatively
be employed to control the latitude and/or longitude coordinates of
the aerial vehicle 102 (for instance, by using wind data from the
data sources 106 to identify an altitude with a more favorable wind
direction and causing the aerial vehicle 102 to move to the
identified altitude), and the propulsion controller 120 may also or
alternatively be employed to control the altitude of the aerial
vehicle 102. In further embodiments, the altitude controller 126
and the propulsion controller 120 may be configured to cooperate
with one another to control any one or any combination of the
altitude, latitude coordinate, or longitude coordinate of the
aerial vehicle 102.
[0055] At block 414, a determination is made as to whether to
terminate control of the aerial vehicle 102, for instance, based on
whether the aerial vehicle 102 remains in flight and/or based on a
mode of operation of the aerial vehicle 102. If it is determined at
block 414 to terminate control of the aerial vehicle 102 ("YES" at
block 414), then the procedure 400 terminates. If it is determined
at block 414 not to terminate control of the aerial vehicle 102
("NO" at block 414), then control passes back to block 402 to
obtain additional or more up-to-date location data as described
above.
[0056] FIG. 5 is a flowchart showing an illustrative method 500 for
controlling an aerial vehicle, from the perspective of the aerial
vehicle 102, in accordance with an embodiment of the present
disclosure. At block 502, the aerial vehicle 102 receives, by way
of the wireless communication link 108 and the transceiver 132, the
navigation command transmitted (FIG. 4, block 412) by the computing
device 104. The aerial vehicle 102 periodically receives multiple
transmissions of navigation commands from the computing device 104,
as described above. If, at the time of receiving the navigation
command at the present instance of block 502, the aerial vehicle
102 has already received a navigation command at a prior instance
of block 502, then at the present instance of block 502, the aerial
vehicle 102 may overwrite the prior navigation command with the
more recently received and up-to-date navigation command.
[0057] At block 504, the altitude controller 126 and/or the
propulsion controller 120 obtain from the sensors 128 location
data, such as altitude data, latitude data, and/or longitude data
indicating a current altitude, latitude coordinate, and/or
longitude coordinate, respectively, of the aerial vehicle 102. As
described above, the altitude controller 126 and the propulsion
controller 120, in various embodiments, may separately control the
altitude, latitude, and longitude coordinates or may cooperate to
control the altitude, latitude and longitude coordinates. In this
regard, the altitude controller 126 and the propulsion controller
120 may obtain from the sensors 128 at block 504 whichever types of
location data may require for processing. In some embodiments, at
block 504, the altitude controller 126 obtains altitude data from
the sensors 128, and the propulsion controller 120 obtains latitude
data and longitude data from the sensors 128.
[0058] At block 506, the altitude controller 126 (or the propulsion
controller 120, as the case may be) compares the current altitude,
as obtained from the sensors 128 at block 504, to the desired
altitude, as dictated based on the navigation command that was
obtained at block 502 and the current time, to determine whether
any adjustment to altitude is needed. If the altitude controller
126 determines at block 506 that the current altitude matches the
desired altitude, within a tolerance band ("YES" at block 506),
then control passes to block 512. If the altitude controller 126
determines at block 506 that the current altitude does not match
the desired altitude, within the tolerance band ("NO" at block
506), then control passes to block 508.
[0059] At block 508, the altitude controller 126 computes an
altitude command to provide to the ballonets 116 in an effort to
move the aerial vehicle 102 throughout the atmosphere from the
current altitude to the desired altitude. At block 510, the
altitude controller 126 provides the altitude command to the
ballonets 116 to cause the aerial vehicle 102 to attempt to attain
and/or maintain the desired altitude.
[0060] At block 512, the propulsion controller 120 (or the altitude
controller 126, as the case may be) compares the current latitude
and longitude coordinates, as obtained from the sensors 128 at
block 504, to the desired latitude and longitude coordinates, as
dictated based on the navigation command that was obtained at block
502 and the current time, to determine whether any adjustment to
the latitude and/or longitude coordinates of the aerial vehicle 102
is needed. If the propulsion controller 120 determines at block 512
that the current latitude and longitude match the desired latitude
and longitude, within a tolerance band ("YES" at block 512), then
control passes to block 518. If the propulsion controller 120
determines at block 512 that the current latitude and/or longitude
does not match the desired latitude and/or longitude, within the
tolerance band ("NO" at block 512), then control passes to block
514.
[0061] At block 514, the propulsion controller 120 computes a
propulsion command to provide to the propeller 130 and/or the
articulable arm member 138 in an effort to move the aerial vehicle
102 throughout the atmosphere from the current latitude and/or
longitude to the desired latitude and/or longitude. At block 516,
the propulsion controller 120 provides the propulsion command to
the propeller 130 and/or the articulable arm member 138 to cause
the aerial vehicle 102 to attempt to attain and/or maintain the
desired latitude and/or longitude. The propulsion control command
may include an amount of propulsion for the propeller 130 to
provide, a direction in which the propeller 130 and/or the
articulable arm member 138 are to propel the aerial vehicle 102,
and/or the like.
[0062] At block 518, a determination is made as to whether to
terminate control of the aerial vehicle 102, for instance, based on
whether the aerial vehicle 102 remains in flight and/or based on a
mode of operation of the aerial vehicle 102. If it is determined at
block 518 to terminate control of the aerial vehicle 102 ("YES" at
block 518), then the procedure 500 terminates. If it is determined
at block 518 not to terminate control of the aerial vehicle 102
("NO" at block 518), then control passes back to block 520.
[0063] At block 520, a determination is made as to whether new
location command (for example, a new altitude command, latitude
control command, and/or longitude control command) is to be
provided to the altitude controller 126 and/or the propulsion
controller 130 adjust the altitude, latitude, and/or longitude
coordinates of the aerial vehicle 102, according to the navigation
command that was obtained at block 502. The determination at block
520 may be based upon comparing the current time to the
corresponding times listed in the navigation command (e.g.,
maneuver plan table 409, FIG. 4) to determine whether it is time to
move the aerial vehicle 102 to a new location or maintain the
aerial vehicle 102 at its current location obtained at block 504.
If it is determined at block 520 that a new location command is to
be provided ("YES" at block 520), then at block 522, a location set
point is updated to reflect the new desired altitude, desired
latitude coordinate, and/or desired longitude coordinate.
[0064] At block 524, a determination is made as to whether a new
navigation command has been received from the computing device 104,
for instance, to update the maneuver plan based on a change in
conditions, such as wind data or other weather data, or based on a
user input. If it is determined at block 524 that a new navigation
command has been received ("YES" at block 524), then control passes
back to block 502 to update or overwrite the navigation command
(e.g., maneuver plan table 409, FIG. 4) that was received at a
prior instance of block 502 with the navigation command that was
received at the most recent instance of block 502. If it is
determined at block 524 that no new navigation command has been
received ("NO" at block 524), then control passes back to block 504
to obtain new or more up-to-date current location data of the
aerial vehicle 102 in an effort to continue to cause the aerial
vehicle 102 to attain or maintain the desired altitude, latitude
coordinate, and longitude coordinate in the atmosphere.
[0065] The embodiments disclosed herein are examples of the present
systems and methods and may be embodied in various forms. For
instance, although certain embodiments herein are described as
separate embodiments, each of the embodiments herein may be
combined with one or more of the other embodiments herein. Specific
structural and functional details disclosed herein are not to be
interpreted as limiting, but as a basis for the claims and as a
representative basis for teaching one skilled in the art to
variously employ the present information systems in virtually any
appropriately detailed structure. Like reference numerals may refer
to similar or identical elements throughout the description of the
figures.
[0066] The phrases "in an embodiment," "in embodiments," "in some
embodiments," or "in other embodiments" may each refer to one or
more of the same or different embodiments in accordance with the
present disclosure. A phrase in the form "A or B" means "(A), (B),
or (A and B)." A phrase in the form "at least one of A, B, or C"
means "(A); (B); (C); (A and B); (A and C); (B and C); or (A, B,
and C)."
[0067] The systems and/or methods described herein may utilize one
or more controllers to receive various information and transform
the received information to generate an output. The controller may
include any type of computing device, computational circuit, or any
type of processor or processing circuit capable of executing a
series of instructions that are stored in a memory. The controller
may include multiple processors and/or multicore central processing
units (CPUs) and may include any type of processor, such as a
microprocessor, digital signal processor, microcontroller,
programmable logic device (PLD), field programmable gate array
(FPGA), or the like. The controller may also include a memory to
store data and/or instructions that, when executed by the one or
more processors, causes the one or more processors to perform one
or more methods and/or algorithms. In example embodiments that
employ a combination of multiple controllers and/or multiple
memories, each function of the systems and/or methods described
herein can be allocated to and executed by any combination of the
controllers and memories.
[0068] Any of the herein described methods, programs, algorithms or
codes may be converted to, or expressed in, a programming language
or computer program. The terms "programming language" and "computer
program," as used herein, each include any language used to specify
instructions to a computer, and include (but is not limited to) the
following languages and their derivatives: Assembler, Basic, Batch
files, BCPL, C, C+, C++, Delphi, Fortran, Java, JavaScript, machine
code, operating system command languages, Pascal, Perl, PL1,
scripting languages, Visual Basic, metalanguages which themselves
specify programs, and all first, second, third, fourth, fifth, or
further generation computer languages. Also included are database
and other data schemas, and any other meta-languages. No
distinction is made between languages which are interpreted,
compiled, or use both compiled and interpreted approaches. No
distinction is made between compiled and source versions of a
program. Thus, reference to a program, where the programming
language could exist in more than one state (such as source,
compiled, object, or linked) is a reference to any and all such
states. Reference to a program may encompass the actual
instructions and/or the intent of those instructions.
[0069] Any of the herein described methods, programs, algorithms or
codes may be contained on one or more non-transitory
computer-readable or machine-readable media or memory. The term
"memory" may include a mechanism that provides (in an example,
stores and/or transmits) information in a form readable by a
machine such a processor, computer, or a digital processing device.
For example, a memory may include a read only memory (ROM), random
access memory (RAM), magnetic disk storage media, optical storage
media, flash memory devices, or any other volatile or non-volatile
memory storage device. Code or instructions contained thereon can
be represented by carrier wave signals, infrared signals, digital
signals, and by other like signals.
[0070] The foregoing description is only illustrative of the
present systems and methods. Various alternatives and modifications
can be devised by those skilled in the art without departing from
the disclosure. Accordingly, the present disclosure is intended to
embrace all such alternatives, modifications and variances. The
embodiments described with reference to the attached drawing
figures are presented only to demonstrate certain examples of the
disclosure. Other elements, steps, methods, and techniques that are
insubstantially different from those described above and/or in the
appended claims are also intended to be within the scope of the
disclosure.
* * * * *