Method, system and entities for multicast content pushing

Abstract
The present invention discloses a method for multicast content pushing between a server entity (UA-I) and at least one client entity (UA-II) as well as a corresponding system and client and server entities. The method comprises the steps of inviting, by the server entity, at least one client entity to join a multicast content streaming session, answering, by the at least one client entity to the server entity, whether the client entity joins the invited multicast content streaming session, releasing, at the server entity and to the server entity, a request for multicast content streaming, responding, by the server entity, to the released request by sending a response to the request to the at least one client entity that joined the multicast content streaming session.
Description

BRIEF DESCRIPTION OF THE DRAWINGS

The invention is described herein below with reference to the accompanying drawings, in which



FIG. 1 shows a conventional usage JPIP Interactive image browsing system;



FIG. 2 shows JPIP-PUSH usage;



FIG. 3 shows a case how JPIP-PUSH would work with FLUTE in a reliable multicast transport scenario;



FIG. 4 shows a typical JPIP-PUSH image streaming system;



FIG. 5 shows an example use case, where the image sharer using the user interface UI on the phone browses the image, and then “pushes” the selected ROI to the JPIP-PUSH clients;



FIG. 6 shows a signaling diagram for the method according to an exemplary implementation of the present invention;



FIG. 7 shows a block circuit diagram of a server entity; and



FIG. 8 shows a block circuit diagram of a client entity.


Claims
  • 1. A method for multicast content pushing between a server entity and at least one client entity, the method comprising: inviting, by the server entity, at least one client entity to join a multicast content streaming session;answering, by the at least one client entity to the server entity, whether the at least one client entity joins the invited multicast content streaming session;releasing, at the server entity and to the server entity, a request for multicast content streaming; andresponding, by the server entity, to the released request by sending a response to the request to the at least one client entity that joined the multicast content streaming session.
  • 2. A method according to claim 1, wherein said inviting further comprises sending invitation information to the at least one client entity in a signaling message of an ongoing session.
  • 3. A method according to claim 1, wherein said inviting further comprises sending invitation information to the at least one client entity within a call of an ongoing session.
  • 4. A method according to claim 1, wherein said releasing further comprises generating a request for multicast content streaming at the server entity via a user-interface.
  • 5. A method according to claim 1, wherein said releasing further comprises retrieving a request for multicast content streaming at the server entity from pre-stored requests.
  • 6. The method according to claim 4, wherein the request is a JPIP request and the multicast streaming content is JPEG 2000 data.
  • 7. The method according to claim 5, wherein the request is a JPIP request and the multicast streaming content is JPEG 2000 data.
  • 8. A method according to claim 1, wherein said responding further comprises composing a response including the multicast streaming content andthe request including parameters for multicast content streaming.
  • 9. A method according to claim 1, wherein said responding further comprises sending the response using a separate multicast content streaming transport session, which is operative in tandem to an ongoing session used for invitation to join the multicast content streaming session.
  • 10. A method according to claim 9, wherein the multicast content streaming transport session is a FLUTE session.
  • 11. A method according to claim 1, further comprising: receiving the response at the at least one client entity that joined the multicast content streaming session, the response including the multicast streaming content and the request including parameters for multicast content streaming;decoding the response; andrendering the multicast streaming content at the at least one client entity using the parameters contained in the response.
  • 12. A system, the system being configured for multicast content pushing between a server entity and at least one client entity and comprisinginvitation unit, at the server entity, configured to invite the at least one client entity to join a multicast content streaming session;answering unit, at the at least one client entity, configured to answer to the server entity, whether the at least one client entity joins the invited multicast content streaming session;releasing unit, at the server entity, configured to release to the server entity a request for multicast content streaming; andresponder unit, at the server entity, configured to respond to the released request by sending a response to the request to the at least one client entity that joined the multicast content streaming session.
  • 13. A system according to claim 12, wherein the invitation unit is configured to send invitation information to the at least one client entity in a signaling message of an ongoing session.
  • 14. A system according to claim 12, wherein the invitation unit is configured to send invitation information to the at least one client entity within a call of an ongoing session.
  • 15. A system according to claim 12, wherein the releasing unit comprises generating unit configured to generate a request for multicast content streaming at the server entity via a user-interface.
  • 16. A system according to claim 12, wherein the releasing unit comprises a retrieval unit configured to retrieve a request for multicast content streaming at the server entity from a memory containing pre-stored requests.
  • 17. A system according to claim 15, wherein the request is a JPIP request.
  • 18. A system according to claim 16, wherein the request is a JPIP request.
  • 19. A system according to claim 12, wherein the responder unit is configured to compose a response including multicast streaming content andthe request including parameters for multicast content streaming.
  • 20. A system according to claim 12, wherein the responder unit is configured to send the response using a separate multicast content streaming transport session, which is operative in tandem to a session used for invitation to join the multicast content streaming session.
  • 21. A system according to claim 20, wherein the multicast content streaming transport session is a FLUTE session.
  • 22. A client entity, configured to receive multicast content pushed from a server entity,
  • 23. The client entity according to claim 22, wherein the request is a JPIP request and the multicast streaming content is JPEG 2000 data.
  • 24. A server entity, configured to multicast content pushing to at least one client entity,
  • 25. A server entity according to claim 24, wherein the invitation unit is configured to send invitation information to the at least one client entity in a signaling message of an ongoing session.
  • 26. A server entity according to claim 24, wherein the invitation unit is configured to send invitation information to the at least one client entity within a call of an ongoing session.
  • 27. A server entity according to claim 24, wherein the releasing unit comprises generating unit configured to generate a request for multicast content streaming at the server entity via a user-interface.
  • 28. A server entity according to claim 24, wherein the releasing unit comprises retrieval unit configured to retrieve a request for multicast content streaming at the server entity from a memory containing pre-stored requests.
  • 29. A server entity according to claim 27, wherein the request is a JPIP request and content being streamed is JPEG 2000 data.
  • 30. A server entity according to claim 28, wherein the request is a JPIP request and content being streamed is JPEG 2000 data.
  • 31. A server entity according to claim 24, wherein the responder unit is configured to compose a response including multicast streaming content andthe request including parameters for multicast content streaming.
  • 32. A server entity according to claim 24, wherein the responder unit is configured to send the response using a separate multicast content streaming transport session, which is operative in tandem to a session used for invitation to join the multicast content streaming session.
  • 33. A server entity according to claim 32, wherein the multicast content streaming transport session is a FLUTE session.
  • 34. A computer program product, configured for a client-server computer system and comprising processor implementable instructions stored as software code portions on a computer-readable medium loadable into an internal memory of the client-server computer, configured for providing for multicast content pushing between a server entity and at least one client entity, comprising:inviting, by the server entity, at least one client entity to join a multicast content streaming session;answering, by the at least one client entity to the server entity, whether the at least one client entity joins the invited multicast content streaming session;releasing, at the server entity and to the server entity, a request for multicast content streaming; andresponding, by the server entity, to the released request by sending a response to the request to the at least one client entity that joined the multicast content streaming session.
  • 35. The computer program product according to claim 34, wherein said releasing further comprises generating a request for multicast content streaming at the server entity via a user-interface.
  • 36. The computer program product according to claim 34, wherein said releasing further comprises retrieving a request for multicast content streaming at the server entity from pre-stored requests.
  • 37. A server entity, configured to multicast content pushing to at least one client entity,
  • 38. A client entity, configured to receive multicast content pushed from a server entity,
Provisional Applications (1)
Number Date Country
60754640 Dec 2005 US