Engine Control By Lock Change Files

A system controls engine power by self-executing contracts with an authority. A distributed method is performed at a plurality of authority apparatus, power level lock change file servers, and engine control units. Each authority apparatus provides a policy object for each Engine Control Unit (ECU). An authority sets power levels for self-executing compliance with policy constraints. A power level lock change file (LockChangeFile) server checks against date time constraints and geo-location scope by its authorities. An ECU receives a power level token when time and location constraint(s) by at least one authority is within scope. A distributed method includes receiving space time constraints and determining a policy object and Authoritative LockChangeFile; receiving date, time, and location indicia from an ECU; determining the lowest power level consistent with the LockChangeFile; and requesting a new power level token by transmitting an identity credential, time and location indicia when needed.

PRIOR ART

As is known, public key cryptography enables self-verifying authentication. As is known content addressable storage is commercially available based on hashes of the data. As is known, date, time, and location information can be obtained from terrestrial cellular telephone base stations, satellite navigation services, celestial and inertial navigation systems, and from solid state clocks and accelerometers.

BACKGROUND OF THE INVENTION

As is known, modern electrical and internal combustion motors used for transportation depend on engine control units to adapt to load and environmental condition for optimum performance and efficiency. However, maintenance and inspection schedules are more what you might call a goal or guideline. What is needed is a way to enforce contractual agreements for maintenance, recalls, insurance policies, leasing terms, licensing, and restrictions on geo-location on engines that have inherent independence of mobility in time and in space.

SUMMARY OF THE INVENTION

A system provides engine power control by a lock control file governed by self-executing contracts with at least one authority.

The system includes a distributed method performed ata plurality of authority apparatus,a plurality of power lock change file servers,a plurality of engine control units, anda network.

Each authority apparatus provides an authority policy object which is a component of a power level lock change file for each engine control unit. The files and their component objects are stored in distributed media for redundancy and availability through network communications. The power level lock change file most recently computed by any authority server includes links to each previous version of the power level lock change file and is Authoritative with respect to its engine control unit.

An authority console enables setting of power levels according to time and location for self-executing compliance with constraints including insurance policies, maintenance and recall policies, financial terms and conditions, ownership, and restriction to geo-location policies.

In an embodiment, power level lock change files include a plurality of objects stored in content addressable media according to their hash.

In an embodiment, a hierarchical object locator provides improved performance in retrieving distributed objects which are addressable by hashed content by dynamically determining the access method with least latency at that time to the Authoritative power level lock change file and its component authority policy objects.

A power level lock change file server determines a power level token for an engine control unit when its time and location indicia is checked against the space time constraints established by its authorities. A power level lock change file is generated including a hierarchical object linking to its previous power level lock change file version and a hierarchical object linking to each authority which has a self-executing policy object for the time and location of the engine control unit.

The lowest power level agreed among the authorities may only be for test, or for transit to inspection or maintenance or for acceleration and climb for the reported time and location.

In an embodiment, a multi-engine configuration may receive a joint power level token causing yaw away from a sensitive location when approaching a geo-location boundary.

An engine control unit determines a power level from its time and location according to a power level token. A power level token is received from a power level lock change server when time and location constraint(s) by at least one authority is within scope.

The power level token is received from a power level lock change file server whenever the engine control unit provides its authenticated time and location indicia.

The distributed method includesReceiving space time constraints from each authority for each engine control unit and determining a policy object and Authoritative power level lock change file;Determining an access method for least latency to the Authoritative power level lock change file and its component objects;Receiving time and location indicia from an engine control unit; Determining the lowest power level consistent with the Authoritative power level lock change file;Generating and transmitting a power level token to the engine control unit;Determining time and location at an engine control unit;Applying a power level permitted by a stored power level token on the condition that the power level lock change file in store is still Authoritative;Requesting a new power level token by transmitting an identity credential, time and location indicia in a request; andDisplaying messages to engine operator and to authority official when a power level is changed, an action is required, or a time and location are out of compliance.

DETAILED DESCRIPTION OF THE INVENTION

The invention includesa plurality of authority apparatus, a plurality of power lock change file servers, a plurality of engine control units, and a network.

The invention includes distributed methods performed among the authority apparatuses, the power level lock change file server, and the engine control units which transform time and location indicia data into power levels emitted by engines including: Receiving date time and location constraints and determining a policy object and Authoritative LockChangeFile;Receiving date, time, and location indicia from an ECU;Determining the lowest power level consistent with the LockChangeFile;Requesting a new power level token by transmitting an identity credential, time and location indicia when needed.

Referring now to the Figures,FIGS.1-4disclose exemplary embodiments of processors and computing environments which enable performance of methods.FIG.1is a pictorial representation of a network of data processing systems in which illustrative embodiments may be implemented;FIG.2is a diagram of a data processing system in which illustrative embodiments may be implemented;FIG.3is a diagram illustrating a cloud computing environment in which illustrative embodiments may be implemented;FIG.4is a diagram illustrating an example of abstraction layers of a cloud computing environment in accordance with an illustrative embodiment;

FIG.5is a block diagram of a control system for engine power level by authorities. A system500includes:

a plurality of authority servers560,a plurality of power level lock change file servers574-576,a plurality of engine control units583-587,a network575communicatively coupling the above subsystems, and in an embodiment, further including a hierarchical object locator561.

FIG.6is a block diagram of authority server600. An exemplary authority server620includesA processor and media module621;An identity credential622;A date time constraint module623;A power level lock change file(s) store624;A network communication transceiver625;A geo-location scope module626;An authority console627;A power level policy module629, and in an embodiment, further including an authoritypolicy object store628;All621-628mutually coupled.

FIG.7is a block diagram of a power level lock change file server700. An exemplary power level lock change file server740includesA processor and media module741,An identity credential(s) store742,A hash module743,A power level lock change file(s) store744,A network communication transceiver745,A winged team ECU groups store747;A power level token generator749, and in an embodiment, further including an hierarchical object(s) generator748,All mutually coupled.

FIG.8is a block diagram of an engine control unit800. An exemplary engine control unit830includesA processor and media module831,An identity credential832,A time and location determination module833,A power level lock change file store834,A multi-band communication transceiver835,An operator user interface837;A power level token store839, and in an embodiment,And further including a thermo-electric power module836, and in an embodiment, further including a warmup restart module838,All mutually coupled.

FIGS.9-11illustrate exemplary flow charts of methods distributed among the authority apparatuses, the power level lock change file server, and the engine control units which transform time and location indicia data into power levels emitted by engines including: Receiving space time constraints and determining a policy object and Authoritative LockChangeFile;Receiving date, time, and location indicia from an ECU;Determining the lowest power level consistent with the LockChangeFile;Requesting a new power level token by transmitting an identity credential, time and location indicia when needed. The references are related to the exemplary embodiments below.

One aspect of the invention is illustrated as an engine power control system500including:A plurality of authority apparatuses562-568;A plurality of Engine Control Units583-587; andA plurality of power level lock change file servers574-576; and a Network575communicatively coupling all the apparatuses.

In an embodiment, the system also includes: at least one hierarchical object locator561whereby content addressable file objects are retrievable by an access method with least latency.

In an embodiment, the system also includes: at least one location and time determination service provider including but not limited to a global positioning service, a cellular radio service, a wi-fi network, a radio beacon service, a satellite navigation service, an inertial navigation service, and electric beacon navigation service.

In an embodiment, said authority apparatus600includes:An authority policy object store628encoded byAn identity credential622;A range of date time constraints623for which the authority permits each engine power level;A range of geo-location zones626within which the authority permits each engine power level;An authentication by the authority;A hash of the current power level lock change file;A link to the location of supporting authority policy objects;A message to be displayed when permission is denied; andA link to a hash of each prior authority policy object and of each prior power level lock change file.

In an embodiment, said power level lock change file server700includes:A network communication transceiver module745to receive power level requests from a first engine control unit and transmit power level tokens;An authentication module to validate the identity credential transmitted from an engine control unit;A hash module743;A store of power level Lock Change Files744;A module to determine the content addressable most recently computed Engine Lock Change File for the engine control unit stored by an Authority;

A module to retrieve each hierarchical object for the Engine Lock Change File from each Authority;A store of wing teamed ecu groups747;A hierarchical object(s) generator748;A module to generate a power level token749, by logically combining the policy objects of all Authorities and provide the power level token to the requesting ECU;A module to transmit a message to an operator user interface with the result of determining a power level token. Such a message may indicate payments, inspections, or maintenance services are due. Power levels consistent with testing, or taxiing may be enabled for a limited time or distance.

In an embodiment, said plurality of authority apparatuses includes at least one maintenance policy whereby failure to log completion of scheduled service causes a power level to be lower than acceleration and climb for a location; a recall policy whereby at least one of a recall notice and failure to record it triggers a self-executing compliance a power level; and at least one of:insurance policy, financial terms and conditions, ownership, andlicensing validation, and restriction to geo-location policies. Rather than contractual obligations for payments, inspections, and maintenance enforced by legal documents, the available power levels reflect the constraints embedded in self-executing objects.

In an embodiment, said plurality of authority servers also includes: a restricted geo-location boundary yaw activation geo-location scope626whereby power levels are overridden for engines within a glide range of a restricted geo-location.

In an embodiment, said engine control unit includes:An identity credential832;A time and location determination module833; andA multi-band communications transceiver835. The time and location determination module may operate internally or obtain reference data from satellites, cellular base stations, radio navigation or celestial navigation services.

In an embodiment, said engine control unit also includes:A thermo-electric power module836;A power level token store839; andA power level lock change file store834. The thermo-electric power module converts heat to electrical power for communications, determining time and location indicia, and transmitting a request for a power level token whenever the engine starts.

In an embodiment, said engine control unit also includes a warmup restart module838;A processor and media831; andAn operator user interface827.

Another aspect of the invention is a method of operation900for a system having the processes at an authority server:Receiving power level constraints and conditions for an engine control unit (ECU)910;Determining a power level policy which expresses the power level for the ECU920;Determining a new content hash for the engine lock change file including the authority policy object930;Storing the authority policy object into a plurality of distributed media940;Updating the hierarchical object locator with the content hash of the authority policy object950;Including the location of the previous authority policy object in the power level lock change file960; and,Updating the power level lock change file server with a new content hash for the ECU990.

In an embodiment the method also includes at a power level lock change file server,Receiving an updated content hash for an engine lock change file from an authority server1010;Storing the policy object for each authority in hierarchical object locator1020;Receiving a request for an updated power level token from an engine control unit1030;Determining an Authoritative lock change file for the engine control unit1050;Retrieving from the hierarchical object locator the access method with least latency to the current policy object from each authority1060;

Determining an updated power level token compliant with all of the restrictions of all the authorities1070;Transmitting a message with the result of the determination to an operator console1080; andTransmitting the updated power level token to the engine control unit1090.

In an embodiment the method also includesA process1100at an engine control unit,Determining a current time and location1110;Combining an identity credential with current time and location indicia1120;Reading a stored power level token1130;Transmitting to a power level lock file server a request for an updated power level token1140;Receiving and storing an updated power level token1150;Displaying a power level status message to an operator console1160; andAdjusting power output to comply with current time and location1190.

Another aspect of the invention is a plurality of engine control units800including: a first engine control unit830coupled to a portside engine and a second engine control unit coupled to a starboardside engine.

In an embodiment, the first engine control unit (ECU) includes:A location and time determination module833;An identity credential module832;A multi-band communication transceiver835; andA power level token store839.

In an embodiment, the first engine control unit (ECU) also includes:A power level token decoder;A power level output control valve: andAn interface to an operator console837.

In an embodiment, the first engine control unit (ECU) also includes: An engine warmup restart module838; A thermoelectric power generator836: and A power level token request module.

In an embodiment, the second ECU includes a configuration store which distinguishes it as one of a port-side engine and a starboard-side engine whereby a joint power level token overrides the power level in at least one engine.

In an embodiment, the location and time determination module determines a vector of travel direction.

In an embodiment, the plurality of engine control units cause a yaw force by differential power output levels applied to the portside engine and to the starboardside engine until the vector of travel direction avoids inertia into a restriction in geo-location. Advantageously such a system provides a long-sought solution of a safety problem by causing any powered flight to steer away from an outer boundary of a restricted geo-location and any unpowered flight to lose momentum outside the inner sensitive area of a restricted geo-location.

In conclusion, the invention may be easily distinguished from simple on-off controls by its enabling power levels for test, taxi, and transit to service centers. The invention is distinguished by controlling by geo-location in addition to date and time. The invention is distinguished by robustness in distributed objects and servers vs centralized control. The invention is distinguished by initialization by engine heat and independence from external power. The invention is distinguished by potentially causing yaw when nearing the boundary of a restricted geo-location area which operates against coasting or gliding into a protected space during a sensitive time.

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. A computer readable specification may be transformed into a specialized hardware processor such as for determining a hash, or a public-private key pair by a synthesis product configuring an IP core such as an ARM design architecture.

With reference now to the figures, and in particular, with reference toFIGS.1-4, diagrams of data processing environments are provided in which illustrative embodiments may be implemented. It should be appreciated thatFIGS.1-4are only meant as examples and are not intended to assert or imply any limitation with regard to the environments in which different embodiments may be implemented. Many modifications to the depicted environments may be made.

FIG.1depicts a pictorial representation of a network of data processing systems in which illustrative embodiments may be implemented. Network data processing system100is a network of computers, data processing systems, and other devices in which the illustrative embodiments may be implemented. Network data processing system100contains network102, which is the medium used to provide communications links between the computers, data processing systems, and other devices connected together within network data processing system100. Network102may include connections, such as, for example, wire communication links, wireless communication links, and fiber optic cables. Also, network102may be, for example, a private network, a public network, a hybrid network, a corporate network, or the like.

In the depicted example, server104and server106connect to network102, along with storage108. Server104and server106may be, for example, server computers with high-speed connections to network102. Also, it should be noted that server104and server106may represent computing nodes in a cloud environment that manages analysis services for one or more networks and their respective resources. Alternatively, server104and server106may represent clusters of servers in a data center. Further, server104and server106may provide information, such as, for example, programs, application, updates, patches, and the like, to the registered client data processing systems.

Client110, client112, and client114also connect to network102. In this example, client110is shown as desktop or personal computer with wire communication links to network102. However, it should be noted that client110is an example only and may represent other types of data processing systems, such as, for example, a video stream capture, a hub, a credential scanner, an optical scanner, a radio transceiver, a bridge, a laptop computer, handheld computer, smart phone, smart watch, smart television, or the like, with wire or wireless communication links to network102. A user of client110may utilize client110to access and utilize the resources and/or services provided by client112and client114. Resources may include, for example, data, documents, software such applications and programs, hardware such as processors, memory, and storage, and the like. Services may include any type of online service, such as, for example, identity services, physical access control services, motor control, storage management, network optimization, version control, network latency reduction, banking services, financial services, governmental services, insurance services, entertainment services, search services, reservation services, and the like. In addition, it should be noted that client110may represent a plurality of different client devices corresponding to a plurality of different users.

Clients112and114are registered clients of server104and server106. In this example, client112and client114each represents a data processing system, such as a sever computer, that provides the resources and services of network102. Further, it should be noted that client112and client114may each represent a plurality of data processing systems corresponding to one or more organizations, enterprises, institutions, agencies, and the like.

Storage108is a network storage device capable of storing any type of data in a structured format or an unstructured format. In addition, storage108may represent a plurality of network storage devices. Further, storage108may store identifiers and network addresses for a plurality of different network security servers, identifiers, and network addresses for a plurality of different registered client devices, identifiers for a plurality of different users, and the like. Furthermore, storage unit108may store identities, IP and URL addresses, policies, and the like. Moreover, storage unit108may store other types of data, such as authentication or credential data that may include user names, passwords, images, and biometric data associated with network users, system administrators, and security analysts, for example.

In addition, it should be noted that network data processing system100may include any number of additional servers, clients, storage devices, and other devices not shown. Program code located in network data processing system100may be stored on a computer readable storage medium and downloaded to a computer or other data processing device for use. For example, program code may be stored on a computer readable storage medium on network security server104and downloaded to client112over network102for use on client112.

In the depicted example, network data processing system100may be implemented as a number of different types of communication networks, such as, for example, the Internet, an intranet, a local area network, a wide area network, a telecommunications network, or any combination thereof.FIG.1is intended as an example only, and not as an architectural limitation for the different illustrative embodiments.

With reference now toFIG.2, a diagram of a data processing system is depicted in accordance with an illustrative embodiment. Data processing system200is an example of a computer, such as server104inFIG.1, in which computer readable program code or instructions implementing processes of illustrative embodiments may be located. In this illustrative example, data processing system200includes communications fabric202, which provides communications between processor unit204, volatile storage206, persistent storage208, communications unit210, input/output unit212, and display214.

Processor unit204serves to execute instructions for software applications and programs that may be loaded into volatile storage206. Processor unit204may be a set of one or more hardware processor devices or may be a multi-core processor, depending on the particular implementation.

Program code244is located in a functional form on computer readable media246that is selectively removable and may be loaded onto or transferred to data processing system200for running by processor unit204. Program code244and computer readable media246form computer program product248. In one example, computer readable media246may be computer readable storage media250or computer readable signal media252. Computer readable storage media250may include, for example, an optical or magnetic disc that is inserted or placed into a drive or other device that is part of persistent storage208for transfer onto a storage device, such as a hard drive, that is part of persistent storage208. Computer readable storage media250also may take the form of a persistent storage, such as a hard drive, a thumb drive, or a flash memory that is connected to data processing system200. In some instances, computer readable storage media250may not be removable from data processing system200.

Alternatively, program code244may be transferred to data processing system200using computer readable signal media252. Computer readable signal media252may be, for example, a propagated data signal containing program code244. For example, computer readable signal media252may be an electro-magnetic signal, an optical signal, and/or any other suitable type of signal. These signals may be transmitted over communication links, such as wireless communication links, an optical fiber cable, a coaxial cable, a wire, and/or any other suitable type of communications link. In other words, the communications link and/or the connection may be physical or wireless in the illustrative examples. The computer readable media also may take the form of non-tangible media, such as communication links or wireless transmissions containing the program code.

In some illustrative embodiments, program code244may be downloaded over a network to persistent storage208from another device or data processing system through computer readable signal media252for use within data processing system200. For instance, program code stored in a computer readable storage media in a data processing system may be downloaded over a network from the data processing system to data processing system200. The data processing system providing program code244may be a server computer, a client computer, or some other device capable of storing and transmitting program code244.

As another example, a computer readable storage device in data processing system200is any hardware apparatus that may store data. Volatile storage206, persistent storage208, and computer readable storage media250are examples of physical storage devices in a tangible form.

It is understood 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, illustrative embodiments are capable of being implemented in conjunction with any other type of computing environment now known or later developed. Cloud computing is a model of service delivery for enabling convenient, on-demand network access to a shared pool of configurable computing resources, such as, for example, networks, network bandwidth, servers, processing, memory, storage, applications, virtual machines, and services, which 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.

The characteristics may include, for example, on-demand self-service, broad network access, resource pooling, rapid elasticity, and measured service. On-demand self-service allows a cloud consumer to 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 provides for capabilities that are available over a network and accessed through standard mechanisms that promote use by heterogeneous thin or thick client platforms, such as, for example, mobile phones, laptops, and personal digital assistants. Resource pooling allows the provider's computing resources to be 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, such as, for example, country, state, or data center. Rapid elasticity provides for capabilities that 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 allows cloud systems to automatically control and optimize resource use by leveraging a metering capability at some level of abstraction appropriate to the type of service, such as, for example, 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 may include, for example, Software as a Service (Saas), Platform as a Service (PaaS), and Infrastructure as a Service (laaS). Software as a Service is the capability provided to the consumer 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 is the capability provided to the consumer 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 is the capability provided to the consumer 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, such as, for example, host firewalls.

Deployment models may include, for example, a private cloud, community cloud, public cloud, and hybrid cloud. A private cloud is a cloud infrastructure operated solely for an organization. The private cloud may be managed by the organization or a third party and may exist on-premises or off-premises. A community cloud is a cloud infrastructure shared by several organizations and supports a specific community that has shared concerns, such as, for example, mission, security requirements, policy, and compliance considerations. The community cloud may be managed by the organizations or a third party and may exist on-premises or off-premises. A public cloud is a cloud infrastructure made available to the general public or a large industry group and is owned by an organization selling cloud services. A hybrid cloud is a cloud infrastructure composed of two or more clouds, such as, for example, private, community, and public clouds, which remain as unique entities, but are bound together by standardized or proprietary technology that enables data and application portability, such as, for example, cloud bursting for load-balancing between clouds.

With reference now toFIG.3, a diagram illustrating a cloud computing environment is depicted in which illustrative embodiments may be implemented. In this illustrative example, cloud computing environment300includes a set of one or more cloud computing nodes310with which local computing devices used by cloud consumers, such as, for example, local computing device320A-N may communicate. Cloud computing nodes310may be, for example, server104, server106, client112, and client114inFIG.1. A local computing device of local computing devices320A-320N may be, for example, client110inFIG.1. Local computing devices may be stationary such as sensors and may be mobile such as vehicles, hand-carried, and body-worn/implanted.

Cloud computing nodes310may communicate with one another and may be grouped physically or virtually into one or more networks, such as private, community, public, or hybrid clouds as described hereinabove, or a combination thereof. This allows cloud computing environment300to offer infrastructure, platforms, and/or software as services for which a cloud consumer does not need to maintain resources on a local computing device, such as local computing devices320A-N. It is understood that the types of local computing devices320A-N are intended to be illustrative only and that cloud computing nodes310and cloud computing environment300can communicate with any type of computerized device over any type of network and/or network addressable connection using a web browser or Internet Protocol, for example.

With reference now toFIG.4, a diagram illustrating abstraction model layers is depicted in accordance with an illustrative embodiment. The set of functional abstraction layers shown in this illustrative example may be provided by a cloud computing environment, such as cloud computing environment300inFIG.3. It should be understood in advance that the components, layers, and functions shown inFIG.4are intended to be illustrative only and embodiments of the invention are not limited thereto. As depicted, the following layers and corresponding functions are provided.

Abstraction layers of a cloud computing environment400include hardware and software layer402, virtualization layer404, management layer406, and workloads layer408. Hardware and software layer402includes the hardware and software components of the cloud computing environment. The hardware components may include, for example, mainframes410, RISC (Reduced Instruction Set Computer) architecture-based servers412, servers414, blade servers416, storage devices418, and networks and networking components420. In some illustrative embodiments, software components may include, for example, network application server software422and database software424.

Virtualization layer404provides an abstraction layer from which the following examples of virtual entities may be provided: virtual servers426; virtual storage428; virtual networks430, including virtual private networks; virtual applications and operating systems432; and virtual clients434.

Workloads layer408provides examples of functionality for which the cloud computing environment may be utilized. Example workloads and functions, which may be provided by workload layer408, may include mapping and navigation446, software development and lifecycle management448, virtual classroom education delivery450, data analytics processing452, transaction processing454, and security management456.

The systems and methods described herein may be embodied in other specific forms without departing from the characteristics thereof. Although the examples provided herein relate to providing interactive content for display, the systems and methods described herein can include applied to other environments in which data included in a log database used and compared to data corresponding to previous requests for content and responsive to determining a change in the data, identifying one or more content elements to which to attribute the credit for the change. The foregoing implementations are illustrative rather than limiting of the described systems and methods. Scope of the systems and methods described herein is thus indicated by the appended claims, rather than the foregoing description, and changes that come within the meaning and range of equivalency of the claims are embraced therein.