CN112911729A

CN112911729A - Method, terminal and storage medium for establishing tunnel direct link

Info

Publication number: CN112911729A
Application number: CN202110124939.9A
Authority: CN
Inventors: 吴昊; 王鑫
Original assignee: Chengdu Jimi Technology Co Ltd
Current assignee: Chengdu Jimi Technology Co Ltd
Priority date: 2021-01-29
Filing date: 2021-01-29
Publication date: 2021-06-04
Anticipated expiration: 2041-01-29
Also published as: CN112911729B

Abstract

The application discloses a method, a terminal and a storage medium for establishing a tunnel direct link, and relates to the field of wireless communication. The method comprises the steps of setting parameters EHT capabilities or EHT operation in a TDLSSetupRequest parameter, a TDLSSetupResponse parameter, a TDLSSetupConfirm parameter, a TDLS SetuP Request frame, a TDLS SetuP Response frame and a TDLSSetuP Confirm frame, and setting a parameter ML Elements when a local parameter dot11multilink operation executed indicates that the terminal supports multilink operation capability or indicates that the terminal supports multilink operation capability and starts the operation. By implementing the scheme of the application, the multilink terminal does not need to execute the process of once TDLS connection establishment on each link, so that air interface signaling is reduced, waste of wireless resources is avoided, and the throughput of effective data is improved.

Description

Method, terminal and storage medium for establishing tunnel direct link

Technical Field

The present application relates to the field of wireless communications, and in particular, to a method, a terminal, and a storage medium for establishing a tunnel direct link.

Background

In the 802.11 system, an access device (AP STA) and a terminal (Non-AP STA) are both internally deployed with a MAC layer and a PHY layer, wherein the main functions of the MAC layer include channel management, connection management, quality of service management, power control, time synchronization, and the like, and the main functions of the PHY layer include modulation, coding, transmission, and the like.

Both the MAC layer and the PHY layer conceptually include management units referred to as a MAC layer management unit mlme (MAC sublayer management entity) and a physical layer management unit plme (PHY sublayer management entity), respectively. These elements provide low-level management service interfaces through which low-level management functions can be invoked.

In order to provide correct MAC operation, each STA (including Non-AP STA and AP STA) has a higher layer management unit, such as SME (device management element), which represents a higher layer management unit above the MAC layer, and is a layer-independent unit, which is located in a separate management plane.

The function of SME: typically, this unit is responsible for functions such as collecting layer-related state from various layer management units (MLME and PLME), which similarly also set layer-specific parameter values. SMEs typically perform such functions on behalf of a general system management entity. FIG. 1 depicts the relationship between management units.

802.11be networks, also known as Extreme High Throughput (EHT) networks, are enhanced by a range of system features and a variety of mechanisms to achieve very High Throughput. As the use of Wireless Local Area Networks (WLANs) continues to grow, it becomes increasingly important to provide wireless data services in many environments, such as homes, businesses, and hot spots. In particular, video traffic will continue to be the dominant type of traffic in many WLAN deployments. With the advent of 4k and 8k video (uncompressed rates of 20 Gbps), the throughput requirements for these applications are constantly evolving. New high throughput, low latency applications such as virtual reality or augmented reality, gaming, remote offices, and cloud computing will proliferate (e.g., latency for real-time gaming is less than 5 milliseconds).

In view of the high throughput and stringent real-time latency requirements of these applications, users expect higher throughput, higher reliability, less latency and jitter, and higher power efficiency when supporting their applications over a WLAN. Users desire improved integration with Time Sensitive Networks (TSNs) to support applications on heterogeneous ethernet and wireless LANs. 802.11be networks aim to ensure the competitiveness of WLANs by further increasing overall throughput and reducing latency, while ensuring backward compatibility and coexistence with legacy technology standards. 802.11 compatible devices operating in the 2.4GHz, 5GHz and 6GHz bands.

Disclosure of Invention

In the conventional TDLS (tunneled direct link setup) technology, a terminal and a terminal can perform direct data communication with coordination of an access device. After the multi-link terminal and the access device are introduced, the direct communication between the terminal and the terminal can be in a more flexible mode, for example, all links can be used for end-to-end communication to improve the data transmission rate, such as high-definition video screen projection and the like, and the end-to-end communication can also be carried out while still carrying out data transmission with the access device, such as on-line game screen projection and the like. According to the above scenario, the present application provides a method for TDLS of a multi-link terminal, a terminal, and a storage medium.

In a first aspect, an embodiment of the present application provides a method for establishing a direct tunnel link, including:

if the local parameter dot11 EHTOptoPrimeTimeImplemented of the initiator terminal indicates that the initiator terminal supports the EHT system capability or indicates that the initiator terminal supports the EHT system capability and enables, the higher management unit of the initiator terminal sends an MLME-TDLSSETUPREQUEST primitive to the lower management unit, wherein the MLME-TDLSSETUPREQUEST primitive comprises parameters TDLSResponnderAddress and TDLSSetupRequest, the TDLSResponnderAddress parameter is used for indicating the address of the responder terminal, the TDLSSetupRequest parameter is used for indicating the TDLS establishment request parameter, the TDLSSetupRequest parameter comprises a parameter EHT Capabilities1, and the EHT Capabilities1 is used for indicating the EHT system capability parameter of the initiator terminal;

the lower management unit of the initiator terminal sends a TDLS Setup Request frame to the responder terminal according to the received address of the TDLSResponnderAddress in the MLME-TDLSSETUPREQUEST primitive, wherein the TDLS Setup Request frame comprises the parameter EHT Capabilities 1;

a low-layer management unit of an initiator terminal receives a TDLS Setup Response frame sent by a responder terminal, wherein the TDLS Setup Response frame comprises a status code and EHT Capabilities2, the status code is used for indicating whether the responder terminal accepts establishment of a tunnel direct link, and the EHT Capabilities2 is used for indicating an EHT system capability parameter of the responder terminal;

the method comprises the steps that a low-layer management unit of an initiator terminal sends an MLME-TDLSSETUPRESPONSE.indication primitive to a high-layer management unit, wherein the MLME-TDLSSETUSPONSE.indication primitive comprises parameters TDLSResponerAndress and TDLSSetupResponse, the TDLSSetupResponse parameter is used for indicating a TDLS establishment response parameter, and the TDLSSetupResponse parameter comprises the parameters status code and EHT Capabilities 2;

when the status code indicates that the responder terminal accepts establishment of a tunnel direct Link, the TDLS Setup Response frame and the TDLSSetupResponse parameter further include a parameter Link info, the Link info is used for indicating established Link information, a higher layer management unit of the initiator terminal sends an MLME-tdlssetupfront request primitive to a lower layer management unit, the MLME-tdlssetupfront request primitive includes parameters tdlsresponsedrardress and tdlssetupfront, the tdlssetupfront parameter is used for indicating a TDLS Setup confirmation parameter, the tdlssetupfront parameter includes parameters EHT Operation1 and Link info, and the tdt Operation1 is used for indicating an EHT system Operation parameter of the initiator terminal;

after receiving the MLME-TDLSSETUPCONFIRM.request primitive, the lower layer management unit of the initiator terminal sends a TDLS Setup Confirm frame to the responder terminal, wherein the TDLS Setup Confirm frame comprises parameters EHT Operation1 and Link info.

In a possible implementation manner, when the local parameter dot11multilink operation executed of the initiator terminal indicates that the initiator terminal supports the multilink operation capability or indicates that the initiator terminal supports the multilink operation capability and starts the operation, the tdlssetup Request parameter, the TDLS Setup Request frame, the tdlssetup parameter, and the TDLS Setup Confirm frame further include a parameter ML Elements1, and the ML Elements1 are used for indicating the multilink parameter of the initiator terminal. Optionally, the parameter ML Elements1 may also be included in the EHT Capabilities1 or the EHT Operation 1. Still further, the parameter ML Elements1 may be included in the MAC Capabilities of the EHT Capabilities1, and the Multi link support is included in the ML Elements 1. When the parameters ML Elements1 are included in the EHT Operation1, the parameters Align start time of PPDU and Align end time of PPDU in the EHT Operation1 may be included in ML Elements 1.

In a second aspect, an embodiment of the present application provides a method for establishing a direct tunnel link, including:

after receiving a TDLS Setup Request frame sent by an initiator terminal, a lower management unit of a responder terminal sends an MLME-TDLSSETUPREQUEST.indication primitive to a higher management unit, wherein the MLME-TDLSSETUPREQUEST.indication primitive comprises parameters TDLSINitiatorAddress and TDLSSetupRequest, the TDLSINitiatorAddress parameter is used for indicating an address of the initiator terminal, the TDLSSetupRequest parameter is used for indicating a TDLS Setup Request parameter, the TDLSSetupRequest parameter comprises a parameter EHT Capabilities1, and the EHT Capabilities1 is used for indicating an EHT system capability parameter of the initiator terminal;

if the local parameter dot11 EHTOptoPrime Implemented of the responder terminal indicates that the responder terminal supports the EHT system capability or indicates that the responder terminal supports and enables the EHT system capability, after receiving the MLME-TDLSSETUPREQUEST.indication primitive, the higher-level management unit of the responder terminal sends an MLME-TDLSSETUPRESPONSE.request primitive to the lower-level management unit, wherein the MLME-TDLSSETUPRESPONSE.request primitive comprises parameters TDLSInitiatedAddress and TDLSSetupResponse, the TDLSSetupResponse parameter is used for indicating a TDLS setup response parameter, the TDLSSetupResponse parameter comprises parameters of status code and EHT Capabilities2, the status code is used for indicating whether the responder terminal accepts the setup of the tunnel direct link, and the EHT Capabilities2 is used for indicating the EHT system capability of the responder terminal;

after receiving the MLME-TDLSSETUPRESPONSE.request primitive, a lower layer management unit of the responder terminal sends a TDLS Setup Response frame to the initiator terminal, wherein the TDLS Setup Response frame comprises the parameter status code and EHT Capabilities 2;

when the status code indicates that a responder terminal accepts establishment of a tunnel direct Link, the TDLSSetupResponse parameter and the TDLS Setup Response frame further contain a parameter Link info, wherein the Link info is used for indicating established Link information, a low-layer management unit of the responder terminal receives a TDLS Setup Confirm frame sent by the initiator terminal, the TDLS Setup Confirm frame contains parameters EHT Operation1 and Link info, and the EHT Operation1 is used for indicating an EHT system Operation parameter of the sender terminal;

the lower layer management unit of the responder terminal sends an MLME-TDLSSETUPCFIRM.indication primitive to the higher layer management unit, wherein the MLME-TDLSSETUPCFIRM.indication primitive comprises parameters TDLSInitiatorAddress and TDLSSetupConfirm, and the TDLSSetupConfirm parameter comprises parameters EHT Operation1 and Link info.

In a possible implementation manner, when the local parameter dot11multilink operation executed of the responder terminal indicates that the responder terminal supports the multilink operation capability or indicates that the responder terminal supports the multilink operation capability and starts the operation, the tdlssetup Response parameter and the TDLS Setup Response frame further include a parameter ML Elements2, and the ML Elements2 is used for indicating the multilink parameter of the responder terminal. Alternatively, the parameter ML Elements2 may be included in the EHT Capabilities 2. Still further, the parameter ML Elements2 may be included in the MAC Capabilities of EHT Capabilities2, and the Multi link support is included in the ML Elements 2.

In a third aspect, an embodiment of the present application provides a terminal, where the terminal includes a higher management unit and a lower management unit, where,

a high-level management unit, configured to send an MLME-tdlssetrequest request primitive to the low-level management unit if a local parameter dot11 ehtoptionpopulated of the initiator terminal indicates that the initiator terminal supports the EHT system capability or indicates that the initiator terminal supports the EHT system capability and is enabled, where the MLME-tdlssetrequest primitive includes parameters tdlsrespondres and TDLSSetupRequest, the tdlsrespondres parameter is used for indicating an address of the responder terminal, the TDLSSetupRequest parameter is used for indicating a TDLS setup request parameter, the TDLSSetupRequest parameter includes a parameter t ehabilities 1, and the EHT Capabilities1 is used for indicating an EHT system capability parameter of the initiator terminal; when the status code indicates that the responder terminal accepts establishment of a tunnel direct Link, sending an MLME-TDLSSETUPCFIRM.request primitive to a lower layer management unit, wherein the MLME-TDLSSETUPCFIRM.request primitive comprises parameters TDLSResponderaddress and TDLSSetupConfirm, the TDLSSetupConfirm parameter is used for indicating a TDLS establishment confirmation parameter, the TDLSSetupConfirm parameter comprises parameters EHT Operation1 and Link info, and the EHT Operation1 is used for indicating an EHT system Operation parameter of the initiator terminal;

a low-level management unit, configured to send a TDLS Setup Request frame to a responder terminal according to a received address of tdlsresponsedraddresses in the MLME-tdlssetup Request primitive, where the TDLS Setup Request frame includes the parameter EHT Capabilities 1; receiving a TDLS Setup Response frame sent by a responder terminal, wherein the TDLS Setup Response frame comprises parameters of status code and EHT Capabilities2, the status code is used for indicating whether the responder terminal accepts establishment of a tunnel direct link, and the EHT Capabilities2 is used for indicating an EHT system capability parameter of the responder terminal; sending an MLME-TDLSSETUPRESPONSE.indication primitive to a high-level management unit, wherein the MLME-TDLSSETUSPONSE.indication primitive comprises parameters TDLSResponnderrAddress and TDLSSetupResponse, the TDLSSetupResponse parameter is used for indicating a TDLS establishment response parameter, and the TDLSSetupResponse parameter comprises the parameters status code and EHT Capabilities 2; when the status code indicates that a responder terminal accepts establishment of a tunnel direct Link, the TDLS Setup Response frame and the TDLSSetupResponse parameter also contain a parameter Link info, and the Link info is used for indicating established Link information; after receiving the MLME-TDLSSETUPCONFIRM.request primitive, sending a TDLS Setup Confirm frame to a responder terminal, wherein the TDLS Setup Confirm frame comprises parameters EHT Operation1 and Link info.

In a fourth aspect, an embodiment of the present application provides a terminal, which includes a higher management unit and a lower management unit, wherein,

the system comprises a lower-layer management unit, a higher-layer management unit and a TDLS (multicast service Request) unit, wherein the lower-layer management unit is used for sending an MLME-TDLSSETUPREQUEST-indication primitive to the higher-layer management unit after receiving a TDLS Setup Request frame sent by an initiator terminal, the MLME-TDLSSETUPREQUEST-indication primitive comprises parameters TDLSINitiatedAddress and TDLSSetupRequest, the TDLSInitiatedAddress parameter is used for indicating the address of the initiator terminal, the TDLSSetupRequest parameter is used for indicating a TDLS establishment Request parameter, the TDLSSetupRequest parameter comprises a parameter EHT Capabilities1, and the EHT Capabilities1 is used for indicating an EHT system capability parameter of the initiator terminal; after receiving MLME-TDLS SETUPRESPONSE.REQUEST primitive, sending a TDLS Setup Response frame to the initiator terminal, wherein the TDLS Setup Response frame comprises the parameter status code and EHT Capabilities 2; when the status code indicates that a responder terminal accepts establishment of a tunnel direct Link, receiving a TDLS Setup Confirm frame sent by an initiator terminal, wherein the TDLS Setup Confirm frame comprises parameters EHT Operation1 and Link info, and the EHT Operation1 is used for indicating an EHT system Operation parameter of the sender terminal; sending an MLME-TDLSSETUPCONFIRM.indication primitive to a high-level management unit, wherein the MLME-TDLSSETUPCONFIRM.indication primitive comprises parameters TDLSInitiatorAddress and TDLSSetupConfirm, and the TDLSSetupConfirm parameter comprises parameters EHT Operation1 and Link info;

a high-level management unit, configured to send an MLME-tdlssetuproprequest.request primitive to a low-level management unit after receiving the MLME-tdlssetuproprequest.indication primitive, where the MLME-tdlssetuponsse.request primitive includes parameters TDLSInitiatorAddress and tdlssetresponsee, the tdlssetresponsee parameter is used to indicate a TDLS setup response parameter, the tdlssetresponsee parameter includes parameters status code and EHT Capabilities2, the status code is used to indicate whether the responder terminal accepts setup of the tunnel direct link, and the EHT Capabilities2 is used to indicate the EHT system capability of the responder terminal; when the status code indicates that the responder terminal accepts establishment of the tunnel direct Link, the tdlssetuprpresponse parameter and the TDLS Setup Response frame further include a parameter Link info, and the Link info is used for indicating established Link information.

In a fifth aspect, an embodiment of the present application provides a terminal, where the terminal includes a processor and a memory, where the memory stores at least one program code, and the at least one program code is loaded and executed by the processor to implement the method for establishing a tunneled direct link according to the first aspect or the second aspect.

In a sixth aspect, an embodiment of the present application provides a storage medium, where at least one program code is stored, and the at least one program code is loaded and executed by a processor to implement the method for establishing a tunneled direct link according to the first aspect or the second aspect.

It should be noted that the terminal described in the third aspect is configured to execute the method provided in the first aspect, the terminal described in the fourth aspect is configured to execute the method provided in the second aspect, and the terminal described in the fifth aspect and the storage medium described in the sixth aspect are configured to execute the method provided in the first aspect or the second aspect, so that the same beneficial effects as those of the method described in the first aspect or the second aspect can be achieved, and details of the embodiments of the present application are not repeated.

By implementing the scheme of the application, the multilink terminal does not need to execute the process of once TDLS connection establishment on each link, so that air interface signaling is reduced, waste of wireless resources is avoided, and the throughput of effective data is improved.

Drawings

The present application will now be described by way of example only and with reference to the accompanying drawings in which:

FIG. 1 is a diagram illustrating a management unit structure of a device in the prior art;

fig. 2 is a schematic diagram of a method for establishing a direct tunnel link according to an embodiment of the present application.

Detailed Description

In order to make those skilled in the art better understand the technical solutions in the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the present application and are not intended to limit the present application. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application. Moreover, while the disclosure herein has been presented in terms of exemplary one or more examples, it is to be understood that each aspect of the disclosure can be utilized independently and separately from other aspects of the disclosure to provide a complete disclosure. The embodiments described below and the features of the embodiments can be combined with each other without conflict.

In the embodiments of the present application, the words "exemplary," "for example," and the like are used to mean serving as an example, instance, or illustration. Any embodiment or design described herein as "exemplary" is not necessarily to be construed as preferred or advantageous over other embodiments or designs. Rather, the term using examples is intended to present concepts in a concrete fashion.

Unless defined otherwise, technical or scientific terms used herein shall have the ordinary meaning as understood by one of ordinary skill in the art to which this application belongs. The use of "first," "second," and similar terms in this application do not denote any order, quantity, or importance, but rather the terms are used merely to distinguish one element from another, and the meanings of the corresponding terms may be the same or different. The word "comprising" or "comprises", and the like, means that the element or item listed before the word covers the element or item listed after the word and its equivalents, but does not exclude other elements or items.

In this embodiment, both the terminal device and the access device include a low-level management unit and a high-level management unit, where the low-level management unit is a unit that manages and controls data transmission of the device, such as an MLME and a PLME, and the high-level management unit is a unit that manages a service or an application of the device, such as an equipment management unit SME and an application management unit ame (application management entity).

It should be noted that the multilink device includes a plurality of logic entities, each logic entity performs data transmission through one link, and each logic entity includes an independent data transceiver module. A conventional single-link device has only one logical entity and only one MAC address, while a multi-link device has one MAC address, and each logical entity belonging to the multi-link device has one MAC address, for example, if a multi-link device runs with 3 logical entities, there are four MAC addresses on the physical device, one is of the multi-link device, and each of the three logical entities has one MAC address. In the embodiment of the present application, the logical STA is a logical entity in the terminal.

In the tunnel direct link establishment, one terminal initiates an end-to-end direct link establishment with another terminal, the terminal initiating the direct link establishment is called an initiator terminal, and a peer terminal establishing the link is called a responder terminal.

Fig. 2 is a schematic diagram of a method for establishing a direct tunnel link according to an embodiment of the present application. As shown in fig. 2, the method for establishing a tunnel direct link includes the following steps:

1. if the current terminal supports the EHT system capability and is enabled, the value of the current terminal is set to true when the parameter dot11 EHTOPTIONPLENED is set locally, and if the terminal supports the EHT system capability and is not enabled, the value of the current terminal is set to false when the parameter dot11 EHTOPTIONPLENED is set locally.

Or, if the current terminal supports the EHT capability, setting a parameter dot11 ehtopitioninplemented locally, and setting the value thereof as true.

2. If the current terminal supports the capability of an EHT system, has multilink operation capability and starts the operation, namely when the dot11EHTOPTIONImplemented is true, the parameter dot11multilink OptionsImplemented is set locally, and the value is set to true; if the multilink operation capability is provided and the operation is closed, a parameter dot11multilink operation executed is set locally, and the value is set to false;

or the like, or, alternatively,

if the current terminal supports the multilink operation capability, a parameter dot11multilink operation executed is set locally, and the value is set to true.

3. The SME of the initiator terminal sends MLME-TDLSSETUPREQUEST primitive to the MLME of the initiator terminal, and the primitive comprises the following parameters:

tdlsrespondaddress: the address of the responder terminal;

TDLSSetupRequest: the TDLS setup request parameters, illustratively, include parameters as shown in table 1.

TABLE 1

An example of the EHT capabilities parameter settings is shown in table 2.

TABLE 2

MAC Capability

PHY Capability

MAC Capability: MAC layer capabilities of the EHT system;

PHY Capability: physical layer capabilities of the EHT system;

the MAC Capability contains one or more of the parameters shown in table 3.

TABLE 3

The PHY Capability contains one or more of the parameters shown in table 4.

TABLE 4

The ML Elements parameter is shown in Table 5.

TABLE 5

MLD common info

STA info 1

STA info n

MLD common info: indicating a multilink common parameter of the terminal;

STA info 1-STA info n: indicating a proprietary parameter of a single logical STA in the terminal, wherein 1-n represents that one or more logical STAs can exist, and the parameter n is determined by the number of the logical STAs actually operated by the terminal;

the STA info 1-n parameters may be set as shown in Table 6.

TABLE 6

Link ID

STA Capability

STA operation

Link ID: an identification indicating a link on which the logical STA operates;

STA Capability: indicating a capability parameter specific to the logical STA;

STA operation: indicating the operating parameters specific to the logical STA.

4. After receiving the MLME-tdlssetup Request primitive, the MLME of the initiator terminal sends a TDLS Setup Request frame to the responder terminal according to the address of tdlsresponsedraddresses in the primitive, where an example of parameters included in the TDLS Setup Request frame is shown in table 7.

TABLE 7

5. After receiving the TDLS Setup Request frame, the MLME of the responder terminal sends an MLME-TDLSSETUPREQUEST.indication primitive to the SME of the responder terminal, wherein the primitive comprises:

TDLSInitiatorAddress: the address of the originator terminal;

TDLSSetupRequest: setting the same parameters as in step 3.

6. After receiving MLME-TDLSSETUPREQUEST.indication primitive, SME of a responder terminal determines whether to accept establishment of a tunnel direct link, and if so, sets a parameter status code as SUCCESS; if the REQUEST is rejected, setting the parameter status code as REQUEST _ DECLINED; a MLME sending MLME-tdlssetup request primitive to the MLME of the responder terminal, the primitive comprising:

TDLSInitiatorAddress: the address of the originator terminal;

tdlssetuprpesponse: the TDLS setup response parameters, illustratively, include parameters such as table 8.

TABLE 8

The Link info setting table shows, for example, table 9.

TABLE 9

7. After receiving the MLME-TDLS Setup Response primitive, the MLME of the responder terminal sends a TDLS Setup Response frame to the initiator terminal, where an example of the parameters included in the TDLS Setup Response frame is shown in table 10.

Watch 10

8. After receiving the TDLS Setup Response frame, the MLME of the initiator terminal sends an MLME-TDLS Setup _ Response primitive to the SME of the initiator terminal, wherein the primitive comprises:

tdlsrespondaddress: the address of the responder terminal;

tdlssetuprpesponse: the same as step 6.

9. The SME of the initiator terminal sends MLME-TDLSSETUPCONFIRM.request primitive to the MLME of the initiator terminal, and the primitive comprises:

tdlsrespondaddress: the address of the responder terminal;

TDLSSetupConfirm: TDLS setup confirmation parameters, a setting example is shown in table 11.

TABLE 11

The EHT operation parameters include one or more of the parameters shown in table 12.

TABLE 12

10. After receiving the MLME-tdlssetup Confirm request primitive, the MLME of the initiator terminal sends a TDLS Setup Confirm frame, for example, table 13, to the responder terminal.

Watch 13

11. After receiving the TDLS Setup Confirm frame, the MLME of the responder terminal sends an MLME-TDLSSETUPCONFIRM.indication primitive to the SME of the responder terminal, wherein the primitive comprises:

TDLSInitiatorAddress: the address of the originator terminal;

TDLSSetupConfirm: the same as step 9.

12. After receiving MLME-TDLSSETUPCONFIRM.indication primitive, SME of the responder terminal executes TDLS operation.

In some embodiments, the TDLSSetupRequest parameter, the TDLSSetupResponse parameter, the TDLSSetupConfirm parameter, the TDLS Setup Request frame, the TDLS Setup Response frame, and the TDLS Setup Confirm frame contain only the parameter EHT capabilities or the parameter EHT operation; the following were used:

TDLSSetupRequest: the TDLS setup request parameters include parameters such as table 14.

TABLE 14

Tdlssetuprpesponse: the TDLS setup response parameters include parameters such as table 15.

Watch 15

TDLSSetupConfirm: the TDLS setup confirmation parameter, a setting example is shown in table 16.

TABLE 16

An example of the parameters contained in the TDLS Setup Request frame is as in table 17.

TABLE 17

An example of the parameters contained in the TDLS Setup Response frame is shown in table 18.

Watch 18

An example of the parameters contained in the TDLS Setup Confirm frame is as in table 19.

Watch 19

And the parameter ML Elements is included in the parameter EHT capabilities or the parameter EHT operation, in the following possible ways:

1) included in the EHT capabilities parameters, EHT capabilities parameter settings are shown in table 20, for example.

Watch 20

2) Included in the MAC Capability, which is a sub-parameter of the EHT capabilities parameter, is an example of the parameters included in the MAC Capability as shown in table 21.

TABLE 21

3) The EHT operation parameter is included in the EHT operation parameter, and the EHT operation parameter setting is shown in table 22, for example.

TABLE 22

In some embodiments, the parameters tdlsrespondresand TDLSInitiatorAddress may be set in the following manner:

tdlsrespondaddress: the address of the responder terminal; when set as the address of the multilink terminal, indicating that it is desired to establish a multilink connection with the responder terminal; when the address of the logic STA which is set to be subordinate to the multilink terminal indicates that the single-link connection is expected to be established with the designated logic STA in the multilink terminal;

TDLSInitiatorAddress: the address of the originator terminal; when the address of the multilink terminal is set, the establishment of multilink connection with the initiator terminal is accepted; when the address of the logical STA subordinate to the multilink terminal is set, the establishment of a single link connection with the specified logical STA in the multilink terminal is accepted.

In some embodiments, step 3 may be preceded by the steps of:

step A1, SME of initiator terminal sends MLME-TDLSPOTENTIALPEERSTA request primitive to MLME of initiator terminal, the primitive includes:

MACAddress: the address of the TDLS peer terminal requesting communication; the address may be set to an address of the multilink terminal or an address of a logical STA subordinate to the multilink terminal.

Step A2: after receiving MLME-TDLSPOTENTIALPEERSTA. request primitive, MLME-TDLSPOTENTIALPEERSTA. confirm primitive is sent to SME of initiator terminal, and the primitive includes:

MACAddress: MAC address of peer terminal requested by SME;

RSSI: signal value of peer terminal requested by SME.

If the mac address received by the MLME is the address of the multilink terminal, then multiple records of the address and signal values of all active logical STAs in the multilink terminal are contained in the MLME-tdlspotentilpeersta. confirm primitive, as shown in table 23, for example.

TABLE 23

MACAddress	RSSI
		Address1	R1
Address2	R2
		Address3	R3

If the MLME receives the mac address as the address of the logical STA belonging to the multilink terminal, only one record is included in the MLME-tdlspotentilpeersta.

The SME of the initiator terminal requests the information of the specified terminal from the MLME through the MLME-TDLSPOTENTIALPEERSTA request primitive, and then the MLME performs measurement or directly feeds back the existing measurement data. Alternatively, the SME may request information of multiple terminals or multiple logical STAs (that is, the mac address of the multiple multilink terminals or the addresses of multiple logical STAs may be included in the parameter mac address of the MLME-tdlspartentilpeersta request primitive), and then make a judgment, and select a suitable terminal or logical STA from the addresses as a TDLS peer terminal or logical STA.

The embodiment of the application provides a terminal, which comprises a high-level management unit and a low-level management unit, wherein,

a high-level management unit, configured to send an MLME-tdlssetpresponse request primitive to a low-level management unit after receiving the MLME-tdlssetpresponse request primitive, where the MLME-tdlssetpresponse request primitive includes parameters TDLSInitiatorAddress and tdlssetprpesponse, and the tdlssetprpesponse parameter is used to indicate a TDLS setup response parameter, and the tdlssetprpesponse parameter includes a parameter status code and an EHT Capabilities2, where the status code is used to indicate whether a responder terminal accepts setup of a tunnel direct link, and the EHT Capabilities2 is used to indicate an EHT system capability parameter of the responder terminal; when the status code indicates that the responder terminal accepts establishment of the tunnel direct Link, the tdlssetuprpresponse parameter and the TDLS Setup Response frame further include a parameter Link info, and the Link info is used for indicating established Link information.

The embodiment of the present application provides a terminal, where the terminal includes a processor and a memory, where at least one program code is stored in the memory, and the at least one program code is loaded and executed by the processor, so as to implement the method for establishing a tunnel direct link according to the above embodiment.

The embodiment of the present application further provides a storage medium, where at least one program code is stored in the storage medium, and the at least one program code is loaded and executed by a processor, so as to implement the method for establishing a tunnel direct link according to the foregoing embodiment.

It should be understood that, in various embodiments of the present application, the sequence numbers of the above-mentioned processes do not mean the execution sequence, some or all of the steps may be executed in parallel or executed sequentially, and the execution sequence of each process should be determined by its function and inherent logic, and should not constitute any limitation to the implementation process of the embodiments of the present application.

Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

It is clear to those skilled in the art that, for convenience and brevity of description, the specific working processes of the above-described systems, apparatuses and units may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.

In the several embodiments provided in the present application, it should be understood that the disclosed system, apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. For example, the flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of apparatus, methods and computer program products according to various embodiments of the present application. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.

The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.

In addition, functional units in the embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit.

The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer readable storage medium. Based on such understanding, the technical solution of the present application or portions thereof that substantially contribute to the prior art may be embodied in the form of a software product stored in a storage medium and including instructions for causing a computer device (which may be a personal computer, a server, a network device or a terminal device, etc.) to execute all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: u disk, removable hard disk, ROM, RAM) magnetic or optical disk, or the like.

The terminology used in the embodiments of the present application is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. As used in the examples of this application and the appended claims, the singular forms "a", "an", and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and/or" as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items. The character "/" herein generally indicates that the former and latter associated objects are in an "or" relationship.

The word "if" or "if" as used herein may be interpreted as "at … …" or "when … …" or "in response to a determination" or "in response to a detection", depending on the context. Similarly, the phrases "if determined" or "if detected (a stated condition or event)" may be interpreted as "when determined" or "in response to a determination" or "when detected (a stated condition or event)" or "in response to a detection (a stated condition or event)", depending on the context.

The above description is only for the specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present application, and shall be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. A method for tunneled direct link setup, comprising:

when the status code indicates that the responder terminal accepts establishment of a tunnel direct Link, the TDLS Setup Response frame and the TDLSSetupResponse parameter further include a parameter Linkinfo, the Linkinfo is used for indicating established Link information, a high-level management unit of the initiator terminal sends an MLME-TDLSSETUPCONFIRM.request primitive to a low-level management unit, the MLME-TDLSSETUPCONFIRM.request primitive includes parameters TDLSRespondedrAres and TDLSSetupConfirm, the TDLSSetupConfirm parameter is used for indicating a TDLS establishment confirmation parameter, the TDLSSetupConfirm parameter includes parameters EHT Operation1 and Link info, and the EHT Operation1 is used for indicating an EHT system Operation parameter of the initiator terminal;

2. The method of claim 1, wherein the EHT Capabilities1 includes parameters MAC Capability and PHY Capability, the MAC Capability including one or more of the following parameters:

trigger P2P support for indicating whether to support point-to-point data transmission Triggered by the access device;

a Multi link support for indicating whether a multilink operation is supported;

a Multi AP support for indicating whether a Multi-point cooperative operation is supported;

a 1024-bit BA bitmap support for indicating whether to support bitmap block feedback of a maximum 1024-bit;

an STR support for indicating whether simultaneous independent transmission and reception is supported;

one or more of the following parameters are included in the PHY Capability:

an EHT MU with 4 × LTF +0.8 μ s GI to indicate whether reception of an EHU MU PPDU with 4 × LTF and 0.8 μ s guard interval is supported;

an 80MHz in 160/80+80MHz EHT PPDU for indicating whether Orthogonal Frequency Division Multiplexing Access (OFDMA) is supported using 160MHz or 80MHz +80MHz resource units over an 80MHz bandwidth;

an 80MHz in 320/160+160MHz EHT PPDU for indicating whether OFDMA is supported to be performed using 320MHz or 160MHz +160MHz resource units over an 80MHz bandwidth;

an 80MHz in 240/160+80MHz EHT PPDU for indicating whether OFDMA is supported for execution using 240MHz or 160MHz +80MHz resource units over an 80MHz bandwidth.

3. The method of claim 1, wherein the EHT Operation1 contains one or more of the following parameters:

a Channel Width field for indicating a Channel bandwidth of an operation;

a CCFS field for indicating a channel center frequency band;

the Basic EHT-MCS and NSS set is used for indicating a modulation coding strategy supported by an EHT system corresponding to each group of space stream number in the receiving and transmitting of the EHT PPDU;

an Align start time of PPDU for indicating whether to start sending PPDU on different links at the same time;

an Align end time of PPDU for indicating whether to finish sending PPDU on different links at the same time.

4. The method of claim 1, wherein when the local parameter dot11multilink operation executed of the initiator terminal indicates that the initiator terminal supports multilink operation capability or indicates that the initiator terminal supports multilink operation capability and starts the operation, the tdlssetup Request parameter, the TDLS Setup Request frame, the tdlssetup response parameter, and the TDLS Setup Confirm frame further include a parameter ML Elements1, and the ML Elements1 are used for indicating the multilink parameter of the initiator terminal.

5. The method of claim 2, wherein when the local parameter dot11multilink operation executed of the initiator terminal indicates that the initiator terminal supports the multilink operation capability or indicates that the initiator terminal supports the multilink operation capability and starts the operation, the EHT Capabilities1 further includes a parameter ML Elements1, and the ML Elements1 is used for indicating the multilink parameter of the initiator terminal.

6. The method of claim 5, wherein the ML Elements1 is contained in the MAC Capabilities of the EHT Capabilities1, and wherein the ML Elements1 contains the Multi link support.

7. The method of claim 3, wherein when the local parameter dot11multilink Operation executed of the initiator terminal indicates that the initiator terminal supports the multilink Operation capability or indicates that the initiator terminal supports the multilink Operation capability and starts the Operation, the EHT Operation1 further includes a parameter ML Elements1, where ML Elements1 are used to indicate the multilink parameter of the initiator terminal.

8. The method of claim 7, wherein the ML Elements1 contains the Align start time of PPDU and the Align end time of PPDU.

9. The method of any of claims 4-8, wherein said ML Elements1 contains parameters MLD common info1 and STA info i, said MLD common info1 is used to indicate the multilink common parameters of the initiator terminal, said STA info i is used to indicate the proprietary parameters of a single logical STA in the initiator terminal, 1 ≦ i ≦ n, n is determined by the number of logical STAs actually operating in the initiator terminal.

10. The method of claim 9, wherein the STA info i comprises Link ID, STA Capability and STA operation, the Link ID is used to indicate an identifier of a Link operated by the logical STA, the STA Capability is used to indicate a Capability parameter specific to the logical STA, and the STA operation is used to indicate an operation parameter specific to the logical STA.

11. The method of claim 1, wherein when a local parameter dot11multilink operation executed of the responder terminal indicates that the responder terminal supports multilink operation capability or indicates that the responder terminal supports multilink operation capability and starts the operation, the tdlssetup Response frame and the TDLS Setup Response frame further include a parameter ML Elements2, and the ML Elements2 is used for indicating multilink parameters of the responder terminal.

12. The method according to claim 1, wherein the Linkinfo includes parameters TDLS initiator STA Address and TDLS responder STA Address, the TDLS initiator STA Address is used for indicating the Address of the initiator terminal, and the TDLS responder STA Address is used for indicating the Address of the responder terminal.

13. The method according to claim 12, wherein the Link info further contains parameter MLD ID and/or Link ID, the MLD ID is used to identify the address or identification of the multilink device, and the Link ID is used to indicate the identification of the Link operated by the logical STA.

14. The method of claim 1, wherein when the tdlsrespondedraddress is set to an address of a multilink terminal, it indicates that it is desired to establish a multilink connection with a responder terminal; when the tdlsrespondres is set to the address of a logical STA subordinate to the multilink terminal, it indicates that it is desired to establish a single link connection with a logical STA designated in the responder terminal.

15. The method of claim 1, wherein before the higher management unit of the originator terminal sends the MLME-tdlssetup request primitive to the lower management unit, the method further comprises:

a high-level management unit of an initiator terminal sends an MLME-TDLSPOTENTIALPEERSTA request primitive to a low-level management unit, wherein the MLME-TDLSPOTENTIALPEERSTA request primitive comprises a parameter MACAddress, and the MACAddress is used for indicating the address of a TDLS peer terminal requesting communication and can be set as the address of a multilink terminal or the address of a logic STA affiliated to the multilink terminal;

after receiving the MLME-TDLSPOTENTIALPEERSTA.request primitive, the lower management unit of the initiator terminal sends an MLME-TDLSPOTENTIALPEERSTA.confirm primitive to the higher management unit, wherein the MLME-TDLSPOTENTIALPEERSTA.confirm primitive comprises parameters MACAddress and RSSI, and the RSSI is used for indicating the signal value of the terminal corresponding to the address of the MACAddress.

16. The method according to claim 15, wherein if the mac address received by the lower management unit of the initiator terminal is the address of the multilink terminal, the MLME-tdlspartentilpeersta. confirm primitive contains the address and signal value of all activated logical STAs in the multilink terminal; if the lower management unit of the initiator terminal receives that the MACAddress is the address of the logical STA belonging to the multilink terminal, the address and the signal value of the logical STA are contained in the MLME-TDLSPOTENTIALPEERSTA.

17. The method of claim 1, wherein the higher layer management unit is an equipment management unit (SME) or an application management unit (AME), and the lower layer management unit is a Media Access Control (MAC) layer management unit (MLME) or a physical layer management unit (PLME).

18. A method for tunneled direct link setup, comprising:

the lower layer management unit of the responder terminal sends an MLME-TDLSSETUPCFIRM.indication primitive to the higher layer management unit, wherein the MLME-TDLSSETUPCFIRM.indication primitive comprises parameters TDLSInitiatorAddress and TDLSSetupConfirm, and the TDLSSetupConfirm parameter comprises parameters EHT Operation1 and Linkinefo.

19. The method of claim 18, wherein the EHT Capabilities2 includes parameters MAC Capability and PHY Capability, the MAC Capability including one or more of the following parameters:

a Multi link support for indicating whether a multilink operation is supported;

one or more of the following parameters are included in the PHY Capability:

an 80MHz 320/160+160MHz EHT PPDU for indicating whether OFDMA is supported to be performed using 320MHz or 160MHz +160MHz resource units over an 80MHz bandwidth;

20. The method of claim 18, wherein when a local parameter dot11multilink operation executed of the responder terminal indicates that the responder terminal supports multilink operation capability or indicates that the responder terminal supports multilink operation capability and starts the operation, the TDLS Setup Response frame further includes a parameter ML Elements2, and the ML Elements2 is used for indicating the multilink parameter of the responder terminal.

21. The method for tunnel direct link setup according to claim 19, wherein when a local parameter dot11multilink operation executed of the responder terminal indicates that the responder terminal supports multilink operation capability or indicates that the responder terminal supports multilink operation capability and starts the operation, a parameter ML Elements2 is further included in the EHT Capabilities2, and the ML Elements2 are used for indicating multilink parameters of the responder terminal.

22. The method of claim 21, wherein the ML Elements2 are included in the MAC Capabilities of the EHT Capabilities2, and wherein the Multi link support is included in the ML Elements 2.

23. The method of any of claims 20-22, wherein said ML Elements2 include parameters MLD common info2 and STA info j, said MLD common info2 indicating multilink common parameters of the responder terminal, said STA info j indicating proprietary parameters of a single logical STA in the responder terminal, 1 ≦ j ≦ m, m being determined by the number of logical STAs actually operating in the responder terminal.

24. The method of claim 23, wherein the STA info j comprises Link ID, STA Capability and STA operation, the Link ID is used to indicate an identity of a Link operated by the logical STA, the STA Capability is used to indicate a Capability parameter specific to the logical STA, and the STA operation is used to indicate an operation parameter specific to the logical STA.

25. The method of claim 18, wherein when the local parameter dot11multilink operation executed of the initiator terminal indicates that the initiator terminal supports multilink operation capability or indicates that the initiator terminal supports multilink operation capability and starts the operation, the TDLSSetupRequest parameter, the TDLS Setup Request frame, the TDLSSetupConfirm parameter, and the TDLS Setup Confirm frame further include a parameter ML Elements1, and the ML Elements1 is used for indicating the multilink parameter of the initiator terminal.

26. The method according to claim 18, wherein the Link info includes parameters TDLS initiator STA Address for indicating an Address of the initiator terminal and TDLS responder STA Address for indicating an Address of the responder terminal.

27. The method of claim 26, wherein the Link info further comprises parameter MLD ID and/or Link ID, the MLD ID is used for identifying the address or identification of the multi-Link device, and the Link ID is used for indicating the identification of the Link operated by the logical STA.

28. The method according to claim 18, wherein when the TDLSInitiatorAddress is set to the address of the multilink terminal, it indicates acceptance of establishing the multilink connection with the originator terminal; and when the TDLSInitiatorAddress is set as the address of the logic STA affiliated to the multilink terminal, the single link connection established with the logic STA appointed in the initiator terminal is accepted.

29. The method of claim 18, wherein the higher layer management unit is an equipment management unit (SME) or an application management unit (AME), and the lower layer management unit is a Media Access Control (MAC) layer management unit (MLME) or a physical layer management unit (PLME).

30. A terminal comprising a higher level management unit and a lower level management unit,

31. A terminal comprising a higher level management unit and a lower level management unit,

the system comprises a lower-layer management unit, a higher-layer management unit and a TDLS (multicast service Request) unit, wherein the lower-layer management unit is used for sending an MLME-TDLSSETUPREQUEST-indication primitive to the higher-layer management unit after receiving a TDLS Setup Request frame sent by an initiator terminal, the MLME-TDLSSETUPREQUEST-indication primitive comprises parameters TDLSINitiatedAddress and TDLSSetupRequest, the TDLSInitiatedAddress parameter is used for indicating the address of the initiator terminal, the TDLSSetupRequest parameter is used for indicating a TDLS establishment Request parameter, the TDLSSetupRequest parameter comprises a parameter EHT Capabilities1, and the EHT Capabilities1 is used for indicating an EHT system capability parameter of the initiator terminal; after receiving MLME-TDLS SETUPRESPONSE.REQUEST primitive, sending a TDLS Setup Response frame to the initiator terminal, wherein the TDLS Setup Response frame comprises the parameter status code and EHT Capabilities 2; when the status code indicates that a responder terminal accepts establishment of a tunnel direct link, receiving a TDLS Setup Confirm frame sent by an initiator terminal, wherein the TDLS Setup Confirm frame comprises parameters EHT Operation1 and Linkinefo, and the EHT Operation1 is used for indicating an EHT system Operation parameter of the sender terminal; sending an MLME-TDLSSETUPCONFIRM.indication primitive to a high-level management unit, wherein the MLME-TDLSSETUPCONFIRM.indication primitive comprises parameters TDLSInitiatorAddress and TDLSSetupConfirm, and the TDLSSetupConfirm parameter comprises parameters EHT Operation1 and Link info;

a high-level management unit, configured to send an MLME-tdlssetuproprequest.request primitive to a low-level management unit after receiving the MLME-tdlssetuproprequest.indication primitive, where the MLME-tdlssetuponsse.request primitive includes parameters TDLSInitiatorAddress and tdlssetresponsee, the tdlssetresponsee parameter is used to indicate a TDLS setup response parameter, the tdlssetresponsee parameter includes parameters status code and EHT Capabilities2, the status code is used to indicate whether the responder terminal accepts setup of the tunnel direct link, and the EHT Capabilities2 is used to indicate the EHT system capability of the responder terminal; when the status code indicates that the responder terminal accepts establishment of a tunnel direct link, the tdlssetup Response parameter and the TDLS Setup Response frame further include a parameter Linkinfo, and the Linkinfo is used for indicating established link information.

32. A terminal, characterized in that the terminal comprises a processor and a memory, in which at least one program code is stored, which is loaded and executed by the processor to implement the method for tunneled direct link setup according to any of claims 1-29.

33. A storage medium having stored therein at least one program code, which is loaded and executed by a processor, to implement the method of tunneled direct link setup according to any of claims 1-29.