Refreshing a session initiation protocol (SIP) session
First Claim
1. A method comprising:
- sending, using a first network device, a negotiation message to a second network device, wherein the negotiation message includes information indicating that a simple-refresh mechanism is supported by the first network device, wherein the simple-refresh mechanism is operable to refresh a Session Initiation Protocol (SIP) session using a first truncated form of an existing SIP message structure with session description protocol fields removed;
responsive to sending the negotiation message, receiving at the first network device a response message from the second network device, wherein the response message (i) includes information indicating whether the simple-refresh mechanism is supported by the second network device and (ii) is in a second truncated form of the existing SIP message structure with the session description protocol fields removed;
examining, using the first network device, the response message to determine whether the response message includes information associated with the simple-refresh mechanism;
identifying, using the first network device, information associated with the simple-refresh mechanism included in the response message; and
based on identifying the information associated with the simple-refresh mechanism included in the response message, determining that the simple-refresh mechanism is supported by the second network device.
0 Assignments
0 Petitions
Accused Products
Abstract
In one embodiment, a session is refreshed using a message that is simplified for refresh purposes. The refresh message that is used is a message used for another purpose in a protocol (e.g., SIP). For example, a reINVITE message may be used as a refresh message. If the reINVITE message is used for its intended purpose, the reINVITE message may be used to change the characteristics of a session. This reINVITE message includes an SDP and full header such that the parameters can be properly changed. However, the reINVITE message may be used to refresh a session. This may be referred to as a simple refresh message. But, the simple refresh message does not include an SDP or any other message body. The simple refresh message includes only a reduced header. This reduces time spent building and parsing the simple refresh message.
-
Citations
22 Claims
-
1. A method comprising:
-
sending, using a first network device, a negotiation message to a second network device, wherein the negotiation message includes information indicating that a simple-refresh mechanism is supported by the first network device, wherein the simple-refresh mechanism is operable to refresh a Session Initiation Protocol (SIP) session using a first truncated form of an existing SIP message structure with session description protocol fields removed; responsive to sending the negotiation message, receiving at the first network device a response message from the second network device, wherein the response message (i) includes information indicating whether the simple-refresh mechanism is supported by the second network device and (ii) is in a second truncated form of the existing SIP message structure with the session description protocol fields removed; examining, using the first network device, the response message to determine whether the response message includes information associated with the simple-refresh mechanism; identifying, using the first network device, information associated with the simple-refresh mechanism included in the response message; and based on identifying the information associated with the simple-refresh mechanism included in the response message, determining that the simple-refresh mechanism is supported by the second network device. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13)
-
-
14. An apparatus comprising:
-
at least one processor; a list of call sessions encoded in a storage medium; a session identification module including instructions encoded in a non-transitory machine-readable medium for execution by the at least one processor and operable to cause the at least one processor to perform functions including; examining the list of call sessions for extracting session identifiers associated with call sessions included in the list; and based upon extracting the session identifiers, determining call sessions that are established between an originating gateway and a terminating gateway; a session refresher unit including instructions encoded in a non-transitory machine-readable medium for execution by the at least one processor and operable to cause the at least one processor to perform functions including; determining, during establishment of a call session between an originating gateway and a terminating gateway through a session border controller, whether a simple-refresh mechanism is supported for the call session, wherein the simple-refresh mechanism is operable to refresh a Session Initiation Protocol (SIP) session using a first truncated form of an existing SIP message structure with session description protocol fields removed; and based upon determining that the simple-refresh mechanism is supported for the call session, generating a simple-refresh message; and an inactive session identifier module including instructions encoded in a non-transitory machine-readable medium for execution by the at least one processor and operable to cause the at least one processor to perform functions including; based upon sending the simple-refresh message from the session refresher unit to a session border controller for the call session, receiving a response message from the session border controller, wherein the response message is in a second truncated form of the existing SIP message structure with the session description protocol fields removed; examining the response message; and based upon examining the response message, determining whether the session is active or inactive. - View Dependent Claims (15, 16)
-
-
17. An apparatus comprising:
-
a message purpose determiner unit including instructions encoded in a non-transitory machine-readable medium for execution by at least one processor and operable to cause the at least one processor to perform functions including; receiving, from a gateway node, a simple-refresh message, wherein the simple-refresh message includes a first truncated form of an existing Session Initiation Protocol (SIP) message structure that is configured to refresh a SIP session and that has session description protocol fields removed; examining the simple-refresh message; based upon examining the simple-refresh message, determining an action that is being requested using information included in the simple-refresh message; and based upon determining that the action being requested is a simple-refresh of a call session, forwarding the simple-refresh message to a session refreshee unit; the session refreshee unit including instructions encoded in a non-transitory machine-readable medium for execution by at least one processor and operable to cause the at least one processor to perform functions including; receiving the simple-refresh message from the message purpose determiner unit; examining the simple-refresh message; based upon examining the simple-refresh message, extracting a session identifier for the call session; and using the session identifier for the call session, determining whether the call session is active or inactive; and a response generator unit including instructions encoded in a non-transitory machine-readable medium for execution by at least one processor and operable to cause the at least one processor to perform functions including; receiving information from the session refreshee unit associated with the call session, wherein the information indicates whether the call session is active or inactive; generating a response message including information indicating whether the call session is active or inactive, wherein the response message is in a second truncated form of the existing SIP message structure with the session description protocol fields removed; and sending the response message to the gateway node. - View Dependent Claims (18)
-
-
19. A method comprising:
-
receiving, at a second network device and from a first network device, a simple-refresh message, wherein the simple-refresh message includes a first truncated form of an existing Session Initiation Protocol (SIP) message structure that is configured to refresh a SIP session and that has session description protocol fields removed; examining, using the second network device, the simple-refresh message; based upon examining the simple-refresh message, determining, using the second network device, that a simple-refresh of a call session is being requested using information included in the simple-refresh message; extracting, using the second network device, a session identifier for the call session from the simple-refresh message; using the session identifier for the call session, determining, using the second network device, whether the call session is active or inactive; generating, using the second network device, a response message including information indicating whether the call session is active or inactive, wherein the response message is in a second truncated form of the existing SIP message structure with the session description protocol fields removed; and sending, using the second network device, the response message to the first network device. - View Dependent Claims (20)
-
-
21. A system comprising:
-
a first network device including instructions encoded in a non-transitory machine-readable medium for execution by at least one processor and operable to cause the at least one processor to perform functions including; sending a negotiation message to a second network device, wherein the negotiation message includes information indicating that a simple-refresh mechanism is supported by the first network device, wherein the simple-refresh mechanism is operable to refresh a Session Initiation Protocol (SIP) session using a first truncated form of an existing SIP message structure and that has session description protocol fields removed; responsive to sending the negotiation message, receiving a response message from the second network device, wherein the response message includes information indicating whether the simple-refresh mechanism is supported by the second network device; examining the response message to determine whether the response message includes information associated with the simple-refresh mechanism; identifying information associated with the simple-refresh mechanism included in the response message; and based on identifying information associated with the simple-refresh mechanism included in the response message, determining that the simple-refresh mechanism is supported by the second network device; and the second network device including instructions encoded in a non-transitory machine-readable medium for execution by at least one processor and operable to cause the at least one processor to perform functions including; receiving, from the first network device, a simple-refresh message, wherein the simple-refresh message includes a truncated form of an existing Session Initiation Protocol (SIP) message structure that is configured to refresh a SIP session; examining the simple-refresh message; based upon examining the simple-refresh message, determining that a simple-refresh of a call session is being requested using information included in the simple-refresh message; extracting a session identifier for the call session from the simple-refresh message; using the session identifier for the call session, determining whether the call session is active or inactive; generating a response message including information indicating whether the call session is active or inactive, wherein the response message is in a second truncated form of the existing SIP message structure with the session description protocol fields removed; and sending the response message to the first network device. - View Dependent Claims (22)
-
Specification