IP Library Granted Patent US 8,463,913
Granted Patent B2
US 8,463,913 · App. 12/240,381 · Granted Jun 11, 2013

System and method of responding to a request in a network environment including IMS

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 8,463,913
App. No.
12/240,381
Granted
Jun 11, 2013
Kind
B2
Abstract

In one embodiment, a scheme is disclosed for facilitating responding to a request in a network environment including IMS. A component associated with a recipient is configured to receive an incoming message from a sender, wherein the incoming message is substantially free of an indication of acceptance by the sender of a body of a particular content type. A component associated with the recipient is configured to provide an outgoing message including at least one body of the particular content type.

Claims (28)

1. A method of responding to a request in a network environment, said method comprising:

receiving at a recipient a Session Initiation Protocol (SIP) request message from a sender, said SIP request message being free of an indication of acceptance by said sender of a body of a particular content type; and

providing a SIP response message including at least one body of said particular content type to said sender, wherein an acceptance of said at least one body of said particular content type was not indicated by said sender in said SIP request message.

2. The method of responding to a request as recited in claim 1 , wherein said SIP request message is a request for an Emergency Services (ES) call session.

3. The method of responding to a request as recited in claim 1 , wherein said particular content type is application/3gpp-ims+xml.

4. The method of responding to a request as recited in claim 1 , wherein said SIP request message includes an Accept header field.

5. The method of responding to a request as recited in claim 1 , wherein said SIP request message is devoid of an Accept header field.

6. The method of responding to a request as recited in claim 1 , wherein said sender is a User Equipment (UE) device disposed in said network environment.

7. The method of responding to a request as recited in claim 1 , wherein said sender is a network node disposed in said network environment.

8. The method of responding to a request as recited in claim 1 , wherein said recipient is a network node disposed in said network environment.

9. The method of responding to a request as recited in claim 1 , wherein said recipient is a UE device disposed in said network environment.

10. The method of responding to a request as recited in claim 1 , wherein at least one of said SIP request message and said SIP response message contain a body comprising at least one XML document.

11. The method of responding to a request as recited in claim 1 , wherein said SIP response message is a SIP 380 (Alternative Service) message.

12. The method of responding to a request as recited in claim 1 , wherein said SIP request message is a SIP INVITE message.

13. An apparatus for facilitating responding to a request in a network environment, said apparatus comprising:

a component associated with a recipient configured to receive a Session Initiation Protocol (SIP) request message from a sender, said SIP request message being free of an indication of acceptance by said sender of a body of a particular content type; and

a component associated with said recipient configured to provide a SIP response message including at least one body of said particular content type to said sender, wherein an acceptance of said at least one body of said particular content type was not indicated by said sender in said SIP request message.

14. The apparatus for facilitating responding to a request as recited in claim 13 , wherein said SIP request message is a request for an Emergency Services (ES) call session.

15. The apparatus for facilitating responding to a request as recited in claim 13 , wherein said particular content type is application/3gpp-ims+xml.

16. The apparatus for facilitating responding to a request as recited in claim 13 , wherein said SIP request message includes an Accept header field.

17. The apparatus for facilitating responding to a request as recited in claim 13 , wherein said SIP request message is devoid of an Accept header field.

18. The apparatus for facilitating responding to a request as recited in claim 13 , wherein said sender is a User Equipment (UE) device disposed in said network environment.

19. The apparatus for facilitating responding to a request as recited in claim 13 , wherein said sender is a network node disposed in said network environment.

20. The apparatus for facilitating responding to a request as recited in claim 13 , wherein said recipient is a network node disposed in said network environment.

21. The apparatus for facilitating responding to a request as recited in claim 13 , wherein said recipient is a UE device disposed in said network environment.

22. The apparatus for facilitating responding to a request as recited in claim 13 , wherein at least one of said SIP request message and said SIP response message contain a body comprising at least one XML document.

23. The apparatus for facilitating responding to a request as recited in claim 13 , wherein said SIP response message is a SIP 380 (Alternative Service) message.

24. The apparatus for facilitating responding to a request as recited in claim 13 , wherein said SIP request message is a SIP INVITE message.

Assignments (9)
CORRECTIVE ASSIGNMENT TO CORRECT THE ADDED PATENT NUMBER TO REMOVE PATENT NO. 8,873,407 AT PREVIOUSLY RECORDED ON REEL 64066 FRAME 1. ASSIGNOR(S) HEREBY CONFIRMS THE NUNC PRO TUNC ASSIGNMENT EFFECTIVE DATE MARCH 20, 2023. Recorded Feb 2, 2026
From: BLACKBERRY LIMITED
To: MALIKIE INNOVATIONS LIMITED
Reel/Frame 074921/0001 →
CORRECTIVE ASSIGNMENT TO CORRECT 12817157 APPLICATION NUMBER PREVIOUSLY RECORDED AT REEL: 064015 FRAME: 0001. ASSIGNOR(S) HEREBY CONFIRMS THE ASSIGNMENT. Recorded Sep 5, 2023
From: OT PATENT ESCROW, LLC
To: MALIKIE INNOVATIONS LIMITED
Reel/Frame 064807/0001 →
CORRECTIVE ASSIGNMENT TO CORRECT THE COVER SHEET AT PAGE 50 TO REMOVE 12817157 PREVIOUSLY RECORDED ON REEL 063471 FRAME 0474. ASSIGNOR(S) HEREBY CONFIRMS THE ASSIGNMENT. Recorded Sep 5, 2023
From: BLACKBERRY LIMITED
To: OT PATENT ESCROW, LLC
Reel/Frame 064806/0669 →
NUNC PRO TUNC ASSIGNMENT Recorded Jun 19, 2023
From: BLACKBERRY LIMITED
To: MALIKIE INNOVATIONS LIMITED
Reel/Frame 064066/0001 →
NUNC PRO TUNC ASSIGNMENT Recorded Jun 16, 2023
From: OT PATENT ESCROW, LLC
To: MALIKIE INNOVATIONS LIMITED
Reel/Frame 064015/0001 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Apr 27, 2023
From: BLACKBERRY LIMITED
To: OT PATENT ESCROW, LLC
Reel/Frame 063471/0474 →
CHANGE OF NAME Recorded Oct 20, 2014
From: RESEARCH IN MOTION LIMITED
To: BLACKBERRY LIMITED
Reel/Frame 034016/0738 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Nov 5, 2010
From: RESEARCH IN MOTION CORPORATION
To: RESEARCH IN MOTION LIMITED
Reel/Frame 025326/0176 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 10, 2010
From: BAKKER, JAN HENDRIK LUCAS; ALLEN, ANDREW; BUCKLEY, ADRIAN
To: RESEARCH IN MOTION CORPORATION
Reel/Frame 024970/0053 →