초록 ▼

In conventional ad-hoc networks using reactive routing protocols the route between the source node and the destination node is not updated until the route is actually broken. In response to predetermined events a request for updated route message can be sent to the destination node to determine if a

In conventional ad-hoc networks using reactive routing protocols the route between the source node and the destination node is not updated until the route is actually broken. In response to predetermined events a request for updated route message can be sent to the destination node to determine if another route exists between the source node and the destination node. A reply to the request for updated route can be provided by either the destination node or by a node which has a cached route between the source node and the destination node. This updated route request scheme can be implemented in networks which use source routing and networks which use distance vector routing.

대표청구항 ▼

In conventional ad-hoc networks using reactive routing protocols the route between the source node and the destination node is not updated until the route is actually broken. In response to predetermined events a request for updated route message can be sent to the destination node to determine if a

In conventional ad-hoc networks using reactive routing protocols the route between the source node and the destination node is not updated until the route is actually broken. In response to predetermined events a request for updated route message can be sent to the destination node to determine if another route exists between the source node and the destination node. A reply to the request for updated route can be provided by either the destination node or by a node which has a cached route between the source node and the destination node. This updated route request scheme can be implemented in networks which use source routing and networks which use distance vector routing. 1. In a communication center system wherein agents participate in and host chat room communication sessions on the Internet, a chat room session management system, comprising: a data repository storing parameters regarding individual sessions in progress in the communication center system and agent parameters including one or both of minimum and maximum load capabilities for individual agents; and a management software executing on a server associated with the communication center system; characterized in that the management software calculates agent load level over sessions hosted by an individual agent, compares the calculated load level with one or both of minimum and maximum load for said agent, and adjusts agent loading or wait time accordingly. 2. The system of claim 1 wherein the session management system, upon determining a first agent's load level is above maximum, increases wait time or assigns one or more sessions hosted by the first agent to a second agent, or both, reducing the first agent's load. 3. The system of claim 1 wherein the session management system, upon determining a first agent's load level is below minimum, assigns one or more addition sessions to the first agent. 4. The system of claim 1 wherein the session management system operates in a call center having multiple agents interconnected on a communication network. 5. The system of claim 1 wherein the management software determines agent loading by both traffic and agent capability level. 6. In a communication center system wherein agents participate in and host chat room communication sessions on the Internet, a method for managing agent load in the sessions, comprising steps of: (a) storing parameters regarding individual chat room sessions in progress in the communication center system and agent parameters including one or both of minimum and maximum load capabilities for individual agents in a data repository; (b) calculating agent load level by a management software; (c) comparing calculated agent load level with stored minimum and/or maximum allowed agent load level; and (d) adjusting agent assignment to sessions according to the comparison in step (c). 7. The method of claim 6 wherein the session management system, upon determining a first agent's load level is above maximum, assigns one or more sessions hosted by the agent to a second agent, reducing the first agent's load. 8. The system of claim 6 wherein the session management system, upon determining a first agent's load level is below minimum, assigns one or more additional sessions to the first agent. 9. The method of claim 6 wherein the session management system operates in a call center having multiple agents interconnected on a local area network (LAN). 10. The method of claim 6 wherein the management software determines agent loading by both traffic and agent capability level. 11. An Internet-capable communication center comprising: multiple agent stations having individual chat room session-capable computer stations interconnected on a local area network (LAN); and a server connected on the LAN and executing a management software; characterized in that the management software calculates agent load-level and manages agent assignment to chat room sessions based on the calculated load level. 12. The communication center of claim 11 wherein individual agents are assigned a maximum load level, and the management software, upon determining a first agent's load level is above maximum, assigns one or more sessions hosted by the first agent to a second agent, reducing the first agent's load level. 13. The communication center of claim 11 wherein individual agents are assigned a minimum load level, and the management software, upon determining a first agent's load level is below minimum, assigns one or more additional sessions to the first agent. 14. The communication center of claim 11 wherein the management software determines agent loading by both traffic and agent c apability level.