CA2246133C - Method and devices for providing network services from several servers - Google Patents
Method and devices for providing network services from several servers Download PDFInfo
- Publication number
- CA2246133C CA2246133C CA002246133A CA2246133A CA2246133C CA 2246133 C CA2246133 C CA 2246133C CA 002246133 A CA002246133 A CA 002246133A CA 2246133 A CA2246133 A CA 2246133A CA 2246133 C CA2246133 C CA 2246133C
- Authority
- CA
- Canada
- Prior art keywords
- network
- server
- subscriber
- computing device
- call notification
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Expired - Fee Related
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
- H04L67/1004—Server selection for load balancing
- H04L67/1006—Server selection for load balancing with static server selection, e.g. the same server being selected for a specific client
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
- H04L67/1027—Persistence of sessions during load balancing
Abstract
Methods and devices for obtaining a network service at a network interconnected computing device (18) from one of plurality of network servers (16a, 16b, 16c), are disclosed. The computing device (18) contacts a first network server (16a) having a first network address, using the network address over the network (10). The device (18) provides this server (16a) with an identifier of the computing device. This identifier may, for example, be a persistent state object or "cookie". The server (16a), in response, queries a database and determines a second network address of a server (16a, 16b or 16c) used to provide a service to the computing device, based on the identifier. This address is provided to the computing device (18) . The network addresses of servers (16a, 16b, 16) may be uniform resource locators. The computing device (18), in turn, contacts the server identified by the second network address and obtains the network service. The service, may for example, include receiving an indicator at the computing device of an incoming telephone call on a telephone network.
Description
METHOD AND DEVICES FOR PROVIDING NETWORK SERVICES FROM
SEVERAL SERVERS
FIELD OF THE INVENTION:
The present invention relates to networked computing devices, and more particularly to a method and devices for offering network based services from multiple servers, thereby allowing for the scalable provision of services.
BACKGROUND OF THE INVENTION:
Packet switched computer networks have become widely used. The best known and most widely used example of such a network is the public internet.
Because of its popularity, the internet has become a desirable vehicle to provide a variety of new services to subscribers. Such services include network commerce, network telephony services, messaging services, video and audio on demand services, and the like. Many of these services appeal to large segments of the population and attract thousands of subscribers.
In order to reduce the cost and simplify the provision of such services, the architecture of devices hosting these services should be scalable. That is, a particular service should preferably be provided by multiple servers, instead of a single server.
An example network service is the Internet Call Waiting ("ICW") service, as disclosed in Canadian Patent Application No. 2,263,264. Known ICW servers are interconnected with the internet and a telephone network such as the public switched telephone network ("PSTN"). This makes the scalability of such servers difficult.
Solutions enabling scalability of servers that rely only on an internet connection are known. Several such solutions distribute internet protocol ("IP") connection requests across several servers. For example, a unique unified resource locator ("URL") may be mapped by a server providing domain name service ("DNS") to several different IP
addresses, each IP address corresponding to a different physical server. Other known solutions distribute IP
requests for a single IP address to multiple servers. A
combination of these solutions can result in a network architecture that is scalable and that accommodates many different services.
On the other hand, services that rely on both PSTN and internet connectivity are further constrained by PSTN
connectivity of a hosting server. Typically, such a server accommodates from one to a few hundred PSTN circuits. In some cases, a specific assigned server must be used for a given subscriber of the service. More sophisticated arrangements allow any server in a group to be used for any subscriber.
This is not always possible or may require a costly front-end PSTN switch or other costly hardware and software.
Alternatively, each subscriber may be required to configure software to contact an assigned server. However, this complicates subscriber configuration requirements and further limits the ability of using several servers to provide service to a single subscriber.
Accordingly, improved methods and devices that allow a network subscriber service to be provided by one of many servers are desirable.
SUMMARY OF THE INVENTION:
In accordance with the present invention, there is provided a method of providing incoming call notification of telephone calls received over a telephone network, to a subscriber at a computing device associated with the subscriber by way of a packet switched data network, the method comprising: operating a plurality of incoming call notification servers, each interconnected with the telephone network and the packet switched data network, each of the incoming call notification servers operable to provide the incoming call notification to specific subscribers;
receiving from the computing device associated with the subscriber at a first network interconnected server, over the packet switched data network, a request to contact a server providing the incoming call notification; receiving over the packet switched data network from the computing device associated with the subscriber at the first network server, an identifier of the computing device associated with the subscriber; redirecting the request to a specific one of the plurality of call notification servers interconnected with the packet switched data network capable of providing the subscriber with the incoming call notification service, based on the identifier.
According to another aspect of the invention, there is provided a method of providing incoming call notification of telephone calls received over a telephone network, to a subscriber at a computing device associated with the subscriber by way of a packet switched data network, the method comprising: receiving from the computing device associated with the subscriber at a first network interconnected server, over the packet switched data network, a request to contact a server providing the incoming call notification; receiving over the packet switched data network from the computing device associated with the subscriber at the first network server, an identifier of the computing device associated with the subscriber; based on the identifier, redirecting the request to a specific one of a plurality of call notification servers interconnected with the packet switched data network and the telephone network and capable of providing the subscriber with the incoming call notification.
According to a further aspect of the invention, there is provided a server interconnected with a packet switched data network, the server comprising a processor and computer readable memory storing program instruction and data adapting the server to: receive from a computing device associated with a subscriber at a first network interconnected server, over the packet switched data network, a request to contact a server providing incoming call notifications over the packet switched data network of telephone calls received over a telephone network, for the subscriber; redirect the request to a specific one of a plurality of call notification servers interconnected with the packet switched data network and the telephone network, each of the incoming call notification servers for providing incoming call notification of telephone calls received over a telephone network to specific subscribers at an associated computing device by way of a packet switched data network, the specific one of the incoming call notification servers capable of providing the subscriber with the incoming call notification, based on the identifier.
Advantageously, subscribers to the service remain unaware of the actual number of servers providing the service and of the particular server providing the service.
BRIEF DESCRIPTION OF THE DRAWING:
In figures which illustrate, by way of example, embodiments of the present invention, FIG. 1 illustrates a plurality of interconnected computing devices, including a plurality of servers and an end-user computing device, exemplary of embodiments of the present invention;
FIG. 2 is a block diagram of an architecture of a server of FIG. 1;
FIG. 3 illustrates an organization of memory of the server of FIG. 2;
FIG. 4 illustrates an organization of a database at the server of FIG.2;
FIG. 5 illustrates an architecture of an end-user computing device, illustrated in FIG. 1;
FIG. 6 illustrates an organization of memory of the device of FIG. 5; and FIGS. 7 and 8 illustrate steps in methods exemplary of embodiments of the present invention.
DETAILED DESCRIPTION:
FIG. 1 illustrates a plurality of computing devices 14, 16a, 16b, 16c, and 18 interconnected to each other by way of network 10. Preferably, network 10 is a packet switched data network, using the internet protocol ("IP"), as detailed in RFC 791, to exchange data in the form of packets between interconnected computing devices, such as computing devices 14, 16a, 16b and 16c, and 18. Network 10 may, for example, be the public internet, a private intranet, or any other suitable local or wide area network.
In the illustrated embodiment, device 18 is an end-user work station; device 14 is a network server providing the work station; device 14 is a network server providing the known internet domain name service ("DNS") as detailed in RFCs 2136 and 2137; and devices 16a, 16b and 16c are other internet servers exemplary of the present invention. Servers 16a, 16b and 16c may be hyper-text-transfer protocol ("HTTP") servers offering internet commerce, or database services;
internet message servers, such as the ICW server detailed more particularly in Canadian Patent Application No.
2,263,264; directory servers; or the like.
Devices 14, 16a, 16b, 16c and 18 may be interconnected with network 10 in any of a number of ways. For example, device 14 may be directly interconnected with a network router using an Ethernet or other physical interface. Device 18 may be intermittently connected to network 10 through the public switched telephone network (the "PSTN" - not illustrated). Similarly, devices 16a, 16b and 16c could be connected to network 10, by an asynchronous transfer mode ("ATM") switch (not illustrated); an integrated standards digital network ("ISDN") (not illustrated); a local area network (not illustrated); or any other suitable physical connection to network 10.
The architecture of each of servers 16a, 16b, and 16c (generically referred to as server 16) is substantially similar and is illustrated in FIG. 2. Each server 16 is typically a conventional server suitable computing device.
Server 16, may for example be a SUN SparcTM server; a Microsoft NTTM Server; a Hewlett Packard HPUXTM server, or the like. Each server 16 comprises a processor 40, in communication with persistent storage memory 42, and network interface 44. As well, server 16 may optionally comprise a display 48 and input device 50, such as a keyboard, mouse or the like.
Processor 40 comprises a conventional central processing unit, and may for example comprise a microprocessor in the INTELT" x86 family. Of course, processor 40 could be a RISC
based CPU; a MotorolaTM CPU, or any other suitable processor known to those skilled in the art. Memory 42 preferably comprises a suitable combination of random access memory, read-only-memory, and disk storage memory used by processor 40 to store and execute programs adapting server 16 to act as a network server as detailed below. Memory 42 may include a device capable of reading and writing data to or from a computer readable medium 45 used to store software and data to be loaded into memory 42. Network interface 44 comprises any interface suitable to physically link server 16 to network 10. Interface 44, may for example be an Ethernet, ATM or ISDN interface or even a telephone modem that may be used to pass data, in the form of packets from and to the remainder of network 10. Servers 16 may comprise further hardware depending on the particular service offered. For example, in the event server 16 acts as a message server each will typically be equipped with an additional interface for connection with another network such as the PSTN, as for example detailed in U.S. Patent No. 6,393,467 entitled "NETWORK INTERCONNECTED COMPUTING DEVICE, SERVER AND
NOTIFICATION METHOD", naming Carl Potvin as inventor.
An exemplary organization of memory 42 of server 16 is illustrated in FIG. 3. Stored within memory 42 are computer software programs and data that are loaded into working memory of server 16 to permit server 16 to be operable as a network server. As illustrated, memory 42 stores operating system software 52; application software 54; and data 56.
Operating system software 52 may, for example, be Microsoft NT'm Server operating system software, UNIX operating system software, or the like. Application software 54 includes network interface software 58, that typically includes an internet protocol suite allowing communication of server 16 and thus operating system 52 with network 10, through physical network interface 44 (FIG. 2). Application software 54 further includes an HTTP server or daemon 60; a server resolution application 62; common gateway interface ("CGI") programs 65; and a messaging application 67, exemplary of the present invention.
HTTP server 60 may for example be an ApacheTM Web Server or a Microsoft Internet Information ServerT"1 application. CGI
SEVERAL SERVERS
FIELD OF THE INVENTION:
The present invention relates to networked computing devices, and more particularly to a method and devices for offering network based services from multiple servers, thereby allowing for the scalable provision of services.
BACKGROUND OF THE INVENTION:
Packet switched computer networks have become widely used. The best known and most widely used example of such a network is the public internet.
Because of its popularity, the internet has become a desirable vehicle to provide a variety of new services to subscribers. Such services include network commerce, network telephony services, messaging services, video and audio on demand services, and the like. Many of these services appeal to large segments of the population and attract thousands of subscribers.
In order to reduce the cost and simplify the provision of such services, the architecture of devices hosting these services should be scalable. That is, a particular service should preferably be provided by multiple servers, instead of a single server.
An example network service is the Internet Call Waiting ("ICW") service, as disclosed in Canadian Patent Application No. 2,263,264. Known ICW servers are interconnected with the internet and a telephone network such as the public switched telephone network ("PSTN"). This makes the scalability of such servers difficult.
Solutions enabling scalability of servers that rely only on an internet connection are known. Several such solutions distribute internet protocol ("IP") connection requests across several servers. For example, a unique unified resource locator ("URL") may be mapped by a server providing domain name service ("DNS") to several different IP
addresses, each IP address corresponding to a different physical server. Other known solutions distribute IP
requests for a single IP address to multiple servers. A
combination of these solutions can result in a network architecture that is scalable and that accommodates many different services.
On the other hand, services that rely on both PSTN and internet connectivity are further constrained by PSTN
connectivity of a hosting server. Typically, such a server accommodates from one to a few hundred PSTN circuits. In some cases, a specific assigned server must be used for a given subscriber of the service. More sophisticated arrangements allow any server in a group to be used for any subscriber.
This is not always possible or may require a costly front-end PSTN switch or other costly hardware and software.
Alternatively, each subscriber may be required to configure software to contact an assigned server. However, this complicates subscriber configuration requirements and further limits the ability of using several servers to provide service to a single subscriber.
Accordingly, improved methods and devices that allow a network subscriber service to be provided by one of many servers are desirable.
SUMMARY OF THE INVENTION:
In accordance with the present invention, there is provided a method of providing incoming call notification of telephone calls received over a telephone network, to a subscriber at a computing device associated with the subscriber by way of a packet switched data network, the method comprising: operating a plurality of incoming call notification servers, each interconnected with the telephone network and the packet switched data network, each of the incoming call notification servers operable to provide the incoming call notification to specific subscribers;
receiving from the computing device associated with the subscriber at a first network interconnected server, over the packet switched data network, a request to contact a server providing the incoming call notification; receiving over the packet switched data network from the computing device associated with the subscriber at the first network server, an identifier of the computing device associated with the subscriber; redirecting the request to a specific one of the plurality of call notification servers interconnected with the packet switched data network capable of providing the subscriber with the incoming call notification service, based on the identifier.
According to another aspect of the invention, there is provided a method of providing incoming call notification of telephone calls received over a telephone network, to a subscriber at a computing device associated with the subscriber by way of a packet switched data network, the method comprising: receiving from the computing device associated with the subscriber at a first network interconnected server, over the packet switched data network, a request to contact a server providing the incoming call notification; receiving over the packet switched data network from the computing device associated with the subscriber at the first network server, an identifier of the computing device associated with the subscriber; based on the identifier, redirecting the request to a specific one of a plurality of call notification servers interconnected with the packet switched data network and the telephone network and capable of providing the subscriber with the incoming call notification.
According to a further aspect of the invention, there is provided a server interconnected with a packet switched data network, the server comprising a processor and computer readable memory storing program instruction and data adapting the server to: receive from a computing device associated with a subscriber at a first network interconnected server, over the packet switched data network, a request to contact a server providing incoming call notifications over the packet switched data network of telephone calls received over a telephone network, for the subscriber; redirect the request to a specific one of a plurality of call notification servers interconnected with the packet switched data network and the telephone network, each of the incoming call notification servers for providing incoming call notification of telephone calls received over a telephone network to specific subscribers at an associated computing device by way of a packet switched data network, the specific one of the incoming call notification servers capable of providing the subscriber with the incoming call notification, based on the identifier.
Advantageously, subscribers to the service remain unaware of the actual number of servers providing the service and of the particular server providing the service.
BRIEF DESCRIPTION OF THE DRAWING:
In figures which illustrate, by way of example, embodiments of the present invention, FIG. 1 illustrates a plurality of interconnected computing devices, including a plurality of servers and an end-user computing device, exemplary of embodiments of the present invention;
FIG. 2 is a block diagram of an architecture of a server of FIG. 1;
FIG. 3 illustrates an organization of memory of the server of FIG. 2;
FIG. 4 illustrates an organization of a database at the server of FIG.2;
FIG. 5 illustrates an architecture of an end-user computing device, illustrated in FIG. 1;
FIG. 6 illustrates an organization of memory of the device of FIG. 5; and FIGS. 7 and 8 illustrate steps in methods exemplary of embodiments of the present invention.
DETAILED DESCRIPTION:
FIG. 1 illustrates a plurality of computing devices 14, 16a, 16b, 16c, and 18 interconnected to each other by way of network 10. Preferably, network 10 is a packet switched data network, using the internet protocol ("IP"), as detailed in RFC 791, to exchange data in the form of packets between interconnected computing devices, such as computing devices 14, 16a, 16b and 16c, and 18. Network 10 may, for example, be the public internet, a private intranet, or any other suitable local or wide area network.
In the illustrated embodiment, device 18 is an end-user work station; device 14 is a network server providing the work station; device 14 is a network server providing the known internet domain name service ("DNS") as detailed in RFCs 2136 and 2137; and devices 16a, 16b and 16c are other internet servers exemplary of the present invention. Servers 16a, 16b and 16c may be hyper-text-transfer protocol ("HTTP") servers offering internet commerce, or database services;
internet message servers, such as the ICW server detailed more particularly in Canadian Patent Application No.
2,263,264; directory servers; or the like.
Devices 14, 16a, 16b, 16c and 18 may be interconnected with network 10 in any of a number of ways. For example, device 14 may be directly interconnected with a network router using an Ethernet or other physical interface. Device 18 may be intermittently connected to network 10 through the public switched telephone network (the "PSTN" - not illustrated). Similarly, devices 16a, 16b and 16c could be connected to network 10, by an asynchronous transfer mode ("ATM") switch (not illustrated); an integrated standards digital network ("ISDN") (not illustrated); a local area network (not illustrated); or any other suitable physical connection to network 10.
The architecture of each of servers 16a, 16b, and 16c (generically referred to as server 16) is substantially similar and is illustrated in FIG. 2. Each server 16 is typically a conventional server suitable computing device.
Server 16, may for example be a SUN SparcTM server; a Microsoft NTTM Server; a Hewlett Packard HPUXTM server, or the like. Each server 16 comprises a processor 40, in communication with persistent storage memory 42, and network interface 44. As well, server 16 may optionally comprise a display 48 and input device 50, such as a keyboard, mouse or the like.
Processor 40 comprises a conventional central processing unit, and may for example comprise a microprocessor in the INTELT" x86 family. Of course, processor 40 could be a RISC
based CPU; a MotorolaTM CPU, or any other suitable processor known to those skilled in the art. Memory 42 preferably comprises a suitable combination of random access memory, read-only-memory, and disk storage memory used by processor 40 to store and execute programs adapting server 16 to act as a network server as detailed below. Memory 42 may include a device capable of reading and writing data to or from a computer readable medium 45 used to store software and data to be loaded into memory 42. Network interface 44 comprises any interface suitable to physically link server 16 to network 10. Interface 44, may for example be an Ethernet, ATM or ISDN interface or even a telephone modem that may be used to pass data, in the form of packets from and to the remainder of network 10. Servers 16 may comprise further hardware depending on the particular service offered. For example, in the event server 16 acts as a message server each will typically be equipped with an additional interface for connection with another network such as the PSTN, as for example detailed in U.S. Patent No. 6,393,467 entitled "NETWORK INTERCONNECTED COMPUTING DEVICE, SERVER AND
NOTIFICATION METHOD", naming Carl Potvin as inventor.
An exemplary organization of memory 42 of server 16 is illustrated in FIG. 3. Stored within memory 42 are computer software programs and data that are loaded into working memory of server 16 to permit server 16 to be operable as a network server. As illustrated, memory 42 stores operating system software 52; application software 54; and data 56.
Operating system software 52 may, for example, be Microsoft NT'm Server operating system software, UNIX operating system software, or the like. Application software 54 includes network interface software 58, that typically includes an internet protocol suite allowing communication of server 16 and thus operating system 52 with network 10, through physical network interface 44 (FIG. 2). Application software 54 further includes an HTTP server or daemon 60; a server resolution application 62; common gateway interface ("CGI") programs 65; and a messaging application 67, exemplary of the present invention.
HTTP server 60 may for example be an ApacheTM Web Server or a Microsoft Internet Information ServerT"1 application. CGI
programs 65 typically interface HTTP server application 60 with other data and applications at server 16. CGI programs 65 may be compiled or interpreted programs, and may therefore include a suitable interpreter such as a Perl interpreter, or the like. Messaging application 67 may provide subscribers with a subscribed-to service, such as the ICW service, notifying subscribers of events, including for example, an indicator of an incoming telephone call at a telephone network, as detailed below.
Preferably, and in addition, forming part of application software 54 is a database application or engine 64, such as, for example, a structured query language ("SQL") database engine capable of retrieving, updating, deleting and otherwise operating on records stored within a database 68.
Database 68 stores records representative of subscribers served by servers 16 in accordance with the present invention. Other applications 66 and data 70 may also be stored within memory 42. As will be appreciated application software 54 may be formed by standard programming techniques known to those skilled in the art.
FIG. 4 illustrates an exemplary organization of data within database 68. As illustrated database 68 contains a plurality of records 72a, 72b and so on (collectively and individually 72). Each record is typically associated with a single subscriber and preferably contains at least one field 74 containing data identifying the subscriber possibly by name; one field 76 containing a further subscriber identifier, typically including a telephone dial number associated with the subscriber; a field 78 containing a status indicator indicating whether or not a subscriber has initiated a network session and "registered" with server 16;
a field 82 containing a session IP address, identifying the subscriber's current IP address; and field 84 containing the URL of a server adapted to provide the subscriber a network service. As will be appreciated, each record 72 could contain many other fields. As well, database 68 has been illustrated as a relational database, but could easily take another form such as an object oriented database.
Preferably, and in addition, forming part of application software 54 is a database application or engine 64, such as, for example, a structured query language ("SQL") database engine capable of retrieving, updating, deleting and otherwise operating on records stored within a database 68.
Database 68 stores records representative of subscribers served by servers 16 in accordance with the present invention. Other applications 66 and data 70 may also be stored within memory 42. As will be appreciated application software 54 may be formed by standard programming techniques known to those skilled in the art.
FIG. 4 illustrates an exemplary organization of data within database 68. As illustrated database 68 contains a plurality of records 72a, 72b and so on (collectively and individually 72). Each record is typically associated with a single subscriber and preferably contains at least one field 74 containing data identifying the subscriber possibly by name; one field 76 containing a further subscriber identifier, typically including a telephone dial number associated with the subscriber; a field 78 containing a status indicator indicating whether or not a subscriber has initiated a network session and "registered" with server 16;
a field 82 containing a session IP address, identifying the subscriber's current IP address; and field 84 containing the URL of a server adapted to provide the subscriber a network service. As will be appreciated, each record 72 could contain many other fields. As well, database 68 has been illustrated as a relational database, but could easily take another form such as an object oriented database.
FIG. 5 illustrates, in block diagram, an exemplary architecture of computing device 18 used by an end-user.
Computing device 18 is a typical home or office computer comprising a processor 86, in communication with persistent memory 90, a network interface such as modem 88, a display 92, and typically at least one input device 94. Processor 86 is a typical central processing unit and may be a processor in the INTELTM x86 family. Persistent memory 90 preferably comprises a hard drive, RAM and ROM memories. Modem 88 is typically a conventional telephone modem such as for example a U.S. RoboticsTm Sportster or equivalent modem.
An exemplary organization of persistent storage memory 90 of device 18 is illustrated in FIG. 6. As with memory 42 of server 16, stored within memory 90 are computer software programs and data that are loaded into operating memory of device 18. These permit device 18 to be operable as an end-user work station. As illustrated, memory 90 stores operating system software 96; application software 98; and data 100. Operating system software 96 may, for example, be Microsoft Windows NTTM Workstation operating system software;
Windows 3.1, 95 or 98TM software; Apple System 7.5TM operating system software; or the like. Application software 98 includes network interface software 104, which also typically includes an internet protocol suite allowing communication of computing device 18 over modem 88 (FIG. 5) and thus operating system 96 with network 10 (FIG. 1) . Application software 98 further comprises a modem dialer 106 that operates modem 88 to establish temporary connections to data network 10 by way of the PSTN, as detailed below. Application software 98 may further comprise an internet browser application 102, such as the known Netscape', Mosaic', or Microsoft Internet ExplorerTM
browser applications; and other applications 108 otherwise employed by the end-user and operator of device 18. Again, application software 98 may be formed using conventional programming techniques known to those skilled in the art.
An exemplary organization of server 14 is not explicitly illustrated. Server 14, is preferably also a conventional network capable computer server similar to server 16. Server 14, however, is adapted to act as a domain name server to provide DNS as detailed in RFC 2136, and 2137, and accordingly stores data and executes DNS software to provide this service. Briefly, as understood by those skilled in the art, server 14 acting to provide DNS resolves assigned domain names, identified as part of uniform resource locators ("URL"s). Network interconnected devices dispatch messages containing alphanumeric domain names to server 14 over network 10, and are returned numeric thirty-two bit IP
addresses, based on database entries at server 14. For each domain name, server 14 stores one or more numeric stored IP
addresses. For domain names with multiple stored IP
addresses, addresses to alternate interconnected devices are returned sequentially in order to distribute requests between servers.
As illustrated in FIG. 1, example servers 16a, 16b and 16c are each identified by at least one URL
"www.serverl.com", "www.server2.com", and "www.server3.com".
These URLs are used by device 18 and other devices to request service from servers 16a, 16b and 16c. Additionally, server 16a is identified by a second URL "www.message.com".
As will become apparent, this URL is used by device 18 in order to obtain an identifier of one of the servers 16a, 16b, and 16c that will ultimately provide service to device 18.
With reference to FIG. 1, in operation, an end-user at device 18 "subscribes" with one of servers 16a, 16b and 16c in order to obtain service from one of servers 16a, 16b and 16c. An example subscription or registration process is detailed in U.S. patent no. 6,393,467, entitled "Network Interconnected Computing Device, Server and Notification Method", naming Carl Potvin as inventor. As part of the subscription process, device 18 contacts one of servers 16a, 16b and 16c using that server's well known URL. For illustration purposes, a user "Jane Doe" may contact server 16a identified by its URL "www.message.com". Specifically, browser 102 at device 18 contacts server 16a, and provides service subscription information to device 16a which is stored at server 16a in record 72b by CGI programs 65 in co-operation with HTTP
server application 60, and database engine 64. Subscription information may include the subscriber's name, telephone number, e-mail address, billing information, and service information that is stored in a record 72 of database 68. At the conclusion of the subscription process, server 16a may provide device 18 with a unique identifier that is stored at device 18 as a persistent state object or as a permanent "cookie", as detailed in RFC 2019. Again, server 16a uses HTTP server application 60, CGI programs 65 and database engine 64 to generate and provide the persistent state object.
As will be appreciated, the contents of database 68 may be maintained at any or all of devices 16a, 16b or 16c. Data may be mirrored or distributed among servers 16a, 16b, and 16c using conventional techniques. Servers 16a, 16b and 16c could, for example, maintain identical databases by exchanging database entries using network 10.
As will further be appreciated, communications between device 18 and servers 16a, 16b and 16c may be effected through network interface software using the known transmission control protocol ("TCP/IP") as detailed in RFC 793, or the uniform datagram protocol ("UDP/IP") as detailed in RFC 768, or using any other suitable protocol over network 10.
Each of servers 16a, 16b and 16c is adapted to offer substantially similar services. However, servers 16a, 16b and 16c, in combination, are adapted to provide services to a large number of subscribers, such as a subscriber located at device 18. As will be apparent, it would be desirable to distribute the provision of services among servers 16a, 16b and 16c thereby allowing each of the servers 16a, 16b and 16c to process a fraction of the total number of subscribers. The distribution of subscribers to whom services are provided by servers 16a, 16b and 16c, among these servers, may be accomplished in a number of ways, including, by service type (or combination of services), geographically, by telephone dial number or otherwise. However, ideally the distribution of service among the servers 16a, 16b, and 16c should be transparent to each subscriber. Each subscriber should be able to access the service by a single URL, common to all subscribers. Once the criteria for allocating servers to subscribers has been selected, CGI programs 65 may select an appropriate server and update field 84 of a subscriber record during the subscription process. As should be appreciated, field 76 could be eliminated if some other mapping scheme is used. As will become apparent, in the preferred embodiment, 91436-126 MZ/br the identifier provided to device 18 during the registration process is later used to retrieve the contents of field 84 for a subscriber and direct the device 18 to the allocated one of servers 16a, 16b and 16c.
Specifically, steps 700 and 800 performed by device 18 at a later time in order to obtain service from one of servers 16a, 16b and 16c are illustrated in FIGS. 7 and 8, respectively. As illustrated, after subscription to the service, the subscriber at device 18 establishes an internet connection to network 10 through, for example, the PSTN in step S702. An internet connection is typically established through the PSTN by running or launching dialer application 106 (FIG. 6) at device 18; establishing a PSTN circuit between computing device 18 and an internet service provider ("ISP", not shown); and establishing a data link between modems at the ISP and device 18. This link may be established by a serial link internet protocol ("SLIP") or a point-to-point-protocol ("PPP") IP connection between device 18 and the ISP.
As part of establishing this IP link between computing device 18 and the ISP, the ISP may assign a temporary "session" IP address to device 18. This session IP address now uniquely identifies device 18 on network 10 and allows IP
packets to be directed to computing device 18 during this session. Device 18 may now notify the identified server 16a, that device 18 is "on-line" by querying DNS 14 using a known URL of the service which corresponds to one of server 16a, using, for example, web browser application 102, in step S704. In the example embodiments, server 16a is identified by the URL "www.message.com". Next, device 18, contacts server 16a using the numeric IP address of server 16a and provides an indicator (typically a persistent state object or "cookie" stored at device 18) that device 18 is network interconnected ("on-line"), and optionally the session IP
address of device 18 in step S706, as detailed in U.S. patent no.6,393,467 entitled "NETWORK INTERCONNECTED COMPUTING
DEVICE, SERVER AND NOTIFICATION METHOD" naming Carl Potvin as inventor.
In response, in step S802, server 16a receives the message containing the identifier dispatched in step S704 and uses server resolution application 62 (FIG. 3) to query its database 68 (FIG. 4) to locate a record containing a matching identifier in field 76 in step S804. Server resolution application 62 determines an appropriate server 16a, 16b and 16c that will provide the subscribed service to the subscriber at device 18 from field 84 of the appropriate record. The IP address or URL
including a domain name of the appropriate one of servers 16a, 16b or 16c contained in field 84 is provided to device 18 in step S806 and received in step S708. In the example embodiments, for subscriber "Jane Doe", server 16a returns a URL of "www.server2.com", identifying server 16b. As well, IP
address field 82 and status field 78 may be updated when the subscriber has registered with server 16. Additionally, browser 102 may be provided with a temporary persistent state object or "cookie", stored at device 18 and indicating that device 18 is on-line.
Device 18, upon receiving the message containing the URL
identifying server 16b, contacts DNS server 14 to obtain the numeric IP address of server 16b corresponding to the URL
"www.server2.com" in step S710 and thereafter contacts the identified server 16b in step S712 and provides server 16b with registration information similar to that provided to server 16a, immediately after establishing the IP session in step S702, in step S714. As will be appreciated by those skilled in the art, the URL identifying server 16b may be provided by way of a Java script, or an HTTP redirection tag. This makes contact of server 16b appear seamless to an end-user.
Server 16b is again provided, registration information that is typically provided transparently by device 18, by providing server 16b with a"cookie" containing the identifier of device 18. The identified server 16b may then provide data, and thus the subscribed service, to device 18 by way of the 91436-126 MZ/br device's IP address. Device 18 thus receives a subscribed to service from server 16b, in steps S716.
Of course, if server resolution application 62 determines server 16a should provide the service, registration information need not again be provided by device 18. Instead, information provided in step S706 may be used to provide the subscribed service to device 18. As noted, in the preferred embodiment, server 16a is identified by two URLs: one URL, "www.message.com", is used to initially access the service and obtain an URL of an appropriate server, while another URL, "www.serverl.com , is used to obtain service from server lGa. If server 16a provides the service as well as determines an appropriate server, the use of the second URL could be eliminated.
In the preferred embodiment, each of servers 16a, 16b and 16c provide an ICW service, as more particularly described in Canadian Patent Application No. 2,263,264. For this purpose, each of servers 16a, 16b, and 16c comprises messaging application 67 (FIG. 3) that adapts each server to provide a subscriber with an indication of an incoming PSTN
telephone call by way of network 10. As will be appreciated, as the ICW service will typically be provided to a large number of subscribers, the above described method may be used to contact and obtain ICW service from any of servers 16a, 16b and 16c. Typically, each of servers 16a, 16b, and 16c will be specifically adapted to provide ICW service to subscribers connected to specified central office switches of the PSTN, as identified by the end-users telephone dial number. For each subscriber one of servers 16a, 16b and 16c is provided with an indication of an incoming call by way of the call forward busy feature of the subscriber's central office switch. Typically only a single server is in communication with a subscriber's central office switch and will therefore be adapted to provide the ICW service for that subscriber.
The ICW service, however, is typically identified by a single URL, such as the disclosed "www.message.com" URL, to all subscribers. In the example embodiment, this URL identifies a resource at server 16a that is used to direct device 18 to an appropriate server. Browser application 102 is used to contact server 16a at this URL (step S704) . Server 16a, in turn identifies one of the servers 16a, 16b and 16c to provide the ICW service for a subscriber at device 18 (steps S802-S806).
Device 18, in turn contacts the appropriate server 16a, 16b or 16c, registers its "on-line" presence (step S708-714), and obtains the ICW service from the appropriate server (step S716).
As will be appreciated only a single device 18 for a single subscriber has been illustrated. Typical servers 16a, 16b and 16c will provide service to large numbers of subscribers operating end-user computing devices interconnected with network 10. Similarly, many other servers like servers 16a, 16b and 16c may co-operate to provide service to all subscribers.
As well, while in the preferred embodiment, device 18 contacts one of servers 16a, 16b, 16c, a person skilled in the art will appreciate that server 16a could serve as a proxy for servers 16b and 16c and contact these servers on behalf of device 18. As will additionally be appreciated, server 16a need not directly provide subscriber services to end-user, but might only act to resolve other servers for subscribers.
While the above embodiment has been described in the context of a temporary connection to network 10 using the PSTN, a person skilled in the art will appreciate that the described embodiments could easily be modified to accommodate other temporary or permanent data network connections, by way of, for example a wireless network, an ISDN connection, an asynchronous digital subscriber line ("ADSL") connection, or another connection known to those skilled in the art. In such modified embodiments, it may be possible to eliminate the use of a stored identifier at device 18. For example, instead, of using 91436-126 MZ/br a stored identifier, device 16a could use the IP address, or a portion of this address, of device 18 in order to decide which of servers 16a, 16b and 16c should provide the service.
As well, each of servers 16a, 16b and 16c could be adapted to redirect queries for interconnected devices to other servers.
As such entries at DNS server 14 for a particular service could resolve DNS queries to the delivered service to any of servers 16a, 16b or 16c. The server contacted as a result of the DNS
resolution then redirects device 18 to the appropriate one of server 16a, 16b and 16c.
Additionally, while the above embodiments have been described specifically with reference to an ICW service, the embodiments could be easily adapted to provide network commerce based services, other messaging services, or simply to distribute server load between multiple servers.
Moreover, while the organization of software and data components at device 26 and gateway 16 has been illustrated as clearly delineated, a person skilled in the art will appreciate that the delineation between applications, network interface software and operating system software is somewhat arbitrary.
Other arrangements of such software are possible. For example, network interface software 104 and 58 may form part of operating system software 52 or 96. Similarly, while the embodiments have been described using the specific IP, and UDP/IP protocols other suitable protocols, such as for example the IPX or SPX protocols, could be used.
It will be further understood that the invention is not limited to the embodiments described herein which are merely illustrative of a preferred embodiments of carrying out the invention, and which are susceptible to modification of form, arrangement of parts, steps, details and order of operation.
The invention, rather, is intended to encompass all modifications within its spirit and scope, as defined by the claims.
91436-126 MZ/br
Computing device 18 is a typical home or office computer comprising a processor 86, in communication with persistent memory 90, a network interface such as modem 88, a display 92, and typically at least one input device 94. Processor 86 is a typical central processing unit and may be a processor in the INTELTM x86 family. Persistent memory 90 preferably comprises a hard drive, RAM and ROM memories. Modem 88 is typically a conventional telephone modem such as for example a U.S. RoboticsTm Sportster or equivalent modem.
An exemplary organization of persistent storage memory 90 of device 18 is illustrated in FIG. 6. As with memory 42 of server 16, stored within memory 90 are computer software programs and data that are loaded into operating memory of device 18. These permit device 18 to be operable as an end-user work station. As illustrated, memory 90 stores operating system software 96; application software 98; and data 100. Operating system software 96 may, for example, be Microsoft Windows NTTM Workstation operating system software;
Windows 3.1, 95 or 98TM software; Apple System 7.5TM operating system software; or the like. Application software 98 includes network interface software 104, which also typically includes an internet protocol suite allowing communication of computing device 18 over modem 88 (FIG. 5) and thus operating system 96 with network 10 (FIG. 1) . Application software 98 further comprises a modem dialer 106 that operates modem 88 to establish temporary connections to data network 10 by way of the PSTN, as detailed below. Application software 98 may further comprise an internet browser application 102, such as the known Netscape', Mosaic', or Microsoft Internet ExplorerTM
browser applications; and other applications 108 otherwise employed by the end-user and operator of device 18. Again, application software 98 may be formed using conventional programming techniques known to those skilled in the art.
An exemplary organization of server 14 is not explicitly illustrated. Server 14, is preferably also a conventional network capable computer server similar to server 16. Server 14, however, is adapted to act as a domain name server to provide DNS as detailed in RFC 2136, and 2137, and accordingly stores data and executes DNS software to provide this service. Briefly, as understood by those skilled in the art, server 14 acting to provide DNS resolves assigned domain names, identified as part of uniform resource locators ("URL"s). Network interconnected devices dispatch messages containing alphanumeric domain names to server 14 over network 10, and are returned numeric thirty-two bit IP
addresses, based on database entries at server 14. For each domain name, server 14 stores one or more numeric stored IP
addresses. For domain names with multiple stored IP
addresses, addresses to alternate interconnected devices are returned sequentially in order to distribute requests between servers.
As illustrated in FIG. 1, example servers 16a, 16b and 16c are each identified by at least one URL
"www.serverl.com", "www.server2.com", and "www.server3.com".
These URLs are used by device 18 and other devices to request service from servers 16a, 16b and 16c. Additionally, server 16a is identified by a second URL "www.message.com".
As will become apparent, this URL is used by device 18 in order to obtain an identifier of one of the servers 16a, 16b, and 16c that will ultimately provide service to device 18.
With reference to FIG. 1, in operation, an end-user at device 18 "subscribes" with one of servers 16a, 16b and 16c in order to obtain service from one of servers 16a, 16b and 16c. An example subscription or registration process is detailed in U.S. patent no. 6,393,467, entitled "Network Interconnected Computing Device, Server and Notification Method", naming Carl Potvin as inventor. As part of the subscription process, device 18 contacts one of servers 16a, 16b and 16c using that server's well known URL. For illustration purposes, a user "Jane Doe" may contact server 16a identified by its URL "www.message.com". Specifically, browser 102 at device 18 contacts server 16a, and provides service subscription information to device 16a which is stored at server 16a in record 72b by CGI programs 65 in co-operation with HTTP
server application 60, and database engine 64. Subscription information may include the subscriber's name, telephone number, e-mail address, billing information, and service information that is stored in a record 72 of database 68. At the conclusion of the subscription process, server 16a may provide device 18 with a unique identifier that is stored at device 18 as a persistent state object or as a permanent "cookie", as detailed in RFC 2019. Again, server 16a uses HTTP server application 60, CGI programs 65 and database engine 64 to generate and provide the persistent state object.
As will be appreciated, the contents of database 68 may be maintained at any or all of devices 16a, 16b or 16c. Data may be mirrored or distributed among servers 16a, 16b, and 16c using conventional techniques. Servers 16a, 16b and 16c could, for example, maintain identical databases by exchanging database entries using network 10.
As will further be appreciated, communications between device 18 and servers 16a, 16b and 16c may be effected through network interface software using the known transmission control protocol ("TCP/IP") as detailed in RFC 793, or the uniform datagram protocol ("UDP/IP") as detailed in RFC 768, or using any other suitable protocol over network 10.
Each of servers 16a, 16b and 16c is adapted to offer substantially similar services. However, servers 16a, 16b and 16c, in combination, are adapted to provide services to a large number of subscribers, such as a subscriber located at device 18. As will be apparent, it would be desirable to distribute the provision of services among servers 16a, 16b and 16c thereby allowing each of the servers 16a, 16b and 16c to process a fraction of the total number of subscribers. The distribution of subscribers to whom services are provided by servers 16a, 16b and 16c, among these servers, may be accomplished in a number of ways, including, by service type (or combination of services), geographically, by telephone dial number or otherwise. However, ideally the distribution of service among the servers 16a, 16b, and 16c should be transparent to each subscriber. Each subscriber should be able to access the service by a single URL, common to all subscribers. Once the criteria for allocating servers to subscribers has been selected, CGI programs 65 may select an appropriate server and update field 84 of a subscriber record during the subscription process. As should be appreciated, field 76 could be eliminated if some other mapping scheme is used. As will become apparent, in the preferred embodiment, 91436-126 MZ/br the identifier provided to device 18 during the registration process is later used to retrieve the contents of field 84 for a subscriber and direct the device 18 to the allocated one of servers 16a, 16b and 16c.
Specifically, steps 700 and 800 performed by device 18 at a later time in order to obtain service from one of servers 16a, 16b and 16c are illustrated in FIGS. 7 and 8, respectively. As illustrated, after subscription to the service, the subscriber at device 18 establishes an internet connection to network 10 through, for example, the PSTN in step S702. An internet connection is typically established through the PSTN by running or launching dialer application 106 (FIG. 6) at device 18; establishing a PSTN circuit between computing device 18 and an internet service provider ("ISP", not shown); and establishing a data link between modems at the ISP and device 18. This link may be established by a serial link internet protocol ("SLIP") or a point-to-point-protocol ("PPP") IP connection between device 18 and the ISP.
As part of establishing this IP link between computing device 18 and the ISP, the ISP may assign a temporary "session" IP address to device 18. This session IP address now uniquely identifies device 18 on network 10 and allows IP
packets to be directed to computing device 18 during this session. Device 18 may now notify the identified server 16a, that device 18 is "on-line" by querying DNS 14 using a known URL of the service which corresponds to one of server 16a, using, for example, web browser application 102, in step S704. In the example embodiments, server 16a is identified by the URL "www.message.com". Next, device 18, contacts server 16a using the numeric IP address of server 16a and provides an indicator (typically a persistent state object or "cookie" stored at device 18) that device 18 is network interconnected ("on-line"), and optionally the session IP
address of device 18 in step S706, as detailed in U.S. patent no.6,393,467 entitled "NETWORK INTERCONNECTED COMPUTING
DEVICE, SERVER AND NOTIFICATION METHOD" naming Carl Potvin as inventor.
In response, in step S802, server 16a receives the message containing the identifier dispatched in step S704 and uses server resolution application 62 (FIG. 3) to query its database 68 (FIG. 4) to locate a record containing a matching identifier in field 76 in step S804. Server resolution application 62 determines an appropriate server 16a, 16b and 16c that will provide the subscribed service to the subscriber at device 18 from field 84 of the appropriate record. The IP address or URL
including a domain name of the appropriate one of servers 16a, 16b or 16c contained in field 84 is provided to device 18 in step S806 and received in step S708. In the example embodiments, for subscriber "Jane Doe", server 16a returns a URL of "www.server2.com", identifying server 16b. As well, IP
address field 82 and status field 78 may be updated when the subscriber has registered with server 16. Additionally, browser 102 may be provided with a temporary persistent state object or "cookie", stored at device 18 and indicating that device 18 is on-line.
Device 18, upon receiving the message containing the URL
identifying server 16b, contacts DNS server 14 to obtain the numeric IP address of server 16b corresponding to the URL
"www.server2.com" in step S710 and thereafter contacts the identified server 16b in step S712 and provides server 16b with registration information similar to that provided to server 16a, immediately after establishing the IP session in step S702, in step S714. As will be appreciated by those skilled in the art, the URL identifying server 16b may be provided by way of a Java script, or an HTTP redirection tag. This makes contact of server 16b appear seamless to an end-user.
Server 16b is again provided, registration information that is typically provided transparently by device 18, by providing server 16b with a"cookie" containing the identifier of device 18. The identified server 16b may then provide data, and thus the subscribed service, to device 18 by way of the 91436-126 MZ/br device's IP address. Device 18 thus receives a subscribed to service from server 16b, in steps S716.
Of course, if server resolution application 62 determines server 16a should provide the service, registration information need not again be provided by device 18. Instead, information provided in step S706 may be used to provide the subscribed service to device 18. As noted, in the preferred embodiment, server 16a is identified by two URLs: one URL, "www.message.com", is used to initially access the service and obtain an URL of an appropriate server, while another URL, "www.serverl.com , is used to obtain service from server lGa. If server 16a provides the service as well as determines an appropriate server, the use of the second URL could be eliminated.
In the preferred embodiment, each of servers 16a, 16b and 16c provide an ICW service, as more particularly described in Canadian Patent Application No. 2,263,264. For this purpose, each of servers 16a, 16b, and 16c comprises messaging application 67 (FIG. 3) that adapts each server to provide a subscriber with an indication of an incoming PSTN
telephone call by way of network 10. As will be appreciated, as the ICW service will typically be provided to a large number of subscribers, the above described method may be used to contact and obtain ICW service from any of servers 16a, 16b and 16c. Typically, each of servers 16a, 16b, and 16c will be specifically adapted to provide ICW service to subscribers connected to specified central office switches of the PSTN, as identified by the end-users telephone dial number. For each subscriber one of servers 16a, 16b and 16c is provided with an indication of an incoming call by way of the call forward busy feature of the subscriber's central office switch. Typically only a single server is in communication with a subscriber's central office switch and will therefore be adapted to provide the ICW service for that subscriber.
The ICW service, however, is typically identified by a single URL, such as the disclosed "www.message.com" URL, to all subscribers. In the example embodiment, this URL identifies a resource at server 16a that is used to direct device 18 to an appropriate server. Browser application 102 is used to contact server 16a at this URL (step S704) . Server 16a, in turn identifies one of the servers 16a, 16b and 16c to provide the ICW service for a subscriber at device 18 (steps S802-S806).
Device 18, in turn contacts the appropriate server 16a, 16b or 16c, registers its "on-line" presence (step S708-714), and obtains the ICW service from the appropriate server (step S716).
As will be appreciated only a single device 18 for a single subscriber has been illustrated. Typical servers 16a, 16b and 16c will provide service to large numbers of subscribers operating end-user computing devices interconnected with network 10. Similarly, many other servers like servers 16a, 16b and 16c may co-operate to provide service to all subscribers.
As well, while in the preferred embodiment, device 18 contacts one of servers 16a, 16b, 16c, a person skilled in the art will appreciate that server 16a could serve as a proxy for servers 16b and 16c and contact these servers on behalf of device 18. As will additionally be appreciated, server 16a need not directly provide subscriber services to end-user, but might only act to resolve other servers for subscribers.
While the above embodiment has been described in the context of a temporary connection to network 10 using the PSTN, a person skilled in the art will appreciate that the described embodiments could easily be modified to accommodate other temporary or permanent data network connections, by way of, for example a wireless network, an ISDN connection, an asynchronous digital subscriber line ("ADSL") connection, or another connection known to those skilled in the art. In such modified embodiments, it may be possible to eliminate the use of a stored identifier at device 18. For example, instead, of using 91436-126 MZ/br a stored identifier, device 16a could use the IP address, or a portion of this address, of device 18 in order to decide which of servers 16a, 16b and 16c should provide the service.
As well, each of servers 16a, 16b and 16c could be adapted to redirect queries for interconnected devices to other servers.
As such entries at DNS server 14 for a particular service could resolve DNS queries to the delivered service to any of servers 16a, 16b or 16c. The server contacted as a result of the DNS
resolution then redirects device 18 to the appropriate one of server 16a, 16b and 16c.
Additionally, while the above embodiments have been described specifically with reference to an ICW service, the embodiments could be easily adapted to provide network commerce based services, other messaging services, or simply to distribute server load between multiple servers.
Moreover, while the organization of software and data components at device 26 and gateway 16 has been illustrated as clearly delineated, a person skilled in the art will appreciate that the delineation between applications, network interface software and operating system software is somewhat arbitrary.
Other arrangements of such software are possible. For example, network interface software 104 and 58 may form part of operating system software 52 or 96. Similarly, while the embodiments have been described using the specific IP, and UDP/IP protocols other suitable protocols, such as for example the IPX or SPX protocols, could be used.
It will be further understood that the invention is not limited to the embodiments described herein which are merely illustrative of a preferred embodiments of carrying out the invention, and which are susceptible to modification of form, arrangement of parts, steps, details and order of operation.
The invention, rather, is intended to encompass all modifications within its spirit and scope, as defined by the claims.
91436-126 MZ/br
Claims (13)
PROPERTY OR PRIVELEGE IS CLAIMED ARE DEFINED AS FOLLOWS:
1. A method of providing incoming call notification of telephone calls received over a telephone network, to a subscriber at a computing device associated with said subscriber by way of a packet switched data network, said method comprising:
operating a plurality of incoming call notification servers, each interconnected with said telephone network and said packet switched data network, each of said incoming call notification servers operable to provide said incoming call notification to specific subscribers;
receiving from said computing device associated with said subscriber at a first network interconnected server, over said packet switched data network, a request to contact a server providing said incoming call notification;
receiving over said packet switched data network from said computing device associated with said subscriber at said first network server, an identifier of said computing device associated with said subscriber;
redirecting said request to a specific one of said plurality of call notification servers interconnected with said packet switched data network capable of providing said subscriber with said incoming call notification service, based on said identifier.
operating a plurality of incoming call notification servers, each interconnected with said telephone network and said packet switched data network, each of said incoming call notification servers operable to provide said incoming call notification to specific subscribers;
receiving from said computing device associated with said subscriber at a first network interconnected server, over said packet switched data network, a request to contact a server providing said incoming call notification;
receiving over said packet switched data network from said computing device associated with said subscriber at said first network server, an identifier of said computing device associated with said subscriber;
redirecting said request to a specific one of said plurality of call notification servers interconnected with said packet switched data network capable of providing said subscriber with said incoming call notification service, based on said identifier.
2. The method of claim 1, further comprising providing said specific one of said plurality of call notification servers with an assigned computer network address of said computing device associated with said subscriber, to later obtain said incoming call notification from said specific one of said plurality of call notification servers.
3. The method of claim 1, wherein said assigned computer network address comprises a temporarily assigned internet protocol (IP) address.
4. The method of claim 3, wherein said identifier is stored at said computing device associated with said subscriber.
5. The method of claim 4, wherein said identifier comprises a persistent state object.
6. The method of claim 5, wherein said first network interconnected server is identified on said packet switched data network by a uniform resource locator ("URL").
7. The method of claim 6, wherein said redirecting comprises providing a network address of said specific one of said plurality of servers to said computing device associated with said subscriber.
8. The method of claim 6, wherein said redirecting comprises providing said computing device associated with said subscriber with a URL of said specific one of said servers.
9. The method of claim 1, further comprising maintaining at said first network interconnected server a database mapping call notification servers to subscribers based to permit said redirecting based on said identifier.
10. A method of providing incoming call notification of telephone calls received over a telephone network, to a subscriber at a computing device associated with said subscriber by way of a packet switched data network, said method comprising:
receiving from said computing device associated with said subscriber at a first network interconnected server, over said packet switched data network, a request to contact a server providing said incoming call notification;
receiving over said packet switched data network from said computing device associated with said subscriber at said first network server, an identifier of said computing device associated with said subscriber;
based on said identifier, redirecting said request to a specific one of a plurality of call notification servers interconnected with said packet switched data network and said telephone network and capable of providing said subscriber with said incoming call notification.
receiving from said computing device associated with said subscriber at a first network interconnected server, over said packet switched data network, a request to contact a server providing said incoming call notification;
receiving over said packet switched data network from said computing device associated with said subscriber at said first network server, an identifier of said computing device associated with said subscriber;
based on said identifier, redirecting said request to a specific one of a plurality of call notification servers interconnected with said packet switched data network and said telephone network and capable of providing said subscriber with said incoming call notification.
11. The method of claim 10, wherein said identifier comprises a persistent state object.
12. Computer readable medium storing processor readable instructions that when loaded at a network server including a processor, adapt said server to perform the method of claim 10.
13. A server interconnected with a packet switched data network, said server comprising a processor and computer readable memory storing program instructions and data adapting said server to:
receive from a computing device associated with a subscriber at a first network interconnected server, over said packet switched data network, a request to contact a server providing incoming call notifications over said packet switched data network of telephone calls received over a telephone network, for said subscriber;
redirect said request to a specific one of a plurality of call notification servers interconnected with said packet switched data network and said telephone network, each of said incoming call notification servers for providing incoming call notification of telephone calls received over a telephone network to specific subscribers at an associated computing device by way of a packet switched data network, said specific one of said incoming call notification servers capable of providing said subscriber with said incoming call notification, based on an identifier of said computing device associated with said subscriber.
receive from a computing device associated with a subscriber at a first network interconnected server, over said packet switched data network, a request to contact a server providing incoming call notifications over said packet switched data network of telephone calls received over a telephone network, for said subscriber;
redirect said request to a specific one of a plurality of call notification servers interconnected with said packet switched data network and said telephone network, each of said incoming call notification servers for providing incoming call notification of telephone calls received over a telephone network to specific subscribers at an associated computing device by way of a packet switched data network, said specific one of said incoming call notification servers capable of providing said subscriber with said incoming call notification, based on an identifier of said computing device associated with said subscriber.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CA002246133A CA2246133C (en) | 1998-08-31 | 1998-08-31 | Method and devices for providing network services from several servers |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CA002246133A CA2246133C (en) | 1998-08-31 | 1998-08-31 | Method and devices for providing network services from several servers |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CA2246133A1 CA2246133A1 (en) | 2000-02-29 |
| CA2246133C true CA2246133C (en) | 2007-12-04 |
Family
ID=29409821
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CA002246133A Expired - Fee Related CA2246133C (en) | 1998-08-31 | 1998-08-31 | Method and devices for providing network services from several servers |
Country Status (1)
| Country | Link |
|---|---|
| CA (1) | CA2246133C (en) |
-
1998
- 1998-08-31 CA CA002246133A patent/CA2246133C/en not_active Expired - Fee Related
Also Published As
| Publication number | Publication date |
|---|---|
| CA2246133A1 (en) | 2000-02-29 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US6801952B2 (en) | Method and devices for providing network services from several servers | |
| US6393467B1 (en) | Network interconnected computing device, server and notification method | |
| US7308499B2 (en) | Dynamic load balancing for enterprise IP traffic | |
| US6421674B1 (en) | Methods and systems for implementing a real-time, distributed, hierarchical database using a proxiable protocol | |
| US6026441A (en) | Method for establishing communication on the internet with a client having a dynamically assigned IP address | |
| EP1207703B1 (en) | Accessing communications data | |
| EP0960515B1 (en) | Gateway location system supporting pots-internet gateways | |
| JP4592184B2 (en) | Method and apparatus for accessing device with static identifier and intermittently connected to network | |
| AU704385B2 (en) | Method of accessing service resource items that are for use in a telecommunications system | |
| US7562153B2 (en) | Method and apparatus for content distribution network brokering and peering | |
| US6282281B1 (en) | Method of providing telecommunications services | |
| US8204046B2 (en) | Method and apparatus for accessing service resource items that are for use in a telecommunications system | |
| KR100426306B1 (en) | Method for providing a load distributed processing among session initiation protocol servers | |
| US20040160946A1 (en) | Internet telephony network and methods for using the same | |
| US6850484B1 (en) | Packet redirection and message stream management | |
| WO1999029083A1 (en) | Method and apparatus for dynamic domain names | |
| CA2246133C (en) | Method and devices for providing network services from several servers | |
| WO1999028979A2 (en) | Digital phone system | |
| WO2002039215A9 (en) | Distributed dynamic data system and method | |
| CA2246136C (en) | Network interconnected computing device, server and notification method | |
| EP1715668A1 (en) | Method of establishing a telecommunication connection | |
| Tsai et al. | A Session Migration Scheme for Smart Web Services in Mobile Computing. | |
| AU4445999A (en) | Method and apparatus for a dynamic ILS |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| EEER | Examination request | ||
| MKLA | Lapsed |
Effective date: 20160831 |