1. A developer system for an electrographic printer having a photoconductor element, comprising:
a magnetic brush having a magnetic core surrounded by a toning shell that rotatably conveys a layer of developer to said photoconductor element;
a sump containing a reservoir of developer;
a self-metering conveyor roller for conveying developer from the reservoir to said toning shell of said magnetic brush having at least two magnetic poles of opposite polarity,
an engageable metering skive in a developer flow path around said toning shell between said conveyor roller and said photoconductor element capable of engagement; and
a driving assembly that rotates the conveyor roller at a saturation speed that saturates the flow of developer on the toning shell so that it is essentially constant when the conveyor roller speed is increased beyond the saturation speed if the engageable metering skive is engaged or not engaged.
2. The developer system of claim 1, further comprising an engageable metering skive that is not engaged.
3. The developer system of claim 1, wherein a maximum magnetic field strength of the outer surface of the roller is less than 1000 gauss, and a minimum magnetic field strength between poles at said outer surface is no less than 30% of said maximum field strength.
4. The developer system of claim 1, wherein; and
the driving assembly that rotates the conveyor roller at a saturation speed that saturates the capacity of the conveyor roller to deliver developer to said toning shell such that the flow of developer on the toning shell is essentially constant when the conveyor roller speed is increased beyond the saturation speed and engages a metering skive such that the flow on the toning shell is less if the metering skive is engaged.
5. The developer system of claim 1, wherein a maximum magnetic field strength of the outer surface of the roller is between about 100 and 300 gauss, and a minimum magnetic field strength of said outer surface is no less than about 35% of said maximum field strength.
6. The developer system of claim 1, wherein said magnetic core of said conveyor roller includes a plurality of magnets around the circumference of the roller, the poles of each of said magnets being radially aligned with respect to a central axis of said roller and alternating between adjacent magnets.
7. The developer system of claim 6, wherein said conveyor roller includes a cylindrical shell rotatably mounted around said magnetic core, and wherein said magnets extend around between about 100\xb0 and 160\xb0 around said circumference of the magnetic core.
8. The developer system of claim 6, wherein said magnets are flexible strip magnets.
9. The developer system of claim 6, wherein said magnetic core includes an even number of magnets.
10. The developer system of claim 1, further comprising means for driving said magnetic brush consistent with a printing speed of at least 80 ppm.
11. The developer system of claim 1, further comprising means for rotating said conveyor roller at a speed that delivers developer at a rate of at least 5.0 gin.-sec.
12. The developer system of claim 11, further comprising means for rotating said conveyor roller at a speed that delivers developer at a rate of at least 5.35 gin.-sec.
13. The developer system of claim 12, wherein said rotating means rotates said developer roller at a speed of at least 75 rpm.
14. A method of metering a constant flow rate of developer to a toning shell of a magnetic brush that develops latent electrostatic images on a photoconductor element without the need for a metering skive, comprising the steps of:
providing an engageable rotatable self-metering conveyor roller between a reservoir of developer and said toning shell, wherein a maximum magnetic field strength on an outer surface of said roller and having at least two magnetic poles of opposite polarity; and
rotating the conveyor roller at a saturation speed that saturates the capacity of the toning shell to receive developer without a metering skive adjacent to the toning shell such that that a constant flow amount of developer is provided to the toning shell despite variations in the speed of rotation of said conveyor roller when the conveyor roller speed is increased beyond the saturation speed.
15. The developer metering method of claim 14, wherein a maximum magnetic field strength of the outer surface of the roller is less than 1000 gauss, and a minimum magnetic field strength between poles at said outer surface is no less than 30% of said maximum magnetic field strength.
16. The developer metering method of claim 14, wherein a maximum magnetic field strength of the outer surface of the roller is between about 100 and 300 gauss, and a minimum magnetic field strength of said outer surface is no less than about 35% of said maximum magnetic field strength.
17. The developer metering method of claim 14, further comprising:
a metering skive in a developer flow path around said toning shell between said conveyor roller and said photoconductor element capable of engagement; and
a driving assembly that rotates the conveyor roller at a saturation speed that saturates the capacity of the conveyor roller to deliver developer to said toning shell such that the flow of developer on the toning shell is essentially constant when the conveyor roller speed is increased beyond the saturation speed and engages a metering skive such that the flow on the toning shell is less if the metering skive is engaged.
18. The developer metering method of claim 14, wherein said conveyor roller includes a cylindrical shell rotatably mounted around a magnetic core, and having magnets that extend around between about 100\xb0 and 160\xb0 around said circumference of the magnetic core.
19. The developer metering method of claim 14, further comprising the step of driving said magnetic brush consistent with a printing speed of at least 80 ppm.
20. The developer metering method of claim 14, further comprising the step of rotating said conveyor roller at a speed that delivers developer at a rate of at least 5.0 gin.-sec.
21. The developer metering method of claim 14, further comprising the step of rotating said conveyor roller at a speed that delivers developer at a rate of at least 6.0 gin.-sec.
22. The developer metering method of claim 14, further comprising the step of rotating said conveyor roller at a speed of at least 75 rpm
The claims below are in addition to those above.
All refrences to claim(s) which appear below refer to the numbering after this setence.
1. A method for application steering or blocking transmitted encrypted data from a source tunnel endpoint to a target tunnel endpoint over an encrypted tunnel in accordance with application steering or blocking policies, the method comprising:
at a source tunnel endpoint of the encrypted tunnel, mapping a first Security Parameter Index (SPI) and a second SPI to a first application identifier to generate first mapping information, the first application identifier identifying the first application that is generating the encrypted data and that, in combination with the application steering or blocking policies, is used to identify a particular interface for further transmitting encrypted data generated by the first application towards the target tunnel endpoint;
communicating the first mapping information from the source tunnel endpoint to an intermediate network entity for use by the intermediate network entity, in combination with the application steering or blocking policies, in identifying the particular interface for further transmitting the encrypted data generated by the first application towards the target tunnel endpoint; and
concatenating an unencrypted header including the first SPI with a first encrypted data payload generated by the first application to create a first communications packet; and
the source tunnel endpoint transmitting the first communications packet to the target tunnel endpoint over the encrypted tunnel via the intermediate network entity and in accordance with the application steering or blocking policies associated with the first application.
2. The method according to claim 1, wherein the first SPI comprises an inbound SPI and wherein the second SPI comprises an outbound SPI.
3. The method according to claim 1, further comprising:
the intermediate network entity extracting the first SPI from the unencrypted header of the first communications packet; and
the intermediate network entity using the first SPI and the first mapping information previously received to determine the first application identifier and to identify the first application associated with the first application identifier;
the intermediate network entity using the identity of the first application and the application steering or blocking policies to determine the particular interface necessary for further transmitting the first encrypted data to the target tunnel endpoint over the encrypted tunnel; and
the intermediate network entity transmitting the first encrypted data to the target tunnel endpoint using the determined particular interface.
4. The method according to claim 3, wherein the determined particular interface comprises one of an 802.11 wireless interface, a cellular wireless interface, a satellite wireless interface, and a wired interface.
5. The method according to claim 4, wherein each of the 802.11 wireless interface, cellular wireless interface, satellite wireless interface, and wired interface is associated with a different internet protocol (IP) address for further transmitting the first communications packet towards the target endpoint.
6. The method according to claim 3, wherein the source tunnel endpoint comprises a mobile host, and wherein the network entity comprises a mobile router.
7. The method according to claim 3, wherein the source tunnel endpoint comprises a Policy Enforcement Point (PEP).
8. The method according to claim 7, wherein the intermediate network entity comprises another Policy Enforcement Point (PEP).
9. The method according to claim 8, wherein the intermediate network entity comprises a mobile router.
10. The method according to claim 1, wherein the intermediate network entity determines the first application identifier from the SPI and uses the first application identifier at the intermediate network entity to enable blocking policies that prevent one or more interfaces from being used to transmit packets which originate from a particular application.
11. The method according to claim 1, wherein communicating the first mapping information from the source tunnel endpoint to the intermediate network entity enables the intermediate network entity to provide different levels of QoS on encrypted data from the source tunnel endpoint dependent on the SPI parameter included in a transmitted packet so that different applications running on the source tunnel endpoint are able to have different levels of QoS.
12. The method according to claim 1, further comprising the source tunnel endpoint negotiating for each application a unique security association (SA) containing the mapping directly with a policy enforcement point of a home network of the source tunnel endpoint prior to communicating the first mapping information from the source tunnel endpoint to the intermediate network entity, the source tunnel endpoint communicating with the policy enforcement point through the intermediate network entity after the source tunnel endpoint negotiated with the policy enforcement point.
13. A system for enabling application steering or blocking transmitted encrypted data from a source tunnel endpoint to a target tunnel endpoint over an encrypted tunnel in accordance with configured application steering or blocking policies, the system comprising:
a source tunnel endpoint node comprising a first processor, first memory, and first transceiver, the first processor configured to:
associate a first Security Parameter Index (SPI) and a second SPI to a first application identifier to generate first mapping information, the first application identifier identifying the first application that is generating the encrypted data and that, in combination with the application steering or blocking policies, is used to identify a particular interface for further transmitting encrypted data generated by the first application towards the target tunnel endpoint;
communicate, via the first transceiver, the first mapping information to an intermediate network entity for use by the intermediate network entity, in combination with the application steering or blocking policies, in identifying the particular interface for further transmitting the encrypted data generated by the first application towards the target tunnel endpoint;
concatenate an unencrypted header including the first SPI with a first encrypted data payload generated by the first application to create a first communications packet; and
transmit, via the first transceiver, the first communications packet to the target tunnel endpoint over the encrypted tunnel via the intermediate network entity and in accordance with the application steering or blocking policies associated with the first application; and
the intermediate network entity, coupled to the source tunnel endpoint over the encrypted tunnel, and comprising a second processor, second transceiver, and second memory, the second processor configured to:
receive, via the second transceiver, the first mapping information and store the first mapping information in the second memory;
receive, via the second transceiver, the first communications packet;
extract the first SPI from the unencrypted header of the first communications packet,
use the first SPI and the first mapping information to determine the first application identifier and to identify the first application associated with the first application identifier;
use the identity of the first application and application steering or blocking policies configured at the intermediate network entity to determine the particular interface necessary for further transmitting the first encrypted data to the target tunnel endpoint over the encrypted tunnel; and
transmit, via the second transceiver, the first encrypted data towards the target tunnel endpoint using the determined particular interface.
14. The system according to claim 13, wherein the first SPI comprises an inbound SPI and the second SPI comprises an outbound SPI.
15. The system according to claim 13, wherein the source tunnel endpoint comprises a mobile host, and wherein the intermediate network entity comprises a mobile router.
16. The system according to claim 13, wherein the intermediate network entity comprises a router, and wherein the selected interface is used to transmit the first communications packet from the router to another network entity on a path towards the target tunnel endpoint.
17. The system according to claim 13, wherein the source tunnel endpoint comprises a Policy Enforcement Point (PEP).
18. The system according to claim 17, wherein the intermediate network entity comprises another Policy Enforcement Point (PEP).
19. The system according to claim 13, wherein the determined particular interface comprises one of an 802.11 wireless interface, a cellular wireless interface, a satellite wireless interface, and a wired interface.
20. The system according to claim 19, wherein each of the 802.11 wireless interface, cellular wireless interface, satellite wireless interface, and wired interface is associated with a different internet protocol (IP) address for further transmitting the first communications packet towards the target tunnel endpoint.
21. A source tunnel node configured to communicate with a target tunnel node via an intermediate network entity over an encrypted tunnel supporting application steering or blocking of encrypted data, the source tunnel node comprising:
a memory configured to store a unique Security Parameter Index (SPI) for each application identifier, each application identifier identifying a particular application that is generating encrypted data at the source tunnel node and that, in combination with application steering or blocking policies, may be used to identify a particular interface necessary for transmitting encrypted data generated by a corresponding application towards the target tunnel node;
a processor configured to associate a first Security Parameter Index (SPI) and a second SPI to a first application identifier and to generate first mapping information, the first application identifier identifying a first application that is generating first encrypted data at the source tunnel node and that, in combination with the application steering or blocking policies, may be used to identify a particular interface necessary for further transmitting encrypted data generated by a first application towards the target tunnel node;
a transmitter configured to transmit the first mapping information to the intermediate network entity for use by the intermediate network entity, in combination with the application steering or blocking policies in identifying the particular interface for further transmitting the encrypted data generated by the first application towards the target tunnel endpoint,
the processor further configured to concatenate an unencrypted header including the first SPI with a first encrypted data payload generated by the first application to create a first communications packet; and
the transmitter further configured to transmit the first communications packet towards the target tunnel node over the encrypted tunnel via the intermediate network entity, and in accordance with the application steering or blocking policies associated with the first application.
22. The source tunnel node according to claim 21, wherein the first SPI comprises an inbound SPI and the second SPI comprises an outbound SPI.
23. The source tunnel node according to claim 21, wherein the source tunnel node comprises a mobile host, and wherein the intermediate network entity comprises a mobile access point.
24. The source tunnel node according to claim 21, wherein the source tunnel node comprises a Policy Enforcement Point (PEP), and wherein the intermediate network entity comprises another Policy Enforcement Point (PEP).
25. An intermediate network entity for forwarding encrypted data payloads received from a source tunnel endpoint to a target tunnel endpoint over an encrypted tunnel, the intermediate network entity comprising:
a memory which stores first mapping information from a source tunnel endpoint, wherein the first mapping information comprises at least a first Security Parameter Index (SPI) and a second Security Parameter Index (SPI) associated with a first application identifier, the first application identifier identifying a particular application that is generating encrypted data at the source tunnel node and that, in combination with application steering or blocking policies, may be used to identify a particular interface necessary for further transmitting encrypted data payloads generated by the first application to the target tunnel node;
a receiver configured to receive a first encrypted communications packet from the source tunnel endpoint over the encrypted tunnel, wherein the first communications packet comprises a first encrypted data payload and a first unencrypted header including the first SPI; and
a processor configured to:
extract the first SPI from the unencrypted header, and to determine the first application identifier based on the first SPI and the previously received first mapping information, and to identify a first application associated with the first application identifier, and
use the identity of the first application and the application steering or blocking policies configured at the intermediate network entity to determine the particular interface necessary for further transmitting the first encrypted data payload to the target tunnel endpoint over the encrypted tunnel; and
a transmitter configured to transmit the first encrypted data payload towards the target tunnel endpoint using the determined particular interface.
26. The intermediate network entity according to claim 25, wherein the first SPI comprises an inbound SPI and the second SPI comprises an outbound SPI.
27. The intermediate network entity according to claim 25, wherein the intermediate network entity comprises a mobile router or a Policy Enforcement Point (PEP).
28. Tile intermediate network entity according to claim 25, wherein the determined particular interface comprises one of an 802.11 wireless interface, a cellular wireless interface, a satellite wireless interface, and a wired interface.
29. The intermediate network entity according to claim 28, wherein each of the 802.11 wireless interface, cellular wireless interface, satellite wireless interface, and wired interface is associated with a different internet protocol (IP) address for further transmitting the first communications packet towards the target tunnel endpoint.