Claims
- 1. A system for managing bandwidth in a remote services system comprising:
a throttle module operable to control transfer of data within said remote services system in accordance with predetermined quality of service parameters; a first remote services system component operable to generate a request to transfer data; and a second remote services system component receiving said request, said second remote services system component being operable to authorize transfer of data in accordance with predetermined parameters and to control operation of said throttle module to maintain a predetermined quality of service for data transfer.
- 2. The system of claim 2, wherein said first system component comprises a proxy.
- 3. The system of claim 1, wherein said second system component comprises an application mid-level manager.
- 4. The system of claim 1, further comprising a queuing module for ranking files in accordance with predetermined priority parameters, said queuing module operating in conjunction with said throttle module to control access to system bandwidth.
- 5. The architecture according to claim 4, further comprising a back-channel data path for implementing access control over system bandwidth by said throttle module.
- 6. The system of claim 1, wherein said application mid-level manager operates in an intermediate mid-level manager farm having a plurality of intermediate mid level managers.
- 7. The system of claim 6, wherein the intermediate mid-level manager farm uses a shared session object to share information among the plurality of intermediate mid-level managers within the intermediate mid level manager farm.
- 8. The system of claim 7 wherein the shared session object includes a local resource locater identifying the proxy that generated the request to transfer data within said remote services system.
- 9. The system of claim 1 wherein the data transferred in said remote services system comprises data that has been converted from email protocol to HTTP protocol.
- 10. An architecture for managing bandwidth in a remote services system comprising:
a throttle module operable to control transfer of data within said remote services system in accordance with predetermined quality of service parameters; a queuing module for ranking files in accordance with predetermined priority parameters, said queuing module operating in conjunction with said throttle module to control access to system bandwidth; a proxy operable to generate a request to transfer data; and at least one mid-level manager operable receive said request to transfer data and to control operation of said throttle and said queuing module to control bandwidth allocation for data transmission over said remote services system.
- 11. The architecture according to claim 10, said priority parameters used by said queuing module comprising precedence and persistence attributes specified in accordance with predetermined quality of service parameters.
- 12. The architecture according to claim 11, further comprising a back-channel data path for implementing access control over system bandwidth by said throttle module.
- 13. The architecture according to claim 12, further comprising a directory assistance protocol server for controlling access to configuration parameters relating to bandwidth allocation in said remote services system.
- 14. The architecture according to claim 13, further comprising an internet web access portal to provide a user with controlled access to said directory assistance protocol server to change said bandwidth allocation parameters.
- 15. The system of claim 10 wherein the data transferred in said remote services system comprises data that has been converted from email protocol to HTTP protocol.
- 16. An architecture for prioritizing data flow in a remote services system comprising:
a throttle module operable to control transfer of data within said remote services system in accordance with predetermined quality of service parameters; a queuing module for ranking files in accordance with predetermined priority parameters, said queuing module operating in conjunction with said throttle module to control access to system bandwidth; an intermediate mid-level manager, an applications mid-level manager, said applications mid-level manager operating in conjunction with said queuing module and said intermediate mid-level manager to control operation of said plurality of proxies to prioritize data transmission over said remote services system.
- 17. The architecture according to claim 16, said queuing module operable to rank data files according to precedence and persistence attributes specified in accordance with predetermined quality-of-service parameters.
- 18. The architecture according to claim 17, further comprising a back-channel data path for implementing access control over system bandwidth by said throttle module.
- 19. The architecture according to claim 18, further comprising a directory assistance protocol server for controlling access to configuration parameters relating to bandwidth allocation in said remote services system.
- 20. The architecture according to claim 19, further comprising an internet web access portal to provide a user with controlled access to said directory assistance protocol server to change said bandwidth allocation parameters.
- 21. The architecture according to claim 16 wherein the data transferred in said remote services system comprises data that has been converted from email protocol to HTTP protocol.
- 22. A method for managing bandwidth in a remote services system, comprising:
generating a request to transfer data from a first component of said remote services system; receiving said request by a second component of said remote services system; using said second component of said remote services system to authorize transfer of data in accordance with predetermined parameters; and using said second component of said remote service system to control operation of a throttle module to maintain transfer of data in said remote service s system in accordance with predetermined quality of service parameters.
- 23. The method of claim 22, wherein said first system component comprises a proxy.
- 24. The method of claim 23, wherein said second system component comprises an application mid-level manager.
- 25. The method of claim 24, further comprising
using said mid-level manager to control a queuing module for ranking files in accordance with predetermined priority parameters, said queuing module operating in conjunction with said throttle module to control access to system bandwidth.
- 26. The method according to claim 25, further comprising using a back-channel data path for implementing access control over system bandwidth by said throttle module.
- 27. The method according to claim 22 wherein the data transferred in said remote services system comprises data that has been converted from email protocol to HTTP protocol.
CROSS REFERENCE TO RELATED APPLICATIONS
[0001] This application relates to co-pending U.S. patent application Ser. No. 10/067,040, attorney docket number P7223, filed on Feb. 4, 2002, entitled “Remote Services System Management Interface” and naming Michael J. Wookey, Trevor Watson and Jean Chouanard as inventors, the application being incorporated herein by reference in its entirety.
[0002] This application relates to co-pending U.S. patent application Ser. No. 10/067,074, attorney docket number P7225, filed on Feb. 4, 2002, entitled “Remote Services Message System to Support Redundancy of Data Flow” and naming Michael J. Wookey, Trevor Watson and Jean Chouanard as inventors, the application being incorporated herein by reference in its entirety.
[0003] This application relates to co-pending U.S. patent application Ser. No. 10/066,950, attorney docket number P7229, filed on Feb. 4, 2002, entitled “Remote Services Delivery Architecture” and naming Michael J. Wookey, Trevor Watson and Jean Chouanard as inventors, the application being incorporated herein by reference in its entirety.
[0004] This application relates to co-pending U.S. patent application Ser. No. 10/066,828, attorney docket number P7230, filed on Feb. 4, 2002, entitled “Prioritization of Remote Services Messages Within a Low Bandwidth Environment” and naming Michael J. Wookey, Trevor Watson and Jean Chouanard as inventors, the application being incorporated herein by reference in its entirety.
[0005] This application relates to co-pending U.S. patent application Ser. No. 10/067,165, attorney docket number P7231, filed on Feb. 4, 2002, entitled “Remote Services System Back-Channel Multicasting” and naming Michael J. Wookey, Trevor Watson and Jean Chouanard as inventors, the application being incorporated herein by reference in its entirety.
[0006] This application relates to co-pending U.S. patent application Ser. No. 10/066,841, attorney docket number P7233, filed on Feb. 4, 2002, entitled “Remote Services System Data Delivery Mechanism” and naming Michael J. Wookey, Trevor Watson and Jean Chouanard as inventors, the application being incorporated herein by reference in its entirety.
[0007] This application relates to co-pending U.S. patent application Ser. No. 10/066,914, attorney docket number P7234, filed on Feb. 4, 2002, entitled “Remote Services WAN Connection Identity Anti-spoofing Control” and naming Michael J. Wookey, Trevor Watson and Jean Chouanard as inventors, the application being incorporated herein by reference in its entirety.
[0008] This application relates to co-pending U.S. patent application Ser. No. 10/066,075, attorney docket number P7235, filed on Feb. 4, 2002, entitled “Automatic Communication Security Reconfiguration for Remote Services” and naming Michael J. Wookey, Trevor Watson and Jean Chouanard as inventors, the application being incorporated herein by reference in its entirety.
[0009] This application relates to co-pending U.S. patent application Ser. No. ______, attorney docket number P7501, filed on an even date herewith, entitled “Remote Services: Nile Communication Modules” and naming Michael J. Wookey, Trevor Watson and Jean Chouanard as inventors, the application being incorporated herein by reference in its entirety.
[0010] This application relates to co-pending U.S. patent application Ser. No. ______, attorney docket number P7502, filed on an even date herewith, entitled “Remote Services: Nile Relocatable Mid Level Manager” and naming Michael J. Wookey, Trevor Watson and Jean Chouanard as inventors, the application being incorporated herein by reference in its entirety.
[0011] This application relates to co-pending U.S. patent application Ser. No. ______, attorney docket number P7504, filed on an even date herewith, entitled “Remote Services: Services API” and naming Michael J. Wookey, Trevor Watson and Jean Chouanard as inventors, the application being incorporated herein by reference in its entirety.