TWI503784B - Social networking grouping hierarchy - Google Patents

Description

Social networking system and method of execution thereof

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

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

In many mainstream social networks, especially in a profile-centric social network, members can view profiles as possible web activity centers or social spaces across the network of contacts and share activities, interests, opinions, status updates , audio/video content, etc. Social networking services may also allow members to track certain activities of other members of the social network, collaborate, find and communicate with existing friends, former acquaintances, and colleagues, and establish new communications with other members.

Individual members typically connect to social networking services via existing web-based platforms via computing devices, tablets or smart phones. Members often share common hobbies, social status, or geographic or cultural exchanges with their respective contacts. Mobile social networking services based on smart phones and game consoles are rapidly evolving regional examples.

In so-called "cloud" computing, computing tasks are performed on remote computers/servers that are typically accessed via an internet connection. One advantage of cloud computing is that it reduces users. The relative processing and storage capabilities required by the device (eg, the cloud computer can load web pages accessed by the tablet device and only pass back the required information to the tablet). As a result, the number of content and applications that have migrated from local or current storage to cloud-based data storage and management has increased in recent years. The software functions/services and content are typically provided on demand via a (virtualized) network infrastructure.

Typically, visitors to locations, networks, etc. are permitted to access location, business network, and possibly access social networking environments, cloud applications, or cloud media content. The permission is often almost unlimited in duration and range. In addition, social groups have various mechanisms for establishing contact with another member, member device, or member device service, including, for example, phone numbers, IP or other routing addresses, VoIP/video call handles, twitter handles, other SNETs. Control points, blogs, web addresses, email addresses, etc. When the above changes, it may be difficult to communicate information to all other members and member devices.

According to an aspect of the present invention, a social networking system is provided that supports support for interacting with at least a first human member and a second human member, the social networking system comprising: a processing system operable to support the first social Creation of a network group and a second social network group, the first social network group having a first group capability, the second social network group having the first human member and a member of a second human member; the processing system operable to also support a first docking method, the first docking method comprising: associating the first social network group with the second social network Linking to provide the first group of capabilities 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 for supporting the presentation of the first group of capabilities.

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

Wherein the processing system is operable to transmit data to the second social network A member of the road group to support presentation of a representation of the first group of capabilities, the representation enabling the member to access the first group of capabilities.

Wherein: the first social network group includes a first plurality of social network groups; the first group capability includes an ability of at least one of the first plurality of social network groups; and The representation map includes a view of the first group capabilities that are independent of views of the first plurality of social network groups.

The processing system is operable to transmit data to a member of the second social network group to support the first representation of the first group capability to be presented to the second social network group at least The first member of the group and the second representation of the first group capability are presented to at least the 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, and the first docking method is an ad hoc docking method, and the ad hoc docking method includes: associating a guest member with the guest social network group. And associating the guest social network group with the first social network group.

The social network system includes: the processing system is operable to establish at least one docking specification, the at least one docking specification including the first social network group and the second social network a condition associated with the group; the processing system operable to manage access by the member of the second social network group to the first group of capabilities based on the at least one docking specification; and the processing The system is operable to change an 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 the third party based on the at least one docking specification A member of the social network group accesses information included in the second social network group and at least one of the first group capabilities.

According to another aspect of the present invention, an apparatus is provided for supporting and social networking a user interacting with the device, the device comprising: an interface configured to be communicatively coupled to the social network; and processing circuitry interoperable with the interface to: interact with the social network to connect the first social network The way group is connected to the second social network group.

The processing circuit and the interface are interoperable to: connect the device to a first social network group, and access the second social network group.

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

The processing circuit and the interface are interoperable to: display, 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 capabilities of the second social network group unrelated to at least one of the plurality of social network groups; and an ability to access the second social network group based on user input, based on The user interface interacts with the user of the representation to determine user input.

The processing circuit and the interface are interoperable to: associate a third-party social network group with the first social network group, and make the third-party social network group via a docking method A member of the group can access at least some information associated with the first social network group; and manage access by the third party social network group member to the first social network group in response to the input .

The processing circuit and the interface are interoperable to: interact with the social network to release the first social network group and the second social network group in response to receiving an input Association.

The processing circuit and the interface are interoperable to: interact with the social network via a docking method to base a geographic location based on the device and a geographic location associated with the second social network group Approaching, associating the first social network group with the second social network group; and responsive to determining that the device is associated with a geographic location associated with the second social network group Geographic proximity exceeds threshold a value that interacts with the social network to disassociate the first social network group from the second social network group.

According to another aspect of the present invention, a method performed by a social networking system is provided, the method comprising: maintaining a first social network group, providing a first group through the first social network group Serving; maintaining a second social network group to support the first human member and the second human member via the first device and the second device, respectively; and accessing the first device and the second device by A group of services responds to the received group-group docking request originating from interaction with the first device.

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 service Giving at least one of the first device and the second device.

The method includes: responding, by means of a representation, to a group-group docking request received by causing both the first device and the second device to access the first group service, The first group service is provided by at least one of a plurality of social network groups, and the representation includes a representation of the first group service unrelated to at least one of the plurality of social network groups.

The method includes the step of restricting access by the second device to the first group service based on a docking specification derived from interaction with the first device.

The first group service includes at least one of a game service and an access to a gambling device.

100‧‧‧SNET grouping hierarchy

101‧‧‧Serving SNET infrastructure

103‧‧‧(first) client SNET infrastructure

105‧‧‧ (second) client SNET infrastructure

107‧‧‧(N) Client SNET Infrastructure

111‧‧‧Social service support user device

113‧‧‧ (social service) application

115‧‧‧SNET (SSUD) group

117‧‧‧SNET (SA/SSUD) group

119‧‧‧SNET (SA) group

125‧‧‧Docking method (Select & Docking)

131, 141, 151‧‧‧ client social devices

135, 145, 155‧‧‧ Client SNET Group

201‧‧‧ first representation

203‧‧‧Nth representation

300‧‧‧SNET grouping hierarchy

301‧‧ (Global Social Services) Infrastructure

303‧‧ (Local/Regional Social Services) Infrastructure

305‧‧‧ representation

313‧‧ Social Service Application

311, 321‧‧ social service support user devices

323‧‧ social service (server/cloud) application

315, 325‧‧‧SNET (SSUD) group

317, 327‧‧‧SNET (L/R Hybrid SA/SSUD) Group

319, 329‧‧‧SNET (SA) group

331‧‧‧Social Service Support (L/R&G) User Device

337‧‧‧(Global) SNET Group

402, 424‧‧‧SNET infrastructure

404, 412, 414, 420, 426, 432, 434‧‧‧ SNET groups

406, 408, 416, 428, 430, 436, 438, 442‧‧‧ docking specifications

407, 409, 418, 429, 431, 437, 439, 444, 446‧‧‧ docking links

500‧‧‧SNET Travel Group

502‧‧‧ (wife's) social group

504‧‧‧ (meeting partner's) social installation

506‧‧‧ (departure) voyage

508‧‧ Hotel Reservation (Information)

510‧‧ (return) voyage

512‧‧‧ line

514‧‧‧Hotel (SNET) group

515‧‧‧(taxi) social installation

516‧‧‧ line

540, 550, 560‧ ‧ state

700‧‧‧Method of establishing a hierarchical view of social resource access to a first social device SNET group

800‧‧‧Methods for controlling SNET group operations

S600~S612, S702~S710, S802~S810‧‧‧ steps

900‧‧‧Social Network (SNET) Group

902‧‧‧Social devices (&accessible resources)

904‧‧‧Human SNET group members

906‧‧‧(Multiple) Artificial Intelligence Agent/Social Robot

908‧‧‧(multiple) SNET security devices

910‧‧‧Electrical, vehicle and service providers

912‧‧‧External social device resources

914‧‧‧(multiple) additional SNET

916‧‧‧SNET processing system and software (SNET infrastructure)

918‧‧‧Identification and security features

920‧‧‧Resource Management, Allocation and Arbitration Module

922‧‧‧Social device association/control module

924‧‧‧SNET Group Member Analysis Module

926‧‧‧SNET Content/Media

928‧‧‧Internet backbone

1000‧‧‧Social Network (SNET) Infrastructure

1001‧‧‧(multiple) social devices

1003‧‧‧(one or more wired and wireless) communication networks

1005‧‧‧Other group application services

1011, 1031‧‧(multiple) communication interface

1013‧‧‧SNET/group/member reporting function

1015‧‧‧ Status (including logic, address, activities, resources)

1016‧‧‧Device information (including function, capability, model, composition)

1017‧‧‧SNET, SNET group, member control functions (including resource management)

1018‧‧‧Social device resources

1019‧‧‧From function

1020‧‧‧ main function

1021‧‧‧Social API

1023‧‧ social applications and services

1025‧‧‧Browser-based interactive capabilities

1027‧‧‧Access, control and security

1033‧‧‧Member report management and processing

1034‧‧‧Member information collection and storage management

1035‧‧‧SNET Application Programming Interface (API)

1037‧‧‧Access control management and security

1038‧‧‧(web) server service

1101‧‧ social devices (including social (S) devices, social "mother" (SP) devices, and social "child" (SC) devices)

1103‧‧‧Social resources

1105‧‧‧Social Resource Management Module

1107‧‧‧Upstream social communication interface circuit

1109‧‧‧SNET infrastructure

1111‧‧‧Social Parent System

1113‧‧‧ Downstream social peering and/or sub-communication interface circuits

1115‧‧‧social sub-device

1117‧‧‧Social peering device

1119‧‧‧Social Parent System (Device)

1121‧‧‧Access, allocation, arbitration and scheduling functions

1122‧‧‧ Establish, restore and abandon control processing functions

1123‧‧‧User I/O interface

1124‧‧‧General purpose and dedicated hardware processing circuits

1125‧‧‧ Peripheral circuits and components

1126‧‧‧Communication bandwidth and credit judgment function

1127‧‧‧Switch/Bridge Function

1128‧‧‧Application software and services

1129‧‧‧Remote social resources (including media and storage)

1131‧‧‧External social resources

1200‧‧‧ resource management node

1201‧‧‧Access rights

1202‧‧‧Access view

1203‧‧‧Dynamic (re)allocation function

1204‧‧‧ Arbitration function

1205‧‧‧Security features

1206‧‧‧SNET Group

1210‧‧‧Social device/group resources

1212‧‧‧SNET server

1213‧‧‧SNET Group/Subgroup

Member of 1214, 1216‧‧

1218‧‧ User Interface (UI)

1220‧‧‧Proxy server

1222‧‧‧Proxy client

1224‧‧‧ social devices

1300‧‧‧Social device/server

1302‧‧ (standardized) communication and control protocol

1304‧‧‧ Agreement

1306‧‧‧SNET resource (automatic) control features

1308‧‧‧Device type/function specific control

1310‧‧‧Security and authentication

1312‧‧‧SNET Docking/Member Control

1314‧‧‧SNET transport/network layer

1316‧‧‧(SNET1.0) client driver (middle layer)

1400a, 1400b‧‧‧SNET subgroup

1402, 1404‧‧‧ social devices

1406, 1408‧‧ ‧ human members

1410‧‧‧Social Network (SNET) Group

1412‧‧‧SNET processing circuits and software

1500‧‧‧(multiple) social devices

1502‧‧‧(secure) SNET group/subgroup

1504‧‧‧SNET Group

1506‧‧‧SNET gateway

1508‧‧‧SNET Gateway

1510‧‧‧Docking and Access Module

1512‧‧‧SNET processing circuits and software

1514‧‧‧(Cloud-based) Registrar

1516‧‧‧Admin/Directory Service

1518‧‧‧Social device resources and other group resources

1600‧‧‧(multiple) (members/guests/visitors) social devices

1602‧‧‧Social resources

1604‧‧‧Access and distribution management functions

1606‧‧‧Access rights

1608‧‧‧Access control function

1610‧‧Arbitration and dynamic (re)distribution

1612‧‧‧Access view control

1614‧‧‧ (browser-based and / or download or pre-installed) application

1616‧‧‧Safety operation

1700‧‧‧ social devices

1701‧‧‧Users

1702‧‧‧Communication interface and transceiver circuit

1704‧‧‧Processing circuit

1706‧‧‧Device/group configuration information and other resources

1708‧‧‧User configuration information

1710‧‧‧User Interface Circuit

1712‧‧‧Software Management Application

1714‧‧‧ docking logic

1716‧‧‧Communication Protocol Control

1718‧‧‧Resource Management

1720‧‧‧Security/Authentication

1722‧‧‧Basic device (core or bottom layer) function

1724‧‧‧Storage

1726‧‧‧SNET/SNET Group/SNET Subgroup

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

2 illustrates a schematic block diagram of a representation in accordance with various embodiments of the present invention.

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

Figure 4 illustrates a schematic block diagram in accordance with various embodiments of the present invention.

FIG. 5 illustrates a timing diagram depicting a travel social network in accordance with various embodiments of the present invention.

Figure 6 illustrates a flow chart in accordance with various embodiments of the present invention.

Figure 7 illustrates a flow chart in accordance with various embodiments of the present invention.

Figure 8 illustrates a flow chart in accordance with various embodiments of the present invention.

Figure 9 illustrates an embodiment of a social networking environment in accordance with various embodiments of the present invention.

Figure 10 illustrates a social networking infrastructure and social devices in accordance with various embodiments of the present invention.

11 illustrates a schematic block diagram of an embodiment of a social device in accordance with various embodiments of the present invention.

12 illustrates a schematic block diagram showing social resource access of a social network group/subgroup in accordance with various embodiments of the present invention.

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

14 illustrates social device membership and access in a social network group/subgroup in accordance with various embodiments of the present invention.

15 illustrates social resource remote access of a social network group/subgroup in accordance with various embodiments of the present invention.

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.

17 illustrates a social device including an integrated function operable to support social network groups/subgroup members and communications, in accordance with various embodiments of the present invention.

As used herein, the terms "social network," "SNET," "social network system," "social network infrastructure," and the like, include groupings or social structures of devices and/or individuals, and between the devices and/or Or personal connections, links, and interdependencies. Members or participants in SNET or related to SNET (including devices) may be referred to herein as "members", "users", "members", "nodes", "social devices", "SNET members", "SNET members", "SNET devices", "user devices" "and / or "module". In addition, the terms "social circle", "social group", "SNET circle", "SNET sub-circle", "SNET group", and "SNET sub-group" generally mean SNET including SNET devices, depending on the context. It includes human SNET members, device SNET members, personal area networks ("PAN"), and so on.

Referring now to Figure 1, a social network (hereinafter "SNET") packet hierarchy 100 is illustrated in accordance with various embodiments of the present invention. In some embodiments, the SNET packet hierarchy 100 includes one or more layers of the SNET infrastructure, at least partially surrounded by SNETs, which may be docked (hereinafter interchangeably referred to as "associated", "connected", etc. Other SNET infrastructure, SNET groups, social devices, etc. For example, in the illustrated embodiment, one level of the SNET grouping hierarchy 100 may include a service 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 embodiments, various levels may be docked such that "higher" levels may be docked to a "lower" level to provide "lower" levels of access to the various capabilities provided by the "higher" level.

In some embodiments, 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, the service SNET infrastructure 101, some or all of the one or more client SNET infrastructures 103, 105, and 107, some combination thereof, etc. may be by one or more social service support devices 111, One or more client social devices 131, 141, and 151, some combination thereof, etc. are managed. Processing systems may include, but are not limited to, one or more examples of processing circuits distributed across one or more server devices, network nodes, some combination thereof, and the like.

For example, in the illustrated embodiment, the SNET grouping hierarchy 100 includes the first The service SNET infrastructure 101 in the hierarchy and the plurality of client SNET infrastructures 103, 105 and 107 in the second hierarchy. 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 are not limited to, customers End, SNET members, SNET non-members, SNET guests, some combinations of them, etc. For example, the service SNET infrastructure 101 can include, but is not limited to, user devices 111, applications 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 one associated with one or more specific clients (hereinafter referred to interchangeably as users, members, visitors, guests, etc.) More than one social device 131. 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 device 131 in the client infrastructure 103 can 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 Model Application Serial No. 13/408,986, entitled "Social Device Resource Management", (Attorney Docket No. BP23776), filed on February 29, 2012, the entire contents of which are incorporated in This is for reference. In some embodiments, a device, SNET group, etc. that is connected to another SNET group becomes a member of the docked SNET group. By docking the client social device 131 to the client SNET group 135, the user associated with the client SNET group 135 can interact with the SNET group 135 by interacting with the social device 131 docked to the SNET group 135. As noted herein, members, clients, users, etc. may include, but are not limited to, human members of SNET or some other network, device members of SNET or some other network, some combination thereof, and the like.

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., one or one via a docking method Above SNET A group, the one or more SNET groups may provide access to a desired capability selection by interacting with the one or more SNET groups. For example, the service SNET infrastructure 101 illustrates capabilities that may be provided by various service support social user devices 111, various social service applications 113, and the like. In some embodiments, access to the social service device 111 is supported by various services, either directly or through interaction with the SNET group 115 docked to the service support social user device 111, either directly or through a SNET group that is connected to the social service application 113. 119 interactions, access to various social service applications 113, etc., may be provided to SNET members. One or more capabilities provided by device 111 and application 113, SNET groups 115 and 119 that are coupled to device 111 and application 113, some combination thereof, etc., may be combined into a single SNET group, which may be a single SNET group Provides access to one or more capabilities provided by devices, services, applications, SNET groups, some combination thereof, and the like.

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

In some embodiments, access to capabilities provided by one or more SNET groups, infrastructure, etc. can be accomplished by docking one SNET group to another SNET group. For example, the client SNET group 135 can be docked to the SNET group 117 via the docking method 125, thereby enabling the user of the client infrastructure 103 to access the capabilities provided by the SNET group 117 through the client SNET group 135. In particular, where one or more social devices 131 are docked to the client SNET group 135, the user may access the SNET group via one or more of the social devices 131 that interface with the client SNET group 135. 117 provides the ability. The docking method 125 can include connecting the client SNET group 135 as a member of the SNET group 117; docking the client SNET group 135 via one of the various processes described herein and at least in the following (also referred to herein as " Associated") to SNET Group 117: US Utility Model Patent Application Serial Number 13/342, 301, titled "Social Networking Device Members and Applications", (Attorney Case No. BP23711), filed on January 3, 2012, US Utility Model Patent Application Serial No. 13/408,986, titled "Social Device Resource Management", (Attorney Case No. BP23776), filed on February 29, 2012, the entire contents of each case are hereby incorporated by reference.

As shown in the above embodiments, users entering locations including, but not limited to, shops, restaurants, hotels, businesses, public areas, etc., may desire to access services, applications, information provided by, but not limited to, SNET groups associated with the venue. , devices, some combination of them, etc. Instead of individually docking individual user devices with the SNET group, the user can simply interface the personal SNET group that is connected to the user device with the SNET group associated with the site, thereby permitting the user to have already passed the user with his personal SNET group. Some or all of the docked devices access the location capabilities. As yet another example, a hotel may provide various capabilities through the SNET group including, but not limited to, call routing telephone service access, specific television device control, data inventory fetching, some combination thereof, and the like. The guest can simply connect his personal SNET group to the hotel SNET group and then access the capabilities provided through the hotel SNET group through the device that interfaces with his personal SNET group, rather than simply connecting his personal device to the hotel The SNET group utilizes the capabilities provided, including but not limited to: docking the smartphone device to the hotel SNET group to utilize the call routing phone service, docking the computer device to the hotel SNET group to control a particular television device, and the like.

In some embodiments, the SNET group is docked such 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, in the case where a user associated with the first client SNET infrastructure 103 can only access the capabilities provided by the serving SNET infrastructure 101 by interfacing with the SNET group 117, the service SNET infrastructure 101, the customer can be One or more processing systems, devices, etc. associated with the end SNET infrastructure 103 and the like utilize various security levels to ensure capability access. Moreover, in some embodiments, the SNET infrastructure is passed through The access capabilities provided by two or more groups provide an additional level of security. For example, where access to capabilities provided by the serving SNET infrastructure 101 requires the client SNET group 135, 145, 155, etc. to be docked to the SNET group 117, a more secure connection with various security levels may be utilized, via A single docking, association, etc. management between the client SNET group and the SNET group 117 can easily permit, change, limit, terminate, and the like. Processing systems, devices, etc. associated with the service SNET infrastructure 101, the client SNET infrastructure 103, etc. may be based on input received from users, third party entities, some internal logic device, time period elapsed, and client SNET infrastructure 103 associated client social device 131 geographic location changes, some other triggering event, some combination thereof, etc. to manage the association.

In some embodiments, the selection and docking method 125 can be automated, automated, some combination thereof, and the like. For example, by triggering based on an infrastructure user location, the docking method may be automated, including but not limited to a user associated with a particular client SNET group 135, a user associated with social device 131, one or more of social devices 131 Geographical proximity to a certain combination of them. In some implementations, a user may provide one or more associated rules that may provide conditions under which one or more particular client SNET groups 135 may interface to other SNET groups. Conditions may include, but are not limited to, geographic proximity to one or more social devices 131 associated with a particular client social device 135 that is associated with an infrastructure 103 associated with the SNET group 117. Authorized users, SNET groups 135, social devices 131, some combination thereof, etc., are authorized to interface the client SNET group 135 with the SNET group 117, some combination thereof, and the like. The associated rules can be communicated to social devices 131 that interface with a particular SNET group 135, processing systems that manage various SNET groups, some combination thereof, and the like. One or more of the processing system, social device 131, some combination thereof, etc. may monitor the client SNET group 135, the social device 131 that is connected to the client SNET group 135, and one or more One or more of one or more SNET groups 117 associated with one or more attributes of the client SNET group 135, the docked social device 131, some combination thereof, etc. (related to one or more associated rules) The above attributes are used to determine whether one or more SNET groups, social devices, etc. are docked together. The associated rules can be changed by the user, the processing system, some other entity, etc., to create new rules, delete rules, change rules, and the like. For example, with the client SNET group 135 (possibly having previously passed the associated rules to the processing system, the associated rules prohibiting the client SNET group 135 from being connected to the SNET group outside of the threshold geographic proximity of the social device 131 Group 117) associated users may immediately transmit associated rule changes, including but not limited to: changing threshold geographic proximity; authorization to client-side SNET group 135 to a particular SNET group 117 on a item-by-item basis; ordering client SNET Group 135 is undocked from another SNET group; some combination of them, and the like.

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

In some implementations, the selection and docking method 125 can be controlled, managed, etc. by one or more different social devices, processing systems, and the like. For example, an SNET infrastructure processing system (which may include one or more processing circuit instances distributed across one or more server devices, network nodes, some combination thereof, etc.) may be based on one or more user interactions with the SNET Associated rules, one or more inputs, some internal logic, some combination thereof, etc., control the docking and undocking of one SNET group to another SNET group. As another example, a social device may control docking of one or more SNET groups based on user interaction with SNET, one or more associated rules, one or more inputs, some internal logic, some combination thereof, and the like. And release the docking. In some embodiments, processing systems, social devices, some combination thereof, etc. that are authorized to manage "higher level" infrastructure may manage one or more "lower levels" that are docked to a "higher level" infrastructure. One or more attributes of an infrastructure access. For example, a processing system authorized to control a "higher level" social service infrastructure 101 can change access to certain capabilities, restrict access to certain capabilities, via a pair of SNET groups based on input, some other logic. Decommissioning with the device to terminate access, some combination of them, and the like. The processing system may determine that the triggering event (including but not limited to all social devices 131 that interface with the client SNET group 135 that is connected to the SNET group 117 has been geographically close to a predetermined threshold that is geographically associated with the SNET group 117) Distance), based on the decision, de-docking the client SNET group 135 from the SNET group 117, partially or completely restricting the client SNET group 135 from accessing certain capabilities provided by the SNET group 117, some combination thereof, and the like.

Referring now to Figure 2, various representations in accordance with various embodiments are discussed. In some In an embodiment, a user, a SNET member, a SNET non-member, etc. associated with the first infrastructure that interfaces with the second infrastructure may be passed through one or more docked SNET groups, social devices, some combination thereof, and the like. Representing a graph interaction to access capabilities provided by the second infrastructure, the representation may be a social system associated with the first infrastructure by the processing system, a portion of the second infrastructure, a portion of the first infrastructure, A portion of the data provided by the device, the second device associated with the user, some combination thereof, and the like. For example, the client SNET group 135 of the first social client infrastructure 103 and the social service infrastructure 101 (providing device access capabilities 111 and 113 provided by the SNET groups 115 and 119) as shown above in FIG. In the case where the SNET group 117 is docked, the user can interact via the representation map 201 (as part of the data provided by one or more SNET systems, SNET, SNET infrastructure, SNET groups, SNET devices, some combination thereof, etc.) To access the capabilities provided by the SNET group 117. In the event that the client SNET group 135 interfaces with one or more client social devices 131, the user can interact with a portion of one or more social devices 131 to directly communicate via the client SNET group 135. Devices 131, some combination thereof, etc., access the capabilities provided by SNET group 117.

In some implementations, the representation can provide a simplified representation of the capabilities that can be accessed via docking of one or more SNET groups. For example, although SNET group 117 provides capabilities 111 and 113 by merging SNET groups 115 and 119 (providing capabilities 111 and 113), it is provided to members, docking, accessing SNET group 117 via docking client SNET group 135. The representation 201 to the social devices 131 of the docking client SNET group 135, some combination thereof, etc. may only show that the SNET group 117 provides little or no groups 115 and 119 (combined to make the SNET group) 117 provides the ability to enable capabilities 111 and 113 to be indicative of real complexity. Members via access capabilities 111 and 113 of representation 201 may be included and included in representation 201 (as one or more SNETs, SNET systems, SNET infrastructure, processing systems, devices, SNET groups, some of their groups) The capabilities in a portion of the data provided by the representation represent interactions to access capabilities 111 and 113. In some implementations, the interaction with representation 201 can be continued via interaction with a portion of the docking social device 131, including but not limited to a user interface, a portion of a docked client SNET group 135, some combination thereof, and the like.

In some embodiments, 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 member access to be associated with the first SNET group Some or all of the information, the capabilities provided by the docking SNET group, some combination of them, etc. are possible. For example, in the illustrated embodiment, the client SNET group 145 can be docked to the client SNET group 135 such that the client SNET group 145 accesses some or all of the information provided to the members of the client SNET group 135. The capabilities provided by the SNET group 117 to the client SNET group 135, some combination thereof, etc., are made possible.

As the above example, a passenger may desire to associate a client SNET group 145 associated with his company with a personal client SNET group 135 associated with his business trip. By docking the corporate client SNET group 145, the passenger can cause the corporate client group 145 members to view the passenger's whereabouts (when they are provided to his personal client SNET group 135), access via the same or similar representation map 201 At least some of the capabilities provided to the passenger by docking with other SNET groups (eg, accessing and managing his travel reservations, providing relevant travel and business update information to the passengers instantly, etc.), some combination thereof, etc., are possible. The docking may be managed by the guest social device 131, the social service infrastructure 101 based on input provided by the passenger, one or more other devices, some combination thereof, and the like. For example, a passenger may only authorize a docked third party SNET group 145 to have limited access to information associated with his personal client SNET group 135, restrict access to capabilities provided by the docked SNET group 117, etc., and the passenger Access restrictions, de-duplication, some combination thereof, etc. may be authorized based on instant input, one or more trigger events, and the like. The triggering event can include, but is not limited to, one or more social devices associated with the passenger 131 associated geographic location changes, authorization information changes provided by the entity, and the like.

In some embodiments, different representations may be provided in the case where a separate SNET group, SNET device, etc. associated with a "lower level" infrastructure is docked to a "higher level" infrastructure in the 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 with The SNET group 117 associated with the social service infrastructure 101. In the illustrated embodiment, the first representation map 201 is provided to members of the ability to access the SNET group 117 through the client SNET group 135, the docking social device 131, some combination thereof, etc., the nth representation 203 through the client End SNET groups 155, docking social devices 151, some combination thereof, etc. are provided to members of the SNET group 117 capabilities. In some embodiments, the representations provided to the individual docked SNET groups are different, separate, etc. with respect to each other. For example, in an implementation where the SNET group 117 provides capabilities associated with the hotel experience, including but not limited to remote control of the television device and the docking client SNET group 135, 155, etc. associated with a separate hotel guest, via The capabilities provided by one or more separate representations may be different such that hotel guests have access to the ability to customize for the guest, including but not limited to remote control of a particular television device associated with the hotel room. In the case where 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 SNET group, some combination thereof, etc., and then connect the created SNET group to another A SNET group to access the capabilities provided by other SNET groups.

Referring now to FIG. 3, some implementations of SNET packet hierarchy 300 may enable client SNET group 135 to interface with 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 the two infrastructures 301 and 303 through a single combined SNET group 337. The global social service infrastructure 301 includes a social service support user device 311, a social service application 313, and various SNET groups 315, 319, and 317 (which provide some combination of capabilities provided by infrastructure 301) provide the capabilities. In addition, the local/regional social service infrastructure 303 also includes provided by the social service support user device 321, the social service application 323, and various SNET groups 325, 329, and 327 that provide some combination of capabilities provided by the infrastructure 303. Ability. The combined local/regional and global SNET group 337 provides the capabilities provided by the social service support user devices 311 and 321 and the combination of social service applications 313 and 323 provided by the two infrastructures 301 and 303. In the case where the client SNET group 135 can interface with the SNET group 337, the client SNET group 135 members will be able to access the two infrastructures by docking a single client SNET group with a single SNET group 337. The capabilities provided.

In some embodiments, the representation 305 provided to the client SNET group 135 (accessing the capabilities provided by the SNET group 337) member 305 includes only the infrastructure provided by the two infrastructures 301 and 303 (initial provisioning capabilities) Some or all of some or all of them indicate irrelevant combined 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 a representation set 305 in a combined set of social service support user devices 331; likewise, from two The social service applications 313 and 323 of the infrastructures 301 and 303 are presented in a representation set 305 in a combined set of social service applications 313. Moreover, SNET groups 315, 317, 319, 325, 327, and 329 in an infrastructure that is partially or fully combined into SNET group 337 may represent a portion of the capabilities of FIG. 305 for accessing capabilities provided by SNET group 337 or It is completely transparent. In some embodiments, the members of the access representation graph 305 can restore the overall complexity of the combination of infrastructures 301 and 303 in FIG. 305 so that the members can view various SNETs specific to various infrastructures and capabilities provided. Groups and abilities.

As an example of the illustrated embodiment, a hotel chain can provide a global SNET infrastructure 301 that provides common capabilities for all hotels that franchise, such as a global media database, corporate contact information. Information, information databases, some combination of them, etc. In addition, a local hotel may desire to have a local SNET infrastructure 303 that provides access to local entertainment, dining, news information, devices, device access specific to local hotels, some of them Combinations, etc. The hotel may desire to combine the hotel chain capabilities provided by the global SNET infrastructure 301 with the local specific capabilities provided by the local SNET infrastructure into a combined SNET group 337 to enable the hotel guest to utilize a single docking method and via a single representation 305 ( It is possible to provide global and local capabilities in partial or complete combinations to access global and local capabilities.

In some embodiments, a combination of capabilities provided by a separate infrastructure is partially or fully managed by one or more processing systems, social devices, members, applications, some combination thereof, and the like (associated with one or more infrastructures). For example, in the illustrated embodiment, the processing system associated with the local SNET infrastructure 303 can manage the ability to combine capabilities from the infrastructures 301 and 303 into SNET groups 337 that manage the client SNET group 135 and SNET groups. 337 docking, some combination of them, etc.

In some embodiments, access to the SNET group 337 by the client SNET group 135 may be via a network manager, processing system, social device, or some of them based on input, trigger events, some other internal logic, and the like. Combination, etc. to permit, limit, terminate, etc. For example, when a social device that interfaces with client social device 135 leaves a location associated with SNET group 337, by terminating or restricting access by the docking permission, changing some or all of the capabilities provided by SNET group 337 The interactive authorization, de-duplication of the client social device 135 from the SNET group 337, some combination thereof, etc., may terminate the client SNET group 135 accessing the capabilities provided by the SNET group 337. In response to a triggering event, including but not limited to, a predetermined time elapses after entering or leaving the venue, etc., this may occur automatically. In some embodiments, the client SNET group 135 can maintain residual access to the SNET group 337 after the device that is connected to the client SNET group 135 leaves the venue. For example, the location associated with SNET group 337 is a hotel and with the client SNET group Where the group 135 associated member belongs to a unique hotel member, the client SNET group 135 associated with the member still receives at least one of the capabilities provided by the SNET group 337 after the docking device leaves the venue. Take, including but not limited to, call routing telephone service.

In some embodiments, a SNET group associated with a member (including a human, device, etc.) can be docked to another SNET group to enable the member to access or receive services, contact information, and SNET groups. Other related information, exchange of information, some combination of them, etc. are possible. 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 with a device may approach 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, etc., will be docked to the SNET associated with the venue. The invitation of the group is provided to the human user via the device, to the device itself, to some combination thereof, and the like. The invitation may change depending on whether one or both of the human user and device are already SNET members, non-members, and the like. For example, in the case where the device is not a social device, the access point may provide the invitation to the device via a browser application or the like in the form of a web page, and the browser application or the like will provide the device with the SNET group option by the special member, Human users, some combination of them, etc. 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.

Invitations can be accepted through one of various acceptance methods. For example, where the social device receives an invitation (including a unique identifier that uniquely identifies an SNET group that invites a member to dock a SNET group, social device, etc.), the social device can access the access point, another device, via an independent path or the like, SNET, SNET groups, SNET subgroups, etc. interact to accept invitations with unique identifiers. Acceptance in the above examples may include simply providing a unique identifier and identifying information about the SNET group associated with the unique identifier offering, based on the unique identifier, the SNET group being docked to the SNET group associated with the venue. In addition, in the case where the non-social device attempts to access the access point and the access point pushes the web page to the browser application on the non-social device, the accepting method can be packaged. Including: accessing web pages, indicating willingness to interface with SNET groups, providing some other information, etc., such that non-social devices, ad hoc guest SNET groups, some combination thereof, etc. are accepted as docking to the SNET group associated with the venue group.

After accepting the invitation, members, human users, devices, some combination thereof, etc. may at least gain 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 the SNET group that is connected to the local SNET group can access the various services via one or more devices docked to his personal SNET group. , including but not limited to online newspapers, videos, project sales lists, door-to-door delivery options, on-site delivery ordering interfaces, other information, some combination of them, etc. In another example, where the venue is a hotel, private residence, etc., a member of the SNET group that is connected to the location-based SNET group may be obtained via one or more device pairs that are docked to his personal SNET group. Access to services, information, and the like, including but not limited to access to local or remote stored content items, contact information, access to field device control functions, some combination thereof, and the like. In another example, where the venue is a shopping mall, the access point can provide, push, etc. the device, device user, some combination thereof, etc., to the SNET group associated with the mall. The access point may require the device, user, etc. to attempt to access the access point before the invitation is provided to the device, user, etc. in the form of a unique identifier, web page, or the like. Services associated with the SNET group may include, but are not limited to, advertisements, sales, and coupon information provided by computing devices of various stores within the mall; mall map services, showing specific store locations that are connected to the SNET group; a music service that provides music or other media content provided by a media source associated with a SNET group to those connected to the SNET group; a directory service; a search engine associated with anything in any store in the store; Combination, etc.

In some embodiments, the access point supports invitation provisioning to the SNET group, invitation processing acceptance, member, ad hoc members, and SNET group potential members to route communications between the SNET, the SNET group network, and the like. The device may need to attempt to access the memory Take a point to receive the invitation provided by the access point. In some embodiments, the access point automatically provides an invitation to the access point to determine that any device has crossed the threshold, such as a predetermined proximity to a venue, location, or the like. Those that are connected to the SNET group (including ad hoc members, SNET groups, ad hoc SNET groups, some combination thereof, etc.) may be able to couple with other devices, users, members, etc. that also interface with the SNET group. The peering to the SNET group may be terminated or restricted after crossing another or the same threshold. For example, in the case where the device entering the location is provided to be connected to the SNET group through the access point, after the determination device has left the location, the access point may limit, terminate, etc. the ad hoc docking.

4 illustrates interactions between various SNET systems, infrastructure, groups, devices, etc., in accordance with various embodiments. In the illustrated embodiment, SNET infrastructure 402 (which may be included in 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 can represent an SNET infrastructure associated with SNETs, SNET groups, processing systems, SNET accounts, SNET members, humans, devices, social devices, some combination thereof, and the like.

In some embodiments, various SNET groups are created through the SNET infrastructure based on input from users, members, processing systems, devices, SNETs, SNET groups, some combination thereof, and the like. For example, where the SNET infrastructure 402 is associated with a SNET member account, account members can provide input to the SNET infrastructure 402 to create the SNET group 404. Inputs may include, but are not limited to, social devices to be docked with group 404, attributes of group 404, information for one or more members of accessible group 404, some combination thereof, and the like.

In some embodiments, the SNET group in the SNET infrastructure interfaces with another SNET group. For example, in the illustrated embodiment, SNET group 404 interfaces with SNET group 412 and SNET group 414 via docking links 407 and 409, respectively. Interfacing one SNET group to another SNET group can be accomplished via one or more different docking methods, including but not limited to by one or one The docking of the above devices, SNET groups, etc. is uniquely initialized.

In some embodiments, the docking method can include an interaction between at least a first SNET group and a second SNET group. For example, where the SNET group 412 is docked to the SNET group 404 via the docking link 407, the SNET group 412 and the SNET group 404 can reference one or more members between the two SNET groups, the docking device , functional elements, accessible information, some combination of them, etc. to exchange security information processing. The exchange enables 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 capabilities of docking SNET groups, devices, members, and the like.

In some embodiments, the docking method can 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, This includes, but is not limited to, verifying the optimal docking location; configuring a docking link representation to users, members, and the like. For example, 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 SNET groups included in SNET infrastructure 424. In this case, the method of associating, docking, etc., the SNET group 420 with another SNET group in the SNET infrastructure 424 may include, but is not limited to, determining that one or more of the SNET group 420 is different from the SNET infrastructure 424. The optimal docking between the SNET groups is such that one or more capabilities of the SNET group 420 members to access the SNET infrastructure 424 are made possible. As shown in the illustrated embodiment, the SNET group 420 is determined in the event that the optimal docking configuration is determined to include, but is not limited to, the SNET group being docked to two SNET groups 432 and SNET groups 434 for access capabilities. The SNET group 420 can be interfaced with the two SNET groups 432 via the docking link 446 and the SNET group 434 via the docking link 444 as part of the SNET group 420 and the various SNET groups provided by the SNET infrastructure 424. Part of a single docking method associated with capabilities. The docking links 446 and 444 can be managed by a single docking specification 442, some other combination of docking specifications that are part of the SNET infrastructure 424, some combination thereof, and the like. In some embodiments, the docking link and the docking specification can 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, and the like.

In some embodiments, the docking method of associating SNET group 420 with SNET infrastructure 424 via interfacing with two SNET groups 432 and SNET group 434 can include configuring a docking link representation such that members of the access capability The entire complexity of interfacing links, interactions, etc. between various SNET groups, devices, SNET infrastructure, etc., is not seen. In the illustrated embodiment, for example, a docking method of interfacing SNET group 420 with SNET groups 432 and 434 can include configuring a representation, representation, etc. of capabilities of SNET group 424 that can be accessed by members of SNET group 420. To hide the fact that the SNET group 420 is connected to two SNET groups via two docking links. Simplified representations, representations, and the like may only present SNET group 420 views that interface with certain capabilities of SNET infrastructure 424. In some embodiments, members may adjust, switch, or otherwise manipulate the complexity of representations, representations, etc., such that the complexity of interfacing links, interactions, etc., between SNET infrastructure, SNET groups, social devices, and the like The part or the entire view is presented to the member.

In some embodiments, establishing multiple docking links may provide additional security for certain capability accesses. For example, a docking link between the SNET group 420 and the SNET group 432 provides a docking link 446 with a higher security link to a certain capability than the docking link 444 to the SNET group 444, via the docking chain Where the paths 444 and 437 provide an indirect link to the SNET group 432, some combination thereof, etc., the docking method can include establishing a docking link 446 to provide for a capability (the link is used to access another More secure link of capacity). In some embodiments, establishing multiple docking links can provide more efficient access to capabilities, services, etc. than a single docking link. For example, the docking method includes determining that the docking links to the two SNET groups 432 and SNET group 434 can more efficiently access the SNET infrastructure than a single docking link. 424 In the event that certain capabilities are possible, the docking method may include, but is not limited to, establishing a plurality of docking links 446 and 444 to the SNET group of the SNET infrastructure 424.

In some embodiments, docking links between various SNET groups, social devices, etc., are managed based on various docking specifications. In some embodiments, the docking specification manages one or more specific docking links, etc., for example, rather than by means of restrictions, access restrictions, restrictions, permissions, etc., security access requirements associated with various capabilities of the SNET group, Access cycles, trigger events, based on the restrictions, access restrictions, restrictions, permissions, etc., security access requirements, access cycles, trigger events, accesses will be changed, restricted, granted, terminated, and the like. For example, as shown in the illustrated embodiment, SNET group 404 includes docking specifications 406 and 408. In some embodiments, the docking specification 406 can manage the docking link 407 between the SNET group 404 and the SNET group 412. In some embodiments, the docking specification 408 manages the interfacing link 409 between the SNET group 404 and the SNET group 414. The docking specification may attempt to interface with the SNET group 404, either partially or completely through an early docking (instantly created as part of a docking method that interfaces the SNET group 404 to another SNET group provided by the SNET infrastructure) The SNET groups, some combination of them, etc. are pre-determined. For example, a member of the SNET group 404 can establish a docking specification 406 that limits the capabilities of the SNET group 412 member to be provided by the SNET group 404 based on subsequent triggering events, including but not limited to elapsed time periods. In some embodiments, the docking specification is specific to other SNET groups and devices, such that the SNET group 404 is docked to various SNET groups with associated attributes. For example, the docking specification 406 may determine that the SNET group 404 is to be docked to the SNET group 412 via the docking link 407 (associated with a geographic location within a predetermined threshold proximity to a geographic location associated with the SNET group 404), And if the geographic location associated with SNET group 412 exceeds a near threshold, then docked link 407 will be restricted, terminated, and the like.

In some embodiments, based on input from users, members, SNET systems, SNET infrastructure, docking devices, docking SNET groups, some combination thereof, and the like, Some or all of the docking specifications can be adjusted, managed, changed, created, deleted, and so on. For example, a member of the SNET group 404 can establish a docking specification 406 with the SNET group 412 to manage the docking link 407 to restrict certain capabilities of the SNET group 412 member to access the SNET group 404, and then with the SNET group 404, SNET The infrastructure 402, some combination thereof, etc. interact to change the docking specification 406 to provide SNET group 412 members with more access to the capabilities provided by the SNET group 404. In terms of existing docking links, docking specifications for managing potential docking links, some combination thereof, and the like, the docking specification management can be performed at any time, immediately, in ad hoc processing.

In some embodiments, the docking specification that manages the interfacing links between the "higher level" SNET group and the "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, by being part of higher level SNET group 404 Docking specifications 406 and 408 to manage interfacing links 407 and 409 between lower level SNET groups 412 and 414 and higher level SNET group 404 such that on a docking link with a lower level SNE group It is possible to control by a higher level SNET group.

In some embodiments, the docking specification can be customized by users, members, SNET systems, SNET infrastructure, SNET groups, social devices, some combination thereof, etc. to provide various levels of interaction and storage between various docked SNET groups. take. For example, in the illustrated embodiment, the docking specification 406 can provide that the docking link 407 provides for full two-way interaction, information, service, etc. sharing between the SNET groups 404 and 412 that are docked via the docking link 407. In another example, the docking specification 408 can provide that the docking link 409 provides a one-way group-group service access between the SNET group 404 and the SNET group 414 via the docking link 409, such that the SNET group Group 414 members may access at least some of the services provided by SNET Group 404 capabilities, while SNET Group 404 members may not have access to some or all of the information, services, devices, etc. associated with SNET Group 414. For example, the SNET group at the hotel guest docks with the hotel's SNET to allow hotel guests to access the hotel service via the hotel SNET group. In the case of capacity, managing the docking specification between the hotel guest SNET group and the hotel SNET group's docking link may specify that the hotel guest is restricted to access certain capabilities of the hotel SNET group, while the hotel SNET group is Any ability to restrict access to a hotel guest SNET group, including but not limited to accessing devices that are connected to a hotel guest SNET group. As discussed above, in some embodiments, docking specification access and interaction aspects can be changed at any time by various users, members, SNET groups, SNET infrastructure, and the like.

In some embodiments, the docking specification imposes certain restrictions on the ability to provide, give, etc. SNET group members to dock SNET group members. For example, the docking specification 406 can specify that only certain capabilities of the SNET group 404 are provided to the SNET group 412 members via the docking link 407. Docking specification 406 may also dictate that members of SNET group 412 have different accesses to different one or more capabilities of SNET group 404. For example, the docking specification 406 can provide that each member of the SNET group 412 is provided with one or more capabilities that uniquely access the SNET group 404.

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

In some embodiments, various SNET groups can be docked to each other 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, the SNET infrastructure 424 includes a SNET group 426 that is docked to the SNET group 432 via a docking link 429 managed by the docking specification 428, and also via the management of the docking specification 430. The docking link 431 is docked to the SNET group 434. In addition, 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 are each docked. The docking links between SNET groups 426, 432, and 434 can provide various levels of access, including but not limited to various levels of security. Moreover, in some embodiments, one of the SNET groups docked into the SNET infrastructure 424 may grant access to some or all of some or all of the SNET groups that one of the SNET groups is connected to.

For example, in the illustrated embodiment, SNET group 404 can be docked to SNET group 426 via docking link 439. Communication over the docking link 439 may be subject to various docking specifications depending on the origin and destination of the communication stream. For example, for media content originating from SNET group 404 via a group member device, storage or service or the like directly associated with SNET group 404, docking specification 438 can manage the media content via docking link 439 Any attempt to access. The accesses may include, but are not limited to, media content reception, media content provisioning, identifying media content, information associated with the media content, some combination thereof, and the like. For example, a foreign SNET group (including but not limited to a SNET group associated with a separate SNET infrastructure) is docked to the SNET group 404 (including from the SNET group 404 via a group directly associated with the SNET group 404) In the case of a group member device, a storage device, or a first, second, and third media content of a service, etc., the docking specification 438 may specify: 1) the first media content is not Recognized as existing at least the foreign SNET group; 2) the second media content can be identified as existing at least the foreign SNET group, but requires advanced DRM and is provided with reduced quality; 3) the third media content can be It is identified as existing at least the foreign SNET group and is provided in its original form without redistribution and consumption restrictions; some combination thereof, and the like. The docking specification 438 may also limit SNET group 404 access, allow the application to have been applied to the SNET group 426, the same or further restrictions of the SNET group 404, some combination thereof, and the like. Likewise, the docking specification restrictions imposed on data or media content originating from SNET group 414 may permit SNET groups 426, 434, 434, some combination thereof, etc. via SNET group 404, SNET group 420, some combination thereof Chain access.

In addition to the various docking specification restrictions imposed on local group offerings, various docking specification restrictions may also be applied to the chain offering. For example, SNET group 414 can freely provide any other SNET group via a direct docking link to SNET group 414, via an indirect link via a docking link to a SNET group (paired to SNET group 414), some of them Access to all offerings, including but not limited to services, content, data, docking device access, some combination thereof, and the like. In some embodiments, the freely provided access can be defined via a docking specification 416. However, the docking specification 438 can impose restrictions on access via the SNET group 404, including but not limited to: not allowing any external SNET group from the docked SNET group 404 (including but not limited to SNET groups 414, 412) Any access or cognition of some or all of the offerings of 420). In this way, according to the docking linkage and interlocking SNET group and device specifications, the offerings can be managed in various ways depending on the underlying needs. In some embodiments, the linkage and chain management of the overall offering is applied twice: once for each access direction. For example, the offering restrictions associated with the SNET infrastructure 402 may be quite different from the offering restrictions of the SNET infrastructure 424. Moreover, even though all relevant docking specifications within the SNET infrastructure 402 can at least allow limited access to specific offerings to the SNET group 426, for example, the access may not extend to the SNET group 432 due to: a ) Docking specification 428 is applied in addition to SNET More access restrictions beyond the required access restrictions of infrastructure 402; b) related docking specifications within SNET infrastructure 402 may limit alien linkages; some combination thereof, and the like.

For example, in an ad hoc travel network docking configuration, a passenger personal SNET group composition (e.g., SNET infrastructure 402) may desire to provide very limited access to a hotel SNET group composition (e.g., SNET infrastructure 424), while in other In the direction, the hotel SNET group can be freely provided to form a offering. The compositions need only provide access to any offerings, member identifications, information, etc. that they may be exposed to. For example, the passenger may choose to expose a) a payment service element located somewhere within the entire personal SNET group composition; b) an incoming message service of the passenger social smart phone; c) an administrator's incoming message service; d) a travel file storage Services; a combination of them, etc., and the hotel may choose to expose, provide, etc., including but not limited to: 1) regional catalogs, maps and other information services; 2) concierge services; 3) billing services; 4) scheduled services ; 5) networked office equipment; some combination of them. For example, the exposure may be defined in any case via various docking specifications associated with the originating SNET group, which is modified by the docking specification associated with the SNET group in the chained path to the destination SNET group.

In some embodiments, in addition to the group level, the docking specification can be extended to provide resolution. For example, the docking specification 428 that manages the docking link 429 may require human identification and various levels of security prior to providing access via the docking link 429 (even including offering identification). In another example, as defined by the docking specification 428, a passenger (which may be a member of the SNET group 404) may gain access to an element, service, or device participating in the SNET group 426 via and to a passenger docked to the SNET group 404. A particular offering provided by the required secure interaction of the local social smart phone, but some or all of the other members of the SNET group 404, other SNET groups, etc. may not have access to the particular offering. In other words, for one or more specific SNET group offerings, capabilities, offering identifiers, etc., and for one or more specific group members, member information, etc., specific interlocking specification details can be established to manage the entire access, This includes but is not limited to limited access. Therefore, although Capabilities are shown as distributed, associated with each link, etc., but the chained protocol flow can be managed through a single user interface and can be stored in a single repository.

In some embodiments, the default docking specification may apply default processing of offerings, accesses, interactions, etc., for one or more specific SNET groups, but allows authorized members, devices, SNET systems, SNET groups, SNET foundations Specific offering modifications, other access modifications, some combination of them, etc. required for facilities, some combination thereof, etc. Again, the entire default processing can be modified.

In some embodiments, the docking specification can be part of one or more SNET groups, SNET infrastructure, social devices, some other entity, some combination thereof, and the like. For example, where the docking method of docking the SNET group 404 to the SNET group 426 is initiated by a device that is connected to the SNET group 404, the docking specification 438 can be part of the SNET group 404. Moreover, where the docking method of connecting the SNET group 404 to the SNET group 426 includes a portion of the SNET infrastructure 424 that receives and permits the docking request from a portion of the SNET infrastructure 402, the docking specification 438 can be a SNET group Part 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 of the first SNET group (including but not limited to services, device access, applications, etc. Provided to one or more devices that are connected to the second SNET group. The docking request may originate from a device that is connected to the first SNET group, a device that is connected to the second SNET group, a first SNET group member, a second SNET group member, a third party, some combination thereof, and the like.

By docking to the SNET group 426, the SNET group 404 can access some or all of the capabilities of the SNET group 432 and the SNET group 434, as specified by one or more of the docking specifications 438, 428, 430, etc.; In the event that SNET group 404 interfaces with SNET group 434, SNET group 404 can access some or all of the capabilities of SNET group 426 and SNET group 434, as specified by one or more of docking specifications 438 and 436.

In some embodiments, various SNET groups and various SNET infrastructures Various SNET group dockings can include various access restrictions and restrictions. For example, where SNET group 404 is docked to SNET group 414 (connected to SNET group 420, all SNET groups within SNET infrastructure 402), various levels of interaction and access of various SNET groups may be managed via docking The management of the various docking specifications 408 and 416 of the link is determined. The three docked SNET groups 404, 414, and 420 all have access to some or all of the mutual capabilities, the SNET group 414 can access the capabilities of the SNET group 404, and the SNET group 404 can access the capabilities of the SNET group 414. SNET groups 404 and 414 can access mutual capabilities, while SNET group 420 accesses some of the capabilities of SNET group 404 and some of the capabilities of SNET group 414, some combination thereof, and the like. The interaction, access, docking, etc. can be performed without any interaction with third party entities, third party SNET groups, and the like.

In some embodiments, where a third party entity, a third party SNET group, etc., is included in the docking link, additional interaction with a third party entity, a third party SNET group, etc. is required. For example, where the SNET group 404 is connected to the SNET group 426, where the corresponding SNET group is part of a separate SNET infrastructure associated with individual users, members, etc., docking, access, etc. may be required Three-way interaction. 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 docking method between SNET groups associated with separate SNET infrastructure, users, members, etc., can be initialized, managed, etc. by various devices, processing systems, SNET systems, SNET infrastructure, and the like. For example, a docking between SNET group 404 and SNET group 426 may be through one or more devices that are connected to SNET group 404, one or more devices that are connected to SNET group 426, and to a third party SNET. One or more devices of a group, one or more processing systems, one or more SNET infrastructures, some combination thereof, etc., initiate, manage, and the like.

In some embodiments, the SNET "Travel" group facilitates and/or monitors travel activities, activities associated with social device aspects, parties associated with social devices Faces, SNET groups associated with members, some combination of them, and so on. An activity may include one or more events (which may include a triggering event) that may affect at least one aspect of the SNET group, including but not limited to membership, information access, some combination thereof, and the like. A SNET travel group may be connected 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, and the like. SNET Travel Group members (temporary or permanent) receive unrestricted access to detailed hotel information (including confirmations, prices, feedback, entertainment facilities, restaurant recommendations, nearby attractions, etc.), social events / outings , babysitter monitoring services, some combination of them, etc. In some embodiments, 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, they 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, etc., in some combination or the like.

FIG. 5 illustrates an implementation of a social networking environment that adaptively triggers events, triggers, and the like. Some implementations of the SNET group may be responsive to externally applied or internally applied triggering events, such as certain event completions, location changes, time lapses, some combination thereof, and the like. As shown in FIG. 5, the illustrated embodiment is a SNET group designed to be used during travel, such that SNET travel group 500 responds by adding, removing, or otherwise modifying information, access, and members of the SNET group. Some travel events are completed, location changes, and upcoming events. The illustrated embodiment also illustrates the changes experienced by the SNET travel group as it progresses. The illustrated embodiment shows SNET travel groups for short-term business trips, including departure and return flights, destination hotel stays, and meetings with destination partners.

As indicated by state 540, at the beginning of the trip, SNET travel group 500 includes two docking entities, a social group 502 associated with the traveler's wife, and a social device 504 associated with the individual the passenger meets at the destination. In some embodiments, SNET The travel group 500 members may include SNET accounts specifically for members of the SNET travel group 500 such that any social devices associated with the members are part of the SNET travel group 500. In addition to docking entities 502 and 504, the SNET travel group at state 540 includes passenger voyages 506 and 510 for his departure and return flights and information 508 related to his hotel reservation. The above members and information may all be manually added from the SNET travel group by the passenger or some other entity, by the travel agency or device, by the docking group 502 member, by the docking device 504 user or social device, some other internal logic of the SNET, etc. , change and remove.

As indicated by line 512, his SNET travel group 500 adapts to state 550 after the passenger completes his departure flight and arrives at his destination. Adaptability may be partially or completely through manual entry from the passenger to the SNET travel group 500, by social device automation associated with the passenger, processing system, infrastructure, etc. (the passenger has provided one or more authorizations, associated rules, etc., The one or more authorizations, associated rules, etc., set SNET groups, social devices having various attributes based on one or more triggering events as determined by one or more social devices, processing systems, some combination thereof, and the like This can be achieved by docking, granting more or less access, and uncoupling conditions. When the departure flight is completed, the SNET travel group 500 removes the departure voyage 506 from the information associated with the SNET travel group 500 when the event has been completed. Additionally, in response to a change in location, the SNET travel group 500 can interface with the SNET group 514 associated with the guest hotel reservation 508 and dock one or more potential taxi cabs in accommodation, advancements, etc. that the passenger may need. Social device 515.

As indicated by line 516, after the passenger meeting is completed and the return flight is ready, the SNET travel group 500 has adapted state 560 after responding to his meeting and his hotel checkout completion. When the passenger checks out of the hotel, the hotel SNET group 514 and the taxi cab social device 515 are un-docked 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 completed, the meeting partner's device 504 is removed from the SNET travel group 500, and They are no longer interested in passenger travel. The only remaining items included in the SNET travel group 500 or docked to the SNET travel group 500 are the passenger's upcoming return flight 510 and the social group 502 associated with the traveler's wife.

In some embodiments, adding, changing, and removing certain information, docking, changing certain device and group accesses, and undocking from certain devices and groups as the passenger travels forward causes the passenger to interact with the majority Information and physical interactions related to upcoming possible trip events are possible, such as reaching new destinations, preparing events, finding landmarks, dining, accommodation, and the like.

According to various embodiments, various techniques, such as those described elsewhere herein, may be utilized to determine the presence and location of SNET infrastructure, SNET groups, SNET sub-groups, docking social devices, some combination thereof, and the like. The location information can be utilized in a variety of ways including, but not limited to, the manner 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., of course including account metadata. Cloud-based storage can be used for a variety of information, including location (eg, GPS), to extend social networking functionality (eg, automatic SNET grouping/introduction, peripheral device automation/selection, etc.). Location-based groups can also be formed for travel, tracking, invitations (and timeouts), and the like. In some embodiments, location information and other factors may also be used to select an online game contest/team. For example, IP address selection can be performed in a DNS-like manner for related domain names. In operation, a game player SNET/SNET group or the like can be formed based on location factors, SNET/SNET group attributes, network attributes, some combination thereof, and the like.

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

6 is a logic diagram of an embodiment of a method of allocating social resources in accordance with various embodiments. In an initial step S600, a 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.) is established to identify associated SNET groups and social resources. The SNET account, associated SNET group and social resources may include one or more capabilities provided by one or more devices, applications, services, SNET groups, some combination thereof, and the like. Next, or simultaneously, in step S602, one or more social resources, SNET groups, etc. are "docked" (eg, online, coupled via near field communication (NFC), or via a network operation) to the SNET account. The docking may include a security and authentication operation step S604. In some implementations, the docking can include a merged SNET group establishment, and the consolidated SNET group will integrate the SNET group, social resources, and the like.

With the creation of one or more SNET groups or (sub)groups that include docked SNET groups (eg, merged SNET groups) and select social devices, applications, services with related or specific characteristics and interdependencies, etc. The other social resources, some combination thereof, etc., the method continues in step S606. In one embodiment, SNET groups and social resources can be docked by dragging and dropping user interfaces or other components. In step S608, access levels and views are manually or automatically defined 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 a request hierarchy setting and allowing a personally customized (pop-up) form or form. A portion of the SNET infrastructure may select a particular SNET group, social device, SNET member (device or human or itself) associated with one or more SNET groups and SNET devices to exhibit hierarchical characteristics and allow access rights modification . In some cases The access rights selection can be based on profile data and other characteristics of a particular device, user, or group seeking to access social resources. In addition, different access rights (including content and capability access views) can be assigned to different social device resources or resource groups, or to specific requests for social resource access.

In step S610, the access level/view attribute is transmitted to an authorized merged SNET group member, which may include a social device (including a member's social device), a human member, a SNET, or one or More than one SNET group. Wherein, it may include providing different content and capability access views for a given docked 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 levels and views transmitted in step S610. For example, social device resource allocation may require the allocation of resources exclusively for use by a docking SNET group member that is subject to reallocation, either permanently or temporarily. For example, if a second SNET group member (or non-member) with higher priority or higher resource access rights requests access to previously assigned social device resources, subsequent redistribution may occur. In some embodiments, if/when a social resource becomes available to some extent, the resource can be dynamically provisioned and distributed. Management of social resource reserves (including related service termination) may be performed by separate devices, groups of devices, and/or centralized or distributed SNET processing circuits, including but not limited to one or more processing systems and software.

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, in accordance with various embodiments. First, the social resource availability accessed by the SNET group/device is determined in step S702. 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 the like. Next, access rights and access views are established in step S704, including but not limited to one or more representations of social resources. Depending on the context, and determined by one or more SNET nodes, processing systems, devices, some combination thereof, etc., with social resource control, or by an authorized entity requesting access to social resources It is determined that the access rights and access views can provide various access levels with different granularities.

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

Referring now to Figure 8, a logic diagram of an embodiment of a method 800 of controlling SNET group operations in accordance with various embodiments is illustrated. Activating or docking a social device, a first SNET group, an SNET subgroup, a social device that interfaces to a first SNET group, a social device that interfaces to a second SNET group, an SNET infrastructure, is associated with an SNET infrastructure After one or more processing systems, devices, etc., the account information is automatically (or via a setup prompt) provided to the social device, the first SNET group, the SNET subgroup, the social device that is connected to the first SNET group, and the like. Next, in step S802, social resource operation control associated with one or more processing systems, devices, etc. associated with the second SNET group, SNET infrastructure, SNET infrastructure or group (which may include, but is not limited to, Services, device access, applications, social resources, some combination thereof, etc.) are assigned to social devices, first SNET groups, SNET sub-groups, nodes that are connected to social devices of the first SNET group, and the like. The node then generates an appropriate control signal based on the context, as shown in step S804.

In step S806, the control signal and the context-sensitive application are transmitted to the second SNET group, the SNET infrastructure, one associated with the SNET infrastructure, or More than one processing system, device, etc. (via a standardized communication protocol). In step S808, in response to the control signal, the second SNET group, the 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 S810, control of the second SNET group, the SNET infrastructure, one or more processing systems, devices, etc. associated with the SNET infrastructure is terminated or abandoned to the user, processing system, device, some other Entity, some other SNET node, some combination of them, etc.

In some embodiments, some SNET groups may only support one member interaction at a time, while supporting or not supporting the underlying owner members at the same time. Other SNET groups can support many of the multiple member (device/human) access capabilities provided by the SNET group and with features reserved specifically for the owner. The standardization or manufacturer-specific methods of control and authentication tags may take into account the changes described in the SNET group capabilities. Content monitoring and snooping (eg, to protect copyright owners) and similar functionality can also be accomplished by compatibility with standardized protocols.

Referring now to Figure 9, a social network circle/group 900 including social devices 902 (hereinafter "social network group", "social network circle", "SNET circle", "SNET group", etc.) is shown) . In addition to traditional social networking features and services, SNET group 900 and associated social devices 902 in accordance with various embodiments include a number of novel features and attributes, as described more fully below with reference to the accompanying drawings.

Briefly, a member of the SNET group 900 can include a docking social device 902 having resources and resource agents that can access other members of the SNET group 900 and human SNET group members 904. In addition, the SNET Group 900 node can include various types of device services and software (eg, applications) that are attended by members. By way of example, SNET group members may include artificial intelligence agents/social robots 906, SNET security device(s) 908, appliances, vehicles and service providers 910, common or authorized members/functions of other external social device resources 912, and the like. . In addition, specific content and resource accesses of the SNET group 900 can be shared with other SNET 914 members. Includes remote or web-based applications. The access can impose conditions on acceptable analysis and associated data. Likewise, social devices, SNET groups, individuals, etc. may be permitted to be temporary or ad hoc members with or without restricting access.

In the illustrated embodiment, the formation, maintenance, and operation of SNET group 900 is performed by one or more SNET processing systems and software 916. Processing systems may include, but are not limited to, one or more examples of separate SNET processing circuits, one or more examples of distributed SNET processing circuits located on one or more devices, social devices, server devices, network nodes, and the like. It should be noted that "SNET processing circuitry" may include hardware, software, applications, or various combinations thereof, and is configured to support the various functions disclosed herein. In addition, SNET processing system 916 can be included in standalone servers, server farms, cloud-based resources, and/or various devices described below, and includes authentication and security functions 918. In addition, dedicated middleware may also be utilized by SNET in accordance with various embodiments, including standardized middleware (or standardized communication protocols) with associated authentication methods. The interaction and interdependence within the SNET group 900 can include one or more of the adaptive resource management, allocation and arbitration module 920, the social device association/control module 922, and the SNET group member analysis module 924, as described below. description. In addition, SNET processing circuitry & association functions can be integrated into one or more social devices.

The internal and external SNET content/media 926 distribution can be accomplished in a variety of ways in accordance with various embodiments. For example, the 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 can include various user-driven (advertisement) channels, pictures, videos, links, online text, and the like. Access to the content and communication with the social device 902 of the SNET group 900 and remote access to the social device 902 can occur over the Internet backbone 928, cellular communication system, WAN, LAN, and the like.

SNET members in accordance with various embodiments, such as the embodiments disclosed herein, may establish rights and/or privacy settings that control and restrict who or what accessible member profile information, connections, and groups group, And define the required access level. Permissions make it possible for a user to maintain a message private or available based on permissions. For example, the visibility of specified user information can be limited to users/devices in the SNET(s). Alternatively, the specified user information can be made public. Similarly, SNET members can optionally decide to allow other members to access personal information such as name, gender, contact information/email address, and the like.

10 is a functional block diagram illustrating a social network (SNET) infrastructure 1000 and (multiple) (member) social devices 1001, in accordance with various embodiments. Communication between the social networking infrastructure 1000(s) social device 1001 and other SNET members can occur over one or more wired and wireless communication networks 1003. The SNET infrastructure 1000 and the social device(s) 1000 are coupled to the communication network 1003 via the communication interface(s) 1031 and 1011, respectively, and any of the communication interfaces 1031 and 1011 can support individual SNET members, SNET member groups, or SNET members. Category communication.

The SNET infrastructure 1001 of the illustrated embodiment includes a number of functions and resources to support the formation and maintenance of SNETs with social device members. In particular, member report management and processing 1033 receives information from SNET/group/member reporting function 1013 in 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 device user.

In addition, social device 1000 can provide device information 1016, for example, indicating device functionality and social capabilities, device model(s), device composition, software version, attached peripherals and downstream (social) devices, device resources and usage, and the like. For SNET resource management purposes, including dynamic resource allocation and arbitration, device information 1016 related to available resources and current resource usage may be utilized by SNET infrastructure 1001.

In various implementations, the social device 1000 can collect, store, and/or report device status/information 1015/1016 at different times. For example, reporting may be required after contacting or docking with the SNET based on the periodicity and/or during operational commitments within and between other SNET resources and devices (including upstream and downstream devices).

Referring again to the 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, which allows SNET-associated software components to communicate with one another; access control management and security Sex 1037 for maintaining SNET and ancillary data/resource integrity; and (web) server service 1038. The social networking infrastructure 1001 also includes: other group application services 1005 corresponding to the above; and additional services, such as described herein. In an exemplary embodiment, SNET infrastructure 1001 may determine (eg, by means of device information 1016) the type and nature of social device 1000 that wishes to participate in SNET. If necessary, the functionality in the SNET infrastructure 1001 can then direct or trigger the installation of the appropriate application software and underlying drivers in the social device 1000. The operations may be performed with minimal participation 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 (eg, including the social resources described in conjunction with FIGS. 11 and 13 and device status/information 1015/1016) as well as functions and resources to support participation in social interactions. network. More specifically, the SNET, SNET, and/or member control functions 1017 can include a slave function 1019, a master function 1020, and various combinations thereof. For example, slave function 1019 includes device (re)configuration, directed resource allocation, management resource arbitration, bridging operations, and the like. The primary function 1020 enables the social device 1000 to establish, manage, and terminate various interactions between nodes or groups of nodes in the social network, including interactions involving the social device 1000 itself.

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

It should be noted that many of the functional blocks of the embodiment shown in Figure 10 may be integrated in whole or in part in one or more (application specific) integrated circuit devices. E.g, The integrated circuit device can include a member reporting module to provide member reporting functions (including device status and device characteristic communication), device control capabilities, master/slave functions, security, and access control modules. The integrated circuit device may also include on-board processing capabilities and/or interfaces to processor devices. Alternatively, the above functions may be integrated in whole or in part in the operating system and/or in the software that loads the operating system kernel.

Referring now to FIG. 11, a schematic block diagram is shown for a social device 1101 that is 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 to enable it to operate in a social device "hierarchy" (including social (S) devices, social "parent" (SP) devices, 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. The social child device can configure the intrinsic social capabilities or gain access to the capabilities from or through the associated parent device. In addition, a human SNET member may have an associated social sub-device or may be served by a social parent device via a user I/O interface (1123).

The social device 1101 according to various embodiments and applications may also be used simultaneously or selectively as a social device, SP device, SC device, or even a "grandmother" device that supports (eg, in a multi-hop environment) a SNET group The parent device in the group. The dynamic and static hierarchies associated between the SP and the SC device can be established selectively, automatically or automatically. In addition, the social device 1101 can take many forms, including but not limited to smart phones, personal computers, servers, tablet devices, access points, gateways, network switches/hubs, bridging devices, set-top boxes, or socially enabled Other devices.

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, downstream social peering and/or sub-communication interface circuitry 1113 enables coupling with social sub-device 1115, social peer device 1117, and/or social parent system (device) 1119. Social resources of upstream and downstream devices can be via social devices 1101 access each other.

The social device 1101 of the present embodiment includes a social resource 1103 that is managed by the social resource management module 1105 along with external SNET resources and that can access at least one other SNET group member. Specific social resources 1103 may include user I/O interface 1123, general purpose and special purpose hardware processing circuitry 1124, peripheral circuitry and components 1125 (possibly or possibly without social capabilities), communication bandwidth and credit determination functionality 1126, handover/bridging functionality 1127, application software and services 1128, remote social resources 1129 of the SNET group, external social resources 1131 controlled by the social device 1101, and the like. For example, external social resources 1131 may include one or more external media/digital media libraries or content from cable, satellite, and/or terrestrial television systems.

Among other functions, the social resource management module 1105 includes access, assignment, arbitration, and scheduling functions 1121 and functions 1122 for establishing, restoring, and abandoning control processing operations, including operations involving access to the social resources 1103. It should be noted that the pairing social resource management functions may exist in the SNET infrastructure 1109 and/or other SNET nodes.

In an exemplary embodiment in which social device 1101 includes a handover 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 requesting according to the access view or according to the allocation and arbitration function, and selectively terminating when excessive bandwidth/resources are consumed or requested.

12 is a schematic block diagram illustrating social resource access to SNET group 1206, in accordance with various embodiments. In some embodiments, a social network group ("SNET Group") member controls different access levels and associated device profiles and capabilities for two pieces of personal information (which may be included in the user profile). The access rights allow members to establish selective, restrictive, and/or hierarchical access rights and views - for all other members of the social group and for non-members - all or some of the member social devices and resources. In addition, members can establish personal information and associated social devices Selective or hierarchical access to configuration files and other resources.

In the illustrated embodiment, the SNET group member 1214/1216 or device (or optionally, no associated entity) accesses the social device/group resource 1210 associated with the SNET group 1206 via the resource management node 1200. The resource management node 1200 includes an access right 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 views 1202 control different access levels and access visibility for member personal information, device information, data, processing and storage capabilities, and other social resources. For example, access rights 1201 and access views 1202 may be predefined based on SNET groups, based on common member devices, or based on member device-device interactions. The predefined can be dynamically customized as needed or based on relationship changes. Access rights 1201 can also be extended to support temporary interaction with guest members or visitor devices. For example, an access member of a smart phone may be allowed to receive/provide media to a social device resident in a "family group."

In some embodiments, the SNET group 1206 member can adjust and modify the access rights 1201 based on information-by-information, device-by-device, member-by-member, and the like. By accessing view 1202, members can also present themselves in various ways depending on the context, location, or based on considerations of use. For example, a member icon/avatar may present different characteristics or abilities related to the context, including work, home, or social settings. The allocation of social resources and, if necessary, dynamic reallocation are performed by dynamic (re)allocation function 1203 and arbitration function 1204. Social resource access may be processed in advance on secure access/authentication performed by security function 1205.

In addition to the social device/group resource 1210, for example, the SNET group 1206 can include the SNET server 1212 and one or more members 1214 and affiliate social devices, services, applications, files, web pages, connections, and other social resources. It should be understood that member 1214 (which may include, but is 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 It can be incorporated into the SNET server 1212 or other SNET social devices, or managed by the SNET bearer infrastructure in an independent manner, in a distributed manner, and the like. In addition, SNET server 1212 can 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 can occur in a variety of 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 that graphically indicates available resources, voice controls, gesture commands, and the like. Access to the SNET group 1206 can also be managed by the proxy server 1220. The proxy server 1220 acts as an intermediary for the proxy client 1222 to access requests - including social devices that connect to the proxy server 1220 via an internet or other IP-based network - seeking to communicate with the SNET group 1206. The social device 1224 affiliated with the SNET 1213 may have the ability to interact directly with the SNET group 1206. It should be noted that human member 1216, proxy server 1220, and social device 1224 can operate independently of the SNET group/subgroup. Further, proxy server 1220 can be a distributed or cloud-based entity, or a member of SNET group/sub-group 1213 or SNET group 1206 (or included in a member).

FIG. 13 is a schematic block diagram of a social device/server 1300 utilizing a communication and control protocol 1302 that enables various SNET resources and control operations in accordance with various embodiments. In the illustrated embodiment, the communication and control protocol 1302 includes protocol composition 1304, SNET resource (automatic) control feature 1306, device type/function specific control 1308, security and authentication features 1310, SNET docking/member control 1312, and SNET. Transport/network layer 1314. Various packet and packaging techniques can 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 that enables integration with a central SNET management node, SNET infrastructure, one or more processing systems, SNET members, and other compatible devices (including possible Social devices that do not fully support the SNET group communication protocol), some combination of them, etc. Communication is possible. The shim layer or client driver 1316 can be installed via a SNET node or local storage, or downloaded from a manufacturer's website or cloud-based resources. After the social device/server 1300 is powered on or activated, the installation may be automated or directed by other SNET nodes.

SNET resource management and access using communication and control protocol 1302 can be performed through a SNET group or a central management node of the SNET hosting infrastructure. The central management node may include integrated artificial intelligence and/or present itself through "characters" or "avatars." In addition, distributed and delegated control mechanisms (including ad hoc or remote operations across one or more SNETs) allow one member to interact with their own or another member social device via a SNET or SNET defined path.

In some embodiments, the standardized version of the communication and control protocol 1302 - referred to herein as "SNET 1.0" standard - is used to facilitate the SNET interaction (and may not require a compatible social device in defining device type characteristics) In the shim layer). Various control operations according to the SNET 1.0 standard may include automatic and ad hoc SNET group associations and support functions such as automatic SNET resource offerings, automatic device registration and composition, upgrade and update maintenance, device-device communication session management, wear/cute/ Encapsulation capabilities, proxy services, social resource allocation, and more. For example, through the docking of affiliated social devices in a SNET group, members may desire to access and control their own remote docking devices, as well as other members' remote docking devices, either directly or via another user device. In some embodiments, the interaction can be facilitated by a SNET 1.0 compliant method.

For example, SNET 1.0 compliant devices can be designated as "SNET 1.0 Certified" and provide system-on-a-chip ("SoC")/hardware and software support specific to a particular device group. By way of example, a SNET 1.0 certified NAS may have storage related, defined control capabilities, including default access level definitions, security, and DRM features as described herein. For example, the control capability is different from the SNET 1.0 certified STB (possibly with multiple tuners/deliveries for transmitting according to the setup program for the device itself) Streaming video with some tuner/delivery). The social device can be configured to delegate control to the SNET (1.0) group/server for manual application or through factory level settings and security for further application, such as described below.

14 illustrates various implementations of social device membership and access in a social network group/subgroup in accordance with various embodiments of the present invention. In some embodiments, members of the SNET group 1410 can be expanded to include public and private social devices and devices. For example, in a SNET group 1410 that includes human members 1406/1408, each human member may have a respective personal SNET subgroup 1400 that can independently or aggregate the associated or docked social devices 1406/1408 participating in the SNET group 1410 (a) ) / 1400 (b). The SNET subgroup may be accessed locally or remotely by human members 1406/1408 and/or other SNET group/subgroup members through various measures, such as clicking on an icon or tag associated with a human member/personal subgroup.

Although the 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 subs Groups and the like, each may include various combinations of social devices 1402/1404. Moreover, the SNET processing circuitry and software 1412 of the illustrated embodiment manages the formation and operation of the SNET group 1410. SNET processing circuitry and software 1412 can be incorporated into standalone servers, social devices, and/or cloud-based resources. The SNET group 1410 can be permanent or limited in duration and includes ad hoc and/or static associations. In addition, SNET groups/subgroups can be permanent or ad hoc/temporary.

The social device 1402/1404 can be broadly classified into: (i) a social device 1402 that includes a user or SNET group interface sufficient to provide (support) meaningful (user) input (eg, SNET settings and management) to the SNET interaction; (ii) The social device 1404 supports minimal user input related to SNET interaction or does not support user input; some combination thereof, and the like. More specifically and without limitation, the first category may include computers, tablet devices, IPTV, IPTV set-top boxes, smart phones, servers, notebook computers, cloud books, network connection storage devices, game consoles, media players. /source, communication section Points (access points, routers, switches, gateways, etc.), user interface devices, power line communication (PLC) devices, etc. The social device can receive user input for SNET setup and management. The second category may include, but is not limited to, printers, projectors, cameras and video cameras, scanners, speakers, earphones, smoke detectors, alarm systems, cameras, mice, and the like. In general, the dockable social device includes any electronic device that is operable to couple or dock in a SNET group/subgroup via a wired or wireless path that participates in the SNET member. Among them, the docked "social" device can participate in the SNET circle/sub-circle.

It should be understood that by docking social devices, SNET group 1410 members may have full or partial remote control and interaction via an authorized member SNET account. For example, a family member 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 docking and accessing social devices are described more fully below (e.g., in conjunction with Figures 15 and 16).

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

In one embodiment, SNET gateway 1506 or SNET group gateway 1508 acts as a proxy for social device 1500. The proxy function in the SNET gateway 1506 can be provided by a software application or a computer system (server), and the software application or computer system (server) is used as a client seeking resources from other servers or gateways (such as SNET gateway 1508). The intermediary (including the connected social device) requested. The resources may include files, services, web pages, connections, analysis information, and other available social device resources and other group resources 1518.

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

The members of the SNET group/subgroup 1502 are established by the SNET processing circuitry and the docking module 1510 of the software 1512, which can support one or more device discovery and composition protocols, including standardized protocols. The local or cloud-based registrar 1514 can be used to provide authentication when the group membership is restricted. 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, the social device can (using a text data format) (Extensible Markup Language (XML)) to broadcast profile data (such as XML) to the local domain.

16 is a schematic block diagram of an embodiment of a social device(s) 1600 including full resource access and allocation management functions in accordance with various embodiments of the present invention. The social device 1600 can operate as a SNET member, a guest member, and/or an authorized visitor. Access and distribution of social resources 1602 of social device 1600 through (predefined or user defined) access and distribution management functions 1604 (whose operations are applicable between SNET member nodes and SNET member nodes) and between social resources 1602 and Control between non-associative entities. Moreover, the access and distribution management functions 1604 can be distributed between one or more social devices/SNET hosting infrastructures.

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 operations of the functions are described in conjunction with various other figures herein. For example, an access request service to social resource 1602 can be performed via a browser and/or downloaded or pre-installed application 1614. In some embodiments, in authentication or security After the full operation 1616, the social resource 1602 is accessed. Moreover, various functional blocks of social device 1600 can be incorporated into one or more integrated circuit devices that can be dedicated to supporting a primary user and/or shared access operations.

17 is a schematic block diagram of an embodiment of a social device 1700 that includes an integrated functionality operable to support social network groups/sub-group members and communications, 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 composition of the social device 1700, communication with the SNET can be one-way or two-way/interactive, and utilizes a dedicated or standardized communication protocol. For example, communications may include device configuration information, user and SNET group configuration information, control signals, media content, interaction with hosted service data, user data, relay information, and the like.

The 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, etc.) . More specifically, for example, processing circuit 1704 can include a software management application 1712 that includes: docking logic 1714 (including support device discovery and composition protocols, such as described below), communication protocol control 1716, resource management 1718, and One or more of the security/authentication 1720 functions.

The social device 1700 can also utilize configuration information and other resources, which can take many forms and remain in the static or dynamic storage 1724. The configuration information enables the social device and/or user 1701 to present their own images and their capabilities to other NSET members. In particular, device/group configuration information and other resources 1706 and user configuration information 1708 can be utilized in various ways to facilitate various social interactions in accordance with various embodiments. Depending on the capabilities and requirements of a particular device (and other members of the SNET), the device or user profile can be static or dynamic.

In some embodiments, the social device 1700 can be via the user interface circuit 1710. Interact with user(s) 1701. For example, user input to social device 1700 can include data input via a keyboard, touch screen, remote control device, game controller, device control buttons, voice or gesture commands, storage devices, and the like. Authorized access or control of the social device 1700 can be facilitated by a unique biometric, password, identity based identification, trust authorization or file (such as a driver's license or passport) and similar authentication means.

The social device 1700 can perform a basic device (core or bottom layer) function 1722. Alternatively, the social device may be primarily used as a social networking interface or communication device, or may be programmed to perform specific functions within a SNET group/sub-group.

As used herein, the terms "substantially" and "about" provide industry-accepted tolerances for their corresponding terms and/or inter-item relativity. The industry-recognized tolerances range from one percent to fifty percent and correspond to, but are not limited to, component values, integrated circuit process variations, temperature deviations, number of lifts, and/or thermal noise. The relative range of projects varies from a few percent to a large difference. Also as used herein, the terms "operating to", "coupled to", and/or "coupled" include inter-project direct coupling and/or inter-project via intermediate items (eg, items include, but are not limited to, components) Indirect coupling of components, circuits, and/or modules, wherein for indirect coupling, the intermediate item does not modify the information of the signal, but its current level, voltage level, and/or power level can be adjusted. Also as used herein, inferred coupling (ie, one element is inferred to the other element by inference) includes direct and indirect coupling between two items in the same manner as "coupled to". Also as used herein, the term "operating to" or "operating to" indicates that the item includes one or more of a power connection, input(s), output(s), etc., when enabled, one or more are performed Its corresponding function, and also includes inferred coupling to one or more other items. Also as used herein, the term "associated with" includes the direct and/or indirect coupling of a single item and/or an item embedded within another item. As used herein, the term "suitable for comparison" indicates a comparison of two or more items, signals, etc., to provide the desired relationship. E.g, When the desired relationship is that signal 1 has a greater magnitude than signal 2, a suitable comparison can be achieved when signal 1 amplitude is greater than signal 2 amplitude or when signal 2 amplitude is less than signal 1 amplitude.

Also as used herein, the terms "processing module," "module," "processing circuit," and/or "processing unit" may be a single processing device or multiple processing devices. The processing device can be a microprocessor, a microcontroller, a digital signal processor, a microcomputer, a central processing unit, a field programmable gate array, a programmable logic device, a state machine, a logic circuit, an analog circuit, a digital circuit, and/or Any device that manipulates signals (analog and/or digital) based on hard coded and/or operational instructions. The processing module, module, processing circuit, and/or processing unit can have associated memory and/or integrated memory elements, which can be a single memory device, multiple memory devices, and/or The processing module, the module, the processing circuit, and/or the embedded circuit of the processing unit. The memory device can be read only memory (ROM), random access memory (RAM), volatile memory, nonvolatile memory, static memory, dynamic memory, flash memory, cache memory, and/or storing digital information. Any device. Please note that if the processing module, module, processing circuit, and/or processing unit includes more than one processing device, the processing device can be centrally located (eg, directly coupled via a wired and/or wireless bus structure) or Distributed positioning (eg, cloud computing indirectly coupled via a LAN path and/or a wide area network). Please also note that if the processing module, module, processing circuit, and/or processing unit implements one or more functions via a state machine, analog circuit, digital circuit, and/or logic circuit, then memory corresponding to the operational command is stored And/or memory elements can be embedded within or external to circuitry including state machines, analog circuits, digital circuits, and/or logic circuits. Please also note that the memory component can store hardcoded and/or operational instructions corresponding to at least some of the steps and/or functions shown in one or more of the figures, as well as processing modules, modules, processing circuits, and/or processing units. The hard coded and/or operational instructions are executed. The memory device or memory component can be included in an article of manufacture.

The invention has been described above by means of method steps illustrating its specific function and relationship performance. For convenience of description, the boundaries and order of these functional blocks and method steps have been arbitrarily defined herein. Alternate boundaries and sequences can be defined as long as the specific functions and relationships are performed accordingly. Any alternative boundaries or sequences are within the scope and spirit of the invention. Moreover, the boundaries of these functional blocks have been arbitrarily defined for ease of description. Alternate boundaries can be defined as long as certain important functions are performed accordingly. Similarly, flowchart blocks may have been arbitrarily defined herein to illustrate certain important functions. Within the scope of use, the flow block boundaries and sequences can be additionally defined and still perform some important functions. Alternative definitions of the functional blocks, as well as the flowchart blocks and sequences, are within the scope and spirit of the invention. Those of ordinary skill in the art will also appreciate that the functional blocks and other illustrative blocks, modules, and components herein can be implemented as discrete components, application specific integrated circuits, processors executing the corresponding software, or the like, or any combination thereof.

The invention may also have been described, at least in part, in one or more embodiments. The embodiments of the invention are used herein to illustrate the invention, aspects of the invention, the features of the invention, the inventive concepts and/or examples of the invention. Physical implementations of devices, articles, machines, and/or methods embodying the invention may include one or more of the aspects, features, concepts, examples, etc. described with reference to the embodiments discussed herein. In addition, the embodiments may include the same or similarly named functions, steps, modules, etc., which may use the same or different reference numerals, and the functions, steps, modules, etc. may be the same or similar functions, Steps, modules, etc. or different functions, steps, modules, etc.

The signals to any of the elements, slave elements, and/or elements of any of the figures presented herein may be analog or digital, time continuous or time discrete, and single ended or differential unless otherwise specifically stated. 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 specific architectures are described herein, one of ordinary skill in the art will appreciate that the same can be implemented. It is an architecture that uses one or more data buses, direct connections between components, and/or indirect coupling between other components not explicitly shown.

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

Although specific combinations of different functions and features of the present invention have been explicitly described herein, other combinations of these features and functions are equally feasible. The invention is not limited to the specific examples disclosed herein, and such other combinations are explicitly included.

1000‧‧‧Social Network (SNET) Infrastructure

1001‧‧‧(multiple) social devices

1003‧‧‧(one or more wired and wireless) communication networks

1005‧‧‧Other group application services

1011, 1031‧ ‧ (multiple) (group & member) communication interface

1013‧‧‧(SNET/Group/Member Report) function

1015‧‧‧ Status (including logic, address, activities, resources)

1016‧‧‧Device information (including function, capability, model, composition)

1017‧‧‧SNET, SNET group, member control functions (including resource management)

1018‧‧‧Social device resources

1019‧‧‧From function

1020‧‧‧ main function

1021‧‧‧Social API

1023‧‧ social applications and services

1025‧‧‧ (browser-based interaction) capabilities

1027‧‧‧Access, control and security

1033‧‧‧Member report management and processing

1034‧‧‧Member information (capture) collection and storage management

1035‧‧‧SNET Application Programming Interface (SNET API)

1037‧‧‧Access control management and security

1038‧‧‧(web) server service

Claims (8)

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 the first social network group and the second social network group Creation of a group, the first social network group having a first group capability, the second social network group having a member including the first human member and the second human member; the processing The system is operable to also support the first docking method, the first docking method comprising: associating the first social network group with the second social network group to Capabilities are provided to members of the second social network group; and the processing system is operative to transmit data to members of the second social network group to support presentation of the first group of capabilities . The social networking system of claim 1, wherein the processing system is operable to transmit data to a member of the second social network group to support representation of the first group of capabilities Presentation of a map that enables the member to access the first group of capabilities. The social networking system of claim 2, wherein: the first social network group comprises a first plurality of social network groups; and the first group capability comprises the first plurality The ability of at least one of the social network groups; and the representation includes a view of the first group capabilities that are unrelated to the views of the first plurality of social network groups. The social networking system of claim 1, wherein the processing system is operable to transmit data to a member of the second social network group to support the first group capability a second representation that the presentation is presented to the first member of the second social network group and the first group capability is presented to at least the second member of the second social network group. First The representation is different from the second representation. An apparatus for supporting a user interacting with a social network, the apparatus comprising: an interface configured to be communicatively coupled to a social network; and processing circuitry interoperable with the interface to: interact with a social network group To connect a first social network group to a second social network group; dock the device to the first social network group, and access the second social network group Ability. The device of claim 5, wherein the processing circuit is interoperable with the interface to: display a second social network associated with the first social network group on a user interface a representation of the group, the representation including a representation of capabilities of the second social network group unrelated to at least one of the plurality of social network groups; and accessing the first based on user input The ability of the second social network group to determine user input based on user interaction with the representation via the user interface. A method performed by a social networking system, the method comprising: maintaining a first social network group, providing a first group service through the first social network group; maintaining a second social network group To support the first human member and the second human member via the first device and the second device, respectively; and the group received by accessing the first group service by both the first device and the second device - Responding to the group docking request, the group-group docking request originating from interaction with the first device; wherein the group-group docking request is to cause the first social network group to The second social network group associated request to provide at least some of the first group service to at least one of the first device and the second device. A method performed by a social networking system as described in claim 7, comprising: receiving, by the representation pair, by accessing the first group service by both the first device and the second device Responding to the group-group docking request, the first group service is provided by at least one of the plurality of social network groups, and the representation includes at least one of the plurality of social network groups An irrelevant representation of the first group of services.