Automatic attachment and detachment for hub and peripheral devices

• US 8,582,570 B2
• Filed: 02/04/2013
• Issued: 11/12/2013
• Est. Priority Date: 03/27/2000
• Status: Expired due to Fees

• Current Assignee: RPX Corporation
• Original Assignee: Tri-County Excelsior Foundation (Oso IP, LLC)
• Inventors: Donaghey, Robert J
• Primary Examiner(s): PHAN, MAN U
• Application Number:
  US13/758,866
• Publication Number:
  US 20130265947A1
• Time in Patent Office: 281 Days
• Field of Search: 370230-313, 370338-347, 370403-449, 709224-229, 710 17- 29
• 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 hub device comprises circuitry and a transceiver in communication with the circuitry. In operation, the hub device is configured to cause the transceiver to i) send a message to indicate the availability of the hub device for attachment to a first peripheral device, ii) receive, from the 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.

Claims

1. 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 attachment to a first peripheral device,

ii) receive, from the 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;

wherein the hub device is operable such that a plurality of unique addresses is operable for being used for identification in association with the first peripheral device;

wherein the hub device is operable such that a first one of the unique addresses is operable for being utilized in connection with a first attachment to the first peripheral device and a second one of the unique addresses is operable for being utilized for data transfer;

wherein the hub device is operable such that the first one of the unique addresses is operable for being initially used in connection with the first attachment to the first peripheral device, after which the second one of the unique addresses is operable for being utilized for the data transfer;

wherein the hub device is operable such that the first one of the unique addresses has a first one or more channels associated therewith with a capability of transferring a first size of communication and the second one of the unique addresses has a second one or more channels associated therewith with a capability of transferring a second size of communication different than the first size of communication.

2. The device according to claim 1, wherein the hub device is operable such that prior to an initiation of the first attachment, there is no communication between the first peripheral device and the hub device.

3. The device according to claim 1, wherein the hub device is operable such that the unique addresses include MAC addresses;

and the hub device is operable such that the unique addresses are generated by the hub device.

4. The device according to claim 1, wherein the hub device is operable such that the unique addresses each uniquely identify the first peripheral device on a shared communication medium.

5. The device according to claim 1, wherein the hub device is operable such that 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, wherein the status blocks are utilized for controlling retransmission.

6. The device according to claim 1, wherein the hub device is operable for providing the first attachment in the personal area network such that i) occurs before ii), ii) occurs before iii), iv) occurs before v), v) occurs before vi), 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).

29. The device according to claim 1, wherein the one or more channels includes at least one of:

one or more links, or one or more streams;

one of the plurality of unique addresses includes the first peripheral device identifier;

the size relates to a block size; and

the message to indicate the availability of the hub device for attachment to the first peripheral device indicates by indicating the availability of the hub device for attachment to any peripheral device.

7. 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 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;

wherein the peripheral device is operable such that a plurality of unique addresses is operable for being used for identification in association therewith;

wherein the peripheral device is operable such that a first one of the unique addresses is utilized in association with a first attachment to the hub device, after which a second one of the unique addresses is utilized for data transfer;

wherein the peripheral device is operable such that the first one of the unique addresses has a first one or more channels associated therewith with a capability of transferring a first amount and the second one of the unique addresses has a second one or more channels associated therewith with a capability of transferring a second amount different than the first amount.

8. The device according to claim 7, wherein the peripheral device is operable such that i), ii), iii), iv), v), and vi) are carried out by a first entity;

and i), ii), iii), iv), v), and vi) are further carried out by a second entity.

9. The device according to claim 8, wherein the peripheral device is operable such that the hub device associated with the first entity and the second entity includes the same hub device.

10. The device according to claim 7, wherein the peripheral device is operable such that the first one of the unique addresses is used for the first attachment without use of the second one of the unique addresses, after which the second one of the unique addresses is utilized.

11. A peripheral device, comprising:

circuitry, and

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

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

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

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

send a response to the hub device,

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

send, to the hub device, a second peripheral response including the peripheral device identifier;

wherein the peripheral device is operable such that a unique address is operable for being assigned by the peripheral device prior to a completion of attachment to the hub device for use in identifying the peripheral device in connection with a group associated with the hub device;

wherein the peripheral device is operable such that a first one of a plurality of unique addresses has a first one or more channels associated therewith with a first data transfer capability associated therewith and a second one of the plurality of unique addresses has a second one or more channels associated therewith with a second data transfer capability associated therewith that is different than the first data transfer capability.

12. The device according to claim 11, wherein the peripheral device is configured such that a unique identifier is operable for being assigned by the hub device for use only in connection with the group associated with the hub device.

30. The device according to claim 11, wherein the unique address is either the first one of the plurality of unique addresses or the second one of the plurality of unique addresses;

and the unique address is the first peripheral device identifier.

13. A device, comprising:

a first entity configured to;

receive a first entity-related other device message from at least one other device to indicate the availability of the at least one other device for attachment,

send, to the at least one other device, a first entity-related message indicating the availability for communication with the at least one other device,

receive, from the at least one other device, a first entity-related signal including a first entity-related device identifier,

send a first entity-related response to the at least one other device,

receive, from the at least one other device, a first entity-related other device response, and

send, to the at least one other device, a first entity-related second response including the first entity-related device identifier; and

a second entity configured to;

receive a second entity-related other apparatus message from at least one other apparatus to indicate the availability of the at least one other apparatus for attachment,

send, to the at least one other apparatus, a second entity-related message indicating the availability for communication with the at least one other apparatus,

receive, from the at least one other apparatus, a second entity-related signal including a second entity-related device identifier,

send a second entity-related response to the at least one other apparatus,

receive, from the at least one other apparatus, a second entity-related other apparatus response, and

send, to the at least one other apparatus, a second entity-related second response including the second entity-related device identifier;

wherein the first entity is configured such that a particular unique address is operable for being assigned by the first entity prior to a completion of attachment to the at least one other device for use in identifying the first entity in connection with a group associated with the at least one other device.

14. The device according to claim 13, wherein the device is configured such that the first entity includes a first virtual entity and the second entity includes a second virtual entity.

15. The device according to claim 13, wherein the device is configured such that the first entity includes an associated first controller and the second entity includes an associated second controller.

16. The device according to claim 13, wherein the device is configured such that the first entity includes an associated first transceiver and the second entity includes an associated second transceiver.

17. The device according to claim 13, wherein the device is configured such that the at least one other device is the at least one other apparatus.

18. The device according to claim 13, wherein the device is configured such that the at least one other device or the at least one other apparatus includes at least one hub device, and the device includes a peripheral device.

19. The device according to claim 13, wherein the device is configured such that a first unique address is used for identification in association with the first entity and a second unique address is used for identification in association with the second entity.

20. The device according to claim 19, wherein the device is configured such that the first unique address uniquely identifies the first entity on a shared communication medium and the second unique address uniquely identifies the second entity on the shared communication medium.

21. The device according to claim 13, wherein the second entity is configured such that a plurality of unique addresses is operable for being used for identification in association therewith.

22. The device according to claim 21, wherein the second entity is configured such that a first one of the unique addresses has a first one or more channels associated therewith with a capability of transferring a first amount and a second one of the unique addresses has a second one or more channels associated therewith with a capability of transferring a second amount different than the first amount.

23. The device according to claim 22, wherein the second entity is configured such that the first one of the unique addresses is operable for being utilized for a first attachment to the second entity and the second one of the unique addresses is operable for being utilized for data transfer;

the first one of the unique addresses is operable for being initially used for the first attachment to the second entity, after which the second one of the unique addresses is operable for being utilized;

there is no communication between the second entity and the at least one other apparatus prior to an initiation of the first attachment;

each send and receive capability of the second entity includes no communication therebetween; and

each send and receive capability of the second entity is for attachment purposes in a personal area network.

24. The device according to claim 21, wherein the second entity is configured such that a first one of the unique addresses is operable for being selected by the second entity, a second one of the unique addresses is operable for being selected by the at least one other apparatus, and the first entity is configured such that the particular unique address is assigned by the first entity by being self-selected by the first entity.

25. The device according to claim 13, wherein the first entity is configured such that a unique identifier is operable for being assigned by the at least one other device for use only in connection with the group associated with the at least one other device.

26. The device according to claim 13, wherein the first entity is configured such that the particular unique address is operable for being assigned by the first entity by being selected from one or more already-existing unique addresses.

27. The device according to claim 13, wherein the first entity is configured such that the particular unique address remains assigned for only a duration of the attachment.

28. The device according to claim 13, wherein the first entity is configured such that the particular unique address remains assigned for a duration of the attachment of the first entity to the at least one other device.