# US 6,731,927 B1 · System and method for context association

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 6,731,927 B1
- Document ID: US6731927B1
- Status: Granted
- Kind: B1
- Application number: 09/668,591
- Filed: 2000-09-22
- Granted: 2004-05-04
- Earliest claimed: 2000-07-14
- Assignees: Context Connect, LLC
- Inventors: Robert Allen Stern; Rod Drury; Sunny Ahn
- Web page: https://patentgrep.com/patent/US6731927B1

## CPC

- H04M 15/49: {Connection to several service providers}
- H04M 3/4931: {Directory assistance systems}
- H04M 15/00: Arrangements for metering, time-control or time indication {; Metering, charging or billing arrangements for voice wireline or wireless communications, e.g. VoIP}
- H04M 15/51: {for resellers, retailers or service providers}
- H04M 3/48: Arrangements for recalling a calling subscriber when the wanted subscriber ceases to be busy
- H04M 2207/18: wireless networks
- H04M 2215/32: Involving wireless systems
- H04M 2215/46: Connection to several service providers
- H04M 2215/54: Resellers-retail or service providers billing, e.g. agreements with telephone service operator, activation, charging/recharging of accounts
- Y10S 707/99939: Privileged access
- H04M: TELEPHONIC COMMUNICATION (circuits for controlling other apparatus via a telephone cable and not involving telephone switching apparatus G08)
- Y10S: TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS

## Abstract

The present invention relates generally to an information system, and more particularly to a system and method for providing access to an entity by context association.

## Claims

### Claim 1

A method for providing information or access to a subscriber comprising the steps:
associating a subscriber or data with at least one predetermined context;
locating the at least one context; and
providing information or access to the subscriber or data when the at least one context is located, wherein a service provider of the subscriber or data provides the information or access to the subscriber or data.

### Claim 2 (depends on 1)

The method according to claim 1, wherein the at least one context includes at least one subscriber fact.

### Claim 3 (depends on 1)

The method according to claim 1, wherein the at least one context includes a context key that is used to locate the at least one subscriber.

### Claim 4 (depends on 3)

The method according to claim 3, wherein the context key includes a domain of predetermined conventions that is used to associate the subscriber with at least one entity, service or other individual, or a combination thereof.

### Claim 5 (depends on 3)

The method according to claim 3, wherein the context key is a private protection key for use by users having discrete knowledge about a predetermined individual or predetermined service.

### Claim 6 (depends on 3)

The method according to claim 3, wherein the context key is a private protection key for use by an organization for providing access to members of the organization.

### Claim 7 (depends on 1)

The method according to claim 1, further comprising the step of incurring a predetermined charge when access is provided.

### Claim 8 (depends on 1)

The method according to claim 1, further comprising the step of incurring a predetermined charge when at least one context is located.

### Claim 9 (depends on 1)

The method according to claim 1, wherein the providing step maintains a predetermined aspect of the subscriber or the data.

### Claim 10 (depends on 1)

The method according to claim 1, wherein the providing step includes transactions for wiring instructions or funds without revealing predetermined data relevant to the transaction.

### Claim 11

A method for providing access to a subscriber comprising the steps:
acquiring a list of predetermined subscribers;
associating at least one predetermined context for each predetermined subscriber on the list;
locating the at least one context; and
providing access to one or more predetermined subscribers on the list when the at least one context is located, wherein the access to the one or more predetermined subscribers is provided without a contact number of the one or more predetermined subscribers being released from a service provider of the one or more predetermined subscribers.

### Claim 12

A method for providing access to a subscriber comprising the steps:
establishing a list having at least one predetermined context;
establishing a list having at least one predetermined subscriber;
associating at least one predetermined context for each predetermined subscriber;
receiving a request for access to at least one predetermined subscriber, wherein the request includes at least one predetermined context associated with the at least one predetermined subscriber;
locating the at least one context; and
forwarding the request to a service provider of the at least one predetermined subscriber, wherein the service provider provides access to the at least one predetermined subscriber.

### Claim 13

A method for providing access to a subscriber comprising the steps:
associating a predetermined subscriber with at least one predetermined context;
locating the at least one context using a first service provider or directory service; and
providing access to the predetermined subscriber when the at least one context is located using a second service provider or directory service.

### Claim 14 (depends on 13)

The method according to claim 13, wherein the at least one context includes at least one predetermined subscriber fact.

### Claim 15 (depends on 13)

The method according to claim 13, wherein the step of associating is accomplished when the predetermined context is a domain of conventions that are associated with individuals or services for locating predetermined subscribers by users having discrete knowledge about the individual or service desired.

### Claim 16

A system for providing access to a plurality of subscribers comprising:
a directory of addresses that are contextually associated with a predetermined subscriber or service, each address providing access or information to one or more of the plurality of subscribers; and
a director providing access or information to one or more of the plurality of subscribers by associating one or more of the plurality of subscribers with at least one predetermined context, wherein the access or information is provided while contact information of the one or more of the plurality of subscribers remains known only to a service provider of the one or more of the plurality of subscribers.

### Claim 17 (depends on 16)

The system of claim 16, wherein the director provides statistics regarding the subscriber or service accessed.

### Claim 18 (depends on 16)

The system of claim 16, wherein the director accepts information from the associated subscriber that determines whether another subscriber can have access or proved information.

### Claim 19 (depends on 16)

The system of claim 16, wherein the director accepts information from the associated subscriber that determines whether another subscriber can have information about the associated subscriber.

### Claim 20 (depends on 16)

The system of claim 16, wherein the director determines whether another subscriber can have access or information.

### Claim 21 (depends on 16)

The system of claim 16, wherein the director prevents said association with one or more subscribers.

### Claim 22 (depends on 16)

The system of claim 16, wherein the director prevents association with one or more participants unless a privacy key has been provided for the association.

### Claim 23 (depends on 16)

The system of claim 16, wherein the directory associates a privacy key to at least one or more subscribers.

### Claim 24 (depends on 16)

The system according to claim 16, wherein the provider establishes or collects a predetermined charge when access is provided.

### Claim 25 (depends on 16)

The system according to claim 16, wherein the provider establishes or collects a predetermined charge when at least one context is located.

### Claim 26 (depends on 16)

The system according to claim 16, wherein the system is an Application Service Provider for managing connectivity worldwide.

### Claim 27

A system for providing access to a subscriber comprising:
an associator for associating a predetermined subscriber with at least one predetermined context;
a locator for locating the at least one context; and
a provider for providing access to the predetermined subscriber when the at least one context is located, wherein the associator is a directory assistance provider or directory service and the provider is a service provider of the predetermined subscriber.

### Claim 28 (depends on 27)

The system according to claim 27, wherein the at least one context includes at least one subscriber fact.

### Claim 29 (depends on 27)

The system according to claim 27, wherein the at least one context includes a context key that is used to locate the at least one subscriber.

### Claim 30 (depends on 29)

The system according to claim 29, wherein the context key includes a domain of predetermined conventions that are used to associate the at least one subscriber, or predetermined individuals, or predetermined services, or a combination thereof.

### Claim 31 (depends on 29)

The system according to claim 29, wherein the context key is a private protection key for use by users having discrete knowledge about a predetermined individual or predetermined service.

### Claim 32 (depends on 27)

The system according to claim 27, wherein the provider establishes or collects a predetermined charge when access is provided.

### Claim 33 (depends on 27)

The system according to claim 27, wherein the provider establishes or collects a predetermined charge when at least one context is located.

### Claim 34

A directory assistance system providing communication connectivity to a subscriber, comprising:
a service provider database having contact information for a subscriber associated with a key;
a contextual directory, in communication with the service provider database, having at least one context associated with the key; wherein:
upon receipt of a call requesting communication connectivity to a pre-determined subscriber, the request including at least one context associated with the pre-determined subscriber, the at least one context received is located, and the key associated with the at least one context in the directory is forwarded with the call to the pre-determined subscriber's service provider where resolution of the key with contact information for the pre-determined subscriber occurs and communication connectivity to the pre-determined subscriber is provided.

### Claim 35 (depends on 34)

The system of claim 34, wherein communication connectivity is provided without revealing the contact information for the pre-determined subscriber outside of the subscriber's service provider.

### Claim 36 (depends on 34)

The system of claim 34, wherein communication connectivity is provided without a need for the directory assistance system to have knowledge of or retain the contact information for the pre-determined subscriber.

### Claim 37 (depends on 34)

The system of claim 34, wherein a caller requesting communication connectivity to a pre-determined subscriber is billed through the caller's service provider upon location of the at least one context in the directory.

### Claim 38 (depends on 37)

The system of claim 37, wherein the pre-determined subscriber is not billed upon location of the at least one context in the directory.

### Claim 39 (depends on 34)

The system of claim 34, wherein a caller requesting communication connectivity to a pre-determined subscriber is billed through the caller's service provider upon communication connection to the pre-determined subscriber.

### Claim 40 (depends on 39)

The system of claim 39, wherein the at least one pre-determined subscriber is not billed upon communication connection to the at least one pre-determined subscriber.

### Claim 41 (depends on 39)

The system of claim 39, wherein the pre-determined subscriber's service provider is compensated for involvement with the system upon communication connection to the pre-determined subscriber.

### Claim 42 (depends on 34)

The system of claim 34, further comprising a service provider connector, the service provider connector providing an interface between the service provider database and the contextual directory, the connector resolving the key with the contact information for the pre-determined subscriber and providing the communication connectivity to the pre-determined subscriber.

### Claim 43 (depends on 34)

The system of claim 34, wherein the key further identifies a communication connectivity platform selected from the group consisting of home telephone, office telephone, cell telephone, e-mail address, and facsimile device.

### Claim 44 (depends on 34)

The system of claim 34, wherein the service provider database further includes financial account information of the subscriber.

### Claim 45 (depends on 44)

The system of claim 44, wherein the communication connectivity includes a funds transaction, and the financial account information of the subscriber is not revealed outside of the subscriber's service provider.

### Claim 46

A method for providing communication connectivity to a subscriber, comprising the steps of:
receiving a call requesting communication connectivity to a pre-determined subscriber, the request including at least one context associated with the pre-determined subscriber;
locating the at least one context in a contextual directory and associating the at least one context with a key;
forwarding the key and the call to a service provider database and linking the key with contact information for the pre-determined subscriber;
providing communication connectivity to the pre-determined subscriber.

### Claim 47 (depends on 46)

The method of claim 46, wherein communication connectivity to the pre-determined subscriber is provided by the subscriber's service provider.

### Claim 48

A method for providing information about or access to a subscriber or data, the method comprising the steps of:
associating contact information for a subscriber or data with a key and providing the contact information linked to the key at a first location;
associating the key with at least one context characterizing the subscriber or data and providing the key linked to the at least one context at a second location;
receiving a request for communication connectivity to a pre-determined subscriber, the request including at least one pre-determined context associated with the pre-determined subscriber;
locating the pre-determined context at the second location;
linking the key with the contact information for the subscriber or data at the first location;
providing information about or access to the subscriber or data.

### Claim 49 (depends on 48)

The method of claim 48, wherein the information about or access to the subscriber or data is provided without revealing the contact information or billing information of the subscriber or data.

### Claim 50 (depends on 48)

The method of claim 48, wherein, when the pre-determined context includes at least one predetermined routing key, the information about or access to the subscriber or data is not provided unless the pre-determined context located includes the at least one predetermined routing key.

### Claim 51 (depends on 50)

The method of claim 50, wherein the subscriber can select whether or not to employ the at least one predetermined routing key, and can select an identity of the at least one predetermined routing key.

### Claim 52 (depends on 48)

The method of claim 48, wherein a fee is charged to a caller's service provider upon the providing, to the caller, of information about or access to the subscriber or data.

### Claim 53 (depends on 48)

The method of claim 48, wherein a fee is charged to the subscriber upon the providing of information about or access to the subscriber or data.

### Claim 54 (depends on 48)

The method of claim 48, wherein information about or access to the subscriber or data is provided without revealing the contact information of the subscriber or data outside the subscriber's service provider.

### Claim 55 (depends on 48)

The method of claim 48, wherein the first location is within a service provider of the subscriber or data.

### Claim 56 (depends on 48)

The method of claim 48, wherein the second location is within a directory assistance system or directory service.

### Claim 57 (depends on 48)

The method of claim 48, wherein locating the pre-determined context at the second location is performed by the service provider of the subscriber or data.

### Claim 58 (depends on 48)

The method of claim 48, wherein providing information about or access to the subscriber or data is performed by the service provider of the subscriber or data.

### Claim 59 (depends on 48)

The method of claim 48, wherein linking the key with the contact information of the subscriber or data is performed by the service provider of the subscriber or data.

### Claim 60 (depends on 48)

The method of claim 48, further comprising, after locating the predetermined context at the second location, the step of providing context-based information to a requester for requestor selection of the context-based information associated with the pre-determined subscriber to thereby narrow a search to the pre-determined subscriber.

### Claim 61 (depends on 60)

The method of claim 60, wherein providing context-based information to the requestor does not reveal the contact information of the pre-determined subscriber.

### Claim 62 (depends on 48)

The method of claim 48, wherein associating contact information for a subscriber or data with a key occurs at the first location.

### Claim 63 (depends on 48)

The method of claim 48, wherein associating the key with at least one context characterizing the subscriber or data occurs at the first location.
