Architecture and method for controlling features and services in packet-based networks

• US 7,463,620 B2
• Filed: 09/10/2002
• Issued: 12/09/2008
• Est. Priority Date: 09/10/2002
• Status: Active Grant

• Current Assignee: Valtrus Innovations Limited (f/k/a Dolya Holdco 9 Limited) (Key Patent Innovations Limited)
• Original Assignee: 3Com Corporation (HP Inc.)
• Inventors: Homeier, Michael, Tripathi, Anoop, Wang, Guanglu
• Primary Examiner(s): Chan; Wing F
• Assistant Examiner(s): Jones; Prenell P
• Application Number:
  US10/243,642
• Publication Number:
  US 20040047339A1
• Time in Patent Office: 2,282 Days
• Field of Search: 370/352, 370260-263, 370389-396, 370/401, 370/466, 370/338, 370/238, 370/522, 370/271, 370/410, 370/400, 370/328, 370/261, 370/329, 370/331, 370/535, 370/355, 370/230, 455/414.1, 455/422, 455/414, 455406-408, 455/436, 455/432, 455/418, 455/466, 455/560, 455/561, 455/412, 455/405, 455/558, 455/550, 455/411, 455/419, 455/421, 455/435, 455439-401, 455/11, 455/433, 455/420, 455/415, 455/456, 455/502, 455/426.2, 379/202.01, 379/219, 379/114.15, 379/114.2, 379/201, 379/102, 379/110, 379/88.19, 379/67.1, 379/207.15, 379/211.02, 379/188, 379/221, 379/142, 379/207, 379/88.17, 379/229, 709222-230, 709/200, 709/249, 709/52, 709/10, 709/64, 709/7, 709/1, 709/219, 709203-207, 709/217, 709/201, 709/202, 709/218, 709/245
• US Class Current: 370/352
• CPC Class Codes: H04L 41/12 Discovery or management of network topologies
• CPC Class Codes: H04L 41/5048 Automatic or semi-automatic definitions, e.g. definition templates
• CPC Class Codes: H04L 41/5058 Service discovery by the service manager
• CPC Class Codes: H04M 3/42144 by service provider
• CPC Class Codes: H04M 7/1205 where the types of switching equipement comprises PSTN/ISDN equipment and switching equipment of networks other than PSTN/ISDN, e.g. Internet Protocol networks

Abstract

Systems and methods for controlling features and services in packet-based networks are disclosed. The present application provides systems and methods that include sending a first message to a network core device, and identifying a profile from user account information stored on the network core device. The profile specifies which features and services may or may not be implemented by an end device. In the systems and methods of the present application, the profile is added to a second message that is sent from the network core device to the end device. Alternatively, a single message or multiple messages containing the profile, regardless and/or independent of any prior message sent from an end device, may be sent from the network core device to the end device. These systems and methods may also use the session initiation protocol for their communications, with the end devices being session initiation protocol phones and the network core device being a session initiation server.

Claims

1. A method for controlling features and services in packet-based networks, the method comprising the steps of:

identifying a profile from user account information stored on a network core device, wherein the network core device is a session initiation protocol server,

the profile specifying which features and services may or may not be implemented by an end device;

adding the profile to at least one message; and

sending the at least one message from the network core device to the end device, said end device using said profile to implement or not implement said features and services, wherein said end device is a session initiation protocol phone.

2. The method of claim 1 further comprising the step of implementing on the end device only the features and services allowed to be implemented by the profile of the at least one message.

3. A method for controlling features and services in packet-based networks, the method comprising the steps of:

sending a first message to a network core device from a first end device;

identifying a profile from user account information stored on the network core device, the profile specifying which features and services may or may not be implemented by a second end device;

adding the profile to a second message;

sending the second message from the network core device to the second end device, said second end device using said profile to implement or not implement said features and services, wherein said second end device is a phone.

4. The method of claim 3 further comprising the steps of adding the profile to the first message to form the second message, and using a first invite message for the first message and a second invite message for the second message.

5. The method of claim 4 further comprising the step of using invite messages that contain information for inviting the second end device to communicate with the first end device.

6. The method of claim 3 further comprising the step of using an invite message for the first message and a response message for the second message.

7. The method of claim 3 further comprising the step of implementing on the second end device only the features and services allowed to be implemented by the profile of the second message.

8. The method of claim 3 further comprising the steps of using a profile based on account information for a user of the first end device, and implementing on the second end device only the features and services allowed to be implemented by the profile of the second message.

9. The method of claim 3 further comprising the steps of using a profile based on account information for a user of the second end device, and implementing on the second end device only the features and services allowed to be implemented by the profile of the second message.

10. The method of claim 3 further comprising the steps of using a profile based on account information for users of both the first and second end devices, and implementing on the second end device only the features and services allowed to be implemented by the profile of the second message.

11. A method for controlling features and services in packet-based networks using the session initiation protocol, the method comprising the steps of:

sending a first message to a session initiation protocol server;

identifying a profile from user account information stored on the session initiation protocol server, the profile specifying which features and services may or may not be implemented by a session initiation protocol phone;

adding the profile to a second message; and

sending the second message from the session initiation protocol server to the session initiation protocol phone, said session initiation protocol phone using said profile to implement or not implement said features and services.

12. The method of claim 11 further comprising the steps of using a register message for the first message and a response message for the second message, and using the session initiation protocol phone to send the register message to the session initiation protocol server.

13. The method of claim 11 further comprising the step of implementing on the session initiation protocol phone only the features and services allowed to be implemented by the profile of the second message.

14. The method of claim 11 further comprising the steps of using a profile based on account information for a user of the session initiation protocol phone, and implementing on the session initiation protocol phone only the features and services allowed to be implemented by the profile of the second message.

15. The method of claim 11 further comprising the steps of using a first session initiation protocol phone to send the first message to the session initiation protocol server, and a second session initiation protocol phone to receive the second message from the session initiation protocol server.

16. The method of claim 15 further comprising the steps of adding the profile to the first message to form the second message, and using a first invite message for the first message and a second invite message for the second message.

17. The method of claim 16 further comprising the step of using invite messages that contain information for inviting the second session initiation protocol phone to communicate with the first session initiation protocol phone.

18. The method of claim 15 further comprising the step of using an invite message for the first message and a response message for the second message.

19. The method of claim 15 further comprising the step of implementing on the second session initiation protocol phone only the features and services allowed to be implemented by the profile of the second message.

20. The method of claim 15 further comprising the steps of using a profile based on account information for a user of the first end session initiation protocol phone, and implementing on the second session initiation protocol phone only the features and services allowed to be implemented by the profile of the second message.

21. The method of claim 15 further comprising the steps of using a profile based on account information for a user of the second session initiation protocol phone, and implementing on the second session initiation protocol phone only the features and services allowed to be implemented by the profile of the second message.

22. The method of claim 15 further comprising the steps of using a profile based on account information for users of both the first and second session initiation protocol phones, and implementing on the second session initiation protocol phone only the features and services allowed to be implemented by the profile of the second message.

23. A system for controlling features and services in packet-based networks communications, the system comprising:

an end device in communication with a network core device, wherein said end device is a session initiation protocol phone and wherein said network core device is a session initiation protocol server;

a profile identified from user account information stored on the network core device, the profile specifying which features and services may or may not be implemented by the end device; and

at least one message including the profile;

wherein the at least one message is sent from the network core device to the end device, the end device implementing only the features and services allowed to be implemented by the profile of the at least one message.

24. A system for controlling features and services in packet-based networks communications, the system comprising:

a first end device in communication with a network core device, wherein said first end device is a session initiation protocol phone;

a second end device in communication with the network core device, the second end device also in communication with the first end device via the network core device, wherein said second end device is a session initiation protocol phone;

a profile identified from user account information stored on the network core device, the profile specifying which features and services may or may not be implemented by the second end device, wherein said network core device is a session initiation protocol server; and

a first message and a second message, the second message including the profile;

wherein the first message is sent from the first end device to the network core device, the second message is sent from the network core device to the second end device, and the second end device receiving the second message implements only the features and services allowed to be implemented by the profile of the second message.

25. The system of claim 24 wherein the first message is a registration message and the second message is a response message.

26. The system of claim 24 wherein the first message is an invite message and the second message is one of a further invite message or a response message.