SYSTEM AND METHOD FOR IDENTIFYING COLLABORATORS ON A SHARED MOBILE DEVICE

A method, computer program product, and system is provided for identifying collaborators on a shared mobile device. In an implementation, a method may include receiving, by a shared mobile device, an identifier input including one or more biometric identifiers associated with a user. The method may also include receiving, by the shared mobile device, a collaborative content input from the user, the collaborative content input being associated with at least a portion of collaborative content. The method may further include comparing the one or more biometric identifiers associated with the user with biometric identifiers of a plurality of users of the shared mobile device. The method may further include, when the identifier input including the one or more biometric identifiers associated with the user matches a biometric identifier of an identified user of the plurality of users of the shared mobile device, associating the identified user with the collaborative content input.

TECHNICAL FIELD

The present disclosure generally relates to identifying users of a mobile device, and more particularly relates to systems and methods for identifying collaborators on a shared mobile device.

BACKGROUND

Many individuals often carry a mobile device. Mobile devices may often be used by individuals to engage in, or at least allow for the possibility, of communicating with others, even when an individual is not at a fixed location, such as a home or office. Examples of mobile devices may include, but are not limited to, cellular telephones, smartphones, tablet computing devices, notebook or laptop computers, or the like. Such mobile devices may allow individuals to engage in and/or receive a variety of communications from others. Mobile devices may also be used to access content, such as documents, presentations, drawings, and the like. Mobile devices may also be shared between a group of individuals and to access the content. For example, a group of individuals may use a shared mobile device to collaborate on the content.

SUMMARY OF DISCLOSURE

According to an implementation, a method may include receiving, by a shared mobile device, an identifier input including one or more biometric identifiers associated with a user. The method may also include receiving, by the shared mobile device, a collaborative content input from the user, the collaborative content input being associated with at least a portion of collaborative content. The method may further include comparing the one or more biometric identifiers associated with the user with biometric identifiers of a plurality of users of the shared mobile device. The method may further include, when the identifier input including the one or more biometric identifiers associated with the user matches a biometric identifier of an identified user of the plurality of users of the shared mobile device, associating the identified user with the collaborative content input.

One or more of the following features may be included. The received one or more biometric identifiers may include at least one of facial recognition, fingerprint recognition, iris and/or retina recognition, and voice recognition

The method may also include, when the identifier input including the one or more biometric identifiers associated with the user does not match a biometric identifier of one of the plurality of users of the shared mobile device, prompting the user for identification details.

The method may also include setting the identified user as a current user of the shared mobile device.

The method may further include editing the portion of the collaborative content based upon, at least in part, the received collaborative content input.

The method may include providing an indicator of the associated identified user and the collaborative content input within the collaborative content. The collaborative content may include one or more collaborative content inputs from at least a portion of the plurality of users of the shared mobile device.

According to another implementation, a computer program product may include a non-transitory computer readable medium having a plurality of instructions stored on it. When executed by a processor, the instructions may cause the processor to perform operations including receiving, by a shared mobile device, an identifier input including one or more biometric identifiers associated with a user. Instructions may also be included for receiving a collaborative content input from the user, the collaborative content input being associated with at least a portion of collaborative content. Instructions may also be included for comparing the one or more biometric identifiers associated with the user with biometric identifiers of a plurality of users of the shared mobile device. Instructions may also be included for, when the identifier input including the one or more biometric identifiers associated with the user matches a biometric identifier of an identified user of the plurality of users of the shared mobile device, associating the identified user with the collaborative content input.

One or more of the following features may be included. The received one or more biometric identifiers may include at least one of facial recognition, fingerprint recognition, iris and/or retina recognition, and voice recognition.

Instructions may be included for, when the identifier input including the one or more biometric identifiers associated with the user does not match a biometric identifier of one of the plurality of users of the shared mobile device, prompting the user for identification details.

Instructions may also be included for setting the identified user as a current user of the shared mobile device.

Instructions may also be included for editing the portion of the collaborative content based upon, at least in part, the received collaborative content input.

Instructions may also be included for providing an indicator of the associated identified user and the collaborative content input within the collaborative content. The collaborative content may include one or more collaborative content inputs from at least a portion of the plurality of users of the shared mobile device.

According to yet another implementation, a system may include at least one processor device and at least one memory architecture coupled with the at least one processor device. The at least one processor device may be configured for receiving, by a shared mobile device, an identifier input including one or more biometric identifiers associated with a user. The at least one processor may also be configured for receiving a collaborative content input from the user, the collaborative content input being associated with at least a portion of collaborative content. The at least one processor may further be configured for comparing the one or more biometric identifiers associated with the user with biometric identifiers of a plurality of users of the shared mobile device. The at least one processor may further be configured for, when the identifier input including the one or more biometric identifiers associated with the user matches a biometric identifier of an identified user of the plurality of users of the shared mobile device, associating the identified user with the collaborative content input.

One or more of the following features may be included. The received one or more biometric identifiers may include at least one of facial recognition, fingerprint recognition, iris and/or retina recognition, and voice recognition.

The at least one processor may be further configured for, when the identifier input including the one or more biometric identifiers associated with the user does not match a biometric identifier of one of the plurality of users of the shared mobile device, prompting the user for identification details.

The at least one processor may be further configured for setting the identified user as a current user of the shared mobile device.

The at least one processor may be further configured for editing the portion of the collaborative content based upon, at least in part, the received collaborative content input.

The at least one processor may be further configured for providing an indicator of the associated identified user and the collaborative content input within the collaborative content.

DETAILED DESCRIPTION

Many individuals often carry a mobile device. Mobile devices may often be used by individuals to engage in, or at least allow for the possibility, of communicating with others, even when an individual is not at a fixed location, such as a home or office. Examples of mobile devices may include, but are not limited to, cellular telephones, smartphones, tablet computing devices, notebook or laptop computers, or the like. In some situations, mobile devices may also be shared between a group of individuals and to create and/or access content, such as documents, presentations, drawings, and the like. For example, a group of individuals may use a shared mobile device to collaborate on the content, or otherwise engage in a collaborative activity that may include or relate to the content.

According to some embodiments, the present disclosure may allow for identification of users associated with at least one shared mobile device. For example, a shared mobile device may be passed to different users. The present disclosure may allow for identification of each user based upon, at least in part, unique characteristics of each user. For example, unique characteristics of the user may include, but are not limited to, biometric identifiers such as facial recognition, voice recognition, iris and/or retina recognition, fingerprint recognition, and the like. For example, a user may be identified as a result of normal use of the shared mobile device, such as simply by holding the shared mobile device in front of the user's face while reviewing the collaborative content, which may allow the shared mobile device to capture a photo of the user's face. In this manner, an identifying characteristic of the user may be captured, for example, in a generally passive way without having to manually enter identification details, such as a username or password. Other biometric identifiers may be captured in similar manners, e.g., as by recording the users' voice, capturing a fingerprint by an appropriate detector, etc. The user may be identified, for example, by comparing the captured biometric identifier to known (e.g., previously captured) biometric identifiers of one or more individuals. In an embodiment, the identified user may provide a collaborative content input associated with at least a portion of the collaborative content. The collaborative content input may be associated with the identified user, such that a history of collaborative content inputs, including comments, edits, contributions, and the like, may be automatically stored and accessed as needed. Further, in some embodiments, by associating the collaborative content input with the identified user, the source of the collaborative content input may be known.

Referring toFIG. 1, there is shown identification process10. For the following discussion, it is intended to be understood that identification process10may be implemented in a variety of ways. For example, identification process10may be implemented as a server-side process, a client-side process, or a server-side/client-side process.

For example, identification process10may be implemented as a purely server-side process via identification process10s. Alternatively, identification process10may be implemented as a purely client-side process via one or more of client-side application10c1, client-side application10c2, client-side application10c3, and client-side application10c4. Alternatively still, identification process10may be implemented as a server-side/client-side process via identification process10sin combination with one or more of client-side application10c1, client-side application10c2, client-side application10c3, and client-side application10c4. In such an example, at least a portion of the functionality of identification process10may be performed by identification process10sand at least a portion of the functionality of identification process10may be performed by one or more of client-side application10c1,10c2,10c3, and10c4.

Accordingly, identification process10as used in this disclosure may include any combination of identification process10s, client-side application10c1, client-side application10c2, client-side application10c3, and client-side application10c4.

Referring also toFIG. 2, and as will be discussed in greater detail below, in an embodiment, identification process10may receive100, by a shared mobile device, an identifier input including one or more biometric identifiers associated with a user. Identification process10may also receive102, by the shared mobile device, a collaborative content input from the user, the collaborative content input being associated with at least a portion of collaborative content. Identification process10may further compare104the one or more biometric identifiers associated with the user with biometric identifiers of a plurality of users of the shared mobile device. Identification process10may further, when the identifier input including the one or more biometric identifiers associated with the user matches a biometric identifier of an identified user of the plurality of users of the shared mobile device, associate106the identified user with the collaborative content input.

Identification process10smay be a server application and may reside on and may be executed by computing device12, which may be connected to network14(e.g., the Internet or a local area network). Examples of computing device12may include, but are not limited to: a personal computer, a server computer, a series of server computers, a mini computer, a mainframe computer, or a dedicated network device.

The instruction sets and subroutines of identification process10s, which may be stored on storage device16coupled to computing device12, may be executed by one or more processors (not shown) and one or more memory architectures (not shown) included within computing device12. Examples of storage device16may include but are not limited to: a hard disk drive; a tape drive; an optical drive; a RAID device; an NAS device, a Storage Area Network, a random access memory (RAM); a read-only memory (ROM); and all forms of flash memory storage devices.

Examples of client-side applications10c1,10c2,10c3,10c4may include an application or process for implementing features and/or operations of identification process10. For example, client-side applications10c1,10c2,10c3,10c4may include and/or interact with an operating system of a mobile device. Additionally, in some embodiments client-side applications10c1,10c2,10c3,10c4may include, but are not limited to, client-side collaboration applications. Examples of such client-side collaboration applications may include, but are not limited to, a word processing application, a presentation application, an electronic spreadsheet application, a drawing application, a web browser (e.g., which may interact and/or communicate with other resources and/or applications) and/or any specialized application that may include collaborative content that may be created and/or modified by a plurality of users (e.g., an application running on a mobile platform). Additionally/alternatively, identification process10may interact and/or communicate with one or more collaboration applications. The instruction sets and subroutines of client-side application10c1,10c2,10c3,10c4, which may be stored on storage devices20,22,24,26(respectively) coupled to client electronic devices28,30,32,34(respectively), may be executed by one or more processors (not shown) and one or more memory architectures (not shown) incorporated into client electronic devices28,30,32,34(respectively). Examples of storage devices20,22,24,26may include but are not limited to: hard disk drives; tape drives; optical drives; RAID devices; random access memories (RAM); read-only memories (ROM), and all forms of flash memory storage devices.

Examples of client electronic devices28,30,32,34may include, but are not limited to, personal computer28, laptop computer30, mobile computing device32, tablet computing device34, a netbook computer (not shown), a server computer (not shown), a gaming console (not shown), a data-enabled television console (not shown), and a dedicated network device (not shown). Client electronic devices28,30,32,34may each execute an operating system.

Users36,38,40,42may access identification process10directly on respective client electronic devices28,30,32,34, and/or through network14or through secondary network18. Further, identification process10may be accessed through secondary network18via link line44.

The various client electronic devices (e.g., client electronic devices28,30,32,34) may be directly or indirectly coupled to network14(or network18). For example, personal computer28is shown directly coupled to network14. Further, laptop computer30is shown wirelessly coupled to network14via wireless communication channel46established between laptop computer30and wireless access point (WAP)50. Similarly, mobile computing device32is shown wirelessly coupled to network14via wireless communication channel48established between mobile computing device32and cellular network/bridge54, which is shown directly coupled to network14and network18. WAP50may be, for example, an IEEE 802.11a, 802.11b, 802.11g, 802.11n, Wi-Fi, Bluetooth, and/or ANT device that is capable of establishing wireless communication channel46between laptop computer30and WAP50. Additionally, tablet computing device34is shown wirelessly coupled to network14via wireless communication channel52established between tablet computing device34and cellular network/bridge54, which is shown directly coupled to network14and network18.

In some embodiments, identification process10may communicate with, interact with, and/or include a component or module of a collaboration application (e.g., collaboration application56). As is generally known, a collaboration application (e.g., collaboration application56) may generally facilitate collaboration between multiple parties. For example, collaboration application56may facilitate collaboration of content between a plurality of users. In some embodiments, collaboration application may include, and/or may interact with, for example, a word processing application, a presentation application, an electronic spreadsheet application, a drawing application, a social networking application, and/or any specialized application that may include collaborative content that may be created and/or modified by a plurality of users (e.g., an application running on a mobile platform).

In an embodiment, the instruction sets and subroutines of collaboration application56may be stored, e.g., on storage device16associated with server computer12, which executes collaboration application56, and/or another suitable storage device. Further, users (e.g., one or more of users36,38,40,42) may access collaboration application56in order to participate in a collaboration session. The users may access collaboration application56via one or more suitable applications, such as client side applications10c1-10c4(e.g., which may include a word processing application, a presentation application, an electronic spreadsheet application, a drawing application, and/or any specialized application that may include collaborative content that may be created and/or modified by a plurality of users) and/or via a different application (not shown). As generally discussed above, a portion and/or all of the functionality of identification process10may be provided by one or more of client side applications10c1-10c4. For example, in some embodiments identification process10(and/or client-side functionality of identification process10) may be included within and/or interactive with client-side applications10c1-10c4, which may include client side collaboration applications, web browsers, or another application. Various additional/alternative configurations may be equally utilized.

As generally discussed above with reference toFIG. 2, in an embodiment identification process10may receive100, by a shared mobile device, an identifier input including one or more biometric identifiers associated with a user. Identification process10may also receive102, by the shared mobile device, a collaborative content input from the user, the collaborative content input being associated with at least a portion of collaborative content. Identification process10may further compare104the one or more biometric identifiers associated with the user with biometric identifiers of a plurality of users of the shared mobile device. Identification process10may further, when the identifier input including the one or more biometric identifiers associated with the user matches a biometric identifier of an identified user of the plurality of users of the shared mobile device, associate106the identified user with the collaborative content input.

For the purpose of the following description, tablet computing device34may be described. However the description of tablet computing device34is intended for the purpose of illustration only. In various embodiments, the shared mobile device may include another mobile device, such as a smart phone device, a notebook computer, and/or any other mobile computing device.

In an embodiment identification process10may receive100, by a shared mobile device, an identifier input including one or more biometric identifiers associated with a user. For example, tablet computing device34may be a shared mobile device, such that a plurality of users may use a common tablet computing device34. The plurality of users may pass tablet computing device34to different users, thus allowing the plurality of users to access and collaborate on content (e.g., via client-side application10c4, which may include a collaboration application, and/or via collaboration application56, which may be accessed via tablet computing device34) using shared mobile device (e.g., tablet computing device34).

In general, biometrics may refer to the identification of individuals by their characteristics and traits. Biometric identifiers may include distinct, measurable characteristics which may be used to identify an individual. As such, some biometric identifiers of individuals may be unique to each individual. Examples of biometric identifiers may include, but are not limited to, facial recognition, fingerprint recognition, iris and/or retina recognition, and voice recognition. As discussed above, identification process10may receive100, by a shared mobile device, an identifier input including one or more biometric identifiers associated with a user. For example, user42may utilize shared mobile device (e.g., tablet computing device34). Tablet computing device34may include functionality to detect one or more biometric identifiers, including, but not limited to, a camera (not shown), microphone (not shown), fingerprint scanner (not shown), iris scanner (not shown), and/or any other feature having functionality capable of allowing identification process10to detect and/or capture a biometric identifier of a user.

For example, identification process10may receive100an identifier input including one or more biometric identifiers associated with user42having tablet computing device34. Further, identification process10may receive100an identifier input including one or more biometric identifiers associated with user42having tablet computing device34. In an embodiment, identification process10may not prompt user42to manually enter or input identification details of user42prior to logging in to, or otherwise using, tablet computing device34. Identification process10may receive100one or more biometric identifiers from user42including at least one of facial recognition, fingerprint recognition, iris and/or retina recognition, and voice recognition. For example, while using tablet computing device34, user42may hold tablet computing device34in such a manner that a camera (not shown) of tablet computing device34may capture a photo of user42's face. Similarly, while using table computing device34, user42may speak into a microphone (not shown) of tablet computing device34, allowing identification process10to capture a sample of user42's voice. Further still, user42may hold tablet computing device34in such a manner that fingerprint scanner (not shown) of tablet computing device34may scan and read user42's fingerprint. Tablet computing device34may also include an iris scanner (not shown) that may scan user42's iris. Thus, identification process10may receive100an identifier input including one or more biometric identifiers associated with user42, e.g., while user42is using tablet computing device34. Various additional and/or alternative biometric identifiers (whether based upon physical features and/or behavioral characteristics) may similarly be received100by identification process10via various suitable input means and/or sensors.

Identification process10may also receive102a collaborative content input from the user, the collaborative content input being associated with at least a portion of collaborative content. Collaborative content may include any content that may be created and/or modified by a user, or a plurality of users, of the shared mobile device, and/or one or more additional devices. Examples of collaborative content may include, but are not limited to, a word processing document, a presentation, a drawing document, and/or any other content that may be created and/or edited by a plurality of users (e.g., either simultaneously and/or at different points in time). Referring to the previous example, user42may provide a collaborative content input (such as a command or spoken content that may be converted to text via speech-to-text functionality, etc.) as a spoken input associated with at least a portion of collaborative content, which may be received102, for example, via a microphone (not shown) of tablet computing device34. For example, user42may wish to modify at least a portion of a presentation that user42's team has been collaborating on using tablet computing device34. User42may speak the command to apply (e.g., utilizing speech input, or speech-to-text capabilities) to a portion of the presentation into the microphone (not shown) of tablet computing device34. Thus, identification process10may receive102the command as a collaborative content input associated with at least a portion of the presentation from user42. Alternatively, identification process10may receive102the collaborative content input by any means available, including, but not limited to, a manually entered text input, or the like.

Identification process10may further compare104the one or more biometric identifiers associated with the user with biometric identifiers of a plurality of users of the shared mobile device. Identification information associated with a plurality of users, including the one or more biometric identifiers associated with the plurality of users, may be stored within a data store. Accordingly, in some embodiments, identification process10may access a data store, and may compare104the one or more biometric identifiers associated with the user with biometric identifiers of a plurality of users based on, at least in part, the identification information of the plurality of users within the data store. In various implementations, the data store may be maintained on the shared mobile device (e.g., storage device26of tablet computing device34in the foregoing example) via which the one or more biometric identifiers is received, and/or may be maintained on another device (e.g., storage device16associated with computing device12, and or on another storage device associated with another computing device).

Examples of a data store may include, but are not limited to, a list, a database, a directory, a corporate directory (such as an LDAP directory), and/or any type of collection of data. Identification information associated with a user stored within the data store may include, but is not limited to, a name of the user, contact information for the user, such as phone number, email, and/or the like, and any other identifying information of the user. One or more biometric identifiers associated with the user may also be stored within the data store, such as an image of the user's face, an audio recording of the user's voice, a scan of the user's iris and/or retina, and/or a scanned fingerprint of the user. Various other biometric identifiers may also and/or alternatively be stored within the data store. As generally set forth in the above example, a biometric identifier associated with the plurality of users may include the same and/or a similar biometric identifier as biometric identifier included within the identifier input that may be received100by identification process10.

Comparing104the one or more biometric identifiers associated with the user with biometric identifiers of a plurality of users based on, at least in part, the identification information of the plurality of users within the data store may include executing a query on the data store for user identification information correlated to the identifier input, including the one or more biometric identifiers, received100by the shared mobile device (e.g., tablet computing device34). Continuing with the above example, when user42(operating tablet computing device34) speaks a collaborative content input (such as a command or spoken content to be converted to text via speech-to-text functionality) associated with at least a portion of the collaborative content into a microphone (not shown) of tablet computing device34, identification process10may receive100, by tablet computing device34, the speech from user42. In such an example, the biometric identifier received100by identification process10may include voice characteristics associated with user42, e.g., which may be quantified and/or characterized using voice recognition functionality. Identification process10(alone and/or in conjunction with one or more other applications or processes) may execute a query on the data store based on the received100one or more biometric identifiers associated with user42(e.g., the spoken command). As such, identification process10may compare104the one or more biometric identifiers (e.g., voice characteristics) associated with user42with biometric identifiers of a plurality of users based on, at least in part, the identification information of the plurality of users within the data store. That is, identification process10may compare the received100voice characteristics to saved voice characteristics associated with other users, which may be stored in the data store. In some embodiments, the queried population (e.g., the plurality of users against which the received100identifier input is compared) may include all users for whom appropriate biometric identifier information (e.g., speech characteristics in the foregoing illustrative example) is available. In some embodiments, the queried population may be constrained based on one or more criteria. For example, the plurality of users of the shared mobile device may be known based upon, e.g., a common calendar/scheduling item indicating that they are currently working together on the collaborative content, known proximity of the users of the shared mobile device (e.g., based upon other wireless devices, access controlled facility, etc.), the users being logged into an application (such as collaboration application), etc.

Identification process10may further, when the identifier input including the one or more biometric identifiers associated with the user matches a biometric identifier of an identified user of the plurality of users of the shared mobile device, associate106the identified user with the collaborative content input. As described above, identification process10may compare104(e.g., based on a query executed on the data store, or other suitable mechanism) the one or more biometric identifiers associated with the user with biometric identifiers of a plurality of users based on, at least in part, the identification information of the plurality of users within the data store. Based upon the comparison, identification process10may determine whether a match exists between the received100identifier input, including the one or more biometric identifiers associated with the user, and biometric identifiers of a plurality of users stored within the data store. If a match exists, identification process10may determine an identity of the user based upon the identification information stored in data store associated with the identified user. That is, for example, in response to determining a match between the biometric identifier of the received100identifier input and the stored biometric identifiers of one of the plurality of users, identification process10may determine that the user from whom the identifier input was received is the individual of the plurality of users who is associated with the matching biometric identifier from the data store.

In an embodiment, identification process10may prompt the user for verification as the identified user. For example, identification process may display the identity of the user on a screen of the shared mobile device and prompt the identified user to select “yes” or “no” to confirm identification of the user. In some embodiments, identification process10may display the identity of the user on the screen of the shared mobile device. If the user determines that the displayed identity is not correct, the user may indicate an erroneous identity determination. If the user determines that the displayed identity is correct, the user may take no action in that regard. That is, a confirmation that the displayed identity is correct may not be required. Upon identification of the user, identification process10may associate106the identified user with the received102collaborative content input. In the above-example, the received102collaborative content input may include a spoken command and/or a manually entered text input. Identification process10may associate106the identified user with the received102collaborative content. In an embodiment, associating106the identified user with the collaborative content input may further include identification process10automatically storing the association106within the data store. In this manner, a history of collaborative content inputs and respective authors/contributors may be stored and accessed at a later time.

In an embodiment, identification process10may, when the identifier input including the one or more biometric identifiers associated with the user does not match a biometric identifier of one of the plurality of users of the shared mobile device, prompt108the user for identification details. As described above, identification process10may compare104(e.g., based on a query executed on the data store, or other suitable mechanism) the one or more biometric identifiers associated with the user with biometric identifiers of a plurality of users based on, at least in part, the identification information of the plurality of users within the data store. Based upon the comparison, identification process10may determine whether a match exists between the received100identifier input, including the one or more biometric identifiers associated with the user, and biometric identifiers of a plurality of users stored within the data store. In an embodiment, if a match does not exist, identification process10display a list of likely users based upon, at least in part, the query executed on the data store. The list may be sorted by likelihood of the match. The user may select a user from the list of likely users. In some embodiments, identification process10may further prompt the user for a password to verify the user.

In an embodiment, if a match does not exist, identification process10may prompt108the user for identification details. Identification process may prompt108the user for identification details including a name of the user, contact information for the user, such as phone number, email, and/or the like, one or more biometric identifiers associated with the user including at least one of an image of the user's face, an audio recording of the user's voice, a scan of the user's iris and/or retina, and/or a scanned fingerprint of the user, and/or any other identification information associated with the user. Identification process10may receive the identification details of the user, including the one or more biometric identifiers of the user (e.g., an image of the user's face via a camera of the shared mobile device, an audio recording of the user's voice via a microphone of the shared mobile device, a scan of the user's iris and/or retinal via an occular scanner of the shared mobile device, and/or a scanned fingerprint of the user via a fingerprint scanner of the shared mobile device). Identification process10may store the identification details of the user to the data store.

In an example embodiment, user42may use the shared mobile device (e.g., tablet computing device34) to access collaborative content. Identification process10may automatically receive100an identifier input, including one or more biometric identifiers associated with user42, via tablet computing device34(e.g., an image of user42's face via a camera of tablet computing device34, a spoken command of user42via a microphone of tablet computing device34, or other biometric identifier associated with user42). Identification process10may compare104the received100one or more biometric identifiers associated with user42with biometric identifiers of a plurality of users of tablet computing device34(e.g., based on a query executed on the data store, or other suitable mechanism). If identification process10matches the received100one or more biometric identifiers with a biometric identifier of the plurality of users of tablet computing device34, identification process10may identify user42. If identification process10does not match the received100one or more biometric identifiers with a biometric identifier of the plurality of users of tablet computing device34, identification process10may not identify user42. Upon identification process10not identifying user42as an identified user of tablet computing device34, identification process10may prompt106user42for identification details. Identification process10may receive the identification details associated with user42, including, but not limited to, user42's name, contact information, a password, and one or more biometric identifiers, including at least one of an image of user42's face (via a camera of tablet computing device34), a scanned fingerprint of user42(via a fingerprint scanner of tablet computing device34), a scanned iris and/or retina of user42(via an iris scanner of tablet computing device34), and an audio recording of user42's voice (via a microphone of tablet computing device34). Identification process10may store the identification details associated with user42in the data store. Upon receiving and storing the identification details associated with user42, identification process10may identify user42as the user of tablet computing device34. Identification process10may then associate106identified user42with the received102collaborative content input received from user42. Identification process10may further store the association106to the data store.

In an embodiment, identification process10may set110the identified user as a current user of the shared mobile device. Further, identification process10may display an identification of the identified user as the current user of the shared mobile device. For example, identification process10may identify user42as the user of tablet computing device34based upon, at least in part, the identifier input, including the one or more biometric identifiers associated with user42, received100from user42. Identification process10may display user42's name as the current user of tablet computing device34on the screen of tablet computing device34.

In a further embodiment, identification process10may edit112the portion of the collaborative content based upon, at least in part, the received collaborative content input. As discussed above, identification process10may receive102a collaborative content input from the user, the collaborative content input being associated with at least a portion of collaborative content. Collaborative content may include any content that may be created and/or modified by one or more users. Examples of collaborative content may include, but are not limited to, a word processing document, a presentation, and/or a drawing document. Based upon the received102collaborative content input associated with at least a portion of collaborative content from the user, identification process10may edit112the portion of the collaborative content. For example, user42may provide the collaborative content input associated with at least a portion of the collaborative content (e.g., word document, presentation, drawing document, or any other collaborative content). As described above, user42may provide the collaborative content input by speaking a command to apply to at least a portion of the collaborative content. Identification process10may use speech-to-text technology to apply the spoken command to the portion of the collaborative content (e.g., to perform some action on the portion of the collaborative content and/or to create, add to, or modify the portion of the collaborative content. Alternatively, user42may manually enter textual edits to the portion of the collaborative content. In this manner, based upon the received102collaborative content input from user42, identification process10may edit112at least a portion of collaborative content. That is, user42may add, delete, modify, and/or comment on portions of the collaborative content.

In an embodiment, identification process10may provide114an indicator of the associated identified user and the collaborative content input within the collaborative content. Identification process10may display the identification of the user who provided the collaborative content input associated with the portion of collaborative content as a visual indicator. For example, continuing with the above-described example, identification process10may display the identity of user42as the user that edited112the portion of the collaborative content. In this manner, as at least a portion of the plurality of users of shared mobile device (e.g., tablet computing device34) provide one or more collaborative content inputs, identification process10may associate106each identified user with their respective collaborative content input(s). As user42reviews the collaborative content, identification process10may provide114a visual indicator identifying each user that provided the collaborative content input associated with each edit and/or modification made to the corresponding portion of collaborative content. For example, if user42provides a collaborative content input associated with a portion of a presentation, the portion of the presentation may be edited112. Identification process10may provide114a visual indicator near the portion of the presentation that has been edited112, indicating that user42has modified that portion of the presentation. The visual indicator may include the identity of user42, along with a time and date stamp, and/or any other information relating to the modification made to the portion of the presentation.

As briefly discussed above, collaborative content may include one or more collaborative content inputs from at least a portion of the plurality of users of the shared mobile device. Continuing with the above example, user42may no longer require access to the collaborative content via shared mobile device (e.g., tablet computing device34). User42may log out of tablet computing device34, may put tablet computing device34away, and/or may hand tablet computing device34to another user (e.g., user40). User40may access the collaborative content via tablet computing device34in a similar manner as described above. For example, without prompting user40for identification information, identification process10may automatically receive100an identifier input, including one or more biometric identifiers associated with user40, via tablet computing device34(e.g., an image of user40's face via a camera of tablet computing device34, a spoken command of user40via a microphone of tablet computing device34, or other biometric identifier associated with user40). For example, user40may simply hold tablet computing device34in such a position while reviewing the collaborative content that identification process10may automatically receive100an image of user40's face captured by tablet computing device34. Alternatively, user40may simply speak while holding tablet computing device34such that identification process10may receive100the speech. Identification process10may compare104the received100one or more biometric identifiers (e.g., a captured image of user40's face and/or user40's voice) associated with user40with biometric identifiers of a plurality of users of tablet computing device34(e.g., based on a query executed on the data store, or other suitable mechanism). If identification process10matches the received100one or more biometric identifiers with a biometric identifier of the plurality of users of tablet computing device34, identification process10may identify user40. If identification process10does not match the received100one or more biometric identifiers with a biometric identifier of the plurality of users of tablet computing device34, identification process10may not identify user40. Upon identification process10not identifying user40as an identified user of tablet computing device34, identification process10may prompt106user40for identification details. Identification process may set110user40as the current user of tablet computing device34. Upon identification process10receiving102a collaborative content input from user40associated with at least a portion of collaborative content, identification process10may edit112the portion of the collaborative content based upon, at least in part, the received102collaborative content input from user40. Identification process may further provide114a visual indicator of the collaborative content input received by user40and applied to the portion of collaborative content. In this manner, shared mobile device (e.g., tablet computing device34) may be accessed by a plurality of users and identification process10may receive100an identifier input including one or more biometric identifiers associated with each of the plurality of users without disrupting the flow of collaboration on the shared mobile device by the plurality of users providing one or more collaborative content inputs associated with portions of the collaborative content. The one or more collaborative content inputs received from at least a portion of the plurality of users of the shared mobile device may be stored within a data store such that the collaborative content inputs are associated with the respective users who provided the collaborative content inputs. In this manner, identification process10may automatically store a history of collaborative content inputs without requiring manually identification of each user who provided each collaborative content input associated with portions of the collaborative content.

Referring also toFIG. 3, there is shown a diagrammatic view of computing system12. While computing system12is shown in this figure, this is for illustrative purposes only and is not intended to be a limitation of this disclosure, as other configurations are possible. For example, any computing device capable of executing, in whole or in part, identification process10may be substituted for computing device12withinFIG. 3, examples of which may include but are not limited to client electronic devices28,30,32,34.

Computing system12may include microprocessor200configured to e.g., process data and execute instructions/code for identification process10. Microprocessor200may be coupled to storage device16. As discussed above, examples of storage device16may include but are not limited to: a hard disk drive; a tape drive; an optical drive; a RAID device; an NAS device, a Storage Area Network, a random access memory (RAM); a read-only memory (ROM); and all forms of flash memory storage devices. IO controller202may be configured to couple microprocessor200with various devices, such as keyboard204, mouse206, USB ports (not shown), and printer ports (not shown). Display adaptor208may be configured to couple display210(e.g., a CRT or LCD monitor) with microprocessor200, while network adapter212(e.g., an Ethernet adapter) may be configured to couple microprocessor200to network14(e.g., the Internet or a local area network).

As will be appreciated by one skilled in the art, the present disclosure may be embodied as a method (e.g., executing in whole or in part on computing device12), a system (e.g., computing device12), or a computer program product (e.g., encoded within storage device16). Accordingly, the present disclosure may take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, micro-code, etc.) or an embodiment combining software and hardware aspects that may all generally be referred to herein as a “circuit,” “module” or “system.” Furthermore, the present disclosure may take the form of a computer program product on a computer-usable storage medium (e.g., storage device16) having computer-usable program code embodied in the medium.

The present disclosure is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the disclosure. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, may be implemented by computer program instructions. These computer program instructions may be provided to a processor (e.g., processor200) of a general purpose computer/special purpose computer/other programmable data processing apparatus (e.g., computing device12), such that the instructions, which execute via the processor (e.g., processor200) of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.

These computer program instructions may also be stored in a computer-readable memory (e.g., storage device16) that may direct a computer (e.g., computing device12) or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function/act specified in the flowchart and/or block diagram block or blocks.