Communication method, access point equipment and communication system

Abstract

The embodiment of the invention relates to a communication method, access point equipment and a communication system. The communication method is applied to a shared access point (AP) device, and comprises the following steps: after a transmission opportunity (TXOP) is obtained, determining a first wireless frame; the first wireless frame identifier sharing AP shares a transmission duration with a shared device according to the TXOP; wherein the first wireless frame comprises first identification information; the first identification information comprises identification information of the shared device; the shared equipment comprises a shared AP (Access Point); sending the first wireless frame, and indicating the shared device to perform data interaction with the shared AP or an STA associated with the shared device within the transmission duration; in the C-TDMA process, the transmission duration is allocated to the shared AP supporting the TXS between the APs in the neighbor APs through the Sharing AP.

Description

Communication method, access point device and communication system Technical Field

[0001] The present disclosure relates to the field of communication technology, and in particular to a communication method, an access point device, and a communication system. Background Art

[0002] With the continuous development of Wi-Fi technology, the next generation of Wi-Fi technology has been proposed: Ultra High Reliability (UHR). In UHR technology, access points (APs) can share transmission opportunity (TXOP) transmission time with other STAs (STAs). After other STAs obtain the transmission time, they can further share it with associated STAs or APs, facilitating non-triggered frame-based (Non-TB) data transmission or peer-to-peer (P2P) data transmission.

[0003] Therefore, a TXOP processing method needs to be provided to improve the TXOP sharing mechanism and support UHR.

[0004] Summary of the Invention

[0005] The embodiments of the present disclosure provide a communication method, an access point device, and a communication system to provide a further enhanced power saving mechanism.

[0006] In a first aspect, an embodiment of the present disclosure provides a communication method for sharing an access point device (AP), including:

[0007] After obtaining a transmission opportunity TXOP, a first radio frame is determined; the first radio frame identifies the transmission duration shared by the sharing AP with the shared device according to the TXOP;

[0008] The first wireless frame includes first identification information; the first identification information includes identification information of the shared device; the shared device includes a shared AP;

[0009] The first wireless frame is sent to instruct the shared device to perform data interaction with the sharing AP or the STA associated with the shared device within the transmission duration.

[0010] In a second aspect, an embodiment of the present disclosure provides a communication method, which is applied to a first AP, including:

[0011] Receive a first wireless frame; the first wireless frame indicates that the sharing AP shares the transmission duration with the shared device according to the obtained TXOP;

[0012] The first wireless frame includes first identification information; the first identification information includes identification information of the shared device; the shared device includes a shared AP;

[0013] Determine that the first identification information includes identification information of the first AP, and perform data interaction with the shared AP or a STA associated with the first AP within the transmission duration.

[0014] In a third aspect, an embodiment of the present disclosure further provides an access point device, wherein the access point device is a shared access point device, and the shared access point device includes:

[0015] A determination module is configured to determine a first radio frame after obtaining a transmission opportunity TXOP; the first radio frame identifies a transmission duration shared by the sharing AP to the shared device according to the TXOP;

[0016] The first wireless frame includes first identification information; the first identification information includes identification information of the shared device; the shared device includes a shared AP;

[0017] The sending module is configured to send the first wireless frame to instruct the shared device to perform data interaction with the sharing AP or the STA associated with the shared device within the transmission duration.

[0018] In a fourth aspect, an embodiment of the present disclosure further provides an access point device, wherein the access point device is a first AP, and the first AP includes:

[0019] A receiving module, configured to receive a first wireless frame; the first wireless frame identifies the transmission duration shared by the sharing AP to the shared device according to the obtained TXOP;

[0020] The first wireless frame includes first identification information; the first identification information includes identification information of the shared device; the shared device includes a shared AP;

[0021] A processing module is used to determine that the first identification information includes the identification information of the first AP, and to interact with the shared AP or the STA associated with the first AP within the transmission duration.

[0022] In a fifth aspect, an embodiment of the present disclosure further provides an access point device, including:

[0023] one or more processors;

[0024] The access point device is used to execute the communication method described in the first aspect or the communication method described in the second aspect of the embodiment of the present disclosure.

[0025] The present disclosure also provides a communication system, including a shared access point device and a first access point device; wherein the shared access point device is configured to implement the communication method described in the first aspect of the present disclosure, and the first access point device is configured to implement the communication method described in the second aspect of the present disclosure.

[0026] An embodiment of the present disclosure also provides a storage medium storing instructions. When the instructions are executed on a communication device, the communication device executes the communication method as described in the first aspect of the embodiment of the present disclosure, or executes the communication method as described in the second aspect of the embodiment of the present disclosure.

[0027] In the embodiment of the present disclosure, after obtaining the transmission opportunity TXOP, the sharing AP determines the first wireless frame; the sharing AP shares the transmission duration with the shared device according to the TXOP through the first wireless frame identification; and the first wireless frame includes first identification information, and the first identification information includes identification information of the shared device; the shared device includes the shared AP; and the first wireless frame is sent to the shared device, instructing the shared device to interact with the sharing AP or the STA associated with the shared device within the transmission duration; in this way, in the C-TDMA process, the transmission duration is allocated to the shared AP that supports TXS between APs among its neighboring APs through the Sharing AP.

[0028] Additional aspects and advantages of the embodiments of the present disclosure will be given in part in the following description, which will become apparent from the following description or be learned through practice of the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0029] In order to more clearly illustrate the technical solutions in the embodiments of the present disclosure, the following drawings required for describing the embodiments are introduced. The following drawings are merely some embodiments of the present disclosure and do not impose specific limitations on the protection scope of the present disclosure.

[0030] FIG1 is an exemplary schematic diagram of the architecture of a communication system provided according to an embodiment of the present disclosure;

[0031] FIG2 is an exemplary interaction diagram of a communication method provided according to an embodiment of the present disclosure;

[0032] FIG3 is a schematic diagram of a scenario of a communication method provided according to an embodiment of the present disclosure;

[0033] FIG4 is a flow chart of a communication method according to an embodiment of the present disclosure;

[0034] FIG5 is a second flow chart of a communication method according to an embodiment of the present disclosure;

[0035] FIG6 is a schematic structural diagram of a shared access point device proposed in an embodiment of the present disclosure;

[0036] FIG7 is a schematic structural diagram of a shared access point device proposed in an embodiment of the present disclosure;

[0037] FIG8 is a schematic diagram of the structure of a terminal proposed in an embodiment of the present disclosure;

[0038] FIG9 is a schematic diagram of the structure of a chip proposed in an embodiment of the present disclosure. DETAILED DESCRIPTION

[0039] The embodiments of the present disclosure provide a communication method, an access point device, and a communication system.

[0040] In a first aspect, an embodiment of the present disclosure provides a communication method for sharing an access point device (AP), including:

[0041] After obtaining a transmission opportunity TXOP, a first radio frame is determined; the first radio frame identifies the transmission duration shared by the sharing AP with the shared device according to the TXOP;

[0042] The first wireless frame includes first identification information; the first identification information includes identification information of the shared device; the shared device includes a shared AP;

[0043] The first wireless frame is sent to instruct the shared device to perform data interaction with the sharing AP or the STA associated with the shared device within the transmission duration.

[0044] In the above embodiment, after obtaining the transmission opportunity TXOP, the sharing AP determines the first wireless frame; the sharing AP shares the transmission duration with the shared device according to the TXOP through the first wireless frame identification; and the first wireless frame includes first identification information, and the first identification information includes identification information of the shared device; the shared device includes the shared AP; and the first wireless frame is sent to the shared device, instructing the shared device to interact with the sharing AP or the STA associated with the shared device within the transmission duration; in this way, in the C-TDMA process, the transmission duration is allocated to the shared AP that supports TXS between APs among its neighboring APs through the Sharing AP.

[0045] In combination with some embodiments of the first aspect, in some embodiments, the first identification information is carried in a user information field User Info field of the first radio frame;

[0046] The User Info field includes an AP MLD ID subfield and a Link ID subfield, and the first identification information identifies the identification information of the shared AP; the AP MLD ID subfield identifies the identification AP MLD ID of the multi-connection access point device to which the shared AP is attached, and the Link ID subfield identifies the link identification Link ID of the shared AP working link.

[0047] In the above embodiment, the first identification information is carried by the User Info field of the first wireless frame, and the User Info field is set to include an AP MLD ID subfield and a Link ID subfield. The AP MLD ID subfield identifies the AP MLD ID of the multi-connection access point device to which the shared AP is attached, and the Link ID subfield identifies the link ID Link ID of the working link of the shared AP. When indicating the identification information of the shared AP, it can be achieved in the C-TDMA process that the transmission time is allocated to the target shared AP among its neighboring APs that supports TXS between APs by the shared AP.

[0048] In conjunction with some embodiments of the first aspect, in some embodiments, the first radio frame further includes second identification information;

[0049] The second identification information identifies: the type of TXS shared by the TXOP initiated by the sharing AP, and the type of the TXS includes allocating the transmission duration to the shared AP.

[0050] In the above embodiment, the type of TXOP shared TXS initiated by the sharing AP is identified by the second identification information in the first wireless frame, and the type of the TXS includes allocating the transmission time to the shared AP; in this way, the device that obtains the first wireless frame can obtain the type of TXOP shared TXS initiated by the sharing AP by parsing the first wireless frame.

[0051] In combination with some embodiments of the first aspect, in some embodiments, the second identification information is carried in a Triggered TXOP Sharing Mode subfield of the first radio frame;

[0052] The Triggered TXOP Sharing Mode subfield is carried in the Common Info field of the first radio frame;

[0053] The Triggered TXOP Sharing Mode subfield is set to a first parameter value, indicating that the sharing AP allocates the transmission duration to the shared AP.

[0054] In the above embodiment, the first wireless frame includes a Common Info field, and the Common Info field includes a Triggered TXOP Sharing Mode subfield. When the Triggered TXOP Sharing Mode subfield is set to a first parameter value, it is indicated that the sharing AP allocates the transmission time to the shared AP. In this way, the device that obtains the first wireless frame can obtain the transmission time allocated by the sharing AP to the shared AP by parsing the parameter value of the Triggered TXOP Sharing Mode subfield in the first wireless frame.

[0055] In conjunction with some embodiments of the first aspect, in some embodiments, the method further includes:

[0056] Determine a second wireless frame; wherein the second wireless frame includes third identification information; the third identification information identifies: whether the neighbor AP of the shared AP supports inter-AP TXS;

[0057] The second radio frame is sent.

[0058] In the above embodiment, the shared AP determines and sends a second wireless frame, and uses the third identification information in the second wireless frame to identify whether the neighbor AP of the shared AP supports inter-AP TXS; in this way, the device receiving the second wireless frame can determine whether the neighbor AP of the shared AP supports inter-AP TXS.

[0059] In combination with some embodiments of the first aspect, in some embodiments, the third identification information is carried in a first triggered transmission opportunity sharing mode 3 support Triggered TXOP Sharing Mode 3 Support flag bit of the second radio frame;

[0060] The first Triggered TXOP Sharing Mode 3 Support flag is carried in the Reduced Neighbor Report element field;

[0061] The first Triggered TXOP Sharing Mode 3 Support flag is set to a third parameter value, indicating that the neighbor AP supports inter-AP TXS.

[0062] In the above embodiment, the second radio frame includes the Reduced Neighbor Report element field, carries the MLD Parameters subfield in the Reduced Neighbor Report element field, and sets the first Triggered TXOP Sharing Mode 3 Support flag in the MLD Parameters subfield to the third parameter value, thereby indicating that the neighbor AP supports inter-AP TXS; otherwise, it indicates that the neighbor AP does not support inter-AP TXS; in this way, the device that obtains the second radio frame can parse the first Triggered TXOP Sharing Mode 3 Support flag in the MLD Parameters subfield to determine whether the neighbor AP supports inter-AP TXS, and when the first Triggered TXOP Sharing Mode 3 Support flag is set to the third parameter value, it is determined that the neighbor AP supports inter-AP TXS.

[0063] In combination with some embodiments of the first aspect, in some embodiments, the second wireless frame further includes fourth identification information; the fourth identification information identifies whether the shared AP supports inter-AP TXS.

[0064] In the above embodiment, the fourth identification information in the second wireless frame indicates whether the shared AP supports inter-AP TXS. In this way, the device receiving the second wireless frame can determine whether the shared AP supports TXS.

[0065] In combination with some embodiments of the first aspect, in some embodiments, the fourth identification information is carried in a second Triggered TXOP Sharing Mode 3 Support flag of the second radio frame;

[0066] The second Triggered TXOP Sharing Mode 3 Support flag is carried in an ultra high reliability capabilities element UHR Capabilities element field of the second radio frame;

[0067] The second Triggered TXOP Sharing Mode 3 Support flag is set to a fourth parameter value, indicating that the shared AP supports inter-AP TXS.

[0068] In the above embodiment, the device that receives the second wireless frame can parse the second wireless frame to obtain the UHR Capabilities element field, and parse the UHR Capabilities element to obtain the second Triggered TXOP Sharing Mode 3 Support flag, and then determine whether the shared AP supports inter-AP TXS based on the parameter value of the second Triggered TXOP Sharing Mode 3 Support flag, and when the second Triggered TXOP Sharing Mode 3 Support flag is set to the fourth parameter value, determine that the shared AP supports inter-AP TXS.

[0069] In combination with some embodiments of the first aspect, in some embodiments, the User Info field further includes: at least one of: an allocation duration subfield, a resource unit allocation RU Allocation subfield, and a master-slave 160PS160 subfield.

[0070] In the above embodiment, the User Info field of the first wireless frame carries the Allocation Duration subfield, the RU Allocation subfield, and the PS160 subfield; in this way, the device receiving the first wireless frame can obtain the transmission resources allocated by the sharing AP to the shared device by parsing the first wireless frame, and then, when the device receiving the first wireless frame is the shared device, perform data interaction based on the transmission resources; when the device receiving the first wireless frame is not the shared device, avoid data interaction within the transmission resource, and avoid interfering with the process of data interaction of the shared device based on the transmission resource.

[0071] In conjunction with some embodiments of the first aspect, in some embodiments, the shared device interacts with the sharing AP or the STA associated with the shared device during the transmission duration, including:

[0072] The shared device exchanges data with the sharing AP or the STA associated with the shared device within the transmission duration according to the transmission resources indicated by at least one of the Allocation Duration subfield, the RU Allocation subfield, and the PS160 subfield.

[0073] In the above embodiment, the shared AP interacts with the sharing AP or the STA associated with the shared AP within the transmission duration based on the transmission resources indicated by at least one of the Allocation Duration subfield, the RU Allocation subfield and the PS160 subfield indicated by the first wireless frame, thereby saving signaling overhead and avoiding contention conflicts and transmission interference in the OBSS scenario.

[0074] In a second aspect, an embodiment of the present disclosure provides a communication method, which is applied to a first AP, including:

[0075] Receive a first wireless frame; the first wireless frame indicates that the sharing AP shares the transmission duration with the shared device according to the obtained TXOP;

[0076] The first wireless frame includes first identification information; the first identification information includes identification information of the shared device; the shared device includes a shared AP;

[0077] Determine that the first identification information includes identification information of the first AP, and perform data interaction with the shared AP or a STA associated with the first AP within the transmission duration.

[0078] In combination with some embodiments of the second aspect, in some embodiments, the first identification information is carried in a User Info field of the first radio frame;

[0079] The User Info field includes an AP MLD ID subfield and a Link ID subfield, wherein the first identification information identifies the identification information of the shared AP; wherein the AP MLD ID subfield identifies the AP MLD ID of the multi-connection access point device to which the shared AP is attached, and the Link ID subfield identifies the link identifier Link ID of the working link of the shared AP;

[0080] The User Info field includes an AID12 subfield, and the first identification information identifies identification information of the shared STA.

[0081] In conjunction with some embodiments of the second aspect, in some embodiments, determining that the first identification information includes identification information of the first AP includes:

[0082] In the case where the User Info field includes the AP MLD ID subfield and the Link ID subfield,

[0083] Determine that the AP MLD ID subfield matches the identifier of the multi-connection access point device to which the first AP is attached, and the Link ID subfield matches the link identifier of the first AP working link, and determine that the first identification information includes identification information of the first AP.

[0084] In combination with some embodiments of the second aspect, in some embodiments, the User Info field further includes: at least one of: an Allocation Duration subfield, an RU Allocation subfield, and a PS160 subfield.

[0085] In conjunction with some embodiments of the second aspect, in some embodiments, the data interaction with the shared AP or the STA associated with the first AP within the transmission duration includes:

[0086] According to the transmission resources indicated by at least one of the Allocation Duration subfield, the RU Allocation subfield, and the PS160 subfield, data interaction is performed with the shared AP or the STA associated with the first AP within the transmission duration.

[0087] In a third aspect, an embodiment of the present disclosure further provides an access point device, wherein the access point device is a shared access point device, and the shared access point device includes:

[0088] A determination module is configured to determine a first radio frame after obtaining a transmission opportunity TXOP; the first radio frame identifies a transmission duration shared by the sharing AP to the shared device according to the TXOP;

[0089] The first wireless frame includes first identification information; the first identification information includes identification information of the shared device; the shared device includes a shared AP;

[0090] The sending module is configured to send the first wireless frame to instruct the shared device to perform data interaction with the sharing AP or the STA associated with the shared device within the transmission duration.

[0091] In a fourth aspect, an embodiment of the present disclosure further provides an access point device, wherein the access point device is a first AP, and the first AP includes:

[0092] A receiving module, configured to receive a first wireless frame; the first wireless frame identifies the transmission duration shared by the sharing AP to the shared device according to the obtained TXOP;

[0093] The first wireless frame includes first identification information; the first identification information includes identification information of the shared device; the shared device includes a shared AP;

[0094] A processing module is used to determine that the first identification information includes the identification information of the first AP, and to interact with the shared AP or the STA associated with the first AP within the transmission duration.

[0095] In a fifth aspect, an embodiment of the present disclosure further provides an access point device, including:

[0096] one or more processors;

[0097] The access point device is used to perform an optional implementation of the first aspect or the second aspect.

[0098] In a sixth aspect, an embodiment of the present disclosure further provides a communication system, comprising a shared access point device and a first access point device; wherein the shared access point device is configured to perform the optional implementation method described in the first aspect, and the first access point device is configured to perform the optional implementation method described in the second aspect.

[0099] In a seventh aspect, an embodiment of the present disclosure further provides a storage medium storing instructions, which, when executed on a communication device, enables the communication device to execute an optional implementation as described in the first aspect or the second aspect.

[0100] In an eighth aspect, an embodiment of the present disclosure proposes a program product. When the program product is executed by a communication device, the communication device executes the method described in the optional implementation manner of the first aspect or the second aspect.

[0101] In a ninth aspect, an embodiment of the present disclosure proposes a computer program, which, when executed on a computer, enables the computer to execute the method described in the optional implementation of the first or second aspect.

[0102] In a tenth aspect, an embodiment of the present disclosure provides a chip or a chip system, wherein the chip or chip system includes a processing circuit configured to execute the method described in the optional implementation of the first or second aspect.

[0103] It is understandable that the aforementioned access point devices, communication systems, storage media, program products, computer programs, chips, or chip systems are all used to perform the methods proposed in the embodiments of the present disclosure. Therefore, the beneficial effects that can be achieved can refer to the beneficial effects of the corresponding methods and will not be repeated here.

[0104] The embodiments of the present disclosure provide a communication method, an access point device, and a communication system. In some embodiments, the terms communication method, signal transmission method, wireless frame transmission method, etc. can be used interchangeably, and the terms information processing system, communication system, etc. can be used interchangeably.

[0105] The embodiments of the present disclosure are not exhaustive and are merely illustrative of some embodiments, and are not intended to be a specific limitation on the scope of protection of the present disclosure. In the absence of contradiction, each step in a certain embodiment can be implemented as an independent embodiment, and the steps can be arbitrarily combined. For example, a solution after removing some steps in a certain embodiment can also be implemented as an independent embodiment, and the order of the steps in a certain embodiment can be arbitrarily exchanged. In addition, the optional implementation methods in a certain embodiment can be arbitrarily combined; in addition, the embodiments can be arbitrarily combined. For example, some or all steps of different embodiments can be arbitrarily combined, and a certain embodiment can be arbitrarily combined with the optional implementation methods of other embodiments.

[0106] In each embodiment of the present disclosure, unless otherwise specified or provided for by logic, the terms and / or descriptions between the embodiments are consistent and can be referenced by each other. The technical features in different embodiments can be combined to form a new embodiment based on their inherent logical relationships.

[0107] The terms used in the embodiments of the present disclosure are only for the purpose of describing specific embodiments and are not intended to limit the present disclosure.

[0108] In the embodiments of the present disclosure, “plurality” refers to two or more.

[0109] In some embodiments, the terms "at least one," "one or more," "a plurality of," "multiple," and the like can be used interchangeably.

[0110] In some embodiments, descriptions such as "at least one of A and B," "A and / or B," "A in one case, B in another case," or "in response to one case A, in response to another case B" may include the following technical solutions depending on the situation: in some embodiments, A (A is executed independently of B); in some embodiments, B (B is executed independently of A); in some embodiments, execution is selected from A and B (A and B are selectively executed); and in some embodiments, A and B (both A and B are executed). The above is also applicable when there are more branches such as A, B, and C.

[0111] In some embodiments, "A or B" and other descriptions may include the following technical solutions depending on the situation: in some embodiments, A (A is executed independently of B); in some embodiments, B (B is executed independently of A); in some embodiments, execution is selected from A and B (A and B are selectively executed). The above is also applicable when there are more branches such as A, B, C, etc.

[0112] The prefixes such as "first" and "second" in the embodiments of the present disclosure are only used to distinguish different description objects and do not constitute any restriction on the position, order, priority, quantity or content of the description objects. For the statement of the description object, please refer to the description in the context of the claims or embodiments, and no unnecessary restriction should be constituted due to the use of prefixes. For example, if the description object is a "field", the ordinal number before the "field" in the "first field" and the "second field" does not limit the position or order between the "fields". "First" and "second" do not limit whether the "fields" they modify are in the same message, nor do they limit the order of the "first field" and the "second field". For another example, if the description object is a "level", the ordinal number before the "level" in the "first level" and the "second level" does not limit the priority between the "levels". For another example, the number of description objects is not limited by the ordinal number and can be one or more. Taking "first device" as an example, the number of "devices" can be one or more. In addition, the objects modified by different prefixes can be the same or different. For example, if the description object is "device", then the "first device" and the "second device" can be the same device or different devices, and their types can be the same or different; for another example, if the description object is "information", then the "first information" and the "second information" can be the same information or different information, and their contents can be the same or different.

[0113] In some embodiments, “including A,” “comprising A,” “used to indicate A,” and “carrying A” can be interpreted as directly carrying A or indirectly indicating A.

[0114] In some embodiments, terms such as "in response to...", "in response to determining...", "in the case of...", "at the time of...", "when...", "if...", "if...", etc. can be used interchangeably.

[0115] In some embodiments, terms such as "greater than", "greater than or equal to", "not less than", "more than", "more than or equal to", "not less than", "higher than", "higher than or equal to", "not less than", "above" can be replaced with each other, and terms such as "less than", "less than or equal to", "not greater than", "less than", "less than or equal to", "not more than", "lower than", "lower than or equal to", "not higher than", and "below" can be replaced with each other.

[0116] In some embodiments, devices and equipment can be interpreted as physical or virtual, and their names are not limited to the names recorded in the embodiments. In some cases, they can also be understood as "equipment", "device", "circuit", "network element", "node", "function", "unit", "section", "system", "network", "chip", "chip system", "entity", "subject", etc.

[0117] In some embodiments, "network" can be interpreted as devices included in the network, such as access network equipment, core network equipment, etc.

[0118] In some embodiments, obtaining data, information, etc. may comply with the laws and regulations of the country where the data is obtained.

[0119] In some embodiments, data, information, etc. may be obtained with the user's consent.

[0120] In addition, each element, each row, or each column in the table of the embodiment of the present disclosure can be implemented as an independent embodiment, and the combination of any elements, any rows, and any columns can also be implemented as an independent embodiment.

[0121] FIG1 is a schematic diagram showing the architecture of a communication system according to an embodiment of the present disclosure.

[0122] As shown in FIG1 , a communication system 100 includes a shared access point (AP) device 101 and a first access point device 102 .

[0123] In some embodiments, the shared access point device 101 and the first access point device 102 can be access points for mobile terminals to enter a wired network. The AP is equivalent to a bridge connecting a wired network and a wireless network. Its main function is to connect various wireless network clients together and then connect the wireless network to the Ethernet. Specifically, the AP can be a terminal device or a network device with a wireless fidelity chip. Optionally, the AP can support multiple WLAN standards such as 802.11ax, 802.11be, 802.11ac, 802.11n, 802.11g, 802.11b and 802.11a, 802.11bf, 802.11bn, and support the next generation 802.11 protocol, but is not limited to this.

[0124] Optionally, in an embodiment of the present disclosure, the AP and STA may be devices supporting multiple connections, for example, they may be represented as a multi-connection access point device (AP MLD) and a multi-connection site device (Non-Access Point Multi-Link Device, Non-AP MLD), respectively; the AP MLD may represent an access point supporting multi-connection communication functions, and the non-AP MLD may represent a site supporting multi-connection communication functions.

[0125] It can be understood that the communication system described in the embodiment of the present disclosure is for the purpose of more clearly illustrating the technical solution of the embodiment of the present disclosure, and does not constitute a limitation on the technical solution proposed in the embodiment of the present disclosure. Ordinary technicians in this field can know that with the evolution of the system architecture and the emergence of new business scenarios, the technical solution proposed in the embodiment of the present disclosure is also applicable to similar technical problems.

[0126] The following embodiments of the present disclosure may be applied to the communication system 100 shown in FIG1 , or a portion thereof, but are not limited thereto. The entities shown in FIG1 are illustrative only. The communication system may include all or part of the entities shown in FIG1 , or may include other entities outside of FIG1 . The number and form of the entities are arbitrary, and the entities may be physical or virtual. The connection relationships between the entities are illustrative only. The entities may be connected or disconnected, and the connection may be in any manner, including direct or indirect, wired or wireless.

[0127] The various embodiments of the present disclosure can be applied to a wireless local area network (WLAN), such as a local area network that adopts the 802.11 series of protocols. In a WLAN, a basic service set (BSS) is a basic component of a WLAN. A BSS network is composed of station devices with certain associations within a specific coverage area. One scenario of association is that stations communicate directly with each other in an ad hoc network, which is called an independent basic service set (IBSS). Another more common scenario is that in a BSS network, there is only one central station with a dedicated BSS management function, which is called an access point device, and other stations in the BSS network that are not APs are called terminals, also called non-AP STAs. APs and non-AP STAs are collectively referred to as STAs. When describing STAs, there is no need to distinguish between APs and non-AP STAs. In the same BSS network, due to distance, transmission power, etc., a STA cannot detect other STAs that are farther away from it, and the two are hidden nodes of each other.

[0128] FIG2 is an interactive diagram of a communication method according to an embodiment of the present disclosure. As shown in FIG2 , the method includes:

[0129] In step 201, the shared access point device 101 determines a second wireless frame, wherein the second wireless frame includes third identification information; the third identification information identifies whether the neighboring AP of the shared AP supports inter-AP TXS (transmission opportunity sharing; TX stands for transmission opportunity).

[0130] Optionally, the second radio frame may include a beacon frame (beacon frame) or a probe response frame (probe response frame).

[0131] With the increase in frequency bands supported by Wi-Fi devices, the trend toward higher frequencies, and the diversification of communication services, WLAN deployments are becoming increasingly dense. This increasing density of APs leads to increased inter-cell interference and increases the risk of access conflicts. To further enhance user service quality and overall network performance, the next-generation Wi-Fi standard working group, 802.11bn, is focusing on coordination among multiple access points while pursuing improvements in communication speed, latency, and reliability within a single BSS. This collaborative effort between access points allows for more efficient allocation of communication resources, ensuring communication quality while improving access efficiency and achieving superior network performance.

[0132] APs can use coordination mechanisms to reduce inter-cell interference, ensure user service quality, and improve network communication speeds. Coordinated Time Division Multiple Address (C-TDMA) has attracted much attention as a coordination mechanism between multiple access points. C-TDMA involves the AP that has gained access dividing the duration of the TXOP and sharing its frequency resources for part of the TXOP duration with neighboring APs. The access point that shares the TXOP is called a Sharing / Coordination AP, and the AP coordinated by the shared AP is called a Shared / Coordinated AP.

[0133] Currently, in the C-TDMA process, the Sharing AP can identify the target STA through the AID (Association Identifier) ​​subfield in the User Info field in the MU-RTS TXS Trigger frame (Multi-User Request to Send, MU RTS), and set the transmission duration allocated by the Sharing AP to the target STA according to the TXOP it obtained in the MU-RTS TXS Trigger frame, so that the target STA can perform UL (up link) transmission or P2P (peer to peer) transmission within the transmission duration allocated by the Sharing AP to the target STA according to the received MU-RTS TXS Trigger frame, thereby realizing the TXS process between the Sharing AP and the target STA.

[0134] Refer to the TXS process between the Sharing AP and the target STA, and the TXS between APs, which refers to the TXS process between the Sharing AP and the Shared AP.

[0135] Optionally, in some embodiments, the third identification information is carried in a first Triggered TXOP Sharing Mode 3 Support identification bit of the second radio frame;

[0136] The first Triggered TXOP Sharing Mode 3 Support flag is carried in the Reduced Neighbor Report element field;

[0137] The first Triggered TXOP Sharing Mode 3 Support flag is set to a third parameter value, indicating that the neighbor AP supports inter-AP TXS.

[0138] As an example, the third parameter value may be set to 1, that is, when the first Triggered TXOP Sharing Mode 3 Support flag is set to 1, it indicates that the neighbor AP supports inter-AP TXS; otherwise, it indicates that the neighbor AP does not support inter-AP TXS.

[0139] In the above embodiment, the second radio frame includes the Reduced Neighbor Report element field, carries the MLD Parameters subfield in the Reduced Neighbor Report element field, and sets the first Triggered TXOP Sharing Mode 3 Support flag in the MLD Parameters subfield to the third parameter value, thereby indicating that the neighbor AP supports inter-AP TXS; otherwise, it indicates that the neighbor AP does not support inter-AP TXS; in this way, the device that obtains the second radio frame can parse the first Triggered TXOP Sharing Mode 3 Support flag in the MLD Parameters subfield to determine whether the neighbor AP supports inter-AP TXS, and when the first Triggered TXOP Sharing Mode 3 Support flag is set to the third parameter value, it is determined that the neighbor AP supports inter-AP TXS.

[0140] As an example, see Table 1, which shows the MLD Parameters subfield in the Neighbor AP Information Fields in the Reduced Neighbor Report element.

[0141] Table 1:

[0142] In Table 1, the AP MLD ID (Access Point Multi-Link Device Identification) field indicates the identifier of the multi-link access point device to which the AP is attached, and occupies 8 bits in the MLD Parameters subfield, with the corresponding bits being B0 to B7. The Link ID (Link Identification) field indicates the link identifier of the AP's working link, and occupies 4 bits in the MLD Parameters subfield, with the corresponding bits being B8 to B11. The BSS Parameters Change Count field indicates the number of BSS parameter set changes, and occupies 8 bits in the MLD Parameters subfield, with the corresponding bits being B12 to B19. The All Updates Included field indicates that all updates are included, and occupies 1 bit in the MLD Parameters subfield, with the corresponding bit being B20. The Disabled Link Indication field indicates the disabled link identifier, and occupies 1 bit in the MLD Parameters subfield, with the corresponding bit being B21. The Triggered TXOP Sharing Mode 3 Support field indicates that TXOP sharing mode 3 is supported, and occupies 1 bit in the MLD Parameters subfield. The reserved bit occupies one bit in the MLD Parameters subfield and has a bit order of B22. The reserved bit occupies one bit in the MLD Parameters subfield and has a bit order of B23.

[0143] Among them, you can<AP MLD ID,Link ID> For the neighbor AP that shares AP101, if the Triggered TXOP Sharing Mode 3 Support subfield is set to 1, it indicates that the neighbor AP supports inter-AP TXS; otherwise, it indicates that the neighbor AP does not support inter-AP TXS.

[0144] As an example, referring to Figure 3 , an AP MLD may represent an access point supporting multi-connection communication, and a non-AP MLD may represent a station supporting multi-connection communication. Referring to Figure 3 , an AP MLD may operate on three communication links (Links), such as AP1, AP2, and AP3, as shown in Figure 3 . AP1 operates on Link 1 (Link 1), AP2 operates on Link 2 (Link 2), and AP3 operates on Link 3 (Link 3). A non-AP MLD may also operate on three links, such as STA1, STA2, and STA3, as shown in Figure 3 . STA1 operates on Link 1, STA2 operates on Link 2, and STA3 operates on Link 3. In the example of Figure 3 , it is assumed that AP1 communicates with STA1 via a corresponding first link, Link 1. Similarly, AP2 communicates with STA2 via a corresponding second link, Link 2, and AP3 communicates with STA3 via a third link, Link 3. The identification information of an AP can be uniquely determined using the identifier of the multi-connection access point device to which it is attached and the link identifier of the link on which the AP operates. See Table 1. You can use the MLD Parameters subfield<AP MLD ID,Link ID> Uniquely identifies the neighboring APs that share the AP.

[0145] Optionally, in some embodiments, the second wireless frame further includes: fourth identification information; the fourth identification information identifies: whether the shared AP supports inter-AP TXS.

[0146] In the above embodiment, the fourth identification information in the second wireless frame indicates whether the shared AP supports inter-AP TXS. In this way, the device receiving the second wireless frame can determine whether the shared AP supports TXS.

[0147] In some embodiments, the fourth identification information is carried in a second Triggered TXOP Sharing Mode3 Support flag of the second radio frame;

[0148] The second Triggered TXOP Sharing Mode 3 Support flag is carried in an ultra high reliability capabilities element UHR Capabilities element field of the second radio frame;

[0149] The second Triggered TXOP Sharing Mode 3 Support flag is set to a fourth parameter value, indicating that the shared AP supports inter-AP TXS.

[0150] Optionally, the UHR Capabilities element field may include: an ultra-high reliability media access control capability information field UHR MAC Capabilities Information field; and the second Triggered TXOP Sharing Mode 3 Support flag is carried through the UHR MAC Capabilities Information field.

[0151] As an example, the fourth parameter value may be set to 1, ie, when the second Triggered TXOP Sharing Mode 3 Support flag is set to 1, it indicates that the shared AP 101 supports inter-AP TXS; otherwise, it indicates that the shared AP 101 does not support inter-AP TXS.

[0152] In the above embodiment, the device that receives the second wireless frame can parse the second wireless frame to obtain the UHR Capabilities element field, and parse the UHR Capabilities element to obtain the second Triggered TXOP Sharing Mode 3 Support flag, and then determine whether the shared AP supports inter-AP TXS based on the parameter value of the second Triggered TXOP Sharing Mode 3 Support flag, and when the second Triggered TXOP Sharing Mode 3 Support flag is set to the fourth parameter value, determine that the shared AP supports inter-AP TXS.

[0153] Step 202 : The shared access point device 101 broadcasts a second wireless frame.

[0154] Optionally, in some embodiments, the shared access point device 101 may broadcast the second wireless frame to neighboring APs (including the first AP 102 ) of the shared access point device 101 or to a site device associated with the shared access point device 101 .

[0155] In some embodiments, the station device includes, for example, a wireless communication chip, a wireless sensor, or a wireless communication terminal that supports Wi-Fi communication. Optionally, the wireless communication terminal includes, but is not limited to, at least one of a mobile phone, a wearable device, an Internet of Things device that supports Wi-Fi communication, a car with WiFi communication, a smart car, a tablet computer, a computer with wireless transceiver function, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal device in industrial control, a wireless terminal device in self-driving, a wireless terminal device in remote medical surgery, a wireless terminal device in a smart grid, a wireless terminal device in transportation safety, a wireless terminal device in a smart city, and a wireless terminal device in a smart home.

[0156] Specifically, the site device may be a terminal device or network device with a Wireless Fidelity (Wi-Fi) chip. Optionally, the site device may support multiple WLAN standards, such as 802.11ax, 802.11be, 802.11ac, 802.11n, 802.11g, 802.11b, 802.11a, 802.11bf, and 802.11bn, as well as the next generation 802.11 protocol, but is not limited thereto.

[0157] In the above embodiment, the shared AP determines and sends a second wireless frame, and uses the third identification information in the second wireless frame to identify whether the neighbor AP of the shared AP supports inter-AP TXS; in this way, the device receiving the second wireless frame can determine whether the neighbor AP of the shared AP supports inter-AP TXS.

[0158] Step 203: After obtaining a transmission opportunity TXOP, the sharing access point device 101 determines a first radio frame; the first radio frame identifies the transmission duration shared by the sharing AP 101 with the shared device according to the TXOP;

[0159] The first wireless frame includes first identification information; the first identification information includes identification information of the shared device; and the shared device includes a shared AP.

[0160] Optionally, the shared AP may be the first AP 102 mentioned above.

[0161] In related technologies, when Shared APs are identified by using the RA (Receiver Address) in the MU-RTS TXS Trigger frame as the AP's MAC address, this not only conflicts with the 802.11 standard that sets the RA in the MU-RTS Trigger frame as the broadcast address, but also results in problems such as Sharing APs being able to allocate TXOPs only to a single Shared AP, resulting in low transmission efficiency. Therefore, in the disclosed embodiments, it is necessary to clearly define how Sharing APs allocate transmission time to neighboring APs that support Inter-AP TXS during C-TDMA.

[0162] Optionally, the first radio frame may be a MU-RTS TXS Trigger frame.

[0163] Optionally, in the first radio frame, the first identification information may be set to identify the identification information of the shared AP or the identification information of the shared STA, depending on the actual situation. As an example, in the first radio frame, the shared AP and the shared STA may share the same field, thereby identifying the shared AP through the first radio frame during the C-TDMA process.

[0164] Optionally, in some embodiments, the first identification information is carried in a user information field of the first radio frame;

[0165] The User Info field includes an AP MLD ID subfield and a Link ID subfield, and the first identification information identifies the identification information of the shared AP101; the AP MLD ID subfield identifies the identification AP MLD ID of the multi-connection access point device to which the shared AP is attached, and the Link ID subfield identifies the link identification Link ID of the shared AP working link.

[0166] As mentioned above, it is possible to<AP MLD ID,Link ID> The unique identification of AP is not described in detail here.

[0167] Optionally, the User Info field may further include an AID (association identifier) ​​12 subfield, where the first identification information identifies identification information of the shared STA.

[0168] Optionally, the AID12 field and the AP Identifier field may share the same field in the User Info field. For example, the AID12 field and the AP Identifier field may share the fields indicated by B0 to B11 in the User Info field.

[0169] In the above embodiment, the first identification information is carried by the User Info field of the first radio frame, and the User Info field is set to include an AP MLD ID subfield and a Link ID subfield, and the AP MLD ID subfield identifies the AP MLD ID of the multi-connection access point device to which the shared AP is attached, and the Link ID subfield identifies the link identifier Link ID of the shared AP working link, indicating the identification information of the shared AP; in this way,<AP MLD ID,Link ID> By sharing the same field in the User Info field as the AID12 subfield, it is possible to achieve, during the C-TDMA process, allocating transmission time by the sharing AP101 to the target sharing AP101 for its neighboring APs supporting inter-AP TXS.

[0170] Optionally, in some embodiments, the User Info field further includes at least one of an Allocation Duration subfield, a Resource Unit Allocation RU Allocation subfield, and a Master-Slave 160 PS160 subfield.

[0171] In the above embodiment, the User Info field of the first wireless frame carries the Allocation Duration subfield, the RU Allocation subfield, and the PS160 subfield; in this way, the device receiving the first wireless frame can obtain the transmission resources allocated by the sharing AP101 to the shared device by parsing the first wireless frame, and then, when the device receiving the first wireless frame is the shared device, data interaction is performed according to the transmission resources; when the device receiving the first wireless frame is not the shared device, data interaction is avoided within the transmission resource, so as to avoid interfering with the process of data interaction of the shared device according to the transmission resource.

[0172] As an example, see Table 2, which shows the User Info field in the MU-RTS TXS Trigger frame.

[0173] Table 2:

[0174] In Table 2, the AID12 field identifies the shared STA's identification information, and the AP Identifier field identifies the shared AP's identification information. The AID12 and AP Identifier fields share the fields indicated by B0 to B11 in the User Info field and occupy 12 bits. When the fields indicated by B0 to B11 in the User Info field include the AP Identifier field, the shared device is identified as a shared AP. When the fields indicated by B0 to B11 in the User Info field include the AID12 field, the shared device is identified as a shared AP.

[0175] RU Allocation indicates resource unit allocation and occupies 8 bits in the User Info field, with the corresponding bits in order from B12 to B19. Allocation Duration indicates the allocation duration and occupies 9 bits in the User Info field, with the corresponding bits in order from B20 to B28. Reserved indicates reserved bits and occupies 10 bits in the User Info field, with the corresponding bits in order from B29 to B38. The PS160 field indicates primary and secondary channel 160 and occupies 1 bit in the User Info field, with the corresponding bit order from B39.

[0176] Table 3:

[0177] As shown in Table 3, when the fields indicated by B0 to B11 in the User Info field include the AP Identifier field, the AP Identifier field may include an AP MLD ID subfield and a Link ID subfield. The AP MLD ID subfield occupies the subfields indicated by B0 to B7 and occupies 8 bits; the Link ID subfield occupies the subfields indicated by B8 to B11 and occupies 4 bits.

[0178] Optionally, in some embodiments, the first radio frame further includes second identification information;

[0179] The second identification information identifies the type of the TXOP shared by the sharing AP 101 , where the type of the TXS includes allocating the transmission duration to the shared AP.

[0180] Optionally, the TXS type may further include: allocating the transmission duration to the shared STA.

[0181] In the above embodiment, the type of TXOP shared TXS initiated by the sharing AP is identified by the second identification information in the first wireless frame, and the type of the TXS includes allocating the transmission time to the shared AP; in this way, the device that obtains the first wireless frame can obtain the type of TXOP shared TXS initiated by the sharing AP by parsing the first wireless frame.

[0182] Optionally, in some embodiments, the second identification information is carried in a Triggered TXOP Sharing Mode subfield of the first radio frame;

[0183] The Triggered TXOP Sharing Mode subfield is carried in the Common Info field of the first radio frame;

[0184] The Triggered TXOP Sharing Mode subfield is set to a first parameter value, indicating that the sharing AP 101 allocates the transmission duration to the shared AP.

[0185] As an example, the first parameter value may be set to 3. That is, when the Triggered TXOP Sharing Mode subfield is set to 3, it indicates that the sharing AP 101 allocates the transmission duration to the shared AP.

[0186] Optionally, when the Triggered TXOP Sharing Mode subfield is set to the second parameter value, it may also indicate that the sharing AP 101 allocates the transmission duration to the shared STA.

[0187] As an example, the second parameter value may be set to 1 or 2. That is, when the Triggered TXOP Sharing Mode subfield is set to 1 or 2, it indicates that the sharing AP 101 allocates the transmission duration to the shared STA.

[0188] As an example, see Table 4, which shows the value and description of the TXOP Sharing Mode subfield in the MU-RTS TXS Trigger frame;

[0189] Table 4:

[0190] Referring to Table 4, when the TXOP Sharing Mode subfield is set to 0, it indicates that MU-RTS does not start the MU-RTS TXOP sharing process; when the TXOP Sharing Mode subfield is set to 1, it indicates that MU-RTS starts the MU-RTS TXOP sharing process, wherein the scheduled STA can only transmit PPDU addressed to its associated AP; when the TXOP Sharing Mode subfield is set to 2, it indicates that MU-RTS starts the MU-RTS TXOP sharing process, wherein the scheduled STA can send PPDU addressed to its associated AP or to another STA; when the TXOP Sharing Mode subfield is set to 3, it indicates that MU-RTS starts the MU-RTS TXOP sharing process, wherein the scheduled AP (Shared AP) can send MPDU to its associated STA or Sharing AP.

[0191] In the above embodiment, the first wireless frame includes a Common Info field, and the Common Info field includes a Triggered TXOP Sharing Mode subfield. When the Triggered TXOP Sharing Mode subfield is set to a first parameter value, it indicates that the sharing AP 101 allocates the transmission time to the shared AP; when the Triggered TXOP Sharing Mode subfield is set to a second parameter value, it indicates that the sharing AP 101 allocates the transmission time to the shared STA. In this way, the device that obtains the first wireless frame can obtain the transmission time allocated by the sharing AP 101 to the shared AP or the shared STA by parsing the parameter value of the Triggered TXOP Sharing Mode subfield in the first wireless frame.

[0192] In step 204 , the sharing AP 101 sends the first wireless frame to instruct the shared device to perform data exchange with the sharing AP 101 or the STA associated with the shared device within the transmission duration.

[0193] Optionally, in some embodiments, the shared access point device 101 may send the first wireless frame to a neighboring AP (including the first AP 102 ) of the shared access point device 101 or a site device associated with the shared access point device 101 .

[0194] In the above embodiment, after obtaining the transmission opportunity TXOP, the sharing AP101 determines the first wireless frame; the sharing AP101 shares the transmission duration with the shared device according to the TXOP through the first wireless frame identification; and the first wireless frame includes first identification information, and the first identification information includes identification information of the shared device; the shared device includes the shared AP; and the first wireless frame is sent to the shared device, instructing the shared device to interact with the sharing AP101 or the STA associated with the shared device within the transmission duration; in this way, in the C-TDMA process, the transmission duration is allocated to the shared AP that supports inter-AP TXS among its neighboring APs through the Sharing AP.

[0195] In step 205 , the first AP 102 determines whether the first identification information includes the identification information of the first AP 102 . If the first identification information includes the identification information of the first AP 102 , step 206 is executed.

[0196] Optionally, in some embodiments, when the User Info field includes an AP MLD ID subfield and a Link ID subfield, the first AP 102

[0197] Determine that the AP MLD ID subfield matches the identifier of the multi-connection access point device to which the first AP102 is attached, and the Link ID subfield matches the link identifier of the working link of the first AP102, and determine that the first identification information includes the identification information of the first AP102.

[0198] Optionally, the first AP 102 may parse the received first wireless frame to determine whether the User Info field includes the AP MLD ID subfield and the Link ID subfield, that is, determine whether the shared device type included in the first identification information is AP.

[0199] Optionally, when the first AP102 determines that the User Info field does not include the AP MLD ID subfield and the Link ID subfield, it can determine that the shared device type included in the first identification information is not an AP, and within the time slot allocated by the shared AP101, it does not interact with data with the shared AP101 or the STA that is not associated with the first AP102.

[0200] Optionally, when determining that the User Info field includes the AP MLD ID subfield and the Link ID subfield (i.e., determining that the shared device type included in the first identification information is AP), the first AP102 can determine whether the AP MLD ID in the AP MLD ID subfield in the User Info field matches the identifier of the multi-connection access point device to which the first AP102 is attached, and whether the Link ID in the Link ID subfield in the AP MLD ID subfield in the User Info field matches the link identifier of the working link of the first AP102; when determining that the AP MLD ID in the AP MLD ID subfield matches the identifier of the multi-connection access point device to which the first AP102 is attached, and the Link ID in the Link ID subfield matches the link identifier of the working link of the first AP102, it is determined that the first identification information includes the identification information of the first AP102.

[0201] Optionally, when the first AP102 determines that the User Info field includes the AP MLD ID subfield and the Link ID subfield, if it is determined that the AP MLD ID in the AP MLD ID subfield does not match the identifier of the multi-connection access point device to which the first AP102 is attached, or the Link ID in the Link ID subfield does not match the link identifier of the working link of the first AP102, it is determined that the first identification information does not include the identification information of the first AP102, and data interaction is not performed with the shared AP101 or the STA that is not associated with the first AP102 within the time slot allocated by the shared AP101.

[0202] In the above embodiment, the first AP102 can determine that the shared AP101 has allocated a transmission duration for the first AP102 when determining that the first identification information includes the identification information of the first AP102, and interact with data with the shared AP101 or the STA associated with the first AP102 within the transmission duration.

[0203] In step 206 , the first AP 102 determines that the first identification information includes the identification information of the first AP 102 , and performs data interaction with the shared AP 101 or the STA associated with the first AP 102 within the transmission duration.

[0204] In the above embodiment, the first AP102 can obtain the first identification information by parsing the received first wireless frame, and when it is determined that the first identification information includes the identification information of the first AP102, it interacts with data with the shared AP101 or the SP associated with the first AP102 within the transmission duration.

[0205] Optionally, the performing data interaction with the shared AP 101 or a STA associated with the first AP 102 within the transmission duration includes:

[0206] According to the transmission resources indicated by at least one of the Allocation Duration subfield, the RU Allocation subfield and the PS160 subfield, data interaction is performed with the shared AP101 or the STA associated with the first AP102 within the transmission duration.

[0207] Optionally, the first AP102 may also perform data interaction with the STA associated with the first AP102 within the transmission duration allocated by the shared AP101 based on the transmission resources indicated by at least one of the Allocation Duration subfield, the RU Allocation subfield and the PS160 subfield.

[0208] In the above embodiment, the first AP102 interacts with the STA that shares AP101 or is associated with the first AP102 within the transmission duration based on the transmission resources indicated by at least one of the Allocation Duration subfield, the RU Allocation subfield, and the PS160 subfield indicated by the first wireless frame, thereby saving signaling overhead and avoiding contention conflicts and transmission interference in the OBSS scenario.

[0209] The media synchronization recovery method involved in the embodiments of the present disclosure may include at least one of the aforementioned steps and embodiments. For example, step 201 can be implemented as an independent embodiment, step 202 can be implemented as an independent embodiment, step 203 can be implemented as an independent embodiment, step 204 can be implemented as an independent embodiment, step 205 can be implemented as an independent embodiment, and step 206 can be implemented as an independent embodiment; the combination of step 201 and step 202 can be implemented as an independent embodiment, the combination of step 203 and step 204 can be implemented as an independent embodiment, the combination of step 205 and step 206 can be implemented as an independent embodiment, the combination of step 203, step 204, step 205 and step 206 can be implemented as an independent embodiment, and the combination of step 201, step 202, step 203, step 204, step 205 and step 206 can be implemented as an independent embodiment, but is not limited thereto.

[0210] In some embodiments, reference may be made to other optional implementations described before or after the description corresponding to FIG. 2 .

[0211] In some embodiments, the names of information, etc. are not limited to the names described in the embodiments, and terms such as "information", "message", "signal", "signaling", "report", "configuration", "indication", "instruction", "command", "channel", "parameter", "domain", "field", "symbol", "bit", "data", "program", and "chip" can be used interchangeably.

[0212] In some embodiments, terms such as "moment", "time point", "time", and "time position" can be replaced with each other, and terms such as "duration", "period", "time window", "window", and "time" can be replaced with each other.

[0213] In some embodiments, terms such as wireless access scheme and waveform may be used interchangeably.

[0214] In some embodiments, terms such as "certain", "preset", "preset", "setting", "indicated", "a certain", "any", and "first" can be interchangeable. "Specific A", "preset A", "preset A", "setting A", "indicated A", "a certain A", "any A", and "first A" can be interpreted as A pre-specified in a protocol, etc., or as A obtained through setting, configuration, or indication, etc., or as specific A, a certain A, any A, or first A, etc., but not limited to this.

[0215] In some embodiments, the determination or judgment can be performed by a value represented by 1 bit (0 or 1), or by a true or false value (Boolean value) represented by true or false, or by comparison of numerical values ​​(for example, comparison with a predetermined value), but is not limited thereto.

[0216] In some embodiments, "not expecting to receive" can be interpreted as not receiving on time domain resources and / or frequency domain resources, or as not performing subsequent processing on the data after receiving it; "not expecting to send" can be interpreted as not sending, or as sending but not expecting the recipient to respond to the content sent.

[0217] FIG4 is a flowchart of a communication method according to an embodiment of the present disclosure.

[0218] As shown in FIG4 , the above method can be applied to a shared access point device 101, and the above method includes:

[0219] Step 401: The shared access point device 101 determines a second wireless frame; wherein the second wireless frame includes third identification information; the third identification information identifies whether a neighboring AP of the shared AP supports inter-AP TXS.

[0220] Optionally, in some embodiments, the third identification information is carried in a first Triggered TXOP Sharing Mode 3 Support identification bit of the second radio frame;

[0221] The first Triggered TXOP Sharing Mode 3 Support flag is carried in the Reduced Neighbor Report element field;

[0222] The first Triggered TXOP Sharing Mode 3 Support flag is set to a third parameter value, indicating that the neighbor AP supports inter-AP TXS.

[0223] Optionally, in some embodiments, the second wireless frame further includes: fourth identification information; the fourth identification information identifies: whether the shared AP supports inter-AP TXS.

[0224] In the above embodiment, the fourth identification information in the second wireless frame indicates whether the shared AP supports inter-AP TXS. In this way, the device receiving the second wireless frame can determine whether the shared AP supports TXS.

[0225] In some embodiments, the fourth identification information is carried in a second Triggered TXOP Sharing Mode 3 Support flag of the second radio frame;

[0226] The second Triggered TXOP Sharing Mode 3 Support flag is carried in an ultra high reliability capabilities element UHR Capabilities element field of the second radio frame;

[0227] The second Triggered TXOP Sharing Mode 3 Support flag is set to a fourth parameter value, indicating that the shared AP supports inter-AP TXS.

[0228] The optional implementation of step 401 can refer to the optional implementation of step 201 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0229] Step 402 : The shared access point device 101 broadcasts a second wireless frame.

[0230] The optional implementation of step 402 can refer to the optional implementation of step 202 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0231] Step 403: After obtaining a transmission opportunity TXOP, the sharing access point device 101 determines a first radio frame; the first radio frame identifies the transmission duration shared by the sharing AP 101 with the shared device according to the TXOP;

[0232] The first wireless frame includes first identification information; the first identification information includes identification information of the shared device; and the shared device includes a shared AP.

[0233] Optionally, in some embodiments, the first identification information is carried in a user information field of the first radio frame;

[0234] The User Info field includes an AP MLD ID subfield and a Link ID subfield, and the first identification information identifies the identification information of the shared AP; the AP MLD ID subfield identifies the identification AP MLD ID of the multi-connection access point device to which the shared AP is attached, and the Link ID subfield identifies the link identification Link ID of the shared AP working link.

[0235] Optionally, in some embodiments, the User Info field further includes at least one of an Allocation Duration subfield, a Resource Unit Allocation RU Allocation subfield, and a Master-Slave 160 PS160 subfield.

[0236] Optionally, in some embodiments, the first radio frame further includes second identification information;

[0237] The second identification information identifies the type of the TXOP shared by the sharing AP 101 , where the type of the TXS includes allocating the transmission duration to the shared AP.

[0238] Optionally, in some embodiments, the second identification information is carried in a Triggered TXOP Sharing Mode subfield of the first radio frame;

[0239] The Triggered TXOP Sharing Mode subfield is carried in the Common Info field of the first radio frame;

[0240] The Triggered TXOP Sharing Mode subfield is set to a first parameter value, indicating that the sharing AP 101 allocates the transmission duration to the shared AP.

[0241] The optional implementation of step 403 can refer to the optional implementation of step 203 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0242] In step 404 , the sharing AP 101 sends the first wireless frame to instruct the shared device to perform data exchange with the sharing AP 101 or a STA associated with the shared device within the transmission duration.

[0243] The optional implementation of step 404 can refer to the optional implementation of step 204 in Figure 2 and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0244] The communication method involved in the embodiments of the present disclosure may include at least one of the aforementioned steps and embodiments. For example, step 401 can be implemented as an independent embodiment, step 402 can be implemented as an independent embodiment, step 403 can be implemented as an independent embodiment, and step 404 can be implemented as an independent embodiment; the combination of step 401 and step 402 can be implemented as an independent embodiment, the combination of step 403 and step 404 can be implemented as an independent embodiment, and the combination of step 401, step 402, step 403, and step 404 can be implemented as an independent embodiment, but is not limited thereto.

[0245] In some embodiments, reference may be made to other optional implementations described before or after the description corresponding to FIG. 4 .

[0246] FIG5 is a second flowchart of a communication method according to an embodiment of the present disclosure.

[0247] As shown in FIG5 , the above method may be applied to the first access point device 102, and the above method includes:

[0248] In step 501 , the first access point device 102 receives a second wireless frame sent by the access point device 101 ; wherein the second wireless frame includes third identification information; the third identification information identifies whether the neighboring AP of the shared AP supports inter-AP TXS.

[0249] Optionally, in some embodiments, the third identification information is carried in a first Triggered TXOP Sharing Mode 3 Support identification bit of the second radio frame;

[0250] The first Triggered TXOP Sharing Mode 3 Support flag is carried in the Reduced Neighbor Report element field;

[0251] The first Triggered TXOP Sharing Mode 3 Support flag is set to a third parameter value, indicating that the neighbor AP supports inter-AP TXS.

[0252] Optionally, in some embodiments, the second wireless frame further includes: fourth identification information; the fourth identification information identifies: whether the shared AP supports inter-AP TXS.

[0253] In the above embodiment, the fourth identification information in the second wireless frame indicates whether the shared AP supports inter-AP TXS. In this way, the device receiving the second wireless frame can determine whether the shared AP supports TXS.

[0254] In some embodiments, the fourth identification information is carried in a second Triggered TXOP Sharing Mode3 Support flag of the second radio frame;

[0255] The second Triggered TXOP Sharing Mode 3 Support flag is carried in an ultra high reliability capabilities element UHR Capabilities element field of the second radio frame;

[0256] The second Triggered TXOP Sharing Mode 3 Support flag is set to a fourth parameter value, indicating that the shared AP supports inter-AP TXS.

[0257] The optional implementation of step 501 can refer to step 201 in FIG. 2 , the optional implementation of step 202 , and other related parts in the embodiment involved in FIG. 2 , which will not be described in detail here.

[0258] Step 502: The first access point device 102 receives a first radio frame sent by the access point device 101 after obtaining a transmission opportunity TXOP; the first radio frame indicates that the sharing AP 101 shares a transmission duration with the shared device according to the TXOP;

[0259] The first wireless frame includes first identification information; the first identification information includes identification information of the shared device; and the shared device includes a shared AP.

[0260] Optionally, in some embodiments, the first identification information is carried in a user information field of the first radio frame;

[0261] The User Info field includes an AP MLD ID subfield and a Link ID subfield, and the first identification information identifies the identification information of the shared AP; the AP MLD ID subfield identifies the identification AP MLD ID of the multi-connection access point device to which the shared AP is attached, and the Link ID subfield identifies the link identification Link ID of the shared AP working link.

[0262] Optionally, in some embodiments, the User Info field further includes at least one of an Allocation Duration subfield, a Resource Unit Allocation RU Allocation subfield, and a Master-Slave 160 PS160 subfield.

[0263] Optionally, in some embodiments, the first radio frame further includes second identification information;

[0264] The second identification information identifies: the type of the TXOP shared TXS initiated by the sharing AP 101, and the type of the TXS includes allocating the transmission duration to the shared AP, or allocating the transmission duration to the shared STA.

[0265] Optionally, in some embodiments, the second identification information is carried in a Triggered TXOP Sharing Mode subfield of the first radio frame;

[0266] The Triggered TXOP Sharing Mode subfield is carried in the Common Info field of the first radio frame;

[0267] The Triggered TXOP Sharing Mode subfield is set to a first parameter value, indicating that the sharing AP 101 allocates the transmission duration to the shared AP.

[0268] The optional implementation of step 502 can refer to the optional implementation of step 203 and step 204 in Figure 2, and other related parts in the embodiment involved in Figure 2, which will not be repeated here.

[0269] In step 503 , the first AP 102 determines whether the first identification information includes the identification information of the first AP 102 . If the first AP 102 determines that the first identification information includes the identification information of the first AP 102 , step 504 is executed.

[0270] Optionally, in some embodiments, when the User Info field includes an AP MLD ID subfield and a Link ID subfield, the first AP 102

[0271] Determine that the AP MLD ID subfield matches the identifier of the multi-connection access point device to which the first AP102 is attached, and the Link ID subfield matches the link identifier of the working link of the first AP102, and determine that the first identification information includes the identification information of the first AP102.

[0272] The optional implementation of step 503 can refer to the optional implementation of step 205 in FIG. 2 and other related parts in the embodiment involved in FIG. 2 , which will not be described in detail here.

[0273] In step 504 , the first AP 102 determines that the first identification information includes the identification information of the first AP 102 , and performs data interaction with the shared AP 101 or the STA associated with the first AP 102 within the transmission duration.

[0274] Optionally, the performing data interaction with the shared AP 101 or a STA associated with the first AP 102 within the transmission duration includes:

[0275] According to the transmission resources indicated by at least one of the Allocation Duration subfield, the RU Allocation subfield and the PS160 subfield, data interaction is performed with the shared AP101 or the STA associated with the first AP102 within the transmission duration.

[0276] The optional implementation of step 503 can refer to the optional implementation of step 206 in FIG. 2 and other related parts in the embodiment involved in FIG. 2 , which will not be described in detail here.

[0277] The communication method involved in the embodiments of the present disclosure may include at least one of the aforementioned steps and embodiments. For example, step 501 can be implemented as an independent embodiment, step 502 can be implemented as an independent embodiment, step 503 can be implemented as an independent embodiment, step 504 can be implemented as an independent embodiment, the combination of step 502 and step 503 can be implemented as an independent embodiment, the combination of step 503 and step 504 can be implemented as an independent embodiment, the combination of step 501, step 502 and step 503 can be implemented as an independent embodiment, and the combination of step 501, step 502, step 503 and step 504 can be implemented as an independent embodiment, but is not limited thereto.

[0278] In some embodiments, reference may be made to other optional implementations described before or after the description corresponding to FIG. 5 .

[0279] The embodiments of the present disclosure further provide an apparatus for implementing any of the above methods. For example, an apparatus is provided, comprising units or modules for implementing each step performed by a terminal in any of the above methods. For another example, another apparatus is provided, comprising units or modules for implementing each step performed by a network device (e.g., an access network device, a core network function node, a core network device, etc.) in any of the above methods.

[0280] It should be understood that the division of the various units or modules in the above device is merely a division of logical functions. In actual implementation, they may be fully or partially integrated into a physical entity, or they may be physically separated. In addition, the units or modules in the device may be implemented in the form of a processor calling software: for example, the device includes a processor, the processor is connected to a memory, and the memory stores instructions. The processor calls the instructions stored in the memory to implement any of the above methods or implement the functions of the various units or modules of the above device, wherein the processor is, for example, a general-purpose processor, such as a central processing unit (CPU) or a microprocessor, and the memory is a memory within the device or a memory outside the device. Alternatively, the units or modules in the device can be implemented in the form of hardware circuits, and the functions of some or all of the units or modules can be realized by designing the hardware circuits. The above-mentioned hardware circuits can be understood as one or more processors; for example, in one implementation, the above-mentioned hardware circuit is an application-specific integrated circuit (ASIC), which realizes the functions of some or all of the above units or modules by designing the logical relationship of the components in the circuit; for example, in another implementation, the above-mentioned hardware circuit can be realized by a programmable logic device (PLD). Taking a field programmable gate array (FPGA) as an example, it can include a large number of logic gate circuits, and the connection relationship between the logic gate circuits is configured by configuring the configuration file, thereby realizing the functions of some or all of the above units or modules. All units or modules of the above devices can be realized in the form of software called by the processor, or in the form of hardware circuits, or in part by the form of software called by the processor, and the rest by hardware circuits.

[0281] In the embodiment of the present disclosure, the processor is a circuit with signal processing capability. In one implementation, the processor can be a circuit with instruction reading and execution capability, such as a central processing unit (CPU), a microprocessor, a graphics processing unit (GPU) (which can be understood as a microprocessor), or a digital signal processor (DSP); in another implementation, the processor can implement certain functions through the logical relationship of the hardware circuit, and the logical relationship of the above hardware circuit is fixed or reconfigurable, such as a hardware circuit implemented by a processor as an application-specific integrated circuit (ASIC) or a programmable logic device (PLD), such as an FPGA. In a reconfigurable hardware circuit, the process of the processor loading a configuration document and implementing the hardware circuit configuration can be understood as the process of the processor loading instructions to implement the functions of some or all of the above units or modules. In addition, it can also be a hardware circuit designed for artificial intelligence, which can be understood as an ASIC, such as a neural network processing unit (NPU), a tensor processing unit (TPU), a deep learning processing unit (DPU), etc.

[0282] FIG6 is a schematic diagram of a structure of a shared access point device according to an embodiment of the present disclosure. As shown in FIG6 , the shared access point device 600 may include at least one of a determination module 601 and a sending module 602 .

[0283] In some embodiments, the above-mentioned determination module 601 is used to determine a first wireless frame after obtaining a transmission opportunity TXOP; the first wireless frame identifies the sharing AP and shares the transmission duration with the shared device according to the TXOP; wherein, the first wireless frame includes first identification information; the first identification information includes identification information of the shared device; and the shared device includes the shared AP.

[0284] In some embodiments, the sending module 602 is configured to send the first wireless frame to instruct the shared device to perform data interaction with the sharing AP or a STA associated with the shared device within the transmission duration.

[0285] Optionally, the determining module 601 is configured to execute at least one of the communication steps (eg, step 201, step 203, step 401, step 403, but not limited thereto) performed by the shared access point device 101 in any of the above methods, which will not be described in detail herein.

[0286] Optionally, the sending module 602 is configured to execute at least one of the sending and receiving steps (eg, step 202, step 202, step 403, step 404, but not limited thereto) executed by the shared access point device 101 in any of the above methods, which will not be described in detail here.

[0287] FIG7 is a schematic diagram of a first access point device according to an embodiment of the present disclosure. As shown in FIG7 , the first access point device 700 may include at least one of a receiving module 701 and a processing module 702 .

[0288] In some embodiments, the above-mentioned receiving module 701 is used to receive a first wireless frame; the first wireless frame identifies that the sharing AP shares the transmission duration with the shared device based on the obtained TXOP; wherein, the first wireless frame includes first identification information; the first identification information includes identification information of the shared device; the shared device includes the shared AP.

[0289] In some embodiments, the processing module 702 is configured to determine that the first identification information includes identification information of the first AP, and to perform data interaction with the shared AP or a STA associated with the first AP within the transmission duration.

[0290] Optionally, the receiving module 701 is configured to execute at least one of the sending and receiving steps (eg, step 501 and step 502 , but not limited thereto) executed by the first access point device 102 in any of the above methods, which will not be described in detail herein.

[0291] The processing module 702 is configured to execute at least one of the communication steps (eg, step 205, step 206, step 503, step 504, but not limited thereto) performed by the first access point device 102 in any of the above methods, which will not be described in detail here.

[0292] Figure 8 is a schematic diagram of the structure of a terminal 800 (e.g., user equipment) proposed in an embodiment of the present disclosure. Terminal 800 can be a chip, chip system, or processor that supports a network device implementing any of the above methods, or a chip, chip system, or processor that supports a terminal implementing any of the above methods. Terminal 800 can be used to implement the methods described in the above method embodiments. For details, please refer to the description of the above method embodiments.

[0293] As shown in Figure 8, terminal 800 includes one or more processors 801. Processor 801 can be a general-purpose processor or a dedicated processor, for example, a baseband processor or a central processing unit. The baseband processor can be used to process communication protocols and communication data, and the central processing unit can be used to control communication devices (such as base stations, baseband chips, terminal devices, terminal device chips, DUs or CUs, etc.), execute programs, and process program data. Terminal 800 is used to perform any of the above methods.

[0294] In some embodiments, the terminal 800 further includes one or more memories 802 for storing instructions. Optionally, all or part of the memories 802 may be located outside the terminal 800.

[0295] In some embodiments, the terminal 800 further includes one or more transceivers 804. When the terminal 800 includes one or more transceivers 804, the transceiver 804 performs at least one of the communication steps such as sending and / or receiving in the above method (for example, step 202, step 204, step 402, step 404, step 501, step 502, but not limited thereto), and the processor 801 performs at least one of the other steps (for example, step 201, step 203, step 205, step 206, step 401, step 403, step 503, step 504, but not limited thereto).

[0296] In some embodiments, a transceiver may include a receiver and / or a transmitter. The receiver and transmitter may be separate or integrated. Optionally, the terms transceiver, transceiver unit, transceiver, and transceiver circuit may be used interchangeably; the terms transmitter, transmitting unit, transmitter, and transmitting circuit may be used interchangeably; and the terms receiver, receiving unit, receiver, and receiving circuit may be used interchangeably.

[0297] In some embodiments, terminal 800 may include one or more interface circuits 803. Optionally, interface circuit 803 is connected to memory 802. Interface circuit 803 may be configured to receive signals from memory 802 or other devices, and may be configured to send signals to memory 802 or other devices. For example, interface circuit 803 may read instructions stored in memory 802 and send the instructions to processor 801.

[0298] The terminal 800 described in the above embodiment may be a communication device such as a user device, but the scope of the terminal 800 described in the present disclosure is not limited thereto, and the structure of the terminal 800 may not be limited by FIG8 . The communication device may be an independent device or may be part of a larger device. For example, the communication device may be: (1) an independent integrated circuit IC, or a chip, or a chip system or subsystem; (2) a collection of one or more ICs, optionally, the above IC collection may also include a storage component for storing data and programs; (3) an ASIC, such as a modem; (4) a module that can be embedded in other devices; (5) a receiver, a terminal device, an intelligent terminal device, a cellular phone, a wireless device, a handheld device, a mobile unit, an in-vehicle device, a network device, a cloud device, an artificial intelligence device, etc.; (6) others, etc.

[0299] FIG9 is a schematic diagram of the structure of a chip 900 according to an embodiment of the present disclosure. If the terminal 1300 can be a chip or a chip system, reference can be made to the schematic diagram of the structure of the chip 900 shown in FIG9 , but the present disclosure is not limited thereto.

[0300] The chip 900 includes one or more processors 901 , and the chip 900 is configured to execute any of the above methods.

[0301] In some embodiments, chip 900 further includes one or more 903. Optionally, interface circuit 903 is connected to memory 902. Interface circuit 903 can be used to receive signals from memory 902 or other devices, and can be used to send signals to memory 902 or other devices. For example, interface circuit 903 can read instructions stored in memory 902 and send the instructions to processor 901.

[0302] In some embodiments, the interface circuit 903 executes at least one of the communication steps such as sending and / or receiving in the above method (for example, step 201, step 203, step 205, step 401, step 403, step 503, but not limited to these), and the processor 901 executes at least one of the other steps (for example, step 201, step 203, step 205, step 206, step 401, step 403, step 503, step 504, but not limited to these).

[0303] In some embodiments, terms such as interface circuit, interface, transceiver pin, and transceiver may be used interchangeably.

[0304] In some embodiments, the chip 900 further includes one or more memories 902 for storing instructions. Alternatively, all or part of the memory 902 may be external to the chip 900.

[0305] The present disclosure also provides a storage medium having instructions stored thereon. When the instructions are executed on the terminal 800, the terminal 800 executes any of the above methods. Optionally, the storage medium is an electronic storage medium. Optionally, the storage medium is a computer-readable storage medium, but is not limited thereto and may also be a storage medium readable by other devices. Optionally, the storage medium may be a non-transitory storage medium, but is not limited thereto and may also be a transient storage medium.

[0306] The present disclosure also provides a program product, which, when executed by the terminal 800, enables the terminal 800 to perform any of the above methods. Optionally, the program product is a computer program product.

[0307] The present disclosure also proposes a computer program, which, when executed on a computer, causes the computer to perform any one of the above methods.

Claims

1. A communication method, characterized in that: Applicable to share access point devices AP, including: After obtaining a transmission opportunity TXOP, a first wireless frame is determined; the first wireless frame identifies that the sharing AP shares the transmission duration with the shared device according to the TXOP; The first wireless frame includes first identification information; the first identification information includes identification information of the shared device; the shared device includes a shared AP; The first wireless frame is sent to instruct the shared device to perform data interaction with the sharing AP or the STA associated with the shared device within the transmission duration.

2. The communication method according to claim 1, characterized in that: The first identification information is carried in a user information field User Info field of the first radio frame; The User Info field includes an AP MLD ID subfield and a Link ID subfield, and the first identification information identifies the identification information of the shared AP; the AP MLD ID subfield identifies the identification AP MLD ID of the multi-connection access point device to which the shared AP is attached, and the Link ID subfield identifies the link identification Link ID of the shared AP working link.

3. The communication method according to claim 1 or 2, characterized in that: The first radio frame further includes second identification information; The second identification information identifies: the type of TXS shared by the TXOP initiated by the sharing AP, and the type of TXS includes allocating the transmission duration to the shared AP.

4. The communication method according to claim 3, characterized in that: The second identification information is carried in a Triggered TXOP Sharing Mode subfield of the first radio frame; The Triggered TXOP Sharing Mode subfield is carried in the Common Info field of the first radio frame; The Triggered TXOP Sharing Mode subfield is set to a first parameter value, indicating that the sharing AP allocates the transmission duration to the shared AP.

5. The communication method according to claim 1, characterized in that: The method further comprises: Determine a second wireless frame; wherein the second wireless frame includes third identification information; the third identification information identifies: whether the neighbor AP of the shared AP supports inter-AP TXS; The second radio frame is sent.

6. The communication method according to claim 5, characterized in that: The third identification information is carried in a first Triggered TXOP Sharing Mode 3 Support identification bit of the second radio frame; The first Triggered TXOP Sharing Mode 3 Support flag is carried in the Reduced Neighbor Report element field of the second radio frame; The first Triggered TXOP Sharing Mode 3 Support flag is set to a third parameter value, indicating that the neighbor AP supports inter-AP TXS.

7. The communication method according to claim 6, characterized in that: The second wireless frame also includes fourth identification information; the fourth identification information identifies whether the shared AP supports inter-AP TXS.

8. The communication method according to claim 7, characterized in that: The fourth identification information is carried in the second Triggered TXOP Sharing Mode 3 Support identification bit of the second radio frame; The second Triggered TXOP Sharing Mode 3 Support flag is carried in an ultra high reliability capability element UHR Capabilities element field of the second radio frame; The second Triggered TXOP Sharing Mode 3 Support flag is set to a fourth parameter value, indicating that the shared AP supports inter-AP TXS.

9. The communication method according to claim 2, characterized in that: The User Info field also includes: Allocation Duration subfield, Resource Unit Allocation RU Allocation subfield subfield and at least one of the master-slave 160PS160 subfields.

10. The communication method according to claim 9, characterized in that: The shared device performs data interaction with the sharing AP or a STA associated with the shared device within the transmission duration, including: The shared device exchanges data with the sharing AP or the STA associated with the shared device within the transmission duration according to the transmission resources indicated by at least one of the Allocation Duration subfield, the RU Allocation subfield and the PS160 subfield.

11. A communication method, characterized in that: Applied to the first AP, including: Receive a first wireless frame; the first wireless frame indicates that the sharing AP shares the transmission duration with the shared device according to the obtained TXOP; The first wireless frame includes first identification information; the first identification information includes identification information of the shared device; the shared device includes a shared AP; Determine that the first identification information includes identification information of the first AP, and perform data interaction with the shared AP or a STA associated with the first AP within the transmission duration.

12. The communication method according to claim 11, characterized in that: The first identification information is carried in a User Info field of the first radio frame; The User Info field includes an AP MLD ID subfield and a Link ID subfield, and the first identification information identifies the identification information of the shared AP; wherein the AP MLD ID subfield identifies the identification AP MLD ID of the multi-connection access point device to which the shared AP is attached, and the Link ID subfield identifies the link identification Link ID of the working link of the shared AP; The User Info field includes an AID12 subfield, and the first identification information identifies identification information of the shared STA.

13. The communication method according to claim 12, characterized in that: The determining that the first identification information includes identification information of the first AP includes: In the case where the User Info field includes an AP MLD ID subfield and a Link ID subfield, Determine that the AP MLD ID subfield matches the identifier of the multi-connection access point device to which the first AP is attached, and the Link ID subfield matches the link identifier of the first AP working link, and determine that the first identification information includes identification information of the first AP.

14. The communication method according to claim 12, characterized in that: The User Info field also includes at least one of: an Allocation Duration subfield, an RU Allocation subfield, and a PS160 subfield.

15. The communication method according to claim 14, characterized in that: The performing data interaction with the shared AP or the STA associated with the first AP within the transmission duration includes: According to the transmission resources indicated by at least one of the Allocation Duration subfield, the RU Allocation subfield and the PS160 subfield, data interaction is performed with the shared AP or the STA associated with the first AP within the transmission duration.

16. An access point device, the access point device being a shared access point device, characterized in that: The shared access point device includes: A determination module, configured to determine a first wireless frame after obtaining a transmission opportunity TXOP; the first wireless frame identifies that the sharing AP shares a transmission duration with the shared device according to the TXOP; The first wireless frame includes first identification information; the first identification information includes identification information of the shared device; the shared device includes a shared AP; The sending module is used to send the first wireless frame to instruct the shared device to perform data interaction with the sharing AP or the STA associated with the shared device within the transmission duration.

17. An access point device, the access point device being a first AP, characterized in that: The first AP includes: A receiving module, configured to receive a first wireless frame; the first wireless frame indicates that the sharing AP shares the transmission duration with the shared device according to the obtained TXOP; The first wireless frame includes first identification information; the first identification information includes identification information of the shared device; the shared device includes a shared AP; A processing module is used to determine that the first identification information includes the identification information of the first AP, and to perform data interaction with the shared AP or the STA associated with the first AP within the transmission duration.

18. An access point device, characterized in that: include: one or more processors; The access point device is used to execute the communication method according to any one of claims 1 to 10 or claims 11 to 15.

19. A communication system, characterized in that: It comprises a sharing access point device and a shared access point device; wherein the sharing access point device is configured to implement the communication method according to any one of claims 1 to 10, and the shared access point device is configured to implement the communication method according to any one of claims 11 to 15.

20. A storage medium storing instructions, characterized in that: When the instruction is executed on a communication device, the communication device is caused to execute the communication method according to any one of claims 1 to 10, or execute the communication method according to any one of claims 11 to 15.

Images