Terminal equipment, base station equipment, and communication method

Abstract

This invention provides terminal equipment, base station equipment, and communication methods that enable efficient communication in a wireless LAN system. [Solution] A base station device having a first AP MLD (1304), wherein the first AP MLD (1304) is connected to a non-AP MLD (1301), and the base station device includes a processing unit that performs a first procedure, and upon success in the first procedure, the first AP MLD (1304) assigns a first AID to the non-AP MLD (1301) which will be the same AID for all non-AP STAs (1302, 1303) to which the non-AP MLD (1301) belongs (1321). The first procedure is a procedure in the roaming preparation procedure to set up a link to a second AP MLD (1307).

Description

Technical Field

[0004] , , ,

[0005] , , ,

[0003] , , ,

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

Background Art

[0006] (2) A second aspect of the present invention is the base station apparatus according to claim 1, wherein the first AID is an AID assigned by the first AP MLD during the roaming preparation procedure.

[0007] (3) A third aspect of the present invention is that the first procedure is performed before the roaming execution procedure in order for the non-AP MLD to transition from the first AP MLD to the second AP MLD. The roaming execution procedure involves the first AP MLD operating with the second AP MLD. A base station device according to claim 1, comprising a procedure for transferring the context necessary to enable the operation.

[0008] (4) A fourth aspect of the present invention is a terminal device having a non-AP MLD, wherein at least a first non-AP STA belongs to the non-AP MLD, and the terminal device includes a processing unit that performs a first procedure, wherein the first non-AP STA belonging to the non-AP MLD of the terminal device has the same AID as the first AID assigned to the non-AP MLD in the first procedure, and the first procedure, in the roaming preparation procedure, sets a link to a second AP MLD. The terminal device is the procedure for setting up the device.

[0009] (5) A fifth aspect of the present invention is that a first AP MLD is connected to a non-AP MLD, and upon success of the first procedure, the first AP MLD assigns to the non-AP MLD a first AID which is the same AID for all non-AP STAs to which the non-AP MLD belongs, and the first procedure is a roaming preparation procedure which sets up a link to a second AP MLD. A sequential method of communication. [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 is a diagram showing an example of the MAC data plane architecture of the MLD according to an aspect of this embodiment. [Figure 11] This is a diagram showing an example of a backoff procedure according to an aspect of this embodiment. [Figure 12] This is a diagram showing an example of the NAV according to an aspect of this embodiment. [Figure 13] This is a diagram showing an example of a transition preparation procedure according to an aspect of this embodiment. [Figure 14] This is a diagram showing an example of a transition preparation procedure according to an aspect of this embodiment.

Mode for Carrying Out the Invention

[0012] [[ID=二十]]Hereinafter, embodiments of the present invention will be described.

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

[0014] The wireless LAN system in this embodiment includes an access point (AP) and a station (STA). The 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 An AP MLD may be included. A single base station device may have one or more APs, one or more AP MLDs, and / or one or more Super AP MLDs. A single terminal device A terminal device may have one or more STAs. A terminal device may have one or more non-AP STAs. A terminal device may have one or more non-AP MLDs. A single terminal device may have one or more non-AP STAs and / or one or more non-AP MLDs.

[0016] Figure 1 shows an example of a wireless LAN system according to one aspect of this embodiment. The wireless LAN system comprises STA103, STA104, and AP102. It may also be called 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] The link may also be a physical path consisting of a single traversal of the wireless medium used to transfer the MSDU between the two STAs.

[0021] 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.

[0022] 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.

[0023] 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).

[0024] 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.

[0025] 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.

[0026] 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).

[0027] 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.

[0028] 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.

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

[0030] 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.

[0031] 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 basic 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.

[0032] 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-GLK (General Link) 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 transmitted via 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.

[0033] 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.

[0034] 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. Updating the mapping may involve updating the mapping between the non-AP MLD to which the DS delivers MAC service tuples and the AP MLD to which that non-AP MLD connects. The DS-STA-NOTIFY primitive is used for mapping updates. 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.

[0035] 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.

[0036] 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).

[0037] 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.

[0038] 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.

[0039] 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 functions on the frame that has undergone processing at the MAC layer. The frame sent from U3 to the RF unit SU2 is converted into an RF signal and transmitted as a wireless signal via the antenna unit SU1.

[0040] 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.

[0041] 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.

[0042] 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.

[0043] 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.

[0044] 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.

[0045] 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. Affiliated STAs may be either APs 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. APs belonging to an AP MLD may be called affiliated APs. A non-AP MLD (non-Access Point Multi-Link Device) is an MLD in which each of the STAs belonging to the MLD is a non-AP STA. It may also refer to the operation between two MLDs.

[0046] 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.

[0047] 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 a name other than MLD. For example, Super MLD may be referred to as Single Mobility Domain (SMD), Seamless Mobility Domain (SMD), Seamless Transition Mobility Domain (STMD), Single Mobility Domain (SMD) MLD, Seamless Mobility Domain (SMD) MLD, Seamless Transition Mobility Domain (STMD) MLD, non-colocated MLD, virtual MLD, transition MLD, or roaming MLD, etc. Family MLDs may be referred to by names other than Family MLD. MLD may include Super MLDs. In other words, MLD may be a Super MLD. Also, MLDs that are not Super MLDs may be referred to as Normal MLDs. 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. It may belong to a Super MLD. A Super MLD may also be an AP MLD. A Super MLD may also be a non-AP MLD. A Super MLD that is an AP MLD may be called a Super AP MLD. Super AP MLD It may be referred to by names other than Super AP MLD. For example, Super AP MLD can be Single Mobility Domain (SMD) AP MLD, Seamless Mobility Domain (SMD) AP MLD, Seamless Transition Mobility Domain (STMD) AP MLD, non-colocated AP MLD, virtual AP MLD, transition It may also be referred to as AP MLD, or roaming AP MLD, etc.

[0048] 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.

[0049] 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 may be referred to by a name other than the Super MLD upper MAC sublayer. The Super MLD lower MAC entity may be referred to by a name other than the Super MLD lower MAC entity. The Super MLD upper MAC sublayer may perform functions common to all MLDs. The Super MLD upper MAC sublayer performs 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.

[0050] 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.

[0051] 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.

[0052] 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.

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

[0054] 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.

[0055] 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.

[0056] A 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 5 GHz and 6 GHz. For example, a UHR STA may be an HE STA at 5 GHz and 6 GHz. For example, a UHR STA may be a VHT STA at 5 GHz and 6 GHz. For example, UHR STA may be HE STA at 2.4GHz. At Hz, it may be an HT STA. The UHR STA may support Super MLD. The UHR STA may support Seamless Transition. The UHR STA may use operation elements for HT, and / or VHT, and / or HE STA, and / or UHR STA. In other words, the UHR STA may be controlled by an HT operation element, and / or a VHT operation element, and / or an HE operation element, and / or an EHT operation element, and / or a UHR operation element.

[0057] 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.

[0058] 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.

[0059] 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.

[0060] 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.

[0061] 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.

[0062] 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 PHY frame in STA may be processed by the physical layer processing unit SU4. 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.

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

[0064] 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.

[0065] 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.

[0066] 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.

[0067] 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.

[0068] 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.

[0069] 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, Block 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.

[0070] The Type subfield and Subtype subfield included in the Frame Control field of the MAC header The subtype of the frame may be determined from the field. 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.

[0071] 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.

[0072] A Beacon frame may contain information such as the Beacon's period and SSID. A Beacon frame may also be a frame that is periodically sent to the STA within the BSS. An Association Request frame may contain information such as the capabilities supported by the STA, the Beacon reception interval, SSID, MLO, etc. It may also be a frame containing information. Association Response frames are supported by STA. The Association Response frame may contain information such as the capabilities supported by the STA, Status code, AID (Association ID), EDCA parameters, Received Channel Power Indicator (RCPI), Received Signal-to-Noise Indicator (RSNI), and MLO. The Association Response frame may be a frame sent in response to a received Association Request frame. The Association Request frame may contain information such as the capabilities supported by the STA, the Beacon reception interval, the MAC address of the AP to which the STA is connected, the SSID, and the MLO. It may also be a frame containing information. Reassociation Response frames are supported by STA. Information such as capabilities, status code, AID, EDCA parameters, RCPI, RSNI, and MLO. A frame containing the following information may also be used. A Reassociation Response frame may be a frame sent in response to a received Reassociation Request frame. A Probe Response frame may be a frame containing information such as the Beacon period and SSID. A Probe Response frame may be a frame sent in response to a received Probe Request frame.

[0073] The AID field may contain AID information. The AID field may contain a value assigned by the AP, PCP, or AP MLD during association. The AID field may contain a value assigned by the current AP MLD during the transition preparation procedure. The AID field may contain a value assigned by the current AP MLD during the setup link(s) with target AP MLD procedure. The AID field may include values ​​assigned from the AP MLD. The AID field may include values ​​assigned from the current AP MLD before the association. The AID field may include values ​​assigned from the target AP MLD during the transition preparation procedure. The AID field may include values ​​assigned from the target AP MLD during the setup link(s) with target AP MLD procedure. It may include values ​​that can be obtained. The AID field is obtained from the target AP MLD before the association. It may include the assigned value. The AID field may represent the 16-bit ID of the STA if it is assigned by the AP or PCP. The AID field may represent the 16-bit ID of the STA if it is assigned by the AP MLD. It may also represent the 16-bit ID of a non-AP MLD. For example, if the AID field represents the 16-bit ID of an STA, values ​​from 1 to 2007 are represented by 14 bits from the least significant bit (LSB) of the AID field. The most significant bit and the next bit of the AID field may both be set to 1, provided that the AID field is located up to the 14th bit, starting from the least significant bit (LSB). For example, if the AID field represents a 16-bit ID for a non-AP MLD, values ​​from 1 to 2006 may be located up to the 14th bit of the AID field, and the most significant bit and the next bit of the AID field may both be set to 1. The fields may be included in the Association Response frame. The AID field may be included in the Reassociation Response frame. The AID field may be included in the Setup Link Response frame. For example, "during association" as described above refers to the period from when the (Re)Association Request frame is sent until the (Re)Association Response frame is sent. This may also be the case. For example, the “during the transition preparation procedure” mentioned above refers to the period from when the Setup Link Request frame is sent until when the Setup Link Response frame is sent. It may also include the following. For example, the above-mentioned “during the transition preparation procedure” may refer to the period before the Transition Request Frame is sent. For example, the above-mentioned “during the setup link(s) with target AP MLD procedure” may refer to the period from when the Setup Link Request frame is sent until the Setup Link Response frame is sent. For example The above-mentioned “during setup link(s) with target AP MLD procedure” may also refer to the period before the Transition Request Frame is sent. For example, “before association” as mentioned above. " may refer to the period before the (Re)Association Request frame is sent. "During the transition preparation procedure," "during the setup link(s) with target AP MLD procedure," and "before association" may be interchangeable.

[0074] 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. If the Type subfield indicates Control frame and the Subtype subfield is set to 1001, the subtype may be Block Ack (BlockAck).

[0075] AP returns acknowledgment to multiple STAs using a Multi-STA BlockAck frame. You may send this. AP MLD returns acknowledgment to multiple STAs or non-AP MLDs. To do this, you may send a Multi-STA BlockAck frame.

[0076] The BlockAck frame may consist of a BA Control field, a BA Information field, etc. The BA Control field may consist of a BA Type subfield, etc. For example If 11 is set in the BA Type subfield, the BlockAck frame is Multi-STA BlockAck frames are also acceptable.

[0077] The BA Information field included in the Multi-STA BlockAck frame may consist of one or more Per AID TID Info subfields. The Per AID TID Info subfield may consist of an AID TID Info subfield, etc. The AID TID Info subfield may consist of an AID11 subfield, an Ack Type subfield, and a TID subfield.

[0078] The AID11 subfield is intended for the non-AP STA of the Per AID TID Info subfield. It is also possible to transmit (carry) the least significant bit (LSB) to the 11th bit of the AID of a non-AP MLD. stomach.

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

[0080] 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. If the STA encounters an element ID that it cannot recognize in the frame body of the received management frame, it ignores that element and continues to parse 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.

[0081] 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.

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

[0083] 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.

[0084] 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.

[0085] 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 consists of fields such as World, Supported Channel Width Set subfield, and Rx LDPC subfield. This is also acceptable. The capabilities supported by VHT STA are listed 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.

[0086] 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.

[0087] 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.

[0088] 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.

[0089] 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.

[0090] 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 a Reassociation Request frame. For example, an EHT Capabilities element may be sent in a Reassociation Response frame. For example, an EHT Capabilities element may be sent in a Probe Request frame. For example, an EHT Capabilities element may be sent in a Probe Response frame.

[0091] 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.

[0092] 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.

[0093] 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 indicates that UHR STA is UHR Link Reconfiguration Mode 1 and UHR Link Rec If both configuration Mode 2 are supported, 3 may be set. 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.

[0094] The UHR Link Reconfiguration Mode 2 Support subfield may also be a subfield indicating support for UHR Link Reconfiguration Mode 2, as described below. 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".

[0095] 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.

[0096] 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.

[0097] 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 a UHR Link Reconfiguration mode in which communication is initiated. 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 may 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 may start sending Data Frames to APs belonging to the target AP MLD. UHR Link Reconfiguration Mode 2 is 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.

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

[0099] 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 BSS is determined by the HT Operation element. It may be controlled. In other words, the HT Operation element may be an operation element that controls the operation of the HT STA within the BSS.

[0100] 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, an HT operation element may be sent in a Probe Response frame.

[0101] 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.

[0102] 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.

[0103] 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.

[0104] 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.

[0105] Channel Center Frequency Segment 1 in the VHT Operation information field The code defines the channel center frequency for a 160MHz or 80+80MHz VHT BSS. 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.

[0106] 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.

[0107] 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.

[0108] 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.

[0109] 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.

[0110] 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 Alternatively, the channel number of the primary channel at 6GHz may be indicated. Channel Center Freque The ncy Segment 0 field is the 20MHz, 40MHz, 80MHz, 160MHz of the BSS operating at 6GHz, 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 Control field format within the 6GHz Operation Information field format may consist of the Channel Width field, Duplicate Beacon subfield, Regulatory Info subfield, Reserved subfield, etc. 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.

[0111] 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.

[0112] 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.

[0113] A-MSDU (Aggregate MSDU) is a sequence of A-MSDU subframes. This is also acceptable. Each A-MSDU subframe has an A-MSDU subframe header. This may consist of an MSDU followed by padding of 0-3. A-MSDU subframe 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).

[0114] 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, 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 also be an 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.

[0115] 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.

[0116] 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.

[0117] 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.

[0118] 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.

[0119] 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.

[0120] 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 may consist of a MAC header field, an A-MSDU field, and an FCS field.

[0121] 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.

[0122] 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

[0123] 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.

[0124] 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 Transition 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

[0125] 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.

[0126] 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.

[0127] 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).

[0128] 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.

[0129] 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.

[0130] 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.

[0131] 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.

[0132] 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.

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

[0134] 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.

[0135] The basic method of accessing MACs used by STA is DFC (Distributed Coordination Function). ) may also be the case. DCF is the same adjustment at each STA in the BSS when the network is running. 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.

[0136] 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.

[0137] 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. .

[0138] 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).

[0139] 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.

[0140] 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.

[0141] 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 will reset until aCWmax is reached. Maintain the value of Wmax. If the transmission of a data frame or management frame is successful, 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 ​​is 7, 15, 31, 63, 127. It may also be a set that includes 255.

[0142] For example, in OFDM PHY characteristics, in the case of 20MHz channel spacing, aSlotTime may be 9μs. In OFDM PHY characteristics, in the case of 20MHz channel spacing, aCWmin may be 15. In OFDM PHY characteristics, in the case of 20MHz channel spacing, aCWmax may be 1023.

[0143] The QoS facility may include an additional coordination function called HCF (Hybrid Coordination Function) that can only be used 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 parameterized QoS access with prioritization to QoS STAs to the wireless medium and continue to support non-QoS STAs for best-effort transfers. HCF may include functions provided by both EDCA (Enhanced Distributed Channel Access) and HCCA (HCF controlled channel access). HCF may use a contention-based channel access method called the EDCA mechanism for contention-based transfers. HCF may use a control channel access method called the HCCA mechanism for contention-free transfers. HCCA (HCF Controlled Channel Access) is for individually addressed downlink transmissions, uplink transmissions, and direct link transmissions, contention by QoS STAs

[0144] This may also be a channel access mechanism used by a Hybrid Coordinator (HC) to coordinate the use of a non-existent medium.

[0145] 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.

[0146] 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.

[0147] A QMF (QoS Management Frame) policy is a policy that defines the AC (Accountability Control) of Management Frames. This may also be the case. The QMF service sends Management frames according to the configured policy. It may also be a service that determines the AC of the trusted EDCA. QMF STA implements the QMF service. It may be an STA. A QMF AP may be an AP that implements the QMF service. A QMF MLD may be an MLD that implements the QMF service. A Non-QMF STA may be an STA that does not implement the QMF service. A Non-QMF AP may be an AP that does not implement the QMF service. A Non-QMF MLD may be an MLD that does not implement the QMF service. IQMF (Individually addressed QoS) The Management Frame may be an individually addressed Management Frame sent using the QMF service.

[0148] An EDCFA (Enhanced Distributed Channel Access Function) is a logical function within a QoS STA that uses an EDCA to determine when a frame in a transmit queue with an associated AC is permitted to be transmitted over the radio medium. There may be one EDCFA per AC. DCFs and HCFs may be defined to operate within the same BSS.

[0149] Each EDCAF may maintain a backoff counter measured in the backoff slot. When the backoff procedure is called, the backoff counter is raised in 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 retry increases, it takes a series of the following values.

[0150] In HCF, the basic unit of assigning transmission rights to a wireless medium may be a TXOP. A TXOP (Transmission Opportunity) is a frame exchange opportunity on a wireless medium provided by a specific QoS STA. It may be a time interval during which one has the right to start a match. TXOP may be defined by the start time and maximum duration. TXOP may be obtained by EDCA. That is, STA is EDCA If you do this, you may earn TXOP.

[0151] Figure 11 shows an example of a backoff procedure according to one aspect of this embodiment. In Figure 11, the horizontal axis may represent time. 1101 may represent the transmission of STA#1. 02 may be an IFS. 1103 may be a backoff counter. 110 3 may be called the contention window. 1104 is the transmission of STA#2. Alternatively, in Figure 11, STA#2 may detect 1101 on the channel. STA#2 is 1 While 101 is detected, the channel may be judged as busy. In other words, 1101 may be the period during which the channel is judged as busy. STA#2 implements carrier sense. You may then determine whether the channel is busy or not. STA#2 will be executed after the period of 1101 has ended. If the channel is determined to be idle, carrier sensing may be performed for a period of 1102. For example, 1102 may be DIFS. 1102 may also be AIFS. STA#2 If the channel is idle during the period of 1102, then 1103 may be started. 1103 decrements the backoff counter while the channel is idle. For example, 6 backoff counters may be generated in 1103. The backoff counter is decremented, and when the backoff counter becomes 0, STA#2 sends It may perform the transmission (1104). Here, the backoff counter may be determined between 0 and CW. CW may be a value selected from a series of values from aCWmin or more to aCWmax or less. The channel may be referred to as a radio medium.

[0152] The carrier sense mechanism may be a mechanism that combines the NAV (Network Allocation Vector) status and the physical carrier sense of the STA transmitter to determine whether the medium is busy or idle. NAV may be maintained by each STA and may be an indicator of the period during which transmission to the radio medium is not started by the STA, regardless of whether the medium is sensed as busy by the CCA (Clear Channel Assessment) function of the STA. The carrier sense mechanism at the STA may be performed by the physical layer processing unit SU3 and / or the MAC layer processing unit SU3. The carrier sense mechanism at the AP may be performed by the physical layer processing unit AU3 and / or the MAC layer processing unit AU3.

[0153] NAV may be a counter that counts down to 0 at a certain speed. When the NAV counter is 0, the STA may indicate that the virtual carrier sense is idle. When the NAV counter is not 0, the STA may indicate that the virtual carrier sense is busy.

[0154] The physical carrier sense function and the virtual carrier sense function may be used to determine the state of the medium. If either the physical carrier sense function or the virtual carrier sense function indicates busy, the medium may be regarded as busy. If both the physical carrier sense function and the virtual carrier sense function indicate idle, the medium may be regarded as idle. The virtual carrier sense may be referred to as NAV. NAV may be provided by all MACs. The NAV counter may be referred to as the NAV timer. ​

[0155] 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.

[0156] 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.

[0157] 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.

[0158] 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.

[0159] Carrier sense (CS) may be performed through both physical and virtual mechanisms. Carrier sense may also be referred to as a carrier sense function. Carrier sense may also be referred to as a carrier sense mechanism. A 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.

[0160] The RTS (Request To Send) frame format includes the Frame Control field and the Duration field. The RTS frame format may include the RA field, TA field, and FCS field. The Duration field of the RTS frame format may indicate the time (in microseconds) required to transmit the pending data or management frame, one CTS frame, one Ack frame, and three SIFS frames. The RA field of the RTS frame indicates the intended direct transmission of the pending individual addressable frame. The TA field may be the address of the receiving STA. The TA field may be the address of the STA sending the RTS frame or the bandwidth signal TA of the STA sending the RTS frame.

[0161] The CTS (Clear To Send) frame format uses the Frame Control field and the Duration field. The RA field and FCS field may be included. The Duration field of the CTS frame format sent in response to an RTS frame may be the Duration field of the previous RTS frame minus the time required to send the CTS frame and the SIFS for it. In other words, it may be the time required to send the pending data or management frame, one Ack frame, and two SIFS. The CTS frame is the first frame of the exchange, and the pending data Alternatively, if the management frame requires an acknowledgment, the Duration field indicates the time required to send the pending data or management frame, two SIFSs, and one Ack frame. (May be in microseconds). The CTS frame is the first frame of the exchange and is held. If the data or management frame inside does not require immediate acknowledgment, the Duration field is the time required for the pending data or management frame and one SIFS transmission. It is also possible. If the CTS frame is a response to the RTS frame, the RA fee 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.

[0162] 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.

[0163] 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, a frame exchange may occur 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, a frame exchange may be , 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.

[0164] 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 may exist. A 4-way handshake may be defined as a pairwise key management protocol in which two parties verify that they mutually possess a Pairwise Master Key (PMK) and distribute a Group Temporal Key (GTK). The 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). The GTK may be a temporary key used to protect information exchanged in a group-addressed Data Frame.

[0165] 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".

[0166] 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.

[0167] 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.

[0168] 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 then 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. Then, non-AP MLD may communicate by making full use of DS. Non-AP STA and AP association The ion may always be initiated by a non-AP STA, not an AP. Between Non-AP MLD and AP MLD The association may always be initiated by a non-AP MLD, not necessarily by an AP MLD.

[0169] 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.

[0170] A non-AP STA may learn which APs exist and what operational capabilities are available from each of those APs, and then initiate an association service to establish an association. 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 initiate an association service to establish an association with the AP MLDs.

[0171] 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.

[0172] 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.

[0173] 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.

[0174] 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.

[0175] 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.

[0176] This state variable may also represent the relationship between local STA and remote STA. iable may 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).

[0177] 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.

[0178] 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 initial value any items (states, agreements, and allocations described above) that the non-AP STA has requested to be deleted or reset to their initial 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. .

[0179] 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.

[0180] 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.

[0181] 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.

[0182] 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.

[0183] The ML (re)setup procedure may be a procedure for setting up a link between a non-AP MLD and an AP MLD. The ML (re)setup procedure may be a procedure completed through the exchange of Association Request frames and Association Response frames. The ML (re)setup procedure may be a procedure completed through the exchange of Reassociation Request frames and Reassociation Response frames. In the ML (re)setup procedure, the non-AP MLD and AP MLD may follow the association or reassociation procedure. ML (re)setup p Route can also be rephrased as ML (re)setup, etc.

[0184] The setup link is between an AP MLD and an associated non-AP MLD (associated non-AP MLD). Therefore, a link that is requested by a non-AP MLD in a (Re)Association Request frame and accepted by an AP MLD in a (Re)Association Response frame, and is related to the AP It is acceptable for links to be deleted or removed in a way that prevents them from being deleted later.

[0185] non-AP MLDs are used to (re)set up one or more links with AP MLDs. A non-AP MLD may initiate an ML (re)setup with an AP MLD. When a non-AP MLD initiates an ML (re)setup with an AP MLD, the non-AP MLD may send a (Re)Association Request frame via a non-AP STA that belongs to the non-AP MLD and is operating on a link that the non-AP MLD expects to be part of the ML (re)setup. The “link that is expected to be part of the ML (re)setup” is the link that the ML (re)setup will initiate. It could be a single link that is expected to be (re)set up.

[0186] The exchange of (Re)Association Request / Response frames is done via the (Re)Association Request frame. The (Re)Association Request frame may be for ML (re)setup only if both the (Re)Association Request frame and the (Re)Association Response frame contain a Basic Multi-Link element. If the (Re)Association Request frame contains a Basic Multi-Link element, the (Re)Association Response frame sent in response to the (Re)Association Request frame will also contain a Basic Multi-Link element.

[0187] In the (Re)Association Request frame, the non-AP MLD requests (re)setup. One or more requested links (requested link(s)) and one or more This may indicate the capabilities and operational parameters of non-AP STAs belonging to a non-AP MLD corresponding to multiple requested links. A non-AP MLD may request the (re)setup of one or more links with one or more subsets of APs belonging to an AP MLD.

[0188] In the (Re)Association Response frame, the AP MLD may indicate one or more request links whose (re)setup was accepted and / or rejected, and the capabilities and operational parameters of one or more request links. The AP MLD does one of the following: • Accept all links that request (re)setup. • Accept a subset of links that have been requested to be (re)set up, and that subset of links includes links that have received a (Re)Association Request frame. • Reject all links that request (re)setup.

[0189] The (Re)Association Response frame may be sent via AP MLD through the affiliated AP that received the (Re)Association Request frame.

[0190] MLDs that request or accept ML (re)setup are requested or accepted by ML (re)setup For two links that are part of multiple links, each link has a different, non-overlapping operation. It ensures that it is located in a different non-overlapping operating channel.

[0191] The link that received the (Re)Association Request frame was not accepted by AP MLD. In this case, AP MLD may treat the ML (re)setup as a failure and may not accept any requested links. If a link that received a (Re)Association Request frame is accepted by AP MLD In addition, ML (re)setup may be successful.

[0192] The AP MLD may assign a single AID to the non-AP MLD once the ML setup is successful.

[0193] If the ML setup is successful, for each setup link accepted as an ML setup, the single AID assigned by the AP MLD to the non-AP MLD will be used for the APs belonging to the AP MLD corresponding to that setup link. Alternatively, the AID must not be one already used by another AP in the same multiple BSSID set as the AP MLD corresponding to that setup link to identify another non-MLD non-AP STA or non-AP MLD.

[0194] All non-AP STAs belonging to a non-AP MLD may have the same AID as the AID assigned to the non-AP MLD within the ML setup.

[0195] After a successful ML (re)setup between a non-AP MLD and an AP MLD, the non-AP MLD may be associated with the AP MLD according to the association or reassociation procedure between MLDs. After the ML (re)setup between the non-AP MLD and the AP MLD is successful, the non-AP MLD and the AP MLD will be one for the MLO. It may have multiple setup links.

[0196] ML reconfiguration requires (re)association between two peer MLDs. Alternatively, the procedure could involve dynamically adding / removing links from the non-AP MLD setup link without requiring a request. ML reconfiguration can also be referred to as link reconfiguration, etc.

[0197] A setup link is a link added after association via multilink reconfiguration (ML reconfiguration), and is not related to the deletion or linking of affiliated APs. Even if the deletion of the link does not result in its subsequent deletion, it is acceptable.

[0198] A non-AP MLD that is in an associated state, i.e., one that holds a state variable that takes a State 3 or State 4 value, will send a Link Reconfiguration Request frame from its non-AP STA to the corresponding AP belonging to the AP MLD it is connected to (associated AP MLD). By sending it, you may request a link reconfiguration for that setup link. The Link Reconfiguration Request frame may be a frame used by non-AP MLD to request the addition and / or removal of links from the links set up during ML setup.

[0199] The Link Reconfiguration Response frame is a response from the AP MLD to the Link Reconfiguration Request frame received from the non-AP MLD, and is used to set up the ML setup of the non-AP MLD. This may also be a frame sent to accept or reject a request to add and / or remove links from a link that was set up at that time.

[0200] Seamless Transition may be a process in which a terminal device transitions from one base station device to another. The terminal device supports multiple different frequency bands. The terminal device may communicate with another base station device using a different frequency band than the one used to communicate with a certain base station device. The terminal device may switch to another base station device using a different frequency band while still communicating with a certain base station device using a certain frequency band. The terminal device may be an STA. The terminal device may have a non-AP MLD built in. This is also acceptable. The terminal device may be a set of multiple STAs. The terminal device may have multiple non-AP MLDs built in. The base station device may be an AP. The base station device may have an AP MLD built in. The base station device may be a set of multiple APs. The base station device may have multiple AP MLDs built in. The base station device may have a program with Super MLD functionality built in. It is also possible that both of the above two base station devices have built-in programs that implement the Super MLD functionality by communicating between programs. Another communication device may incorporate a program that has Super MLD functionality. A communication device incorporating a program that has Super MLD functionality may include multiple base stations, including the two base station devices mentioned above. The device may be maintained. For example, by incorporating a program that has the functionality of Super MLD. Furthermore, the communication device connected to the two base station devices may be maintained by sending signaling from a program with Super MLD functionality to the two base station devices so that the AIDs assigned to the terminal devices by the two base station devices are different. For example, a communication device that has a built-in program with Super MLD functionality and is connected to the two base station devices The signaling equipment may be maintained by sending signaling from a program with Super MLD functionality to the two base station devices so that the AIDs assigned to the terminal devices by the two base station devices are different. If a program is built in, the two base station devices described above may implement the Super MLD function by communicating between programs. For example, the two base station devices described above may be terminal devices Signaling between programs built into base station equipment so that different AIDs are assigned to each device. Maintenance may be performed by transmission. For example, the two base station devices may signal between the programs built into the base station devices so that the AID assigned to the terminal device is different. Maintenance may be performed by sending a message. Seamless Transition is a non-AP MLD. This was a set of procedures for migrating from one AP MLD to another. It is also acceptable. Seamless Transition does not compromise connectivity between non-AP MLD and DS. It may be a series of steps to minimize lost time. Therefore, non-AP MLDs may maintain State 4 during the transition. In other words, in a Seamless Transition, a non-AP MLD retains a state variable that takes the value of State 4 during the transition. (Keep) is also acceptable. In addition, in Seamless Transition, non-AP MLD is seamless. For a seamless experience, the context of data transmission may be preserved. Seamless Transition may be referred to by names other than Seamless Transition. For example, Seamless Transition may be referred to as Seamless BSS Transition, Seamless Roaming, MLD Transition, SMD Transition, 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. "Transition" is equivalent to "roaming". This may be rephrased as "transfer," etc. The transition may include BSS transition. The transition may include reassociation. The transition may include reassociation service. The transition may include Fast BSS transition. The transition may include MLO. A Super MLD may be used in the transition. Two or more AP MLDs belonging to a Super MLD may be used in the transition. "A certain AP MLD" may be referred to as "current AP MLD," "serving AP MLD," etc. "Another AP MLD" may be referred to as "target AP MLD," etc. "A series of steps The term "order" can be rephrased as "mechanism," etc.

[0201] Seamless Transition includes at least a transition procedure. For example, the transition procedure may be a procedure for a non-AP MLD to transition from the current AP MLD to the target AP MLD. Seamless Transition also includes a transition preparation procedure. That is also acceptable. For example, the transition preparation procedure may be a procedure performed as preparation for the transition of a non-AP MLD. If a non-AP MLD uses Seamless Transition to migrate from the current AP MLD to the target AP MLD, the transition preparation procedure may be performed before the transition procedure. The current AP MLD may remain connected to the non-AP MLD while the transition preparation procedure is running. The target AP MLD does not need to be connected to the non-AP MLD while the transition preparation procedure is running. i. While the transition preparation procedure is running, the non-AP MLD may stop sending Data frames to the current AP MLD. An MLD does not have to stop sending Data frames to the current AP MLD. A non-AP MLD may decide whether or not to stop sending Data frames to the current AP MLD during the execution of the transition preparation procedure based on the values ​​of some or all of the subfields contained in the received UHR Capabilities element. For example, a non-AP MLD may decide whether or not to stop sending Data frames to the current AP MLD during the execution of the transition preparation procedure based on the values ​​of some or all of the subfields contained in the received UHR Capabilities element. Based on the values ​​of the UHR Link Reconfiguration Support subfield and / or the UHR Link Reconfiguration Mode 2 Support subfield in the ment, it determines whether to stop sending Data frames to the current AP MLD during the execution of the transition preparation procedure. It is permissible to make such a judgment. A transition procedure may be referred to by a name other than "transition procedure." For example, a transition procedure may be referred to as a transition execution procedure, roaming procedure, roaming execution procedure, etc. A transition preparation procedure may be referred to by a name other than "transition preparation procedure." For example, transition The preparation procedure may also be referred to as the roaming preparation procedure, etc. The transition preparation procedure may include some or all of the following: • Transfer of context related to non-AP MLD from the current AP MLD to the target AP MLD. • Renegotiation of the context with target AP MLD • Setting up one or more links with the target AP MLD (see the setup link(s) with target AP MLD procedure below).

[0202] The aforementioned "context related to non-AP MLD" refers to PTK (Pairwise Transient Key) It may be included. The aforementioned "context related to non-AP MLD" refers to PMK (Pairwise Master). It may include Keys. The aforementioned "context related to non-AP MLD" may include information about SCS (Stream Classification Service). The aforementioned "context related to non-AP MLD" may include information about TWT (Target Wake Time). The aforementioned "context related to non-AP MLD" may include BA (Block Ack) agreements. The “context related to non-AP MLD” mentioned above may include other information related to non-AP MLD.

[0203] The setup link(s) with target AP MLD procedure may also be a procedure for setting up the link between the non-AP MLD and the target AP MLD before the non-AP MLD migrates from the current AP MLD to the target AP MLD. In the formulation procedure, one or more phosphorylation of target AP MLD is performed. This may also be a procedure for setting up the link. The setup link(s) with target AP MLD procedure is performed through the exchange of Setup Link Request frames and Setup Link Response frames. It may be a procedure that is completed. In the setup link(s) with target AP MLD procedure, non-AP MLD and target AP MLD do not follow the association and reassociation procedures. It is also acceptable. In the setup link(s) with target AP MLD procedure, non-AP MLD is target You may set up links for multiple AP MLDs that could be candidates for AP MLD. In the link(s) with target AP MLD procedure, when a non-AP MLD sets up links to multiple AP MLDs that could be candidates for the target AP MLD, the “target AP MLD” is: It may refer to one of several AP MLDs that have links to be set up. The setup link(s) with target AP MLD procedure may be referred to in ways other than setup link(s) with target AP MLD procedure. For example, the setup link(s) with target AP MLD procedure may be referred to as setup link(s) before transition procedure, setup link(s) before transition, setup link(s) before seamless transition, etc.

[0204] The Setup Link Request frame contains some or all of the information included in the Association Request frame. The Setup Link Request frame may include the fields of the Reassociation Request frame. The Setup Link Request frame may include some or all of the fields included in the Reassociation Request frame. This may include some or all of the fields contained in the FT Request frame, which is one of the FT Action frames. The Setup Link Request frame is used in ML reconfiguration procedures. The Setup Link Request frame may include some or all of the fields contained in the Link Reconfiguration Request frame used. The Setup Link Request frame may include some or all of the fields contained in the other frames. It may be referred to as something other than the st frame. The Setup Link Response frame may contain some or all of the fields included in the Association Response frame. The Setup Link Response frame may contain some or all of the fields included in the Reassociation Response frame. For example, the Setup Link Response frame may contain the AID field. The Setup Link Response frame may contain some or all of the fields included in the FT Response frame, which is one of the FT Action frames. The Setup Link Response frame contains some of the fields included in the Link Reconfiguration Response frame used in ML reconfiguration procedures. Alternatively, it may include all fields. The Setup Link Response frame may contain fields other than those mentioned above. It may include some or all of the fields contained in the frame. The Setup Link Response frame may be referred to in a different way than Setup Link Response frame.

[0205] The target setup link may be a link between a non-AP MLD and a target AP MLD, requested by the non-AP MLD in a Setup Link Request frame and accepted by the current AP MLD or the target AP MLD in a Setup Link Response frame. This may be a link that will not be deleted later due to the deletion of related APs or links. The target setup link may be referred to by something other than target setup link. For example, the target setup link may be referred to as setup link, etc.

[0206] An example of a setup link(s) before transition procedure is described below. A non-AP MLD may initiate a setup link(s) before transition procedure with a target AP MLD in order to set up one or more links with the target AP MLD. When a non-AP MLD initiates a setup link(s) before transition procedure with a target AP MLD, the non-AP MLD sends a message to the current AP MLD regarding the non-AP STAs belonging to the non-AP MLD and the connected... A Setup Link Request frame may be sent via the AP. The AP connected to the non-AP STA mentioned above may belong to the current AP MLD.

[0207] In the Setup Link Request frame, non-AP MLD contains one or more links for which setup has been requested (requested link(s)) and one or more requests The capabilities and operational parameters of the non-AP STA belonging to the non-AP MLD corresponding to the linked non-AP MLD may be indicated. The non-AP MLD belongs to the target AP MLD. You may request the setup of one or more links with a subset of one or more APs.

[0208] In the Setup Link Response frame, the current AP MLD indicates one or more request links for which the setup was accepted, and / or one or more links for which the setup was rejected. This may indicate multiple request links, and the capabilities and operational parameters of one or more request links.

[0209] The current AP MLD may perform some or all of the following actions. • Accept all links that request setup. • Accept a subset of the multiple links that have been requested to be set up. • Reject all links that request setup.

[0210] The Setup Link Response frame is transmitted via the affiliated AP that received the Setup Link Request frame. It may be sent using the current AP MLD.

[0211] Request or accept setting up multiple links between non-AP MLD and target AP MLD. The MLD specifies that for two links that are part of multiple links requested or accepted by the setup link(s) before transition procedure, each link has a different, non-overlapping operational channel. It ensures that it is located in a different non-overlapping operating channel.

[0212] The current AP MLD may decide to accept or reject a link requested for setup through negotiation with the target AP MLD. For example, for each link requested for setup by a non-AP MLD, the current AP MLD may determine whether the single AID assigned to the non-AP MLD is already being used to identify another non-MLD non-AP STA or non-AP MLD by an AP belonging to the target AP MLD corresponding to that link, or by another AP in the same multiple BSSID set as the AP belonging to the target AP MLD corresponding to that link. To do this, you may request the corresponding target AP MLD to assign an AID to a non-AP MLD. In this case, the target AP MLD will assign an AID to each link requested by the current AP MLD. If the AID is not already in use, the target AP MLD may accept the assignment of the AID to the non-AP MLD. Alternatively, the target AP MLD may refuse to assign the AID to the non-AP MLD if the corresponding AID is already in use for each link requested by the current AP MLD. If the current AP MLD accepts the assignment of the AID to the non-AP MLD from the target AP MLD, it will assign the corresponding AID to the non-AP MLD. All links may be accepted. If the current AP MLD is refused by the target AP MLD to assign an AID to a non-AP MLD, it may request the target AP MLD to assign an AID to the non-AP MLD again for the corresponding link, but with a different AID value. The current AP MLD assigns AID to a non-AP MLD within a certain period of time to the target AP If not accepted by the MLD, all corresponding links may be rejected. The current AP MLD may treat the setup link(s) before transition procedure for a target AP MLD as a failure if the assignment of AID to a non-AP MLD is not accepted by the target AP MLD within a certain period of time.

[0213] If one or more links requested for setup by the Setup Link Request frame are accepted by the current AP MLD, the setup link(s) before transition procedure is completed. It may be a success.

[0214] The current AP MLD is created when the setup link(s) before transition procedure is successful. A single AID may be assigned to a non-AP MLD.

[0215] If the setup link(s) before transition procedure is successful, the current AP MLD will be applied to each target setup link accepted as the setup link(s) before transition procedure. A single AID assigned to a non-AP MLD is an AP belonging to the target AP MLD corresponding to that target setup link, or an AP belonging to the target AP MLD corresponding to that target setup link. The AID must not be one already used by another AP within the same multiple BSSID set to identify another non-MLD non-AP STA or non-AP MLD.

[0216] All non-AP STAs belonging to a non-AP MLD may have the same AID as the AID assigned to the non-AP MLD within the setup link(s) before transition procedure.

[0217] The setup link(s) before transition procedure between the non-AP MLD and the current AP MLD was successful. After that, the non-AP MLD and target AP MLD may have one or more target setup links for Seamless Transition. In other words, after the setup of the link to the target AP MLD is successful, the non-AP MLD and target AP MLD may have one or more target setup links for Seamless Transition.

[0218] This section describes another example of a setup link(s) before a transition procedure. (non-AP) The MLD may initiate a setup link(s) before transition procedure with the target AP MLD to set up one or more links with the target AP MLD. When the non-AP MLD initiates the setup link(s) before transition procedure with the target AP MLD, the non-AP MLD communicates to the current AP MLD the non-AP STAs and connections belonging to the non-AP MLD. A Setup Link Request frame may be sent via the AP that is connected to the AP. The AP connected to the non-AP STA mentioned above may also belong to the current AP MLD.

[0219] In the Setup Link Request frame, non-AP MLD contains one or more links for which setup has been requested (requested link(s)) and one or more requests The capabilities and operational parameters of the non-AP STA belonging to the non-AP MLD corresponding to the linked non-AP MLD may be indicated. The non-AP MLD belongs to the target AP MLD. You may request the setup of one or more links with a subset of one or more APs.

[0220] In the Setup Link Response frame, the current AP MLD indicates one or more request links for which the setup was accepted, and / or one or more links for which the setup was rejected. This may indicate multiple request links, and the capabilities and operational parameters of one or more request links.

[0221] The current AP MLD may perform some or all of the following actions. • Accept all links that request setup. • Accept a subset of the multiple links that have been requested to be set up. • Reject all links that request setup.

[0222] The Setup Link Response frame is transmitted via the affiliated AP that received the Setup Link Request frame. It may be sent using the current AP MLD.

[0223] Request or accept setting up multiple links between non-AP MLD and target AP MLD. The MLD specifies that for two links that are part of multiple links requested or accepted by the setup link(s) before transition procedure, each link has a different, non-overlapping operational channel. It ensures that it is located in a different non-overlapping operating channel.

[0224] The current AP MLD may decide to accept or reject a link requested for setup through negotiation with the target AP MLD. For example, for each link requested for setup by a non-AP MLD, the current AP MLD may determine whether the single AID assigned to the non-AP MLD is already being used to identify another non-MLD non-AP STA or non-AP MLD by an AP belonging to the target AP MLD corresponding to that link, or by another AP in the same multiple BSSID set as the AP belonging to the target AP MLD corresponding to that link. To do this, you may request the corresponding target AP MLD to assign an AID to a non-AP MLD. In this case, the target AP MLD will assign an AID to each link requested by the current AP MLD. If the AID is not already in use, the target AP MLD may accept the assignment of the AID to the non-AP MLD. Alternatively, the target AP MLD may refuse to assign the AID to the non-AP MLD if the corresponding AID is already in use for each link requested by the current AP MLD. If the current AP MLD accepts the assignment of the AID to the non-AP MLD from the target AP MLD, it will assign the corresponding AID to the non-AP MLD. All links may be accepted. If the current AP MLD is refused by the target AP MLD to assign an AID to a non-AP MLD, it may request the target AP MLD to assign an AID to the non-AP MLD again for the corresponding link, but with a different AID value. The current AP MLD assigns AID to a non-AP MLD within a certain period of time to the target AP If not accepted by the MLD, all corresponding links may be rejected. The current AP MLD may treat the setup link(s) before transition procedure for a target AP MLD as a failure if the assignment of AID to a non-AP MLD is not accepted by the target AP MLD within a certain period of time.

[0225] One or more links requested to be set up by the Setup Link Request frame are curr If accepted by ent AP MLD, the setup link(s) before transition procedure is completed. It may be a success.

[0226] The current AP MLD is created when the setup link(s) before transition procedure is successful. A single AID may be assigned to a non-AP MLD.

[0227] If the setup link(s) before transition procedure is successful, the current AP MLD will be applied to each target setup link accepted as the setup link(s) before transition procedure. A single AID assigned to a non-AP MLD is an AP belonging to the target AP MLD corresponding to that target setup link, or an AP belonging to the target AP MLD corresponding to that target setup link. The AID must not be one already used by another AP within the same multiple BSSID set to identify another non-MLD non-AP STA or non-AP MLD.

[0228] A non-AP STA belonging to a non-AP MLD and having a link whose setup has been accepted by the current AP MLD is assigned to the non-AP MLD within the setup link(s) before transition procedure. It may have the same AID as the one assigned. In other words, a non-AP STA belonging to a non-AP MLD but not having a link whose setup has been accepted by the current AP MLD may have a different AID than the one assigned to the non-AP MLD within the setup link(s) before transition procedure. They may have the same AID as the non-AP MLD, for example, a non-AP STA belonging to a non-AP MLD but not having a link whose setup has been accepted by the current AP MLD may have the same AID as the non-AP MLD assigned within the ML setup.

[0229] The setup link(s) before transition procedure between the non-AP MLD and the current AP MLD was successful. After that, the non-AP MLD and target AP MLD may have one or more target setup links for Seamless Transition. In other words, after the setup of the link to the target AP MLD is successful, the non-AP MLD and target AP MLD may have one or more target setup links for Seamless Transition.

[0230] This section describes another example of a setup link(s) before a transition procedure. (non-AP) The MLD may initiate a setup link(s) before transition procedure with the target AP MLD to set up one or more links with the target AP MLD. When a non-AP MLD initiates the setup link(s) before transition procedure with a target AP MLD, the non-AP MLD may send a Setup Link Request frame to the target AP MLD via a non-AP STA belonging to the non-AP MLD and operating on a link that the non-AP MLD expects to be part of the setup link(s) before transition procedure. The “link expected to be part of the setup link(s) before transition procedure” may be any single link that the non-AP MLD expects to be set up in the setup link(s) before transition procedure. In other words, the non-AP MLD may use one of the links for which it requests setup to initiate the Setup Link Request to the target AP MLD. You may send a Link Request frame.

[0231] In the Setup Link Request frame, non-AP MLD contains one or more links for which setup has been requested (requested link(s)) and one or more requests The capabilities and operational parameters of non-AP STAs belonging to the non-AP MLD corresponding to the linked non-AP MLD may be shown. A non-AP MLD is one or more non-AP STAs belonging to the target AP MLD. You may request the setup of one or more links with a subset of several APs.

[0232] In the Setup Link Response frame, the target AP MLD contains one or more request links whose setup was accepted, and / or rejected, as well as the capabilities and operation of one or more request links. You may also show the nal parameters.

[0233] The target AP MLD may perform one of the following actions. • Accept all links that request setup. • Accept a subset of multiple links that have been requested to be set up, and that subset of links includes the links that have received a Setup Link Request frame. • Reject all links that request setup.

[0234] The Setup Link Response frame is transmitted via the affiliated AP that received the Setup Link Request frame. It may be sent via target AP MLD.

[0235] Request or accept setting up multiple links between non-AP MLD and target AP MLD. The MLD specifies that for two links that are part of multiple links requested or accepted by the setup link(s) before transition procedure, each link has a different, non-overlapping operational channel. It ensures that it is located in a different non-overlapping operating channel.

[0236] The target AP MLD may decide whether to accept or reject a link requested for setup through negotiation with the current AP MLD. For example, the target AP MLD may request the current AP MLD to assign an AID to each link requested for setup by a non-AP MLD. In this case, the current AP MLD will then... For each requested AID, the target AP MLD may accept or reject the assignment to a non-AP MLD. The target AP MLD accepts the assignment of all AIDs to non-AP MLDs from the current AP MLD. The target AP MLD may accept the link. For links where the current AP MLD has refused to assign an AID to the non-AP MLD, the target AP MLD may again request the current AP MLD to assign an AID to the non-AP MLD with a different value. If the assignment of AID to a non-AP MLD is not accepted by the current AP MLD within a certain period of time... If so, you may reject all links that request setup. target AP MLD If the assignment of AID to a non-AP MLD is not accepted by the current AP MLD within a certain period of time... If so, the `setup link(s) before transition` procedure may be treated as a failure.

[0237] The link that received the Setup Link Request frame was not accepted by the target AP MLD. In this case, the target AP MLD will treat the setup link(s) before transition procedure as a failure and may not accept any of the requested links.

[0238] If the link that received the Setup Link Request frame is accepted by the target AP MLD The `setup link(s) before transition` procedure may be successful.

[0239] The target AP MLD may assign a single AID to the non-AP MLD once the setup link(s) before transition procedure is successful.

[0240] If the setup link(s) before transition procedure is successful, for each target setup link accepted as part of the setup link(s) before transition procedure, the single AID assigned by the target AP MLD to the non-AP MLD corresponds to the target AP MLD for that target setup link. The AID must not be one already used by an AP belonging to the target AP MLD, or by another AP in the same multiple BSSID set as an AP belonging to the target AP MLD corresponding to its target setup link, to identify another non-MLD non-AP STA or non-AP MLD.

[0241] All non-AP STAs belonging to a non-AP MLD may have the same AID as the AID assigned to the non-AP MLD within the setup link(s) before transition procedure.

[0242] After the setup link(s) before transition procedure between the non-AP MLD and the target AP MLD is successful, the non-AP MLD and the target AP MLD may have one or more target setup links for Seamless Transition. In other words, after the setup of the link to the target AP MLD is successful, the non-AP MLD and the target AP MLD may have one or more target setup links for Seamless Transition.

[0243] This section describes another example of a setup link(s) before a transition procedure. (non-AP) The MLD may initiate a setup link(s) before transition procedure with the target AP MLD to set up one or more links with the target AP MLD. When a non-AP MLD initiates the setup link(s) before transition procedure with a target AP MLD, the non-AP MLD may send a Setup Link Request frame to the target AP MLD via a non-AP STA belonging to the non-AP MLD and operating on a link that the non-AP MLD expects to be part of the setup link(s) before transition procedure. The “link expected to be part of the setup link(s) before transition procedure” may be any single link that the non-AP MLD expects to be set up in the setup link(s) before transition procedure. In other words, the non-AP MLD may use one of the links for which it requests setup to initiate the Setup Link Request to the target AP MLD. You may send a Link Request frame.

[0244] In the Setup Link Request frame, non-AP MLD contains one or more links for which setup has been requested (requested link(s)) and one or more requests The capabilities and operational parameters of non-AP STAs belonging to the non-AP MLD corresponding to the linked non-AP MLD may be shown. A non-AP MLD is one or more non-AP STAs belonging to the target AP MLD. You may request the setup of one or more links with a subset of several APs.

[0245] In the Setup Link Response frame, the target AP MLD may indicate one or more request links whose setup was accepted and / or rejected, as well as the capabilities and operational parameters of one or more request links.

[0246] The target AP MLD may perform one of the following actions. • Accept all links that request setup. • Accept a subset of multiple links that have been requested to be set up, and that subset of links includes the links that have received a Setup Link Request frame. • Reject all links that request setup.

[0247] The Setup Link Response frame is transmitted via the affiliated AP that received the Setup Link Request frame. It may be sent via target AP MLD.

[0248] Request or accept setting up multiple links between non-AP MLD and target AP MLD. The MLD specifies that for two links that are part of multiple links requested or accepted by the setup link(s) before transition procedure, each link has a different, non-overlapping operational channel. It ensures that it is located in a different non-overlapping operating channel.

[0249] The target AP MLD may decide whether to accept or reject a link requested for setup through negotiation with the current AP MLD. For example, the target AP MLD may request the current AP MLD to assign an AID to each link requested for setup by a non-AP MLD. In this case, the current AP MLD will then... For each requested AID, the target AP MLD may accept or reject the assignment to a non-AP MLD. The target AP MLD accepts the assignment of all AIDs to non-AP MLDs from the current AP MLD. The target AP MLD may accept the link. For links where the current AP MLD has refused to assign an AID to the non-AP MLD, the target AP MLD may again request the current AP MLD to assign an AID to the non-AP MLD with a different value. If the assignment of AID to a non-AP MLD is not accepted by the current AP MLD within a certain period of time... If so, you may reject all links that request setup. target AP MLD If the assignment of AID to a non-AP MLD is not accepted by the current AP MLD within a certain period of time... If so, the `setup link(s) before transition` procedure may be treated as a failure.

[0250] The link that received the Setup Link Request frame was not accepted by the target AP MLD. In this case, the target AP MLD will treat the setup link(s) before transition procedure as a failure and may not accept any of the requested links.

[0251] If the link that received the Setup Link Request frame is accepted by the target AP MLD The `setup link(s) before transition` procedure may be successful.

[0252] The target AP MLD may assign a single AID to the non-AP MLD once the setup link(s) before transition procedure is successful.

[0253] If the setup link(s) before transition procedure is successful, for each target setup link accepted as part of the setup link(s) before transition procedure, the single AID assigned by the target AP MLD to the non-AP MLD corresponds to the target AP MLD for that target setup link. The AID must not be one already used by an AP belonging to the target AP MLD, or by another AP in the same multiple BSSID set as an AP belonging to the target AP MLD corresponding to its target setup link, to identify another non-MLD non-AP STA or non-AP MLD.

[0254] Links belonging to a non-AP MLD and whose setup has been accepted by the target AP MLD. Non-AP STAs with this feature are assigned to non-AP MLDs within the setup link(s) before transition procedure. It may have the same AID as the one assigned to it. In other words, a non-AP STA belonging to a non-AP MLD but not having a link whose setup has been accepted by the target AP MLD may have a different AID than the one assigned to the non-AP MLD within the setup link(s) before transition procedure. For example, a non-AP STA belonging to a non-AP MLD but not having a link whose setup has been accepted by the target AP MLD A non-AP STA that does not have an accepted link may have the same AID as the non-AP MLD assigned within the ML setup.

[0255] After the setup link(s) before transition procedure between the non-AP MLD and the target AP MLD is successful, the non-AP MLD and the target AP MLD may have one or more target setup links for Seamless Transition. In other words, after the setup of the link to the target AP MLD is successful, the non-AP MLD and the target AP MLD may have one or more target setup links for Seamless Transition.

[0256] In the transition procedure, the non-AP MLD moves from the current AP MLD to the target AP MLD. When using Seamless Transition to perform an action, the non-AP MLD will be compared to the current AP MLD. The current AP MLD may send a Transition Request Frame. Within a certain period, the current AP MLD may send data frames from one or more individually addressed downlinks to non-AP. It may be sent to the MLD. The aforementioned period may begin from the time the Transition Request Frame is received. If a non-AP MLD chooses to receive one or more individually addressed buffered downlink Data Frames from the current AP MLD, it may receive them during the aforementioned period. The Transition Request Frame may also be called a UHR Link Reconfiguration Request Frame, etc. The UHR Link Reconfiguration Request Frame is a request from the non-AP MLD to the current AP MLD to link to the target AP MLD. It may be used to request the addition of a . Transition Request Frame may contain some or all of the fields included in the Reassociation Request Frame. Transition Request Frame may contain some or all of the fields included in the FT Request Frame, which is one of the FT Action frames. It may include all fields. Transition Request Frame is ML reconfiguration A portion of the Link Reconfiguration Request frame used in the procedure or It may include all fields. The Transition Request Frame may be a frame with a different name. In the transition procedure, the current AP MLD may send a Transition Response Frame to the non-AP MLD after receiving the Transition Request Frame and after the context transfer or renegotiation is complete. The non-AP MLD does not have to send one or more Class 3 frames to the target AP MLD until it receives a Transition Response Frame from the current AP MLD. For example, the non-AP MLD does not have to send one or more uplink Data frames to the target AP MLD until it receives a Transition Response Frame from the current AP MLD. For example, the non-AP MLD does not have to send one or more Action frames to the target AP MLD until it receives a Transition Response Frame from the current AP MLD. The Transition Response Frame may 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 may accept or reject the request to add a link to the target AP MLD. The Transition Response Frame is included in the Reassociation Response Frame. It may include some or all of the fields. The Transition Response Frame may include some or all of the fields included in the FT Response Frame, which is one of the FT Action frames. The Transition Response Frame may include some or all of the fields included in the Link Reconfiguration Response Frame used in ML reconfiguration procedures. But that's fine. The Transition Response Frame may have a different name. "non-AP MLD" and "current AP MLD" are "non-AP STAs belonging to non-AP MLD," respectively. This can also be rephrased as "APs belonging to the current AP MLD." Furthermore, "current AP MLD" can be rephrased as "target AP MLD."

[0257] Non-AP STAs belonging to non-AP MLD may send frames containing information elements that include information related to Seamless Transition. Non-AP STAs belonging to non-AP MLD may send frames containing information elements that include information related to Seamless Transition when performing Seamless Transition. Non-AP STAs belonging to non-AP MLD may send frames containing information elements that include information related to Seamless Transition. When sending a Link Reconfiguration Request Frame, a frame containing an information element with information related to Seamless Transition may be sent to indicate whether or not to stop sending Data Frames to APs belonging to the current AP MLD until a UHR Link Reconfiguration Response Frame is received. Non-AP STAs belonging to non-AP MLDs do not need to include an information element with information related to Seamless Transition in the frames they send if they do not perform a Seamless Transition. For example, an information element with information related to Seamless Transition may be called a UHR Link Reconfiguration element. For example, an information element containing information related to Seamless Transition is UHR Link. It may also be called a Reconfiguration operation element. For example, Seamless Transition An information element containing information related to Seamless Transition may be called a UHR operation element. For example, an information element containing information related to Seamless Transition may be called a UHR Multi-Link element. An information element containing information related to Seamless Transition may be referred to in ways other than those mentioned above. For example, an information element containing information related to Seamless Transition may be called a UHR Multi-Link element. A frame containing an information element that includes information related to Seamless Transition may be a frame for initiating the Seamless Transition procedure. For example, information related to Seamless Transition Frames containing the information element are UHR Link Reconfiguration Request Frames. This may also be the case. For example, a frame containing an information element that includes information related to Seamless Transition may be an Association Request frame. A frame containing an information element with information related to an arrangement may be a Reassociation Request frame. For example, a frame containing an information element with information related to a Seamless Transition may be an FT Request frame. For example, Seamless A frame containing an information element with information related to Transition may be a Link Reconfiguration Request frame. A frame containing an information element with information related to Seamless Transition may be any other Management frame.

[0258] A non-AP STA belonging to a non-AP MLD may decide whether to include an information element containing information related to Seamless Transition in the frame it transmits, based on whether or not it supports UHR Link Reconfiguration. A non-AP STA belonging to a non-AP MLD may decide whether or not the current AP MLD and / or the target AP MLD support UHR Link Reconfiguration. Based on whether or not it is enabled, information related to Seamless Transition is included in the frame being sent. 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 Transition in the frame it transmits, based on whether or not it supports UHR Link Reconfiguration Mode 2. 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 transmits to an AP belonging to the current AP MLD. For example, if a non-AP STA belonging to a non-AP MLD supports UHR Link If Reconfiguration Mode 2 is not supported, 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. For example, a non-AP STA belonging to a non-AP MLD may, if it supports UHR Link Reconfiguration Mode 2, include a UHR Link Reconfiguration element containing a UHR Link Reconfiguration Mode subfield set to 1 in the frame sent to the AP belonging to the current AP MLD. If a non-AP STA does not support UHR Link Reconfiguration Mode 2, set it to 0. A UHR Link Reconfiguration element containing the set UHR Link Reconfiguration Mode subfield may be included in the frame sent to the AP belonging to the current AP MLD.

[0259] 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. The UHR Link Reconfiguration element, including the field, is used by APs belonging to the current AP MLD. It may be included in the frame sent. For example, a field indicating the mode of UHR Link Reconfiguration included in the UHR Link Reconfiguration element may be called the UHR Link Reconfiguration Mode subfield. The UHR Link Reconfiguration Mode subfield is used 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 may be a subfield indicating whether or not to stop sending Data frames to the AP. For example, if a non-AP STA belonging to a non-AP MLD sends a UHR Link Reconfiguration Request Frame and stops sending Data frames to the AP 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 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 the AP 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 (e.g., 1) different from the first value. For example, if a non-AP STA belonging to a non-AP MLD sends a UHR Link Reconfiguration Request Frame, it may set to a second value (e.g., 1) different from the first value. 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.

[0260] 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].

[0261] For example, a UHR Multi-Link element may indicate information for controlling the MLD to which the UHR STA belongs. For example, a UHR Multi-Link element may indicate 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. A UHR Multi-Link element is used 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 from the current AP MLD. 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 have 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.

[0262] Information related to Seamless Transition is at least from the UHR Link Reconfiguration section. Information indicating the mode of UHR Link Reconfiguration may also be provided by the AP belonging to the current AP MLD when a non-AP STA belonging to a non-AP MLD sends a UHR Link Reconfiguration Request Frame and receives a UHR Link Reconfiguration Response Frame. This could also be information indicating whether or not to stop sending Data Frames to the system. Information related to Seamless Transition should include at least the UHR Link Reconfiguration Mode subfield. This is also acceptable. A non-AP STA belonging to a non-AP MLD may send a frame containing information related to Seamless Transition if it supports at least one of UHR Link Reconfiguration Mode 1 or UHR Link Reconfiguration Mode 2. An AP belonging to a current AP MLD may send a frame containing information related to Seamless Transition in a frame received from a non-AP STA belonging to a non-AP MLD. If the received information contains relevant data, the AP may decide whether or not to forward the data frame to the AP belonging to the target AP MLD based on the received information. For example, 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 Transition indicating UHR Link Reconfiguration Mode 1, the AP may decide not to forward the data frame to the AP belonging to the target AP MLD. For example, 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 Transition indicating UHR Link Reconfiguration Mode 2, the AP may decide not to forward the data frame to the AP belonging to the target AP MLD. It may be decided to transfer the Data Frame to the AP belonging to the target AP MLD.

[0263] In the transition procedure, the current AP MLD receives a Transition Request Frame. After that, the following is intended for non-AP MLDs that have initiated Seamless Transition: The pending, individually addressed data frames of one or more downlinks may be forwarded to the target AP MLD. For example, if an AP belonging to the current AP MLD decides to forward a data frame to an AP belonging to the target AP MLD, it may forward data frames belonging to non-AP MLDs. Data frames received from non-AP STAs may be forwarded to APs belonging to the target AP MLD. For example, APs belonging to the current AP MLD will be transferred to the non-AP MLD after the DS mapping update. If a Data frame is received from a non-AP STA, 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 may deliver the Data frame forwarded from the AP belonging to the current AP MLD to the DS as MAC service tuples. If the AP belonging to the current AP MLD receives a Data frame from a non-AP STA belonging to a non-AP MLD after the DS mapping update, it may forward that Data frame after sending a UHR Link Reconfiguration Response Frame. It is not necessary to forward the data 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 the DS mapping update, it is not necessary to forward that Data frame to the AP 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 the DS mapping update, it is not necessary to forward that Data frame to the AP belonging to the target AP MLD. When a frame is received, that Data Frame may be distributed to the DS as a MAC service tuples.

[0264] In a transition procedure, the current AP MLD, after receiving a Transition Request Frame, needs the necessary context to enable operations with the target AP MLD. This transfers the information. For example, in a transition procedure, when an AP belonging to the current AP MLD receives a Transition Request Frame from an STA belonging to a non-AP MLD, the current AP MLD may begin transferring the context necessary to enable operation with the target AP MLD to the target AP MLD. The "context necessary to enable operation with the target AP MLD" may include the SN (Sequence Number). The "context necessary to enable operation with the target AP MLD" may also include the PN (Packet Number). The "context necessary to enable operation with target AP MLD" may include a PTK (Pairwise Transient Key). The "text" may include PMK (Pairwise Master Key). "Operation with target AP MLD" The "context necessary to enable the operation" may include information about SCS (Stream Classification Service). The "context necessary to enable operation with target AP MLD" may include information about SCS (Stream Classification Service). The "text" may include information about the Target Wake Time (TWT). The "context necessary to enable operation with the target AP MLD" may include Block Ack (BA) agreements. The "context necessary to enable operation with the target AP MLD" may include other information about non-AP MLDs. Some of the context necessary to enable operation with the target AP MLD may be transferred in the transition preparation procedure.

[0265] In the transition procedure, the non-AP MLD moves from the current AP MLD to the target AP MLD. During the process, the current AP MLD may forward one or more frames to the target AP MLD. Frames forwarded to the current AP MLD and / or target AP MLD belong to APs or The frame forwarded from the current AP MLD to the target AP MLD may include a Data frame sent to an STA belonging to a non-AP MLD. In the transition procedure, the frame forwarded from the current AP MLD to the target AP MLD may include an individually addressed QoS Data frame. In the transition procedure, the frame forwarded from the current AP MLD to the target AP MLD may include an individually addressed Management frame. In the transition procedure, the frame forwarded from the current AP MLD to the target AP Frames forwarded to the MLD may include IQMF. In the transition procedure, frames forwarded from the current AP MLD to the target AP MLD may include other types of frames. It may be included.

[0266] 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.

[0267] 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.

[0268] 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.

[0269] 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.

[0270] 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.

[0271] 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 sequence number of a frame 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 And it may also be rephrased as "AP MLD4", "AP MLD3", etc. "An AP MLD3 belonging to Super MLD, or an AP MLD4 belonging to Super MLD, or a 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 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.

[0272] 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, “If either AP MLD3 or AP MLD4 or non-AP MLD5 is a non-QMF MLD” is equivalent to “If either 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.

[0273] 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.

[0274] 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.

[0275] 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.

[0276] 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. If so, AP MLD1 and AP MLD2 may sequentially assign sequence numbers to frames transmitted by APs belonging to AP MLD1 or AP MLD2. If AP MLD1 and AP MLD2 belonging to Super MLD maintain a sequence number space, AP MLD1 and AP MLD2 will Alternatively, even if you assign sequence numbers to frames transmitted by APs belonging to AP MLD2 in sequence good.

[0277] 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.

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

[0279] 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".

[0280] 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).

[0281] 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.”

[0282] 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."

[0283] 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 STA belonging to MLD2. To determine the number, you may use the sequence number space identifier held by MLD1.

[0284] If AP MLD3 belonging to Super MLD, AP MLD4 belonging to Super MLD, or non-AP MLD5 is a non-QMF MLD, then 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".

[0285] 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. An "individually addressed Management frame" may also be called a "frame." An "individually addressed Management frame" can be rephrased as a "frame." This is also acceptable. 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.”

[0286] 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.

[0287] 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 an MLD", "when Super MLD is a QMF MLD", etc. "when either AP MLD6 belonging to Super MLD, 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 a "frame". "IQMF" may be rephrased as a "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".

[0288] 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".

[0289] 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 the 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), group-addressed frames If a frame is received, the appropriate cache for a matching frame may be searched. If a PV1 Data frame or PV1 Management frame is received, even if the Frame Control field does not have a Retry subfield, if it does, the appropriate cache for a matching frame may be searched. 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.

[0290] 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".

[0291] All STAs belonging to an MLD will identify the duplicate detection caches maintained by the MLD in order to assist the MLD in discarding duplicate, individually addressed QoS Data frames belonging to TIDs without BA negotiation that are sent from STAs belonging to other MLDs. You may use an identifier that does not require a specific identifier.

[0292] 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, 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.

[0293] 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.

[0294] 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.

[0295] 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.

[0296] 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. To assist non-AP MLD3 in discarding duplicate, individually addressed Management frames that are believed, 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.

[0297] 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.

[0298] 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.

[0299] 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.

[0300] An A-MSDU contains only an MSDU 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 have an ack policy of Normal Ack, Implicit BAR, PSMP Ack, or Block Ack. For MSDUs or A-MSDUs belonging to the QoSNoAck service class when the receiver is a QoS STA, the QoS Data frame used to transmit these MSDUs or A-MSDUs may have an ack policy of No Ack.

[0301] Figure 13 shows an example of the steps of the transition preparation procedure according to one aspect of this embodiment. 1301 may be a non-AP MLD. 1302 and 1303 may be non-AP STAs belonging to a non-AP MLD. 1302 and 1303 may use different frequency bands. 1301 may belong to non-AP STAs other than 1302 and 1303. 1304 may be a current AP MLD. 1305 and 1306 may be APs belonging to a current AP MLD. 1305 and 1306 may use different frequency bands. 1304 may belong to APs other than 1305 and 1306. 1307 may be a target AP MLD. 1308 and 1309 may be APs belonging to a target AP MLD. 1308 and 1309 may use different frequency bands. AP 1307 may belong to APs other than 1308 and 1309. APs 1302, 1305, and 1308 may use the same frequency band. APs 1303, 1306, and 1309 may use the same frequency band. In Figure 13, the vertical axis may represent time. AP 1310 may be the timeline of AP 1302's operation. AP 1311 may be the timeline of AP 1303's operation. AP 1312 may be the timeline of AP 1305's operation. AP 1313 may be the timeline of AP 1306's operation. AP 1314 may be the timeline of AP 1308's operation. AP 1315 may be the timeline of AP 1309's operation. AP 1316 may be a frame transmitted from AP 1302 to AP 1305. For example, AP 1316 may be an Association Request frame. For example, 1316 could be a Reassociation Request frame. 1317 could be 1 It may be a frame sent from 305 to 1302. For example, 1317 may be an Association Response frame. For example, 1317 may be a Reassociation Response frame. 1317 may contain an AID field representing AID#1. 1305 may send 1317 based on having received 1316. 1305 may assign AID#1 to 1302 by sending 1317. 1318 is 130 It may also be a frame sent from 2 to 1305. For example, 1318 is Setup Link. It may also be a Request frame. 1301 may send 1318 to 1304 when starting the setup link(s) before transition procedure. 1318 is when 1301 sets One or more links to 1307 requesting a set-up may be provided. For example, if 1301 requests the setup of a link between 1303 and 1309, then 1318 This may indicate information regarding the link between 1303 and 1309. 1319 and 1320 may be negotiations between 1304 and 1307. For example Then, in 1319, 1304 assigns AID#2 to 1301, to 1307. They may request it. For example, 1307 may accept or reject the assignment of AID#2 requested by 1304 in 1320. 1321 may send from 1305 to 1302. It may be a frame. For example, 1321 was a Setup Link Response frame. 1321 may indicate one or more links that 1304 has accepted or rejected. 1321 may include an AID field representing AID#2. 1305 may send 1321 to 1302 based on having received 1318. 1304 may, based on having received 1318 and having accepted the assignment of AID#2 in 1320, You may assign AID#2 to 1301 by sending 1321. 1304 It was reported that 1318 was received, and that the assignment of AID#2 was denied at 1320. Based on this, it is not necessary to assign AID#2 to 1301.

[0302] In Figure 13, as an example of the transition preparation procedure after AID#2 is assigned to 1301, 1302 and 1303 may also have AID#2. That is, after AID#2 is assigned to 1301, 1302 and 1303 may retain AID#2. In this case, 1302 does not need to retain AID#1 after AID#2 is assigned to 1301. Alternatively, 1302 may retain AID#1 after AID#2 is assigned to 1301. It may retain AID#1 after being used.

[0303] In Figure 13, as another example of the transition preparation procedure after AID#2 is assigned to 1301, 1302 has AID#1 and 1303 has AID#2 This is also acceptable. That is, after AID#2 is assigned to 1301, 1303 will retain AID#2, but 1302 does not have to retain AID#2. In this case, 1302 may retain AID#1 after AID#2 is assigned to 1301.

[0304] In Figure 13, if 1301 does not stop sending Data frames to 1304 while the transition preparation procedure is running, 1302 may send a Data frame to 1305 even after sending 1318. Based on the fact that 1305 has received the Data frame from 1301, 1304 may return an acknowledgment for this Data frame by sending a Multi-STA BlockAck frame from 1305 to 1302. In this case, 1304 will use the AID11 subfield contained in the corresponding Per AID TID Info subfield. And it may indicate the AID of 1302. If 1302 holds AID#2 after AID#2 has been assigned to 1301, 1302 expects the acknowledgment for the Data frame it sent to 1305 to be sent with the Per AID TID Info subfield indicating AID#2. AID#2 If 1302 does not retain AID#2 after it has been assigned to 1301, then 1302 will be assigned to 13 The acknowledgment for the Data frame sent to 05 indicates AID#1. It is expected to be transmitted in the field. In Figure 13, if 1301 is transition If the transmission of Data frames to 1304 is stopped during the execution of the preparation procedure, 1305 does not need to send a Multi-STA BlockAck frame to 1302.

[0305] In Figure 13, 1304 and 1307 are AID#2 by 1319 and 1320. Although I know this, 1307 does not know when 1305 sent 1321, that is, when 1304 assigned AID#2 to 1301. In Figure 13, the AP MLD that assigns AID#2 to 1301 and the AP MLD that sends a Multi-STA BlockAck frame to 1301 are the same at 1304. Therefore, if 1301 does not stop sending Data frames to 1304 while the transition preparation procedure is running, in both cases where 1302 retains AID#2 after AID#2 is assigned to 1301, and where 1301 does not retain AID#2, 1301 will perform an ac for the Data frame sent to 1304. The knowledgment can still be received even after AID#2 is assigned.

[0306] Figure 14 shows an example of the steps of the transition preparation procedure according to one aspect of this embodiment. 1401 may be a non-AP MLD. 1402 and 1403 may be non-AP STAs belonging to a non-AP MLD. 1402 and 1403 may use different frequency bands. 1401 may belong to non-AP STAs other than 1402 and 1403. 1404 may be a current AP MLD. 1405 and 1406 may be APs belonging to a current AP MLD. 1405 and 1406 may use different frequency bands. 1404 may belong to APs other than 1405 and 1406. 1407 may be a target AP MLD. 1408 and 1409 may be APs belonging to a target AP MLD. 1408 and 1409 may use different frequency bands. AP 1407 may belong to APs other than 1408 and 1409. APs 1402, 1405, and 1408 may use the same frequency band. APs 1403, 1406, and 1409 may use the same frequency band. In Figure 14, the vertical axis may represent time. AP 1410 may be the timeline of AP 1402's operation. AP 1411 may be the timeline of AP 1403's operation. AP 1412 may be the timeline of AP 1405's operation. AP 1413 may be the timeline of AP 1406's operation. AP 1414 may be the timeline of AP 1408's operation. AP 1415 may be the timeline of AP 1409's operation. AP 1416 may be a frame transmitted from AP 1402 to AP 1405. For example, AP 1416 may be an Association Request frame. For example, 1416 could be a Reassociation Request frame. 1417 could be 1 It may be a frame sent from 405 to 1402. For example, 1417 may be an Association Response frame. For example, 1417 may be a Reassociation Response frame. 1417 may contain an AID field representing AID#1. 1405 may send 1417 based on having received 1416. 1405 may assign AID#1 to 1402 by sending 1417. 1418 is 140 It may also be a frame sent from 3 to 1409. For example, 1418 is Setup Link. It may also be a Request frame. 1401 may send 1418 to 1407 when starting the setup link(s) before transition procedure. 1418 is when 1401 sets One or more links to 1407 requesting a setup may be shown. For example, if 1401 requests the setup of a link between 1403 and 1409, 1418 may show information regarding the link between 1403 and 1409. 1419 and 1420 may be negotiations between 1404 and 1407. Then, in 1419, 1407 assigns AID#2 to 1401, to 1404. They may request it. For example, 1404 may accept or reject the assignment of AID#2 requested by 1407 in 1420. 1421 may send from 1409 to 1403. It may be a frame. For example, 1421 was a Setup Link Response frame. 1421 may indicate one or more links that 1407 has accepted or rejected. 1421 may include an AID field representing AID#2. 1409 may send 1421 to 1403 based on having received 1418. 1407 may, based on having received 1418 and having accepted the assignment of AID#2 in 1420 You may assign AID#2 to 1401 by sending 1421. 1407 It was reported that 1418 was received, and that the assignment of AID#2 was denied at 1420. Based on this, it is not necessary to assign AID#2 to 1401.

[0307] In Figure 14, as an example of the transition preparation procedure after AID#2 is assigned to 1401, 1402 and 1403 may also have AID#2. That is, after AID#2 is assigned to 1401, 1402 and 1403 may retain AID#2. In this case, 1402 does not need to retain AID#1 after AID#2 is assigned to 1401. Alternatively, 1402 may retain AID#2 after AID#2 is assigned to 1401. It may retain AID#1 after being used.

[0308] In Figure 14, as another example of the transition preparation procedure after AID#2 is assigned to 1401, 1402 has AID#1 and 1403 has AID#2 This is also acceptable. That is, after AID#2 is assigned to 1401, 1403 may retain AID#2, but 1402 does not have to retain AID#2. In this case, 1402 may retain AID#1 after AID#2 is assigned to 1401.

[0309] In Figure 14, if 1401 does not stop sending Data frames to 1404 while the transition preparation procedure is running, 1402 may send a Data frame to 1405 even after 1403 has sent 1318. Based on the fact that 1405 has received the Data frame from 1401, 1404 may return an acknowledgment for this Data frame by sending a Multi-STA BlockAck frame from 1405 to 1402. In this case, 1404 will send the AID11 subfield included in the corresponding Per AID TID Info subfield. In the `TID` field, AID 1402 may be indicated. If 1402 retains AID #2 after AID #2 has been assigned to 1401, 1402 expects the acknowledgment for the Data frame sent to 1405 to be sent with the Per AID TID Info subfield indicating AID #2. If 1402 does not retain AID #2 after AID #2 has been assigned to 1401, 1402 expects the acknowledgment for the Data frame sent to 1405 to be sent with the Per AID TID Info subfield indicating AID #1. It is expected to be sent in the Info subfield. In Figure 14, if 1401 stops sending the Data Frame to 1404 while the transition preparation procedure is running... 1405 does not need to send a Multi-STA BlockAck frame to 1402.

[0310] In Figure 14, 1404 and 1407 are AID#2 by 1419 and 1420. I know that, but I don't know when 1409 sent 1421, that is, when 1407 assigned AID#2 to 1401. i. In Figure 14, AP MLD 1407 is assigned AID#2 to 1401, The AP MLD that sends the Multi-STA BlockAck frame to 1401 is different for 1404. If 1401 does not stop sending Data frames to 1404 while the transition preparation procedure is running, and 1402 holds AID#2 after AID#2 is assigned to 1401, then 1404 will be the one indicated in the AID11 subfield included in the Per AID TID Info subfield. There is a period during which it is not possible to determine whether AID 1402 is AID#1 or AID#2. Therefore, if 1402 holds AID#2 after it has been assigned to 1401, 1401 must stop sending Data Frames to 1404 while the transition preparation procedure is running. If frame transmission is not stopped, and AID#2 is assigned to 1401, and 1402 does not retain AID#2, then 1404 will have the AID11 subfield included in the Per AID TID Info subfield. In the field, by indicating AID#1 as the AID for 1402, 1401 will continue to receive acknowledgments for the data frame it sent to 1404, even after AID#2 is assigned. It is possible.

[0311] For example, in transition preparation, if the current AP MLD assigns AID#2 to a non-AP MLD using a Transition Response Frame, negotiation is necessary between the current AP MLD and the target AP MLD during transition preparation to determine whether AID#2 is being used to identify other non-AP STAs or other non-AP MLDs connected to the target AP MLD. In each embodiment, by assigning AID#2 to a non-AP MLD during the transition preparation procedure, the AP during transition preparation will have to consider which AID#2 is available. This eliminates the need for negotiations between MLDs. As a result, the time during which connectivity is lost between non-AP MLDs and DSs during Seamless Transition can be minimized.

[0312] 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.

[0313] "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."

[0314] 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.

[0315] As described above, the embodiments of the present invention relate the current AP to the target AP MLD. Upon successful setup, the same AID is assigned to all non-AP STAs to which the non-AP MLD belongs. This invention enables more efficient execution of Seamless Transition.

[0316] 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.

[0317] 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.

[0318] 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. Furthermore, "computer-readable recording media" refers to portable media such as flexible disks, magneto-optical disks, ROMs, and CD-ROMs, as well as hard disks built into computer systems. It refers to a storage device.

[0319] 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.

[0320] 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.

[0321] 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.

[0322] Furthermore, some or all of the terminal device and base station device in the above-described embodiments may be implemented as LSIs, which are typically integrated circuits, or as chipsets. Each functional block of the device and base station equipment may be individually chipped, or some or all of them may be integrated into a single chip. Furthermore, the method of integrated circuit creation is not limited to LSIs; dedicated circuits or general-purpose circuits may also be used. 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.

[0323] 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.

[0324] 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]

[0325] 101, 201, 205 BSS 102, 202, 206 AP 103, 104, 203, 204, 207, 208 STA 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 base station device having a first AP MLD, The aforementioned first AP MLD is connected to a non-AP MLD. The base station device includes a processing unit that performs a first procedure, The first AP MLD of the base station device is Upon successful completion of the first step, A first AID, which is the same AID for all non-AP STAs to which the aforementioned non-AP MLD belongs, is assigned to the aforementioned non-AP MLD. The first procedure described above is, In the roaming preparation procedure, This is the procedure for setting up a second link to AP MLD. Base station equipment.

2. The first AID mentioned above is The aforementioned first AP MLD, The AID assigned during the aforementioned roaming preparation procedure is The base station device according to claim 1.

3. The first procedure described above is, In order for the non-AP MLD to transition from the first AP MLD to the second AP MLD, It is executed before the roaming execution procedure. The aforementioned roaming execution procedure is: The procedure includes transferring the context necessary to enable the first AP MLD to operate with the second AP MLD, The base station device according to claim 1.

4. A terminal device having a non-AP MLD, The aforementioned non-AP MLD includes at least one non-AP STA, The terminal device includes a processing unit that performs a first procedure, The first non-AP STA belonging to the non-AP MLD of the terminal device is Having the same AID as the first AID assigned to the non-AP MLD in the first procedure, The first procedure described above is, In the roaming preparation procedure, This is the procedure for setting up a second link to AP MLD. Terminal device.

5. The first AP MLD is connected to the non-AP MLD. The aforementioned first AP MLD is Once the first step is successful, A first AID, which is the same AID for all non-AP STAs to which the aforementioned non-AP MLD belongs, is assigned to the aforementioned non-AP MLD. The first procedure described above is, In the roaming preparation procedure, This is the procedure for setting up a second link to AP MLD. Communication method.

Images