# US 2017/0289261 A1 · Communications methods and apparatus related to web initiated sessions

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

- Number: US 2017/0289261 A1
- Document ID: US20170289261A1
- Status: Published application
- Kind: A1
- Application number: 15/623,026
- Filed: 2017-06-14
- Published: 2017-10-05
- Earliest claimed: 2013-07-05
- Assignees: Sonus Networks, Inc.
- Applicants: Sonus Networks, Inc.
- Inventors: Tolga Asveren
- Web page: https://patentgrep.com/patent/US20170289261A1

## CPC

- H04L 63/08: {for authentication of entities (cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32)}
- G06F 21/33: using certificates
- H04L 63/0823: {using certificates (cryptographic mechanisms or cryptographic arrangements for entity authentication involving certificates H04L9/3263)}
- H04L 63/123: {received data contents, e.g. message integrity}
- H04L 65/1104: Session initiation protocol [SIP]
- H04M 7/003: {Click to dial services}
- G06F 21/31: User authentication
- H04L 63/1458: {Denial of Service}
- H04L 67/14: Session management (for real-time applications in data packet communications networks H04L65/1066)
- H04M 3/523: with call distribution or queueing
- H04M 15/39: {Arrangements for preventing metering, charging or billing}
- H04M 2203/2016: Call initiation by network rather than by subscriber
- H04M 2203/6081: Service authorization mechanisms
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- H04M: TELEPHONIC COMMUNICATION (circuits for controlling other apparatus via a telephone cable and not involving telephone switching apparatus G08)

## Abstract

A client device, e.g., a smartphone including a web browser, requests a call authorization token from a web server, e.g., a web page server. The web server, acting on behalf of a company, whose web page is hosted and whose phone corresponds to the called party, screens incoming requests and decides whether or not to issue an authorization token, e.g., a signed token including an encrypted portion. The web server issues a call authorization token and communicate the issued token to the client device. The client device includes the received issued call authorization token in a signal, e.g., a SIP INVITE signal, which it generates and sends to a session border controller (SBC). The session border controller processes the received authorization token and checks the authorization token to validate the received token. The SBC establishes a communications session if the received token passes the validation check.

## Claims

### Claim 1

A method of operating a client device, the method comprising:
detecting, by the client device, user input indicating selection of a call initiation option corresponding to a web page used to initiate a call to a party;
sending, by the client device, a request for a call authorization token to a web server;
receiving, by the client device, an issued call authorization token from said web server, said call authorization token including encrypted information and authorizing a Session Border Controller to establish a call between the client device and a called party device, said encrypted information including a token number; and
sending, by the client device, a signal to initiate a call to said Session Border Controller, said signal being an invite message including information identifying the party to which said call is directed and said issued call authorization token.

### Claim 2 (depends on 1)

The method of claim 1 further comprising:
generating said token number; and
including said token number in said request for a call authorization token.

### Claim 3 (depends on 1)

The method of claim 1, wherein said token number is a random number.

### Claim 4 (depends on 3)

The method of claim 3, wherein said issued call authorization token includes only encrypted information.

### Claim 5 (depends on 3)

The method of claim 3, wherein said issued call authorization token includes at least some encrypted information and additional information, said additional information being unencrypted and being some but not all of the information used to generate the encrypted information.

### Claim 6 (depends on 5)

The method of claim 5, wherein said encrypted information is generated based on a signal from said client device.

### Claim 7 (depends on 5)

The method of claim 5, further comprising:
receiving, by the client device, a request for user input from said web server; and
wherein said signal from said client device includes a message providing information entered by a user of said client device in response to said request for user input.

### Claim 8 (depends on 7)

The method of claim 7, wherein said request for user input is a request that the user enter text corresponding to a phrase supplied by said web server.

### Claim 9

A communications device including a processor configured to control the communications device to:
detect user input indicating selection of a call initiation option corresponding to a web page used to initiate a call to a party;
send a request for a call authorization token to a web server;
receive an issued call authorization token from said web server, said call authorization token including encrypted information and authorizing a Session Border Controller to establish a call between the communications device and a called party device, said encrypted information including a token number; and
send a signal to initiate a call, said signal being an invite message including information identifying the party to which said call is directed and said issued call authorization token.

### Claim 10 (depends on 9)

The communications device of claim 9, wherein said token number is a random number.

### Claim 11 (depends on 9)

The communications device of claim 9, wherein said issued call authorization token includes at least some encrypted information and additional information, said additional information being unencrypted and being some but not all of the information used to generate the encrypted information.

### Claim 12

A method of operating a web server, the method comprising:
receiving a request for a call authorization token from a client device executing a web browser in response to user selection of an initiate call web page option presented to a user in a web page;
determining whether or not to issue a call authorization token in response to said request;
when it is determined that a call authorization token is to be issued,
i) generating, using encryption, the call authorization token, said call authorization token including a token number and authorizing a control device to establish a call between the client device and a called party device; and
ii) sending the generated call authorization token to said client device for use in establishing a call with a called party.

### Claim 13 (depends on 12)

The method of claim 12, further comprising:
prior to receiving the request for a call authorization token, transmitting a web page to a client device, said web page including a Java script providing a call initiate option which when activated by a user of said web browser triggers the web browser to send said request for a call authorization token.

### Claim 14 (depends on 12)

The method of claim 12, wherein determining whether or not to issue a call authorization token includes:
determining if said request for a call authorization token corresponds to a known customer of a business to which said web page corresponds based on information included in said request, said request including a customer identifier or an identifier identifying the client device from which said request was sent.

### Claim 15 (depends on 12)

The method of claim 12, wherein determining whether or not to issue a call authorization token includes determining to issue said call authorization token when it is determined the request for a call authorization token corresponds to the known customer of the business to which the web page corresponds.

### Claim 16 (depends on 15)

The method of claim 15, wherein determining whether or not to issue a call authorization token includes, when it is determined that the request for a call authorization token did not come from a known customer:
sending a request for user input to the client device; and
making a decision whether or not to issue the call authorization token based on user input received from said client device.

### Claim 17

A web server including a processor configured to control said web server to:
receive a request for a call authorization token from a client device executing a web browser in response to a user selection of an initiate call web page option presented to a user in a web page;
determine whether or not to issue a call authorization token in response to said request;
generate, using encryption, the call authorization token, when it is determined that a call authorization token is to be issued, said call authorization token including a token number and authorizing a control device to establish a call between the client device and a called party device; and
send the generated call authorization token to said client device for use in establishing a call with a called party.

### Claim 18 (depends on 17)

The web server of claim 17, wherein said processor is further configured to control said web server to:
transmit a web page to a client device, said web page including a JavaScript providing a call initiate option which when activated by a user of said web browser triggers the web browser to send said request for a call authorization token.

### Claim 19 (depends on 18)

The web server of claim 18, wherein to determine whether or not to issue a call authorization token includes:
determining if said request for a call authorization token corresponds to a known customer of a business to which said web page corresponds based on information included in said request, said request including a customer identifier or an identifier identifying the client device from which said request was sent.
