SESSION UPDATE USING MANAGEMENT OF CAPABILITY OF TERMINAL

• US 20100093346A1
• Filed: 11/13/2007
• Published: 04/15/2010
• Est. Priority Date: 01/08/2007
• Status: Active Grant

• Current Assignee: LG Electronics, Inc. (LG Corporation)
• Original Assignee: LG Electronics, Inc. (LG Corporation)
• Inventors: Ra, Mi-Seon, Yoon, Kyung-Ae, Kim, Hyun-Sook, Song, Jae-Seung
• Granted Patent: US 8,175,597 B2
• Time in Patent Office: Days
• US Class Current: 455/435.1
• CPC Class Codes: H04L 41/12 Discovery or management of network topologies
• CPC Class Codes: H04L 67/14 Session management for real-time applications in data packet communications networks H04L65/1066
• CPC Class Codes: H04L 67/142 Managing session states for stateless protocols; Signalling session states; State transitions; Keeping-state mechanisms
• CPC Class Codes: H04L 67/303 Terminal profiles
• CPC Class Codes: H04L 69/24 Negotiation of communication capabilities

Abstract

Management of capability information is disclosed. A server in a network acquires information about capability of a user equipment (or terminal) and manages the information in a centralized manner, to reduce signaling through a radio interface between user equipments to thus reduce a waste of radio resources.

Claims

1. A method for updating a session in a terminal, comprising:

a) performing one or more services with one or more entities;

b) transmitting information about one or more changed capabilities to a management server in order to distribute the corresponding information to the one or more entities, when one or more capabilities change; and

c) updating a session with the one or more entities by using the changed capability information.

2. The method of claim 1, further comprising, before performing step a):

transmitting information about one or more capabilities to the management server.

3. The method of claim 1, further comprising, before performing step a):

transmitting a registration message to the management server;

receiving a capability information request message from the management server; and

transmitting a capability information response message including the information about at least one or more capabilities in response to the request.

4. The method of claim 3, wherein the registration message may be an SIP-based REGISTER message, the capability information request message may be an SIP-based OPTIONS message, and the capability information response message may be an SIP-based 200 OK message.

5. The method of claim 3, wherein the registration message comprises one or more of a first parameter indicating whether or not a management function is used by the management server;

and a second parameter indicating a version of the capability information, wherein the second parameter may be a capability version.

6. The method of claim 1, wherein the transmission step b) comprises:

transmitting a notification message to the management server to notify that one or more capabilities change;

receiving a capability information request message from the management server; and

transmitting a capability information response message including the information about the one or more changed capabilities to the management server.

7. The method of claim 6, wherein the notification message may be a NOTIFY message, the capability information request message may be an OPTIONS message, and the capability information response message may be a 200 OK message.

8. The method of claim 1, wherein the transmission step b) comprises:

transmitting a capability information update message including the information about the one or more changed capabilities to the management server; and

receiving a reception success response message from the management server.

9. The method of claim 8, wherein the capability information update message may be a NOTIFY message, and the reception success response message may be a 200 OK message.

11. The method of claim 1, wherein the updating step c) comprises:

receiving a session initiation request message or a session update message from the one or more entities; and

transmitting an accept response message to the one or more entities.

12. The method of claim 11, wherein the session initiation request message may be an SIP-based INVITE message, and the accept response message may be an SIP-based 200 OK message.

13. The method of claim 1, further comprising, before the step c):

transmitting, by the management server, information about the changed capability to the one or more entities.

10. The method of clam 8, wherein the capability information update message comprises a parameter indicating a version of the information about the changed capability, or a capability version.

14. A method for managing one or more capabilities of a terminal by a server, comprising:

a) receiving one or more information about one or more changed capabilities from one or more terminals; and

b) transmitting the one or more information about the one or more changed capabilities of the one or more terminals to one or more entities connected with the one or more terminals in a session.

15. The method of claim 14, wherein the one or more entities request the server to notify about the corresponding capability information when the capability information of the terminal changes, or the one or more entities register in the server so that the server can notify about the corresponding capability information.

16. The method of claim 14, wherein the receiving step a) comprises:

receiving a notification message indicating that one or more capabilities have been changed from the one or more terminals;

transmitting capability information request message to the one or more terminals; and

receiving a capability information response message including the information about one or more changed capabilities from the one or more terminals.

17. The method of claim 16, wherein the capability information response message comprises a parameter indicating a version of the information about the changed capability, or a capability version.

18. The method of claim 16, wherein the notification message may be a NOTIFY message, the capability information request message may be an OPTIONS message, and the capability information response message may be a 200 OK message.

19. The method of claim 14, wherein the receiving step a) comprises:

receiving a capability information update message including the information about one or more changed capabilities from the one or more terminals; and

transmitting a reception success response message to the one or more terminals.

20. The method of claim 19, wherein the capability information update message may be a NOTIFY message, and the reception success response message may be an SIP-based 200 OK message.

21. The method of clam 19, wherein the capability information update message comprises a parameter indicating a version of the information about the changed capability, or a capability version.

22. A terminal comprising:

a transmitting/receiving unit; and

a controller for controlling the transmitting/receiving unit to transmit to a management server information about one or more capabilities required for performing a service with one or more entities in order to distribute the information to the one or more entities, transmit to the management server information about one or more changed capabilities, when one or more capabilities change, in order to distribute the changed information to the one or more entities, and for updating a session with the one or more entities so as to be suitable for the changed capability.

23. The terminal of claim 22, wherein the information about one or more capabilities may be transmitted by being included in a capability information response message, and the information about the one or more changed capabilities may be transmitted by being included in a capability information update message.

24. The terminal of claim 22, wherein the information about the one or more capabilities may be transmitted by being included in an SIP-based 200 OK message, and the information about one or more changed capabilities may be transmitted by being included in an SIP-based 200 OK message or a NOTIFY message.