U.S. Pat. No. 12,407,883

DETAILED DESCRIPTION

The present disclosure will now be described more fully hereinafter with reference to the accompanying drawings, which form a part hereof, and which show, by way of non-limiting illustration, certain example embodiments. Subject matter may, however, be embodied in a variety of different forms and, therefore, covered or claimed subject matter is intended to be construed as not being limited to any example embodiments set forth herein; example embodiments are provided merely to be illustrative. Likewise, a reasonably broad scope for claimed or covered subject matter is intended. Among other things, for example, subject matter may be embodied as methods, devices, components, or systems. Accordingly, embodiments may, for example, take the form of hardware, software, firmware or any combination thereof (other than software per se). The following detailed description is, therefore, not intended to be taken in a limiting sense.

Throughout the specification and claims, terms may have nuanced meanings suggested or implied in context beyond an explicitly stated meaning. Likewise, the phrase “in one embodiment” as used herein does not necessarily refer to the same embodiment and the phrase “in another embodiment” as used herein does not necessarily refer to a different embodiment. It is intended, for example, that claimed subject matter include combinations of example embodiments in whole or in part.

In general, terminology may be understood at least in part from usage in context. For example, terms, such as “and”, “or”, or “and/or.” as used herein may include a variety of meanings that may depend at least in part upon the context in which such terms are used. Typically, “or” if used to associate a list, such as A, B or C, is intended to mean A, B, and C, here used in the inclusive sense, as well as A, B or C, here used in the exclusive sense. In addition, the term “one or more” as used herein, depending at least in part upon context, may be used to describe any feature, structure, or characteristic in a singular sense or may be used to describe combinations of features, structures or characteristics in a plural sense. Similarly, terms, such as “a,” “an,” or “the,” again, may be understood to convey a singular usage or to convey a plural usage, depending at least in part upon context. In addition, the term “based on” may be understood as not necessarily intended to convey an exclusive set of factors and may, instead, allow for existence of additional factors not necessarily expressly described, again, depending at least in part on context.

The present disclosure is described below with reference to block diagrams and operational illustrations of methods and devices. It is understood that each block of the block diagrams or operational illustrations, and combinations of blocks in the block diagrams or operational illustrations, can be implemented by means of analog or digital hardware and computer program instructions. These computer program instructions can be provided to a processor of a general purpose computer to alter its function as detailed herein, a special purpose computer, ASIC, or other programmable data processing apparatus, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, implement the functions/acts specified in the block diagrams or operational block or blocks. In some alternate implementations, the functions/acts noted in the blocks can occur out of the order noted in the operational illustrations. For example, two blocks shown in succession can in fact be executed substantially concurrently or the blocks can sometimes be executed in the reverse order, depending upon the functionality/acts involved.

For the purposes of this disclosure a non-transitory computer readable medium (or computer-readable storage medium/media) stores computer data, which data can include computer program code (or computer-executable instructions) that is executable by a computer, in machine readable form. By way of example, and not limitation, a computer readable medium may include computer readable storage media, for tangible or fixed storage of data, or communication media for transient interpretation of code-containing signals. Computer readable storage media, as used herein, refers to physical or tangible storage (as opposed to signals) and includes without limitation volatile and non-volatile, removable and non-removable media implemented in any method or technology for the tangible storage of information such as computer-readable instructions, data structures, program modules or other data. Computer readable storage media includes, but is not limited to, RAM, ROM, EPROM, EEPROM, flash memory or other solid state memory technology, optical storage, cloud storage, magnetic storage devices, or any other physical or material medium which can be used to tangibly store the desired information or data or instructions and which can be accessed by a computer or processor.

For the purposes of this disclosure the term “server” should be understood to refer to a service point which provides processing, database, and communication facilities. By way of example, and not limitation, the term “server” can refer to a single, physical processor with associated communications and data storage and database facilities, or it can refer to a networked or clustered complex of processors and associated network and storage devices, as well as operating software and one or more database systems and application software that support the services provided by the server. Cloud servers are examples.

For the purposes of this disclosure a “network” should be understood to refer to a network that may couple devices so that communications may be exchanged, such as between a server and a client device or other types of devices, including between wireless devices coupled via a wireless network, for example. A network may also include mass storage, such as network attached storage (NAS), a storage area network (SAN), a content delivery network (CDN) or other forms of computer or machine-readable media, for example. A network may include the Internet, one or more local area networks (LANs), one or more wide area networks (WANs), wire-line type connections, wireless type connections, cellular or any combination thereof. Likewise, sub-networks, which may employ different architectures or may be compliant or compatible with different protocols, may interoperate within a larger network.

For purposes of this disclosure, a “wireless network” should be understood to couple client devices with a network. A wireless network may employ stand-alone ad-hoc networks, mesh networks, Wireless LAN (WLAN) networks, cellular networks, or the like. A wireless network may further employ a plurality of network access technologies, including Wi-Fi, Long Term Evolution (LTE), WLAN, Wireless Router mesh, or 2nd, 3rd, 4thor 5thgeneration (2G, 3G, 4G or 5G) cellular technology, mobile edge computing (MEC), Bluetooth, 802.11b/a/g/n/ac/ax/be, or the like. Network access technologies may enable wide area coverage for devices, such as client devices with varying degrees of mobility, for example.

In short, a wireless network may include virtually any type of wireless communication mechanism by which signals may be communicated between devices, such as a client device or a computing device, between or within a network, or the like.

A computing device may be capable of sending or receiving signals, such as via a wired or wireless network, or may be capable of processing or storing signals, such as in memory as physical memory states, and may, therefore, operate as a server. Thus, devices capable of operating as a server may include, as examples, dedicated rack-mounted servers, desktop computers, laptop computers, set top boxes, integrated devices combining various features, such as two or more features of the foregoing devices, or the like.

For purposes of this disclosure, a client (or user, entity, subscriber or customer) device may include a computing device capable of sending or receiving signals, such as via a wired or a wireless network. A client device may, for example, include a desktop computer or a portable device, such as a cellular telephone, a smart phone, a display pager, a radio frequency (RF) device, an infrared (IR) device a Near Field Communication (NFC) device, a Personal Digital Assistant (PDA), a handheld computer, a tablet computer, a phablet, a laptop computer, a set top box, a wearable computer, smart watch, an integrated or distributed device combining various features, such as features of the forgoing devices, or the like.

A client device may vary in terms of capabilities or features. Claimed subject matter is intended to cover a wide range of potential variations, such as a web-enabled client device or previously mentioned devices may include a high-resolution screen (HD or 4K for example), one or more physical or virtual keyboards, mass storage, one or more accelerometers, one or more gyroscopes, global positioning system (GPS) or other location-identifying type capability, or a display with a high degree of functionality, such as a touch-sensitive color 2D or 3D display, for example.

Certain embodiments and principles will be discussed in more detail with reference to the figures.

According to some embodiments, the disclosed framework can provide a computerized dynamic for fan-athlete interaction. As fans watch a game, whether live or televised, the disclosed framework (e.g., application executing a device of a user for example) can seamlessly integrate with the real-time action, allowing fans to interact with the platform through their smartphones. When a player delivers an extraordinary performance, the framework notifies fans, offering them the opportunity to reward the athlete in real-time.

Additionally, athletes can benefit from the disclosed framework by gaining a direct avenue for fan recognition and compensation. Athletes can register with the platform, associating their profile with their NIL status.

As evidenced from the disclosure herein, the disclosed framework has the potential to significantly enhance fan engagement in sports, transforming the traditional passive role of spectators. The disclosed platform introduces ways for fans to become more emotionally invested (e.g., fans become emotionally invested in the game, knowing that they have a direct stake in rewarding their favorite players when they deliver exceptional performances), as they can engage with the athletes/players via real-time interaction (e.g., the disclosed framework's real-time notifications ensure that fans remain actively engaged throughout the game, with their focus directed towards the athletes' performances).

As such, the disclosed systems and methods provide a framework that can redefine fan engagement and athlete empowerment within the sports industry. The disclosed framework's unique fusion of blockchain technology, smart contracts and digital currencies has the potential to revolutionize how fans interact with their favorite athletes, making the experience of watching sports more immersive, dynamic and rewarding.

With reference toFIG.1, system100is depicted which includes user equipment (UE)102(e.g., a client device, as mentioned above and discussed below in relation toFIG.6), network104, cloud system106, database108and engagement engine200. It should be understood that while system100is depicted as including such components, it should not be construed as limiting, as one of ordinary skill in the art would readily understand that varying numbers of UEs, peripheral devices, cloud systems, databases and networks can be utilized; however, for purposes of explanation, system100is discussed in relation to the example depiction inFIG.1.

According to some embodiments, UE102can be any type of device, such as, but not limited to, a mobile phone, tablet, laptop, sensor, IoT device, wearable device, autonomous machine, smart television, media streaming device, game console, and any other device equipped with a cellular or wireless or wired transceiver.

In some embodiments, peripheral devices (not shown) can be connected to UE102, and can be any type of peripheral device, such as, but not limited to, a wearable device (e.g., smart ring, smart watch, for example), printer, speaker, sensor, and the like. In some embodiments, a peripheral device can be any type of device that is connectable to UE102via any type of known or to be known pairing mechanism, including, but not limited to, WiFi, Bluetooth™, Bluetooth Low Energy (BLE), NFC, and the like.

In some embodiments, network104can be any type of network, such as, but not limited to, a wireless network, cellular network, the Internet, and the like (as discussed above). Network104facilitates connectivity of the components of system100, as illustrated inFIG.1.

According to some embodiments, cloud system106may be any type of cloud operating platform and/or network based system upon which applications, operations, and/or other forms of network resources may be located. For example, system106may be a service provider and/or network provider from where services and/or applications may be accessed, sourced or executed from. For example, system106can represent the cloud-based, which has associated network resources hosted on the internet or private network (e.g., network104), which enables (via engine200) the content and resource management discussed herein.

In some embodiments, cloud system106may include a server(s) and/or a database of information which is accessible over network104. In some embodiments, a database108of cloud system106may store a dataset of data and metadata associated with local and/or network information related to a user(s) of the components of system100and/or each of the components of system100(e.g., UE102, and the services and applications provided by cloud system106and/or engagement engine200).

In some embodiments, for example, cloud system106can provide a private/proprietary management platform, whereby engine200, discussed infra, corresponds to the novel functionality system106enables, hosts and provides to a network104and other devices/platforms operating thereon.

Turning toFIGS.4and5, in some embodiments, the exemplary computer-based systems/platforms, the exemplary computer-based devices, and/or the exemplary computer-based components of the present disclosure may be specifically configured to operate in a cloud computing/architecture106such as, but not limiting to: infrastructure as a service (IaaS)510, platform as a service (PaaS)508, and/or software as a service (SaaS)506using a web browser, mobile app, thin client, terminal emulator or other endpoint504.FIGS.4and5illustrate schematics of non-limiting implementations of the cloud computing/architecture(s) in which the exemplary computer-based systems for administrative customizations and control of network-hosted application program interfaces (APIs) of the present disclosure may be specifically configured to operate.

Turning back toFIG.1, according to some embodiments, database108may correspond to a data storage for a platform (e.g., a network hosted platform, such as cloud system106, as discussed supra) or a plurality of platforms. Database108may receive storage instructions/requests from, for example, engine200(and associated microservices), which may be in any type of known or to be known format, such as, for example, standard query language (SQL). According to some embodiments, database108may correspond to any type of known or to be known storage, for example, a memory or memory stack of a device, a distributed ledger of a distributed network (e.g., blockchain, for example), a look-up table (LUT), and/or any other type of secure data repository.

Engagement engine200, as discussed above and further below in more detail, can include components for the disclosed functionality. According to some embodiments, engagement engine200may be a special purpose machine or processor, and can be hosted by a device on network104, within cloud system106, and/or on UE102. In some embodiments, engine200may be hosted by a server and/or set of servers associated with cloud system106.

According to some embodiments, as discussed in more detail below, engagement engine200may be configured to implement and/or control a plurality of services and/or microservices, where each of the plurality of services/microservices are configured to execute a plurality of workflows associated with performing the disclosed content and resource management. Non-limiting embodiments of such workflows are discussed and provided below.

According to some embodiments, as discussed above, engagement engine200may function as an application provided by cloud system106. In some embodiments, engine200may function as an application installed on a server(s), network location and/or other type of network resource associated with system106. In some embodiments, engine200may function as an application installed and/or executing on UE102. In some embodiments, such application may be a web-based application accessed by UE102, and/or devices over network104from cloud system106. In some embodiments, engine200may be configured and/or installed as an augmenting script, program or application (e.g., a plug-in or extension) to another application or program provided by cloud system106and/or executing on UE102.

As illustrated inFIG.2, according to some embodiments, engagement engine200includes identification module202, analysis module204, determination module206and output module208. It should be understood that the engine(s) and modules discussed herein are non-exhaustive, as additional or fewer engines and/or modules (or sub-modules) may be applicable to the embodiments of the systems and methods discussed. More detail of the operations, configurations and functionalities of engine200and each of its modules, and their role within embodiments of the present disclosure will be discussed below.

Turning toFIG.3, Process300provides non-limiting example embodiments for the disclosed content and resource management framework. According to some embodiments, Step302Process300can be performed by identification module202of engagement engine200; Steps304and314can be performed by analysis module204; Step306can be performed by determination module206; and Steps308-312can be performed by output module208.

According to some embodiments, Process300begins with Step302where engine200can identify an event and the participants of the event. The event, for example, can be a sporting event, and the participants can be the players on each team (e.g., the eligible players, as in some embodiments, those players that are injured and/or not active, can be filtered out of the participant listing). In some embodiments, a user (e.g., fan) can be viewing the event, where the user can be at the event and/or viewing (e.g., streaming) the event on a device (e.g., UE102).

In Step304, upon commencement of the event (e.g., start of the game), the game action is monitored. The monitoring can be continuous and/or according to predetermined and/or dynamically determined time period. Such monitoring can be based on a type of event. For example, if the event is a football game, the monitoring can start when the ball is hiked, and end when the referee blows their whistle (e.g., player tackled, out of bounds, in complete, timeout, touchdown, and the like). Similarly, if the game is a baseball game, the monitoring can start when the pitcher starts their windup, and end when the pitcher receives the ball again.

In some embodiments, Step304involves analyzing the game play data/metadata related to the content of the event. According to some embodiments, the computational analysis performed by engine200can involve any type of known or to be known computational analysis technique, algorithm, mechanism or technology to analyze the collected/monitored data for determinations whether a play of the game corresponds to a highlight (e.g., particularly exciting, interesting, or noteworthy moment or segment of gameplay that has been identified or captured for special attention—for example, a scoring play, a play that account for a certain threshold satisfying value (e.g., a football play of over 15 yards, a baseball hit of more than a single, and the like)). In some embodiments, a highlight can also correspond to a audio level or decibel level of the fans in attendance that at least reaches or exceeds a decibel level (e.g., the fans cheering a certain amount may designate the play as of importance).

In some embodiments, engine200may include a specific trained artificial intelligence/machine learning model (AI/ML), a particular machine learning model architecture, a particular machine learning model type (e.g., convolutional neural network (CNN), recurrent neural network (RNN), autoencoder, support vector machine (SVM), and the like), or any other suitable definition of a machine learning model or any suitable combination thereof.

In some embodiments, engine200may be configured to utilize one or more AI/ML techniques chosen from, but not limited to, computer vision, feature vector analysis, decision trees, boosting, support-vector machines, neural networks, nearest neighbor algorithms, Naive Bayes, bagging, random forests, logistic regression, and the like. By way of a non-limiting example, engine200can implement an XGBoost algorithm for regression and/or classification to analyze the collected data, as discussed herein.

In some embodiments and, optionally, in combination of any embodiment described above or below, a neural network technique may be one of, without limitation, feedforward neural network, radial basis function network, recurrent neural network, convolutional network (e.g., U-net) or other suitable network. In some embodiments and, optionally, in combination of any embodiment described above or below, an implementation of Neural Network may be executed as follows:a. define Neural Network architecture/model,b. transfer the input data to the neural network model,c. train the model incrementally,d. determine the accuracy for a specific number of timesteps,c. apply the trained model to process the newly-received input data,f. optionally and in parallel, continue to train the trained model with a predetermined periodicity.

In some embodiments and, optionally, in combination of any embodiment described above or below, the trained neural network model may specify a neural network by at least a neural network topology, a series of activation functions, and connection weights. For example, the topology of a neural network may include a configuration of nodes of the neural network and connections between such nodes. In some embodiments and, optionally, in combination of any embodiment described above or below, the trained neural network model may also be specified to include other parameters, including but not limited to, bias values/functions and/or aggregation functions. For example, an activation function of a node may be a step function, sine function, continuous or piecewise linear function, sigmoid function, hyperbolic tangent function, or other type of mathematical function that represents a threshold at which the node is activated. In some embodiments and, optionally, in combination of any embodiment described above or below, the aggregation function may be a mathematical function that combines (e.g., sum, product, and the like) input signals to the node. In some embodiments and, optionally, in combination of any embodiment described above or below, an output of the aggregation function may be used as input to the activation function. In some embodiments and, optionally, in combination of any embodiment described above or below, the bias may be a constant value or function that may be used by the aggregation function and/or the activation function to make the node more or less likely to be activated.

In Step306, based on the analysis from Step304, engine200can determine an occurrence of the highlight. In some embodiments, should monitored and collected data/metadata (or content) related to a play be determined to not be a highlight play, then processing of Process300can proceed back to Step304for further monitoring. In some embodiments, such monitoring is continued until the game is concluded (and can account for time-outs, halftimes, commercials, injuries, and the like).

In Step308, engine200can compile an electronic message or communication that can be electronically sent to a device (e.g., UE102) of the user. The electronic message, for example, can be a push notification that is sent to the smart phone of a user that enables the user to interact with a series of inputs to remit electronic payment within an account of a player involved in the highlight. In some embodiments, the message or notification can be sent to a device of the user and cause display of a graphical user interface (GUI) that includes interactive interface objects that correspond to players selections (e.g., the players involved in the highlight) and types and/or amounts of assets to transfer to the players' accounts.

According to some embodiments, the communication can be secured to only enable accounts of players involved in the highlight to be subject to payment. In some embodiments, those players not involved in a highlight may have their accounts locked (or read or write access revoked) for a time period (e.g., a Time-To-Live (TTL) tag applied thereto, which prevents unnecessary payment for players that are not part of particular plays). In some embodiments, such control and/or communication functionality can be a by-product of a smart contract that is associated with the event.

In Step312, engine200can receive input corresponding to the engagement of the fan with an account of the participant(s) involved in the highlight. Such engagement can be, but is not limited to, sending them fiat currency, sending them cryptocurrency, providing them a brand endorsement, and the like, as discussed supra. According to some embodiments, Step312can involve a smart contract determining and applying read and/or read/write access to the user for the participant's account, thereby enabling the secure access and transfer to the player's account. Such secure access can be granted for a time period (e.g., via a TTL, as discussed above), which can be triggered via the determination of the highlight (as in Step306).

And, in Step314, engine200can continue monitoring the game play via the protocols effectuated and implemented in Step304, discussed supra. Such monitoring can occur until the game is completed.

In some embodiments, the athlete receiving the transfer of the funds or reward (or transfer from the user, discussed above) can reject in whole or part or accept, which can provide control to the athlete as to how their account can be accessed by other users.

According to some embodiments, a smart contract can be created that automates the electronic transfer of Step314. For example, upon the game beginning or prior thereto, the user can compile, generate and/or execute a smart contract that indicates that for certain types of plays, for certain teams and/or certain players, they agree to automatically remit payment to the account of a/the player(s). Such remittance can occur in the same manner as discussed above.

FIG.6is a schematic diagram illustrating a client device showing an example embodiment of a client device that may be used within the present disclosure. Client device600may include many more or less components than those shown inFIG.6. However, the components shown are sufficient to disclose an illustrative embodiment for implementing the present disclosure. Client device600may represent, for example, UE102discussed above at least in relation toFIG.1.

As shown in the figure, in some embodiments, Client device600includes a processing unit (CPU)622in communication with a mass memory630via a bus624. Client device600also includes a power supply626, one or more network interfaces650, an audio interface652, a display654, a keypad656, an illuminator658, an input/output interface660, a haptic interface662, an optional global positioning systems (GPS) receiver664and a camera(s) or other optical, thermal or electromagnetic sensors666. Device600can include one camera/sensor666, or a plurality of cameras/sensors666, as understood by those of skill in the art. Power supply626provides power to Client device600.

Client device600may optionally communicate with a base station (not shown), or directly with another computing device. In some embodiments, network interface650is sometimes known as a transceiver, transceiving device, or network interface card (NIC).

Audio interface652is arranged to produce and receive audio signals such as the sound of a human voice in some embodiments. Display654may be a liquid crystal display (LCD), gas plasma, light emitting diode (LED), or any other type of display used with a computing device. Display654may also include a touch sensitive screen arranged to receive input from an object such as a stylus or a digit from a human hand.

Keypad656may include any input device arranged to receive input from a user. Illuminator658may provide a status indication and/or provide light.

Client device600also includes input/output interface660for communicating with external. Input/output interface660can utilize one or more communication technologies, such as USB, infrared, Bluetooth™, or the like in some embodiments. Haptic interface662is arranged to provide tactile feedback to a user of the client device.

Optional GPS transceiver664can determine the physical coordinates of Client device600on the surface of the Earth, which typically outputs a location as latitude and longitude values. GPS transceiver664can also employ other geo-positioning mechanisms, including, but not limited to, triangulation, assisted GPS (AGPS), E-OTD, CI, SAI, ETA, BSS or the like, to further determine the physical location of client device600on the surface of the Earth. In one embodiment, however, Client device600may through other components, provide other information that may be employed to determine a physical location of the device, including for example, a MAC address, Internet Protocol (IP) address, or the like.

Mass memory630includes a RAM632, a ROM634, and other storage means. Mass memory630illustrates another example of computer storage media for storage of information such as computer readable instructions, data structures, program modules or other data. Mass memory630stores a basic input/output system (“BIOS”)640for controlling low-level operation of Client device600. The mass memory also stores an operating system641for controlling the operation of Client device600.

Memory630further includes one or more data stores, which can be utilized by Client device600to store, among other things, applications642and/or other information or data. For example, data stores may be employed to store information that describes various capabilities of Client device600. The information may then be provided to another device based on any of a variety of events, including being sent as part of a header (e.g., index file of the HLS stream) during a communication, sent upon request, or the like. At least a portion of the capability information may also be stored on a disk drive or other storage medium (not shown) within Client device600.

Applications642may include computer executable instructions which, when executed by Client device600, transmit, receive, and/or otherwise process audio, video, images, and enable telecommunication with a server and/or another user of another client device. Applications642may further include a client that is configured to send, to receive, and/or to otherwise process gaming, goods/services and/or other forms of data, messages and content hosted and provided by the platform associated with engine200and its affiliates.

According to some embodiments, certain aspects of the instant disclosure can be embodied via functionality discussed herein, as disclosed supra. According to some embodiments, some non-limiting aspects can include, but are not limited to the below method aspects, which can additionally be embodied as system, apparatus and/or device functionality:

Aspect 1. A method comprising:identifying, by a device, an event, the event comprising a set of participants;analyzing, by the device, content captured related to real-time action of the event;determining, by the device, based on the analysis, an occurrence during the event of a highlight, the highlight being a portion of the real-time action that has characteristics at least a threshold degree of difference from other action occurring during the event;electronically communicating, by the device, over a network, an electronic notification to a user device, the communication comprising an interactive user interface (UI) that enables identification of particular participants within the portion real-time action associated with the highlight and a selection of a digital asset value; andelectronically communicating, via the device, over the network, the digital asset value to an electronic account of a participant identified via interaction with the UI.

Aspect 2. The method of aspect 1, wherein the digital asset value is at least one of a cryptocurrency and fiat.

Aspect 3. The method of aspect 1, wherein the communication of the electronic notification is performed in compliance with a smart contract, the smart contract associated with the event.

Aspect 4. The method of aspect 1, further comprising:determining a type of the event; andmonitoring the event according to a time period based on the type of event, wherein the analysis of the content captured is based on the time period of the monitoring of the event.

Aspect 5. The method of aspect 1, further comprising:communicating, over the network, a communication to the identified participant, the communication enabling the participant functionality to accept or deny the communication of the digital asset.

Aspect 6. The method of aspect 1, wherein the highlight is stored in a database upon the determination of the occurrence.

Aspect 7. The method of aspect 1, wherein the user device is a smart phone of the user.

Aspect 8. The method of aspect 1, wherein the event is a live event.

Aspect 9. The method of aspect 1, wherein the user is streaming the event.

Aspect 10. The method of aspect 1, wherein the user is at the event.

As used herein, the terms “computer engine” and “engine” identify at least one software component and/or a combination of at least one software component and at least one hardware component which are designed/programmed/configured to manage/control other software and/or hardware components (such as the libraries, software development kits (SDKs), objects, and the like).

Examples of hardware elements may include processors, microprocessors, circuits, circuit elements (e.g., transistors, resistors, capacitors, inductors, and so forth), integrated circuits, application specific integrated circuits (ASIC), programmable logic devices (PLD), digital signal processors (DSP), field programmable gate array (FPGA), logic gates, registers, semiconductor device, chips, microchips, chip sets, and so forth. In some embodiments, the one or more processors may be implemented as a Complex Instruction Set Computer (CISC) or Reduced Instruction Set Computer (RISC) processors; x86 instruction set compatible processors, multi-core, or any other microprocessor or central processing unit (CPU). In various implementations, the one or more processors may be dual-core processor(s), dual-core mobile processor(s), and so forth.

Computer-related systems, computer systems, and systems, as used herein, include any combination of hardware and software. Examples of software may include software components, programs, applications, operating system software, middleware, firmware, software modules, routines, subroutines, functions, methods, procedures, software interfaces, API, instruction sets, computer code, computer code segments, words, values, symbols, or any combination thereof. Determining whether an embodiment is implemented using hardware elements and/or software elements may vary in accordance with any number of factors, such as desired computational rate, power levels, heat tolerances, processing cycle budget, input data rates, output data rates, memory resources, data bus speeds and other design or performance constraints.

For the purposes of this disclosure a module is a software, hardware, or firmware (or combinations thereof) system, process or functionality, or component thereof, that performs or facilitates the processes, features, and/or functions described herein (with or without human interaction or augmentation). A module can include sub-modules. Software components of a module may be stored on a computer readable medium for execution by a processor. Modules may be integral to one or more servers, or be loaded and executed by one or more servers. One or more modules may be grouped into an engine or an application.

One or more aspects of at least one embodiment may be implemented by representative instructions stored on a machine-readable medium which represents various logic within the processor, which when read by a machine causes the machine to fabricate logic to perform the techniques described herein. Such representations, known as “IP cores,” may be stored on a tangible, machine readable medium and supplied to various customers or manufacturing facilities to load into the fabrication machines that make the logic or processor. Of note, various embodiments described herein may, of course, be implemented using any appropriate hardware and/or computing software languages (e.g., C++, Objective-C, Swift, Java, JavaScript, Python, Perl, QT, and the like).

For example, exemplary software specifically programmed in accordance with one or more principles of the present disclosure may be downloadable from a network, for example, a website, as a stand-alone product or as an add-in package for installation in an existing software application. For example, exemplary software specifically programmed in accordance with one or more principles of the present disclosure may also be available as a client-server software application, or as a web-enabled software application. For example, exemplary software specifically programmed in accordance with one or more principles of the present disclosure may also be embodied as a software package installed on a hardware device.

For the purposes of this disclosure the term “user”, “subscriber” “consumer” or “customer” should be understood to refer to a user of an application or applications as described herein and/or a consumer of data supplied by a data provider. By way of example, and not limitation, the term “user” or “subscriber” can refer to a person who receives data provided by the data or service provider over the Internet in a browser session, or can refer to an automated software application which receives the data and stores or processes the data. Those skilled in the art will recognize that the methods and systems of the present disclosure may be implemented in many manners and as such are not to be limited by the foregoing exemplary embodiments and examples. In other words, functional elements being performed by single or multiple components, in various combinations of hardware and software or firmware, and individual functions, may be distributed among software applications at either the client level or server level or both. In this regard, any number of the features of the different embodiments described herein may be combined into single or multiple embodiments, and alternate embodiments having fewer than, or more than, all of the features described herein are possible.

Functionality may also be, in whole or in part, distributed among multiple components, in manners now known or to become known. Thus, myriad software/hardware/firmware combinations are possible in achieving the functions, features, interfaces and preferences described herein. Moreover, the scope of the present disclosure covers conventionally known manners for carrying out the described features and functions and interfaces, as well as those variations and modifications that may be made to the hardware or software or firmware components described herein as would be understood by those skilled in the art now and hereafter.

Furthermore, the embodiments of methods presented and described as flowcharts in this disclosure are provided by way of example in order to provide a more complete understanding of the technology. The disclosed methods are not limited to the operations and logical flow presented herein. Alternative embodiments are contemplated in which the order of the various operations is altered and in which sub-operations described as being part of a larger operation are performed independently.

While various embodiments have been described for purposes of this disclosure, such embodiments should not be deemed to limit the teaching of this disclosure to those embodiments. Various changes and modifications may be made to the elements and operations described above to obtain a result that remains within the scope of the systems and processes described in this disclosure.