Method and system of a computer system for establishing communications between a service provider and a central service factory and registry in a computer system

• US 6,330,608 B1
• Filed: 03/31/1997
• Issued: 12/11/2001
• Est. Priority Date: 03/31/1997
• Status: Expired due to Term

• Current Assignee: Stiles Regisration Technologies, Inc.
• Original Assignee: Stiles Inventions, LLC
• Inventors: Stiles, Ian James
• Primary Examiner(s): Coulter, Kenneth R.
• Application Number:
  US08/828,721
• Time in Patent Office: 1,716 Days
• Field of Search: 709/217, 709/218, 709/225, 709/229, 395/200.47, 395/200.48, 395/200.55, 395/200.59, 380/4, 380/30, 713/201
• US Class Current: 709/229
• CPC Class Codes: G06F 21/445 by mutual authentication, e.g. between devices or programs

Abstract

A system and method for registering computer software modules to allow or reject it for opportunities of interacting with a computer system, hardware and software and receiving service requests is described. The method is designed to receive the module; to check whether the module contains any suspect “virus type” code; to check the module'"'"'s version compatibility; to check if the module contains an agreement string, a trademark string and a copyrighted text string. If all checks are valid, the module is registered and permitted to link and receive service requests. If not the module is rejected.

Claims

1. A process for registering modules for access to a computer system comprising:

(A) receiving a module for registration;

(B) loading said module into computer memory;

(C) checking said module for compliance with requirements for access to the computer system, wherein said checking includes testing said module to determine if said module includes a required trademarked string;

(D) if said module is found to comply with said requirements for access, granting access to said module, otherwise denying access.

2. A process for registering modules for access to a computer system, as recited in claim 1 wherein said checking said module for compliance step further comprises the step of checking said module for byte code validity.

3. A process for registering modules for access to a computer system, as recited in claim 1 wherein said checking said module for compliance step further comprises the step of checking said module to determine if said module has a version compatible with said computer system.

4. A process for registering modules for access to a computer system, as recited in claim 1 wherein said checking said module for compliance step further comprises the step of checking said module to determine if said module contains an expected string value.

5. A process for registering modules for access to a computer system, as recited in claim 1 wherein said checking said module for compliance step further comprises the step of checking said module to determine if said module contains an expected text string.

6. A process for registering modules for access to a computer system, as recited in claim 1 wherein said checking said module for compliance step further comprises the step of registering said module if all said checks return appropriate values.

7. A process for registering modules for access to a computer system, as recited in claim 1 wherein said checking said module for compliance step further comprises the step of returning to a previous routine.