# US 2013/0254302 A1 · Supporting intermediate back to back user agents between user agents and a conference focus

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

- Number: US 2013/0254302 A1
- Document ID: US20130254302A1
- Status: Published application
- Kind: A1
- Application number: 13/429,074
- Filed: 2012-03-23
- Published: 2013-09-26
- Earliest claimed: 2012-03-23
- Assignees: Avaya Inc.
- Inventors: Joel Ezell; Frank Boyle
- Web page: https://patentgrep.com/patent/US20130254302A1

## CPC

- H04L 67/141: Setup of application sessions (admission control or resource allocation in data switching networks H04L47/70)
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

A communication system, method, and components are described. Specifically, a communication system having one or more Back-to-Back User Agents (B2BUAs) therein is described. The communication system also includes an RFC 4579 conference focus. Mechanisms are described which enable User Agents (UAs) to subscribe to conference state events and create ad-hoc conferences even though the conference focus is operating in a B2BUA environment.

## Claims

### Claim 1

A method, comprising:
receiving a first message;
determining that the first message is associated with a conference focus;
in response to determining that the first message is associated with a conference focus, extracting a first Contact URI from the first message; and
generating a second message that contains the first Contact URI embedded as a contact URI parameter of the second message.

### Claim 2 (depends on 1)

The method of claim 1, wherein the first message is received at a first Back-to-Back User Agent (B2BUA) and wherein the first B2BUA generates the second message, the method further comprising:
transmitting the second message from the first B2BUA to at least one of a second B2BUA and a UA.

### Claim 3 (depends on 2)

The method of claim 2, wherein the first and second message both comprise a parameter value that indicates an association with the conference focus and wherein the first B2BUA transmits the second message to a second B2BUA, the method further comprising:
determining, by the second B2BUA, that the second message comprises the parameter value that indicates an association with the conference focus;
in response to determining that the second message is associated with the conference focus, extracting, by the second B2BUA, a second Contact URI from the second message, the second Contact URI corresponding to a Contact URI of the first B2BUA; and
generating a third message that contains the second Contact URI embedded with the first Contact URI as a contact URI parameter of the third message.

### Claim 4 (depends on 3)

The method of claim 3, wherein the third message further comprises the parameter value that indicates an association with the conference focus.

### Claim 5 (depends on 4)

The method of claim 4, wherein the contact URI parameter is at least one of encrypted and obfuscated.

### Claim 6 (depends on 1)

The method of claim 1, wherein the first Contact URI corresponds to a URI of the conference focus and wherein the contact header parameter comprises a URI parameter.

### Claim 7 (depends on 1)

The method of claim 1, wherein the conference focus operates in accordance with RFC 4579.

### Claim 8 (depends on 1)

The method of claim 1, wherein the first message is a SIP request.

### Claim 9 (depends on 1)

The method of claim 1, wherein the first message is a SIP response.

### Claim 10 (depends on 1)

A non-transitory computer-readable medium comprising processor-executable instructions that, when executed by a processor, perform the method of claim 1.

### Claim 11

A method, comprising:
receiving a message;
determining the message is an Out-of-Dialog (OOD) message and contains a Request URI parameter containing an original conference focus URI; and
in response to determining that the message is an OOD message with an original conference focus URI parameter, promoting the URI from the Request URI parameter.

### Claim 12 (depends on 11)

The method of claim 11, wherein the OOD message is at least one of a SUBSCRIBE and REFER message.

### Claim 13 (depends on 11)

The method of claim 11, wherein the URI corresponds to a Contact URI of a Back-to-Back User Agent (B2BUA) that is next closest to the conference focus.

### Claim 14 (depends on 11)

The method of claim 11, wherein the URI corresponds to a URI of the conference focus.

### Claim 15 (depends on 11)

The method of claim 11, wherein promoting the URI from the message comprises un-escaping the URI from a contact URI parameter of the message and making the URI a first level parameter.

### Claim 16 (depends on 11)

A non-transitory computer-readable medium comprising processor-executable instructions that, when executed by a processor, perform the method of claim 11.

### Claim 17

A communication system,
a communication component that is configured to analyze a received message, determine that the received message is an Out-of-Dialog (OOD) message and is associated with a conference focus, and in response thereto promote a URI from a contact URI parameter of the message.

### Claim 18 (depends on 17)

The system of claim 17, wherein the communication component comprises a User Agent (UA).

### Claim 19 (depends on 17)

The system of claim 17, wherein the communication component comprises a Back-to-Back User Agent (B2BUA).

### Claim 20 (depends on 17)

The system of claim 17, wherein the URI corresponds to a URI of the conference focus.
