Inheritance-based link addition for multi-link settings

Abstract

Techniques are provided for reducing signaling overhead in multi-link reconfiguration. The first MLD generates a first configuration file for the first link, where the first configuration file includes a plurality of parameter sets, each parameter set being assigned an element identifier and including a first set of values related to operation of the first link. The first MLD generates a second configuration file for the second link, where one or more parameter sets having the same set of values as the first configuration file are omitted, and for each parameter set having a different set of values from the first configuration file, the element identifier and the second set of values are incorporated into the second configuration file. The first MLD generates a link reconfiguration frame including the first and second configuration files, and sends the frame to the second MLD.

Description

[0001] Cross-references to related applications This application claims the benefit of co-pending U.S. provisional patent application No. 63 / 580,211, filed September 1, 2023. The entire contents of the aforementioned patent application are incorporated herein by reference. Technical Field

[0002] The embodiments presented in this application generally relate to multi-link reconfiguration. More specifically, the embodiments disclosed herein relate to reducing the signaling overhead of multi-link setup by managing parameter inheritance among multiple per-STAprofile subelements. Background Technology

[0003] The IEEE 802.11be amendment defines the process for seamlessly adding links to the multilink (ML) setup of a non-access point (AP) multilink device (non-AP MLD, also known as a terminal multilink device (STA MLD)). This allows a non-AP MLD to dynamically add one or more links to its ML setup without reassociation. This operation utilizes Link Reconfiguration Request / Response frames. In the Link Reconfiguration Request frame, the STA MLD requesting the addition of a new link specifies the STA profile for the new link in the Per-STA Profile sub-element within the Reconfiguration Multi-link (ML) element. In the Link Reconfiguration Response frame, the AP MLD indicates, through the Per-STA Profile sub-element within the Basic ML element, that it accepts the AP's profile for the added link. Attached Figure Description

[0004] To provide a detailed understanding of the above features of this application, the application briefly summarized above can be described in more detail with reference to the embodiments (some of which are shown in the accompanying drawings). However, it should be noted that the drawings only show typical embodiments and therefore should not be considered limiting; other equally effective embodiments are conceivable.

[0005] Figure 1 An example environment is described in which a STA MLD adds multiple links to its current configuration according to some embodiments of this application.

[0006] Figure 2 An example reconfiguration ML element according to some embodiments of this application is depicted.

[0007] Figure 3 An example reconfiguration ML element comprising two Per-STA Profile sub-elements with fully inherited parameters, according to some embodiments of this application, is depicted.

[0008] Figure 4 An example reconfiguration ML element comprising two Per-STA Profile sub-elements with incomplete parameter inheritance is depicted according to some embodiments of this application.

[0009] Figure 5 An example reconfiguration ML element comprising two Per-STA Profile sub-elements with globally non-inherited fields is depicted according to some embodiments of this application.

[0010] Figure 6 An example reconfiguration ML element is depicted according to some embodiments of this application, comprising two Per-STA Profile sub-elements having profile-specific, non-inherited fields.

[0011] Figure 7 An example method is described according to some embodiments of this application for generating a Link Reconfiguration Request frame that includes multiple Per-STA Profile sub-elements with applied inheritance rules.

[0012] Figure 8 This is a flowchart illustrating an example method for managing parameter inheritance among multiple Per-STA Profile sub-elements according to some embodiments of this application.

[0013] Figure 9An example network device configured to perform various aspects of this application is described.

[0014] For ease of understanding, common elements across the figures are identified using the same reference numerals where possible. It is conceivable that elements disclosed in one embodiment may be advantageously used in other embodiments without specific explanation. Detailed Implementation

[0015] Overview One embodiment of this application provides a method comprising: generating a first profile for a first link by a first multi-link device (MLD), wherein the first profile includes a plurality of parameter sets, each parameter set being assigned a corresponding element identifier and including a corresponding first value set related to the operation of the first link; generating a second profile for a second link by the first MLD; generating a link reconfiguration frame including the first and second profiles by the first MLD; and transmitting the link reconfiguration frame to the second MLD by the first MLD. The generation of the second profile includes: omitting one or more parameter sets within the plurality of parameter sets that have the same value set as the first profile in the second profile; and for each parameter set within the plurality of parameter sets that has a different value set than the first profile, incorporating the corresponding element identifier and a corresponding second value set related to the operation of the second link into the second profile.

[0016] Other embodiments of this application provide one or more non-transitory computer-readable media containing computer program code in any combination of forms, which, when executed by operation of a computer system, performs operations according to one or more of the methods described above; and a system of a network device comprising one or more computer processors and one or more memories, which collectively contain one or more programs that, when executed by the one or more computer processors, perform operations according to one or more of the methods described above.

[0017] Example Implementation According to the definition in IEEE 802.11be, a non-AP MLD can seamlessly add a link to its ML setup by sending a Link Reconfiguration Request frame to the AP, without re-associating it. The Link Reconfiguration Request frame includes a Reconfiguration ML element, which also includes a Per-STA Profile sub-element containing all the necessary parameters related to the operation and establishment of the new link for the non-AP MLD. Upon receiving the request, the AP evaluates these parameters and determines whether to add the new link based on network policies and available resources. If the AP approves the request and decides to establish the link, it sends a Link Reconfiguration Response frame to the non-AP MLD. This response frame includes the necessary configuration details from the Basic ML element, such as the parameters of the new link, channel access settings, and any security credentials required to set up the link.

[0018] In some embodiments, a non-AP MLD can request the addition of multiple links to its ML setup in a single Link Reconfiguration Request frame. This can be achieved by the non-AP MLD sending a Link Reconfiguration Request frame to its associated AP MLD or the new AP MLD to which it intends to roam. The Link Reconfiguration Request frame may include multiple Per-STA Profile sub-elements, each corresponding to a specific link and containing a complete profile for the non-AP STA. The AP MLD can process the request, and if approved, can send a Link Reconfiguration Response frame back to the STA MLD. The response frame may also include multiple Per-STA Profile sub-elements, each containing a complete profile for the AP MLD and the relevant parameters for establishing the corresponding link.

[0019] The IEEE 802.11be amendment does not define inheritance rules for parameters (or elements) between these Per-STA Profile sub-elements within the Reconfiguration ML and Basic ML elements. Therefore, the current approach to adding link operations defined in the IEEE 802.11be amendment may result in common parameters between Per-STA Profile sub-elements being included multiple times in the same Link Reconfiguration Request / Response frame. This redundancy makes the frames lengthy and consumes more airtime.

[0020] Embodiments of this application propose techniques for optimizing signaling overhead during ML reconfiguration, more specifically, by reducing the size of Link Reconfiguration Request / Response frames through the application of inheritance rules among sub-elements of the Per-STA Profile. This method effectively minimizes (or at least reduces) redundancy and reduces airtime consumption.

[0021] The Per-STA Profile sub-elements within a Link Reconfiguration Request / Response frame can include various parameters (or elements) related to the operation of non-AP STAs and AP MLDs, as well as parameters related to establishing a new link between the two devices. These parameters include, but are not limited to: STA MAC address, AP MAC address, channel access parameters, security capabilities and configurations, and power management parameters.

[0022] In some embodiments, element identifiers (IDs) and / or element ID extensions can be assigned to one or more parameters (or elements) contained within a Per-STA Profile sub-element. When multiple links are added between a non-AP STA and an AP MLD, resulting in a single Link Reconfiguration Request / Response frame containing multiple Per-STA Profile sub-elements, the first Per-STA Profile sub-element can contain the complete profile, including all necessary operational and link establishment parameters for the non-AP STA. Subsequent Per-STA Profile sub-elements can inherit all values ​​from the first profile (explicitly or implicitly via positive inheritance elements), except where they include element identifiers (IDs) and / or element ID extensions with new values, or where these element identifiers (IDs) and / or element ID extensions are listed in non-inheritance elements. This disclosed inheritance mechanism significantly reduces the size of LinkReconfiguration Request / Response frames by avoiding duplication of the same parameters (or elements) across multiple Per-STA profiles.

[0023] Figure 1 An example environment 100 is described, which depicts a STA MLD 110 according to some embodiments of this application, adding multiple links to its current configuration.

[0024] As shown in the figure, example environment 100 contains two Basic Service Sets (BSS), namely BSS 1 and BSS 2. These two BSSs reside within the same Service Life Set (ESS). BSS 1 includes AP MLD 120-1, while BSS 2 includes AP MLD 120-2. Each AP MLD consists of two radios. As shown in the figure, AP MLD 120-1 includes AP 115-1 and AP 115-2, while AP MLD 120-2 includes AP 115-3 and AP 115-4.

[0025] As shown in the figure, STA MLD 110 includes two radios, namely STA 105-1 and STA 105-2. As used herein, the term "radio" can refer to the ability to connect to a peer device via a link. As shown within STA MLD 110, the two radios 105-1 and 105-2 can represent two physical radios or two logical radios enabled by a single physical radio (capable of being used on two different links via time-division switching).

[0026] As shown in the diagram, STA MLD 110 is located in the overlapping area of ​​two BSSs and is currently connected to AP MLD 120-1 via two links, Link 1 and Link 2. Link 1 connects AP 115-1 to STA 105-2, and Link 2 connects AP 115-2 to STA 105-2. STA MLD 110 is moving away from AP MLD 120-1 and towards AP MLD 120-2. Therefore, STA MLD 110 is roaming towards AP MLD 120-2 and plans to establish two new links: one between STA 105-1 and AP 115-3, and the other between STA 105-2 and AP 115-4.

[0027] To set up a new link, STA MLD 110 sends a LinkReconfiguration Request frame 130 to AP MLD 120-2. Request frame 130 can include two Per-STA Profile sub-elements within its Reconfiguration ML element, each profile corresponding to the newly added link. For example, the first Per-STA Profile sub-element can include all the necessary parameters required to establish a link between STA 105-1 and AP 115-3, and the second Per-STA Profile sub-element can include all the necessary parameters required to establish a link between STA 105-2 and AP 115-4.

[0028] AP MLD 120-2 receives Link Reconfiguration Request frame 130 and evaluates the request based on the current network policy and available network resources. If AP MLD 120-2 approves the request, it sends Link Reconfiguration Response frame 135 to STA MLD 110. Response 135 may also include two Per-STA Profile sub-elements within a Basic ML element, each sub-element including (if accepted) configuration details for the corresponding new link: one for the link between STA 105-1 and AP 115-3, and another for the link between STA 105-2 and AP 115-4.

[0029] In conventional systems, due to the lack of defined and applied inheritance rules, each Per-STA Profile sub-element within LinkReconfiguration Request / Response frames 130 and 135 includes a complete profile for establishing the corresponding new link. Therefore, identical parameters (or elements) may be repeatedly included in each profile, leading to increased frame length and higher airtime consumption. In the system shown, by defining and applying inheritance rules between Per-STA Profile sub-elements, redundant parameter duplication can be avoided, thereby reducing signaling overhead and optimizing airtime utilization.

[0030] like Figure 1As illustrated, to clearly illustrate the concept, a STA MLD 110 including two radio devices (e.g., STA 105-1 and STA 105-2) is provided. In some embodiments, the STA MLD 110 may include more than two radio devices, and more than two links need to be added when roaming from AP MLD 120-1 to AP MLD 120-2. In this configuration, the Link Reconfiguration Request / Response frame may contain multiple (e.g., more than two) Per-STA Profile sub-elements. If each sub-element contains a complete profile, it may make the frame length unnecessarily verbose and inefficient, consuming excessive airtime. Therefore, to avoid repeating the same parameters (or elements) across multiple profiles, inheritance rules for the first profile can be implemented in Link Reconfiguration Request / Response frames 130 and 135. By applying these rules, subsequent Per-STA Profile sub-elements contain only unique parameters or changes, thereby effectively reducing signaling overhead and improving the overall efficiency of ML reconfiguration.

[0031] In some embodiments, STA MLD 110 may remain connected to AP MLD 120-1 but intend to add additional links within the same configuration. STA MLD 110 may send a LinkReconfiguration Request frame 130 to AP MLD 120-1 to establish these additional links. The request may include multiple Per-STA Profile sub-elements, each corresponding to a new link that STA MLD intends to add. AP MLD 120-1 may process the request, and if approved, AP MLD 120-1 may send a Link Reconfiguration Response frame 135 back to STA MLD 110. The response may also include multiple Per-STA Profile sub-elements, each providing the necessary details required to establish the new link. To reduce redundancy and optimize the reconfiguration process, inheritance rules may also be applied to these LinkReconfiguration Request / Response frames.

[0032] Figure 2Example reconfiguration ML element 200 according to some embodiments of this application is depicted. In some embodiments, the reconfiguration ML element 200 can be used by: non-AP MLD (e.g., Figure 1 Initiating an ML reconfiguration operation by AP MLD (e.g., 110) to add or remove links in its existing ML settings; and / or by AP MLD (e.g., 120-1) for its associated non-AP MLD (e.g., Figure 1 110) provides recommendations regarding ML reconfiguration. In some embodiments, the Reconfiguration ML element 200 may be included in a LinkReconfiguration Request frame (e.g., Figure 1 (130) in the middle.

[0033] As shown in the figure, the Reconfiguration ML element 200 consists of six fields: Element ID field 202, Length field 204, Element ID Extension field 208, Multi-Link Control field 210, Common Info field 212, and Link Info field 214. One or more Per-STA Profile sub-elements 216 are contained within the Link Info field 214. Each Per-STA Profile sub-element 216 represents a configuration for non-AP STAs (e.g., ...). Figure 1 The specific link configuration of 110 in the middle.

[0034] As shown in the figure, each Per-STA Profile sub-element 216 includes five fields: Subelement ID 220, Length 222, STA Control 224, STA Info 226, and STA Profile 228. The STA Profile field 224 contains specific control information for non-AP STAs, which includes nine subfields: Link ID subfield 230, Complete Profile subfield 232, STA MAC Address Present subfield 234, AP Removal TimerPresent subfield 236, Reconfiguration Operation Type subfield 238, Operation Parameters Present subfield 240, NSTR BitmapSize subfield 242, NSTR Indication Bitmap Present subfield 244, and Reserved subfield 246. The STA Info field 226 provides detailed information about the STA and includes five subfields: STA Info Length (subfield 250), STA MAC Address (subfield 252), AP Removal Timer (subfield 254), Operation Parameters (subfield 256), and NSTR Indication Bitmap (subfield 258). The STA Profile field 228 contains the necessary configuration data required for link establishment.The example parameters (or elements) contained in field 228 of the STA Profile may include, but are not limited to: channel access parameters, security parameters (e.g., authentication and key management (AKM) suites, cipher suites, group cipher suites, pairwise cipher suites, key management protocols, encryption methods, authentication methods), power management parameters (e.g., power saving mode, preferred wake-up time, maximum sleep duration, maximum transmit power, minimum transmit power), device capability parameters (e.g., supported data rates, supported channels, beamforming capabilities, supported modulation and coding scheme (MCS) index), and operating parameters (e.g., BSS identifier, BSS load, BSS affiliation information).

[0035] In non-AP STA (e.g., Figure 1 In the embodiment of adding multiple links (110), multiple Per-STA Profile sub-elements 216 can be included in the Link Info field 214 of the Reconfiguration ML element 200. By convention, each Per-STA Profile sub-element 216 corresponds to a specific link and contains all the necessary parameters required to establish that link.

[0036] Parameters (or elements) within these Per-STA Profile sub-elements 216 can share the same values ​​across multiple links. For example, if the same type of reconfiguration is applied across different links, subfields in the STA Control field 224 (such as Reconfiguration Operation Type 238) can be identical. Subfields in the STA Info field 226, such as Operation Parameters 256 or AP Removal Timer 254, can remain consistent across different links. Furthermore, within the STA Profile field 228, when links are intended to support similar traffic types or applications, channel access parameters (such as EDCA parameters and MU-EDCA parameters—e.g., Access Category (AC), Arbitration Interframe Spacing (AIFSN), Minimum Contention Window (CWmin), Maximum Contention Window (CWmax), and Transmission Opportunity Limit (TXOP)) can take the same values ​​across different links. If the same security protocol is required, security parameters such as the authentication and key management (AKM) suite can be kept consistent across multiple links.

[0037] Conventional methods can lead to unnecessary duplication of identical parameters across Per-STA Profile sub-elements, resulting in increased signaling overhead and inefficient use of airtime. To address these issues, inheritance rules can be applied across Per-STA Profile sub-elements to eliminate redundancy. Further details regarding the application of inheritance rules when generating multiple Per-STA Profile sub-elements will be provided below. Figures 3 to 6 Let's have a discussion.

[0038] Figure 3 An example reconfiguration ML element 300 according to some embodiments of this application is depicted, which includes two Per-STA Profile sub-elements 305 and 310 with full parameter inheritance.

[0039] The two Per-STA Profile sub-elements 305 and 310 can be included in the Link Info field of the Reconfiguration ML element 300 (e.g., Figure 2 214) in.

[0040] As shown in the figure, the first Per-STA Profile sub-element 305 includes the complete profile, which contains all the necessary data explicitly defined for establishing the first link. To enable efficient identification and potential inheritance among multiple profiles, each parameter (or element) is assigned an Element ID and / or Element ID extension (if applicable) within field 328 of the STA Profile. For example, Element ID 100 (identified in field 340-1) is assigned to AC, Element ID 101 (corresponding to field 350-1) is assigned to AIFSN, Element ID 102 (corresponding to field 360-1) is assigned to CWmin, and Element ID 103 (corresponding to field 370-1) is assigned to CWmax.

[0041] In the first Per-STA Profile sub-element 305 corresponding to the first link, the STA Profile field 328 includes the following sub-fields: Element ID sub-field 340-1 (indicating Element ID 100), Length sub-field 342-1 (indicating a length of 1 byte), Element ID Extension sub-field (optional) 344-1, and AC sub-field 346-1 (indicating voice (AC_VO)); Element ID sub-field 350-1 (indicating Element ID 101), Length field 352-1 (indicating a length of 1 byte), Element ID Extension sub-field (optional) 354-1, and AIFSN sub-field 356-1 (indicating 2); Element ID sub-field 360-1 (indicating Element ID 102), Length field 362-1 (indicating a length of 1 byte), Element ID Extension sub-field (… The first Per-STA Profile includes the optional IDExtension subfield 364-1 and the CWmin subfield 366-1 (indicating 7); the Element ID subfield 370-1 (indicating Element ID 103), the Length field 372-1 (indicating a length of 1 byte), the Element ID Extension subfield 374-1 (indicating 15), and the CWmax subfield 376-1. These subfields ensure that all necessary parameters required to establish the first link are explicitly defined in the first Per-STA Profile sub-element 305.

[0042] As shown in the figure, the second Per-STA Profile sub-element 310 is associated with the second link and provides the necessary data for establishing the link. Since the second link has the same AC, AIFSN, CWmin, and CWmax as the first link (for example, perhaps because both links serve the same service type or application), the second Per-STA Profile sub-element 310 no longer needs to repeat all these parameters. Instead, the second Per-STA Profile sub-element 310 implicitly inherits the AC data (AC_VO), AIFSN data (2), CWmin data (7), and CWmax data (15) from the first Per-STA Profile sub-element 305. Therefore, subfields for element ID, element ID extension, length, and / or specific data values ​​are omitted in the second profile, further reducing redundancy and signaling overhead for ML reconfiguration.

[0043] In some embodiments, the Positive Inheritance Element 380-1 may be included within the STA Profile 338 to enable explicit inheritance. More specifically, the Positive Inheritance Element 380-1 can provide explicit information about which parameters (or elements) the current profile 310 inherits from the first profile 305. This element ensures clarity when specific parameters require explicit references to inheritance. As shown, the Positive Inheritance Element 380-1 may include five subfields: Element ID subfield 382, ​​Length subfield 384, Element ID Extension subfield (if applicable) 386, List of Element IDs subfield 388, and List of Element ID Extensions subfield 390. The List of Element IDs subfield 388 also includes two additional subfields: Length subfield 392 and Element ID List subfield 394. The Element ID List subfield 394 specifically lists the Element IDs inherited from the first profile 305 by the second Per-STA Profile sub-element 310. Here, since the first and second links share the same values ​​for channel access parameters (e.g., AC (AC_VO), AIFSN (2), CWmin (7), and CWmax (15)), the Element ID List subfield 394 explicitly includes Element ID 100, Element ID 101, Element ID 102, and Element ID 103. In some embodiments, the positive inheritance element 380-2 may be added after the STA Profile field 338, rather than being included as the last item in the STA Profile field 338.

[0044] Figure 4An example reconfiguration ML element 400 according to some embodiments of this application is depicted, which includes two Per-STA Profile sub-elements 405 and 410 with incomplete parameter inheritance.

[0045] The two Per-STA Profile sub-elements 405 and 410 can be included in the Link Info field of the Reconfiguration ML element 400 (e.g., Figure 2 214) in.

[0046] As shown in the figure, the first Per-STA Profile sub-element 405 and Figure 3 The first Per-STA Profile sub-element 305 shown is identical. The first Per-STA Profile sub-element 405 contains all the necessary parameters required to establish the first link, including a complete profile with the following subfields: Element ID subfield 440-1 (indicating Element ID 100), Length subfield 442-1 (indicating a length of 1 byte), Element ID Extension subfield (optional) 444-1, and AC subfield 446-1 (indicating voice (AC_VO)); Element ID subfield 450-1 (indicating Element ID 101), Length field 452-1 (indicating a length of 1 byte), Element ID Extension subfield (optional) 454-1, and AIFSN subfield 456-1 (indicating 2); Element ID subfield 460-1 (indicating Element ID 101); Element ID subfield 460-1 (indicating Element ID 101); Element ID Sub ... The following fields are also present: ID (102), Length (462-1) (indicating a length of 1 byte), Element ID Extension (optional) 464-1, and CWmin (466-1) (indicating 7); Element ID (470-1) (indicating Element ID (103), Length (472-1) (indicating a length of 1 byte), Element ID Extension (474-1) (optional), and CWmax (476-1) (indicating 15).

[0047] In the second Per-STA Profile sub-element 410 corresponding to the second link, most parameters (such as AC, AIFSN, and CWmin) remain the same as those in the first profile. Therefore, the second Per-STA Profile sub-element 410 inherits these parameter values ​​from the first profile. For these parameters, the element ID, element ID extension, length, and specific data fields are omitted in the second profile 410.

[0048] However, for the second link, its CWmin differs from that of the first link. To address higher contention, the CWmax used for the second link is set to 31 instead of 15. Therefore, the second Per-STA Profile sub-element also includes the following subfields: Element ID subfield 470-2 (indicating Element ID 103), Length field 472-2 (indicating a length of 1 byte), Element ID Extension subfield (optional) 474-2, and CWmax subfield 476-2 (indicating 31). The inclusion of the CWmax subfield 476-2 (with a value of 31) in the second Per-STA Profile sub-element 410 indicates that this new value overrides the value from the first profile (e.g., 15). In other words, unless the STA Profile field 438 of the subsequent Per-STA Profile sub-element 410 carries the same Element IDs (e.g., 103) and / or Element ID Extensions with new values ​​(e.g., 31), the parameters (or elements) carried in the STA Profile field 428 of the first Per-STA Profile sub-element 405 will be inherited and treated as part of the subsequent Per-STA Profile sub-element 410.

[0049] In some embodiments, the Positive Inheritance Element 480-1 may be included within the STA Profile 438, providing explicit information about which parameters (or elements) are inherited by the current profile 410 from the first profile 405. As shown, the Positive Inheritance Element 480-1 may include five subfields: Element ID subfield 482, Length subfield 484, Element ID Extension subfield (if applicable) 486, List of Element IDs subfield 488, and List of Element ID Extensions subfield 490. The List of Element IDs subfield 488 also includes two additional subfields: Length subfield 492 and Element ID List subfield 494. The Element IDList subfield 494 specifically lists the element IDs inherited from the first profile 405 by the second Per-STA Profile sub-element 410. Here, since the first and second links share the same values ​​for AC, AIFSN, and CWmin, but have different values ​​for CWmax, the Element IDList subfield 494 explicitly includes Element ID 100, Element ID 101, and Element ID 102, indicating that these parameters are inherited. In some embodiments, Positive InheritanceElements 480-2 may be added after the STA Profile 338 of the second profile 410, rather than being included within the STA Profile 438.

[0050] like Figure 3 and Figure 4As shown, to clearly illustrate the concept, an example Reconfiguration ML element including two Per-STA Profile sub-elements is provided. In some embodiments, the Reconfiguration ML element may include any number of Per-STA Profile sub-elements (including one), depending on the number of links added to the ML setting. For example, if only one link is added, the Reconfiguration ML element may include a single Per-STA Profile sub-element (e.g., ...). Figure 3 (305 in the text). If multiple links are added, the Reconfiguration ML element can include multiple Per-STA Profile sub-elements (e.g., Figure 3 305 and 310 in the middle, Figure 4 (405 and 410 in the text), each sub-element corresponds to a specific link.

[0051] In some embodiments, in addition to the STA Profile field (e.g., Figure 3 328 in Figure 4 In addition to 428), Element IDs and / or Element ID Extensions can also be assigned to STA Control fields (e.g., Figure 3 324 in the middle, Figure 4 The 424) and / or STA Information (STAInfo) fields (e.g., Figure 3 326 in the middle, Figure 4 The parameters (or elements) in 426) of the table. Examples of such parameters (or elements) may include: Reconfiguration Operation Type (e.g., Figure 2 238 in the middle), AP Removal Timer (e.g., Figure 2 254 in the middle) and operation parameters (e.g., Figure 2 (256 in the example). These identifiers enable efficient management of these parameters (or elements) across multiple profiles. For example, in a second Per-STA profile (e.g., ...) sub-elements... Figure 3 310 in the middle, Figure 4In section 410), if the reconfiguration operation type and AP removal timer are related to the first Per-STA Profile sub-element (e.g., Figure 3 305 in the middle, Figure 4 If the same condition is found in 305, then it can be found in a positive inheritance element (e.g., Figure 3 380 in Figure 4 Within 480, these parameters are referenced using element IDs (e.g., element IDs for the Reconfiguration Operation Type), explicitly indicating that the values ​​of these parameters are inherited from the first configuration file.

[0052] Figure 3 and Figure 4 This shows how element IDs can be assigned to STAProfile fields (e.g., Figure 3 328 in Figure 4 The various parameters (or elements) in 428) are used to achieve efficient identification and potential inheritance between multiple configuration files. Although Figure 3 and Figure 4 The focus is on four specific channel access parameters (e.g., AC, AIFSN, CWmin, and CWmax), but these examples are provided only for clarity of concept. In some embodiments, STA Profile fields (e.g., Figure 3 328 in Figure 4 428 in the middle can include more than Figure 3 and Figure 4 This includes a wider range of parameters (or elements). For example, the STA Profile field may also include additional EDCA / MU-EDCA parameters. Furthermore, the STA Profile field may contain parameters (or elements) related to security settings (e.g., Authentication and Key Management (AKM) suites, cipher suites, group cipher suites, pairwise cipher suites, key management protocols, encryption methods, authentication methods), parameters (or elements) related to power management (e.g., maximum sleep duration, maximum transmit power, minimum transmit power), parameters (or elements) related to device capabilities (e.g., supported data rates, supported channels, beamforming capabilities, supported MCS indexes), and operational parameters (e.g., BSS identifier, BSS load, BSS affiliation information).

[0053] By assigning element IDs and / or element ID extensions (if applicable) to these various parameters (or elements), the Reconfiguration ML element can effectively manage the information required for link establishment and reconfiguration. In embodiments where multiple links share the same values ​​for certain parameters (or elements), inheritance rules can be applied to reduce redundancy and signaling overhead, such as... Figure 3 and Figure 4 As shown.

[0054] Figure 5 An example reconfiguration ML element 500 according to some embodiments of this application is depicted, which includes two Per-STA Profile sub-elements 505 and 510 with a global non-inherited field 580.

[0055] The two Per-STA Profile sub-elements 505 and 510 can be included in the Link Info field of the Reconfiguration ML element 500 (e.g., Figure 2 Within (214). The first Per-STA Profile sub-element 505 corresponds to the first link and includes a complete profile that explicitly defines all the necessary data required to establish the first link. The second Per-STA Profile sub-element 510 corresponds to the second link and may inherit certain parameters (or elements) from the first profile.

[0056] As shown in the figure, the STA Profile field 528 in the first Per-STA Profile sub-element 505 is... Figure 3 and Figure 4The STA Profile fields 328 and 428 shown are identical, including the following subfields: Element ID subfield 540-1 (indicating Element ID 100), Length subfield 542-1 (indicating a length of 1 byte), Element ID Extension subfield (optional) 544-1, and AC subfield 546-1 (indicating voice (AC_VO)); Element ID subfield 550-1 (indicating Element ID 101), Length field 552-1 (indicating a length of 1 byte), Element ID Extension subfield (optional) 554-1, and AIFSN subfield 556-1 (indicating 2); Element ID subfield 560-1 (indicating Element ID 102), Length field 562-1 (indicating a length of 1 byte), Element ID Extension subfield 544-1, and AC subfield 546-1 (indicating voice (AC_VO)); Element ID subfield 54 ... The optional extension subfield 564-1 and the CWmin subfield 566-1 (indicating 7); the element ID subfield 570-1 (indicating element ID 103), the length field 572-1 (indicating a length of 1 byte), the optional element ID extension subfield 574-1, and the CWmax subfield 576-1 (indicating 15). However, as Figure 5 As shown, the first Per-STA Profile sub-element 505 also includes a Global Non-Inheritance field 580, which follows but is independent of STA Profile field 528, or is the last item within STA Profile field 528 (e.g., 580-1). The Global Non-Inheritance field 580 provides information about parameters (or elements) that should not be inherited by any subsequent profiles. Specifically, the Global Non-Inheritance field 580 indicates that all subsequent profiles should explicitly include the new values ​​for these parameters (or elements), even if these values ​​remain unchanged or have only minor differences.

[0057] As shown in the figure, the global non-inheritance field 580 consists of five subfields: Element ID (582), Length (584), Element ID Extension (if applicable) (586), List of Element IDs (588), and List of Element ID Extensions (590). The List of Element IDs (588) subfield also includes two additional subfields: Length (592) and Element ID List (594). The Element ID List (594) subfield specifically lists the non-inheritable Element IDs. In other words, unless the first Per-STA Profile sub-element 505 includes a global non-inheritance field 580 and the element IDs (e.g., element ID 100) and / or element ID extensions for these parameters (or elements) are listed in the global non-inheritance field 580, the parameters (or elements) carried in the STA Profile field 528 of the first Per-STA Profile sub-element 505 will be inherited and treated as part of the subsequent Per-STA Profile sub-element 510.

[0058] As shown in the figure, subfield 594 of the Element ID List indicates that Element ID 100 (AC) and Element ID 102 (CWmin) cannot be inherited by any subsequent profile. More specifically, any Per-STA Profile sub-elements after the first profile should explicitly include the new value for AC (e.g., Background (AC_BK)) and the new value for CWmin (e.g., 15), regardless of whether these values ​​remain the same or differ.

[0059] As shown in the figure, in the second Per-STA Profile sub-element 510, the following subfields are included in its STA Profile field 538: Element ID subfield 540-2 (indicating Element ID 100), Length subfield 542-2 (indicating a length of 1 byte), Element ID Extension subfield 544-2 (optional), AC subfield 546-2 (indicating AC_BK); Element ID subfield 560-2 (indicating Element ID 102), Length subfield 562-2 (indicating a length of 1 byte), Element ID Extension subfield 564-2 (optional), CWmin subfield 566-2 (indicating 15).

[0060] Since the global non-inheritance field 580 explicitly states that the values ​​of Element ID 100 (AC) and Element ID 102 (CWmin) are not inherited by subsequent profiles, the second Per-STA Profile sub-element 510 specifies new values ​​(e.g., AC_BK, 15) for these two parameters (or elements), which will override the values ​​presented in the first profile 505 (e.g., AC_VO, 7). Furthermore, since the Element IDs of AIFSN (e.g., Element ID 101) and CWmax (e.g., Element ID 103) are not listed in the global non-inheritance field 580, the values ​​of these two parameters are implicitly inherited by the second profile 510. Therefore, the sub-fields for AIFSN and CWmax are omitted in the second profile 510.

[0061] Figure 6 An example reconfiguration ML element 600 according to some embodiments of this application is depicted, which includes two Per-STA Profile sub-elements 605 and 610 having a profile-specific non-inheritance field 680.

[0062] The two Per-STA Profile sub-elements 605 and 610 can be included in the Link Info field of the Reconfiguration ML element 600 (e.g., Figure 2 Within (214). The first Per-STA Profile sub-element 605 corresponds to the first link and includes a complete profile that explicitly defines all the necessary data required to establish the first link. The second Per-STA Profile sub-element 610 corresponds to the second link and may inherit certain parameters (or elements) from the first profile.

[0063] As shown in the figure, the STA Profile field 628 in the first Per-STA Profile sub-element 605 is... Figure 3 , Figure 4 as well as Figure 5The STA Profile fields 324, 428, and 528 shown are identical, including the following subfields: Element ID subfield 640-1 (indicating Element ID 100), Length subfield 642-1 (indicating a length of 1 byte), Element ID Extension subfield (optional) 644-1, and AC subfield 646-1 (indicating voice (AC_VO)); Element ID subfield 650-1 (indicating Element ID 101), Length field 652-1 (indicating a length of 1 byte), Element ID Extension subfield (optional) 654-1, and AIFSN subfield 656-1 (indicating 2); Element ID subfield 660-1 (indicating Element ID 102), Length field 662-1 (indicating a length of 1 byte), Element ID Extension subfield 644-1, and AC subfield 646-1 (indicating voice (AC_VO)); Element ID subfield 650-1 (indicating Element ID 101), Length field 652-1 (indicating a length of 1 byte), Element ID Extension subfield 654-1, and AIFSN subfield 656-1 (indicating 2); Element ID subfield 660-1 (indicating Element ID 102), Length field 662-1 (indicating a length of 1 byte), Element ID Extension subfield 654-1, and AC subfield 646-1 (indicating voice (AC_VO)); Element ID Subfield 660-1 (indicating Element ID 102), Length field 662-1 (indicating a length of 1 byte), Element ID Extension subfield 654-1, and AC Subfield 646-1 (indicating voice (AC_VO)); Element ID Subfield 6 Extension) subfield (optional) 664-1, and CWmin subfield 666-1 (indicating 7); Element ID subfield 670-1 (indicating Element ID 103), Length field 672-1 (indicating length is 1 byte), Element ID Extension subfield (optional) 674-1, and CWmax subfield 676-1 (indicating 15).

[0064] In the second Per-STA Profile sub-element 610, Figure 6 A configuration file-specific non-inheritance field 680 is introduced. This field provides information about parameters (or elements) in the second configuration file 610 that differ from those in the first configuration file 605. Figure 5 Unlike the global non-inheritance field 580 that affects all subsequent configuration files, the configuration file-specific non-inheritance field 680 applies only to the second configuration file 610. Only the second configuration file 610 does not inherit the values ​​of these listed parameters (or elements) from the first configuration file.

[0065] As shown in the figure, the configuration file-specific non-inheritance field 680 either immediately follows but is independent of the STA Profile 638 (e.g., 680-2), or it is located within the STA Profile field 638, and if present, constitutes its last field (e.g., 680-1). The configuration file-specific non-inheritance field 680 consists of five subfields: Element ID subfield 682, Length subfield 684, Element ID Extension subfield (if applicable) 686, List of Element IDs subfield 688, and List of Element ID Extensions subfield 690. The List of Element IDs subfield 688 also includes two additional subfields: Length subfield 692 and Element ID List subfield 694. The Element ID List subfield 694 specifically lists element IDs that are not inheritable in the current profile. In other words, unless a subsequent Per-STA Profile sub-element 610 includes a profile-specific Non-Inheritance field 680 and the element IDs (e.g., element ID 102) and / or element ID extensions used for these parameters (or elements) are already listed within the profile-specific Non-Inheritance field 680, the parameters (or elements) carried in the STA Profile field 628 of the first Per-STA Profile sub-element 605 will be inherited and considered as part of the subsequent Per-STA Profile sub-element 610.

[0066] like Figure 6As shown, the Element ID List subfield 694 indicates that Element ID 103 (CWmax) will not be inherited by the second profile 610 from the first profile 605. This means that the second Per-STA Profile sub-element 610 should include a new value for CWmax, whether that value remains the same or is different.

[0067] As shown in the figure, in the second Per-STA Profile sub-element 610, the following subfields are included in its STA Profile field 638: Element ID subfield 670-2 (indicating Element ID 103), Length subfield 672-2 (indicating a length of 1 byte), Element ID Extension subfield 674-2 (optional), and CWmax subfield 676-2 (indicating 31).

[0068] The configuration file-specific non-inheritance field 680 allows specific parameters (or elements) to be overridden in the current configuration file while maintaining inheritance of other parameters (or elements) from the first configuration file. In the second Per-STA Profile 610, a new value for CWmax (e.g., 31) overrides the value presented in the first configuration file (e.g., 15), while the values ​​of AC (e.g., AC_VO), AIFSN (e.g., 2), and CWmin (e.g., 7) are implicitly inherited from the first configuration file, and the subfields for these parameters (or elements) are omitted in the second configuration file 610.

[0069] like Figure 5 and Figure 6 As shown, to clearly illustrate the concept, an example Reconfiguration ML element is provided, which includes two Per-STA Profile sub-elements. In some embodiments, the Reconfiguration ML element may include any number of Per-STA Profile sub-elements (including one), depending on how many links are added to the ML settings.

[0070] In some embodiments, in addition to the STA Profile field (e.g., Figure 5 528 in the middle, Figure 6In addition to 628 in the above, Element IDs and / or Element ID Extensions can also be assigned to STA Control fields (e.g., Figure 5 524 in the middle, Figure 6 The 624) and / or STA Information (STAInfo) fields (e.g., Figure 5 526 in the middle, Figure 6 The parameters (or elements) in 626).

[0071] In some embodiments, a global non-inheritance field 580 and a profile-specific non-inheritance field 680 can be used together in a reconfiguration ML element. For example, a first per-STA profile sub-element (e.g., Figure 5 The 505 condition may include a global non-inheritance field (e.g., Figure 5 580 in the example is used to specify that certain parameters (such as AC and AIFSN) will not be inherited by any subsequent profiles. Within the same Reconfiguration ML element, a second Per-STA Profile sub-element (e.g., 510) can include profile-specific non-inheritance fields (e.g., ...). Figure 6 680 in the middle). This field indicates that the current profile does not inherit different parameters (such as CWmin) from the first profile. Therefore, when both global and profile-specific non-inheritance rules are applied, the second Per-STA Profile child element (e.g., Figure 5 The value of 510 should include new values ​​for AC, AIFSN, and CWmin.

[0072] In some embodiments, the STA Profile field (e.g., Figure 5 528 and 538 in the middle, Figure 6628 and 638 in the table may include subfields, such as a Complete Profile subfield, to indicate whether the current STA Profile is a complete profile or inherits data from a previous profile. In some embodiments, the subfield may use binary values ​​(e.g., 0 or 1) to indicate the state of the profile. For example, a value of 1 may be used to indicate that the current STA Profile field includes a complete profile, where all necessary data is explicitly defined, while a value of 0 may be used to indicate that the current STA Profile field is not a complete profile but inherits data from a previous profile (e.g., a first Per-STA Profile sub-element).

[0073] The disclosed inheritance rules between Per-STA Profile sub-elements for the first Per-STA Profile sub-element provide an efficient mechanism for managing the configuration of multiple links in an ML setup. According to these rules, parameters (or elements) carried in the first Per-STA Profile sub-element will be inherited implicitly (e.g., via silent methods) or explicitly (e.g., via positive inheritance elements) and will be considered part of subsequent Per-STA Profile sub-elements (such as...). Figure 3 and Figure 4 (As shown). This inheritance remains valid only if subsequent Per-STA Profile child elements explicitly include the same element ID with the new value (e.g., ...). Figure 4 (As shown) or the element ID referencing this parameter is listed in a non-inheritance field (global or configuration file specific) (e.g. Figure 5 and Figure 6 Except as shown in the example. In some embodiments, these inheritance rules can be extended and applied to all frames except for Link Reconfiguration Request / Response frames (e.g., Figure 1 Any other management frames besides those shown as 130 or 135, which include multiple Per-STA Profile sub-elements, each intended to carry a complete profile for the corresponding STA.

[0074] In some embodiments, even with inheritance rules applied, the payload of a Per-STA Profile sub-element may still be too large (e.g., exceeding 255 bytes). In such a configuration, fragmentation of the Per-STA Profile sub-element may be necessary to accommodate transmission constraints. Inheritance rules can operate at a level higher than the sub-element fragmentation and reassembly process. For example, the Per-STA Profile sub-element can be compressed first by applying inheritance rules. If a multi-link element including the compressed Per-STA Profile sub-element, or if the compressed Per-STA Profile sub-element itself still exceeds the maximum allowed size (e.g., 255 bytes), the (sub)element can be segmented into smaller segments. Each segment can be structured with appropriate headers and metadata to ensure subsequent reassembly. Fragments of the (sub)element can be transmitted over the network in Link Reconfiguration Request / Response frames. After receiving all the fragments, the receiving device can reassemble them in the correct order to reconstruct the original ML elements and the compressed Per-STA Profile sub-elements. After fragment reassembly, inheritance rules can be applied to decompress the Per-STA Profile sub-elements, such as parsing parameters inherited from the first profile and applying these parameters to subsequent profiles.

[0075] In some embodiments, each Per-STA Profile sub-element (e.g., 605 or 610) can be assigned a profile number to uniquely identify the sub-element within a link reconfiguration frame. Profile numbers allow for more flexible inheritance across multiple profiles. For example, a third Per-STA Profile sub-element can inherit parameters from either the first Per-STA Profile sub-element 605 or the second Per-STA Profile sub-element 610 by referencing the corresponding profile number. The profile number can serve as a reference point, allowing the third profile to selectively inherit parameters from one of the earlier profiles. In some embodiments, a reference to the profile number can be included as an additional element within the third Per-STA Profile sub-element. This additional element can include one or more profile numbers indicating which profile the third Per-STA Profile sub-element is inheriting parameters from.

[0076] Figure 7 Example method 700 is described according to some embodiments of this application for generating link reconfiguration request / response frames including multiple per-STA profile sub-elements with applied inheritance rules. In some embodiments, when a non-AP STA (e.g., Figure 1 When an AP MLD (e.g., 100) attempts to add multiple links to its configuration by sending a Link Reconfiguration Request frame, example method 700 can be executed. In some embodiments, the example method can be provided by the AP MLD (e.g., Figure 1 AP120-2 in the document is executed when returning the Link Reconfiguration Response frame, the approval request, and when establishing the link.

[0077] In box 705, MLD generates a first Per-STA Profile sub-element for the first link (e.g., Figure 3 (305 in the original text). In some embodiments, the first Per-STA Profile sub-element may include the complete profile, wherein the STA Profile fields (e.g., ...) Figure 3All parameters within (328) are explicitly defined and assigned values. Furthermore, in some embodiments, each parameter (or element) within the STA Profile field may be assigned a corresponding Element ID (e.g., such as...). Figure 3 As shown, the element IDs (100) and / or element ID extensions (if applicable) are used for the average data rate. The assigned element IDs and / or element ID extensions (if applicable) can be used in subsequent configuration files to reference these values ​​(carried in the first configuration file) for inheritance.

[0078] In box 710, the MLD determines whether an additional link has been added. If an additional link has been added, an additional Per-STA Profile sub-element can be generated for this link and sent along with the first profile. If the MLD determines that no additional link has been added, method 700 proceeds to box 715, where the MLD incorporates the first Per-STA Profile sub-element into the management frame and sends it to the receiving device. When the MLD is a non-AP MLD (e.g., ...), Figure 1 In the embodiment of (110) in the example, the management frame may refer to a Link Reconfiguration Request frame. In the case where the MLD is the AP MLD (e.g., Figure 1 In the embodiment of 120-2), the management frame may refer to the link reconfiguration response frame.

[0079] If MLD determines that additional links have been added, method 700 proceeds to box 720, where MLD generates additional Per-STA Profile sub-elements for that additional link (e.g., Figure 3(See 310 in the original text). Additional Per-STA Profile sub-elements can include all the necessary data required to establish additional links. As part of generating additional Per-STA Profile sub-elements, in box 725, MLD determines whether parameters (or elements) can be inherited from the first profile. According to the inheritance rules described above, all parameters (or elements) within the STA Profile fields of the first Per-STA Profile sub-element can be implicitly (e.g., via silent) or explicitly (e.g., via positive inheritance elements) inherited by the additional Per-STA Profile sub-elements, except for parameters (or elements) that require different values ​​on the additional links or whose element IDs and / or element ID extensions are listed in non-inheritance fields (whether global or profile-specific). If the parameter (element) is inheritable, method 700 proceeds to box 730, where the element ID is included in an additional Per-STA Profile sub-element to indicate that the value from the first profile is carried over to the additional profile. If the parameter is not inheritable (possibly due to different link requirements or the presence of non-inheritance fields), method 700 proceeds to box 735, where MLD includes the new value of the parameter in an additional Per-STA Profile sub-element. This can be done for STA Profile fields (e.g., Figure 3 Each parameter (or element) within 328 is checked repeatedly until all parameters (or elements) are evaluated and correctly included in the second configuration file.

[0080] In box 740, MLD will include additional Per-STA Profile sub-elements (e.g., Figure 3The first element (310) in the management frame is included. Method 700 then returns to box 710, where the MLD continues to determine if any additional links (e.g., a third link) have been added. If an additional link has been added, the process of generating another Per-STA Profile sub-element continues. If no new link has been added, the method moves to box 715, where the MLD transmits the first and all newly added Per-STA Profile sub-elements from the management frame to the receiving device.

[0081] In some embodiments, such as when a multi-link element including compressed Per-STA Profile sub-elements or when the compressed Per-STA Profile sub-element itself exceeds a defined size limit (e.g., 255 bytes), the MLD can segment the (sub)element into fragments and send them separately to the receiving device. Each fragment may include a header and metadata (such as a sequence number or fragment identifier) ​​to ensure proper reassembly. Upon receiving the fragments, the receiving device can reassemble the fragmented pieces into the original (sub)element and decompress the Per-STA Profile sub-elements using inheritance rules.

[0082] Figure 8 This is a flowchart depicting an example method 800 for managing parameter inheritance among multiple Per-STA Profile sub-elements according to some embodiments of this application.

[0083] In box 805, the multilink device (MLD) generates a first profile for the first link, wherein the first profile includes multiple parameter sets, each parameter set being assigned a corresponding element identifier and including a corresponding first value set related to the operation of the first link.

[0084] In box 810, the MLD generates a second profile for the second link. To generate the second profile, the first MLD omits one or more parameter sets within the multiple parameter sets that have the same value set as the first profile, and for each parameter set within the multiple parameter sets that has a different value set than the first profile, the first MLD incorporates the corresponding element identifier and the corresponding second value set associated with the operation of the second link into the second profile. In some embodiments, the corresponding second value set may override the corresponding first value set of the corresponding element identifier within the second profile.

[0085] In box 815, the first MLD generates a link reconfiguration frame that includes the first and second profiles.

[0086] In box 820, the first MLD transmits the link reconfiguration frame to the second MLD.

[0087] In some embodiments, the first MLD may include a Terminal MLD (STA MLD), the second MLD may include an Access Point MLD (AP MLD), and the link reconfiguration frame may include a link reconfiguration request frame. In some embodiments, the first MLD may include an Access Point MLD (AP MLD), the second MLD may include a Terminal MLD (STA MLD), and the link reconfiguration frame may include a link reconfiguration response frame.

[0088] In some embodiments, the first MLD may incorporate additional elements within or after the first profile indicating a list of element identifiers that will not be inherited by any subsequent profile.

[0089] In some embodiments, the first MLD may incorporate additional elements within or after the second profile indicating a list of element identifiers that are not inherited by the second profile from the first profile.

[0090] In some embodiments, the second configuration file may include a new set of values ​​for the parameter set corresponding to the list of element identifiers, wherein the new set of values ​​is related to the operation of the second link.

[0091] In some embodiments, the first configuration file may include complete configuration file subfields, which include numbers indicating that the first configuration file includes a complete set of element identifiers whose corresponding parameter set is related to the operation of the first link.

[0092] In some embodiments, the first configuration file may include a complete configuration file subfield, which includes a second number indicating that the second configuration file inherits a first set of values ​​from the first configuration file.

[0093] In some embodiments, a link reconfiguration frame may include one or more additional profiles for one or more additional links, wherein each profile is identified by a profile number.

[0094] In some embodiments, a third configuration file, within one or more additional configuration files, may include references to one or more configuration file numbers of at least one of the first configuration file, the second configuration file, or one or more additional configuration files, for indicating from which configuration file the parameter set is inherited.

[0095] In some embodiments, one or more configuration file numbers may be carried as new elements in a third configuration file.

[0096] In some embodiments, the parameters in the first configuration file may include at least one parameter related to channel access, security settings, power management, or network operation.

[0097] In some embodiments, after receiving a link reconfiguration frame, the second MLD can determine that if an element contained in the first configuration file does not exist in the second configuration file and the element is not listed as a non-inherited element in the second configuration file, then the element is part of the second configuration file.

[0098] In some embodiments, a first MLD may determine that the size of a multi-link element exceeds a predefined threshold, wherein the multi-link element includes first and second profiles and is located within a link reconfiguration frame, and in response to the determination, divides the multi-link element into multiple fragments, wherein the size of each fragment is less than or equal to the predefined threshold, and transmits the multiple fragments to a second MLD via the link reconfiguration frame.

[0099] In some embodiments, a first MLD may determine that the size of a sub-element exceeds a predefined threshold, wherein the sub-element includes a first or second profile and is located within a link reconfiguration frame, and in response to the determination, divide the sub-element into multiple fragments, wherein the size of each fragment is less than or equal to the predefined threshold, and transmit the multiple fragments to a second MLD via the link reconfiguration frame.

[0100] In some embodiments, the first MLD may include a terminal MLD (STA MLD), the second MLD may include an access point MLD (AP MLD), and the link reconfiguration frame may include an association request carrying multiple profiles for multiple links.

[0101] In some embodiments, the first MLD may include an access point MLD (AP MLD), the second MLD may include a terminal MLD (STA MLD), and the link reconfiguration frame may include an associated response carrying multiple profiles for multiple links.

[0102] Figure 9 An example network device 900 configured to perform various aspects of this application is depicted according to some aspects of this application. In some embodiments, the example network device 900 may correspond to a non-AP MLD (such as, Figure 1 STA110 shown), or corresponding to AP MLD (such as, Figure 1 The AP MLD shown is 120-1 or 120-2.

[0103] As shown in the figure, the example network device 900 includes a processor 905, memory 910, storage device 915, one or more transceivers 920, one or more I / O interfaces 980, and one or more network interfaces 925. In some embodiments, I / O devices 940 are connected via I / O interfaces 980. Furthermore, via network interfaces 925, the network device 900 can be communicatively coupled to one or more other devices and components (e.g., via a network, which may include the Internet, a local area network, etc.). Each component is communicatively coupled via one or more buses 930. In some embodiments, one or more antennas 935 may be coupled to transceivers 920 for transmitting and receiving wireless signals.

[0104] Processor 905 typically represents a single central processing unit (CPU) and / or graphics processing unit (GPU), multiple CPUs and / or GPUs, a microcontroller, an application-specific integrated circuit (ASIC), or a programmable logic device (PLD). Processor 905 processes information received through transceiver 920, I / O interface 980, and network interface 925. Processor 905 can retrieve and execute programming instructions stored in memory 910, and can also store and retrieve application data residing in storage device 915.

[0105] Storage device 915 can be composed of any combination of devices such as hard disk drives, flash storage devices, etc., and can include fixed and / or removable storage devices, such as fixed hard disk drives, removable memory cards, caches, optical storage devices, network-attached storage devices (NAS), or storage area networks (SAN). Storage device 915 can store various types of data to enable efficient system operation.

[0106] Memory 910 may include random access memory (RAM) and read-only memory (ROM). Memory 910 may store processor-executable software code containing instructions that, when executed by processor 905, enable network device 900 to perform the various wireless communication functions described herein. In the illustrated example, memory 910 includes two software components: a configuration file compression / decompression component 645 and a frame fragmentation / fragmentation reassembly component 650.

[0107] In some embodiments, the configuration file compression / decompression component 645 can be configured to generate and compress Per-STA Profile sub-elements before transmission. The configuration file compression / decompression component 645 can assign element IDs and / or element ID extensions (if applicable) to parameters (or elements) within the STA Profile fields, and apply inheritance rules to reduce redundancy. The configuration file compression / decompression component 645 can ensure that each configuration file is either complete or correctly inherits values ​​from previous configuration files. Furthermore, when compressed Per-STA Profile sub-elements are received, the configuration file compression / decompression component 645 can decompress these sub-elements by applying inheritance rules and reconstruct a complete configuration file for each link.

[0108] In some embodiments, the frame fragmentation / fragmentation reassembly component 650 can be located in multi-link elements (e.g., Figure 2 200 in the Per-STA Profile (e.g., ) or Per-STA Profile sub-elements (e.g. Figure 2 When the size of a segment (e.g., 216) exceeds a defined limit (e.g., 255 bytes), its segmentation is processed. The frame fragmentation / reassembly unit 650 can split large multi-link elements or Per-STA Profile sub-elements into smaller fragments, each with its own header and metadata (e.g., sequence number or fragment identifier) ​​to ensure correct reassembly by the receiving device. Furthermore, when fragments of a (sub)element are received, the frame fragmentation / reassembly unit 650 can reassemble these fragments into their original format for subsequent processing.

[0109] Although the components shown are depicted as discrete components for clarity of concept, in some embodiments, the operation of the shown components (and other components not shown in the figures) may be combined or distributed among any number of components. Furthermore, although the shown components are depicted as software residing in memory 910, in some aspects, the operation of the shown components (and other components not shown in the figures) may be implemented using hardware, software, or a combination of hardware and software.

[0110] Various different embodiments are mentioned in this application. However, the scope of this application is not limited to the specifically described embodiments. Rather, any combination of the features and elements—whether or not related to different embodiments—is contemplated for implementing and practicing the contemplated embodiments. Furthermore, when elements in the embodiments are described in the form of "at least one of A and B" or "at least one of A or B," it should be understood that embodiments including only element A, only element B, and including both elements A and B are contemplated. While some embodiments disclosed herein may have advantages over other possible solutions or prior art, whether a given embodiment achieves a particular advantage does not limit the scope of this application. Therefore, the aspects, features, embodiments, and advantages disclosed herein are merely illustrative and should not be considered elements or limitations of the appended claims unless expressly listed in the claims. Similarly, references to "the present invention" should not be construed as a generalization of any inventive subject matter disclosed herein and should not be considered elements or limitations of the appended claims unless expressly listed in the claims.

[0111] Those skilled in the art will understand that the embodiments disclosed herein can be embodied as systems, methods, or computer program products. Therefore, embodiments can take the form of purely hardware embodiments, purely software embodiments (including firmware, resident software, microcode, etc.), or embodiments combining software and hardware aspects, and are collectively referred to herein as “circuit,” “module,” or “system.” Furthermore, embodiments can also take the form of computer program products embodied in one or more computer-readable media on which computer-readable program code is carried.

[0112] Program code embodied on a computer-readable medium may be transmitted using any suitable medium, including but not limited to wireless, wired, fiber optic cable, RF, or any suitable combination of the above media.

[0113] The computer program code used to perform the operations of the embodiments of this application can be written in any combination of one or more programming languages, including object-oriented programming languages ​​(such as Java, Smalltalk, C++, etc.) and conventional procedural programming languages ​​(such as the "C" programming language or similar programming languages). The program code can be executed entirely on the user's computer, or partially on the user's computer as a standalone software package, or partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the latter scenario, the remote computer can be connected to the user's computer via any type of network (including a local area network (LAN) or a wide area network (WAN)), or can be connected to an external computer (e.g., using the Internet through an Internet service provider).

[0114] Various aspects of this application have been described herein with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments set forth in this application. It should be understood that each block in the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, or other programmable data processing apparatus to generate a machine such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, form means for implementing the functions / operations specified in the blocks of the flowchart illustrations and / or block diagrams.

[0115] These computer program instructions may also be stored in a computer-readable medium that instructs a computer, other programmable data processing apparatus, or other device to operate in a particular manner, such that the instructions stored in the computer-readable medium form an article of writing comprising instructions for implementing functions / operations specified in boxes of flowcharts and / or block diagrams.

[0116] Computer program instructions may also be loaded onto a computer, other programmable data processing apparatus or other device to cause a series of operational steps to be performed on the computer, other programmable apparatus or other device, thereby creating a computer-implemented process, such that the instructions that execute on the computer, other programmable data processing apparatus or other device provide a process for implementing the function / operation specified in the boxes of a flowchart and / or block diagram.

[0117] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various different embodiments. In this sense, each box in a flowchart or block diagram may represent a module, code segment, or portion of code, comprising one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions marked in the boxes may not occur in the illustrated order. For example, two boxes shown consecutively may actually be executed substantially simultaneously, or these boxes may sometimes be executed in reverse order, depending on the functionality involved. It should also be noted that each box in the flowcharts and / or block diagrams, and combinations of boxes in the flowcharts and / or block diagrams, may be implemented by a dedicated hardware system performing the specified function or operation, or by a combination of dedicated hardware and computer instructions.

[0118] In view of the foregoing, the scope of this application is defined by the following claims.

Claims

1. A method for managing multiple links in a wireless communication network, the method comprising: generating, by a first multi-link device (MLD), a first profile for a first link, wherein the first profile comprises a plurality of parameter sets, each parameter set being assigned with a respective element identifier and comprising a respective first set of values related to operation of the first link; generating, by the first MLD, a second profile for a second link, including: omitting, in the second profile, one or more parameter sets within the plurality of parameter sets that have the same set of values as the first profile and are related to operation of the second link; and for each parameter set within the plurality of parameter sets that has a different set of values as the first profile, incorporating the respective element identifier and a respective second set of values related to operation of the second link into the second profile; and generating, by the first MLD, a link reconfiguration frame comprising the first and second profiles; and transmitting, by the first MLD, the link reconfiguration frame to a second MLD.

2. The method of claim 1, wherein, the respective second set of values overrides the respective first set of values of the respective element identifier within the second profile.

3. The method of claim 1 or 2, further comprising: incorporating, by the first MLD, within or after the first profile, a global non-inheritance element indicating a list of element identifiers that are not inherited by any subsequent profile.

4. The method of any preceding claim, further comprising: incorporating, by the first MLD, within or after the second profile, a profile-specific non-inheritance element comprising a list of element identifiers that are not inherited by the second profile from the first profile.

5. The method of claim 3, wherein, the second profile comprises a new set of values for a parameter set corresponding to the list of element identifiers, wherein the new set of values is related to operation of the second link.

6. The method of any preceding claim, wherein, the first profile comprises a complete profile subfield indicating that the first profile comprises a complete set of element identifiers whose corresponding parameter sets are related to operation of the first link.

7. The method of any preceding claim, wherein, the link reconfiguration frame comprises one or more additional profiles for one or more additional links, and wherein each profile is identified by a profile number.

8. The method of claim 7, wherein, a third profile within the one or more additional profiles comprises a reference to one or more profile numbers of at least one of the first profile, the second profile, or the one or more additional profiles, for indicating from which profile a parameter set is inherited.

9. The method of any preceding claim, wherein, the plurality of parameter sets comprises at least one parameter related to channel access, security settings, power management, or network operation.

10. The method of any preceding claim, wherein, The second MLD determines, upon receipt of the link reconfiguration frame, that an element contained in the first profile is not present in the second profile and is not listed as a non-inherited element in the second profile, the element is part of the second profile.

11. The method of any preceding claim, further comprising: determining, by the first MLD, that a size of a multi-link element exceeds a predefined threshold, wherein the multi-link element comprises the first profile and a second profile and is located within the link reconfiguration frame; responsive to the determination, fragmenting, by the first MLD, the multi-link element into a plurality of fragments, wherein each respective fragment has a size that is less than or equal to the predefined threshold; and transmitting, by the first MLD to the second MLD via the link reconfiguration frame, the plurality of fragments.

12. The method of any preceding claim, further comprising: determining, by the first MLD, that a size of a sub-element exceeds a predefined threshold, wherein the sub-element comprises the first profile or the second profile and is located within the link reconfiguration frame; responsive to the determination, fragmenting, by the first MLD, the sub-element into a plurality of fragments, wherein each respective fragment has a size that is less than or equal to the predefined threshold; and transmitting, by the first MLD to the second MLD via the link reconfiguration frame, the plurality of fragments.

13. The method of any preceding claim, wherein, The first MLD comprises a terminal MLD (STA MLD), the second MLD comprises an access point MLD (AP MLD), and the link reconfiguration frame comprises a link reconfiguration request frame.

14. The method of any one of claims 1 to 12, wherein, The first MLD comprises an access point MLD (AP MLD), the second MLD comprises a terminal MLD (STA MLD), and the link reconfiguration frame comprises a link reconfiguration response frame.

15. The method of any one of claims 1 to 12, wherein, The first MLD comprises a terminal MLD (STA MLD), the second MLD comprises an access point MLD (AP MLD), and the link reconfiguration frame comprises an association request or re-association request carrying a plurality of profiles for a plurality of links.

16. The method of any one of claims 1 to 12, wherein, The first MLD comprises an access point MLD (AP MLD), the second MLD comprises a terminal MLD (STA MLD), and the link reconfiguration frame comprises an association response or re-association response carrying a plurality of profiles for a plurality of links.

17. A system having a first multi-link device (MLD), the system comprising: one or more computer processors; and one or more memories that collectively contain one or more programs which, when executed by the one or more computer processors, perform operations comprising: generating, by the first MLD, a first profile for a first link, wherein the first profile comprises a plurality of parameter sets, each parameter set being assigned a respective element identifier and comprising a respective first set of values related to operation of the first link; generating, by the first MLD, a second profile for a second link, wherein the second profile comprises a plurality of parameter sets, each parameter set being assigned a respective element identifier and comprising a respective second set of values related to operation of the second link; generating, by the first MLD, a second profile for a second link, the generating of the second profile comprising: omitting, in the second profile, one or more of the parameter sets of the plurality of parameter sets that have the same set of values as the first profile; and for each parameter set of the plurality of parameter sets that has a different set of values than the first profile, incorporating the respective element identifier and a respective second set of values related to operation of the second link into the second profile; generating, by the first MLD, a link reconfiguration frame comprising the first profile and the second profile; and transmitting, by the first MLD, the link reconfiguration frame to a second MLD.

18. The system of claim 17, wherein, the one or more programs, when executed by the one or more computer processors, perform further operations comprising: incorporating, by the first MLD, within or after the first profile, a global non-inheritance element indicating a list of element identifiers that are not to be inherited by any subsequent profile.

19. The system of claim 17 or 18, wherein, the one or more programs, when executed by the one or more computer processors, perform further operations comprising: determining, by the first MLD, that a size of a multi-link element exceeds a predefined threshold, wherein the multi-link element comprises the first profile and the second profile and is located within the link reconfiguration frame; responsive to the determining, fragmenting, by the first MLD, the multi-link element into a plurality of fragments, wherein each respective fragment has a size that is less than or equal to the predefined threshold; and transmitting, by the first MLD, the plurality of fragments to the second MLD via the link reconfiguration frame.

20. One or more non-transitory computer-readable media containing computer program code in any combination thereof, the computer program code, when executed by a computer system, performs operations comprising: generating, by a first multi-link device (MLD), a first profile for a first link, wherein the first profile comprises a plurality of parameter sets, each parameter set being assigned a respective element identifier and comprising a respective first set of values related to operation of the first link; generating, by the first MLD, a second profile for a second link, the generating of the second profile comprising: omitting, in the second profile, one or more of the parameter sets of the plurality of parameter sets that have the same set of values as the first profile; and for each parameter set of the plurality of parameter sets that has a different set of values than the first profile, incorporating the respective element identifier and a respective second set of values related to operation of the second link into the second profile; generating, by the first MLD, a link reconfiguration frame comprising the first profile and the second profile; and transmitting, by the first MLD, the link reconfiguration frame to a second MLD.

Images