1461106765-38cd19cb-935a-4680-b532-f0e31215a3e6

1. A fluid power fluid cylinder and more particularly a pneumatic power cylinder, comprising
a cylinder housing (2) containing therein a piston receiving space (6) in which a piston (8) able to be moved by fluid actuation is arranged, which is kinematically coupled with a piston rod (14) extending out at the front end of the cylinder housing (14),
a control system housing (33) mounted on the rear end of the cylinder housing, which system housing contains control components (34) cooperating for control of fluid actuation of the piston (8), such control components including an electrically actuated valve means (44) and furthermore electronic valve circuitry andor electronic control circuitry (58) cooperating in the electrical control of the valve means (44),
electrical connection means (63) provided externally on the control system housing (33) for the supply of electrical control signals, which electrical connection means (63) are connected in the control housing (33) with electronic valve circuitry andor electronic control circuitry (58),
and fluid connection means (48) provided externally on the control system housing (33) for the supply of an actuating fluid, which electrical connection means (48) are connected with the valve means (44), whence control ducts (17 and 18) emerge, which extend in the wall of the cylinder housing (4) to the piston receiving space (6).
2. The fluid power cylinder as set forth in claim 1, characterized in that the outline of the control system housing (33) does not project past the outline of the axially adjoining cylinder housing (2).
3. The fluid power cylinder as set forth in claim 1 or in claim 2, characterized in that the cylinder housing (2) and the control system housing (33) possess essentially similar rectangular and preferably square outlines.
4. The fluid power cylinder as set forth in any of the claims 1 through 3, characterized in that on the cylinder housing (2) sensor means (26 and 27) are provided in the peripheral part of the piston receiving space (6) for detecting the position of the piston (8), and electrical sensor signal lines (77) extend from such sensor means and into the control system housing (33).
5. The fluid power cylinder as set forth in claim 4, characterized in that the sensor means (26 and 27) and the sensor signal lines (77) are accommodated in sensor grooves (32) provided on the outer periphery of the cylinder housing (2) and preferably in such a manner that same do not extend past the outline of the cylinder housing (2).
6. The fluid power cylinder as set forth in claim 4 on claim 5, characterized in that the electrical sensor signal lines (77) extend in the transition zone between the cylinder housing (2) and the control system housing (33) through an opening (76) turned toward the cylinder housing (2), of the control system housing into the interior space (37) in the control system housing (33).
7. The fluid power cylinder as set forth in any one of the claims 4 through 6, characterized in that the sensor signal lines (77) are connected in the interior of the control system housing (33) with the electronic valve circuitry andor electronic control circuitry (58) or directly with the electrical connection means (63).
8. The fluid power cylinder as set forth in any one of the claims 1 through 7, characterized in that the control system housing (33) has at least one, preferably laterally placed access opening (65, 72 and 74), which is sealed off by a removable housing cover (66, 73 and 75).
9. The fluid power cylinder as set forth in claim 8, characterized in that a housing cover (66) constitutes a support for the electronic valve circuitry andor electronic control circuitry (58) arranged on the inner side of the support.
10. The fluid power cylinder as set forth in claim 9, characterized in that the electronic valve circuitry andor electronic control circuitry (58) is provided on a printed circuit board (68) with electronic circuitry mounted on the inner side of the respective housing cover (68).
11. The fluid power cylinder as set forth in any one of the claims 1 through 10, characterized in that on the side the control system housing (63) has a plurality of access openings (65, 72 and 74) arranged about the periphery and closed by detachable housing covers (66, 73 and 75), one opening (72) being opposite to the electrical drive means (57) of the valve means (44) and a further access opening (65) being arranged adjacent to the electronic valve circuitry andor electronic control circuitry (58).
12. The fluid power cylinder as set forth in any one of the claims 1 through 11, characterized in that the electronic control circuitry (58) comprises a field bus electronic system.
13. The fluid power cylinder as set forth in any one of the claims 1 through 12, characterized in that the electrical connection means (63) on the control system housing (33) are in the form of a field bus connection.
14. The fluid power cylinder as set forth in any one of the claim 1 through 14, characterized in that the control system housing (33) is pot-like and has a floor (68) and a side wall (42) and with the open side, opposite to the floor (38) to the fore, is mounted on the rear side of the cylinder housing (2).
15. The fluid power cylinder as set forth in any one of the claims 1 through 14, characterized in that the valve means (44) extend between the rear end face (24) of the cylinder housing (2) and an inner face (46) of the housing, opposite to such end face (24), of the control system housing (33) and is held on such faces.
16. The fluid power cylinder as set forth in claim 15, characterized in that the valve means (44) possesses plug dowels (47), which are fitted in holding openings (49) in the rear end face (24 of the cylinder housing (2) and in the housing’s inner face (46) facing same, in the control system housing (33) in an interlocking manner.
17. The fluid power cylinder as set forth in claim 15 or claim 16, characterized in that the housing’s inner face (46) is constituted by the inner face of the floor (38) of the pot-like control system housing (33).
18. The fluid power cylinder as set forth in any one of the claims 1 through 17, characterized in that the fluid connection means (48) are provided on the rear side, facing away from the cylinder housing (2) of the control system housing (33).
19. The fluid power cylinder as set forth in any one of the claims 1 through 18, characterized by a design in the form of a pneumatic fluid power cylinder, in the case of which all venting openings (53) are provided at the rear side, facing away from the cylinder housing (2) of the control system housing (33).
20. The fluid power cylinder as set forth in claim 19, characterized in that each venting opening (53) is fitted with a muffler (55) and preferably a muffler with an integral venting choke means.
21. The fluid power cylinder as set forth in any one of the claims 1 through 20, characterized in that the valve means (44) comprises a four way valve or a five way valve or two three way valves.

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 of device tracking, comprising:
detecting, by a server, a request from a client device to visit a third-party content supplier in association with a redirection instruction;
identifying, by the server and in response to the request, device information associated with the client device, location information associated with the client device, and a time of the request;
generating, by the server, a first time-dependent identifier for the client device using the device information, the location information, and the time of the request;
monitoring, by the server, accesses to content provided by the third-party content supplier; and
associating, by the server, an access to a piece of content provided by the third-party content supplier with the request based on the first time-dependent identifier corresponding to a second time-dependent identifier associated with the access to the piece of content.
2. The method as recited in claim 1, further comprising:
identifying, by the server and in response to the access, device information associated with a device that accessed the piece of content, location information associated with the device that accessed the piece of content, and a of the access to the piece of content; and
generating, by the server, the second time-dependent identifier using the device information associated with the device that accessed the piece of content, location information associated with the device that accessed the piece of content, and a time of the access to the piece of content.
3. The method as recited in claim 2, further comprising:
comparing the first time-dependent identifier to the second time dependent identifier; and
determining that the first-time dependent identifier matches the second time dependent identifier.
4. The method as recited in claim 3, wherein:
the request is in connection with a request to download an application;
the third-party content supplier comprises a third-party application store; and
the redirection instruction comprises an application switch instruction to the third-party application store to allow for downloading of the application.
5. The method as recited in claim 4, wherein monitoring, by the server, accesses to content provided by the third-party content supplier comprises receiving, from client devices, indications of launches of the application.
6. The method as recited in claim 1, wherein generating, by the server, the first time-dependent identifier for the client device using the time of the request comprises:
truncating the time of the request; and
generating a time window for the first time dependent identifier based on the truncated time of the request.
7. The method as recited in claim 6, wherein truncating the time of the request further comprises:
removing at least one digit from an epoch time of the request;
dividing a remaining final digit of the epoch time by a predetermined number; and
rounding the final digit of the epoch time down to a closest integer.
8. The method as recited in claim 7, further comprising assigning the first time-dependent identifier to one of a plurality of identifier groups based on the final digit of the epoch time and the predetermined number.
9. The method as recited in claim 1, wherein determining the device information associated with the client device comprises determining at least one of an operating system version for the client device or a device type for the client device.
10. The method as recited in claim 1, wherein determining the location information associated with the client device comprises determining a truncated Internet Protocol address for the client device.
11. The method as recited in claim 1, wherein the first time-dependent identifier further comprises an application identifier for an application associated with the redirection instruction.
12. The method as recited in claim 1, wherein generating the first time-dependent identifier comprises:
generating a concatenated number by combining a number representing the device information associated with the client device, a number representing the location information associated with the client device, and a number representing the time of the request; and
performing a hash on the concatenated number.
13. A method of device identification, comprising:
detecting, by a server, an initial event performed by a first client device;
identifying, by the server and in response to the initial event, device information associated with the first client device, location information associated with the first client device at a time of the initial event, and a time of the initial event;
identifying a time period associated with the time of the initial event;
detecting, by the server, a plurality of subsequent events associated with one or more client devices; and
associating, by the server, a particular subsequent event, of the plurality of subsequent events, with the initial event based on device information associated with the particular subsequent event corresponding to the device information associated with the first client device, location information associated with the particular subsequent event corresponding to the location information associated with the first client device, and a time of the particular subsequent event being within the identified time period.
14. The method as recited in claim 13, further comprising generating a first time-dependent identifier based on the device information associated with the first client device, location information associated with the first client device at the time of the initial event, and the time of the initial event.
15. The method as recited in claim 14, wherein generating the first time-dependent identifier further comprises:
truncating the time of the initial event; and
generating the time period based on the truncated time of the initial event.
16. The method as recited in claim 13, wherein the initial event corresponds to a request from the first client device to visit a third-party content supplier for downloading an application, and the particular subsequent event corresponds to a launch of the application.
17. The method as recited in claim 13, further comprising:
determining that the first time-dependent identifier corresponds to a second time-dependent identifier associated with the particular event; and
associating the first client device with a campaign corresponding to the initial event.
18. A system for device tracking, comprising:
at least one processor;
at least one non-transitory computer readable storage medium storing instructions thereon, that, when executed by the at least one processor, cause the system to:
detect, at a server, a request from a client device to visit a third-party content supplier in association with a redirection instruction;
identify, by the server and in response to the request, device information associated with the client device, location information associated with the client device, and a time of the request;
generate, by the server, a first time-dependent identifier for the client device using the device information, the location information, and the time of the request;
monitor, by the server, accesses to content provided by the third-party content supplier; and
associate, by the server, an access to a piece of content provided by the third-party content supplier with the request based on the first time-dependent identifier corresponding to a second time-dependent identifier associated with the access to the piece of content.
19. The system as recited in claim 18, further comprising:
truncating the time of the request; and
generating a valid time window for the first time dependent identifier based on the truncated request time.
20. The system as recited in claim 19, wherein truncating the request time further comprises:
removing at least one digit from an epoch time associated with the request;
dividing a remaining final digit of the epoch time by a predetermined number; and rounding the final digit of the epoch time down to a closest integer.