Weighting social network relationships based on communications history

BACKGROUND

0001Social networks are increasingly becoming a popular platform for individuals or organizations to communicate with one another. Typically, a social network allows individuals or organizations to share interests, ideas, beliefs, and/or views, develop friends or business relationships, sustain communication with existing friends or family, or simply provide an open forum for anyone to communicate.

0002Given the expansive nature and various forms of communication available today, users of social networks can accumulate a large number of “connections.”

BRIEF DESCRIPTION OF THE DRAWINGS

0003<figref idref="DRAWINGS">FIG. 1</figref> is a diagram illustrating an overview of exemplary embodiments described herein;

0004<figref idref="DRAWINGS">FIG. 2</figref> is a diagram of exemplary functional components for collecting session information and creating a social graph based on a weighting scheme;

0005<figref idref="DRAWINGS">FIG. 3</figref> is a diagram illustrating an exemplary weighted social graph;

0006<figref idref="DRAWINGS">FIG. 4</figref> is a diagram of an exemplary user device in which the embodiments described herein may be implemented;

0007<figref idref="DRAWINGS">FIG. 5</figref> is a diagram illustrating exemplary components of the user device;

0008<figref idref="DRAWINGS">FIG. 6</figref> is a diagram illustrating exemplary components of a device that may correspond to one or more devices in the network and/or the social network;

0009<figref idref="DRAWINGS">FIG. 7</figref> is a diagram illustrating an exemplary database that includes information associated with a weighted social graph and/or communication history;

0010<figref idref="DRAWINGS">FIG. 8</figref> is a flow diagram illustrating an exemplary process for providing social network information based on a weighted social graph;

0011<figref idref="DRAWINGS">FIG. 9</figref> is a diagram illustrating an exemplary graphical user interface (GUI) that shows social network information associated with connections lists;

0012<figref idref="DRAWINGS">FIGS. 10A-10C</figref> are diagrams illustrating exemplary GUIs that show social network information associated with user presence information;

0013<figref idref="DRAWINGS">FIG. 11</figref> is a diagram illustrating an exemplary GUI that shows social network information having the user's communication history with this connection;

0014<figref idref="DRAWINGS">FIG. 12</figref> is a diagram illustrating an exemplary GUI that shows social network information associated with ranking connections during a discussion forum;

0015<figref idref="DRAWINGS">FIG. 13</figref> is a flow diagram illustrating an exemplary process for providing session information to a social network; and

0016<figref idref="DRAWINGS">FIG. 14</figref> is a flow diagram illustrating an exemplary process for providing social network information based on a weighted social graph.

DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS

0017The following detailed description refers to the accompanying drawings. The same reference numbers in different drawings may identify the same or similar elements. Also, the following detailed description does not limit the invention.

0018The term “connection,” as used herein, is intended to be broadly interpreted to include a social network contact. The social network contact may correspond to an individual, a group of individuals, or an entity (e.g., a business).

0019The term “social graph” or “weighted social graph,” as used herein, is intended to be broadly interpreted to correspond to a user's connections and a user's relational links with these connections. A relational link between the user and a connection signifies a relationship between the user and the connection. Relational links in the weighted social graph may be weighted. A weight assigned to a relational link may be based on a communication history associated with communications between the user and the connection. The weight may correspond to a level of importance of the connection, from the perspective of the user. The communication between the user and the connection may occur outside of the social network.

0020Embodiments described herein relate to utilizing session information occurring outside of a social network. In one embodiment, a weighting scheme, based on the session information, may be utilized to create relational links between the user and connections associated with the social network. For example, the weight assigned to the relational link may be based on quantifiable information, such as, for example, the user's communications history with the connection. In one implementation, the more frequently the user communicates with the connection, the greater the weight that may be assigned to the relational link. Additionally, or alternatively, other parameters related to the user's communication history may be considered, such as, for example, the type of communications (e.g., e-mail, telephone), the direction of the communications (e.g., from the user to the connection or from the connection to the user), the duration of the communications, the communication addresses (e.g., home telephone number, business telephone number), name information, and/or address information.

0021Based on such a weighting scheme, the social network may, for example, prioritize presentation of information (e.g., postings) to the user or delivery of communications to the user according to the user's weighed social graph. As will be described, the weighted social graph may include connections and the weighted relational links, from the perspective of the user.

0022Additionally, the social network may, for example, sort the user's connection list based on the user's weighted social graph, or sort the user's connection list based on the most recent activity with connections in the user's weighted social graph. The social network may also provide a detailed communication history with respect to connections (e.g., based on the session information) in conjunction with the connection's activity history on the social network. The social network may prioritize an order in which the user may communicate with his or her connections based on the user's weighted social graph. The social network may also identify a preferred form of communication with connections of the user's weighted social graph. The social network may allow the user to control, the level or degree of disclosure of presence of the user to his or her connections, based on the weighted social graph. Also, the social network may rank or prioritize input (e.g., comments) from connections, which the user may view during a debate, a commentary and/or a decision-making process, based on the weighted social graph.

0023As described herein, by overlaying information about the user's communication history (e.g., based on the session information) within the user's social graph, the social network may automatically manage relational links of the user's social graph and dynamically adapt various services provided to the user via the social network, as well as improve the user's interaction with his or her social graph.

0024<figref idref="DRAWINGS">FIG. 1</figref> is a diagram illustrating an overview of exemplary embodiments described herein. As illustrated in <figref idref="DRAWINGS">FIG. 1</figref>, an exemplary environment <b>100</b> may include users <b>105</b>-<b>1</b> through <b>105</b>-<b>4</b> (referred to generally as user(s) <b>105</b>), user devices <b>110</b>-<b>1</b> through <b>110</b>-<b>4</b> (referred to generally as user device(s) <b>110</b>), a network <b>115</b> that may include a social network <b>120</b>-<b>1</b>, and network <b>115</b> may be connected to (e.g., communicatively coupled to) social networks <b>120</b>-<b>2</b> to <b>120</b>-N (referred to generally as social network(s) <b>120</b>).

0025User device <b>110</b> may include a device having communication capability. By way of example, user device <b>110</b> may include a wireless telephone (e.g., a mobile phone, a cellular phone), a computational device (e.g., a computer), a personal digital assistant (PDA), a web-browsing device, a personal communication systems (PCS) device, a television and (e.g., a set top box and/or a remote control), a vehicle-based device, and/or some other type of portable, mobile, stationary, or handheld device.

0026Network <b>115</b> may include one or multiple networks of any type (i.e., wired and/or wireless). For example, network <b>115</b> may include a local area network (LAN), a wide area network (WAN), a telephone network, such as a Public Switched Telephone Network (PSTN), a cellular network, or a Public Land Mobile Network (PLMN), a satellite network, an intranet, the Internet, a data network, and/or a private network. Social network <b>120</b> may correspond to a social networking on-line site and/or system that allow individuals to interact.

0027In an exemplary implementation, network <b>115</b> may collect session information related to communications to and from users <b>105</b>. The session information may include, for example, the individuals involved in the communication (e.g., the names of the individuals), the type of communication (e.g., telephone, e-mail, short messaging service (SMS), multimedia messaging service (MMS), paging, video session, etc.), communication address information (e.g., telephone number, e-mail address, etc.), the duration of the communication, as well as other types of information that may be attributed to session information. Network <b>115</b> may provide the session information to social network <b>120</b>. Based on the session information, social network <b>120</b> may perform a lookup to determine whether the session information corresponds to information in social network <b>120</b>. For example, social network <b>120</b> may determine whether a name or a telephone number from the session information corresponds to a name or a telephone number of an individual (e.g., a subscriber or a participant) in social network <b>120</b>. Based on a comparison between the session information and the information in social network <b>120</b>, social network <b>120</b> may construct a weighted social graph for the user in social network <b>120</b>.

0028Once the weighted social graph is created, social network <b>120</b> may, for example, prioritize presentation of information, sort connection lists, prioritize an order in which the user may communicate with his or her connections, and/or provide different levels of disclosure of presence information, for the user. Social network <b>120</b> may perform other types of services, as described herein, for the user.

0029As a result of the foregoing, by utilizing the user's communication history with respect to connections, social network <b>120</b> may automatically create and/or manage the user's weighted social graph and dynamically adapt various services provided to the user via the social network, as well as improve the user's interaction with his or her weighted social graph.

0030Since exemplary embodiments and implementations have been broadly described, variations to the above embodiments and implementations exist, and will be discussed further below.

0031It will be appreciated that the collecting of session information and creating weighted social graphs for users may involve multiple entities. For example, referring to <figref idref="DRAWINGS">FIG. 1</figref>, network <b>115</b> may be owned, operated, and/or managed by one entity (e.g., a service provider or a network operator), while social networks <b>120</b>-<b>2</b> to <b>120</b>-N may be owned, operated, and/or managed by other entity(ies) (e.g., a social network provider(s)). In such instances, it is assumed that a business relationship might exist between the two (or more entities). By way of example, network <b>115</b> may be owned, operated, and/or managed by a service provider, such as Verizon, while social networks <b>120</b>-<b>2</b> to <b>120</b>-N may correspond to social networks, such as, for example, LinkedIn, Facebook, MySpace, etc., which may be owned, operated, and/or managed by social network providers. Alternatively, referring to <figref idref="DRAWINGS">FIG. 1</figref>, network <b>115</b> may be owned, operated, and/or managed by a same entity as social network <b>120</b>-<b>1</b>. By way of example, Verizon may own, operate, and/or manage network <b>115</b> and may offer social network services (e.g., social network <b>120</b>-<b>1</b>) to their subscribers.

0032<figref idref="DRAWINGS">FIG. 2</figref> is a diagram of exemplary functional components for collecting session information and creating a social graph based on a weighting scheme. As illustrated in <figref idref="DRAWINGS">FIG. 2</figref>, network <b>115</b> may include an IP multimedia subsystem component (IMS) <b>205</b>, and a session record processing component (SRP) <b>210</b>. Additionally, social network <b>120</b> may include a social network weighting component (SNW) <b>215</b>.

0033IMS <b>205</b> may include one or a group of devices that, among other things, provide a variety of multimedia services (e.g., voice, video, data, SMS, MMS, etc.) to users (e.g., person-to-person communication, person-to-group communication, and person-to-content communication). IMS <b>205</b> may collect or receive session information associated with the multimedia services provided. IMS <b>205</b> may include, for example, a server, a data center, a computer, and/or some other type of network device.

0034SRP <b>210</b> may include one or multiple devices that, among other things, detect, monitor, collect, receive, and/or manage session information associated with communications in or via network <b>115</b>. Depending on the type of communication, the content of the session information may be different. SRP <b>210</b> may include, for example, a server, a data center, a computer, and/or some other type of network device.

0035SNW <b>215</b> may include one or multiple devices that, among other things, generate weighted social graphs for users based on session information received from network <b>115</b> (e.g., IMS <b>205</b> and/or SRP <b>210</b>). The session information may be sent to social network <b>120</b> and/or social network <b>120</b> may retrieve the session information from network <b>115</b> via a real-time feed or retrieval arrangement, a periodic feed or retrieval arrangement, or some other type of user-configured arrangement. The weighted social graph may be associated with the user and the user's connections. The weighted social graph may include relational links between the user and the user's connections. SNW <b>215</b> may apply a weighting scheme to each relational link. The weighting calculus (i.e., the weighting scheme) may be user-configured. By way of example, the weight of the relational link, between the user and the connection, may be selected based on parameters associated with a communication history between the user and the connection. For example, the number of communications, the type of communications, the direction of the communications (e.g., from the user to the connection or from the connection to the user), the duration of the communications, the communication addresses (e.g., home telephone number versus business telephone number), name information (e.g., relative or family member), and/or address information (e.g., lives with connection, lives near or far from connection) may be utilized to determine the weight of the relational link. SNW <b>215</b> may also generate weighted social graphs based on the session information from network <b>115</b> and social network activity.

0036Although <figref idref="DRAWINGS">FIG. 2</figref> illustrates exemplary functional components, in other implementations, fewer, additional, and/or different functional components, or a different arrangement of functional components than those illustrated in <figref idref="DRAWINGS">FIG. 2</figref>, and described herein, may be implemented.

0037<figref idref="DRAWINGS">FIG. 3</figref> is a diagram illustrating an exemplary weighed social graph scheme. As illustrated, user <b>105</b> may belong to or interact with social networks <b>120</b>-<b>1</b> through <b>120</b>-<b>4</b>. Each social network <b>120</b> may, from the perspective of user <b>105</b>, include connections. For example, as illustrated in <figref idref="DRAWINGS">FIG. 3</figref>, social network <b>120</b>-<b>1</b> may include connections <b>305</b>-<b>1</b>, <b>305</b>-<b>2</b>, and <b>305</b>-<b>3</b> (referred to generally as connection <b>305</b>) that have relational links <b>310</b>-<b>1</b>, <b>310</b>-<b>2</b>, and <b>310</b>-<b>3</b> (referred to generally as relational link <b>310</b>), respectively, with user <b>105</b>. As further illustrated, each relational link <b>310</b> may be assigned a corresponding weight <b>315</b>-<b>1</b>, <b>315</b>-<b>2</b>, and <b>315</b>-<b>3</b> (referred to generally as weight <b>315</b>). Weight <b>315</b> may correspond to a level of strength or importance of connection <b>305</b>, from the perspective of user <b>105</b>. As previously described, the calculation of weight <b>315</b> may be based on session information (i.e., communication history) associated with user <b>105</b> and a particular connection <b>305</b>. Although not illustrated, user <b>105</b> may have connections <b>305</b> in social networks <b>120</b>-<b>2</b> through <b>120</b>-<b>4</b>. Similarly, each relational link <b>310</b> between connections <b>305</b> in social networks <b>120</b>-<b>2</b> through <b>120</b>-<b>4</b> may be assigned a corresponding weight <b>315</b>.

0038<figref idref="DRAWINGS">FIG. 4</figref> is a diagram of an exemplary user device <b>110</b> in which the embodiments described herein may be implemented. As illustrated in <figref idref="DRAWINGS">FIG. 4</figref>, user device <b>110</b> may include a housing <b>405</b>, a microphone <b>410</b>, a speaker <b>415</b>, a keypad <b>420</b>, and a display <b>425</b>. In other embodiments, user device <b>110</b> may include fewer, additional, and/or different components, or a different arrangement of components than those illustrated in <figref idref="DRAWINGS">FIG. 4</figref> and described herein.

0039Housing <b>405</b> may include a structure to contain components of user device <b>110</b>. For example, housing <b>405</b> may be formed from plastic, metal, or some other material. Housing <b>405</b> may support microphone <b>410</b>, speaker <b>415</b>, keypad <b>420</b>, and display <b>425</b>.

0040Microphone <b>410</b> may transduce a sound wave to a corresponding electrical signal. For example, a user may speak into microphone <b>410</b> during a telephone call or to execute a voice command. Speaker <b>415</b> may transduce an electrical signal to a corresponding sound wave. For example, a user may listen to music or listen to a calling party through speaker <b>415</b>.

0041Keypad <b>420</b> may provide input to user device <b>110</b>. Keypad <b>420</b> may include a standard telephone keypad, a QWERTY keypad, and/or some other type of keypad. Keypad <b>420</b> may also include one or more special purpose keys. In one implementation, each key of keypad <b>420</b> may be, for example, a pushbutton. A user may utilize keypad <b>420</b> for entering information, such as text or activating a special function.

0042Display <b>425</b> may output visual content and may operate as an input component. For example, display <b>425</b> may include a liquid crystal display (LCD), a plasma display panel (PDP), a field emission display (FED), a thin film transistor (TFT) display, or some other type of display technology. Display <b>425</b> may display, for example, text, images, and/or video information to a user. In one implementation, display <b>425</b> may include a touch-sensitive screen. Display <b>425</b> may correspond to a single-point input device (e.g., capable of sensing a single touch) or a multipoint input device (e.g., capable of sensing multiple touches that occur at the same time). Display <b>425</b> may implement, for example, a variety of sensing technologies, including but not limited to, capacitive sensing, surface acoustic wave sensing, resistive sensing, optical sensing, pressure sensing, infrared sensing, gesture sensing, etc.

0043<figref idref="DRAWINGS">FIG. 5</figref> is a diagram illustrating exemplary components of user device <b>110</b>. As illustrated, user device <b>110</b> may include a processing system <b>505</b>, a memory/storage <b>510</b>, a communication interface <b>520</b>, an input <b>530</b>, and an output <b>535</b>. In other embodiments, user device <b>110</b> may include fewer, additional, and/or different components, or a different arrangement of components than those illustrated in <figref idref="DRAWINGS">FIG. 5</figref> and described herein.

0044Processing system <b>505</b> may include one or multiple processors, microprocessors, data processors, co-processors, network processors, application specific integrated circuits (ASICs), controllers, programmable logic devices, chipsets, field programmable gate arrays (FPGAs), and/or some other component that may interpret and/or execute instructions and/or data. Processing system <b>505</b> may control the overall operation (or a portion thereof) of user device <b>110</b> based on an operating system and/or various applications. Processing system <b>505</b> may interpret and/or execute instructions and/or data.

0045Memory/storage <b>510</b> may include memory and/or secondary storage. For example, memory/storage <b>510</b> may include a random access memory (RAM), a dynamic random access memory (DRAM), a read only memory (ROM), a programmable read only memory (PROM), a flash memory, and/or some other type of memory. Memory/storage <b>510</b> may include a hard disk (e.g., a magnetic disk, an optical disk, a magneto-optic disk, etc.) or some other type of computer-readable medium, along with a corresponding drive. The term “computer-readable medium,” as used herein, is intended to be broadly interpreted to include a memory, a secondary storage, a compact disc (CD), a digital versatile disc (DVD), or the like. The computer-readable medium may be implemented in a single device, in multiple devices, in a centralized manner, or in a distributed manner.

0046Memory/storage <b>510</b> may store data, application(s), and/or instructions related to the operation of user device <b>110</b>. For example, memory/storage <b>510</b> may include a variety of applications <b>515</b>, such as, for example, an e-mail application, a telephone application, a camera application, a video application, a multi-media application, a music player application, a visual voicemail application, a contacts application, a data organizer application, a calendar application, an instant messaging application, a texting application, a web browsing application, a location-based application (e.g., a GPS-based application), a blogging application, and/or other types of applications (e.g., a word processing application, a spreadsheet application, etc.).

0047Communication interface <b>520</b> may permit user device <b>110</b> to communicate with other devices, networks, and/or systems. For example, communication interface <b>520</b> may include an Ethernet interface, a radio interface, a microwave interface, or some other type of wireless and/or wired interface.

0048Input <b>530</b> may permit a user and/or another device to input information in user device <b>110</b>. For example, input <b>530</b> may include a keyboard, keypad <b>420</b>, display <b>425</b>, a touchpad, a mouse, a button, a switch, a microphone, an input port, voice recognition logic, and/or some other type of visual, auditory, etc., input component. Output <b>535</b> may permit user device <b>110</b> to output information to a user and/or another device. For example, output <b>535</b> may include display <b>425</b>, speaker <b>415</b>, one or more light emitting diodes (LEDs), an output port, a vibrator, and/or some other type of visual, auditory, tactile, haptic, etc., output component.

0049<figref idref="DRAWINGS">FIG. 6</figref> is a diagram illustrating exemplary components of a device <b>600</b> that may correspond to one or more devices in network <b>115</b> and/or social network <b>120</b>. For example, device <b>600</b> may correspond to devices associated with IMS <b>205</b>, SRP <b>210</b>, and/or SNW <b>215</b>. As illustrated, device <b>600</b> may include a processing system <b>605</b>, a memory/storage <b>610</b>, and a communication interface <b>620</b>. In other embodiments, device <b>600</b> may include fewer, additional, and/or different components, or a different arrangement of components than those illustrated in <figref idref="DRAWINGS">FIG. 6</figref> and described herein.

0050Processing system <b>605</b> may include one or multiple processors, microprocessors, data processors, co-processors, network processors, ASICs, controllers, programmable logic devices, chipsets, FPGAs, and/or some other component that may interpret and/or execute instructions and/or data. Processing system <b>605</b> may control the overall operation (or a portion thereof) of device <b>600</b> based on an operating system and/or various applications. Processing system <b>605</b> may interpret and/or execute instructions and/or data.

0051Memory/storage <b>610</b> may include memory and/or secondary storage. For example, memory/storage <b>610</b> may include a RAM, a DRAM, a ROM, a PROM, a flash memory, and/or some other type of memory. Memory/storage <b>610</b> may include a hard disk (e.g., a magnetic disk, an optical disk, a magneto-optic disk, solid state disk, etc.) or some other type of computer-readable medium, along with a corresponding drive.

0052Memory/storage <b>610</b> may store data, application(s), and/or instructions related to the operation of device <b>600</b>. For example, in the instance that device <b>600</b> corresponds to IMS <b>205</b>, memory/storage <b>610</b> may include applications <b>615</b>, such as, for example, to provide and/or deliver multimedia services to users <b>105</b>. Applications <b>615</b> may also detect, monitor, collect, receive, and/or manage session information. Alternatively, in the instance that device <b>600</b> corresponds to SRP <b>210</b>, memory/storage <b>610</b> may include applications <b>615</b>, such as, for example, to detect, monitor, collect, receive, and/or manage session information. Alternatively, in the instance that device <b>600</b> corresponds to SNW <b>215</b>, memory/storage <b>610</b> may include applications <b>615</b>, such as, for example, to generate weighted social graphs based on session information. Applications <b>615</b> may apply a weighting calculus to determine the weight assigned to a relational link. The weight of each parameter associated with session information (e.g., the type of communication, the duration of the communication, etc.), which is used for determining the weight of the relational link, may be user-configured. In one implementation, application <b>615</b> may compile information of one or multiple sessions associated with a communication history between the user and the connection in order to select the weight. SNW <b>215</b> may also process the session information to provide various social network services (e.g., prioritize presentation/delivery of information, sort connections list, etc.), as described herein, to the user.

0053Communication interface <b>620</b> may permit device <b>600</b> to communicate with other devices, networks, and/or systems. For example, communication interface <b>620</b> may include an Ethernet interface, a radio interface, a microwave interface, or some other type of wireless interface and/or wired interface.

0054As previously described, weighted relational links in the weighted social graph for a user may be used by the social network to prioritize presentation of information to the user, deliver communications, sort connections listed in a connection list, etc. Additionally, the social network may provide the user with other information that may enhance the user's experience in the social network.

0055<figref idref="DRAWINGS">FIG. 7</figref> is a diagram illustrating an exemplary database <b>700</b> that includes information associated with a weighted social graph and/or communication history. Database <b>700</b> may include a presentation/delivery field <b>705</b>, a weighted connection list field <b>710</b>, a temporal connection list field <b>715</b>, a communication history field <b>720</b>, a communication preferences field <b>725</b>, a presence field <b>730</b>, and a debate/decisions field <b>735</b>. The term “database,” as used herein, is intended to be broadly interpreted to include an arrangement of data. For example, a database may correspond to a table or some other type of data structure. Database <b>700</b> (or portions thereof) may be stored in memory/storage <b>610</b> of device <b>600</b>.

0056Presentation/delivery field <b>705</b> may include information for presenting and delivering social network activity based on the weighted relational links in the user's weighted social graph. For example, social network <b>120</b> may prioritize the presentation and/or delivery of information associated with social network activity (e.g., postings, news feed, communications, etc.) according to the weight assigned to the weighted relational link. Presentation/delivery field <b>705</b> may include information for prioritizing an order in which the user communicates with his or her connections based on the weighted relational links in the user's weighted social graph. For example, in the instance that multiple connections each initiate an IM session with the user. Social network <b>120</b> may prioritize an order in which the user communicates with the multiple connections based on the user's weighted social graph.

0057Weighted connection list field <b>710</b> may include information for sorting connections in a user's connections list based on the weighted relational links in the user's weighted social graph. For example, social network <b>120</b> may sort the user's connections in a connections list so that the most weighted connection is listed at the top of the connections list and the remaining connections are sorted in descending order according to their respective weighted relational links.

0058Temporal connection list field <b>715</b> may include information for sorting connections in a user's connections list based on how recent the user has communicated with each connection. For example, social network <b>120</b> may sort the user's connections in a connection list so that the connection, which the user has mostly recently communicated with, is listed at the top of the connections list, and the remaining connections are sorted in descending order according to the temporal aspects of communications. In one implementation, social network <b>120</b> may utilize the communication history from network <b>115</b> to determine the temporal ordering of connections. Additionally, or alternatively, the social network may determine the temporal ordering of connections based on communications conducted (e.g., while logged in) in social network <b>120</b>.

0059Communication history field <b>720</b> may include communication history (e.g., session information) from network <b>115</b> and social network activity information. By way of example, SNW <b>215</b> may receive or retrieve communication history information from IMS <b>205</b> and/or SRP <b>210</b>. Social network <b>120</b> may utilize the information contained in communication history field <b>720</b> to, for example, provide the user with the user's communication history (i.e., outside of the social network with the connection) and the connection's social network activity (e.g., status, postings, photos, videos, etc.) on social network <b>120</b>.

0060Communication preferences field <b>725</b> may include communication history (e.g., session information) from network <b>115</b>. For example, social network <b>120</b> may utilize the information contained in communication preferences field <b>725</b> to provide the user with a preferred method of communication with the user's connection based on the communication history associated with the user and the connection. In an example case, the connection may leave the user a posting on social network <b>120</b>. Based on the communication history between the user and the connection, social network <b>120</b> may determine that the preferred method of communication with this connection is by e-mail because the connection is currently traveling overseas and is in a different time zone. For example, the communication history may reveal that the user has recently been communicating with the connection via e-mail.

0061Presence field <b>730</b> may include information corresponding to the weighted relational links in the user's weighted social graph and presence information. For example, social network <b>120</b> may utilize the information contained in presence field <b>730</b> to permit the user to disclose presence related information to connections based on their corresponding weighted relational links. For example, the user may set-up varying levels of presence information, where connections having a higher weighting may be provided with more specific information relating to the presence of the user.

0062Debate/decisions field <b>735</b> may include information that ranks or sorts feedback from connections with respect to, for example, a discussion form, based on the weighted social graph. The term “discussion forum,” as used herein is intended to be broadly interpreted to include, for example, a discussion, a commentary, a debate, a decision-making process, or a feedback session. For example, social network <b>120</b> may utilize the information contained in debate/decisions field <b>735</b> to prioritize input (e.g., comments, feedback, etc.) from connections during the discussion forum according to the weight associated with the connection. In some implementations, the user may not see the comments or feedback (e.g., the comment or feedback may be dropped or omitted) of a connection having a weight below a user-configured threshold.

0063Although, <figref idref="DRAWINGS">FIG. 7</figref> illustrates an exemplary database <b>700</b>, in other implementations, fewer, additional, or different informational fields may be included. It will be appreciated that database <b>700</b> may be implemented in a distributed manner (e.g., among multiple devices (e.g., network servers, information repositories, etc.)) or in a centralized manner (e.g., on a single device).

0064<figref idref="DRAWINGS">FIG. 8</figref> is a flow diagram illustrating an exemplary process <b>800</b> for providing social network information based on a weighted social graph. In one implementation, process <b>800</b> may be performed by user device <b>110</b>.

0065Process <b>800</b> may begin with transmitting a communication intended to another user over a non-social network, or receiving a communication from another user over the non-social network (block <b>805</b>). User <b>105</b> may transmit a communication (e.g., an e-mail, a telephone call, a video call, an SMS message, a MSM message, a page, or some other type of electronic message) to another user <b>105</b> via user device <b>110</b>. Additionally, or alternatively, user <b>105</b> may receive a communication from another user <b>105</b> via user device <b>110</b>. The communication transmitted or the communication received may occur over network <b>115</b> (i.e., outside of social network <b>120</b>). It will be appreciated that one or multiple communications may occur.

0066A social network may be accessed (block <b>810</b>). Subsequent to the transmitted or received communication(s), user device <b>110</b> may access social network <b>120</b>. In some instances, user <b>105</b> may have to log-in to social network <b>120</b>.

0067Social network information, that includes a weighting of the other user based on session information associated with the communication, may be received (block <b>815</b>). For purposes of discussion, it is assumed that other user <b>105</b> corresponds to a connection in social network <b>120</b>. As described herein, the session information may be used, by social network <b>120</b>, to weight relational links associated with user's <b>105</b> weighted social graph on social network <b>120</b>. In turn, the weighted social graph of user <b>105</b> may be used to provide user <b>105</b> with social network information via user device <b>110</b>. The term “social network information,” is to be broadly interpreted to include information based on the weighted social graph and communication history, as well as other types of information relating to a user's experience in social network <b>120</b> that necessarily flow therefrom.

0068The social network information may include information associated with database <b>700</b> and the services provided by social network <b>120</b> based on the weighted social graph. By way of example, the social network information may include presentation and delivery of social network activity, sorting of connections list based on weighting or most recent communications, communication history, communication preferences, presence information, and ranking of comments from connections, as previously described.

0069The social network information may be displayed (block <b>820</b>). User device <b>110</b> may display the social network information (e.g., on display <b>425</b>) to user <b>105</b>. <figref idref="DRAWINGS">FIGS. 9-12</figref> are diagrams illustrating exemplary graphical user interfaces (GUIs) that provide social network information, as described herein.

0070Although <figref idref="DRAWINGS">FIG. 8</figref> illustrates an exemplary process <b>800</b>, in other implementations, fewer, additional, or different operations may be performed.

0071<figref idref="DRAWINGS">FIG. 9</figref> is a diagram illustrating an exemplary GUI that shows social network information associated with connections lists. As illustrated, a GUI <b>905</b> may include a menu <b>910</b>. Menu <b>910</b> may include selectors <b>915</b> and <b>920</b>. Selector <b>915</b> may permit user <b>105</b> to view connections in social network <b>120</b> based on the weighted relational links associated with his or her connections. Selector <b>920</b> may permit user <b>105</b> to view connections in social network <b>120</b> according to a temporal relationship with the communications (e.g., from most recent to least recent). In this way, user <b>105</b> may determine which connections that user <b>105</b> has not communicated with recently.

0072<figref idref="DRAWINGS">FIGS. 10A-10C</figref> are diagrams illustrating exemplary GUIs that show social network information associated with user presence information. As illustrated, a GUI <b>1005</b> may include various levels of user presence information based on the weighted relational links. For purposes of discussion, assume <figref idref="DRAWINGS">FIG. 10A</figref> corresponds to a GUI <b>1005</b> with respect to a connection assigned a low-weighted relational link, <figref idref="DRAWINGS">FIG. 10B</figref> corresponds to a GUI <b>1005</b> with respect to a connection assigned a medium-weighted relational link, and <figref idref="DRAWINGS">FIG. 10C</figref> corresponds to a GUI <b>1005</b> with respect to a connection assigned a high-weighted relational link. By comparing the presence information <b>1010</b>, <b>1015</b>, and <b>1020</b> in <figref idref="DRAWINGS">FIGS. 10A-10C</figref>, respectively, each connection is afforded a corresponding level of presence information of user <b>105</b>. For example, as illustrated in <figref idref="DRAWINGS">FIG. 10A</figref>, the connection assigned the low-weighted relational link may see that user <b>105</b> is “busy” (as presence information). In <figref idref="DRAWINGS">FIG. 10B</figref>, the connection assigned the medium-weighted relational link may see that user <b>105</b> is “busy at party” (as presence information). In <figref idref="DRAWINGS">FIG. 10C</figref>, the connection assigned the high-weighted relational link may see that user <b>105</b> is “busy at my son's B-day party, at the bowling alley” (as presence information). User <b>105</b> may be permitted to provide varying levels of presence information to social network <b>120</b> based on user's <b>105</b> weighted social graph.

0073<figref idref="DRAWINGS">FIG. 11</figref> is a diagram illustrating an exemplary GUI that shows social network information having the user's communication history with this connection. As illustrated, a GUI <b>1105</b> may include an activity label <b>1110</b> and corresponding window <b>1115</b> that shows a connection's activity on social network <b>120</b>. GUI <b>1105</b> may include a contact history label <b>1120</b> and a corresponding window <b>1125</b> that shows user's <b>105</b> communication history with this connection. That is, window <b>1125</b> may include information based on session information that occurred outside of social network <b>120</b>. Additionally, GUI <b>1105</b> may also include a preferred communication label <b>1130</b> and a corresponding preferred communication field <b>1135</b> that identifies a preferred method of communication for user <b>105</b> to communicate with this connection. In this example, preferred communication field <b>1135</b> indicates that a preferred method of communication with this contact is by e-mail.

0074<figref idref="DRAWINGS">FIG. 12</figref> is a diagram illustrating an exemplary GUI that shows social network information associated with ranking connections during a discussion forum. As illustrated a GUI <b>1205</b> may provide a topic of discussion (e.g., the Stimulus Package). GUI <b>1205</b> may permit user <b>105</b> to view input (e.g., comments) from connections according to their assigned weight based on selector <b>1210</b>. As illustrated, user <b>105</b> may see comments <b>1215</b>-<b>1</b>, <b>1215</b>-<b>2</b>, and <b>1215</b>-<b>3</b> (referred to generally as comments <b>1215</b>) from connections, such as Jane and Kevin. The order of Jane's comments <b>1215</b>-<b>1</b> and <b>1215</b>-<b>2</b> may be listed before Kevin's comment <b>1215</b>-<b>3</b>. That is, for example, Jane may be assigned a higher weighted relational link than Kevin. Social network <b>120</b> may also omit comments <b>1215</b> from connections that have a weighted relational link below a threshold value. In other implementations, social network <b>120</b> may not omit any comments <b>1215</b> with respect to user's <b>105</b> connections.

0075<figref idref="DRAWINGS">FIG. 13</figref> is a flow diagram illustrating an exemplary process <b>1300</b> for providing session information to a social network. In one implementation, process <b>1300</b> may be performed by, for example, IMS <b>205</b> and/or SRP <b>210</b>. In other implementations, network devices or network systems, which obtain session information, although not specifically mentioned in the description, may perform process <b>1300</b>.

0076Process <b>1300</b> may begin with collecting session information associated with communications sent or received by a user (block <b>1305</b>). IMS <b>205</b> and/or SRP <b>210</b> may collect session information associated with communications sent or received by user <b>105</b>. The communications may include, for example, telephone calls, e-mail, SMS, MMS, paging, video sessions and/or some other form of electronic communication. The session information may also include information, not specifically collected as a result of the communication, such as, for example, name and/or address information.

0077The session information may be provided to a social network (block <b>1310</b>). In one implementation, IMS <b>205</b> and/or SRP <b>210</b> may transmit the session information to social network <b>120</b>. In other implementations, social network <b>120</b> may retrieve the information from IMS <b>205</b>, SRP <b>210</b>, or another device (e.g., a repository or a data center). It will be appreciated that social network <b>120</b> may obtain the session information from network <b>115</b> in various ways depending on the arrangement. For example, in the instance that social network <b>120</b> is part of network <b>115</b> (e.g., the same service provider or network operator owns, operates, and/or manages network <b>115</b> and social network <b>120</b>), the process of providing the session information to social network <b>120</b> may be different than the instance that social network <b>120</b> is not part of network <b>115</b> (e.g., the same service provider or network provider does not own, operate, and/or manage network <b>115</b> and social network <b>120</b>).

0078Although <figref idref="DRAWINGS">FIG. 13</figref> illustrates an exemplary process <b>1300</b>, in other implementations, fewer, additional, or different operations may be performed.

0079<figref idref="DRAWINGS">FIG. 14</figref> is a flow diagram illustrating an exemplary process <b>1400</b> for providing social network information based on a weighted social graph. In one implementation, process <b>1400</b> may be performed by, for example, SNW <b>215</b>. It will be appreciated, however, that the functionality associated with SNW <b>215</b>, as described herein, may be incorporated in one or multiple devices, and/or implemented in a centralized or a distributed manner. The one or multiple devices may include, for example, a server, a data center, a computer, or some other type of network device.

0080Process <b>1400</b> may begin with receiving or retrieving session information associated with a communication that occurred outside of a social network and involved users of the social network (block <b>1405</b>). SNW <b>215</b> may receive from network <b>115</b> (e.g., IMS <b>205</b> and/or SRP <b>210</b>) session information associated with a communication between users <b>105</b>. Alternatively, SNW <b>215</b> may retrieve, from network <b>115</b> (e.g., IMS <b>205</b> and/or SRP <b>210</b>), session information associated with a communication between users <b>105</b>.

0081The session information may be compared with the users of the social network (block <b>1410</b>). SNW <b>215</b> may compare the session information with information that social network <b>120</b> maintains on its users. For example, SNW <b>215</b> may compare telephone numbers, e-mail address, contact information, and/or session information that social network <b>120</b> maintains on its users with the session information received or retrieved from network <b>115</b>.

0082A user of the social network may be selected when the session information matches information of the social network (block <b>1415</b>). SNW <b>215</b> may select a user of social network <b>120</b> when the session information matches information of social network <b>120</b>.

0083A connection of the social network may be selected when the session information matches information of the social network (block <b>1420</b>). SNW <b>215</b> may select a connection of social network <b>120</b> when the session information matches information of social network <b>120</b>. The connection will be a connection of the user selected in block <b>1420</b>. It will be appreciated that SNW <b>215</b> may swap the selection of the user and the connection of the user. That is, when two or more users are involved in a communication, one user may be selected as the user of social network <b>120</b> and the remaining user(s) may be selected as connection(s) of the selected user. However, in another iteration with respect to the session information, SNW <b>215</b> may select another user as the user of social network <b>120</b> and the remaining user(s) may be selected as connection(s) of the selected user. SNW <b>215</b> may continue these iterations until each individual is selected as a user of the social network. Additionally, it will be appreciated that SNW <b>215</b> may correspondingly perform multiple iterations for the remaining operations described in blocks <b>1425</b>, <b>1430</b>, and <b>1435</b>.

0084A weighed social graph for the user of the social network may be generated based on the session information (block <b>1425</b>). SNW <b>215</b> may generate a weighted social graph for the user of the social network. For example, as previously described, SNW <b>215</b> may assign a weight to a relational link between the selected user and the selected connection. In instances when the weighted social graph already exists, SNW <b>215</b> may update the weight of the relational link.

0085Social network information may be generated based on the weighted social graph (block <b>1430</b>). SNW <b>215</b> may generate social network information, as previously described. The social network information may include information based on the weighted social graph and/or the session information (e.g., communication history). By way of example, the social network information may include information associated with prioritizing the presentation of information (e.g., postings) to the user, information associated with the prioritizing of delivering communications to the user according to the user's weighted social graph. Additionally, the social network information may include, for example, information associated with the sorting of the user's connection list based on the user's weighted social graph, and/or the sorting of the user's connection list based on the most recent activity with the connection in the user's weighted social graph. The social network information may also include, for example, information associated with providing a detailed communication history with respect to connections in conjunction with the connection's activity history. The social network may prioritize an order in which the user may communicate with his or her connections based on the user's weighted social graph. The social network information may also include information that identifies a preferred form of communication with a connection. The social network information may include information to allow the user to control the level or degree of disclosure of presence of the user to his or her connections based on the user's weighted social graph. Also, the social network information may include information to allow a user to rank or prioritize input from connections during a discussion forum based on the user's weighted social graph.

0086Social network information may be provided (block <b>1435</b>). SNW <b>215</b> may provide various services, as previously described herein, to the user of social network <b>120</b>. The various services may be based on the user's weighted social graph and/or communication history.

0087Although <figref idref="DRAWINGS">FIG. 14</figref> illustrates an exemplary process <b>1400</b>, in other implementations, fewer, additional, or different operations may be performed.

0088According to the embodiments described herein, a social network may utilize a communication history to create and/or update a weighted social graph for users of the social network. The social network may provide various services based on the weighted social graph and/or the communication history.

0089The foregoing description of implementations provides illustration, but is not intended to be exhaustive or to limit the implementations to the precise form disclosed. Accordingly, modifications to the embodiments, implementations, etc., described herein may be possible. For example, one or more operations associated with exemplary processes <b>1300</b> and/or <b>1400</b> may be implemented in the user device.

0090The term “may” is used throughout this application and is intended to be interpreted, for example, as “having the potential to,” “configured to,” or “being able to,” and not in a mandatory sense (e.g., as “must”). The terms “a,” “an,” and “the” are intended to be interpreted to include one or more items. Where only one item is intended, the term “one” or similar language is used. Further, the phrase “based on” is intended to be interpreted as “based, at least in part, on,” unless explicitly stated otherwise. The term “and/or” is intended to be interpreted to include any and all combinations of one or more of the associated list items.

0091In addition, while series of blocks have been described with regard to the processes illustrated in <figref idref="DRAWINGS">FIGS. 8, 13, and 14</figref>, the order of the blocks may be modified in other implementations. Further, non-dependent blocks may be performed in parallel.

0092It will be apparent that the device(s) described herein may be implemented in many different forms of software or firmware in combination with hardware in the implementations illustrated in the figures. The actual software code (executable by hardware) or specialized control hardware used to implement these concepts does not limit the disclosure of the invention. Thus, the operation and behavior of a device(s) was described without reference to the specific software code—it being understood that software and control hardware can be designed to implement the concepts based on the description herein.

0093Even though particular combinations of features are recited in the claims and/or disclosed in the specification, these combinations are not intended to limit the disclosure of the invention. In fact, many of these features may be combined in ways not specifically recited in the claims and/or disclosed in the specification.

0094No element, act, or instruction used in the present application should be construed as critical or essential to the implementations described herein unless explicitly described as such.