METHOD AND SYSTEM FOR DYNAMIC APPLICATION MANAGEMENT

Abstract

A system (and method) for device-independent point to multipoint communication is disclosed. The system is configured to receive a message addressed to one or more destination users, the message type being, for example, Short Message Service (SMS), Instant Messaging (IM), E-mail, web form input, or Application Program Interface (API) function call. The system also is configured to determine information about the destination users, the information comprising preferred devices and interfaces for receiving messages, the information further comprising message receiving preferences. The system applies rules to the message based on destination user information to determine the message endpoints, the message endpoints being, for example, Short Message Service (SMS), Instant Messaging (IM), E-mail, web page output, or Application Program Interface (API) function call. The system translates the message based on the destination user information and message endpoints and transmits the message to each endpoint of the message. A system (and method) also enables user to perform a keyword search, after performing the keyword search, a result display on the first computing device to the first user, in which are displayed individual messages located in the keyword search, wherein the result display provides a graphical subscribe indicator that, when selected after the search is performed and after the individual messages are displayed, subscribes the first user to a second user who provided the selected individual message from the search results, so as to enable the first user to be a follower of the second user, wherein the first user becomes one of several followers of the second user and the second user has a second computing device and storing, by the one or more computer processors, the followers of the second user, including the first user, in a first storage. User is also enabling to post, a new message for distribution to one or more unspecified recipients wherein server identifies the followers of the posting user as recipients of the new message and sending the new message to the followers of the second user, including the first user.

Claims

1. A method of message distribution, comprising: causing to be provided on a first computing device of a first user a search display to perform a keyword search; causing to be provided, by one or more computer processors, after performing the keyword search, a result display on the first computing device to the first user, in which are displayed individual messages located in the keyword search, wherein the result display provides a graphical subscribe indicator that, when selected after the search is performed and after the individual messages are displayed, subscribes the first user to a second user who provided the selected individual message from the search results, so as to enable the first user to be a follower of the second user, wherein the first user becomes one of several followers of the second user and the second user has a second computing device; receiving, from the first computing device of the first user, a selection of a plurality of endpoints for receiving messages, wherein the first user is one of a plurality of users who are followers of the second user; storing, by the one or more computer processors, the selection of the plurality of endpoints in a third storage; storing, by the one or more computer processors, the followers of the second user, including the first user, in a first storage; receiving, from the second computing device of the second user, a new message for posting and subsequent distribution to one or more unspecified recipients; storing, by the one or more computer processors, the posted new message in a second storage; identifying, by the one or more computer processors and the first storage, the followers of the second user as recipients of the new message; and identifying, by the one or more computer processors and the third storage, the plurality of endpoints selected by the first user, wherein sending, by the one or more computer processors, includes sending the new message to each of the plurality of endpoints selected by the first user.

2. A method of message distribution according to claim 1, further comprising: receiving, from the first computing device of the first user, a selection of a plurality of endpoints for receiving messages, wherein the first user is one of a plurality of users who are followers of the second user; storing, by the one or more computer processors, the selection of the plurality of endpoints in a third storage; and identifying, by the one or more computer processors and the third storage, the plurality of endpoints selected by the first user, wherein the sending of the new message includes sending the new message to each of the plurality of endpoints selected by the first user.

3. A method of message distribution, comprising: causing to be provided on a first computing device of a first user a search display to perform a keyword search; causing to be provided, by one or more computer processors, after performing the keyword search, a user result display on the first computing device to the first user, in which are displayed a list of users located in the keyword search, wherein the user result display provides a graphical subscribe indicator that, when selected after the search is performed and after the list of users is displayed, subscribes the first user to a second user from the list of users, so as to enable the first user to be a follower of the second user, wherein the first user becomes one of several followers of the second user and the second user has a second computing device; storing, by the one or more computer processors, the followers of the second user, including the first user, in a first storage; receiving, from the second computing device of the second user, a new message for posting and subsequent distribution to one or more unspecified recipients; storing, by the one or more computer processors, the posted new message in a second storage; identifying, by the one or more computer processors and the first storage, the followers of the second user as recipients of the new message; and sending, by the one or more computer processors, the new message to the followers of the second user, including the first user.

4. A method of message distribution according to claim 3, further comprising: receiving, from the first computing device of the first user, a selection of a plurality of endpoints for receiving messages, wherein the first user is one of a plurality of users who are followers of the second user; storing, by the one or more computer processors, the selection of the plurality of endpoints in a third storage; and identifying, by the one or more computer processors and the third storage, the plurality of endpoints selected by the first user, wherein the sending of the new message includes sending the new message to each of the plurality of endpoints selected by the first user.

5. A method of message distribution according to claim 3, further comprising: causing to be provided, by one or more computer processors, after performing the keyword search, a message result display on the first computing device to the first user, in which are displayed individual messages located in the keyword search, wherein the message result display provides a graphical subscribe indicator that, when selected after the search is performed and after the individual messages are displayed, subscribes the first user to a second user who provided the selected individual message from the search results, so as to enable the first user to be a follower of the second user, wherein the first user becomes one of several followers of the second user.

6. A method of message distribution according to claim 4, further comprising: receiving, from the first computing device of the first user, a selection of a plurality of endpoints for receiving messages, wherein the first user is one of a plurality of users who are followers of the second user; storing, by the one or more computer processors, the selection of the plurality of endpoints in a third storage; and identifying, by the one or more computer processors and the third storage, the plurality of endpoints selected by the first user, wherein the sending of the new message includes sending the new message to each of the plurality of endpoints selected by the first user.

Description

BRIEF DESCRIPTION OF THE DRAWINGS

[0232] Further aspects of the present invention will become apparent from the following description which is given by way of example only and with reference to the accompanying drawings in which:

[0233] For illustrative purposes, some embodiment of the UHSF system software component are described below in which each of specific UHSF embodiments are providing various types of capabilities and functionalities with respect to various types of actions, operations and time of use, using various specific types of user interfaces and other communication and interactions including searching of various databases via said interfaces and various tools embedded exclusively and separately providing those claimed functionalities and capabilities. However those skilled in the art will appreciate that the techniques taught in this invention can be used in a variety of other situations, including services, tools and methods in part or in full in the connected digital media, internet and peer to peer distributed environment, and that the invention is not limited to the exemplary details provided.

[0234] FIG. 1 shows a schematic block diagram of a preferred embodiment of Universal Human Service Framework (UHSF) illustrating structural connection of each operational channel nodes with the HSN controller alongwith the relationship aspects thereof

[0235] FIG. 2 shows a schematic block diagram of a preferred embodiment of Universal Human Service Framework (UHSF) illustrating structural connection of developer nodes in the peer to peer environment alongwith the relationship aspects thereof with the other channel nodes and HSN controller.

[0236] FIG. 3 shows a schematic block diagram of a preferred embodiment of HumanServiceNet Service Provider (HSNSP) illustrating each relational communication modality with other channel nodes therein the UHSF system alongwith possible tools and methodology for service offering thereof.

[0237] FIG. 4 shows a schematic block diagram of a preferred embodiment of HumanServiceNet Human Agent (HSNHA) illustrating each relational communication modality with other channel nodes therein the UHSF system alongwith possible tools and methodology for service offering thereof.

[0238] FIG. 5 shows a schematic block diagram of a preferred embodiment of HumanServiceNet Broker (HSNB) illustrating relational engagement and communication modality thereof with multiple subscriber and multiple Human Agent nodes therein the UHSF system.

[0239] FIG. 6 shows a schematic block diagram of a preferred embodiment of HumanServiceNet subscriber (HSNS) illustrating each relational communication modality with other channel nodes therein the UHSF system alongwith possible tools and methodology for service offering.

[0240] FIG. 7 shows a logical block diagram of HumanServiceNet Framework illustrating each of the relational engagement of each of the channel node alongwith communication and service or product offering inter-engagements thereof in the inter-channel and intra-channel mode of operandi.

[0241] FIG. 8 shows a logical connection diagram of HumanServiceNet (HSN) active HumanServiceNet Explorer (HSNE) illustrating collapsible tree representing each of channel node wise segregation of control and management information and multiple tools employed therefor.

[0242] FIG. 9 shows a logical connection diagram of extended view of FIG. 8.

[0243] FIG. 10 shows a logical connection diagram of extended view of FIG. 8.

[0244] FIG. 11 shows a logical connection diagram of Developer (HSND) active HumanServiceNet Explorer (HSNE) illustrating collapsible tree representing each of channel node wise segregation of management information and multiple tools employed therefor.

[0245] FIG. 12 shows a logical connection diagram of Service Provider (HSNSP) active HumanServiceNet Explorer (HSNE) illustrating collapsible tree representing each of channel node wise segregation of control and management information and multiple tools employed therefor.

[0246] FIG. 13 shows a logical connection diagram of Human Agent (HSNHA) active HumanServiceNet Explorer (HSNE) illustrating collapsible tree representing each of channel node wise segregation of control and management information and multiple tools employed therefor.

[0247] FIG. 14 shows a logical connection diagram of Subscriber (HSNS) active HumanServiceNet Explorer (HSNE) illustrating collapsible tree representing each of channel node wise segregation of control and management information and multiple tools employed therefor.

[0248] FIG. 15 shows a logical connection diagram of Broker (HSNB) active HumanServiceNet Explorer (HSNE) illustrating collapsible tree representing each of channel node wise segregation of control and management information and multiple tools employed therefor.

[0249] FIG. 16 shows a logical connection line diagram of Universal HumanServiceNet Framework (UHSF) illustrating all possible combinations of Peer to Peer (Human to Human & Machine to Machine) relational connections.

[0250] FIG. 17 shows a logical block diagram of HumanServiceNet Framework's Namespace or URI or Domain Name (URL) illustrating multiple identifier and example of path traversal for representation thereof.

[0251] FIG. 18 showing comprehensive view of operational graphical user interface (GUI) for Subscriber (HSNS) illustrating the HumanServiceNet Messenger (HSNM) & HumanServiceNet Explorer (HSNE) positioned therein alongwith workspace, Match Engine and communication interface therefor.

[0252] FIG. 19 illustrates example of graphical user interface (GUI) for HumanServiceNet Subscriber (HSNS) active Organizer & Message Manager and multiple query formulation tools therefor.

[0253] FIG. 20 illustrates example of graphical user interface (GUI) for Subscriber (HSNS) active Journal illustrating multiple entries details therein the said journal.

[0254] FIG. 21 showing comprehensive view of operational graphical user interface (GUI) for Human Agent (HSNHA) illustrating the HumanServiceNet Messenger (HSNM) & HumanServiceNet Explorer (HSNE) positioned therein alongwith workspace, Match Engine and communication interface therefor.

[0255] FIG. 22 illustrates example of graphical user interface (GUI) for HumanServiceNet Human Agent (HSNHA) active Organizer & Answer Manager and multiple query answering tools therefor.

[0256] FIG. 23 illustrate example of graphical user interface (GUI) for Human Agent (HSNHA) active Journal illustrating multiple entries details therein the said journal.

[0257] FIG. 24 illustrate example of graphical user interface (GUI) for Subscriber active composite search engine alongwith the multiple search results thereof and multiple searching tools therefor.

[0258] FIG. 25 illustrate example of graphical user interface (GUI) for Human Agent active composite search engine alongwith the multiple search results thereof and multiple searching tools therefor.

[0259] FIG. 26 illustrate example of graphical user interface (GUI) for Service Provider (HSNSP) active wizards illustrating each of GUI for each of channel node and HSN controller alongwith the formatting parameters thereof.

[0260] FIGS. 27 and 28 illustrate examples of graphical user interface (GUI) for Human Agent (HSNHA) active wizards illustrating each of GUI for each of channel node and HSN controller alongwith the formatting parameters thereof.

[0261] FIGS. 29 and 30 illustrate examples of graphical user interface (GUI) for Subscriber (HSNS) active wizards illustrating each of GUI for each of channel node and HSN controller alongwith the formatting parameters thereof.

[0262] FIG. 31 illustrate examples of graphical user interface (GUI) for Developers (HSND) active wizards illustrating each of GUI for each of channel node and HSN controller alongwith the formatting parameters thereof.

[0263] FIG. 32 illustrate algorithmic sequences flowchart for each of channel node registering for HOS products with the HumanServiceNet Controller.

[0264] FIG. 33 illustrate algorithmic sequences flowchart of the Developers' development proposition, registration and certification methodology.

[0265] FIG. 34 illustrate algorithmic sequences flowchart of the Service providers' service offering proposition, registration and certification methodology.

[0266] FIG. 35 illustrate algorithmic sequences flowchart of the Human Agent service proposition, registration and certification methodology

[0267] FIG. 36 illustrate algorithmic sequences flowchart of the Brokers' service proposition, registration and certification methodology.

[0268] FIG. 37 illustrate algorithmic sequences flowchart of Subscribers' Paid Certification and Registration methodology with HSN Controller

[0269] FIG. 38 illustrate algorithmic sequences flowchart of Registration of Human Agents', Service Providers' and Subscribers' with HSN Developer via HumanServiceNet.

[0270] FIG. 39 illustrate algorithmic sequences flowchart of Selective Multi Services Subscription request by plurality of channel nodes and its processing by HumanServiceNet Controller and package key issuance thereby.

[0271] FIG. 40 illustrate algorithmic sequences flowchart of Selective Multi Services Subscription request by plurality of channel nodes and its processing by Service Providers and package key issuance thereby.

[0272] FIG. 41 illustrate algorithmic sequences flowchart of Selective Multi Services Subscription request for AI Agents by plurality of channel nodes and its processing by Developers and package key issuance thereby.

[0273] FIG. 42 illustrate algorithmic sequences flowchart of Selective Multi Services Subscription request for knowledge invocation (KIS) and knowledge support services (KSS) by one or more subscribers & Human Agents and its processing by Human Agent and package key issuance thereby.

[0274] FIG. 43 illustrate algorithmic sequences flowchart of Selective Multi Services Subscription request for intermediary services by one or more subscribers & Human Agents and its processing by the Broker and package key issuance thereby.

[0275] FIG. 44 illustrate algorithmic sequences flowchart of service delivery model of the Service Providers displaying multiple communications with the multiple other Service Providers, subscribers & Human Agents.

[0276] FIG. 45 illustrate algorithmic sequences flowchart of service delivery model of the AI Agents displaying multiple communications with the multiple channel nodes.

[0277] FIG. 46 illustrates algorithmic sequences flowchart of service delivery model of the Human Agents displaying multiple communications with the multiple channel nodes and one or more Human Circles thereof.

[0278] FIG. 47 illustrate algorithmic sequences flowchart of service delivery model of the Brokers displaying multiple communications with the multiple Subscribers and Human Agents.

[0279] FIG. 48 illustrate algorithmic sequences flowchart of communication model of the Subscribers displaying multiple communications with the multiple channel nodes, including social personal group thereof and with the HSN controller.

[0280] FIG. 49 illustrate algorithmic sequences flowchart of each of CHN's Service Package Keys Management displaying multiple package key configuring parameters related to each of subscriber thereof.

[0281] FIG. 50 illustrate algorithmic sequences flowchart of each of CHN's product Keys Management displaying multiple product key configuring parameters related to each of subscriber thereof

[0282] FIG. 51 illustrates a flow diagram of HSN Default Multi AI Agents and AI Agent enabled Services (AIS) working modality including its development, registration and subscription flow and exploitation for automation.

[0283] FIG. 52 showing comprehensive view of operational graphical user interface (GUI) for Email Service (HSNEM), Massaging, Notification and Communication System illustrate HumanServiceNet Email Service interface therein.

[0284] FIG. 53 showing comprehensive view of the graphical user interface (GUI) for HumanServiceNet Online Portal (HSNOP) illustrates the possible knowledge fields and tools therefor.

[0285] FIG. 54 illustrates Holistic View of Universal Human Service framework's (UHSF) Operating System (HOS) displaying the layered segregated circular operating tiers necessary for service integration.

[0286] FIG. 55 showing graphical user interface (GUI) for HumanServiceNet Replication & Synchronization Manager (Publisher) illustrate multiple tools responsible for Synchronization and Replication of Services including Source links, applications and Contents alongwith the replication explorer thereof.

[0287] FIG. 56 shows a logical block diagram of HumanServiceNet (HSN) Replication Topology Models illustrate the replication topology of each of CHN as per protocols thereof.

[0288] FIG. 57 showing graphical user interface (GUI) for binding human services from the UHSF system via web services with the 3.sup.rd party software and web sites like e-commerce, search engine and other web sites illustrate the required tools therefor.

[0289] FIG. 58 shows discrete services which Human Grid can integrate for true universal operation.

[0290] FIG. 59 shows a logical segregation of Human Grid in term of multiple Sub-Grids and integration thereof.

[0291] FIG. 60 showing graphical user interface (GUI) for Human Services Aggregation, Integration, Collaboration, Composition, Comparison, Co-ordination, Workflow, Orchestration and Choreography Manager for HumanServiceNet Subscribers [HSNS].

[0292] FIG. 61 showing graphical user interface (GUI) for Human Services Federation, Aggregation, Integration, Collaboration, Composition, Co-ordination, Workflow, Orchestration and Choreography Manager for HumanServiceNet Human Agents[HSNHA].

[0293] FIG. 62 showing graphical user interface (GUI) for HumanServiceNet Query Manager illustrate multiple tools for knowledge invocation and management thereof alongwith the pane showing answers to the posted query.

[0294] FIG. 63 showing graphical user interface (GUI) for Hit Statistics Manager for HSN Controller illustrate the hit statistics for each of the channel node.

[0295] FIG. 64 showing graphical user interface (GUI) for Hit Statistics Manager for HumanServiceNet Developer (HSND), HumanServiceNet Human Agent (HSNHA), HumanServiceNet AI Agent (HSNAIA), HumanServiceNet Service Provider (HSNSP) and HumanServiceNet Broker (HSNB) and Hit Managements' menu options.

[0296] FIG. 65 showing graphical user interface (GUI) for Multi Rank System for HumanServiceNet (HSN), HumanServiceNet Human Agent (HSNHA) and HumanServiceNet Subscriber (HSNS).

[0297] FIG. 66 showing a logical block diagram illustrates the scheme for Searching & Matching of Subscribers for Contents & Sources, mode of communication therewith and associated advertising of contents by each of CHN.

[0298] FIG. 67 showing a logical block diagram illustrates logical connection of each of supernode with the CHN, HSNS and the HSN controller, composition of a supernode and taxonomically organized connectivity of each of SN components for search and match of HSNS.

[0299] FIG. 68 showing a logical functioning of Spider agent of a supernode and integration of each of action agents alongwith relation data handling thereby each of action agent.

[0300] FIG. 69 showing an interface for management of knowledge support services (KSS) illustrates the KSS project explorer, workspace explorer, KSS status and plurality of management tools.

[0301] FIG. 70 showing a logical block diagram illustrate HSNS universal profile creation and updation at a supernode via survey system.

[0302] FIG. 71 showing an interface for management of subscriber support services (SSS) illustrates the SSS project explorer, workspace explorer, SSS status and plurality of management tools.

[0303] FIG. 72 shows a logical block diagram illustrate developers dissemination pattern of Rule Enabled applications [REA], rule enabled services [RES] and rule wizards including functioning of various components, and data flow in the Rules-Based System.

[0304] FIG. 73 showing a logical block diagram of Black-Box Searching (BBS) system illustrates internal components of BBS system and its functioning in the keyword handling from the CHN.

[0305] FIG. 74 showing a logical block diagram of Universal Distributed (P2P) Knowledge and Information Database (UKID) system illustrate a method for Creation, Searching, Organization and Management of plurality of UKID and LKID structures and replication thereof.

[0306] FIG. 75 showing a logical block diagram of HSN AdRouting System illustrates system components for advertisement storage, customer tracking and a method for advertisement relevancy optimization.

[0307] FIG. 76 illustrates a graphical user interface (GUI) for search macro management.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0308] FIG. 1 illustrate a schematic block diagram of an essential embodiment of the Universal Human Service Framework (UHSF) showing the primary and rudimentary structural connections of the components, describing the provisions for Human service net controller (1A) as a UHSF network controller and regulator of the plurality of operations in the network and is connected with various other plurality of operating components preferably known as channel nodes in the network 1I denoting the developer component, 1J denoting the service provider component, 1K denoting the Human Agent component, 1L denoting the broker component, IM denoting the subscriber component, and IN denoting the Artificial intelligent agent component. Furthermore the network connection lines signifying the relationship aspect of the each operational channel nodes with the HSN controller alongwith the relationship aspects thereof. 1B-1E illustrating a typical composition of the HSN controller server wherein HSN controller server (1A) forms a web server containing a cluster of servers and peer to peer coordination & discovery server, for (1B) hosting database, (1C) a MS SQL Server meant for acting as repository to all UHSF system data is communicating via protocol, (1E) a web server operating via HTTP is a means for offering online portal for UHSF activities using business logic which are in the form of web services e.g. (1D) .Net web service and hosts Human Services and other HSN Services in the form of web services. FTP Server (1F) for file and products downloading including but not limited to HSNM, HSNEM, and Applications & AI Agents. HSN E-Mail Server (1G) to provide E-Mail services via SMTP and POP and other E-Mail protocols. 1I to 1M shows multiple services and products provided by HumanServiceNet Controller to all other nodes

[0309] FIG. 2 shows a schematic block diagram of a preferred embodiment of Universal Human Service Framework (UHSF) illustrating structural connection of developer nodes in the peer to peer environment alongwith the relationship aspects thereof with the other channel nodes and HSN controller. 2A-2G illustrating preferred components of present web server so as to establish connection with the various HumanServiceNet Channel nodes and internet framework wherein the network connection lines signifying the relationship aspect of the each operational channel node with the said developer alongwith the relationship aspects thereof. Notably enough each of channel nodes is preidentified with specific functionalities and requirements. The enablement of the said functionalities is requiring various applications and utilities, various developers providing the required applications, utilities, add-ons and AI agents to various channel nodes, the connection lines indicating the transmission of the same by means of product or package key. Wherein (2A) shows a host computer, for HumanServiceNet Developers (HSND), in the form of web server containing a cluster of servers and peer to peer coordination & discovery server, for (2B) hosting database, (2C) MS SQL Server communicate via protocol, (2E) HTTP using business logic which are in the form of web services, (2D) .Net web service for providing related services to the related parties and provide Centralize downloads or upload for modules, demo & like so and its Updates & Upgrades via (2F) FTP web server, communicate to the all related parties, (2J) HumanServiceNet, (2K) HumanServiceNet Developer (HSND), (2L) HumanServiceNet Service Provider (HSNSP), (2M) HumanServiceNet Human Agent (HSNHA), (2N) HumanServiceNet Subscriber (HSNS) & other 3.sup.rd parties via (2G) Mail Server and all other required services and (2I) Peer to Peer sharing and communication with all related CHN

[0310] FIG. 3 shows a schematic block diagram of a preferred embodiment of HumanServiceNet Service Provider (HSNSP) illustrating each relational communication modality with other channel nodes and peer service providers therein the UHSF system wherein the communication tool including HSNM, HSNE, HSNEM, and HSNOP facilitating the communication for service offering thereof, the network connectivity is illustrated in various modes including peer to peer and via web server wherein each of operational modes for multidevice (3I) enablement is represented alongwith multiuser (3F) operation and multiclient usability in the various smart devices (3J) thereof. (3A) illustrates a computer for HumanServiceNet Service Provider (HSNSP) on which (3B) Multi AI Agents and (3C) communication, management & other utilities are installed to provide Domain Server Admin capability to the provider to facilitate Communication using Selective multi AI Agents, applications, utilities & Add-On from selective (3N) HSN Developers, Selective multi Collaboration for Selective Multi Services from (3O) HSN Service Providers, Provides Selective Multi Services to (3P) subscribed HSN Human Agents and Provides Selective Multi Services to (3Q) subscribed HSN Subscribers. (3A) HSNSP could have multiple domains and (3F) Multi User & Admin levels capability, could share & synchronized data, share files and communicate via (3G) web server remotely with (3H) Remote Server and/or with other Domain Server for Collaboration via (3K) peer to peer with (3L) Remote Server and/or with other Domain Server for collaboration or with other (3J) Multiple Client e.g. PDA, Mobile etc (3D) HSNOP or using (3E) 3.sup.rd parties application, utilities, tools & services and/or share & synchronized data within the modules using connected (3I) Multi Devices for the same.

[0311] FIG. 4 shows a schematic block diagram of a preferred embodiment of HumanServiceNet Human Agent (HSNHA) illustrating each relational functional protocol based communication modality with other channel nodes and peer service providers therein the UHSF system wherein the communication tool including HSNM, HSNE, HSNEM, and HSNOP facilitating the communication for service offering thereof, the network connectivity is illustrated in various modes including peer to peer and via web server wherein each of operational modes for multidevice (4I) enablement is represented alongwith multiuser (4F) operation and multiclient usability in the various smart devices (4J) thereof. (4A) illustrates a computer for HumanServiceNet Human Agent (HSNHA) on which (4B) Multi AI Agents and (4C) communication, various management & other utilities are installed to provide Domain Server Admin capability to the Human Agent to facilitate Communication using Selective multi AI Agents, applications, utilities & Add-On from selective (4O) HSN Developers, Selective multi Collaboration for Selective Multi Services from (4Q) Human Agents, Provides Selective Multi Services to (4P) subscribed HSN service providers and Provides Selective Multi Services to (4S) subscribed HSN Subscribers and (4R) Brokers. (4A) HSNHA could have multiple domains and (4F) Multi User & Admin levels capability, could share & synchronized data, share files and communicate via (4G) web server or via (4K) peer to peer connectivity remotely with (4H) and (4L) Remote Server and/or with other Domain Server for Collaboration or with other (4J) Multiple Client e.g. PDA, Mobile etc via (4D) HSNOP or using (4E) 3.sup.rd party application, utilities, tools & services and/or share & synchronized data within the modules using connected (4I) Multi Devices for the same.

[0312] FIG. 5 illustrates a schematic block diagram of a preferred embodiment of HumanServiceNet Brokers (HSNB) protocol based relationship and communication modality via peer to peer and web server wherein 5A, a broker's host computer characterizing the general computing aspects of the broker and communication channel of the said broker with the various component of a typical web server comprising a cluster of servers and peer to peer coordination & discovery server, (5B) hosting database, (5C) MS SQL Server communicate via protocol, (5E) HTTP using business logic which are in the form of web services, (5D) .Net web service for providing related services to the related parties and provide Centralize downloads or upload for modules, demo & like so and its Updates & Upgrades via (5F) FTP web server, communicate to the all related parties i.e. (5I) HumanServiceNet, (5J) HumanServiceNet Human Agent (HSNHA), (5K) HumanServiceNet Subscriber (HSNS) & other 3.sup.rd parties via (5G) Mail Server and all other required services. Each of broker channel node the UHSF system by default protocol communicating with various human agents and subscribers. The broker is meant for facilitation of services of the said human agents to the appropriately matched subscribers wherein each of brokers analyzing and categorizing various services of various human agents so as to provide cost effective and reliable services sources to various subscribers and receiving the predefined or preagreed uni-way or bi-way commission in the said service subscription transaction via same intermediate link of communication between human agent and the subscriber.

[0313] As the UHSF system is primarily meant for providing value added knowledge invocation and support services to each of service subscriber. Each of subscribers is essentially connected with every service and product procurement sources as illustrated in the FIG. 6 showing functional protocol based relationships of HumanServiceNet Subscriber (HSNS) with all HumanServiceNet channel nodes and various communication tools including HSNM & HSNE, HSNEM and HSNOP so as to establish said communication links. The host computer (6A) Subscriber (HSNS) is being installed with HSNM & HSNE, (6B) Multi AI Agents and (6C) communication, management & other utilities providing Admin capability to the subscriber to facilitate communication using selective Multi Services from (6M) HSN, Selective Multi AI Agents, applications, utilities & Add-On from selective (6O) HSN Developers, Selective Multi Services from Selective multi (6P) Human Agents, Selective Multi Services from Selective (6Q) Brokers and Selective Multi Resources from Selective (6R) Subscribers of Personal Networks, using (6J) Multi client e.g. PDA, Mobile etc, (6D) HSNOP or using (6E) 3.sup.rd parties application, utilities, tools & services as well as to create (6L) Personal Network. (6A) illustrates a computer for HumanServiceNet Subscriber (HSNS), could have multiple members and (6F) Multi User & Admin levels capability, could share & synchronized data, share files and communicate via (6G) web server remotely with (6H) Remote Server and/or via (6K) peer to peer with (6L) Remote Server or with other members and/or share & synchronized data within the modules and use connected (6I) Multi Devices for the same.

[0314] In the UHSF system framework each of channel node communicate and transact with other channel node via predefined protocols wherein the knowledge communication being facilitated by means of various tools wherein FIG. 7 illustrates a logical block diagram of Universal Human Service Framework (UHSF) characterizing each of protocol based transaction amongst all the channel nodes illustrating interrelation map of all the channel nodes. The HSN Controller (7A) being connected via segmented lines to each of channel nodes offering various regulatory services and functional products including HumanServiceNet Messenger (HSNM) & HumanServiceNet Explorer (HSNE), HumanServiceNet E-Mail (HSNEM) and HumanServiceNet Online Portal (HSNOP) to each of channel nodes possessing active rights therefore, wherein the active rights are determined by means of product or package key issued by HSN controller in respect of the said channel node. Each of Developers (HSND) collaborating, and issuing product or package key to human agents, subscribers and providers with respect to product request therefrom and developing Multi AI Agents, Applications and Utilities & Add-On independently or collaboratively upon receiving license from HSN Controller, wherein each of subscriber mainly utilizing the human knowledge services from various human agents (7D) or from the brokers (7E) and from various service providers (7C) thereof by means of package key via various transmission modalities including peer to peer, or via web service or via web services or via AI agents. The subscribers are forming various personal as well as social networks and using the same via multi-client or multidevices enablement. Service providers (HSNSP) providing rule enabled services (RES), AI enabled services (AIS) and sponsored support services (SSP) to each of requesting human agents and subscribers and (7E) Broker (HSNB) offering intermediary services facilitation services via Package Key. (7F) Subscriber (HSNS) node alternatively can work in standalone or have client-server methodology and link with other client like online or mobile to exchange & Share data or link peer to peer to share files and share & synchronized data, communication remotely or with other members with restricted permission by exploiting the existing communication standards and modalities, however utilizing the service subscription management including rights and privileges administration.

[0315] In a methodological embodiment of HumanServiceNet, illustration 8 through 10 represents the organizational framework and control & management utilities for continues regulation & governance by each entity as per importance and functionalities attached therewith.

[0316] FIG. 8 shows a logical connection diagram of HumanServiceNet (HSN) active HumanServiceNet Explorer (HSNE) illustrating collapsible tree representing each of channel node wise segregation of control and management information and multiple tools employed therefor wherein 8C-8I showing the data arrangement of each of channel node in the HSN controller's explorer. The said explorer is meant for management of each of data related to each of channel node alongwith the repositories for various administrative data. The functional aspect of each of channel node is managed via various management utilities, product management, and service management. The functional utilities illustrated herein are examples of the interface of the explorer not essentially covering the said functions and not excluding the other which are not represented herein. The various management functions includes Reports and Analysis, Ontology & Taxonomy Management, Content Management, HSNOP Management, Monitoring, Security, Action, Statistics & Analysis Management, Communication (Complaints, Supports, Feedbacks, Requests), Backup & Restore, Advertising Management, Administration, HSN Wizards (HSND Management, HSNHA Management, HSNSP Management, HSNAIA Management, HSNS Management, HSNB Management), Synchronization, E-Commerce Management, Multi AI Agents Management, Rules Wizard, Rules Management, UKID Structure & software/tools Management, Survey Management, Query Manager, CHN Accounts for Commission and Settings, each of function facilitating HSN controller management of various essential functions. Likewise the product management utilities facilitating generation, configuration of product keys for various products, upgrades, updates and uploading of the same via FTP module. In the service management utilities facilitating package key configuration, generation and maintaining various repositories and comprising various preservice and postservice related miscellaneous function management modules including Reporting Service, Directories, Repositories & Inventories (HSN (Public Contents), HSND, HSNHA (KIS, KSS, HC, FS, RES, AIS, SSP), HSNB, HSNSP (KIS, FS, RES, AIS, SSP), HSNS (SSS), HSNAI-HSNAIS, Super Nodes, Rules, Ontology & Taxonomy, UKID Structures, Web Services, Resources Offerings, Survey Forms, Advertisings, Publications, Auto Content Providers, CHN's Dynamic Relationships & Metadata Journal (For Explorer), Online HSNEM, HSNOP, Identity, Registration & Authentication, Alerts & Notification, Certification & Agreements, Replication, Search Engine, Match Engine, Rank Service, Brokering, Testing, Statistics & Analysis, Payment, Advertising, E-Commerce, Accounts & Metering, 3rd Party Services, Web Hosting, and Peer to Peer Co-ordination & Discovery server wherein each of the said functions are performed via the software modules thereof and are integrated for combine relational data management having checks and permissions and event actuation of the said data-contents.

[0317] The explorer pane at the left side of the interface is being managed via Explorer Management utilities wherein facilitating searching, filtering, sorting, Selecting Views, Replicating, Administering, and showing properties of respective channel node details

[0318] FIGS. 9 and 10 showing the extended view of FIG. 8 illustrating events and historical data related attributes referring to each of channel node as represented by 8C to 8I.

[0319] (8I) illustrates the HumanServiceNet Explorer (HSNE) part of HumanServiceNet Client Software preferably HumanServiceNet Messenger (HSNM) (HumanServiceNet Active) which lists the in-depth details related to the HumanServiceNet Services and related channel node subscribers i.e. HumanServiceNet Developer (HSND), HumanServiceNet Service Provider (HSNSP), HumanServiceNet AI Agent (HSNAIA), HumanServiceNet Human Agent (HSNHA), HumanServiceNet Broker (HSNB), HumanServiceNet Subscriber (HSNS).

[0320] (8C) illustrates the HumanServiceNet Explorer (HSNE) part of HumanServiceNet Client Software preferably HumanServiceNet Messenger (HSNM) (HumanServiceNet Active) which lists the in-depth details related to the HumanServiceNet Service Provider (HSNSP) that show the list of providers & its details in tree format the same be devised so that each higher attribute encircles the following one in a concentric encircled map. The explorer tree represents classification as per dynamic taxonomy management preferably Fields followed by Location followed by Providers (Domains). The explorer tree show (9A) a) details of specific HumanServiceNet Service Provider (HSNSP) services, b) details of HumanServiceNet services used by specific HumanServiceNet Service Provider (HSNSP) c) details of Developers from whom Multi AI Agents, Applications, Utilities & Add-On purchased by a specific HumanServiceNet Service Provider (HSNSP), d) details of collaboration with other HumanServiceNet Service Providers (HSNSP), e) details of HumanServiceNet AI Agents (HSNAIA), HumanServiceNet Human Agents (HSNHA) & HumanServiceNet Subscribers (HSNS) subscribed for services.

[0321] (8D) illustrates the HumanServiceNet Explorer (HSNE) aspect of HumanServiceNet Messenger (HSNM) (HumanServiceNet Active) which list the in depth details related to the HumanServiceNet Developers (HSND) which show the list of developers & its details in tree format the same being devised so that each higher attribute encircles the following one in a concentric encircled map. The explorer tree represents classification as per dynamic taxonomy management preferably Fields followed by Location followed by Domains followed by Developers. The explorer tree show (9B) a) details of HumanServiceNet Multi AI Agents, Applications, Utilities & Add-On developed by a specific developer, b) list and details of developers for collaborative development for AI Agents, Applications, Utilities & Add-On c) details of HumanServiceNet Service Provider (HSNSP), HumanServiceNet Human Agent (HSNHA), HumanServiceNet Subscriber (HSNS) to whom HumanServiceNet Multi AI Agents, Applications, Utilities & Add-On sold by a specific developer.

[0322] (8E) illustrates the HumanServiceNet Explorer (HSNE) aspect of HumanServiceNet Messenger (HSNM) (HumanServiceNet Human Agent (HSNHA) Active) which list the in depth details related to the HumanServiceNet Human Agent (HSNHA) which show the list of HumanServiceNet Human Agent (HSNHA) & its details in tree format the same being devised so that each higher attribute encircles the following one in a concentric encircled map. The explorer tree represents classification as per dynamic taxonomy management preferably Fields followed by Location followed by HumanServiceNet Human Agent (HSNHA). The explorer tree show (10A) a) details of all services provide by specific HumanServiceNet Human Agent (HSNHA), b) details of HumanServiceNet services used by specific HumanServiceNet Human Agent (HSNHA), c) details of Developers from whom Multi AI Agents, Applications, Utilities & Add-On purchased by a specific HumanServiceNet Human Agent (HSNHA), d) details of restricted Human Circles (HC) with other HumanServiceNet Human Agent (HSNHA), e) details of multi service provided by specific HumanServiceNet Human Agent (HSNHA) to HumanServiceNet Subscribers (HSNS), f) details of HumanServiceNet AI Agents (HSNAIA), HumanServiceNet Brokers (HSNB) and HumanServiceNet Service Provider (HSNSP) services subscribed by specific HumanServiceNet Human Agent (HSNHA).

[0323] (8H) illustrates the HumanServiceNet Explorer (HSNE) aspect of HumanServiceNet Messenger (HSNM) (HumanServiceNet Subscriber (HSNS) Active) which list the in depth details related to the HumanServiceNet Subscriber (HSNS) which show the list of HumanServiceNet Subscribers (HSNS) & its details in tree format the same being devised so that each higher attribute encircles the following one in a concentric encircled map. The explorer tree represents classification as per dynamic taxonomy management preferably Fields followed by Location followed by HumanServiceNet Subscribers (HSNS). The explorer tree show (9C) a) details of all services subscribed by specific HumanServiceNet Subscriber (HSNS), b) details of HumanServiceNet services used by specific HumanServiceNet Subscriber (HSNS), c) details of Developers from whom Multi AI Agents, Applications, Utilities & Add-On purchased by a specific HumanServiceNet Subscriber (HSNS), d) details of restricted personal networks with other HumanServiceNet Subscribers (HSNS), e) details of HumanServiceNet AI Agents (HSNAIA), HumanServiceNet Human Agents (HSNHA) and HumanServiceNet Service Provider (HSNSP) services subscribed by specific HumanServiceNet Subscribers (HSNS).

[0324] FIG. 11 shows a logical connection diagram of Developer active Explorer (HSNE) illustrating collapsible tree representing each of related channel node wise segregation of control and management information and multiple tools employed therefor. (11A) illustrates the developer active explorer representing a tree structure containing information pointers and shortcut link to the related developers, providers, human agents, subscribers & 3.sup.rd parties, the explorer tree shows the purchase details of service modules of the said developer by various service provider, subscribers and human agents and the developers with whom Service Modules, Attached Utilities, Other Utilities and Application are develop collaboratively, wherein 11C-11G showing the data arrangement of each of channel node. The explorer being a means for exploring the prearranged information related to each of related channel node wherein each of developer performing the product and customer management by means of various tools provided for Accounts & Sales Status generation, Reports and Analysis generation, Explorer customization by Filtering and searching, Statistics & Analysis Management, Communication for handling Complaints, Supports, Feedbacks, Requests, HSN (Certification & Registration), performing Backup & Restore operations, Notification generation, Wizards for handling various channel nodes and formulating rules, KSS management, Query Manager and Advertising Management. Each of developer being provided with the Products Management utilities for generating, Configuring and updating the product keys and for uploading the said products via FTP module. Adjunctively each of developer providing the product subscriptions via HSNOP on predefined usage basis and by means of creating & configure package keys.

[0325] Data management being one of the significant function of the explorer, various tools for customization and for manipulating the explorer are provided therein the utilities sections facilitating searching, Filtering & Sorting, views determination, wizards execution, bookmarking, sharing and security determination, and replication of each of element in the explorer tree.

[0326] FIG. 12 shows a logical connection diagram of provider active Explorer (HSNE) illustrating collapsible tree representing each of related channel node wise segregation of control and management information and multiple tools employed therefor. (12A) illustrates the provider active explorer representing a tree structure containing information pointers and shortcut links to the related developers, providers, human agents, subscribers & 3.sup.rd parties, the explorer tree shows the subscription details of various services of the said provider by various service provider, subscribers and human agents and the developers, wherein 12C-12H showing the data arrangement of each of channel node. product and customer management by means of various tools provided for Accounts & Sales Status generation, Reports and Analysis generation, Explorer customization by Filtering and searching, Statistics & Analysis Management, Communication for handling Complaints, Supports, Feedbacks, Requests, HSN (Certification & Registration), performing Backup & Restore operations, Notification generation, Wizards for handling various channel nodes and formulating rules via rules wizards, KSS management, UKID wizard management, search macro management, Query Manager and Advertising Management. Each of provider being provided with the information storage and management utilities are generating, configuring and updating the package keys. Various tools for customization and for manipulating the explorer are provided therein the utilities sections for explorer management facilitating searching, Filtering & Sorting, views determination, wizards execution, bookmarking, sharing and security determination, and replication of each of element in the explorer tree.

[0327] FIG. 13 shows a logical connection diagram of human agent active Explorer (HSNE) illustrating collapsible tree representing each of related channel node wise segregation of control and management information and multiple tools employed therefor. (13A) illustrates the human agent active explorer representing a tree structure containing information pointers and shortcut links to the related developers, providers, human agents, subscribers & 3.sup.rd parties, the explorer tree shows the subscription details of various services of the said human agent by various service provider, subscribers and human agents and the developers, wherein 13C-13I showing the data arrangement of each of channel node product and customer management by means of various tools provided for Accounts & Sales Status generation, Reports and Analysis generation, Explorer customization by Filtering and searching, Statistics & Analysis Management, Communication for handling Complaints, Supports, Feedbacks, Requests, HSN (Certification & Registration), performing Backup & Restore operations, Notification generation, Wizards for handling various channel nodes and formulating rules via rules wizards, KSS management, UKID wizard management, search macro management, HC management, answer Manager, replication management and Advertising Management. Each of provider being provided with the information storage and management utilities are generating, configuring and updating the package keys. Various tools for customization and for manipulating the explorer are provided therein the utilities sections for explorer management facilitating searching, Filtering & Sorting, views determination, wizards execution, bookmarking, sharing and security determination, and replication of each of element in the explorer tree, wherein each of human agent initially downloading the requisite communication and software utilities from the HSN controller and developers and providing knowledge services by means of answer manager having provided with the workspaces creation and modification tools for project management. The knowledge services and knowledge support services are being offered via package keys wherein each of human agents creating, configuring various package keys.

[0328] FIG. 14 shows a logical connection diagram of subscriber active Explorer (HSNE) illustrating collapsible tree representing each of related channel node wise segregation of control and management information and multiple tools employed therefor. (14A) illustrates the subscriber active explorer representing a tree structure containing information pointers and shortcut links to the related developers, providers, human agents, subscribers & 3.sup.rd parties, the explorer tree shows the subscription details of various subscribed services of the said subscriber from various service provider, subscribers and human agents and the developers, wherein 14C-14I showing the data arrangement of each of channel node. product and customer management by means of various tools provided for Accounts & Sales Status generation, Reports and Analysis generation, search macro player and search macro management, Explorer customization by Filtering and searching, Statistics & Analysis Management, Communication for handling Complaints, Supports, Feedbacks, Requests, performing Backup & Restore operations, Notification generation, Wizards for handling various channel nodes and formulating rules via rules wizards, KSS service subscription management, SSS management, various project collaboration management, UKID wizard management, replication management, social networking management and Advertising Management. Each of subscriber posting request for package keys Various tools for customization and for manipulating the explorer are provided therein the utilities sections for explorer management facilitating searching, Filtering & Sorting, views determination, wizards execution, bookmarking, sharing and security determination, and replication of each of element in the explorer tree.

[0329] The explorer tree shows the details of (14C) HSN services and subscriptions, (14D) part of the explorer tree shows the details of developers whose service modules, attached utilities, other utilities and application are used by a service subscriber, list of other related service module developers which are further made searchable for desired attributes found with the help of search & filter and more, (14E) part of the service explorer providing details of service provider whose services are subscribed or intended to subscribed and are being bookmarked by the subscriber and the list of other related service providers which are further made searchable for desired attributes. (14G) part of the service explorer providing details of human agents whose services are subscribed or intended to subscribed and are being bookmarked by the subscriber and the list of other related human agents which are further made searchable for desired attributes. (14H) part of the service explorer providing details of brokers whose services are subscribed or intended to subscribed and are being bookmarked by the subscriber and the list of other related brokers which are further made searchable for desired attributes. (14I) part of the explorer tree shows the details of subscribers, details of services subscribed by subscriber, list of subscribers in the personal networks and list of subscribers found with the help of search & Filter for facilitating social networking.

[0330] FIG. 15 shows a logical connection diagram of broker active Explorer (HSNE) illustrating collapsible tree representing each of related channel node wise segregation of control and management information and multiple tools employed therefor. (15A) illustrates the broker active explorer representing a tree structure containing information pointers and shortcut links to the human agents and subscribers, detailing the subscription details of various services human agents and subscribers, wherein 15C-15F showing the data arrangement of human agents and subscribers channel nodes. 15B representing the management pane facilitating product and customer management by means of various tools provided for Accounts & Sales Status generation, Reports and Analysis generation, Explorer customization by Filtering and searching, Statistics & Analysis Management, Communication for handling Complaints, Supports, Feedbacks, Requests, HSN (Certification & Registration), performing Backup & Restore operations, Notification generation, Wizards for handling various channel nodes and formulating rules via rules wizards, KSS management, UKID wizard management, Query Manager and Advertising Management. Each of provider being provided with the information storage and management utilities are generating, configuring and updating the package keys. Various tools for customization and for manipulating the explorer are provided therein the utilities sections for explorer management facilitating searching, Filtering & Sorting, views determination, wizards execution, bookmarking, sharing and security determination, and replication of each of element in the explorer tree.

[0331] FIG. 16 illustrating a typical connection diagram for UHSF system, depicting mainly the protocol based relationship networking and communication patterns, wherein showing combinations of Peer to Peer Files Sharing, Data Sharing & Synchronization, and communications between all the parties in the UHSF system. Beside combination it also show the advantages Peer to Peer Files Sharing, Data Sharing & Synchronization, and communications. All connections are loosely coupled having high level of integrity to manage system resources so as to facilitate fast copying & sharing with the help of a combined browser having all the roles active rights. The peer to peer enability via said browser makes searching, matching, sharing, synchronization and communication a effective experience.

[0332] Communication has been a very systematic process since developed, it identifies source, destination and various channels of data flow. In the UHSF system as shown in FIG. 17 namespace is a tool to systematically shape up the communication channel. Namespace traverses all hierarchical nodes in the UHSF system and are separated by an interval as illustrated in an example (17M). A typical linear representation model of namespace showing 17A traveling through various nodes in a linear fashion i.e. from HSN controller to various channel nodes. This traversal is varying in nature with regards to source of the information comprising one or more optional parameters. For example with respect to channel node a typical namespace derivation stands as follows [0333] 1. HSN.Domain.HSND.<Developer Name>.ProdType.<Prod Name> [0334] 2. HSN.Domain.HSNSP.<Service Provider Name>.ServiceType.(KIS|RES|AIS|SSP|SMS).<Service Name> [0335] 3. HSN.Domain.HSNAIA.<AI Agent Name>.ServiceType.<Service Name> [0336] 4. HSN.Domain.HSNHA.<Human Agent Name>. ServiceType (KIS|KSS|RES|AIS|SSP|SMS) <Service Name> [0337] 5. HSN.Domain.HSNHA.HCIFS.<Human Agent Name>. ServiceType (KIS|KSS|RES|AIS|SSP).<Service Name> [0338] 6. HSN.Domain.Broker.<Service Name> [0339] 7. HSN.Domain.Subscriber.SSS.<Service Name> [0340] 8. HSN.Domain.Subscriber.Snet.<Snet Name>.<Subscriber Name> [0341] 9. EmailAddress@HumanServiceNet.Com

[0342] E.g.: HSN.LasVegasTravel.HSNHA.YogeshRathod.KIS.TravelGuide

[0343] The first example of HumanServiceNet Namespace shows HumanServiceNet Namespace parameters for (17M) start with Root the first which indicate the top most node i.e. (17A) HumanServiceNet itself. The second parameter in the HumanServiceNet Namespace is Domain, the third parameter is the CHN name, the forth parameter is the human agent name, fifth parameter is service type and the sixth parameter is service name.

[0344] FIGS. 18 and 21 showing graphical user interface (GUI) for Subscriber (HSNS) and human agent active Messenger (HSNM) having embedded Explorer (HSNE) illustrate various tools for match making, various (18L and 21L) parameters selection including taxonomy classification, domain, channel node, source name and service. The subject field is selected via 18B & 21B, the 18L & 21L selection fields are linked with the subject field (18B and 21B) and (18D and 21D) providing for further multiple channel nodes and UHSF identified cluster as well as service type including paid, free, offline smart client, mobile or wireless client, HSN via web services and HSNM with 3.sup.rd party applications and services for devising strategies for conditional match making by means of plurality of Booleans logical combinations to improve upon search specificity in particular domain thus saving on time and network resources employed therein. Search engine further facilitating search conduction at four different granular levels including HSN, Taxonomy classification based Service Cluster, Personal Networks and Local Networks, restricting search to specific domain wherein each of human agent sending selected resources from selected sources for selected queries of selected services to selected subscribers via selected utilities by selected client of HSNM. As HSN employs cluster approach for improving on service orientation ground, same tool of clusters is used to limit the search to specific cluster of operation. 18E and 21E represents a typical format of search results and are browsed via 18C & 21C changeable tab selection and 18F & 21F showing search status bar showing description of match making result and actual annotated results, with its namespace appended therein respectively. 18G & 21G showing a massager having a input area and massaging contents of each of participant in the communication process with the said subscriber or within the said group, the said match making engine employing plurality of match making techniques to retrieval relevance and precision optimization conducting basic match making, wizard based match making, advanced match making, and command based match making, wherein 18H & 21H providing for selection of various communication modality including text massaging, voice & video, file sharing, chatting, IP phone, fax, emailing, meeting and collaborating. 18J & 21J showing a subscriber's and human agent's workspace respectively, providing for management of different searching attempts which are carried on the project basis, providing details regarding current contacts which are currently active with in the said workspace, online contacts which are currently online in the UHSF system and offline contact which are not currently logged in to the UHSF system, wherein the users can manipulate each of the member in the workspace by creating, deleting, renaming, copying, restoring, and sending workspaces. Workspaces are categorized into 1. Active, 2. Unread and 3. Read wherein active workspaces are the one which members have open for reading or updating, Unread workspaces contains new or updated information, and Read workspaces that do not currently contains any new or updated information.

[0345] The said GUI is fully customizable as per requirements. Section 18I & 21I navigation tree structure is based on dynamic taxonomy classification (e.g. Field, Location and Domain etc.) of each of channel node and subscriber can select node & use 3.sup.rd click menu options to take necessary actions, Section 18D & 21D of the search engine GUI illustrate basic match making engines enabling selection of various searched parameters based on The HumanServiceNet match making engine is enabled for tracking operations for plurality of channel nodes based on predefined specified criterions, expressed in terms of plurality of keywords with combinational Booleans logic involved therein. Also the said search engine employs subject specific semantic ontology to improve upon precision and relevance of searched information into the HumanServiceNet framework. Further the matched or searched results are operated with plurality of functional tools including but not restricted to sorting, ranking, tracking, filtering, settings, printing, sending matched or searched results, downloading information, comparing, multiple view generating, auto matching, exporting and saving the said results.

[0346] 18D & 21B provides for text box to enter Keywords and Boolean Logic like (AND (+), OR (|), NOT (), Phrases, Multi Brackets for Multi Inner searches, ontology & taxonomy selection tools to select hierarchical categorization or classification of entities or services within a domain or field e.g. taxonomy classification of services like Fields, location, domain category, sub-category etc., multiple Channel nodes and check box selection to provides granularity in searching approach is enabled by penta tier searching facilitated by searching depth determination.

[0347] The matched results (18F & 21F) containing URI or HSN Namespace or URL, Source channel node name, weight, rank, grade or points, Paid or free or sponsored or relational (Personal network) service, status (subscribed or not subscribed) for particular service, short information of source.

[0348] Users are being enabled to bookmark, save results or sent queries to selected sources and can click hyperlink for more details, further performing 3.sup.rd click operations on hyperlinks for more actions like ask for more details, subscribe and make payments, sort results (node wise, ASC, DESC etc.), take printouts etc.

[0349] FIG. 19 illustrating a query manager a means for organizing the queries via various selection provisions, wherein necessarily each of intended query need to be selected from a specific taxonomy class from the selection in 19B, the query can be keyword based, natural language queries (19C), or command based and the said query can be selectively posted at the selected sources, for selected consideration via selected communication utility (19I). Additional tool facilitating the management of the said query considering it to be knowledge invocation activity for archiving the posted queries, providing query directory, query assistant for helping user to draft queries, scheduling, saving, and publishing the said queries. Queries posted therein are ready to use query or query syntax or query in the repository, or published query (taxonomy classification based) wherein each of query are validated for protocol based role activity.

[0350] FIGS. 20 and 23 illustrating a GUI of a journal module showing various entries of the actions and responses of each the HSNS and human agent respectively wherein the recording fields includes date, HSN URL, source (from box), service, communication details, status, massages, details, descriptions, attachments, lists, taxonomy classification, size, workspace, and tracking status for each of action and transaction of the said subscriber and human agent, the said journal is being made searchable (20A & 23A) and can be sorted in the desired sort preference.

[0351] FIG. 22 showing GUI for various utilities and provisions for organizer and answer manager for each of human agent, facilitating human agent to organize each of received queries from one or more subscriber wherein selecting subscribers (22C) via selection window and actively exploit multiple UHSF system resources (22G & 22H) for answering the said queries alongwith resources are provided to querying subscriber (22I). Further the communication utilities can be selected for forwarding answers to subscribers via 22K multiple communication utility selection windows. Wherein human agent optionally publishing the said answer globally UHSF wide, or in the related human circles based on the mutual data confidentiality agreement terms acceptance by mutual parties. Additional answer organizing tools are provided (22N) which are providing for scheduling, creating publication, drafting, saving and exploiting rules wizard.

[0352] FIGS. 24 and 25 illustrate example of graphical user interface (GUI) for Subscriber and human agent active composite search engine alongwith the multiple search results thereof and multiple searching tools therefor including tools for bookmarking, sorting, ranking, comparing, searching, filtering and printing of the search results. 24I & 25I showing the respective activity specific explorer, 24D & 25D various search parameters and 24E & 25E showing a typical representation of search results showing namespace of the result and actionable tools supplemented therewith so as to execute the said search results to its final accomplishment includes details, rank, subscribe, package details, review, download and status

[0353] FIG. 26 through 31 illustrating wizard interfaces for each of channel node with respect to specific accomplishment via other channel nodes. FIG. 26 to 31 illustrating example of graphical user interface (GUI) for Service Provider (HSNSP), HSNHA, HSNS, and HSND active wizards illustrating each of GUI for each of channel node and HSN controller alongwith the formatting parameters thereof, the formatting parameter selection is based on the predetermined selection logic for each of channel node wherein each of steps providing multiple options to choose from so as to accomplish the selected task.

[0354] The general tasks accomplishment by each of provider via wizard in FIG. 26 with respect to particular channel node to be accomplished are as follows:

for Developer (26A): a. download AI agents, utilities, & application, b. make payments, c. get product details, d. register;
for HSN controller (26B): a. check service details, b. make payments, c. get package keys, d. subscribe;
for Human agent (26C): a. browse HA, b. search, match and bookmark HA, check request, c. send matched contents, d. send package key;
for subscriber (26D): a. brows HSNS, b. search, match, bookmark HSNS, c. check request, d. send match contents, e. send package keys;
wherein each of tasks performed via wizards are alternatively accomplished by means of separate specific functional tool or combination of tools thereof in the same order or in the different.

[0355] The general tasks accomplishment by each of human agent via wizard in FIGS. 27 & 28 with respect to particular channel node to be accomplished are as follows:

for Developer (27A): a. download AI agents, utilities, & application, b. make payments, c. get product details, d. register;
for HSN controller (27B): a. check service details, b. make payments, c. get package key, d. subscribe;
for provider (27C): a. check service details, b. make payments, c. get package key, d. subscribe
for Human agent (27D): a. browse HA, b. search, match and bookmark HA, check request, c. send matched contents, d. send package key;
for subscriber (28A): a. brows HSNS, b. search, match, bookmark HSNS, c. check request, d. send match contents, e. send package keys;
for Brokers (28B): a. check service details, b. make payments, c. get package key, d. subscribe;
wherein each of tasks performed via wizards are alternatively accomplished by means of separate specific functional tool or combination of tools thereof in the same order or in the different.

[0356] The general tasks accomplishment by each of subscriber via wizard in FIGS. 29 & 30 with respect to particular channel node to be accomplished are as follows:

for Developer (29A): a. download AI agents, utilities, & application, b. make payments, c. get product details, and d. register.
for HSN controller (29B): a. check service details, b. make payments, c. get package key, d. subscribe;
for provider (29C): a. check service details, b. make payments, c. get package key, d. subscribe
for Human agent (27D): a. browse HA, b. search, match and bookmark HA, check request, c. send matched contents, d. send package key;
for subscriber (30A): a. brows HSNS, b. search, match, bookmark HSNS, c. check request, d. send match contents, e. send package keys;
for Brokers (30B): a. check service details, b. make payments, c. get package key, d. subscribe;
wherein each of tasks performed via wizards are alternatively accomplished by means of separate specific functional tool or combination of tools thereof in the same order or in the different.

[0357] The general tasks accomplishment by each of developer via wizard in FIG. 31 with respect to particular channel node to be accomplished are as follows:

for HSN controller (31A): a. check service details, b. make payments, c. get package key, d. subscribe;
for Developer (31B): a. upload AI agents, utilities, & application, resources, updates and upgrades b. collaboration, c. support, d. product key management, e. package key management
for Human agent (31C): a. browse HA, b. search, match and bookmark HA, check request, c. send matched contents, d. send package key;
for subscriber (31D): a. brows HSNS, b. search, match, bookmark HSNS, c. check request, d. send match contents, e. send package keys;
wherein each of tasks performed via wizards are alternatively accomplished by means of separate specific functional tool or combination of tools thereof in the same order or in the different.

[0358] FIG. 32 illustrate algorithmic sequences flowchart for registration of each of channel node with the HumanServiceNet Controller. The logical flow therein deriving dependencies from the previous status of both registered and unregistered users in the UHSF system.

[0359] FIG. 33 illustrate algorithmic sequences flowchart of the Developers' development proposition, registration and certification methodology.

[0360] FIG. 34 illustrate algorithmic sequences flowchart of the Service providers' service offering proposition, registration and certification methodology.

[0361] FIG. 35 illustrate algorithmic sequences flowchart of the Human Agent service proposition, registration and certification methodology

[0362] FIG. 36 illustrate algorithmic sequences flowchart of the Brokers' service proposition, registration and certification methodology.

[0363] FIG. 37 illustrate algorithmic sequences flowchart of Subscribers' Paid Certification and Registration methodology with HSN Controller

[0364] FIG. 38 illustrate algorithmic sequences flowchart of Registration of Human Agents', Service Providers' and Subscribers' with HSN Developer via HumanServiceNet.

[0365] FIG. 39 illustrate algorithmic sequences flowchart of Selective Multi Services Subscription request by plurality of channel nodes and its processing by HumanServiceNet Controller and package key issuance thereby.

[0366] FIG. 40 illustrate algorithmic sequences flowchart of Selective Multi Services Subscription request by plurality of channel nodes and its processing by Service Providers and package key issuance thereby.

[0367] FIG. 41 illustrate algorithmic sequences flowchart of Selective Multi Services Subscription request for AI Agents by plurality of channel nodes and its processing by Developers and package key issuance thereby.

[0368] FIG. 42 illustrate algorithmic sequences flowchart of Selective Multi Services Subscription request for knowledge invocation (KIS) and knowledge support services (KSS) by one or more subscribers & Human Agents and its processing by Human Agent and package key issuance thereby.

[0369] FIG. 43 illustrate algorithmic sequences flowchart of Selective Multi Services Subscription request for intermediary services by one or more subscribers & Human Agents and its processing by the Broker and package key issuance thereby.

[0370] FIG. 44 illustrate algorithmic sequences flowchart of service delivery model of the Service Providers displaying multiple communications with the multiple other Service Providers, subscribers & Human Agents.

[0371] FIG. 45 illustrate algorithmic sequences flowchart of service delivery model of the AI Agents displaying multiple communications with the multiple channel nodes.

[0372] FIG. 46 illustrates algorithmic sequences flowchart of service delivery model of the Human Agents displaying multiple communications with the multiple channel nodes and one or more Human Circles thereof.

[0373] FIG. 47 illustrate algorithmic sequences flowchart of service delivery model of the Brokers displaying multiple communications with the multiple Subscribers and Human Agents.

[0374] FIG. 48 illustrate algorithmic sequences flowchart of communication model of the Subscribers displaying multiple communications with the multiple channel nodes, including social personal group thereof and with the HSN controller.

[0375] FIG. 49 illustrate algorithmic sequences flowchart of each of CHN's Service Package Keys Management displaying multiple package key configuring parameters related to each of subscriber thereof.

[0376] FIG. 50 illustrate algorithmic sequences flowchart of each of CHN's product Keys Management displaying multiple product key configuring parameters related to each of subscriber thereof

[0377] FIG. 51 illustrates a flow diagram of HSN Default Multi AI Agents and AI Agent enabled Services (AIS) working modality including its development, registration and subscription flow and exploitation for automation wherein plurality of developers (51B) developing one or more AI agents and each of service offeror (51C) including at least one human agent and at least one providers downloading one or more AI agents from one or more developers (51B) wherein each of service offeror (51C) customizing and training the downloaded AI agents to offer AI enabled services (AIS) to one or more channel nodes (51G) in the UHSF system and registering the said AIS with HSN controller (51A) wherein HSN controller storing and maintaining repository of each of registered AIS and making them searchable to each of subscribers (51E) wherein the subscribers downloading requisite AIS from one or more searched human agents and providers offering AI enabled services and customizing and training said AIS personally or collaboratively with other subscribers (51F) as per preferences thereof.

[0378] FIG. 52 showing comprehensive view of operational graphical user interface (GUI) for Email Service (HSNEM), Massaging, Notification and Communication System illustrate HSN Email Service interface wherein 52D showing the emailing posting windows and writing area whereas 52H showing the received emails arranged datewise. Each of mail can either be posted to specific channel node or can be broadcast using filter operation. The explorer 52C in the lest hand side enabling email display to relevantly clicked channel node and 52E section forming a database part of the emailing system comprising of inbox, outbox, draft, sent item, recycles items, journal, search, organizer, query manager, replication manager, calendar, contact, notes and tasks. The functional aspect of emailing covering inmail and outmail alerts and asks for permissions as per settings via (52F) a auto content alters setting by the users thereof wherein selecting taxonomy, sources, source name and services for receiving auto alerts. The HSNE provides for all Human Services via Email and communicate with known as well as unknown users and subscribe for auto contents from selected multi sources. Send or advertise Email content to any matched subscribers (two way match making) based on the associated metadata and send Emails to Multi known as well as unknown matched sources via multi Search Sources & Contents options.

[0379] FIG. 53 showing comprehensive view of the graphical user interface (GUI) for HumanServiceNet Online Portal (HSNOP) illustrate the possible knowledge fields and tools therefor, 53D representing a typical directory structure of plurality of subject containing subject index followed by UHSF activity specific accomplishment of each of task including products and services subscription therefrom. An online portal providing for web based support, subscription system for online shopping, webservices, emailing and massaging, questions and answer publication, and primarily an interface for membership and channel node membership registration. Providing for a UHSF system wide 53E data analysis, facilitating users for better understanding the system function providing for rankwise human agents, human circle directory, Publish Directory & CD, Human Agents Job Posts, Human Agents Franchise, Purchase Contents, RES Services & Apps Directory, Survey Searches & Directory, HSN Human Services via Web Services Directory, HSN Free Web Space (Human Sites), HSN Publications (News Papers & Magazines), HSN Domain specific knowledge Dictionary CD, Knowledge Support Services (KSS) Directory, Subscriber Support Services (SSS) Directory, and Super Nodes & Taxonomy Directory. 53F provides for plurality of service directories and download facility of plurality of channel nodes including that of HSN controller. 53B and 53C providing interface for searching and navigating UHSF resources. Each of users having access to the said online portal is enabled to login via product key thereof.

[0380] FIG. 54 illustrates Holistic View of Universal Human Service framework's (UHSF) Operating System (HOS) displaying the layered segregated circular operating tiers necessary for service integration wherein users (54F) forming the external most layer of the UHSF operating system. This layer (54F) typical meant for human networking and social networking development on the UHSF interactive and communication platform as represented by communication layer (54E) the said layer comprising of plurality of communication modality integrated in one platform and provided by means of product key on demand, wherein each of user in layer 54F installing the said communication utility including HSNE, HSNM, HSNEM, and HSNOP providing for different modality including voice, text and video communication. The UHSF operating system further providing for core system level functionality (54D) search and matching of system resources including channel nodes for requisite keywords or full text queries. The operating system further providing for integration of human (54C) services at the internal core of the operating system model, wherein each of human in the UHSF system are perceived in the predefined and system identified attributes and parameters, facilitating KSS, RES, AIS, SSS, SSP and knowledge invocation services (KIS), the system level enability of plurality of functions provided by UHSF system are operated by means of various application and software utilities developed by plurality of developers (54B) so as to facilitate user perform advance functions on the UHSF platform, the HSN controller forming the core kernel (54A) of the said model of UHSF operating system is a means for system wide events, registration and certain essential functions which are not performed in peer to peer environment are centrally managed by the said controller.

[0381] FIG. 55 showing graphical user interface (GUI) for HumanServiceNet Replication & Synchronization Manager (Publisher) providing knowledge replication services. User can replicate publications of Service Sources, Applications and Contents via push subscriptions to selected subscribers as well as subscribe for replication publications via pull subscriptions. In the UHSF system data can be published either globally i.e. complete UHSF systemwide or in the specified identified social group or to the identified privileged channel nodes for conditional access therefor. Replication is a set of technologies for copying and distributing Sources (Services), Applications and Contents (Data & Files) from one Source to another and then Synchronizing between Sources for consistency. Using replication, users are enabled to distribute data to different locations, to remote or mobile users over a local area network, using a dial-up connection, and over the Internet. Replication also allows users to enhance application performance, physically separate data based on how it is used or distribute database processing across multiple servers. The content of each of channel node needs replication and synchronization at the appropriate part of the system for updated picture of the system providing availability of data when and where it is needed. The replication and synchronization manager helps accomplish the said task via various tools wherein the interface thereof having regular system explorer (55C) to the left and specifically replication explorer (55D) to the right showing the publication details of the said publisher. Replication facilitating multiple users to keep copies of the same data which is useful when multiple users need to read the same data and facilitates greater autonomy in the system for distributing copies of data and changes on a scheduled basis wherein multiple users making changes then merging the data modifications together by means of creating publication. Publications are basically made for sources (55F), applications (55G), and contents (55H), wherein the publisher selecting each of services, data-files, and applications via filtering from the sources thereof. 55I selection providing for determination of replication type as a transactional, merge or snapshot and providing for privilege of anonymous pull subscription and selection and filter for subscribers for generating push subscription. The replication further can be preprogrammed via replication rules wizard and can be monitored.

[0382] FIG. 56 shows a logical block diagram of HumanServiceNet (HSN) Replication Topology Models illustrate the replication topology of each of CHN as per protocols and relationship established via FIGS. 7 and 16 wherein HSN controller (56A) replicating topologically to at least one human agent, service provider and subscriber, each of human agent providing replicating topologically to SN controller and to at least one human agent, human circle, human federated services and subscriber, each of subscriber replicating to HSN controller and at least one subscriber, each of service provider replicating to HSN controller, and at least one service provider, subscriber, human agent, human circle, and human federated services and each of developer replicating to at least one service provider, subscriber, human agent. The said replication and synchronization of various publications is regulated via protocol based correspondence logic.

[0383] FIG. 57 showing graphical user interface (GUI) for binding human services from the UHSF system via web services with the 3.sup.rd party software and web sites like e-commerce, search engine and other web sites illustrate the required tools therefor including searching (57B) and navigation (57C) tools wherein each of UHSF system user searching for human agents services deemed to be used via web services and establishing connection therewith via webservices invocation logic.

[0384] FIG. 58 shows discrete services which Human Grid can integrate for true universal operation. Fields, domain and subject are being identified parameter whereby each of interested human are grouped together forming a segregated subjectwise human aggregation for social networking and knowledge sharing, the similar aspects are exemplified but not restricting the scope of operation of the said system which includes universal human operating system (58A), universal human service framework (58B), Universal Human Relationship Management (58C), Universal Innovation Networking (58D), Universal Clustered Virtual Brain (58E), Universal Social Networking (58F), Universal Knowledge Management (58G), Universal Digital Divide Solver (58H), Universal Human Search Engine (58I), Universal Human Match Maker (58J), Universal Human ID (58K), Universal Human Knowledge Transfer (58L), Universal Human Resources Repository (58M), Universal Human Linking & Network (58N), Universal Human Taxonomy Classification (58O), Universal Human Resource Planning (58P), Universal Human to Human Communication (58Q), Universal Human Collaboration (58R), Universal Human Grid Utilization (58S), Universal Human society (58T), Universal Human and Machine Collaboration via Human (Services) Grid and Information & Computing Grid (58U).

[0385] FIG. 59 shows a logical segregation of Human Grid in term of multiple Sub-Grids and integration thereof as exemplified in FIG. 58. 59A realizing a human grid and possible subcomponents into data & information grid (59B), physical grid (59E), knowledge grid (59C), computing grid (59D), resources grid (59H) and various sub grids as per attributes, taxonomy, ontology and classification (59G). In the UHSF system grid formation being considered at universal level, enterprisewide grid creation can not be ruled out as corporate are growing in sizes hence it is difficult to manage such distributed physical and computing resources without grid formation. Though communication and transactional aspects remains the same in any grid configuration what differs is subject headings, their behaviors, and their desired implementation, which can be worked out for any given situation.

[0386] FIG. 60 showing graphical user interface (GUI) for Human Services Aggregation, Integration, Collaboration, Composition, Comparison, Co-ordination, Workflow, Orchestration and Choreography Manager for Subscribers (HSNS) wherein each of subscriber exploiting the UHSF system resources and enabling the communication, interaction and data transfer based on the predetermined protocol and widely automating various functions and managing them in the workspaces (60E). Services and resources utilization requires a platform having tools for aggregation integration, collaboration, composition, comparison, coordination, workflow management, orchestration and choreographing of the said services. Each of subscriber organizing services subscription and planning via tools provided for searching, inquiring and subscribing the said services. 60D providing for a ready reference showing status availability of various sources. 60G a messenger for submitting selected queries of selected classification of selected services for multiple resources via selected utilities by selected clients of HSNM. 60A & 60B providing for various tools for accomplishment of above stated objects wherein the said objects includes management tools for various operations related to workspace, taxonomy, services, utilities, tools, actions, message, transaction and project management. 60F providing for content organization wherein all communication and events related data is stored. Choreographing via use of various tools facilitating weaving of different Human Services into meaningful business process, Sequence, and transaction. Sequence whereby aggregating service groups and service collections, integrating 3.sup.rd party web services, establishing collaborative communication flow between human agents, human services and other all services, composing life cycle management (e.g. creation, termination etc.), comparing Human Services as per quality (hits & ranks), relevance and package price (as per TCO), coordinating Workflow the management of steps in a business processes wherein a workflow specifies what tasks need to be done, in what order (sometimes linearly, sometimes in parallel), and who has permission to perform each task. Most task performers are humans but they can also be automated processes, orchestrating the control and data flow between Human Services into business process.

[0387] (60B and 60C) Workflow Explorer contains 1 or more user created Topic and all Sub-Topics related to particular subject or task or query or issue or problem or business requirements etc. e.g. Topic is [How to Setup Firm at New York City?] and its Sub Topics are (1) Real Estate (2) Legal Requirements (3) Recruitment (4) Marketing (5) Finance etc. which is classified and arranged via (Step-1) Taxonomy & Ontology Management which provides all functionalities like create new, open existing, use from archive or tag, replication from multi sources and import taxonomy project. Projects can be edited and deleted. Taxonomy can be ordered and ranked as per requirements and metadata can associate with each part of taxonomy. Each Sub-Topic has (Step-2) Workspace Management, in which 1 or more workspace can be managed. User can create new, open existing, attach, detach, use from Archive or tag, import, replication and invite for workspaces. E.g. Sub-Topic Real Estate has two workspaces like Estate_NY and Estate_NJ. Each Workspace can contain 1 or more utilities and applications for communication, collaboration and content management via (Step-3) Utilities Management which contains attach, detach, download and replication of Utilities. e.g. HSN IM, HSN Email, Collaboration, Discussion, File Sharing, Chat, IP Phone, Fax, E-Mail. Each Sub-Topic has (Step-4) Service Management, in which 1 or more services of HSN, HSNHA, HSNSP, HSNAIA, and HSNB are attached, detached, searches via multi options like Auto Match, Custom Match, Search & Bookmark, Browse HSN Directory, Publish (Global), Publish (Filtered), Auto Content (Alert), HSN Address Directory, HSN Explorer (HSNE) and Human Match Maker, Ranking & Ordering, Replication, Aggregation, Integration, Collaboration, Composition, Comparison, Co-ordination, Workflow, Orchestration and Choreography. (Step-5) is Message management with the help of Journal, Organizer, and Multi search & math options, Inbox, Outbox, Sent Items, Draft, Recycle and other options required for message and content management. (Step-6) is Action Management which provides varies utilities and tools for successful workflow.

[0388] Like Calendar, Tasks, Journals, Services and Utilities & Applications. (Step-7) is Transaction Management which has 1 or more Services e.g. Payment for successful transaction.

[0389] (60D) illustrates Service Sources status like Current indicates currently sources are communicating, Online status indicates service sources are online and available for communication and offline status indicates currently service sources are offline and available at later.

[0390] (60E) illustrates workspace status Current (Legal, Setup Firm, Estate_NY, Estate_NJ) indicates currently use workspaces, Read (Legal, Estate_NY, Setup Firm) indicates workspace contents already read and Unread (Recruitment, Marketing, Estate_NJ) indicates workspaces content not read.

[0391] FIG. 61 showing graphical user interface (GUI) for Human Services Federation, Aggregation, Integration, Collaboration, Composition, Co-ordination, Workflow, Orchestration and Choreography Manager for Human Agents (HSNHA) wherein each of HA providing one or more federated services including devising services categories as per taxonomy and related to particular subject or task or problem or issue or topic and arrange and transmit for solution or answer thereof to one or more subscribers thereof composing one or more needs, behavior, likings, requirements, and queries of one or more subscribers and one or more service group explorers wherein the choreography of said composition is executed via workspace explorer thereof so as to orchestrate the federated services of plurality of HSNHA. The service federation by each of HA is enabled via various management tools (61A & 61B) including taxonomy, services, package key, subscribers, workspaces, group, and tools management, wherein each of human agent providing various federated services and communicating, interacting and transferring data based on the predetermined protocol. Each of service offering and federation thereof is widely automated and managing them in the workspaces (60E) wherein tools therefor organizing services federation and planning including searching, inquiring and subscribing the said services.

[0392] (61B and 61C) Service Groups or Federation Explorer contains 1 or more user created Service Groups and Sub-Groups related to particular subject or task or query or issue or problem or business requirements etc. e.g. Service Group is [US Travel] and all related services are (1) Travel Enquiry (2) Visa Procedure (3) Travel Experience (4) Book Air/Car/Cruise (5) Hotel Booking etc. which is classified and arranged via (Step-1) Taxonomy & Ontology Management which provides all functionalities like create new, open existing, use from archive or tag, replication from multi sources and import taxonomy project. Projects can be edited and deleted. Taxonomy can be ordered and ranked as per requirements and metadata can associate with each part of taxonomy. Each Sub-Topic has (Step-2) Service Management, in which 1 or more services of HSN, HSNHA, HSNHC, HSNSP, HSNB, HSNAIA are attached, detached, searches via multi options like Auto Match, Custom Match, Search & Bookmark, Browse HSN Directory, Publish (Global), Publish (Filtered), Auto Content (Alert), HSN Address Directory, HSN Explorer (HSNE), Human Match Maker and Federated Services Directory, Ranking & Ordering, Replication, Federation, Aggregation, Integration, Collaboration, Composition, Comparison, Co-ordination, Workflow, Orchestration and Choreography. (Step-3) is Package Keys Management in which system user (HSNHA) can create and customize package keys and search and collaborate with other service providers for combo or bundled services package keys related to particular service groups or subscribers requirements. (Step-4) is Subscribers Management in which system user (HSNHA) can check subscribers service request, provides guidance & solution and issue package keys as per requirements. E.g. Subscribers Management in service group explorer tree shows Subscriber Amitabh and his all subscribed services and service package keys management, Collaborative or others Services Links and service package keys management and lists requested Services, Alternate services and suggested services.

[0393] (61D) illustrates Service Sources status like Current indicates currently sources are communicating, Online status indicates service sources are online and available for communication and offline status indicates currently service sources are offline and available at later.

[0394] (61E) illustrates workspace status Current (Travel, Book Hotel, Cruise, US Visa) indicates currently use workspaces, Read (Travel, Book Hotel) indicates workspace contents already read and Unread (US Visa, Cruise) indicates workspaces content not read.

[0395] FIG. 62 illustrates HSN Query Manager which is an interactive graphical tool for knowledge invocation and management thereof alongwith the pane showing answers to the posted query that allows user to create one or more queries and other scripts and execute them against HSN Service Providers (Service or Content Providers Peer to Peer or centralize HSN search engine) and is providing for all search, match and post search management tools.

[0396] In HSN Query Manager, users enter simple keyword, natural language or HSN-SQL statements in a query window (62E), execute the statements, and view the results (62F) in a results window. HSN Query Manager also providing tools for determining how HSNM is interpreting and working with a HSN-SQL statement wherein a user can display a graphical representation of the execution plan generated for the statement, display statistics about the performance of the statement. Searches options provided therewith includes advance search, search wizard, search editor, templates, auto match, custom match, HSN Directory, Auto Content, Source Address navigator and explorer. The connect service tab in the tool bar (62B) providing for knowledge service connection for the intended to subscriber service by means of service connection wizard or disconnecting any or all of the already subscribed services. The transaction management tab in the tool bar (62B) providing for the means to negotiation and payment management for each of services subscribed by the said CHN. The search and match options provided therein the toolbar providing for selection of service types to be queried for posting the query with out of various channel nodes, human services, including RES, AIA-AIS, HSNHC, HSNFS, KSS.

[0397] The query window (62E) is composed of multiple panes. The Editor pane is a text editor where you can enter HSN Query, SQL Query, English (Natural) Query, Full-Text Search statements. The Results pane (62F) displays result sets. The Messages pane displays error messages. The Execution Plan pane displays a graphical representation of an execution plan. The Trace pane displays server trace information. The Statistics pane displays statistics information.

[0398] Taxonomy Repository menu provides options to Associate one or more taxonomy to one or more Services to put service in one or more categories for easy search and retrieval via Filter & Download (HSN) option system user can download filtered centralize taxonomy repository for search requirements. Action Management menu provides post search management operations including download searched AI Agents, application and utilities via Download Links, Check Details of Services and Products via Details Links, Request Product Keys for selected Products, Subscribe Services online, Request Package Keys for Selected Services and Request More Details for selected products and services and Transaction Management menu facilitates to all transaction via services like Make Payment for selected products and services etc.

[0399] Other search options are statistics details, status, reviews, Bookmark, Sort, Rank, Compare, Filter, Print search results and Search within Search. Apply various Search Settings to customize Query Manager and Search Results etc.

[0400] FIG. 63 showing graphical user interface (GUI) for Hit Statistics Manager for HSN Controller illustrate the hit statistics of each of contents, utilities, search macros, published data in public and private domain of each of the channel node in the UHSF system.

[0401] FIG. 64 showing graphical user interface (GUI) for Hit Statistics Manager for HumanServiceNet Developer (HSND), HumanServiceNet Human Agent (HSNHA), HumanServiceNet AI Agent (HSNAIA), HumanServiceNet Service Provider (HSNSP) and HumanServiceNet Broker (HSNB) and Hit Managements' menu options.

[0402] FIG. 65 showing a graphical user interface (GUI) for Multi Rank System for HSN controller, Human Agent (HSNHA) and Subscriber (HSNS) wherein HSN provides two types of Rank Services namely

[0403] HSN Auto Rank Service which is based on Hit Statistics in combination with scores generated by points assigned by content users (HSNS and HSNHA) and

[0404] HSN Paid Rank Service which is based on Hit Statistics in combination with scores generated by points assigned by content users (HSNS, HSNHA & HSNB)] and one or more parameters out of quality, transaction, goodwill, brand and certification status. HSNHA and HSNS Rank Services (65B & 65C) providing for assignment of scoring points in the range of 1 to 100 to the services offered by various CHN & CHN Service related answered contents and comments on answered contents and also to the various search macros facilitating ranked knowledge package invocation wherein the rationale followed is based on hit statistics, grade or weight or rank assigned by HSN (65A) each of rank assignment is possible via 3.sup.rd clicking the channel nodes and services thereof in the explorer, wherein selecting and providing numeric input to the ranking module. The said ranking module works on the cumulative aggregation basis, wherein rank is instantly revised on the basis of said input via mathematical algorithm, the said algorithm output being linked with the replication and synchronization module, providing for updated rank at display in the UHSF system.

[0405] FIG. 66 showing a logical block diagram illustrating the scheme for searching & matching of subscribers for contents & sources, mode of communication therewith and associated advertising of contents by each of CHN. Showing 66E to 66J representational plurality of distributed HSN controller registered channel nodes communicating in the peer to peer environment, sending search queries to HSN supernode (SN) directory based routing server (66C) which is having SN lookup directories and plurality of subscribers partial profiles stored therein, the said SN directory based routing server (66C) emulating and routing the said query at the matched SN (66D) via routing agents which is based on the domain specific taxonomically precategorised supernodes matching logic, wherein each of matched SN (66D) sending plurality of spiders for fetching matched contents with respect to the said query or one or more searching CHNs (66E to 66J) requesting after filtering (66O) the said HSNS for the sources or sending advertisements via communication modules (66K to 66M). The said spider passing on the said keyword to the input module of the black box searching (BBS) wherein each of each of BBS providing the search results at the desktop of each of user and providing for OUT permission alert to each of desktop user, acceptance of said OUT permission provides for search contents to be routed via said spider to the querying CHN. Block 66A and 66B showing the subscriber's relationship with the each of service providing channel node and HSN controller wherein each of subscribers querying to 66A and in receiving answers therefrom. In the process of searching each of searchers are provided with penta tier searching capability via 66Q search depth selection option specifying the tier of searching as per desired granularity and being provided at options to select the human involvement in the searching operation. HSN controller being a means for repositing taxonomically and ontologically classified list of various UHSF wide CHNs, providing for lookup directories of precategorised and preidentified CHNs and resources thereof and establishing direct connection therewith,

[0406] The penta tier searching model works at desired level throughout the UHSF system wherein the said search query terms are matched with taxonomically categorized supernodes (66D) via HSN controller (66C) central search and match engine and routing and replicating relevant matched SNs result to each of querying channel node towards 1.sup.st tier refinement depth selection; one or more routing agent routing query term to 1.sup.st online available matched supernode (66D) wherein said SN matching query term with plurality of HSNS extended shared profiles, indexed keywords, black box indexes, LKID resources in peer to peer environment by multiple taxonomy matching logic based on the profiles of plurality of HSNS being updated and clusterwise posted in the taxonomically classified profile database of one or more supernodes (66D) and routing & replicating relevant matched HSNSs (66B) results to each of querying channel node (66E to 66J) towards 2.sup.nd tier refinement depth selection; one or more matched and filtered HSNS (66B) receiving request for content source pointers or advertisement either from querying CHN (66E to 66J) or to each of matched HSNS directly from matched SN and each of requested HSNS routing & replicating relevant matched source pointers result to each of querying channel node or advertisement subscription request to respective advertisers thereof towards 3.sup.rd tier refinement depth selection wherein each of HSNS (66B) preselectively enabling or disabling respective BBS and LKID search thereof; one or more HSNS of 2.sup.nd tier refinement depth result after routing source pointers, receiving abstract request from querying CHN (66E to 66J) and in response to that routing & replicating automatically or manually one or more abstract of one or more source pointers to each of querying CHN (66E to 66J) towards 4.sup.th tier refinement depth selection; each of querying CHN (66E to 66J) filtering abstracts for determining and sending final selection request to one or more HSNS of 2.sup.nd tier refinement depth result and one or more HSNS responding and sending full contents via associated one or more publications or resources towards 5.sup.th tier refinement depth selection;

[0407] Each of query is selectively dealt by respective querying CHN (66E to 66J) by communicating either through HSNEM (66K) or through HSNE (66L) for various subscription and purchase in the UHSF system, and generating one or more publication (66N) filtering (66O) one or more matched subscriber for enabling effective searching experience.

[0408] FIG. 67 showing a logical block diagram illustrating logical connection of each of supernode represented via supernode-1(67C) and supernode-2 (67D) with the CHN (67A), HSNS represented by HSNS-1(67E) and HSNS-2 (67F) and the HSN controller (67B), composition of a supernode and taxonomically organized connectivity of each of SN component for search and match of HSNS. The basic premise behind working of the supernode mediated searching system is real time data replication within UHSF system wherein as shown in the FIGS. 67C and 67D supernodes are having respective relevant HSNS database (67G) and associated historical relevant HSNS database (67H) wherein real time relevance is generated via replicating the metadata for each of IN and OUT permission of HSNS with the associated relevant HSNS DB (67G) of respective supernode. HSN server (67B) directing the query of each of CHN (67A) to the associated supernode (67C) or each of CHN (67A) via associated taxonomy cluster. CHNs directly searching through the BBS of identified HSNS-1 (67E), at HSNS-1 (67E) desertion accepting IN or OUT permission or routing the query of advertise to the other identified HSNS-2 (67F) wherein each of IN and OUT permission acceptance are captured by respective supernodes and are replicated in the SN relevant DB (67G). Each of SN facilitating HSNS match making via SN relevant DB & HSNS extended resources DB wherein each of SN linking and routing the keywords with the other matched SNs for carrying forward the irrelevant queries and keywords tries at it. The HSNS related data in the SN relevant DB is the most recent one in the UHSF system, and matching of the queries and keywords executed via the schematic logic explained in FIG. 66 with the said DB provides for highly relevant search results and matches. This aspect is uniquely significant as catching of realtime information of users in any networked system is a tedious job is currently challenges for working of all intelligent systems, the integrated organization of data storage, routing and replication mechanism accomplishing the said challenge in the UHSF system. Additionally provides for excellent platform for ecommerce operations enability and SN mediated human and auto searching & matching method. Each of vendor scanning supernodes for fostering ecommerce operations thereof. The data contents in the databases of HSN server, SN, and SN relevant database are exemplified in the table format, the data category being representation only can add or delete any of the category as per logic modulation.

[0409] FIG. 68 showing a logical organization and integrated functioning of multiple spider agent (68F) of each of supernode and integrational, replicative connectivity of each of agents thereof alongwith relation data handling thereby each of agents wherein the said spider agent (68F) is a preprogrammed software module meant for plurality of independent functions of supernodes tasks via independent coordinated AI agents thereof including: [0410] 1. Taxo Sync Agent (68B) [0411] 2. SN candidate collection agent (68D) [0412] 3. Watch Agent (68E) [0413] 4. Action Agent (68F)

[0414] Each of said AI agents working independently facilitating combinational accomplishing building SN directories and plurality of actions, wherein SN candidate collection agent (68D) searching potential supernodes within the UHSF system based on predefined threshold parameters and entering the qualified SN into prospective SN directory at HSN controller's server, each of such selected SN is being plugged with one or more taxonomically segregated directory via one or more taxonomy sync agents (68B) and watch (68E) and action agents (68F) coordinating for alteration and restructuring of the said SN directory, wherein Taxo Sync Agents (68B) synchronizing the associated HSN taxonomy changes with the appropriate SN taxonomy directory and reporting the same to an action agent for further action. SN candidate collector agent (68D) crawling continuously through HSNS registration directory (68C) collecting plurality of related parameters thereof including public IP address, CPU details, memory capacity, network bandwidth level so as to prepare prospective SNs ranked database based on online availability thereof and concurrently SN watch Agents (68E) quantifying and keeping watch of existing SNs quality wherein checking online availability thereof by pinging thereto and adjunctively reporting alterations in each of the parameter collected by SN candidate collector agent and generating and appending a quality report therein the database thereof. The report from plurality if agents are executed via action agents (68F) performing plurality of actions based on the predefined threshold parameter conditions wherein primarily assigning one or more new or modified taxonomy to each of preemptively future operational SN based on rank thereof, performing plurality of load balancing actions wherein replacing, dividing and merging one or more existing SNs based on the quality report appended therein the database thereof by watch agent, performing load balancing of one or more overloaded or underloaded SNs wherein based on the predefining overload and underload threshold levels logically shifting the load to one or more other SNs for load value above prefixed overload threshold value and merging one or more SNs for load value below prefixed underload thresholds value, determining obsolesce of supernode on the basis of threshold predefined no of recursive pinging attempts wherein after crossing said threshold no of such pinging attempts the said supernode is made obsolete and replaced by either randomly selected new supernode in the said peer to peer environment or with the highest ranked SN from prospective SN database thereof.

[0415] FIG. 69 showing an interface for management of knowledge support services (KSS) illustrates the KSS project explorer (69C), workspace explorer (69E), KSS status explorer (69D) and plurality of management tools (69A). the knowledge support services specifically includes routing, scanning, analyzing, filtering, searching, matching, categorizing, book marking, search macros configuration, post action and transactions of ecommerce, sales, marketing, purchasing, ordering, billing, payments and contextual metadata, keywords, taxonomy, classification, ontology and semantic syntax building. Each of HSNHA providing for KSS services via package keys thereof. Creating, opening or importing multiple separate KSS projects in the said workspace (69E), organizing the said KSS service delivery via taxonomy management and managing KSS services via multiple preidentified separate KSS management utility for each of KSS function and further managing the said project in the said workspace for collaboration with other KSS providers.

[0416] FIG. 70 showing a logical block diagram illustrating HSNS universal profile creation and updation at a supernode via survey system wherein each of HSNS (70B) intermittently being fed with HSN controller's surveying system (70A) at predefined or circumstantial times wherein HSN controller preparing and sending Survey forms to each of HSNS and each HSNS submitting the said survey towards consideration of free utilities, social networking creation, receiving relevant advertisement contents, and matched service list. Figure showing the relational benefits received by each of HSNS (70B) from plurality of CHNs from 70D to 70I, the submission of the said surveys at the HSN controller resulting in the extended profile updation followed by linked replication at the related domain specific supernodes (70C), wherein each of supernodes updating the HSN controller about survey analysis and survey results for survey forms creation as per taxonomy cluster. The updated profile of each of HSNS at respective SNs results in the higher relevance searching and matching.

[0417] FIG. 71 showing an interface for management of subscriber support services (SSS) illustrate the SSS project explorer (71C), workspace explorer (71E), SSS status explorer (71D) and plurality of management tools (71A & 71B), the subscriber support services (SSS) specifically includes routing, scanning, analyzing, filtering, searching, matching, categorizing, comparing, mapping, formatting, and other supportive work like communication, printing, marketing, etc. via sponsored, paid, HSN currency, or barter exchange. Each of HSNS creating, opening or importing multiple separate SSS projects in the said workspace (71E), organizing the said SSS service delivery via taxonomy management and managing SSS services via multiple preidentified separate SSS management utility for each of SSS function and further managing the said project in the said workspace for collaboration with other SSS providers.

[0418] FIG. 72 shows a logical block diagram illustrating developers dissemination pattern of Rule Enabled applications [REA], rule enabled services [RES] and rule wizards (RW) including functioning of various components, and data flow towards implementation of the Rules-Based System. (72B) developer developing and customizing RES specific applications, utilities, AI Agents, and tools either independently or collaboratively and human agents (HSNHA) and service providers (HSNSP) (72C) downloading the said RES specific developed application & utilities for deploying the said applications & utilities for rules development for RES, testing, updating, and executing independently or via in collaboration with other (72D) service providers and human agents respectively wherein sharing said rules templates. The final rules policy implemented RES application & utilities are registered with the HSN controller (72A) and each of subscriber (72E) searching for the said registered RES at the HSN server, subscribing the said searched RES from one or more HSNHA & HSNSP via single or collaborative or federated package keys and sharing the said rule and templates with other peer subscribers (72F).

[0419] FIG. 73 showing a logical block diagram of Black-Box Searching (BBS) system illustrating internal components of BBS system and its functioning in the keyword handling from the various CHNs. Each of user's resources in the UHSF system are indexed and made searchable via black box search (BBS) logic as shown in the 73F. The black box search or desktop search utility is installed at the user machine (73F) having inport (73I) in the form of incoming keyword management for receiving multiple keywords, search syntax from plurality of BBS searcher or CHNs and outport (73J) for permissions and selection management for providing the search results thereto. A black box searching system comprising of resource index management (73G) unit for indexing files, images, docs, video, databases, favorites, registry, cookie, folders, emails, attachments, programs, contacts, machine configuration & all other info. which are further auto indexed, filtered, and categorized from local machine or network or server via multiple algorithms or methods or systems and publishing IN and OUT full or partial index to the multiple matched SN (73B), the incoming keyword is searched and matched by means black box search and match engine (73H) with the indexed resources provided by resource index management unit (73G) and based on the search and match results transmitting multiple permissions generation signals to the permission and selection management unit (73J). If the query containing linking and routing request alongwith depth thereof for extended matching the host user forwarding the said incoming query via linking and routing management unit (73D) to the multiple users BBS (73E). Multiple CHNs (73C) and P2P supernodes (73B) are shown in searching facilitation engagement wherein CHN sending search query at matched SNs and each of SNs sending the matched HSNS and resources thereof wherein the said matched SNs are obtained by sending SN matching query at the HSN controller. 73K top 73N showing the permission and selection and communication enabling interfaces.

[0420] FIG. 74 showing a logical block diagram of Universal Distributed (P2P) Knowledge and Information Database (UKID) system illustrating a method for creation, searching, organization and management of plurality of UKID and LKID structures and replication thereof wherein HSN central server (74A) as per taxonomy creating and updating multiple universal knowledge and information database (UKID) structures and maintaining and synchronizing the said structures throughout the UHSF system and one or more HSNS (74G) searching, downloading and utilizing one or more existing UKID structures or part thereof from plurality of taxonomically derived database structures stored in one or more database servers from the HSN server and downloading UKID related applications, utilities, AI agents and tools from one or more developers (74F) whereby organizing and modifying respective local knowledge and information database (LKID) structures of each of HSNS facilitating management and organization of respective information and knowledge contents wherein one or more HSNS modifying or creating new taxonomy and sending the same to the HSN controller (74A) and HSN controller selectively updating the said taxonomy by creating and storing new database structure therein the UKID thereof whereby combinly aggregating each of LKID structures of plurality of HSNS into the Universal knowledge and information database (UKID) in a p2p distributed communication environment. 74G showing the LKID structure management for data organization of each of HSNS. The searching system and logic as explained in FIGS. 66 and 73 working in the similar fashion, all resource indexing and local HSNS data organization is managed via LKID structures.

[0421] The HSN controller having one or more database servers storing taxonomy or field or domains into the primary UKID database structure therein and one or more management and organization tools therefor wherein said UKID database structure comprising of plurality of tables which are being attached therewith associated metadata thereof wherein the said UKID structure of HSN controller forming a primary database structure's source mechanism enabling information and knowledge management process within UHSF system.

[0422] Each of channel node being provided with plurality of LKID (74G) organization and management utilities performing database creation, organization and modification includes: [0423] 1. LKID wizard (74H) [0424] 2. LKID structure management (74I) [0425] 3. Data input management (74J) [0426] 4. Resource index management (74K) [0427] 5. LKID search and match engine (74L) [0428] 6. Incoming keyword management (74M) [0429] 7. Permissions and selection management (74N) [0430] 8. Linking and routing management (74D)
wherein each of channel node creating one or more databases structures manually or through a LKID creation wizard (74H) and managing data and structure thereof by means of management tools thereof.

[0431] One or more channel nodes (74G) providing one or more KSS and SSS services in one or more taxonomically classified subject areas and further creating, updating and modifying one or more LKID structures of one or more channel nodes wherein other CHN (74C) sending search syntax or query at the incoming keyword management unit (74M) of the searching CHN (74C) which forwarding the said query to the searching and matching engine (74L) which is forwarding the search results to the permission and selection management unit (74N) which is generating multiple permissions, selections, views and popup for sending matched database structures and resources thereof to the querying CHN wherein the permission and selection management is a means for selecting permissions and options provided therewith for incoming and outgoing data resources wherein providing plurality of views and interfaces for outgoing database results and incoming advertisements into the database thereof via multiple selection viewers further managing the same by generating plurality of log reports, blocking one or more users, monitoring, sharing, notifying, synchronizing & replicating one or more updates and predefining rules and settings for secured operations thereof.

[0432] FIG. 75 showing a logical block diagram of HSN AdRouting System illustrating system components for advertisement storage, customer tracking and a method for advertisement relevancy optimization comprising of various components for storage (75H), retrieval (75N), routing (75J), linking (75L), and dissemination of plurality of advertisements (75A & 75N) and accomplishing associated pecuniary transaction effected thereby, wherein various advertisers posting one or more advertisements (75G) in the advertisings and tacking DB (75H) alongwith daily budget and possible keywords therefor. The match making and business logic unit (75J) providing for the relevant matches of the advertisement with the prospectively interested CHNs by matching the entries of the prospective customer DB and that of HSN prospective customer preferences. The routing of the advertisements to the relevant subscribers is a dependant function on the prospective customer DB (75D), which is an integral part of UHSF SN mediated search system as described in FIGS. 66 & 67. In the searching operations each of searching CHN (75A) receiving the matched results for the searched keywords wherein each of matched HSNS (75B) selecting IN and OUT permission selection options wherein the IN permission selection enablement triggering the auto posting the details of each of HSNS including metadata, URL, registration no, keyword responded, date, and location into the prospective customer database (75D) via HSN AI agent and OUT permission selection enablement triggering posting of content searching CHN's (75A) metadata into the prospective customer database (75D), and in an another instance one or more CHNs and 3 parties providing for personalized preferences in the HSN prospective customer preferences DB (75M). Each of intended advertiser downloading advertisement wizard and management system and registering with HSN controller (75C) and requesting package key therefrom for posting one or more advertisements campaigns at HSN advertisement and tracking database (75H) and/or at HSNOP (75N) by means of HSN advertise wizard and management system; each of associated channel node involved in the accomplishment of the adrouting are governed via business logic to the each of associated channel nodes, subscribers and advertisers for fees and commission receipts or payments; HSNOP (75N) facilitating advertisement posting for various advertisers and eCommerce operations via multi vendor shopping cart for matched adviewers and further synchronizing the entry of each of products or services into the respective taxonomywise listing at HSNOP from advertise and tracking database thereof.

[0433] Each of the associated channel nodes for said advertisement are being determined via at least one correspondence relationship of each of CHN including: [0434] 1. CHNs posting, routing, hitting or linking the said advertise [0435] 2. CHNs referring the said prospective customers stored in the URL attached therewith the said advertise [0436] 3. CHNs offering sponsored services for the said advertise and [0437] 4. Prospective customers of the said advertise.

[0438] The said correspondence relationship is used to determine the payments and commissions for stipulated activities wherein HSN controller receiving the payments for each advertisement posting and later for commissions effected thereby in the further process of routing, linking and viewing of each of the said advertise campaign wherein the receipt of payments from and delivery of commissions to each of correspondingly related CHN is carried out by determinants thereof.

[0439] In an human alternative to ad sense generated via IN and OUT keyword tracking one or more Human Agents (HSNHA) and service Providers (HSNSP) registering with HSN controller for offering sponsored services (SP) (75K) forming the network thereof wherein the advertise management system attaching the related one or more advertisements with each of communication of each of sponsored service provider (SSP) (75K).

[0440] HSN controller determining CTR (Click Through Rate) wherein determining the no of impressions per hit signifying the conversion factor of impressions into actual hits by means of the business logic unit (75J)

[0441] FIG. 76 showing the graphical user interface (GUI) for the search macro management, wherein provided with explorer (76C) for devising taxonomically organized projects and formulating plurality of subgroups therein the said project having one or more keywords to configure macros. The utilities section (76B) having various utilities for recording, testing and deployment of such configured macros. Further the utilities provide for project opening, editing, archiving and tagging, importing, inviting, replicating, ranking, collaborating, applying security features, notification, and SSS & KSS management. Each of human agents and serviced providers offering the subscription to such configured search macros by means of search macros package keys.