IP Library Granted Patent US 7,822,035
Granted Patent B2
US 7,822,035 · App. 11/715,209 · Granted Oct 26, 2010

Use of communication service identifiers

View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 7,822,035
App. No.
11/715,209
Granted
Oct 26, 2010
Kind
B2
Abstract

Disclosed is a method in an application server. A request for initiating a communication session is received, and responsive to the request including a first service identifier pertaining to a service not supported by the application server, the first service identifier is removed from the request. A response to the request is received, and responsive to having removed the first service identifier from the request and the response including a second service identifier pertaining to the same service as the first service identifier, the second service identifier is removed from the response.

Claims (41)

1. A method comprising:

receiving, at an application server, a request, from an originating user equipment, for initiating a communication session,

responsive to the request comprising a first service identifier pertaining to a service not supported by the application server, removing the first service identifier from the request,

forwarding the request having the first service identifier removed to a terminating user equipment,

receiving, from the terminating user equipment, a response to the request, and

responsive to having removed the first service identifier from the request and the response comprising a second service identifier pertaining to the same service as the first service identifier, removing the second service identifier from the response.

2. A method according to claim 1 , wherein the first service identifier is a service identifier of a requested service and a second service identifier is a service identifier of a supported service.

3. A method according to claim 1 , further comprising maintaining the first and second service identifiers comprised in the request and response otherwise unmodified.

4. A method according to claim 1 , further comprising

responsive to the request comprising a service identifier pertaining to an unallowed service, removing the first service identifier pertaining to the unallowed service from the request.

5. A method according to claim 1 , further comprising

responsive to the request comprising a set of one or more service identifiers, maintaining unmodified the received set of one or more identifiers comprised in the request.

6. A method according to claim 1 , wherein said first service identifier resides in a first header and said second service identifier resides in a second header.

7. A method according to claim 6 , further comprising processing the request and response such that:

if the first header comprises a service identifier for a service which is supported by the application server, the request is forwarded with said service identifier in the first header, and the received second service identifier, if any, in the second header of the associated response is forwarded unmodified,

if the first header comprises a service identifier for a service which is not supported by the application server, the request is forwarded without a service identifier in the first header, and the corresponding second service identifier, if present, is removed from the second header of the associated response and the response is forwarded without said removed service identifier in the second header, and

if the first header does not comprise a service identifier for a service, the request is forwarded without a service identifier in the first header, and the received second service identifier, if any, in the second header of the associated response is forwarded unmodified.

8. A method according to claim 6 , wherein the first header is an accept contact header.

9. A method according to claim 6 , wherein the second header is one of the following: a contact header, a supported header, a user agent header, a server header, and a services header.

10. An apparatus comprising at least one processor; and at least one memory including computer program code, the at least one memory and the computer program code configured to, with the at least one processor, cause the apparatus to perform at least the following:

to receive a request, from an originating user equipment, for initiating a communication session and a response to the request, from a terminating user equipment,

to remove, responsive to the request comprising a first service identifier pertaining to a service not supported by the apparatus, the first service identifier from the request,

to forward the request having the first service identifier removed to the terminating user equipment, and

to remove, responsive to having removed the first service identifier from the request and the response comprising a second service identifier pertaining to the same service as the first service identifier, the second service identifier from the response.

11. An apparatus according to claim 10 , wherein the first service identifier is a service identifier of a requested service and a second service identifier is a service identifier of a supported service.

12. An apparatus according to claim 10 , wherein the at least one memory and the computer program code are further configured to maintain the first and second service identifiers comprised in the request and response otherwise unmodified.

13. An apparatus according to claim 10 , the at least one memory and the computer program code are further configured to remove, responsive to the request comprising a service identifier pertaining to an unallowed service, the service identifier pertaining to the unallowed service from the request.

14. An apparatus according to claim 10 , the at least one memory and the computer program code are further configured, responsive to the request comprising a set of one or more service identifiers, to maintain unmodified the received set of one or more identifiers comprised in the request.

15. An apparatus according to claim 10 , wherein said first service identifier resides in a first header and said second service identifier resides in a second header.

16. An apparatus according to claim 15 , wherein the at least one memory and the computer program code are further configured to process the request and response such that:

if the first header comprises a service identifier for a service which is supported by the apparatus, the request is forwarded with said service identifier in the first header, and the received second service identifier, if any, in the second header of the associated response is forwarded unmodified,

if the first header comprises a service identifier for a service which is not supported by the apparatus, the request is forwarded without the service identifier in the first header, and the corresponding second service identifier, if present, is removed from the second header of the associated response and the response is forwarded without said removed second service identifier in the second header, and

if the first header does not comprise a service identifier for a service, the request is forwarded without a service identifier in the first header, and the received second service identifier, if any, in the second header of the associated response is forwarded unmodified.

17. An apparatus according to claim 15 , wherein the first header is an accept contact header.

18. An apparatus according to claim 15 , wherein the second header is one of the following: a contact header, a supported header, a user agent header, a server header, and a services header.

19. A computer-readable memory tangibly encoding a computer executable program code configured to cause a processor executing the program code to perform the method of claim 1 .

20. An apparatus comprising:

means for receiving a request, from an originating user equipment, for initiating a communication session and for receiving a response to the request, from a terminating user equipment,

means for removing, responsive to the request comprising a first service identifier pertaining to a service not supported by the apparatus, the first service identifier from the request

means for forwarding the request having the first service identifier removed to the terminating user equipment, and

means for removing, responsive to having removed the first service identifier from the request and the response comprising a second service identifier pertaining to the same service as the first service identifier, the second service identifier from the response.

Assignments (8)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jun 19, 2017
From: INVENTERGY, INC.
To: INVT SPE LLC
Reel/Frame 042885/0685 →
SECURITY INTEREST Recorded Jan 4, 2017
From: INVENTERGY GLOBAL, INC.; INVENTERGY, INC.; EON COMMUNICATION SYSTEMS, INC.; INVENTERGY HOLDING, LLC; INVENTERGY INNOVATIONS, LLC; INVENTERGY IOT, LLC; INVENTERGY LBS, LLC
To: DBD CREDIT FUNDING LLC, AS COLLATERAL AGENT
Reel/Frame 041247/0908 →
RELEASE OF SECURITY INTEREST Recorded Nov 3, 2014
From: HUDSON BAY IP OPPORTUNITIES MASTER FUND, LP, FOR ITSELF AND AS COLLATERAL AGENT FOR CERTAIN BUYERS
To: INVENTERGY, INC.
Reel/Frame 034150/0298 →
RELEASE OF SECURITY INTEREST Recorded Oct 14, 2014
From: HUDSON BAY IP OPPORTUNITIES MASTER FUND, LP
To: INVENTERGY, INC
Reel/Frame 033987/0866 →
SECURITY INTEREST Recorded Oct 1, 2014
From: INVENTERGY, INC
To: DBD CREDIT FUNDING LLC
Reel/Frame 033883/0330 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jun 20, 2014
From: NOKIA CORPORATION
To: INVENTERGY, INC.
Reel/Frame 033152/0876 →
SECURITY INTEREST Recorded Jun 20, 2014
From: INVENTERGY, INC.
To: HUDSON BAY IP OPPORTUNITIES MASTER FUND, LP, AS COLLATERAL AGENT
Reel/Frame 033205/0166 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded May 8, 2007
From: MUTIKAINEN, JARI; POIKSELKA, MIIKKA
To: NOKIA CORPORATION
Reel/Frame 019279/0589 →