Terminal equipment, base station equipment, and communication method

Abstract

Achieve efficient communication with a wireless LAN system. [Solution] A terminal device having a non-AP MLD, wherein the non-AP MLD has at least a first non-AP STA to it, the first AP MLD connected to the non-AP MLD has at least a first AP to it, and the second AP MLD not connected to the non-AP MLD has at least a second AP to it, and the terminal device includes a transmitting unit that transmits a first frame, a receiving unit that receives a second frame, and a processing unit, and if it supports a second mode, when transmitting the first frame, it does not stop transmitting the Data frame to the first AP until it receives the second frame, and when it receives the second frame, it starts transmitting the Data frame to the second AP. The first and second frames are link addition request and response frames with respect to the second AP MLD.

Description

Technical Field

[0001] The present invention relates to a terminal device, a base station device, and a communication method.

Background Art

[0002] The improvement of the speed and frequency utilization efficiency of wireless LAN (Local Area Network) communication has been studied by the IEEE (The Institute of Electrical and Electronics Engineers Inc.). Currently, the standardization of IEEE802.11bn has been started as a successor standard to IEEE802.11be.

Prior Art Documents

Non-Patent Documents

[0003] IEEE802.11-23 / 1996r0, Po-Kai Huang (Intel), “Improve roaming between MLDs”, November 2023.

Summary of the Invention

Problems to be Solved by the Invention

[0004] The present invention provides a terminal device, a base station device, and a communication method capable of efficient communication.

Means for Solving the Problems

[0005] (1) A first aspect of the present invention is a terminal device having a non-AP MLD, wherein the non-AP MLD has at least a first non-AP STA to it, a first AP MLD connected to the non-AP MLD has at least a first AP to it, and a second AP MLD not connected to the non-AP MLD has at least a second AP to it, and the terminal device includes a transmitting unit that transmits a first frame, a receiving unit that receives a second frame, and a processing unit, wherein, when the terminal device supports a second mode, when it transmits the first frame, it does not stop transmitting a Data frame to the first AP until it receives the second frame, and when it receives the second frame, it starts transmitting a Data frame to the second AP, the first frame is a frame for requesting the addition of a link to the second AP MLD, and the second frame is a response frame to the request for the addition of a link to the second AP MLD.

[0006] (2) A second aspect of the present invention is the terminal device according to claim 1, wherein the frame transmitted by the terminal device includes a first subfield, and if the terminal device supports the second mode, the first subfield is set to a first value.

[0007] (3) A third aspect of the present invention is the terminal device according to claim 1, wherein the first frame transmitted by the terminal device includes a second subfield, and if the terminal device supports the second mode, the second subfield is set to a second value.

[0008] (4) A fourth aspect of the present invention is a base station device having a first AP MLD, wherein at least a first AP belongs to the first AP MLD, and at least a first non-AP STA belongs to a non-AP MLD connected to the first AP MLD, and a second AP is not connected to the non-AP MLD The MLD has at least a second AP, and the base station device includes a receiving unit that receives a first frame, a transmitting unit that transmits a second frame, and a processing unit, and if the first non-AP STA supports the second mode, when it receives the first frame, it does not stop transmitting the Data frame to the first AP until it transmits the second frame, and when it transmits the second frame, it instructs the first non-AP STA to start transmitting the Data frame to the second AP, the first frame is a frame for requesting the addition of a link to the second AP MLD, and the second frame is to the second AP MLD A response frame to a request for an additional link from the base station equipment.

[0009] (5) A fifth aspect of the present invention is a communication method to which a non-AP MLD has at least a first non-AP STA to which a first AP MLD connected to the non-AP MLD has at least a first AP to which a first AP MLD connected to the non-AP MLD has at least a second AP to which a second AP MLD not connected to the non-AP MLD has at least a second AP to which a first non-AP STA supports a second mode, when the first non-AP STA transmits a first frame it does not stop transmitting a Data frame to the first AP until it receives a second frame, when it receives the second frame it starts transmitting a Data frame to the second AP, the first frame is a frame for requesting the addition of a link to the second AP MLD, and the second frame is a response frame to the request for the addition of a link to the second AP MLD. [Effects of the Invention]

[0010] This enables the realization of an efficient wireless communication system. [Brief explanation of the drawing]

[0011] [Figure 1] This figure shows an example of a wireless LAN system according to one aspect of this embodiment. [Figure 2] This figure shows an example of OBSS according to one aspect of this embodiment. [Figure 3] This diagram shows an example of the configuration of STA according to one aspect of this embodiment. [Figure 4] This diagram shows an example of the configuration of an AP according to one aspect of this embodiment. [Figure 5] This figure shows an example of a MAC frame format according to one aspect of this embodiment. [Figure 6] This figure shows an example of an A-MSDU according to one aspect of this embodiment. [Figure 7] This figure shows an example of an A-MPDU according to one aspect of this embodiment. [Figure 8] This figure shows an example of Fragmentation according to one embodiment. [Figure 9] This figure shows an example of a PPDU according to one aspect of this embodiment. [Figure 10] This figure shows an example of the MAC data plane architecture of an MLD according to one aspect of this embodiment. [Figure 11] This figure shows an example of a backoff procedure according to one aspect of this embodiment. [Figure 12] This figure shows an example of a NAV according to one aspect of this embodiment. [Figure 13] This figure shows an example of the procedure for UHR Link Reconfiguration according to one aspect of this embodiment. [Modes for carrying out the invention]

[0012] Embodiments of the present invention will be described below.

[0013] "A, and / or B" may be a term that includes "A", "B", or "A and B".

[0014] The wireless LAN system in this embodiment includes an access point (AP) and a station (STA). A network composed of an access point and a station is called a BSS (Basic Service Set). The wireless LAN system may be composed of one or more stations. When the wireless LAN system is composed of two or more STAs, the wireless LAN system may be called a BSS.

[0015] The access point (AP) may be called a base station device. The station (STA) may be called a terminal device. One base station device may have one or more APs. One base station device may have one or more AP MLDS. One base station device may have one or more Super MLDS. One base station device may have one or more Super AP MLDS. One base station device may have one or more APs, one or more AP MLDS, and / or one or more Super AP MLDS. One terminal device may have one or more STAs. One terminal device may have one or more non-AP STAs. One terminal device may have one or more non-AP MLDS . One terminal device may have one or more non-AP STAs and / or one or more non-AP MLDS.

[0016] FIG. 1 is a diagram showing an example of a wireless LAN system according to an aspect of this embodiment. In FIG. 1 , the wireless LAN system includes STA103, STA104, and AP102. 101 may be called a BSS.

[0017] STA may be a logical entity. This logical entity is the Medium Access Control (MAC) and physical layer interface to the wireless medium (WM: Wireless Medium). STA may be a logical entity that is a single addressable instance. It may also be a communication device that uses a wireless medium. Furthermore, STA may include AP (Access Point) having the function of a base station and / or non-AP STA having the function of a terminal. In other words, STA may be an AP. Also, STA may be a non-AP STA. Also, STA may refer to both AP and non-AP STA. STA may also be called a terminal device.

[0018] Wireless media use PDUs (Protocol Data Units) between peer physical layer entities of a Wireless LAN. It may be a medium used to implement the transfer. A wireless medium may be referred to as a medium. A medium may be referred to as a medium.

[0019] A channel may be an instance of a radio medium used to transmit PPDUs between two or more STAs.

[0020] An AP may include one STA and be an entity that provides access to distribution system services (DSS) via a wireless medium to associated STA(s). An AP may include an STA and a distribution system access function (DSAF). An AP may also be referred to as an STA. Good. In other words, AP can also be STA.

[0021] A non-AP STA (non-access point station) may be an STA that is not included within an AP. For example, a non-AP STA may be an HT STA. A non-AP STA may be a VHT STA. This is also acceptable. Non-AP STA may also be HE STA. Non-AP STA may also be EHT STA. A non-AP STA may also be a UHR STA. A non-AP STA is an STA other than the aforementioned STA. That is also acceptable. Non-AP STA may be referred to as STA.

[0022] Distribution system services are services provided by the distribution system (DS). It may also be a set of services. The distribution system access function is a function within the AP. The distribution system may also use MAC services and distribution system services to provide access between the distribution system and the wireless medium. The distribution system may be a system used to interconnect a set of BSSs and an integrated LAN in order to create an Extended Service Set (ESS).

[0023] The BSS may be a set of STAs that successfully synchronized using JOIN service primitives and a set of STAs using START primitive. For example, MLME-JOIN.confirm may be used as the JOIN service primitive. MLME-JOIN.confirm confirms synchronization with the BSS. It may be a primitive for doing so. MLME-JOIN.request may be used as the JOIN service primitive. MLME-JOIN.request is a primitive for requesting synchronization with BSS. This is also acceptable. For example, MLME-START.request may be used as the START primitive. Good. MLME-START.request may be a primitive for a MAC entity to request that a new BSS be started. A primitive is an internal signal in STA or AP. This is also acceptable. The internal signals referred to here may be internal signals used for information exchange between entities at different layers or different protocols, such as between an SME and an MLME, between an SME and a PLME, or between two MLMEs and a PLME.

[0024] An ESS is a set of one or more interconnected BSSs, which appear as a single BSS in the Logical Link Control (LLC) layer of an STA associated with any of these BSSs. It is also possible. An ESS (Extended Service Set) may have a connection path via a WM between one of the APs that are members of the ESS and a non-AP STA. An ESS may have overlapping coverage areas (areas) composed of multiple BSSs. An ESS may have multiple BSSs that are far apart, and the coverage covered by multiple BSSs may be considered as a wider coverage. It may be ranged. In other words, the communication area of ​​ESS may be the same as or wider than the communication area of ​​BSS alone. The communication area formed by ESS is called ESA (Extended Service Area). It may also be used.

[0025] An OBSS (Overlapping Basic Service Set) may be a BSS that operates on the same channel as the STA's BSS, and within (partially or entirely) its BSA (Basic Service Area).

[0026] Figure 2 shows an example of OBSS according to one aspect of this embodiment. In Figure 2, 202 203 may be AP#1. 203 may be STA#1. 204 may be STA#2. 201 may be BSS#1, which consists of 202, 203, and 204. 203 204 may be synchronized with 202. 206 may be AP#2. 207 may be STA#3. 208 may be STA#4. 205 may be BSS#2, which consists of 206, 207, and 208. 207 is 206 may be synchronized with 208. 202 may not be synchronized with 207. 202 may not be synchronized with 208. 206 may not be synchronized with 203. 206 may not be synchronized with 204. 201 and 205 may be BSS operating on the same channel. 205 may be considered an OBSS to 201. 201 may be considered an OBSS to 205. For example, 202 may receive a frame transmitted by 207. 204 may receive a frame transmitted by 207. 207 may receive a frame transmitted by 202. 207 may receive a frame transmitted by 204. For example, 202 may determine that the channel is busy while 207 is transmitting. 204 may determine that the channel is busy while 207 is transmitting. 207 may determine that the channel is busy while 202 is transmitting. 207 may determine that the channel is busy while 204 is transmitting.

[0027] A BSA may be a region that includes members of a BSS. A BSA may also include members of other BSSs. For example, in Figure 2, 201 is a BSA that includes 203, 204, and 207. This is also acceptable. Here, 207 may be another member of the BSS.

[0028] IBSS (Independent Basic Service Set) is a BSS that forms a self-contained network, and access to the DS is not available.

[0029] The addressable unit may be a station (STA). Physical and operational Characteristics may also be defined by modifiers placed before the STA term. For example, in the case of location or mobility, the addressable unit is fixed STA. ), mobile STA, and mobility STA may also be used. STA is A While the recipient can specify a dress code, it does not (generally) have to be a fixed location. STA is multiple It may have a number of different characteristics, each of which forms its function. This is also acceptable. For example, a single addressable unit may simultaneously possess the characteristics of a portable STA, a QoS STA, a dependent STA, and a hidden STA. That's fine.

[0030] The architecture provides a WLAN that transparently supports STA migration to the upper layers. It may consist of several interacting components. The BSS may be a fundamental component of the LAN. The range over which member STAs of the BSS can communicate may be considered the coverage area. The range is the set of all possible directional transmissions by member STAs. It may also be called BSA.

[0031] Physical limitations may determine the direct distance between STAs. An infrastructure BSS may be part of a network composed of multiple BSSs. The architectural component for interconnecting infrastructure BSSs may be a DS for non-General Link (non-GLK) operations. DS and Extended Service Sets (ESSs) may be mechanisms for extending connectivity for non-GLK operations. GLK operations use bridges. An extended network may be formed using these. The wireless medium and the DSM (Distribution System Medium) may be logically separated. Each logical medium has a different architecture. They may be used for different purposes by different components. Recognizing that multiple media are logically different is important for understanding the flexibility of the architecture. LAN The architecture is specified independently of the physical characteristics of a particular implementation. DS provides the logical services necessary for address-to-destination mapping and the seamless integration of multiple BSSs. This may enable support for mobile devices. The AP uses STA functionality and DSAF. It is an entity with a Distribution System Access Function (BSS) and may enable the associated STA to access the DS via wireless media. The data between the BSS and the DS is handled by the AP. It may travel via the internal DSAF. The AP may include an STA, and its STA address may be addressable on the radio medium. For the AP to communicate with the radio medium and DSM The addresses used do not necessarily have to be the same. Data sent from one of the STAs associated with the AP to the AP's STA address is always received on an uncontrolled port. It may be processed by the access entity. If the controlled port is authorized, the frame may conceptually pass through the DS.

[0032] A DS Service Access Point (SAP) is an interface between multiple DS SAP service users and DS SAP service providers. It may also be a face. A DS SAP service user may be a connected AP, mesh gate, portal, and AP MLD. A DS SAP service provider may also be a DS.

[0033] DS SAP may perform some or all of the following actions: MAC service tuples (MAC service tuples) -VistaPlu) is a collection of MPDUs, and is a port of AP, mesh gate, ESS. The data may be delivered via DS between the Tal and AP MLD. Mapping update This involved updating the APs via MAC service tuples distributed between STA and DS. It is also possible that the mapping update involves updating the mapping between the destination STA to which the DS delivers MAC service tuples and the APs to which that STA connects. The mapping update also involves updating the mesh gate through which the MAC service tuples delivered between the STA and the DS pass. This may also be the case. The mapping update is performed by the STA of the destination where the DS delivers MAC service tuples. This may involve updating the mapping between the STA and the mesh gate to which it is connected. The update is delivered via MAC service tuples between the non-AP MLD and DS, and then to the AP. This may involve updating the MLD. Mapping updates involve the DS distributing MAC service tuples. This may involve updating the mapping between the non-AP MLD of the destination being communicated and the AP MLD to which that non-AP MLD is connected. DS-STA-NOTIFY primitive is used for updating the mapping. It may be a primitive. The DS-STA-NOTIFY primitive may be generated by AP, Meshgate, or AP MLD. AP, Meshgate, and AP MLD may use the DS-STA-NOTIFY primitive to request a mapping update from DS SAP. For example, DS-STA-NOTIFY.request may be used as the DS-STA-NOTIFY primitive. The update may also be called a DS mapping update. a) AP, Meshgate, Portal, and AP MLD (part of MAC service tuples) (and) accept MSDU. b) AP, Meshgate, Portal, or AP MLD (as part of MAC service tuples) (Te) Distribute MSDU. c) Accept updates to the mapping between STA and AP from AP. d) Accept updates to the mapping between STA and mesh gates from mesh gates. e) Accept updates to the mapping between non-AP MLD and AP MLD from AP MLD.

[0034] When DS delivers MAC service tuples to AP, AP may decide when and how to deliver MAC service tuples to AP's MAC via MAC SAP. When DS delivers MAC service tuples to mesh gate, mesh gate may decide when and how to deliver MAC service tuples to mesh gate's MAC via MAC SAP. When DS delivers MAC service tuples to AP MLD through DSAF, AP MLD may decide when and how to deliver MAC service tuples to AP MLD's MLD upper MAC sublayer via MAC SAP. You may decide whether or not to distribute it via this method.

[0035] DS and Infrastructure BSS enable wireless networks of any size and complexity. A network may be constructed. This network may be called an ESS (Extensible Services Set). Good. An ESS is a collection of infrastructure BSSs connected by the same SSID, which may also be connected by DSs. An ESS does not necessarily contain a DS. For the LLC layer, an ESS is an IBSS. It may look the same. STAs within ESS can communicate, and mobile STA(s) are (same Within the ESS, movement between BSSs may be transparent to the LLC. In the ESS, the BSS is partial It may overlap. This may be commonly used to position coverage within a physical range. In ESS, BSS may be physically separated. In ESS, logically There may be no restrictions on the distance between BSSs. In ESS, BSSs are physically located in the same place. This may be done to provide redundancy. In an ESS, one or more IBSS(s) or ESS(s) may physically reside in the same location as one or more ESS(s).

[0036] Figure 3 shows an example of the device configuration of an STA according to one embodiment of this model. The STA may have an antenna unit SU1, an RF (Radio Frequency) unit SU2, a physical layer processing unit (PHY layer processing unit) SU3, a MAC layer processing unit SU4, and an upper layer packet processing unit SU5. The STA may also have a wireless transceiver unit SU6 and a frame processing unit SU7. The wireless transceiver unit SU6 connects the antenna unit SU1 and the RF The frame processing unit SU7 may be configured to include a physical layer processing unit SU3 and a MAC layer processing unit SU4. The RF unit SU2 transmits radio signals via the antenna unit SU1. Received the number.

[0037] The signal received by the RF unit SU2 is converted into a baseband signal and sent to the physical layer processing unit SU3. The physical layer processing unit SU3 performs processing related to the physical layer function (PHY function) on the converted baseband signal. The signal that has undergone processing at the physical layer in the physical layer processing unit SU3 is sent to the MAC layer processing unit SU4. The MAC layer processing unit SU4 performs processing related to the MAC layer function (MAC function) on the baseband signal. The signal that has undergone processing at the MAC layer in the MAC layer processing unit SU4 is sent as an upper layer packet to the upper layer packet processing unit SU5. The upper layer packet processing unit SU5 performs processing related to the upper layer function on the upper layer packet extracted from the received signal.

[0038] The upper layer packet processing unit SU5, when transmitting upper layer packets, processes information related to the functions of the upper layer. Processing is performed. The upper layer packet to be transmitted is sent from the upper layer packet processing unit SU5 to the MAC layer processing unit SU4. The MAC layer processing unit SU4 performs processing on the upper layer packet related to the MAC layer function. The frame after processing at the MAC layer in the MAC layer processing unit SU4 (the upper layer packet has been processed) The generated frame is sent to the physical layer processing unit SU3. The physical layer processing unit SU3 performs processing related to the physical layer's functions on the frame that has undergone processing at the MAC layer. The frame sent from the physical layer processing unit SU3 to the RF unit SU2 is converted into an RF signal and transmitted as a wireless signal via the antenna unit SU1.

[0039] The processing of the physical layer processing unit SU3 may be controlled by a PLME (Physical Layer Management Entity), which is an entity that controls the physical layer. The processing of the MAC processing unit SU4 may be controlled by an MLME (MAC Layer Management Entity), which is an entity that controls the MAC layer. PLME and MLME provide their respective layer management service interfaces. Furthermore, PLME and MLME may be controlled by an SME (Station Management Entity), which is an entity independent of the layer. PLME, MLME, and SME may be included in the frame processing unit SU7.

[0040] Figure 4 shows an example of the device configuration of an AP according to one aspect of this embodiment. The AP may include an antenna unit AU1, an RF unit AU2, a physical layer processing unit AU3, a MAC layer processing unit AU4, and a DSAF unit AU5. The DSAF unit AU5 may also have a higher layer packet processing function. Furthermore, the AP is capable of wireless transmission and reception. The unit may have a section AU6 and a frame processing section AU7. The wireless transceiver section AU6 may be configured to include an antenna section AU1 and an RF section AU2. The frame processing section AU7 may be configured to include a physical layer processing section AU3 and a MAC layer processing section AU4.

[0041] The signal received by the RF unit AU2 is converted into a baseband signal and sent to the physical layer processing unit AU3. The physical layer processing unit AU3 processes the converted baseband signal to determine the function of the physical layer. Processing is performed. The signal that has undergone processing in the physical layer processing unit AU3 is sent to the MAC layer processing unit AU4. The MAC layer processing unit AU4 processes the baseband signal, performing operations related to the MAC layer's functions. The MAC layer processing in MAC layer processing unit AU4 is sent to DSAF unit AU5 as a higher layer packet. DSAF unit AU5 then processes the higher layer packet extracted from the received signal. It performs processing related to the functions of the higher layer. In addition, the DSAF unit AU5 provides higher layer packets to the DS. That's good too.

[0042] The DSAF unit AU5 may acquire upper-layer packets from the DS. When transmitting upper-layer packets, the DSAF unit AU5 performs processing related to the functions of the upper layer. The packet is sent to the MAC layer processing unit AU4. The MAC layer processing unit AU4 performs processing related to the MAC layer's functions on the upper layer packet. The frame that has undergone MAC layer processing in the MAC layer processing unit AU4 (a frame generated by processing the upper layer packet) is sent to the physical layer processing unit AU3. The physical layer processing unit AU3 performs processing related to the physical layer's functions on the frame that has undergone processing at the MAC layer. The frame sent from the physical layer processing unit AU3 to the RF unit AU2 is converted into an RF signal and transmitted as a wireless signal via the antenna unit AU1.

[0043] The processing of the physical layer processing unit AU3 may be controlled by PLME. The processing of the MAC processing unit AU4 may be controlled by MLME. Furthermore, PLME and MLME are independent of the layer. It may be controlled by the SME, which is a type. PLME, MLME, and SME are connected to the frame processing unit AU7. It may be included.

[0044] MLD (Multi-Link Device) supports multiple affiliated STAs (STAs), and multiple It may also refer to a logical entity that can be manipulated using the series STA. The series STA is MLD It may also refer to an STA that provides link-specific MLD lower MAC sublayers and physical layer (PHY) services within the MLD. In other words, a family STA may be an STA belonging to an MLD. An MLD may have two STAs. An MLD may have three or more STAs. A series of STAs may be either AP or non-AP STAs. An AP MLD (Access Point Multi-Link Device) may be an MLD in which each of the STAs belonging to the MLD is an AP. A non-AP MLD (non-Access Point Multi-Link Device) may be an MLD in which each of the STAs belonging to the MLD is a non-AP STA. An MLO (Multi-Link Operation) may be an operation between two MLDs.

[0045] In MLD, the MAC layer may be divided into an MLD upper MAC sublayer and an MLD lower MAC entity. The MLD upper MAC sublayer is It may perform functions common to all links. MLD subordinate MAC entities are MLD and It may be shared between APs or non-AP STAs belonging to the MLD. MLD subordinate MAC entities Each link may perform local functions. Some functions may require co-processing of both the MLD upper MAC sublayer and the MLD lower MAC entities.

[0046] A Super MLD (Super Multi-Link Device) may be defined. A Super MLD is a multi-system A column MLD (affiliated MLD) may also be a logical entity that supports affiliated MLDs and can be operated using multiple series MLDs. A series MLD may also be an MLD that provides MLD-specific MAC sublayers and / or physical layer (PHY) services within a Super MLD. In other words, a series MLD may also be an MLD belonging to a Super MLD. A Super MLD can have two MLDs. It is permissible. There may be three or more MLDs belonging to Super MLD. Super MLD is Super It may be referred to by names other than MLD. For example, Super MLD can be referred to as Single Mobility Domain (SMD), Seamless Mobility Domain (SMD), Single Mobility Domain (SMD) MLD, Seamless Mobility Domain (SMD) MLD, non-colocated MLD, virtual MLD, or roming MLD, etc. It is also acceptable to refer to it as follows. A series MLD may be referred to as something other than a series MLD. MLD may include Super MLD. In other words, MLD may be a Super MLD. Also, an MLD that is not a Super MLD may be called a Normal MLD. Each MLD belonging to a Super MLD may be an AP MLD. Each MLD belonging to a Super MLD may be a non-AP MLD. In addition to MLDs, STAs may belong to a Super MLD. In addition to MLDs, APs may belong to a Super MLD. A Super MLD may be an AP MLD. A Super MLD may be a non-AP MLD. A Super MLD is an AP MLD. MLD may also be called Super AP MLD. Super AP MLD may be referred to by other names. For example, Super AP MLD may be called Single Mobility Domain (SMD) AP MLD, Seamless Mobility Domain (SMD) AP MLD, non-colocated AP MLD, virtual AP MLD, or roaming AP MLD, etc.

[0047] The MAC layer of Super MLD does not need to be divided into two or more MAC sublayers or MAC entities. The MAC layer of Super MLD may be referred to as Super MLD MAC entities, etc. Super MLD MAC entities may be referred to by names other than Super MLD MAC entities. Super MLD MAC entities may perform functions common to all MLDs. Super MLD MAC entities perform functions common to all MLDs belonging to Super MLD. The MLD upper MAC sublayer may be shared between the Super MLD and the AP MLDs belonging to that Super MLD. The MLD upper MAC sublayer performs functions local to each MLD. Alternatively, the MLD upper MAC sublayer may perform functions local to each MLD belonging to the Super MLD. Some functions may be performed by both the Super MLD MAC entity and the MLD upper MAC sublayer. Joint processing may be required.

[0048] Even if the MAC layer in Super MLD is divided into the Super MLD upper MAC sublayer and the Super MLD lower MAC entity, Good. The Super MLD upper MAC sublayer can be referred to in ways other than the Super MLD upper MAC sublayer. i. Super MLD lower MAC entities may be referred to by names other than Super MLD lower MAC entities. Super MLD upper MAC sublayers may perform functions common to all MLDs. Super MLD upper MAC sublayers perform functions common to all MLDs belonging to Super MLD. It is permissible. Super MLD subordinate MAC entities are Super MLD and APs belonging to Super MLD. It may be shared with MLD. Super MLD subordinate MAC entities have functions local to each MLD. The following may be performed: A Super MLD subordinate MAC entity may perform functions local to each MLD belonging to the Super MLD. A Super MLD subordinate MAC entity may perform some or all of the functions performed by an MLD subordinate MAC entity. In addition to or instead, a Super MLD subordinate MAC entity may perform some or all of the functions performed by an MLD upper MAC sublayer. A Super MLD subordinate MAC entity may be an MLD subordinate MAC entity. Alternatively, a Super MLD subordinate MAC entity may be split into an MLD upper MAC sublayer and an MLD subordinate MAC entity. Some functions may require joint processing by both the Super MLD upper MAC sublayer and the Super MLD subordinate MAC entity.

[0049] In two or more APs (Application Platforms) with MLD (Multiple Access Points), the upper MAC sublayer of the MLD may be common. The MLD upper MAC sublayer, which is common to all MLDs, may also be called the MLD common MAC sublayer or the MLD common upper MAC sublayer. The MLD common MAC sublayer may be referred to by other names. The MLD common MAC sublayer may perform functions common to all MLDs. The MLD common MAC sublayer may perform functions common to all MLDs belonging to the same Super MLD. Alternatively, the MAC layer of AP MLD may be divided into the MLD Common MAC Sublayer, the MLD Upper MAC Sublayer, and the MLD Lower MAC Entity. Some functions are performed by the MLD Common MAC Sublayer and the MLD Lower MAC Co-processing of both entities may be required. Some functions may require co-processing of both the MLD common MAC sublayer and Super MLD lower MAC entities. Some functions may require co-processing of both the MLD common MAC sublayer and the MLD upper MAC sublayer. Some functions may require co-processing of three or more MAC sublayers or MAC entities, such as the MLD common MAC sublayer, the MLD upper MAC sublayer, and the MLD lower MAC entities.

[0050] HT STA (High-Throughput STA) is measured at MAC Data Services Access Points (SAPs). The PHY and MAC may provide capabilities to support a specified throughput of 100 Mb / s or higher. The HT STA may also be a QoS STA. The HT feature may be used in an HT STA associated with an HT AP (High-Throughput AP). A subset of the HT feature may be used between two HT STAs that are members of the same IBSS. Some PHY features that distinguish HT STAs from non-HT STAs include multiple input multiple output (MIMO) operation, spatial multiplexing (SM), Spatial mapping (including transmit beamforming), spacetime block coding (STBC), low-density parity check (LDPC) coding, and antenna selection (ASEL) may be used. The permitted PPDU formats for HT STA may be non-HT format, HT-mixed format, and HT-greenfield format. In HT STA, PPDU may be transmitted with a 20 MHz bandwidth. In HT STA, PPDU may be transmitted with a 40 MHz bandwidth. HT STA may have MAC functionality including frame aggregation, several block ack features, low-power multipole (PSMP) operation, reverse direction (RD), and protection mechanisms to support coexistence with non-HT STA. good.

[0051] VHT STA (Very High-Throughput STA) supports the same features as HT STA, in addition to the other features supported by HT STA. The VHT STA may also support VHT functionality. The main PHY functions of the VHT STA may support 40MHz and 80MHz channel widths. The main PHY functions of the VHT STA may also support VHT single-user (SU) PPDUs. The main PHY functions of the VHT STA may also support 160MHz. Channel widths of 80+80MHz may be supported. VHT multi-user (MU)PPDUs may be supported as the main PHY function of VHT STA. The main PHY function of VHT is present in HT STA. It is not required. As a primary MAC function of VHT STA, A-MPDU padding of VHT PPDU may be supported. As a primary MAC function of VHT STA, S-MPDU may be supported. As a primary MAC function of VHT STA, bandwidth indication response may be supported. The MAC function does not need to be present in HT STA. The VHT function is VHT AP (Very High-Throughput). It may be used with VHT STA associated with AP). A subset of VHT functions is available in the same IBSS. It may be used between two VHT STAs that are members of the same group.

[0052] The operating channel width is the channel width that the STA can currently receive. That's fine.

[0053] HE (High Efficiency) STA can also be VHT STA when operating in the 5GHz band. i. A 20MHz-only HE STA does not need to support 40MHz and 80MHz channel widths. Support for a 20MHz operating channel width may be mandatory for HE STA. A 20MHz-only non-AP HE STA does not need to support 40MHz and 80MHz operating channel widths. This may be required. HE STA has operating channel widths of 160MHz and 80+80MHz. Support for this may be optional. HE STA may be HT STA. The main PHY features of HE STA that are not present in HT STA or VHT STA may be DL and UL OFDMA (Up Link Orthogonal Frequency Division Multiple Access) support. The main PHY features of HE STA that are not present in HT STA or VHT STA may be HE AP that supports four or more spatial streams when MU-MIMO (Multi User Multiple Input Multiple Output) is performed across the entire PPDU bandwidth. Support for DL ​​MU-MIMO (Down Link Multi User Multiple Input Multiple Output) It may be so. The main PHY function of HE STA that is not present in HT STA or VHT STA is non-AP HE STA It may also support DL MU-MIMO reception. The main HE STA that does not exist in HT STA or VHT STA. The MAC function may be support for the AP's OMI (Operating Mode Indication) responder and OMI initiator. The main MAC function of HE STA that is not present in HT STA or VHT STA may be support for the AP's individual TWT (Target Wake Time). The main MAC function of HE STA that is not present in HT STA or VHT STA may be support for non-AP STA's two NAV operation.

[0054] EHT (Extreme High Throughput) STA can operate in a bandwidth between 1 GHz and 7.250 GHz. For example, EHT STA may be HE STA at 5GHz and 6GHz. At 2.4GHz, the STA may be an HE STA. The EHT STA may use the operation element for HT and / or VHT and / or HE STA. The main PHY function of the EHT STA that is not present in HT STA, VHT STA, or HE STA is the support for MRU (Multiple Resource Unit). It may be present. The main PHY function of EHT STA that is not present in HT STA, VHT STA, or HE STA may be support for any type of preamble puncturing in non-OFDMA, which is necessary for supporting MRU (Multiple Resource Unit) in non-OFDMA. The main MAC function of EHT STA that is not present in HT STA, VHT STA, or HE STA may be support for MLO in the case of EHT AP. This is also acceptable. The main MAC function of EHT STA that is not present in HT STA, VHT STA, or HE STA may, in the case of MLD, be support for the ML (Multi-Link) discovery procedure. The main MAC function of EHT STA that is not present in HT STA, VHT STA, or HE STA may, in the case of MLD, be support for the ML (re)setup procedure. The main MAC function of EHT STA that is not present in HT STA, VHT STA, or HE STA may, in the case of MLD, be support for the ML BlockAck procedure. The main MAC function of EHT STA that is not present in HT STA, VHT STA, or HE STA may, in the case of MLD, be support for MLD level sequence number spaces. Support may be provided. Main MAC functions of EHT STA that are not present in HT STA, VHT STA, or HE STA. In the case of MLD, this may also be support for MLD level packet number space. The main MAC function of EHT STA, which is not present in HT STA, VHT STA, or HE STA, may be support for ML reconfiguration procedures in the case of MLD.

[0055] UHR (Ultra High Reliability) STA may operate in a bandwidth between 1 GHz and 7.250 GHz. For example, a UHR STA may be an EHT STA at 5GHz and 6GHz. For example, a UHR STA may be an HE STA at 5GHz and 6GHz. For example, a UHR STA may be a VHT STA at 5GHz and 6GHz. For example, a UHR STA may be an HE STA at 2.4GHz. For example, a UHR STA may be an HT STA at 2.4GHz. A UHR STA may support Super MLD. A UHR STA may support Seamless Roaming. A UHR STA may support HT and / or VHT. , and / or, operation elements for HE STA, and / or UHR STA may be used. In other words, UHR STA may be controlled by HT operation element, and / or VHT operation element, and / or HE operation element, and / or EHT operation element, and / or UHR operation element.

[0056] APs and STAs within a BSS may transmit based on CSMA / CA (Carrier Sense Multiple Access with Collision Avoidance). The CSMA / CA protocol is designed to reduce the probability of collisions at the point in time when collisions between multiple STAs accessing the medium are most likely to occur. The protocol used may also be acceptable.

[0057] HT BSS may be a BSS in which the Beacon frame transmitted by HT STA includes an HT Capabilities element. VHT BSS may be a BSS in which the Beacon frame transmitted by VHT STA includes a VHT Operation element. HE BSS may be a BSS in which the Beacon frame transmitted by HE STA includes an HE Operation element. It is also possible that the EHT BSS is a BSS in which the Beacon frame transmitted by the HE STA contains an EHT Operation element. For example, the HT BSS is a BSS that enables the HT STA to perform It may be configured with ported STAs. For example, VHT BSS may use the capability of VHT STA. It may be configured with ported STAs. For example, HE BSS supports HE capability It may be composed of STAs that support the capabilities of EHT. For example, EHT BSS supports the capabilities of EHT. It may be composed of STAs that support the capabilities of UHR. For example, UHR BSS may be composed of STAs that support the capabilities of UHR.

[0058] In this embodiment, STA may be, for example, HT STA, VHT STA, HE STA, EHT STA, or UHR STA. STA may also be any STA other than those described above.

[0059] AP and STA are frames of multiple frame types that share a common frame format. A frame may be sent. A frame may be defined at the physical layer, MAC layer, and Logical Link Control (LLC) layer, respectively.

[0060] A MAC frame may be a unit of data exchanged between MAC entities. A synonym for MAC frame may be MPDU. An MPDU (MAC Protocol Data Unit) may be a unit of data exchanged between two peer MAC entities using physical layer (PHY) data services. A synonym for MPDU may be MAC frame. An MSDU (MAC Service Data Unit) is a unit exchanged between MAC service access points (SAPs). The information may be distributed in this manner. The MAC frame in the STA may be processed by the MAC layer processing unit SU4. The MAC frame in the STA may be processed by the frame processing unit SU7. The MAC frame may be processed by the MAC layer processing unit AU4. The MAC frame in AP may be processed by the frame processing unit AU7.

[0061] A PHY frame may be a unit of data exchanged between PHY entities. A synonym for PHY frame may be PPDU. A PPDU (PHY Protocol Data Unit) may be a unit of data exchanged between two peer PHY entities using the Physical Layer (PHY) data service. A synonym for PPDU may be PHY frame. In STA, a PHY frame is a unit of data. The stratification processing unit SU4 may also process the PHY frame in STA. The PHY frame in AP may be processed by the physical layer processing unit AU4. The PHY frame in AP may be processed by the frame processing unit AU7.

[0062] The MAC frame format may consist of a MAC header, a Frame body, and an FCS. The MAC frame format consists of a set of fields that occur in a fixed order in all frames. It may be configured as follows.

[0063] The MAC header consists of the Frame Control field, Duration / ID field, and Address1 field. The MAC header may consist of fields such as Address2, Address3, Sequence Control, Address4, QoS Control, HT Control, etc. The MAC header may consist of all of the aforementioned fields. The MAC header may consist of some of the aforementioned fields.

[0064] Figure 5 shows an example of a MAC frame format according to one aspect of this embodiment. In Figure 5, the MAC frame format may consist of a MAC header, a Frame Body, and an FCS. In this case, the MAC header may consist of a Frame Control field, a Duration field, an Address1 field, an Address2 field, an Address3 field, a Sequence Control field, an Address4 field, and a QoS Control field. The MAC frame format may be MPDU.

[0065] The MAC header's Frame Control field is a Protocol Version subfield, Type subfield. Field, Subtype subfield, To DS subfield, From DS subfield More Fragments subfield, Retry subfield, Power Management subfield The MAC header may consist of subfields such as: Frame Control, More data subfield, Protected Frame subfield, +HTC subfield, Control Frame Extension subfield, Compressed SSID Present subfield, ANO Present subfield, BSS BW subfield, Security subfield, AP PM subfield, etc. The field may consist of some of the subfields mentioned above. The Frame Control field of the MAC header may consist of all of the subfields mentioned above. The Frame Control field in the MAC header determines the frame type, depending on the subframe. It may also be composed of combinations of Lud.

[0066] The frame type may also be indicated in the Type subfield within the Frame Control field of the MAC header. The frame type may be defined as Control frame, Management frame, or Data frame. It may be shown. For example, the Type subfield may be a 2-bit subfield. If the Type subfield is set to 00, the frame type may be a Management frame. If the Type subfield is set to 01, the frame type may be a Control frame. That's fine. If the Type subfield is set to 10, the frame type may also be a Data frame.

[0067] A Management frame may be a frame for managing the connection status between devices. A Control frame may be a frame for managing the communication status between devices. A Data frame may be a frame containing the actual data to be transmitted.

[0068] The Subtype subfield in the Frame Control field of the MAC header may indicate the frame's subtype. Possible frame subtypes include Association Request, Association Response, Reassociation Request, Reassociation Response, Probe Request, Probe Response, Beacon, ATIM, Disassociation, Authentication, Deauthentication, Action, B lock Ack Request, Block Ack, PS-Poll, RTS, CTS, Ack, CF-End, Data, QoS Data, etc. Any subtype may be defined. Other subtypes may also be defined.

[0069] The frame subtype may be determined from the Type and Subtype subfields contained in the Frame Control field of the MAC header. The Subtype subfield is 4 bits. It may also be a subfield of . If the Type subfield is set to 00, the Type subfield may indicate a Management frame. If the Type subfield is set to 01, the Type subfield may indicate a Control frame. If the field is set to 10, the Type subfield may indicate a Data frame.

[0070] For example, the Type subfield indicates a Management frame, and the Subtype subfield If 0000 is set, the subtype may be Association Request. The Type subfield indicates Management frame and the Subtype subfield is 0001. If configured, the subtype may be Association Response. In the table, the Management frame is shown, and the Subtype subfield is set to 0010. If present, the subtype may be a Reassociation Request. If the Type subfield indicates a Management frame and the Subtype subfield is set to 0011, the subtype may be a Reassociation Response. If a frame is shown and the Subtype subfield is set to 0100, the subtype may be a Probe Request. If the Type subfield shows a Management frame and the Subtype subfield is set to 0101, the subtype may be a Probe Response. It is also acceptable. The Type subfield indicates the Management frame, and the Subtype subfield If 1000 is set in the configuration, the subtype may be Beacon.

[0071] A Beacon frame may be a frame containing information such as the Beacon period and SSID. A Beacon frame may be a frame that is periodically sent to the STA in the BSS. An Association Response frame may be a frame containing information such as the Status code. An Association Response frame may be a frame that is sent as a response to a received Association request frame. An Association Response frame may be a frame containing information such as the Status code. It may also be a frame. A Reassociation Response frame may be a frame sent in response to an received Reassociation Request frame. A Probe Response frame is The frame may also contain information such as the Beacon's period and SSID. The Probe Response frame may be a frame sent as a response to a received Probe Request frame.

[0072] For example, if the Type subfield indicates Control frame and the Subtype subfield is set to 1011, the subtype may be RTS. If the Type subfield indicates Control frame and the Subtype subfield is set to 1100, the subtype may be CTS. If the Type subfield indicates Control frame and the Subtype subfield is set to 1101, the subtype may be Ack.

[0073] For example, the Type subfield indicates a Data frame, and the Subtype subfield is 00 If 00 is set, the subtype may be Data. If the Type subfield indicates a Data frame and the Subtype subfield is set to 1000, then the subtype This may also be QoS Data.

[0074] The Frame body field of the MAC frame format may consist of fields and elements defined for each subtype of management frame. The elements are displayed in the specified relative order, and non-existent fields or elements may be skipped. The frame body of the received management frame encounters an element ID that is not recognized. The STA then ignores that element and continues parsing the rest of the management frame body (if any) in search of additional elements with recognizable element IDs. In other words, the frame body of a management frame may contain one or more elements.

[0075] The element format of each element contained within the Frame body is determined by the Element ID field and Length field. Defined in fields, Element ID Extension fields, information fields, etc. This is also acceptable. The Information field may contain information specific to the element. For example, if the Element ID is 61, it may indicate the element for HT Operation. For example, Element If the ID is 191, it may indicate an element for VHT Capabilities. For example, if the Element ID is 192, it may indicate an element for VHT Operation. For example, if the Element ID is 255, it may indicate an element for HE Capabilities. For example, if the Element ID is 255, it may indicate an element for HE Operation.

[0076] The Capabilities element is information that indicates the capabilities supported by STA. It is also possible that the Capabilities element consists of multiple fields.

[0077] The HT Capabilities element consists of the Element ID field, Length field, HT Capability Information field, A-MPDU Parameters field, Supported MCS Set field, HT Extended Capabilities field, and Transmit Beamforming Capabilities field. The LDPC Capability may be defined in the ASEL Capabilities field. The HT Capability Information field is a subfield of the LDPC Coding Capability field, Supported Channel Width Set field. The HT Extended Capabilities field may consist of a main field, an SM Power Save subfield, etc. The HT Extended Capabilities field may consist of an MCS Feedback subfield, a +HTC-HT Support subfield, etc. Capabilities supported by the HT STA may be indicated by the HT Capabilities element. In other words, the HT Capabilities element may be a Capabilities element that indicates the capabilities supported by the HT STA.

[0078] The HT Capabilities element may also be sent in the Management frame. The element may be sent in a Control frame. The HT Capabilities element may be sent in a Data frame. For example, the HT Capabilities element may be sent in a Beacon frame. For example, the HT Capabilities element may be sent in the Association Request frame. For example, the HT Capabilities element may be sent in the Association Response frame. For example, the HT Capabilities element may be sent in the Reassociation Request frame. For example, the HT Capabilities element may be sent in the Reassociation Response frame. It may be sent. For example, the HT Capabilities element may be sent in the Probe Request frame. For example, the HT Capabilities element may be sent in the Probe Response frame. That's good too.

[0079] A VHT Capabilities element is defined by the Element ID field, Length field, VHT Capabilities Information field, and Supported VHT-MCS and NSS Set field. It is also acceptable. The VHT Capabilities Information field is the Maximum MPDU Length subfield. It may consist of a table, a Supported Channel Width Set subfield, an Rx LDPC subfield, etc. The capabilities supported by VHT STA are in the VHT Capabilities element. Therefore, it may be shown. In other words, the VHT Capabilities element is supported by VHT STA. It may also be a Capabilities element that indicates the capability.

[0080] A VHT Capabilities element may be sent in a Management frame. A VHT Capabilities element may be sent in a Control frame. A VHT Capabilities element may be sent in a Data frame. For example, a VHT Capabilities element may be sent in a Beacon frame. This may be done. For example, the VHT Capabilities element is sent in the Association Request frame. It may be sent in an Association Response frame. For example, a VHT Capabilities element may be sent in a Reassociation Request frame. For example, a VHT Capabilities element may be sent in a Reassociation Response frame. For example, a VHT Capabilities element may be sent in a Probe Request frame. For example, a VHT Capabilities element may be sent in a Probe Response frame.

[0081] The HE Capabilities element may be defined by the Element ID field, Length field, Element ID Extension field, HE MAC Capabilities Information field, HE PHY Capabilities Information field, Supported HE-MCS and NSS Set field, and PPE Thresholds field. The HE MAC Capabilities Information field is +HTC HE subfield, TWT Requester subfield, TWT Responder subfield, etc. It may be configured. The HE PHY Capabilities Information field is Supported Channel Width Set subfield, Punctured Preamble Rx subfield, Device Class subfield It may consist of fields, etc. The capabilities supported by HE STA may be indicated by the HE Capabilities element. In other words, the HE Capabilities element may be a Capabilities element that indicates the capabilities supported by HE STA.

[0082] The HE Capabilities element may also be sent in a Management frame. The element may be sent in a Control frame. The HE Capabilities element may be sent in a Data frame. For example, the HE Capabilities element may be sent in a Beacon frame. For example, the HE Capabilities element may be sent in the Association Request frame. For example, the HE Capabilities element may be sent in the Association Response frame. For example, the HE Capabilities element may be sent in the Reassociation Request frame. For example, the HE Capabilities element may be sent in the Reassociation Response frame. It may be sent. For example, the HE Capabilities element may be sent in the Probe Request frame. For example, the HE Capabilities element may be sent in the Probe Response frame. That's good too.

[0083] The EHT Capabilities element has an Element ID field, a Length field, and an Element ID The following fields may be defined: Extension field, EHT MAC Capabilities Information field, EHT PHY Capabilities Information field, Supported EHT-MCS And NSS Set field, and EHT PPE Thresholds field. The EHT MAC Capabilities Information field may consist of subfields such as EPCS Priority Access Support, EHT OM Control Support, TXS Mode 1 Support, TXS Mode 2 Support, etc. The EHT PHY Capabilities Information field may consist of subfields such as Support For 320 MHz In 6 GHz, Support For 242-tone RU In BW Wider Than 20 MHz, Partial Bandwidth UL MU-MIMO subfield, etc. EHT STA is Supported capabilities may be indicated by the EHT Capabilities element. In other words, the EHT Capabilities element may be a Capabilities element that indicates the capabilities supported by the EHT STA.

[0084] The EHT Capabilities element may be sent in a Management frame. The EHT Capabilities element may be sent in a Control frame. The EHT Capabilities element may be sent in a Data frame. For example, the EHT Capabilities element may be sent in a Beacon frame. This may be done. For example, the EHT Capabilities element is sent in the Association Request frame. It may be sent in an Association Response frame. For example, an EHT Capabilities element may be sent in an Association Request frame. For example, an EHT Capabilities element may be sent in an Association Response frame. For example, an EHT Capabilities element may be sent in an Association Response frame. For example, an EHT Capabilities element may be sent in a Probe Request frame. It may also be sent in a Probe Response frame. For example, the EHT Capabilities element may be sent in a Probe Response frame.

[0085] The UHR Capabilities element has an Element ID field, a Length field, and an Element ID Defined in some or all of the following fields: Extension field, UHR MAC Capabilities Information field, UHR PHY Capabilities Information field, Supported UHR-MCS And NSS Set field, UHR PPE Thresholds field, and / or other fields. It is also acceptable. The UHR MAC Capabilities Information field is used for UHR Link Reconfiguration. Support subfield, UHR Link Reconfiguration Mode 2 Support subfield, etc. It may consist of part or all of the above. Capabilities supported by UHR STA may be indicated by the UHR Capabilities element. That is, the UHR Capabilities element may be a Capabilities element that indicates the capabilities supported by UHR STA. The UHR Capabilities element may be referred to in ways other than the UHR Capabilities element. Also, UHR MAC Capabilities Information may be referred to in ways other than the UHR MAC Capabilities Information.

[0086] The UHR Capabilities element may be sent in a Management frame. The UHR Capabilities element may be sent in a Control frame. The UHR Capabilities element may be sent in a Data frame. For example, the UHR Capabilities element may be sent in a Beacon frame. This may be done. For example, the UHR Capabilities element is sent in the Association Request frame. It may be sent in an Association Response frame. For example, a UHR Capabilities element may be sent in a Reassociation Request frame. For example, a UHR Capabilities element may be sent in a Reassociation Response frame. For example, a UHR Capabilities element may be sent in a Probe Request frame. For example, a UHR Capabilities element may be sent in a Probe Response frame.

[0087] The UHR Link Reconfiguration Support subfield may also be a subfield indicating support for UHR Link Reconfiguration. That is, the UHR Link Reconfiguration Support subfield indicates whether or not the UHR STA supports UHR Link Reconfiguration. It may also be a subfield indicating the following. The UHR Link Reconfiguration Support subfield may be set to a first value if the UHR STA supports UHR Link Reconfiguration Mode 1 as described below. For example, the UHR Link Reconfiguration Support subfield may be set to 1 if the UHR STA supports UHR Link Reconfiguration Mode 1. The UHR Link Reconfiguration Support subfield may be set to a second value different from the first value if the UHR STA supports UHR Link Reconfiguration Mode 2 as described below. For example, the UHR Link Reconfiguration Support subfield may be set to 2 if the UHR STA supports UHR Link Reconfiguration Mode 2 as described below. The UHR Link Reconfiguration Support subfield may be set to a first value and a second value different from the first value if the UHR STA supports both UHR Link Reconfiguration Mode 1 and UHR Link Reconfiguration Mode 2 as described below. A third value different from the second value may be set. For example, UHR Link Reconfiguration The Support subfield may be set to 3 if the UHR STA supports both UHR Link Reconfiguration Mode 1 and UHR Link Reconfiguration Mode 2. For example, UHR The Link Reconfiguration Support subfield may be set to 0 if the UHR STA does not support UHR Link Reconfiguration. The UHR Link Reconfiguration Support subfield may be referred to by a name other than the UHR Link Reconfiguration Support subfield. "UHR STA" is referred to as "non-AP MLD" or "non-AP STA belonging to a non-AP MLD". It's okay if it's replaced.

[0088] The UHR Link Reconfiguration Mode 2 Support subfield is described below in UHR Link Reconf This may be a subfield indicating support for Iguration Mode 2, i.e., UHR Link. The Reconfiguration Mode 2 Support subfield may also be a subfield indicating whether or not the UHR STA supports UHR Link Reconfiguration Mode 2. For example, UHR The Link Reconfiguration Mode 2 Support subfield may be set to 1 if the UHR STA supports UHR Link Reconfiguration Mode 2. For example, the UHR Link Reconfiguration Mode 2 Support subfield may be set to 0 if the UHR STA does not support UHR Link Reconfiguration Mode 2. For example, both the UHR Link Reconfiguration Support subfield and the UHR Link Reconfiguration Mode 2 Support subfield may be set to 1 if the UHR STA supports both UHR Link Reconfiguration Mode 1 and UHR Link Reconfiguration Mode 2. "UHR STA" may be rephrased as "non-AP MLD" or "non-AP STA belonging to a non-AP MLD".

[0089] The UHR Link Reconfiguration Support subfield may be sent in the Management frame. The UHR Link Reconfiguration Support subfield may be sent in the Control frame. The UHR Link Reconfiguration Support subfield may be sent in a Data frame. For example, the UHR Link Reconfiguration Support subfield may be sent in a Beacon frame. For example, the UHR Link Reconfiguration Support subfield may be sent in an Association Request frame. For example, the UHR Link Reconfiguration Support subfield may be sent in an Association Response frame. For example, The Link Reconfiguration Support subfield may be sent in the Reassociation Request frame. For example, the UHR Link Reconfiguration Support subfield may be sent in the Reassociation Response frame. For example, the UHR Link Reconfiguration Support subfield may be sent in the Probe Request frame. For example, the UHR Link Reconfiguration Support subfield may be sent in the Probe Response frame.

[0090] The UHR Link Reconfiguration Mode 2 Support subfield is sent in the Management frame. It may be trusted. The UHR Link Reconfiguration Mode 2 Support subfield is Control It may be sent as a frame. UHR Link Reconfiguration Mode 2 Support subfield This may be sent in a Data frame. For example, the UHR Link Reconfiguration Mode 2 Support subfield may be sent in a Beacon frame. For example, the UHR Link Reconfiguration Mode 2 Support subfield may be sent in an Association Request frame. For example, the UHR Link Reconfiguration Mode 2 Support subfield may be sent in the Association Response frame. For example, the UHR Link Reconfiguration Mode 2 Support subfield may be sent in the Reassociation Request frame. For example, the UHR Link Reconfiguration Mode 2 Support subfield may be sent in the Reassociation Response frame. For example, the UHR Link Reconfiguration Mode 2 Support subfield This may also be sent in a Probe Request frame. For example, UHR Link Reconfiguration Mode 2. The Support subfield may be sent in the Probe Response frame.

[0091] UHR Link Reconfiguration Mode 1 is a frame used by a non-AP STA belonging to a non-AP MLD to request the addition of a link to the target AP MLD (see UHR Link Reconfiguration Mode below). When sending a Request Frame, the response to the additional request for a link to the target AP MLD. The transmission of Data Frames to APs belonging to the current AP MLD is stopped until a frame (UHR Link Reconfiguration Response Frame, described below) is received, and when a response frame for the request to add a link to the target AP MLD is received, the transmission of Data Frames to APs belonging to the target AP MLD is stopped. It may also be in the UHR Link Reconfiguration mode that initiates communication. That is, if a non-AP STA belonging to a non-AP MLD supports UHR Link Reconfiguration Mode 1, when sending a UHR Link Reconfiguration Request Frame, it will stop sending Data Frames to APs belonging to the current AP MLD until it receives a UHR Link Reconfiguration Response Frame, and when it receives a UHR Link Reconfiguration Response Frame, it will send Data Frames to APs belonging to the target AP MLD. You may start sending the Data frame. UHR Link Reconfiguration Mode 2 is used when a non-AP STA belonging to a non-AP MLD sends a frame (UHR Link Reconfiguration Request Frame, described below) to request the addition of a link to the target AP MLD The transmission of Data Frames to APs belonging to the current AP MLD will not stop until a response frame to the request for adding a link (UHR Link Reconfiguration Response Frame, described below) is received. Alternatively, when a response frame is received for an additional link request to the target AP MLD, it may be in UHR Link Reconfiguration mode, initiating the transmission of a Data frame to the APs belonging to the target AP MLD. That is, a non-AP STA belonging to a non-AP MLD will send a UHR Link Reconfiguration Request Frame if it supports UHR Link Reconfiguration Mode 2. When doing so, the current AP MLD will remain until it receives a UHR Link Reconfiguration Response Frame. Without stopping the transmission of Data Frames to the APs to which it belongs, UHR Link Reconfiguration Response Frame When receiving the target AP MLD, it may begin sending Data frames to APs belonging to the target AP MLD. If a non-AP STA belonging to a non-AP MLD does not support UHR Link Reconfiguration Mode 2, when sending a UHR Link Reconfiguration Request Frame, it will not begin sending Data frames to APs belonging to the current AP MLD until it receives a UHR Link Reconfiguration Response Frame. You may stop sending data frames and start sending data frames to APs belonging to the target AP MLD when you receive a UHR Link Reconfiguration Response Frame. The AP MLD and / or APs belonging to the AP MLD may support both UHR Link Reconfiguration Mode 1 and UHR Link Reconfiguration Mode 2. For example, the AP MLD and / or APs belonging to the AP MLD may set the UHR Link Reconfiguration Support subfield to 3. "Data frame" may be rephrased as "MSDU", "A-MSDU", or "PPDU", etc. "Do not stop sending data frames" may be rephrased as "Continue sending data frames", "Continue sending data frames", etc. "Non-AP STA belonging to a non-AP MLD" and "AP belonging to an AP MLD" may be rephrased as "non-AP MLD" and "AP MLD", respectively.

[0092] An Operation element may be information for controlling the operation of STA within BSS. An Operation element may consist of multiple fields.

[0093] The HT Operation element is defined by the Element ID field, Length field, Primary Channel field, HT Operation information field, and Basic HT-MCS Set field. The Primary Channel field may indicate the channel number of the primary channel. The HT Operation information field may indicate the Secondary Channel Offset field. The STA Channel Width field may also be included. The Secondary Channel Offset field may indicate the offset of the secondary channel relative to the primary channel. If the Secondary Channel Offset field is set to 1, the secondary channel may be positioned above the primary channel. If the Secondary Channel Offset field is set to 3, The secondary channel may be located below the primary channel. If the Secondary Channel Offset field is set to 0, the secondary channel may not exist. The STA Channel Width field may define the channel width that the STA can use for transmission. The STA Channel Width field may be set to 0 for 20MHz. The STA Channel Width field may allow the use of any channel within the supported channel width set. In total, 1 may be set. The operation of HT STA(s) within the BSS may be controlled by an HT Operation element. That is, an HT Operation element may be an operation element that controls the operation of HT STA within the BSS.

[0094] HT Operation elements may be sent in a Management frame. HT Operation elements may be sent in a Control frame. HT Operation elements may be sent in a Data frame. For example, an HT operation element may be sent in a Beacon frame. For example, an HT operation element may be sent in an Association Response frame. For example, an HT Operation element may be sent in a Reassociation Response frame. For example, the HT operation element may be sent in the Probe Response frame.

[0095] The VHT Operation element has an Element ID field, a Length field, and VHT Operation The information field may also be defined in the Basic VHT-MCS And NSS Set field. The VHT Operation information field consists of the Channel Width field, Channel Center Frequency Segment 0 field, and Channel Center Frequency Segment 1 field. The operation of VHT STA(s) within the BSS may be controlled by the HT Operation element and the VHT Operation element. In other words, the VHT Operation element controls the VHT STA(s) within the BSS. It may also be an operation element that controls the behavior.

[0096] A VHT operation element may be sent in a Management frame. A VHT operation element may be sent in a Control frame. A VHT operation element may be sent in a Data frame. For example, a VHT operation element may be sent in a Beacon frame. For example, the VHT operation element may be sent in the Association Response frame. For example, a VHT operation element may be sent in a Reassociation Response frame. For example, the VHT operation element may be sent in the Probe Response frame.

[0097] The Channel Width field in the VHT Operation information field is for HT operation The BSS bandwidth may be defined along with the element's STA channel width field. The Channel Width field may be set to 0 for a 20MHz or 40MHz BSS bandwidth. Good. The Channel Width field may be set to 1 for 80MHz, 160MHz, or 80+80MHz BSS bandwidth. The Channel Width field may be set to 2 for 160MHz BSS bandwidth. The Channel Width field may be set to 2 for 80+80MHz BSS bandwidth. 3 may be set. Values ​​in the Channel Width field ranging from 4 to 255 are reserved. That's fine.

[0098] Channel Center Frequency Segment 0 in the VHT Operation information field The channel is for VHT BSS at 20MHz, 40MHz, 80MHz, 160MHz, or 80+80MHz. You may define a center frequency. Channel Center Frequency Segment 0 field For a BSS bandwidth of 20MHz, 40MHz, or 80MHz, this may indicate the channel center frequency index of 20MHz, 40MHz, or 80MHz on which VHT BSS operates. The Channel Center Frequency Segment 0 field is for a BSS bandwidth of 160MHz and the Channel Width subfield is If 1, it may indicate the channel center frequency index of the 80 MHz channel segment containing the primary channel. The Channel Center Frequency Segment 0 field is the 160 MHz BSS. When the bandwidth and Channel Width subfield are 2, VHT BSS operates on a 160MHz channel. The channel center frequency index may also be shown. Channel Center Frequency Segment The 0 field has a BSS bandwidth of 80 + 80 MHz and a Channel Width subfield of 1 or 3. In this case, the channel center frequency index of the primary 80MHz channel of the VHT BSS may be shown.

[0099] Channel Center Frequency Segment 1 in the VHT Operation information field The code defines the channel center frequency for a VHT BSS of 160 MHz or 80+80 MHz. The Channel Center Frequency Segment 1 field may be set to 0 for BSS bandwidths of 20MHz, 40MHz, or 80MHz. The Channel Center Frequency Segment 1 field may be set to 0 for BSS bandwidths of 160MHz and Channel Width subfield is 1. The Channel Center Frequency Segment 1 field may indicate the channel center frequency index of the 160MHz channel on which the BSS operates. If the BSS bandwidth is 160MHz and the Channel Width subfield is 2, this field may be set to 0. If the BSS bandwidth is 80+80MHz and the Channel Width subfield is 1 or 3, the Channel Center Frequency Segment 1 field may indicate the channel center frequency index of the Secondary 80MHz channel of the VHT BSS. You may also show an example.

[0100] The HE Operation element format includes the Element ID field, the Length field, and the Element ID Extension field, HE Operation Parameter field, BSS Color Information field, Basic HE-MCS And NSS Set field, VHT Operation Information field Rudo, Max Co-Hosted BSSID Indicator field, 6GHz Operation Information field It may consist of a rd, etc. When operating in the 2.4GHz band, the HE STA in the HE BSS may be controlled by an HT Operation element and an HE Operation element. When operating in the 5GHz band, the HE STA in the HE BSS may consist of an HT Operation element and an VHT Operation element. If present, and may be controlled by an HE Operation element. When operating in the 6GHz band, the HE STA in the HE BSS may be controlled by an HE Operation element. In other words, the HE Operation element may be an operation element that controls the operation of the HE STA in the BSS.

[0101] HE operation elements may be sent in a Management frame. HE operation elements may be sent in a Control frame. HE operation elements may be sent in a Data frame. For example, an HE operation element may be sent in a Beacon frame. For example, an HE operation element may be sent in an Association Response frame. For example, an HE operation element may be sent in a Reassociation Response frame. For example, an HE operation element may be sent in a Probe Response frame.

[0102] The HE Operation Parameter field format of the HE Operation element format may consist of the Default PE Duration subfield, TWT Required subfield, TXOP Duration RTS Threshold subfield, VHT Operation Information Present subfield, Co-Hosted BSS subfield, ER SU Disabled subfield, 6GHz Operation Information Present subfield, Reserved subfield, etc. The VHT Operation Information Present subfield may be set to 1 to indicate that the VHT Operation Information field exists in the HE Operation element, and to 0 otherwise. The 6GHz Operation Information Present field may be set to 1 to indicate that the 6GHz Operation Information field exists, and to 0 otherwise.

[0103] The BSS Color Information field format of the HE Operation element format may consist of a BSS Color subfield, a Partial BSS Color subfield, a BSS Color Disabled subfield, and so on.

[0104] The 6GHz Operation Information field in the HE Operation element format may provide channel and bandwidth information related to 6GHz operation. The 6GHz Operation Information field format includes a Primary channel field, a Control field, a Channel Center Frequency Segment 0 field, and a Channel Center Frequency Segment 1 field. It may consist of a Minimum Rate field, etc. The Primary Channel field is The channel number of the primary channel at 6 GHz may also be indicated. The Channel Center Frequency Segment 0 field indicates the 20 MHz, 40 MHz, 80 MHz, 160 MHz of the BSS operating at 6 GHz, and This may indicate the channel center frequency index of the 80+80MHz channel. The Frequency Segment 0 field is used when the BSS channel width is 160MHz or 80+80MHz. The Channel Center Frequency Segment 1 field may indicate the channel center frequency index of the primary 80MHz channel. The Channel Center Frequency Segment 1 field may indicate the channel center frequency index of the 160MHz channel of the BSS operating at 6GHz. The Channel Center Frequency Segment 1 field may indicate the channel center frequency index of the secondary 80MHz channel if the channel width is 80+80MHz. The 6GHz Operation Information field format contains the Cont The rol field format may consist of a Channel Width field, a Duplicate Beacon subfield, a Regulatory Info subfield, a Reserved subfield, and so on. The Channel Width field indicates the BSS channel width and may be set to 0 for 20MHz, 1 for 40MHz, 2 for 80MHz, or 3 for 80+80MHz or 160MHz.

[0105] The EHT Operation element format may also be an Operation element for controlling an EHT STA operating in an EHT BSS. When operating in the 2.4GHz band, an EHT STA in an EHT BSS may be controlled by an HT Operation element, an HE Operation element, and an EHT Operation element. Good. When operating in the 5GHz band, the EHT STA in the EHT BSS may be controlled by the HT Operation element, VHT Operation element (if present), HE Operation element, and EHT Operation element. When operating in the 6GHz band, the EHT STA in the EHT BSS may be controlled by the HE Operation element and EHT Operation element.

[0106] The EHT Operation element format may consist of the following fields: Element ID, Length, Element ID Extension, EHT Operation Parameter, Basic EHT-MCS And Nss Set, and EHT Operation Information. The EHT Operation Information field is a Control field. The Control subfield may consist of a main field, a CCFS0 subfield, a CCFS1 subfield, and a Disabled Subchannel Bitmap subfield. The Control subfield may include a Channel Width subfield. The Channel Width subfield may be a subfield for defining the EHT BSS bandwidth. The Channel Width subfield may define a 20MHz EHT You may define 0 for the BSS bandwidth. The Channel Width subfield is 40MHz. For the EHT BSS bandwidth, 1 may be defined. For the Channel Width subfield, 2 may be defined for the 80MHz EHT BSS bandwidth. For a 160MHz EHT BSS bandwidth, 3 may be defined. Channel Width subfi The field may define 4 for a 320MHz EHT BSS bandwidth. CCFS0 subfeed The `CCFS0` subfield may define the center frequencies of the primary 80MHz channel for 20MHz EHT BSS, 40MHz EHT BSS, 80MHz EHT BSS, 160MHz EHT BSS, or the primary 160MHz channel for 320MHz EHT BSS. The CCFS0 subfield defines the 20MHz channel, 40MHz channel, and 80MHz channel on which the EHT BSS operates for the 20MHz BSS bandwidth, 40MHz BSS bandwidth, or 80MHz BSS bandwidth. The channel center frequency index may be indicated. The CCFS0 subfield may indicate the channel center frequency index of the primary 80MHz channel for a 160MHz BSS bandwidth. The CCFS0 subfield may indicate the channel center frequency index of the primary 160MHz channel for a 320MHz BSS bandwidth. The CCFS1 subfield may define the center frequency of the 160MHz EHT BSS or the 320MHz EHT BSS. The B-field may be set to 0 for the 20MHz BSS bandwidth, 40MHz BSS bandwidth, or 80MHz BSS bandwidth. The CCFS1 subfield may index the center frequency of the 160MHz channel for the 160MHz BSS bandwidth. The index may be the center frequency of the 320MHz channel for a 320MHz BSS bandwidth.

[0107] A-MSDU (Aggregate MSDU) is a sequence of A-MSDU subframes. Each A-MSDU subframe may consist of an A-MSDU subframe header followed by MSDU and padding 0-3. In this configuration, the A-MSDU subframe header may include the DA field, SA field, and Length field. The DA and SA fields may contain the values ​​passed in MA-UNITDATA.request and MAUNITDATA.indication primitives. The Length field may contain the MSDU The length may be included in octets (i.e., 8 bits).

[0108] Figure 6 shows an example of an A-MSDU according to one aspect of this embodiment. In Figure 6, the MAC frame format may consist of a MAC header, a Frame Body, and an FCS. Here, MAC header r may consist of a Frame Control field, a Duration field, an Address1 field, an Address2 field, an Address3 field, a Sequence Control field, an Address4 field, and a QoS Control field. The MAC frame format may be MPDU. The Frame Body may consist of n A-MSDU subframes. Each A-MSDU may consist of an A-MSDU subframe header, MSDU, and padding. The A-MSDU subframe header is a DA file. It may consist of a field, an SA field, and a Length field.

[0109] A-MPDU (Aggregate MPDU) is a sequence of one or more A-MPDU subframes and a variable amount of EOF. It may consist of padding. Each A-MPDU subframe may optionally be followed by an MPDU delimiter. It may consist of an MPDU. Each nonfinal A-MPDU subframe within an A-MPDU may have padding octets added to make the subframe length a multiple of 4 octets. The EOF Padding field may consist of an EOF Padding subframe field and an EOF Padding Octets field. The A-MPDU pre-EOF padding may refer to the contents of the A-MPDU without including the EOF Padding field. The MPDU delimiter consists of the EOF field, the Reserved field, and the MPDU Even if it consists of a Length field, a CRC field, and a Delimiter Signature field good.

[0110] Figure 7 shows an example of an A-MPDU according to one aspect of this embodiment. In Figure 7, the A-MPDU may consist of n A-MPDU subframe fields and an EOF Padding field. The n A-MPDU subframe fields may be referred to as A-MPDU pre-EOF padding. Each A-MPDU subframe field may consist of an MPDU delimiter field, an MPDU field, and a padding field. The MPDU delimiter field may consist of an EOF field and a Reserved field. Fields: MPDU Length field, CRC field, Delimiter Signature field The EOF Padding field may consist of an EOF Padding subframe field and an EOF Padding Octets field.

[0111] MSDU or MMPDU (MAC Management Protocol Data Unit) for smaller MAC-level files The process of splitting into MPDUs may also be called fragmentation. MAC is Fragmenting and reconstructing MSDUs or MMPDUs that are delivered in individually addressed MPDUs It is permissible.

[0112] Figure 8 shows an example of Fragmentation according to one aspect of this embodiment. The MSDU may be fragmented into n parts. The MSDU is divided into n Frame Bodies, and each Frame Body is assigned MAC HDR (header) and CRC (Cyclic Redundancy Check). That's fine.

[0113] A PPDU consists of components such as the PHY preamble, PHY header, and PSDU (PHY Service Data Unit). PPDU may also be assigned L-STF, L-LTF, and L-SIG. PPDU may also be assigned HT-STF, HT-LTF, and HT-SIG. PPDU may also be assigned VHT-STF, VHT-LTF, VHT-SIG-A, and VHT-SIG-B. The following may be assigned: PPDU may be assigned HE-STF, HE-LTF, HE-SIG-A, HE-SIG-B. PPDU may be assigned HT-STF, HT-LTF, HT-SIG in addition to L-STF, L-LTF, L-SIG. In addition to L-STF, L-LTF, and L-SIG, PPDU also includes VHT-STF, VHT-LTF, VHT-SIG-A, and VHT-SIG-B. The following may be assigned: In addition to L-STF, L-LTF, and L-SIG, PPDU may also be assigned HE-STF, HE-LTF, HE-SIG-A, and HE-SIG-B.

[0114] Figure 9 shows an example of a PPDU according to one aspect of this embodiment. In Figure 9, L-STF and L-LTF may be added to the PPDU in the PHY layer. In Figure 9, the PPDU is a PSDU, PHY It may consist of a preamble, PHY header, Tail, and Padding. Here, the PSDU may be an A-MPDU in the MAC sublayer. The A-MPDU may consist of multiple MAC frame formats. Here, one MAC frame format is a MAC header field, an A-MSDU field It may consist of an FCS field.

[0115] Figure 10 shows an example of a MAC data plane architecture for an MLD according to one aspect of this embodiment. The MAC data plane architecture may refer to processing involving the transmission of all or part of the MSDU. In the MLO, one or more links may be used for communication between the AP MLD and the non-AP MLD. During transmission, MAC services... The MSDU from the access point (SAP) undergoes the processing shown on the left side of Figure 10, followed by traffic identification. Based on the child (TID: Traffic Identifier), one or more MPDUs may be forwarded via TTLM (TID-To-Link Mapping) processing to one or more MLD subordinate MAC entities and then to the corresponding PHY SAP. During reception, MPDUs sent from different PHY SAPs may first pass through the MLD subordinate MAC entities, then undergo merging processing, pass through the remaining processing on the right side of Figure 10, and then one or more MSDUs may be delivered to the LLC layer via MAC SAP or to the DS via DSAF.

[0116] The functions of the MLD upper MAC sublayer may include some or all of the following: Authentication and association between AP MLD and non-AP MLD ), reassociation • Security associations such as PMKSA (Pairwise Master Key Security Association) and PTKSA (Pairwise Transient Key Security Association), and GTK (Group Temporal Key) Distribution of Keys) / IGTK (Integrity Group Temporal Key) / BIGTK (Beacon Integrity Group Temporal Key) • Assignment of SN (Sequence Number) / PN (Packet Number) for frames encrypted by PTK (Pairwise Transient Key) for individually addressed frames. • Assignment of SNs for multiple MSDUs addressed to a group • Power-saving buffering for individually addressed frames (AP MLD only) • PTK encryption / decryption of individually addressed frames • Selection of MLD lower MAC entities for transmission Merging MPDUs received from two or more links • Packet reordering to ensure packets are delivered in the correct order for each Block Ack session. picture • Block Ack scoreboarding for individually addressed frames through collaboration with MLD lower MAC entities. • Exchange / instruction of MLD-level management information via MLD subordinate MAC entities • Each STA in its own network has its own EDCA (Enhanced Distributed Channel Access). Access) Parameter Selection

[0117] The functionality of an MLD subordinate MAC entity may include some or all of the following: • Exchange / instruction of link-specific control information such as RTS / CTS, acknowledgements, and NDP (Null Data PPDU). • Power saving state and mode • MAC address filtering for frame reception • Block Ack scoreboarding for individually addressed frames through collaboration with the MLD upper MAC sublayer.

[0118] The functionality of the Super MLD MAC entity may include some or all of the following. The functionality of the Super MLD upper MAC sublayer may include some or all of the following. MLD common MAC sub The functionality of a layer may include some or all of the following: • Operations performed by two MLDs belonging to the same Super MLD • Operations performed by two MLDs belonging to different Super MLDs • Operations performed by one MLD belonging to Super MLD and one MLD not belonging to Super MLD • Operations performed by Super MLD and Normal MLD • Operations performed by the two Super MLDs • Operations performed by the two AP MLDs Seamless roaming between AP MLD and non-AP MLD Other operations between AP MLD and non-AP MLD • Security associations such as PMKSA and PTKSA, and distribution of GTK / IGTK / BIGTK. • Frames encrypted by PTK for individually addressed frames SN / PN assignment • Assignment of SNs for multiple MSDUs addressed to a group • Power-saving buffering of individually addressed frames • PTK encryption / decryption of individually addressed frames • Selection of Super MLD lower MAC entities for transmission • Selection of MLD lower MAC entities for transmission • Selection of MLD upper MAC sublayer for transmission Merging MPDUs received from two or more MLDs • Packet reordering to ensure packets are delivered in the correct order for each Block Ack session. picture • Block Ack scoreboarding for individually addressed frames through collaboration with Super MLD lower MAC entities. • Block Ack scoreboarding for individually addressed frames through collaboration with MLD lower MAC entities. • Block Ack scoreboarding for individually addressed frames through collaboration with the MLD upper MAC sublayer. • Exchange / instruction of MLD-level management information via Super MLD subordinate MAC entities • Exchange / instruction of MLD-level management information via MLD subordinate MAC entities • Exchange / instruction of MLD-level management information via the MLD upper MAC sublayer • Selection of the EDCA parameters for each MLD series • Selection of each AP MLD's own EDCA parameters

[0119] The functionality of a Super MLD subordinate MAC entity may include some or all of the following: Authentication, association, and reassociation between AP MLD and non-AP MLD • Power-saving buffering for individually addressed frames (AP MLD only) • PTK encryption / decryption of individually addressed frames • Selection of MLD lower MAC entities for transmission Merging MPDUs received from two or more links • Packet reordering to ensure packets are delivered in the correct order for each Block Ack session. picture • Block Ack scoreboarding for individually addressed frames through collaboration with MLD lower MAC entities. • Exchange / instruction of MLD-level management information via MLD subordinate MAC entities • Selection of EDCA parameters for each series STA • Exchange / instruction of link-specific control information such as RTS / CTS, acknowledgements, and NDP (Null Data PPDU). • Power saving state and mode • MAC address filtering for frame reception • Block Ack scoreboarding for individually addressed frames through collaboration with the Super MLD upper MAC sublayer.

[0120] The time interval between frames may also be called IFS (Inter Frame Space). STA is specified The carrier sense function may be used at the specified time interval to determine if the medium is idle. In other words, the STA may perform carrier sense for the duration of the IFS to determine whether the medium is idle or not.

[0121] Multiple types of IFS may be defined. For example, IFS may include RIFS (Reduced Inter Frame Space), SIFS (Short Inter Frame Space), PIFS (Priority Inter Frame Space), DIFS (DCF Inter Frame Space), AIFS (Arbitration Inter Frame Space), EIFS (Extended Inter Frame Space), SBIFS (Short Beamforming Inter Frame Space), BRPIFS (Beam Refinement Inter Frame Space), MBIFS (Medium Beamforming Inter Frame Space), and LBIFS (Long Beamforming Inter Frame Space).

[0122] The time interval may differ depending on the type of IFS. For example, PIFS has a longer time interval than SIFS. An IFS with a longer interval is also acceptable. DIFS may be an IFS with a longer time interval than PIFS. The type of IFS may provide a priority level for access to the wireless medium. In other words, an IFS with a short time interval may be an IFS with a high priority level for access to the wireless medium.

[0123] SIFS (Short Inter Frame Space) is the last symbol or signal of the previous frame. This may be the time from the end of the extension (if any) until the first symbol of the preamble for the next frame is seen on the wireless medium.

[0124] Priority Inter Frame Space (PIFS) may be used to control access to media in order to obtain priority access. PIFS may also be used to perform Clear Channel Assessment (CCA) on secondary 20MHz, secondary 40MHz, and secondary 80MHz channels before transmission at 40MHz, 80MHz, and 160MHz.

[0125] CCA (Clear Channel Assessment) is the process of determining the current usage status of a wireless medium. It is acceptable. CCA is a function at the physical layer for determining the current usage state of the wireless medium. It is also acceptable to refer to CCA as CCA function.

[0126] DIFS (DCF Inter Frame Space) may be used by an STA operating with DCF to transmit data frames (MPDUs) and management frames (MMPDUs). After an STA using DCF has successfully received a frame, the CS (Carrier Sense) mechanism determines that the medium is idle at the TxDIFS slot boundary, and the value of the STA's backoff counter is... If the value is zero, you may proceed with sending.

[0127] AIFS (Arbitration Inter Frame Space) may be used for QoS STAs that access media using EDCAF.

[0128] EIFS (Extended Inter Frame Space) may be used in DCF when the medium is immediately determined to be idle after receiving a frame with an incorrect FCS value.

[0129] The basic method of accessing MACs used by STAs may be DFC (Distributed Coordination Function). DCF ensures the same coordination across all STAs within the BSS when the network is operational. The functional logic may always be an active class adjustment function. DCF is one of CSMA / CA It may be a species. DCF may be a feature that needs to be implemented in all STAs.

[0130] The STA detects the medium and determines whether another STA is currently transmitting in order to transmit. If the medium is not busy, the STA may transmit. If interrupted, STA will postpone the transmission until the current transmission is complete.

[0131] In the CSMA / CA distributed algorithm, specified between frame exchange sequences. A gap exists in the specified period. The specified gap in the frame exchange sequence may be referred to as the IFS. The transmitting STA ensures that the medium is idle for a certain required period before attempting to transmit. This required period may be the specified gap in the frame exchange sequence. This required period may be referred to as the IFS. .

[0132] STA resets the backoff counter before attempting to transmit again after a delay or immediately after a successful transmission. The backoff counter may be initialized to a random value. The STA may decrement the backoff counter once every aSlotTime while the medium is idle. aSlotTime may be the time length of the slot. The slot time referred to here may be the time of the slot that the MAC uses to define the IFS. aSlotTime may also be a predetermined time length. It may also be a fixed time length (for example, in microseconds).

[0133] The basic media access protocol may be DCF. DCF is a protocol that allows CSMA / CA and media to be accessed via Through the use of a random backoff counter after the G state, media between compatible PHYs Enables automatic sharing. All individually addressed traffic will use an immediate positive acknowledgment (Ack frame), and if an Ack frame is not received, it will not send Resending is scheduled by the person in charge. Multiple STAs are waiting for the medium to become available. There is a possibility of collisions occurring, and the likelihood of collisions is highest when the medium transitions from busy to idle. Therefore, a random backoff procedure is necessary to resolve medium contention. An STA transmission can interfere with (collision with) other STA transmissions even if the carrier sense function (CS function) indicates the medium is not busy. Interference is expected. This may be specified if a response frame is not received.

[0134] STAs that wish to initiate the transfer of data frames or management frames using DCF may use a carrier sense mechanism to determine the busy / idle state of the medium. If the medium is busy, the STA will continue without interruption until the medium is determined to be idle during the IFS. It waits. Here, the type of IFS is when the transition to the last idle state is correctly received on the medium. If the detection is based on frames that were not detected, EIFS may be used. Otherwise, IFS The type may be DIFS. After the medium idles in DIFS or EIFS, the STA may generate a random backoff count for an additional delay time before transmission. However, if the backoff counter already contains a non-zero value, the selection of a random number is not required. The backoff counter may be a pseudorandom integer obtained by subtracting a uniform variance between [0, CW]. CW is an integer within the range of the values ​​aCWmin and aCWmax, which are characteristics of the PHY. It is also acceptable to have a value of CW greater than or equal to aCWmin and less than or equal to aCWmax. CW may also be called the Contention Window.

[0135] The contention window parameter may take the initial value of aCWmin. The contention window takes a series of values ​​each time an MPDU transmission attempt fails and any STA retry increases until the contention window reaches the value of aCWmax. The contention window maintains the value of aCWmax until it is reset when aCWmax is reached. If a data frame or management frame is successfully sent, the contention window may be reset to aCWmin. If SSRC reaches dot11ShortRetryLimit, the contention window may be reset to aCWmin. The set of contention window values ​​may be in ascending order as integers obtained by powers of 2 minus 1, starting from the PHY-specific aCWmin value and continuing up to the PHY-specific aCWmax. For example, if aCWmin is 7 and aCWmax is 255, the set of contention window values ​​would be 7, 15, 31, 63, 127. It may also be a set that includes 255.

[0136] For example, in OFDM PHY characteristics, with a 20MHz channel spacing, aSlotTime may be 9μs. In OFDM PHY characteristics, with a 20MHz channel spacing, aCWmin may be 15. In OFDM PHY characteristics, with a 20MHz channel spacing, aCWmax may be 1023.

[0137] A QoS facility may include an additional coordinating function called HCF (Hybrid Coordination Function), which is only available in a QoS network configuration. HCF may be implemented in all QoS STAs. HCF combines aspects of contention-based and contention-free access methods to provide prioritized, parameterized QoS access to the QoS STA via the wireless medium. It is a well-functioning system that continues to support non-QoS STA for best-effort transfers. It is also acceptable. HCF stands for EDCA (Enhanced Distributed Channel Access). Both access and HCCA (HCF controlled channel access) Features provided by may be included. HCF uses EDCA mechanisms for competition-based transfers. You may also use a competition-based channel access method called M. HCF is competition-free. A control channel access method called the HCCA mechanism may be used for the transfer.

[0138] HCCA (HCF Controlled Channel Access) is an individually addressed downlink For transmission, uplink transmission, and direct link transmission, QoS STA ensures that contention is handled. This may also be a channel access mechanism used by a Hybrid Coordinator (HC) to coordinate the use of a non-existent medium.

[0139] The EDCA mechanism uses eight different UP (User Priority) values ​​to send wireless media to the STA. It may provide differentiated distributed access. UP uses MSDU (MAC Service Data Unit) This is an associated value and may indicate how MSDU is processed. UP is the higher level of MAC. The MSDU may be assigned at the layer. UP may take any value from 0 to 7. The EDCA mechanism may define four ACs (Access Categories) to support traffic delivery using the STA's UP. ACs are QoS STA channels AC may be a label for a common set of EDCA parameters used to compete for and send MSDUs with a specific priority. AC may take one of the values ​​AC_BE, AC_BK, AC_VI, or AC_VO. AC_BE, AC_BK, AC_VI, and AC_VO may indicate access categories corresponding to best effort, background, video, and voice, respectively.

[0140] QoS (Quality of Service) functions (facilities) are parameterized and prioritized. Extended functions, channel access rules, and frame rates used to provide a QoS are also used. - It may be a mat, frame exchange sequence, or managed object. QoS STA is , or an STA that implements QoS functionality. A QoS AP is an AP that supports QoS functionality. Alternatively, a QoS BSS may also be a BSS that provides QoS functionality. This may include a QoS AP.

[0141] The QMF (QoS Management Frame) policy may be a policy that defines the AC of Management frames. The QMF service may be a service that determines the AC of EDCA that transmits Management frames according to the set policy. The QMF STA may be a STA that implements the QMF service. The QMF AP may be an AP that implements the QMF service. The QMF MLD may be an MLD that implements the QMF service. The Non-QMF STA may be a STA that does not implement the QMF service. The Non-QMF AP may be an AP that does not implement the QMF service. The Non-QMF MLD may be an MLD that does not implement the QMF service. The IQMF (Individually addressed QoS Management Frame) may be an individually addressed Management frame transmitted using the QMF service.

[0142] The EDCFA (Enhanced Distributed Channel Access Function) is a logical function within a QoS STA, and may determine when frames in a transmission queue with the relevant AC are permitted to be transmitted via the wireless medium using EDCA. There may be one EDCFA for each AC. The DCF and HCF may be defined to operate within the same BSS.

[0143] Each EDCFA may maintain a backoff counter measured in backoff slots. When the backoff procedure is called, the backoff counter is randomly selected from a uniform distribution from 0 to CW. ​​​​It may be set to an integer value selected randomly. AIFS may be defined as AIFSN × aSlotTime + aSIFSTime. For example, in OFDM PHY characteristics, with a 20MHz channel spacing, aSlotTime may be 9μs and aSIFTTime may be 16μs. AIFSN may differ for each AC. For example, if AC is AC_BK, AIFSN may be 7. If AC is AC_BE, AIFSN may be 3. If AC is AC_VI, AIFSN may be 2. i. If AC is AC_VO, AIFSN may be 2. CW may be in ascending order as integers obtained by subtracting 1 from a power of 2, starting from the PHY-specific CWmin value and continuing up to the PHY-specific CWmax. CWmin and CWmax may differ for each AC. For example, if AC is AC_BK, CWmin may be aCWmin and CWmax may be aCWmax. If AC is AC_BE, CWmin may be aCWmin and CWmax may be aCWmax. If AC is AC_VI, CWmin may be {(aCWmin+1) / 2}-1 and CWmax may be aCWmin. If AC is AC_VO, CWmin may be {(aCWmin+1) / 4}-1 and CWmax may be {(aCWmin+1) / 2}-1. In OFDM PHY characteristics, for a 20MHz channel spacing, aCWmin may be 15. In OFDM PHY characteristics, with a 20MHz channel spacing, aCWmax may be 1023. The STA may decrement its backoff counter once per aSlotTime period while the medium is idle. Each time an MPDU transmission attempt fails and any STA's retry count increases, it takes a series of the following values.

[0144] In HCF, the basic unit of allocation of the right to transmit to the wireless medium may be a TXOP. A TXOP (Transmission Opportunity) may be a time interval during which a specific QoS STA has the right to start a frame exchange sequence on the wireless medium. A TXOP may be defined by a start time and a maximum duration. A TXOP may be acquired by EDCA. That is, when a STA performs EDCA, it may acquire a TXOP. Figure 11 is a diagram showing an example of a backoff procedure according to an aspect of the present embodiment. In FIG. 11, the horizontal axis may be time. 1101 may be a transmission by STA#1. 11 02 may be an IFS. 1103 may be a backoff counter. 110

[0145] 3 may be referred to as a contention window. 1104 may be a transmission by STA#2. In FIG. 11, STA#2 may detect 1101 on the channel. While STA#2 detects 1 101, it may determine that the channel is busy. That is, 1101 may be a period during which the channel is determined to be busy. STA#2 may perform carrier sense and determine whether the channel is busy. When the period of 1101 ends and STA#2 determines that the channel is idle, it may perform carrier sense during the period of 1102. For example, 1102 may be a DIFS. 1102 may be an AIFS. If STA#2 is idle during the period of 1102, it may start 1103. 1103 decrements the backoff counter while the channel is idle. For example, six backoff counters may be generated in 1103. While the channel is idle, the backoff counter is decremented, and when the backoff counter becomes 0, STA#2 transmits. While detecting 1101, STA#2 may determine that the channel is busy. That is, 1101 may be a period during which the channel is determined to be busy. STA#2 may perform carrier sense and determine whether the channel is busy. When the period of 1101 ends and STA#2 determines that the channel is idle, it may perform carrier sense during the period of 1102. For example, 1102 may be a DIFS. 1102 may be an AIFS. If STA#2 is idle during the period of 1102, it may start 1103. 1103 decrements the backoff counter while the channel is idle. For example, six backoff counters may be generated in 1103. While the channel is idle, the backoff counter is decremented, and when the backoff counter becomes 0, STA#2 transmits. When the period of 1101 ends and STA#2 determines that the channel is idle, it may perform carrier sense during the period of 1102. For example, 1102 may be a DIFS. 1102 may be an AIFS. If STA#2 is idle during the period of 1102, it may start 1103. 1103 decrements the backoff counter while the channel is idle. For example, six backoff counters may be generated in 1103. While the channel is idle, the backoff counter is decremented, and when the backoff counter becomes 0, STA#2 transmits. Signal (1104) may be performed. Here, the backoff counter may be determined to be between 0 and CW. CW may be a value selected from a range of values ​​between aCWmin and aCWmax. The channel may be called the radio medium.

[0146] The carrier sense mechanism uses NAV (Network Allocation Vector) status and STA transmission. It may also be a mechanism that combines the physical carrier sense of the transmitter to determine whether the medium is busy or idle. The NAV is maintained by each STA, and the STA's CCA (Clear Channel Access) This may be an indicator of the period of time during which transmission to the wireless medium is not initiated by the STA, regardless of whether the Assessment function detects that the medium is busy.

[0147] The carrier sense mechanism in STA may be performed in the physical layer processing unit SU3 and / or the MAC layer processing unit SU3. The carrier sense mechanism in AP may be performed in the physical layer processing unit AU3 and / or the MAC layer processing unit AU3.

[0148] NAV may be a counter that counts down to 0 at a constant rate. STA may indicate that the virtual carrier sense is idle if the NAV counter is 0. STA may indicate that the virtual carrier sense is busy if the NAV counter is not 0. Physical and virtual carrier sensing functions may be used to determine the state of a medium. If either the physical or virtual carrier sensing function indicates busy, the medium may be considered busy. If both the physical and virtual carrier sensing functions indicate idle, the medium may be considered idle. Virtual carrier sensing may also be referred to as NAV. Good. NAV may be provided by all MACs. The NAV counter may be called a NAV timer.

[0149] The physical carrier sense function in the STA may be controlled by the physical layer processing unit SU3. The virtual carrier sense function in the STA may be controlled by the MAC layer processing unit SU4. The physical carrier sense function may be controlled by the physical layer processing unit AU3. The carrier sense function may be controlled by the MAC layer processing unit AU4. NAV in STA is the MAC layer The NAV in the AP may be controlled by the MAC layer processing unit SU4.

[0150] The STA may set NAV if the address field of the received frame is not its own address. When the STA receives at least one valid frame in the PSDU, it sets NAV in the PSDU. The STA may update the NAV using the information from any valid Duration field. The STA may update the NAV if the value indicated by the Duration field of the received frame is greater than the current NAV value. The STA may update the NAV if the RA (address) of the received frame is greater than the STA's own MAC address. If they are equal, the NAV will not be updated.

[0151] STA may maintain two NAVs. AP may maintain two NAVs. The two NAVs may be an intra-BSS NAV and a basic NAV. The intra-BSS NAV is controlled by an intra-BSS PPDU. The basic NAV may be updated by an inter-BSS PPDU. The basic NAV may be updated by an intra-BSS PPDU or a PPDU that cannot be classified as an inter-BSS PPDU. An STA maintaining two NAVs may indicate that the media is idle if the timers of both NAVs are 0. In other words, an STA maintaining two NAVs may indicate that the media is idle if the timers of both the intra-BSS NAV and the basic NAV are 0. The virtual CS indication may indicate that the media is busy if at least one of the two NAV timers is not 0. In other words, if an STA or AP maintaining two NAVs has a timer that is not zero on at least one Intra-BSS NAV or basic NAV, the virtual CS indication will indicate that the media is busy. You may show it.

[0152] The NAV may be a basic NAV. The NAV may also be an intra-BSS NAV. basic NAV It may also be called NAV. Intra-BSS NAV may also be called NAV. NAV is called basic NAV. This may be done. NAV may be called intra-BSS NAV. Basic NAV may be called NAV. Intra-BSS NAV may be called NAV.

[0153] Career Sense (CS) involves both physical and virtual mechanisms. It may be performed through both. Carrier sense may also be called a carrier sense function. Carrier sense may also be called a carrier sense mechanism. The virtual carrier sense mechanism is implemented by distributing reservation information that notifies of advance notice of media use. Exchanging RTS frames and CTS frames before the actual data frame may be one means of distributing media reservation information. The RTS frame and CTS frame are the actual data frame The Duration field defines the period during which the medium is reserved for sending an Ack frame. May include: RTS frames (sent by the originating STA) or CTS frames (destination The STA that receives the originating STA processes the media reservation. The STA receives from the originating STA. Even if it's not possible, you can still know that the media is intended to be used to send the data frame. The media reservation information is in the Duration / ID field of the individually addressed frame. It may be distributed via [platform name]. The Duration / ID field indicates the time (period) for which the media is reserved. The Duration / ID field may indicate the time the medium is reserved to end in the following Ack frame. For fragment sequences, the Duration / ID field This is the time the medium is reserved until the end of the Ack frame that follows the next fragment. This may also be shown. The RTS / CTS mechanism may function even when multiple BSSs using the same channel overlap. The media reservation mechanism may function across BSS boundaries.

[0154] The RTS (Request To Send) frame format includes the Frame Control field and the Duration field. It may include a RUD, RA field, TA field, and FCS field. The Duration field in the RTS frame format may indicate the time (in microseconds) required for transmitting the pending data or management frame, one CTS frame, one Ack frame, and three SIFSs. The RA field of the RTS frame may be the address of the STA that is the intended direct recipient of the addressed frame with a reservation. The TA field may be the address of the STA that transmits the RTS frame or the bandwidth signal TA of the STA that transmits the RTS frame.

[0155] The CTS (Clear To Send) frame format may include a Frame Control field, Duration field d, RA field, and FCS field. The Duration field of the CTS frame format transmitted in response to the RTS frame may be the result of subtracting the time required for transmitting the CTS frame and the SIFS for it from the Duration field of the previous RTS frame. That is, it may be the time required for transmitting the pending data or management frame, one Ack frame, and two SIFSs. If the CTS frame is the first frame of the exchange and the pending data or management frame requires an acknowledgment, the Duration field may be the time (in microseconds) required for transmitting the pending data or management frame, two SIFSs, and one Ack frame . If the CTS frame is the first frame of the exchange and the pending data or management frame does not require an immediate acknowledgment, the Duration field may be the time required for transmitting the pending data or management frame and one SIFS . If the CTS frame is a response to the RTS frame, the RA field of the CTS frame The `rd` bit is set to the address of the TA field of the RTS frame, and the individual / group bits are set to 0. It may be set to if the CTS frame is the first frame in a frame exchange, then the RA frame The field may be set to the MAC address of the sender.

[0156] Figure 12 is a diagram showing an example of a NAV according to one aspect of this embodiment. In Figure 12, horizontal The axis may represent time. For example, 1201 may be the timeline of AP#1's operation. 1202 may be the timeline of STA#1's operation. 1203 may be the timeline of AP#2's operation. It could be the production timeline. 1204 could also be the timeline for STA#2's operation. Good. 1201, 1202, 1203, and 1204 may be timelines on the same channel. 1205 may be an RTS frame. 1206 may be the NAV period for AP#1. 1207 may be a CTS frame. 1208 may be the NAV period for STA#2. It can be in between. 1209 can be a Data frame. 1210 is an AcK frame. It may be present. 1211 may be IFS. 1212 is Contention Window It may also be U (backoff counter, backoff procedure). STA#1 is 1205 to AP#2 It may be sent to [address]. AP#1 will receive 1205 and the duration indicated in the RTS Duration field will be [duration]. Alternatively, you can set it to 1206. When AP#2 receives 1205, it sends 1207 to STA#1. You may send a message. STA#2 may set 1208 for the period indicated in the CTS Duration field upon receiving 1207. STA#1 may send 1209 upon receiving 1207. AP#2 may send 1210 to STA#1 upon receiving 1209. AP#1 may start 1212 with 1211 after 1206 is finished, if the channel is idle. STA#2 If the channel is idle during the IFS period before transmitting 1207, AP#2 may start 1212 after 1208 has finished. There may be an IFS between 1205 and 1207. AP#2 may transmit 1207 if the channel is idle during the IFS period before transmitting 1207. There may be an IFS between 1207 and 1209. STA#1 may transmit 1209 if the channel is idle during the IFS period before transmitting 1209. If it's in dollars, you can send 1209. The time between 1209 and 1210 can be IFS. AP#2 will send 1210 if the channel is idle during the IFS period before sending 1210. You may believe this. Here, for example, AP#1 may be 202 in Figure 2. For example, STA#1 may be 207 in Figure 2. For example, AP#2 may be 206 in Figure 2. It may be present. For example, STA#2 may be 208 in Figure 2. 1201 is AP Alternatively, it may be the timeline of STA's operation. 1202 may be the timeline of AP or STA's operation. 1203 may be the timeline of AP or STA's operation. 1204 may be the timeline for AP or STA operation.

[0157] STA or AP may perform a frame exchange. For example, frame exchange The exchange occurs when STA or AP transmits RTS, and STA or AP transmits CTS in response to RTS. This may also be the case. For example, frame exchange may be when the STA or AP sends a trigger frame and the STA or AP sends a CTS in response to the trigger frame. For example, frame exchange is , when STA or AP sends MU-RTS and STA or AP sends CTS in response to MU-RTS It is also acceptable. For example, a trigger frame is used when the AP assigns a RU (Resource Unit) to the STA. It may be used for this purpose. The trigger frame may be a frame that contains at least a common Info field and / or a User Info List field. The common Info field may contain multiple STAs. It may be a field for notifying common information. The User Info List field may contain zero or more User Info fields. Each User Info field assigns a RU to each STA. It may also be a field for that purpose. For example, the User Info field may include the RU allocation subfield.

[0158] BSS transition refers to the transition from one BSS to another within the same ESS by STA. It may also refer to a change in association. An association is the process of establishing a mapping between AP and STA, enabling STA invocation by distribution system services (DSSs), or AP MLD It may also refer to a service that establishes a mapping between and non-AP MLD and enables non-AP MLD invocation by DSS. A disassociation service is a service that removes an existing association. Yes, that's fine. Reassociation service is a service that transfers associations established between APs and STAs from one AP to another (or the same AP). It may also refer to a service. Authentication is the process of establishing the identity of a particular STA to prove that it is a member of a set of STAs that are permitted to connect to another STA, or the process of establishing the identity of a particular MLD to prove that it is a member of a set of MLDs that are permitted to connect to another MLD. It may also refer to a service used to establish proof of membership. Robust Security Network Association (RSNA) is the type of association used by a pair of STAs when the procedure for establishing authentication or association between them includes a 4-way handshake or the Fast BSS Transition (FT) protocol. It's acceptable. A 4-way handshake is when two parties use a Pairwise Master Key. It may be defined as a pairwise key management protocol that verifies mutual ownership of PMKs and distributes Group Temporal Keys (GTKs). A PMK may be a key derived from a key generated using the Extensible Authentication Protocol (EAP) method, or a key obtained directly from a pre-shared key (PSK). A GTK may be a temporary key used to protect information exchanged in group-addressed Data Frames.

[0159] The primary purpose of MAC sublayers is to transfer MSDUs between MAC sublayer entities. The information necessary for the distribution system service to operate is provided by the association services. The MSDU is processed by the distribution system service. Before being included, STA or MLD may be an "association".

[0160] A BSS transition may be defined for an STA or MLD. In a BSS transition, the movement of an STA from one BSS within a given ESS to another BSS within the same ESS is defined. This is also acceptable. In a BSS transition, each non-AP STA belonging to a non-AP MLD is within one BSS, and different non-AP STAs belonging to non-AP MLDs are in different BSSs, with one AP within one ESS. From MLD, each non-AP STA belonging to non-AP MLD is located within a different BSS, and belongs to non-AP MLD The movement of a non-AP MLD to another AP MLD within the same ESS may be defined when different non-AP STAs are in different BSSs. In a BSS transition, each non-AP STA belonging to a non-AP MLD is 1 Within one BSS, different non-AP STAs belonging to non-AP MLDs are located within different BSSs, and from one AP MLD within one ESS, the MLD MAC address of the non-AP MLD is transmitted to the MAC address of the non-AP STA. The movement of a non-AP MLD to become a non-AP STA by moving to another BSS within the same ESS, which is the same, may be defined. In a BSS transition, the movement of a non-AP STA to become a non-AP MLD by moving from a BSS within a given ESS to an AP MLD within the same ESS, where each non-AP STA belonging to the non-AP MLD is in a different BSS, different non-AP STAs belonging to the non-AP MLD are in different BSSs, and the MAC address of the non-AP STA is the same as the MLD MAC address of the non-AP MLD may be defined.

[0161] To deliver an MSDU within an ESS via a DS, the DS needs to know which AP or AP MLD within the ESS to deliver the MSDU to. This information may be provided to the DS through the concept of association. Association is necessary, but not sufficient, to support BSS-transition mobility. Association may be one of the services of the DSS. Even if a non-AP STA is associated with an AP before being allowed to deliver an MSDU via the AP, Good. A non-AP MLD may first be associated with an AP MLD before being permitted to distribute MSDUs via an AP MLD. In the case of a non-GLK STA that does not belong to an MLD, the act of connecting with an AP may invoke an association service and provide a mapping from the STA to the AP to the DS. In the case of a non-AP MLD, the act of connecting with an AP MLD may invoke an association service and provide a mapping from the non-AP MLD to the AP MLD to the DS.

[0162] At any given moment, a non-AP STA may connect to one AP, and a non-AP MLD may connect to one AP MLD. Once the association between the non-AP STA and the AP is complete, the non-AP STA will connect to the DS. You may make full use of it for communication. Similarly, when association is completed between a non-AP MLD and an AP MLD. Therefore, non-AP MLDs may communicate by making full use of DS. Associations between non-AP STAs and APs may always be initiated by non-AP STAs, not APs. Between non-AP MLDs and AP MLDs The association may always be initiated by a non-AP MLD, not necessarily by an AP MLD.

[0163] An AP may connect to multiple non-AP STAs simultaneously. Similarly, an AP MLD may connect to multiple non-APs simultaneously. You may connect it to MLD.

[0164] Non-AP STA learns which APs exist and what operational capabilities are available from each of them, and then establishes an association. An n service may be started. Similarly, a non-AP MLD may learn which MLDs exist and what operational capabilities are available from each of those AP MLDs and the APs belonging to each AP MLD, and then start an association service to establish an association with the AP MLDs.

[0165] In order to support BSS-transition mobility, additional functionality is required, and this machine The ability may be provided by a reaassociation service. Reassociation is a service of DSS. It may be one of the following.

[0166] The Reassociation service may be started to move the current association of an AP and a non-AP STA from one AP to the same AP or a different AP. The Reassociation service may be started to move the current association of an AP MLD and a non-AP MLD from one AP MLD to the same AP MLD or a different AP MLD. The Reassociation service may be started to move the current association of an AP and a non-AP STA to an association of an AP MLD and a non-AP MLD where the MLD MAC address of the non-AP MLD is the same as the MAC address of the non-AP STA. The Reassociation service may be started to move the current association of an AP MLD and a non-AP MLD to an association of an AP and a non-AP STA where the MAC address of the non-AP STA is the same as the MLD MAC address of the non-AP MLD.

[0167] In ESS, the reassociation service may notify the DS of the current mapping between APs and non-AP STAs, or between AP MLDs and non-AP MLDs. Furthermore, reassociation may allow non-AP STAs or non-AP MLDs to modify the association attributes of an established association while remaining connected to the same AP or AP MLD, respectively. Good. Reassociation may always be initiated by a non-AP STA or non-AP MLD.

[0168] The Authentication service is used in both ESS and IBSS, and all STAs communicate with each other. It may be used to establish its own identity. If a mutually acceptable level of authentication is not established between the two STAs, the association is not established. It is not necessary. An STA may be authenticated with many other STAs simultaneously. If authentication continues until reassociation, it may affect the speed at which STAs reassociate between APs, potentially limiting the performance of BSS-transition mobility. Using preauthentication removes the overhead of the authentication service from the time-critical reassociation process. It's okay if he dies.

[0169] An STA (local STA) for which dot11OCBActivated is false may keep an enumerated state variable for each STA (remote STA) that requires direct communication via WM. An MLD (local MLD) can communicate with a remote MLD from an STA belonging to the local MLD. It may also maintain a state variable listed for each MLD (remote MLD) that requires direct communication between two MLDs via WM to another STA to which it belongs.

[0170] This state variable may represent the relationship between local STA and remote STA. This state variable may also represent the relationship between local MLD and remote MLD. The state variable may take any of the following values. • State 1: Initial startup state of non-DMG STA performing authentication. Initial startup state of MLD performing authentication. Unauthenticated and unassociated. • State 2: Authenticated but unassociated . State 3: Authenticated and associated. Waiting for RSNA authentication. (Pending RSNA Authentication). State 4: Authenticated and associated. RSNA established. Alternatively, RSNA is not required (RSNA Established or Not Required).

[0171] Upon receiving the MLME-REASSOCIATE.request primitive, non-AP STAs, non-AP MLDs, and non-PCP (PBSS control point) STAs may perform reassociation with APs, AP MLDs, or PCPs, respectively, using the following procedures. If the STA or non-AP MLD is not connected within the same ESS, or if the status of the new AP, AP MLD, or PCP is State 1, the MLME-REASSOCIATE.confirm primitive may be issued to notify the SME that reassociation failed, and this process may be terminated. A non-AP STA may send a Reassociation Request frame to a new AP or PCP, or a non-AP STA belonging to a non-AP MLD may send a Reassociation Request frame containing a Basic Multi-Link element to an AP belonging to a new AP MLD. Unless otherwise specified, a non-AP STA belonging to a Non-AP MLD will send a Reassociation Request frame on the recommended link included in the MLME-REASSOCIATE.request primitive. You may start sending it. The Reassociation Request frame may include the RSNE (Robust Security Network Element) contained in the MLME-ASSOCIATE.request primitive. If a Reassociation Response frame with a status code indicating SUCCESS is received, the state variable of the new AP, AP MLD, or PCP may be set to State 4, or to State 3 if dot11RSNAActivated is true and the FT protocol is not being used for the new AP, AP MLD, or PCP. Unless the PCP and the new AP, AP MLD, or PCP are the same, the old AP, AP MLD, or PCP The state variable may be set to State 2. Also, MLME has a relationship with SME. You may issue the MLME-REASSOCIATE.confirm primitive to notify that it was successful. • The MLME-REASSOCIATION.request primitive has a new AP in the CurrentAPAddress parameter. If the MAC address of the AP MLD or PCP is stored (reassociation to the same AP, AP MLD, or PCP), the following states, agreements, and allocations may be deleted or reset to their initial values. 1) All EDCAF(Enhanced Distributed Channel Access Function) state 2) Any block ack agreements that are not GCR(GroupCast with Retries) agreements 3) Sequence number 4) Duplicate detection caches 5) Anything queued for transmission 6) Fragmentation and reassembly buffers 7) Power management mode 8) WNM(Wireless Network Management) sleep mode 9) TDLS(Tunneled Direct-Link Setup) agreements 10) TPKSAs (TDLS PeerKey Security Associations) established with any peers 11) TSPECs (Traffic SPECification) 12) DMG(Directional Multi-Gigabit) TSPECs 13) GLK-GCR agreement 14) MSCS(Mirrored Stream Classification Service) 15) SCS (Stream Classification Service) 16) TWT (Target Wake Time) • If the reassociation destination is the same AP and the existing association is not between MLDs, the following states, agreements, and allocations may not be affected by the reassociation procedure. 1) Enablement / Deenablement 2) GDD (Geolocation Database Dependent) enablement 3) MMSLs (Multiple MAC Sublayers Links) 4) GCR agreements that are not GLK-GCR agreements 5) DMS (Directed Multicast Service) agreements 6) TFS (Traffic Filtering Service) agreements 7) FMS (Flexible Multicast Service) agreements 8) Triggered autonomous reporting agreements 9) FTM (Fine Timing Measurement) sessions 10) DMG SP(Service Period) and CBAP(Contention Based Access Period) allocations 11) PTP (Peer-to-Peer) TSPECs. • In the case of reassociation to a different AP, AP MLD, or PCP, or in the case of reassociation to an AP where the new AP address is the same as the value of the CurrentAPAddress parameter and the existing association is between MLDs, or the new AP MLD address is the same as the CurrentAPAddress parameter If the value is the same as the previous value, and the existing association is not between MLDs, then for a reassociation to AP MLD, all of the above states, agreements, and allocations may be deleted or reset to their initial values.

[0172] If the AP or PCP receives a Reassociation Request frame from the STA, or if the AP MLD If the AP to which you belong receives a Reassociation Request frame containing a Basic Multi-Link element from a non-AP STA belonging to a non-AP MLD, the following procedure may be used. The MLME may issue an MLME-REASSOCIATE.indication primitive to notify the SME of a reassociation request. The SME may issue an MLME-REASSOCIATE.response primitive to the STA or non-AP MLD identified by the PeerSTAAddress parameter of the MLME-REASSOCIATE.indication primitive. If the reassociation fails, the SME may indicate the specific reason for the failure in the ResultCode parameter. MLME may send a Reassociation Response frame upon receiving the MLME-REASSOCIATE.response primitive. • Reassociation Response frame with status code indicating SUCCESS is STA or non-AP MLD If acknowledged by the non-AP STA to which it belongs, the status of the STA or non-AP MLD will be set to State 4, or dot11RSNAActivated will be true and reassociation will be fast. If it is not part of a BSS transition, it may be set to State 3. • AP or PCP is when the ResultCode of MLME-REASSOCIATE.response primitive is SUCCESS. If the CurrentAPAddress parameter of the MLME-REASSOCIATION.indication primitive is the MAC address of its own AP or PCP (reassociation to the same AP or PCP), then the treatment of the agreements and allocations of the non-AP STA described above will be consistent. The AP or PCP may delete or reset to its default values ​​any items (states, agreements, and allocations described above) that the non-AP STA has requested to be deleted or reset to their default values. The AP or PCP will treat the states, agreements, and allocations listed as unaffected by the reassociation procedure as follows: You don't need to change the allocations. • If the ResultCode of the MLME-REASSOCIATE.response primitive is SUCCESS and the CurrentAPAddress parameter of the MLME-REASSOCIATION.indication primitive is the MLD MAC address of the AP MLD itself (reassociation to the same AP MLD), the AP MLD will treat the agreements and allocations of the non-AP MLD as described above. Items requesting removal or reset to their initial values ​​(states, agreements, and allocations mentioned above) may be deleted or reset to their initial values. AP MLD may modify states, agreements, and allocations that are listed as unaffected by the reassociation procedure. You don't have to. • The ResultCode of the MLME-REASSOCIATE.response primitive is SUCCESS, and the CurrentAPAddress parameter of MLME-REASSOCIATION.indication is the MAC address of its own AP or PCP. If not, all states, agreements, and allocations of the connected STA (associating STA) described above may be deleted or reset to their initial values. If the ResultCode of the MLME-REASSOCIATE.response primitive is SUCCESS, and the CurrentAPAddress parameter of MLME-REASSOCIATION.indication is not the MLD MAC address of its own AP MLD, then all states, agreements, and allocations of the connected non-AP MLD (associating non-AP MLD) described above may be deleted or reset to their initial values. .

[0173] Fast BSS transition may aim to reduce the time during which connectivity is lost between STA and DS, or between non-AP MLD and DS, during BSS transition. FT (Fast BSS Transition) protocols are part of a reassociation service and may only apply when an STA or MLD moves to an AP or AP MLD within the same mobility domain in the same ESS. A mobility domain is a set of BSSs within the same ESS, and supports Fast BSS transitions between sets. You may do so.

[0174] The FT protocol is the initial association between STA and AP, or between non-AP MLD and AP MLD. It may be necessary to exchange information during the initial or subsequent reassociation. STAs and non-AP MLDs may be referred to as FT Originators (FTOs). APs and AP MLDs may be referred to as FT Responders (FTRs). The initial exchange may be referred to as an FT initial mobility domain association. Successive reassociations to FTRs within the same mobility domain may use FT protocols.

[0175] Even if two FT protocols are defined, such as the FT protocol and the FT resource request protocol... The FT protocol is executed when the FTO moves to the target FTR (target FTR). The protocol may not require a prior resource request. The resource request protocol is executed when an FTO requires a resource request before it can move. It may also be a protocol that can be used.

[0176] When an FTO travels to a target FTR using FT protocols, message exchange may be performed using one of two methods: Over-the-Air or Over-the-DS. In this case, the FTO may communicate directly with the target FTR using authentication by the FT authentication algorithm. In Over-the-DS, the FTO communicates with the current FTR. Communication with the target FTR may be done via the FTR. In Over-the-DS, communication between the FTO and the target FTR may be done via FT Action frames between the FTO and the current FTR. Furthermore, communication between the current FTR and the target FTR may be performed using an encapsulation method. In Over-the-DS, the current FTR switches between the two encapsulations. That's fine.

[0177] Seamless Roaming may be a process in which a terminal device transitions from one base station device to another. A terminal device may support multiple different frequency bands. A terminal device may communicate with another base station device using a different frequency band than the one used to communicate with the first base station device. A terminal device may transition to another base station device using a different frequency band while still communicating with the first base station device using a certain frequency band. A terminal device may be a STA (Stand-Ahead) device. A terminal device may have a non-AP MLD (Multi-Level Terminal Device) built-in. i. The terminal device may be a set of multiple STAs. The terminal device may be a set of multiple non-APs. The MLD may be built-in. The base station equipment may also be an AP. The base station equipment may have an AP MLD built-in. The base station equipment may be a set of multiple APs. The base station equipment may have multiple APs The MLD may be built-in. The base station equipment may also have a program with Super MLD functionality built-in. Good. Both of the above two base station devices communicate with each other via programs to enable Super MLD A program to implement the functionality may be built into the device. Another communication device connected to the two base station devices mentioned above may also have a program with Super MLD functionality built into it. A communication device with a program with Super MLD functionality built into it may include multiple base station devices, including the two base station devices mentioned above. It may be maintained. For example, it has a built-in program that has the functionality of Super MLD. The communication device connected to the two base station devices uses the Super MLD function to ensure that the sequence numbers assigned by the two base station devices to the frames transmitted to the terminal device are consecutive. Maintenance may be performed by transmitting signaling to the two base station devices from a program that has the following capabilities. For example, a program with Super MLD functionality is built in, and the two base station devices A communication device connected to two base station devices has a Super MLD function that ensures that the packet numbers assigned by the two base station devices to the frames transmitted to the terminal device are consecutive. Maintenance may also be performed by transmitting signaling from Gram to the two base station devices mentioned above. Both of the two base station devices have a built-in program that has Super MLD functionality. If present, the two base station devices mentioned above communicate with each other through programs to enable Super MLD The function may be implemented. For example, the two base station devices may be maintained by transmitting signaling between programs built into the base station devices so that the sequence numbers assigned to frames transmitted to the terminal device are consecutive. For example, the two base station devices may be maintained by transmitting signaling between programs built into the base station devices so that the packet numbers assigned to frames transmitted to the terminal device are consecutive. Seamless Roaming is when a non-AP MLD roams from one AP MLD to another, and that non-AP MLD remains in State 4 during and after roaming to the other AP MLD. It may also be called roaming. Seamless Roaming may be referred to by names other than Seamless Roaming. For example, Seamless Roaming may be called MLD Roaming, SMD Roaming, UHR BSS Transition, UHR Link Reconfiguration, MLD-based mobility, SMD-based mobility, Super MLD-based mobility, MLD-based BSS transition, SMD-based BSS transition, Super MLD-based BSS transition, MLD-based fast BSS transition, etc. "Roaming" is, It may also be called “transition,” “movement,” etc. “Roaming” may be rephrased as “transition,” “movement,” etc. Roaming may include BSS transition. Roaming may include reassociation. Roaming may include reassociation service. Roaming may include Fast BSS transition. Roaming may include MLOs. Super MLDs may be used in roaming. Two or more AP MLDs belonging to a Super MLD may be used in roaming. "A certain AP MLD" may be referred to as "current AP MLD," etc. "Another AP MLD" may be referred to as "target AP MLD," etc.

[0178] AP and / or STA may perform Seamless Roaming. AP MLD and / or non-AP MLD may perform Seamless Roaming. Super MLD and / or non-AP MLD may perform Seamless Roaming. Super AP MLD and / or non-AP MLD may perform Seamless Roaming may be performed. In seamless roaming, STA and / or non-AP MLD An STA belonging to an AP may send a frame to an AP belonging to an AP and / or AP MLD requesting roaming to the target AP MLD. An STA belonging to an STA and / or non-AP MLD may send a frame to an AP belonging to an AP and / or AP MLD requesting roaming to the target AP MLD. The Seamless Roaming procedure may be initiated by sending a frame to request roaming. For example, a “frame to request roaming to target AP MLD” is a frame to request the addition of a link to target AP MLD. It may also be a frame for requesting roaming to the target AP MLD. This may also be called a UHR Link Reconfiguration Request Frame. The UHR Link Reconfiguration Request Frame is a request from a non-AP MLD to the current AP MLD for the target AP MLD. It may be used to request the addition of a link. “Rambling to target AP MLD The "frame for questing" may also be a Reassociation Request frame. The "frame for requesting roaming to target AP MLD" may also be an FT Request frame, which is one of the FT Action frames. The "frame for setting up" may also be the Link Reconfiguration Request frame used in ML reconfiguration procedures. The "frame for doing so" may be a frame with a different name. In Seamless Roaming, APs belonging to AP and / or AP MLDs belong to STA and / or non-AP MLDs. You may send a frame to the STA in response to the roaming request to the target AP MLD. For example, “In response to the roaming request to the target AP MLD The frame for responding is a response frame to the additional request for a link to the target AP MLD. It may also be a frame. "Respond to a roaming request to target AP MLD" The frame for this purpose may also be called a UHR Link Reconfiguration Response Frame, etc. The UHR Link Reconfiguration Response Frame is sent by the current AP MLD in response to a UHR Link Reconfiguration Request Frame received from a non-AP MLD, and links to the target AP MLD. You may accept or reject the additional request to “target AP MLD”. The frame used to respond to a roaming request is called a Reassociation Response. It may also be a frame. "Respond to a roaming request to target AP MLD" The "frame for" is the FT Response frame, which is one of the FT Action frames. The "frame for responding to a roaming request to the target AP MLD" is the Link Reconfiguration Response frame used in ML reconfiguration procedures. It may be there. "A response to a roaming request to target AP MLD" The term "frame" may have other names. "Non-AP STA belonging to non-AP MLD" and "AP belonging to AP MLD" may be replaced with "non-AP MLD" and "AP MLD," respectively.

[0179] A non-AP STA belonging to a non-AP MLD may send a frame containing an information element with information related to Seamless Roaming. A non-AP STA belonging to a non-AP MLD may send a frame containing an information element with information related to Seamless Roaming when performing Seamless Roaming. When a non-AP STA belonging to a non-AP MLD sends a UHR Link Reconfiguration Request Frame, it may choose to stop sending Data Frames to APs belonging to the current AP MLD until it receives a UHR Link Reconfiguration Response Frame. To demonstrate this, the information element includes information related to Seamless Roaming. Frames may be sent. Non-AP STAs belonging to non-AP MLDs do not need to include an information element containing information related to Seamless Roaming in the frames they send if they do not perform Seamless Roaming. For example, information containing information related to Seamless Roaming The element may also be called a UHR Link Reconfiguration element. For example, an information element containing information related to Seamless Roaming may be called a UHR Link Reconfiguration operation element. For example, an information element containing information related to Seamless Roaming may be called a UHR operation element. For example, Seamless Roaming An information element containing related information may also be called a UHR Multi-Link element. Information elements containing information related to Seamless Roaming may be referred to as other than those mentioned above. This may be done in the following way: for example, an information element containing information related to Seamless Roaming. A frame containing an information element containing information related to Seamless Roaming may be a frame for initiating the Seamless Roaming procedure. For example, a frame containing an information element containing information related to Seamless Roaming may be It may also be a UHR Link Reconfiguration Request Frame. For example, a frame containing an information element with information related to Seamless Roaming may be an Association Request Frame. For example, a frame containing an information element with information related to Seamless Roaming may be a Reassociation Request Frame. For example, a frame containing an information element with information related to Seamless Roaming may be an FT Request Frame. This may also be the case. For example, an information element containing information related to Seamless Roaming. A frame containing the information element may be a Link Reconfiguration Request frame. A frame containing the information element, which contains information related to Seamless Roaming, may be any other Management frame.

[0180] Does a non-AP STA belonging to non-AP MLD support UHR Link Reconfiguration? Based on whether or not, you may decide whether or not to include an information element containing information related to Seamless Roaming in the frame you send. A non-AP STA belonging to a non-AP MLD may decide whether or not to include an information element containing information related to Seamless Roaming in the frame it sends, based on whether or not the current AP MLD and / or the target AP MLD support UHR Link Reconfiguration. A non-AP STA belonging to a non-AP MLD Based on whether or not UHR Link Reconfiguration Mode 2 is supported, the data to be sent will be sent. Whether or not to include an information element in the frame that contains information related to Seamless Roaming. You may make a judgment. For example, if a non-AP STA belonging to a non-AP MLD supports UHR Link Reconfiguration Mode 2, it may include a UHR Link Reconfiguration element containing a field indicating UHR Link Reconfiguration Mode 2 in the frame it sends to the AP belonging to the current AP MLD. For example, if a non-AP STA belonging to a non-AP MLD does not support UHR Link Reconfiguration Mode 2, it may include a UHR Link Reconfiguration element containing a field indicating UHR Link Reconfiguration Mode 1 in the frame it sends to the AP belonging to the current AP MLD. For example, if a non-AP STA belonging to a non-AP MLD does not support UHR Link Reconfiguration Mode 2, it may include a UHR Link Reconfiguration element containing a field indicating UHR Link Reconfiguration Mode 1 in the frame it sends to the AP belonging to the current AP MLD. If Reconfiguration Mode 2 is supported, a UHR Link Reconfiguration element containing the UHR Link Reconfiguration Mode subfield set to 1 may be included in the frame sent to the AP belonging to the current AP MLD. For example, if a non-AP STA belonging to a non-AP MLD does not support UHR Link Reconfiguration Mode 2, a UHR Link Reconfiguration element containing the UHR Link Reconfiguration Mode subfield set to 0 may be included in the frame sent to the AP belonging to the current AP MLD.

[0181] An Element ID may be set for the UHR Link Reconfiguration element. An Element ID may be set for the Reconfiguration operation element. An Element ID may be set for the UHR operation element. For the UHR Multi-Link element. An Element ID may be set. For example, the UHR Link Reconfiguration element may indicate information for UHR Link Reconfiguration. The UHR Link Reconfiguration element may consist of one or more fields. The UHR Link Reconfiguration element may include a field indicating the Element ID. The UHR Link Reconfiguration element may include a field indicating whether to stop sending Data Frames to APs belonging to the current AP MLD when a non-AP STA belonging to a non-AP MLD sends a UHR Link Reconfiguration Request Frame until it receives a UHR Link Reconfiguration Response Frame. It is also possible that the UHR Link Reconfiguration element includes fields to indicate the mode of UHR Link Reconfiguration. Fields other than those mentioned above may be included in the UHR Link Reconfiguration element. For example, a non-AP STA belonging to a non-AP MLD may, when sending a UHR Link Reconfiguration Request Frame, send a UHR Link Reconfiguration Request Frame. Stop sending Data Frames to APs belonging to the current AP MLD until a Response Frame is received. If so, a UHR Link Reconfiguration element containing a field indicating UHR Link Reconfiguration Mode 1 may be included in the frame sent to the AP belonging to the current AP MLD. Non-AP STAs belonging to non-AP MLDs send a UHR Link Reconfiguration Request Frame. When doing so, the current AP MLD will remain until it receives a UHR Link Reconfiguration Response Frame. If the transmission of data frames to the AP to which it belongs is not stopped, it will display UHR Link Reconfiguration Mode 2. A UHR Link Reconfiguration element containing a subfield may be included in the frame sent to an AP belonging to the current AP MLD. For example, a field in the UHR Link Reconfiguration element that indicates the mode of UHR Link Reconfiguration may be called the UHR Link Reconfiguration Mode subfield. The UHR Link Reconfiguration Mode subfield is included when a non-AP STA belonging to a non-AP MLD sends a UHR Link Reconfiguration Request Frame until it receives a UHR Link Reconfiguration Response Frame. This could be a subfield indicating whether to stop sending Data frames to the AP. For example, when a non-AP STA belonging to a non-AP MLD sends a UHR Link Reconfiguration Request Frame, it will continue sending until it receives a UHR Link Reconfiguration Response Frame from the current AP. If you stop sending Data frames to APs belonging to an MLD, the UHR Link Reconfiguration Mode subfield may be set to the first value (e.g., 0). For example, if a non-AP STA belonging to a non-AP MLD sends a UHR Link Reconfiguration Request Frame and does not stop sending Data frames to APs belonging to the current AP MLD until it receives a UHR Link Reconfiguration Response Frame, the UHR Link Reconfiguration Mode subfield may be set to a second value different from the first value (e.g., 1). For example, if a non-AP STA belonging to a non-AP MLD sends a UHR Link Reconfiguration Request Frame, it may set the UHR Link Reconfiguration Mode subfield to a second value different from the first value (e.g., 1). Stop sending Data Frames to APs belonging to the current AP MLD until a Response Frame is received. If so, a UHR Link Reconfiguration element containing the UHR Link Reconfiguration Mode subfield set to 0 may be included in the frame sent to the AP belonging to the current AP MLD. A non-AP STA belonging to a non-AP MLD, when sending a UHR Link Reconfiguration Request Frame, will not stop sending Data frames to the AP belonging to the current AP MLD until it receives a UHR Link Reconfiguration Response Frame, and will include a UHR Link Reconfiguration element containing the UHR Link Reconfiguration Mode subfield set to 1 in the frame sent to the current AP MLD. This may be included in frames sent to APs belonging to AP MLD.

[0182] For example, the UHR operation element may display information for controlling the UHR STA. For example, the UHR operation element may display information for UHR Link Reconfiguration. The UHR operation element may consist of one or more fields. The UHR operation element may include a field indicating the Element ID. The UHR operation element may include a field indicating whether the UHR operation element contains information related to UHR Link Reconfiguration. The UHR operation element is located in the non-AP MLD. The UHR operation element may include a field indicating whether the non-AP STA to which it belongs will stop sending data frames to APs belonging to the current AP MLD until it receives a UHR Link Reconfiguration Response Frame when it sends a UHR Link Reconfiguration Request Frame. The UHR operation element may include a field to indicate the mode of UHR Link Reconfiguration. If the UHR operation element indicates that information related to UHR Link Reconfiguration is included in the UHR operation element, then when the non-AP STA to which it belongs sends a UHR Link Reconfiguration Request Frame, it will stop sending data frames to APs belonging to the current AP MLD until it receives a UHR Link Reconfiguration Response Frame. It may include a field indicating whether to proceed or not. The UHR operation element may also include a field indicating the mode of UHR Link Reconfiguration if it indicates that information related to UHR Link Reconfiguration is included in the UHR operation element. Other fields may be included in the UHR operation element. For example, non-AP MLD Non-AP STAs belonging to this group will, when sending a UHR Link Reconfiguration Request Frame, send a UHR Link Reconfiguration Response Frame to the AP belonging to the current AP MLD until they receive a UHR Link Reconfiguration Response Frame. To stop sending Data frames, the field indicating UHR Link Reconfiguration Mode 1 is displayed. The frame sent to the AP belonging to the current AP MLD includes a UHR operation element. That's fine. Non-AP STAs belonging to non-AP MLDs will send a UHR Link Reconfiguration Request Frame until they receive a UHR Link Reconfiguration Response Frame. If the transmission of Data Frames to APs belonging to the AP MLD is not stopped, the UHR operation element containing a field indicating UHR Link Reconfiguration Mode 2 will be sent to the APs belonging to the current AP MLD. It may be included in the frame sent to [the destination].

[0183] For example, a UHR Multi-Link element may display information for controlling the MLD to which the UHR STA belongs. For example, a UHR Multi-Link element may display information for UHR Link Reconfiguration. A UHR Multi-Link element may consist of one or more fields. A UHR Multi-Link element may include a field indicating the Element ID. A UHR Multi-Link element may include a field indicating whether information related to UHR Link Reconfiguration is included in the UHR Multi-Link element. This means that when a non-AP STA belonging to a non-AP MLD sends a UHR Link Reconfiguration Request Frame, the current AP MLD will wait until it receives a UHR Link Reconfiguration Response Frame. The UHR Multi-Link element may include a field indicating whether to stop sending Data frames to APs belonging to the specified AP. The UHR Multi-Link element may include a field indicating the mode of UHR Link Reconfiguration. If the UHR Multi-Link element indicates that information related to UHR Link Reconfiguration is included in the UHR Multi-Link element, it may include a field indicating whether to stop sending Data frames to APs belonging to the current AP MLD when a non-AP STA belonging to a non-AP MLD sends a UHR Link Reconfiguration Request Frame until it receives a UHR Link Reconfiguration Response Frame. The UHR Multi-Link element may include a field indicating whether to stop sending Data frames to APs belonging to the current AP MLD when a non-AP STA belonging to a non-AP MLD sends a UHR Link Reconfiguration Request Frame until it receives a UHR Link Reconfiguration Response Frame. If it indicates that it is being used, it may include a field to indicate the mode of UHR Link Reconfiguration. Fields other than those mentioned above may be included in the UHR Multi-Link element. For example, a non-AP STA belonging to a non-AP MLD may be a UHR Link Reconfiguration Request When sending a Frame, if you stop sending Data Frames to APs belonging to the current AP MLD until you receive a UHR Link Reconfiguration Response Frame, you may include a UHR Multi-Link element containing a field indicating UHR Link Reconfiguration Mode 1 in the frame sent to the APs belonging to the current AP MLD. When a non-AP STA belonging to a non-AP MLD sends a UHR Link Reconfiguration Request Frame, if you do not stop sending Data Frames to APs belonging to the current AP MLD until you receive a UHR Link Reconfiguration Response Frame, then UHR A UHR Multi-Link element containing a field indicating Link Reconfiguration Mode 2 may be included in the frame sent to the AP belonging to the current AP MLD.

[0184] Information related to Seamless Roaming may include at least information indicating the UHR Link Reconfiguration mode. This information may also indicate whether a non-AP STA belonging to a non-AP MLD will stop sending Data Frames to APs belonging to the current AP MLD when sending a UHR Link Reconfiguration Request Frame, until it receives a UHR Link Reconfiguration Response Frame. Relevant information may include at least the UHR Link Reconfiguration Mode subfield. Non-AP STAs belonging to non-AP MLDs support at least one of UHR Link Reconfiguration Mode 1 or UHR Link Reconfiguration Mode 2, and are related to Seamless Roaming. APs belonging to the current AP MLD may send frames containing information related to Seamless Roaming. If an AP belonging to the current AP MLD receives a frame from a non-AP STA belonging to a non-AP MLD that contains information related to Seamless Roaming, it may decide whether or not to forward the data frame to an AP belonging to the target AP MLD based on the received information. For example, an AP belonging to the current AP MLD may send a frame containing information related to non-AP Frames received from non-AP STAs belonging to MLD have UHR Link Reconfiguration Mode 1 If the data frame contains information related to Seamless Roaming indicating that, it may be decided not to forward it to the APs belonging to the target AP MLD. For example, the APs belonging to the current AP MLD are Frames received from non-AP STAs belonging to non-AP MLDs contain UHR Link Reconfiguration If the data frame contains information related to Seamless Roaming indicating Mode 2, it may be decided to forward it to the AP belonging to the target AP MLD.

[0185] APs belonging to the current AP MLD transfer data frames to APs belonging to the target AP MLD. If it is determined that this is the case, the AP may forward the Data frame received from a non-AP STA belonging to a non-AP MLD to the AP belonging to the target AP MLD. For example, if an AP belonging to the current AP MLD receives a Data frame from a non-AP STA belonging to a non-AP MLD after a DS mapping update, it may forward that Data frame to the AP belonging to the target AP MLD until it sends a UHR Link Reconfiguration Response Frame. The AP belonging to the target AP MLD delivers the Data frame forwarded from the AP belonging to the current AP MLD to the DS as MAC service tuples. That's fine too. APs belonging to the current AP MLD will be transferred to the non-AP MLD after the DS mapping update. When a Data frame is received from a non-AP STA, the UHR Link Reconfiguration Response Fr After sending an AME, it is not necessary to forward that Data Frame to APs belonging to the target AP MLD. If an AP belonging to the current AP MLD receives a Data Frame from a non-AP STA belonging to a non-AP MLD before a DS mapping update, it is not necessary to forward that Data Frame to APs belonging to the target AP MLD. If an AP belonging to the current AP MLD receives a Data Frame from a non-AP STA belonging to a non-AP MLD before a DS mapping update, it may distribute that Data Frame to the DS as MAC service tuples.

[0186] In Seamless Roaming, non-AP MLDs roam from the current AP MLD to the target AP MLD. During roaming, context related to non-AP MLDs may be transferred from the current AP MLD to the target AP MLD. For example, in Seamless Roaming, the current AP When an AP belonging to this current AP MLD receives a frame from an STA belonging to a non-AP MLD requesting roaming to the target AP MLD, the MLD may begin forwarding the context related to the non-AP MLD to the target AP MLD. The text may include SN (Sequence Number). The content related to non-AP MLD "Kist" may include PN (Packet Number). "Context related to non-AP MLD" "T" may include PTK (Pairwise Transient Key). "Consequences related to non-AP MLD" The "text" may include PMK (Pairwise Master Key). The "context related to non-AP MLD" may include information about SCS (Stream Classification Service). The "context related to non-AP MLD" may include information about TWT (Target Wake Time). That's fine. The “context related to non-AP MLD” may include BA (Block Ack) agreements. The “context related to non-AP MLD” may also include other information related to non-AP MLD.

[0187] In Seamless Roaming, non-AP MLDs roam from the current AP MLD to the target AP MLD. During roaming, the current AP MLD may forward one or more frames to the target AP MLD. In Seamless Roaming, the current AP MLD forwards frames to the target AP MLD. The forwarded frames may include data frames sent from APs belonging to the current AP MLD and / or target AP MLD to STAs belonging to non-AP MLDs. In Seamless Roaming, frames forwarded from the current AP MLD to the target AP MLD are individually addressed. It may also include a QoS Data frame. In Seamless Roaming, frames forwarded from the current AP MLD to the target AP MLD are individually addressed Management frames. It may be included. In Seamless Roaming, the forwarding from the current AP MLD to the target AP MLD The frames may include IQMF. In Seamless Roaming, frames forwarded from the current AP MLD to the target AP MLD may include other types of frames.

[0188] Because MAC-level acknowledgments and retransmissions are built into the protocol, frames may be received multiple times. The procedure described in this document may attempt to filter out these duplicates. Filtering of duplicate frames is done using the Sequence Control field (consisting of sequence number and fragment number) in Data, Management, and Extension frames, the TID subfield within the QoS Control field in QoS Data frames, the ACI (Access Category Index) subfield within the Sequence Number field in QMFs (QoS Management Frames), and the Frame in PV1 (Protocol Version 1) Data frames. Include the PTID (Peer Traffic Indication) / Subtype subfield within the Control field. This may be promoted.

[0189] STA is used to determine the sequence number of a frame when sending a frame. MLD may maintain one or more sequence number spaces. When an STA belonging to an MLD sends an individually addressed QoS Data frame to an STA belonging to an associated MLD, the frame It may retain one or more sequence number spaces used to determine the sequence number.

[0190] Super MLD is used to determine the sequence number of a frame when an AP belonging to an AP MLD belonging to a Super MLD sends an individually addressed QoS Data frame to a non-AP STA belonging to a connected non-AP MLD (associated non-AP MLD). Alternatively, multiple sequence number spaces may be maintained. An “individually addressed QoS Data frame” may be referred to as a “frame”. The term "frame" may be rephrased as "frame." The aforementioned "frame" may include individually addressed QoS Data frames and other types of frames.

[0191] AP MLD3 and AP MLD4 are connected to non-APs that belong to AP MLD3 or AP MLD4. When sending individually addressed QoS Data frames to non-AP STAs belonging to MLD5 In this case, one or more sequences used to determine the sequence number of the frame Number spaces may be maintained. AP MLD3 and AP MLD4 belong to Super MLD. This is also acceptable. “Individually addressed QoS Data frame” may be referred to as “frame.” “Individually addressed QoS Data frame” may be rephrased as “frame.” The aforementioned “frame” may include individually addressed QoS Data frames and other types of frames.

[0192] If either MLD1 or MLD2 is a non-QMF MLD, MLD1 sends an individually addressed Management frame to the STA belonging to MLD2 via the STA belonging to MLD1. When doing so, a single sequence number space may be maintained that is used to determine the sequence number of the frame.

[0193] If any of the AP MLD3, AP MLD4, or non-AP MLD5 belonging to Super MLD is a non-QMF MLD, Super MLD may maintain a single sequence number space used to determine the frame sequence number when sending an individually addressed Management frame to a non-AP STA belonging to non-AP MLD5 via an AP belonging to AP MLD3 or AP MLD4. "AP MLD3 or AP MLD4" may also be referred to as "AP MLD3 and AP MLD4", "AP MLD3", etc. "AP MLD3 or AP MLD4" may also be referred to as "AP MLD3 This can also be rephrased as "AP MLD4", "AP MLD3", etc. "If any of the following are non-QMF MLDs: an AP MLD3 belonging to a Super MLD, an AP MLD4 belonging to a Super MLD, or a non-AP MLD5" is equivalent to "if any of the following are non-QMF MLDs: a Super MLD or a non-AP MLD5". It may also be called: “If any of the AP MLD3 belonging to Super MLD, or AP MLD4 belonging to Super MLD, or non-AP MLD5 is a non-QMF MLD” can be rephrased as “If either the Super MLD or non-AP MLD5 is a non-QMF MLD.” A "addressed Management frame" may also be referred to as a "frame." An "individually addressed Management frame" may be rephrased as a "frame." The aforementioned "frame" may include individually addressed Management frames and other types of frames.

[0194] If AP MLD3, AP MLD4, or non-AP MLD5 is a non-QMF MLD, then AP MLD3 and AP MLD4 belong to non-AP MLD5 via APs belonging to AP MLD3 or AP MLD4. When sending individually addressed Management frames to non-AP STAs, a single sequence number space is maintained which is used to determine the sequence number of the frame. It is also acceptable to use "AP MLD3 or AP MLD4" instead of "AP MLD3 and AP MLD4", "AP MLD3", etc. It may also be called "AP MLD3 or AP MLD4", "AP MLD3 and AP MLD4", or "AP MLD3 It can also be rephrased as follows: AP MLD3 and AP MLD4 may belong to Super MLD. In this case, either AP MLD3, AP MLD4, or non-AP MLD5 is a non-QMF MLD. In some cases, "Super MLD or non-AP MLD5 is a non-QMF MLD." It may also be called: “If AP MLD3 or AP MLD4 or non-AP MLD5 is a non-QMF MLD” is “If Super MLD or non-AP MLD5 is a non-QMF MLD” It may also be rephrased as “combined.” “Individually addressed Management frame” may also be referred to as “frame.” “Individually addressed Management frame” may also be rephrased as “frame.” The aforementioned “frame” may include individually addressed Management frames and other types of frames.

[0195] A QMF MLD is a single sequence used to determine the frame sequence number when an MLD transmits an IQMF to an STA belonging to another QMF MLD via an STA belonging to the MLD. A number space may be maintained for each AC.

[0196] If either AP MLD6 or AP MLD7 belonging to Super MLD is a QMF MLD, then Super MLD will not allow AP MLDs belonging to Super MLD to have APs belonging to that AP MLD. When sending IQMF to a non-AP STA belonging to another QMF MLD via this, the frame sequence A single sequence number space used to determine the Kens number is used for each AC. It may be retained. "If either AP MLD6 belonging to Super MLD or AP MLD7 belonging to Super MLD is a QMF MLD" is "If AP MLD belonging to Super MLD is a QMF MLD" It may also be referred to as "when Super MLD is QMF MLD," etc. "when either AP MLD6 belonging to Super MLD, or AP MLD7 belonging to Super MLD is QMF MLD" is "Super "When an AP MLD belonging to an MLD is a QMF MLD," "When a Super MLD is a QMF MLD," etc. They can be rephrased as follows: “AP MLD belonging to Super MLD” and “the AP MLD in question” It may also be referred to as “QMF MLD belonging to Super MLD” or “the said QMF MLD”. “AP MLD belonging to Super MLD” and “the said AP MLD” may be rephrased as “QMF MLD belonging to Super MLD” and “the said QMF MLD,” respectively. “IQMF” may also be referred to as “frame”. “IQMF” may also be rephrased as “frame”. The above-mentioned “frame” refers to IQMF and Other types of frames may also be included.

[0197] If either AP MLD6 or AP MLD7 is a QMF MLD, then AP MLD6 and AP MLD7 are QMF When an MLD transmits an IQMF to a non-AP STA belonging to another QMF MLD via an AP belonging to that QMF MLD, it may maintain a single sequence number space for each AC used to determine the sequence number of the frame. AP MLD6 and AP MLD7 may belong to a Super MLD. If "either AP MLD6 or AP MLD7 is a QMF MLD", It can also be referred to as "when AP MLD is QMF MLD," "when Super MLD is QMF MLD," etc. The phrase "If either AP MLD6 or AP MLD7 is a QMF MLD" may be rephrased as "If AP MLD is a QMF MLD", "If Super MLD is a QMF MLD", etc. "IQMF" may be referred to as "frame". "IQMF" may be rephrased as "frame". The aforementioned "frame" may include IQMF and other types of frames.

[0198] If multiple sequence number spaces are supported, the appropriate sequence number space may be determined by information from the MAC control fields of the transmitted frame. Each sequence number space starts at 0 and increments by 1 for each MSDU, A-MSDU, or MMPDU transmitted using that sequence number space. It may also be represented by a modulo 4096 counter. If dot11MACPrivacyActivated is true, the counter in each sequence number space may be set to a modulo 4096 random number when the STA's MAC address changes. If Super MLD maintains a sequence number space, Super MLD maintains the sequence number of frames transmitted by APs belonging to AP MLDs belonging to Super MLD. Numbers may be assigned consecutively. AP MLD1 and AP MLD2 hold the sequence number space. In this case, AP MLD1 and AP MLD2 may sequentially assign sequence numbers to frames transmitted by APs belonging to AP MLD1 or AP MLD2. AP MLD1 and belonging to Super MLD If AP MLD2 holds the sequence number space, then AP MLD1 and AP MLD2 are... Alternatively, even if you assign sequence numbers to frames transmitted by APs belonging to AP MLD2 in sequence good.

[0199] MPDUs contained within the same MSDU or A-MSDU may have the same sequence number. Different MSDUs or A-MSDUs may (with a high probability) have different sequence numbers.

[0200] The transmitting STA supports applicable sequence number spaces. Alternatively, MLD may support applicable sequence number spaces, indicated by a status of "Mandatory".

[0201] Super MLD may support applicable sequence number spaces with a status of "Mandatory". AP MLD1 and AP MLD2 may support applicable sequence number spaces with a status of "Mandatory".

[0202] STAs belonging to an MLD determine the sequence number of an individually addressed QoS Data frame sent to an STA belonging to another MLD, using the sequence number spatial identifier maintained by the MLD. You may also use a sequence number space identifier (Besshi).

[0203] APs belonging to an AP MLD belonging to a Super MLD may use the sequence number space identifier held by the Super MLD to determine the sequence number of an individually addressed QoS Data frame sent to a non-AP STA belonging to the connected non-AP MLD (associated non-AP MLD). An "individually addressed QoS Data frame" is a "frame". It may also be referred to as “an individually addressed QoS Data frame.” “An individually addressed QoS Data frame” may be rephrased as “a frame.” The aforementioned “frame” may include individually addressed QoS Data frames and other types of frames. “The sequence number space identifier held by Super MLD” may be a different sequence number space identifier from “the sequence number space identifier held by MLD.” “The sequence number space identifier held by Super MLD” may be the same sequence number space identifier as “the sequence number space identifier held by MLD.”

[0204] APs belonging to AP MLD3 or AP MLD4 determine the sequence number of the individually addressed QoS Data frame sent to the non-AP STA belonging to the connected non-AP MLD5. For this purpose, the sequence number space identifiers held by AP MLD3 and AP MLD4 may be used. AP MLD3 and AP MLD4 may also belong to Super MLD. A defined QoS Data frame may also be referred to as a "frame." An individually addressed QoS Data frame may also be referred to as a "frame." The aforementioned "frame" may include individually addressed QoS Data frames and other types of frames. The "sequence number space identifier held by AP MLD3 and AP MLD4" may be a different sequence number space identifier from the "sequence number space identifier held by MLD." The "sequence number space identifier held by AP MLD3 and AP MLD4" may be the same sequence number space identifier as the "sequence number space identifier held by MLD."

[0205] If either MLD1 or MLD2 is a non-QMF MLD, the STA belonging to MLD1 will send the sequence number of the individually addressed Management frame to the other STA belonging to MLD2. To determine the number, you may use the sequence number space identifier held by MLD1.

[0206] AP MLD3 belonging to Super MLD, or AP MLD4 belonging to Super MLD, or non-AP MLD If any of the 5 is a non-QMF MLD, APs belonging to AP MLD3 or AP MLD4 will send individually addressed Management frames to non-AP STAs belonging to non-AP MLD5. To determine the sequence number, the sequence number space identifier held by Super MLD may be used. "AP MLD3 or AP MLD4" may be referred to as "AP MLD3 and AP MLD4", "AP MLD3", etc. "AP MLD3 or AP MLD4" may be rephrased as "AP MLD3 and AP MLD4", "AP MLD3", etc. "If any of AP MLD3 belonging to Super MLD, or AP MLD4 belonging to Super MLD, or non-AP MLD5 is a non-QMF MLD" may be referred to as "If either Super MLD or non-AP MLD5 is a non-QMF MLD". "AP MLD3 belonging to Super MLD, or AP MLD4 belonging to Super MLD, or non-AP MLD5 If either of them is a non-QMF MLD, then either Super MLD or non-AP MLD5. This can be rephrased as "when it is a non-QMF MLD". An "individually addressed Management frame" may also be called a "frame". An "individually addressed Management frame" may also be rephrased as a "frame". The above-mentioned "frames" are individually It may include an addressed Management frame and other types of frames. The “sequence number space identifier held by Super MLD” is a different sequence number space identifier from the “sequence number space identifier held by MLD1”. This is also acceptable. The "sequence number space identifier held by Super MLD" may be the same sequence number space identifier as the "sequence number space identifier held by MLD1".

[0207] If AP MLD3, AP MLD4, or non-AP MLD5 is a non-QMF MLD, APs belonging to AP MLD3 or AP MLD4 will send individual messages to non-AP STAs belonging to non-AP MLD5. To determine the sequence number of the Management frame addressed to AP MLD3, You may also use the sequence number space identifier held by AP MLD4. "AP MLD3 or AP MLD4" may also be referred to as "AP MLD3 and AP MLD4", "AP MLD3", etc. "MLD3 or AP MLD4" can be rephrased as "AP MLD3 and AP MLD4", "AP MLD3", etc. This is also acceptable. AP MLD3 and AP MLD4 may belong to Super MLD. In this case, if "AP MLD3 or AP MLD4 or non-AP MLD5 is a non-QMF MLD", then "Super It may also be referred to as “when either MLD or non-AP MLD5 is a non-QMF MLD”. The phrase "If MLD3, AP MLD4, or non-AP MLD5 is a non-QMF MLD" can be rephrased as "If Super MLD or non-AP MLD5 is a non-QMF MLD." Good. “Individually addressed Management frames” may also be referred to as “frames.” “Individually addressed Management frames” may be rephrased as “frames.” The aforementioned “frames” may include individually addressed Management frames and other types of frames. “The sequence number space identifier held by AP MLD3 and AP MLD4” may be a different sequence number space identifier from “the sequence number space identifier held by MLD1.” “The sequence number space identifier held by AP MLD3 and AP MLD4” may be the same sequence number space identifier as “the sequence number space identifier held by MLD1.”

[0208] STAs belonging to a QMF MLD use the sequence number space identifier held by the QMF MLD to determine the sequence number of an IQMF that is sent to an STA belonging to another QMF MLD. That's good too.

[0209] If either AP MLD6 or AP MLD7 belonging to Super MLD is a QMF MLD, then APs belonging to that QMF MLD will transmit to non-AP STAs belonging to other QMF MLDs. To determine the sequence number of the IQMF, the sequence number space identifier held by the Super MLD may be used. If either AP MLD6 or AP MLD7 belonging to the Super MLD is a QMF MLD, then the sequence number space identifier held by the Super MLD is a QMF MLD. It may also be referred to as "when it is MLD", "when Super MLD is QMF MLD", etc. If either AP MLD6 belonging to D or AP MLD7 belonging to Super MLD is a QMF MLD "Combined" can be rephrased as "when an AP MLD belonging to Super MLD is a QMF MLD", "when Super MLD is a QMF MLD", etc. "IQMF" may be called "frame". "IQMF" may be rephrased as "frame". The above "frame" may include IQMF and other types of frames. "sequence number space held by Super MLD" The "identifier" may be a different sequence number space identifier from the "sequence number space identifier held by QMF MLD". The "sequence number space identifier held by Super MLD" may be the same sequence number space identifier as the "sequence number space identifier held by QMF MLD".

[0210] If either AP MLD6 or AP MLD7 is a QMF MLD, the AP belonging to that QMF MLD will determine the sequence number of the IQMF to be sent to the non-AP STA belonging to the other QMF MLD. , the sequence number space identifier held by AP MLD6 and AP MLD7 may be used. "When either AP MLD6 or AP MLD7 is a QMF MLD" may be referred to as "when AP MLD is a QMF MLD", "when Super MLD is a QMF MLD", etc. "When either AP MLD6 or AP MLD7 is a QMF MLD" may be rephrased as "when AP MLD is a QMF MLD", "when Super MLD is a QMF MLD", etc. "IQMF" may be referred to as "frame". "IQMF" may be rephrased as "frame". The above-mentioned "frame" may include IQMF and other types of frames. "The sequence number space identifier held by Super MLD" may be a different sequence number space identifier from "the sequence number space identifier held by AP MLD6 and AP MLD7". The "sequence number space identifier" held by MLD may be the same as the "sequence number space identifier held by AP MLD6 and AP MLD7".

[0211] STA or MLD may maintain one or more duplicate detection caches. If so, the record of that frame may be inserted into the appropriate cache. The record contains the sequence number and, if applicable, the frame's MAC control field (MAC). It may be identified by other information from control fields. If a Data, Management, or Extension frame is received in which the Retry subfield of the Frame Control field is equal to 1, the appropriate cache may search for a matching frame, if any. In DMG (Directional Multi-Gigabit), if a group-addressed frame is received, the appropriate cache may search for a matching frame. If a PV1 Data frame or PV1 Management frame is received, even if the Frame Control field does not have a Retry subfield, the appropriate cache may search for a matching frame, if any. The frame may be searched. If the search is successful, the frame may be considered a duplicate. Duplicate frames may be discarded. All non-AP STAs belonging to a non-AP MLD, when they receive a frame from an AP belonging to an AP MLD belonging to a Super MLD, will search the frame. Using the access number, it is sent from APs belonging to other AP MLDs belonging to the same Super MLD. Duplicate frames may be detected. All non-AP STAs belonging to non-AP MLD are AP When a frame is received from an AP belonging to an MLD, the sequence number of that frame may be used to detect duplicate frames sent from APs belonging to other AP MLDs.

[0212] Receiving STA (receiving STA) indicates that the status is "Mandatory" and applies. MLD may implement possible receiver requirements. MLD may implement applicable receiver requirements, indicated by a status of "Mandatory".

[0213] All STAs belonging to an MLD are instructed to discard duplicate, individually addressed QoS Data frames belonging to a TID without BA negotiation, sent from an STA belonging to another MLD. To assist the LD, identify the duplicate detection caches held by the MLD. You may use an identifier that does not require a specific identifier.

[0214] All non-AP STAs belonging to a non-AP MLD may use identifiers that identify duplicate detection caches held by the non-AP MLD to assist the non-AP MLD in discarding duplicate, individually addressed QoS Data frames belonging to TIDs without BA negotiation, which are sent from APs belonging to AP MLDs belonging to a Super MLD. “Duplicate, individually addressed QoS Data frames belonging to TIDs without BA negotiation” is defined as “duplicate frame It may also be called a "team". "Duplicate individual addresses belonging to a TID without BA negotiation" The specified QoS Data frame may also be referred to as a "duplicate frame." The aforementioned "duplicate frame" is a duplicate, individually addressed frame belonging to a TID that does not have a BA negotiation. This may include duplicate QoS data frames and other types of duplicate frames.

[0215] All non-AP STAs belonging to non-AP MLD3 are APs belonging to AP MLD4 or AP MLD5. To assist non-AP MLDs in discarding duplicate, individually addressed QoS Data Frames belonging to TIDs without BA negotiation that are transmitted, identifiers that identify duplicate detection caches held by non-AP MLDs may be used. AP MLD3 and AP MLD4 It may belong to Super MLD. A “duplicate, individually addressed QoS Data frame belonging to a TID without BA negotiation” may be called a “duplicate frame”. "Duplicate, individually addressed QoS Data frames belonging to a TID without negotiation" This can also be rephrased as “duplicate frames”. The “duplicate frames” mentioned above are duplicate, individually addressed QoS Data frames belonging to a TID without BA negotiation and It may also include other types of duplicate frames.

[0216] If either MLD1 or MLD2 is a non-QMF MLD, all STAs belonging to MLD1 may use identifiers that identify duplicate detection caches held by MLD1 to assist MLD1 in discarding duplicate, individually addressed Management frames sent from STAs belonging to the other MLD2.

[0217] If non-AP MLD3, AP MLD4 belonging to Super MLD, or AP MLD5 belonging to Super MLD is a non-QMF MLD, then all non-AP STAs belonging to non-AP MLD3 will assist non-AP MLD3 in discarding duplicate, individually addressed Management frames sent from APs belonging to AP MLD3 or AP MLD4, and will hold non-AP MLD3. Identifiers may be used to identify duplicate detection caches. "AP MLD4 or AP MLD5" may be referred to as "AP MLD4 and AP MLD5", "AP MLD4", etc. "AP MLD4 or AP MLD5" may be rephrased as "AP MLD4 and AP MLD5", "AP MLD4", etc. "When either non-AP MLD3, or AP MLD4 belonging to Super MLD, or AP MLD5 belonging to Super MLD is a non-QMF MLD" may be referred to as "When either non-AP MLD3, or Super MLD is a non-QMF MLD". The phrase "If either AP MLD4 or AP MLD5 belonging to Super MLD is a non-QMF MLD" can be rephrased as "If either non-AP MLD3 or Super MLD is a non-QMF MLD". It may be said that “duplicate individually addressed Management frames” may be referred to as “duplicate frames.” It may be said that “duplicate individually addressed Management frames” is a rephrased term for “duplicate frames.” The “duplicate frames” mentioned above may include duplicate individually addressed Management frames and other types of duplicate frames.

[0218] If non-AP MLD3, AP MLD4, or AP MLD5 is a non-QMF MLD, all non-AP STAs belonging to non-AP MLD3 will transmit from APs belonging to AP MLD3 or AP MLD4. Non-AP M should discard duplicate, individually addressed Management frames that are believed to be legitimate. To assist LD3, identifiers may be used to identify duplicate detection caches held by non-AP MLD3. "AP MLD4 or AP MLD5" may be referred to as "AP MLD4 and AP MLD5", "AP MLD4", etc. "AP MLD4 or AP MLD5" may be rephrased as "AP MLD4 and AP MLD5", "AP MLD4", etc. AP MLD4 and AP MLD5 are located in Super MLD It is acceptable to belong to either non-AP MLD3, AP MLD4, or AP MLD5. If either is a non-QMF MLD, then either non-AP MLD3 or Super MLD is a non-QMF It may also be referred to as “if it is MLD”. “non-AP MLD3, or AP MLD4, or AP MLD5”. The phrase “if either is a non-QMF MLD” may be rephrased as “if either a non-AP MLD3 or a Super MLD is a non-QMF MLD.” The phrase “duplicate individually addressed Management frames” may be referred to as “duplicate frames.” The phrase “duplicate frames” as described above may include duplicate individually addressed Management frames and other types of duplicate frames.

[0219] All STAs belonging to a QMF MLD may use identifiers that identify duplicate detection caches held by the QMF MLD to assist the QMF MLD in discarding duplicate IQMFs sent from STAs belonging to other QMF MLDs.

[0220] If either AP MLD6 belonging to Super MLD or AP MLD7 belonging to Super MLD is a QMF MLD, then all non-AP STAs belonging to QMF MLD are AP MLDs belonging to Super MLD or Therefore, the QMF MLD should discard duplicate IQMFs transmitted through APs belonging to that AP MLD. To assist in this, QMF MLD identifies duplicate detection caches it holds. You may use "child". If "AP MLD6 belonging to Super MLD, or AP MLD7 belonging to Super MLD is a QMF MLD", then "AP MLD belonging to Super MLD is a QMF MLD". It may also be referred to as "in the case of", "when Super MLD is QMF MLD", etc. The phrase "If either AP MLD6 or AP MLD7 belonging to Super MLD is a QMF MLD" can be rephrased as "If an AP MLD belonging to Super MLD is a QMF MLD", "If Super MLD is a QMF MLD", etc. "AP MLD belonging to Super MLD" and "the said AP MLD" are used interchangeably. These may be referred to as “QMF MLD belonging to Super MLD” and “the said QMF MLD.” “AP MLD belonging to Super MLD” and “the said AP MLD” may be rephrased as “QMF MLD belonging to Super MLD” and “the said QMF MLD,” respectively. “Duplicate IQMF” may be referred to as “duplicate frame.” It is also acceptable to use the term "duplicate IQMF" instead of "duplicate frame." The aforementioned "duplicate frame" may include duplicate IQMFs and other types of duplicate frames.

[0221] If either AP MLD6 or AP MLD7 is a QMF MLD, all non-AP STAs belonging to the QMF MLD may use identifiers that identify duplicate detection caches held by the QMF MLD to assist the QMF MLD in discarding duplicate IQMFs transmitted from other QMF MLDs through APs belonging to that QMF MLD. AP MLD6 and AP MLD7 are Super MLDs They may belong to one. "When either AP MLD6 or AP MLD7 is a QMF MLD" may be referred to as "when AP MLD is a QMF MLD", "when Super MLD is a QMF MLD", etc. "When either AP MLD6 or AP MLD7 is a QMF MLD" may be rephrased as "when AP MLD is a QMF MLD", "when Super MLD is a QMF MLD", etc. "Duplicate IQMF" may be referred to as "duplicate frame". "Duplicate IQMF" may be rephrased as "duplicate frame". The above-mentioned "duplicate frame" may include duplicate IQMF and other types of duplicate frames.

[0222] An A-MSDU contains only MSDUs of a single service class and may inherit that service class for the purposes of the following rules: For MSDUs or A-MSDUs belonging to the QoSAck service class when the receiver is a QoS STA, the QoS Data frame used to transmit these MSDUs or A-MSDUs may be a Normal Ack, Implicit BAR, PSMP Ack, or Block Ack. An ack policy of Ack may be used. When the recipient is a QoS STA and the MSDU or A-MSDU belongs to the QoS NoAck service class, the QoS Data frame used to send these MSDUs or A-MSDUs may have an ack policy of No Ack.

[0223] Figure 13 shows an example of the UHR Link Reconfiguration procedure according to one aspect of this embodiment. 1301 may be a non-AP MLD. 1301 may be a non-AP STA belonging to a non-AP MLD. 1302 may be a current AP MLD. 1302 may be an AP belonging to a current AP MLD. 1303 may be a target AP MLD. 1303 may be an AP belonging to target AP MLD. 1304 may be a DS. Good. In Figure 13, the vertical axis may represent time. 1305 may be the timeline of 1301's actions. 1306 may be the timeline of 1302's actions. 1307 may be the timeline of 1303's actions. 1308 may be the timeline of 1304's actions. 1309 may be the sending of a UHR Link Reconfiguration Request Frame to 1302. 1309 may be the receiving of a UHR Link Reconfiguration Request Frame from 1301. 1310 may be the updating of the AP MLD, which is traversed by MAC service tuples distributed between 1301 and 1304, from 1302 to 1303. 1310 may be the generation of a DS-STA-NOTIFY primitive by 1302. It is also acceptable for 1310 to be the generation of the DS-STA-NOTIFY primitive by 1303. i. 1310 may perform a DS mapping update. 1311 may send a UHR Link Reconfiguration Response Frame to 1301. 1311 may receive a UHR Link Reconfiguration Response Frame from 1302. 1301 may perform a DS mapping update. 1302 may send a frame to 2 before 1309. 1302 may receive a frame from 1301 before 1309. If 1302 receives a frame from 1301 before 1309, it may deliver that frame to 1304 before 1310. If 1301 supports UHR Link Reconfiguration Mode 1, For 1302, it is not necessary to send a frame after 1309. If 1301 supports UHR Link Reconfiguration Mode 1, it is not necessary to send a frame after 1309 to 1302. From time 1301 until time 1311, it is not necessary to send frames. From time 1301 until time 1309, it is not necessary to receive frames. 1301 is UHR Link Reconfiguration If Mode 2 is supported, send frames to 1302 after 1309. You may do so. If 1301 supports UHR Link Reconfiguration Mode 2, Frames may be sent to 1302 from 1309 until 1311. Frames may be received from 1301 after 1309. If 1302 receives a frame from 1301 after 1309, it may deliver that frame to 1304 before 1310. If 1302 receives a frame from 1301 after 1309, it may forward that frame to 1303 after 1310. If 1302 receives a frame from 1301 after 1309 1303 does not have to forward the frame after 1311. 1302 does not have to forward the frame to 1303 before 1310 if it receives the frame from 1301 after 1309. 1302 does not have to forward the frame to 1303 if it receives the frame from 1301 before 1309. 1303 may deliver the frame to 1304 if it receives the frame from 1302. "After 1309" may be referred to as "before 1311". 1301 supports UHR Link Reconfiguration Mode 1, to 1303 And frames may be sent after 1311. If 1301 supports UHR Link Reconfiguration Mode 1, it may send frames to 1303 after 1311. You may start the communication. 1301 supports UHR Link Reconfiguration Mode 2. If so, 1303 may send a frame after 1311. If 1301 supports UHR Link Reconfiguration Mode 2, 1301 may send a frame to 1303. You may start transmitting frames from when it is 1. 1303 is from 1301, from 1311. Frames may be received later. If 1303 receives a frame from 1301 after 1311, it may deliver that frame to 1304. Frames transmitted, received, forwarded, and / or delivered in Figure 13 may be, for example, Data frames. Frames transmitted, received, forwarded, and / or delivered in Figure 13 may be, for example, MSDUs. Frames transmitted, received, forwarded, and / or delivered in Figure 13 may be, for example, A-MSDUs. Frames transmitted, received, forwarded, and / or delivered in Figure 13 may be, for example, MMPDUs. In Figure 13, transmission, reception, forwarding, The frames transmitted and / or delivered may be, for example, PPDUs. The frames transmitted, received, forwarded, and / or delivered in Figure 13 may be, for example, individually addressed QoS Data frames. The frames transmitted, received, forwarded, and / or delivered in Figure 13 may be, for example, individually addressed Management frames. The frames transmitted, received, forwarded, and / or delivered in Figure 13 may be, for example, IQMFs. The frames transmitted, received, forwarded, and / or delivered in Figure 13 may be, for example, other types of frames. "Frames" may be replaced with "MAC service tuples," etc.

[0224] The term "frame" may also be referred to as a "MAC frame." The term "frame" may be rephrased as "MAC frame." The term "frame" includes the MSDU, A-MSDU, and / or MMPDU. But that's fine.

[0225] "Maintaining a sequence number space" means determining the sequence number of a frame. It may also be necessary to maintain it. For example, “maintain the sequence number space” "to" may include "start the modulo 4096 counter from 0", "increment the modulo 4096 counter by 1", etc. "to maintain the sequence number space" may also be called "to maintain the sequence number space". "To maintain" can also be rephrased as "to maintain the sequence number space." "To retain a sequence number space identifier" can also be referred to as "to maintain a sequence number space identifier." "To retain a sequence number space identifier" can also be rephrased as "to maintain a sequence number space identifier."

[0226] A Super MLD may maintain a 1-based 48-bit counter for sequentially assigning packet numbers (PN) to frames transmitted by APs belonging to AP MLDs belonging to the Super MLD. AP MLD1 and AP MLD2 belong to AP MLD1 or AP MLD2. A 48-bit sequence starting from 1 to assign sequential packet numbers to frames transmitted by the AP. AP MLD1 and AP MLD2 belonging to Super MLD may maintain a 1-based 48-bit counter for sequentially assigning packet numbers to frames transmitted by APs belonging to AP MLD1 or AP MLD2. All non-AP STAs belonging to non-AP MLDs receive frames from APs belonging to AP MLDs belonging to Super MLDs. If such a frame is received, the packet number of that frame may be used to detect tampered frames sent from APs belonging to other AP MLDs belonging to the same Super MLD. All non-AP STAs belonging to a particular AP MLD may, upon receiving a frame from an AP belonging to a certain AP MLD, use the packet number of that frame to detect tampered frames transmitted from APs belonging to other AP MLDs. Packet numbers will not be repeated for the same temporal key.

[0227] As described above, in embodiments of the present invention, when a non-AP STA belonging to a non-AP MLD sends a frame to request the addition of a link to a target AP MLD, it continues to send data frames to the AP belonging to the current AP MLD until it receives a response frame to the request for the addition of a link to the target AP MLD. With this invention, a non-AP STA belonging to a non-AP MLD can Even during seamless roaming, data frames can be sent with low latency to APs belonging to the AP MLD.

[0228] The programs that run on the base station device and terminal device according to embodiments of the present invention may be programs that control the CPU (Central Processing Unit) and the like (programs that make the computer function) in order to realize the functions of the above embodiments according to embodiments of the present invention. The information handled by these devices is temporarily stored in RAM (Random Access) during processing. It is stored in Memory, and then stored in various ROMs such as Flash ROM (Read Only Memory) or HDD (Hard Disk Drive), and read, modified, and written by the CPU as needed. It can be done.

[0229] Furthermore, the terminal device and some of the base station devices in the above-described embodiment may be implemented using a computer. In that case, the program for implementing this control function may be recorded on a computer-readable recording medium, and the program recorded on this recording medium may be loaded into a computer system and executed.

[0230] Furthermore, the term "computer system" as used herein refers to a computer system built into a terminal device or base station device, and includes hardware such as the operating system and peripheral devices. Also, "computer-readable recording media" refers to portable media such as flexible disks, magneto-optical disks, ROMs, CD-ROMs, and hard disks built into computer systems. It refers to a storage device.

[0231] Furthermore, "computer-readable recording media" may include those that dynamically hold programs for a short period of time, such as communication lines used when transmitting programs via networks such as the Internet or communication lines such as telephone lines, as well as those that hold programs for a certain period of time, such as volatile memory within a computer system that acts as a server or client in such cases. In addition, the above-mentioned program may be for the purpose of realizing some of the functions described above, and may also be a program that can realize the above-mentioned functions in combination with a program already recorded in the computer system.

[0232] The terminal device may consist of at least one processor and at least one memory containing computer program instructions (computer program). The memory and computer program instructions (computer program) may be configured to cause the terminal device to perform the operations and processing described in the above embodiment using the processor. The base station device may consist of at least one processor and at least one memory containing computer program instructions (computer program). The memory and computer program instructions (computer program) may be configured to cause the base station device to perform the operations and processing described in the above embodiment using the processor.

[0233] Furthermore, the base station device in the above-described embodiment can also be implemented as an assembly (device group) composed of multiple devices. Each device constituting the device group may have some or all of the functions or functional blocks of the base station device related to the above-described embodiment. The device group only needs to have a complete set of functions or functional blocks of the base station device. In addition, the terminal device related to the above-described embodiment can also communicate with the base station device as an assembly.

[0234] Furthermore, some or all of the terminal device and base station device in the above-described embodiment may be implemented as an LSI, which is typically an integrated circuit, or as a chipset. Each functional block of the device and base station device may be individually chipped, or some or all of them may be combined. They can be stacked and made into a chip. Furthermore, the method of integrated circuit creation is not limited to LSIs; dedicated circuits or general-purpose circuits are also possible. It could also be implemented using a processor. Furthermore, advances in semiconductor technology could lead to the development of integrated circuits that replace LSIs. If such technology emerges, it will also be possible to use integrated circuits based on that technology.

[0235] Furthermore, although the above-described embodiment mentions a terminal device as an example of a communication device, the present invention is not limited to this and can also be applied to stationary or non-movable electronic devices installed indoors or outdoors, such as terminal devices or communication devices for AV equipment, kitchen equipment, cleaning and washing machines, air conditioning equipment, office equipment, vending machines, and other household appliances.

[0236] While embodiments of this invention have been described in detail above with reference to the drawings, the specific configuration is not limited to these embodiments, and design modifications and the like that do not depart from the gist of this invention are also included. Furthermore, the present invention can be modified in various ways within the scope of the claims, and embodiments obtained by appropriately combining the technical means disclosed in different embodiments are also included in the technical scope of this invention. In addition, configurations in which elements described in each of the above embodiments that produce similar effects are substituted for each other are also included. [Explanation of Symbols]

[0237] 101, 201, 205 BSS 102, 202, 206 AP 103, 104, 203, 204, 207, 208 STAs SU1, AU1 Antenna Section SU2, AU2 RF section SU3, AU3 Physical Layer Processing Unit SU4, AU4 MAC layer processing unit SU5 Upper Layer Packet Processing Unit SU6, AU6 Wireless Transceiver Unit SU7, AU7 Frame Processing Unit AU5 DSAF section 1101, 1104 STA transmission 1102, 1211 IFS 1103, 1212 Backoff counter (contention window) 1201, 1202, 1203, 1204 Timeline 1205 RTS frame 1206, 1208 NAV period 1207 CTS frame 1209 Data frame 1210 AcK frame

Claims

1. A terminal device having a non-AP MLD, The aforementioned non-AP MLD includes at least one non-AP STA, The first AP MLD connected to the aforementioned non-AP MLD has at least one first AP to it. A second AP MLD that is not connected to the aforementioned non-AP MLD has at least a second AP to it. The terminal device includes a transmitting unit that transmits a first frame, a receiving unit that receives a second frame, and a processing unit. If the terminal device supports the second mode, When transmitting the first frame, the transmission of the Data frame to the first AP is not stopped until the second frame is received. Upon receiving the second frame, the transmission of a Data frame to the second AP is initiated. The first frame is a frame for requesting the addition of a link to the second AP MLD, The second frame is a response frame to an additional request for a link to the second AP MLD. Terminal device.

2. The frame transmitted by the terminal device includes a first subfield, If the terminal device supports the second mode, The first subfield is set to the first value. The terminal device according to claim 1.

3. The first frame transmitted by the terminal device includes a second subfield. If the terminal device supports the second mode, The second subfield is set to the second value. The terminal device according to claim 1.

4. A base station device having a first AP MLD, The aforementioned first AP MLD includes at least the first AP, The non-AP MLD connected to the first AP MLD has at least one non-AP STA to it. A second AP MLD that is not connected to the aforementioned non-AP MLD has at least a second AP to it. The base station device includes a receiving unit that receives a first frame, a transmitting unit that transmits a second frame, and a processing unit. If the first non-AP STA supports the second mode, When the first frame is received, the first non-AP STA is not allowed to stop transmitting the Data frame to the first AP until the second frame is transmitted. When transmitting the second frame, the first non-AP STA starts transmitting a Data frame to the second AP. The first frame is a frame for requesting the addition of a link to the second AP MLD, The second frame is a response frame to an additional request for a link to the second AP MLD. Base station equipment.

5. non-AP MLD has at least one non-AP STA to its roster. The first AP MLD connected to the aforementioned non-AP MLD has at least one first AP to it. A second AP MLD that is not connected to the aforementioned non-AP MLD has at least a second AP to it. If the first non-AP STA supports the second mode, When transmitting the first frame, data is sent to the first AP until the second frame is received. Without stopping the transmission of frames, Upon receiving the second frame, the transmission of a Data frame to the second AP is initiated. The first frame is a frame for requesting the addition of a link to the second AP MLD, The second frame is a response frame to an additional request for a link to the second AP MLD. Communication method.

Images