Multi-modality communication with interceptive conversion

Disclosed herein are example embodiments for multi-modality communication with interceptive conversion. Described embodiments may include, but are not limited to, receiving from a first communication device data corresponding to a first communication modality, with the data corresponding to the first communication modality associated with a communication flow between the first communication device and a second communication device, and with the communication flow comprising a multi-modality communication in which a first user is to interact with the first communication device using a first communication modality and a second user is to interact with the second communication device using a second communication modality. Data corresponding to the first communication modality may be converted to data corresponding to the second communication modality and transmitted to the second communication device. A notification of at least one aspect of a conversion applicable to the communication flow may be transmitted to the first communication device.

The United States Patent Office (USPTO) has published a notice to the effect that the USPTO's computer programs require that patent applicants reference both a serial number and indicate whether an application is a continuation or continuation-in-part. Stephen G. Kunin,Benefit of Prior-Filed Application, USPTO Official Gazette Mar. 18, 2003, available at http://www.uspto.gov/web/offices/com/sol/og/2003/week11/patbene.htm. The present Applicant Entity (hereinafter “Applicant”) has provided above a specific reference to the application(s) from which priority is being claimed as recited by statute. Applicant understands that the statute is unambiguous in its specific reference language and does not require either a serial number or any characterization, such as “continuation” or “continuation-in-part,” for claiming priority to U.S. patent applications. Notwithstanding the foregoing, Applicant understands that the USPTO's computer programs have certain data entry requirements, and hence Applicant is designating the present application as a continuation-in-part of its parent applications as set forth above, but expressly points out that such designations are not to be construed in any way as any type of commentary and/or admission as to whether or not the present application contains any new matter in addition to the matter of its parent application(s).

DETAILED DESCRIPTION

FIG. 1is schematic diagram100of two communication devices that may be participating in an example communication in accordance with certain example embodiments. As shown inFIG. 1, by way of example but not limitation, schematic diagram100may include communication devices102, users104, communication modalities106, or at least one channel108. More specifically, schematic diagram100may include a remote communication device102R, a remote user104R, a remote communication modality106R, a local communication device102L, a local user104L, a local communication modality106L, or a channel108.

For certain example embodiments, a user104may be associated with a communication device102. A user104may be interacting with a communication device102via at least one communication modality106. Communication devices102may comprise, by way of example but not limitation, a mobile phone, a mobile terminal, a laptop or notebook computer, a personal digital assistant (PDA), a netbook, an entertainment appliance (e.g., a television, a gaming console, a set-top box, a music player, some combination thereof, etc.), a smart phone, a portable gaming device, a user equipment, a tablet or slate computer, a home phone, a desktop computer, a personal navigation device (PND), a vehicle with user-accessible communication capabilities, a private branch exchange (PBX)-based phone, videoconferencing equipment, any combination thereof, and so forth. A user104may comprise, by way of example only, a person. Example communication modalities106may include, by way of example but not limitation, a textual communication modality (e.g., wherein text may be communicated such as via a text message), a vocal communication modality (e.g., wherein sounds may be communicated such as via a voice call or teleconference), a visual communication modality (e.g., wherein moving images may be communicated such as via a video call or video conference), any combination thereof, and so forth.

For certain example embodiments, remote user104R may be associated with remote communication device102R. Remote user104R may be interacting with remote communication device102R via at least one remote communication modality106R. Local user104L may be associated with local communication device102L. Local user104L may be interacting with local communication device102L via at least one local communication modality106L. Remote communication device102R or remote user104R may be participating in at least one communication with local communication device102L or local user104L via one or more channels108. A channel108may comprise, by way of example but not limitation, one or more of: at least one wired link, at least one wireless link, at least part of public network, at least part of a private network, at least part of a packet-switched network, at least part of a circuit-switched network, at least part of an infrastructure network, at least part of an ad hoc network, at least part of a public-switched telephone network (PSTN), at least part of a cable network, at least part of a cellular network connection, at least part of an Internet connection, at least part of a Wi-Fi connection, at least part of a WiMax connection, multiple instances of any of the above, any combination of the above, and so forth. A channel108may include one or more nodes through which signals are propagated.

For certain example implementations, a communication may be initiated by remote communication device102R, remote user104R, local communication device102L, local user104L, any combination thereof, and so forth. For certain example implementations, remote communication modality106R and local communication modality106L may comprise a same one or more communication modalities106or may comprise at least one different communication modality106. Furthermore, for certain example implementations, remote communication modality106R or local communication modality106L may change from one communication modality to another communication modality during a single communication, across different communications, and so forth.

Moreover, it should be understood that the terms “remote” and “local” may, depending on context, be a matter of perspective. For instance, a communication device102or user104or communication modality106may be considered a local one at one moment, for one communication, for one perspective, etc. but may be considered a remote one at a different moment, for a different communication, for a different perspective, etc. However, one of ordinary skill in the art will recognize that the terms “remote” and “local” may serve, depending on context, to indicate that different interactions, acts, operations, functionality, a combination thereof, etc. may be occurring at, may be more closely associated with, a combination thereof etc. one side, aspect, location, combination thereof, etc. of a communication as compared to another side, aspect, location, combination thereof, etc. of the communication. For example, one signal may be transmitted from a remote communication device102R and received at a local communication device102L, or another signal may be transmitted from a local communication device102L and received at a remote communication device102R.

FIG. 2is schematic diagram200of two communication devices that may be participating in a communication involving two communication modalities in accordance with at least one example intimacy setting, in accordance with certain example embodiments. As shown inFIG. 2, by way of example but not limitation, schematic diagram200may include communication devices102, users104, communication modalities106, or at least one signal202. More specifically, schematic diagram200may include a remote communication device102R, a remote user104R, a first communication modality106-1, a local communication device102L, a local user104L, a second communication modality106-2, or one or more signals202. Furthermore, at least local communication device102L may include (e.g., store, establish, have access to, a combination thereof, etc.) at least one intimacy setting204.

For certain example embodiments, remote user104R may be associated with remote communication device102R. Remote user104R may be interacting with remote communication device102R via at least one first communication modality106-1. Local user104L may be associated with local communication device102L. Local user104L may be interacting with local communication device102L via at least one second communication modality106-2. First communication modality106-1may differ from second communication modality106-2. Remote communication device102R or remote user104R may be participating in at least one communication with local communication device102L or local user104L via one or more signals202. Signals202may propagate via one or more channels108(e.g., ofFIG. 1). Signals202, by way of example but not limitation, may comprise, electrical signals, magnetic signals, electromagnetic signals, photonic signals, wireless signals, wired signals, any combination thereof, and so forth.

For certain example embodiments, a local communication device102L may receive one or more signals202corresponding to a first communication modality106-1. A local communication device102L may respond to one or more signals202corresponding to first communication modality106-1based at least partly on local user104L interaction via a second communication modality106-2in accordance with at least one intimacy setting204. By way of example but not limitation, at least one intimacy setting204may indicate what kind of one or more communication modalities a user is willing to expose for at least one communication.

For certain example embodiments, at least one intimacy setting204may indicate how a user104is to interact with a communication device102with respect to a given communication without condition (e.g., a user may limit any current communications to text). Additionally or alternatively, at least one intimacy setting204may indicate how a user104is to interact with a communication device with respect to a given communication on a conditional basis. By way of example only, a user104may indicate a communication modality in at least partial dependence on whether an associated communication device102initiated a communication or terminated a communication. For instance, at least one intimacy setting204may indicate that communications are to be initiated using an interaction in accordance with a voice communication modality, but the at least one intimacy setting204may indicate that communications are to be terminated using a textual communication modality. Additionally or alternatively, a local user104L may indicate a local communication modality106L (e.g., ofFIG. 1) in at least partial dependence on a remote communication modality106R. For instance, at least one intimacy setting204may indicate that if a remote communication modality106R corresponds to text, a local communication modality106L is also to correspond to text; furthermore, the at least one intimacy setting204may indicate that if a remote communication modality106R corresponds to voice, a local communication modality106L is to correspond to text; moreover, the at least one intimacy setting204may indicate that if a remote communication modality106R corresponds to video, a local communication modality106L is to correspond to voice. Additionally or alternatively, a local user104L may indicate a local communication modality106L (e.g., ofFIG. 1) that is based at least partially on an identity of a remote user104R; a time of day, day of week, a combination thereof, etc.; an environmental condition (e.g., an ambient lighting level, a level or type of movement—e.g. vehicle motion may be detected, a combination thereof, etc.); any combination thereof; and so forth. However, claimed subject matter is not limited to any particular examples.

FIG. 3Ais schematic diagram300A of an example communication device that may be participating in a communication using a signal receiver or a response handler in accordance with certain example embodiments. As shown inFIG. 3A, by way of example but not limitation, schematic diagram300A may include a local communication device102L, a local user104L, a second communication modality106-2, or one or more signals202. More specifically, a local communication device102L of schematic diagram300may include at least one intimacy setting204, a signal receiver302, or a response handler304.

For certain example embodiments, a signal receiver302may receive one or more signals202corresponding to a first communication modality106-1. By way of example but not limitation, one or more signals202may correspond to first communication modality106-1if one or more signals202originated at remote communication device102R (e.g., ofFIG. 2) in at least partial dependence on interaction by remote user104R with remote communication device102R via first communication modality106-1, if one or more signals202are derived at least partly from interaction by remote user104R with remote communication device102R via first communication modality106-1, if one or more signals202are encoded to support user input via first communication modality106-1, if one or more signals202are encoded to support user output in accordance with first communication modality106-1, any combination thereof, and so forth. A response handler304may respond to one or more signals202corresponding to first communication modality106-1based at least partly on local user104L interaction via a second communication modality106-2in accordance with at least one intimacy setting204. Example implementations with respect to a response handler304are described herein below with particular reference to at leastFIGS. 4A-4C. Additional and/or alternative implementations are described herein below with respect to at leastFIGS. 6A-6K.

For certain example embodiments, signal receiver302and response handler304may comprise a single component together, a single component apiece, multiple components, or any combination thereof, and so forth. Example components for a communication device102are described herein below with particular reference to at leastFIG. 5. By way of example but not limitation, signal receiver302may comprise an antenna, a wired connector, a signal downconverter, a baseband processor, a signal processing module (e.g., to account for signal manipulation for a communication protocol, to decrypt, to extract data, a combination thereof, etc.), a processor, hardware, software, firmware, logic, circuitry, any combination thereof, and so forth. By way of example but not limitation, response handler304may comprise an intimacy-related module, hardware, software, firmware, logic, circuitry, any combination thereof, and so forth.

FIG. 3Bis a schematic diagram300B of an example communication device that may realize a user interface feature in accordance with certain example embodiments. As shown inFIG. 3B, by way of example but not limitation, schematic diagram300B may include a local communication device102L, a local user104L, or at least one intimacy setting204. More specifically, schematic diagram300B may include at least one user interface (UI) feature controller306, at least one user interface feature manipulation detector308, at least one user interface feature310, at least one user interface feature provider312, one or more communication modality options314, or at least one user selection320.

For certain example embodiments, a user interface feature310may be realized by a local communication device102L. Example implementations for a user interface feature310are described herein with particular reference toFIGS. 3C-3FandFIGS. 8A-8I, but by way of example but not limitation. A user interface feature310may enable a user104to operate a communication device102with regard to multi-modality communications. A user interface feature310may, for example, provide visual, aural, haptic, etc. output and accept visual, touch, or sound input to enable a user104to establish settings (e.g., at least one intimacy setting204), activate a multi-modality communication, any combination thereof, and so forth. For certain example implementations, a user interface feature310may include or present one or more communication modality options314. Communication modality options314are described, by way of example but not limitation, with particular reference toFIGS. 3D-3F. In an example operation, user selection320of a communication modality option314may enable a user104to establish settings, activate a multi-modality communication, any combination thereof, and so forth

For certain example embodiments, a user interface feature provider312may provide a user interface feature310. A user interface feature manipulation detector308may detect if or when a user interface feature310is being manipulated by a user104. A user interface feature controller306may control an implementation or realization of a user interface feature. For certain example implementations, a user interface feature controller306may control interactions between user interface feature manipulation detector308or user interface feature provider312or may control interactions among user interface feature provider312, user interface feature manipulation detector308, and other components of a communication device102. For instance, a user interface feature controller306may provide access to one or more signals202(e.g., ofFIGS. 2 and 3A) for user interface feature provider312, to calling functionality of a communication device102, to display functionality of a communication device102, to an operating system resident on a communication device102(e.g., if a user interface feature or multi-modality communication is at least partially implemented by an application that is separate from an operating system), to user interface components516, any combination thereof, and so forth. However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.

FIG. 3Cis a schematic diagram300C of an example communication device that may include a physical component or a virtual component of a user interface feature in accordance with certain example embodiments. As shown inFIG. 3C, by way of example but not limitation, schematic diagram300C may include a communication device102or a user interface feature310. More specifically, schematic diagram300C may include at least one physical component316of a user interface feature310or at least one virtual component318of a user interface feature310.

For certain example embodiments, a user interface feature310may comprise one or more physical components316, one or more virtual components318, any combination thereof, and so forth. By way of example but not limitation, a physical component316of a user interface feature310may comprise a component that is at least partially implemented in hardware as part of a communication device102. Examples of physical components316may include, but are not limited to, at least one knob, at least one dial, at least one slider, at least one switch, one or more keys (e.g., that are part of a numeric, alphabetical, alphanumeric, etc. keypad or keyboard), one or more buttons, at least one trackball, at least one track wheel, at least one joystick, a track stick, or at least one touch-sensitive surface (e.g., a touch-sensitive screen, a track pad, etc.). Physical components316(e.g., a knob, a switch, a slider, a dial, a key, a button, a trackball, a track wheel, etc.) may be physically moveable by a user. A physical component316may be integrated with a communication device102. A physical component316may be a hardware input/output component that is dedicated (e.g., temporarily or permanently) to a user interface feature310. Examples of physical components316that are illustrated in schematic diagram300C may include, by way of example but not limitation, a touch-sensitive screen316a, a switch316b, a trackball or track wheel316c, a button or key316d, a combination thereof, and so forth. As shown, by way of example but not limitation, a switch316bmay be switched between a first communication modality106-1and a second communication modality106-2(e.g., ofFIG. 2).

For certain example embodiments, a user interface feature310may comprise one or more virtual components318. By way of example but not limitation, a virtual component318of a user interface feature310may comprise a component that is at least partially implemented in software or firmware as part of a communication device102. Examples of virtual components318may include, but are not limited to, a visual presentation, an aural presentation, a haptic presentation, any combination thereof, and so forth. For certain example implementations, a virtual component318may be displayed on a screen, played on a speaker, projected on a screen, vibrated by a device, any combination thereof, and so forth. A virtual component318may be reconfigurable during operation. A virtual component318may be displayed at one moment, modified at another moment, removed from a display at another moment, a combination thereof, and so forth. An example of a virtual component318that is illustrated in schematic diagram300C may include, by way of example but not limitation, a display318a. Physical components316or virtual components318may not be mutually exclusive. For example, a screen316amay serve to present a virtual component318on a physical component316. Additionally or alternatively, a physical component316(e.g., a trackball316cor a button/key316d) may be used to select an aspect of a virtual component318(e.g., that is part of a display318a). However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.

FIGS. 3D-3Fare schematic diagrams300D-300F of example user interface features in accordance with certain example embodiments. As shown inFIGS. 3D-3F, by way of example but not limitation, schematic diagrams300D-300F may include one or more example user interface features310a-310f. More specifically, schematic diagram300D illustrates example user interface features310aor310bthat may be implemented at least partially as physical components316. Schematic diagram300E illustrates example user interface features310cor310dthat may be implemented at least partially as virtual components318. Schematic diagram300F illustrates example user interface features310eor310fthat may be implemented at least partially as virtual components318. Schematic diagrams300D-300F also illustrate examples of communication modality options314. However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.

For certain example embodiments, as shown in schematic diagram300D ofFIG. 3D, a user interface feature310ais illustrated. User interface feature310amay comprise a dial or knob316ethat enables a user to adjust an intimacy setting204(e.g., ofFIGS. 2, 3A, and 3B). For an example implementation, intimacy knob316emay be rotated to any of five different communication modalities A, B, C, D, or E. Each respective communication modality A, B, C, D, or E may be represented by a respective communication modality option314a. (For the sake of visual clarity, each communication modality option314may not be separately identified by reference number in each schematic diagram. For instance, one of five communication modality options314ais explicitly identified for user interface feature310a.) Each communication modality may correspond, by way of example but not limitation, to a type of user interaction with a communication device, to a type of user interaction with a communication device for user input interaction or user output interaction, any combination thereof, and so forth.

For certain example embodiments, as shown in schematic diagram300D ofFIG. 3D, a user interface feature310bis illustrated. User interface feature310bmay comprise a slider316fthat enables a user to adjust an intimacy setting. For an example implementation, slider316fmay be slid to any of three different communication modalities that correspond to different degrees of communicative exposure: a first degree, a second degree, or a third degree. Each communicative exposure degree may be represented by a respective communication modality option314b. Each communication modality may correspond, by way of example but not limitation, to textual communication, speech communication, video communication at a first resolution, video communication at a second higher resolution, video communication with stereoscopic (e.g., 3D) images, facial video communication, full-body video communication, any combination thereof, and so forth. Although shown and described in terms of a physical component316, a dial316eor a slider316fmay additionally or alternatively be implemented as a virtual component318(e.g., that is displayed on a screen).

For certain example embodiments, as shown in schematic diagram300E ofFIG. 3E, a user interface feature310cis illustrated. User interface feature310cmay comprise a display318bthat is separated into user input interaction (e.g., at an upper row) and into user output interaction (e.g., at a lower row). For an example implementation, one or more communication modalities that are presented (e.g., in a menu or arrived via a menu) may be selected for user input interaction or user output interaction via one or more buttons (e.g., “radio-style” buttons, but multiple ones of such buttons may be selected as shown in the lower row). Display318bmay be presented to a user so that a user may adjust input or output communication modalities, which may be represented by one or more communication modality options314c. By way of example but not limitation, a user may select video, voice, or text. As shown for example user interface feature310c, a user has selected to provide input to a communication device as text but to accept output from a communication device as video, voice, or text. A user may make such selections if, for instance, a user is at home and may see, hear, read, etc. incoming communicative signals but wishes to limit outgoing communicative signals because the user has not yet made themselves professionally presentable.

For certain example embodiments, as shown in schematic diagram300E ofFIG. 3E, a user interface feature310dis illustrated. User interface feature310dmay comprise a display318cthat is presented in response to receiving an incoming communication that corresponds to, e.g., a first communication modality. A communication device may ask a user if the user wishes to attempt to continue the communication using one or more communication modality options314d. For an example implementation, one or more communication modality options314dmay be presented to a user via a scrolling menu as shown. A user may scroll through communication modality options314duntil a desired communication modality option is identified and selected. As shown, a second communication modality option may be highlighted for selection by a user via a touch, a movement of a physical component, some combination thereof, and so forth.

For certain example embodiments, as shown in schematic diagram300F ofFIG. 3F, a user interface feature310eis illustrated. User interface feature310emay comprise a display318dhaving a pop-up menu that is presented to a user if, by way of example but not limitation, an incoming voice call from a particular person (e.g., “John”) is received. A communication device may inquire as to how a user wishes to answer John's incoming voice call. Multiple communication modality options314eare shown as virtual buttons that may be selected. By way of example but not limitation, available communication modality options may comprise “Voice”, “Text”, “Video (with Audio)”, “Video (with Text)”, “Other”, and so forth. If a local user selects “Video (with Text)”, for instance, a local communication device may answer the voice call and offer to continue the communication with a remote user under a condition that the local user may interact with the local communication device in accordance with video and text (e.g., which might be desired if a local user is currently located in a noisy environment).

For certain example embodiments, as shown in schematic diagram300F ofFIG. 3F, a user interface feature310fis illustrated. User interface feature310fmay comprise a display318ehaving another pop-up menu, which may be presented if a user selects an “Other” button of user interface feature310e. Multiple communication modality options314fare shown as virtual buttons that may be selected. By way of example but not limitation, available communication modality options may comprise “Incoming Voice—Outgoing Text”, “Incoming Text—Outgoing Voice”, and “Incoming Voice—Outgoing Video & Text”, and so forth. If a user selects an “Incoming Voice—Outgoing Text” button, for instance, a user may interact with a local device in accordance with voice communications for device output interaction and may interact with the local device in accordance with textual communications for device input interaction.

Multiple different embodiments may additionally or alternatively be implemented. For example, degrees of communicative exposure (e.g., of communication modality options314b) may be presented as radio-style buttons (e.g., like communication modality options314c). As another example, display(s) at least similar or analogous to display318c,318d, or318emay be presented to establish at least one intimacy setting204prior to arrival of an incoming communication notification. As yet another example, communication modality options314e(e.g., of user interface feature310e) or communication modality options314c(e.g., of user interface feature310c) may be presented as a slider interface (e.g., as shown in schematic diagram300D as part of user interface feature310b). As another example, a user interface feature310may be accessible via a widget of a communication device102. However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.

FIG. 4Ais schematic diagram400A of a communication device that may be participating in a communication using an example response handler having a conversion effectuator in accordance with certain example embodiments. As shown inFIG. 4A, by way of example but not limitation, schematic diagram400A may include a local communication device102L, a local user104L, a second communication modality106-2, or one or more signals202. More specifically, a local communication device102L of schematic diagram400A may include at least one intimacy setting204, a signal receiver302, or a response handler304, which may include a conversion effectuator402.

For certain example embodiments, a conversion effectuator402may cause a conversion of a correspondence with one communication modality to a correspondence with another communication modality. By way of example but not limitation, a conversion effectuator402may cause a conversion (e.g., of signals, such as one or more signals202) from a correspondence with a first communication modality106-1to a correspondence with a second communication modality106-2, may cause a conversion (e.g., of signals derived from user input of local user104L) from a correspondence with a second communication modality106-2to a correspondence with a first communication modality106-1, some combination thereof, and so forth. Example implementations with respect to a conversion effectuator402are described herein below with particular reference to at leastFIGS. 4B and 4C. Additional or alternative implementations are described herein below with respect to at leastFIGS. 6A-6K.

FIG. 4Bis schematic diagram400B of a communication device that may be participating in a communication using an example conversion effectuator having a converter in accordance with certain example embodiments. As shown inFIG. 4B, by way of example but not limitation, schematic diagram400B may include a local communication device102L that includes at least one intimacy setting204, a signal receiver302, or a response handler304. More specifically, a local communication device102L of schematic diagram400B may include a response handler304having a conversion effectuator402, which may include a converter404.

For certain example embodiments, a converter404may perform a conversion of a correspondence with one communication modality to a correspondence with another communication modality. By way of example but not limitation, a converter404may perform a conversion (e.g., of signals) from a correspondence with a first communication modality106-1to a correspondence with a second communication modality106-2, may perform a conversion (e.g., of signals) from a correspondence with a second communication modality106-2to a correspondence with a first communication modality106-1, some combination thereof, and so forth. Additional or alternative implementations are described herein.

FIG. 4Cis schematic diagram400C of a communication device that may be participating in a communication using an example conversion effectuator having a conversion requester in accordance with certain example embodiments. As shown inFIG. 4C, by way of example but not limitation, schematic diagram400C may include a local communication device102L that includes at least one intimacy setting204, a signal receiver302, or a response handler304. More specifically, a local communication device102L of schematic diagram400C may include a response handler304having a conversion effectuator402, which may include a conversion requester406. Furthermore, by way of example but not limitation, schematic diagram400C may include a conversion node408, which may include a converter410.

For certain example embodiments, a conversion effectuator402may cause a conversion of a correspondence with one communication modality to a correspondence with another communication modality based, at least partly, on one or more interactions with a conversion node408using a conversion requester406. For certain example implementations, a conversion node may be external to local communication device102L. A conversion node408may comprise, by way of example but not limitation, a telecommunications node (e.g., a telecom switch or router, a base station, a base station controller, a mobile switching center, a public switched telephone network node, a gateway to a telecommunications network, some combination thereof, etc.), an Internet node (e.g., a switch, a router, a server, a server blade, a virtual server machine, a combination thereof, etc.), a local area network (LAN) node, a computer, some combination thereof, and so forth.

For certain example embodiments, conversion requester406may transmit one or more signals (e.g., one or more signals202or a derivative thereof) corresponding to a first communication modality106-1to conversion node408. Using converter410, conversion node408may perform a conversion (e.g., of signals) from a correspondence with a first communication modality106-1to a correspondence with a second communication modality106-2. Conversion node408may transmit one or more signals corresponding to a second communication modality106-2to conversion effectuator402(e.g., to conversion requester406) of local communication device102L. Additionally or alternatively, conversion requester406may transmit one or more signals corresponding to a second communication modality106-2to conversion node408. Using converter410, conversion node408may perform a conversion (e.g., of signals) from a correspondence with a second communication modality106-2to a correspondence with a first communication modality106-1. Conversion node408may transmit one or more signals corresponding to a first communication modality106-1to conversion effectuator402(e.g., to conversion requester406) of local communication device102L. However, claimed subject matter is not limited to examples as described herein.

FIGS. 4D, 4E, 4F, and 4Gdepict different example sequence diagrams400D,400E,400F, and400G, respectively, for example multi-modality communications. As shown, by way of example but not limitation, each sequence diagram may include a remote communication device102R or a local communication device102L, as well as multiple actions. Although actions of sequence diagrams400D,400E,400F, and400G are shown or described in a particular sequence, it should be understood that methods or processes may be performed in alternative manners without departing from claimed subject matter, including, but not limited to, with a different sequence or number of actions, with a different relationship between or among actions, with a different communication device (or node) performing action(s). Also, at least some actions of sequence diagrams400D,400E,400F, and400G may be performed so as to be fully or partially overlapping with other action(s) in a temporal sense, in a communication sense (e.g., over one or more channels), in a processing sense (e.g., using multiple cores, multitasking, a combination thereof, etc.), some combination thereof, and so forth. By way of example only, a given communication may comprise a fully or partially duplex communication, thereby enabling independent or overlapping transmissions or receptions.

As depicted, by way of example but not limitation, each example multi-modality communication includes a communication that may be initiated by a remote communication device102R. However, multi-modality communications may alternatively or additionally include communications that may be initiated by a local communication device102L. As illustrated, by way of example but not limitation, each example multi-modality communication may involve two communication modalities including voice interaction and text interaction. However, multi-modality communications may alternatively or additionally involve two or more communication modalities that include voice interaction, text interaction, video interaction, any combination thereof, and so forth. As shown, by way of example but not limitation, a local communication device102L, in conjunction with an indication from a local user104L, may determine that a communication is to be a multi-modality communication at or around when a communication is initiated. However, a remote communication device102R may additionally or alternatively determine that a communication is to be a multi-modality communication. Furthermore, a communication may be migrated to a multi-modality communication at virtually any time during a communication. Moreover, a communication device may additionally or alternatively initiate a communication as a multi-modality communication.

For certain example embodiments, sequence diagrams400D,400E,400F, and400G may include one or more transmissions or receptions. Transmissions or receptions may be made, by way of example but not limitation, from or to a remote communication device102R or from or to a local communication device102L. A given transmission or reception may be made via any one or more channels108(e.g., ofFIG. 1). Examples of channels may include, but are not limited to, a voice connection channel, a voice data channel, a voice over internet protocol (VOIP) channel, a packet data channel, a signaling channel, a channel over the Internet, a cellular-text-messaging channel, any combination thereof, and so forth. Additionally or alternatively, although two communication devices are shown as participating in a given communication, more than two communication devices or more than two users may participate in a given communication.

FIG. 4Dis a sequence diagram400D of an example multi-modality communication in which conversion occurs at a local communication device. As shown inFIG. 4D, by way of example but not limitation, one or more of actions412a-412kmay be performed for a communication. For an example sequence diagram400D, a local communication device102L may cause two conversions to be performed.

For certain example embodiments, at action412a, a remote communication device102R may transmit or a local communication device102L may receive a notification of an incoming communication that corresponds to voice. By way of example but not limitation, a notification may comprise a text message, a ringing signal, a communication inquiry, a communication notice, any combination thereof, and so forth. At action412b, local communication device102L may determine that the communication may continue in a manner that is at least partially corresponding to text. For certain example implementations, local communication device102L may make a determination based, at least partly, on an existing intimacy setting (e.g., on a current default intimacy setting), on a contemporaneous intimacy setting indication provided by local user104L (e.g., by a local user without prompting, by a local user in response to options presented by a local communication device in conjunction with presentation of a call notification to the local user, some combination thereof, etc.), any combination thereof, and so forth.

For certain example embodiments, at action412c, a local communication device102L may transmit or a remote communication device102R may receive a message indicating that a communication is accepted if it may correspond at least partially to text. At action412d, a remote communication device102R may provide a remote user104R with an opportunity to switch to text (e.g., to establish a single-modality textual communication), with an opportunity to continue a communication with remote user interactivity including voice (e.g., to establish a dual-modality voice and textual communication), with an opportunity to propose a different one or more interactivity-types of communication(s), any combination thereof, and so forth. For certain examples as described herein, with respect to action412d, it is given that a remote user104R elects to continue a communication as a multi-modality communication with voice interaction for remote user104R and (at least partial) textual interaction for local user104L.

For certain example embodiments, at action412e, a remote communication device102R may accept user voice input. For an example implementation, a remote communication device102R may enable voice interaction with a remote user104R by accepting voice input via at least one user input interface516a(e.g., ofFIG. 5), such as at least one microphone. At action412f, a remote communication device102R may transmit or a local communication device102L may receive voice data.

For certain example embodiments, at action412g, a local communication device102L may cause a conversion of voice data (e.g., as received from a remote communication device102R) to text data. For an example implementation, a local communication device102L may cause a conversion from voice data to text data using a converter404(e.g., ofFIG. 4B), using a conversion requester406(e.g., ofFIG. 4C) (e.g., that communicates with a conversion node408having a converter410), any combination thereof, and so forth. At action412h, a local communication device102L may present text output (e.g., as converted as a result of action412g) to a local user104L. For an example implementation, a local communication device102L may display text to a local user104L via at least one user output interface516b(e.g., ofFIG. 5), such as at least one display screen. At action412i, a local communication device102L may accept user text input. For an example implementation, a local communication device102L may accept text input from a local user104L via at least one user input interface516a, such as a physical or virtual keyboard. A user input interface516afor accepting text input may alternatively or additionally comprise a text message application, a text message module of an operating system, a general text entry application, a general text entry module of an operation system, a specialized text entry application, a specialized text entry module of operating system, any combination thereof, and so forth. A specialized text entry application or operating system module may, by way of example but not limitation, be linked to a voice capability (e.g., a calling feature) or video capability or be designed at least partially to implement multi-modality communications in accordance with certain embodiments that are described herein.

For certain example embodiments, at action412j, a local communication device102L may cause text data of accepted text to be converted to voice data. For an example implementation, a local communication device102L may cause a conversion from text to voice using a converter404(e.g., ofFIG. 4B), using a conversion requester406(e.g., ofFIG. 4C), any combination thereof, and so forth. At action412k, a local communication device102L may transmit or a remote communication device102R may receive converted voice data. A remote communication device102R may present the converted voice data (e.g., play the voice data over one or more speakers) in accordance with a voice communication modality of interaction by remote user104R at remote communication device102R.

FIG. 4Eis a sequence diagram400E of an example multi-modality communication in which conversion occurs at a remote communication device. As shown inFIG. 4E, by way of example but not limitation, one or more of actions412a-412eor414a-414gmay be performed for a communication. For an example sequence diagram400E, a remote communication device102R may cause two conversions to be performed. Actions412a-412eof sequence diagram400E may be at least similar or analogous to actions412a-412e, respectively, of sequence diagram400D.

For certain example embodiments, at action412e, a remote communication device102R may accept user voice input. For an example implementation, a remote communication device102R may enable voice interaction with a remote user104R by accepting voice input via at least one user input interface516a(e.g., ofFIG. 5), such as at least one microphone. At action414a, a remote communication device102R may cause a conversion of voice data (e.g., as accepted from a remote user104R) to text data. For an example implementation, a remote communication device102R may cause a conversion using a converter404(e.g., ofFIG. 4B), using a conversion requester406(e.g., ofFIG. 4C), any combination thereof, and so forth.

For certain example embodiments, at action414b, a remote communication device102R may transmit or a local communication device102L may receive converted text data. At action414c, a local communication device102L may present text output to a local user104L. For an example implementation, a local communication device102L may display converted text to a local user104L via at least one user output interface516b(e.g., ofFIG. 5), such as at least one display screen, wherein the converted text was caused to be converted from voice data by a remote communication device102R. A user output interface516bfor presenting text output may alternatively or additionally comprise a text message application, a text message module of an operating system, a general text output application, a general text output module of an operation system, a specialized text output application, a specialized text output module of operating system, any combination thereof, and so forth. A specialized text output application or operating system module may, by way of example but not limitation, be linked to a voice capability (e.g., a calling feature) or video capability or be designed at least partially to implement multi-modality communications in accordance with certain embodiments that are described herein. A user input interface516afor accepting text input may be separate from or fully or partially combined with a user output interface516bfor presenting text output. At action414d, a local communication device102L may accept user text input. At action414e, a local communication device102L may transmit or a remote communication device102R may receive text data.

For certain example embodiments, at action414f, a remote communication device102R may cause received text data to be converted to voice data. For an example implementation, a remote communication device102R may cause a conversion from text to voice using a converter404(e.g., ofFIG. 4B), using a conversion requester406(e.g., ofFIG. 4C), any combination thereof, and so forth. At action414g, a remote communication device102R may present voice data (e.g., as converted from received text data as a result of action414f) to a remote user104R. For an example implementation, a remote communication device102R may present voice data as converted from text data to a remote user104R via at least one user output interface516b(e.g., ofFIG. 5), such as at least one speaker.

For certain example implementations, e.g.—as described with reference to sequence diagram400E, text data is transmitted between remote communication device102R and local communication device102L. Text data may consume less bandwidth than voice data (or less than video data). Generally, transmission of data corresponding to one type of communication modality may consume less bandwidth than transmission of data corresponding to another type of communication modality. Accordingly, a determination or selection of a location or a communication device at which to perform a conversion of data corresponding to one communication modality to data corresponding to another communication modality may be based, at least in part, on a bandwidth consumed by data of each communication modality. By way of example but not limitation, a location or communication device for conversion may be determined or selected such that relatively lower bandwidth data is transmitted.

FIG. 4Fis a sequence diagram400F of an example multi-modality communication in which conversion occurs at a local communication device and at a remote communication device. As shown inFIG. 4F, by way of example but not limitation, one or more of actions412a-412e,414a-414d, or416a-416fmay be performed for a communication. For an example sequence diagram400F, a remote communication device102R may cause a conversion to be performed, and a local communication device102L may cause a conversion to be performed. Action412e(plus actions412a-412d, which are not shown inFIG. 4Ffor the sake of clarity) of sequence diagram400E and actions414a-414dmay be at least similar or analogous to actions412e(plus412a-412d) of sequence diagram400D and actions414a-414dof sequence diagram400E, respectively.

For certain example embodiments, at action414a, a remote communication device102R may cause a conversion of voice data (e.g., as accepted from a remote user104R at action412e) to text data. At action414b, a remote communication device102R may transmit or a local communication device102L may receive converted text data. At action414c, a local communication device102L may present text data as text output to a local user104L, which text data may comprise converted text data that was caused to be converted from voice data by another communication device, such as a remote communication device102R. At action414d, a local communication device102L may accept user text input. At action416a, a local communication device102L may cause text data of accepted text to be converted to voice data. At action416b, a local communication device102L may transmit or a remote communication device102R may receive converted voice data.

For certain example embodiments, at action416c, a remote communication device102R may present voice data as voice output to a remote user104R, which voice data may comprise converted voice data that was caused to be converted by another communication device, such as local communication device102L. At action416d, a remote communication device102R may accept user voice input. At action416e, a remote communication device102R may cause a conversion of voice data (e.g., as accepted from a remote user104R) to text data. At action416f, a remote communication device102R may transmit or a local communication device102L may receive converted text data.

FIG. 4Gis a sequence diagram400G of an example multi-modality communication in which conversion occurs at a local communication device and in which a multi-modality input/output interaction occurs at the local communication device. As shown inFIG. 4G, by way of example but not limitation, one or more of actions412aor418a-418kmay be performed for a communication. For an example sequence diagram400G, a local communication device102L may cause a conversion to be performed. Action412aof sequence diagram400G may be at least similar or analogous to action412aof sequence diagram400D.

For certain example embodiments, at action412a, a remote communication device102R may transmit or a local communication device102L may receive a notification of an incoming communication that corresponds to voice. At action418a, local communication device102L may determine that the communication may continue as at least partially corresponding to text. For certain example implementations, local communication device102L may make a determination based, at least partly, on an existing intimacy setting (e.g., a current default intimacy setting), on a contemporaneous intimacy setting indication provided by local user104L (e.g., by a local user without prompting, by a local user in response to options presented by a local communication device in conjunction with presentation of a call notification to the local user, some combination thereof, etc.), any combination thereof, and so forth.

For certain example embodiments, at least one user may engage in a multi-modality communication in which a user interacts with a communication device using two (or more) different communication modalities. For certain example implementations, a user may select to interact with a communication device via voice for input and via text for output. For instance, a user may speak to provide user voice input, but a user may read to acquire user text output for a single communication. As shown for an example of sequence diagram400G, a user has instead selected for user output interaction to comprise voice and for user input interaction to comprise text. This may occur, for instance, if a user having a wireless or wired headset is located in an environment in which quiet is expected, such as a library or “quiet car” of a train. For a given communication, a user may be presented voice data output (e.g., may hear voice sounds) from another participant of the given communication, but may provide text input that is ultimately sent to the other participant (e.g., before or after conversion, if any, from text data to voice data).

For certain example embodiments, at action418b, a local communication device102L may transmit or a remote communication device102R may receive a message indicating that a communication is accepted if it may correspond at least partially to text. For an example implementation, a message may indicate that a local user104L intends to continue a communication by interacting with local communication device102L via voice for user output and via text for user input. At action418c, a remote communication device102R may provide a remote user104R with an opportunity to switch to full or partial text (e.g., to request to establish a single-modality textual communication, to establish that remote user104R is willing to receive text output thereby obviating a conversion), with an opportunity to continue a communication with remote user interactivity including voice (e.g., to accept a multi-modality communication in which remote user104R provides user input interaction via voice and accepts user output interaction via converted voice data), with an opportunity to propose a different one or more interactivity-types of communication(s), any combination thereof, and so forth. For certain examples described herein with respect to action418c, it is given that a remote user104R elects to continue a communication as a multi-modality communication with (i) voice input and voice output interaction for remote user104R and (ii) textual input and voice output interaction for local user104L.

For certain example embodiments, at action418d, a remote communication device102R may accept user voice input. At action418e, a remote communication device102R may transmit or a local communication device102L may receive voice data. At action418f, a local communication device102L may present voice data to a local user104L. For an example implementation, a local communication device102L may present voice data (e.g., without conversion) to a local user104L via at least one user output interface516b(e.g., ofFIG. 5), such as at least one speaker, including but not limited to a speaker of a headset. At action418g, a local communication device102L may accept user text input. For an example implementation, a local communication device102L may accept text input from a local user104L via at least one user input interface516a, such as a physical or virtual keyboard. At action418h, a local communication device102L may cause text data of accepted text to be converted to voice data.

For certain example embodiments, at action418i, a local communication device102L may transmit or a remote communication device102R may receive converted voice data. At action418j, a remote communication device102R may present voice data to a remote user104R, which voice data may comprise converted voice data that was caused to be converted by another communication device, such as local communication device102L. Additionally or alternatively, local communication device102L may transmit (unconverted) text data to remote communication device102R, and remote communication device102R may cause text data to be converted to voice data prior to its presentation to remote user104R. At action418k, a remote communication device102R may accept user voice input. At action418i, a remote communication device102R may transmit or a local communication device102L may receive voice data.

For certain example embodiments, a communication may be initiated (e.g., by a remote communication device102R or a local communication device102L or another communication device) that is to be a multi-modality communication from a perspective of an initiating user or device alone. By way of example but not limitation, a remote user104R of a remote communication device102R may initiate a communication in which interaction by remote user104R is to comprise text output interaction and voice input interaction (e.g., if a remote user104R is located in a noisy environment and possesses noise canceling microphone(s) but no noise canceling speaker). By way of example but not limitation, a remote user104R of a remote communication device102R may instead initiate a communication in which interaction by remote user104R is to comprise voice output interaction and text input interaction (e.g., remote user104R is to receive voice output from a remote communication device102R via at least one speaker but is to provide text input for a remote communication device102R via at least one keyboard). For certain example implementations, a remote user104R may initiate a voice communication and then subsequently send a message to migrate the voice communication to a multi-modality communication in which text is used for at least one of user input interaction or user output interaction for at least interaction by remote user104R with remote communication device102R. However, claimed subject matter is not limited to any particular example embodiments, implementations, etc. that are described herein or illustrated in the accompanying drawings (e.g., including but not limited toFIGS. 4D-4G).

FIG. 5is a schematic diagram500of an example communication device including one or more example components in accordance with certain example embodiments. As shown inFIG. 5, a communication device102may include one or more components such as: at least one processor502, one or more media504, logic506, circuitry508, at least one communication interface510, at least one interconnect512, at least one power source514, or at least one user interface516, any combination thereof, and so forth. Furthermore, as shown in schematic diagram500, one or more media may comprise one or more instructions518, one or more settings520, some combination thereof, and so forth; communication interface510may comprise at least one wireless communication interface510a, at least one wired communication interface510b, some combination thereof, and so forth; or user interface516may comprise at least one user input interface516a, at least one user output interface516b, some combination thereof, and so forth. However, a communication device102may alternatively include more, fewer, or different components from those that are illustrated without deviating from claimed subject matter.

For certain example embodiments, a communication device102may include or comprise at least one electronic device. Communication device102may comprise, for example, a computing platform or any electronic device having at least one processor or memory. Processor502may comprise, by way of example but not limitation, any one or more of a general-purpose processor, a specific-purpose processor, a digital signal processor (DSP), a processing unit, a combination thereof, and so forth. A processing unit may be implemented, for example, with one or more application specific integrated circuits (ASICs), DSPs, digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), processors generally, processing cores, discrete/fixed logic circuitry, controllers, micro-controllers, microprocessors, a combination thereof, and so forth. Media504may bear, store, contain, provide access to, a combination thereof, etc. instructions518, which may be executable by processor502. Instructions518may comprise, by way of example but not limitation, a program, a module, an application or app (e.g., that is native, that runs in a browser, that runs within a virtual machine, a combination thereof, etc.), an operating system, etc. or portion thereof; operational data structures; processor-executable instructions; code; or any combination thereof; and so forth. Media504may comprise, by way of example but not limitation, processor-accessible or non-transitory media that is capable of bearing instructions, settings, a combination thereof, and so forth.

For certain example embodiments, execution of instructions518by one or more processors502may transform communication device102into a special-purpose computing device, apparatus, platform, or any combination thereof, etc. Instructions518may correspond to, for example, instructions that are capable of realizing at least a portion of one or more flow diagrams methods, processes, operations, functionality, technology, or mechanisms, etc. that are described herein or illustrated in the accompanying drawings. Settings520may comprise, by way of example but not limitation, one or more indicators that may be established by a user or other entity, one or more indicators that may determine at least partly how a communication device102is to operate or respond to situations, one or more indicators or other values that may be used to realize flow diagrams, methods, processes, operations, functionality, technology, or mechanisms, etc. that are described herein or illustrated in the accompanying drawings.

For certain example embodiments, logic506may comprise hardware, software, firmware, discrete/fixed logic circuitry, any combination thereof, etc. that is capable of performing or facilitating performance of methods, processes, operations, functionality, technology, or mechanisms, etc. that are described herein or illustrated in the accompanying drawings. Circuitry508may comprise hardware, software, firmware, discrete/fixed logic circuitry, any combination thereof, etc. that is capable of performing or facilitating performance of methods, processes, operations, functionality, technology, or mechanisms, etc. that are described herein or illustrated in the accompanying drawings, wherein circuitry508comprises at least one physical or hardware component or aspect.

For certain example embodiments, one or more communication interfaces510may provide one or more interfaces between communication device102and another device or a person/operator. With respect to a person/operator, a communication interface510may include, by way of example but not limitation, a screen, a speaker, a keyboard or keys, or other person-device input/output features. A communication interface510may also or alternatively include, by way of example but not limitation, a transceiver (e.g., transmitter or receiver), a radio, an antenna, a wired interface connector or other similar apparatus (e.g., a universal serial bus (USB) connector, a proprietary connector, a Thunderbolt® or Light Peak® connector, a combination thereof, etc.), a physical or logical network adapter or port, or any combination thereof, etc. to communicate wireless signals or wired signals via one or more wireless communication links or wired communication links, respectively. Communications with at least one communication interface510may enable transmitting, receiving, or initiating of transmissions, just to name a few examples.

For certain example embodiments, at least one interconnect512may enable signal communication between or among components of communication device102. Interconnect512may comprise, by way of example but not limitation, one or more buses, channels, switching fabrics, or combinations thereof, and so forth. Although not explicitly illustrated inFIG. 5, one or more components of communication device102may be coupled to interconnect512via a discrete or integrated interface. By way of example only, one or more interfaces may couple a communication interface510or a processor502to at least one interconnect512. At least one power source514may provide power to components of communication device102. Power source514may comprise, by way of example but not limitation, a battery, a power connector, a solar power source or charger, a mechanical power source or charger, a fuel source, any combination thereof, and so forth.

For certain example embodiments, a user interface516may enable one or more users to interact with communication device102. Interactions between a user and device may relate, by way of example but not limitation, to touch/tactile/feeling/haptic sensory (e.g., a user may shake or move a device which may be detected by a gyroscope, an accelerometer, a compass, a combination thereof, etc; a user may press a button, slide a switch, rotate a knob, etc.; a user may touch a touch-sensitive screen; a device may vibrate; some combination thereof; etc.), to sound/hearing/speech sensory (e.g., a user may speak into a microphone, a device may generate sounds via a speaker, some combination thereof, etc.), to sights/vision sensory (e.g., a device may activate one or more lights, modify a display screen, a combination thereof, etc.), any combination thereof, and so forth.

For certain example embodiments, a user interface516may comprise a user interface input516a, a user output interface516b, a combination thereof, and so forth. A user input interface516amay comprise, by way of example but not limitation, a microphone, a button, a switch, a dial, a knob, a wheel, a trackball, a key, a keypad, a keyboard, a touch-sensitive screen, a touch-sensitive surface, a camera, a gyroscope, an accelerometer, a compass, any combination thereof, and so forth. A user output interface516bmay comprise, by way of example but not limitation, a speaker, a screen (e.g., with or without touch-sensitivity), a vibrating haptic feature, any combination thereof, and so forth. Certain user interfaces516may enable both user input and user output. For example, a touch-sensitive screen may be capable of providing user output and accepting user input. Additionally or alternatively, a user interface component (e.g., that may be integrated with or separate from a communication device102), such as a headset that has a microphone and a speaker, may enable both user input and user output.

It should be understood that for certain example implementations components illustrated separately inFIG. 5are not necessarily separate or mutually exclusive. For example, a given component may provide multiple functionalities. By way of example only, a single component such as a USB connector may function as a wired communication interface510band a power source514. Additionally or alternatively, a single component such as a display screen may function as a communication interface510with a user, as a user input interface516a, or as a user output interface516b. Additionally or alternatively, one or more instructions518may function to realize at least one setting520.

It should also be understood that for certain example implementations components illustrated in schematic diagram500or described herein may not be integral or integrated with a communication device102. For example, a component may be removably connected to a communication device102, a component may be wirelessly coupled to a communication device102, any combination thereof, and so forth. By way of example only, instructions518may be stored on a removable card having at least one medium504. Additionally or alternatively, a user interface516(e.g., a wired or wireless headset, a screen, a video camera, a keyboard, a combination thereof, etc.) may be coupled to communication device102wirelessly or by wire. For instance, a user may provide user input or accept user output corresponding to a voice communication modality to or from, respectively, a communication device102via a wireless (e.g., a Bluetooth®) headset.

FIG. 6is an example schematic diagram600of a network communication device and two communication devices that may be participating in a communication flow in accordance with certain example embodiments. As shown inFIG. 6, by way of example but not limitation, schematic diagram600may include communication devices102, users104, communication modalities106, at least one channel108, or at least one network communication device602. More specifically, schematic diagram600may include a first communication device102-1, a first user104-1, a first communication modality106-1, a second communication device102-2, a second user104-2, a second communication modality106-2, one or more channels108, or at least one network communication device602.

For certain example embodiments, a user104may be associated with a communication device102. A user104may be interacting with a communication device102via at least one communication modality106. More specifically, but by way of example only, first user104-1may be associated with first communication device102-1. First user104-1may be interacting with first communication device102-1via at least one first communication modality106-1. Additionally or alternatively, second user104-2may be associated with second communication device102-2. Second user104-2may be interacting with second communication device102-2via at least one second communication modality106-2. First communication device102-1or first user104-1may be participating in at least one communication flow (not explicitly shown inFIG. 6) with second communication device102-2or second user104-2via one or more channels108.

For certain example embodiments, a channel108may comprise, by way of example but not limitation, one or more of: at least one wired link, at least one wireless link, at least part of public network, at least part of a private network, at least part of a packet-switched network, at least part of a circuit-switched network, at least part of an infrastructure network, at least part of an ad hoc network, at least part of a public-switched telephone network (PSTN), at least part of a cable network, at least part of a cellular network connection, at least part of an Internet connection, at least part of a Wi-Fi connection, at least part of a WiMax connection, at least part of an internet backbone, at least part of a satellite network, at least part of a fibre network, multiple instances of any of the above, any combination of the above, and so forth. A channel108may include one or more nodes (e.g., a telecommunication node, an access point, a base station, an internet server, a gateway, any combination thereof, etc.) through which signals are propagated. A network communication device602may communicate with first communication device102-1or second communication device102-2using any one or more of multiple channels108, a few examples of which are shown in schematic diagram600.

For certain example implementations, a communication may be initiated by first communication device102-1, first user104-1, second communication device102-2, second user104-2, any combination thereof, and so forth. For certain example implementations, first communication modality106-1and second communication modality106-2may comprise a same one or more communication modalities106or may comprise at least one different communication modality106. Furthermore, for certain example implementations, first communication modality106-1or second communication modality106-2may change from one communication modality to another communication modality during a single communication, across different communications, and so forth. Additionally or alternatively, a different communication modality may be referred to herein as a “third communication modality” or a “fourth communication modality”, for example.

Moreover, it should be understood that the terms “first” or “second” may, depending on context, be a matter of perspective. For instance, a communication device102or a user104or a communication modality106may be considered a first one at a given moment, for a given communication, from a given perspective, etc. but may be considered a second one at a different moment, for a different communication, from a different perspective, etc. However, one of ordinary skill in the art will recognize that the term “first” or “second” (or “third” or “fourth” etc.) may serve, depending on context, to indicate that different interactions, acts, operations, functionality, a combination thereof, etc. may be occurring at, may be more closely associated with, a combination thereof etc. one side, aspect, location, combination thereof, etc. of a particular communication flow as compared to another side, aspect, location, combination thereof, etc. of the particular communication flow. For example, one signal including data may be transmitted from a first communication device102-1and received at a second communication device102-2, or another signal including data may be transmitted from a second communication device102-2and received at a first communication device102-1.

FIG. 7Ais a schematic diagram700A of an example network communication device in accordance with certain example embodiments. As shown inFIG. 7A, by way of example but not limitation, schematic diagram700A may include communication devices102, at least one network communication device602, or at least one communication flow710. More specifically, schematic diagram700A may include a first communication device102-1, a second communication device102-2, at least one network communication device602, at least one communication flow710, data712, converted data714, or one or more commands716. As illustrated, an example network communication device602may include a converter702or a signal manipulator704, which may include a receiver706or a transmitter708.

For certain example embodiments, a communication flow710may be created, may be extant, may be terminated, may be facilitated, some combination thereof, etc. between a first communication device102-1and a second communication device102-2. A communication flow710may comprise, by way of example but not limitation, a transmission, a reception, an exchange, etc. of data for a communication between two or more communication devices102, such as first communication device102-1and second communication device102-2. Data for a communication may correspond to any one or more of multiple communication modalities. Communication flows are described further herein below, by way of example but not limitation, with particular reference to at leastFIGS. 10A-10D.

For certain example embodiments, a network communication device602may include a converter702, a signal manipulator704, a combination thereof, and so forth. A signal manipulator704may include, by way of example but not limitation, a receiver706, a transmitter708, a combination thereof (e.g., a transceiver), and so forth. In certain example implementations, a converter702, a signal manipulator704, a receiver706, a transmitter708, or any combination thereof, etc. may be realized using any one or more components. Components are described herein below, by way of example but not limitation, with particular reference to at leastFIG. 9.

For certain example embodiments, a network communication device602may receive data712. A network communication device602may transmit converted data714. Although not explicitly indicated in schematic diagram700A, a network communication device602may additionally or alternatively transmit data712or receive converted data714. (Illustrated arrow directions are provided by way of example only.) For certain example implementations, network communication device602may transmit one or more commands716or may receive one or more commands716. Commands716may be transmitted to or received from a first communication device102-1, a second communication device102-2, another network communication device602, a telecommunications node, any combination thereof, and so forth.

For certain example embodiments, a network communication device602may enable the offloading of modality conversion for multi-modality communications. A receiver706may receive data corresponding to a first communication modality from at least one of a first communication device102-1or a second communication device102-2, with the data associated with a communication flow710between first communication device102-1and second communication device102-2. Communication flow710may comprise a multi-modality communication in which a first user (e.g., a first user104-1(e.g., ofFIG. 6)) interacts with first communication device102-1using at least one different communication modality than a second user (e.g., a second user104-2(e.g., ofFIG. 6)) interacts with second communication device102-2. For instance, a first communication modality (e.g., a first communication modality106-1(e.g., ofFIG. 6)) may differ from a second communication modality (e.g., a second communication modality106-2(e.g., ofFIG. 6)). A converter702may convert the data corresponding to the first communication modality to data corresponding to a second communication modality. A transmitter708may transmit the data corresponding to the second communication modality to at least one of the first communication device or the second communication device. However, a network communication device602may alternatively include more, fewer, or different modules from those that are illustrated without deviating from claimed subject matter.

FIG. 7Bis a schematic diagram700B of an example network communication device in accordance with certain example embodiments. As shown inFIG. 7B, by way of example but not limitation, schematic diagram700B may include communication devices102, at least one network communication device602, or at least one communication flow710. More specifically, schematic diagram700B may include a first communication device102-1, a second communication device102-2, at least one network communication device602, at least one communication flow710, data712, converted data714, one or more commands716, or at least one notification720. As illustrated, an example network communication device602may include a converter702; a signal manipulator704, which may include a receiver706or a transmitter708; or a notifier718.

For certain example embodiments, a communication flow710may be created, may be extant, may be terminated, may be facilitated, some combination thereof, etc. between a first communication device102-1and a second communication device102-2. A communication flow710may comprise, by way of example but not limitation, a transmission, a reception, an exchange, etc. of data for a communication between two or more communication devices102, such as first communication device102-1and second communication device102-2. Data for a communication may correspond to any one or more of multiple communication modalities. Communication flows are described further herein below, by way of example but not limitation, with particular reference to at leastFIGS. 10E-10H.

For certain example embodiments, a network communication device602may include a converter702, a signal manipulator704, a notifier718, a combination thereof, and so forth. A signal manipulator704may include, by way of example but not limitation, a receiver706, a transmitter708, a combination thereof (e.g., a transceiver), and so forth. In certain example implementations, a converter702, a signal manipulator704, a receiver706, a transmitter708, a notifier718, or any combination thereof, etc. may be realized using any one or more components. Components are described herein below, by way of example but not limitation, with particular reference to at leastFIG. 9.

For certain example embodiments, a network communication device602may receive data712. A network communication device602may transmit converted data714. Although not explicitly indicated in schematic diagram700B, a network communication device602may additionally or alternatively transmit data712or receive converted data714. (Illustrated arrow directions are provided by way of example only.) For certain example embodiments, a network communication device602may generate, analyze, process, transmit, receive, any combination thereof, etc. one or more notifications720. Examples of notifications720may include, but are not limited to, a signal, a message, a request, a packet, any combination thereof, and so forth. A notification720may pertain, by way of example but not limitation, to at least one aspect of a conversion related to a communication flow710. A notification720may be received from or transmitted to a communication device102, another network communication device602, a conversion service, any combination thereof, and so forth. Notification720examples are additionally or alternatively described herein below, by way of example but not limitation, with particular reference toFIGS. 10E-10H. For certain example implementations, network communication device602may transmit one or more commands716or may receive one or more commands716or may process or generate one or more commands716. Commands716may be transmitted to or received from a first communication device102-1, a second communication device102-2, another network communication device602, a telecommunications node, any combination thereof, and so forth.

For certain example embodiments, a network communication device602may implement interceptive conversion with multi-modality communications. A receiver706may receive from a first communication device102-1data712corresponding to a first communication modality (e.g., a first communication modality106-1(e.g., ofFIG. 6)), with data712corresponding to the first communication modality being associated with a communication flow710between first communication device102-1and a second communication device102-2. Communication flow710may comprise a multi-modality communication in which a first user (e.g., a first user104-1(e.g., ofFIG. 6)) is to interact with first communication device102-1using a first communication modality and a second user (e.g., a second user104-2(e.g., ofFIG. 6)) is to interact with second communication device102-2using a second communication modality (e.g., a second communication modality106-2(e.g., ofFIG. 6)). A converter702may convert data712corresponding to the first communication modality to data corresponding to the second communication modality (e.g., to produce converted data714). A transmitter708may transmit to second communication device102-2the data corresponding to the second communication modality. A transmitter708may also transmit to first communication device102-1a notification720of at least one aspect of a conversion applicable to communication flow710, wherein first communication device102-1is to have initiated communication flow710. However, a network communication device602may alternatively include more, fewer, or different components or modules from those that are illustrated without deviating from claimed subject matter. Moreover, although schematic diagrams700A and700B (e.g., ofFIGS. 7A and 7B, respectively) are illustrated and described herein separately, one or more aspects of either may be implemented with respect to the other, unless context dictates otherwise.

FIG. 8is a schematic diagram800of a network communication device including example settings or example parameters in accordance with certain example embodiments. As shown inFIG. 8, by way of example but not limitation, schematic diagram800may include at least one network communication device602. More specifically, at least one network communication device602may include one or more settings802, one or more parameters804, any combination thereof, and so forth. As illustrated, settings802may include at least a user identification (ID)806, one or more default preferences812, at least one auto-accept status814, at least one change notification indicator816, one or more conversion samples818, at least one language indication820, any combination thereof, and so forth. As illustrated, parameters804may include at least a communication flow identifier (ID)808, one or more communication flow endpoints810, at least one text delivery level indicator822, at least one conversion verification indicator824, at least one entry progress indicator826, at least one modality reminder indicator828, any combination thereof, and so forth. Although shown separately, different aspects that are described as a setting802or as a parameter804may additionally or alternatively be implemented as a parameter804or as a setting802, respectively. For certain example embodiments, different conversion-related aspects, including but not limited to changes thereto, may be sent to an associated user or another party that is participating in a communication flow with an associated user as one or more notifications (e.g., as one or more notifications720(e.g., ofFIG. 7B)).

For certain example embodiments, a setting802may be associated with a user (e.g., a user104(e.g., ofFIG. 6)), an account for an entity (e.g., a person, a business, a group, an organization, a combination thereof, etc.), a communication device (e.g., a communication device102(e.g., ofFIG. 6)), any combination thereof, and so forth. A setting802may, by way of example only, persist across multiple communication flows. By way of example but not limitation, settings802may include a user ID806, indicia of equipment (e.g., a communication device102(e.g., ofFIG. 6)) that is or are associated with a user, indicia of account(s) or contact information (e.g., phone numbers, messaging identifiers, a combination thereof, etc.) associated with a user, account information (e.g., billing information, contact information, a combination thereof, etc.), default user preferences812(e.g., preferences that may be implemented across multiple communication flows), any combination thereof, and so forth. A parameter804may correspond to a particular communication flow (or particular communication flows having at least one commonality) (e.g., a communication flow710(e.g., ofFIG. 7A or 7B)). By way of example but not limitation, parameters804may include a communication flow ID808, current preferences (e.g., one or more preferences to be implemented for a particular communication flow (or particular communication flows having at least one commonality)), indicia of one or more endpoints of a communication flow (e.g., communication flow endpoints810), redirect information for a communication flow (e.g., identification of one or more nodes to perform conversion), routing information for a communication flow, conversion parameters for data of a communication flow, any combination thereof, and so forth.

For certain example embodiments, one or more settings802may pertain to a user, a communication device, an account, any combination thereof, and so forth. For certain example implementations, at least one auto-accept status814may relate to whether an auto-accept feature is active. An auto-accept status814may additionally or alternatively indicate whether a conversion is to be implemented for a communication flow if auto-accept is implemented for an incoming communication notification. For certain example implementations, at least one change notification indicator816may indicate whether an associated user wishes to be notified if another participant in a communication flow makes a change (e.g., changes a conversion parameter). For certain example implementations, one or more conversion samples818may include one or more conversion samples from an associated user. By way of example but not limitation, a conversion sample may comprise sound samples from a user that may be utilized to generate synthesized voice from text. Also by way of example but not limitation, a conversion sample may comprise word vocalization samples from a user that may be utilized to enhance a conversion from voice to text. For certain example implementations, at least one language indication820may identify one or more languages that an associated user is capable of understanding (e.g., in text, in voice, in both text and voice, etc.).

For certain example embodiments, one or more parameters804may pertain to a user, a communication device, a particular communication flow or flows having at least one commonality, any combination thereof, and so forth. For certain example implementations, at least one text delivery level indicator822, may indicate a level of text to be delivered. Examples of text delivery levels may include, but are not limited to, an amount of text that may be transmitted as a block (e.g., at one time, in one transmission, until a response is made or received, a combination thereof, etc.), a speed of transmission or reception of text (e.g., characters per second, words per minute, a combination thereof, etc.), any combination thereof, and so forth. For certain example implementations, at least one conversion verification indicator824may indicate if a user, another participant, each participant, a combination thereof, etc. wishes to be provided an opportunity to receive a proposed conversion and approve or disapprove it prior to transmission to another party. For certain example implementations, at least one entry progress indicator826may indicate if a user wishes to be notified if another communication participant is currently entering communication data (e.g., speaking for voice, typing for text, a combination thereof, etc.). By way of example but not limitation, a notification may be presented to a user as a beep or other sound, a light or other visual indicator, an icon, a recorded message, a synthesized message, a combination thereof, and so forth. For certain example implementations, at least one modality reminder indicator828may indicate if a user wishes to be reminded of a communication modality with which another participant is currently interacting. By way of example but not limitation, a user that is interacting with text while another participant is interacting with voice may be reminded that the other participant is expecting real-time responses so that too much time does not elapse between consecutive responses. Also by way of example but not limitation, a user that is interacting with voice while another participant is interacting with text may be reminded that the other participant may prefer briefer communications relative to if the other participant was also interacting with voice. Reminders may comprise a beep or other sound, a light or other visual indicator, an icon, a recorded or synthesized message, a combination thereof, and so forth. Reminders may be provided at regular intervals, after a period of inactivity, a combination thereof, and so forth.

FIG. 9is a schematic diagram900of an example network communication device including one or more example components in accordance with certain example embodiments. As shown inFIG. 9, a network communication device602may include one or more components such as: at least one processor902, one or more media904, logic906, circuitry908, at least one communication interface910, at least one interconnect912, at least one power source914, or at least one entity interface916, any combination thereof, and so forth. Furthermore, as shown in schematic diagram900, one or more media may comprise one or more instructions918, one or more settings920, one or more parameters922, some combination thereof, and so forth; or communication interface910may comprise at least one wireless communication interface910a, at least one wired communication interface910b, some combination thereof, and so forth. However, a network communication device602may alternatively include more, fewer, or different components from those that are illustrated without deviating from claimed subject matter.

For certain example embodiments, a network communication device602may include or comprise at least one processing or computing device or machine. Network communication device602may comprise, for example, a computing platform or any electronic device or devices having at least one processor or memory. Processor902may comprise, by way of example but not limitation, any one or more of a general-purpose processor, a specific-purpose processor, a digital signal processor (DSP), a processing unit, a combination thereof, and so forth. A processing unit may be implemented, for example, with one or more application specific integrated circuits (ASICs), DSPs, digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), processors generally, processing cores, discrete/fixed logic circuitry, controllers, micro-controllers, microprocessors, a combination thereof, and so forth. Media904may bear, store, contain, provide access to, a combination thereof, etc. instructions918, which may be executable by processor902. Instructions918may comprise, by way of example but not limitation, a program, a module, an application or app (e.g., that is native, that runs in a browser, that runs within a virtual machine, a combination thereof, etc.), an operating system, etc. or portion thereof; operational data structures; processor-executable instructions; code; or any combination thereof; and so forth. Media904may comprise, by way of example but not limitation, processor-accessible or non-transitory media that is capable of bearing instructions, settings, parameters, a combination thereof, and so forth.

For certain example embodiments, execution of instructions918by one or more processors902may transform network communication device602into a special-purpose computing device, apparatus, platform, or any combination thereof, etc. Instructions918may correspond to, for example, instructions that are capable of realizing at least a portion of one or more flow diagrams methods, processes, operations, functionality, technology, or mechanisms, etc. that are described herein or illustrated in the accompanying drawings. Settings920(e.g., which may correspond to settings802(e.g., ofFIG. 8)) may comprise, by way of example but not limitation, one or more indicators that may be established by a user or other entity, one or more indicators that may determine at least partly how a network communication device602is to operate or respond to situations, one or more indicators or other values that may be used to realize flow diagrams, methods, processes, operations, functionality, technology, or mechanisms, etc. that are described herein or illustrated in the accompanying drawings. Parameters922(e.g., which may correspond to parameters804(e.g., ofFIG. 8)) may comprise, by way of example but not limitation, one or more indicators that may be established by a user or other entity, one or more indicators that may determine at least partly how a network communication device602is to operate or respond to situations, one or more indicators or other values that may be used to realize flow diagrams, methods, processes, operations, functionality, technology, or mechanisms, etc. that are described herein or illustrated in the accompanying drawings.

For certain example embodiments, logic906may comprise hardware, software, firmware, discrete/fixed logic circuitry, any combination thereof, etc. that is capable of performing or facilitating performance of methods, processes, operations, functionality, technology, or mechanisms, etc. that are described herein or illustrated in the accompanying drawings. Circuitry908may comprise hardware, software, firmware, discrete/fixed logic circuitry, any combination thereof, etc. that is capable of performing or facilitating performance of methods, processes, operations, functionality, technology, or mechanisms, etc. that are described herein or illustrated in the accompanying drawings, wherein circuitry908comprises at least one physical or hardware component or aspect.

For certain example embodiments, one or more communication interfaces910may provide one or more interfaces between network communication device602and another device or a person/operator/entity indirectly. A communication interface910may also or alternatively include, by way of example but not limitation, a transceiver (e.g., transmitter or receiver), a radio, an antenna, a wired interface connector or other similar apparatus (e.g., a network connector, a universal serial bus (USB) connector, a proprietary connector, a Thunderbolt® or Light Peak® connector, a combination thereof, etc.), a physical or logical network adapter or port, an internet or telecommunications backbone connector, or any combination thereof, etc. to communicate wireless signals or wired signals via one or more wireless communication links or wired communication links, respectively. Communications with at least one communication interface910may enable transmitting, receiving, or initiating of transmissions, just to name a few examples.

For certain example embodiments, at least one interconnect912may enable signal communication between or among components of network communication device602. Interconnect912may comprise, by way of example but not limitation, one or more buses, channels, switching fabrics, local area networks (LANs), storage area networks (SANs), or combinations thereof, and so forth. Although not explicitly illustrated inFIG. 9, one or more components of network communication device602may be coupled to interconnect912via a discrete or integrated interface. By way of example only, one or more interfaces may couple a communication interface910or a processor902to at least one interconnect912. At least one power source914may provide power to components of network communication device602. Power source914may comprise, by way of example but not limitation, a power connector for accessing an electrical grid, a fuel cell, a solar power source, any combination thereof, and so forth.

For certain example embodiments, an entity interface916may enable one or more entities (e.g., other devices, persons, groups, a combination thereof, etc.) to provide input to or receive output from network communication device602. Interactions between entities and a device may relate, by way of example but not limitation, to inputting instructions, commands, settings, parameters, any combination thereof, and so forth. Certain entity interfaces916may enable both entity input and entity output.

It should be understood that for certain example implementations components illustrated separately inFIG. 9are not necessarily separate or mutually exclusive. For example, a given component may provide multiple functionalities. By way of example only, hard-wired logic906may form circuitry908. Additionally or alternatively, a single component such as connector may function as a communication interface910or as an entity interface916. Additionally or alternatively, one or more instructions918may function to realize at least one setting920or at least one parameter922.

It should also be understood that for certain example implementations components illustrated in schematic diagram900or described herein may not be integral or integrated with a network communication device602. For example, a component may be removably connected to a network communication device602, a component may be wirelessly coupled to a network communication device602, any combination thereof, and so forth. By way of example only, instructions918may be stored on one medium904, and settings902or parameters922may be stored on a different medium904. Additionally or alternatively, respective processor-media pairs may be physically realized on respective server blades. Multiple server blades, for instance, may be linked to realize at least one network communication device602.

FIGS. 10A, 10B, 10C, and 10Ddepict example sequence diagrams1002,1004,1006, and1008, respectively, for example multi-modality communications. As shown, by way of example but not limitation, each sequence diagram may include a first communication device102-1, a second communication device102-2, or a network communication device602, as well as multiple actions. Although actions of sequence diagrams1002,1004,1006, and1008are shown or described in a particular sequence, it should be understood that methods or processes may be performed in alternative manners without departing from claimed subject matter, including, but not limited to, with a different sequence or number of actions, with a different relationship between or among actions, with a different communication device (or node) performing action(s), or any combination thereof, and so forth. Also, at least some actions of sequence diagrams1002,1004,1006, and1008may be performed so as to be fully or partially overlapping with other action(s) in a temporal sense, in a communication sense (e.g., over one or more channels), in a processing sense (e.g., using multiple cores, multitasking, a combination thereof, etc.), some combination thereof, and so forth. By way of example only, a given communication or channel may comprise a fully or partially duplex communication, thereby enabling independent or overlapping transmissions or receptions.

As depicted, by way of example but not limitation, each example multi-modality communication includes a communication flow that may be initiated by a first communication device102-1. However, multi-modality communications may alternatively or additionally include communications that may be initiated by a second communication device102-2. As illustrated, by way of example but not limitation, each example multi-modality communication may involve at least two communication modalities that include voice interaction or text interaction by a user of a first or a second communication device102-1or102-2. However, multi-modality communications may alternatively or additionally involve two or more communication modalities that include voice interaction, text interaction, video interaction, any combination thereof, and so forth. As shown, by way of example but not limitation, a second communication device102-2, in conjunction with an indication from a second user104-2(e.g., ofFIG. 6), may determine that a communication is to comprise a multi-modality communication at or around when a communication flow is initiated. However, a first communication device102-1(or a user thereof) may additionally or alternatively determine that a communication flow is to comprise a multi-modality communication. Furthermore, a communication flow may be migrated to a multi-modality communication or from one modality type conversion to another modality type conversion at virtually any time during a communication by a communication device or a network communication device. Moreover, a communication device may additionally or alternatively initiate a communication flow as a multi-modality communication.

For certain example embodiments, sequence diagrams1002,1004,1006, and1008may include one or more transmissions or receptions. Transmissions or receptions may be made, by way of example but not limitation, from or to a first communication device102-1, from or to a second communication device102-2, or from or to a network communication device602. A given transmission or reception may be made via any one or more channels108(e.g., ofFIG. 6). Examples of channels may include, but are not limited to, a voice connection channel, a voice data channel, a voice over internet protocol (VOIP) channel, a packet data channel, a signaling channel, a channel over the Internet (e.g., a session), a cellular-text-messaging channel, an internet or telecommunications backbone, any combination thereof, and so forth. Additionally or alternatively, although two communication devices and one network communication device are shown as participating in a given communication flow, more than two communication devices, more than two users, or more than one network communication device may participate in a given communication flow.

FIGS. 10A and 10Bare sequence diagrams1002and1004that jointly illustrate an example multi-modality communication in which conversion may be performed at a network communication device via transmission of data external to a core communication flow in accordance with certain example embodiments. As shown inFIGS. 10A and 10B, by way of example but not limitation, one or more of actions1002a-1002jor1004a-1004hmay be performed for a communication flow. For example sequence diagrams1002and1004, a network communication device602may perform conversions that have been farmed out by a communication device, such as second communication device102-2.

For certain example embodiments, at action1002a, a first communication device102-1may transmit or a second communication device102-2may receive a notification of an incoming communication that corresponds to voice. By way of example but not limitation, a notification may comprise a text message, a ringing signal, a communication inquiry, a communication notice, a session initiation message, any combination thereof, and so forth. At action1002b, second communication device102-2may determine that a communication flow may continue in a manner that is at least partially corresponding to text. For certain example implementations, second communication device102-2may make a determination based, at least partly, on an existing intimacy setting (e.g., on a current default intimacy setting), on a contemporaneous intimacy setting indication provided by second user104-2(e.g., by a second user without prompting, by a second user in response to options presented by a second communication device in conjunction with presentation of a call notification to the second user, some combination thereof, etc.), any combination thereof, and so forth.

For certain example embodiments, at action1002c, a second communication device102-2may transmit or a first communication device102-1may receive a message indicating that a communication flow is accepted if it may correspond at least partially to text. At action1002d, a first communication device102-1may provide a first user104-1with an opportunity to switch to text (e.g., to establish a single-modality textual communication), with an opportunity to continue a communication with first user interactivity including voice (e.g., to establish a dual-modality voice and textual communication), with an opportunity to propose a different one or more interactivity-types of communication(s), any combination thereof, and so forth. For certain examples as described herein, with respect to action1002d, it is given that a first user104-1elects to continue a communication flow as a multi-modality communication with voice interaction for first user104-1and (at least partial) textual interaction for second user104-2. This election may be communicated to second communication device102-2.

For certain example embodiments, at action1002e, a first communication device102-1may accept user voice input. For an example implementation, a first communication device102-1may enable voice interaction with a first user104-1(not shown inFIG. 10A) by accepting voice input via at least one user input interface516a(e.g., ofFIG. 5), such as at least one microphone. At action1002f, a first communication device102-1may transmit or a second communication device102-2may receive voice data. At action1002g, second communication device102-2may forward the received voice data. For an example implementation, a second communication device102-2may forward voice data to a known web service that provides conversion services from voice to text. A known web service may be free and usable without registration, may be free and usable upon registration, may impose a fee and involve registration, any combination thereof, and so forth.

For certain example embodiments, at action1002h, a second communication device102-2may transmit or a network communication device602may receive voice data. At action1002i, a network communication device602may convert voice data to text (e.g., to converted text data). At action1002j, a network communication device602may transmit or a second communication device102-2may receive converted text data. As indicated inFIG. 10A, sequence diagram1002is continued with sequence diagram1004ofFIG. 10B.

With reference toFIG. 10B, for certain example embodiments, at action1004a, a second communication device102-2may present text output (e.g., as converted by network communication device602) to a second user104-2(not shown inFIG. 10B). For an example implementation, a second communication device102-2may display text to a second user104-2via at least one user output interface516b(e.g., ofFIG. 5), such as at least one display screen. At action1004b, a second communication device102-2may accept user text input. For an example implementation, a second communication device102-2may accept text input from a second user104-2via at least one user input interface516a, such as a physical or virtual keyboard.

For certain example embodiments, at action1004c, a second communication device102-2may transmit or a network communication device602may receive text data. At action1004d, a network communication device602may convert text data to voice (e.g., to converted voice data). At action1004e, a network communication device602may transmit or a second communication device102-2may receive converted voice data.

For certain example embodiments, at action1004f, a second communication device102-2may determine that the received converted voice data is to be forwarded to a first communication device102-1. For an example implementation, the converted voice data may be forwarded to first communication device102-1via a voice channel already established (and maintained) between second communication device102-2and first communication device102-1for a given communication flow. At action1004g, a second communication device102-2may transmit or a first communication device102-1may receive converted voice data. At action1004h, a first communication device102-1may present voice data as voice output to a first user104-1, which voice data may comprise converted voice data that was converted by a network communication device602and forwarded by another communication device, such as second communication device102-2.

FIGS. 10C and 10Dare sequence diagrams1006and1008that jointly illustrate an example multi-modality communication in which conversion may be performed at a network communication device via transmission of data within a core communication flow in accordance with certain example embodiments. As shown inFIGS. 10C and 10D, by way of example but not limitation, one or more of actions1006a-1006hor1008a-1008fmay be performed for a communication flow. For example sequence diagrams1006and1008, a network communication device602may perform conversions via a detour of a communication flow to network communication device602.

For certain example embodiments, at action1006a, a first communication device102-1may transmit or a second communication device102-2may receive a notification of an incoming communication that corresponds to voice. By way of example but not limitation, a notification may comprise a text message, a ringing signal, a communication inquiry, a session initiation message, a communication notice, any combination thereof, and so forth. At action1006b, second communication device102-2may determine that a communication flow may continue in a manner that is at least partially corresponding to text. For certain example implementations, second communication device102-2may make a determination based, at least partly, on an existing intimacy setting (e.g., on a current default intimacy setting), on a contemporaneous intimacy setting indication provided by second user104-2(e.g., by a second user without prompting, by a second user in response to options presented by a second communication device in conjunction with presentation of a call notification to the second user, some combination thereof, etc.), any combination thereof, and so forth. Second communication device102-2or a user thereof may also determine that conversions are to be performed by a network communication device, such as network communication device602, via a detour of a communication flow. A designated network communication device may be accessible via a reference. By way of example but not limitation, a reference may comprise a network address, a uniform resource locator (URL), any combination thereof, and so forth.

For certain example embodiments, at action1006c, a second communication device102-2may transmit or a first communication device102-1may receive a message indicating that a communication flow is accepted if it may correspond at least partially to text. For certain example implementations, a message may include a reference to a network communication device that is to perform conversions. At action1006d, a first communication device102-1may provide a first user104-1with an opportunity to switch to text (e.g., to establish a single-modality textual communication), with an opportunity to continue a communication with first user interactivity including voice (e.g., to establish a dual-modality voice and textual communication), with an opportunity to propose a different one or more interactivity-types of communication(s), with an opportunity to approve a designated conversion service, with an opportunity to request a different conversion service, any combination thereof, with an opportunity to perform the conversion itself, and so forth. For certain examples as described herein, with respect to action1006d, it is given that a first user104-1elects to continue a communication flow as a multi-modality communication with voice interaction for first user104-1and (at least partial) textual interaction for second user104-2and that a referenced conversion service may be used for conversion.

For certain example embodiments, at action1006e, a first communication device102-1may accept user voice input. At action1006f, a first communication device102-1may transmit (e.g., to a destination corresponding to a reference received at action1006c) or a network communication device602may receive voice data. At action1006g, a network communication device602may convert voice data to text (e.g., to converted text data). At action1006h, a network communication device602may transmit or a second communication device102-2may receive converted text data. Network communication device602may be informed of a destination for converted text data of a given communication flow as part of action1006f(e.g., from first communication device102-1). Additionally or alternatively, network communication device602may be informed of a destination for converted text data of a given communication flow via a message (not explicitly shown) that is received from second communication device102-2. As indicated inFIG. 10C, sequence diagram1006is continued with sequence diagram1008ofFIG. 10D.

With reference toFIG. 10D, for certain example embodiments, at action1008a, a second communication device102-2may present text output (e.g., as converted by network communication device602) to a second user104-2. At action1008b, a second communication device102-2may accept user text input. At action1008c, a second communication device102-2may transmit or a network communication device602may receive text data. At action1008d, a network communication device602may convert text data to voice (e.g., to converted voice data). For certain example implementations, a network communication device602may access parameters804(e.g., ofFIG. 8) at an entry that corresponds to a given communication flow (e.g., as indicated by a communication flow ID808) to determine a communication flow endpoint (e.g., from communication flow endpoint(s)810) or a channel on which to transmit converted voice data. At action1008e, a network communication device602may transmit or a first communication device102-1may receive converted voice data. For an example implementation, the converted voice data may be sent to first communication device102-1via a voice channel already established (and maintained) between network communication device602and first communication device102-1for a given communication flow (e.g., that is used for action1006f). At action1008f, a first communication device102-1may present voice data as voice output to a first user104-1, which voice data may comprise converted voice data that was converted by a network communication device602and sent to first communication device102-1by network communication device602.

FIGS. 10E, 10F, 10G, and 10Hdepict example sequence diagrams1010,1012,1014, and1016, respectively, for example multi-modality communications. As shown, by way of example but not limitation, each sequence diagram may include a first communication device102-1, a second communication device102-2, or a network communication flow device602*, as well as multiple actions. Although actions of sequence diagrams1010,1012,1014, and1016are shown or described in a particular sequence, it should be understood that methods or processes may be performed in alternative manners without departing from claimed subject matter, including, but not limited to, with a different sequence or number of actions, with a different relationship between or among actions, with a different communication device (or node) performing action(s), or any combination thereof, and so forth. Also, at least some actions of sequence diagrams1010,1012,1014, and1016may be performed so as to be fully or partially overlapping with other action(s) in a temporal sense, in a communication sense (e.g., over one or more channels), in a processing sense (e.g., using multiple cores, multitasking, a combination thereof, etc.), some combination thereof, and so forth. By way of example only, a given communication or channel may comprise a fully or partially duplex communication, thereby enabling independent or overlapping transmissions or receptions.

For certain example embodiments, a network communication device602may comprise a network communication flow device602*. As used herein, a network communication flow device602* may comprise a network communication device602through which data of a communication flow is to propagate regardless of whether a conversion is to be applied to the communication flow. By way of example but not limitation, a telecommunications node that is routing data for a communication flow between two communication devices102regardless of whether communication-modality-conversion processing is to be applied to the communication flow may comprise a network communication flow device602*. As another example, but not by way of limitation, an internet server or cable node that is routing voice-over-IP (VoIP) data between two communication devices102regardless of whether communication-modality-conversion processing is to be applied to the communication flow may comprise a network communication flow device602*. Although schematic diagrams1010,1012,1014, and1016(e.g., ofFIGS. 10E, 10F, 10G, and 10H, respectively) are illustrated and described with regard to an example network communication flow device602* and schematic diagrams1002,1004,1006, and1008(e.g., ofFIGS. 10A, 10B, 10c, and10D, respectively) are illustrated and described with regard to an example network communication device602, one or more aspects of any schematic diagram may be implemented with respect to another schematic diagram, unless context dictates otherwise.

As depicted, by way of example but not limitation, each example multi-modality communication includes a communication flow that may be initiated by a first communication device102-1. However, multi-modality communications may alternatively or additionally include communications that may be initiated by a second communication device102-2. As illustrated, by way of example but not limitation, each example multi-modality communication may involve at least two communication modalities that include voice interaction or text interaction by a user of a first or a second communication device102-1or102-2. However, multi-modality communications may alternatively or additionally involve two or more communication modalities that include voice interaction, text interaction, video interaction, any combination thereof, and so forth. As shown in sequence diagrams1010and1012, by way of example but not limitation, a second communication device102-2, such as in conjunction with an indication from a second user104-2(e.g., ofFIG. 6), may determine that a communication is to comprise a multi-modality communication at or around when a communication flow is initiated. However, a first communication device102-1(or a user thereof) may additionally or alternatively determine that a communication flow is to comprise a multi-modality communication at or around a time of initiation of the communication flow.

Additionally or alternatively, as shown in sequence diagrams1014and1016, by way of example but not limitation, a second communication device102-2, such as in conjunction with an indication from a second user104-2(e.g., ofFIG. 6), may determine that one or more future communications are to comprise one or more multi-modality communications prior to when a communication flow is initiated (e.g., by establishing one or more settings at a network communication flow device602*). However, a first communication device102-1(or a user thereof) may additionally or alternatively determine that a communication flow is to be a multi-modality communication prior to a time of initiation of the communication flow. Furthermore, a communication flow may be migrated to a multi-modality communication or from one modality type conversion to another modality type conversion at virtually any time during a communication by a communication device or a network communication device. Moreover, a communication device may additionally or alternatively initiate a communication flow as a multi-modality communication.

For certain example embodiments, sequence diagrams1010,1012,1014, and1016may include one or more transmissions or receptions. Transmissions or receptions may be made, by way of example but not limitation, from or to a first communication device102-1, from or to a second communication device102-2, or from or to a network communication flow device602*. A given transmission or reception may be made via any one or more channels108(e.g., ofFIG. 6). Examples of channels may include, but are not limited to, a voice connection channel, a voice data channel, a voice over internet protocol (VOIP) channel, a packet data channel, a signaling channel, a channel over the Internet (e.g., a session), a cellular-text-messaging channel, an internet or telecommunications backbone, any combination thereof, and so forth. Additionally or alternatively, although two communication devices and one network communication device (e.g., a network communication flow device602*) are shown as participating in a given communication flow, more than two communication devices, more than two users, or more than one network communication device may participate in a given communication flow.

FIGS. 10E and 10Fare sequence diagrams1010and1012that jointly illustrate an example multi-modality communication in which interceptive conversion may be performed at a network communication flow device responsive to a current request from a destination device in accordance with certain example embodiments. As shown inFIGS. 10E and 10F, by way of example but not limitation, one or more of actions1010a-1010jor1012a-1012hmay be performed for a communication flow. For example sequence diagrams1010and1012, a network communication flow device602* may perform conversions by virtue of being positioned to intercept data sent between first communication device102-1and second communication device102-2or responsive to a roughly contemporaneous request from a second communication device102-2.

For certain example embodiments, at action1010a, a first communication device102-1may transmit or a network communication flow device602* may receive a notification of an incoming communication that corresponds to voice. By way of example but not limitation, a notification may comprise a text message, a ringing signal, a communication inquiry, a communication notice, a session initiation message, any combination thereof, and so forth. At action1010b, a network communication flow device602* may transmit or a second communication device102-2may receive a notification of an incoming communication that corresponds to voice (e.g., a network communication flow device602* may generate or may forward or route to second communication device102-2a notification of an incoming communication that corresponds to voice).

For certain example embodiments, at action1010c, second communication device102-2may determine that a communication flow may continue in a manner that is at least partially corresponding to text. For certain example implementations, second communication device102-2may make a determination based, at least partly, on an existing intimacy setting (e.g., on a current default intimacy setting), on a contemporaneous intimacy setting indication provided by second user104-2(e.g., ofFIG. 6) (e.g., by a second user without prompting, by a second user in response to options presented by a second communication device in conjunction with presentation of a call notification to the second user, some combination thereof, etc.), any combination thereof, and so forth.

For certain example embodiments, at action1010d, a second communication device102-2may transmit or a network communication flow device602* may receive a message indicating that a communication flow is accepted if it may correspond at least partially to text. For certain example implementations, a message indicating that a communication flow is accepted or a different message may request that a conversion service be established by network communication flow device602* for the instant communication flow. A message or messages may specify parameters (e.g., parameters804(e.g., ofFIG. 8)) for a conversion, may reference conversion settings (e.g., settings802(e.g., ofFIG. 8)) for second communication device102-2or a user of second communication device102-2, some combination thereof, and so forth. At action1010e, a network communication flow device602* may transmit or a first communication device102-1may receive a message indicating that a communication flow is accepted if it may correspond at least partially to text. For certain example implementations, a message indicating that a communication flow is accepted or a different message may notify a first communication device102-1of one or more settings or one or more parameters related to at least one aspect of a requested conversion.

For certain example embodiments, at action1010f, a first communication device102-1may provide a first user104-1(e.g., ofFIG. 6) with an opportunity to switch to text (e.g., to establish a single-modality textual communication), with an opportunity to continue a communication with first user interactivity including voice (e.g., to establish a dual-modality voice and textual communication), with an opportunity to propose a different one or more interactivity-types of communication(s), with an opportunity to request one or more settings or parameters be changed, with an opportunity to elect to perform a conversion (e.g., fully or partially in lieu of a conversion being performed by a network communication flow device602*), any combination thereof, and so forth. For certain examples as described herein, with respect to action1010f, it is given that a first user104-1elects to continue a communication flow as a multi-modality communication with voice interaction for first user104-1and (at least partial) textual interaction for second user104-2and with conversion being performed by network communication flow device602*. This election may be communicated to a network communication flow device602* or second communication device102-2(not explicitly shown inFIG. 10E). At action1010g, a first communication device102-1may accept user voice input. For an example implementation, a first communication device102-1may enable voice interaction with a first user104-1by accepting voice input via at least one user input interface516a(e.g., ofFIG. 5), such as at least one microphone. At action1010h, a first communication device102-1may transmit or a network communication flow device602* may receive voice data.

For certain example embodiments, at action1010i, a network communication flow device602* may maintain a voice communication channel. For certain example implementations, a network communication flow device602* may maintain at least a voice communication channel at least with first communication device102-1(e.g., at least partially while network communication flow device602* communicates with second communication device102-2via at least text). At action1010j, a network communication flow device602* may convert voice data to text (e.g., to converted text data). As indicated inFIG. 10E, sequence diagram1010is continued with sequence diagram1012ofFIG. 10F.

With reference toFIG. 10F, for certain example embodiments, at action1012a, a network communication flow device602* may transmit or a second communication device102-2may receive converted text data. At action1012b, a second communication device102-2may present text output (e.g., as converted by network communication flow device602*) to a second user104-2(e.g., ofFIG. 6). For an example implementation, a second communication device102-2may display text to a second user104-2via at least one user output interface516b(e.g., ofFIG. 5), such as at least one display screen. At action1012c, a second communication device102-2may accept user text input. For an example implementation, a second communication device102-2may accept text input from a second user104-2via at least one user input interface516a, such as a physical or virtual keyboard. At action1012d, a second communication device102-2may transmit or a network communication flow device602* may receive text data.

For certain example embodiments, at action1012e, a network communication flow device602* may convert text data to voice (e.g., to converted voice data). At action1012f, a network communication flow device602* may determine that the converted voice data is to be sent to a first communication device102-1. For an example implementation, the converted voice data may be sent to first communication device102-1via a voice channel already established (and maintained) between network communication flow device602* and first communication device102-1for a given communication flow. At action1012g, a network communication flow device602* may transmit or a first communication device102-1may receive converted voice data. At action1012h, a first communication device102-1may present voice data as voice output to a first user104-1, which voice data may comprise converted voice data that was converted by a network communication flow device602*.

FIGS. 10G and 10Hare sequence diagrams1014and1016that jointly illustrate an example multi-modality communication in which interceptive conversion may be performed at a network communication flow device responsive to a previous request or an established setting from a destination device in accordance with certain example embodiments. As shown inFIGS. 10G and 10H, by way of example but not limitation, one or more of actions1014a-1014for1016a-1016emay be performed for a communication flow. For example sequence diagrams1014and1016, a network communication flow device602* may perform conversions by virtue of being positioned to intercept data sent between first communication device102-1and second communication device102-2or responsive to a previous request or a stored setting from a second communication device102-2or a user thereof.

For certain example embodiments, at action1014a, a second communication device102-2or a second user104-2(e.g., ofFIG. 6) may determine that a future incoming voice communication is to be auto-accepted and converted to text. At action1014b, a second communication device102-2may transmit or a network communication flow device602* may receive a request to establish a conversion service. A request may indicate that incoming voice communications are to be auto-accepted as text (e.g., by a network communication flow device602*) and that voice data is to be converted to text data (e.g., by a network communication flow device602*). Additionally or alternatively, a second user104-2may establish settings or parameters for conversion of communications in which a second communication device102-2is to participate using a different device than second communication device102-2.

For certain example embodiments, at action1014c, a network communication flow device602* may establish a voice-text conversion service or an auto-accept (e.g., an auto-answer) service for second communication device102-2responsive to a request. For an example implementation, a network communication flow device602* may establish an auto-answer setting for incoming voice calls that are to be accepted as corresponding at least partially to text and may establish a voice-text conversion service. At action1014d, a network communication flow device602* may transmit or a second communication device102-2may receive a notification confirming that a conversion service or an auto-accept setting has been established.

For certain example embodiments, after an auto-answer or conversion service has been established (e.g., at action1014c), at action1014e, a first communication device102-1may transmit or a network communication flow device602* may receive an incoming voice communication notice. By way of example but not limitation, a notification may comprise a text message, a ringing signal, a communication inquiry, a communication notice, a session initiation message, any combination thereof, and so forth. For certain example implementations, a notification may include a destination, such as second communication device102-2or a second user104-2, for a communication flow. At action1014f, a network communication flow device602* may ascertain that a destination for an incoming voice communication notice has pre-established an auto-answer service or a voice-text conversion service. As indicated inFIG. 10G, sequence diagram1014is continued with sequence diagram1016ofFIG. 10H.

With reference toFIG. 10H, for certain example embodiments, at action1016a, a network communication flow device602* may determine that a communication flow may continue in a manner that is at least partially corresponding to text based on, at least partly, at least one auto-answer voice calls setting, at least one voice-text conversion setting, at least one auto-answer-voice-calls-as-text setting, some combination thereof, and so forth. For certain example implementations, a network communication flow device602* may make a determination responsive to a previous request by a second communication device102-2or a second user104-2, responsive to stored settings (e.g., settings802(e.g., ofFIG. 8)), responsive to stored parameters (e.g., parameters804(e.g., ofFIG. 8)), any combination thereof, and so forth. At action1016b, a network communication flow device602* may transmit or a first communication device102-1may receive a message indicating that a communication flow is accepted if it may correspond at least partially to text. For certain example implementations, a message indicating that a communication flow is accepted or a different message may notify a first communication device102-1of one or more settings or one or more parameters related to a conversion for a requested communication. Although not shown in sequence diagram1016ofFIG. 10H, a communication flow between first communication device102-1and second communication device102-2may continue after action1016bin accordance with actions1010f-1010jof sequence diagram1010(e.g., ofFIG. 10E) or actions1012a-1012hof sequence diagram1012(e.g., ofFIG. 10F).

For certain example embodiments, e.g. during a communication flow between first communication device102-1and second communication device102-2, second communication device102-2may request to change one or more aspects of a conversion service. At action1016c, a second communication device102-2may transmit or a network communication flow device602* may receive a request to change at least one aspect of a conversion service that is being provided by network communication flow device602*. At action1016d, network communication flow device602* may determine that another participant is to be notified of a conversion service change. At action1016e, a network communication flow device602* may transmit or a first communication device102-1may receive a notification of a change to at least one aspect of conversion service, such as a change to at least one conversion parameter, at least one conversion setting, at least one communication modality, any combination thereof, and so forth. Although not shown in sequence diagram1016, in response to a notification, first communication device102-1may be afforded an opportunity to terminate a communication flow, reject a (proposed) conversion parameter change, request a conversion parameter change, negotiate a different conversion parameter change, any combination thereof, and so forth. Although not shown in sequence diagram1016, first communication device102-1may additionally or alternatively request a change to a conversion service (e.g., request from or request a change by network communication flow device602*), or second communication device102-2may receive a notification of a requested conversion service parameter change from network communication flow device602*.

FIG. 11Ais a flow diagram1100A illustrating an example method for a network communication device that may perform a conversion for a communication flow between first and second communication devices in accordance with certain example embodiments. As illustrated, flow diagram1100A may include any of operations1102-1106. Although operations1102-1106are shown or described in a particular order, it should be understood that methods may be performed in alternative manners without departing from claimed subject matter, including, but not limited to, with a different order or number of operations or with a different relationship between or among operations. Also, at least some operations of flow diagram1100A may be performed so as to be fully or partially overlapping with other operation(s).

For certain example embodiments, a method for conversion offloading with multi-modality communications may be at least partially implemented using hardware and may comprise an operation1102, an operation1104, or an operation1106. An operation1102may be directed at least partially to receiving data corresponding to a first communication modality from at least one of a first communication device or a second communication device, the data associated with a communication flow between the first communication device and the second communication device, the communication flow comprising a multi-modality communication in which a first user interacts with the first communication device using at least one different communication modality than a second user interacts with the second communication device. By way of example but not limitation, a network communication device602may receive via a receiver706data corresponding to a first communication modality106-1from at least one of a first communication device102-1or a second communication device102-2(e.g., in accordance with an action1002h,1004c,1006f,1008c, a combination thereof, etc.). Data may be associated with a communication flow710between first communication device102-1and second communication device102-2. Communication flow710may comprise a multi-modality communication in which a first user104-1interacts with first communication device102-1using at least one different communication modality as compared to a communication modality or modalities used by a second user104-2to interact with second communication device102-2. However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.

For certain example embodiments, an operation1104may be directed at least partially to converting the data corresponding to the first communication modality to data corresponding to a second communication modality. By way of example but not limitation, a network communication device602may convert via a converter702data corresponding to a first communication modality106-1to data corresponding to a second communication modality106-2(e.g., in accordance with an action1002i,1004d,1006g,1008d, a combination thereof, etc.). An operation1106may be directed at least partially to transmitting the data corresponding to the second communication modality to at least one of the first communication device or the second communication device. By way of example but not limitation, a network communication device602may transmit via a transmitter708the data corresponding to the second communication modality106-2to at least one of the first communication device102-1or the second communication device102-2(e.g., in accordance with an action1002j,1004e,1006h,1008e, a combination thereof, etc.). However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.

FIGS. 11B-11Jdepict example alternatives for a flow diagram ofFIG. 11Ain accordance with certain example embodiments. As illustrated, flow diagrams ofFIGS. 11B-11Jmay include any of the illustrated or described operations. Although operations are shown or described in a particular order, it should be understood that methods may be performed in alternative manners without departing from claimed subject matter, including, but not limited to, with a different order or number of operations or with a different relationship between or among operations. Also, at least some operations of flow diagrams ofFIGS. 11B-11Jmay be performed so as to be fully or partially overlapping with other operation(s).

FIG. 11Billustrates a flow diagram1100B having example operations1110or1112. For certain example embodiments, an operation1110may be directed at least partially to wherein the receiving data corresponding to a first communication modality from at least one of a first communication device or a second communication device (e.g., of operation1102) comprises receiving the data corresponding to the first communication modality from the second communication device (for an operation1110a); and wherein the transmitting the data corresponding to the second communication modality to at least one of the first communication device or the second communication device (e.g., of operation1106) comprises transmitting the data corresponding to the second communication modality to the second communication device (for an operation1110b). By way of example but not limitation, data may be received from and converted data may be transmitted to a same communication device, such as a second communication device102-2(e.g., in accordance with actions1002hand1002j, actions1004cand1004e, a combination thereof, etc.). However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.

For certain example embodiments, an operation1112may be directed at least partially to wherein the receiving data corresponding to a first communication modality from at least one of a first communication device or a second communication device (e.g., of operation1102) further comprises receiving the data corresponding to the first communication modality from the first communication device (for an operation1112a); and wherein the transmitting the data corresponding to the second communication modality to at least one of the first communication device or the second communication device (e.g., of operation1106) further comprises transmitting the data corresponding to the second communication modality to the second communication device (for an operation1112b). By way of example but not limitation, data may be received from one communication device, such as first communication device102-1, and converted data may be transmitted to a different communication device, such as a second communication device102-2(e.g., in accordance with actions1006fand1006h, actions1008cand1008e, a combination thereof, etc.). For certain example implementations, a conversion scenario may switch from farming out conversions in accordance with sequence diagrams1002and1004to detouring a communication flow to perform conversions in accordance with sequence diagrams1006and1008during a given communication flow (e.g., during a single phone call or voice session). However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.

FIG. 11Cillustrates a flow diagram1100C having example operations1108,1114,1116,1122, or1124. As illustrated, one or more operations1108may be performed in addition to those operations1102,1104, and1106of flow diagram1100A. For certain example embodiments, an operation1114may be directed at least partially to receiving from the second communication device during the communication flow a command to begin receiving the data corresponding to the first communication modality from the first communication device. By way of example but not limitation, a network communication device602may receive from a second communication device102-2during a communication flow710a command716to begin receiving data corresponding to a first communication modality106-1from a first communication device102-1(e.g., without first passing through second communication device102-2). For certain example implementations, a conversion scenario may be switched thusly to reduce latency, to reduce a number or amount of transmissions, any combination thereof, and so forth. However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.

For certain example embodiments, an operation1116may be directed at least partially to transmitting from a network communication device to the first communication device during the communication flow a command to begin transmitting the data corresponding to the first communication modality from the first communication device to the network communication device. By way of example but not limitation, a network communication device602may transmit a command716to a first communication device102-1during a communication flow710to begin transmitting data corresponding to a first communication modality106-1from first communication device102-1to network communication device602(e.g., instead of transmitting data corresponding to a first communication modality106-1from first communication device102-1to second communication device102-2). Additionally or alternatively, a second communication device102-2may transmit a command to a first communication device102-1during a communication flow710to begin transmitting data corresponding to a first communication modality106-1from first communication device102-1to network communication device602. However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.

FIG. 11Dillustrates a flow diagram1100D having example operations1118or1120. For certain example embodiments, an operation1118may be directed at least partially to wherein the receiving data corresponding to a first communication modality from at least one of a first communication device or a second communication device (e.g., of operation1102) comprises receiving the data corresponding to the first communication modality from the first communication device (for an operation1118a); and wherein the transmitting the data corresponding to the second communication modality to at least one of the first communication device or the second communication device (e.g., of operation1106) comprises transmitting the data corresponding to the second communication modality to the second communication device (for an operation1118b). By way of example but not limitation, data may be received from one communication device, such as first communication device102-1, and converted data may be transmitted to a different communication device, such as a second communication device102-2(e.g., in accordance with actions1006fand1006h, actions1008cand1008e, a combination thereof, etc.). However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.

For certain example embodiments, an operation1120may be directed at least partially to wherein the receiving data corresponding to a first communication modality from at least one of a first communication device or a second communication device (e.g., of operation1102) further comprises receiving the data corresponding to the first communication modality from the second communication device (for an operation1120a); and wherein the transmitting the data corresponding to the second communication modality to at least one of the first communication device or the second communication device (e.g., of operation1106) further comprises transmitting the data corresponding to the second communication modality to the second communication device (for an operation1120b). By way of example but not limitation, data may be received from and converted data may be transmitted to a same communication device, such as a second communication device102-2(e.g., in accordance with actions1002hand1002j, actions1004cand1004e, a combination thereof, etc.). For certain example implementations, a conversion scenario may switch from performing conversions within a core communication flow (e.g., that has been detoured) in accordance with sequence diagrams1006and1008to performing conversions outside of a core communication flow between a first communication device102-1and a second communication device102-2in accordance with sequence diagrams1002and1004during a given communication flow (e.g., during a single phone call or voice session). However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.

With reference toFIG. 11C, for certain example embodiments, an operation1122may be directed at least partially to receiving during the communication flow a command to begin receiving the data corresponding to the first communication modality from the second communication device. By way of example but not limitation, a network communication device602may receive a command716(e.g., from a first communication device102-1or a second communication device102-2) to begin receiving data corresponding to a first communication modality106-1from a second communication device102-2(e.g., instead of “directly” from a first communication device102-1). However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.

For certain example embodiments, an operation1124may be directed at least partially to transmitting from a network communication device to the first communication device a command to begin transmitting the data corresponding to the first communication modality from the first communication device to the second communication device. By way of example but not limitation, a network communication device602may transmit to a first communication device102-1a command716to begin transmitting data corresponding to first communication modality106-1to a second communication device102-2(e.g., instead of to network communication device602). For certain example implementations, such a command may cause data detouring to be ceased for conversion purposes, and farming out of data conversion may be commenced. However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.

FIG. 11Eillustrates a flow diagram1100E having example operations1126or1128. For certain example embodiments, an operation1126may be directed at least partially to wherein the receiving data corresponding to a first communication modality from at least one of a first communication device or a second communication device (e.g., of operation1102) comprises receiving a command that indicates that the data is to be converted from corresponding to the first communication modality to corresponding to the second communication modality, the command including at least one type of communication modality for the second communication modality. By way of example but not limitation, a network communication device602may receive (e.g., from a first communication device102-1, a second communication device102-2, a combination thereof, etc.) a command716that indicates that data is to be converted from corresponding to a first communication modality106-1to corresponding to a second communication modality106-2, with command716including at least one type of communication modality106for second communication modality106-2. Examples of communication modality types may include, but are not limited to, voice, text, video, some combination thereof, and so forth. However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.

For certain example embodiments, an additional operation1128may be directed at least partially to receiving additional data corresponding to the second communication modality from at least one of the second communication device or the first communication device (for an operation1128a); converting the additional data corresponding to the second communication modality to additional data corresponding to the first communication modality; (for an operation1128b) and transmitting the additional data corresponding to the first communication modality to at least one of the second communication device or the first communication device (for an operation1128c). By way of example but not limitation, a network communication device602that is responsible for converting data from corresponding to a first communication modality106-1to corresponding to a second communication modality106-2may also or alternatively be responsible for converting additional data from corresponding to second communication modality106-2to corresponding to first communication modality106-1. Additional data or converted additional data may be received from or transmitted to first communication device102-1or second communication device102-2. However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.

FIG. 11Fillustrates a flow diagram1100F having example operations1130,1132,1134, or1136. For certain example embodiments, an operation1130may be directed at least partially to wherein the converting the data corresponding to the first communication modality to data corresponding to a second communication modality (e.g., of operation1104) comprises converting the data between voice data and text data. By way of example but not limitation, a network communication device602may convert voice data to text data, or vice versa (e.g., in accordance with an action1002i,1004d,1006g,1008d, a combination thereof, etc.). However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.

For certain example embodiments, an operation1132may be directed at least partially to wherein the converting the data corresponding to the first communication modality to data corresponding to a second communication modality (e.g., of operation1104) comprises converting the data between video data and text data. By way of example but not limitation, a network communication device602may convert video data to text data, or vice versa (e.g., in accordance with an action1002i,1004d,1006g,1008d, a combination thereof, etc.). However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.

For certain example embodiments, an operation1134may be directed at least partially to wherein the converting the data between video data and text data (e.g., of operation1132) comprises converting at least one textual description of a facial expression to at least one facial expression included as at least part of an avatar image. By way of example but not limitation, a textual description (e.g., words, emoticons, combinations thereof, etc.) of a facial expression (e.g., a smile, an eyebrow raise, a wink, squinting, a grimace, a palm-plant-to-forehead, a combination thereof, etc.) may be converted so that an avatar image of a user mimics the facial expression (e.g., a mouth of an avatar smiles). However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.

For certain example embodiments, an operation1136may be directed at least partially to wherein the converting the data between video data and text data (e.g. of operation1132) comprises converting at least one facial expression from one or more frames of video to at least one textual description of a facial expression. By way of example but not limitation, a facial expression (e.g., a smile, an eyebrow raise, a wink, squinting, a grimace, a palm-plant-to-forehead, a combination thereof, etc.) detected in at least one frame of a video sequence may be converted into a textual description (e.g., words, emoticons, combinations thereof, etc.). However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.

FIG. 11Gillustrates a flow diagram1100G having example operations1138,1140,1142, or1144. For certain example embodiments, an additional operation1138may be directed at least partially to storing one or more parameters related to the communication flow, the one or more parameters including at least a communication flow identifier and an indication of the second communication modality (for an operation1138a); receiving a command to change the converting during the communication flow (for an operation1138b); and performing a different conversion on data for the communication flow responsive to the command (for an operation1138c). By way of example but not limitation, a network communication device602may store one or more parameters804related to a communication flow710, with the one or more parameters804including at least a communication flow ID808and an indication of a second communication modality106-2(e.g., text, video, voice, a combination thereof, etc.); may receive a command716to change the converting during communication flow710(e.g., to change to converting to a different communication modality106); and may perform a different conversion on data712for communication flow710responsive to received command716. However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.

For certain example embodiments, an operation1140may be directed at least partially to wherein the receiving a command to change the converting during the communication flow (e.g., of operation1138b) comprises receiving the command to change the converting during the communication flow, the command indicating that data corresponding to the first communication modality is to be converted to data corresponding to a third communication modality. By way of example but not limitation, during a given communication flow710, a network communication device602may receive a command716to change a conversion whereby data712that corresponds to a first communication modality106-1is to be converted to converted data714that corresponds to a third communication modality, with the third communication modality differing at least from second communication modality106-2. However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.

For certain example embodiments, an operation1142may be directed at least partially to wherein the performing a different conversion on data for the communication flow responsive to the command (e.g., of operation1138c) comprises converting data for the communication flow from corresponding to a third communication modality to corresponding to a fourth communication modality. By way of example but not limitation, a first communication modality106-1corresponding to data712and a second communication modality106-2corresponding to converted data714may both be changed during a communication flow710, such as to a third communication modality corresponding to data712and a fourth communication modality corresponding to converted data714. However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.

For certain example embodiments, an operation1144may be directed at least partially to wherein the performing a different conversion on data for the communication flow responsive to the command (e.g., of operation1138c) comprises converting data for the communication flow from corresponding to a third communication modality to corresponding to the second communication modality. By way of example but not limitation, a first communication modality106-1corresponding to data712may be changed during a communication flow710, such that data712corresponding to a third communication modality is then being converted to converted data714that corresponds to second communication modality106-2. However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.

FIG. 11Hillustrates a flow diagram1100H having example operations1146or1148. For certain example embodiments, an additional operation1146may be directed at least partially to storing one or more parameters related to the communication flow, the one or more parameters including at least a communication flow identifier, an identification of the first communication device, and an identification of the second communication device (for an operation1146a); receiving a command to change the converting during the communication flow (for an operation1146b); and sending a notification to the first communication device, the notification indicating that at least one aspect of the converting is changing (for an operation1146c). By way of example but not limitation, a network communication device602may store one or more parameters804related to a communication flow710, with one or more parameters804including at least a communication flow identifier808, an identification of a first communication device102-1(e.g., as part of communication flow endpoints810), and an identification of a second communication device102-2(e.g., as part of communication flow endpoints810); may receive a command716to change the converting during communication flow710(e.g., receive from at least second communication device102-2); and may send a notification to first communication device102-1, with the notification indicating that at least one aspect of the converting is changing. For certain example implementations, a notification of a conversion change may be sent: responsive to any change in a conversion procedure (e.g., communication modality, conversion service provider, communication flow routing, speed of conversion, a combination thereof, etc.), responsive to any change in a conversion process that is detectable by a user of an associated device, in accordance with parameters or settings for any participant of a communication flow, any combination thereof, and so forth. However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.

For certain example embodiments, an operation1148may be directed at least partially to wherein the receiving a command to change the converting during the communication flow (e.g., of operation1146b) comprises receiving from the second communication device the command to change the converting during the communication flow. By way of example but not limitation, a notification that is sent by a network communication device602to a first communication device102-1may be triggered by receipt at network communication device602from a second communication device102-2of a command716to change some aspect of a conversion during a communication flow. For certain example implementations, a default setting may cause a network communication device602to keep participating users up-to-date on conversion parameters. However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.

FIG. 11Iillustrates a flow diagram1100I having example operations1150,1152, or1154. For certain example embodiments, an additional operation1150may be directed at least partially to negotiating one or more aspects of a conversion of data for the communication flow with at least one of the first communication device or the second communication device. By way of example but not limitation, a network communication device602may negotiate one or more aspects (e.g., a communication modality106, a conversion service, a maximum latency, a language conversion, a routing path for data to a conversion service, obligations for notice of conversion changes, a combination thereof, etc.) of a conversion of data for a communication flow710with a first communication device102-1or a second communication device102-2. However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.

For certain example embodiments, an additional operation1152may be directed at least partially to facilitating a negotiation between the first communication device and the second communication device of one or more aspects of a conversion of data for the communication flow. By way of example but not limitation, a network communication device602may facilitate a negotiation between a first communication device102-1and a second communication device102-2(e.g., by acting as a go-between, a mediator, some combination thereof, etc.) of one or more aspects (e.g., a communication modality106, a conversion service, a maximum latency, a language conversion, a routing path for data to a conversion service, obligations for notice of conversion changes, a combination thereof, etc.) of a conversion of data for a communication flow710. However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.

For certain example embodiments, an operation1154may be directed at least partially to wherein the receiving data corresponding to a first communication modality from at least one of a first communication device or a second communication device (e.g., of operation1102) comprises receiving the data corresponding to the first communication modality from at least one of the first communication device or the second communication device via at least one telecommunications node. By way of example but not limitation, a network communication device602may receive data712corresponding to a first communication modality106-1from at least one of a first communication device102-1or a second communication device102-2via at least one telecommunications node. For certain example implementations, data712or converted data714for a communication flow710may pass through at least one telecommunications node, such as a node (e.g., a telecom switch, a base station, a gateway to a telecommunications network, some combination thereof, etc.) in a telecommunications network. However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.

FIG. 11Jillustrates a flow diagram1100J having example operations1156,1158,1160, or1162. For certain example embodiments, a method (e.g., a method in accordance with flow diagram1100A) may be performed wherein the communication flow between the first communication device and the second communication device is routed through at least one telecommunications node. By way of example but not limitation, a communication flow710(e.g., of data712, converted data714, a combination thereof, etc.) between a first communication device102-1and a second communication device102-2may be routed through at least one telecommunications node (e.g., a telecom switch or router, a base station, a base station controller, a mobile switching center, a public switched telephone network node, a gateway to a telecommunications network, some combination thereof, etc.) of a telecommunications network. However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc. For certain example embodiments, an additional operation1156may be directed at least partially to instructing the at least one telecommunications node to intercept data of the communication flow and perform a conversion of the intercepted data from corresponding to the first communication modality to corresponding to the second communication modality. By way of example but not limitation, a network communication device602may send a command716to a telecommunications node instructing it to begin intercepting data712of a communication flow710and to perform a conversion of intercepted data from corresponding to a first communication modality106-1to corresponding to a second communication modality106-2. For certain example implementations, transferring conversion responsibility from a network communication device602to a telecommunications node through which data of communication flow710is already traversing may reduce latency, costs, a combination thereof, and so forth. However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.

For certain example embodiments, a method (e.g., a method in accordance with flow diagram1100A) may be performed wherein the receiving data, the converting the data, and the transmitting the data are performed at least partially by one or more internet servers. By way of example but not limitation, a network communication device602that comprises one or more internet servers may perform the receiving of data, the converting of the data to produce converted data, and the transmitting of the converted data. However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.

For certain example embodiments, an additional operation1158may be directed at least partially to storing a stream of converted data based, at least in part, on the converting (for an operation1158a) and mining the stored stream of converted data (for an operation1158b). By way of example but not limitation, a network communication device602may store results of multiple conversions of data and may mine the stored conversion results. For certain example implementations, stored conversion results may be mined for search purposes, for targeted advertising purposes, for social networking purposes, any combination thereof, and so forth. However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.

For certain example embodiments, an additional operation1160may be directed at least partially to establishing an account with at least one user associated with at least one of the first communication device or the second communication device (for an operation1160a) and storing one or more settings for the at least one user based, at least in part, on the established account (for an operation1160b). By way of example but not limitation, a network communication device602may establish an account (e.g., at least partially for conversion services) with a first user104-1associated with a first communication device102-1or with a second user104-2associated with a second communication device102-2. An account may be free, may cost a fee, may involve some other form of consideration, any combination thereof, and so forth. A network communication device602may store one or more settings802for at least one user104-1or104-2based at least partly on the established account. For certain example implementations, account settings may include, but are not limited to, conversion preferences, communication modality preferences, data routing preferences (e.g., detoured data vs. exchanging data with a converting network node), notification preferences, any combination thereof, and so forth. However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.

For certain example embodiments, an operation1162may be directed at least partially to wherein the converting the data corresponding to the first communication modality to data corresponding to a second communication modality (e.g., of operation1104) comprises converting the data corresponding to the first communication modality to the data corresponding to the second communication modality based at least partly on the stored settings for the at least one user that is associated with at least one of the first communication device or the second communication device. By way of example but not limitation, a network communication device602may convert data712corresponding to a first communication modality106-1to converted data714corresponding to a second communication modality106-2based at least partly on stored settings802for a user104-1or a user104-2that is associated with a first communication device102-1or a second communication device102-2, respectively. However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.

FIG. 12Ais a flow diagram1200A illustrating an example method for a network communication device (e.g., a network communication flow device) that may perform a conversion for a communication flow between first and second communication devices in accordance with certain example embodiments. As illustrated, flow diagram1200A may include any of operations1202-1208. Although operations1202-1208are shown or described in a particular order, it should be understood that methods may be performed in alternative manners without departing from claimed subject matter, including, but not limited to, with a different order or number of operations or with a different relationship between or among operations. Also, at least some operations of flow diagram1200A may be performed so as to be fully or partially overlapping with other operation(s).

For certain example embodiments, a method for interceptive conversion with multi-modality communications may be at least partially implemented using hardware and may comprise an operation1202, an operation1204, an operation1206, or an operation1208. An operation1202may be directed at least partially to receiving from a first communication device data corresponding to a first communication modality, with the data corresponding to the first communication modality associated with a communication flow between the first communication device and a second communication device, the communication flow comprising a multi-modality communication in which a first user is to interact with the first communication device using a first communication modality and a second user is to interact with the second communication device using a second communication modality. By way of example but not limitation, a receiver706may receive from a first communication device102-1data712corresponding to a first communication modality106-1(e.g., in accordance with an action1010h,1012d, a combination thereof, etc.). Data712may correspond to first communication modality106-1and may be associated with a communication flow710between first communication device102-1and a second communication device102-2. Communication flow710may comprise a multi-modality communication in which a first user104-1is to interact with first communication device102-1using a first communication modality106-1and a second user104-2is to interact with second communication device102-2using a second communication modality106-2. However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.

For certain example embodiments, an operation1204may be directed at least partially to converting the data corresponding to the first communication modality to data corresponding to the second communication modality. By way of example but not limitation, a converter702may convert data712corresponding to first communication modality106-1to converted data714corresponding to second communication modality106-2(e.g., in accordance with an action1010j,1012e, a combination thereof, etc.). An operation1206may be directed at least partially to transmitting to the second communication device the data corresponding to the second communication modality. By way of example but not limitation, a transmitter708may transmit to second communication device102-2(converted) data714corresponding to second communication modality106-2(e.g., in accordance with an action1012a,1012g, a combination thereof, etc.). An operation1208may be directed at least partially to transmitting to the first communication device a notification of at least one aspect of a conversion applicable to the communication flow. By way of example but not limitation, a transmitter708or a notifier718may transmit to first communication device102-1a notification720of at least one aspect (e.g., initial setting(s), initial parameter(s), changed parameter(s), change request(s), a combination thereof, etc.) of a conversion applicable to communication flow710. For certain example implementations, a method for interceptive conversion with multi-modality communications may be performed wherein the first communication device initiates the communication flow. By way of example but not limitation, a communication flow710may have been initiated by a first communication device102-1(e.g., a first communication device102-1may have transmitted an initial voice communication notice). However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.

FIGS. 12B-12Gdepict example alternatives for a flow diagram ofFIG. 12Ain accordance with certain example embodiments. As illustrated, flow diagrams ofFIGS. 12B-12Gmay include any of the illustrated or described operations. Although operations are shown or described in a particular order, it should be understood that methods may be performed in alternative manners without departing from claimed subject matter, including, but not limited to, with a different order or number of operations or with a different relationship between or among operations. Also, at least some operations of flow diagrams ofFIGS. 12B-12Gmay be performed so as to be fully or partially overlapping with other operation(s).

FIG. 12Billustrates a flow diagram1200B having example operations1212,1214, or1216. For certain example embodiments, an operation1212may be directed at least partially to wherein the transmitting to the first communication device a notification of at least one aspect of a conversion applicable to the communication flow (e.g., of operation1208) comprises transmitting to the first communication device the notification of the at least one aspect of the conversion applicable to the communication flow in response to a change to the conversion applicable to the communication flow. By way of example but not limitation, a transmitter708or a notifier718may transmit to a first communication device102-1a notification720in response to a change to a conversion (e.g., in response to a change to at least one parameter for a conversion) that is applicable to a communication flow710(e.g., in accordance with an action1016e). However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.

At an operation1210(for any ofFIGS. 12B-12G), one or more additional operations may be performed. For certain example embodiments, an operation1214may be directed at least partially to receiving from the second communication device a request for the change to the conversion applicable to the communication flow. By way of example but not limitation, a receiver706may receive from a second communication device102-2a request for a change to a conversion that is applicable to a communication flow710(e.g., in accordance with an action1016c). However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.

For certain example embodiments, an operation1216may be directed at least partially to receiving from the first communication device a request for a change to the conversion applicable to the communication flow (for an operation1216a) and transmitting to the second communication device a notification of the requested change to the conversion applicable to the communication flow (for an operation1216b). By way of example but not limitation, a receiver706may receive from a first communication device102-1a request for a change to a conversion that is applicable to a communication flow710, or a transmitter708or a notifier718may transmit to a second communication device102-2a notification720in response to a requested change to a conversion (e.g., in response to a change to at least one parameter for a conversion) that is applicable to a communication flow710. However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.

FIG. 12Cillustrates a flow diagram1200C having example operations1218,1220, or1222. For certain example embodiments, an operation1218may be directed at least partially to wherein the transmitting to the first communication device a notification of at least one aspect of a conversion applicable to the communication flow (e.g., of operation1208) comprises transmitting to the first communication device the notification, the notification comprising an initial notification that a user of the second communication device intends to participate via the conversion applicable to the communication flow. By way of example but not limitation, a transmitter708or a notifier718may transmit to a first communication device102-1an initial notification720that a second communication device102-2or a second user104-2intends to participate in communication flow710via a conversion that is applicable to communication flow710(e.g., in accordance with an action1010e,1016b, a combination thereof, etc.). However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.

For certain example embodiments, an operation1220may be directed at least partially to wherein the transmitting to the first communication device a notification of at least one aspect of a conversion applicable to the communication flow (e.g., of operation1208) further comprises providing to the first communication device an opportunity to request a change to the at least one aspect of the conversion applicable to the communication flow. By way of example but not limitation, a network communication device602may provide to a first communication device102-1an opportunity to request a change to at least one aspect of a conversion that is applicable to a communication flow710. For certain example implementations, an opportunity may be provided by sending an explicit message invitation to change one or more aspects, by accepting or receiving a request to make a change, by acknowledging a request to make a change, by processing a change request, any combination thereof, and so forth. However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.

For certain example embodiments, an operation1222may be directed at least partially to receiving from the first communication device a request to permit the first communication device to perform the conversion applicable to the communication flow. By way of example but not limitation, a receiver706may receive from a first communication device102-1a request to permit first communication device102-1to perform a conversion applicable to communication flow710(e.g., instead of a conversion being performed by a network communication device602). However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.

FIG. 12Dillustrates a flow diagram1200D having example operations1224or1226. For certain example embodiments, an operation1224may be directed at least partially to receiving from the first communication device an initial communication notification for a communication with the second communication device, the communication to include data that corresponds to the first communication modality (for an operation1224a) and receiving from the first communication device a request to send data that corresponds to a communication modality that differs from the first communication modality (for an operation1224b). By way of example but not limitation, a receiver706may receive from a first communication device102-1an initial communication notification720for a communication with a second communication device102-2, with the communication to include data712that corresponds to a first communication modality106-1(e.g., in accordance with an action1010a,1014e, a combination thereof, etc.). A receiver706may further receive from first communication device102-1a request to send data712that corresponds to a communication modality that differs from first communication modality106-1. For certain example implementations, a communication device102that initiates a call with one type of communication modality may subsequently change to a different type of communication modality. However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.

For certain example embodiments, an operation1226may be directed at least partially to transmitting to the first communication device the data corresponding to the second communication modality for verification by a first user associated with the first communication device. By way of example but not limitation, a transmitter708may transmit to a first communication device102-1(converted) data714corresponding to a second communication modality106-2for verification by a first user104-1associated with first communication device102-1. For certain example implementations, a network communication device602may provide an originating user an opportunity to verify or confirm that a conversion has been performed to at least an acceptable level (e.g., to approve a conversion proposal) prior to transmitting the conversion to a destination user. However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.

FIG. 12Eillustrates a flow diagram1200E having example operations1228or1230. For certain example embodiments, an operation1228may be directed at least partially to receiving from the second communication device additional data corresponding to the second communication modality (for an operation1228a); converting the additional data corresponding to the second communication modality to additional data corresponding to the first communication modality (for an operation1228b); and transmitting to the second communication device the additional data corresponding to the first communication modality as a conversion proposal for verification by a second user associated with the second communication device (for an operation1228c). By way of example but not limitation, a network communication device602may receive from a second communication device102-2additional data712corresponding to a second communication modality106-2, may convert additional data712corresponding to second communication modality106-2to additional (converted) data714corresponding to a first communication modality106-1, and transmit to second communication device102-2additional (converted) data714corresponding to first communication modality106-1as a conversion proposal for verification (e.g., for approval, disapproval, editing, a combination thereof, etc) by a second user104-2associated with second communication device102-2. However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.

For certain example embodiments, an operation1230may be directed at least partially to receiving from the second communication device a message indicative of a verification response for the conversion proposal (for an operation1230a) and determining whether to transmit to the first communication device the additional data corresponding to the first communication modality based, at least in part, on the verification response for the conversion proposal (for an operation1230b). By way of example but not limitation, a network communication device602may receive from a second communication device102-2a message indicative of a verification response (e.g., an approval, a disapproval, an edited version, a combination thereof, etc.) for a conversion proposal. A network communication device602may also determine whether to transmit to a first communication device102-1additional (converted) data714corresponding to first communication modality106-1based, at least in part, on the verification response for the conversion proposal. For certain example implementations, a verification response comprising an approval may prompt a network communication device602to send converted data to first communication device102-1, but a verification response comprising a disapproval may prompt a network communication device602to perform another conversion or to request that a second user104-2associated with a second communication device102-2input communication data again. For certain example implementations, a verification response comprising an edited version of converted data may prompt a network communication device602to send an edited version of converted data to first communication device102-1. However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.

For certain example embodiments, a method may be directed at least partially to wherein the receiving, the converting, the transmitting to the second communication device, and the transmitting to the first communication device are performed by a network communication flow device through which data for the communication flow is to propagate regardless of whether the data for the communication flow is subject to conversion from one communication modality to another communication modality. By way of example but not limitation, a network communication flow device602* through which data for a communication flow710is to propagate regardless of whether data712for communication flow710is subject to conversion from one communication modality to another communication modality may perform the receiving, the converting, the transmitting to the second communication device, and the transmitting to the first communication device. However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.

For certain example embodiments, a method may be directed at least partially to wherein the receiving, the converting, the transmitting to the second communication device, and the transmitting to the first communication device are performed by at least one telecommunications node. By way of example but not limitation, the receiving, the converting, the transmitting to the second communication device, and the transmitting to the first communication device may be performed by a telecommunications node (e.g., a telecom switch or router, a base station, a base station controller, a mobile switching center, a public switched telephone network node, a gateway to a telecommunications network, some combination thereof, etc.). However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.

FIG. 12Fillustrates a flow diagram1200F having example operations1232,1234, or1236. For certain example embodiments, an operation1232may be directed at least partially to receiving from the second communication device at least one indication of one or more conversion settings for multi-modality communications. By way of example but not limitation, a receiver706may receive from second communication device102-2at least one indication of one or more conversion settings (e.g., one or more settings802(e.g., ofFIG. 8)) for multi-modality communications. For certain example implementations, indications of conversations settings may be received by a network communication device602, for example, roughly contemporaneously with a beginning of a communication (e.g., during call notification or setup), prior to initiation of a communication, any combination thereof, and so forth. However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.

For certain example embodiments, an operation1234may be directed at least partially to wherein the receiving from the second communication device at least one indication of one or more conversion settings for multi-modality communications (e.g., of operation1232) comprises receiving from the second communication device the at least one indication of the one or more conversion settings, the one or more conversion settings including a setting to auto-accept incoming communication notifications for communications corresponding to the first communication modality as a multi-modality communication in which a user of the second communication device is to interact with the second communication device using a second communication modality. By way of example but not limitation, a network communication device602may receive from a second communication device102-2a setting to auto-accept incoming communication notifications (e.g., auto-answer incoming voice calls) for communications corresponding to a first communication modality106-1as a multi-modality communication in which a second user104-2of second communication device102-2is to interact with second communication device102-2using a second communication modality106-2(e.g., in accordance with an action1014b, etc.). However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.

For certain example embodiments, an operation1236may be directed at least partially to wherein the receiving from the second communication device at least one indication of one or more conversion settings for multi-modality communications (e.g., of operation1232) comprises receiving from the second communication device the at least one indication of the one or more conversion settings, the one or more conversion settings including a setting specifying a level of text delivery or a language understood by a user of the second communication device. By way of example but not limitation, a network communication device602may receive from a second communication device102-2one or more conversion settings (e.g., one or more settings802(e.g., ofFIG. 8)) including a setting specifying a level of text delivery (e.g., a text delivery level indicator822(e.g., ofFIG. 8)) or a language (e.g., a language indicator820(e.g., ofFIG. 8)) understood by a second user104-2associated with second communication device102-2. However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.

FIG. 12Gillustrates a flow diagram1200G having example operations1238,1240,1242, or1244. For certain example embodiments, an operation1238may be directed at least partially to wherein the transmitting to the first communication device a notification of at least one aspect of a conversion applicable to the communication flow (e.g., of operation1208) comprises transmitting to the first communication device the notification of the at least one aspect of the conversion applicable to the communication flow, the notification comprising an indication that the second user is currently entering user input corresponding to the second communication modality. By way of example but not limitation, a network communication device602may transmit to a first communication device102-1a notification720that is prompted by an entry progress indicator826and that indicates that a second user104-2is currently entering user input corresponding to a second communication modality106-2(e.g., is currently entering text, is currently speaking, a combination thereof, etc.). However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.

For certain example embodiments, an operation1240may be directed at least partially to wherein the transmitting to the first communication device a notification of at least one aspect of a conversion applicable to the communication flow (e.g., of operation1208) comprises transmitting to the first communication device the notification of the at least one aspect of the conversion applicable to the communication flow, the notification comprising a reminder that another communication participant is currently in a text interaction modality. By way of example but not limitation, a network communication device602may transmit to a first communication device102-1a notification720that is prompted by a modality reminder indicator828and that indicates that another communication participant (e.g., a second user104-2) is currently in a text interaction modality. However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.

For certain example embodiments, an operation1242may be directed at least partially to wherein the transmitting to the first communication device a notification of at least one aspect of a conversion applicable to the communication flow (e.g., of operation1208) comprises transmitting to the first communication device the notification of the at least one aspect of the conversion applicable to the communication flow, the notification comprising a reminder that another communication participant is currently in a voice interaction modality. By way of example but not limitation, a network communication device602may transmit to a first communication device102-1a notification720that is prompted by a modality reminder indicator828and that indicates that another communication participant (e.g., a second user104-2) is currently in a voice interaction modality. However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.

For certain example embodiments, an operation1244may be directed at least partially to wherein the transmitting to the first communication device a notification of at least one aspect of a conversion applicable to the communication flow (e.g., of operation1208) comprises transmitting to the first communication device the notification of the at least one aspect of the conversion applicable to the communication flow while the communication flow is extant, the notification comprising an indication that a user of the second communication device is switching away from the second communication modality to a different communication modality for interacting with the second communication device. By way of example but not limitation, a network communication device602may transmit to a first communication device102-1a notification720of at least one aspect of a conversion applicable to a communication flow710while communication flow710is extant, with notification720comprising an indication that a second user104-2of a second communication device102-2is switching away from a second communication modality106-2to a different communication modality for interacting with second communication device102-2. By way of example but not limitation, a notification720may be prompted by a change notification indicator816(e.g., that applies to communication participants in addition to or instead of an associated user), by a change notification indicator that comprises a parameter804(which is not explicitly shown inFIG. 8) and applies at least to other participants, some combination thereof, and so forth. However, claimed subject matter is not limited to any particular described embodiments, implementations, examples, etc.

It should be appreciated that the particular embodiments (e.g., processes, apparatuses, systems, media, arrangements, etc.) described herein are merely possible implementations of the present disclosure, and that the present disclosure is not limited to the particular implementations described herein or shown in the accompanying figures.

In addition, in alternative implementations, certain acts, operations, etc. need not be performed in the order described, and they may be modified and/or may be omitted entirely, depending on the circumstances. Moreover, in various implementations, the acts or operations described may be implemented by a computer, controller, processor, programmable device, or any other suitable device, and may be based on instructions stored on one or more computer-readable or processor-accessible media or otherwise stored or programmed into such devices. If computer-readable media are used, the computer-readable media may be, by way of example but not limitation, any available media that can be accessed by a device to implement the instructions stored thereon.

Various methods, systems, techniques, etc. have been described herein in the general context of processor-executable instructions, such as program modules, executed by one or more processors or other devices. Generally, program modules may include routines, programs, objects, components, data structures, combinations thereof, etc. that perform particular tasks or implement particular abstract data types. Typically, functionality of program modules may be combined or distributed as desired in various alternative embodiments. In addition, embodiments of methods, systems, techniques, etc. may be stored on or transmitted across some form of device-accessible media.

It may also be appreciated that there may be little distinction between hardware implementations and software implementations for aspects of systems, methods, etc. that are disclosed herein. Use of hardware or software may generally be a design choice representing cost vs. efficiency tradeoffs, for example. However, in certain contexts, a choice between hardware and software (e.g., for an entirety or a given portion of an implementation) may become significant. Those having skill in the art will appreciate that there are various vehicles by which processes, systems, technologies, etc. described herein may be effected (e.g., hardware, software, firmware, combinations thereof, etc.), and that a preferred vehicle may vary depending upon a context in which the processes, systems, technologies, etc. are deployed. For example, if an implementer determines that speed and accuracy are paramount, an implementer may opt for a mainly hardware and/or firmware vehicle. Alternatively, if flexibility is deemed paramount, an implementer may opt for a mainly software implementation. In still other implementations, an implementer may opt for some combination of hardware, software, and/or firmware. Hence, there are multiple possible vehicles by which processes and/or devices and/or other technologies described herein may be effected. Which vehicle may be desired over another may be a choice dependent upon a context in which a vehicle is to be deployed or specific concerns (e.g., speed, flexibility, predictability, etc.) of an implementer, any of which may vary. Those skilled in the art will recognize that optical aspects of example implementations may employ optically-oriented hardware, software, and/or firmware.

Those skilled in the art will recognize that it is common within the art to describe devices and/or processes in fashion(s) as set forth herein, and thereafter use standard engineering practices to realize such described devices and/or processes into workable systems having described functionality. That is, at least a portion of the devices and/or processes described herein may be realized via a reasonable amount of experimentation.

Aspects and drawings described herein illustrate different components contained within, or connected with, other different components. It is to be understood that such depicted architectures are presented merely by way of example, and that many other architectures may be implemented to achieve identical or similar functionality. In a conceptual sense, any arrangement of components to achieve described functionality may be considered effectively “associated” such that desired functionality is achieved. Hence, any two or more components herein combined to achieve a particular functionality may be seen as “associated with” each other such that desired functionality is achieved, irrespective of architectures or intermedial components. Likewise, any two or more components so associated can also be viewed as being “operably connected” or “operably coupled” (or “operatively connected,” or “operatively coupled”) to each other to achieve desired functionality, and any two components capable of being so associated can also be viewed as being “operably couplable” (or “operatively couplable”) to each other to achieve desired functionality. Specific examples of operably couplable include, but are not limited to, physically mateable and/or physically interacting components and/or wirelessly interactable and/or wirelessly interacting components and/or logically interacting and/or logically interactable components.

Those skilled in the art will recognize that at least some aspects of embodiments disclosed herein may be implemented at least partially via integrated circuits (ICs), as one or more computer programs running on one or more computing devices, as one or more software programs running on one or more processors, as firmware, as any combination thereof, and so forth. It will be further understood that designing circuitry and/or writing code for software and/or firmware may be accomplished by a person skilled in the art in light of the teachings and explanations of this disclosure.

The foregoing detailed description has set forth various example embodiments of devices and/or processes via the use of block diagrams, flowcharts, examples, combinations thereof, etc. Insofar as such block diagrams, flowcharts, examples, combinations thereof, etc. may contain or represent one or more functions and/or operations, it will be understood by those within the art that each function and/or operation within such block diagrams, flowcharts, examples, combination thereof, etc. may be implemented, individually and/or collectively, by a wide range of hardware, software, firmware, any combination thereof, and so forth. For example, in some embodiments, one or more portions of subject matter described herein may be implemented via Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs), digital signal processors (DSPs), or other integrated formats. However, those skilled in the art will recognize that some aspects of example embodiments disclosed herein, in whole or in part, may be equivalently implemented in integrated circuits, as one or more computer programs running on one or more computers (e.g., as one or more programs running on one or more computer systems), as one or more programs running on one or more processors (e.g., as one or more programs running on one or more microprocessors), as firmware, as virtually any combination thereof, etc. and that designing circuitry and/or writing code for software and/or firmware is within the skill of one of skill in the art in light of the teachings of this disclosure.

Although particular aspects of the present subject matter described herein have been shown and described, it will be apparent to those skilled in the art that, based upon the teachings herein, changes and modifications may be made without departing from the subject matter described herein and its broader aspects and, therefore, the appended claims are to encompass within their scope all such changes and modifications as are within the true spirit and scope of this subject matter described herein. Furthermore, it is to be understood that inventive subject matter is defined by the appended claims.

As a further example of “open” terms in the present specification including the claims, it will be understood that usage of a language construction of “A or B” is generally interpreted, unless context dictates otherwise, as a non-exclusive “open term” meaning: A alone, B alone, and/or A and B together. Furthermore, in those instances where a convention analogous to “at least one of A, B, and C, etc.” is used, in general such a construction is intended in the sense one having skill in the art would understand the convention (e.g., “a system having at least one of A, B, and C” would include but not be limited to systems that have A alone, B alone, C alone, A and B together, A and C together, B and C together, and/or A, B, and C together, etc.). In those instances where a convention analogous to “at least one of A, B, or C, etc.” used, in general such a construction is intended in the sense one having skill in the art would understand the convention (e.g., “a system having at least one of A, B, or C” would include but not be limited to systems that have A alone, B alone, C alone, A and B together, A and C together, B and C together, and/or A, B, and C together, etc.).