Author: claimsbot

1. A process comprising:
determining a state of a CPU-enabled flag during execution of an idle thread by a central processing unit (CPU) in a plurality of central processing units in a symmetric multiprocessor system; and
shutting down said CPU during execution of said idle thread, upon said determining said state of said CPU-enabled flag finding that said state indicates said CPU is not logically enabled.
2. The process of claim 1 further comprising:
changing said state of said CPU-enabled flag from a first state to a second state, wherein said second state indicates that said CPU is not logically enabled.
3. The process of claim 2 further comprising:
setting said state of said CPU-enabled flag to said first state, wherein said first state indicates that said CPU is logically enabled.
4. The process of claim 2 further comprising:
setting an execution priority of said idle thread to a high idle execution priority.
5. The process of claim 1 further comprising:
setting said state of said CPU-enabled flag to a first state, wherein said first state indicates that said CPU is logically enabled.
6. A process comprising:
setting an execution priority of an idle thread to a high idle execution priority;
determining a state of a CPU-enabled flag, during execution of said idle thread, by a central processing unit (CPU) corresponding to said CPU-enabled flag wherein said CPU is in a plurality of central processing units in a symmetric multiprocessor system; and
shutting down said CPU during execution of said idle thread, upon said determining said state of said CPU-enabled flag finding that said state indicates said CPU is not logically enabled.
7. A process comprising:
setting a state of a CPU-enabled flag to a first state, wherein said first state indicates that a central processing unit (CPU) corresponding to said CPU-enabled flag is logically enabled, and further wherein said CPU is in a plurality of central processing units in a symmetric multiprocessor system;
setting an execution priority of an idle thread to a low idle execution priority;
determining said state of said CPU-enabled flag during execution of said idle thread by said CPU; and
shutting down said CPU during execution of said idle thread, upon said determining said state of said CPU-enabled flag finding that said state indicates said CPU is not logically enabled.
8. The process to claim 7 further comprising:
changing said state of said CPU-enabled flag from said first state to a second state, wherein said second state indicates that said CPU is not logically enabled.
9. The process of claim 7 further comprising:
changing said execution priority of said idle thread from said low idle execution priority to a high idle execution priority.
10. A process comprising:
setting a state of a CPU-enabled flag to a first state, wherein said first state indicates that a central processing unit (CPU) corresponding to said CPU-enabled flag is logically enabled, and further wherein said CPU is in a plurality of central processing units in a symmetric multiprocessor system;
setting an execution priority of an idle thread to a low idle execution priority;
changing said state of said CPU-enabled flag from said first state to a second state, wherein said second state indicates that said CPU is not logically enabled;
changing said execution priority of said idle thread from said low idle execution priority to a high idle execution priority;
determining a state of said CPU-enabled flag during execution of said idle thread by said CPU; and
shutting down said CPU during execution of said idle thread, upon said determining said state of said CPU-enabled flag finding that said state indicates said CPU is not logically enabled.
11. A process comprising:
determining an execution priority of an idle thread during execution of said idle thread by a central processing unit (CPU) in a plurality of central processing units in a symmetric multiprocessor system;
changing said execution priority from a normal idle execution priority to a shutdown priority; and
shutting down said CPU during execution of said idle thread, upon said determining said execution priority finding that said execution priority of said idle thread is said shutdown priority.
12. A structure comprising:
a plurality of central processing units in a symmetric multiprocessing system; and
a memory system coupled to said plurality of central processing units, said memory system further comprising:
a plurality of CPU-enabled flags wherein when a CPU-enabled flag for a central processing unit (CPU) has a first state, the CPU is logically enabled, and when said CPU-enabled flag for said CPU has a second state, the CPU is not logically enabled; and
a queue including control blocks for executable threads, wherein said control blocks includes control blocks for idle threads and further wherein at least one of said control blocks for idle threads has a high idle execution priority.
13. A structure comprising:
a plurality of central processing units in a symmetric multiprocessing system; and
means for safely shutting down a central processing unit in said plurality of central processing units, said means further comprising:
means for setting an execution priority of an idle thread to other than a lowest priority.
14. The structure of claim 13 wherein said means for safely shutting down a central processing unit further comprises:
means for identifying a logically enabled state of said central processing unit.
15. The structure of claim 14 wherein said means for identifying a logically enabled state of said central processing unit is included in an idle thread executed by said central processing unit.
16. The structure of claim 13 wherein said means for setting an execution priority of an idle thread is included in a heuristic procedure executed by said central processing unit.
17. A process comprising:
assigning a first execution priority to one idle thread executed in a symmetric multiprocessor system wherein execution of said one idle thread with said first execution priority by a central processing unit in said symmetric multiprocessor system results in said central processing unit idling; and
assigning a second execution priority, different from said first execution priority, to said idle thread wherein execution of said idle thread with said second execution priority results in shutting down said central processing unit.
18. The process of claim 17 further comprising
assigning uninterruptible threads an execution priority higher than said second execution priority.
19. The process of claim 17 further comprising
assigning user mode tasks an execution priority between said first and second execution priorities.
20. A process comprising:
assigning a first execution priority to one idle thread executed in a symmetric multiprocessor system wherein execution of said one idle thread with said first execution priority by a central processing unit in said symmetric multiprocessor system results in said central processing unit idling;
assigning a second execution priority, different from said first execution priority, to said idle thread wherein execution of said idle thread with said second execution priority results in shutting down said central processing unit;
assigning uninterruptible threads an execution priority higher than said second execution priority; and
assigning user mode tasks an execution priority between said first and second execution priorities.

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 lighting system comprising:
an electric lamp (1), which has a first (11) and at least one second lamp filament (12);
an electronic ballast (2), which is electrically connected to the lamp filaments (11, 12); and
at least two further light sources (31a to 31c; 32a to 32c), which are connected in a parallel circuit (3) with one another,
wherein the parallel circuit (3) comprising the two further light sources (31a to 31c; 32a to 32c) is connected in series between the first (11) and the second lamp filament (12).
2. The lighting system as claimed in claim 1, wherein the at least two further light sources (31a to 31c; 32a to 32c) are electrically connected to a first terminal (11a) of the first lamp filament (11) and a first terminal (12a) of the second lamp filament (12).
3. The lighting system as claimed in claim 1, wherein, the electronic ballast (2) is electrically connected to a second terminal (11b) of the first lamp filament (11) and to a second terminal (12b) of the second lamp filament (12).
4. The lighting system as claimed in claim 1, wherein the two further light sources (31a to 31c; 32a to 32c) are in the form of LEDs and are connected in phase opposition to one another into the respective signal paths (31, 32) of the parallel circuit (3).
5. The lighting system as claimed in claim 1, wherein a lamp filament preheating means (4) is connected in series with the parallel circuit (3) comprising the two further light sources (31a to 31c; 32a to 32c).
6. The lighting system as claimed in claim 5, wherein the lamp filament preheating means (4) is electrically connected to the first terminal (12a) of the second lamp filament (12).
7. The lighting system as claimed in claim 5, wherein the lamp filament preheating means (4) has a reactance (41), in particular a capacitor.
8. The lighting system as claimed in claim 1, wherein a switch (5) is connected in parallel with the parallel circuit (3) comprising the further light sources (31a to 31c; 32a to 32c).
9. The lighting system as claimed in claim 1, wherein a reactance (6), is connected in parallel with the parallel circuit (3) comprising the further light sources (31a to 31c; 32a to 32c).
10. The lighting system as claimed in claim 9, wherein said reactance is a capacitor.

1. A coated article, comprising:
a substrate being made of aluminum alloy or magnesium alloy;
an anti-corrosion layer formed on the substrate, the anti-corrosion layer being an amorphous alloy layer and containing about 68% to about 72% of iron, about 8% to about 12% of chromium, about 10% to about 14% of boron, and about 2% to about 14% of M by atomic percentage; and
a decorative layer directly formed on and contacting the anti-corrosion layer;
wherein M being one or more selected from the group consisting of phosphorus, carbon and silicon.
2. The coated article as claimed in claim 1, wherein the anti-corrosion layer has a thickness of about 800 nm to about 1200 nm.
3. The coated article as claimed in claim 1, wherein the decorative layer is composed of a compound selected from the group consisting of carbide of titanium, chromium or zirconium, nitride of titanium, chromium or zirconium, and oxide of titanium, chromium or zirconium.
4. The coated article as claimed in claim 1, wherein the decorative layer has a thickness of about 400 nm to about 600 nm.

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 computer-implemented method for converting authentication-tokens, comprising:
receiving, at a computer, a command-execution request from a first application, wherein the command-execution request specifies a command to be executed by a second application and includes a first authentication-token that is created by the first application based on a user authenticating to the first application;
verifying the first authentication-token at the computer;
translating the first authentication-token to a form associated with the second application to produce a second authentication-token, wherein the second authentication-token is in a form different than the first authentication-token;
modifying the command-execution request by replacing the first authentication-token with the second authentication-token to create a modified command-execution request; and
sending the modified command-execution request to the second application,
wherein the command-execution request includes a target Uniform Resource Locator (URL) which specifies a location of the second application, a second authentication-token type which specifies a form of the second authentication-token, a user identifier for a user who is associated with the first authentication-token, and payload data for the second application.
2. The method of claim 1, wherein the first application is located on the same computer system as the second application.
3. The method of claim 1, wherein the command-execution request comprises a first authentication-token type which specifies a form of the first authentication-token.
4. The method of claim 1, wherein verifying the first authentication-token further comprises:
identifying a first authentication-token type for the first authentication-token;
using decryption rules associated with the first authentication-token type to decrypt the first authentication-token to produce a decrypted first authentication-token; and
verifying the validity of the decrypted first authentication-token.
5. The method of claim 4, wherein verifying the validity of the decrypted first authentication-token can involve:
verifying that the decrypted first authentication-token has not expired; and
verifying that the decrypted first authentication-token is associated with a user identifier.
6. The method of claim 1, wherein translating the first authentication-token further comprises:
identifying the second authentication-token type;
identifying a second user identifier which is mapped from the user identifier; and
creating the second authentication-token associated with the second user identifier, wherein the second authentication-token is of the form specified by the second-authentication-token type.
7. The method of claim 6, wherein creating the second authentication-token can involve:
requesting the second authentication-token from a third-party authentication-token provider; and
receiving the second authentication-token from the third-party authentication-token provider.
8. The method of claim 6, wherein the second user identifier comprises the user identifier.
9. The method of claim 1, wherein the first authentication-token and the second authentication-token include one or more of:
a cookie;
a digital certificate;
a user-namepassword pair;
a cryptographic key; and
a biometric identifier.
10. The method of claim 1, wherein modifying the command-execution request further comprises:
modifying a format of the command to a format associated with the second application; and
including the modified command with the modified command-execution request.
11. A non-transitory computer-readable storage medium storing instructions that when executed by a computer cause the computer to perform a method for converting authentication-tokens, the method comprising:
receiving, at a bridge, a command-execution request from a first application, wherein the command-execution request specifies a command to be executed by a second application and includes a first authentication-token that is created by the first application based on a user authenticating to the first application;
verifying the first authentication-token at the bridge;
translating the first authentication-token to a form associated with the second application to produce a second authentication-token, wherein the second authentication-token is in a form different than the first authentication-token;
modifying the command-execution request by replacing the first authentication-token with the second authentication-token to create a modified command-execution request; and
sending the modified command-execution request to the second application,
wherein the command-execution request includes a target Uniform Resource Locator (URL) which specifies a location of the second application, a second authentication-token type which specifies a form of the second authentication-token, a user identifier for a user who is associated with the first authentication-token, and payload data for the second application.
12. The computer-readable storage medium of claim 11, wherein the first application is located on the same computer system as the second application.
13. The computer-readable storage medium of claim 11, wherein the command-execution request comprises a first authentication-token type which specifies a form of the first authentication-token.
14. The computer-readable storage medium of claim 11, wherein verifying the first authentication-token further comprises:
identifying a first authentication-token type for the first authentication-token;
using decryption rules associated with the first authentication-token type to decrypt the first authentication-token to produce authentication-token; and
verifying the validity of the decrypted first authentication-token.
15. The computer-readable storage medium of claim 14, wherein verifying the validity of the decrypted first authentication-token can involve:
verifying that the decrypted first authentication-token has not expired; and
verifying that the decrypted first authentication-token is associated with a user identifier.
16. The computer-readable storage medium of claim 11, wherein translating the first authentication-token further comprises:
identifying the second authentication-token type;
identifying a second user identifier which is mapped from and the user identifier; and
creating the second authentication-token associated with the second user identifier, wherein the second authentication-token is of the form specified by the second-authentication-token type.
17. The computer-readable storage medium of claim 16, wherein creating the second authentication-token can involve:
requesting the second authentication-token from a third-party authentication-token provider; and
receiving the second authentication-token from the third-party authentication-token provider.
18. The computer-readable storage medium of claim 16, wherein the second user identifier comprises the user identifier.
19. The computer-readable storage medium of claim 11, wherein the first authentication-token and the second authentication-token include one or more of:
a cookie;
a digital certificate;
a user-namepassword pair;
a cryptographic key; and
a biometric identifier.
20. The computer-readable storage medium of claim 11, wherein modifying the command-execution request further comprises:
modifying a format of the command to a format associated with the second application; and
including the modified command with the modified command-execution request.
21. An apparatus that converts authentication-tokens, comprising:
a receiving mechanism configured to receive, at a bridge, a command-execution request from a first application, wherein the command-execution request specifies a command to be executed by a second application and includes a first authentication-token that is created by the first application based on a user authenticating to the first application;
a verification mechanism configured to verify the first authentication token at the bridge;
a translation mechanism configured to translate the first authentication-token to a form associated with the second application to produce a second authentication-token, wherein the second authentication-token is in a form different than the first authentication-token;
a modification mechanism configured to modify the command-execution request by replacing the first authentication-token with the second authentication-token to create a modified command-execution request; and
a sending mechanism configured to send the modified command-execution request to the second application,
wherein the command-execution request includes a target Uniform Resource Locator (URL) which specifies a location of the second application, a second authentication-token type which specifies a form of the second authentication-token, a user identifier for a user who is associated with the first authentication-token, and payload data for the second application.
22. The apparatus of claim 21, wherein the verification mechanism further comprises:
an identification mechanism configured to identify a first authentication-token type for the first authentication-token;
a decryption mechanism configured to use decryption rules associated with the first authentication-token type to decrypt the first authentication-token to produce a decrypted first authentication-token; and
a second verification mechanism configured to verify the validity of the decrypted first authentication-token.
23. The apparatus of claim 21, wherein the translation mechanism further comprises:
an identification mechanism configured to identify the second authentication-token type;
a second identification mechanism configured to identify a second user identifier which is mapped from and the user identifier; and
a creation mechanism configured to create the second authentication-token associated with the second user identifier, wherein the second authentication-token is of the form specified by the second-authentication-token type.
24. The apparatus of claim 22, wherein the second verification mechanism is further configured to:
verify that the decrypted first authentication-token has not expired; and to
verify that the decrypted first authentication-token is associated with a user identifier.
25. The apparatus of claim 23, wherein the creation mechanism further comprises:
a requesting mechanism configured to request the second authentication-token from a third-party authentication-token provider; and
a receiving mechanism configured to receive the second authentication-token from the third-party authentication-token provider.
26. The apparatus of claim 21, wherein the modification mechanism is further configured to:
modify a format of the command to a format associated with the second application; and to
include the modified command with the modified command-execution request.