Cross-device wireless communication method

Abstract

The invention relates to the field of communication, and discloses a cross-device wireless communication method, which comprises the following steps of: broadcasting a multi-basic service set identifier device MBTD search request frame after an NAP (Network Access Point) is started; receiving an MBTD search response frame sent by a main wireless communication access point MAP in the target MBTD set; according to the signal strength of the MBTD search response frame, the maximum number of access point devices supported by the MAP, the number of occupied access point devices and the BI, whether the target MBTD set is accessed or not is judged; if the target MBTD set is determined to be accessed, sending an MBTD access request frame to the MAP; receiving an MBTD access response frame sent by the MAP; if the access information in the MBTD access response frame indicates that the NAP is accessed, the NAP is in the target MBTD set and is used as the slave wireless communication access point SAP of the MAP, the method and the device enable a plurality of wireless communication access points in the same air interface environment to form the MBTD set, and the MBTD set can pass through the Beacon Frame of the MBSSID of cross equipment, so that the Beacon Frame in the air interface environment is greatly reduced, and the data transmission utilization rate is greatly improved.

Description

Technical Field

[0001] The embodiments of the present application relate to the field of communications, and in particular to a cross-device wireless communication method. Background Art

[0002] As Wi-Fi (Wireless Fidelity) communication becomes the mainstream device for current home communications, the air interface communication environment has become more crowded. According to the Wi-Fi protocol, each AP (Access Point) must continuously broadcast Beacon Frames (beacon frames used to broadcast its own information) to indicate its existence and performance parameters so that STA (Station) can discover and connect to it. Under normal circumstances, each AP sends a Beacon Frame once every 100ms by default. A general home may have multiple APs, and an AP may have multiple VAPs; in addition, Beacon Frames from multiple neighboring APs and VAPs can be received around the home. This causes the air interface environment to be occupied by a large number of Beacon Frames, and the actual data transmission utilization rate is not high.

[0003] In order to better solve the above problems, Multiple BSSID (Multiple Basic Service Set Identifiers) are designed in the new Wi-Fi protocol, which aims to allow the AP to send out the Beacon Frames of the VAPs under it in one Beacon Frame, which can greatly reduce the number of Beacon Frames in the air interface environment, so as to make more channel resources available for data transmission. Even though Multiple BSSID can reduce the Beacon Frames of VAPs, a family may have multiple APs, and there are multiple APs in the same space for several neighbors, and the spaces adjacent to multiple APs are not far away, resulting in a large number of Beacon Frames in the air interface environment and a low data transmission utilization rate. Summary of the invention

[0004] The purpose of the embodiments of the present application is to provide a cross-device wireless communication method to reduce the number of Beacon Frames in an air interface environment and improve data transmission utilization.

[0005] In order to solve the above technical problems, an embodiment of the present application provides a cross-device wireless communication method, which is applied to a new wireless communication access point NAP, including: after the NAP is started, broadcasting a multi-basic service set identifier device MBTD search request frame; wherein the MBTD search request frame is a request frame newly created by the NAP and includes the MBSSID of the NAP and load capacity information; receiving an MBTD search response frame sent by a main wireless communication access point MAP in a target MBTD set; wherein the MBTD search response frame is a response frame newly created by the main wireless communication access point MAP and includes the maximum number of access point devices supported by the MAP, the number of occupied access point devices, and the beacon frame sending interval BI; according to the signal strength of the MBTD search response frame, the access point devices supported by the MAP, The maximum number of access point devices, the number of occupied access point devices and the BI are used to determine whether to access the target MBTD set; if it is determined to access the target MBTD set, an MBTD access request frame is sent to the MAP; wherein the MBTD access request frame is a request frame newly created by the NAP and contains the MBSSID of the NAP and the VAP corresponding to the NAP, the number of the VAP corresponding to the NAP and load capacity information; an MBTD access response frame is received from the MAP; wherein the MBTD access response frame is a response frame newly created by the MAP and contains access information; if the access information in the MBTD access response frame indicates that the NAP has been accessed, the NAP is in the target MBTD set and serves as a slave wireless communication access point SAP of the MAP.

[0006] The embodiment of the present application also provides a cross-device wireless communication method, which is applied to a main wireless communication access point MAP, including: receiving a multi-basic service set identifier device set MBTD search request frame broadcasted by a new wireless communication access point NAP; wherein the MBTD search request frame is a request frame newly created by the NAP and includes the MBSSID and load capacity information of the NAP; the new wireless communication access point NAP is used to execute any of the cross-device wireless communication methods described above; according to the MBSSID and load capacity information of the NAP, determining whether to allow the NAP to access the target MBTD set where the MAP is located; if the NAP is allowed to access the target MBTD set, sending an MBTD search response frame to the NAP; wherein the MBTD search response The response frame is a response frame newly created by the MAP and includes the maximum number of access point devices supported by the MAP, the number of occupied access point devices and the beacon frame sending interval BI; the MBTD access request frame sent by the NAP is received; wherein the MBTD access request frame is a request frame newly created by the NAP and includes the MBSSID of the NAP and the virtual wireless communication access point VAP corresponding to the NAP, the number of VAPs corresponding to the NAP and load capacity information; the NAP is added to the target MBTD set, and the NAP serves as the slave wireless communication access point SAP of the MAP, and sends an MBTD access response frame to the SAP; wherein the MBTD access response frame is a response frame newly created by the MAP and includes access information.

[0007] In this application, the physical AP not only needs to package its own VAP into the MBSSID, but also needs to form a device set MBTD with other physical APs in the air interface environment. In this set, the MAP is responsible for forming an MBSSID of all physical APs and their VAPs in the set and broadcasting it through Beacon Frame. Through this method, the number of Beacon Frames in the air interface environment can be greatly reduced, and the data transmission utilization rate can be improved. BRIEF DESCRIPTION OF THE DRAWINGS

[0008] Figure 1 It is a structural diagram of a cross-device wireless communication system provided by an embodiment of the present application;

[0009] Figure 2 It is a flowchart of a first cross-device wireless communication method provided in an embodiment of the present application;

[0010] Figure 3 It is a flowchart of a second cross-device wireless communication method provided in an embodiment of the present application;

[0011] Figure 4It is a flowchart of a third cross-device wireless communication method provided in an embodiment of the present application;

[0012] Figure 5 It is a structural diagram of a cross-device wireless communication apparatus provided in an embodiment of the present application;

[0013] Figure 6 is a flowchart of a fourth cross-device wireless communication method provided in an embodiment of the present application;

[0014] Figure 7 is a flowchart of a fifth cross-device wireless communication method provided in an embodiment of the present application;

[0015] Figure 8 is a flowchart of a sixth cross-device wireless communication method provided in an embodiment of the present application;

[0016] Fig. 9 It is a flowchart of the seventh cross-device wireless communication method provided in an embodiment of the present application. DETAILED DESCRIPTION

[0017] The basic communication system usually includes: a wireless router and a wireless communication terminal. Among them, the wireless router is responsible for the operation of the entire communication system. The AP (Access Point, access point / wireless communication access point) is located in the wireless router, responsible for the part related to Wi-Fi communication in the system, and establishes a Wi-Fi connection with the STA (Station: Wi-Fi terminal / wireless communication terminal). The AP can create at least one VAP (Virtual Access Point, virtual access point / virtual wireless communication access point), which is responsible for establishing a Wi-Fi connection with the wireless communication terminal. Of course, the AP may not create a VAP. The wireless communication terminal is responsible for establishing a Wi-Fi connection with the AP and the VAP. In order to make the solution of the present application clearer, the basic technology is continued to be described. The steps of a wireless communication method of the basic technology include: Step T101, the router system is started. Step T102, the AP group package includes a Beacon Frame of Multiple BSSID. Step T103, the AP sends a Beacon Frame. Step T104, the AP receives the ProbeRequest Frame sent by the STA. Step T105, the AP group package includes a Probe ResponseFrame of Multiple BSSID. In step T106, the AP sends a Probe Response Frame to the STA. In step T107, the above process is repeated until the router system ends. In basic technology, the AP is responsible for sending Beacon Frames including Multiple BSSIDs to the STA; at the same time, it replies to the Probe Request Frame of the STA through the Probe Response Frame. Although Multiple BSSID can significantly reduce the Beacon Frames of the VAP, a family may have multiple APs, and there are multiple APs in the same space for several neighbors, and their adjacent spaces are not far away. MBSSID only centrally manages the Beacons of the AP and VAP under one AP, and fails to uniformly manage the Beacons of multiple APs in the same space, resulting in a large number of Beacon Frames in the air interface environment and low data transmission utilization.

[0018] In order to solve the above technical problems, the present application provides a cross-device wireless communication system and a corresponding communication method. In order to make the present application solution clearer, the terms are first explained, as shown in Table 1 below.

[0019] Table 1

[0020]

[0021] The embodiment of the present application provides a cross-device wireless communication system. Figure 1 is a schematic diagram of the structure of a cross-device wireless communication system provided in an embodiment of the present application, such as Figure 1 The cross-device wireless communication system includes: a master wireless communication access point (Master AP, MAP) D101, a slave wireless communication access point (Slave AP, SAP) D201, and a new wireless communication access point (New AP, NAP) D301. The master wireless communication access point D101 and all the slave wireless communication access points D201 connected to it form an MBTD set.

[0022] Among them, MAP, as the main control AP in the MBTD Set, becomes the Master, responsible for assembling the MBSSID across devices and broadcasting the MTDB Beacon Frame. SAP, as the Salve in the MBTD Set, is the AP that joins the MBTD Set, such as the AP of a new router that joins the Set, rather than the VAP of the router. NAP is a newly started AP in the air interface environment that has not joined the MBTD Set. After joining, it can serve as the Salve of MBTD; NAP can also independently create a set as the Master of the MBTD Set. VAP serves as the VAP of the Master AP or the Slave AP or the VAP of the New AP. In the embodiment of the present application, it does not participate in events and is only used to form the MBSSID and is managed by its AP.

[0023] MAP is responsible for the operation of the MBTD centralized Master router system. The wireless communication access point (AP) D102 in MAP is located in MAP and is responsible for the Wi-Fi communication-related part of the system, and is used to establish a Wi-Fi connection with the STA. The virtual wireless communication access point (VAP) D103 in MAP is responsible for establishing a Wi-Fi connection with the STA. SAP is responsible for the operation of the MBTD centralized Salve router system. The wireless communication access point (AP) D202 in SAP is located in SAP and is responsible for the Wi-Fi communication-related part of the system, and is used to establish a Wi-Fi connection with the STA. The virtual wireless communication access point (VAP) D203 in SAP is responsible for establishing a Wi-Fi connection with the STA. NAP is a new router in the air interface environment and is responsible for the operation of the new router system in the air interface environment. The wireless communication access point (AP) D302 in NAP is located in the new router D301 and is responsible for the Wi-Fi communication-related part of the system, and is used to establish a Wi-Fi connection with the STA. The virtual wireless communication access point (VAP) D303 in NAP is responsible for establishing a Wi-Fi connection with the STA.

[0024] Based on the above cross-device wireless communication system, an embodiment of the present application provides a cross-device wireless communication method. Figure 2 is a flow chart of a first cross-device wireless communication method provided in an embodiment of the present application, such as Figure 2 As shown, the cross-device wireless communication method is applied to a new wireless communication access point NAP in the cross-device wireless communication system, and includes the following steps.

[0025] Step 301: After NAP is started, it broadcasts a multiple basic service set identifier (MBTD) device search request frame.

[0026] The MBTD search request frame is a request frame newly created by the NAP and includes the MBSSID of the NAP and load capacity information.

[0027] After NAP starts, it broadcasts its own Beacon Frame, including the MBSSID of its VAP, to let other APs and STAs in the air interface environment know about it. At this time, NAP is a New AP that has just started and has not yet joined any MBTD set. NAP packages an MBTD search request frame (MBTD Search Request Frame) to scan whether there is an MBTD Set in the current air interface, and broadcasts the MBTD search request frame. Among them, the MBSSID of NAP includes not only the MBSSID of the AP, but also the MBSSID of its VAP.

[0028] Step 302: Receive an MBTD search response frame sent by a master wireless communication access point MAP in a target MBTD set.

[0029] Among them, the MBTD search response frame (MBTD Search Response Frame) is a response frame newly created by the main wireless communication access point MAP, which contains the maximum number of access point devices supported by the MAP, the number of occupied access point devices, and the beacon frame transmission interval BI. After receiving the MBTD Search Request Frame from the NAP, the MAP in the target MBTD set determines whether to allow the NAP to join the target MBTD set, and sends it to the NAP through the MBTD search response frame.

[0030] Optionally, the MBTD Search Request Frame also includes the number of VAPs of the NAP, as shown in Table 2. If the number of VAPs of the NAP is too large and exceeds the capacity of the MBSSID of the MAP in the target MBTD set, the MAP will reject the NAP's joining. The frame structure of the MBTD Search Response frame is shown in Table 3.

[0031] Table 2

[0032]

[0033] Table 3

[0034]

[0035] In this step, the MAP unicasts an MBTD search response frame to the requesting NAP.

[0036] Step 303: Determine whether to access the target MBTD set according to the signal strength of the MBTD search response frame, the maximum number of access point devices supported by the MAP, the number of occupied access point devices, and the BI.

[0037] After receiving the MBTD Search Response Frame from MAP, NAP parses the "SupportedMax VAP Num (maximum number of access point devices supported by MAP)", "Current VAP Num (number of occupied access point devices)" and "BI" carried in the frame. NAP calculates the RSSI information of MAP (signal strength of MBTD search response frame).

[0038] In one embodiment, the RSSI information is calculated by the Wi-Fi signal receiving end (such as NAP) itself instead of being provided by MAP, because the RSSI provided by MAP is definitely 100% signal strength, but the remaining signal strength at the Wi-Fi signal receiving end needs to be calculated by the receiving end (such as NAP). In another embodiment, the RSSI value has been calculated and included in the frame header of the Wi-Fi wireless frame (such as MBTDSearch Response Frame).

[0039] If the signal strength of the MBTD search response frame, the maximum number of access point devices supported by the MAP, the number of occupied access point devices, and the BI all meet the corresponding preset conditions set by the NAP, then the NAP is considered suitable for accessing the target MBTD set.

[0040] If at least one of the signal strength of the MBTD search response frame, the maximum number of access point devices supported by the MAP, the number of occupied access point devices, and the BI does not meet the corresponding preset conditions set by the NAP, the NAP is considered unsuitable for accessing the target MBTD set. For example, if the RSSI information of the target MBTD set is low, the NAP is considered unsuitable for joining the target MBTD set. At this time, the NAP assembles and sends an MBTD Beacon Ack Frame to inform the MAP not to join the target MBTD set. The frame structure of the MBTDBeacon Ack Frame is shown in Table 4 below.

[0041] Table 4

[0042]

[0043] Step 304: If the target MBTD set is determined to be accessed, an MBTD access request frame is sent to the MAP.

[0044] The MBTD access request frame is a request frame newly created by the NAP and includes the MBSSID of the NAP and the VAP corresponding to the NAP, the number of the VAP corresponding to the NAP, and load capacity information.

[0045] After the NAP determines the target MBTD set to be accessed, the NAP packages the MBSSID information of itself and its subordinate VAPs, and sends it to the MAP via an MBTD Join Request Frame, requesting to join the target MBTD set. The frame structure of the MBTD Join Request Frame is shown in Table 5 below.

[0046] Table 5

[0047]

[0048] MBSSID (Multiple BSSID) is a list including information (Element) of APs and VAPs under the NAP. In the embodiment of the present application, MBSSID also includes the load capacity (Capability) of each AP and / or VAP.

[0049] The AP Num is used to indicate how many APs there are in the MBSSID list of the NAP, including VAPs.

[0050] MBSSID is the traditional MBSSID part, where SAP MAC is used to indicate which SAP the VAP belongs to. Element indicates the RSN information of the AP / VAP, which is the content of the original MBSSID, including: BSSIDCapability: BSSID support capability, SSID: network name, Multiple BSSID Index: the position of the VAP in the MBSSID, RSN Information: the security information of the VAP, RSN eXtension: the extended security information of the VAP. The above elements are all the content of the original MBSSID protocol.

[0051] The load capacity of each AP / VAP in the MBSSID: Capability is used to display its physical information and load to the STA so that the STA can make a better choice.

[0052] The load capacity part of MBSSID is a newly added part in the embodiment of the present application, including: Max SupportedSTAs: maximum number of supported STA connections, Current Associated STAs: number of currently connected STAs, Max TxRate: maximum supported transmission rate, Current Tx Rate: current transmission rate, Max Rx Rate: maximum supported reception rate, Current Rx Rate: current reception rate, InterferencePercent: air interface congestion level, SNR: signal-to-noise ratio, RSSI: signal strength, Supported Standards: supported protocols, Supported Channels: supported Channels.

[0053] NAP sends the assembled MBTD Join Request Frame. In this step, it is unicasted to the MasterAP.

[0054] Step 305: Receive the MBTD access response frame sent by the MAP.

[0055] The MBTD access response frame is a response frame newly created by the MAP and contains access information.

[0056] After receiving the MBTD Join Request Frame packaged by NAP, MAP analyzes the MBSSID and other information carried by NAP, adds it to its own MBSSID, and updates its own MBTD Beacon Frame, including the MBSSID and the number of MBSSIDs, and replies with an MBTD Join Response Frame to NAP.

[0057] The NAP receives the MBTD access response frame sent by the MAP.

[0058] Step 306: If the access information in the MBTD access response frame indicates that the access has been completed, the NAP is in the target MBTD set and serves as a secondary wireless communication access point SAP of the MAP.

[0059] If the access information in the MBTD access response frame indicates that access has been completed, the frame structure of the MBTD access response frame is shown in Table 6 below.

[0060] Table 6

[0061]

[0062] The MBTD Join Response Frame includes an Action field, indicating whether to accept the request of the MBTD Join Request Frame of the NEW AP. At this time, the NAP is in the target MBTD set and serves as the slave wireless communication access point SAP of the MAP, that is, the process of NAP joining the MBTD Set of the MAP is completed, and the NAP becomes a Slave AP.

[0063] In the embodiment of the present application, a new protocol process is added to allow an AP to join the cross-device MBTD set formed by other APs after startup. The physical AP not only needs to package its own VAP group into the MBSSID, but also needs to form a device set MBTD with other physical APs in the air interface environment. In this set, MAP is responsible for forming an MBSSID of all physical APs and their VAPs in the set, and broadcasting it through Beacon Frame. Through this method, the number of Beacon Frames in the air interface environment can be greatly reduced, and the utilization rate of data transmission can be improved.

[0064] The embodiment of the present application further provides another cross-device wireless communication method. In the above step 306, after the NAP is in the target MBTD set and serves as a slave wireless communication access point SAP of the MAP, the following steps are also included.

[0065] Step 401: Receive an MBTD beacon frame sent by a MAP.

[0066] Among them, the MBTD beacon frame is a beacon frame newly created by MAP and contains a confirmation response interval. NAP joins the MBTD Set of the Master AP and becomes a Salve AP (SAP). The Master AP will send an MBTD Beacon Frame (MBTD Beacon Frame). MAP will broadcast the MBTD Beacon Frame to the outside in a loop. MAP broadcasts the MBTD Beacon Frame to the outside, and SAP will receive the MBTD Beacon Frame it broadcasts, and STAs in the air interface environment can also receive it.

[0067] Step 402: When the number of received MBTD beacon frames is equal to the confirmation response interval, MBTD beacon confirmation response frames are sent to the MAP.

[0068] The MBTD Beacon ACK Frame is a response frame newly created by SAP that includes the start time of the ACK cycle, the end time of the ACK cycle, and the ACK action.

[0069] After receiving the MBTD Beacon Frame from MAP, SAP parses the Ack Interval AI (Ack Interval). The Ack Interval carried in the MBTD Beacon Frame indicates how many MBTD Beacon Frames MAP needs SAP to receive before SAP replies with an MBTD Beacon Ack Response Frame to MAP to indicate that it has received the frame.

[0070] In this step, SAP determines whether the current AI counter starts from 0. If it starts from 0, the current time is recorded as "Ack cycle start time: Ack Time Start". If it does not start from 0, the current time is not recorded, and only the AI ​​counter needs to be added by 1. The specific time is already carried in the air interface signaling frame header of Wi-Fi.

[0071] SAP determines whether the value of the AI ​​counter is greater than the threshold for replying to the MBTD Beacon Frame, that is, whether it needs to reply to the MBTD Beacon Frame, indicating that it has received the MBTD Beacon Frame.

[0072] In the embodiment of the present application, the threshold for replying to the MBTD Beacon Frame can be 10, that is, MAP stipulates that after SAP receives 10 MBTD Beacon Frames, it needs to reply to an MBTD Beacon Ack Frame to indicate confirmation. It is not necessary to reply every time an MBTD Beacon Frame is received, so as to maximize the data transmission rate in the air interface. However, in order to let MAP know that SAP has received it, SAP needs to reply once in a while. Of course, the confirmation response interval can also be 11, 12, 13, etc., which is not specifically limited in the embodiment of the present application.

[0073] When SAP determines that the number of MBTD Beacon Frames it has received is greater than or equal to the threshold indicated by AI, it records the current time as "Ack cycle end time: Ack Time Stop". SAP assembles an MBTD beacon confirmation response frame MBTDBeacon Ack Frame to reply to MAP.

[0074] The MBTD Beacon Ack Frame includes the following fields: Ack Time Start: Ack cycle start time, Ack Time Stop: Ack cycle end time, Action: Indicates that the action of SAP in response to MAP is Ack. The frame structure of the MBTD beacon confirmation response frame is shown in Table 7. After SAP sends the MBTD Beacon Ack Frame, it is necessary to clear the AI ​​counter in this step and recalculate the AI ​​value.

[0075] Table 7

[0076]

[0077] Optionally, the MBTD Beacon Frame also includes the MBSSID part. After receiving the MBTD Beacon Frame from the MAP, the SAP parses the MBSSID part to determine whether the MBSSID includes itself and its VAP. The MBSSID Sub Element part includes the SAP MAC field, which can be used to determine whether it includes itself and the VAP. If it does not include itself, it is directly discarded without processing.

[0078] In the embodiment of the present application, not only is the Ack confirmation between SAP and MAP guaranteed, but SAP does not need to reply every time it receives an MBTD Beacon Frame, thereby improving the data transmission rate in the air interface.

[0079] The embodiment of the present application further provides another cross-device wireless communication method, wherein the MBTD beacon frame in the above step 402 further includes: the sorting positions of BI and SAP in the MBTD beacon frame, and the method further includes the following steps.

[0080] Step 501 : determining the frame loss rate of the MAP and the signal strength of each MBTD beacon frame according to the BI in the MBTD beacon frame received within a unit time and the number of MBTD beacon frames received within a unit time.

[0081] The MBTD Beacon Frame sent by MAP contains BI information, which indicates how many milliseconds to send the MBTD Beacon Frame. In this step, SAP checks the number of MBTD Beacon Frames received per unit time and calculates the frame loss rate of MAP.

[0082] In the embodiment of the present application, the frame loss rate of MAP calculated by SAP = ((unit time / BI)-the number of MBTD Beacon Frames received per unit time) / (unit time / BI). The unit time can be freely defined by SAP and is not specifically limited in the embodiment of the present application. For example, 8 MBTD Beacon Frames are received within a unit time of 1200ms, and the value of the BI carried in the MBTD Beacon Frame of MAP is 100ms, then the frame loss rate of MAP = (1200 / 10-8) / (1200 / 100) = 33%.

[0083] The SAP may obtain the RSSI value (signal strength of the MBTD beacon frame) from the MBTD Beacon Frame, and may also obtain the signal strength of each MBTD beacon frame by calculation, which is not specifically limited in the embodiment of the present application.

[0084] Step 502: If the frame loss rate of MAP is greater than the preset first frame loss rate threshold, or the signal strength of each MBTD beacon frame is less than the preset signal strength, or the BI in each MBTD beacon frame is greater than the preset BI threshold, or the sorting position of SAP in the MBTD beacon frame is greater than the preset position, an MBTD beacon request frame is sent to MAP.

[0085] The MBTD beacon request frame is a request frame newly created by SAP and contains the target MBTD set exit parameter.

[0086] Optionally, for SAP, if it detects that the number of received MBTD Beacon Frames is too small within a period of time, it considers that the MBTD Beacon Frame loss rate is too high, and the AP and its VAP are not suitable for continuing to be broadcasted by MAP, and sends MBTD beacon request frames to MAP.

[0087] If the MBTD Beacon Frame loss rate per unit time is greater than the "MBTD Beacon Frame loss rate threshold" (preset first frame loss rate threshold), SAP believes that the frame loss rate is too high and is not suitable for the MAP to continue broadcasting itself, then SAP applies to exit the target MBTD set through an MBTD Beacon Request Frame. At this time, the MBTD Beacon Request Frame includes the Action and Reason fields, and the Action is: Exit (target MBTD set exit parameter), indicating that the SAP and its VAP apply to exit the target MBTD set, and the frame structure is shown in Table 8 below.

[0088] Table 8

[0089]

[0090] SAP determines whether the RSSI value of the MBTD beacon frame is less than the RSSI threshold (preset signal strength) of SAP for several consecutive times. If it is less than the RSSI threshold of SAP occasionally instead of several consecutive times, it may be caused by a sudden situation in the air interface environment.

[0091] In the embodiment of the present application, if the signal strength of each MBTD beacon frame within a unit time is less than the preset signal strength, or if it is less than the RSSI threshold of SAP for multiple consecutive times (5 times, 6 times, etc.), it is considered that the MAP is too far away from the SAP or the air interface environment is poor, and it is not suitable for the MAP to broadcast the SAP. If the SAP considers that the MAP signal is too poor and is not suitable for the MAP to broadcast itself, the SAP applies to exit the target MBTD set through an MBTD beacon request frame (MBTD Beacon Request Frame).

[0092] Among them, the number of times that RSSI is continuously less than the RSSI threshold can be determined based on actual conditions. The RSSI threshold (preset signal strength) can be -70dBm. A value below -70dBm is considered to be RSSI below the threshold. It can also be other values ​​such as -71dBm, which are not specifically limited in the embodiments of the present application.

[0093] At this time, the MBTD Beacon Request Frame includes the Action field, MAC and Reason field. Action: Indicates the operation content of the MBTD Beacon Request Frame. Here, Action is Request to Exit (target MBTD set exit parameter), which means requesting MAP to delete SAP and its VAPs, and SAP exits MBTD Set. MAC: Indicates the MAC address corresponding to the SAP that performs the above operation. Reason: Indicates the reason for executing the above Action. Here, Reason is: RSSItoo Low. The frame structure is shown in Table 9 below.

[0094] Table 9

[0095]

[0096]

[0097] SAP counts BI values. Since BI generally does not change, if each BI within a unit time or N BIs are monitored continuously and are consistent and lower than SAP's BI threshold (preset BI threshold), the BI is considered too long. If each BI within a unit time is inconsistent or the values ​​of N consecutive BIs are inconsistent, wait until N are consistent before making a judgment. N can be 3, 4, etc.

[0098] When each BI within a unit time, or the BI values ​​of N continuously monitored MBTD Beacon Frames are consistent and lower than the preset BI threshold, the BI is considered to be too long; if there are inconsistencies in the N BI values, it may be that MAP is adjusting the BI value of the MBTD BeaconFrame. In an embodiment of the present application, the preset BI threshold may be 300ms, that is: if the N BIs of N continuously monitored MBTD BeaconFrames are all longer than 300ms, it is determined that the SAP threshold is exceeded, and SAP applies to exit the target MBTD set through an MBTD beacon request frame (MBTDBeacon Request Frame). Of course, the preset BI threshold can also be 310ms, etc., which is not specifically limited in the embodiment of the present application.

[0099] At this time, the MBTD Beacon Request Frame includes the Action, MAC and Reason fields. Action is: Exit (target MBTD set exit parameter), indicating that the SAP and its VAP apply to exit the target MBTD set. The frame structure is shown in Table 10 below.

[0100] Table 10

[0101]

[0102] SAP determines whether its BSSID Position (the order position of SAP in the MBTD beacon frame) in the MBSSID part of the current MBTD Beacon Frame is too far back. If the MBSSID information of SAP in the MBSSID part of the MBTD Beacon Frame is too far back every time within a unit time, or too far back for many times in a row, it will apply to exit the target MBTD set.

[0103] If the MBSSID information of the SAP is too far back in the MBSSID part of the MBTD Beacon Frame, the STA may not be able to resolve the SAP, or the STA may choose to connect after resolving the front MBSSID in the MBTD Beacon Frame and fail to find the SAP. Optionally, in an embodiment of the present application, if the MBSSID of the SAP ranks in the last 50% of the MBSSID part of the MBTD Beacon Frame, it is determined that it is not suitable to be handed over to the MAP to broadcast the SAP.

[0104] Parse and count the MBSSID part in the MBTD Beacon Frame. Because the MBSSID part generally does not change, if the MBSSID Position of the SAP always exceeds the threshold of SAP (corresponding to the preset position) in the monitored MBTD Beacon Frame within a unit of time, or the MBSSID Position of the SAP in the MBTD Beacon Frame exceeds the threshold of SAP (corresponding to the preset position) for multiple consecutive times, then it is considered that the MBSSID Position is too far back. If it is only occasionally far back, no other operations are required. In the embodiment of the present application, if it is too far back for 3 consecutive times (4, 5 times, etc.), it is determined that the MBSSID Position of SAP is too far back.

[0105] In the embodiment of the present application, the threshold of BSSID Position is 50%. That is, if the BSSID Position of SAP is ranked after 50% of MBSSID (such as 60%, 70%), it is determined to exceed the threshold.

[0106] When the ranking position of SAP in the MBTD beacon frame exceeds the preset position, it is considered that the MBSSID Position of SAP is too far back and is not suitable for the MAP to broadcast the SAP. Then SAP applies to exit the target MBTD set through the MBTD beacon request frame (MBTD Beacon Request Frame). At this time, the MBTD Beacon Request Frame includes the Action and Reason fields. Action is: Exit (target MBTD set exit parameter), indicating that SAP and its VAP apply to exit the target MBTD set. The frame structure is shown in Table 11 below.

[0107] Table 11

[0108]

[0109] Step 503: Receive a response frame sent by the MAP indicating successful exit from the target MBTD set.

[0110] Receiving the response frame sent by the MAP indicating successful exit from the target MBTD set indicates that the SAP becomes a new wireless communication access point NAP that is not connected to any MBTD set.

[0111] In the embodiment of the present application, the SAP actively withdraws from an inappropriate MBTD set, so that the SAP becomes a NAP again, and finds a suitable MBTD set for itself again to improve communication quality.

[0112] The embodiment of the present application also provides another cross-device wireless communication method, wherein the MBTD beacon request frame in the above step 502 further includes: an exit reason parameter. The exit reason parameter is Reason in the above tables 8 to 11. After the above step 502 sends the MBTD beacon request frame to the MAP, the following steps are further included.

[0113] Step 601: Receive an MBTD beacon response frame sent by a MAP.

[0114] The MBTD beacon response frame is a response frame newly created by SAP according to the exit reason parameter and contains optimized parameters.

[0115] After receiving SAP's application to exit the target MBTD set, MAP can first try to optimize according to SAP's exit reason parameters, or accept SAP's exit target MBTD set. When the structure of the MBTD beacon request frame is the structure of Table 9, the exit reason parameter is: RSSI is lower than the preset signal strength. The corresponding optimization parameter is: increase RSSI. When the structure of the MBTD beacon request frame is the structure of Table 10, the exit reason parameter is: BI exceeds the preset BI threshold. The corresponding optimization parameter is: reduce BI. When the structure of the MBTD beacon request frame is the structure of Table 11, the exit reason parameter is: SAP's MBSSID Position exceeds the preset position. The corresponding optimization parameter is: move SAP's MBSSID forward.

[0116] After receiving the request from SAP to exit the target MBTD set, if MAP confirms that it cannot be optimized, it will directly exit SAP from the target MBTD set. For example, when the structure of the MBTD beacon request frame is the structure of Table 8, the exit reason parameter is: the frame loss rate exceeds the preset first frame loss rate threshold. For this exit reason parameter, MAP believes that it cannot be optimized. When it cannot be optimized, MAP can directly delete the BSSID part of SAP, so that SAP exits the target MBTD set. At this time, SAP directly receives the response frame sent by MAP to successfully exit the target MBTD set.

[0117] Step 602: Send an MBTD beacon confirmation response frame to the MAP.

[0118] The MBTD beacon confirmation response frame includes acceptance optimization parameters or target MBTD set exit parameters.

[0119] After receiving the MBTD beacon response frame from MAP, SAP notifies MAP of its selection result through the MBTD beacon confirmation response frame (MBTD BeaconAck Frame). The selection result can be to accept the optimization or not to accept the optimization. If the optimization is accepted, the MBTD beacon confirmation response frame includes the accepted optimization parameter (Accepted Optimized). The frame structure is shown in Table 12 below.

[0120] Table 12

[0121]

[0122] If the optimization is not accepted, the MBTD beacon confirmation response frame includes the target MBTD set exit parameter (Request to Exit). The frame structure is shown in Table 13 below.

[0123] Table 13

[0124]

[0125] Step 603: Receive a response frame sent by the MAP indicating that the target MBTD set is optimized successfully or that the target MBTD set is exited successfully.

[0126] MAP returns the corresponding response frame according to SAP's decision (accept optimization or not accept optimization). When SAP's decision is to accept optimization, MAP optimizes according to the optimization parameters and sends a response frame to SAP indicating the successful optimization of the target MBTD set. When SAP's decision is not to accept optimization, MAP deletes SAP and sends a response frame to SAP indicating the successful exit from the target MBTD set.

[0127] In the embodiment of the present application, when SAP finds that MAP is not suitable, it can continue to access the target MBTD set by accepting the optimization of MAP to improve the communication quality. After not accepting the optimization, AP becomes NAP again to find a suitable MBTD set for itself to improve the communication quality.

[0128] An embodiment of the present application also provides another cross-device wireless communication method, which also includes the following steps.

[0129] When the NAP is not connected to the MBTD set, a new MBTD set is created, and the NAP serves as the master wireless communication access point MAP of the new MBTD set.

[0130] When the NAP is not connected to an MBTD set, it can select a target MBTD set to connect to, or it can create an MBTD set by itself. When the NAP creates a new MBTD set by itself, the NAP acts as the master wireless communication access point MAP of the new MBTD set, and other NAPs that connect to the new MBTD set will act as slave wireless communication access points SAP of the MAP of the new MBTD set.

[0131] In the embodiment of the present application, in addition to accessing the target MBTD set, the NAP can also create a new MBTD set by itself, thereby improving the flexibility of the MBTD set.

[0132] Based on the above embodiments, the embodiments of the present application further provide another cross-device wireless communication method, Figure 3 is a flow chart of a second cross-device wireless communication method provided in an embodiment of the present application, such as Figure 3 As shown, the cross-device wireless communication method is applied to the main wireless communication access point MAP in the cross-device wireless communication system, and specifically includes the following steps.

[0133] Step 701: receiving a multiple basic service set identifier device set MBTD search request frame broadcasted by a new wireless communication access point NAP.

[0134] The MBTD search request frame is a request frame newly created by the NAP that includes the MBSSID and load capacity information of the NAP. Optionally, the MBTD search request frame also includes the number of VAPs of the NAP. At this time, the frame structure of the MBTD access request frame is shown in Table 2 above.

[0135] Step 702: Determine whether to allow the NAP to access the target MBTD set where the MAP is located according to the MBSSID and load capacity information of the NAP.

[0136] If MAP supports the MBSSID and load capacity information of NAP, NAP is allowed to join the target MBTD set where MAP is located. Otherwise, NAP is not allowed to join the target MBTD set where MAP is located. Optionally, after MAP finds that the number of VAPs in the MBTD search request frame exceeds the capacity of MAP's MBSSID, NAP is rejected from joining the target MBTD set where MAP is located. Otherwise, NAP is allowed to join the target MBTD set where MAP is located.

[0137] Step 703: If the NAP is allowed to access the target MBTD set, an MBTD search response frame is sent to the NAP.

[0138] The MBTD search response frame (MBTD Search Response Frame) is a response frame newly created by the MAP and includes the maximum number of access point devices supported by the MAP, the number of occupied access point devices, and the beacon frame sending interval BI.

[0139] The frame structure of the MBTD search response frame is shown in Table 3 above, including: the maximum number of MBSSIDs supported by the MAP, the number of currently occupied MBSSIDs and the BI value.

[0140] Optionally, if the NAP is not allowed to join the target MBTD set, no response frame is sent to the NAP.

[0141] Step 704: Receive the MBTD access request frame sent by the NAP.

[0142] The MBTD Join Request Frame is a request frame newly created by the NAP and includes the MBSSID of the NAP and the virtual wireless communication access point VAP corresponding to the NAP, the number of VAPs corresponding to the NAP, and load capacity information.

[0143] When the NAP determines the access target MBTD set through the MBTD search response frame, the NAP sends an MBTD access request frame to the MAP. The frame structure of the MBTD access request frame is shown in Table 5 above.

[0144] Step 705: Add the NAP to the target MBTD set, and the NAP, as a slave wireless communication access point SAP of the MAP, sends an MBTD access response frame to the SAP.

[0145] Among them, the MBTD Join Response Frame is a response frame newly created by MAP that contains access information. The frame structure of the MBTD Join Response Frame is shown in Table 6 above. MAP receives the MBSSID and other information carried in the MBTD Join Request Frame sent by NAP, adds it to its own MBSSID, and updates its own MBTD Beacon Frame, including the MBSSID and the number of MBSSIDs therein. And replies the MBTD Join Response Frame to NAP.

[0146] In the embodiment of the present application, multiple physical APs are formed into a device set MBTD. In this set, NAP is added through MAP, and MAP is also responsible for forming MBSSID of all physical APs and their VAPs in the set and broadcasting it through Beacon Frame. Through this method, the number of Beacon Frames in the air interface environment can be greatly reduced, and the data transmission utilization rate can be improved.

[0147] The embodiment of the present application also provides another cross-device wireless communication method. In step 705, MAP adds NAP to the target MBTD set. After NAP serves as the slave wireless communication access point SAP of MAP and sends an MBTD access response frame to SAP, the following steps are also included.

[0148] Step 801: Update the MBTD beacon frame.

[0149] The MBTD beacon frame (MBTD Beacon Frame) is a beacon frame newly created by MAP and includes the confirmation response interval, the BI and the sequencing position of the SAP in the MBTD beacon frame.

[0150] NAP is added to the target MBTD set of MAP and becomes SAP.

[0151] MAP needs to broadcast an MBTD beacon frame, which is also a newly created frame in the embodiment of the application. The MBTD beacon frame contains the MBSSID and the number of MBSSIDs in the target MBTD set, which are all related to SAP. When the SAP changes, the MBTD beacon frame needs to be updated. In the embodiment of the present application, the frame structure of the MBTD beacon frame is shown in Table 14 below.

[0152] Among them, Supported AP Num: the maximum number of AP / VAPs supported by the MBSSID in the MBTD Beacon Frame. Current AP Num: the number of AP / VAPs currently existing in the MBTD Beacon Frame. BI: the interval for sending Beacons in the MBTD Beacon Frame. AI: after receiving AI Beacons, the Slave AP needs to reply an ACK Frame to the MAP to confirm that it has received the MBTD Beacon Frame. MAP MAC: indicates the MAC address of the Master AP.

[0153] Multiple BSSID: Indicates the MBSSID part carried by the Beacon Frame. MBSSID is a list, each list item is the information of an AP or VAP, and each list item includes SAP, Element information and Capability (load capacity). SAP MAC indicates which SAP the current MBSSID information belongs to, and the MAC address of the SAP must be specified here.

[0154] Element indicates the RSN information of the AP / VAP, which belongs to the original MBSSID content, including: BSSIDCapability: BSSID support capability. SSID: Network name. Multiple BSSID Index: The position of the VAP in the MBSSID. RSN Information: The security information of the VAP. RSN eXtension: The extended security information of the VAP. The above elements are all in the original MBSSID protocol.

[0155] Capability: Load capacity is a new part in the embodiment of the application, which is used to indicate the load capacity of the VAP. The load capacity is packaged together with the MBSSID and broadcast to the STA in the Beacon Frame, so that the STA can choose to connect according to the load capacity of the current VAP.

[0156] The content of Capability includes: Max Supported STAs: maximum number of supported STA connections, Current Associated STAs: number of currently connected STAs, Max Tx Rate: maximum supported transmission rate, Current Tx Rate: current transmission rate, Max Rx Rate: maximum supported reception rate, Current Rx Rate: current reception rate, Interference Percent: air interface congestion level, SNR: signal-to-noise ratio, RSSI: signal strength, Supported Standards: supported protocols, Supported Channels: supported channels.

[0157] Table 14

[0158]

[0159]

[0160] Step 802: cyclically broadcast MBTD beacon frames based on a preset interval.

[0161] MAP is broadcast once every BI (Beacon Interval) time. In the embodiment of the present application, the MBTD beacon frame is broadcast once every 100ms by default. Of course, the preset interval can also be 110ms, 120ms, etc., which is not specifically limited in the embodiment of the present application.

[0162] MAP broadcasts the latest MBTD Beacon Frame cyclically. It broadcasts once every BI time. MAP broadcasts MBTD Beacon Frame to the outside, and SAP will receive the MBTD Beacon Frame it broadcasts. STAs in the air interface environment can also receive it. After receiving the MBTD Beacon Frame, SAP analyzes it to determine whether it includes itself and its subordinate VAPs. If it does not include itself, it will directly discard it and continue to wait for the next MBTD Beacon Frame that includes itself.

[0163] In the embodiment of the present application, by timely updating the MBTD beacon frame, all SAPs of the MAP can receive the MBTD beacon frame, thereby ensuring the Ack confirmation between the SAP and the MAP.

[0164] The embodiment of the present application further provides another cross-device wireless communication method, which includes the following steps after step 802 , cyclically broadcasting the MBTD beacon frame based on a preset interval.

[0165] Step 901: Receive an MBTD beacon confirmation response frame sent by SAP.

[0166] The MBTD Beacon ACK Frame is a response frame newly created by SAP that includes the start time of the ACK cycle, the end time of the ACK cycle, and the ACK action.

[0167] The Ack Interval (AI) carried in the MBTD beacon frame indicates how many MBTD beacon frames the MAP needs SAP to receive before replying an MBTD beacon confirmation frame to the MAP to indicate that it has received the frame. Therefore, the MAP will receive the MBTD beacon confirmation frame sent by SAP. At this time, the frame structure of the MBTD beacon confirmation frame is shown in Table 7 above.

[0168] Step 902: Determine the frame loss rate of SAP according to the confirmation response period start time, the confirmation response period end time and the preset frame number.

[0169] MAP parses SAP's MBTD Beacon Ack Frame, including the Action field, Ack Time Start, and Ack Time Stop fields. The Action field is Ack (confirmation action). The Ack Time Start field indicates the start time when SAP starts to calculate the MBTD beacon frames sent by MAP after receiving a preset number of frames. The Ack Time Stop field indicates the end time when SAP starts to calculate the MBTD beacon frames sent by MAP after receiving a preset number of frames. Among them, AI is set by MAP.

[0170] For example, if MAP sets AI to 10, it means that SAP needs to reply to MAP with an MBTDBeacon Ack Frame after receiving 10 MBTD beacon frames. At this time, MAP knows how many MBTD beacon frames MAP has sent in this time slice according to SAP's "Ack Time Start" and "Ack Time Stop" fields and BI, but SAP has received AI (preset number of frames) MBTD beacon frames in this time slice.

[0171] MAP counts the MBTD beacon frame loss rate of SAP. The calculation formula is: Frame loss rate = (Number of MBTD beacon frames sent by MAP - AI) / Number of MBTD beacon frames sent by MAP. In the embodiment of the present application, because SAP is required to receive AI MBTD beacon frames before replying to the MBTD Beacon Ack Frame, the number received by SAP here must be AI. For example, within the time slice reported by SAP, MAP sent a total of 13 MBTD beacon frames, but SAP received 10, so the loss rate is (13-10 / 13) = 23%.

[0172] Step 903: If the frame loss rate of the SAP is greater than a preset second frame loss rate threshold, the SAP and the virtual wireless communication access point VAP corresponding to the SAP are deleted from the target MBTD set.

[0173] The MAP determines whether the frame loss rate exceeds a preset second frame loss rate threshold. In the embodiment of the present application, the preset second frame loss rate threshold can be set to 20%, or can be set to 25%, etc., which is not specifically limited in the embodiment of the present application.

[0174] When the frame loss rate is greater than the preset second frame loss rate threshold, MAP considers that the SAP is too far away or the air interface environment is poor, and SAP is no longer suitable to remain in the MBTD Set. MAP sends an MBTD Beacon Request Frame to inform SAP that SAP will be removed from the target MBTD set where MAP is located and will no longer broadcast its MBTD beacon frame. At this time, the frame structure of the MBTD Beacon Request Frame is shown in Table 15 below.

[0175] Table 15

[0176]

[0177] Among them, the MBTD Beacon Request Frame includes the Action field, MAC and Reason fields. Action: indicates the operation content of the MBTD Beacon Request Frame. Here, Action is Delete SAP, which means deleting SAP and its VAP. MAC: indicates the MAC address corresponding to the above operation. Reason: indicates the reason for executing the above Action. Here, Reason is: Beacon Loss Rate too Large. MAP deletes the MBSSID information of the SAP from its own MBSSID. After receiving the MBTD Beacon Request Frame from MAP, SAP replies with MBTD Beacon Ack Frame to indicate that it has been received. At this time, the frame structure of the MBTD Beacon Ack Frame is shown in Table 16 below.

[0178] Table 16

[0179]

[0180] The MBTD Beacon Ack Frame includes the following fields: Action: Received, indicating that it has been received. Since the Beacon loss rate is too high, it may be caused by a bad air interface environment, so the MBTD Beacon Ack Frame may not be transmitted to the MAP. Even if the MAP cannot receive the MBTD Beacon Ack Frame, it does not affect the MAP to continue the subsequent process.

[0181] In the embodiment of the present application, when the MAP finds that the SAP is not suitable, the SAP and the virtual wireless communication access point VAP corresponding to the SAP may be deleted from the target MBTD set to improve the communication quality.

[0182] The embodiment of the present application further provides another cross-device wireless communication method, which includes the following steps after step 802 , cyclically broadcasting the MBTD beacon frame based on a preset interval.

[0183] Step 1001: Receive an MBTD beacon request frame sent by SAP.

[0184] The MBTD Beacon Request Frame is a request frame newly created by SAP that includes a target MBTD set exit parameter and an exit reason parameter, as shown in Table 8 above.

[0185] Step 1002: Determine optimization parameters according to the target MBTD set exit parameters and exit reason parameters.

[0186] After receiving the MBTD beacon request frame sent by SAP, MAP parses it and obtains the target MBTD set exit parameter and exit reason parameter.

[0187] In the first case, the target MBTD set exit parameter is: Action: Exit, and the exit reason parameter is: RSSI is lower than the preset signal strength. MAP finds that SAP requests to exit the target MBTD set due to too low RSSI. MAP can optimize the target MBTD set based on the reason for SAP to exit the target MBTD set. At this time, MAP can choose to increase the transmission power to improve RSSI, or directly agree to SAP's exit request. Therefore, the corresponding optimization parameter is: increase RSSI.

[0188] In the second case, the target MBTD set exit parameter is: Action: Exit, and the exit reason parameter is: BI exceeds the preset BI threshold. MAP finds that SAP is due to the BI value being too large. At this time, MAP can choose to reduce BI or directly agree to SAP's request. Therefore, the corresponding optimization parameter is: reduce BI.

[0189] In the third case, the target MBTD set exit parameter is: Action: Exit, and the exit reason parameter is: SAP's MBSSID Position exceeds the preset position. MAP finds that it is SAP because SAP's MBSSID Position is too far back. At this time, MAP can choose to adjust the order of SAP's MBSSID, or choose to directly agree to SAP's request. Therefore, the corresponding optimization parameter is: move SAP's MBSSID forward.

[0190] In the fourth case, the target MBTD set exit parameter is: Action: Exit, and the exit reason parameter is: the frame loss rate exceeds the preset first frame loss rate threshold. For this exit reason parameter, MAP considers that it cannot be optimized.

[0191] Step 1003: Send an MBTD beacon response frame to SAP.

[0192] The MBTD beacon response frame is a response frame newly created by SAP according to the exit reason parameter and contains optimization parameters.

[0193] In the first case, MAP replies to SAP via an MBTD Beacon Response Frame. The frame structure of the MBTD Beacon Ack Frame is shown in Table 17. If MAP wants to increase the transmit power to improve RSSI based on the Reason of SAP, the frame can be filled as follows: Action: Optimized MAP, indicating that MAP is optimized and continues to send MBTD Beacon Frames including SAP MBSSID. Reason: Increase RSSI, indicating that the transmit power is increased to improve RSSI.

[0194] Table 17

[0195]

[0196] MAP can also accept the request of SAP and delete it directly. At this time, the frame structure of the MBTD Beacon Ack Frame is shown in Table 18. Action: Deleted SAP, indicating the deletion of SAP and its VAP. MAC: Indicates the MAC address corresponding to the above operation. Reason: Indicates the reason for executing the above Action, where Reason is: Request to Exit.

[0197] Table 18

[0198]

[0199] In the second case, MAP replies to SAP via an MBTD Beacon Response Frame. At this time, the frame structure of the MBTD Beacon Ack Frame is shown in Table 19. If MAP wants to reduce the BI value according to the Reason of SAP, the frame can be filled as follows: Action: Optimized MAP, indicating that MAP is optimized and continues to send MBTD Beacon Frames including SAP MBSSID. Reason: Decrease BI, indicating that the BI value is reduced.

[0200] Table 19

[0201]

[0202] MAP can also accept SAP's request to delete directly. In this case, the frame structure of the MBTD Beacon Ack Frame is shown in Table 20. The frame composition is as follows: Action: Deleted SAP, indicating the deletion of SAP and its VAP. MAC: Indicates the MAC address corresponding to the above operation. Reason: Indicates the reason for executing the above Action. In this case, Reason is Request to Exit.

[0203] Table 20

[0204]

[0205] In the third case, MAP replies to SAP via an MBTD Beacon Response Frame. At this time, the frame structure of the MBTD Beacon Ack Frame is shown in Table 21 below. If MAP moves the Position of SAP's BSSID forward according to SAP's Reason, the frame can be filled in as follows: Action: Optimized MAP, indicating that MAP is optimized and continues to send Beacon Frames including SAP MBSSID. Reason: Move forward SAP, moving SAP's MBSSID forward in the MBSID field.

[0206] Table 21

[0207]

[0208] AP can also accept SAP's request and delete it directly. In this case, the frame structure of the MBTD Beacon Ack Frame is shown in Table 22 below. The frame composition is: Action: Deleted SAP, which means deleting SAP and its VAP. MAC indicates the MAC address corresponding to the above operation. Reason indicates the reason for executing the above Action. In the third case, Reason is Request to Exit. In the fourth case, this step is not executed.

[0209] Table 22

[0210]

[0211] Step 1004: Receive the MBTD beacon confirmation response frame sent by SAP.

[0212] The MBTD beacon confirmation response frame includes a response frame for accepting optimization parameters or target MBTD set exit parameters.

[0213] In the first three cases, SAP notifies MAP of its selection result through an MBTD Beacon Ack Frame after receiving the MBTD Beacon Response Frame from MAP. If SAP accepts the optimization strategy of MAP, it replies Accepted Optimized. The frame structure of the MBTD Beacon Ack Frame is shown in Table 23 below. If not accepted, it replies Request to Exit. The frame structure of the MBTD Beacon Ack Frame is shown in Table 24 below.

[0214] Table 23

[0215]

[0216] Table 24

[0217]

[0218] In the fourth case, MAP deletes the MBSSID information of the SAP from its own MBSSID. After MAP deletes the MBSSID information of the SAP, it notifies SAP through the MBTD Beacon Ack Frame. At this time, the frame structure of the MBTD Beacon Ack Frame is shown in Table 25 below. MBTD Beacon Ack Frame includes the Action field, MAC, and Reason fields. Action: Deleted SAP, indicating deletion of SAP and its VAPs. MAC: indicates the MAC address corresponding to the above operation. Reason: indicates the reason for executing the above Action, where Reason is: Request to Exit.

[0219] Table 25

[0220]

[0221] Since the Beacon loss rate is too high, it may be caused by a bad air interface environment, so the MBTD Beacon AckFrame here may not be transmitted to the MAP. Even if the MAP cannot receive the MBTD Beacon Ack Frame, it will not affect the MAP to continue the subsequent process.

[0222] Step 1005: If the MBTD beacon confirmation response frame includes accepting the optimization parameters, the target MBTD set is optimized according to the optimization parameters, and a response frame indicating the success of optimizing the target MBTD set is sent to the SAP.

[0223] In the first case, if the MBTD beacon confirmation response frame includes the accepted optimization parameter (AcceptedOptimized), MAP chooses to increase the transmission power to improve RSSI according to the decision of SAP. In the second case, if the MBTD beacon confirmation response frame includes the accepted optimization parameter (AcceptedOptimized), MAP chooses to reduce BI according to the decision of SAP. In the third case, if the MBTD beacon confirmation response frame includes the accepted optimization parameter (AcceptedOptimized), MAP chooses to move forward the MBSSID Position of SAP according to the decision of SAP.

[0224] Step 1006: If the MBTD beacon confirmation response frame includes the target MBTD set exit parameter, SAP is exited from the target MBTD set according to the target MBTD set exit parameter, and a response frame indicating successful exit from the target MBTD set is sent to SAP.

[0225] In the first three cases, if the MBTD beacon confirmation response frame includes the target MBTD set exit parameter (Request to Exit), the MAP deletes the SAP and reassembles the MBSSID information.

[0226] In the embodiment of the present application, when SAP finds that MAP is not suitable, MAP can determine optimization parameters, and SAP can continue to access the target MBTD set by accepting the optimization of MAP to improve communication quality. After not accepting the optimization, AP becomes NAP again to find a suitable MBTD set for itself to improve communication quality.

[0227] An embodiment of the present application also provides another cross-device wireless communication method, which also includes the following steps.

[0228] Step 1101: Receive a beacon frame from a NAP in an air interface.

[0229] When NAP is not connected to MBTD, it broadcasts NAP's beacon frame. MAP finds that NAP has not sent MBTD SearchRequest Frame but receives NAP's Beacon Frame. MAP of the target MBTD set determines that NAP's Beacon Frame is in the air interface and believes that NAP has not actively applied to join the MBTD set.

[0230] Step 1102, determine the signal strength of the beacon frame of the NAP.

[0231] Step 1103: If the signal strength of the beacon frame of the NAP meets the preset signal strength condition, an MBTD access invitation frame is sent to the NAP.

[0232] The MBTD access invitation frame is a request frame newly created by the MAP and includes the maximum number of access point devices supported by the MAP, the number of occupied access point devices, and the beacon frame transmission interval BI.

[0233] If the signal strength of the beacon frame of the NAP meets the preset signal strength condition, the MAP actively sends an MBTD Join Invite Frame to the NAP to invite it to join its target MBTD set. The frame structure of the MBTD Join Invite Frame is shown in Table 26. The MBTD Join Invite Frame includes the maximum number of APs / VAPs supported by the MBTD Set, the number of currently occupied APs / VAPs, and the BI of the MBTD.

[0234] Table 26

[0235]

[0236] Step 1104: Receive the MBTD access request frame sent by the NAP.

[0237] Among them, the MBTD access request frame is a request frame newly created by the NAP that contains the MBSSID of the NAP and the virtual wireless communication access point VAP corresponding to the NAP, the number of VAPs corresponding to the NAP, and load capacity information. The NAP parses the MBTDJoin Invite Frame sent by the MAP, including the maximum number of VAPs it supports, the number of currently occupied VAPs, and the BI, calculates the RSSI of the MAP, and determines whether to accept the request of the MAP to join its target MBTD set. If accepted, the NAP packages the MBSSID information of itself and its subordinate VAPs and sends an MBTD access request frame (MBTD Join Request Frame) message to the MAP. When the NAP refuses to join the target MBTD set, the NAP sends an MBTD Ack Frame to inform the MAP that it does not join its target MBTD set. At this time, the frame structure of the MBTD AckFrame is shown in Table 27 below.

[0238] Table 27

[0239]

[0240] Step 1105: Add the NAP to the target MBTD set, and the NAP, as a slave wireless communication access point SAP of the MAP, sends an MBTD access response frame to the SAP.

[0241] Among them, the MBTD Join Response Frame is a response frame newly created by MAP that contains access information. After receiving the MBTD Join Request Frame, MAP analyzes the MBSSID and other information carried by NAP, adds it to its own MBSSID, and updates its own MBTD Beacon Frame, including the MBSSID and the number of MBSSIDs, and replies to the NAP with an MBTD Join Response Frame. After completing this step, the process of MAP inviting NAP to join the target MBTD set of MAP is completed, and NAP becomes SAP at this time.

[0242] In the embodiment of the present application, the MAP actively invites the NAP to join the target MBTD set of the MAP, which reflects the initiative of the target MBTD set.

[0243] The embodiments of the present application also provide a specific cross-device wireless communication method and a cross-device wireless communication apparatus. Figure 4 is a flow chart of a third cross-device wireless communication method provided in an embodiment of the present application, Figure 5is a schematic diagram of the structure of a cross-device wireless communication device provided in an embodiment of the present application, such as Figure 4 As shown, the specific steps include the following steps.

[0244] Step S100, after NAP is started, it actively queries MBTD Set. NAP sends its MBSSID and load capacity information to MAP to request to join its MBTD Set. MAP can also actively send an invitation to NAP to join its MBTD Set. NAP can join MBTD Set or refuse to join.

[0245] Step S200, after SAP parses the received MBTD Beacon Frame, it sets the AI ​​counter and sends the MBTD Beacon Ack Frame to the MAP when the AI ​​threshold is reached; the MAP calculates the Beacon Frame loss rate of the SAP, and deletes the SAP and its VAP when the loss rate exceeds the threshold; the SAP calculates the loss rate of the Beacon Frame sent by the MAP by the BI value in the Beacon Frame, and requests the MAP to exit the MBTD Set when the loss rate exceeds the threshold.

[0246] Step S300, after SAP parses the received MBTD Beacon Frame, it determines that the RSSI of MAP exceeds the threshold of SAP, and requests MAP to exit MBTD Set; at the same time, it monitors the BI of MAP's Beacon Frame, and requests to exit MBTD Set after it exceeds the BI threshold of its own SAP; at the same time, it monitors the position of SAP's MBSSID in the MBSSID of MBTD Beacon Frame, and requests to exit if the position is too far back. After receiving the exit request from SAP, MAP can choose to optimize MBSSID, or directly delete the BSSID part of SAP.

[0247] Step S400: NAP creates MBTD Set and broadcasts MBTD Beacon Frame. When NAP's Beacon Frame is found in the air interface, it parses the Beacon Frame and determines its RSSI. MAP actively invites NAP to join MBTD Set. NAP can choose to join MBTD Set or refuse to join after analyzing MAP's RSSI.

[0248] like Figure 5 As shown, the dynamic addition module M100 runs on the Master D101 of MBTD and the Salve D201 of MBTD. Specifically, on the Master D101 of MBTD, D102 AP is responsible; on the Salve D201 of MBTD, D202AP is responsible.

[0249] After NAP starts, it actively queries MBTD Set. After MAP receives NAP's query and responds, NAP sends its MBSSID and load capacity information to MAP to request to join its MBTD Set; NAP can also refuse to join. When MAP finds that NAP has not requested to join its MBTD Set, it can also actively send an invitation to NAP to join. After analysis, NAP can join MBTD Set or directly refuse to join.

[0250] Figure 6 is a flow chart of a fourth cross-device wireless communication method provided in an embodiment of the present application, such as Figure 6 As shown, the specific steps include the following steps.

[0251] Step S101: After starting up, the AP broadcasts its own Beacon Frame, including the MBSSID of its VAP, to let other APs and STAs in the air interface environment know about itself.

[0252] Step S102: The MBTD Master AP determines whether it has received an MBTD Search Frame (MBTD Search Request Frame) from a newly started AP.

[0253] Step S103: The NAP forms an MBTD Search Request Frame to scan whether there is an MBTDSet in the current air interface, and broadcasts it.

[0254] Step S104, after receiving the number of VAPs carried in the MBTD Search Request Frame of the NAP, the Master AP determines whether to allow the NAP to join the MBTD Set, and sends a newly added frame MBTD Search Response Frame to the NAP.

[0255] Step S105: After receiving the MBTD Search Response Frame of the MAP, the NAP parses the "Supported Max VAP Num", "Current VAP Num" and "BI" carried in the frame.

[0256] Step S106, the NAP calculates the RSSI information of the MAP. The NAP determines whether to join the MBTD Set based on the RSSI, BI, "Supported Max VAPNum" and "Current VAP Num". If the RSSI of the MBTD Set is too low, it means that the NAP is not suitable to join this MBTD Set. If it joins, execute step S107; otherwise, execute step S111.

[0257] Step S107, the NAP packages the MBSSID information of itself and its subordinate VAPs, and in the next step sends a newly added frame MBTDJoin Request Frame to the MAP to request to join the MBTD Set.

[0258] Step S108: NAP assembles and sends an MBTD Join Request Frame.

[0259] Step S109, after receiving the MBSSID and other information carried by the NAP, the MAP analyzes it and adds it to its own MBSSID. At the same time, it updates its own MBTD Beacon Frame, including the MBSSID and the number of MBSSIDs. It also replies with an MBTD JoinResponse Frame to the NAP. After completing this step, the process of NAP joining the MBTD Set of the MAP is completed, and the NAP becomes a Slave AP.

[0260] Step S110: This step is performed when it is determined in step S106 that the NAP does not want to join the MBTD Set of the MAP after receiving the Search Response Frame of the MAP. In this step, the NAP assembles and sends an MBTD Ack Frame to inform the MAP that it does not want to join its MBTD Set.

[0261] In step S102, MAP finds that NAP has not sent MBTD Search Request Frame but has received Beacon Frame. MBTD MAP determines that there is Beacon Frame of NAP in the air interface and believes that NAP has not actively applied to join MBTD Set, and can invite it to join MBTD Set through MBTD Join Invite Frame. Then, step S111 is executed.

[0262] Step S111: MAP actively sends an MBTD Join Invite Frame to NAP to invite it to join its MBTD Set.

[0263] Step S112: The NAP parses the MBTD Join Invite Frame sent by the MAP, including the maximum number of VAPs supported by the NAP, the number of currently occupied VAPs, and the BI.

[0264] Step S113, after parsing the MBTD Join Invite Frame of the MAP in the previous step, the RSSI of the MAP is calculated here, and it is determined whether to accept the request of the MAP to join its MBTD Set. If yes, execute step S114; otherwise, execute step S117.

[0265] Step S114, after determining in the previous step that the NAP agrees to join the MBTD Set, in this step, the MBSSID information of the NAP and its subordinate VAPs is packaged.

[0266] Step S115: The AP assembles and sends a Join Request Frame message to the MAP. The frame structure of the Join Request Frame has been described in detail in step S108.

[0267] Step S116, after receiving the MBSSID and other information carried by the NAP, the MAP analyzes it and adds it to its own MBSSID. At the same time, it updates its own MBTD Beacon Frame, including the MBSSID and the number of MBSSIDs, and replies the MBTD JoinResponse Frame to the NAP. After completing this step, the process of the MAP inviting the NAP to join the MBTD Set of the MAP is completed, and the NAP becomes a Slave AP.

[0268] Step S117: when it is determined in step S113 that the NAP refuses to join the MBTD Set, this step is performed, and the NAP sends an MBTDAck Frame to inform the MAP that it does not join its MBTD Set.

[0269] The above steps S101 to S117 complete the process that after MAP discovers that NAP is started through Beacon Frame, it accepts NAP's MBTD Search Frame and replies to MBTD Response Frame. After NAP analyzes, it sends its own and its subordinate VAP's MBSSID and load capacity information to MAP to request to join its MBTD MBTD Set; NAP can also refuse to join. When MAP finds that NAP has not requested to join its MBTD Set, it can also actively send MBTD Join Invite Frame to invite NAP to join. After analysis, NAP can join MBTD Set through MBTD Join Request Frame or directly reply MBTD AckFrame to refuse to join.

[0270] The real-time monitoring module M200 runs on the Master D101 and the Salve D201 of MBTD. Specifically, on the Master D101 of MBTD, the D102 AP is responsible; on the Salve D201 of MBTD, the D202 AP is responsible.

[0271] After SAP parses the received MBTD Beacon Frame, it sets the AI ​​counter and sends an MBTD Beacon Ack Frame to MAP when the AI ​​threshold is reached. MAP calculates the Beacon Frame loss rate of SAP and deletes the SAP and its VAP when the loss rate exceeds the threshold. SAP calculates the loss rate of Beacon Frame sent by MAP based on the BI value in the Beacon Frame. When the loss rate exceeds the threshold, it requests MAP to exit MBTD Set.

[0272] Figure 7 is a flowchart of a fifth cross-device wireless communication method provided in an embodiment of the present application, such as Figure 7 As shown, the specific steps include the following steps.

[0273] Step S201: MAP cyclically broadcasts MBTD Beacon Frame to the outside, once per Beacon Interval.

[0274] Step S202: MAP broadcasts MBTD Beacon Frame externally, SAP will receive the broadcasted MBTD Beacon Frame, and STAs in the air interface environment can also receive it.

[0275] Step S203, after SAP receives the Beacon Frame from MAP, it parses the AI ​​(Ack Interval: Ack interval) and MBSSID part to determine whether the MBSSID includes itself and its VAP. The MBSSID Sub Element part includes the SAPMAC field, which can be used to determine whether it includes itself and the VAP. If it does not include itself, it is directly discarded without processing. The Ack Interval carried in the Beacon Frame indicates how many Beacon Frames MAP needs SAP to receive before replying an MBTD Beacon ACK Frame to MAP to indicate that it has received it. In this step, SAP counts according to the AI ​​counter.

[0276] In step S204, SAP determines whether the value of the AI ​​counter is greater than the threshold for replying the MBTD Beacon Ack Frame, that is, whether it needs to reply the MBTD Beacon Ack Frame, indicating that it has received the Beacon Frame.

[0277] Step S205: When SAP determines that the number of Beacon Frames it has received is greater than the threshold indicated by AI, it records the current time as the end time of the Ack cycle: "Ack Time Stop".

[0278] Step S206: assemble an MBTD Beacon Ack Frame to reply to the MAP.

[0279] Step S207: After sending the MBTD Beacon Ack Frame in the previous step, it is necessary to clear the AI ​​counter in this step and re-count the AI ​​value.

[0280] Step S208: MAP parses the MBTD Beacon Ack Frame of SAP, including the Action field and the Ack Time Start / Ack Time Stop field.

[0281] Step S209: MAP determines whether the number of Beacon Frames lost by SAP exceeds a loss threshold.

[0282] Step S210: When it is determined in the previous step that the Beacon Frame loss rate is greater than the threshold, the MAP considers that the SAP is too far away or the air interface environment is poor, and the SAP is no longer suitable to remain in the MBTD Set.

[0283] Step S211: MAP deletes the MBSSID information of the SAP from its own MBSSID.

[0284] Step S212: After receiving the MBTD Beacon Request Frame from the MAP, the SAP replies with an MBTD Beacon AckFrame to indicate receipt.

[0285] Step S213: The MBTD Beacon Frame sent by the MAP contains BI information, indicating how often in milliseconds the MBTD Beacon Frame is sent.

[0286] Step S214: If the loss rate of MBTD Beacon Frames per unit time is greater than the "MBTD Beacon Frame loss rate threshold", then step S214 is executed; otherwise, the determination is continued.

[0287] Step S215: SAP considers that the Beacon Frame loss rate is too high and it is not suitable for the MAP to continue broadcasting itself, so it applies to exit the MBTD Set through the MBTD Beacon Request Frame.

[0288] Step S216: After receiving the information, the MAP deletes the MBSSID information of the SAP from its own MBSSID.

[0289] Step S217: After deleting the MBSSID information of the SAP, the MAP notifies the SAP via an MBTD Beacon Ack Frame.

[0290] The above steps S201 to S217 complete the process in which SAP parses the received MBTD Beacon Frame, sets the AI ​​counter, and sends the MBTD Beacon Ack Frame to MAP when the AI ​​threshold is reached; MAP calculates the Beacon Frame loss rate of SAP, and deletes the SAP and its VAP when the loss rate exceeds the threshold; SAP calculates the loss rate of the Beacon Frame sent by MAP through the BI value in the Beacon Frame, and requests MAP to exit the MBTD Set process when the loss rate exceeds the threshold.

[0291] The active disengagement module M300 runs on the Master D101 and the Salve D201 of MBTD. Specifically, on the Master D101 of MBTD, the D102 AP is responsible; on the Salve D201 of MBTD, the D202 AP is responsible.

[0292] After SAP analyzes the received MBTD Beacon Frame, it determines that the RSSI of MAP exceeds the threshold of SAP, and requests MAP to exit MBTD Set; at the same time, it monitors the BI of MAP's MBTD Beacon Frame. If it exceeds the BI threshold of its own SAP, it also requests to exit MBTD Set; at the same time, it monitors the position of SAP's MBSSID in the MBTD Beacon Frame's MBSSID. If the position is too far back, it also requests to exit. After receiving the exit request from SAP, MAP can choose to optimize the MBSSID or directly delete the BSSID part of SAP.

[0293] Figure 8 is a flow chart of a sixth cross-device wireless communication method provided in an embodiment of the present application, such as Figure 8 As shown, the specific steps include the following steps.

[0294] Step S301, MAP cyclically broadcasts MBTD Beacon Frame to the outside, once every BI (Beacon Interval) time. In this application embodiment, the default broadcasting time is once every 100ms.

[0295] Step S302: MAP broadcasts MBTD Beacon Frame externally, SAP will receive the broadcasted MBTD Beacon Frame, and STAs in the air interface environment can also receive it.

[0296] Step S303: SAP receives the MBTD Beacon Frame and analyzes it to determine whether it includes itself and its subordinate VAPs. If it does not include itself, SAP directly discards it and continues to wait for the next MBTD Beacon Frame that includes itself.

[0297] Step S304, SAP determines whether the RSSI value of the current MBTD Beacon Frame is less than the RSSI threshold of SAP for several consecutive times. If it is not less than the RSSI threshold of SAP for several consecutive times, it may be caused by a sudden situation in the air interface environment.

[0298] Step S305, SAP obtains the RSSI value from the MBTD Beacon Frame. In this embodiment of the application, if the RSSI value is less than the RSSI threshold of SAP for five consecutive times, it is considered that the MBTD MAP is too far away from itself or the air interface environment is poor, and it is not suitable for the MAP to broadcast itself.

[0299] Step S306, SAP considers that the MAP signal is too poor and is not suitable for MAP to broadcast itself, and applies to exit the MBTDSet of MAP. After receiving the exit request from SAP, MAP first tries to optimize the MBSSID according to the exit reason of SAP. If optimization is not possible, the BSSID part of SAP can be directly deleted.

[0300] Step S307: After receiving the MBTD Beacon Request Frame from SAP, MAP analyzes the Action and Reason and finds that SAP requests to exit the MBTD Set due to low RSSI. MAP can optimize the MBTD Set according to the Reason for SAP to exit the MBTD Set. At this time, MAP can choose to increase the transmission power to improve RSSI, or directly agree to SAP's request.

[0301] Step S308: After receiving the Response Frame from the MAP, the SAP notifies the MAP of its selection result through the MBTD Beacon Ack Frame.

[0302] Step S309: MAP increases the transmission power to improve RSSI according to the decision of SAP, or deletes SAP and reorganizes MBSSID information.

[0303] Step S310: SAP determines whether the BI value of the current MBTD Beacon Frame exceeds the BI threshold of SAP.

[0304] Step S311, count the BI values. Since BI generally does not change, if N consecutive BIs are consistent and lower than the BI threshold of SAP, the BI is considered to be too long. If the values ​​of N consecutive BIs are inconsistent, continue to wait until all N BIs are consistent before making a judgment.

[0305] Step S312: When it is determined in the previous step that the BI of the MBTD Beacon Frame is greater than the BI threshold of the SAP, the SAP requests to exit the MBTD Set. The SAP assembles and sends the MBTD Beacon Request Frame.

[0306] Step S313, after receiving the MBTD Beacon Request Frame from SAP, MAP parses the Action and Reason therein and finds that the BI value of SAP is too large. At this time, MAP can choose to reduce the BI or directly agree to SAP's request.

[0307] Step S314: After receiving the Response Frame from the MAP, the SAP notifies the MAP of its selection result through the MBTD Beacon Ack Frame.

[0308] Step S315, MAP chooses to reduce BI according to the decision of SAP, or deletes SAP and reorganizes MBSSID information.

[0309] Step S316, SAP determines whether the BSSID Position (position) of the MBSSID part of the current MBTD Beacon Frame is too far back.

[0310] Step S317, parse and count the MBSSID part in the MBTD Beacon Frame. Because the MBSSID part generally does not change, if the MBSSID Position in the Beacon Frame is lower than the SAP threshold after monitoring several times, it is considered that the MBSSID Position is too far behind. If it is only occasionally far behind, no other operations are required.

[0311] Step S318: When it is determined in the previous step that the Position of the MBSSID of the MBTD Beacon Frame is greater than the sorting threshold of the SAP, the SAP requests to exit the MBTD Set. The SAP assembles the packet and sends the MBTD Beacon Request Frame.

[0312] Step S319, after receiving the MBTD Beacon Request Frame from SAP, MAP analyzes the Action and Reason therein and finds that SAP is not responding because SAP's MBSSID Position is too far back. At this time, MAP can choose to adjust the order of SAP's MBSSID or directly agree to SAP's request.

[0313] Step S320: After receiving the Response Frame from the MAP, the SAP notifies the MAP of its selection result through an Ack Frame.

[0314] Step S321, the AP moves forward the MBSSID Position of the SAP according to the decision of the SAP, or deletes the SAP and reorganizes the MBSSID information.

[0315] The above steps S301 to S321 complete the process in which SAP parses the received MBTD Beacon Frame and determines that the RSSI of MAP exceeds the threshold of SAP, and requests MAP to exit MBTD Set; at the same time, monitor the BI of MAP's MBTD Beacon Frame, and request to exit MBTD Set after it exceeds the BI threshold of its own SAP; at the same time, monitor the position of SAP's MBSSID in the MBSSID of MBTD BeaconFrame, and request to exit if the position is too far back. After receiving the exit request from SAP, MAP can choose to optimize MBSSID or directly delete the BSSID part of SAP.

[0316] The self-created module M400 runs on the Master D101 and the Salve D201 of MBTD. Specifically, the D102 AP is responsible for the Master D101 of MBTD, and the D202 AP is responsible for the Salve D201 of MBTD.

[0317] After the NAP creates the MBTD Set, it broadcasts the MBTD Beacon Frame. When the NAP's Beacon Frame is found in the air interface, it parses the Beacon Frame and determines its RSSI. The MAP actively invites the NAP to join the MBTD Set. After analyzing the MAP's RSSI, the NAP can choose to join the MBTD Set or refuse to join.

[0318] Fig. 9 is a flow chart of a seventh cross-device wireless communication method provided in an embodiment of the present application, such as Fig. 9 As shown, the specific steps include the following steps.

[0319] Step S401, NAP (New AP: newly started AP that has not joined the MBTD Set) finds that there is no MBTD Set in the air interface environment or actively detaches from the MBTD Set it has joined, and prepares to independently create an MBTD Set. There is one MAP in an MBTD Set, and the others are SAPs. MAP is responsible for assembling the MBTD Beacon Frame. The frame structure of the MBTD Beacon Frame has been described in detail in the real-time monitoring module M200. As shown in Table 14 above. In this step, the AP is responsible for creating the MBTDSet, that is, forming the MBTD Beacon Frame, and setting the MAP MAC in the Beacon Frame to its own MAC address. After successfully creating the MBTD Set, the AP becomes a MAP (Master AP).

[0320] Step S402: MAP broadcasts MBTD Beacon Frame externally, and both SAP and STA in the air interface can receive it.

[0321] Step S403: The NAP in the air interface that has not joined the MBTD Set assembles a BeaconFrame of a Single Beacon.

[0322] In step S404, the NAP broadcasts the Beacon Frame of the Single Beacon to the outside, and the MAP and STA can receive it.

[0323] Step S405: After receiving the Beacon Frame from the NAP, the MAP analyzes and determines whether the RSSI value satisfies the minimum RSSI threshold of the MAP.

[0324] Step S406, MAP determines whether the RSSI value of the NAP meets the minimum RSSI threshold requirement of the MBTD Set. The minimum RSSI threshold is set in the MBTD Set. If the RSSI of the received NAP is lower than the threshold, it is considered not suitable to be added to the MBTD Set.

[0325] Step S407, if it is determined in the previous step that the RSSI of the NAP is greater than the MAP RSSI threshold, it is considered that the NAP can be added to its own MBTD Set, and an MBTD Join Invite Frame is assembled to invite the NAP to join. When the MAP invites the NAP to join its MBTD Set, it first determines whether the RSSI of the NAP meets the RSSI threshold of the MBTD Set. The MBTD JoinInvite Frame sent by the MAP is also a new frame in the embodiment of the present application. It includes the maximum number of APs / VAPs supported by the MBTD Set, the number of currently occupied APs / VAPs, and the BI of the MBTD. As shown in the above Table 26.

[0326] Step S408: The NAP parses the MBTD Join Invite Frame sent by the MAP, including the maximum number of VAPs it supports, the number of VAPs currently in use, and the BI.

[0327] Step S409, after parsing the MBTD Join Invite Frame of the MAP in the previous step, the RSSI of the MAP is calculated here, and it is determined whether to accept the request of the MAP to join its MBTD Set. If yes, execute step S410; otherwise, execute step S413.

[0328] Step S410: The AP composes an MBTD Join Request Frame message and sends it to the MAP.

[0329] Step S411: NAP assembles and sends an MBTD Join Request Frame.

[0330] Step S412: After receiving the message, MAP analyzes the MBSSID and other information carried by NAP, adds it to its own MBSSID, and updates its own MBTD Beacon Frame, including the MBSSID and the number of MBSSIDs. After completing this step, the process of MAP inviting NAP to join MAP's MBTD Set is completed. At this point, NAP becomes a Slave AP.

[0331] Step S413: When it is determined in step S409 that the NAP refuses to join the MBTD Set, this step is performed, and the NAP sends an MBTD Beacon Ack Frame to inform the MAP that it does not join its MBTD Set.

[0332] The above steps S401 to S413 complete the process of NAP broadcasting MBTD Beacon Frame after creating MBTD Set. When NAP's Beacon Frame is found in the air interface, it parses its Beacon Frame and determines its RSSI. MAP actively invites NAP to join MBTD Set. NAP can choose to join MBTD Set or refuse to join after analyzing MAP's RSSI.

[0333] Figure 5 The dynamic joining module in the system runs on MAP, SAP and NAP, and is responsible for actively querying MBTD Set after NAP is started. NAP sends its MBSSID and load capacity information to MAP to request to join its MBTD Set. MAP can also actively invite NAP to join its MBTD Set. NAP can join MBTD Set or directly refuse to join.

[0334] Figure 5 The real-time monitoring module in the system runs on MAP and SAP. After SAP parses the received MBTD Beacon Frame, it sets the AI ​​counter and sends the MBTD Beacon Ack Frame to MAP when the AI ​​threshold is reached. MAP calculates the Beacon Frame loss rate of SAP and deletes the SAP and its VAP when the loss rate exceeds the threshold. SAP calculates the loss rate of Beacon Frame sent by MAP based on the BI value in the Beacon Frame and requests MAP to exit MBTD Set when the loss rate exceeds the threshold.

[0335] Figure 5The active disengagement module in the MAP runs on the MAP and SAP. After the SAP parses the received MBTD Beacon Frame, it determines that the RSSI of the MAP exceeds the threshold of the SAP, and requests the MAP to exit the MBTD Set. At the same time, it monitors the BI of the MAP Beacon Frame. If it exceeds the BI threshold of its own SAP, it also requests to exit the MBTD Set. At the same time, it monitors the position of the SAP's MBSSID in the MBTDBeacon Frame. If the position is too far back, it also requests to exit. After receiving the exit request from the SAP, the MAP can choose to optimize the MBSSID or directly delete the BSSID part of the SAP.

[0336] Figure 5 The autonomous creation module in the MAP runs on the MAP and NAP. After the NAP creates the MBTD Set, it broadcasts the MBTD Beacon Frame. When the Beacon Frame of the NAP is found in the air interface, the Beacon Frame is parsed and its RSSI is determined. The MAP actively invites the NAP to join the MBTD Set. After analyzing the RSSI of the MAP, the NAP can choose to join the MBTD Set or refuse to join.

[0337] This application takes the AP beacon frame as an example. For the Probe Response Frame, a similar method of cross-device MBSSID packaging can be used, which will not be expanded here, but the same solution is used, so it is also included in the protection scope of this application.

[0338] This application adds a new protocol process to allow an AP to join the cross-device MBTD set formed by other APs after startup. The Master AP in the MBTD set can actively add the newly started AP in the air interface environment, and can also accept requests from other APs to invite them to join their own MBTD set. The Slave AP in the MBTD set can monitor the MBTD set in real time and choose to exit the set according to the situation; at the same time, the Master AP in the set can also detect the Slave AP in real time and delete the Slave AP according to the situation; the Slave AP in the set can choose to exit the set based on the Master AP's RSSI (received signal strength indication), BI and its own position in the MBSSID, or form a cross-device MBSSID set and invite new APs to join. This application allows multiple APs and VAPs in the same air interface environment to form a Beacon Frame of a cross-device MBSSID, which can greatly reduce the Beacon Frame in the air interface environment and greatly improve the utilization rate of data transmission. Simply put, in the basic technology, a physical AP, such as a router, is responsible for packaging its VAPs into MBSSID and broadcasting them through Beacon Frames, which can reduce the number of Beacon Frames in the air interface environment. In this application, the physical AP not only needs to package its VAPs into MBSSID, but also needs to form a set with other physical APs in the air interface environment. In this set, the Master AP is responsible for forming an MBSSID of all physical APs and their VAPs in the set and broadcasting them through Beacon Frames. Through this method and system, the number of Beacon Frames in the air interface environment can be greatly reduced.

[0339] The steps of the above methods are divided only for the purpose of clear description. When implemented, they can be combined into one step or some steps can be split and decomposed into multiple steps. As long as they include the same logical relationship, they are all within the protection scope of this patent. In practical applications, various changes can be made to the above embodiments in form and details without departing from the spirit and scope of this application.

Claims

1. A cross-device wireless communication method, characterized in that: Applied to a new wireless communication access point NAP, the method comprises: After the NAP is started, a multi-basic service set identifier device MBTD search request frame is broadcast; wherein the MBTD search request frame is a request frame newly created by the NAP and includes the NAP's MBSSID and load capacity information; Receive an MBTD search response frame sent by a master wireless communication access point MAP in a target MBTD set; wherein the MBTD search response frame is a response frame newly created by the master wireless communication access point MAP and includes the maximum number of access point devices supported by the MAP, the number of occupied access point devices, and the beacon frame sending interval BI; Determine whether to access the target MBTD set according to the signal strength of the MBTD search response frame, the maximum number of access point devices supported by the MAP, the number of occupied access point devices, and the BI; If it is determined to access the target MBTD set, an MBTD access request frame is sent to the MAP; wherein the MBTD access request frame is a request frame newly created by the NAP and includes the MBSSID of the NAP and the VAP corresponding to the NAP, the number of the VAP corresponding to the NAP, and load capacity information; receiving an MBTD access response frame sent by the MAP; wherein the MBTD access response frame is a response frame newly created by the MAP and containing access information; If the access information in the MBTD access response frame indicates that the access has been completed, the NAP is in the target MBTD set and serves as a slave wireless communication access point SAP of the MAP.

2. The cross-device wireless communication method according to claim 1, characterized in that: The NAP is located in the target MBTD set and is behind the slave wireless communication access point SAP of the MAP, further comprising: receiving an MBTD beacon frame sent by the MAP; wherein the MBTD beacon frame is a beacon frame newly created by the MAP and includes a confirmation response interval; When the number of received MBTD beacon frames is the confirmation response interval, MBTD beacon confirmation response frames are sent to the MAP; wherein the MBTD beacon confirmation response frame is a response frame newly created by the SAP and includes a confirmation response cycle start time, a confirmation response cycle end time and a confirmation action.

3. The cross-device wireless communication method according to claim 2, characterized in that: The MBTD beacon frame further includes: the sorting positions of the BI and the SAP in the MBTD beacon frame; and the method further includes: Determine the frame loss rate of the MAP and the signal strength of each MBTD beacon frame according to the BI in the MBTD beacon frame received within a unit time and the number of MBTD beacon frames received within a unit time; If the frame loss rate of the MAP is greater than a preset first frame loss rate threshold, or the signal strength of each MBTD beacon frame is less than a preset signal strength, or the BI in each MBTD beacon frame is greater than a preset BI threshold, or the sorting position of the SAP in the MBTD beacon frame is greater than a preset position, an MBTD beacon request frame is sent to the MAP; wherein the MBTD beacon request frame is a request frame newly created by the SAP and includes a target MBTD set exit parameter; A response frame sent by the MAP indicating successful exit from the target MBTD set is received.

4. The cross-device wireless communication method according to claim 3, characterized in that: The MBTD beacon request frame further includes: an exit reason parameter; after sending the request frame for exiting the target MBTD set to the MAP, the frame further includes: receiving an MBTD beacon response frame sent by the MAP; wherein the MBTD beacon response frame is a response frame newly created by the SAP according to the exit reason parameter and containing optimization parameters; Sending an MBTD beacon confirmation response frame to the MAP; wherein the MBTD beacon confirmation response frame includes acceptance optimization parameters or the target MBTD set exit parameters; A response frame sent by the MAP indicating a successful optimization of the target MBTD set or a successful exit from the target MBTD set is received.

5. The cross-device wireless communication method according to claim 1, characterized in that: The method further comprises: When the NAP is not connected to the MBTD set, a new MBTD set is created, and the NAP serves as the master wireless communication access point MAP of the new MBTD set.

6. A cross-device wireless communication method, characterized in that: Applied to a primary wireless communication access point MAP, the method comprises: Receive a multi-basic service set identifier device set MBTD search request frame broadcasted by a new wireless communication access point NAP; wherein the MBTD search request frame is a request frame newly created by the NAP and includes the MBSSID and load capacity information of the NAP; the new wireless communication access point NAP is used to perform the cross-device wireless communication method described in any one of claims 1 to 5 above; Determine whether to allow the NAP to access the target MBTD set where the MAP is located according to the MBSSID and load capacity information of the NAP; If the NAP is allowed to access the target MBTD set, an MBTD search response frame is sent to the NAP; wherein the MBTD search response frame is a response frame newly created by the MAP and includes the maximum number of access point devices supported by the MAP, the number of occupied access point devices, and the beacon frame sending interval BI; receiving an MBTD access request frame sent by the NAP; wherein the MBTD access request frame is a request frame newly created by the NAP and includes the MBSSID of the NAP and the virtual wireless communication access point VAP corresponding to the NAP, the number of VAPs corresponding to the NAP, and load capacity information; The NAP is added to the target MBTD set, and the NAP serves as a slave wireless communication access point SAP of the MAP, and sends an MBTD access response frame to the SAP; wherein the MBTD access response frame is a response frame newly created by the MAP and contains access information.

7. The cross-device wireless communication method according to claim 6, characterized in that: The MAP adds the NAP to the target MBTD set, and the NAP, as a slave wireless communication access point SAP of the MAP, sends an MBTD access response frame to the SAP, further comprising: Updating an MBTD beacon frame; wherein the MBTD beacon frame is a beacon frame newly created by the MAP and includes a confirmation response interval, the BI, and the sorting position of the SAP in the MBTD beacon frame; The MBTD beacon frame is cyclically broadcast based on a preset interval.

8. The cross-device wireless communication method according to claim 7, characterized in that: After the MBTD beacon frame is cyclically broadcasted based on a preset interval, the method further includes: Receiving an MBTD beacon confirmation response frame sent by the SAP; wherein the MBTD beacon confirmation response frame is a response frame newly created by the SAP and includes a confirmation response cycle start time, a confirmation response cycle end time, and a confirmation action; Determine the frame loss rate of the SAP according to the confirmation response period start time, the confirmation response period end time and the preset number of frames; If the frame loss rate of the SAP is greater than a preset second frame loss rate threshold, the SAP and the virtual wireless communication access point VAP corresponding to the SAP are deleted from the target MBTD set.

9. The cross-device wireless communication method according to claim 7, characterized in that: After the MBTD beacon frame is cyclically broadcasted based on a preset interval, the method further includes: receiving an MBTD beacon request frame sent by the SAP; wherein the MBTD beacon request frame is a request frame newly created by the SAP and includes a target MBTD set exit parameter and an exit reason parameter; Determining optimization parameters according to the target MBTD set exit parameters and exit reason parameters; Sending an MBTD beacon response frame to the SAP; wherein the MBTD beacon response frame is a response frame newly created by the SAP according to the exit reason parameter and containing optimization parameters; Receiving an MBTD beacon confirmation response frame sent by the SAP; wherein the MBTD beacon confirmation response frame includes an acceptance optimization parameter or an exit parameter of the target MBTD set; If the MBTD beacon confirmation response frame includes acceptance of optimization parameters, optimizing the target MBTD set according to the optimization parameters, and sending a response frame indicating successful optimization of the target MBTD set to the SAP; If the MBTD beacon confirmation response frame includes a target MBTD set exit parameter, the SAP is exited from the target MBTD set according to the target MBTD set exit parameter, and a response frame indicating successful exit from the target MBTD set is sent to the SAP.

10. The cross-device wireless communication method according to claim 6, characterized in that: The method further comprises: receiving a beacon frame of the NAP in an air interface; wherein, when the NAP is not connected to the MBTD, broadcasting the beacon frame of the NAP; Determining a signal strength of a beacon frame of the NAP; If the signal strength of the beacon frame of the NAP meets the preset signal strength condition, an MBTD access invitation frame is sent to the NAP; wherein the MBTD access invitation frame is a request frame newly created by the MAP and includes the maximum number of access point devices supported by the MAP, the number of occupied access point devices, and the beacon frame sending interval BI; Receiving an MBTD access request frame sent by the NAP; The NAP is added to the target MBTD set, and the NAP serves as a slave wireless communication access point SAP of the MAP, and sends an MBTD access response frame to the SAP.

Images