Patent Application
20150081776
This application claims the priority under 35 U.S.C. §119(a) to Indian Provisional patent application Serial No. 4142/CHE/2013, which was filed in the Indian Intellectual Property Office on Sep. 17, 2013, and Indian Provisional patent application Serial No. 4261/CHE/2013, which was filed in the Indian Intellectual Property Office on Sep. 20, 2013, and Indian Complete patent application Serial No. 4142/CHE/2013, which was filed in the Indian Intellectual Property Office on Sep. 10, 2014, the entire content of which are incorporated herein by reference.
1. Field of the Invention
The present invention relates to mobile communications on mobile devices with integrated content viewing and communication and more particularly to establish an integrated group session for collaborative content viewing.
2. Description of the Related Art
Open Mobile Alliance (OMA) has identified requirements of the Immersive Social Centre (ISC) enabler for enhancing user experience with value added features to provide immersive (being their-being with) experience. These value added features include enabling multiple communication devices identified as a group to simultaneously organize a content viewing session and a communication session to enable integration of content viewing and communication session in the group with reference to the content being viewed. The integrated sessions for a group of ISC users established by an ISC enabler in an ISC architecture is an integrated group ISC session.
Interested content be viewed called a content interest can be selected by an ISC user interested in initiating the integrated group ISC session from a received list of the real-time or non-real-time contents provided by a service provider. The ISC user can receive a full XDM document (a full contents list) or a partial XDM document (a partial contents list). However, the partial contents list is based on only pre-defined user preferences and thus is limited to only static preferences of the ISC user. The content interest is then to be conveyed to the components of the ISC enabler that enable establishing the integrated group ISC session.
Delivering a contents list to the ISC user based on varied user preferences and user's context information not limited to static preferences of the ISC user can enhance the user experience. Also, providing efficient methods for conveying the content interest of the ISC user to the ISC enabler components in the wireless network to view the content interest during the integrated group ISC session will be appreciated.
The principal object of the embodiments herein is to provide a method and system for establishing an integrated group Immersive Social Centre (ISC) session for a content viewing and a communication, among members of a pre-defined group by an ISC server for delivering content associated with a content interest expressed by an initiator ISC client.
Another object of the invention is to provide a method for delivering a personalized contents list or a full contents list to an ISC user based on static user preferences or on-demand user preferences and/or user's context information of the ISC user associated with the initiator ISC client. Further, allowing the ISC user to select the content interest for the integrated group ISC session from the personalized contents list.
Accordingly the invention provides a method for establishing an integrated group Immersive Social Centre (ISC) session for content viewing and communication based on a content interest. Further, the method comprises receiving the content interest by the ISC session server, wherein the content interest is received in a request from the initiator ISC client for initiation of the integrated group ISC session. Further, the method comprises interacting with at least one recipient ISC client from a plurality of recipient ISC clients by the ISC session server for communicating the content interest. The plurality of recipient ISC clients is available to the ISC session server as a Uniform Resource Indicator (URI) list in the received request. Furthermore, the method comprises identifying each interested ISC client among the plurality of recipient ISC clients, by the ISC session server, that indicate interest in the content interest. Furthermore, the method comprises establishing the integrated group ISC session among members of a pre-defined group by the ISC session server to deliver content associated with the content interest. The members of the pre-defined group include the initiator ISC client and each the interested ISC client.
Accordingly the invention provides a system for establishing an integrated group Immersive Social Centre (ISC) session for content viewing and communication based on a content interest. The system comprises an ISC session server, an initiator ISC client, and a plurality of recipient ISC clients. The initiator ISC client is configured to receive a request to initiate the integrated group ISC session based on the content interest. The initiator ISC client is further configured to generate and send a request with the content interest to the ISC session server for initiation of the integrated group ISC session. Further, the ISC session server is configured to interact with at least one recipient ISC client from the plurality of recipient ISC clients for communicating the content interest. The plurality of recipient ISC clients is available to the ISC session server as a Uniform Resource Indicator (URI) list in the request sent by the initiator ISC client. The ISC session server is further configured to identify each interested ISC client among the plurality of recipient ISC clients indicating interest in the content interest. The ISC session server is further configured to establish the integrated group ISC session among members of a pre-defined group to deliver content associated with the content interest. The members of the pre-defined group include the initiator ISC client and each of the interested ISC clients.
Accordingly the invention provides a computer program product comprising computer executable program code recorded on a computer readable non-transitory storage medium, the computer executable program code when executed, causing the actions including receiving a content interest in a request for initiation of a integrated group ISC session from an initiator ISC client by an ISC session server in an ISC architecture. Further, the actions caused by execution of the executable program code include interacting with at least one recipient ISC client from a plurality of recipient ISC clients by the ISC session server for communicating the content interest. The plurality of recipient ISC clients is available to the ISC session server as a Uniform Resource Indicator (URI) list in the received request. Further, the actions caused by execution of the executable program code include identifying each interested ISC client among the plurality of recipient ISC clients indicating interest in the content interest by the ISC session server. Furthermore, the actions caused by execution of the executable program code include establishing the integrated group ISC session among members of a pre-defined group by the ISC session server to deliver content associated with the content interest. The members of the pre-defined group includes the initiator ISC client and each the interested ISC client.
These and other aspects of the embodiments herein will be better appreciated and understood when considered in conjunction with the following description and the accompanying drawings. It should be understood, however, that the following descriptions, while indicating preferred embodiments and numerous specific details thereof, are given by way of illustration and not of limitation. Many changes and modifications may be made within the scope of the embodiments herein without departing from the spirit thereof, and the embodiments herein include all such modifications.
This invention is illustrated in the accompanying drawings, throughout which like reference letters indicate corresponding parts in the various figures. The embodiments herein will be better understood from the following description with reference to the drawings, in which:
The embodiments herein and the various features and advantageous details thereof are explained more fully with reference to the non-limiting embodiments that are illustrated in the accompanying drawings and detailed in the following description. Descriptions of well-known components and processing techniques are omitted so as to not unnecessarily obscure the embodiments herein. The examples used herein are intended merely to facilitate an understanding of ways in which the embodiments herein can be practiced and to further enable those of skill in the art to practice the embodiments herein. Accordingly, the examples should not be construed as limiting the scope of the embodiments herein.
Prior to describing the embodiments in detail, it is useful to provide definitions for key terms and concepts used herein. Unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by a person having ordinary skill in the art to which this invention belongs.
Initiator Immersive Social Centre (ISC) client: Refers to an ISC client on a communication device that initiates an ISC session. The ISC session is initiated by an initiator ISC client on receiving a request from a user (ISC user) and receiving ISC service from an ISC enabler provided by an ISC environment. The ISC session can be a personal ISC session, a one to one ISC session or a group ISC session. Further, the initiator ISC client is also called the originating client.
Recipient ISC client: Refers to an ISC client on another communication device of another ISC user participating in the ISC session. The ISC session referred here can be one to one ISC session or a group ISC session initiated by the initiator ISC client. Here, group ISC session may involve a session established among multiple ISC clients forming the group. Further, the recipient ISC client is also called the terminating client. Further, the group ISC session integrating a content viewing and a communication for delivering contents associated with a content interest expressed by an ISC user associated with the initiator ISC client is called the integrated group ISC session.
The embodiments herein achieve a method and system for establishing an integrated group Immersive Social Centre (ISC) session for a content viewing and a communication by an ISC server based on the content interest expressed by an ISC user. The integrated group ISC session is established for a pre-defined group created with members indicating interest to watch the content in the group ISC session initiated by an initiator ISC client. The members are interested recipient ISC clients from plurality of recipient ISC clients in a Uniform Resource Identifier (URI) list of the initiator ISC client. The method allows the ISC server to receive the content interest from the initiator ISC client.
In an embodiment, the ISC session server can be a presence server or an ISC server in the ISC architecture. The method allows the ISC server to receive and further deliver contents associated with the content interest by establishing the integrated ISC session for the content viewing and the communication. Further, the method allows the members of the pre-defined group to interact with each other for scheduling time for the integrated group ISC session for the content viewing and the communication of interested content. The method allows the ISC server (or Presence server) to receive the published content-delivery information of an initiator ISC client for the content interest. The method allows the ISC server to send alert notifications before delivering the content interest during the established group ISC session for content viewing and the communication. The content interest received from the initiator ISC client is selected by the ISC user of the initiator ISC client from a contents list sent by the ISC server or an ISC Extensible Markup Language Document Management Server (XDMS) in the ISC architecture. The contents list can be a personalized contents list or a full contents list. The personalized contents list is generated by the ISC server or the ISC XDMS based on static user preferences or on demand user preferences of the ISC user associated with the initiator ISC client.
Establishing of the group ISC session for the content viewing and the communication includes performing plurality of steps by the ISC server. The method allows the ISC server to create the pre-defined group for the group ISC session, establish group ISC session for communication to allow scheduling for the group ISC session for content viewing and communication. Further, the method allows the ISC server to notify interested recipient ISC clients on corresponding communication devices about scheduled time and send an alert notification before delivering the contents associated with the content interest and establish the group ISC session based on SIP protocol and deliver the contents associated with the content interest to members of the pre-defined group.
The exchange of SIP protocol signals for establishment of the integrated group ISC session and/or any other ISC session such a one to one ISC session or a group ISC session for the content viewing and/or communication is performed as disclosed in Combined Complete application in pursuance to the Provisional Application No. 4201/CHE/2013 & 4223/CHE/2013 filed with the Indian Patent Office.
The initiator ISC client and the recipient ISC client is a client module on a communication device. In an embodiment, the communication device can be a smart phone, a tablet, a personal digital assistant, a palmtop, a laptop and any other communication device capable handling the ISC session.
Referring now to the drawings that include
As per the standard specification provided by the OMA alliance, the ISC architecture includes an ISC enabler 112 including plurality of functional components and supported by external functional components 113. The ISC enabler 111 includes an ISC client 101 (initiator ISC client), an ISC client 102 (recipient ISC client) and an ISC client 103 (recipient ISC client) in the communication device 100a, 100b and 100c respectively. In the network domain, the ISC enabler 111 includes an ISC server 105, an ISC XML Document Management Server (ISC XDMS) 106 and an ISC CP Gateway (CP Gateway) 107. The ISC enabler functional components in the network domain are supported by external functional components 112 including but not limited to SIP/IP core of the core network 104, a supporting server 108 with a presence server 109, a content provider 110 and a remote ISC environment 111.
The method disclosed allows the initiator ISC client 101 to initiate the integrated group ISC session for the content viewing and the communication among ISC users of communication devices 100b and 100c respectively in the ISC environment depicted by the
The presence server 109 provides ISC Users with the possibility to publish and retrieve presence Information. It also allows the ISC user to publish the content-delivery information (time decided for later delivery of the content and time to receive the alert notification before the content is delivered) and notify subscribed ISC users the content-delivery information. It also allows ISC Users to obtain the presence Information of other ISC Users. The functionalities provided by a Presence Enabler are specified in [OMA-PRS-AD]. The ISC enabler 112 uses the functionalities of the Presence Enabler to obtain Presence Information. The ISC Clients 101, 102, 103 respectively interacts with the Presence Enabler via the PRS-1 and PRS-2 reference points defined by the Presence Enabler.
The initiator ISC client 101 can select the content interest from a contents list provided by the ISC server or the ISC XDMS. The contents list can be a personalized contents list based on one or more static user preferences, a personalized contents list based on one or more on-demand user preferences and/or user's context information or a FullContentList.
In an embodiment, a request, by the initiator ISC client, to retrieve the contents list includes a UserChoice element whose sub-element RefName is set to either ReferPredefinedPref indicating static user preferences, ReferOnDemandPref indicating on-demand user preferences or FullContentsList indicating full contents list requested by an ISC user associated with the initiator ISC client 101. As a person skilled in the art understands, the full contents list can be readily available with the ISC XDMS 106 or can be retrieved by the ISC XDMS using various protocols such as XCAP GET and the like.
The ISC XDMS 106 (XDMS) in the ISC architecture stores and manages XML documents. The functionalities provided by the XDMS are specified in [OMA-XDM-AD]. The XDM Enabler provides XDM operations for ISC User Preferences Profiles, access policies, user lists and group definitions.
In an embodiment, the content, associated with the content interest, delivered to the members during the integrated group ISC session can be media content such as a live content, a video on demand and the like and is provided by the content provider 110.
The communication devices 100a, 100b and 100c respectively are illustrated for simplicity of understanding. However, the ISC environment can include a plurality of communication devices capable of participating in the ISC session on receiving a request from any initiator ISC client in the ISC environment.
The User Interface (UI) module 201 can provide the necessary user interface for the ISC client 101 to receive ISC session establishment request from the ISC user as well as provide indications to the ISC user depicting progress of the initiated ISC session. The communication interface module 202 provides the necessary communication interface to the ISC client 101 to communicate with the ISC server 105, the presence server 108 and the ISC XDMS 106.
The ISC client 101 when configured to function as recipient ISC client notifies the ISC user about the initiated integrated group ISC session and sends control signals and messages to the ISC server 105 based the corresponding ISC users consent to participate in the integrated group ISC session.
The memory module 303 stores contact details and URI list of other ISC users, to be used by the ISC client 101 during the initiation of the ISC session.
For simplicity and ease of understanding, the modules in communication device 100a are limited to the embodiments of the invention. However, the communication device 100a includes various other modules to support additional functionalities and operations of the communication device 100a.
Although it is illustrated in
The Contents Guide Function 301 is configured to provide personalized contents list based on user's context information and user preferences (including metadata) such contents (live or non-live) from content provider 110, user generated contents (live or non-live), and associated contents.
The contents guide function 301 functionalities include but not limited to providing full contents list, sorting of list of available contents as per ISC user specified criteria, searching contents in the contents list, personalization of contents list based on context information of the ISC user (user context) and user preferences, synchronization of contents list with the content provider 110, management (for e.g., removing from availability list, access control list, categorization) of contents. Based on the type of contents list request from the ISC Client, the list of contents includes Content Provider contents (live and non-live), Associated Contents and user Generated Contents (live and non-live).
The communication function in the ISC server 105 performs following functionalities such as:
Perform content viewing and communication session handling (session initiation, modification and termination) related functions.
Provide support for simultaneous sessions for content Viewing and communication.
Maintain integration information of content viewing and communication with one to one ISC session (1-1 ISC session) and group ISC session (1-many ISC session).
Generate the content viewing Group information.
Generate the content view information for sharing to other ISC Users.
Provide support for synchronizing the content viewing between ISC Users.
The communication function of the ISC server 105 interacts with other ISC network components such as a XDM Enabler for the retrieval of user preferences, groups and policies, the Presence Enabler (via Presence Source) for publishing content viewing information and communication information in 1-1 and 1-many ISC sessions, between multi-communication devices when content viewing and communication being distributed on different devices.
The media function of the ISC server 105 supports the following functionalities such as providing centralized mixing of contents (primary content, Associated Content, Remote ISC User content) based on spatial configuration of devices and multi-device capabilities.
The names of the modules of the ISC server 105 are used for illustrative purposes only and should not be considered as a limitation.
The various embodiments for retrieving the personalized contents list or the full contents list are described later in sequence diagrams of
At step 402a, the method 400a configures the ISC server 105 or the ISC XDMS 106, whoever receives the request for retrieving the contents list, to identify whether the request for retrieving the contents list indicates the personalized contents list or the full contents list. The UserChoice element in the SIP SUBSCRIBE request indicates the ISC user desired type of contents list. The UserChoice element whose sub-element RefName can be set by the initiator ISC client 101 to either ReferPredefinedPref, ReferOnDemandPref, or FullContentList
If at step 402a, it is determined that the FullContentList is required, then at step 403a, the method 400a configures the ISC server 105 or the ISC XDMS 106 to provide the full contents list to the ISC user. If at step 402a, it is determined that the personalized contents list is required, then at step 404a, the method 400a configures the ISC server 105 or the ISC XDMS 106 to generate the personalized contents list by applying appropriate filter based on the UserChoice element whose sub-element RefName set to either the ReferPredefinedPref or the ReferOnDemandPref.
In an embodiment, the method 400a applies the user's context information (context information of the ISC user associated with the initiator ISC client 101) is applied on the full contents list to generate the personalized contents list.
Further the ISC server 105 provides the desired contents list to the ISC user. The various actions, acts, blocks, steps, and the like in method 400a may be performed in the order presented, in a different order or simultaneously. Further, in some embodiments, some actions, acts, blocks, steps, and the like may be omitted, added, modified, skipped, and the like without departing from the scope of the invention.
The
In an embodiment the ISC session server can be the ISC server 105 receiving the request in a Session Initiation Protocol (SIP) MESSAGE. In an embodiment the ISC session server can be the presence server 109 receiving the request in a SIP PUBLISH request for the integrated group ISC session initiation. The SIP PUBLISH request allows the initiator ISC client to publish the content interest to the presence server 109. At step 402b, the method 400b configures the ISC session server to interact with the plurality of recipient ISC clients such as the recipient ISC client 102 and the recipient ISC client 103 indicated by a URI list provided by the initiator ISC client 101. At step 403b, the method 400b configures the ISC session server to identify interested ISC client, from the plurality of recipient ISC clients, desiring to participate in the integrated group ISC session initiated by the initiator ISC client 101. The steps describing interaction with the plurality of recipient ISC clients and identifying the interested ISC client are described later in sequence diagrams of
At step 404b, the method 400b configures the ISC server 105 to create a pre-defined group upon receiving a request from the initiator ISC client 101 and send group announcement to all the members of the pre-defined group including the interested recipient ISC clients and the initiator ISC client 101. At step 405b, the method 400b configures the ISC server 105 to establish the group ISC session for communication to allow the members of the pre-defined group to decide the time to watch the content associated interest during the integrated group ISC session. During the group ISC session for communication the participating members also decide upon the reminder time to receive a Content-alert information before the content is delivered. The steps for creation of the pre-defined group, performing group announcement and establishing the group ISC session for communication are described later in sequence diagram of
At step, 406b the method 400b configures the presence server 109 to receive a SIP PUBLISH request, publishing the Content-delivery information and further notify the interested recipient ISC clients about scheduled time (StartTime) for the integrated group ISC session to be established for viewing the interested content. Further the method configures the presence server 109 to send the Content-alert information of the integrated group ISC session to all the members prior to delivery of the contents associated with the content interest, expressed by the ISC user. The Content-alert information includes but is not limited to a StartTime and a text indicating an alert notification for the integrated group ISC session. The alert notification is sent to all members of the pre-defined group based on the reminder time (ReminderTime) decided by the members of the pre-defined group. The steps for publishing the Content-delivery information and sending the Content-alert information are described later in the sequence diagram of
The Content-delivery information includes a reference to the content, start time for the later delivery of the content associated with the content interest and the reminder time to receive the alert notification prior to the delivery of the content expressed by the user through the content interest. The Content-delivery information is included in the presence event package and published in the presence server using SIP PUBLISH request wherein the SIP PUBLISH body includes below as a MIME content:
ContentRef: uniquely identifies the content and indicating reference to the content to be delivered during the integrated group ISC session.SIP URI can be set as the value for ContentRef for the Video on Demand (VOD) Content and Channel Number can be set as the value for the LIVE Content.
StartTime: Indicates ISC user the time decided to watch the content.
ReminderTime: Indicates ISC user the reminder time to receive the alert notification prior to delivery of the content associated with the content interest.
At step, 407b, the method 400b configures the ISC server 105 to establish the integrated group ISC session and deliver the contents associated with the content interest to members of the pre-defined group. The various actions, acts, blocks, steps, and the like in method 400b may be performed in the order presented, in a different order or simultaneously. Further, in some embodiments, some actions, acts, blocks, steps, and the like may be omitted, added, modified, skipped, and the like without departing from the scope of the invention.
The ISCConvergenceID is an ISC specific header field. Including the ISCConvergenceID in the SIP MESSAGE request or SIP INVITE request which is globally unique identifier that indicates the ISC request and response associated with an ISC content viewing and communication, content interest. All requests and responses belonging to the same ISC content viewing and communication or the same content interest carry the same value for the ISCConvergenceID header field. Sending ISC functional component includes an ISCConvergenceID header field in each SIP MESSAGE request or SIP INVITE request that are associated with the ISC content viewing and communication, content interest. The sending ISC functional component ensures that the included ISCConvergenceID is globally unique.
The ISC Content Interest Feature Tag in the first SIP MESSAGE indicates the ISC server 105 whether the initiated ISC session is for establishing an integrated group ISC session to watch the interested content at scheduled time along with other ISC user(s). The ISC Client includes both an IMS Communication Service Identifier (ICSI) and an IMS Application Reference Identifier(IARI)feature tag in the Accept-Contact header, Contact header and P-Preferred-Service header as per [RFC3841], [RFC3840], if the ISC Server has to behave differently when it receives IARI, else the ISC Client includes only ICSI feature tag in the request.
For example CI_FT (Content Interest Feature Tag) is an ISC feature tag set to:
The table 1 provided below describes the ISC feature tag.
Upon receiving request from the ISC user indicating the ISC user's interest in viewing a particular content along with other ISC users, the initiator ISC client 101 generates the SIP MESSAGE request as defined in IETF RFC 3428 with the following clarifications:
Further, the initiator ISC client 101 stores the ISCConvergenceID locally on the device until UserSetExpiryTime lapses and sends (501) the SIP MESSAGE request towards the ISC server 105.
The ISC server 105 checks the value of ISCConvergenceID received in the SIP MESSAGE with the locally stored ISCConvergenceID values and if the value does not match with any of the locally stored ISCConvergenceIDs then the ISC Server 105 stores the value of ISCConvergenceID locally. The ISC Server 105 obtains the plurality of recipient ISC clients (the recipient ISC client 102 and 103 respectively) from the URI list received in the SIP MESSAGE request and obtains the content interest for publishing it to the obtains the plurality of recipient ISC clients (the recipient ISC client 102 and 103 respectively). Further, the ISC server 105 returns (502) 202 Accepted in response to the SIP MESSAGE request received if there are no errors to the request to the initiator ISC client 101 otherwise the ISC server 105 returns error as specified in IETF RFC 3428.
Further, the ISC server 105 forwards (503, 504) the SIP MESSAGE request to the recipient ISC client 102 and 103 respectively as specified in the URI list in the received SIP MESSAGE. The forwarded SIP MESSAGE includes the content interest and retains the same value of the ISCConvergenceID specified in the received SIP MESSAGE. Upon reception of the forwarded SIP MESSAGE, the recipient ISC clients 102 and 103 respectively return (505, 506) 200 OK in response if there are no errors to the request. Otherwise ISC server 105 returns error as specified in IETF RFC 3428. In a particular scenario in the figure, recipient ISC client 102 is interested in the content interest (provides consent for the content interest) expressed by the initiator ISC client 101 while recipient ISC client 103 is not interested in the content interest for participating in the integrated group ISC session based on the content interest.
Thus, the recipient ISC client 102 and 103 checks if the UserSetExpiryTime is lapsed or not. If not lapsed the ISC client 102 and 103 generates and sends (507) a SIP MESSAGE (response SIP MESSAGE) in response to the forwarded SIP MESSAGE request. The SIP MESSAGE from plurality of recipient ISC clients 102 and 103 respectively indicates to the ISC server 105 whether the plurality of recipient ISC clients given their consent to the integrated group ISC session for the content interest. The SIP MESSAGE response comprises the ISCConvergenceID as received in the SIP MESSAGE request, the CI_FT as specified in Table 1, and UserInterest indicating consent/response of the recipient ISC clients 102 and 103 respectively for the interested content with the value UserInterest set to either yes (interested) or no (not interested). This SIP MESSAGE response is sent towards the ISC Server 105. If the UserSetExpiryTime has lapsed and the recipient ISC User(s) has not responded until, then the recipient ISC Client(s) notifies the recipient ISC User(s) about the expired time. The ISC server 105 returns (508) a 200 OK in response to the SIP MESSAGE received from the recipient ISC clients 102 and 103 respectively if there are no errors to the request. Otherwise ISC server 105 return error as specified in IETF RFC 3428.
However, as depicted in the figure the recipient ISC client 103, which is not interested in the content interest, may not respond with the response SIP MESSAGE. Thus, the ISC server 105 waits for the ISC User(s) consent (response from the ISC user(s) associated with all corresponding recipient ISC client(s) recipient ISC client 102 and 103 respectively) until the UserSetExpiryTime lapses, aggregate and forwards the recipient ISC user(s) responses in SIP MESSAGE (509) towards the initiator ISC client 101 including each recipient ISC user(s) response in the UserID element and the corresponding sub-element UserInterest element in the MIME body.
Upon receiving the SIP MESSAGE with content interest, the initiator ISC client 101 checks the value of the ISCConvergenceID matched with the locally stored value and then extracts the UserID element(s) and its corresponding sub-element UserInterest element from the MIME body containing the Content-Type “application/vnd.omadsc.content-interest+xml”; The initiator ISC Client 101 then notifies the initiator ISC User about the content interest response from the recipient ISC Users according to the value extracted from the sub-element UserInterest of the element UserID.
The initiator ISC client 101 returns (510) a 200 OK in response to the SIP MESSAGE received from the ISC server 105 if there are no errors to the request. Otherwise ISC server 105 return error as specified in IETF RFC 3428.
Upon receiving request from the ISC user indicating the ISC user's interest in viewing a particular content, the initiator ISC client 101 generates (601) the SIP PUBLISH request to a presence event package with the content interest (“isc-content-interest”) being specified in the SIP PUBLISH request body. For example:
The ISC server 105 returns (602) 200 OK in response to the SIP PUBLISH request received if there are no errors to the request. Otherwise ISC server returns error as specified in IETF RFC 3261.
Further, the recipient ISC client 102 and 103 respectively subscribe (603, 605) to the presence event package by sending SIP SUBSCRIBE request to the ISC server 105. The ISC server returns 200 OK (604, 606) in response to the SIP SUBSCRIBE request received. For example:
Further, the presence server 109 generates (607, 608) a SIP NOTIFY (first SIP Notify) request to the recipient ISC clients 102 and 103 respectively to notify about the content interest of the initiator ISC client 101 in the presence event package. For example:
The recipient ISC client 102 and 103 respectively return (609, 610) 200 OK in response to the SIP NOTIFY received. Further, if the recipient ISC client 102 receives a request from the ISC user associated with the recipient ISC client 102 indicating consent in the content interest, the recipient ISC client 102 generates and sends (611) a SIP PUBLISH request to the presence event package with “application/vnd.oma.isc.content-interest” being included in the SIP PUBLISH request body.
The ISC server returns (612) 200 OK in response to the SIP PUBLISH request received if there are no errors to the request. Further, since the recipient ISC client 103 is not interested in the content interest it does not publish presence information in the ISC server 105.
Upon the initiator ISC client 101 subscription to the presence event package, the initiator ISC client 101 generates and sends (613) a SIP SUBCRIBE request to the presence server 109 and gets notified from the presence server 109 when there is update in the presence event package. Thus, whenever any of the ISC users show interest in content interest, then the initiator ISC client 101 gets notified (615) in SIP NOTIFY from the presence server. In response to the SIP NOTIFY the initiator ISC client 101 sends (616) the 200 OK in response to the SIP NOTIFY.
The ISC server 105 obtains the plurality of recipient ISC clients from the URI list and creates the pre-defined group. Further, the ISC server returns (702) a 200 OK in the response to the XCAP PUT received if there are no errors to the request.
Once the ISC server 105 sends the 200 OK, the ISC server 105 performs group announcement to all members of the pre-defined group informing the creation of the pre-defined group. The group announcement of the newly formed group is performed through the SIP MESSAGE (703, 704) to the members and the members respond to the group announcement in the 200 OK (705, 706).
Further, for establishing the group communication session among the members for deciding the time to watch the contents associated with the content interest plurality of steps are performed. The steps including the exchange of SIP control signals such as SIP INVITE (707, 709), the 200 OK (708, 710) and the MSRP send (711) to establish the group ISC session for communication are performed as described in application 4223/CHE/2013. Upon establishment of the group ISC session for communication the members of the pre-defined group decide on time to watch the content and receive the alert notification prior to the delivery of contents associated with content interest.
Upon receiving the request from the ISC user for setting up time for later delivery of the content and for receiving the alert notification prior to the content delivery, the initiator ISC client 101 generates (801) and sends a SIP PUBLISH request with presence event package towards the presence server 109.
The SIP PUBLISH request publishes the Content-delivery information to the presence event package and the MIME body of the SIP PUBLISH request publishing the Content-delivery information indicates a StartTime, a ReminderTime and a ContentRef to the presence server 109.
The SIP PUBLISH request is sent with following additional clarifications:
For example:
The presence server 109 returns (802) 200 OK in response to the SIP PUBLISH request received if there are no errors to the request. Further, the presence server 109 generates and sends (803) a SIP NOTIFY (second SIP NOTIFY) to each interested ISC client. The SIP NOTIFY indicates the Content-delivery information to each interested ISC client in the pre-defined group.
The recipient ISC client 102 returns (804) 200 OK to the presence server 109 in response to SIP NOTIFY received if there are no errors to the request.
Further, after return of the 200 OK in response to the SIP NOTIFY by the presence server 109, upon lapse of the reminder time to send alert, the ISC server 105 (Contents Guide Function 301) generates and sends (805, 806) the SIP MESSAGE request for communication as defined in IETF RFC 3428 stating as “alert message from the ISC server before the content distribution starts” with the following clarifications:
The MIME body of the SIP MESSAGE includes the content-alert information such as StartTime, a text indicating the alert notification and the ContentRef.
Further, on reception (807, 808) of the 200 OK from the members of the pre-defined group (initiator ISC client 101 and the recipient ISC client 102) the ISC server 105 establishes the integrated group ISC session for delivering the content associated with the content interest and allow the members to communicate with each other with reference to the content being delivered.
The ISC XDMS 106 can obtain the XML document containing the list of contents (contents list) and its associated metadata information and sends (901) an XCAP GET request to ISC CP Gateway 107, which responds (902) to the XCAP GET with 200 OK providing the full contents list in 200 OK.
However, the full contents list can be obtained by the ISC XDMS 107 using any existing method and is not limited to XCAP Get Schema for full contents list is provided, according to the embodiments as disclosed herein. The contents list schema for retrieving the full and personalized contents list from ISC XDMS and the elements are briefly described in below in table 2.
The full Contents List can be generated by the Service Provider (SP) or offered by the Content Provider (CP) Full Contents List schema. The SP can receive the list of contents from all the CP's they are associated with and form a Full Contents List for their subscribed user. The Full Contents List contains list of all contents provided by the SP.
This Full Contents List Schema is not exhaustive. It can also include more information provided by either SP or CP such as offers and so on.ET.
Further, the initiator ISC client 101 creates a Contents-list event package which can be specified in new Content-Type in HTTP GET header.
For example,
Further, the initiator ISC client 101 subscribes (903) to the Contents-list event package whose schema is described above by sending SIP SUBSCRIBE request and specifying the
<UserChoice: RefName=> in the xml body.
The UserChoice element set to ReferPredefinedPref indicates that the ISC user has requested the personalized contents list with static preferences that the ISC user has pre-defined in the ISC server 105. The ISC server 105 sends (904) the 200 OK. The contents guide function 301 parses the value of “UserChoice: RefName” element and refers the value with Full Contents list schema to provide the type of contents list to the ISC user has requested. In this scenario the contents guide function 301 has to provide the personalized contents list to the user according to the pre-defined preferences stated by the user. Also the “Expires” header field value is “Zero” in the SIP SUBSCRIBE request stating to fetch the contents list only once by SIP SUBSCRIBE request.
For example,
Further, the contents guide function 301, to obtain the Contents-list XDM document, sends (905) an XCAP GET request to ISC XDMS 106 and receives (906) the full Contents-list XML document in 200 OK. Further, contents guide function 301 obtains the User-Preferences XDM document by purpose sending (907) the XCAP GET request to the ISC XDMS 106 and receives the user preferences XML document in 200 OK. For example, the initiator ISC client 101 has sets preferences “Action” in “Genre” element. The when User-Preferences XDM document is already created for initiator ISC client 101 in the ISC XDMS 106. The contents guide function 301 in the ISC server 105 on receiving (908) the Contents-list XDM document and User-Preferences XDM document in the 200 OK applies pre-defined user preferences of the imitator ISC client 101 to the Contents-list XDM document (full contents list) and notifies (909) the personalized contents list to theimitator ISC client 101 through the SIP NOTIFY. For example,
The steps 1001, 1002, 1003, 1004, 1005 and 1006 for obtaining the full contents list by the contents guide function 301 from the ISC XDMS 106 on receiving the subscription to Content-list event package from the initiator ISC client 101 are similar to steps 902 to 906 respectively and are not repeated for brevity. However, the initiator ISC client generates and sends (1003) the SIP SUBSCRIBE request similar to step 901 with the UserChoice element set to on demand preferences (ReferOnDemandPref) as requested by the ISC user.
<UserChoice: RefName=ReferOnDemandPref>.
The body of the SIP SUBSCIBE further includes the on demand preferences of the ISC user along with the context information of the user (user context information) such as history of content watched by the ISC user
The contents guide function 301 parses the value of “UserChoice: RefName” element and refers the value with Full Contents list schema to provide the type of contents list to the user. In this scenario the contents guide function 301 has to provide the Personalized Contents List to the user according to the pre-defined preferences stated by the user.
For example,
On receiving the full contents list form the ISC XDMS 106 at step 1006, the contents guide function 301 of the ISC server 105 applies the on demand user preferences (ReferOnDemandPref) which is received by the ISC server 105 at step 1003 in the body of the SIP SUBSCRIBE request.
Further, the contents guide function notifies (1007) the personalized contents list based on ReferOnDemandPref to the imitator ISC client 101 through SIP NOTIFY (third SIP NOTIFY).
For example,
Further, the initiator ISC client 101 send (1008) the 200 OK in response to the SIP NOTIFY.
In an embodiment, in case the ISC user requests for the full contents list the initiator ISC client 101 generates and sends the SIP SUBSCRIBE with
<UserChoice: RefName=FullContentsList>
In such scenario the full contents list obtained by the ISC server 105 from the ISC XDMS 106 and forwarded to the initiator ISC client 101 without applying any filter for user preferences.
In another embodiment, the initiator ISC client 101 can directly send a request to retrieve the full contents list by generating and sending the XCAP GET request to the ISC XDMS 106r and receives the full Contents-list XDM document in 200 OK.
In an embodiment, the personalized contents list can be requested directly to the ISC XDMS 106 by the initiator ISC client 101 through an XQUERY by specifying the XQUERY filter as user preferences. For example, to obtain the personalized contents list with “Genre” as “Action” and “AspectRatio” as “HD” the initiator ISC client 101 sends the XQUERY (HTTP POST) request to the ISC XDMS 106. The search is targeted at the home domain only.
For example,
The ISC XDMS 106 performs the search operation and sends an HTTP “200 OK” response including the requested results in the body.
For example,
In an embodiment, the initiator ISC client can request for retrieving the personalized contents list through the XCAP GET request towards the ISC XDMS 106 with user preferences in a REQUEST URI. The search is targeted at the home domain only. Further, the ISC XDMS 106 performs the search operation and sends an HTTP “200 OK” response including the requested results in the body.
For example,
The initiator ISC client 101 generates and sends (1101) the SIP SUBSCRIBE request with user preferences specified by xcap-diff-Content-list event package, diff-processing=aggregate to the contents guide function 301 of the ISC server 105. For example, the initiator ISC client (“sip:joebloggs@example.com”) subscribes to the Contents-list event package with contact SIP URI “sip:joebloggs@example.com” since the ISC user wants the contents list to be updated by sending the SIP SUBSCRIBE request to the contents guide function 301. For example,
Further, the contents guide function 301 forwards (11020 the initiator ISC client's 101 (“sip:joebloggs@example.com”) SIP SUBSCRIBE request to the ISC XDMS 106. Further, the ISC XDMS 106 performs the necessary authorization checks on the request originator, the ISC XDMS sends (1103) HTTP “200 OK” response including the requested document in the body. The contents guide function 301 forwards (1104) the “200 OK response to the originator (initiator ISC client 101) of the SIP SUBSCRIBE request “sip:joe.bloggs@example.com”. Further, the ISC XDMS 106 generates and sends (1105) an initial SIP NOTIFY containing the initial references to the XDM document (aggregated differences in the contents list).
For example,
Further, the contents guide function 301 forwards (1106) the SIP NOTIFY request to the initiator ISC client 101 with the aggregated differences (personalized contents list as requested).
If the ISC XDMC does not have local copies of the XDM document it may retrieve as required.
Further, the initiator ISC client responds (1107) to the received SIP NOTIFY with the 200 OK. Further, the contents guide function 301 forwards (1108) the 200 OK to the ISC XDMS 106.
Upon receiving the request from the ISC user to receive the personalized contents list, the initiator ISC client 101 subscribes to the xcap-diff event package, generates and sends (1201) a SIP SUBSCRIBE request towards the ISC XDMS 106 with following clarifications:
After the ISC XDMS 106 receives the SIP SUBSCRIBE request, performs the necessary authorization checks on the request originator (initiator ISC client 101) and sends (1202) the 200 OK response towards the initiator ISC client. Further, on receiving the SIP SUBSCRIBE request from the initiator ISC client, the ISC XDMS 106 checks the SIP SUBSCRIBE request carrying user preferences and/or user's context information in its body and identifies UserChoice element whose sub-element RefName carries value FullContentsList or ReferOnDemandPref. If the SIP SUBSCRIBE request carries the UserChoice element whose sub-element RefName value is ReferOnDemandPref, then the ISC XDMS 106 applies the user preferences and/or user's context information received in the SIP SUBSCRIBE request on the full contents list obtained from the ISC CP Gateway 107 and generates and sends (1203) in the SIP NOTIFY body containing the personalized contents list document.
Further, the initiator ISC client 101 responds (1204) to the ISC XDMS 106 with the 200 OK on receiving the personalized contents list.
The overall computing environment 1301 can be composed of multiple homogeneous and/or heterogeneous cores, multiple CPUs of different kinds, special media and other accelerators. The processing unit 1304 is responsible for processing the instructions of the algorithm. Further, the plurality of processing units 1304 may be located on a single chip or over multiple chips.
The algorithm comprising of instructions and codes required for the implementation are stored in either the memory unit 1305 or the storage 1306 or both. At the time of execution, the instructions may be fetched from the corresponding memory 1305 and/or storage 1306, and executed by the processing unit 1304.
In case of any hardware implementations various networking devices 1308 or external I/O devices 1307 may be connected to the computing environment to support the implementation through the networking unit and the I/O device unit.
The embodiments disclosed herein can be implemented through at least one software program running on at least one hardware device and performing network management functions to control the elements. The elements shown in
The foregoing description of the specific embodiments will so fully reveal the general nature of the embodiments herein that others can, by applying current knowledge, readily modify and/or adapt for various applications such specific embodiments without departing from the generic concept, and, therefore, such adaptations and modifications should and are intended to be comprehended within the meaning and range of equivalents of the disclosed embodiments. It is to be understood that the phraseology or terminology employed herein is for the purpose of description and not of limitation. Therefore, while the embodiments herein have been described in terms of preferred embodiments, those skilled in the art will recognize that the embodiments herein can be practiced with modification within the spirit and scope of the embodiments as described herein.
| Number | Date | Country | Kind |
|---|---|---|---|
| 4142/CHE/2013 | Sep 2013 | IN | national |
| 4261/CHE/2013 | Sep 2013 | IN | national |
