text: fig1 is a schematic diagram of a system 100 for automatically sharing profile information between devices in accordance with an embodiment of the inventive arrangements disclosed herein . more specifically , system 100 can include two computing devices 110 and 140 , each of which includes a profile handling agent 120 and 144 , respectively . each profile handling agent 120 and 144 can include a profile for a device user , which provides some identifying information concerning that person , which can be configured by that person in any manner he or she desires . when devices 120 and 140 are within a communication range of each other , such as within a bluetooth range , profiling information can be automatically shared . the receiving device 110 and / or 140 can compare the received information against a set of contact rules 128 and can selectively execute a communication based upon this comparison . a contact action can be an action designed to facilitate an interpersonal collaboration between device owners , who may not have previously met . as shown in system 100 , computing device 110 an computing device 140 can each be a consumer electronic device , such as a mobile telephone or personal data assistant ( pda ), upon which a profile handling agent 120 and 144 is loaded . each communication device 110 and 140 can also include a number of components , such as components 112 - 116 and 142 . the components for each device 110 and 140 can differ from each other . for example , device 110 can be a mobile telephone and device 140 can be a handheld entertainment system . both devices 110 and 140 can share an ability to communicate over one or more communication channels 152 - 156 , including an interrogation channel 152 , a data exchange channel 154 , and an interaction channel 156 . depending on implementation specifies used in system 100 , the different channels 152 - 156 can use the same communication protocols as other channels 152 - 156 or can use different , channel specific communication protocols . the interrogation channel 152 can be used to send availability , acknowledgement , and authorization data between profile - sharing devices . for example , interrogation channel 152 can be used by computing devices 110 and / or 140 to announce a profile sharing capability to each other . unlike other communication channels , such as channels 154 and / or 156 , which can permit encrypted or secure communications , the interrogation channel 152 will generally be an open or unencrypted channel . additionally , the interrogation channel 152 can have a more restricted range than other channels 154 and / or 156 . this restricted range can ensure that profile sharing only occurs between people located near each other . the restricted range can be a user configurable software - based limitation and / or a hardware limitation , such as a range of bluetooth based communication . in situations where profile sharing between devices 110 and / or 140 is restricted , identification information , certification information , and / or authorization information can be conveyed over the interrogation channel 152 before profile sharing occurs . the data exchange channel 154 can be an infuriation sharing channel used to convey profiling and other information between devices 110 and / or 140 . in one embodiment , profile information exchanged between devices 110 and 140 over channel 154 can be protected to prevent potential information abuses . for example , conveyed profile information can be configured to automatically expire after an owner - established duration . in another example , access rights for content within a conveyed profile can be restricted for use by profile handling agents only . other applications can be prevented from viewing this information , unless explicit permission is granted by an information conveyer . this protection can be implemented using encryption technologies , proprietary data formatting , secure data conveyance standards , and the like . in one arrangement , the profiling data exchanged over channel 154 can be segmented into different granularity levels , such as an overview level , a detailed level , and a secure level . access to different levels can require authorization . when a commonality exists between device users , as determined by agents 120 and / or 144 , additional information , such as information contained in a lower granularity level of a profile , concerning that interest can be requested and conveyed over channel 154 . for example , a profile overview conveyed from device 110 to 140 can indicate that a user of device 110 plays chess as a hobby . rules in device 140 can cause the device to determine more information , such as an elo rating to determine if the users of devices 110 - 140 have compatible skills . further queries to determine resident applications on the devices 110 and 140 can be conducted to determine if it would be possible for users of the devices 110 and 140 to interactively , engage in a chess game using software loaded on devices 110 and 140 . if so , a notification can be generated to inform users of devices 110 and / or 140 of the common interest in chess . the notification can specify the respective elo rank of each player , can propose a time for playing a game , and / or can indicate that a game can be played using a pre - existing chess application already loaded on the devices 110 and 140 . the additional information exchanged between devices 110 and 140 can be conducted via a user - device communication mode and / or an automated communication mode . the user - device communication mode and the automated communication mode can each result in an exchange of information over channels 152 and / or 154 . the automated communication mode can be a device - to - device information exchange mode with little to no user interaction between users and devices where queries are automatically constructed and information provided based upon the previously configured rules 128 . the user - device communication mode can be a mode where one of the users interacts with a device 110 or 140 via a user - device interface , where the interactions can result in user - directed information exchanges between devices 110 and 140 . the user - device communication mode permits device - to - device information exchanges and device - to - user interactions . in one example , a user utilizing device 110 in the user - device communication mode can direct device 110 to provide a top five potential contact opportunities with nearby users . further interactive inquiries can be used to aid the user to determine , which , if any , of these opportunities should be pursued . for instance , the top five potential contact opportunities can be presented with a brief description of opportunity specifics . one of the opportunities can specify a shared hobby of chess exists with a nearby person . in the user - device communication mode , the user can further query for an age , gender , name , and elo ranking of this nearby chess player . the user for whom queries are directed is not directly contacted until an explicit decision to do so is made . this user may not be aware of the data exchanges resulting from another user interacting in the user - device communication mode . therefore , if the first user only prefers to play chess with adults and discovers that the nearby chess player is a child , the first user can choose to ignore the potential contact opportunity without ever having explicitly initiated contact with the nearby chess - playing youngster . the interaction channel 156 can be used to permit users to interact or communicate with each other via their devices 110 and 140 . interaction channel 156 can permit telephone interactions , text - messaging , chatting , instant messaging , email , electronic - document sharing , co - browsing , interactive gaming , and any other form of interactive communication , which can depend upon capabilities of the respective devices 110 and 140 . turning to specifics of device 110 , communication components 112 can exist which enable communications with other devices , such as device 140 . the communication components 112 can be capable of different communication modes , such as telephone mode , an instant messaging mode , a direct data exchange mode , and the like . one of the communication modes can enable direct peer - to - peer communications ( e . g . bluetooth communications ). another of the communication modes can enable server - assisted communications ( e . g . mobile telephony communications ). the application components 114 on a computing device 110 can be used to facilitate interactions and / or to store profile data in an organized fashion . for example , the application components 114 can include an email program or text messaging program , both of which can be used to communicate over channel 156 . application components 114 can also include a contact management application , and scheduling application , and the like . the contact management application can , in one illustrative instance , directly upload profile information from device 140 . the scheduling application can be integrated with the contact rules 128 so that contact actions can depend upon a schedule of a device 110 owner . interface components 116 of devices 110 can permit a user to interface with the device 110 . common interfaces include voice interfaces , text interfaces , graphical user interfaces , and the like . interfaces components 116 can utilize peripherals attached to or integrated with the computing device 110 . the profile handling agent 120 can include machine readable instructions encoded in software / hardware / firmware capable of being understood by computing device 110 . these instructions can allow profile sharing to occur , as described herein . the agent 120 can include an administration module 122 , a broadcast module 124 , a receiver module 126 , a contact rules module 128 , a security module 130 , a proxy agent module 132 , a link agent module 134 , a storage module 136 , and the like . the administration module 122 can permit a user to configure the profile handling agent 120 and to selectively enable profiles . multiple profiles can exist , such as a business profile , a family and a friend &# 39 ; s profile , and a dating profile , which can be activated under different conditions that can be specified using administration module 122 . for example , a business profile can be activated monday through friday from nine am to six pm , a family profile can be activated monday through friday after six pm and a dating profile can be activated saturdays between six pm and midnight . activation conditions are not restricted to time windows and other conditions can be specified . the broadcast module 124 can handle details for broadcasting profile data to other computing devices , such as device 140 . for example , the broadcast module 124 can establish different granularity levels for profiles , broadcast conditions , security rights for broadcasting profiles , profile expiration times , broadcast protocols , broadcast range , and the like . similar functions and features for receiving profile data from other devices can be handled by the receiver module 126 . the contact rules module 128 can dictate when contact based upon shared profile data should be initiated and / or when notifications concerning potential contacts are to be provided . contact rules module 128 can also state what contact actions , if any , are to be taken . the contact rules module 128 can establish various thresholds , factors , and values , which are used to determine desired responses for different contact opportunities . for example , contact rules module 128 can classify different contact opportunities as critical , important , moderate , unimportant , and disfavored . a user &# 39 ; s current status can be classified as frantic , busy , average , and slow . a rules can state that when an opportunity is important and when a user &# 39 ; s status is average or less , that the user is to be notified immediately of the contact opportunity . a different rule can establish that when an opportunity is of moderate importance and when the user is busy or greater , then contact information for a potential contact is to be stored and that a message is to be automatically conveyed indicating to the profile conveying party that contact is desired , but that the current individual is presently occupied . security module 130 can handle security functions and features for agent 120 . communication channel encryption techniques , file encryption techniques , authorization codes usage , exchanged certificates , and the like can all be used by the security module 130 . the security module 130 can establish access rights and / or expiration conditions on transmitted profile data . security can exist for conveyed profile data and for received profile data . for example , received profile information can be scanned for malicious content , such as viruses or spyware . any suspicious content can be discarded and / or quarantined . firewall procedures can also be instituted to prevent unauthorized automated data exchanges . for example , a user can be a member of a profile sharing network or service and profile sharing can be restricted to other members of the same network or service . in another example , a conference can permit profile sharing among paying participants , where guests are denied this ability . sharing restrictions and permissions can be enabled by requiring devices 110 and 140 to possess a private / public key in order to participate in a particular profile sharing service or group . the proxy agent module 132 can act as a proxy for another device , when permitted by the device 110 owner . for example , device 140 can request that device 110 be a proxy for device 140 . if the proxy request is accepted , all profile - based communications of device 140 can pass through device 110 , until the proxy feature is disabled . profile - based communications associated with device 140 and / or a user of device 140 will be based upon specifies of profile handling agent 144 and not profile handling agent 120 . the use of the proxy agent module 132 can be particularly useful in situations where a user does not want to disclose his or her identity . the linked agent 134 can be used to create virtual cooperative networks or ad hoc networks between multiple computing devices , thereby extending an effecting communication range of the devices . for example , devices 110 and 140 can be outside of a wireless broadcasting range of each other , but can both be within a communication range of a third device ( not shown ). a virtual cooperative network can be established between the three devices , permitting the third device to route information between devices 110 and 140 . the storage module 136 can manage specifies related to storage . the storage module 136 can determine a time period for which messages can be stored when communications are intermittent or fail for a period of time . for example , a user communicating with device 110 who is near the outer communication range of device 110 can intermittently exchange information . the storage module 136 can establish criteria for which information is stored in case the recipient comes back within range , at which point , stored messages can be conveyed . the storage module 136 can also determine criteria for deleting and / or saving external profile information sent to device 110 . the criteria can be established by a user receiving the profile information and / or by the user sending the information . for example , a time based criteria can be established to delete all profile information after thirty minutes of receiving the information unless a communication was explicity established with a user for whom the profile information relates . it should be appreciated that the device components 142 of device 140 can be similar to components 112 - 116 of device 110 . the components 142 can also vary significantly from components 112 - 116 , so long as at both devices 110 and 140 include compatible profile handling agents 120 and 144 and are both capable of sharing profiles over channels 152 - 156 . fig2 is a schematic diagram showing a profile sharing computing system 200 in accordance with an embodiment of the inventive arrangements disclosed herein . system 200 can include a computing device 210 and a computing device 220 , which share profile 260 data directly via network 250 . profile sharing functions can be handled by profile handling agents 219 and / or 222 . the profile handling agents 219 and 222 can be implemented as a software / firmware module , as a local stand - alone application , as a remotely called application , as a web service , as a plug - in , as an applet , and the like . network 250 can include wireless and / or line - based communication pathways , which permit data to be exchanged directly between devices 210 and / or 220 . network 250 can utilize any of a variety of protocols and / or standards to exchange information . for example network 250 can use bluetooth , universal plug and play ( upnp ), an infrared data association ( irda ) protocol , and ieee 802 . 11 protocol , and other wireless protocols to share profile 260 data . network 250 can also use line - based connections and protocols including , but not limited to , universal serial buss ( usb ), firewire , a laplink connection , an ethernet crossover connection , and the like . computing devices 210 and 220 can be any device , mobile or otherwise , capable sharing profile information . computing devices 210 and 220 can , for example , include a mobile phone , a personal data assistant ( pda ), a media player , an entertainment system , a tablet computer , a wearable computer , notebook , an embedded computing system , a desktop computer , a handheld navigation device , and the like . each computing device 210 and / or 220 can include a variety of hardware components , such as transceiver 211 , processor 212 , display 213 , keypad 214 , audio transducer 215 , data storage 216 , and / or location beacon 217 . transceiver 211 can be any communications device capable of both transmitting and receiving data . multiple different transceivers 211 can be included in each computing device 210 and 220 . for example , transceivers 211 for bluetooth , usb , and 802 . 11 protocol , ethernet , firewire , mobile telephony communications , two way radio communications , and the like can be included in device 210 . the processor 212 can be an electronic computer central processing unit ( cpu ) that performs processing operations for device 210 . the processor 212 can be connected to a circuit board ( not shown ), power supply ( not shown ), and other electronic components . the display 213 can include a screen upon which text and / or graphics can be presented . the keypad 214 can include a number pad , a keyboard , and the like . audio transducer 211 can be a device that converts one form of energy into another form of energy , such as converting sound to electrical impluses ( acting as a microphone ) and / or converting electrical impulses to sound ( acting as a speaker ). voice and / or audio interfaces can require audio transducer 215 as well as speech processing components ( not shown ). other peripherals ( not shown ), such as a mouse , pointer , touchpad , biometric sensor , camera , and the like , can be included in computer device 210 . data storage 216 can be used to store profile handling agent 219 , profile information , contact rules , contact actions , and the like . data storage 216 can include any type of information store including , but not limited to , a magnetic disk , an optical disk , a semiconductor memory , a digitally encoded plastic memory , a holographic memory , or any other recording medium . the data storage 216 can be a local store or a networked storage space . information contained in storage 216 can be stored within a database structure or can be stored within one or more files of a file storage system , where each file may or may not be indexed for information searching purposes . data storage 216 can utilize one or more encryption mechanisms to protect stored information from unauthorized access . the location beacon 217 can be include a device tracking component such as a radio frequency identification ( rfid ) tag and / or a global positioning system ( gps ) component . the location beacon 217 can be used to determine absolute or relative coordinates of device 210 . in one embodiment a location from beacon 217 can be combined with mapping data to guide a user of device 210 to a location of profile sharing device 220 ( assuming that an interpersonal contact is desired ). in system 200 , computing devices 210 and 220 can also be communicatively , linked to network 252 to which contact server 230 and certification server 240 can be connected . computing devices 210 and 220 call convey information between each other including profile 260 data , using network 252 . communications over network 252 will normally be based upon internet protocol ( ip ) and / or telephony protocols . network 252 can include any hardware / software / and firmware necessary to convey data encoded within carrier waves . data can be contained within analog or digital signals and conveyed though data or voice channels . network 252 can include local components and data pathways necessary for communications to be exchanged among computing device components and between integrated device components and peripheral devices . network 252 can also include network equipment such as routers , data lines , hubs , and intermediary servers which together form a data network , such as the internet . network 252 can also include circuit - based communication components and mobile communication components , such as telephony switches , modems , cellular communication towers , and the like . network 252 can include line based and / or wireless communication pathways . the contact server 230 can optionally provide supplemental information that facilitates interactions and / or profile sharing between computing device 210 and / or 220 . it should be emphasized that the contact server 230 is not necessary for the operation of system 200 and that direct peer - to - peer communications between devices 210 - 220 can be performed without server 230 . in one embodiment , the contact server 230 can include an email server , an instant messaging server , a chat server , a telephony server , and the like , which can be involved in establishing or maintaining interactive communications between devices 210 and 220 . the contact server 230 can connect either device 210 and / or 220 to a networked resource , such as a web site , which can host interactive games , co - browsing sessions , teleconferencing sessions , and the like for devices 210 and / or 220 . the contact server 230 can permit data exchanged between devices 210 and 220 to be remotely stored or accessed via remotely located resources which can be extremely , beneficial for when either device 210 and / or 220 is a mobile device with limited computing resources . for example , a profile - sharing occurrence can result in a business meetings being established between users of the devices 210 and 220 , where an owner of device 220 is going to present material in a slide - show format . a slide - show file can be conveyed from device 220 to device 210 before the meeting . device 210 can be unable to directly , access ( or even store ) the content of the slide - show file . profile handling agent 219 can , recognizing the limitations of device 210 , convey the slide - show file to contact server 230 , which can be a desktop computer accessible by a user of device 210 . a remote viewing client ( e . g . citrix ) can permit device 210 to view open and view the slide - show file , which uses an application residing on the desktop computer . thus , contact server 230 can be used in conjunction with computing device 210 to overcome resource limitations of device 210 . in still another embodiment , contact server 230 can further include a range - extension server that increases a range over which computing devices 210 and / or 220 can share information . for example the devices can typically share profile information via bluetooth transmissions , which limit transmission range to approximately thirty feet . a range - extension server can accept , repeat , and / or receive wireless network communications , such as 802 . 11 protocol communications , from devices 210 and / or 220 , thereby permitting profile data to be shared up to a range of the wireless network . certification server 240 can be optionally used to establish certified , secure , verified and / or private networks for profile sharing . the certification server 240 can be one of many security components involved in system 200 to prevent abuses , such as identity theft , from occurring as a result of profile sharing . additionally , certification server 240 can be used to verify that information contained in a profile is accurate . for example , the certification server 240 can check tax records , address records , business records , professional licenses , and the like to ensure that a name , address , occupation , salary , and other information in a profile is accurate and not fictitious . use of this verification function of the server 240 can prevent users from masquerading as others . special identifiers can be presented upon display 213 to indicate when server 240 has verified a user &# 39 ; s profile information or when the profile information is not able to be verified . fig3 is an illustration showing a plurality of individuals in a profile - sharing environment 300 in accordance with an embodiment of the inventive arrangements disclosed herein . each person 341 - 349 in environment 300 can carry a computing device with a profiling agent , as described in system 100 and / or 200 . each device can have a communication range 351 - 359 within which profile data can be wirelessly exchanged using peer - to - peer communications ( e . g . by bluetooth or other wireless communication means ). a contact server 322 can be an optional component of environment 300 that is able to establish a communication range 324 for all people 341 - 344 in building 320 ( e . g . using 802 . 11 based wireless networking technologies ). peer - to - peer communications between devices are still available using appropriate transceivers ( e . g ., bluetooth ) without using capabilities of server 322 , even when devices are within range 324 . the range 324 is a hardware limited range , and shorter , software limited ranges can be established by contact server 322 and / or individual computing devices . for example , person 341 and person 342 can establish a software defined range of “ one floor ” for profile sharing purposes . accordingly , person 341 and 342 can share profile information with each other ( although both are outside peer - to - peer ranges 351 and 352 ) with the assistance of server 322 . neither person 341 and / or 342 can share profile information with people 343 and / or 344 on different floors due to the software established range limitation . if a software range limitation , were extended to include a current and an adjacent floor , person 343 could share profiling information with persons 341 , 342 , and 344 , but person 344 would be unable to share profile information with person 341 or 342 . in one embodiment , a series of personal area networks can interact to form a virtual cooperative network , thereby extending a profile sharing range . for example , overlapping ranges 355 - 358 can form a virtual cooperative network having an area of the combined ranges , which allows person 345 to share profile information with person 348 . hence , profile sharing devices of person 346 and 347 can automatically relay information conveyed between person 345 and 348 . further , a temporary profile cache can be maintained in computing devices for a short period , permitting dynamic profile sharing in a time delayed fashion . for example , person 349 can have recently left building 320 and can have a profile cache containing profile data for persons 341 - 344 which was conveyed to the device , when the device was within range 324 . when person 349 is within range 359 of person 345 , the temporary profile cache information can be conveyed to person 345 , informing person 345 of potential contact opportunities with people 341 - 344 based upon cached content transferred from a device of person 349 . moreover , contact desires and profile information associated with person 345 can be conveyed to profile caches included in devices of people 346 - 348 . when any of the people 346 - 348 enter range 324 , this cached content from person 345 can be conveyed to people 341 - 344 . fig4 is a flow chart of a method 400 for sharing profile information between computing devices in accordance with an embodiment of the inventive arrangements disclosed herein . method 400 can be performed in the context of a system 100 , 200 , or any system capable enabled to permit profile sharing . method 400 can begin in step 405 , where a profile containing user specific information can be stored in a first computing device . the computing device can be a mobile device and the profile data can be user configurable . in step 410 , data in the stored profile can be wirelessly broadcasted to other devices in a broadcast range . the broadcast range can be determined by hardware and / or software established limits . the broadcast can convey data directly using a peer - to - peer communication , such as a bluetooth based communication . in step 415 , one of the devices can receive the profile data . this device can be referred to as a second computing device , which can also be mobile computing device . in step 420 , the second device can compare the received data against a set of previously established contact rules , which can be user configured . if the rules determine that contact is not desired , then the second device can disregard the received profile data and the method can end in step 425 . if the rules indicate that contact is desire , then the method can progress from step 420 to step 430 , where the second device can automatically determine at least one contact action to take . contact actions can be user configurable actions established by the contact rules . in step 435 , the determined contact action can automatically execute . in step 440 , a contact action can indicate that contact information from the profile should be stored for later use and that an immediate contact is not appropriate at this time . in step 445 , the contact action can indicate that an immediate interpersonal contact is desired . towards this end , a message indicating a contact desire can be conveyed from the second device to the first device . all steps up to now ( steps 405 - 445 ) can be automated steps not requiring user attention or interactions . in step 450 , the first device can notify a user of the desired contact . this notification can include a contact purpose and a contact means , which can be ascertained from information conveyed from the second device . the user of the first device can choose to ignore the notification or to act upon it . in step 455 , the user can choose to initiate an interpersonal communication with the owner of the second device . for example , the first device can dial a telephone number of the second device or a text message can be conveyed from the first to the second device . in step 460 , the user of the second device can be alerted to the interpersonal contact attempt ( e . g . the second device can ring or a text message can be received ). the user of the second device can then choose to accept the interpersonal communication . before the interpersonal contact is established , both communicators can be aware of the shared common interest and of the purpose of the communication . fig5 is a flow chart of a method 500 , where a service agent can configure a system or device that permits profile sharing in accordance with an embodiment of the inventive arrangements disclosed herein . method 500 can be preformed in the context of system 100 , 200 , or method 400 . method 500 can begin in step 505 , when a customer initiates a service request . the service request can be a request for a service agent to add a profile handling agent upon one or more computing device for a customer . the request can also be a request to configure contact rules upon any of these devices . the request can also be to integrate profile sharing capabilities into one or more different applications , such as permitting calendaring application to provide availability information that is used by computing devices when sharing profile information . requests can also be to add remote - server capabilities , such as profile certification or verification capabilities to an existing profile sharing system . in step 510 , a human agent can be selected to respond to the service request . in step 515 , the human agent can analyze a customer &# 39 ; s current system or device and can develop a solution . in step 520 , the human agent can configure the client system or device so that the system is part of and / or communicatively linked to a profile sharing system . for example , the human agent can and business owned communication devices to a private profile sharing “ network ”. in another example , the human agent can troubleshoot a problem with an existing profile sharing system and / or can add new customer desire features to an existing profile sharing system . in step 525 , the human agent can complete the service activities . it should be noted that while the human agent may physically travel to a location local to adjust the customer &# 39 ; s computer or application server , physical travel may be unnecessary . for example the human agent can use a remote agent to remotely manipulate the customer &# 39 ; s computer system . the present invention may be realized in hardware , software , or a combination of hardware and software . the present invention may be realized in a centralized fashion in one computer system or in a distributed fashion where different elements are spread across several interconnected computer systems . any kind of computer system or other apparatus adapted for carrying out the methods described herein is suited . a typical combination of hardware and software may be a general purpose computer system with a computer program that , when being loaded and executed , controls the computer system such that it carries out the methods described herein . the present invention also may be embedded in a computer program product , which comprises all the features enabling the implementation of the methods described herein , and which when loaded in a computer system is able to carry out these methods . computer program in the present context means any expression , in any language , code or notation , of a set of instructions intended to cause a system having an information processing capability to perform a particular function either directly or after either or both of the following : a ) conversion to another language , code or notation ; b ) reproduction in a different material form . this invention may be embodied in other forms without departing from the spirit or essential attributes thereof . accordingly , reference should be made to the following claims , rather than to the foregoing specification , as indicating the scope of the invention .