Patent Application
20250168208
The present disclosure relates to video conference streaming, and, more specifically, to communications protocols for video conference streaming.
Video conferencing is a technology that allows users in different locations to hold real-time face-to-face meetings. Video conferencing works by transmitting audio and/or video between two or more devices over a network, such as the Internet. Video conferencing can be used for various purposes, such as business meetings, educational courses, medical appointments, and social events. Platforms for video conferencing can include features that allow users to share their screens, chat with one another, record video conference sessions, as well as other features.
Aspects of the present disclosure are directed toward a computer-implemented method comprising receiving an instruction to share a media item to one or more other user devices participating in a video conference session. The computer-implemented method further comprising capturing an independent data feed for the media item that is separate from a video conference data feed. The computer-implemented method further comprising sending the independent data feed for the media item to the one or more other user devices using a messaging protocol that identifies the independent data feed for the media item as being separate from the video conference data feed to enable the one or more other user devices to provide the independent data feed in an application window that is independent of a video conference application window of the video conference session.
Additional aspects of the present disclosure are directed to systems and computer program products configured to perform the methods described above. The present summary is not intended to illustrate each aspect of, every implementation of, and/or every embodiment of the present disclosure.
The drawings included in the present application are incorporated into and form part of the specification. They illustrate embodiments of the present disclosure and, along with the description, serve to explain the principles of the disclosure. The drawings are only illustrative of certain embodiments and do not limit the disclosure.
While the present disclosure is amenable to various modifications and alternative forms, specifics thereof have been shown by way of example in the drawings and will be described in detail. It should be understood, however, that the intention is not to limit the present disclosure to the particular embodiments described. On the contrary, the intention is to cover all modifications, equivalents, and alternatives falling within the spirit and scope of the present disclosure.
Aspects of the present disclosure are directed to sharing a media item to a video conference session using an independent data feed that enables the media item to be provided in an independent application window on participant user devices that is separate from a video conference application window. While not limited to such applications, embodiments of the present disclosure may be better understood in light of the aforementioned context.
Generally, video conferencing technologies allow a presenter to share (display) one or more media items, such as text documents, slideshows, videos, etc. with other participants of the video conference session. For example, a presenter can share a media item by opening the media item on the presenter's user device and selecting a share function of the video conferencing platform that captures the media item and integrates the capture of the media item into a video conference data feed of the video conference shown in a video conference application window of the video conference on the other participant's user devices. However, when received at the participant user devices, prior to the present disclosure, the elements included in the video conference data feed were shown in a fixed layout in a video conference application window (e.g., a fixed configuration of participant video feeds, chat features, and other media items shared by the presenter). Accordingly, the participants of the video conference could not change the layout to better view and/or interact with the shared media item displayed in the video conference application window. For example, the participants could not separate the media item from the video conference application window to better view and/or interact with the media item. Moreover, in cases where multiple media items were shared to the video conference session, a media item with which the presenter was currently interacting with was obscured by the other shared media items.
Advantageously, aspects of the present disclosure overcome these challenges by substantially simultaneously capturing an independent data feed for a media item that is shared to user devices participating in a video conference session to enable the user device to provide the independent data feed in an application window that is separate (autonomous) from a video conference application window. Providing the independent data feed in the application window allows a participant of the video conference session to adjust a position and/or size of the application window separate from the video conference application window.
In some embodiments, a computer-implemented method shares a media item to a video conference session using a messaging protocol that enables participant user devices to provide the media item in an application window that is separate from a video conference application window. Namely, a computer receives an instruction to share a media item to one or more other user devices participating in a video conference session. In response, the computer captures an independent data feed for the media item that is separate from a video conference data feed, and the computer sends the independent data feed for the media item to the one or more other user devices using a messaging protocol that identifies the independent data feed for the media item as being separate from the video conference data feed. The identifying of the independent data feed as being separate from the video conference data feed enables the one or more other user devices to provide the independent data feed in an application window that is independent of a video conference application window of the video conference session. As a result, the computer-implemented method provides the technical effect of enhancing a message protocol to differentiate between a video conference data feed for a video conference session and an independent data feed for a media item shared to user devices participating in the video conference session.
In some embodiments, the computer determines a bitrate and an encoding technique for the independent data feed based on a file type of the media item. As a result, the computer-implemented method provides the technical effect of selecting a bitrate and encoding technique to enable efficient transmission of the independent data feed to the user devices participating in the video conference session. That is, because a bitrate and encoding technique used to transmit the video conference data feed to the user devices participating in the video conference session may not be optimal for transmitting the independent data feed to the user devices, the computer-implemented method allows the selection of a more optimal bitrate and encoding technique for transmitting the independent data feed of the media item.
In some embodiments, the computer comprises a user device that generates the independent data feed for sharing the media item to the one or more other user devices participating in the video conference session. Because the independent data feed is generated locally on the user device sharing the media item, the computer-implemented method provides the technical effect of reducing a workload on a video conference server that would otherwise generate the independent data feed.
In some embodiments, a participant user device of the video conference session receives streaming data for the video conference session, determines that a message included in the streaming data identifies the independent data feed for the media item as separate from the video conference data feed of the video conference session, decodes the independent data feed using a decoding technique indicated in the message, and instantiates an application window to provide the independent data feed on the participant user device. Instantiating the application window allows a user of the participant user device to adjust a size and position of the application window separately from the video conference application window of the video conference session. As a result, the computer-implemented method provides the technical effect of providing an application window for the independent data feed that is independent of the video conference application window, which allows the user to control the size and position of the application window independently from the video conference application window. Providing the application window for the independent data feed is an improvement to a user interface and the user experience because having the ability to adjust the size and position of the application window independently from the video conference application window improves viewability of the shared media item on the user's desktop.
In some embodiments, the computer enhances a real-time messaging protocol (RTMP) message to identify the independent data feed for the media item as being separate from the video conference data feed of the video conference session. As a result, the computer-implemented method provides the technical effect of a multiple data feed (video conference data feed and media item data feed) that is sent in parallel from a presenter user device to one or more participant user devices using enhanced RTMP messages. That is, enhancing the RTMP messages to identify the independent data feed as being separate from the video conference data feed enables sending of the data feeds in parallel.
In some embodiments, the computer further enhances the RTMP message to specify: a stream identifier for the independent data feed of the media item, an encoding technique used to encode the independent data feed of the media item, and layout settings for the application window to be initially used by the one or more other user devices to provide the independent data feed of the media item. As a result, the computer-implemented method provides the technical effect of providing a participant user device information for identifying the independent data feed for the media item in a multiple data feed, and providing the independent data feed in an application window on the participant user device. Namely, the information in the enhanced RMTP message enables the participant user device to differentiate between the independent data feed and the video conference data feed, and to independently decode independent data feed, and to instantiate the application window for the independent data feed using initial layout settings (e.g., an initial size and position), which can thereafter be changed by the user.
In some embodiments, the computer captures a plurality of independent data feeds for a plurality of media items shared to the video conference session, where a message of the messaging protocol sent to the one or more other user devices identifies, separately, the plurality of independent data feeds to enable the one or more other user devices to provide each independent data feed in the plurality of independent data feeds in a separate application window that is independent of the video conference application window of the video conference session. As a result, the computer-implemented method provides the technical effect of providing a separate application window for each media item that is shared to the video conference session, which allows a user to independently adjust the application windows according to the user's preferences.
In some embodiments, the computer adds information to a message of the messaging protocol that identifies an active media item, included in a plurality of media items, that has a most recent focus on the desktop of a user device that is sharing the plurality of media items to other user devices participating in the video conference session. As a result, the computer-implemented method provides the technical effect of notifying participant user devices which of the plurality of media items is the active media item on the presenter's desktop. That is, because each of the plurality of media items is provided a separate application window on the participating user devices, the messaging protocol informs the participating user devices which of the application windows contains the active media item.
In some embodiments, a participant user device of the video conference session receives a message of the messaging protocol and determines that the message identifies the active media item having the most recent focus on the desktop of the user device sharing the plurality of media items. In response, the participant user device displays a visual indication on the participant user device to identify the active media item. As a result, the computer-implemented method provides the technical effect of displaying, to the participants of the video conference session, which of the application windows containing shared media items is the active media item on the presenter's desktop. Displaying the visual indication is an improvement to a user interface and the user experience because it differentiates an application window containing the active media item from other application windows containing inactive media items.
Moreover, in some embodiments, a computer-implemented method comprises a presenter user device of a video conference session that receives an instruction to share a media item to one or more participating user devices of the video conference session. In response, the presenter user device captures an independent data feed for the media item that is separate from a video conference data feed and sends the independent data feed for the media item to the one or more participating user devices using an enhanced RTMP that specifies a stream identifier for the independent data feed of the media item, an encoding technique used to encode the independent data feed of the media item, and layout settings for the application window to be initially used by the one or more other user devices to provide the independent data feed of the media item. The computer-implemented method further comprises one or more participating user devices of the video conference session that receive streaming data for the video conference session and determine that an RTMP message included in the streaming data includes the stream identifier, the encoding technique, and the layout settings for the application window. In response, the one or more participating user devices identify the independent data feed for the media item using the stream identifier indicated in the RTMP message, decode the independent data feed based on the encoding technique indicated in the RTMP message, and instantiate an application window using the layout settings indicated in the RTMP message to provide the independent data feed on the one or more participant user devices, thereby allowing the users of the participant user devices to adjust a size and position of the application window separately from the video conference application window of the video conference session. As a result, the computer-implemented method provides the technical effect of enhancing the RTMP to differentiate between a video conference data feed for a video conference session and an independent data feed for a media item shared to user devices participating in the video conference session, and to include information for providing the independent data feed for the media item in an application window that is separate from a video conference application window used to provide participant video, audio, chat, etc.
Referring now to the figures,
Accordingly, one feature and advantage of some embodiments is the video conferencing system 100 illustrated in
To provide an understanding of a data flow between a presenter user device 130A and 130N,
As shown in
The video conference network 106 enables communication between the video conference clients 102. The video conference network 106 can include one or more video conferencing servers and computing networks (not shown), including an intranet, the Internet, a local area network, a wide area network, a wireless data network, or any other such network or combination thereof. Components utilized for the video conference network 106 can depend at least in part upon the type of network and/or environment selected. Communication over the video conference network 106 can be enabled by wired connections, wireless connections, and combinations thereof.
With continuing reference to
As shown in
In addition to selecting a bitrate for the independent data feed, the encoder 112 selects an encoding technique to generate the independent data feed for the media item 110. In some embodiments, the encoder 112 selects an appropriate encoding technique from a plurality of codecs 116. A codec 116 comprises a device or software that compresses a data feed for streaming to the video conference clients 102B, and decompresses the data feed for playback by the video conference clients 102B. Non-limiting examples of video codecs include H.264, H.265, VP9, and AV1. Non-limiting examples of audio codecs include MP3, AAC, and Opus.
As mentioned earlier, the video conference client 102A includes an enhanced message protocol module 118 for sending individual data feeds associated with a video conference session to the video conference network 106 for distribution to the video conference clients 102B. The individual data feeds include a video conference data feed for the video conference session (e.g., participant video and/or audio, chat messages, etc.) and one or more independent data feeds for one or more media items 110 shared by a presenter to the other participants of the video conference session.
In some embodiments, the enhanced message protocol module 118 modifies a known communications protocol for streaming data over a network to indicate (identify) a video conference data feed for a video conference session, and to indicate (identify) one or more independent data feeds for one or more media items 110 shared to the video conference session. A message generated by the enhanced message protocol module 118 can include information that identifies an independent data feed for a media item 110 and information used by a video conference client 102B to decode and display the independent data feed on a user device 130N. In one example, the message can include: a stream identifier for an independent data feed of a media item 110, an encoding technique (codec) used to encode the independent data feed, layout settings for sizing and positioning an independent application window 210 used to provide the independent data feed on the desktop a user device 130N, and other information as can be appreciated.
In some embodiments, the enhanced message protocol module 118 modifies the RMTP to provide independent data feeds of media items 110 to participant user devices 130N. As background, RTMP is a TCP-based protocol configured to maintain persistent low-latency connections between video conference clients 102. RTMP splits streaming data into fragments to deliver a video stream smoothly and transmit as much information as possible. RTMP data packets sent over a TCP connection between video conference clients 102 contain a header and a body. The body contains the payload (the actual data contained in the message, such as compressed video data or audio data). The header is split into a basic header and a chunk message header. The chunk message basic header encodes a chunk stream ID and a chunk type. The chunk type determines the format of the encoded message header. Information in the basic header includes a stream ID. The chunk message header contains meta-data information, such as the message size (measured in bytes), the timestamp delta, and the message type.
As shown in the non-limiting example below, an RMTP message generated by the enhanced message protocol module 118 can include a chunk stream ID in the basic header field that identifies an independent data feed for a media item 110, and information in the data field that identifies a codec used to encode the chunk data and layout settings (e.g., application window position and size) for displaying the independent data feed on a user device 130N (including, in some embodiments, an active parameter to indicate that the media item 110 is the active media item on the presenter's desktop).
As shown in the non-limiting example below, in the case where multiple (e.g., three) media items 110 are shared to a video conference session, the enhanced message protocol module 118 generates information for each media item 110 that sent to the video conference network 106 for distribution to participant user devices 130N.
In response to receiving an enhanced message (e.g., an enhanced RTMP message) at a participant user device 130N, the enhanced message is provided to a video conference client 102B hosed on the user device 130N. The video conference client 102B processes the enhanced message to determine whether video streaming data for the video conference session includes an independent data feed for a media item 110. As shown in
As shown in
With continuing reference to
Determining which of a plurality of shared media items 304/306 is the active media item 304 can comprise: identifying an application window for a shared media item on the presenter's desktop that has the focus on the presenter's desktop (e.g., such as when the presenter sets the application window as the foreground window on the presenter's desktop); identifying an application window on the presenter's desktop that contains a shared media item and is receiving some type of user input (e.g., such as when the presenter hovers a cursor over the media item); and/or identifying an application window containing a shared media item that was last interacted with by the presenter (i.e., the last shared media item with which the presenter interacted).
After determining which of the shared media items 304/306 is the active media item 304 on the presenter's desktop, the video conference client 102A generates an enhanced message for the independent data feed of the active media item 304 to indicate that the independent data feed is associated with the active media item 304. When the messages for the independent data feed are received at a participant user device 302N, the video conference client 102B evaluates the active parameter to identify the active media item 304, and the video conference client 102B causes a visual indication 308 (e.g., a label, banner, animation, color, or the like) to be displayed on the participant user device 302N that identifies the independent application window 312 as containing the active media item 304. In the event that another media item becomes the active media item 304 on the presenter's desktop (e.g., the presenter opens or selects a different document, image, slideshow, video, or the like), the video conference client 102A updates the messages for the respective independent data feeds accordingly, which when received by the video conference client 102B, causes the video conference client 102B to update the display of the visual indication 308 to be associated with the independent application window that displays the active media item 304 on the participant user device 302N.
All or a portion of the components shown in
Generally, the components illustrated include routines, programs, components and/or data structures that perform particular tasks and/or implement particular abstract data types. In some embodiments, the components can be implemented as computing services hosted in a computing service environment. For example, a module can be considered a service with one or more processes executing on a server or other computer hardware. Such services can provide a service application that receives requests and provides output to other services or consumer devices. An API can be provided for each module to enable a first module to send requests to and receive output from a second module. Such APIs can also allow third parties to interface with the module and make requests and receive output from the modules.
While the figures described above illustrate examples of a computational environment that can implement the techniques above, many other similar or different environments are possible. The example environments discussed and illustrated above are merely representative and not limiting. Other components in addition to, or in place of, the ones illustrated may be used. Some components may be unnecessary. Also, the blocks are presented to illustrate some functional components. One or more of these blocks may be combined, divided, or combined and divided into different blocks when implemented in an illustrative embodiment.
In operation 402, the method 400 captures an independent data feed for a media item to share with user devices participating in a video conference session. The method 400, in some embodiments, captures the independent data feed in response to receiving an instruction to share the media item to one or more other user devices participating in the video conference session. Capturing the independent data feed can comprise generating a series of screenshots of the media item displayed on the presenter's desktop and generating video data from the screenshots that can be shared with the participating user devices. As will be appreciated, other techniques for capturing the independent data feed are within the scope of the present disclosure.
In operation 404, the method 400 calculates a bitrate for sending the independent data feed to the participant user devices. In some embodiments, the method 400 calculates the bitrate based on a file type of the media item, such that the method 400 selects a higher bitrate for file types (e.g., videos) that require a higher bitrate to provide a quality representation on a user device, and the method 400 selects a lower bitrate for file types (e.g., images) that do not require a high bitrate to provide a quality representation on a user device. In some embodiments, the method 400 evaluates a media item to determine whether the media item contains embedded content that requires a higher bitrate for quality playback on a user device, and the method 400 selects a higher bitrate to enable quality playback of the embedded content on the participant user devices.
In operation 406, the method 400 selects an encoding technique for the independent data feed based on a file type of the media item. For example, the method 400 can select an appropriate codec to compress the independent data feed for streaming to the user devices participating in the video conference session. Non-limiting examples of codecs include H.264, H.265, VP9, AV1, MP3, AAC, and Opus. In operation 408, the method 400 encodes the independent data feed using the selected encoding technique.
In operation 410, the method 400 sends the independent data feed of the media item to the user devices participating in the video conference session to enable the participating user devices to provide the independent data feed in an independent application window that is separate from a video conference application window of the video conference session. The method 400 uses an enhanced message protocol to send the independent data feed to the user devices. The enhanced message protocol identifies the independent data feed as being separate from a video conference data feed of the video conference session, which allows the independent data feed to be provided in an independent application window on participating user devices that is separate (autonomous) from the video conference application window of the video conference session. In some embodiments, the enhanced message protocol comprises the real-time message protocol (RTMP).
The method 400, in some embodiments, enhances the message protocol to include a stream identifier for the independent data feed of the media item, an encoding technique (e.g., codec) used to encode the independent data feed of the media item, layout settings (e.g., position and size) for an independent application window for the media item, as well as other information for providing the media item on the participating user devices. Also, in some embodiments, the method 400 enhances the message protocol to identify an active media item included in multiple media items on a presenter's desktop. The active media item comprises one of multiple media items open on the presenter's desktop with which the presenter is currently, or most recently, referencing. Identification of which media item open on the presenter's desktop is the active media item can be used to identify (highlight) an open independent application window on the participant's desktop that contains the active media item. Illustratively, the method 400 can determine which of the media items open on the presenter's desktop is the active media item by determining which application window containing a media item open on the presenter's desktop has the focus (e.g., is the foreground application window on the presenter's desktop), or is receiving some type of user input (e.g., such as when the presenter hovers a cursor over the media item), or was the last media item interacted with by the presenter.
In operation 502, the method 500 receives streaming data for a video conference session. In response to receiving the streaming data, the method 500, in operation 504, determines that the streaming data includes an independent data feed for a shared media item that is separate from a video conference data feed for the video conference session. For example, the method 500 processes (analyzes) messages included in the streaming data to determine whether the messages contain information for a media item shared by a presenter user device. In some embodiments, the messages comprise RTMP messages. As described earlier, the messages are enhanced to include, for example, a stream identifier for an independent data feed of a media item, an encoding technique (e.g., codec) used to encode the independent data feed, layout settings (e.g., position and size) for an independent application window for the media item, and other information as will be appreciated.
In operation 506, the method 500 decodes the independent data feed for the media item using a decoding technique specified in the streaming data. The enhanced messages included in the independent data feed of the media item specify a codec used to encode the independent data feed. The method 500 processes the messages to identify the codec, and the method 500 decodes the independent data feed using the codec. Because the independent data feed for the media item is separate from the video conference data feed for the video conference session, the codec used to encode and decode the independent data feed may be different than a codec used to encode and decode the video conference data feed for the video conference session.
In operation 508, the method 500 instantiates an independent application window used to provide the independent data feed for the media item on the participating user device. The independent application window for the media item is separate from a video conference application window used to provide a user interface for the video conference session. As such, participants of the video conference session have the ability to reposition and resize the independent application window according to the participants' preferences, as well as make the independent application window the foreground window on the participants' user devices. Illustratively, when multiple media items are shared to the video conference session, a participant can modify the layout (size and position) of independent application windows on the participant's desktop to enable viewing of a selected media item of interest to the participant.
In some embodiments, the method 500 instantiates the independent application window using layout setting specified in the messages associated with the independent data feed of the media item. The method 500 processes the messages to identify the layout settings for an independent application window, and the method 500 uses the layout settings to instantiate the independent application window on the desktop of a participant's user devices.
The methods illustrated and described above can be performed by a computer (e.g., computer 601 in
In some alternative implementations of an illustrative embodiment, the function or functions noted in the blocks may occur out of the order noted in the figures. For example, in some cases, two blocks shown in succession can be performed substantially concurrently, or the blocks may sometimes be performed in the reverse order, depending upon the functionality involved. Also, other blocks can be added in addition to the illustrated blocks in a flowchart or block diagram.
Various aspects of the present disclosure are described by narrative text, flowcharts, block diagrams of computer systems and/or block diagrams of the machine logic included in computer program product (CPP) embodiments. With respect to any flowcharts, depending upon the technology involved, the operations can be performed in a different order than what is shown in a given flowchart. For example, again depending upon the technology involved, two operations shown in successive flowchart blocks may be performed in reverse order, as a single integrated step, concurrently, or in a manner at least partially overlapping in time.
A computer program product embodiment (“CPP embodiment” or “CPP”) is a term used in the present disclosure to describe any set of one, or more, storage media (also called “mediums”) collectively included in a set of one, or more, storage devices that collectively include machine readable code corresponding to instructions and/or data for performing computer operations specified in a given CPP claim. A “storage device” is any tangible device that can retain and store instructions for use by a computer processor. Without limitation, the computer readable storage medium may be an electronic storage medium, a magnetic storage medium, an optical storage medium, an electromagnetic storage medium, a semiconductor storage medium, a mechanical storage medium, or any suitable combination of the foregoing. Some known types of storage devices that include these mediums include: diskette, hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or Flash memory), static random-access memory (SRAM), compact disc read-only memory (CD-ROM), digital versatile disk (DVD), memory stick, floppy disk, mechanically encoded device (such as punch cards or pits/lands formed in a major surface of a disc) or any suitable combination of the foregoing. A computer readable storage medium, as that term is used in the present disclosure, is not to be construed as storage in the form of transitory signals per se, such as radio waves or other freely propagating electromagnetic waves, electromagnetic waves propagating through a waveguide, light pulses passing through a fiber optic cable, electrical signals communicated through a wire, and/or other transmission media. As will be understood by those of skill in the art, data is typically moved at some occasional points in time during normal operations of a storage device, such as during access, de-fragmentation or garbage collection, but this does not render the storage device as transitory because the data is not transitory while it is stored.
Computing environment 600 contains an example of an environment for the execution of at least some of the computer code involved in performing the disclosed methods, such as block 650 containing computer code for the video conference client described earlier. In addition to block 650, computing environment 600 includes, for example, computer 601, wide area network (WAN) 602, end user device (EUD) 603, remote server 604, public cloud 605, and private cloud 606. In this embodiment, computer 601 includes processor set 610 (including processing circuitry 620 and cache 621), communication fabric 611, volatile memory 612, persistent storage 613 (including operating system 622 and block 650, as identified above), peripheral device set 614 (including user interface (UI), device set 623, storage 624, and Internet of Things (IoT) sensor set 625), and network module 615. Remote server 604 includes remote database 630. Public cloud 605 includes gateway 640, cloud orchestration module 641, host physical machine set 642, virtual machine set 643, and container set 644.
COMPUTER 601 may take the form of a desktop computer, laptop computer, tablet computer, smart phone, smart watch or other wearable computer, mainframe computer, quantum computer or any other form of computer or mobile device now known or to be developed in the future that is capable of running a program, accessing a network or querying a database, such as remote database 630. As is well understood in the art of computer technology, and depending upon the technology, performance of a computer-implemented method may be distributed among multiple computers and/or between multiple locations. On the other hand, in this presentation of computing environment 600, detailed discussion is focused on a single computer, specifically computer 601, to keep the presentation as simple as possible. Computer 601 may be located in a cloud, even though it is not shown in a cloud in
PROCESSOR SET 610 includes one, or more, computer processors of any type now known or to be developed in the future. Processing circuitry 620 may be distributed over multiple packages, for example, multiple, coordinated integrated circuit chips. Processing circuitry 620 may implement multiple processor threads and/or multiple processor cores. Cache 621 is memory that is located in the processor chip package(s) and is typically used for data or code that should be available for rapid access by the threads or cores running on processor set 610. Cache memories are typically organized into multiple levels depending upon relative proximity to the processing circuitry. Alternatively, some, or all, of the cache for the processor set may be located “off chip.” In some computing environments, processor set 610 may be designed for working with qubits and performing quantum computing.
Computer readable program instructions are typically loaded onto computer 601 to cause a series of operational steps to be performed by processor set 610 of computer 601 and thereby effect a computer-implemented method, such that the instructions thus executed will instantiate the methods specified in flowcharts and/or narrative descriptions of computer-implemented methods included in this document (collectively referred to as “the disclosed methods”). These computer readable program instructions are stored in various types of computer readable storage media, such as cache 621 and the other storage media discussed below. The computer readable program instructions, and associated data, are accessed by processor set 610 to control and direct performance of the disclosed methods. In computing environment 600, at least some of the instructions for performing the disclosed methods may be stored in block 650 in persistent storage 613.
COMMUNICATION FABRIC 611 is the signal conduction paths that allow the various components of computer 601 to communicate with each other. Typically, this fabric is made of switches and electrically conductive paths, such as the switches and electrically conductive paths that make up busses, bridges, physical input/output ports and the like. Other types of signal communication paths may be used, such as fiber optic communication paths and/or wireless communication paths.
VOLATILE MEMORY 612 is any type of volatile memory now known or to be developed in the future. Examples include dynamic type random access memory (RAM) or static type RAM. Typically, the volatile memory is characterized by random access, but this is not required unless affirmatively indicated. In computer 601, the volatile memory 612 is located in a single package and is internal to computer 601, but, alternatively or additionally, the volatile memory may be distributed over multiple packages and/or located externally with respect to computer 601.
PERSISTENT STORAGE 613 is any form of non-volatile storage for computers that is now known or to be developed in the future. The non-volatility of this storage means that the stored data is maintained regardless of whether power is being supplied to computer 601 and/or directly to persistent storage 613. Persistent storage 613 may be a read only memory (ROM), but typically at least a portion of the persistent storage allows writing of data, deletion of data and re-writing of data. Some familiar forms of persistent storage include magnetic disks and solid-state storage devices. Operating system 622 may take several forms, such as various known proprietary operating systems or open-source Portable Operating System Interface type operating systems that employ a kernel. The code included in block 650 typically includes at least some of the computer code involved in performing the disclosed methods.
PERIPHERAL DEVICE SET 614 includes the set of peripheral devices of computer 601. Data communication connections between the peripheral devices and the other components of computer 601 may be implemented in various ways, such as Bluetooth connections, Near-Field Communication (NFC) connections, connections made by cables (such as universal serial bus (USB) type cables), insertion type connections (for example, secure digital (SD) card), connections made though local area communication networks and even connections made through wide area networks such as the internet. In various embodiments, UI device set 623 may include components such as a display screen, speaker, microphone, wearable devices (such as goggles and smart watches), keyboard, mouse, printer, touchpad, game controllers, and haptic devices. Storage 624 is external storage, such as an external hard drive, or insertable storage, such as an SD card. Storage 624 may be persistent and/or volatile. In some embodiments, storage 624 may take the form of a quantum computing storage device for storing data in the form of qubits. In embodiments where computer 601 is required to have a large amount of storage (for example, where computer 601 locally stores and manages a large database) then this storage may be provided by peripheral storage devices designed for storing very large amounts of data, such as a storage area network (SAN) that is shared by multiple, geographically distributed computers. IoT sensor set 625 is made up of sensors that can be used in Internet of Things applications. For example, one sensor may be a thermometer and another sensor may be a motion detector.
NETWORK MODULE 615 is the collection of computer software, hardware, and firmware that allows computer 601 to communicate with other computers through WAN 602. Network module 615 may include hardware, such as modems or Wi-Fi signal transceivers, software for packetizing and/or de-packetizing data for communication network transmission, and/or web browser software for communicating data over the internet. In some embodiments, network control functions and network forwarding functions of network module 615 are performed on the same physical hardware device. In other embodiments (for example, embodiments that utilize software-defined networking (SDN)), the control functions and the forwarding functions of network module 615 are performed on physically separate devices, such that the control functions manage several different network hardware devices. Computer readable program instructions for performing the disclosed methods can typically be downloaded to computer 601 from an external computer or external storage device through a network adapter card or network interface included in network module 615.
WAN 602 is any wide area network (for example, the internet) capable of communicating computer data over non-local distances by any technology for communicating computer data, now known or to be developed in the future. In some embodiments, the WAN may be replaced and/or supplemented by local area networks (LANs) designed to communicate data between devices located in a local area, such as a Wi-Fi network. The WAN and/or LANs typically include computer hardware such as copper transmission cables, optical transmission fibers, wireless transmission, routers, firewalls, switches, gateway computers and edge servers.
END USER DEVICE (EUD) 603 is any computer system that is used and controlled by an end user (for example, a customer of an enterprise that operates computer 601), and may take any of the forms discussed above in connection with computer 601. EUD 603 typically receives helpful and useful data from the operations of computer 601. For example, in a hypothetical case where computer 601 is designed to provide a recommendation to an end user, this recommendation would typically be communicated from network module 615 of computer 601 through WAN 602 to EUD 603. In this way, EUD 603 can display, or otherwise present, the recommendation to an end user. In some embodiments, EUD 603 may be a user device, such as thin client, heavy client, mainframe computer, desktop computer and so on.
REMOTE SERVER 604 is any computer system that serves at least some data and/or functionality to computer 601. Remote server 604 may be controlled and used by the same entity that operates computer 601. Remote server 604 represents the machine(s) that collect and store helpful and useful data for use by other computers, such as computer 601. For example, in a hypothetical case where computer 601 is designed and programmed to provide a recommendation based on historical data, then this historical data may be provided to computer 601 from remote database 630 of remote server 604.
PUBLIC CLOUD 605 is any computer system available for use by multiple entities that provides on-demand availability of computer system resources and/or other computer capabilities, especially data storage (cloud storage) and computing power, without direct active management by the user. Cloud computing typically leverages sharing of resources to achieve coherence and economies of scale. The direct and active management of the computing resources of public cloud 605 is performed by the computer hardware and/or software of cloud orchestration module 641. The computing resources provided by public cloud 605 are typically implemented by virtual computing environments that run on various computers making up the computers of host physical machine set 642, which is the universe of physical computers in and/or available to public cloud 605. The virtual computing environments (VCEs) typically take the form of virtual machines from virtual machine set 643 and/or containers from container set 644. It is understood that these VCEs may be stored as images and may be transferred among and between the various physical machine hosts, either as images or after instantiation of the VCE. Cloud orchestration module 641 manages the transfer and storage of images, deploys new instantiations of VCEs and manages active instantiations of VCE deployments. Gateway 640 is the collection of computer software, hardware, and firmware that allows public cloud 605 to communicate through WAN 602.
Some further explanation of virtualized computing environments (VCEs) will now be provided. VCEs can be stored as “images.” A new active instance of the VCE can be instantiated from the image. Two familiar types of VCEs are virtual machines and containers. A container is a VCE that uses operating-system-level virtualization. This refers to an operating system feature in which the kernel allows the existence of multiple isolated user-space instances, called containers. These isolated user-space instances typically behave as real computers from the point of view of programs running in them. A computer program running on an ordinary operating system can utilize all resources of that computer, such as connected devices, files and folders, network shares, CPU power, and quantifiable hardware capabilities. However, programs running inside a container can only use the contents of the container and devices assigned to the container, a feature which is known as containerization.
PRIVATE CLOUD 606 is similar to public cloud 605, except that the computing resources are only available for use by a single enterprise. While private cloud 606 is depicted as being in communication with WAN 602, in other embodiments a private cloud may be disconnected from the internet entirely and only accessible through a local/private network. A hybrid cloud is a composition of multiple clouds of different types (for example, private, community or public cloud types), often respectively implemented by different vendors. Each of the multiple clouds remains a separate and discrete entity, but the larger hybrid cloud architecture is bound together by standardized or proprietary technology that enables orchestration, management, and/or data/application portability between the multiple constituent clouds. In this embodiment, public cloud 605 and private cloud 606 are both part of a larger hybrid cloud.
The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the various embodiments. As used herein, the singular forms “a,” “an,” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. The terms “comprises,” “comprising,” “includes,” “including,” “has,” “having,” “contains” or “containing,” or any other variation thereof, are intended to cover a non-exclusive inclusion. For example, a process, method, article, or apparatus that comprises a list of elements is not necessarily limited to only those elements but can include other elements not expressly listed or inherent to such process, method, article, or apparatus. The term “user” refers to an entity (e.g., an individual(s), a computer, or an application executing on a computer). It will be further understood that the terms “includes” and/or “including,” when used in this specification, specify the presence of the stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.
In the previous detailed description of example embodiments of the various embodiments, reference was made to the accompanying drawings (where like numbers represent like elements), which form a part hereof, and in which is shown by way of illustration specific example embodiments in which the various embodiments can be practiced. These embodiments were described in sufficient detail to enable those skilled in the art to practice the embodiments, but other embodiments can be used and logical, mechanical, electrical, and other changes can be made without departing from the scope of the various embodiments. In the previous description, numerous specific details were set forth to provide a thorough understanding the various embodiments. But the various embodiments can be practiced without these specific details. In other instances, well-known circuits, structures, and techniques have not been shown in detail in order not to obscure embodiments.
Different instances of the word “embodiment” as used within this specification do not necessarily refer to the same embodiment, but they can. Any data and data structures illustrated or described herein are examples only, and in other embodiments, different amounts of data, types of data, fields, numbers and types of fields, field names, numbers and types of rows, records, entries, or organizations of data can be used. In addition, any data can be combined with logic, so that a separate data structure may not be necessary. The previous detailed description is, therefore, not to be taken in a limiting sense.
Although the present disclosure has been described in terms of specific embodiments, it is anticipated that alterations and modification thereof will become apparent to the skilled in the art. Therefore, it is intended that the following claims be interpreted as covering all such alterations and modifications as fall within the true spirit and scope of the disclosure. Note further that numerous aspects or features are disclosed herein, and unless inconsistent, each disclosed aspect or feature is combinable with any other disclosed aspect or feature as desired for a particular application of the concepts disclosed.
As used herein, the terms “example” and/or “exemplary” are utilized to mean serving as an example, instance, or illustration. For the avoidance of doubt, the subject matter described herein is not limited by such examples. In addition, any aspect or design described herein as an “example” and/or “exemplary” is not necessarily to be construed as preferred or advantageous over other aspects or designs, nor is it meant to preclude equivalent exemplary structures and techniques known to those of ordinary skill in the art. Any advantages discussed in the present disclosure are example advantages, and embodiments of the present disclosure can exist that realize all, some, or none of any of the discussed advantages while remaining within the spirit and scope of the present disclosure.
It will be further appreciated that various aspects of the present invention may be provided in the form of a service deployed on behalf of a customer to offer service on demand.
The descriptions of the various aspects of the present invention have been presented for purposes of illustration, but are not intended to be exhaustive or limited to the approaches disclosed. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the described aspects. The terminology used herein was chosen to best explain the principles of the various aspects described, the practical application or technical improvement over technologies found in the marketplace, or to enable others of ordinary skill in the art to understand the approaches disclosed herein.
