HK1180475A - Social networking grouping hierarchy structure - Google Patents

Abstract

The present invention discloses a social networking grouping hierarchy structure and a social networking environment which enable interaction between social networking (SNET) groups. Some interactions between SNET groups can include docking various SNET groups based upon interactions between a member and some part of a social network. Various hierarchies of social networking infrastructure can enable hierarchical interactions between social devices, SNET groups, and other elements associated with various social networking infrastructures. Capabilities provided by various elements in various SNET infrastructures can be docked to create combined SNET groups, and capabilities provided by an SNET group can be accessed via interaction with a representative view of the capabilities. Various interactions can be managed based upon inputs, trigger events, authorizations, and the like provided by various processing systems, devices, members, or the like. Various interactions can enable members associated with an SNET infrastructure to access capabilities provided by an SNET group via a docked SNET group.

Description

Social network packet hierarchy

CROSS-REFERENCE TO RELATED APPLICATIONS

Priority of the present application claims priority of united states provisional patent application 61/545,147 filed on 8/10/2011, united states utility patent application 13/342,301 filed on 3/1/2012, united states utility patent application 13/408,986 filed on 29/2/2012, united states utility patent application 13/351,822 filed on 17/1/2012, and united states utility patent application 13/436,557 filed on 30/3/2012, the entire contents of which are incorporated herein by reference.

Technical Field

The present invention relates generally to social networks and, more particularly, to social network group access, interaction, communication, control, and related services and communications.

Background

The popularity and growth of social networking sites and services has increased dramatically over the past few years. Social networking sites currently include Facebook, Google +, Twitter, MySpace, YouTube, LinkedIn, Flicker, Jaiku, MYUBO, Bebo, and the like. The Social Networking (SNET) sites are typically web-based and are organized around user profiles and/or collections of content accessible by network members. Members of the social network include individuals or groups, which are generally represented by profile pages and allow interaction as determined by the social network service.

In many mainstream social networks, especially profile-centric social networks, web activity centers or social spaces that enable members to view profiles communicate across a contact network and share activities, interests, opinions, status updates, audio/video content, etc. The social networking service may also allow members to track certain activities of other members of the social network, collaborate, find and communicate with existing friends, previous acquaintances, and colleagues, and establish new communications with other members.

Personal members typically connect to social networking services through existing web-based platforms via computing devices, tablets, or smartphones. Members often share a common hobby, social status, or geographical or cultural exchange with their respective contacts. Mobile social networking services based on smart phones and gaming machines are rapidly evolving local examples.

In so-called "cloud" computing, computing tasks are performed on remote computers/servers that are typically accessed via an internet connection. One benefit of cloud computing is that the relative processing and storage capabilities required by the user device may be reduced (e.g., the cloud computer may load a web page accessed by the tablet device and only return the required information to the tablet). Thus, in recent years, the amount of content and application software migrating from local or current storage to cloud-based data storage and management has increased. The software functions/services and content are typically provided on demand via a (virtualized) network infrastructure.

Typically, visitors to a location, network, etc. are granted access to the location, business network, and possibly a social networking environment, cloud applications, or cloud media content. The grant tends to be almost unlimited in duration and range. In addition, social groups have various mechanisms for establishing a connection with another member, member device, or member device service, including, for example, a phone number, an IP or other routing address, a VoIP/video call control point, a twitter control point, other SNET control points, a blog, a web address, an email address, and so forth. When the above changes occur, it may be difficult to convey information to all other members and member devices.

Disclosure of Invention

According to one aspect of the present invention, there is provided a social networking system that supports interaction with at least a first human member and a second human member, the social networking system comprising: a processing system operable to support creation of a first social network group having first group capabilities and a second social network group having members including the first human member and the second human member; the processing system is operable to also support a first docking method comprising: associating the first social network group with the second social network to provide the first group capability to members of the second social network group; and the processing system is operable to transmit data to members of the second social network group to support presentation of the first group capability.

Wherein, in response to an input, the processing system changes the association of the first social network group with the second social network group.

Wherein the processing system is operable to transmit data to members of the second social network group to support presentation of a representation of the first group capability that enables the members to access the first group capability.

Wherein: the first social network group comprises a first plurality of social network groups; the first group capability comprises a capability of at least one of the first plurality of social network groups; and the representation includes a view of the first group capability independent of a view of the first plurality of social network groups.

Wherein the processing system is operable to communicate data to members of the second social network group to enable a first representation of the first group capability to be presented to at least a first member of the second social network group and a second representation of the first group capability to be presented to at least a second member of the second social network group, the first representation being different from the second representation.

The second social network group is a guest social network group, the first docking method is an ad hoc docking method, and the ad hoc docking method comprises the following steps: associating a guest member with the guest social network group and associating the guest social network group with the first social network group.

Wherein, the social network system comprises: the processing system is operable to establish at least one docking specification that includes a condition that the first social network group may be associated with the second social network group; the processing system is operable to manage access to the first group capability by members of the second social network group based on the at least one docking specification; and the processing system is operable to change the association of the member social network group with the merged social network group as specified by the at least one docking specification.

Wherein: the processing system is operable to associate the second social network group with a third-party social network group, the processing system operable to manage access by members of the third-party social network group to at least one of information included in the second social network group and the first group capability based on the at least one docking specification.

According to another aspect of the present invention, there is provided an apparatus for supporting users interacting with a social network, the apparatus comprising: an interface configured to communicatively couple with a social network; and processing circuitry interoperable with the interface to: interact with a social network to join the first social network group to the second social network group.

Wherein the processing circuit is interoperable with the interface to: the ability to interface the device to a first social network group, and to access the second social network group.

Wherein the second social network group comprises a plurality of social network groups, and the capability of the second social network group is the capability of at least one of the plurality of social network groups.

Wherein the processing circuit is interoperable with the interface to: displaying, on a user interface, a representation of a second social network group associated with the first social network group, the representation including a representation of an ability of the second social network group independent of at least one of the plurality of social network groups; and determining a user input based on user interaction with the representation via a user interface based on an ability of the user input to access the second social network group.

Wherein the processing circuit is interoperable with the interface to: associating a third-party social network group with the first social network group, such that members of the third-party social network group may access at least some information associated with the first social network group via a docking method; and in response to the input, managing access to the first social network group by the third party social network group member.

Wherein the processing circuit is interoperable with the interface to: in response to receiving an input, interacting with the social network to disassociate the first social network group from the second social network group.

Wherein the processing circuit is interoperable with the interface to: interact with the social network via a docking method to associate the first social network group with the second social network group based on a geographic proximity of the device to a geographic location associated with the second social network group; and in response to determining that the geographic proximity of the device to the geographic location associated with the second social network group exceeds a threshold, interacting with the social network to disassociate the first social network group from the second social network group.

According to another aspect of the invention, there is provided a method performed by a social networking system, the method comprising: maintaining a first social network group through which a first group service is provided; maintaining a second social network group to support the first and second human members via the first and second devices, respectively; and responding to a group-group docking request received by having both a first device and a second device access the first group service, the group-group docking request originating from an interaction with the first device.

Wherein the group-group docking request is a request to associate the first social network group with the second social network group to provide at least some of the first group services to at least one of the first device and the second device.

The method comprises the following steps: responding to a group-group docking request received by having both the first device and the second device access the first group service, the first group service being provided by at least one of a plurality of social network groups, via a representation, and the representation including a representation of the first group service unrelated to the at least one of the plurality of social network groups.

The method comprises the following steps: based on a docking specification resulting from interaction with the first device, causing the second device to have limited access to the first group service.

Wherein the first group service includes at least one of a gaming service and access to a wagering apparatus.

Drawings

FIG. 1 illustrates a schematic block diagram of a social networking packet hierarchy in accordance with various embodiments of the present invention;

FIG. 2 illustrates a schematic block diagram representation according to various embodiments of the present invention;

FIG. 3 illustrates a schematic block diagram of a social networking packet hierarchy in accordance with various embodiments of the present invention;

FIG. 4 illustrates a schematic block diagram according to various embodiments of the present invention;

FIG. 5 illustrates a timing diagram depicting a travel social network according to various embodiments of the invention;

FIG. 6 illustrates a flow diagram according to various embodiments of the invention;

FIG. 7 illustrates a flow diagram according to various embodiments of the invention;

FIG. 8 illustrates a flow diagram according to various embodiments of the invention;

FIG. 9 illustrates an embodiment of a social network environment, according to various embodiments of the invention;

FIG. 10 illustrates a social network infrastructure and social devices in accordance with various embodiments of the invention;

FIG. 11 illustrates a schematic block diagram of an embodiment of a social device, according to various embodiments of the present invention;

FIG. 12 illustrates a schematic block diagram showing social resource access for a social network group/sub-group in accordance with various embodiments of the present invention;

FIG. 13 illustrates a schematic block diagram of an embodiment of a social device/server incorporating communication and control protocol capabilities in accordance with various embodiments of the present invention;

FIG. 14 illustrates social device members and access in a social network group/subgroup according to various embodiments of the present invention;

FIG. 15 illustrates social resource remote access of a social network group/sub-group in accordance with various embodiments of the invention;

FIG. 16 illustrates a schematic block diagram of an embodiment of a social device including full resource access and allocation management functionality in accordance with various embodiments of the present invention; and

FIG. 17 illustrates a social device including integrated functionality operable to support social network group/subgroup membership and communication in accordance with various embodiments of the present invention.

Detailed Description

As used herein, the terms "social network," "SNET," "social networking system," "social networking infrastructure," and the like include a grouping or social structure of devices and/or individuals as well as connections, links, and interdependencies between the devices and/or individuals. Members or participants (including devices) within or having a relationship to a SNET may be referred to herein as "members," users, "" members, "" nodes, "" social devices, "" SNET members, "" SNET devices, "" user devices, "and/or" modules. Further, the terms "social circle," "social group," "SNET circle," "SNET group," and "SNET subgroup" generally refer to SNET that includes SNET devices, including human SNET members, device SNET members, personal area networks ("PANs"), and the like, as the context dictates.

Referring now to fig. 1, a social networking (hereinafter "SNET") grouping hierarchy 100 is illustrated, in accordance with various embodiments of the present invention. In some embodiments, SNET grouping hierarchy 100 includes one or more levels of SNET infrastructure, at least partially surrounded by SNET, which may be interfaced to (hereinafter interchangeably referred to as "associated," "connected," etc.) other SNET infrastructures, SNET groups, social devices, and the like. For example, in the illustrated embodiment, one level of the SNET grouping hierarchy 100 may include a serving SNET infrastructure 101 and another level of the SNET grouping hierarchy 100 may include one or more client SNET infrastructures 103, 105 and 107. In some implementations, the various hierarchies can be docked such that a "higher" hierarchy can be docked to a "lower" hierarchy to provide the "lower" hierarchy with access to the various capabilities provided by the "higher" hierarchy.

In some implementations, one or more infrastructures are managed by one or more processing systems, computers, service devices, network nodes, social devices, some combination thereof, and the like. For example, in the illustrated embodiment, service SNET infrastructure 101, some or all of one or more client SNET infrastructures 103, 105, and 107, some combination thereof, and/or the like, may be managed by one or more social service support devices 111, one or more client social devices 131, 141, and 151, some combination thereof, and/or the like. A processing system may include, but is not limited to, one or more instances of processing circuitry distributed across one or more server devices, network nodes, some combination thereof, and the like.

For example, in the illustrated embodiment, SNET grouping hierarchy 100 includes a serving SNET infrastructure 101 in a first hierarchy and a plurality of client SNET infrastructures 103, 105, and 107 in a second hierarchy. The infrastructure may include, but is not limited to, one or more SNET groups, one or more services, applications, resources, devices, etc. associated with one or more entities, which may include, but is not limited to, clients, SNET members, SNET non-members, SNET guests, some combination thereof, and the like. For example, service SNET infrastructure 101 may include, but is not limited to, user device 111, application 113, and SNET groups 115, 117, and 119 associated with one or more services. Client SNET infrastructure 103 may include one or more client SNET groups 135 and one or more social devices 131 associated with one or more particular clients (hereinafter interchangeably referred to as users, members, visitors, guests, etc.). For example, the first client infrastructure 103 can include one or more SNET groups 135 associated with SNET members and one or more social devices 131 associated with SNET members. As shown in the illustrated embodiment, the social devices 131 in the client infrastructure 103 may interface, associate, connect, etc. with a SNET group associated with the client. At least one docking method is discussed in more detail in at least U.S. utility patent application serial No. 13/408,986, entitled "social device resource management" (attorney docket No. BP 23776), filed 2 months and 29 days 2012, the entire contents of which are incorporated herein by reference. In some embodiments, a device docked to another SNET group, a SNET group, etc. becomes a member of the docked SNET group. By interfacing client social device 131 to client SNET group 135, a user associated with client SNET group 135 may interact with SNET group 135 by interacting with social device 131 interfaced to SNET group 135. As noted herein, a member, client, user, etc. may include, but is not limited to, a human member of SNET or some other network, a device member of SNET or some other network, some combination thereof, etc.

In some embodiments, one or more capabilities (including but not limited to various services, applications, SNET groups, some combination thereof, etc.) are mixed, combined, merged, some combination thereof, etc. via a docking method into one or more SNET groups that can provide access to desired capability selections by interacting with the one or more SNET groups. For example, the service SNET infrastructure 101 illustrates capabilities that may be provided by various services supporting social user devices 111, various social service applications 113, and so forth. In some implementations, access to various service supporting social user devices 111, either directly or through interaction with a SNET group 115 that interfaces to the service supporting social user devices 111, and access to various social service applications 113, either directly or through interaction with a SNET group 119 that interfaces to the social service applications 113, and the like, may be provided to SNET members. One or more capabilities provided by the device 111 and the application 113, the SNET groups 115 and 119 interfaced to the device 111 and the application 113, some combination thereof, and/or the like, may be combined into a single SNET group that may provide access to one or more capabilities provided by the device, the service, the application, the SNET group, some combination thereof, and/or the like.

For example, a user of the client SNET infrastructure 103 may obtain access to the capabilities provided by both SNET groups 115 and 119 by interfacing with SNET group 117 by interfacing social device 131 to a single SNET group 117 (self-combining SNET groups 115 and 119) via interfacing method 125.

In some embodiments, access to capabilities provided by one or more SNET groups, infrastructure, etc. may be accomplished by interfacing one SNET group to another SNET group. For example, client SNET group 135 may interface to SNET group 117 via interfacing method 125, thereby enabling a user of client infrastructure 103 to access capabilities provided by SNET group 117 through client SNET group 135. In particular, where one or more social devices 131 are interfaced to client SNET group 135, a user may access the capabilities provided by SNET group 117 via one or more of social devices 131 interfaced with client SNET group 135. The docking method 125 may include: connecting client SNET group 135 as SNET group 117 members; interfacing (also referred to herein as "associating") client SNET group 135 to SNET group 117 via one of various processes described herein and at least in the following: U.S. utility model patent application serial No. 13/342,301, entitled "social networking device members and applications", (attorney docket No. BP 23711), filed 1/3/2012, U.S. utility model patent application serial No. 13/408,986, entitled "social device resource management", (attorney docket No. BP 23776), filed 2/29/2012, each of which is incorporated herein by reference in its entirety.

As shown in the above embodiments, a user entering a venue including, but not limited to, a store, restaurant, hotel, enterprise, public area, etc. may desire access to capabilities including, but not limited to, services, applications, information, devices, some combination thereof, etc. provided by a SNET group associated with the venue. A user may simply dock a personal SNET group docked to a user device with a SNET group associated with a venue, rather than individually docking individual user devices with the SNET group, permitting the user to access venue capabilities through some or all of the devices that the user has docked with his personal SNET group. As yet another example, a hotel may provide various capabilities through a SNET group, including but not limited to call routing telephony service access, specific television device control, database access, some combination thereof, and the like. Rather than docking his personal device separately to the hotel SNET group to take advantage of the capabilities provided, the guest may simply dock his personal SNET group to the hotel SNET group and then access the capabilities provided by the hotel SNET group through the device docked with his personal SNET group, including but not limited to: docking a smartphone device to a hotel SNET group to utilize call routing telephony services, docking a computer device to a hotel SNET group to control a particular television device, and so forth.

In some implementations, the SNET groups are docked so that users, members, clients, etc. can access the capabilities provided by the various services, devices, SNET groups, etc. associated with the various SNET infrastructures to enhance security. For example, where a user associated with first client SNET infrastructure 103 has access to only capabilities provided by serving SNET infrastructure 101 by interfacing with SNET group 117, various levels of security may be utilized by one or more processing systems, devices, etc. associated with serving SNET infrastructure 101, client SNET infrastructure 103, etc. to ensure capability access. Further, in some embodiments, an additional level of security is provided by the SNET infrastructure by interfacing the access capabilities provided by two or more groups. For example, where access to capabilities provided by serving SNET infrastructure 101 requires interfacing client SNET groups 135, 145, 155, etc. to SNET group 117, more secure connections with various security levels may be utilized, and capability access may be readily granted, changed, restricted, terminated, etc. via a single interface, association, etc. management between the client SNET group and SNET group 117. Processing systems, devices, etc. associated with service SNET infrastructure 101, client SNET infrastructure 103, etc. may manage the association based on input received from a user, a third party entity, some internal logic device, the passage of a time period, a change in geographic location of client social device 131 associated with client SNET infrastructure 103, some other triggering event, some combination thereof, etc.

In some embodiments, the selection and docking method 125 may be automated, some combination thereof, and the like. For example, by triggering based on infrastructure user location, the docking method may be automatic, including but not limited to geographic proximity of users docked with a particular client SNET group 135, users associated with social devices 131, one or more of social devices 131, some combination thereof, and so forth. In some implementations, a user can provide one or more associated rules that can provide conditions under which one or more particular client SNET groups 135 can interface to other SNET groups. Conditions may include, but are not limited to, a geographic proximity of one or more social devices 131 that are docked to a particular client social device 135 to a geographic location associated with SNET group 117, which SNET group 117 is authorized by a user associated with infrastructure 103, SNET group 135, social device 131, some combination thereof, and/or the like, to dock client SNET group 135 with SNET group 117, some combination thereof, and/or the like. The associated rules may be communicated to the social devices 131 that interface with a particular SNET group 135, a processing system that manages the various SNET group interfaces, some combination thereof, and so forth. One or more of processing system, social device 131, some combination thereof, etc. may monitor one or more of client SNET group 135, social device 131 docked to client SNET group 135, one or more attributes of one or more SNET groups 117 related to one or more attributes of one or more client SNET groups 135, docked social device 131, some combination thereof, etc. (related to one or more associated rules) to determine whether to dock one or more SNET groups, social devices, etc. together. The associated rule may be changed by a user, a processing system, some other entity, etc., on the fly to create a new rule, delete a rule, change a rule, etc. For example, a user associated with client SNET group 135 (which may have previously communicated an associated rule to the processing system that prohibits docking client SNET group 135 to SNET group 117 outside of a threshold geographic proximity of social device 131) may communicate associated rule changes on-the-fly, including but not limited to: changing the threshold geographic proximity; authorizing on an item-by-item basis docking of client SNET group 135 to a particular SNET group 117; ordering the client SNET group 135 to be undocked from another SNET group; some combination thereof, and the like.

In some embodiments, the various levels of SNET grouping hierarchy 100 are subject to various levels of information access. For example, in the illustrated embodiment, a user of "higher level" service SNET infrastructure 101 may be able to view respective client SNET groups 135, 145, and 155 associated with "lower level" client SNET infrastructures 103, 105, and 107 that are docked to SNET group 117 associated with social service infrastructure 101. Users of service SNET infrastructure 101 may also be able to view various social devices 131, 141, and 151, which various social devices 131, 141, and 151 are interfaced to various client SNET groups 135, 145, and 155. In another example, one or more users of a "lower level" infrastructure (including but not limited to client SNET infrastructures 103, 105, and 107) may be able to view some or all of the capabilities provided by SNET groups associated with a "higher level" infrastructure (docked to SNET groups associated with a "lower level" infrastructure), but not able to view some or all of the capabilities of a "higher level" infrastructure, including but not limited to initially providing various SNET groups 115 and 119, providing capabilities from various SNET groups 115 and 119. Furthermore, a "lower level" infrastructure user accessing SNET group 117 associated with "higher level" service SNET infrastructure 101 may not be able to view some or all of the other similar "lower level" client SNET infrastructures 105 and 107 (also interfacing with the same SNET group 117).

In some embodiments, the selection and docking method 125 may be controlled, managed, etc. by one or more different social devices, processing systems, etc. For example, a SNET infrastructure processing system (which may include one or more instances of processing circuitry distributed across one or more server devices, network nodes, some combination thereof, etc.) may control docking and undocking of one SNET group to another SNET group based on user interaction with the SNET, one or more associated rules, one or more inputs, some internal logic, some combination thereof, etc. As another example, a social device may control the docking and undocking of one or more SNET groups based on user interaction with the SNET, one or more associated rules, one or more inputs, some internal logic, some combination thereof, and/or the like. In some implementations, a processing system authorized to manage a "higher-level" infrastructure, a social device, some combination thereof, or the like, may manage one or more attributes accessed by one or more "lower-level" infrastructures interfaced to the "higher-level" infrastructure. For example, a processing system authorized to control the "higher-level" social services infrastructure 101 may change access to certain capabilities based on input, some other logic, restrict access to certain capabilities, terminate access via undocking of SNET groups and devices, some combination thereof, and so forth. The processing system may determine that a triggering event (including, but not limited to, all social devices 131 docked to client SNET group 135 docked to SNET group 117 have exceeded a predetermined threshold geographic proximity distance from a geographic location associated with SNET group 117), based on the determination, undock client SNET group 135 from SNET group 117, partially or completely limit client SNET group 135 from accessing certain capabilities provided by SNET group 117, some combination thereof, and/or the like.

Referring now to FIG. 2, various representations according to various embodiments will be discussed. In some implementations, via one or more interfacing SNET groups, social devices, some combination thereof, or the like, a user, SNET member, SNET non-member, or the like associated with a first infrastructure that interfaces with a second infrastructure may access capabilities provided by the second infrastructure by interacting with a representation that may be part of data provided by a processing system, some portion of the second infrastructure, some portion of the first infrastructure, a social device associated with the first infrastructure, a second device associated with the user, some combination thereof, or the like. For example, where the client SNET group 135 of the first social client infrastructure 103 interfaces with the SNET group 117 of the social service infrastructure 101 (providing the device access capabilities 111 and 113 provided by SNET groups 115 and 119) as shown above in fig. 1, a user may access the capabilities provided by SNET group 117 via interaction with the representation 201 (as part of data provided by one or more SNET systems, SNET infrastructures, SNET groups, SNET devices, some combination thereof, and so forth). Where client SNET group 135 interfaces with one or more client social devices 131, a user may interact with some portion of one or more social devices 131 to access capabilities provided by SNET group 117 via client SNET group 135, directly via social devices 131, some combination thereof, or the like.

In some implementations, the representation can provide a simplified representation of the capabilities that are accessible via docking of one or more SNET groups. For example, while SNET group 117 provides capabilities 111 and 113 by merging SNET groups 115 and 119 (providing capabilities 111 and 113), representation 201 provided to members accessing SNET group 117 via docking client SNET group 135, social device 131 docked to docking client SNET group 135, some combination thereof, and so forth, may only show the ability to provide real complexity indications by SNET group 117 with little or no groups 115 and 119 (combined to make it possible for SNET group 117 to provide capabilities 111 and 113). Members accessing capabilities 111 and 113 via representation 201 can access capabilities 111 and 113 by interacting with the capability representations included in representation 201 (as part of data provided by one or more SNETs, SNET systems, SNET infrastructures, processing systems, devices, SNET groups, some combination thereof, and so forth). In some implementations, interaction with representation 201 may continue via interaction with some portion of docking social device 131, including but not limited to a user interface, docking a portion of client SNET group 135, some combination thereof, and so forth.

In some implementations, one or more third party SNET groups associated with individual members, infrastructure, etc. interface with the first SNET group to enable third party SNET group members to access some or all of the information associated with the first SNET group, the capabilities provided by the interfacing SNET group, some combination thereof, and so forth. For example, in the illustrated embodiment, client SNET group 145 may be interfaced to client SNET group 135, thereby enabling client SNET group 145 to access some or all of the information provided to members of client SNET group 135, the capabilities provided by SNET group 117 interfaced to client SNET group 135, some combination thereof, and so forth.

As the above example, a traveler may desire to interface a group 145 of client SNETs associated with his company to a group 135 of personal client SNETs associated with his business trip. By interfacing with the corporate client SNET group 145, a traveler may make it possible for corporate client group 145 members to view the traveler's whereabouts (as they are provided to his personal client SNET group 135), access at least some of the ability to be provided to the traveler by interfacing with other SNET groups via the same or similar representation 201 (e.g., access and manage his travel reservations, provide relevant travel and business updates to the traveler on-the-fly, etc.), some combination thereof, and so forth. The docking may be managed by the traveler social device 131, the social service infrastructure 101 based on input provided by the traveler, one or more other devices, some combination thereof, and so forth. For example, a traveler may only authorize docking third party SNET group 145 to have limited access to information associated with his personal client SNET group 135, limited access to capabilities provided by docking SNET group 117, etc., and the traveler may authorize access to be limited, undocked, some combination thereof, etc., based on instant input, one or more triggering events, etc. The triggering events may include, but are not limited to: a change in geographic location associated with one or more social devices 131 associated with the traveler, a change in authorization information provided by the entity, etc.

In some embodiments, different representations may be provided where individual SNET groups, SNET devices, etc. associated with a "lower level" infrastructure are interfaced to a "higher level" infrastructure in a SNET grouping hierarchy. In the illustrated embodiment, for example, client SNET group 135 and client SNET group 155 (associated with first social client infrastructure 103 and nth social client infrastructure 105, respectively) are each docked to SNET group 117 associated with social service infrastructure 101. In the illustrated embodiment, a first representation 201 is provided to members accessing the ability of SNET group 117 via client SNET group 135, docking social device 131, some combination thereof, and the like, and an nth representation 203 is provided to members accessing the ability of SNET group 117 via client SNET group 155, docking social device 151, some combination thereof, and the like. In some embodiments, the representations provided to the individual docked SNET groups are different, separate, etc. with respect to each other. For example, in implementations where the SNET group 117 provides capabilities associated with a hotel experience (including, but not limited to, remote control of television devices and docking client SNET groups 135, 155, etc. associated with individual hotel guests), the capabilities provided via one or more individual representations may be different such that the hotel guest may have access to the capabilities customized for the guest, including, but not limited to, remote control of a particular television device associated with the hotel room. In the event that the guest is not a SNET member, the guest may be invited to create a temporary SNET group, a guest SNET group, an ad hoc (ad hoc) SNET group, some combination thereof, or the like, and then dock the created SNET group to another SNET group to access the capabilities provided by the other SNET group.

Referring now to fig. 3, some embodiments of SNET packet hierarchy 300 may enable client SNET group 135 to interface to SNET groups that provide capabilities from various infrastructures. In the illustrated embodiment, the two infrastructures 301 and 303 are combined, docked, associated, etc., to provide capabilities from both infrastructures 301 and 303 through a single combined SNET cohort 337. The global social service infrastructure 301 includes capabilities provided by a social service support user device 311, a social service application 313, and various SNET groups 315, 319, and 317 that provide some combination of the capabilities provided by the infrastructure 301. In addition, local/regional social service infrastructure 303 also includes capabilities provided by social service support user devices 321, social service applications 323, and various SNET groups 325, 329, and 327 (which provide some combination of the capabilities provided by infrastructure 303). Combined local/regional and global SNET group 337 provides a combination of the capabilities provided by social service support user devices 311 and 321 and the social service applications 313 and 323 provided by the two infrastructures 301 and 303. In the event that client SNET group 135 can interface with SNET group 337, client SNET group 135 members will have access to the capabilities provided by both infrastructures by interfacing a single client SNET group with a single SNET group 337.

In some embodiments, representation 305 provided to members of client SNET group 135 (accessing capabilities provided by SNET group 337) includes only combined capabilities provided by both infrastructures 301 and 303 independent of some or all indications of the infrastructure (that originally provided some or all of the capabilities). In the illustrated embodiment, for example, the capabilities provided by the social service support user devices 331 and 321 from the two infrastructures 301 and 303 are presented in the representation 305 in a combined set of social service support user devices 331; likewise, social service applications 313 and 323 from both infrastructures 301 and 303 are presented in the representation 305 in a combined set of social service applications 313. Furthermore, SNET groups 315, 317, 319, 325, 327, and 329 in the infrastructure partially or fully assembled as SNET group 337 may be partially or fully transparent to accessing the members of capability representation 305 provided by SNET group 337. In some implementations, a member accessing representation 305 can restore the overall complexity of the combination of infrastructures 301 and 303 in representation 305 so that the member can view various SNET groups and capabilities specific to various infrastructures and capabilities provided.

As an example of the illustrated embodiment, a chain of hotels may provide a global SNET infrastructure 301 that provides capabilities common to franchising all hotels, such as a global media database, business contact information, an information database, some combination thereof, and so forth. Further, a local hotel may desire to have a local SNET infrastructure 303, the local SNET infrastructure 303 providing access to local entertainment, dining, news information, devices, device access specific to the local hotel, some combination thereof, and the like. The hotel may desire to combine the chain of hotel capabilities provided by the global SNET infrastructure 301 with local specific capabilities provided by the local SNET infrastructure into a combined SNET group 337 to enable hotel guests to access the global and local capabilities using a single docking method and via a single representation 305 (providing partial or full combined global and local capabilities).

In some implementations, the combination of capabilities provided by the individual infrastructures is partially or fully managed by one or more processing systems, social devices, members, applications, some combination thereof, and/or the like (associated with one or more infrastructures). For example, in the illustrated embodiment, a processing system associated with local SNET infrastructure 303 may manage combining capabilities from infrastructures 301 and 303 into SNET group 337, manage interfacing client SNET group 135 with SNET group 337, some combination thereof, and so forth.

In some implementations, access to SNET group 337 by client SNET group 135 may be granted, limited, terminated, etc. by a network manager, processing system, social device, some combination thereof, etc., based on input, a triggering event, some other internal logic, etc. For example, when a social device docked with client social device 135 leaves a venue associated with SNET group 337, client SNET group 135 may be terminated from accessing the capabilities provided by SNET group 337 by terminating or limiting access permitted by the docking, changing interaction authorization with some or all of the capabilities provided by SNET group 337, undocking client social device 135 from SNET group 337, some combination thereof, or the like. This may occur automatically in response to a triggering event, including but not limited to the passage of a predetermined time after entering or leaving the venue, etc. In some implementations, client SNET group 135 may retain residual access to SNET group 337 after a device docked to client SNET group 135 leaves the venue. For example, where the venue associated with SNET group 337 is a hotel and the members associated with client SNET group 135 belong to unique hotel members, client SNET group 135 associated with the members still receives at least some access to the capabilities provided by SNET group 337 after the docking device leaves the venue, including but not limited to call routing telephony services.

In some embodiments, a SNET group associated with a member (including a human, a device, etc.) may be docked to another SNET group to enable the member to access or receive services, contact information, other information associated with the SNET group, exchange information, some combination thereof, and/or the like. The member may be an existing member of SNET, a non-member (also referred to herein as a third party), and the like. For example, a human user having a device may be within a threshold (such as proximity) of a venue access point or the like, based on which the access point, some other device associated with the venue, or the like provides an invitation to connect to a SNET group associated with the venue to the human user via the device, to the device itself, some combination thereof, or the like. The invitation may change depending on whether one or both of the human user and the device are already a SNET member, a non-member, etc. For example, where the device is not a social device, the access point may provide the invitation to the device in the form of a web page via a browser application or the like that provides the device, a human user, some combination thereof, or the like with an ad hoc membership join SNET group option. Where the device is a social device, the invitation may include interfacing the SNET group with a SNET group associated with the venue via a social interface, user interface, etc. located on the device.

The invitation may be accepted via one of various acceptance methods. For example, where a social device receives an invitation (a SNET group that includes a unique identifier that uniquely identifies the inviting member to the SNET group, social device, etc.), the social device may interact with an access point, another device, SNET group, SNET subgroup, etc., via an independent pathway, etc., to accept the invitation with the unique identifier. Accepting in the above example may include simply providing a unique identifier based on which the SNET group is docked to the SNET group associated with the venue, and information identifying the SNET group associated with the provision of the unique identifier. Further, in the event that the non-social device attempts to access the access point and the access point pushes the web page to a browser application on the non-social device, the method of acceptance may comprise: access a web page, indicate a willingness to interface with a SNET group, provide some other information, etc., such that a non-social device, an ad hoc guest SNET group, some combination thereof, etc., is accepted as interfacing to a SNET group associated with a venue.

Upon accepting the invitation, the member, the human user, the device, some combination thereof, or the like may obtain at least some access to the capabilities provided by the SNET group associated with the venue. For example, where the venue is a coffee shop, a member of a personal SNET group docked to the SNET group associated with the venue may gain access to various services including, but not limited to, online newspapers, videos, item sales listings, delivery options, on-site delivery ordering interfaces, other information, some combination thereof, and the like, via one or more devices docked to his personal SNET group. In another example, where the venue is a hotel, private home, etc., a member of a personal SNET group docked to the venue-based SNET group may gain access to services, information, etc., including, but not limited to, access to locally or remotely stored content items, contact information, access to field device control functions, some combination thereof, etc., via one or more devices docked to his personal SNET group. In another example, where the venue is a shopping mall, the access point may provide, push, etc. the invitation to the device, the device user, some combination thereof, etc. to interface to a SNET group associated with the mall. The access point may require the device, user, etc. to attempt to access the access point before an invitation is provided to the device, user, etc. in the form of a unique identifier, web page, etc. Services associated with a SNET group may include, but are not limited to: advertising, sales and coupon information, etc. provided by computing devices at various stores within a mall; a mall map service showing specific store locations docked to the SNET group; a marketplace music service that provides music or other media content provided by media sources associated with the SNET group for those docked to the SNET group; a telephone directory service; a search engine related to anything in any store in a mall; some combination thereof, and the like.

In some embodiments, the access point supports invitation provisioning for interfacing to a SNET group, invitation processing acceptance, routing communications between members, ad hoc members, and potential members of the SNET group, and the SNET, SNET group, and the like. The device may need to attempt to access the access point to receive the invitation provided by the access point. In some implementations, the access point automatically provides an invitation to any device that the access point determines has crossed a threshold, such as a predetermined proximity to a venue, location, etc. Those that interface to a SNET group (including an ad hoc member, a SNET group, an ad hoc SNET group, some combination thereof, etc.) may be able to couple with other devices, users, members, etc. that also interface with the SNET group. After crossing another or the same threshold, docking to the SNET group may be terminated or restricted. For example, where a device entering a venue is provided ad hoc docking to a SNET group through an access point, the access point may restrict, terminate, etc. ad hoc docking after determining that the device has left the venue.

Fig. 4 illustrates interactions between various SNET systems, infrastructures, groups, devices, etc., according to various embodiments. In the illustrated embodiment, SNET infrastructure 402 (which may be included in a SNET, SNET system, SNET infrastructure, some combination thereof, etc.) may include one or more different SNET groups, social devices, some combination thereof, etc. For example, infrastructure 402 may represent SNET infrastructure associated with SNET, a SNET group, a processing system, a SNET account, a SNET member, a human, a device, a social device, some combination thereof, and the like.

In some embodiments, various SNET groups are created by the SNET infrastructure based on input from a user, a member, a processing system, a device, a SNET group, some combination thereof, and the like. For example, where SNET infrastructure 402 is associated with SNET member accounts, the account members may provide input to SNET infrastructure 402 to create SNET group 404. The input may include, but is not limited to, a social device to interface with the group 404, attributes of the group 404, information that may access one or more members of the group 404, some combination thereof, and so forth.

In some embodiments, a group of SNETs in the SNET infrastructure interfaces with another group of SNETs. For example, in the illustrated embodiment, SNET group 404 interfaces with SNET group 412 and SNET group 414 via interfacing links 407 and 409, respectively. Docking one SNET group to another SNET group may be accomplished via one or more different docking methods, including but not limited to docking unique initialization by one or more devices, SNET groups, or the like.

In some embodiments, the docking method may include an interaction between at least the first group of SNETs and the second group of SNETs. For example, where SNET group 412 is docked to SNET group 404 via docking link 407, SNET group 412 and SNET group 404 may exchange security information processing, etc., with reference to one or more members, docking devices, functional elements, accessible information, some combination thereof, etc., between the two SNET groups. The exchange may enable additional security verification of proper interaction and access between two SNET groups, their respective members, and the like. In some embodiments, additional security processing (such as human validation requirements) is utilized to ensure secure access to one or more docking SNET groups, devices, members, and the like.

In some embodiments, the docking method may include various actions performed by one or more of SNET, SNET system, SNET infrastructure, processing system, SNET group, social device, user, member, some combination thereof, and the like, which may include, but are not limited to: verifying the optimal docking position; a representation of the docking link to the user, member, etc. For example, where a user associated with SNET infrastructure 402 interacts with SNET infrastructure 402 to interface SNET group 420 to a portion of SNET infrastructure 402 to access various capabilities of a SNET group included in SNET infrastructure 424, docking methods to associate SNET group 420 with another SNET group in SNET infrastructure 424, docking, etc. may include, but are not limited to: determining a best docking configuration between SNET group 420 and one or more different SNET groups in SNET infrastructure 424 to enable members of SNET group 420 to access one or more capabilities of SNET infrastructure 424. As shown in the illustrated embodiment, in the event that the best docking configuration is determined to include, but is not limited to, docking a SNET group to both SNET groups 432 and 434 to access capabilities, SNET group 420 may dock with both SNET groups 432 via docking link 446 and with SNET group 434 via docking link 444 as part of a single docking method that associates SNET group 420 with certain capabilities provided by the various SNET groups in SNET infrastructure 424. Docking links 446 and 444 may be managed by a single docking specification 442, some other combination of docking specifications that are part of SNET infrastructure 424, some combination thereof, and so forth. In some embodiments, the docking links and docking specifications may be docked, associated, etc. in a one-to-one type relationship, a one-to-many type relationship, a many-to-one type relationship, some combination thereof, etc.

In some implementations, the docking method to associate SNET group 420 with SNET infrastructure 424 via docking with two SNET groups 432 and 434 may include: the docking link representation is configured such that members with access capability do not see the entire complexity of docking links, interactions, etc. between various SNET groups, devices, SNET infrastructures, etc. In the illustrated embodiment, for example, a docking method of docking SNET group 420 with SNET groups 432 and 434 may include: representations, etc. of the capabilities of SNET group 424 accessible by SNET group 420 members are configured to hide the fact that SNET group 420 is docked to both SNET groups via two docking links. A simplified representation, etc. may only present SNET group 420 views that interface with certain capabilities of SNET infrastructure 424. In some implementations, members can adjust, toggle, or otherwise manipulate the complexity of the representations, representation graphs, or the like such that a partial or entire view of the complexity of interfacing links, interactions, or the like between SNET infrastructures, SNET groups, social devices, or the like is presented to the members.

In some embodiments, establishing multiple docking links may provide additional security for certain capability accesses. For example, where a docking link between SNET group 420 and SNET group 432 provides docking link 446 to SNET group 444 with a higher security link than docking link 444, provides an indirect link to SNET group 432 via docking links 444 and 437, some combination thereof, or the like, the docking method may comprise: docking link 446 is established to provide a more secure link to a certain capability (the link is used to access another capability). In some embodiments, establishing multiple docking links may provide more efficient access to capabilities, services, etc. than a single docking link. For example, where a docking method includes determining that docking links to two SNET groups 432 and 434 may enable more efficient access to certain capabilities of SNET infrastructure 424 than a single docking link, the docking method may include, but is not limited to, establishing multiple docking links 446 and 444 to a SNET group of SNET infrastructure 424.

In some implementations, the docking links between various SNET groups, social devices, and the like are managed based on various docking specifications. In some implementations, the docking specification manages one or more particular docking links, etc., e.g., rather than by means of restrictions, access restrictions, permissions, etc., security access requirements, access cycles, trigger events associated with various capabilities of the SNET group based on which access is to be changed, restricted, permitted, terminated, etc. For example, as shown in the illustrated embodiment, SNET group 404 includes docking specifications 406 and 408. In some embodiments, docking specification 406 may manage docking link 407 between SNET group 404 and SNET group 412. In some embodiments, docking specification 408 manages docking link 409 between SNET group 404 and SNET group 414. The docking specification may be determined in part or in whole in advance by the SNET group 404 members docked in advance (created immediately as part of the docking method that docks SNET group 404 to another SNET group provided by the SNET infrastructure), the SNET group attempting to dock with SNET group 404, some combination thereof, and so forth. For example, a SNET group 404 member may establish a docking specification 406 based on a subsequent triggering event (including, but not limited to, the passage of a time period), which docking specification 406 restricts SNET group 412 members from accessing the capabilities provided by SNET group 404. In some implementations, the docking specification is specific to attributes of other SNET groups and devices such that SNET group 404 is docked to various SNET groups having associated attributes. For example, docking specification 406 may decide that SNET group 404 is to be docked to SNET group 412 via docking link 407 (associated with a geographic location within a predetermined threshold proximity to a geographic location associated with SNET group 404), and if the geographic location associated with SNET group 412 exceeds the proximity threshold, docking link 407 is to be restricted, terminated, etc.

In some embodiments, some or all of the docking specifications may be adjusted, managed, changed, created, deleted, etc. based on input from a user, a member, a SNET system, a SNET infrastructure, a docking device, a docking SNET group, some combination thereof, etc. For example, SNET group 404 members may establish a docking specification 406 with SNET group 412 that manages docking links 407 to restrict certain capabilities of SNET group 412 members to access SNET group 404, and then interact with SNET group 404, SNET infrastructure 402, some combination thereof, and the like to change docking specification 406 to provide SNET group 412 members with more access to the capabilities provided by SNET group 404. The docking specification management may be performed at any time, on-the-fly, in an ad hoc process, etc., with respect to existing docking links, docking specifications that manage potential docking links, some combination thereof, etc.

In some embodiments, a docking specification that manages docking links between a "higher level" SNET group and a "lower level" SNET group is part of the higher level SNET group. For example, in the illustrated embodiment, where SNET group 404 is a higher level SNET group and SNET groups 412 and 414 are lower level SNET groups, docking links 407 and 409 between lower level SNET groups 412 and 414 and higher level SNET group 404 are managed by docking specifications 406 and 408 that are part of higher level SNET group 404, thereby making it possible for higher level SNET groups to control over docking links with lower level SNET groups.

In some implementations, the docking specification can be customized by a user, a member, a SNET system, a SNET infrastructure, a SNET group, a social device, some combination thereof, and the like, to provide various levels of interaction and access between various docked SNET groups. For example, in the illustrated embodiment, docking specification 406 may specify that docking link 407 provide for full bidirectional interaction, sharing of information, services, etc., between SNET groups 404 and 412 docked via docking link 407. In another example, docking specification 408 may specify that docking link 409 provide unidirectional group-group service access between SNET group 404 and SNET group 414 via docking link 409 such that SNET group 414 members may access at least some services provided by SNET group 404 capabilities, while SNET group 404 members may not access some or all of the information, services, devices, etc. associated with SNET group 414. For example, where the SNET group of a hotel guest interfaces with the SNET of the hotel to permit the hotel guest to access hotel services capabilities via the hotel SNET group, the docking specification governing the docking link between the hotel guest SNET group and the hotel SNET group may specify that the hotel guest is restricted from accessing certain capabilities of the hotel SNET group, while the hotel SNET group is restricted from accessing any capabilities of the hotel guest SNET group, including but not limited to accessing devices that interface to the hotel guest SNET group. As discussed above, in some embodiments, the docking specification access and interaction aspects may be changed at any time by various users, members, SNET groups, SNET infrastructure, and the like.

In some embodiments, the docking specification imposes certain limitations on providing, granting, etc., SNET group capabilities to dock SNET group members. For example, docking specification 406 may specify that only certain capabilities of SNET group 404 are provided to SNET group 412 members via docking link 407. Docking specification 406 may also specify that each member of SNET group 412 has different access to different one or more capabilities of SNET group 404. For example, docking specification 406 may specify that each member of SNET group 412 is provided with one or more capabilities that uniquely access SNET group 404.

In some embodiments, interfacing links between various SNET groups enables additional SNET groups to access the capabilities provided by SNET groups indirectly associated, interfaced with, etc. the additional SNET groups. For example, in the illustrated embodiment, with SNET group 404 docked to SNET group 414 via docking link 409, SNET group 414 is docked to SNET group 420 via docking link 418. Docking link 418 is managed by docking specification 416 in SNET group 414. In some embodiments, SNET group 420 members may be granted access to at least some of the capabilities of SNET group 404 (SNET group 414 members are granted access). The ability of a member of SNET group 420 to access SNET group 404 can be determined by various docking specifications, including but not limited to: a docking specification 416 that manages a docking link 418 between SNET group 414 and SNET group 420; and a docking specification 408 that manages docking links 409 between SNET group 404 and SNET group 414. For example, by restricting the ability to access SNET group 404 by a SNET group docked to SNET group 414, docking specification 408 may permit SNET group 414 members to access SNET group 404 certain capabilities via docking link 409. In another example, docking specification 416 may specify that SNET group 420 members may not access the capabilities of other SNET groups, access some capabilities, all capabilities, etc. of other SNET groups, including but not limited to SNET group 404 (docked to SNET group 414).

In some embodiments, various groups of SNETs may dock with one another such that some or all of the docked SNET groups gain access to some or all of the capabilities of other docked SNET groups. In the illustrated embodiment, for example, SNET infrastructure 424 includes SNET group 426, SNET group 426 being docked to SNET group 432 via docking link 429 managed by docking specification 428, and also being docked to SNET group 434 via docking link 431 managed by docking specification 430. Further, SNET group 434 is docked to SNET group 432 via docking link 437 managed by docking specification 436; thus, SNET groups 426, 432, and 434 each interface with one another. Interfacing links between SNET groups 426, 432, and 434 may provide various levels of access including, but not limited to, various levels of security. Further, in some embodiments, interfacing to one of the SNET groups in SNET infrastructure 424 may permit access to some or all of the capabilities of some or all of the SNET groups to which the one of the SNET groups is interfaced.

For example, in the illustrated embodiment, SNET group 404 may be docked to SNET group 426 via docking link 439. Depending on the origination and destination of the communication flow, the communication flowing through docking link 439 may be subject to various docking specifications. For example, the docking specification 438 may manage any attempted access to media content originated from the SNET group 404 via a group member device, memory, service, or the like directly associated with the SNET group 404 via the docking link 439. The access may include, but is not limited to, media content reception, media content provision, identifying media content, information associated with media content, some combination thereof, and so forth. For example, where a foreign SNET group (including, but not limited to, a SNET group associated with a separate SNET infrastructure) is docked to SNET group 404 (including first, second, and third media content originating from SNET group 404 via a group member device, memory, or service, etc. directly associated with SNET group 404), docking specification 438 may specify: 1) the first media content is not identified as existing at least the foreign SNET group; 2) second media content may be identified as existing at least the foreign SNET group, but requiring advanced DRM and being provided at a reduced quality; 3) third media content can be identified as existing at least the foreign SNET group and provided in its original form without redistribution and consumption limitations; some combination thereof, and the like. The docking specification 438 may also restrict SNET group 404 access, allow applications to have imposed the same or further restrictions on SNET group 426, SNET group 404, some combination thereof, and the like. Likewise, docking specification restrictions imposed on data or media content originating from SNET group 414 may permit chained access of SNET groups 426, 434, some combination thereof, and so forth via SNET group 404, SNET group 420, some combination thereof, and so forth.

In addition to the various docking specification limits imposed on local group dedications, various docking specification limits may also be imposed on the chain offerings. For example, SNET group 414 may be free to provide access to all dedications, including but not limited to services, content, data, docking device access, some combination thereof, etc., of any other SNET group via a direct docking link to SNET group 414, via an indirect link to the SNET group (docked to SNET group 414) via a docking link, some combination thereof, etc. In some implementations, the freely provided access may be defined via the docking specification 416. However, docking specification 438 may impose restrictions on access via SNET group 404, including but not limited to: no access, awareness, etc. is allowed with respect to some or all of the dedications from any external SNET group (including but not limited to SNET groups 414, 412, and 420) that interface to SNET group 404. In this way, the dedications can be managed in various ways according to the underlying needs, according to the docking linkage and interlocking SNET group and device specifications. In some embodiments, the linkage and interlock management of the overall dedication is applied twice: once for each access direction. For example, the contribution limit associated with SNET infrastructure 402 may be completely different from the contribution limit of SNET infrastructure 424. Furthermore, even though all relevant docking specifications within SNET infrastructure 402 may at least allow restricted access to specific dedications to SNET group 426, for example, the access may not extend to SNET group 432 because: a) docking specification 428 imposes more access restrictions in addition to those required by SNET infrastructure 402; b) the relevant docking specifications within SNET infrastructure 402 may restrict foreign linkages; some combination thereof, and the like.

For example, in an ad hoc travel network docking configuration, a passenger's personal SNET group configuration (e.g., SNET infrastructure 402) may desire to provide very limited access to a hotel SNET group configuration (e.g., SNET infrastructure 424), while in other directions, hotel SNET group configuration contributions may be freely provided. Each component need only provide access to any dedications, member identifications, information, etc. that they may be exposed to. For example, a traveler may choose to expose a) a payment service element located somewhere within the entire personal SNET group formation; b) incoming message service for passenger social smart phones; c) an incoming message service for the administrator; d) a travel document storage service; some combination thereof, etc., while the hotel may choose to expose capacity, dedications, etc., including but not limited to: 1) regional directories, maps and other information services; 2) a concierge service; 3) a charging service; 4) reserving a service; 5) networking office equipment; some combination thereof, and the like. For example, any exposure may be defined via various docking specifications associated with an originating SNET group modified to a destination SNET group by the docking specifications associated with SNET groups in the chain.

In some embodiments, the docking specification may be extended to provide resolution in addition to the group level. For example, the docking specification 428 that manages the docking link 429 may require human recognition and various levels of security before providing access (even including contribution recognition) via the docking link 429. In another example, as defined by docking specification 428, a traveler (who may be a SNET group 404 member) may gain access to a particular contributor provided by one element, service, or device participating in SNET group 426 via a desired secure interaction with the traveler's local social smartphone docked to SNET group 404, but some or all of the other members of SNET group 404, other SNET groups, etc. may not gain access to the particular contributor. In other words, specific linkage docking specification details may be established to manage overall access, including but not limited to limited access, for one or more specific SNET group dedications, capabilities, dedication identifiers, etc., and for one or more specific group members, member information, etc. Thus, while the functionality is shown as distributed, associated with links, etc., the chain docking specification flow may be managed through a single user interface and may be stored in a single database construct.

In some implementations, the default docking specification can impose default handling of contributions, accesses, interactions, etc. with respect to one or more particular SNET groups, but allow for particular contribution modifications, other access modifications, some combination thereof, etc. as needed to authorize members, devices, SNET systems, SNET groups, SNET infrastructure, some combination thereof, etc. Likewise, the entire default process may also be modified.

In some implementations, the docking specification can be part of one or more SNET groups, SNET infrastructure, social devices, some other entity, some combination thereof, and so forth. For example, where the docking method that docks SNET group 404 to SNET group 426 is initialized by the device that docks SNET group 404, docking specification 438 may be part of SNET group 404. Further, where the docking method of docking SNET group 404 to SNET group 426 includes some portion of SNET infrastructure 424 that receives and grants docking requests from some portion of SNET infrastructure 402, docking specification 438 may be part of SNET group 426. In some embodiments, the docking request may include, but is not limited to: a request to connect one SNET group to another SNET group; capabilities (including but not limited to services, device access, applications, etc.) of the first group of SNETs are provided to one or more devices docked to the second group of SNETs. The docking request may originate from a device docked to the first SNET group, a device docked to the second SNET group, a first SNET group member, a second SNET group member, a third party, some combination thereof, and/or the like.

By interfacing to SNET group 426, SNET group 404 may access some or all of the capabilities of SNET group 432 and SNET group 434, as specified by one or more of the interfacing specifications 438, 428, 430, etc.; conversely, where SNET group 404 interfaces with SNET group 434, SNET group 404 may access some or all of the capabilities of SNET group 426 and SNET group 434, as specified by one or more of interface specifications 438 and 436.

In some implementations, interfacing various SNET groups with various SNET groups in various SNET infrastructures can include various access restrictions and restrictions. For example, with SNET group 404 docked to SNET group 414 (docked to SNET group 420, all SNET groups within SNET infrastructure 402), various levels of interaction and access for the various SNET groups may be determined via management of various docking specifications 408 and 416 that manage the docking links. All three docking SNET groups 404, 414, and 420 are capable of accessing some or all of the mutual capabilities, SNET group 414 is capable of accessing the capabilities of SNET group 404, while SNET group 404 is capable of accessing SNET group 414, SNET groups 404 and 414 are capable of accessing the mutual capabilities, while SNET group 420 is capable of accessing some of the capabilities of SNET group 404 and some of the capabilities of SNET group 414, some combination thereof, and so forth. The interaction, access, docking, etc. may be performed without any interaction with third party entities, third party SNET groups, etc.

In some embodiments, where a third party entity, a third party SNET group, or the like is included in the docking link, additional interaction with the third party entity, the third party SNET group, or the like is required. For example, where SNET group 404 is docked to SNET group 426, docking, accessing, etc. may require interaction with a third party where the respective SNET group is part of a separate SNET infrastructure associated with individual users, members, etc. Interactions may include, but are not limited to, security challenges, acceptances, invitations, etc. to SNET group 404 members attempting to access SNET group 426 capabilities. In some embodiments, the interfacing methods between SNET groups associated with individual SNET infrastructures, users, members, and the like may be initialized, managed, and the like by various devices, processing systems, SNET infrastructures, and the like. For example, docking between SNET group 404 and SNET group 426 may be initiated, managed, etc. by one or more devices docked to SNET group 404, one or more devices docked to SNET group 426, one or more devices docked to a third party SNET group, one or more processing systems, one or more SNET infrastructures, some combination thereof, etc.

In some embodiments, a SNET "travel" group facilitates and/or monitors travel activities, activities associated with aspects of a social device, aspects associated with a social device, a SNET group associated with a member, some combination thereof, and/or the like. An activity may include one or more events (which may include a triggering event) that may affect at least one aspect of a SNET group, including but not limited to a member, access to information, some combination thereof, and so forth. A SNET travel group may interface to a SNET group that includes entities related to one or more activities, including but not limited to travel companies, family members, friends and visitors, restaurant coupons/discount services, etc. SNET travel group members (which may be temporary or permanent) may receive detailed hotel information (including confirmation orders, prices, feedback, entertainment, restaurant recommendations, nearby tourist attractions, etc.), a list of social events/outing participants, a caregiver monitoring service, some combination thereof, and the like, without limitation. In some implementations, in response to one or more triggering events, input from one or more SNET group members, input from one or more SNET group non-members, input from one or more devices, some combination thereof, or the like, one or more elements associated with a SNET travel group may be managed by one or more processing systems, server devices, network nodes, remote devices, social devices, or the like.

FIG. 5 illustrates an embodiment of a social network environment that adapts trigger events, triggers, etc. Some embodiments of the SNET group may respond to externally applied or internally applied triggering events, such as certain events being completed, a change in location, a passage of time, some combination thereof, and so forth. As shown in fig. 5, the illustrated embodiment is a SNET group designed for use during travel, such that SNET travel group 500 responds to certain travel event completion, location change, and upcoming events by adding, removing, or otherwise modifying the SNET group's information, access, and membership. The illustrated embodiment also illustrates the changes experienced by SNET travel groups as a trip progresses. The illustrated embodiment shows a SNET travel group for short-term business trips, including departure and return flights, destination hotel stays, and meetings with destination partners.

As shown in state 540, at the beginning of the journey, SNET travel group 500 includes two docking entities, a social group 502 associated with the passenger's wife, and a social device 504 associated with the person the passenger meets at the destination. In some implementations, SNET travel group 500 members may include SNET accounts that are specific to the SNET travel group 500 members such that any social devices associated with the members are part of the SNET travel group 500. In addition to the docking entities 502 and 504, at state 540 the SNET travel group includes passenger flights 506 and 510 for his outgoing and return flights and information 508 related to his hotel reservations. All of the above members and information may be manually added, changed, and removed from the SNET travel group by a traveler or some other entity, by a travel agency or device, by a docking group 502 member, by a docking device 504 user or social device, some other internal logic of the SNET, and so forth.

After the traveler completes his departure flight and arrives at his destination, his SNET travel group 500 adapts state 550, as shown by line 512. The adaptation may be accomplished, in part or in whole, by manual input from the traveler to SNET travel group 500, automatically by a social device associated with the traveler, a processing system, infrastructure, etc. (the traveler has provided one or more authorizations, associated rules, etc. that set conditions under which SNET groups, social devices, etc. having various attributes are to be docked, granted more or less access, and undocked, based on one or more triggering events as determined by one or more social devices, processing systems, some combination thereof, etc.). When the departure flight is complete, SNET travel group 500 removes departure flight 506 from the information associated with SNET travel group 500 when the event has been completed. Further, in response to the location change, SNET travel group 500 may interface to SNET group 514 associated with the passenger hotel reservation 508 and to one or more potential taxi cab social devices 515 in an accommodation, advance, etc. that the passenger may need.

As shown by line 516, SNET travel group 500 has adapted state 560 after the passenger meeting is completed and the return flight is ready, in response to completion of his meeting and his hotel checkout. When the traveler checks out of the hotel, the hotel SNET group 514 and the taxi cab social device 515 are undocked from the SNET travel group 500 while the hotel reservation information 508 is removed from the SNET travel group 500. Further, when the meeting is complete, the meeting partner's devices 504 are removed from the SNET travel group 500 and they are no longer interested in passenger travel. The only items included in SNET travel group 500 or docked to SNET travel group 500 are passenger upcoming journey 510 and social group 502 associated with the passenger wife.

In some embodiments, adding, changing, and removing certain information, docking, changing access to, and undocking from certain devices and groups as a traveler progresses makes it possible for the traveler to interact with most of the information and entities related to current and upcoming possible travel events, such as reaching a new destination, preparing an event, finding a landmark building, dining, lodging, and the like.

According to various embodiments, the presence and location of SNET infrastructure, SNET groups, SNET subgroups, docking social devices, some combination thereof, and the like may be determined using various techniques, such as those described elsewhere herein. The location information may be utilized in various ways including, but not limited to, the ways described below. For example, the SNET location service may utilize one or more of the following criteria: GPS, LTE eNB, (IP) address, NFC (near field communication), bluetooth, WiFi, infrared, etc., including of course account metadata. The cloud-based memory may be used for various information, including location (e.g., GPS), to extend social networking functionality (e.g., automatic SNET grouping/introduction, peripheral automatic service/selection, etc.). Location-based groups may also be formed for travel, tracking, invitations (and timeouts), and the like. In some embodiments, location information, as well as other factors, may also be used to select an online gaming tournament/team. For example, the IP address selection may be made in a DNS-like manner for the relevant domain name. In operation, a game player SNET/SNET group or the like may be formed based on location factors, SNET/SNET group attributes, network attributes, some combination thereof, or the like.

In some implementations, SNET group members may interface SNET groups (including but not limited to SNET travel group 500) to one or more SNET infrastructures, SNET groups, or the like, to engage in gaming and wagering activities. For example, a traveler entering a casino, mall, etc. may add a gambling credit account to his SNET travel group and utilize the account to interact and play various gambling and gaming activities. In some other implementations, SNET members may establish a game on a network by adding a social gaming device to a SNET group. Further, in some implementations, SNET members may be added to one or more SNET groups that are specific to gaming activities based on certain information associated with the SNET members, such as device connection speed, device capabilities, game scores, and the like.

FIG. 6 is a logic diagram of embodiments of a method of allocating social resources according to various embodiments. In an initial step 600, some portion of the SNET infrastructure (including, but not limited to, one or more SNET members, processing systems, social devices, network nodes, some combination thereof, etc.) establishes a SNET account that identifies an associated SNET group and social resources, which may include one or more capabilities provided by one or more devices, applications, services, SNET groups, some combination thereof, etc. Next, or concurrently, in step 602, one or more social resources, SNET groups, etc., are "docked" (e.g., online, coupled through Near Field Communication (NFC), or operated via a network) to the SNET account. The interfacing may include security and authentication operations 604. In some embodiments, the interfacing may include a merged SNET group building that integrates interfacing SNET groups, social resources, and the like.

The method continues in step 606 with creating one or more SNET groups or (sub) groups including docking SNET groups (e.g., merged SNET groups) and selecting social devices, applications, services, other social resources, some combination thereof, etc., that have related or particular characteristics and interdependencies, etc. In one embodiment, a SNET group and social resource may be interfaced through a drag-and-drop user interface or other means. In step 608, access hierarchies and views are defined, either manually or automatically, for selecting personal information, SNET group information, social resource information, social device information, and other related resources. This step can be done in whole or in part by means of (pop-up) forms or forms that request the hierarchy setting and allow individual customization. Certain portions of the SNET infrastructure may select particular SNET groups, social devices, SNET members (devices or humans or themselves) associated with one or more SNET groups and SNET devices to reveal hierarchical characteristics and allow access rights modification. In some cases, the access rights selection may be based on profile data and other characteristics of the particular device, user, or group seeking access to the social resource. Further, different access rights (including content and capability access views) may be assigned to different social device resources or groups of resources, or to specific requests for social resource access.

In step 610, access tier/view characteristics are communicated to authorized consolidated SNET group members, which may include social devices (including members' social devices), human members, SNET, or one or more SNET groups. Among other things, may include providing different content and capability access views for a given docking SNET group or access request; the selection recipient may be authorized to customize the access view. Next, in step 612, social resources are allocated according to the access hierarchy and view transmitted in step 610. For example, social device resource allocation may require allocation of resources exclusively used by interfacing SNET group members that are to undergo reallocation on a permanent or temporary basis. For example, if access to a previously allocated social device resource is requested by a second SNET group member (or non-member) having a higher priority or higher resource access rights, then a subsequent reallocation may occur. In some implementations, social resources can be dynamically provisioned and allocated if/when the resources become available to some extent. Management of social resource reserves, including related service terminations, may be performed by individual devices, groups of devices, and/or centralized or distributed SNET processing circuitry, including but not limited to one or more processing systems and software.

Fig. 7 is a logic diagram of an embodiment of a method 700 of establishing a hierarchical view of social resource access to a first social device SNET group, according to various embodiments. First, the availability of social resources accessed by a SNET group/device is determined in step 702. Social resources may include, but are not limited to, one or more capabilities provided by one or more SNET groups, SNET infrastructure, some combination thereof, and so forth. Next, access rights and access views, including but not limited to one or more representations of social resources, are established in step 704. The access rights and access view may provide various levels of access with different granularities, as the context may dictate, and as determined by one or more SNET nodes having social resource control, processing systems, devices, some combination thereof, or the like, or by an authorized entity requesting access to a social resource.

The established access permission level is then applied to allow access and allocation of social resources in step 706. If there is a conflict, then the modification or additional access request is identified in step 708, and reallocation and/or arbitration is performed as needed to resolve the conflict or other service request in step 710. In one embodiment, wherein a particular SNET group, social device, user associated with one or more SNET groups or social devices, some combination thereof, or the like requires or requests a relatively large percentage of available resources, access may be denied or restricted, including on a temporary or permanent basis. Alternatively, other enabled and available social resources may be used to resolve the request. Potential overuse or abuse of SNET resources may be detected by the SNET monitoring function, including but not limited to one or more processing systems, devices, network nodes, some combination thereof, or the like, that utilize static or dynamic thresholds.

Referring now to fig. 8, a logic diagram of an embodiment of a method 800 of controlling SNET group operation in accordance with various embodiments is shown. Upon activating or interfacing a social device, a first SNET group, a SNET subgroup, a social device interfaced to the first SNET group, a social device interfaced to a second SNET group, a SNET infrastructure, one or more processing systems, devices associated with the SNET infrastructure, or the like, account information is automatically (or via a setup prompt) provided to the social device, the first SNET group, the SNET subgroup, the social device interfaced to the first SNET group, or the like. Next, in step 802, social resource operational control (which may include, but is not limited to, services, device access, applications, social resources, some combination thereof, etc.) associated with the second SNET group, SNET infrastructure, one or more processing systems, devices associated with the SNET infrastructure or group, etc. is given to the nodes of the social devices, the first SNET group, SNET subgroup, social devices interfacing to the first SNET group, etc. The node then generates the appropriate control signals according to the context, as shown in step 804.

In step 806, the control signals and the context-related application are communicated to a second SNET group, SNET infrastructure, one or more processing systems, devices, etc. associated with the SNET infrastructure (via a standardized communication protocol). In step 808, in response to the control signal, the second SNET group, SNET infrastructure, one or more processing systems, devices, etc. associated with the SNET infrastructure are automatically or authorized by the user to perform one or more functions. In a subsequent step 810, control of the second SNET group, SNET infrastructure, one or more processing systems, devices, etc. associated with the SNET infrastructure is terminated or relinquished to the user, the processing system, the device, some other entity, some other SNET node, some combination thereof, etc.

In some embodiments, some SNET groups may support only one member interaction at a time, with or without simultaneously supporting the underlying owner members. Other SNET groups may support many multiple member (device/human) access capabilities provided by the SNET group and having functionality specifically reserved for the owner. Standardized or manufacturer-specific methods of controlling and authenticating the markers may take into account such variations in SNET cohort capabilities. Content monitoring and snooping (e.g., to protect copyright holders) and similar functions may also be accomplished by being compatible with standardized protocols.

Referring now to fig. 9, a social network circle/group 900 (hereinafter "social network group," "social network circle," "SNET group," etc.) is shown that includes a social device 902. In addition to traditional social networking features and services, SNET group 900 and associated social devices 902 according to various embodiments include a number of novel features and attributes, as described more fully below with reference to the illustrations.

Briefly, members of SNET group 900 may include a docking social device 902 having resources and resource agents that may access other members of SNET group 900 and human SNET group members 904. Further, SNET group 900 nodes may include various types of device services and software (e.g., applications) with members participating. By way of example, SNET group members may include artificial intelligence agents/social bots 906, SNET security device(s) 908, appliances, vehicle and service providers 910, common or authorized members/functions of other SNET groups 912, and the like. Further, specific content and resource access by SNET group 900 may be shared with additional SNET 914 member(s), including remote or web-based applications. The access may impose conditions on acceptable analysis and associated data. Likewise, social devices, SNET groups, individuals, etc. may be granted temporary or ad hoc membership with or without limited access.

In the illustrated embodiment, the formation, maintenance, and operation of SNET cohort 900 is performed by one or more SNET processing systems and software 916. The processing system may include, but is not limited to, one or more instances of stand-alone SNET processing circuitry, one or more instances of distributed SNET processing circuitry located on one or more devices, social devices, server devices, network nodes, and the like. It should be noted that "SNET processing circuitry" may comprise hardware, software, applications, or various combinations thereof, and be configured to support the various functions disclosed herein. Further, SNET processing system 916 may be included in a stand-alone server, a server farm, cloud-based resources, and/or the various devices described below, and includes authentication and security functions 918. Furthermore, proprietary middleware may also be utilized by SNET according to various embodiments, including standardized middleware (or standardized communication protocols) with associated authentication methods. The interactions and interdependencies within SNET group 900 may include one or more of an adaptive resource management, allocation, and arbitration module 920, a social device association/control module 922, and a SNET group member analysis module 924, as described more fully below. Furthermore, the SNET processing circuitry & association functionality may be integrated into one or more social devices.

Internal and external SNET content/media 926 distribution may be accomplished in various ways according to various embodiments. For example, media distribution may include an adaptive or parallel network routing infrastructure, including various communication protocols and wired and/or wireless communication channels. For example, SNET content/media 926 may include various user driven (ad) channels, pictures, videos, links, online text, and the like. Access to the content, as well as communication with the social devices 902 of the SNET group 900 and remote access to the social devices 902 may be over an internet backbone 928, a cellular communication system, WAN, LAN, etc.

SNET members according to various embodiments (such as those disclosed herein) may establish permissions and/or privacy settings that control and limit who or what may access member profile information, connections, and groups, as well as define the degree of access desired. Permissions may make it possible for a user to only maintain certain information private or available based on the permissions. For example, visibility of specified user information may be limited to users/devices in the SNET(s). Alternatively, the specified user information may be disclosed. Also, SNET members may selectively decide to allow other members to access personal information, such as name, gender, contact information/email address, etc.

Fig. 10 is a functional block diagram illustrating a Social Network (SNET) infrastructure 1000 and social device(s) (member) 1001, in accordance with various embodiments. Communications between social network infrastructure 1000 social device(s) 1001 and other SNET members may be conducted over one or more wired and wireless communication networks 1003. SNET infrastructure 1000 and social device(s) 1000 are coupled to communication network 1003 via communication interface(s) 1031 and 1011, respectively, either of communication interfaces 1031 and 1011 may support communication with individual SNET members, groups of SNET members, or categories of SNET members.

The SNET infrastructure 1001 of the illustrated embodiment includes many functions and resources to support the formation and maintenance of a SNET with social device members. In particular, the membership report management and processing 1033 receives information from the SNET/group/membership report function 1013 in the associated social device 1000. For example, the information may include status data 1015 related to the location, address, and activity of the social device 1000 and/or the device user.

Further, social device 1000 may provide device information 1016, such as indicating device functionality and social capabilities, device model(s), device make-up, software version, attached peripherals and downstream (social) devices, device resources and usage, and so forth. Device information 1016 relating to available resources and current resource usage may be utilized by SNET infrastructure 1001 for SNET resource management purposes, including dynamic resource allocation and arbitration.

In various embodiments, the social device 1000 may collect, store, and/or report device status/information 1015/1016 at different times. Reporting may be required after association or interfacing with the SNET, for example, on a periodic basis and/or during operational engagement with other SNET resources and devices, including upstream and downstream devices.

Referring again to SNET infrastructure 1001, additional functions and resources include, but are not limited to: SNET member information collection and storage management 1034; SNET Application Programming Interface (API) 1035 to allow SNET-associated software components to communicate with each other; access control management and security 1037 for maintaining SNET and ancillary data/resource integrity; and a (web) server service 1038. The social network infrastructure 1001 further includes: other group application services 1005 corresponding to the above; and additional services, such as described herein. In one exemplary embodiment, SNET infrastructure 1001 may determine (e.g., via device information 1016) the nature and kind of social devices 1000 that wish to participate in SNET. If necessary, the functions in SNET infrastructure 1001 may then direct or trigger the installation of the appropriate application software and the installation of the underlying drivers in social device 1000. The operations may be performed with minimal involvement of the inherent functionality of the social device 1000.

In the illustrated embodiment, the social device 1000 includes a number of additional social device resources 1018 (e.g., including the social resources and device status/information 1015/1016 described in connection with fig. 11 and 13) as well as functionality and resources to support participation in a social network. More specifically, the SNET, and/or member control function 1017 may include a slave function 1019, a master function 1020, and various combinations thereof. For example, the slave function 1019 includes device (re) composition, directed resource allocation, managed resource arbitration, bridging operations, and the like. The master function 1020 makes it possible for the social device 1000 to establish, manage, and terminate various interactions between nodes or groups of nodes in a social network, including interactions involving the social device 1000 itself.

The social device 1000 also includes a social API 1021 and browser-based interaction capability 1025, for example, to support relevant social applications and services 1023 (which may include slave and master functions 1019 and 1020). The access control (including access views provided to other SNET group members) and security 1027 layers allow the social device 1000 to connect or establish secure SNET groups/circles and control access to internal and external SNET resources, as described more fully below.

It should be noted that many of the functional blocks of the embodiment shown in fig. 10 may be integrated, in whole or in part, in one or more (application-specific) integrated circuit devices. For example, an integrated circuit device may include a membership reporting module to provide membership reporting functions (including device status and device characteristic communications), device control capabilities, master/slave functions, security and access control modules, and the like. The integrated circuit device may also include on-board processing capabilities and/or an interface to a processor device. Alternatively, several of the functions described above may be integrated in whole or in part in the operating system and/or software that loads the operating system kernel.

Referring now to FIG. 11, a schematic block diagram is shown for a social device 1101, the social device 1101 operable to support various resource access interactions with other social devices and social systems in accordance with various embodiments. The social device 1101 configures various functions making it possible to operate in a social device "hierarchy" (including social (S), social "parent" (SP), and social "child" (SC) devices). For example, a social parent device may enable a docking social child device to access parent device resources and/or connect to and interact (directly or indirectly) with a social network. Social child devices may configure internal social capabilities or gain access to the capabilities from or through an associated parent device. Further, human SNET members may have associated social kid devices, or may be served by social parent devices via a user I/O interface (1123).

The social device 1101 according to various embodiments and applications may also simultaneously or selectively function as a social device, SP device, SC device, or even an "grandmother" device that supports (e.g., in a multi-hop environment) a mother device in a SNET group. Dynamic and static hierarchical associations between SP and SC devices may be established in a selective, automated, or automated manner. Further, social device 1101 may take many forms, including but not limited to a smartphone, personal computer, server, tablet device, access point, gateway, network switch/hub, bridge device, set-top box, or other device that enables social capabilities.

In the illustrated embodiment, social device 1101 is communicatively coupled to SNET infrastructure 1109 and/or social parent system 1111 via upstream social communication interface circuitry 1107. Likewise, the downstream social peer and/or sub-communication interface circuitry 1113 makes coupling with the social sub-device 1115, the social peer device 1117, and/or the social parent system (device) 1119 possible. Social resources of upstream and downstream devices may access each other via social device 1101.

Social device 1101 of this embodiment includes social resources 1103, social resources 1103 being managed by social resource managing module 1105 along with external SNET resources, and having access to at least one other SNET group member. Specific social resources 1103 may include user I/O interfaces 1123, general and specific hardware processing circuitry 1124, peripheral circuitry and components 1125 (which may or may not have social capabilities), communication bandwidth and credit determination functionality 1126, switching/bridging functionality 1127, applications and services 1128, remote social resources 1129 of the SNET group, external social resources 1131 controlled by social device 1101, and the like. For example, external social resources 1131 may include external media/digital media libraries or content from one or more of cable, satellite, and/or terrestrial television systems.

The social resource management module 1105 includes, among other functions, access, allocation, arbitration and scheduling functions 1121 as well as functions 1122 for establishing, restoring and relinquishing control processing operations, including operations involving access to social resources 1103. It should be noted that the pairing social resource management functionality may be present in SNET infrastructure 1109 and/or other SNET nodes.

In one exemplary embodiment where the social device 1101 includes a switching bridge, bandwidth capacity may be dynamically allocated through access, allocation, arbitration, and scheduling functions 1121. Access to the bandwidth capacity and other resources of the social device 1101 may be available only after a request according to the access view or according to the allocation and arbitration function, and selectively terminated when excess bandwidth/resources are consumed or requested.

Fig. 12 is an exemplary block diagram illustrating social resource access to a SNET group 1206, according to various embodiments. In some embodiments, a social network group ("SNET group") member controls different levels of access to two personal information (which may be included in a user profile) and associated device profiles and capabilities. The access permissions allow members to establish selective, restrictive, and/or hierarchical access permissions and views-to other members of the social group and to non-members-to all or some of the members' social devices and resources. Further, members may establish selective or hierarchical access to personal information and associated social device profiles, as well as other resources.

In the illustrated embodiment, SNET group 1204/1206 members or devices (or, optionally, unassociated entities) access social device/group resources 1210 associated with SNET group 1206 via resource management node 1200. The resource management node 1200 includes access rights 1201, an access view 1202, a dynamic (re) allocation function 1203, an arbitration function 1204, and a security function 1205.

In operation, access rights 1201 and access view 1202 control different levels of access and visibility of access to member personal information, device information, data, processing and storage capabilities, and other social resources. For example, access permissions 1201 and access view 1202 may be predefined based on SNET groups, based on common member devices, or based on member own device-device interactions. The predefinitions may be dynamically customized as needed or as relationship changes. The access rights 1201 may also be extended to support temporary interaction with guest members or visitor devices. For example, an access member of a smartphone may be allowed to receive/provide media to social devices residing in a "family group.

In some embodiments, SNET group 1206 members may adjust and modify access rights 1201 on an information-by-information basis, a device-by-device basis, a member-by-member basis, and the like. By accessing view 1202, members can also present themselves in various ways depending on context, location, or usage-based considerations. For example, the member icons/avatars may present different characteristics or capabilities that are contextually relevant, including work, family, or social settings. The allocation of social resources and, if necessary, dynamic reallocation is performed by a dynamic (re) allocation function 1203 and an arbitration function 1204. Social resource access may be handled in advance on the security access/authentication performed by the security function 1205.

In addition to social device/group resources 1210, for example, SNET group 1206 may include SNET server 1212 and one or more members 1214 as well as affiliated social devices, services, applications, files, web pages, connections, and other social resources. It should be appreciated that members 1214 (which may include, but are not limited to, human members, device members, etc.) may establish selective or hierarchical access to personal information and associated social device profiles, as well as other resources as described above. In some embodiments, resource management node 1200 may be incorporated into SNET server 1212 or other SNET social devices, or managed by the SNET hosting infrastructure in a standalone manner, a distributed manner, or the like. Further, SNET server 1212 may include a firewall operable to provide secure access and perform basic routing functions.

Access to the social device/circle resource 1210 by the SNET group 1213 node may occur in various ways, including via a User Interface (UI) 1218 utilized by one or more humans 1216. The UI 1218 may include a Graphical User Interface (GUI) or browser to graphically indicate available resources, voice controls, gesture commands, and the like. Access to SNET group 1206 may also be managed by proxy server 1220. Proxy server 1220 acts as a broker for proxy client 1222 access requests-including social devices connected to proxy server 1220 via the internet or other IP-based network-seeking communication with SNET group 1206. Social devices 1224 affiliated with SNET 1213 may have the ability to interact directly with SNET group 1206. It should be noted that the human member 1216, proxy server 1214, and social devices 1224 may operate independently of SNET groups/subgroups. Further, proxy 1214 may be a distributed or cloud-based entity, or a member (or included in a member) of SNET group/subgroup 1213 or SNET group 1206.

Fig. 13 is a schematic block diagram of a social device/server 1300 utilizing a communication and control protocol 1302 that enables various SNET resource and control operations in accordance with various embodiments. In the illustrated embodiment, the communication and control protocol 1302 includes a protocol construct 1304, SNET resource (automatic) control feature 1306, device type/function specific control 1308, security and authentication features 1310, SNET docking/membership control 1312, and SNET transport/network layer 1314. Various encapsulation and packaging techniques may be used to transmit and receive control signals and data.

In one embodiment, the social device/server 1300 includes a shim layer or client driver 1316 enabling communication with a central SNET management node, SNET infrastructure, one or more processing systems, SNET members, and other compatible devices (including social devices that may not fully support the SNET group communication protocol), some combination thereof, and so forth. Shim (shim) layer or client driver 1316 may be installed through SNET node or local memory, or downloaded from a manufacturer's website or cloud-based resource. The installation may be done automatically or directed by other SNET nodes after the social device/server 1300 is powered on or activated.

SNET resource management and access using communication and control protocol 1302 may be performed by a SNET group or a central management node of a SNET hosting infrastructure. The central management node may include integrated artificial intelligence and/or present itself through a "role" or "avatar". Furthermore, the control mechanism of distribution and delegation (including ad hoc or remote operation across one or more SNETs) allows one member to interact with themselves or another member social device via SNETs or SNET-defined pathways.

In some embodiments, a standardized version of the communication and control protocol 1302, referred to herein as the "SNET 1.0" standard for brevity, is used to facilitate the SNET interaction (and may not require a shim layer in a compatible social device that defines device type characteristics). Various control operations in accordance with the SNET1.0 standard may include automatic and ad hoc SNET group association and support functions such as automatic SNET resource dedication, automatic device registration and composition, upgrade and update maintenance, device-device communication session management, tunneling/encapsulation functions, proxy services, social resource allocation, and the like. For example, by docking of an affiliated social device in the SNET group, the members may desire to access and control their own remote docking device as well as remote docking devices of other members, either directly or via yet another user device. In some embodiments, the interaction may be facilitated by a SNET1.0 compatible method.

For example, a SNET1.0 compliant device may be designated as "SNET 1.0 certified" and provide system on a chip ("SoC")/hardware and software support specific to a particular group of devices. By way of example, the SNET1.0 authentication NAS may have storage-related, definition control capabilities, including default access hierarchy definitions, security and DRM features, etc., as described herein. For example, the control capability is different from SNET1.0 certified STBs (possibly with multiple tuners/delivery paths for delivering streaming video with certain tuners/delivery paths reserved for the device itself according to a setup program). The social device may be configured, manually or through factory level settings and security, to delegate membership control to a SNET (1.0) group/server for further applications, such as described below.

FIG. 14 illustrates various embodiments of social device members and access in a social network group/subgroup, according to various embodiments of the present invention. In some embodiments, the members of SNET group 1410 are extensible to include public and private social devices and equipment. For example, in a SNET group 1410 that includes human members 1406/1408, each human member may have a respective personal SNET subgroup 1400 (a)/1400 (b) that is capable of independently or collectively participating in the SNET group 1410 or interfacing with a social device 1406/1408. The SNET subgroup may be accessed locally or remotely by human members 1406/1408 and/or other SNET group/subgroup members through various means, such as clicking on an icon or label associated with a human member/person subgroup.

Although SNET subgroups 1400 (a) and 1400 (b) are shown as separate subgroups, the subgroups may instead comprise a single SNET group or subgroup or any number of additional SNET groups, SNET subgroups, etc., each of which may include various combinations of social devices 1402/1404. In addition, SNET processing circuitry and software 1412 of the illustrated embodiment manages the formation and operation of SNET group 1410. SNET processing circuitry and software 1412 may be incorporated in a stand-alone server, social device, and/or cloud-based resource. The SNET group 1410 may be permanent or of limited duration and include ad hoc and/or static associations. Further, the SNET groups/subgroups may be permanent or ad hoc/temporary.

The social device 1402/1404 may be broadly divided into: (i) a social device 1402 comprising a user or SNET group interface sufficient to provide (support) meaningful (user) input (e.g., SNET settings and management) to SNET interactions; (ii) social device 1404 supporting minimal or no user input related to SNET interaction; some combination thereof, and the like. More specifically and without limitation, the first category may include computers, tablet devices, IPTV set-top boxes, smart phones, servers, laptops, cloud books, network-attached storage devices, gaming machines, media players/sources, communication nodes (access points, routers, switches, gateways, etc.), user interface devices, Power Line Communication (PLC) devices, and the like. The social device may receive user input for SNET settings and management. The second category may include, but is not limited to, printers, projectors, cameras and camcorders, scanners, speakers, headphones, smoke detectors, alarm systems, cameras, mice, and the like. In general, a dockable social device includes any electronic device operable to couple or dock in a SNET group/subgroup via a wired or wireless pathway involving SNET members. Wherein the docked "social" device may participate in the SNET circle/subcycle.

It should be appreciated that by interfacing with social devices, SNET group 1410 members may obtain remote control and interaction via all or part of an authorized member SNET account. For example, family members authorized to participate in a "family" SNET group may remotely access the docking social device via one or more associated SNET accounts. Various embodiments of interfacing and accessing social devices are described more fully below (e.g., in conjunction with fig. 15 and 16).

Fig. 15 is a schematic block diagram illustrating remote access of social resources of a social network group/sub-group, in accordance with various embodiments. In the illustrated embodiment, the social device 1500 may indicate a desire to associate, interface, access, or otherwise communicate with a (secure) SNET group/subgroup 1502, social device resources and other group resources 1518. The social device 1500 may be autonomous and independent, or alternatively, participate in a second SNET group 1504 or other network serviced by SNET gateway 1506.

In one embodiment, SNET gateway 1506 or SNET group gateway 1508 acts as a proxy for social device 1500. The proxy functionality within the SNET gateway 1506 may be provided by a software application or computer system (server) that acts as an intermediary for requests from clients (including connected social devices) seeking resources from other servers or gateways, such as the SNET gateway 1508. The resources may include files, services, web pages, connections, analytics information, and other available social device resources and other group resources 1518.

The SNET gateway 1506 may evaluate the social device request according to various filtering rules. For example, SNET gateway 1506 may filter traffic by IP address or protocol. Once the social device 1500 requests to be active (if necessary), SNET gateway 1506 connects to SNET group gateway 1508 via a WLAN/LAN or other communication path and requests access to resources of SNET group/subgroup 1502 represented by social device 1500.

The members of SNET group/subgroup 1502 are established by a docking module 1510 of SNET processing circuitry and software 1512, which may support one or more device discovery and composition protocols, including standardized protocols. When restricting group members, a local or cloud-based registrar 1514 may be used to provide authentication. The registrar 1514 of the illustrated embodiment may utilize an administrator or directory service 1516, such as a Lightweight Directory Access Protocol (LDAP) based directory server (storing attribute data). LDAP is a well-known application protocol for querying and modifying items in a directory service. When interfacing with an IP-based SNET group, a social device may broadcast profile data (using a text data format) (extensible markup language (XML)) to a local domain.

FIG. 16 is a schematic block diagram of an embodiment of social device(s) 1600 that include full resource access and allocation management functionality in accordance with various embodiments of the present invention. Social device 1600 may operate as a SNET member, guest member, and/or authorized visitor. Access and allocation of social resources 1602 of social device 1600 is controlled by (predefined or user defined) access and allocation management functions 1604 (the operation of which may apply to within and between SNET member nodes) and interactions between social resources 1602 and unassociated entities. Further, access and distribution management functions 1604 may be distributed among one or more social device/SNET hosting infrastructures.

The access and allocation management functions 1604 include access rights 1606, access control functions 1608, arbitration and dynamic (re) allocation 1610, and access view control 1612. Exemplary operation of the described functionality is described in connection with various other figures herein. For example, access request services to social resources 1602 may be performed via a browser and/or a downloaded or pre-installed application 1614. In some embodiments, social resource 1602 access is made after the authentication or security operation 1616. Further, various functional blocks of social device 1600 may be incorporated in one or more integrated circuit devices, which may be dedicated to supporting primary user and/or shared access operations.

Fig. 17 is a schematic block diagram of an embodiment including a social device 1700 operable to support integrated functionality of social network group/subgroup membership and communication in accordance with various embodiments of the present invention. In the illustrated embodiment, the communication interface and transceiver circuitry 1702 is operable to perform wired or wireless communication between the social device 1700 and the SNET/SNET group/SNET subgroup 1726 via one or more communication channels. Depending on the capabilities and makeup of social device 1700, communications with the SNET may be unidirectional or bidirectional/interactive and utilize proprietary or standardized communication protocols. For example, the communications may include device configuration information, user and SNET group configuration information, control signals, media content, interactions with hosted service data, user data, relay information, and so forth.

Social device 1700 also includes processing circuitry 1704 operable to process and manage communications, services, and associations between the device and other entities, including SNET/SNET group/SNET subgroup 1724 members, third parties, software agents, and the like. More specifically, for example, processing circuit 1704 may include software management application 1712, software management application 1712 including: docking logic 1714 (including supporting device discovery and composition protocols, such as described below), communication protocol control 1716, resource management 1718, and security/authentication 1720 functionality.

Social device 1700 may also utilize configuration information and other resources, which may take many forms and be maintained in static or dynamic memory 1724. The configuration information makes it possible for the social device and/or the user 1701 to present self images and their capabilities to other members of the NSET. In particular, device/group configuration information and other resources 1706 and user configuration information 1708 may be utilized in various ways to facilitate various social interactions according to various embodiments. A device or user profile may be static or dynamic, depending on the capabilities and requirements of a particular device (and other members of the SNET).

In some implementations, the social device 1700 may interact with the user(s) 1701 via the user interface circuitry 1710. For example, user input to social device 1700 may include data input through a keyboard, touch screen, remote control device, game controller, device control buttons, voice or gesture commands, storage device, and the like. Authorized access or control of social device 1700 may be facilitated by unique biometric identifiers, passwords, token-based identification, trust authority or documents (such as driver's licenses or passports), and similar authentication means.

Social device 1700 may perform core or underlying functions 1720. Or alternatively, the social device may be used primarily as a social network interface or communication device, or may be programmed to perform specific functions within a SNET group/subgroup.

As used herein, the terms "substantially" and "approximately" provide industry-accepted tolerances for their corresponding terms and/or relativity between items. The industry-accepted tolerance ranges from one percent to fifty percent and corresponds to, but is not limited to, component values, integrated circuit process variations, temperature variations, rise and fall times, and/or thermal noise. Relativity between items ranges from a few percent difference to a large difference. Also as used herein, the term(s) "operatively coupled," "coupled," and/or "coupled" includes both direct coupling between items and/or indirect coupling between items via intermediate items (e.g., items include, but are not limited to, components, elements, circuits, and/or modules), where, for indirect coupling, the intermediate items do not modify the information of a signal but may adjust its current level, voltage level, and/or power level. As also used herein, inferred coupling (i.e., where one element is coupled to another element by inference) includes direct and indirect coupling between two items in the same manner as "coupled to". Also as used herein, the terms "operative to" or "operatively coupled to" indicate that an item includes one or more of a power connection, input(s), output(s), etc., that when enabled performs one or more of its corresponding functions, and also includes inferred coupling to one or more other items. Also as used herein, the term "associated with …" includes direct and/or indirect coupling of the individual items and/or one item embedded within another item. As used herein, the term "compares favorably", indicates that a comparison of two or more items, signals, etc., provides a desired relationship. For example, a suitable comparison may be achieved when the desired relationship is that signal 1 has a greater magnitude than signal 2, when signal 1 has a greater magnitude than signal 2, or when signal 2 has a lesser magnitude than signal 1.

Also as used herein, the terms "processing module," "processing circuit," and/or "processing unit" may be a single processing device or a plurality of processing devices. The processing device may be a microprocessor, microcontroller, digital signal processor, microcomputer, central processing unit, field programmable gate array, programmable logic device, state machine, logic circuitry, analog circuitry, digital circuitry, and/or any device that manipulates signals (analog and/or digital) based on circuit hardcoding and/or operational instructions. A processing module, processing circuit, and/or processing unit may have associated memory and/or integrated memory elements, which may be a single memory device, multiple memory devices, and/or embedded circuitry of the processing module, processing circuit, and/or processing unit. The memory device may be a Read Only Memory (ROM), Random Access Memory (RAM), volatile memory, non-volatile memory, static memory, dynamic memory, flash memory, cache memory, and/or any device that stores digital information. Note that if the processing module, processing circuit, and/or processing unit includes more than one processing device, the processing devices may be centrally located (e.g., directly coupled together via a wired and/or wireless bus structure) or distributively located (e.g., cloud computing indirectly coupled via a local area network and/or a wide area network). It is also noted that if the processing module, processing circuit, and/or processing unit implements one or more of its functions via a state machine, analog circuitry, digital circuitry, and/or logic circuitry, the memory and/or memory elements storing the corresponding operational instructions may be embedded within, or external to, the circuitry comprising the state machine, analog circuitry, digital circuitry, and/or logic circuitry. It is also noted that the memory elements may store, and the processing modules, processing circuits, and/or processing units execute, hard-coded and/or operational instructions corresponding to at least some of the steps and/or functions noted in one or more of the figures. The memory device or memory element may be included in an article of manufacture.

The invention has been described above with the aid of method steps illustrating its specific functional and relational properties. Boundaries and the order of these functional blocks and method steps have been arbitrarily defined herein for convenience of description. Alternative boundaries and sequences may be defined so long as the specified functions and relationships are performed accordingly. Any alternative boundaries or sequence are within the scope and spirit of the invention. Further, boundaries of these functional blocks have been arbitrarily defined for the convenience of the description. Alternate boundaries may be defined so long as certain important functions are performed accordingly. Likewise, flow diagram blocks may have been arbitrarily defined herein to illustrate certain important functions. To the extent used, the flow diagram block boundaries and sequence may be otherwise defined and still perform some significant functions. Alternative definitions of both functional blocks and flowchart blocks and sequences are within the scope and spirit of the present invention. Those of ordinary skill in the art will also recognize that the functional blocks, as well as other illustrative blocks, modules, and components herein, may be implemented as discrete components, application specific integrated circuits, processors executing corresponding software, etc., or any combination thereof.

The invention may have been described, at least in part, in terms of one or more embodiments. The embodiments of the invention are used herein to illustrate the invention, inventive aspects, inventive features, inventive concepts and/or inventive examples. Physical embodiments of devices, articles of manufacture, machines and/or methods that embody the present invention may include one or more of the aspects, features, concepts, examples, etc., described with reference to the embodiments discussed herein. Furthermore, from figure to figure, embodiments may include the same or similarly named functions, steps, modules, etc. that may use the same or different reference numbers, and thus the functions, steps, modules, etc. may be the same or similar functions, steps, modules, etc. or different functions, steps, modules, etc.

Signals to, from, and/or between elements in any of the figures presented herein may be analog or digital, time continuous or time discrete, and single ended or differential, unless specifically noted otherwise. For example, if the signal path is shown as a single-ended path, it also represents a differential signal path. Likewise, if the signal path is shown as a differential path, it also represents a single-ended signal path. Although one or more particular architectures are described herein, it will be appreciated by those of ordinary skill in the art that other architectures may be implemented as well, using one or more data buses, direct connections between elements, and/or indirect couplings between other elements that are not explicitly shown.

The term "module" is used in the description of the various embodiments of the invention. A module includes functional blocks that are implemented via hardware to perform one or more module functions, such as processing one or more input signals to generate one or more output signals. The hardware implementing the modules may itself operate in conjunction with software and/or firmware. As used herein, a module may include one or more sub-modules, which are themselves modules.

Although specific combinations of features and characteristics of the present invention have been described herein, other combinations of features and functions are also possible. The invention is not limited to the specific examples disclosed herein and these other combinations are expressly included.

Claims (10)

1. A social networking system that supports interaction with at least a first human member and a second human member, the social networking system comprising:

a processing system operable to support creation of a first social network group having first group capabilities and a second social network group having members including the first human member and the second human member;

the processing system is operable to also support a first docking method comprising: associating the first social network group with the second social network to provide the first group capability to members of the second social network group; and

the processing system is operable to transmit data to members of the second social network group to support presentation of the first group capability.

2. The social networking system of claim 1, the processing system operable to transmit data to members of the second social networking group to support presentation of a representation of the first group capability that enables the members to access the first group capability.

3. The social networking system of claim 2, wherein:

the first social network group comprises a first plurality of social network groups;

the first group capability comprises a capability of at least one of the first plurality of social network groups; and

the representation includes a view of the first group capability independent of a view of the first plurality of social network groups.

4. The social networking system of claim 2, the processing system operable to communicate data to members of the second social network group to enable a first representation of the first group capability to be presented to at least a first member of the second social network group and a second representation of the first group capability to be presented to at least a second member of the second social network group, the first representation being different from the second representation.

5. An apparatus that supports users interacting with a social network, the apparatus comprising:

an interface configured to communicatively couple with a social network; and

processing circuitry interoperable with the interface to:

interact with a social network to join the first social network group to the second social network group.

6. The apparatus of claim 5, the processing circuit interoperable with the interface to:

docking the device to a first social network group, an

An ability to access the second social network group.

7. The apparatus of claim 6, the processing circuit interoperable with the interface to:

displaying, on a user interface, a representation of a second social network group associated with the first social network group, the representation including a representation of an ability of the second social network group independent of at least one of the plurality of social network groups; and

determining a user input based on user interaction with the representation via a user interface based on an ability of a user input to access the second social network group.

8. A method performed by a social networking system, the method comprising:

maintaining a first social network group through which a first group service is provided;

maintaining a second social network group to support the first and second human members via the first and second devices, respectively; and

responding to a group-group docking request received by having both a first device and a second device access the first group service, the group-group docking request originating from an interaction with the first device.

9. The method of claim 8, the group-group docking request being a request to associate the first social network group with the second social network group to provide at least some of the first group services to at least one of the first device and the second device.

10. The method of claim 8, comprising:

responding to a group-group docking request received by having both the first device and the second device access the first group service, the first group service being provided by at least one of a plurality of social network groups, via a representation, and the representation including a representation of the first group service unrelated to the at least one of the plurality of social network groups.