Patent application number | Description | Published |
20100068617 | Lithium microbattery comprising an encapsulating layer and fabrication method - A lithium microbattery formed by a stack of thin layers on a substrate which comprises two current collectors, a positive electrode, a solid electrolyte layer, a negative electrode and an encapsulating layer. The encapsulating layer is formed by a protective layer made from polymer material on which a barrier layer is arranged. The protective layer comprises a copolymer formed from a homogeneous mixture of at least two photopolymerizable precursor materials, respectively acrylate-based and epoxide-based. | 03-18-2010 |
20100129717 | Microbattery on a substrate with monolithic packaging - The microbattery comprises a first current collector and a second current collector arranged on a substrate, and a stack comprising two electrodes separated by an electrolytic film. Each electrode is connected to a corresponding collector, one of the electrodes being a lithium-based anode. The stack is covered by a packaging comprising a metal layer. The first current collector is salient from the packaging and the second current collector is in contact with the metal layer. An alumina plug with a thickness of less than 30 nm is arranged between the first current collector and the metal layer, the electrode in contact with the first current collector being electrically insulated from the metal layer by the alumina plug. | 05-27-2010 |
20100310932 | FLEXIBLE PACKAGING DEVICE OF A MICROBATTERY - The packaging device of a microbattery arranged on a flexible support comprises at least one thin layer forming a protective barrier deposited on the whole of the microbattery, and a flexible compensation cover above the barrier. The cover is made from a material, for example polymer, with a thickness t | 12-09-2010 |
20110097625 | LITHIUM MICROBATTERY PROVIDED WITH AN ELECTRONICALLY CONDUCTIVE PACKAGING LAYER - A lithium microbattery comprises a packaging thin layer formed by a matrix of polymer material in which metallic particles are dispersed. The packaging thin layer constitutes at least a part of the anodic current collector of the lithium microbattery. The polymer material is advantageously obtained from at least a photopolymerizable precursor material chosen from bisphenol A diglycidylether, bisphenol F butanediol diglycidil ether, 7-oxabicylco[4.1.0]heptane-3-carboxylate of 7-oxabicylco[4.1.0]hept-3-ylmethyl and a mixture of bisphenol A and epichloridine. It can also be a copolymer obtained from a homogenous mixture of at least two photopolymerizable precursor materials, respectively acrylate-base, such as diacrylate 1,6-hexanediol and methacrylate, and epoxide-base, for example chosen from bisphenol A diglycidylether, 7-oxabicylco[4.1.0]heptane-3-carboxylate of 7-oxabicylco[4.1.0]hept-3-ylmethyl and a mixture of bisphenol A and epichloridine. | 04-28-2011 |
20120070588 | METHOD FOR PATTERNING A POLYMER LAYER AND METHOD FOR PACKAGING A MICROBATTERY - The method for patterning a polymer layer arranged on a support comprises deposition of a layer made from a lithium-based polymerization inhibitor material on a first area of the support, deposition of a cationically polymerizable material on the polymerization inhibitor layer and on a second area of the support, application of polymerization treatment resulting in a non-solidified sacrificial layer in the first area and the polymer layer in the second area, and elimination of the sacrificial layer. | 03-22-2012 |
Patent application number | Description | Published |
20090037731 | Architecture and Design for Central Authentication and Authorization in an On-Demand Utility Environment Using a Secured Global Hashtable - A Centralized Authentication & Authorization (CAA) system that prevents unauthorized access to client data using a secure global hashtable residing in the application server in a web services environment. CAA comprises a Service Request Filter (SRF) and Security Program (SP). The SRF intercepts service requests, extracts the service client's identifier from a digital certificate attached to the request, and stores the identifier in memory accessible to service providers. The client identifier is secured by the SP using a key unique to the client identifier. When the web services manager requests the client identifier, the web services manager must present the key to the SP in order to access the client identifier. Thus, the present invention prevents a malicious user from attempting to obtain sensitive data within the application server once the malicious user has gained access past the firewall. | 02-05-2009 |
20090204810 | Architecture and Design for Central Authentication and Authorization in an On-Demand Utility Environment - A Centralized Authentication & Authorization (CAA) system that facilitates secure communication between service clients and service providers. CAA comprises a Service Request Filter (SRF), a Service Client Authentication Program (SCAP), a Service Authorization Program (SAP), and an Authorization Database (ADB). The SRF intercepts service requests, extracts the service client's identifier from a digital certificate attached to the request, and stores the identifier in memory accessible to service providers. In the preferred embodiment, the SRF forwards the service request to a web service manager. The web service manager invokes SCAP. SCAP matches the identifier with a record stored in ADB. SAP queries ADB to determine if the service request is valid for the service client. If the service request is valid, SAP authorizes the service request and the appropriate service provider processes the service request. | 08-13-2009 |
20110083164 | ASSOCIATING MULTIPLE SECURITY DOMAINS TO APPLICATION SERVERS - Multiple security domains can be created and associated with various scopes within the cell allowing security configurations of each scope to be managed collectively. Examples of scopes include the entire cell, one or more application servers, one or more applications, one or more clusters, one or more service integration buses, one or more nodes, etc. Security configurations associated with the security domains can be applied to the scopes based on a hierarchy of the security domains. In addition, new security domains may be created automatically based on security requirements of newly installed applications. | 04-07-2011 |
20130007453 | Lattice scheme for establishing a secure multi-identity authentication context - This disclosure describes a secure and computationally-efficient method to establish a single authentication context for multiple identities. The method is implemented in an authentication system using a key exchange protocol, namely, the Diffie-Hellman key exchange. One or more entities that desire to authenticate (either individually or jointly) register with the authentication system and receive private Diffie-Hellman keys (the PINs). Later, during an authentication operation, each entity provides the PIN to the authentication system, preferably over a secure transport. The authentication system, using Diffie-Hellman key exchange artifacts, generates a Diffie-Hellman cryptographic value for each PIN, although the value need not be maintained private. The authentication system orders the Diffie-Hellman values as a “partially ordered set” to form a lattice. An authentication context is derived from the Diffie-Hellman values in the lattice. Thus, for example, during authentication of multiple entities, a shared key is computed incrementally as the Diffie-Hellman keys arrive from the entities for which a multi-identity authentication is required. The shared key represents a proof of group authentication. | 01-03-2013 |
20130007845 | Authentication and authorization methods for cloud computing security platform - An authentication and authorization plug-in model for a cloud computing environment enables cloud customers to retain control over their enterprise information when their applications are deployed in the cloud. The cloud service provider provides a pluggable interface for customer security modules. When a customer deploys an application, the cloud environment administrator allocates a resource group (e.g., processors, storage, and memory) for the customer's application and data. The customer registers its own authentication and authorization security module with the cloud security service, and that security module is then used to control what persons or entities can access information associated with the deployed application. The cloud environment administrator, however, typically is not registered (as a permitted user) within the customer's security module; thus, the cloud environment administrator is not able to access (or release to others, or to the cloud's general resource pool) the resources assigned to the cloud customer (even though the administrator itself assigned those resources) or the associated business information. To further balance the rights of the various parties, a third party notary service protects the privacy and the access right of the customer when its application and information are deployed in the cloud. | 01-03-2013 |