Communication methods and devices

Abstract

A communication method and apparatus applicable to the field of communication technology are provided, which may be applicable to wireless local area network systems that support 802.11 series protocols, such as the next-generation Wi-Fi protocol of IEEE 802.11ax, e.g., 802.11be, Wi-Fi 7, or EHT, and the next-generation protocols of 802.11be, Wi-Fi 8, UHR, or Wi-Fi AI. Furthermore, it may also be applicable to UWB-supported WPAN systems, sensing systems, etc. After generating a first communication frame, the current AP or target AP transmits the first communication frame, and the non-AP STA receives and parses the first communication frame. The first communication frame contains first instruction information, which indicates whether the non-AP STA should initiate an IP address assignment request when the non-AP STA is handed over from the current AP to the target AP. This method can effectively reduce the roaming handover time of the non-AP STA.

Description

Technical Field

[0001] This application claims priority to Chinese Patent Application No. 202310443022.4, titled "Communication Method and Device", filed with the China National Intellectual Property Administration on April 21, 2023, the entire content of which is incorporated herein by reference.

[0002] This application relates to the field of communication technologies, and in particular, to communication methods and devices.

Background Art

[0003] Currently, there is a roaming handover scenario. For example, when a non-access point station (non-AP STA) is handed over from one access point (AP) to another AP, and both the non-AP STA and the other AP support the fast initial link setup (FILS) protocol, the non-AP STA uses a re-association request frame and a re-association response frame to IP be assigned an (internet protocol, IP) address. The re-association request frame and the re-association response frame each contain a FILS IP address assignment element.

[0004] If at least one of the non-AP STA and the other AP does not support the FILS protocol, the non-AP STA needs to initiate a separate IP address assignment request. For example, the non-AP STA performs dynamic host configuration protocol (DHCP) negotiation. In this mode, the roaming handover time of the non-AP STA may further increase.

Summary of the Invention

[0005] The embodiments of this application provide a communication method and apparatus for reducing the roaming handover time of a non-AP STA by preventing it from initiating unnecessary IP address allocation requests.

[0006] According to a first aspect, the embodiment of the present application provides a communication method. The method is applied to a first communication device. The method is: Steps include: generating a first communication frame, the first communication frame containing first instruction information, the first instruction information indicating whether the non-AP STA should initiate an Internet Protocol IP address assignment request when the non-AP STA is being handed over from the current access point AP to the target AP; and The steps include: sending a first communication frame;

[0007] In this embodiment of the present application, the first communication device may be the current AP or the target AP, and the first communication device explicitly indicates, via first instruction information, whether a non-AP STA needs to initiate an IP address assignment request, so that the non-AP STA can explicitly know, based on the first instruction information, whether a non-AP STA needs to initiate an IP address assignment request. Thus, the non-AP STA can be effectively prevented from initiating unnecessary IP address assignment requests (also known as IP address negotiations). This improves the need for non-AP STAs to restart IP address assignment requests, reduces roaming handover times for non-AP STAs, and reduces service interruption times caused by roaming of non-AP STAs.

[0008] According to a second aspect, the embodiment of the present application provides a communication method. The method is applied to a second communication device. The method is: Steps include: receiving a first communication frame, the first communication frame containing first instruction information, the first instruction information indicating whether the non-AP STA should initiate an Internet Protocol IP address assignment request when the non-AP STA is being handed over from the current access point AP to the target AP; and The process includes the step of analyzing a first communication frame.

[0009] In this embodiment of the present application, the second communication device may be a non-AP STA. The need for the non-AP STA to initiate an IP address assignment request is improved when the first instruction information indicates that the non-AP STA needs to initiate an IP address assignment request. For example, when the first instruction information indicates that the non-AP STA does not need to initiate an IP address assignment request, the method provided in this embodiment of the present application can effectively reduce the roaming handover time of the non-AP STA, reduce service interruption time, and effectively reduce unnecessary signaling overhead, such as the signaling overhead caused by the resumption of an IP address assignment request by the non-AP STA.

[0010] With respect to the second aspect, in possible implementations, the method further: The process includes the step of sending a second communication frame, the second communication frame containing second instruction information, the second instruction information indicating whether the non-AP STA initiates an IP address allocation request.

[0011] In this embodiment of the present application, a non-AP STA can indicate to the current AP via second instruction information whether the non-AP STA initiates an IP address assignment request based on the first instruction information. Thus, the current AP can know in advance the specific behavior of the non-AP STA, thereby improving the efficiency of communication between the two communicating parties.

[0012] With respect to the second aspect, in possible implementations, the method further: A step to remove the source IP address that was used by the non-AP STA for data transmission when the non-AP STA initiates an IP address assignment request based on the first instruction information; or The steps include: using the source IP address for data transmission if the non-AP STA does not initiate an IP address assignment request based on the first instruction information;

[0013] In the first or second embodiment, in a possible implementation, the first instruction information is included in the neighbor report element of the first communication frame.

[0014] In the first or second embodiment, in a possible implementation, the first instruction information is included in the First Initial Link Setup FILS IP Address Assignment element of the first communication frame.

[0015] In the first or second embodiment, in a possible implementation, the FILS IP address assignment element includes an IP address response control field, wherein the first instruction information is contained in the first or eighth bit of the IP address response control field.

[0016] According to a third aspect, embodiments of the present application provide a communication device configured to perform the method of the first aspect, the second aspect, or any possible implementation. The communication device includes a unit that performs the method of the first aspect, the second aspect, or any possible implementation.

[0017] For example, a communication device could be a WLAN device or a chip, and a chip could be used in a WLAN device.

[0018] According to a fourth aspect, an embodiment of the present application provides a communication device. The communication device includes a processor configured to perform the method of the first aspect, the second aspect, or any possible implementation. Alternatively, the processor is configured to execute a program stored in memory. Once the program is executed, the method of the first aspect, the second aspect, or any possible implementation is performed.

[0019] In possible implementations, memory is located outside the communication device.

[0020] In possible implementations, memory is located inside the communication device.

[0021] In this embodiment of the present application, the processor and memory may, alternatively, be integrated into a single device. In other words, the processor and memory may, alternatively, be integrated together. For example, the communication device may be a chip.

[0022] In possible implementations, the communication device further includes a transceiver, which is configured to receive or transmit signals.

[0023] According to a fifth aspect, an embodiment of the present application provides a communication device. The communication device comprises a logic circuit and an interface. The logic circuit is coupled to the interface. The interface is configured to input and / or output control information. The logic circuit is configured to perform the method of the first aspect, the second aspect, or any possible implementation.

[0024] According to the sixth aspect, an embodiment of the present application provides a computer-readable storage medium. The computer-readable storage medium is configured to store a computer program, and when the computer program is executed on a computer, the computer is able to perform the methods of the first aspect, the second aspect, or any possible implementation.

[0025] According to a seventh aspect, an embodiment of the present application provides a computer program product. The computer program product includes a computer program or computer code, and when the computer program or computer code is executed on a computer, the method according to the first aspect, the second aspect, or any possible implementation is executed.

[0026] According to an eighth aspect, an embodiment of the present application provides a computer program. When the computer program is executed on a computer, the method according to the first aspect, the second aspect, or any possible implementation is executed.

[0027] According to a ninth aspect, an embodiment of the present application provides a communication system. The wireless communication system includes a first communication device and a second communication device. The first communication device is configured to execute the method according to the first aspect or any possible implementation of the first aspect, and the second communication device is configured to execute the method according to the second aspect or any possible implementation of the second aspect.

Brief Description of the Drawings

[0028] [Figure 1a] FIG. 1a and FIG. 1b are diagrams of the architecture of a communication system according to an embodiment of the present application, respectively. [Figure 1b] FIG. 1a and FIG. 1b are diagrams of the architecture of a communication system according to an embodiment of the present application, respectively.

[0029] [Figure 2a] FIG. 2a and FIG. 2b are diagrams of communication between a multi-link device and another device according to an embodiment of the present application, respectively. [Figure 2b] FIG. 2a and FIG. 2b are diagrams of communication between a multi-link device and another device according to an embodiment of the present application, respectively.

[0030] [Figure 3a]Figures 3a and 3b are diagrams of roaming scenarios according to embodiments of the present application, respectively. [Figure 3b] Figures 3a and 3b are diagrams of roaming scenarios according to embodiments of the present application, respectively.

[0031] [Figure 4] Figure 4 is a schematic flowchart of the AP-start BSS transition according to the embodiment of this application.

[0032] [Figure 5] Figure 5 is a schematic flowchart of DHCP negotiation according to the embodiment of the present application.

[0033] [Figure 6] Figure 6 is a schematic flowchart of the communication method according to the embodiment of the present application.

[0034] [Figure 7a] Figure 7a is a diagram illustrating the format of the neighbor report element in the BSS transition candidate list according to an embodiment of the present application.

[0035] [Figure 7b] Figure 7b is a schematic flowchart of the BTM according to the embodiment of the present application.

[0036] [Figure 7c] Figure 7c is a diagram showing the format of the BTM request frame according to the embodiment of the present application.

[0037] [Figure 7d] Figure 7d is a diagram illustrating the format of a BTM query frame according to an embodiment of the present application.

[0038] [Figure 7e] Figure 7e is a diagram showing the format of the BTM response frame according to the embodiment of the present application.

[0039] [Figure 8a] Figures 8a and 8b are diagrams showing the format of the FILS IP address assignment element according to the embodiment of this application, respectively. [Figure 8b] Figures 8a and 8b are diagrams showing the format of the FILS IP address assignment element according to the embodiment of this application, respectively.

[0040] [Figure 8c] Figure 8c is a schematic flowchart of the reassociation according to the embodiment of the present application.

[0041] [Figure 9] Figures 9 to 11 are diagrams illustrating the structure of a communication device according to an embodiment of the present application. [Figure 10] Figures 9 to 11 are diagrams illustrating the structure of a communication device according to an embodiment of the present application. [Figure 11] Figures 9 to 11 are diagrams illustrating the structure of a communication device according to an embodiment of the present application. [Modes for carrying out the invention]

[0042] To facilitate understanding of the technical solution presented in this application, the application will be further described below with reference to the attached drawings.

[0043] The terms “first,” “second,” and similar terms in the specification, claims, and accompanying drawings of this application are used solely to distinguish different subjects and not to describe a particular order. Furthermore, terms such as “includes” and “has,” and any other variations thereof, are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or device comprising a series of steps or units is not limited to the listed steps or units, but rather optionally includes further steps or units not listed, or optionally includes other steps or units specific to these processes, methods, products, or devices.

[0044] The “embodiments” as used in this specification indicate that certain features, structures, or characteristics described in combination in an embodiment may be included in at least one embodiment of this application. Words used in various parts of the specification do not necessarily mean the same embodiment, nor do they necessarily refer to an exclusive, independent, or alternative embodiment to another embodiment. It will be explicitly and implicitly understood by those skilled in the art that the embodiments described herein may be combined with other embodiments.

[0045] In this application, “at least one (item)” means one or more, “multiple” means two or more, “at least two (items)” means two, three or more, and “and / or” is used to describe the relationship of association between related objects and indicates that three relationships may exist. For example, “A and / or B” could indicate that only A exists, only B exists, and both A and B exist. A and B can be singular or plural. “Or” indicates that two relationships may exist, for example, only A exists and also only B exists. If A and B are not mutually exclusive, it could indicate that three relationships exist, for example, only A exists, only B exists, and both A and B exist. The character “ / ” generally indicates an “or” relationship between related objects. “At least one of the following” or similar expressions mean any combination of these items. For example, at least one of a, b, or c may represent: a, b, c, "a and b", "a and c", "b and c", or "a, b and c".

[0046] The technical solutions provided in embodiments of this application may be applied to WLAN systems, such as Wi-Fi. For example, the methods provided in embodiments of this application are applicable to IEEE 802.11 series protocols, such as 802.11a / b / g protocols, 802.11n protocols, 802.11ac protocols, 802.11ax protocols, 802.11be protocols, or next-generation protocols. Examples are not exhaustively listed. The technical solutions provided in embodiments of this application may further be applied to wireless personal area networks (WPANs) based on UWB technology. For example, the methods provided in embodiments of this application are applicable to IEEE 802.15 series protocols, such as 802.15.4a protocols, 802.15.4z protocols, 802.15.4ab protocols, or next-generation UWB WPAN protocols. Examples are not exhaustively listed. The technical solutions provided in the embodiments of this application may be further applied to the following communication systems, for example, Internet of Things (IoT) systems, Vehicle-to-X (V2X) systems, and Narrow Band Internet of Things (NB-IoT) systems; or to Vehicle-to-Everything devices, Internet of Things nodes, sensors and the like in the Internet of Things (IoT), smart cameras in smart homes, smart remote controls, and smart water or electricity meters, sensors and the like in smart cities; or further to Long Term Evolution (LTE) systems, 5th Generation (5G) communication systems, new communication systems emerging in future communication developments and the like.

[0047] WLAN systems can provide high-rate and low-latency transmission. With the continuous evolution of WLAN application scenarios, WLAN systems are applicable to a wider range of scenarios and industries, such as the Internet of Things industry, vehicle-to-everything industry, banking industry, corporate offices, stadiums and exhibition halls, concert halls, hotel rooms, dormitories, hospital rooms, classrooms, shopping malls and supermarkets, squares, streets, production plants, and warehouses. Indeed, devices that support WLAN communication or sensing (e.g., access points or stations) could be sensor nodes in a smart city (e.g., smart water meters, smart electricity meters, or smart air sensing nodes), smart devices in a smart home (e.g., smart cameras, projectors, displays, televisions, stereos, refrigerators, or washing machines), nodes in the Internet of Things, entertainment terminals (e.g., wearable devices such as augmented reality (AR) or virtual reality (VR) devices), smart devices in a smart office (e.g., printers, projectors, loudspeakers, or stereos), vehicle-to-everything devices in vehicle-to-everything, infrastructure in everyday life scenarios (e.g., vending machines, self-service navigation consoles in shopping malls or supermarkets, self-service cash register devices, or self-service ordering machines), devices in large-scale sports and music venues, or similar.

[0048] The embodiments of this application primarily use, as examples, networks applicable to WLANs, particularly the IEEE 802.11 series standards, such as systems supporting Wi-Fi 7, sometimes referred to as extremely high throughput (EHT) systems, or systems supporting Wi-Fi 8, sometimes referred to as ultra-high reliability (UHR) or ultra-high reliability and throughput (UHRT) systems. Those skilled in the art will readily understand that various aspects of the embodiments of this application may be extended to various standards or protocols, such as Bluetooth, high-performance radio LAN (HIPERLAN) (a wireless standard similar to the IEEE 802.11 standard, mainly used in Europe), and wide-area networks (WANs), or other networks that are known or to be developed in the future.

[0049] In possible implementations, the methods provided in the embodiments of this application may be applied to scenarios such as communication or sensing between access points (APs) and non-access point stations (non-AP STAs) in a WLAN.

[0050] For example, an access point is a device having wireless communication capabilities that supports communication or sensing by using the WLAN protocol and has the ability to communicate or sense with other devices in the WLAN network (e.g., non-AP STAs or other access points), and of course, it may further have the ability to communicate or sense with other devices. Alternatively, an access point is equivalent to a bridge connecting wired and wireless networks. The main function of an access point is to connect various wireless network clients together and then connect the wireless network to Ethernet. In a WLAN system, an access point is sometimes called an access point station (AP STA). A device having wireless communication capabilities may be an entire device, or a chip, processing system, functional module, or the like mounted on the entire device. A device to which a chip, processing system, or functional module is attached can implement the methods, functions, and the like in the embodiments of this application under the control of the chip, processing system, or functional module. The AP in the embodiments of this application is a device that provides services to a non-AP STA and is capable of supporting 802.11 series protocols, successor protocols, or similar protocols. For example, the access point may be an access point for terminals (e.g., mobile phones) to access a wired (or wireless) network and is mainly located in homes, buildings, and campuses. Typical coverage radii are tens of meters to just over 100 meters. Of course, the access point may alternatively be located outdoors. In another example, the AP may be a communications entity, such as a communications server, router, switch, or bridge; or the AP may include various forms of macro base stations, micro base stations, relay stations, and the like.

[0051] For example, a non-AP STA is a device having wireless communication capabilities that supports communication or sensing by using the WLAN protocol and has the ability to communicate or sense with another non-AP STA or access point within a WLAN network. For example, a non-AP STA is any user communication device that enables a user to communicate or sense with an AP and further communicate with the WLAN. A device having wireless communication capabilities may be an entire device, or a chip, processing system, functional module, or similar mounted on the entire device. A device to which a chip, processing system, or functional module is attached may implement the methods, functions, and similar in the embodiments of this application under the control of the chip, processing system, or functional module. For example, a non-AP STA may be a wireless communication chip, wireless sensor, wireless communication terminal, or similar, and may also be referred to as a user. For example, a non-AP STA may be a mobile phone, tablet computer, set-top box, smart TV, smart wearable device, in-vehicle communication device, and a computer that supports Wi-Fi communication capabilities.

[0052] Figure 1a is a diagram of the architecture of a communication system according to an embodiment of the present application. As shown in Figure 1a, the communication system may include one or more access points (APs) and one or more non-AP stas (STAs). Figure 1a shows two access points: AP1 and AP2, and two non-AP STAs: non-AP STA1 and non-AP STA2. It will be understood that one or more APs may communicate with one or more non-AP STAs. Of course, APs can also communicate with other APs, and non-AP STAs can also communicate with other non-AP STAs.

[0053] Figure 1a uses an example where the non-AP STA is a mobile phone and the AP is a router, and it will be understood that this does not mean that the types of APs and non-AP STAs in the embodiments of this application are limited. Also, Figure 1a shows an example where there are only two APs and two non-AP STAs. However, there may be more or fewer APs or non-AP STAs. This is not limited to the embodiments of this application.

[0054] In another possible implementation, the method provided in the embodiments of this application may be applied to scenarios of communication or sensing between multi-link devices (MLDs) within a WLAN, or equivalent.

[0055] A multi-link device (MLD) is a device having multiple stations (e.g., APs or non-AP STAs) operating on different frequency bands or channels. A multi-link device includes multiple affiliated stations. Affiliated stations may be physical or logical stations. Each station may operate on one link, one frequency band, one channel, or similar. Affiliated stations may be APs or non-AP STAs. For ease of explanation, in the embodiments of this application, A multi-link device whose affiliated station is an AP may be called a multi-link AP, multi-link AP device, or AP multi-link device (AP MLD). A multi-link device whose affiliated stations are non-AP STA may be called a multi-link STA, multi-link STA device, or STA multi-link device. A multi-link device whose affiliated stations are non-AP STAs is sometimes called a multi-link non-AP, multi-link non-AP device, or non-AP multi-link device (non-AP MLD). A multi-link device (which may be a non-AP MLD or AP MLD in this case) may be a communication device having wireless communication capabilities. The communication device may be the entire device, or it may be a chip, processing system, functional module, or similar implemented within the entire device. A device in which a chip, processing system, or functional module is implemented can carry out the methods and functions of the embodiments of this application under the control of the chip, processing system, or functional module.

[0056] A multi-link device can perform wireless communication with another device in accordance with the 802.11 series protocol, for example, in accordance with EHT, or in accordance with 802.11 be, or compatible with 802.11 be. Of course, the other device may or may not be a multi-link device. Multiple links, for example, link 1, link 2, and link n shown in Figure 1b, are established between one multi-link device and another multi-link device.

[0057] Figure 1b is a diagram of the architecture of a communication system according to an embodiment of the present application. As shown in Figure 1b, the AP MLD includes AP1, AP2, ..., and APn, and the non-AP MLD includes STA1, STA2, ..., and STAn. The AP MLD and non-AP MLD can perform parallel communication on links 1, 2, ..., and n. STA1 in the non-AP MLD establishes link 1 with AP1 in the AP MLD, STA2 in the non-AP MLD establishes link 2 with AP2 in the AP MLD, STAn in the non-AP MLD establishes a link with APn in the AP MLD, and so on. Therefore, the non-AP MLD and AP MLD can communicate with each other after establishing an association relationship. For example, the multi-link device in the embodiment of the present application may be a single-antenna device or a multi-antenna device. For example, the multi-link device may be a device having more than two antennas. The number of antennas included in the multi-link device is not limited to the embodiments of this application.

[0058] The frequency bands in which multi-link devices operate may include, but are not limited to, sub-1 GHz, 2.4 GHz, 5 GHz, 6 GHz, and high-frequency 60 GHz. Figures 2a and 2b are two diagrams illustrating communication between a multi-link device and another device in a wireless local area network over multiple links.

[0059] For example, Figure 2a shows a scenario in which AP MLD 101 communicates with non-AP MLD 102. AP MLD 101 includes affiliated AP 101-1 and affiliated AP 101-2. non-AP MLD 102 includes affiliated STA 102-1 and affiliated STA 102-2. AP MLD 101 and non-AP MLD 102 implement parallel communication through Link 1 and Link 2.

[0060] For example, Figure 2b shows a scenario in which AP MLD 101 communicates with non-AP MLD 102, non-AP MLD 103, and STA 104. AP MLD 101 includes affiliated AP 101-1 or affiliated AP 101-3. non-AP MLD 102 includes three affiliated stations: STA 102-1, STA 102-2, and STA 102-3. non-AP MLD 103 includes two affiliated stations: STA 103-1 and STA 103-2. STA 104 is a single-link device and includes STA 104-1. AP MLD 101 can communicate separately with non-AP MLD 102 on links 1, 2, and 3, with non-AP MLD 103 on links 2 and 3, and with STA 104 on link 1. For example, STA 104 operates on the 2.4GHz frequency band; with non-AP MLD 103, STA 103-1 operates on the 5GHz frequency band and STA 103-2 operates on the 6GHz frequency band; with non-AP MLD 102, STA 102-1 operates on the 2.4GHz frequency band, STA 102-2 operates on the 5GHz frequency band, and STA 102-3 operates on the 6GHz frequency band. AP 101-1, operating in the 2.4GHz frequency band with AP MLD 101, can communicate uplink or downlink data with STA 104 and STA 102-1 in non-AP MLD 102 on link 1. AP 101-2, operating in the 5GHz frequency band with AP MLD 101, can communicate uplink or downlink data on Link 2 with STA 103-1, operating in the 5GHz frequency band with non-AP MLD 103. It can also communicate uplink or downlink data on Link 2 with STA 102-2, operating in the 5GHz frequency band with non-AP MLD 102. AP 101-3, operating in the 6GHz frequency band with AP MLD 101, can communicate uplink or downlink data via link 3 to STA 102-3, operating in the 6GHz frequency band with non-AP MLD 102. It can also communicate uplink or downlink data via link 3 to STA 103-2 in the non-AP MLD.

[0061] Figure 2a simply shows that the AP MLD supports two frequency bands. Figure 2b simply shows an example in which the AP MLD 101 supports three frequency bands (2.4 GHz, 5 GHz, and 6 GHz), each frequency band corresponding to one link, and the AP MLD 101 may operate on one or more of Link 1, Link 2, or Link 3. In practice, AP MLDs and non-AP MLDs may support more or fewer frequency bands, i.e., AP MLDs and non-AP MLDs may operate on more or fewer links. This is not limited to the embodiments of this application. Figures 2a and 2b are merely simple diagrams and do not constitute any limitation on the scope of protection of the embodiments of this application. It will be understood that for descriptions of the 802.11 physical layer (PHY) and 802.11 medium access control (MAC) layers in multi-link devices, please refer to the relevant standards, protocols, or similar. Details are not comprehensively provided in the embodiments of this application.

[0062] In connection with the above-mentioned descriptions of AP, non-AP STA, AP MLD, and non-AP MLD, the roaming scenario in the embodiments of this application will be described below with reference to Figures 3a and 3b. It will be understood that Figure 3a is illustrated using a single-link device as an example, and Figure 3b is illustrated using a non-AP MLD as an example.

[0063] As shown in Figure 3a, in a roaming scenario, a non-AP STA may be handed over from AP1 to AP2. For example, AP1 may be understood as the AP currently associated with the non-AP STA, e.g., abbreviated as current AP, source AP, or old AP; and AP2 may be understood as the target AP to which the non-AP STA should be handed over (or the target AP to which the non-AP STA should be associated, the target AP that the non-AP STA is expected to access, etc.), e.g., abbreviated as target AP, destination AP, or new AP.

[0064] As shown in Figure 3b, in a roaming scenario, a non-AP MLD may be handed over from AP MLD1 to AP MLD2, that is, a non-AP MLD is handed over from the currently associated AP MLD1 (which may be called the current AP MLD) to the target AP MLD2 (which may be called the target AP MLD).

[0065] Regardless of whether it is a single-link non-AP STA shown in Figure 3a or a multi-link non-AP MLD shown in Figure 3b, an IP address must be assigned to the single-link non-AP STA or multi-link non-AP MLD before data transmission. In other words, all non-AP STAs within a non-AP MLD use the same IP address for data transmission.

[0066] For the sake of clarity, the following examples will use a non-AP STA, a current AP, and a target AP to illustrate the methods provided in the embodiments of this application. Specifically, the device types (e.g., single-link devices or multi-link devices) of the non-AP STA, the current AP, and the target AP are not distinguished in the following manner. In other words, the following non-AP STA may be a single-link non-AP STA or a non-AP STA in a non-AP MLD; and the current AP or target AP may be a single-link AP or an AP in an AP MLD.

[0067] It will be understood that the handover of a non-AP STA from the current AP to the target AP in this embodiment of the present application may be called a BSS transition, a non-AP STA roaming handover, or something similar. For example, before the handover, the non-AP STA may be communicating with the current AP, i.e., the non-AP STA has established an association relationship with the current AP. After the handover, the non-AP STA communicates with the target AP, i.e., the non-AP STA has established an association relationship with the target AP, or the non-AP STA no longer has an association relationship with the current AP, or is disconnected from the current AP.

[0068] Figure 4 is a schematic flowchart of the AP-initiated BSS transition according to the embodiment of the present application. As shown in Figure 4, the BSS transition procedure may include the following steps:

[0069] 401: The current AP sends a measurement request, and in response, a non-AP STA receives the measurement request.

[0070] For example, if the current AP detects that the signal strength (or signal quality) of a non-AP STA is below a threshold, it may send a measurement request. For example, the measurement type of the measurement request may be set to a beacon request. The measurement request may be used to ask the non-AP STA to perform channel sounding to collect nearby APs that can be detected around the non-AP STA.

[0071] 402: non-AP STA sends a probe request, and in response, the target AP receives the probe request.

[0072] 403: The target AP sends a probe response, and in response, the non-AP STA receives a probe response.

[0073] For example, after receiving a measurement request, a non-AP STA may jump to another channel, send a probe request, and receive a corresponding probe response. Alternatively, after receiving a measurement request, a non-AP STA can jump to another channel and monitor beacon frames.

[0074] It will be understood that Figure 4 is illustrated by using an example where a non-AP STA sends a probe request to a target AP. However, in reality, a non-AP STA can send probe requests to multiple neighboring APs, and these multiple neighboring APs include the target AP.

[0075] 404: non-AP STA sends a measurement response, and in response, the current AP receives the measurement response.

[0076] For example, after receiving relevant information about nearby APs, a non-AP STA may feed that information back to the current AP via a measurement response. The measurement response can instruct the current AP to perform a roaming determination. For example, the measurement response may contain relevant information about nearby APs, which may include at least one of the following: Basic Service Set identifier (BSS identifier, BSSID), operating class, channel number, received signal strength indicator (RSSI), or the beacon frame or probe response frame body of the corresponding nearby AP.

[0077] 405: The current AP sends a BSS transition management request (BTM request), and in response, the non-AP STA receives the BTM request.

[0078] For example, the current AP can advise the non-AP STA to hand over to a candidate nearby AP based on relevant information about surrounding APs collected by the non-AP STA. In other words, the current AP can recommend one or more candidate target APs, which may be called alternative target APs, etc. For example, a BSS migration management request may include relevant information about one or more candidate target APs.

[0079] For example, before step 405, the non-AP STA may send further BTM queries, to which the current AP will receive the BTM queries (not shown in Figure 4).

[0080] 406: non-AP STA sends a BSS transition management response (BTM response), and in response, the current AP receives the BSS transition management response.

[0081] For example, the BTM response may indicate that the non-AP STA is precisely handing over to the target AP, or it may indicate that the non-AP STA is rejecting the handover request for the current AP.

[0082] It will be understood that the method in Figure 4 is illustrated by using an example in which a non-AP STA performs a BSS transition based on a measurement request sent by the current AP. In another possible implementation, the non-AP STA may proactively perform a BSS transition if it does not receive a BTM request sent by the current AP. Alternatively, the method shown in Figure 4 may omit steps 401, 402, 405, and 406. Alternatively, after receiving a BTM request, the non-AP STA may omit sending a BTM response. In other words, the method in Figure 4 may include step 405 and omit step 406.

[0083] For example, if it is decided that a non-AP STA will be handed over to a target AP, the non-AP STA and the target AP must perform data transmission after the following negotiations: for example, authentication request and response (e.g., steps 407 and 408), reassociation request and response (e.g., steps 409 and 410), 801.1X authentication and key agreement (e.g., step 411), dynamic host configuration protocol (DHCP) negotiation (e.g., step 412), and add block acknowledgement (ADDBA) negotiation (e.g., step 413). The execution of the aforementioned negotiation processes may cause interruptions to the service transmission of the non-AP STA; that is, the execution time between steps 407 and 413 can be understood as service interruption time for the non-AP STA.

[0084] 407: non-AP STA sends an authentication request, and the target AP receives the authentication request accordingly.

[0085] 408: The target AP sends an authentication response, and the non-AP STA receives the authentication response accordingly.

[0086] 409: non-AP STA sends a reassociation request, and in response, the target AP receives the reassociation request.

[0087] 410: The target AP sends a reassociation response, and in response, the non-AP STA receives the reassociation response.

[0088] In existing solutions, a non-AP STA cannot determine whether an IP address assignment request needs to be initiated when the non-AP STA is handed over to the target AP. Therefore, the non-AP STA initiates the IP address assignment request by including a FILS IP address assignment element in the reassociation request frame. For example, if both the non-AP STA and the target AP support the Fast Initial Link Setup (FILS) protocol, the reassociation request and reassociation response can include a FILS IP address assignment element. The FILS IP address assignment element can be used to conduct the negotiation for IP address assignment by the non-AP STA. Thus, the non-AP STA does not need to additionally initiate a new IP address assignment request (i.e., DHCP negotiation as shown in Figure 4), and as a result, roaming interaction time can be reduced. If both the non-AP STA and the target AP support the FILS protocol, the FILS IP address assignment element included in the reassociation request can be used to request an IP address, and the FILS IP address assignment element included in the reassociation response will contain the assigned IP address. Alternatively, the non-AP STA can initiate a separate IP address assignment request. For the methods by which the non-AP STA initiates an IP address assignment request, see the explanation in step 412 or Figure 5.

[0089] 411: The non-AP STA performs authentication and key agreement with the target AP.

[0090] For example, when a fast transition (FT) protocol is used between a non-AP STA and a target AP, it is possible to reduce the key agreement time.

[0091] 412: The non-AP STA performs DHCP negotiation with the target AP.

[0092] For example, a non-AP STA can obtain an IP address through DHCP negotiation, and this IP address can be used for subsequent data transmission by the non-AP STA. It will be understood that DHCP negotiation is a negotiation between the non-AP STA and the DHCP server. However, in the process of the non-AP STA negotiating with the DHCP server, relevant information is transmitted via the target AP. Therefore, although the DHCP negotiation shown in Figure 4 uses a non-AP STA and a target AP as examples, this should not be interpreted as a limitation to the embodiments of this application.

[0093] Figure 5 shows an example of the DHCP negotiation procedure. The procedure shown in Figure 5 omits the process by which the target AP transfers information between the non-AP STA and the DHCP server. As shown in Figure 5, the DHCP negotiation procedure includes the following steps:

[0094] 501: non-AP STA sends a DHCP discovery packet, and in response, the DHCP server receives the DHCP discovery packet.

[0095] 502: The DHCP server sends a DHCP offer packet, and in response, the non-AP STA receives the DHCP offer packet.

[0096] For example, a DHCP offer packet contains information such as the lease-up time and the IP address assigned to the non-AP STA by the DHCP server. For a specific description of DHCP discovery packets and DHCP offer packets, please refer to the relevant standards or protocols. Details are not described in the embodiments of this application.

[0097] 503: non-AP STA sends a DHCP request, and in response, the DHCP server receives the DHCP request.

[0098] After receiving a DHCP offer packet, the non-AP STA can extract the IP address from the DHCP offer packet and then indicate to the DHCP server via a DHCP request that the non-AP STA has received the DHCP offer packet.

[0099] 504: The DHCP server sends a DHCP acknowledgment, and in response, the non-AP STA receives the DHCP acknowledgment.

[0100] For example, a DHCP acknowledgment indicates that the DHCP server has acknowledged that a DHCP request has been received. A DHCP acknowledgment is sometimes also called an acknowledgment (ACK).

[0101] It should be understood that the DHCP discovery packet described above may also be abbreviated as DHCP discovery, and the DHCP offer packet may also be abbreviated as DHCP offer. For specific DHCP negotiation methods, please refer to the relevant standards or protocols. Details are not described in the embodiments of this application.

[0102] 413: The non-AP STA performs ADDBA negotiation with the target AP.

[0103] For example, a non-AP STA can establish a block acknowledgment session to perform data transmission with a target AP. For a detailed explanation of steps 407 through 411 and step 413, please refer to the relevant standards, protocols, or similar. Details are not described in the embodiments of this application. It is possible to understand that the measurement request shown in Figure 4 may be called a measurement request frame, the measurement response may be called a measurement response frame, the probe request may be called a probe request frame, the probe response may be called a probe response frame, the BSS transition management request may be called a BSS transition management request frame, the BSS transition management response may be called a BSS transition management response frame, and so on. Examples are not exhaustively listed. In other words, each request shown in this embodiment of this application may be called a request frame, and each response may be called a response frame.

[0104] It will be understood that the BSS transition procedure shown in Figure 4 is merely an example. In practice, a non-AP STA may perform some of the steps in the BSS transition procedure (for example, steps 401, 402, 405, and 406 may not be performed), or some of the steps shown in Figure 4 may be replaced in other ways (for example, steps 407 and 408 may be replaced in other ways). The specific procedure of the BSS transition is not limited to the embodiments of this application.

[0105] As can be seen from the methods shown in Figures 4 and 5, when a non-AP STA is handed over from the current AP to the target AP, the non-AP STA needs to initiate an IP address assignment request again. For example, the target IP address (i.e., the IP address used for data transmission after the non-AP STA establishes association with the target AP) may be obtained through a reassociation request and reassociation response, or the target IP address may be obtained through DHCP negotiation. In other words, in existing solutions, as long as the non-AP STA is performing a BSS transition, the non-AP STA needs to initiate an IP address assignment request.

[0106] However, in practice, under certain conditions, non-AP STAs do not need to initiate an IP address allocation request again and can continue using the source IP address, avoiding the unnecessary and time-consuming initiation of an IP address allocation request. This significantly reduces roaming time and improves the user experience.

[0107] In view of this, embodiments of the present application provide a communication method and apparatus for effectively optimizing the IP address negotiation procedure, avoiding unnecessary IP address negotiation, shortening roaming handover time for non-AP STAs, and reducing service interruption time. For example, if the current AP and the target AP are in the same Layer 2 network, the IP addresses assigned by the same DHCP server are usually the same. Therefore, a non-AP STA does not need to acquire an IP address again when it is handed over from the current AP to the target AP. Thus, the current AP may send first instruction information to the non-AP STA to indicate that the non-AP STA does not need to initiate an IP address assignment request, thereby effectively shortening the roaming time for the non-AP STA and reducing service interruption time. It will be understood that the Layer 2 network shown in this embodiment of the present application may be understood as having a core layer and an access layer, but not an aggregation layer. For example, "Layer 2" and "Layer 3" may be understood as classifications based on logical topological structure, and may refer to the core layer, aggregation layer, and access layer instead of the data link layer and network layer in the International Organization for Standardization (ISO) 7-layer model. A Layer 2 network has only a core layer and an access layer, and no aggregation layer. A Layer 2 network can communicate via MAC addresses, but its networking capabilities are limited. A Layer 2 network may also be understood as a security domain, that is, the security of non-AP STA within the same Layer 2 network may be considered the same from a network perspective. The description of Layer 2 networks in this application is merely an example and should not be interpreted as a limitation on the embodiments of this application.

[0108] An IP address may be used to route and address a non-AP STA. Therefore, an IP address may be used to carry out data transmission between a non-AP STA and another device. This other device may include, but is not limited to, the current AP or the target AP. For ease of explanation, this embodiment of the present application illustrates the method provided in this embodiment of the present application using examples in which a non-AP STA performs data transmission with the current AP and a non-AP STA performs data transmission with the target AP. However, this should not be construed as a limitation to the embodiments of the present application. A source IP address can be understood as the IP address used by a non-AP STA to carry out data transmission when the non-AP STA is associated with the current AP. If the non-AP STA does not initiate an IP address assignment request, the non-AP STA may still continue to use the source IP address when carrying out data transmission.

[0109] Figure 6 is a schematic flowchart of a communication method according to an embodiment of the present application. The method may be applied to a first communication device or a second communication device. The first communication device may include a current AP or a target AP, and the second communication device may include a non-AP STA. For a specific description of the AP or non-AP STA in this method, please refer to Figures 1a, 1b, 2a, 2b, 3a, and 3b. Further details are not described here. As shown in Figure 6, the method includes the following steps.

[0110] 601: The first communication device generates the first communication frame.

[0111] The first communication frame contains first instruction information, which indicates whether the non-AP STA should initiate an IP address assignment request when the non-AP STA is handed over from the current AP to the target AP. Alternatively, the first instruction information may be: during a BSS transition, Whether a non-AP STA needs to initiate an IP address allocation request, Whether the non-AP STA needs to restart the IP address allocation request, This may be understood as indicating whether a non-AP STA needs to initiate an IP address assignment request negotiation. Alternatively, the first instruction information may be understood as indicating whether a non-AP STA needs to initiate an IP address assignment request during a roaming handover, etc. For a specific description of the current AP and the target AP, please refer to the relevant descriptions in Figures 3a and 3b. Further details are not provided here.

[0112] For example, a first instruction value being a first value indicates that the non-AP STA needs to initiate an IP address allocation request, or that the first instruction is unavailable. The first instruction being unavailable may be understood as the validity of the first instruction being unknown. If the first instruction is unavailable, see the steps taken by the non-AP STA based on the first instruction for the steps taken by the non-AP STA initiating an IP address allocation request. Alternatively, a first instruction value being a second value indicates that the non-AP STA does not need to initiate an IP address allocation request.

[0113] In another example, the value of the first instruction information being the second value could alternatively indicate that the first instruction information is included in (i.e., present in) the first communication frame, and the inclusion of the first instruction information could indicate that a non-AP STA does not need to initiate an IP address assignment request.

[0114] For example, the first instruction information may occupy 1 bit, the second value may be 1, and the first value may be 0.

[0115] For example, the first communication device is the current AP. If the current AP detects that the current AP and the target AP are located on the same Layer 2 network and are handled by the same DHCP server, the current AP sets the first instruction information to indicate that when a non-AP STA is handed over to the target AP, the non-AP STA does not need to initiate an IP address assignment request. Alternatively, the first communication device is the target AP. If the target AP detects that the target AP and the current AP are located on the same Layer 2 network and are handled by the same DHCP server, the target AP may set the first instruction information to indicate that when a non-AP STA is handed over to the target AP, the non-AP STA does not need to initiate an IP address assignment request.

[0116] The frame format of the first instruction information is described in detail below.

[0117] Example 1

[0118] The first instruction information is contained within a neighbor report element in the first communication frame. For example, the first communication frame may contain a BSS transition candidate list, which may contain one or more neighbor report elements. A single neighbor report element may contain relevant information for one neighbor AP. Therefore, each neighbor report element in the BSS transition candidate list may correspond to one neighbor AP. It should be understood that the neighbor APs shown here may be understood as alternative target APs, candidate target APs, or similar entities. The BSS transition candidate list is optional.

[0119] Figure 7a shows an example of a neighbor report element in the BSS transition candidate list, where ellipses indicate the omission of another neighbor report element. As shown in Figure 7a, a neighbor report element may include the following fields: element ID, length, basic service set identifier (BSS identifier, BSSID), basic service set identifier information (BSSID info), operating class, channel number, physical layer type (PHY type), and optional subelement. The BSSID field indicates the BSSID corresponding to the reported nearby AP. The BSSID info field indicates relevant information about the reported BSSID. The operating class and channel number fields indicate the channel to which the reported BSSID belongs. The physical layer type field indicates the physical layer type of the AP corresponding to the reported BSSID.

[0120] For example, the BSSID information field may include the following fields: AP reachability, security, key scope, capabilities, mobility domain, high throughput, very high throughput, fine timing measurement (FTM), high efficiency, extended range BSS (ER BSS), co-located AP, unsolicited probe response active, member of an extended service set with a 2.4 / 5 GHz co-located AP, on-channel tunneling (OCT) supported with reporting AP, co-located with a 6GHz AP, and a field containing first directional information.

[0121] Fields containing the first directive information within the BSSID information field use the original reserved bit in the BSSID information field to include the first directive information. For example, a field set to 1 indicates that the non-AP STA does not need to restart the IP address assignment request; or a field set to 0 indicates that the non-AP STA needs to restart the IP address assignment request negotiation, or that the first directive information is unavailable. Referring to the relationship between neighbor report elements and APs, a field containing the first directive information set to 1 can further indicate that the non-AP STA does not need to restart the IP address assignment request when the non-AP STA is handed over from the current AP to a nearby AP corresponding to the neighbor report element.

[0122] For example, the first communication frame may be a BTM request frame. Figure 7b is a schematic flowchart of BTM according to an embodiment of the present application. As shown in Figure 7b, the current AP can send a BTM request frame to a non-AP STA. For a detailed explanation of Figure 7b, please refer to Figure 4. Details will not be explained again here. Figure 7c is a format diagram of a BTM request frame according to an embodiment of the present application. As shown in Figure 7c, the BTM request frame may include the following fields: category, wireless network management action, dialog token, request mode, disassociation timer, validity interval, BSS termination duration, session info, universal resource locator (URL), and BSS transition candidate list. The BSS transition candidate list is optional. The validity interval field indicates the number of beacon periods during which the BSS transition candidate list is valid. The Disassociation Timer field indicates the time elapsed before the current AP sends a disassociation frame.

[0123] The request mode field indicates a specific request mode. The request mode field may include the following fields: preferred candidate list included (may be understood as a BSS transition candidate list), abridge, disassociation imminent, BSS termination included, extended service set (ESS) disassociation imminent, link removal, and reserved (e.g., 2 bits). The preferred candidate list included field indicates whether or not to include a list of preferred candidates. Usage of the abridge field: If the associated AP does not advise the STA to hand over to a BSS not on the preferred candidate list, or if the STA prohibits handing over to a BSS not on the preferred candidate list, the abridge field is set to 0; also, if the associated AP has set the preference value of a BSS not on the preferred candidate list to 0, the abridge field is set to 1. Usage of the Disconnection Warning Field: A Disconnection Warning Field set to 1 indicates that the current AP may send a disassociation frame regarding being disconnected from a non-AP STA; a Disconnection Warning Field set to 0 indicates that the current AP may not send a disassociation frame regarding being disconnected from the STA.

[0124] It will be understood that for a specific description of the BTM request frame, please refer to the relevant standards or protocols. The embodiments of this application do not provide an exhaustive description of the details. The ACK frame of the BTM request frame shown in Figure 7b may be used to confirm that a non-AP STA has received the BTM request frame. By analogy, the ACK frame of a BTM query frame may be used to confirm that the current AP has received the BTM query frame, and the ACK frame of a BTM response frame may be used to confirm that the current AP has received the BTM response frame.

[0125] In this embodiment of the present application, the current AP is capable of sending a BTM request frame to a non-AP STA. The BTM request frame includes one or more neighbor report elements, each neighbor report element including a field containing first instruction information, which can indicate whether the non-AP STA needs to restart the IP address assignment request when handing over from the current AP to the nearby AP corresponding to the neighbor report element. The value of the first instruction information in each neighbor report element may be set separately. For example, the current AP may set the value of the first instruction information separately based on the relationship between the current AP and the nearby AP corresponding to the neighbor report element (i.e., the candidate target AP). For the relationship shown herein, see the relevant description above regarding Layer 2 networks and the same DHCP server. Further details are not described here.

[0126] For example, if the first instruction indicates that a non-AP STA does not need to initiate an IP address assignment request again when it is handed over from the current AP to a corresponding nearby AP (including the target AP), then the non-AP STA may not need to initiate an IP address assignment request. Therefore, when a non-AP STA performs a BSS transition, it may not need to perform the DHCP negotiation shown in Figure 4, or the reassociation request frame and reassociation response frame may not include the FILS IP address assignment element.

[0127] In another example, if the first instruction indicates that a non-AP STA needs to restart the IP address assignment request when it is handed over from the current AP to a corresponding nearby AP (including the target AP), the non-AP STA may include a FILS IP address assignment element in the reassociation request frame (provided both the non-AP STA and the corresponding nearby AP support the FILS protocol), or the non-AP STA may restart the IP address assignment request during the DHCP negotiation phase (as shown in Figure 5).

[0128] Referring to the procedure shown in Figure 4, if the current AP indicates to the non-AP STA in the BTM request frame that the non-AP STA does not need to initiate an IP address assignment request, the reassociation request frame or reassociation response frame does not need to include the FILS IP address assignment element, thereby reducing the workload for both parties in parsing the reassociation request frame or reassociation response frame; and the non-AP STA does not need to perform DHCP negotiation, resulting in reduced roaming handover time and reduced service interruption time for the non-AP STA.

[0129] In possible implementations, the current AP may receive a BTM query frame from a non-AP STA before generating a BTM request frame. For example, as shown in Figure 7d, the BTM query frame may include the following fields: category, wireless network management (WNM) action, dialog token, BSS transition query reason, and BSS transition candidate list. The BSS transition candidate list is optional. The BSS transition candidate list field includes one or more neighbor report elements. The BSS transition query reason field can indicate the reason why a non-AP STA is sending a BTM query frame. For example, see Table 1 for the relationship between the description and value of the BSS transition query reason field. For a specific description of the BTM query frame, see the relevant standard or protocol. Details are not described in the embodiments of this application. For example, a neighbor report element in the BSS transition candidate list of a BTM query frame may include a first directive (for example, the first directive set to a first value indicates that the first directive is unavailable), or it may not include a first directive. Table 1 [Table 1]

[0130] In this embodiment of the present application, the first instruction information is included in the neighbor report element within the BTM request frame, allowing the current AP to notify the non-AP in advance whether the STA needs to initiate an IP address assignment request. This optimizes IP address negotiation. For example, if the first instruction information indicates that the non-AP STA does not need to initiate an IP address assignment request, the roaming handover time for the non-AP STA is reduced, and the non-AP STA does not need to include the FILS IP address assignment element in the reassociation request frame. This reduces signaling overhead.

[0131] Example 2

[0132] The first instruction information is contained within the First Initial Link Setup FILS IP Address Assignment element of the first communication frame. For example, the FILS IP Address Assignment element in the first communication frame may include an IP address response control field, which may contain fields used to include the first instruction information. Figure 8a shows an example of a FILS IP Address Assignment element. As shown in Figure 8a, the FILS IP Address Assignment element may include the following fields: element identifier, length, element ID extension, and IP address data. For example, the IP address data field may include an IP address response control field and a domain name system (DNS) information control field.

[0133] In one example, the first instruction information may be contained in the first or eighth bit of the IP address response control field. The first and eighth bits shown here are determined in order from least significant to most significant. As shown in Figure 8a, the first instruction information may be contained in the B0 or ​​B7 bit.

[0134] In the current solution (or may be understood as an alternative solution), the meaning of each bit in the IP address response control field may be as shown in Table 2. Table 2 [Table 2]

[0135] However, in the solution provided in this embodiment of the present application, if the first instruction information is included in the B0 bit, setting the B0 bit to 1 may indicate that the non-AP STA does not need to initiate an IP address assignment request, or that the IP address may be fed back later. If the first instruction information is included in the B7 bit, setting the B7 bit to 1 may indicate that the non-AP STA does not need to initiate an IP address assignment request. If the first instruction information is included in the B7 bit, setting the B7 bit to 1 may be understood as the IP address response control field including the field used to include the first instruction information. Including this field indicates that the non-AP STA does not need to initiate an IP address assignment request. Setting the B7 bit to 0 may be understood as the IP address response control field excluding the field used to include the first instruction information. Excluding the field indicates that the non-AP STA needs to initiate an IP address assignment request.

[0136] In another example, the first directive information may alternatively be contained in the reserved bits of the DNS information control field. For example, as shown in Figure 8b, the DNS information control field may include the DNS server IPv4 address present field, the DNS server IPv6 address present field, the IPv4 DNS server MAC address present field, the IPv6 DNS server MAC address present field, the field used to include the first directive information, and the reserved field. See Figure 8a for a description of the first directive information. Further details are not provided here. For a description of other fields within the DNS information control field, refer to the relevant standard or protocol.

[0137] If the first instruction indicates that the non-AP STA does not need to initiate an IP address assignment request, the non-AP STA may not need to perform the DHCP negotiation procedure shown in Figure 4 or Figure 5. If the first instruction indicates that the non-AP STA needs to initiate an IP address assignment request, the FILS IP address assignment element may include the target IP address. Alternatively, the non-AP STA can obtain the target IP address by performing the DHCP negotiation procedure shown in Figure 4 or Figure 5.

[0138] For example, the first communication frame may be a reassociation response frame. Figure 8c is a diagram of the reassociation procedure according to an embodiment of the present application. As shown in Figure 8c, the target AP can send a reassociation response frame to a non-AP STA. The format of the reassociation response frame may be as shown in Table 3. It will be understood that x1, y1, z1, and o1 shown in Table 3 are all integers. The specific values ​​of x1, y1, z1, and o1 are not limited to the embodiments of the present application. As shown in Table 3, the reassociation response frame includes a FILS IP address assignment element. For a specific description of the FILS IP address assignment element, see Figure 8a. Further details are not provided here. For a description of other elements or fields in the reassociation response frame, see the relevant standard or protocol. Further details are not provided in the embodiments of the present application. Table 3 [Table 3]

[0139] In possible implementations, before the target AP generates a reassociation response frame, the target AP may receive further reassociation request frames from the non-AP STA. The format of the reassociation request frame may be as shown in Table 4, and the FILS IP address assignment element is optional. It will be understood that x2, y2, z2, and o2 shown in Table 4 are all integers. The specific values ​​of x2, y2, z2, and o2 are not limited to the embodiments of this application. For a specific description of the FILS IP address assignment elements included in Table 4, see Table 3 or the relevant standards, protocols, or similar. Details are not described in the embodiments of this application. For example, the FILS IP address assignment element in the reassociation response frame may include first instruction information (e.g., the first instruction information being set to a first value indicates that the first instruction information is unavailable) or may not include first instruction information. Table 4 [Table 4]

[0140] In this embodiment of the present application, even if a non-AP STA does not include a FILS IP address assignment element in its reassociation request frame, the target AP may include a FILS IP address assignment element in its reassociation response frame, the FILS IP address assignment element including first instruction information.

[0141] The fact that the first communication frame shown above is a BTM request frame or a reassociation response frame is merely an example. As standards evolve, the roaming handover procedure for non-AP STAs may change. If the roaming handover procedure changes (if the procedure shown in Figure 4 changes), the first communication frame may further include other types of communication frames. The description of the first communication frame in this case is also applicable to the second communication frame.

[0142] 602: The first communication device transmits a first communication frame, and the second communication device receives the first communication frame in response.

[0143] 603: The second communication device analyzes the first communication frame.

[0144] For example, a non-AP STA may determine whether it needs to initiate an IP address assignment request by analyzing the first instruction information within the first communication frame.

[0145] For example, if the first instruction information indicates that the non-AP STA does not need to initiate an IP address assignment request, the non-AP STA may not initiate an IP address assignment request. If the non-AP STA does not initiate an IP address assignment request, after being handed over to the target AP, the non-AP STA can continue to use the source IP address to perform data transmission with the target AP. It will be understood that the data transmission described in this embodiment of the present application includes at least one of the non-AP STA sending data to the target AP and the target AP sending data to the non-AP STA. Specifically, with respect to the non-AP STA, the data transmission includes at least one of data transmission and reception; with respect to the target AP, the data transmission includes at least one of data reception and transmission.

[0146] In another example, a non-AP STA may initiate an IP address assignment request if the first instruction indicates that the non-AP STA needs to initiate one. For example, when the first communication frame is a BTM request frame, see the reassociation request and reassociation response methods shown in Figure 4, or the DHCP negotiation methods shown in Figure 4 or 5, for an example of how a non-AP STA may initiate an IP address assignment request when the first communication frame is a reassociation response frame, see the DHCP negotiation methods shown in Figure 4 or 5. Once a non-AP STA initiates an IP address assignment request, it can delete the source IP address. After obtaining the target IP address, the non-AP STA may perform data transmission with the target AP by using the target IP address. Before the non-AP STA obtains the target IP address, or after the non-AP STA obtains the target IP address, the non-AP STA deletes the source IP address. This is not limited to the embodiments of this application.

[0147] Indeed, if the first instruction indicates that the non-AP STA does not need to initiate an IP address allocation request, the non-AP STA can still initiate one. For example, if the non-AP STA is legacy, it may not be able to parse the first instruction, and therefore may still initiate an IP address allocation request.

[0148] In a possible implementation, the method shown in Figure 6 may further include: a non-AP STA transmits a second communication frame, and in response, the current AP receives the second communication frame.

[0149] For example, as shown in Figure 7b, if the first communication frame is a BTM request frame, the non-AP STA may send a second communication frame, which may be a BTM response frame. As shown in Figure 7e, the BTM response frame may include the following fields: Category, Wireless Network Management Action, Dialog Token, BTM Status Code, BSS Termination Delay, Target BSSID, and BSS Transition Candidate List. The Target BSSID and BSS Transition Candidate List are optional. For example, if the value of the BTM Status Code field is 0, the BTM response frame may include the Target BSSID field. The BTM Status Code field may indicate whether the BSS transition request is accepted. The BSS Termination Delay indicates the time from the current time to the BSS termination time. For example, see Table 5 for the relationship between the BTM Status Code value and the descriptive description. The BTM Status Code values ​​shown in Table 5 are just examples. As standards evolve, BTM status codes may have more values, more meanings, or similar codes. Table 5 [Table 5]

[0150] For example, the neighbor report element in the BSS transition candidate list shown in Figure 7e may contain the first instruction information. For a specific description of the BSS transition candidate list shown in Figure 7e, see Figure 7a. Further details are not provided here. In other words, the neighbor report element in the BSS transition candidate list in the BTM response frame may be the same as the corresponding neighbor report element in the BSS transition candidate list in the BTM request frame.

[0151] In another example, the last bit in the BSSID information of the neighbor report element in the BSS transition candidate list shown in Figure 7e is still a reserved bit.

[0152] In yet another example, the last bit of the leading bits in the BSSID information of the neighbor reporting element in the BSS transition candidate list shown in Figure 7e is used to include second directive information, which can indicate whether the non-AP STA initiates an IP address assignment request. In other words, the non-AP STA can indicate to the current AP via the second directive information whether the non-AP STA initiates an IP address assignment request based on the first directive information. Thus, the current AP can know in advance the specific behavior of the non-AP STA, improving the efficiency of the interaction between the two communicating parties.

[0153] In this embodiment of the present application, the first communication device explicitly indicates, via first instruction information, whether a non-AP STA needs to initiate an IP address assignment request, so that the non-AP STA can explicitly know, based on the first instruction information, whether it needs to initiate an IP address assignment request. For example, if the first instruction information indicates that the non-AP STA does not need to initiate an IP address assignment request, the method provided in this embodiment of the present application can effectively reduce the roaming handover time of the non-AP STA, reduce service interruption time, effectively avoid unnecessary IP address assignment requests, and optimize the IP address negotiation procedure. For example, if the first instruction information indicates that the non-AP STA needs to initiate an IP address assignment request, the need for the non-AP STA to initiate an IP address assignment request again is reduced.

[0154] In the embodiments shown in this application, “field” is used as an illustrative example, and “field” is not particularly distinguished from “subfield” and similar entities. Although “field” and “subfield” are not particularly distinguished in the embodiments shown in this application, a person skilled in the art can appropriately distinguish the relationships between fields (or elements and fields) shown in this application.

[0155] The communication device provided in the embodiment of this application will be described below.

[0156] In this application, the communication device is divided into functional modules based on embodiments of the method described above. For example, the functional modules may be divided into corresponding functions, or two or more functions may be integrated into a single processing module. The integrated module may be implemented in hardware form or in the form of a software functional module. It should be noted that in this application, module division is merely an example and is nothing more than a logical functional division. In practice, other division methods may be used. The communication device in the embodiments of this application will be described in detail below with reference to Figures 9 to 11.

[0157] Figure 9 is a structural diagram of a communication device according to an embodiment of the present application. As shown in Figure 9, the communication device includes a processing unit 901 and a transceiver unit 902. The transceiver unit 902 is capable of performing corresponding communication functions, and the processing unit 901 is configured to process data. For example, the transceiver unit 902 may also be called a communication interface or a communication unit.

[0158] In some embodiments of this application, the communication device may be configured to perform operations performed by the first communication device (such as the current AP or target AP) in embodiments of the method described above. In this case, the communication device may be a WLAN device, chip, or functional module built into a WLAN device, or similar. The transceiver unit 902 is configured to perform sensing / receiving operations of the first communication device in embodiments of the method described above. The processing unit 901 is configured to perform operations related to processing of the first communication device in embodiments of the method described above.

[0159] For example, the processing unit 901 is configured to generate a first communication frame; the transceiver unit 902 is configured to transmit or output the first communication frame.

[0160] It will be understood that the transceiver unit 902 is capable of transmitting a first communication frame to another communication device, or that the transceiver unit 902 is capable of outputting a first communication frame from the first processing unit 901 to another component, another functional module, or similar device within the first communication device. The explanation relating to the output of other information by the transceiver unit is similar and will not be described in detail below.

[0161] For example, the transceiver unit 902 is configured to input or receive a second communication frame. The processing unit 901 is further configured to analyze the second communication frame.

[0162] In other embodiments of this application, the communication device may be configured to perform operations performed by the non-AP STA in the embodiments of the method described above. In this case, the communication device may be a WLAN device, chip, or functional module built into a WLAN device, or similar. The transceiver unit 902 is configured to perform the transmission / reception operations of the non-AP STA in the embodiments of the method described above. The processing unit 901 is configured to perform the processing operations of the non-AP STA in the embodiments of the method described above.

[0163] The transceiver unit 902 is configured to receive or input a first communication frame; the processing unit 901 is further configured to analyze the first communication frame.

[0164] For example, the transceiver unit 902 is configured to output or transmit a second communication frame.

[0165] Optionally, the communication device may further include a storage unit. The storage unit may be configured to store instructions and / or data. The processing unit 901 can read the instructions and / or data from the storage unit, thereby enabling the communication device to carry out embodiments of the method described above. For example, the storage unit may be configured to store information such as an IP address.

[0166] It will be understood that the specific descriptions of the transceiver unit and processing unit in the embodiments of this application are merely illustrative. For specific functions, steps, or similar actions performed by the transceiver unit and processing unit, please refer to the embodiments of the method described above. Details are not described here.

[0167] For a description of the first communication frame, first instruction information, second communication frame, and similar elements in the embodiments described above, please refer to the description in the embodiments of the method described above. Further details will not be described here.

[0168] The above describes the communication device in the embodiment of the present application. The following describes possible product forms of the communication device. It should be understood that any form of product having the functionality of the communication device shown in Figure 9 falls within the scope of protection of the embodiment of the present application. It should be further understood that the following description is merely an example and does not limit the product form of the communication device in the embodiment of the present application.

[0169] In possible implementations, in the communication device shown in Figure 9, the processing unit 901 may be one or more processors, and the transceiver unit 902 may be a transceiver, or the transceiver unit 902 may be a transmitting unit and a receiving unit. The transmitting unit may be a transmitter, and the receiving unit may be a receiver. The transmitting unit and the receiving unit are integrated into a single device, for example, a transceiver. In this embodiment of the present application, the processor and the transceiver may be coupled or similar. The connection method between the processor and the transceiver is not limited to the embodiment of the present application. In the process of performing the method described above, the information transmission process in the method described above may be understood as the process of outputting information by the processor. When outputting information, the processor outputs information to the transceiver so that the transceiver transmits the information. After the information has been output by the processor, further processing may have to be performed on the information before the processed information arrives at the transceiver. Similarly, the information reception process in the method described above may be understood as the process of receiving input information by the processor. When the processor receives input information, the transceiver receives that information and inputs it to the processor. Furthermore, after the transceiver receives the information, other processing may need to be performed on that information before it is received by the processor.

[0170] As shown in Figure 10, the communication device 100 includes one or more processors 1020 and transceivers 1010.

[0171] In some embodiments of the present application, the communication device may be configured to perform steps, functions, or similar actions performed by the first communication device in the embodiments of the method described above.

[0172] For example, the processor 1020 is configured to generate a first communication frame; the transceiver 1010 is configured to transmit the first communication frame.

[0173] For example, transceiver 1010 is configured to receive a second communication frame; processor 1020 is configured to analyze the second communication frame.

[0174] In other embodiments of this application, the communication device may be configured to perform steps, functions, or similar actions performed by a non-AP STA in the embodiments of the method described above.

[0175] The transceiver 1010 is configured to receive a first communication frame; the processor 1020 is configured to analyze the first communication frame.

[0176] For example, transceiver 1010 is configured to send a second communication frame. For example, processor 1020 is further configured to generate a second communication frame.

[0177] It will be understood that the specific descriptions of the transceiver and processor in the embodiments of this application are merely illustrative. For specific functions, steps, or similar actions performed by the transceiver and processor, please refer to the embodiments of the method described above. Further details are not described here.

[0178] For a description of the first communication frame, first instruction information, second communication frame, and similar elements in the embodiments described above, please refer to the description in the embodiments of the method described above. Further details will not be described here.

[0179] In each implementation of the communication device shown in Figure 10, the transceiver may include a receiver and a transmitter. The receiver is configured to perform the function (or operation) of receiving. The transmitter is configured to perform the function (or operation) of transmitting. The transceiver is configured to communicate with another device / device via a transmission medium.

[0180] Optionally, the communication device 100 may further include one or more memories 1030 configured to store program instructions, data and / or the like. The memories 1030 are coupled to the processor 1020. The coupling in this embodiment of the present application is an indirect coupling or communication connection between devices, units, or modules, which may be in electrical, mechanical, or other forms, and is used for information exchange between devices, units, and modules. The processor 1020 is capable of operating with the memories 1030. The processor 1020 is capable of executing program instructions stored in the memories 1030. Optionally, at least one of the one or more memories may be included in the processor. For example, the memory may be configured to store IP addresses and the like.

[0181] The specific connecting medium between the transceiver 1010, the processor 1020, and the memory 1030 is not limited to the embodiments of this application. In this embodiment of the application, in Figure 10, the memory 1030, the processor 1020, and the transceiver 1010 are connected to each other via a bus 1040. The bus is shown in Figure 10 using a thick line. The connections between other components are merely examples for illustrative purposes and are not limited to them. Buses may be classified as address buses, data buses, control buses, and similar. For simplicity of representation, buses are shown in Figure 10 using only a single thick line. However, this does not indicate that there is only one bus or only one type of bus.

[0182] In this embodiment of the present application, the processor may be a general-purpose processor, a digital signal processor, an application-specific integrated circuit, a field-programmable gate array or other programmable logic device, a discrete gate or transistor logic device, a discrete hardware component, or the like. The processor is capable of carrying out or executing the methods, steps, and logic block diagrams disclosed in the embodiments of the present application. The general-purpose processor may be a microprocessor, any conventional processor, or the like. The steps of the methods disclosed with reference to the embodiments of the present application may be carried out directly by a hardware processor, or by using a combination of hardware and software modules within the processor, etc.

[0183] In this embodiment of the present application, memory may include, but is not limited to, non-volatile memory such as a hard disk drive (HDD) or solid-state drive (SSD), random access memory (RAM), erasable programmable read-only memory (EPROM), read-only memory (ROM), or compact disc read-only memory (CD-ROM). Memory is any storage medium that can be used to contain or store program code in the form of instructions or data structures and that can be read and / or written to by a computer (e.g., a communication device as described in this application). However, this application is not limited to these. Alternatively, memory in this embodiment of the present application may be a circuit or any other device capable of performing a storage function and configured to store program instructions and / or data.

[0184] For example, processor 1020 is configured primarily to process communication protocols and data, control the entire communication device, execute software programs, and process data for software programs. Memory 1030 is configured primarily to store software programs and data. Transceiver 1010 may include a control circuit and an antenna. The control circuit is configured primarily to perform conversions between baseband signals and radio frequency signals and to process radio frequency signals. The antenna is configured primarily to receive or transmit radio frequency signals in the form of electromagnetic waves. Input / output devices, such as touchscreens, displays, or keyboards, are configured primarily to receive data entered by the user and output data to the user.

[0185] After the communication device is powered on, the processor 1020 may read the software program in the memory 1030, interpret and execute the instructions of the software program, and process the data of the software program. If it is necessary for the data to be transmitted wirelessly, the processor 1020 performs baseband processing on the data to be transmitted, and then outputs the baseband signal to the radio frequency circuit, which performs radio frequency processing on the baseband signal and then transmits the radio frequency signal to the outside in the form of electromagnetic waves via the antenna. When the data is transmitted to the communication device, the radio frequency circuit receives the radio frequency signal via the antenna, converts the radio frequency signal into a baseband signal, and outputs the baseband signal to the processor 1020. The processor 1020 converts the baseband signal into data and processes the data.

[0186] In other implementations, the radio frequency circuitry and antennas may be located independently of the processor performing baseband processing. For example, in a distributed scenario, the radio frequency circuitry and antennas may be located independently of the communication equipment.

[0187] It will be understood that the communication device shown in the embodiments of this application may have more components and similar components than those shown in Figure 10. This is not limited to the embodiments of this application. The method performed by the processor and transceiver is merely an example. For specific steps performed by the processor and transceiver, please refer to the method described above.

[0188] In another possible implementation, in the communication device shown in Figure 9, the processing unit 901 may be one or more logic circuits, and the transceiver unit 902 may be an input / output interface, also called a communication interface, interface circuit, interface, or similar. Alternatively, the transceiver unit 902 may be a transmit unit and a receive unit. The transmit unit may be an output interface, and the receive unit may be an input interface. The transmit unit and the receive unit are integrated into a single unit, for example, an input / output interface. As shown in Figure 11, the communication device shown in Figure 11 includes a logic circuit 1101 and an interface 1102. In other words, the processing unit 901 may be implemented using the logic circuit 1101, and the transceiver unit 902 may be implemented using the interface 1102. The logic circuit 1101 may be a chip, processing circuit, integrated circuit, system on chip (SoC), or similar. The interface 1102 may be a communication interface, input / output interface, pin, or similar. For example, Figure 11 shows an example where the communication device is a chip. The chip includes a logic circuit 1101 and an interface 1102.

[0189] In this embodiment of the present application, the logic circuits and interfaces may be further coupled to one another. The specific method of connection between the logic circuits and interfaces is not limited to the embodiment of the present application.

[0190] In some embodiments of the present application, the communication device may be configured to perform steps, functions, or similar actions performed by the first communication device in the embodiments of the method described above.

[0191] For example, logic circuit 1101 is configured to generate a first communication frame; interface 1102 is configured to output the first communication frame.

[0192] For example, interface 1102 is configured to receive a second communication frame; logic circuit 1101 is configured to analyze the second communication frame.

[0193] In other embodiments of this application, the communication device may be configured to perform steps, functions, or similar actions performed by a non-AP STA in the embodiments of the method described above.

[0194] Interface 1102 is configured to receive a first communication frame; logic circuit 1101 is configured to analyze the first communication frame.

[0195]

[0195] For example, interface 1102 is configured to output a second communication frame. For example, logic circuit 1101 is further configured to generate a second communication frame.

[0196] It will be understood that the specific descriptions of the logic circuits and interfaces in the embodiments of this application are merely examples. For specific functions, steps, or similar actions performed by the logic circuits and interfaces, please refer to the embodiments of the method described above. Further details are not described here.

[0197] For example, the chip may also include memory, which may be configured to store IP addresses.

[0198] In the embodiments described above, please refer to the description in the embodiments of the method described above for a description of the first communication frame, the first instruction information, the second communication frame, and similar elements. Further details will not be described here.

[0199] It will be understood that the communication device described in this embodiment of the present application may implement the method provided in the embodiment of the present application in hardware form, or in software form. This is not limited to the embodiments of the present application.

[0200] Embodiments of this application further provide a communication system. The communication system includes a first communication device (e.g., a current AP or a target AP) and a non-AP STA. For a description of the current AP (or target AP) and the non-AP STA, please refer to the preceding description.

[0201] Furthermore, this application further provides a computer program. The computer program is used to perform operations and / or processes performed by the current AP or the target AP in the manner provided in this application.

[0202] This application further provides a computer program. The computer program is used to implement operations and / or processes that are performed by non-AP STA in the manner provided in this application.

[0203] This application further provides a computer-readable storage medium for storing computer code. When the computer code is executed on a computer, the computer becomes capable of performing operations and / or processes performed by the current AP or a target AP in the manner provided in this application.

[0204] This application further provides a computer-readable storage medium for storing computer code. When the computer code is executed on a computer, the computer becomes capable of performing operations and / or processes that are performed by non-AP STA in the manner provided in this application.

[0205] This application further provides a computer program product, which includes computer code or a computer program. When the computer code or computer program is executed on a computer, the actions and / or processes performed by the current AP or the target AP are executed in the manner provided in this application.

[0206] This application further provides a computer program product, which includes computer code or a computer program. When the computer code or computer program is executed on a computer, the operations and / or processes performed by non-AP STA in the manner provided in this application are executed.

[0207] In some embodiments provided in this application, it will be understood that the disclosed systems, apparatus, and methods may be carried out in other ways. For example, the embodiments of the apparatus described are merely examples. For example, the division into units is merely a logical functional division and may actually be a different division. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not performed. Furthermore, the mutual coupling, direct coupling, or communication connection shown or described may be carried out through some interface, indirect coupling or communication connection between apparatus or units, electrical connection, mechanical connection, or other form of connection.

[0208] Units described as separate parts may or may not be physically separate, and parts shown as units may or may not be physical units, and may be located in one place or distributed across multiple network units. Some or all of the units can be selected based on the actual requirements for achieving the technical effects of the solutions provided in the embodiments of this application.

[0209] Furthermore, the functional units in the embodiments of this application may be integrated into a single processing unit, each unit may exist physically independently, or two or more units may be integrated into a single unit. The integrated unit may be implemented in hardware form or in the form of a software functional unit.

[0210] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, the integrated unit may be stored on a computer-readable storage medium. Based on such understanding, the technical solution of the present application, or a portion of the technical solution that contributes to the prior art, may be implemented in the form of a software product. A computer software product is stored on a storage medium and includes a number of instructions for instructing a computer device (which may be a personal computer, server, network device, or the like) to perform all or part of the steps of the method described in the embodiments of the present application. The readable storage medium includes any medium capable of storing program code, such as a USB flash drive, removable hard disk, read-only memory (ROM), random access memory (RAM), magnetic disk, or optical disk.

[0211] The foregoing description is merely a specific implementation of the present application and does not limit the scope of protection of the present application. Any modifications or substitutions readily conceived by a person skilled in the art within the technical scope disclosed in the present application shall fall within the scope of protection of the present application. Accordingly, the scope of protection of the present application shall be subject to the scope of protection of the claims.

Claims

1. It is a method of communication: Steps include: generating a first communication frame, the first communication frame including first instruction information, the first instruction information indicating whether the non-AP STA should initiate an Internet Protocol IP address assignment request when the non-AP STA is handed over from the current access point AP to the target AP; and The step of transmitting the first communication frame; A method that includes this.

2. The method according to claim 1, wherein the first instruction information is included in the neighbor report element of the first communication frame.

3. The method according to claim 1, wherein the first instruction information is included in the First Initial Link Setup FILS IP Address Assignment element of the first communication frame.

4. The method according to claim 3, wherein the FILS IP address assignment element includes an IP address response control field, and the first instruction information is contained in the first or eighth bit of the IP address response control field.

5. A method according to any one of claims 1 to 4, wherein the value of the first instruction information being a first value indicates that the non-AP STA needs to initiate the IP address allocation request; or the value of the first instruction information being a second value indicates that the non-AP STA does not need to initiate the IP address allocation request.

6. A method according to any one of claims 1 to 5, wherein the first communication frame is one of the following: a basic service set BSS transition management BTM request frame and a reassociation response frame.

7. It is a method of communication: Steps include: receiving a first communication frame, the first communication frame containing first instruction information, the first instruction information indicating whether the non-AP STA should initiate an Internet Protocol IP address assignment request when the non-AP STA is being handed over from the current access point AP to the target AP; and Steps to analyze the first communication frame; A method that includes this.

8. The method according to claim 7, further: A method comprising the step of transmitting a second communication frame, wherein the second communication frame includes second instruction information, the second instruction information indicating whether the non-AP STA initiates an IP address allocation request.

9. The method according to claim 7 or 8, wherein the first instruction information is included in the neighbor report element of the first communication frame.

10. The method according to claim 7 or 8, wherein the first instruction information is included in the First Initial Link Setup FILS IP Address Assignment element of the first communication frame.

11. The method according to claim 10, wherein the FILS IP address assignment element includes an IP address response control field, and the first instruction information is contained in the first or eighth bit of the IP address response control field.

12. In the method according to any one of claims 7 to 11, the first communication frame is one of the following: a basic service set BSS transition management BTM request frame and a reassociation response frame; and The second communication frame is the BTM response frame, method.

13. The method according to any one of claims 7 to 12, further: When the non-AP STA initiates the IP address assignment request based on the first instruction information, the step of deleting the source IP address that was used by the non-AP STA for data transmission; or If the non-AP STA does not initiate the IP address assignment request based on the first instruction information, the step of using the source IP address for data transmission; A method that includes this.

14. A communication device comprising a unit configured to perform the method described in any one of claims 1 to 13.

15. A communication device including a processor and memory, The memory is configured to store instructions; and A communication device wherein the processor is configured to execute the instructions to perform the method according to any one of claims 1 to 13.

16. A communication device comprising a logic circuit and an interface, wherein the logic circuit is coupled to the interface, the interface is configured to input and / or output code instructions, and the logic circuit is configured to execute the code instructions to perform the method according to any one of claims 1 to 13.

17. A computer-readable storage medium configured to store a computer program, wherein when the computer program is executed, the method according to any one of claims 1 to 13 is performed.

18. A communication system comprising a first communication device and a second communication device, wherein the first communication device is configured to perform the method described in any one of claims 1 to 6, and the second communication device is configured to perform the method described in any one of claims 7 to 13.

Images