WLAN peer-to-peer connection using MBSSID

Abstract

A method of establishing direct communication between two peer-to-peer non-AP STAs in a network environment comprising a plurality of networks, at least one access point (AP), and at least two non-AP STAs, the method comprising: the AP advertising at least two basic service sets (BSSs), where the BSSs allow peer-to-peer (P2P) connections, where each BSS comprises a respective BSS profile, where the BSS profile is configured to communicate with the plurality of networks, the at least one access point (AP), and the at least two non-AP STAs. The BSS profile includes an identifier element (P2PID element) for identifying the P2P capability, thereby advertising the P2P capability to the corresponding BSS; the two peer-to-peer non-AP STAs discover a P2PID element; a P2P connection is established between two peer-to-peer non-AP STAs.

Description

TECHNICAL FIELD

[0001] The present disclosure relates generally to methods and systems in the field of point-to-point connectivity. BACKGROUND

[0002] Tunneled Direct Link Setup (TDLS) enables two peer non-access point (non-AP) stations (STAs) to establish direct communication with each other. Once the TDLS link is established, traffic flows directly between the peer STAs without bridging through the AP. TDLS can only be established between two STAs associated with the same AP in the same basic service set (BSS). The path of frames is reduced from STA-AP-STA to STA-STA.

[0003] IEEE 802.11 includes a feature of Multiple BSS identifier (MBSSID). MBSS enables an AP to advertise multiple co-located BSSs using an MBSSID and a single beacon. The BSSs are connected to separate extended service sets (ESSs) / distribution systems (DSs), so it is unclear whether the BSSs provide connectivity to a single local area network (LAN).

[0004] Furthermore, TDLS can enable peer STAs to establish direct communication, but only if the peer STAs are connected to the same BSS, i.e., the same AP. With the MBSSID feature, the peer STAs can be connected to the same AP on different BSSs.

[0005] In many use cases, STA-to-STA communication is useful and does not require a network, e.g., file and media sharing, peripheral communication (e.g., external display), and gaming.

[0006] Based on IEEE 802.11, technologies such as Wi-Fi Direct and independent basic service set (IBSS) can provide direct connection between stations, but are cumbersome to configure and manage. Therefore, most STA-to-STA communication takes place within the coverage of an access point.

[0007] Discovery and setup frames are typically encapsulated within data frames for exchange between peer STAs through an AP. Therefore, the AP does not need to "support TDLS". Once setup is complete, the two non-AP STAs can communicate directly.

[0008] TDLS communication is used in various applications, such as screen sharing and streaming to display devices.

[0009] One problem with point-to-point communication between STAs is that the bands in which the STAs can operate are limited, i.e. when both devices cannot operate as master of a given regulatory domain, they cannot operate in the radar (e.g. UNII-2) and 6 GHz bands.

[0010] By establishing a connection through an AP, the peer devices can at least operate on the same channel on which the AP operates.

[0011] Therefore, in view of the above, it is an object of the present disclosure to find an alternative solution that allows a peer STA to establish a connection when the peer STA is associated with a different BSS. SUMMARY

[0012] Throughout the text of the present disclosure, the terms "point-to-point", "P2P initiator" and "P2P initiator STA" shall be understood as synonyms. Furthermore, the terms "P2P responder" and "P2P responder STA" shall be understood as synonyms.

[0013] In view of the above, the present disclosure relates to a method and system for establishing a direct communication between two peer non-access point (non-AP) stations (STAs) in a network environment comprising a plurality of networks.

[0014] The present disclosure is defined by the scope of the independent claims. The dependent claims provide advantageous embodiments of the present disclosure.

[0015] The present disclosure provides a first aspect of a method for establishing a direct communication between two peer non-access point (AP) stations (STAs) in a network environment comprising a plurality of networks, at least one AP and at least two non-AP STAs, the method comprising: the AP advertising at least two basic service sets (BSSs), wherein the BSSs allow a peer-to-peer (P2P) connection, wherein each BSS comprises a respective BSS profile comprising an identifier element (i.e. P2P ID element) for identifying a P2P capability, thereby advertising the P2P capability to the respective BSS; the two peer non-AP STAs discovering the P2P ID element; establishing a P2P connection between the two peer non-AP STAs.

[0016] According to one implementation of the method of the first aspect, in the method, the BSS configuration file may further include a subfield indicating a P2P connection, namely a P2P connection subfield.

[0017] According to one implementation of the method of the first aspect, the method may further include: in the case of BSS co-location, the AP sends a separate beacon for each BSS hosted by the AP, wherein the AP uses the separate beacon for advertising, and each of the separate beacons in the BSS profile includes an element that enables the AP to advertise BSSs that allow P2P connections, i.e., a P2P connection element.

[0018] According to one implementation of the method of the first aspect, in the method, the P2P connection element may include at least the following subfields: a subfield indicating the identifier element (i.e., the P2PID element) used to identify the P2P capability; the subfield indicating the P2P connection; and a subfield indicating the sender's BSSID (i.e., TX BSSID), wherein the TX BSSID is set to the BSSID of the P2P initiator.

[0019] According to one implementation of the method of the first aspect, in the method, the AP may advertise the at least two BSSs using Multiple BSSIDs (MBSSIDs).

[0020] According to one implementation of the method of the first aspect, in the method, the sender's BSSID (i.e., TX BSSID) may be equivalent to the AP's MBSSID.

[0021] According to one implementation of the method of the first aspect, in the method, the P2P connection subfield may include one or more of the following attributes: an attribute indicating whether the BSS announced by the P2PID element is connected to the same LAN or a different LAN; an attribute indicating whether the P2P connection uses auto-IP in IPv4; and an attribute indicating whether the P2P connection uses IPv6.

[0022] According to one implementation of the method of the first aspect, in the method, the identifier element used to identify the P2P can be an identifier used to identify the P2P link, that is, a P2P link identifier element.

[0023] According to one implementation of the method of the first aspect, in the method, the P2P link identifier element may include at least the following subfields: a subfield indicating the MAC address of the P2P initiator; a subfield indicating the MAC address of the P2P responder; a subfield indicating the BSSID of the P2P sender, wherein the BSSID of the P2P sender is set according to the type of the frame to be sent as follows: when sending a TDLS discovery request frame, it is set to the BSSID of the P2P initiator; when sending a TDLS discovery response frame, it is set to the BSSID of the P2P responder; when sending a TDLS establishment request frame or a TDLS establishment confirmation frame, it is set to the BSSID of the P2P initiator; when sending a TDLS establishment response frame, it is set to the BSSID of the P2P responder; and a subfield indicating the TX BSSID of the AP.

[0024] According to one implementation of the method of the first aspect, the method may further include: one of the two peer non-AP STAs is the P2P initiator, and the other of the two peer non-AP STAs is the P2P responder, wherein the P2P initiator, the P2P responder, and the AP communicate via a tunneled direct link setup (TDLS) frame; the method may further include: the P2P initiator provides a predefined TDLS discovery request frame; the predefined TDLS discovery request frame is modified by adding the P2P link identifier element to the TDLS discovery request frame to obtain a modified TDLS discovery request frame; the P2P initiator sends the modified TDLS discovery request frame to the P2P responder via the AP; the P2P responder receives the modified TDLS discovery request frame along with the address and TX of the P2P initiator. The P2P responder matches the BSSID; the P2P responder directly responds to the P2P initiator with a TDLS discovery response frame using the P2P link identifier element; the P2P initiator verifies the address and TX BSSID of the P2P initiator in the TDLS discovery response frame received from the P2P responder; the P2P initiator provides a predefined TDLS establishment request frame; the predefined TDLS discovery establishment request frame is modified by adding the P2P link identifier element to the TDLS establishment request, thereby obtaining a modified TDLS establishment request frame; the P2P initiator establishes the P2P link by sending the modified TDLS establishment request frame to the P2P responder via the AP; after receiving the modified TDLS establishment request frame via the AP, the P2P responder responds to the P2P initiator via the AP by sending a TDLS establishment response frame, and the P2P responder derives a TDLS peer key (TDLS peer key). The P2P initiator receives the TDLS establishment response frame from the P2P responder via the AP, the P2P initiator derives the TPK, and the P2P initiator responds to the P2P responder via the AP with a TDLS establishment confirmation frame.

[0025] According to one implementation of the method of the first aspect, in the method, the modified TDLS discovery request frame, the TDLS establishment request frame, the TDLS establishment response frame, and the TDLS confirmation frame can be transmitted between the P2P initiating STA and the P2P responding STA as management frames according to IEEE 802.11, wherein the management frame includes subfields according to the following table:

[0026]

[0027] A1, A2, and A3 are addresses based on IEEE 802.11, ToDS and FromDS are subfields of the frame control field, and SameLAN and DifferentLAN represent TDLS frame types, depending on whether the two peer non-AP STAs are on the same LAN or different LANs.

[0028] According to one implementation of the method of the first aspect, in the method, deriving the TPK may include: generating an input for deriving the TPK, namely TPK-Key-Input; deriving the TPK using a predefined key derivation function (KDF), wherein the KDF parameters include the TPK-Key-Input and one or more of the following: the minimum value of the MAC address values ​​of the MAC addresses of the P2P initiator and the P2P responder, the maximum value of the MAC address values ​​of the MAC addresses of the P2P initiator and the P2P responder, the P2P identifier element, the BSSID of the P2P initiator, the BSSID of the P2P responder, and the sent BSSID; wherein the BSSID of the P2P initiator is the identifier of the BSS of the corresponding P2P initiator STA, and the BSSID of the P2P responder STA is the identifier of the BSS of the P2P responder STA.

[0029] This disclosure provides a second aspect of a system for establishing direct communication between two peer non-AP STAs in a network environment comprising multiple networks, at least one access point (AP), and at least two non-AP stations (STAs). The AP is used to advertise at least two basic service sets (BSSs), wherein each BSS allows peer-to-peer (P2P) connections. Each BSS includes a corresponding BSS profile, which includes an identifier element (i.e., a P2PID element) for identifying P2P capabilities, thereby advertising the P2P capabilities to the corresponding BSS. The two peer non-AP STAs are used to discover the P2PID element and to establish a P2P connection between themselves.

[0030] According to one implementation of the system described in the second aspect, the BSS configuration file may further include a subfield indicating a P2P connection, namely a P2P connection subfield.

[0031] According to one implementation of the system of the second aspect, the system may further include: in the case of BSS co-location, the AP is used to send a separate beacon for each BSS hosted by the AP, wherein the AP is used to advertise using the separate beacon, and each of the separate beacons in the BSS profile includes an element that enables the AP to advertise BSSs that allow P2P connections, i.e., a P2P connection element.

[0032] According to one implementation of the system of the second aspect, the P2P connection element includes at least the following subfields: a subfield indicating the identifier element (i.e., the P2PID element) used to identify the P2P capability; the subfield indicating the P2P connection; and a subfield indicating the sender's BSSID (i.e., TX BSSID), wherein the TXBSSID is set to the BSSID of the P2P initiator.

[0033] According to one implementation of the system described in the second aspect, the AP can be used to advertise the at least two BSSs using multiple BSSIDs (MBSSIDs).

[0034] According to one implementation of the system described in the second aspect, the BSSID (i.e., the TX BSSID) of the sender may be equivalent to the MBSSID of the AP.

[0035] According to one implementation of the system described in the second aspect, the P2P connection subfield may include one or more of the following attributes: an attribute indicating whether the BSS advertised by the P2PID element is connected to the same LAN or a different LAN; an attribute indicating whether the P2P connection uses auto-IP in IPv4; and an attribute indicating whether the P2P connection uses IPv6.

[0036] According to one implementation of the system described in the second aspect, the identifier element used to identify the P2P can be an identifier used to identify the P2P link, i.e., a P2P link identifier element.

[0037] According to one implementation of the system described in the second aspect, the P2P link identifier element may include at least the following subfields: a subfield indicating the MAC address of the P2P initiator; a subfield indicating the MAC address of the P2P responder; a subfield indicating the BSSID of the P2P sender, wherein the BSSID of the P2P sender is set according to the frame type as follows: when sending a TDLS discovery request frame, it is set to the BSSID of the P2P initiator; when sending a TDLS discovery response frame, it is set to the BSSID of the P2P responder; when sending a TDLS establishment request frame or a TDLS establishment confirmation frame, it is set to the BSSID of the P2P initiator; when sending a TDLS establishment response frame, it is set to the BSSID of the P2P responder; and a subfield indicating the TX BSSID of the AP.

[0038] According to one implementation of the system described in the second aspect, the system may further include: one of the two peer non-AP STAs is the P2P initiator, and the other of the two peer non-AP STAs is the P2P responder, wherein the P2P initiator, the P2P responder, and the AP communicate via a tunneled direct link setup (TDLS) frame; the P2P initiator provides a predefined TDLS discovery request frame; the P2P initiator modifies the predefined TDLS discovery request frame by adding the P2P link identifier element to the TDLS discovery request frame, thereby obtaining a modified TDLS discovery request frame; the P2P initiator sends the modified TDLS discovery request frame to the P2P responder via the AP; and the P2P responder combines the received modified TDLS discovery request frame with the address and TX of the P2P initiator. The P2P responder matches the BSSID; the P2P responder uses the P2P link identifier element to directly respond to the P2P initiator with a TDLS discovery response frame; the P2P initiator verifies the address and TX BSSID of the P2P initiator in the TDLS discovery response frame received from the P2P responder; the P2P initiator provides a predefined TDLS establishment request frame; the P2P initiator modifies the predefined TDLS establishment request frame by adding the P2P link identifier element to the TDLS establishment request message, thereby obtaining a modified TDLS establishment request frame; the P2P initiator establishes the P2P link by sending the modified TDLS establishment request frame to the P2P responder via the AP; the P2P responder receives the modified TDLS establishment request frame via the AP, then responds to the P2P initiator via the AP by sending a TDLS establishment response frame, and the P2P responder derives the TDLS peer key (TDLS peer key). The P2P initiator is used to receive the TDLS establishment response message frame from the P2P responder via the AP, derive the TPK, and respond to the P2P responder via the AP with a TDLS establishment confirmation frame.

[0039] It should be noted here that the P2P connection is established after successfully receiving the TDLS establishment confirmation.

[0040] According to one implementation of the system described in the second aspect, the modified TDLS discovery request frame, the TDLS establishment request frame, the TDLS establishment response frame, and the TDLS establishment confirmation frame can be transmitted between the P2P initiating STA and the P2P responding STA as management frames according to IEEE 802.11, wherein the management frame includes subfields according to the following table:

[0041]

[0042] A1, A2, and A3 are address fields according to IEEE 802.11, ToDS and FromDS are subfields of the frame control field, and SameLAN and DifferentLAN represent TDLS frame types, depending on whether the two peer non-APSTAs are on the same LAN or on different LANs.

[0043] According to one implementation of the system described in the second aspect, the system may further include: the P2P responder deriving the TPK includes: the P2P responder generating an input for deriving the TPK, namely TPK-Key-Input; deriving the TPK using a predefined key derivation function (KDF), wherein the KDF parameters include the TPK-Key-Input and one or more of the following: the minimum value of the MAC address values ​​in the MAC addresses of the P2P initiator and the P2P responder, the maximum value of the MAC address values ​​in the MAC addresses of the P2P initiator and the P2P responder, the P2P identifier element, the BSSID of the P2P initiator, the BSSID of the P2P responder, and the sent BSSID; wherein the BSSID of the P2P initiator is the identifier of the BSS of the corresponding P2P initiator STA, and the BSSID of the P2P responder is the identifier of the BSS of the P2P responder STA.

[0044] According to one implementation of the system described in the second aspect, the system may further include: the P2P initiator deriving the TPK includes: the P2P initiator generating an input for deriving the TPK, namely TPK-Key-Input; deriving the TPK using a predefined key derivation function (KDF), wherein the KDF parameters include the TPK-Key-Input and one or more of the following: the minimum value of the MAC address values ​​in the MAC addresses of the P2P initiator and the P2P responder, the maximum value of the MAC address values ​​in the MAC addresses of the P2P initiator and the P2P responder, the P2P identifier element, the BSSID of the P2P initiator, the BSSID of the P2P responder, and the sent BSSID; wherein the BSSID of the P2P initiator is the identifier of the BSS of the corresponding P2P initiator STA, and the BSSID of the P2P responder STA is the identifier of the BSS of the P2P responder STA.

[0045] This disclosure also provides a third aspect of a system for establishing direct communication between two peer non-AP STAs in a network environment comprising multiple networks, at least one access point (AP), and at least two non-AP stations (STAs). The AP includes an announcement unit for announcing at least two basic service sets (BSSs), wherein each BSS allows peer-to-peer (P2P) connections, and each BSS includes a corresponding BSS profile including an identifier element (i.e., a P2PID element) for identifying P2P capabilities, thereby announcing the P2P capabilities to the corresponding BSS. Each of the two peer non-AP STAs includes a discovery unit for discovering the P2PID element, respectively. Each of the two peer non-AP STAs also includes a connection unit for establishing a P2P connection between the two peer non-AP STAs, respectively.

[0046] This disclosure provides a fourth aspect of a computer program product including program code, which, when executed on a computer or processor, is used to perform the method according to the first aspect.

[0047] This disclosure provides a fifth aspect of a non-transitory computer-readable medium carrying program code, which, when executed by a computer device, causes the computer device to perform the method according to the first aspect. Attached Figure Description

[0048] The embodiments of the present invention will be described in detail below with reference to the accompanying drawings, in which:

[0049] Figure 1 A known example of negotiating a TDLS peer connection between two traditional STAs is illustrated schematically.

[0050] Figure 2 A method for establishing direct communication between two peer non-access point (non-AP) stations (STAs) according to embodiments of the present disclosure is shown.

[0051] Figure 3 The P2P identifier field of the BSS profile for announcing P2P connections is shown according to an embodiment of this disclosure.

[0052] Figure 4 The following diagram illustrates the relationship between the present disclosure and embodiments thereof. Figure 3 The P2P identifier field is similar to the P2P identifier field, which includes a P2P connection subfield.

[0053] Figure 5 The following are illustrations of elements included according to embodiments of the present disclosure. Figure 4 Variations of the field.

[0054] Figure 6 An example of a P2P connection subfield according to an embodiment of this disclosure is shown.

[0055] Figure 7 An example of a P2P link identifier element according to an embodiment of this disclosure is shown.

[0056] Figure 8 An embodiment according to this disclosure is shown. Figure 7 A variant of the P2P link identifier element.

[0057] Figure 9 The protocol flow details for establishing a P2P connection according to an embodiment of this disclosure are shown.

[0058] Figure 10 A table is shown, which includes information about Figure 9 The specific addressing of the frame shown.

[0059] Figure 11 An example of a P2P connection element according to another embodiment of this disclosure is shown.

[0060] Figure 12 A system for establishing direct communication between two peer non-access point (non-AP) stations (STAs) according to an embodiment of the present disclosure is shown. Detailed Implementation

[0061] Figure 1 A known example of negotiating a TDLS peer connection between two traditional STAs is illustrated schematically.

[0062] In this known example, TDLS enables two peering non-AP STAs to establish direct communication with each other. Once a TDLS link is established, traffic flows directly between the peering STAs without bridging through the AP. TDLS can only be established between two STAs associated with an AP in the same BSS. The frame path is reduced from STA-AP-STA to STA-STA.

[0063] The above may also include TDLS security. The goal of TDLS security is to establish a direct link between legacy STA 1 and legacy STA 2 using an AP (e.g., a 2.4 GHz AP) to facilitate communication during the discovery and establishment process. STAs must be associated with the same AP within the same BSS. Once a secure connection is established, data flows directly between the two STAs without going through an access point.

[0064] The establishment of TDLS is divided into two stages: (1) TDLS discovery; (2) TDLS establishment.

[0065] TDLS discovery: The STA determines that it is communicating with a peer STA on the local LAN. This can be done at the application layer or the network layer. The STA determines that it can communicate directly with the peer STA via TDLS.

[0066] To discover whether a TDLS link can be established, the STA (e.g., traditional STA 1) sends a TDLS discovery request frame to its peer STA. The TDLS discovery request frame is then sent to the peer STA (e.g., traditional STA 2) via an AP (e.g., a 2.4 GHz AP). The peer STA, in turn, responds to the originating STA with a TDLS discovery response frame via the 2.4 GHz AP. At this point, the STA and the peer STA can determine whether they are connected to the same BSS, i.e., the same AP.

[0067] TDLS Establishment: The STA then sends a TDLS establishment request frame to the peer STA via the 2.4 GHz AP. The peer STA processes the request, derives TDLS key material (TDLS peer key), and responds to the STA with a TDLS establishment response via the AP. The STA derives its TDLS key material, successfully verifies the TDLS establishment response, and sends a TDLS establishment confirmation to the other STA via the 2.4 GHz AP. The STA verifies the TDLS establishment confirmation frame to complete the TDLS handshake.

[0068] At this point, the STA and its peer STA can communicate directly using TDLS key materials, transmitting encapsulated traffic. The STA and its peer STA can now communicate directly over a secure connection while maintaining a connection with the AP.

[0069] IEEE 802.11 includes the feature of MBSSID, enabling APs to advertise multiple co-located BSSs using a single beacon. However, since BSSs are connected to separate ESS / DS, it is unclear whether they provide connectivity to a single LAN.

[0070] and Figure 1 A relevant first use case example could be, for instance, a conference room in a company office. The conference room includes a projector connected to the company network via an access point (AP) in the conference room. The AP in the conference room advertises two networks via an MBSSID: the company network and a guest network. The company network and the guest network are connected to a separate LAN. Salespeople carrying mobile devices arrive at the company office to give a presentation. They connect their mobile devices to the guest network. The salespeople configure their mobile devices to discover and connect to the projector.

[0071] and Figure 1 A relevant second use case example could be a home scenario. In a residential environment, an access point (AP) advertises to both the home network and the guest network. The AP uses an MBSSID to advertise two BSSs, and both BSSs are connected to the same LAN. A smart TV connects to the home network in the living room. A friend of the family visits with a mobile device and wants to share videos of their trip. Their mobile device connects to the guest network. The mobile device discovers the smart TV and connects directly to it via the guest network to share the video.

[0072] Figure 2 A method for establishing direct communication between two peer non-access point (non-AP) stations (STAs) according to embodiments of the present disclosure is shown. Figure 2A method is shown for establishing direct communication between two peer non-AP STAs in a network environment comprising multiple networks, at least one access point (AP), and at least two non-AP stations (STA). Figure 2 The method includes: Step 351: The AP advertises at least two basic service sets (BSS), wherein the BSS allows peer-to-peer (P2P) connections, wherein each BSS includes a corresponding BSS profile, and the BSS profile includes an identifier element (i.e., a P2PID element) for identifying P2P capabilities, thereby advertising P2P capabilities to the corresponding BSS; Step 353: Two peer non-AP STAs discover the P2PID element; Step 355: A P2P connection is established between the two peer non-AP STAs.

[0073] Figure 3 A P2P identifier field 201 for announcing P2P connections in a BSS profile 200 according to a first embodiment of this disclosure is shown. Therefore, this embodiment relates to the P2P identifier field of a BSS announced via an MBSSID AP. It should be clear that... Figure 3 Only a portion of the BSS configuration file 200 is shown.

[0074] In more detail, Figure 3 The diagram illustrates a new P2P identifier field 201 in the BSS profile 200 used to announce BSSs that allow P2P connections. This new P2P identifier element 201 can be a field or a new element. This new P2P element can be sent by the AP hosting the BSS. Figure 3 In the example shown, the P2PID field is 1 octet in length.

[0075] Here exists a P2P identifier element 201, which announces that the BSS of the AP service can support P2P connections.

[0076] According to another embodiment, Figure 4 It shows the relationship with Figure 3 The BSS configuration file 200 is similar to the BSS configuration file 200 in the example. Figure 4 It shows the relationship with Figure 3 The P2P identifier field 201 is similar to the P2P identifier field 201. Figure 4 In the BSS configuration file 200, there is also a P2P connection subfield 203. More details... Figure 4The P2P connection subfield 203, which provides attributes for the P2P connection, is shown. One of the attributes provided for the P2P connection can be whether the BSS, advertised by the P2PID, is connected to the same LAN. Therefore, the BSS profile 200, including the P2P connection subfield 203, can be sent from a BSS-enabled AP within a beacon or probe response. More details are provided in... Figure 4 In this context, P2PID 201 enables the STA to discover which peers it can establish P2P connections with via multiple BSSs. Another possible attribute concerns IP addressing used for P2P connections. Therefore, Figure 4 An exemplary P2P identifier field 201 and P2P connection subfield 203 are shown. In this example, the P2PID field 201 is 1 octet long, and the P2P connection subfield 203 is 1 octet long.

[0077] according to Figure 4 Variations of the illustrated embodiments, Figure 5 The BSS configuration file 200' used as an element is shown. Figure 5 The BSS configuration file 200' shown includes a subfield 251' indicating the element identifier (i.e., element ID), a subfield 253' indicating the element length, and a subfield 255' indicating the element ID extension. The BSS configuration file 200' also includes... Figure 3 and Figure 4 The P2P identifier field 201 is similar to the P2P identifier field 201'. The BSS configuration file 200' also includes... Figure 4 The P2P connection subfield 203 is similar to the P2P connection subfield 203'. Therefore, the P2PID subfield 201' and the P2P connection subfield 203' can be carried as (sub)fields in the new element (i.e., BSS profile 200'). This is useful when the BSS is not advertised using MBSSID (i.e., using a separate beacon frame). Subfields 201' and 203' can be included in the new element (i.e., BSS profile 200') or included in an existing element.

[0078] Figure 6 It further shows that, for Figure 4 The P2P connection subfield 203 shown or similar Figure 5The subfield 203' shown can be defined as follows: The P2P connection subfield 203 includes a subfield indicating whether the BSS advertised by the P2P identifier is on a LAN, namely, the LAN subfield 213. The P2P connection subfield 203 includes a subfield indicating whether the P2P connection uses Auto-IP in IPv4, namely, the Auto-IP subfield 215. The P2P connection subfield 203 also includes a subfield indicating whether the P2P connection uses IPv6, namely, the IPv6 subfield 217. Here,

[0079] The bits in subfield 213 indicate that the BSS advertised by the P2P identifier is connected to the same LAN. Here, a value of 0 indicates different LANs; a value of 1 indicates the same LAN.

[0080] The bits in subfield 215 indicate whether the P2P connection uses auto-IP in IPv4.

[0081] The bits in subfield 217 indicate whether the P2P connection uses IPv6.

[0082] In this embodiment, such as Figure 4 , Figure 5 and Figure 6 As shown, the P2PID (see P2PID elements 201, 201') provides the STA with an indication that the BSS supports a specific P2P. If two STAs can discover the same P2PID (possibly in different BSSs), a P2P connection can be established between the two STAs.

[0083] P2P connection subfield 203 can provide the STA with additional information about the LAN's architecture / topology and whether IPv4 or IPv6 is being used.

[0084] Figure 7 An example of a P2P link identifier element 250 according to an embodiment of this disclosure is shown. Previous embodiments relate to the announcement and discovery of P2P connections. Here, this embodiment relates to the establishment of a P2P connection. The P2P link identifier element 250 provides peer STA information for establishing a P2P connection. Since this embodiment describes the next step in the connection process after announcement and discovery, it relates to the previous embodiments.

[0085] exist Figure 7 In this context, a P2P link identifier element 250 is added to the existing TDLS discovery and establishment frame. The P2P link identifier element 250 provides information to peer STAs capable of establishing P2P connections. More specifically, in Figure 7In the example of the P2P link identifier element 250 shown, the P2P link identifier element 250 includes:

[0086] Including the MAC address of the P2P initiator (subfield 257)

[0087] Including the MAC address of the P2P responder (subfield 259)

[0088] This includes subfield 261 of the P2P sender BSSID, where the P2P sender BSSID is conditional, specifically depending on the sender of the frame.

[0089] For TDLS discovery request frames, the P2P sender's BSSID is set to the P2P initiator's BSSID;

[0090] For TDLS discovery response frames, the P2P sender's BSSID is set to the P2P responder's BSSID;

[0091] For TDLS establishment requests / acknowledgments, the P2P sender's BSSID is set to the P2P initiator's BSSID;

[0092] For TDLS establishment response frames, the P2P sender's BSSID is set to the P2P responder's BSSID;

[0093] The subfield 263 indicates the AP's TX BSSID.

[0094] Figure 7 The P2P link identifier element 250 shown also includes a subfield 251 indicating the element identifier (i.e., element ID 251), a subfield 253 indicating the element length, and a subfield 255 indicating the element ID extension.

[0095] therefore, Figure 7 The P2P link identifier element 250 shown provides addressing and other information that enables two peer STAs to establish a P2P connection between them.

[0096] It should be understood that P2P connections can be established by reusing existing TDLS discovery and establishment frames, leveraging [the technology / methods]. Figure 7 Similar to the additional new P2P link identifier element described in the embodiments.

[0097] Figure 8 An embodiment according to this disclosure is shown. Figure 7A variant of the P2P link identifier element. Figure 8 The image shows P2P link identifier element 250'. This P2P link identifier element 250' is related to... Figure 7 The P2P link identifier element 250 includes the same element, but Figure 8 Element 250' also includes a P2P identifier field 201 and a P2P connection subfield 203 (see Figure 3 , Figure 4 and Figure 5 The P2P link identifier element 250' can be exchanged between peers.

[0098] Figure 9 The protocol flow details for establishing a P2P connection according to an embodiment of this disclosure are shown. Figure 9 The diagram illustrates the communication between AP 100 (denoted as MBSSID AP), which is capable of sending MBSSID, and a first STA 101, which acts as the P2P initiator STA, and a second STA 102, which acts as the P2P responder STA. It should be understood that the roles of STA 101 and STA 102 can be interchanged. Figure 9 The steps are described below:

[0099] In step 701, the P2P initiator 101 discovers the P2P responder 102 via the LAN, and the MBSSID AP 100 communicates with each of STA 101 and STA 102 respectively. It should be noted that if the peer STA 101 and STA 102 are operating on different LANs, the IP Service Advertisement Protocol can be used; alternatively, the P2P initiator and P2P responder can establish an IP connection on the network.

[0100] In step 703, the P2P initiator 101 sends a TDLS discovery request frame to the P2P responder 102. The TDLS discovery request frame includes a P2P link identifier element and is sent through MBSSID AP 100.

[0101] In step 705, the P2P responder 102 receives the TDLS discovery request frame sent by the P2P initiator 101 through the MBSSID AP 100.

[0102] In step 706, the P2P responder 102 processes the received TDLS discovery request frame. That is, the P2P responder 102 matches the address and TX BSSID of the P2P responder 102.

[0103] In step 707, P2P responder 102 responds to the TDLS discovery request frame by directly sending a TDLS discovery response frame to P2P initiator 101. Here, directly sending the TDLS discovery response frame means that the TDLS discovery response frame is not sent to P2P initiator 101 via MBSSID AP 100 using the P2P link identifier element, but rather communication occurs directly between P2P responder 102 and P2P initiator 101.

[0104] In step 708, the P2P initiator 101, which directly receives the TDLS discovery response frame from the P2P responder 102, processes the TDLS discovery response frame. That is, the P2P initiator 101 verifies its address and TX BSSID in the received TDLS discovery response frame and initiates a connection with the P2P responder 102. Therefore, the P2P initiator 101 begins link establishment. In step 709, the P2P initiator 101 sends a TDLS establishment request frame to the P2P responder 102 via the MBSSID AP 100.

[0105] MBSSID AP 100 sends a TDLS establishment request frame to P2P responder 102. In step 711, P2P responder 102 receives the TDLS establishment request frame.

[0106] In step 713, P2P responder 102 replies to P2P initiator 101 via MBSSID AP 100 using TDLS to establish a response frame. In step 714, P2P responder 102 derives TPK.

[0107] In step 715, P2P initiator 101 receives a TDLS establishment response frame sent via MBSSID AP 100 from P2P responder 102. In step 716, P2P initiator 101 derives TPK. Then, in step 717, P2P initiator 101 replies with a TDLS establishment acknowledgment frame sent via MBSSID AP 100. In step 719, P2P responder receives the TDLS establishment acknowledgment frame.

[0108] Finally, in step 721, direct P2P communication is established between P2P initiator 101 and P2P responder 102.

[0109] Therefore, P2P connections can be established between peer STAs using the modified TDLS frames.

[0110] about Figure 9 Implementation examples, Figure 10 A table is shown, which includes information about Figure 9 The specific addressing of the frame shown.

[0111] Existing TDLS mechanisms use data frames of Ethernet type 89-0d and payload type 2 to transmit TDLS discovery request frames and TDLS establishment request / response / acknowledgment frames. For brevity, the term "frame" will be omitted hereafter, and they will be referred to simply as TDLS discovery request and TDLS establishment request / response / acknowledgment. For P2P connections, enhanced TDLS frames will be reused using new payload type values. Figure 10 The IEEE 802.11 A1, A2, and A3 addresses and their values ​​are shown according to this disclosure.

[0112] Each row in Table 10 represents one of the TDLS discovery request and TDLS establishment request / response / acknowledgment, followed by a P2P data frame. Values ​​for subfields A1, A2, and A3 are given. For simplicity, the P2P responder is referred to as the responder, and the P2P initiator as the initiator. Furthermore, in Figure 10 The table values ​​for the ToDS and FromDS subfields are provided. ToDS and FromDS are subfields of the frame control field. Furthermore, in... Figure 10 In the table, SameLAN and DifferentLAN represent TDLS frame types, depending on whether the two peer non-AP STAs are on the same LAN or on different LANs.

[0113] therefore, Figure 10 The P2P addressing shown facilitates the reuse of existing TDLS frames for P2P connections.

[0114] like Figure 9 As shown, the P2P responder and the P2P initiator each derive their TPK. Here, the security of the P2P link depends on the MBSSID AP, the P2P initiator's BSS, and the P2P responder's BSS. Key derivation should reflect these attributes.

[0115] An example TPK is generated as follows:

[0116] TPK-Key-Input = Hash(min (SNonce, ANonce) || max (SNonce, ANonce))

[0117] TPK = KDF-Hash-Length(TPK-Key-Input, “P2P Setup PMK”, min (MAC_I,MAC_R) || max (MAC_I, MAC_R) || Initiator BSSID || Responder BSSID ||P2P Identifier || BSSID_Initiator || BSSID_Responder || Transmitted BSSID )

[0118] Here, regarding this disclosure Figure 9 and Figure 10 The new value has been underlined. The keyderivation function (KDF) conforms to IEEE 802.11. Furthermore, "||" represents the "OR" operator.

[0119] The values ​​are as follows:

[0120] In the prior art, the values ​​MAC_I and MAC_R are set to the MAC addresses of the P2P initiator and P2P responder.

[0121] The BSSID of the P2P initiator and the P2P responder is the BSS of the corresponding P2P initiator and the P2P responder STA.

[0122] The transmitted BSSID is the BSSID transmitted by the AP, i.e., MBSSID.

[0123] Here, TPK derivation can include a subset of P2P identifiers, the BSSID of the P2P initiator / responder, and the BSSID sent. It should be understood that one or more new values ​​can be used. Furthermore, it is not necessary to use all new values.

[0124] In this way, the security key of the established P2P connection is bound to the P2P initiator, the responder, and the intermediate AP hosting the BSS.

[0125] Figure 11 Another possibility involves establishing P2P connections. The AP advertising a co-located BSS can send a separate beacon for each hosted BSS. In this case, the MBSSID element is not required to advertise multiple BSSs.

[0126] In this case, there is no TX BSSID, that is, to carry the MBSSID element, so the TX BSSID is set to the BSSID of the initiating peer STA.

[0127] therefore, Figure 11 A P2P connection element 204 is shown that enables the AP to advertise the BSS that allows P2P connections. The P2P connection element 204 advertises via a separate beacon or probe response. Figure 11 An exemplary P2P connection element 204 is shown in the figure.

[0128] exist Figure 11In the P2P connection element 204, there are subfields 205 indicating the element ID and 207 indicating the element length. The P2P connection element 204 also includes... Figure 3 , Figure 4 and Figure 5 The P2PID subfield is similar to the P2PID subfield 201. Figure 11 The P2P connection element 204 also includes a P2P connection subfield 203. The P2P connection element 204 also includes a subfield 211 indicating the sender's BSSID. Here, the subfield 211 indicating the TX BSSID includes a common transmission BSSID used for exchanging P2P frames between peer STAs. The peer STA will use the address provided in the subfield indicating the TX BSSID as the transmission BSSID.

[0129] Therefore, in Figure 11 In this case, the TX BSSID address will be used in the same way as the BSSID sent by the AP when it uses MBSSID to advertise the BSS.

[0130] Therefore, when BSSs are co-located within the same AP, P2P connection element 204 can be transmitted within multiple beacon frames.

[0131] Figure 12 A system 20 according to another embodiment of the present disclosure is shown. Figure 12 System 20 is a system for establishing direct communication between two peer non-AP STAs in a network environment comprising multiple networks, at least one access point (AP), and at least two non-AP stations (STAs). Figure 12 In this configuration, the AP includes an announcement unit 2501, which announces at least two basic service sets (BSSs) that allow peer-to-peer (P2P) connections. Each BSS includes a corresponding BSS configuration file, which includes an identifier element (i.e., a P2PID element) for identifying P2P capabilities, thereby announcing P2P capabilities to the corresponding BSS. Each of the two peer non-AP STAs includes a discovery unit 2503, which discovers the P2PID element for each of the two peer non-AP STAs. Each of the two peer non-AP STAs also includes a connection unit 2505, which establishes a P2P connection between the two peer non-AP STAs.

[0132] Abbreviations

[0133] AKM Authentication and Key Management

[0134] DA (Destination Address)

[0135] DL downlink

[0136] EHT (Extremely High Throughput)

[0137] LAN (Local Area Network)

[0138] RA Receiver address

[0139] RSNE (Robust Security Network Element)

[0140] Security Association (SA)

[0141] SAP service access point

[0142] STA station

[0143] TA (transmitter address)

[0144] TDLS tunneled direct link setup

[0145] TG task group

[0146] TPK TDLS key derivation

[0147] UL uplink

[0148] WLAN (Wireless Local Area Network)

Claims

1. A method for establishing direct communication between two peer non-AP STAs in a network environment comprising multiple networks, at least one access point (AP), and at least two non-AP STAs, the method comprising: (351) The AP advertises at least two Basic Service Sets (BSS), wherein the BSS allows point-to-point (P2P) connections. Each BSS includes a corresponding BSS configuration file (200), which includes an identifier element (P2PID element (201)) for identifying P2P capabilities, thereby announcing the P2P capabilities to the corresponding BSS. (353) The two equivalent non-AP STAs discover the P2PID element (201); (353) Establish a P2P connection between the two peer non-AP STAs.

2. The method according to claim 1, wherein, The BSS configuration file also includes a subfield indicating a P2P connection, the P2P connection subfield (203).

3. The method according to claim 2, wherein, In the case of BSS co-location, the AP sends a separate beacon for each BSS hosted by the AP, wherein the AP uses the separate beacon for advertising, and each of the separate beacons in the BSS profile includes an element that enables the AP to advertise BSSs that allow P2P connections, P2P connection, P2P connection element (204).

4. The method according to claim 3, wherein, The P2P connection element (204) includes at least the following subfields: Indicates a subfield (201) of the identifier element (the P2PID element (201)) used to identify the P2P capability. The subfield (203) that indicates the P2P connection; The subfield (211) indicates the sender's BSSID (TX BSSID), wherein the TX BSSID is set to the BSSID of the P2P initiator.

5. The method according to claim 1 or 2, wherein, The AP uses multiple BSSIDs (MBSSIDs) to advertise the at least two BSSs.

6. The method according to claim 5, wherein, The sender's BSSID (TX BSSID) is equivalent to the AP's MBSSID.

7. The method according to claim 6, wherein, The P2P connection subfield (203) includes one or more of the following attributes: Indicates whether the BSS, announced by the P2PID element (201), is connected to the same LAN or a different LAN; Indicates whether the P2P connection uses the auto-IP attribute in IPv4; This indicates whether the P2P connection uses an IPv6 attribute.

8. The method according to any one of claims 1 to 7, wherein, The identifier element (201) used to identify the P2P is an identifier used to identify the P2P link, P2P link identifier element (250).

9. The method according to claim 8, wherein, The P2P link identifier element (250) includes at least the following subfields: The subfield (257) indicates the MAC address of the P2P initiator. The subfield (259) indicates the MAC address of the P2P responder; The subfield (261) indicates the BSSID of the P2P sender, wherein the BSSID of the P2P sender is set according to the frame type as follows: When sending a TDLS discovery request frame, set it to the BSSID of the P2P initiator; When sending a TDLS discovery response frame, set it to the BSSID of the P2P responder; When sending a TDLS establishment request frame or a TDLS establishment confirmation frame, set it to the BSSID of the P2P initiator; When sending a TDLS establishment response frame, set it to the BSSID of the P2P responder; The subfield (263) indicates the TX BSSID of the AP.

10. The method according to claim 9, wherein, Also includes: One of the two peer non-AP STAs is the P2P initiator (101), and the other non-AP STA is the P2P responder (102). The P2P initiator (101), the P2P responder (102), and the AP (100) communicate via a TDLS frame established through a direct channel link. The method further includes: The P2P initiator (101) provides a predefined TDLS discovery request frame; The predefined TDLS discovery request frame is modified by adding the P2P link identifier element to the TDLS discovery request frame, thereby obtaining the modified TDLS discovery request frame. The P2P initiator (101) sends the modified TDLS discovery request frame to the P2P responder (102) via the AP; The P2P responder (102) matches the received modified TDLS discovery request frame with the address and TX BSSID of the P2P initiator (101); The P2P responder (102) uses the P2P link identifier element to directly respond to the P2P initiator (101) with a TDLS discovery response frame. The P2P initiator (101) verifies the address and TX BSSID of the P2P initiator (101) in the TDLS discovery response frame received from the P2P responder (102); The P2P initiator (101) provides a predefined TDLS establishment request frame; The predefined TDLS discovery establishment request frame is modified by adding the P2P link identifier element to the TDLS establishment request frame, thereby obtaining the modified TDLS establishment request frame. The P2P initiator (101) establishes the P2P link by sending the modified TDLS establishment request frame to the P2P responder (102) via the AP; After receiving the modified TDLS establishment request frame via the AP, the P2P responder (102) responds to the P2P initiator (101) via the AP by sending a TDLS establishment response frame, and the P2P responder (102) derives the TDLS peer key TPK. The P2P initiator (101) receives the TDLS establishment response frame from the P2P responder (102) via the AP. The P2P initiator (101) derives the TPK and responds to the P2P responder (102) via the AP with a TDLS establishment confirmation frame.

11. The method according to claim 10, wherein, The modified TDLS discovery request frame, the TDLS establishment request frame, the TDLS establishment response frame, and the TDLS confirmation frame are transmitted between the P2P initiator STA (101) and the P2P responder STA (102) as management frames according to IEEE 802.11, wherein the management frame includes subfields according to the following table: A1, A2, and A3 are addresses based on IEEE 802.11, ToDS and FromDS are subfields of the frame control field, and SameLAN and DifferentLAN represent TDLS frame types, depending on whether the two peer non-AP STAs are on the same LAN or different LANs.

12. The method according to claim 10 or 11, wherein, The derived TPK includes: Generate the input used to derive the TPK, TPK-Key-Input; The TPK is derived using the predefined key derivation function KDF. The KDF parameters include the TPK-Key-Input and one or more of the following: the minimum value of the MAC address in the MAC address of the P2P initiator (101) and the P2P responder (102), the maximum value of the MAC address in the MAC address of the P2P initiator (101) and the P2P responder (102), the P2P identifier element, the BSSID of the P2P initiator (101), the BSSID of the P2P responder (102), and the BSSID sent. Wherein, the BSSID of the P2P initiator (101) is the identifier of the BSS of the corresponding P2P initiator STA (101), and the BSSID of the P2P responder (102) is the identifier of the BSS of the P2P responder STA (102).

13. A system for establishing direct communication between two peer non-AP STAs in a network environment comprising multiple networks, at least one access point (AP), and at least two non-AP stations (STAs), wherein, The AP is used to advertise at least two Basic Service Sets (BSS), wherein the BSS allows peer-to-peer (P2P) connections. Each BSS includes a corresponding BSS configuration file, which includes an identifier element (P2PID element (201)) for identifying P2P capabilities, thereby announcing the P2P capabilities to the corresponding BSS. The two equivalent non-AP STAs are used to discover the P2PID element (201). The two peer non-AP STAs are used to establish a P2P connection between the two peer non-AP STAs.

14. The system according to claim 13, wherein, The BSS configuration file also includes a subfield indicating a P2P connection, the P2P connection subfield (203).

15. The system according to claim 14, wherein, In the case of BSS co-location, the AP is used to send a separate beacon for each BSS hosted by the AP, wherein the AP is used to advertise using the separate beacon, and each of the separate beacons in the BSS profile includes an element that enables the AP to advertise BSSs that allow P2P connections, a P2P connection element (204).

16. The system according to claim 15, wherein, The P2P connection element (204) includes at least the following subfields: Indicates a subfield of the identifier element (the P2PID element (201)) used to identify the P2P capability; The subfield indicating the P2P connection; A subfield indicating the sender's BSSID (TX BSSID), wherein the TX BSSID is set to the BSSID of the P2P initiator (101).

17. The system according to claim 13 or 14, wherein, The AP is used to advertise the at least two BSSs using multiple BSSIDs (MBSSIDs).

18. The system according to claim 17, wherein, The sender's BSSID (TX BSSID) is equivalent to the AP's MBSSID.

19. The system according to claim 18, wherein, The P2P connection subfield (203) includes one or more of the following attributes: Indicates whether the BSS, announced by the P2PID element (201), is connected to the same LAN or a different LAN; Indicates whether the P2P connection uses the auto-IP attribute in IPv4; This indicates whether the P2P connection uses an IPv6 attribute.

20. The system according to any one of claims 13 to 19, wherein, The identifier element used to identify the P2P is an identifier used to identify the P2P link, namely the P2P link identifier element.

21. The system according to claim 20, wherein, The P2P link identifier element includes at least the following subfields: A subfield indicating the MAC address of the P2P initiator (101); A subfield indicating the MAC address of the P2P responder (102); A subfield indicating the BSSID of the P2P sender, wherein the BSSID of the P2P sender is set according to the frame type as follows: When a TDLS discovery request frame is sent, the BSSID of the P2P initiator (101) is set; In the case of sending a TDLS discovery response frame, set it to the BSSID of the P2P responder (102); When sending a TDLS establishment request frame or a TDLS establishment confirmation frame, set it to the BSSID of the P2P initiator (101); When sending a TDLS establishment response frame, set it to the BSSID of the P2P responder (102); The subfield indicating the TX BSSID of the AP.

22. The system according to claim 21, wherein, Also includes: One of the two peer non-AP STAs is the P2P initiator, and the other of the two peer non-AP STAs is the P2P responder. The P2P initiator (101), the P2P responder (102), and the AP communicate by establishing TDLS frames via a direct channel link. The P2P initiator (101) is used to provide a predefined TDLS discovery request frame; The P2P initiator (101) is used to modify the predefined TDLS discovery request frame by adding the P2P link identifier element to the TDLS discovery request frame, thereby obtaining the modified TDLS discovery request frame. The P2P initiator (101) is used to send the modified TDLS discovery request frame to the P2P responder (102) via the AP; The P2P responder (102) is used to match the received modified TDLS discovery request frame with the address and TX BSSID of the P2P initiator (101); The P2P responder (102) is used to directly respond to the P2P initiator (101) using the P2P link identifier element in a TDLS discovery response frame. The P2P initiator (101) is used to verify the address and TX BSSID of the P2P initiator (101) in the TDLS discovery response frame received from the P2P responder (102); The P2P initiator (101) is used to provide a predefined TDLS establishment request frame; The P2P initiator (101) is used to modify the predefined TDLS discovery establishment request frame by adding the P2P link identifier element to the TDLS establishment request message, thereby obtaining the modified TDLS establishment request frame. The P2P initiator (101) is used to establish the P2P link by sending the modified TDLS establishment request frame to the P2P responder (102) via the AP; The P2P responder (102) is used to receive the modified TDLS establishment request frame via the AP, and then respond to the P2P initiator (101) via the AP by sending a TDLS establishment response frame. The P2P responder (102) is also used to derive the TDLS peer key TPK. The P2P initiator (101) is used to receive the TDLS establishment response frame from the P2P responder (102) via the AP, derive the TPK, and respond to the P2P responder (102) via the AP with a TDLS establishment confirmation frame.

23. The system according to claim 22, wherein, The modified TDLS discovery request frame, the TDLS establishment request frame, the TDLS establishment response frame, and the TDLS confirmation frame are transmitted as management frames according to IEEE 802.11 between the P2P initiator STA (101) and the P2P responder STA (102), wherein the management frame includes subfields according to the following table: A1, A2, and A3 are addresses based on IEEE 802.11, ToDS and FromDS are subfields of the frame control field, and SameLAN and DifferentLAN represent TDLS frame types, depending on whether the two peer non-AP STAs are on the same LAN or different LANs.

24. The system according to claim 22 or 23, wherein, The P2P responder (102) for deriving the TPK includes: The P2P responder (102) for: Generate the input used to derive the TPK, TPK-Key-Input; The TPK is derived using the predefined key derivation function KDF. The KDF parameters include the TPK-Key-Input and one or more of the following: the minimum value of the MAC address in the MAC address of the P2P initiator (101) and the P2P responder (102), the maximum value of the MAC address in the MAC address of the P2P initiator (101) and the P2P responder (102), the P2P identifier element, the BSSID of the P2P initiator (101), the BSSID of the P2P responder (102), and the BSSID sent. Wherein, the BSSID of the P2P initiator (101) is the identifier of the BSS of the corresponding P2P initiator STA (101), and the BSSID of the P2P responder (102) is the identifier of the BSS of the P2P responder STA (102).

25. The system according to any one of claims 22 to 24, wherein, The P2P initiator (101) is used to derive the TPK, including: The P2P initiator (101) is used to: Generate the input used to derive the TPK, TPK-Key-Input; The TPK is derived using the predefined key derivation function KDF. The KDF parameters include the TPK-Key-Input and one or more of the following: the minimum value of the MAC address in the MAC address of the P2P initiator (101) and the P2P responder (102), the maximum value of the MAC address in the MAC address of the P2P initiator (101) and the P2P responder (102), the P2P identifier element, the BSSID of the P2P initiator (101), the BSSID of the P2P responder (102), and the BSSID sent. Wherein, the BSSID of the P2P initiator (101) is the identifier of the BSS of the corresponding P2P initiator STA (101), and the BSSID of the P2P responder (102) is the identifier of the BSS of the P2P responder STA (102).

26. A system (20) for establishing direct communication between two peer non-AP STAs in a network environment comprising multiple networks, at least one access point (AP), and at least two non-AP stations (STAs), wherein, The AP includes an announcement unit (2501), wherein the announcement unit (2501) is used to announce at least two Basic Service Sets (BSS), wherein the BSS allows peer-to-peer (P2P) connections. Each BSS includes a corresponding BSS configuration file, which includes an identifier element (P2PID element (201)) for identifying P2P capabilities, thereby announcing the P2P capabilities to the corresponding BSS. Each of the two peer non-AP STAs includes a discovery unit (2503), wherein the discovery unit of each of the two peer non-AP STAs is used to discover the P2PID element (201) respectively. Each of the two peer non-AP STAs includes a connection unit (2505), wherein each connection unit (2505) is used to establish a P2P connection between the two peer non-AP STAs respectively.

27. A computer program product, wherein, The computer program product includes program code that, when executed on a computer or processor, performs the method according to any one of claims 1 to 12.

28. A non-transitory computer-readable medium, wherein, The computer-readable storage medium carries program code that, when executed by a computer device, causes the computer device to perform the method according to any one of claims 1 to 12.

Images