Communication method, site equipment and communication system

Abstract

The embodiment of the invention relates to a communication method, station equipment and a communication system. The communication method is applied to a first station device, and comprises the following steps: determining a channel direct connection establishment request TDLS Setup Request frame; the TDLS Setup Request frame comprises first identification information, and the first identification information identifies the support capability information of the first station equipment to a peer-to-peer transmission opportunity sharing (P2P TXS) mode; the support capability information comprises whether the first site equipment supports a P2P transmission opportunity sharing (TXS) mode or not and at least one of the types of the P2P TXS mode supported by the first site equipment; and the TDLS Setup Request frame is sent by the data transmission module and the TDLS Setup Request frame. According to the method provided by the embodiment of the invention, the sudden low-delay service can be effectively dealt with, the low-delay transmission mechanism is further improved, and the transmission delay of the low-delay communication service is reduced.

Description

Communication method, site equipment and communication system Technical Field

[0001] The present disclosure relates to the field of communication technology, and in particular to a communication method, site equipment, and a communication system. Background Art

[0002] Currently, Wi-Fi technology research focuses on Ultra High Reliability (UHR), with the goal of improving the reliability of Wireless Local Area Networks (WLAN) connections, reducing latency, improving manageability, increasing throughput at different signal-to-noise ratio (SNR) levels, and reducing device-level power consumption.

[0003] In Ultra High Resolution (UHR), low-latency service transmission mechanisms will be further enhanced to support multi-connection scenarios. To enhance throughput at varying signal-to-noise ratio (SNR) levels, transmission opportunity (TXOP) sharing may be adopted in Ultra High Resolution (UHR). Therefore, the TXOP sharing mechanism needs to be further refined to meet the transmission requirements of Ultra High Resolution (UHR).

[0004] Summary of the Invention

[0005] The embodiments of the present disclosure provide a communication method, a station device, and a communication system to further improve the TXOP sharing mechanism to meet the transmission requirements of UHR.

[0006] In one aspect, an embodiment of the present disclosure provides a communication method, applied to a first site device, the method comprising:

[0007] Determine a channel direct connection establishment request TDLS Setup Request frame; the TDLS Setup Request frame includes first identification information, the first identification information identifying the first site device's support capability information for the point-to-point transmission opportunity sharing (P2P TXS) mode; the support capability information includes: whether the first site device supports the P2P transmission opportunity sharing (TXS) mode, and at least one of a type of P2P TXS mode supported by the first site device;

[0008] Send the TDLS Setup Request frame.

[0009] On the other hand, an embodiment of the present disclosure further provides a communication method, applied to a second site device, the method comprising:

[0010] receiving a TDLS Setup Request frame; the TDLS Setup Request frame including first identification information, where the first identification information identifies the first site device's support capability information for the P2P TXS mode; the support capability information including: whether the first site device supports the P2P transmission opportunity sharing TXS mode, and at least one type of the P2P TXS mode supported by the first site device;

[0011] Determine a TDLS Setup Response frame; the TDLS Setup Response frame includes second identification information, where the second identification information identifies support capability information of the second site device for the P2P TXS mode; the support capability information includes: whether the second site device supports the P2P transmission opportunity sharing TXS mode, and at least one type of the P2P TXS mode supported by the second site device;

[0012] Send the TDLS Setup Response frame.

[0013] On the other hand, an embodiment of the present disclosure further provides a site device, where the site device is a first site device, and the first site device includes:

[0014] A first determining module is configured to determine a Tunnel Direct Connection Setup Request (TDLS) Setup Request frame; the TDLS Setup Request frame includes first identification information, where the first identification information identifies information about the first site device's support capability for the P2P TXS mode; the support capability information includes at least one of: whether the first site device supports the P2P transmission opportunity sharing (TXS) mode and a type of P2P TXS mode supported by the first site device;

[0015] The first sending module is configured to send the TDLS Setup Request frame.

[0016] On the other hand, an embodiment of the present disclosure further provides a site device, where the site device is a second site device, and the second site device includes:

[0017] A first receiving module is configured to receive a TDLS Setup Request frame; the TDLS Setup Request frame includes first identification information, where the first identification information identifies information about the first site device's support capability for the P2P TXS mode; the support capability information includes at least one of: whether the first site device supports the P2P transmission opportunity sharing TXS mode and a type of P2P TXS mode supported by the first site device;

[0018] A second determining module is configured to determine a TDLS Setup Response frame; the TDLS Setup Response frame includes second identification information, where the second identification information identifies support capability information of the second site device for the P2P TXS mode; the support capability information includes at least one of: whether the second site device supports the P2P transmission opportunity sharing TXS mode and a type of P2P TXS mode supported by the second site device;

[0019] The second sending module is used to send the TDLS Setup Response frame.

[0020] On the other hand, an embodiment of the present disclosure further provides a site device, where the site device is a first site device, including:

[0021] one or more processors;

[0022] The first site device is used to execute the communication method described in the embodiment of the present disclosure.

[0023] On the other hand, an embodiment of the present disclosure further provides a site device, where the site device is a second site device, including:

[0024] one or more processors;

[0025] The second site device is used to execute the communication method described in the embodiment of the present disclosure.

[0026] An embodiment of the present disclosure further provides a communication system, including a first site device and a second site device; wherein the first site device is configured to implement the communication method described in the embodiment of the present disclosure, and the second site device is configured to implement the communication method described in the embodiment of the present disclosure.

[0027] The embodiment of the present disclosure further 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 embodiment of the present disclosure.

[0028] In the disclosed embodiments, during the TDLS link establishment process, a TDLS device notifies the other party of its support for the P2P TXS mode through first identification information. Later in the communication process, if a bursty / temporary low-latency communication service is encountered by the TXOP responder (the second site device), and the TXOP holder (the first site device) supports inter-site transmission opportunity sharing and has the ability to share with other devices, the TXOP responder can send a transmission opportunity sharing request to obtain a transmission opportunity. The methods provided in the disclosed embodiments can effectively address bursty low-latency services, further improve the low-latency transmission mechanism, and reduce the transmission delay of low-latency communication services.

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

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

[0031] FIG1 is an exemplary schematic diagram of the architecture of a communication system provided by an embodiment of the present disclosure;

[0032] FIG2 is one of exemplary interaction diagrams of the method provided in an embodiment of the present disclosure;

[0033] FIG3 is a second exemplary interaction diagram of the method provided in an embodiment of the present disclosure;

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

[0035] FIG5 is a second flow chart of the communication method provided in an embodiment of the present disclosure;

[0036] FIG6 is a schematic structural diagram of a first site device proposed in an embodiment of the present disclosure;

[0037] FIG7 is a schematic structural diagram of a second site device proposed in an embodiment of the present disclosure;

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

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

[0040] The embodiments of the present disclosure provide a communication method, a station device, and a communication system.

[0041] In a first aspect, an embodiment of the present disclosure provides a communication method, the method comprising:

[0042] Determine a channel direct connection establishment request TDLS Setup Request frame; the TDLS Setup Request frame includes first identification information, the first identification information identifying the first site device's support capability information for the point-to-point transmission opportunity sharing (P2P TXS) mode; the support capability information includes: whether the first site device supports the P2P transmission opportunity sharing (TXS) mode, and at least one of a type of P2P TXS mode supported by the first site device;

[0043] Send the TDLS Setup Request frame.

[0044] In the above embodiment, during the TDLS link establishment process, the TDLS device notifies the other party of its support for the P2P TXS mode through first identification information. Later in the communication process, if the TXOP responder (the second site device) encounters bursty / temporary low-latency communication traffic and the TXOP holder (the first site device) supports inter-site transmission opportunity sharing and has the ability to share with other devices, the TXOP responder can send a transmission opportunity sharing request to obtain a transmission opportunity.

[0045] In conjunction with some embodiments of the first aspect, in some embodiments, the TDLS Setup Request frame includes an ultra-high reliability UHR capability element

[0046] The first identification information is carried in the P2P TXOP Sharing mode support Mode Support identification field of the UHR capability element.

[0047] In the above embodiment, during the process of establishing a TDLS link, the TDLS device notifies the other party of its own capability information supporting the P2P TXS mode through the first identification information.

[0048] In conjunction with some embodiments of the first aspect, in some embodiments, the method includes at least one of the following:

[0049] The first identification information is set to a first parameter value, indicating that the first site device supports the ability to initiate a TXS to a TDLS device and supports the ability to respond to a TXS initiated by other TDLS devices;

[0050] The first identification information is set to a second parameter value, indicating that the first site device supports the ability to initiate a TXS to a TDLS device, and does not support the ability to respond to a TXS initiated by other TDLS devices;

[0051] The first identification information is set to a third parameter value, indicating that the first site device does not support the capability of initiating a TXS to a TDLS device, but supports the capability of responding to a TXS initiated by other TDLS devices;

[0052] The first identification information is set to a fourth parameter value, indicating that the first site device does not support the capability of initiating a TXS to a TDLS device, and does not support the capability of responding to a TXS initiated by other TDLS devices.

[0053] In the above embodiment, a specific identification form of the first station device's support capability information for the P2P TXS mode is provided to improve the TXOP sharing mechanism.

[0054] In combination with some embodiments of the first aspect, in some embodiments, after sending the TDLS Setup Request frame, the method further includes:

[0055] receiving a direct connection establishment response TDLS Setup Response frame sent by the second site device;

[0056] The TDLS Setup Response frame includes second identification information, where the second identification information identifies the second site device's support capability information for the P2P TXS mode; the support capability information includes: whether the second site device supports the P2P transmission opportunity sharing TXS mode, and at least one of the types of P2P TXS modes supported by the second site device.

[0057] In the above embodiment, the first site device obtains the second site device's support capability information for the P2P TXS mode through the second identification information in the TDLS Setup Response frame, for subsequent implementation of the TXS mechanism.

[0058] In combination with some embodiments of the first aspect, in some embodiments, after receiving the TDLS Setup Response frame sent by the second site device, the method further includes:

[0059] In the first TXOP, data is sent to the second site device; wherein the second identification information indicates that the second site device does not support the ability to respond to TXS initiated by other TDLS devices, or the first identification information indicates that the first site device does not support the ability to initiate TXS to the TDLS device;

[0060] Receive a first TXOP sharing request sent by the second site device; wherein the first TXOP sharing request is used to request the first site device to share part of the transmission time within the first TXOP for the second site device to perform low-latency service transmission; wherein the second identification information identifies that the second site device supports the ability to respond to TXS initiated by other TDLS devices, and the first identification information identifies that the first site device supports the ability to initiate TXS to the TDLS device;

[0061] or

[0062] Send a second TXOP sharing request to the second site device; wherein the second TXOP sharing request is used to request the second site device to share part of the transmission time within the second TXOP for the first site device to perform low-latency service transmission; wherein the first identification information identifies that the first site device supports the ability to respond to TXS initiated by other TDLS devices, and the second identification information identifies that the second site device supports the ability to initiate TXS to the TDLS device.

[0063] In the above embodiment, the TXOP sharing mechanism is executed according to the specific types of the first identification information and the second identification information to reduce the transmission delay of the low-latency communication service.

[0064] In combination with some embodiments of the first aspect, in some embodiments, after receiving the first TXOP sharing request sent by the second site device, the method further includes:

[0065] In response to the first TXOP sharing request, the first site device sends a first multi-user request to send transmission opportunity sharing trigger MU-RTS TXS Trigger frame to the second site device; the first MU-RTS TXS Trigger frame includes a User Info field, and the User Info field includes device identification information of the second site device.

[0066] In the above embodiment, TXOP sharing is triggered by the MU-RTS TXS Trigger frame.

[0067] In combination with some embodiments of the first aspect, in some embodiments, during the transmission time shared by the first site device to the second site device, the first site device sends data only when it receives a data sending request from the second site device and responds to the data sending request.

[0068] In the above embodiment, the behavior of the first site device is specified within the transmission time shared by the first site device to prevent it from occupying the channel during the transmission time shared with other devices, thereby affecting the transmission of low-latency services.

[0069] In combination with some embodiments of the first aspect, in some embodiments, after sending the second TXOP sharing request to the second site device, the method further includes:

[0070] Receive a second MU-RTS TXS Trigger frame sent by the second site device; the second MU-RTS TXS Trigger frame includes a user information field User Info field, and the User Info field includes device identification information of the first site device.

[0071] In the above embodiment, whether the second station device allocates transmission time to the first station device is determined according to whether the User Info field of the second MU-RTS TXS Trigger frame includes the identification information of the first station device.

[0072] In a second aspect, an embodiment of the present disclosure provides a communication method, applied to a second site device, the method including:

[0073] receiving a TDLS Setup Request frame; the TDLS Setup Request frame including first identification information, where the first identification information identifies the first site device's support capability information for the P2P TXS mode; the support capability information including: whether the first site device supports the P2P transmission opportunity sharing TXS mode, and at least one type of the P2P TXS mode supported by the first site device;

[0074] Determine a TDLS Setup Response frame; the TDLS Setup Response frame includes second identification information, where the second identification information identifies support capability information of the second site device for the P2P TXS mode; the support capability information includes: whether the second site device supports the P2P transmission opportunity sharing TXS mode, and at least one type of the P2P TXS mode supported by the second site device;

[0075] Send the TDLS Setup Response frame.

[0076] In conjunction with some embodiments of the second aspect, in some embodiments, the TDLS Setup Request frame includes a UHR capability element;

[0077] The second identification information is carried in the P2P TXOP Sharing Mode Support identification field of the UHR capability element.

[0078] In conjunction with some embodiments of the second aspect, in some embodiments, the method includes at least one of the following:

[0079] The second identification information is set to the first parameter value, indicating that the second site device supports the ability to initiate a TXS to the TDLS device and supports the ability to respond to a TXS initiated by other TDLS devices;

[0080] The second identification information is set to a second parameter value, indicating that the second site device supports the ability to initiate a TXS to a TDLS device, and does not support the ability to respond to a TXS initiated by other TDLS devices;

[0081] The second identification information is set to a third parameter value, indicating that the second site device does not support the capability of initiating a TXS to a TDLS device, but supports the capability of responding to a TXS initiated by other TDLS devices;

[0082] The second identification information is set to a fourth parameter value, indicating that the second site device does not support the ability to initiate a TXS to a TDLS device, and does not support the ability to respond to a TXS initiated by other TDLS devices;

[0083] In conjunction with some embodiments of the second aspect, in some embodiments, after receiving the TDLS Setup Request frame, the method further includes:

[0084] In the first TXOP, maintaining a receiving state, receiving data sent by the first site device; wherein the second identification information indicates that the second site device does not support the ability to respond to TXS initiated by other TDLS devices, or the first identification information indicates that the first site device does not support the ability to initiate TXS to the TDLS device;

[0085] Sending a TXOP sharing request to the first site device; wherein the TXOP sharing request is used to request the first site device to share part of the transmission time within the first TXOP for the second site device to perform low-latency service transmission; wherein the second identification information identifies the second site device's ability to support responding to TXS initiated by other TDLS devices, and the first identification information identifies the first site device's ability to support initiating TXS to the TDLS device;

[0086] or

[0087] Receive a second TXOP sharing request sent by the first site device; wherein the second TXOP sharing request is used to request the second site device to share part of the transmission time within the second TXOP for the first site device to perform low-latency service transmission; wherein the first identification information identifies that the first site device supports the ability to respond to TXS initiated by other TDLS devices, and the second identification information identifies that the second site device supports the ability to initiate TXS to the TDLS device.

[0088] In conjunction with some embodiments of the second aspect, in some embodiments, after sending the TXOP sharing request to the first site device, the method further includes:

[0089] A first MU-RTS TXS Trigger frame sent by the first site device to the second site device is received; the first MU-RTS TXS Trigger frame includes a User Info field.

[0090] In conjunction with some embodiments of the second aspect, in some embodiments, the User Info field includes device identification information of the second site device, and transmits the low-latency service within the transmission time indicated by the MU-RTS TXS Trigger frame;

[0091] or

[0092] The User Info field does not include the device identification information of the second site device. In the first TXOP, the receiving state is maintained to receive data sent by the first site device.

[0093] In conjunction with some embodiments of the second aspect, in some embodiments, after receiving the second TXOP sharing request sent by the first site device, the method further includes:

[0094] In response to the second TXOP sharing request, a second MU-RTS TXS Trigger frame is sent to the first site device; the second MU-RTS TXS Trigger frame includes a User Info field, and the User Info field includes device identification information of the first site device.

[0095] In combination with some embodiments of the second aspect, in some embodiments, within the transmission time shared by the second site device to the first site device, the second site device sends data only when it receives a data sending request from the first site device and responds to the data sending request.

[0096] In a third aspect, an embodiment of the present disclosure further provides a site device, which is a first site device. The first site device includes at least one of a determination module and a sending module; wherein the first site device is used to execute an optional implementation method of the first aspect.

[0097] In a fourth aspect, an embodiment of the present disclosure further provides a site device, which is a second site device and includes: a first receiving module; wherein the second site device is used to execute the optional implementation of the second aspect.

[0098] In a fifth aspect, an embodiment of the present disclosure further provides a site device, where the site device is a first site device, including:

[0099] one or more processors;

[0100] The first site device is used to execute an optional implementation of the first aspect.

[0101] In a sixth aspect, an embodiment of the present disclosure further provides a site device, where the site device is a second site device, including:

[0102] one or more processors;

[0103] The second site device is used to execute an optional implementation of the second aspect.

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

[0105] In an eighth 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 the optional implementation methods described in the first and second aspects.

[0106] In a ninth 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 of the first and second aspects.

[0107] In a tenth 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 and second aspects.

[0108] In an eleventh 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 and second aspects above.

[0109] It is understandable that the first site device, the second site device, the communication system, the storage medium, the program product, the computer program, the chip, or the chip system described above are all used to perform the methods proposed in the embodiments of the present disclosure. Therefore, the beneficial effects that can be achieved can be referred to the beneficial effects of the corresponding methods and will not be repeated here.

[0110] The embodiments of the present disclosure provide a communication method, a station 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.

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

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

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

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

[0115] In some embodiments, the terms "at least one," "one or more," "a plurality of," "multiple," etc. may be used interchangeably.

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

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

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

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

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

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

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

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

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

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

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

[0127] As shown in FIG1 , a communication system 100 includes a station device (STA) 101 and an access point device (AP) 102 .

[0128] In some embodiments, the site device 101 includes, for example, a wireless communication chip, a wireless sensor, or a wireless communication terminal that supports WiFi 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 WiFi communication, a car with WiFi communication, a smart car, a tablet computer, a computer with wireless transceiver capabilities, a virtual reality (VR) terminal device, an augmented reality (AR) terminal device, a wireless terminal device used in industrial control, a wireless terminal device used in self-driving, a wireless terminal device used in remote medical surgery, a wireless terminal device used in a smart grid, a wireless terminal device used in transportation safety, a wireless terminal device used in a smart city, and a wireless terminal device used in a smart home.

[0129] Specifically, the station device 101 may be a terminal device or network device equipped with a wireless fidelity (WiFi) chip. Optionally, the station device 101 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.

[0130] In some embodiments, the access point device 102 can be an access point for a mobile terminal 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.

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

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

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

[0134] The various embodiments of the present disclosure can be applied to wireless local area networks (WLANs), such as those using the 802.11 series of protocols. In a WLAN, a Basic Service Set (BSS) is a fundamental component of a WLAN. A BSS network consists of station devices with some association 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 dedicated to managing the BSS, called an access point, and all other STAs in the network are associated with it. Other stations in the BSS network that are not the central station are called terminals, also called non-AP STAs. Terminals 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, and other factors, a STA cannot detect other STAs that are farther away from it, and the two STAs are each other's hidden nodes.

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

[0136] In step 201, a first site device determines a TDLS Setup Request frame; the TDLS Setup Request frame includes first identification information, where the first identification information identifies the first site device's support capability information for the P2P TXS mode; the support capability information includes: whether the first site device supports the P2P transmission opportunity sharing TXS mode, and at least one of the types of P2P TXS modes supported by the first site device.

[0137] In WLAN communication, reducing the transmission delay of low-latency communication services is one of the main research goals. For deterministic or periodic low-latency services, the Restricted-Target Wake Time (R-TWT) mechanism can effectively ensure the timely transmission of low-latency communication services. However, when the AP or STA faces some temporary or sudden low-latency services, the R-TWT mechanism is no longer applicable. Therefore, in the embodiment of the present disclosure, during the process of establishing a Tunneled Direct Link Setup (TDLS) link between a first site device and a second site device, the first site device determines a TDLS Setup Request frame and carries first identification information in the TDLS Setup Request frame. The first identification information identifies the first site device's support capability information for the P2P TXS mode, thereby realizing P2P TXS mode support capability interaction with the TDLS device.

[0138] Two TDLS devices that have established a TDLS link can communicate directly over the TDLS link. P2P TXS mode refers to the point-to-point (P2P) transmission opportunity sharing (TXS) mode. For example, a TXOP holder can trigger the TXS process to allocate part of its reserved TXOP time to other devices. These other devices then use the allocated TXOP to promptly send low-latency services to the receiving device.

[0139] The first site device's support capability information for the P2P TXS mode includes at least one of the following:

[0140] Whether the first site device supports the P2P transmission opportunity sharing (TXS) mode, and the type of the P2P TXS mode supported by the first site device.

[0141] Among them, whether the first site device supports the P2P transmission opportunity sharing TXS mode, that is, whether the first site device supports the P2P TXS mode; the type of P2P TXS mode supported by the first site device, for example, whether the first site device supports actively initiating the P2P TXS mode, or the first site device supports responding to the P2P TXS mode initiated by other devices.

[0142] Typically, within a TXOP, only the TXOP holder can actively send data; other devices can only receive data or send response frames (e.g., ACK frames) for the data they receive. For example, when the first station device is a STA and, as the TXOP holder, is sending data (uplink data or P2P data) to a second station device (the AP that establishes an initial association with the STA, or the STA that establishes a P2P link with the STA), if the second station device has temporary / burst low-latency communication services to transmit to other communication devices, it can use the transmission time allocated to it by the first station device through the P2P TXS mode to transmit the temporary / burst low-latency communication services, thereby ensuring the transmission of low-latency services. This eliminates the need for the second station device to wait until the TXOP held by the first station device ends before it has the opportunity to transmit the temporary / burst low-latency communication services, resulting in higher transmission latency.

[0143] In the disclosed embodiments, during the TDLS link establishment process, a TDLS device notifies the other party of its support for the P2P TXS mode through first identification information. Later in the communication process, if a bursty / temporary low-latency communication service is encountered by the TXOP responder (the second site device), and the TXOP holder (the first site device) supports inter-site transmission opportunity sharing and has the ability to share with other devices, the TXOP responder can send a transmission opportunity sharing request to obtain a transmission opportunity. The methods provided in the disclosed embodiments can effectively address bursty low-latency services, further improve the low-latency transmission mechanism, and reduce the transmission delay of low-latency communication services.

[0144] Step 202: The first site device sends the TDLS Setup Request frame.

[0145] The first site device sends the TDLS Setup Request frame, and notifies the other party of its own support capability information for the P2P TXS mode by carrying the first identification information in the TDLS Setup Request frame.

[0146] In some embodiments, the TDLS Setup Request frame includes a UHR Capabilities element;

[0147] The first identification information is carried in a P2P TXOP Sharing mode support (Mode Support) identification field of the UHR capability element.

[0148] The first identification information is included in the UHR capability element.

[0149] For example, the first identification information may be carried in the P2P TXOP Sharing Mode Support identification field, and is used to identify whether the device sending the TDLS Setup Request frame supports the P2P TXS mode and the type of support.

[0150] In some embodiments, the first identification information includes at least one of the following situations 1 to 4:

[0151] In case one, the first identification information is set to the first parameter value, indicating that the first site device supports the ability to initiate TXS to the TDLS device, and supports the ability to respond to TXS initiated by other TDLS devices; for example, when the first parameter value is set to 3, it indicates that the device sending the TDLS Setup Request frame (the first site device) has the ability to initiate TXS to other TDLS devices, and has the ability to respond to TXS initiated by other TDLS devices.

[0152] In case two, the first identification information is set to the second parameter value, indicating that the first site device supports the ability to initiate TXS to the TDLS device, and does not support the ability to respond to TXS initiated by other TDLS devices; for example, when the second parameter value is set to 2, it indicates that the device (first site device) sending the TDLS Setup Request frame has the ability to initiate TXS to other TDLS devices, but does not have the ability to respond to TXS initiated by other TDLS devices.

[0153] Case three, the first identification information is set to the third parameter value, indicating that the first site device does not support the ability to initiate TXS to the TDLS device, and supports the ability to respond to TXS initiated by other TDLS devices; for example, when the third parameter value is set to 1, it indicates that the device (first site device) sending the TDLS Setup Request frame does not have the ability to initiate TXS to other TDLS devices, but has the ability to respond to TXS initiated by other TDLS devices.

[0154] Case four, the first identification information is set to the fourth parameter value, indicating that the first site device does not support the ability to initiate TXS to the TDLS device, and does not support the ability to respond to TXS initiated by other TDLS devices; for example, when the fourth parameter value is set to 0, it indicates that the device (first site device) sending the TDLS Setup Request frame does not have the ability to initiate TXS to other TDLS devices, and does not have the ability to respond to TXS initiated by other TDLS devices.

[0155] Step 203: The second site device sends a TDLS Setup Response frame.

[0156] The TDLS Setup Response frame includes second identification information, where the second identification information identifies the second site device's support capability information for the P2P TXS mode; the support capability information includes: whether the second site device supports the P2P transmission opportunity sharing TXS mode, and at least one of the types of P2P TXS modes supported by the second site device.

[0157] The TDLS Setup Response frame is used to respond to the TDLS Setup Request frame. After receiving the TDLS Setup Request frame from the first site device, the second site device sends a TDLS Setup Response frame to the first site device. The TDLS Setup Response frame includes second identification information, which is used to identify whether the second site device supports P2P TXS mode and the specific type it supports.

[0158] Optionally, the format of the second identification information is the same as the second identification information in the TDLS Setup Request frame, and the TDLS Setup Response frame includes a UHR Capabilities element (UHR Capabilities element);

[0159] The second identification information is carried in the P2P TXOP Sharing Mode Support identification field of the UHR capability element.

[0160] The second identification information is included in the UHR capability element.

[0161] For example, the second identification information may be carried in the P2P TXOP Sharing Mode Support identification field, and is used to identify whether the device sending the TDLS Setup Response frame supports the P2P TXS mode and the type of mode it supports.

[0162] In some embodiments, the second identification information includes at least one of the following cases 5 to 8:

[0163] Case five, the second identification information is set to the first parameter value, indicating that the second site device supports the ability to initiate TXS to the TDLS device, and supports the ability to respond to TXS initiated by other TDLS devices; for example, when the second parameter value is set to 3, it indicates that the device sending the TDLS Setup Response frame (the second site device) has the ability to initiate TXS to other TDLS devices, and has the ability to respond to TXS initiated by other TDLS devices.

[0164] Case six, the second identification information is set to the second parameter value, indicating that the second site device supports the ability to initiate TXS to the TDLS device, and does not support the ability to respond to TXS initiated by other TDLS devices; for example, when the second parameter value is set to 2, it indicates that the device (second site device) sending the TDLS Setup Response frame has the ability to initiate TXS to other TDLS devices, but does not have the ability to respond to TXS initiated by other TDLS devices.

[0165] Case seven, the second identification information is set to the third parameter value, indicating that the second site device does not support the ability to initiate TXS to the TDLS device, and supports the ability to respond to TXS initiated by other TDLS devices; for example, when the third parameter value is set to 1, it indicates that the device (second site device) sending the TDLS Setup Response frame does not have the ability to initiate TXS to other TDLS devices, but has the ability to respond to TXS initiated by other TDLS devices.

[0166] Case eight, the second identification information is set to the fourth parameter value, indicating that the second site device does not support the ability to initiate TXS to the TDLS device, and does not support the ability to respond to TXS initiated by other TDLS devices; for example, when the fourth parameter value is set to 0, it indicates that the device (second site device) sending the TDLS Setup Response frame does not have the ability to initiate TXS to other TDLS devices, and does not have the ability to respond to TXS initiated by other TDLS devices.

[0167] Step 204: The first site device receives a TDLS Setup Response frame sent by the second site device.

[0168] After receiving the TDLS Setup Response frame, the first site device determines the second site device's capability to support the P2P TXS mode based on the second identification information. If the first site device and the second site device successfully establish a TDLS link, and the first site device holds the first TXOP and the second site device, acting as the TXOP responder, receives data from the first site device, and the second site device has a temporary / burst low-latency service to transmit, then steps 205 to 207 are performed based on the specific capabilities of the first and second identification information.

[0169] Step 205: Within the first TXOP, the first site device sends data to the second site device; wherein the second identification information indicates that the second site device does not support the ability to respond to TXS initiated by other TDLS devices, or the first identification information indicates that the first site device does not support the ability to initiate TXS to the TDLS device.

[0170] The second identification information indicates that the second site device does not support the ability to respond to TXS initiated by other TDLS devices. For example, the second identification information is set to 0 or 2;

[0171] Or the first identification information indicates that the first site device does not support the capability of initiating TXS to the TDLS device, and the second identification information is set to 1;

[0172] In any of the above situations, within the first TXOP, the first site device sends data to the second site device, and the second site device continues to maintain a receiving state within the first TXOP to receive the data sent by the first site device.

[0173] Step 206: The first site device receives a first TXOP sharing request sent by the second site device; wherein the first TXOP sharing request is used to request the first site device to share part of the transmission time within the first TXOP for the second site device to perform low-latency service transmission; wherein the second identification information identifies that the second site device supports the ability to respond to TXS initiated by other TDLS devices, and the first identification information identifies that the first site device supports the ability to initiate TXS to the TDLS device;

[0174] The second identification information identifies that the second site device supports the ability to respond to TXS initiated by other TDLS devices, and the first identification information identifies that the first site device supports the ability to initiate TXS to the TDLS device. For example, the second identification information is set to 1 (or 3) and the first identification information is set to 2 (or 3). Then, within the first TXOP, when the second site device sends a first TXOP sharing request (such as an ACK or BlockAck frame) to the first site device, it requests the first site device to share part of the first TXOP for low-latency communication service transmission.

[0175] Step 207: Send a second TXOP sharing request to the second site device; wherein the second TXOP sharing request is used to request the second site device to share part of the transmission time within the second TXOP for the first site device to perform low-latency service transmission; wherein the first identification information identifies the ability of the first site device to support responding to TXS initiated by other TDLS devices, and the second identification information identifies the ability of the second site device to support initiating TXS to the TDLS device.

[0176] Among them, the first identification information identifies that the first site device supports the ability to respond to TXS initiated by other TDLS devices, and the second identification information identifies that the second site device supports the ability to initiate TXS to the TDLS device; for example, the first identification information is set to 1 (or 3), and the second identification information is set to 2 (or 3), then in the second TXOP (the second site device is the TXOP holder), when the first site device sends a second TXOP sharing request (such as an ACK or BlockAck frame) to the second site device, it requests the second site device to share part of the second TXOP for low-latency communication service transmission.

[0177] In some embodiments, after step 206, the method further includes:

[0178] Step 208: In response to the first TXOP sharing request, the first site device sends a first multi-user request to send transmission opportunity sharing trigger (Multi User TXOP sharing Trigger, MU-RTS TXS) frame to the second site device; the first MU-RTS TXS Trigger frame includes a User Info field, and the User Info field includes device identification information of the second site device.

[0179] After the first site device receives the first TXOP sharing request sent by the second site device, the first site device sends a MU-RTS TXS Trigger frame to share part of the transmission time of the first TXOP with the second site device. The MU-RTS TXS Trigger frame includes a User Info field, and the User Info field includes an identifier of the target second site device.

[0180] Optionally, when the second site device is not an affiliated STA of a non-AP MLD, the identifier of the second site device may be a media access control layer (MAC) address of the second site device; when the second site device is an affiliated STA of a non-AP MLD, the identifier of the second site device is set to the MAC address of the MLD to which the second site device is affiliated.

[0181] Correspondingly, the User Info field of the first MU-RTS TXS Trigger frame includes the device identification information of the second site device, and transmits the low-latency service within the transmission time indicated by the MU-RTS TXS Trigger frame, that is, the identifier of the User Info field matches the second site device, and the second site device uses the transmission time allocated by the first site device to transmit its cached temporary / burst low-latency communication service;

[0182] or

[0183] The User Info field does not include the device identification information of the second site device. Within the first TXOP, the receiving state is maintained to receive data sent by the first site device. That is, the identifier of the User Info field does not match that of the second site device. The second site device does not respond and maintains the receiving state.

[0184] In some embodiments, after step 207, the method further includes:

[0185] Step 209: In response to the second TXOP sharing request, the second site device sends a second MU-RTS TXS Trigger frame to the first site device; the second MU-RTS TXS Trigger frame includes a User Info field, and the User Info field includes device identification information of the first site device.

[0186] After the second site device receives the second TXOP sharing request sent by the first site device, the second site device sends a MU-RTS TXS Trigger frame to share part of the transmission time of the second TXOP (the TXOP held by the second site device) with the first site device. The MU-RTS TXS Trigger frame includes a User Info field, and the User Info field includes an identifier of the target second site device.

[0187] Optionally, when the first site device is not an affiliated STA of a non-AP MLD, the identifier of the first site device may be the MAC address of the first site device; when the first site device is an affiliated STA of a non-AP MLD, the identifier of the first site device is set to the MAC address of the MLD to which the first site device is affiliated.

[0188] In some embodiments, during the transmission time shared by the first site device to the second site device, the first site device sends data only when receiving a data sending request from the second site device and responding to the data sending request.

[0189] Among them, during the transmission time shared by the first site device to the second site device, the first site device can send data unless the second site device sends data to the first site device and requests a response; in other cases, the first site device does not send data, for example, setting its network allocation vector (NAV) to a busy state.

[0190] As an example, see Figure 3, which illustrates a specific application process of an embodiment of the present disclosure, in which STA1 serves as the first station device and the TXOP holder, and STA2 serves as the second station device. Figure 3 uses step 206 as an example for illustration. Steps 205 and 207 are similar and are not further described here.

[0191] Step 301: STA1 sends a TDLS Setup Request frame to STA2. The TDLS Setup Request frame includes first identification information indicating STA1's support capability for the P2P TXS mode. The first identification information indicates that the first station device supports the capability of initiating TXS to the TDLS device.

[0192] In step 302, STA2 sends a TDLS Setup Response frame to STA1. The TDLS Setup Response frame includes second identification information indicating STA2's ability to support the P2P TXS mode. The second identification information indicates the second station device's ability to respond to TXS initiated by other TDLS devices.

[0193] Step 303: When the first TXOP arrives, STA1, as the TXOP holder, sends an RTS frame to STA2.

[0194] In step 304, STA2, as the TXOP Responder, replies with a CTS frame to STA1.

[0195] Step 305: STA1 and STA2 transmit non-low-latency service data frames (data).

[0196] Step 306: STA2 transmits a low-latency service to other devices.

[0197] For example, the second site device has temporary / burst low-latency communication services to transmit to other communication devices.

[0198] In step 307, STA2 sends a first TXOP sharing request (BA frame in FIG3 ) to STA1, requesting STA1 to share part of the transmission time in the first TXOP for STA2 to perform low-latency service transmission.

[0199] In step 308 , STA1 responds to the first TXOP sharing request, and the first station device sends a first MU-RTS TXS Trigger frame to STA2, sharing the transmission time with STA2 through the first MU-RTS TXS Trigger frame.

[0200] In step 309, STA2 sends an RTS frame to other devices (receiving ends of temporary / burst low-latency communication services, which may be APs or STAs).

[0201] As shown in FIG3 , at step 309 when the first TXOP arrives, the NAV of the other device is set to a busy state; and at step 310 , the other device resets its NAV to access the channel to receive the low-latency communication service.

[0202] In step 311, the other device sends a CTS frame to STA2.

[0203] Step 312: STA2 transmits low-latency service data frames (data) with the other devices.

[0204] Step 313: Other devices reply to STA2 with a BA frame to confirm receipt of the low-latency service data.

[0205] The low-latency service data transmission between STA2 and the other devices is completed. As shown in step 313, the first TXOP may still have TXOP time left, so non-low-latency service data frames can continue to be transmitted between STA1 and STA2. The embodiments of the present disclosure will not be repeated here.

[0206] 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", "codepoint", "bit", "data", "program", and "chip" can be used interchangeably.

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

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

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

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

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

[0212] 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 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, step 206 can be implemented as an independent embodiment, and step 207 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 206 and step 208 can be implemented as an independent embodiment, and the combination of step 207 and step 209 can be implemented as an independent embodiment, but are not limited thereto.

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

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

[0215] As shown in FIG4 , the above method may be applied to the first site device 101, and the above method includes:

[0216] Step 401: Determine a Tunnel Direct Connection Setup Request (TDLS) Setup Request frame; the TDLS Setup Request frame includes first identification information, where the first identification information identifies the first site device's support capability for the peer-to-peer transmission opportunity sharing (P2P TXS) mode; the support capability information includes at least one of: whether the first site device supports the P2P transmission opportunity sharing (TXS) mode and the type of P2P TXS mode supported by the first site device;

[0217] Step 402: Send the TDLS Setup Request frame.

[0218] Optionally, in the embodiment of the present disclosure, the TDLS Setup Request frame includes an ultra-high reliability UHR capability element

[0219] The first identification information is carried in the P2P TXOP Sharing mode support Mode Support identification field of the UHR capability element.

[0220] Optionally, in an embodiment of the present disclosure, the method includes at least one of the following:

[0221] The first identification information is set to a first parameter value, indicating that the first site device supports the ability to initiate a TXS to a TDLS device and supports the ability to respond to a TXS initiated by other TDLS devices;

[0222] The first identification information is set to a second parameter value, indicating that the first site device supports the ability to initiate a TXS to a TDLS device, and does not support the ability to respond to a TXS initiated by other TDLS devices;

[0223] The first identification information is set to a third parameter value, indicating that the first site device does not support the capability of initiating a TXS to a TDLS device, but supports the capability of responding to a TXS initiated by other TDLS devices;

[0224] The first identification information is set to a fourth parameter value, indicating that the first site device does not support the capability of initiating a TXS to a TDLS device, and does not support the capability of responding to a TXS initiated by other TDLS devices.

[0225] Optionally, in the embodiment of the present disclosure, after sending the TDLS Setup Request frame, the method further includes:

[0226] Step 403: Receive a TDLS Setup Response frame sent by the second site device.

[0227] The TDLS Setup Response frame includes second identification information, where the second identification information identifies the second site device's support capability information for the P2P TXS mode; the support capability information includes: whether the second site device supports the P2P transmission opportunity sharing TXS mode, and at least one of the types of P2P TXS modes supported by the second site device.

[0228] Optionally, in the embodiment of the present disclosure, after receiving the TDLS Setup Response frame sent by the second site device, the method further includes:

[0229] Step 404: Send data to the second site device within the first TXOP; wherein the second identification information indicates that the second site device does not support the ability to respond to TXS initiated by other TDLS devices, or the first identification information indicates that the first site device does not support the ability to initiate TXS to a TDLS device;

[0230] Step 405: Receive a first TXOP sharing request sent by the second site device; wherein the first TXOP sharing request is used to request the first site device to share part of the transmission time within the first TXOP for the second site device to perform low-latency service transmission; wherein the second identification information identifies the second site device's ability to respond to TXS initiated by other TDLS devices, and the first identification information identifies the first site device's ability to initiate TXS to a TDLS device;

[0231] or

[0232] Step 406: Send a second TXOP sharing request to the second site device; wherein the second TXOP sharing request is used to request the second site device to share part of the transmission time within the second TXOP for the first site device to perform low-latency service transmission; wherein the first identification information identifies that the first site device supports the ability to respond to TXS initiated by other TDLS devices, and the second identification information identifies that the second site device supports the ability to initiate TXS to the TDLS device.

[0233] Optionally, in the embodiment of the present disclosure, after receiving the first TXOP sharing request sent by the second site device, the method further includes:

[0234] Step 407: In response to the first TXOP sharing request, the first site device sends a first multi-user request to send transmission opportunity sharing trigger MU-RTS TXS Trigger frame to the second site device; the first MU-RTS TXS Trigger frame includes a User Info field, and the User Info field includes device identification information of the second site device.

[0235] Optionally, in the embodiment of the present disclosure, within the transmission time shared by the first site device to the second site device, the first site device sends data only when receiving a data sending request from the second site device and responding to the data sending request.

[0236] Optionally, in the embodiment of the present disclosure, after sending the second TXOP sharing request to the second site device, the method further includes:

[0237] Step 408: Receive a second MU-RTS TXS Trigger frame sent by the second site device. The second MU-RTS TXS Trigger frame includes a user information field, and the User Info field includes device identification information of the first site device.

[0238] 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, step 404 can be implemented as an independent embodiment, step 405 can be implemented as an independent embodiment, and step 406 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 402 and step 403 can be implemented as an independent embodiment, the combination of step 405 and step 407 can be implemented as an independent embodiment, and the combination of step 406 and step 408 can be implemented as an independent embodiment, but are not limited thereto.

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

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

[0241] As shown in FIG5 , the above method may be applied to the second site device 102, and the above method includes:

[0242] Step 501: Receive a TDLS Setup Request frame; the TDLS Setup Request frame includes first identification information, where the first identification information identifies the first site device's support capability information for the P2P TXS mode; the support capability information includes at least one of: whether the first site device supports the P2P transmission opportunity sharing TXS mode and the type of P2P TXS mode supported by the first site device;

[0243] Step 502: Determine a TDLS Setup Response frame; the TDLS Setup Response frame includes second identification information, where the second identification information identifies the second site device's support capability information for the P2P TXS mode; the support capability information includes at least one of: whether the second site device supports the P2P transmission opportunity sharing TXS mode and the type of P2P TXS mode supported by the second site device;

[0244] Step 503: Send the TDLS Setup Response frame.

[0245] Optionally, in an embodiment of the present disclosure, the TDLS Setup Request frame includes a UHR capability element;

[0246] The second identification information is carried in the P2P TXOP Sharing Mode Support identification field of the UHR capability element.

[0247] Optionally, in an embodiment of the present disclosure, the method includes at least one of the following:

[0248] The second identification information is set to the first parameter value, indicating that the second site device supports the ability to initiate a TXS to the TDLS device and supports the ability to respond to a TXS initiated by other TDLS devices;

[0249] The second identification information is set to a second parameter value, indicating that the second site device supports the ability to initiate a TXS to a TDLS device, and does not support the ability to respond to a TXS initiated by other TDLS devices;

[0250] The second identification information is set to a third parameter value, indicating that the second site device does not support the capability of initiating a TXS to a TDLS device, but supports the capability of responding to a TXS initiated by other TDLS devices;

[0251] The second identification information is set to a fourth parameter value, indicating that the second site device does not support the ability to initiate a TXS to a TDLS device, and does not support the ability to respond to a TXS initiated by other TDLS devices;

[0252] Optionally, in the embodiment of the present disclosure, after receiving the TDLS Setup Request frame, the method further includes:

[0253] Step 504: Maintain a receiving state within the first TXOP and receive data sent by the first site device; wherein the second identification information indicates that the second site device does not support the ability to respond to TXS initiated by other TDLS devices, or the first identification information indicates that the first site device does not support the ability to initiate TXS to a TDLS device;

[0254] Step 505: Send a TXOP sharing request to the first site device; wherein the TXOP sharing request is used to request the first site device to share part of the transmission time within the first TXOP for the second site device to perform low-latency service transmission; wherein the second identification information identifies the second site device's ability to respond to TXS initiated by other TDLS devices, and the first identification information identifies the first site device's ability to initiate TXS to the TDLS device;

[0255] or

[0256] Step 506: Receive a second TXOP sharing request sent by the first site device; wherein the second TXOP sharing request is used to request the second site device to share part of the transmission time within the second TXOP for the first site device to perform low-latency service transmission; wherein the first identification information identifies that the first site device supports the ability to respond to TXS initiated by other TDLS devices, and the second identification information identifies that the second site device supports the ability to initiate TXS to the TDLS device.

[0257] Optionally, in the embodiment of the present disclosure, after sending the TXOP sharing request to the first site device, the method further includes:

[0258] Step 507: Receive a first MU-RTS TXS Trigger frame sent by the first site device to the second site device; the first MU-RTS TXS Trigger frame includes a User Info field.

[0259] Optionally, in an embodiment of the present disclosure, the User Info field includes device identification information of the second site device, and transmits a low-latency service within the transmission time indicated by the MU-RTS TXS Trigger frame;

[0260] or

[0261] The User Info field does not include the device identification information of the second site device. In the first TXOP, the receiving state is maintained to receive data sent by the first site device.

[0262] Optionally, in the embodiment of the present disclosure, after sending the second TXOP sharing request to the second site device, the method further includes:

[0263] Step 508: In response to the second TXOP sharing request, send a second MU-RTS TXS Trigger frame to the first site device; the second MU-RTS TXS Trigger frame includes a User Info field, and the User Info field includes device identification information of the first site device.

[0264] Optionally, in an embodiment of the present disclosure, within the transmission time shared by the second site device to the first site device, the second site device sends data only when receiving a data sending request from the first site device and responding to the data sending request.

[0265] 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, step 505 can be implemented as an independent embodiment, and step 506 can be implemented as an independent embodiment; the combination of step 501 and step 502 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 501, step 502 and step 503 can be implemented as an independent embodiment, the combination of step 505 and step 507 can be implemented as an independent embodiment, and the combination of step 506 and step 508 can be implemented as an independent embodiment, but is not limited thereto.

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

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

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

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

[0270] Fig. 6 is a schematic diagram of the structure of a first site device according to an embodiment of the present disclosure. As shown in Fig. 6 , the first site device 600 may include at least one of a determining module 601 and a first sending module 602 .

[0271] In some embodiments, the above-mentioned determination module 601 is used to determine a channel direct connection establishment request TDLS Setup Request frame; the TDLS Setup Request frame includes first identification information, and the first identification information identifies the first site device's support capability information for the P2P TXS mode; the support capability information includes: whether the first site device supports the P2P transmission opportunity sharing TXS mode, and at least one of the types of P2P TXS modes supported by the first site device.

[0272] The first sending module 602 is configured to send the TDLS Setup Request frame.

[0273] Optionally, the determination module 601 is configured to execute at least one of the communication steps (e.g., step 201, step 301, and step 401, but not limited thereto) performed by the first site device 101 in any of the above methods, which are not described in detail here. The first sending module 602 is configured to execute at least one of the communication steps (e.g., step 202, step 205, step 207, step 303, step 308, step 402, step 404, step 406, and step 407, but not limited thereto) performed by the first site device 101 in any of the above methods, which are not described in detail here.

[0274] FIG7 is a schematic diagram of the structure of a second site device according to an embodiment of the present disclosure. As shown in FIG7 , the second site device 700 may include: a first receiving module 701 , a second determining module 702 , and a second sending module 703 .

[0275] In some embodiments, the first receiving module 701 is configured to receive a TDLS Setup Request frame; the TDLS Setup Request frame includes first identification information, where the first identification information identifies the first site device's support capability information for the P2P TXS mode; the support capability information includes: whether the first site device supports the P2P transmission opportunity sharing TXS mode, and at least one of the types of P2P TXS modes supported by the first site device;

[0276] A second determining module 702 is configured to determine a TDLS Setup Response frame; the TDLS Setup Response frame includes second identification information, where the second identification information identifies the second site device's support capability information for the P2P TXS mode; the support capability information includes at least one of: whether the second site device supports the P2P transmission opportunity sharing TXS mode and a type of P2P TXS mode supported by the second site device;

[0277] The second sending module 703 is configured to send the TDLS Setup Response frame.

[0278] Optionally, the above-mentioned first receiving module 701 is used to execute at least one of the communication steps (for example, step 203, step 501, step 504, step 506, step 507 but not limited to) performed by the second site device 102 in any of the above methods, the second determination module 702 is used to execute at least one of the communication steps (for example, step 502, but not limited to) performed by the second site device 102 in any of the above methods, and the second sending module 703 is used to execute at least one of the communication steps (for example, step 203, step 209, step 302, step 304, step 307, step 309, step 505, step 508, but not limited to) performed by the second site device 102 in any of the above methods, which will not be repeated here.

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

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

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

[0282] 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 203, step 204, step 205, step 206, step 207, step 208, step 209, steps 301 to 313, step 402, step 403, step 404, step 405, step 406, step 407, step 408, step 501, step 503, step 505, step 505, step 506, step 507, step 508, but not limited thereto), and the processor 801 performs at least one of the other steps (for example, step 201, step 401, step 301, step 502, but not limited thereto).

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

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

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

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

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

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

[0289] 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 202, step 203, step 204, step 205, step 206, step 207, step 208, step 209, steps 301 to 313, step 402, step 403, step 404, step 405, step 406, step 407, step 408, step 501, step 503, step 505, step 505, step 506, step 507, step 508, but not limited to these), and the processor 901 executes at least one of the other steps (for example, step 201, step 401, step 301, step 502, but not limited to these).

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

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

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

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

[0294] 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, applied to a first site device, It is characterized in that The method comprises: Determine a channel direct connection establishment request TDLS Setup Request frame; the TDLS Setup Request frame includes first identification information, the first identification information identifies the support capability information of the first site device for the point-to-point transmission opportunity sharing P2P TXS mode; the support capability information includes: whether the first site device supports the P2P transmission opportunity sharing TXS mode, and at least one of the types of the P2P TXS mode supported by the first site device; Send the TDLS Setup Request frame.

2. The communication method according to claim 1, It is characterized in that The TDLS Setup Request frame includes the Ultra High Reliability (UHR) capability element. The first identification information is carried in the P2P TXOP Sharing mode support Mode Support identification field of the UHR capability element.

3. The communication method according to claim 1 or 2, It is characterized in that The method comprises at least one of the following: The first identification information is set to a first parameter value, indicating that the first site device supports the capability of initiating TXS to the TDLS device, and supports the capability of responding to TXS initiated by other TDLS devices; The first identification information is set to a second parameter value, indicating that the first site device supports the capability of initiating TXS to the TDLS device, and does not support the capability of responding to TXS initiated by other TDLS devices; The first identification information is set to a third parameter value, indicating that the first site device does not support the capability of initiating TXS to the TDLS device, and supports the capability of responding to TXS initiated by other TDLS devices; The first identification information is set to a fourth parameter value, indicating that the first site device does not support the capability of initiating TXS to a TDLS device, and does not support the capability of responding to TXS initiated by other TDLS devices.

4. The communication method according to claim 1, It is characterized in that After sending the TDLS Setup Request frame, the method further includes: receiving a direct connection establishment response TDLS Setup Response frame sent by the second site device; The TDLS Setup Response frame includes second identification information, and the second identification information identifies the support capability information of the second site device for the P2P TXS mode; the support capability information includes: whether the second site device supports the P2P transmission opportunity sharing TXS mode, and at least one of the types of P2P TXS modes supported by the second site device.

5. The communication method according to claim 4, It is characterized in that After receiving the TDLS Setup Response frame sent by the second site device, the method further includes: In the first TXOP, data is sent to the second site device; wherein the second identification information indicates that the second site device does not support the ability to respond to the TXS initiated by other TDLS devices, or the first identification information indicates that the first site device does not support the ability to initiate a TXS to the TDLS device; Receive a first TXOP sharing request sent by the second site device; wherein the first TXOP sharing request is used to request the first site device to share part of the transmission time within the first TXOP for the second site device to perform low-latency service transmission; wherein the second identification information identifies the ability of the second site device to support responding to TXS initiated by other TDLS devices, and the first identification information identifies the ability of the first site device to support initiating TXS to the TDLS device; or A second TXOP sharing request is sent to the second site device; wherein the second TXOP sharing request is used to request the second site device to share part of the transmission time within the second TXOP for the first site device to perform low-latency service transmission; wherein the first identification information identifies that the first site device supports the ability to respond to TXS initiated by other TDLS devices, and the second identification information identifies that the second site device supports the ability to initiate TXS to the TDLS device.

6. The communication method according to claim 5, It is characterized in that After receiving the first TXOP sharing request sent by the second site device, the method further includes: In response to the first TXOP sharing request, the first site device sends a first multi-user request to send transmission opportunity sharing trigger MU-RTS TXS Trigger frame to the second site device; the first MU-RTS TXS Trigger frame includes a User Info field, and the User Info field includes device identification information of the second site device.

7. The communication method according to claim 5 or 6, It is characterized in that During the transmission time shared by the first site device to the second site device, the first site device sends data only when receiving a data sending request from the second site device and responding to the data sending request.

8. The communication method according to claim 5, It is characterized in that After sending the second TXOP sharing request to the second site device, the method further includes: A second MU-RTS TXS Trigger frame sent by the second site device is received; the second MU-RTS TXS Trigger frame includes a user information field User Info field, and the User Info field includes device identification information of the first site device.

9. A communication method, applied to a second site device, It is characterized in that The method comprises: receiving a TDLS Setup Request frame; the TDLS Setup Request frame comprising first identification information, wherein the first identification information identifies the support capability information of the first site device for the P2P TXS mode; the support capability information comprises: whether the first site device supports the P2P transmission opportunity sharing TXS mode, and at least one of the types of the P2P TXS mode supported by the first site device; Determine a TDLS Setup Response frame; the TDLS Setup Response frame includes second identification information, the second identification information identifies the support capability information of the second site device for the P2P TXS mode; the support capability information includes: whether the second site device supports the P2P transmission opportunity sharing TXS mode, and at least one of the types of the P2P TXS mode supported by the second site device; Send the TDLS Setup Response frame.

10. The communication method according to claim 9, It is characterized in that The TDLS Setup Request frame includes a UHR capability element; The second identification information is carried in the P2P TXOP Sharing Mode Support identification field of the UHR capability element.

11. The communication method according to claim 9 or 10, It is characterized in that The method comprises at least one of the following: The second identification information is set to the first parameter value, indicating that the second site device supports the ability to initiate TXS to the TDLS device, and supports the ability to respond to TXS initiated by other TDLS devices; The second identification information is set to a second parameter value, indicating that the second site device supports the capability of initiating TXS to the TDLS device, and does not support the capability of responding to TXS initiated by other TDLS devices; The second identification information is set to a third parameter value, indicating that the second site device does not support the capability of initiating TXS to the TDLS device, and supports the capability of responding to TXS initiated by other TDLS devices; The second identification information is set to a fourth parameter value, indicating that the second site device does not support the capability of initiating TXS to the TDLS device, and does not support the capability of responding to TXS initiated by other TDLS devices.

12. The communication method according to claim 9, It is characterized in that After receiving the TDLS Setup Request frame, the method further includes: In the first TXOP, maintaining a receiving state, receiving data sent by the first site device; wherein the second identification information indicates that the second site device does not support the ability to respond to TXS initiated by other TDLS devices, or the first identification information indicates that the first site device does not support the ability to initiate TXS to the TDLS device; Sending a TXOP sharing request to the first site device; wherein the TXOP sharing request is used to request the first site device to share part of the transmission time within the first TXOP for the second site device to perform low-latency service transmission; wherein the second identification information identifies the ability of the second site device to support responding to TXS initiated by other TDLS devices, and the first identification information identifies the ability of the first site device to support initiating TXS to the TDLS device; or Receive a second TXOP sharing request sent by the first site device; wherein the second TXOP sharing request is used to request the second site device to share part of the transmission time within the second TXOP for the first site device to perform low-latency service transmission; wherein the first identification information identifies that the first site device supports the ability to respond to TXS initiated by other TDLS devices, and the second identification information identifies that the second site device supports the ability to initiate TXS to TDLS devices.

13. The communication method according to claim 12, It is characterized in that After sending the TXOP sharing request to the first site device, the method further includes: A first MU-RTS TXS Trigger frame sent by the first site device to the second site device is received; the first MU-RTS TXS Trigger frame includes a User Info field.

14. The communication method according to claim 13, It is characterized in that The User Info field includes device identification information of the second site device, and transmits a low-latency service within the transmission time indicated by the MU-RTS TXS Trigger frame; or The User Info field does not include the device identification information of the second site device, and in the first TXOP, maintains a receiving state to receive data sent by the first site device.

15. The communication method according to claim 12, It is characterized in that After receiving the second TXOP sharing request sent by the first site device, the method further includes: In response to the second TXOP sharing request, a second MU-RTS TXS Trigger frame is sent to the first site device; the second MU-RTS TXS Trigger frame includes a User Info field, and the User Info field includes device identification information of the first site device.

16. The communication method according to claim 12 or 15, It is characterized in that During the transmission time shared by the second site device to the first site device, the second site device sends data only when receiving a data sending request from the first site device and responding to the data sending request.

17. A site device, wherein the site device is a first site device, It is characterized in that The first site equipment includes: A first determination module is used to determine a channel direct connection establishment request TDLS Setup Request frame; the TDLS Setup Request frame includes first identification information, and the first identification information identifies the support capability information of the first site device for the P2P TXS mode; the support capability information includes: whether the first site device supports the P2P transmission opportunity sharing TXS mode, and at least one of the types of the P2P TXS mode supported by the first site device; The first sending module is used to send the TDLS Setup Request frame.

18. A site device, wherein the site device is a second site device, It is characterized in that The second site equipment includes: A first receiving module, configured to receive a TDLS Setup Request frame; the TDLS Setup Request frame includes first identification information, wherein the first identification information identifies the support capability information of the first site device for the P2P TXS mode; the support capability information includes: whether the first site device supports the P2P transmission opportunity sharing TXS mode, and at least one of the types of the P2P TXS mode supported by the first site device; A second determination module is used to determine a TDLS Setup Response frame; the TDLS Setup Response frame includes second identification information, and the second identification information identifies the support capability information of the second site device for the P2P TXS mode; the support capability information includes: whether the second site device supports the P2P transmission opportunity sharing TXS mode, and at least one of the types of the P2P TXS mode supported by the second site device; The second sending module is used to send the TDLS Setup Response frame.

19. A site device, wherein the site device is a first site device, It is characterized in that include: one or more processors; The first site device is used to execute the communication method according to any one of claims 1 to 8.

20. A site device, wherein the site device is a second site device, It is characterized in that include: one or more processors; Wherein, the second site device is used to execute the communication method according to any one of claims 9 to 16.

21. A communication system, It is characterized in that It comprises a first site device and a second site device; wherein the first site device is configured to implement the communication method according to any one of claims 1 to 8, and the second site device is configured to implement the communication method according to any one of claims 9 to 16.

22. A storage medium storing instructions, It is 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 8, or execute the communication method according to any one of claims 9 to 16.

Images