Execution methods and apparatuses for roaming process, devices and medium

Abstract

The present application belongs to the technical field of communications. Disclosed in the present application are execution methods and apparatuses for a roaming process, devices and a medium. A method comprises: in a seamless roaming process, executing a behavior conforming to a first rule.

Description

Methods, devices, equipment, and media for the roaming process Technical Field

[0001] This application relates to the field of communication technology, and in particular to a method, apparatus, device and medium for performing roaming processes. Background Technology

[0002] When a non-access point device initiates roaming, it can stop communicating with the source network device and switch to communicating with the target network device.

[0003] During roaming, how to avoid the channel accessed by non-access point devices being inconsistent with the channel operated by the target network devices is an urgent problem to be solved. Summary of the Invention

[0004] This application provides a method, apparatus, device, and medium for performing roaming processes. The technical solution is as follows:

[0005] According to one aspect of this application, a method for performing a roaming process is provided, the method being performed by a target-side network device, the method comprising:

[0006] Perform actions that conform to the first rule during seamless roaming.

[0007] According to another aspect of this application, a method for performing a roaming process is provided, the method being performed by a non-access point device, the method comprising:

[0008] Perform actions that conform to the first rule during seamless roaming.

[0009] According to another aspect of this application, an execution apparatus for a roaming process is provided, the apparatus being used in a target-side network device, the apparatus comprising:

[0010] The execution module is used to perform behaviors that conform to the first rule during seamless roaming.

[0011] According to another aspect of this application, an execution device for a roaming process is provided, the device being used for a non-access point device, the device comprising:

[0012] Perform actions that conform to the first rule during seamless roaming.

[0013] According to another aspect of this application, a non-access point device is provided, the non-access point device comprising:

[0014] A processor; a transceiver connected to the processor; a memory for storing executable instructions of the processor; wherein the non-access point device is configured to load and execute the executable instructions to implement the execution methods for the roaming process as described above.

[0015] According to another aspect of this application, a target-side network device is provided, the target-side network device comprising:

[0016] A processor; a transceiver connected to the processor; a memory for storing executable instructions of the processor; wherein the target-side network device is configured to load and execute the executable instructions to implement the execution methods for the roaming process as described above.

[0017] According to another aspect of this application, a computer-readable storage medium is provided, wherein a computer program is stored therein, the computer program being executed by a processor to implement the above-described execution method for the roaming process.

[0018] According to another aspect of this application, a chip is provided, the chip including programmable logic circuitry and / or program instructions, which, when the chip is run on a communication device, are used to implement the above-described execution method for the roaming process.

[0019] According to another aspect of this application, a computer program product is provided, the computer program product including computer instructions stored in a computer-readable storage medium; a processor of a communication device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the communication device to implement the above-described execution method for the roaming process.

[0020] According to another aspect of this application, a computer program is provided, which is executed by a processor of a communication device to implement the above-described execution method for the roaming process.

[0021] The technical solutions provided in this application have at least the following beneficial effects:

[0022] By performing actions that conform to the first rule during seamless roaming, it is possible to ensure that non-access point devices can receive beacon frames sent by target-side network devices through the first rule. Attached Figure Description

[0023] To more clearly illustrate the technical solutions in the embodiments of this application, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0024] Figure 1 is a schematic diagram of a communication system provided in an exemplary embodiment of this application;

[0025] Figure 2 illustrates the process by which a non-access point device roams or switches from a first access point device to a second access point device, as provided in an exemplary embodiment of this application.

[0026] Figure 3 is a schematic diagram of a signaling flow provided in an exemplary embodiment of this application;

[0027] Figure 4 is a schematic diagram of a signaling flow provided in an exemplary embodiment of this application;

[0028] Figure 5 is a schematic diagram of a signaling flow provided in an exemplary embodiment of this application;

[0029] Figure 6 is a schematic diagram of a signaling flow provided in an exemplary embodiment of this application;

[0030] Figure 7 is a schematic diagram of the connection relationship between APs provided in an exemplary embodiment of this application;

[0031] Figure 8 is a schematic diagram of a process for switching the main channel provided in an exemplary embodiment of this application;

[0032] Figure 9 is a flowchart of an execution method for a roaming process provided in an exemplary embodiment of this application;

[0033] Figure 10 is a flowchart of a signaling transmission method for a roaming process provided in an exemplary embodiment of this application;

[0034] Figure 11 is a flowchart of an execution method for a roaming process provided in an exemplary embodiment of this application;

[0035] Figure 12 is a schematic diagram of the frame format of a RAR frame provided in an exemplary embodiment of this application;

[0036] Figure 13 is a schematic diagram of the frame format of an FT reassociation response frame provided in an exemplary embodiment of this application;

[0037] Figure 14 is a schematic diagram of the frame format of a RAI frame provided in an exemplary embodiment of this application;

[0038] Figure 15 is a schematic diagram of the frame format of an FT reassociation request frame provided in an exemplary embodiment of this application;

[0039] Figure 16 is a flowchart of a signaling transmission method for a roaming process provided in an exemplary embodiment of this application;

[0040] Figure 17 is a schematic diagram of a signaling flow provided in an exemplary embodiment of this application;

[0041] Figure 18 is a schematic diagram of a signaling flow provided in an exemplary embodiment of this application;

[0042] Figure 19 is a schematic diagram of a signaling flow provided in an exemplary embodiment of this application;

[0043] Figure 20 is a schematic diagram of a signaling flow provided in an exemplary embodiment of this application;

[0044] Figure 21 is a block diagram of a signaling receiving apparatus for a roaming process provided in an exemplary embodiment of this application;

[0045] Figure 22 is a block diagram of a signaling transmission apparatus for a roaming process provided in an exemplary embodiment of this application;

[0046] Figure 23 is a block diagram of a signaling transmission apparatus for a roaming process provided in an exemplary embodiment of this application;

[0047] Figure 24 is a schematic diagram of the structure of a communication device provided in one embodiment of this application. Detailed Implementation

[0048] To make the objectives, technical solutions, and advantages of this application clearer, the embodiments of this application will be further described in detail below with reference to the accompanying drawings. Exemplary embodiments will be described in detail here, examples of which are illustrated in the accompanying drawings. When the following description refers to the drawings, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with this application. Rather, they are merely examples of apparatuses and methods consistent with some aspects of this application as detailed in the appended claims. All other embodiments obtained by those skilled in the art without inventive effort in relation to the embodiments of this application are within the scope of protection of this application. The terminology used in this disclosure is for the purpose of describing particular embodiments only and is not intended to limit this disclosure. The singular forms “a,” “the,” and “the” used in this disclosure and the appended claims are also intended to include the plural forms unless the context clearly indicates otherwise. It should also be understood that the term “and / or” as used herein refers to and includes any or all possible combinations of one or more associated listed items. It should be understood that although the terms first, second, third, etc., may be used in this disclosure to describe various information, such information should not be limited to these terms. These terms are used only to distinguish information of the same type from one another. For example, without departing from the scope of this disclosure, first information may also be referred to as second information, and similarly, second information may also be referred to as first information. Depending on the context, the word “if” as used herein may be interpreted as “when”, “when”, or “in response to determination”.

[0049] Figure 1 is a schematic diagram of a communication system 10 provided in an exemplary embodiment of this application. The communication system 10 includes terminals and terminals, or terminals and network devices, or access points (APs) and stations (STAs), which are not limited in this application. In this application, the communication system 10 is illustrated using an AP 110 and a STA 120 as an example.

[0050] In some scenarios, an AP can also be called an AP STA, meaning that in a sense, an AP is also a type of STA. In other scenarios, a STA can also be called a non-AP STA.

[0051] In some embodiments, a STA may include an AP STA and a non-AP STA. Communication in the communication system can be between an AP and a non-AP STA, between two non-AP STAs, or between a STA and a peer STA. A peer STA can refer to a device communicating with the STA from the other end; for example, a peer STA may be an AP or a non-AP STA. Exemplarily, there are two communication scenarios between a STA and an AP: uplink communication and downlink communication. Uplink communication refers to the STA sending signals to the AP; downlink communication refers to the AP sending signals to the STA. An AP acts as a bridge connecting wired and wireless networks, its main function being to connect various wireless network clients together and then connect the wireless network to the Ethernet. An AP device can be a terminal device (such as a mobile phone) or a network device (such as a router) with a Wireless Fidelity (WiFi) chip.

[0052] It should be understood that the role of a STA in a communication system is not absolute. For example, in some scenarios, when a mobile phone connects to a router, it acts as a non-AP STA; when the phone serves as a hotspot for other mobile phones, it acts as an AP. APs and non-AP STAs can be devices used in vehicle-to-everything (V2X) networks, IoT nodes and sensors in the Internet of Things (IoT), smart cameras, smart remote controls, smart water and electricity meters in smart homes, and sensors in smart cities.

[0053] In some embodiments, the non-AP STA may support, but is not limited to, the 802.11bf standard. The non-AP STA may also support various current and future 802.11 family of Wireless Local Area Network (WLAN) standards, such as 802.11ax, 802.11ac, 802.11n, 802.11g, 802.11b, and 802.11a. In some embodiments, the AP may be a device that supports the 802.11bf standard. The AP may also be a device that supports various current and future 802.11 family of WLAN standards, such as 802.11ax, 802.11ac, 802.11n, 802.11g, 802.11b, and 802.11a.

[0054] In this application embodiment, the STA can be a mobile phone, tablet computer, computer, virtual reality (VR) device, augmented reality (AR) device, communication device in industrial control, set-top box, communication device in autonomous driving, vehicle communication device, communication device in telemedicine, communication device in smart grid, communication device in transportation safety, communication device in smart city, or communication device in smart home, wireless communication chip, etc. WLAN technology can support frequency bands including but not limited to: low frequency bands (2.4GHz, 5GHz, 6GHz) and high frequency bands (45GHz, 60GHz).

[0055] One or more links exist between a site and an access point. In some embodiments, the site and access point support multi-band communication, for example, communicating simultaneously on the 2.4 GHz, 5 GHz, 6 GHz, and 60 GHz bands, or simultaneously communicating on different channels within the same (or different) bands, improving communication throughput and / or reliability between devices. Such devices are commonly referred to as multi-band devices, and may also be called multi-link devices (MLDs), sometimes also called multi-link entities or multi-band entities. A multi-link device can be an access point device or a site device. If the multi-link device is an access point device, it includes one or more access points (APs); if the multi-link device is a site device, it includes one or more non-AP STAs. A multi-link device including one or more APs can also be called an AP, and a multi-link device including one or more non-AP STAs can also be called a Non-AP. In this embodiment, a Non-AP can be called a STA.

[0056] In this embodiment of the application, an AP may include multiple APs, and a Non-AP may include multiple STAs. Multiple links may be formed between the multiple APs in the AP and the multiple STAs in the Non-AP. Data communication may be performed between the APs in the AP and the corresponding STAs in the Non-AP through the corresponding links.

[0057] An AP is a device deployed in a wireless local area network to provide wireless communication functions for a STA. A STA may include: User Equipment (UE), access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, wireless communication equipment, user agent, or user device. Optionally, a STA may also be a cellular phone, cordless phone, Session Initiation Protocol (SIP) phone, Wireless Local Loop (WLL) station, Personal Digital Assistant (PDA), handheld device with wireless communication functions, computing device, or other processing device connected to a wireless modem, vehicle-mounted device, or wearable device. This application embodiment does not limit the scope of the application.

[0058] In the embodiments of this application, both STA and AP support the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standard, but are not limited to the IEEE 802.11 standard.

[0059] The following is an introduction to NPCA:

[0060] Primary Channel: This refers to the channel shared by all member stations in the basic service set (BSS). For example, in a BSS corresponding to 20MHz, 40MHz, 80MHz, 160MHz, or 80+80MHz, the primary channel is a main 20MHz channel.

[0061] Nonprimary channel: refers to any 20MHz channel other than the primary 20MHz channel within a 40MHz, 80MHz, 160MHz, or 80+80MHz basic service set (BSS).

[0062] Primary 20MHz Channel: This refers to the 20MHz channel used to transmit 20MHz physical layer (PHY) protocol data units (PPDUs) within a basic service set (BSS) of 20MHz, 40MHz, 80MHz, 160MHz, or 80+80MHz.

[0063] The primary 40MHz channel is a 40MHz channel used to transmit 40MHz physical layer (PHY) protocol data units (PPDUs) within an 80MHz, 160MHz, or 80+80MHz basic service set (BSS).

[0064] Primary 80MHz Channel: Within a 160MHz or 80+80MHz basic service set (BSS), this 80MHz channel is used to transmit 80MHz physical layer (PHY) protocol data units (PPDUs).

[0065] Primary 160MHz Channel: Within a 320MHz basic service set (BSS), this is the 160MHz channel that includes the primary 20MHz channel.

[0066] Sometimes the aforementioned main 20MHz channel, main 40MHz channel, main 80MHz channel, and main 160MHz channel are collectively referred to as the main channel.

[0067] A secondary channel is a channel associated with a primary channel and used to create a channel wider than the primary channel. In a 40MHz, 80MHz, 160MHz, or 80+80MHz basic service set (BSS), the secondary channel is a secondary 20MHz channel.

[0068] Secondary 20MHz Channel: In the 40MHz very high throughput basic service set, the 20MHz channel adjacent to the primary 20MHz channel together forms the 40MHz channel corresponding to the 40MHz very high throughput basic service set. In the 80MHz very high throughput basic service set, the 20MHz channel adjacent to the primary 20MHz channel together forms the primary 40MHz channel corresponding to the 80MHz very high throughput basic service set. In the 160MHz or 80+80MHz very high throughput basic service set, the 20MHz channel adjacent to the primary 20MHz channel together forms the primary 40MHz channel corresponding to the 160MHz or 80+80MHz very high throughput basic service set. (In a 40MHz very high throughput(VHT)basic service set(BSS), the 20MHz channel adjacent to the primary 20MHz channel that together form the 40MHz channel of the 40MHz VHT BSS.In an 80MHz VHT BSS, the 20MHz channel adjacent to the primary 20MHz channel that together form the primary 40MHz channel of the 80MHz VHT BSS.In a 160MHz or 80+80MHz VHT BSS, the 20MHz channel adjacent to the primary 20MHz channel that together form the primary 40MHz channel of the 160MHz or 80+80MHz VHT BSS.In a VHT BSS, the secondary 20MHz channel is also the secondary channel.)

[0069] The secondary 40MHz channel: In an 80MHz very high throughput (VHT) basic service set (BSS), the 40MHz channel adjacent to the primary 40MHz channel together forms the 80MHz channel of the 80MHz VHT BSS. In a 160MHz or 80+80MHz VHT BSS, the 40MHz channel adjacent to the primary 40MHz channel together forms the primary 80MHz channel.

[0070] Secondary 80MHz Channel: In a 160MHz or 80+80MHz very high throughput (VHT) basic service set (BSS), the 80MHz channel, excluding the primary 20MHz channel, together with the primary 80MHz channel, forms the 160MHz or 80+80MHz channel corresponding to the 160MHz or 80+80MHz VHT BSS.

[0071] The Secondary 160MHz Channel: Within a 320MHz basic service set (BSS), the 160MHz channel, excluding the primary 20MHz channel, together with the primary 160MHz channel, forms the 320MHz channel corresponding to the 320MHz extremely high throughput (EHT) BSS.

[0072] Sometimes the aforementioned 20MHz, 40MHz, 80MHz, and 160MHz channels are collectively referred to as secondary channels.

[0073] Operating Channel: This refers to the channel used to transmit beacon frames. It can be a collection of multiple channels used during operation. Specific examples include 20MHz, 40MHz, 80MHz, 160MHz, or 320MHz operating channels.

[0074] Operating Channel Width: This refers to the bandwidth of the channel through which the station (STA) is currently able to receive signals. Examples include 20MHz, 40MHz, 80MHz, 160MHz, or 320MHz.

[0075] Anchor Channel: Also known as Non-Primary Channel Access (NPCA) Primary Channel, Second Primary Channel, Temporary Primary Channel, Assistant Primary Channel, Auxiliary Primary Channel, or Target Subchannel. A subchannel within the current operating channel of the basic service set, used as the primary channel when the access point and associated site perform non-primary channel access. Specifically, assuming the access point's current operating channel bandwidth is 160MHz, the subchannels include: Primary 80MHz (P80, including Primary 20MHz (P20), Secondary 20MHz (S20), Secondary 40MHz (S40, including S20-1, S20-2)), and Secondary 80MHz (S80, including S20-3, S20-4, S20-5, S20-6). Optionally, when performing non-master channel access, S20-3 can be used as P20, S20-4 as S20, S20-5 and S20-6 as S40, and P80 as S80.

[0076] The following is an introduction to roaming:

[0077] Roaming refers to the process of a non-access point device migrating from its currently associated first access point device to a second access point device. Alternatively, it can be understood as the process of migrating from its currently associated source access point device to a target access point device. The source access point device is also known as the current access point device.

[0078] In some embodiments, non-access point devices include non-access point single-site devices (non-AP STA) or non-access point multi-link devices (non-AP MLD).

[0079] In some embodiments, the first access point device includes a first access point single-site device or a first access point multi-link device. Alternatively, the first access point device is a source access point device, including a source access point single-site device or a source access point multi-link device. Alternatively, the first access point device is a current access point device, including a current access point single-site device or a current access point multi-link device.

[0080] In some embodiments, the second access point device includes a second access point single-site device or a second access point multi-link device. Alternatively, the second access point device is a target access point device, including a target access point single-site device or a target access point multi-link device.

[0081] In some embodiments, the first access point device and the second access point device belong to the same Extended Service Set (ESS), or the same Seamless Roaming Domain (SMD), or the same Roaming AP MLD.

[0082] In this embodiment, the non-access point device is described as a non-access point multi-link device, the first access point device is the source access point multi-link device, and the second access point device is the target access point multi-link device. Referring to Figure 2, the process of a non-access point device roaming or switching from the first access point device to the second access point device is illustrated. In some embodiments, before the non-access point device decides to initiate roaming, it associates / connects with the first access point device. Uplink and downlink data transmission can occur between the non-access point device and the first access point device, and uplink and downlink data transmission can occur between the first access point device and the distribution system (DS).

[0083] In some embodiments, the non-access point device decides whether to initiate roaming or handover. When the non-access point device decides to initiate roaming or handover, step 1 is performed.

[0084] Further, the non-access point device performs step 2, sending a roaming preparation request frame to notify either the first or second access point device that the non-access point device is about to roam. The roaming preparation request frame carries one or more candidate AP MLDs. The one or more candidate AP MLDs include the second access point device.

[0085] Furthermore, after receiving the roaming preparation request frame sent by the non-access point device, the first access point device may optionally select a second access point device from one or more candidate AP MLDs, and may optionally execute step 3 to migrate data communication context information (such as BA protocol negotiation parameters) to the second access point device.

[0086] Further, the first access point device or the second access point device executes step 4, sending a roaming preparation response frame to the non-access point device to notify the non-access point device of: the second access point device, the roaming or handover request timeout parameters, the BA protocol negotiation parameter migration status, etc.

[0087] Further, the non-access point device executes step 5, sending a roaming request frame to the first access point device or the second access point device to initiate a roaming request.

[0088] Further, after the non-access point device (NAP) completes its roaming, i.e., after migrating from the first access point device to the second access point device, the second access point device executes step 6, sending a roaming response frame to the NAP. Optionally, this roaming response frame is used to instruct the NAP to prepare to send a Class 3 frame to the second access point device. Upon receiving this roaming response frame, the NAP can send a Class 3 frame to the second access point device. Class 3 frames refer to three types of frames: data frames, management frames, and control frames. In some embodiments, during the period between the NAP sending the roaming request frame and receiving the roaming response frame, the migration of data communication context information (such as BA protocol negotiation parameters and / or BA protocol control and status parameters) may also be optionally performed.

[0089] In some embodiments, after the non-access point device (NAP) finishes roaming, it associates / connects with the second access point device. Uplink and downlink data transmission are possible between the NAP and the second access point device, and uplink and downlink data transmission are also possible between the second access point device and the DS.

[0090] The following describes the signaling flow for seamless roaming based on a non-collocated AP MLD:

[0091] For example, the signaling flow for seamless roaming based on a non-co-located AP MLD mainly includes:

[0092] • The source AP, target AP, and controller communicate via backhaul;

[0093] • Context can be transmitted from the source AP to the target AP via backhaul;

[0094] There is no data forwarding between APs;

[0095] • AP1 (source AP) and AP2 (destination AP) can be extended to AP MLD1 and AP MLD2 in the call flow;

[0096] •STA and non-AP MLD are synonyms in the call flow.

[0097] The contexts that can be migrated between APs include:

[0098] • Information about the Sequence Number (SN) (per-TID);

[0099] • Information about the Packet Number (PN).

[0100] For example, the signaling flow is shown in Figure 3 when a non-AP STA can communicate with multiple non-co-located AP MLDs during roaming. The signaling flow is shown in Figure 4 when a non-AP STA can communicate with only one non-co-located AP MLD at a time during roaming. The signaling flow is shown in Figure 5 when a non-AP STA can communicate with only one non-co-located AP MLD at a time during roaming, but immediately switches to the target AP without context transition after sending a Roaming Announcement Indicator (RAI) frame.

[0101] The following section introduces the seamless roaming architecture based on hot association via the Distribution System (DS) (over-the-DS):

[0102] A Data Controller (DS) is a system used to interconnect a set of Basic Service Sets (BSSs) and integrated Local Area Networks (LANs) to create Extended Service Sets (ESSs). The primary function of a DS is to connect different BSSs, allowing communication devices between different BSSs to communicate. For example, by connecting BSS1 and BSS2, data in BSS1 and BSS2 can be forwarded to each other. In some embodiments, each BSS includes one or more communication devices; for example, BSS1 includes site 1 (STA1) and site 2 (STA2), and BSS2 includes site 3 (STA3) and site 4 (STA4). Exemplarily, a DS can be used to forward data from site 2 (STA2) to site 3 (STA3), or vice versa.

[0103] For example, the signaling flow for seamless roaming based on over-the-DS hot backup association mainly includes:

[0104] • Non-AP MLDs exchange Fast Transition (FT) probe request / response frames with the current AP MLD to obtain information about neighboring AP MLDs;

[0105] • Non-AP MLDs exchange FT reassociation request / response frames with the current AP MLD to perform hot backup association with neighboring AP MLDs.

[0106] For example, the signaling flow for seamless roaming based on over-the-DS hot backup association is shown in Figure 6. As shown in Figure 7, the current AP MLD701 and the neighboring AP MLD702 are connected via DS703.

[0107] The following is an introduction to Ultra High Reliability (UHR) Secondary Channel Access:

[0108] Secondary channel access allows a station to transmit only on the secondary channel after detecting that the primary channel is busy. For example, the main features of secondary channel access include:

[0109] AP behavior (transmitter):

[0110] • Monitor the medium idle / busy status on the second primary channel (P2):

[0111] Clear Channel Assessment (CCA) based on Energy Detection (ED) / Packet Detection (PD): for example, Short Training Field (STF) detection.

[0112] • If the first primary channel (P1) is busy for the duration of the Network Allocation Vector (NAV), while the second primary channel is idle for the duration of X:

[0113] On the second primary channel, the AP will back off and initiate a Transmission Opportunity (TXOP) to the target STA using a Buffer Status Report Poll (BSRP) trigger or a Request To Send (RTS) frame (control frame). During this process, control frame exchanges of RTS / Clear To Send (CTS) or BSRP / BSR type are required to determine whether the target STA is on the second primary channel.

[0114] STA behavior (receiver):

[0115] • If the first primary channel is busy during the NAV duration:

[0116] The STA will move to the second primary channel and wait for a BSRP or RTS (control frame) from the AP. The STA will return to the first primary channel before NAV=0.

[0117] The first primary channel mentioned above is a channel shared by all member sites in the Basic Service Set (BSS). For example, in the BSS corresponding to 20MHz, 40MHz, 80MHz, 160MHz, or 80+80MHz, the primary channel is a main 20MHz channel. The second primary channel mentioned above can be called the Non-Primary Channel Access (NPCA) primary channel. The NPCA primary channel is the primary channel used when the access point and associated site perform non-primary channel access. The NPCA primary channel can also be called the NPCA anchor channel. For example, Figure 8 is a schematic diagram of the process of switching primary channels provided by an exemplary embodiment of this application. As shown in Figure 8, the STA initially communicates with the AP on the first primary channel with a bandwidth of 40MHz. The STA initially communicates with the AP on the AP's first primary channel with a channel bandwidth of 40MHz. Later, due to the first primary channel being busy, the STA will move to the AP's second primary channel to communicate with the AP with a channel bandwidth of 40MHz.

[0118] As described above, during roaming, the target network device may be located on the NPCA primary channel (the second primary channel) instead of the primary channel (the first primary channel). The target network device being on a particular channel means that it is receiving and / or transmitting frames on that channel. In this case, if the non-access point device defaults to accessing the target network device's primary channel instead of the NPCA primary channel after roaming, the non-access point device will be unable to communicate with the target network device immediately due to the different channel it accesses, thus affecting the latency performance of seamless roaming.

[0119] The method provided in this application, by providing first information to a non-access point device (NAPD) during roaming, assists the NAPD in determining the primary channel for communication with the target network device, thereby facilitating the NAPD's access to the primary channel of the target network device. This enables the NAPD to quickly establish an association and exchange frames with the target network device during roaming, reducing time wasted due to channel mismatch and thus decreasing roaming latency, ultimately improving the user's roaming experience.

[0120] Figure 9 is a flowchart of an execution method for a roaming process provided in an exemplary embodiment of this application. This method can be executed by a non-access point device. Optionally, the non-access point device in this embodiment includes a non-access point site device or a non-access point site multilink device. The method includes:

[0121] Step 902: Execute the behavior that conforms to the first rule during seamless roaming.

[0122] A non-access point device receives a first signaling message sent by a network device. The first signaling message carries first information about the target network device, which assists the non-access point device in determining the primary channel for communication with the target network device. In some embodiments, the first information assists the non-access point device in determining the primary channel on which the target network device is located, including the primary channel on which the target network device receives and / or transmits frames. In some embodiments, the first information assists the non-access point device in determining the primary channel on which the target network device operates. In some embodiments, the first information assists the non-access point device in determining the primary channel it accesses within the primary channel of the target network device. In some embodiments, the first information is determined by the target network device.

[0123] In some embodiments, the target-side network device corresponds to at least two main channels; for example, the target-side network device corresponds to two main channels. In some embodiments, the main channels of the target-side network device include: a first main channel; and a second main channel. The first main channel and the second main channel are different main channels.

[0124] In some embodiments, the first primary channel includes a common operating channel / channel for all non-access point devices in the BSS of the target-side network device. In some embodiments, the first primary channel is a channel shared by all member sites in the BSS of the target-side network device. For example, in the basic service set corresponding to 20MHz, 40MHz, 80MHz, 160MHz, or 80+80MHz, the first primary channel is a primary 20MHz channel. In some embodiments, the first primary channel may be referred to as the first primary channel. In some embodiments, the second primary channel includes the NPCA primary channel. In some embodiments, the NPCA primary channel is the primary channel used when a non-access point device accesses a non-primary channel. In some embodiments, the second primary channel may be referred to as the second primary channel or the NPCA anchor channel.

[0125] In some embodiments, the first signaling is equivalent to / can be replaced by NPCA status request signaling, and the first information is equivalent to / can be replaced by NPCA status information. The first information is used to indicate the NPCA status of the target-side network device.

[0126] In some embodiments, the first signaling is sent by the source-side network device. In some embodiments, the first signaling is sent by the target-side network device. In some embodiments, in non-collocated seamless roaming scenarios, the first signaling can be sent by either the source-side network device or the target-side network device. For example, during roaming, if the non-access point device maintains a link connection with only one non-collocated network device at the same time, the first signaling is sent by the source-side network device; if the non-access point device maintains a link connection with two or more non-collocated network devices at the same time, the first signaling is sent by the source-side network device; if the non-access point device maintains a link connection with only one non-collocated network device at the same time, and the non-access point device immediately switches to the target-side network device after sending the RAI without performing a context transition, the first signaling is sent by the target-side network device. In some embodiments, in seamless roaming scenarios hot-associated through a Distribution System (DS), the first signaling is sent by the source-side network device.

[0127] In some embodiments, the target-side network device can also be understood as a target access point device. A target access point device includes a target access point site device or a target access point site multi-link device. In some embodiments, the aforementioned non-access point device includes a non-access point site device, the source-side network device includes a source access point site device, and the target-side network device includes a target access point site device. In some embodiments, the aforementioned non-access point device includes a non-access point site device, the source-side network device includes a source access point site device, and the target-side network device includes a target access point site multi-link device. In some embodiments, the aforementioned non-access point device includes a non-access point site device, the source-side network device includes a source access point site multi-link device, and the target-side network device includes a target access point site device. In some embodiments, the aforementioned non-access point device includes a non-access point site device, the source-side network device includes a source access point site multi-link device, and the target-side network device includes a target access point site multi-link device. In some embodiments, the aforementioned non-access point device includes a non-access point site multi-link device, the source-side network device includes a source access point site device, and the target-side network device includes a target access point site device. In some embodiments, the aforementioned non-access point device includes a non-access point site multi-link device, the source-side network device includes a source access point site device, and the target-side network device includes a target access point site multi-link device. In some embodiments, the aforementioned non-access point device includes a non-access point site multi-link device, the source-side network device includes a source access point site multi-link device, and the target-side network device includes a target access point site device. In some embodiments, the aforementioned non-access point device includes a non-access point site multi-link device, the source-side network device includes a source access point site multi-link device, and the target-side network device includes a target access point site multi-link device.

[0128] In some embodiments, the first information includes one or more of the following: dwell channel; main channel busy time; dwell time; main channel bandwidth; main channel timeout time; timestamp.

[0129] A dwell channel is used to indicate the primary channel on which the target network device is located. For example, a dwell channel is used to indicate that the target network device is located on a first primary channel or a second primary channel. In some embodiments, a dwell channel is used to indicate the primary channel on which the target network device is located at the time of sending / receiving the first signaling and / or at the current time. In some embodiments, a dwell channel is used to indicate the primary channel on which the target network device is located at the time indicated by the timestamp. In some embodiments, the timestamp is used to indicate the time when the first information was generated, such as the Timing Synchronization Function (TSF) time. In some embodiments, a dwell channel may be referred to as a Channel.

[0130] The primary channel busy time is used to indicate the duration of continuous busy activity on the primary channel of the target-side network device, such as the NAV value set by the target-side network device on the primary channel. In some embodiments, the dwell channel is used to indicate the duration of continuous busy activity on the primary channel of the target-side network device from the time of sending / receiving the first signaling and / or the current time. In some embodiments, the primary channel busy time is used to indicate the duration of continuous busy activity on the primary channel from the time indicated by the timestamp. In some embodiments, the timestamp is used to indicate the time when the first information was generated, such as the TSF time. In some embodiments, the primary channel busy time may be referred to as the Primary Channel NAV.

[0131] The dwell time is used to indicate the duration of time the target network device remains on the primary channel indicated by the dwell channel. In some embodiments, the dwell time indicates the duration of time the target network device remains on the primary channel indicated by the dwell channel, starting from the time of sending / receiving the first signaling and / or the current time. In some embodiments, the dwell time indicates the duration of time the target network device remains on the primary channel indicated by the dwell channel, starting from the time indicated by the timestamp. In some embodiments, the timestamp indicates the time when the first information is generated. In some embodiments, the dwell duration indicated by the dwell time includes one or more of a single dwell duration (a time range) and periodic multiple dwell durations (periodic multiple time ranges). In some embodiments, the timestamp indicates the time when the first information is generated, for example, the TSF time. In some embodiments, the dwell time may be referred to as Dwell Time.

[0132] The primary channel bandwidth is used to indicate the bandwidth transmitted on the secondary primary channel of the target-side network device. In some embodiments, the bandwidth indicated by the primary channel bandwidth includes the bandwidth for transmitting Physical Layer Protocol Data Units (PPDUs) and / or receiving PPDUs. In some embodiments, the primary channel bandwidth is used to indicate the maximum bandwidth transmitted on the secondary primary channel of the target-side network device within the continuous busy duration indicated by the primary channel busy time, starting from the time of transmitting / receiving the first signaling and / or the current time. In some embodiments, the primary channel bandwidth is used to indicate the maximum bandwidth transmitted on the secondary primary channel within the continuous busy duration indicated by the primary channel busy time, starting from the time indicated by the timestamp. In some embodiments, the timestamp is used to indicate the time when the first information was generated, such as the TSF time. In some embodiments, the primary channel bandwidth may be referred to as NPCA Channel Max BW.

[0133] The primary channel timeout period indicates the maximum listening duration of a non-access point device (NAPD) on the target network device's second primary channel after roaming. In some embodiments, the primary channel timeout period indicates the maximum listening duration of the NAPD immediately after roaming on the target network device's second primary channel. In some embodiments, if the NAPD fails to communicate successfully with the target network device within the maximum listening duration indicated by the primary channel timeout period, the NAPD will switch to the target network device's first primary channel. In some embodiments, the primary channel timeout period may be referred to as the NPCA Channel Timeout.

[0134] In some embodiments, the dwell channel is used to indicate that the target AP MLD / AP is located on the first primary channel or the NPCA primary channel (second primary channel). The primary channel busy time is used to indicate the continuous busy time of the target AP MLD / AP's first primary channel, i.e., the NAV of the first primary channel detected by the target AP MLD / AP. The dwell time is used to indicate the dwell time of the target AP MLD / AP on the first primary channel or the NPCA primary channel; it can indicate a time range starting from the current moment, a future time range, or multiple periodic time ranges in the future. The maximum NPCA primary channel bandwidth is used to indicate the maximum bandwidth by which the target AP MLD / AP transmits or receives PPDUs on the NPCA primary channel. The NPCA primary channel timeout is used to indicate the maximum duration for which a Non-AP MLD / Non-AP STA has continuously failed to successfully exchange frames with the target AP MLD / AP on the target AP MLD / AP's NPCA primary channel; after this duration, the Non-AP MLD / Non-AP STA should / must return to the target AP MLD / AP's first primary channel. The timestamp is used to indicate the local synchronization time of the target AP MLD / AP when at least one of the four NPCA status information is generated: the target AP MLD / AP generates the stationary channel, the main channel busy time, the maximum NPCA main channel bandwidth, and the NPCA main channel timeout time.

[0135] In some embodiments, the non-access point device (NAPD) determines the primary channel indicated by the dwell channel as the primary channel for communication with the target network device. In some embodiments, if the current time falls within the continuous busy duration indicated by the primary channel busy time, the NAPD determines the second primary channel of the target network device as the primary channel for communication with the target network device. In some embodiments, if the current time falls within the dwell time indicated by the dwell time, the NAPD determines the primary channel indicated by the dwell channel as the primary channel for communication with the target network device. In some embodiments, if the bandwidth transmitted on the second primary channel indicated by the primary channel bandwidth meets the transmission requirements of the NAPD, the NAPD determines the second primary channel of the target network device as the primary channel for communication with the target network device. In some embodiments, if the time difference between the current time and the time indicated by the timestamp is greater than a time difference threshold, the NAPD will not use the first information to determine the primary channel for communication with the target network device. It should be noted that the above conditions can be used individually or in combination, and this application embodiment does not impose any restrictions on this.

[0136] In some embodiments, the first signaling includes a first action frame. In some embodiments, the first action frame includes a first field for carrying first information. In some embodiments, the frame body of the first action frame includes the first field. In some embodiments, the first action frame includes one or more of the following action frames: a Roaming Announcement Response (RAR) frame; a Fast Transition (FT) Reassociation Response frame. In some embodiments, in non-co-located seamless roaming scenarios, the first signaling includes a RAR frame. In seamless roaming scenarios via DS hot associativity, the first signaling includes an FT reassociation response frame.

[0137] In some embodiments, the first signaling is actively sent by the source-side network device or the target-side network device to the non-access point device. In some embodiments, the first signaling is sent by the source-side network device or the target-side network device to the non-access point device when the non-access point device requests first information. In this case, the non-access point device sends a second signaling to the source-side network device, the second signaling being used to request the first information. In some embodiments, when the source-side network device sends the first signaling to the non-access point device, upon receiving the second signaling, the source-side network device obtains the first information through the target-side network device, i.e., receives the first information sent by the target-side network device, and then sends the first signaling to the non-access point device accordingly. In some embodiments, when the target-side network device sends the first signaling to the non-access point device, upon receiving the second signaling, the source-side network device notifies the target-side network device that the non-access point device requests the first information, thereby causing the target-side network device to send the first signaling.

[0138] In some embodiments, the second signaling includes a second action frame. In some embodiments, the second action frame includes a second field indicating a request for first information. In some embodiments, the frame body of the second action frame includes the second field. In some embodiments, the second action frame includes one or more of the following action frames: a Roaming Announcement Indicator (RAI) frame; and an FT Reassociation Request frame. In some embodiments, in non-co-located seamless roaming scenarios, the second signaling includes a RAI frame. In seamless roaming scenarios via DS hot association, the second signaling includes an FT Reassociation Request frame.

[0139] When a non-access point device (NAP) seamlessly roams to access a target network device using the methods described above, there may be instances where the NAP fails to receive beacon frames sent by the target network device, thus preventing the NAP from measuring Received Signal Strength Indication (RSSI). For example, the NAP accesses the target network device's NPCA main channel, while the target network device sends beacon frames on its BSS main channel. To address this, in some embodiments, during seamless roaming, the NAP performs actions conforming to a first rule. Performing actions conforming to the first rule includes receiving beacon frames sent by the target network device during or within a portion of the seamless roaming process; suspending, or being required to suspend, or should suspending, or suspending NPCA functionality on the link where seamless roaming occurs, during a portion of the seamless roaming process; and establishing at least one of two or more links with the target network device during seamless roaming.

[0140] In some embodiments, the beacon frames received by the non-access point device satisfy at least one of the following conditions: they use, must use, or should use the Non-High Throughput (Non-HT) Duplicated Physical Layer Protocol Data Unit (PPDU) format; the bandwidth of the beacon frame is the total operating bandwidth of the BSS associated with the target network device; and the bandwidth of the beacon frame includes the BSS main channel and NPCA main channel of the target network device. In some embodiments, beacon frames transmitted by the target network device during a portion of the time range of the seamless roaming process satisfy at least one condition.

[0141] Since non-access point devices (NADs) typically measure RSSI based on beacon frames sent by network devices (e.g., APs) to determine roaming conditions, if the beacon frames sent by the target network device only occupy the BSS primary channel and not the NPCA primary channel, then when the NAD switches to the NPCA primary channel, it will not be able to receive the beacon frames sent by the target network device, thus preventing RSSI measurement. The aforementioned rule requires that the beacon frames sent by the target network device occupy both the BSS and NPCA primary channels. This has the advantage that regardless of which primary channel the NAD is on, it can receive the beacon frames through at least one 20MHz bandwidth or channel, thereby identifying the sender of the beacon frame and enabling RSSI measurement.

[0142] In some embodiments, the start time of the aforementioned partial time range includes at least one of the following: the successful transmission time of the roaming preparation request frame; the successful transmission time of the immediate response frame to the roaming preparation request frame; the successful transmission time of the roaming preparation response frame; the successful transmission time of the immediate response frame to the roaming preparation response frame; and the start time of context transmission. The end time of the aforementioned partial time range includes at least one of the following: the successful transmission time of the roaming request frame; the successful transmission time of the immediate response frame to the roaming request frame; the successful transmission time of the roaming response frame; and the successful transmission time of the immediate response frame to the roaming response frame.

[0143] For example, the aforementioned partial time range includes at least one of the following: the time range between the successful transmission time of the roaming preparation request frame or the immediate response frame of the roaming preparation request frame and the successful transmission time of the roaming request frame or the immediate response frame of the roaming request frame; the time range between the successful transmission time of the roaming preparation request frame or the immediate response frame of the roaming preparation request frame and the successful transmission time of the roaming response frame or the immediate response frame of the roaming response frame; the time range between the successful transmission time of the roaming preparation request frame or the immediate response frame of the roaming preparation request frame and the successful transmission time of the roaming request frame or the immediate response frame of the roaming request frame; the time range between the start time of the context transfer and the successful transmission time of the roaming request frame or the immediate response frame of the roaming request frame; and the time range between the start time of the context transfer and the successful transmission time of the roaming response frame or the immediate response frame of the roaming response frame.

[0144] In some embodiments, the roaming preparation request frame is sent by the non-access point device (NAPD) to the source network device. The roaming preparation request frame is used to initialize the seamless roaming process between the NAPD and the target network device. In some embodiments, the roaming preparation request frame is used for at least one of the following in the seamless roaming process: link initialization, link capability information notification, key initialization, and semi-static context transmission initialization. In some embodiments, the roaming preparation response frame is sent by the source network device to the NAPD. The roaming preparation response frame is used to indicate that seamless roaming initialization has been completed. In some embodiments, the roaming request frame is sent by the NAPD to the target network device. The roaming request frame is used to request at least one of link activation, identity verification, and dynamic context transmission. In some embodiments, the roaming response frame is sent by the target network device to the NAPD. The roaming response frame is used to indicate at least one of link activation status and key transmission.

[0145] By suspending the NPCA function of the target-side network devices and non-access point devices for a portion of the time during seamless roaming, the target-side network devices and non-access point devices can operate on the same primary channel during that portion of the time, thus avoiding the two sites being on different primary channels.

[0146] In some embodiments, the non-access point device (NAPD) establishes two or more links with the target network device during seamless roaming, including at least one link corresponding to the BSS primary channel and at least one link corresponding to the NPCA primary channel. By establishing two or more links, the NAPD and the target network device can obtain more transmission opportunities to transmit roaming-related signaling, thereby reducing roaming latency. Simultaneously, by pre-establishing multiple links between the target network device and the NAPD, the probability that the NAPD will obtain a transmission opportunity (TXOP) on at least one link can be increased, enabling timely transmission of roaming-related signaling.

[0147] In some embodiments, the establishment of two or more links between the non-access point device and the target network device is requested by the non-access point device. In this case, the non-access point device sends a first request to the target network device, which requests the establishment of two or more links with the target network device.

[0148] It should be noted that the process by which a non-access point device performs behavior conforming to the first rule can be implemented as an independent embodiment, or it can be implemented in conjunction with other content provided in the embodiments of this application. The embodiments of this application do not impose any restrictions on this. Furthermore, each of the three ways in which a non-access point device performs behavior conforming to the first rule can also be implemented as an independent embodiment. The embodiments of this application do not impose any restrictions on this.

[0149] In summary, the method provided in this embodiment, by providing first information to the non-access point device (NAPD) during roaming, assists the NAPD in determining the primary channel for communication with the target network device, thereby helping the NAPD access the primary channel of the target network device. This enables the NAPD to quickly establish an association and exchange frames with the target network device during roaming, reducing time wasted due to channel mismatch and thus reducing latency during roaming, ultimately improving the user's roaming experience.

[0150] The method provided in this embodiment also assists the non-access point device (NAPD) in determining whether to access the target network device's NPCA main channel through first information. This enables the NAPD to communicate with the target network device on the NPCA main channel when the target network device is located there. The dwell channel in the first information indicates the main channel on which the target network device is located, facilitating communication between the NAPD and the target network device on the target network device's current main channel. The main channel busy time in the first information indicates the duration of continuous busy activity on the first main channel, helping the NAPD to understand the busy status of the first main channel before communicating with the target network device. The dwell time in the first information indicates the dwell time of the target network device on the current main channel, helping the NAPD to understand the future channel dwell status of the target network device before communicating with it. The main channel bandwidth in the first information indicates the transmission bandwidth of the second main channel, helping the NAPD to understand whether the second main channel meets transmission requirements before communicating with the target network device. The primary channel timeout time in the first message indicates the maximum listening time on the secondary primary channel, enabling non-access point devices to switch channels promptly when they cannot listen to the secondary primary channel. The timestamp in the first message allows non-access point devices to ascertain the validity of the first message. Sending the first signaling via either the source-side network device or the target-side network device is suitable for different application scenarios. Sending the second signaling allows non-access point devices to request the first message on demand.

[0151] Figure 10 is a flowchart of a signaling transmission method for a roaming process provided in an exemplary embodiment of this application. This method can be executed by a source-side network device. Optionally, the source-side network device in this embodiment can also be understood as a source access point device, which includes a source access point site device or a source access point site multi-link device. The method includes:

[0152] Step 1002: Send the first signaling to the non-access point device.

[0153] The first signaling carries first information about the target-side network device. This first information is used to assist the non-access point device in determining the primary channel for communication with the target-side network device. For a detailed description of the first signaling, please refer to the relevant content in other embodiments of this application.

[0154] In summary, the method provided in this embodiment, by providing first information to the non-access point device (NAPD) during roaming, assists the NAPD in determining the primary channel for communication with the target network device, thereby helping the NAPD access the primary channel of the target network device. This enables the NAPD to quickly establish an association and exchange frames with the target network device during roaming, reducing time wasted due to channel mismatch and thus reducing latency during roaming, ultimately improving the user's roaming experience.

[0155] Figure 11 is a flowchart of an execution method for a roaming process provided in an exemplary embodiment of this application. This method can be executed by a target-side network device. Optionally, the target-side network device in this embodiment can also be understood as a target access point device. The target access point device includes a target access point site device or a target access point site multi-link device. The method includes:

[0156] Step 1102: Execute the behavior that conforms to the first rule during seamless roaming.

[0157] The target network device sends a first signaling message to the non-access point device. This first signaling message carries first information about the target network device, which assists the non-access point device in determining the primary channel for communication with the target network device. For a detailed description of the first signaling message, please refer to the relevant content in other embodiments of this application.

[0158] When a non-access point device (NAP) seamlessly roams to access a target network device using the methods described above, there may be instances where the NAP fails to receive beacon frames sent by the target network device, thus preventing the NAP from measuring RSSI. For example, the NAP accesses the target network device's NPCA main channel, while the target network device sends beacon frames on its BSS main channel. To address this, in some embodiments, during seamless roaming, the target network device performs actions conforming to a first rule. Performing actions conforming to the first rule includes sending beacon frames during or within a portion of the seamless roaming process; suspending, or being required to suspend, or should suspending, or suspending NPCA functionality on the link where seamless roaming occurs, within a portion of the seamless roaming process; and establishing at least one of two or more links with the NAP during seamless roaming.

[0159] In some embodiments, the beacon frames sent by the target-side network device satisfy at least one of the following conditions: they use, must use, or should use the Non-HT Duplicated PPDU format; the bandwidth of the beacon frame is the total operating bandwidth of the BSS associated with the target-side network device; and the bandwidth of the beacon frame includes the BSS main channel and the NPCA main channel of the target-side network device. In some embodiments, the beacon frames sent by the target-side network device during a portion of the time range of the seamless roaming process satisfy at least one condition.

[0160] In some embodiments, the start time of the aforementioned partial time range includes at least one of the following: the successful transmission time of the roaming preparation request frame; the successful transmission time of the immediate response frame to the roaming preparation request frame; the successful transmission time of the roaming preparation response frame; the successful transmission time of the immediate response frame to the roaming preparation response frame; and the start time of context transmission. The end time of the aforementioned partial time range includes at least one of the following: the successful transmission time of the roaming request frame; the successful transmission time of the immediate response frame to the roaming request frame; the successful transmission time of the roaming response frame; and the successful transmission time of the immediate response frame to the roaming response frame.

[0161] For example, the aforementioned partial time range includes at least one of the following: the time range between the successful transmission time of the roaming preparation request frame or the immediate response frame of the roaming preparation request frame and the successful transmission time of the roaming request frame or the immediate response frame of the roaming request frame; the time range between the successful transmission time of the roaming preparation request frame or the immediate response frame of the roaming preparation request frame and the successful transmission time of the roaming response frame or the immediate response frame of the roaming response frame; the time range between the successful transmission time of the roaming preparation request frame or the immediate response frame of the roaming preparation request frame and the successful transmission time of the roaming request frame or the immediate response frame of the roaming request frame; the time range between the start time of the context transfer and the successful transmission time of the roaming request frame or the immediate response frame of the roaming request frame; and the time range between the start time of the context transfer and the successful transmission time of the roaming response frame or the immediate response frame of the roaming response frame.

[0162] In some embodiments, the roaming preparation request frame is sent by the non-access point device (NAPD) to the source network device. The roaming preparation request frame is used to initialize the seamless roaming process between the NAPD and the target network device. In some embodiments, the roaming preparation request frame is used for at least one of the following in the seamless roaming process: link initialization, link capability information notification, key initialization, and semi-static context transmission initialization. In some embodiments, the roaming preparation response frame is sent by the source network device to the NAPD. The roaming preparation response frame is used to indicate that seamless roaming initialization has been completed. In some embodiments, the roaming request frame is sent by the NAPD to the target network device. The roaming request frame is used to request at least one of link activation, identity verification, and dynamic context transmission. In some embodiments, the roaming response frame is sent by the target network device to the NAPD. The roaming response frame is used to indicate at least one of link activation status and key transmission.

[0163] In some embodiments, the target-side network device establishes two or more links with the non-access point device during seamless roaming, including at least one link corresponding to the BSS primary channel and at least one link corresponding to the NPCA primary channel. In some embodiments, the establishment of two or more links between the non-access point device and the target-side network device is requested by the non-access point device. In this case, the non-access point device sends a first request to the target-side network device, which requests the establishment of two or more links with the target-side network device.

[0164] It should be noted that the process by which the target network device performs behavior conforming to the first rule can be implemented as an independent embodiment, or it can be implemented in conjunction with other content provided in the embodiments of this application. The embodiments of this application do not impose any restrictions on this. Furthermore, each of the three ways in which the non-access point device performs behavior conforming to the first rule can also be implemented as an independent embodiment. The embodiments of this application do not impose any restrictions on this.

[0165] In summary, the method provided in this embodiment, by providing first information to the non-access point device (NAPD) during roaming, assists the NAPD in determining the primary channel for communication with the target network device, thereby helping the NAPD access the primary channel of the target network device. This enables the NAPD to quickly establish an association and exchange frames with the target network device during roaming, reducing time wasted due to channel mismatch and thus reducing latency during roaming, ultimately improving the user's roaming experience.

[0166] The method provided in this application, by providing first information to a non-access point device (NAPD) during roaming, assists the NAPD in determining the primary channel for communication with the target network device, thereby facilitating the NAPD's access to the primary channel of the target network device. This enables the NAPD to quickly establish an association and exchange frames with the target network device during roaming, reducing time wasted due to channel mismatch and thus decreasing roaming latency, ultimately improving the user's roaming experience.

[0167] The following describes the signaling and related rules involved in this application:

[0168] First signaling:

[0169] The first signaling carries first information about the target-side network device. This first information assists the non-access point device in determining the primary channel for communication with the target-side network device. In some embodiments, the first information includes one or more of the following: channel; primary channel busy time (NAV); dwell time; primary channel bandwidth (NPCA Channel Max BW); primary channel timeout; and timestamp.

[0170] In some embodiments, the first signaling includes a first action frame. In some embodiments, the first action frame includes one or more of the following action frames: a RAR frame; an FT reassociation response frame.

[0171] Taking the first action frame provided in this application embodiment as a RAR frame as an example, Figure 12 is a schematic diagram of the frame format of a RAR frame provided in an exemplary embodiment of this application. The fields in the RAR frame shown in Figure 12 are described below:

[0172] • Frame Control: Indicates basic information such as frame type.

[0173] • Duration: Indicates the time interval from the end of the current frame to the end of the TXOP.

[0174] • Address 1: Indicates the receiving address.

[0175] • Address 2: Indicates the sending address.

[0176] • Address 3: Same as Address 2.

[0177] • Sequence Control: Indicates the sequence number of the MAC Service Data Unit (MSDU) and MAC Protocol Data Unit (MPDU).

[0178] HT Control (High Throughput Control): Carries multiple control signaling protocols.

[0179] • Category: Indicates the type of Action frame. The value is any integer between 40 and 125, such as 40, to indicate a Protected UHR type Action frame.

[0180] • Protected UHR Action: Indicates the subtype of the Protected UHR Action frame, with a value of any integer between 0 and 255, such as 1, to indicate a RAR frame.

[0181] • Dialog Token (Session Identifier): Set to a non-zero value to indicate a request / response session.

[0182] • Status Code: Indicates the status code.

[0183] • STA Address: Indicates the Media Access Control (MAC) address of the non-AP MLD / non-AP STA that sends the RAI frame corresponding to this RAR frame.

[0184] • Target AP Address: Indicates the BSSID of a target AP's BSS.

[0185] • Target AP NPCA Status Info: Indicates the NPCA status information of a target AP. In some embodiments, when the first signaling is a RAR frame, the Target AP NPCA Status Info field corresponds to the first field mentioned above.

[0186] • Channel: Indicates the primary channel on which the target AP is located. For example, a value of 1 indicates the first primary channel, and a value of 0 indicates the second primary channel (NPCA primary channel); or a value of 0 indicates the first primary channel, and a value of 1 indicates the second primary channel.

[0187] • Primary Channel NAV: Indicates the duration of continuous busy activity of the target AP on the primary channel, i.e., the NAV value set for the target AP on the primary channel.

[0188] • Dwell Time: Indicates the duration for which the target AP stays on the first or second primary channel indicated by the Channel field.

[0189] • NPCA Channel Max BW (NPCA Channel Maximum Bandwidth): This field is reserved when the Channel field indicates the first primary channel; otherwise, it indicates the maximum bandwidth of PPDUs that the target AP can transmit or receive on the NPCA primary channel. For example, a value of 0 represents 20MHz, a value of 1 represents 40MHz, a value of 2 represents 80MHz, a value of 3 represents 160MHz, and other values ​​are reserved.

[0190] • NPCA Channel Timeout: This field is reserved when the Channel field indicates the primary channel; otherwise, it indicates the maximum listening time on the NPCA primary channel after a non-AP MLD / non-AP STA roams. If communication with the target AP fails within the time indicated by the NPCA Channel Timeout field, the system switches to the target AP's primary channel.

[0191] • Timestamp: Indicates the local time of the target AP when it generated at least one of the following fields: Channel, Primary Channel NAV, Dwell Time, NPCA Channel Max BW, and NPCA Channel Timeout, such as TSF time.

[0192] • FCS: Frame Check.

[0193] Taking the first action frame provided in this application embodiment as an FT reassociation response frame as an example, Figure 13 is a schematic diagram of the frame format of an FT reassociation response frame provided in an exemplary embodiment of this application. The fields in the FT reassociation response frame shown in Figure 13 are described below:

[0194] • Frame Control: Indicates basic information such as frame type.

[0195] • Duration: Indicates the time interval from the end of the current frame to the end of the TXOP.

[0196] • Address 1: Indicates the receiving address.

[0197] • Address 2: Indicates the sending address.

[0198] • Address 3: Same as Address 2.

[0199] • Sequence Control: Indicates the sequence number of the MSDU and MPDU.

[0200] • HT Control: Carries various control signaling.

[0201] • Category: Indicates the Action frame type. A value of 6 indicates the FT Action frame type.

[0202] • FT Action: Indicates the subtype of the FT Action frame, with a value of any integer between 5 and 255, such as 6, to indicate the FT reassociation response frame.

[0203] •STA Address: Indicates the MAC address of the non-AP MLD / non-AP STA that sent the FT reassociation request frame corresponding to this frame.

[0204] • Target AP Address: Indicates the BSSID of a target AP's BSS.

[0205] • Status Code: Indicates the status code.

[0206] • FT Reassociation Request frame body: Used to contain other fields. In some embodiments, when the first signaling is an FT reassociation response frame, the FT Reassociation Request frame body field corresponds to the first field mentioned above.

[0207] • Channel: Indicates the primary channel on which the target AP is located. For example, a value of 1 indicates the first primary channel, and a value of 0 indicates the second primary channel (NPCA primary channel); or a value of 0 indicates the first primary channel, and a value of 1 indicates the second primary channel.

[0208] • Primary Channel NAV: Indicates the duration of continuous busy activity of the target AP on the primary channel, i.e., the NAV value set for the target AP on the primary channel.

[0209] • Dwell Time: Indicates the duration for which the target AP stays on the first or second primary channel indicated by the Channel field.

[0210] • NPCA Channel Max BW (NPCA Channel Maximum Bandwidth): This field is reserved when the Channel field indicates the first primary channel; otherwise, it indicates the maximum bandwidth of PPDUs that the target AP can transmit or receive on the NPCA primary channel. For example, a value of 0 represents 20MHz, a value of 1 represents 40MHz, a value of 2 represents 80MHz, a value of 3 represents 160MHz, and other values ​​are reserved.

[0211] • NPCA Channel Timeout: This field is reserved when the Channel field indicates the primary channel; otherwise, it indicates the maximum listening time on the NPCA primary channel after a non-AP MLD / non-AP STA roams. If communication with the target AP fails within the time indicated by the NPCA Channel Timeout field, the system switches to the target AP's primary channel.

[0212] • Timestamp: Indicates the local time of the target AP when it generated at least one of the following fields: Channel, Primary Channel NAV, Dwell Time, NPCA Channel Max BW, and NPCA Channel Timeout, such as TSF time.

[0213] • FCS: Frame Check.

[0214] Second signaling:

[0215] The second signaling is used to request the first information. In some embodiments, the second signaling includes a second action frame. In some embodiments, the second action frame includes one or more RAI frames from the following action frames: FT reassociation request frame.

[0216] Taking the second action frame provided in this application embodiment as a RAI frame as an example, Figure 14 is a schematic diagram of the frame format of a RAI frame provided in an exemplary embodiment of this application. The fields in the RAI frame shown in Figure 14 are described below:

[0217] • Frame Control: Indicates basic information such as frame type.

[0218] • Duration: Indicates the time interval from the end of the current frame to the end of the TXOP.

[0219] • Address 1: Indicates the receiving address.

[0220] • Address 2: Indicates the sending address.

[0221] • Address 3: Same as Address 2.

[0222] • Sequence Control: Indicates the sequence number of the MSDU and MPDU.

[0223] • HT Control: Carries various control signaling.

[0224] • Category: Indicates the type of Action frame. The value is any integer between 40 and 125, such as 40, to indicate a Protected UHR type Action frame.

[0225] • Protected UHR Action: Indicates the subtype of the Protected UHR Action frame, with a value of any integer between 0 and 255, such as 0, to indicate a RAI frame.

[0226] • Dialog Token (Session Identifier): Set to a non-zero value to indicate a request / response session.

[0227] •STAAddress: Indicates the MAC address of the non-AP MLD / non-AP STA that sent this RAI frame.

[0228] • Target AP Address: Indicates the BSSID of a target AP's BSS.

[0229] • Request for NPCA Status of Target AP: Indicates whether the NPCA status of the target AP is requested. For example, a value of 1 indicates yes, and a value of 0 indicates no; or, a value of 0 indicates yes, and a value of 1 indicates no. In some embodiments, when the second signaling is a RAI frame, the Request for NPCA Status of Target AP field corresponds to the second field mentioned above.

[0230] • FCS: Frame Check.

[0231] Taking the first action frame provided in this application embodiment as an FT reassociation request frame as an example, Figure 15 is a schematic diagram of the frame format of an FT reassociation request frame provided in an exemplary embodiment of this application. The fields in the FT reassociation request frame shown in Figure 15 are described below:

[0232] • Frame Control: Indicates basic information such as frame type.

[0233] • Duration: Indicates the time interval from the end of the current frame to the end of the TXOP.

[0234] • Address 1: Indicates the receiving address.

[0235] • Address 2: Indicates the sending address.

[0236] • Address 3: Same as Address 2.

[0237] • Sequence Control: Indicates the sequence number of the MSDU and MPDU.

[0238] • HT Control: Carries various control signaling.

[0239] • Category: Indicates the type of Action frame. For example, a value of 6 indicates the FT Action frame type.

[0240] • FT Action: Indicates the subtype of the FT Action frame, with a value of any integer between 5 and 255, such as 5, to indicate the FT reassociation request frame.

[0241] •STA Address: Indicates the MAC address of the non-AP MLD / non-AP STA that sent this frame.

[0242] • Target AP Address: Indicates the BSSID of a target AP's BSS.

[0243] • FT Reassociation Request frame body: The frame body field, used to contain other subfields.

[0244] • Request for NPCA Status of Target AP: Indicates whether the NPCA status of the target AP is requested. For example, a value of 1 indicates yes, and a value of 0 indicates no; or, a value of 0 indicates yes, and a value of 1 indicates no. In some embodiments, when the second signaling is an FT reassociation request frame, the Request for NPCA Status of Target AP field corresponds to the second field mentioned above.

[0245] FCS: Frame Check.

[0246] Signaling-related rules:

[0247] • When roaming, a non-access point device can send a status request signaling (first signaling) to the source network device to request the source network device to obtain the NPCA status of the target network device.

[0248] • After obtaining the NPCA status information of the target network device, the source-side network device should send it to the non-access point device (as soon as possible).

[0249] • Under certain circumstances, target-side network devices can also directly send NPCA status information to non-access point devices.

[0250] • Non-access point devices can determine whether the primary channel for communication with the target network device next is the first primary channel or the second primary channel (NPCA primary channel) based on the NPCA status information received from the target network device.

[0251] Figure 16 is a flowchart of a signaling transmission method for a roaming process provided in an exemplary embodiment of this application. This method can be used in the system shown in Figure 1. The method includes:

[0252] Step 1602: The non-access point device sends a second signaling message to the source network device.

[0253] For details regarding the second signaling, please refer to the relevant content in other embodiments of this application.

[0254] Step 1604: The source-side network device sends the first signaling to the non-access point device.

[0255] For details regarding the first signaling, please refer to the relevant content in other embodiments of this application.

[0256] Step 1606: The target-side network device sends the first signaling to the non-access point device.

[0257] For details regarding the first signaling, please refer to the relevant content in other embodiments of this application.

[0258] It should be noted that steps 1604 and 1606 above are parallel steps, and either one can be selected for execution. For example, in the scenario of seamless roaming without co-location, during roaming, if the non-access point device maintains a link connection with only one non-co-location network device at the same time, steps 1602 and 1604 are executed; if the non-access point device maintains a link connection with two or more non-co-location network devices at the same time, steps 1602 and 1604 are executed; if the non-access point device maintains a link connection with only one non-co-location network device at the same time, and the non-access point device immediately switches to the target network device after sending the RAI without performing a context migration, steps 1602 and 1606 are executed. In the scenario of seamless roaming via DS hot association, steps 1602 and 1604 are executed.

[0259] In this embodiment, steps 1602, 1604, and 1606 are optional. In different embodiments, one or more of these steps may be omitted or substituted.

[0260] Step 1602 can be implemented as a standalone embodiment, such as a signaling transmission method on the non-access point device side or a signaling reception method on the source network device side. Step 1604 can be implemented as a standalone embodiment, such as a signaling reception method on the non-access point device side or a signaling transmission method on the source network device side. Step 1606 can be implemented as a standalone embodiment, such as a signaling reception method on the non-access point device side or a signaling transmission method on the target network device side.

[0261] In summary, the method provided in this embodiment, by providing first information to the non-access point device (NAPD) during roaming, assists the NAPD in determining the primary channel for communication with the target network device, thereby helping the NAPD access the primary channel of the target network device. This enables the NAPD to quickly establish an association and exchange frames with the target network device during roaming, reducing time wasted due to channel mismatch and thus reducing latency during roaming, ultimately improving the user's roaming experience.

[0262] Taking the method provided in this application embodiment as an example of a scenario of seamless non-collocated roaming: the signaling flow for the case where a non-AP STA can maintain a link connection with only one non-collocated AP at the same time during roaming is shown in Figure 17; the signaling flow for the case where a non-AP STA can maintain a link connection with two or more non-collocated APs at the same time during roaming is shown in Figure 18; and the signaling flow for the case where a non-AP STA can maintain a link connection with only one non-collocated AP at the same time during roaming, and the non-AP STA immediately switches to the target AP after sending the RAI without performing a context transition is shown in Figure 19.

[0263] As shown in Figure 17, the Non-AP STA sets the "Request for NPCA Status of Target AP" field in the RAI frame sent to the current AP (AP1) in step 4 to indicate "Yes," meaning it requests to obtain the NPCA status of the target AP through the current AP. AP1 can obtain a set of NPCA status information from the target AP (AP2) through step 9 or other means (before step 10 begins), which includes Channel, Primary Channel NAV, Dwell Time, NPCA Channel Max BW, NPCA Channel Timeout, and Timestamp. In this embodiment, Channel = NPCA Primary Channel, indicating that the target AP is on the NPCA primary channel at the time indicated by the Timestamp; Primary Channel NAV = 4ms, indicating that the target AP's primary channel (first primary channel) will be busy for 4ms starting from the time indicated by the Timestamp; Dwell Time = 4ms, indicating that the target AP will work on the NPCA primary channel for 4ms starting from the time indicated by the Timestamp; NPCA Channel Max BW = 80MHz, indicating that the maximum bandwidth of PPDUs that the target AP can send and / or receive on the NPCA primary channel is 80MHz; NPCA Channel Timeout = 1.5ms, indicating that the NPCA primary channel listening timeout is 1.5ms; Timestamp = t, indicating the local time when the target AP generated this Channel, Primary Channel NAV, NPCA Channel Max BW, and NPCA Channel Timeout, such as TSF time.

[0264] Subsequently, in step 10, AP1 carries the aforementioned Channel, Primary Channel NAV, Dwell Time, NPCA Channel Max BW, NPCA Channel Timeout, and Timestamp in the RAR frame and sends them to the Non-AP STA, thereby assisting the Non-AP STA in deciding whether to access the target AP's NPCA primary channel or primary channel during roaming.

[0265] The Non-AP STA receives the RAR frame and obtains the NPCA status information of the target AP. However, due to the time required for frame transmission or other operations, the Non-AP STA obtains the NPCA status information of the target AP later than the time indicated in the Timestamp. In this embodiment, the Non-AP STA receives the NPCA status information of the target AP at t+2ms, which is 2ms later than time t. This time has not exceeded the duration (4ms) indicated by the Primary Channel NAV field and / or Dwell Time field, so the NPCA status information of the target AP has not expired and has high reliability. In addition, the Non-AP STA can calculate that from time t+2ms, the target AP can still operate on its NPCA main channel for 2ms, which is sufficient time.

[0266] Therefore, in step 11, the Non-AP STA will first switch to the target AP's NPCA primary channel to attempt to compete for or listen to the channel, thereby establishing a connection with the target AP and exchanging frames for a period of time. The length of this period depends on the specific situation, but generally does not exceed the duration indicated by the Primary Channel NAV field and / or Dwell Time field, i.e., not exceeding t+4ms.

[0267] In this way, the Non-AP STA can communicate with the target AP more accurately as soon as it starts roaming. On the one hand, the Non-AP STA can compete on the NPCA main channel to send uplink low-latency data as soon as possible; on the other hand, the target AP can also send downlink low-latency data in advance on the NPCA main channel.

[0268] As shown in Figure 18, the signaling flow in Figure 18 differs from that in Figure 17 only in that the non-AP MLD can maintain link connections with two or more non-collocated APs simultaneously during roaming, thus the signaling flow is different. However, the information and rules transmitted by the RAI and RAR frames are the same as in Figure 17. As shown in Figure 19, the signaling flow in Figure 19 differs from that in Figure 17 only in that the non-AP STA immediately switches to the target AP after sending the RAI and does not perform a context transition. Therefore, the RAR frame is sent by the target AP to the non-AP STA instead of by the current AP. Moreover, the target AP has the ability to predict NPCA status information in advance, i.e., the Dwell Time field carries a period of dwell time for the target AP on the main channel or NPCA main channel in the future, or multiple periodic dwell times in the future. Therefore, the signaling flow is different. However, the information and rules transmitted by the RAI and RAR frames are the same as in Example 1.

[0269] Taking the method provided in this application embodiment as an example of seamless roaming via DS hot-association, Figure 20 is a schematic diagram of the signaling flow provided in an exemplary embodiment of this application. As shown in Figure 20, the Non-AP STA sets the Request for NPCA Status of Target AP field to "Yes" in the FT reassociation request frame sent to the current AP MLD, that is, it requests to obtain the NPCA status of the target AP MLD through the current AP MLD. The current AP MLD can obtain a set of NPCA status information from the target AP MLD in some way, including Channel, Primary Channel NAV, Dwell Time, NPCA Channel Max BW, NPCA Channel Timeout, and Timestamp. In this embodiment, Channel = NPCA Primary Channel, indicating that the target AP MLD is located on the NPCA primary channel at the time indicated by the Timestamp; Primary Channel NAV = 4ms, indicating that the target AP MLD will continue to work on the NPCA primary channel for 4ms starting from the time indicated by the Timestamp; NPCA Channel Max BW = 80MHz, indicating that the maximum bandwidth of PPDU that the target AP MLD can send and / or receive on the NPCA primary channel is 80MHz; NPCA Channel Timeout = 1.5ms, indicating that the NPCA primary channel listening timeout is 1.5ms; Timestamp = t, indicating the local time when the target AP MLD generates this Channel, Primary Channel NAV, Dwell Time, NPCA Channel Max BW, and NPCA Channel Timeout, such as TSF time.

[0270] Subsequently, the current AP MLD carries the aforementioned Channel, Primary Channel NAV, Dwell Time, NPCA Channel Max BW, NPCA Channel Timeout, and Timestamp information in the FT reassociation response frame and sends it to the Non-AP MLD, thereby assisting the Non-AP MLD in deciding whether to access the target AP MLD's NPCA primary channel or primary channel (first primary channel) during roaming.

[0271] The Non-AP MLD receives the FT reassociation response frame and obtains the NPCA status information of the target AP MLD. However, due to the time required for frame transmission or other operations, the Non-AP MLD obtains the NPCA status information of the target AP MLD later than the time indicated in the Timestamp. In this embodiment, the Non-AP MLD receives the NPCA status information of the target AP at t+2ms, which is 2ms later than time t. This time has not exceeded the duration (4ms) indicated by the Primary Channel NAV field, so the NPCA status information of the target AP MLD has not expired and has high reliability. In addition, the Non-AP MLD can calculate that from time t+2ms, the target AP MLD can still work on its NPCA main channel for 2ms, which is sufficient time.

[0272] Therefore, the Non-AP MLD can first switch to the NPCA main channel of the target AP MLD, send an activation hot backup association request frame to the target AP MLD, and receive an activation hot backup association response frame, thereby establishing an association with the target AP MLD and exchanging frames for a period of time. The length of this period depends on the specific situation, but generally does not exceed the duration indicated by the Primary Channel NAV field, that is, not exceeding t+4ms.

[0273] It should be noted that the order of the method steps provided in the embodiments of this application can be appropriately adjusted, and the steps can be added or removed as appropriate. Furthermore, different steps can be freely combined to form new embodiments. Any variations that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the protection scope of this application, and therefore will not be elaborated further. In addition, the order of the different situations described above does not have a preferred meaning, but is only for convenience of description.

[0274] It should be noted that the source-side network device in this application embodiment is equivalent to / can be replaced by at least one of the following: source network device, current network device, current AP, and first AP. The target-side network device in this application embodiment is equivalent to / can be replaced by at least one of the following: target network device, target AP, and second AP.

[0275] Figure 21 is a block diagram of a signaling receiving device for roaming provided in an exemplary embodiment of this application. This device can be implemented as a non-access point device (NAPD) or as part of an NAPD by software, hardware, or a combination of both. The device includes a receiving module 2101 and a transmitting module 2102.

[0276] The receiving module 2101 is used to receive first signaling sent by the network device. The first signaling carries first information about the target network device, which is used to assist the device in determining the primary channel for communication with the target network device. In some embodiments, the target network device corresponds to at least two primary channels, for example, the target network device corresponds to two primary channels. In some embodiments, the primary channels of the target network device include: a first primary channel; and a second primary channel. The first primary channel and the second primary channel are different primary channels. In some embodiments, the first primary channel includes a common operating channel / channel for all devices in the target network device's BSS. In some embodiments, the first primary channel is a channel shared by all member sites in the target network device's BSS. In some embodiments, the second primary channel includes an NPCA primary channel. In some embodiments, the NPCA primary channel is the primary channel used when the device performs non-primary channel access.

[0277] In some embodiments, the first signaling is sent by the source-side network device. In some embodiments, the first signaling is sent by the target-side network device. In some embodiments, in non-co-located seamless roaming scenarios, the first signaling can be sent by either the source-side network device or the target-side network device. In some embodiments, in seamless roaming scenarios via DS hot-association, the first signaling is sent by the source-side network device.

[0278] In some embodiments, the first information includes one or more of the following: a dwell channel; a primary channel busy time; a dwell time; a primary channel bandwidth; a primary channel timeout; and a timestamp. The dwell channel indicates the primary channel on which the target network device is located. The primary channel busy time indicates the duration of continuous busy activity on the target network device's first primary channel, such as the NAV value set by the target network device on the primary channel. The dwell time indicates the duration the target network device remains on the primary channel indicated by the dwell channel. The primary channel bandwidth indicates the bandwidth transmitted on the target network device's second primary channel. The primary channel timeout indicates the maximum listening time on the target network device's second primary channel after roaming.

[0279] In some embodiments, the first signaling includes a first action frame. In some embodiments, the first action frame includes a first field for carrying first information. In some embodiments, the frame body of the first action frame includes the first field. In some embodiments, the first action frame includes one or more of the following action frames: a RAR frame; an FT reassociation response frame. In some embodiments, in a non-co-located seamless roaming scenario, the first signaling includes a RAR frame. In a seamless roaming scenario via DS hot associativity, the first signaling includes an FT reassociation response frame.

[0280] In some embodiments, the first signaling is actively sent to the device by either the source-side network device or the target-side network device. In some embodiments, the first signaling is sent to the device by either the source-side network device or the target-side network device when the device requests first information. The sending module 2102 is configured to send a second signaling to the source-side network device, the second signaling being used to request the first information. In some embodiments, the second signaling includes a second action frame. In some embodiments, the second action frame includes a second field, the second field being used to indicate the request for the first information. In some embodiments, the frame body of the second action frame includes the second field. In some embodiments, the second action frame includes one or more of the following action frames: a RAI frame; an FT reassociation request frame. In some embodiments, in a non-co-located seamless roaming scenario, the second signaling includes a RAI frame. In a seamless roaming scenario via DS hot associativity, the second signaling includes an FT reassociation request frame.

[0281] In some embodiments, the apparatus in this application further includes an execution module for performing behavior conforming to a first rule during seamless roaming.

[0282] In some embodiments, the receiving module 2101 is configured to receive beacon frames sent by the target-side network device during seamless roaming or within a portion of the time frame during seamless roaming; wherein the beacon frames satisfy at least one of the following conditions: they use, must use, or should use a non-high-throughput repetitive physical layer protocol data unit format; the bandwidth of the beacon frames is the total operating bandwidth of the BSS associated with the target-side network device; the bandwidth of the beacon frames includes the BSS main channel and the NPCA main channel of the target-side network device. In some embodiments, the beacon frames sent by the target-side network device within a portion of the time frame during seamless roaming satisfy at least one condition.

[0283] In some embodiments, the execution module is configured to suspend, or must suspend, or should suspend, or suspend NPCA functions on the link where seamless roaming is occurring, during a portion of the time range in the seamless roaming process. In some embodiments, the start time of the portion of the time range includes at least one of the following: the successful transmission time of the roaming preparation request frame; the successful transmission time of the immediate response frame to the roaming preparation request frame; the successful transmission time of the roaming preparation response frame; the successful transmission time of the immediate response frame to the roaming preparation response frame; and the start time of context transmission. In some embodiments, the end time of the portion of the time range includes at least one of the following: the successful transmission time of the roaming request frame; the successful transmission time of the immediate response frame to the roaming request frame; the successful transmission time of the roaming response frame; and the successful transmission time of the immediate response frame to the roaming response frame.

[0284] For example, the aforementioned partial time range includes at least one of the following: the time range between the successful transmission time of the roaming preparation request frame or the immediate response frame of the roaming preparation request frame and the successful transmission time of the roaming request frame or the immediate response frame of the roaming request frame; the time range between the successful transmission time of the roaming preparation request frame or the immediate response frame of the roaming preparation request frame and the successful transmission time of the roaming response frame or the immediate response frame of the roaming response frame; the time range between the successful transmission time of the roaming preparation request frame or the immediate response frame of the roaming preparation request frame and the successful transmission time of the roaming request frame or the immediate response frame of the roaming request frame; the time range between the start time of the context transfer and the successful transmission time of the roaming request frame or the immediate response frame of the roaming request frame; and the time range between the start time of the context transfer and the successful transmission time of the roaming response frame or the immediate response frame of the roaming response frame.

[0285] In some embodiments, the roaming preparation request frame is sent by the device to the source-side network device. The roaming preparation request frame is used to initialize the seamless roaming process between the device and the target-side network device. In some embodiments, the roaming preparation request frame is used for at least one of link initialization, link capability information notification, key initialization, and semi-static context transmission initialization in the seamless roaming process. In some embodiments, the roaming preparation response frame is sent by the source-side network device to the device. The roaming preparation response frame is used to indicate that seamless roaming initialization has been completed. In some embodiments, the roaming request frame is sent by the device to the target-side network device. The roaming request frame is used to request at least one of link activation, identity verification, and dynamic context transmission. In some embodiments, the roaming response frame is sent by the target-side network device to the device. The roaming response frame is used to indicate at least one of link activation status and key transmission.

[0286] In some embodiments, the execution module is configured to establish two or more links with the target-side network device during seamless roaming. In some embodiments, the sending module 2102 is configured to send a first request to the target-side network device; wherein the first request is used to request the establishment of two or more links with the target-side network device. In some embodiments, the two or more links established by the device with the target-side network device during seamless roaming include at least one link corresponding to the BSS main channel and at least one link corresponding to the NPCA main channel.

[0287] It should be noted that the process of performing the behavior conforming to the first rule can be implemented as an independent embodiment on its own, or it can be implemented in conjunction with other content provided in the embodiments of this application. The embodiments of this application do not impose any restrictions on this. Furthermore, each of the three ways of performing the behavior conforming to the first rule can also be implemented as an independent embodiment on its own, and the embodiments of this application do not impose any restrictions on this.

[0288] Figure 22 is a block diagram of a signaling transmission apparatus for roaming processes provided in an exemplary embodiment of this application. This apparatus can be implemented as a source-side network device, or as part of a source-side network device, through software, hardware, or a combination of both. The apparatus includes a transmitting module 2201 and a receiving module 2202.

[0289] The sending module 2201 is used to send a first signaling message to a non-access point device. The first signaling message carries first information about the target network device, which assists the non-access point device in determining the primary channel for communication with the target network device. In some embodiments, the first information assists the non-access point device in determining the primary channel on which the target network device is located, including the primary channel on which the target network device receives and / or transmits frames. In some embodiments, the first information assists the non-access point device in determining the primary channel on which the target network device operates. In some embodiments, the first information assists the non-access point device in determining the primary channel it accesses within the primary channel of the target network device. In some embodiments, the first information is determined by the target network device.

[0290] In some embodiments, the target-side network device corresponds to at least two main channels; for example, the target-side network device corresponds to two main channels. In some embodiments, the main channels of the target-side network device include: a first main channel; and a second main channel. The first main channel and the second main channel are different main channels.

[0291] In some embodiments, the first primary channel includes a common operating channel / channel for all non-access point devices in the BSS of the target-side network device. In some embodiments, the first primary channel is a channel shared by all member sites in the BSS of the target-side network device. In some embodiments, the second primary channel includes the NPCA primary channel. In some embodiments, the NPCA primary channel is the primary channel used when a non-access point device accesses a non-primary channel. In some embodiments, the first signaling is equivalent to / can be replaced by NPCA status request signaling, and the first information is equivalent to / can be replaced by NPCA status information. The first information is used to indicate the NPCA status of the target-side network device.

[0292] In some embodiments, in non-co-located seamless roaming scenarios, the first signaling is sent by the device. For example, during roaming, the first signaling is sent by the device when the non-access point device maintains a link connection with only one non-co-located network device at the same time; the first signaling is also sent by the device when the non-access point device maintains a link connection with two or more non-co-located network devices at the same time. In some embodiments, in seamless roaming scenarios via DS hot-association, the first signaling is sent by the device.

[0293] In some embodiments, the first information includes one or more of the following: a dwell channel; a primary channel busy time; a dwell time; a primary channel bandwidth; a primary channel timeout; and a timestamp. The dwell channel indicates the primary channel on which the target network device is located. The primary channel busy time indicates the duration of continuous busy activity on the target network device's first primary channel, such as the NAV value set by the target network device on the primary channel. The dwell time indicates the duration the target network device remains on the primary channel indicated by the dwell channel. The primary channel bandwidth indicates the bandwidth transmitted on the target network device's second primary channel. The primary channel timeout indicates the maximum listening time of the non-access point device on the target network device's second primary channel after roaming. The timestamp indicates the time at which the first information was generated.

[0294] In some embodiments, the first signaling includes a first action frame. In some embodiments, the first action frame includes a first field for carrying first information. In some embodiments, the frame body of the first action frame includes the first field. In some embodiments, the first action frame includes one or more of the following action frames: a RAR frame; an FT reassociation response frame. In some embodiments, in a non-co-located seamless roaming scenario, the first signaling includes a RAR frame. In a seamless roaming scenario via DS hot associativity, the first signaling includes an FT reassociation response frame.

[0295] In some embodiments, the first signaling is actively sent by the device to the non-access point device. In some embodiments, the first signaling is sent by the device to the non-access point device when the non-access point device requests first information. The receiving module 2202 is used to receive a second signaling sent by the non-access point device, the second signaling being used to request the first information. In some embodiments, when the device receives the second signaling, it obtains the first information through the target-side network device, that is, it receives the first information sent by the target-side network device, and then sends the first signaling to the non-access point device accordingly.

[0296] In some embodiments, the second signaling includes a second action frame. In some embodiments, the second action frame includes a second field indicating a request for first information. In some embodiments, the frame body of the second action frame includes the second field. In some embodiments, the second action frame includes one or more of the following action frames: a RAI frame; an FT reassociation request frame. In some embodiments, in non-co-located seamless roaming scenarios, the second signaling includes a RAI frame. In seamless roaming scenarios via DS hot associativity, the second signaling includes an FT reassociation request frame.

[0297] Figure 23 is a block diagram of a signaling transmission apparatus for a roaming process provided in an exemplary embodiment of this application. This apparatus can be implemented as a target-side network device, or as part of a target-side network device, through software, hardware, or a combination of both. The apparatus includes a transmission module 2301.

[0298] The transmitting module 2301 is configured to transmit a first signaling message to a non-access point device. The first signaling message carries first information about the device, which assists the non-access point device in determining the primary channel for communication with the device. In some embodiments, the first information assists the non-access point device in determining the primary channel on which the device is located, including the primary channel on which the device receives and / or transmits frames. In some embodiments, the first information assists the non-access point device in determining the primary channel on which the device operates. In some embodiments, the first information assists the non-access point device in determining the primary channel it accesses within the device's primary channel. In some embodiments, the first information is determined by the device itself.

[0299] In some embodiments, the device corresponds to at least two main channels; for example, the device corresponds to two main channels. In some embodiments, the main channels of the device include: a first main channel; and a second main channel. The first main channel and the second main channel are different main channels.

[0300] In some embodiments, the first primary channel includes a common operating channel / channel for all non-access point devices in the device's BSS. In some embodiments, the first primary channel is a channel shared by all member sites in the device's BSS. In some embodiments, the second primary channel includes the NPCA primary channel. In some embodiments, the NPCA primary channel is the primary channel used when a non-access point device accesses a non-primary channel. In some embodiments, the first signaling is equivalent to / can be replaced by NPCA status request signaling, and the first information is equivalent to / can be replaced by NPCA status information. The first information is used to indicate the NPCA status of the device.

[0301] In some embodiments, in non-co-located seamless roaming scenarios, the first signaling is sent by the device. For example, if a non-access point device maintains a link connection with only one non-co-located network device at a time, and the non-access point device switches to the device immediately after sending a RAI without performing a context transition, the first signaling is sent by the device.

[0302] In some embodiments, the first information includes one or more of the following: a dwell channel; a primary channel busy time; a dwell time; a primary channel bandwidth; a primary channel timeout; and a timestamp. The dwell channel indicates the primary channel on which the device is located. The primary channel busy time indicates the duration of continuous busy activity on the device's first primary channel, such as the NAV value set by the device on the primary channel. The dwell time indicates the duration the device remains on the primary channel indicated by the dwell channel. The primary channel bandwidth indicates the bandwidth transmitted on the device's second primary channel. The primary channel timeout indicates the maximum listening time of the non-access point device on the device's second primary channel after roaming. The timestamp indicates the time at which the first information was generated.

[0303] In some embodiments, the first signaling includes a first action frame. In some embodiments, the first action frame includes a first field for carrying first information. In some embodiments, the frame body of the first action frame includes the first field. In some embodiments, the first action frame includes a RAR frame. In some embodiments, in a non-co-located seamless roaming scenario, the first signaling includes a RAR frame.

[0304] In some embodiments, the first signaling is actively sent by the device to the non-access point device. In some embodiments, the first signaling is sent by the device to the non-access point device when the non-access point device requests first information. In this case, the source-side network device receives a second signaling sent by the non-access point device, which is used to request the first information. In some embodiments, when the source-side network device receives the second signaling, it notifies the device that the non-access point device requests the first information, thereby causing the device to send the first signaling.

[0305] In some embodiments, the second signaling includes a second action frame. In some embodiments, the second action frame includes a second field indicating a request for first information. In some embodiments, the frame body of the second action frame includes the second field. In some embodiments, the second action frame includes a RAI frame. In some embodiments, in a non-co-located seamless roaming scenario, the second signaling includes a RAI frame.

[0306] In some embodiments, the apparatus in this application further includes an execution module for performing behavior conforming to a first rule during seamless roaming.

[0307] In some embodiments, the transmitting module 2301 is configured to transmit beacon frames during seamless roaming or within a portion of the time frame during seamless roaming; wherein the beacon frame satisfies at least one of the following conditions: it uses, must use, or should use a non-high-throughput repetitive physical layer protocol data unit format; the bandwidth of the beacon frame is the total operating bandwidth of the device-associated BSS; and the bandwidth of the beacon frame includes the device's BSS main channel and NPCA main channel. In some embodiments, the beacon frames transmitted by the device within a portion of the time frame during seamless roaming satisfy at least one condition.

[0308] In some embodiments, the execution module is configured to suspend, or must suspend, or should suspend, or suspend NPCA functions on the link where seamless roaming is occurring, during a portion of the time range in the seamless roaming process. In some embodiments, the start time of the portion of the time range includes at least one of the following: the successful transmission time of the roaming preparation request frame; the successful transmission time of the immediate response frame to the roaming preparation request frame; the successful transmission time of the roaming preparation response frame; the successful transmission time of the immediate response frame to the roaming preparation response frame; and the start time of context transmission. In some embodiments, the end time of the portion of the time range includes at least one of the following: the successful transmission time of the roaming request frame; the successful transmission time of the immediate response frame to the roaming request frame; the successful transmission time of the roaming response frame; and the successful transmission time of the immediate response frame to the roaming response frame.

[0309] For example, the aforementioned partial time range includes at least one of the following: the time range between the successful transmission time of the roaming preparation request frame or the immediate response frame of the roaming preparation request frame and the successful transmission time of the roaming request frame or the immediate response frame of the roaming request frame; the time range between the successful transmission time of the roaming preparation request frame or the immediate response frame of the roaming preparation request frame and the successful transmission time of the roaming response frame or the immediate response frame of the roaming response frame; the time range between the successful transmission time of the roaming preparation request frame or the immediate response frame of the roaming preparation request frame and the successful transmission time of the roaming request frame or the immediate response frame of the roaming request frame; the time range between the start time of the context transfer and the successful transmission time of the roaming request frame or the immediate response frame of the roaming request frame; and the time range between the start time of the context transfer and the successful transmission time of the roaming response frame or the immediate response frame of the roaming response frame.

[0310] In some embodiments, the roaming preparation request frame is sent by the non-access point device to the source-side network device. The roaming preparation request frame is used to initialize the seamless roaming process between the non-access point device and the apparatus. In some embodiments, the roaming preparation request frame is used for at least one of the following in the seamless roaming process: link initialization, link capability information notification, key initialization, and semi-static context transmission initialization. In some embodiments, the roaming preparation response frame is sent by the source-side network device to the non-access point device. The roaming preparation response frame is used to indicate that seamless roaming initialization has been completed. In some embodiments, the roaming request frame is sent by the non-access point device to the apparatus. The roaming request frame is used to request at least one of link activation, identity verification, and dynamic context transmission. In some embodiments, the roaming response frame is sent by the apparatus to the non-access point device. The roaming response frame is used to indicate at least one of link activation status and key transmission.

[0311] In some embodiments, the execution module is configured to establish two or more links with the non-access point device during seamless roaming. In some embodiments, the apparatus further includes a receiving module for receiving a first request sent by the non-access point device; wherein the first request is for requesting the establishment of two or more links with the apparatus. In some embodiments, the two or more links established by the apparatus with the non-access point device during seamless roaming include at least one link corresponding to the BSS primary channel and at least one link corresponding to the NPCA primary channel.

[0312] It should be noted that the process of performing the behavior conforming to the first rule can be implemented as an independent embodiment on its own, or it can be implemented in conjunction with other content provided in the embodiments of this application. The embodiments of this application do not impose any restrictions on this. Furthermore, each of the three ways of performing the behavior conforming to the first rule can also be implemented as an independent embodiment on its own, and the embodiments of this application do not impose any restrictions on this.

[0313] It should be noted that the device provided in the above embodiments is only illustrated by the division of the above functional modules when implementing its functions. In actual applications, the above functions can be assigned to different functional modules according to actual needs, that is, the content structure of the device can be divided into different functional modules to complete all or part of the functions described above.

[0314] Regarding the apparatus in the above embodiments, the specific manner in which each module performs its operation has been described in detail in the embodiments related to the method, and will not be elaborated upon here.

[0315] To reiterate, the frame formats, element formats, and field formats shown in the above embodiments are merely examples and not limitations. This application supports modifications to the formats of each frame, element, and field based on the format design described above, such as changing the order of fields / elements, changing the number of bytes in fields / elements, changing the number of bits in fields / elements, changing the names of fields / elements / frames, etc. It also supports setting some fields / elements as reserved fields.

[0316] It should be understood that the format, name, and value of the frames / elements / fields involved in the various embodiments of this application are merely examples and do not imply any limitation on the format, name, and value of the frames / elements / fields. In different embodiments or designs, it is possible that one or more of the aforementioned element / field names, their positions in the frame, their arrangement order with other elements / fields, the number of bytes occupied, or the number of bits occupied may change. Similarly, in different embodiments or designs, it is possible that one or more of the aforementioned frame names, included elements / fields, the number of bytes occupied, or the number of bits occupied may change.

[0317] Figure 24 is a schematic diagram of the structure of a communication device (network device or terminal device) provided in an embodiment of this application. The communication device may include: a processor 2401, a receiver 2402, a transmitter 2403, a memory 2404, and a bus 2405.

[0318] The processor 2401 includes one or more processing cores, and the processor 2401 executes various functional applications and information processing by running software programs and modules.

[0319] The receiver 2402 and the transmitter 2403 can be implemented as a transceiver 2406, which can be a communication chip.

[0320] The memory 2404 is connected to the processor 2401 via the bus 2405. The memory 2404 can be used to store computer programs, and the processor 2401 can be used to execute the computer programs to implement the various steps performed by the network device or terminal device in the above method embodiments.

[0321] Furthermore, the memory 2404 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, including but not limited to: RAM (Random-Access Memory) and ROM (Read-Only Memory), EPROM (Erasable Programmable Read-Only Memory), EEPROM (Electrically Erasable Programmable Read-Only Memory), flash memory or other solid-state storage technologies, CD-ROM (Compact Disc Read-Only Memory), DVD (Digital Video Disc) or other optical storage, magnetic tape cassettes, magnetic tape, disk storage or other magnetic storage devices.

[0322] This application embodiment also provides a computer-readable storage medium storing a computer program for execution by a processor of a terminal device or a network device to implement the steps of the above-described signaling reception method for roaming, and / or signaling transmission method for roaming, and / or signaling transmission method for roaming, and / or control method for roaming, and / or request method for roaming.

[0323] In some embodiments, the computer-readable storage medium may include ROM (Read-Only Memory), RAM (Random-Access Memory), SSD (Solid State Drives), or optical disc, etc. The random access memory may include ReRAM (Resistance Random Access Memory) and DRAM (Dynamic Random Access Memory).

[0324] This application embodiment also provides a chip, the chip including programmable logic circuits and / or program instructions, which, when the chip is running on a terminal device or network device, are used to implement the various steps of the above-mentioned signaling reception method for roaming process, and / or, signaling transmission method for roaming process, and / or, signaling transmission method for roaming process, and / or, control method for roaming process, and / or, request method for roaming process.

[0325] This application also provides a computer program product or computer program, which includes computer instructions stored in a computer-readable storage medium. The processor of the communication device reads and executes the computer instructions from the computer-readable storage medium to implement the various steps in the above-described signaling reception method for roaming, and / or signaling transmission method for roaming, and / or signaling transmission method for roaming, and / or control method for roaming, and / or request method for roaming.

[0326] Those skilled in the art will recognize that the functions described in the embodiments of this application in one or more of the above examples can be implemented using hardware, software, firmware, or any combination thereof. When implemented using software, these functions can be stored in a computer-readable medium or transmitted as one or more instructions or code on a computer-readable medium. Computer-readable media include computer storage media and communication media, wherein communication media include any medium that facilitates the transfer of a computer program from one place to another. Storage media can be any available medium that can be accessed by a general-purpose or special-purpose computer.

[0327] The above description is merely an exemplary embodiment of this application and is not intended to limit this application. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the protection scope of this application.

Claims

1. An execution method for a roaming process, characterized in that, The method is performed by a target-side network device, and the method includes: Perform actions that conform to the first rule during seamless roaming.

2. The method according to claim 1, characterized in that, The actions performed during seamless roaming that conform to the first rule include: Send beacon frames during the seamless roaming process or within a portion of the seamless roaming process; The beacon frame satisfies at least one of the following conditions: it uses, must use, or should use a non-high-throughput repetitive physical layer protocol data unit format; the bandwidth of the beacon frame is the total operating bandwidth of the BSS associated with the target-side network device; and the bandwidth of the beacon frame includes the BSS main channel and NPCA main channel of the target-side network device.

3. The method according to claim 2, characterized in that, The beacon frames sent by the target-side network device during a portion of the time range of the seamless roaming process satisfy at least one of the conditions.

4. The method according to any one of claims 1 to 3, characterized in that, The actions performed during seamless roaming that conform to the first rule include: During a portion of the time frame of the seamless roaming process, the NPCA function on the link where seamless roaming occurs is suspended, or must be suspended, or should be suspended, or should be suspended.

5. The method according to claim 4, characterized in that, The start time of the specified time range includes at least one of the following: The successful transmission time of the roaming preparation request frame; the successful transmission time of the immediate response frame to the roaming preparation request frame; the successful transmission time of the roaming preparation response frame; the successful transmission time of the immediate response frame to the roaming preparation response frame; the start time of the context transmission.

6. The method according to claim 4 or 5, characterized in that, The end time of the specified time range includes at least one of the following: The successful transmission time of the roaming request frame; the successful transmission time of the immediate response frame of the roaming request frame; the successful transmission time of the roaming response frame; the successful transmission time of the immediate response frame of the roaming response frame.

7. The method according to any one of claims 1 to 6, characterized in that, The actions performed during seamless roaming that conform to the first rule include: During the seamless roaming process, two or more links are established with non-access point devices.

8. The method according to claim 7, characterized in that, The method further includes: Receive the first request sent by the non-access point device; The first request is used to request the establishment of two or more links with the target-side network device.

9. An execution method for a roaming process, characterized in that, The method is performed by a non-access point device, and the method includes: Perform actions that conform to the first rule during seamless roaming.

10. The method according to claim 9, characterized in that, The actions performed during seamless roaming that conform to the first rule include: During the seamless roaming process or within a certain time range of the seamless roaming process, beacon frames sent by the target-side network device are received; The beacon frame satisfies at least one of the following conditions: it uses, must use, or should use a non-high-throughput repetitive physical layer protocol data unit format; the bandwidth of the beacon frame is the total operating bandwidth of the BSS associated with the target-side network device; and the bandwidth of the beacon frame includes the BSS main channel and NPCA main channel of the target-side network device.

11. The method according to claim 10, characterized in that, The beacon frames sent by the target-side network device during a portion of the time range of the seamless roaming process satisfy at least one of the conditions.

12. The method according to any one of claims 9 to 11, characterized in that, The actions performed during seamless roaming that conform to the first rule include: During a portion of the time frame of the seamless roaming process, the NPCA function on the link where seamless roaming occurs is suspended, or must be suspended, or should be suspended, or should be suspended.

13. The method according to claim 12, characterized in that, The start time of the specified time range includes at least one of the following: The successful transmission time of the roaming preparation request frame; the successful transmission time of the immediate response frame to the roaming preparation request frame; the successful transmission time of the roaming preparation response frame; the successful transmission time of the immediate response frame to the roaming preparation response frame; the start time of the context transmission.

14. The method according to claim 12 or 13, characterized in that, The end time of the specified time range includes at least one of the following: The successful transmission time of the roaming request frame; the successful transmission time of the immediate response frame of the roaming request frame; the successful transmission time of the roaming response frame; the successful transmission time of the immediate response frame of the roaming response frame.

15. The method according to any one of claims 9 to 14, characterized in that, The actions performed during seamless roaming that conform to the first rule include: During the seamless roaming process, two or more links are established with the target-side network device.

16. The method according to claim 15, characterized in that, The method further includes: Send a first request to the target-side network device; The first request is used to request the establishment of two or more links with the target-side network device.

17. An execution device for a roaming process, characterized in that, The device is used in a target-side network device, and the device includes: The execution module is used to perform behaviors that conform to the first rule during seamless roaming.

18. An execution device for a roaming process, characterized in that, The device is used for a non-access point device, and the device includes: Perform actions that conform to the first rule during seamless roaming.

19. A target-side network device, characterized in that, The target-side network device includes: processor; A transceiver connected to the processor; Memory for storing the executable instructions of the processor; The target-side network device is configured to load and execute the executable instructions to implement the execution method for the roaming process as described in any one of claims 1 to 8.

20. A non-access point device, characterized in that, The non-access point device includes: processor; A transceiver connected to the processor; Memory for storing the executable instructions of the processor; The non-access point device is configured to load and execute the executable instructions to implement the execution method for the roaming process as described in any one of claims 9 to 16.

21. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that is executed by a processor to implement the execution method for a roaming process as described in any one of claims 1 to 16.

22. A chip, characterized in that, The chip includes programmable logic circuits and / or program instructions, which, when the chip is run on a communication device, are used to implement the execution method for the roaming process as described in any one of claims 1 to 16.

23. A computer program product, characterized in that, The computer program product includes computer instructions stored in a computer-readable storage medium; the processor of the communication device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the communication device to implement the execution method for the roaming process as described in any one of claims 1 to 16.

24. A computer program, characterized in that, The computer program is executed by the processor of the communication device to implement the execution method for the roaming process as described in any one of claims 1 to 16.

Images