US20040254929A1 - Request matching system and method - Google Patents

Request matching system and method Download PDF

Info

Publication number
US20040254929A1
US20040254929A1 US10493229 US49322904A US2004254929A1 US 20040254929 A1 US20040254929 A1 US 20040254929A1 US 10493229 US10493229 US 10493229 US 49322904 A US49322904 A US 49322904A US 2004254929 A1 US2004254929 A1 US 2004254929A1
Authority
US
Grant status
Application
Patent type
Prior art keywords
request
providers
respective
requests
provider
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Abandoned
Application number
US10493229
Inventor
Stephen Isaac
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
SITRA Ltd
Original Assignee
SITRA Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATIONS NETWORKS
    • H04W4/00Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/02Services making use of location information
    • GPHYSICS
    • G01MEASURING; TESTING
    • G01CMEASURING DISTANCES, LEVELS OR BEARINGS; SURVEYING; NAVIGATION; GYROSCOPIC INSTRUMENTS; PHOTOGRAMMETRY OR VIDEOGRAMMETRY
    • G01C21/00Navigation; Navigational instruments not provided for in preceding groups
    • GPHYSICS
    • G07CHECKING-DEVICES
    • G07BTICKET-ISSUING APPARATUS; FARE-REGISTERING APPARATUS; FRANKING APPARATUS
    • G07B15/00Arrangements or apparatus for collecting fares, tolls or entrance fees at one or more control points
    • GPHYSICS
    • G08SIGNALLING
    • G08GTRAFFIC CONTROL SYSTEMS
    • G08G1/00Traffic control systems for road vehicles
    • G08G1/20Monitoring the location of vehicles belonging to a group, e.g. fleet of vehicles, countable or determined number of vehicles
    • G08G1/202Dispatching vehicles on the basis of a location, e.g. taxi dispatching
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network-specific arrangements or communication protocols supporting networked applications
    • H04L67/16Service discovery or service management, e.g. service location protocol [SLP] or Web services
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network-specific arrangements or communication protocols supporting networked applications
    • H04L67/18Network-specific arrangements or communication protocols supporting networked applications in which the network application is adapted for the location of the user terminal
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00Application independent communication protocol aspects or techniques in packet data networks
    • H04L69/30Definitions, standards or architectural aspects of layered protocol stacks
    • H04L69/32High level architectural aspects of 7-layer open systems interconnection [OSI] type protocol stacks
    • H04L69/322Aspects of intra-layer communication protocols among peer entities or protocol data unit [PDU] definitions
    • H04L69/329Aspects of intra-layer communication protocols among peer entities or protocol data unit [PDU] definitions in the application layer, i.e. layer seven

Abstract

A real-time request matching system for and method of matching free-format requests of users, as requestors, to providers in servicing the requests, each of the requesters having at least one communicator for making requests and addressing replies thereto and each of the providers having at least one communicator for addressing requests and respective replies thereto, the method comprising the steps of: receiving requests from requestors; for each request, providing for the request to be relayed to selected providers as addressed thereby; receiving replies from selected providers, the replies received being made by the respective providers based on the respective requests; and one or both of supplying, for each request, information regarding the respective requestor to any providers having provided a positive reply to the respective request, with a positive reply indicating that a provider is able to meet a request, and information regarding replies from selected providers to the respective request to the respective requestor.

Description

  • The present invention relates to a request matching system for and a method of matching requests of users, as requestors, to providers in servicing the requests. [0001]
  • The present invention finds application in many fields, but particularly in classification structures where a user, as a requestor, wants to make a request of a community of interest, that is, a plurality of providers who are commonly classified. [0002]
  • It is envisaged that the present invention will find particular application in relation to trade classifications, where providers are grouped according to the goods or services provided. [0003]
  • Such trade classifications are currently embodied in a local trade directory, such as the Yellow Pages® or Thomson Directory® In the UK, and, when seeking goods or services, a person would use the local directory to locate a provider for the goods or services. [0004]
  • In using such a directory, a person would first determine the classification most likely to supply the goods or services, review the corresponding section in the directory, select one or more providers, and then telephone those providers. When telephoning the providers, the same request, for example, “Can you provide goods/service X, for cost Y and before date Z?”, would have to made repeatedly to each provider. Often, especially if the request is specific, for example, “Do you have car part X in stock?”, the person would have to telephone many of the selected providers before finding a provider that can satisfy the request. This is particularly the case where more than one provider has to be identified, for example, such as to allow for a comparison of costs, delivery times, etc. [0005]
  • Such a process is both time consuming, in having first to identify possible providers and subsequently establish conversation with many providers until one or more providers are identified who can satisfy the request, and also relatively costly, in incurring the telephone costs associated with telephoning each of the many providers. [0006]
  • Although it is envisaged that the present invention will find particular application in relation to trade classifications, the present invention also has application in relation to many other classification structures. [0007]
  • One such other classification structure is broadcast classifications, where a request is broadcast to a plurality of providers, which enables replies to be obtained from all of the providers, and provides for the logging of one or both of positive and negative replies from providers, and also those providers who do not reply. It is envisaged that such classifications could find application in obtaining information in response to a query, for example, in building marketing lists or polling. [0008]
  • Another such other classification structure is community classifications, where persons having a common interest are commonly classified such as to allow a request to be made by a requester, who may be a provider in the community classification, of ones or all of the other persons in the community classification, as providers. One example of a community classification is a local help group whose members offer assistance on an ad hoc basis, where requests for assistance can be made of the members. [0009]
  • A further such other classification structure is tasking classifications, where a request is made to a plurality of providers requiring performance of a task. It is envisaged that such classifications will find particular application in the corporate environment, where requests can be made of particular departments, for example, the purchasing or marketing departments. [0010]
  • A yet further such other classification structure is promotion classifications, where a particular promotion is run, typically for a short period of time, and supported by a plurality of providers. One example of a promotion classification is holiday breaks, for example, fixed-price weekend breaks, where providers wishing to join the promotion opt into the classification. In a preferred embodiment the providers would have the ability to opt into and out of the classification subject to the availability of the goods or services provided by the respective providers. [0011]
  • It is an aim of the present invention to provide a matching system and method which provides for the matching of requests of users, as requesters, to providers without a requestor having to identify possible providers and contact those providers to determine whether a request can be met. [0012]
  • In one aspect the present invention provides a matching system for matching requests of users, as requestors, to providers in servicing the requests, each of the requesters having at least one communicator for making requests and addressing respective replies thereto and each of the providers having at least one communicator for addressing requests and respective replies thereto, the system comprising: at least one request receiving unit for receiving requests from requestors; at least one request relaying unit for providing for each of the requests to be relayed to selected providers as addressed thereby; at least one reply receiving unit for receiving replies from providers, the replies received being made by the respective providers, as human decision-makers, based on the respective requests; and at least one information supplying unit for one or both of supplying, for each request, information regarding the respective requestor to any providers having provided a positive reply to the respective request, with a positive reply indicating that a provider is able meet a request, and Information regarding replies from selected providers to the respective request to the respective requestor. [0013]
  • Preferably, the system is a real-time matching system. [0014]
  • Preferably, the requests are free-format requests. [0015]
  • Preferably, the requests include voice requests. [0016]
  • Preferably, the communicators include mobile communicators, such as telephones, PDAs, personal computers and games devices. [0017]
  • Preferably, the communicators include fixed communicators, such as telephones, fax machines, personal computers, set-top boxes and games consoles. [0018]
  • Preferably, the communicators include combination fixed/mobile communicators, such as telephones. [0019]
  • In one embodiment the system comprises: at least one inbound communications unit, each comprising at least one request receiving unit. [0020]
  • In one embodiment the system comprises: at least one outbound communications unit, each comprising at least one request relaying unit, at least one reply receiving unit and at least one information supplying unit. [0021]
  • In another embodiment the system comprises: at least one communications unit, each comprising at least one request receiving unit, at least one request relaying unit, at least one reply receiving unit and at least one information supplying unit. [0022]
  • In one embodiment the at least one request relaying unit is configured to relay a request directly to the communicators of selected providers. [0023]
  • Preferably, the at least one request relaying unit is configured to provide for a request to be relayed without any interrogation thereof to establish content. [0024]
  • 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. [0025]
  • More preferably, the classification contact addresses are dialling numbers. [0026]
  • In one embodiment the system further comprises: at least one provider selection unit for selecting providers to address a request. [0027]
  • Preferably, the at least one provider selection unit is configured to select providers for a request based at least in part on a geographic location assigned to the respective request and one or both of geographic locations or geographic zones assigned to the providers. [0028]
  • In one embodiment the geographic location assigned to the respective request is a current geographic location of the respective requestor. [0029]
  • Preferably, the current geographic location is determined from a communicator contact address of the communicator of the respective requestor, where the communicator contact address has an assigned location. [0030]
  • More preferably, the communicator contact address is a dialling number. [0031]
  • In one embodiment the geographic location assigned to the respective request is an alternate geographic location as assigned by the respective requestor. [0032]
  • Preferably, the alternate geographic location is determined from a communicator contact address of a communicator, where the communicator contact address has an assigned location. [0033]
  • More preferably, the communicator contact address is a dialling number. [0034]
  • Preferably, geographic location of mobile communicators is determined from one of cell Identification, triangulation, radio positioning or satellite positioning, such as GPS. [0035]
  • Preferably, geographic location of fixed communicators is determined from respective assigned locations. [0036]
  • Preferably, the at least one provider selection unit is configured to select providers for a request within a predeterminable spatial geographic zone relative to the geographic location assigned to the respective request. [0037]
  • More preferably, the predeterminable spatial geographic zone is one of a geographic radius relative to the geographic location assigned to the respective request, a distance of travel relative to the geographic location assigned to the respective request, or a time of travel relative to the geographic location assigned to the respective request. [0038]
  • Preferably, the at least one provider selection unit is configured to select providers for a request based at least in part on at least one requestor characteristic for the respective requester, such as geographically-related and socio-economic information, as an assigned characteristic for the respective requestor or a characteristic input by the respective requester in making the request. [0039]
  • Preferably, the at least one provider selection unit is configured to select providers for a request based at least in part on at least one provider characteristic for the providers, such as requiring requestors to have a predeterminable profile or to provide contact details, as an assigned characteristic for the respective providers. [0040]
  • Preferably, the at least one provider selection unit is configured to select providers for a request based at least in part on current time. [0041]
  • Preferably, the at least one provider selection unit is configured to select providers for a request based at least in part on at least one classification characteristic, such as a selection mechanism for selecting providers, as an assigned characteristic for the respective classification. [0042]
  • Preferably, the at least one request relaying unit is configured to relay a request to a predeterminable number of selected providers as addressed thereby. [0043]
  • Preferably, the at least one request relaying unit is configured to multicast a request to selected providers where the request is to be relayed to a plurality of providers as addressed thereby. [0044]
  • Preferably, the at least one information supplying unit is configured, for a request, to supply information regarding providers having provided a positive reply to the respective request to the respective requestor. [0045]
  • In another aspect the present invention provides a matching system for matching requests of users, as requesters, to providers in servicing the requests, the system comprising: a plurality of requester communicators, each being for use by requesters in making requests and addressing replies thereto, at least ones of the replies including information regarding replies from selected providers, as human decision-makers, to respective requests; and a plurality of provider communicators, each being for use by providers in addressing requests and replies thereto, the requests being relayed to respective selected providers as addressed and at least ones of the replies including information regarding the requestor of a respective request where having provided a positive reply to the respective request, with a positive reply indicating that a provider is able to meet a request. [0046]
  • Preferably, the system is a real-time matching system. [0047]
  • Preferably, the requests are free-format requests. [0048]
  • Preferably, the requests include voice requests. [0049]
  • Preferably, the communicators include mobile communicators, such as telephones, PDAs, personal computers and games devices. [0050]
  • Preferably, the communicators include fixed communicators, such as telephones, fax machines, personal computers, set-top boxes and games consoles. [0051]
  • Preferably, the communicators include combination fixed/mobile communicators, such as telephones. [0052]
  • In one embodiment a request is relayed directly to respective selected providers. [0053]
  • Preferably, a request is relayed without any interrogation thereof to establish content. [0054]
  • Preferably, the system further comprises: a communications unit including a plurality of receivers for receiving requests, each request having a classification contact address associated with a predeterminable classification. [0055]
  • More preferably, the classification contact addresses are dialling numbers. [0056]
  • Preferably, providers are selected for a request based at least in part on a geographic location assigned to the respective request and one or both of geographic locations or geographic zones assigned to the providers. [0057]
  • In one embodiment the geographic location assigned to the respective request is a current geographic location of the respective requestor. [0058]
  • Preferably, the current geographic location is determined from a communicator contact address of the communicator of the respective requestor, where the communicator contact address has an assigned location. [0059]
  • More preferably, the communicator contact address is a dialling number. [0060]
  • In one embodiment the geographic location assigned to the respective request is an alternate geographic location as assigned by the respective requestor. [0061]
  • Preferably, the alternate geographic location is determined from a communicator contact address of a communicator, where the communicator contact address has an assigned location. [0062]
  • More preferably, the communicator contact address is a dialling number. [0063]
  • Preferably, providers are selected within a predeterminable spatial geographic zone relative to the geographic location assigned to the respective request. [0064]
  • Preferably, providers are selected for a request based at least in part on at least one requestor characteristic for the respective requestor, such as geographically-related and socio-economic information, as an assigned characteristic for the respective requestor or a characteristic input by the respective requestor in making the request. [0065]
  • Preferably, providers are selected for a request based at least in part on at least one provider characteristic for the providers, such as requiring requesters to have a predeterminable profile or to provide contact details, as an assigned characteristic for the respective providers. [0066]
  • Preferably, providers are selected for a request based at least in part on current time. [0067]
  • Preferably, providers are selected for a request based at least in part on at least one classification characteristic, such as a selection mechanism for selecting providers, as an assigned characteristic for the respective classification. [0068]
  • In a further aspect the present Invention provides a matching system for matching requests of users, as requesters, to providers in servicing the requests, each of the requestors having at least one communicator for making requests and addressing replies thereto and each of the providers having at least one communicator for addressing requests, the system comprising: at least one request receiving unit for receiving requests from requestors; at least one request relaying unit for providing for each of the requests to be relayed to selected providers as addressed thereby; and at least one reply receiving unit for receiving replies from providers, the replies received being made by the respective providers, as human decision-makers, based on the respective requests. [0069]
  • In a yet further aspect the present invention provides a matching system for matching requests of users, as requesters, to providers in servicing the requests, the system comprising: a plurality of requestor communicators, each being for use by requestors in making requests and addressing respective replies thereto; a plurality of provider communicators, each being for use by providers in addressing requests and respective replies thereto; and at least one communications unit communicatable with the requestor communicators and the provider communicators, and including at least one provider selection unit for selecting providers to address a request made by a requester; wherein, for each request, the system is configured such that the request is provided to be relayed to selected providers, as human decision-makers, as addressed thereby. [0070]
  • Preferably, the system is further configured such that, for a request, the respective requestor is supplied with Information regarding replies from selected providers to the respective request. [0071]
  • Preferably, the system is a real-time matching system. [0072]
  • Preferably, the requests are free-format requests. [0073]
  • Preferably, the requests include voice requests. [0074]
  • Preferably, the communicators include mobile communicators, such as telephones, PDAs, personal computers and games devices. [0075]
  • Preferably, the communicators include fixed communicators, such as telephones, fax machines, personal computers, set-top boxes and games consoles. [0076]
  • Preferably, the communicators include combination fixed/mobile communicators, such as telephones. [0077]
  • In one embodiment the system is configured such that a request is relayed directly to the provider communicators of selected providers. [0078]
  • Preferably, the system is configured to provide that a request is relayed without any interrogation thereof to establish content. [0079]
  • Preferably, the at least one communications unit includes a plurality of receivers for receiving requests, each request having a classification contact address associated with a predeterminable classification. [0080]
  • More preferably, the classification contact addresses are dialling numbers. [0081]
  • Preferably, the at least one provider selection unit is configured to select providers for a request based at least in part on a geographic location assigned to the respective request and one or both of geographic locations or geographic zones assigned to the providers. [0082]
  • In one embodiment the geographic location assigned to the respective request is a current geographic location of the respective requestor. [0083]
  • Preferably, the current geographic location is determined from a communicator contact address of the communicator of the respective requestor, where the communicator contact address has an assigned location. [0084]
  • More preferably, the communicator contact address is a dialling number. [0085]
  • In one embodiment the geographic location assigned to the respective request is an alternate geographic location as assigned by the respective requester. [0086]
  • Preferably, the alternate geographic location is determined from a communicator contact address of a communicator, where the communicator contact address has an assigned location. [0087]
  • More preferably, the communicator contact address is a dialling number. [0088]
  • Preferably, the at least one provider selection unit is configured to select providers within a predeterminable spatial geographic zone relative to the geographic location assigned to the respective request. [0089]
  • More preferably, the predeterminable spatial geographic zone is one of a geographic radius relative to the geographic location assigned to the respective request, a distance of travel relative to the geographic location assigned to the respective request, or a time of travel relative to the geographic location assigned to the respective request. [0090]
  • Preferably, the at least one provider selection unit is configured to select providers for a request based at least in part on at least one requestor characteristic for the respective requester, such as geographically-related and socio-economic information, as an assigned characteristic for the respective requestor or a characteristic input by the respective requestor in making the request. [0091]
  • Preferably, the at least one provider selection unit is configured to select providers for a request based at least in part on at least one provider characteristic for the providers, such as requiring requesters to have a predeterminable profile or to provide contact details, as an assigned characteristic for the respective providers. [0092]
  • Preferably, the at least one provider selection unit is configured to select providers for a request based at least in part on current time. [0093]
  • Preferably, the at least one provider selection unit is configured to select providers for a request based at least in part on at least one classification characteristic, such as a selection mechanism for selecting providers, as an assigned characteristic for the respective classification. [0094]
  • Preferably, the system is configured such as to provide for a request to be relayed to the provider communicators of a predeterminable number of respective selected providers as addressed thereby. [0095]
  • Preferably, the system is configured to multicast a request to the provider communicators of respective selected providers where the respective request is to be relayed to a plurality of providers as addressed thereby. [0096]
  • In yet another aspect the present invention provides a method of matching requests of users, as requestors, to providers in servicing the requests, each of the requesters having at least one communicator for making requests and addressing replies thereto and each of the providers having at least one communicator for addressing requests and replies thereto, the method comprising the steps of: receiving requests from requesters; for each request, providing for the request to be relayed to selected providers as addressed thereby; receiving replies from selected providers, the replies received being made by the respective providers, as human decision-makers, based on the respective requests; and one or both of supplying, for each request, information regarding the respective requestor to any providers having provided a positive reply to the respective request, with a positive reply indicating that a provider is able to meet a request, and information regarding replies from selected providers to the respective request to the respective requestor. [0097]
  • Preferably, the method is a real-time matching method. [0098]
  • Preferably, the requests are free-format requests. [0099]
  • Preferably, the requests include voice requests. [0100]
  • Preferably, the communicators include mobile communicators, such as telephones, PDAs, personal computers and games devices. [0101]
  • Preferably, the communicators include fixed communicators, such as telephones, fax machines, personal computers, set-top boxes and games consoles. [0102]
  • Preferably, the communicators include combination fixed/mobile communicators, such as telephones. [0103]
  • In one embodiment the step of providing for a request to be relayed to selected providers as addressed thereby comprises the step of: relaying a request directly to the communicators of selected providers. [0104]
  • Preferably, a request is relayed without any interrogation thereof to establish content. [0105]
  • Preferably, the step of receiving requests from requestors comprises the step of: receiving requests from requestors at a plurality of receivers, each of the requests having a classification contact address associated with a predeterminable classification. [0106]
  • More preferably, the classification contact addresses are dialling numbers. [0107]
  • In one embodiment the method further comprises the step of: selecting respective providers to address a request. [0108]
  • Preferably, the step of selecting respective providers to address a request comprises the step of: selecting respective providers to address a request based at least in part on a geographic location assigned to the respective request and one or both of geographic locations or geographic zones assigned to the providers. [0109]
  • In one embodiment the geographic location assigned to the respective request is a current geographic location of the respective requestor. [0110]
  • Preferably, the current geographic location is determined from a communicator contact address of the communicator of the respective requester, where the communicator contact address has an assigned location. [0111]
  • More preferably, the communicator contact address is a dialling number. [0112]
  • In one embodiment the geographic location assigned to the respective request is an alternate geographic location as assigned by the respective requestor. [0113]
  • Preferably, the alternate geographic location is determined from a communicator contact address of a communicator, where the communicator contact address has an assigned location. [0114]
  • Preferably, the communicator contact address is a dialling number. [0115]
  • Preferably, geographic location of mobile communicators is determined from one of cell identification, triangulation, radio positioning or satellite positioning, such as GPS. [0116]
  • Preferably, geographic location of fixed communicators is determined from an assigned location. [0117]
  • Preferably, the step of selecting respective providers to address a request comprises the step of: selecting respective providers to address a request within a predeterminable spatial geographic zone relative to the geographic location assigned to the respective request. [0118]
  • More preferably, the predeterminable spatial geographic zone is one of a geographic radius relative to the geographic location assigned to the respective request, a distance of travel relative to the geographic location assigned to the respective request, or a time of travel relative to the geographic location assigned to the respective request. [0119]
  • Preferably, the step of selecting respective providers to address a request comprises the step of: selecting respective providers to address a request based at least in part on at least one requestor characteristic for the respective requestor, such as geographically-related and socio-economic information, as an assigned characteristic for the respective requestor or a characteristic input by the respective requestor in making the request. [0120]
  • Preferably, the step of selecting respective providers to address a request comprises the step of: selecting respective providers to address a request based at least in part on at least one provider characteristic for the providers, such as requiring requesters to have a predeterminable profile or to provide contact details, as an assigned characteristic for the respective providers. [0121]
  • Preferably, the step of selecting respective providers to address a request comprises the step of: selecting respective providers to address a request based at least in part on current time. [0122]
  • Preferably, the step of selecting respective providers to address a request comprises the step of: selecting respective providers to address a request based at least in part on at least one classification characteristic, such as a selection mechanism for selecting providers, as an assigned characteristic for the respective classification. [0123]
  • Preferably, the step of providing for a request to be relayed to selected providers as addressed thereby comprises the step of: providing for a request to be relayed to a predeterminable number of selected providers as addressed thereby. [0124]
  • Preferably, the step of providing for a request to be relayed to selected providers as addressed thereby comprises the step of: multicasting a request to selected providers where the request is to be relayed to a plurality of providers as addressed thereby. [0125]
  • Preferably, the step of supplying information comprises the step of: supplying, for a request, information regarding providers having provided a positive reply to the request to the respective requester. [0126]
  • In still yet another aspect the present invention provides a method of matching requests of users, as requesters, to providers in servicing the requests, each of the requestors having at least one communicator for making requests and addressing replies thereto and each of the providers having at least one communicator for addressing requests, the method comprising the steps of: receiving requests from requesters; for each request, providing for the request to be relayed to selected providers as addressed thereby; and receiving replies from providers, the replies received being made by the respective providers, as human decision-makers, based on the respective requests. [0127]
  • In a still yet further aspect the present invention provides a method of matching requests of users, as requestors, to providers in servicing the requests, the method comprising the steps of: receiving signals comprising requests from requestors; for each request, transmitting a signal to selected providers comprising the request as received; receiving signals comprising replies from selected providers, the replies being made by the respective providers based on the respective requests; and for each request, transmitting one or both of a signal comprising information regarding the respective requestor to any providers having provided a positive reply to the respective request, with a positive reply indicating that a provider is able to meet a request, and a signal comprising information regarding replies from selected providers to the respective request to the respective requestor. [0128]
  • The present invention, to be known as the Responsa™ matching system, provides an automated matching system, allowing in particular voice requests, and especially free-format requests, to be matched with providers that have received a request and have confirmed that the request can be met. [0129]
  • In a preferred embodiment this matching is achieved based on a location associated with the requestor, typically the location of the communicator of the requestor, the assigned locations of the providers in the classification selected, and the classification selected. In other embodiments the current time and characteristics of one or both of the requestor and the providers can be utilized in the selection of providers. [0130]
  • With the present invention, the request as received is relayed, re-played for voice requests, to selected providers, and, if any provider cannot satisfy the request, the provider simply has to decline the request, typically through one a “Decline” reply, a keystroke corresponding to a “Decline” reply, or simply hanging up the communicator. As the request is relayed, all communication by the requestors and the providers is a one-way communication. Thus, there is no direct conversation required between the requestor and a provider, both parties avoiding the time consuming task of having to establish a polite discussion when the provider cannot satisfy the request. A direct conversation ensues only between the requestor and a provider who can satisfy the request. [0131]
  • The present Invention provides for automated matching and yet allows the personal, free-format style of human communication. Preferred embodiments of the present invention, in utilizing free-format requests, provide the requestors with the freedom to frame the requests as desired; the language and form of the requests not being constrained, such as by requiring the requestor to utilize predetermined keywords. [0132]
  • In addition, the present invention only relays requests to providers who wish to receive requests and are in a position to service the requests, for example, providers who are open and within a specific geographic zone, as dictated by the particular classification. [0133]
  • In the present invention, it is human decision-makers, as opposed to a computer, who receive the requests and can intelligently interpret the requests. This avoids the problems associated with matching systems which require the requests to be defined using predetermined keywords, for example, by the use of drop-down menus. [0134]
  • Moreover, the present invention finds application both within a private environment, such as operated by organisations for use by members of the organisation, and a public environment, which allows use by members of the public. [0135]
  • In certain embodiments the present Invention can be configured to bias a match in favour of either the requestor or selected providers. This is envisaged to be appropriate within some niche applications, notably in the private environment.[0136]
  • Preferred embodiments of the present Invention will now be described hereinbelow by way of example only with reference to the accompanying drawings, in which: [0137]
  • FIG. 1 diagrammatically illustrates a matching system for matching requests of users, as requesters, to providers in servicing requests in accordance with a preferred embodiment of the present invention. [0138]
  • The matching system comprises at least one telephony management (TM) system [0139] 1, in this embodiment first and second TM systems 1 a, 1 b, for managing inbound telephone calls to and outbound telephone calls from the matching system. In another embodiment the matching system could include a single TM system 1, and in further embodiments could include any number, from tens to hundreds, of TM systems 1.
  • In this embodiment the TM systems [0140] 1 a, 1 b are co-located, but in other embodiments could be remotely located. In one such other embodiment the TM systems 1 a, 1 b could be located at separate locations in a geographic region. By way of example, in the UK, one TM system 1 a could be located at one center, for example, London, to serve the Southern half of the UK, and the other TM system 1 b could be located at another center, for example, Glasgow, to serve the Northern half of the UK. In other embodiments which include many TM systems 1, the TM systems 1 could be located at principal centers, for example, cities and towns, throughout a geographic region.
  • The matching system further comprises a first communications network [0141] 3 which provides a communications link to and between the TM systems 1 a, 1 b.
  • In this embodiment, where the TM systems [0142] 1 a, 1 b are co-located, the communications network 3 comprises a local area network (LAN), such as an Ethernet.
  • In other embodiments, where the TM systems [0143] 1 a, 1 b are remotely located, the communications network 3 could comprise a telephone network, preferably an integrated services digital network (ISDN).
  • The TM systems [0144] 1 a, 1 b each comprise an inbound telephony management (ITM) unit 5 for managing inbound telephone calls from requestors on inbound telephone lines 7, preferably ISDN lines. In this embodiment multiple subscriber numbering (MSN) is employed such that a plurality of requesters each requiring the same classification can be supported simultaneously.
  • The ITM unit [0145] 5 comprises an inbound interactive voice response (IIVR) module 11 which is connected to the inbound telephone lines 7 to monitor for inbound telephone calls and supports voice and keytones, an inbound telephony application management (ITAM) module 13 for generating request documents corresponding to the requests, in this embodiment voice requests, in each of the inbound telephone calls and transmitting the same to a provider selection unit 33 a, 33 b, 33 c, as will be described In more detail hereinbelow, a first, classification characteristics (CC) database 15 for storing the classification characteristics for each classification which is connected to the ITAM module 13, and a requestor information (RI) database 17 for storing information relating to requesters which is connected to the ITAM module 13.
  • With this configuration, the CC database [0146] 15 and the RI database 17 are not accessible to the IIVR module 11, thereby securing the RI database 17 from being accessed by a third party. In this embodiment the ITM unit 5 includes an intrusion detector between the IIVR module 11 and the ITAM module 13 such as to monitor, typically by the identification of unusual packets, for third party intrusion, and thereby provide for the security of the ITAM module 13.
  • In this embodiment communication between the IIVR module [0147] 11 and the ITAM module 13 is by the VoiceXML communications protocol.
  • In this embodiment a request document generated by the ITAM module [0148] 13 includes at least a classification identifier which, in this embodiment, is the called number, that is, the telephone number called by the requester, and identifies the classification to which the request is to be matched, a requester identifier which, in this embodiment, is the calling line identification (CLI) of the telephone of the requestor, that is, the telephone number to which the system or positive-reply providers are to contact in reply to the request, and identifies the requestor, and a request file corresponding to the request to be relayed to providers, in this embodiment a voice file corresponding to the voice request to be re-played to providers. In an alternative embodiment the requestor identifier is a telephone number derived either from the CLI of the telephone of a requestor or information, for example, including an authentication code, provided by the requestor in making the request.
  • In an alternative embodiment, as will be described in more detail hereinbelow, a request document generated by the ITAM module [0149] 13 could omit the request file for the request where the file is stored in a file store 19 which is accessible to enable the request subsequently to be relayed.
  • In this embodiment, a request document generated by the ITAM module [0150] 13 includes a location identifier which identifies the location of the search center, where the location of the requestor cannot be determined from the requestor identifier at the provider identification unit 33 a, 33 b, 33 c. Typical examples where the requestor identifier does not allow for the location of the requester to be determined are as a result of the requester being ex-directory and the requestor not having otherwise provided an address for the calling number or the calling telephone being a mobile telephone, or where the requester requires an alternate location for the search center. In this embodiment the location Identifier is a telephone number, other than the number of the calling telephone, which is provided by the requester to represent the location of the search center.
  • In this embodiment the CC database [0151] 15 is a structured query language (SQL) database.
  • In this embodiment the components of the ITM unit [0152] 5, namely the IIVR module 11, the ITAM module 13, the CC database 15 and the RI database 17, are co-located.
  • In other embodiments the IIVR module [0153] 11 and the ITAM module 13, can be co-located, and one or both of the CC database 15 and the RI database 17 remotely located. In this embodiment the communications network between the ITAM module 13 and the CC database 15 and the RI database 17 is a virtual private network (VPN).
  • In further embodiments one or both of the IIVR module [0154] 11 and the ITAM module 13 can be remotely located, and the CC database 15 and the RI database 17 co-located.
  • In a still further embodiment all of the components of the ITM unit [0155] 5, namely the IIVR module 11, the ITAM unit 13, the CC database 15 and the RI database 17, can be remotely located.
  • The TM systems [0156] 1 a, 1 b each further comprise a file store 19 for storing classification greetings and prompts for the supported classifications. As mentioned hereinabove, in one embodiment the file store 19 stores the request files for each of the requests from the requesters. This storage of the request files enables the request files to be retrieved, and thus the request documents need not include the request files, which provides for significantly higher traffic flows for the same system capacity, as the request documents are much smaller in size.
  • The operation of the ITM units [0157] 5 of the TM systems 1 a, 1 b will now be described hereinbelow.
  • The ITM units [0158] 5 each receive inbound telephone calls on the respective inbound telephone lines 7 from requestor communicators 20, in this embodiment telephones, with the particular ITM unit 5 which receives the telephone call being dictated by the called number, that is, the telephone number called by a requestor.
  • In this embodiment, where the matching system is configured to operate as a trade classification matching system, a requestor is able to select from a plurality of classification entries which correspond to different kinds of goods and service providers. Each classification entry has an associated telephone number which a requestor has to dial to access the matching system for that classification, and in this embodiment is the classification identifier which determines the search criteria, the matching criteria and the termination criteria by which the matching operation is performed, as will be described in more detail hereinbelow. In one embodiment each classification entry can include a summary of one or both of the service or goods in order to enable a requestor to determine that the correct classification is being selected for the particular request. [0159]
  • For each inbound call, the IIVR module [0160] 11 transmits the called number and the calling number, that is, the calling line identification (CLI) of the communicator 20 of the requestor, the calling communicator, to the ITAM module 13. In this embodiment the requestor communicator 20 can be a fixed telephone, a mobile telephone, a combination fixed/mobile telephone or a PDA.
  • The ITAM module [0161] 13 then looks up the called number in the CC database 15, and retrieves the classification greeting file identifier for the “Classification” greeting to be played to the requestor.
  • Where the called number is not associated with a classification, for example, where the called number was previously used in association with a classification but is not currently in use, the ITAM module [0162] 13 instructs the IIVR module 11 to execute an “Unassigned Classification” script, which plays an “Unassigned Classification” greeting and closes the call connection.
  • Where the calling communicator [0163] 20 has no CLI, as when CLI barred, the ITAM module 13 instructs the IIVR module 11 to execute a “Number Withheld” script, which plays a “Number Withheld” greeting which instructs the requestor to enable the CLI of the calling telephone or provide an authentication code relating to register as an authenticated requester.
  • In this embodiment the system is configured to allow a requestor to proceed with a request only when the inbound call has a CLI. By requiring the use of CLI-enabled communicators [0164] 20, abuse of the system by requesters directing replies to third parties can be prevented.
  • Where the calling communicator [0165] 20 has a CLI, the ITAM module 13 then looks up the CLI of the calling communicator 20 in the RI database 17 to confirm requester information, including confirmation that location information is available for the CLI, and obtain the default requestor preferences, such as whether the requestor details for the requestor are to be provided to providers or withheld.
  • Where the CLI of the calling communicator [0166] 20 is that of a fixed communicator and the RI database 17 Includes location information for the CLI of the calling telephone, the ITAM module 13 instructs the IIVR module 11 to execute a “Fixed Requestor” script.
  • Where the CLI of the calling communicator [0167] 20 is that of a mobile communicator and the RI database 17 includes no default location information for the CLI of the calling communicator 20, the ITAM module 13 determines the location of the calling communicator 20 from network information and instructs the IIVR module 11 to execute the “Mobile Requestor” script. In this embodiment the cell ID for the calling communicator 20 is utilized to determine the location of the requester, which cell ID is representative of the cell, that is a geographic zone, in which the calling communicator 20 is located, with the ITAM module 13 looking up the cell ID in the RI database 17 to obtain the location of the calling communicator 20. In other embodiments the calling communicator 20 of the requestor can be determined by triangulation, radio positioning or satellite positioning, such as GPS.
  • Where there is a CLI, but the location cannot be determined from the CLI, such as when the requester is ex-directory, that is, where the requester has required the service provider not to disclose location information corresponding to the number of the requester communicator [0168] 20, and no location information has been otherwise provided by the requester, the ITAM module 13 looks up the search vector for the classification corresponding to the called number in the CC database 15 to determine whether there is a vector for handling location-independent requesters. Where there is a vector for handling location-independent requesters, the ITAM module 13 utilizes that vector. Where there is no vector for handling location-independent requesters, the ITAM module 13 instructs the IIVR module 11 to execute a “Location Required” script which plays a “Location Required” greeting and prompts the requestor for location information, typically the number of a known CLI-enabled telephone, for which location Information is held in the CC database 15, to act as the search center.
  • Where there is a CLI, but the calling number is of a switchboard (manned or automated), the ITAM module [0169] 13 instructs the IIVR module 11 to execute an appropriate “Switchboard Requestor” script.
  • Under the “Fixed Requestor” and “Mobile Requestor” scripts, the IIVR module [0170] 11 plays a “Classification Title” greeting corresponding to the retrieved classification greeting identifier, and then a “Request Prompt” greeting which prompts for the request from the requestor. For example, where the called number corresponds to the classification “Toy Shops”, in this embodiment the classification greeting would be “Welcome to the Responsa™ classification for Toy Shops”, and the “Request Prompt” greeting would be “Please leave your request after the tone and hang up when completed”.
  • Under the “Switchboard Requestor” script, the IIVR module [0171] 11 plays in turn the “Classiflcation Title” greeting corresponding to the retrieved classification greeting identifier, an “Extension Identification” greeting which prompts the requestor to provide an extension number, typically, through the keying in of the number or through a voice reply, and the “Request Prompt” greeting which prompts for the request from the requestor. In this embodiment the “Request Prompt” greeting is played only following a predetermined keystroke on the calling communicator 20, which keystroke confirms the provision of the extension number of the calling communicator 20. For example, where the called number corresponds to the classification “Toy Shops”, in this embodiment the “Classification Title” greeting would be “Welcome to the Responsa™ classification for Toy Shops”, the “Extension Identification” greeting would be “Please leave your extension number after the tone, followed by the X key”, and, following the required keystroke, the “Request Prompt” greeting would be “Please leave your request after the tone and hang up when completed”.
  • Where a requestor wishes to set alternative preferences, for example, to withhold contact details from providers where the default is to provide details to providers, provide an alternative search center location, or alternative search parameters, the IIVR module [0172] 11 provides for the input of keystrokes to set these preferences.
  • In this embodiment the IIVR module [0173] 11 is configured to allow for the re-recording of requests, such as where a requestor makes a mistake in recording a request, through the keying of a predetermined keystroke.
  • Also in this embodiment the IIVR module [0174] 11 is configured to enable requests to be reviewed, here re-played, prior to initiating a matching operation.
  • In this embodiment the call connection is closed after the elapse of a predetermined period of time following the “Request Prompt” greeting, or on the requester hanging up where this event can be identified by the IIVR module [0175] 11.
  • In one embodiment the ITAM module [0176] 13 stores each request in the file store 19 under an assigned file name.
  • The TM systems [0177] 1 a, 1 b each further comprise an outbound telephony management (OTM) unit 21 for managing outbound calls on outbound lines 23, preferably ISDN lines, to providers on provider communicators 24 and requesters on requestor communicators 20.
  • The OTM unit [0178] 21 comprises an outbound interactive voice response (OIVR) module 25 which is connected to the outbound lines 23 for effecting outbound calls to providers and requestors, and an outbound telephony application management (OTAM) module 27 for scheduling and instructing calls to the OIVR module 25 in accordance with call documents as received from a provider selection unit 33 a, 33 b, 33 c. In this embodiment call documents can be scheduled in accordance with a priority flag, with, for example, status reports for requestors having a lower priority than requests for providers.
  • In operation, where effecting an outbound call to a provider, the OIVR module [0179] 25 dials the number of the provider communicator 24 as identified in the call document.
  • Where the call effected by the OIVR module [0180] 25 to the provider communicator 24 is answered, the OIVR module 25 executes a “Request Playback” script, which first plays a “VRS Welcome” greeting, for example “VRS for hairdressers”, followed by a first short tone, and subsequently re-plays the request to the provider followed by a second short tone. In this embodiment the request is relayed, here re-played, without any interrogation, such as by speech recognition, since such is not necessary; the classification being dictated by the called number. In an alternative embodiment the request could be interrogated, where a more refined or elaborate matching system is required.
  • On hearing the request, the provider has the following reply options, which each have an associated keystroke: [0181]
  • “Accept” which is confirmation that the request can be satisfied. For example, where the request is “Do you cut hair?”, that is, where the requester is merely attempting to obtain details of local hairdressers, and the request is appropriate, the provider would reply “Accept”. [0182]
  • “Probably” which is an indication that the request can probably be satisfied, but the provider has to confirm. Where the request is more complex, such as “Can you fit me in for a haircut next Thursday at 1530?”, the provider may recall that next Thursday afternoon is not fully booked, but would need to check if that exact time is free, in which case the provider would reply “Probably”. [0183]
  • “Decline” which confirms that the request cannot be satisfied. In this embodiment hanging up is the equivalent of the reply option “Decline”. [0184]
  • “Inappropriate” which indicates that the request is either inappropriate for the classification or incomprehensible. [0185]
  • “Abusive” which indicates that the request is considered abusive. [0186]
  • In this embodiment the replies of the providers are logged, such as to enable the classification managers to monitor the behaviour of the providers and in part the requestors, which inter alia allows for the targeted provision of guidance to requestors and providers, and even the barring of requesters or providers where behaviour is unacceptable. [0187]
  • For example, “Inappropriate” replies are logged against both the providers so replying and the requestors who made the requests, as repeated “Inappropriate” replies may be caused by either the requesters or the providers being confused about the purpose of a classification. [0188]
  • Also, “Abusive” replies are logged against both the providers so replying and the requesters who made the requests, and, In this embodiment, in addition to terminating a matching operation, repeated abusive requests, as established by confirmed “Abusive” replies, result in the respective requesters being barred from use of classifications or even the entire matching system. In this embodiment, repeated “Abusive” replies by providers, typically significantly above the average for a classification, would also be investigated. [0189]
  • On the provider providing a positive reply, that is, in this embodiment one of the reply options “Accept” or “Probably”, the OIVR module [0190] 25 executes an “Acknowledgement” script, which plays a “Reply Acknowledged” greeting followed by a short tone, and updates the call document to include a positive reply identifier and transmits the updated call document to the originating provider selection unit 33 a, 33 b, 33 c.
  • Where the contact details of the requester have been withheld, the “Acknowledgement” script also plays a “Contact Details Withheld” greeting. [0191]
  • Where the contact details are not withheld, the “Acknowledgement” script also provides contact details for the requestor followed by a short tone. In one embodiment the provider can record the details of the requestor subsequently to call the requester. In another embodiment the provider can contact the requestor directly through a predetermined keystroke. Where the requestor is following the process on line, the requestor is able to connect directly to the provider while the provider is still on line. [0192]
  • Where the calling communicator [0193] 20 is from an extension off a manned switchboard, the “Acknowledgement” script also provides the switchboard telephone number and the extension of the requester so as to allow the provider to navigate the switchboard.
  • Where the calling communicator [0194] 20 is from an extension off an unmanned switchboard, the “Acknowledgement” script also plays a “Please stay on line until a tone is heard” greeting. In the period prior to the tone, the details of the provider are provided to the requestor and the requestor is thus provided an opportunity to connect directly to the provider who is still on line. Where immediate connection is required, the requestor is connected to the provider and thereby establishes a conversation. Where immediate connection is not established, the requestor can contact the provider later.
  • In this embodiment the system is configured such as to allow the “Acknowledgement” script to be re-executed with a predetermined keystroke. [0195]
  • In this embodiment a positive reply is either of the reply options “Accept” or “Probably”. In other embodiments, and particularly for some classifications, the matching system can be configured to seek only “Accept” replies as positive replies, in which embodiments the “Request Playback” script also plays a “Decline or accept only, please” greeting, with all “Probably” and “Decline” replies being taken as negative replies. [0196]
  • Where the call effected by the OIVR module [0197] 25 to the provider is not answered, the OIVR module 25 assigns one of the following states as a call state identifier to the call document, that is, “Number Unobtainable” where the number held for the provider communicator 24 is unobtainable, “Engaged” where the number held for the provider is engaged, and “Rings Out” where the number held for the provider rings out and there is no reply, updates the call document to include the relevant call state identifier and transmits the updated call document to the originating provider selection unit 33 a, 33 b, 33 c.
  • The TM systems [0198] 1 a, 1 b each further comprise a telephony management (TM) communications network 29 which provides a communications link to the first main communications network 3 and between the ITM unit 5, in this embodiment both the IIVR module 11 and the ITAM module 13 separately, the file store 19, and the OTM unit 21, in this embodiment both the OIVR module 25 and the OTAM module 27 separately. In one embodiment the communication with the ITM unit 5, the file store 19 and the OTM unit 21, and between the IIVR module 11 and the ITAM module 13, is coded, typically either an encrypted communication or an authenticated communication, such as a signed communication.
  • In this embodiment, where the ITM unit [0199] 5, the file store 19 and the OTM unit 21 are co-located, the TM communications network 29 comprises a local area network (LAN), such as an Ethernet.
  • In other embodiments, where the ITM unit [0200] 5, the file store 19 and the OTM unit 21 are remotely located, the TM communications network 29 could comprise an established telephone network, preferably an ISDN network.
  • The matching system further comprises at least one provider selection unit [0201] 33, In this embodiment three provider selection units 33 a, 33 b, 33 c, for selecting the providers to be contacted in matching a request and scheduling the contact with the providers by the OTM units 21 of the TM systems 1 a, 1 b. It will be appreciated that the matching system can include any number of provider selection units 33; this embodiment including three provider selection systems 33 a, 33 b, 33 c simply by way of exemplification.
  • In this embodiment the provider selection units [0202] 33 a, 33 b, 33 c are co-located, but in other embodiments ones or all of the provider selection units 33 a, 33 b, 33 c could be remotely located.
  • In this embodiment the provider selection units [0203] 33 a, 33 b, 33 c are each configured to support all of the addressable classifications, but in other embodiments, particularly where there are many tens or hundreds of the provider selection units 33 a, 33 b, 33 c, the provider selection units 33 a, 33 b, 33 c could be configured to support only one classification or a sub-set of the addressable classifications.
  • The matching system further comprises a second main communications network [0204] 34 which provides a communications link to and between the provider selection units 33 a, 33 b, 33 c.
  • In this embodiment, where the provider selection units [0205] 33 a, 33 b, 33 c are co-located, the second main communications network 34 comprises a local area network (LAN), such as an Ethernet.
  • In other embodiments, where the provider selection units [0206] 33 a, 33 b, 33 c are remotely located, the second main communications network 34 could comprise a telephone network, preferably an integrated services digital network (ISDN).
  • The matching system further comprises a router [0207] 35 for routing request documents and call documents between respective ones of the TM systems 1 a, 1 b and the provider selection units 33 a, 33 b, 33 c.
  • The provider selection units [0208] 33 a, 33 b, 33 c each include a classification information (CI) database 37 which contains information, including provider characteristics, regarding each of the providers in each of the classifications supported by the respective provider selection unit 33 a, 33 b, 33 c, provider list building parameters for each classification, match criteria for each classification and termination criteria for each classification, a second requestor information (RI) database 39 which contains information, including requestor characteristics, regarding each of the requesters, a document scheduler 41 for scheduling documents to and from the respective one of the provider selection units 33 a, 33 b, 33 c, and a provider list building unit 43 which, for each request, builds a sorted provider list of providers from the providers contained in the CI database 37 for the classification to which the request is directed.
  • The CI database [0209] 37 contains information regarding each of the providers in each classification, each provider being referenced by a provider identifier. The information held for each provider includes the name of the provider, the address of the provider, the contact number for the provider, provider characteristics, and system history Information, including the number of requests delivered, the number of positive replies, that is, in this embodiment as one of “Accept” or “Probably” replies, and in other embodiments as an “Accept” reply, the number of negative replies, that is, in this embodiment as a “Decline” reply, and in other embodiments as one of “Decline” or “Probably” replies, the number of “Inappropriate” replies, and the number of “Abusive” replies. In this embodiment the CI database 37 is a spatial-join database, that is, a database which provides for spatial operations.
  • The provider list building unit [0210] 43 includes a provider selection module 44 which is configured to create one or more candidate provider lists in accordance with a predetermined listing mechanism for the classification to which the request is addressed, and, where the listing mechanism utilizes a location-based vector, based on a search center, which is usually the location of the requestor, but can be an alternative location as specified by the requester, or the location of the first provider having replied positively to a request where a search is re-centered. As will be described in more detail hereinbelow, the creation of a plurality of candidate provider lists provides for a mix of providers, for example, a mix of local and national providers.
  • In this embodiment the provider selection module [0211] 44 employs the following listing mechanisms to create the one or more candidate provider lists:
  • Listing Mechanism A—Closest [0212]
  • This listing mechanism creates a candidate provider list of candidate providers closest, in terms of a spatially-related parameter, typically direct (point-to-point) distance, travelling distance or travelling time, to the search center. In one embodiment the candidate provider list can be truncated by number, that is, to include a predetermined number of closest providers to the search center. In another embodiment the candidate provider list can be truncated by an upper limit to the spatially-related parameter, that is, to include all of the providers within a spatial zone of predetermined size. [0213]
  • Listing Mechanism B—Closest Cluster [0214]
  • This listing mechanism creates a candidate provider list of candidate providers which represent the closest set of providers, as a closest cluster, which satisfy the cluster characteristics for the classification to which the request is addressed. In this embodiment the cluster characteristics define the closest cluster as the closest set of providers comprising at least a predetermined number of providers within a spatial zone, typically direct (point-to-point) distance, travelling distance or travelling time, of predetermined size. [0215]
  • Listing Mechanism C—Greatest Density Cluster [0216]
  • This listing mechanism creates a candidate provider list of candidate providers which represent the set of providers, as a cluster but not necessarily the closest cluster, which satisfy the density characteristics for the classification to which the request is addressed. In this embodiment the density characteristics define the cluster as the set of providers comprising the highest number of providers within a first spatial zone, typically direct (point-to-point) distance, travelling distance or travelling time, of a first predetermined size within a second spatial zone of a second predetermined size of greater size than the first spatial zone and centered about the search center. This listing mechanism is effective to locate the largest town or city within the geographic zone, and avoids providers outside of the main concentrations, which are likely to be more widely dispersed. For this reason, it is expected that this listing mechanism will commonly be used as part of a series of searches. [0217]
  • Listing Mechanism D—Segment [0218]
  • This listing mechanism creates a candidate provider list of candidate providers from within a segment of a circle which has a predetermined segment angle and a radius of either a first predetermined size, typically direct (point-to-point) distance, travelling distance or travelling time, to the search center or a second smaller, distance where the segment of the smaller radius encompasses a predetermined number of candidate providers. [0219]
  • In this embodiment the candidate provider list is ordered in terms of a spatially-related parameter, typically direct (point-to-point) distance, travelling distance or travelling time, from the search center, with the closest being listed first in the list. Where re-invoked as result of the matching operation not being successful, a subsequent segment, either in a clockwise or counter-clockwise sense, is utilized. This listing mechanism has been developed for use where there is a variable, but high density of providers in a region of interest, and the requestor is keen to identify providers within a general travel direction extending from the search center. In this embodiment the segment of the circle is randomly selected. [0220]
  • Listing Mechanism E—All [0221]
  • This listing mechanism creates a candidate provider list of all of the candidate providers with a spatial zone, in terms of a spatially-related parameter, typically direct (point-to-point) distance, travelling distance or travelling time, of a predetermined size centered about the search center. [0222]
  • Listing Mechanism F—Threshold [0223]
  • This listing mechanism creates a candidate provider list of candidate providers which satisfy the threshold characteristics for the classification to which the request is addressed. In this embodiment the threshold characteristics define providers which satisfy a predetermined threshold criteria, for example, above or below at least one predetermined threshold value. Examples of threshold criteria include turnover, number of employees, quality rating, and speed of delivery. [0224]
  • The provider list building unit [0225] 43 further includes a provider sorting module 45 for creating provider contact lists by sorting the candidate providers in the candidate provider lists created by the provider selection module 44 in accordance with a predetermined sorting mechanism for the classification to which the request is addressed. In one embodiment the created provider contact lists can be truncated.
  • In this embodiment the provider sorting module [0226] 45 can employ the following sorting mechanisms:
  • Sorting Mechanism A—None [0227]
  • This sorting mechanism provides for no sorting of a candidate provider list. The provider contact list has the order of the candidate provider list as created by the provider selection module [0228] 44.
  • Sorting Mechanism B—Random [0229]
  • This sorting mechanism creates a provider contact list by randomizing a candidate provider list as created by the provider selection module [0230] 44.
  • Sorting Mechanism C—Take-Turns [0231]
  • This sorting mechanism creates a provider contact list by sorting a candidate provider list as created by the provider selection module [0232] 44 in accordance with the last contact with the providers so as to ensure that the providers are contacted in turn according to a specified ratio, with the last-contacted provider being at the bottom of the list. In this embodiment a log is maintained as to the previous contact with the providers.
  • Sorting Mechanism D—Closest [0233]
  • This sorting mechanism creates a provider contact list by sorting a candidate provider list as created by the provider selection module [0234] 44 in terms of a spatially-related parameter, typically direct (point-to-point) distance, travelling distance or travelling time, to the search center, with the closest being listed first and so on.
  • Sorting Mechanism E—Ranked [0235]
  • This sorting mechanism creates a provider contact list by sorting a candidate provider list as created by the provider selection module [0236] 44 into ranked order in accordance with a particular ranking parameter, for example, by turnover, number of employees, quality rating, and speed of delivery. This sorting mechanism is particularly suited to searching for providers where the location is unimportant. These providers will tend to be national providers, and the location of these providers is only relevant insofar that the providers encompass the location of the requester. A typical classification would be insurance services where contact with the providers would be by telephone. It will be appreciated that this sorting mechanism can create lists that never include certain providers and, for that reason, is usually utilized as one of a series of searches.
  • In this embodiment, where the list building criteria for a selected classification requires more than one contact provider list, the list building unit [0237] 43 is configured to merge the plurality of provider contact lists to create a single provider contact list. The creation of a single provider contact list from a plurality of provider contact lists finds application where a mix of providers, for example, local and national providers, are to be selected. A typical classification to which such a provider contact list is appropriate is that of computer suppliers, where a requestor may want a local provider or perhaps a national provider.
  • The provider contact lists built by the list building unit [0238] 43 include a plurality of state fields for each provider entry, but with the restriction that a provider can be included in only one field. In this way, the state of the provider can be maintained. Several states can be grouped as meaning that the request has not yet been delivered, these including the “Available”, “Out of Hours”, “Engaged” and “Ring Out” states. Final response states include the “Accepted”, “Declined”, “Probably”, “Inappropriate” and “Abusive” states.
  • In building a provider contact list, a database query is performed 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, an event is queued to move the provider from the “Out of Hours” field to the “Available” field. Similarly, as each “Available” provider becomes unavailable, an event is queued to move the provider from the “Available” to the “Out of Hours” state. [0239]
  • In one embodiment the provider selection units [0240] 33 a, 33 b, 33 c can be configured to provide for re-centering of the search center to the location of a provider providing the first positive reply. Where re-centering is enabled, and a provider has been identified who has provided a positive reply, the provider list building unit 43 is re-invoked to create a further provider contact list which utilizes the location of the identified provider as the search center. Such re-centering is utilized to identify providers which are as close together as possible, thereby attempting to avoid the identification of providers which are widely spaced, for example, two providers which are in opposite directions, and hence widely separated, from the search center. It is envisaged that re-centering will find application in identifying a number of relatively-closely located providers to be visited by the requestor, such as would be desired in enabling a comparison of the services or goods provided by the providers.
  • The document scheduler [0241] 41, in scheduling call documents to the OTM units 21 of the TM systems 1 a, 1 b is configured to perform a calculation to compute how many providers can be concurrently called and whether the calls are “Accept-Only”. That number is used to determine if the “In Progress” list of providers to be contacted can accommodate another provider. If another provider can be accommodated, the first provider from the “Available” list is used. If the “Available” list is empty, the document scheduler 41 waits for an “Engaged”, “Ring Out” or “Out of Hours” provider to become available. A further interface method is utilized to move a provider from one list to another, thereby allowing the document scheduler 41 to move an “In Progress” provider to the final response state, such as “Accepted”, “Declined”, “Probably”, etc. This is the same method used to move providers between “Available” and “Out of Hours” and vice versa. The use of the same method allows multiple checks to be performed, such as re-queuing an “Engaged” provider when the provider is “Out of Hours”.
  • The provider selection units [0242] 33 a, 33 b, 33 c are configured to terminate searching where the match criteria is satisfied, or, if the match criteria is not met, one of the following termination criteria where enabled. In this embodiment, for each classification, any of the termination criteria can be enabled or disabled. Where any of the termination criteria are enabled, the provider selection units 33 a, 33 b, 33 c terminate searching where termination criteria are satisfied, and a termination report is delivered to the respective provider.
  • In this embodiment the termination criteria are as follows: [0243]
  • Termination Event A—Number of Declines [0244]
  • For this termination event, termination occurs when a predetermined percentage of the providers on the provider contact list for the respective request have been contacted. The provider selection units [0245] 33 a, 33 b, 33 c are configured to contact as many of the selected providers as possible, in re-trying providers where the telephone numbers for those providers are engaged or ring out without answer. As will be appreciated, the telephone numbers for some providers may be permanently engaged or ring out, and, as such, the system cannot necessarily contact all selected providers.
  • Termination Event B—Elapse of Predetermined Period [0246]
  • For this termination event, termination occurs where a predetermined time limit has elapsed. In preferred embodiments termination occurs at the first of a predetermined time period having elapsed since the request was made by the requestor or a predetermined percentage of providers on the provider contact list for a request have not been contacted within a predetermined period since the request was made by the requestor. [0247]
  • Termination Event C—Abusive Request [0248]
  • For this termination event, termination occurs where a predetermined number, in this embodiment two, of the providers report a request as abusive, an “Abusive” reply being a reply option of the providers. [0249]
  • Termination Event D—Inappropriate Request [0250]
  • For this termination event, termination occurs where a predetermined number, in this embodiment two, of the providers report a request as inappropriate, an “Inappropriate” reply being a reply option of the providers. [0251]
  • Termination Event E—List Exhausted [0252]
  • For this termination event, termination occurs where the contact provider list is exhausted. [0253]
  • In a preferred embodiment the number of “Incomprehensible” or “Inappropriate” replies is set at a number greater than one, for example, two or three, such that a single “Incomprehensible” or “Inappropriate” reply is not sufficient to cause termination of the matching operation, as could be provided by a rogue provider or as a result of a simple mistake on the part of a provider. [0254]
  • Where the system has not satisfied the matching criteria within a reasonable time, the requestor is contacted and provided with a progress report. The system continues until either satisfying the matching criteria or one of the termination criteria. If the termination criteria is satisfied for a request, the requestor is contacted to report the end of the search and the results achieved. In general, if the requestor hears nothing, the requestor can be confident that the system has been successful in matching the request in accordance with the matching criteria for the classification. Progress or termination reports are returned to a switchboard requestor, but the reports are always preceded by the recorded name and extension number of the requestor, so that the switchboard operator can pass the message on to the requestor. [0255]
  • In this embodiment the system also provides for the initiation of the matching operation to be delayed. Often there are occasions when a person would like to make a request, but he is aware that most or all of the potential offers are currently closed. The system can still be used on these occasions. A requestor can make a request at any time of the day, for example, at 0200, knowing that the request is unlikely to be matched. Any selected providers active at that time will be contacted, allowing those providers an opportunity to respond to the request. The active periods will be known for all providers. During normal daytime working hours for many providers, the number of available providers will be much greater. If this is the case, the requestor will be given a termination report as usual, but the system is configured to relay the request again at a specified other time when a greater number of providers in the given classification are active. In this embodiment the system is configured such as to allow this feature to be over-ridden through the application of a predetermined keystroke. As a default, the act of hanging up is taken to require that the request be relayed at a time that is more likely to obtain a match. [0256]
  • In this embodiment the system is also configured such that a requester can specify an alternate location for the search center which is not that associated with the CLI of the calling telephone. In this embodiment, the IIVR module [0257] 11 provides for this feature to be enabled with a predetermined keystroke, and, when enabled, the IIVR module 11 executes an “Alternate Location” script which plays the “Alternate Location” greeting and prompts the requester to input the telephone number of the alternate search center, followed by another predetermined keystroke. The system then utilizes the alternate location telephone number to determine the search center. The system only uses the alternate location telephone number for building the provider contact list and not as the calling number. The calling number, usually the CLI, is utilized as the telephone number to which status or termination reports are delivered.
  • This feature provides for the circumstance where the requestor wishes to identify providers within a different geographic region. For example, suppose the requestor is travelling away to visit friends for a weekend and wants to locate a French restaurant in the region to be visited, the requestor would perform the “Alternate Location” keystroke during the classification greeting, and enter the enter the alternate telephone number, typically the telephone number of the friends to be visited, followed by a “Completion” keystroke, and then leave the request, for example, “A nice French restaurant, table for four, 1930 Saturday night, please phone back tonight.”. Where the contact mode is set to provide requestor details, any providers giving a positive reply would be provided with the calling number of the requester, as opposed to the alternate location telephone number. [0258]
  • In this embodiment the system is also configured to allow a requestor to remain on line and follow the matching operation. This would typically be where a requester believes that a match is quite likely to be achieved quickly. In this embodiment his feature is enabled through a predetermined keystroke on completion of the recordal of the request, and disabled by repeating the predetermined keystroke. The matching system reports each event In real-time, for example, “Just Cuts, declined”, “His Hair, declined”, “Cool Cuts, accepted”, etc. In this mode, each provider which provides a positive reply, in this embodiment one of an “Accept” or a “Probably”, is assigned a particular keystroke, and performing the relevant keystroke establishes a call to the provider. [0259]
  • In this embodiment, for each requestor, the configuration options Include a contact mode setting, which allows the requester to configure the system, in default, either to withhold the contact details of the requestor from providers, in which case any reports to the requestor are provided with the details of the Identified providers which have provided a positive reply in order to allow the requestor to contact the providers, or provide the contact details of the requestor to the identified providers on acceptance of the request, such that the accepting provider can contact the requestor directly. [0260]
  • In this embodiment the system is configured to enable a requestor to override the default contact mode setting, here by performing a predetermined keystroke during the classification greeting. In this embodiment, unless specifically configured, the default reply mode setting is to provide requestor details. Where the default contact mode setting is set to provide details, the application of the predetermined key acts to switch the contact mode setting to from that of provide requester details to withhold requestor details, whereupon the contact mode greeting “Requestor details will be withheld” is played, followed by the usual record request tone. Where the default contact mode setting is set to withhold details, application of the predetermined key acts to switch the contact mode setting from that of withhold requestor details to provide requestor details, whereupon the contact mode greeting “Requestor details will be supplied” is played, followed by the usual record request tone. [0261]
  • Where the contact mode setting is set to withhold requestor details, the system, having identified the providers for a request, calls the requestor on the calling number, and provides the termination report which includes the details of the providers, in this embodiment, for each provider, a contact name, either the name of the provider or a contact person at the provider, and the contact number. In this embodiment each of the providers mentioned in the termination report is assigned an associated key on the keypad, such as to allow the requestor to speed dial a selected one of the providers. Where the requester does not take the return call from the system, and the calling number of the requestor has an attached answer machine, the call is taken by the answer machine, with the termination report being recorded such as to enable the requestor to listen to the return call later. Where the calling number rings out, and the calling number of the requestor does not have an attached answer machine, the system calls back at set intervals until the call is made. [0262]
  • At the time of registration, the configuration details include the business availability of the provider, that is, the business working hours for each of the seven days of the week. Within these working hours, the system, as a default, is configured to assume that the provider wishes to receive requests. In this embodiment the system is configured such as to allow the provider to remove himself/herself from the classification and therefore not receive any further requests. Note that If the provider removes himself/herself from the classification, the provider will not appear in any lists built by the list building units [0263] 43 of the provider selection units 33 a, 33 b, 33 c until the provider positively re-introduces himself/herself into the classification. This feature allows businesses to turn the service off for long breaks, for example, holidays. Outside business hours, the system does not contact the provider, who, it is assumed, does not want to receive requests. In this embodiment a provider can temporarily alter the assigned business hours by setting one of “Open” or “Closed” states, but so setting the business is only a temporary function, and, if the assigned business are not reset before the next business hours session, the default times for hours of business are adopted.
  • In this embodiment the system enables a provider to block requests from requesters who cannot be serviced. A typical example is because the location of the requestor is not a location served by the requestor. Another typical example is where the provider only provides a service for a particular group of people, such as for the young as opposed to the elderly, and a request from an elderly person could not be serviced. This does not bias the search, but merely obviates inappropriate contacts. [0264]
  • In this embodiment the system also enables a provider to block requests from requestors where the contact details of the requesters are withheld. In such circumstances, a provider could be concerned that competitors would covertly use the system to gather intelligence. [0265]
  • In this embodiment these preferences are set by a classification manager using the classification management unit [0266] 49.
  • The matching system further comprises a classification management unit [0267] 49 which provides for the maintenance of the classification databases, that is, the CC database 15 and the CL database 37, and the requester databases, that is, the first and second RI databases 17, 39. In particular, the classification management unit 49 provides for the updating of provider entries, the inclusion of new provider entries, the alteration of the list building parameters for any classification, and the Inclusion of new classifications. In this embodiment the classification management unit 49 includes a web interface to allow for remote operation. In a preferred embodiment the classification management unit 49 is operated by a plurality of classification managers, each of which are assigned to and manage one or more classifications.
  • Finally, it will be understood that the present invention has been described in its preferred embodiments and can be modified in many different ways without departing from the scope of the invention as defined by the appended claims. [0268]
  • For example, in the described embodiments, the system is configured to utilize voice requests made using a telephone, but the use of other communicators [0269] 20, 24 is envisaged, for example, PDAs, personal computers, set-top boxes, games devices and games consoles, that is, any apparatus which has a communications function, and also other formats for the receipt and delivery of requests, for example, text-encoded requests, such as SMS and e-mail, pictoral requests, typically containing drawings, stills or video, such as MMS and EMS, and fax requests. Indeed, requests could be made in one format, for example, as voice requests, and delivered in another format, for example, SMS requests. Also, requests could be multi-format requests, for example, comprising voice and text-encoded request components or text-encoded and pictoral request components.
  • In general, the providers are the persons who respond to the respective requests, but there are exceptions. One such other provider is an observing provider who can only receive requests, but not respond to the requests. Another such provider is a split provider, where a request is received by one person, usually the decision-maker who replies to the request, and transferred to another person further to handle the request, for example, in handling the customer engagement. A further such provider is a sorting provider who receives the request and acts to re-direct the request to another provider. [0270]
  • As an example of a sorter provider, the providers can have a hierarchy. Thus, “Car Sales” could have children of “New Cars” and “Second Hand Cars”, which could themselves have children by make of car, for example, Ford, Vauxhall, VW etc. The system can support this hierarchy, but, consistent with the philosophy that humans are the best people to process requests, the system only supports cascading of classifications via human sorters. The matching process is as follows. A requester decides that he/she is looking for a new blue Ford Focus 1.8 Ghia. The requestor dials the telephone number for the classification “Car Sales” and leaves a request. The request is passed to selected providers within that classification. One provider may, however, be a dealership which sells many makes of car. For this provider, other departments have previously been configured with children described as hereinabove. In this case, the person that hears the request acts a sorter who decides to which department the request should be presented. The system is configured to recognize that this provider is a sorter and therefore expects to receive a keycode related to one of the previously set up departments. On receiving this keycode, the system presents the request to the newly-identified provider, which itself could be set up as a sorter provider. After looping through this procedure one or more times, the request will be made to a provider where no further sorting is required. [0271]
  • Further, where the system is to be utilized as a private matching system, the set-up for a private matching system is similar to above except that the matching system presents the request to a provider which has an Internal, private matching system. In this situation, all the keycodes that are used to obtain a response are logged, as these codes allow the hierarchy to be navigated to report and provide contact details. [0272]

Claims (51)

  1. 1-116. (Cancelled)
  2. 117. A matching system for matching requests of users, as requesters, to providers in servicing the requests, each of the requesters having at least one communicator for making requests and addressing replies thereto and each of the providers having at least one communicator for addressing requests, the system comprising:
    at least one request receiving unit for receiving free-format requests of requesters and storing the free-format requests as received;
    at least one request relaying unit for providing for each of the stored requests to be relayed to selected providers as addressed thereby such as to enable the selected providers, as human decision-makers, to interpret the respective requests and decide upon a match; and
    at least one reply receiving unit for receiving replies from providers, the replies received being made by the respective providers on interpreting the respective requests and deciding upon a match.
  3. 118. The system of claim 117, further comprising:
    at least one information supplying unit for one or both of supplying, for each request, information regarding the respective requestor to any providers having provided a positive reply to the respective request, with a positive reply indicating that a provider is able meet a request, and information regarding replies from selected providers to the respective request to the respective requester.
  4. 119. The system of claim 117, wherein the requests include voice requests.
  5. 120. The system of claim 117, comprising:
    at least one inbound communications unit, each comprising at least one request receiving unit.
  6. 121. The system of claim 117, comprising:
    at least one outbound communications unit, each comprising at least one request relaying unit, at least one reply receiving unit and at least one information supplying unit.
  7. 122. The system of claim 117, comprising:
    at least one communications unit, each comprising at least one request receiving unit,
    at least one request relaying unit, at least one reply receiving unit and at least one information supplying unit.
  8. 123. The system of claim 117, wherein the at least one request relaying unit is configured to relay a request directly to the communicators of selected providers.
  9. 124. The system of claim 117, wherein the at least one request relaying unit is configured to provide for a request to be relayed without any interrogation thereof to establish content.
  10. 125. The system of claim 117, wherein 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.
  11. 126. The system of claim 117, further comprising:
    at least one provider selection unit for selecting providers to address a request.
  12. 127. The system of claim 126, wherein the at least one provider selection unit is configured to select providers for a request based at least in part on a geographic location assigned to the respective request and one or both of geographic locations or geographic zones assigned to the providers.
  13. 128. The system of claim 127, wherein the geographic location assigned to the respective request is a current geographic location of the respective requester.
  14. 129. The system of claim 128, wherein the current geographic location is determined from a communicator contact address of the communicator of the respective requester, where the communicator contact address has an assigned location.
  15. 130. The system of claim 127, wherein the geographic location assigned to the respective request is an alternate geographic location as assigned by the respective requester.
  16. 131. The system of claim 130, wherein the alternate geographic location is determined from a communicator contact address of a communicator, where the communicator contact address has an assigned location.
  17. 132. The system of claim 126, wherein the at least one provider selection unit is configured to select providers for a request within a predeterminable spatial geographic zone relative to the geographic location assigned to the respective request.
  18. 133. The system of claim 132, wherein the predeterminable spatial geographic zone is one of a geographic radius relative to the geographic location assigned to the respective request, a distance of travel relative to the geographic location assigned to the respective request, or a time of travel relative to the geographic location assigned to the respective request.
  19. 134. The system of claim 126, wherein the at least one provider selection unit is configured to select providers for a request based at least in part on at least one requester characteristic for the respective requester, such as geographically-related and socio-economic information, as an assigned characteristic for the respective requestor or a characteristic input by the respective requestor in making the request.
  20. 135. The system of claim 126, wherein the at least one provider selection unit is configured to select providers for a request based at least in part on at least one provider characteristic for the providers, such as requiring requesters to have a predeterminable profile or to provide contact details, as an assigned characteristic for the respective providers.
  21. 136. The system of claim 126, wherein the at least one provider selection unit is configured to select providers for a request based at least in part on current time.
  22. 137. The system of claim 126, wherein the at least one provider selection unit is configured to select providers for a request based at least in part on at least one classification characteristic, such as a selection mechanism for selecting providers, as an assigned characteristic for the respective classification.
  23. 138. The system of claim 126, wherein the at least one provider selection unit is configured to schedule relaying of a request to selected providers by the at least one request relaying unit in accordance with match criteria and terminate a matching operation where the match criteria or termination criteria are satisfied.
  24. 139. The system of claim 117, wherein the at least one request relaying unit is configured to relay a request to a predeterminable number of selected providers as addressed thereby.
  25. 140. The system of claim 117, wherein the at least one request relaying unit is configured to multicast a request to selected providers where the request is to be relayed to a plurality of providers as addressed thereby.
  26. 141. The system of claim 117, wherein the at least one information supplying unit is configured, for a request, to supply information regarding providers having provided a positive reply to the request to the respective requestor.
  27. 142. A method of matching requests of users, as requesters, to providers in servicing the requests, each of the requesters having at least one communicator for making requests and addressing replies thereto and each of the providers having at least one communicator for addressing requests, the method comprising the steps of:
    receiving free-format requests of requesters;
    storing the free-format requests as received;
    for each request, providing for the stored request to be relayed to selected providers as addressed thereby such as to enable the selected providers, as human decision-makers, to interpret the request and decide upon a match; and
    receiving replies from providers, the replies received being made by the respective providers on interpreting the respective requests and deciding upon a match.
  28. 143. The method of claim 142, further comprising the step of:
    one or both of supplying, for each request, information regarding the respective requester to any providers having provided a positive reply to the respective request, with a positive reply indicating that a provider is able to meet a request, and information regarding replies from selected providers to the respective request to the respective requester.
  29. 144. The method of claim 142, wherein the requests include voice requests.
  30. 145. The method of claim 142, wherein the step of providing for a request to be relayed to selected providers as addressed thereby comprises the step of:
    relaying a request directly to the communicators of selected providers.
  31. 146. The method of claim 142, wherein a request is relayed without any interrogation thereof to establish content.
  32. 147. The method of claim 142, wherein the step of receiving requests from requestors comprises the step of:
    receiving requests from requesters at a plurality of receivers, each of the requests having a classification contact address associated with a predeterminable classification.
  33. 148. The method of claim 142, further comprising the step of:
    selecting respective providers to address a request.
  34. 149. The method of claim 148, wherein the step of selecting respective providers to address a request comprises the step of:
    selecting respective providers to address a request based at least in part on a geographic location assigned to the respective request and one or both of geographic locations or geographic zones assigned to the providers.
  35. 150. The method of claim 149, wherein the geographic location assigned to the respective request is a current geographic location of the respective requester.
  36. 151. The method of claim 150, wherein the current geographic location is determined from a communicator contact address of the communicator of the respective requester, where the communicator contact address has an assigned location.
  37. 152. The method of claim 149, wherein the geographic location assigned to the respective request is an alternate geographic location as assigned by the respective requester.
  38. 153. The method of claim 152, wherein the alternate geographic location is determined from a communicator contact address of a communicator, where the communicator contact address has an assigned location.
  39. 154. The method of claim 148, wherein the step of selecting respective providers to address a request comprises the step of:
    selecting respective providers to address a request within a predeterminable spatial geographic zone relative to the geographic location assigned to the respective request.
  40. 155. The method of claim 154, wherein the predeterminable spatial geographic zone is one of a geographic radius relative to the geographic location assigned to the respective request, a distance of travel relative to the geographic location assigned to the respective request, or a time of travel relative to the geographic location assigned to the respective request.
  41. 156. The method of claim 148, wherein the step of selecting respective providers to address a request comprises the step of:
    selecting respective providers to address a request based at least in part on at least one requestor characteristic for the respective requestor, such as geographically-related and socio-economic information, as an assigned characteristic for the respective requester or a characteristic input by the respective requestor in making the request.
  42. 157. The method of claim 148, wherein the step of selecting respective providers to address a request comprises the step of:
    selecting respective providers to address a request based at least in part on at least one provider characteristic for the providers, such as requiring requestors to have a predeterminable profile or to provide contact details, as an assigned characteristic for the respective providers.
  43. 158. The method of claim 148, wherein the step of selecting respective providers to address a request comprises the step of:
    selecting respective providers to address a request based at least in part on current time.
  44. 159. The method of claim 148, wherein the step of selecting respective providers to address a request comprises the step of:
    selecting respective providers to address a request based at least in part on at least one classification characteristic, such as a selection mechanism for selecting providers, as an assigned characteristic for the respective classification.
  45. 160. The method of claim 148, further comprising the steps of:
    scheduling relaying of a request to selected providers in accordance with match criteria; and
    terminating a matching operation where the match criteria or termination criteria are satisfied.
  46. 161. The method of claim 142, wherein the step of providing for a request to be relayed to selected providers as addressed thereby comprises the step of:
    providing for a request to be relayed to a predeterminable number of selected providers as addressed thereby.
  47. 162. The method of claim 142, wherein the step of providing for a request to be relayed to selected providers as addressed thereby comprises the step of:
    multicasting a request to selected providers where the request is to be relayed to a plurality of providers as addressed thereby.
  48. 163. The method of claim 142, wherein the step of supplying information comprises the step of:
    supplying, for a request, information regarding providers having provided a positive reply to the request to the respective requester.
  49. 164. A matching system for matching requests of users, as requesters, to providers in servicing the requests, the system comprising:
    a plurality of requestor communicators, each being for use by requestors in making free-format requests and addressing any respective replies thereto, at least ones of the replies including information regarding replies from selected providers to respective requests; and
    a plurality of provider communicators, each being for use by providers in addressing requests and any respective replies thereto, the requests being relayed to respective selected providers as addressed such as to enable the selected providers, as human decision-makers, to interpret the respective requests and decide upon a match, and at least ones of the replies including information regarding the requester of a respective request where having provided a positive reply to the respective request, with a positive reply indicating that a provider is able to meet a request.
  50. 165. A matching system for matching requests of users, as requestors, to providers in servicing the requests, the system comprising:
    a plurality of requestor communicators, each being for use by requestors in making free-format requests and addressing respective replies thereto;
    a plurality of provider communicators, each being for use by providers in addressing requests and respective replies thereto; and
    at least one communications unit communicatable with the requester communicators and the provider communicators, and including at least one provider selection unit for selecting providers to address each request made by a requestor;
    wherein, for each request, the system is configured such that the request is provided to be relayed to selected providers as addressed thereby such as to enable the selected providers, as human decision-makers, to interpret the request and decide upon a match.
  51. 166. A method of matching requests of users, as requesters, to providers in servicing the requests, the method comprising the steps of:
    receiving signals comprising free-format requests from requesters;
    for each request, transmitting a signal to selected providers comprising the request as received such as to enable the selected providers, as human decision-makers, to interpret the request and decide upon a match;
    receiving signals comprising replies from selected providers, the replies being made by the respective providers on interpreting the respective requests and deciding upon a match; and
    for each request, transmitting one or both of a signal comprising information regarding the respective requestor to any providers having provided a positive reply to the respective request, with a positive reply indicating that a provider is able to meet a request, and a signal comprising information regarding replies from selected providers to the respective request to the respective requestor.
US10493229 2000-05-19 2002-11-06 Request matching system and method Abandoned US20040254929A1 (en)

Priority Applications (3)

Application Number Priority Date Filing Date Title
GB0012195A GB0012195D0 (en) 2000-05-19 2000-05-19 Location information services
GB0012195.4 2000-05-19
PCT/GB2002/004987 WO2003040971A1 (en) 2001-11-07 2002-11-06 Request matching system and method

Publications (1)

Publication Number Publication Date
US20040254929A1 true true US20040254929A1 (en) 2004-12-16

Family

ID=9891978

Family Applications (2)

Application Number Title Priority Date Filing Date
US10276754 Active 2021-12-22 US7209757B2 (en) 2000-05-19 2001-04-23 Location information services
US10493229 Abandoned US20040254929A1 (en) 2000-05-19 2002-11-06 Request matching system and method

Family Applications Before (1)

Application Number Title Priority Date Filing Date
US10276754 Active 2021-12-22 US7209757B2 (en) 2000-05-19 2001-04-23 Location information services

Country Status (5)

Country Link
US (2) US7209757B2 (en)
EP (1) EP1282988A1 (en)
CN (1) CN100474944C (en)
GB (1) GB0012195D0 (en)
WO (1) WO2001091485A1 (en)

Cited By (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20080120623A1 (en) * 2006-11-22 2008-05-22 Fujitsu Limited Work-flow apparatus, work-flow process, and computer-readable medium storing work-flow program
US20080243556A1 (en) * 2006-10-31 2008-10-02 Dennis Hogan Historical insurance transaction system and method
US20090023429A1 (en) * 2007-07-17 2009-01-22 Yahoo! Inc. Asynchronous search platform for mobile device users
EP2146526A1 (en) 2008-07-14 2010-01-20 Samsung Electronics Co., Ltd. Apparatus and method for providing regional information in mobile communication system
US20100305978A1 (en) * 2009-05-29 2010-12-02 Hyperquest, Inc. Automation of auditing claims
US20100305941A1 (en) * 2009-05-29 2010-12-02 Hyperquest, Inc. Automation of auditing claims
US20100305977A1 (en) * 2009-05-29 2010-12-02 Hyperquest, Inc. Automation of auditing claims
US20120158764A1 (en) * 2009-03-03 2012-06-21 Microsoft Corporation Mapping from objects to data model
US20130216029A1 (en) * 2010-09-30 2013-08-22 British Telecommunications Public Limited Company Speech comparison
US8543431B2 (en) 2009-05-29 2013-09-24 Hyperquest, Inc. Automation of auditing claims

Families Citing this family (140)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7333946B1 (en) 2000-09-01 2008-02-19 Nokia Corporation Ticketing with printing option
GB0109429D0 (en) * 2001-04-17 2001-06-06 Vanes David C Improvements relating to transport resource management
WO2003034761A1 (en) * 2001-10-12 2003-04-24 Schlumberger Systemes Process and device for value added service access control
GB0126516D0 (en) * 2001-11-05 2002-01-02 Nokia Corp A method and system for providing a service
EP1451737A1 (en) * 2001-11-07 2004-09-01 Sitra Ltd Request matching system and method
EP2200224B1 (en) * 2001-12-27 2016-03-30 Brother Kogyo Kabushiki Kaisha Restriction for providing service
EP1466435A4 (en) 2002-01-08 2011-05-18 Seven Networks Inc Secure transport for mobile communication network
WO2003069874A9 (en) * 2002-02-11 2004-03-04 Unified Dispatch Inc Automated transportation call-taking system
JP3826807B2 (en) * 2002-02-13 2006-09-27 日本電気株式会社 Positioning system in a mobile communication network
JP4199475B2 (en) 2002-04-11 2008-12-17 日本電気株式会社 Positioning gateway device, terminal location information request processing method and program
US6958709B2 (en) * 2002-08-08 2005-10-25 General Electric Company Method, system, and storage medium for integrating vehicle management, transportation and communications functions
US7340260B2 (en) * 2002-10-09 2008-03-04 Mdf Holdings, Inc. System and method for tracking the location of multiple mobile radio transceiver units
DE60313735T2 (en) * 2003-03-28 2007-10-18 Alcatel Lucent Communication method for a wireless network
US20050108366A1 (en) * 2003-07-02 2005-05-19 International Business Machines Corporation Administering devices with domain state objects
US7275689B2 (en) * 2003-09-05 2007-10-02 Bcode Pty Ltd Baggage check-in using short message device
EP1519288A1 (en) * 2003-09-25 2005-03-30 Nagravision S.A. Car-pooling system and process and communication device for carrying out the process
US7742757B2 (en) * 2003-10-14 2010-06-22 At&T Mobility Ii Llc Location announcement for mobile devices
FI20040036A0 (en) 2004-01-13 2004-01-13 Nokia Corp Production Location Information in the visited network
WO2005094109A1 (en) * 2004-03-18 2005-10-06 Nokia Corporation Position-based context awareness for mobile terminal device
JP2005316610A (en) * 2004-04-27 2005-11-10 Ntt Docomo Inc Data distribution device and data distribution method
WO2006007623A1 (en) * 2004-07-22 2006-01-26 Blue Pulse Pty Ltd Location dependent content provision
US9704502B2 (en) 2004-07-30 2017-07-11 Invention Science Fund I, Llc Cue-aware privacy filter for participants in persistent communications
US9779750B2 (en) * 2004-07-30 2017-10-03 Invention Science Fund I, Llc Cue-aware privacy filter for participants in persistent communications
US9723087B2 (en) * 2004-08-03 2017-08-01 Lg Electronics Inc. User privacy management apparatus and method in mobile communications system
US20060079249A1 (en) * 2004-08-03 2006-04-13 Lg Electronics Inc. User privacy management apparatus and method in mobile communications system
KR100690867B1 (en) * 2004-08-06 2007-03-09 엘지전자 주식회사 Apparatus and method for managing user privacy in mobile communication system
US8010082B2 (en) 2004-10-20 2011-08-30 Seven Networks, Inc. Flexible billing architecture
WO2006045102A3 (en) 2004-10-20 2008-11-13 Seven Networks Inc Method and apparatus for intercepting events in a communication system
US7706781B2 (en) 2004-11-22 2010-04-27 Seven Networks International Oy Data security in a mobile e-mail service
FI117152B (en) 2004-12-03 2006-06-30 Seven Networks Internat Oy The introduction of mobile e-mail settings
DE102005003435A1 (en) * 2005-01-25 2006-07-27 Giesecke & Devrient Gmbh Data record transmitting method for use in e.g. heater consumption data reading areas, involves transmitting data record to portion of transmitting line by using contact device for communication with devices provided outside mobile terminal
US7752633B1 (en) 2005-03-14 2010-07-06 Seven Networks, Inc. Cross-platform event engine
US7353034B2 (en) 2005-04-04 2008-04-01 X One, Inc. Location sharing and tracking using mobile phones or other wireless devices
EP1883914B1 (en) * 2005-05-06 2011-07-06 Omnilink Systems, Inc. System and method of tracking the movement of individuals and assets
WO2006108077A1 (en) 2005-04-06 2006-10-12 Omnilink Systems, Inc. System and method for tracking monitoring, collecting, reporting and communicating with the movement of individuals
US7796742B1 (en) 2005-04-21 2010-09-14 Seven Networks, Inc. Systems and methods for simplified provisioning
US8438633B1 (en) 2005-04-21 2013-05-07 Seven Networks, Inc. Flexible real-time inbox access
US8045998B2 (en) 2005-06-08 2011-10-25 Cisco Technology, Inc. Method and system for communicating using position information
WO2006136660A1 (en) 2005-06-21 2006-12-28 Seven Networks International Oy Maintaining an ip connection in a mobile network
US8069166B2 (en) 2005-08-01 2011-11-29 Seven Networks, Inc. Managing user-to-user contact with inferred presence information
US7853563B2 (en) 2005-08-01 2010-12-14 Seven Networks, Inc. Universal data aggregation
US7917468B2 (en) 2005-08-01 2011-03-29 Seven Networks, Inc. Linking of personal information management data
US8468126B2 (en) 2005-08-01 2013-06-18 Seven Networks, Inc. Publishing data in an information community
WO2007014574A1 (en) * 2005-08-02 2007-02-08 Galini Associates Ltd System and method for controlling multiple services with restricted access
US7706339B2 (en) 2005-08-10 2010-04-27 Cisco Technology, Inc. Method and system for communicating media based on location of media source
US7633914B2 (en) 2005-08-10 2009-12-15 Cisco Technology, Inc. Method and system for providing interoperable communications with location information
US7636339B2 (en) 2005-08-10 2009-12-22 Cisco Technology, Inc. Method and system for automatic configuration of virtual talk groups based on location of media sources
US7869386B2 (en) * 2005-08-29 2011-01-11 Cisco Technology, Inc. Method and system for conveying media source location information
FR2890511B1 (en) * 2005-09-08 2007-10-26 Alcatel Sa Device processing information data on passenger transport, for mobile terminals attached to a mobile communication network
WO2007073748A1 (en) * 2005-12-16 2007-07-05 Entersoft Szamitastechnikai Kft. System and method for determining the tolls for road sections and/or regions which are subject to a toll
US8085671B2 (en) 2006-02-27 2011-12-27 Cisco Technology, Inc. Method and system for providing interoperable communications with congestion management
US8260338B2 (en) 2006-02-28 2012-09-04 Cisco Technology, Inc. Method and system for providing interoperable communications with dynamic event area allocation
US7570959B2 (en) 2006-04-19 2009-08-04 Nokia Corporation Apparatus, method and computer program product providing location-enhanced contact list
US7860070B2 (en) 2006-05-10 2010-12-28 Cisco Technology, Inc. Providing multiple virtual talk group communication sessions
US7831270B2 (en) 2006-05-18 2010-11-09 Cisco Technology, Inc. Providing virtual talk group communication sessions in accordance with endpoint resources
US20070270166A1 (en) * 2006-05-19 2007-11-22 Karl Georg Hampel Prioritization of location queries in a location-based services system
US7639634B2 (en) 2006-06-02 2009-12-29 Cisco Technology, Inc. Method and System for Joining a virtual talk group
US7769395B2 (en) 2006-06-20 2010-08-03 Seven Networks, Inc. Location-based operations and messaging
US8118223B2 (en) * 2006-09-28 2012-02-21 Visa U.S.A. Inc. Smart sign mobile transit fare payment
US8523069B2 (en) * 2006-09-28 2013-09-03 Visa U.S.A. Inc. Mobile transit fare payment
US8570909B1 (en) 2006-10-17 2013-10-29 Cisco Technology, Inc. Method and system for providing an indication of a communication
US7527208B2 (en) 2006-12-04 2009-05-05 Visa U.S.A. Inc. Bank issued contactless payment card used in transit fare collection
US8386349B2 (en) * 2007-02-28 2013-02-26 Visa U.S.A. Inc. Verification of a portable consumer device in an offline environment
US8346639B2 (en) 2007-02-28 2013-01-01 Visa U.S.A. Inc. Authentication of a data card using a transit verification value
US20080203170A1 (en) * 2007-02-28 2008-08-28 Visa U.S.A. Inc. Fraud prevention for transit fare collection
US8115621B2 (en) * 2007-05-01 2012-02-14 Yoganand Rajala Device for tracking the movement of individuals or objects
US8874159B2 (en) 2007-05-10 2014-10-28 Cisco Technology, Inc. Method and system for handling dynamic incidents
US8805425B2 (en) 2007-06-01 2014-08-12 Seven Networks, Inc. Integrated messaging
US8693494B2 (en) 2007-06-01 2014-04-08 Seven Networks, Inc. Polling
US8364181B2 (en) 2007-12-10 2013-01-29 Seven Networks, Inc. Electronic-mail filtering for mobile devices
US8793305B2 (en) 2007-12-13 2014-07-29 Seven Networks, Inc. Content delivery to a mobile device from a content service
US9002828B2 (en) 2007-12-13 2015-04-07 Seven Networks, Inc. Predictive content delivery
US8738485B2 (en) 2007-12-28 2014-05-27 Visa U.S.A. Inc. Contactless prepaid product for transit fare collection
US8131307B2 (en) 2008-01-03 2012-03-06 Lubeck Olaf M Method for requesting transportation services
WO2009087489A1 (en) * 2008-01-08 2009-07-16 Jean-Marie Michaud Networking system
US8107921B2 (en) 2008-01-11 2012-01-31 Seven Networks, Inc. Mobile virtual network operator
US8862657B2 (en) 2008-01-25 2014-10-14 Seven Networks, Inc. Policy based content service
US20090192851A1 (en) * 2008-01-25 2009-07-30 Bishop Paul L Location-Based Transportation Management
US20090193338A1 (en) 2008-01-28 2009-07-30 Trevor Fiatal Reducing network and battery consumption during content delivery and playback
US8787947B2 (en) 2008-06-18 2014-07-22 Seven Networks, Inc. Application discovery on mobile devices
US8078158B2 (en) 2008-06-26 2011-12-13 Seven Networks, Inc. Provisioning applications for a mobile device
US9112707B2 (en) * 2008-08-15 2015-08-18 International Business Machines Corporation System and method for providing location based services using collaborative networks
US9159238B2 (en) * 2008-10-02 2015-10-13 Microsoft Technology Licensing, LLP Location-aware selection of public transportation
US8909759B2 (en) 2008-10-10 2014-12-09 Seven Networks, Inc. Bandwidth measurement
US8892128B2 (en) * 2008-10-14 2014-11-18 Telecommunication Systems, Inc. Location based geo-reminders
US8041378B2 (en) 2008-12-19 2011-10-18 Cisco Technology, Inc. System and method for providing channel configurations in a communications environment
US8433341B2 (en) * 2009-02-05 2013-04-30 Universal Metaphor, Llc System and methods for distributed tracking of public transit vehicles
US8787929B2 (en) * 2009-02-09 2014-07-22 International Business Machines Corporation System and methods for providing location information using location based queues
WO2011073700A1 (en) * 2009-12-16 2011-06-23 Pintz Gyoergy Configuration and procedure for setting up a seat reservation system
US8489113B2 (en) * 2010-02-09 2013-07-16 Omnilink Systems, Inc. Method and system for tracking, monitoring and/or charging tracking devices including wireless energy transfer features
US8639439B2 (en) * 2010-03-26 2014-01-28 Hon Hai Precision Industry Co., Ltd. Electronic device and transportion information management method utilized thereby
US9043731B2 (en) 2010-03-30 2015-05-26 Seven Networks, Inc. 3D mobile user interface with configurable workspace management
US8554608B1 (en) 2010-04-17 2013-10-08 James O'Connor Driver controlled automated taxi service and devices
US9043433B2 (en) 2010-07-26 2015-05-26 Seven Networks, Inc. Mobile network traffic coordination across multiple applications
US8838783B2 (en) 2010-07-26 2014-09-16 Seven Networks, Inc. Distributed caching for resource and mobile network traffic management
WO2012018556A3 (en) 2010-07-26 2012-08-09 Michael Luna Mobile application traffic optimization
US9077630B2 (en) 2010-07-26 2015-07-07 Seven Networks, Inc. Distributed implementation of dynamic wireless traffic policy
WO2012060995A3 (en) 2010-11-01 2012-07-12 Michael Luna Distributed caching in a wireless network of content delivered for a mobile application over a long-held request
WO2012060997A3 (en) 2010-11-01 2012-07-19 Michael Luna Application and network-based long poll request detection and cacheability assessment therefor
US9330196B2 (en) 2010-11-01 2016-05-03 Seven Networks, Llc Wireless traffic management system cache optimization using http headers
US8843153B2 (en) 2010-11-01 2014-09-23 Seven Networks, Inc. Mobile traffic categorization and policy for network use optimization while preserving user experience
WO2012061437A1 (en) 2010-11-01 2012-05-10 Michael Luna Cache defeat detection and caching of content addressed by identifiers intended to defeat cache
GB201307556D0 (en) 2010-11-01 2013-06-12 Seven Networks Inc Caching adapted for mobile application behavior and network conditions
US8484314B2 (en) 2010-11-01 2013-07-09 Seven Networks, Inc. Distributed caching in a wireless network of content delivered for a mobile application over a long-held request
US9060032B2 (en) 2010-11-01 2015-06-16 Seven Networks, Inc. Selective data compression by a distributed traffic management system to reduce mobile data traffic and signaling traffic
WO2012061430A3 (en) 2010-11-01 2012-06-28 Michael Luna Distributed management of keep-alive message signaling for mobile network resource conservation and optimization
GB201309234D0 (en) 2010-11-22 2013-07-03 Seven Networks Inc Optimization of resource polling internvals to satisfy mobile device requests
WO2012071283A1 (en) 2010-11-22 2012-05-31 Michael Luna Aligning data transfer to optimize connections established for transmission over a wireless network
CN102073031A (en) * 2010-12-09 2011-05-25 南京航空航天大学 Sensor network-based environmental monitoring system and method
GB2501416B (en) 2011-01-07 2018-03-21 Seven Networks Llc System and method for reduction of mobile network traffic used for domain name system (DNS) queries
EP2700019A4 (en) 2011-04-19 2015-01-28 Seven Networks Inc Social caching for device resource sharing and management
US8832228B2 (en) 2011-04-27 2014-09-09 Seven Networks, Inc. System and method for making requests on behalf of a mobile device based on atomic processes for mobile network traffic relief
WO2012149434A3 (en) 2011-04-27 2013-01-24 Seven Networks, Inc. Detecting and preserving state for satisfying application requests in a distributed proxy and cache system
US9239800B2 (en) 2011-07-27 2016-01-19 Seven Networks, Llc Automatic generation and distribution of policy information regarding malicious mobile traffic in a wireless network
US8868753B2 (en) 2011-12-06 2014-10-21 Seven Networks, Inc. System of redundantly clustered machines to provide failover mechanisms for mobile traffic management and network resource conservation
US8934414B2 (en) 2011-12-06 2015-01-13 Seven Networks, Inc. Cellular or WiFi mobile traffic optimization based on public or private network destination
GB2498064A (en) 2011-12-07 2013-07-03 Seven Networks Inc Distributed content caching mechanism using a network operator proxy
US9277443B2 (en) 2011-12-07 2016-03-01 Seven Networks, Llc Radio-awareness of mobile device for sending server-side control signals using a wireless network optimized transport protocol
WO2013090821A1 (en) 2011-12-14 2013-06-20 Seven Networks, Inc. Hierarchies and categories for management and deployment of policies for distributed wireless traffic optimization
WO2013090834A1 (en) 2011-12-14 2013-06-20 Seven Networks, Inc. Operation modes for mobile traffic optimization and concurrent management of optimized and non-optimized traffic
US20130159511A1 (en) 2011-12-14 2013-06-20 Seven Networks, Inc. System and method for generating a report to a network operator by distributing aggregation of data
US20130173316A1 (en) * 2011-12-30 2013-07-04 Rajesh Agrawal Mobile Ticket Application
EP2801236A4 (en) 2012-01-05 2015-10-21 Seven Networks Inc Detection and management of user interactions with foreground applications on a mobile device in distributed caching
US20130267253A1 (en) * 2012-01-12 2013-10-10 Environmental Systems Research Institute, Inc. Trigger zones and dwell time analytics
US9215578B2 (en) 2012-01-27 2015-12-15 Omnilink Systems, Inc. Monitoring systems and methods
WO2013116856A1 (en) 2012-02-02 2013-08-08 Seven Networks, Inc. Dynamic categorization of applications for network access in a mobile network
WO2013116852A1 (en) 2012-02-03 2013-08-08 Seven Networks, Inc. User as an end point for profiling and optimizing the delivery of content and data in a wireless network
US8812695B2 (en) 2012-04-09 2014-08-19 Seven Networks, Inc. Method and system for management of a virtual network connection without heartbeat messages
US8775631B2 (en) 2012-07-13 2014-07-08 Seven Networks, Inc. Dynamic bandwidth adjustment for browsing or streaming activity in a wireless network based on prediction of user behavior when interacting with mobile applications
US9161258B2 (en) 2012-10-24 2015-10-13 Seven Networks, Llc Optimized and selective management of policy deployment to mobile clients in a congested network to prevent further aggravation of network congestion
WO2014077770A1 (en) * 2012-11-16 2014-05-22 Mobile Payment Solutions Holding Nordic Ab Method for making a payment using a portable communication device
US9307493B2 (en) 2012-12-20 2016-04-05 Seven Networks, Llc Systems and methods for application management of mobile device radio state promotion and demotion
US9241314B2 (en) 2013-01-23 2016-01-19 Seven Networks, Llc Mobile device with application or context aware fast dormancy
US8874761B2 (en) 2013-01-25 2014-10-28 Seven Networks, Inc. Signaling optimization in a wireless network for traffic utilizing proprietary and non-proprietary protocols
US8750123B1 (en) 2013-03-11 2014-06-10 Seven Networks, Inc. Mobile device equipped with mobile network congestion recognition to make intelligent decisions regarding connecting to an operator network
CN103295394B (en) * 2013-06-24 2015-01-14 东南大学 Method based on generalized GPS (global position system) data for determining passenger-waiting station alternative addresses of taxis
US9065765B2 (en) 2013-07-22 2015-06-23 Seven Networks, Inc. Proxy server associated with a mobile carrier for enhancing mobile traffic management in a mobile network
CN104735121B (en) * 2013-12-23 2018-04-24 财团法人工业技术研究院 The matchmaking service device and a network method and system
US9713085B2 (en) * 2014-05-30 2017-07-18 Verizon Patent And Licensing Inc. Dynamic activation and deactivation of access points
RU2608882C2 (en) * 2014-12-25 2017-01-25 Общество С Ограниченной Ответственностью "Яндекс" Method of user search request processing and server

Citations (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4360875A (en) * 1981-02-23 1982-11-23 Behnke Robert W Automated, door-to-door, demand-responsive public transportation system
US5432840A (en) * 1990-11-27 1995-07-11 Ryden; Leif C. Method and arrangement for connecting selectively a stationary subscriber apparatus to a neighboring mobile subscriber apparatus with the aid of a telephone switchboard function
US5930474A (en) * 1996-01-31 1999-07-27 Z Land Llc Internet organizer for accessing geographically and topically based information
US6061432A (en) * 1997-12-23 2000-05-09 Bell Atlantic Network Services, Inc. Voice mail system for obtaining routing information from signaling nodes
US6182050B1 (en) * 1998-05-28 2001-01-30 Acceleration Software International Corporation Advertisements distributed on-line using target criteria screening with method for maintaining end user privacy
US20010037174A1 (en) * 2000-04-04 2001-11-01 Dickerson Stephen L. Communications and computing based urban transit system
US20010037280A1 (en) * 2000-03-09 2001-11-01 Ingraham Scott S. System and method for facilitating renting and purchasing relationships
US6338081B1 (en) * 1997-06-12 2002-01-08 International Business Machines Corporation Message handling method, Message handling apparatus, and memory media for storing a message handling apparatus controlling program
US6345273B1 (en) * 1999-10-27 2002-02-05 Nancy P. Cochran Search system having user-interface for searching online information
US6842460B1 (en) * 2001-06-27 2005-01-11 Nokia Corporation Ad hoc network discovery menu
US6862594B1 (en) * 2000-05-09 2005-03-01 Sun Microsystems, Inc. Method and apparatus to discover services using flexible search criteria
US7065500B2 (en) * 1999-05-28 2006-06-20 Overture Services, Inc. Automatic advertiser notification for a system for providing place and price protection in a search result list generated by a computer network search engine
US7284036B2 (en) * 2001-01-29 2007-10-16 Koninklijke Philips N.V. Method, wireless MP3 player and system for downloading MP3 files from the internet

Family Cites Families (30)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP0235498B2 (en) * 1985-12-09 1996-01-03 Funktaxi 3130 Vermittlungsgesellschaft m.b.H. und Co. KG. Communication exchange device and method for hired vehicles
US5168451A (en) * 1987-10-21 1992-12-01 Bolger John G User responsive transit system
FR2674355B1 (en) * 1991-03-21 1995-07-07 Grp Taxi Ste Nouvelle Individual transport system or semi-collective terminal has automatic call.
US5724520A (en) * 1993-06-08 1998-03-03 Anthony V. Pugliese Electronic ticketing and reservation system and method
US5493694A (en) * 1993-11-08 1996-02-20 Trimble Navigation Limited Fast response system for a fleet of vehicles
US5570100A (en) * 1994-03-10 1996-10-29 Motorola, Inc. Method for providing a communication unit's estimated time of arrival
US5648768A (en) * 1994-12-30 1997-07-15 Mapsys, Inc. System and method for identifying, tabulating and presenting information of interest along a travel route
DE19524927A1 (en) * 1995-07-08 1997-01-09 Sel Alcatel Ag Guidance of a participant within an SDMA mobile radio network
US6006159A (en) * 1995-08-14 1999-12-21 Schmier; Kenneth J. Public transit vehicle arrival information system
US5812959A (en) * 1996-02-27 1998-09-22 Trimble Navigation Limited Automated vehicle recommendation system
US6519463B2 (en) * 1996-02-28 2003-02-11 Tendler Cellular, Inc. Location based service request system
US5963861A (en) * 1996-04-05 1999-10-05 Lucent Technologies Inc. Dealer-locator service and apparatus for mobile telecommunications system
US5799263A (en) * 1996-04-15 1998-08-25 Bct Systems Public transit system and apparatus and method for dispatching public transit vehicles
FR2757726B1 (en) * 1996-12-20 1999-03-19 Bannery Jacques Method and Call centralized system to access a service, including centralized call taxis
FR2765710B1 (en) 1997-07-04 1999-09-10 Jean Claude Decaux information system for informing users of a public transport system with respect to waiting times at stops of the network
US5959577A (en) * 1997-08-28 1999-09-28 Vectorlink, Inc. Method and structure for distribution of travel information using network
US6529735B1 (en) * 1997-12-19 2003-03-04 Telefonaktiebolaget Lm Ericsson (Publ) Method and arrangement in a communication network
US6535743B1 (en) * 1998-07-29 2003-03-18 Minorplanet Systems Usa, Inc. System and method for providing directions using a communication network
EP1046097B1 (en) 1998-09-17 2004-03-17 Philips Electronics N.V. Remote control device with location dependent interface
US20020016171A1 (en) * 1998-09-30 2002-02-07 Yurdaer N. Doganata Mobile unit location system for automatically reporting to a central controller and subscriber the proximity of mobile units to a destination
US6339745B1 (en) * 1998-10-13 2002-01-15 Integrated Systems Research Corporation System and method for fleet tracking
US6563430B1 (en) * 1998-12-11 2003-05-13 Koninklijke Philips Electronics N.V. Remote control device with location dependent interface
US6304850B1 (en) * 1999-03-17 2001-10-16 Netmarket Group, Inc. Computer-implemented system and method for booking airline travel itineraries
US6466796B1 (en) * 1999-04-01 2002-10-15 Lucent Technologies Inc. System for providing location based service to a wireless telephone set in a telephone system
US6212393B1 (en) * 1999-08-02 2001-04-03 Motorola, Inc. Method and apparatus for communication within a vehicle dispatch system
US6756913B1 (en) * 1999-11-01 2004-06-29 Mourad Ben Ayed System for automatically dispatching taxis to client locations
US6615046B1 (en) * 1999-12-29 2003-09-02 International Business Machines Corporation Automatic dispatch of mobile services
JP2003109191A (en) * 2001-09-28 2003-04-11 Fujitsu Ltd Vehicle allocation system and vehicle allocation processor
US6606557B2 (en) * 2001-12-07 2003-08-12 Motorola, Inc. Method for improving dispatch response time
US6711500B2 (en) * 2002-03-15 2004-03-23 E-Lead Electronic Co., Ltd. Method for vehicle dispatching system

Patent Citations (13)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4360875A (en) * 1981-02-23 1982-11-23 Behnke Robert W Automated, door-to-door, demand-responsive public transportation system
US5432840A (en) * 1990-11-27 1995-07-11 Ryden; Leif C. Method and arrangement for connecting selectively a stationary subscriber apparatus to a neighboring mobile subscriber apparatus with the aid of a telephone switchboard function
US5930474A (en) * 1996-01-31 1999-07-27 Z Land Llc Internet organizer for accessing geographically and topically based information
US6338081B1 (en) * 1997-06-12 2002-01-08 International Business Machines Corporation Message handling method, Message handling apparatus, and memory media for storing a message handling apparatus controlling program
US6061432A (en) * 1997-12-23 2000-05-09 Bell Atlantic Network Services, Inc. Voice mail system for obtaining routing information from signaling nodes
US6182050B1 (en) * 1998-05-28 2001-01-30 Acceleration Software International Corporation Advertisements distributed on-line using target criteria screening with method for maintaining end user privacy
US7065500B2 (en) * 1999-05-28 2006-06-20 Overture Services, Inc. Automatic advertiser notification for a system for providing place and price protection in a search result list generated by a computer network search engine
US6345273B1 (en) * 1999-10-27 2002-02-05 Nancy P. Cochran Search system having user-interface for searching online information
US20010037280A1 (en) * 2000-03-09 2001-11-01 Ingraham Scott S. System and method for facilitating renting and purchasing relationships
US20010037174A1 (en) * 2000-04-04 2001-11-01 Dickerson Stephen L. Communications and computing based urban transit system
US6862594B1 (en) * 2000-05-09 2005-03-01 Sun Microsystems, Inc. Method and apparatus to discover services using flexible search criteria
US7284036B2 (en) * 2001-01-29 2007-10-16 Koninklijke Philips N.V. Method, wireless MP3 player and system for downloading MP3 files from the internet
US6842460B1 (en) * 2001-06-27 2005-01-11 Nokia Corporation Ad hoc network discovery menu

Cited By (20)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7945478B2 (en) 2006-10-31 2011-05-17 Hyperquest, Inc. Historical vehicle parts database system
US20080243556A1 (en) * 2006-10-31 2008-10-02 Dennis Hogan Historical insurance transaction system and method
US20080120623A1 (en) * 2006-11-22 2008-05-22 Fujitsu Limited Work-flow apparatus, work-flow process, and computer-readable medium storing work-flow program
US20090023429A1 (en) * 2007-07-17 2009-01-22 Yahoo! Inc. Asynchronous search platform for mobile device users
EP2146526A1 (en) 2008-07-14 2010-01-20 Samsung Electronics Co., Ltd. Apparatus and method for providing regional information in mobile communication system
US8392462B2 (en) * 2009-03-03 2013-03-05 Microsoft Corporation Mapping from objects to data model
US20120158764A1 (en) * 2009-03-03 2012-06-21 Microsoft Corporation Mapping from objects to data model
US8346577B2 (en) 2009-05-29 2013-01-01 Hyperquest, Inc. Automation of auditing claims
US20100305977A1 (en) * 2009-05-29 2010-12-02 Hyperquest, Inc. Automation of auditing claims
US8255205B2 (en) 2009-05-29 2012-08-28 Hyperquest, Inc. Automation of auditing claims
US20100305941A1 (en) * 2009-05-29 2010-12-02 Hyperquest, Inc. Automation of auditing claims
US20100305978A1 (en) * 2009-05-29 2010-12-02 Hyperquest, Inc. Automation of auditing claims
US8447632B2 (en) 2009-05-29 2013-05-21 Hyperquest, Inc. Automation of auditing claims
US8447638B2 (en) 2009-05-29 2013-05-21 Hyperquest, Inc. Automation of auditing claims
US8478583B2 (en) 2009-05-29 2013-07-02 Hyperquest, Inc. Computer system with second translator for vehicle parts
US8510101B2 (en) 2009-05-29 2013-08-13 Hyperquest, Inc. Computer system with second translator for vehicle parts
US8600782B2 (en) 2009-05-29 2013-12-03 Hyperquest, Inc. Automation of auditing claims
US8543431B2 (en) 2009-05-29 2013-09-24 Hyperquest, Inc. Automation of auditing claims
US8781863B2 (en) 2009-05-29 2014-07-15 Hyperquest, Inc. Automation of auditing claims
US20130216029A1 (en) * 2010-09-30 2013-08-22 British Telecommunications Public Limited Company Speech comparison

Also Published As

Publication number Publication date Type
WO2001091485A1 (en) 2001-11-29 application
GB0012195D0 (en) 2000-07-12 grant
CN100474944C (en) 2009-04-01 grant
US20030153330A1 (en) 2003-08-14 application
US7209757B2 (en) 2007-04-24 grant
CN1436431A (en) 2003-08-13 application
EP1282988A1 (en) 2003-02-12 application

Similar Documents

Publication Publication Date Title
US5930700A (en) System and method for automatically screening and directing incoming calls
US6738462B1 (en) Unified communications automated personal name addressing
US6594502B1 (en) Dating system
US6430289B1 (en) System and method for computerized status monitor and use in a telephone network
US7373428B1 (en) Intelligent filtering for contact spanning multiple access networks
US6075851A (en) Organization chart based call information routing
US20040125940A1 (en) Computer telephony integration (CTI) complete hospitality contact center
US20080037720A1 (en) Voice Activated Communication Using Automatically Updated Address Books
US20100046731A1 (en) Method, apparatus and system for use of presence and location information in intelligent call routing
US20050157858A1 (en) Methods and systems for contact management
US20030108187A1 (en) Hold queue wait estimations
US20030112928A1 (en) Logging calls according to call context
US7631047B1 (en) Systems and methods for providing critical information based on profile data
US20030007627A1 (en) Technique for providing information assistance including concierge-type services
US7103172B2 (en) Managing caller profiles across multiple hold queues according to authenticated caller identifiers
US20020038219A1 (en) Matching and communication method and system
US20010012335A1 (en) Preference based telecommunication information service
US20020076026A1 (en) Automated personalized telephone management system
US7640006B2 (en) Directory assistance with multi-modal messaging
US20030185379A1 (en) Managing communications in a call centre
US6970906B1 (en) Voice mail caller identification
US20040086094A1 (en) Method of providing personal event notification during call setup
US20030165223A1 (en) Technique for providing a telecommunication service including information assistance
US6678366B1 (en) System and method for locating subscribers using a best guess location algorithm
US5963626A (en) Method and system for posting messages to callers based on caller identity

Legal Events

Date Code Title Description
AS Assignment

Owner name: SITRA LTD., UNITED KINGDOM

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:ISAAC, STEPHEN JOHN;REEL/FRAME:014816/0935

Effective date: 20040622