JP2005508558A - Requirement matching system and method - Google Patents

Abstract

A real-time request matching system and method for matching a free format request to a provider of a user as a requester when processing the request. Each of the requesters has at least one communicator for creating a request and addressing an answer to it, and each of the providers is at least one for addressing the request and a respective answer to it. Has two communicators. The method is based on receiving a request from a requester, for each request, allowing the request to be relayed to a selected provider, and thereby addressed. Receiving a response from the provider created by each provider, and an affirmative response indicates that the provider can accept the request, and for each request, information about each requestor is provided for each request. Providing one or both of providing an affirmative answer to any given provider and providing information about the answer to each request from the selected provider to each requestor.

Description

【Technical field】
[0001]
The present invention relates to a request matching system and method for matching a request to a provider (provider) of a user as a requester (requester) when the request is processed.
[0002]
The present invention finds application in many fields, but particularly in a classification structure where the user wishes to create a request for a community of interests, ie, a plurality of commonly classified providers, as a requester. Heading.
[0003]
It is foreseen that the present invention will find special applications related to transaction classification where providers are grouped according to the goods and services offered.
[0004]
Such transaction classifications are currently embodied as local transaction directories, such as Yellow Pages (registered trademark) or Thomson Directory (registered trademark) in the UK. Then, when looking for an object or service, a person uses the local directory to determine the location of the provider for the object or service.
[0005]
When using such a directory, a person first determines the classification that is most likely to supply the product or service, reviews the corresponding section in the directory, selects one or more providers, and then assigns them to those providers. to call. When calling a provider, for example, the same request is repeatedly made to each provider, "Can you provide goods / services X at cost Y by Z days?" Often, especially if the request is specified, for example, "Is there an inventory of auto parts X?", The person calls many of the selected providers and submits the request. There is a need to find one provider that can be met. This is a special case where two or more providers must be identified, for example to be able to compare costs and delivery times.
[0006]
Such a process is time consuming because it must first identify possible providers and then establish conversations with many providers before one or more providers can be identified that can satisfy the request. . In addition, the telephone costs associated with each of the many providers are relatively expensive.
[0007]
Although the present invention is envisaged to find special applications related to transaction classification, the present invention also has applications related to many other classification structures.
[0008]
One such other classification structure is broadcast classification. In this case, a single request is broadcast to multiple providers, allowing them to get answers from all of the providers and logging one or both positive and negative answers from the providers, as well as providers that do not answer. Like that. It is foreseen that such classification will find application in obtaining information in response to questions in building, for example, marketing lists and polls.
[0009]
Another such other classification structure is community classification. In this case, people with common interests are categorized in common and allow one request to be made by one requestor. This requester can also be a single provider in the community classification. This provider is included in some or all of others as providers in the community classification. An example of community classification is a local help group. Members of this group give assistance for each specific issue. Requests for assistance can be made by members.
[0010]
Another such classification structure that is different is task classification. In this case, one request is created for a plurality of providers that need to perform one task. It is foreseen that such a classification will find particular application in a collective environment. In this case, the request can be made by a special department, such as a purchasing or marketing department.
[0011]
Yet another such classification structure that is different is the promotion classification. In this case, special promotions are typically run for a short time and are supported by multiple providers. An example of a promotion classification is a holiday break, for example a fixed price weekend break. In this case, the provider who wishes to participate in the promotion decides to join the classification. In a preferred embodiment, providers have the ability to decide access to their classification according to the availability of goods and services provided by their respective providers.
[0012]
One object of the present invention is to provide a request matching system and method for matching requests to a provider of a user as a requester. In this case, the requester is not required to identify possible providers and contact them to determine if the request can be accepted.
[0013]
In one form, the present invention provides a matching system for matching a request to a user's provider as a requester when processing the request. Each of the requesters has at least one communicator for creating a request and addressing a respective answer thereto, and each of the providers is provided for addressing a request and a respective answer thereto. Having at least one communicator. The system includes at least one request receiving unit for receiving a request from a requester, and at least one for causing each of the requests to be relayed to a selected provider thereby addressed. One request relay unit, at least one answer receiving unit for receiving an answer from the provider created by each provider as a human decision maker based on each request, and For each request, provide information about each requestor to any provider given an affirmative response to each request, and indicate each request from the selected provider Information about the response to the request for each request It is fed to motor, comprising one or at least one information supplying unit for performing both.
[0014]
The system is preferably a real time matching system.
[0015]
The request is preferably a free format request.
[0016]
The request preferably includes a voice request.
[0017]
The communicator preferably includes mobile communicators such as telephones, PDAs, personal computers and gaming devices.
[0018]
The communicators preferably include fixed communicators such as telephones, fax machines, personal computers, set top boxes and game consoles.
[0019]
The communicator preferably comprises a hybrid fixed / mobile communicator such as a telephone.
[0020]
In one embodiment, the system comprises at least one inbound communication unit, each having at least one request receiving unit.
[0021]
In one embodiment, the system comprises at least one outbound communication unit, each having at least one request relay unit, at least one answer receiving unit, and at least one information supply unit.
[0022]
In another embodiment, the system comprises at least one communication unit, each of which has at least one request receiving unit, at least one request relay unit, at least one answer receiving unit, and at least one information supply. Unit.
[0023]
In one embodiment, the at least one request relay unit is configured to relay a request directly to a selected provider's communicator.
[0024]
The at least one request relay unit is preferably configured such that the request is relayed without making an inquiry and setting the content.
[0025]
Preferably, the at least one request receiving unit includes a plurality of receivers for receiving requests, each request having a classification contact address associated with a predeterminable classification.
[0026]
More preferably, the classification contact address is a dial number.
[0027]
In one embodiment, the system further comprises at least one provider selection unit for selecting a provider to address the request.
[0028]
The at least one provider selection unit is a provider for requests based at least in part on a geographical location assigned to each request and one or both of a geographical location or a geographical area assigned to the provider. It is preferable that it is comprised as what selects.
[0029]
In one embodiment, the geographic location assigned to each request is the current geographic location of each requester.
[0030]
Preferably, the current geographical location is a communicator contact address of a communicator of each requester, and the communicator contact address has an assigned location.
[0031]
More preferably, the communicator contact address is a dial number.
[0032]
In one embodiment, the geographic location assigned to each request is an alternate geographic location assigned by each requester.
[0033]
The alternative geographic location is determined from a communicator's communicator contact address, and the communicator contact address preferably has an assigned location.
[0034]
More preferably, the communicator contact address is a dial number.
[0035]
The geographical location of the mobile communicator is preferably determined from one of cell identification methods, triangulation methods, radio location methods or satellite location methods such as GPS.
[0036]
The geographic location of the fixed communicator is preferably determined from each assigned location.
[0037]
The at least one provider selection unit is preferably configured to select a provider for the request within a spatial geographical area that is predeterminable for the geographical location assigned to each request.
[0038]
The predeterminable spatial geographic area is assigned to each request, whether it is a geographical radius for the geographical location assigned to each request, or a distance of movement for the geographical location assigned to each request. More preferably, it is one of the times of travel relative to the geographical location.
[0039]
The at least one provider selection unit is based at least in part on at least one requestor feature for each requester, for example, as an assigned feature for each requestor or as a feature input when creating information by each requester, It is preferably configured to select a provider for the request based on geographically relevant socio-economic information.
[0040]
The at least one provider selection unit has a predeterminable profile, at least in part, based on at least one provider feature for the provider, eg as an assigned feature for the respective provider, or contact details Is preferably configured to select a provider for the request based on requesting the requestor to provide the request.
[0041]
The at least one provider selection unit is preferably configured to select a provider for the request based at least in part on the current time.
[0042]
The at least one provider selection unit selects a provider for the request based at least in part on at least one classification feature, eg, based on a selection mechanism for selecting a provider, as an assigned feature for each classification. It is preferable to be configured for selection.
[0043]
The at least one request relay unit is preferably configured to relay the request to a predeterminable number of selected providers thereby addressed.
[0044]
The at least one request relay unit is configured to multicast a request to a selected provider, the request being relayed to a plurality of providers and thereby addressed. preferable.
[0045]
Preferably, the at least one information supply unit is configured to supply, to each requester, information regarding a provider who has been given an affirmative response to the request.
[0046]
In another form, the present invention provides a matching system for matching a request to a user's provider as a requester when processing the request. The system includes a plurality of requester communicators and a plurality of provider communicators. Each requestor communicator is used by the requester when creating a request and addressing its respective answer to it, at least some of the answers being sent from the selected provider to the respective requestor. Contains information about the answers, each provider communicator is used by the provider when addressing the request and the respective answer to it, and the request is addressed to the respective selected provider And at least some of the requests contain information about the requesters of each request, a positive response is given for each request, and a positive response is received by the provider. It shows that can be done.
[0047]
The system is preferably a real time matching system.
[0048]
The request is preferably a free format request.
[0049]
The request preferably includes a voice request.
[0050]
The communicator preferably includes mobile communicators such as telephones, PDAs, personal computers and gaming devices.
[0051]
The communicators preferably include fixed communicators such as telephones, fax machines, personal computers, set top boxes and game consoles.
[0052]
The communicator preferably comprises a hybrid fixed / mobile communicator such as a telephone.
[0053]
In one embodiment, the request is relayed directly to each selected provider.
[0054]
The request is preferably relayed without making an inquiry and setting the content.
[0055]
Preferably further comprising a communication unit including a plurality of receivers for receiving requests, each request having a classification contact address associated with a predeterminable classification.
[0056]
More preferably, the classification contact address is a dial number.
[0057]
Preferably, a provider for a request is selected based at least in part on the geographic location assigned to each request and one or both of the geographic location and / or geographic area assigned to the provider.
[0058]
In one embodiment, the geographic location assigned to each request is the current geographic location of each requester.
[0059]
Preferably, the current geographical location is a communicator contact address of a communicator of each requester, and the communicator contact address has an assigned location.
[0060]
More preferably, the communicator contact address is a dial number.
[0061]
In one embodiment, the geographic location assigned to each request is an alternate geographic location assigned by each requester.
[0062]
The alternative geographic location is determined from a communicator's communicator contact address, and the communicator contact address preferably has an assigned location.
[0063]
More preferably, the communicator contact address is a dial number.
[0064]
Preferably, providers are selected within a spatial geographic area that is predeterminable for the geographical location assigned to each request.
[0065]
Geographically relevant socio-economic information, at least in part, based on at least one requester feature for each requester, eg, assigned features for each requestor or feature input when creating information by each requester Based on which the provider for the request is preferably selected.
[0066]
At least in part requires the requestor to have a predeterminable profile or provide contact details based on at least one provider feature for the provider, eg, as an assigned feature for each provider Based on that, the provider for the request is preferably selected.
[0067]
The provider for the request is preferably selected based at least in part on the current time.
[0068]
Preferably, the provider for the request is selected based at least in part on at least one classification feature, eg, based on a selection mechanism for selecting a provider, as an assigned feature for each classification.
[0069]
In a different form, the present invention provides a matching system for matching a request to a user's provider as a requester when processing the request. Each of the requesters has at least one communicator for creating a request and addressing an answer thereto, and each of the providers has at least one communicator for addressing the request. The system includes at least one request receiving unit for receiving a request from a requester, and at least one for causing each of the requests to be relayed to a selected provider thereby addressed. One request relay unit and at least one answer receiving unit for receiving an answer from a provider created by each provider as a human decision maker based on each request.
[0070]
In yet another form, the present invention provides a matching system for matching a request to a user's provider as a requester when processing the request. The system includes a plurality of requester communicators, a plurality of provider communicators, and at least one communication unit capable of communicating with the requester communicators and the provider communicators.
Each requestor communicator is used by the requester when creating a request and addressing its respective answer to it, and each provider communicator when addressing a request and its respective answer to it Wherein the at least one communication unit includes at least one provider selection unit for selecting a provider and addressing each request made by the requestor, the system comprising: In response to a request, the request is configured as a human decision maker to be relayed to a selected provider thereby being addressed.
[0071]
Preferably, the system is further configured such that for each request, each respective requester is provided with information regarding a response to the request from a selected provider.
[0072]
The system is preferably a real time matching system.
[0073]
The request is preferably a free format request.
[0074]
The request preferably includes a voice request.
[0075]
The communicator preferably includes mobile communicators such as telephones, PDAs, personal computers and gaming devices.
[0076]
The communicators preferably include fixed communicators such as telephones, fax machines, personal computers, set top boxes and game consoles.
[0077]
The communicator preferably comprises a hybrid fixed / mobile communicator such as a telephone.
[0078]
In one embodiment, the system is configured to relay requests directly to the provider communicator of a selected provider.
[0079]
The system is preferably configured such that the request is relayed without making an inquiry and setting the content.
[0080]
Preferably, the at least one communication unit includes a plurality of receivers for receiving requests, each request having a classification contact address associated with a predeterminable classification.
[0081]
More preferably, the classification contact address is a dial number.
[0082]
The at least one provider selection unit is a provider for requests based at least in part on a geographical location assigned to each request and one or both of a geographical location or a geographical area assigned to the provider. It is preferable that it is comprised as what selects.
[0083]
In one embodiment, the geographic location assigned to each request is the current geographic location of each requester.
[0084]
Preferably, the current geographical location is a communicator contact address of a communicator of each requester, and the communicator contact address has an assigned location.
[0085]
More preferably, the communicator contact address is a dial number.
[0086]
In one embodiment, the geographic location assigned to each request is an alternate geographic location assigned by each requester.
[0087]
The alternative geographic location is determined from a communicator's communicator contact address, and the communicator contact address preferably has an assigned location.
[0088]
More preferably, the communicator contact address is a dial number.
[0089]
The at least one provider selection unit is preferably configured to select providers within a spatial geographical area that can be predetermined for the geographical location assigned to each request.
[0090]
The predeterminable spatial geographic area is assigned to each request, whether it is a geographical radius for the geographical location assigned to each request, or a distance of movement for the geographical location assigned to each request. More preferably, it is one of the times of travel relative to the geographical location.
[0091]
The at least one provider selection unit is based at least in part on at least one requestor feature for each requester, for example, as an assigned feature for each requestor or as a feature input when creating information by each requester, It is preferably configured to select a provider for a request based on geographically relevant socio-economic information.
[0092]
The at least one provider selection unit has a predeterminable profile, at least in part, based on at least one provider feature for the provider, eg as an assigned feature for the respective provider, or contact details Is preferably configured to select a provider for the request based on requesting the requestor to provide the request.
[0093]
The at least one provider selection unit is preferably configured to select a provider for the request based at least in part on the current time.
[0094]
The at least one provider selection unit selects a provider for the request based at least in part on at least one classification feature, eg, based on a selection mechanism for selecting a provider, as an assigned feature for each classification. It is preferable to be configured for selection.
[0095]
The system is preferably configured to relay the request to the provider communicator of a predeterminable number of selected providers as addressed thereby.
[0096]
The system is configured to multicast the request to the provider communicator of each selected provider, and each request is relayed to multiple providers thereby addressed. It is preferable.
[0097]
In yet another aspect, the present invention provides a method for matching a request to a user's provider as a requester when processing the request. Each of the requesters has at least one communicator for creating a request and addressing an answer to it, and each of the providers is at least one for addressing the request and a respective answer to it. Has two communicators. The method is based on receiving a request from a requester, for each request, allowing the request to be relayed to a selected provider, and thereby addressed. Receiving a response from the provider created by each provider as a human decision maker, and an affirmative response for each request, indicating that the provider can receive the request One or both of supplying information about each requestor to any provider given an affirmative response to each request and providing information to each requestor about the response to each request from the selected provider The step of performing.
[0098]
The method is preferably a real time matching method.
[0099]
The request is preferably a free format request.
[0100]
The request preferably includes a voice request.
[0101]
The communicators preferably include mobile communicators such as telephones, PDAs, personal computers and gaming devices.
[0102]
The communicators preferably include fixed communicators such as telephones, fax machines, personal computers, set top boxes and game consoles.
[0103]
The communicator preferably comprises a hybrid fixed / mobile communicator such as a telephone.
[0104]
In one embodiment, allowing the request to be relayed to and addressed by the selected provider includes relaying the request directly to the communicator of the selected provider.
[0105]
The request is preferably relayed without making an inquiry and setting the content.
[0106]
Receiving the request from the requester includes receiving the request from the requester at a plurality of receivers, preferably each of the requests has a classification contact address associated with a predeterminable classification.
[0107]
More preferably, the classification contact address is a dial number.
[0108]
In one embodiment, the method further comprises selecting a respective provider that addresses the request.
[0109]
Selecting each provider addressing the request is based at least in part on the geographic location assigned to each request and one or both of the geographic location or geographic area assigned to the provider. Preferably, the method includes the step of selecting each provider addressing the request.
[0110]
In one embodiment, the geographic location assigned to each request is the current geographic location of each requester.
[0111]
Preferably, the current geographical location is a communicator contact address of a communicator of each requester, and the communicator contact address has an assigned location.
[0112]
More preferably, the communicator contact address is a dial number.
[0113]
In one embodiment, the geographic location assigned to each request is an alternate geographic location assigned by each requester.
[0114]
The alternative geographic location is determined from a communicator's communicator contact address, and the communicator contact address preferably has an assigned location.
[0115]
The communicator contact address is preferably a dial number.
[0116]
The geographical location of the mobile communicator is preferably determined from one of cell identification methods, triangulation methods, radio location methods or satellite location methods such as GPS.
[0117]
The geographic location of the fixed communicator is preferably determined from the assigned location.
[0118]
Selecting each provider addressing the request includes selecting each provider addressing the request within a spatial geographic area determinable with respect to the geographic location assigned to the request. It is preferable.
[0119]
The predeterminable spatial geographic area is assigned to each request, whether it is a geographical radius for the geographical location assigned to each request, or a distance of movement for the geographical location assigned to each request. More preferably, it is one of the times of travel relative to the geographical location.
[0120]
The step of selecting each provider addressing the request is based at least in part on at least one requester feature for each requester, for example, an assigned feature for each requestor or a feature during creation of information by each requester. Preferably, the method includes the step of selecting each provider addressing the request based on the geographically relevant socio-economic information as input.
[0121]
Selecting each provider addressing the request has a predeterminable profile, at least in part, based on at least one provider feature for the provider, eg, as an assigned feature for each provider; Or preferably, based on requesting the requestor to provide contact details, selecting a respective provider to address the request.
[0122]
Preferably, selecting each provider addressing the request includes selecting each provider addressing the request based at least in part on the current time.
[0123]
The step of selecting each provider addressing the request is based at least in part on at least one classification feature, eg, based on a selection mechanism for selecting a provider, as an assigned feature for each classification. Preferably, the method includes the step of selecting each provider addressing the request.
[0124]
Allowing the request to be relayed to and addressed by the selected provider is relaying the request to and addressed by a predeterminable number of selected providers It is preferable to contain.
[0125]
Allowing the request to be relayed to the selected provider and thereby addressed includes multicasting the request to the selected provider, the request being thereby transmitted to the plurality of providers. It is preferably relayed to be addressed.
[0126]
Preferably, the step of providing information includes the step of providing, for each request, information about the provider that has been given an affirmative response to said request to the respective requester.
[0127]
In yet another aspect, the present invention provides a method for matching a request to a user's provider as a requester when processing the request. Each of the requesters has at least one communicator for creating a request and addressing an answer thereto, and each of the providers has at least one communicator for addressing the request. The method is based on receiving a request from a requester, for each request, allowing the request to be relayed to a selected provider, and thereby addressed. Receiving a response from the provider created by each provider as a human decision maker.
[0128]
In yet another form, the present invention provides a method for matching a request to a user's provider as a requester when processing the request. The method includes receiving a signal having a request from a requester, sending a signal having the request as received to a selected provider for each request, and based on each request. Receiving a signal created by the respective provider with a response from the selected provider, and an affirmative response indicating that the provider can accept the request, for each request, for each request Send one or both of a signal with information about each requester for any provider given a positive response and a signal with information about the response to each request from the selected provider for each requester And providing a step.
[0129]
The present invention, known as the Responsa ™ matching system, provides an automated matching system. This system specifically allows voice requests, particularly free format requests, to be matched with a provider receiving the request and confirming that the request is acceptable.
[0130]
In the preferred embodiment, this matching is achieved based on the location associated with the requester, typically the location of the requestor's communicator, the provider's assigned location in the selected classification, and the selected classification. The In other embodiments, the current time and characteristics of one or both of the requester and provider are available for provider selection.
[0131]
According to the present invention, the received request is relayed to the selected provider and replayed for a voice request. If any provider cannot fulfill the request, must the provider simply decline the request, typically by keying in response to a “reject” or “reject” response? Or you just have to turn off the communicator. When the request is relayed, all communication by the requester and provider is one-way communication. Thus, there is no direct conversation required between the requester and one provider. Both parties avoid time-consuming tasks that have to establish a polite discussion when their providers are unable to satisfy the request. Direct conversation is only possible between the requester and one provider that can satisfy the request.
[0132]
The present invention allows for automated matching and further allows individuals to communicate in a free format fashion. The preferred embodiment of the present invention gives the requester the freedom to shape the request as desired when utilizing a free format request. The language and form of the request is not constrained by, for example, requesting the requester to use a predetermined keyword.
[0133]
In addition, the present invention is defined by a special classification for providers that wish to receive requests and are in a position to process the requests, for example, providers that are in business and are in a unique geographic area. Just relay the request.
[0134]
In the present invention, what receives a request and intelligently interprets the request is a human decision maker, unlike a computer. This avoids problems associated with matching systems that require a requirement to be defined using a predetermined keyword, for example by using a drop-down menu.
[0135]
Furthermore, the present invention finds application in both personal environments that are manipulated by the organization to be used by members of the organization and in social environments that allow use by members of society.
[0136]
In certain embodiments, the present invention may be configured to bias the match to benefit either the requester or the selected provider. This is expected to be appropriate in some niche applications, especially in the personal environment.
[0137]
Hereinafter, preferred embodiments of the present invention will be described by way of example only with reference to the accompanying drawings.
[0138]
This matching system comprises at least one telephone management (TM) system 1 for managing inbound telephone calls to and from outbound telephone calls to the matching system, in this embodiment first and second TM systems 1a. , 1b. This matching system has a single TM system 1 in another embodiment and any number of TM systems 1, in the different embodiments, from tens to hundreds.
[0139]
The TM systems 1a and 1b are arranged in the same place in this embodiment, but are arranged apart in other embodiments. In one such embodiment, the TM systems 1a, 1b are located at remote locations within one geographic region. As an example, within the UK, one TM system 1a is located in one center, eg London, serving the southern half of the UK, while the other TM system 1b is located in another center, eg Glasgow, Serving the northern half of the UK. In other embodiments including multiple TM systems 1, the TM system 1 is located in a major center, for example, a city or town across an entire geographic area.
[0140]
The matching system further comprises a first communication network 3 that provides a communication link to and between the TM systems 1a, 1b.
[0141]
In this embodiment where the TM systems 1a, 1b are located at the same location, the communication network 3 comprises a local area network (LAN) such as Ethernet.
[0142]
In another embodiment in which the TM systems 1a, 1b are remotely located, the communication network 3 comprises a telephone network, preferably an integrated digital communication service network (ISDN).
[0143]
Each TM system 1a, 1b comprises an inbound telephone management (ITM) unit 5 for managing inbound telephone calls from requesters on the inbound telephone line 7, preferably the ISDN line. In this embodiment, multiple subscriber numbering (MSN) is used so that multiple requesters, each requiring the same classification, can be supported simultaneously.
[0144]
The ITM unit 5 is connected to an inbound telephone line 7 for monitoring inbound telephone calls, and an inbound interactive voice response (IIVR) module 11 that supports voice and key tones, as described in more detail below. An inbound telephone application management (ITAM) module 13 for generating a request document corresponding to the request at each of the telephone calls, in this embodiment a voice request, and for sending it to the provider selection units 33a, 33b, 33c; , For storing a classification feature for each classification, for storing a first classification feature (CC) database 15 connected to the ITAM module 13 and information about the requester, the ITAM Liquid connected to module 13 Star Information (RI) and a database 17.
[0145]
With this configuration, the CC database 15 and the RI database 17 are not accessible to the IIVR module 11, thereby preventing the RI database 17 from being accessed by a third party. In this embodiment, the ITM unit 5 has an intrusion detector between the IIVR module 11 and the ITAM module 13. This is intended to monitor the intrusion of a third party and to keep the ITAM module 13 safe by identifying abnormal packets.
[0146]
In this embodiment, the communication between the IIVR module 11 and the ITAM module 13 is based on the VoiceXML communication protocol.
[0147]
In this embodiment, the request document generated by the ITAM module 13 is a called party number, i.e. a telephone number called by the requester, in this embodiment, a classification identifier identifying the classification to which the request is matched; In this embodiment, the caller's line identification (CLI) of the requester's telephone, that is, the telephone number for the system or the provider that responds to respond in response to the request, the requester identifier identifying the requester, and the relay to the provider A request file corresponding to the request to be made, in this embodiment, at least an audio file corresponding to the voice request to be played back to the provider. In an alternative embodiment, the requester identifier is a phone number, which is either derived from the requester's phone CLI or information including, for example, an authentication code provided by the requester at the time of request creation.
[0148]
In an alternative embodiment, the request document generated by ITAM module 13 can omit the request file for the request, as described in more detail below. This is the case if the file is stored in an accessible file store 19 to allow subsequent requests to be relayed.
[0149]
In this embodiment, the request document generated by the ITAM module 13 includes a location identifier that identifies the location of the search center if the provider identification units 33a, 33b, 33c cannot determine the location of the requester from the requester identifier. . A typical example where the requester identifier does not make it possible to determine the location of the requester is that the requester is not in the directory, otherwise the requester is not given an address for the calling party number, or the calling party The result is that the calling phone is a mobile phone, or the requester is seeking an alternate location from the search center. In this embodiment, the location identifier is a phone number other than the calling phone number, which is given by the requestor to represent the location of the search center.
[0150]
In this embodiment, the CC database 15 is a structured query language (SQL) database.
[0151]
In this embodiment, the components of the ITM unit 5, that is, the IIVR module 11, the ITAM module 13, the CC database 15, and the RI database 17 are arranged at the same position.
[0152]
In other embodiments, the IIVR module 11 and the ITAM module 13 are located at the same location, and one or both of the CC database 15 and the RI database 17 are located remotely. In this embodiment, the communication network between the ITAM module 13, the CC database 15, and the RI database 17 is a virtual private network (VPN).
[0153]
In different embodiments, one or both of the IIVR module 11 and the ITAM module 13 are located remotely, and the CC database 15 and the RI database 17 are located at the same location.
[0154]
In a further different embodiment, the components of the ITM unit 5, i.e. the IIVR module 11, the ITAM module 13, the CC database 15, and the RI database 17, are located remotely.
[0155]
Each of the TM systems 1a, 1b further comprises a file store 19 for storing classification greetings and prompts for the supported classifications. As described above, in one embodiment, the file store 19 stores a request file for each request from the requester. This storage of the request file allows the request file to be retrieved. Thus, the request document need not contain the request file. Thus, if the size of the requested document is small, a significantly high traffic (call volume) flow is possible for the same system capacity.
[0156]
Hereinafter, the operation of the ITM unit 5 of the TM systems 1a and 1b will be described.
[0157]
Each ITM unit 5 receives a requestor communicator 20 on the respective inbound telephone line 7, in this embodiment an inbound telephone call from the telephone. In this case, the special ITM unit 5 receives the telephone call indicated by the called party number, i.e. the number called by the requester.
[0158]
In this embodiment where the matching system is configured to operate as a transaction classification matching system, a requester can select from a plurality of classification entries corresponding to different types of goods and service providers. Each classification entry has an associated telephone number that the requester must dial to access the matching system for that classification. This is a classification identifier in this embodiment. This identifier determines the search criteria, matching criteria and termination criteria with which the matching operation is performed, as will be described in more detail below. In one embodiment, each classification entry may include a summary of one or both of services and things. This is so that the requester can determine that the correct classification has been selected for that particular requirement.
[0159]
For each inbound call, the IIVR module 11 sends to the ITAM module 13 the called party number and the calling party number, i.e., the calling line identifier (CLI) of the requester communicator 20 that is the calling party communicator. Send. In this embodiment, the requester communicator 20 is a landline phone, a mobile phone, a combined fixed / mobile phone, or a PDA.
[0160]
The ITAM module 13 searches for the called party number in the CC database 15 and searches the classification greeting file identifier for a “classification” greeting to be played back to the requester.
[0161]
If the called party number is not associated with a classification, for example if the called party number was previously used in association with a classification but is not currently used, the ITAM module 13 instructs the IIVR module 11. To execute the “unassigned classification” script. This script plays the “unassigned classification” greeting and closes the call connection.
[0162]
If the calling communicator 20 does not have a CLI because CLI is prohibited, the ITAM module 13 instructs the IIVR module 11 to execute the “number not used” script. This script plays the “No Number” greeting. This greeting instructs the requester to enable the calling party's CLI or to provide an authentication code associated with the register as an authenticated requester.
[0163]
In this embodiment, the system is configured to allow the requester to handle the request only when the inbound call has a CLI. By requiring the use of a CLI-capable communicator 20, misuse of the system by a requester that directs an answer to a third party is prevented.
[0164]
If the calling side communicator 20 has a CLI, the ITAM module 13 searches the RI database 17 for the CLI of the calling side communicator 20 to check the requester information, for example, the position information is for the CLI. Make sure it is available and get default requester preferences for whether requester details for the requester are given to the provider or not used, for example.
[0165]
If the CLI of the calling party communicator 20 is that of a fixed communicator and the RI database 17 contains location information for the CLI of the calling party telephone, the ITAM module 13 instructs the IIRV module 11 to “ Run the "fixed requester" script.
[0166]
If the CLI of the calling communicator 20 is that of the mobile communicator and the RI database 17 does not contain default location information for the CLI of the calling communicator 20, the ITAM module 13 will call the calling communicator. The 20 locations are determined from the network information and instructed to the IIRV module 11 to execute the “Move Requester” script. In this embodiment, the cell ID for the calling communicator 20 is used to determine the location of the requester. This cell ID represents a cell which is a geographical area where the calling side communicator 20 is arranged. In this case, the ITAM module 13 searches the cell ID in the RI database 17 to obtain the position of the calling side communicator 20. In other embodiments, the requester's calling communicator 20 is determined by triangulation, radio location, or satellite location such as GPS.
[0167]
If there is a CLI but, for example, the requester is not listed in the directory and the position cannot be determined from that CLI, that is, the requester wants the service provider not to disclose the location information corresponding to the requester communicator 20 number. If the location information is not otherwise provided by the requester, the ITAM module 13 searches the CC database 15 for a search vector corresponding to the classification corresponding to the called party number, and a vector for handling the requester not related to the location. Determine whether there is. When there is a vector for handling a requester not related to the position, the ITAM module 13 uses the vector. If there is no vector to handle requesters that are not related to position, the ITAM module 13 instructs the IIRV module 11 to execute the “required position” script. The script plays the “required location” greeting and advises the requester with location information, typically a known CLI capable phone number. For this purpose, position information is held in the CC database 15 and operates as a search center.
[0168]
If there is a CLI but the calling party number is that of a switch board (manned or automatic), the ITAM module 13 instructs the IIRV module 11 to execute the appropriate “switch board requester” script.
[0169]
Under the “fixed requester” script and the “move requester” script, the IIRV module 11 plays a “category title” greeting corresponding to the retrieved category greeting identifier and then facilitates the request from the requester. Play the greeting. For example, if the called party number corresponds to the classification “toy store”, in this embodiment the classification greeting is “Responsa for toy store”. ^TM ) "Welcome to Classification" and "Request Prompt" greeting becomes "Leave your request after tone and hang up when finished".
[0170]
Under the “Switchboard Requester” script, the IIRV module 11 provides an extension number, typically by keying or voice response of the “category title” greeting corresponding to the retrieved category greeting identifier. The "extension identification" greeting that prompts the requester and the "request prompt" greeting that prompts the request from the requester are reproduced in order. In this embodiment, the “request prompt” greeting is played only following a predetermined keystroke at the calling party communicator 20. This keystroke confirms the supply of the extension number of the calling side communicator 20. For example, if the called party number corresponds to the category “toy store”, in this embodiment the “category title” greeting is “Responsa for toy store”. ^TM ) "Welcome to Classification" and "Extension Identification" greeting becomes "Please leave your extension number after the tone and then press X" and then follow the required keystrokes and "Request Prompt" The greeting becomes "Leave your request after the tone and hang up when finished".
[0171]
If the requester wants to set alternative preferences, for example to suppress contact details from the provider, and the default is to give details to the provider and give alternative search center locations or alternative search parameters, IIVR Module 11 allows entry of keystrokes that set these preferences.
[0172]
In this embodiment, the IIVR module 11 is configured to enable request recording. This is done, for example, by key entry with a predetermined keystroke if the requester makes a mistake when recording a request.
[0173]
In this embodiment, the IIVR module 11 is also configured to allow the request to be reviewed before it starts the matching operation, here it can be played back.
[0174]
In this embodiment, the call connection is closed after a predetermined period of time following the “request prompt” greeting, or when the requester hangs up if this event is identifiable by the IIVR module 11.
[0175]
In this embodiment, the ITAM module 13 stores each request in the file store 19 with the assigned file name.
[0176]
Each of the TM systems 1a, 1b has an outbound telephone management (OTM) for managing outbound calls destined for the provider on the provider communicator 24 and the requester on the requester communicator 20 on the outbound line 23, preferably the ISDN line. ) The unit 21 is further provided.
[0177]
The OTM unit 21 follows an outbound interactive voice response (OIVR) module 25 connected to the outbound line 23 to fulfill an outbound call to the provider and requester, and according to the call document received from the provider selection units 33a, 33b, 33c. And an outbound telephone application management (OTAM) module 27 for scheduling and directing calls to the OIVR module 25. In this embodiment, the calling document is scheduled according to a priority flag. In this case, for example, the status report for the requester has a lower priority than the request for the provider.
[0178]
In operation, when an outbound call is made to the provider, the OIVR module 25 dials the number of the provider communicator 24 identified in the call document.
[0179]
If there is a response to the call to provider communicator 24 made by the OIVR module 25, the OIVR module 25 executes a “request playback” script. This first reproduces a “VRS welcome” greeting, such as “VRS for hairdressers”. This is followed by a first short tone. Subsequently, the request to the provider is reproduced. This is followed by a second short tone. In this embodiment, the request is relayed, here replayed, without a query such as by speech recognition (since it is not necessary). The classification is indicated by the called party number. In alternative embodiments where a more precise or elaborate matching system is required, the requirements are queried.
[0180]
When listening to the request, the provider has the following answer options: Each option has an associated keystroke.
[0181]
“Accept” is confirmation that the request is satisfied. For example, if the request is “Can you barber?”, That is, if the requester is just trying to get details of a local hairdresser and the request is appropriate, the provider Answer “Accept”.
[0182]
“Maybe” indicates that the request is probably fulfilled, but the provider must confirm. If the request is complex, for example, “Can you schedule a hairdressing next 1530 hours?”, The provider may remember that the next Wednesday afternoon is not fully booked, but the exact It is necessary to check if there is a free time. In such a case, the provider answers “maybe”.
[0183]
“Deny” is confirmation that the request is not satisfied. In this embodiment, hanging up is equivalent to the answer option “reject”.
[0184]
“Inappropriate” indicates that the request is either inappropriate for classification or unintelligible.
[0185]
“Unauthorized” indicates that the request is considered to be unauthorized.
[0186]
In this embodiment, provider answers are logged, allowing, for example, a classification manager to monitor the behavior of providers and some requesters. This behavior makes it possible to provide guidance aimed specifically at providers and requesters. It also even allows the provider or requestor to be prohibited if the behavior is not acceptable.
[0187]
For example, an “inappropriate” answer is logged to both the provider answering so and the requester that created the request. This is because repeated “inappropriate” answers are made either by requesters or providers who are confused about the purpose of classification.
[0188]
Also, the “illegal” answer is logged to both the provider answering so and the requester that created the request. In this embodiment, in addition to terminating the matching operation, the repeated “incorrect” answer established by the confirmed “incorrect” answer allows each requestor to ban the use of the classification and even the entire matching system. Result. In this embodiment, repeated “illegal” answers that are significantly above the average for a single classification, typically by a provider, will be investigated.
[0189]
When the provider gives an affirmative answer, ie one of the answer options “accept” or “maybe” in this embodiment, the OIVR module 25 executes the “acknowledge” script. This script plays the greeting “Answer answered”. This is followed by a short tone. The script also updates the call document to include an affirmative identifier and sends the updated call document to the originating provider selection unit 33a, 33b, 33c.
[0190]
If the requester's contact details are refrained, the “Acknowledgement” script will also play a “contact details refrained” greeting.
[0191]
If the contact details are not reserved, the “Acknowledge” script also provides contact details for the requester. This is followed by a short tone. In one embodiment, the provider can record the requester details and then call the requester. In another embodiment, the provider can contact the requester directly by a predetermined keystroke. If the requester is following a process on the line, the requester can connect directly to the provider if the provider is still on the line.
[0192]
If the calling communicator 20 is from an extension off the manned switch board, the “Acknowledge” script will also provide the switch board phone number and requester extension so that the provider can navigate the switch board. To do.
[0193]
If the calling communicator 20 is from an extension off the unattended switchboard, the “acknowledgment” script will also play a “Please wait on line until you hear a tone” greeting. During the period preceding this tone, provider details are given to the requester, and the requester is given the opportunity to connect directly with the provider still on the line. If an intermediate connection is required, the requester connects to the provider and establishes a conversation. If an intermediate connection is not established, the requester can later contact the provider.
[0194]
In this embodiment, the system is configured such that the “acknowledge” script is re-executed with a predetermined keystroke.
[0195]
In this embodiment, the positive answer is either the answer option “accepted” or “maybe”. In other embodiments, and particularly for certain categories, the matching system can be configured to look for only “accepted” answers as positive answers. In such an embodiment, the “request playback” script also plays a “reject or accept only” greeting. In this case, all “maybe” and “reject” responses are negative responses.
[0196]
If there is no response to a call to the provider made by the OIVR module 25, the OIVR module 25 will be able to obtain a "number can be obtained" if the number maintained for the provider communicator 24 cannot be obtained: 1 ”,“ busy ”when the number held for the provider is busy, and“ calling ”when the telephone number held for the provider is ringing but there is no answer Is assigned to the calling document as a call state identifier, the call document is updated to include the associated call state identifier, and the updated call document is transmitted to the originating provider selection unit 33a, 33b, 33c.
[0197]
Each of the TM systems 1a, 1b provides a communication link to the first main communication network 3, as well as an ITM unit 5 (in this embodiment both the IIVR module 11 and the ITAM module 13 are separate), a file store 19, and an OTM. A telephone management (TM) communication network 29 is further provided that provides a communication link between the units 21 (in this embodiment, both the OIVR module 25 and the OTAM module 27 are separate). In one embodiment, communications with the ITM unit 5, file store 19 and OTM unit 21, and communications between the IIVR module 11 and the ITAM module 13 are encoded. Typically, either encrypted or authenticated communication, for example signed communication.
[0198]
In this embodiment where the ITM unit 5, file store 19 and OTM unit 21 are located at the same location, the TM communication network 29 is a local area network (LAN), eg, Ethernet.
[0199]
In another embodiment where the ITM unit 5, file store 19 and OTM unit 21 are located remotely, the TM communication network 29 is an established telephone network, preferably an ISDN network.
[0200]
The matching system further includes at least one provider selection unit 33, in this embodiment 3 for selecting the provider to be contacted by the OTM unit 21 of the TM system 1a, 1b during scheduling of request matching and contact with the provider. One provider selection unit 33a, 33b, 33c is provided. It should be appreciated that this matching system can include any number of provider selection units 33. This embodiment simply includes three provider selection units 33a, 33b, 33c for illustration.
[0201]
In this embodiment, the provider selection units 33a, 33b, 33c are arranged at the same position, but in other embodiments, some or all of the provider selection units 33a, 33b, 33c are arranged apart.
[0202]
In this embodiment, the provider selection units 33a, 33b, 33c are each configured to support all of the addressable classifications, but in other embodiments, many provider selections, especially tens or hundreds. If there are units 33a, 33b, 33c, provider selection units 33a, 33b, 33c may be configured to support only one or a subset of the addressable classifications.
[0203]
The matching system further comprises a second main communication network 34 providing a communication link to and between the provider selection units 33a, 33b, 33c.
[0204]
In this embodiment where the provider selection units 33a, 33b, 33c are located at the same location, the second main communication network 34 is a local area network (LAN), for example Ethernet.
[0205]
In another embodiment in which the provider selection units 33a, 33b, 33c are remotely located, the second main communication network 34 is a telephone network, preferably an integrated digital communication service network (ISDN).
[0206]
The matching system further includes a router 35 for routing the requested document and the calling document between the TM systems 1a and 1b and the provider selection units 33a, 33b and 33c.
[0207]
Each of the provider selection units 33a, 33b, and 33c includes information such as provider characteristics regarding each provider in each of the classifications supported by the respective provider selection units 33a, 33b, and 33c, provider list / building parameters for each classification, A classification information (CI) database 37 that contains matching criteria for classification and termination criteria for each classification; a second request information (RI) database 39 that contains information such as requester characteristics for each of the requesters; and a provider selection unit CI about the document scheduler 41 for scheduling documents to and from each of 33a, 33b, 33c and the classification to which each request is directed. From the contained provider database 37, and a provider list building unit 43 for constructing a sorted provider list of providers.
[0208]
The CI database 37 stores information on each provider in each classification, and each provider is referred to by a provider identifier. Information held for each provider includes provider name, provider address, provider contact number, provider characteristics, and system history information, such as the number of requests delivered, the number of positive responses (in this embodiment, “ As one of the “accepted” or “probably” responses, and in other embodiments as “accepted” responses), the number of negative responses (in this embodiment as “rejected” responses, and in other embodiments “rejected” or As "maybe" answers), including the number of "inappropriate" answers and the number of "illegal" answers. The CI database 37 in this embodiment is a spatial collection database, that is, a database that enables spatial operations.
[0209]
The provider list / building unit 43 includes a provider selection module 44. The module may include one or more candidates based on a predetermined listing mechanism for the classification to which the request is addressed and, if the table creation mechanism uses a position-based vector, based on the search center. It is configured to generate a provider list. This search center is usually the location of the requester, but can also be an alternate location specified by the requester. Alternatively, if the search is re-centered, it is the location of the first provider that acknowledged the request. As described in further detail below, the generation of a plurality of candidate provider lists defines a set of providers, eg, a set of local and national providers.
[0210]
In this embodiment, the provider selection module 44 generates one or more candidate provider lists using the following tabulation mechanism.
[0211]
[Table organization A-closest]
This tabulation mechanism generates a candidate provider list of candidate providers closest to the search center in terms of spatially related parameters, typically direct (between two points) distance, travel distance or travel time. In one embodiment, the candidate provider list may be truncated by number, i.e., to include a predetermined number of closest candidate providers in the search center. In another embodiment, the candidate provider list may be truncated by an upper bound on spatially related parameters, i.e. to include all providers within a predetermined size spatial area.
[0212]
[Table Organization B-Closest Group]
This tabulation mechanism generates a candidate provider list of candidate providers that represents the closest set of providers that meet the collective characteristics for the classification to which the request is addressed as a closest collection. In this embodiment, the ensemble feature is used to determine the nearest ensemble of a provider with at least a predetermined number of providers within a predetermined sized spatial area, typically within a direct (between two points) distance, travel distance or travel time. It is defined as a close pair.
[0213]
[Table organization mechanism C-maximum concentration group]
This tabulation mechanism generates a candidate provider list of candidate providers that represent the set of providers that satisfy the density feature for the classification to which the request is addressed as a group but not necessarily the nearest group. In this embodiment, the concentration feature is a provider comprising the highest number of providers within a first spatial area of a first predetermined size, typically within a direct (between two points) distance, travel distance or travel time. It is prescribed as a set. The first spatial zone is within a second spatial zone centered at the search center, having a second predetermined size of a larger size. This tabulation mechanism is effective in placing large towns and cities within a geographic area, and avoids providers leaving the main density that is likely to be more widely distributed. For this reason, it is expected that this tabulation mechanism will be commonly used as part of a series of searches.
[0214]
[Table organization D-segment]
The tabulation mechanism generates a candidate provider list of candidate providers from within a circle segment having a predetermined segment angle and radius. This radius is typically a first predetermined size that is a direct (two-point) distance, travel distance or travel time to the search center, or a second segment with a small radius segment containing a predetermined number of candidate providers. Either a small distance. The candidate provider list in this embodiment is the closest listed first in the list with respect to spatially related parameters, typically direct (two points) distance, travel distance or travel time from the search center. As ordered. If a reference is made again as a result of an unsuccessful matching operation, the subsequent segment in either clockwise or counterclockwise direction is utilized. This tabulation mechanism has been developed for use when changing but high concentration providers are present in the area of interest. In this case, the requester identifies the provider sharply within the general direction of travel extending from the search center. In this embodiment, the circle segments are randomly selected.
[0215]
[Table organization E-all]
This tabulation mechanism is based on a spatial area of a given size centered around the search center, and all the provider's Generate a candidate provider list.
[0216]
[Table organization mechanism F-threshold value]
This tabulation mechanism generates a candidate provider list of providers that satisfy the threshold characteristics for the classification to which the request is addressed. In this embodiment, the threshold feature defines a provider that satisfies a predetermined threshold criterion, eg, greater than or less than at least one threshold. Examples of threshold criteria include turnover, number of employees, quality assignment, and delivery speed.
[0217]
The provider list building unit 43 further generates a provider contact list by sorting candidate providers in the candidate provider list generated by the provider selection module 44 according to a predetermined alignment mechanism for the classification to which the request is addressed. A provider alignment module 45 for In one embodiment, the generated provider contact list is truncated.
[0218]
The provider alignment module 45 in this embodiment uses the following alignment mechanism.
[0219]
[Alignment mechanism A-None]
This alignment mechanism does not align the candidate provider list. The provider contact list has an order of candidate provider lists generated by the provider selection module 44.
[0220]
[Alignment mechanism B-Random]
The alignment mechanism generates a provider contact list by randomizing the candidate provider list generated by the provider selection module 44.
[0221]
[Alignment mechanism C-order]
This alignment mechanism provides the provider by aligning the candidate provider list generated by the provider selection module 44 according to the last contact with the provider to ensure that the providers are contacted in order according to a specific ratio. Generate a contact list. In this case, the last contacted provider is at the bottom of the list. In this embodiment, the log is maintained with respect to previous contacts with the provider.
[0222]
[Alignment mechanism D-closest]
This alignment mechanism aligns the candidate provider list generated by the provider selection module 44 with respect to spatially related parameters, typically direct (to two points) distance, travel distance or travel time candidates to the search center. To generate a provider contact list. In this case, for example, the closest one is posted first.
[0223]
[Alignment mechanism E-ranking]
This alignment mechanism sorts the candidate provider list generated by the provider selection module 44 according to special ranking parameters, for example in the order ranked by turnover, number of employees, quality rating, and delivery speed. To generate a provider contact list. This alignment mechanism is particularly suitable for searching providers when the position is not important. These providers tend to be national providers, and their location is only relevant as long as the provider includes the requester's location. A typical classification is insurance business, and contact with the provider in this case is by telephone. It should be appreciated that this alignment mechanism can generate a list that never contains certain providers and, for that reason, is usually used as one of a series of searches.
[0224]
In this embodiment, if the list building criteria for the selected classification requires more than one contact provider list, the list building unit 43 merges multiple provider contact lists into a single provider contact list. Is configured to generate Generation of a single provider contact list from multiple provider contact lists finds application when a set of providers, eg, local and national providers, is selected. A typical classification for which such provider contact lists are appropriate is that of a computer supplier. In this case, the requester wants a local provider, or perhaps a national provider.
[0225]
The provider contact list constructed by the list building unit 43 includes a plurality of status fields for each provider entry, with the restriction that one provider is included in only one field. In this way, the state of the provider can be maintained. Several states are grouped as meaning that the request has not yet been delivered, including “Available”, “Out of Hours”, “Busy” and “Calling” states. Final response states include “accepted”, “rejected”, “maybe”, “inappropriate” and “incorrect” states.
[0226]
When building the provider contact list, a database query is made to establish which providers are available. This list is examined and the providers are sorted into “available” and “out of hours” states. As each “out-of-hours” provider becomes available, the event is queued and moves the provider from the “out-of-hours” field to the “available” field. Similarly, as each “available” provider becomes unavailable, the event is queued and moves the provider from “available” to “out of time” state.
[0227]
In one embodiment, the provider selection units 33a, 33b, 33c can be configured to re-center the search center for the provider location that gave the first affirmative response. If re-centering is enabled and the provider has been identified as affirmative, the provider list building unit 43 is again referred to and another location that uses the identified provider's location as a search center. Generate provider contact list. Such re-centering is used to identify providers that are as close as possible to each other. This attempts to avoid the identification of two widely spaced providers, eg, two providers that are in the opposite direction from the search center and thus widely separated. Recentering is expected to find application in identifying a number of relatively closely located providers visited by requesters. For example, where it is desired to be able to compare things and services provided by a provider.
[0228]
When scheduling a call document for the OTM unit 21 of the TM system 1a, 1b, the document scheduler 41 determines how many providers are currently callable and whether the call is "accept only". It is comprised as what calculates. That number is used to determine that the “ongoing” list of providers to be contacted can accommodate another provider. If another provider is available, the first provider from the “Available” list is used. If the “Available” list is empty, the document scheduler 41 waits for a “busy”, “busy” or “out of hours” provider to become available. Another mediation method is used to move the provider from one list to another, which causes the document scheduler 41 to accept an "in progress" provider in a final response state, eg "accepted", "rejected" ”,“ Maybe ”, etc. This method is the same as that used to move the provider between “available” and “out of time” and vice versa. Use of the same method allows multiple checks to be made. For example, a “busy” provider may be requeued when the provider is “out of time”.
[0229]
The provider selection units 33a, 33b, 33c are configured to terminate the search operation if the match criteria are met or if the match criteria does not match one of the possible end criteria shown below. In this embodiment, for each classification, any termination criteria are enabled and disabled. If any of the termination criteria is possible, the provider selection units 33a, 33b, 33c terminate the search operation when the termination criteria are met. Then, the end report is delivered to each provider.
[0230]
In this embodiment, the termination criteria are as follows:
[0231]
[End event A-Number of rejections]
For this termination event, termination occurs when a predetermined percentage of providers on the provider contact list for each requester is contacted. The provider selection unit 33a, 33b, 33c will try to make as many of the selected providers as possible when retrying the provider if the telephone number for the selected provider is busy or is ringing without answering. Configured to contact. As will be appreciated, the telephone number for a provider is either permanently busy or ringing, and as such, the system cannot always contact all selected providers.
[0232]
[End event B-elapse of a predetermined period]
For this end event, the end occurs when a predetermined time limit has elapsed. In a preferred embodiment, a predetermined percentage of providers on the provider contact list for a request have not been contacted when a predetermined period has elapsed since the request was created by the requestor or within a predetermined period of time since the request was created by the requester The end occurs at the first of the times.
[0233]
[End Event C-Invalid Request]
For this termination event, termination occurs if a predetermined number of, in this embodiment, two providers report the request as invalid. The “illegal” answer is the provider's answer option.
[0234]
[End Event D-Improper Request]
For this termination event, termination occurs when a predetermined number of, in this embodiment, two providers report a request as inappropriate. The “inappropriate” answer is the provider's answer option.
[0235]
[End Event E-Empty List]
For this termination event, termination occurs when the contact provider list is empty.
[0236]
In a preferred embodiment, the number of “unintelligible” or “inappropriate” answers is set to a number greater than 1, for example 2 or 3. Thus, a single “incomprehensible” or “inappropriate” answer, such as given by a bad provider or as a result of a simple mistake on the provider side, is not sufficient to end the matching operation.
[0237]
If the system does not meet the matching criteria within a reasonable time, the requester is contacted and given a progress list. The system continues until either the matching criterion or the termination criterion is met. If the termination criteria are met for the request, the requester is contacted to report the termination of the search and the results achieved. In general, if the requester has not heard anything, the requester can be confident that the system has successfully matched the request according to the matching criteria for the classification. Progress or termination reports are returned to the switchboard requester, but the report board always has the requester's recorded name and extension at the beginning of the report, so the switchboard operator can pass the message to the requester. it can.
[0238]
In this embodiment, the system can also cause the start of the matching operation to be delayed. Often an event occurs when a person tries to make a request, but he is aware that most or all of the potential offers are currently closed. Even with these events, the system is still usable. The requester can make a request (knowing that the request is unlikely to be matched) at any time of the day, for example, 0200 hours. The selected provider currently active is contacted. This is to allow those providers the opportunity to respond to the request. The duration of activity is known for all providers. During normal business hours for many providers, the number of providers available is higher. In this case, the requester is given a termination report as usual, but the system is configured to relay the request again at some other point in time when more providers are active in the given classification. Has been. In this embodiment, the system is configured to allow this feature to be overridden by the application of a predetermined keystroke. As a default, an action to hang up is interpreted as requiring that the request be relayed at a time when it is more likely to obtain a match.
[0239]
The system in this embodiment is also configured such that the requester identifies an alternate location for the search center that is not associated with the calling party's CLI. In this embodiment, the IIRV module 11 allows this feature to be enabled with a predetermined keystroke. When enabled, the IIRV module 11 executes the “alternate location” script. This plays the “alternate location” greeting, enters the alternate search center phone number, and prompts the requester to perform another predetermined keystroke. The system then uses the alternate location phone number to determine the search center. The system only uses the alternate location phone number to build the provider contact list, not as the calling party number. This calling party number, usually CLI, is used as the telephone number to which the status or termination report is delivered.
[0240]
This feature defines the environment in which the requester wishes to identify providers in another geographic region. For example, if the requester is traveling to visit a friend on the weekend and wants to locate a French restaurant in the area he is visiting, the requester Make an "alternate location" keystroke, enter an alternate phone number, typically the phone number of the friend you are visiting, and continue with the "done" keystroke. Then leave a request, for example, “A nice French restaurant, a table for four, 19:00 on Saturday night, call me tonight”. If the contact mode is set to give the requester details, the provider giving the affirmative answer is given the requester's calling party number rather than the alternate location phone number.
[0241]
The system in this embodiment is also configured to allow the requester to stay on the line and follow the matching operation. This is typically the case when the requester believes that matching is being achieved quickly. In this embodiment, this feature is enabled by a predetermined keystroke at the completion of request recording and disabled by repeating the predetermined keystroke. This matching system reports each event in real time, for example, “Cut only, rejected”, “His hair, rejected”, “Cool cut, accepted”. In this mode, each provider that responds positively, either “accepted” or “probably” in this embodiment, is assigned a special keystroke, and the associated keystroke causes a call to the provider. Established.
[0242]
In this embodiment, for each requester, the configuration options include a contact mode setting that enables the requester to configure the system by default. In this case, either refrain from requester contact details from the provider (in this case, the report to the requester will be given the details of the identified provider that has been positively acknowledged to allow the requester to contact the provider. Requestor contact details are provided to the identified provider so that the accepting provider can contact the requestor directly upon accepting the request.
[0243]
In this embodiment, the system is configured such that the requester can override the default contact mode setting, thereby making a predetermined keystroke during a classified greeting. In this embodiment, if not specifically configured, the default answer mode setting is for providing requester details. If the default contact mode setting is set to give details, the application of the predetermined key acts to switch the contact mode setting from a setting that gives requester details to a setting that refrains from requester details. As a result, the contact mode greeting “requester details are withheld” is reproduced. This is followed by a normal recording request tone. If the default contact mode setting is set to refrain from details, the application of the predetermined key acts to switch the contact mode setting from a setting that refrains from requester details to a setting that gives requester details. As a result, the contact mode greeting “requester details are supplied” is reproduced. This is followed by a normal recording request tone.
[0244]
If the contact mode setting is set to refrain from requester details, the system identifying the provider for the request calls the requester with the calling party number, and the provider details, in this embodiment for each provider Provide a completion report that includes the contact name, either the provider name or provider contact, and the contact number. In this embodiment, each of the providers mentioned in the termination report is assigned an associated key on the keypad so that the requester can quickly dial a selected one in the provider. . If the requester does not receive a return call from the system but an answering machine is attached to the requester's calling party number, the call is accepted by the answering machine. In this case, an end report is recorded and the requester can hear the call back later. If the calling party number is ringing but no answering machine is attached to the requester's calling party number, the system will call back at a set interval until the call is established. .
[0245]
At registration, the configuration details include the business availability of the provider, ie, business hours for each of the 7 days a week. Within these business hours, the system is configured by default to assume that the provider wants to receive requests. In this embodiment, the system is configured so that the provider can remove itself from classification and therefore not receive any further requests. It should be noted here that if a provider removes itself from the classification, the provider will continue to use the list-building unit 43 of the provider selection unit 33a, 33b, 33c until it reintroduces itself to that classification. It does not appear in any list built. This feature allows businesses to suspend services for extended periods of time, such as holidays. Outside business hours, the system does not contact providers that are assumed not to receive requests. In this embodiment, the provider can temporarily change the assigned business hours by setting one of the “open” or “closed” states, but setting up a business in that way If it is a temporary function and the assigned business is not set before the next business time starts, the default time is applied to the business time.
[0246]
In this embodiment, the system also allows the provider to block requests from requesters that cannot receive service. A typical example is that the position of the requester is not the position supplied by the requester. Another typical example is when a provider only provides services for a special group of people, for example younger people, not older people, and requests from older people are not handled It is. This does not bias the search, but simply avoids inappropriate contact.
[0247]
In this embodiment, the system allows the provider to block requests from the requester when the requester contact details have been withheld. In such an environment, the provider can be concerned that competitors will secretly use this system to gather information.
[0248]
In this embodiment, these preferences are set by the classification manager using the classification management unit 49.
[0249]
The matching system further includes a classification management unit 49. This unit maintains the classification databases, ie, the CC database 15 and CL database 37, and the requester databases, ie, the first and second RI databases 17,39. In particular, the classification management unit 49 updates provider entries, includes new provider entries, changes list building parameters for all classifications, and includes new classifications. In this embodiment, the classification management unit 49 has a web interface and enables remote operation. In a preferred embodiment, the classification management unit 49 is operated by a plurality of classification managers. Each of the classification managers is assigned to one or more classifications and manages them.
[0250]
Finally, it will be understood that the invention has been described in its preferred embodiments, but can be modified in many different ways without departing from the scope of the invention as defined by the appended claims. It will be.
[0251]
For example, in the described embodiment, the system is configured to use a voice response created using a telephone, but other communicators 20, 24 such as PDAs, personal computers, set boxes, gaming devices And the use of game consoles, i.e. any device with communication capability, is anticipated. Also for receiving and delivering requests such as text encoding requests (such as SMS and e-mail), image requests (typically MMS and EMS including still images or videos), and fax requests Use the format. In practice, the request can be made in one format, for example as a voice request, and delivered in another format. The request can also be a multi-format request with, for example, a voice and text encoding request component or a text encoding and image request component.
[0252]
In general, providers are those who respond to their requests, but there are exceptions. One such provider is an observational provider that can only receive requests and cannot respond to the requests. Another such provider is a split provider. In this case, one request is received by one person, usually a decision maker who answers the request, and then transferred to another person who handles the request further, eg when dealing with a customer contract. . Another such provider is an aligned provider that serves to receive a request and redirect the request to another provider.
[0253]
As an example of an aligner provider, the provider can have a hierarchical structure. Thus, “car sales” can have the children “new car” and “used car”. These can have children of their own car type, such as Ford, Vauxhall, VW. The system can support this hierarchical structure, but devoted to the philosophy that humans are the best people to handle requests, the system supports subordinate connections of classification through human aligners (sorters) Just do it. The matching process is as follows. The claimant determines that he is looking for the new blue Ford Focus 1.8 Ghia. The requester dials the telephone number for the classification “car sales” and leaves the request. This request is passed to the provider selected within that classification. However, one provider may be a distributor that sells many types of cars. For this provider, the other departments have already been configured with the above mentioned children. In this case, the person who hears the request serves as an aligner who determines to which department the request should be presented. The system is configured to recognize that this provider is an aligner and therefore expects to receive a key code associated with one of the departments set up so far. Upon receiving this key code, the system presents the request to the newly identified provider, which is itself set up as an aligner provider. After repeating this procedure one or more times, the request is made to a provider that does not require further alignment.
[0254]
Furthermore, if the system is used as a private matching system, the setup for the private matching system is similar to the above. However, this matching system presents requests to providers that have an internal private matching system. In this situation, all key codes used to get the response are logged. This is because these codes allow the hierarchy to be navigated to report and provide contact details.
[Brief description of the drawings]
[0255]
FIG. 1 schematically illustrates a matching system according to a preferred embodiment of the present invention for matching a request to a user's provider as a requester during request processing.

Claims (116)

A matching system for matching a request to a user's provider as a requester at the time of processing the request, wherein each of the requesters creates a request and addresses at least one answer to it. Each of the providers has at least one communicator for addressing a request and a respective answer thereto, the system comprising:
At least one request receiving unit for receiving a request from the requester;
At least one request relay unit for causing each of said requests to be relayed to and selected by a selected provider;
At least one answer receiving unit for receiving an answer from the provider created by each provider based on each request;
Acknowledgments indicate that the provider can accept requests, for each request, supply information about each requestor to any provider given an affirmative response to each request, and selected A system comprising: at least one information supply unit for providing one or both of providing information to each requester regarding an answer to each request from a provider. The system of claim 1, wherein the system is a real-time matching system. The system according to claim 1, wherein the request is a free format request. The system according to claim 1, wherein the request includes a voice request. The system according to claim 1, wherein the communicator includes a mobile communicator such as a telephone, a PDA, a personal computer and a game device. 6. A system according to any preceding claim, wherein the communicator comprises a stationary communicator such as a telephone, fax machine, personal computer, set top box and game console. 7. A system as claimed in any preceding claim, wherein the communicator comprises a hybrid fixed / mobile communicator such as a telephone. The system according to claim 1, comprising at least one inbound communication unit, each having at least one request receiving unit. The system according to any of claims 1 to 8, comprising at least one outbound communication unit, each comprising at least one request relay unit, at least one answer receiving unit, and at least one information supply unit. 8. The system according to claim 1, comprising at least one communication unit, each having at least one request receiving unit, at least one request relay unit, at least one answer receiving unit, and at least one information supply unit. The system described in Crab. 11. A system according to any preceding claim, wherein the at least one request relay unit is configured to relay a request directly to a selected provider communicator. The system according to any one of claims 1 to 11, wherein the at least one request relay unit is configured such that a request is relayed without making an inquiry and setting contents. 13. The at least one request receiving unit includes a plurality of receivers for receiving requests, each request having a classification contact address associated with a predeterminable classification. system. The system according to claim 13, wherein the classification contact address is a dial number. 15. A system according to any preceding claim, comprising at least one provider selection unit for selecting a provider to address the request. The at least one provider selection unit is a provider for requests based at least in part on a geographical location assigned to each request and one or both of a geographical location or a geographical area assigned to the provider. The system of claim 15, wherein the system is configured to select The system of claim 16, wherein the geographic location assigned to each respective request is a current geographic location of each requester. The system of claim 17, wherein the current geographic location is a communicator contact address of a communicator of each requester, and the communicator contact address has an assigned location. The system of claim 18, wherein the communicator contact address is a dial number. The system of claim 16, wherein the geographic location assigned to each respective request is an alternate geographic location assigned by a respective requester. 21. The system of claim 20, wherein the alternative geographic location is determined from a communicator communicator contact address, the communicator contact address having an assigned location. The system of claim 21, wherein the communicator contact address is a dial number. 23. A system according to any of claims 15 to 22, wherein the mobile communicator's geographic location is determined from one of cell identification, triangulation, radio location or satellite location such as GPS. 24. A system according to any of claims 15 to 23, wherein the geographic location of the fixed communicator is determined from each assigned location. 25. The at least one provider selection unit is configured to select a provider for a request within a spatial geographic area that is predeterminable for a geographical location assigned to each request. The system according to any of the above. The predeterminable spatial geographic area is assigned to each request, whether it is a geographical radius for the geographical location assigned to each request, or a distance of movement for the geographical location assigned to each request. 26. The system of claim 25, wherein the system is one of the times of travel relative to the geographic location. The at least one provider selection unit is based at least in part on at least one requestor feature for each requester, for example, as an assigned feature for each requestor or as a feature input when creating information by each requester, 27. A system according to any of claims 15 to 26, wherein the system is configured to select a provider for a request based on geographically relevant socio-economic information. The at least one provider selection unit has a predeterminable profile, at least in part based on at least one provider feature for the provider, eg as an assigned feature for each provider, or contact details 28. A system according to any of claims 15 to 27, wherein the system is configured to select a provider for the request based on requesting the requestor to provide the request. 29. A system according to any of claims 15 to 28, wherein the at least one provider selection unit is configured to select a provider for a request based at least in part on a current time. The at least one provider selection unit selects a provider for the request based at least in part on at least one classification feature, eg, based on a selection mechanism for selecting a provider, as an assigned feature for each classification. 30. A system according to any one of claims 15 to 29, which is configured for selection. 31. A method as claimed in any preceding claim, wherein the at least one request relay unit is configured to relay a request to a predeterminable number of selected providers thereby addressed. system. The at least one request relay unit is configured to multicast a request to a selected provider, wherein the request is relayed to and addressed by a plurality of providers. The system according to any one of 1 to 30. The at least one information supply unit is configured to supply, to each requester, information on a provider who has been given an affirmative response to the request for each request. System. A matching system for matching a request to a user's provider as a requester when processing the request,
With multiple requestor communicators,
With multiple provider communicators,
Each requestor communicator is used by the requester when creating a request and addressing its respective answer to it, at least some of the answers being sent from the selected provider to the respective requestor. Contains information about the answer,
Each provider communicator is to be used by the provider when addressing requests and their respective answers, and the requests are relayed to be addressed to their respective selected providers And at least some of the requests contain information about the requestor of each request, and a positive response is given for each request, which indicates that the provider can accept the request. System characterized by. The system of claim 34, wherein the system is a real-time matching system. 36. A system according to claim 34 or 35, wherein the request is a free format request. 37. A system according to any of claims 34 to 36, wherein the request comprises a voice request. 38. A system according to any of claims 34 to 37, wherein the communicator comprises a mobile communicator such as a telephone, PDA, personal computer and gaming device. 39. A system according to any of claims 34 to 38, wherein the communicator comprises a stationary communicator such as a telephone, fax machine, personal computer, set top box and game console. 40. A system according to any of claims 34 to 39, wherein the communicator comprises a hybrid fixed / mobile communicator such as a telephone. 41. A system according to any of claims 34-40, wherein the request is relayed directly to each selected provider. The system according to any one of claims 34 to 41, wherein the request is relayed without making an inquiry and setting contents. 43. A system according to any of claims 34 to 42, further comprising a communication unit including a plurality of receivers for receiving requests, each request having a classification contact address associated with a predeterminable classification. 44. The system of claim 43, wherein the classification contact address is a dial number. 45. A provider for a request is selected based at least in part on the geographic location assigned to each request and one or both of the geographic location and / or geographic area assigned to the provider. The system according to any of the above. 46. The system of claim 45, wherein the geographic location assigned to each request is the current geographic location of each requester. 47. The system of claim 46, wherein the current geographic location is a communicator contact address of a respective requester communicator, and the communicator contact address has an assigned location. 48. The system of claim 47, wherein the communicator contact address is a dial number. 46. The system of claim 45, wherein the geographic location assigned to each request is an alternate geographic location assigned by a respective requester. 50. The system of claim 49, wherein the alternate geographic location is determined from a communicator's communicator contact address, and the communicator contact address has an assigned location. 51. The system of claim 50, wherein the communicator contact address is a dial number. 52. A system according to any of claims 34 to 51, wherein a provider is selected within a spatial geographical area that is predeterminable for the geographical location assigned to each request. Geographically related socio-economic information, at least in part, based on at least one requestor feature for each requester, eg, assigned features for each requestor or feature input when creating information by each requester 53. A system according to any of claims 34 to 52, wherein a provider for a request is selected based on At least in part requires the requestor to have a predeterminable profile or provide contact details based on at least one provider feature for the provider, eg, as an assigned feature for each provider 54. A system according to any of claims 34 to 53, wherein a provider for the request is selected on the basis. 55. A system according to any of claims 34 to 54, wherein a provider for the request is selected based at least in part on the current time. 56. A provider for a request is selected based at least in part on at least one classification feature, e.g., based on a selection mechanism for selecting a provider as an assigned feature for each classification. A system according to any of the above. A matching system for matching a request to a provider of a user as a requester at the time of processing the request, each requester creating at least one request and addressing an answer thereto. And each of the providers has at least one communicator for addressing a request, the system comprising:
At least one request receiving unit for receiving a request from the requester;
At least one request relay unit for causing each of said requests to be relayed to and selected by a selected provider;
At least one answer receiving unit for receiving an answer from the provider created by each provider based on each request;
A system comprising: A matching system for matching a request to a user's provider as a requester when processing the request,
With multiple requestor communicators,
Multiple provider communicators,
And at least one communication unit capable of communicating with the requester communicator and the provider communicator,
Each requestor communicator is used by the requester when creating a request and addressing its respective answer to it,
Each provider communicator is what is used by the provider when addressing requests and their respective answers,
The at least one communication unit includes at least one provider selection unit for selecting a provider and addressing each request made by the requestor;
The system is configured such that for each request, the request is relayed to a selected provider thereby addressed. 59. The system according to claim 58, wherein the system is further configured for requests, wherein each respective requester is provided with information regarding a response to the request from a selected provider. 60. The system of claim 58 or 59, wherein the system is a real time matching system. The system according to any one of claims 58 to 60, wherein the request is a free format request. 62. A system according to any of claims 58 to 61, wherein the request comprises a voice request. 63. A system according to any of claims 58 to 62, wherein the communicator comprises a mobile communicator such as a telephone, PDA, personal computer and gaming device. 64. A system as claimed in any of claims 58 to 63, wherein the communicator comprises a stationary communicator such as a telephone, fax machine, personal computer, set top box and game console. 65. A system according to any of claims 58 to 64, wherein the communicator comprises a hybrid fixed / mobile communicator such as a telephone. 66. A system according to any of claims 58 to 65, wherein the system is configured to relay requests directly to the provider communicator of a selected provider. The system according to any one of claims 58 to 66, wherein the system is configured such that the request is relayed without making an inquiry and setting contents. 68. A system according to any of claims 58 to 67, wherein the at least one communication unit includes a plurality of receivers for receiving requests, each request having a classification contact address associated with a predeterminable classification. . 69. The system of claim 68, wherein the classification contact address is a dial number. The at least one provider selection unit is a provider for requests based at least in part on a geographical location assigned to each request and one or both of a geographical location or a geographical area assigned to the provider. 70. A system according to any of claims 58 to 69, wherein the system is configured to select. The system of claim 70, wherein the geographic location assigned to each respective request is a current geographic location of each requester. 72. The system of claim 71, wherein the current geographic location is a communicator contact address of a respective requester communicator, and the communicator contact address has an assigned location. The system of claim 72, wherein the communicator contact address is a dial number. The system of claim 70, wherein the geographic location assigned to each respective request is an alternate geographic location assigned by a respective requester. 75. The system of claim 74, wherein the alternate geographic location is determined from a communicator's communicator contact address, and the communicator contact address has an assigned location. The system of claim 75, wherein the communicator contact address is a dial number. 77. Any of claims 58-76, wherein the at least one provider selection unit is configured to select a provider within a spatial geographic area that is predeterminable for a geographical location assigned to each request. The system described in Crab. The predeterminable spatial geographic area is assigned to each request, whether it is a geographical radius for the geographical location assigned to each request, or a distance of movement for the geographical location assigned to each request. 78. The system of claim 77, wherein the system is one of the times of travel relative to the geographic location. The at least one provider selection unit is based at least in part on at least one requestor feature for each requester, for example, as an assigned feature for each requestor or as a feature input when creating information by each requester, 79. A system according to any of claims 58 to 78, wherein the system is configured to select a provider for a request based on geographically relevant socio-economic information. The at least one provider selection unit has a predeterminable profile, at least in part based on at least one provider feature for the provider, eg as an assigned feature for each provider, or contact details 80. A system according to any of claims 58 to 79, wherein the system is configured to select a provider for the request based on requesting the requestor to provide the request. 81. A system according to any of claims 58 to 80, wherein the at least one provider selection unit is configured to select a provider for a request based at least in part on a current time. The at least one provider selection unit selects a provider for the request based at least in part on at least one classification feature, eg, based on a selection mechanism for selecting a provider, as an assigned feature for each classification. 82. A system according to any of claims 58 to 81, wherein the system is configured for selection. 83. Any of claims 58-82, wherein the system is configured to relay a request to the provider communicator of a predeterminable number of selected providers as addressed thereby. The system described in. The system is configured to multicast a request to the provider communicator of each selected provider, and the request is relayed to multiple providers thereby being addressed. 84. A system according to any of claims 58 to 83. A method for matching a request to a user's provider as a requester at the time of processing the request, each requester having at least one communicator for creating a request and addressing an answer thereto. And each of the providers has at least one communicator for addressing requests and respective answers thereto, the method comprising:
Receiving a request from the requester;
For each request, allowing said request to be relayed to and addressed by a selected provider;
Receiving an answer from the provider created by each provider based on each request;
Acknowledgments indicate that the provider can accept requests, for each request, supply information about each requestor to any provider given an affirmative response to each request, and selected Providing one or both of providing information to each requester regarding an answer to each request from a provider. 86. The method of claim 85, wherein the method is a real time matching method. 87. A method according to claim 85 or 86, wherein the request is a free format request. 88. A method according to any of claims 85 to 87, wherein the request comprises a voice request. 88. A method according to any of claims 85 to 87, wherein the communicator comprises a mobile communicator such as a telephone, PDA, personal computer and gaming device. 90. A method according to any of claims 85 to 89, wherein the communicator comprises a stationary communicator such as a telephone, fax machine, personal computer, set top box and game console. 91. A method according to any of claims 85 to 90, wherein the communicator comprises a hybrid fixed / mobile communicator such as a telephone. The steps for allowing a request to be relayed to and addressed by a selected provider are as follows:
92. A method according to any of claims 85 to 91, comprising relaying a request directly to the communicator of a selected provider. 93. A method according to any of claims 85 to 92, wherein the request is relayed without making an inquiry and setting the content. The step of receiving the request from the requester is:
94. A method according to any of claims 85-93, comprising receiving requests from requesters at a plurality of receivers, each of said requests having a classification contact address associated with a predeterminable classification. 95. The method of claim 94, wherein the classification contact address is a dial number. 96. A method as claimed in any of claims 85 to 95, further comprising selecting a respective provider addressing the request. The step of selecting each provider addressing the request is:
Selecting a respective provider addressing the request based at least in part on the geographic location assigned to each request and one or both of the geographic location and / or geographic area assigned to the provider; 96. A method according to any of claims 85 to 95 comprising. 98. The method of claim 97, wherein the geographic location assigned to each respective request is the current geographic location of each requester. 99. The method of claim 98, wherein the current geographic location is a communicator contact address of a respective requester communicator, and the communicator contact address has an assigned location. The method of claim 99, wherein the communicator contact address is a dial number. 98. The method of claim 97, wherein the geographic location assigned to each respective request is an alternate geographic location assigned by a respective requester. 102. The method of claim 101, wherein the alternative geographic location is determined from a communicator's communicator contact address, the communicator contact address having an assigned location. 103. The method of claim 102, wherein the communicator contact address is a dial number. 104. A method according to any of claims 96 to 103, wherein the geographical location of the mobile communicator is determined from one of a cell identification method, a triangulation method, a radio location method or a satellite location method such as GPS. 105. A method according to any of claims 96 to 104, wherein the geographic location of the fixed communicator is determined from the assigned location. The step of selecting each provider addressing the request is:
106. A method according to any of claims 96-105, comprising the step of selecting each provider addressing the request within a pre-determined spatial geographic area for the geographical location assigned to each request. The predeterminable spatial geographic area is assigned to each request, whether it is a geographical radius for the geographical location assigned to each request, or a distance of movement for the geographical location assigned to each request. 107. The method of claim 106, wherein the time is one of the times of travel relative to the geographic location. The step of selecting each provider addressing the request is:
Geographically relevant socio-economic information, at least in part, based on at least one requestor feature for each requester, eg, assigned features for each requestor or feature input when creating information by each requester 108. A method as claimed in any of claims 96 to 107, comprising selecting a respective provider addressing the request based on. The step of selecting each provider addressing the request is:
At least in part requires the requestor to have a predeterminable profile or provide contact details based on at least one provider feature for the provider, eg, as an assigned feature for each provider 109. A method according to any of claims 96-108, comprising, based on said, selecting a respective provider that addresses the request. The step of selecting each provider addressing the request is:
110. A method according to any of claims 96 to 109, comprising selecting a respective provider addressing the request based at least in part on the current time. The step of selecting each provider addressing the request is:
Selecting each provider addressing the request based at least in part on at least one classification feature, eg, based on a selection mechanism for selecting a provider, as an assigned feature for each classification. 111. A method according to any of claims 96-110. The steps for allowing a request to be relayed to and addressed by a selected provider are as follows:
112. A method as claimed in any of claims 85 to 111, comprising relaying the request to a predeterminable number of selected providers to be addressed thereby. The steps for allowing a request to be relayed to and addressed by a selected provider are as follows:
113. The method of any of claims 85-112, comprising multicasting a request to a selected provider, wherein the request is relayed to a plurality of providers thereby addressed. The step of providing information is
114. The method according to any of claims 85-113, comprising providing, for each request, information about a provider who is given an affirmative response to the request to a respective requester. A method for matching a request to a user's provider as a requester at the time of processing the request, each requester having at least one communicator for creating a request and addressing an answer thereto. And each of the providers has at least one communicator for addressing a request, the method comprising:
Receiving a request from the requester;
For each request, allowing said request to be relayed to and addressed by a selected provider;
Receiving a response from the provider created by each provider based on each request. A method for matching a request to a user provider as a requester when processing the request,
Receiving a signal having a request from a requester;
For each request, sending a signal having the request as received to the selected provider;
Receiving a signal generated by each provider based on each request and having an answer from the selected provider;
Acknowledgments indicate that the provider can accept requests, for each request, a signal with information about each requestor for any provider given an affirmative response to each request, and each Transmitting one or both signals for a requester having information regarding an answer to each request from a selected provider.