Patent Application
20180351757
The present disclosure pertains to multiparty network conferencing, and more specifically to providing detecting unauthorized participants in a multiparty conferencing session.
Multiparty conferencing allows participants from multiple locations to collaborate. For example, participants from multiple geographic locations can join a conference meeting and communicate with each other to discuss issues, share ideas, etc. These collaborative sessions may include one or two-way audio transmissions, video transmission, or other data supporting tools that support the sharing of content presented by one participant to other participants. Thus, conference meetings can simulate in-person interactions between people.
A conferencing session is typically established by an enterprise or provider of conferencing services within an enterprise network or other private network. However, the resources required for private-network conferencing requires large costs and investments with respect to private network bandwidth and equipment within the private network.
Switched or cloud-based conferencing solutions involves the use of public networks and may be more cost effective because the hardware, application, and bandwidth costs may be covered by the conferencing provider and an enterprise may pay for what is actually used versus needing to pay for even idle time in private-network conferencing. Furthermore, cloud-based conferencing solutions are more easily scalable. However, deploying conference resources in a cloud environment that uses public networks introduces additional security risks.
The above-recited and other advantages and features of the disclosure will become apparent by reference to specific embodiments thereof which are illustrated in the appended drawings. Understanding that these drawings depict only example embodiments of the disclosure and are not therefore to be considered to be limiting of its scope, the principles herein are described and explained with additional specificity and detail through the use of the accompanying drawings in which:
Various embodiments of the disclosure are discussed in detail below. While specific implementations are discussed, it should be understood that this is done for illustration purposes only. A person skilled in the relevant art will recognize that other components and configurations may be used without parting from the spirit and scope of the disclosure.
The disclosed technology addresses the need in the art for a more secure and cost efficient way to provide multiparty conferencing sessions.
Switched or cloud-based conferencing solutions provide a more cost effective and scalable alternative to private-network conferencing. However, deploying conference resources in a cloud environment introduces additional security risks resulting from some network entities being in a public network.
Various aspects of the subject technology relate to mitigating these and other security risks by having an endpoint compare a roster list provided via a first communication channel (e.g., a Session Initiation Protocol (SIP) communication) and a participant list provided via a second communication channel (e.g., a participant list from a key management server). To improve efficiency and protect sensitive information in the lists, a hash of both the roster list and the participant list may be compared instead of the lists themselves. If the hash values match, the roster list is valid and the conference can continue. If the hash values do not match, there may be an unauthorized listener and a meeting organizer may take steps to address the violation.
The network environment 100 includes one or more endpoints 115 and 120 as well as network entities configured to provide conferencing services. These network entities may include one or more media distributors 125, one or more conference controllers 130, and one or more key management servers 135. The various network entities may be physical machines (e.g., a server or computer), virtual machines, applications, containers, or other entity configured to perform the functions of a network entity.
Although the cloud network 110 may include one or more enterprise or otherwise private networks, the cloud network may also include a public network or semi-public network. The public network may include, for example, any one or more of a cellular network, a satellite network, a wide area network (WAN), a broadband network (BBN), the Internet, and the like. Communication network 110 may be implemented using any number of communications links associated with one or more service providers, including one or more wired communication links, one or more wireless communication links, or any combination thereof. Additionally, network 110 can be configured to support the transmission of data formatted using any number of protocols.
The one or more endpoints 115 and 120 may be customer or users devices configured to provide the conferencing data to a user. Example endpoints 115 and 120 may include, but are not limited to, computers, laptops, tablets, smartphones or other mobile devices, set-top boxes, smart appliances (e.g., smart televisions), multipoint control units (MCUs), media gateways, media recording devices, conference room devices, or other conferencing equipment.
The endpoints 115 and 120 may be configured to communicate via various protocols such as, for example, the real-time transport protocol (RTP). Each endpoint may be a source and/or a destination of an RTP communication flow and have access to one or more encryption keys (e.g., end-to-end media encryption keys) to encrypt or decrypt the conferencing data. Other communication channels and/or protocols may also be used. For example, the endpoints 115 and 120 may use SCTP over DTLS for web RTC communications, BFCP, various file transfer protocols or application data channels, etc.
The one or more media distributors 125, also known as media distribution devices or media distribution servers, are network entities configured to receive and forward RTP data towards their destination. According to some embodiments, the media distributors 125 are not allowed to have access to the end-to-end media encryption keys and, as a result, do not have access to encrypted conferencing data. Furthermore, they may be restricted on what other types of data it can access or alter. For example, a media distributor may be restricted from altering certain fields in an RTP header containing conferencing data.
The one or more conference controllers 130 are network entities configured to establish and manage a conferencing session or perform call processing functions. Although various conferencing protocols may be used, for clarity, various aspects of the subject technology will be described with respect to a Session Initiated Protocol (SIP) configured to aid in the signaling and control of multimedia communication sessions.
The conference controllers 130 may be configured to maintain a SIP signaling relationship with each participant in the conference and ensure that the media streams that constitute the conference are available to the participants (e.g., the endpoints) in the conference. The conference controllers 130 may use of one or more mixers, each of which combines a number of input media streams to produce one or more output media streams. The focus uses the media policy to determine the proper configuration of the mixers.
The conference controllers 130 may use various notifications to the various network entities to coordinate the conferencing session. The conference controllers 130 may, for example, accept subscriptions from endpoints for a notification service associated with a conferencing session and generate notifications to them as the state of the conference changes. The state of the conference may include the participants connected to the conference and also information about the dialogs associated with them. As new participants join, this state changes, and is reported through the notification service. Similarly, when a participant leaves, the state of the conference also changes, allowing subscribers to learn about this fact. If a participant is anonymous, the conference notification service may either withhold the identity of a new participant from other conference participants, or will neglect to inform other conference participants about the presence of the anonymous participant.
The conference controller 130 may include one or more physical and/or logical components depending on the specific implementation. The conference controller 130 may be implemented as a centralized server or conference server or one or more SIP servers.
The one or more key management servers 135 are network entities configured to distribute keys and related information to other network entities as appropriate. For example, two different types of key information may be used. End-to-end key information (e.g., end-to-end encryption keys) is configured to secure communications from a source endpoint through one or more media distributors to a destination endpoint. Hop-to-hop key information (e.g., hot-to-hop and/or per-hop encryption keys) is configured to secure communications between an endpoint and a media distributor or between media distributors. The key management server 135 is configured to provide end-to-end key information to endpoints.
The key management server 135 may be implemented as a standalone key distributor network entity, collocated with an endpoint, or collocated with another network entity. Furthermore, the key management server 135 may be managed by an enterprise network or a third-party network that is separate from cloud network 110. However, because the key management server 135 plays an important role in securing conferencing data, the key management server 135 may be configured to be more secure and managed in a way to prevent or mitigate exploitation.
In order to provide more secure conferencing sessions using the cloud network 110, various aspects of the subject technology use trusted and untrusted statuses and assign these statuses to the various network entities in the cloud environment 100. Although various aspects use the terms “trusted” and “untrusted,” in other aspects, other terms such as trusted and semi-trusted, secured and unsecured, or other terms may be used to indicate a higher level of trustworthiness and a lower level of trustworthiness.
Aspects of the subject technology allow for untrusted or semi-trusted network entities allows for these entities to be hosted in the cloud network 110 and allows the conferencing system to leverage the benefits provided by cloud network 110, which may include a public network or a network of a conferencing provider where the trustworthiness is below the level required to ensure that the privacy of a participant's media will not be compromised.
Although the term “untrusted” or “semi-trusted” is used to describe these entities, these entities are still used in a conferencing session to reliably connect endpoints or in other non-media related aspects of hosting a conferencing session, but not trusted with key information needed to decrypt any of the participant's media (e.g., end-to-end key information). The one or more media distributors 125A and 125B and conference controller 130 are examples of untrusted entities.
Each media distributor is configured to forward conferencing data (e.g., RTP data flows) between endpoints participating in a conferencing session while performing per-hop authentication of each data packet (e.g., an RTP packet). The media distributor may obtain per-hop key information from the key management server 135. The media distributor may access to one or more data packet headers or header extensions and potentially add or modify portions of the data packet headers or extensions. The media distributor may also relay communications between an endpoint and the key management server 135. However, the key management server 135 does not provide the media distributor with end-to-end key information (e.g., end-to-end encryption keys configured to encrypt and/or decrypt the media content of the conferencing data).
The key management server 135 also does not provide the conference controller 130 with end-to-end key information. The conference controller 130 may be configured to process conferencing signaling messages, sign the conferencing signaling messages, and/or authenticate endpoints for call signaling or joining a conferencing session hosted through a set of media distributors.
Trusted entities are allowed access to end-to-end key information such as encryption keys configured to encrypt and/or decrypt the media content of the conferencing data flows. The one or more endpoints 115 and 120 and the key management server 135 are considered trusted entities.
The one or more endpoints 115 and 120 are considered trusted entities and have access to end-to-end key information. Although an endpoint may have additional security features, it may still be compromised. However, the endpoint will need to have the end-to-end key information to decrypt the media content of the conferencing data flows and present the media content to a user.
As described above, the key management server 135 is a trusted entity and configured to provide key information to media distributors 125 and the various endpoints 115 and 120 involved in a conferencing session. To enable end-to-end privacy and integrity, the key management server 135 restricts end-to-end key information to trusted entities. However, media distributors 125 do have access to RTP headers and header extensions and are able to authenticate packets hop-by-hop using hop-to-hop key information.
According to various aspects of the subject technology, end-to-end keys (E2E Keys) may be generated for each endpoint and configured to authenticate encryption of RTP media between endpoints. For example, an E2E Key(i) may be generated for endpoint i. Hop-to-hop keys (H2H Keys) may be generated for each hop between an endpoint and a media distributor or between media distributors. For example, H2H Key(j) may be generated for hop j.
A second layer of encryption is added on to the communication flow between the endpoints. For example, each hop between network entities is further encrypted by hop-to-hop keys. Conferencing data from endpoint A 215 to media distributor 225X is encrypted with H2H Key(AX), conferencing data from media distributor 225X to media distributor 225Y is encrypted with H2H Key(XY), and conferencing data from media distributor 225Y to endpoint B 220 is encrypted with H2H Key(YB).
According to various aspects of the subject technology, a Secure Real-time Transport Protocol (SRTP) may be used for the keying material and recommended cryptographic transform(s) for the H2H and E2E keys such that an endpoint may use an appropriate E2E key may be used to encrypt RTP media content and that encrypted output may be encrypted again using the appropriate H2H key. A media distributor may simply decrypt and/or encrypt the conferencing data flow using the appropriate H2H keys. According to other aspects however, other protocols may also be used.
According to various aspects of the subject technology, a key encryption key (KEK) may be used to ensure the confidentiality between E2E keys shared between endpoints. The KEK may be an Encrypted Key Transport (EKT) key configured to encrypt SRTP keys (e.g., the E2E keys) used for E2E authentication encryption of media sent by an endpoint.
To establish or generate an E2E key and H2H key for an endpoint and/or an H2H key for a media distributor, an association may be formed between an endpoint and the key management server. Media distributors may communicate directly with another media distributor to establish H2H keys for transmitting data to that media distributor. Protocols, such as Datagram Transport Layer Security (DTLS) Extension to Establish Keys for the Secure Real-time Transport Protocol (SRTP) and/or DTLS-SRTP may be used, in accordance with some aspects of the subject technology.
The association between each endpoint and the key management server 335 will enable each endpoint to receive E2E key information, Key Encryption Key (KEK) information (e.g., an EKT key), and H2H key information. The key management server 335 may also securely provide the H2H key information to the media distributor 325.
The endpoints 315 and 320 may establish an association over the RTP session's media ports for the purposes of key information exchange with the key management server 335. The media distributor forwards packets received from an endpoint on to the key management server 335 and vice versa via the tunnel 350 established between media distributor 325 and the key management server 335. The tunnel 350 may be configured to implement the signaling between the key management server 335 and the endpoints. The tunnel 350 may also be used to convey H2H key information from the key management server 335 to the media distributor 325.
After the initial key information exchange with the key management server 335, the endpoints 315 and 320 may be able to encrypt media end-to-end with their respective E2E key information, and send their respective E2E key information to other endpoints via the encrypted key transport (EKT) mechanism. The endpoints 315 and 320 will also be able to encrypt and authenticate RTP packets using the H2H key information.
However, there may be several shortcomings to the disclosed conferencing session. For example, a conferencing session may use various methods to authorize a participant to the conferencing session. For example, identity assertions or certificate fingerprints may be used by the key management server to verify that endpoints are authorized to participate in the conference. However, as discussed above, media distributors relied upon to establish associations between a key management server and endpoints and pass key information between the key management server and endpoints even though the media distributors are not trusted entities, may reside in a less secure network or portion of the network, and may be open to additional attacks.
If a media distributor were to become compromised, the media distributor may forward messages from endpoints that are not authorized to participate in a particular conferencing session to the key management server. The key management server may authenticate the user/endpoint, however the key management server relies on the media distributor to determine whether a user/endpoint is authorized as a participant in a conferencing session. Accordingly, an authenticated endpoint that is not a valid participant in a conferencing session may be added as a participant and receive conferencing data as well as key information that the endpoint may use to decrypt the conferencing data.
In another example, conference participants may not be aware of other recipients of conferencing session data to whom the key management server may have given KEK information to. This can lead to a scenario where an eavesdropper can listen to and view a conferencing session without other participants (e.g., the speakers) being aware that the eavesdropper is receiving the media stream. For example, a conferencing session may be compromised either because of an internal attack (e.g., disgruntled employee launching inside attack) or an external agency inserting implants to eavesdrop on a media session.
Various aspects of the subject technology address these and other technical problems by providing a mechanism for participants in a conferencing session to validate a participant list or conference roster. A participant in a conferencing session may validate a conference roster list by comparing a roster or a proxy for the roster received from a key management server with a roster or proxy for the roster received from another conferencing channel (e.g., a SIP communication channel). If there is a match, the roster is valid. If there is no match, the roster is invalid and the system or participant may take one or more actions to resolve the issue.
Although various aspects are described with respect to hash functions (e.g., a SHA-2 hash function) or hash values (e.g., a reference hash value, a roster hash value, etc.), other proxies for the roster or participant list may also be used. For example, the roster or participant list may be encoded by various techniques to generate various codes.
At operation 405, the system may join a conferencing session. There are various ways to join a conferencing session using various protocols. One such protocol discussed for illustrative purposes includes the Session Initiation Protocol (SIP) which supports the initiation, modification, and termination of conferencing sessions between endpoints. The conferencing sessions may be managed by SIP dialogs, which represent a SIP relationship between a pair of entities (e.g., endpoints) in the network. SIP may be used in communications between two or more endpoints and in architectures where there is no central point of control, in distributed multiparty conferencing where each participant may maintain signaling relationships with other participants, in architectures that include a central point of control, or a combination thereof.
For example, the system may send an invite to a conference controller (e.g., a SIP focus entity configured to maintain a SIP signaling relationship with each participant in the conference). The conference controller may authenticate the system for the purpose of conference signaling based on, for example, conference policies stored in a conference policy database. If the system is authenticated, the system is added to the conference, which may be represented by a universal resource identifier (URI). Alternatively, the conference controller may also send an invite to the system, the system may transmit an invite acceptance to the conference controller, and the conference controller may add the system to the conference.
The conference is hosted through one or more media distributors and, as a result, the key management server and the media distributors hosting the conference are configured to establish one or more tunnels (e.g., Transport Layer Security (TLS) protocol connections) between each other to facilitate an initial key exchange and key exchanges during the conference, as described above. Once the tunnels between the media distributors and the key management server are established, the system may use one or more of the tunnels to establish encryption and authentication keys with the key distributor, for example, by using DTLS-SRTP protocols. Once the appropriate keying information is provided to the system, the media distributors, and other endpoints in the conference, the conferencing session may proceed.
At operation 410, the system may obtain a roster for the conferencing session. The roster may be implemented as a list of participants in the conferencing session and may be obtained at once (e.g., the whole roster), piecemeal (e.g., one participant at a time), and/or updated continually (e.g., receiving whole roster updates, adding one participant to the roster, removing one participant from the roster, etc.).
According to some aspects of the subject technology, the system may obtain a roster through SIP signaling messages from a conference controller. For example, as provided by a SIP framework, the conference controller may provide a conference notification service and may accept subscriptions from endpoints in the conferencing session, monitor the state of the conference, generate notifications as the state of the conference changes, and transmit the notifications to the subscribers for the conferencing session.
The state of the conference includes the participants of the conferencing session (e.g., the endpoints that the conference controller has added to the conferencing session) as well as information about the dialogs associated with the participants. As new participants are added by the conference controller the state changes and the change is reported through the notification service. Similarly, when a participant leaves or is removed by the conference controller the state changes and this change is also reported to subscribers.
The system may be subscribed to the conference notification service provided by the conference controller when the conference controller added the system to the conferencing session or via a separate transaction. Once subscribed to the conference notification service, the system may receive notifications from the conference controller indicating that a participant has been added or removed from the conferencing session. The system may use these notifications to generate the roster.
As participants are added to the conferencing session, the participants obtain keying information by contacting the key management server via one of the tunnels established between the key management server and the media distributors. When contacted by a participant, the key management server validates the participant and provides appropriate key information to the participant.
The key management server may also extract the identity of the participant and add identity to a list of participants in the conferencing session. As described above, the validation of the participant may be through identity assertions, certificate fingerprints, or other means. Accordingly, the key management server may extract the identity of the participant from the certificate or request and receive the identity of the participant from an identity provider.
The key management server may sort the list of participants in various ways and generate a reference hash value of the list of participants. According to some implementations, the list of participants may be sorted by alphabetical order. However other factors or combinations of factors may also be used to sort the list of participants. The reference hash value may be generated based on a SHA-2 hash function, or some other hash function. The key management server may transmit this reference hash value to the system.
At operation 415, the system receives the reference hash value from the key management server. At operation 420, the system may sort the participants in the roster obtained in operation 410 and generate a roster hash value based on that roster. The system may sort the participants in the roster in a similar manner to the key management server such as, for example, in alphabetical order. Similarly the system may use the same hash function as the key management server (e.g., a SHA-2 hash function).
At operation 425, the system compares the roster hash value to the reference hash value received from the key management server to determine whether the roster hash value is equivalent to the reference hash value. If the roster hash value is the same as the reference hash value, then the key management server is likely to have the same list of participants as the conference controller and the system. Accordingly, at operation 430, the system validates the roster (e.g., determines that the roster is valid) and may continue the conferencing session.
If the roster hash value is not equivalent to the reference hash value, it is likely that the key management server does not have the same list of participants as the conference controller and the system. This may indicate the possibility of the existence of an eavesdropper or that the conferencing session is otherwise compromised. For example, the key management server may have provided key information for one or more endpoints that are not in the roster that the system has obtained in operation 410. Accordingly the system, at operation 435, determines that the roster for the conferencing session is invalid (e.g., the roster cannot be validated) and may respond accordingly.
According to some implementations, the system may notify the other participants in the conferencing session that the conferencing session may be compromised, leave the conferencing session, end the conferencing session, or attempt to resolve the conflict. For example, the system may notify an application running on the system (e.g., conferencing software, a browser, etc.) or a user of the system that there may be an unknown listener on the conferencing session and the user may ask that the unknown user to leave the conferencing session. Alternatively, or additionally, the system may notify other applications running on the other endpoints that there may be an unknown listener on the conferencing session and ask the unknown user to leave.
After a period of time configured to give the unknown user an opportunity to leave and the conferencing entities time to detect the leaving of the unknown user, the system may check again to see whether the roster can be validated. For example, the process may return to operation 410 to obtain a new roster for the conferencing session, receive a new reference hash value from the key management server, generate a new roster hash value based on the new roster, and attempt to validate the new roster based on a comparison of the new roster hash value and the new reference hash value.
In an illustrative scenario, a conferencing session may be established to interview several candidates. Once a candidate has finished his interview, the interviewer may ask the candidate to drop off of the conferencing session or remove the candidate from the conferencing session. To prevent the candidate from eavesdropping on the remainder of the conferencing session, the interviewer's conferencing application may request the candidate to drop off from the conferencing session and/or ensure that the candidate is no longer able to decrypt the media. The client application may perform cross-checks with the key management server to determine whether the candidate is still a part of the list of updated listeners authorized to receive the updated KEK. If the candidate is not a part of the list of updated listeners, the conferencing session may continue. If the candidate is still a part of the list of updated listeners, the client application may notify the interviewer and/or ask the candidate again to drop off the conferencing session until cross checks indicate that the candidate is no longer a part of the updated list of listeners.
According to some aspects, if the roster is invalid, the system may send the roster obtained to the key management server where the key management server may compare the roster from the system to the list of participants tracked by the key management server to specifically identify an unknown user. The unknown user may then be removed from the conferencing session. The key management server may also, or alternatively, send the list of participants it has tracked to the system where the system may compare the roster from the system to the list of participants tracked by the key management server to specifically identify an unknown user.
According to some aspects, the key management server may categorize participants into speakers (e.g., content generators) and receivers (e.g., content receivers) depending on the key information received by each participant. In some cases the participant may be both speaker and receiver. The key management server may build a separate list of identities for speaker participants and for receiver participants or the list of identities may specify whether each identity corresponds to a speaker participant, a receiver participant, or a participant that is both a speaker and a receiver. The reference hash value may be calculated based on the list of receivers and be transmitted to the system where it may be compared to the roster hash value in operation 425.
According to some aspects of the subject technology, not all participants in a conferencing session may be configured to validate the roster. For example, when the participant list is large, the key management server may nominate a specific set of participants in the conference call to validate the roster. The key management server may nominate the participants based on whether the participant is a speaker and/or whether the participant has a high reputation score. The reputation score may be calculated in various ways based on various signals.
According to some aspects, one participant in the nominated set of participants may validate the roster. For example, the key management server detect that a new participant or recipient participant has been added to the conferencing session or a participant has left the conferencing session. In response, the key management server may use a round-robin technique to select one participant in the nominated set of participants to validate the roster and transmit instructions to the selected participant to validate the roster. The next time the key management server detects a change to the list of participants in the conferencing session, the next participant in the nominated set of participants may validate the roster.
As discussed above, a conference controller residing in the cloud network may become compromised. In a compromised state, the conference controller may send a participant list that includes unauthorized participants to other participants of a conferencing session. According to various aspects of the subject technology, this attack may be addressed by allowing a new participant to join an on-going conferencing session only if one of the other participants in the conferencing session sends a new message signaling the identity of the new participant to all other participants through the conference controller. However, because the conference controller is not a trusted entity (e.g., the conference controller may be untrusted or semi-trusted), this new message must be signed by the participant's client application (e.g. the participant gets short-term certificate from an identity provider and uses an Elliptic Curve Digital Signature Algorithm (ECDSA) to sign the new message).
The other participants in the conferencing session may validate the digital signature of the new message and identify that the new participant is indeed added by an existing participant in the conferencing session. For example, a client application for a speaker in the conferencing session may compare the identity of the new participant received from the key management server with the identity of the participant received in the new message. If they do not match then the speaker's client application may transmit instructions to the key management server to not permit the new participant to receive the KEK.
To enable user interaction with the computing device 500, an input device 545 can represent any number of input mechanisms, such as a microphone for speech, a touch-sensitive screen for gesture or graphical input, keyboard, mouse, motion input, speech and so forth. An output device 535 can also be one or more of a number of output mechanisms known to those of skill in the art. In some instances, multimodal systems can enable a user to provide multiple types of input to communicate with the computing device 500. The communications interface 540 can generally govern and manage the user input and system output. There is no restriction on operating on any particular hardware arrangement and therefore the basic features here may easily be substituted for improved hardware or firmware arrangements as they are developed.
Storage device 530 is a non-volatile memory and can be a hard disk or other types of computer-readable media which can store data that are accessible by a computer, such as magnetic cassettes, flash memory cards, solid state memory devices, digital versatile disks, cartridges, random access memories (RAMs) 525, read only memory (ROM) 520, and hybrids thereof.
The storage device 530 can include software modules 532, 534, 536 for controlling the processor 510. Other hardware or software modules are contemplated. The storage device 530 can be connected to the system bus 505. In one aspect, a hardware module that performs a particular function can include the software component stored in a computer-readable medium in connection with the necessary hardware components, such as the processor 510, bus 505, display 535, and so forth, to carry out the function.
Chipset 560 can also interface with one or more communication interfaces 590 that can have different physical interfaces. Such communication interfaces can include interfaces for wired and wireless local area networks, for broadband wireless networks, as well as personal area networks. Some applications of the methods for generating, displaying, and using the GUI disclosed herein can include receiving ordered datasets over the physical interface or be generated by the machine itself by processor 555 analyzing data stored in storage 570 or 575. Further, the machine can receive inputs from a user via user interface components 585 and execute appropriate functions, such as browsing functions by interpreting these inputs using processor 555.
It can be appreciated that example systems 500 and 550 can have more than one processor 510 or be part of a group or cluster of computing devices networked together to provide greater processing capability.
For clarity of explanation, in some instances the present technology may be presented as including individual functional blocks including functional blocks comprising devices, device components, steps or routines in a method embodied in software, or combinations of hardware and software.
In some embodiments the computer-readable storage devices, mediums, and memories can include a cable or wireless signal containing a bit stream and the like. However, when mentioned, non-transitory computer-readable storage media expressly exclude media such as energy, carrier signals, electromagnetic waves, and signals per se.
Methods according to the above-described examples can be implemented using computer-executable instructions that are stored or otherwise available from computer-readable media. Such instructions can comprise, for example, instructions and data which cause or otherwise configure a general purpose computer, special purpose computer, or special purpose processing device to perform a certain function or group of functions. Portions of computer resources used can be accessible over a network. The computer executable instructions may be, for example, binaries, intermediate format instructions such as assembly language, firmware, or source code. Examples of computer-readable media that may be used to store instructions, information used, and/or information created during methods according to described examples include magnetic or optical disks, flash memory, USB devices provided with non-volatile memory, networked storage devices, and so on.
Devices implementing methods according to these disclosures can comprise hardware, firmware and/or software, and can take any of a variety of form factors. Typical examples of such form factors include laptops, smart phones, small form factor personal computers, personal digital assistants, and so on. Functionality described herein also can be embodied in peripherals or add-in cards. Such functionality can also be implemented on a circuit board among different chips or different processes executing in a single device, by way of further example.
The instructions, media for conveying such instructions, computing resources for executing them, and other structures for supporting such computing resources are means for providing the functions described in these disclosures.
Although a variety of examples and other information was used to explain aspects within the scope of the appended claims, no limitation of the claims should be implied based on particular features or arrangements in such examples, as one of ordinary skill would be able to use these examples to derive a wide variety of implementations. Further and although some subject matter may have been described in language specific to examples of structural features and/or method steps, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to these described features or acts. For example, such functionality can be distributed differently or performed in components other than those identified herein. Rather, the described features and steps are disclosed as examples of components of systems and methods within the scope of the appended claims.
