Abstract:
Services and resources hosted by more than one originator are distributed to a plurality of consumers. To facilitate the distribution of the services and resources, the reseller contains host access information for each originator to which the reseller is authorized to access resources. Upon receipt of consumer access information to an authorized consumer, the reseller provides host access information to each originator hosting resources the authorized consumer is authorized to access. Each originator receiving host access information from the reseller will permit the authorized consumer access to the resources and services. In this way, a reseller provides a “virtual host” to consumers by reselling services and resources from different originators. An originator may also be a reseller of those services and resources of other originators. The originators and resellers are identified by unique randomly created identifiers to maintain their identities confidential. Each originator stores information correlating the consumers with the resellers through which the consumer obtains the services of the originator. In this way, the originator can deny access to a reseller, as well as all consumers accessing services through the unauthorized reseller.

Description:
FIELD OF THE INVENTION  
         [0001]    This invention relates to the field of distributed computing and distribution of services and resources. More particularly, this invention relates to a method and system to facilitate distribution of services and resources through a network.  
         BACKGROUND OF THE INVENTION  
         [0002]    It is known in the art to have various originators which host services and resources for use by consumers. It is also known to have originators which physically possess the systems to host services and resources and distribute and sell these services and resources through a network to various remotely located consumers. The consumers purchase these services and resources as required.  
           [0003]    The originators can host any number of different services and resources. In a particular case where the originator hosts services for Internet customers, these services and resources would include computer processing space, disk space, IP addresses, web servers, database servers, file servers, connections to backbones and other types of services and resources. In this case, the consumer would generally be a web site owner and would purchase the hosted resources and services as required to operate its web site.  
           [0004]    [0004]FIG. 1 shows a conventional system  8  for distributing resources and services S over a network I. As illustrated in FIG. 1, the originator  2  provides resources and services, shown generally by reference numerals S 1 , S 2 , S 3 , and collectively by reference numeral S. These services and resources S can be purchased and used directly by consumers  6 , such as consumer  6 A. In addition to consumer  6 A purchasing and using the services and resources S 1 , S 2 , S 3  directly from the originator  2 , resellers  4  may purchase use of the services and resources S from the originator  2  for resale to other consumers  6 . For example, in FIG. 1, the reseller  4 A has purchased use of services S 1 , S 2  and the reseller  4 B has purchased use of services S 1 , S 3 . The reseller  4 A can then resell these services S 1 , S 2  to consumers  6 B to  6 D and resellers  4 B can then resell these services S 1 , S 3  to consumers  6 E and  6 F.  
           [0005]    Furthermore, in the conventional system  8 , the identity of the originator  2  actually hosting the services and resources may be known to all of the consumers  6 , including consumers  6 B to  6 D,  6 E and  6 F accessing the resources and services through resellers  4 A,  4 B.  
           [0006]    While the conventional system  8  has worked well in the past, the conventional system  8  suffers from several disadvantages. For example, the conventional system  8  suffers from the disadvantage that it has a limited scope. This is the case, in part, because all of the services and resources S accessed by the consumer  6  in the conventional system  8  can originate from only one originator  2 . In other words, consumers  6  are limited in their ability to simultaneously access services and resources S hosted by a number of different originators  2 .  
           [0007]    The conventional system  8  also suffers from the disadvantage that the resellers  4  are captive in that they can only resell services and resources S from the one originator  2 . This limits the resellers  4  to purchasing the services and resources S from only one originator  2 . This also gives the originator  2  an unfair business advantage. For example, the originator  2  could sell one of the services and resources S 1 , S 2 , S 3  at a higher price, or, force the resellers  4  to purchase services and resources S which the resellers  4  may not require. Furthermore, the resellers  4  generally are precluded from hosting services and resources S independently and combining these with the services and resources S from other originators  2 .  
           [0008]    A further disadvantage of the conventional system  8  is that the consumers  6  can only access services and resources S ultimately hosted by one originator  2 . In this way, the consumer  6  may be precluded from obtaining a desired combination of services and resources S, if the desired combination of services and resources S are not all offered by the same originator  2 . Furthermore, the consumers as illustrated in FIG. 1, for example, are precluded from having services S other than services S 1 , S 2  and S 3  because originator  2 , from whom the consumers  6  ultimately obtain their services, only provides services S 1 , S 2  and S 3 .  
         SUMMARY OF THE INVENTION  
         [0009]    Accordingly, it is an object of this invention to at least partially overcome the disadvantages of the prior art. Also, it is an object of this invention to provide an improved type of system and method to facilitate distribution of services and resources through a network. Furthermore, it is an object of this invention to provide an improved system and device which increases the versatility of the distribution of services and resources through the network.  
           [0010]    Accordingly, in one of its objects, the present invention resides in a system for facilitating access by a plurality of consumers to services hosted on more than one originator, said system comprising: in each originator, a host record storing host access information HAI for each consumer authorized to access a service hosted by the originator; in a reseller for reselling services hosted by more than one originator, said reseller containing a reseller record storing host access information for each originator from which the reseller is authorized to access services, and, consumer access information for each consumer authorized to access services provided through the reseller; wherein, in response to the reseller receiving information from an authorized consumer corresponding to the consumer access information for the authorized consumer, the reseller provides host access information from its reseller records to each originator hosting services the authorized consumer is authorized to access; and wherein each originator receiving the host access information permits the authorized consumer access to the services for which the host access information received from the reseller corresponds with host access information stored in the host record of the originator.  
           [0011]    In a further aspect, the present invention resides in a method for facilitating access by a plurality of consumers to services hosted on more than one originator, said method comprising the steps of: (a) for each originator, providing a host record storing host access information for each consumer authorized to access a service hosted by the originator; (b) at a reseller, determining which services an authorized consumer is authorized to access; and (c) sending host access information from the reseller to each originator hosting services the authorized consumer is authorized to access.  
           [0012]    One advantage of the present invention is that services and resources which may originate from a number of originators, and hosted by a number of different hosting systems, can be accessed, purchased and used by any number of resellers and consumers. In this way, it is possible for a reseller to purchase the use of services and resources from a number of different originators and then resell those resources and services to other consumers. A further advantage of the present invention is that the resellers can also act as originators by hosting services and resources, as well as reselling the services and resources from other originators. A further advantage of the present invention is that resellers can also resell the services and resources to other resellers, thereby permitting resellers to buy the use of a large quantity of hosted applications, from one or more originators, for later resale to a number of smaller resellers.  
           [0013]    A further advantage of the present invention is that it provides the ability to bill the consumers of the services and resources for the services and resources which the consumers use. This billing can then be distributed amongst the various resellers and ultimately to the originator hosting the billed services and resources.  
           [0014]    A further advantage of the present invention is that it provides confidentiality between the various levels of originators, resellers and consumers. In other words, it is not necessary that the originator know all of the entities between the originator and the ultimate consumer of the services. Rather, the originators only need know the immediate purchaser of the services and resources.  
           [0015]    Another advantage of the present invention is that access to services and resources can be discontinued by any one entity. In other words, should an entity choose to discontinue access to services and resources which it provides, whether or not the entity is an originator, reseller, or combination of an originator and reseller, the entity can do so independently. In this event, it is understood that the entity would discontinue the access to services and resources of all other entities which obtain the services and resources through it, even if the other entities do not do so directly.  
           [0016]    A still further advantage of the present invention is that it provides the ability to create a liquid market for services and resources. In other words, by providing resellers and consumers with the ability to access, purchase, use and/or resell the services and resources from a number of different originators, the resources and services can then be accessed, sold, used and/or distributed in the network, similar to any other commodity and without restriction as to the originator of the services and resources.  
           [0017]    A still further advantage of the present invention is that in a preferred embodiment, the host systems or hosting machines are identified by a unique address on the network. For example, if the present invention is implemented on the Internet, each host system or hosting machines may have an Internet protocol (IP) address. In this way, the host machines can be addressed directly to more efficiently permit transfer of information to and from the host systems and machines.  
           [0018]    Further aspects of the invention will become apparent upon reading the following detailed description and drawings which illustrate the invention and preferred embodiments of the invention.  
       
    
    
     BRIEF DESCRIPTION OF THE DRAWINGS  
       [0019]    In the drawings, which illustrate embodiments of the invention:  
         [0020]    [0020]FIG. 1 is a schematic diagram illustrating a conventional system.  
         [0021]    [0021]FIG. 2 is a schematic diagram illustrating an example of the system according to one embodiment of the present invention.  
         [0022]    [0022]FIG. 3 is a schematic diagram illustrating a selection of consumers shown in FIG. 2 administering their services on corresponding originators.  
         [0023]    [0023]FIG. 4 is a block diagram illustrating the records stored within originators and resellers according to one embodiment of the present invention.  
         [0024]    [0024]FIGS. 5A and 5B illustrate the records stored in originator A of the example shown in FIG. 2 and according to one embodiment of the present invention.  
         [0025]    [0025]FIGS. 6A and 6B illustrate the records stored in originator D of the example shown in FIG. 2 and according to one embodiment of the present invention.  
     
    
     DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS  
       [0026]    In one embodiment, the present invention provides a system and method which facilitates an originator of some services, reselling services and resources hosted by other originators. In this way, the system and method according to the present invention provides a single “virtual host” or “virtual originator” which may comprise services and resources hosted by a number of individual and separately located originators, but administered by one consumer, such as a web administrator. This permits a consumer, such as a web administrator, to administer services and resources provided by more than one actual originator.  
         [0027]    The present invention also provides the ability for a number of resellers to resell the services and resources from different originators. In other words, the resellers can become a “virtual host” or “virtual originator” providing to a consumer the services and resources being hosted by a number of different originators. It is apparent that the consumer need not be aware that the “virtual host” is not the real host of all the services and resources. In this way, the system and method supports a value added reseller (VAR) structure where a number of resellers can purchase large volumes of services and resources from various originators and then resell the services and resources to either consumers, or other resellers.  
         [0028]    To facilitate this VAR structure, the present invention provides a system and method wherein each of the originators and resellers contain records indicating the volume of services and resources having been purchased by the corresponding reseller and/or available by a corresponding originator, and an indication of the further reseller or consumer to whom these services and resources have been resold. These records can be contained within a directory in each originator and each reseller along with the passwords and access information, such as operating accounts, to permit an authorized consumer to access the services and resources. In a preferred embodiment, logs are also kept regarding the usage of each consumer in order to assess billing of the consumer, as well as the resellers, within the VAR structure.  
         [0029]    In a further preferred embodiment, the records stored in each database identifying the various resellers and originators are randomly generated, such as by a Globally Unique Identifier (GUID), and can be used to identify the ultimate originator hosting the services and resources and the ultimate consumer to whom the resources have been sold and resold. In this way, confidentiality amongst the various entities in the VAR structure is maintained. Furthermore, encryption is utilized for all communication between the entities within the VAR structure.  
         [0030]    In a further preferred embodiment, the consumers are virtual administrators, which is a term used to refer to persons from hosting client companies, typically web site owners, that are responsible for the web site maintenance of a particular web site. Virtual administrators are given enough rights to perform functions asked of them, such as administering the web site of their clients, but not so much access that the security of the system, or other web sites hosted on the system, might be exposed. One system and method for controlling the access of virtual administrators to the system resources, and in particular restricting access of each virtual administrator to the services and resources they are administering on behalf of their clients, is disclosed in co-pending U.S. application Ser. No. 09/631,700 by Chernyavsky et al. entitled “Method and System for Facilitating Remote Administration of Web Sites”, which is assigned to the present applicant and the contents of which is hereby incorporated by reference. It is understood that, while in a preferred embodiment the consumers and administrators in the present system may be virtual administrators as disclosed in U.S. application Ser. No. 09/631,700, it is not necessary in the present system for the consumers and administrators to also be virtual administrators or utilize the system and method described in this application.  
         [0031]    [0031]FIG. 2 shows a system, illustrated generally by reference numeral  110 , according to an embodiment of the present invention. As illustrated in FIG. 2, the system  110  comprises originator A which hosts services S 1 , S 2 , S 3 , S 4 , S 5  and S 7 , and, originator D which hosts service S 6 . The system  110  also comprises originator B which hosts service S 3  and originator C which hosts service S 4 . The services S 3 , S 4  hosted by originators B and C, respectively, may be similar to the services S 3 , S 4  hosted by originator A.  
         [0032]    It is understood that reference to the services S in the context of this specification is interchangeable with reference to resources. In other words, throughout this application, including in the claims, reference to services or resources should be considered to include both services and resources.  
         [0033]    Entities F and G are resellers  40  in that they resell the services of others. For example, reseller F resells service S 2  from originator B and resells services S 1  and S 3  from originator C. Likewise, reseller L resells service S 6  from D and reseller G resells services S 1  from F and service S 4  from C.  
         [0034]    It is also apparent from FIG. 2 that, in the example illustrated in FIG. 2, all of the originators  20  also act as resellers  40  in that they resell services S hosted by other originators  20 . For instance, originator A, in addition to hosting services S 1 , S 2 , S 3 , S 4 , S 5  and S 7 , also resells service S 6  from L. Likewise, originator D, while hosting service S 6 , also resells service S 1 , S 3  and S 5  from A. It should be noted from FIG. 2 that reseller L resells service S 6  from D to A.  
         [0035]    Likewise, originator B, which hosts service S 3 , also resells services S 1  and S 2  from A. Similarly, originator C, which hosts services S 4 , also resells services S 1  and S 3  from originator A. It is understood that while the present invention facilitates the originators  20  also acting as resellers  40  reselling the services of others, it is not necessary that each or any originator  20  also act as a reseller  40  for the invention to operate.  
         [0036]    [0036]FIG. 2 illustrates the consumers  60  using services S hosted by the originators  20 . The services S which the consumers  60  are authorized to use are shown in brackets. The specific consumers  60  are identified by reference symbols VA 1  to VA 11 . Reference symbol “VA” is used to indicate that the consumers  60  are virtual administrators, as described above. However, as also described above, it is understood that the consumers  60  need not be “virtual administrators”, but rather any type of administrator could be used.  
         [0037]    As illustrated in FIG. 2, the consumer  60  can obtain the services S from a number of different originators  20 . For example, originator C hosts services S 4  and provides this service to consumer VA 11 . However, originator C resells services S 1  from originator A. In this case, service S 4  is provided through originator C to consumer VA 11 .  
         [0038]    As illustrated in FIG. 2, reseller F only resells services S 1 , S 2 , S 3  and does not host any services S. Services S, S 3  are provided through reseller F to consumer VA 3 . The services S 1 , S 3  are resold by F from originator C. Originator C in turn only hosts service S 4  and in fact, resells services S 1 , S 3  from originator A. In this case, originator C is acting as an intermediary reseller  40 I in that originator C resells services S 1 , S 3  from originator A to reseller F and reseller F then resells the services S 1 , S 3  to consumer VA 4 .  
         [0039]    [0039]FIG. 3 illustrates connections by selected consumers VA 6 , VA 7 , VA 8 , VA 9 , VA 10  and VA 11 , shown in FIG. 2, to administer their services. For clarity, only a portion of the system  110  illustrated in FIG. 2 is reproduced in FIG. 3. Consumer VA 6  will be discussed first.  
         [0040]    Consumer VA 6  is authorized to access services S 1 , S 4 . Services S 1  and S 4  are hosted by originator A and originator C, respectively. As illustrated in FIG. 3, originator A comprises Host 1  for hosting services S 1 , S 2 , S 3 . Originator A also hosts additional services S 4 , S 5  on Host 2  and service S 7  on Host 3 . Likewise, originator C is shown having Hosts for hosting service S 4 .  
         [0041]    In order to access the services S, an agent  140  is used. Access to the agent  140  is obtained once the host access information HA 1  is received by the agent  140  and compared to corresponding host access information HA 1  stored in its host record  152 . A host record  152  may be contained in each of the originators A, C and D. The host record  152  may be stored locally at the agent  140  for the corresponding host machine H, as illustrated by originators C and D in FIG. 3. Alternatively, the host record  152  for one or more host machines H can be stored in a central location within an originator  20 , as illustrated by originator A in FIG. 3. Preferably, the host record  152  is stored locally at each agent  140  for a host machine H to permit more efficient access to the services S being hosted by the host machine H. However, if an originator  20  has only one host machine H, such as originators C and D, the host record  152  may be stored centrally within the originator  20  without much decrease in efficiency.  
         [0042]    Likewise, resellers  40  contain reseller records  160  having stored therein the consumer access information CAI for authorized consumers  60 . The reseller records  160  of a reseller  40  may also contain the host access information HAI permitting the consumer  60  to access services S from each of the host machines H which the authorized consumer  60  is authorized to access. Furthermore, as all of the originators A, C and D in FIG. 3 also resell their services S to other resellers or directly to consumers  60 , originators A, C and D also have reseller records  160  to store consumer access information CAI of their consumers  60  and host access information HAI to permit their consumers  60  to access host machines H on other originators  20 .  
         [0043]    It is understood that the host record  152  and reseller records  160  are generally stored in directories (not shown) in each originator  20  or reseller  40 . The directories can be any type of directory stored on a storage device and supported by any type of operating system. In one embodiment, Windows 2000 is utilized as part of the operating system in which case the directory may be the active directory supported through Windows 2000. In an alternate embodiment, the directory may be supported through the Microsoft Data Engine.  
         [0044]    When consumer VA 6  wishes to administer services S 1 , S 4 , it will send its consumer access information CAI to its reseller  40 , which in this example is reseller G. Reseller G will compare the information received by consumer VA 6  with information stored in reseller records  160  contained in reseller G. If consumer VA 6  is an authorized consumer  60 , the consumer access information CAI received by the reseller G from consumer VA 6  will correspond to the consumer access information CAI stored in reseller G.  
         [0045]    Once reseller G is satisfied that consumer VA 6  has provided the proper consumer access information CAI, such as password and login, reseller G will interface through a network  101  to the originators from which reseller G is authorized to access services for consumer VA 6 . In this case, reseller G will send host access information HAI, stored in the reseller records  160 , through its interface  78 , through the network  101  and then to originators A and C which host the services S 1 , S 4  which consumer VA 6  is authorized access.  
         [0046]    The network  101  may be any type of network, including the Internet I. Once originators A and C receive the host access information HAI from reseller G, originators A and C will determine if the host access information HAI received from reseller G corresponds with the host access information HAI they have stored for consumer VA 6 . Generally, the host records  152  of originators A and C will contain the host access information HAI which must be received before consumer VA 6  can be permitted to access services S 1 , S 4 .  
         [0047]    If the host access information HAI provided by reseller G corresponds with the host access information HAI stored in originators A and C, originators A and C will provide access to the resources which consumer VA 6  is authorized to use. Reseller G will then create a graphical user interface for services S 1 , S 4  so that consumer VA 6  may access and/or administer the services S 1 , S 4 . In one embodiment, the graphical user interface provided by reseller G will be substantially identical to a graphical user interface reseller G would have provided if reseller G hosted both services S 1 , S 4  locally. In other words, consumer VA 6  may not be aware that the services S 1 , S 4  are not hosted by reseller G or that they are indeed hosted by two separate originators  20 , namely originator A and originator D.  
         [0048]    Consumer VA 11  is similar to consumer VA 6  in that consumer VA 11  also administers services S 1 , S 4 . However, consumer VA 11  administers its services through originator C. In this case, originator C hosts service S 4  and resells service S 1  from originator A. Accordingly, originator C acts as both an originator and a reseller in this example.  
         [0049]    When consumer VA 11  wishes to access and/or administer its services S 1  and S 4 , consumer VA 11  will send its consumer access information CAI to originator C. Originator C will compare the consumer access information CAI received from consumer VA 11  with the consumer access information CAI it has stored for consumer VA 11 . If the information received by originator C from consumer VA 11  corresponds to the consumer access information CAI stored by originator C, consumer VA 11  will be given access to services S hosted by and provided through originator C for consumer VA 6 . In this way, originator C will be performing a consumer authorization function similar to the function performed by reseller G when consumer VA 6  accesses reseller G.  
         [0050]    Once originator C is satisfied that consumer VA 11  has provided the proper consumer access information CAI, such as password and login, originator C will permit consumer VA 11  to access service S 4  which originator C hosts locally on machine H 5 . This may be done in a conventional manner as originator C hosts services S 4  locally. However, for other services S, originator C will interface through the network  101  to the originators from which originator C is authorized to access resources and for which consumer VA 11  has previously contracted with originator C to provide. In other words, originator C will perform a function similar to reseller G, namely sending host access information HAI from its reseller records  160 , through its interface  78 , through the network  101  and then to originator A which hosts service S 1 .  
         [0051]    Once originator A receives the host access information HAI from originator C, originator A will determine if the received host access information HAI corresponds with the host access information HAI originator A has stored for consumer VA 6 . If the received host access information HAI corresponds, originator A will provide access to the services S which consumer VA 11  is authorized to use. Originator C will then create a graphical user interface for services S 1  and S 4  so that consumer VA 11  may access and/or administer the services S 1 , S 4 . Consumer VA 11  may not perceive any differences between services S 1  and S 4 , even though service S 4  is hosted locally by originator C, while service S 1  is hosted remotely at originator A and provided through originator C.  
         [0052]    Similarly, consumers VA 8  and VA 7  access services through originator D. Originator D also performs the dual function of hosting service S 6  on Host 4 , while also reselling other services, namely reselling services S 1 , S 3  and S 5  from originator A.  
         [0053]    Consumer VA 8  will access and administer services S 1  and S 6  in a similar manner to that which consumer VA 11  accesses services S 1  and S 4 . In other words, consumer VA 8  will send its consumer access information CAI to originator D, and originator D will then compare the consumer access information CAI received from consumer VA 8  with the consumer access information CAI it has stored for consumer VA 8 . If consumer VA 8  is an authorized consumer  60 , the information received by originator D from consumer VA 8  will correspond to the consumer access information CAI stored in originator D. Originator D will then create a graphical user interface  78  for services S 1  and S 6  so that consumer VA 8  may access and/or administer the services S 1 , S 6 . Consumer VA 8  may not be aware that service S 6  is being provided locally by originator D, but service S 1  is being provided remotely by originator A.  
         [0054]    With respect to consumer VA 7 , consumer VA 7  is authorized to use services S 1  and S 3 . Originator D offers neither of these services S 1 , S 3 . Accordingly, originator D will provide consumer VA 7  with services S 1 , S 3  from originator A. In this case, originator D will be performing the function purely of a reseller  40 , similar to reseller G, because originator D does not host either of the services S 1 , S 3  which consumer VA 7  is authorized to use, even though originator D hosts services S 6  and is therefore generally referred to as originator D.  
         [0055]    Consumer VA 9  is authorized to use service S 6  from originator A. However, originator A does not host service S 6 . Accordingly, consumer VA 9  will access service S 6  through originator A, but originator A will obtain service S 6  from reseller L. Reseller L obtains the service S 6  from originator D, which may be unbeknownst to originator A. Originator A therefore acts also as a reseller for service S 6  from reseller L to consumer VA 9 , in a similar fashion to how reseller G provides services S 1  and S 4  to consumer VA 6 . Reseller L, in turn, obtains the service S 6  from originator D. Neither consumer VA 9  nor originator A may know that service S 4  is being hosted by originator D. Rather, consumer VA 9  may believe the service S 6  is being provided by originator A, and originator A in turn may believe service S 6  is being provided by originator L.  
         [0056]    Consumer VA 10  is authorized to use services S 6  and S 7 . Service S 7  is hosted locally by originator A through Host 3 , in a manner similar to consumer VA 11  accessing service S 4  locally at originator C. Consumer VA 10  will also access service S 6  which originator A provides from reseller L, but which is in fact hosted by originator D. Originator A will create a graphical user interface for services S 6  and S 7  for use by consumer VA 10 , but consumer VA 10  may not know that service S 7  is being hosted locally at originator A while service S 6  is being hosted by originator D and provided through reseller L.  
         [0057]    As described above, the information to facilitate sharing of the services S amongst various originators  20  is facilitated by the information stored in reseller records  160  and host records  152  contained within directories of the resellers  40  and originators  20 . The specific information stored in these records  152 ,  160 , according to one preferred embodiment of the invention, is illustrated in FIG. 4.  
         [0058]    As illustrated in FIG. 4, the first record, namely record  1  identified by reference numeral  100 , is “identification of current AD”. This is an identifier for the current entity, namely an originator  20  or a reseller  40  where the reseller record  160  is stored.  
         [0059]    The letters “AD” in FIG. 4 is an acronym for “administrative directory”. This identifies the administrative directory of the entity. In a preferred embodiment, the “AD” refers to the administrative directory used in the Windows™ operating systems. However, it is understood that any type of directory could be used in the present invention, and, it is not necessary that the records identify an administrative directory utilized by WindowsT™ operating systems.  
         [0060]    [0060]FIGS. 5A and 5B illustrate, symbolically, the nature of the information which may be stored in each of the records for originator A. For record  1 , shown by reference numeral  100 A in FIG. 5 a , the identifier for the current AD  100  is shown as “A(AD)” which represents the identification of the administrative directory for originator A. It is understood that the identifier could be any type of symbol, number or other indicia which can identify an originator  20  or reseller  40 .  
         [0061]    As shown in FIG. 4, record  2 , in one preferred embodiment, comprises three fields, namely (i) “ID of other AD accessible for current AD”, shown by reference numeral  201 , (ii) “person&#39;s identification in that AD”, shown by reference numeral  202  and (iii) “person&#39;s password in that AD”, shown by reference numeral  203 . The second record, namely record  2  identified by reference numeral  200  in FIG. 4, identifies the other entities, namely originators  20  or resellers  40 , the present entity can directly access. In other words, with reference to FIG. 2, originator A can access services offered by reseller L. Accordingly, for originator A, record  2  will contain information necessary for originator A to access the services from reseller L.  
         [0062]    [0062]FIG. 5A shows the nature of the information which would be stored in each of the fields  201 ,  202 ,  203  for record  2  of originator A. As shown by reference numeral  200 A in FIG. 5A, the first field  201  would comprise the identification of the administrative directory for originator L shown symbolically as “L(AD)”. This reflects that originator A has access to the service S 6  provided by reseller L as illustrated in FIG. 2. In the second field, the symbol “A&#39;s P_L” represents the identifier of originator A in reseller L&#39;s reseller record  160 . The third symbol in FIG. 5A, namely “A&#39;s psw_L”, represents the password of originator A in reseller L&#39;s reseller record  160 . It is understood that reseller L will have corresponding information in its reseller record  160 , but in a different field, to permit comparison and authorization of the information being provided by originator A.  
         [0063]    Returning to FIG. 4, in a preferred embodiment, the reseller records  160  contains a third record, namely record  3  which contains information regarding the entities, in this case originators  20 , resellers  40  or consumers  60 , who can access services S through the present entity. Record  3  comprises four fields, namely (i) “person&#39;s ID in current AD”, (ii) “person&#39;s password in current AD”, (iii) “person&#39;s role in AD”, and (iv) “person&#39;s internal account”, identified by reference numerals  301 ,  302 ,  303  and  304 , respectively.  
         [0064]    [0064]FIG. 5A illustrates the nature of the information stored in record  3  for originator A, shown generally by reference numeral  300 A. The first entry in record  300 A contains “D&#39;s P_A, D&#39;s psw_A, Reseller, D_INT” which represents the information in fields  301 ,  302 ,  303  and  304  of record  3  of originator A. Using the same convention as referred to above, the first item, namely “D&#39;s P_A”, represents the identifier of originator D in originator A&#39;s directory. The second item, namely “D&#39;s psw_A”, represents the password of originator D in originator A&#39;s directory. The third field  303  in record  3  is shown as “Reseller” which identifies originator D as performing the role of reseller with respect to services S provided by originator A. The fourth field  304  represents the person&#39;s internal account, which means the account used internally by the entity. For instance, in FIG. 5A, the internal account number identifying originator D in originator A is represented by “D_INT”.  
         [0065]    The last entry of record  3  in FIG. 5A shows the corresponding information for consumer VA 10  being “VA 10 &#39;s P-_A, VA 10 &#39;s psw_A, VA, VA 10 _INT”. This entry for consumer VA 10  mirrors the information for originator D in originator A&#39;s record  3 . In particular, this shows the identifier of consumer VA 10  in originator A&#39;s directory as “VA 10 &#39;s P_A”, the password of consumer VA 10  in originator A&#39;s directory “VA 10 &#39;s psw_A”, the role of consumer VA 10  with respect to originator A “VA” (which in this embodiment illustrates that consumer VA 10  is an administrator or virtual administrator), and consumer VA 10 &#39;s internal account number “VA 10 _INT”. Accordingly, it is clear that the entry for VA 10 , which accesses the services S 6 , S 7  from originator A, is similar to the entry for originator D, which accesses services S from originator A for resale, except that the role for consumer VA 10  is identified as being an administrator “VA”, while the role for originator D is identified as being a “reseller”.  
         [0066]    For consumers  60 , fields  301 ,  302 , which contain “person&#39;s ID in current AD” and “person&#39;s password in AD”, may be used to store the consumer access information CAI which a consumer  60  would need to provide to obtain access to services S. Accordingly, to access services S provided on or through originator A, consumer VA 10  would need to provide the consumer access information CAI “VA 10 &#39;s P_A, VA 10 &#39;s psw_A” which would then be compared against the information stored in fields  301  and  302 . If the information corresponds, the internal number “VA 10 _INT” for consumer VA 10  in field  304  can be used to identify the services S consumer VA 10  is authorized to use.  
         [0067]    For resellers  40 , fields  301  and  302  provide the information which one originator  20  or reseller  40 , such as originator D, would need to provide to communicate with originator A. Similarly, if originator A desires to communicate with another originator  20  or reseller  40 , originator A would need to provide corresponding information. For example, in record  2 , originator A contains its identifier “A&#39;s P_L” in field  202  and password “A&#39;s psw_L” in field  203  which originator A must provide to communicate with reseller L. This communication between originators  20  and resellers  40  could be for any purpose, such as creating accounts for consumers  60 , administering accounts of consumers  60 , obtaining billing information, or even accessing services S for their own use.  
         [0068]    Record  5 , identified by reference numeral  500  in FIG. 4, contains the information for accessing the services S hosted by originator A and also the services S to which originator A has access. In other words, record  5  contains the information necessary to provide services S hosted by originator A and hosted by other originators, but provided through originator A acting as a reseller.  
         [0069]    As illustrated in FIG. 4, the first field  501  referred to as “AD&#39;s identification in current scope” identifies the directory of the entity (originator  20  or reseller  40 ) from which a particular service S is provided. The second field  502  in FIG. 4 is referred to as “person&#39;s account or GUID”. This refers to the identifier originator A used to track a person&#39;s activity. For entities which are directly associated with originator A, the person&#39;s internal account in the present entity, which corresponds to field  304  of record  3 , will be used. If the person is not directly associated with originator A, the person will not have an entry in record  3  and will not have an internal account. In this case, the person will be given a GUID number. Preferably, a GUID is used in order to preserve the clients of other resellers confidential.  
         [0070]    The third field  503  is the “person&#39;s host access ID” which is the information necessary to permit the person to access to the services S. In other words, the third field  503  will contain sufficient information for the software to provide access to hosted services S, or, provide a link to where such information is stored. Finally, the fourth field  504  in FIG. 4 is entitled “person&#39;s password on a host” and corresponds to the actual password the person has with the particular host machine, wherever the host machine is located.  
         [0071]    With reference to FIG. 5A, record  5  is identified by reference numeral  500 A and the fourth entity shows “A(AD), D_INT, D_H 1 _Access, D&#39;s psw_H 1 ” which represents the information stored in the four fields,  501 ,  502 ,  503 ,  504  for originator D&#39;s access to host H 1 . In particular, the first field  501  contains “A(AD)” which identifies originator A where host H 1  is located. The second field contains the person&#39;s account number. In this case, originator D is directly associated with originator A and this field contains the internal account number for originator D, namely “D_INT”. As originator D is directly associated with originator A, originator D has an internal account number, as also shown at entry  1  of record  3  in the fourth field  504 . The next field contains originator D&#39;s host access ID “D_H 1 _Access” and in this case it is the host access ID for originator D to access host H 1 . The final field contains D&#39;s personal password for host H 1  at originator A.  
         [0072]    Reference is also made to the fourth to last entry in FIG. 5A which states “A(AD), VA 8 _D_GUID, VA 8 _D_H 1 _Access, VA 8 &#39;s psw_D_H 1 ”. This shows customer&#39;s VA 8  access through originator D to the service S 1  on host H 1  hosted by originator A. It should be noted that customer VA 8  does not have a direct relationship with originator A, but rather purchases the services S through originator D when originator D acts as a reseller. For this reason, consumer VA 8  will not have an internal number, but rather has a GUID number, namely “VA 8 _D_GUID”. The GUID for each entity indirectly associated with originator A will be unique and not used to identify any other entity in originator A. This prevents an ambiguity which could arise if more than one entity in originator A was identified by the same identifier. This also can conceal the true identity of consumer VA 8  from originator A, thereby preventing originator A from contacting consumer VA 8  directly. However, for monitoring billing and log purposes, originator D may receive a report from originator A showing consumer VA 8 &#39;s access to service S 1  identifying consumer VA 8  by “VA 8 _D_GUID” identification. Only originator D will be able to associate the GUID number “VA 8 _D_GUID” with consumer VA 8 &#39;s true identity.  
         [0073]    In the same entry, field  503  contains the host access ID “VA 8 _D_H 1 ” for consumer VA 8  and the field  504  contains the password “VA 8 &#39;s psw_D_H 1 ” for consumer VA 8  to host H 1 . This assists originator A to track the access of consumer VA 8  to service S 1  on host H 1  as described more fully below.  
         [0074]    The last entry in record  5  states “D(AD), VA 10 _A_L_GUID, VA 10 _A_L_H 4 _Access, VA 10 &#39;s psw_A_L_H 4 ”. This shows consumer VA 10 &#39;s access through reseller L to the service S 6  which is hosted on host H 4 . The first field  501  of this entry shows “D(AD)” indicating that the host H 4  is hosted by originator D. As illustrated in FIGS. 2 and 3, the service S 6  is hosted by originator D on host H 4 . Originator A indirectly obtains access to host H 4  through reseller L which in this case acts as an intermediate reseller  40 I.  
         [0075]    The second field  502  contains the internal number VA 10 _INT because consumer VA 10  accesses its services S through originator A. The internal number “VA 10 _INT” in field  502  also corresponds to the internal number “VA 10 _INT” in field  304 . Accordingly, the internal number “VA 10 _INT” can be searched in field  502  to locate all of the services S for which consumer VA 10  is permitted access. This is similar to entry  11  in record  5 , which contains “A(AD), VA 10 _INT, VA 10 _H 3 _Access, VA 10 &#39;s psw_H 3 ”, which is the information for consumer VA 10  to access service S 7  hosted on host H 3  located within originator A. However, entry  11  in fields  503 ,  504  contains the information, namely “VA 10 _H 3 _Access, VA 10 &#39;s psw_H 3 ”, for accessing services S 7  locally on host H 3 , while the last entry in fields  503 ,  504  contains the information, namely “VA 10 _A_L_H 4 _Access, VA 10 &#39;s psw_A_L_H 4 ” for accessing service S 6  on host H 4  remotely located in originator D.  
         [0076]    Record  6 , shown generally by reference numeral  600  in FIG. 4, contains information linking the host access ID with the operating account (“OS”) on a particular host machine which is hosted by originator A. The first field  601  of record  6  contains the “person&#39;s host access ID”. This corresponds to the same number stored in field  503  of record  5 . The second field  602  in record  6  contains the “person&#39;s role”, namely reseller or administrator. The third field  603  contains the host access ID of the creator of the entity referred to in field  601 . In this way, field  603  contains an indication of the person who contracted with originator A to provide the services S hosted by originator A. The fourth field  604  contains the “person&#39;s operating account” for the particular host H 1 .  
         [0077]    As shown in FIG. 5B, the first line of record  6  for originator A contains the entry “A_H 1 _Access, Originator, A_H 1 _OS”. The first field  601  of the first entry states “A_H 1 _Access” which is the access information for originator A for host H 1 . In other words, this is the access number for originator A to access its own host H 1 . The second field  602  contains “Originator” indicating that originator A is acting as originator in its own directory. The third field  603  contains a blank space “ ” because host H 1  is located at originator A, and therefore there is no creator. The fourth field  604  contains the symbol “A_H 1 _OS” which is the operating account of originator A on host H 1  permitting originator A to have direct access to host H 1 .  
         [0078]    Reference is also made to the fourth entry of record  6  in FIG. 5B which contains “D_H 1 _Access, Reseller, A_H 1 _Access, D_H 1 _OS”. This entry in record  6  contains information for originator D, which is a reseller, to obtain its operating account “D_H 1 _OS” to a host H 1  giving originator D direct access to host H 1 . It is interesting to note that the third field  603  shows the creator of this account to be “A_H 1 _Access” which is the access information of originator A to host H 1 . Reference is also made to the last entry in record  6  shown in FIG. 5B which is “VA 8 _D_H 1 _Access, VA, D_H 1 _Access, VA 8 _D_H 1 _OS”. The first field  601  for consumer VA 8 , namely “VA 8 _D_H 1 _Access”, is an identifier created by originator A to control consumer VA 8 &#39;s access to host H 1 . The second field  602  identifies consumer VA 8  as an administrator. The third field  603  identifies the creator of consumer VA 8 &#39;s account with A as being “D_H 1 _Access” which is the identifier for originator D to access host H 1  in originator A&#39;s account. The fourth field  604  contains the operating account of consumer VA 8  for host H 1 .  
         [0079]    The operating accounts OS in field  604  for each of the entities is mirrored in the host record  152  shown in FIG. 4 by reference numeral  800 . As shown in FIG. 4, the host record  152  contains in the first field  801  the “operating account” which corresponds to the operating account in field  604  of record  6 . The second field  802  contains a “password” used by the entity to access the services S. This prevents other entities from inadvertently obtaining the operating account OS and tampering with the entities&#39; services S.  
         [0080]    [0080]FIG. 6 shows the records in the directory  152  for originator D. As these records mirror the records stored in originator A, they will not be described in detail. However, reference is made to the third entry of record  3 , identified by reference numeral  600 A in FIG. 6, which shows the entry “VA 8 &#39;s_P_D, VA 8 &#39;s psw_D, VA, VA 8 _INT” which is the entry in originator D for consumer VA 8 . It is noted that because consumer VA 8  is associated directly with originator D, consumer VA 8  will have an entry in record  3  of originator D and will also have an internal number “VA 8 _INT” in the directory of originator D. Accordingly, when consumer VA 8  wishes to access services S hosted by or provided through originator D, consumer VA 8  will provide its identifier in originator D&#39;s directory “VA 8 &#39;s_P_D” and its password “VA 8 &#39;s psw_D” in originator D&#39;s directory. In this embodiment, the identifier “VA 8 &#39;s_P_D” and password “VA 8 &#39;s psw_D” will correspond to the consumer access information CAI referred to above for consumer VA 8  to access services S provided by and through originator D.  
         [0081]    Assuming that the identifier “VA 8 &#39;s_P_D” and password “VA 8 &#39;s psw_D” provided by consumer VA 8  corresponds to that in record  3  of originator D, consumer VA 8  will have access to the services S provided by and through originator D. Originator D will then create a virtual host or virtual originator for consumer VA 8  comprising the services S 1 , S 6  for which consumer VA 8  has been authorized. Originator D will identify services S 1 , S 6  by searching in record  5  field  502  using consumer VA 8 &#39;s internal number “VA 8 _INT”.  
         [0082]    The services S for which consumer VA 8  has been contracted is identified in entries  3  and  6  of record  5  in FIG. 6. As shown in FIG. 6, consumer VA 8  has access to host H 4  which is hosted by originator D (line  3  of record  5 ) for providing service S 6 , as well as host H 1  in originator A (line  6  of record  5 ) for providing service S 1 . Because service S 6  is hosted locally on host H 4  at originator D, originator D will use the identifier “VA 8 _H 4 _Access” stored in field  503  of entry  3  to obtain the operating account of consumer VA 8  on host H 4  “VA 8 _H 4 _OS” contained at line  3  of record  6  for originator D. Likewise, originator D will obtain the password “VA 8 &#39;s psw_H 4 ”, from field  504 , entry  3 , for consumer VA 8  to access host H 4 . This information, namely “VA 8 &#39;s psw_H 4 ” and “VA 8 _H 4 _OS”, will then be provided to the host record  152  for host H 4  and to the host part  152  and assuming these numbers correspond to the information stored in records  801  and  802  in record  800 D, respectively, consumer VA 8  will have access to service S 6  on host H 4  within originator D.  
         [0083]    Entry  6  of record  5  contains information for consumer VA 8  to access host H 1  on originator A. As field  501  contains “A(AD)” identifying originator A, originator D will be alerted to the fact that consumer VA 8  will have access to host H 1  on originator A and that originator D must access originator A. Specifically, originator D will obtain the identifier and password for consumer VA 8 , namely “VA 8 _H 1 _Access” and “VA 8 &#39;s psw_H 1 ” contained in fields  503  and  504  of entry  6  in record  500 D. Originator D will then provide this information through interface  78  and network I to agent  140  as discussed above with respect to FIG. 3. The information “VA 8 _H 1 _Access, VA 8 &#39;s psw_H 1 ” corresponds to the host access information HAI referred to above. This host access information HAI is preferably sent directly to agent  140  for host H 1 . To accomplish this, agent  140  will have an address in the network  101 , such as an IP address if the network  101  is the Internet I, as described above. This address may be embedded in the identifier “VA 8 _H 1 _Access”, or embedded in A(AD) stored in field  501  of entry  6  in record  500 D, or could be stored in another field (not shown) of the directory in originator D.  
         [0084]    In any case, the host access information HAI for consumer VA 8 , namely “VA 8 _H 1 _Access,VA 8 &#39;s psw_H 1 ” will eventually be provided to host record  152  for agent  140  to host H 1 . This host access information HAI will then be compared to the operating account and password, namely “VA 8 _D_H 1 _OS” and “VA 8 &#39;s psw_D_H 1 ” in the last entry of record  800 A, and, assuming they correspond, consumer VA 8  will have access to host H 1 . It is understood that having the host access information HAI stored in record  6  is a preferred embodiment and the host access information HAI could be provided by the consumer  60 .  
         [0085]    If, for whatever reason, originator A decides to discontinue access to originator D, originator A can determine the accounts of originator D using the internal number “D_INT” shown in record  3 , line  1 , of originator A. With this information, originator A can obtain the identifier of originator D to control access to the originator A&#39;s host H 1 , shown as “D_H 1 _Access” in record  5  as referred to above. Originator A can then discontinue or delete entries  4  and  5  in record  6  showing “D_H 1 _Access” and “D_H 2 _Access”, corresponding to the access ID for originator D.  
         [0086]    In addition, originator A will need to delete or discontinue all entities having access through originator D. Originator A can do so by accessing field  603  in record  6  which contains information regarding the creator of a host access ID. In other words, originator A will delete or discontinue the last two entries in record  6  corresponding to consumers VA 7  and VA 8  because field  603  for these entities shows the creator being “D_H 1 _Access”.  
         [0087]    In a preferred embodiment, field  603  is host specific, meaning that there will be a unique number for each host H to which originator D has access. For example, entry  5  in record  500 A contains “A(AD), D_INT, D_H 2 _Access, D&#39;s psw_H 2 ”. Accordingly, field  603  would need to be searched for “D_H 2 _Access” also in order to discontinue all entities having access through originator D. Alternatively, originator A can discontinue originator D&#39;s access to either host H 1  or H 2 .  
         [0088]    While the steps taken to delete the entries in records  5  and  4  will prevent originator D, and consumers VA 7  and VA 8  from administering the services S, it may still be possible for originator D, or consumers VA 7  and VA 8  to access the agent  140  for host H 1  directly and provide the operating account numbers “D_H 1 _OS”, “D_H 2 _OS”, “VA 7 _D_H 1 _OS” and “VA 8 _D_H 1 _OS”, as well as the associated passwords directly to the agent  140 . To avoid this possibility, the entries having these operating accounts OS will be identified from record  6  and removed from the host record  152 , namely entries  4 ,  5 ,  20  and  21  in record  800 A.  
         [0089]    In this way, originator D, as well as all entities accessing services through originator D, will be deleted from originator A&#39;s directory  152 . It should be noted that this can all be done locally in originator A&#39;s directory  152 . In other words, this can be accomplished without access to originator D&#39;s directory.  
         [0090]    Record  4 , shown in FIG. 4 by reference numeral  400 , and shown with respect to originator A in FIG. 5A by reference numeral  400 A, stores information relating to the volume of services S which can be provided by the originator  20  within which the record  4  is stored. Accordingly, it is clear that record  4  will be empty for a reseller  40 , such as reseller G, because a reseller  40  does not host any services S, but only resells services S from other entities. For this reason, record  4  will generally be stored in the host records  152  of an originator  20 .  
         [0091]    As illustrated in FIG. 5A, record  400 A for originator A shows services S 1 , S 2 , S 3 , S 4 , S 5  and S 7 . The first field  401 , referred to as “host ID” in FIG. 4, identifies a host in originator  20 . For instance, the first entry of record  4  in FIG. 5A shows “A_H 1 ” which identifies host H 1  in originator A.  
         [0092]    The second field  402 , referred to as “source ID” in FIG. 4, identifies services S reserved for rental or sale. For example, in FIG. 5A, record  4  at the first entry shows “H 1 _S 1 _ 1 ” which indicates that service S 1  is allocated on host H 1  in originator A. Because it is possible to have another portion of service S 1  on the same host, record  4  identified by reference numeral  400 A in FIG. 5A, has the additional number “1” after “S 1 ”. For example, in line  2  of record  4 , another portion of service S 1  is also hosted by host H 1  owned by originator A, as shown by the symbol “H 1 _S 1 _ 2 ”. The other two fields, referred to as “resource state provisioned”, identified by reference numeral  403  in FIG. 4, and “Original volume”, identified by reference numeral  404  in FIG. 4, simply show the portion of the resource or service S which has been provisioned in the original volume of the resource or service.  
         [0093]    Referring to FIG. 4, a further record, namely record  7 , identified by reference numeral  700 , contains the fields “person&#39;s host access ID”  701 , “resource ID”  702 , “resource (sold, free, consumed)”  703 , and “volume of resource sold, free or consumed”  704 . Record  7 , in combination with record  4 , assists originators  20  in following the sale of the services to ensure that not more than the total number of services are sold or consumed.  
         [0094]    Initially, before any sales, record  7  for originator A for host H 1  and service S 1  will read “A_H 1 _Access, H 1 _S 1 _ 1 , Free, Original Volume D”. After the sales referred to above and illustrated in FIG. 2, record  7  will contain the information appearing in FIG. 5B for originator A. Similar information will be stored in record  7  for the other hosts H 2  and H 3 .  
         [0095]    Likewise, originator D will have a record  7  for host H 4 , which in FIG. 6A shows the initial condition before any sales occur. It is clear that the total volume of the services S consumed or sold will eventually equal the original volume V.  
         [0096]    It will be understood that, although various features of the invention have been described with respect to one or another of the embodiments of the invention, the various features and embodiments of the invention may be combined or used in conjunction with other features and embodiments of the invention as described and illustrated herein.  
         [0097]    Although this disclosure has described and illustrated certain preferred embodiments of the invention, it is to be understood that the invention is not restricted to these particular embodiments. Rather, the invention includes all embodiments which are functional, mechanical or electrical equivalents of the specific embodiments and features that have been described and illustrated herein.