# US 10,484,436 B2 · User device selection

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

- Number: US 10,484,436 B2
- Document ID: US10484436B2
- Status: Granted
- Kind: B2
- Application number: 16/260,283
- Filed: 2019-01-29
- Published: 2019-06-06
- Granted: 2019-11-19
- Earliest claimed: 2012-08-30
- Assignees: Verizon Patent and Licensing Inc.; Cellco Partnership
- Applicants: Verizon Patent and Licensing Inc.; Cellco Partnership
- Inventors: Priscilla Lau; Mingxing Li; Jeffrey R. Evans
- Web page: https://patentgrep.com/patent/US10484436B2

## CPC

- H04L 65/1073: Registration or de-registration
- G06F 21/00: Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06Q 30/04: Billing or invoicing
- H04L 12/6418: {Hybrid transport}
- H04L 12/66: Arrangements for connecting between networks having differing types of switching systems, e.g. gateways
- H04L 61/5007: Internet protocol [IP] addresses
- H04L 63/08: {for authentication of entities (cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32)}
- H04L 65/1104: Session initiation protocol [SIP]
- 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)
- G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR

## Abstract

A method may include receiving, at an application server, a session initiation protocol (SIP) message including a public user identifier (ID) associated a user. The public user ID corresponds to a plurality of user devices. The method also includes determining an applicable order of alerting at least one of the plurality of user devices. The method further includes identifying at least one available user device associated with the user, based on a terminal identifier (ID) associated with each at least one available user device. The method also includes selecting a user device from the at least one available user device based on the applicable order of alerting. A SIP invite message, including a terminal ID for the selected user device, is generated. The method includes sending the SIP invite message to the selected user device based on the applicable order of alerting, and receiving a response to the SIP invite message.

## Claims

### Claim 1

A method comprising:
receiving, at a device and from a user device, a message including a terminal identifier (ID) of the user device and a public user ID associated with a user of the user device;
sending, to a network device, a request for user authentication data, wherein the request includes the public user ID and the terminal ID;
authenticating the user device based on the user authentication data;
creating a registration context of the user device, wherein the registration context of the user device includes the terminal ID, the public user ID, and a registration status of the user device;
storing the registration context for the user device;
sending, to the network device, a server assignment request (SAR) message;
receiving, from the network device, a server assignment answer (SAA) message, wherein subsequent registrations from other user devices associated with the public user ID are to be directed to the device;
storing, by the device, the registration status of the user device based on a combination of the terminal ID and the public user ID, wherein the registration status includes an authentication scheme associated with the user device, and wherein storing the registration status includes:
storing the registration status and the authentication scheme locally when the terminal ID is based on a device type of the user device, and
storing the registration status and the authentication scheme at the network device when the terminal ID is unique for the user; and
sending the message including the terminal ID and the public user ID to an application server, wherein the application server is to provide a session to the user device based on the registration context of the user device.

### Claim 2 (depends on 1)

The method of claim 1, wherein the terminal ID includes at least one of the device type of the user device or an address of the user device.

### Claim 3 (depends on 1)

The method of claim 1, wherein sending the SAR message comprises:
sending an address associated with the device to the network device and indicating the device is a serving node for the user associated with the public user ID.

### Claim 4 (depends on 1)

The method of claim 1, further comprising:
storing contact information associated with the user device based on a combination of the terminal ID, the public user ID, and an address associated with the device.

### Claim 5 (depends on 1)

The method of claim 1, further comprising:
billing for a service associated with the user device based on the terminal ID.

### Claim 6 (depends on 1)

The method of claim 1, wherein the received message further includes an international mobile subscriber identity associated with the user device.

### Claim 7 (depends on 1)

The method of claim 1, wherein the received message includes a terminal ID header that identifies the terminal ID of the user device.

### Claim 8

A device comprising:
a memory to store a plurality of instructions; and
a processor configured to execute instructions in the memory to:
receive, from a user device, a message including a terminal identifier (ID) of the user device and a public user ID associated with a user of the user device;
send, to a network device, a request for user authentication data, wherein the request includes the public user ID and the terminal ID;
authenticate the user device based on the user authentication data;
create a registration context of the user device, wherein the registration context of the user device includes based on the terminal ID, the public user ID, and a registration status of the user device;
store the registration context for the user device;
send, to the network device, a server assignment request (SAR) message;
receive, from the network device, a server assignment answer (SAA) message, wherein subsequent registrations from other user devices associated with the public user ID are to be directed to the device;
store the registration status of the user device based on a combination of the terminal ID and the public user ID, wherein the registration status includes an authentication scheme associated with the user device, and wherein, when storing the registration status, the processor is configured to:
store the registration status and the authentication scheme locally when the terminal ID is based on a device type of the user device, and
store the registration status and the authentication scheme at the network device when the terminal ID is unique for the user; and
send the message including the terminal ID and the public user ID to an application server, wherein the application server is to provide a session to the user device based on the registration context of the user device.

### Claim 9 (depends on 8)

The device of claim 8, wherein the terminal ID includes at least one of the device type of the user device or an address of the user device.

### Claim 10 (depends on 8)

The device of claim 8, wherein the processor is further configured to execute instructions in the memory to:
store, at the device, contact information associated with the user device based on a combination of the terminal ID, the public user ID, and an address associated with the device.

### Claim 11 (depends on 8)

The device of claim 8, wherein the processor is further configured to execute instructions in the memory to:
bill for a service associated with the user device based on the terminal ID.

### Claim 12 (depends on 8)

The device of claim 8, wherein the message further includes an international mobile subscriber identity associated with the user device.

### Claim 13 (depends on 8)

The device of claim 8, wherein the message includes a terminal ID header that identifies the terminal ID of the user device.

### Claim 14

A non-transitory computer-readable medium including instructions, the instructions comprising:
one or more instructions that, when executed by a processor, cause the processor to:
receive, from a user device, a message including a terminal identifier (ID) of the user device and a public user ID associated with a user of the user device;
send, to a network device, a request for user authentication data, wherein the request includes the public user ID and the terminal ID;
authenticate the user device based on the user authentication data;
create a registration context of the user device, wherein the registration context of the user device includes the terminal ID, the public user ID, and
a registration status of the user device;
store the registration context for the user device;
send, to the network device, a server assignment request (SAR) message;
receive, from the network device, a server assignment answer (SAA) message, wherein subsequent registrations from other user devices associated with the public user ID are to be directed to a device associated with the processor;
store the registration status of the user device based on a combination of the terminal ID and the public user ID, wherein the registration status includes an authentication scheme associated with the user device, and wherein the one or more instructions that cause the processor to store the registration status includes one or more instructions that cause the processor to:
store the registration status and the authentication scheme locally when the terminal ID is based on a device type of the user device, and
store the registration status and the authentication scheme at the network device when the terminal ID is unique for the user; and
send the message including the terminal ID and the public user ID to an application server, wherein the application server is to provide a session to the user device based on the registration context of the user device.

### Claim 15 (depends on 14)

The non-transitory computer-readable medium of claim 14, wherein the terminal ID includes at least one of the device type of the user device or an address of the user device.

### Claim 16 (depends on 14)

The non-transitory computer-readable medium of claim 14, wherein the instructions that cause the processor to send the SAR message further comprise:
one or more instructions that, when executed by a processor, cause the processor to:
send an address of the device associated with the processor to the network device and indicate the device is a serving node for the user associated with the public user ID.

### Claim 17 (depends on 16)

The non-transitory computer-readable medium of claim 16, wherein the instructions further comprise:
one or more instructions that, when executed by a processor, cause the processor to:
store contact information associated with the user device based on a combination of the terminal ID, the public user ID, and the address of the device.

### Claim 18 (depends on 14)

The non-transitory computer-readable medium of claim 14, wherein the instructions further comprise:
one or more instructions that, when executed by a processor, cause the processor to:
bill for a service associated with the user device based on the terminal ID.

### Claim 19 (depends on 14)

The non-transitory computer-readable medium of claim 14, wherein the message further includes an international mobile subscriber identity associated with the user device.

### Claim 20 (depends on 14)

The non-transitory computer-readable medium of claim 14, wherein the message includes a terminal ID header that identifies the terminal ID of the user device.