Personal area network with automatic attachment and detachment

• US 7,756,129 B2
• Filed: 03/23/2007
• Issued: 07/13/2010
• Est. Priority Date: 03/27/2000
• Status: Expired due to Fees

• Current Assignee: RPX Corporation
• Original Assignee: Azure Networks, LLC (Oso IP, LLC)
• Inventors: Donaghey, Robert J.
• Primary Examiner(s): PHAN, MAN U
• Application Number:
  US11/728,246
• Publication Number:
  US 20070274309A1
• Time in Patent Office: 1,208 Days
• Field of Search: 370230-252, 370310-389, 370400-452, 709202-217, 709220-229
• US Class Current: 370/389
• CPC Class Codes: G06F 13/10 Program control for peripheral devices G06F13/14 - G06F13/42 take precedence
• CPC Class Codes: G06F 13/38 Information transfer, e.g. on bus G06F13/14 takes precedence
• CPC Class Codes: H04B 7/2612 Arrangements for wireless medium access control, e.g. by allocating physical layer transmission capacity H04B7/2615 - H04B7/2643 take precedence; provision for broadband connection H04Q11/0478
• CPC Class Codes: H04L 12/66 Arrangements for connecting between networks having differing types of switching systems, e.g. gateways
• CPC Class Codes: H04L 51/00 User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
• CPC Class Codes: H04L 51/08 Annexed information, e.g. attachments
• CPC Class Codes: H04L 61/5038 for local use, e.g. in LAN or USB networks, or in a controller area network [CAN]
• CPC Class Codes: H04L 61/5069 for group communication, multicast communication or broadcast communication
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04W 4/80 Services using short range communication, e.g. near-field communication [NFC], radio-frequency identification [RFID] or low energy communication
• CPC Class Codes: H04W 48/16 Discovering, processing access restriction or access information
• CPC Class Codes: H04W 60/00 Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
• CPC Class Codes: H04W 76/00 Connection management
• CPC Class Codes: H04W 76/10 Connection setup
• CPC Class Codes: H04W 8/245 from a network towards a terminal
• CPC Class Codes: H04W 84/12 WLAN [Wireless Local Area Networks]
• CPC Class Codes: Y02D 10/00 Energy efficient computing, e.g. low power processors, power management or thermal management

Abstract

A network (100) includes a hub device (110) and at least one unattached peripheral device (120). The unattached peripheral device (120) transmits an attach request to the hub device (110) with a selected address, receives a new address from the hub device to identify the unattached peripheral device (120), and communicates with the hub device (110) using the new address.

Claims

1. A method of communicating between a first peripheral device and a hub device in a personal area network, comprising:

sending by the hub device, a signal to indicate availability of the hub device for peripheral attachment,

in response to the signal sent by the hub device, sending by the first peripheral device, a signal to indicate availability of the first peripheral device for communication with the hub device,

sending, by the hub device to the first peripheral device, a signal including a first peripheral device identifier,

subsequent to sending the signal including a first peripheral device identifier from the hub device, sending by the first peripheral device to the hub device a first peripheral response,

subsequent to the receiving of the first peripheral response by the hub device, sending by the hub device to the first peripheral device a hub response, and

subsequent to the receiving of the hub response by the first peripheral device, sending by the first peripheral device to the hub device a second peripheral response including the first peripheral device identifier.

2. The method according to claim 1, wherein the first peripheral device identifier is based at least in part on a MAC address of the first peripheral device.

3. The method according to claim 2, wherein the MAC address for the first peripheral device includes an AMAC address for the first peripheral device.

4. The method according to claim 2, wherein the MAC address for the first peripheral device is different from an AMAC address for the first peripheral device.

5. The method according to claim 1, wherein the hub device controls the allocation of communications channels among a plurality of peripheral devices with which the hub device is communicating.

6. The method according to claim 1 comprising communicating, by the hub device, with at least one additional peripheral device having a peripheral device identifier different from the first peripheral device identifier.

7. The method according to claim 1 comprising broadcasting a message from the hub device to a plurality of peripheral devices with which the hub device is attached, the message including a broadcast identifier.

8. The method according to claim 1, wherein the signal broadcast from the hub device includes a range of peripheral device identifiers, one of which being the first peripheral device identifier.

9. The method according to claim 8 comprising receiving at the hub device, identifiers within the range of the identifier of the peripheral device for a plurality of other peripheral devices indicating their availability for communication with the hub device in response to the signal sent by the hub device.

10. The method according to claim 1 comprising assigning, by the hub device to the first peripheral device, one or more additional identifiers to the first peripheral device, wherein the one or more additional identifiers is used to further identify communications between the hub device and the first peripheral device.

11. The method according to claim 10, wherein the one or more additional identifiers include a stream number for identifying a particular communication channel between the peripheral device and the hub device.

12. The method of claim 10, wherein the one or more additional identifiers include a token that includes a stream number for identifying a particular communication channel between the first peripheral device and the hub device, and the first peripheral device identifier.

13. The method of claim 1, wherein the identifier is associated with a network address.

218. The method according to claim 1, wherein the communication between the first peripheral device and the hub device is such that a plurality of MAC addresses is capable of being used for identification purposes in connection with the first peripheral device.

14. A hub device for use within a personal area network, comprising:

circuitry, and

a transceiver in communication with the circuitry, the hub device configured to cause the transceiver to

i) send a message to indicate the availability of the hub device for peripheral device attachment,

ii) receive, from a first peripheral device, a message indicating the availability of the first peripheral device for communication with the hub device,

iii) send, to the first peripheral device, a signal including a first peripheral device identifier,

iv) receive, from the first peripheral device, a response,

v) send a hub response to the first peripheral device, and

vi) receive, from the first peripheral device, a second peripheral response including the first peripheral device identifier.

15. The device according to claim 14, wherein the first peripheral device identifier is based at least in part on a MAC address for the first peripheral device.

16. The device according to claim 15, wherein the MAC address for the first peripheral device includes an AMAC address for the first peripheral device.

17. The device according to claim 15, wherein the MAC address for the first peripheral device is different from an AMAC address for the first peripheral device.

18. The device according to claim 14, wherein the circuitry is configured to control the allocation of communication channels among a plurality of peripheral devices with which the hub device is communicating.

19. The device according to claim 14, wherein the hub device is configured to cause the transceiver to communicate with at least one additional peripheral device having a peripheral device identifier different from the first peripheral device identifier.

20. The device according to claim 14, wherein the transceiver is configured to broadcast a signal from hub device to a plurality of peripheral devices with which the hub device is attached, the signal including a broadcast identifier.

21. The device according to claim 14, wherein the signal sent from the hub device includes a range of peripheral device identifiers, one of which being the first peripheral device identifier.

22. The device according to claim 21, wherein the transceiver is configured to receive identifiers within the range of the peripheral device identifiers for a plurality of other peripheral devices indicating their availability for communication with the hub device in response to the signal sent by the hub device.

23. The device according to claim 14, wherein the transceiver is configured to send one or more additional identifiers to the first peripheral device, wherein the one or more identifiers are used to further identify communications between the hub device and the first peripheral device.

24. The device according to claim 23, wherein the one or more additional identifiers include a stream number for identifying a particular communication channel between the first peripheral device and the hub device.

25. The device according to claim 23, wherein the one or more additional identifiers include a token that includes a stream number for identifying a particular communication channel between the first peripheral device and the hub device, and the first peripheral device identifier.

26. The device according to claim 14, wherein the identifier is associated with a network address.

38. The hub device according to claim 14, wherein the hub device is operable such that different channels are utilized for different functions.

39. The hub device according to claim 14, wherein the hub device includes a transceiver and digital control logic integrated on a single integrated circuit.

40. The hub device according to claim 14, wherein the hub device includes a host on a single integrated circuit.

41. The hub device according to claim 14, wherein the hub device includes a transceiver integrated on a single integrated circuit.

42. The hub device according to claim 14, wherein the hub device includes digital control logic integrated on a single integrated circuit.

43. The hub device according to claim 14, wherein the hub device is configured such that a plurality of MAC addresses is capable of being used for identification in association with the first peripheral device.

44. The hub device according to claim 43, wherein the hub response to the first peripheral device includes the first peripheral device identifier.

45. The hub device according to claim 43, wherein the first peripheral device includes a plurality of virtual entities.

46. The hub device according to claim 45, wherein each of the plurality of virtual entities is capable of being identified utilizing an associated one of the plurality of MAC addresses.

47. The hub device according to claim 43, wherein the plurality of MAC addresses exist simultaneously.

48. The hub device according to claim 43, wherein the hub device is operable such that the plurality of MAC addresses is used by a link layer embodied on a computer readable medium.

49. The hub device according to claim 48, wherein the link layer resides between a physical layer and a network layer embodied on the computer readable medium.

50. The hub device according to claim 48, wherein the link layer is responsible for assignment of the plurality of MAC addresses.

51. The hub device according to claim 43, wherein the plurality of MAC addresses includes at least three MAC addresses.

52. The hub device according to claim 43, wherein the hub device is configured to cause the transceiver to follow a protocol that involves a plurality of data blocks and a plurality of status blocks that include a channel identifier in connection with each of the data blocks and the status blocks, wherein the data blocks are capable of being used for retransmission of data.

53. The hub device according to claim 43, wherein the hub device is configured to cause the transceiver to follow a protocol that involves a plurality of data blocks and a plurality of status blocks that each include a channel identifier.

54. The hub device according to claim 53, wherein the channel identifier includes a stream number.

55. The hub device according to claim 53, wherein the status blocks are utilized for controlling retransmission.

56. The hub device according to claim 53, wherein a first channel identifier associated with at least one of the status blocks is different than a second channel identifier associated with at least one of the data blocks.

57. The hub device according to claim 53, wherein at least one of the data blocks includes data to be retransmitted and at least one of the status blocks is adapted for controlling transmission of the at least one data block.

58. The hub device according to claim 43, wherein the message to indicate the availability of the hub device for peripheral device attachment is sent via a broadcast.

59. The hub device according to claim 43, wherein the peripheral device attachment and peripheral device detachment is automatic.

60. The hub device according to claim 43, wherein the hub device is configured such that the plurality of MAC addresses is used to identify the first peripheral device.

61. The hub device according to claim 43, wherein the plurality of MAC addresses is associated with the first peripheral device.

62. The hub device according to claim 43, wherein the hub device is operable such that the plurality of MAC addresses is capable of being used to identify peripheral entities associated with the first peripheral device, the peripheral device attachment is automatic, and at least three MAC addresses are capable of existing simultaneously in association with the first peripheral device, which includes a single physical device.

63. The hub device according to claim 43, wherein the plurality of MAC addresses is each associated with a separate class of MAC addresses.

64. The hub device according to claim 43, wherein the hub device is configured to control allocation of communication channels among a plurality of peripheral devices with which the hub device is communicating.

65. The hub device according to claim 43, wherein the hub device is configured to cause the transceiver to communicate with at least one additional peripheral device having a peripheral device identifier different from the first peripheral device identifier.

66. The hub device according to claim 43, wherein the hub device is configured to cause the transceiver to send one or more additional identifiers to the first peripheral device, wherein the one or more identifiers is used to further identify communications between the hub device and the first peripheral device.

67. The hub device according to claim 66, wherein the one or more additional identifiers includes a stream number for identifying a particular communication channel between the first peripheral device and the hub device.

68. The hub device according to claim 66, wherein the one or more additional identifiers is associated with a token that includes a stream number for identifying a particular communication channel between the first peripheral device and the hub device.

69. The hub device according to claim 43, wherein the message to indicate the availability of the hub device for peripheral device attachment includes a heartbeat signal.

70. The hub device according to claim 43, wherein the message to indicate the availability of the hub device for peripheral device attachment is an initial message.

71. The hub device according to claim 43, wherein the hub device is operable such that an attachment process is initialized with the message to indicate the availability of the hub device for peripheral device attachment.

72. The hub device according to claim 43, wherein the hub device is operable such that the message to indicate the availability of the hub device for peripheral device attachment is sent repeatedly.

73. The hub device according to claim 43, wherein the hub device is configured to cause the transceiver to follow a protocol that involves a plurality of data blocks and a plurality of status blocks that each include a channel identifier, in association with transmission of data multiple times.

74. The hub device according to claim 73, wherein the hub device is operable such that an attachment process is initialized with the message to indicate the availability of the hub device for peripheral device attachment.

75. The hub device according to claim 43, wherein the message indicating the availability of the first peripheral device includes an attachment peripheral device identifier.

76. The hub device according to claim 75, wherein the attachment peripheral device identifier is initially provided by the first peripheral device after the message to indicate the availability of the hub device for peripheral device attachment is sent.

77. The hub device according to claim 75, wherein the attachment peripheral device identifier is received from the first peripheral device in response to the message to indicate the availability of the hub device for peripheral device attachment.

78. The hub device according to claim 43, wherein the message indicating the availability of the first peripheral device includes a temporary peripheral device identifier, for use during an attachment process.

79. The hub device according to claim 43, wherein the hub device is operable such that:

one of the MAC addresses is used for identification in association with a first entity of the first peripheral device and another one of the MAC addresses is used for identification in association with a second entity of the first peripheral device;

the first entity includes a first controller and the second entity includes a second controller;

at least three of the MAC addresses are capable of existing simultaneously in association with the first peripheral device which includes a single physical device;

the transceiver is caused to follow a protocol that involves a plurality of data blocks and a plurality of status blocks that each include a channel identifier, in association with transmission of data multiple times;

a first one of the MAC addresses is capable of being utilized for attachment purposes and a second one of the MAC addresses is capable of being utilized for data transfer;

the first one of the MAC addresses is capable of being initially used for the attachment purposes in association with the first peripheral device without use of the second one of the MAC addresses, after which the second one of the MAC addresses is capable of being utilized; and

the first one of the MAC addresses has a first one or more channels associated therewith with a capability of transferring a first amount of data and the second one of the MAC addresses has a second one or more channels associated therewith with a capability of transferring a second amount of data different than the first amount of data.

80. The hub device according to claim 79, wherein the hub device is operable such that the plurality of MAC addresses is used by a link layer embodied on a computer readable medium that resides between a physical layer and a network layer embodied on the computer readable medium, the link layer being responsible for assignment of the plurality of MAC addresses.

81. The hub device according to claim 79, wherein the hub device is operable such that an attachment process is initialized with the message to indicate the availability of the hub device for peripheral device attachment;

the message to indicate the availability of the hub device for peripheral device attachment is sent repeatedly;

i)-vi) are communications associated with the attachment process;

the transceiver is caused to communicate between the hub device and the first peripheral device, utilizing one or more additional identifiers; and

a memory is included with a control structure embodied thereon that performs network bandwidth control.

82. The hub device according to claim 43, wherein the first peripheral device identifier includes a newly-selected address.

83. The hub device according to claim 43, wherein the message indicating the availability of the first peripheral device includes an attachment peripheral device identifier that is selected by the first peripheral device.

84. The hub device according to claim 43, wherein the hub device is configured for reattachment.

85. The hub device according to claim 84, wherein the reattachment involves an attach request using a previously-assigned address.

86. The hub device according to claim 84, wherein the reattachment involves an attach request using a newly-selected address.

87. The hub device according to claim 43, wherein at least i)-iv) are communications associated with an attachment process.

88. The hub device according to claim 43, wherein i)-vi) are communications associated with an attachment process.

89. The hub device according to claim 43, wherein iv) includes a confirmation message.

90. The hub device according to claim 43, wherein v) includes a confirmation message.

91. The hub device according to claim 43, wherein vi) includes an acknowledgement message.

92. The hub device according to claim 43, wherein i)-vi) are the only communications associated with an attachment process.

93. The hub device according to claim 43, wherein no other communications occur between i)-ii), no other communications occur between ii)-iii), no other communications occur between iii)-iv), no other communications occur between iv)-v), and no other communications occur between v)-vi).

94. The hub device according to claim 43, wherein the hub device is configured to send keep-alive messages.

95. The hub device according to claim 43, wherein the hub device is configured to cause the transceiver to communicate between the hub device and the first peripheral device, utilizing one or more additional identifiers.

96. The hub device according to claim 95, wherein the one or more additional identifiers includes a stream identifier.

97. The hub device according to claim 95, wherein the one or more additional identifiers indicates a direction of a data transfer.

98. The hub device according to claim 95, wherein the one or more additional identifiers indicates a size of a data transfer.

99. The hub device according to claim 95, wherein the hub device is operable such that the one or more additional identifiers is sent from the hub device to the first peripheral device.

100. The hub device according to claim 95, wherein the hub device is operable such that the one or more additional identifiers is used to further identify communications between the hub device and the first peripheral device.

101. The hub device according to claim 95, wherein the one or more additional identifiers includes a stream number for identifying a communication channel between the first peripheral device and the hub device.

102. The hub device according to claim 101, wherein the communication channel is uni-directional.

103. The hub device according to claim 95, wherein the one or more additional identifiers are included in a token.

104. The hub device according to claim 103, wherein the token includes a stream number.

105. The hub device according to claim 104, wherein the stream number is for identifying a particular communication channel between the first peripheral device and the hub device.

106. The hub device according to claim 104, wherein the stream number is for identifying a particular communication channel between the first peripheral device and the hub device, and the token further includes an address for the first peripheral device.

107. The hub device according to claim 43, wherein the hub device is configured to cause the transceiver to communicate via a communications protocol shared by the hub device and the first peripheral device to synchronize timing of the communication.

108. The hub device according to claim 107, wherein the communications protocol includes a plurality of frames.

109. The hub device according to claim 108, wherein each of the frames includes a signal that marks a start of the frame.

110. The hub device according to claim 108, wherein each of the frames is associated with at least one data transfer opportunity that permits the hub device to communicate a data block with the first peripheral device.

111. The hub device according to claim 43, wherein the hub device includes a memory including a control structure embodied thereon that performs network bandwidth control.

112. The hub device according to claim 43, wherein the hub device includes a memory including a control structure embodied thereon that performs token planning.

113. The hub device according to claim 43, wherein the hub device includes a memory including a network interface structure embodied thereon that determines whether or when to schedule a data transfer, and a link layer transport structure embodied thereon that provides a reliable data transfer for a network interface.

114. The hub device according to claim 43, wherein the hub device includes a memory including a link layer transport structure embodied thereon that provides a reliable data transfer for a network interface.

115. The hub device according to claim 43, wherein the hub device includes a memory including a link layer control structure embodied thereon that performs token planning or bandwidth control.

116. The hub device according to claim 43, wherein the hub device includes a memory including a structure embodied thereon that provides a reliable data transfer for a network interface.

117. The hub device according to claim 43, wherein at least one of the hub device and the first peripheral device is further configured to transfer the same data in multiple forms.

118. The hub device according to claim 117, wherein a stream on which the data is communicated indicates a form of transfer.

119. The hub device according to claim 117, wherein at least one of the hub device and the first peripheral device is further configured to combine the multiple forms of the same data to reconstruct the data.

120. The hub device according to claim 117, wherein the multiple forms include an original form and at least one of a complemented form and a reverse order form.

121. The hub device according to claim 117, wherein the multiple forms include at least one of a complemented form and a reverse order form.

122. The hub device according to claim 43, wherein the hub device is further configured to schedule transmission of a status block from the first peripheral device.

123. The hub device according to claim 122, wherein the hub device is further configured to schedule transmission of data from the first peripheral device when the status block from the first peripheral device indicates that the first peripheral device has data ready for transmission to the hub device.

124. The hub device according to claim 43, wherein the hub device is operable such that the plurality of MAC addresses is capable of being used to identify virtual peripheral entities associated with the first peripheral device, the peripheral device attachment is automatic, at least three MAC addresses are capable of existing simultaneously, a first one of the MAC addresses is utilized for attachment purposes, and a second one of the MAC addresses is utilized for data transfer.

125. The hub device according to claim 43, wherein the hub device is operable such that a first one of the MAC addresses is utilized for attachment purposes.

126. The hub device according to claim 125, wherein the hub device is operable such that a second one of the MAC addresses is utilized for data transfer.

127. The hub device according to claim 125, wherein the hub device is operable such that the first one of the MAC addresses is also used for data transfer.

128. The hub device according to claim 125, wherein the hub device is operable such that a second one of the MAC addresses is utilized for non-attachment purposes.

129. The hub device according to claim 43, wherein the hub device is operable such that a first one of the MAC addresses has a first plurality of channels associated therewith and a second one of the MAC addresses has a second plurality of channels associated therewith.

130. The hub device according to claim 129, wherein the first plurality of channels include channels supported by the first MAC address.

131. The hub device according to claim 129, wherein the first plurality of channels include active channels supported by the first MAC address.

132. The hub device according to claim 129, wherein the hub device is operable such that different channels are utilized for different functions.

133. The hub device according to claim 43, wherein the hub device includes a transceiver and digital control logic integrated on a single integrated circuit.

134. The hub device according to claim 43, wherein the hub device includes a host, a transceiver, and digital control logic integrated on a single integrated circuit.

135. The hub device according to claim 43, and further comprising:

a software architecture embodied in memory including a link layer driver layer, a link layer transport layer, a network interface layer, and a link layer control layer.

136. The hub device according to claim 43, and further comprising:

a software architecture embodied in memory including i) a link layer driver layer, ii) a link layer transport layer, and iii) a network interface layer, where i) resides below ii), and ii) resides below iii).

137. The hub device according to claim 43, wherein the hub device is operable such that a first one of the MAC addresses has a first plurality of channels associated therewith with a capability of transferring a first amount of data and a second one of the MAC addresses has a second plurality of channels associated therewith with a capability of transferring a second amount of data less than the first amount of data.

138. The hub device according to claim 137, wherein the first amount of data is provided utilizing a first data block size, and the second amount of data is provided utilizing a second data block size.

139. The hub device according to claim 43, wherein the hub device is operable such that a first one of the MAC addresses has a plurality of channels associated therewith with a capability of transferring an amount of data that has an associated maximum size.

140. The hub device according to claim 43, wherein the hub device is operable such that a plurality of streams are partitioned between the MAC addresses.

141. The hub device according to claim 43, wherein the circuitry includes a processor.

142. The hub device according to claim 43, wherein the circuitry includes a microcontroller.

143. The hub device according to claim 43, wherein the first peripheral identifier is one of the MAC addresses.

144. The hub device according to claim 43, wherein the hub device is operable such that i) occurs before ii), ii) occurs before iii), iv) occurs before v), and vi) occurs before v).

145. The hub device according to claim 43, wherein the hub device is operable such that only a first one of the MAC addresses is initially used for identification in association with the first peripheral device, after which a second one of the MAC addresses is utilized.

146. The hub device according to claim 43, wherein the hub device is operable such that only a first one of the MAC addresses is initially used for identification in association with the first peripheral device, after which a second one of the MAC addresses is utilized simultaneously with the first MAC address.

147. The hub device according to claim 43, wherein the hub device is operable such that a first one of the MAC addresses is used for identification in association with a first entity of the first peripheral device, and a second one of the MAC addresses is used for identification in association with a second entity of the first peripheral device.

148. The hub device according to claim 147, wherein the first entity includes a first controller, and the second entity includes a second controller.

149. The hub device according to claim 43, wherein the hub device is operable such that a first one of the MAC addresses has a first plurality of channels associated therewith with a first capability and a second one of the MAC addresses has a second plurality of channels associated therewith with a second capability different from the first capability.

150. The hub device according to claim 43, wherein the hub device is operable such that a first one of the MAC addresses has a first plurality of channels associated therewith with a first communication purpose and a second one of the MAC addresses has a second plurality of channels associated therewith with a second communication purpose different from the first communication purpose.

151. The hub device according to claim 43, wherein the hub device is operable such that data is sent via a first channel, and the same data is also sent via a second channel.

152. The hub device according to claim 151, wherein the hub device is operable such that the data is sent via the first channel using a first format, and the data is sent via the second channel using a second format.

153. The hub device according to claim 43, wherein the hub device is operable such that the plurality of MAC addresses is capable of being used to identify virtual peripheral entities associated with the first peripheral device, where the first peripheral device includes a single physical device.

154. The hub device according to claim 153, wherein the virtual peripheral entities include virtual devices.

155. The hub device according to claim 43, wherein the hub device is operable such that responses are received in connection with each of the plurality of MAC addresses.

156. The hub device according to claim 43, wherein the hub device is operable such that at least one active communication stream is associated with each of the plurality of MAC addresses.

157. The hub device according to claim 43, wherein the first peripheral device includes a plurality of virtual peripheral devices.

158. The hub device according to claim 43, wherein the peripheral device attachment is automatic.

159. The hub device according to claim 43, wherein the hub device includes a computer readable medium with computer code embodied thereon including a transport layer.

160. The hub device according to claim 14, wherein the sent message is a broadcasted message.

161. The hub device according to claim 160, wherein the response in iv) includes the first peripheral device identifier.

162. The hub device according to claim 161, wherein the broadcasted message includes a heartbeat signal.

163. The hub device according to claim 161, wherein the broadcasted message is an initial message.

164. The hub device according to claim 161, wherein the hub device is operable such that an attachment process is initialized with the broadcasted message.

165. The hub device according to claim 161, wherein the hub device is operable such that the broadcasted message is broadcasted periodically.

166. The hub device according to claim 161, wherein the broadcasted message includes a hub device identifier.

167. The hub device according to claim 166, wherein the hub device identifier includes a MAC address.

168. The hub device according to claim 166, wherein the hub device is operable such that an attachment process is initialized with the broadcasted message.

169. The hub device according to claim 161, wherein the message indicating the availability of the first peripheral device includes an attachment peripheral device identifier.

170. The hub device according to claim 169, wherein the hub device is operable such that the attachment peripheral device identifier is initially received from the first peripheral device after the broadcasted message is broadcasted.

171. The hub device according to claim 169, wherein the hub device is operable such that the attachment peripheral device identifier is received from the first peripheral device in response to the broadcasted message.

172. The hub device according to claim 161, wherein the message indicating the availability of the first peripheral device includes a temporary peripheral device identifier, for use during an attachment process.

173. The hub device according to claim 161, wherein the message indicating the availability of the first peripheral device includes an attachment peripheral device identifier that is, at least in part, randomly selected.

174. The hub device according to claim 161, wherein the message indicating the availability of the first peripheral device includes an attachment peripheral device identifier that is selected from a range of identifiers.

175. The hub device according to claim 161, wherein the message indicating the availability of the first peripheral device includes an attachment peripheral device identifier that is selected by the first peripheral device.

176. The hub device according to claim 161, wherein the first peripheral device identifier includes a newly-selected address.

177. The hub device according to claim 161, wherein the first peripheral device identifier includes a previously-assigned address.

178. The hub device according to claim 161, wherein the hub device is configured to cause the transceiver to perform a reattachment process.

179. The hub device according to claim 178, wherein the reattachment process involves an attach request using a previously-assigned address.

180. The hub device according to claim 178, wherein the reattachment process involves an attach request using a newly-selected address.

181. The hub device according to claim 161, wherein at least i)-iii) are communications associated with an attachment process.

182. The hub device according to claim 161, wherein at least i)-iv) are communications associated with an attachment process.

183. The hub device according to claim 161, wherein iv) includes a confirmation message.

184. The hub device according to claim 161, wherein v) includes a confirmation message.

185. The hub device according to claim 161, wherein vi) includes an acknowledgement message.

186. The hub device according to claim 161, wherein no other communications occur between i) and ii).

187. The hub device according to claim 161, wherein no other communications occur between ii) and iii).

188. The hub device according to claim 161, wherein the hub device is configured to send keep-alive messages.

189. The hub device according to claim 161, wherein the hub device is configured to cause the transceiver to communicate with the first peripheral device, utilizing one or more additional identifiers.

190. The hub device according to claim 189, wherein the one or more additional identifiers includes a stream identifier.

191. The hub device according to claim 189, wherein the one or more additional identifiers indicates a direction of a data transfer.

192. The hub device according to claim 189, wherein the one or more additional identifiers indicates a size of a data transfer.

193. The hub device according to claim 189, wherein the hub device is configured such that the one or more additional identifiers is sent from the hub device to the first peripheral device.

194. The hub device according to claim 189, wherein the hub device is configured such that the one or more additional identifiers is used to further identify communications between the hub device and the first peripheral device.

195. The hub device according to claim 189, wherein the one or more additional identifiers includes a stream number for identifying a communication channel between the first peripheral device and the hub device.

196. The hub device according to claim 195, wherein the communication channel is uni-directional.

197. The hub device according to claim 189, wherein the one or more additional identifiers is associated with a token.

198. The hub device according to claim 197, wherein the token includes a stream number.

199. The hub device according to claim 198, wherein the stream number is for identifying a particular communication channel between the first peripheral device and the hub device.

200. The hub device according to claim 198, wherein the stream number is for identifying a particular communication channel between the first peripheral device and the hub device, and the token further includes an address for the first peripheral device.

201. The hub device according to claim 161, wherein the hub device is configured to cause the transceiver to communicate via a communications protocol shared by the hub device and the first peripheral device to synchronize timing of the communication.

202. The hub device according to claim 201, wherein the communications protocol includes a plurality of frames.

203. The hub device according to claim 202, wherein each of the frames includes a signal that marks a start of the frame.

204. The hub device according to claim 202, wherein each of the frames includes at least one token transmission that identifies at least one data transfer opportunity that permits the hub device to communicate a data block with the first peripheral device.

205. The hub device according to claim 161, wherein the hub device includes a memory including a control structure embodied thereon that performs network bandwidth control.

206. The hub device according to claim 161, wherein the hub device includes a memory including a control structure embodied thereon that performs token planning.

207. The hub device according to claim 161, wherein the hub device includes a memory including a network interface structure embodied thereon that determines whether or when to schedule a data transfer, and a link layer transport structure embodied thereon that provides a reliable data transfer for a network interface.

208. The hub device according to claim 161, wherein the hub device includes a memory including a link layer transport structure embodied thereon that provides a reliable data transfer for a network interface.

209. The hub device according to claim 161, wherein the first peripheral device includes a memory including a link layer control structure embodied thereon that performs token planning.

210. The hub device according to claim 161, wherein the first peripheral device includes a memory including a link layer transport structure embodied thereon that provides a reliable data transfer for a network interface.

211. The hub device according to claim 161, wherein at least one of the hub device and the first peripheral device is further configured to transfer the same data in multiple forms.

212. The hub device according to claim 211, wherein a stream on which the data is communicated indicates a form of transfer.

213. The hub device according to claim 211, wherein at least one of the hub device and the first peripheral device is further configured to combine the multiple forms of the same data to reconstruct the data.

214. The hub device according to claim 211, wherein the multiple forms include an original form and at least one of a complemented form and a reverse order form.

215. The hub device according to claim 211, wherein the multiple forms include at least one of a complemented form and a reverse order form.

216. The hub device according to claim 161, wherein the hub device is further configured to schedule transmission of a status block from the first peripheral device.

217. The hub device according to claim 216, wherein the hub device is further configured to schedule transmission of data from the first peripheral device when the status block from the first peripheral device indicates that the first peripheral device has data ready for transmission to the hub device.

27. A peripheral device for use within a personal area network, comprising:

circuitry, and

a transceiver in communication with the circuitry, the peripheral device configured to cause the transceiver to

i) receive a sent message from a hub device to indicate the availability of the hub device for peripheral device attachment,

ii) send, to the hub device, a message indicating the availability of the peripheral device for communication with the hub device,

iii) receive, from the hub device, a signal including a peripheral device identifier,

iv) send a response to the hub device,

v) receive, from the hub device, a hub response, and

vi) send, to the hub device, a second peripheral response including the peripheral device identifier.

28. The device according to claim 27, wherein the peripheral device identifier is based at least in part on a MAC address for the peripheral device.

29. The device according to claim 28, wherein the MAC address for the peripheral device includes an AMAC address for the peripheral device.

30. The device according to claim 28, wherein the MAC address for the peripheral device is different from an AMAC address for the peripheral device.

31. The device according to claim 27, wherein the circuitry is configured to manage network timing with the hub device to enable the allocation of available bandwidth with other peripheral devices which the hub device is currently communicating.

32. The device according to claim 27, wherein the transceiver is configured to receive a signal broadcast from the hub device including a broadcast identifier.

33. The device according to claim 27, wherein the transceiver is configured to receive a broadcast signal from the hub device including a range of peripheral device identifiers, one of which being the peripheral device identifier.

34. The device according to claim 27, wherein the transceiver is configured to receive, from the hub device, one or more additional identifiers, wherein the one or more identifiers are used to further identify communications between the hub device and the peripheral device.

35. The device according to claim 34, wherein the one or more additional identifiers include a stream number for identifying a particular communication channel between the peripheral device and the hub device.

36. The device according to claim 34, wherein the one or more identifiers include a token that includes a stream number for identifying a particular communication channel between the peripheral device and the hub device, and the peripheral device identifier.

37. The device according to claim 27, wherein the identifier is associated with a network address.

219. The peripheral device according to claim 27, wherein the peripheral device is operable such that different channels are utilized for different functions.

220. The peripheral device according to claim 27, wherein the peripheral device includes a transceiver and digital control logic integrated on a single integrated circuit.

221. The peripheral device according to claim 27, wherein the peripheral device is configured such that a plurality of MAC addresses is capable of being used for identification in association therewith.

222. The peripheral device according to claim 221, wherein the hub response includes the peripheral device identifier.

223. The peripheral device according to claim 221, wherein the peripheral device includes a plurality of virtual entities.

224. The peripheral device according to claim 223, wherein the peripheral device is operable such that each of the plurality of virtual entities is capable of being identified utilizing an associated one of the plurality of MAC addresses.

225. The peripheral device according to claim 221, wherein the plurality of MAC addresses exist simultaneously.

226. The peripheral device according to claim 221, wherein the peripheral device is operable such that the plurality of MAC addresses is used by a link layer embodied on a computer readable medium.

227. The peripheral device according to claim 226, wherein the link layer resides between a physical layer and a network layer embodied on the computer readable medium.

228. The peripheral device according to claim 226, wherein the link layer is responsible for assignment of the plurality of MAC addresses.

229. The peripheral device according to claim 221, wherein the plurality of MAC addresses includes at least three MAC addresses.

230. The peripheral device according to claim 221, wherein the peripheral device is configured to cause the transceiver to follow a protocol that involves a plurality of data blocks and a plurality of status blocks that each include a channel identifier, in association with retransmission of data such that the data is transmitted multiple times.

231. The peripheral device according to claim 221, wherein the peripheral device is configured to cause the transceiver to follow a protocol that involves a plurality of data blocks and a plurality of status blocks that each include a channel identifier.

232. The peripheral device according to claim 231, wherein the channel identifier includes a stream number.

233. The peripheral device according to claim 231, wherein the status blocks are utilized for controlling retransmission.

234. The peripheral device according to claim 231, wherein a first channel identifier associated with at least one of the status blocks is different than a second channel identifier associated with at least one of the data blocks.

235. The peripheral device according to claim 231, wherein at least one of the data blocks includes data to be retransmitted and at least one of the status blocks is adapted for controlling transmission of the at least one data block.

236. The peripheral device according to claim 221, wherein the message to indicate the availability of the hub device for peripheral device attachment is sent via a broadcast.

237. The peripheral device according to claim 221, wherein the peripheral device attachment and peripheral device detachment is automatic.

238. The peripheral device according to claim 221, wherein the peripheral device is configured such that the plurality of MAC addresses is used to identify the peripheral device.

239. The peripheral device according to claim 221, wherein the plurality of MAC addresses is associated with the peripheral device.

240. The peripheral device according to claim 221, wherein the peripheral device is operable such that the plurality of MAC addresses is capable of being used to identify virtual peripheral entities associated with the peripheral device, the peripheral device attachment is automatic, and at least three of the MAC addresses are capable of existing simultaneously in association with the peripheral device.

241. The peripheral device according to claim 221, wherein the circuitry is configured to manage network timing with the hub device to enable the allocation of available bandwidth with other peripheral devices with which the hub device is currently communicating.

242. The peripheral device according to claim 221, wherein the peripheral device is configured to cause the transceiver to send, to the hub device, one or more additional identifiers, wherein the one or more identifiers is used to further identify communications between the hub device and the peripheral device.

243. The peripheral device according to claim 242, wherein the one or more additional identifiers includes a stream number for identifying a particular communication channel between the peripheral device and the hub device.

244. The peripheral device according to claim 242, wherein the one or more identifiers is associated with a token that includes a stream number for identifying a particular communication channel between the peripheral device and the hub device, and the peripheral device identifier.

245. The peripheral device according to claim 221, wherein the peripheral device identifier is associated with a network address.

246. The peripheral device according to claim 221, wherein the message to indicate the availability of the hub device for peripheral device attachment includes a heartbeat signal.

247. The peripheral device according to claim 221, wherein the message to indicate the availability of the hub device for peripheral device attachment is an initial message.

248. The peripheral device according to claim 221, wherein the peripheral device is operable such that an attachment process is initialized with the message to indicate the availability of the hub device for peripheral device attachment.

249. The peripheral device according to claim 221, wherein the peripheral device is operable such that the message to indicate the availability of the hub device for peripheral device attachment is received repeatedly.

250. The peripheral device according to claim 221, wherein the peripheral device is configured to cause the transceiver to follow a protocol that involves a plurality of data blocks and a plurality of status blocks that each include a channel identifier, in association with transmission of data multiple times.

251. The peripheral device according to claim 221, wherein the sent message includes a hub device identifier.

252. The peripheral device according to claim 221, wherein the peripheral device is operable such that an attachment process is initialized with the message to indicate the availability of the hub device for peripheral device attachment.

253. The peripheral device according to claim 221, wherein the message indicating the availability of the peripheral device includes an attachment peripheral device identifier.

254. The peripheral device according to claim 253, wherein the attachment peripheral device identifier is initially provided by the peripheral device after the message to indicate the availability of the hub device for peripheral device attachment is sent.

255. The peripheral device according to claim 253, wherein the attachment peripheral device identifier is received from the peripheral device in response to the message to indicate the availability of the hub device for peripheral device attachment.

256. The peripheral device according to claim 221, wherein the message indicating the availability of the peripheral device includes a temporary peripheral device identifier, for use during an attachment process.

257. The peripheral device according to claim 221, wherein the peripheral device is operable such that:

one of the MAC addresses is used for identification in association with a first entity of the peripheral device and another one of the MAC addresses is used for identification in association with a second entity of the peripheral device;

the first entity includes a first controller and the second entity includes a second controller;

the peripheral device attachment is capable of being automatic;

at least three of the MAC addresses are capable of existing simultaneously in association with the peripheral device which includes a single physical device;

the transceiver is caused to follow a protocol that involves a plurality of data blocks and a plurality of status blocks that each include a channel identifier, in association with transmission of data multiple times;

a first one of the MAC addresses is utilized for attachment purposes and a second one of the MAC addresses is utilized for data transfer;

the first one of the MAC addresses is initially used for the attachment purposes in association with the peripheral device without use of the second one of the MAC addresses, after which the second one of the MAC addresses is utilized; and

the first one of the MAC addresses has a first one or more channels associated therewith with a capability of transferring a first amount of data and the second one of the MAC addresses has a second one or more channels associated therewith with a capability of transferring a second amount of data that is different than the first amount of data.

258. The peripheral device according to claim 257, wherein the peripheral device is operable such that the plurality of MAC addresses is used by a link layer embodied on a computer readable medium that resides between a physical layer and a network layer embodied on the computer readable medium, and is responsible for assignment of the plurality of MAC addresses.

259. The peripheral device according to claim 257, wherein the peripheral device is operable such that an attachment process is initialized with the message to indicate the availability of the hub device for peripheral device attachment;

the message to indicate the availability of the hub device for peripheral device attachment is sent repeatedly;

i)-vi) are communications associated with the attachment process;

the transceiver is caused to communicate between the hub device and the peripheral device, utilizing one or more additional identifiers; and

a memory is included with a control structure embodied thereon that performs network bandwidth control.

260. The peripheral device according to claim 221, wherein the peripheral device identifier includes a newly-selected address.

261. The peripheral device according to claim 221, wherein the peripheral device identifier includes a previously-assigned address.

262. The peripheral device according to claim 221, wherein the peripheral device is configured for reattachment.

263. The peripheral device according to claim 262, wherein the reattachment involves an attach request using a previously-assigned address.

264. The peripheral device according to claim 262, wherein the reattachment involves an attach request using a newly-selected address.

265. The peripheral device according to claim 221, wherein at least i)-iv) are communications associated with an attachment process.

266. The peripheral device according to claim 221, wherein i)-vi) are communications associated with an attachment process.

267. The peripheral device according to claim 221, wherein iv) includes a confirmation message.

268. The peripheral device according to claim 221, wherein v) includes a confirmation message.

269. The peripheral device according to claim 221, wherein vi) includes an acknowledgement message.

270. The peripheral device according to claim 221, wherein i)-vi) are the only communications associated with an attachment process.

271. The peripheral device according to claim 221, wherein no other communications occur between i)-ii), no other communications occur between ii)-iii), no other communications occur between iii)-iv), no other communications occur between iv)-v), and no other communications occur between v)-vi).

272. The peripheral device according to claim 221, wherein the peripheral device is configured to receive keep-alive messages from the hub device.

273. The peripheral device according to claim 221, wherein the peripheral device is configured to cause the transceiver to communicate between the hub device and the peripheral device, utilizing one or more additional identifiers.

274. The peripheral device according to claim 273, wherein the one or more additional identifiers includes a stream identifier.

275. The peripheral device according to claim 273, wherein the one or more additional identifiers indicates a direction of a data transfer.

276. The peripheral device according to claim 273, wherein the one or more additional identifiers indicates a size of a data transfer.

277. The peripheral device according to claim 273, wherein the peripheral device is operable such that the one or more additional identifiers is received from the hub device.

278. The peripheral device according to claim 273, wherein the peripheral device is operable such that the one or more additional identifiers is used to further identify communications between the hub device and the peripheral device.

279. The peripheral device according to claim 273, wherein the one or more additional identifiers includes a stream number for identifying a communication channel between the peripheral device and the hub device.

280. The peripheral device according to claim 279, wherein the communication channel is uni-directional.

281. The peripheral device according to claim 273, wherein the one or more additional identifiers are included in a token.

282. The peripheral device according to claim 281, wherein the token includes a stream number.

283. The peripheral device according to claim 282, wherein the stream number is for identifying a particular communication channel between the peripheral device and the hub device.

284. The peripheral device according to claim 282, wherein the stream number is for identifying a particular communication channel between the peripheral device and the hub device, and an address for the peripheral device.

285. The peripheral device according to claim 221, wherein the peripheral device is configured to cause the transceiver to communicate via a communications protocol shared by the hub device and the peripheral device to synchronize timing of the communication.

286. The peripheral device according to claim 285, wherein the communications protocol includes a plurality of frames.

287. The peripheral device according to claim 286, wherein each of the frames includes a signal that marks a start of the frame.

288. The peripheral device according to claim 286, wherein each of the frames is associated with at least one data transfer opportunity that permits the hub device to communicate a data block with the peripheral device.

289. The peripheral device according to claim 221, wherein the peripheral device includes a memory including a link layer control structure embodied thereon that performs network bandwidth control.

290. The peripheral device according to claim 221, wherein the peripheral device includes a memory including a control structure embodied thereon that performs token planning.

291. The peripheral device according to claim 221, wherein the peripheral device includes a memory including a network interface structure embodied thereon that determines whether or when to schedule a data transfer, and a link layer transport structure embodied thereon that provides a reliable data transfer for a network interface.

292. The peripheral device according to claim 221, wherein the peripheral device includes a memory including a link layer transport structure embodied thereon that provides a reliable data transfer for a network interface.

293. The peripheral device according to claim 221, wherein the peripheral device includes a memory including a link layer control structure embodied thereon that performs token planning.

294. The peripheral device according to claim 221, wherein the peripheral device includes a memory including a structure embodied thereon that provides a reliable data transfer for a network interface.

295. The peripheral device according to claim 221, wherein at least one of the hub device and the peripheral device is further configured to transfer the same data in multiple forms.

296. The peripheral device according to claim 295, wherein a stream on which the data is communicated indicates a form of transfer.

297. The peripheral device according to claim 295, wherein at least one of the hub device and the peripheral device is further configured to combine the multiple forms of the same data to reconstruct the data.

298. The peripheral device according to claim 295, wherein the multiple forms include an original form and at least one of a complemented form and a reverse order form.

299. The peripheral device according to claim 295, wherein the multiple forms include at least one of a complemented form and a reverse order form.

300. The peripheral device according to claim 221, wherein the peripheral device is further configured to schedule transmission of a status block from the peripheral device.

301. The peripheral device according to claim 300, wherein the peripheral device is operable such that a transmission of data from the peripheral device is scheduled when the status block from the peripheral device indicates that the peripheral device has data ready for transmission to the hub device.

302. The peripheral device according to claim 221, wherein the peripheral device is operable such that the plurality of MAC addresses is capable of being used to identify virtual peripheral entities associated with the peripheral device, the peripheral device attachment is automatic, at least three MAC addresses are capable of existing simultaneously, a first one of the MAC addresses is utilized for attachment purposes, and a second one of the MAC addresses is utilized for data transfer.

303. The peripheral device according to claim 221, wherein the peripheral device is operable such that a first one of the MAC addresses is utilized for attachment purposes.

304. The peripheral device according to claim 303, wherein the peripheral device is operable such that a second one of the MAC addresses is utilized for data transfer.

305. The peripheral device according to claim 304, wherein the peripheral device is operable such that the first one of the MAC addresses is also used for data transfer.

306. The peripheral device according to claim 303, wherein the peripheral device is operable such that a second one of the MAC addresses is utilized for non-attachment purposes.

307. The peripheral device according to claim 221, wherein the peripheral device is operable such that a first one of the MAC addresses has a first plurality of channels associated therewith and a second one of the MAC addresses has a second plurality of channels associated therewith.

308. The peripheral device according to claim 307, wherein the first plurality of channels include channels supported by the first MAC address.

309. The peripheral device according to claim 307, wherein the first plurality of channels include active channels supported by the first MAC address.

310. The peripheral device according to claim 307, wherein the peripheral device is operable such that different channels are utilized for different functions.

311. The peripheral device according to claim 221, wherein the peripheral device includes a transceiver and digital control logic integrated on a single integrated circuit.

312. The peripheral device according to claim 221, wherein the peripheral device includes a host, a transceiver, and digital control logic integrated on a single integrated circuit.

313. The peripheral device according to claim 221, and further comprising:

a software architecture embodied in memory including a link layer driver layer, a link layer transport layer, a network interface layer, and a link layer control layer.

314. The peripheral device according to claim 221, and further comprising:

a software architecture embodied in memory including i) a link layer driver layer, ii) a link layer transport layer, and iii) a network interface layer, where i) resides below ii), and ii) resides below iii).

315. The peripheral device according to claim 221, wherein the peripheral device is operable such that a first one of the MAC addresses has a first plurality of channels associated therewith with a capability of transferring a first amount of data and a second one of the MAC addresses has a second plurality of channels associated therewith with a capability of transferring a second amount of data less than the first amount of data.

316. The peripheral device according to claim 315, wherein the first amount of data is provided utilizing a first data block size, and the second amount of data is provided utilizing a second data block size.

317. The peripheral device according to claim 221, wherein the peripheral device is operable such that a first one of the MAC addresses has a plurality of channels associated therewith with a capability of transferring an amount of data that has an associated maximum size.

318. The peripheral device according to claim 221, wherein the peripheral device is operable such that a plurality of streams are partitioned between the MAC addresses.

319. The peripheral device according to claim 221, wherein the circuitry includes a processor.

320. The peripheral device according to claim 221, wherein the peripheral device includes a first peripheral device that is a component of a system, the system further including a second peripheral device.

321. The peripheral device according to claim 320, wherein the system further includes the hub device.

322. The peripheral device according to claim 221, wherein the peripheral device is operable such that i) occurs before ii), ii) occurs before iii), iv) occurs before v), and vi) occurs before v).

323. The peripheral device according to claim 221, wherein the peripheral device is operable such that only a first one of the MAC addresses is initially used for identification in association with the peripheral device, after which a second one of the MAC addresses is utilized.

324. The peripheral device according to claim 221, wherein the peripheral device is operable such that only a first one of the MAC addresses is initially used for identification in association with the peripheral device, after which a second one of the MAC addresses is utilized simultaneously with the first MAC address.

325. The peripheral device according to claim 221, wherein the peripheral device is operable such that a first one of the MAC addresses is used for identification in association with a first entity of the peripheral device, and a second one of the MAC addresses is used for identification in association with a second entity of the peripheral device.

326. The peripheral device according to claim 325, wherein the first entity includes a first controller, and the second entity includes a second controller.

327. The peripheral device according to claim 221, wherein the peripheral device is operable such that a first one of the MAC addresses has a first plurality of channels associated therewith with a first capability and a second one of the MAC addresses has a second plurality of channels associated therewith with a second capability different from the first capability.

328. The peripheral device according to claim 221, wherein the peripheral device is operable such that a first one of the MAC addresses has a first plurality of channels associated therewith with a first communication purpose and a second one of the MAC addresses has a second plurality of channels associated therewith with a second communication purpose different from the first communication purpose.

329. The peripheral device according to claim 221, wherein the peripheral device is operable such that data is sent via a first channel, and the data is also sent via a second channel.

330. The peripheral device according to claim 329, wherein the peripheral device is operable such that the data is sent via the first channel using a first format, and the data is sent via the second channel using a second format.

331. The peripheral device according to claim 221, wherein the signal includes an attachment-related message.

332. The peripheral device according to claim 221, wherein the peripheral device is operable such that the plurality of MAC addresses is capable of being used to identify virtual peripheral entities associated with the peripheral device, where the peripheral device includes a single physical device.

333. The peripheral device according to claim 332, wherein the virtual peripheral entities include virtual devices.

334. The peripheral device according to claim 221, wherein the peripheral device is configured to respond in connection with each of the plurality of MAC addresses.

335. The peripheral device according to claim 221, wherein the peripheral device is further configured to associate a plurality of active communication streams with each of the plurality of MAC addresses.

336. The peripheral device according to claim 221, wherein the peripheral device includes a plurality of virtual peripheral devices.

337. The peripheral device according to claim 221, wherein the peripheral device attachment is automatic.

338. The peripheral device according to claim 221, wherein the peripheral device includes a computer readable medium with computer code embodied thereon including a transport layer capable of providing enhanced capabilities.

339. The peripheral device according to claim 27, wherein the sent message is a broadcasted message.

340. The peripheral device according to claim 339, wherein the response in iv) includes the peripheral device identifier.

341. The peripheral device according to claim 340, wherein the broadcasted message includes a heartbeat signal.

342. The peripheral device according to claim 340, wherein the broadcasted message is an initial message.

343. The peripheral device according to claim 340, wherein the peripheral device is operable such that an attachment process is initialized with the broadcasted message.

344. The peripheral device according to claim 340, wherein the peripheral device is operable such that the broadcasted message is received periodically.

345. The peripheral device according to claim 340, wherein the broadcasted message includes a hub device identifier.

346. The peripheral device according to claim 345, wherein the hub device identifier includes a MAC address.

347. The peripheral device according to claim 345, wherein the peripheral device is operable such that an attachment process is initialized with the broadcasted message.

348. The peripheral device according to claim 340, wherein the message indicating the availability of the peripheral device includes an attachment peripheral device identifier.

349. The peripheral device according to claim 348, wherein the peripheral device is operable such that the attachment peripheral device identifier is initially received from the peripheral device after the broadcasted message is broadcasted.

350. The peripheral device according to claim 348, wherein the peripheral device is operable such that the attachment peripheral device identifier is received from the peripheral device in response to the broadcasted message.

351. The peripheral device according to claim 340, wherein the message indicating the availability of the peripheral device includes a temporary peripheral device identifier, for use during an attachment process.

352. The peripheral device according to claim 340, wherein the message indicating the availability of the peripheral device includes an attachment peripheral device identifier that is, at least in part, randomly selected.

353. The peripheral device according to claim 340, wherein the message indicating the availability of the peripheral device includes an attachment peripheral device identifier that is selected from a range of identifiers.

354. The peripheral device according to claim 340, wherein the message indicating the availability of the peripheral device includes an attachment peripheral device identifier that is selected by the peripheral device.

355. The peripheral device according to claim 340, wherein the peripheral device identifier includes a newly-selected address.

356. The peripheral device according to claim 340, wherein the peripheral device identifier includes a previously-assigned address.

357. The peripheral device according to claim 340, wherein the peripheral device is configured to cause the transceiver to perform a reattachment function.

358. The peripheral device according to claim 357, wherein the reattachment function involves an attach request using a previously-assigned address.

359. The peripheral device according to claim 357, wherein the reattachment function involves an attach request using a newly-selected address.

360. The peripheral device according to claim 340, wherein at least i)-iii) are communications associated with an attachment process.

361. The peripheral device according to claim 340, wherein at least i)-iv) are communications associated with an attachment process.

362. The peripheral device according to claim 340, wherein iv) includes a confirmation message.

363. The peripheral device according to claim 340, wherein v) includes a confirmation message.

364. The peripheral device according to claim 340, wherein vi) includes an acknowledgement message.

365. The peripheral device according to claim 340, wherein no other communications occur between i) and ii).

366. The peripheral device according to claim 340, wherein no other communications occur between ii) and iii).

367. The peripheral device according to claim 340, wherein the peripheral device is configured to receive keep-alive messages from the hub device.

368. The peripheral device according to claim 340, wherein the peripheral device is configured to cause the transceiver to communicate with the hub device, utilizing one or more additional identifiers.

369. The peripheral device according to claim 368, wherein the one or more additional identifiers includes a stream identifier.

370. The peripheral device according to claim 368, wherein the one or more additional identifiers indicates a direction of a data transfer.

371. The peripheral device according to claim 368, wherein the one or more additional identifiers indicates a size of a data transfer.

372. The peripheral device according to claim 368, wherein the peripheral device is operable such that the one or more additional identifiers is received from the hub device.

373. The peripheral device according to claim 368, wherein the peripheral device is configured such that the one or more additional identifiers is used to further identify communications between the hub device and the peripheral device.

374. The peripheral device according to claim 368, wherein the one or more additional identifiers includes a stream number for identifying a communication channel between the peripheral device and the hub device.

375. The peripheral device according to claim 374, wherein the communication channel is uni-directional.

376. The peripheral device according to claim 368, wherein the one or more additional identifiers is associated with a token.

377. The peripheral device according to claim 376, wherein the token includes a stream number.

378. The peripheral device according to claim 377, wherein the stream number is for identifying a particular communication channel between the peripheral device and the hub device.

379. The peripheral device according to claim 377, wherein the stream number is for identifying a particular communication channel between the peripheral device and the hub device and an address for the peripheral device.

380. The peripheral device according to claim 340, wherein the peripheral device is configured to cause the transceiver to communicate via a communications protocol shared by the hub device and the peripheral device to synchronize timing of the communication.

381. The peripheral device according to claim 380, wherein the communications protocol includes a plurality of frames.

382. The peripheral device according to claim 381, wherein each of the frames includes a signal that marks a start of the frame.

383. The peripheral device according to claim 381, wherein each of the frames includes at least one token transmission that identifies at least one data transfer opportunity that permits the hub device to communicate a data block with the peripheral device.

384. The peripheral device according to claim 340, wherein the peripheral device includes a memory including a control structure embodied thereon that performs network bandwidth control.

385. The peripheral device according to claim 340, wherein the peripheral device includes a memory including a link layer control structure embodied thereon that performs token planning.

386. The peripheral device according to claim 340, wherein the peripheral device includes a memory including a network interface structure embodied thereon that determines whether or when to schedule a data transfer, and a link layer transport structure embodied thereon that provides a reliable data transfer for a network interface.

387. The peripheral device according to claim 340, wherein the peripheral device includes a memory including a link layer transport structure embodied thereon that provides a reliable data transfer for a network interface.

388. The peripheral device according to claim 340, wherein the peripheral device includes a memory including a control structure embodied thereon that performs token planning.

389. The peripheral device according to claim 340, wherein the hub device includes a memory including a link layer transport structure embodied thereon that provides a reliable data transfer for a network interface.

390. The peripheral device according to claim 340, wherein at least one of the hub device and the peripheral device is further configured to transfer the same data in multiple forms.

391. The peripheral device according to claim 390, wherein a stream on which the data is communicated indicates a form of transfer.

392. The peripheral device according to claim 390, wherein at least one of the hub device and the peripheral device is further configured to combine the multiple forms of the same data to reconstruct the data.

393. The peripheral device according to claim 390, wherein the multiple forms include an original form and at least one of a complemented form and a reverse order form.

394. The peripheral device according to claim 390, wherein the multiple forms include at least one of a complemented form and a reverse order form.

395. The peripheral device according to claim 340, wherein the hub device is further configured to schedule transmission of a status block from the peripheral device.

396. The peripheral device according to claim 395, wherein the hub device is further configured to schedule transmission of data from the peripheral device when the status block from the peripheral device indicates that the peripheral device has data ready for transmission to the hub device.

397. The peripheral device according to claim 221, wherein the peripheral device includes a cellular phone.

398. The peripheral device according to claim 221, wherein the peripheral device includes a computer.

399. The peripheral device according to claim 221, wherein the peripheral device includes a movement sensor.

400. The peripheral device according to claim 221, wherein the peripheral device includes a bar code scanner.

401. The peripheral device according to claim 340, wherein the peripheral device is configured to cause the transceiver to communicate with the hub device utilizing a plurality of additional identifiers, the peripheral device being configured such that the plurality of additional identifiers is used to further identify communications between the hub device and the peripheral device.