Classifications

• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
  • H04L41/08—Configuration management of networks or network elements
  • H04L41/0803—Configuration setting
  • H04L41/0806—Configuration setting for initial configuration or provisioning, e.g. plug-and-play
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L12/00—Data switching networks
  • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L12/00—Data switching networks
  • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
  • H04L12/2803—Home automation networks
  • H04L12/2805—Home Audio Video Interoperability [HAVI] networks

Definitions

• the invention relates to a method and system for networking information processing sub-systems.
• the invention relates especially to configuring a network of PC's in the home environment.
• Jini is a Java-based software technology that assists in networking PC's and peripherals.
• a Jini-enabled device When plugged into a network, a Jini-enabled device will broadcast its presence. Network clients that are ready to use that device can request the necessary software from the device, bypassing a server or a network administrator.
• This architecture builds on top of an existing network. The network itself is assumed to have been configured in advance.
• the first problem relating to the detection has been solved by plug-and-play technology.
• the Windows95 OS allows many Ethernet cards / token ring cards to work automatically upon insertion in the system.
• the second problem relating to address assignment is currently being worked on in the industry.
• a known solution is a configuration management protocol, an example of which is the DHCP protocol (Dynamic Host Configuration Protocol) that lets network administrators manage centrally and automate the assignment of Internet Protocol (IP) addresses in an organization's network.
• IP Internet Protocol
• An object of the invention is to provide a solution for the third problem, that is, for the implementing of a sharing protocol.
• the invention provides a method of enabling sharing a first resource or a first service, which is registered with a first information processing sub-system (e.g., a first PC), with a second information processing sub-system (e.g., a second PC).
• the method comprises enabling the second sub-system to be informed about access to the first sub-system and enabling registering with the second sub-system of a first interface to the first sub-system and addressable through the second sub-system.
• the method further comprises enabling sharing with the first sub-system, a second resource or a second service registered with the second sub-system, enabling the first sub-system to be informed about access to the second sub-system; and enabling registering with the first sub-system of a second interface to the second sub-system and addressable through the first sub-system.
• Each of the sub-systems sets up as an interface proxy client for access to the other sub-system and a proxy server for handling requests from the other sub-systems proxy server.
• the registering of services and resources of one PC at the other one through the proxy clients thus enables automatic configuration of a network in order to share resources.
• the registering hides the idea of whether a resource or a service is local or is residing at another apparatus.
• the invention uses the registering as a tool for autoconfiguration of a network.
• Jini focuses on the process of adding a device to the network and broadcasting information about the device to other machines. In this way, Jini provides a "Lookup" service that allows applications on other machines to use the newly added device.
• the approach of Jini assumes the network and operating system have already been configured so that each computer already knows about other computers. Jini's functionality occurs at a layer above the network. It does not, for example, solve the problems of automatic configuration of the network upon connection, disconnection, or reconnection. It assumes that the network is up or down, independent of Jini. Jini leverages the services provided by the network to implement its services. In other words, the invention uses the registering as a tool for autoconfiguration.
• Fig.l is a diagram of the configuration of a system of the invention.
• Figs.2-7 are diagrams illustrating various steps in the autoconfiguration process and during operational use.
• Fig.l is a block diagram with the main components of an operational system 100 in the invention.
• System 100 comprises a first PC 102 and a second PC 104 coupled via a bus 106.
• Bus 106 may be a wired bus or a wireless bus or a combination thereof.
• PC 102 has resources and provides services.
• PC 102 has a hard drive 108, an email capability 110, a web browser 112, a printer 114, etc.
• PC 104 has resources and services, such as a hard drive 116, a wordprocessing service 118, a graphics program 120, a printer 122, etc.
• the terms "resource” and “service” are used interchangeably below for the sake of brevity.
• PC 102 has a registry 124 for registering interfaces to resources and services
• PC 104 has a registry 126 for registering interfaces to resources and services 116- 122 local to PC 104.
• PC 102 further comprises the following entities that are concurrent and may be threads or processes: a broadcaster 128, a port listener 130 and a broadcast listener 132.
• PC 104 has a broadcaster 134, a port listener 136 and a broadcast listener 138.
• PC 102 further comprises a proxy client 142 and a proxy server 144.
• PC 104 has a proxy client 140 and a proxy server 144.
• Proxy client 142 communicates with proxy server 146, and proxy client 140 communicates with proxy server 144.
• Fig.2 is a diagram of the initial configuration of system 100 when PC's 102 and 104 have been functionally connected to bus 106.
• broadcasters 128 sends out on bus 106 a network address for PC 102, say "X”, and a port number, say "x", on an established channel.
• broadcaster 134 sends out a broadcast on bus 106 with a network address for PC 104, "Y", and a port number "y” on another established channel.
• Broadcast listener 138 of PC 104 receives the message broadcasted by PC 102.
• Broadcast listener 132 of PC 102 receives the message broadcasted by PC 104.
• Fig.3 illustrates a next step of the autoconfiguration process.
• broadcast listener 132 of PC 102 Having received the broadcast message from PC 104, broadcast listener 132 of PC 102 generates a proxy client 142. Proxy client 142 thereupon establishes a connection with port listener 136 of PC 104 at port "y". Similarly, broadcast listener 138 of PC 104 generates proxy client 140 that establishes a connection with port listener 130 at port "x”.
• Fig.4 shows a further step in the autoconfiguration process.
• Port listener 130 starts up a proxy server 144 to handle requests from remote client 140.
• Proxy server 144 sends information about resources 108-114, e.g., as contained in registry 124, to proxy client 140.
• Proxy client 140 registers this information with registry 126.
• port listener 136 starts up a proxy server 146 to handle requests from remote client 142.
• Proxy server 146 sends information about resources 116-122 to proxy client 142, which thereupon registers this with registry 124.
• Fig.5 shows the step wherein proxy client 142 registers with registry 124 as a local service for each resource or service available in registry 126, and wherein proxy client 140 registers with registry 126 for each resource or service available in registry 124.
• PC 102 has now copied its registry 124 specifying the addresses of its local resources and services to PC 104, where the copy is added to registry 126.
• PC 104 has copied its registry 126 to PC 102 where it gets added to registry 124. Both PC's 102 and 104 have now been registered with each other.
• a third PC 148 is connected to bus 106, a process similar as the one discussed above occurs automatically.
• Registries 124 and 126 thus hide the idea of whether a resource or a service is local or is residing at another apparatus.
• Each of the addresses in registry 124 is unique throughout registry 124.
• each of the addresses in registry 126 is unique throughout registry 126.
• a user working at PC 102 and requesting a local resource or service i.e., one of resources or services 108-114 has the request passed on directly to the resource or service requested indicated by the corresponding address in registry 124.
• the user requests a remote service or remote resource, i.e., one of resources or services 116-122 that is local to remote PC 104, the request is forwarded to proxy client 142 and processed by proxy server 146 as discussed below with reference to Fig.7.
• Fig.6 gives diagrams 600 and 602 as an example of the registering of proxy client 142 with registry 124.
• Diagram 600 represents initial registry 126 with a list of local resources and services available at PC 104 and their respective local addresses.
• Diagram 602 represents registry 124 after client 142 has registered with it.
• Registry 124 initially comprises the list of resources and services 108-114 with local addresses #1 to #K.
• registry 124 has an entry for PC 104 as proxy device at address #Q.
• Remote resources and services 116-122 now have addresses dependent on address #Q.
• Fig.7 illustrates this address-based operation involving proxy client 142 and proxy server 146.
• a software application 702 running on PC 102 generates a request for resource 118 at remote PC 104.
• a reference to resource 118 has been added to registry 124 as discussed above. The reference has a pointer (arrow 704) to proxy client 142.
• Proxy client 142 on PC 102 contacts (arrow 706) proxy server 146 on remote PC 104.
• Proxy server 146 has an address, or: handle, (arrow 708) to resource 118 via local registry 126. Results of the processing by resource 118 are routed back (arrow 708) via proxy server 146 and proxy client 142 (arrow 706) to application 702 (arrow 712).
• Proxy client 142 and proxy server 146 serve as a pipe.
• a request or message generated at PC 102 has an address for one of local resources or services 108-114, the message gets passed on directly to the service or device driver (not shown) of the relevant resource.
• the message is sent (702) to proxy client 142, which in turn passes on (704) the request to proxy server 146 at the dedicated port.
• Proxy server 146 processes the request and routes it (706) to the relevant one of resources 116-122 via registry 126.
• the result of the request being processed is then communicated (708) from proxy server 146 to proxy client 142 from which the result is routed to, e.g., a local application at PC 102 or a display driver (not shown) local to PC 102.
• the address of remote clients 142 and 140 can be removed from local registries 124 and 126, respectively.
• the autoconfiguration means gets used when stand-alone PC 102 or 104 is connected to a network or when stand-alone PC's 102 and 104 are connected together.
• the software is provided to users, for example, as a program on a diskette or is made downloadable from the web. An implementation of this autoconfiguration system can be demonstrated using a java-based system.
• two stand-alone PC's have Java, a network card, and a TCP/IP stack installed on their machines.
• a respective random LP number is used for each respective one of the machines.
• the idea here is that the LP address and standard TCP/IP settings have not been pre-configured by the user.
• a unique id is generated — this could be a random number of sufficient complexity so that a collision is statistically improbable (a working example of this is
• GUID Global Unique LDentifier
• a runtime executable is started that spawns off three objects: a Broadcaster, a Broadcast Listener, and a Port Listener - each as a Java thread.
• the Broadcast Listener could use a Java multicast socket to subscribe to a multicast.
• the Broadcaster could also use a Java multicast socket to send information to a multicast group.
• the Port Listener could be implemented as a Java ServerSocket.
• the Broadcast Listener receives a message and the LP address is the same as its own LP address and the ULD is not the same, it brings down each of its Proxy Servers, randomly generates a new LP address, and automatically reconfigures itself. In this way, the LP addresses of each machine are eventually ensured to be unique.
• the Broadcast Listener receives a message and the IP address is the same as its own LP address and the ULD is the same, then the message is ignored since the message was generated by its own Broadcaster.
• a new Java thread is generated: a Proxy Client which connects to the Port Listener on the other machine.
• the broadcast message contains port and LP address for the Proxy Client to connect as a Java Socket.
• the Port Listener through the java accept() method spawns a new Java thread to handle this request: a Proxy Server. Resource information flows from the Proxy Server to the Proxy Client back to the registry.
• the registry can be organized as a hash table, where each resource is identifiable by a unique address generated when the resource or service is added to the registry.
• the Proxy Server sends information about the current registry.
• the Proxy Client then adds this information to the registry local to the Proxy Client.
• the important idea is that a handle gets associated with the Proxy Client in the registry, so that the process or thread local to the new address is the Proxy Client rather than a local process or thread.
• control information is passed to the Proxy Client which passes this same information to the Proxy Server which then passes this information to the resource or service on the other machine.
• each of these services consists of a java object that receives ByteData either from another object using the service or resource or from the Proxy Server. In this way, both the client application using the service and the service itself appear local on the same machine.
• the important idea behind the registry used is that it associates services/resources with addresses and it takes packets of data which it transmits to the appropriate service or resource based on this address.
• this data is passed using a java data input streams and data output streams.
• the address of remote clients 142 and 140 can be removed from local registries 124 and 126, respectively.
• a heartbeat protocol between the PC's ensures that each is kept aware of the other until the heartbeat of one of the PC's disappears.
• a timer expires and automatically triggers the procedure to disable the registry's entry to the relevant client.

Landscapes

• Engineering & Computer Science (AREA)
• Computer Networks & Wireless Communication (AREA)
• Signal Processing (AREA)
• Multimedia (AREA)
• Automation & Control Theory (AREA)
• Computer And Data Communications (AREA)
• Small-Scale Networks (AREA)
• Data Exchanges In Wide-Area Networks (AREA)

Priority Applications (5)

Applications Claiming Priority (2)

Publications (1)

Family

ID=22459532

Family Applications (1)

Country Status (9)

Cited By (2)

Families Citing this family (58)

Citations (2)

Family Cites Families (5)

• 1998
  • 1998-08-13 US US09/133,622 patent/US6314459B1/en not_active Expired - Fee Related
• 1999
  • 1999-08-04 DE DE69933852T patent/DE69933852T2/de not_active Expired - Fee Related
  • 1999-08-04 EP EP99941549A patent/EP1046260B1/en not_active Expired - Lifetime
  • 1999-08-04 WO PCT/EP1999/005767 patent/WO2000010295A1/en not_active Ceased
  • 1999-08-04 CN CNB998018260A patent/CN1201524C/zh not_active Expired - Fee Related
  • 1999-08-04 IL IL13556199A patent/IL135561A/en not_active IP Right Cessation
  • 1999-08-04 KR KR1020007004010A patent/KR100699701B1/ko not_active Expired - Fee Related
  • 1999-08-04 ES ES99941549T patent/ES2276527T3/es not_active Expired - Lifetime
  • 1999-08-04 JP JP2000565644A patent/JP2002523925A/ja active Pending

Patent Citations (2)

Non-Patent Citations (1)

Also Published As

Similar Documents

Legal Events