214 may include watermarks, evidence stamps, an evidence number, seals, signature, a document number, a page number, or other designation of information that may be added to the master version of the document. Typically, these master layers 214 may be added during the certification and/or encryption of the master version. The certification and/or encryption may take place during or before the active event. This may depend on when the documents are uploaded and/or other rules (such as when the document is admitted into evidence). A set of pre-active layers 216A-C may be added by the user devices before the active event. These may include notes, questions, talking points, highlights, cross-references, and the like. The user may add the pre-active layer during preparation for the active event, so as to assist the user in accessing and/or displaying information during the active event. A set of active layers 218A-D may be created and or added during the active event. The set of active layers 218A-D may be added to any of various screens of the various user devices and/or copies of the electronic documents. For example, a user may take notes during a deposition, which information may then be saved as a layer. The notes may be displayed to that user, and to other authorized users, during the deposition. Similarly, various aspects of the document may be highlighted, emphasized, enlarged, or otherwise customized on the active copy of the document. This active layer may be displayed to all participants. A set of post-active layers 220 may be created that may be permanently saved with the document. The set of post-active layers 220 may include the one or more active layers that were shown to all participants, as a record of the document as displayed during the active event. The post-active layers 220 may additionally or alternatively be added after the active event.

Other manipulations of the electronic document may also be possible in various embodiments of the present disclosure. As a first example, the document may be signed by one or more users during the active event, such as during a negotiation as an active event. As a second example, the document may be modified or translated during the active event.

Now referring to FIG. 3, each block of method 300, described herein, comprises a computing process that may be performed using any combination of hardware, firmware, and/or software. For instance, various functions may be carried out by a processor executing instructions stored in memory. The method 300 may also be embodied as computer-usable instructions stored on computer storage media. The method 300 may be provided by a standalone application, a service or hosted service (standalone or in combination with another hosted service), or a plug-in to another product, to name a few. In addition, method 300 is described, by way of example, with respect to the system of FIG. 1. However, this method may additionally or alternatively be executed by any one system, or any combination of systems, including, but not limited to, those described herein.

FIG. 3 is a flow diagram showing a method 300 for document-sharing conferencing, suitable for use in implementing some embodiments of the present disclosure. In the example of FIG. 3, steps performed by a server (such as application server 104) are shown on a left side of the figure, and steps performed by a user device (such as client devices 102) are shown on a right side of the figure. The method 300, at Step 302, includes receiving an electronic document as an original version 200. The original version 200 may be sent from a source computing device, such as one of the user devices. The user device may send the original version 200 before the beginning of the active event, such that the original version 200 may be fully uploaded and ready at the beginning of the active event. In some instances, another source computing device may send the original version 200, such as an original creator or custodian of the electronic document.

The method 300, at Step 304, includes storing a master copy 202 of the electronic document. The step of storing the master copy 202 may include encrypting the master copy 202 such that the master copy 202 cannot be changed or altered (either accidentally or intentionally). The step of storing the master copy 202 may also include certifying the original version 200, such as by authenticating the original version 200 directly or indirectly.

The method 300, at Step 306, includes a first user device receiving a first user copy 204. The user may access or request the first user copy before, during, and/or after the active event (such as the deposition, mediation, or other hearing). This step may include storing the first user copy 204 in local storage. In other embodiments, the first user copy 204 may only be accessible while the user device is connected to the server, such that there is no local storage permitted.

The method 300, at Step 308, includes displaying the first user copy 204 on the first user device. Displaying the first user copy 204 may allow the user to review the contents, take notes, customize the first user copy 204, and perform other functions. The method 300, at Step 310, includes receiving and saving a customization. The customization may be a pre-active layer 216 or an active layer 218. The pre-active layer 216 and/or the active layer 218 may be shown overlaying or otherwise altering the display of the first user copy 204.

The method 300, at Step 312, includes receiving an active event indication, such as an indication that the active event is about to begin. The active event may be any type of event, such as in which the electronic document may be displayed to two or more people. The two or more people may be remote from each other (e.g., a video conference in which the electronic document is displayed to two or more participants) or local to each other (e.g., in an in-person courtroom hearing with a screen to show the electronic document). The method 300, at Step 314, includes displaying an active copy 210 of the electronic document. The active copy 210 may be shown alongside the video conference, such that users may see the electronic document with the one or more layers thereon, while also seeing one or more other participants. The method 300, at Step 316, includes instructing a video conference feed. The method 300, at Step 318, includes displaying the video conference feed along with the active display copy.

The method 300, at Step 320, includes sending an active layer 218 to the server. The active layer 218 may be sent by one or more user devices. As an example, the user may select one of the pre-active layers 216 saved before the active event to display as an active layer 218 to all participants. The active layer 218 may highlight a certain portion of the document, or provide some other customization. The method 300, at Step 322, includes distributing the active layer to one or more additional user devices. This allows all participants to see the new active layer 218 during the active event. The method 300, at Step 324, includes saving a post-active layer. The active layer 218 or layers that were displayed during the active event may be saved such that a record exists of what active layers were shown. This may allow for recreation of the active layers, such as in the case of a subsequent active event, such as another hearing, an appeal from the prior hearing, general record keeping, or the like.

Turning to FIGS. 4A-D, example graphical user interfaces that may be displayed in one or more embodiments of the present disclosure. The example graphical user interfaces may show one or more aspects of the present disclosure and are intended to convey these concepts to the reader. Other aspects of the invention may not be shown or may be displayed in another user interface.

FIG. 4A shows an example case creation interface. In the example legal field of use, the case creation interface may allow a user, such as an attorney, paralegal, assistant, judge, court clerk, mediator, arbitrator, litigant, witness, or other person to create a case record. A menu panel (shown at left) may include a dashboard, cases, depositions, and/or other resources to which the user has access. The menu may also provide access to account information, a help center, a payment center, a terms of service statement, and/or other resources to which the user may have access. For a particular case, the user may be presented with one or more fields to enter information related to that case. This information may be associated with the documents directly or indirectly. For example, the information from the fields may be added or associated with the documents as metadata. Example fields include a case name, a case number, due dates, case type, court name, party names, attorney names, and other information.

FIG. 4B shows an example document management interface. This example document management interface is related to a deposition of a single witness within a case, such as the one created in FIG. 4A. The example document management interface may include information about the active event associated, such as a deposition of a certain witness. The document management interface may include information about the witness, a stenographer, and/or other observers. The document management interface may further include a listing of personal documents, exhibits, outlines, and other files. The user may be able to add documents, which may be treated as original versions 200 of the electronic document. The user may select any of various documents to display and customize with one or more layers. The user may also create new documents for notes, outlines, questions, or the like.

FIG. 4C shows an example document sharing video conference interface. The document sharing conference interface may be shown during the active event, such as the deposition, arbitration, hearing, or other event. The video conference interface may show one or more video feeds and/or audio feeds. Additional participants or observers may be watching with neither a video feed nor an audio feed. An active copy 210 of the electronic document may be shown to one or more participants or observers. One user, such as an attorney, may ask questions related to the active copy 210 of another user, such as a witness. The witness may refer to the document in providing answers. The attorney, or other presenter, may emphasize or show certain portions of the active copy 210. Some users may be able to independently scroll through the document, open and close other documents, and perform other tasks related to documents while the active copy 210 is being shown.

FIG. 4D shows an example document sharing video conference interface with an active layer on an active copy 210 as well as a user-specific document. The active layer, such as the highlighting shown, may emphasize or increase visibility of a section of the active copy 210.

The user may additionally be able to view a user-specific document. The user-specific document may be an outline, instructions, a list of questions, background information, or another document. The user may reference the user-specific document during the active event. The user interface may also present a warning, as shown, to let a user known that a certain action may move another document to be the active document. In embodiments of the present disclosure, the user-specific document may have been at least partially created and/or edited by a machine learning algorithm or other artificial intelligence, such as the analyzation/creation application 122 discussed above. The analyzation/creation application 122 may produce and/or supplement a list of key information for the document, a list of background information, a list of foundational questions for the document, a list of key information from the document, a list of quotes from one or more external documents (such as a complaint) that relate to the current document and/or witness, or provide other information that may be useful to the attorney or other user.

The user may be presented with other information during the active event. As a first example, a user (such as a defending attorney at a deposition) may be presented with a prompt recommending an object to be made based upon a question being asked by another user (such as a deposing attorney). The prompt may recommend a certain objection be entered into the record, and may provide a basis for the objection. The prompt may be determined based upon an analysis of the question as recorded by a speech-to-text algorithm, by a human stenographer, a transcript, or other source. As a second example, a user may be presented with recommended follow-up questions. The recommended question may be based in part on one or more prior answers, on information in one or more documents, on a list of questions or notes prepared before the active event (such as illustrated at left in FIG. 4D). As a third example, a user may be presented with a prompt indicative of a conflicting answer being given. The system may know an expected answer to an asked question based upon information in one or more documents. The system may then identify when an answer is given that is contrary to an expected answer. The system may also provide a basis (such as a section of a specific document) in which the original answer was given and present that to the user, such that the user may impeach the witness or other participant. As a fourth example, a user may be presented with a prompt indicative of an ethical issue, a potential appeal issue, or other issue that the user may raise or avoid during the active event.

In embodiments of the present disclosure, the system may also decide or provide a recommendation regarding a disagreement between two or more users. The recommendation may analyze past decisions, rules, and other evidence to determine a likely resolution to the disagreement. For example, during a deposition, a disagreement may arise over the permissibility of a certain question. A first attorney may instruct a client not to answer the question while a second attorney insists on an answer. The system may analyze the disagreement and provide a recommendation as to which attorney is likely correct, along with one or more supporting reasons (such as a rule citation). This may serve as an independent suggestion to resolve the dispute, without the attorneys having to involve an outside decision maker (such as a judge or mediator).

Embodiments of the present disclosure may track success rates, usage rates, types of active events, and other statistics related to a user for a specific user account. The user (such as an attorney, moderator, arbitrator, expert witness, etc.) may thus advertise or find more work based at least in part on these tracked statistics. The user may share other information, such as a calendar of availability, notes, statements of specialty or interest areas, and the like. The user may further utilize the user account to receive and make payments related to the services rendered and received, respectively.

Example Content Streaming System

Now referring to FIG. 5, FIG. 5 is an example system diagram for a content streaming system 500, in accordance with some embodiments of the present disclosure. FIG. 5 includes application server(s) 502 (which may include similar components, features, and/or functionality to the example computing device 600 of FIG. 6), client device(s) 504 (which may include similar components, features, and/or functionality to the example computing device 600 of FIG. 6), and network(s) 506 (which may be similar to the network(s) described herein). In some embodiments of the present disclosure, the system 500 may be implemented. The application session may correspond to a game streaming application, a remote desktop application, a simulation application (e.g., autonomous or semi-autonomous vehicle simulation), computer aided design (CAD) applications, virtual reality (VR) and/or augmented reality (AR) streaming applications, deep learning applications, and/or other application types.

In the system 500, for an application session, the client device(s) 504 may only receive input data in response to inputs to the input device(s), transmit the input data to the application server(s) 502, receive encoded display data from the application server(s) 502, and display the display data on the display 524. As such, the more computationally intense computing and processing is offloaded to the application server(s) 502 (e.g., rendering—in particular ray or path tracing—for graphical output of the application session is executed by the GPU(s) of the game server(s) 502). In other words, the application session is streamed to the client device(s) 504 from the application server(s) 502, thereby reducing the requirements of the client device(s) 504 for graphics processing and rendering.

For example, with respect to an instantiation of an application session, a client device 504 may be displaying a frame of the application session on the display 524 based on receiving the display data from the application server(s) 502. The client device 504 may receive an input to one of the input device(s) and generate input data in response. The client device 504 may transmit the input data to the application server(s) 502 via the communication interface 520 and over the network(s) 506 (e.g., the Internet), and the application server(s) 502 may receive the input data via the communication interface 518. The CPU(s) may receive the input data, process the input data, and transmit data to the GPU(s) that causes the GPU(s) to generate a rendering of the application session. For example, the input data may be representative of a movement of a character of the user in a game session of a game application, firing a weapon, reloading, passing a ball, turning a vehicle, etc. The rendering component 512 may render the application session (e.g., representative of the result of the input data) and the render capture component 514 may capture the rendering of the application session as display data (e.g., as image data capturing the rendered frame of the application session). The rendering of the application session may include ray or path-traced lighting and/or shadow effects, computed using one or more parallel processing units—such as GPUs, which may further employ the use of one or more dedicated hardware accelerators or processing cores to perform ray or path-tracing techniques—of the application server(s) 502. In some embodiments, one or more virtual machines (VMs)—e.g., including one or more virtual components, such as vGPUs, vCPUs, etc.—may be used by the application server(s) 502 to support the application sessions. The encoder 516 may then encode the display data to generate encoded display data and the encoded display data may be transmitted to the client device 504 over the network(s) 506 via the communication interface 518. The client device 504 may receive the encoded display data via the communication interface 520 and the decoder 522 may decode the encoded display data to generate the display data. The client device 504 may then display the display data via the display 524.

Example Computing Device

FIG. 6 is a block diagram of an example computing device(s) 600 suitable for use in implementing some embodiments of the present disclosure. Computing device 600 may include an interconnect system 602 that directly or indirectly couples the following devices: memory 604, one or more central processing units (CPUs) 606, one or more graphics processing units (GPUs) 608, a communication interface 610, input/output (I/O) ports 612, input/output components 614, a power supply 616, one or more presentation components 618 (e.g., display(s)), and one or more logic units 620. In at least one embodiment, the computing device(s) 600 may comprise one or more virtual machines (VMs), and/or any of the components thereof may comprise virtual components (e.g., virtual hardware components). For non-limiting examples, one or more of the GPUs 608 may comprise one or more vGPUs, one or more of the CPUs 606 may comprise one or more vCPUs, and/or one or more of the logic units 620 may comprise one or more virtual logic units. As such, a computing device(s) 600 may include discrete components (e.g., a full GPU dedicated to the computing device 600), virtual components (e.g., a portion of a GPU dedicated to the computing device 600), or a combination thereof.

Although the various blocks of FIG. 6 are shown as connected via the interconnect system 602 with lines, this is not intended to be limiting and is for clarity only. For example, in some embodiments, a presentation component 618, such as a display device, may be considered an I/O component 614 (e.g., if the display is a touch screen). As another example, the CPUs 606 and/or GPUs 608 may include memory (e.g., the memory 604 may be representative of a storage device in addition to the memory of the GPUs 608, the CPUs 606, and/or other components). In other words, the computing device of FIG. 6 is merely illustrative. Distinction is not made between such categories as “workstation,” “server,” “laptop,” “desktop,” “tablet,” “client device,” “mobile device,” “hand-held device,” “game console,” “electronic control unit (ECU),” “virtual reality system,” and/or other device or system types, as all are contemplated within the scope of the computing device of FIG. 6.

The interconnect system 602 may represent one or more links or busses, such as an address bus, a data bus, a control bus, or a combination thereof. The interconnect system 602 may include one or more bus or link types, such as an industry standard architecture (ISA) bus, an extended industry standard architecture (EISA) bus, a video electronics standards association (VESA) bus, a peripheral component interconnect (PCI) bus, a peripheral component interconnect express (PCIe) bus, and/or another type of bus or link. In some embodiments, there are direct connections between components. As an example, the CPU 606 may be directly connected to the memory 604. Further, the CPU 606 may be directly connected to the GPU 608. Where there is direct, or point-to-point connection between components, the interconnect system 602 may include a PCIe link to carry out the connection. In these examples, a PCI bus need not be included in the computing device 600.

The memory 604 may include any of a variety of computer-readable media. The computer-readable media may be any available media that may be accessed by the computing device 600. The computer-readable media may include both volatile and nonvolatile media, and removable and non-removable media. By way of example, and not limitation, the computer-readable media may comprise computer-storage media and communication media.

The computer-storage media may include both volatile and nonvolatile media and/or removable and non-removable media implemented in any method or technology for storage of information such as computer-readable instructions, data structures, program modules, and/or other data types. For example, the memory 604 may store computer-readable instructions (e.g., that represent a program(s) and/or a program element(s), such as an operating system. Computer-storage media may include, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which may be used to store the desired information and which may be accessed by computing device 600. As used herein, computer storage media does not comprise signals per se.

The computer storage media may embody computer-readable instructions, data structures, program modules, and/or other data types in a modulated data signal such as a carrier wave or other transport mechanism and includes any information delivery media. The term “modulated data signal” may refer to a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal. By way of example, and not limitation, the computer storage media may include wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, RF, infrared and other wireless media. Combinations of any of the above should also be included within the scope of computer-readable media.

The CPU(s) 606 may be configured to execute at least some of the computer-readable instructions to control one or more components of the computing device 600 to perform one or more of the methods and/or processes described herein. The CPU(s) 606 may each include one or more cores (e.g., one, two, four, eight, twenty-eight, seventy-two, etc.) that are capable of handling a multitude of software threads simultaneously. The CPU(s) 606 may include any type of processor, and may include different types of processors depending on the type of computing device 600 implemented (e.g., processors with fewer cores for mobile devices and processors with more cores for servers). For example, depending on the type of computing device 600, the processor may be an Advanced RISC Machines (ARM) processor implemented using Reduced Instruction Set Computing (RISC) or an x86 processor implemented using Complex Instruction Set Computing (CISC). The computing device 600 may include one or more CPUs 606 in addition to one or more microprocessors or supplementary co-processors, such as math co-processors.

In addition to or alternatively from the CPU(s) 606, the GPU(s) 608 may be configured to execute at least some of the computer-readable instructions to control one or more components of the computing device 600 to perform one or more of the methods and/or processes described herein. One or more of the GPU(s) 608 may be an integrated GPU (e.g., with one or more of the CPU(s) 606 and/or one or more of the GPU(s) 608 may be a discrete GPU. In embodiments, one or more of the GPU(s) 608 may be a coprocessor of one or more of the CPU(s) 606. The GPU(s) 608 may be used by the computing device 600 to render graphics (e.g., 3D graphics) or perform general purpose computations. For example, the GPU(s) 608 may be used for General-Purpose computing on GPUs (GPGPU). The GPU(s) 608 may include hundreds or thousands of cores that are capable of handling hundreds or thousands of software threads simultaneously. The GPU(s) 608 may generate pixel data for output images in response to rendering commands (e.g., rendering commands from the CPU(s) 606 received via a host interface). The GPU(s) 608 may include graphics memory, such as display memory, for storing pixel data or any other suitable data, such as GPGPU data. The display memory may be included as part of the memory 604. The GPU(s) 608 may include two or more GPUs operating in parallel (e.g., via a link). The link may directly connect the GPUs (e.g., using NVLINK) or may connect the GPUs through a switch (e.g., using NVSwitch). When combined together, each GPU 608 may generate pixel data or GPGPU data for different portions of an output or for different outputs (e.g., a first GPU for a first image and a second GPU for a second image). Each GPU may include its own memory, or may share memory with other GPUs.

In addition to or alternatively from the CPU(s) 606 and/or the GPU(s) 608, the logic unit(s) 620 may be configured to execute at least some of the computer-readable instructions to control one or more components of the computing device 600 to perform one or more of the methods and/or processes described herein. In embodiments, the CPU(s) 606, the GPU(s) 608, and/or the logic unit(s) 620 may discretely or jointly perform any combination of the methods, processes and/or portions thereof. One or more of the logic units 620 may be part of and/or integrated in one or more of the CPU(s) 606 and/or the GPU(s) 608 and/or one or more of the logic units 620 may be discrete components or otherwise external to the CPU(s) 606 and/or the GPU(s) 608. In embodiments, one or more of the logic units 620 may be a coprocessor of one or more of the CPU(s) 606 and/or one or more of the GPU(s) 608.

Examples of the logic unit(s) 620 include one or more processing cores and/or components thereof, such as Tensor Cores (TCs), Tensor Processing Units (TPUs), Pixel Visual Cores (PVCs), Vision Processing Units (VPUs), Graphics Processing Clusters (GPCs), Texture Processing Clusters (TPCs), Streaming Multiprocessors (SMs), Tree Traversal Units (TTUs), Artificial Intelligence Accelerators (AIAs), Deep Learning Accelerators (DLAs), Arithmetic-Logic Units (ALUs), Application-Specific Integrated Circuits (ASICs), Floating Point Units (FPUs), input/output (I/O) elements, peripheral component interconnect (PCI) or peripheral component interconnect express (PCIe) elements, and/or the like.

The communication interface 610 may include one or more receivers, transmitters, and/or transceivers that enable the computing device 600 to communicate with other computing devices via an electronic communication network, included wired and/or wireless communications. The communication interface 610 may include components and functionality to enable communication over any of a number of different networks, such as wireless networks (e.g., Wi-Fi, Z-Wave, Bluetooth, Bluetooth LE, ZigBee, etc.), wired networks (e.g., communicating over Ethernet or InfiniBand), low-power wide-area networks (e.g., LoRaWAN, SigFox, etc.), and/or the Internet.

The I/O ports 612 may enable the computing device 600 to be logically coupled to other devices including the I/O components 614, the presentation component(s) 618, and/or other components, some of which may be built in to (e.g., integrated in) the computing device 600. Illustrative I/O components 614 include a microphone, mouse, keyboard, joystick, game pad, game controller, satellite dish, scanner, printer, wireless device, etc. The I/O components 614 may provide a natural user interface (NUI) that processes air gestures, voice, or other physiological inputs generated by a user. In some instances, inputs may be transmitted to an appropriate network element for further processing. An NUI may implement any combination of speech recognition, stylus recognition, facial recognition, biometric recognition, gesture recognition both on screen and adjacent to the screen, air gestures, head and eye tracking, and touch recognition (as described in more detail below) associated with a display of the computing device 600. The computing device 600 may be include depth cameras, such as stereoscopic camera systems, infrared camera systems, RGB camera systems, touchscreen technology, and combinations of these, for gesture detection and recognition. Additionally, the computing device 600 may include accelerometers or gyroscopes (e.g., as part of an inertia measurement unit (IMU)) that enable detection of motion. In some examples, the output of the accelerometers or gyroscopes may be used by the computing device 600 to render immersive augmented reality or virtual reality.

The power supply 616 may include a hard-wired power supply, a battery power supply, or a combination thereof. The power supply 616 may provide power to the computing device 600 to enable the components of the computing device 600 to operate.

The presentation component(s) 618 may include a display (e.g., a monitor, a touch screen, a television screen, a heads-up-display (HUD), other display types, or a combination thereof), speakers, and/or other presentation components. The presentation component(s) 618 may receive data from other components (e.g., the GPU(s) 608, the CPU(s) 606, etc.), and output the data (e.g., as an image, video, sound, etc.).

Example Data Center

FIG. 7 illustrates an example data center 700 that may be used in at least one embodiments of the present disclosure. The data center 700 may include a data center infrastructure layer 710, a framework layer 720, a software layer 730, and/or an application layer 740.

As shown in FIG. 7, the data center infrastructure layer 710 may include a resource orchestrator 712, grouped computing resources 714, and node computing resources (“node C.R.s”) 716(1)-716(N), where “N” represents any whole, positive integer. In at least one embodiment, node C.R.s 716(1)-716(N) may include, but are not limited to, any number of central processing units (CPUs) or other processors (including accelerators, field programmable gate arrays (FPGAs), graphics processors or graphics processing units (GPUs), etc.), memory devices (e.g., dynamic read-only memory), storage devices (e.g., solid state or disk drives), network input/output (NW I/O) devices, network switches, virtual machines (VMs), power modules, and/or cooling modules, etc. In some embodiments, one or more node C.R.s from among node C.R.s 716(1)-716(N) may correspond to a server having one or more of the above-mentioned computing resources. In addition, in some embodiments, the node C.R.s 716(1)-7161(N) may include one or more virtual components, such as vGPUs, vCPUs, and/or the like, and/or one or more of the node C.R.s 716(1)-716(N) may correspond to a virtual machine (VM).

In at least one embodiment, grouped computing resources 714 may include separate groupings of node C.R.s 716 housed within one or more racks (not shown), or many racks housed in data centers at various geographical locations (also not shown). Separate groupings of node C.R.s 716 within grouped computing resources 714 may include grouped compute, network, memory or storage resources that may be configured or allocated to support one or more workloads. In at least one embodiment, several node C.R.s 716 including CPUs, GPUs, and/or other processors may be grouped within one or more racks to provide compute resources to support one or more workloads. The one or more racks may also include any number of power modules, cooling modules, and/or network switches, in any combination.

The resource orchestrator 722 may configure or otherwise control one or more node C.R.s 716(1)-716(N) and/or grouped computing resources 714. In at least one embodiment, resource orchestrator 722 may include a software design infrastructure (SDI) management entity for the data center 700. The resource orchestrator 722 may include hardware, software, or some combination thereof.

In at least one embodiment, as shown in FIG. 7, framework layer 720 may include a job scheduler 732, a configuration manager 734, a resource manager 736, and/or a distributed file system 738. The framework layer 720 may include a framework to support software 732 of software layer 730 and/or one or more application(s) 742 of application layer 740. The software 732 or application(s) 742 may respectively include web-based service software or applications, such as those provided by Amazon Web Services, Google Cloud and Microsoft Azure. The framework layer 720 may be, but is not limited to, a type of free and open-source software web application framework such as Apache Spark™ (hereinafter “Spark”) that may utilize distributed file system 738 for large-scale data processing (e.g., “big data”). In at least one embodiment, job scheduler 732 may include a Spark driver to facilitate scheduling of workloads supported by various layers of data center 700. The configuration manager 734 may be capable of configuring different layers such as software layer 730 and framework layer 720 including Spark and distributed file system 738 for supporting large-scale data processing. The resource manager 736 may be capable of managing clustered or grouped computing resources mapped to or allocated for support of distributed file system 738 and job scheduler 732. In at least one embodiment, clustered or grouped computing resources may include grouped computing resource 714 at data center infrastructure layer 710. The resource manager 1036 may coordinate with resource orchestrator 712 to manage these mapped or allocated computing resources.

In at least one embodiment, software 732 included in software layer 730 may include software used by at least portions of node C.R.s 716(1)-716(N), grouped computing resources 714, and/or distributed file system 738 of framework layer 720. One or more types of software may include, but are not limited to, Internet web page search software, e-mail virus scan software, database software, and streaming video content software.

In at least one embodiment, application(s) 742 included in application layer 740 may include one or more types of applications used by at least portions of node C.R.s