SIP device-level call/session/service management

Patent metadata

Field	Value
Publication number	US-9350769-B2
Application number	US-201113045479-A
Country	US
Kind code	B2
Filing date	Mar 10, 2011
Priority date	Mar 10, 2011
Publication date	May 24, 2016
Grant date	May 24, 2016

Abstract

Systems, methods, and computer readable media for session initiation protocol (SIP) device-level call/session/service management are disclosed. According to one aspect, a system for SIP device-level management includes a SIP service node that makes available to a user the unique device identifier of a SIP device, where the SIP device is one of multiple devices that register using the same SIP identity, and that allows the user to use the unique device identifier to manage calls, sessions, or services on a SIP device-level basis, which may include performing screening, routing, or logging operations. In one embodiment, the SIP service node is configured to receive SIP device-level management rules for managing SIP calls, sessions, or services on a SIP device-level basis and to use the rules to manage calls, sessions, or services on a SIP device-level basis.

First claim

What is claimed is:

1. A system, comprising:
a session initiation protocol (SIP) service node having a processor and a memory coupled to the processor, the memory having program instructions stored thereon that, upon execution by the processor, cause the SIP service node to:
associate each of a plurality of SIP devices with a different SIP instance identifier, wherein each of the plurality of the SIP devices registers with the SIP service node using the same SIP Uniform Resource Identifier (URI) such that any of the plurality of SIP devices uses the same SIP URI but the SIP URI does not include any of the different SIP instance identifiers, wherein the different SIP instance identifiers are values used as contact header field parameters in SIP requests distinctly or separately from the SIP URI, and wherein each of the different SIP instance identifiers is associated with a corresponding user-defined nickname;
use the different SIP instance identifiers to manage calls, sessions, or services on a SIP device-level basis for any of the plurality of SIP devices based on SIP device-level management rules, wherein the SIP device-level management rules refer to the user-defined nicknames, wherein a SIP device-level management rule identifies at least one of the plurality of SIP devices to which the rule is to be applied using a corresponding one of the plurality of SIP instance identifiers;
detect signaling related to a call, session, or service that is associated with at least one of the plurality of SIP devices that register with the SIP service node using the same SIP URI;
determine whether the SIP device-level management rule applies to the at least one SIP device; and
in response to a determination that the SIP device-level management rule applies to the at least one SIP device, apply the rule to the call, session, or service with respect to the at least one SIP device using at least one SIP instance identifiers associated with the at least one SIP device.

2. The system of claim 1 , wherein using the different SIP instance identifiers includes logging a given one of the plurality of SIP device's activity.

3. The system of claim 1 , wherein the SIP device-level management rule is received from a user.

4. The system of claim 1 , wherein the program instructions, upon execution by the processor, further cause the SIP service node to:
determine whether signaling related to a call, session, or service is associated with at least one of the plurality of SIP devices that register with the SIP service node using the same SIP URI; and
upon a determination that the signaling is associated with the at least one of the plurality of SIP devices that register with the SIP node using the same SIP URI, perform, using at least one SIP instance identifier associated with the at least one SIP device, at least one of: a screening operation, a routing operation, or a logging operation.

5. The system of claim 1 , wherein managing calls, sessions, or services on a SIP device-level basis for the plurality of SIP devices includes using the user-defined nicknames.

6. The system of claim 5 , wherein receiving the configuration information occurs during a registration process for registering each of the plurality of SIP devices to the SIP service node.

7. The system of claim 5 , wherein to receive the configuration information, the program instructions, upon execution by the processor, further cause the SIP service node to:
communicate with each of the plurality of SIP devices;
prompt a user to enter a nickname for each of the plurality of SIP devices;
receive from the user a nickname for each of the plurality of SIP devices; and
store an association between a SIP instance identifier and the nickname for each of the plurality of SIP devices.

8. The system of claim 7 , wherein to communicate with each of the plurality of SIP devices, the program instructions, upon execution by the processor, further cause the SIP service node to:
cause two or more of the plurality of SIP devices to generate an alert, detect that one of the two or more of the plurality of SIP devices has been answered by a user, and determine the SIP instance identifier of the one of the two or more of the plurality of SIP devices that has been answered by the user;
select one of the plurality of SIP devices and causing the selected SIP device to generate an alert; or
detect that a user has called a telephone number for configuring a SIP device and determining the SIP instance identifier of the SIP device that was used to make the call.

9. The system of claim 7 , wherein the program instructions, upon execution by the processor, further cause the SIP service node to indicate to the user the SIP instance identifier of the SIP device to which the nickname will apply.

10. The system of claim 1 , wherein the program instructions, upon execution by the processor, further cause the SIP service node to provide the user-defined nickname associated with one of the plurality of SIP devices to another party in a call with the one of the plurality of SIP devices.

11. A method for session initiation protocol (SIP) device-level management, the method comprising:
at a SIP service node:
associating each of a plurality of SIP devices with a different SIP instance identifier, wherein each of the plurality of the SIP devices registers with the SIP service node using the same SIP identity such that any of the plurality of SIP devices uses the same SIP identity but the SIP identity does not include any of the different SIP instance identifiers, wherein each of the different SIP instance identifiers is a value used as a contact header field parameter in a SIP message distinctly or separately from the SIP identity, and wherein each SIP instance identifier is associated with a user-defined nickname for a corresponding SIP device;
using the different SIP instance identifiers to manage calls, sessions, or services on a SIP device-level basis for any of the plurality of SIP devices based on SIP device-level management rules, wherein the SIP device-level management rules refer to the user-defined nicknames, wherein a SIP device-level management rule identifies at least one of the plurality of SIP devices to which the rule is to be applied using a corresponding one of the plurality of SIP instance identifiers;
detecting signaling related to a call, session, or service that is associated with at least one of the plurality of SIP devices that register with the SIP service node using the same SIP URI;
determining whether the SIP device-level management rule applies to the at least one SIP device; and
in response to a determination that the SIP device-level management rule applies to the at least one SIP device, applying the rule to the call, session, or service with respect to the at least one SIP device using at least one SIP instance identifiers associated with the at least one SIP device.

12. The method of claim 11 , wherein using the different SIP instance identifiers to manage calls, sessions, or services on a SIP device-level basis includes logging SIP device activity.

13. The method of claim 11 , wherein receiving the SIP device-level management rule comprises receiving the SIP device-level management rule from a user.

14. The method of claim 11 , wherein using the rule to manage calls on a SIP device-level basis includes:
determining whether the signaling related to a call, session or service is associated with at least one of the plurality of SIP devices that register using the same SIP identity; and
upon a determination that signaling related to a call, session, or service is associated with at least one

Assignees

• Smith Joan
• Lindsay Brian
• Sylvain Dany
• Genband Us Llc

Inventors

• Smith Joan
• Lindsay Brian
• Sylvain Dany

Classifications

• H04L65/1073 Primary

  Registration or de-registration · CPC title

• H04L65/1006

  Electricity · mapped topic

• H04L65/1104

  Session initiation protocol [SIP] · CPC title