CN112911686A

CN112911686A - Method for acquiring and sending neighbor information, wireless local area network and storage medium

Info

Publication number: CN112911686A
Application number: CN202110125907.0A
Authority: CN
Inventors: 吴昊; 王鑫
Original assignee: Chengdu Jimi Technology Co Ltd
Current assignee: Chengdu Jimi Technology Co Ltd
Priority date: 2021-01-29
Filing date: 2021-01-29
Publication date: 2021-06-04
Anticipated expiration: 2041-01-29
Also published as: CN112911686B

Abstract

The application discloses a method for acquiring and sending neighbor cell information, a wireless local area network and a storage medium, and relates to the field of wireless communication. The method for acquiring the neighbor cell information comprises the following steps: a high-level management unit of the terminal sends MLME-NEIGHBORREPREQ.request primitive to a low-level management unit; the low-layer management unit sends a Neighbor Report Request frame to the access point, receives a Neighbor Report Response frame sent by the access point, and sends an MLME-NEIGHBORREPRESP. The method and the device have the advantages that the neighbor cell information is obtained and sent based on multilinks, the terminal can provide more flexible neighbor cell information through the setting of the request message, and the access point provides more accurate information for decision making through the setting of the response message, so that the terminal can have more accurate information when the access point needs to be replaced, and the network interruption time caused by the replacement of the access point is reduced.

Description

Method for acquiring and sending neighbor information, wireless local area network and storage medium

Technical Field

The present application relates to the field of wireless communications, and in particular, to a method for acquiring and sending neighbor information, a wireless local area network, and a storage medium.

Background

In the 802.11 system, an access device (AP STA) and a terminal (Non-AP STA) are both internally deployed with a MAC layer and a PHY layer, wherein the main functions of the MAC layer include channel management, connection management, quality of service management, power control, time synchronization, and the like, and the main functions of the PHY layer include modulation, coding, transmission, and the like.

Both the MAC layer and the PHY layer conceptually include management units referred to as a MAC layer management unit mlme (MAC sublayer management entity) and a physical layer management unit plme (PHY sublayer management entity), respectively. These elements provide low-level management service interfaces through which low-level management functions can be invoked.

In order to provide correct MAC operation, each STA (including Non-AP STA and AP STA) has a higher layer management unit, such as SME (device management element), which represents a higher layer management unit above the MAC layer, and is a layer-independent unit, which is located in a separate management plane.

The function of SME: typically, this unit is responsible for functions such as collecting layer-related state from various layer management units (MLME and PLME), which similarly also set layer-specific parameter values. SMEs typically perform such functions on behalf of a general system management entity. FIG. 1 depicts the relationship between management units.

802.11be networks, also known as Extreme High Throughput (EHT) networks, are enhanced by a range of system features and a variety of mechanisms to achieve very High Throughput. As the use of Wireless Local Area Networks (WLANs) continues to grow, it becomes increasingly important to provide wireless data services in many environments, such as homes, businesses, and hot spots. In particular, video traffic will continue to be the dominant type of traffic in many WLAN deployments. With the advent of 4k and 8k video (uncompressed rates of 20 Gbps), the throughput requirements for these applications are constantly evolving. New high throughput, low latency applications such as virtual reality or augmented reality, gaming, remote offices, and cloud computing will proliferate (e.g., latency for real-time gaming is less than 5 milliseconds).

In view of the high throughput and stringent real-time latency requirements of these applications, users expect higher throughput, higher reliability, less latency and jitter, and higher power efficiency when supporting their applications over a WLAN. Users desire improved integration with Time Sensitive Networks (TSNs) to support applications on heterogeneous ethernet and wireless LANs. 802.11be networks aim to ensure the competitiveness of WLANs by further increasing overall throughput and reducing latency, while ensuring backward compatibility and coexistence with legacy technology standards. 802.11 compatible devices operating in the 2.4GHz, 5GHz and 6GHz bands.

Disclosure of Invention

In a conventional wireless local area network, a terminal can request access point for neighbor cell information, where a neighbor cell refers to an access point adjacent to an access point to which the terminal is currently connected, so that the terminal can be helped to connect to a new access point more quickly when the terminal moves or a current network link is lost, and network interruption time is reduced. The multilink access equipment can have a plurality of logic access points which operate independently, the access point information obtained by using the traditional adjacent cell request can have a plurality of access points belonging to the same multilink access equipment, when the access equipment has faults or is changed in setting, the managed logic access points are not suitable for terminal access, and when the access equipment only has a certain link with heavy load and needs to carry out load balancing, other logic access points which are replaced to the access equipment can lead the terminal to obtain shorter interrupt time. Therefore, it is more complicated in a multilink scenario. In view of the above, the present application provides a method for acquiring and sending neighbor information, a wireless local area network and a storage medium.

In a first aspect, an embodiment of the present application provides a method for acquiring neighboring cell information, where the method is applied to a terminal, and the terminal includes a lower management unit and a higher management unit, and the method includes:

a high-level management unit of the terminal sends MLME-NEIGHBORREPREQ.request primitive to a low-level management unit;

after receiving the MLME-NEIGHBORREPREQ.request primitive, a lower management unit of the terminal sends a Neighbor Report Request frame to an access point;

a lower management unit of a terminal receives a Neighbor Report Response frame sent by an access point, wherein the Neighbor Report Response frame comprises a parameter Neighbor list set, the Neighbor list set comprises an Information element BSSID Information and optional Information elements, the BSSID Information comprises a parameter explicit High threshold, the explicit High threshold is used for indicating whether a Neighbor cell is an EHT access point, when the explicit High threshold indicates that the Neighbor cell is the EHT access point, the optional High threshold comprises parameters EHT Capability and/or EHT operation, and the parameters EHT Capability and EHT operation are set to the same value as a parameter broadcasted in a broadcast message of the Neighbor cell, and the parameters EHT Capability and EHT operation are used for indicating the Capability of an EHT system, and the access point is used for indicating the Capability of the EHT system;

and the lower management unit of the terminal sends an MLME-NEIGHBORREPRESP.indication primitive to the higher management unit, wherein the MLME-NEIGHBORREPRESP.indication primitive comprises the parameter NeighborListSet.

In a second aspect, an embodiment of the present application provides a method for sending neighbor information, where the method is applied to an access device, where the access device includes a lower management unit and a higher management unit, and the method includes:

a low-layer management unit of the access equipment receives a Neighbor Report Request frame sent by a terminal and sends an MLME-NEIGHBORREPREQ.indication primitive to a high-layer management unit;

after receiving the MLME-neighbor report request.indication primitive, a High level management unit of an access device constructs a MLME-neighbor report request.request primitive according to a parameter in the MLME-neighbor report request.indication primitive and sends the MLME-neighbor report request.request primitive to a low level management unit if a locally configured parameter dot11 rmneighborreportactived value is true, the MLME-neighbor report request.request primitive includes a parameter neighbor list, the neighbor list includes an Information element BSSID Information for indicating Information of a neighbor and optional Information elements, the BSSID Information includes a parameter exception High threshold, the exception High level threshold is used for indicating whether the exception High threshold is used for indicating that the neighbor is an eh value, and the exception High level threshold is used for indicating that the exception High is equal to the access point threshold, and the exception High level broadcast parameter is equal to the access point of the neighbor access point, and the exception High level broadcast parameter is equal to the exception High level broadcast parameter, and the exception High level broadcast is equal to the access point, if the exception High level broadcast parameter of the access point is equal to the neighbor broadcast, the access point, the exception High level broadcast, the access point broadcast Capability of the access point broadcast of the neighbor and the neighbor broadcast of the neighbor access point, the access point, if the access point, the neighbor broadcast of the access point, the neighbor list of the neighbor access, the EHT operation is used for indicating an EHT system operating parameter of an EHT access point;

after receiving the MLME-NEIGHBORREPRESP request primitive, the lower management unit of the access device sends a Neighbor Report Response frame to the terminal, wherein the Neighbor Report Response frame comprises the parameter Neighbor ListSet.

In a third aspect, an embodiment of the present application provides a terminal, where the terminal includes a lower management unit and a higher management unit, where the higher management unit is configured to send an MLME-neighbor report request primitive to the lower management unit;

a low-layer management unit, configured to send a Neighbor Report Request frame to an access point after receiving the MLME-Neighbor Report req.request primitive; receiving a Neighbor Report Response frame sent by an access point, wherein the Neighbor Report Response frame contains a parameter Neighbor List, the Neighbor List contains an Information element BSSID Information and optional Information elements, the BSSID Information contains a parameter egress High Throughput, the egress High Throughput is used for indicating whether a Neighbor cell is an EHT access point, when the egress High Throughput indicates that the Neighbor cell is the EHT access point, the egress High Throughput contains a parameter EHT Capability and/or EHT operation, and the parameters EHT Capability and EHT operation are set to be the same value as the same parameter broadcasted in the broadcast message of the Neighbor cell, the EHT Capability is used for indicating the EHT operation Capability, and the access point is used for indicating the EHT operation Capability of the system; and sending an MLME-NEIGHBORREPRESP.indication primitive to a high-level management unit, wherein the MLME-NEIGHBORREPRESP.indication primitive comprises the parameter NeighborListSet.

In a fourth aspect, an embodiment of the present application provides an access device, where the access device includes a lower management unit and a higher management unit, where the lower management unit is configured to receive a Neighbor Report Request frame sent by a terminal, and send an MLME-Neighbor Report req.indication primitive to the higher management unit; after receiving MLME-NEIGHBORREPRESP.request primitive sent by a high-level management unit, sending a Neighbor Report Response frame to a terminal, wherein the Neighbor Report Response frame comprises a parameter NeighborListset;

a High-level management unit, configured to, after receiving the MLME-neighbor report _ indication primitive, if a locally configured parameter dot11RMNeighborReportActivated value is true, construct a MLME-neighbor report _ request primitive according to a parameter in the MLME-neighbor report _ indication primitive, and send the MLME-neighbor report _ request primitive to a low-level management unit, where the MLME-neighbor report _ request primitive includes a parameter neighbor list, the neighbor list includes an Information element BSSID Information for indicating Information of a neighbor and optional Information elements, the BSSID Information includes a parameter exception High threshold, the exception High threshold is used for indicating whether the exception High threshold is used for indicating that the neighbor is an ehprobability, and the exception High threshold is used for indicating that the exception High threshold is set to the same as the access point ehprobability, and the exception access point broadcasts the exception access point is a Capability of the neighbor access point, if the locally configured parameter dot11 rmneighborborreportactived value is true, and the MLME-neighbor report _ request primitive includes the parameter, and the exception High-level _ request _ primitive includes the parameter, and the exception High _ request _ message includes the parameter, and the parameter is set to the same as the neighbor access point, if the neighbor access point is a Capability of the neighbor, the neighbor access point, the access point, and the exception High _ request, the EHT operation is used to indicate EHT system operating parameters of an EHT access point.

In a fifth aspect, an embodiment of the present application provides a wireless local area network, where the wireless local area network includes a terminal and an access device, where the terminal is the terminal in the third aspect, and the access device is the access device in the fourth aspect.

In a sixth aspect, an embodiment of the present application provides a storage medium, where at least one program code is stored in the storage medium, and the at least one program code is loaded and executed by a processor to implement the method for acquiring neighboring cell information according to the first aspect or the method for sending neighboring cell information according to the second aspect.

It should be noted that, the terminal in the third aspect is configured to execute the method in the first aspect, the access device in the fourth aspect is configured to execute the method in the second aspect, and the storage medium in the sixth aspect is configured to execute the method in the first aspect or the second aspect, so that the same beneficial effects as the method in the first aspect or the second aspect may be achieved, and the embodiments of the present application are not described again.

The method and the device have the advantages that the neighbor cell information is obtained and sent based on multilinks, the terminal can provide more flexible neighbor cell information through the setting of the request message, and the access point provides more accurate information for decision making through the setting of the response message, so that the terminal can have more accurate information when the access point needs to be replaced, and the network interruption time caused by the replacement of the access point is reduced.

Drawings

The present application will now be described by way of example only and with reference to the accompanying drawings in which:

FIG. 1 is a diagram illustrating a management unit structure of a device in the prior art;

fig. 2 is a schematic diagram of a method for acquiring neighboring cell information according to an embodiment of the present application.

Detailed Description

In order to make those skilled in the art better understand the technical solutions in the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the present application and are not intended to limit the present application. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application. Moreover, while the disclosure herein has been presented in terms of exemplary one or more examples, it is to be understood that each aspect of the disclosure can be utilized independently and separately from other aspects of the disclosure to provide a complete disclosure. The embodiments described below and the features of the embodiments can be combined with each other without conflict.

In the embodiments of the present application, the words "exemplary," "for example," and the like are used to mean serving as an example, instance, or illustration. Any embodiment or design described herein as "exemplary" is not necessarily to be construed as preferred or advantageous over other embodiments or designs. Rather, the term using examples is intended to present concepts in a concrete fashion.

Unless defined otherwise, technical or scientific terms used herein shall have the ordinary meaning as understood by one of ordinary skill in the art to which this application belongs. The use of "first," "second," and similar terms in this application do not denote any order, quantity, or importance, but rather the terms are used merely to distinguish one element from another, and the meanings of the corresponding terms may be the same or different. The word "comprising" or "comprises", and the like, means that the element or item listed before the word covers the element or item listed after the word and its equivalents, but does not exclude other elements or items.

In this embodiment, both the terminal and the access device include a lower layer management unit and a higher layer management unit, where the lower layer management unit is a unit that manages and controls data transmission of the device, such as an MLME and a PLME, and the higher layer management unit is a unit that manages a service or an application of the device, such as an equipment management unit SME and an application management unit ame (application management entity).

Fig. 2 is a schematic diagram of a method for acquiring neighboring cell information according to an embodiment of the present application. As shown in fig. 2, the method comprises the steps of:

1. the SME of the terminal sends an MLME-neighbor report req. request primitive to the MLME of the terminal, and parameters included in the primitive are shown in table 1, for example.

TABLE 1

2. After receiving the MLME-Neighbor Report Request primitive, the MLME of the terminal sends a Neighbor Report Request frame to the access point, where, for example, parameters included in the Neighbor Report Request frame are shown in table 2.

TABLE 2

3. After receiving the Neighbor Report Request frame, the MLME of the access point sends an MLME-Neighbor Report req.

TABLE 3

4. After receiving the MLME-neighbor report request indication primitive, if the locally configured parameter dot11RMNeighborReportActivated value is true (indicating that the access point supports a reporting neighbor), the SME of the access point constructs the MLME-neighbor report request primitive according to the parameter in the MLME-neighbor report request indication primitive, which is specifically exemplified as follows:

if the SSID is contained, the neighbor cell belonging to the SSID is contained in the primitive according to the value of the SSID;

and if the LCI Measurement Request is included, acquiring the position information of the adjacent cell, wherein the position information is included in the primitive.

5. The SME of the access point sends an MLME-neighbor report request primitive to the MLME of the access point, illustratively, the parameters contained in this primitive are as shown in table 4.

TABLE 4

Among them, NeighborListSet can be set as shown in table 5.

TABLE 5

Among them, BSSID Information may be set as shown in table 6.

TABLE 6

The parameters that optional attributes may contain are shown in table 7.

TABLE 7

Parameter(s)	Description of the invention
		EHT Capability	Indicating EHT system capability parameters of EHT access points
EHT operation	Indicating EHT system operating parameters of an EHT access point
		ML Elements	Indicating multilink parameters

Among them, EHT Capability parameters may be set as shown in table 8.

TABLE 8

MAC Capability

PHY Capability

MAC Capability: MAC layer capabilities of the EHT system;

PHY Capability: physical layer capabilities of the EHT system;

the MAC Capability may contain one or more of the parameters shown in table 9:

TABLE 9

PHY Capability may include one or more of the parameters shown in table 10:

watch 10

The EHT operation parameters may include one or more of the parameters shown in table 11:

TABLE 11

The ML Elements parameters may include one or more of the parameters shown in Table 12:

TABLE 12

6. The MLME of the access point sends a Neighbor Report Response frame to the terminal, and illustratively, the parameters contained in the Neighbor Report Response frame are shown in table 13.

Watch 13

7. After receiving the Neighbor Report Response frame, the MLME of the terminal sends an MLME-Neighbor Report indication primitive to the SME of the terminal, where parameters included in the primitive are shown in table 14.

TABLE 14

8. After receiving the MLME-NEIGHBORREPRESP.indication primitive, the SME of the terminal stores the NeighborListset parameter.

If the terminal is an EHT terminal, when an access point needs to be replaced, firstly trying to connect from the access point indicated as the EHT access point, and if the access point contains a parameter STRs, preferentially selecting the access point supporting STR to connect; attempting to connect to a non-EHT access point after all EHT access points fail to connect;

if the terminal is a multilink terminal and the access point needs to be replaced, if the replacement reason is mobility, other access points which are indicated as being affiliated to the same multilink equipment as the current access point are not taken as candidate access points;

if the terminal is a multilink terminal and when an access point needs to be replaced, if the replacement reason is load balancing, other access points which are indicated to be subordinate to the same multilink device as the currently connected access point are preferentially selected.

In some embodiments, the optional details only include the parameters EHT Capability and EHT operation, and the parameter ML Elements is included in the parameter EHT Capability or EHT operation, for example, in the following possible ways:

1) included in the EHT Capability parameters, as shown in table 15.

Watch 15

MAC Capability

PHY Capability

ML Elements

2) Included in the MAC Capability, a sub-parameter of the EHT Capability parameter, in this embodiment, the Multi link support parameter may be included in ML Elements, as shown in table 16.

TABLE 16

3) Included in the EHT operation parameters, as shown in table 17, in this embodiment, the parameters Align start time of PPDU and Align end time of PPDU may be included in ML Elements.

TABLE 17

In some embodiments, the AP MLD parameters may also be set as shown in Table 18.

Watch 18

The embodiment of the application also provides a terminal, which comprises a low-layer management unit and a high-layer management unit, wherein the high-layer management unit is used for sending MLME-NEIGHBORREPREQ.request primitive to the low-layer management unit; a low-layer management unit, configured to send a Neighbor Report Request frame to an access point after receiving the MLME-Neighbor Report req.request primitive; receiving a Neighbor Report Response frame sent by an access point, wherein the Neighbor Report Response frame contains a parameter Neighbor List, the Neighbor List contains an Information element BSSID Information and optional Information elements, the BSSID Information contains a parameter egress High Throughput, the egress High Throughput is used for indicating whether a Neighbor cell is an access point, when the egress High Throughput indicates that the Neighbor cell is an EHT access point, the egress High Throughput contains a parameter EHT Capability and/or EHT operation, and the parameter EHT Capability and/or EHT operation are the same as the parameter broadcast in the broadcast message of the Neighbor cell and are set to the same value, and the EHT Capability is used for indicating the Capability of the system EHT, and the access point is used for indicating the Capability of the system EHT; and sending an MLME-NEIGHBORREPRESP.indication primitive to a high-level management unit, wherein the MLME-NEIGHBORREPRESP.indication primitive comprises the parameter NeighborListSet.

The embodiment of the application also provides an access device, which comprises a low-layer management unit and a high-layer management unit, wherein the low-layer management unit is used for receiving a Neighbor Report Request frame sent by a terminal and sending an MLME-NEIGHBORREPREQ.indication primitive to the high-layer management unit; after receiving MLME-NEIGHBORREPRESP.request primitive sent by a high-level management unit, sending a Neighbor Report Response frame to a terminal, wherein the Neighbor Report Response frame comprises a parameter NeighborListset; a High-level management unit, configured to, after receiving the MLME-neighbor report _ indication primitive, if a locally configured parameter dot11RMNeighborReportActivated value is true, construct a MLME-neighbor report _ request primitive according to a parameter in the MLME-neighbor report _ indication primitive, and send the MLME-neighbor report _ request primitive to a low-level management unit, where the MLME-neighbor report _ request primitive includes a parameter neighbor list, the neighbor list includes an Information element BSSID Information for indicating Information of a neighbor and optional Information elements, the BSSID Information includes a parameter exception High threshold, the exception High threshold is used for indicating whether the exception High threshold is used for indicating that the neighbor is an eh value, and the exception High threshold is used for indicating that the exception High is equal to the neighbor access point EHT, and the exception High-level access point broadcast parameter is equal to the neighbor access point or the neighbor access point broadcast EHT, and the exception High-level broadcast parameter is equal to the neighbor access point, and the exception High-level broadcast EHT access point broadcast parameters are equal to the neighbor access point, and the exception High-level broadcast parameters are equal to the neighbor access point broadcast parameters, and the neighbor access point broadcast parameters, when the exception High-level broadcast parameters are equal to the neighbor access point broadcast parameters, the neighbor broadcast parameters, and the neighbor access point broadcast parameters, the neighbor access point broadcast parameters, and the neighbor access point broadcast parameters, the neighbor, the EHT operation is used to indicate EHT system operating parameters of an EHT access point.

The embodiment of the present application further provides a wireless local area network, where the wireless local area network includes a terminal and an access device, the terminal is the terminal related to the above embodiment, and the access device is the access device related to the above embodiment.

The embodiment of the present application further provides a storage medium, where at least one program code is stored in the storage medium, and the at least one program code is loaded and executed by a processor, so as to implement the method for acquiring neighboring cell information or the method for sending neighboring cell information according to the foregoing embodiment.

It should be understood that, in various embodiments of the present application, the sequence numbers of the above-mentioned processes do not mean the execution sequence, some or all of the steps may be executed in parallel or executed sequentially, and the execution sequence of each process should be determined by its function and inherent logic, and should not constitute any limitation to the implementation process of the embodiments of the present application.

Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.

In the several embodiments provided in the present application, it should be understood that the disclosed system, apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. For example, the flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of apparatus, methods and computer program products according to various embodiments of the present application. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit.

The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application or portions thereof that substantially contribute to the prior art may be embodied in the form of a software product stored in a storage medium and including instructions for causing a computer device (which may be a personal computer, a server, a network device or a terminal device, etc.) to execute all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: u disk, removable hard disk, ROM, RAM) magnetic or optical disk, or the like.

The terminology used in the embodiments of the present application is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. As used in the examples of this application and the appended claims, the singular forms "a", "an", and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and/or" as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items. The character "/" herein generally indicates that the former and latter associated objects are in an "or" relationship.

The word "if" or "if" as used herein may be interpreted as "at … …" or "when … …" or "in response to a determination" or "in response to a detection", depending on the context. Similarly, the phrases "if determined" or "if detected (a stated condition or event)" may be interpreted as "when determined" or "in response to a determination" or "when detected (a stated condition or event)" or "in response to a detection (a stated condition or event)", depending on the context.

The above description is only for the specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present application, and shall be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. A method for obtaining adjacent area information is applied to a terminal, wherein the terminal comprises a low-level management unit and a high-level management unit, and the method is characterized by comprising the following steps:

a low-layer management unit of a terminal receives a Neighbor Report Response frame sent by an access point, wherein the Neighbor Report Response frame comprises a parameter Neighbor list set, the Neighbor list set comprises an Information element BSSID Information and optional Information elements, the BSSID Information comprises a parameter explicit High threshold, the explicit High threshold is used for indicating whether the Neighbor is an EHT access point, when the explicit High threshold indicates that the Neighbor is the EHT access point, the explicit High threshold comprises a parameter EHT Capability and/or EHT operation, the parameter T Capability and/or EHT operation are set to be the same as the parameter broadcasted in the broadcast message of the Neighbor, and the parameter T Capability and/or EHT operation is used for indicating the Capability of the EHT system;

2. The method for acquiring neighboring cell Information as claimed in claim 1, wherein the BSSID Information further includes one or more of the following parameters:

the AP MLD is used for indicating whether the adjacent cells are the access points to which the same multilink equipment belongs;

and the STR MLD is used for indicating whether the multilink equipment to which the adjacent cell belongs supports STR or not, and the STR indicates the capability that a plurality of links of the multilink equipment can independently receive or transmit at the same time.

3. The method of claim 1, wherein the EHT Capability includes parameters MAC Capability and PHY Capability, and the MAC Capability includes one or more of the following parameters:

trigger P2P support for indicating whether to support access point Triggered point-to-point data transmission;

a Multilink support for indicating whether a Multilink operation is supported;

a MultiAP support for indicating whether a multi-point cooperative operation is supported;

a 1024-bit BA bitmap support for indicating whether to support bitmap block feedback of a maximum 1024-bit;

an STR support for indicating whether simultaneous independent transmission and reception is supported;

one or more of the following parameters are included in the PHY Capability:

an EHT MU with 4 × LTF +0.8 μ s GI to indicate whether reception of an EHU MU PPDU with 4 × LTF and 0.8 μ s guard interval is supported;

an 80MHzin 160/80+80MHz EHT PPDU for indicating whether the terminal is supported to perform Orthogonal Frequency Division Multiplexing Access (OFDMA) using 160MHz or 80MHz +80MHz resource units over an 80MHz bandwidth;

an 80MHzin 320/160+160MHz EHT PPDU for indicating whether the terminal is supported to perform OFDMA using 320MHz or 160MHz +160MHz resource units over an 80MHz bandwidth;

an 80MHzin 240/160+80MHz EHT PPDU for indicating whether a terminal is supported to perform OFDMA using 240MHz or 160MHz +80MHz resource units over an 80MHz bandwidth;

160MHz 320/160+160MHz EHT PPDU for indicating whether a terminal is supported to perform OFDMA using 320MHz or 160MHz +160MHz resource units over a 160MHz bandwidth;

160MHz 240/160+80MHz EHT PPDU for indicating whether a terminal is supported to perform OFDMA using 240MHz or 160MHz +80MHz resource units over a 160MHz bandwidth.

4. The method of claim 1, wherein the EHT operation includes one or more of the following parameters:

a ChannelWidth field for indicating a channel bandwidth of operation;

a CCFS field for indicating a channel center frequency band;

the Basic EHT-MCS and NSS set is used for indicating a modulation coding strategy supported by an EHT system corresponding to each group of space stream number in the receiving and transmitting of the EHT PPDU;

an Align start time of PPDU for indicating whether to start sending PPDU on different links at the same time;

an Align end time of PPDU for indicating whether to finish sending PPDU on different links at the same time.

5. The method of claim 1, wherein the optional sub-Elements further include parameters ML Elements, and the ML Elements are used for indicating multilink operation parameters.

6. The method of claim 3, wherein the EHT Capability further comprises a parameter ML Elements, and the ML Elements are used for indicating multilink operation parameters.

7. The method of claim 6, wherein the ML Elements are included in a MAC Capability of the EHT Capability, and the ML Elements include the Multilink support.

8. The method of claim 4, wherein the EHT operation further includes a parameter ML Elements, and the ML Elements are used for indicating multilink operation parameters.

9. The method of claim 8, wherein the ML Elements include the Align start time of PPDU and the Align end time of PPDU.

10. The method for acquiring neighboring cell information according to any one of claims 5-9, wherein the ML Elements include one or more of the following parameters:

the MLD index is used for indicating whether the adjacent cell and the access point which is currently connected belong to the same multilink equipment and the identification multilink equipment or not;

a LinkID to indicate a link on a multilink device;

a Change sequence used for indicating the sequence number of the key system message Change on the adjacent cell;

STRs used for indicating whether the multilink equipment to which the adjacent cell belongs supports STR.

11. The method of claim 10, wherein the MLD index, when set to a first value, indicates that the neighboring cell and a currently connected access point belong to a same multi-link device; when set to other values, an index number indicating BSSIDs in the same multiple BSSID set, or an identifier uniquely identifying a multi-link device.

12. The method of claim 2, wherein when the AP MLD is set to the second value, indicating that the neighboring cell and the currently connected access point belong to the same multilink device; and when the value is set to the third value, indicating that the adjacent cell is not the access point of the multilink equipment or the access point of the multilink equipment, but does not belong to the same multilink equipment as the currently connected access point.

13. The method of claim 2, wherein when the APMLD is set to a fourth value, indicating that the neighboring cell and the currently connected access point belong to the same multi-link device; when the value is set to the fifth value, indicating that the adjacent cell is not the access point of the multilink equipment; and when the value is set to the sixth value, indicating that the adjacent cell is the access point of the multilink equipment, but the adjacent cell does not belong to the same multilink equipment with the currently connected access point.

14. The method of claim 1, wherein the method further comprises:

after receiving the MLME-NEIGHBORREPRESP.indication primitive, a high-level management unit of the terminal stores the parameter NeighborListSet;

if the terminal is a multilink terminal and the access point needs to be replaced, if the replacement reason is mobility, other access points which are indicated as being affiliated to the same multilink equipment with the currently connected access point are not taken as candidate access points;

if the terminal is a multilink terminal and when the access point needs to be replaced, if the replacement reason is load balancing, other access points which are indicated to be subordinate to the same multilink device as the currently connected access point are preferentially selected.

15. A method for sending neighbor cell information is applied to an access device, the access device comprises a low-layer management unit and a high-layer management unit, and the method is characterized by comprising the following steps:

after receiving the MLME-neighbor report request.indication primitive, a High level management unit of an access device constructs a MLME-neighbor report request.request primitive according to a parameter in the MLME-neighbor report request.indication primitive and sends the MLME-neighbor report request.request primitive to a low level management unit if a locally configured parameter dot11 rmneighborreportactived value is true, the MLME-neighbor report request.request primitive includes a parameter neighbor list, the neighbor list includes an Information element BSSID Information for indicating Information of a neighbor and optional Information elements, the BSSID Information includes a parameter exception High threshold, the exception High level threshold is used for indicating whether the neighbor is an eh channel, the exception High level threshold is used for indicating whether the EHT channel is used for indicating that the access point EHT channel is the same as the access point, and the access point broadcasts the access point is the same as the neighbor access point, and the access point broadcasts the exception access point is the same as the access point for the access point. The EHT operation is used for indicating an EHT system operating parameter of an EHT access point;

16. The method for sending neighbor Information according to claim 15, wherein the BSSID Information further includes one or more of the following parameters:

17. The method of claim 15, wherein the EHT Capability includes MAC Capability and PHY Capability, and wherein the MAC Capability includes one or more of the following parameters:

a Multilink support for indicating whether a Multilink operation is supported;

one or more of the following parameters are included in the PHY Capability:

160MHz in 240/160+80MHz EHT PPDU for indicating whether a terminal is supported to perform OFDMA using 240MHz or 160MHz +80MHz resource units over a 160MHz bandwidth.

18. The method of claim 15, wherein the EHT operation includes one or more of the following parameters:

a ChannelWidth field for indicating a channel bandwidth of operation;

a CCFS field for indicating a channel center frequency band;

19. The method of claim 15, wherein the optional sub-Elements further include parameters ML Elements, and the ML Elements are used for indicating multilink operation parameters.

20. The method of claim 17, wherein the EHT Capability further comprises a parameter ML Elements, and wherein the ML Elements are used for indicating multilink operation parameters.

21. The method of claim 20, wherein the ML Elements are included in a MAC Capability of the EHT Capability, and the ML Elements include the Multilink support.

22. The method of claim 18, wherein the EHT operation further includes a parameter ML Elements, and the ML Elements are used for indicating a multilink operation parameter.

23. The method of claim 22, wherein the ML Elements include the Align start time of PPDU and the Align end time of PPDU.

24. The method of any one of claims 19-23, wherein the ML Elements comprise one or more of the following parameters:

a LinkID to indicate a link on a multilink device;

25. The method of claim 24, wherein the MLD index, when set to the first value, indicates that the neighboring cell and a currently connected access point belong to the same multi-link device; when set to other values, an index number indicating BSSIDs in the same multiple BSSID set, or an identifier uniquely identifying a multi-link device.

26. The method of claim 16, wherein when the APMLD is set to the second value, indicating that the neighboring cell and the currently connected access point belong to the same multi-link device; and when the value is set to the third value, indicating that the adjacent cell is not the access point of the multilink equipment or the access point of the multilink equipment, but does not belong to the same multilink equipment as the currently connected access point.

27. The method of claim 16, wherein when the AP MLD is set to a fourth value, indicating that the neighboring cell and the currently connected access point belong to the same multi-link device; when the value is set to the fifth value, indicating that the adjacent cell is not the access point of the multilink equipment; and when the value is set to the sixth value, indicating that the adjacent cell is the access point of the multilink equipment, but the adjacent cell does not belong to the same multilink equipment with the currently connected access point.

28. A terminal comprising a lower management unit and a higher management unit, wherein,

the high-level management unit is used for sending MLME-NEIGHBORREPREQ.request primitive to the low-level management unit;

a low-layer management unit, configured to send a Neighbor Report Request frame to an access point after receiving the MLME-Neighbor Report req.request primitive; receiving a Neighbor Report Response frame sent by an access point, wherein the Neighbor Report Response frame contains a parameter Neighbor List, the Neighbor List contains an Information element BSSID Information and optional Information elements, the BSSID Information contains a parameter egress High Throughput, the egress High Throughput is used for indicating whether a Neighbor cell is an access point, when the egress High Throughput indicates that the Neighbor cell is an EHT access point, the egress High Throughput contains a parameter EHT Capability and/or EHT operation, and the parameter EHT Capability and/or EHT operation are the same as the parameter broadcast in the broadcast message of the Neighbor cell and are set to the same value, and the EHT Capability is used for indicating the Capability of the system EHT, and the access point is used for indicating the Capability of the system EHT; and sending an MLME-NEIGHBORREPRESP.indication primitive to a high-level management unit, wherein the MLME-NEIGHBORREPRESP.indication primitive comprises the parameter NeighborListSet.

29. An access device comprising a lower management unit and a higher management unit, wherein,

the low-layer management unit is used for receiving a Neighbor Report Request frame sent by the terminal and sending MLME-NEIGHBORREPREQ.indication primitive to the high-layer management unit; after receiving MLME-NEIGHBORREPRESP.request primitive sent by a high-level management unit, sending a Neighbor Report Response frame to a terminal, wherein the Neighbor Report Response frame comprises a parameter NeighborListset;

a High-level management unit, configured to, after receiving the MLME-neighbor report _ indication primitive, if a locally configured parameter dot11RMNeighborReportActivated value is true, construct a MLME-neighbor report _ request primitive according to a parameter in the MLME-neighbor report _ indication primitive, and send the MLME-neighbor report _ request primitive to a low-level management unit, where the MLME-neighbor report _ request primitive includes a parameter neighbor list, the neighbor list includes an Information element BSSID Information for indicating Information of a neighbor and optional Information elements, the BSSID Information includes a parameter exception High threshold, the exception High threshold is used for indicating whether the exception High threshold is used for indicating that the neighbor is an eh value, and the exception High threshold is used for indicating that the exception High is equal to the neighbor access point EHT, and the exception High-level access point broadcast parameter is equal to the neighbor access point or the neighbor access point broadcast EHT, and the exception High-level broadcast parameter is equal to the neighbor access point, and the exception High-level broadcast EHT access point broadcast parameters are equal to the neighbor access point, and the exception High-level broadcast parameters are equal to the neighbor access point broadcast parameters, and the neighbor access point broadcast parameters, when the exception High-level broadcast parameters are equal to the neighbor access point broadcast parameters, the neighbor broadcast parameters, and the neighbor access point broadcast parameters, the neighbor access point broadcast parameters, and the neighbor access point broadcast parameters, the neighbor, the EHT operation is used to indicate EHT system operating parameters of an EHT access point.

30. A wireless local area network comprising a terminal and an access device, wherein the terminal is the terminal of claim 28 and the access device is the access device of claim 29.

31. A storage medium, characterized in that at least one program code is stored in the storage medium, and loaded and executed by a processor to implement the method for obtaining neighbor information according to any one of claims 1-14 or the method for sending neighbor information according to any one of claims 15-27.