WO2008134743A1

WO2008134743A1 - Reconfigurable network system and method

Info

Publication number: WO2008134743A1
Application number: PCT/US2008/062061
Authority: WO
Inventors: Craig Sayers; Paul Hiles; Ian Robinson; Geoff Lyon
Original assignee: Hewlett-Packard Development Company, L.P.
Priority date: 2007-04-30
Filing date: 2008-04-30
Publication date: 2008-11-06

Abstract

A reconfigurable network system comprises a dock having a plurality of external ports, the dock comprising a controller configured to automatically reconfigure internal couplings of the dock based on which of the plurality of external ports a host-capable system is connected.

Description

RECONFIGURABLE NETWORK SYSTEM AND METHOD

BACKGROUND

[0001] Various electronic devices, such as cellular phones, personal digital assistants (PDAs), and digital cameras, may have different but somewhat overlapping capabilities, and a user may wish to exchange information between the different devices. For example, a user may wish to exchange a list of phone numbers between a PDA and a cell phone or exchange a video clip between a cell phone and a digital camera. When two or more devices are connected, one device typically needs to function as a host in order to control the movement of data, whereas other devices function as peripherals, or slave devices, under the control of the host. In order to simplify connections, some devices, such as digital cameras, may be designed to function as a peripheral whenever they are connected to another device. However, a user may wish to choose a particular device to be the host, based on the user's preference for and familiarity with that device.

BRIEF DESCRIPTION OF THE DRAWINGS

[0002] For a more complete understanding of the present application, the objects and advantages thereof, reference is now made to the following descriptions taken in conjunction with the accompanying drawings, in which:

[0003] FIGURES IA and IB are diagrams illustrating an embodiment of a reconfϊgurable dock in different configurations for a reconfϊgurable network system;

[0004] FIGURE 2 is a diagram illustrating embodiments of different components for a reconfϊgurable network system;

[0005] FIGURE 3 is a diagram illustrating embodiments of different host- capable systems for a reconfϊgurable network system;

[0006] FIGURE 4 is a diagram illustrating embodiments of different host- capable systems for a reconfϊgurable network system;

[0007] FIGURE 5 is a diagram illustrating embodiments of a reconfϊgurable network system using different network components; and

[0008] FIGURE 6 is a flow diagram illustrating a method of reconfiguring a network. DETAILED DESCRIPTION OF THE DRAWINGS

[0009] FIGURES IA and IB are diagrams illustrating different operating configurations of an embodiment of a reconfϊgurable dock 100 for a reconfigurable network system. In some embodiments, dock 100 automatically reconfigures internal port couplings to enable an external system or device connected to dock 100 to function as either a host or a peripheral based upon a particular port of dock 100 to which the system or device is connected. A host system is a system that controls its own resources, for example a memory of the host system, as well as resources in a peripheral system. A peripheral system, such as an input/output device, is a system that has its resources controlled by another system.

[0010] Embodiments of dock 100 enable a user to select a particular system to function as a host in a multi-system network by connecting the desired host to a particular port of dock 100. Thus, some embodiments of dock 100 provide network configuration flexibility for enabling a user to specify a host without burdensome complexity. In some embodiments, dock 100 is configured to function as a docking station for a computing system comprising at least one of a cellular phone, a personal digital assistant (PDA), a computer, an audio device, a video device, a gaming device and a terminal unit. However, it should be understood that dock 100 may be configured to dock with other types of devices.

[0011] In the embodiment illustrated in FIGURES IA and IB, dock 100 comprises a communication module 116 coupled to three external ports 101-103. External ports 101-103 are configured to couple dock 100 to external systems or devices. In FIGURES IA and IB, communication module 116 comprises a controller 104 and a communication hub 105. In the embodiment illustrated in FIGURES IA and IB, controller 104 comprises ports 106-109, and communication hub 105 comprises a master port 110 and five slave ports 111-115. However, it should be understood that a greater or fewer quantity of slave ports may be used. In some embodiments, communication hub 105 comprises a universal serial bus (USB) hub, although it should be understood that other connection protocols in addition to or in place of USB may be used. In some embodiments, external port 101 is configured to have a form factor compatible with external port 102 such that a connector similar to external port 101 is connectable to external port 102 and a connector similar to external port 102 is connectable to external port 101.

[0012] In the embodiment illustrated in FIGURES IA and IB, dock 100 further comprises a user interface (UI) 119 coupled to slave port 115, an expansion port 117 coupled to slave port 114, and a dock-specific function 118 coupled to slave port 113. In some embodiments, UI 119 may comprise a keyboard, a display, an audio device, a pointer device, a media reader, a printer, an imaging device, a communication system, a gaming device, a biometric device or any other type of user interface for inputting information to and/or receiving information from dock 100. In some embodiments, expansion port 117 may comprise a port suitable for coupling an expansion device to dock 100 to expand the capabilities of dock 100. For example, expansion port 117 may comprise a memory connector or a PDA expansion connector. In some embodiments, dock-specific function 118 may comprise a particular function associated with the particular type or configuration of dock 100 (e.g., whether dock 100 is configured for a PDA or whether dock 100 is configured for a notebook computer). Thus, in some embodiments, for example, dock- specific function 108 may comprise a network interface, such as an Ethernet adapter, for enabling communications with a network via dock 100. However, it should be understood that in some embodiments, dock-specific function 118 may comprise different functionality.

[0013] In some embodiments, master port 110 is the port of communication hub 105 to which a host system is coupled, whereas peripheral systems are coupled to slave ports 111-115 of communication hub 105. In some embodiments, dock 100 enables a particular external system to act as a host system, at least in part, by coupling that system to master port 110, whereas other external systems would be coupled to slave ports 111-115. In order to simplify network configuration for a user, some embodiments of controller 104 automatically select one of external ports 101 and 102 for coupling with master port 110 and couple the other one of external ports 101 and 102 to one of slave ports 111-115. For some embodiments, if a host-capable system is connected to external port 102, external port 102 is automatically coupled to master port 110 so that the system coupled to external port 102 is enabled to act as a host (e.g., independent of whether a host-capable system is connected to external ports 101 and/or 103). However, if there is no host-capable system connected to external port 102 (e.g., there is no system connected to port 102 or the system connected to port 102 is not host-capable), then external port 101 is automatically coupled to master port 110 to enable the system coupled to external port 101 to act as a host system. Thus, in some embodiments, controller 104 automatically controls the internal coupling of master port 110 of communication hub 105 to one of external ports 101 and 102. It should be understood that controller 104 may also be configured such that, as a default configuration, a particular external port (e.g., one of ports 101 or 102) is coupled to master port 110 (e.g., in the absence of a host-capable system coupled to one of ports 101 or 102 or when host-capable systems are coupled to both ports 101 and 102). In some embodiments, controller 104 may be configured to receive an input by a user indicating which of external ports 101 and 102 the user desires to have associated with a host-capable system such that controller 104 couples the designated external port 101 or 102 to master port 110. For example, in this embodiment, if host- capable systems are coupled to both external ports 101 and 102, instead of controller 104 automatically connecting one of external ports 101 or 102 to master port 110 as a default condition, controller 104 is configured to receive user input as to which of the host capable systems connected to external ports 101 and 102 the user desires to have act as the host. Thus, in this example, instead of a user having to switch or change which host-capable systems are connected to which external ports 101 and 102 in order to have a particular or desired system to act as a host, the user input is received by controller 104 and, in response thereto, controller 104 automatically couples the indicated external port 101 or 102 to master port 110.

[0014] FIGURE IA illustrates a configuration of dock 100 in which an external system connected to port 101 functions as a host, whereas FIGURE IB illustrates a configuration of dock 100 in which an external system connected to port 102 functions as a host. In this manner, some embodiments of dock 100 enable a user to select one of two or more systems to function as the host by coupling the selected system to a particular port of dock 100.

[0015] Referring to FIGURE IA, port 106 is coupled to external port 101, port

107 is coupled to external port 102, port 108 is coupled to a master port 110 of communication hub 105, and port 109 is coupled to a slave port 111 of communication hub 105. In the embodiment illustrated in FIGURE IA where a host-capable system is coupled to external port 101, communication module 116 is configured to couple port 106 to port 108, thereby coupling external port 101 to master port 110. In this configuration, an external system coupled to external port 101 is coupled to master port 110 and is thus enabled by dock 100 to function as a host system for any systems or devices coupled to slave ports 111-115. Referring to FIGURE IB, port 107 is coupled to port 108, and port 106 is coupled to port 109, thereby coupling external port 102 to master port 110 and external port 101 to slave port 111. In this configuration, an external system coupled to external port 102 is coupled to master port 110 and is thus enabled by dock 100 to function as a host system for any systems or devices coupled to slave ports 111-115. If the configuration illustrated in FIGURE IB is selected as the default configuration for dock 100, for example, any host-capable system coupled to port 101 would be treated as a peripheral system.

[0016] Controller 104 is configured to sense the coupling of a host-capable external system (e.g. a system that is capable of controlling resources in another system or device) to external ports 101 and 102. For example, in some embodiments, controller 104 is configured to sense signals arriving on ports 106 and/or 107 to detect a signal sent by a host- capable external system that is coupled to external ports 101 and/or 102, respectively, that identifies the respective external system as host-capable. As an exemplary illustration, consider that dock 100 is presently in the configuration illustrated in FIGURE IB (e.g., without any external systems coupled to ports 101 and 102). If a host-capable system is then coupled to external port 101, controller 104 detects that a host-capable system has been coupled to external port 101 and automatically reconfigures itself so that external port 101 is coupled to master port 110. Thus, in this example, controller 104 is configured to automatically (without reference to order or a particular sequence of actions): 1) decouple port 106 from port 109; 2) decouple port 108 from port 107; 3) couple port 108 to port 106; and 4) couple port 107 to 109, thereby decoupling master port 110 from external port 102 and coupling master port 110 to external port 101 (to arrive at the configuration illustrated in FIGURE IA). It should be understood that the above actions may be reversed to arrive at the configuration illustrated in FIGURE IB (e.g., in response to detecting a disengagement of a host-capable system from external port 101 or in response to detecting a host-capable system connected to external port 102 (even though a host capable system is still connected to external port 101)).

[0017] In the embodiment illustrated in FIGURES IA and IB, external port

103 is coupled to slave port 112, enabling an external system, including a host-capable system, to couple to dock 100 as a peripheral system. Any system, including a host-capable system, coupled to dock 100 through external port 103 will function as a peripheral system, subject to control by a host system coupled to either external port 101 or external port 102. The external system coupled to dock 100 may be another embodiment of dock 100, thereby daisy-chaining multiple embodiments of dock 100. For example, external port 103 of a first dock 100 may be coupled to an external port 102 of a second dock 100, and further, an external port 103 of the second dock 100 may be coupled to an external port 102 of a third dock 100. [0018] FIGURE 2 is a diagram illustrating different embodiments of components 30 for a reconfigurable network system. In FIGURE 2, the illustrated components comprise a network dock 100_A, a keyboard dock 100_B, host-capable systems 300 and utility devices 310. In the embodiment illustrated in FIGURE 2, dock-specific function 118_A of network dock 100_A comprises a network interface, whereas for keyboard dock 100_B, UI 119_B comprises a keyboard. Thus, it should be understood that dock-specific function 118 and/or UI 119 may vary for different types of docks 100. In the embodiment illustrated in FIGURE 2, network dock 100_A and keyboard dock 100_B are configured to couple to one or more of host-capable systems 300 and devices 310.

[0019] In FIGURE 2, host-capable systems 300 comprise different types of computing systems such as a cell phone 300_A, a small PDA 300_B, a large PDA 300c and a terminal unit 300_D, although it should be understood that host-capable systems 300 may comprise other types of systems and/or devices. In FIGURE 2, each of cell phone 300_A, a small PDA 300_B, a large PDA 300c and a terminal unit 300_D comprises a docking port 301 (identified as ports 301 _{A D} in FIGURE 2, respectively) configured to couple to external port 101 on a dock 100, such as port 101_A on network dock 100_A or port 101_B on keyboard dock 100β. In some embodiments docking port 301 is configured to connect directly to external port 101. In some embodiments docking port 301 is configured to couple to external port 101 through another system or device, for example, a cable. In some embodiments, docking port 301 is configured to have a form factor similar to external port 102, such that a connector able to connect to external port 102 is also able to connect to docking port 301. In the embodiments illustrated in FIGURE 2, cell phone 300_A, a small PDA 300_B, a large PDA 300_c and a terminal unit 300_D each comprise a user interface 302_A-_D, respectively. In some embodiments, user interfaces 302_A-_D each comprise a display capable of use as data entry system, for example a touch-sensitive screen, as well as an output of displayed information.

[0020] In FIGURE 2, devices 310 comprise a cable 310_A, a power adapter

310_B, an automobile power adapter 310c, and an airplane power adapter 310_D, although it should be understood that devices 310 may comprise other types of devices. In the embodiment illustrated in FIGURE 2, cable 310a comprises a connector 312 (configured to connect to external port 102) and a connector 313 (configured to connect to external port 103). Thus, cable 310a may be used to couple two docks 100 together. For example, connector 312 of cable 310_A may be connected to external port 102_A of network dock 100_A, and connector 313 of cable 310_A may be connected to external port 103_B of keyboard dock 100_B, thereby enabling a host-capable system coupled to one of external ports 10 I_B or 102_B of keyboard dock 100_B to function as a host for keyboard dock 100_B, a host for network dock 100_A, and a host for any other systems coupled to external ports 101_A or 103 _A of network dock 100_A- Alternatively, cable 310_A may be connected to external port 102_B of keyboard dock 100_B and external port 103_A of network dock 100_A, thereby enabling a host-capable system coupled to one of external ports 101_A or 102_A of network dock 100_A to function as a host for keyboard dock 100_B, a host for network dock 100_A, and a host for any other systems coupled to external ports 101B or 103B of keyboard dock 100B. In some embodiments, connector 312 is configured to connect to docking port 301.

[0021] In FIGURE 2, each of power adapter 310_B, automobile power adapter

310c and airplane power adapter 310D comprises a port 314 (identified as ports 314A-_C in FIGURE 2, respectively) configured to couple to connector 313 on cable 310_A, thereby enabling dock 100 to receive external power through external port 102 while a host-capable system coupled to external port 101 functions as a host. In some embodiments, power adapter 310_B comprises an alternating current (AC) power adapter. In some embodiments, automobile power adapter 310c and airplane power adapter 310_D each comprise a direct current (DC) power adapter. In some embodiments, dock 100 may receive external power through external port 103.

[0022] FIGURE 3 is a diagram illustrating different embodiments of host- capable systems 300 for a reconfigurable network system. In FIGURE 3, host-capable systems 300 comprise cell phones 300AI and 300A2 and PDAs 300_B1 and 300_B2- In the illustrated embodiments, cell phone 300_AI and PDA 300_Bi are each configured to function as a host, whereas cell phone 300_A2 and PDA 30O_B2, even though host-capable, are each configured to function as a peripheral. In the embodiment illustrated in FIGURE 3, cell phones 300_AI and 300_A2 comprise processing modules 401_AI and 401_A2, persistent memories 402AI and 402A2, interface modules 403AI and 403A2 and docking ports 301AI and 301A2, respectively. Interface modules 403AI and 403A2 comprise ports 404AI and 404A2 coupled to docking ports 301AI and 301A2, ports 405AI and 405A2, coupled to processing modules 401AI and 401A2, and ports 406AI and 406A2 coupled to persistent memories 402_Ai and 402A2, respectively. Processing modules 401_AI and 401_A2 perform computing functions for respective cell phones 300AI and 300A2, and persistent memories 402AI and 402A2 store information used by respective cell phones 300_AI and 300_A2, such as a list of phone numbers. Interface modules 403AI and 403A2 configure respective cell phones 300AI and 300A2 to function as either a host or a peripheral. In some embodiments, controller 104 in dock 100 (FIGURES IA and IB) is configured to send a signal to respective interface modules 403_AI and 403A2, causing interface modules 403AI and 403A2 to configure each of respective cell phones 300_AI and 300_A2 to function as either a host or a peripheral.

[0023] In cell phone 300_AI, interface module 403_AI is configured to couple port 404_Ai to port 405 A₁, thereby coupling processing module 401_AI to docking port 301_AI and insulating persistent memory 402_AI from docking port 301_AI - Therefore, in cell phone 300AI, processing module 401AI is enabled to control persistent memory 402AI as well as to potentially control resources in a peripheral system coupled to docking port 301_AI- In cell phone 300_A2, however, interface module 403_A2 is configured to couple port 404_A2 to port 406A2, thereby coupling persistent memory 402A2 to docking port 301A2- Therefore, in cell phone 300_A2, an external system is enabled to control persistent memory 402_A2- Thus, cell phone 300_AI is configured to function as a host whereas cell phone 300_A2 is configured to function as a peripheral.

[0024] In the embodiment illustrated in FIGURE 3, PDAs 300_Bi and 300_B2 comprises processing modules 41 1BI and 41 1B2, persistent memories 412BI and 412B₂, controllers 413_BI and 413_B2, communication hubs 414_B1 and 414_B2, expansion ports 415_BI and 415B2 and docking ports 301BI and 301β2, respectively. Controllers 413BI and 413B2 comprise ports 416BI and 416B2 coupled to docking ports 301BI and 301B2, port 417BI and 417B2 coupled to processing modules 411_B1 and 41 IB₂, and ports 418BI, 418B2, 419BI and 419_B2 coupled to communication hubs 414_B1 and 414_B2, respectively. Communication hubs 414_Bi and 414_B2 comprise master ports 420_Bi and 420_B2 coupled to ports 418_Bi and 418_B2, respectively. Communication hubs 414BI and 414B2 comprise three slave ports 42IB₁, and 421B2, 422BI and 422B2, and 423BI and 423B2, respectively, although a greater or lesser quantity of slave ports may be used. Slave ports 421_Bi and 421_B2 are coupled to persistent memories 412_Bi and 412_B2, slave ports 422_Bi and 422_B2 are coupled to expansion bays 415_BI and 415B2, and slave ports 423BI and 423B2 are coupled to ports 419BI and 419B2, respectively. In some embodiments, communication hubs 414_BI and 414_B2 comprises USB hubs.

[0025] Processing modules 411_B1 and 411_B2 perform computing functions for respective PDAs 300BI and 300B2 and persistent memories 412BI and 412B2 store information used by respective PDAs 300BI and 300B2, such as a programs and data. Controllers 413BI and 413B2 configure respective PDAs 300BI and 300B2 to function as either a host or a peripheral. In some embodiments, controller 104 in dock 100 (FIGURES IA, IB and 2) is configured to send a signal to controllers 413_BI and 413_B2, causing controller 413_BI and 413_B2 to configure respective PDAs 300_BI and 30O_B2 to function as either a host or a peripheral. Master ports 420BI and 420B2 are the ports of respective communication hubs 414BI and 414_B2 to which a host system or processor couples, whereas peripheral systems and components couple to slave ports 421-423 of respective communication hubs 411_B1 and 41 1B2- Expansion ports 415BI and 415B2 comprise a port suitable for coupling an expansion device to expand the capabilities of PDAs 300BI and 300B2-

[0026] In PDA 300_BI, controller 413_BI is configured to couple port 416_BI to port 419_BI and port 417_BI to port 418_BI, thereby coupling processing module 41 l_Bi to master port 420BI and docking port 301BI to slave port 423BI- Therefore, in PDA 300BI, processing module 41 1_BI is enabled to control persistent memory 412_BI as well as to potentially control resources in a peripheral system coupled to docking port 301_Bi- In PDA 300_B2, however, controller 413_B2 is configured to couple port 416_B2 to port 418_B2 and couple port 417_B2 to port 419B2, thereby coupling processing module 411B2 to slave port 423B2 and docking port 301B2 to master port 420_B2- Therefore, in PDA 300_B2, an external system is enabled to control persistent memory 412_B2 and/or processing module 411_B2- Thus, PDA 300_BI is configured to function as a host whereas PDA 300_B2 is configured to function as a peripheral. In some embodiments, coupling PDA 300_Bi to cell phone 300_A2 through dock 100 (FIGURES IA, IB and 2) enables the transfer of information between PDA 300_BI and cell phone 300_A2, for example the transfer of a list of phone numbers between persistent memory 412_Bi and persistent memory 402_A2-

[0027] FIGURE 4 is another diagram illustrating embodiments of host- capable systems 300 for a reconfigurable network system. In FIGURE 4, host-capable systems 300 comprise terminal units 302_D1 and 302_D2. In the embodiment illustrated in FIGURE 4, terminal units 302_D1 and 302_D2 comprise processing modules 501_DI and 501_D2, ports 502_Di and 502_D2, expansion ports 503DI and 503D2, communication hubs 514_Di and 514_D2 and docking ports 301DI and 301D2, respectively. Processing modules 501DI and 501D2, ports 502_D1 and 502_D2, expansion ports 503_Di and 503_D2 and docking ports 301_Di and 301_D2 are each connected to respective communication hubs 514_D1 and 514_D2.

[0028] Processing modules 501_DI and 501_D2 perform computing functions for respective terminal units 302DI and 302D2 and are connected to master ports 520DI and 520D2 of respective communication hubs 514DI and 514D2- Processing modules 501DI and 501D2 are therefore also coupled to ports 502_D1 and 502_D2, expansion ports 503_DI and 503_D2 and docking ports 301_DI and 30I_D2 via communication hubs 514_D1 and 514_D2, respectively. Ports 502_Di and 502_D2 are coupled to slave ports 521_Di and 521_D2, respectively, and are configured similarly to port 101 on dock 100 (FIGURES IA, IB and 2), thus enabling a system compatible with port 101 of dock 100 to couple to ports 502_D1 and 502_D2 of respective terminal units 302_D1 and 302_D2. In some embodiments, processing modules 501_Di and 501_D2 are configured to send a signal to a system coupled to respective ports 502_DI and 502_D2 causing the system coupled to ports 502_DI and 502_D2 to function as a peripheral. Expansion ports 503_DI and 503_D2 are coupled to respective slave ports 522_D1 and 522_D2 and comprise a port suitable for coupling an expansion device to expand the capabilities of terminal units 302DI and 302D₂- In the embodiment illustrated in FIGURE 4, docking port 301DI and 301D2 are coupled to slave ports 523DI and 523D₂, respectively.

[0029] In the embodiment illustrated in FIGURE 4, terminal units 302_D1 and

302_D2 are configured without user-modifiable, persistent memory (e.g., user-modifiable nonvolatile memory). The lack of user-modifiable, persistent memory reduces the risk of virus infection, the need for software updates, and the likelihood of data compromise in the event that terminal unit 302_D1 and/or 302_D2 is lost or stolen. In the embodiment illustrated in FIGURE 4, terminal units 302_D1 and 302_D2 therefore rely solely on persistent memory in a peripheral system for permanent storage, software programs to execute, etc.

[0030] In FIGURE 4, terminal unit 302_Di is illustrated as coupled to a peripheral system 505 through an intermediate device 504, which in turn is coupled to docking port 301_D1. Peripheral system 505 comprises persistent memory 506, which is accessed and controlled by processing module 501_DI. Peripheral system 505 may comprise any system configured to couple to docking port 301_DI and provide processing module 501_DI with control of persistent memory 506. In some embodiments, intermediate device 504 comprises cable 310A (FIGURE 2). In some embodiments, intermediate system 504 comprises dock 100 (FIGURES IA, IB and 2). In FIGURE 4, cell phone 30O_A2 (FIGURE 3) is coupled to port 502_D2 of terminal unit 302_D2. Since cell phone 30OA₂ is configured to function as a peripheral, processing module 501_D2 is able to access and control persistent memory 402A2 of cell phone 30OA₂-

[0031] FIGURE 5 is a diagram illustrating embodiments of three reconfigurable network systems 601-603. In the embodiments illustrated in FIGURE 6, reconfigurable network system 601 comprises cell phone 300_AI (FIGURES 2 and 3) coupled to keyboard dock 100_B (FIGURES IA, IB and 2). Reconfigurable network system 602 comprises PDA 300_Bi (FIGURES 2 and 3) coupled to power adapter 310_B (FIGURE 2) and keyboard dock 100_B (FIGURES IA, IB and 2) through network dock 100_A (FIGURES IA, IB and 2) using cables 310_A (FIGURE 2) attached to each of ports 102_A and 103A, respectively, of network dock 100_A- Reconfigurable network system 603 comprises terminal unit 302_D1 (FIGURES 2 and 3) coupled to power adapter 310_B (FIGURE 2), keyboard dock 100_B (FIGURES IA, IB and 2) and cell phone 300_A2 (FIGURES 2 and 3) through network dock 100_A (FIGURES IA, IB and 2) and cables 310_A (FIGURE 2) attached to each of ports 102_A and 103_A, respectively, of network dock 100_A- Reconfigurable network systems 602 and 603 are each coupled to external networks 604A and 604B, respectively, through network interface dock-specific functions 118_A of network dock 100_A-

[0032] In reconfigurable network systems 601-603, cell phone 300_AI, PDA

300_BI, and terminal unit 302_D1 function as hosts, whereas network dock 100_A, keyboard dock 100_B and cell phone 300_A2 function as peripherals. However, referring to network system 603, for example, it should be understood that if keyboard dock 100_B is decoupled from external port 103_A of network dock 100_A, controller 104 (FIGURES IA and IB) in keyboard dock 100_B will change configuration to enable cell phone 300_A2 to function as a host system. Further, referring to network system 603, for example, if power adapter 310_B is decoupled from external port 102_A of network dock 100_A, and keyboard dock 100_B is moved from external port 103_A to external port 102_A of network dock 100_A, controller 104 (FIGURES IA and IB) in network dock 100_A will change configuration to enable cell phone 300_A2 to function as the host of reconfigurable network system 603. It should further be understood that multiple alternative reconfigurable network configurations are possible using embodiments of components 30.

[0033] FIGURE 6 is a diagram illustrating a method of automatically reconfiguring a network. The method depicted in FIGURE 6 is described with reference to reconfigurable network system 602 of FIGURE 5, although it should be understood that the method of FIGURE 6 may be used with alternative embodiments.

[0034] At block 600, controller 104 (FIGURES IA and IB) of network dock

100_A senses the coupling of a system or device to external port 102_A of network dock 100_A- In this example, external port 102_A is configured as a default host port. At decision block 601, controller 104 determines whether the system or device coupled to external port 102_A comprises a host-capable system. For example, if a terminal unit 300_D is coupled to external port 102_A through an intermediate system, such as another embodiment of dock 100, controller 104 will sense the coupling of a host-capable system to external port 102_A. If, however, as illustrated in FIGURE 5, power adapter 310_B is coupled to external port 102_A, controller 104 will detect an absence of a host-capable system at external port 102_A. If at decision block 701 controller 104 determines that a host-capable device is coupled to external port 102_A, the method proceeds to block 602, where controller 104 maintains the configuration of external port 102_A coupled to master port 110 of communications hub 105 (FIGURES IA and IB). If at decision block 601 controller 104 determines that a host- capable device is absent from external port 102_A, the method proceeds to block 603.

[0035] At block 603, controller 104 changes the coupling of master port 110 from external port 102_A to external port 101_A by decoupling master port 110 from external port 102 A and coupling master port 110 to external port 101 A, thereby enabling PDA 300_BI to function as host. Thus, in this example, external port 102_A is considered as a default location or port for a host system while external port 101_A is considered a secondary location or port for a host system. However, it should be understood that network dock 100_A may be otherwise configured. At block 604, controller 104 couples slave port 111 to external port 102_A.

[0036] Thus, embodiments of reconfigurable network systems 601-603 and components 30 of such reconfigurable network systems 601-603 enable various devices to be coupled and/or daisy-chained together while enabling a user to easily select which of the devices will function as a host system relative to the other coupled devices. Further, embodiments of components 30, such as terminal unit 302_D2, facilitate use of a device with little or no persistent storage while enabling the device to be coupled to and use resources of other devices. It should be understood that in the described method, certain functions may be omitted, accomplished in a sequence different from that depicted in FIGURE 6, or performed simultaneously. Also, it should be understood that the method depicted in FIGURE 6 may be altered to encompass any of the other features or aspects as described elsewhere in the specification. Further, embodiments may be implemented in software and can be adapted to run on different platforms and operating systems. In particular, functions implemented by controller 104, controller 413, and interface module 403, for example, may be provided as an ordered listing of executable instructions that can be embodied in any computer-readable medium for use by or in connection with an instruction execution system, apparatus, or device, such as a computer-based system, processor-containing system, or other system that can fetch the instructions from the instruction execution system, apparatus, or device, and execute the instructions. In the context of this document, a "computer-readable medium" can be any means that can contain, store, communicate, propagate or transport the program for use by or in connection with the instruction execution system, apparatus, or device. The computer-readable medium can be, for example, but is not limited to, an electronic, magnetic, optical, electro-magnetic, infrared, or semi-conductor system, apparatus, device, or propagation medium.

Claims

WHAT IS CLAIMED IS:

1. A reconfigurable network system, comprising: a dock having a plurality of external ports, the dock comprising a controller configured to automatically reconfigure internal couplings of the dock based on which of the plurality of external ports a host-capable system is connected.

2. The system of Claim 1, wherein the controller is configured to reconfigure connectivity of the plurality of ports to a communications hub of the dock based on which of the plurality of external ports the host-capable system is connected.

3. The system of Claim 1, wherein the controller is configured to selectively connect one of the plurality of external ports to a master port of a communications hub in response to the host-capable system connected to the one external port.

4. The system of Claim 1, wherein the controller is configured to automatically decouple one of the plurality of external ports from a master port of a communications hub in response to detecting the host-capable system connected to another one of the plurality of external ports.

5. The system of Claim 1, wherein the controller is configured to detect the host- capable system being coupled to at least one of the plurality of external ports through another dock.

6. The system of Claim 1, wherein the controller is configured to enable a host- capable system connected to one of the plurality of external ports to be controlled as a peripheral system in response to a different host-capable system being connected to another one of the plurality of external ports.

7. The system of Claim 1, wherein the controller is configured to reconfigure internal couplings of the dock based on a user selection of one of the plurality of external ports to enable a system coupled to the selected one external port to act as a host.

8. The system of Claim 1, wherein the controller is configured to, in response to a host-capable system being coupled to each of the plurality of external ports, reconfigure internal couplings of the dock based on a user designation of which of the host-capable systems is to act as a host.

9. A reconfigurable network method, comprising: automatically reconfiguring internal couplings of a dock based on which of a plurality of external ports of the dock a host-capable system is connected.

10. The method of Claim 9, further comprising reconfiguring connectivity of the plurality of the plurality of external ports to a communications hub of the dock based on which of the plurality of external ports the host-capable system is connected.

11. The method of Claim 9, further comprising selectively connecting one of the plurality of external ports to a master port of a communications hub in response to the host- capable system connected to the one external port.

12. The method of Claim 9, further comprising automatically decoupling one of the plurality of external ports from a master port of a communications hub in response to detecting the host-capable system connected to another one of the plurality of external ports.

13. The method of Claim 9, further comprising detecting the host-capable system being coupled to at least one of the plurality of external ports through another dock.

14. The method of Claim 9, further comprising enabling a first host-capable system connected to one of the plurality of external ports to be controlled as a peripheral system in response to a second host-capable system being connected to another one of the plurality of external ports.

15. A reconfigurable network system, comprising: means for automatically reconfiguring internal couplings of a docking means based on which of a plurality of external ports of the docking means a host-capable system is connected.

16. The system of claim 15, further comprising means for reconfiguring connectivity of the plurality of the plurality of external ports to a communications hub of the docking means based on which of the plurality of external ports the host-capable system is connected.

17. The system of Claim 15, further comprising means for selectively connecting one of the plurality of external ports to a master port of a communications hub in response to the host-capable system connected to the one external port.

18. The system of Claim 15, further comprising means for automatically decoupling one of the plurality of external ports from a master port of a communications hub in response to detecting the host-capable system connected to another one of the plurality of external ports.

19. The system of Claim 15, further comprising means for detecting the host- capable system being coupled to at least one of the plurality of external ports through another docking means.