Delegating group ownership in peer-to-peer network

Abstract

To provide methods and systems for delegating group ownership in P2P networks.SOLUTION: A method includes: among other things, responsive to a pending disconnection of the first station device from a P2P network, identifying, from a list of a plurality of station devices maintained by the first station device, a second station device to delegate ownership of the P2P network; and delegating ownership from the first station device to the second station device.SELECTED DRAWING: Figure 4

Description

[Technical Field]

[0001] TECHNICAL FIELD This disclosure relates to peer-to-peer (P2P) networks, and more particularly to group ownership delegation in P2P networks. [Background technology]

[0002] A wireless local area network (WLAN) peer-to-peer (P2P) network is a type of wireless network configuration in which various client devices, also known as station devices, communicate directly with each other without relying on a centralized access point such as a router. It serves as a flexible way to create temporary networks, small home networks, in situations where a central access point is not readily available. Typically, these WLAN P2P networks facilitate file sharing between station devices. Summary of the Invention [Means for solving the problem]

[0003] Aspects and embodiments of the present disclosure will be more fully understood from the following detailed description and the accompanying drawings of various aspects and embodiments of the present disclosure, which, however, should not be construed to limit the disclosure to any particular aspect or embodiment, but are for purposes of illustration and understanding only. [Brief explanation of the drawings]

[0004] [Figure 1A] FIG. 2 is a block diagram of an illustrative example of a station device, according to an embodiment of the present disclosure. [Figure 1B] 1 is a block diagram of an illustrative example environment in which one or more station devices establish a WLAN P2P network, according to an embodiment of the present disclosure. [Figure 2]1 illustrates an established WLAN P2P network based on different delegation techniques according to an embodiment of the present disclosure. [Figure 3] FIG. 1 illustrates a ranking list used to facilitate the delegation of group ownership from one station device to another, according to an embodiment of the present disclosure. [Figure 4] 1 is a flow chart illustrating an example method for transferring group ownership from one station device to another station device, according to an embodiment of the present disclosure. [Figure 5] 1 is a flow diagram illustrating an example method for maintaining a ranking list for delegating group ownership from one station device to another, according to an embodiment of the present disclosure. DETAILED DESCRIPTION OF THE INVENTION

[0005] Aspects of the present disclosure relate to delegation of group ownership in a P2P network. A WLAN P2P network (referred to as a P2P network for simplicity) refers to a network of interconnected nodes (e.g., station devices) that establish WLAN connections without intermediate wireless access points, routers, or Internet connections. A P2P network is established when station devices discover each other. Once the station devices discover each other, one station device is designated as the group owner (GO). This is typically determined through a negotiation process that can be initiated by either of the station devices. The negotiation process determines which station device (STA) will become the GO based on factors such as power source (battery or wall-powered) and network conditions. The STA designated as the GO (e.g., the GO) is responsible for managing network configuration and controlling access to the network (e.g., accepting new connections and disconnecting existing connections). Once the P2P network is established, data can be transferred directly between the station devices. This can include file sharing, media streaming, or Internet connection sharing if the GO has access to another network (such as a mobile data connection).

[0006] Typically, a station device (or a STA designated as a group client (GC)) that is not designated as a GO (e.g., a GC) may wish to exit a P2P network or terminate a P2P network session. When a GC exits a P2P network, it disconnects from the P2P network without affecting the P2P network itself (i.e., the GO and other GCs can continue to communicate within the P2P network). However, in the current implementation, if a GO wishes to exit a P2P network, the P2P network is disbanded because the GO cannot delegate its ownership of the P2P network to another GC. Similarly, if a new station device that is more suitable as a GO joins the P2P network, the new station device cannot be designated as the GO.

[0007] In the current implementation, a GO may delegate its ownership of the P2P network to a GC based on the capabilities of the station device. More specifically, when a GO wants to exit a P2P network, the GO sends a request to obtain intent values ​​from each GC in the P2P network. The intent values ​​sent by each GC in the P2P network may be based on details such as cross-connections, services provided, and device capabilities. The intent values ​​received by the GO from each GC in the P2P network may be used to select a GC (e.g., a new GO) from among the GCs in the P2P network. The method for selecting a new GO may vary depending on the algorithm used (e.g., selecting the GC with the highest intent value).

[0008] Once the new GO is selected from among the GCs in the P2P network, the GO sends a delegation confirmation to the new GO. When the new GO receives the delegation confirmation from the GO, the new GO either accepts or rejects the delegation confirmation. If the new GO rejects the delegation confirmation, the GO negotiates with other GCs in the P2P network. If the new GO accepts the delegation confirmation, the GO handshakes with the new GO and sends the relevant information, such as dynamic host configuration protocol (DHCP) server details, peer-to-peer device and interface addresses, group identification, and client state. The GO also sends notifications to the other GCs in the P2P network, identifying the new GO as the GO.

[0009] Although the current implementation provides the ability for a station device (e.g., a GO) of a P2P network to delegate its ownership of the P2P network to another station device (e.g., a new GO) based on its capabilities, it is possible that one or more GCs of the P2P network are not within the communication range of the new GO. Thus, one or more GCs of the P2P network that are not within the communication range of the new GO but were within the communication range of the GO can no longer communicate with other GCs of the P2P network. As a result, if the communication range of the P2P network associated with the new GO includes a small subset of the GCs, the delegation of ownership from the GO to the new GO is equivalent to disbanding the P2P network.

[0010] Aspects and embodiments of the present disclosure address these and other limitations of existing technologies by creating and maintaining a list (e.g., a ranking list) of one or more station devices (e.g., STAs) to facilitate delegation of GO responsibilities from a GO to another GC. The ranking list includes, for each GC, an intent value, a reachability value, and a ranking score calculated based on the intent value and the reachability value. The intent value is a predefined value indicating the priority of the GO. The reachability value is a value indicating the number of GCs communicatively accessible by the respective GC. The reachability value may be determined using various methods, such as reading from various packets, frames, and / or messages sent by nearby GCs, among other information. The intent value, and in some embodiments, the reachability value, are also received by the GO from one or more GCs during negotiation. The GO periodically updates the ranking list at predetermined time intervals based on the reachability values ​​periodically sent by each GC to the GO.

[0011] During the delegation of the GO role from the GO to a GC, the GO obtains the GC (or station device) with the highest ranking score (e.g., the highest-ranked station or highest-ranked STA) from the ranking list. In some embodiments, additional logic may be implemented in selecting the highest-ranked STA. The GO delegates the GO role to the highest-ranked STA by providing role-related information including an intent value for each GC to be used by the highest-ranked STA to create the ranking list before disconnecting from the P2P network. In some embodiments, the GO may further establish secure connections with other GCs on behalf of the highest-ranked STA using a secure connection method such as push-button configuration (e.g., Wi-Fi Protected Setup (WPS)) and provide the highest-ranked STA with access to the established secure connections.

[0012] Aspects of the present disclosure overcome these and other drawbacks by maintaining a ranking list used to facilitate group ownership delegation and maintaining the GC's connection to the P2P network during group ownership delegation, thereby reducing the GC's sensing and power overhead and maintaining a constant connection to the P2P network.

[0013] 1A is a block diagram of an illustrative example of a station device (e.g., station device 110). In at least some embodiments, station device 110 includes, but is not limited to, a transmitter 102A, a receiver 104A, a communication interface 106, a transmit (TX) antenna 102B coupled to transmitter 102A, a receive (RX) antenna 104B coupled to receiver 104A, a memory 108, one or more input / output (I / O) devices 112 (such as a display screen, touch screen, keypad, etc.), and a processor 114. In some cases, one or more of the components, such as memory 108, may also be coupled to a communication bus 116. In some embodiments, aspects of communication interface 106 cooperate with processor 114 to operate or function as a processing device for station device 110. In some embodiments, there is a single antenna and multiplexing logic for switching antenna use between transmitter 102A and receiver 104A. In various embodiments, front-end components such as the transmitter 102A, receiver 104A, communication interface 106, and one or more antennas (e.g., TX antenna 102B and / or RX antenna 104B) described herein in various devices are adapted for or configured for WLAN and personal area network (PAN)-based frequency bands, e.g., Bluetooth® (BT), Bluetooth Low Energy (BLE), Wi-Fi™, Zigbee®, Z-wave™, etc. The processor 114 may include a role delegation component 115.

[0014] 1A illustrates one or more components of station device 110, station device 120, station device 130, station device 140, station device 150, station device 160, station device 170, and station device 180 also include similar components. Thus, each STA of the plurality of STAs includes, but is not limited to, a transmitter, a receiver, a communication interface, a transmit (TX) antenna coupled to the transmitter, a receive (RX) antenna coupled to the receiver, memory, and a processor including role delegation component 115.

[0015] FIG. 1B is a block diagram of an illustrative example of an environment 100 including multiple station devices (STAs) (e.g., STAs 110-180) according to an embodiment of the present disclosure. The multiple STAs may establish a wireless network, such as a WLAN P2P network (e.g., a P2P network). In particular, an STA of the multiple STAs (e.g., an initiating STA of the multiple STAs) may establish the P2P network and initiate discovery of other STAs (e.g., remaining STAs of the multiple STAs) in the vicinity (e.g., within the environment 100) that are configured to be discoverable. In particular, the initiating STA sends out a discovery signal or probe. The remaining STAs of the environment 100 respond to the initiating STA's discovery signal (e.g., acknowledge the discovery signal). This response typically includes information necessary to establish a connection, such as device name, device type, supported services, connection parameters, etc.

[0016] After discovery, the STAs negotiate to determine which of the STAs will act as a group owner (e.g., GO) and which will act as a group client (e.g., GC). In particular, the STAs share their intention to become GOs. The STAs' intentions may be expressed as intent values. The intent values ​​are predefined values ​​that indicate the priority of acting as GOs, which may be influenced (or determined) by the STA's processing capabilities, connectivity options, battery life, etc. Based on the shared intentions, the STAs agree on which STA (e.g., STA 110) will become the GO and designate that STA as the GO. Typically, the STAs agree that the STA with the highest intention will become the GO. Each of the remaining STAs (e.g., STA 120, STA 130, STA 140, STA 150, STA 160, STA 170, and STA 180) is designated as a GC (e.g., multiple GCs). The GO functions as an access point in a conventional WLAN network. The GO manages the P2P network configuration, including the Service Set Identifier (SSID) and security settings, and controls access to the P2P network. The GC connects to the GO and communicates through the GO.

[0017] After negotiation, the multiple GCs establish direct P2P connections 125-185 that are used to establish a P2P network. In particular, each GC of the multiple GCs may have a specific P2P connection, such as a Personal Identification Number (PIN) entry, a push button configuration (e.g., Wi-Fi Protected Setup (WPS) or near field communication), etc. Each GC establishes a secure connection with the GO (e.g., a direct P2P connection among the direct P2P connections 125-185) using a secure connection method such as Near Field Communication (NFC). Each GC exchanges connection information with the GO, which may include a service set identifier (SSID), security settings, and other network configuration details that ensure the GO and GC are configured to communicate effectively. Using the exchanged connection information, the GCs connect to the GO, and the GO accepts the connection. The GO may assign network addresses (such as IP addresses) to the GCs. Once the secure connections (e.g., direct P2P connections 125-185) are established, the GCs can begin communicating, enabling data transfer, file sharing, streaming, or any other P2P network activity. The GO manages the P2P network, controls access, and manages communication between the GCs. The GO can also handle the joining of new STAs (e.g., new GCs) to the P2P network or the leaving of existing STAs (e.g., existing GCs).

[0018] As described above, each of the STAs 110-180 may include a role delegation component (e.g., role delegation components 191-198) similar to the role delegation component 115 that facilitates the delegation of the role of the GO. In particular, the role delegation component 191 of the GO (e.g., the STA 110 or first station device) maintains a list (e.g., a ranking list) of multiple GCs used to facilitate the delegation of the role of the GO from the GO to a GC among the multiple GCs. During negotiation, the role delegation component 191 of the GO creates a list of multiple GCs with corresponding intents (e.g., intent values) (i.e., inserts each GC into the list along with its corresponding intent value). The list (or ranking list) of multiple GCs may be stored in the GO. In some embodiments, during negotiation, the role delegation components 192-198 of the multiple STAs may share their reachability values. The reachability value is a value indicative of the number of STAs in the environment 100 that are communicatively accessible. Each STA's role delegation component 191-198 may determine its reachability value using various methods, such as reading from various packets, frames, and / or messages transmitted by nearby STAs, among other information. Packets may include, for example, transmission control protocol (TCP) frames. Frames may include, for example, beacon frames. Messages may include, for example, keep-alive messages. Thus, the GO's role delegation component 191 may include their corresponding reachability values ​​in creating a list of multiple GCs with corresponding intents (e.g., intent values).

[0019] The GO role delegation component 191 may calculate a ranking score for each STA in the list of multiple GCs and include the calculated ranking score with the respective STA in the list of multiple GCs. The ranking score is calculated using the STA's intent value and the STA's reachability value. In some embodiments, the ranking score may be calculated by adding (e.g., summing) the intent value and the reachability value. In some embodiments, the ranking score may be calculated by averaging the intent value and the reachability value. In some embodiments, the ranking score may be calculated by applying a weight value to the intent value and / or the reachability value and adding (e.g., weighted sum) the intent value and the reachability value.

[0020] In some embodiments, the role delegation components 192-198 of each of the multiple GCs may share their reachability values ​​with the GO after establishing a wireless network at regular intervals requested by the respective GCs. For example, the regular intervals of one or more of the multiple GCs may be the same or different. The role delegation component 191 of the GO may update the reachability value of each of the multiple GCs in the ranking list at periodic time intervals. In particular, the most recently received reachability value of each of the multiple GCs is used to replace the reachability value of each of the multiple GCs in the ranking list. Thus, the ranking score is recalculated based on the replaced (or updated) reachability value in the ranking list.

[0021] The GO role delegation component 191 may initiate the delegation of the GO role from the GO to a GC of the multiple GCs. In some embodiments, the initiation of the GO role delegation may be in response to the GO indicating a pending disconnection from the P2P network (e.g., due to the GO's power loss or intention to disconnect). In some embodiments, the initiation of the GO role delegation may be in response to a new GC joining the P2P network. In some embodiments, the initiation of the GO role delegation may be in response to a ranking score of a GC of the multiple GCs in a ranking list exceeding the ranking score of the GO. Other conditions and / or scenarios for initiating the GO role delegation are also contemplated. The GO role delegation component 191 identifies a GC of the multiple GCs with the highest ranking score from the ranking list. In some embodiments, the GO role delegation component 191 may determine that one or more GCs of the multiple GCs have the highest ranking score. Thus, the GO role delegation component 191 may prioritize selecting a GC of the one or more GCs from the one or more GCs of the multiple GCs with the highest ranking score using one or more criteria. The one or more criteria may include power source (eg, wall or battery powered) and highest remaining battery life among battery-powered GCs, among other contemplated criteria.

[0022] For example, in some cases, the GO role delegation component 191 may prioritize selecting a GC from one or more GCs that use an alternating current (AC) connection (e.g., wall-powered) from one or more GCs from the plurality of GCs with the highest ranking score. In some cases, the GO role delegation component 191 may determine that one or more GCs from the plurality of GCs with the highest ranking score are all battery-powered. Thus, the GO role delegation component 191 may prioritize selecting a GC from one or more GCs with the highest remaining battery power from one or more GCs from the plurality of GCs with the highest ranking score. In some cases, the GO role delegation component 191 may determine that one or more GCs from the plurality of GCs with the highest ranking score have the same remaining battery power. Thus, the GO role delegation component 191 may randomly select a GC from one or more GCs from the one or more GCs from the plurality of GCs with the highest ranking score. The GC from the plurality of GCs selected by the GO role delegation component 191 is set as the highest-ranked station or the highest-ranked STA (e.g., the second station device).

[0023] The GO role delegation component 191 delegates the role of GO to the highest-ranked STA. In particular, the GO provides the highest-ranked STA with role-related information (e.g., DHCP server details, group identification, client state, etc.). The role-related information may include an intent value for each GC of multiple GCs to be used by the highest-ranked STA to create a ranking list.

[0024] In some embodiments, the GO may have sufficient time before disconnecting from the P2P network. Thus, to delegate the role of the GO, the GO's role delegation component 191 establishes a secure connection on behalf of the highest-ranked STA using a secure connection method such as a push-button setup (e.g., Wi-Fi Protected Setup (WPS)). For example, the GO generates encryption keys for multiple GCs using the current secure connection with the GO and provides the encryption keys for the multiple GCs to the highest-ranked STA. Thus, the highest-ranked STA may establish secure connections to the multiple GCs using the encryption keys.

[0025] Once the GO has provided the encryption keys for the multiple GCs to the highest-ranked STA, the GO may disconnect from the P2P network. In another embodiment, because the GO may not have much time before disconnecting from the P2P network, the GO disconnects after providing role-related information, including the intent values ​​of each GC of the multiple GCs, to be used by the highest-ranked STA to create a ranking list. Thus, the process of establishing a secure connection between the highest-ranked STA and the multiple GCs is left to the highest-ranked STA. In particular, the highest-ranked STA may establish the secure connection using a secure connection method.

[0026] 2 is a block diagram of an illustrative example of the environment 100 of FIG. 1 in which GO role delegation affects a P2P network, according to an embodiment of the present disclosure. Similar to FIG. 1, the environment 100 includes multiple station devices (STAs) (e.g., STAs 110-180).

[0027] Of the multiple STAs, STA 110 may be designated a GO role (e.g., GO), and STAs 120-180 may be designated a GC role (e.g., GC). STA 180's communication range 210 enables the establishment of a P2P network (via direct P2P connections between STA 110 and STAs 120-180, not shown). Communication ranges, such as communication range 210, communication range 240, and communication range 260, refer to the maximum distance over which a station (e.g., STA 110, STA 140, and STA 160, respectively) can effectively transmit and receive signals.

[0028] In response to initiating the GO role delegation, STA 110 may determine that STA 160 should be delegated the GO role based on the intent value. STA 160's communication range 260 allows for the establishment of a P2P network (via a direct P2P connection between STA 160 and STA 170, not shown). As a result, STA 120, STA 130, STA 140, STA 150, and STA 180 will be disconnected from the P2P network.

[0029] In response to initiating the GO role delegation, STA 110 may determine that STA 140 should be delegated the GO role based on a ranking score obtained from the ranking list of STA 110. Communication range 240 of STA 140 allows for the establishment of a P2P network (via direct P2P connections between STA 140 and STAs 120, 130, 150, 160, 170, and 180, not shown). As a result, no (or fewer) STAs were involuntarily disconnected from the P2P network.

[0030] 3 illustrates a ranking list 300 maintained by a GO of a P2P network in accordance with an embodiment of the present disclosure. The ranking list 300 includes a plurality of entries. Each entry of the plurality of entries corresponds to a STA among a plurality of STAs (e.g., STA 120, STA 130, STA 140, STA 150, STA 160, STA 170, and STA 180 in FIG. 1 ). Each entry includes an identifier of the STA among the plurality of STAs, an intent value, a reachability score, and a ranking score.

[0031] The intent value of a particular STA is a predefined value that indicates the preference of the particular STA to act as a GO, which may be influenced (or determined) by the particular STA's processing capabilities, connectivity options, battery life, etc. The reachability value of a particular STA is a value that indicates the number of STAs in environment 100 that are within communication range (i.e., communicatively accessible) of the particular STA. Referring briefly to FIG. 2, the intent value of STA 160 (e.g., 12) is greater than the intent value of STA 140 (e.g., 10), but the reachability value of STA 160 (e.g., 1) is less than the reachability value of STA 140 (e.g., 6). As a result, the ranking score of STA 160 (e.g., 13) is less than the ranking score of STA 140 (e.g., 16), indicating that STA 140 is more suited to the role of GO than STA 160.

[0032] 4 is a flow diagram of a method 400 for delegating group ownership from one station device to another station device according to an embodiment of the present disclosure. Method 400 can be performed by processing logic that can include hardware (e.g., a processing device, circuitry, dedicated logic, programmable logic, microcode, device hardware, integrated circuits, etc.), software (e.g., instructions operating on or executed on a processing device), or a combination thereof. In some embodiments, method 400 is performed by a GO that includes role delegation component 115 (of FIG. 1), role delegation components 191-198 (of FIG. 2), and / or a processor (e.g., a processing device).

[0033] At operation 410, the processing logic determines whether the GO has initiated delegation of its GO role in the P2P network. As previously described, the initiation of delegation of the GO role may be in response to the GO indicating a pending disconnection from the P2P network (e.g., due to the GO's power loss or intention to disconnect), a new GC joining the P2P network, or the GC's ranking score in the ranking list exceeding the GO's ranking score. The ranking list is stored in the GO and includes, for each GC, an intent value, a reachability value, and a ranking score calculated based on the intent value and the reachability value. The intent value is a predefined value indicating the priority of the GO. The reachability value is a value indicating the number of GCs communicatively accessible by each GC.

[0034] At operation 420, the processing logic obtains, from the ranking list of the GO, a station device to which the role of GO should be delegated. As described above, the station device may be selected from the ranking list by identifying the station device (or GC) with the highest ranking score. In some embodiments, if two or more station devices (or GCs) have the highest ranking scores, the station device using an AC connection is prioritized. If two or more station devices with the highest ranking scores are battery-powered rather than AC-connected, the station device among the two or more station devices with the highest ranking scores that has the highest remaining battery life is prioritized. If two or more station devices with the highest ranking scores have the same remaining battery life, the station device among the two or more station devices with the highest ranking scores is randomly selected. Alternatively, rather than prioritizing AC connections and / or remaining battery life, the station device among the two or more station devices with the highest ranking scores is randomly selected.

[0035] At operation 430, the processing logic transfers the role of GO from the GO to the station device. As described above, the GO transfers the role to the station device by providing role-related information including an intent value for each station (or GC) of multiple station devices (e.g., GCs) to be used to create a new ranking list by the highest-ranked STA. Depending on the amount of time the GO has until it disconnects from the P2P network, the GO may establish a secure connection with the remaining station devices on behalf of the station device using various secure connection methods. Once established, the GO provides information about the secure connection (e.g., encryption keys) to the station device. If there is enough time remaining before it disconnects, the GO establishes the secure connection on behalf of the station device.

[0036] 5 is a flow diagram of a method 500 for maintaining a ranking list for delegating group ownership from one station device to another station device according to an embodiment of the present disclosure. Method 500 can be performed by processing logic that can include hardware (e.g., a processing device, circuitry, dedicated logic, programmable logic, microcode, device hardware, integrated circuits, etc.), software (e.g., instructions operating on or executed on a processing device), or a combination thereof. In some embodiments, method 500 is performed by a GO that includes role delegation component 115 (of FIG. 1), role delegation components 191-198 (of FIG. 2), and / or a processor (e.g., a processing device).

[0037] At operation 510, the processing logic creates a ranking list. As previously described, in some embodiments, during negotiations to establish a P2P network with a plurality of station devices, a station device designated as a GO (e.g., a GO) may receive an intent value from each of the remaining station devices among the plurality of station devices designated as GCs (e.g., a plurality of GCs). In some embodiments, each GC of the plurality of GCs may share a reachability value in addition to an intent value. The reachability value is a value indicating the number of GCs among the plurality of GCs that are communicatively accessible. The reachability value may be determined using various methods, such as reading from various packets, frames, and / or messages transmitted by nearby station devices, among other information. The GO may calculate a ranking score for each GC of the plurality of GCs based on its respective intent value and its respective reachability value. In some embodiments, the ranking score may be calculated by adding the intent value and the reachability value. In some embodiments, the ranking score may be calculated by averaging the intent value and the reachability value. In some embodiments, the ranking score may be calculated by applying a weighting value to the intent value and / or the reachability value and adding the intent value and the reachability value.

[0038] At operation 520, processing logic determines whether a periodic interval has been reached. The periodic interval may be the period between occurring operations. At operation 530, in response to determining that the periodic interval has been reached, processing logic updates the ranking list. As described above, the last received reachability value of each GC of the plurality of GCs is used to replace the reachability value of each GC of the plurality of GCs in the ranking list. Thus, the ranking score is recalculated based on the replaced (or updated) reachability value in the ranking list.

[0039] At operation 540, in response to determining that the periodic interval has not been reached, the processing logic receives reachability values ​​from each station device in the P2P network. At regular intervals, each GC of the multiple GCs shares their reachability values ​​with the GO based on their (e.g., respective GC) requested interval. In summary, the ranking list is not updated based on receiving reachability values ​​from the multiple GCs, but is triggered in response to reaching each periodic interval of the GO.

[0040] Throughout this specification, the reference to "one embodiment," "one embodiment," "implementation," or "embodiment" means that a particular feature, structure, or characteristic described in connection with that embodiment and / or embodiment is included in at least one embodiment and / or embodiment. Thus, the use of the phrase "in one embodiment" or "in an embodiment" in various places throughout this specification may, but does not necessarily, refer to the same embodiment, depending on the context. Furthermore, particular features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.

[0041] To the extent that the terms "includes," "including," "has," "contains," variations of these terms, and other similar terms are used in either the detailed description or the claims, these terms are intended to be as inclusive as the term "comprising" as open-ended transitional terms that do not exclude additional or other elements.

[0042] As used in this application, terms such as “component,” “module,” and “system” are intended to generally refer to computer-related entities, either hardware (e.g., circuitry), software, a combination of hardware and software, or an entity associated with an operating machine having one or more specific functions. For example, a component can be, but is not limited to, a process running on a processor (e.g., a digital signal processor), a processor, an object, an executable file, a thread of execution, a program, and / or a computer. By way of example, both an application running on a controller and the controller can be a component. One or more components can reside within a process and / or thread of execution, and a component can be localized on one computer and / or distributed among two or more computers. Furthermore, a “device” can take the form of specially designed hardware, general-purpose hardware that is specialized by the execution of software that enables the hardware to perform a specific function (e.g., generate points of interest and / or descriptors), software on a computer-readable medium, or a combination thereof.

[0043] The aforementioned systems, circuits, modules, etc. have been described with respect to interactions between several components and / or blocks. It will be understood that such systems, circuits, components, blocks, etc. may include those components or designated subcomponents, portions of the designated components or subcomponents, and / or additional components, according to various permutations and combinations of the foregoing. Subcomponents may also be implemented as components communicatively coupled to other components rather than being contained within a parent component (hierarchical). Furthermore, it should be noted that one or more components may be combined into a single component providing aggregate functionality or may be divided into several separate subcomponents, and that one or more optional intermediate layers, such as a management layer, may be provided to communicatively couple such subcomponents to provide integrated functionality. Any component described herein may also interact with one or more other components not specifically described herein but known to those skilled in the art.

[0044] Furthermore, the words "example" or "exemplary" are used herein to mean serving as an example, instance, or illustration. Any aspect or design described herein as "exemplary" is not necessarily to be construed as preferred or advantageous over other aspects or designs. Rather, use of the word "example" or "exemplary" is intended to present a concept in a concrete manner. As used in this application, the term "or" is intended to mean an inclusive "or" rather than an exclusive "or." That is, unless otherwise specified or clear from the context, "X uses A or B" is intended to mean any of the natural inclusive permutations. That is, if X uses A, if X uses B, or if X uses both A and B, then "X uses A or B" is satisfied under any of the aforementioned examples. Additionally, the articles "a" and "an," as used in this application and the appended claims, should generally be construed to mean "one or more" unless otherwise specified or unless the singular form is clearly intended from the context.

[0045] Finally, embodiments described herein include collections of data describing users and / or user activities. In one embodiment, such data is collected only when the user consents to the collection of this data. In some embodiments, the user is prompted to explicitly authorize data collection. Additionally, the user may opt in or out of participating in such data collection activities. In one embodiment, the collected data is anonymized before any analysis is performed to obtain any statistical patterns, so that the user's identity cannot be determined from the collected data.

Claims

1. A first station device of a plurality of station devices in a peer-to-peer (P2P) network, comprising: The processor of the first station device responsive to a pending disconnection of the first station device from the P2P network, identifying a second station device from the list of station devices maintained by the first station device to which ownership of the P2P network should be transferred; transferring ownership from the first station device to the second station device; performing an action including First station device.

2. The operation of transferring ownership from the first station device to the second station device includes: providing an intent value associated with each station device in the list to the second station device; causing the second station device to take ownership of the P2P network; Including, The first station device of claim 1 .

3. The operation of transferring ownership from the first station device to the second station device includes: generating one or more encryption keys for the plurality of station devices; providing the one or more encryption keys to the second station device; providing an intent value associated with each station device of the plurality of station devices from the list to the second station device; causing the second station device to take ownership of the P2P network; Including, The first station device of claim 1 .

4. The processor of the first station device: receiving an intent value and a reachability value from each station device of the plurality of station devices in response to establishing the P2P network; generating the list by inserting each station device of the plurality of station devices into the list along with a corresponding intent value and a corresponding reachability value; performing the operations further comprising: The first station device of claim 1 .

5. the reachability value is the number of station devices among the plurality of station devices that are within communication range of each station device; The first station device of claim 4 .

6. The processor of the first station device: an operation of receiving a plurality of reachability values ​​from the plurality of station devices, each reachability value of the plurality of reachability values ​​corresponding to a station device of the plurality of station devices; updating the list based on the plurality of reachability values; identifying a station device in the list identified as a highest ranked station device based on the intent value and the reachability value; performing the operations further comprising: The first station device of claim 1 .

7. the P2P network is a wireless local area network (WLAN) established among the plurality of station devices; The first station device of claim 1 .

8. 1. A wireless network, comprising: a first station device among a plurality of station devices that acts as an owner of the wireless network; The processor of the first station device an operation of periodically receiving a plurality of reachability values ​​from the plurality of station devices, each reachability value of the plurality of reachability values ​​corresponding to a station device of the plurality of station devices; an operation of updating, at each predetermined time interval, a list of the plurality of station devices maintained by the first station device using the plurality of reachability values, wherein each station device in the list includes a corresponding intent value and a corresponding reachability value; identifying, based on the list, a station device in the list to be designated as a highest-ranked station device to transfer ownership in response to a pending disconnection of the first station device; performing an action including Wireless network.

9. the wireless network is a wireless local area network (WLAN) established among the plurality of station devices; The wireless network of claim 8.

10. The processor of the first station device: retrieving the highest ranked station device from the list in response to the pending disconnection of the first station device; transferring ownership to the highest ranked station device; performing the operations further comprising: The wireless network of claim 8.

11. The operation of transferring ownership to the highest-ranked station device includes: providing the highest ranked station device with an intent value associated with each station device in the list; The wireless network of claim 10.

12. The operation of transferring ownership to the highest-ranked station device includes: generating one or more encryption keys for the plurality of station devices; providing the one or more encryption keys to the highest-ranked station device; providing the highest ranked station device with an intent value associated with each station device in the list; Including, The wireless network of claim 10.

13. each reachability value being the number of station devices among the plurality of station devices that are within communication range of the respective station device; The wireless network of claim 8.

14. 1. A method comprising: The method includes maintaining, by a first station device of a plurality of station devices of a wireless network, a list of the plurality of station devices, each station device in the list including an intent value and a reachability value; A method comprising:

15. The method further includes, in response to a pending disconnection of the first station device, transferring ownership of the wireless network from the first station device to a station device identified as the highest-ranked station device in the list based on the intent value and the reachability value.

15. The method of claim 14.

16. the wireless network is a wireless local area network (WLAN) established among the plurality of station devices; 15. The method of claim 14.

17. The method further includes generating, by the first station device, the list in response to establishing the wireless network for the plurality of station devices.

15. The method of claim 14.

18. The step of generating the list by the first station device includes: receiving, by the first station device, an intent value and a reachability value from each station device of the plurality of station devices; inserting, by the first station device, each station device of the plurality of station devices into a list with a corresponding intent value and a corresponding reachability value; storing, by the first station device, the list; Including, 18. The method of claim 17.

19. The step of maintaining the list by the first station device comprises: receiving, by the first station device, a current reachability value from each station device of the plurality of station devices; updating, by the first station device at each predetermined time interval, the reachability value of each station device in the list with a corresponding current reachability value; Including, 15. The method of claim 14.

20. the reachability value is the number of station devices among the plurality of station devices that are within communication range of each station device; 15. The method of claim 14.

Images