CN116801233A

CN116801233A - Associated identifier reassignment method and device and multi-link equipment

Info

Publication number: CN116801233A
Application number: CN202210250084.9A
Authority: CN
Inventors: 顾祥新
Original assignee: Spreadtrum Communications Shanghai Co Ltd
Current assignee: Spreadtrum Communications Shanghai Co Ltd
Priority date: 2022-03-14
Filing date: 2022-03-14
Publication date: 2023-09-22

Abstract

The application discloses a method and a device for reassigning associated identifiers and multi-link equipment; the method comprises the following steps: transmitting first information for reassigning an AID to a second multi-link device if the second multi-link device negotiates a or default TID-to-link mapping; the first information is received. It can be seen that after the first multilink device assigns an AID to the second multilink device, this will result in the presence of redundant invalid information for the multilink traffic elements, as the second multilink device may become negotiated or default TID to link mapping. In this regard, the embodiment of the present application introduces the first information, so that the first multilink device may redistribute the AID to the second multilink device through the first information, thereby being beneficial to avoiding the possibility that there is redundant invalid information in the multilink traffic element, and realizing the possibility of reducing the size of the multilink traffic element to avoid unnecessary signaling overhead.

Description

Associated identifier reassignment method and device and multi-link equipment

Technical Field

The present application relates to the field of communications technologies, and in particular, to a method and an apparatus for reassigning an association identifier, and a multi-link device.

Background

Institute of electrical and electronics engineers (Institute of Electrical and Electronic Engineers, IEEE) has established the IEEE 802.11be protocol standard for wireless local area networks (wireless local access network, WLAN) to introduce a multi-link (ML) mechanism. Among other things, multi-link devices (MLDs) may support data transmission over multiple links.

A multi-link device may contain multiple Access Points (APs) or one or more non-access point stations (non-AP STAs, also simply referred to as STAs or stations). If the multi-link device contains multiple access points, the multi-link device may be referred to as an access point multi-link device (AP MLD); if the multi-link device contains one or more stations, the multi-link device may be referred to as a non-access point multi-link device (non-AP MLD). Meanwhile, different access points or stations may operate on different carrier frequencies, for example, 2.4GHz, 5GHz, 6GHz, and the like.

During Association, the AP MLD will assign an Association identifier (Association Identifier, AID) to the non-AP MLD to which it is connected. However, in some specific scenarios, the AP MLD needs to reassign the AID to the non-AP MLD.

Disclosure of Invention

The application provides a method and a device for reassigning an associated identifier, and a multi-link device, wherein the method and the device are used for expecting to introduce first information and reassigning AIDs to a second multi-link device with negotiated or default TIDs-to-link mapping through the first information.

In a first aspect, the present application is a method for reassigning an association identifier, which is applied to a first multilink device, where the first multilink device assigns an association identifier AID to a second multilink device; the method comprises the following steps:

and transmitting first information, wherein the first information is used for reallocating AID to the second multi-link device if the second multi-link device negotiates or defaults a traffic identifier TID to link mapping.

It can be seen that after the first Multi-link device assigns an AID to the second Multi-link device (i.e., after association), there are many locations Per-link traffic indication bitmap (Per-Link Traffic Indication Bitmap) in the Multi-link traffic element (Multi-Link Traffic element) sent by the subsequent first Multi-link device that are invalid due to the second Multi-link device possibly initiating a TID-to-link Mapping (TID-to-link Mapping) negotiation process or a tear down process to become negotiated with TID-to-link Mapping or default TID-to-link Mapping.

In order To avoid the existence of redundant invalid information in Multi-Link Link Traffic element, the embodiment of the present application introduces first information, so that the first Multi-Link device can reallocate the AID To the second Multi-Link device negotiated with TID-To-Link Mapping or default TID-To-Link Mapping through the first information, so that the position of Per-Link Traffic Indication Bitmap in Multi-Link Traffic element is determined according To the reallocated AID, and the reallocated AID of the second Multi-Link device corresponding To Per-Link Traffic Indication Bitmap in Multi-Link Traffic element is as continuous as possible, thereby being beneficial To avoiding the possibility of existence of redundant invalid information in Multi-Link Traffic element, and reducing the size of Multi-Link Traffic element To avoid unnecessary signaling overhead.

A second aspect is a method for reassigning an association identifier of the present application, which is applied to a second multilink device, where the second multilink device is assigned an association identifier AID by a first multilink device; the method comprises the following steps:

first information is received for reassigning an AID to the second multi-link device if the second multi-link device negotiates a or default traffic identifier TID to link mapping.

In a third aspect, an apparatus for reassigning an association identifier of the present application, the apparatus assigns an association identifier AID to a second multilink device; the device comprises:

a sending unit, configured to send first information, where the first information is used to reallocate an AID to the second multi-link device if the second multi-link device negotiates a or default traffic identifier TID to link mapping.

In a fourth aspect, the present application is an association identifier reassigning apparatus, which is assigned with an association identifier AID by a first multi-link device; the device comprises:

a receiving unit, configured to receive first information, where the first information is used to reallocate an AID to the apparatus if the apparatus negotiates a or default traffic identifier TID to link mapping.

In a fifth aspect, the present application is a multi-link device, where the multi-link device is a first multi-link device, and the first multi-link device includes a processor, a memory, and a computer program or instructions stored on the memory, where the processor executes the computer program or instructions to implement the steps in the method designed in the first aspect.

In a sixth aspect, the present application is a multi-link device, where the multi-link device is a second multi-link device, and the second multi-link device includes a processor, a memory, and a computer program or instructions stored on the memory, where the processor executes the computer program or instructions to implement the steps in the method designed in the second aspect.

A seventh aspect is a chip according to the present application, comprising a processor, wherein the processor performs the steps of the method according to the first or second aspect.

An eighth aspect is a chip module according to the present application, including a transceiver component and a chip, where the chip includes a processor, and the processor executes the steps in the method designed in the first aspect or the second aspect.

A ninth aspect is a computer readable storage medium of the present application, in which a computer program or instructions are stored which, when executed, implement the steps in the method devised in the first or second aspect above.

In a tenth aspect, the present application is a computer program product comprising a computer program or instructions which, when executed, implement the steps of the method devised in the first or second aspect.

The technical effects of the third to tenth aspects may be seen in the technical effects of the first aspect, and are not described here again.

Drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present application, the following will briefly introduce the drawings that are needed in the embodiments or the description of the prior art.

Fig. 1 is a schematic diagram of a wireless communication system according to an embodiment of the present application;

fig. 2 is a schematic diagram of the structure of a multilink element according to an embodiment of the present application;

FIG. 3 is a schematic diagram of the structure of a TID to Link mapping element according to an embodiment of the present application;

FIG. 4 is a schematic diagram of the structure of a TID to Link mapping control field according to an embodiment of the present application;

fig. 5 is a schematic structural view of a TIM element according to an embodiment of the present application;

FIG. 6 is a schematic diagram of a bitmap control field according to an embodiment of the present application;

fig. 7 is a schematic diagram of a structure of a multi-link traffic element according to an embodiment of the present application;

fig. 8 is a schematic diagram of a structure of a multilink flow control field according to an embodiment of the present application;

fig. 9 is a schematic diagram of a per-link flow control indication list field according to an embodiment of the present application;

FIG. 10 is a schematic diagram of the structure of yet another TID to Link mapping element of an embodiment of the present application;

FIG. 11 is a schematic diagram of a new definition element structure according to an embodiment of the present application;

FIG. 12 is a flow chart of a method for reassigning associated identifiers in accordance with an embodiment of the present application;

FIG. 13 is a functional block diagram of a device for reassigning associated identifiers according to an embodiment of the present application;

FIG. 14 is a functional block diagram of yet another associated identifier reassignment device according to an embodiment of the present application;

fig. 15 is a schematic structural diagram of a multi-link device according to an embodiment of the present application;

fig. 16 is a schematic structural diagram of still another multi-link device according to an embodiment of the present application.

Detailed Description

In order to better understand the technical solution of the present application for those skilled in the art, the following describes the technical solution of the embodiment of the present application with reference to the accompanying drawings in the embodiment of the present application. It will be apparent that the described embodiments are some, but not all, embodiments of the application. All other embodiments, which can be made by those skilled in the art to which the application pertains without inventive faculty, are intended to fall within the scope of the application.

It should be understood that the terms "first," "second," and the like, as used in embodiments of the present application, are used for distinguishing between different objects and not for describing a particular sequential order. Furthermore, the terms "comprise" and "have," as well as any variations thereof, are intended to cover a non-exclusive inclusion. For example, a process, method, software, article, or apparatus that comprises a list of steps or elements is not limited to only those listed steps or elements but may include other steps or elements not listed or inherent to such process, method, article, or apparatus.

Reference in the specification to "an embodiment" means that a particular feature, structure, or characteristic described in connection with the embodiment may be included in at least one embodiment of the application. The appearances of such phrases in various places in the specification are not necessarily all referring to the same embodiment, nor are separate or alternative embodiments mutually exclusive of other embodiments. Those of skill in the art will explicitly and implicitly appreciate that the embodiments described herein may be combined with other embodiments.

In the embodiment of the application, "and/or" describes the association relation of the association objects, which indicates that three relations can exist, for example, a and/or B can indicate the following three cases: a is present alone, while A and B are present together, and B is present alone. Wherein A, B can be singular or plural. The symbol "/" may indicate that the context-dependent object is an "or" relationship. In addition, the symbol "/" may also denote a divisor, i.e. performing a division operation.

The expression "at least one item" or the like in the embodiments of the present application may refer to any combination of these items, including any combination of single item(s) or plural items(s), and may refer to one or more, and plural refers to two or more. For example, at least one (one) of a, b or c may represent the following seven cases: a, b, c, a and b, a and c, b and c, a, b and c. Wherein each of a, b, c may be an element or a set comprising one or more elements.

In the embodiments of the present application, "of", "corresponding", "indicated" may be used in a mixed manner. It should be noted that the meaning of what is meant is consistent when de-emphasizing the differences.

The "connection" in the embodiments of the present application refers to various connection modes such as direct connection or indirect connection, so as to implement communication between devices, which is not limited in any way.

The "network" and the "system" in the embodiments of the present application may be expressed as the same concept, and the communication system is the communication network.

The details, concepts and meanings that may be involved in the embodiments of the present application are further explained below.

1. Access point, station, multi-link device, and wireless communication system

The embodiment of the application can be applied to wireless local area networks (wireless local area network, WLAN). Currently, the protocol standard adopted by WLANs is the IEEE 802.11 family. Wherein the WLAN may comprise a plurality of basic service sets (basic service set, BSS), the devices in the basic service sets may comprise stations (access point station, AP STA, also simply referred to as AP or access point) of the access point and stations (none access point station, non-AP STA, also simply referred to as STA or station) of the non-access point, and each basic service set may comprise one access point and at least one station.

In addition, the devices in the basic service set may include multi-link devices (MLDs). The following will specifically describe each.

1) Access point

In an embodiment of the present application, an access point may be an entity that provides network access to stations connected thereto via a wireless medium. The access point may access each wireless network client to ethernet, may be a network device of a wireless fidelity (wireless fidelity, wi-Fi) chip, and may be a device supporting various IEEE 802.11 protocol standards, which is not specifically limited.

For example, the access point may be a device supporting IEEE802.11 ac, IEEE802.11 n, IEEE802.11 g, IEEE802.11b, IEEE802.11ax, IEEE802.11be, the next generation WLAN protocol standard, etc. The access points may include a centralized controller, a Base Station (BS), a base transceiver station (base transceiver station, BTS), a site controller, a switch, and the like.

In some possible implementations, the access point may include a device with wireless communication capabilities (or a device with transceiver capabilities), such as a system-on-a-chip, a chip module. The chip system may include a chip, and may further include other discrete devices, such as a transceiver device, etc.

In some possible implementations, the access point may communicate with an internet protocol (Internet Protocol, IP) network. Such as the internet, a private IP network or other data network, etc.

2) Site(s)

In the embodiment of the application, the station can be a wireless communication chip, a wireless sensor or a wireless communication terminal.

For example, a User Equipment (UE), remote/remote terminal (remote UE), access terminal, subscriber unit, subscriber station, mobile device, user terminal, smart terminal, wireless communication device, user agent or user equipment/cellular phone, cordless phone, session initiation protocol (session initiation protocol, SIP) phone, wireless local loop (wireless local loop, WLL) station, personal digital assistant (personal digital assistant, PDA), handheld device, vehicle mounted device, wearable device, etc., supporting Wi-Fi communication functions, without limitation.

In embodiments of the present application, the stations may include non-access point enhanced high throughput stations (none AP extremely high throughput station, non-AP EHT STAs), non-access point high efficiency stations (none AP high efficiency station, non-AP HE STAs), and the like.

In addition, the station may include a device having a wireless communication function (or a device having a transceiving function), such as a chip system, a chip module. The chip system may include a chip, and may further include other discrete devices, such as a transceiver device, etc.

3) Multilink device

In the embodiment of the application, the multi-link device can support data transmission on a plurality of links. A multi-link device may include multiple access points or multiple stations, and different access points or different stations may operate on different carrier frequencies, e.g., 2.4GHz, 5GHz, 6GHz, etc.

If the multi-link device contains multiple access points, the multi-link device may be referred to as an access point multi-link device (AP MLD); if the multi-link device contains one or more stations, the multi-link device may be referred to as a non-access point multi-link device (non-AP MLD).

4) Wireless communication system

A wireless communication system according to an embodiment of the present application will be described by taking a multi-link device as an example.

For an exemplary wireless communication system according to an embodiment of the present application, please refer to fig. 1. The wireless communication system 10 may include an access point multi-link device/non-access point multi-link device (AP MLD/non-AP MLD) 110 and a non-access point multi-link device (non-AP MLD) 120.

Wherein the access point multilink device/non-access point multilink device 110 may comprise a plurality of access points/stations such as AP/STA 111, AP/STA112, AP/STA 113, etc.

The non-access point multilink device 120 may contain multiple stations such as STA 121, STA 122, STA 123, etc.

Multiple links are established between the AP/non-AP device 110 and the non-AP device 120, including link 131 between AP/STA 111 and STA 121, link 132 between AP/STA112 and STA 122, and link 133 between AP/STA 113 and STA 123, with different links having different operating carrier frequencies. For example, link 131 has an operating carrier frequency of 6GHz, link 132 has an operating carrier frequency of 5GHz, and link 133 has an operating carrier frequency of 2.4GHz.

In some possible implementations, the wireless communication system 10 may also include other multi-link devices, access points, stations, etc., in addition to the access point multi-link device/non-access point multi-link device 110 and the non-access point multi-link device 120, as not specifically limited.

In some possible implementations, the wireless communication system 10 may further include an access network (radio access network, RAN) device, a Core Network (CN) device, a network controller, a mobility management entity, and other network entities, which are not particularly limited.

In some possible implementations, the communication between the access point multilink device/non-access point multilink device 110 and the non-access point multilink device 120 in the wireless communication system 10 may be wireless communication or wired communication, which is not particularly limited.

In some possible implementations, the non-access point multilink device 120 in the wireless communication system 10 may be multiple. That is, the access point multilink device/non-access point multilink device 110 may communicate with a plurality of non-access point multilink devices 120, and the number of one or more links established between the access point multilink device/non-access point multilink device 110 and different non-access point multilink devices 120 may be different, which is not particularly limited.

2. Multilink (ML), first multilink device, second multilink device

The IEEE 802.11be protocol standard introduces a multilink mechanism. Among other things, a multi-link device (MLD) may support data transmission over one or more links.

The multi-link device may be an access point multi-link device (AP MLD) or a non-access point multi-link device (non-AP MLD). For ease of distinction, the embodiments of the present application may refer to the AP MLD as a "first multi-link device" and the non-AP MLD as a "second multi-link device". Other term descriptions may be used, of course, provided that they have the same meaning/function/explanation/concept as the one claimed, and are not intended to be limiting in any way.

In the embodiment of the application, the AP MLD may include a plurality of Access Points (APs), the non-AP MLD may include one or more Stations (STAs), and different APs or STAs may operate on different carrier frequencies, for example, on carrier frequencies of 2.4GHz, 5GHz, 6GHz, etc. or on two carrier frequencies of the 5GHz band.

In embodiments of the present application, one or more links may be established between the AP MLD/non-AP MLD and the non-AP MLD, and data may be transmitted over the one or more links.

3. Multilink Element (Multi-Link Element)

In an embodiment of the present application, the association request (Association Request) frame sent by the non-AP MLD may contain multiple link elements.

Illustratively, as shown in FIG. 2, the multilink Element 20 may include an Element identifier (Element ID) field 210, a Length field 220, an Element identifier extension (Element ID Extension) field 230, a multilink Control (Multi-Link Control) field 240, a Common information (Common Info) field 250, and a Link information (Link Info) field 260. Wherein the element ID field 210 is used to indicate the ID value of the multilink element 20; the length field 220 is used to indicate the length of the multi-link element 20; the element identifier extension field 230 is used to extend the element ID field 210.

4. Traffic identifier to link mapping mechanism (Traffic ID-to-Link MappingMechanism)

Data may be transmitted on one or more links established between the AP MLD and the non-AP MLD, and which links on the one or more links the data is transmitted on may be determined by a Traffic Identifier (TID) of the data.

A TID-To-Link Mapping (TID-To-Link Mapping) mechanism may be used To determine how TID maps onto one or more links established between AP MLD and non-AP MLD.

In the case of default TID-To-Link Mapping (i.e., default Mapping mode), all TIDs should be mapped onto all links of the Downlink (DL) and Uplink (UL). When two multi-Link devices explicitly negotiate a TID-To-Link Mapping, each TID may map To the same or different Link sets.

If at least one TID maps onto a link, the link is defined as enabled (enabled); if no TID maps onto a link, the link is defined as disabled. At any point in time, the TID should always map onto at least one link unless admission control is used. By default (default mapping mode), all links should be enabled because TIDs map onto all links.

If a link is enabled, the link may be used for data transmission; if a link is disabled, the link is not available for transmission. For example, if the TID of an MSDU/A-MSDU maps onto a link, that link is enabled and the MSDU/A-MSDU may be transmitted on that link. In addition, management frames and control frames may also be transmitted over the enabled links.

A TID-To-link mapping element (TID-To-Link MappingElement) may be used To indicate on which links data corresponding (belonging, associated, or related) To a TID may be transmitted.

Illustratively, as shown in FIG. 3, the frame body of TID to link map element 30 may contain an element identifier field 310, a length field 320, an element identifier extension field 330, a TID to link map control field 340, a link map field 350 for TID 0, a link map field 360 for TID 7, and so on.

Wherein the link map field of TID n (n e 0,1, …, 7) may indicate the links that are allowed to transmit data corresponding to TID n. If the value of the ith bit of the link map field of TID n (n ε {0,1, …,7 }) is 1, then TID n is indicated to be mapped onto the link with which the link ID (link ID) is associated.

As shown in fig. 4, TID-to-link map control field 340 may contain a direction subfield 3401, a default link map subfield 3402, a reserved subfield 3403, and a link map presence indication subfield 3404. Wherein the direction subfield 3401 indicates 0 (downlink) if the TID-to-link mapping element 30 provides TID-to-link mapping information specifically for data transmitted on the downlink.

The direction subfield 3401 indicates 2 if the TID-to-link mapping element 30 provides TID-to-link mapping information specifically for data transmitted on the downlink and uplink.

If the TID To Link Mapping element 30 indicates default TID-To-Link Mapping, then the default Link Mapping subfield 3402 indicates 1; otherwise, the indication is 0.

The link map presence indication subfield 3404 may indicate whether a TID n link map field is present in the TID-to-link map element 30. If the value of the nth bit of the link map presence indication subfield 3404 is 1, a link map field indicating TID n is present in the TID-to-link map element 30; otherwise, a link map field indicating TID n is not present in TID-to-link map element 30.

5. TID-To-Link Mapping negotiation (registration) procedure

In the embodiment of the application, the non-AP MLD and the AP MLD can negotiate TID-To-Link Mapping. In combination with the content of the above "4, traffic identifier To Link Mapping mechanism", when TID-To-Link Mapping is negotiated, the transmission of data on one or more links established by non-AP MLD and AP MLD is determined by TID of the data.

The negotiation process of TID-To-Link Mapping can be realized in two ways:

Mode one: during association, the non-AP MLD sends an association request frame (Association Request frame) To the AP MLD, which Association Request frame is used To request negotiation of TID-To-Link Mapping.

Correspondingly, the AP MLD sends an association response frame (Association Responseframe) to the non-AP MLD and carries TID-to-Link Mapping Element through the Association Response frame to realize negotiation;

mode two: after association, the non-AP MLD sends a TID-To-Link Mapping request frame (TID-To-Link Mapping Request frame) To the AP MLD, which TID-To-Link Mapping Request frame is used To request negotiation of TID-To-Link Mapping.

Correspondingly, the AP MLD sends a TID-To-Link mapping response frame (TID-To-Link Mapping Response frame) To the non-AP MLD and carries the TID-To-Link Mapping Element over the TID-To-Link Mapping Response frame To effect negotiation.

6. Detachment (teardown) procedure for TID-To-Link Mapping

In the embodiment of the application, the negotiated TID-To-Link Mapping can be disassembled between the non-AP MLD and the AP MLD, so that default TID-To-Link Mapping (default TID-To-Link Mapping) is changed.

In combination with the content of the above "4, traffic identifier To Link Mapping mechanism", default TID-To-Link Mapping may be understood that the transmission of data on one or more links established by non-AP MLD and AP MLD need not be determined by the TID of the data, but may be transmitted on any Link. That is, default TID-To-Link Mapping, it is understood that TID-To-Link Mapping is not negotiated.

The disassembly process of TID-to-Link Mapping can be realized as follows: after association, the non-AP MLD sends a TID-To-Link mapping teardown frame (TID-To-Link Mapping Teardown frame) To the AP MLD To effect teardown.

In summary, after association, the non-AP MLD negotiated with TID-To-Link Mapping may become default TID-To-Link Mapping through the detach procedure of TID-To-Link Mapping.

In addition, in combination with the content in the above "negotiation process of 5, TID To Link Mapping", after association, the non-AP MLD of default TID-To-Link Mapping may be changed into non-default TID To Link Mapping (non-default TID-To-Link Mapping) through the negotiation process of TID-To-Link Mapping. The non-default TID-To-Link Mapping is understood To be negotiated with TID-To-Link Mapping.

7. Power saving Mode (Power Save Mode, PSM)

IEEE protocols established by the IEEE organization introduce a power saving mode.

For an STA configured with a power saving mode, when the STA has no data to transmit, the STA may enter a sleep (doze) state and notify the AP of the need to enter the sleep state through a power management subfield (power management subfield) in a MAC frame before entering the sleep state. Correspondingly, the AP may buffer downlink data for STAs that enter a sleep state.

For a STA entering a sleep state, the STA receives a Beacon (Beacon) frame from the sleep state to the awake (awake) state every listening period (listen interval), and detects a traffic indicator element (traffic indication map element, TIM element) in the Beacon frame to determine whether there is buffered downlink data to be received. If there is buffered downlink data to be received, the STA sends a power save poll (PS poll) frame to the AP. Correspondingly, after receiving the PS poll frame, the AP sends the buffered downlink data to the STA.

1)TIM Element

Illustratively, as shown in fig. 5, the TIM element 50 may include an element identifier (element ID) field 510, a length field 520, a commit traffic indication table count (delivery traffic indication map count, DTIM count) field 530, a DTIM period (DTIM period) field 540, a bitmap control field (bitmap control) 550, and a partial virtual bitmap (partial virtual bitmap) field 560.

Wherein the element ID field 510 is used to indicate the ID value of the TIM element 50; the length field 520 is used to indicate the length of the TIM element 50; the DTIM count field 530 is used to indicate the number of beacon frames to be transmitted before the next DTIM frame is transmitted; the DTIM period field 540 is used to indicate the period of a beacon frame between two DTIM frames; the bitmap control field 550 may be used to indicate whether there is buffered downstream data to be received; the partial virtual bitmap field 560 may be used to determine which station the buffered downstream data is to be received.

Illustratively, as shown in fig. 6, the bitmap control field 550 may contain a traffic indication (traffic indicator) 5501, a bitmap offset (bitmap offset) 5502.

It should be noted that, by using the bitmap control field 550 and the partial virtual bitmap field 560, it is possible to determine which station the buffered downlink data is to be received.

In particular implementations, bit positions in bitmap offset 5502 and partial virtual bitmap field 560 indicate the association identifier (association identifier, AID) of the station where the buffered downstream data is to be received.

In addition, the TIM Element in one beacon frame may only indicate a partially associated legacy (legacy) STA or non-AP MLD at a time.

2)AID

AID may be used to uniquely identify STA or non-AP MLD.

In the association process in which the STA establishes a link with the AP, the AP may assign an AID to the STA through an association response frame (association response frame).

Also, in the association process in which the non-AP MLD establishes a link with the AP MLD, the AP MLD may assign an AID to the non-AP MLD through an association response frame (association response frame).

3) Multilink traffic element (Multi-Link Traffic Element)

a) Definition of Multi-Link Traffic Element

Based on TIM Element, IEEE protocol formulated by IEEE organization introduced Multi-Link Traffic Element for power saving modes in a Multi-link system. Wherein Multi-Link Traffic Element may indicate that one or more links of one or more links established by the non-AP MLD and the AP MLD have buffered downlink data to be received.

b) Transmission of Multi-Link Traffic Element

In an embodiment of the application, multi-Link Traffic Element may be carried by a beacon frame to effect transmission.

After association, and in the non-AP MLD indicated by the TIM Element, if there is a non-AP MLD To which TID-To-Link Mapping is negotiated, on one or more links established between the AP MLD and the non-AP MLD, the AP MLD needs To specifically indicate To the non-AP MLD on which Link or links To receive the buffered downlink data. Therefore, the beacon frame transmitted by the AP MLD to the non-AP MLD needs to carry mult-Link Traffic Element, so as to indicate through mult-Link Traffic Element.

If there is a non-AP MLD with default TID-To-Link Mapping, on one or more links established between the AP MLD and the non-AP MLD, when the AP MLD wants To recommend a Link for transmitting downlink data To the non-AP MLD, a beacon frame sent by the AP MLD To the non-AP MLD needs To carry mult-Link Traffic Element.

If there is a non-AP MLD with default TID-To-Link Mapping, on one or more links established between the AP MLD and the non-AP MLD, the TIM Element in the beacon frame sent by the AP MLD To the non-AP MLD is used for telling whether the non-AP MLD has cached downlink data To be received. The AP MLD may not specifically indicate to the non-AP MLD on which link to receive the buffered downlink data, and may be determined by the non-AP MLD itself.

In addition, for a non-AP MLD configured with a power save mode, the non-AP MLD may receive a beacon frame on one of the one or more links established with the AP MLD and learn which link or links have buffered downlink data to receive through Multi-Link Traffic Element in the beacon frame.

For a non-AP MLD that enters a sleep state, the non-AP MLD enters an awake state from the sleep state every listening period (Listen Interval) to receive a beacon frame, and detects muli-Link Traffic Element in the beacon frame.

c) Composition of Multi-Link Traffic Element

In an embodiment of the present application, as shown in fig. 7, the Multi-link traffic element 70 may include an element identifier field 710, a length field 720, an element identifier extension field 730, a Multi-link traffic control (Multi-Link Traffic Control) field 740, and a Per-link traffic control indication list (Per-Link Traffic Indication List) field 750. Wherein the element ID field 710 is used to indicate the ID value of the multilink traffic element 70; the length field 720 is used to indicate the length of the multi-link traffic element 70; the element identifier extension field 730 is used to extend the element identifier field.

d) Composition of multilink flow control fields

As shown in fig. 8, the multi-link flow control field 740 may include a Bitmap Size (Bitmap Size) field 7401, an AID Offset (AID Offset) field 7402, and a reserved field 7403. Among other things, the AID offset field 7402 may be used to indicate the AID of the non-AP MLD.

e) Composition of per-link flow control indication list fields

As shown in fig. 9, the Per-link flow control indication list field 750 may include a Per-link flow indication bitmap 1 (Per-Link Traffic Indication Bitmap 1) field 7501, a Per-link flow indication bitmap n (Per-Link Traffic Indication Bitmap n) field 7502, and a Padding field 7503. Wherein the value of m is indicated by a bitmap size field 7401; the value of n is determined by the number of non-AP MLDs connected to the AP MLD.

Note that one non-AP MLD corresponding to one per-link traffic indication bitmap field. Or, an AID of a non-AP MLD corresponding to the per-link traffic indication bitmap field. The per-link traffic indication bitmap field may be used to indicate whether there is buffered downlink data to be transmitted on one or more links established by the corresponding non-AP MLD and the AP MLD.

f) Continuous AID

Note that in Multi-Link Traffic Element, n per-link traffic indication bitmap fields in Multi-link traffic control (Multi-Link Traffic Control) field 740 need to correspond to n consecutive AIDs in order to reduce the size of Multi-Link Traffic Element. Wherein the AID corresponding to the Per link traffic indication bitmap 1 (Per-Link Traffic Indication Bitmap 1) field 7501 is indicated by the AID offset field 7402.

For example, if the AID offset field 7402 indicates 32, the AID corresponding to the bitmap 1 field is 33 per link traffic indication, the AID corresponding to the bitmap 2 field is 33 per link traffic indication, the AID corresponding to the bitmap n field is 33+n per link traffic indication, and so on.

8. AID reassignment method

1) Multi-Link Traffic element with redundant invalid information

In combination with the above, during association, an AP MLD may assign consecutive AIDs to multiple non-AP MLDs. However, after the consecutive AIDs are assigned (i.e., after association), there may be some non-AP MLDs in the plurality of non-AP MLDs that are negotiated with TID-To-Link Mapping or default TID-To-Link Mapping.

Wherein, the non-AP MLDs negotiated with TID-To-Link Mapping may be implemented as follows: after association, the non-AP MLD initiates a negotiation process of TID-To-Link Mapping To become a non-AP MLD negotiated with TID-To-Link Mapping; alternatively, after association, the non-AP MLD of default TID-To-Link Mapping is changed To non-default TID-To-Link Mapping by carrying TID-To-Link Mapping Element via TID-To-Link Mapping Response Frame.

These non-AP MLDs of default TID-To-Link Mapping may be implemented as follows: after association, the non-AP MLD does not initiate a negotiation process of TID-To-Link Mapping To become a non-AP MLD of default TID-To-Link Mapping; alternatively, after association, the non-AP MLD negotiated with TID-To-Link Mapping is changed To default TID-To-Link Mapping by TID-To-Link Mapping Teardown Frame.

Since the AID of these non-AP MLDs may not be continuous, this will result in the situation where Per-Link Traffic Indication Bitmap, where there are many locations in Multi-Link Traffic element sent by the AP MLD, is invalid, i.e., invalid Per-Link Traffic Indication Bitmap does not have a corresponding non-AP MLD, resulting in the existence of redundant invalid information for Multi-Link Traffic element, causing unnecessary signaling overhead.

2) Exemplary description of the existence of redundant invalid information in Multi-Link Traffic element

Illustratively, during the association process, the AP MLD establishes connections with 20 non-AP MLDs and assigns AID values of 1 to 20 to these non-AP MLDs in turn. However, after association, and in the subsequent non-AP MLDs indicated by TIM Element, the non-AP MLDs corresponding To AIDs with odd values are negotiated with TID-To-Link Mapping, while the non-AP MLDs corresponding To AIDs with even values are default TID-To-Link Mapping, i.e., AID discontinuities of the non-AP MLDs with TID-To-Link Mapping are negotiated.

After association, and in the non-AP MLD indicated by TIM Element, since there is a non-AP MLD To which TID-To-Link Mapping is negotiated, the beacon frame sent by AP MLD needs To carry Multi-Link Traffic Element, while the AID Offset field in Multi-Link Traffic Element indicates 21, and the Per-Link Traffic Indication List field contains 20 Per-Link Traffic Indication Bitmap. However, among the 20 Per-Link Traffic Indication Bitmap, per-Link Traffic Indication Bitmap in the odd position is effective, and Per-Link Traffic Indication Bitmap in the even position is ineffective, resulting in the existence of redundant ineffective information of the Multi-Link Traffic element.

3) Reassigning AIDs to determine where Per-Link Traffic Indication Bitmap is located in Multi-Link Traffic element

In order To avoid the existence of redundant invalid information in Multi-Link Traffic element, after association, the embodiment of the present application may reassign the AID To the non-AP MLD negotiated with TID-To-Link Mapping or default TID-To-Link Mapping through the AP MLD, and determine the location of Per-Link Traffic Indication Bitmap in Multi-Link Traffic element according To the reassigned AID, so that the non-AP MLD reassigned AID corresponding To Per-Link Traffic Indication Bitmap in Multi-Link Traffic element is as continuous as possible, thereby advantageously avoiding the possibility of existence of redundant invalid information in Multi-Link Traffic element, and realizing reduction of the size of Multi-Link Traffic element To avoid the possibility of unnecessary signaling overhead.

That is, the embodiment of the present application can determine the position of Per-Link Traffic Indication Bitmap in Multi-Link Traffic element according to the AID reassigned by the non-AP MLD, where Per-Link Traffic Indication Bitmap corresponds to the non-AP MLD.

For example, in the above example, the AP MLD may reassign a new AID, such as an AID having a value of 21 to 30, to a non-AP MLD corresponding to an AID having an odd value. At this time, the AID Offset field indication 21 in Multi-Link Traffic Element and the Per-Link Traffic Indication List field only need to contain 10 Per-Link Traffic Indication Bitmap without invalid Per-Link Traffic Indication Bitmap, so that the size of Multi-Link Traffic element can be reduced and the signaling load of the beacon frame can be reduced.

4) First information

a) Definition of first information

In order To realize the AID reassignment, the embodiment of the application introduces the first information, so that the AP MLD can reassign the AID To the non-AP MLD negotiated with the TID-To-Link Mapping or the default TID-To-Link Mapping through the first information after the association.

That is, the first information may be used To reallocate AIDs To the non-AP MLD in the case where the non-AP MLD negotiates TID-To-Link Mapping or default TID-To-Link Mapping.

Of course, the first information may also be described by other terms, such as configuration information, indication information, first signaling, etc., as long as the same meaning/function/interpretation/concept is included in the scope of the embodiments of the present application.

b) Transmission of first information

In some possible implementations, the transmission of the first information according to the embodiments of the present application may have the following implementation manner:

mode 1:

the first information may be carried by TID-To-Link Mapping Response frame.

Wherein TID-To-Link Mapping Response frame may be used To respond To TID-To-Link Mapping Request frame and TID-To-Link Mapping Request frame To request negotiation of TID-To-Link Mapping.

It should be noted that, in combination with the content of the foregoing "negotiation process of 5, TID-To-Link Mapping", in order To implement negotiation of TID-To-Link Mapping, the non-AP MLD will send TID-To-Link Mapping Request frame To the AP MLD after association.

Correspondingly, the AP MLD sends TID-To-Link Mapping Response frame To the non-AP MLD, carries TID-To-Link Mapping Element through the TID-To-Link Mapping Response frame To realize negotiation, and carries first information through the TID-To-Link Mapping Response frame To realize AID reassignment.

It can be seen that the embodiment of the application can realize the transmission of the first information through TID-To-Link Mapping Response frame.

Mode 2:

in combination with the above "mode 1", the first information may be transmitted after the AP MLD receives TID-To-Link Mapping Request frame from the non-AP MLD.

Correspondingly, the first information may be received after the non-AP MLD transmits TID-To-Link Mapping Request frame.

Wherein the TID-To-Link Mapping Request frame is used To request negotiation of TID-To-Link Mapping.

In addition, the first information may be transmitted or received after association.

Mode 3:

in combination with the above "mode 1", the first information may be sent by the AP MLD in the negotiation process of TID-To-Link Mapping.

Correspondingly, the first information may be received by the non-AP MLD during the negotiation of TID-To-Link Mapping.

It can be appreciated that, in the TID-To-Link Mapping negotiation process, after receiving TID-To-Link Mapping Request frame, the AP MLD may carry the first information in TID-To-Link Mapping Response frame, so as To implement the AID reassignment for the non-AP MLD.

Mode 4:

the first information may be transmitted after the AP MLD receives TID-To-Link Mapping Teardown frame from the non-AP MLD.

Correspondingly, the first information may be received after the non-AP MLD transmits TID-To-Link Mapping Teardown frame.

Wherein TID-To-Link Mapping Teardown frame can be used To disassemble TID-To-Link Mapping.

In addition, in combination with the content of the above "detachment process of 6, TID-To-Link Mapping", in order To achieve detachment of TID-To-Link Mapping, the non-AP MLD will send TID-To-Link Mapping Teardown frame To the AP MLD after association.

Correspondingly, the AP MLD sends TID-To-Link Mapping Response frame To the non-AP MLD and carries the first information through the TID-To-Link Mapping Response frame To realize the reassignment of the AID.

It can be seen that the embodiment of the application can realize the transmission of the first information through the TTID-To-Link Mapping Teardown frame.

Mode 5:

in combination with the above "mode 4", the first information may be sent by the AP MLD during the disassembly of TID-To-Link Mapping.

Correspondingly, the first information may be received by the non-AP MLD during the disassembly of the TID-To-Link Mapping.

It can be appreciated that, in the process of dismounting the TID-To-Link Mapping, after receiving the TID-To-Link Mapping Teardown frame, the AP MLD may carry the first information in the TID-To-Link Mapping Response frame, so as To reassign the AID To the non-AP MLD.

Mode 6:

the first information may be carried by TID-To-Link Mapping Request frame.

Wherein TID-To-Link Mapping Request frame is used To negotiate TID-To-Link Mapping.

It should be noted that, the AP MLD may send TID-To-Link Mapping Request frame To the non-AP MLD, and carry the first information through the TID-To-Link Mapping Request frame, so as To implement negotiation To reallocate AID for the non-AP MLD.

It can be seen that the embodiment of the application can realize the transmission of the first information through TID-To-Link Mapping Request frame.

c) Type of first information

In some possible implementations, the type of the first information of the embodiment of the present application may have the following implementation manner:

Mode a:

in some possible implementations, the first information may be a new definition field in TID-To-Link Mapping Element, which may be used To indicate AID.

It will be appreciated that embodiments of the present application may newly define an optional field in TID-To-Link Mapping Element and implement reassignment of AID via that field.

For example, as shown in FIG. 10, an optional new AID field 1070 is newly defined in the TID-To-Link Mapping Element shown in FIG. 3.

Of course, the new AID field may also be described by other terms, such as a reconfiguration AID field, a reconfiguration field, etc., so long as they have the same meaning/function/interpretation/concept, etc., and are within the scope of the embodiments of the present application.

Additionally, in some possible implementations, the presence of the newly defined field is indicated by a TID-To-Link Control field in TID-To-Link Mapping Element.

It is understood that the embodiment of the present application may indicate whether the newly defined field exists through the TID-To-Link Control field.

In particular implementation, the embodiment of the application can indicate whether the newly defined field exists through a certain bit in the reserved field of the TID-To-Link Control field. Wherein the bit is 1 (0), indicating that a newly defined field exists; the bit is 0 (1), indicating that the newly defined field does not exist.

For example, in fig. 4, whether a newly defined field exists is indicated by B3 in the reserved field 3403.

In addition, in some possible implementations, the TID-To-Link Mapping Element described above may be carried by TID-To-Link Mapping Response frame.

It will be appreciated that in connection with the above description of "mode 1", after association, embodiments of the present application may carry TID-To-Link Mapping Element through TID-To-Link Mapping Response frame To effect negotiation, and carry newly defined fields through TID-To-Link Mapping Element To effect reassignment of AIDs.

In some possible implementations, the TID-To-Link Mapping Element described above may be carried by TID-To-Link Mapping Request frame.

It will be appreciated that in connection with the above "manner 6", after association, embodiments of the present application may carry the newly defined field through TID-To-Link Mapping Request frame To effect reassignment of AID.

Mode b:

in some possible implementations, the first information may be a new definition field in an Action field (Action filtered) of TID-to-link Mapping Response frame, which may be used to indicate AID.

It will be appreciated that after association, embodiments of the present application may newly define an optional field in the Action file of TID-to-link Mapping Response frame and implement reassignment of AIDs via that field.

Note that the Action file of TID-to-link Mapping Response frame may include a Category (Category) field, a Protected extremely high throughput (Extremely Hight Throughput, EHT) Action field, a Dialog Token (Dialog Token) field, a Status Code (Status Code) field, and a TID-to-link Mapping field. The TID-to-link Mapping field may include one or more TIDs-to-link Mapping Element, as shown in Table 1. Therefore, an optional field needs to be newly defined in the Action file in the embodiment of the present application.

TABLE 1

Order (Order)	Information (i.e. field)
		1	Category (Category)
2	Protected very high throughput action (Protected EHT Action)
		3	Dialog Token (Dialog Token)
4	State Code (Status Code)
		5	TID-to-link Mapping

In addition, in some possible implementations, the newly defined field may be located after the Status Code field.

For example, in table 2, the newly defined field is the New AID field. Of course, the New AID may also be described by other terms, which are not particularly limited.

In summary, in "manner b", after association, and after receiving TID-to-link Mapping Request frame, the AP MLD may carry a new definition field in TID-to-link Mapping Response frame and reassign the AID to the non-AP MLD via the new definition field.

TABLE 2

Order (Order)	Information (i.e. field)
		1	Category (Category)
2	Protected very high throughput action (Protected EHT Action)
		3	Dialog Token (Dialog Token)
4	State Code (Status Code)
		5	New association identifier (New AID) (Option)
6	TID to Link Mapping (TID-to-Link Mapping)

Mode c:

in some possible implementations, the first information may be a new definition field in the action field of TID-to-link Mapping Request frame, which may be used to indicate AID.

Note that the Action file of TID-to-link Mapping Request frame may include a Category field, a Protected extremely high throughput (Extremely Hight Throughput, EHT) Action field, a Dialog Token field, and a TID-to-link Mapping field. Wherein the TID-to-link Mapping field may include one or more TID-to-link Mapping Element, as shown in Table 3. Therefore, an optional field needs to be newly defined in the Action file in the embodiment of the present application.

TABLE 3 Table 3

Order (Order)	Information (i.e. field)
		1	Category (Category)
2	Protected very high throughput action (Protected EHT Action)
		3	Dialog Token (Dialog Token)
4	TID-to-link Mapping

Additionally, in some possible implementations, the newly defined field may be located after the Dialog Token field.

For example, in table 4, the newly defined field is the New AID field. Of course, the New AID may also be described by other terms, which are not particularly limited.

In summary, in "manner c", after association, the AP MLD may carry a new definition field in TID-to-link Mapping Request frame and reassign the AID to the non-AP MLD via the new definition field. If the Status Code field of the non-AP MLD in the replied TID-To-Link Mapping Response frame is successful (SUCCESS), it means that the non-AP MLD accepts the AP MLD To reassign the AID for it. Thus, the non-AP MLD communicates later using the reassignment AID.

TABLE 4 Table 4

Order (Order)	Information (i.e. field)
		1	Category (Category)
2	Protected very high throughput action (Protected EHT Action)
		3	Dialog Token (Dialog Token)
4	New association identifier (New AID) (Option)
		5	TID to chainRoad Mapping (TID-to-link Mapping)

Mode d:

in some possible implementations, the first information may be a new definition element, which may be used to indicate the AID.

It will be appreciated that embodiments of the present application may newly define an optional Element (Element) and implement reassignment of the AID through the Element.

For example, as shown in fig. 11, the new definition element 110 may include an element identifier field 1101, a length field 1102, an element identifier extension field 1103, and a new AID field 1104. Wherein the element identifier field 1101 is used to indicate an ID value of the newly defined element 110, and the length field 1102 is used to indicate a length of the newly defined element 110; the element identifier extension field 1103 is used to extend the element identifier field 1101, and the new AID field 1104 is used to indicate an AID to enable reassignment of the AID. Of course, the new AID field 1104 may also be described in other terms, which are not particularly limited.

Additionally, in some possible implementations, the new definition element may be located after the TID-to-link Mapping field in the Action file of TID-to-link Mapping Response frame.

For example, in Table 5, the newly defined element is the New AID field. Of course, the New AID may also be described by other terms, which are not particularly limited.

Additionally, in some possible implementations, the new definition element may be located after the TID-to-link Mapping field in the Action file of TID-to-link Mapping Request frame.

TABLE 5

Order (Order)	Information (i.e. field)
		1	Category (Category)
2	Protected very high throughput action (Protected EHT Action)
		3	Dialog Token (Dialog Token)
4	State Code (Status Code)
		5	TID to Link Mapping (TID-to-Link Mapping)
6	New association identifier (New AID)

For example, in Table 6, the New definition element is the New AID field. Of course, the New AID may also be described by other terms, which are not particularly limited.

TABLE 6

Order (Order)	Information (i.e. field)
		1	Category (Category)
2	Protected very high throughput action (Protected EHT Action)
		3	Dialog Token (Dialog Token)
4	TID to Link Mapping (TID-to-Link Mapping)
		5	New association identifier (New AID) (Option)

5) An exemplary illustration of a method for reassigning associated identifiers

In summary, an AID reassignment method according to an embodiment of the present application is described below as a communication interaction between a first multi-link device and a second multi-link device. Wherein the first multi-link device is an AP MLD and the second multi-link device is a non-AP MLD. In addition, the first multi-link device includes a chip or a chip module, and the second multi-link device includes a chip or a chip module, which is not particularly limited.

Fig. 12 is a flowchart of a method for reassigning association identifiers according to an embodiment of the present application, which specifically includes the following steps:

S1210, the first multi-link device sends first information.

The first information may be used to reallocate the AID to the second multi-link device when the second multi-link device negotiates TID-to-link Mapping or default TID-to-link Mapping.

Correspondingly, the second multilink device receives the first information.

Before the first information is sent, the first multilink device assigns an AID to the second multilink device in the association process. After association, if the second Multi-link device negotiates TID-to-link Mapping or default TID-to-link Mapping, the first Multi-link device may reallocate the AID to the second Multi-link device through the first information, thereby facilitating avoiding that Multi-Link Traffic element has redundant invalid information, and achieving the possibility of reducing the size of Multi-Link Traffic element to avoid unnecessary signaling overhead.

In addition, after reassigning the AID to the second multi-link device (i.e., after association), the second multi-link device may initiate a negotiation process or a teardown process of TID-to-link Mapping. At this time, the second multi-link device is a non-AP MLD indicated by the TIM Element and negotiated with TID-to-link Mapping or default TID-to-link Mapping.

For the first information, the content in the "4) first information" and other related content may be described in detail, which will not be described herein.

It can be seen that after the first Multi-link device assigns an AID to the second Multi-link device (i.e., after association), since the second Multi-link device may initiate a negotiation process or a disassembly process of TID-to-link Mapping to become negotiated with TID-to-link Mapping or default TID-to-link Mapping, this will result in a situation where there are many places Per-Link Traffic Indication Bitmap in the Multi-Link Traffic element sent by the subsequent first Multi-link device that are not valid.

In some possible implementations, the first information is carried by a TID-to-link mapping request frame or a TID-to-link mapping response frame.

It can be seen that after association and after receiving the TID-to-link mapping request frame, the first multi-link device may carry first information in the TID-to-link mapping response frame and reallocate the AID to the second multi-link device through the first information; or,

after association, the first multi-link device may carry first information in a TID-to-link mapping request frame and reallocate the AID to the second multi-link device with the first information.

In some possible implementations, the first information is sent after receiving a TID-to-link mapping request frame or TID-to-link mapping tear down frame from the second multi-link device.

Correspondingly, the first information is received after the second multi-link device transmits a TID-to-link mapping request frame or TID-to-link mapping tear down frame.

It can be seen that after association, the first multi-link device reassigns the AID to the second multi-link device after receiving the TID-to-link mapping request frame or TID-to-link mapping tear down frame.

In some possible implementations, the first information is sent during negotiation or teardown of the TID to link mapping.

Correspondingly, the first information is received during negotiation or teardown of the TID to link mapping.

It can be seen that the embodiment of the present application may reassign the AID to the second multilink device during negotiation or teardown of TID to link mapping.

In some possible implementations, the first information is a new definition field in the TID-to-link mapping element, the new definition field being used to indicate the AID.

It can be seen that the embodiment of the present application can implement the reassignment of the AID to the second multilink device through the newly defined field in the TID-to-link mapping element.

In some possible implementations, the presence of the newly defined field is indicated by a TID-to-link control field in the TID-to-link mapping element.

It can be seen that the embodiment of the present application can indicate whether the TID-to-link mapping element has a newly defined field through the TID-to-link control field.

In some possible implementations, the TID-to-link mapping element is carried by a TID-to-link mapping request frame or a TID-to-link mapping response frame.

It can be seen that the embodiment of the present application may implement the reassignment of the AID to the second multilink device through a TID-to-link mapping request frame or a TID-to-link mapping response frame.

In some possible implementations, the first information is a new definition field in an action field of the TID-to-link mapping response frame, the new definition field being used to indicate the AID; or,

The first information is a new definition field in an action field of the TID-to-link mapping request frame, the new definition field being used to indicate the AID.

It can be seen that the embodiment of the present application may implement the reassignment of the AID to the second multi-link device by using a newly defined field in the action field of the TID-to-link mapping response frame or TID-to-link mapping request frame.

In some possible implementations, the newly defined field is located after a state encoding field in an action field of the TID-to-link mapping response frame; or,

the newly defined field is located after the session token field in the action field of the TID-to-link mapping request frame.

In some possible implementations, the first information is a new definition element, which is used to indicate the AID.

It can be seen that the embodiment of the present application may be a new definition element, and reassign the AID to the second multilink device is implemented through the new definition element.

In some possible implementations, the new definition element is located after the TID-to-link mapping field in the action field of the TID-to-link mapping response frame; or,

the new definition element is located after the TID-to-link mapping field in the action field of the TID-to-link mapping request frame. In some possible implementations, after the first information is transmitted in S1210, the method may further include the steps of:

And the first multi-link device determines the position of each link flow indication bitmap field in the multi-link flow element according to the reassigned AID of the second multi-link device, and each link flow indication bitmap field corresponds to the second multi-link device.

It can be seen that the embodiment of the present application can determine the position of the bitmap field of the per-link traffic indication corresponding to the second multi-link device in the multi-link traffic element according to the reassigned AID.

9. Exemplary illustrations of an associated identifier reassignment apparatus

The foregoing description of the embodiments of the present application has been presented primarily from a method-side perspective. It will be appreciated that the multi-link device, in order to achieve the above-described functionality, comprises corresponding hardware structures and/or software modules that perform the respective functions. Those of skill in the art will appreciate that the application may be implemented in hardware or a combination of hardware and computer software, as a method, module, unit or algorithm steps in connection with the examples described in connection with the embodiments disclosed herein. Whether a method, function, module, unit, or step is implemented as hardware or computer software driven hardware depends upon the particular application and design constraints imposed on the solution. Those skilled in the art may implement the described methods, functions, modules, units, or steps using different methods for each particular application, but such implementation is not to be considered as outside the scope of the present application.

The embodiment of the application can divide functional units/modules of the multi-link device according to the method example. For example, each functional unit/module may be divided corresponding to each function, or two or more functions may be integrated in one functional unit/module. The integrated functional units/modules described above may be implemented in hardware or in software. It should be noted that the division of the functional units/modules in the embodiment of the present application is schematic, but only one logic function is divided, and another division manner may be implemented in practice.

In the case of an integrated unit/module, fig. 13 is a functional unit block diagram of an associated identifier reassigning device of the application embodiment. The association identifier reassignment apparatus 1300 may include: a transmitting unit 1301.

The transmitting unit 1301 may be a module unit for transmitting and receiving or processing signals, data, information, and the like.

In some possible implementations, the transmitting unit 1301 may be integrated in a processing unit or a communication unit.

The communication unit may be a communication interface, a transceiver circuit, or the like.

The processing unit may be a processor or controller, and may be, for example, a baseband processor, a baseband chip, a central processing unit (central processing unit, CPU), a general purpose processor, a digital signal processor (digital signal processor, DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (field programmable gate array, FPGA) or other programmable logic device, a transistor logic device, a hardware component, or any combination thereof. Which may implement or perform the various exemplary logical blocks, modules, and circuits described in connection with the present disclosure. The processing unit may also be a combination that implements computing functionality, e.g., comprising one or more microprocessor combinations, a combination of DSPs and microprocessors, etc.

In some possible implementations, the association identifier reassignment apparatus 1300 may further include a storage unit for storing a computer program or instructions that are executed by the association identifier reassignment apparatus 1300. The memory unit may be a memory.

In some possible implementations, the association identifier reassignment device 1300 may be a chip or a chip module.

In a specific implementation, the sending unit 1301 is configured to perform the steps described in the method embodiment above. The following is a detailed description.

A transmitting unit 1301 may be configured to transmit first information for reallocating the AID to the second multi-link device in case the second multi-link device negotiates a or default traffic identifier TID to link mapping.

It can be seen that after the association identifier reassigning apparatus 1300 assigns an AID to the second Multi-link device (i.e., after association), since the second Multi-link device may initiate a negotiation process or a disassembly process of TID-to-link Mapping to become negotiated with TID-to-link Mapping or default TID-to-link Mapping, there are many situations where Per-Link Traffic Indication Bitmap in the Multi-Link Traffic element sent by the subsequent association identifier reassigning apparatus 1300 are invalid.

In order To avoid the existence of redundant invalid information in Multi-Link Traffic element, the embodiment of the present application introduces first information, so that the associated identifier reassigning apparatus 1300 can reassign the AID To the second Multi-Link device negotiated with TID-To-Link Mapping or default TID-To-Link Mapping through the first information, so as To determine the position of Per-Link Traffic Indication Bitmap in Multi-Link Traffic element according To the reassigned AID later, so that the reassigned AID of the second Multi-Link device corresponding To Per-Link Traffic Indication Bitmap in Multi-Link Traffic element is as continuous as possible, thereby being beneficial To avoid the possibility that redundant invalid information exists in Multi-Link Traffic element, and To realize the possibility of reducing the size of Multi-Link Traffic element To avoid unnecessary signaling overhead.

It should be noted that, the specific implementation of each operation in the embodiment shown in fig. 13 may be described in detail in the above-shown method embodiment, which is not described herein.

the new definition element is located after the TID-to-link mapping field in the action field of the TID-to-link mapping request frame.

In some possible implementations, after sending the first information, the association identifier reassignment apparatus 1300 may further include:

And the determining unit is used for determining the position of each link flow indication bitmap field in the multi-link flow element according to the reassigned AID of the second multi-link device, wherein each link flow indication bitmap field corresponds to the second multi-link device.

10. Exemplary description of yet another associated identifier reassignment apparatus

In the case of an integrated unit/module, fig. 14 is a functional unit block diagram of an associated identifier reassigning device of the application embodiment. The association identifier reassignment apparatus 1400 may include: a receiving unit 1401.

The receiving unit 1401 may be a module unit for transmitting and receiving or processing signals, data, information, and the like.

In some possible implementations, the receiving unit 1401 may be integrated in a processing unit or a communication unit.

In some possible implementations, the associated identifier reassignment device 1400 may also include a memory unit for storing computer programs or instructions for execution by the associated identifier reassignment device 1400. The memory unit may be a memory.

In some possible implementations, the association identifier reassignment device 1400 may be a chip or a chip module.

In a specific implementation, the receiving unit 1401 is configured to perform the steps described in the method embodiments described above. The following is a detailed description.

The receiving unit 1401 may be configured to receive first information for reassigning an AID to the associated identifier reassignment device 1400 if the associated identifier reassignment device 1400 negotiates a or default traffic identifier TID to link mapping.

It can be seen that after the first Multi-link device assigns an AID to the association identifier reassignment apparatus 1400 (i.e., after association), since the association identifier reassignment apparatus 1400 may initiate a negotiation process or a disassembly process of TID-to-link Mapping to become negotiated with TID-to-link Mapping or default TID-to-link Mapping, this will result in a situation where there are many places Per-Link Traffic Indication Bitmap in the Multi-Link Traffic element sent by the subsequent first Multi-link device that are invalid.

In order To avoid the existence of redundant invalid information in Multi-Link Traffic element, the embodiment of the present application introduces first information, so that the first Multi-Link device can reassign the AID To the associated identifier reassigning device 1400 that negotiates with TID-To-Link Mapping or default TID-To-Link Mapping through the first information, so as To determine the position of Per-Link Traffic Indication Bitmap in Multi-Link Traffic element according To the reassigned AID later, and make the reassigned AID by the associated identifier reassigning device 1400 corresponding To Per-Link Traffic Indication Bitmap in Multi-Link Traffic element be as continuous as possible, thereby being beneficial To avoiding the possibility that redundant invalid information exists in Multi-Link Traffic element, and realizing the possibility of reducing the size of Multi-Link Traffic element To avoid unnecessary signaling overhead.

It should be noted that, the specific implementation of each operation in the embodiment shown in fig. 14 may be described in detail in the above-shown method embodiment, which is not described herein.

It can be seen that after association, and after receiving the TID-to-link mapping request frame, the first multi-link device may carry first information in the TID-to-link mapping response frame and reassign the AID to the association identifier reassignment means 1400 by the first information; or,

after association, the first multi-link device may carry first information in the TID-to-link mapping request frame and reassign the AID to the associated identifier reassignment means 1400 through the first information.

In some possible implementations, the first information is received after the association identifier reassignment device 1400 sends the TID-to-link mapping request frame or the TID-to-link mapping tear down frame.

It can be seen that after association, the first multi-link device reassigns the AID to the association identifier reassignment means 1400 after receiving the TID-to-link mapping request frame or TID-to-link mapping tear down frame.

In some possible implementations, the first information is received during negotiation or teardown of the TID to link mapping.

It can be seen that embodiments of the present application may reassign AIDs to the associated identifier reassignment device 1400 during negotiation or tear down of TID to link mappings.

It can be seen that embodiments of the present application may implement reassigning AIDs to the associated identifier reassigning device 1400 through a newly defined field in the TID-to-link mapping element.

It can be seen that embodiments of the present application may implement reassigning AIDs to the associated identifier reassigning device 1400 through TID-to-link mapping request frames or TID-to-link mapping response frames.

It can be seen that embodiments of the present application may implement reassigning AIDs to the association identifier reassigning device 1400 through a newly defined field in the action field of the TID-to-link mapping response frame or TID-to-link mapping request frame.

It can be seen that embodiments of the present application may implement reassigning AIDs to the associated identifier reassigning device 1400 with a new definition element.

In some possible implementations, the new definition element is located after the TID-to-link mapping element in the action field of the TID-to-link mapping response frame; or,

In some possible implementations, the association identifier reassignment device 1400 reassigns the AID to determine a location of a per-link traffic indication bitmap field in the multi-link traffic element, the per-link traffic indication bitmap field corresponding to the association identifier reassignment device 1400.

It can be seen that the embodiment of the present application can determine the location of the bitmap field of the traffic indication per link corresponding to the associated identifier reassignment device 1400 in the multi-link traffic element according to the reassigned AID.

11. Exemplary illustrations of multilink devices

Referring to fig. 15, fig. 15 is a schematic structural diagram of a multi-link device according to an embodiment of the present application. The multi-link device 1500 may be a first multi-link device, including a processor 1510, a memory 1520, and a communication bus for connecting the processor 1510 and the memory 1520.

Memory 1520 includes, but is not limited to, random access memory (random access memory, RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM), or portable read-only memory (compact disc read-only memory, CD-ROM), memory 1520 for storing program code and transmitted data that is executed by multi-link device 1500.

The multi-link device 1500 may also include a communication interface that may be used to receive and transmit data.

The processor 1510 may be one or more CPUs. In the case where the processor 1510 is one CPU, the CPU may be a single-core CPU or a multi-core CPU.

The processor 1510 in the multi-link device 1500 is configured to execute computer programs or instructions 1521 stored in the memory 1520 to implement the following: the first information is sent for reassigning the AID to the second multi-link device if the second multi-link device negotiates or defaults the traffic identifier TID to link mapping.

It can be seen that after the first Multi-link device assigns an AID to the second Multi-link device, since the second Multi-link device may initiate a negotiation process or a disassembly process of TID-to-link Mapping to become negotiated with TID-to-link Mapping or default TID-to-link Mapping, this will result in a situation where there are many places Per-Link Traffic Indication Bitmap in the Multi-Link Traffic element sent by the subsequent first Multi-link device that are not valid.

It should be noted that, the specific implementation of each operation may be described in the foregoing embodiments of the method, and the multi-link device 1500 may be used to perform the method on the multi-link device side of the foregoing embodiments of the method of the present application, which is not described herein in detail.

It can be seen that after association, and after receiving the TID-to-link mapping request frame, the multi-link device 1500 may carry the first information in the TID-to-link mapping response frame and reallocate the AID to the second multi-link device by the first information; or,

after association, the multi-link device 1500 may carry the first information in the TID-to-link mapping request frame and reallocate the AID to the second multi-link device with the first information.

It can be seen that after association, the multi-link device 1500 reassigns the AID to the second multi-link device after receiving the TID-to-link mapping request frame or TID-to-link mapping tear down frame.

In some possible implementations, after sending the first information, the processor 1510 in the multi-link device 1500 is further configured to execute the computer program or instructions 1521 stored in the memory 1520 to implement the following:

and determining the position of each link flow indication bitmap field in the multi-link flow element according to the reassigned AID of the second multi-link device, wherein each link flow indication bitmap field corresponds to the second multi-link device.

12. Exemplary description of yet another multilink device

Referring to fig. 16, fig. 16 is a schematic structural diagram of still another multi-link device according to an embodiment of the present application. The multi-link device 1600 may be a second multi-link device, including a processor 1610, a memory 1620, and a communication bus connecting the processor 1610 and the memory 1620.

Memory 1620 includes, but is not limited to, random access memory (random access memory, RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM), or portable read-only memory (compact disc read-only memory, CD-ROM), memory 1620 is configured to store program code and transmitted data for execution by multi-link device 1600.

The multi-link device 1600 may also include a communication interface that may be used to receive and transmit data.

Processor 1610 may be one or more CPUs. In the case where processor 1610 is a CPU, the CPU may be a single core CPU or a multi-core CPU.

The processor 1610 in the multi-link device 1600 is configured to execute the computer program or instructions 1621 stored in the memory 1620 to implement the following: the method includes receiving first information for reassigning an AID to a second multi-link device if the second multi-link device negotiates a or default traffic identifier, TID, to link mapping.

It should be noted that, the specific implementation of each operation may be described in the foregoing embodiments of the method, and the multi-link device 1600 may be used to perform the method on the multi-link device side of the foregoing embodiments of the method of the present application, which is not described herein in detail.

It can be seen that after association, and after receiving the TID-to-link mapping request frame, the first multi-link device may carry first information in the TID-to-link mapping response frame, and reallocate the AID to the multi-link device 1600 through the first information; or,

after association, the first multi-link device may carry the first information in the TID-to-link mapping request frame and reallocate the AID to the multi-link device 1600 with the first information.

In some possible implementations, the first information is received after the multi-link device 1600 transmits a TID-to-link mapping request frame or TID-to-link mapping tear down frame.

It can be seen that after association, the first multi-link device reassigns the AID to the multi-link device 1600 after receiving the TID-to-link mapping request frame or TID-to-link mapping tear down frame.

It can be seen that embodiments of the present application may reassign AIDs to multi-link device 1600 during negotiation or teardown of TID to link mappings.

It can be seen that embodiments of the present application may implement reassignment of AIDs to the multi-link device 1600 through newly defined fields in the TID-to-link mapping element.

It can be seen that embodiments of the present application may implement reallocation of AIDs to the multi-link device 1600 through TID-to-link mapping request frames or TID-to-link mapping response frames.

It can be seen that embodiments of the present application may implement reassigning AIDs to the multi-link device 1600 through a newly defined field in the action field of the TID-to-link mapping response frame or TID-to-link mapping request frame.

It can be seen that embodiments of the present application may implement a new definition element and reassign AIDs to the multi-link device 1600 through the new definition element.

In some possible implementations, the association identifier reassignment apparatus 1400 reassigns the AID to determine a location of a per-link traffic indication bitmap field in the multi-link traffic element, the per-link traffic indication bitmap field corresponding to the second multi-link device.

It can be seen that the embodiment of the present application can determine the location of the bitmap field of the per-link traffic indication corresponding to the multi-link device 1600 in the multi-link traffic element according to the reassigned AID.

13. Other exemplary description

In some possible implementations, the embodiments of the present application further provide a chip including a processor, a memory, and a computer program or instructions stored on the memory, where the processor executes the computer program or instructions to implement the steps performed by the first multi-link device or the second multi-link device described in the above method embodiments.

In some possible implementations, the embodiments of the present application further provide a chip module, including a transceiver component and a chip, where the chip includes a processor, a memory, and a computer program or instructions stored on the memory, where the processor executes the computer program or instructions to implement the steps performed by the first multi-link device or the second multi-link device described in the above method embodiments.

In some possible implementations, the embodiments of the present application further provide a computer readable storage medium storing a computer program or instructions that, when executed, implement the steps performed by the first multi-link device or the second multi-link device described in the above method embodiments.

In some possible implementations, the embodiments of the present application further provide a computer program product comprising a computer program or instructions which, when executed, implement the steps performed by the first multi-link device or the second multi-link device described in the above method embodiments.

In some possible implementations, embodiments of the present application also provide a wireless communication system including a first multi-link device or a second multi-link device.

For the above embodiments, for simplicity of description, the same is denoted as a series of combinations of actions. It will be appreciated by persons skilled in the art that the application is not limited by the order of acts described, as some steps in embodiments of the application may be performed in other orders or concurrently. In addition, those skilled in the art will appreciate that the embodiments described in the specification are presently preferred embodiments, and that the acts, steps, modules, or units, etc. that are described are not necessarily required by the embodiments of the application.

In the foregoing embodiments, the descriptions of the embodiments of the present application are emphasized, and in part, not described in detail in one embodiment, reference may be made to related descriptions of other embodiments.

The steps of a method or algorithm described in connection with the embodiments disclosed herein may be embodied in hardware, or may be embodied in software instructions executed by a processor. The software instructions may be comprised of corresponding software modules that may be stored in RAM, flash memory, ROM, erasable programmable read-only memory (erasable programmable ROM, EPROM), electrically erasable programmable read-only memory (EEPROM), registers, hard disk, a removable disk, a compact disc read-only memory (CD-ROM), or any other form of storage medium known in the art. An exemplary storage medium is coupled to the processor such the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium may be integral to the processor. The processor and the storage medium may reside in an ASIC. In addition, the ASIC may be located in a terminal device or a management device. The processor and the storage medium may reside as discrete components in a terminal device or management device.

Those skilled in the art will appreciate that in one or more of the examples described above, the functions described in the embodiments of the present application may be implemented, in whole or in part, in software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When loaded and executed on a computer, produces a flow or function in accordance with embodiments of the present application, in whole or in part. The computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable apparatus. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center by a wired (e.g., coaxial cable, fiber optic, digital subscriber line (digital subscriber line, DSL)), or wireless (e.g., infrared, wireless, microwave, etc.). The computer readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. that contains an integration of one or more available media. The usable medium may be a magnetic medium (e.g., a floppy disk, a hard disk, a magnetic tape), an optical medium (e.g., a digital video disc (digital video disc, DVD)), or a semiconductor medium (e.g., a Solid State Disk (SSD)), or the like.

The respective apparatuses and the respective modules/units included in the products described in the above embodiments may be software modules/units, may be hardware modules/units, or may be partly software modules/units, and partly hardware modules/units. For example, for each device or product applied to or integrated on a chip, each module/unit included in the device or product may be implemented in hardware such as a circuit, or at least part of the modules/units may be implemented in software program, where the software program runs on a processor integrated inside the chip, and the rest (if any) of the modules/units may be implemented in hardware such as a circuit; for each device and product applied to or integrated in the chip module, each module/unit contained in the device and product can be realized in a hardware manner such as a circuit, different modules/units can be located in the same component (such as a chip, a circuit module and the like) or different components of the chip module, or at least part of the modules/units can be realized in a software program, the software program runs on a processor integrated in the chip module, and the rest (if any) of the modules/units can be realized in a hardware manner such as a circuit; for each device, product, or application to or integrated with the terminal device, each module/unit included in the device may be implemented in hardware such as a circuit, and different modules/units may be located in the same component (e.g., a chip, a circuit module, etc.) or different components in the terminal device, or at least some modules/units may be implemented in a software program, where the software program runs on a processor integrated within the terminal device, and the remaining (if any) part of the modules/units may be implemented in hardware such as a circuit.

The foregoing detailed description of the embodiments of the present application further illustrates the purposes, technical solutions and advantageous effects of the embodiments of the present application, and it should be understood that the foregoing description is only a specific implementation of the embodiments of the present application, and is not intended to limit the scope of the embodiments of the present application, and any modifications, equivalent substitutions, improvements, etc. made on the basis of the technical solutions of the embodiments of the present application should be included in the scope of the embodiments of the present application.

Claims

1. The method for reassigning the association identifier is characterized by being applied to a first multi-link device, wherein the first multi-link device assigns an association identifier AID for a second multi-link device; the method comprises the following steps:

2. The method of claim 1, wherein the first information is carried by a TID-to-link mapping request frame or a TID-to-link mapping response frame.

3. The method of claim 1, wherein the first information is sent after receiving a TID-to-link mapping request frame or a TID-to-link mapping tear down frame from the second multi-link device.

4. The method of claim 1, wherein the first information is sent during negotiation or teardown of TID-to-link mapping.

5. The method of claim 1, wherein the first information is a newly defined field in a TID-to-link mapping element, the newly defined field being used to indicate an AID.

6. The method of claim 5, wherein the presence of the newly defined field is indicated by a TID-to-link control field in the TID-to-link mapping element.

7. The method of claim 5 or 6, wherein the TID-to-link mapping element is carried by a TID-to-link mapping request frame or a TID-to-link mapping response frame.

8. The method of claim 1, wherein the first information is a newly defined field in an action field of a TID-to-link mapping response frame, the newly defined field being used to indicate an AID; or,

the first information is a new definition field in an action field of a TID-to-link mapping request frame, wherein the new definition field is used for indicating an AID.

9. The method of claim 8, wherein the newly defined field is located after a state encoding field in an action field of the TID-to-link mapping response frame; or,

The newly defined field is located after a session token field in an action field of the TID-to-link mapping request frame.

10. The method of claim 1, wherein the first information is a New definition element, and the New definition element is used to indicate AID.

11. The method of claim 10, wherein the new definition element is located after a TID-to-link mapping field in an action field of the TID-to-link mapping response frame; or,

the new definition element is located after a TID-to-link mapping field in an action field of the TID-to-link mapping request frame.

12. The method according to any of claims 1-11, wherein after said transmitting the first information, the method further comprises:

and determining the position of each link flow indication bitmap field in the multi-link flow element according to the reassigned AID of the second multi-link device, wherein the each link flow indication bitmap field corresponds to the second multi-link device.

13. An associated identifier reassignment method is characterized by being applied to a second multi-link device, wherein the second multi-link device is assigned with an associated identifier AID by a first multi-link device; the method comprises the following steps:

14. The method of claim 13, wherein the first information is carried by a TID-to-link mapping request frame or a TID-to-link mapping response frame.

15. The method of claim 13, wherein the first information is received after the second multi-link device transmits a TID-to-link mapping request frame or a TID-to-link mapping tear down frame.

16. The method of claim 13, wherein the first information is received during negotiation or teardown of TID-to-link mapping.

17. The method of claim 13, wherein the first information is a newly defined field in a TID-to-link mapping element, the newly defined field being used to indicate an AID.

18. The method of claim 17, wherein the presence of the newly defined field is indicated by a TID-to-link control field in the TID-to-link mapping element.

19. The method of claim 17 or 18, wherein the TID-to-link mapping element is carried by a TID-to-link mapping request frame or a TID-to-link mapping response frame.

20. The method of claim 13, wherein the first information is a newly defined field in an action field of a TID-to-link mapping response frame, the newly defined field being used to indicate an AID; or,

21. The method of claim 20, wherein the newly defined field is located after a state encoding field in an action field of the TID-to-link mapping response frame; or,

22. The method of claim 13, wherein the first information is a new definition element, the new definition element being used to indicate an AID.

23. The method of claim 22, wherein the newly defined element is located after a TID-to-link mapping element in an action field of the TID-to-link mapping response frame; or,

24. The method according to any of claims 13-23, wherein the second multi-link device reallocates AID to determine a location of a per-link traffic indication bitmap field in a multi-link traffic element, the per-link traffic indication bitmap field corresponding to the second multi-link device.

25. An association identifier reassignment apparatus, characterized in that the apparatus assigns an association identifier AID to a second multilink device; the device comprises:

26. An associated identifier reassignment apparatus, characterized in that the apparatus is assigned an associated identifier AID by a first multilink device; the device comprises:

27. A multi-link device being a first multi-link device comprising a processor, a memory and a computer program or instructions stored on the memory, characterized in that the processor executes the computer program or instructions to implement the steps of the method of any of claims 1-12.

28. A multilink device which is a second multilink device, the first multilink device comprising a processor, a memory and a computer program or instructions stored on the memory, wherein the processor executes the computer program or instructions to carry out the steps of the method of any of claims 13 to 24.

29. A chip comprising a processor, wherein the processor performs the steps of the method of any one of claims 1-12 or 13-24.

30. A computer readable storage medium, characterized in that it stores a computer program or instructions which, when executed, implement the steps of the method of any one of claims 1-12 or 13-24.