Wireless docking

• US 9,547,619 B2
• Filed: 04/30/2014
• Issued: 01/17/2017
• Est. Priority Date: 05/24/2013
• Status: Active Grant

• Current Assignee: Qualcomm, Inc.
• Original Assignee: Qualcomm, Inc.
• Inventors: Huang, Xiaolong, De Vegt, Rolf, Davidson, Andrew Mackinnon, Raveendran, Vijayalakshmi Rajasundaram
• Primary Examiner(s): AUVE, GLENN ALLEN
• Application Number:
  US14/265,740
• Publication Number:
  US 20140351475A1
• Time in Patent Office: 993 Days
• Field of Search: 710/303
• US Class Current: 1/1
• CPC Class Codes: G06F 1/1632 External expansion units, e.g. docking stations
• CPC Class Codes: G06F 13/4068 Electrical coupling
• CPC Class Codes: H04L 67/51 Discovery or management thereof, e.g. service location protocol [SLP] or web services
• CPC Class Codes: H04M 1/00 Substation equipment, e.g. for use by subscribers subscriber services or facilities provided at exchanges H04M3/00; prepayment telephone coin boxes H04M17/00; current supply arrangements H04M19/08
• CPC Class Codes: H04M 1/72412 using two-way short-range wireless interfaces
• CPC Class Codes: H04W 76/10 Connection setup
• CPC Class Codes: H04W 8/005 Discovery of network devices, e.g. terminals
• CPC Class Codes: H04W 84/18 Self-organising networks, e.g. ad-hoc networks or sensor networks

Abstract

In one example, a method includes determining, by a wireless dockee (WD), one or more peripheral functions (PFs) associated with a wireless docking center (WDC). In this example, the method further includes establishing a docking session via a direct wireless connection between the WD and the WDC. In this example, the method further includes selecting, by the WD, at least one PF of the one or more PFs associated with the WDC. In this example, the method further includes accessing, by the WD, the at least one PF of the one or more PFs associated with the WDC.

Claims

1. A method for wireless docking, the method comprising:

determining, by a wireless dockee (WD), one or more peripheral functions (PFs) associated with a wireless docking center (WDC);

establishing a docking session via a direct wireless connection between the WD and the WDC;

selecting, by the WD, at least one PF of the one or more PFs associated with the WDC, wherein selecting includes sending, by the WD and to the WDC, a message that indicates whether the WD is selecting PFs by individually identifying the at least one PF in the message or by selecting a default set of PFs that includes the at least one PF without individually identifying the at least one PF in the message; and

accessing, by the WD, the at least one PF of the one or more PFs associated with the WDC, wherein accessing the at least one PF of the one or more PFs associated with the WDC comprises establishing, for a respective PF of the at least one PF of the one or more PFs associated with the WDC, a respective session between a corresponding PF service of the WD and a corresponding PF service of the WDC.

2. The method of claim 1,

wherein the determining the one or more PFs associated with the WDC comprises determining, by a docking service of the WD, the one or more PFs associated with the WDC;

wherein establishing the docking session via the direct wireless connection between the WD and the WDC comprises establishing, by the docking service of the WD, the docking session via the direct wireless connection between the WD and the WDC;

wherein selecting, by the WD, the at least one PF of the one or more PFs associated with the WDC comprises selecting, by the docking service of the WD, the at least one PF of the one or more PFs associated with the WDC; and

wherein accessing, by the WD, the at least one PF of the one or more PFs associated with the WDC comprises accessing, by the docking service of the WD, the at least one PF of the one or more PFs associated with the WDC.

3. The method of claim 1, wherein determining, by the WD, the one or more PFs associated with the WDC comprises:

performing, by the WD, docking pre-association discovery with the WDC for information regarding the one or more PFs associated with the WDC.

4. The method of claim 3, wherein determining, by the WD, the one or more PFs associated with the WDC comprises:

receiving, by the WD and from the WDC, an indication of the one or more PFs associated with the WDC.

5. The method of claim 4, wherein receiving the indication of the one or more PFs associated with the WDC comprises receiving a message from the WDC that indicates one or more characteristics of the WDC.

6. The method of claim 5, wherein the one or more characteristics indicated by the message include:

a device type;

a device name;

a device availability;

the indication of the one or more PFs associated with the WDC; and

one or more docking environment types.

7. The method of claim 5, wherein the message comprises a UTF-8 text string of XML data that includes a preassociationServiceDiscovery element.

8. The method of claim 4, further comprising

sending, by the WD and to the WDC, a request for information regarding the one or more PFs associated with the WDC.

9. The method of claim 8, wherein sending, by the WD and to the WDC, the request for the information regarding the one or more PFs associated with the WDC comprises:

executing, by the WD, a SeekService method based on the following parameters;

a service name value, an exact search value, a MAC address value, and a service information request value.

10. The method of claim 9, wherein the service name value comprises org.wi-fi.wfds.docking.wdc, and wherein the exact search value is set to TRUE.

11. The method of claim 9, wherein receiving the indication of the one or more PFs associated with the WDC comprises receiving a message from the WDC that indicates one or more characteristics of the WDC, and wherein the service information request value includes a subset of a string of text included in the message received from the WDC that indicates the one or more characteristics of the WDC.

12. The method of claim 4, further comprising:

responsive to determining that the indication of the one or more PFs associated with the WDC indicates one or more PFs sought by the WD, establishing the docking session.

13. The method of claim 12, further comprising:

determining, by the WD and based on user input, the one or more PFs sought by the WD.

14. The method of claim 1, wherein establishing the docking session comprises:

performing, by the WD, docking connection setup exchange between the WD and the WDC; and

performing, by the WD, docking ASP (application service platform) session setup between the WD and the WDC.

15. The method of claim 1, wherein establishing the docking session comprises:

forming a peer-to-peer (P2P) group that includes both the WD and WDC.

16. The method of claim 1, wherein establishing the docking session comprises:

executing, by the WD, a ConnectSessions method based on the following parameters;

a service MAC value, an advertisement identification value, a session information value, and a network role value, wherein the service MAC value indicates a MAC address of the WDC and the advertisement identification value indicates a docking service of the WDC.

17. The method of claim 1, wherein selecting, by the WD, the at least one PF of the one or more PFs associated with the WDC comprises:

exchanging, by the WD and with the WDC, docking configuration and control protocol communications.

18. The method of claim 1, further comprising:

querying, by the WD and during operation of the docking session, the WDC for information regarding the one or more PFs associated with the WDC.

19. The method of claim 1, wherein the message that indicates whether the WD is selecting PFs by individually identifying the at least one PF in the message or by selecting a default set of PFs that includes the at least one PF without individually identifying the at least one PF further includes a request to access one or more sought PFs of the one or more PFs associated with the WDC, and wherein selecting, by the WD, the at least one PF of the one or more PFs associated with the WDC further comprises:

receiving, by the WD and from the WDC, a message indicating whether or not the WDC accepts the request for the WD to access the one or more sought PFs; and

responsive to determining that the WDC accepts the request, accessing, by the WD, the one or more sought PFs, wherein the one or more sought PFs includes the at least one PF.

20. The method of claim 19, wherein the request individually identifies the one or more sought PFs.

21. The method of claim 19, wherein a default set of PFs of the one or more PFs associated with the WDC includes the one or more sought PFs, and wherein the request does not individually identify the one or more sought PFs.

22. The method of claim 1, wherein establishing, for the respective PF of the at least one PF of the one or more PFs associated with the WDC, the respective session between the corresponding PF service of the WD and the corresponding PF service of the WDC comprises:

sending, by the WD and to the WDC, a message that includes an advertisement identification value that corresponds to the respective PF.

23. The method of claim 1, further comprising one or more of:

sending, by the corresponding PF service of the WD to the corresponding PF service of the WDC and via the respective session, output data; and

receiving, by the corresponding PF service of the WD from the corresponding PF service of the WDC and via the respective session, input data.

24. The method of claim 1, further comprising:

receiving, by the WD and from the WDC and at a first time, a message that includes information regarding the one or more PFs associated with the WDC; and

receiving, by the WD and from the WDC and at a second, later, time, a second message indicating that the information regarding the one or more PFs associated with the WDC has changed.

25. The method of claim 1, further comprising:

deselecting, by the WD, the at least one PF of the one or more PFs associated with the WDC, wherein deselecting comprises;

sending, by the WD and to the WDC, a notification that the WD is deselecting the at least one PF of the one or more PFs associated with the WDC; and

closing a corresponding session between a corresponding PF service of the WD and a corresponding PF service of the WDC.

26. A wireless dockee (WD) comprising:

a memory;

one or more processors;

at least one module executable by the one or more processors to;

determine one or more peripheral functions (PFs) associated with a wireless docking center (WDC);

establish a docking session via a direct wireless connection between the WD and the WDC;

select at least one PF of the one or more PFs associated with the WDC, wherein, to select the at least one PF, the at least one module is executable by the one or more processors to send, to the WDC, a message that indicates whether the WD is selecting PFs by individually identifying the at least one PF in the message or by selecting a default set of PFs that includes the at least one PF without individually identifying the at least one PF in the message; and

access the at least one PF of the one or more PFs associated with the WDC, wherein the access the at least one PF, the at least one module is executable by the one or more processors to establish, for a respective PF of the at least one PF of the one or more PFs associated with the WDC, a respective session between a corresponding PF service of the WD and a corresponding PF service of the WDC.

27. The WD of claim 26, wherein the at least one module includes a docking service executable by the one or more processors to:

determine the one or more PFs associated with the WDC;

establish the docking session via the direct wireless connection between the WD and the WDC;

select the at least one PF of the one or more PFs associated with the WDC; and

access the at least one PF of the one or more PFs associated with the WDC.

28. The WD of claim 26, wherein the at least one module is executable by the one or more processors to determine the one or more PFs associated with the WDC by at least:

performing docking pre-association discovery with the WDC for information regarding the one or more PFs associated with the WDC.

29. The WD of claim 28, wherein the at least one module is executable by the one or more processors to determine the one or more PFs associated with the WDC by at least:

receiving, from the WDC, an indication of the one or more PFs associated with the WDC.

30. The WD of claim 29, wherein the at least one module is executable by the one or more processors to receive the indication of the one or more PFs associated with the WDC by at least:

receiving, from the WDC, a message that indicates one or more characteristics of the WDC.

31. The WD of claim 29, wherein the at least one module is further executable by the one or more processors to:

send, to the WDC, a request for information regarding the one or more PFs associated with the WDC.

32. The WD of claim 31, wherein the at least one module is executable by the one or more processors to send, to the WDC, the request for the information regarding the one or more PFs associated with the WDC by at least:

executing a SeekService method based on the following parameters;

a service name value, an exact search value, a MAC address value, and a service information request value.

33. The WD of claim 32, wherein the at least one module is executable by the one or more processors to receive the indication of the one or more PFs associated with the WDC by at least:

receiving a message from the WDC that indicates one or more characteristics of the WDC, and wherein the service information request value includes a subset of a string of text included in the message received from the WDC that indicates the one or more characteristics of the WDC.

34. The WD of claim 29, wherein responsive to determining that the indication of the one or more PFs associated with the WDC indicates one or more PFs sought by the WD, the at least one module is executable by the one or more processors to establishing the docking session.

35. The WD of claim 26, wherein the at least one module is executable by the one or more processors to establish the docking session by at least:

performing docking connection setup exchange between the WD and the WDC; and

performing docking ASP (application service platform) session setup between the WD and the WDC.

36. The WD of claim 26, wherein the at least one module is executable by the one or more processors to establish the docking session by at least:

forming a peer-to-peer (P2P) group that includes both the WD and WDC.

37. The WD of claim 26, wherein the at least one module is executable by the one or more processors to establish the docking session by at least:

executing a ConnectSessions method based on the following parameters;

a service MAC value, an advertisement identification value, a session information value, and a network role value, wherein the service MAC value indicates a MAC address of the WDC and the advertisement identification value indicates a docking service of the WDC.

38. The WD of claim 26, wherein the at least one module is executable by the one or more processors to select the at least one PF of the one or more PFs associated with the WDC by at least:

exchanging, with the WDC, docking configuration and control protocol communications.

39. The WD of claim 26, wherein the at least one module is further executable by the one or more processors to:

query, during operation of the docking session, the WDC for information regarding the one or more PFs associated with the WDC.

40. The WD of claim 26, wherein the message that indicates whether the WD is selecting PFs by individually identifying the at least one PF in the message or by selecting a default set of PFs that includes the at least one PF without individually identifying the at least one PF further includes a request to access one or more sought PFs of the one or more PFs associated with the WDC, and wherein the at least one module is further executable by the one or more processors to select the at least one PF of the one or more PFs associated with the WDC by at least:

receiving, from the WDC, a message indicating whether or not the WDC accepts the request for the WD to access the one or more sought PFs; and

responsive to determining that the WDC accepts the request, accessing the one or more sought PFs, wherein the one or more sought PFs includes the at least one PF.

41. The WD of claim 40, wherein the request individually identifies the one or more sought PFs.

42. The WD of claim 40, wherein a default set of PFs of the one or more PFs associated with the WDC includes the one or more sought PFs, and wherein the request does not individually identify the one or more sought PFs.

43. The WD of claim 26, wherein the at least one module is further executable by the one or more processors to one or more of:

send, by the corresponding PF service of the WD to the corresponding PF service of the WDC and via the respective session, output data; and

receive, by the corresponding PF service of the WD from the corresponding PF service of the WDC and via the respective session, input data.

44. The WD of claim 26, wherein the at least one module is further executable by the one or more processors to:

receive, from the WDC and at a first time, a message that includes information regarding the one or more PFs associated with the WDC; and

receive, from the WDC and at a second, later, time, a second message indicating that the information regarding the one or more PFs associated with the WDC has changed.

45. The WD of claim 26, wherein the at least one module is further executable by the one or more processors to:

deselect the at least one PF of the one or more PFs associated with the WDC, wherein the at least one module is executable by the one or more processors to deselect the at least one PF by at least;

sending, to the WDC, a notification that the WD is deselecting the at least one PF of the one or more PFs associated with the WDC; and

closing a corresponding session between a corresponding PF service of the WD and a corresponding PF service of the WDC.

46. A wireless dockee (WD) comprising:

means for determining one or more peripheral functions (PFs) associated with a wireless docking center (WDC);

means for establishing a docking session via a direct wireless connection between the WD and the WDC;

means for selecting at least one PF of the one or more PFs associated with the WDC, wherein the means for selecting include means for sending, to the WDC, a message that indicates whether the WD is selecting PFs by individually identifying the at least one PF in the message or by selecting a default set of PFs that includes the at least one PF without individually identifying the at least one PF in the message; and

means for accessing the at least one PF of the one or more PFs associated with the WDC, wherein the means for accessing the at least one PF comprise means for establishing, for a respective PF of the at least one PF of the one or more PFs associated with the WDC, a respective session between a corresponding PF service of the WD and a corresponding PF service of the WDC.

47. A non-transitory computer-readable storage medium stores instructions that, when executed, cause one or more processors of a wireless dockee (WD) to:

determine one or more peripheral functions (PFs) associated with a wireless docking center (WDC);

establish a docking session via a direct wireless connection between the WD and the WDC;

select at least one PF of the one or more PFs associated with the WDC, wherein the instructions that cause the one or more processors to select the at least one PF include instructions that cause the one or more processors to send, to the WDC, a message that indicates whether the WD is selecting PFs by individually identifying the at least one PF in the message or by selecting a default set of PFs that includes the at least one PF without individually identifying the at least one PF in the message; and

access the at least one PF of the one or more PFs associated with the WDC, wherein the instructions that cause the one or more processors to access that at least one PF comprise instructions that cause the one or more processors to establish, for a respective PF of the at least one PF of the one or more PFs associated with the WDC, a respective session between a corresponding PF service of the WD and a corresponding PF service of the WDC.

48. A method for wireless docking, the method comprising:

determining, by a wireless docking center (WDC), one or more peripheral functions (PFs) associated with the WDC;

establishing a docking session via a direct wireless connection between the WDC and a wireless dockee (WD);

selecting at least one PF of the one or more PFs associated with the WDC, wherein selecting includes receiving, by the WDC and from the WD, a message that indicates whether the WD is selecting PFs by individually identifying the at least one PF in the message or by selecting a default set of PFs that includes the at least one PF without individually identifying the at least one PF in the message; and

providing, by the WDC and to the WD, access to the at least one PF of the one or more PFs associated with the WDC, wherein providing access to the at least one PF comprises establishing, for a respective PF of the at least one PF of the one or more PFs associated with the WDC, a respective session between a corresponding PF service of the WDC and a corresponding PF service of the WD.

49. The method of claim 48,

wherein the determining the one or more PFs associated with the WDC comprises determining, by a docking service of the WDC, the one or more PFs associated with the WDC;

wherein establishing the docking session via the direct wireless connection between the WDC and the WD comprises establishing, by the docking service of the WDC, the docking session via the direct wireless connection between the WDC and the WD;

wherein selecting the at least one PF of the one or more PFs associated with the WDC comprises selecting, by the docking service of the WDC, the at least one PF of the one or more PFs associated with the WDC; and

wherein providing, by the WDC, access to the at least one PF of the one or more PFs associated with the WDC comprises providing, by the docking service of the WDC, access to the at least one PF of the one or more PFs associated with the WDC.

50. The method of claim 48, wherein determining, by the WDC, the one or more PFs associated with the WDC comprises:

performing, by the WDC, docking pre-association discovery with the WD to provide information regarding the one or more PFs associated with the WDC.

51. The method of claim 50, wherein determining, by the WDC, the one or more PFs associated with the WDC comprises:

sending, by the WDC and to the WD, an indication of the one or more PFs associated with the WDC.

52. The method of claim 51, wherein sending the indication of the one or more PFs associated with the WDC comprises sending a message to the WD that indicates one or more characteristics of the WDC.

53. The method of claim 52, wherein the one or more characteristics indicated by the message include:

a device type;

a device name;

a device availability;

the indication of the one or more PFs associated with the WDC; and

one or more docking environment types.

54. The method of claim 52, wherein the message comprises a UTF-8 text string of XML data that includes a preassociationServiceDiscovery element.

55. The method of claim 51, further comprising

receiving, by the WDC and from the WD, a request for information regarding the one or more PFs associated with the WDC.

56. The method of claim 55, wherein receiving, by the WDC and from the WD, the request for the information regarding the one or more PFs associated with the WDC comprises:

executing, by the WD, an AdvertiseService method based on one or more of the following parameters;

a service name value, an auto-accept value, a service information value, and a service status value, wherein the service information value includes the indication of the one or more PFs associated with the WDC.

57. The method of claim 56, wherein the service name value comprises org.wi-fi.wfds.docking.wdc.

58. The method of claim 51, further comprising:

responsive to determining that the indication of the one or more PFs associated with the WDC indicates one or more PFs sought by the WD, establishing the docking session.

59. The method of claim 48, wherein establishing the docking session comprises:

performing, by the WDC, docking connection setup exchange between the WDC and the WD; and

performing, by the WDC, docking ASP (application service platform) session setup between the WDC and the WD.

60. The method of claim 48, wherein establishing the docking session comprises:

forming a peer-to-peer (P2P) group that includes both the WDC and WD.

61. The method of claim 48, wherein establishing the docking session comprises:

executing, by the WDC, a ConfirmSession method based on one or more of the following parameters;

a session MAC value, a session ID value, and a confirmed value.

62. The method of claim 48, wherein selecting the at least one PF of the one or more PFs associated with the WDC comprises:

exchanging, by the WDC and with the WD, docking configuration and control protocol communications.

63. The method of claim 48, further comprising:

receiving, by the WDC and from the WD and during operation of the docking session, a query for information regarding the one or more PFs associated with the WDC.

64. The method of claim 48, wherein the message that indicates whether the WD is selecting PFs by individually identifying the at least one PF in the message or by selecting a default set of PFs that includes the at least one PF further includes a request to access one or more sought PFs of the one or more PFs associated with the WDC, and wherein selecting the at least one PF of the one or more PFs associated with the WDC further comprises:

determining, by the WDC, whether or not the accept the request for the WD to access the one or more sought PFs;

sending, by the WDC and to the WD, a message indicating whether or not the WDC accepts the request for the WD to access the one or more sought PFs; and

responsive to determining, by the WDC, to accept the request, providing, by the WDC and to the WD, access to the one or more sought PFs, wherein the one or more sought PFs includes the at least one PF.

65. The method of claim 64, wherein the request individually identifies the one or more sought PFs.

66. The method of claim 64, wherein a default set of PFs of the one or more PFs associated with the WDC includes the one or more sought PFs, and wherein the request does not individually identify the one or more sought PFs.

67. The method of claim 48, wherein establishing, for the respective PF of the at least one PF of the one or more PFs associated with the WDC, the respective session between the corresponding PF service of the WDC and the corresponding PF service of the WD comprises:

receiving, by the WDC and from the WD, a message that includes an advertisement identification value that corresponds to the respective PF.

68. The method of claim 67, wherein the advertisement identification value is sent by the WDC to the WD prior to the establishment of the docking session.

69. The method of claim 48, further comprising one or more of:

sending, by the corresponding PF service of the WDC to the corresponding PF service of the WD and via the respective session, input data; and

receiving, by the corresponding PF service of the WDC from the corresponding PF service of the WD and via the respective session, output data.

70. The method of claim 48, further comprising:

sending, by the WDC and to the WD and at a first time, a message that includes information regarding the one or more PFs associated with the WDC; and

sending, by the WDC and to the WD and at a second, later, time, a second message indicating that the information regarding the one or more PFs associated with the WDC has changed.

71. The method of claim 48, further comprising:

deselecting the at least one PF of the one or more PFs associated with the WDC, wherein deselecting comprises;

receiving, by the WDC and from the WD, a notification that the WD is deselecting the at least one PF of the one or more PFs associated with the WDC; and

closing a corresponding session between a corresponding PF service of the WDC and a corresponding PF service of the WD.

72. A wireless docking center (WDC) comprising:

a memory;

one or more processors;

at least one module executable by the one or more processors to;

determine one or more peripheral functions (PFs) associated with the WDC;

establish a docking session via a direct wireless connection between the WDC and a wireless dockee (WD);

select at least one PF of the one or more PFs associated with the WDC, wherein, to select the at least one PF, the at least one module is executable by the one or more processors to receive, from the WD, a message that indicates whether the WD is selecting PFs by individually identifying the at least one PF in the message or by selecting a default set of PFs that includes the at least one PF without individually identifying the at least one PF in the message; and

provide, to the WD, access to the at least one PF of the one or more PFs associated with the WDC, wherein, to provide access to the at least one PF, the at least one module is executable by the one or more processors to establish, for a respective PF of the at least one PF of the one or more PFs associated with the WDC, a respective session between a corresponding PF service of the WDC and a corresponding PF service of the WD.

73. The WDC of claim 72, wherein the at least one module includes a docking service executable by the one or more processors to:

determine the one or more PFs associated with the WDC;

establish the docking session via the direct wireless connection between the WDC and the WD;

select the at least one PF of the one or more PFs associated with the WDC; and

provide, to the WD, the access to the at least one PF of the one or more PFs associated with the WDC.

74. The WDC of claim 72, wherein the at least one module is executable by the one or more processors to determine the one or more PFs associated with the WDC by at least:

performing docking pre-association discovery with the WD to provide information regarding the one or more PFs associated with the WDC.

75. The WDC of claim 74, wherein the at least one module is executable by the one or more processors to determine the one or more PFs associated with the WDC by at least:

sending, to the WD, an indication of the one or more PFs associated with the WDC.

76. The WDC of claim 75, wherein the at least one module is executable by the one or more processors to send the indication of the one or more PFs associated with the WDC by at least sending a message to the WD that indicates one or more characteristics of the WDC.

77. The WDC of claim 75, wherein the at least one module is further executable by the one or more processors to:

receive, from the WD, a request for information regarding the one or more PFs associated with the WDC.

78. The WDC of claim 77, wherein the at least one module is executable by the one or more processors to receive, from the WD, the request for the information regarding the one or more PFs associated with the WDC by at least:

executing an AdvertiseService method based on one or more of the following parameters;

a service name value, an auto-accept value, a service information value, and a service status value, wherein the service information value includes the indication of the one or more PFs associated with the WDC.

79. The WDC of claim 75, wherein responsive to determining that the indication of the one or more PFs associated with the WDC indicates one or more PFs sought by the WD, the at least one module is further executable by the one or more processors to establishing the docking session.

80. The WDC of claim 72, wherein the at least one module is executable by the one or more processors to establish the docking session by at least:

performing docking connection setup exchange between the WDC and the WD; and

performing docking ASP (application service platform) session setup between the WDC and the WD.

81. The WDC of claim 72, wherein the at least one module is executable by the one or more processors to establish the docking session by at least:

forming a peer-to-peer (P2P) group that includes both the WDC and WD.

82. The WDC of claim 72, wherein the at least one module is executable by the one or more processors to establish the docking session by at least:

executing a ConfirmSession method based on one or more of the following parameters;

a session MAC value, a session ID value, and a confirmed value.

83. The WDC of claim 72, wherein the at least one module is executable by the one or more processors to select the at least one PF of the one or more PFs associated with the WDC by at least:

exchanging, with the WD, docking configuration and control protocol communications.

84. The WDC of claim 72, wherein the at least one module is further executable by the one or more processors to:

receive, from the WD and during operation of the docking session, a query for information regarding the one or more PFs associated with the WDC.

85. The WDC of claim 72, wherein the message that indicates whether the WD is selecting PFs by individually identifying the at least one PF in the message or by selecting a default set of PFs that includes the at least one PF further includes a request to access one or more sought PFs of the one or more PFs associated with the WDC, and wherein the at least one module is further executable by the one or more processors to select the at least one PF of the one or more PFs associated with the WDC by at least:

determining whether or not the accept the request for the WD to access the one or more sought PFs;

sending, to the WD, a message indicating whether or not the WDC accepts the request for the WD to access the one or more sought PFs; and

responsive to determining to accept the request, providing, to the WD, the access to the one or more sought PFs, wherein the one or more sought PFs includes the at least one PF.

86. The WDC of claim 85, wherein the request individually identifies the one or more sought PFs.

87. The WDC of claim 85, wherein a default set of PFs of the one or more PFs associated with the WDC includes the one or more sought PFs, and wherein the request does not individually identify the one or more sought PFs.

88. The WDC of claim 72, wherein the at least one module is further executable by the one or more processors to one or more of:

send, by the corresponding PF service of the WDC to the corresponding PF service of the WD and via the respective session, input data; and

receive, by the corresponding PF service of the WDC from the corresponding PF service of the WD and via the respective session, output data.

89. The WDC of claim 72, wherein the at least one module is further executable by the one or more processors to:

send, to the WD and at a first time, a message that includes information regarding the one or more PFs associated with the WDC; and

send, to the WD and at a second, later, time, a second message indicating that the information regarding the one or more PFs associated with the WDC has changed.

90. The WDC of claim 72, wherein the at least one module is further executable by the one or more processors to:

deselect the at least one PF of the one or more PFs associated with the WDC, wherein the at least one module is executable by the one or more processors to deselect the at least one PF by at least;

receiving, from the WD, a notification that the WD is deselecting the at least one PF of the one or more PFs associated with the WDC; and

closing a corresponding session between a corresponding PF service of the WDC and a corresponding PF service of the WD.

91. A wireless docking center (WDC) comprising:

means for determining one or more peripheral functions (PFs) associated with the WDC;

means for establishing a docking session via a direct wireless connection between the WDC and a wireless dockee (WD);

means for selecting at least one PF of the one or more PFs associated with the WDC, wherein the means for selecting the at least one PF include means for receiving, from the WD, a message that indicates whether the WD is selecting PFs by individually identifying the at least one PF in the message or by selecting a default set of PFs that includes the at least one PF without individually identifying the at least one PF in the message; and

means for providing, to the WD, access to the at least one PF of the one or more PFs associated with the WDC, wherein the means for providing access to the at least one PF comprise means for establishing, for a respective PF of the at least one PF of the one or more PFs associated with the WDC, a respective session between a corresponding PF service of the WDC and a corresponding PF service of the WD.

92. A non-transitory computer-readable storage medium stores instructions that, when executed, cause one or more processors of a wireless docking center (WDC) to:

determine one or more peripheral functions (PFs) associated with the WDC;

establish a docking session via a direct wireless connection between the WDC and a wireless dockee (WD);

select at least one PF of the one or more PFs associated with the WDC, wherein the instructions that cause the one or more processors to select the at least one PF include instructions that cause the one or more processors to receive, from the WD, a message that indicates whether the WD is selecting PFs by individually identifying the at least one PF in the message or by selecting a default set of PFs that includes the at least one PF without individually identifying the at least one PF in the message; and

provide, to the WD, access to the at least one PF of the one or more PFs associated with the WDC, wherein the instructions that cause the one or more processors to provide access to the at least one PF comprise instructions that cause the one or more processors to establish, for a respective PF of the at least one PF of the one or more PFs associated with the WDC, a respective session between a corresponding PF service of the WDC and a corresponding PF service of the WD.