Performing proprietary link manager feature discovery and exchange with a peer proprietary device

1. A method of wireless communication performed by a first device, the method comprising:

transmitting a non-proprietary link manager protocol (LMP) version request protocol data unit (PDU) to a second device;

receiving a LMP version response PDU from the second device, the LMP version response PDU including at least one of a link layer identification, a version number, or a sub-version number associated with the second device;

determining if one or more of the link layer identification, the version number, or the sub-version number included in the LMP version response PDU are associated with a recognized proprietary link manager (QLM); and

transmitting a first LMP encapsulated header PDU that includes a first QLM protocol (QLMP) feature request opcode to the second device when it is determined that one or more of the link layer identification, the version number, or the sub-version number included in the LMP version response PDU are associated with the recognized QLM.

2. The method of claim 1 , further comprising:

receiving a first LMP accepted PDU when the QLMP feature request opcode is recognized by the second device;

receiving a LMP not accepted PDU when the QLMP feature request opcode is not recognized by the second device;

transmitting a first LMP encapsulated payload PDU including a QLMP feature request payload to the second device, the QLMP feature request payload including a first bit mask that indicates a first set of QLMP features associated with the first device;

receiving a second LMP accepted PDU when the first LMP encapsulated payload PDU is received by the second device;

receiving a second LMP encapsulated header PDU that includes a second QLMP opcode;

receiving a second LMP encapsulated payload PDU including a QLMP feature response payload from the second device, the QLMP feature response payload including a second bit mask that indicates a second set of QLMP features associated with the second device; and

determining the second set of QLMP features associated with the second device based on the second bit mask.

3. The method of claim 2 , wherein the second set of QLMP features associated with the second device includes virtual addressing, the method further comprising:

transmitting a third LMP encapsulated header PDU to the second device, the third LMP encapsulated header PDU including at least in part a QLMP virtual address opcode;

receiving a third LMP accepted PDU when the third LMP encapsulated header PDU is received by the second device;

transmitting a third encapsulated payload PDU that includes a virtual address payload to the second device, the virtual address payload indicating a virtual address that is associated with both the first device and the second device;

receiving a fourth LMP encapsulated header PDU that includes a QLMP accepted opcode when the virtual address is accepted by the second device; and

transmitting a fourth LMP accepted PDU when the fourth LMP encapsulated header PDU is received by the first device.

4. The method of claim 2 , wherein the second set of QLMP features associated with the second device includes a split asynchronous connectionless (ACL) link, the method further comprising:

transmitting a third LMP encapsulated header PDU that includes a QLMP split ACL opcode to the second device;

receiving a third LMP accepted PDU when the third LMP encapsulated header PDU is received by the second device;

transmitting a third LMP encapsulated payload PDU that includes a QLMP split ACL payload to the second device;

receiving a fourth LMP encapsulated header PDU that includes a QLMP accepted opcode when split ACL is enabled at the second device; and

enabling split ACL at the first device.

5. A method of wireless communication performed by a first device, the method comprising:

receiving a non-proprietary link manager protocol (LMP) version request protocol data unit (PDU) from a second device;

transmitting a LMP version response PDU to the second device, the LMP version response PDU including at least one of a link layer identification, a version number, or a sub-version number associated with the first device; and

receiving a first LMP encapsulated header PDU that includes a first proprietary link manager protocol (QLMP) feature request opcode from the second device when one or more of the link layer identification, the version number, or the sub-version number included in the LMP version response PDU are associated with a proprietary link manager (QLM) recognized by the second device.

6. The method of claim 5 , further comprising:

transmitting a first LMP accepted PDU when the QLMP feature request opcode is recognized by the first device;

transmitting a LMP not accepted PDU when the QLMP feature request opcode is not recognized by the first device;

receiving a first LMP encapsulated payload PDU including a QLMP feature request payload from the second device, the QLMP feature request payload including a first bit mask that indicates a first set of QLMP features associated with the second device;

transmitting a second LMP accepted PDU when the first LMP encapsulated payload PDU is received by the first device;

transmitting a second LMP encapsulated header PDU that includes a second QLMP opcode; and

transmitting a second LMP encapsulated payload PDU including a QLMP feature response payload to the second device, the QLMP feature response payload including a second bit mask that indicates a second set of QLMP features associated with the first device.

7. The method of claim 6 , wherein when the first set of QLMP features associated with the first device includes virtual addressing, the method further comprises:

receiving a third LMP encapsulated header PDU from the second device, the third LMP encapsulated header PDU including at least in part a QLMP virtual address opcode;

transmitting a third LMP accepted PDU when the third LMP encapsulated header PDU is received by the first device;

receiving a third encapsulated payload PDU that includes a virtual address payload from the second device, the virtual address payload indicating a virtual address that is associated with both the first device and the second device;

transmitting a fourth LMP encapsulated header PDU that includes a QLMP accepted opcode when the first device accepts the virtual address; and

receiving a fourth LMP accepted PDU when the fourth LMP encapsulated header PDU is received by the second device.

8. The method of claim 7 , further comprising:

transmitting a LMP host connection request to a third device;

receiving a fifth encapsulated header PDU that includes a QLMP actual address request opcode from the third device;

transmitting a fifth LMP accepted PDU when the fifth encapsulated header PDU is received by the third device;

transmitting a sixth encapsulated header PDU that includes a QLMP actual address response opcode to the third device;

receiving a sixth LMP accepted PDU when the sixth encapsulated header PDU is received by the third device;

transmitting a fourth LMP encapsulated payload PDU including a QLMP actual address payload to the third device; and

establishing a connection with the third device.

9. The method of claim 6 , wherein when the first set of QLMP features associated with the first device includes a split asynchronous connectionless (ACL) link, the method further comprises:

receiving a third LMP encapsulated header PDU that includes a QLMP split ACL opcode from the second device;

transmitting a third LMP accepted PDU when the third LMP encapsulated header PDU is received by the first device;

enabling split ACL at the first device; and

transmitting a fourth LMP encapsulated header PDU that includes a QLMP accepted opcode when split ACL is enabled at the first device.

10. A method of wireless communication performed by a first device, the method comprising:

receiving information from a second device that includes a virtual address associated with the second device and a third device;

disconnecting from the second device;

transmitting a first non-proprietary link manager protocol (LMP) encapsulated header protocol data unit (PDU) including a proprietary link manager protocol (QLMP) virtual paging opcode to the third device that is paired with the second device;

receiving a first LMP accepted PDU when the first LMP encapsulated header PDU is received by the third device;

receiving a second LMP encapsulated header PDU including a QLMP accepted opcode from the third device;

transmitting a second LMP accepted PDU to the third device when the second LMP encapsulated header PDU is received;

receiving a LMP host connection request PDU from the third device; and

establishing a connection with the third device.

11. An apparatus for wireless communication for a first device, comprising:

a memory; and

at least one processor coupled to the memory and configured to:

transmit a non-proprietary link manager protocol (LMP) version request protocol data unit (PDU) to a second device;

receive a LMP version response PDU from the second device, the LMP version response PDU including at least one of a link layer identification, a version number, or a sub-version number associated with the second device;

determine if one or more of the link layer identification, the version number, or the sub-version number included in the LMP version response PDU are associated with a recognized proprietary link manager (QLM); and

transmit a first LMP encapsulated header PDU that includes a first QLM protocol (QLMP) feature request opcode to the second device when it is determined that one or more of the link layer identification, the version number, or the sub-version number included in the LMP version response PDU are associated with the recognized QLM.

12. The apparatus of claim 11 , wherein the at least one processor is further configured to:

receive a first LMP accepted PDU when the QLMP feature request opcode is recognized by the second device;

receive a LMP not accepted PDU when the QLMP feature request opcode is not recognized by the second device;

transmit a first LMP encapsulated payload PDU including a QLMP feature request payload to the second device, the QLMP feature request payload including a first bit mask that indicates a first set of QLMP features associated with the first device;

receive a second LMP accepted PDU when the first LMP encapsulated payload PDU is received by the second device;

receive a second LMP encapsulated header PDU that includes a second QLMP opcode;

receive a second LMP encapsulated payload PDU including a QLMP feature response payload from the second device, the QLMP feature response payload including a second bit mask that indicates a second set of QLMP features associated with the second device; and

determine the second set of QLMP features associated with the second device based on the second bit mask.

13. The apparatus of claim 12 , wherein the second set of QLMP features associated with the second device includes virtual addressing, and wherein the at least one processor is further configured to:

transmit a third LMP encapsulated header PDU to the second device, the third LMP encapsulated header PDU including at least in part a QLMP virtual address opcode;

receive a third LMP accepted PDU when the third LMP encapsulated header PDU is received by the second device;

transmit a third encapsulated payload PDU that includes a virtual address payload to the second device, the virtual address payload indicating a virtual address that is associated with both the first device and the second device;

receive a fourth LMP encapsulated header PDU that includes a QLMP accepted opcode when the virtual address is accepted by the second device; and

transmit a fourth LMP accepted PDU when the fourth LMP encapsulated header PDU is received by the first device.

14. The apparatus of claim 12 , wherein the second set of QLMP features associated with the second device includes a split asynchronous connectionless (ACL) link, and wherein the at least one processor is further configured to:

transmit a third LMP encapsulated header PDU that includes a QLMP split ACL opcode to the second device;

receive a third LMP accepted PDU when the third LMP encapsulated header PDU is received by the second device;

transmit a third LMP encapsulated payload PDU that includes a QLMP split ACL payload to the second device;

receive a fourth LMP encapsulated header PDU that includes a QLMP accepted opcode when split ACL is enabled at the second device; and

enable split ACL at the first device.