# US 7,412,522 B2 · System and method for facilitating communication using presence and communication services

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

- Number: US 7,412,522 B2
- Document ID: US7412522B2
- Status: Granted
- Kind: B2
- Application number: 10/631,789
- Filed: 2003-08-01
- Published: 2004-02-26
- Granted: 2008-08-12
- Earliest claimed: 2002-08-12
- Assignees: Mitel Networks Corporation
- Inventors: Ramiro Liscano; Natalia Balaba
- Web page: https://patentgrep.com/patent/US7412522B2

## CPC

- H04L 67/54: Presence management, e.g. monitoring or registration for receipt of user log-on information, or the connection status of the users
- H04L 69/329: in the application layer [OSI layer 7]
- H04M 7/00: Arrangements for interconnection between switching centres
- H04L 51/04: Real-time or near real-time messaging, e.g. instant messaging [IM]
- H04M 3/42059: {Making use of the calling party identifier}
- H04M 3/42093: {Notifying the calling party of information on the called or connected party}
- H04M 3/42365: {Presence services providing information on the willingness to communicate or the ability to communicate in terms of media capability or network connectivity}
- H04M 2203/2066: Call type detection of indication, e.g. voice or fax, mobile of fixed, PSTN or IP
- H04M 2203/4536: Voicemail combined with text-based messaging
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- H04M: TELEPHONIC COMMUNICATION (circuits for controlling other apparatus via a telephone cable and not involving telephone switching apparatus G08)

## Abstract

A method for facilitating communication with a user. The method comprises the steps of: receiving contact information for the user, from a presence service; checking to determine if a particular communication service is supported by the user; checking to determine if the contact address of the user is accessible; launching at least one of an appropriate helper application and objects; and initiating communication with the user through the particular communication service.

## Claims

### Claim 1

A method for facilitating communication with a user, the method comprising the steps of:
receiving contact information for said user, from a presence service, said contact information comprising a contact address of the user;
checking to determine if a particular communication service is supported by said user said particular communication service associated with said contact address;
checking to determine if the contact address of the user is accessible;
launching at least one of a helper application that assists with said particular communication service and an object that supports said particular communication service, in response to said contact address of the user being accessible; and
initiating communication with the user through the particular communication service.

### Claim 2 (depends on 1)

A method as claimed in claim 1, wherein said step of checking to determine if a particular communication service is supported comprises checking a service look-up table.

### Claim 3 (depends on 2)

A method as claimed in claim 2, wherein said step of checking said service look-up table includes determining if domain information in a service url of the user is accessible.

### Claim 4 (depends on 2)

A method as claimed in claim 2, wherein said step of checking to determine if the contact address of the user is accessible is based on an address-family of the user.

### Claim 5 (depends on 2)

A method as claimed in claim 2 further comprising the step of receiving availability information of the user from a presence service, prior to the step of receiving contact information.

### Claim 6 (depends on 2)

A method as claimed in claim 2 further comprising the step of projecting availability information to the presence service, prior to the step of receiving availability information of the user.

### Claim 7 (depends on 3)

A method as claimed in claim 3, wherein said step of checking to determine if the contact address of the user is accessible is based on an address-family of the user.

### Claim 8 (depends on 3)

A method as claimed in claim 3 further comprising the step of receiving availability information of the user from a presence service, prior to the step of receiving contact information.

### Claim 9 (depends on 3)

A method as claimed in claim 3 further comprising the step of projecting availability information to the presence service, prior to the step of receiving availability information of the user.

### Claim 10 (depends on 1)

A method as claimed in claim 1, wherein said step of checking to determine if the contact address of the user is accessible is based on an address-family of the user.

### Claim 11 (depends on 10)

A method as claimed in claim 10 further comprising the step of receiving availability information of the user from a presence service, prior to the step of receiving contact information.

### Claim 12 (depends on 10)

A method as claimed in claim 10 further comprising the step of projecting availability information to the presence service, prior to the step of receiving availability information of the user.

### Claim 13 (depends on 1)

A method as claimed in claim 1 further comprising the step of receiving availability information of the user from said presence service, prior to the step of receiving contact information.

### Claim 14 (depends on 13)

A method as claimed in claim 13 further comprising the step of projecting availability information to the presence service, prior to the step of receiving availability information of the user.

### Claim 15 (depends on 1)

A method as claimed in claim 1 further comprising the step of projecting availability information to the presence service, prior to the step of receiving availability information of the user.

### Claim 16

A method for facilitating communication with a presentity, comprising the steps of:
projecting a subscription request to a presence service for determining the availability of the presentity;
receiving a notification message from the presence service in response to said subscription request, said notification message comprising a role tags for identifying a role that the presentity is in and a key tag for identifying the availability of the presentity for the subscription request;
receiving a notification of availability of the presentity if said role tag is indicative that the presentity is in a role where notifications of availability may be received, and said key tag is indicative that the presentity is available for the subscription request; and,
responsive to said notification of availability being indicative of the presentity being available,
checking to determine if a particular communication service is supported by the presentity;
checking network accessibility of the presentity;
launching at least one of a helper application that assists with said particular communication service and an object that supports said particular communication service, in response to said network accessibility of the presentity being accessible; and
initiating communication with the presentity through the particular communication service.

### Claim 17 (depends on 16)

A method as claimed in claim 16, wherein said step of checking to determine if a particular communication service is supported comprises checking a service look-up table.

### Claim 18 (depends on 17)

A method as claimed in claim 17, wherein said step of checking said service look-up table includes determining if domain information of the presentity is accessible.

### Claim 19 (depends on 17)

A method as claimed in claim 17, wherein the step of checking network accessibility of the presentity is based on an address-family of the user.

### Claim 20 (depends on 17)

A method as claimed in claim 17 further comprising the step of projecting availability information to the presence service, prior to the step of projecting a subscription request.

### Claim 21 (depends on 18)

A method as claimed in claim 18, wherein the step of checking network accessibility of the presentity is based on an address-family of the user.

### Claim 22 (depends on 18)

A method as claimed in claim 18 further comprising the step of projecting availability information to the presence service, prior to the step of projecting a subscription request.

### Claim 23 (depends on 16)

A method as claimed in claim 16, wherein the step of checking to determine if the contact address of the presentity is accessible is based on an address-family of the user.

### Claim 24 (depends on 23)

A method as claimed in claim 23 further comprising the step of projecting availability information to the presence service, prior to the step of projecting a subscription request.

### Claim 25 (depends on 16)

A method as claimed in claim 16 further comprising the step of projecting availability information to the presence service, prior to the step of projecting a subscription request.

### Claim 26

A system for facilitating communication with a presentity, comprising:
a presentity presence client;
a watcher presence client for projecting a subscription request;
a presence server connected to the presentity presence client and the watcher presence client, said presence server for receiving the subscription request and for replying to said watcher presence client to identify the availability of the presentity for the subscription request; and
a communication service separate from said presence server and connected to said watcher presence client and said presentity presence client,
wherein said watcher presence client is operable to launch at least one of an helper application that assists with said particular communication service and an object that supports said particular communication service, said watcher presence client further operable to initiate communication with the presentity through the particular communication service.

### Claim 27 (depends on 26)

A system for initiating communication as claimed in claim 26 wherein said presentity comprises a presentity resource.

### Claim 28 (depends on 26)

A system for initiating communication as claimed in claim 26, wherein said presence server comprises a directory service for storing a data record in association with a plurality of users.

### Claim 29 (depends on 28)

A system for initiating communication as claimed in claim 28, wherein said presence server further comprises a user agent for maintaining information about the availability of the presentity, said presence server enabled to determine if the presentity is available.
