Author: claimsbot

1. A method for the treatment of inflammatory bowel disease due to bacterial infection comprising administering daily, for a period of at least 120 days, a composition comprising:
an amount of an antibiotic effective to reduce colonization of pathogenic bacteria in the gastrointestinal tract, said antibiotic comprising a combination of sulfamethoxazole and trimethoprim, and
a probiotic formulation in an amount effective to restore normal microflora colonies in the gut, said probiotic formulation including live cells from at least one strain selected from the group consisting of Arthrobacter agilis, Arthrobacter citreus, Arthrobacter globiformis, Arthrobacter leuteus, Arthrobacter simplex, Azotobacter chroococcum, Azotobacter paspali, Azospirillum brasiliencise, Azospriliium lipoferum, Bacillus brevis, Bacillus macerans, Bacillus pumilus, Bacillus polymyxa, Bacillus subtilis, Bacteroides lipolyticum, Bacteroides succinogenes, Brevibacterium lipolyticum, Brevibacterium stationis, Bacillus laterosporus, Bacillus bifidum, Bacillus laterosporus, Bifidophilus infantis, Streptococcus thermophilous, Bifodophilus longum, Bifidobacteria animalis, Bifidobacteria bifidus, Bifidobacteria breve, Bifidobacteria longum, Kurtha zopfil, Lactobacillus paracasei, Lactobacillus acidophilus, Lactobacillus planetarium, Lactobacillus salivarius, Lactobacillus rueteri, Lactobacillus bulgaricus, Lactobacillus helveticus, Lactobacillus casei, Lactobacillus rhamnosus, Lactobacillus sporogenes, Lactococcus lactis, Myrothecium verrucaris, Pseudomonas calcis, Pseudomonas dentrificans, Pseudomonas flourescens, Pseudomonas glathei, Phanerochaete chrysosporium, Saccharomyces boulardii, Streptomyces fradiae, Streptomyces cellulosae, Streptomyces griseoflavus, and combinations thereof.
2. The method according to claim 1, wherein said sulfamethoxazole is administered in a dose from about 400 mg to about 2,400 mg daily and said trimethoprim is administered in a dose from 80 mg to about 480 mg daily.
3. The method according to claim 2, wherein said sulfamethoxazole is administered in a dose of about 1,600 mg daily and said trimethoprim is administered in a dose of about 360 mg daily.
4. The method according to claim 1, wherein at least 20 billion probiotic cells are administered daily.
5. The method according to claim 1, wherein at least 40 billion probiotic cells are administered daily.
6. The method according to claim 1, wherein said probiotic formulation includes Bifidobacterium bifidum.
7. The method according to claim 1, wherein said probiotic formulation includes Bifidobacterium breve.
8. The method according to claim 1, wherein said probiotic formulation includes Bifidobacterium infantis.
9. The method according to claim 1, wherein said probiotic formulation includes Bifidobacterium longum.
10. The method according to claim 1, wherein said probiotic formulation includes Saccharomyces boulardii.
11. The method according to claim 1, wherein said probiotic formulation includes Lactobacillus acidophilus.
12. The method according to claim 1, wherein said probiotic formulation includes Lactobacillus bulgaricus.
13. The method according to claim 1, wherein said probiotic formulation includes Lactobacillus paracasei.
14. The method according to claim 1, wherein said amount of probiotic formulation is sufficient to provide a daily dose of:
about 5 billion cells of Bifidobacterium bifidum;
about 2 billion cells of Bifidobacterium breve;
about 2 billion cells of Bifidobacterium infantis;
about 2 billion cells of Bifidobacterium longum;
about 5 billion cells of Lactobacillus acidophilus;
about 500 million cells of Lactobacillus bulgaricus;
about 2 billion cells of Lactobacillus paracasei; and
about 2.5 billion cells of Saccharomyces boulardii.
15. The method according to claim 1, wherein said amount of probiotic formulation is sufficient to provide a daily dose of:
about 10 billion cells of Bifidobacterium bifidum;
about 4 billion cells of Bifidobacterium breve;
about 4 billion cells of Bifidobacterium infantis;
about 4 billion cells of Bifidobacterium longum;
about 10 billion cells of Lactobacillus acidophilus;
about 1 billion cells of Lactobacillus bulgaricus;
about 4 billion cells of Lactobacillus paracasei; and
about 5 billion cells of Saccharomyces boulardii.
16. The method according to claim 1, wherein said inflammatory bowel disease is ulcerative colitis.
17. The method according to claim 16, wherein said ulcerative colitis is active.
18. The method according to claim 16, wherein said ulcerative colitis is in remission.
19. The method according to claim 1, wherein said inflammatory bowel disease is Crohn’s disease.
20. The method according to claim 19, wherein said Crohn’s disease is active.
21. The method according to claim 19, wherein said Crohn’s disease is in remission.
22. The method according to claim 1, wherein treatment of said inflammatory bowel disease is carried out in the absence of an immunosuppressant or immunomodulatory drug.
23. The method according to claim 22, wherein said immunosuppressant or immunomodulatory drugs are selected from the group consisting of azathioprine, methotrexate, and 6-mercaptopurine.
24. The method according to claim 1, wherein said treatment period is at least about 180 days.
25. The method according to claim 1, further comprising daily administration of an aminosalicylate.
26. The method according to claim 25, wherein said aminosalicylate is mesalamine.
27. The method according to claim 1, further comprising administration of at least 1,000 mg of omega-3 fatty acids daily.
28. The method according to claim 27, wherein said omega-3 fatty acids comprise eicosapentaenoic acid (EPA) and docosahexaenoic acid (DHA).
29. The method according to claim 1, wherein prophylactic treatment is continued for an additional period from 120 to 180 days following remission of symptoms.
30. The method according to claim 29, wherein the dose of antibiotic drug is reduced following remission of symptoms.
31. The method according to claim 30, wherein the dose of antibiotic drug is reduced by half following remission of symptoms.
32. The method according to claim 1, wherein said treatment period is at least about 150 days.
33. The method according to claim 1, wherein said antibiotic is substantially released in the small intestine, and wherein said probiotic formulation is released upon contact with fluid in the stomach.

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, comprising:
determining, for each non-security component of an application, (a) types of interactions the non-security component has with security components of the application for a plurality of requests and a total number for each interaction type;
determining, based on (a) and an expected number of incoming requests to the application: (b) types of requests to the security components from the non-security components and types of interactions with the security components involving the non-security components; and (c) for each type of request to the security components from the non-security components, a total number of requests to the security components involving the non-security components and a total number of interactions with the security components involving the non-security components;
determining, for each security component, a capacity required to process each type of request involving the non-security components and a capacity required to perform each type of interaction involving the non-security components; and
changing the capacities of the security components to new capacities, wherein the new capacities are based on (a), (c) and the determined capacities.
2. The method of claim 1, wherein (a) is determined by analyzing code of the security and non-security components, non-functional or functional subsystems associated with the application that interact with a security component or influence the load on at least one of the security components, configuration information of the security and non-security components, a workflow of the application and deployment parameters of the application.
3. The method of claim 1, wherein the capacity required to perform each type of interaction involving the non-security components and a security component is determined by analyzing the capacities required to process each type of request involving the non-security components and a security component, the current load on the application, the expected load on the application due to the incoming requests, and service level agreement (SLA) and quality of service (QoS) parameters of the application.
4. The method of claim 1, wherein the load on a specific security component is computed using SLA and QoS parameters of the application.
5. The method of claim 1, wherein changing the capacities of the security components to the new capacities includes increasing or decreasing the total number of security components.
6. The method of claim 1, wherein changing the capacities of the security components to the new capacities includes increasing or decreasing internal capacities of the security components or capacities of the infrastructure and components on which the security components depend.
7. A computer program product, comprising:
a non-transitory computer readable storage medium having computer readable program code embodied therewith, the computer readable program code comprising:
computer readable program code configured to determine, for each non-security component of an application, (a) types of interactions the non-security component has with security components of the application for a plurality of requests and a total number for each interaction type;
computer readable program code configured to determine, based on (a) and an expected number of incoming requests to the application: (b) types of requests to the security components from the non-security components and types of interactions with the security components involving the non-security components; and (c) for each type of request to the security components from the non-security components, a total number of requests to the security components involving the non-security components and a total number of interactions with the security components involving the non-security components;
computer readable program code configured to determine, for each security component, a capacity required to process each type of request involving the non-security components and a capacity required to perform each type of interaction involving the non-security components; and
computer readable program code configured to change the capacities of the security components to new capacities, wherein the new capacities are based on (a), (c) and the determined capacities.
8. The computer program product of claim 7, wherein (a) is determined by analyzing code of the security and non-security components, non-functional or functional subsystems associated with the application that interact with a security component or influence the load on at least one of the security components, configuration information of the security and non-security components, a workflow of the application and deployment parameters of the application.
9. The computer program product of claim 7, wherein the capacity required to perform each type of interaction involving the non-security components and a security component is determined by analyzing the capacities required to process each type of request involving the non-security components and a security component, the current load on the application, the expected load on the application due to the incoming requests, and service level agreement (SLA) and quality of service (QoS) parameters of the application.
10. The computer program product of claim 7, wherein the load on a specific security component is computed using SLA and QoS parameters of the application.
11. The computer program product of claim 7, wherein the capacities of the security components are changed to the new capacities by increasing or decreasing the total number of security components.
12. The computer program product of claim 7, wherein changing the capacities of the security components to the new capacities includes increasing or decreasing internal capacities of the security components or capacities of the infrastructure and components on which the security components depend.
13. A system, comprising:
a memory device for storing a program; and
a processor in communication with the memory device, the processor operative with the program to:
determine, for each non-security component of an application, (a) types of interactions the non-security component has with security components of the application for a plurality of requests and a total number for each interaction type;
determine, based on (a) and an expected number of incoming requests to the application: (b) types of requests to the security components from the non-security components and types of interactions with the security components involving the non-security components; and (c) for each type of request to the security components from the non-security components, a total number of requests to the security components involving the non-security components and a total number of interactions with the security components involving the non-security components;
determine, for each security component, a capacity required to process each type of request involving the non-security components and a capacity required to perform each type of interaction involving the non-security components; and
change the capacities of the security components to new capacities, wherein the new capacities are based on (a), (c) and the determined capacities.
14. The system of claim 13, wherein (a) is determined by analyzing code of the security and non-security components, non-functional or functional subsystems associated with the application that interact with a security component or influence the load on at least one of the security components, configuration information of the security and non-security components, a workflow of the application and deployment parameters of the application.
15. The system of claim 13, wherein the capacity required to perform each type of interaction involving the non-security components and a security component is determined by analyzing the capacities required to process each type of request involving the non-security components and a security component, the current load on the application, the expected load on the application due to the incoming requests, and service level agreement (SLA) and quality of service (QoS) parameters of the application.
16. The system of claim 13, wherein the load on a specific security component is computed using SLA and QoS parameters of the application.
17. The system of claim 13, wherein the capacities of the security components are changed to the new capacities by increasing or decreasing the total number of security components.
18. The system of claim 13, wherein changing the capacities of the security components to the new capacities includes increasing or decreasing internal capacities of the security components or capacities of the infrastructure and components on which the security components depend.
19. A method, comprising:
determining, for each functional component of an application, (a) types of interactions the functional component has with non-functional components of the application for a plurality of requests and a total number for each interaction type;
determining, based on (a) and an expected number of incoming requests to the application: (b) types of requests to the non-functional components from the functional components and types of interactions with the non-functional components involving the functional components; and (c) for each type of request to the non-functional components from the functional components, a total number of requests to the non-functional components involving the functional components and a total number of interactions with the non-functional components involving the functional components;
determining, for each non-functional component, a capacity required to process each type of request involving the functional components and a capacity required to perform each type of interaction involving the functional components; and
changing the capacities of the non-functional components to new capacities, wherein the new capacities are based on (a), (c) and the determined capacities.
20. The method of claim 19, wherein a functional component includes a non-security component and a non-functional component includes a security component.

1. A semiconductor device comprising:
a semiconductor layer having an opening over an insulating surface;
a first insulating layer over the semiconductor layer;
a gate electrode over the first insulating layer;
a second insulating layer over the gate electrode; and
a conductive layer over the second insulating layer,
wherein at least a part of the opening reaches the insulating surface, and
wherein the conductive layer is connected to a side surface of the semiconductor layer and a top surface of the semiconductor layer.
2. The semiconductor device according to claim 1, wherein the semiconductor layer is a single crystal silicon layer.
3. The semiconductor device according to claim 1, wherein the semiconductor layer comprise a silicide region.
4. The semiconductor device according to claim 1, wherein a thickness of the semiconductor layer is 10 to 200 nm.
5. The semiconductor device according to claim 1, wherein the conductive layer comprises tungsten.
6. A semiconductor device comprising:
a semiconductor layer having an opening over an insulating surface;
a first insulating layer over the semiconductor layer;
a gate electrode over the first insulating layer;
a second insulating layer over the gate electrode; and
a conductive layer over the second insulating layer,
wherein the conductive layer is connected to the insulating surface through the opening, and
wherein the conductive layer is connected to a side surface of the semiconductor layer and a top surface of the semiconductor layer.
7. The semiconductor device according to claim 6, wherein the semiconductor layer is a single crystal silicon layer.
8. The semiconductor device according to claim 6, wherein the semiconductor layer comprise a silicide region.
9. The semiconductor device according to claim 6, wherein a thickness of the semiconductor layer is 10 to 200 nm.
10. The semiconductor device according to claim 6, wherein the conductive layer comprises tungsten.
11. A semiconductor device comprising:
a semiconductor layer having a first opening over a first insulating layer , the first insulating layer having a second opening;
a second insulating layer over the semiconductor layer;
a gate electrode over the second insulating layer;
a third insulating layer over the gate electrode, the third insulating layer having a third opening; and
a conductive layer over the third insulating layer,
wherein the conductive layer is connected to a side surface of the semiconductor layer and a side surface of the silicide region.
12. The semiconductor device according to claim 11, wherein the semiconductor layer is a single crystal silicon layer.
13. The semiconductor device according to claim 11, wherein the silicide region does not overlap the second insulating film.
14. The semiconductor device according to claim 11, wherein a thickness of the semiconductor layer is 10 to 200 nm.
15. The semiconductor device according to claim 11, wherein the conductive layer comprises tungsten.
16. The semiconductor device according to claim 1, wherein the opening reaches the insulating surface.
17. The semiconductor device according to claim 6, wherein the opening reaches the insulating surface.
18. The semiconductor device according to claim 1, wherein the opening is surrounded by the semiconductor layer.
19. The semiconductor device according to claim 6, wherein the opening is surrounded by the semiconductor layer.
20. The semiconductor device according to claim 11,
wherein the first insulating layer is over an insulating surface,
wherein the conductive layer is connected to the insulating surface through the first opening, the second opening, and the third opening.

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 control module for a motor vehicle, comprising:
a seat coupled to the vehicle;
a housing coupled to the seat;
at least one locking element coupled to the housing that is configured to resiliently deflect, and releasably secure the housing in the seat when the at least one locking element assumes a locking position;
a push button coupled to the at least one locking element, the push button configured to resiliently deflect the locking element into a position that releases the housing; and
a switch coupled to the housing, the switch having an opening therein that enables the locking element to move into the release position only when the switch is rotated to a defined switching position.
2. A control module according to claim 1, wherein the defined switching position for release of the locking element includes a position into which the switch is not moved during normal operation of the motor vehicle.
3. A control module according to claim 1, wherein each push button and each associated locking element form a slidepush connection, which transfers a movement of the push button to the locking element.
4. The control module according to claim 1, wherein the switch is configured as a rotary switch.
5. A control module for a motor vehicle, comprising:
a seat coupled to the vehicle;
a housing coupled to the seat;
a switch coupled to the housing;
at least one locking element coupled to the housing and configured to resiliently deflect, and to releasably secure the housing in the seat when the at least one locking element is in a locking position; and
a push button coupled to the at least one locking element and configured to unlock the at least one locking element enabling it to be deflected, and wherein the switch is further configured to act upon the at least one locking element and resiliently deflect it into a position that releases the housing.
6. A control module according to claim 5, wherein the push button and locking element form a groove and tongue connection that is released upon operation of the push button.
7. The control module according to claim 5, wherein the locking element is further configured such that an increased force expenditure is necessary to move the switch into the defined switching position to release the locking element.
8. A control module for a motor vehicle, comprising:
a seat coupled to the vehicle;
a housing coupled to the seat;
a switch coupled to the housing;
at least one locking element coupled to the housing and configured to resiliently deflect and releasably secure the housing in the seat when the at least one locking element is in a locking position; and
a push button configured to unlock the switch enabling it to rotate, and wherein the switch is further configured to resiliently deflect the at least one locking element to a release position and release the housing.
9. A method for releasing a vehicular control module from a seat, the control module having a housing with a switch, wherein the housing has at least one resiliently deflectable locking element, and wherein the locking element is prevented from deflecting into a release position when a groove and tongue connection is engaged, the groove and tongue connection having a pushbutton actuator, the method comprising the steps of:
releasing the groove and tongue connection by depressing the pushbutton actuator; and
moving the switch into a defined switching position to resiliently deflect the locking element into a release position.