This invention relates generally to networked devices, and more particularly to the initiation of relationships between devices.
A portion of the disclosure of this patent document contains material, which is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure as it appears in the Patent and Trademark Office patent file or records, but otherwise reserves all copyright rights whatsoever. The following notice applies to the software and data as described below and in the drawings hereto: Copyright © 2002, Sony Electronics, Inc., All Rights Reserved.
The Internet has created the ability for many new types of virtual communities. Online communities exist for all sorts of reasons, including; product reviews, shared interests, socialization and the selling or auctioning of goods and services to name a few. These services are currently centralized, server-based services. Being centralized (e.g., hosted on a single server or group of servers) makes it easy for the service to poll the activity level and generate reports or displays of the current community status and activity. In contrast, a decentralized service does not provide for a service to generate reports and display decentralized information as with the centralized service.
Persona information is exchanged between devices in a network. Based upon the persona information, a user of a device may initiate a relationship with another device.
In the following detailed description of embodiments of the invention, reference is made to the accompanying drawings in which like references indicate similar elements, and in which is shown by way of illustration specific embodiments in which the invention may be practiced. These embodiments are described in sufficient detail to enable those skilled in the art to practice the invention, and it is to be understood that other embodiments may be utilized and that logical, mechanical, electrical, functional and other changes may be made without departing from the scope of the present invention. The following detailed description is, therefore, not to be taken in a limiting sense, and the scope of the present invention is defined only by the appended claims.
Each device also has the capability of identifying devices it would like to communicate or initiate a relationship with, to discover devices entering and leaving the network environment 100 (discovery process) and to determine what communications protocol is being used in the network environment 100. For example, communication between peer devices may be via a wire and/or wireless protocol, such as TCP/IP, Bluetooth, 802.11x protocols commonly referred to as WiFi (Wireless Fidelity) and WAP (Wireless Application Protocol), which are used to exchange data across mobile telephone networks, among other communication protocols well known in the art.
The devices 5, 10, 15, 20, 25, 30 and 35 may include mobile devices such as a personal digital assistance (PDA), a mobile phone, a portable computer, a pager and a portable music player (e.g., MP3 player), among other devices. Alternatively, the devices 5, 10, 15, 20, 25, 30 and 35 may include typical non-mobile devices, such as a desktop computer, a home entertainment system, a set-top box and a gaming system, among other examples. An exemplary embodiment of a suitable device is described below in conjunction with
It will be appreciated that the peer-to-peer network environment 100 illustrated in
Each device 5, 10, 15, 20, 25, 30 and 35 also includes relationship initiation software 50 that facilitates the creation, sharing, modifying and deletion of persona information, as will be described. Persona information may reflect the personality, behaviors, habits and personal interests of a user of each device. For example, the persona information for a user of a device may include a set of attributes such as an artist list, a song list, a favorite song list, a favorite artist list, rating of users, comments on songs, an interest list (e.g., vegetarian, chess player, etc.), among other attributes that relate to the user. Those of ordinary skill in the art will recognize that numerous attributes may be used and the invention is not limited to only those described herein.
In one embodiment, persona information associated with a user of a device is automatically collected. For example, a list of interests of a user of the device 5 may be automatically generated by recording the web sites, the user visits, the music the user listens to, the films the user watches, etc. The persona information may be stored as public and private persona information relating to the user of the device.
The relationship initiation software 50 on each device 5, 10, 15, 20, 25, 30 and 35 also allows the user of each device to initiate a relationship and store persona information from one or more of the other users of the devices on the network, as will be described. For example, a user may seek to initiate a relationship with another user by initiating a conversation (e.g., querying others for a restaurant recommendation, initiating an instant messaging session, etc.), to share digital content of common interest (e.g., music, poetry, literature, films, pictures, etc.), etc. Furthermore, depending on the type of relationship that is generated between the users, a level of trust may be built and visually displayed, as will be described.
It should also be understood that a relationship might be initiated by a user (e.g., a user determines whether to initiate an instant messaging session with another user on another device) or automatically by a device (e.g., a device automatically determines a musical piece to play based on a favorite list of another user having a common interest in music).
Although the description describes embodiments of the invention that use messages to communicate between the devices, it should be understood that messages as described herein may include numerous message configurations based on the communication protocol being used. Furthermore, those of ordinary skill in the art will recognize that other mechanisms may be used to initiate relationships that do not include messages and are not described herein as to not obscure the description.
A dotted line 202 in
At block 205, the device 5 generates an overview message. The overview message may include a subset or all of the persona information associated with the user of device 5. For example, the overview message may include personal interests of the user of device 5, such as being a chess player. The overview message may also include a query to the other users on the network. For example, the overview message may ask the other users on the network “Does anyone know of any nice vegetarian restaurants in San Francisco?”
At block 208, the device 5 broadcasts the overview message to the other devices on the network.
At block 210, the device 10 on the network 100 receives the overview message. Alternatively, it is understood that the overview message may be received by any one of the devices on the network 100. At block 215, the device 10 also analyzes the overview message. For example, the device 10 may analyze the overview message to determine areas of common interest with the user of device 5. The device 10 may also analyze the message to determine whether to answer the query. Based on the information included in the message the user of device 10 may decide to reply.
At block 217, the device 10 determines whether to reply to the overview message. If the device 10 determines not to reply to the overview message, control passes to block 218. If the device 10 determines to reply to the overview message, control passes to block 220.
At block 218, the device 10 does nothing in response to receiving the overview message and/or query. The device may automatically determine not to reply to the overview message based on the persona information received in the overview message. Alternatively, the user of the device 10 may not have an answer for the query.
At block 220, the device 10 generates a reply message and automatically replies directly to the device 5. The device 10 may reply directly with the device 5 based on an identifier included in the overview message received from the device 5. For example, the identifier may be an IP address associated with the device 5 that identifies the device 5 on the network 100. The reply message may include the subset or entire persona information of the user of device 10. For example, the reply message may include the personal interest of the user of device 10.
The device 10 may also decide to store in the reply message, a suggestion of another interest it assumes the user of device 5 might consider interesting based on the persona information received from device 5. For example, device 10 may assume that device 5 might enjoy a game of Checkers based on device 5's interest in the game of Chess, and include this suggestion in the reply message to device 5.
The reply message may also include an answer to the query. For example, the user of device 10 may suggest a vegetarian restaurant, or the device 10 may include in the reply message a copy of a favorite vegetarian restaurant list of the user of device 10.
In one embodiment, the device 10 may initiate a relationship directly with device 5 upon analyzing the overview message at block 215. For example, the user of device 10 may include in the reply message an indication to initiate a relationship to play a game of Chess.
At block 225, the device 5 receives the reply message from the device 10.
At block 230, the device 5 stores the persona information of device 10 into a data store (e.g., a database). The data store may be on device 5 or on another remote device. In this way, the device 5 may contain the persona information from one or more devices on the network. If the persona information is stored on another remote device, the user of device 5 may link to the data on the other device.
At block 240, the device 5 analyzes the persona information of device 10. For example, device 5 may automatically determine a shared interest of the user of device 5 and device 10. Device 5 may present automatically the shared interest to the user via a user interface on the device 5.
In one embodiment, the device 5 generates a visualization of one or more of the devices on the network that share a common interest with the device 5. That is, the device 5 may generate a visualization of a sub community of the entire network of devices at variable resolutions and time dynamics. The user interface may show network relationships among the various devices.
It should be understood that the user interface 300 might include any number of possible visualizations based on the attributes of the persona information to represent similar relationships between users of devices on the network. A few examples are content or network maps, an animated grid of pixels that change color and blink rates depending on content type and activity, and status displays that show the users, exchange volume and appropriateness of content accessible from the peer devices on the network 100, among other examples.
The visualization may be interactive, allowing the individual to drill down on areas of interest to learn more and possibly initiate new relationships. Application software on each device may also include transactional tools that enable the sharing, playing and purchasing of network content.
At block 250, the device 5 initiates a relationship with one or more devices on the network. For example, the user may initiate a file swapping protocol to share music, literature, poetry, a film, etc. In another example, the user may initiate a conversation session with the one or more devices of the network via email, instant messaging, a chat room, etc. The user may also initiate a gaming session to, for example, play a game of Chess with a user having the same skill level on the network 100.
It should be understood that each device on the network 100 may post their persona information for other devices on the network to analyze and possibly initiate a relationship based on the persona information, as described in one embodiment above. The device 10 may also automatically include in the reply message a description of the current activity on the device 10. For example, the device 10 may indicate the user of device 10 is currently listening to classic jazz or playing a game of Chess against the device 10. Again, upon receiving the reply message, the user of device 10 may determine to initiate a relationship based on the current activity of a device on the network.
At block 405, the device 5 generates a polling query message to be shared with each device on the network 100. The polling query message may include a subset or the entire persona information of the device 5, such as being a Chess player.
At block 410, the device 5 transmits the polling query message to device 10 on the network 100.
At block 415, the device 10 receives the polling query message.
At block 420, the device 10 analyzes the polling query message. For example, the device 10 may analyze the polling query message to determine areas of common interest with the user of device 5.
At block 425, the device 10 determines whether to indicate a willingness to initiate a relationship with the device 5. If, at block 425, the device 10 chooses not to indicate a willingness to initiate a relationship with device 5, control passes to block 430. If, at block 425, the device 10 chooses to indicate a willingness to initiate a relationship with device 5, control passes to block 435.
At block 430, the device 10 does nothing in response to receiving the polling query message from the other devices. That is, the device 10 ignores the polling query message and forwards the message to the next device on the network.
At block 435, the device 10 stores a subset or all of the persona information for the user of the device 10 into the polling query message.
At block 440, the device 10 determines which device is next to receive the polling query message from device 10. If there is another device on the network 100 to receive the polling query message from the device 10, control is passed to block 445. If there is not another device on the network 100 to receive the polling query message, control passes to block 450.
At block 445, the device 10 determines whether to transmit the polling query message to a device that has not received the polling query message from device 5. It should be understood that, in one embodiment, when the next device (e.g., device 15) receives the polling query message it would follow a similar process flow as started at block 415, as illustrated by dotted line 447. In this way, each device may store persona information into the polling query message.
At block 450, the device 10 transmits the polling query message to the originating device 5.
At block 455, the device 5 receives the polling query message.
At block 460, the device 5 stores the persona information from the one or more devices into a data store (e.g., database). That data store may be on device 5 or on another remote device. In this way, the device 5 may contain the persona information from one or more devices on the network 100.
At block 465, the device 5 analyzes the returned polling query message. For example, the device 5 may build a model of the current community activity and areas of shared interest, as described above.
At block 475, the device 5 initiates and sends a negotiation query message to one or more devices that indicate a willingness to initiate a relationship. The relationship may be based on shared interest between the users of the devices. For example, the user of device 5 may chose to initiate a relationship with device 10 to play a Chess game using application software on each device.
It should be appreciated that the process flow 400 may be able to communicate with devices a further distance than which may be achieved via the broadcast process flow 200. Because a message is passed to each device, one device may be able to pass the message outside the local area network of the originating device. For example, an intermediate device in the path may be a gateway type device that connects two local area networks.
The message generation component 610 includes software instructions to generate messages (e.g., an overview message, a reply message, a polling query message, a negotiation message, etc.), as described above for
One embodiment of a system suitable for use in the environments of
The description of
It will be appreciated that more or fewer processes may be incorporated into the methods illustrated in
In addition to the typical software subsystems of a peer-to-peer device, to perform device discovery, identification and communications protocol, as described above, each device on the network 100 may include relationship initialization software components.
A relationship initiation between devices in a network environment has been described. It should be understood that each device on the network 100 might share persona information. In this way, each device may also generate a visualization of the community with a user interface or analyze the network to determine whether to initiate a relationship with other devices having similar discovered interests. Although specific embodiments have been illustrated and described herein, it will be appreciated by those of ordinary skill in the art that any arrangement that is calculated to achieve the same purpose may be substituted for the specific embodiments shown. This application is intended to cover any adaptations or variations of the present invention.
While the invention is not limited to any particular implementation, for the sake of clarity a simplified method and system for initiating relationships between devices has been described. For example, those of ordinary skill within the art will appreciate that a device may include multiple users. Each user of a single device has the capability to store individual persona information, which may be used to initiate a relationship with users of other devices on the network. Furthermore, the terminology used in this application with respect to “message” is meant to include any protocol to communicate between devices. Therefore, it is manifestly intended that this invention be limited only by the following claims and equivalents thereof.
This application claims the benefit of U.S. Provisional Application No. 60/371,183, filed Apr. 8, 2002, incorporated herein by reference.
Number | Name | Date | Kind |
---|---|---|---|
5796393 | MacNaughton et al. | Aug 1998 | A |
5799318 | Cardinal et al. | Aug 1998 | A |
5940830 | Ochitani | Aug 1999 | A |
5983214 | Lang et al. | Nov 1999 | A |
6029195 | Herz | Feb 2000 | A |
6112181 | Shear et al. | Aug 2000 | A |
6176425 | Harrison et al. | Jan 2001 | B1 |
6205478 | Sugano et al. | Mar 2001 | B1 |
6226618 | Downs et al. | May 2001 | B1 |
6249226 | Harrison et al. | Jun 2001 | B1 |
6249282 | Sutcliffe et al. | Jun 2001 | B1 |
6279000 | Suda et al. | Aug 2001 | B1 |
6342830 | Want et al. | Jan 2002 | B1 |
6438579 | Hosken | Aug 2002 | B1 |
6446208 | Gujar et al. | Sep 2002 | B1 |
6480961 | Rajasekharan et al. | Nov 2002 | B2 |
6490579 | Gao et al. | Dec 2002 | B1 |
6504920 | Okon et al. | Jan 2003 | B1 |
6519629 | Harvey et al. | Feb 2003 | B2 |
6523022 | Hobbs | Feb 2003 | B1 |
6678680 | Woo | Jan 2004 | B1 |
6728729 | Jawa et al. | Apr 2004 | B1 |
6742032 | Castellani et al. | May 2004 | B1 |
6757710 | Reed | Jun 2004 | B2 |
6865599 | Zhang | Mar 2005 | B2 |
6944669 | Saccocio | Sep 2005 | B1 |
6947966 | Oko, Jr. et al. | Sep 2005 | B1 |
6957199 | Fisher | Oct 2005 | B1 |
6961723 | Faybishenko et al. | Nov 2005 | B2 |
6968333 | Abbott et al. | Nov 2005 | B2 |
7010537 | Eyal et al. | Mar 2006 | B2 |
7092952 | Wilens | Aug 2006 | B1 |
7117245 | Levkoff et al. | Oct 2006 | B1 |
7130807 | Mikurak | Oct 2006 | B1 |
7162488 | DeVorchik et al. | Jan 2007 | B2 |
20010039656 | Nakamura et al. | Nov 2001 | A1 |
20010051996 | Cooper | Dec 2001 | A1 |
20020002483 | Siegel et al. | Jan 2002 | A1 |
20020027567 | Niamir | Mar 2002 | A1 |
20020028889 | McCoskey et al. | Mar 2002 | A1 |
20020055919 | Mikheev | May 2002 | A1 |
20020062290 | Ricci | May 2002 | A1 |
20020077988 | Sasaki et al. | Jun 2002 | A1 |
20020091642 | Rahnasto | Jul 2002 | A1 |
20020107701 | Batty et al. | Aug 2002 | A1 |
20020138744 | Schleicher et al. | Sep 2002 | A1 |
20020147880 | Baldonado | Oct 2002 | A1 |
20020156917 | Nye | Oct 2002 | A1 |
20030009570 | Moskowitz et al. | Jan 2003 | A1 |
20030028610 | Pearson | Feb 2003 | A1 |
20030037097 | Meyer et al. | Feb 2003 | A1 |
20030037157 | Pestoni et al. | Feb 2003 | A1 |
20030041108 | Henrick et al. | Feb 2003 | A1 |
20030046281 | Son | Mar 2003 | A1 |
20030115318 | Wueste | Jun 2003 | A1 |
20030121008 | Tischer | Jun 2003 | A1 |
20030126245 | Feltin et al. | Jul 2003 | A1 |
20030158958 | Chiu | Aug 2003 | A1 |
20040030741 | Wolton et al. | Feb 2004 | A1 |
20040039707 | Ricci | Feb 2004 | A9 |
20050113066 | Hamberg | May 2005 | A1 |
20050266835 | Agrawal et al. | Dec 2005 | A1 |
20070106780 | Farnham et al. | May 2007 | A1 |
Number | Date | Country |
---|---|---|
19929188 | Nov 2001 | DE |
0993163 | Dec 2000 | EP |
1154390 | Nov 2001 | EP |
2367916 | Apr 2002 | GB |
WO 0101239 | Jan 2001 | WO |
WO 0106398 | Jan 2001 | WO |
WO 0146843 | Jun 2001 | WO |
WO 0175640 | Oct 2001 | WO |
Number | Date | Country | |
---|---|---|---|
20030233399 A1 | Dec 2003 | US |
Number | Date | Country | |
---|---|---|---|
60371183 | Apr 2002 | US |