# US 2010/0303062 A1 · IP telephone and method for controlling supplementary services

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

- Number: US 2010/0303062 A1
- Document ID: US20100303062A1
- Status: Published application
- Kind: A1
- Application number: 12/805,590
- Filed: 2010-08-06
- Published: 2010-12-02
- Earliest claimed: 2008-02-08
- Assignees: Fujitsu Limited
- Inventors: Masahide Noda; Kazuki Matsui; Satoshi Okuyama; Masahiko Murakami
- Web page: https://patentgrep.com/patent/US20100303062A1

## CPC

- H04M 1/2535: {adapted for voice communication over an Internet Protocol [IP] network (Voice over Internet Protocol (VoIP) network equipment and services H04M7/006; implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP] H04L69/16)}
- H04M 1/57: Arrangements for indicating or recording the number of the calling subscriber at the called subscriber's set (at the operator set in a manual exchange H04M5/20)
- H04M: TELEPHONIC COMMUNICATION (circuits for controlling other apparatus via a telephone cable and not involving telephone switching apparatus G08)

## Abstract

A request destination management table that stores therein a service ID uniquely identifying a service being interrelated with a request destination to which execution of a service is requested and a report destination management table that stores therein a call ID uniquely identifying a call being interrelated with a report destination of a call state transition report indicative of state transition of the call are provided. An IP telephone receives a request for a supplementary service, obtains a request destination corresponding to a service ID of the supplementary service from the request destination management table, and transfers the request for the supplementary service to the request destination. The IP telephone receives a call state transition report, obtains a report destination corresponding to a call ID of the call state transition report from the report destination management table, and transfers the call state transition report to the report destination.

## Claims

### Claim 1

An IP telephone comprising:
a user interface that receives a request of a user for execution of a service;
a service extension unit that receives a request for execution of a supplementary service from the user interface and executes the supplementary service, the supplementary service varying according to vendor;
a request destination management storage unit that stores in a request destination management storage a service identifier uniquely indentifying a service and a request destination to which execution of the service is requested being interrelated with each other;
a report destination management storage unit that stores in a report destination management storage a call identifier uniquely identifying a call and a report destination of a call state transition report indicative of state transition of the call being interrelated with each other;
a request transfer unit that receives a request for a supplementary service from the user interface, obtains the request destination corresponding to a service identifier of the supplementary service from the request destination management storage, and transfers the request for the supplementary service to the request destination; and
a report transfer unit that receives the call state transition report, obtains the report destination corresponding to a call identifier of the call state transition report from the report destination management storage, and transfers the call state transition report to the report destination.

### Claim 2 (depends on 1)

The IP telephone according to claim 1, wherein the request transfer unit receives a request for a basic service from the user interface and, when the request is a call generation request, adds an identifier for a call to be generated to the report destination management storage and, when the request is a call release request, deletes an identifier for a call to be released from the report destination management storage.

### Claim 3 (depends on 1)

The IP telephone according to claim 1, wherein the report transfer unit receives the call state transition report and, when a report source of the call state transition report is the service extension unit and the call state transition report is a service start request report, updates the report destination management storage such that a report destination of a call identifier for a service to be started is set to the service extension unit and, when the report source of the call state transition report is the service extension unit and the call state transition report is a service completion request report, updates the report destination management storage such that a report destination of a call identifier for a service to be completed is set to the user interface.

### Claim 4 (depends on 1)

The IP telephone according to claim 1, further comprising a module management storage unit that stores in a module management storage a vendor identifier uniquely identifying a vendor, a service identifier of the vendor, and a module identifier uniquely identifying a module that executes the service being interrelated with one another.

### Claim 5 (depends on 1)

The IP telephone according to claim 1, wherein the report destination management storage unit stores in the report destination management storage a service execution status with the call identifier and the report destination being interrelated with one another, and
wherein the request transfer unit refers to the service execution status stored in the report destination management storage when a request for a service is received from the user interface and, when the service is in progress, rejects the request for the service received.

### Claim 6

A computer readable storage medium having stored therein a supplementary services control program for controlling supplementary services with a user interface receiving from a user a request for execution of a service and a service extension unit executing a supplementary service, the supplementary service varying according to vendor, the supplementary services control program causing a computer to execute a process comprising:
storing in a request destination management storage a service identifier that uniquely identifies a service and a request destination to which execution of the service is requested being interrelated with each other;
storing in a report destination management storage a call identifier that uniquely identifies a call and a report destination of a call state transition report indicative of state transition of the call being interrelated with each other;
receiving a request for a supplementary service from the user interface, obtaining the request destination corresponding to a service identifier of the supplementary service from the request destination management storage, and transferring the request for the supplementary service to the request destination; and
receiving the call state transition report, obtaining the report destination corresponding to a call identifier of the call state transition report from the report destination management storage, and transferring the call state transition report to the report destination.

### Claim 7 (depends on 6)

The computer readable storage medium according to claim 6, the process further comprising:
receiving a request for a basic service from the user interface;
adding an identifier for a call to be generated to the report destination management storage when the request is a call generation request; and
deleting an identifier for a call to be released from the report destination management storage when the request is a call release request.

### Claim 8 (depends on 6)

The computer readable storage medium according to claim 6, the process further comprising:
receiving the call state transition report;
updating the report destination management storage such that a report destination of a call identifier for a service to be started is set to the service extension unit when a report source of the call state transition report is the service extension unit and the call state transition report is a service start request report; and
updating the report destination management storage such that a report destination of a call identifier for a service to be completed is set to the user interface when the report source of the call state transition report is the service extension unit and the call state transition report is a service completion request report.

### Claim 9 (depends on 6)

The computer readable storage medium according to claim 6, the process further comprising storing in a module management storage a vendor identifier uniquely identifying a vendor, a service identifier of the vendor, and a module identifier uniquely identifying a module that executes the service being interrelated with one another.

### Claim 10 (depends on 6)

The computer readable storage medium according to claim 6, the process further comprising:
storing in the report destination management storage a service execution status with the call identifier and the report destination being interrelated with one another;
referring to the service execution status stored in the report destination management storage when a request for a service is received from the user interface; and
rejecting the request for the service received when the service is in progress.

### Claim 11

A method for controlling supplementary services with a user interface that receives from a user a request for execution of a service and a service extension unit that executes a supplementary service, the supplementary service varying according to vendor, the method for controlling supplementary services comprising:
storing in a request destination management storage a service identifier that uniquely identifies a service and a request destination to which execution of the service is requested being interrelated with each other;
storing in a report destination management storage a call identifier that uniquely identifies a call and a report destination of a call state transition report indicative of state transition of the call being interrelated with each other;
receiving a request for a supplementary service from the user interface, obtaining the report destination corresponding to a service identifier of the supplementary service from the request destination management storage, and transferring the request for the supplementary service to the request destination; and
receiving the call state transition report, obtaining the report destination corresponding to a call identifier of the call state transition report from the report destination management storage, and transferring the call state transition report to the report destination.

### Claim 12 (depends on 11)

The method according to claim 11, further comprising:
receiving a request for a basic service from the user interface;
adding an identifier for a call to be generated to the report destination management storage when the request is a call generation request; and
deleting an identifier for a call to be released from the report destination management storage when the request is a call release request.

### Claim 13 (depends on 11)

The method according to claim 11, further comprising:
receiving the call state transition report;
updating the report destination management storage such that a report destination of a call identifier for a service to be started is set to the service extension unit when a report source of the call state transition report is the service extension unit and the call state transition report is a service start request report; and
updating the report destination management storage such that a report destination of a call identifier for a service to be completed is set to the user interface when the report source of the call state transition report is the service extension unit and the call state transition report is a service completion request report.

### Claim 14 (depends on 11)

The method according to claim 11, further comprising storing in a module management storage a vendor identifier uniquely identifying a vendor, a service identifier of the vendor, and a module identifier uniquely identifying a module that executes the service being interrelated with one another.

### Claim 15 (depends on 11)

The method according to claim 11, further comprising:
storing in the report destination management storage a service execution status with the call identifier and the report destination being interrelated with one another;
referring to the service execution status stored in the report destination management storage when a request for a service is received from the user interface; and
rejecting the request for the service received when the service is in progress.
