Patent Abstract:
A system for providing group accessibility is provided. An example method includes storing a profile associated with a user in a database; maintaining a service group including a plurality of service representatives in the database; and in response to a session between the user and a first one of the service representatives: adding, with a processor, the service group to the profile associated with the user; and associating a rule with the profile to cause the service group to be indicated to the user as present on a network only when the first service representative is present on the network.

Full Description:
RELATED APPLICATIONS 
     This patent arises from a continuation of U.S. patent application Ser. No. 11/842,236, filed Aug. 21, 2007, now U.S. Pat. No. 7,831,664, which is a continuation of U.S. patent application Ser. No. 10/223,858, filed Aug. 19, 2002, now U.S. Pat. No. 7,263,535, which claims priority to U.S. Provisional Patent Application No. 60/382,106, filed May 21, 2002, each of which is hereby incorporated herein by reference in its entirety. 
    
    
     FIELD OF THE DISCLOSURE 
     The present invention is generally related to telecommunications and more particularly to services provided to clients via instant messaging applications. 
     BACKGROUND 
     The development of the internet has driven vast technological developments, particularly in the areas of networking hardware and software. Networking hardware developments have enabled networks to transfer large files in fractions of a second. Software developments, such as the world-wide-web (web) and e-mail, have facilitated communications over these networks that have allowed users to remain in almost constant contact with work. These types of communications have become of utmost importance in the business setting, where response time has become a key survival factor for many companies. Other networking software has allowed users to access and run applications from remote locations, thus enabling a businessperson to remain more productive, even on a business trip. 
     Moreover, the internet has changed the way people communicate. E-mail has become the dominant means of communications in many settings, being preferred over traditional mail, and even telephones in some cases. Almost instantaneous communication with little charge has driven much of the popularity of e-mail. Once used only in university and military settings, e-mail has gained widespread public acceptance. 
     In a world economy based largely upon communication, the relative speed of e-mail in comparison to traditional mail is often not fast enough or as effective. Demand for faster access to more information has resulted in the development of a number of instant messaging (IM) services. IM brings presence information into the communications arena, and it allows users to have real-time chat sessions with other users who are present on the system. The real-time nature of IM has led to quick acceptance by many in the business community of IM as an invaluable tool for communication. However, current IM systems often have administration and management problems. 
     Therefore, there is a need for systems and method that address these and/or other perceived shortcomings of the prior art. 
    
    
     
       BRIEF DESCRIPTION OF THE DRAWINGS 
       The invention can be better understood with reference to the following drawings. The components in the drawings are not necessarily to scale, emphasis instead being placed upon clearly illustrating the principles of the present invention. Moreover, in the drawings, like reference numerals designate corresponding parts throughout the several views. 
         FIG. 1A  is a block diagram illustrating an interoperability architecture for instant messaging used in one embodiment, among others, of the present invention. 
         FIG. 1B  is a block diagram illustrating an alternative embodiment, among others of an interoperability architecture for instant messaging used in one embodiment, among others, of the present invention. 
         FIG. 2  is a block diagram of the interoperability architecture used in one embodiment, among others, of the present invention. 
         FIG. 3  is a block diagram of one embodiment, among others, of a system for providing group accessibility in accordance with the present invention. 
         FIG. 4  is an embodiment, among others, of a data structure used to store groups and manage the presence of groups facilitated by the system of  FIG. 3 . 
         FIG. 5  is a flowchart illustrating operation of the system of  FIG. 3 . 
     
    
    
     DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS 
     The preferred embodiments of the present invention now will be described more fully with reference to the accompanying drawings. The invention may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein; rather, these embodiments are intended to convey the scope of the invention to those skilled in the art. Furthermore, all “examples” given herein are intended to be non-limiting. 
     Referring now to  FIG. 1A , shown is a block diagram illustrating an interoperability architecture for instant messaging used in one embodiment, among others, of the present invention. Each of a plurality of remote computers  100   a - i  access a network  110  through a local internet service provider (ISP) server  120   a ,  120   b ,  140 . The local ISP  120   a ,  120   b ,  140  can offer network  110  access through myriad connection types, including a digital subscriber line (DSL) service, an integrated services digital network (ISDN) service, an analog dial-up service, ethernet, T-1, or any other service for transmitting data through a network  110 . Universal servers  130   a - c  are located between the internet and each of local ISP servers  120   a ,  120   b , and located inside local ISP  140 . These universal servers  130   a - c  provide interoperability between a plurality of proprietary instant messaging clients  100   a - i . Of course, the scope of the presentation includes networks other than those with universal servers or instant messaging. 
     Referring now to  FIG. 1B , shown is an illustration of an alternative embodiment, among others, of a universal architecture. Greater detail regarding this interoperability architecture may be found in U.S. patent application Ser. No. 10/135,929, entitled “Instant Messaging Architecture and System for Interoperability and Presence Management,” which is hereby incorporated by reference. The universal architecture uses a universal protocol, such as the extensible markup language (XML) protocol to allow users of different ISPs  120   a ,  140  that use proprietary protocols to communicate with one another. Universal servers  130   a ,  130   c  located at each of the ISPs  120   a ,  140  are the key feature of the universal architecture.  FIG. 1B  illustrates two separate ISP networks  120   a ,  140 . The discussion of the ISP  120   a ,  140  will be limited to the components that provide the universal service. 
     The ISP  120   a  contains a local IM server  150   a , and is connected to the universal server  130   a . The local IM server  150   a  provides the standard IM function for the ISP  120   a . The universal server  130   a  provides the universal function that allows the first user  160   a , who is registered with the first ISP  120   a , to communicate with a second user  160   c  registered with the second ISP  140 . The first ISP  120   a  provides connections to a plurality of clients  170   a ,  170   b  on computers  100   a ,  100   b , which allows users  160   a ,  160   b  to access the proprietary IM and universal functions of the ISP  120   a . The first ISP  120   a  is “bimodal,” in that it uses both a proprietary and universal format to provide a proprietary IM function that only allows the users who are registered with the ISP  120   a  to send and receive instant messages. For example, if only one user has registered with the universal server  130   a , then the local IM server  150   a  will transfer instant messages between the first and second users  160   a ,  160   b  using the proprietary protocol. However, if both the first and second users  160   a ,  160   b  are registered with the universal server  130   a , then the first ISP  120   a  can transfer instant messages between them using the universal protocol. By supporting both formats at the first ISP  120   a , users can migrate to the universal format over time. When all users  160   a ,  160   b  have migrated the proprietary format can be discontinued. 
     The universal server  130   a  removes the restrictions associated with proprietary IM functions associated with the ISP  120   a . The universal server  130   a  uses a universal format, such as XML, or any other suitable format, that allows users  160   a ,  160   b  registered with an ISP  120   a , such as BellSouth DotNet, to send and receive instant messages from other users  160   c ,  160   d  registered with another ISP  140 , such as America Online (AOL). 
     The user  160   a  accesses the local IM server  150   a  of the ISP  120   a  through the IM client  170   a  located on the user&#39;s computer  100   a . The IM client  170   a  typically includes a proprietary software program that is capable of opening communications sockets that allow the IM client  170   a  to communicate with the local IM server  150   a  using either the proprietary or universal protocols. The software program is capable of formatting an instant message sent from the IM client  170   a  to the appropriate format used by the IM function of the ISP  120   a . In this manner, the user  160   a  is capable of communicating with any other user  160   b  registered with the ISP  120   a . However, the local IM server  150   a  on a first ISP  120   a  is also connected to a first universal server  130   a . The first universal server  130   a  is in turn, connected to a second universal server  130   c  on the second ISP  140  via a distributed network, such as the internet  110 . This allows the user  160   a  to communicate not only with the user  160   b  who is registered with the first ISP  120   a , but also with users  160   c  who are registered with the second ISP  140  that uses a different proprietary IM protocol to send and receive instant messages within the network of the second ISP  140 . 
     In order for the first user  160   a  to be able to send and receive messages with a third user  160   c  on the second ISP  140 , the IM client  170   a  must be able to identify the IP address and presence information associated with the third user  160   c . The presence information for the third user  160   c  is stored on the universal server  130   a  connected to the first ISP  120   a . The universal server  130   a  on the first ISP  120   a  stores the IP address and presence information for the third user  160   c . Therefore, the first user  160   a , who is registered with the universal server  130   a  on the first ISP  120   a  has access to the IP address and presence information of the third user  160   c.    
     One skilled in the art will recognize the difference between the first local ISP  120   a  and the second ISP  140 . The second local ISP  140  is an alternative embodiment that includes within the ISP  140  both the universal server  130   c  and a local IM server  150   b . Here, the local IM server  150   b  does not communicate with the universal server  130   c . Thus, the first user  160   a  will not be able to communicate with a fourth user  160   d  if the fourth user  160   d  is not registered with the universal server  130   b , but instead is only registered with a local IM server  150   b . As a result, the fourth user  160   d  is able to send and receive instant messages using only the proprietary format over local IM server  150   b . Therefore, the user  160   d  is limited to communicating via instant messages with users of the second ISP  140 , such as the third user  160   c.    
     An advantageous feature of the universal architecture is that it is designed to be easily integrated within existing ISPs  120   a ,  140 , such as AOL and Microsoft Network (MSN) without disrupting the current IM function of these ISPs  120   a ,  140 . Each ISP  120   a ,  140  that adopts the universal architecture requires only a slight modification to the existing network. The ISP  120   a ,  140  either adds a universal server  130   a  between the local IM server  150   a  and the internet  110 , or adds an additional server to function as the universal server  130   b  and can install a universal application program on the local IM server  150   a ,  150   b  and each IM client  170   a - d  attached to the network. The universal application program that is installed at each ISP  120   a ,  140  converts the ISP  120   a ,  140  to function as “bimodal.” That is, the ISP  120   a ,  140  is capable of using the proprietary IM protocol of the local IM server  150   a ,  150   b  and the universal protocol of the universal architecture. The bimodal nature of the universal architecture allows the universal server  130   a ,  130   b  to be implemented into existing ISPs  120   a ,  140  such as AOL and MSN without disrupting the current proprietary IM functions of those services. This allows the current users  160   a - d  to continue using the proprietary IM function of their particular ISP  120   a ,  140  until every user  160   a - d  can be converted to the universal protocol. 
     Referring now to  FIG. 2 , shown is a block diagram illustrating an embodiment, among others, of the universal server  130  of  FIGS. 1A  &amp; B, which is used in conjunction with an embodiment, among others, of the present invention. The client  170  includes at least three layers of functionality in one embodiment, among others, to communicate with the universal server  130 . The first layer is the presentation layer  205 . The presentation layer  205  includes the logic that is used to present the instant messenger or another application to a user. The second layer is a middleware layer  210 . The middleware layer  210  includes logic used to handle the message routing of the instant messaging application between the presentation layer  205  and the service layer  215 . The third layer is the service layer  215 . The service layer  215  handles both the applications management and communications management of the client  170 . The service layer  215  communicates with the communications layer  220  on the universal server  130 . 
     Preferably, there are three basic layers to the instant messaging service. The first layer is the communications manager (CCM)  220 . The communications manager  220  manages the connections between the client communications manager  215  and the universal server  130 . In one embodiment, among others, of the universal server  130 , communications between the client service layer  215  and the universal server  130  communications manager  220  occur in extensible markup language (XML). Further, the communications may be secure socket layer (SSL) encrypted for security. Moreover, the communications can be compressed by a compression/decompression algorithm implemented on a compression-decompression module, more commonly referred to as a CODEC, to provide faster data transfer. 
     The communications manager  220  includes a number of connection sockets between the communications manager  220  and a plurality of users. The communications manager  220  can further include a load balancer (not shown) to balance the connections over a number of different communications managers. The load balancer can maintain a connection to the same connection socket during the period while the user is logged on and connected to an operable communications manager  220 , and can automatically connect the user to an alternate connection socket when a communications manager might fail. Thus, a continuous connection can be maintained during an active session despite hardware failures. The load balancer can also protect the server against denial of service attacks, which have become increasingly prevalent on the internet. 
     A standard communications manager  220  will typically attempt to recover and reallocate a connection socket after a period of time with no activity from the client  170 . In this situation the communications manager  220  assumes that the client  170  is no longer present on the system. However, because presence is an important piece of the instant messaging architecture, the communications layer  215  on the client-side sends a signal to the universal server  130  to keep the connection socket active on the communications manager  220 . 
     The second layer is the service router  225 , with one example known as a JabberD in the Jabber architecture, such as that available from Jabber, Inc. of Denver, Colo., which performs a similar function to the message router  210  on the client side of the network. A number of different service managers  230  can be coupled to the service router  225 , each of which can provide a different service to the client  170  over the internet. Thus when a service is requested, the service router  225  routes the request to the requested service manager  230 . In the instant messaging architecture the service manager  230  is a Jabber service manager (JSM) which allows text communication between parties. The JSM  230  also keeps track of presence and roster information  235 ,  240 , respectively, for a particular user on the network who has logged into the instant messaging system. Presence  235  typically refers to the user&#39;s status on the network, while roster  240  typically refers to the status on the network of those on the user&#39;s resource list. 
     Similarly to the communications manager  220 , the service router  225  can utilize a self-similar architecture using the CODEC (not shown) and load balancer (not shown) to optimize the connection between the communications manager  220  and the service router  225 . Use of the CODEC enables high speed data transmission between the communications manager  220  and the service router  225 . The load balancer provides a robustness that allows the client to maintain contact with a selected service manager  230  during a session. 
     In one embodiment, among others, of the universal server  130 , the database containing the non-persistent data, such as presence and roster information  235 ,  240 , can be severed from the service manager  230 . The presence information  235  typically includes a list of all users who are registered with the universal server  130 , while the roster list includes a non-persistent list of those resources which are present on the network. Thus, the non-persistent data can be maintained and updated at a single database, and the plurality of service routers  225  can connect to the same presence information  235 . After severing this database from the service manager  230  the service manager  230  can be equipped, as described above, with a CODEC (not shown) and load balancer (not shown), again utilizing a self-similar architecture to provide quality of service and communication efficiencies. 
     The service router  225  is further coupled, in one embodiment, among others, to an XML database (XDB) library  245 . The XDB library  245  is used as a translator such that the service router  225  can communicate with a database system  250  that includes persistent data relating to a plurality of clients. The database system  250  which contains most of the persistent data for the services on the network, such as resource lists, preferences, etc. In one embodiment, among others, of the universal server  130  the database system  250  can be an Oracle 91 database. The XDB library  245  can be further coupled to an authentication server, such as a username and password database  255 . Thus a username and password can be required before the user is authenticated and allowed to access the database system  250  for any profile information. 
     After registering with the database system  250 , the user is provided with a resource list. The client  170  can then contact the service manager  230  to find out which of the resources on the resource list is present and/or available on the network. Typically, presence refers to the registration state of a client  170 . If a client  170  is logged-in to the network, the client  170  is present on the network. Typically, availability refers to the status of a user at the client computer. A user can be made unavailable by the network if there has been no activity on the client computer  170  for a period of time. Otherwise, a client  170  can be made unavailable by user choice, if the user does not wish to be disturbed. One skilled in the art will recognize that these are merely definitions of various states that can be defined according to any specific implementation of the presence and roster databases  235 ,  240 . Furthermore, these databases  235 ,  240  that contain non-persistent information could keep track of any other states that might be defined by the specific implementation of the service manager  230 . 
     Typically with respect to other instant messaging systems, the resource list only comprises a list of other users for which the client  170  wishes to know the status. However, the resource list of some embodiments of the present invention could include access to a plurality of applications, and there could be multiple service managers that include managers for the plurality of applications coupled to the service router  225 . These service managers could provide access to a multitude of different applications and resources, such as Microsoft Word and/or Visio, provided by Microsoft Corp. of Redmond, Wash., and/or billing entry applications, etc. Moreover, the Jabber service manager  230  could keep track of the presence of these other applications and other resources on the network. For example, if a client wished to access an e-mail account from a remote location and the system was down, the Jabber service manager  230  could alert the user that the server was down. Thus the client  170  would not waste resources searching and waiting for e-mail from a server that is off-line. 
     Thus, Jabber can be used similarly to an operating system. When a resource server  260  is present on the network, the resource(s) associated with that resource server can be displayed as an icon on the client computer display, and when a resource server is down, the resource(s) can be removed from the client computer  170  display. Thus, icons, for example, could appear and disappear from a client computer  170  display as they become present and available, and not present or unavailable. Selecting the icon while it is displayed will cause a routing request to be sent to the service router  225 . Upon receiving the routing request, the service router  225  will determine the correct routing of the routing request and deliver the proper service to the client computer  170 . 
     Referring now to  FIG. 3 , shown is an embodiment, among others, of a system for providing group accessibility. Here, the system uses a group management system  300  in conjunction with the universal server  130  of  FIG. 2  to provide group accessibility. The group management system  300  allows a group to be created in the persistent database  250 ′ under a group tag  305 . The group is similar to a newsgroup, where groups can be organized by topic and separated from one another. Moreover, the group in alternative embodiments can be created by a centralized administrator or by an individual. 
     Once the group tag  305  is created, the group management system  300  can be configured, in one embodiment, among others, to allow a user to retrieve a resource list and send the resource list, including the group tag  305 , to the Jabber service manager  230  roster database  240 . The service manager  230  can be set up to display a group tag  305  as present when at least one member  320  of the group is logged onto the universal server  130 . Thus, when a user logs-in to the server and receives the resource list, which can include the group tag  305 , and checks the status of the group tag  305 , the group tag  305  will be present when at least one of the members  320  included within the group tag  305  is logged on to the universal server  130 . Furthermore, the universal server  130  can be configured to provide the client  170  with a specific number of members of the group who are present and available. Thus, when an icon which can indicate accessibility of the group can also indicate how many members of the group are accessible. 
     In an alternative embodiment of the group management system  300 , a group could comprise a department identification, for example. When a user wishes to contact a specific member in that departmental group, the user could merely type that member&#39;s identification and temporarily bring that group member outside of the group to get status information and/or begin a chat session with that group member. 
     In another embodiment of the group management system  300 , the user may enter a rule  310  into the persistent database  250 ′ that gets read up to the Jabber service manager  230  when the group tag  305  is read up to the non-persistent roster  240 . The Jabber service manager  230  can execute the rule  310  and show the presence of a group on the client computer  170  display when the rule  310  is met. Thus, the system can be configured to indicate presence only when a particular member  320  of the group is present on the universal server  130 , according to a rule  310  entered by the user. 
     One such example where this feature would be useful is the situation where a customer chats with a member  320  of the service center group  305 . The customer can set their profile in the persistent database  250 ′ to make the service center group  305  appear present only when that same particular service center group member  320  is present. Thus the customer can later chat with the same service center group member  320  and retain some continuity in service. Moreover, the service manager  230  can, in one embodiment, among others, be designed to automatically add a service group  305  to the user&#39;s profile following a service call. The service manager  230  can further set the rule  310  such that the client  170 , can only reconnect with the same service center group member  320 . 
     One skilled in the art will recognize that multiple group members  320  can be singled out in a rule  310  to indicate presence of the group, or that the user could set the rule  310  so that the group appears present when a first, third and fourth group member are all present at the same time. This rule can be set by the user through the client  200 , the client being operable to generate user screens and prompts, and to send commands to the universal server  130 . There are myriad possible combinations to enable a group to appear present according to presence status of the group&#39;s individual members  320 , and each of those combinations are intended to be included within the scope of the present invention. 
     One skilled in the art will further recognize that in the instance where the group is a blind list (e.g. help desk, service center, technical assistance) and a user merely chooses the group (instead of an individual within the group), it would be helpful to include a rule which rotates among the group. Therefore, when there are five members available at the help desk, the first member does not receive a disproportionate number of the inquiries. This feature can be facilitated using a rule that correlates to a tag number associated with a group member&#39;s identification, and the service manager receiving the request can distribute the requests among group members by rotating numerically. Alternatively, the service manager  230  could rotate requests alphabetically. However, such an alphabetical sort typically requires more processing power than a numerical sort. 
     Referring now to  FIG. 4 , shown is an embodiment, among others, illustrating a data structure used to store the group and manage group presence of  FIG. 3 . The database typically contains a number of different user profiles  400 . Each of the user profiles  400  contain a information stored by the user associated with the profile  400 . For example, the profile  400  may contain preference information  405 , a resource list  410 , and a class of service marker  415 . 
     The preference field  405  could contain the preferences of the user. In one embodiment, among others, the user could specify to the universal server  130  that the user would like an aural notification when a user on the resource list  410  has become available. As recognized by one skilled in the art, these preferences could take many forms, and this invention is not meant to be limited merely to those preferences disclosed. 
     With regard to the resource list  410 , the user can specify a number of contacts  420 ,  425 ,  430 ,  435  at his or her pleasure. Typically, these contacts  420 ,  425 ,  430 ,  435  are those people with whom the user often communicates. The contacts listed fall into two categories, individual contacts  420 ,  425 ,  430  and group contacts  435 . Each of the individual contacts  420 ,  425 ,  430  has a unique identifier associated with the individual contact  420 ,  425 ,  430 . The group contact  435 , a service center in this example, has a number of operators  436 - 439  listed. Each of the operators  436 - 439  has a unique identifier associated with the operator  436 - 439 . These unique identifiers in alternative embodiments may or may not be viewable by the user. Moreover, the service center group  435  has a rule  440  associated with it. The rule  440  in alternative embodiments can be set by the universal server  130  or the user him/herself. The rule  440  in this embodiment tells the service manager  230  ( FIG. 3 ) that the group is only present when operator  3   438  is present and available. 
     With respect to the class of service marker  415 , the class of service marker may be used by the database  250 ″ administrator to restrict access to various resources. These resources can be other users, applications residing on a server  260  coupled to the service router  225 , or even a network connection socket. The class of service marker  415  would be read up to the client  170  upon a user logging in to the database  250 ″, and would be included with every service request received from the client  170 . It should be recognized that the class of service marker  415  can be used to facilitate a variety of different advantageous transactions, including both commercial and security driven transactions. It should be further recognized that the above data structure is merely an example of one structure that can be used, and the structure is set out only to more clearly explain the invention, rather than limit the invention. 
     Referring now to  FIG. 5 , shown is an embodiment, among others, of a flowchart illustrating the operation of the universal server including an embodiment, among others, of the group management system  300  of  FIG. 3 . The first step  500  is to create a group  305 . Typically the group  305  can be created by a centralized administrator, although it can also be created by a client  170 , or both a centralized administrator and a client  170 . In the next step  505 , the group is stored in the persistent database  250 . 
     After the group  305  is stored in the persistent database  250 , in the next step  510 , the group management system  300  checks waits for a client  170  to request the group  305 . If there has been no request, the group management system  300  continues checking for a group member  320  until one becomes present. When a group is requested, the next step  515  is to have the database pass the group  305  and any stored rules  310  to the service manager  230 . In accordance with the next step  520 , the service manager  230  then checks to see whether any group members are present. If there are group members present, in accordance with step  525  the service manager  230  checks to see if a rule  310  was passed up. If there was no rule  310  included with the group  305 , the next step  530  is for the service manager  230  to show the group  305  as present on the client computer  170  display. 
     If there is a rule  310  that was passed up with the group  305 , the service manager  230  executes the rule  310 , in accordance with step  535 . Then if the rule  310  is met, the next step  540  is to have the service manager  230  display the group  305  as present on the client computer  170  display. However, if the rule  310  is not met, the service manager  230  in the next step  545  checks to see that there is still a member  320  of the group  305  present. If there are no group members  320  present, the group  305  is passed back down to the persistent database  250 , in accordance with step  550 , and the persistent database  250 ′ waits for a group member  320  to become present. If there are still group members  320  present, the service manager  230  in step  555  checks to see whether there are any new group members  320 . If there are no new group members  320 , the service manager  230  returns to step  545 , and again checks to make sure there are still group members  320 . However, if there are new group members  320  the service manager  230  executes the rule  310 , and checks to see if the rule  310  is met. If the rule  310  is met with the new group member  320 , the service manager  230  displays the group  305  as present on the client computer  170  display. 
     Process and function descriptions and blocks in flow charts can be understood as representing, in some embodiments, modules, segments, or portions of code which include one or more executable instructions for implementing specific logical functions or steps in the process, and alternate implementations are included within the scope of the preferred embodiment of the present invention in which functions may be executed out of order from that shown or discussed, including substantially concurrently or in reverse order, depending on the functionality involved, as would be understood by those reasonably skilled in the art of the present invention. In addition, such functional elements can be implemented as logic embodied in hardware, software, firmware, or a combination thereof, among others. In some embodiments involving software implementations, such software comprises an ordered listing of executable instructions for implementing logical functions and can be embodied in any computer-readable medium for use by or in connection with an instruction execution system, apparatus, or device, such as a computer-based system, processor-containing system, or other system that can fetch the instructions from the instruction execution system, apparatus, or device and execute the instructions. In the context of this document, a computer-readable medium can be any means that can contain, store, communicate, propagate, or transport the software for use by or in connection with the instruction execution system, apparatus, or device. 
     It should be emphasized that the above-described embodiments of the present invention are merely possible examples of implementations set forth for a clear understanding of the principles of the invention. Many variations and modifications may be made to the above-described embodiment(s) of the invention without departing substantially from the principles of the invention. All such modifications and variations are intended to be included herein within the scope of this disclosure and the present invention and protected by the following claims.

Technology Classification (CPC): 8