Method, device and system for distributing AID

Abstract

The invention provides a method, a device and a system for allocating an AID, and belongs to the technical field of network communication. The method comprises: a management device obtains parameters of an STA, the management device allocates an AID for the STA based on the parameters of the STA, and determines a first AP in a plurality of APs managed by the management device, the first AP being used for sending the AID to the STA, the BSSIDs of the plurality of APs being the same, at least one AP in the plurality of APs receiving an authentication request sent by the STA, and the first AP belonging to the at least one AP. And the management equipment sends the AID and the identifier of the STA to the first AP. By adopting the scheme provided by the invention, different STAs can correspond to different AIDs, so that the AP can distinguish the STAs when the STAs send the message carrying the AIDs to the AP and the source MAC address is not carried.

Description

[0001] This application is a divisional application. The application number of the original application is 202210087389.2, and the original application date is January 25, 2022. The entire content of the original application is incorporated herein by reference. Technical Field

[0002] This application relates to the field of network communication technologies, and particularly relates to a method, apparatus, and system for allocating an AID. Background Art

[0003] In a wireless local area network (WLAN), when a station (STA) accesses the WLAN, an access point (AP) will allocate an association identifier (AID) to the STA. This AID is used to identify that a corresponding relationship has been established between the STA and the AP, and the STA and the AP can communicate. Usually, when the AP allocates an AID to the STA, it allocates it to the STA in ascending order starting from 1.

[0004] In a traditional network architecture, the basic service set identifier (BSSID) of each AP is independent, and each AP manages the AIDs of the STAs associated with itself. Since the AID allocated by the AP to its associated STA is unique, in a network architecture identified by a BSSID, the AID can also be used to identify the STA in some messages instead of the media access control (MAC) address. For example, the scheduling information of the corresponding STA is distinguished by the AID.

[0005] However, with the development of communication technologies, a network architecture in which multiple APs share a BSSID appears. If the traditional allocation method is still used to allocate AIDs (for example, in this network architecture, multiple APs respectively allocate AIDs to the STAs accessing themselves), it is possible that two APs allocate the same AID to different STAs. In this way, since there are STAs with the same AID in a network architecture identified by a BSSID, when the STA sends a message carrying the AID to the AP without carrying the source MAC address, the AP cannot distinguish the STA. Summary of the Invention

[0006] This application provides a method, apparatus, system, device, and storage medium for allocating an AID, which solves the problem that the AP cannot distinguish the STA in a network architecture identified by a BSSID.

[0007] In a first aspect, the present application provides a method for allocating an AID, which is executed by a management device. The method includes:

[0008] The management device obtains the parameters of the STA; based on the parameters of the STA, the management device allocates an AID for the STA, and determines a first AP among multiple APs managed by the management device. The first AP is used to send the AID to the STA. The BSSIDs of the multiple APs are the same, and at least one of the multiple APs receives an authentication request sent by the STA. The first AP belongs to the at least one AP; the management device sends the AID and the identifier of the STA to the first AP.

[0009] In the solution shown in the present application, the management device uses the parameters of the STA to allocate an AID for the STA. The management device determines the first AP that sends the AID to the STA, and the management device sends the AID and the identifier of the STA to the first AP, so that the first AP sends the AID to the STA. In this way, in a network architecture where multiple APs share the same BSSID, the management device uniformly allocates AIDs for STAs, so that the AIDs allocated for each STA under this network architecture are different. Furthermore, when the STA sends a message carrying the AID to the AP without carrying the source MAC address, the AID can also be used to distinguish the STA.

[0010] In a possible implementation, the method further includes: the management device sends the AID and the identifier of the STA to other APs except the first AP among the multiple APs. In this way, since the AID corresponding to the STA will also be recorded in other APs, after the STA roams to other APs, there is no need to re-authenticate and re-associate, which can save the access network duration.

[0011] In a possible implementation, the method further includes: the management device detects that the STA is offline; the management device sends a recovery message to each of the multiple APs, and the recovery message is used to indicate the recovery of the AID.

[0012] In the solution shown in the present application, after the STA is offline, the management device can notify each AP to recover the AID corresponding to the STA, so that the AID can be allocated to other STAs subsequently, saving the resources of the AID.

[0013] In a possible implementation, the multiple APs and the management device form a fiber to the room (FTTR) network architecture. The management device carries the AID and the identifier of the STA through an allocation message. The AID and the identifier of the STA are located in the payload field of the allocation message, and the destination address of the allocation message is the identifier of the AP that receives the allocation message. Wherein, the identifier of each AP is used to uniquely identify the AP.

[0014] In a possible implementation, the multiple APs and the management device form an Ethernet architecture, and the management device carries the AID and the identifier of the STA through an Ethernet frame, where the AID and the identifier of the STA are located in the payload field of the Ethernet frame.

[0015] In a possible implementation, the multiple APs and the management device form an architecture of a passive optical network (PON), and the management device carries the AID and the identifier of the STA through an optical network unit management and control interface (OMCI) message, where the AID and the identifier of the STA are located in the message content field of the OMCI message.

[0016] In a possible implementation, the management device obtains the parameters of the STA, including: the management device receives an authentication report message sent by at least one of the multiple APs, and the authentication report message includes the parameters of the STA; the management device obtains the parameters of the STA from the authentication report message. In this way, the management device can obtain the parameters of the STA from the authentication report message.

[0017] In a possible implementation, the method further includes: the management device obtains the characteristic information of the at least one AP, and the characteristic information of each AP includes at least one of load information, interference information received, and signal quality information received from the STA; determining a first AP among the multiple APs managed by the management device includes: the management device determines the connection quality of the at least one AP with the STA respectively based on the characteristic information of the at least one AP, and determines the AP with the highest connection quality among the at least one AP as the first AP.

[0018] In the solution shown in this application, the management device uses the characteristic information of at least one AP to determine the AP with the highest connection quality among the at least one AP as the AP to be associated with the STA. In this way, the at least one AP is the AP that sends the authentication report message to the management device, that is, the at least one AP is the AP that receives the authentication request sent by the STA. Then each AP among the at least one AP can communicate with the STA, and selecting the AP with the highest connection quality among these APs can ensure that the selected AP can communicate with the STA.

[0019] In a possible implementation, the method further includes: the management device detects that the STA moves from the coverage area of the first AP to the coverage area of the second AP among the multiple APs; the management device sends a notification message to the second AP, where the notification message is used to instruct the second AP to connect to the STA. In this way, after the STA roams to the coverage area of the second AP, the management device can notify the second AP to provide the function of forwarding packets for the STA, so that the STA does not perceive the AP handover.

[0020] In a second aspect, the present application provides a method for allocating an AID. The method is executed by a first AP and includes:

[0021] The first AP receives the AID and the identifier of the STA sent by the management device, where the AID is the AID allocated by the management device for the STA; the first AP stores the identifier of the STA and the AID in correspondence.

[0022] In the solution shown in the present application, in a network architecture where multiple APs share a BSSID, the management device uniformly allocates AIDs for STAs, so that the AIDs allocated for each STA in this network architecture are different. Furthermore, when the STA sends a message carrying the AID to the AP without carrying the source MAC address, the AID can also be used to distinguish the STA.

[0023] In a possible implementation, the method further includes: when the first AP is the AP specified by the management device to be associated with the STA, the first AP sends the AID to the STA. In this way, the AP specified by the management device sends the AID to the STA, which not only enables the STA to obtain its corresponding AID, but also prevents the STA from receiving the AID repeatedly.

[0024] In a possible implementation, before the first AP receives the AID and the identifier of the STA sent by the management device, it further includes: the first AP receives an authentication request sent by the STA, where the authentication request includes the parameters of the STA; the first AP sends an authentication report message to the management device, where the authentication report message includes the parameters of the STA; after the first AP receives the AID and the identifier of the STA sent by the management device, it further includes: when the first AP is the AP specified by the management device to be associated with the STA, the first AP sends an authentication response message to the STA.

[0025] In the solution shown in this application, after the first AP receives the authentication request sent by the STA, it notifies the management device, enabling the management device to allocate an AID to the STA. And when the first AP is designated as the AP associated with the STA, it sends an authentication response message to the STA, enabling the STA to continue the process of accessing the network. Moreover, only the AP associated with the STA sends the authentication response message to the STA, so that the STA will not receive the authentication response message repeatedly.

[0026] In a possible implementation, the method further includes: the first AP receives the recycling message sent by the management device, where the recycling message is used to indicate recycling the AID; the first AP recycles the AID.

[0027] In the solution shown in this application, after the first AP receives the recycling message of the AID, it recycles the AID, so that the AID can still be allocated to other STAs, saving the resources of the AID.

[0028] In a third aspect, this application provides a device for allocating an AID, and the device has the function of implementing the first aspect or any optional manner of the first aspect above. The device includes at least one module, and at least one module is used to implement the method for allocating an AID provided by the first aspect or any optional manner of the first aspect above.

[0029] In a fourth aspect, this application provides a device for allocating an AID, and the device has the function of implementing the second aspect or any optional manner of the second aspect above. The device includes at least one module, and at least one module is used to implement the method for allocating an AID provided by the second aspect or any optional manner of the second aspect above.

[0030] In a fifth aspect, this application provides a management device, and the management device includes a network interface, a memory, and a processor connected to the memory;

[0031] The network interface is used to obtain the parameters of the STA and send the identifier and AID of the STA to the first AP;

[0032] The memory is used to store computer instructions;

[0033] The processor is used to execute the computer instructions, so that the management device implements the method for allocating an AID provided by the first aspect or any optional manner of the first aspect above.

[0034] In a sixth aspect, this application provides an AP, and the AP includes a network interface, a memory, and a processor connected to the memory;

[0035] The network interface is used to receive the identifier and AID of the STA sent by the management device;

[0036] The memory is used to store computer instructions;

[0037] The processor is used to execute the computer instructions, so that the AP implements the method for allocating AID provided in the second aspect or any optional manner of the second aspect.

[0038] In a seventh aspect, the present application provides a computer-readable storage medium, in which at least one computer instruction is stored, and the computer instruction is read by a processor to enable a management device to execute the method for allocating AID provided in the first aspect or any optional manner of the first aspect.

[0039] In an eighth aspect, the present application provides a computer-readable storage medium, in which at least one computer instruction is stored, and the computer instruction is read by a processor to enable the AP to execute the method for allocating AID provided in the second aspect or any optional manner of the second aspect.

[0040] In a ninth aspect, the present application provides a computer program product, which includes computer instructions stored in a computer-readable storage medium. A processor of a management device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the management device executes the method for allocating AID provided in the first aspect or any optional manner of the first aspect.

[0041] In a tenth aspect, the present application provides a computer program product, which includes computer instructions stored in a computer-readable storage medium. A processor of the AP reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the AP executes the method for allocating AID provided in the second aspect or any optional manner of the second aspect.

[0042] In an eleventh aspect, the present application provides a system for allocating AID, which includes a management device and an AP. The management device is used to execute the method for allocating AID provided in the first aspect or any optional manner of the first aspect, and the AP is used to execute the method for allocating AID provided in the second aspect or any optional manner of the second aspect. Description of the Drawings

[0043] Figure 1 is a schematic diagram of a traditional network architecture provided by an exemplary embodiment of the present application;

[0044] Figure 2 is a schematic diagram of multiple APs sharing a single BSSID provided by an exemplary embodiment of the present application;

[0045] Figure 3It is a schematic structural diagram of a system for allocating AID provided by an exemplary embodiment of the present application;

[0046] Figure 4 It is a schematic structural diagram of a device provided by an exemplary embodiment of the present application;

[0047] Figure 5 It is a schematic structural diagram of an AP provided by an exemplary embodiment of the present application;

[0048] Figure 6 It is a schematic flowchart of a method for allocating AID provided by an exemplary embodiment of the present application;

[0049] Figure 7 It is another schematic flowchart of a method for allocating AID provided by an exemplary embodiment of the present application;

[0050] Figure 8 It is yet another schematic flowchart of a method for allocating AID provided by an exemplary embodiment of the present application;

[0051] Figure 9 It is a schematic diagram of an AID allocation field provided by an exemplary embodiment of the present application;

[0052] Figure 10 It is another schematic diagram of an AID allocation field provided by an exemplary embodiment of the present application;

[0053] Figure 11 It is a schematic diagram of an allocation message provided by an exemplary embodiment of the present application;

[0054] Figure 12 It is a schematic diagram of an Ethernet frame provided by an exemplary embodiment of the present application;

[0055] Figure 13 It is a schematic diagram of an OMCI message provided by an exemplary embodiment of the present application;

[0056] Figure 14 It is a schematic diagram of STA roaming provided by an exemplary embodiment of the present application;

[0057] Figure 15 It is a schematic flowchart of reclaiming AID provided by an exemplary embodiment of the present application;

[0058] Figure 16 It is a schematic diagram of an AID allocation field and an AID reclamation field provided by an exemplary embodiment of the present application;

[0059] Figure 17 It is a schematic diagram of a reclamation message provided by an exemplary embodiment of the present application;

[0060] Figure 18 It is a schematic structural diagram of a device for allocating AIDs provided by an exemplary embodiment of the present application;

[0061] Figure 19 It is another schematic structural diagram of a device for allocating AIDs provided by an exemplary embodiment of the present application. Detailed implementation manners

[0062] To make the objectives, technical solutions, and advantages of the present application clearer, the following will further describe the embodiments of the present application in detail with reference to the accompanying drawings.

[0063] The following describes the solutions of the related technologies.

[0064] In the related technologies, in a traditional network architecture, each BSSID identifies a network architecture. Each network architecture includes an AP, and the AP in each network architecture manages the AIDs of the STAs associated with itself. Since the AIDs assigned by the AP to its associated STAs are unique, in a network architecture identified by a BSSID, the AID can also be used to identify the STA in some messages instead of the MAC address. For example, as Figure 1 shown, three network architectures respectively include AP1, AP2, and AP3. AP1 assigns AID1 to STA1, AP1 assigns AID2 to STA2, AP2 assigns AID1 to STA3, AP3 assigns AID1 to STA4, and AP3 assigns AID2 to STA5. Since the BSSIDs of AP1 and AP2 are different, even if only AID1 is carried in the messages sent by STA1 and STA3, there will be no confusion.

[0065] However, with the development of communication technologies, there appears a network architecture in which multiple APs share a BSSID. If multiple APs in this network architecture respectively assign AIDs to the STAs accessing them, it is possible that two APs assign the same AID to different STAs. In this way, since there are STAs with the same AID in a network architecture identified by a BSSID, when an STA sends a message carrying the AID to the AP without carrying the source MAC address, the AP will be unable to distinguish the STA, and when the AP sends a message carrying the AID to the STAs associated with itself, confusion will occur on the STA side. For example, as Figure 2As shown in the figure, a network architecture includes AP4 and AP5. AP4 assigns AID1 to STA6, AP5 assigns AID1 to STA7, and AP5 assigns AID2 to STA8. Since in a network architecture identified by a BSSID, the MAC addresses of each AP are the same, when STA6 sends a message with AID1 and without the source MAC address, both AP4 and AP5 will receive the message, and it is impossible to distinguish whether the message belongs to STA6 or STA7. AP4 sends a beacon frame indicating that STA6 with AID1 has data to be transmitted. The sleep of STA6 will be awakened, and at the same time, STA7 will mistakenly think that it also has data to be transmitted, and its sleep will also be awakened, affecting the energy-saving efficiency.

[0066] In this application, in a network architecture where multiple APs share a BSSID, the management device uniformly assigns AIDs to STAs, so that the AIDs assigned to each STA in this network architecture are different. Furthermore, when a STA sends a message carrying an AID to an AP without carrying the source MAC address, the AID can also be used to distinguish the STA.

[0067] Next, in the order of the system for assigning AIDs, the hardware structures of various devices in the system, and the method for assigning AIDs, the technical solutions provided by the embodiments of this application will be specifically described from multiple perspectives.

[0068] The following introduces the system for assigning AIDs provided by the embodiments of this application.

[0069] See Figure 3 , the embodiments of this application provide a system 300 for assigning AIDs. The system 300 includes multiple APs 301 and a management device 302. The multiple APs 301 form a network architecture. In this network architecture, the BSSIDs of the APs 301 are the same, the MAC addresses of each AP 301 are the same, and the coverage ranges of two adjacent APs 301 may or may not overlap. For example, the AP 301 can be a router, a switch, an optical modem, etc. The management device 302 is used to assign AIDs. The management device 302 can be an AP in the network architecture, and this AP is called a central AP, such as the AP with the strongest capabilities in the network architecture, or it can be an access controller responsible for managing multiple APs 301. Among them, the embodiments of this application do not limit the number and type of APs.

[0070] The management device 302 can communicate with each AP 301, such as through optical fiber communication, through cable communication, or through wireless communication, etc. In one implementation, the management device 302 and multiple APs 301 form an FTTR network architecture. The management device 302 is an optical gateway, and multiple APs 301 are edge APs. The edge APs are used for STAs to access. The optical gateway and the edge APs are connected by optical fiber, by wireless connection, or by cable connection. In another implementation, the management device 302 and multiple APs 301 form an Ethernet architecture. In another implementation, the management device 302 and multiple APs 301 form a PON architecture, and the management device 302 and multiple APs 301 are connected by optical fiber. The description here of the management device 302 and multiple APs 301 forming a PON architecture is to illustrate that the network architecture between the management device 302 and multiple APs 301 is similar to a PON.

[0071] The system architecture provided by the embodiments of the present application is introduced above. Next, the hardware structure of the devices in the above system architecture will be introduced.

[0072] Please refer to Figure 4 , Figure 4 The device 400 shown is an example illustration of the AP 301 and the management device 302 in the above system architecture. Optionally, the device 400 is configured as an AP 301, a management device 302, etc.

[0073] The device 400 is optionally implemented by a general bus architecture. The device 400 includes at least one processor 401, a communication bus 402, a memory 403, and at least one network interface 404.

[0074] The processor 401 is, for example, a general-purpose central processing unit (CPU), a network processor (NP), a Graphics Processing Unit (GPU), a neural-network processing unit (NPU), a Data Processing Unit (DPU), a microprocessor, or one or more integrated circuits for implementing the solution of this application. For example, the processor 401 includes an application-specific integrated circuit (ASIC), a programmable logic device (PLD), or a combination thereof. The PLD is, for example, a complex programmable logic device (CPLD), a field-programmable gate array (FPGA), a generic array logic (GAL), or any combination thereof.

[0075] The communication bus 402 is used to transmit information between the above components. The communication bus 402 can be divided into an address bus, a data bus, a control bus, etc. For the sake of simplicity of representation, only a thick line is shown in the figure, but it does not mean that there is only one bus or one type of bus. Figure 4 In the figure, only a thick line is shown, but it does not mean that there is only one bus or one type of bus.

[0076] The memory 403 is, for example, a read-only memory (ROM) or other type of static storage device that can store static information and instructions, such as a random access memory (RAM) or other type of dynamic storage device that can store information and instructions, such as an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM), or other optical disc storage, optical disc storage (including compact discs, laser discs, optical discs, digital versatile discs, Blu-ray discs, etc.), magnetic disk storage media, or other magnetic storage devices, or any other medium that can be used to carry or store the desired program code in the form of instructions or data structures and can be accessed by a computer, but is not limited thereto. The memory 403 exists independently, for example, and is connected to the processor 401 through the communication bus 402. The memory 403 can also be integrated with the processor 401.

[0077] Optionally, the memory 403 is used to store the AID and the like allocated by the device 400 for the SAT.

[0078] The network interface 404 uses any device such as a transceiver to communicate with other devices or communication networks. The network interface 404 includes a wired network interface and may also include a wireless network interface. Among them, the wired network interface can be, for example, an Ethernet interface. The Ethernet interface can be an optical interface, an electrical interface, or a combination thereof. The wireless network interface can be a WLAN interface, a cellular network interface, or a combination thereof, etc.

[0079] In a specific implementation, as an embodiment, the processor 401 may include one or more CPUs.

[0080] In a specific implementation, as an embodiment, the device 400 may include multiple processors. Each of these processors can be a single-core processor (single-CPU) or a multi-core processor (multi-CPU). Here, the processor can refer to one or more devices, circuits, and / or processing cores for processing data (such as computer program instructions).

[0081] In some embodiments, the memory 403 is used to store the program code 4031 for executing the solution of this application. The program code 4031 is a computer instruction, and the processor 401 can execute the program code 4031 stored in the memory 403. That is, the device 400 can implement the method for allocating the AID provided by the method embodiment through the processor 401 and the program code 4031 in the memory 403.

[0082] In another implementation, Figure 5 A schematic structural diagram of the AP301 is shown. The AP301 includes a main control board 3011 and an interface board 3012. The main control board 3011 belongs to the control plane of the AP301, and the interface board 3012 belongs to the data plane of the AP301. The main control board 3011 includes a processor and a memory. The interface board 3012 includes a processor, a memory, and an interface card.

[0083] A communication connection is established between the main control board 3011 and the interface board 3012.

[0084] The processor of the main control board 3011 can be a CPU or an ASIC, etc. The processor can include one or more chips. The memory of the main control board 3011 can be a ROM, a static storage device, a dynamic storage device, or a RAM. The memory of the main control board 3011 can store computer instructions. When the computer instructions stored in this memory are executed by the processor, the processor of the main control board 3011 executes the method of allocating AID.

[0085] The processor of the interface board 3012 can be a CPU, an ASIC, etc. The processor of the interface board 3012 can include one or more chips. The memory of the interface board 3012 can be a ROM, a static storage device, a dynamic storage device, or a RAM. The memory of the interface board 3012 can store computer instructions. When the computer instructions stored in this memory are executed by the processor of the interface board 3012, the processor of the interface board 3012 executes the method of allocating AID. The interface card can implement the sending and receiving processing of messages.

[0086] Next, the processing of the management device in the method flow of allocating AID in the embodiments of the present application is described. Refer to Figure 6 Steps 601 to 603 in it. In the following text, the AP is the AP301, and the management device is the management device 302.

[0087] Step 601, the management device obtains the parameters of the STA.

[0088] Among them, the STA is any device requesting to access the AP, such as a mobile phone, a tablet, a speaker, or a notebook, etc.

[0089] In this embodiment, the management device determines that the STA requests authentication and obtains the parameters of the STA. The parameters include but are not limited to the capability level and model of the STA, etc.

[0090] Step 602: The management device assigns an AID to the STA based on the parameters of the STA, and determines a first AP among multiple APs managed by the management device. The first AP is used to send the AID to the STA. The basic service set identifiers (BSSIDs) of the multiple APs are the same, and at least one of the multiple APs receives an authentication request sent by the STA.

[0091] In this embodiment, the management device verifies the parameters of the STA and determines whether to allow the STA to go online. For example, the management device determines whether the model of the STA belongs to the allowed access model, and determines whether the capability level of the STA meets the required capability level of the management device. If both meet the requirements, it is determined to allow the STA to go online; otherwise, the STA is not allowed to go online. If the STA is allowed to go online, an AID is assigned to the STA. For the convenience of description, this AID is referred to as the target AID. For example, the management device selects the AID with the smallest serial number among the currently unassigned AIDs. If the STA is not allowed to go online, the management device sends an authentication failure message to an AP that has received the authentication request, so that the AP sends an authentication response message to the STA, and the authentication response message indicates authentication failure.

[0092] And the management device determines a first AP among multiple APs it manages. The first AP is the AP to which the STA is to be associated, and the first AP is used to send the target AID to the STA. When the management device is the central AP, if the central AP determines that it is the first AP, step 603 may not be executed.

[0093] Optionally, when the management device assigns an AID, it can assign the AIDs in ascending order of the access sequence of the STAs. The range of the AIDs is from 1 to 2007, and each AID corresponds to an available flag bit, and this flag bit is default set to 1. After the target AID is assigned to the STA, the flag bit of the target AID is set to 0. In this way, when the management device assigns an AID to the STA, it assigns the AID with the flag bit set to 1, so that there is no STA using the same AID at the same time.

[0094] It should be noted that the multiple APs are the APs that the STA may access. In addition, since the selected first AP is for communicating with the STA, it should be able to communicate with the STA currently. Then the first AP belongs to the AP that has received the authentication request sent by the STA.

[0095] Step 603: The management device sends the AID and the identifier of the STA to the first AP.

[0096] In this embodiment, after the management device determines the target AID and the first AP, it sends the target AID and the identifier of the STA to the first AP. Among them, the identifier of the STA can be the MAC address of the STA or other unique identifiers that indicate the STA.

[0097] The following describes the processing of the AP in the method flow for allocating AIDs in the embodiments of the present application. Refer to Figure 7 Steps 701 to 702 in

[0098] Step 701, the first AP receives the AID and the identifier of the STA sent by the management device, where the AID is the AID allocated by the management device for the STA.

[0099] Step 702, the first AP stores the identifier of the STA and the AID in a corresponding manner.

[0100] In this embodiment, the first AP stores the identifier of the STA corresponding to the target AID, so that when the first AP receives a message including the target AID, it can determine that the message comes from the STA indicated by the identifier of the STA, and when the first AP sends a message to the STA, it only needs to carry the AID. In this way, the AID is generally 1 or 2 bytes, while the MAC address is 6 bytes. Carrying the AID can save the byte overhead of the message compared to carrying the MAC address.

[0101] Combined with Figure 6 Steps 701 to 702, the process of interaction between the management device and the first AP is shown in Figure 7 .

[0102] Based on Figure 7 The shown process, in a network architecture where multiple APs share a BSSID, the management device uniformly allocates AIDs for STAs, so that the AIDs allocated for each STA under this network architecture are different, and then the AID can be carried when sending a message to identify the STA.

[0103] The following explains the method of allocating AIDs from the perspectives of both the management device and the AP. Refer to Figure 8 The shown process.

[0104] Step 801, the STA sends an authentication request, and the authentication request includes the parameters of the STA.

[0105] In this embodiment, the STA first scans the wireless network. After the scan is completed, the scanned wireless networks are displayed on the screen. The user selects to connect to a wireless network with a network architecture including multiple APs (this network architecture corresponds to a BSSID). The STA generates an authentication request, and the authentication request includes the parameters of the STA. The parameters include but are not limited to the capability level and model of the STA, etc. The STA sends the authentication request. This is only one possible way to trigger the STA to send an authentication request, and the embodiments of the present application do not limit this.

[0106] Step 802: The first AP receives the authentication request sent by the STA.

[0107] In this embodiment, any AP that currently covers the STA can receive the authentication request sent by the STA. Here, it is assumed that the first AP receives the authentication request sent by the STA.

[0108] Step 803: The first AP sends an authentication report message to the management device. The authentication report message includes the parameters of the STA.

[0109] In steps 802 to 803, only the situation where the first AP receives the authentication request sent by the STA and sends an authentication report message to the management device is shown. It is possible that other APs also receive the authentication request sent by this STA, and these other APs will also send authentication report messages to the management device.

[0110] Step 804: The management device receives the authentication report messages sent by at least one AP among multiple APs. The authentication report message includes the parameters of the STA.

[0111] Among them, the authentication report message is used to indicate a request to perform an authentication operation for the STA.

[0112] In this embodiment, at least one AP will send an authentication report message to the management device, and the management device will receive the authentication report messages sent by at least one AP.

[0113] Step 805: The management device obtains the parameters of the STA from the authentication report message.

[0114] In this embodiment, a certain field in the authentication report message is specifically used to store the parameters of the STA, and the management device can obtain the parameters of the STA from this field.

[0115] Step 806: The management device obtains the feature information of at least one AP. The feature information of each AP includes at least one of load information, interference information received, and signal quality information for receiving the signal sent by the STA.

[0116] Among them, the at least one AP is the AP among multiple APs that receives the authentication request sent by the STA.

[0117] In one implementation, when the AP sends an authentication report message to the management device, the authentication report message includes the feature information of the AP. The feature information of the AP includes at least one of the load information of the AP, the interference information received, and the quality information of the signal received from the STA. The load information of the AP refers to the number of currently associated STAs or the number of remaining associable STAs. The interference information received by the AP refers to the interference value from other APs. The quality information of the signal received from the STA refers to the signal strength of the authentication request sent by the STA received by the AP, etc. The management device can obtain the feature information of the AP from the authentication report message.

[0118] In another implementation, the authentication report message does not include the feature information. The management device can send a request for obtaining the feature information to the AP, and the AP reports the feature information to the management device.

[0119] In another implementation, the authentication report message does not include the feature information. For the quality information, the management device can send a request for obtaining the quality information to the AP, and the AP reports the quality information of the signal received from the STA to the management device. For the load information, the management device can determine the number of STAs currently communicating with the AP. For example, when the management device first designates an STA to associate with the AP, it will record the communication between the AP and the STA. When the STA roams into the coverage area of another AP from the currently communicating AP, the management device will update the STA communicating with the AP. For the interference information received, the management device obtains the interference information reported by the AP last time and determines it as the interference information received.

[0120] Step 807, the management device allocates a target AID for the STA based on the parameters of the STA. The management device determines the connection quality between each of the at least one AP and the STA based on the feature information of the at least one AP, and determines the AP with the highest connection quality among the at least one AP as the first AP.

[0121] Among them, the at least one AP is the AP that receives the authentication request sent by the STA. Here, since the selected first AP is used to communicate with the STA, the AP that can currently receive the authentication request sent by the STA should be selected so that the STA can communicate with the first AP.

[0122] In this embodiment, the process of the management device allocating the target AID for the STA refers to the description in step 602 and will not be elaborated here.

[0123] When the feature information of at least one AP includes one type, for any AP, if the content included in the feature information of the AP is negatively correlated with the connection quality, then take the reciprocal of the content included in the feature information and determine it as the connection quality between the AP and the STA. If the content included in the feature information of the AP is positively correlated with the connection quality, then determine the content included in the feature information as the connection quality between the AP and the STA. For example, the feature information includes load information, and the load information is the number of STAs communicating with the AP. Take the reciprocal of the number of STAs and determine it as the connection quality with the STA.

[0124] When the feature information of at least one AP includes multiple types, for any AP, weight the various contents of the feature information to obtain a weighted value, and determine the weighted value as the connection quality. Here, when weighting, the content negatively correlated with the connection quality takes the reciprocal, and the reciprocal content is used for weighting. Specifically, the weights of the various contents in the feature information can be set according to actual needs, and the embodiments of the present application do not limit them.

[0125] After the management device determines the connection quality between the AP and the STA, it determines the AP with the highest connection quality as the first AP.

[0126] It should be noted that the above is only an exemplary method for determining the connection quality based on the feature information, and the embodiments of the present application do not limit it.

[0127] Step 808, the management device sends the target AID and the identifier of the STA to the first AP. And sends the target AID and the identifier of the STA to other APs except the first AP among the multiple APs.

[0128] In this embodiment, the management device has multiple ways to notify the target AID, and the following provides two feasible ways.

[0129] Method 1, the management device sends an allocation message to each AP. The allocation message includes an AID allocation field. The AID allocation field includes an STA identifier field, an AID field, and an indication field for responding to the authentication request. The identifier of the STA can be the MAC address of the STA. The target AID is stored in the AID field. See the Figure 9 shown AID allocation field. For the AID allocation field sent to the first AP, the content of the indication field for responding to the authentication request is used to indicate the first AP to send the target AID to the STA. For the AID allocation field sent to other APs except the first AP among the multiple APs, the content of the indication field for responding to the authentication request is used to indicate not to send the target AID to the STA. For example, in the AID allocation field sent to the first AP, the content of the indication field for responding to the authentication request is 1, and in the AID allocation field sent to other APs, the content of the indication field for responding to the authentication request is 0.

[0130] In the second method, the management device sends an allocation message to each AP. The allocation message includes an AID allocation field, and the AID allocation field includes an AP identification field, an STA identification field, and an AID field. Among them, the first AP's identification is stored in the AP identification field, and the first AP's identification uniquely indicates the first AP. The target AID is stored in the AID field. Refer to Figure 10 the AID allocation field shown. The AP that receives the AID allocation field determines whether its own identification is the same as the AP identification in the AID allocation field. If they are the same, it means that this AP is the first AP. If they are not the same, it means that this AP is another AP other than the first AP among the multiple APs.

[0131] In the first and second methods, after the management device sends the STA identification and the target AID to the other APs other than the first AP among the multiple APs, the other APs store the target AID and the STA identification. In this way, when the STA roams from the coverage area of the first AP to the coverage area of the other APs, even if the message carries the target AID but does not carry the STA identification, the other APs can still identify the STA.

[0132] Optionally, in order to distinguish the allocation message from the recycling message mentioned later, the AID allocation field includes a message identifier. The message identifier takes different values to identify the allocation message and the recycling message respectively. For example, when the message identifier is 1, the message is an allocation message, and when the message identifier is 0, the message is a recycling message.

[0133] It should be noted that in Figure 9 and Figure 10 the AID allocation field shown may be part of the AID allocation field.

[0134] Exemplarily, in different network architectures, the message format carrying the AID allocation field may be different. For example, multiple APs and the management device form an FTTR network architecture, and the management device is respectively connected to the multiple APs through optical fibers or wireless connections, etc. The message carrying the AID allocation field can be called an allocation message. Refer to Figure 11The allocation message shown includes an AID allocation field, a destination address field, a source address field, a message type field, a payload length field, and a payload field. The payload field can also be referred to as the net payload field. For an allocation message sent to any AP, the destination address is the identifier of that AP. The identifier of the AP uniquely indicates the AP, and different APs have different identifiers. Here, the identifier of the AP can be any content that can uniquely identify the AP, such as an index number, etc. For example, the destination address of the allocation message sent to the first AP is the index number of the first AP. The source address is the identifier of the management device. The identifier of the management device can be the MAC address of the management device, or an index identifier that uniquely identifies the management device. It should be noted that when the management device is the central AP, since the MAC addresses of the central AP and other APs are the same, the identifier of the management device is not the MAC address. The message type field indicates that the allocation message is a control message, rather than a data message.

[0135] Optionally, the allocation message further includes a reserved field.

[0136] Multiple APs and the management device form an Ethernet architecture. The management device and multiple APs are respectively connected by optical fibers or cables. The format of the allocation message carrying the AID allocation field is an Ethernet frame. Refer to Figure 12 the Ethernet frame shown. The AID allocation field is located in the payload field of the Ethernet frame. In Figure 12 the Ethernet frame shown, if the management device is not the central AP in the network architecture, the source address is the MAC address of the management device, and the destination address is the virtual MAC address of the AP that receives the Ethernet frame. If the management device is the central AP in the network architecture, the source address is the virtual MAC address of the management device, and the destination address is the virtual MAC address of the AP that receives the Ethernet frame. Here, within a network architecture identified by a BSSID, since the MAC addresses of each AP are the same, in order to distinguish different APs, a virtual MAC address is assigned to each AP to distinguish different APs. For example, after each AP goes online, the management device assigns different virtual MAC addresses to each AP. In addition, the virtual MAC address of each AP is invisible to the STA. When the AP communicates with the STA, the MAC address of the AP is carried, rather than the virtual MAC address.

[0137] In addition, the Ethernet frame further includes a type field, a length field, a frame check sequence (FCS) field, etc.

[0138] Multiple APs and a management device form a PON architecture, and the management device is connected to the multiple APs through an optical distribution network (ODN). The format of the allocation message carrying the AID allocation field is the format of an OMCI message. Refer to the OMCI message shown in Figure 13. The AID allocation field is located in the MessageContents field of the OMCI message. In Figure 13 In the OMCI message shown, the OMCI message further includes a Gigabit-Capable PON encapsulation mode (GEM) Header field, a Transaction Correlation Identifier field, a Message Type field, a Device Identifier field, a Message Identifier field, and an OMCI Trailer field, etc.

[0139] Among them, the GEM Header field includes the GEM payload length, the GEM port identifier, the payload type indicator (PTI), and the header error check (HEC), etc. Different GEM port identifiers are used to identify different APs. After an AP receives an OMCI message, it can determine the OMCI message carrying its corresponding GEM port identifier as the OMCI message sent to itself.

[0140] The value of the Transaction Correlation Identifier field should be the same in a set of corresponding request and response messages. The Message Type field is used to identify the specific type of the message. For example, the content of the Message Type field is 0x20. The Device Identifier field is used to identify the type of the AP. The Message Identifier field is used to identify the general type of the message, and the Message Type belongs to one of the general types identified by the Message Identifier. The OMCI Trailer field is used for message verification.

[0141] Step 809, the first AP receives the target AID and the identifier of the STA sent by the management device.

[0142] Step 810, other APs except the first AP receive the target AID and the identifier of the STA sent by the management device.

[0143] In this embodiment, other APs except the first AP store the target AID and the identifier of the STA in a corresponding manner. In Figure 8 only the reception of the target AID and the identifier of the STA by the second AP is shown.

[0144] Step 811: The first AP stores the identifier of the STA and the target AID in a corresponding manner.

[0145] In this embodiment, the first AP stores the identifier of the STA and the target AID in a corresponding relationship, and records the capability information of the STA, etc. in this corresponding relationship.

[0146] Step 812: When the first AP is the AP associated with the STA designated by the management device, the first AP sends an authentication response message to the STA.

[0147] In this embodiment, when the first AP receives the target AID and the identifier of the STA, since the first AP is the device designated by the management device to respond to the STA, the first AP sends an authentication response message to the STA.

[0148] Step 813: The STA receives the authentication response message and sends an association request.

[0149] In this embodiment, after the STA receives the authentication response message sent by the first AP, the STA generates an association request. The association request includes, but is not limited to, the rates supported by the STA, channels, quality of service (QoS) capabilities, and the selected access authentication and encryption algorithms, etc. Then the STA sends the association request. Here, since the MAC addresses of the APs with the same BSSID are the same, for the STA, it just sends the association request to the AP with this MAC address, and all the APs covering the STA may receive the association request.

[0150] Step 814: The first AP receives the association request sent by the STA.

[0151] Step 815: When the first AP is the AP associated with the STA designated by the management device, the first AP sends an association response message to the STA, and the association response message includes the target AID.

[0152] In this embodiment, the first AP is the device associated with the STA designated by the management device. The first AP sends an association response message to the STA, and the target AID is included in this association response message.

[0153] In addition, other APs except the first AP may also receive the association request, but since other APs are not the devices designated to be associated with the STA, they will not send an association response message to this STA.

[0154] It should be noted that in the case where multiple APs and a management device form an FTTR network architecture, in step 803, the format of the authentication report message can be the same as that of the message shown in Figure 11 In the case where multiple APs and a management device form an Ethernet architecture, in step 803, the format of the authentication report message can be the same as that of the Ethernet frame shown in Figure 12 In the case where multiple APs and a management device form a PON architecture, in step 803, the format of the authentication report message can be the same as that of the OMCI message shown in Figure 13 the same.

[0155] It should also be noted that in the process shown in Figure 8 the management device sends the target AID and the identifier of the STA to the second AP. In step 808, it can also be that after the first AP associates with the STA, the first AP sends the target AID and the identifier of the STA to the second AP. In addition, when the management device or the first AP sends the target AID and the identifier of the STA to the second AP, it can also send the content negotiated when the first AP associates with the STA, such as the rate, channel, and QoS capabilities supported by the STA, as well as the selected access authentication and encryption algorithms. In this way, after the STA roams into the coverage area of the second AP, the second AP can directly communicate with the STA and provide the function of forwarding packets for the STA.

[0156] In the embodiments of the present application, after the STA moves, the AP that provides forwarding processing for the packets of the STA can also be adjusted. The processing process is as follows:

[0157] After the STA associates with the first AP through the process shown in Figure 8 the first AP is responsible for forwarding the packets of the STA (the packets of the STA include the packets sent to the STA and the packets received from the STA), and it is considered that the STA is currently within the coverage area of the first AP. The STA may move, so that it moves from within the coverage area of the first AP to within the coverage area of the second AP among multiple APs. For example, a company where a user is located includes multiple office areas, and the user moves from one office area to another office area, and the user's STA may also move from within the coverage area of the first AP to within the coverage area of the second AP. Refer to Figure 14 . The management device can send a notification message to the second AP. To distinguish it from the notification message in the following text, this notification message is called the first notification message, and this first notification message instructs the second AP to connect to the STA. After receiving this first notification message, when the second AP subsequently receives the packets of this STA, it is responsible for forwarding processing. Here, the second AP already stores the identifier of the STA and the target AID, so the second AP can distinguish the STA based on the AID.

[0158] Optionally, the management device may send a second notification message to the first AP, and the second notification message indicates that the first AP no longer forwards the packets of the STA. In this way, when the coverage areas of the first AP and the second AP overlap, only one AP is responsible for forwarding the packets of the STA at the same time.

[0159] Exemplarily, the first notification message and the second notification message may further carry the same time indication identifier, and the time indication identifier indicates that the first AP no longer forwards the packets of the STA after this time, and indicates that the second AP starts to forward the packets of the STA after this time.

[0160] Exemplarily, the process for the management device to determine that the STA enters the coverage area of the second AP is as follows:

[0161] Each time an AP receives a packet sent by the STA, it records the signal strength of the received packet, sends the signal strength and the identifier of the STA to the management device, or sends the signal strength and the target AID to the management device. After the management device receives the signal strength and the target AID, the signal strength of the packet sent by the STA received by the first AP is the first strength, and the signal strength of the packet sent by the STA received by the second AP is the second strength. If the first strength is lower than the second strength, it is determined that the STA roams from the coverage area of the first AP to the coverage area of the second AP. Here, the AP can also periodically obtain the signal strength of the received packet sent by the STA and send it to the management device.

[0162] Optionally, if the first strength is continuously lower than the second strength within a period of time, it is determined that the STA roams from the coverage area of the first AP to the coverage area of the second AP.

[0163] It should be noted that the first notification message may carry the identifier of the STA and the identifier indicating the forwarded packet, and the second notification message may carry the identifier of the STA and the identifier indicating the stop of forwarding the packet.

[0164] It should also be noted that when the STA sends a packet, any AP covering the STA may receive the packet. However, since the management device only designates one AP to connect to the STA at a certain moment, there will be no situation where multiple APs process the packets of the STA at the same time. In addition, since the MAC addresses of multiple APs are the same, from the perspective of the STA, the STA believes that it is always connected to a wireless network.

[0165] In the embodiments of the present application, in order to enable more STAs to access the wireless network, after the STA goes offline from the wireless network, the AID allocated to the STA is recycled, and the recycled AID can be allocated to other APs waiting to access the wireless network. For the recycling process, refer to Figure 15 Steps 1501 to 1505.

[0166] Step 1501, the management device detects that the STA is offline.

[0167] In this embodiment, there are multiple ways for the management device to detect that the STA is offline. Here are two feasible ways provided:

[0168] Way 1: Each time the AP receives a message sent by the STA, it records the signal strength of the received message and sends the signal strength and the identifier of the STA to the management device, or sends the signal strength and the target AID to the management device. If the management device does not receive the signal strength of the message received from the STA within the first duration, it determines that the STA is offline. The first duration can be set according to actual needs.

[0169] Way 2: The AP associated with the STA detects that the STA is offline, and the AP sends a message indicating that the STA is offline to the management device. After receiving this message, the management device determines that the STA is offline. Exemplarily, the way for the AP to detect that the STA is offline is as follows: The AP actively determines that the STA is offline. For example, after the STA has associated with the AP, the administrator enters an access blacklist in the AP. If the STA is in this blacklist, the AP determines that the STA is offline. Another example is that the AP associated with the STA periodically sends management frames to the STA. If the STA does not respond within the target number of cycles or the second duration, it is determined that the STA is offline. The target number and the second duration can be set according to actual needs.

[0170] Alternatively, in some cases, the STA sends an offline message to the AP, and the AP determines that the STA is offline. For example, when the STA switches the wireless network, the STA sends an offline message to the AP, and the AP determines that the STA is offline.

[0171] Way 1 and Way 2 are only two optional ways, and the embodiments of the present application do not limit this.

[0172] Step 1502, the management device sends a recycling message to the first AP respectively. The recycling message is used to indicate the recycling target AID.

[0173] In this embodiment, after the management device determines that the STA is offline, it generates a recycling message, which includes the identifier of the STA or the target AID. The management device sends the recycling message to multiple allocations.

[0174] Exemplarily, the recovery message includes an AID recovery field, where the AID recovery field includes an AID field, or the AID recovery field includes an AID field and an STA identification field. Alternatively, the AID recovery field includes an AID field, an STA identification field, and a message identifier field. The AID field is used to store the target AID, and the message identifier is used to indicate whether the message is a recovery message or an allocation message. When the value of the message identifier is 1, the message is an allocation message, and when the value of the message identifier is 0, the message is a recovery message. For example, see Figure 16 the AID recovery field shown, as well as the AID allocation field.

[0175] Exemplarily, in different network architectures, the format of the recovery message carrying the AID recovery field may be different. For example, multiple APs and a management device form an FTTR network architecture, and the management device is connected to multiple APs via optical fibers or wireless connections respectively. See Figure 17 the recovery message shown. The recovery message includes an AID recovery field, a destination address field, a source address field, a message type field, a payload length field, and a payload field. For the recovery message sent to any AP, the destination address is the identifier of that AP, and the identifier of the AP uniquely indicates that AP, and different APs have different identifiers. The source address is the identifier of the management device, and the identifier of the management device can be the MAC address of the management device or an index identifier that uniquely identifies the management device. The message type field identifies that the recovery message is a control message.

[0176] Optionally, the recovery message further includes a reserved field.

[0177] For another example, multiple APs and a management device form an Ethernet architecture, and the management device is connected to multiple APs via optical fibers or cables respectively. The format of the recovery message carrying the AID recovery field is an Ethernet frame, and the AID recovery field is located in the payload field of the Ethernet frame. See the source address and destination address of the Ethernet frame shown in Figure 12

[0178] For another example, multiple APs and a management device form a PON architecture, and the management device is connected to multiple APs via an ODN. The format of the recovery message carrying the AID recovery field is the format of an OMCI message, and the AID recovery field is located in the message content field of the OMCI message. Here, see the structure of the OMCI message in Figure 13 .

[0179] Step 1503, multiple APs respectively receive the recovery message sent by the management device.

[0180] Step 1504, multiple APs respectively recover the target AID.

[0181] ​In this embodiment, after each of the multiple APs receives the recycling message, it deletes the target AID. For example, the first AP among the multiple APs deletes the correspondence between the target AID and the identifier of the STA.

[0182] Step 1505, the multiple APs respectively send a recycling completion message to the management device.

[0183] In this embodiment, after the AP deletes the target AID, there is no correspondence between the identifier of the STA and the target AID. After the management device receives the recycling completion message sent by each of the multiple APs, the management device can allocate the target AID to another STA to be connected. In this way, after the STA goes offline, the target AID can still be provided for other STAs to use, improving the utilization rate of the AID.

[0184] Optionally, after the target AID is recycled, the management device sets the flag position of the target AID to 1, indicating that the target AID can be allocated to other STAs.

[0185] It should be noted that in Figure 15 only the process of the management device sending a recycling message to the first AP is shown. For the processing of the management device sending a recycling message to other APs, refer to Figure 15 .

[0186] In another implementation, the management device only sends the AID and the identifier of the STA to the first AP. The management device can only send a recycling message to the first AP, so that the first AP deletes the AID.

[0187] In another implementation, the management device sends the AID and the identifier of the STA to all the multiple APs it manages. The management device can send a recycling message to the first AP, so that the first AP deletes the AID, and the first AP sends a recycling message to other APs except the first AP among the multiple APs, so that the other APs delete the AID.

[0188] In the embodiment of the present application, a process for the management device to detect the status of the AP is also provided. The processing is as follows: A heartbeat connection is established between the management device and each AP. The management device periodically sends a heartbeat message to the AP. If the management device does not receive a heartbeat reply message sent by a certain AP within a consecutive target number of cycles, it is determined that the AP has a fault, and a prompt message can be sent to the device of the management personnel, so that the management personnel can timely troubleshoot the fault of the AP. Here, the target number can be set according to actual needs.

[0189] In an embodiment of the present application, in a network architecture identified by a BSSID, a management device uniformly assigns AIDs, such that different STAs accessing the network architecture correspond to different AIDs, so that messages carrying AIDs between multiple APs and STAs will not be confused. Moreover, since one AID uniquely corresponds to one STA, the AID can be used to identify the STA instead of the MAC address, saving byte overhead. For example, the MAC address is 6 bytes, while using the AID can reduce it to 1 byte or 2 bytes.

[0190] The following introduces the device provided in the embodiment of the present application.

[0191] Figure 18 It is a structural diagram of the device for allocating AIDs provided in the embodiment of the present application. This device can be implemented as part or all of the device through software, hardware, or a combination of both. This device is applied to the management device. The device provided in the embodiment of the present application can implement the Figure 6 process described above. This device includes: an acquisition module 1810, a determination module 1820, and a sending module 1830:

[0192] The acquisition module 1810 is configured to acquire parameters of the STA, and specifically can be used to implement the acquisition function of step 601 and execute the implicit steps included in step 601;

[0193] The determination module 1820 is configured to allocate an AID to the STA based on the parameters of the STA, and determine a first AP among multiple APs managed by the management device. The first AP is used to send the AID to the STA. The BSSIDs of the multiple APs are the same, and at least one of the multiple APs receives an authentication request sent by the STA. The first AP belongs to the at least one AP. Specifically, it can be used to implement the determination function of step 602 and execute the implicit steps included in step 602;

[0194] The sending module 1830 is configured to send the AID and the identifier of the STA to the first AP. Specifically, it can be used to implement the sending function of step 603 and execute the implicit steps included in step 603.

[0195] In a possible implementation manner, the sending module 1830 is further configured to:

[0196] Send the AID and the identifier of the STA to other APs among the multiple APs except the first AP.

[0197] In a possible implementation manner, the determination module 1820 is further configured to detect that the STA is offline;

[0198] The sending module 1830 is further configured to send a recycling message to each of the multiple APs, where the recycling message is used to indicate recycling of the AID.

[0199] In a possible implementation, the multiple APs and the management device form a Fiber to the Room (FTTR) network architecture. The management device carries the AID and the identifier of the STA in an allocation message, where the AID and the identifier of the STA are located in the payload field of the allocation message, and the destination address of the allocation message is the identifier of the AP that receives the allocation message.

[0200] In a possible implementation, the multiple APs and the management device form an Ethernet architecture. The management device carries the AID and the identifier of the STA in an Ethernet frame, where the AID and the identifier of the STA are located in the payload field of the Ethernet frame.

[0201] In a possible implementation, the multiple APs and the management device form a Passive Optical Network (PON) architecture. The management device carries the AID and the identifier of the STA in an OMCI message, where the AID and the identifier of the STA are located in the message content field of the OMCI message.

[0202] In a possible implementation, the obtaining module 1810 is configured to:

[0203] Receive an authentication report message sent by at least one of the multiple APs, where the authentication report message includes parameters of the STA;

[0204] Obtain the parameters of the STA from the authentication report message.

[0205] In a possible implementation, the obtaining module 1810 is further configured to obtain feature information of the at least one AP, where the feature information of each AP includes at least one of load information, interference information received, and signal quality information of receiving a signal sent by the STA;

[0206] The determining module 1820 is configured to determine the connection quality between each of the at least one AP and the STA based on the feature information of the at least one AP, and determine the AP with the highest connection quality among the at least one AP as the first AP.

[0207] In a possible implementation, the determining module 1820 is further configured to detect that the STA moves from the coverage range of the first AP to the coverage range of a second AP among the multiple APs;

[0208] The sending module 1830 is further configured to send a notification message to the second AP, where the notification message is used to instruct the second AP to connect to the STA.

[0209] Figure 19 It is a structural diagram of a device for allocating AID provided by an embodiment of the present application. This device can be implemented as a part or all of the device through software, hardware, or a combination of both. This device is applied to the first AP. The device provided by the embodiment of the present application can implement some processing in the Figure 7 process described in the embodiment of the present application. The device includes: a receiving module 1910 and a processing module 1920:

[0210] The receiving module 1910 is configured to receive the AID and the identifier of the STA sent by the management device. The AID is the AID allocated by the management device for the STA, and specifically can be used to implement the receiving function of step 701 and execute the implicit steps included in step 701;

[0211] The processing module 1920 is configured to store the identifier of the STA and the AID in a corresponding manner, and specifically can be used to implement the processing function of step 702 and execute the implicit steps included in step 702.

[0212] In a possible implementation manner, the device further includes: a sending module, configured to send the AID to the STA when the first AP is the AP associated with the STA designated by the management device.

[0213] In a possible implementation manner, before the receiving module 1910 receives the AID and the identifier of the STA sent by the management device, it is further configured to receive an authentication request sent by the STA, where the authentication request includes the parameters of the STA;

[0214] The device further includes: a sending module, configured to send an authentication report message to the management device, where the authentication report message includes the parameters of the STA;

[0215] After receiving the AID and the identifier of the STA sent by the management device, when the first AP is the AP associated with the STA designated by the management device, send an authentication response message to the STA.

[0216] In a possible implementation manner, the receiving module 1910 is further configured to receive a recycling message sent by the management device, where the recycling message is used to indicate recycling the AID;

[0217] The processing module 1920 is further configured to recycle the AID.

[0218] Figure 18 andFigure 19 For the detailed process of the device for allocating AID shown, please refer to the descriptions in the previous embodiments, and no repeated description will be given here. Figure 18 The device for allocating AID shown is attached Figure 3 to the management device 302 in Figure 19 The device for allocating AID shown is attached Figure 3 to the AP 301 in

[0219] In some embodiments, a computer program product is provided, which includes computer instructions stored in a computer-readable storage medium. The processor of the management device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, causing the management device to execute Figure 6 the process shown.

[0220] In some embodiments, a computer program product is provided, which includes computer instructions stored in a computer-readable storage medium. The processor of the first AP reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, causing the first AP to execute Figure 7 the partial process shown.

[0221] Those of ordinary skill in the art can realize that, in combination with the method steps and units described in the embodiments disclosed in this application, they can be implemented by electronic hardware, computer software, or a combination of the two. To clearly illustrate the interchangeability of hardware and software, the steps and components of the embodiments have been generally described according to functions in the above description. Whether these functions are executed in a hardware or software manner depends on the specific application and design constraints of the technical solution. Those of ordinary skill in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of this application.

[0222] In the several embodiments provided in this application, it should be understood that the disclosed system architecture, device, and method can be implemented in other ways. For example, the device embodiments described above are merely illustrative. For example, the division of the modules is only a logical function division, and there can be other division methods in actual implementation. For example, multiple modules or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the displayed or discussed couplings or direct couplings or communication connections to each other can be indirect couplings or communication connections through some interfaces, devices, or modules, and can also be electrical, mechanical, or other forms of connection.

[0223] The module described as a separate component may or may not be physically separated. The component shown as a module may or may not be a physical module, that is, it may be located in one place or distributed across multiple network modules. Some or all of the modules can be selected according to actual needs to achieve the purpose of the solution of the embodiments of the present application.

[0224] In addition, in each embodiment of the present application, the modules can be integrated into one processing module, or each module can exist physically alone, or two or more modules can be integrated into one module. The above-mentioned integrated modules can be implemented in the form of hardware or in the form of software modules.

[0225] If the integrated module is implemented in the form of a software functional module and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, in essence, or the part that contributes to the prior art, or all or part of the technical solution can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several instructions for causing a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods in the various embodiments of the present application. The aforementioned storage medium includes: various media such as USB flash drives, mobile hard disks, ROM, RAM, magnetic disks, or optical discs that can store program codes.

[0226] In the present application, terms such as "first" and "second" are used to distinguish the same items or similar items with basically the same functions and effects. It should be understood that there is no logical or temporal dependence between "first" and "second", nor are the quantity and execution order limited. It should also be understood that although the following description uses the terms first and second to describe various elements, these elements should not be limited by the terms. These terms are only used to distinguish one element from another. For example, without departing from the scope of the various examples, the first AP can be called the second AP, and similarly, the second AP can be called the first AP. Both the first AP and the second AP can be APs, and in some cases, they can be separate and different APs.

[0227] In the present application, the meaning of the term "at least one" refers to one or more, and the meaning of the term "multiple" refers to two or more.

[0228] The above description is only a specific implementation manner of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art within the technical scope disclosed by the present application can easily think of various equivalent modifications or substitutions, and these modifications or substitutions should be covered within the protection 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 allocating an associated identifier AID, characterized in that, The method includes: The management device receives an authentication report message of a station sent by at least one access point among a plurality of access points; The management device assigns an AID to the station and determines a first access point among the plurality of access points managed by the management device; The management device sends the AID and the identifier of the station to the first access point.

2. The method according to claim 1, characterized in that, The method further includes: The management device sends the AID and the identifier of the station to other access points among the plurality of access points except the first access point.

3. The method according to claim 2, wherein The method further includes: After the management device detects that the station is offline, it reclaims the AID.

4. The method according to claim 1, wherein The plurality of access points and the management device form a Fiber to the Room (FTTR) network architecture.

5. The method according to any one of claims 1 to 4, characterized in that The plurality of access points are connected to the management device through optical fibers.

6. The method according to any one of claims 1 to 4, characterized in that, The authentication report message is sent by at least one access point among the plurality of access points in response to receiving an authentication request sent by the station.

7. The method according to any one of claims 1 to 4, characterized in that The assigning the AID to the station includes: The management device assigns the AID to the station based on the parameters of the station.

8. The method according to claim 7, wherein It further includes: The management device obtains the parameters of the station from the authentication report message.

9. The method according to any one of claims 1 to 4, characterized in that The method further includes: The management device obtains the characteristic information of the at least one access point, and the characteristic information of each access point includes at least one of load information, interference information received, and signal quality information for receiving a signal sent by the station; The determining a first access point among the plurality of access points managed by the management device includes: The management device determines the connection quality between the at least one access point and the station based on the characteristic information of the at least one access point, and determines the access point with the highest connection quality among the at least one access point as the first access point.

10. The method according to any one of claims 1 to 4, characterized in that, The method further includes: The management device detects that the station moves from the coverage range of the first access point to the coverage range of a second access point among the plurality of access points; The management device sends a notification message to the second access point, and the notification message is used to instruct the second access point to connect to the station.

11. The method according to any one of claims 1 to 4, characterized in that, The Basic Service Set Identifiers (BSSIDs) of the plurality of access points are the same.

12. A method for allocating an associated identifier AID, characterized in that, The method includes: The first access point receives an authentication request sent by the station and sends an authentication report message to the management device in response to the authentication request; The first access point receives the AID and the identifier of the station sent by the management device, and the AID is the AID assigned by the management device to the station.

13. The method according to claim 12, wherein The method further includes: When the first access point is the access point associated with the station designated by the management device, the first access point sends the AID to the station.

14. The method according to claim 12 or 13, characterized in that, The authentication request includes the parameters of the station, and the authentication report message includes the parameters of the station.

15. The method according to claim 12, wherein After the first access point receives the AID and the identifier of the station sent by the management device, it further includes: When the first access point is the access point associated with the station designated by the management device, the first access point sends an authentication response message to the station.

16. The method according to claim 13, characterized in that, The first access point sending the AID to the station includes: The first access point sends an association response message to the station, and the association response message includes the AID.

17. A management device, characterized in that, The management device is used to implement the method for allocating the AID provided in any one of claims 1-11 above.

18. An access point, characterized in that, The management device is used to implement the method for allocating the AID provided in any one of claims 12-16 above.

19. A network system, characterized in that, The system includes a management device and an access point; The management device is used to execute the method described in any one of claims 1 to 11; The access point is used to execute the method described in any one of claims 12 to 16.

Images