TW201325300A - Management of social device interaction with social network infrastructure - Google Patents

Abstract

A social networking system enables interaction between various devices, infrastructures, and the like based upon monitoring, analysis, processing, and the like of information received from devices. Some or all of an infrastructure can monitor information output from one or more socially controllable devices. Upon receiving a trigger or determining a trigger event processing of received data, some or all of the infrastructure, supporting processing systems, and the like can take one or more various responsive actions, including contacting a user associated with the social devices, contacting a third party that is not a member of the social network group, contacting a service that is a member of the group, and controlling or enabling others to control aspects of devices docked with the user's group.; A user can manage various levels of authorized interaction between associated devices and a docked social group.

Description

Management of interactions between social devices and social networking infrastructure

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 grown. Existing social networking sites include Facebook, Google+, Twitter, MySpace, YouTube, LinkedIn, Flicker, Jaiku, MYUBO, Bebo, and more. Such social network (SNET) addresses are typically network-based and organize these social network addresses around user profiles and/or collections of content available to network members. Members of such a social network include individuals or groups of individuals, usually represented by archive pages and determined by social networking services, allowing them to interact.

In a large number of well-known social networks, especially those that focus on archives, activity centers on web pages or social spaces that allow members to view files can transmit and share activities, interests, opinions, status updates, audio/via via the contact network. Video content and more. Social networking services also allow members to track certain actions of other members of the social network, collaborate, share and connect with current friends, old friends, and colleagues, and establish new connections with other members.

Human members typically connect to social networking services through existing web-based platforms through computing devices, tablets or smart phones. Members typically share a common connection, social status, or geographic or cultural connection with their respective contacts. Smart phones and game-based mobile social networking services are examples of rapidly growing regions.

In so-called "cloud" computing, computing tasks are performed on remote computers/servers that are typically accessed over a network connection. One advantage of cloud computing is that the relative processing and storage capacity required by the user device can be reduced (e.g., the cloud computer can load the web page accessed by the tablet device and simply pass the required message back to the tablet). Therefore, in recent years, the amount of content and application software moving from local or on-site storage to cloud-based data storage and management is increasing. This software function/service and content is usually available on demand through a (virtualized) network infrastructure.

Typically, visitors entering a location, network, etc. are allowed to access a location, commercial network, and possibly access to a social networking environment, cloud application, or cloud media content. In practice, the duration and scope of such authorizations are generally not limited. In addition, social groups have various mechanisms for serving with another member, member device, or member device (eg, including phone numbers, IP or other routing addresses, VoIP/video call processing, microblogging processing, other SNET processing, blogs) , web address, email address, etc.) to establish contact. When the above changes, it is difficult to transmit the message to all other members and member devices.

The reason is that the present inventors have felt that the above problems can be improved, and that the present invention has been deliberately studied and used in conjunction with the theory, and a present invention which is reasonable in design and effective in improving the above problems has been proposed.

(1) A social networking system that supports interaction with a third party monitoring service and at least a first human member, the social networking system including: a management service that supports creation of a first social networking group, the management service support a pairing process and a second docking process, the first docking process including associating the first social networking group with a first device of the first human member, the second docking process including the first a social networking group associated with the third party monitoring service; and the management service supports a social path via the first social networking group, the third party monitoring service being receivable from the first device Information, and the monitoring service selectively triggers a support function in response to the received data, the support function including the third party monitoring service via the social path and the The interaction of at least a first portion of a device.

(2) The social networking system of (1), the support function comprising the third party monitoring service controlling the first portion of the first device via the social path.

(3) The social networking system of (1), wherein the support function comprises the third party monitoring service accessing a status message from the first portion of the first device via the social path.

(4) The social networking system according to (3), wherein the support function comprises a third party device that provides at least some status messages to a third party.

(5) The social networking system of (1), wherein the social path is a direct peer-to-peer path between the third party monitoring service and the first device.

(6) The social networking system of (1), wherein the monitoring service selectively triggers a support function in response to determining that the received data is associated with a trigger threshold.

(7) A monitoring system supporting a plurality of clients, the monitoring system comprising: a first system, interacting with a social network in a first docking process to join at least a first social network group, the first social network The set of pathways includes a first human member and a first social device member of the first human member, the first human member being a first one of the plurality of clients; the first system via the first social The first social path provided by the network group receives communication from the first social device member and evaluates it; and the first system responds to the evaluation by selectively triggering a support function, the support function including An interaction with at least a first portion of the first social device member.

(8) The monitoring system of (7), wherein the support function comprises accessing, by the first system, a status message from at least a first portion of the first social device member.

(9) The monitoring system of (7), wherein the support function comprises control of at least a first portion of the first social device member by the first system.

(10) The monitoring system according to (9), wherein The first social device includes an audiovisual interface; and the support function includes control of the audiovisual interface by the first system.

(11) The monitoring system of (8), wherein the support function further comprises providing a status message to at least one of the plurality of customers.

(12) The monitoring system of (7), the first docking process comprising verifying a secure interaction between the first system and the first social device member via the first social path.

(13) The monitoring system of (8), wherein the first system responds to the evaluation by selectively triggering a support function, the support function comprising interacting with a third party.

(14) The monitoring system of (13), the interacting with the third party comprises providing communication received by the first system from the first social device member to a third party device supporting the third party.

(15) A device for supporting a member of a social networking system, the device comprising: an interface communicatively coupled to the social networking system; and processing circuitry operably interoperable with the interface to: at the first docking Interacting with the social networking system to interface the device with a first social networking group, the first social networking group comprising a third party monitoring service member; and, socially provided via the first social networking group A path to transmit a status message associated with the first portion of the device to the third party monitoring service member.

(16) The apparatus of (15), the processing circuit being operably interoperable with the interface to provide the third party monitoring service member with control of the first portion of the device.

(17) The device of (15), the first portion of the device comprising a sensor capable of generating data based on an environment proximate to the device.

(18) The apparatus of (17), the processing circuit being operative to work with the interface and the sensor to: evaluate data generated by the sensor; responsive to the evaluating, via the first The social path provided by the social networking group will A status message associated with the sensor is communicated to the third party monitoring service member.

(19) The apparatus of (17), the processing circuit capable of operating in cooperation with the interface and the sensor to transmit a status message associated with the sensor to a member of the first social networking group In response to a signal from the third party monitoring service member.

(20) The apparatus of (15), the first docking process comprising verifying a secure interaction between the device and the third party monitoring system via the social path.

100‧‧‧SNET grouping hierarchy

101‧‧‧Serving SNET infrastructure

103, 105, 107‧‧‧ Client SNET Infrastructure

106‧‧‧Docking specifications

111‧‧‧User device (service support social user device)

113‧‧‧Application (social service application)

115‧‧‧SNET (SSUD) group

117‧‧‧ (mixed SA/SSUD) SNET group

119‧‧‧SNET (SA) group

125‧‧‧Docking treatment (selection & docking process)

131, 141, 151‧‧‧ Client social devices (client social user devices)

135, 145, 155‧‧‧ Client SNET Group

200‧‧‧SNET grouping hierarchy

201‧‧‧Global Social Service Infrastructure

203‧‧‧ (local/regional social services) infrastructure

205‧‧‧ representative map

211‧‧‧ Social service support user device (device)

213‧‧‧Social Service App

215, 225‧‧‧SNET (SSUD) group

217, 227‧‧ (mixed SA/SSUD) SNET group

219, 229‧‧‧SNET (SA) group

221‧‧‧Social service support user device (device)

223‧‧‧Social Services (Server/Cloud) application

231‧‧‧Social Service Support (L/R&G) User Equipment (Equipment)

233‧‧‧Social Services (Server/Cloud) (L/R&G) application

237‧‧‧ (combined local/regional & global) SNET group

301‧‧‧ (combined social security services) infrastructure

313‧‧‧ Law enforcement services (social law enforcement officers)

315‧‧‧Social Police Terminal/Radio

321‧‧‧Monitoring Service (Social Monitoring & Analysis Service Application)

324‧‧‧Docking specifications

325‧‧‧Social third-party device interface & control application

331‧‧ (Secure Service) SNET Group

333‧‧‧(Neighbor & Family View)

350‧‧ (first neighbourhood) infrastructure

351‧‧‧ (first social user I/F device) device

353‧‧‧ (socially controllable audiovisual I/F) interface

355‧‧‧ (user input I/F) interface

357‧‧‧ (first social security system) device

360‧‧‧ (Nth Neighbourhood) infrastructure

370‧‧‧ (family member) infrastructure

371‧‧‧ (Social Monitoring & Analysis Service) application

381‧‧‧ Third party installation

391‧‧‧ (system group view of the first neighbourhood)

401‧‧‧ (combined social medical/health services) infrastructure

415‧‧ (social fire terminal/radio) fire service

417‧‧‧ (social ambulance staff) ambulance service

419‧‧ (social medical service device) medical services

421‧‧‧ (Social Monitoring & Analysis Service) application

424‧‧‧Docking specifications

431‧‧ Medical Services Section

433‧‧‧(Neighbor & Family View)

450‧‧‧ (first neighbourhood) infrastructure

451‧‧‧ (first social user I/F device) device

453‧‧‧ (socially controllable audiovisual I/F) interface

455‧‧‧ (user input I/F) interface

459‧‧‧ (first social medical system) device

460‧‧‧ (Nth Neighbourhood) infrastructure

470‧‧‧ (family member) infrastructure

471‧‧‧ (Social Monitoring & Analysis Service) application

491‧‧‧ (system group view of the first neighbourhood)

501‧‧‧ (combined) social service infrastructure

521‧‧‧ (Social Monitoring & Analysis Service) application

531‧‧‧Self-organized SNET (Services) Group

533‧‧‧(Friend & Family View) Chart

550‧‧‧ (first) user system

551‧‧‧ (first social user I/F device) interface device

553‧‧‧ (socially controllable audiovisual I/F) interface

555‧‧‧ (user input I/F) interface

557‧‧‧ (first device) camera

560‧‧ (Nth User) System

570‧‧‧ (family member) system

573‧‧‧Docking specifications

591‧‧‧ (first user's system group view) diagram

600‧‧‧Family environment

603‧‧‧ (social security device group) SNET group

606‧‧‧(family member device) social device

608‧‧‧ (personal family account) account

610‧‧‧Social security device

620‧‧‧Social security device

630‧‧‧ (extra) social devices

650‧‧‧SNET

660‧‧‧Security company

670‧‧‧Emergency Service Provider

680‧‧‧Insurance company

690‧‧‧ repair service

692‧‧‧Automotive environment

694‧‧‧Social car installation

700‧‧‧(Electrical ring/sub-circle) electrical group/subgroup

702‧‧‧ social appliances

704‧‧‧SNET processing circuit/software

706‧‧‧ family members

708‧‧ (personal) (family) account

710‧‧‧ (extra) social devices

712‧‧‧ Cloud

800‧‧‧Vehicle SNET Group/Subgroup

802, 804‧‧ vehicles

806‧‧‧ Passenger SNET Subgroup

808‧‧‧ entertainment devices

810‧‧‧Communication device

812‧‧‧ computing device

814‧‧‧ social devices

816‧‧‧ payment processing

818‧‧‧Insurance Company

820‧‧‧Emergency services/devices

822‧‧‧Vehicle manufacturers

824‧‧‧ (location-based) content provider

826‧‧‧Cellular Network/WAN/Mobile Hotspot

902~918‧‧‧ box

1002~1026‧‧‧ box

1152~1168‧‧‧ box

1272~1290‧‧‧ box

1300‧‧‧Social Network Circle/Group

1302‧‧ Social devices (available resources)

1304‧‧‧SNET group human members

1306‧‧‧Artificial Intelligence Agent/Social Robot

1308‧‧‧SNET Security Device

1310‧‧‧Electrical, vehicle and service providers

1312‧‧‧SNET Group (External Social Device Resources)

1314‧‧‧Additional SNET

1316‧‧‧SNET processing system and software

1318‧‧ (certification and security) certification and security features

1320‧‧‧Resource Management, Allocation and Arbitration Module

1322‧‧‧Social device association/control module

1324‧‧‧SNET Group Member (Data) Module

1326‧‧‧SNET Content/Media

1328‧‧‧ Internet backbone

1400‧‧ social network (SNET) infrastructure

1401‧‧‧ (one of several social devices) social devices

1403‧‧‧(one or more) wired or wireless communication networks

1405‧‧‧Other group application services

1413‧‧‧SNET/group/member reporting function

1415‧‧‧Status Information

1416‧‧‧Device Information

1417‧‧‧ (SNET, group, management control) SNET, SNET and/or member control functions

1419‧‧‧Subordinate function

1420‧‧‧Main function

1421‧‧‧Social API

1423‧‧‧(subsidiary applications/services) applications and services

1425‧‧‧Browser-based interactive features

1427‧‧‧ (Access Control & Security) Security

1411, 1431‧‧‧ communication interface

1433‧‧‧Member report management and processing

1434‧‧‧(Member) Message Acquisition and Storage Management

1435‧‧‧SNET Application Programming Interface (API)

1437‧‧‧Access Control Management and Security

1438‧‧‧ (network) server service

1501‧‧ (social, social, or social) social devices

1503‧‧‧Social resources

1505‧‧‧Social Resource Management Module

1507‧‧‧Upstream social communication interface circuit

1509‧‧‧SNET infrastructure

1511‧‧‧Social Parent System

1513‧‧‧Down social peer-to-peer and/or sub-communication interface circuits

1515‧‧‧social sub-device

1517‧‧‧Social peering device

1519‧‧‧Social parent system (device)

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

1522‧‧‧Re-acquisition and abandonment of control processing operations

1523‧‧‧User I/O Interface

1524‧‧‧General purpose and dedicated hardware processing circuits

1525‧‧‧ peripheral circuits and components

1526‧‧‧Communication bandwidth and credit determination

1527‧‧‧Switch/Bridge Function

1528‧‧‧Application software and services

1529‧‧‧SNET group's remote social resources

1531‧‧‧External social resources

1600‧‧‧ resource management node

1601‧‧‧Access rights

1602‧‧‧Access view

1603‧‧‧Dynamic (re)allocation function

1604‧‧‧ Arbitration function

1605‧‧‧(safety) security features

1606‧‧‧SNET Group

1610‧‧‧Social device/group resources

1612‧‧‧SNET server

1613‧‧‧SNET group/subgroup

1614, 1616‧‧‧ human members

1618‧‧ User Interface (UI)

1620‧‧‧Proxy server

1622‧‧‧Proxy client

1624‧‧‧ social devices

1626‧‧‧Internet backbone

1700‧‧‧(SNET) social device/server

1702‧‧‧Communication and Control Protocol

1704‧‧‧ Protocol configuration

1706‧‧‧SNET resources (automatic) control

1708‧‧‧Device type/function specific control

1710‧‧‧Safety and authentication functions

1712‧‧‧SNET docking/membership (qualification) control

1714‧‧‧SNET transport/network layer

1716‧‧‧Client Drive/Intermediary

1800(a)/1800(b)‧‧‧SNET subgroup

1802/1804‧‧‧ social devices

1806/1808‧‧‧ human members

1810‧‧‧ (social network) SNET group

1812‧‧‧SNET processing circuits and software

1900‧‧‧ social devices

1902‧‧‧(Secure SNET circle/sub-circle) SNET group/subgroup

1904‧‧‧(second) SNET group/circle

1906, 1908‧‧‧SNET gateway

1910‧‧‧ (dock and access) docking module

1912‧‧‧SNET processing circuits and software

1914‧‧‧ (cloud-based) registrar

1916‧‧‧Administrator or directory service

1918‧‧‧ (Social Device Resources & Other Circle Resources) Group Resources

2000‧‧‧ (members, guests, visitors) social devices

2002‧‧‧Social resources

2004‧‧‧Access and distribution management functions

2006‧‧‧Access rights

2008‧‧‧Access Control Function

2010‧‧Arbitration and dynamic (re)distribution

2012‧‧‧Access View Control

2014‧‧‧ (Browser & Downloadable or Pre-installed) application

2016‧‧‧ (safety) certification or safe operation

2100‧‧‧Social devices

2101‧‧‧Users

2102‧‧‧Communication interface and transceiver circuit

2104‧‧‧Processing Circuit

2106‧‧‧(Device/Group Information & Other Resources) Resources

2108‧‧‧User Information Message

2110‧‧‧User Interface Circuit

2112‧‧‧ (SNET Management) application

2114‧‧‧ docking logic

2116‧‧‧Communication Protocol Control

2118‧‧‧Resource Management

2120‧‧‧Safety/Certification (Security)

2122‧‧‧ core or underlying functions

2124‧‧‧Storage

2126‧‧‧SNET/SNET Group/SNET Subgroup

1 is a schematic block diagram of a social network packet hierarchy in accordance with various embodiments of the present disclosure; FIG. 2 is a schematic block diagram of a social network packet hierarchy in accordance with various embodiments of the present disclosure; Schematic block diagram of a social networking environment of various embodiments; FIG. 4 is a schematic block diagram of a social networking environment in accordance with various embodiments of the present disclosure; FIG. 5 is a social networking environment in accordance with various embodiments of the present disclosure. Schematic block diagram; FIG. 6 illustrates a social networking environment in accordance with various embodiments of the present disclosure; FIG. 7 illustrates an electrical social networking group/subgroup in accordance with various embodiments of the present disclosure; FIG. Vehicle social networking group/subgroup of various embodiments of the present disclosure; FIG. 9 is a flowchart in accordance with various embodiments of the present disclosure; FIG. 10 is a flowchart in accordance with various embodiments of the present disclosure; FIG. A flowchart of various embodiments of the present invention; FIG. 12 is a flowchart in accordance with various embodiments of the present disclosure; FIG. 13 illustrates a social networking environment in accordance with various embodiments of the present disclosure; FIG. 14 illustrates a social networking infrastructure and social devices in accordance with various embodiments of the present disclosure; FIG. 15 is a various embodiments in accordance with the present disclosure. Schematic block diagram of an embodiment of a social device; FIG. 16 is a schematic block diagram illustrating accessing social resources of a social networking group/subgroup in accordance with various embodiments of the present disclosure; FIG. 17 is a various embodiment in accordance with the present disclosure. A schematic block diagram of an embodiment of a social device/server that includes communication and control protocol functions; FIG. 18 illustrates social device members and access within a social networking group/subgroup in accordance with various embodiments of the present disclosure; 19 illustrates remotely accessing social resources of social network groups/subgroups in accordance with various embodiments of the present disclosure; FIG. 20 is a social device including overall resource access and allocation management functions in accordance with various embodiments of the present disclosure. Schematic block diagram of an embodiment; and FIG. 21 illustrates a social device including an overall function that is operable to support Social network group/subgroup members and communications of various embodiments.

The terms "social network," "SNET," "social network system," "social network infrastructure," and the like, as used herein, include groupings or social structures of devices and/or individuals, and such devices and/or Connections, connections, and correlations between individuals. Members or participants (including devices) within or affiliated with SNET may be referred to herein as "members", "users", "members", "nodes", "social devices", "SNET members", "SNET" Membership, "SNET Device", "User Device" 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 and suitably adapted in a specific environment. Includes personal SNET members, device SNET members, personal area networks ("PAN"), and more.

Referring now to Figure 1, a social network ("hereinafter referred to as "SNET") packet hierarchy 100 is illustrated in accordance with various embodiments. In certain embodiments, the SNET packet hierarchy 100 includes at least a portion of the SNET inclusions. One or more layers of SNET infrastructure that can interface with other SNET infrastructure, SNET groups, social devices, etc. (hereinafter referred to interchangeably as "associated", "connected", "combined", etc.). For example, in the office In the illustrated embodiment, one layer of SNET packet hierarchy 100 may include a serving SNET infrastructure 101, and another layer of SNET grouping hierarchy 100 may include one or more client SNET infrastructures 103, 105, and 107. In some embodiments The layers can be docked so that the "higher" layer can interface with the "lower" layer so that the "lower" layer accesses the various functions provided by the "higher" layer.

In some embodiments, one or more infrastructures are managed by one or more management systems, processing systems, computers, service devices, network nodes, social devices, some combination thereof, and the like. For example, in the illustrated embodiment, some or all of the service SNET infrastructure 101, one or more client SNET infrastructures 103, 105, and 107, some combination thereof, etc. may be supported by one or more social services. The device 111, one or more client social devices 131, 141, and 151, one or more management services, some combination thereof, and the like are managed. The processing system may include, but is not limited to, one or more instances of processing circuitry distributed over one or more server devices, network nodes, some combination thereof, and the like. In some embodiments, some or all of the SNETs may be managed by a management service that one or more processing systems may support. For example, the management service can manage the docking process between various devices, between various devices and SNET groups, between various SNET groups, between some combination thereof, etc., managing various devices that interface with various SNET groups, devices, and the like. The communication path between services, services, etc., is interchangeably referred to herein as a "social path."

For example, in the illustrated embodiment, the SNET packet hierarchy 100 includes a serving SNET infrastructure 101 at a first level and multiple clients at a second level SNET infrastructure 103, 105 and 107. 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, clients, SNET members, SNET non-members, SNET customers, some combination 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 or docked with one or more services. In some embodiments, a SNET group within an infrastructure can interface with one or more third party services, applications, and the like. Client SNET infrastructure 103 may include one or more social devices 131 and one or more clients associated with one or more specific clients (referred to hereinafter as users, members, visitors, guests, etc.) End SNET group 135. 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 within the client infrastructure 103 can interface, associate, connect, etc. with the SNET group associated with the client. At least in US Utility Patent Application Serial No. 13/408,986 (Attorney Applicant Application No. BP23776), filed on February 29, 2012, entitled "Social Device Resource Management", discusses at least in detail A docking process, the entire text of which is hereby incorporated by reference in its entirety. In some embodiments, a device, SNET group, etc. that interfaces with another SNET group becomes a member of the SNET group to which it interfaces. By interfacing the client social device 131 with the client SNET group 135, a user associated with the client SNET group 135 can interact with the SNET group 135 by interacting with the social device 131 that interfaces with the SNET group 135. The members, clients, users, and the like shown herein 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 functions may include, but are not limited to, various services, applications, SNET groups, some combination thereof, etc., which may be mixed, combined, fused, and some of them by docking processing. Combine and so on to one or more SNETs Within the group, by interacting with one or more SNET groups, a selection of the required functions can be accessed. For example, the service SNET infrastructure 101 illustrates various service support functions that the social user device 111, various social applications 113, and the like can provide. In some embodiments, the SNET member can interact with the SNET group 115 or the SNET group 117 that interfaces with the service support social user device 111, access various service support social user devices 111, and can directly or through social interaction with and The application 113 interfaces with the SNET group 119 or the SNET group 117 to access various social applications 113. One or more functions provided by device 111 and application 113, SNET groups 115 and 119 docked with device 111 and application 113, some combination thereof, etc., may be combined into a single SNET group, the group of accessible devices One or more functions provided by a service, application, SNET group, some combination thereof, and so on.

For example, the social device 131 is interfaced with a single SNET group 117 that is itself associated with the SNET groups 115 and 119 by a docking process 125 such that the user accessible SNET groups 115 and 119 of the client SNET infrastructure 103 are provided by interfacing with the SNET group 117. These features.

In some embodiments, the functionality provided by one or more SNET groups, infrastructure, etc., can be accessed by interfacing one SNET group with another SNET group. For example, the client SNET group 135 can interface with the SNET group 117 through the docking process 125, thereby enabling the user of the client infrastructure 103 to access the functionality provided by the SNET group 117 through the client SNET group 135. In particular, when one or more social devices 131 interface with the client SNET group 135, the user can access the functionality provided by the SNET group 117 through one or more social devices 131 that interface with the client SNET group 135. The docking process 125 may include connecting the client SNET group 135 as a member of the SNET group 117, interfacing the client SNET group 135 with the SNET group 117 by one of various processes, some combination thereof, etc. (also referred to herein as "Associated"), in this article and at least on January 3, 2012, the US Utility Patent Application Serial Number entitled "Social Network Device Memberships and Applications" 13/342, 301 (Attorney Application No. BP23771), and US Utility Patent Application Serial No. 13/408,986, filed on February 29, 2012, entitled "Social Device Resource Management" (attorney agent) These processes are described in application Serial No. BP23776), the entire disclosure of which is hereby incorporated by reference in its entirety.

When describing the above embodiments, users entering business premises (including but not limited to stores, restaurants, hotels, establishments, public areas, etc.) need access functions, including but not limited to those provided by the SNET group associated with the business premises. Services, applications, messages, devices, some combination of them, and more. Rather than individually interfacing each user device with the SNET group, the user can simply interface the individual SNET group (the user device is docked with the personal SNET group) with the SNET group associated with the business location, thereby allowing the user to pass the user already with their personal SNET. The ability of some or all of the devices docked to access the premises. As another example, a hotel may provide various functions through the SNET group, including but not limited to accessing a call routing telephone service, controlling a particular television device, accessing a database, some combination thereof, and the like. The personal device and the hotel's SNET group are not individually docked to use the provided functionality, including but not limited to docking the smart phone device with the hotel's SNET group to interface with the hotel's SNET group using the call routing telephone service To control a particular television set or the like, the customer can simply dock their personal SNET group with the hotel's SNET group and then access the functionality provided by the hotel's SNET group through the device that interfaces with their personal SNET group.

In some embodiments, the SNET group is docked such that users, members, clients, etc. can access the functionality provided by various services, devices, SNET groups, etc. associated with various SNET infrastructures, which increases security. For example, when a user associated with the first client SNET infrastructure 103 can access only the functionality provided by the service SNET infrastructure 101 by interfacing with the SNET group 117, the service SNET infrastructure 101, the client SNET infrastructure 103 One or more related processing systems, devices, etc., can use various levels of security to ensure secure access to these functions. Moreover, in some embodiments, accessing the functionality provided by the SNET infrastructure by docking two or more SNET groups provides an additional level of security. For example, when the functionality provided by the access service SNET infrastructure 101 is such that client SNET groups 135, 145, 155, etc. are required to interface with the SNET group 117, a more secure connection with various security levels can be employed, and by managing the client Access to these functions can be readily permitted, changed, restricted, terminated, etc., by a single docking, association, etc. between the end SNET group and the SNET group 117. Based on input received from the user, third party entity, some internal logic, elapsed time period, change in geographic location of the client social device 131 associated with the client SNET infrastructure 103, some other triggering event, some of it Combinations and the like, processing systems, devices, etc. associated with the service SNET infrastructure 101, the client SNET infrastructure 103, etc., can manage this association.

In some embodiments, the selection and docking process 125 can be mechanized, automated, some combination thereof, and the like. For example, depending on the location of the user of the infrastructure, including but not limited to geographical proximity to one or more users, social devices 131 associated with the user, social devices 131 that interface with a particular client SNET group 135, some combination thereof, etc. Etc., the docking process is triggered so that the process can be automated. In some embodiments, 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 with other SNET groups. Conditions may include, but are not limited to, one or more social devices 131 that interface with a particular client SNET group 135 are geographically adjacent to a geographic location associated with the SNET group 117, with the infrastructure 103, the SNET group 135, the social device 131, A certain combination or the like is associated with the user authorization so that the client SNET group 135 interfaces with the SNET group 117, some combination thereof, and the like. The relevant rules can be communicated to the social device 131, which interfaces with a particular SNET group 135, a processing system that manages various SNET groups, some combination thereof, and the like. One or more processing systems, social devices 131, some combination thereof, etc., can monitor client SNET group 135, social device 131 that interfaces with client SNET group 135, and relative to one or more correlation rules One or more One or more attributes of one or more SNET groups 117 of one or more attributes of a client SNET group 135, a docked social device 131, some combination thereof, etc., to determine whether one or more SNETs will be Groups, social devices, etc. are docked together. The correlation rules can be changed at runtime by the user, the processing system, some other entity, etc., in order to generate new rules, delete rules, change rules, and the like. For example, a user associated with the client SNET group 135 can transmit a change in a dependency rule that has previously transmitted a dependency rule to the processing system that prohibits geographically adjacent to the threshold of the social device 131, The client SNET group 135 and the SNET group 117 are connected. The change of the correlation rule may include, but is not limited to, changing the threshold geographical proximity, authorizing the client SNET group 135 and the specific SNET group 117 to connect one by one, and commanding the client SNET group. 135 is disconnected from another SNET group, some combination thereof, and the like.

In some embodiments, each layer of SNET packet hierarchy 100 can access messages at different levels. For example, in the illustrated embodiment, a user of the "higher level" service SNET infrastructure 101 can view each client SNET group 135, 145 associated with the "lower layer" client SNET infrastructures 103, 105, and 107. And 155, the client SNET infrastructure interfaces with the SNET group 117 associated with the social service infrastructure 101. Users of the service SNET infrastructure 101 may be able to view various social devices 131, 141, and 151 that interface with different 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 can view the SNET group provided through the "higher layer" infrastructure. Some or all of the functionality (the SNET group associated with the "lower layer" infrastructure interfaces with the "higher layer" infrastructure), but the user cannot view some or all of the various SNET groups 115 and 119 including but not limited to " The higher level infrastructure initially provides the functionality provided by the SNET Group 117 through the "higher layer" infrastructure. In addition, the "lower layer" infrastructure user accesses the SNET group 117 associated with the "higher layer" service SNET infrastructure 101, which cannot be viewed and also interfaced with the same SNET group 117. Some or all of the other similar "lower layer" client SNET infrastructures 105 and 107.

In some embodiments, the selection and docking process 125 can be controlled, managed, etc. by one or more different social devices, processing systems, management services, and the like. For example, the processing system of the SNET infrastructure can control one SNET group to interface with another based on user interaction with SNET, one or more correlation rules, one or more inputs, some internal logic, some combination thereof, and the like. In conjunction with undocking, the SNET infrastructure can include one or more instances of processing circuitry, network nodes, some combination thereof, etc. distributed across one or more server devices. As another example, a social device may control the docking of one or more SNET groups based on user interaction with the SNET, one or more relevance rules, one or more inputs, some internal logic, some combination thereof, and the like. And detached from docking. In some embodiments, a processing system, a social device, some combination thereof, etc., that are authorized to manage a "higher layer" infrastructure can manage one or more "lower layer" foundations that interface with a "higher layer" infrastructure. One or more access attributes of the facility. For example, a processing system that authorizes control of a "higher level" social service infrastructure 101 may change access to certain functions, restrict access to certain functions, by passing SNET groups and devices, depending on input or some other logic. Detach the docking to terminate access, some combination thereof, and so on. The processing system may determine a triggering event including, but not limited to, the following: all social devices 131 that interface with the client SNET group 135 that interfaces with the SNET group 117 have exceeded a predetermined threshold geography of the geographic location associated with the SNET group 117. The proximity distance, and according to the determination, the client SNET group 135 and the SNET group 117 are undocked, partially or completely restricting the client SNET group 135 from accessing certain functions provided by the SNET group 117, some combination thereof, etc. Wait.

In some embodiments, various SNET groups are created by a portion of the SNET infrastructure, including but not limited to, based on user input, members, processing systems, devices, SNETs, SNET groups, some combination thereof, and the like. Management services. For example, when the SNET infrastructure 103 is associated with a SNET member account, members of the account may The input is provided to the SNET infrastructure 103 to create the SNET group 135. The input may include, but is not limited to, attributes of group 135, social devices 131 that interface with group 135, messages available to one or more members of the group 135, some combination thereof, and the like.

In some embodiments, one SNET group within the SNET infrastructure interfaces with another SNET group. For example, in the illustrated embodiment, SNET group 135 interfaces with SNET group 117 via a docking link. One or more SNET groups can interface with another SNET group through one or more various docking processes, including but not limited to being individually docked by one or more devices, SNET groups, and the like.

In some embodiments, the docking process can include interaction between at least some of the first SNET group and the second SNET group. For example, when the SNET group 135, the application 113, etc. are to interface with the SNET group 117 via the docking link, the SNET group 135, the application 113, and the SNET group 117 can reference one or more members between the two SNET groups, Docked devices, functional components, available messages, some combination thereof, etc., exchange of secure message processing, and the like. This exchange can additionally securely verify proper interaction and access between two SNET groups, their various members, and the like. In some embodiments, additional secure processing (eg, personal confirmation requirements) is used to ensure secure interaction between the functionality of one or more docked SNET groups, devices, members, and the like.

In some embodiments, the docking process can include various actions taken by one or more SNETs, SNET systems, SNET infrastructure, processing systems, SNET groups, social devices, users, members, some combination thereof, and the like. Actions may include, but are not limited to, verifying the best docking location, displaying the docking link to users, members, and the like. For example, when a user associated with the SNET infrastructure 103 interacts with the SNET infrastructure 103 to interface the SNET group 135 with a portion of the SNET infrastructure 101, thereby accessing various functions of the SNET group contained within the SNET infrastructure 101. The docking process for associating, docking, etc., the SNET group 135 with another SNET group within the SNET infrastructure 101 may include, but is not limited to, determining one or more different SNET groups within the SNET group 135 and the SNET infrastructure 101. Optimal docking configuration between the members of the SNET group 135 to allow access to the SNET infrastructure 101 Some or some of the features. As shown in the illustrated embodiment, the SNET group 135 can interface with the SNET group 117 over the first docking link and interface with the SNET group 115 through the second docking link as part of a single docking process, thereby placing the SNET group 135 is associated with certain functions provided by various SNET groups within the SNET infrastructure 101, wherein the optimal docking configuration determination includes, but is not limited to, interfacing the SNET group 135 with the SNET group 117 and the SNET group 115 to access these Features. Certain other combinations of docking specifications, single docking specifications, as part of one or more SNET infrastructures 101 and 103, management services, some combination thereof, etc., can control various docking links. In some embodiments, the docking link and the docking specification can be docked, associated, etc., using 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 process associates SNET group 135 with certain functions of SNET infrastructure 101 by interfacing with SNET group 117 and SNET group 115, which may include setting up a display of the docking link for access Members of these functions do not see the complete complexity of docking links, interactions, etc. between various SNET groups, devices, SNET infrastructure, and the like. In the illustrated embodiment, for example, the docking process of interfacing SNET group 135 with SNET group 117 and SNET group 115 may include displaying a display of the functionality of SNET group 117 accessible by members of SNET group 135, representative maps, and the like. In order to hide the fact that the SNET group 117 is interfaced with the two SNET groups 115 and 119 through two docking links. Simplified displays, representative figures, and the like may only show a diagram of the SNET group 117 that interfaces with certain functions of the SNET infrastructure 101. In some embodiments, members can adjust, switch, or manipulate the complexity of displays, representations, and the like to display to members a docking link, interaction, etc. between the SNET infrastructure, SNET groups, social devices, and the like. Part of the complexity or the entire diagram.

In some embodiments, establishing multiple docking links may provide additional security in order to access certain functions. For example, when the docking link between the SNET group 135 and the SNET group 117 provides a docking link for a function, the docking link has a ratio A more secure link of the docking link of the SNET group 115, the indirect link of the SNET group 115, some combination thereof, etc., the docking process may include establishing a docking link to provide a function for a function Access a link that is safer to another functional link. In some embodiments, establishing multiple docking links can more efficiently access functions, services, and the like than a single docking link. For example, when the docking process includes determining that the docking link of the SNET group 117 and the SNET group 115 can access certain functions of the SNET infrastructure 101 more efficiently than a single docking link, the docking process can include, but is not limited to, the SNET infrastructure 101. The SNET group establishes multiple docking links.

In some embodiments, docking links between different SNET groups, social devices, and the like are managed according to different docking specifications. In some embodiments, the docking specification can manage one or more specific docking links, and for example, rather than by way of limitation, different functions related to the SNET group, depending on which access is changed, restricted, permitted, terminated, Security access requirements, access time periods, access restrictions related to triggering events, restrictions, permissions, and more. For example, as shown in the illustrated embodiment, the SNET group 135 can include a docking specification 106 that controls the docking link between the SNET group 135 and the SNET group 117. In some embodiments, the separate docking specifications contained within group 135 can control the docking links between SNET group 135 and SNET group 115, SNET group 135 and device 131, some combination thereof, and the like. Prior to docking, the docking specification is partially or fully predetermined by the members of the SNET group 135, which is created as part of the docking process for the SNET group 135 to connect to another SNET group at runtime, by the SNET infrastructure 103, attempting to interface with SNET The docking specification is provided by the group 135 docked SNET group, some combination thereof, and the like. For example, a member of the SNET group 135 can establish a docking specification 106 that can restrict member access by the SNET group 117 to be provided by the SNET group 135, one or more devices 131 that interface with the group 135, etc., based on later triggering events. The function of the trigger event includes but is not limited to the elapsed time period, member access authorization, some combination thereof, and the like. In some embodiments, the docking specification is specific to certain attributes of other SNET groups and devices, thereby interfacing the SNET group 135 into various SNET groups with associated attributes. E.g, The docking specification 106 may indicate that the SNET group 135 is to interface with the SNET group 117 associated with the geographic location within a predetermined threshold through the docking link, the geographic location being adjacent to the geographic location associated with the SNET group 135, and the docking specification may indicate if If the geographic location associated with the SNET group 117 has exceeded the proximity threshold, then the docking link to the SNET group 117 is restricted and terminated.

In some embodiments, certain, or may be adjusted, managed, changed, created, deleted, etc. based on user input, members, SNET systems, SNET infrastructure, docked devices, docked SNET groups, some combination thereof, and the like. All docking specifications. For example, members of SNET group 135 can establish docking specifications 106 to control the docking links of one or more SNET groups 117, 115, and 119, thereby restricting members of SNET groups 115, 117, 119, 145, and 155 from accessing the SNET group. 135. Certain functions of the device 131 interfaced with the SNET group 135, etc., then interacting with the SNET group 135, the SNET infrastructure 103, some combination thereof, etc., to change the docking specification 106 such that members of the SNET group 117, Members of group 145 that interface with SNET group 117 and more access the functionality provided by SNET group 135, one or more devices 131 that interface with SNET group 135, some combination thereof, and the like. In the self-organizing process, the docking specification can be managed at any time during the self-organizing process, relative to the existing docking link, the docking specification for controlling the potential docking link, some combination thereof, and the like.

In some embodiments, the docking specification that controls the docking link between the "higher layer" SNET group and the "lower layer" SNET group is part of a higher layer SNET group. For example, in the illustrated embodiment, SNET group 117 is a higher layer SNET group, and SNET groups 135, 145, and 155 are lower layer SNET groups, lower layer SNET groups 135, 145, and 155 and higher layer SNET groups. The docking link between 117 is controlled by the docking specification, which is part of the higher layer SNET group 117, and is thus controllable by the higher layer SNET group on the docking link with the lower layer SNET group.

In some embodiments, the docking specification can be modified by users, members, SNET systems, SNET infrastructure, social devices, some combination thereof, etc., to provide various levels of interaction and access between different docked SNET groups. . For example, in the explanation In the illustrated embodiment, the docking specification 106 may indicate one or more devices 131 that interface with the SNET group 117 at one or more SNET groups 135 and 117 connected by the docking link, and the SNET group 135, Between a combination and so on, providing full two-way interaction, sharing messages, services, and more. In another example, the docking specification 106 can indicate that the docking link provides one-way group-to-group service access between the SNET group 135 and the SNET group 117 via the docking link, so members of the SNET group 135 can access the SNET group. At least some of the services provided by the functions of 117, but members of SNET group 117, members of groups 145, 155 that are docked with group 117, etc., are unable to access certain or all of the messages, services, devices, etc. associated with SNET group 135. . For example, the hotel customer's SNET group is docked with the hotel's SNET group to allow the hotel customer to control the docking link specification between the hotel customer's SNET group and the hotel's SNET group when accessing the hotel service function through the hotel's SNET group. It may be provided to restrict hotel customers from accessing certain functions of the hotel's SNET group while restricting the hotel's SNET group from accessing any functions of the hotel customer's SNET group, including but not limited to accessing devices that interface with the hotel customer's SNET group. In another example, when the first adjacent SNET group interfaces with the adjacent observation group, and the first adjacent security camera, motion detector, or the like interfaces with the first adjacent SNET group, the first neighbor may be restricted. Or not allowing the neighbor to observe the members of the SNET group accessing the data generated by the first neighboring security device, but the first neighbor may later change the docking specification to allow members of the neighboring viewing group to access some or all of the first neighbors Some or all of the data generated by the security device, thereby transmitting data generated by some or all of the first adjacent security devices to a neighboring observation group for access, monitoring, analysis, and the like. As noted above, in certain embodiments, different users, members, SNET groups, SNET infrastructure, and the like can change such access and interaction aspects of the docking specification at any time.

In some embodiments, the docking specification imposes certain restrictions on the functionality of the SNET group, providing and supplying these functions to members of the docked SNET group. For example, the docking specification 106 may indicate that only certain functions of the SNET group 135 are provided to members of the SNET group 135 via one or more links with the SNET group 117. Docking specification 106 may also instruct each of the SNET groups 135, 145, and 155 to access different one or more functions of the SNET group 117 differently. For example, docking specification 106 may instruct each of SNET groups 135, 145, and 155 to uniquely access one or more functions of SNET group 117.

In some embodiments, the docking links between the various SNET groups can allow additional SNET groups to access the functionality provided by the SNET group, with additional SNET groups indirectly associated with these SNET groups, docking, and the like. For example, in the illustrated embodiment, when the SNET group 145 interfaces with the SNET group 117 through the docking link, the SNET group 145 can interface with the SNET group 135 through the docking link between the SNET groups 135, 117, and 145. One or more docking links are controlled by docking specifications 406 within the SNET group 135. In some embodiments, members of SNET group 145 may be permitted to access at least some functions of SNET group 135 (members of SNET group 117 are permitted to access SNET group 135). The various docking specifications may determine the functionality of members of the SNET group 117 to access the SNET group 135, including but not limited to the docking specification 406 that controls the docking link between the SNET group 135 and the SNET group 117, and the control SNET group 117 and one or One or more docking specifications for a docking link between multiple SNET groups 135, 145, and 155. For example, by restricting the functionality of the SNET group access SNET group 135 that interfaces with the SNET group 117, the docking specification 106 may permit members of the SNET group 135 to access certain functions of the SNET group 135 through a docking link with the SNET group 117. In another example, the docking specification 406 may dictate that members of the SNET group 117 may not access, access, or access the functionality of some or all of the other SNET groups, including but not limited to the device 131 that interfaces with the SNET group 135.

Various docking specification restrictions In addition to local group supply, various docking specification restrictions are also available for chain supply. For example, SNET group 135 can freely allow any other SNET group to pass through a direct docking link to SNET group 117, through an indirect link, through a docking link to a SNET group that interfaces with SNET group 117, some combination thereof, etc. Accessing all of the offerings, including but not limited to services, content, materials, access to docked devices 131, some combination thereof, and the like. In some embodiments, it can be docked Specification 106 defines this freely provided access. However, the docking specification 406 may limit access through the SNET group 117, including but not limited to disallowing access to some or all of the provisioning of any external SNET group, the SNET group 135 interfacing with external SNET groups, including but not limited to one Or multiple SNET groups 145 and 155. Thus, depending on the docking connection and the chained SNET group and device specifications, the supply can be managed in various ways according to the underlying requirements. In some embodiments, this connection and chain management of the entire supply is used twice: once for one access direction. For example, the supply restrictions associated with the SNET infrastructure 103 can be quite different from the SNET infrastructure 105. Moreover, even if all of the associated docking specifications within the SNET infrastructure 101 can allow for at least restricting access to a particular provision of SNET groups that interface with the SNET group 117, such accesses cannot be extended to, for example, the docked device 131 and the SNET group 135, This is because: a) the docking specification 106 further proposes access restrictions beyond the access restrictions required by the SNET infrastructure 101, b) the associated docking specifications within the SNET infrastructure 101 may limit foreign connections, some combination thereof, and the like.

For example, in an ad hoc travel network docking configuration, a visitor's personal SNET group structure (eg, SNET infrastructure 103) may need to provide very limited access to the hotel's SNET group structure (eg, SNET infrastructure 101), However, in the other direction, the hotel's SNET group structure supply can be provided freely. Each structure only needs to provide access to any offerings, membership certificates, messages, etc. to be presented. Visitors may choose to present, for example, a) a payment service component located somewhere within the entire personal SNET group structure; b) an incoming messaging service for the social smart phone of the visitor; c) an incoming messaging service for the administrator; Travel document storage service; a certain combination, etc., and the hotel can choose to present functions, supplies, etc., including but not limited to: 1) regional catalogs, maps and other information services; 2) concierge services; 3) billing Service; 4) reservation service; 5) network office equipment; some combination thereof. For example, by various docking specifications associated with the original SNET group, presentation in either case can be defined to be modified by docking specifications associated with the SNET group within the chained path to the destination.

In another example, an adjacent personal SNET group structure (eg, SNET infrastructure 103) may need to provide very limited access to a neighboring watch group structure (eg, SNET infrastructure 101), and in another direction, Proximity observation of the SNET group structure supply can be provided freely. Access provided by the neighbor may include access to data generated by various devices 131 associated with the neighbor, including but not limited to security devices, monitoring devices, and the like.

In some embodiments, the docking specifications can be extended to provide resolutions that exceed the group level. For example, prior to providing access through the docking link, the docking specification 106 may require identification, various levels of security verification, some combination thereof, and the like, and even include providing proof of identity. In another example, the docking specification 106 defines a member of the SNET group 135 to access a component, service within the SNET group 145 through a secure interaction of the local social smart phone 141 of the desired visitor to the SNET group 145. Or a particular offer provided by the device participant, but some or all of the other members of the SNET group 155, other SNET groups, etc. cannot access the particular offer. In other words, for one or more specific SNET group offerings, functions, provisioning identifiers, etc., and for one or more specific group members, member messages, etc., specific chain docking specification details can be established to manage the entire Access, including but not limited to restricted access. Thus, while functionally shown as being distributed, associated with each link, etc., the chained specification process can be managed by a single user interface and the process can be stored within a single repository structure.

In some embodiments, the default docking specification can handle provisioning, accessing, interacting, etc., with respect to one or more particular SNET groups by default, but authorizing members, devices, SNET systems, SNET groups, SNET infrastructure, some of them Combinations, etc., allow for specific provisioning modifications, other access modifications, some combination thereof, and the like. Similarly, the entire default process 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, device 131 that interfaces with SNET group 135 initiates docking of SNET group 135 The docking specification 106 may be part of the SNET group 135 when docked to the SNET group 117. Moreover, the docking specification 106 can be part of the SNET group 117 when the docking process of the SNET group 135 to the SNET group 117 includes a portion of the SNET infrastructure 101 that receives and agrees to a partial DNET infrastructure 103 docking request. In some embodiments, the docking request may include, but is not limited to, a request to connect one SNET group to another SNET group, a request to connect the device to the SNET group, a function of the first SNET group (including but not limited to services, The access device, application, etc.) provides a request to one or more devices that interface with the second SNET group. The docking request may come from a device that interfaces with the first SNET group, a device that interfaces with the second SNET group, a member of the first SNET group, a member of the second SNET group, a third party, some combination thereof, and the like.

By interfacing with SNET group 117, SNET group 135 can access some or all of the functionality of SNET group 115 and SNET group 119 as specified by one or more docking specifications within infrastructure 101; instead, SNET group 135 and SNET group 117 When docked, the SNET group 117 can access some or all of the functionality of the SNET group 135 as specified by the docking specification 106.

In some embodiments, interfacing various SNET groups with various SNET groups within various SNET infrastructures can include various access restrictions and limitations. For example, when the SNET group 115 is docked with the SNET group 117 that interfaces with the SNET group 119, these SNET groups are all within the SNET infrastructure 101, and various levels of various SNET groups can be determined by managing various docking specifications for controlling the docking links. Interaction and access. The three docked SNET groups 115, 117, and 119 can access some or all of the functions of each other, the SNET group 117 can access the functions of the SNET group 115, and the SNET groups 117 and 115 can access each other's functions, while the SNET group 117 may access certain functions of SNET group 119, some combination thereof, and the like. This interaction, access, docking, etc. can be performed without any interaction with third party entities, third party SNET groups, and the like.

In some embodiments, a third party entity, a third party SNET group, etc., when included in a docking link, need to have a third party entity, a third party SNET group, etc. Additional interaction. For example, when one or more devices 131 are to interface with SNET group 117, docking, accessing, etc., need to interact with one or more SNET groups 135 through a third device, which may be part of infrastructure 103. In some embodiments, docking processing between SNET groups associated with individual SNET infrastructure, users, members, and the like can be initiated, managed by various devices, processing systems, SNET systems, SNET infrastructure, and the like. For example, one or more other devices 131 that interface with SNET group 135, one or more devices that interface with SNET group 117, one or more devices that interface with a third party SNET group, one or more processing systems, one Or a plurality of SNET basic settings, some combination thereof, etc., initiate and manage the docking between the first device 131, the SNET group 135, and the like and the SNET group 117.

In some embodiments, the functionality provided by one or more SNET groups, infrastructure, etc., includes services, devices, etc. that access one or more interfaces that interface with one or more SNET groups Devices and SNET groups, etc. and interact with them. For example, in the illustrated embodiment, the service SNET infrastructure 101 can include one or more social service applications 113 that monitor and analyze data related to one or more customer social user devices 131, customer social users. The device 131 interfaces with the SNET group 117 directly or indirectly through the docked client SNET group 135 or the like. Such monitoring and analysis may include, but is not limited to, receiving data, one or more social devices controlled by the social device, devices communicating with the social device, some combination thereof, etc., a sensor, component, functional component, etc. Generate and collect this information. In some embodiments, the social service application 113 receives the data from the user device 131, and the user device 131 interfaces with the group 117 directly or indirectly through the docking group 135 or the like, wherein the data and device 131 and the device 131 Another component, a functional component, a sensor, etc. associated with another device connected, some combination thereof, and the like. The information may be provided by the device 131 as requested by the device 131, by the access device 131 via the link with the SNET group 117, as provided by one or more docking specifications within one or more of the infrastructures 103 and 101. The docking specification may authorize access to the material; in some embodiments, one or more entities may change the pair Connect specifications so that at runtime, limit, enable, terminate, authorize scheduled trigger events, trigger conditions, and more.

In some embodiments, monitoring data includes comparing data and messages to determine if the data is associated with one or more thresholds. For example, the social service application 113 can monitor the device 131 by determining whether the material is associated with a message stored locally in the infrastructure 101, a third party infrastructure, one or more third party devices, some combination thereof, or the like. data of. Analytical data includes, but is not limited to, one or more assembly, comparisons of data received from one or more devices, SNET groups, etc., in order to identify data trends, determine whether data from one or more sources is in accordance with a predetermined one. Or multiple trigger events, some combination thereof, and so on. For example, application 113 may collect data from devices 131, 141, and 151 associated with a plurality of individual motion detectors and analyze the data to track motion over a geographic area. In another example, one or more of the devices 131, 141, and 151 includes an image capture device that can generate an image of the item and a GPS beacon, and the application 113 collects images and GPS coordinates from the devices 131, 141, and 151, the coordinates corresponding to At the time and place of the captured image, the application 113 may include monitoring and analysis systems, monitoring systems, analysis systems, monitoring and analysis services, monitoring services, analysis services, etc., to identify images associated with certain messages. Specific items and then analyze the data to track the item in geographic area and elapsed time.

In some embodiments, the one or more functions provided by the first SNET group include one or more functions capable of accessing a device that interfaces with the first SNET group, a second SNET group, and the like. Such access may be based on monitoring and analyzing data received by one or more functions provided by the first SNET group. For example, in the illustrated embodiment, the application 113 monitors data from one or more SNET groups 135, 145, and 155, one or more devices 131, 141, and 151, some combination thereof, and the like, the application 113 may respond to certain inputs, triggers, etc. by interacting with one or more devices, third party entities, some combination thereof, and the like. The third party device can include a user associated with the device from which at least some of the material is received, with one or more infrastructure The associated internal logic, SNET group, etc., identified predetermined devices, SNET groups, accounts, and the like. For example, an application may access (via communication, interaction, etc.) one or more devices 141, third party SNET groups, devices, members, etc. that have been predetermined by application 113, some other member, device, entity, and the like. Etc., the response determines that the data from one device 131 is associated with exceeding the trigger threshold. In some embodiments, the application can respond by interacting with another user device when the material has been received from one of the user devices. For example, when data has been received from device 131 that interfaces with group 135, the group 135 is a sensor device that generates data related to the environment adjacent to one or more devices 131. By collecting additional data from the sensors, application 113 can In response, requesting data from another separate device 131 that interfaces with group 135, transmitting the signal to a separate device 131 having a user interface, interacting with a third party device, analyzing data collected from the plurality of devices to track data trends , some combination of it, and so on.

Referring now to Figure 2, certain embodiments of the SNET packet hierarchy 200 can enable the client SNET group 135 to interface with SNET groups that provide the functionality of various infrastructures. In the illustrated embodiment, the two infrastructures 201 and 203 are combined, docked, and associated to provide functionality from the two infrastructures 201 and 203 through a single combined SNET group 237. The global social service infrastructure 201 includes functionality provided by various social networking support devices 211, social service applications 213, and various SNET groups 215, 219, and 217 that combine some of the functionality provided by the infrastructure 201. In addition, the local/regional social service infrastructure 203 also includes various SNET groups 225, 229, and 227 provided by the social service support user device 221, the social service application 223, and some combination of functions provided by the infrastructure 203. The function. The combined local/regional and global SNET group 237 provides a combination of the functionality provided by the social service support user devices 211 and 221 and the social service applications 213 and 223 provided by the infrastructures 201 and 203. When the client SNET group 135 can interface with the SNET group 237, by interfacing a single client SNET group with a single SNET group 237, members of the client SNET group 135 can Access to the functionality provided by these two infrastructures.

In some embodiments, the representative map 205 of the members of the client SNET group 135 provided to access the functionality provided by the SNET group 237 includes only the combined functionality provided by the two infrastructures 201 and 203, with the infrastructure Some or all of the instructions are unrelated and initially provide some or all of the functionality through the infrastructure. In the illustrated embodiment, for example, the functions provided by the social service support user devices 231 and 221 are displayed in the representative map 205 as a combined group of the social service support user devices 231; likewise, the representative map 205 is displayed from this. The social service applications 213 and 223 of the two infrastructures 201 and 203 serve as a combined group of social service applications 233. Moreover, for members of the representative map 205 that access the functionality provided by the SNET group 237, all or one of the SNET groups 215, 217 within the infrastructure within the SNET group 237 is partially or fully integrated by one or more docking processes. 219, 225, 227, and 229 may be partially or completely transparent. In some embodiments, the members of the access representative map 205 can restore the entire complexity of the combination of infrastructures 201 and 203 in the representation 205 so that the member can view various SNET groups and various infrastructure-specific functions as well as The features provided.

As an example of the illustrated embodiment, the hotel chain can provide a global SNET infrastructure 201 that provides functions common to all hotels that are franchised, such as a global media database, corporate contact information, a message database, and one of them. Combination and so on. In addition, a local hotel needs to have a local SNET infrastructure 203 that provides access to local entertainment venues, dining, news, local hotel-specific device access, some combination thereof, and the like. The hotel needs to combine the functionality of the hotel chain provided by the global SNET infrastructure 201 with the functionality of the specific location provided by the local SNET infrastructure into a combined SNET group 237 to allow the hotel customer to use a single docking process and via a single representative 205 Accessing global and local capabilities, the representative provides global and local functionality in partial or complete combinations.

In some embodiments, one or more processing systems, social devices, members, applications, some combination thereof, etc. associated with one or more infrastructures Or fully manage the combination of features provided by separate infrastructure. For example, in the illustrated embodiment, the processing system associated with the local SNET infrastructure 203 can manage the integration of the functionality of the infrastructures 201 and 203 into the SNET group 237, managing the docking of the client SNET group 135 and the SNET group 237, Some combination of it and so on.

In some embodiments, network administrators, processing systems, social devices, some combination thereof, etc. permit, restrict, terminate client SNET group 135 access based on input, trigger events, some other internal logic, and the like. SNET group 237. For example, when a social device that interfaces with client social device 135 leaves a business location associated with SNET group 237, by terminating or restricting access granted during docking, changing interactions with some or all of the functionality provided by SNET group 237 Authorization, detaching the client social device 135 from the SNET group 237, some combination thereof, etc., terminates the client SNET group 135 accessing the functionality provided by the SNET group 237. This can occur automatically in response to a triggering event, including but not limited to a predetermined time elapsed after entering or leaving the premises. In some embodiments, after the device that interfaces with the client SNET group 135 leaves the premises, the client SNET group 135 can maintain the remaining access to the SNET group 237. For example, when the business place related to the SNET group 237 is a hotel, and the member related to the client SNET group 135 belongs to the exclusive member of the hotel, the client SNET group 135 associated with the member may be after the docked device leaves the business place. At least some access to the functionality provided by SNET Group 237 is still received, including but not limited to call routing telephone services.

In some embodiments, a SNET group associated with a member (including a person, device, etc.) can interface with another SNET group to enable the member to access or receive services, contact information, other messages related to the SNET group. , exchange messages, some combination of them, and more. Such members may be existing members of SNET, non-members, also referred to herein as third parties, and the like. For example, a human user with a device may be within a threshold of an access point of a business location or the like (eg, near the threshold) such that the access point, some other device associated with the business location, etc., send an invitation, In order to connect the SNET group related to the business site with the human user through the device, and install Set itself to dock, some combination of it, and so on. The invitation may change depending on whether the human user and/or the device is already a SNET member, a non-member, and the like. For example, when the device is not a social device, the access point may send the invitation to the device in the form of a webpage by providing a browser application such as a device, an individual user, some combination thereof, etc., and join the SNET as a temporary member. group. When the device is a social device, the invitation may include a direct invitation to interface the SNET group with the SNET group associated with the business premises via a social interface, user interface, etc. on the device.

The invitation is accepted by one of the various acceptance processes. For example, the social device receives an invitation including a unique identifier that uniquely identifies the SNET group to which the member is invited to dock the SNET group, social device, etc., at which point the social device can interface with it via a separate path or the like The ingress, another device, SNET, SNET group, SNET subgroup, etc. interact to accept the invitation using a unique identifier. Acceptance within the above examples may include simply transmitting a unique identifier and identifying a message of the SNET group associated with transmitting the unique identifier to interface the SNET group with the SNET group associated with the business premises. In addition, when the non-social device attempts to access the access point and the access point pushes the web page into the browser application on the non-social device, the accepting process may include accessing the web page, indicating the need to interface with the SNET group, providing a certain Other messages, etc., can accept non-social devices, temporary client SNET groups, some combination thereof, etc., and interface with SNET groups associated with the business premises.

Upon acceptance of the invitation, members, individual users, devices, some combination thereof, etc., may at least access and operate the functions provided by the SNET group associated with the venue. For example, when the business premises is a coffee shop, members of the personal SNET group and the SNET group associated with the business site may access various services, including but not limited to online, through one or more devices that interface with their personal SNET group. Newspapers, videos, item sales lists, home delivery options, on-site delivery booking interfaces, other messages, some combination, and more. In another example, when the business location is a hotel, a private residence, etc., a member of the personal SNET group that interfaces with the SNET group based on the business premises can access the service through one or more devices that interface with their personal SNET group. Messages, etc. This includes, but is not limited to, accessing content items stored locally or remotely, contact information, accessing functional elements of a field device, some combination thereof, and the like. In another example, when the business location is a shopping mall, any access point can transmit and push invitations to devices, device users, some combination thereof, etc., to interface with the SNET group associated with the shopping center. The access point may require that the device, user, etc. attempt to access the access point before sending the invitation 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 each store within the shopping mall, etc., display of those groups of malls that interface with the SNET group at the location of the particular store A map service, a shopping mall music service providing a music source or other media content provided by a media source associated with the SNET group for those groups that interface with the SNET group, a phone book service, and any object in any store within the mall Search engine, some combination of it, and more.

In some embodiments, the access point supports sending invitations to interface with SNET groups, processing acceptance invitations, routing communications between SNET groups and members of SNETs, temporary members, and potential members, SNET groups, and the like. The device needs to attempt to access the access point in order to receive the invitation provided by the access point. In some embodiments, the access point will automatically provide the access point to the access point to determine any device that passes through the threshold, such as a predetermined proximity to a business location, location, and the like. Those that interface with the SNET group include temporary members, SNET groups, self-organizing SNET groups, some combination thereof, and the like, and can be coupled with other devices, users, members, and the like that also interface with the SNET group. When passing through another or the same threshold, you can terminate or restrict docking with the SNET group. For example, when the device entering the business premises temporarily connects to the SNET group through the access point, and determines that the device has left the business site, the access point can restrict and terminate the temporary docking.

Referring now to Figure 3, a social network (hereinafter referred to as "SNET") environment in accordance with various embodiments is set forth and discussed. In the illustrated embodiment, the infrastructure 301 is connected to various functions 313, 315, 321 and 325, some or all of the various infrastructures 350, 360 and 370, and various third party devices 381 through the docking links of the SNET group 331. Provide interaction between each other. In some embodiments, some or all of the various infrastructures Supported by various processing systems, SNET systems, SNETs, management services, devices, network nodes, some combination thereof, and the like.

In some embodiments, various devices, groups, services, applications, and the like can interface with one or more various devices, groups, services, applications, and the like. For example, in the illustrated embodiment, various portions of infrastructure 350, 360, and 370, including various devices 357 and 351 that are part of infrastructure 350, interface with one or more SNET groups 331 controlled by various docking specifications 324. . The management system, the processing system, some combination thereof, etc. can support and manage the docking of various devices with the SNET group. Various docking links to one or more SNET groups, etc., may be represented by one or more representative diagrams of various functions, services, applications, etc., which may be interfaced with the group or the like. Groups, various components, infrastructure, devices, etc. are provided. For example, in the illustrated embodiment, one or more users associated with infrastructure 350 may provide representative maps 391 of various functions, components, etc. associated with group 331 in which one or more devices 351 and 357 interface with the SNET group 331. As noted above, diagram 391 can show a simplified diagram of SNET group 331; diagram 391 can also display a restriction map of components, functions, and the like that interface with group 331. In some embodiments, the user can interact with the representative map to interact with the various functions provided by the docking group. For example, in the illustrated embodiment, a user associated with infrastructure 350 can interact with representative map 391 to interact with various functions provided by SNET group 331, including but not limited to the various services provided with SNET group 331 , applications, etc. interact, interact with data provided by various services, applications, functions, devices, infrastructure, groups, etc. that interface with SNET Group 331 to access various devices that interface directly or indirectly with SNET Group 331 One or more different functional components, various docking specifications 324 that manage the docking links that control the SNET group 331, and the like. Moreover, in some embodiments, users associated with infrastructure 350 can manage various docking specifications 324 to manage access to and/or as a basis for some or all of the docked components, functions, infrastructure, devices, etc. of SNET group 331 Information, functional departments related to various devices, groups, etc. of a part of the facility 350 Pieces and so on.

In some embodiments, various users associated with the infrastructure are represented by a variety of different representations of the infrastructure, groups that interface with some or all of the infrastructure, and the like. For example, in the illustrated embodiment, devices 357 and 351 of infrastructure 350 interface with SNET group 331, and at least one user of infrastructure 391 is represented by a representative map 391 of functions provided by SNET group 331, and Various other users associated with facility 350 may be represented by different representative maps 333 of group 331. These different graphs 333 may represent different levels of access to the functionality provided by the SNET group 331. For example, when the user represented by the representation 391 is the owner of the infrastructure 350, and the different family members, friends, neighbors, etc. of the user have at least some access to the infrastructure 350, the user may be functional through the SNET group 331. "Neighborhood and Family" diagram 333, the functionality of group access group 331 is limited. Restrictions may include, but are not limited to, restrictions on accessing or managing various docking specifications 324.

In some embodiments, the functionality provided by the SNET group includes services, applications, and the like that interface with the SNET group through docking. The management system can manage the support docking process. For example, the management system may have one or more different social monitoring and analysis service applications 321 (hereinafter referred to interchangeably as "monitoring systems"), functions 313, 315, 325, etc., through one or more different docking processes. Wait until the SNET group 331. In some embodiments, the functionality may be provided by a third party service, application, or the like that interfaces with the SNET group 331.

In some embodiments, the SNET environment is capable of interacting between various devices, SNET groups, functions, services, applications, etc. based on analysis of data from various sources. For example, the interaction may be based on identification of various triggering events, in response to various triggering events within the data received in the data source, and the like. Interactions may include, but are not limited to, accessing various devices, groups, infrastructure, etc., of various other functional devices, groups, and the like associated with one or more SNET groups. For example, in the illustrated embodiment, SNET group 331 enables docking, association with SNET group 331, some or all of the different infrastructures 350, 360, and 370, and various third party devices 381. The various functions 313, 315, 321, 325 access the data received from various devices, SNET groups, and the like. According to various docking specifications 324 as part of one or more of the infrastructures 301, 350, 360, and 370, such access can be managed, controlled, and can be with one or more infrastructures, one or more devices, one or One or more users associated with a plurality of third parties, one or more processing systems, one or more management systems, some combination thereof, etc., establish, manage, change, update, terminate such access. For example, in the illustrated embodiment, data for one or more devices 357 that interface with SNET group 331 may be provided to SNET group 331, wherein docking specifications 324 for various links between management device 357 and group 331 Certain services, applications, entities within infrastructure 301, members of SNET group 331, infrastructures 360 and 370, third party devices 381, etc. are restricted from accessing material. One or more authorized users, devices, processing systems, management systems, SNET groups, etc. may change the docking specifications at any time under certain conditions based on internal logic, triggering event responses, and the like.

Accessing data from the source may include, but is not limited to, receiving data provided by the docked source to the SNET group, accessing the source of the docking through one or more docking links to obtain data, and providing data from the requesting source from the source of the docking Receive data, some combination of it, and more. This type of access control of various docking specifications controls the various links of the SNET group. For example, in the illustrated embodiment, a user associated with infrastructure 350 can manage docking specifications 324 to allow SNET group 331 to receive material from various devices 357 that interface with SNET group 331.

In some embodiments, different members, functions, services, applications, devices, etc., coupled to a SNET group, device, processing system, infrastructure, etc., can process, monitor, and analyze the received data. For example, in the illustrated embodiment, infrastructure 301 can include one or more monitoring and analysis service applications 321 that can monitor, analyze, and process received from various devices, groups, etc. that interface with SNET group 331. data. Such monitoring, analysis, processing, etc. may include, but is not limited to, monitoring data to determine whether the data is related to one or more different thresholds, meets and exceeds the threshold, wherein the thresholds are built by various applications in operation Predetermined by various sources and accessed by the monitoring and analysis application during the operation, these thresholds can be stored as messages in the network-related infrastructure 301, the processing system of the support infrastructure 301, various devices, Processing a part of the system, network nodes, and so on. Different applications 321 , some portion of infrastructure 301 , some portion of a third party, another infrastructure 350 , 360 , and 370 can establish, update, rewrite, and terminate thresholds. In some embodiments, the social monitoring and analysis service application 321 can include, but is not limited to, monitoring services, analytics services, monitoring and analysis services, and the like. One or more monitoring and analysis service applications may also include third party services. For example, one or more social monitoring and analysis service applications 321 can include third party monitoring services.

In some embodiments, the monitoring and analysis application can respond to data, analyze data, and the like by selectively triggering support functions. Such a response can include determining that some or all of the data is associated with a threshold, meets and exceeds the threshold by taking various actions. Support functions may include, but are not limited to, attempting to obtain additional messages from various sources; various notifications, requests, etc. are sent to various services, devices. Infrastructure, etc.; analyzing data from one or more different sources to determine trends, master items, track events, some combination thereof, etc.; control one or more portions of one or more devices, and the like. For example, when the social monitoring and analysis service application 321 that monitors the data received from the device 357 by the docking group 331 determines that the data received from the device 357 exceeds a threshold, the application 321 can access the device 357 by accessing a portion of the device 357. Determining to respond; accessing a portion of device 351; transmitting a notification to a user associated with device 357 using signals accessible by the user via various interfaces 353, 355, etc. on device 351; through the interface and controlling the application Program 325 (which is coupled to application 321 via SNET group 331), interacts with at least some portion 353, 355, etc. of third party device 381; interacts with different entities via devices 313 and 315; through devices 313 and 315 Some or all of the received data, data analysis of the application 321 , invitation to interface with the SNET group 331, some combination thereof, etc. are transmitted to various entities; different bases with some or all of the SNET group 331 Assume Shi 360 and 370 interact; some combination of them and so on. In some embodiments, accessing a portion of a device that interfaces with a SNET group can include, but is not limited to, controlling at least some functional component of the device, accessing another device through the docked device, some combination thereof and many more.

In some embodiments, various functions, services, applications, devices, SNET groups, and the like can be docked to each other by different docking processes, and can be initiated and managed by components, third devices, groups, and the like to be docked. For example, in the illustrated embodiment, based on commands, inputs, etc. from a user associated with infrastructure 350, based on input, commands, etc. of the other device 351 as part of infrastructure 350, some combination thereof, etc. And, device 357, which is part of infrastructure 350, can initiate a docking process to interface with SNET group 331 without interfering with human users associated with infrastructure 350. In some embodiments, devices, groups, and the like can be interfaced with another device, group, or the like by actions, commands, inputs, and the like from another device. For example, in the illustrated embodiment, a user can interact with various interfaces 353 and 355 on interface device 351 to interface various devices 357 and SNET group 331, and the docking link between management device 357 and SNET group 331 will The various SNET groups and SNET groups 331 that are part of the infrastructure 350 are docked, some combination thereof, and the like. The user can use the interface device to manage the docking specification 324 of the link between the control device 357 and the SNET group 331 to establish various responses and various actions to be taken by the various monitoring and analysis service applications 321 in response to various decisions. and many more. For example, the user can set the third party device 381 using the device 351. If it is determined that the data of the docked device 357 exceeds a certain threshold, the application 321 communicates with the third party device.

In some embodiments, various infrastructures, SNET groups, devices, etc. associated with the SNET system interact to enable monitoring of data for various devices and responding to data monitoring. For example, in the illustrated embodiment, the SNET group provides functions, services, applications, and the like related to social security services, and may include monitoring and responding to various security systems that interface with the SNET group 331 within the infrastructure 301. . In response to input from another infrastructure, device, etc., based on an internal logic The group 331 may be established by a portion of the infrastructure 301, including but not limited to management services. In some embodiments, the illustrated monitoring and analysis service application 321 that interfaces with the SNET group 331 can monitor and analyze data received from one or more docked data sources, including but not limited to devices, SNET groups, and the like. And interacting with various third party devices 381, interacting with various devices 357, 351, etc. associated with various infrastructures 350, 360, and 370, in response to such monitoring and analysis, by interacting with various services 313 and 315, and many more. In certain embodiments, security system device 357 can include, but is not limited to, a motion sensor, a camera system, an environmental sensor, some combination thereof, and the like. Based on some logic internal to device 357, based on commands, inputs, etc. of interface device 351, through the SNET group (to which device 357 interfaces) to the SNET group 331, some combination thereof, etc., device 357 can be associated with the SNET group. 331 docking without disturbing the user. The SNET group 331, various members, functions, services, applications, infrastructure, some combination thereof, etc., which are provided with respect to various docking specifications, internal logic of various processing systems, devices, etc., are transmitted, provided, and docked. Some or all of the material generated by device 357, another device 357 connected to docking device 357, some combination thereof, and the like. For example, device 357 that interfaces with SNET group 331 can set a docking specification that restricts only some applications 321 and docked infrastructures 360 and 370 to access the data generated by device 357 and through SNET with interface device 351. The representative map of group 331 interacts, and the user associated with infrastructure 350 can further manage and change docking specifications 324. In some other embodiments, the user can interface the different security devices 357 with the SNET group 331 using the interface device 351, set various docking specifications for the links between the control device 357 and the SNET group 331, and the like. When various docking specifications 324 can allow the monitoring and analysis service application 321 to access the data generated by the docked device 357, the application 321 can monitor the data associated with the various thresholds. For example, in the illustrated embodiment, the data generated by the various security devices may include images, video streams, motion detection data, various other materials associated with the environmentally adjacent docking device 357, some other location, and the like. The application 321 can monitor the threshold data, including but not It is limited to detecting motion at different predetermined times, and detecting motion when receiving an alarm notification from a different user, a third party, or the like. In some embodiments, the social monitoring and analysis service application can be located on a device outside of the service infrastructure 301. For example, in the illustrated embodiment, the application 371 can be located on the interface device 351 and can monitor and analyze some or all of the data generated by the various devices 357, and send the monitoring and analysis data to the SNET group 331, one of which Combinations and so on. In some embodiments, the device generating the data can also be monitored and analyzed, and the results of the monitoring and analysis are provided to the SNET group 331.

The monitoring and analysis service application can take responsive actions when it receives the data. Such responsive actions may include triggering one or more support functions. A responsive action may be taken in response to determining that the profile is related to, exceeds, and meets the threshold. For example, in the illustrated embodiment, by transmitting an alert notification to the user associated with device 357 at interface device 351, an alert notification is sent to various other docked infrastructures 360 and 370, some or all of which are monitored. Data, alarm notifications, and the like are sent to various services 313, 315 and services connected to the SNET group 331, and alert notifications, data access of various devices 357, and the like are transmitted to the third party device 381, some combination thereof, etc. The third party monitoring service 321 docked by the SNET group 331 can respond to the data representation position motion from the various docked devices 357. In some embodiments, the alert notification may include requests for additional access, docking, etc., of different devices associated with the notification recipient; invitations to interface with different devices, SNET groups, etc.; with various other devices, users, etc. Request for communication. For example, by transmitting an alert notification to the third party device 381, the application 321 may respond to the determination of the location indication movement from the docking device 357, the notification may include a contact message to contact the different services associated with the device 357. User, device 357 itself, some combination thereof, and the like.

In some embodiments, the monitoring application can analyze data from various sources to establish trends, track events, track trends, track objects, some combination thereof, and the like. For example, application 321 is based on an analysis of data from device 357, When detecting the motion of the first location, the application can analyze the data of the various additional docking devices of the infrastructures 350, 360, and 370 to track motion detection over a wider geographic area. If the docking specification currently limits such access, the application can send a request to a user associated with various devices, infrastructure, etc., to allow access to the material of the associated device. In addition, when the monitoring and analysis application is located on the devices 351, 357, etc., the application 371 can access and request storage with respect to various devices related to the infrastructures 360 and 370 and the like, various third-party devices 381, and the like. And so on, communication with various services 313 and 315 associated with SNET group 331, signaling to users associated with infrastructure 350 via interface device 351, one or more representative maps 391 and 333, some combination thereof, and the like.

In some embodiments, various materials, analytics, functional components, and the like can be accessed based on notifications received from various services, users, and the like. For example, in the illustrated embodiment, the third party device 381, the user, service 313, service 315, etc. associated with the infrastructure 350, 360, 370, etc., can send an alert notification to the SNET group 331 for transmission and forwarding. Various devices, infrastructure, etc. that interface with the SNET group 331. Such notifications may include requests to modify various docking specifications so that different members, functions, infrastructure, devices, etc., that interface with SNET group 331 can access the data generated by various devices 357. For example, the law enforcement service 313 can send a local crime notification to the security device SNET group 331 that forwards the notification to the infrastructure-related users having the device 357 that interfaces with the group 331, wherein the notification includes user management Various requests for docking specifications 324 are provided so that various applications, other users, services 313, etc. can access the materials of the associated device. In some embodiments, the service 313 can unilaterally traverse the docking specification 324 and access data, functional components, and the like associated with various devices that interface with the SNET group 331. For example, when the law enforcement service 313 receives a crime notification at a location, the service also uses the SNET group 331 to control and access the security device 357 associated with the location in the process of crossing the various docking specifications 324. In some embodiments, the alignment specification may override certain access restrictions depending on certain triggering events. For example, response The monitoring and analysis service application 321 determines that a trigger event is identified by the device 357 that exceeds a certain threshold. The docking specification 324 that controls the data generated by the SNET group 331 access device 357 can bypass all data access. limit.

In some embodiments, communication, interaction, etc., continue between different devices, SNET groups, services, applications, etc., over one or more different communication links. For example, in the illustrated embodiment, when the social device 351 interfaces with the SNET group 331, and the monitoring and analysis service application 321 (eg, a third party monitoring service) interfaces with the SNET group 331, the social device 351 and the monitoring service 321 can Interacting through one or more different communication paths may include, but is not limited to, a social path. For example, communication between the social device 351 and the monitoring service 321 may flow through a path provided by one or more management services within the SNET infrastructure 301, including but not limited to management services that support the communication path, and the device 351 and monitoring The service 321 interfaces with the SNET group 331, a certain combination thereof, and the like. A SNET group that interfaces with two entities provides a communication path between the two entities. For example, in the illustrated embodiment, the communication path between device 351 and monitoring service 321 may be provided by SNET group 331. This path can travel directly or indirectly. For example, the communication path between the device 351 and the monitoring service 321 can be continued by the third party entity, by the management service supporting the SNET group 331, by the third party entity, and by the agent, some combination thereof, etc., to redirect the communication path. The communication path can be made directly in the point-to-point path between the device 351 and the monitoring service 321 without going through the management service. For example, the monitoring service 321 can access the address information of the SNET group 331 and can use the message to communicate with the device 351 without going through the SNET group 331. The communication path can also be continued through an agent, which can include third party devices, services, and the like. In addition, the communication path can be redirected through devices, services, nodes, etc. outside of the SNET infrastructure 401. Path characteristics may be determined by management services, one or more processing systems, docking devices, services, applications, third parties, and the like. Moreover, the path features may be managed by one or more management systems, devices, services, nodes, etc. associated with the path, and may be altered to adapt to changes in path characteristics, including but not limited to Rate, latency, bit error rate, some combination thereof, and so on.

Referring now to Figure 4, an environment of a social network (hereinafter referred to as "SNET") in accordance with various embodiments is illustrated and discussed. Certain embodiments of the environment discussed in FIG. 3 may be configured for various services. For example, in the illustrated embodiment, various processing systems, devices, network nodes, SNET systems, SNETs, some combination thereof, and the like may partially or fully support infrastructure 401, which provides the functionality of medical service group 431 The medical service group is able to interact between various medical devices, interface devices, third party devices, applications, services, and the like. Such interaction between docking devices, infrastructure, and the like can be controlled by different docking specifications 424, which can be part of a docked infrastructure, a central service infrastructure, some combination thereof, and the like. In the illustrated embodiment, and discussed in FIG. 3, various devices 459 associated with infrastructure 450 may interface with SNET group 431 that is part of infrastructure 401; such docking may be initiated by docking device 459, by another A device 451 controls, some combination thereof, and the like. Interactions with functions, members, services, applications, docking infrastructure, etc. associated with SNET group 431 may continue through interaction with one or more different representative maps 491 and 433 of SNET group 331.

In some embodiments, one or more monitoring and analysis services 421, 471, etc. can monitor data generated by one or more different devices that are directly or indirectly interfaced with SNET group 431, and based on data analysis, different The decision to respond. For example, when the infrastructure 450 includes various devices 459 including motion detection devices, the motion detection device generates motion detection data for different rooms in a house in which an elderly user, an individual, or the like resides, and the application 421 can respond to the decision: The contact request is sent to the interface device 451 associated with the infrastructure 450, and the motion is no longer detected in a certain room and during a certain period of time. The request may require the elderly to communicate with services, applications, etc. associated with the SNET group 431 via interfaces 435 and 455, etc., thereby ensuring that the individual does not stop exercising due to some weakness, injury, or the like. In some embodiments, the application 321 can compare the threshold to the data received from the docking device, which threshold can include various time and location ranges. For example, solution In addition to, equipped with some other device, security system, etc., if the data from device 459 indicates that it has been stopped for some time of day, in certain rooms in the house, in some combination thereof, etc. Motion, then the application 321 may only determine that the threshold has been exceeded, which may constitute a triggering event that requires some reaction of the infrastructure 401. The application 421 can also respond to the determination of the triggering event by sending a notification to the third party device 481. For example, in response to determining that there is a lack of motion within the premises after a certain period of time by sending a request to a third party device 481 of a neighbor, family member, friend, etc., the application 421 may pass through the interface device 451, some other Methods, a combination of them, etc., contact the elderly to ensure personal safety. In some embodiments, the application 421 can respond to the following determinations: by sending an alert notification to different services 417, 419, 415, etc., various neighboring infrastructures 460, 470, etc., access control and infrastructure 450 related various devices, some combination thereof, etc., the notification sent to device 351 has not received any response, and some additional time has elapsed. In some embodiments, when it is initially determined that the data for the various devices 459 exceeds a threshold, a notification is sent to one or more different services 417, 419, 415 such that a triggering event occurs. For example, when device 459 is a medical device that monitors personal health, an application that monitors data generated by some or all of the devices may respond to the following decisions: by sending an alert notification to various services, infrastructure, third party devices, etc. , the data exceeds the threshold. In some embodiments, the infrastructure sent to the notification can be determined by various messages related to the infrastructure. For example, when infrastructure 401 accesses a message identifying a geographic location associated with some or all of infrastructures 450, 460, and 470, responding to determining that a triggering event has occurred may include transmitting an alert notification to the infrastructure, Related devices, devices, and the like, devices, etc., are geographically adjacent to a certain threshold of one or more devices, infrastructure, etc. that have triggered events, and the infrastructure, devices, etc. are geographically related.

In some embodiments, the infrastructure is capable of interacting between various devices and services. For example, in the illustrated embodiment, through various medical services 419, fire service 415, ambulance service 417, various other services, some combination thereof, etc. Messages, interactions, etc., based on data received from various devices, infrastructure, etc., the application 421 can respond to the determination that one or more trigger events have occurred. In some embodiments, at least some portion of the infrastructure 401 can invite one or more different services to interface with the group 431, interface with various services, detach from various services, some combination thereof, and the like.

Referring now to Figure 5, an environment of a social network (hereinafter referred to as "SNET") in accordance with various embodiments is illustrated and discussed. Certain embodiments of the environment discussed in FIG. 3 may be configured for temporary services, interactions, and the like. For example, in the illustrated embodiment, the social service infrastructure 501 can establish an ad hoc SNET group 531 that interfaces with various functions, services, applications, infrastructure, devices, and the like. As shown in the illustrated embodiment, the infrastructure 501 can include an ad hoc SNET group 531 that only connects certain services 313, 325, 419, 315, and 521 associated with the infrastructure 501, but is associated with the infrastructure 401 At least some of the services 417 are not connected to the self-organizing SNET group 531. In some embodiments, one or more of the various self-organizing SNET groups are established to determine which services, functions, services, applications, infrastructure, devices, etc., to which the connection, docking, and invitation are docked, which may be by the infrastructure 501, one or Management of multiple different users, one or more different user systems, infrastructure, and the like. For example, a user associated with user system 550 may request to create an ad hoc SNET group 531 that is connected to certain services, functions, applications, infrastructure, and the like. The infrastructure 501 can respond to the creation of the group 531 by sending an invitation to interface with the group 531 to a different infrastructure, system, device, etc., based on user input, according to some internal logic, some combination thereof, and the like. . In some embodiments, creating a SNET group includes specifying a threshold message by which the monitoring and analysis service application monitors data received from certain docked devices to identify trigger events, track trends, track events, Track entities, some combination of them, and more.

For example, a user associated with system 550, law enforcement service 313, some combination thereof, etc. may report a child abduction event to infrastructure 501. Responding to the report, responding to An additional request for an abduction event-specific SNET group, some combination thereof, etc., the infrastructure 501 can create an ad hoc SNET group dedicated to abduction events. In some embodiments, the infrastructure can receive threshold information from user system 550, service 313, access threshold information from service 315, access threshold information from third party devices, some combination thereof, and the like. For example, users, services, and the like that require the creation of an ad hoc SNET group 531 dedicated to abduction events may provide threshold information regarding licenses, manufacturing, models, etc. associated with the vehicle, which involves an abduction event. The infrastructure 501 can also find threshold information from predetermined third party devices, services, and the like. The infrastructure can also find threshold messages from sources identified by an internal logic.

In some embodiments, by interfacing one or more different devices, certain devices, etc. with SNET group 531, infrastructure 501, user system 550, third party device 381, some combination thereof, etc. may request other Systems 560, 570, etc. are added to the self-organizing SNET group 531 to enable monitoring and analysis of the data generated by the docked devices. For example, in the illustrated embodiment, the invitation requests the car user to interface the camera device 557 located in the car that provides the license plate image captured by the camera device with the SNET group 531 for analysis by various applications 521. By interacting with one or more interfaces 553, 555, etc., a separate interface device 551 can interface with device 557, and the user interacts with the interface device such that such device 557 can interface with group 531. In some embodiments, the user may also authorize various applications, services, infrastructure, devices, third parties, users, etc. by setting one or more docking specifications 573 for the link between the control device 557 and the SNET group 531. The data generated by the various docking devices 557 is accessed.

In some embodiments, the application can monitor the data received from the docking device to determine if the data for any one or more of the devices is related to a threshold. Determining that when the threshold is reached, the triggering event can be caused, the application 521, the infrastructure 501, the processing system supporting some or all of the infrastructure 501, some combination thereof, etc. can be taken by taking one or more actions , responded. For example, the application 521 receives a license plate image from various camera devices that interface with the SNET group 531. For example, when one or more license plate images associated with an interest vehicle are identified within the threshold message, the application can send a notification to one or more services, infrastructure, third party devices, etc. that have taken an image of the vehicle of interest. In some embodiments, when the image material received from the one or more docked camera devices includes geographic location data generated by various devices associated with the docking device, the notification can include a time and location indication of the vehicle identification. The notification can also be sent to the user associated with the device that captured the trigger image to provide additional information, contact a law enforcement service, track identified vehicles, some combination thereof, and the like.

In some embodiments, an application can analyze data received from various devices, infrastructure, etc. to collect trends, grasp trends, master time, master entities, some combination thereof, and the like. For example, one or more applications 521 can analyze an image with associated time and location data from various devices that interface with SNET group 531 and several images are associated with the threshold information to identify the vehicle of interest. Received data to inform the direction of movement of the vehicle of interest, to predict its potential movement, to inform the predicted location of the vehicle, possible trajectories, some combination thereof, etc., to various services, applications, third parties, foundations Facilities, installations, etc.

Certain embodiments in accordance with the present disclosure include a wide range of social devices, device services, agents, and various software applications that participate as members of the SNET/SNET group. Moreover, social devices and other types of SNET/SNET group members have related or specific aspects, features, dependencies, etc., which can form SNET/SNET groups with specific uses, such as those described in FIG. 1 below. Various embodiments may include, for example, SNET/SNET group members, such as device manufacturers, vehicle owners, hospitals and medical providers, garages, insurance companies, and others that may be interested in communicating with human members and/or related SNET devices. Third party. This SNET/SNET group/SNET subgroup can be a stand-alone or extension of other SNET/SNET group/SNET subgroups.

Certain embodiments of the SNET/SNET group/SNET subgroup according to the present disclosure include Various safety devices and related services. Such SNETs may include, for example, child supervision groups, proximity observation groups, police/fire and security company groups, and the like. In some embodiments, a police or security company may participate in the SNET to monitor a series of criminal alert situations through the system and neighboring groups of participants. Other actions/functions may include, but are not limited to, a socially docked alert system generating an alert (eg, neighboring security device activation may trigger an alert at a nearby home, may allow a neighbor to identify a thief, etc., and activate a continuous set of neighboring homes outdoors) Lighting); activate a security camera with recording capabilities; some combination of it, etc. Also, in some embodiments, the police can access and participate in the full area mapping using SNET. In this way, social network "civilians" and their communication devices (opening sensor device recordings) are used in and around the area, and the personal identity of potential visitors can be recorded for use as evidence to identify and quickly process criminal hotspots. .

In some embodiments, the social (home) communication device indicates when the home may be vacant. When the house is vacant, the motion detection performed in the house can be regarded as intrusion. The social camera device can then be activated to begin capturing and storing motion related messages over the social network and transmitting them to the home communication device. Family members then make decisions about this message and, if necessary (through a docked social device), engage the police or security team.

In certain embodiments, social security/security devices may include, but are not limited to, smoke, carbon dioxide and helium detectors, some combination thereof, and the like. For example, social smoke detectors can send alerts in a conventional manner as well as through some or all of the docked social devices within the secure SNET/SNET group. With this SNET group, other social devices in the home can start an alarm. Some of these devices may even be transmitted to neighbors, friends or relatives, fire stations and/or other supervisors. In some embodiments, other social device members may be used through the SNET group. For example, a social camera dedicated to the home can be activated and the camera begins capturing, storing, and forwarding video. To identify intruders, face recognition can be used. The fire or police can view the forwarded video to assess whether it is necessary to schedule and/or contact the owner (using social outfits within the dominant SNET) Set) for voice/video communication. Smoke data can also be transmitted with smoke detector metadata such as GPS data ("bedroom" on the northeast corner of the first floor of the house), home address, owner, contact details, etc., which can be used by the social security SNET group. section. It is to be noted that the social smoke detector can have an integrated camera as well as a fire storage for subsequent explanation of the cause of the fire.

Figure 6 illustrates an embodiment of interaction between various social devices and one or more social networks. In some embodiments, the social device can be located in an environment, including but not limited to home environment 600, automotive environment 692, office environment, industrial environment, some combination thereof, and the like. A social device located in one environment can be a functional device that interacts with a social network, other devices, and the like. For example, home environment 600 can include one or more devices that are socially conscious, including but not limited to one or more social security devices 620, one or more social security devices 610, one or more additional social devices 630, and the like . The social security device can be a smoke detector, a fire alarm, a carbon monoxide detector, a sprinkler, a helium detector, a Geiger counter, some combination thereof, and the like. The social security device 610 can include, but is not limited to, a motion detector, a lock, a security system, a closed circuit television (CCTV) camera, some combination thereof, and the like. Additional social devices may include, but are not limited to, thermometers, temperature controllers, lawn sprinkler systems, humidity detectors, rain gauges, and the like. Such a device may perform, in addition to its separate functions, one or more social networks or social network groups, other devices within or outside the home environment 600, within a social network, or outside of any social network. Multiple members, some combination of them, etc. interact. As a member of SNET 650, a particular SNET group 603 dedicated to a similar type of device, some combination thereof, etc., the social device may be dedicated to or not dedicated to one or more aspects of the social device, social device, etc. The SNET 650 interacts. User input, internal logic, and the like can determine whether the social device interacts with the SNET 650 or the SNET group 603. For example, when connected to the network, the social smoke detector can be hardwired, find and access one or more selected SNETs 650, SNET groups 603, and the like. The social device can be configured to communicate with one or more SNETs over a wireless network, a wired network, a cellular network, some combination thereof, and the like. 650, SNET group 603 and so on. This connection can be adapted to change local conditions. For example, as long as the smoke detector receives power from within the house, the social smoke detector can interact with the social security device group 603 using the wireless network, but loses the primary power or the primary power drops below a certain threshold, such as through a cellular The network can be switched to a lower power connection.

Participants of SNET 650 may include entities having particular interests in one or more aspects of social devices 610, 620, 630, 694, and the like. These aspects may include, but are not limited to, one or more of the functions, functions, features, locations, performance, some combination thereof, and the like associated with one or more devices. For example, SNET 650 may include one or more security companies 660, emergency service providers 670, insurance companies 680, maintenance services 690, accounts of SNET members associated with one or more home environments 600, automotive environments 692, etc., and Or personal social device 606 that is not associated with a SNET member account, some combination thereof, and the like. When the social device sends a notification to SNET 650, SNET group 603, etc., additional notifications may be sent to one or more members of SNET 650 or SNET group 603, respectively. For example, when the social security device 610 detects an intruder, in addition to triggering an alert, the social security device 610 also sends an alert signal to the SNET 650 warning that some or all of the member social security devices of the SNET 650 have raised an alert. The alert signal can be directed to any member of SNET 650, certain members, and the like, such as any device 606 or account 608 associated with a member of home environment 600, one or more security companies 660, emergency services 670, and the like.

When the social security device 620 is a smoke detector that detects smoke, the alert signal can be sent to the SNET 650, or to the SNET group 603 dedicated to or not dedicated to smoke detectors, social devices within a particular home environment, and the like. The alert signal may be received by a member of the SNET 650 or SNET group, including but not limited to emergency services, insurance companies, repair services, devices 606 associated with members of the home environment 600, or accounts 608, and the like. Moreover, in some embodiments, participants of SNET 650, SNET group 603, etc. can interact with social devices within home environment 600, even if they are not currently in the environment. For example, in the case of launching a social security device 610 (eg, a security device), The security company 660 receiving the alert signal from the social security device 610 via the SNET 650 can instruct the social security 610 to activate a local CCTV camera within the home environment 600, activate some other social device 630, or can activate the additional social device itself. Moreover, when the social security device 620 (eg, a smoke alert) is triggered, when the alert signal is received from the social security device 620 via the SNET group 603 at the device 606, a member of the home environment 600 can command the shutdown of the additional social device 630 that caused the fire, This includes but is not limited to household gas lines. To this end, certain devices can be combined into a SNET group to facilitate activities involving multiple devices simultaneously. For example, in the above case, all socially conscious devices 630 (eg, cooking appliances, gas lines, gas heaters, etc.) that cause a fire can be collectively combined into a SNET group, thereby receiving a certain alarm, family environment members Commands can be sent to all devices in the group in one action, such as a command shutdown.

In certain embodiments in accordance with the present disclosure, insurance company 680, repair service 690, etc. participate in SNET 650 to view and verify driving behavior history/data and possibly underestimate relevant driving behavior history/information. For example, the company may interact with one or more car social devices 694 within one or more cars, car environments 692, and the like. When an event involves car environment 692, social car device 694, etc., messages may be sent to certain members of SNET 650 either directly or through SNET 650. For example, if the car environment 692 is involved in an incident, the social car device 694 can send a message to the SNET 650 that can be distributed to the emergency service 670, the insurance company 680, the repair service 690, one or more separate household accounts 608, or A device 606 associated with the automotive environment on the SNET 650, some combination thereof, and the like.

In some embodiments, the interaction between one or more user management devices and the SNET group. This interaction can support aspects related to one or more SNET groups. Members of the SNET may be part of one or more family accounts 608, may control, access devices within the home environment 600, some other device 606, 694, etc., may manipulate the account 608, devices associated with the account 608, etc. The interaction between. For example, members of the SNET group can manipulate other members of the SNET group under the control of members of the SNET group. Take messages, functional components, etc. associated with one or more devices. When the SNET group is associated with a local neighbor watcher, the user can allow some or all members of the SNET group to access messages for one or more devices. Such access may include, but is not limited to, directing the device to interact with the SNET group, directing the device to upload the message to the SNET group, allowing the selected SNET group member to directly access the device's messages, functional components, etc., some combination thereof and many more. Directing the device with the SNET group can include associating the account 608 with the SNET group, wherein the account includes accessing one or more aspects related to the device, functional components, and the like. For example, when a SNET group is associated with a local neighbor watch program, a user who is a member of account 608 can allow interaction between device 610 and the SNET group, thereby providing the information collected and generated by device 610 to the SNET group, providing Give some or all members of the SNET group and so on.

In some embodiments, a user associated with one or more devices 694, 610, 620, 630, one or more accounts 608, some combination thereof, etc., may authorize some or all of the SNET group 603 members and the device. Interact, thereby requesting the message of device 610, accessing one or more functional components associated with device 610, some combination thereof, and the like. For example, when the SNET group 603 is associated with a local neighbor watch program, the user can authorize the security device 610 to provide a message to the SNET group 603, including but not limited to video delivery, motion detection messages, and the like. In some embodiments, one or more members of the SNET group 603 can access, analyze, and interpret messages provided by the device to the SNET group 603. For example, when one or more devices 610 provide video delivery messages to the SNET group 603, the device, infrastructure, SNET group 603 members, some combination thereof, etc., can analyze the provided information to grasp the individual within the approximate location. Exercise, monitoring emergencies, some combination of them, and more.

In some embodiments, at runtime, in response to one or more events, the user can change the authorization of the device to interact with the SNET group 603. For example, SNET group 603 is associated with a local neighbor watch program, and account 608 is associated with the SNET group. When the user of the account receives an alert from a suspiciously active SNET group 603 in the vicinity, the authorized interaction of device 610 can be changed, so now authorized The device provides the message to the SNET group 603. The device was not previously authorized to provide a message to the SNET group 603. When the device 610 is a security camera, the live broadcast is provided to the SNET group 603 by the authorizing device 610, and the user can react to the alert so that members of the SNET group 603 can monitor the suspicious activity using video delivery. One or more members of the SNET group 603 can generate an alert notification in response to analyzing the infrastructure of the message generation notification provided by one or more devices, some combination thereof, and the like.

In some embodiments, the user can manage the interaction between the device and the SNET group 603 at runtime. For example, the user may be in the car environment 692 and receive event notifications including, but not limited to, child abduction. The notification may be received from the SNET 650 or through another communication path, and the notification may include information related to the vehicle of interest, including but not limited to license plate information, vehicle color, manufacturing, model, some combination thereof, etc., and social When the car device 694 includes a mechanism, functional components, etc. that can collect information about the surrounding environment, the user can join the SNET group 603 associated with the time and authorize the social car device 694 to interact with the SNET group 603 to be associated with the SNET group 603. One or more components can access the information provided by the social car device 694, one or more functional components associated with the social car device, some combination thereof, and the like. For example, when the social car device 694 includes an image capture device that can take a picture of a license plate for other cars on the road, the user-authorizable device 694 interacts with the SNET group 603 to provide a picture of the other license plate photographed by the device 694 to the SNET group 603, Used for other SNET group 603 members to view, analyze, and so on. In some embodiments, a user may authorize multiple devices to interact with the SNET group 603. For example, when one or more members of the SNET group 603 make a request, transmit a message from the social car device 694, at some other time interval, etc., the user can authorize the GPS device within the car environment to provide information related to the car environment 692. Location message. For example, when the social car device 694 including the camera within the car environment 692 captures a license plate image that matches the description associated with the SNET group 603, one or more members of the SNET group 603 can receive, request, and receive when the image is captured. Location information associated with the automotive environment 692, thereby providing one or more social car devices 694 in one or more automotive environments Matching license plate images allows SNET members to track cars with matching license plates.

In some embodiments, the user can generate a SNET group 603 for the device to interact with it at runtime. For example, when a user in an automotive environment receives a child abduction notification, the user may generate a SNET group 603 related to child abduction within the SNET 650 via one or more devices 606, 694, etc., and invite other members associated with the SNET 650, Non-members and the like join the generated SNET group 603. A user may authorize one or more devices to interact with SNET group 603, including but not limited to social car device 694, devices coupled to a social car device, home member device 606, some combination thereof, etc., to enable SNET group 603 One or more members analyze the information provided to the SNET group 603 to search, identify, and track individuals, vehicles, and the like associated with the child abduction alert.

In certain embodiments in accordance with the present disclosure, members of the SNET may wish to share images or other social media with family members, photographers, friends, designers, and the like. For example, a member can dine at a restaurant in Athens and take photos or videos through a social camera docked within a social sharing network. Such a sharing network may include SNET groups and subgroups, such as tour groups, European subgroups; Greek subgroups; Athens sub-subgroups; restaurant sub-subgroups. By joining such a restaurant subgroup, members can access restaurant reviews and messages and/or use previously captured media and provide members with similar contributions to others. Sharing information with others can be based on similar aspects. For example, other SNET users, SNET group members, etc. can access messages contained within a SNET subgroup, which is determined by one or more aspects of the SNET group members, including but not limited to device proximity supporting a SNET group member. A device that supports members of the SNET group that uploads messages, a member of a common SNET group, a combination of them, and so on.

In some embodiments, the social picture/video frame can be an outlet for displaying social content (eg, video). In addition to the actual dedicated frames, the associated SNET can be extended to software that supports the display of social content on televisions, computing devices, or any other social device, including social communication devices. SNET operation according to this embodiment The map may be further related to the map/location such that a set of photos of various social cameras within or outside the SNET group, along with metadata supporting future or existing trips (eg, GPS locations, map routes, etc.), are queued for display. For example, a member's social picture frame may have a map image through which SNET participants may enter a central point, a SNET group, a country, or an area. The SNET can then provide relevant transfers that can be changed periodically. Media delivery can be submitted for itself, its family, or globally. This image can also be a photo of people to introduce the infrastructure. For example, a member can see that someone is focusing on finding food and pressing a frame screen to get further information and may request an introduction.

In some embodiments, SNET is established to support game/gambling activities. For example, the SNET may include a continuous SNET or a temporary SNET group, and may purchase or transmit a game "credit" including, but not limited to, NFC support for the purchase. For example, the online game itself can be established and set up using a social device or the like.

In accordance with the present disclosure, various techniques (eg, techniques described elsewhere herein) can be used to determine the presence and location of SNET/SNET group members and their associated social devices. Such location information can be used in a variety of ways including, but not limited to, those described below. For example, the SNET location service may use one or more of the following criteria: GPS, LTE eNB, (IP) address, NFC (Near Field Communication), Bluetooth, WiFi, Infrared, etc., and account metadata. Cloud-based storage can be used for a variety of messages, including location (eg, GPS), to extend social networking functionality (eg, automatic SNET grouping/introduction, automated service/selection of peripherals, etc.). Location-based groups can also be formed for running, tracking, inviting (and timeout settings), and so on. In some embodiments, location profiles and other factors can also be used to select an online game competition/team. For example, an IP address can be selected in a manner similar to DNS for the associated domain name. In the course of the operation, a SNET/SNET group of game players and the like can be formed according to location factors, SNET/SNET group attributes, network attributes, some combination thereof, and the like.

Various embodiments of the SNET group in accordance with the present disclosure may include various social devices, device services, agents, and various types of soft participation as members of the SNET group. Application. Moreover, social devices and other types of SNET group members have related or specific characteristics and correlations that can form SNET groups with specific uses. For example, various embodiments may include SNET/group members, such as device manufacturers, vehicle owners, hospitals and medical providers, garages, insurance companies, and others that may be interested in communicating with human members and/or related SNET devices. Third party. This SNET/group can be a stand-alone or extension of another SNET/group.

Certain implementations of the SNET group in accordance with the present disclosure may include various social devices, device services, agents, and various types of software applications that participate as members of a SNET group. Moreover, social devices and other types of SNET group members have related or specific characteristics and correlations that can form SNET groups with specific uses. For example, various embodiments may include SNET/group members, such as device manufacturers, vehicle owners, hospitals and medical providers, garages, insurance companies, and others that may be interested in communicating with human members and/or related SNET devices. Third party. This SNET/group can be a stand-alone or extension of another SNET/group.

FIG. 7 illustrates an embodiment of an appliance social networking group/subgroup in accordance with the present disclosure. In this embodiment, the appliance group/subgroup 700 includes various (home) appliances/electronic devices ("social appliances" 702), which may include, but are not limited to, washing machines, dryers, refrigerators, televisions, STBs, thermostats, nets Road equipment and so on. Members within appliance group/subgroup 700 allow various interactions with or among such social appliances 702, including setup, configuration (generally as described above), testing, registration, firmware, and drivers. Updates, sharing, status updates including power consumption messages, power company integration, location messaging, social subgroup formation, rights management, and more.

This interaction includes communicating with various social devices 710 and family members 706 participating in the electrical group/subgroup 700, which facilitates such interaction through the SNET processing circuitry/software 704. In addition, personal (home) accounts 708 can also interact between individuals and nodes within appliance group/subgroup 700. Other network paths used by the cloud 712 communication channel or appliance group/subgroup 700 can also interact with authorized non-members.

Regarding certain expected social appliances 702, such as smoke detectors, carbon dioxide probes Detectors, alarm systems, and other security devices, automated SNET capabilities can be used to automatically make calls or notify family members or emergency response entities (firefighters, law enforcement officers, etc.) for the following detection of security incidents. Residents nearby can also receive such notifications.

When the new social appliance 702 joins the appliance/subgroup 700, the SNET processing circuitry/software 704 or similar functionality may determine the model/submodel of the appliance, the delivery software update, the configuration mode of operation, and the like. Moreover, the appliance can receive or provide profile information associated with other members of the appliance or appliance group/subgroup 700. Two-way communication with the appliance SNET group is possible via a power line/telephone line/cable device communication system (eg, via an internet path, a power company power line, or other specific communication path). Smart grid functions and interactions can also be performed through Zigbee, WiFi, NFC, LTE, IMT-Advanced/4G, and/or other applicable protocols.

FIG. 8 illustrates various embodiments of a vehicle SNET group/subgroup 806 in accordance with the present disclosure. The SNET group/subgroup 806 includes a vehicle 802 and may further include one or more additional vehicles 804, such as a shared or home vehicle. Various other devices, SNET sub-groups, service and content providers, providers, entities may participate in the vehicle SNET group/sub-group 806. In another embodiment, the vehicle SNET sub-group 800 itself may join another SNET group (eg, a vehicle owner or passenger SNET group).

More specifically, members within the vehicle SNET group/subgroup 806 may include a passenger SNET subgroup 806 that includes human members and associated entertainment devices 808, communication devices 810, computing devices 812, and additional social devices 814. Other participants may include, for example, payment processing services (for automatic payment of gas, service fees, vehicle services/inspections, drive-through restaurants, etc.), insurance company 818, emergency services/devices 820, vehicle manufacturers 822, and (based on Location Provider 824. The various nodes of the vehicle SNET group/subgroup 806 may include interfaces for communication over a cellular network, WAN or mobile hotspot 826, and the like. Various usage models include, for example, activation of SNET group nodes based on proximity, such as garage door openers, environmental controllers, and the like. In addition, insurance companies can participate in, for example, to view and verify driving behavior history/information and possibly low Estimate the relevant driving behavior history/information.

Vehicle 802 in accordance with the present disclosure may be a car, bus, train, industrial or agricultural vehicle, ship, or aircraft. Vehicle nodes/modules in accordance with the present disclosure may control particular components associated with various functions. Such on-board group nodes may include, for example, cameras and sensors, entertainment systems, environmental controllers, computing resources, steering and location functions, security systems, brakes and suspension systems, battery systems/fuel cell displays, emission control modules, performance/engines Control modules and more. A variety of such vehicle group nodes can be configured to communicate with one another.

At least partial communication between members and modules of the vehicle SNET group/sub-group 800 can be made via the in-vehicle network using standard protocols, such as a vehicle local area network (VAN) or controller area network (CAN). A variety of proprietary protocols have been developed and are currently used in vehicle communications, but it is expected that multiple such protocols will eventually be replaced by more common network technologies such as Ethernet and TCP/IP. Communication within the vehicle SNET group/subgroup 800 can use wireless communication technology and/or physical transmission media, such as single wire and twisted pair cable, fiber optic, power line communication (eg, through a charging station of a battery powered vehicle) Connect) and so on.

Figure 9 illustrates a process 900 by which a device can interact with a SNET group, directly or through another SNET group docked therewith, some combination thereof, etc., the device interfaces with the SNET group. As shown in block 902, process 900 can include device initialization. Initialization may include, but is not limited to, turning on, activating one or more functional components, and the like. As shown in block 904, process 900 can include detecting one or more networks. In some embodiments, the device can interact with various networks including, but not limited to, a wired LAN, a WLAN, a cellular network, some combination thereof, and the like. When the device is initialized, the network can be detected continuously, intermittently, at predetermined time intervals, some combination thereof, and the like. As shown in block 906, process 900 can include arranging the detected networks, infrastructure, and the like in an optimized order. Devices that have detected multiple networks may prioritize which network to use to interact with one or more SNETs, devices, some combination thereof, and the like. For example, the device can prioritize the WLAN network over the cellular network, thereby The device attempts to access one or more WLAN groups or other devices using the WLAN; when powering down or interrupting service through the WLAN, the device can switch to another network, such as a cellular network, to maintain or re-establish with SNET, one Or a connection of multiple devices or the like. The prioritization of the network can be done according to one or more rules, the device can store the rule, receive the rule from a remote source, and the like. For example, the device may prioritize the network according to internal rules; the rule may be replaced by an updated rule that receives updated rules over a network connection. Rules regarding which network to prioritize may include, but are not limited to, connection speed, security, the likelihood of a connection outage, the likelihood of a connection failure, some combination thereof, and the like.

As shown in block 908, process 900 can include accessing one or more SNETs, SNET infrastructure, SNET groups, devices, some combination thereof, and the like. The access is accomplished by one or more networks detected within block 904. In some embodiments, the device can find certain SNETs based on predetermined messages. For example, the device can have internal stored messages that, when connected to one or more networks, identify one or more particular SNETs that the device is looking for in order to join or establish an SNET associated with the device. The SNET list within the message can be arranged in an optimized order such that the device finds certain SNETs before other SNETs based on one or more rules. The SNET list can be modified over time depending on the interaction of the device with other devices, when receiving updates to remote locations, some combination thereof, and the like.

As shown in block 910, process 900 can include determining if the located SNET includes a predetermined SNET group. In some embodiments, the apparatus can include a message identifying one or more predetermined SNET groups that the device is looking for or joining. Such predetermined SNET groups may include, but are not limited to, SNET groups for similar devices, SNET groups for similar devices within a geographic area, some combination thereof, and the like. Similar devices may include, but are not limited to, devices associated with one or more similar aspects, functional components, features, capabilities, locations, etc., devices that are similarly related to a similar purpose, physical devices that can interact with the network, A combination and so on. For example, manufacturers of smoke detectors can interact with the network to maintain smoke detection for some or all of their manufacturing. The SNET group of the detector. Manufacturers can allow some or all of their smoke detectors by providing information to smoke detectors, including but not limited to SNET-related Uniform Resource Locator (URL) addresses, SNET group identifiers, some combination thereof, and so on. Find and join their SNET group. In another example, one or more SNET groups may serve various appliances that are physically located in certain different locations, which may include, but are not limited to, a kitchen, a room, a structure, a geographic location, one of them Combination and so on. The one or more appliances may have a message identifying the SNET group that the appliance is looking for based on the geographic location of the appliance.

As determined in block 912, upon determining to discover a predetermined SNET group, the device may request membership within the predetermined SNET group. Membership may include interfacing the device with a SNET group, interfacing a SNET group with a device that interfaces with a predetermined SNET group, some combination thereof, and the like. In some embodiments, the apparatus may request the SNET to add the device as a member of the SNET group, request an existing member of the SNET group to accept the device as a member of the SNET group, provide a password code for the membership of the SNET group, some combination thereof and many more. The cryptographic code can be stored internally by the device, received from another device, some combination thereof, and the like.

As shown within blocks 914-916, process 900 can include means for establishing a SNET group. The SNET group can be established in response to determining that there are no predetermined SNET groups, detecting one or more SNETs, some combination thereof, and the like. For example, in some embodiments, the device does not know any predetermined SNET groups and can create its own SNET group when interacting with the SNET over a network connection. As shown in block 914, the device may request the SNET to create a SNET group, create a SNET group itself, some combination thereof, etc., and may provide information about the SNET group, for example, the name required by the SNET group, the SNET group. Selected messages available to one or more selected members, rules related to interactions between members of the SNET group, some combination thereof, and the like. As shown in block 916, process 900 can include establishing a member of a SNET group. In some embodiments, the device may request that certain entities be added to the SNET group, including but not limited to another device associated with the device, a device supporting members of the SNET, and supporting SNET. Non-member devices, members of SNET, non-members of SNET, some combination thereof, and so on. For example, the home security device of the SNET group that established the device may request that residents of the home in which the security device is located be added to the SNET as well as local local police services, local security services, some combination thereof, and the like. When a non-member is added as a member of the SNET group, the device may request the SNET to send an invitation to join the group to the non-member, so that the non-member can become a formal member of the SNET group, a customer member of the SNET group, a certain combination thereof, etc. . Invited invitations are discussed in a pending US Utility Patent Application Serial No. 13/351,822 (Attorney Application No. BP23785), filed on January 17, 2012, entitled "Ad Hoc Social Networking" To SNET, the full text of the case is incorporated herein by reference.

In the processing shown in blocks 912 and 916, the device can establish a docking specification that controls the interaction between the device and one or more SNET groups, members of the SNET group, and the like. For example, when the device is a security device that interfaces with a predetermined SNET group, the device can establish a docking specification that restricts access by some or all of the other members of the predetermined SNET group that are not pre-authorized by the user of the security device. The docking specification may be created by the device, input that may be received by the SNET group based on a user associated with the device, input that may be received by the SNET group based on another member of the SNET group, internal logic, some combination thereof, and the like.

As shown in block 918, process 900 can include providing a message about the device to the SNET group. The message may be associated with one or more functional components of the device, one or more functional components of another device, contact information for the device or some other device, a notification, some combination thereof, and the like. For example, the security device can provide video transmission of the surveillance camera, local data on whether to occupy the local environment, data of the motion sensor, and the like. The device located in the car can provide information about the vehicle's current rate, speed, location, fuel consumption, diagnostic messages, some combination thereof, and the like.

The message is available to one or more selected members of the SNET group based on one or more rules, docking specifications, and the like. For example, a device in a car can provide diagnostic information to the SNET so that the diagnostic service can be obtained as a member of the SNET group. And the device can provide information about the current rate and location of the car so that only a selected member of the SNET group can obtain the information, including but not limited to the owner. In another example, the device can be authorized to only provide limited access to the data from the device by the SNET group, unless and until the user associated with the device changes the docking specification to allow access, the SNET group can be authorized from The device receives the data, accesses the device, requests the device, etc., as authorized by the docking specification that controls one or more links to the device.

Figure 10 illustrates a process 1000 in which at least some portion of a device interacts with one or more functions of a SNET group. The SNET group can be a group that the device has joined, established, directly docked, indirectly connected through one or more devices and SNET groups, and the like. As shown in block 1002, in some embodiments, the device is a device having one or more functional components. Functional components may include, but are not limited to, sensors that collect information about the environment, generate information about the environment, some combination thereof, and the like. The environment can be a particular environment adjacent to the sensor, some other device, a user-defined environment, some combination thereof, and the like. For example, the device can include a camera, a thermometer, a motion sensor, an air component detector, some combination thereof, and the like. The device can be communicatively coupled to one or more SNET groups via one or more networks.

As shown within block 1004, process 1000 can include receiving material. The data can be received at a portion of the device, including but not limited to processing circuitry of the device. The functional components of the device discussed in block 1002 can generate the material, receive the data from another separate device, and the like. This material can include the output of functional components. For example, the smoke detector device can receive information about the local environment, such as local air temperature and composition, from one or more functional components within the smoke detector. In another example, the security device can receive data including video transmissions from the surveillance camera, receive information from the motion detectors indicating whether the motion detectors detected motion, some combination thereof, and the like.

As shown in block 1006, process 1000 can include analyzing the received data to determine if a trigger threshold is exceeded. The device can be compared to a stored set of rules, The data is analyzed to determine if one or more thresholds are exceeded, the data is analyzed against a set of rules received simultaneously from one or more functional components within or outside the device, and the like. The functional component can be analyzed and another portion of the device notified when the functional data exceeds one or more thresholds. In some embodiments, the trigger threshold is associated with a functional component. For example, a portion of the smoke detector can analyze the data of the functional components of the smoke detector to determine if there is smoke in the local environment; the portion of the smoke detector can analyze the air constituent data to determine the presence of smoke, at least some The air component indicates the presence of smoke. In another example, a device within a car can analyze data relating to vehicle speed to determine if a threshold speed is exceeded or the like.

As shown within blocks 1008 and 1010, process 1000 can include transmitting data to a SNET group, transmitting a message to select one or more devices, a user supported by the device, and the like, when the threshold is exceeded. A SNET group may include SNET groups associated with one or more devices, a local geographic area, one or more SNET users, some combination thereof, and the like. For example, when determining that smoke is present in the local environment, the smoke detector can send data to a SNET group associated with a smoke detector within a geographic area. The information sent to the SNET group may include notification that a smoke detector at a location has detected smoke and functional information of one or more functional components of the smoke detector, such as air composition data. One or more selected members of the SNET group may obtain some or all of the transmitted material, send the information directly to the selected SNET member as a notification or with the notification, and send the data to other nearby devices. The device is also a member of the SNET group, a non-member of the SNET group, some combination thereof, and the like. For example, all members of the SNET group may receive a smoke detection notification sent by a smoke detector to a SNET group associated with the smoke detector, which may send a smoke detection notification to a member of the SNET group, which is a local fire station, emergency The dispatcher, the owner of the building where the smoke detector is located, a certain combination, etc. The notification may include information from a smoke detector, another nearby device, and the like. In another example, the security device can receive and determine the overtouch The motion detection notification of the threshold is sent to the SNET associated with the security device, and the security device is served by the specific security company, thereby transmitting a notification exceeding the trigger threshold to the security company, the local emergency dispatcher, and the resident of the building where the security device is located. , some combination of it, and so on.

As shown within block 1012, process 1000 can include receiving control inputs from one or more members, applications, services, and the like associated with the SNET group. In some embodiments, a member of the SNET group can access one or more components of the device such that a member of the SNET group can request information about the device, interact with the device, interact with the individual device through the device, some combination thereof and many more. The first time a member of the SNET group receives a notification, signal, etc. from the device, the interaction can be adjusted by docking specifications and the like. For example, the smoke detector device detects smoke in the air and sends a smoke detection notification to the SNET group such that one or more members of the SNET group receive one or more of the SNET groups when the smoke detector has received a notification that the smoke detector has detected the smoke. Members can respond to this notification by interacting with the smoke detector. Such interactions may include, but are not limited to, requesting additional material from one or more functional components of the device or another device, accessing one or more functional components of the device or another device, some combination thereof, and the like. Wait. For example, by requesting local temperature data from a smoke detector, another device adjacent to the smoke detector, etc., the local emergency dispatcher can respond to the notification that the smoke detector has detected the smoke. The dispatcher can request a live broadcast of the nearest surveillance camera to search for smoke evidence. In another example, by accessing the nearest surveillance camera, the emergency dispatcher can respond to the notification that the surveillance camera has received motion detection to find the source of the motion detection.

As shown in blocks 1014 and 1016, when the input is at least some portion of a device for receiving the input, process 1000 includes at least some portion of the device implementing the received input. This embodiment may include a portion of the device transmitting commands, signals, messages, and the like to another portion of the device. This embodiment may include converting a command received from a member of the SNET group into one or more separate components of the device that are solvable A command issued or executed.

As shown in block 1020, process 1000 can include responding to a decision that by establishing membership of another device within one or more SNET groups, input from a member of the SNET group includes a signal for another device The one or more SNET groups may include the same SNET group to which the SNET group members belong. Such membership, relevance, docking links, etc. may be temporary, time-limited, and may be revoked by the device, the SNET, one or more SNET group members, some combination thereof, and the like. Such membership of the external device can allow one or more members of the SNET group to access data, functional components, and the like associated with the external device. Access is made by means of the device that initially received the input in block 1012 or through another path. For example, by requesting access to a surveillance camera adjacent to a smoke detector that detects smoke, a member of the SNET group can respond to a notification of smoke detection at a location. The access request can be sent directly to the surveillance camera, some combination thereof, etc. via a smoke detector. By establishing temporary membership by a surveillance camera within the SNET group, the smoke detector can respond to the request so that the surveillance camera can provide information from one or more members of the SNET group and can access the surveillance camera . As shown within blocks 1024-326, process 1000 can include transmitting input to and receiving data from an external device. This input can be transferred to an external device based on the functional components of the external device. For example, when an air temperature request is received from a SNET group member, the smoke detector can send the request to the nearest thermometer. A request from a member of the SNET group may explicitly request temperature data for the thermometer; the request may also be a request for temperature data for any recent device, wherein the smoke detector sends the request to one or more of the most recent thermometers. The request may also be translated as necessary to be interpreted, executed, etc. by one or more components of one or more separate devices. For example, a smoke detector can convert a general request for temperature data into a command signal for a thermometer to provide temperature data. As shown in block 1026, material from one or more external devices can be received by the device transmitting the input. The received data can be forwarded to the SNET group, which can be used by the device alone or in combination with one or more other functions Capability components for analysis, some combination thereof, and so on. This data can be transferred directly to one or more SNET groups and bypassed by the device. For example, when a smoke detector has established a temporary SNET group membership for a thermometer, the thermometer can send temperature data directly to the SNET group without sending data through the smoke detector. It is also possible to send data through a smoke detector without requiring the smoke detector to analyze the temperature data. When the thermometer does not have SNET group membership, the thermometer can send the temperature to the smoke detector, which can send the data to the SNET group members for access by one or more SNET group members, and analyze the temperature data in combination with other data. , some combination of it, and so on.

FIG. 11 illustrates a process 1150 that may be performed by a device having functional components, as shown in block 1152. In some embodiments, the device is capable of interacting with the SNET over one or more network connections, the user of the device authorizing the device. As shown in block 1154, the process 1150 can include receiving rules regarding interaction with the SNET group. The rules may include rules for interacting with one or more SNET groups, docking specifications for controlling the docking links of the SNET group, some combination thereof, and the like. Through the interface of the device, through the signal of another device supporting the user, the signal through the remote control device on the network, from the input of the user of the device, from the SNET group, from one or more functions of the SNET group, And receiving the rule from the SNET infrastructure, the SNET system, the SNET, some combination thereof, and the like. This rule may limit or allow different levels of interaction between the device and one or more SNET groups within the SNET group. For example, the rule may restrict the device from providing any message to any SNET, one or more SNET groups, and the like. This rule may also allow for limited messaging between the device and the SNET, SNET group, and the like. This rule allows for interaction between one or more functional components of the device and some or all of the SNETs, SNET groups, one or more components of the SNET group, some combination thereof, and the like.

As shown in block 1156, the process 1150 can include determining if the interaction rule permits interaction between the device and the SNET. The interaction can include interacting with some or all of the one or more SNET groups. If the interaction is allowed, then processing 1150 can include determining whether to permit the device to provide data to one or more SNETs, SNET groups, SNET group members, SNET group non-members, some combination thereof, and the like, as shown in block 1158. As shown in block 1160, if the device is allowed to provide data to one or more SNETs, SNET groups, SNET group members, SNET group non-members, some combination thereof, etc., the device can be provided as permitted data. As shown in block 1160, the received interaction rules determine that providing the material can include providing the material from one or more functional components to some or all of the one or more SNET groups. For example, the device includes a camera, and when the received interaction rules permit the device to provide a picture taken by the camera to the selected SNET group, the device can provide the data to the SNET group.

As shown in block 1162, the received SNET interaction rules determine that the process 1150 can include functional access to one or more SNETs, SNET groups, SNET group members, SNET group non-members, some combination thereof, and the like. Functional access may include, but is not limited to, accessing one or more functional components associated with the device. For example, when the device is located within a car, the functional components associated with the device may include, but are not limited to, a digital camera device, a GPS positioning device, and the like. If access is permitted, as shown in blocks 1164-366, the device receives the function command and performs the command function. For example, the device includes a camera, and when the received interaction rules permit a member of the SNET group to make a functional access, the device can direct the camera to take a picture when requested by the SNET group member.

In some embodiments, the received interaction rules may permit access to a selected portion of the SNET, SNET group, SNET group member, network user, some combination thereof, etc., to access a function. For example, an interaction rule may permit only certain members (including but not limited to local offices) to access functions associated with the device. As shown in block 1168, the process 1150 can include monitoring any changes that occur within the interaction rules. When receiving a new interaction rule instead of the originally received interaction rule, when receiving the update of the interaction rule, when the authorized user crosses the interaction rule, authorizing the user to update or change the interaction rule, a certain combination thereof, etc. This change can occur.

Figure 12 illustrates a process 1270 in which a processing system, a server device, a remote control device, a network node, an SNET infrastructure, a SNET system, an SNET, some combination thereof, etc., can perform the process. In some embodiments, the processing system supports some or all aspects of the SNET, including but not limited to storing messages provided to the SNET, one or more SNET groups, etc., from one or more SNET members, non-members, etc. Receive interaction rules, docking specifications, etc., establish docking specifications, manage docking specifications, SNET members, SNET non-members, devices, one or more functional components related to the device, messages provided to the SNET, some combination thereof Promote interaction between and so on. For example, the processing system may allow a user to set interaction rules that determine that other SNET members may access user-related messages, interactions, device functions, etc., and such SNET members may implement such access and the like.

As described in block 1274, the process 1270 can include setting interaction rules, docking specifications, some combination thereof, etc., for one or more SNET groups, SNET infrastructure, etc. and related to users, SNET infrastructure, and the like. A link between one or more accounts, SNET groups, devices, and the like. The user may be a member of the SNET, a member of one or more SNET groups, a non-member of the SNET accessing the SNET as a guest, a certain combination thereof, and the like. The docking specification may be partially or completely set by one or more processing systems, users, accounts associated with the user, devices supporting the user, SNET groups, some combination thereof, and the like. For example, a SNET member that is a member of the SNET group of the neighbor watcher can set the docking specification of the boot processing system to allow security devices associated with the SNET member's account to provide messages such as video delivery to the SNET group, but will be Access is restricted to only selected members of the SNET group, such as neighbors of SNET members, trusted friends, and so on. In some embodiments, the docking specifications may be changed, updated, or changed at any time by the user, by the SNET member, by the processing system, according to predetermined rules, according to some internal logic, some combination thereof, and the like. For example, a SNET member may provide, as one or more docking specifications, one or more trigger events, including but not limited to alert notifications, emergencies, interference, etc., when a certain one or more trigger events are detected somewhere in the vicinity of the SNET member's residence. Etc., for accounts with SNET members Access to messages provided by the user-related device can be extended to some or all members of the SNET group.

As described in block 1276, the process 1270 can include receiving material from the device. The data can be received and guided by the account docking specification received by the processing system. For example, the docking specification may allow the processing system to accept motion detection messages associated with one or more devices that are associated with the SNET member's account, but may limit the processing system's access to any device associated with the SNET member's account. Video transmission data. As described in blocks 1278-1280, process 1270 can include determining whether to grant access to material received from the device, and allowing access to the material if the access is permitted. One or more docking specifications associated with the SNET user's account may direct such a decision, the device being associated with the SNET user. Access may include, but is not limited to, partial or full access to some or all of the selected one or more SNET group members, non-members, and the like. For example, when one or more docking specifications only allow a certain selection of SNET group members to access data, the processing system only allows those selected SNET group members to access the material. In some embodiments, access is subject to additional restrictions. For example, some or all of the received docking specifications may limit any allowed SNET group members from accessing the received data for no more than a predetermined amount of time.

As described in block 1282, the process 1270 can include performing data monitoring, analysis, processing, some combination thereof, and the like on the received data. In some embodiments, the processing system processes data received from a plurality of SNET members, non-members, member-related devices, non-member related devices, some combination thereof, etc., in order to determine trends, master events, etc. . For example, the processing system has established a SNET group associated with one or more child abductions, and one or more SNET group members have set docking specifications that permit the processing system to receive from one or more devices associated with the SNET group members Data, SNET group members include, but are not limited to, camera devices, GPS location devices, some combination thereof, etc., at this time, the processing system can store, process, analyze and interact with the received data to track people, vehicles, etc. Wait. As described in block 1284, the process 1270 can include transmitting a data analysis. In some embodiments, the processing system has identified trends, people, vehicles, items, some combination thereof, etc. by interacting with the received material, and the processing system responds to the identification by sending a notification. The notification can be sent to one or more SNET group members, one or more non-members, and the like. For example, when the processing system processes the received data to identify an interest vehicle in an abduction event, track an interest vehicle, some combination thereof, etc., the processing system can send a notification to a local authorization service, including but not limited to an emergency dispatcher . The notification may include some or all of the received data, analytical data, and the like. The notification may also include an invitation to join the SNET group and access some or all of the information provided to the SNET group.

As described in blocks 1286-1288, process 1270 can include determining whether to authorize one or more SNET group members, non-members, processing systems, etc. to access some or all portions of the device. The device can be associated with an account of a SNET member, a non-member, and the like. Accessing may include accessing one or more functional components associated with the device. Authorization to access some or all portions of the device may be determined by one or more received docking specifications. For example, the processing system may determine to permit one or more SNET members to obtain GPS location information associated with supporting another SNET group member. The processing system can route communications between one or more SNET members and devices when one or more docking specifications allow access to GPS location information. The server can also provide messages to one or more SNET members, thereby enabling these members to access the device independently of the processing system.

As described in block 1290, the process 1270 can include determining if the docking specification has been changed. These docking specifications can be changed, updated, changed, and rewritten using partial or complete replacement of these docking specifications. One or more SNET members, SNET non-members, SNET group members, SNET group non-members, processing systems, one or more devices associated with one or more SNET accounts, some combination thereof, etc. may change the docking specifications.

Referring now to Figure 13, a social network circle/group 1300 including social devices 1302 (hereinafter referred to as "social network group", "social network circle", "SNET" is shown. Circles, "SNET Groups, etc." In addition to common social networking features and services, SNET Group 1300 and related social devices 1302 in accordance with various embodiments include a number of new features and attributes, generally referred to below. The figure is more fully described.

In short, membership within the SNET group 1300 can include docked social devices 1302, with other members of the SNET group 1300 and SNET group human members 1304 and their agents accessible resources. Moreover, the SNET Group 1300 node can include device services and various software (eg, applications) that participate as members. By way of example, SNET group members may include artificial intelligence agents/social robots 1306, SNET security devices 1308, appliances, vehicles and service providers 1310, other SNET groups 1312 shared or authorized members/functions, and the like. Moreover, the additional SNET 1314 can collectively access specific content and resources of the SNET Group 1300, including remote or web-based applications. This access can be adjusted based on acceptable archiving and correlation data. Likewise, social devices, SNET groups, individuals, etc. may be allowed to become temporary or temporary members, with or without restrictive access.

In the illustrated embodiment, one or more SNET processing systems and software 1316 form, maintain, and operate SNET group 1300. Processing systems may include, but are not limited to, one or more instances of standalone SNET processing circuitry, one or more instances of distributed SNET processing circuitry located on one or more devices, social devices, server devices, network nodes, etc. Wait. It is noted that "SNET processing circuitry" may include hardware, software, applications, or various combinations thereof, and may be configured to support the various functions disclosed herein. Moreover, SNET processing circuitry 1316 can be included in separate servers, server farms, cloud-based resources, and/or various devices described below, and includes authentication and security functions 1318. Moreover, according to various embodiments, SNET may also use dedicated middleware, including standard middleware (or standard communication protocols) with associated authentication processing. As described more fully below, the interactions and correlations within the SNET group 1300 can include one or more adaptive resource management, distribution and arbitration modules 1320, a social device association/control module 1322, and a SNET group member overview module 1324. .

According to various embodiments, the distribution of internal and external SNET content/media 1326 can be accomplished in a variety of ways. 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. SNET content/media 1326 may include, for example, various user-driven (advertising) channels, pictures, videos, links, online text, and the like. Such content, communication with the social device 1302 of the SNET group 1300, and remote access to the social device are available through the Internet backbone 1328, cellular communication system, WAN, LAN, and the like.

In accordance with various embodiments, such as the embodiments disclosed herein, members of the SNET may establish rights and/or privacy settings, control and restrict access to profile information, connections and groups of people or objects, and define the required Access level. Permissions allow users to keep certain messages private or available only on a licensed basis. For example, the visibility of a particular user message may be limited to users/devices within the SNET. Alternatively, a specific user message can be publicly used. Similarly, SNET members can selectively decide to allow others to access personal information, such as name, gender, contact information/email address, and so on.

14 is a functional block diagram showing a social networking (SNET) infrastructure 1400 and (member) social device 1401 in accordance with various embodiments. Communication between the social networking infrastructure 1400 and the social device 1401 and other SNET members can be through one or more wired or wireless communication networks 1403. The SNET infrastructure 1400 and social device 1401 are coupled to the communication network 1403 via communication interfaces 1431 and 1411, respectively, and each of the communication interfaces can support communication with a single SNET member, a group of SNET members, or various SNET members.

The SNET infrastructure 1401 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 1433 receives messages from SNET/group/member reporting function 1413 within associated social device 1400. Such a message may include, for example, status data 1415 related to the location, address, and activity of the social device 1400 and/or device user.

Additionally, the social device 1400 can provide a device message 1416 indicating, for example, device functionality And social functions, device models, device configurations, software versions, connected peripheral and downstream (social) devices, device resources and uses, and the like. The SNET infrastructure 1401 can use device information 1416 regarding the available resources and the use of existing resources for SNET resource management, including dynamic resource allocation and arbitration.

In various implementations, social device 1400 is obligated to accumulate, store, and/or report device status/message 1415/1016 at different times. For example, reporting is required when associated with or docked with SNET, periodically, and/or in conjunction with operations and resources and devices (including upstream and downstream devices) within and between other SNETs.

Referring again to the SNET infrastructure 1401, additional functionality and resources include, but are not limited to, SNET component message capture and storage management 1434; SNET application programming interface (API) 1435 that allows SNET-related software components to communicate with each other; for maintaining SNET and Access control management and security 1437; and (network) server service 1438 for the integrity of the ancillary data/resources. The social networking infrastructure 1401 further includes other group application services 1405 that correspond to the above and additional services, such as the services described herein. In an exemplary embodiment, SNET infrastructure 1401 may determine the category and nature of social device 1400 that wishes to participate in the SNET (eg, via device message 1416). If desired, the functionality of the SNET infrastructure 1401 can then direct or trigger the installation of appropriate application software and underlying drivers within the social device 1400. This can be done when at least the inherent functionality of the social device 1400 is involved.

In the illustrated embodiment, social device 1400 includes a plurality of additional social device resources 1418 (including, for example, the social resources described in Figures 15 and 17 and device status/message 1415/1016) as well as functions and resources to support participation. Social network. More specifically, SNET, SNET, and/or member control functions 1417 can include slave functions 1419, main functions 1420, and various combinations thereof. Dependent functions 1419 include, for example, setup configurations, guided resource configurations, managed resource arbitration, bridging operations, and the like. The primary function 1420 can allow the social device 1400 to establish, manage, and terminate interactions between nodes or groups of nodes within the social network, including those involving the social device 1400 itself. Interaction.

The social device 1400 further includes a social API 1421 and a browser-based interactive function 1425 to support, for example, related social applications and services 1423 (which may include dependent and primary functions 1419 and 1420). Access control (including access views provided to other SNET group members) and secure layer 1427 allow social device 1400 to engage or establish a SNET group/circle with a secure SNET group/circle, and control access to internal and external SNET resources, The following is a more complete description.

It is noted that the plurality of functional components of the embodiment depicted in Figure 14 may be wholly or partially contained within one or more (dedicated) integrated circuit devices. For example, an integrated circuit device can include a member reporting module to provide member reporting functions (including communication of device status and status features), device control functions, master/slave functions, security and access control modules, and the like. Such integrated circuit devices may also include on-board processing functions and/or interface with processor devices. Alternatively, several of the above functions may be wholly or partially contained within a software loaded on the operating system and/or operating system core.

Referring now to Figure 15, a schematic block diagram of a social device 1501 is shown that is operable to support various resource access interactions with other social devices and social systems in accordance with various embodiments. The social device 1501 is configured with various functions that enable the device to operate within a social device "hierarchy", including social (S) devices, social "parent" (SP) devices, and social "child" (SC) devices. For example, the social parent device can allow the docked social child device to access the resources of the parent device and/or connect to the social network and interact (directly or indirectly) with the social network. The social sub-device can be configured with inherent social functionality, or access this functionality from within or through the associated parent device. Moreover, SNET human members may have associated social sub-devices or be provisioned by the social parent device through the user I/O interface (1123).

The social device 1501 in accordance with various embodiments and applications may also be used simultaneously or selectively as a social device, SP device, SC device, or even a "grandparent" device that supports (eg, in a multi-hop environment) SNET group Mother device inside. The movement between the SP and the SC device can be established in an optional, automatic or automated manner State or static hierarchical correlation. Moreover, the social device 1501 can take many forms including, but not limited to, a smart phone, a personal computer, a server, a tablet, an access point, a gateway, a network switch/hub, a bridge, a set top box, or enabled via social functions. Other devices.

In the illustrated embodiment, social device 1501 is communicatively coupled to SNET infrastructure 1509 and/or social mother system 1511 via uplink social communication interface circuitry 1507. Likewise, the downlink social peer-to-peer and/or sub-communication interface circuit 1513 can be coupled to the social child device 1515, the social peer device 1517, and/or the social mother system (device) 1519. Through the social device 1501, the social resources of the upstream and downstream devices are accessible to each other.

The social device 1501 of this embodiment includes a social resource 1503 that is managed by the social resource management module 1505 along with external SNET resources and is obtainable by at least one other SNET group member. Specific social resources 1503 may include user I/O interface 1523, general purpose and special purpose hardware processing circuitry 1524, peripheral circuitry and components 1525 (which may or may not have social functionality), communication bandwidth and credit determination functionality 1526, handover/bridge functionality 1527 The application software and services 1528, the remote social resources 1529 of the SNET group, the external social resources 1531 controlled by the social device 1501, and the like. External social resources 1531 may include, for example, external media/digital libraries, or content of one or more circuits, satellites, and/or terrestrial television systems.

Among other functions, the social resource management module 1505 also includes access, assignment, arbitration, and scheduling functions 1521 and functions for establishing, reacquiring, and abandoning control processing operations 1522, including operations involving accessing social resources 1503. It is to be noted that the SNET infrastructure 1509 and/or other SNET nodes may have corresponding social resource management functions.

In an exemplary embodiment, where social device 1501 includes an exchange bridge, access, allocation, arbitration, and scheduling functions 1521 can dynamically allocate bandwidth capacity. Upon request, each access view or each allocation and arbitration function can access the bandwidth capacity and other resources of the social device 1501 and consume or require excessive bandwidth/resources The access can be selectively terminated.

16 is a schematic block diagram illustrating accessing social resources of SNET group 1606 in accordance with various embodiments. In some embodiments, members of a social networking group ("SNET Group") control different access levels of personal messages (which may be included in the user profile) and related device profiles and functions. Such access rights allow members to establish selective, restrictive, and/or hierarchical access and views to all or some of the member social devices and resources for other members of the social/group and non-members.

In the illustrated embodiment, members or devices of SNET group 1604/1606 (or separate entities) access social device/group resources 1610 associated with SNET group 1606 through resource management node 1600. The resource management node 1600 includes an access right 1601, an access view 1602, a dynamic (re)allocation function 1603, an arbitration function 1604, and a security function 1605.

In operation, access rights 1601 and access views 1602 control different access levels and access visibility for member personal messages, device messages, profiles, processing and storage functions, and other social resources. For example, access rights 1601 and access views 1602 may be predefined based on the SNET group, according to the cooperating member device, or interacting with the device based on the member's own device. This pre-definition can be modified dynamically as needed or as a function of relationship. Access rights 1601 can also be extended to support temporary interaction with customer members or guest devices. For example, an access member carrying a smart phone may be allowed to receive/provide media to social devices within the "family group."

In some embodiments, members of SNET group 1606 can adjust and modify access rights 1601 on a message-by-message, device-by-member basis, member by member basis. By accessing view 1602, members can also display themselves in different ways depending on the context, location, or usage-based considerations. For example, a member icon/avatar may display different features or functions that depend on the background, including work, home, or social settings. Dynamic (re)allocation function 1603 and arbitration function 1604 allocate social resources and dynamically reassign social resources as necessary. The security function 1605 can be pre-prepared to access social resources on secure access/verification.

In addition to the social device/group resource 1610, the SNET group 1606 can include, for example, the SNET server 1612 and one or more members 1614 and associated social devices, services, applications, files, web pages, connections, and other social resources. It will be appreciated that member 1614 may include, but is not limited to, human members, device members, etc., and may selectively or hierarchically access the personal information and associated social device data and other resources described above. In some embodiments, resource management node 1600 can be included within SNET server 1612 or other SNET social devices, or can be managed by the SNET host infrastructure in an independent manner, distributed manner, and the like. Moreover, SNET server 1612 can include a firewall that is operable to provide secure access and perform basic routing functions.

The nodes of the SNET group 1613 can access the social device/circle resources 1610 in different ways, including through the user interface (UI) 1618 used by one or more humans 1611. The UI 1618 may include a graphical user interface (GUI) or browser that graphically indicates available resources, voice controls, gesture commands, and the like. The proxy server 1620 can also manage access to the SNET group 1606. The proxy server 1620 acts as an intermediary for proxy client 1622 access requests - including social devices connected to the proxy server 1620 via the Internet or other IP-based network - attempting to communicate with the SNET group 1606. The social device 1624 associated with the SNET 1613 is capable of interacting directly with the SNET group 1606. It is noted that human member 1616, proxy server 1614, and social device 1624 can operate independently of the SNET group/subgroup. Moreover, proxy server 1614 can be a distributed or cloud-based entity, or a member of SNET group/subgroup 1613 or SNET group 1606 (or included within its members).

17 is a schematic block diagram of a social device/server 1700 that uses a communication and control protocol 1702 that is capable of performing various SNET resources and control operations in accordance with various embodiments. In the illustrated embodiment, communication and control protocol 1702 includes protocol configuration 1704, SNET resource (automatic) control function 1706, device type/function specific control 1708, security and authentication function 1710, SNET docking/member control 1712, and SNET. Transport/network layer 1714. Various packaging and packaging techniques are available Send and receive control signals and data.

In one embodiment, the social device/server 1700 includes an intermediation layer or client driver 1716 capable of communicating with a central SNET management node, an SNET infrastructure, one or more processing systems, SNET members, and other compatible devices, including Social devices that do not fully support the SNET group communication protocol, some combination thereof, and so on. The mediation layer or client driver 1716 can be installed via a SNET node or local storage, or can be downloaded from a manufacturer's website or a cloud-based resource. This installation can be automated when powering up or activating social device/server 1700 or as shown by other SNET nodes.

The central management node of the SNET group or SNET host infrastructure can manage and access SNET resources using the communication and control protocol 1702. The central management node may include integrated artificial intelligence and/or may display itself through a "personality mask" or "avatar." In addition, distributed and delegated control mechanisms, including self-organizing or remote operations across one or more SNETs, allow one member to interact with its own or another member's social device via a SNET or SNET defined path.

In some embodiments, a standard version of the Communication and Control Protocol 1702 (referred to herein simply as the "SNET 1.0" standard) is used to facilitate such SNET interactions (and may not be within a compatible social device that has defined features of the device type) Need a mediation layer). Various control operations according to the SNET 1.0 standard may include automatic and temporary SNET group dependencies, as well as support functions such as automatic SNET resource provisioning, automatic device registration and configuration, upgrade and update maintenance, device-to-device communication session management, Tunneling/encapsulation functions, proxy services, social resource allocation, and more. For example, by docking an affiliated social device within a SNET group, a member wishes to access and control their own remote docking device and other members' remote docking devices either directly or through another user device. In some embodiments, this interaction can be facilitated by SNET 1.0 compatible methods.

SNET 1.0 compliant devices may be referred to as, for example, "SNET 1.0 Authentication" and may provide a specific device family-specific system-on-a-chip ("SoC")/hardware and software support. By way of example, SNET 1.0 certified NAS can have storage-related and defined control functions, including the default access layer definitions, security and DRM functions described herein. This control function, for example, with SNET 1.0 certified STB (depending on the setup program, can have multiple tuners/pipes for transmitting video streams with certain tuners/pipes, these tuners/pipes are used by the device owner) . The social device can be configured manually or through factory level settings and security to delegate members to control the SNET (1.0) group/server for other applications described below.

FIG. 18 illustrates various implementations of social device members and accessibility within a social networking group/sub-group, in accordance with various embodiments of the present disclosure. In some embodiments, membership within the SNET group 1810 can be expanded to include both public and private social devices and devices. For example, within a SNET group 1810 that includes human members 1806/1808, each human member can have individual SNET sub-groups 1800 (a) that can participate in the associated or docked social devices 1806/1808 of the SNET group 1810, either individually or in aggregate. ) / 1800 (b). Human members 1806/1808 and/or other SNET group/subgroup members can access SNET subgroups locally or remotely by various methods, such as clicking on icons or tags associated with human members/personal subgroups.

Although the SNET subgroups 1800(a) and 1800(b) are illustrated as separate subgroups, the subgroups may instead include a single SNET group or subgroup, or any number of additional SNET groups, SNET subgroups, etc., Various combinations of social devices 1802/1804 can be included. Moreover, the SNET processing circuitry and software 1812 of the described embodiment manages the formation and operation of the SNET group 1810. SNET processing circuitry and software 1812 may be included in standalone servers, social devices, and/or cloud-based resources. The SNET group 1810 can be persistent or have a limited duration and include self-organizing and/or static correlation.

The social device 1802/1804 can be broadly divided into (i) a social device 1802, including a user or SNET group interface, sufficient to provide an intended input to the SNET interaction, (ii) a social device 1804, supporting minimal user input or not. Support for user input, which is related to SNET interaction, some combination thereof, and the like. More specifically And without limitation, the first category may include computers, tablets, IPTV, IPTV set top boxes, smart phones, servers, laptops, cloud books, internet connection storage devices, game consoles, media players/sources , communication nodes (access points, routers, switches, gateways, etc.), user interface devices, power line communication (PLC) devices, and more. This social device can receive user input for SNET setup and management. The second category may also include, without limitation, printers, projectors, cameras and cameras, scanners, speakers, earphones, smoke detectors, alarm systems, cameras, mice, and the like. In general, dockable social devices include any electronic device that is operatively coupled to or docked within a SNET group/subgroup via a wired or wireless path for participation as a SNET member.

It is to be understood that by docking the social device, members of the SNET group 1810 can obtain full or partial remote control and interaction through the authorized member SNET account. For example, a family member authorized to participate in a "family" SNET group can remotely access a docked social device through one or more related SNET accounts. Various embodiments of docking and accessing social devices are described more fully below (e.g., in conjunction with Figures 19 and 20).

19 is a schematic block diagram illustrating remote access to social resources of a social networking group/subgroup in accordance with various embodiments. In the illustrated embodiment, social device 1900 can represent the need to associate, dock, access social device resources and other group resources 1918, or communicate with (secure) SNET group/subgroup 1902. The social device 1900 can be autonomous and independent, or can be a participant of other networks provided by the second SNET group 1904 or the SNET gateway 1906.

In one embodiment, SNET gateway 1906 or SNET group gateway 1908 acts as a proxy for social device 1900. A software application or computer system (server) acting as an intermediary can provide proxy functionality within the SNET gateway 1906 to seek resources from other servers or gateways (eg, SNET gateway 1908) (including The connected social device) makes the request. Such requests may include files, services, web pages, connections, profiling messages, and other available social device resources and other group resources 1918.

The SNET gateway 1906 can evaluate the request of the social device based on various filtering rules. For example, SNET gateway 1906 can filter traffic by IP address or protocol. Once the request of the social device 1900 is confirmed (if necessary), the SNET gateway 1906 is connected to the SNET group gateway 1908 via a WLAN/LAN or other communication path and requests access to the SNET group/subgroup 1902 on behalf of the social device 1900. resource of.

The membership within the SNET group/subgroup 1902 is established by the SNET processing circuitry and the docking module 1910 of the software 1912, which can support one or more device discovery and configuration protocols, including standard protocols. When restricting group membership, authentication can be provided using a local or cloud-based registrar 1914. The registrar 1914 of the described embodiment can use an administrator or directory service 1916, for example, a Lightweight Directory Access Protocol (LDPA) based directory service that stores attribute data. LDPA is a known application protocol for querying and modifying entries within a directory service. When interfacing with an IP-based SNET group, the social device can transmit the file material to the local domain using a textual material format (eg, Extensible Markup Language (XML)).

20 is a schematic block diagram of an embodiment of a social device 2000 that includes an overall social resource access and assignment management function in accordance with various embodiments. The social device 2000 can be used as a member of the SNET, a guest member, and/or an authorized visitor. The (predetermined or user defined) access and assignment management function 2004 controls access and distribution of the social resources 2002 of the social device 2000, the functionality of which can be used for membership nodes within and between SNETs as well as social resources 2002 and non-affiliated Interaction between entities. Moreover, the access and distribution management function 2004 can be distributed between one or more social devices/SNET host infrastructures.

The access and assignment management function 2004 includes access rights 2006, access control functions 2008, arbitration and dynamic (re)allocation 2010, and access view control 2012. Exemplary operations of such functionality are described in conjunction with various other figures herein. For example, a request to access social resource 2002 may be provided through a browser and/or downloaded or pre-installed application 2014. In some embodiments, based on authentication or security operations 2016, restricted access to social resources 2002. In addition, various functional modules of social device 2000 can be included in one or more integrated circuit devices that can be dedicated to supporting primary users and/or shared access operations.

21 is a schematic block diagram of an embodiment of a social device 2100 that includes an overall function that is operable to support social network groups/subgroup members and communications in accordance with various embodiments of the present disclosure. In the illustrated embodiment, the communication interface and transceiver circuitry 2102 is operable to perform wired or wireless communication between the social device 2100 and the SNET/SNET group/SNET sub-group 2126 over one or more communication channels. Depending on the functionality and configuration of the social device 2100, communication with the SNET can be one-way or two-way/interactive, and use proprietary or standard communication protocols. Communications may include, for example, device profile messages, user and SNET group profile messages, control signals, media content, interactions with hosted service profiles, user profiles, relay messages, and the like.

The social device 2100 further includes processing circuitry 2104 operable to process and manage communications, services, and dependencies between the device and other entities, including members of the SNET/SNET Group/SNET Subgroup 2124, third parties, Software agents and so on. More specifically, processing circuitry 2104 can include, for example, a software management application 2112 that includes one or more docking logic 2114 (including support for device discovery and configuration protocols described below), communication protocol control 2116, resource management 2118, and security/authentication. 2120 function.

The social device 2100 can further utilize data messages and other resources that can take many forms and can remain within the static or dynamic storage 2124. Such data messages can allow the social device and/or user 2101 to display their own images and their functions to other members of the SNET. In particular, device/group profile messages and other resources 2106 and user profile messages 2108 can be used in a variety of ways to facilitate various social interactions, in accordance with various embodiments. The device or user profile can be static or dynamic depending on the functionality and requirements of the particular device (and other members of the SNET).

In some embodiments, the social device 2100 can pass through the user interface circuit 2110. Interact with user 2101. User input to the social device 2100 can include data input, such as by a keyboard, touch screen, remote control, game controller, device control buttons, voice or gesture commands, storage devices, and the like. Authorized access or control of the social device 2100 can be facilitated by a unique biometric identifier, password, token-based identification, trusted authority or document (eg, a driver's license or pass), and similar authentication methods.

The social device 2100 can perform core or underlying functionality 2120. Alternatively, the social device may be primarily used as a social networking interface or communication device, or programmable to perform specific functions within the SNET group/subgroup.

The terms "approximately" and "approximately" as used herein, are used to provide an industrially acceptable tolerance and/or correlation between items for their respective terms. Such industrially acceptable tolerances range from less than 1% to 50% and correspond to, but are not limited to, component values, integrated circuit processing variations, temperature variations, rise and fall times, and/or thermal noise. This correlation between items ranges from a few percent difference to a large difference. The terms "operably coupled to," "coupled to," and/or "coupled", as used herein, are meant to include a direct coupling between items and/or an intermediate item between items (eg, an item including but not limited to The components, components, circuits, and/or modules are indirectly coupled, wherein for indirect coupling, the intermediate item does not modify the signal message, but its current level, voltage level, and/or power level can be adjusted. Inferred coupling, which may be further used herein (i.e., one component coupled with another component by inference) includes direct and indirect coupling between two items in the same manner as "coupled to." The term "operable to" or "operably coupled to" as used further herein means that the article includes one or more power connections, inputs, outputs, etc., such that upon activation, one or more of its respective Functionality, and may further include inferring coupling to one or more other items. The term "associated", which may still be used further herein, refers to a single item and/or an item embedded within another item for direct and/or indirect coupling. As used herein, the term "advantageously compare" means that the comparison between two or more items, signals, and the like provides the desired relationship. E.g, The required relationship is that when the amplitude of the signal 1 is greater than the amplitude of the signal 2, the amplitude of the signal 1 is larger than the amplitude of the signal 2 or the amplitude of the signal 2 is smaller than the amplitude of the signal 1, and an advantageous comparison can be made.

The terms "processing module", "module", "processing circuit", and/or "processing unit" as may also be used herein may be a processing device or a plurality of processing devices. Such processing devices can be microprocessors, microcontrollers, digital signal processors, microcomputers, central processing units, field programmable gate arrays, programmable logic devices, state machines, logic circuits, analog circuits, digital circuits, and / or any device that manipulates (analog or digital) signals according to hard-coded and/or operational instructions of the circuit. The processing module, module, processing circuit and/or processing unit may have associated storage and/or integrated storage components, which may be a single storage device, multiple storage devices, and/or processing modules, modules An embedded circuit that processes circuitry and/or processing units. Such storage devices may be read-only storage, random access storage, volatile storage, non-volatile storage, state machines, dynamic storage, flash storage, high speed storage, and/or Any device that stores digital messages. It should be noted that if the processing module, module, processing circuit, and/or processing unit includes more than one processing device, centralized positioning (eg, directly coupled through a wired and/or wireless bus structure) or distributed positioning These processing devices are (for example, indirect coupling via a local area network and/or a wide area network for cloud computing). Moreover, it is noted that if the processing module, module, processing circuit, and/or processing unit performs one or more functions through a state machine, analog circuit, digital circuit, and/or logic circuit, then the corresponding operational command is stored The storage and/or storage components can be embedded within or external to the circuitry including the state machine, analog circuitry, digital circuitry, and/or logic circuitry. It is further noted that the memory component can store and process the module, module, processing circuitry, and/or processing unit to execute hardcoded and/or operational instructions that are at least as described in one or more of the figures. Some steps and / or functions correspond. Such a reservoir device or reservoir component can be included in the article.

The method steps that have been described above for the performance of specific functions and their relationships have been The invention has been described. The boundaries and sequence of these functional components and method steps have been arbitrarily defined herein for the convenience of the description. Alternate boundaries and sequences may be defined as long as the specified functions and relationships are properly performed. The scope and spirit of any such alternatives are therefore within the scope and spirit of the invention as claimed. Moreover, the boundaries of these functional components have been arbitrarily defined for the convenience of the description. Alternate boundaries can be defined as long as certain important functions are performed appropriately. Also, block flow diagrams have been arbitrarily defined herein to illustrate certain important functions. To the extent of some use, the boundaries and order of the block flow diagrams may be additionally defined and still perform some important function. This alternative definition of functional components and block flow diagrams is therefore within the scope and spirit of the claimed invention. Those skilled in the art will also appreciate that the functional components and other elaborations therein can be performed as shown, or by discrete components, application specific integrated circuits, processors executing appropriate software, and the like, or any combination thereof. Sexual blocks, modules and components.

The invention has also been described, at least in part, in one or more embodiments. One embodiment of the invention is used herein to illustrate the invention, an aspect of the invention, its function, its concept, and/or its examples. Apparatus, articles, machines, and/or physical embodiments embodying the processes of the present invention can include one or more aspects, functions, concepts, and/or examples, performed in one or more embodiments discussed herein. description. Moreover, in all figures, these embodiments may include functions, steps, modules, etc., having the same or similar names, and the same or different reference numerals may be used, and the functions, steps, modules, and the like may be the same. Or similar or different functions, steps, modules, and so on.

Unless explicitly stated to the contrary, in any of the figures shown herein, the signals sent to the component, the signals transmitted from the component, and/or the signals between the components may be analog or digital, continuous time discrete time, And single-ended or differential signals. For example, if the signal path is displayed as a single-ended path, the signal path also represents a differential signal path. Similarly, if the signal path is displayed as a differential path, the signal path also represents a single-ended signal path. Those skilled in the art will recognize that in this article While describing one or more specific structures, other structures may be utilized that use one or more data buses, direct connections between components, and/or indirect coupling between other components that are not explicitly shown.

In describing various embodiments of the invention, the term "module" is used. The module includes a function block that is used by the hardware to perform one or more module functions, such as processing one or more input signals to generate one or more output signals. The hardware of the execution module itself can be operated in conjunction with software and/or firmware. The modules used herein may include one or more sub-modules, which are themselves modules.

Although specific combinations of the various functions and features of the present invention have been described herein, these features and functions can also have other combinations. The invention is not limited by the specific examples disclosed herein, and such other combinations are explicitly included.

100‧‧‧SNET grouping hierarchy

101‧‧‧Serving SNET infrastructure

103, 105, 107‧‧‧ Client SNET Infrastructure

106‧‧‧Docking specifications

111‧‧‧User device (service support social user device)

113‧‧‧Application (social service application)

115‧‧‧SNET (SSUD) group

117‧‧‧ (mixed SA/SSUD) SNET group

119‧‧‧SNET (SA) group

125‧‧‧Docking treatment (selection & docking process)

131, 141, 151‧‧‧ Client social devices (client social user devices)

135, 145, 155‧‧‧ Client SNET Group

Claims (10)

A social networking system supporting interaction with a third party monitoring service and at least a first human member, the social networking system comprising: a management service supporting creation of a first social networking group, the management service supporting a first docking process And a second docking process, the first docking process comprising associating the first social networking group with a first device of the first human member, the second docking process comprising the first social networking group Associated with the third party monitoring service; and the management service supports a social path via the first social networking group, through which the third party monitoring service is capable of receiving material from the first device, and The monitoring service selectively triggers a support function in response to the received data, the support function including interaction with the at least a first portion of the first device by the third party monitoring service via the social pathway. The social networking system of claim 1, wherein the support function comprises the third party monitoring service controlling the first portion of the first device via the social path. The social networking system of claim 1, wherein the support function comprises the third party monitoring service accessing a status message from the first portion of the first device via the social path access. The social networking system of claim 1, wherein the monitoring service selectively triggers the support function in response to determining that the received data is associated with a trigger threshold. A monitoring system supporting a plurality of clients, the monitoring system comprising: a first system, interacting with a social network in a first docking process to join at least a first social network group, the first social network group comprising a first human member and a first social device member of the first human member, the first human member being a first one of the plurality of clients; the first system via the first social network group First social provided The path receives and evaluates communications from the first social device member; and the first system responds to the evaluation by selectively triggering a support function, the support function including at least the first social device member The first part of the interaction. The monitoring system of claim 5, wherein the support function comprises accessing, by the first system, a status message from at least a first portion of the first social device member. The monitoring system of claim 5, wherein the support function comprises control of at least a first portion of the first social device member by the first system. An apparatus for supporting a member of a social networking system, the apparatus comprising: an interface communicatively coupled to the social networking system; and processing circuitry operative with the interface to: in the first docking process The social networking system interacts to interface the device with a first social networking group, the first social networking group including a third party monitoring service member; and a social path provided via the first social networking group, A status message associated with the first portion of the device is communicated to the third party monitoring service member. The apparatus of claim 8, wherein the processing circuit is operative with the interface to provide control to the third party monitoring service member for the first portion of the apparatus. A device as claimed in claim 8 wherein the first portion of the device comprises a sensor capable of generating data based on an environment proximate to the device.