Patent Application
20230243615
This disclosure relates generally to a mobile defense system, and more specifically to a relatively compact, armored all-terrain vehicle with a turret on top that's compatible with conventional firearms as well as certain less than lethal weapons.
Traditionally, the job of securing a given finite area is performed by human security personnel that are co-located with their charge. Whether a private home, commercial interest, or even the space around an individual, human beings are tasked with putting their safety and sometimes their lives on the line for a paycheck. This model of security, which has remained unchanged since its inception, has two key problems.
The first of these is a reflection of human nature. While there are many highly motivated and dedicated security professionals working in the industry, none are infallible. In the course of carrying out their duty, at a critical moment (home invasions, active shooters, violent riots, etc.) they may decide, and rightly so, that their health or life is not worth risking, and abandon their post or shy away from action. A machine would not be able to make such a decision.
The second of these is the problem of cost, which itself can be broken down into two components. The first is monetary. Full time security guards, especially armed ones, are expensive to maintain. More so if the object of security is to be protected around the clock. Insurance, benefits, sick leave, vacations and so on are all expenses passed down to the consumer of security that do not directly benefit them.
The second of these is the potential cost of human lives. As a benefit of its achievement, civilized society over time tends to reduce the number of situations in which humans are exposed to the threat of physical harm. Besides military groups and police departments, private security professionals find themselves in the only other profession that pays them to be exposed to deliberate violence from other humans. Reducing the number of such jobs would aid in the preservation of human life.
A robotic platform, which can be viewed as a piece of equipment and thus does not suffer from the first aspect of cost, can provide security at a far lower price to the consumer of the service for the same and in many cases superior level of service.
Presently there is no such comprehensive security solution available on the market.
In a first embodiment, the present invention is a remotely controlled weaponized vehicle, comprising: a vehicular base comprising, a mobilized vehicular device, a first computing system, wherein the first computing system controlled the vehicle device, a weapon system attached to the vehicular base, wherein the weapon system comprises, a mounting system connected to the vehicular base, a weapon mount attached to the mounting system, a weapon attached to the weapon mount, an ammunition feeding system connected to the weapon, a second computing system, wherein the second computing system controls the mounting system, the weapon mount, the weapon, and the ammunition feeding system; a plurality of sensors collecting data from the vehicular base and the weapon system, wherein data collected from the plurality of sensors is sent to the first or the second computing systems.
In a second embodiment, the present invention is a weaponized vehicle with two separate control systems, comprising: a vehicle base having a first control system; and a weapon system having a second control system, wherein the first control system and the second control system are independently controlled and the weapon system comprises, a mounting base connected to the vehicle base, an articulating arm connected to the vehicle base, a weapon mount connected to the articulating arm; a plurality of sensors integrated into the vehicle base and the weapon system, wherein the plurality of sensors provide data to at least one of the first and second control systems; and an ammunition feeding system integrated into the vehicle base and the weapon system.
In a third embodiment, the present invention is a vehicle, comprising a vehicle with a power source and a first control system; a weapon system attached to the vehicle having a second control system and wherein the second control system is unidirectionally connected to the first control system and the second control system is able to communicate with the first control system; and an ammunition feeding system integrated into the vehicle and the weapon system; a plurality of sensors are connected to the first control system and the second control system.
Referring now to the drawings in which like reference numbers represent corresponding parts throughout:
As will be appreciated by one skilled in the art, aspects of the present invention may be embodied as a system, method or computer program product. Accordingly, aspects of the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, micro-code, etc.) or an embodiment combining software and hardware aspects may generally be referred to herein as a “circuit,” “module”, or “system.” Furthermore, aspects of the present invention may take the form of a computer program product embodied in one or more computer readable medium(s) having computer readable program code/instructions embodied thereon.
In one embodiment, the present invention relates to a semi-autonomous, remote-controllable mobile security robot (“platform”). More specifically, the invention relates to a relatively compact, armored all-terrain vehicle with a turret on top that's compatible with conventional firearms as well as certain less than lethal weapons. The system has some autonomous behavioral capability but is primarily controlled by a remote operator through a software system that connects the operator to the robot over the internet.
In another embodiment, the present invention relates to a semi-autonomous, remote-controllable mobile security robot. More specifically, the invention relates to a relatively compact, armored all-terrain vehicle with a turret on top that's compatible with conventional firearms as well as certain less than lethal weapons. The system has some autonomous behavioral capability but is primarily controlled by a remote operator through a software system that connects the operator to the robot over the internet.
The present invention seeks to provide a solution to these problems by creating a mobile, semi-autonomous, remote-controllable security platform. The platform is controlled by a remote operator via the internet and has some limited autonomous behaviors that it can be programmed to follow. In some embodiments, the remote-controlled security platform is mounted to a stationary object and is non-mobile but still provides the same targeting and controlling means.
The present invention also seeks to provide a solution by creating a mobile, semi-autonomous, remote-controllable security platform that has two control systems, the vehicle portion and the weapon portion of the overall design. The platform can be controlled by a remote operator via the internet, and also has the ability to be autonomous in nature. The vehicle portion of the device has its own control system, and the weapon portion has its own control system. These systems are separate to allow for one or both to autonomous and manually operated.
The platform makes use of various sensing devices (e.g., vision and image sensors, temperature sensors, proximity sensors, position sensors, motion sensors, audio sensors, and the like) that feed audio, video and data to a remote operator over an online protocol. The operator sees and hears from the viewpoint of the platform and can issue commands to it which are acted upon in real time. The platform can be made to execute basic sentry type tasks wherein it monitors a defined workspace and alerts the operator whenever certain conditions are encountered. These conditions can include unidentified humans or vehicles, ballistic discharges or explosions, or other programmed occurrences. Once alerted, the operator can immediately assume full control of the platform and act as necessary. The platform can also remain dormant in a waiting pattern until an alarm is triggered, at which point it will become active as well as alert the operator. In one embodiment, the device itself would have no offensive capabilities that are autonomous routines. The decision to shoot or take other aggressive action would remain solely in the hands of the human operator. The platform's primarily functional component is an adaptable turret, which may interchangeably and trivially equip various firearms, projectile shooters, and offensive add-ons.
The flowcharts and block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of the present invention. In this regard, each block in the flowcharts may represent a module, segment, or portion of instructions, which comprises one or more executable instructions for implementing the specified logical function(s). In some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the flowchart illustrations, and combinations of blocks in the flowchart illustrations, can be implemented by special purpose hardware-based systems that perform the specified functions or acts or carry out combinations of special purpose hardware and computer instructions.
It is understood in advance that although this disclosure includes a detailed description on cloud computing, implementation of the teachings recited herein are not limited to a cloud computing environment. Rather, embodiments of the present invention are capable of being implemented in conjunction with any other type of computing environment now known or later developed.
The system 100 contains a multilayer cybersecurity system as part of its computational architecture that is fundamental to its use. Two computing systems—one primary and one secondary. The secondary computing system is dedicated to the control and triggering of the weapon system 106, which contains offensive capability. The weapon system 106 is to be used wirelessly by actors over long range or short-range wireless networking methods. As part of this system, special authorization is required for activation and use of the weapon system 106. While the vehicle base 102 of the platform may be operated autonomously and remotely, the weapon system 106 may only be accessed remotely with a special authorization. This authorization may take many forms including but not limited to the use of additional private keys and user based encrypted authentication.
Vehicle Base 102 comprises computing device 110, sensors 112, power source 114, and control system 116. The vehicle base 102 may be a mobile vehicle, but it may also be replaced or removed if the weapon system 106 is mounted to a stationary object such as a building. In these instances, the vehicle base 102 is removed. In addition to the elements and components identified below, additional components such as defense systems may be integrated into the vehicle base 102. Such as, but not limited to, gas canisters, tasers, and the like which could be used to protect the vehicle base 102 in a non-lethal manner. In some embodiments, the vehicle base 102 is not present as the weapon system 106 is mounted directly to a stationary object such as a building or a surface.
Computing device 110 may be a management server, a web server, or any other electronic device or computing system capable of processing program instructions and receiving and sending data. In other embodiments, computing device 110 may be a laptop computer, tablet computer, netbook computer, personal computer (PC), a desktop computer, or any programmable electronic device capable of communicating with vehicle base 102, the weapon system 106, operator computing device 108, and the server 124 via network 104. Computing device 110 may include components, as depicted and described in further detail with respect to
Sensors 112 are used to collect specific data related to various aspects of the vehicle base 102. The sensors 112 may, but are not limited to, vision and image sensors, temperature sensors, proximity sensors, position sensors, motion sensors, audio sensors, cameras, microphones, motion sensors, positioning units, accelerometers, light and sound responsive sensors and the like. Based on the necessary data which needs to be collected related to the vehicle base 102, the sensors are designed to collect the data, and send the data to server 124 and operator computing device 108. The sensors 112 of the vehicle base 102 are able to communicate with the sensors 120 of the weapon system 106 and vice versa.
Power source 114 is based on the vehicle base 102 design. If the vehicle base is a drone, the power source may be a battery, if the vehicle base is an all-terrain vehicle, the power source may be a gasoline engine or a batter. The power source 114 is designed to provide adequate power for both the vehicle base 102 and the weapon system 106. In embodiments where the power source 114 is able to be recharged, the vehicle base 102 may have integrated renewable energy devices (e.g., solar panels) to recharge the battery.
Control system 116 provides for the control of the vehicle base 102. This would control the movement, direction, and other features which are integrated into the vehicle base 102 only. The vehicle base 102 controls do not provide control for the weapon system 106. Through the separation of these two systems the vehicle base 102 if autonomously controlled can never activate or use the weapon system 106.
Weapon system 106 comprises computing device 118, sensors 120, and controllers 122.
Computing device 118 may be a management server, a web server, or any other electronic device or computing system capable of processing program instructions and receiving and sending data. In other embodiments, computing device 110 may be a laptop computer, tablet computer, netbook computer, personal computer (PC), a desktop computer, or any programmable electronic device capable of communicating with weapon system 106, operator computing device 108, and the server 124 via network 104. Computing device 118 may include components, as depicted and described in further detail with respect to
Sensors 120 are used to collect specific data related to various aspects of the weapon system 106. The sensors 120 may, but are not limited to, vision and image sensors, temperature sensors, proximity sensors, position sensors, motion sensors, audio sensors, cameras, microphones, motion sensors, positioning units, accelerometers, light and sound responsive sensors and the like. Based on the necessary data which needs to be collected related to the weapon system 106, the sensors are designed to collect the data, and send the data to server 124 and operator computing device 108. The sensors 120 of the weapon system 106 are able to communicate with the sensors 112 of the vehicle base 102 and vice versa.
Controllers 122 provides for the control of the weapon system 106. This would control the movement, direction, and other features which are integrated into the vehicle base 102 only. The vehicle base 102 controls do not provide control for the weapon system 106. Through the separation of these two systems the vehicle base 102 if autonomously controlled can never activate or use the weapon system 106.
The weapon system 106 has an independent computing device 118 and controllers 122 to create a more secure system where the autonomous or controls of the vehicle base 102 are independent of the weapon system 106.
Operator computing device 108 may be a management server, a web server, or any other electronic device or computing system capable of processing program instructions and receiving and sending data as well as providing controls for the vehicle base 102 and the weapon system 106. In some embodiments, the operating computing device 108 has various controllers to control the vehicle base 102 or the weapon system 106. The operator computing device 108 can control the vehicle base 102 speed, direction, and movement and additional features of the vehicle base 102 such as lights, alarms, defense systems, shut down, and give commands to patrol, stop, return to a location, etc. The operator computing device 108 can control the weapon system 106 to articulate and move the mounting system to point at a target, “stick” the weapon on a target, cycle through targets, fire the weapon In other embodiments, operator computing device 108 may be a laptop computer, tablet computer, netbook computer, personal computer (PC), a desktop computer, or any programmable electronic device capable of communicating with vehicle base 102, the weapon system 106, and the server 124 via network 104. In other embodiments, operator computing device 106 may be a server computing system utilizing multiple computers as a server system, such as in a cloud computing environment. In one embodiment, operator computing device 106 represents a computing system utilizing clustered computers and components to act as a single pool of seamless resources. operator computing device 106 may include components, as depicted and described in further detail with respect to
The cameras (e.g., sensors 112 and 120) feeds are either processed simultaneously or stitched together and then processed depending on the embodiment. Furthermore, various sensors 112 and 120 including but not limited to accelerometers, ultrasound, light response, and sound are processed and provided to the operator computing device 108. Multiple accelerometers and sensors are used, to accurately define relative acceleration, velocity, and position at any given time along each computation cycle. Processing involves running a set of algorithms, machine learning algorithms and AI models on the images. For the embodiment specified the machine learning models and algorithms used are to identify unauthorized firearms, persons, vehicles, creatures, and other dangers or suspicious activity.
Machine learning algorithms are deployed to stitch together the data from the various sensors 120. Camera based computer vision algorithms keep track of suspicious activity (including but not limited to animals, humans, weapons) and report this activity to the operator. The operator then may decide to flag suspicious threats as non-suspicious for the machine learning algorithms to correct themselves for future operation, or the operator may inform authorities, or the operator may operate the machine—engaging the turret system and onboard communication devices to deal with the suspicious and threatening activity.
Network 102 may be a local area network (LAN), a wide area network (WAN) such as the Internet, any combination thereof, or any combination of connections and protocols that can support communications between vehicle base 102, weapon system 106, and operator computing device 108 and server 124. Network 102 may include wired, wireless, or fiber optic connections.
Server 124 may be a management server, a web server, or any other electronic device or computing system capable of processing program instructions and receiving and sending data. In other embodiments server 124 may be a laptop computer, tablet computer, netbook computer, personal computer (PC), a desktop computer, or any programmable electronic device capable of communicating via network 104 with the vehicle base 102, the weapon system 106, and the operator computing device 108. In one embodiment, server 124 may be a server computing system utilizing multiple computers as a server system, such as in a cloud computing environment. In one embodiment, server 124 represents a computing system utilizing clustered computers and components to act as a single pool of seamless resources. In the depicted embodiment database 126 is located on server 124. Server 124 may include components, as depicted and described in further detail with respect to
Operator computing device 108 may be a management server, a web server, or any other electronic device or computing system capable of processing program instructions and receiving and sending data. In other embodiments, operator computing device 108 may be a laptop computer, tablet computer, netbook computer, personal computer (PC), a desktop computer, or any programmable electronic device capable of communicating with vehicle base 102, the weapon system 106, and the server 124 via network 104. In other embodiments, operator computing device 106 may be a server computing system utilizing multiple computers as a server system, such as in a cloud computing environment. In one embodiment, operator computing device 106 represents a computing system utilizing clustered computers and components to act as a single pool of seamless resources operator computing device 106 may include components, as depicted and described in further detail with respect to
Database 114 may be a repository that may be written to and/or read by vehicle computing system 104, targeting program 110, weapon utilization program 112, and operating computing device 106. In one embodiment, database 114 is a database management system (DBMS) used to allow the definition, creation, querying, update, and administration of a database(s). In the depicted embodiment, database 114 resides on vehicle computing system 104. In other embodiments, database 114 resides on another server, or another computing device, provided that database 114 is accessible to vehicle computing system 104, targeting program 110, weapon utilization program 112, and operating computing device 106.
The vehicle system 202 provides for the base and mobility for the weapon system 106. The vehicle is capable of being remotely controlled and is controlled by the integrated control system 116. The vehicle is equipped with various sensors 112 and has an internal power source 114. In some embodiments, the vehicle may be equipped with a renewable power source, and include, integrated into the vehicle a means to recharge the power source (e.g., solar panels). This power source 114 is adequate to power both the vehicle and the weapon system 106.
Secured to the vehicle system 202 is a mounting system 212. The mounting system 212 provides for the mounting of the weapon mount system 218 as well as the means to articulate the weapon mount system 218 as needed by the design of the system as a whole. The mounting system 212 may be comprised of arm members, sets of gimbals (e.g., degree of freedom: roll, pitch, and yaw), joints, and the necessary actuators, motors, stabilizers, and electrical components to articulate the various members of the weapon mount system 218. The mounting system 212 is able to pan, tilt, and reposition the weapon as desired and based on the limitation of the overall design of the mounting system 212. The mounting system 212 is based on the firearm type. For example, if the firearm is a pistol, the weight and strength requirements of the mounting system 212 is reduced compared to a long rifle or a water hose setup. The mounting system 212 is designed and configured to accommodate the firearm type and the intended use of the device. In some embodiments, the mounting system 212 is interchangeable, with the ability to switch between different firearms with adapters and replaceable components. In some embodiments, the mounting system 212 provides full 6 degrees of freedom control through panning, tilting mechanism. The mounting system 212 is designed to accommodate all mechanical and electrical components.
A feeder system 216 is used to feed the ammunition to the weapon. The feeder system 216 is designed based on the weapon type and the ammunition type. The feeder system 216 is connected to the weapon mounting system 218. The feeder system 216 may be integrated into the mounting system 212 and the vehicle system 202. The feeder system 216 is integrated with one or more of the sensors 120 and in communication with the computing device 118 to collect data related to the quantity of the ammunition remaining, and issues with the feeding system 216 and to transmit data. There is also an external port, lid, or otherwise which enables safe refilling of the repository with more offensive materials.
The weapon mount system 218 provides for the attachment point of the weapon to the mounting system 212. The weapon system 218 may have its own adjustment members to provide the desired degrees of rotation and freedom of movement from the mount system 212 and includes the necessary actuators and motors. The weapon mount system 218 is in communication with various sensors 120, the computing device 118 and is mechanical connection with the feeder system 216 and the mounting system 212.
Depicted in
The base mount 302 provides for the foundation upon which the mounting system 212 is attached and also house the computing device 118 and provides a component to attach various sensors 120. The base mount 302 is designed based on the vehicle design or vehicle type. Sensors 120 exist around the stationary base of the weapon system 300, which serve to generate a 360-degree view around the weapon system 300, identifying and noting all targets with respect to a 3D cartesian plane in which the base mount 302 serves as the origin. Distances are approximated visually by using average human height, head size, and torso size - which are known entities. Targets and positions are communicated and identified in real time and a target queue is updated every computation cycle.
The repository 308 provides for a receptacle for the ammunition to be stored in, based on the ammunition type. For example, if the ammunition is bullets this would be a different container than if the ammunition was water. In some embodiments the ammunition storage container is contained within the base mount 302. In the depicted embodiment, the repository 308 is attached to the base mount 302. The feeder 310 provides for the connection between the repository 308 and the weapon 316. The feeder system is designed to feed the ammunition to the weapon 316 as needed. This can be, for example, a belt feed, a hose, or the like. In some embodiments, the feeder 310 is integrated into the repository 308 and the mounting system 212 so as to not obstruct the rotation and movement of the mounting system 212 and the weapon mount 314.
In some embodiments, there are a second set of mechanical adapters from the repository 308 to the weapon 316 through the feeder 310 and the mounting system 212. Several embodiments of this mechanical linkage for water transfer, ammunition transfer, and rubber bullet transfer are possible. The repository 308 is to house various ammunition, including but not limited to: bullets (rubber or otherwise), paintballs or similar, and water. In the case of a water gun, this adapter would be a hose and pump system. Similarly, in the case of a firearm a magazine specific adapter, and bullet chain or unordered to ordered bullet vacuuming mechanism would be used. Due to the mobility of the mounting system 212 and the direction of the feeder 310 (bottom up), the adapters for the weapon 316 to the repository 308 requires adapters to be flexible.
The mounting system 212 is connected to the weapon mount 314. The weapon mount 314 may have independent actuators, gimbals, or the like to provide another point of rotation from the mounting system 212. The weapon mount 314 is designed based on the weapon 316 type and is modified to accommodate the weapon 316. The trigger actuator 318 is integrated into the weapon mount 314 and is designed based on the weapon 316 type to adequately fire the weapon when the command is received. This may be a mechanical designed component or may be integrated into the weapon 316 depending on the weapon 316 type and limitations. For example, when a pistol is used, the trigger actuator is a mechanical device that would physically pull the trigger upon the command being received.
The weapon mount 314 is designed to accept conventional firearms chambered in the most common calibers, so that consumers of the platform may provide their own munitions. The adapter provides for various types of weapons to be fitted to the weapon mounting system 218 with minimal replacement of parts. In other embodiments different adapters may be provided to support a variety of offensive capability including but not limited to paintball guns, high pressure water guns, and taser prongs. In all embodiments the turret system contains actuating mechanisms to trigger the offensive capability. In some embodiments a camera or cameras and sensors may be attached to the turret to provide point of view for the operator.
Sensors 120 are and may be attached to the weapon 316, the weapon mount 314, the trigger actuator 318, the feeder 310, or the repository 308 to provide additional information based on the sensor 120 type. These sensors 120 are connected to the computing device 118 and are able to transmit the collected data to via the network 104.
In one embodiment, the vehicle base 102 is an all-terrain vehicle with an armored chassis and an interchangeable weapon system 106. The vehicle base has an all-electric drivetrain and batteries that are rechargeable with solar cells on the body. The vehicle base 102 contains a set of high-powered electric motors, electric motor drivers, batteries, battery regulatory circuitry, external charging capability, steering system, reinforced suspension, tires, and supplemental binding structures. The vehicle base 102 of the constitutes a primary part of the platforms' body, enabling rapid electrically driven movement. The vehicle base 102 is weatherproof, waterproof, and capable of driving the platform at high speeds and supporting large shifts in acceleration due to its electrical design.
In some embodiments, a sheath or holster may be incorporated into the design of the mounting system or the vehicle. The sheath is used when the weapon system is in a standby or inactive mode, so that weapon would be secured within the sheath for safety purposes. When holstered in the sheath, the weapon actuator or trigger system may be placed in a locked mode or an inactive mode so the weapon cannot be fired. This provides additional safety features in addition to locking the trigger actuator or locking the feeder so that the weapon cannot be loaded or fired.
In computing node 10 there is a computer system/server 12, which is operational with numerous other general purpose or special purpose computing system environments or configurations. Examples of well-known computing systems, environments, and/or configurations that may be suitable for use with computer system/server 12 include, but are not limited to, personal computer systems, server computer systems, thin clients, thick clients, hand-held or laptop devices, multiprocessor systems, microprocessor-based systems, set top boxes, programmable consumer electronics, network PCs, minicomputer systems, mainframe computer systems, and distributed cloud computing environments that include any of the above systems or devices, and the like.
Computer system/server 12 may be described in the general context of computer system executable instructions, such as program modules, being executed by a computer system. Generally, program modules may include routines, programs, objects, components, logic, data structures, and so on that perform particular tasks or implement particular abstract data types. Computer system/server 12 may be practiced in distributed cloud computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed cloud computing environment, program modules may be located in both local and remote computer system storage media including memory storage devices.
As shown in
Bus 18 represents one or more of any of several types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, and a processor or local bus using any of a variety of bus architectures. By way of example, and not limitation, such architectures include Industry Standard Architecture (ISA) bus, Micro Channel Architecture (MCA) bus, Enhanced ISA (EISA) bus, Video Electronics Standards Association (VESA) local bus, and Peripheral Component Interconnects (PCI) bus.
Computer system/server 12 typically includes a variety of computer system readable media. Such media may be any available media that is accessible by computer system/server 12, and it includes both volatile and non-volatile media, removable and non-removable media.
System memory 28 can include computer system readable media in the form of volatile memory, such as random-access memory (RAM) 30 and/or cache memory 32. Computer system/server 12 may further include other removable/non-removable, volatile/non-volatile computer system storage media. By way of example only, storage system 34 can be provided for reading from and writing to a nonremovable, non-volatile magnetic media (not shown and typically called a “hard drive”). Although not shown, a magnetic disk drive for reading from and writing to a removable, non-volatile magnetic disk (e.g., a “floppy disk”), and an optical disk drive for reading from or writing to a removable, non-volatile optical disk such as a CD-ROM, DVD-ROM or other optical media can be provided. In such instances, each can be connected to bus 18 by one or more data media interfaces. As will be further depicted and described below, memory 28 may include at least one program product having a set (e.g., at least one) of program modules that are configured to carry out the functions of embodiments of the invention.
Program/utility 40, having a set (at least one) of program modules 42, may be stored in memory 28 by way of example, and not limitation, as well as an operating system, one or more application programs, other program modules, and program data. Each of the operating system, one or more application programs, other program modules, and program data or some combination thereof, may include an implementation of a networking environment. Program modules 42 generally carry out the functions and/or methodologies of embodiments of the invention as described herein.
Computer system/server 12 may also communicate with one or more external devices 14 such as a keyboard, a pointing device, a display 24, etc.; one or more devices that enable a user to interact with computer system/server 12; and/or any devices (e.g., network card, modem, etc.) that enable computer system/server 12 to communicate with one or more other computing devices. Such communication can occur via Input/Output (I/O) interfaces 22. Still yet, computer system/server 12 can communicate with one or more networks such as a local area network (LAN), a general wide area network (WAN), and/or a public network (e.g., the Internet) via network adapter 20. As depicted, network adapter 20 communicates with the other components of computer system/server 12 via bus 18. It should be understood that although not shown, other hardware and/or software components could be used in conjunction with computer system/server 12. Examples, include, but are not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data archival storage systems, etc.
The computer readable storage medium can be a tangible device that can retain and store instructions for use by an instruction execution device. The computer readable storage medium may be, for example, but is not limited to, an electronic storage device, a magnetic storage device, an optical storage device, an electromagnetic storage device, a semiconductor storage device, or any suitable combination of the foregoing. A non-exhaustive list of more specific examples of the computer readable storage medium includes the following: a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), a static random access memory (SRAM), a portable compact disc read-only memory (CD-ROM), a digital versatile disk (DVD), a memory stick, a floppy disk, a mechanically encoded device such as punch-cards or raised structures in a groove having instructions recorded thereon, and any suitable combination of the foregoing. A computer readable storage medium, as used herein, is not to be construed as being transitory signals per se, such as radio waves or other freely propagating electromagnetic waves, electromagnetic waves propagating through a waveguide or other transmission media (e.g., light pulses passing through a fiber-optic cable), or electrical signals transmitted through a wire.
Computer readable program instructions described herein can be downloaded to respective computing/processing devices from a computer readable storage medium or to an external computer or external storage device via a network, for example, the Internet, a local area network, a wide area network and/or a wireless network. The network may comprise copper transmission cables, optical transmission fibers, wireless transmission, routers, firewalls, switches, gateway computers and/or edge servers. A network adapter card or network interface in each computing/processing device receives computer readable program instructions from the network and forwards the computer readable program instructions for storage in a computer readable storage medium within the respective computing/processing device.
Computer readable program instructions for carrying out operations of the present invention may be assembler instructions, instruction-set-architecture (ISA) instructions, machine instructions, machine dependent instructions, microcode, firmware instructions, state-setting data, or either source code or object code written in any combination of one or more programming languages, including an object oriented programming language such as Smalltalk, C++ or the like, and conventional procedural programming languages, such as the “C” programming language or similar programming languages. The computer readable program instructions may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider). In some embodiments, electronic circuitry including, for example, programmable logic circuitry, field-programmable gate arrays (FPGA), or programmable logic arrays (PLA) may execute the computer readable program instructions by utilizing state information of the computer readable program instructions to personalize the electronic circuitry, in order to perform aspects of the present invention.
Aspects of the present invention are described herein with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer readable program instructions.
These computer readable program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks. These computer readable program instructions may also be stored in a computer readable storage medium that can direct a computer, a programmable data processing apparatus, and/or other devices to function in a particular manner, such that the computer readable storage medium having instructions stored therein comprises an article of manufacture including instructions which implement aspects of the function/act specified in the flowchart and/or block diagram block or blocks.
The computer readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other device to cause a series of operational steps to be performed on the computer, other programmable apparatus or other device to produce a computer implemented process, such that the instructions which execute on the computer, other programmable apparatus, or other device implement the functions/acts specified in the flowchart and/or block diagram block or blocks.
Cloud computing is a model of service delivery for enabling convenient, on-demand network access to a shared pool of configurable computing resources (e.g., networks, network bandwidth, servers, processing, memory, storage, applications, virtual machines, and services) that can be rapidly provisioned and released with minimal management effort or interaction with a provider of the service. This cloud model may include at least five characteristics, at least three service models, and at least four deployment models.
Characteristics are as follows:
On-demand self-service: a cloud consumer can unilaterally provision computing capabilities, such as server time and network storage, as needed automatically without requiring human interaction with the service's provider.
Broad network access: capabilities are available over a network and accessed through standard mechanisms that promote use by heterogeneous thin or thick client platforms (e.g., mobile phones, laptops, and PDAs).
Resource pooling: the provider's computing resources are pooled to serve multiple consumers using a multi-tenant model, with different physical and virtual resources dynamically assigned and reassigned according to demand. There is a sense of location independence in that the consumer generally has no control or knowledge over the exact location of the provided resources but may be able to specify location at a higher level of abstraction (e.g., country, state, or datacenter).
Rapid elasticity: capabilities can be rapidly and elastically provisioned, in some cases automatically, to quickly scale out and rapidly released to quickly scale in. To the consumer, the capabilities available for provisioning often appear to be unlimited and can be purchased in any quantity at any time.
Measured service: cloud systems automatically control and optimize resource use by leveraging a metering capability at some level of abstraction appropriate to the type of service (e.g., storage, processing, bandwidth, and active user accounts). Resource usage can be monitored, controlled, and reported providing transparency for both the provider and consumer of the utilized service.
Service Models are as follows:
Software as a Service (SaaS): the capability provided to the consumer is to use the provider's applications running on a cloud infrastructure. The applications are accessible from various client devices through a thin client interface such as a web browser (e.g., web-based e-mail). The consumer does not manage or control the underlying cloud infrastructure including network, servers, operating systems, storage, or even individual application capabilities, with the possible exception of limited user-specific application configuration settings.
Platform as a Service (PaaS): the capability provided to the consumer is to deploy onto the cloud infrastructure consumer-created or acquired applications created using programming languages and tools supported by the provider. The consumer does not manage or control the underlying cloud infrastructure including networks, servers, operating systems, or storage, but has control over the deployed applications and possibly application hosting environment configurations.
Infrastructure as a Service (IaaS): the capability provided to the consumer is to provision processing, storage, networks, and other fundamental computing resources where the consumer is able to deploy and run arbitrary software, which can include operating systems and applications. The consumer does not manage or control the underlying cloud infrastructure but has control over operating systems, storage, deployed applications, and possibly limited control of select networking components (e.g., host firewalls).
Deployment Models are as follows:
Private cloud: the cloud infrastructure is operated solely for an organization. It may be managed by the organization or a third party and may exist on-premises or off-premises.
Community cloud: the cloud infrastructure is shared by several organizations and supports a specific community that has shared concerns (e.g., mission, security requirements, policy, and compliance considerations). It may be managed by the organizations or a third party and may exist on-premises or off-premises.
Public cloud: the cloud infrastructure is made available to the general public or a large industry group and is owned by an organization selling cloud services.
Hybrid cloud: the cloud infrastructure is a composition of two or more clouds (private, community, or public) that remain unique entities but are bound together by standardized or proprietary technology that enables data and application portability (e.g., cloud bursting for load-balancing between clouds).
A cloud computing environment is service oriented with a focus on statelessness, low coupling, modularity, and semantic interoperability. At the heart of cloud computing is an infrastructure comprising a network of interconnected nodes.
The computer readable storage medium can be a tangible device that can retain and store instructions for use by an instruction execution device. The computer readable storage medium may be, for example, but is not limited to, an electronic storage device, a magnetic storage device, an optical storage device, an electromagnetic storage device, a semiconductor storage device, or any suitable combination of the foregoing. A non-exhaustive list of more specific examples of the computer readable storage medium includes the following: a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), a static random access memory (SRAM), a portable compact disc read-only memory (CD-ROM), a digital versatile disk (DVD), a memory stick, a floppy disk, a mechanically encoded device such as punch-cards or raised structures in a groove having instructions recorded thereon, and any suitable combination of the foregoing. A computer readable storage medium, as used herein, is not to be construed as being transitory signals per se, such as radio waves or other freely propagating electromagnetic waves, electromagnetic waves propagating through a waveguide or other transmission media (e.g., light pulses passing through a fiber-optic cable), or electrical signals transmitted through a wire.
Computer readable program instructions described herein can be downloaded to respective computing/processing devices from a computer readable storage medium or to an external computer or external storage device via a network, for example, the Internet, a local area network, a wide area network and/or a wireless network. The network may comprise copper transmission cables, optical transmission fibers, wireless transmission, routers, firewalls, switches, gateway computers and/or edge servers. A network adapter card or network interface in each computing/processing device receives computer readable program instructions from the network and forwards the computer readable program instructions for storage in a computer readable storage medium within the respective computing/processing device.
Computer readable program instructions for carrying out operations of the present invention may be assembler instructions, instruction-set-architecture (ISA) instructions, machine instructions, machine dependent instructions, microcode, firmware instructions, state-setting data, or either source code or object code written in any combination of one or more programming languages, including an object oriented programming language such as Smalltalk, C++ or the like, and conventional procedural programming languages, such as the “C” programming language or similar programming languages. The computer readable program instructions may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider). In some embodiments, electronic circuitry including, for example, programmable logic circuitry, field-programmable gate arrays (FPGA), or programmable logic arrays (PLA) may execute the computer readable program instructions by utilizing state information of the computer readable program instructions to personalize the electronic circuitry, to perform aspects of the present invention.
Aspects of the present invention are described herein with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer readable program instructions.
These computer readable program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks. These computer readable program instructions may also be stored in a computer readable storage medium that can direct a computer, a programmable data processing apparatus, and/or other devices to function in a particular manner, such that the computer readable storage medium having instructions stored therein comprises an article of manufacture including instructions which implement aspects of the function/act specified in the flowchart and/or block diagram block or blocks.
The computer readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other device to cause a series of operational steps to be performed on the computer, other programmable apparatus or other device to produce a computer implemented process, such that the instructions which execute on the computer, other programmable apparatus, or other device implement the functions/acts specified in the flowchart and/or block diagram block or blocks.
The flowchart and block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of instructions, which comprises one or more executable instructions for implementing the specified logical function(s). In some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems that perform the specified functions or acts or carry out combinations of special purpose hardware and computer instructions.
Present invention: should not be taken as an absolute indication that the subject matter described by the term “present invention” is covered by either the claims as they are filed, or by the claims that may eventually issue after patent prosecution; while the term “present invention” is used to help the reader to get a general feel for which disclosures herein that are believed as maybe being new, this understanding, as indicated by use of the term “present invention,” is tentative and provisional and subject to change over the course of patent prosecution as relevant information is developed and as the claims are potentially amended.
The foregoing descriptions of various embodiments have been presented only for purposes of illustration and description. They are not intended to be exhaustive or to limit the present invention to the forms disclosed. Accordingly, many modifications and variations of the present invention are possible in light of the above teachings will be apparent to practitioners skilled in the art. Additionally, the above disclosure is not intended to limit the present invention. In the specification and claims the term “comprising” shall be understood to have a broad meaning similar to the term “including” and will be understood to imply the inclusion of a stated integer or step or group of integers or steps but not the exclusion of any other integer or step or group of integers or steps. This definition also applies to variations on the term “comprising” such as “comprise” and “comprises”.
Although various representative embodiments of this invention have been described above with a certain degree of particularity, those skilled in the art could make numerous alterations to the disclosed embodiments without departing from the spirit or scope of the inventive subject matter set forth in the specification and claims. Joinder references (e.g., attached, adhered, joined) are to be construed broadly and may include intermediate members between a connection of elements and relative movement between elements. As such, joinder references do not necessarily infer those two elements are directly connected and in fixed relation to each other. Moreover, network connection references are to be construed broadly and may include intermediate members or devices between network connections of elements. As such, network connection references do not necessarily infer those two elements are in direct communication with each other. In some instances, in methodologies directly or indirectly set forth herein, various steps and operations are described in one possible order of operation, but those skilled in the art will recognize that steps and operations may be rearranged, replaced or eliminated without necessarily departing from the spirit and scope of the present invention. It is intended that all matter contained in the above description or shown in the accompanying drawings shall be interpreted as illustrative only and not limiting. Changes in detail or structure may be made without departing from the spirit of the invention as defined in the appended claims.
Although the present invention has been described with reference to the embodiments outlined above, various alternatives, modifications, variations, improvements and/or substantial equivalents, whether known or that are or may be presently foreseen, may become apparent to those having at least ordinary skill in the art. Listing the steps of a method in a certain order does not constitute any limitation on the order of the steps of the method.
Accordingly, the embodiments of the invention set forth above are intended to be illustrative, not limiting. Persons skilled in the art will recognize that changes may be made in form and detail without departing from the spirit and scope of the invention. Therefore, the invention is intended to embrace all known or earlier developed alternatives, modifications, variations, improvements and/or substantial equivalents.
