|Publication number||US7353281 B2|
|Application number||US 09/923,663|
|Publication date||Apr 1, 2008|
|Filing date||Aug 6, 2001|
|Priority date||Aug 6, 2001|
|Also published as||US20030028653|
|Publication number||09923663, 923663, US 7353281 B2, US 7353281B2, US-B2-7353281, US7353281 B2, US7353281B2|
|Inventors||John C. New, Jr., Mark T. Price|
|Original Assignee||Micron Technology, Inc.|
|Export Citation||BiBTeX, EndNote, RefMan|
|Patent Citations (35), Referenced by (24), Classifications (21), Legal Events (3)|
|External Links: USPTO, USPTO Assignment, Espacenet|
The present invention relates generally to computer systems, and more specifically to providing access to computer resources over a computer network such as the Internet.
The architecture of computer networks has changed dramatically over the last several decades. In the seventies and early eighties, probably the most prevalent architecture was the mainframe architecture in which a very powerful mainframe computer contained all processing and storage power and users accessed the mainframe via so called “dumb” terminals, which had no processing power and acted merely as user interfaces to the mainframe. The mainframe architecture is prone to system failures because all processing power is located in the powerful mainframe computer, and while the mainframe computer is down no users can access the system. In the eighties, advancements in semiconductor technology enabled significant processing power to be placed on a user's desktop in the form of a personal computer. Consequently, the predominant computer network architecture defaulted into a distributed architecture, with a number of personal computers being interconnected via a communications network, such as a local area network. Under this type of architecture, each personal computer was able to share resources with the other computers, but many resources, such as application programs, were primarily stored and run independently on each personal computer, due, in part, to bandwidth limitations of communicating over the network.
In today's computing environment, the Internet forms part of a Global Communications Network that interconnects millions of computers via the client-server network architecture. In the client-server architecture, servers are powerful computers dedicated to managing network resources, and clients are personal computers or workstations that run application programs and rely on servers for computer resources such as files and even processing power. The client-server architecture has become a viable network architecture due in part to the dramatically increased bandwidth provided by the communications infrastructure forming the backbone of the Internet, as will be appreciated by those skilled in the art. The distributed processing power between the client and server systems has led to a myriad of third parties that provide software services to a number of users over the Internet or other wide area network. These third parties are known as Application Service Providers (“ASPs”) and they allow users to access software services provided by the ASPs by accessing a server maintained by the ASP over a suitable communications network.
In the example of
In operation, a user of the client computer system 102 accesses the ASP server computer system 104 and typically provides a request that includes various user information, such as user name, credit information, and which ones of the client application programs 114 the user desires to access. The server engine 110 processes the request, which includes verifying the user's credit, and thereafter transfers the selected application programs 114 to the client computer system 102. The user of the client computer system 102 thereafter utilizes the transferred application programs 114 as desired.
Depending on the type of service been provided by the ASP server computer system 104, the transferred application programs 114 may correspond to either the entire executable application program including all required system files, such as any required dynamic link library files, or may be an application “stub” or module containing only a portion of the application. When the entire executable application program 114 is transferred, the user simply opens this program as he would any other programs stored on the system 102 and need not be connected to the server computer system 104 when using the application program. This situation may be termed a broken-connection mode of operation because the client computer system 102 and server computer system 104 are not communicating when the application program 114 is being run. In contrast, when an application module is transferred to the client computer system 102, upon opening this module the application is initiated and the server computer system 104 is contacted and thereafter communicates with the client computer system to execute the application program. This situation may be termed a continuous-connection mode of operation because the client computer system 102 and server computer system 104 are communicating when the application program 114 is being run.
The user of the client computer system 102 must, of course, pay for the application programs 114 provided by the server computer system 104. Typically, the user pays for the application programs 114 in one of two ways. In the broken-connection situation, a user typically pays as he goes, meaning that the user simply pays for each application program 114 downloaded to the client computer system 102. In the continuous-connection situation, the user typically pays via a subscription agreement, allowing the user to pay a periodic subscription fee and obtain access to the services provided by the ASP server computer system 104. A user is typically assigned a username and password, which the user supplies to gain access to the application programs 114 corresponding to his subscription agreement.
Each of the broken-connection and the continuous-connection situations has drawbacks, both from the user's and ASP's perspectives. When a user downloads an application program 114 to the client computer system 102, the user may thereafter use the program on multiple computer systems and provide copies of the program to other users. While the terms of the license under which the user agrees to use the application program 114 may proscribe such conduct, the user may nonetheless take such action. In the continuous-connection environment, the user must connect to the server computer system 104 to run the selected application program 114, and this connection can dramatically slow the operation of the program, such as when the server computer system 104 has a large number of client computer systems 102 requesting service. Moreover, although a subscription agreement may be limited to a single user and a single machine, a user may provide his password to others, enabling other users to access the computer resources.
There is a need for providing users access to computer resources offered by ASPs that overcomes at least some of the shortcomings of the existing ASP systems.
According to one aspect of the present invention, a method for providing access to computer resources on a computer system includes generating a token containing encrypted user information including credit, authorization, and authentication information. A request is initiated to open an encrypted computer resource stored on the computer system, and execution of a remote application manager component on the computer system is also initiated. Under the control of the remote application manager component, the token is decrypted and a user of the computer system is authenticated using authentication information stored in the token. Whether the user is authorized to use the requested computer resource using authorization information stored in the token is then verified, as is whether the user has sufficient credit contained in the token to use the requested computer resource using credit information stored in the token. When the user is authenticated, authorized, and has sufficient credit, the requested computer resource is decrypted and opened. Use of the computer resource is then monitored to determine whether the user has sufficient credit to continue using the computer resource. A notification is provided when the monitored usage of the opened computer resource has exceeded the credit. The computer system on which the above method is executed may be a client system.
According to another aspect of the present invention, a server system receives client requests from client computers, such client requests including authorization, authentication, and credit information, and verifies credit information contained in such requests. When the credit of a user is verified, the server system generates the token containing the associated user information. The server system also selects computer resources using information contained in the client requests and encrypts each selected computer resource. The server system transfers to the client system the token and the encrypted selected computer resources along with the remote application manager component. The server system may thereafter update credit information and authorization information in response to client request from the client system, and provide the client system with an updated token and updated selection of computer resources.
The client computer systems 204 and 206 communicate with the server computer system 202 over communications links 208 and 210, respectively. The communications links 208 and 210 are illustrated separately to depict a continuous-connection environment via the link 208 and a broken-connection environment via the link 210, and each link corresponds to any of a variety of communications networks, such as the Internet, Local Area Networks, Wide Area Networks, a wireless network using the Wireless Application Protocol, and the like, as will be appreciated by those skilled in the art.
The server computer system 202 includes a client interface component 212 that processes requests received from the client computer systems 204, 206 and communicates with other components on the server computer system to provide the client computer systems with responses to such requests. An accounting and billing component 214 receives credit and billing information from the client interface component 212 and processes such information to verify a user's credit and bill the user for his use of the selected computer resources. A plurality of application programs 216 are stored on the server computer system 202, and correspond to one type of computer resource that may be supplied to the client computer systems 204, 206. The client interface component 212 selects particular ones of application programs 216 in response to corresponding client requests, encrypts the selected application programs, and provides the encrypted application programs to the client computer systems 204, 206. A token generation component 218 receives user information from the client interface component 212 and generates a token 220 using this information, where the token corresponds to a binary file containing encrypted user information, as will be described in more detail below. A key generation component 222 is responsible for generating encryption keys for use by the client interface component 212 in encrypting application programs 216 and the token generation component 218 in encrypting information. The key generation component 222 may utilize any of a variety of encryption methodologies in generating the encryption keys, and in one embodiment utilizes the Public Key encryption methodology to obtain public-private key pairs.
Each of the client computer systems 204 and 206 includes a number of components that have been downloaded from the server computer system 202. The client computer system 204 includes the token 220 and a plurality of application modules AM1-AMN, each application module being an encrypted file corresponding to a selected application program 216 on the server computer system 202. A remote application manager component 224 operates as a supervisory component to decrypt the token 220 and verify that a user is permitted to use a particular application module AM1-AMN, and thereafter decrypts the corresponding application module to enable the user to utilize the application module, as will be discussed in more detail below. The client computer system 204 is also shown as including a phantom application 226, which corresponds to an object which, when opened, initiates execution of corresponding application program stored on the server computer system 202. The phantom application 226 is thus similar to the application modules AM1-AMN except that no portion of the application program is actually stored on the client computer system 204. The client computer system 204 may contain any combination of application modules AM1-AMN and phantom applications 226.
The client computer system 206 also includes the token 220 and remote application manager component 224, along with a plurality of application programs AP1-APN, each application program being an encrypted file corresponding to a selected program 216 on the server computer system 202. Each application program AP1-APN is a complete executable program including any necessary system files, as previously discussed with reference to
In one embodiment, the client computer system 206 includes a card reader 226 that is adapted to receive a “smart card” 228 on which the token 220 is stored. The card reader 226 reads the token 220 stored on the smart card 228 and provides the token to the remote application manager component 224. The smart card 228 may be any type of compact card on which the token 220 may be stored, such as a true smart card containing embedded intelligence and memory, a credit card, an ATM card, and the like. The use of the smart card 228 enables a user to utilize multiple client computer systems to access the server computer system 202, and also provides added security in that presumably only the authorized user will be in possession of the smart card. Although the card reader 226 and smart card 228 are shown connected to the client computer system 206, they could also be utilized in the client computer system 204.
The specific type of user information stored in the token 220 aids in understanding the overall operation of the ASP system 200, and thus, before describing such overall operation, the token 220 will be described in more detail with reference to
In the embodiment of
A maintenance field 308 includes a user timestamp 310 corresponding to the time on the client computer system 204, 206 when the token 220 was generated. A server timestamp 312 stores the time on the server computer system 202 when the token 220 was generated. These timestamps 310, 312 ensure that the duration for which a user accesses a computer resource may be accurately tracked. An authorization field 314 includes an application identification field 316 that includes an application identification number for each application program the user is authorized to use. The application identification number is a unique number associated with each application program, as will be appreciated by those skilled in the art. An application authorization level field 318 stores information regarding particular authorization levels for each authorized application (i.e., each application identification stored in the field 312). Each authorized application may have a number of different authorization levels, and which authorization level a particular user has is stored in the field 318.
An accounting field 320 includes a use credit field 322 containing a value corresponding to the time for which a user may utilize the associated computer resources, and a use value field 324 corresponding to the time for which the user has actually utilized the computer resources. The difference between the fields 322 and 324 yields the time remaining for the user to utilize the computer resources. The fields 322, 324 may contain values corresponding to different ways of measuring a user's use of the computer resources. For example, instead of the duration for which the resource is used, the fields 322, 324 could include integer values, with the field 322 having a value indicating how many times a user is allowed to access the computer resource and the field 324 indicating how many times he has accessed the resource. In this way, the number of times the user may access the computer resource is limited, regardless of how long he accesses the resource each time. Other methods for measuring a user's use of the computer resource may also be utilized, as will be appreciated by those skilled in the art. The token 220 may further include additional fields 326 containing various other information such as error detection and correction fields, as will be understood by those skilled in the art.
The overall operation of the ASP system 200 will now be described in more detail. Initially, the client computer systems 204, 206 contact the server computer system 202 to establish service with the Application Service Provider. In the following example, it is assumed the client computer system 206 has contacted the server computer system 202. The client interface component 212 handles this interface with the client computer system 206, and may, for example, provide Web pages to the client computer systems allowing users to supply billing, credit, and personal information, as well as information about the computer resources the user desires to access, in addition to any other information the server computer system 202 desires to collect. The client interface component 212 thereafter supplies billing and credit information to the accounting in billing component 214 which, in turn, verifies the user's credit and establishes billing records. If the user's credit is declined, the component 214 notifies the client interface component 212, which then notifies the client computer system 206. The component 214 similarly notifies the client interface component 212 when the user's credit is approved, and the following discussion assumes the credit has been approved.
The client interface component 212 supplies the user information to be contained in the token 220 to the token generation component 218, and activates the key generation component 222 to generate an encryption key to be utilized for the client computer system 206 being processed. The token generation component 218 thereafter encrypts the user information received from the client interface component 212 using the encryption key to thereby generate the token 220. The client interface component 212 uses the key to encrypt the application programs 216 corresponding to the selected application programs contained in the supplied user information. At this point, the client interface component 212 transfers the token 220, the encrypted application programs 216 (designated application programs AP1-APN on the client computer system 206), and the remote application manager component 224 to the client computer system 206.
When the user of the client computer system 206 attempts to open one of the transferred application programs AP1-APN, the remote application manager 224 operates in combination with the token 220 and the selected application program to provide the user access to the selected program. The process executed by the remote application manager component 224 will be described in more detail with reference to the flow diagram of
Once step 404 is complete or if the determination in step 402 is positive, the process goes to step 406 and decrypts the token 220. The process then goes to step 408 and examines the contents of the decrypted token component 224 to determine whether the selected application is authorized for use. When the determination in step 408 is positive, the process goes immediately to step 410 and decrypts and executes the selected application program. From step 410, the process goes to step 412 and monitors the use of the selected application program. The process then goes to step 414 and determines whether the credit contained in the token 220 has expired. When the determination in step 414 is negative, the process proceeds to step 416 and determines whether the user has indicated a desire to stop running the selected application program. When the determination in step 416 is negative, the process goes back to step 412 and continues executing steps 412 and 414 to monitor the use of the selected application program AP1-APN and ensure that the user has sufficient credit to continue using the program. When the determination in step 416 is positive, indicating the user desires to stop running the selected application program, the process goes immediately to step 418 and the selected application program is once again encrypted along with the token 220. From step 418 the process goes to step 420 and terminates.
When the determination in step 414 is positive, this indicates the user's credit contained in the token 220 has expired and the process goes to step 422 and warns the user to save his work. From step 422, the process goes to step 424 and determines whether the user wishes to continue running the selected application program AP1-APN. When the determination in step 424 is negative, the process goes immediately step 418 and encrypts the selected application program and the token 220, and then goes to step 420 terminates. When the determination in step 424 is positive, the process goes to step 426 and contacts the server computer system 202 to obtain additional credit for the user. Once the server computer system 202 has been contacted, the process goes to step 428 and determines whether the user has sufficient credit. When the process arrives at step 428 in this manner, the inquiry in step 428 is necessarily negative and the process goes immediately step 430. In step 430, the user is presented with a billing screen and provides required information to obtain additional credit.
From step 430, the process goes to step 432 and supplies the information entered in step 430 to the server computer system 202. From step 432, the process goes to step 434 and determines whether the user's credit has been approved or declined by the server computer system 202. When the determination in step 434 is negative, the users credit has been declined and the process goes immediately to step 420 and terminates. When the determination in step 434 is positive, the user's credit has been approved and the process goes to step 436 and a new token 220 is received from the server computer system 202. The new token 220 contains updated credit information so that the user may access the desired application programs AP1-APN. From step 436, the process goes back to step 406. As indicated in
Going back to step 408, when the determination in step 408 is negative the selected application program AP1-APN is not authorized for use. As a result, the process goes to step 438 and contacts the server computer system 202 in order to obtain authorization for the selected application program AP1-APN. In step 438, the user will supply any required information to obtain access to the selected application program AP1-APN. From step 438, the process goes to step 428 and determines whether the user has sufficient credit. If the determination in step 428 is positive, the process goes to step 436 and receives a new token from the server computer system 202. It should be noted that when the process arrives at the step 436 via the determination in step 408 being negative and the determination in step 428 being positive, the new token 220 received in step 436 will include only updated authorization information. Conversely, when the process arrives at step 436 via steps 426 and 428, the new token 220 received in step 436 will include only updated credit information. When the process arrives at the step 436 via the step 434, the new token 220 may include both updated credit and authorization information.
With the ASP system 200, an Application Service Provider can provide application programs for certain periods of time in both broken-connection and continuous-connection environments. Moreover, with the system 200 the versions of application programs being run by users may be conveniently updated each time the client computer system 204, 206 contacts the server computer system 202 to obtain additional credit. The system 200 also provides added security for Application Service Providers because unauthorized copies of the application programs may not be made, and users may be limited to a particular client computer system 204, 206 on which they can use the selected application programs. In the embodiment where the token 220 is contained on a smart card 228, each user also realizes added security in preventing unauthorized use of the application programs since the smart card is required to access to such programs.
It is to be understood that even though various embodiments and advantages of the present invention have been set forth in the foregoing description, the above disclosure is illustrative only, and changes may be made in detail, and yet remain within the broad principles of the invention. For example, although the components described above would typically be implemented in software on suitable processing circuitry, where appropriate such components may be also be implemented using either digital or analog circuitry, or a combination of both. Therefore, the present invention is to be limited only by the appended claims.
|Cited Patent||Filing date||Publication date||Applicant||Title|
|US5761309 *||Aug 29, 1995||Jun 2, 1998||Kokusai Denshin Denwa Co., Ltd.||Authentication system|
|US5768382 *||Nov 22, 1995||Jun 16, 1998||Walker Asset Management Limited Partnership||Remote-auditing of computer generated outcomes and authenticated biling and access control system using cryptographic and other protocols|
|US5850442 *||Mar 26, 1996||Dec 15, 1998||Entegrity Solutions Corporation||Secure world wide electronic commerce over an open network|
|US6006328 *||Jul 12, 1996||Dec 21, 1999||Christopher N. Drake||Computer software authentication, protection, and security system|
|US6173400 *||Jul 31, 1998||Jan 9, 2001||Sun Microsystems, Inc.||Methods and systems for establishing a shared secret using an authentication token|
|US6175922 *||Mar 13, 2000||Jan 16, 2001||Esign, Inc.||Electronic transaction systems and methods therefor|
|US6270011 *||May 28, 1999||Aug 7, 2001||Benenson Tal||Remote credit card authentication system|
|US6363488||Jun 7, 1999||Mar 26, 2002||Intertrust Technologies Corp.||Systems and methods for secure transaction management and electronic rights protection|
|US6438597||Aug 17, 1998||Aug 20, 2002||Hewlett-Packard Company||Method and system for managing accesses to a data service system that supports persistent connections|
|US6449719 *||Nov 9, 1999||Sep 10, 2002||Widevine Technologies, Inc.||Process and streaming server for encrypting a data stream|
|US6523022||Jul 7, 1999||Feb 18, 2003||Allen Hobbs||Method and apparatus for selectively augmenting retrieved information from a network resource|
|US6594692||Apr 29, 1996||Jul 15, 2003||Richard R. Reisman||Methods for transacting electronic commerce|
|US6658568||Oct 26, 1999||Dec 2, 2003||Intertrust Technologies Corporation||Trusted infrastructure support system, methods and techniques for secure electronic commerce transaction and rights management|
|US6662231||Jun 30, 2000||Dec 9, 2003||Sei Information Technology||Method and system for subscriber-based audio service over a communication network|
|US6721716||Sep 29, 2000||Apr 13, 2004||Mobius Management Systems, Inc.||Payment certification string and related electronic payment system and method|
|US6763370||May 12, 1999||Jul 13, 2004||Softricity, Inc.||Method and apparatus for content protection in a secure content delivery system|
|US6769010||May 11, 2000||Jul 27, 2004||Howzone.Com Inc.||Apparatus for distributing information over a network-based environment, method of distributing information to users, and method for associating content objects with a database wherein the content objects are accessible over a network communication medium by a user|
|US6769127||Jun 16, 2000||Jul 27, 2004||Minerva Networks, Inc.||Method and system for delivering media services and application over networks|
|US6810525 *||Aug 3, 2000||Oct 26, 2004||General Instrument Corporation||Impulse pay per use method and system for data and multimedia services|
|US6918113 *||Apr 5, 2001||Jul 12, 2005||Endeavors Technology, Inc.||Client installation and execution system for streamed applications|
|US20010051996||Feb 20, 2001||Dec 13, 2001||Cooper Robin Ross||Network-based content distribution system|
|US20020002538||Jan 2, 2001||Jan 3, 2002||Ling Marvin T.||Method and apparatus for conducting electronic commerce transactions using electronic tokens|
|US20020007321||Mar 22, 2001||Jan 17, 2002||Burton Peter A.||Methods and apparatus for on-line ordering|
|US20020013944||Aug 6, 2001||Jan 31, 2002||Gordon Donald F.||Method and apparatus for providing subscription-on-demand services for an interactive information distribution system|
|US20020026503||Apr 11, 2001||Feb 28, 2002||Samuel Bendinelli||Methods and system for providing network services using at least one processor interfacing a base network|
|US20020037075||Jul 2, 2001||Mar 28, 2002||Flanagan Thomas F.||Provisioning of subscriber services|
|US20020055878||Mar 22, 2001||May 9, 2002||Burton Peter A.||Methods and apparatus for on-line ordering|
|US20020104019||Jan 31, 2001||Aug 1, 2002||Masayuki Chatani||Method and system for securely distributing computer software products|
|US20020112171 *||Jan 19, 2001||Aug 15, 2002||Intertrust Technologies Corp.||Systems and methods for secure transaction management and electronic rights protection|
|US20020141387||Apr 3, 2001||Oct 3, 2002||David Orshan||System, method and computer program product for delivery of internet services from a central system to multiple internet service providers at guaranteed service levels|
|US20020188863||May 11, 2001||Dec 12, 2002||Solomon Friedman||System, method and apparatus for establishing privacy in internet transactions and communications|
|US20020194140||Apr 18, 2001||Dec 19, 2002||Keith Makuck||Metered access to content|
|US20020194143||Apr 26, 2001||Dec 19, 2002||International Business Machines Corporation||Method and system for usage-based pricing of E-content|
|US20030028586||Jul 31, 2001||Feb 6, 2003||International Business Machines Corporation||System and method for providing efficient and secure data exchange using strip information elements|
|US20030236745||Jun 12, 2001||Dec 25, 2003||Hartsell Neal D||Systems and methods for billing in information management environments|
|Citing Patent||Filing date||Publication date||Applicant||Title|
|US7516104||Sep 29, 2005||Apr 7, 2009||Qurio Holdings, Inc.||Methods of providing software over a network and related systems and computer program products|
|US7818582 *||Oct 19, 2010||Accenture Global Services Gmbh||Single sign-on with common access card|
|US8032922 *||Dec 18, 2006||Oct 4, 2011||Oracle International Corporation||Method and apparatus for providing access to an application-resource|
|US8196175||Jun 5, 2012||Microsoft Corporation||Self-describing authorization policy for accessing cloud-based resources|
|US8321924 *||Sep 14, 2007||Nov 27, 2012||Feitian Technologies Co., Ltd.||Method for protecting software accessible over a network using a key device|
|US8418222 *||Sep 30, 2008||Apr 9, 2013||Microsoft Corporation||Flexible scalable application authorization for cloud computing environments|
|US8443055 *||Jun 23, 2005||May 14, 2013||Fujitsu Limited||System and method to provide device control service, and computer product|
|US8458098 *||Jun 4, 2013||Qurio Holdings, Inc.||Methods of tracking remote software installations and registrations and related systems and computer program products|
|US8522042 *||Oct 31, 2006||Aug 27, 2013||Hewlett-Packard Development Company, L.P.||Method and apparatus for enforcement of software licence protection|
|US8561908 *||Aug 29, 2006||Oct 22, 2013||Felica Networks, Inc.||Information processing system, clients, server, programs and information processing method|
|US8645945 *||Aug 9, 2010||Feb 4, 2014||International Business Machines Corporation||Method and apparatus for dynamic middleware assembly|
|US8949821 *||Nov 30, 2007||Feb 3, 2015||Cassis International Pte. Ltd||Cap file for the personalization of a java application|
|US20060031683 *||Jun 27, 2005||Feb 9, 2006||Accenture Global Services Gmbh||Single sign-on with common access card|
|US20060059374 *||Dec 23, 2003||Mar 16, 2006||Trusted Logic||Method for securing computer systems by software containment|
|US20060187857 *||Jun 23, 2005||Aug 24, 2006||Fujitsu Limited||System and method to provide device control service, and computer product|
|US20070045408 *||Aug 29, 2006||Mar 1, 2007||Jun Ogishima||Information processing system, clients, server, programs and information processing method|
|US20080072297 *||Sep 14, 2007||Mar 20, 2008||Feitian Technologies Co., Ltd.||Method for protecting software based on network|
|US20080148351 *||Dec 18, 2006||Jun 19, 2008||Gaurav Bhatia||Method and apparatus for providing access to an application-resource|
|US20080148400 *||Oct 31, 2006||Jun 19, 2008||Hewlett-Packard Development Company, L.P.||Method and apparatus for enforcement of software licence protection|
|US20090228950 *||Mar 5, 2008||Sep 10, 2009||Microsoft Corporation||Self-describing authorization policy for accessing cloud-based resources|
|US20090228967 *||Sep 30, 2008||Sep 10, 2009||Microsoft Corporation||Flexible Scalable Application Authorization For Cloud Computing Environments|
|US20100077392 *||Nov 30, 2007||Mar 25, 2010||Kian Teck Soh||Cap file for the personalization of a java application|
|US20100306761 *||Aug 9, 2010||Dec 2, 2010||Diament Judah M||Method and apparatus for dynamic middleware assembly|
|US20110072018 *||May 27, 2008||Mar 24, 2011||Jeffrey Joel Walls||Hierarchical administration of resources|
|U.S. Classification||709/229, 717/178, 713/185, 713/188, 713/189, 717/172, 709/219, 713/193, 713/192, 717/175, 713/190, 717/174, 717/177, 713/191, 717/176|
|International Classification||H04L29/06, G06F15/16|
|Cooperative Classification||H04L63/08, H04L63/04|
|European Classification||H04L63/04, H04L63/08|
|Aug 6, 2001||AS||Assignment|
Owner name: MICRON TECHNOLOGY, INC., IDAHO
Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:NEW, JOHN C., JR.;PRICE, MARK T.;REEL/FRAME:012063/0418;SIGNING DATES FROM 20010710 TO 20010719
|Aug 31, 2011||FPAY||Fee payment|
Year of fee payment: 4
|Sep 16, 2015||FPAY||Fee payment|
Year of fee payment: 8