# US 2004/0083291 A1 · System and method for conveying terminal capability and user preferences-dependent content characteristics for content adaptation

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

- Number: US 2004/0083291 A1
- Document ID: US20040083291A1
- Status: Published application
- Kind: A1
- Application number: 10/281,872
- Filed: 2002-10-28
- Published: 2004-04-29
- Earliest claimed: 2002-10-28
- Assignees: Nokia Corporation
- Inventors: Pekka Pessi; Stephane Coulombe
- Web page: https://patentgrep.com/patent/US20040083291A1

## CPC

- H04L 65/1083: In-session procedures
- H04L 65/1104: Session initiation protocol [SIP]
- H04L 65/756: adapting media to device capabilities
- H04L 65/762: {at the source (reformatting of additional data in video distribution servers H04N21/2355)}
- H04L 65/765: {intermediate}
- H04L 67/303: Terminal profiles
- H04L 67/306: User profiles
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

A system and method for conveying content-specific characteristics related to terminal capabilities and user preferences, and adapting content for particular terminals in response to the conveyed information. A content type or other message characteristic that is recognizable by the terminal is identified, as are operational confines of the terminal by which the content type is to comply. The content type is associated with the operational confines of the terminal. The content type and associated operational confines are provided to the network server for use by the network server in delivering messages to the terminal as dictated by the operational confines.

## Claims

### Claim 1

A method for procuring operational characteristics of a terminal at a network server for use by the network server in delivering terminal-compliant messages to the terminal, comprising:
specifying at least one content type recognizable by the terminal;
specifying operational confines of the terminal by which the content type is to comply;
associating the content type with the operational confines of the terminal; and
providing the content type and associated operational confines to the network server for use by the network server in delivering messages to the terminal as dictated by the operational confines.

### Claim 2 (depends on 1)

The method of claim 1, wherein providing the content type and associated operational confines comprises transmitting the content type and associated operational confines via Session Initiation Protocol (SIP).

### Claim 3 (depends on 1)

The method of claim 1, wherein:
specifying at least one content type comprises specifying a content type in a Session Initiation Protocol (SIP) header;
specifying operational confines of the terminal comprises specifying the operational confines in an extended SIP header field;
associating the content type with the operational confines comprises correlating the extended SIP header field with the SIP header; and
providing the content type and associated operational confines to the network server comprises transmitting a message including the SIP header and extended SIP header field via SIP to the network server.

### Claim 4 (depends on 1)

The method of claim 1, wherein:
specifying at least one content type comprises specifying a content type in a first Caller Preferences and Callee Capabilities (CPCC) feature tag;
specifying operational confines of the terminal comprises specifying the operational confines in a second CPCC feature tag;
associating the content type with the operational confines comprises correlating the second CPCC feature tag with the first CPCC feature tag; and
providing the content type and associated operational confines to the network server comprises transmitting a message including the correlated first and second feature tags to the network server.

### Claim 5 (depends on 4)

The method of claim 4, further comprising mapping the correlated first and second feature tags to Session Initiation Protocol (SIP) contact parameters.

### Claim 6 (depends on 1)

The method of claim 1, wherein specifying a content type comprises specifying any one or more of an image type, video type, text type, audio type.

### Claim 7 (depends on 6)

The method of claim 6, specifying operational confines of the terminal comprises specifying at least a data size constraint by which the content type is to comply.

### Claim 8 (depends on 1)

The method of claim 1, wherein specifying a content type comprises specifying an image type, and wherein specifying operational confines of the terminal comprises specifying at least a data size constraint by which the image type is to comply.

### Claim 9 (depends on 8)

The method of claim 8, wherein specifying a data size constraint comprises specifying at least one of a minimum, maximum, range, or specified data size by which the image type is to comply.

### Claim 10 (depends on 1)

The method of claim 1, wherein specifying a content type comprises specifying an image type, and wherein specifying operational confines of the terminal comprises specifying at least a media resolution constraint by which the image type is to comply.

### Claim 11 (depends on 10)

The method of claim 10, wherein specifying a media resolution constraint comprises specifying at least one of a minimum, maximum, range, or specified resolution size by which the image type is to comply.

### Claim 12 (depends on 10)

The method of claim 10, wherein specifying a media resolution constraint comprises specifying at least a horizontal resolution and a vertical resolution by which the image type is to comply.

### Claim 13 (depends on 12)

The method of claim 12, wherein:
specifying a media horizontal resolution comprises specifying a first Caller Preferences and Callee Capabilities (CPCC) feature tag specifying a number of horizontal pixels; and
specifying a media vertical resolution comprises specifying a second CPCC feature tag specifying a number of vertical pixels.

### Claim 14 (depends on 12)

The method of claim 12, wherein:
specifying a media horizontal resolution comprises specifying a first extended Session Initiation Protocol (SIP) header field specifying a number of horizontal pixels; and
specifying a media vertical resolution comprises specifying a second extended SIP header field specifying a number of vertical pixels.

### Claim 15 (depends on 1)

The method of claim 1, wherein specifying a content type comprises specifying an image type, and wherein specifying operational confines of the terminal comprises specifying at least a data size constraint and a media resolution constraint by which the image type is to comply.

### Claim 16 (depends on 1)

The method of claim 1, wherein:
specifying at least one content type comprises specifying a plurality of image types; and
wherein specifying operational confines of the terminal comprises specifying at least one of a data size constraint and a media resolution constraint for which each of the plurality of image types is to comply.

### Claim 17 (depends on 1)

The method of claim 1, wherein specifying a content type comprises specifying an audio type, and wherein specifying operational confines of the terminal comprises specifying one or more of a number of audio channels and a sampling rate by which the audio type is to comply.

### Claim 18 (depends on 1)

The method of claim 1, wherein specifying a content type comprises specifying an video type, and wherein specifying operational confines of the terminal comprises specifying at least a frame rate by which the video type is to comply.

### Claim 19 (depends on 1)

The method of claim 1, wherein specifying a content type comprises specifying an video type, and wherein specifying operational confines of the terminal comprises specifying at least a media resolution by which the video type is to comply.

### Claim 20 (depends on 1)

The method of claim 1, wherein specifying a content type comprises specifying a text type, and wherein specifying operational confines of the terminal comprises specifying one or more of a number of character sets by which the text type is to comply.

### Claim 21 (depends on 1)

The method of claim 1, wherein specifying operational confines of the terminal comprises specifying a maximum message body data size to be received at the terminal.

### Claim 22 (depends on 1)

The method of claim 1, wherein providing the content type and associated operation confines comprises providing the content type and associated operation confines in connection with at least one of a terminal registration process for messaging services and a terminal subscription process for presence services.

### Claim 23 (depends on 1)

The method of claim 1, wherein specifying operational confines comprises specifying technical capabilities of the terminal.

### Claim 24 (depends on 1)

The method of claim 1, wherein specifying operational confines comprises specifying user-defined terminal configuration parameters.

### Claim 25

A method for procuring operational characteristics of a terminal at a network server for use by the network server in delivering terminal-compliant messages to the terminal, comprising:
specifying at least one content type acceptable by the terminal via an accept-type header field of a registration or subscription message;
specifying rules pertaining to the content type via an extension to the accept-type header field, wherein the rules establish terminal-specific conditions in which the content type will be accepted at the terminal; and
sending the registration or subscription message to the network server for use in delivering the terminal-compliant messages to the terminal as mandated by the rules.

### Claim 26 (depends on 25)

The method of claim 25, wherein the accept-type header field comprises an Accept header field of a Session Initiation Protocol (SIP) message, and wherein sending the registration or subscription message comprises transmitting the message via SIP.

### Claim 27 (depends on 25)

The method of claim 25, wherein the content type comprises a message coding type and the accept-type header field comprises an Accept-encoding header field of a Session Initiation Protocol (SIP) message, and wherein sending the registration or subscription message comprises transmitting the message via SIP.

### Claim 28 (depends on 27)

The method of claim 27, wherein the rules comprise an acceptable message body length for messages delivered to the terminal.

### Claim 29

A method for procuring operational characteristics of a terminal at a network server for use by the network server in delivering terminal-compliant messages to the terminal, comprising:
specifying at least one content type acceptable by the terminal using Caller Preferences and Callee Capabilities (CPCC) in connection with a registration or subscription message;
specifying rules pertaining to the content type via media feature tags, wherein the rules establish terminal-specific conditions in which the content type will be accepted at the terminal; and
sending the registration or subscription message, with the rules expressed by way of the CPCC, to the network server for use in delivering the terminal-compliant messages to the terminal as mandated by the rules.

### Claim 30

A method for preparing message content for use on a terminal, comprising:
providing terminal-related information to at least one network element involved in communications with the terminal, wherein the terminal-related information comprises one or more content types accepted by the terminal, and operational limits of the terminal by which the content types are to comply;
receiving at least one message targeted for the terminal at the network element; and
adapting content associated with the received message for use on the terminal, based on the terminal-related information.

### Claim 31 (depends on 30)

The method of claim 30, wherein the content type comprises an accept content type, wherein the operational limits comprise a maximum message body size for the received message, and wherein adapting content comprises reducing a bit size of the received message body to conform to the maximum message body size.

### Claim 32 (depends on 31)

The method of claim 31, wherein reducing the bit size of the received message body comprises at least one of discarding at least a portion of the received message, utilizing content indirection by storing at least a portion of the received message and supplying an content retrieval address for the stored portion, converting a format of at least a portion of the received message to another format, and modifying media characteristics of at least a portion of the received message.

### Claim 33 (depends on 30)

The method of claim 30, wherein:
the operational limits comprise a maximum data length for content associated with the content type; and
adapting content comprises reducing a bit size of the content to conform to the maximum data length.

### Claim 34 (depends on 33)

The method of claim 33, wherein reducing the bit size of the content comprises at least one of discarding at least a portion of the received message, converting a format of at least a portion of the content to another format, modifying media characteristics of at least a portion of the content, and modifying a presentation layout of at least a portion of the content.

### Claim 35 (depends on 30)

The method of claim 30, wherein adapting content comprises employing content indirection by storing at least a portion of the content, and providing a content retrieval address at which the terminal can retrieve the stored portion of the content, based on the provided operational limits of the terminal.

### Claim 36 (depends on 30)

The method of claim 30, wherein adapting content comprises converting the digital format of the content to another digital format based on the provided operational limits of the terminal.

### Claim 37 (depends on 30)

The method of claim 30, wherein adapting content comprises modifying media characteristics of the content based on the provided operational limits of the terminal.

### Claim 38 (depends on 30)

The method of claim 30, wherein adapting content comprises modifying a presentation layout of the content based on the provided operational limits of the terminal.

### Claim 39 (depends on 30)

The method of claim 30, wherein adapting content comprises modifying a digital size of the received message based on the provided operational limits of the terminal.

### Claim 40 (depends on 30)

The method of claim 30, wherein providing terminal-related information to the network element comprises transmitting at least one request message having a header and one or more associated header fields, and incorporating the terminal-related information into header extensions associated with the header fields.

### Claim 41 (depends on 40)

The method of claim 40, wherein the request message comprises a Session Initiation Protocol (SIP) message, and wherein the header extensions conform to a Multipurpose Internet Mail Extensions (MIME) header format.

### Claim 42 (depends on 40)

The method of claim 40, wherein the request message comprises a Hypertext Transfer Protocol (HTTP) message, and wherein the header extensions conform to a Multipurpose Internet Mail Extensions (MIME) header format.

### Claim 43 (depends on 30)

The method of claim 30, wherein providing terminal-related information to the network element comprises transmitting the terminal-related information using Caller Preferences and Callee Capabilities (CPCC) feature tags.

### Claim 44 (depends on 30)

The method of claim 30, wherein the network element comprises a network registrar, and wherein the method further comprises registering the terminal with the network registrar and providing the terminal-related information in connection with registering the terminal with the network registrar.

### Claim 45 (depends on 30)

The method of claim 30, wherein the network element comprises a presence server, and wherein the method further comprises subscribing the terminal with the presence server and providing the terminal-related information in connection with subscribing the terminal with the presence server.

### Claim 46 (depends on 30)

The method of claim 30, further comprising storing the terminal-related information at the network element for use in adapting content associated with subsequently-received messages received at the network element and targeted for the terminal.

### Claim 47 (depends on 30)

The method of claim 30, further comprising defining conflict rules where two or more of the operational limits associated with the terminal-related information are inconsistent, and wherein adapting content associated with the received message based on the terminal-related information comprises adapting the content according to the defined conflict rules.

### Claim 48

A system for delivering digital content over a network, comprising:
a network server system coupled to receive messages targeted for terminals via the network;
a plurality of terminals coupled to the network, wherein each of the terminals is configured to provide its corresponding terminal-dependent information to the network server system via Session Initiation Protocol (SIP) headers, wherein the terminal-dependent information comprises one or more message characteristics accepted by the terminal, and operational limits specific to the terminal by which the message characteristics are to comply; and
wherein the network server system is configured to receive the SIP headers, and to adapt the content associated with the received messages for each of the terminals based on at least the operational limits specific to the terminal.

### Claim 49 (depends on 48)

The system as in claim 48, wherein the network server system comprises at least one of a SIP registrar and a presence server to receive the terminal-dependent information.

### Claim 50 (depends on 48)

The system as in claim 48, wherein the network server comprises a SIP proxy for receiving the messages targeted for the terminals, and a SIP registrar configured to store the terminal-dependent information for a plurality of the terminals coupled to the network.

### Claim 51 (depends on 48)

The system as in claim 48, wherein the terminals comprise one or more of a landline computing system and a wireless communications device.

### Claim 52

A system for delivering digital content over a network, comprising:
a network server system coupled to receive messages targeted for terminals via the network;
a plurality of terminals coupled to the network, wherein each of the terminals is configured to provide its corresponding terminal-dependent information to the network server system via Caller Preferences and Callee Capabilities (CPCC) feature tags, wherein the terminal-dependent information comprises one or more message characteristics accepted by the terminal, and operational limits specific to the terminal by which the message characteristics are to comply; and
wherein the network server system is configured to receive the CPCC feature tags, and to adapt the content associated with the received messages for each of the terminals based on at least the operational limits specific to the terminal.

### Claim 53 (depends on 52)

The system as in claim 52, wherein:
each of the terminals is further configured to selectively provide at least some of its corresponding terminal-dependent information to the network server system via Session Initiation Protocol (SIP) headers; and
the network server system is configured to receive the CPCC feature tags and the SIP headers, and to adapt the content associated with the received messages for each of the terminals based on at least the operational limits specific to the terminal.
