Author: claimsbot

1. A cloud gateway system comprising:
an enterprise gateway system located in an enterprise network and comprising
a software installer configured to upload remote gateway software to a cloud provider network and to install the remote gateway software on a first virtual machine in the cloud provider network, and
a network services tool configured to establish a virtual private network between the enterprise gateway system and the first virtual machine and to provide plug-in network services having remote components; and

a remote gateway system located in the cloud provider network and comprising
a virtual machine connection tool configured to establish a secure connection between the first virtual machine and a second virtual machine in the cloud provider network, and
a remote network services tool configured to execute the remote components of the plug-in network services.
2-6. (canceled)
7. The cloud gateway system of claim 1, wherein the remote gateway system further comprises a virtual machine creation tool configured to create the second virtual machine in the cloud provider network.
8. The cloud gateway system of claim 1, further comprising a client access agent located on a mobile device.
9. The cloud gateway system of claim 8, wherein the client access agent comprises a mobile network services tool configured to establish a mobile virtual private network between the mobile device and the second virtual machine and to provide plug-in network services having remote components.
10. A cloud hypervisor system comprising:
a set of front-end plug-ins, each configured to establish a pseudo-hypervisor instance and to translate a hypervisor API call received by the pseudo-hypervisor instance into an intermediate representation;
a service bus configured to route an intermediate representation to a back-end plug-in; and
a set of back-end plug-ins, each configured to translate an intermediate representation into a cloud API call.
11. The cloud hypervisor system of claim 10, wherein each front-end plug-in is further configured to place an intermediate representation on the service bus.
12. The cloud hypervisor system of claim 11, wherein each front-end plug-in is further configured to pass a destination parameter with each intermediate representation placed on the service bus.
13. The cloud hypervisor system of claim 12, wherein the destination parameter indicates a cloud provider network account.
14. The cloud hypervisor system of claim 12, wherein the destination parameter indicates a route to a back-end plug-in.
15. The cloud hypervisor system of claim 11, wherein each front-end plug-in is further configured to return a response code to a pseudo-hypervisor instance after placing an intermediate representation on the service bus.
16. The cloud hypervisor system of claim 10, wherein each front-end plug-in is further configured to generate an intermediate representation that can be understood by all of the back-end plug-ins.
17. The cloud hypervisor system of claim 10, wherein the pseudo-hypervisor instance is associated with an account at a cloud infrastructure provider.
18. The cloud hypervisor system of claim 10, wherein the service bus is further configured to return a result code to a pseudo-hypervisor instance after routing an intermediate representation.
19. The cloud hypervisor system of claim 10, wherein the service bus is further configured to return a result code to a pseudo-hypervisor instance upon a failure to complete the routing of an intermediate representation.
20. The cloud hypervisor system of claim 10, wherein each back-end plug-in corresponds to a cloud provider account.
21. The cloud hypervisor system of claim 10, further comprising a web console configured to plug into the service bus and graphically expose cloud infrastructure management functions.
22. The cloud hypervisor system of claim 10, further comprising a topology manager configured to plug into the service bus, wherein the topology manager includes an infrastructure topology creation tool and an infrastructure topology deployment tool.
23. A cloud hypervisor system comprising:
a pseudo-hypervisor creation tool configured to establish a pseudo-hypervisor instance;
an API call listening tool configured to listen for and receive hypervisor API calls;
a hypervisor API call translation tool configured to translate a hypervisor API call received by the API call listening tool into an intermediate representation;
a cloud API translation tool configured to translate an intermediate representation into a cloud API call; and
a routing tool configured to route an intermediate representation from the hypervisor API call translation tool to the cloud API translation tool.
24. A method for managing cloud infrastructure, the method comprising:
uploading remote gateway software from an enterprise network to a cloud provider network;
installing the remote gateway software on a first virtual machine in the cloud provider network;
establishing a virtual private network between the enterprise network and the first virtual machine;
establishing a secure connection between the first virtual machine and a second virtual machine in the cloud provider network; and
executing plug-in network services on the first virtual machine.
25. The method of claim 24, further comprising the steps of:
enabling a client access agent on a device outside the enterprise network and cloud provider network;
connecting the device to a public network; and
establishing a virtual private network between the device and one or both of the first virtual machine and the second virtual machine.
26. A method for communicating with cloud accounts, the method comprising:
establishing a pseudo-hypervisor instance on an enterprise network;
configuring the pseudo-hypervisor instance to receive a hypervisor API call from an enterprise systems management tool on the enterprise network;
translating a received hypervisor API call into an intermediate representation;
routing the intermediate representation to a back-end plug-in;
translating the intermediate representation into a cloud API call; and
transmitting the cloud API call to a cloud provider network for delivery to a cloud account.
27. The method of claim 26, further comprising the step of verifying successful execution of the cloud API call.
28. The method of claim 27, further comprising the step of reporting verification information concerning the cloud API call to the pseudo-hypervisor instance.
29. The method of claim 28, further comprising the step of translating the verification information into a hypervisor-specific result code.
30. The method of claim 29, further comprising the step of reporting the hypervisor-specific result code to an enterprise systems management tool.

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 stitched in-stack stabilized CPP synthetic spin-valve sensor comprising:
a multi-layered pillar type synthetic spin-valve formation, said pillar being defined by a common and uniform lateral cross-section of all included layers and said formation having a longitudinally magnetized ferromagnetic free layer as its uppermost layer;
a decoupling layer formed on said free layer, said decoupling layer having the same lateral cross-sectional area as said spin-valve formation;
a longitudinal bias layer (LBL) formed on said decoupling layer, said LBL having the same lateral cross-section as said decoupling layer;
a multi-layer formation stitched onto said LBL, said formation being characterized by a larger lateral cross-section than said LBL and said formation including:
a synthetic exchange tri-layer formation;
an antiferromagnetic pinning layer formed on said tri-layer formation;
a capping and conducting lead layer formed on said pinning layer; and

wherein said tri-layered structure and said LBL are longitudinally magnetized and strongly exchange coupled to said free layer and, thereby, stabilize it.
2. The sensor of claim 1 wherein said synthetic spin-valve formation further comprises:
a seed layer;
an antiferromagnetic pinning layer formed on said seed layer;
a synthetic antiferromagnetic pinned layer formed on said pinning layer, said layer comprising a first (AP1) and a second (AP2) laminated ferromagnetic layer, wherein each said layer is magnetized in opposite directions transversely to the ABS of the sensor, said layers being separated by a non-magnetic layer;
a non-magnetic spacer layer formed on said pinned layer; and
a longitudinally magnetized ferromagnetic free layer formed on said spacer layer.
3. The sensor of claim 2 wherein said first ferromagnetic layer is the lamination CoFeCuCoFeCuCoFe, wherein the CoFe lamina are formed to a thickness between approximately 7 and 15 angstroms and the Cu lamina are formed to a thickness between approximately 1 and 4 angstroms.
4. The sensor of claim 2 wherein said second ferromagnetic layer is the lamination FeCoTaFeCoTaFeCo wherein the FeCo lamina are formed to a thickness between approximately 5 and 15 angstroms and the Ta lamina are formed to a thickness between approximately 0.5 and 3 angstroms.
5. The sensor of claim 1 wherein said decoupling layer is a tri-layer of non-magnetic materials comprising:
a first layer of Cu of thickness between approximately 4 and 6 angstroms;
a layer of Ta of thickness between approximately 4 and 15 angstroms;
a second layer of Cu of thickness between approximately 4 and 6 angstroms.
6. The sensor of claim 1 wherein said LBL is a layer of FeCo formed to a thickness between approximately 40 and 50 angstroms.
7. The sensor of claim 1 wherein said free layer is the lamination CoFeCuCoFeCuCoFe wherein the CoFe lamina are formed to a thickness between approximately 7 and 15 angstroms and the Cu lamina are formed to a thickness between approximately 1 and 4 angstroms.
8. The sensor of claim 1 wherein said synthetic exchange tri-layer formation comprises:
a first ferromagnetic layer, FM1, formed on said LBL;
a coupling layer formed on FM1;
a second ferromagnetic layer, FM2, formed on the coupling layer; and
FM1 and FM2 are longitudinally magnitized in antiparallel directions, FM1 and LBL are magnetized in the same direction and FM2 and said ferromagnetic layer are magnetized in the same direction.
9. The sensor of claim 8 wherein the magnetic thicknesses of FM1, FM2 and LBL satisfy the relationships: t(LBL)+t(FM1)<t(FM2) and t(LBL)+t(FM1)t(FM2)=7090 angstroms of CoFe.
10. The sensor of claim 8 wherein FM1 is a layer of FeCo formed to a thickness between approximately 5 and 20 angstroms, FM2 is a bilayer of CoFeFeCo, wherein the CoFe is formed to a thickness between approximately 60 and 90 angstroms and the FeCo is formed to a thickness between approximately 5 and 20 angstroms and the coupling layer is a layer of Ru formed to a thickness between approximately 3 and 5 angstroms.

1. Cable terminator (8), in particular outdoor terminator for an electrical cable (10) having a cable conductor (12), a cable insulation (14), a conductive layer (15) and a cable shield (11), the terminator (8) being mounted at one end on a base fitting (20), having means (18) on the base fitting (20) for fastening the cable (10),
having an electrical duct (32) in the interior of the terminator (8),
having a top fitting (70) for fastening an electrical conductor to the duct (32),
having means (30) for electrically connecting the cable shield (11) to earth potential,
having a field control device (34,36) and a field insulating device for the potential transitions at the cable end,
having an insulating body (50) and having means (23) for fastening the insulating body (50) to the base fitting (20), the electrical duct (32) being connected to the cable conductor (12) via contact elements (17,30), characterised in that the contacts (17,30) are designed as clamping elements, in that the insulating body (50) is filled up with material from the region of the fastening (23) to the base fitting (20) up to the level of the contacts (17) and
the filling is reduced towards the top fitting (70), such that an internal cavity (56) is formed, and
the insulating body (50) is designed to take up mechanical load on the terminator (8), and
in that the surface of the insulating body (50) is coated with a voltage-dependent field-controlling layer (64).
2. Cable terminator according to claim 1, characterised in that the field-controlling layer (64) is formed from microvaristors.
3. Cable terminator according to claim 2, characterised in that the microvaristors used are ZnO microvaristors.
4. Cable terminator according to one of the preceding claims, characterised in that the field-controlling layer (64) runs over the entire length of the insulating body (50).
5. Cable terminator according to one of the preceding claims, characterised in that the inner surface (54) of the cavity (56) bears a conductive coating (58).
6. Cable terminator according to one of the preceding claims, characterised in that the insulating body (50) is produced from cast resin.
7. Cable terminator according to one of the preceding claims, characterised in that the electrical duct (32) is designed as a tube.
8. Cable terminator according to one of the preceding claims, characterised in that the contact elements (17) on the cable conductor (14) are laminated contacts.

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 precombustion-chamber fuel supply device for a gas internal combustion engine of a Miller-cycle type, comprising:
a main chamber defined between a piston and a cylinder head of the gas internal combustion engine;
a precombustion chamber which communicates with the main chamber via a nozzle and in which fuel gas is combusted by a spark plug;
a gas supply channel to precombustion chamber for supplying the fuel gas to the precombustion chamber from a fuel-gas supply source;
a precombustion-chamber electromagnetic valve which controls the fuel gas flowing out from the fuel-gas supply source to the gas supply channel to precombustion chamber; and
a check valve disposed in the gas supply channel to precombustion chamber and configured to open due to a pressure decrease in the precombustion chamber at a bottom dead center of an intake stroke of a Miller cycle in which the piston closes an intake valve before the bottom dead center of the intake stroke so as to allow supply of the fuel gas to the precombustion chamber,
wherein the gas supply channel to precombustion chamber includes a check-valve insertion hole in which the check-valve is disposed and a flow-channel space defined inside a fuel-inlet connector which extends in a direction orthogonal to a center line of the check-valve insertion hole, the fuel-inlet connector being connected to the fuel-gas supply source via the precombustion-chamber electromagnetic valve.
4. The precombustion-chamber fuel supply device for a gas internal combustion engine according to claim 1,
wherein the check valve includes:
a check-valve body disposed in the check-valve insertion hole of the gas supply channel to precombustion chamber so as to define a check-valve upper chamber and a check-valve lower chamber in the check-valve insertion hole, the check-valve body including a through hole penetrating from the check-valve upper chamber to the check-valve lower chamber inside the check-valve body and a seal portion formed on a periphery of an opening of the through hole adjacent to the check-valve lower chamber;
a valve body including a column portion fitted into the through hole, a valve-body top portion formed on an end of the column portion adjacent to the valve-body lower chamber, and a stopper portion formed on an end of the column portion adjacent to the valve-body upper chamber; and
an elastic member which presses the valve-body top portion against the seal portion.
5. The precombustion-chamber fuel supply device for a gas internal combustion engine according to claim 4,
wherein a pressing force W of the elastic member is within a range of a following expression (1):
Q2\xd7Sa\u2212Q1\xd7Sb>W \u2003\u2003(1)
, where Q1 is a gas pressure in the precombustion chamber at the bottom dead center in the intake stroke; Q2 is a fuel-gas pressure of the gas supply channel to precombustion chamber; Sa is a fuel-gas pressure receiving area of the valve body; and Sb is a precombustion-chamber gas pressure receiving area of the valve body.
6. The precombustion-chamber fuel supply device for a gas internal combustion engine according to claim 1,
wherein a fuel-gas pressure of the gas supply channel to precombustion chamber is set to be lower than a gas pressure of the precombustion chamber in an exhaust stroke.
7. The precombustion-chamber fuel supply device for a gas internal combustion engine according to claim 4,
wherein the check-valve body further includes a plurality of communication channels each of which communicates with the through hole in a vicinity of the check-valve lower chamber and has an opening toward the check-valve upper chamber, the plurality of communication channels being disposed on an outer side of an outer circumferential rim of the through hole.