WO2016140984A1

WO2016140984A1 - A smart iot wearable

Info

Publication number: WO2016140984A1
Application number: PCT/US2016/020296
Authority: WO
Inventors: Subramanya P. Herle
Original assignee: Applied Materials,Inc.
Priority date: 2015-03-03
Filing date: 2016-03-01
Publication date: 2016-09-09

Abstract

Embodiments include methods and apparatuses used in a smart ID network. In an embodiment, a smart ID network may be used for determining a physical location of a first smart ID that is communicatively coupled to a smart ID network. Embodiments may also include determining if a second smart ID that is communicatively couple to the smart ID network is proximately located to the first smart ID. In an embodiment, when the second smart ID is proximately located to the first smart ID, the process may include delivering public profile information associated with the first smart ID to the second smart ID over the smart ID network, and delivering public profile information associated with the second smart ID to the first smart ID over the smart ID network.

Description

A SMART IOT WEARABLE

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims the benefit of U.S. Provisional Patent Application 62/127,809 filed March 3, 2015, entitled A SMART IOT WEARABLE, and which is incorporated herein by reference in its entirety for all purposes.

BACKGROUND

1) FIELD

Embodiments pertain to the field of identification badges. More specifically,

embodiments pertain to smart identification badges that are communicatively coupled to a wireless network.

2) DESCRIPTION OF RELATED ART

Businesses and organizations control access to physical locations within their facilities (e.g., buildings, offices, etc.) with security badges. These security badges typically do not require a high degree of sophistication. For example, security badges may include a radio-frequency identification (RFID) tag. When the RFID tag is presented to an RFID reader, the RFID tag is activated and can transmit, to the RFID reader, the permissions (e.g., which doors may be unlocked by the security badge holder) that have been granted to the user of the security badge. If the permissions indicate that the user is allowed to access the location, a door may be unlocked. In large organizations it is beneficial to minimize the cost of the security badges since each individual that regularly works within a given facility, and possibly even guests to the facility, may need a security badge. Accordingly, there is little motivation to increase the complexity of the security badge, because the cost of the badge would increase.

However, as organizations increase in size and/or the frequency of face-to-face interactions decreases, the social interactions between individuals typically suffer. For example, an employee from a first department of the organization may rarely interact with an employee from a second department of the organization. When the two employees do cross paths (e.g., in a hallway or in a break room), it may be difficult for the employees to remember each other's name, or they may have never met before. As such, the employees may avoid any

communication with each other. This is not optimal for many organizations, especially where regular social interactions can build morale or spur creative brainstorming between employees.

Current security badge technology does not aid in the social interactions between the employees. Security badges are used primarily for providing access to facilities. As such, the badges are often hidden in pockets or wallets and may not be visible to others, since there is no line of sight requirement for RFID tags to function. Even when visible, the security badge may not provide any additional information beyond the employee's name. With limited information, it may be difficult to initiate a conversation.

SUMMARY

Embodiments include methods and apparatuses used for providing a plurality of smart identifications (IDs) that are communicatively coupled to one or more servers over a network.

An embodiment includes a method for sharing a public profile associated with a smart ID to proximately located smart IDs. In an embodiment the method may include determining a physical location of a first smart identification (ID) that is communicatively coupled to a smart ID network. The method may also include determining if a second smart ID that is

communicatively couple to the smart ID network is proximately located to the first smart ID. When two smart IDs are proximately located to each other, the method may include delivering public profile information associated with the first smart ID to the second smart ID over the smart ID network and delivering public profile information associated with the second smart ID to the first smart ID over the smart ID network.

According to an embodiment, the smart ID network may include one or more smart IDs. Embodiments include a smart ID that comprises a processer and a display electrically coupled to the processor. The smart ID may also include a network interface for sending and receiving data over a smart ID network. Embodiments may also include one or more sensors that are electrically coupled to the processor.

BRIEF DESCRIPTION OF THE DRAWINGS

Figure 1 is a diagrammatic illustration of a smart ID network, according to an

embodiment.

Figure 2 illustrates a block diagram of an exemplary smart ID, according to an embodiment.

Figure 3A is a diagrammatic illustration of a smart ID network that includes an additional client device, according to an embodiment.

Figure 3B is an illustration of a user interface that may be used to modify a public profile associated with a smart ID, according to an embodiment.

Figure 3C is an illustration of a user interface that may be used to modify profile settings associated with a smart ID, according to an embodiment.

Figure 4 is an illustration of a plan view of a portion of an office that includes a smart ID network, according to an embodiment.

Figure 5 is a flow chart that illustrates processing operations that may be implemented to share public profiles with smart IDs that are located proximate to each other, according to an embodiment.

Figure 6 is a flow chart that illustrates processing operations that may be implemented to provide a mapping functionality to a smart ID, according to an embodiment.

Figure 7 is a flow chart that illustrates processing operations that may be implemented to provide a voting functionality to one or more smart IDs, according to an embodiment.

Figure 8 is an illustration of a portion of an office that includes a public display that is communicatively coupled to a smart ID network, according to an embodiment.

Figure 9 is a flow chart that illustrates processing operations that may be implemented to provide a reality mining functionality to a smart ID network, according to an embodiment.

Figure 10 is a flow chart that illustrates processing operations that may be implemented to provide tourism and entertainment functionality to a smart ID network, according to an embodiment.

DETAILED DESCRIPTION

Embodiments include methods and apparatuses used for providing a plurality of smart identifications (IDs) that are communicatively coupled to one or more servers over a network. It will be apparent to one skilled in the art that embodiments may be practiced without these specific details. In other instances, well-known aspects are not described in detail in order to not unnecessarily obscure embodiments disclosed herein. Furthermore, it is to be understood that the various embodiments shown in the Figures are illustrative representations and are not necessarily drawn to scale.

In addition to providing typical functions of a security badge, such as those described above, a smart ID allows for increased social interaction within an enterprise. Embodiments include systems and methods that allow for a first smart ID to recognize that a second smart ID is proximately located and, thereafter, display a profile assigned to the second smart ID on a display of the first smart ID. For example, the profile may include the name and job title of the user of the second smart ID. Similarly, the second smart ID may display a profile associated with the first smart ID. Therefore, social interactions between the end users of the first and second smart IDs may be facilitated because each may be provided with the name and additional information about the other person.

In addition to the ability to share profiles between smart IDs that are proximately located to each other, embodiments may also include a plurality of other features beneficial to the end user. By way of example, and not by way of limitation, these additional features may include one or more of behavioral reminders, calendar integration, the ability to obtain flash updates, mapping functionalities, and voting functionalities. These additional features may be

inexpensively integrated into the smart IDs due to the network connection. The enhanced functionality of the smart IDs is provided by offloading some or all of the processing and data storage functions to the server over the network. Therefore, the smart IDs may be made in a cost effective manner since the components (e.g., processor, memory, etc.) do not need to be as robust as would be the case if the processing was implemented on the smart ID itself.

The value of the smart ID system increases as a greater percentage of an organization adopts the use of the technology. Accordingly, it may be beneficial to allow users to customize information that may be shared as part of their profile. Additionally, persons who have privacy concerns may also want to disable certain functionalities of the smart ID. As such, embodiments may include one or more ways to disable functionalities of the smart ID. For example, the ability to modify settings of the smart ID may be software based or they may be hardware based. In an embodiment, the software based control may be implemented by modifying profile settings in the profile associated with a smart ID. In an embodiment, the hardware based modifications may be implemented with one or more sensors or physical switches on or in the smart ID that disable transmission of data over the network.

Additionally, embodiments allow for enterprise wide reality mining. For example, the locations and interactions between individuals may be logged by a central server. The logged data may be used by the enterprise to study patterns and/or behaviors, and the effect that the patterns and behaviors have on the workplace environment. For example, the social interactions between employees may be monitored after a merger between two companies to determine whether the employees from each of the companies are integrating.

Furthermore, while embodiments are described in view of an organizational or business environment, the benefits obtained from the use of smart IDs are not limited to such

environments. By way of example, and not by way of limitation, a smart ID system may be utilized in an educational environment, to aid in tourism (e.g., a museum, a downtown area, a historical district, etc.), or in an entertainment environment, such as to facilitate the playing of a game.

Referring now to Figure 1, a diagrammatic representation of a smart ID network 100 is illustrated according to an embodiment. As illustrated, one or more uniquely identifiable smart IDs 120i - 120_n may be communicatively coupled to one or more servers 160 in the smart ID network 100. In an embodiment, the smart ID 120 is shaped to be worn as a badge. For example, a lanyard or a clip (not shown) may be attached to the smart ID 120 to allow for easy and comfortable wearing. In an embodiment, a display 210 covers a substantial portion of a surface of the smart ID 120, though embodiments are not limited to such configurations. In an additional embodiment, the smart ID 120 may be incorporated into a band that may be worn around a user's wrist, into clothing, or into any other wearable article.

In an embodiment, the smart ID network 100 may be a Wireless Local Area Network (WLAN) (e.g., a Wi-Fi network). WLANs are becoming increasingly common features that are included in the infrastructure of enterprises (e.g., companies, organizations, etc.) in order to provide wireless connection to persons within an enterprise's facility. As such, the integration of a smart ID network 100 into a preexisting WLAN may not need a significant investment in additional infrastructure.

Client devices that are within the WLAN communicate with one or more access points 140i - 140_n in order to obtain access to one or more network servers 160. In an embodiment the one or more smart IDs 120 are client devices that are able to communicate with the access points 140. An access point is a digital device that operates as a gateway for a client device to establish a connection (e.g., a communicative coupling) with one or more networks. For example, an access point 140 may be implemented as a wireless access point (WAP), which is configured to communicate wirelessly with one or more client devices, such as the smart IDs 120, as well as communicate with a networked device associated with the one or more networks, such as, for example, the server 160, through a wired or wireless connection. Accordingly, embodiments include a smart ID network 100 that allows for one or more smart IDs 120₁ - 120_n to

communicate with a server 160 through one or more access points 140.

It is to be appreciated that the smart ID network 100 is not limited to being implemented on a WLAN. Additional embodiments may include a smart ID network 100 that is implemented on any other wireless network. By way of example, and not by way of limitation, the smart ID network 100 may be implemented on one or more of a cellular network, a wireless personal area network (WPAN) (e.g., Bluetooth), or the like.

Referring now to Figure 2, a diagrammatic representation of a smart ID 120 is illustrated. According to an embodiment, the smart ID 120 may operate in the capacity of a client device in a client-server network environment, such as the smart ID network 100, described above. In an embodiment, the smart ID 120 may use a network interface 208 to send and receive signals (e.g., data packets) to the access points 140. The network interface 208 may include the necessary hardware (e.g., an antenna, a signal generator, etc.), firmware, and software for communicating with the one or more wireless access points 140 of the smart ID network 100. According to additional embodiments, the smart ID 120 may include two or more network interfaces 208 to facilitate communication with different network types. For example, a smart ID may include network interfaces 208 that allow for communication over a WLAN, a WPAN, a cellular network, or any combination thereof. Embodiments may also include a global positioning system (GPS) 246. The GPS 246 may allow for accurate location information of the smart ID 120 to be shared with the server 160 over the smart ID network 100.

The exemplary smart ID 120 includes a processor 202, a main memory 204 (e.g., readonly memory (ROM), flash memory, dynamic random access memory (DRAM) such as synchronous DRAM (SDRAM) or Rambus DRAM (RDRAM), etc.), and a static memory 206 (e.g., flash memory, static random access memory (SRAM), etc.), which communicate with each other via a bus 230.

Processor 202 represents one or more general-purpose processing devices such as a microprocessor, central processing unit, or the like. More particularly, the processor 202 may be a complex instruction set computing (CISC) microprocessor, reduced instruction set computing (RISC) microprocessor, very long instruction word (VLrW) microprocessor, processor implementing other instruction sets, or processors implementing a combination of instruction sets. Processor 202 may also be one or more special-purpose processing devices such as an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), a digital signal processor (DSP), network processor, or the like. Processor 202 is configured to execute the processing logic 226 for performing the operations described herein.

The smart ID 120 also may include a display unit 210 (e.g., a liquid crystal display (LCD), a light emitting diode (LED) display, an organic light emitting diode (OLED) display, or an electrophoretic ink (E-ink) display). According to an embodiment, the display unit 210 may be chosen to provide low power consumption. For example, current OLED display and E-ink display technologies may utilize significantly less power than current LCD display technologies. Embodiments may use components with lower power consumption in order to improve the battery life of the smart ID 120. In an embodiment, the smart ID 120 may be powered by a power supply 218. By way of example, the power supply 218 may be a battery or a capacitive storage device. In an embodiment, the smart ID 120 may include one or more input devices 212. In an embodiment, the input device 212 may be a keyboard. By way of example, the keyboard may be integrated into the display unit 210 when the display is a touch screen device. A touch screen device may allow for additional security features to be integrated into the smart ID 120, such as, for example, a fingerprint scanner. Additional input devices 212 may include a camera, or a microphone. The use of a camera or a microphone may allow for voice generated commands or eye-tracking capabilities. According to an embodiment, a smart ID 120 may also include a signal generation device 216, such as a speaker.

In an embodiment, software 222 that embodies any one or more of the methodologies or functions described herein may reside completely or partially within the main memory 204 and/or within the processor 202 during execution thereof by the smart ID 120, the main memory 204 and the processor 202 also constituting machine-readable storage media. The software 222 may further be transmitted or received over the smart ID network 100 via the network interface 208. The term "machine-readable storage medium" or "non-transitory machine readable storage medium" should be taken to include a single medium or multiple media (e.g., a centralized or distributed database, and/or associated caches and servers) that store the one or more sets of instructions. The term "machine-readable storage medium" or "non-transitory machine readable storage medium" shall also be taken to include any medium that is capable of storing or encoding a set of instructions for execution by the machine and that cause the machine to perform any one or more of the methodologies of embodiments described herein. The term "machine-readable storage medium" or "non-transitory machine readable storage medium" shall accordingly be taken to include, but not be limited to, solid-state memories, and optical and magnetic media.

Embodiments may also include one or more sensors 247. The sensors 247 allow for additional position data of the smart ID to be obtained and/or allow for gesture based commands. In an embodiment, the sensors may be microelectromechanical systems (MEMS). MEMS sensors may be inexpensively integrated into the smart IDs 120 while still maintaining a thin physical profile. As such, the inclusion of MEMS sensors 247 may not significantly increase the size of the smart IDs 120 or increase their cost. By way of example, the sensors 247 may include one or more of an accelerometer, a gyroscope, or the like.

Embodiments may also include a smart ID 120 that further includes an RFID tag 231. The RFID tag 231 may include a memory for storing information regarding a set of permissions. For example, the set of permissions may includes a list of all locations within a facility that the user may access, a list of locations within a facility that the user may not access, a set of restrictions based on time of day (e.g., no access allowed after normal working hours), a set of restrictions based on the day of the week (e.g., no access allowed on weekends), or the like, and any combinations thereof. When the smart ID 120 is presented to an RFID reader, such as a reader that is located proximate to a locked door, the RFID tag 231 may transmit the permissions stored on the smart ID 120. If the permissions indicate that the individual has permission to enter the location, then the door may be temporarily unlocked.

According to an additional embodiment, the smart ID 120 may also include an RFID reader 232. The inclusion of an RFID reader 232 may aid in proximity monitoring applications. For example, an RFID reader 232 may be able to identify the RFID tags in other smart IDs 120 that are proximately located, or be able to detect an RFID tag that is associated with a location within a facility in order to provide location information to the server 160. Such embodiments are described in greater detail below.

Each smart ID 120 may be associated with a user profile. In an embodiment, an end user is able to control information that is stored on the user profile, what information from the user profile is shared with other smart ID users, which additional features of the smart ID may be activated, and whether or not the smart ID should be tracked by the smart ID network. Referring now to Figure 3 A, a schematic diagram illustrates that the server 160 may include a profile database 355, according to an embodiment. For example, the profile database 355 may be stored in a memory within the server 160, or the profile database 355 may be stored in a memory external to the server 160, but accessible to the server 160 over the smart ID network 100. The exemplary server 160 may include a main memory (e.g., ROM, flash memory, DRAM, such as SDRAM or RDRAM, etc.), and a static memory (e.g., flash memory, SRAM, etc.), which communicate with each other via a bus (not shown).

The profile database 355 may store one or more unique profiles that are each associated with different smart IDs 120. Storing the profiles on the server 160 reduces the memory capacity needed for the smart ID 120. Instead of storing the profile locally on the smart ID 120, embodiments allow for the smart ID 120 to access the profile it is associated with, in addition to the profiles associated with other smart IDs 120, through the network 100. Accordingly, if an end user wants to modify the profile associated with their assigned smart ID 120, they can do so by accessing the profile database 355 through the smart ID network 100, via the smart ID 120.

Additional embodiments may allow for a user to access the profile associated with their assigned smart ID 120 via another client device 322 connected to the smart ID network 100. In an embodiment, the additional client device 322 may be a mobile device, such as a cellular phone or a laptop, or the additional client device 322 may be stationary, such as a desktop computer. The additional client device 322 may be coupled to the smart ID network 100 via a wireless connection through an access point 140, or through a wired connection 353, such as, for example, an Ethernet connection.

Referring now to Figure 3B, a schematic representation is illustrated that depicts a user interface for a public profile 356 that is associated with a smart ID 120. It is to be appreciated that the layout and design of the user interface of the public profile 356 is exemplary in nature and the public profile that may be displayed or transmitted over the smart ID network 100 is not limited to such configurations. The user may access the user interface of the public profile 356 through the smart ID 120, or through an additional client device 322 connected to the smart ID network 100.

In an embodiment, the public profile 356 may include one or more personal information items 357. By way of example, and not by way of limitation, the personal information items 357 may include information regarding the smart ID user's name, job title, hobbies, a picture of the user, the user's schedule, or any other information that may be beneficial for sharing. In an embodiment, the personal information items 357 may be modifiable by the user of the smart ID 120. Additional embodiments may include one or more personal information items that are not modifiable by the user of the smart ID 120. For example, personal information items 357 such as the user's name and job title may be set by an administrator and are not modifiable, whereas personal information items 357 such as, listed hobbies and schedule may be modifiable by the smart ID user.

Additional embodiments allow the smart ID user to modify which personal information items are sharable and which are private. A sharable personal information item 357 may be transmitted over the smart ID network 100 to smart IDs 120 that are not associated with the profile 356, as will be described in greater detail below. Personal information items 357 that are deemed private will not be transmitted over the smart ID network 100 to smart IDs 120 that are not associated with the profile 356. Accordingly, users may have control over which portions of their profile 356 are accessible to other users of the smart ID network 100. In an exemplary embodiment illustrated in Figure 3B, each of the personal information items may have a button that may be toggled between a public setting and a private setting, in accordance with the user's selections.

Referring now to Figure 3C, a schematic representation is illustrated that depicts a user interface for a group of profile settings 358 that are associated with a smart ID 120. It is to be appreciated that the layout and design of the user interface of the profile settings 358 is exemplary in nature and the profile settings that may be displayed or transmitted over the smart ID network 100 is not limited to such configurations. The user may access the user interface of the profile settings 358 through the smart ID 120, or through an additional client device 322 connected to the smart ID network 100.

In an embodiment, the profile settings 358 allow the user to control different settings of the smart ID 120 and/or whether or not various features are enabled. Embodiments may include one or more tracking settings 361. Modifying the tracking settings 361 allows the end user to control what information about the use of the smart ID 120 is being stored and/or shared by the server 160.

In one embodiment, the tracking settings 361 may include an option to turn off all tracking and storage of information related to the smart ID 120. For example, turning off all tracking and storage of information may be implemented by disabling the network interface 208 of the smart ID 120. As a result, the smart ID 120 is blocked from accessing the smart ID network 100. Blocking the smart ID 120 from accessing the smart ID network 100 may reduce the functionality of the smart ID 120 (e.g., the smart ID may not be able to access profile information associated with other smart IDs 120, access maps of the facility, provide reminders, etc.), but the RFID tag 231 may still function to open locked doors.

Additional embodiments may include a tracking setting 361 that controls when the smart ID 120 may be tracked. In an embodiment, the tracking setting 361 may be set such that the smart ID 120 is only tracked when the smart ID 120 is located within certain areas of the facility. For example, an employee may only want to be tracked while in the break room. As such, the smart ID users are able to select a balance between functionality and privacy.

Further embodiments allow for tracking settings 361 to be overridden by inputting a password into the smart ID 120. In an embodiment, the password may be an alphanumeric password that is inputted with an input device 212, such as a touchscreen keyboard on the display 210. In an additional embodiment, the password may be based on a biometric sensor that only the user assigned to the smart ID 120 may activate. For example, a fingerprint scan may be implemented through a designated finger print sensor 247 located on the smart ID 120, or through a fingerprint scan on a touchscreen display 210. Additional biometric sensors 247, such as voice recognition through a microphone or a retinal scan with a camera, may be used to override and/or disable tracking settings 361. In an embodiment, the password may be a gesture based password detected via a camera, an accelerometer, or a gyroscope. A gesture based password may be any repeatable physical motion of the smart ID 120 that may be sensed by one or more of the sensors 247, or a repeatable physical motion performed by the user of the smart ID that may be captured by the camera 212. Additional embodiments may include a hardware switch or button on the smart ID 120 that electrically disconnects the network interface 208. For example, a physical switch or button may be used to electrically disconnect the network interface 208 from the power source 218. Accordingly, in some embodiments, end users may be provided additional control over their privacy because they are able to override the tracking settings 361 by turning on or off a hardware switch that cannot be overridden by software.

An additional embodiment may preclude the user of the smart ID 120 from disabling the tracking settings 361. For example, an organization may desire to track all movement of the employees in order to find patterns and behaviors that are effecting the efficiency or environment of the organization. In such embodiments, there may not be a physical switch or a password that can override the tracking settings 361.

In an embodiment, one or more behavior reminders 362 may be included as an additional feature available in the profile settings 358. Behavior reminders 362 are reminders that may be chosen by the user in order to improve their efficiency, health, attitude, or the like. A selected behavior reminder 362 may be broadcast from the server 160 over the smart ID network 100 to the smart ID 120 associated with the profile. The reminder may be broadcast at predetermined times, one or more times a day, at random times, or the like. By way of example, and not by way of limitation, a user may select a behavior reminder 362 that contains a reminder to drink water, and the user may set the frequency of the reminder to be once every two hours, during working hours. As such, the user may be reminded to drink water several times a day. Additional behavior reminders 362 may include, but are not limited to, taking a break, walking, stretching, checking posture, eating a healthy snack, or any other behavior.

In an embodiment, one or more scheduling reminders 363 may be included as an additional feature available in the profile settings 358. By way of example, and not by way of limitation, scheduling reminders 363 may provide reminders for meetings, due dates, responding to emails, or the like. In an embodiment, scheduling reminders 363 may be auto-populated by the server 160, when the server 160 is able to interface with a user's email and/or calendar account(s). Additional embodiments may allow for the end user to manually set up reminders in the profile settings 358. In an embodiment, when a scheduling reminder 363 is set, either automatically by the server 160 or manually by the user, the server 160 may transmit the reminder over the smart ID network 100 to the smart ID 120 at the scheduled time.

In an embodiment, the profile settings 358, may also include the ability to receive flash updates 364. A flash update is a message that may be sent out over the smart ID network 100 to one or more smart IDs 120 at substantially the same time. For example, a flash update 364 may be used to notify employees that a party is being hosted in a break room, severe weather may be on the way, building maintenance issues, or any other message that may need to be sent to one or more, or all employees.

According to an embodiment, a flash update 364 may be initiated by an administrator who has authority to send flash updates 364. As such, the frequency of the flash updates 364 can be controlled by limiting who has the authority to send the flash updates 364. The authorized user may provide instructions to the server 160 to deliver the flash update over the network 100 to one or more of the smart IDs 120. In an embodiment, the flash update may be selectively sent to certain smart IDs. By way of example, and not by way of limitation, the flash update 364 may be selectively sent to smart IDs 120 that are located in a certain area of the facility, to smart ID's 120 that are possessed by users who belong to a certain work group, to smart ID's 120 that are possessed by users who hold a certain job title, or the like.

However, if a user of a smart ID 120 does not want to receive the flash updates 364, then the flash updates 364 may be disabled. Additional embodiments may include modifying the profile settings 358 so that only certain categories of flash updates 364 may be received. For example, the user may only want to receive flash updates 364 that pertain to an emergency (e.g., weather warnings, security concerns, etc.), and the user may not wish to receive flash updates 364 that are not as critical (e.g., party notifications, planned building maintenance, etc.).

According to an additional embodiment, the smart ID 120 may also be configured to provide an adaptable user interface. In one embodiment, the user interface may be modifiable by the end user. For example, an end user of a smart ID 120 may prefer that a certain set of options or settings be the first items displayed on the display 210. The user may change what is displayed and the layout of the display by accessing the user profile associated with their smart ID 120 that is stored in the profile database 355. The end user may access the profile in the profile database 355 with the smart ID 120 or with an alternative client device 322. In addition to modifying the layout and contents of a user interface, the end user may also program shortcuts. For example, a shortcut may be programmed to bring up a list of often used contacts (e.g., a favorites list) when a meeting is being scheduled on the smart ID 120.

In an additional embodiment, the adaptable user interface may be modified automatically. The user interface may be modified by software that is located on the server 160 or is accessible to the server 160. Generally, the software may be configured to monitor the usage of each smart ID 120 in order to detect patterns. When a pattern is detected, the software may modify the user interface in order to provide a personalized user interface that is easier and/or more efficient for an end user to operate. In an additional embodiment, if a pattern is detected, the end user may be notified and given the option to accept or decline the automatic modification of the user interface.

In an embodiment, software may be configured to monitor end user behavior in order to determine if one or more different pattern types occur. Pattern types may include repeated sequences of events, repeated instances of an event that occurs at a certain time, conditional relationships, combinations of such patterns, or the like. For example, a repeated sequence of events may include accessing a directory, then searching for a particular contact, and then selecting the particular contact. In such an embodiment, the user interface may be modified so that the act of accessing the directory may automatically bring up the option to select the particular contact without needing to search for the contact. An example of a repeated instance of an event that occurs at a certain time may include a weekly meeting. For example, if a meeting is regularly scheduled for Tuesday mornings at 10:00 AM, then a schedule reminder 363 may be automatically generated for that time. A conditional relationship between behaviors may include a situation where behaviors commonly occur together. For example, some end users may turn on tracking each time they enter a common area. In such an embodiment, the user interface may be modified to provide the tracking settings as the first item on the display when the end user enters a common area. It is to be appreciated that the examples of pattern types listed above are exemplary in nature and are not limiting.

In some embodiments, a threshold percentage may be used for determining if a pattern has been formed. For example, the threshold percentage may be 80% (e.g., with respect to a conditional pattern, if the observed relationship holds true at least 80% of the time, then the behavior is considered to be a pattern). While 80% is used as an example, it is to be appreciated that the threshold percentage may be any percentage. For example, different behaviors may use a different threshold percentages to be considered a pattern.

Embodiments include features that may be used to increase social interaction between users of the smart IDs 120 and/or increase productivity. An exemplary illustration of the social interaction benefit provided by an embodiment is explained in conjunction with Figure 4. In Figure 4, an overhead view of a portion of an office 405 is illustrated. According to an embodiment, the office 405 includes one or more rooms 480. The rooms may be designated for different purposes. For example, the rooms may be a private office, a meeting room, a break room, or the like. In the office 405 illustrated in Figure 4, rooms 480A are private offices, room 480B is a break room, and room 480c is a meeting room. One or more smart IDs 120 may be located throughout the office 405. For example, each employee may be wearing or holding a smart ID 120. As such, the location of the smart IDs 120 may change as employees move around. The office 405 may include a smart ID network 100. The smart ID network 100 may include one or more access points 140. The access points 140 provide wireless access to the smart IDs 120 and allow for them to be communicatively coupled to one or more servers 160 (not shown in Figure 4).

In an embodiment, the smart ID network 100 within an office 405 allows for increased frequency of social interaction. The frequency of social interaction may increase because the user of the smart ID 120 may have access to public profile information of persons that are nearby. For example, if a first user of the smart ID 120₁ is located proximate to a second user of the smart ID 120₂, then public profile information associated with the neighboring second smart ID 120₂ may be sent to the first smart ID 120₁ to provide the identity and other information from the neighbor's public profile.

Referring now to Figure 5, a flow chart is provided that illustrates processing operations that may be implemented by the server 160 to allow for sharing public profile information between smart IDs 120 that are located proximate to each other, according to an embodiment. At operation 570, the server determines the location of a first smart ID 120i. Embodiments include different processes to determine the location of the first smart ID 120i. In an embodiment, the location of first smart ID 120₁ may be determined by a GPS unit 246 in the first smart ID 120i. For example, the server 160 may send a request to the first smart ID 120₁ that instructs the first smart ID 120₁ to report to the server 160 its current location obtained from the GPS unit 246.

Additional embodiments include using the access points 140 to determine the location of a smart ID 120. For example, the signal strength from the access point 140 may be used to determine the distance from the access point 140. In embodiments with a plurality of access points 140, the signal strength from two or more of the access points 140 may be used to triangulate the location of the smart ID 120.

Additional embodiments may utilize a system of RFID readers 466 to monitor the position of the smart ID 120. For example, the RFID readers 466 may be located throughout the office 405, and are each connected to the smart ID network 100. In an embodiment, an RFID reader 466 may be located at the entrance to each room 480. As a smart ID 120 passes by the RFID reader 466, the RFID reader 466 is triggered and the RFID tag 231 in the smart ID 120 is read to determine the identity of the smart ID 120. The RFID reader 466 may then send a signal to the server 160 (not shown) that instructs the server to update the location of the smart ID 120 that triggered the RFID reader 466 to the location of the triggered RFID reader 466.

Referring now to operation 571, the server 160 may determine if a second smart ID 120 is located proximate to the first smart ID 120. A proximate relationship between smart IDs 120 may be any distance that would allow for verbal communication. In an embodiment, two smart IDs 120 may be considered proximate to each other when they are within the same room 480. For example, in Figure 4, the first smart ID 120₁ and the second smart ID 120₂ are proximately located with each other. However, it should be noted that being in the same room 480 may not always result in two smart IDs being proximate to each other. For example, a room 480 may be large and have a capacity to hold many persons (e.g., a cafeteria, an auditorium, a gymnasium, or the like). In such situations, more precise location information for the smart IDs 120 may be used to determine if the two smart IDs are proximate to each other. For example, location information obtained from a GPS 246, signal strength of the access points 140, or information from a RFID reader 232 within the smart IDs 120 may allow for more precise location information of the smart IDs 120 to be obtained.

In an embodiment, a proximate relationship between the location of smart IDs 120 may be considered to be a physical separation of less than approximately twenty feet. An additional embodiment may consider a proximate relationship between the location of smart IDs 120 to be a physical separation of less than approximately ten feet. In embodiments that utilize an RFID reader 232 within the smart IDs 120 to provide the location information, a proximate relationship between smart IDs 120 may be a physical separation that is less than or equal to the maximum range of the RFID reader 232.

In some embodiments, the locations of two smart IDs 120 may be physically close to each other, but not proximate to each other. For example, in Figure 4, the first smart ID 120₁ and the third smart ID 120₃ may be physically close to each other, but would not be able to verbally communicate because they are located on opposite sides of a wall. As such, the server 160 may determine that the first smart ID 120₁ and the third smart ID 120₃ are not proximately located to each other, because there is a wall between them.

Referring now to operation 572, when the server determines that the second smart ID 120₂ is proximately located to the first smart ID 120i, the server may deliver public profile information associated with the first smart ID 120₁ to the second smart ID 120₂ over the smart ID network 100, and the server 160 may also deliver public profile information associated with the second smart ID 120₂ to the first smart ID 120₁ over the smart ID network 100. In an

embodiment, the public profile information delivered to the first and second smart IDs 120₁ and 120₂ may be displayed on the displays 210 of the smart IDs 120. As such, the persons using the smart IDs 120₁ and 120₂ are provided with some information about the person to whom they are proximately located. This information may provide convenient conversation starters that may lead to increased frequency of social interaction between the individuals. For example, if the personal information items 357 that are shared include hobbies, then a discussion about that hobby may be initiated.

In an embodiment, the smart ID network 100 may also allow for a mapping application to be used in conjunction with the smart IDs 120. In large facilities, an individual may not be familiar with each portion of the building. For example, a facility may include multiple floors, wings, or even multiple buildings. In situations where a meeting is being held in a location that a person is unfamiliar with, it may be beneficial to provide a mapping functionality with the smart IDs 120. Additionally, a mapping application may also be beneficial to visitors or new

employees who are not familiar with the facility.

Referring now to Figure 6, a flow chart is illustrated that shows several processing operations that may be implemented by the server 160 to provide a mapping feature to a smart ID 120, according to an embodiment. Referring now to operations 670, the server 160 may obtain a map request for a smart ID 120. In an embodiment, the map request may be

automatically generated by the server 160. For example, when the smart ID 120 is linked with a scheduling program used by the smart ID user, a meeting scheduled in the scheduling program may automatically trigger the server 160 to generate a map request to the meeting location.

Additional embodiments may allow a user of the smart ID 120 to send a map request to the server 160 that requests directions to any location within the facility. In such embodiments, the smart ID user may select a destination from a user interface displayed on the display 210 of the smart ID 120. The selection may be made with a voice command, a gesture, or an input, such as clicking on the location displayed on the display 210.

After receiving the map request, the server 160 may determine the location of the smart ID 120, as illustrated in operation 671. The server 160 may determine the location of the smart ID 120 in substantially the same manner as described above with respect to the profile sharing embodiment, and as such, will not be repeated here.

In an embodiment, the server 160 may then determine a route from the present location of the smart ID 120 to the destination location, as illustrated in operation 672. In an embodiment, the route that is determined by the server may be the shortest route between the two locations. An additional embodiment may provide a route that avoids any locations that the smart ID 120 is not provided permission to enter. For example, if the shortest route between the present location of the smart ID 120 and the destination forces the user of the smart ID to cross through a building or office that the user is not authorized to enter, then the smart ID 120 may alter the route. An additional embodiment may provide a route that is determined in view of

environmental factors. For example, if one possible route dictates that the user exit a building and go outside and an alternate route allows for the user to remain indoors the entire route, then the outdoor route may be chosen if it is a sunny day, whereas the indoor route may be chosen if it is a rainy day. Embodiments may also determine the route based on one or more factors such as traffic, occupied rooms, accessibility (e.g., wheel chair accessible), or the like.

Once the route is determined by the server 160, the process may advance to operation 673. In operation 673 the server may deliver the route information to the smart ID 120 over the network. In an embodiment, the route information may include turn-by-turn written directions and/or a visual map. Once the route information is received by the smart ID 120, the smart ID 120 may display the map and/or written directions on the display 210.

In an additional embodiment a plurality of smart IDs 120 may be utilized for a voting operation. A voting operation may be beneficial because it allows for a group of people to express their opinion on a subject. For example, the voting operation may allow for participants in a meeting to quickly determine the percentage of the participants that agree or disagree with a proposal.

Referring now to Figure 7, a flow chart is illustrated that shows several processing operations that may be implemented by the server 160 to provide a voting feature to a plurality of smart IDs 120, according to an embodiment. In operation 770, the server 160 may receive a vote request from a smart ID 120 used by a vote originator. In an embodiment, the vote request may include one or more voting parameters.

In an embodiment, the voting parameters may include the selection of a voting format. For example, the vote may provide the voters with a "yes" or "no" option, the vote may provide the voters with the option of choosing one candidate from a list of two or more candidates, the vote may provide the voters with a list of options that can be ranked from highest to lowest, or the like.

In an embodiment, the voting parameters may also include the duration that the opportunity to vote will be open. For example, if a quick vote is needed, the voting parameter may limit the time for voting to less than a minute, whereas if more thought is needed, the voting parameter may include no limit for the amount of time the votes may be submitted. Additional embodiments may not include a set duration, and instead allow the vote originator to end the voting at any time.

In an embodiment, the voting parameters may also include a selection of which smart IDs 120 will be allowed to vote. For example, the opportunity to vote may be may be selectively sent to smart IDs 120 that are located in a certain area of the facility, to smart ID's 120 that are possessed by users who belong to a certain work group, to smart ID's 120 that are possessed by users who hold a certain job title, or the like.

Embodiments may also include a voting parameter that allows for the cast votes to be public or anonymous. Allowing the votes to be made public may be beneficial if the vote originator wants to know how each person voted. Alternatively, an anonymous vote may allow for a more candid response.

Referring now to operation 771, the server 160 may generate a ballot based on the voting parameters that were chosen by the vote originator. Thereafter, at operation 772, the server 160 may deliver the ballot to each of the smart IDs 120 selected by the vote originator over the smart ID network 100. In embodiments that include a timed voting duration, the time allotted for the vote may begin once the ballots have been delivered to the smart IDs 120 by the server 160.

Once received by a smart ID 120, the ballot may be displayed to the user of the smart ID by the display 210. In an embodiment, the user may select their vote from their smart ID 120. For example, the user may make their selection by touching the portion of the display on which their selection is located, when the display 210 is a touch screen display. Once the vote is selected by the user, the smart ID 120 may deliver the completed ballot over the smart ID network 100 to the server 160.

Referring now to operation 773, the server 160 may receive the completed ballots from one or more of the smart IDs 120. According to an embodiment, the server 160 may continue to receive completed ballots from the smart IDs 120 until the vote is completed. By way of example, the vote may be completed at the expiration of the vote duration selected by the vote originator. When the vote does not include a timed duration, the voting may be completed when all ballots sent by the server 160 have been returned. Additional embodiments allow the vote originator to end the voting at any time.

Referring now to operation 774, the completed ballots are counted by the server 160. In an embodiment, the server may generate a summary of the vote. By way of example, the summary may include the vote totals for each of the selections, who voted for each option, who did not vote, or any other available information that the vote originator may want to obtain. Thereafter, the summary may be delivered to the smart ID 120 that is used by the vote originator over the smart ID network 100, as shown in operation 775. According to an additional embodiment, the summary may also be delivered to one or more of the smart IDs 120 that participated in the vote.

An additional embodiment includes the use of one or more public displays to further enhance the functionality of the smart IDs and the smart ID network. Instead of displaying information received from the server on a display incorporated into the smart ID, embodiments allow for the information from the server to be displayed on public displays that are proximately located to the smart ID. Accordingly, the smart ID does not need a display, or the display does not need to be used as frequently. Since the display typically consumes the most power in the smart ID, limiting the use of the display, or removing the display, allows for an increase in the battery life of the smart ID.

Referring now to Figure 8, a portion of a room 880 that includes a public display 896 that is communicatively coupled to a smart ID network is illustrated, according to an

embodiment. As illustrated, the public display 896 may be located on a wall 882 of a room 880. For example, the display may be an LCD, an LED display, an OLED display, a projection from a projector, or any other display technology. Embodiments may also include a public display 896 that is located on the walls in hallways, on tables, glass, or any other location where a display may be integrated.

In an embodiment, when the server 160 (not show) determines that a smart ID 120 is proximately located to a public display 896, information that would be delivered from the server 160 to the smart ID 120 (e.g., public profiles, schedules, behavior reminders, maps, or the like) may be redirected to the proximately located public display 896. In an embodiment, a smart ID 120 and a public display 896 may be proximately located with each other when the smart ID 120 is within the same room as the public display 896. A proximate relationship may also be based on a physical separation between the smart ID 120 and the public display 896. For example, a physical separation of less than approximately ten feet between the smart ID 120 and the public display 896 may be considered a proximate relationship.

In an embodiment, the public display 896 may be shared by two or more smart IDs 120. In the exemplary embodiment illustrated in Figure 8, a first smart ID 120₁ is held by a first user 819i, and a second smart ID 120₂ is held by a second user 819₂. Further, both the first smart ID 120i and the second smart ID 120₂ are proximately located to the public display 896.

Accordingly, embodiments allow for information that is intended for the first user 819i to be displayed on a first portion of the public display 895A, and information intended for the second user 819₂ may be displayed on a second portion of the public display 895B -

According to an additional embodiment , a smart ID user 819 may not want their information displayed on a public display 896. For example, a meeting reminder may be for a private meeting. In such embodiments, public display 896 may only display information received from the server when the user of the smart ID user 819 authorizes the display of the information. For example, the user may authorize the display of information on a public display 896 by entering a password on the smart ID 120. In an embodiment, the password may be based on a biometric sensor that only the user 819 assigned to the smart ID 120 may activate. For example, a fingerprint scan may be implemented through a designated finger print sensor 247 located on the smart ID 120, or through a fingerprint scan on a touchscreen display 210. Additional biometric sensors 247, such as voice recognition through a microphone or a retinal scan with a camera, may be used to authorize the display of information on a public display 896. In an embodiment, the password may be a gesture based password detected via a camera, an accelerometer, or a gyroscope.

According to additional embodiments , the smart ID network 100 may also be used for reality mining. As used herein, reality mining may include the collection, storage, and/ or manipulation of data obtained from the smart ID network 100. As described above, the smart ID network may allow for the location of the smart IDs 120 to be determined when they are connected to the smart ID network 100. Accordingly, in addition to using the location

information for profile sharing, mapping, voting, and other processes described herein, embodiments include accumulating and storing the location information. By way of example, the location information may be stored in a memory on the server 160, or on an external storage device accessible to the server 160.

The stored location information may be analyzed to determine various patterns and behaviors that occur in the workplace. By way of example, and not by way of limitation, the stored location information may be used to determine when the employees get to the office, how often they use the break room, which persons interact with each other frequently, which meeting rooms are used most often, at what times the meeting rooms are used most often, and the like.

Additional embodiments allow for the stored location data to be used to quantify social experiments. For example, it may be desirable to have employees eat in a common area (e.g., a break room or a cafeteria) in order to spur social interaction, brainstorming, or other

collaborative behaviors. As such, a social experiment may be implemented to see if certain incentives will cause more people to eat in the common area. In an exemplary social experiment, the enterprise may provide free sodas in the common area and monitor the difference between behavior before the free sodas were provided and after the free sodas were provide.

Reality mining using data acquired according to embodiments described herein allows for improved analysis. For example, without the recorded location information, the consumption of the sodas may indicate that the sodas were causing more employees to visit the common area. However, monitoring the consumption of the sodas alone would not account for individuals who took one of the sodas and left the common area before drinking the soda. In contrast, location information provided according to embodiments described herein indicate how long an individual stayed in the common area. Accordingly, if the average time individuals spent in the common area increased, as a result of providing free sodas, it would indicate that the goal was being achieved. In contrast, if the average time individuals spent in the common area decreased, then it may indicate that people were visiting the common area to take a free soda and then they left shortly thereafter.

It is noted that the social experiment described above is exemplary in nature, and is not intended to be a limiting example. Many different experiments may benefit from the collection of location data according to embodiments described herein. For example, a social experiment may be implemented by following one or more operations. Figure 9 illustrates a flow chart that shows several processing operations that may be executed by the server 160 to implement a social experiment, according to an embodiment.

Referring now to operation 970, the server 160 may obtain a set of smart ID data from a first test condition. According to an embodiment the first set of smart ID data may include location information of a plurality of smart IDs 120, settings from a plurality of smart IDs 120, or the like. For example, with respect to the free soda in the common area experiment described above, the first set of smart ID data may be the average time each end user spent in the breakroom before free sodas were made available to the end users.

Referring now to operation 971, the server 160 may obtain a set of smart ID data from a second test condition. In an embodiment, the set of smart ID data from the second test condition may be the same type of data after a variable has been changed. For example, the variable that is changed for the second test condition may be the introduction of the free sodas in the break room.

Thereafter, the process may proceed to operation 972, and the server 160 may compare the sets of smart ID data obtained under the first and second test conditions. For example, a change in the average amount of time each end user spent in the common area may be determined.

Furthermore, while embodiments described above are set in an organizational or business environment, the benefits obtained from the use of smart IDs are not limited to such

In an embodiment, a smart ID network 100 may be utilized in an educational

environment. For example, the profile sharing features may allow children who are not friends an opportunity to get to know each other. By way of example, the public profile may be tailored to include additional person information items that are pertinent to the educational environment, such as, for example, who their teachers are, which classes they are taking, grade level, favorite subjects, or the like.

Additional embodiments may utilize the voting feature described above to aid classroom discussions. For example, a teacher may be the vote originator, and the vote parameters may include a list of possible answers to a question asked by the teacher. In such an embodiment, the students may then answer the question by submitting their ballots over the smart ID network 100. Upon receiving the results, the teacher may see that a large percentage of the students have answered correctly, and the teacher may feel comfortable moving on to the next subject.

Additionally, embodiments may allow parents to schedule behavioral reminders for their children. By way of example, and not by way of limitation, the reminders may remind the child to pay attention to the teacher, remind the child to call the parent when school is over, remind the child that they are taking the bus home from school, or the like.

In an embodiment, the tracking settings described above may be controlled by a parent of the student using the smart ID, or by the administrators of the school. As such, the student may not be able to turn off or alter the tracking capabilities, as described above. The ability to track a student allows administrators and parents to see the daily behaviors of a student. The knowledge that a parent or an administrator knows where the student is going during the day may deter the student from showing up late to class or leaving the classroom excessively during class time. Additional embodiments may include using the tracking settings to perform social experiments, such as those described above. For example, the tracking of the students through the smart ID networks may be combined with test scores and/or grade point averages to see if any correlation can be found between the behavior of the students and the test scores and/or grade point averages. If a correlation is found, new programs or rules may be implemented by the school that encourage the behavior that was linked to better test scores and/or grade point averages.

In an additional embodiment, the smart ID network may be used for tourism. The smart ID network 100 described above may be modified to allow for the user of a smart ID 120 to be guided on a tour, according to an embodiment. For example, the mapping functionality described above may be useful for guiding an individual to points of interest. Points of interest may include historical landmarks, famous buildings, scenic views, or the like. Embodiments may also include a public profile that is associated with each of the points of interest. Accordingly, when a user of a smart ID 120 is proximate to the point of interest, the public profile that corresponds to the point of interest may be displayed on the display 210 of the user's smart ID 120. For example, the public profile associated with the point of interest may include the name of the point of interest, historical facts about the point of interest, famous persons associated with the point of interest, or the like.

The points of interest may also be associated with commercial enterprises (i.e., business such as restaurants, stores, etc.). In such embodiments, the owner of the commercial enterprise may include a coupon in the public profile. For example, the coupon may be a buy one get one free coupon, a discount coupon, or the like. The inclusion of a coupon in the public profile for the commercial enterprise may be used to entice visitors to enter the commercial enterprise and spend money. In some embodiments, the coupon included in the public profile may be tailored to the history of the smart ID 120. For example, if a smart ID 120 had been recorded as being at a restaurant within the past hour, then the coupon may be tailored to deliver a discount on a dessert or a coffee since it is likely that the user of the smart ID 120 had just finished a meal.

In an additional embodiment, the smart ID network 100 may also be utilized in an entertainment environment. In one example, the smart ID network 100 may be used in a treasure hunting game. In such an embodiment, a plurality of participants in a game may be issued a smart ID 120. A plurality of checkpoints may be dispersed over an area within the smart ID network 100. The checkpoints may each have a public profile that contains a clue to the next checkpoint. When a smart ID 120 is proximately located to the checkpoint the public profile displaying the clue may be displayed on the user's smart ID. Once all of the checkpoints have been found by a user, the game may end. Such embodiments may utilize a larger sized network than those used in a business environment. For example, the network may be a wilderness area, a town, or a larger geographic region. As such, the smart ID network 100 may be a cellular network.

In an embodiment, the use of a smart ID 120 in a smart ID network 100 in a tourism or entertainment embodiment, such as those described above, may be implemented by following one or more operations. Figure 10 illustrates a flow chart that shows several processing operations that may be implemented by the server 160 according to an embodiment.

Referring now to operation 1070, the server may obtain the location of a smart ID 120. For example, the server 160 may send a request to the smart ID 120 that instructs the smart ID 120 to report to the server 160 its current location obtained from the GPS unit 246.

Additional embodiments include using the access points 140 to determine the location of a smart ID 120. For example, the signal strength from an access point 140 may be used to determine the distance from the access point 140. In embodiments with a plurality of access points 140, the signal strength from two or more of the access points 140 may be used to triangulate the location of the smart ID 120.

Additional embodiments may utilize a system of RFID readers to monitor the position of the smart ID 120. For example, the RFID readers may be located throughout a city, a museum, a mall, or the like, and are each connected to the smart ID network 100. As a smart ID 120 passes by the RFID reader, the RFID reader is triggered and the RFID tag 231 in the smart ID 120 is read to determine the identity of the smart ID 120. The RFID reader may then send a signal to the server 160 that instructs the server to update the location of the smart ID 120 that triggered the RFID reader to the location of the triggered RFID reader.

Referring now to operation 1071, the server determines if the smart ID 120 is proximately located to a destination that is associated with a public profile. For example, the destination may be a point of interest or a checkpoint, similar to those described above.

Referring now to operation 1072, the server may deliver public profile information associated with the destination to the smart ID 120 over the smart ID network 100 when the smart ID 120 is proximately located to the destination. In an embodiment, the public profile information delivered to the first smart ID 120 may be displayed on the display 210 of the smart ID 120. As such, the person using the smart ID 120 is provided with some information about the destination to which they are proximately located. For example, the public profile information may include information about the destination, a coupon for services or goods at the destination, or a clue to find a second destination, as is described above.

Claims

CLAIMS What is claimed is:

1. A non-transitory computer readable medium comprising instructions which, when executed by one or more hardware processors, causes performance of operations, comprising: determining a physical location of a first smart identification (ID) that is

communicatively coupled to a smart ID network;

determining if a second smart ID that is communicatively couple to the smart ID network is proximately located to the first smart ID; and

delivering public profile information associated with the first smart ID to the second smart ID over the smart ID network and delivering public profile information associated with the second smart ID to the first smart ID over the smart ID network when the second smart ID is proximately located to the first smart ID.

2. The non-transitory computer readable medium of claim 1, wherein the first smart ID comprises a global positioning system (GPS) and determining the physical location of the first smart ID comprises, receiving location information from the first smart ID obtained from the GPS.

3. The non-transitory computer readable medium of claim 1, wherein determining the physical location of the first smart ID comprises, triangulating the physical location of the first smart ID with a plurality of wireless access points communicatively coupled to the smart ID network.

4. The non-transitory computer readable medium of claim 1, wherein determining the physical location of the first smart ID comprises, receiving location information from a radio frequency identification (RFID) reader that is communicatively coupled to the smart ID network.

5. The non-transitory computer readable medium of claim 1, wherein the public profile information associated with the first and second smart IDs comprise a name of an end user assigned to the first and second smart IDs.

6. The non-transitory computer readable medium of claim 1, wherein the public profile information associated with the first and second smart IDs comprise one or more of, a job title of an end user assigned to the first and second smart IDs, a picture of an end user assigned to the first and second smart IDs, one or more hobbies of an end user assigned to the first and second smart IDs, and schedule information of an end user assigned to the first and second smart IDs.

7. The non-transitory computer readable medium of claim 1, wherein the second smart ID is proximately located to the first smart ID when the first smart ID and the second smart ID are located within the same room.

8. A smart identification (ID), comprising:

a processer;

a display electrically coupled to the processor;

a network interface for sending and receiving data over a network; and

one or more sensors electrically coupled to the processor, wherein the one or more sensors control a switch for disabling the network interface.

9. The smart ID of claim 8, wherein the switch is operable after a password is detected by the one or more sensors.

10. The smart ID of claim 9, wherein at least one of the sensors is a biometric sensor.

11. The smart ID of claim 10, wherein the biometric sensor is a fingerprint scanner, voice recognition scanner, or retinal scanner.

12. The smart ID of claim 9, wherein the password is based on a gesture.

13. The smart ID of claim 12, wherein the gesture is detected by one or more of an accelerometer, a gyroscope, or a camera.

14. The smart ID of claim 8, further comprising a radio frequency identification (RFID) tag.

15. The smart ID of claim 14, wherein the RFID tag comprises one or more permissions that allows entrance into a facility.