Method and system for telecommunication session output integration

A method and system for integrating telecommunication session output with one or more applications are provided herein. The method for integrating telecommunication session output with one or more applications includes communicating with one or more second devices in a telecommunication session using a first application disposed on a first device; tracking attributes associated with the telecommunication session; recording at least a portion of the telecommunication session on the first device to produce a session recording; and storing the attributes and at least one of the session recording, or a text transcription of the session recording in a second application on the first device.

BACKGROUND

Field

Embodiments of the present invention generally relate to methods and systems for telecommunication session output integration, and more particularly, to a method and system for creating post-call reminders.

Description of the Related Art

Often, after a telecommunication session, a mobile phone user needs to record information discussed during the telecommunication session, or schedule tasks in response to the discussion. For example, the user may set a reminder to call a person, or record a note to ask said person about a given topic. Each of these tasks requires manual entry on the part of the user. Manual entry of tasks is time consuming and inefficient. In addition, manually noting what was discussed during a session may be inaccurate and incomplete.

Therefore, there exists a need in the art for a method and system for integrating telecommunication session output with one or more applications.

SUMMARY

A method and system for integrating telecommunication session output with one or more applications are provided herein. In some embodiments, a method for integrating telecommunication session output with one or more applications may include communicating with one or more second devices in a telecommunication session using a first application disposed on a first device; tracking attributes associated with the telecommunication session; recording at least a portion of the telecommunication session on the first device to produce a session recording; and storing the attributes and at least one of the session recording, or a text transcription of the session recording in a second application on the first device.

In some embodiments, a method for integrating telecommunication session output with one or more applications may include communicating with one or more second devices in a telecommunication session using a first application disposed on a first device, tracking attributes associated with the telecommunication session, receiving an input indicating a task associated with the telecommunication session to send to one or more second devices, generating a message comprising the task and at least some of the tracked attributes, and transmitting the message to the one or more second devices.

In some embodiments, a system for integrating telecommunication session output with one or more applications, may include a mobile application configured to: communicate with one or more second devices in a telecommunication session using a first application disposed on a first device; track attributes associated with the telecommunication session; record at least a portion of the telecommunication session on the first device to produce a session recording; and store the attributes and at least one of session recording, or a text transcription of the session recording in a second application on the first device.

In some embodiments, a computer readable medium for integrating telecommunication session output with one or more applications is disclosed. The computer readable medium comprises instructions that when executed by at least one processor causes the at least one processor to perform the method for integrating telecommunication session output with one or more applications.

DETAILED DESCRIPTION

Embodiments of the present invention generally relate to a method and system for integrating telecommunication session output with one or more applications (also referred to as apps herein). More specifically, embodiments of the present invention enable recording of a telecommunication session. The telecommunication session may be recorded in part or in its entirety. In some embodiments, permission from all participants of the telecommunication session is received prior to recording the telecommunication session communications. After the telecommunication session has ended, either the recording itself or a text version/transcript of the recording is stored on a user's device in an application of the user's choosing, for example, a calendar app, a notes app, or the like. In some embodiments, permission from the participants is requested and verified prior to storing/using the recording or transcript of the recording. In addition, the user is prompted to store other tasks or reminders. For example, the user may store a reminder to ask a specific person a question next time the user and the person speak. The reminder may be stored in a notes app and linked to the person's contact information such that when the person calls, the reminder is displayed to the user. Other tasks may include storing a location in a map app, storing a time in the calendar app when to place a call, and the like. Further, a task may be sent to a participant in the telecommunication session and placed in an application on the participant's mobile device. For example, a first participant on a first device may send a task to a second participant's device to place a reminder on the second participant's calendar app reminding the second participant to call the first participant at a later specified time. Thus, embodiments of the present invention advantageously provide a user in a telecommunication session an ability to store reminders and tasks in one or more applications on the user's device or a participant's device.

Some exemplary embodiments described below are with respect to a mobile Voice over Internet Protocol (VOIP) telecommunication app. However, one skilled in the art will readily recognize from the following description that any native application may be used in embodiments consistent with the present invention without departing from the principles of the disclosure described herein.

In the following description, the terms VOIP system, VOIP telephony system, IP system and IP telephony system are all intended to refer to a system that connects callers and that delivers data, text and video communications using Internet protocol data communications. Those of ordinary skill in the art will recognize that embodiments of the present invention are not limited to use with IP telephony systems and may also be used in other systems.

As illustrated inFIG. 1, a communications environment100is provided to facilitate IP enhanced communications. An IP telephony system120enables connection of telephone calls between its own customers and other parties via data communications that pass over a data network110. The data network110is commonly the Internet, although the IP telephony system120may also make use of private data networks. The IP telephony system120is connected to the Internet110. In addition, the IP telephony system120is connected to a publicly switched telephone network (PSTN)130via a gateway122. The PSTN130may also be directly coupled to the Internet110through one of its own internal gateways (not shown). Thus, communications may pass back and forth between the IP telephony system120and the PSTN130through the Internet110via a gateway maintained within the PSTN130.

The gateway122allows users and devices that are connected to the PSTN130to connect with users and devices that are reachable through the IP telephony system120, and vice versa. In some instances, the gateway122would be a part of the IP telephony system120. In other instances, the gateway122could be maintained by a third party.

Customers of the IP telephony system120can place and receive telephone calls using an IP telephone108that is connected to the Internet110. Such an IP telephone108could be connected to an Internet service provider via a wired connection or via a wireless router. In some instances, the IP telephone108could utilize a packet-switched network of a cellular telephone system to access the Internet110.

Alternatively, a customer could utilize an analog telephone102which is connected to the Internet110via a telephone adapter104. The telephone adapter104converts analog signals from the telephone102into data signals that pass over the Internet110, and vice versa. Analog telephone devices include but are not limited to standard telephones and document imaging devices such as facsimile machines. A configuration using a telephone adapter104is common where the analog telephone102is located in a residence or business. Other configurations are also possible where multiple analog telephones share access through the same IP adaptor. In those situations, all analog telephones could share the same telephone number, or multiple communication lines (e.g., additional telephone numbers) may provisioned by the IP telephony system120.

In addition, a customer could utilize a soft-phone client running on a computer106or a television109to place and receive IP based telephone calls, and to access other IP telephony systems (not shown). The computer106may be a personal computer (PC), a tablet device, a gaming system, and the like. In some instances, the soft-phone client could be assigned its own telephone number. In other instances, the soft-phone client could be associated with a telephone number that is also assigned to an IP telephone108, or to a telephone adaptor104that is connected to one or more analog telephones102.

Users of the IP telephony system120are able to access the service from virtually any location where they can connect to the Internet110. Thus, a customer could register with an IP telephony system provider in the U.S., and that customer could then use an IP telephone108located in a country outside the U.S. to access the services. Likewise, the customer could also utilize a computer outside the U.S. that is running a soft-phone client to access the IP telephony system120.

A third party using an analog telephone132which is connected to the PSTN130may call a customer of the IP telephony system120. In this instance, the call is initially connected from the analog telephone132to the PSTN130, and then from the PSTN130, through the gateway122to the IP telephony system120. The IP telephony system120then routes the call to the customer's IP telephony device. A third party using a cellular telephone134could also place a call to an IP telephony system customer, and the connection would be established in a similar manner, although the first link would involve communications between the cellular telephone134and a cellular telephone network. For purposes of this explanation, the cellular telephone network is considered part of the PSTN130.

In the following description, references will be made to an “IP telephony device.” This term is used to refer to any type of device which is capable of interacting with an IP telephony system to complete an audio or video telephone call or to send and receive text messages, and other forms of communications. An IP telephony device could be an IP telephone, a computer running IP telephony software, a telephone adapter which is itself connected to a normal analog telephone, or some other type of device capable of communicating via data packets. An IP telephony device could also be a cellular telephone or a portable computing device that runs a software application that enables the device to act as an IP telephone. Thus, a single device might be capable of operating as both a cellular telephone that can facilitate voice based session calls, and an IP telephone that can facilitate data based session calls.

The following description will also refer to a mobile telephony device. The term “mobile telephony device” is intended to encompass multiple different types of devices. In some instances, a mobile telephony device could be a cellular telephone. In other instances, a mobile telephony device may be a mobile computing device, such as the APPLE IPHONE, that includes both cellular telephone capabilities and a wireless data transceiver that can establish a wireless data connection to a data network. Such a mobile computing device could run appropriate application software to conduct VoIP telephone calls via a wireless data connection. Thus, a mobile computing device, such as an APPLE IPHONE, a RIM BLACKBERRY or a comparable device running GOOGLE ANDROID operating system could be a mobile telephony device.

In still other instances, a mobile telephony device may be a device that is not traditionally used as a telephony device, but which includes a wireless data transceiver that can establish a wireless data connection to a data network. Examples of such devices include the APPLE IPOD TOUCH and the IPAD. Such a device may act as a mobile telephony device once it is configured with appropriate application software, sometimes referred to as an “over-the-top” (or “OTT”) telecommunication application, as it provides a service over the wireless data connection.

FIG. 1illustrates that a mobile computing device with cellular capabilities136A(e.g., a smartphone) is capable of establishing a first wireless data connection A with a first wireless access point140, such as a WiFi or WiMax router. The first wireless access point140is coupled to the Internet110. Thus, the mobile computing device136Acan establish a VOIP telephone call with the IP telephony system120via a path through the Internet110and the first wireless access point140.

FIG. 1also illustrates that the mobile computing device136Acan establish a second wireless data connection B with a second wireless access point142that is also coupled to the Internet110. Further, the mobile computing device136Acan establish either a third wireless data connection C via a packet-switch network provided by a cellular service provider130using its cellular telephone capabilities, or establish a voice based session telephone call via a circuit-switched network provided by a cellular service provider130. The mobile computing device136Acould also establish a VoIP telephone call with the IP telephony system120via the second wireless connection B or the third wireless connection C.

Although not illustrated inFIG. 1, the mobile computing device136Amay be capable of establishing a wireless data connection to a data network, such as the Internet110, via alternate means. For example, the mobile computing device136Amight link to some other type of wireless interface using an alternate communication protocol, such as the WIMAX standard.

Similarly, mobile computing device with cellular capabilities136Bmay also be coupled to internet110and/or cellular service provider130. In some embodiments, mobile computing device136Bmay be connected to internet110via a WIFI or WIMAX connection, and the like, and can also establish a VOIP telephone calls with the IP telephony system120similar to mobile computing device136A. In embodiments of the present invention, communications environment100may be used to establish voice based or data based telecommunications sessions between mobile computing device136Aand mobile computing device136B, depending on various criteria associated with each of the mobile computing devices, as will be described below in more detail.

In the embodiments described above, a device may act as a mobile telephony device once it is configured with appropriate application software that may be downloaded from an app distribution platform144. For example, mobile computing device136Amay download a VOIP mobile app from app distribution platform144and install the VOIP mobile app locally making the app a native application running on mobile computing device136A.

FIG. 2depicts a block diagram of a system200for integrating telecommunication session output with one or more applications, according to one or more embodiments. The system200includes at least one telecommunication service provider server206that can provide telecommunication services to a plurality of end-user devices (e.g., such as User A device202and User B device204) via one or more networks208. Devices202and204may include a computer with IP software106, IP telephone108, and/or mobile computing device with cellular capabilities136A,136B, and the like, as shown inFIG. 1. The telecommunication service provider server206may include IP telephone system120or PSTN/cellular provider130.

Each user device (e.g., User A device202and User B device204) comprises a Central Processing Unit (CPU)210, support circuits212, display214, and a memory216. The CPU210may comprise one or more commercially available microprocessors or microcontrollers that facilitate data processing and storage. The various support circuits212facilitate the operation of the CPU210and include one or more clock circuits, power supplies, cache, input/output circuits, and the like. The memory216comprises at least one of Read Only Memory (ROM), Random Access Memory (RAM), disk drive storage, optical storage, removable storage and/or the like. In some embodiments, the memory216comprises an operating system218, a mobile application220, a calendar app230, a notes app232, and one or more other apps234. The mobile application207may include a communication module222, a call recording module224, an after call utility module226, and user settings228. In some embodiments, the mobile application220may be an OTT telecommunication application as described above.

The operating system (OS)218generally manages various computer resources (e.g., network resources, file processors, and/or the like). The operating system218is configured to execute operations on one or more hardware and/or software modules, such as Network Interface Cards (NICs), hard disks, virtualization layers, firewalls and/or the like. Examples of the operating system218may include, but are not limited to, LINUX, MAC OSX, BSD, UNIX, MICROSOFT WINDOWS,10S, ANDROID and the like.

The telecommunication service provider server206may include a call management system236. The call management system236may include a Central Processing Unit (CPU)238, support circuits240, and a memory244. The CPU238may comprise one or more commercially available microprocessors or microcontrollers that facilitate data processing and storage. The various support circuits240facilitate the operation of the CPU238and include one or more clock circuits, power supplies, cache, input/output circuits, and the like. The memory244comprises at least one of Read Only Memory (ROM), Random Access Memory (RAM), disk drive storage, optical storage, removable storage and/or the like. The memory244includes an operating system246, a notification module248, and a messaging system250. The messaging system250may be any system that facilitates the sending and receiving of SMS and MMS message, OTT messaging app messages, and the like.

The operating system246generally manages various computer resources (e.g., network resources, file processors, and/or the like). The operating system246is configured to execute operations on one or more hardware and/or software modules, such as Network Interface Cards (NICs), hard disks, virtualization layers, firewalls and/or the like. Examples of the operating system246may include, but are not limited to, LINUX, MAC OSX, BSD, UNIX, MICROSOFT WINDOWS, IOS, ANDROID and the like.

The networks208comprise one or more communication systems that connect computers by wire, cable, fiber optic and/or wireless link facilitated by various types of well-known network elements, such as hubs, switches, routers, and the like. The networks208may include an Internet Protocol (IP) network110, a public switched telephone network (PSTN)130, or other mobile communication networks, and may employ various well-known protocols to communicate information amongst the network resources.

In operation, user A device202may initiate a call to user B device204. Call management system236of service provider server206establishes the call between user A device202and user B device204. In some embodiments, the service provider server206may be a VoIP service provider server and the call between user A device202and user B device may be a VoIP call over a VoIP network. In a VoIP network, the call request oftentimes takes the form of a Session Initiation Protocol (SIP) INVITE message sent from user A device202to a call management system236. In a VoIP network, the call management system236may be, for example, part of a SIP Proxy Network. The details and functionality of SIP can be found in the Internet Engineering Task Force (IETF) Request for Comments (RFC) Paper No. 3261 entitled, “SIP: Session Initiation Protocol” herein incorporated in its entirety by reference. Although the present disclosure describes embodiments involving calls between two participants, the call may include two or more participants. In some embodiments, the call recording module224on user A device202and user B device204displays a prompt requesting permission to record the call. In some embodiments, the responses to the prompt are sent via the messaging system250to user A device202. In other embodiments, the responses may be sent via User Datagram Protocol (UDP) datagrams or Transmission Control Protocol (TCP) data packets. The call recording module224of user A device202determines whether all participants have granted permission based on the responses received. In some embodiments, the call recording module224may generate a notification message (e.g., via an SMS message, UDP datagram, etc.) indicating the recording status of the telecommunication session, for example, “Call may be recorded” or “Call is not being recorded”. The communication module222transmits the message to the service provider server206, where the notification module248forwards the message to each participant's user device. The call recording module224displays the message on display214. Based on user setting228, call information may be tracked during the call. Call information includes attributes of the call, for example, participants on the call, call duration, call quality, and the like. While the call is in progress, if recording is enabled, the user of user A device202may select to start and/or stop recording at any time during the call in order to record parts of the call or to record the call in its entirety. The call recording module224records the selected conversations during the call. In some embodiments, when the call is ended, the call recording module224may once again prompt each participant to verify permission to store the recording of the call. If all participants grant permission, the after-call utility module226prompts the user to identify in what application the user would like to store the recording of the call. In other embodiments, permission from all participants may not be required and the after-call utility module226prompts the user to identify in what application the user would like to store the recording of the call as soon as the call has ended. For example, the user may select the calendar app230so the user may refer back to the date of the call on the calendar app230and listen to the recorded portions of the call. Alternatively, the user may select to convert the audio to text. The user may select to store the text of the conversation on the calendar app230, the notes app232, or another app234on the user A device202.

The after call utility module226then displays a prompt on the user A device202providing options of other after-call tasks or reminders. For example, the user may select an option to store the tracked call information on the calendar. The information may be linked to contact information of the participants on the call, such that when a participant calls user A device202, the call information may be displayed, thereby reminding the user of user A device202of their last call. Alternatively, the user may select an option to store a reminder to the calendar app230to call a participant at a later date. The user may store any desired information about the call on any available app on the user A device202.

The after-call utility module226may also prompt the user to set a task in an application on a participant's device, for example, on the calendar app230of user B device204. For example, the user may select an option to place a reminder on the calendar app230of user B device204to call the user at a specific date and time. The task is transmitted from the user A device202to the service provider server206, specifying the task to be stored and an app on user B device204in which to store the task. The notification module248identifies one or more participants who are to receive the task and transmits the task to the user device of the one or more identified participants, for example user B device204. The mobile app220of user B device204parses the task received from the notification module248and stores the task in the specified app.

FIG. 3depicts a flow diagram of a method300for integrating telecommunication session output with one or more applications, according to one or more embodiments of the invention. The method300begins at step302and proceeds to step304.

At step304, a communication session, for example, an audio call is established between a user who initiates the call and one or more participants. The user initiates the call from a mobile device that includes a mobile app, such as a mobile Voice over Internet Protocol (VOIP) telecommunication app.

At step306, information regarding the call is tracked based on user settings. User settings within the mobile app may include participant identities, call duration, call quality and the like. The information specified by the user settings is tracked for the duration of the call.

At step308, optionally, a request for permission to record the call is sent from the device of the user who initiated the call to each of the one or more participants. The request is sent to a service provider server of the provider of the mobile app. The request is forward to each of the one or more participants.

At step310, it is optionally determined whether all participants on the call have granted permission to record the call. In some embodiments, the call recording module224on the user device202determines whether each participant on the call granted permission to record the call. If permission is not granted by all participants, the method300proceeds to step322.

At step322, a message is displayed on the user device indicating that the call is not being recorded. The message is also sent via the service provider server to the other participants on the call to inform the other participants that the call is not being recorded. The call continues without being recorded. At step324, it is determined whether the call has ended. If the call has not ended, the call continues as the method300waits until the call has ended at which time, the method300proceeds to step326.

However, if at step310, it is determined that all participants on the call have granted permission to record the call, the method300proceeds to step312. At step312, a message is displayed on the user device indicating that recording of the call is enabled. The message is also sent via the service provider server to the other participants on the call to inform the other participants that recording of the call is enabled. In some embodiments, the call is automatically recorded in its entirety. In some embodiments, the recording may be started and stopped, such that excerpts of the call are recorded, rather than the entire call.

At step314, it is determined whether the call has ended. If the call has not ended, the call continues as the method300waits until the call has ended, at which time, the method300proceeds to step316.

At step316, optionally, a request to verify permission to store the call is sent from the device of the user who initiated the call to each of the one or more participants. The request is sent in order to give participant an opportunity to stop storage of the recording based on what was discussed on the call. The request is sent to a service provider server of the provider of the mobile app. The request is forward to each of the one or more participants.

At step318, it is optionally determined whether all participants on the call have verified permission to store the call. If permission is verified by all participants, the method300proceeds to step320. At step320, a user is prompted to select a storage location for the recording. The user is prompted to select an application from the plurality of applications on the user's device in which to store the recording. In some embodiments, the user may select to store an audio recording of the call or store a text version of the recording. For example, the user may select an option to convert the audio to text and store it in a calendar app on the date of the call. The user may select an option to store the text in a notes app of the user's device. The user may store the recording in one or more applications on the user's device. The method300proceeds to step326.

However if at step318, permission is not verified by all participants at the end of the call, the method300skips storage of the recording and proceeds to step326.

At step326, the method300prompts the user to select one or more post-call tasks to be performed. For example, the user may select an option to store the information tracked per user settings in a calendar app to maintain a record of the call. In some embodiments, the user may select an option to link the tracked information in the calendar app to contact information for the participants on the call. The user may select an option to enter a note regarding the call and have the note linked to the tracked information in the calendar app and/or linked to a contact associated with the entered note. The user may select an option to store a location in, for example, a map app to in order to identify a location discussed during the call. Any information may be stored in any application on the user device and linked to the call information and/or contact information.

In addition, the user may select an option to place any information regarding the call to be placed in an application on one or more participants' devices. The user may select an option to place a task in an application on the device of one or more participants. For example, the user may choose to place a task in a participant's calendar application reminding the participant to call the user back at a specific date and time.

At step328, the one or more options selected by the user are performed. Information, tasks, and reminders are stored in the one or more applications selected by the user. Application Program Interfaces (APIs) are used to interface with the one or more applications selected by the user. For example, on an ANDROID device, apps may subscribe to ANDROID events. In order for the mobile app to make a change in a calendar app, the mobile app subscribes to events regarding changes in calendar events. When the user selects to place information, tasks, or reminders in the calendar app, the mobile app triggers an ANDROID OS event of type calendar, and all of the apps listening to events of type calendar act according to the event prompted. The user may be provided an option to select which calendar app to use to complete the task. On an iOS, the operating system provides a list of calendars. Each calendar object implements APIs that outside apps may use to add/edit/remove events from a selected calendar.

In the event the user selects to place a task in an application of a participant, a message is sent to the identified participant. For example, the message format may be Extensible Markup Language (XML) where each tag represents either a text value or a name of a file (e.g., a call recording). A mobile app on the participant device stores the identified task in the specified app using APIs as described above. Files that are created by a user, for example, a call recording, are uploaded to a service provider server. The app on the participant's device interprets the text values and/or sends a request to the server for the file. After the app on the participant's device receives the file from the service provider server, the app stores the data in the participant's device. The messages are sent between the user devices and the service provider server using a TCP/IP protocol. The method300proceeds to step330and ends.

FIG. 4depicts a computer system400that can be utilized in various embodiments of the present invention to implement the computer and/or the display, according to one or more embodiments.

Various embodiments of method and apparatus for organizing, displaying and accessing contacts in a contact list, as described herein, may be executed on one or more computer systems, which may interact with various other devices. One such computer system is computer system400illustrated byFIG. 4, which may in various embodiments implement any of the elements or functionality illustrated inFIGS. 1-5. In various embodiments, computer system400may be configured to implement methods described above. The computer system400may be used to implement any other system, device, element, functionality or method of the above-described embodiments. In the illustrated embodiments, computer system400may be configured to implement the method300as processor-executable executable program instructions422(e.g., program instructions executable by processor(s)410) in various embodiments.

In the illustrated embodiment, computer system400includes one or more processors410a-410ncoupled to a system memory420via an input/output (I/O) interface430. Computer system400further includes a network interface440coupled to I/O interface430, and one or more input/output devices450, such as cursor control device460, keyboard470, and display(s)480. In various embodiments, any of the components may be utilized by the system to receive user input described above. In various embodiments, a user interface may be generated and displayed on display480. In some cases, it is contemplated that embodiments may be implemented using a single instance of computer system400, while in other embodiments multiple such systems, or multiple nodes making up computer system400, may be configured to host different portions or instances of various embodiments. For example, in one embodiment some elements may be implemented via one or more nodes of computer system400that are distinct from those nodes implementing other elements. In another example, multiple nodes may implement computer system400in a distributed manner.

In various embodiments, computer system400may be a uniprocessor system including one processor410, or a multiprocessor system including several processors410(e.g., two, four, eight, or another suitable number). Processors410may be any suitable processor capable of executing instructions. For example, in various embodiments processors410may be general-purpose or embedded processors implementing any of a variety of instruction set architectures (ISAs). In multiprocessor systems, each of processors410may commonly, but not necessarily, implement the same ISA.

System memory420may be configured to store program instructions422and/or data432accessible by processor410. In various embodiments, system memory420may be implemented using any suitable memory technology, such as static random access memory (SRAM), synchronous dynamic RAM (SDRAM), nonvolatile/Flash-type memory, or any other type of memory. In the illustrated embodiment, program instructions and data implementing any of the elements of the embodiments described above may be stored within system memory420. In other embodiments, program instructions and/or data may be received, sent or stored upon different types of computer-accessible media or on similar media separate from system memory420or computer system400.

In one embodiment, I/O interface430may be configured to coordinate I/O traffic between processor410, system memory420, and any peripheral devices in the device, including network interface440or other peripheral interfaces, such as input/output devices450. In some embodiments, I/O interface430may perform any necessary protocol, timing or other data transformations to convert data signals from one component (e.g., system memory420) into a format suitable for use by another component (e.g., processor410). In some embodiments, I/O interface430may include support for devices attached through various types of peripheral buses, such as a variant of the Peripheral Component Interconnect (PCI) bus standard or the Universal Serial Bus (USB) standard, for example. In some embodiments, the function of I/O interface430may be split into two or more separate components, such as a north bridge and a south bridge, for example. Also, in some embodiments some or all of the functionality of I/O interface430, such as an interface to system memory420, may be incorporated directly into processor410.

Input/output devices450may, in some embodiments, include one or more display terminals, keyboards, keypads, touchpads, scanning devices, voice or optical recognition devices, or any other devices suitable for entering or accessing data by one or more computer systems400. Multiple input/output devices450may be present in computer system400or may be distributed on various nodes of computer system400. In some embodiments, similar input/output devices may be separate from computer system400and may interact with one or more nodes of computer system400through a wired or wireless connection, such as over network interface440.

In some embodiments, the illustrated computer system may implement any of the operations and methods described above, such as the method illustrated by the flowchart ofFIG. 3. In other embodiments, different elements and data may be included.