SIP-based feature control

• US 6,615,236 B2
• Filed: 11/08/1999
• Issued: 09/02/2003
• Est. Priority Date: 11/08/1999
• Status: Expired due to Fees

• Current Assignee: Verizon Patent and Licensing Incorporated (Verizon Communications Inc.)
• Original Assignee: WorldCom, Inc. (Verizon Communications Inc.)
• Inventors: Devanathan, Raghavan, Donovan, Steven R.
• Primary Examiner(s): Eng, David Y.
• Application Number:
  US09/436,793
• Publication Number:
  US 20020129093A1
• Time in Patent Office: 1,394 Days
• Field of Search: 709/203, 709/227, 709/230
• US Class Current: 709/203
• CPC Class Codes: H04L 65/1096 Supplementary features, e.g. call forwarding or call holding systems providing special services or facilities to telephony subscribers H04M3/42
• CPC Class Codes: H04L 65/1101 Session protocols
• CPC Class Codes: H04L 65/1104 Session initiation protocol [SIP]
• CPC Class Codes: H04L 69/327 in the session layer [OSI layer 5]
• CPC Class Codes: H04M 3/42314 in private branch exchanges
• CPC Class Codes: H04M 3/436 Arrangements for screening incoming calls , i.e. evaluating the characteristics of a call before deciding whether to answer it based on the calling party profile H04M3/42059; based on location H04M3/42348; based on presence H04M3/42365; diversion H04M3/54
• CPC Class Codes: H04M 7/006 Networks other than PSTN/ISDN providing telephone service, e.g. Voice over Internet Protocol (VoIP) , including next generation networks with a packet-switched transport layer H04L65/00 takes precedence; aspects not specific to the type of network H04M3/00; special services in those networks H04M3/42

Abstract

A system and method for providing an addition to the Session Initiation Protocol is disclosed. The addition is a new field header, preferably entitled “Feature”, that is added to the REGISTER message. This field would contain control information for various feature services, like the Do Not Disturb feature and other services provided by traditional PBX systems.

Claims

1. A system for providing at least one PBX type service in a Session Initiation Protocol (SIP) based network, comprising:

at least one user agent client configured to insert a feature field header into at least one SIP formatted message; and

at least one SIP server coupled to the at least one user agent client, the SIP server being programmed to process the at least one SIP formatted message, the feature field header including a feature status portion configured to program the at least one SIP server to thereby activate or deactivate the at least one PBX type service.

2. The system as recited in claim 1, wherein the at least one user agent client enables a user to initiate a session, send and receive requests from the at least one server, the at least one server receiving a request, determining where to send the request, and forwarding the request, said at least one SIP formatted message containing said feature status information sent between the at least one user agent client and the at least one server.

3. The system as recited in claim 1, wherein the at least one user agent client enables a user to initiate a session, send and receive requests from the at least one server, the at least one server receiving a request, determining where to send the request, and informing said at least one user agent client where to send the request, said at least one SIP formatted message containing said feature status information sent between the at least one user agent client and the at least one server.

4. The system as recited in claim 1, wherein the at least one SIP server is configured to provide features, and receive the at least one SIP formatted message with feature status information, the at least one SIP server implementing the features according to the feature status information contained in the received at least one SIP formatted message.

5. The system as recited in claim 1, wherein said additional field header containing said feature status information is added to a REGISTER message.

6. The system as recited in claim 1, wherein said SIP based network initiates telephony sessions.

7. The system as recited in claim 6, wherein a feature corresponding to the feature status information is call forwarding.

8. The system as recited in claim 6, wherein a feature corresponding to the feature status information is call blocking.

9. The system as recited in claim 6, wherein a feature corresponding to the feature status information is call screening.

10. A method for providing feature status information in a Session Initiation Protocol (SIP) based network, said network having at least one user agent client (UAC) which is implemented in an end client device used by a user, at least one SIP server for implementing features, and messages including at least one field header, comprising the steps of:

adding feature status information to a message from the UAC to the SIP server;

transmitting said message to the SIP server;

implementing said features according to the feature status information in said message;

indicating to the end client device what feature status changes the user wishes to make; and

creating feature status information from said indication.

11. The method as recited in claim 10, wherein said feature status information has a feature status field header.

12. The method as recited in claim 10, wherein said message with added feature status information is a REGISTER message.

13. The method as recited in claim 10, wherein said SIP based network initiates telephony sessions.

14. The method as recited in claim 10, wherein a feature corresponding to the feature status information is call forwarding.

15. The method as recited in claim 10, wherein a feature corresponding to the feature status information is call blocking.

16. The method as recited in claim 10, wherein a feature corresponding to the feature status information is call screening.

17. A system for providing feature status information in a Session Initiation Protocol (SIP) based network, said network having method messages including at least INVITE, ACK, OPTIONS, BYE, CANCEL, REGISTER, each said method message having at least one field header, comprising:

at least one user agent client for using an additional field header to add feature status information to a REGISTER message, said user agent client sending said REGISTER message to at least one SIP server;

said at least one SIP server for receiving said REGISTER message from said at least one user agent client and for implementing features according to the feature status information in said REGISTER message; and

at least one said network for transmitting messages between said at least one user agent client and said at least one SIP server.

18. The system as recited in claim 17, wherein said network initiates telephony sessions.

19. The system as recited in claim 18, wherein said features include one of call forwarding, call screening, and call blocking.