hash
stringlengths 32
32
| doc_id
stringlengths 7
13
| section
stringlengths 3
121
| content
stringlengths 0
3.82M
|
|---|---|---|---|
a51f761c27385e5a8c90041b2c701012
|
182 027
|
8.3.2.1 UE-initiated BC session modification
|
Figure 15 provides an overview of the information flows for UE-initiated BC session modification. ETSI ETSI TS 182 027 V3.5.1 (2011-03) 57 Figure 15: UE-initiated BC session modification 1) The UE initiates a session modification procedure in order to start a modification of network parameters necessary to handle the BC service. 2) The session modification request is forwarded to the SCF through the Core IMS. 3) Procedures for the negotiation of the network parameters necessary to handle the BC service take place between the UE and the SCF (see clause 8.3.1.2). NOTE: In a particular protocol realization, the messages supporting step 3 may be embedded in the messages supporting session modification. 4) The SCF acknowledges the session modification. 5) The P-CSCF within the Core IMS interacts with the RACS to commit all resources previously reserved. 6) The P-CSCF forwards the confirmation to the UE. 7) The UE starts joining multicast channels and receiving multicast flows.
|
a51f761c27385e5a8c90041b2c701012
|
182 027
|
8.3.2.2 SCF-initiated BC session modification
|
Figure 16 provides an overview of the information flows for SCF-initiated session modification. SCF UE Core IMS RACS (7) Content Control and Content Delivery Flows (3) Content Delivery Channel Setup/Modification (1) Session Modification Request (2) Session Modification Request (4) Session Modification Response (5) ResourcesCommit (6) Session Modification Response ECF/ EFF ETSI ETSI TS 182 027 V3.5.1 (2011-03) 58 Figure 16: SCF-initiated BC session modification 1) The SCF initiates a session modification procedure in order to start a negotiation for network parameters necessary to handle the BC service. 2) The session modification request is forwarded to the UE by the Core IMS. 3) Procedures for the negotiation of the network parameters necessary to handle the BC service take place between the UE and the MF (see clause 8.3.1.2). NOTE: In a particular protocol realization, the messages supporting step 3 may be embedded in the messages supporting session modification. 4) The UE confirms the modification of the session. 5) The P-CSCF within the Core IMS interacts with the RACS to commit all resources previously reserved. 6) The Core IMS forwards this modification to the SCF. 7) The UE starts joining multicast channels and receiving multicast flows.
|
a51f761c27385e5a8c90041b2c701012
|
182 027
|
8.3.3 Signalling flows for broadcast session release
| |
a51f761c27385e5a8c90041b2c701012
|
182 027
|
8.3.3.1 UE-initiated session release
|
Figure 17 provides an overview of the information flows for UE-initiated session release. SCF UE Core IMS RACS (7) Content Control and Content Delivery Flows (3) Content Delivery Channels Setup/Modification (2) Session Modification Request (1) Session Modification Request (6) Session Modification Response (5) ResourcesCommit (4) Session Modification Response ECF/ EFF ETSI ETSI TS 182 027 V3.5.1 (2011-03) 59 SCF UE Core IMS RACS (5) Session Terimnation Confirm (4) Session Termination Confirm (1) Session ITermination Request (3) Session Termination Request (2) Resources release Figure 17: UE-initiated broadcast session release 1) The UE initiates a session termination. 2) The P-CSCF interacts with the RACS to release all transport resources that had been reserved for this session and to deactivate the service package in transport network element to prevent invalid multicast joining. 3) The Session Termination Request is routed by the Core IMS entities up to the SCF. 4) The SCF returns a Session Termination Confirm to the Core IMS. 5) The P-CSCF forwards the Session Termination Confirm to the UE.
|
a51f761c27385e5a8c90041b2c701012
|
182 027
|
8.3.3.2 SCF-initiated session release
|
Figure 18 provides an overview of the information flows for SCF-initiated session release. ETSI ETSI TS 182 027 V3.5.1 (2011-03) 60 SCF UE Core IMS RACS (5) Session Termination Confirm (4) Session Termination Confirm (1) Session Termination Request (3) Session Termination Request (2) Resources release Figure 18: SCF-initiated broadcast session release 1) The SCF initiates a session termination. 2) The P-CSCF interacts with the RACS to release all transport resources that had been reserved for this session and to deactivate the service package in transport network element to prevent invalid multicast joining. 3) The Session Termination Request is routed by the Core IMS entities up to the UE. 4) The UE returns a Session Termination Confirm to the Core IMS. 5) The Core IMS forwards the Session Termination Confirm to the SCF.
|
a51f761c27385e5a8c90041b2c701012
|
182 027
|
8.3.4 Signalling flow for Broadcast TV channel switching
|
Figure 19 provides an example of a signalling flow for channel switching. It shows how the SCF can be informed about what channel is currently being watched. Core IMS SCF (3) Inform channel change (4) Inform channel change ECF/EFF (1) Switch multicast channel UE (2) Delay Figure 19: Broadcast TV channel switching ETSI ETSI TS 182 027 V3.5.1 (2011-03) 61 1) The UE leaves a multicast channel and joins another multicast channel. 2) A delay may be applied. If the user switches channel again during this delay time, the flow is restarted at step 1. 3) The UE sends information about which channel is being watched. 4) Core IMS routes the information to the SCF. The SCF stores channel change information in the Service Action Data. 8.3.5 Signalling flows for transition from Broadcast TV to Broadcast TV with trick play Figure 20 provides the signalling flow for trick play of a Broadcast TV channel. In order to apply trick modes to a Broadcast TV session, this must be established as indicated in clause 8.3.1. The same session is used in the trick play session modification, in order not to change the bandwidth requirements on the network. At successful conclusion of these procedures the UE seamlessly transitions from viewing Broadcast TV to Broadcast TV with trick play. NOTE: As an alternative to the session modification, it is possible to initiate a separate session for trick modes handling, in addition to the Broadcast TV one, while keeping control of the bandwidth requirements between the two of them. This method is, however, out of the scope of the present document. ETSI ETSI TS 182 027 V3.5.1 (2011-03) 62 Figure 20: Signalling flow for initiating trick play of broadcast TV channel 1) Broadcast TV session initiation. NOTE 1: The procedures are the same as clause 8.3.2, Overview of the signalling flows for session initiation. RACS and channel establishment have been removed for purpose of simplification. 2) The UE sends information on the current channel being watched, in order for the SCF to know what channel should be recorded. 3) Core IMS routes the information to the SCF. Core IMS/RACS MCF UE SCF (2) Inform current channel (3) Inform current channel (4) Session Modification Request & Media offer for Content Control and Content Delivery Channel (5) Session Modification Request & Media offer for Content Control and Content Delivery Channel (6) Session Initiation Request & Media offer for Content Control and Content Delivery Channel (7) Session Initiation Response & Media answer for Content Control and Content Delivery Channel (8) Session Modification Response & Media answer for Content Control and Content Delivery Channel (9) Session Modification Response & Media answer for Content Control and Content Delivery Channel el ECF/EFF (10) Leave multicast channel (11) Content Control and Content Delivery Flows MF Reserver Resources Reserver Commit (1) Broadcast TV session initiation ETSI ETSI TS 182 027 V3.5.1 (2011-03) 63 4) When the UE initiates trick play mode of a Broadcast TV the UE sends a session modify request which includes a media offer for a content control channel and content delivery channel with the MF. If trick play service is not available for the UE, the session modification is not sent. NOTE 2: The Broadcast TV with trick play session modification is performed on the same session as the Broadcast TV session initiation. The existing reservation (for broadcast) needs to be modified to add a unicast flow that reuses the resources dedicated to the user. In the figure, RACS has been combined with Core IMS for the purpose of simplification. NOTE 3: Steps 2 and 3 are optional in a generic Broadcast TV session, but are required if trick play is activated. The implementation of both steps as separate messages or combined with step 4 is an implementation issue. 5) After reserving resources in RACS Core IMS forwards the session modification request to the SCF. 6) The SCF forwards the session modification request as a new session initiation to the MF along with the channel indication. The MF will determine if the programme currently broadcasted has trick play support.. Prior to replying the MF uses real time to calculate the media offset for the broadcast TV channel when replying with the offered media. If trick play service is not available for the UE the session modification is rejected and the old Broadcast TV session initiation (along with the previous reserved committed resources) is maintained. 7) The MF sends the session modification response to the SCF. 8) The SCF forwards the session modification response to the Core IMS. 9) After committing resources in RACS Core IMS forwards the session modification response to the UE. 10) The UE leaves the multicast channel. 11) The UE starts playing content and receiving unicast flow. NOTE 4: Alternatives to the above call-flow are for further study. 8.3.6 Signalling flows for transition from Broadcast TV with trick play to Broadcast TV The UE returns from Broadcast TV trick play to linear Broadcast TV, for example when the UE switches channels from a paused channel to another live Broadcast TV channels, or when the UE fast-forwarding in a unicast stream and catches up with the live Broadcast TV channel. The trigger to transition from Broadcast TV with Trick Play to Broadcast TV may be initiated by the UE, SCF or MCF. NOTE: The event to trigger the transition is outside of the present document. The UE or SCF may request a Broadcast TV session modification as described in clause 8.3.2, titled Overview of the signalling flows for session modification. The difference is that the Broadcast TV session modification is performed on the same session, in order to release unicast resources, and the SCF is responsible for releasing the resources in the MCF with a session termination request/response. The MCF may request a session termination towards SCF which in turn performs Broadcast TV session modification towards the UE.
|
a51f761c27385e5a8c90041b2c701012
|
182 027
|
8.3.7 Signalling flows for Broadcast TV with trick play session release
|
When the UE terminates the Broadcast TV with trick play the UE shall follow the same flows as clause 8.4.3.1.
|
a51f761c27385e5a8c90041b2c701012
|
182 027
|
8.3.8 Signalling flows for Pay Per View service
|
Figure 20A depicts signalling flows for PPV service, this procedure applies for IPTV users subscribing to a PPV program scheduled on a channel to which the user is not subscribed to. ETSI ETSI TS 182 027 V3.5.1 (2011-03) 64 Figure 20A: Signalling flows for Pay Per View session Prior to the PPV program session initiation, users should have subscribed a PPV program. The subscription information which may be saved as user profile include the user's indentity, BC service ID and BC program ID of the PPV program. 1) UE initiates the PPV program session as the BC session initiation procedures specified in clause 8.3.1.1.1, The PPV specific steps here are as follows: i) The PPV program session initiation request includes the BC service ID and the BC program ID of the PPV program. ii) When SCF receives the request, the SCF identifies the program according to the BC service ID and BC program ID, and verifies based on the IPTV user profile, that the program has been PPV subscribed. Upon successful verification, the SCF verifies that the program is ready to start, i.e. the current time is greater than/equal to program start time. Then accepts the request. If not, it refuses the request. NOTE 1: The SCF authorizes the BC Session Initiation for that BC Service ID based on the fact that BC Program ID has been PPV subscribed. In the answer to the session initiation, the SCF includes information related to that authorized PPV program to enable the Core IMS to provision RACS with necessary parameters. NOTE 2: The initiation of PPV program session may be triggered by the user's action or the notification from SCF (e.g. SCF detects the PPV program is ready to start, and sends a notification to UE as specified in clause 8.11.1). 2) The UE starts joining multicast channels and receiving multicast flows. 3) UE or SCF initiates the PPV program session release procedure as BC session release procedures specified in clause 8.3.3. As part of the PPV program session release, RACS is updated by removing the BC Service. NOTE 3: Session release for PPV service can be initiated either by SCF or UE. SCF initiates session release when detects the PPV program is over. NOTE 4: An alternative solution using release 2 mechanisms can also be used. The SCF indicates the BC service ID that identifies the PPV program either at session initiation (clause 8.3.1) if the PPV programm is already authorised or by initiating a session modification (clause 8.3.2). If the BC session is on-going when the authorisation duration has elapsed, the SCF modify the session to remove the appropriate BC service ID from the authorised BC service list.
|
a51f761c27385e5a8c90041b2c701012
|
182 027
|
8.4 CoD session
|
The procedures described here are for streaming cases distinguished from upload/download cases (described in clause 8.18). RACS SCF UE Core IMS ECF/EFF (3) PPV program session release (1) PPV program session initiation (2) Content Delivery Flows ETSI ETSI TS 182 027 V3.5.1 (2011-03) 65
|
a51f761c27385e5a8c90041b2c701012
|
182 027
|
8.4.1 Signalling Flows for CoD session initiation
|
Before the User Equipment can view the content, a session initiation procedure shall take place as described in clause 8.4.1. The UE retrieves necessary network parameters to handle the CoD service before the session initiation procedure (from the SSF), or as part of the session initiation procedure, or after the session initiation procedure (from the MF). The session can be terminated by the User Equipment using the procedures described in clause 8.4.3.1 or by the network clause 8.4.3.2. Interactions between the IMS and the RACS take place at different steps of the session initiation/modification and release. In certain cases such as in conventional content server deployments, it may be preferable that a content control channel and content delivery channel(s) be established separately.
|
a51f761c27385e5a8c90041b2c701012
|
182 027
|
8.4.1.1 Overall signalling flows for CoD session initiation
| |
a51f761c27385e5a8c90041b2c701012
|
182 027
|
8.4.1.1.1 UE-initiated CoD session initiation
|
Figure 21 provides an overview of the information flows for UE-initiated CoD session initiation. Figure 21: UE-initiated CoD session initiation 1) (Optionally) UE may retrieve COD offset from service action data. 2) (Optionally) SSF may return COD offset for specified content. 3) The UE initiates a dialogue to the CoD service. (10) Resources Commit (6) Content Control and/or Delivery Channel Setup UE (3) Session Initiation Request (11) Session Initiation Response SSF (1)Retrieve stored offset (optional) (2) COD offset (optional) (4) Session Initiation Request (7) Session Initiation (9) Session Initiation Response (8) Retrieve stored offset (optional) RACS (5) Session Initiation Request Core IMS MF SCF Respons e (12) Content Control flows ETSI ETSI TS 182 027 V3.5.1 (2011-03) 66 4) The session initiation request is routed by the Core IMS entities up to the SCF in charge of the requested CoD service. 5) The SCF performs service authorization as described in clause 5.1. If the UE is allowed to access the content, the SCF forwards the session initiation request to the selected MF. 6) Signalling procedures for establishment of a content control channel and optionally (see note 2) content delivery channels take place between the UE and the MF (see clause 8.4.1.2.1). NOTE 1: In a particular protocol realization, the messages supporting step 6 may be embedded in the messages supporting session initiation. NOTE 2: The establishment of the content delivery channel in the session initiation is only optional when network has provided information for only content control channel setup. In this case, the content delivery channel is established during session modification. 7) The MF confirms the establishment of the dialogue with the UE. 8) (Optionally) If the session initiation does not include a COD offset, the SCF may try to retrieve a stored offset for this CoD service in service action data. In this case, the SCF includes this offset in the session initiation answer. 9) The SCF forwards this confirmation to the Core IMS. 10) The P-CSCF within the Core IMS interacts with the RACS to commit all resources previously reserved. This includes opening pinholes for exchanging content control messages and/or content delivery. 11) The P-CSCF forwards the dialogue confirmation to the UE.
|
a51f761c27385e5a8c90041b2c701012
|
182 027
|
8.4.1.1.2 SCF-initiated CoD session initiation
|
Figure 21A provides an overview of the information flows for SCF-initiated CoD session initiation. ETSI ETSI TS 182 027 V3.5.1 (2011-03) 67 SCF UE MF Core IMS RACS (12) Content Control Flows (4) Session IInitiation Request (3) Session Initiation Request (2) Session Initiation Request (8) Session Initiation Response (7) Ressources Commit (6) Session Initiation Response (5) Content Control and/or Content Delivery Channel Setup (9) Session Initiation Response (1) Retrieve COD offset (optional) SSF (10) Retrieve COD offset (optional) (11) COD offset (optional) Figure 21A: SCF-initiated CoD session initiation 1) (Optionally) The SCF may retrieves the COD offset if present in service action data. 2) The SCF sends a session initiation request including the COD offset to the MF. 3) The SCF sends a session initiation request to the UE via the core IMS. 4) The Core IMS forwards the session initiation request to the UE. 5) If the UE accepts the request, signalling procedures for establishment of a content control channel and optionally (see note 2) content delivery channels take place between the UE and the MF via the SCF (see clause 8.4.1.2.2). NOTE 1: In a particular protocol realization, the messages supporting step 5 may be embedded in the messages supporting session initiation. NOTE 2: The establishment of the content delivery channel in the session initiation is only optional when network has provided information for only content control channel setup. In this case, the content delivery channel is established during session modification. 6) The UE confirms the establishment of the dialogue with the SCF. 7) The P-CSCF within the Core IMS interacts with the RACS to commit all resources previously reserved. This includes opening pinholes for exchanging content control messages and/or content delivery. 8) The core IMS forwards this confirmation to the SCF. 9) The MF confirms the establishment of the dialogue with the SCF. 10) (Optionally) UE may retrieve COD offset from service action data. 11) (Optionally) SSF may return COD offset for specified content. ETSI ETSI TS 182 027 V3.5.1 (2011-03) 68 After this point, UE may use the content control channel to request content to be streamed and the actual content will be then delivered/streamed over the content delivery channels. The content control channel will also be used to carry UE requests for controlling the streams, e.g. "pause", "fast forward", etc.
|
a51f761c27385e5a8c90041b2c701012
|
182 027
|
8.4.1.2 Media Channel Negotiation (MCN)
|
The following clauses go into details related to Content Control and/or Delivery Channel Setup steps in the session initiation in clause 8.4.1.1 (step 6 in clause 8.4.1.1.1 and step 5 in clause 8.4.1.1.2, respectively). 8.4.1.2.1 Signalling flows for the establishment of the content control and content delivery channels from MF Figure 22 shows information flows applicable when network parameters necessary to handle the CoD service are provided by the MF as part of the session initiation procedure. This set of information flows assume that the UE does not receive a description of the network parameters required from the SSF before initiating the session. SCF UE MF Core IMS RACS (44) Media Offer for Content Control and Content Delivery (42) Media Offer for Content Control and Content Delivery (41) Media Offer for Content Control and Content Delivery (45) Media Answer for Content Control and Content Delivery (47) Media Answer for Content Control and Content Delivery (48) Media Answer for Content Control and Content Delivery (43) Resources Reservation (46) Resources Reservation Figure 22: Signalling flows for the establishment of the content control and content delivery channels from MF (41) The MF initiates negotiation of a content control channel and one or more content delivery channels with the UE, by sending a media offer to the SCF. (42) The media offer is forwarded to the Core IMS. (43) The P-CSCF within the Core IMS interacts with the RACS to reserve transport resources for the content control channel and one ore more content delivery channels. (44) The P-CSCF within the Core IMS forwards the media offer to the UE. (45) The UE provides a media answer to the Core IMS. (46) The P-CSCF within the Core IMS interacts with the RACS to update the reservation (optional). ETSI ETSI TS 182 027 V3.5.1 (2011-03) 69 (47) The media answer for the content control channel and one or more content delivery channels is propagated to the SCF. (48) The SCF forwards the media answer to the MF. 8.4.1.2.2 Signalling flows for the establishment of the content control and content delivery channels from UE Figure 23 provides an overview of the information flows for UE-initiated negotiation of the network parameters necessary to handle the CoD service. This set of information flows assume that the UE receives a description of the network parameters required from the SSF before initiating the session. SCF UE MF Core IMS RACS (44) Media Offer for Content Control and Content Delivery (45) Media Answer for Content Control and Content Delivery (41) Media Offer for Content Control and Content Delivery (43) Media Offer for Content Control and Content Delivery (48) Media Answer for Content Control and Content Delivery (46) Media Answer for Content Control and Content Delivery (42) Resources Reservation (47) Resources Reservation Figure 23: Signalling flows for the establishment of the content control and content delivery channels from UE (41) The UE initiates negotiation of a content control channel and one or more content delivery channels with the MF, by sending a media offer to the Core IMS. (42) The P-CSCF within the Core IMS interacts with the RACS to reserve transport resources for the content control channel and one or more content delivery channels. (43) The media offer is forwarded to the SCF. (44) The SCF forwards the media offer to the MF. (45) The MF provides a media answer to the SCF. (46) The SCF forward the media answer to the Core IMS. (47) Within the Core IMS, the P-CSCF interacts with the RACS to update the previous reservation (optional). (48) The media answer for the content control channel and one or more content delivery channels is propagated to the UE. ETSI ETSI TS 182 027 V3.5.1 (2011-03) 70
|
a51f761c27385e5a8c90041b2c701012
|
182 027
|
8.4.1.2.3 Signalling flows for the establishment of the content control channel from UE
|
Figure 24 provides an overview of the information flows for UE-initiated establishment of the content control channel. SCF UE MF Core IMS RACS (46) Media Answer for Content Control (45) Media Answer for Content Control (41) Media Offer for Content Control (43) Media Offer for Content Control (44) Media Offer for Content Control (48) Media Answer for Content Control (42) Resources Reservation (47) Resources Reservation Figure 24: Signalling flows for the establishment of the content control channel from UE (41) The UE initiates negotiation of a content control channel with the MF, by sending a media offer to the Core IMS. (42) The P-CSCF within the Core IMS interacts with the RACS to reserve transport resources for the content control channel. (43) The media offer is forwarded to the SCF. (44) The SCF forwards the media offer to the MF. (45) The MF provides a media answer to the SCF. (46) The SCF forward the media answer to the Core IMS. (47) Within the Core IMS, the P-CSCF interacts with the RACS to update the previous reservation (optional). (48) The media answer for the content control channel is propagated to the UE.
|
a51f761c27385e5a8c90041b2c701012
|
182 027
|
8.4.2 Signalling Flows for CoD session modification
|
The CoD session modification procedure is used to add, remove or modify one or more content delivery channels in an existing session. The CoD session modification procedure is initiated by the UE or the MF. The session modification procedure shall take place immediately after the session initiation procedure (e.g. using network parameters retrieved from content control messages) when no content delivery channels were set during this previous phase. In case of a session modification, the content delivery channel setup/modification procedure is always triggered by the entity initiating the session modification.
|
a51f761c27385e5a8c90041b2c701012
|
182 027
|
8.4.2.0A UE-initiated CoD session modification
|
Figure 25 provides an overview of the information flows for UE-initiated CoD session modification. ETSI ETSI TS 182 027 V3.5.1 (2011-03) 71 Figure 25: UE-initiated CoD session modification 1) The UE initiates a session modification procedure in order to start a negotiation for one or more content delivery channel(s). 2) The session modification request is forwarded to the SCF through the Core IMS. 3) The SCF performs service authorization as described in clause 5.1. If the UE is allowed to modify the content, the SCF forwards the session modification request to the MF. 4) Procedures for establishment of a content delivery channels take place between the UE and the MF (see clause 8.4.2.1). NOTE: The messages supporting step 4 are embedded in the messages supporting session modification. 5) The MF confirms the modification of the session. 6) The SCF forwards this modification to the Core IMS. 7) The P-CSCF within the Core IMS interacts with the RACS to commit all resources previously reserved. This includes opening pinholes for content delivery. 8) The P-CSCF forwards the confirmation to the UE. After this point, UE may request content to be delivered over the content control channel and the actual content will be then delivered over the content delivery channels. The content control channel will also be used to carry UE requests for controlling the streams over the content delivery channels, e.g. "pause", "fast forward", etc. (4) Content Control and/or Content Delivery Channel Setup (7) Resources Commit SCF UE MF Core IMS RACS (1) Session Modification Request (2) Session Modification Request (3) Session Modification Request (5) Session Modification Response (6) Session Modification Response (8) Session Modification Response Content Control and Content Delivery Flows ETSI ETSI TS 182 027 V3.5.1 (2011-03) 72
|
a51f761c27385e5a8c90041b2c701012
|
182 027
|
8.4.2.0B MF-initiated CoD session modification
|
Figure 26 provides an overview of the information flows for MF-initiated CoD session modification. Figure 26: MF-initiated CoD session modification 1) The MF initiates a session modification procedure in order to start a negotiation for one or more content delivery channel(s). 2) The SCF performs service authorization as described in clause 5.1. The SCF forwards the session modification request to the MF. 3) The session modification request is forwarded to the UE by the Core IMS. 4) Procedures for establishment of a content delivery channels take place between the UE and the MF (see clause 8.4.2.2). NOTE: The messages supporting step 4 are embedded in the messages supporting session modification. 5) The UE confirms the modification of the session. 6) The P-CSCF within the Core IMS interacts with the RACS to commit all resources previously reserved. This includes opening pinholes for content delivery. 7) The Core IMS forwards this modification to the SCF. 8) The SCF forwards the confirmation to the MF. After this point, UE may send a request over the content control channel to stream content and the actual content will be then delivered over the content delivery channels. (6) Resources Commit (4) Content Control and/or Content Delivery Channel Setup SCF UE MF Core IMS RACS (1) Session Modification Request (3) Session Modification Request (2) Session Modification Request (5) Session Modification Response (7) Session Modification Response (8) Session Modification Response Content Control and Content Delivery Flows ETSI ETSI TS 182 027 V3.5.1 (2011-03) 73 The content control channel will also be used to carry UE requests for controlling the content streams e.g. "pause", "fast forward", etc. 8.4.2.1 Signalling flows for the establishment/modification of the content delivery channel from UE Figure 27 provides an overview of the information flows for UE-initiated establishment or modification of the content delivery channel. SCF UE MF Core IMS RACS (48) Media Answer for Content Delivery (46) Media Answer for Content Delivery (41) Media Offer for Content Delivery (43) Media Offer for Content Delivery (44) Media Offer for Content Delivery (45) Media Answer for Content Delivery (42) Resources Reservation (47) Resources Reservation Figure 27: Signalling flows for the establishment/modification of the content delivery channel from UE (41) The UE initiates negotiation of one or more content delivery channel with the MF, by sending a media offer to the Core IMS. (42) The P-CSCF within the Core IMS interacts with the RACS to reserve transport resources for the content delivery channels. (43) The media offer is forwarded to the SCF. (44) The SCF forwards the media offer to the MF. (45) The MF provides a media answer to the SCF. (46) The SCF forward the media answer to the Core IMS. (47) Within the Core IMS, the P-CSCF interacts with the RACS to update the previous reservation (optional). (48) The media answer for the content delivery channels is propagated to the UE.
|
a51f761c27385e5a8c90041b2c701012
|
182 027
|
8.4.2.2 Signalling flows for the modification of the content delivery channels from MF
|
Figure 28 provides an overview of the information flows for MF-initiated modification of the content delivery channel. ETSI ETSI TS 182 027 V3.5.1 (2011-03) 74 SCF UE MF Core IMS RACS (44) Media Offer for Content Delivery (42) Media Offer for Content Delivery (41) Media Offer for Content Delivery (45) Media Answer for Content Delivery (47) Media Answer for Content Delivery (48) Media Answer for Content Delivery (43) Resources Reservation (46) Resources Reservation Figure 28: Signalling flows for the modification of the content delivery channels from MF (41) The MF initiates negotiation of one or more content delivery channels with the UE, by sending a media offer to the SCF. (42) The media offer is forwarded to the Core IMS. (43) The P-CSCF within the Core IMS interacts with the RACS to reserve transport resources for the content delivery channels. (44) The P-CSCF within the Core IMS forwards the media offer to the UE. (45) The UE provides a media answer to the Core IMS. (46) The P-CSCF within the Core IMS interacts with the RACS to update the reservation (optional). (47) The media answer for the content delivery channels is propagated to the SCF. (48) The SCF forwards the media answer to the MF.
|
a51f761c27385e5a8c90041b2c701012
|
182 027
|
8.4.3 Signalling Flows for CoD session release
| |
a51f761c27385e5a8c90041b2c701012
|
182 027
|
8.4.3.1 UE-initiated session release
|
Figure 29 provides an overview of the information flows for UE-initiated session release. ETSI ETSI TS 182 027 V3.5.1 (2011-03) 75 SCF UE MF Core IMS RACS (7) Session Termination Confirm (6) Session Termination Confirm (5)Session Termination Confirm (1) Session Termination Request (3) Session Termination Request (4) Session Termination Request (2) Resources release Figure 29: UE-initiated session release 1) The UE initiate a session termination. 2) The P-CSCF interacts with the RACS to release all transport resources that had been reserved for this session. 3) The Session Termination Request is routed by the Core IMS entities up to the SCF. 4) The SCF forwards the Session Termination Request to the appropriate Media Function. 5) The Media Function (i.e. the MCF) release all resources associated with the session and returns a Session Termination Confirm. 6) The SCF forwards the Session Termination Confirm to the Core IMS. 7) The P-CSCF forwards the Session Termination Confirm to the UE.
|
a51f761c27385e5a8c90041b2c701012
|
182 027
|
8.4.3.2 SCF-initiated session release
|
Figure 30 provides an overview of the information flows for SCF-initiated session release. ETSI ETSI TS 182 027 V3.5.1 (2011-03) 76 SCF UE MF Core IMS RACS (6) Session Termination Confirm (7) Session Termination Confirm (2)Session Termination Confirm (5) Session Termination Request (3) Session Termination Request (1) Session Termination Request (4) Resources release Figure 30: SCF-initiated session release 1) The SCF initiates a session termination towards the MF. 2) The Media Function (i.e. the MCF) releases all resources associated with the session and returns a Session Termination Confirm. 3) The SCF initiates a session termination towards the UE. 4) The P-CSCF interacts with the RACS to release all transport resources that had been reserved for this session. 5) The Session Termination Request is routed by the Core IMS entities up to the UE. 6) The UE returns a Session Termination Confirm to the Core IMS. 7) The Core IMS forwards the Session Termination Confirm to the SCF.
|
a51f761c27385e5a8c90041b2c701012
|
182 027
|
8.4.3.3 MF-initiated session release
|
Figure 31 provides an overview of the information flows for MF-initiated session release. ETSI ETSI TS 182 027 V3.5.1 (2011-03) 77 SCF UE MF Core IMS RACS (5) Session Termination Confirm (6) Session Termination Confirm (7)Session Termination Confirm (4) Session Termination Request (2) Session Termination Request (1) Session Termination Request (3) Resources release Figure 31: MF-initiated session release 1) The MF initiates a session termination towards the SCF. 2) The SCF forwards the session termination request to the Core IMS. 3) The P-CSCF interacts with the RACS to release all transport resources that had been reserved for this session. 4) The Session Termination Request is routed by the Core IMS entities up to the UE. 5) The UE returns a Session Termination Confirm to the Core IMS. 6) The Core IMS forwards the Session Termination Confirm to the SCF. 7) The SCF forwards the Session Termination Confirm to the MF that releases all resources associated with the session.
|
a51f761c27385e5a8c90041b2c701012
|
182 027
|
8.4.4 Signalling Flows for CoD session transfer
|
The CoD session transfer is used to transfer an on-going CoD session from one terminal called transferor UE to another one called transferee UE. The transferor UE and the transferee UE must be served by different or the same SCF. The session transfer could be handled directly between both terminals or can be managed by the transferee SCF. In the latter case, the transferor SCF will initiate a CoD session with the transferee UE at session transfer request from the transferor UE. NOTE: 3GPP Release 9 specifications are limited to UE centric push mode for session transfer, i.e. only the case in clause 8.4.4.1 is addressed by 3GPP in release 9. For reference, the related 3GPP specifications are TS 123 237 [17] and TS 124 237 [18].
|
a51f761c27385e5a8c90041b2c701012
|
182 027
|
8.4.4.1 Terminal centric session transfer pushed from transferor UE to transferee UE
|
Figure 31A provides an overview of the information flows for direct CoD session transfer between the transferor UE (UE1) and the transferee UE (UE2). For clarity purpose, core-IMS is not indicated in the figure but all messages go through it. In this scenario the transferor UE discovers the devices to which a potential transfer can be initiated. The transferor UE selects a devices and initiates the procedure. ETSI ETSI TS 182 027 V3.5.1 (2011-03) 78 Figure 31A: Terminal centric session transfer pushed from transferor UE to transferee UE 1) UE1 has initiated a dialogue to the CoD service as defined in clause 8.4.1. A session is on going with the MF1. 2) The user decides to transfer the session to another device. UE1 performs device discovery as defined in TS 123 237 [17], and TS 124 237 [18] to discover the devices that it can transfer the session to. 3) The UE1 may send an offset notification to the SCF. If the SCF has not received an offset notification from UE1 it uses CoD Service Action Data requested by the SCF procedure to acquire an offset. (3) Offset Notification SCF UE1 MF2 UE2 (4) Session Transfer Request MF1 (5) Session Transfer Request (8) Session Transfer Start Notification (6) Session Transfer Response (7) Session Transfer Response (10) Session Transfer Complete Notification (1) Session Initiation (11) Session termination (9) Session Initiation (2) Discover devices ETSI ETSI TS 182 027 V3.5.1 (2011-03) 79 4) UE1 sends a Session Transfer Request to the SCF via the core-IMS containing Session transfer identifier- STI (identity of the session to be transferred). The SCF obtains the CoD content-id, and perform service authorisation and checks that the user is authorised to perform session transfer. The SCF also obtains the UE2 identity and the target user identity from the incoming request. To allow UE2 to acquire the content id used to set up the initial session, UE1 shall include the content id in the session transfer request. 5) The Session Transfer Request, including the offset, is forwarded from the SCF to the UE2 via the Core-IMS. 6) UE2 receives an invitation to initiate a CoD session for the content indicated by the content-id. It acknowledges the Request by sending a Session Transfer Response to the SCF via the Core-IMS. 7) The SCF forwards the Session Transfer Response to the UE1 via the Core-IMS. 8) The UE2 informs the UE1 that it initiates the CoD session initiation by sending a Session Transfer Start Notification to the UE1 via the core-IMS. NOTE 1: This message can optionally go through the SCF. 9) CoD session initiation between the UE2 and MF2 via core-IMS is done as defined in clause 8.4.1.1.1. 10) The UE2 informs the UE1 that CoD session initiation is complete by sending a Session Transfer Complete Notification to the UE1. NOTE 2: This message can optionally go through the SCF. 11) The UE1 terminates the CoD session with the MF1 as defined in clause 8.4.3.1. 8.4.4.2 Network centric session Transfer pushed from transferor UE to transferee UE Figure 31B provides an overview of the information flows for CoD session transfer between the transferror UE (UE1) and the transferee UE (UE2) managed by the transferor SCF. For clarity purpose, core-IMS is not indicated in the figure but all messages go through it. ETSI ETSI TS 182 027 V3.5.1 (2011-03) 80 Figure 31B: Network centric session Transfer pushed from transferor UE to transferee UE 1) UE1 has initiated a dialogue to the CoD service as defined in clause 8.4.1. A session is on going with the MF1. The user decides to transfer the session to the another device. UE1 performs device discovery as defined by TS 123 237 [17], and TS 124 237 [18]. 2) The UE1 may send an offset notification to the SCF. If the SCF has not received an offset notification from UE1 it uses CoD Service Action Data requested by the SCF procedure to acquire an offset. 3) UE1 sends a Session Transfer Request to the SCF via the Core- containing the Session Tranfer Identfier-STI (the identity of the session to be transferred) and if necessary the UE2 ID (e.g. if the user ID corresponds to multiple UEs). The SCF obtains the CoD content-id, and performs service authorisation and also checks that the user is authorised to perform session transfer. The SCF also obtains the UE2 identity and the target user identity from the incoming request. To allow UE2 to acquire the content id used to set up the initial session, UE1 shall include the content id in the session transfer request. 4) The SCF replies by a Session Transfer Response to the UE1. UE1 MF 2 SCF UE2 (4) Session Transfer Request MF1 (1) Session Initiation (5) Session Transfer Response (6) Session Transfer Start Notification (7) Session Initiation (8) Session Transfer Complete Notification (9) Session termination (3) Offset Notification (2) Discover devices ETSI ETSI TS 182 027 V3.5.1 (2011-03) 81 5) The SCF informs the UE1 that it initiates the CoD session initiation by sending a Session Transfer Start Notification to the UE1 via the core-IMS. 6) SCF-initiated CoD session initiation between the UE2 and MF2 is done by the SCF as defined in clause 8.4.1.1.2. 7) The SCF informs the UE1 that CoD session initiation is complete by sending a Session Transfer Complete Notification to the UE1. 8) The SCF terminates the CoD session between the UE1 and the MF1 as defined in clause 8.4.3.2. 8.4.4.3 Session Replication pushed from transferor UE to transferee UE This scenario is identical to the session transfer in clause 8.4.4.1 with the exception that the last step of terminating the session towards the transferor UE is not carried out. Hence, the transferor UE maintains his session as well. At the end of the procedure both the transferor UE and the transferee UE have independent sessions watching same content from the same or a different MF. 8.4.4.4 Session Transfer pulled by the transferee UE Figure 31C provides an overview of the information flows for direct CoD session transfer between the transferor UE (UE1) and the transferee UE (UE2). In this scenario the transferee UE discovers the devices and the active sessions on these devices that he can transfer to his own device. ETSI ETSI TS 182 027 V3.5.1 (2011-03) 82 Figure 31C: Session Transfer pulled by the transferee UE 1) UE1 has initiated a dialogue to the CoD service as defined in clause 8.4.1.1.1. A session is on going with the MF1. 2) The user decides to go to his device UE2, to transfer an ongoing CoD session from device UE1. The user on UE2 performs device discovery and requests from SCF the active sessions on these devices, as defined by TS 123 237 [17], and TS 124 237 [18]. SCF UE1 MF2 UE2 MF1 (4) Session Transfer Start Notification (5) Session Transfer Complete Notification (6) Session termination (3) Session Initiation Core IMS (1) Session Initiation (2) Discover devices and active sessions ETSI ETSI TS 182 027 V3.5.1 (2011-03) 83 3) The user on UE2 sends a Session initiation to the SCF via the core-IMS, to transfer the session from device UE1. The UE includes the Session Transfer Identfier-STI (identity of the session to be transferred) in his request. The SCF obtains the CoD content-id, from the incoming session initiation request (acquired by UE2 in step2), and performs service authorisation and checks that the user is authorised to perform session transfer. UE1 may send an offset notification to SCF. If the SCF has not received an offset notification from UE1 it uses network initated content marker procedure to acquire an offset. 4) UE2 informs the UE1 that it initiates the CoD session initiation by sending a Session Transfer Start Notification to the UE1 via the core-IMS. NOTE 1: This message can optionally go through the SCF. 5) The UE2 informs the UE1 that CoD session initiation is complete by sending a Session Transfer Complete Notification to the UE1. NOTE 2: This message can optionally go through the SCF. 6) The UE1 terminates the CoD session with the MF1 as defined in clause 8.4.3.1. 8.4.4.5 Session Replication Between transferor to transferee in a pull mode transfer This scenario is identical to the session transfer in clause 8.4.4.4 with the exception that the last step of terminating the session towards the transferor UE is not carried out. Hence, the transferor UE maintains his session as well. At the end of the procedure both the transferor UE and the transferee UE have independent sessions watching same content from the same or a different MF.
|
a51f761c27385e5a8c90041b2c701012
|
182 027
|
8.4.5 Signalling flows for CoD service action data update/Requests
|
CoD service action data may be updated by UE as described in clause 8.4.5.1 and generically may be updated by MF as described in clause 8.4.5.2. Furthermore, CoD service action data requests may be initiated by the SCF as described in clause 8.4.5.3.
|
a51f761c27385e5a8c90041b2c701012
|
182 027
|
8.4.5.1 CoD service action data updated by UE
|
The UE use the procedure described in figure 31D to save a current CoD SAD. This procedure may occur at any time. The most common use case is the stop CoD viewing request. Figure 31D: CoD service action data updated by UE 1) The UE sends a CoD SAD update request to save the current position of the content. This request may also include a indicator to inform the SCF of the reason for the CoD SAD update. 2) The IMS core forwards this request to the SCF. SCF UE Core IMS (1) CoD SAD update request (2) CoD SAD update Request (5) CoD SAD update Response (4) CoD SAD update Response (3) Save content offset ETSI ETSI TS 182 027 V3.5.1 (2011-03) 84 3) The SCF store this offset as service action data for this user. 4) The SCF confirms the CoD SAD update. 5) The IMS core forwards the response to the UE.
|
a51f761c27385e5a8c90041b2c701012
|
182 027
|
8.4.5.2 CoD service action data updated by MF
|
The procedure described in figure 31E is used to save a CoD service action data by MF. This CoD SAD may need to be updated for example when a user pauses a streaming, terminates the session or if the MF detects that the UE becomes unexpectedly offline. Figure 31E: CoD service action data updated by MF 1) CoD session initiation is performed as described in clause 8.4.1. 2) MF detects a pause, end of session or that the UE becomes offline unexpectedly. The MF may decides to send changes of SAD to SCF. 3) MF sends a CoD SAD update request to save the current CoD SAD. This request may also include a indicator to inform the SCF of the reason for the CoD SAD update. 4) The IMS core forwards this request to the SCF. 5) The SCF updates the CoD SAD. 6) The SCF confirms the CoD SAD update. 7) The IMS core forwards the response to the MF. ETSI ETSI TS 182 027 V3.5.1 (2011-03) 85
|
a51f761c27385e5a8c90041b2c701012
|
182 027
|
8.4.5.3 CoD Service Action Data requested by the SCF
|
This procedure allows the SCF to acquire the current offset in a streamed content during an ongoing session in case such information is not available and required. Figure 31F provides an overview of the information flow for a CoD SAD request by the SCF to acquire the offset. This procedure can occur at any time during IPTV services (CoD/N-PVR/, etc.). Figure 31F: SCF SAD Request Procedure 1) The SCF sends a SAD request to the MF, via the IMS core, to request the offset during an ongoing IPTV service. 2) The IMS core forwards this request to the appropriate MF for the IPTV service. 3) The MF acquires the requested information. 4) The MF returns to core IMS the requested information in a SAD response. 5) The IMS core forwards the response to the SCF. 8.4.6 Signalling flows for generating playlist by SCF and sending playlist information from SCF to MF during CoD session initiation Figure 31G provides an overview of the information flows for playlist generation by SCF and sending playlist information from SCF to MF when UE initiated CoD session. SCF Core IMS MF (1) IPTV SAD Request (3) MF fetches the information (2) IPTV SAD Request (4) IPTV SAD Response (5) IPTV SAD Response ETSI ETSI TS 182 027 V3.5.1 (2011-03) 86 Figure 31G: Playlist communication during CoD session initiation 1) The UE initiates a dialogue to the CoD service as defined in clause 8.4.1.1.1, step 3. 2) The session initiation request is routed by the Core IMS entities up to the SCF in charge of the requested CoD service as defined in clause 8.4.1.1.1, step 4. 3) The SCF performs service authorization as described in clause 5.1. If the UE is allowed to access the service, the SCF generates playlist information or fetches a pre-configured playlist from a repository, based on the content ID carried in the session initiation request. Other information (e.g. the User ID, etc.) may also be used to generate the playlist. The playlist contains the list of content ID to be played and optionally content duration and restricted trick-play indication for each content. The data model for playlist is defined in clause 8.4.6.1. 4) The SCF selects an appropriate MF and forwards the session initiation request including playlist information to the selected MF. NOTE 1: The above procedure supports only content delivery from one single MF. 5) The MF interprets playlist information and prepares for content delivery. 6) Content Control and or Content Delivery Channel Setup procedures and finalization of the CoD Session initiation procedure follow clause 8.4.1.1.1, steps 6-11. NOTE 2: During this signalling, the UE might learn that a playlist was generated and act accordingly. Depending on the service type, the UE might already have learned the playlist in advance of service invocation.
|
a51f761c27385e5a8c90041b2c701012
|
182 027
|
8.4.6.1 IPTV Data Model for playlist
| |
a51f761c27385e5a8c90041b2c701012
|
182 027
|
8.4.6.1.1 General
|
This clause defines the data model for playlist for IPTV CoD/N-PVR/Ad content delivery, which can be used for content delivery. UE RACS Core IMS SCF MF (1) Session Initiation Request (2) Session Initiation Request (5) playlist interpretation (4) Session Initiation Request including playlist information 6) Steps 6-11 of 8.4.1.1.1 (3) playlist generation/ fetching ETSI ETSI TS 182 027 V3.5.1 (2011-03) 87 Figure 31H: IPTV playlist
|
a51f761c27385e5a8c90041b2c701012
|
182 027
|
8.4.6.1.2 ContentD
|
This attribute identifies the associated content. • In case of CoD, it shall be set to the "CoDId" (see clause 7.4.1). • In case of N-PVR, it shall be set to the "N-PVRContentId" (see clause 7.4.1). • In case of Ad, it shall contain the ad content id (see clause 8.14.1).
|
a51f761c27385e5a8c90041b2c701012
|
182 027
|
8.4.6.1.3 Duration
|
This optional attribute may be used to identify the duration of IPTV content.
|
a51f761c27385e5a8c90041b2c701012
|
182 027
|
8.4.6.1.4 Begin Time
|
This optional attribute may be used to identify the starting point of IPTV content.
|
a51f761c27385e5a8c90041b2c701012
|
182 027
|
8.4.6.1.5 Restricted trick play
|
This optional attribute may be used to identify whether trick play control for IPTV content is allowed or not. 8.4.7 Signalling flows for generating playlist by SCF and sending playlist information from SCF to MF during an existing CoD session Figure 31I provides an overview of the information flows for playlist generation by SCF and sending playlist information from SCF to MF during an existing CoD session. This playlist may be a new playlist or an update. IPTV playlist IPTV Content ContentID: String Duration: String Begin Time: String Restricted trick play: boolean 1…n ETSI ETSI TS 182 027 V3.5.1 (2011-03) 88 Figure 31I: Playlist communication during an existing CoD session 1) A CoD session has been successfully established as described in clause 8.4.1.1. 2) Due to detecting an event, the SCF may choose to generate or update playlist information for the ongoing CoD session. The playlist contains the list of content ID to be played and optionally content duration and restricted trick-play indication for each content. 3) The SCF passes the playlist information to the MF. 4) The MF interprets the playlist information and acts accordingly. This may have immediate impact on the ongoing media channel. NOTE: A new or updated playlist might make a modification of the session necessary.
|
a51f761c27385e5a8c90041b2c701012
|
182 027
|
8.4.8 Content switch procedure within a CoD playlist
|
Figure 31J provides an overview of the information flows for content switch within a CoD playlist. UE RACS Core IMS SCF MF (1) Existing CoD session (2) Detection of event and playlist generation/update (3) playlist information (4) playlist interpretation ETSI ETSI TS 182 027 V3.5.1 (2011-03) 89 Figure 31J: Content switch within a CoD playlist 1) The UE initiates a dialogue to the CoD service as defined in clause 8.4.6. In addition,the playlist which is generated by the SCF as defined in clause 8.4.6 may be forwarded to the UE by the MF for user to choose the subsequent content. 2) The UE sends the content switch request related to the selected content within the playlist. The similar mechanism defined in TS 126 234 [i.20] clause 5.5.4.2 may be used here. 3) The MF checks that the selected content is referred in the playlist, and confirms the request. 4) The MF starts to deliver the new content, reusing the established media channel in case of the numbers of channels and QoS requirements are the same as the previous channel. NOTE: Session modifications may be needed if QoS requirements of the new content is not the same as the previous one.
|
a51f761c27385e5a8c90041b2c701012
|
182 027
|
8.5 PVR service procedures
| |
a51f761c27385e5a8c90041b2c701012
|
182 027
|
8.5.0 PVR use for non-BC services
|
Although the procedures in the following clauses focus on PVR-recording of BC services (clause 8.3), they may be applicable to the recording of other IPTV services. Depending on the service, specific requirements on e.g. user subscription and profile may apply. Examples such as Content on Demand (clause 8.4) and Personal Service Composition (clause 8.22), among others, can be accommodated by using the appropriate IPTV Content Identifier and initiating the appropriate type of IPTV session. Details on PVR usage for each of these services are not specified in the present document.
|
a51f761c27385e5a8c90041b2c701012
|
182 027
|
8.5.0A Signalling Flows for PVR Using Impulsive Request
|
Figure 32 depicts the typical steps that occur when the UE makes an impulsive request for a PVR service. Core IMS SCF MF (1).Playlist communication during CoD session initiation(in Clause 8.4.6) (4).New content delivery (2).Request for content switch (3). Content switch response UE ETSI ETSI TS 182 027 V3.5.1 (2011-03) 90 Figure 32: PVR capture using impulsive request Specifics of interaction with RACS have been removed for purpose of simplification. It will follow the same procedures as outlined in the BroadcastTV and COD flows in clauses 8.3 and 8.4. 1) UE initiates Broadcast TV session following procedures specified in clause 8.3.1.1.1. 2) The user (on UE) makes a request to the SCF through the core IMS to capture the currently watched live content. During this step, the UE identifies to the SCF the content to be recorded using the IPTV content identifier, see Annex I.1, and possibly other parameters (e.g. time channel delimitation code, beginning date, end date, duration, etc.). The UE also indicates the type of recording (N-PVR or C-PVR) and the target UE. The target UE identifies either the UE that is asked to record the content in case of C-PVR or the UE where the content will be downloaded, if required, in case of N-PVR. The SCF may override the PVR request from the target UE (N-PVR or C-PVR) based on the service provider's specific service policy in SCF and the PVR subscription. In case of N-PVR, The SCF may check the N-PVR max-duration parameter to decide whether to allow the user to capture the selected live content. Instead of specifying a time limit, the UE may specify the current ProgrammeID indicating that the current Broadcast programme needs to be captured. The SCF answers with an N-PVR content capture response indicating to the user if capture of the content is allowed or not. In case of C-PVR or N-PVR with download, the SCF will check whether the target UE is authorized to record or receive the selected live content, and in the case of one UE-A scheduling C-PVR Service Capture Request for another UE-B, SCF further checks that UE-B has C-PVR terminal capabilities and UE-A is authorized by UE-B to make C-PVR Capture Requests on behalf of UE-B. Optionally, the SCF notifies the target UE of the storage requirements for the actual recording. For example, SCF calculates the required storage space according to the time duration and the content metadata information, the target UE checks the local storage capabilities and reserves corresponding space for the recording. 3A) In case of N-PVR, the SCF records the PVR/BC bookmark information as part of the IPTV service action data and then follows relevant procedures to initiate the recording of the content by the MF. UE CORE IMS SCF MF SSF (2). PVR content capture request (2). PVR content capture response (1).Session initiation procedures for broadcast Session (3 A) SCF records N-PVR/BC Information and initiates the recording of the content towards MF (4). Broadcast Session termination (2). PVR content capture request (2). PVRB content capture response (3 B) SCF records C-PVR/BC Information and initiates the recording of the content towards the UE. ETSI ETSI TS 182 027 V3.5.1 (2011-03) 91 3B) In case of C-PVR, the SCF records the PVR/BC bookmark information as part of the IPTV service action data and then follows procedures in clause 8.5.2.2 to initiate the recording of the content by the specified client device. 4) The UE initiates Broadcast session termination procedures as defined in clause 8.3.3.1. Depending on the usage model, the UE initiates the Broadcast session termination procedure immediately after issuing the PVR capture request or it may do it at later point. The former would be the typically be the case of "Park and Pickup TV". NOTE: In case of N-PVR, The SCF may check if the N-PVR content is Time-shifted content, or was already pre-recorded for another user. Then the MF does not need to record the same content according to the information from SCF to avoid that the same content is recorded repeatedly. 8.5.0B Signalling flows for the PVR off-line capture request Figure 33 depicts the typical steps that occur when the UE makes an offline request for a PVR service. Figure 33: PVR Capture procedures using offline request 1) The user (on UE) makes a request to the SCF through the core-IMS to capture a particular live content. During this step, the UE identifies to the SCF the content to be recorded using the IPTV content identifier, see clause I.1, and possibly other parameters (e.g. time channel delimitation code, beginning_date, end_date, duration, etc.). The UE also indicates the type of recording (N-PVR or C-PVR) and the target UE. The target UE identifies either the UE that is asked to record the content in case of C-PVR or the UE where the content will be downloaded, if required, in case of N-PVR. The SCF may override the PVR request from the target UE (N-PVR or C-PVR) based on the service provider's specific service policy in SCF and the PVR subscription. The SCF may check the N-PVR max-duration parameter to decide whether to allow the user to capture the selected live content. NOTE 1: The content capture request may go to the SSF instead of the SCF. This implies that the SSF needs to communicate with the SCF. A reference point for direct communication between the SSF and SCF is out of scope for this release. UE CORE IMS SCF MF SSF (1). PVR content capture request (1). PVR content capture response (2 A ) Store N-PVR/BC Information and initiate the recording of the content (1). PVR content capture request (1). PVR content capture response (2 B) Store C-PVR/BC Information and initiate the recording of the content ETSI ETSI TS 182 027 V3.5.1 (2011-03) 92 In case of C-PVR or N-PVR with download, the SCF will check whether the target UE is authorized to record or receive the selected live content, and in the case of one UE-A scheduling C-PVR Service Capture Request for another UE-B, SCF further checks that UE-B has C-PVR terminal capabilities and UE-A is authorized by UE-B to make C-PVR Capture Requests on behalf of UE-B. Optionally, the SCF notifies the target UE of the storage requirements for the actual recording. For example, SCF calculates the required storage space according to the time duration and the content metadata information, the target UE checks the local storage capabilities and reserves corresponding space for the recording. 2) The SCF stores the PVR/BC information. In case of N-PVR, as described in step 2A), the SCF follows relevant procedures to initiate the recording of the content by the MF. In case of C-PVR, as described in step 2B), the SCF follows procedures in clause 8.5.2.2 to initiate the recording of the content by the specified client device. NOTE 2: In case of N-PVR, The SCF may check if the N-PVR content is Time-shifted content, or was already pre-recorded for another user. Then the MF does not need to record the same content according to the information from SCF to avoid that the same content is recorded repeatedly.
|
a51f761c27385e5a8c90041b2c701012
|
182 027
|
8.5.1 Network PVR service procedures
|
Network PVR (N-PVR) service is used by the UE to ask for a capture of live content by the network and to access it later on. The N-PVR service procedures comprise two major steps: Step 1: Request for N-PVR Service Capture Request. The UE sends an N-PVR content capture request to the SCF. This request can be: • an impulsive request: in this case, a BC service is already activated. The UE asks the SCF to record the live content currently being watched. This may be a request to record current Broadcast Programme or a sequence of programmes from a given position in time (BC bookmark).This is as discussed in clause 8.5.1.1.1. • an off-line request: the UE asks the SCF to record a particular live content unrelated to any active BC session. may be a request to record current Broadcast Programme or a sequence of programmes This is as discussed in clause 8.5.1.1.2. Step 2: Request for N-PVR service Once recorded, the user can make a request for previously recorded N-PVR request. The N-PVR content can be resumed on the same UE or different UE belonging to user from start or from the point at which the content recording was requested. The N-PVR content may have also been downloaded to the UE making local watching of the content possible. NOTE: The case when an N-PVR service capture is done as an impulsive request and is requested later from the same or another UE from the point at which the content recording was requested can be viewed as a case of "Park and Pickup TV" as described in clause 3.1. In this case, the currently active Broadcast TV programme or channel that was scheduled for an impulsive N-PVR capture request can be requested at a later point on the same or different UE from the previously paused/parked point.
|
a51f761c27385e5a8c90041b2c701012
|
182 027
|
8.5.1.1 Signalling Flows for Network-PVR Service Capture Request
|
This can be handled as an off-line request or as an impulsive request.
|
a51f761c27385e5a8c90041b2c701012
|
182 027
|
8.5.1.1.1 Signalling Flows for Network-PVR Using Impulsive Request
|
Refer to clause 8.5.0A.
|
a51f761c27385e5a8c90041b2c701012
|
182 027
|
8.5.1.1.2 Signalling flows for the Network-PVR off-line capture request
|
Refer to clause 8.5.0B. ETSI ETSI TS 182 027 V3.5.1 (2011-03) 93
|
a51f761c27385e5a8c90041b2c701012
|
182 027
|
8.5.1.2 Signalling flows for Network-PVR content session
|
Figure 34 depicts the typical steps that occur when the UE makes a request to retrieve/resume previously recorded N-PVR content. NOTE: If the N-PVR content has been previously downloaded to the UE, it can watch it locally without using the following procedures. Figure 34: Signalling flows for Network-PVR content session 1) The SSF presents the UE with listing of available N-PVR Broadcast TV content captured via impulsive or offline capture requests, from which the user can select. In addition the "BC bookmark" information could be presented by the SSF else the UE can make a separate request to retrieve it from the SCF as specified in step (3). 2) The UE initiates an N-PVR session. The N-PVR session is equivalent to the CoD session. Therefore procedures defined in clause 8.4.1.1.1 apply. 3) The UE may request to the SCF through the core-IMS BC bookmark information pertaining to the Broadcast TV programme(s) that was previously requested to be recorded. NOTE 1: Instead of having the UE retrieve the BC bookmark information as in Step (1) or (3), it may be possible for SCF to directly send the BC bookmark information from IPTV service action data to the MCF. Details of the procedures are out of scope for this release. NOTE 2: This is a logical step. For efficiency purposes it may be combined with step (2). 4) The UE makes a request to play the content from specified bookmarked location. 5) This includes procedures for trick play control of the resumed BroadcastTV stream. UE CORE IMS SCF (2) N-PVR content session initiation MF SSF (6). N-content session modification/termination (1). N-PVR content selection request (1). N-PVR content selection response (3). NPVR/BC Bookmark service action data request (3). NPVR/BC bookmark service action data response (5) Content Control Flows (4) Request to play stream from start or recorded position (3). NPVR/BC Bookmark service action data request (3). NPVR/BC bookmark service action data response ETSI ETSI TS 182 027 V3.5.1 (2011-03) 94 6) When the UE wishes to modify to terminate the resumed BC programme, it follows session termination procedures as specified in clauses 8.4.2.1 and 8.4.3.1.
|
a51f761c27385e5a8c90041b2c701012
|
182 027
|
8.5.2 Client PVR service procedures
|
Client PVR (C-PVR) service is used by the UE to ask for a capture of live content locally or by the remote client device and to access the recorded content later on. NOTE 1: In case of local capture requests that do not need network IPTV management or authorization, the recording can be handled locally on the client without SCF involvement. The procedures for local recording on client without SCF involvement is outside scope of specification. The C-PVR service procedures comprise three major steps: Step 1: Initiate C-PVR Service Capture Request. The UE sends a C-PVR content capture request to the SCF. This request can be an impulsive request or an off-line request. Impulsive request and off-line request are the same with the definitions in clause 8.5. This step is used for SCF to perform C-PVR service authorization, or where one UE schedules the C-PVR task for a future time or for another UE. NOTE 2: If further mechanisms are required to protect the digital rights of the content, the system could use DRM to prohibit unauthorized access to the content. Step 2: Request for initiation of the C-PVR recording session. When the event for the C-PVR recording have been reached (e.g. beginning time of a TV program), the SCF initiates a request to UE to trigger the initiation of the C-PVR recording session and record the content. NOTE 3: In case the UE makes an impulsive request for a C-PVR service, the existing BC session may be reused, thus the step 2 is optional. NOTE 4: The SCF may not be required to trigger the C-PVR recording, e.g. in the case where the UE directly initiates a recording session by a timer, external trigger, or by user control. These procedures are out of scope of the current specification Step 3: Access the recorded content. Once recorded, The C-PVR content can be resumed on the UE which stored the content from the point at which the content recording was requested. NOTE 5: Since the content is stored on the UE, it will not be required to have any further interaction between the UE and any other network entities to either access or play recorded content in this step.
|
a51f761c27385e5a8c90041b2c701012
|
182 027
|
8.5.2.1 Signalling Flows for Client-PVR Service Capture Request
| |
a51f761c27385e5a8c90041b2c701012
|
182 027
|
8.5.2.1.1 Signalling Flows for Client-PVR Using Impulsive Request
|
Refer to clause 8.5.0A.
|
a51f761c27385e5a8c90041b2c701012
|
182 027
|
8.5.2.1.2 Signalling flows for the Client-PVR off-line capture request
|
Refer to clause 8.5.0B.
|
a51f761c27385e5a8c90041b2c701012
|
182 027
|
8.5.2.2 Signalling flows for Client-PVR recording session
|
Figure 34A depicts the typical steps when the SCF makes a request to initiate the recording of the content. For the scenario when the UE makes an impulsive request for a C-PVR service, the existing BC session may be reused if one exists instead of the following procedures. ETSI ETSI TS 182 027 V3.5.1 (2011-03) 95 Figure 34A: Signalling flows for Client-PVR recording session 1) The SCF detects the event that triggers the C-PVR service, e.g. when the BC program is ready to be recorded. The SCF initiates a notification request to the UE designated by the C-PVR content capture request to record the content, and the notification request carries parameters to identify the content to be recorded (e.g. BC service id and or current BC Programme ID, time channel delimitation code, beginning date, end date, duration, etc.) and indicates that the content should be recorded. NOTE: The notification request procedures are the same as sending notification using signalling path specified in clause 8.11.1.1. 2) UE initiates BC session initiation procedures as specified in clause 8.3.1.1.1, and after the content delivery channel setup, the UE joins multicast channels and receives multicast flows. 3) The UE records the multicast flows. 4) When the end time of the recording is reached, the UE or SCF initiates BC session release procedures as specified in clause 8.3.3.
|
a51f761c27385e5a8c90041b2c701012
|
182 027
|
8.5.3 PVR content update procedures
|
Figure 34B: PVR content update procedure UE CORE IMS SCF SSF (1). PVR content update request (3). PVR content update response (2) Apply PVR Information update (1). PVR content update request (3). PVR content update response Core IMS BC-SCF UE C-PVR-SCF (1) Notification procedure using signalling path (in Clause 8.11.1.1) ECF/EFF (3) Content Delivery Flows (4) Broadcast Session Release (In Clause 8.3.3) (2) BC Session Initiation (in Clause 8.3.1) (3) Record the multicast flows SCF ETSI ETSI TS 182 027 V3.5.1 (2011-03) 96 1) The UE sends a PVR content update request to change information on existing PVR content capture request or existing PVR content. It includes the PVR content ID and the related change request: - Cancellation of a content capture request. - Modification of recording parameters (e.g. time range). - Deletion of a recorded content. 2) The SCF checks if the request is valid (e.g. the PVR Id exists, the time range modification is possible, etc.) and applies the PVR content update. NOTE: In case of N-PVR content deletion request, the SCF deletes the related entry in the PVR table for that user. It can also take appropriate action to delete the related content in case the content is recorded only for that user. 3) The SCF sends a PVR Content Update response to the UE via the core IMS. In case of C-PVR, the UE applies the PVR content update (e.g. it deletes the related content).
|
a51f761c27385e5a8c90041b2c701012
|
182 027
|
8.6 Time Shift service procedures
|
The Time Shift service is used by the UE to view a programme that has already occurred or started. It is necessary for the IPTV operator to store a programme in order for this service to be available. Note that unlike N-PVR it is not necessary for a UE to indicate that a programme shall be recorded but it is not always the case that a programme is Time Shift enabled. The time to live for Time Shifted enabled programmes have a different expiration time compared to N-PVR (example 1 week compared to possible 6 months for N-PVR). For a programme that has not finished it is possible that the UE catches up with the broadcasted programme sent in real time. The user selects timeshift content from the information provided by the SSF; just as any other CoD content. Consequently initiation and termination of time-shift sessions are exactly the same as for CoD, as described in clauses 8.4.1 and 8.4.3 respectively. Modification of the session is also the same as for the CoD service, as described in clause 8.4.2, except for the special case when the timeshift session catches up with real time, at which time the session may be modified to switch over to multicast. In this case the same flows as for trickplay TV will be used.
|
a51f761c27385e5a8c90041b2c701012
|
182 027
|
8.7 Preview procedures
|
8.7.1 Preview procedures for BC service The preview content of BC service may have lower bit-rate compared with the corresponding regular BC content, hence requires lower bandwidth. The BC content preview procedures may take place in either one of the following cases: 1) Multi-screen BC preview: Preview the BC service before the users decide to enjoy it in a full screen mode, where the preview content is provided through a multi-screen mode (e.g. PiP, Mosaic), or 2) Single-screen BC preview: Preview the specific BC program before the users decide to pay for it, where the regular BC service procedures of clause 8.3.1 apply before some notification or purchase procedure can take place. NOTE: How the purchase procedure is activated, as well as the concrete flows for a commercial purchase are out scope of the present document. ETSI ETSI TS 182 027 V3.5.1 (2011-03) 97
|
a51f761c27385e5a8c90041b2c701012
|
182 027
|
8.7.1.1 Session initiation procedures for multi-screen BC preview
|
The procedures described in clause 8.3.1.1 apply for multi-screen BC preview session initiation, with the following differences: • The initiation request carries the BC service IDs available for preview, and the maximum bandwidth needed for muti-screen preview. In case there is a primary stream (i.e. a regular BC service) besides the preview streams, the related regular BC service IDs are also carried in the initiation request; NOTE: In case of multiple media channels, either a single session can be used to set up all media channels, or one session per media channel can be used. In either case, existing procedures for BC session initiation apply. • Multiple media channels are established for multi-screen preview, and channel change is enabled for each media channel. 8.7.1.2 Procedures for transition between multi-screen BC preview and regular BC service The transition between the multi-screen BC preview and a regular BC service may take place e.g. when one preview channel is selected for full-screen viewing. The transition can be achieved by the actions of channel switching, channel join or channel leave, e.g. channel switching on the primary channel and channel leave/join on the preview channels at the same time. The preview session may be modified according to the change on the network parameters, e.g. bandwidth. 8.7.2 Preview procedures for COD service The CoD content preview procedures may take place before the users decide to obtain some particular CoD content. The preview content may have its own content identifier to enable the content selection (e.g. from the content guide), in which case the preview procedures can refer to procedures specified in clause 8.4. The preview content may also share the content identifier with the regular CoD content, while variation of the regular CoD content (e.g. segment collection, lower bit-rate transcoding etc.) is delivered to the UE based on criteria such as content metadata or policy of service provider. In the case of sharing identifier, the additional preview indicator should be present during session initiation procedure by the UE, and the MF is informed of preview indicator to deliver content for preview (e.g. segment collections, lower bit-rate stream). The main procedure for sharing identifier preview complies with 8.4.1 signalling flows for CoD session initiation with the following differences: 1) The session initiation request message initiated by the UE (in step 3 of clause 8.4.1.1) carries additional content preview indicator, which indicates that the session request is for CoD preview, not for regular CoD viewing. 2) Upon incoming session initiation request (in step 4 and 5 of clause 8.4.1.1), the SCF identifies the session initiation is for content preview and performs service authorization. If the UE is allowed to preview the content, the SCF forwards the session initiation request to the selected MF, including the preview indicator. 3) Signalling procedures for establishment of a content control channel and optionally content delivery channels for the content preview take place between the UE and the MF as described in clause 8.4.1.2. MF enforces the preview policy and delivers the preview content to UE according to the preview policy. NOTE: The preview policy provision on the MF is out of scope. It may be subject to some type of criteria, e.g. content metadata. Examples of preview policy include the preview bitrate, time period permitted for preview, etc. ETSI ETSI TS 182 027 V3.5.1 (2011-03) 98 8.7.3 Preview procedures for other IPTV service The preview of other IPTV services is similar to preview of BC and CoD. The content to be previewed is identified by the IPTV content identifier, see clause I.1.
|
a51f761c27385e5a8c90041b2c701012
|
182 027
|
8.8 Parental control procedures
|
On receipt of a CoD session initiation request as defined in 8.4.1 or BC session initiation request as defined in clause 8.3.1, the SCF shall chek the following parameters in IPTV user profile in the following order: • If the requested content is not compatible with parental control level or PC-ClassificationRestrictionn then the SCF shall reject the request. • If PC-CostLimit, PC-TotalCostLimit, PC-TotalPlayTimeLimit are exceeded, then the SCF shall reject the request. • If PC-TimeRestrcition is present If the time and if the request occurs within PC-TimePeriodRestriction range, then the SCF shall contact the user indicated in PC-Contact if " dynamic PC-activation" is activated. If not, the SCF shall proceed the request as indicated in clauses 8.4.1 for CoD and 8.3.1 for BC. • If no PC-TimeRestriction is present and if dynamic PC-activation is activated then the SCF shall contact the user indicated in PC-Contact. If not, the SCF shall proceed the request as indicated in clauses 8.4.1 for CoD and 8.3.1 for BC. In case the SCF has contacted the user indicated in PC-contact, if the answer is positive, the SCF shall proceed the request as indicated in clauses 8.4.1 for CoD and 8.3.1 for BC. If the answer is negative or if there is no answer after a associated timer has elapsed, the SCF shall reject the request. NOTE: Parental control procedure is valid for any services based on CoD or BC procedures (e.g. UGC, N-PVR, etc.) Figure 34C describes the SCF behaviour regarding parental control. ETSI ETSI TS 182 027 V3.5.1 (2011-03) 99 Session initiation request received by SCF Dynamic PC- activation activated ? Any of PC-CostLimit, PC-Total-CostLimit, PC- totalPlayLimit exceeded ? No Yes Reject the request PC-Time- PeriodRestriction present ? Carry on with the request Compatible with PC- ClassificationRestriction ad Parental Control Level ? In PC- TImePeriodRestriction range ? No Yes Dynamic PC- activation activated ? No Yes Yes No Contact PC-Contact No Yes Yes No Figure 34C: Parental control checkings in the SCF During an on-going CoD or BC session, if the PCtotalPlayLimit becomes exceeded, the SCF shall terminate the CoD or BC session as defined in clauses 8.3.3 for BC and 8.4.3 for CoD. If the session enters the PCTimePeriodRestriction range, the SCF shall apply the procedure from the box 'PC-TimePOeriodRestriction present defined in figure 34C. ETSI ETSI TS 182 027 V3.5.1 (2011-03) 100
|
a51f761c27385e5a8c90041b2c701012
|
182 027
|
8.9 UGC procedures
| |
a51f761c27385e5a8c90041b2c701012
|
182 027
|
8.9.1 Overview
|
There are two types of UGC procedures: • creation of the User Generated Content: this type of procedure allows a user to declare and upload/upstream his/her own content to the network; • watching of User Generated Content: this type of procedure allows a user to select and watch User Generated Content. NOTE: The clause 8.9.3 UGC watching procedure may start before the clause 8.9.2 UGC creation procedure has been completed (see e.g. TS 181 016 [15], clause A.9.1.2, "Use case: Home movie sharing, streaming").
|
a51f761c27385e5a8c90041b2c701012
|
182 027
|
8.9.2 UGC creation procedure
|
The UGC creation procedure comprises four major steps: Step 1: Declaration of User Generated Content • The UE sends a User Generated Content creation request to the SCF and receives a content ID for the UGC from the SCF. The content ID is independent of the address where the UGC can be retrieved by other UEs. Step 2: Publication of User Generated Content information by the UE • The UE sends a request to the SCF that contains a description of the User Generated Content (name, type, restriction, textual description, special group users, etc.). This request may be combined with the User Generated Content Declaration request in step 1. The UGC item described in clause 7.4.1 is used for UGC description information carried in the publication request. Step 3: Creation of User Generated Content • The UE initiates a session with the SCF and MF in order to connect with the MF to create the User Generated Content (i.e. upload/upstream (unicast) the content to the MF). The MF provides the SCF with the location at which the UGC becomes available. Step 4: Publication of User Generated Content information by the SCF • The SCF establishes the relationship between UGC content ID, UGC description, and optionally the MF, and publishes this UGC description information. The UGC description publication by the SCF in step 4 may take place before, during or after the UGC content creation delivery session initiation in step 3. NOTE 1: In general, the UGC procedures should allow for all forms of SCF-MF interaction as described in clause 5.2. Step 1 is always the first step. Step 2 may happen at any time during the UGC creation and can be repeated during the lifetime of the content. NOTE 2: UE publishes the UGC description to SCF, optionally it may be audited by the SCF or the management entities. As a result of this audition the UGC description may be rejected or a revision of the description may be required. Also the UGC content may also be audited. The mechanisms for UGC description and content auditing are out scope of the present document. Figure 34D depicts the typical steps that occur when the UE creates UGC. ETSI ETSI TS 182 027 V3.5.1 (2011-03) 101 Figure 34D: UGC creation 1A) The UE sends a UGC Declaration Request through the Core IMS to the SCF. 1B) The SCF records the UGC information and sends a UGC Declaration Response including a UGC content ID through to core IMS to the UE. 2A) The UE sends a UGC Description Request through the Core IMS to the SCF. The request contains a description of the User Generated Content (name, type, restriction, textual description, special group users, etc.). 2B) The SCF records the UGC description, establishes the relationship between UGC ID and UGC description and sends a UGC Description Response through to core IMS to the UE. NOTE 1: Steps 2A/B can be done either after steps 1A/1B or combined with steps 1A/1B. 3) The UE initiates a UGC creation session, including a content upload/upstream channel to the MF. The content upstream procedure is similar to the one defined in clause 8.4.1.1.1 for CoD initiation procedure (steps 3-6 and 9-11). The content control channel may not be required. The content upload procedure is specified in clause 8.18.1. The session initiation response from the MF to the SCF includes the location on which the UGC becomes available. 4) The SCF establishes the relationship between UGC ID, UGC description and optionally UGC location (address), and publishes this UGC information. The UE can modify or terminate the established UGC creation session later on. NOTE 2: Updating the SSF for UGC information from the SCF is required, but the method for achieving this is out scope of the present document. UE CORE IMS SCF MF 4. Publication of UGC information 1A. UGC Declaration Request 1B. UGC Declaration Response 1B. UGC Declaration Response 1A. UGC Declaration Request 3. UGC creation session initiation SSF 2A. UGC Description Request 2B. UGC Description Response 2B. UGC Description Response 2A. UGC Description Request UGC creation session modification/termination ETSI ETSI TS 182 027 V3.5.1 (2011-03) 102 NOTE 3: In a particular protocol realization, the messages supporting steps 1 and 2 may be embedded in the messages supporting UGC session initiation. For a UGC creation session initiated by Remote UE, the Remote UE starts-up the UGC content creation service according to the procedures of service initiation by remote UE specified in clause 8.25 which indicates the UGC service for the Target UE to upload/upstream UGC content. Then the Local UE initiates the UGC creation procedure using the same steps in figure 34D. NOTE 4: UGC creation by direct multicast from a UE to a multicast group is not supported in this release.
|
a51f761c27385e5a8c90041b2c701012
|
182 027
|
8.9.3 UGC watching procedure
|
The UGC watching procedure comprises two major steps: Step 1: Selection of UGC • The selection of the UGC may be done through the SSF. Alternatively, UGC selection can be triggered by a content recommendation or a notification. The UE may also pre-select UGC that has already been declared and published (clause 8.9.2, steps 1, 2 and 4), but not yet created (clause 8.9.2, step 3). NOTE: Other ways of selecting UGC (notification from another UE) are out of scope of this release. Step 2: Watching of UGC • Session initiation can be performed by the UE or the SCF in order to watch the selected UGC. The UGC watching session is equivalent to the CoD session. If the UE has previously pre-selected UGC that had already been declared and published but not yet created (see above), then this UGC will be delivered in an SCF-initiated CoD session (clause 8.4.1, figure 21A) connecting the UE to the SCF and MF when the UGC is created. Figure 34E depicts the typical steps of the UGC watching procedure. Figure 34E: UGC watching procedure UE CORE IMS SCF 3 UGC watching session initiation MF SSF UGC watching session modification/termination 1 UGC selection 2 Notification of UGC availability ETSI ETSI TS 182 027 V3.5.1 (2011-03) 103 1) The UE can use two methods for UGC selection: - The UE can select UGC through service selection procedure with SSF (clause 8.2, step 4) For selection using the SSF the SSF may restrict the list of UGC depending on user identity and UE capabilities. - The user can pre-select UGC that has already been declared and published (clause 8.9.2, steps 1, 2 and 4), but not yet created (clause 8.9.2, step 3). The SCF then stores this pre-selection of UGC. 2) If the SCF wants to inform the user of UGC availability the SCF can use the notification procedure as defined in clause 8.11.1 or recommendation procedure from the SCF as defined in clause 8.13. 3) The UE or the SCF initiates a UGC watching session. The UGC watching session is equivalent to the CoD session. Therefore procedures defined in clause 8.4.1 apply. When the SCF detects that pre-selected UGC becomes available (i.e. its creation, as described in clause 8.9.2, step 3, is starting or has been completed), then this UGC will be delivered in an SCF-initiated CoD session (clause 8.4.1.1.2). When the UE wishes to modify or to terminate the UGC session, it follows session modification/termination procedures as specified in clauses 8.4.2.1 and 8.4.3.1. NOTE: UGC watching through multicast (e.g. in a BC session) is not described in the present document. Generic BC procedures can be reused.
|
a51f761c27385e5a8c90041b2c701012
|
182 027
|
8.9.4 UGC removal procedure
|
The user can decide to remove one of his/her UGC by using UGC description procedure as defined in clause 8.9.2. The operator can decide to remove the created UGC at any time due to local or legal policies. It may inform the user that has created the UGC by using the Notification procedure as defined in clause 8.11.1.1 or other methods. The network shall ensure that the UGC will not be present in the related MF and that UGC description is also removed. 8.10 Personalized channel (PCh) service procedures PCh service allows the users to tune in a single (virtual) channel and watch one or multiple pre-configured content items identified in the service profile (PCh information). Before the PCh service is available to the user, the configuration procedure shall take place, through which particular IPTV content items identified by their IPTV content identifier, see clause I.1, are selected and scheduled in the PCh information. The UE retrieves the specific PCh information from the SSF via service selection procedure as described in clause 8.2. Before the user can view the content items in the PCh information, a session initiation procedure for the PCh service shall take place.
|
a51f761c27385e5a8c90041b2c701012
|
182 027
|
8.10.1 Generic Procedure for PCh service
|
Figure 34F shows the major steps enabling the PCh service. ETSI ETSI TS 182 027 V3.5.1 (2011-03) 104 Figure 34F: Major steps for PCh service 1) The PCh declaration procedure takes place between UE and SCF. The UE sends a PCh Declaration Request to the SCF via Core IMS, and the initial PCh information, containing the PCh id, is created and returned based on user profile and content metadata. 2) The PCh Configuration procedures takes place between SCF and UE (e.g. add an item to the list, remove an item from the list, arrange the schedule), as described in clause 8.12 upon user's decision. The SCF saves the PCh configuration, e.g. the time schedule for each PCh content item. SCF may accept or reject the overlap between content items. In this release overlap between broadcast items shall be accepted during the configuration phase. Overlap between a broadcast content and a CoD content shall not be accepted during the configuration phase. Overlap shall be handled in accordance with one of the following options: a) The network automatically records the new content and maintains the ongoing content. b) The network switches to the new content, bookmarks the old content and/or starts recording the old content. c) The network advises the user that makes the decision if the network supports either of the above options. 3) The selection procedure of PCh information takes place either between UE and SSF as described in clause 8.2 or notification procedures between UE and SCF as described in clause 8.11.1 or recommendation procedures as described in clause 8.13. During this step, the UE retrieves the PCh id and other necessary network parameters (e.g. the bandwidth requirement) to facilitate the initiation of PCh session (i.e. step 3). Optionally the time schedule can be also provided in this step. 4) The PCh service provision procedures take place after the selection of the PCh information. This step shall conform to one of the following options: a) The PCh service is provided through a single unicast session for all content items inside the specific PCh, including BC. The procedure for this case is described in clause 8.10.2. b) The PCh session alters between unicast and multicast under control of the SCF. The procedure for this case is described in clause 8.10.3. UE SSF Core IMS SCF MF 3. PCh Selection 4. PCh Service Provision (8.10.2/8.10.3) 1a. PCh Declaration Request (User ID) 1b. PCh Declaration Response (PCh ID) 2. PCh Configuration in 8.12 ETSI ETSI TS 182 027 V3.5.1 (2011-03) 105
|
a51f761c27385e5a8c90041b2c701012
|
182 027
|
8.10.2 MF Option for PCh Service Provision
|
Figure 34G depicts the PCh service procedure that utilizes a single unicast session for all PCh content items, including BC. Figure 34G: MF option for PCh service provision 1) The PCh session initiated by the UE, as similar with the one defined in 8.4.1 for CoD initiation procedure with the following differences: - The session initiation request from the UE contains the PCh id as the CoD content id. - The SCF retrieves the PCh information (e.g. list of content to be played with the time schedule of each item) and sends it to the selected MF in addition to the PCh ID. The SCF may send either part of the PCh list (e.g. the first item) or the entire PCh information to the MF, for the purpose of content channel negotiation. 2) When there is overlap between two PCh content items, the SCF handles the conflict items according to the selected policy by the SP as per clause 8.10.1. In this step, the SCF triggers the N-PVR procedures for recording of either the upcoming item or the on-going item according to the SP policy. NOTE 1: The rest of the call flow assumes there is no overlap. 3) Based on the current time, the SCF sends PCh control message to the MF via Core IMS, indicating the delivery of the upcoming PCh content item. The PCh control message contains the upcoming PCh item id(s) within the PCh list, as well as the time schedule of each item. NOTE 2: The PCh control message is used when the SCF does not send all of the PCh information to the MF in session initiation (i.e. in step 1). 4) The PCh session may be modified if the reserved resource is not sufficient for the upcoming PCh item, e.g. due to higher bandwidth requirement. In this case the MF-initiated session modification procedure described in clause 8.4.2 applies. 5) The indicated PCh content is delivered to the UE through the unicast content delivery channel established during step 3. The MF needs to fetch the content in from MDF or from other content sources. The MF may also perform the content adaptation or conversion before the unicast content is sent out to UE, e.g. multicast-unicast conversion, transcoding, etc. UE SSF Core IMS SCF MF 1. PCh Session Initiation (8.4.1) 5. Unicast Content Delivery to UE 3.PCh Control Message 6. PCh Session Termination (8.4.3) Repeatable 2. Overlap Handling 4. MF-initiated session modification for PCh ETSI ETSI TS 182 027 V3.5.1 (2011-03) 106 NOTE 3: The steps 2 to 5 can be repeated during the life time of PCh session, for the purpose of switching among multiple content items. NOTE 4: How the MF fetches the PCh content item from the content source is out scope of the present document. In specific implementations, the MF contacts the source via file transfer or joins a BC multicast group to receive the indicated content. 6) Initiated by the UE or the network, the PCh session is terminated at some time, as the ones defined in clause 8.4.3.
|
a51f761c27385e5a8c90041b2c701012
|
182 027
|
8.10.3 UE Option for PCh Service Provision
|
Figure 34H depicts the signalling flow for UE option of PCh service provision, which enables the SCF to control UE to alter the PCh session between unicast and multicast depending on the type of viewed item. Figure 34H: UE option for PCh service provision 1) The PCh session initiated by the UE according to the type of first PCh content item in the PCh information, i.e. BC session initiation described in clause 8.3.1, or CoD session initiation described in clause 8.4.1. The session initiation request contains the specific PCh id and the first CoD content id/BC service id. After the PCh session initiation, the UE receives the indicated content through the delivery channel. Note that the UE may also have the content information stored locally. 2) When there is overlap between two PCh content items, the SCF handles the conflict items according to the selected policy by the SP as per clause 8.10.1. In this step, the SCF triggers the N-PVR (or C-PVR) procedures towards the MF (or UE) for recording of either the upcoming item or the on-going item according to the SP policy. Note that the UE client in this case will be coordinated to follow the SP policy as well. NOTE 1: The rest of the call flow assumes no overlap. 3) The SCF sends UE the PCh control message carrying the control command (e.g. item switch, PVR, etc.) and upcoming content id(s) that are to be handled. Note that the UE may also have the content information stored locally. ECF/EFF UE Core IMS SCF MF 1. PCh Session Initiation (8.3.1 for BC, or 8.4.1 for CoD) 3. PCh Control Message (upcoming content ids) 4a. BC channel switch 2. Overlap Handling 5. PCh Session Termination (8.3.3/8.4.3) Repeatable 4b. CoD session modification(8.4) 4c. PVR capture request(8.5) ETSI ETSI TS 182 027 V3.5.1 (2011-03) 107 4) The procedures are initiated according to the PCh control message, for example, switch to another multicast group for BC item (4a), initiate a session modification for upcoming CoD item (4b), perform PVR service as described in clause 8.5 (4c), etc. NOTE 2: The steps 2 to 4 can be repeated during the life time of PCh session, for the purpose of switch among multiple PCh items. 5) Initiated by the UE or the network, the PCh session is terminated at some time, as the ones defined in clauses 8.3.3 or 8.4.3 with respect to the type of the latest PCh content item. NOTE 3: The pure UE centric PCh, where the PCh control decision is made locally on the UE without interaction with the network, is out scope of the present document. NOTE 4: The PCh control message can be session modification request (e.g. SIP re-INVITE, etc.) or non-stateful message exchange (e.g. SIP INFO,etc.), and should be determined in the protocol implementation phase, which is out scope of the present document. 8.11 Interaction procedures with other IPTV Services 8.11.1 Notification procedures Notification procedure can be used for several purposes: notification that a CoD is available based on user's prior subscription to that information, caller-Id on TV screen, reminder from a particular TV program based on user's setting, etc.
|
a51f761c27385e5a8c90041b2c701012
|
182 027
|
8.11.1.1 Notification procedures using signalling path
|
Figure 35 depicts the typical steps that occur when the SCF wants to notification the user on a particular event using signalling path. Figure 35: notification procedure using signalling path Priori to the procedure, it is considered that the SCF has detected an event that would cause the notification to be sent to the UE. For example, it can be informed of an incoming call to the user. It could also be based on user's subscription dealing with a notification to be sent when a particular BC program/CoD content is available. UE CORE IMS SCF 1Notification Request 2. Notification Request 3. Notification Response 4. Notification Response Event trigerring the notification ETSI ETSI TS 182 027 V3.5.1 (2011-03) 108 1) Based on the service logic, the SCF sends an Notification Request to the UE via the core IMS. The message shall contains at least: i) the reason of the notification: Examples include incoming phone-calls, CoD content or TV program notification based on reminder/subscription set by the user; ii) related parameters: Examples include calling-number/URI, CoD content identifier or BC service ID, service provider id of the associated SSF from where the update service information may be retrieved, etc. 2) The core IMS forwards the Notification Request to the UE. NOTE: The Notification may be displayed to the user. 3) The UE answers to the SCF via the core IMS. 4) The Notification Response is forwarded to the SCF. After this step, the UE can take appropriate action (e.g. initiate a CoD session) based on user's decision.
|
a51f761c27385e5a8c90041b2c701012
|
182 027
|
8.11.1.2 Notification procedures using multicast media path
|
Figure 35A depicts the steps that occur when the SCF and MF use the multicast media path to send a notification to users who are watching a specific BC channel. Figure 35A: notification procedure using multicast media path When receiving a notification trigger event from external entity (e.g. SCF in charge of BC service) or detecting an internal notification trigger (e.g. SCF detects that it should send a notification to users who have subscribed to the content recommendation service for an upcoming BC program) or receiving a message need to be delivered using media path, the SCF would send notifications to users who are watching a specific BC channel. If the users want to receive the notification, they will have joined the specific notification multicast stream in addition to the BC service multicast streams. 1) SCF sends the notification to the selected MF (e.g. SCF retrieve MF from local configured information) via Core IMS. The notification request shall contain at least: i) The reason of the notification: e.g. upcoming programs, floating ad or weather forecast. ii) Related parameters: e.g. BC service ID, service provider id, etc. UE SCF MF 1. Notification Request Event trigerring the notification UE joins the multicast notification stream ECF/EFF 3. Media stream notification 2. deliver the notification to the notification multicast group ETSI ETSI TS 182 027 V3.5.1 (2011-03) 109 NOTE 1: As stated in TS 182 006 [2], an Application Server may originate requests to a destination without involving the S-CSCF. This capability should be used if SCF sends the notification to MF directly without Core IMS involved 2) MF delivers the notification to the specific notification multicast group. NOTE 2: The multicast address for the notification channel may be pre-configured on the MF or it may get it from the notification request in step 1. Other options may be possible and out of scope of specification. 3) The UE receives the notification from ECF/EFF and displays the notification to the user. NOTE 3: Before step 3 could take place, UE should first discover the specific multicast group information for the notification (e.g. through the Service Discovery and Selection procedure) and then join the notification multicast group. The UE can take appropriate action based on the user's decision.
|
a51f761c27385e5a8c90041b2c701012
|
182 027
|
8.12 Procedures for IPTV User Profile Configuration
|
This clause describes the generic procedures for IPTV user profile configuration. These procedures may be used in conjunction with other procedures for delivery of other IPTV services - e.g. Content recommendation service, N-PVR. Figure 35B: User Profile Configuration procedures 1) The user (on UE) makes a request to the SCF to configure IPTV User profile settings. 2) The SCF shall perform relevant authentication and authorization of the User Profile Configuration request by the user before permitting the request. The SCF records the profile settings as part of the IPTV user profile information as described in clause 7.3.1. NOTE: In case the UE needs to directly contact a network functional element, (e.g. Service Control Function), it should perform GBA authentication, for key management purposes, during the session start-up phase. Please refer to TS 187 003 [5]. 3) The UE is informed of the result of the IPTV user profile service configuration request. 3. User Profile Configuration Response 1. User Profile Configuration Request UE SCF 2. Record user profile/preferences ETSI ETSI TS 182 027 V3.5.1 (2011-03) 110
|
a51f761c27385e5a8c90041b2c701012
|
182 027
|
8.13 Content Recommendation service procedures
|
The Content Recommendation Service (CRS) is used for providing recommendations to IPTV users or user groups. The content recommendation service may make recommendations to user/groups based on different criteria which include user profile e.g. preferences settings, current viewing habits of user, etc. The CRS service procedures include 3 major steps: 1) CRS event detection. The events include request from the UE, new content arrival notification, presence update, trick play reports from MF, channel change report from UE etc. This step is triggered due to the user subscription or service provider's policy, and it may also be based on user request (e.g. for sepecific program or during specific time period). 2) CRS information generation for specific user. The CRS info includes one or more IPTV content identifiers (clause I.1), identifying the recommended content. The user profile (e.g. user preference, watching habits, etc.) is used for filtering/sorting of CRS info. 3) CRS information delivery to the UE. SCF sends the generated CRS information to specific UE(s). In the case when user profile settings are used for making content recommendations, the user preferences in IPTV profile are configured using procedures described in clause 8.12. The CRS information is delivered to the UE by the SCF using notification procedures as described in clause 8.11. The UE may subsequently fetch the details about the recommended content from the SSF via procedures described in clause 8.2. Figure 35C depicts the typical steps for CRS. Figure 35C: signalling flows for CRS provided by SCF 1) UE may optionally send a request to the SCF for CRS information notifications. NOTE 1: This step is optional in case the user only wants to get notified during specific content play back or specific time period. 2) The SCF detects the CRS events based on user profile, user request or service provider's policy. 3) The SCF generates the requested CRS information for specific user. The CRS information includes one or more identifier(s) of the recommended content. NOTE 2: How to generate the program related CRS information on the SCF is out scope of the present document. UE Core IMS SCF 3 CRS information generation 4 Delivery of CRS information (clause 8.11.1.1) 1 Request for CRS information notifications 2 CRS event detection ETSI ETSI TS 182 027 V3.5.1 (2011-03) 111 4) SCF sends UE the generated CRS information using notification procedures described in clause 8.11.1.1.
|
a51f761c27385e5a8c90041b2c701012
|
182 027
|
8.14 Advertising (Ad) service procedures
|
There are several types of procedures in Advertising (Ad) service, including: 1) Targeted ad insertion: some selected ad content is provided to the UE during the IPTV content playback, based on the user profile (user preference, shopping habits, location information, etc.) and the IPTV service status (e.g. current BC program, commercial breaks or pause during content playback). Content replacement or multi-window rendering takes place within the insertion time period. 2) Pull mode Advertising: Advertising is content in its own right and can be selected by the UE, and the users can actively retrieve or interact with the ad content. Audio-visual content of this ad type can be provided to the users via similar procedures with CoD or BC. Other procedures for non audio-visual ad content provision, such as interactive ad and banners, may also be described here. 3) Broadcast based Ad-insertion: Ad content (local or regionalized) is inserted into the IPTV content that is broadcasted to the UE without factoring in any information related to user profile. Such ad content is not targeted any any specific user or user groups but it may be targeted to regions or zones depending on network topology. NOTE 1: Other procedure types of Ad service can be included. Where Targeted Ad Insertion (TAI) is required, Ad procedures shall follow the generic procedures in clauses 8.14.1 and 8.14.2, implemented according to one or more of the following options: • Internal option in which advertising tasks are done by entities within the TISPAN IPTV system For the internal option, refer to clause E.1. • External option in which an external Advertising sub-system is interconnected with TISPAN entities For the external option, refer to clauses E.2 (SCTE) and/or E.3 (OMA MobAd). NOTE 2: In the second option, the SCF acts as a broker to bundle information from IPTV user profile and service profile along with information on placement opportunities and sends it over to the external advertising sub-system which responds back to SCF with the ad-placement decisions decisions. • Implementation examples of these options are documented in annexes E and F. The upcoming clause discusses a generic architecture that can be instantiated into any of the options in annexes E and F.
|
a51f761c27385e5a8c90041b2c701012
|
182 027
|
8.14.1 Generic Procedures for targeted ad insertion (TAI)
|
Ad insertion implies that an IPTV sesssion exists prior to the insertion time. The targeted ad is selected by the SCF with regard to user profile (e.g. shopping habits) or other criteria, e.g current BC program. IPTV content and ad content in the context of ad insertion can be described as: • IPTV content: the content to be partially (or entirely) replaced during the IPTV session. There is usually some cue/hint related to the IPTV content used to trigger ad insertion, e.g. insertion time in content metadata or insertion points in the actual content itself where a targeted ad can be inserted to replace an existing default ad. • Ad content: the content which is inserted to the IPTV content during the ad insertion time, or to replace a default ad. The ad can be rendered sequentially or in parallel with the IPTV content. The ad insertion can be performed at either UE side or MF side: • When UE performs ad insertion, it is informed of ad insertion indication, it can receive both IPTV content and ad content at the same time, and renders them in a sequential or simultaneous way. The UE could also have the ad content stored locally through off-line means. • When MF performs ad insertion, it is informed of ad insertion indication, it can retrieve or receive the ad content, and delivers the combinded IPTV stream and ad to the UE. ETSI ETSI TS 182 027 V3.5.1 (2011-03) 112 The major steps of TAI is as follows: 1) IPTV service status detection/awareness: There are several options in this case: - the SCF can be fully responsible for the awareness/detection of the user's IPTV service status, in which case, the SCF shall reuse the existing procedures for that purpose (see clause 5.5); - optionally the MF can be fully responsible for the awareness/detection given that the MF is in the signalling and the media control path and can be informed of media embedded events related to ad insertion; - additionally the UE can be fully responsible for the awareness/detection using its local state for that purpose; - Finally, a service provider can use a hybrid approach where some events are detected by the SCF while others are detected by the MF, and/or the UE. 2) Identification of Targeted Ad Insertion Points: Places to insert Ad could be known in advance (predetermined) or detected during the play (unexpected). More details on Ad placement in annex G. 3) Ad Content Selection: One or more ad content(s) is selected with regard to user profile (e.g. shopping habits, user preference, etc.). The user's IPTV service status and/or the metadata of current content can also be used for locating of ad content targeted to specific user or user group. 4) Ad content delivery: The selected ad content is delivered to the UE, before or after which essential ad insertion is performed (i.e. either at MF side or UE side).
|
a51f761c27385e5a8c90041b2c701012
|
182 027
|
8.14.2 Generic Signalling for Targeted Ad insertion
|
NOTE: The term Ad Server is used for the generic purpose of Ad selection and/or control, and it can be implemented in SCF or externally, based on the examples in annex E.
|
a51f761c27385e5a8c90041b2c701012
|
182 027
|
8.14.2.1 Signalling flows for TAI at UE side
|
When the ad insertion takes place at UE side, the UE is informed about ad insertion information from SCF. The UE may initiate individual session request for Ad content, which implies that multiple sessions exist on the UE during the ad insertion time. Other means for retrieving the content are also envisioned. Figure 36 depicts the typical steps when UE is informed of targeted ad insertion information. ETSI ETSI TS 182 027 V3.5.1 (2011-03) 113 Figure 36: Signalling flows for UE performing TAI 1) An IPTV session is established between UE and SCF in charge of general IPTV services as described in clause 8, e.g. BC session in clause 8.3.1.1, CoD session in clause 8.4.1.1, etc. and the related IPTV content is delivered to the UE. 2) The service state of on-going IPTV session is detected on the SCF, MF or UE (e.g. the current IPTV content identifier (clause I.1), the commercial break of the program, the trick-play events, etc.). Detection of the IPTV service state at the SCF is done based on IPTV Service State Data (see clause 5.5) or using IPTV Presence information (see clause 9.1). Note that for simplicity, the figure does not show the option when the service state detection happens at the UE. 3) The Ad Server is informed of the ongoing IPTV service state of the specific user detected by SCF/MF/UE and decides to trigger ad insertion. This step isimplemented depending on the selected option in annex E. Note that for simplicity, the figure above does not show the option when the UE contacts the Ad Server with state information. 4) The Ad Server selects the appropriate target ads which can be inserted in the currently streamed content. 5) The notification procedures specified in clause 8.11.1 are applied to deliver the ad insertion information to the UE. This step is implemented depending on the selected option in Annex E. The ad insertion information can include the selected ad content identifier, insertion time (begin time and/or length), and other information needed for ad insertion. Other means for conveying the same information are also possible. 6) In order to retrieve the ads, the UE may perform session modification procedure in case the MF for the target ads is the same MF from which the streaming of the actual content occurs. Alternatively, the UE may also initiate a separate session to MF that includes the target ad content. During this step the procedures described in clauses 8.3.1 and 8.3.2 for BC session or 8.4.1 and 8.4.2 for CoD session applies. NOTE: Other means such as off-line mechanisms can be also used to deliver the target ads to the UE, which are out of scope of the present document. 7) The UE performs the ad insertion, i.e. renders the ad content embedded within the actual content or in parallel with the ongoing IPTV content (e.g. in PiP). 8) When the ad insertion time is up, the session for ad content is released as procedures described in clauses 8.3.3 or 8.4.3, and UE resumes the rendering of the IPTV content. UE Core IMS SCF MF Ad Server 1 Session initiation (clause 8.3.1.1, 8.4.1.1, …) 4 Ad content selection 2 IPTV service state detection 5. Send ad insertion information to UE 6. Ad content delivery 3. State informed to Ad Server 7.Ad insertion ETSI ETSI TS 182 027 V3.5.1 (2011-03) 114
|
a51f761c27385e5a8c90041b2c701012
|
182 027
|
8.14.2.2 Signalling flows for TAI at MF side
|
When the ad insertion takes place at MF, the MF is informed of the ad insertion information from the SCF. The MF performs the ad insertion, i.e. delivery ad content to the UE during the ad insertion time of IPTV content play back. Figure 37 depicts the typical steps when MF is informed of the ad insertion indication. Figure 37: Signalling flows for MF performing TAI 1) An IPTV session is established between UE and SCF(BC/CoD/…) as described in clause 8, e.g. BC session in clause 8.3.1.1 CoD session in clause 8.4.1.1, etc. and some IPTV content is delivered to the UE. 2) The service state of on-going IPTV session is detected on the SCF or MF (e.g. the current BC program ID, the commercial break of the program, the current CoD content id, the trick-play events, etc.). Detection of the IPTV service state at the SCF is done based on IPTV Service State Data (see clause 5.5) or using IPTV Presence information (see clause 9.1). 3) The Ad Server is informed of the ongoing IPTV service state of the specific user detected by SCF/MF and decides to trigger ad insertion. This step is implemented depending on the selected option in annex E. 4) The Ad Server selects the appropriate target ads which can be inserted in the currently streamed content. 5) The ad insertion information is sent to the MF. This step is implemented depending on the selected option in annex E. The ad insertion information can include the selected ad content identifier, insertion time (begin time and/or length), and other information needed for ad insertion. The means by which the MF acquires the ad content is outside scope. 6) The MF performs the ad insertion, i.e. insert the ad content to the on-going IPTV content or replace the default ad content. The MF may perform transcoding or initiate session modification if the network parameters (e.g. codec or bandwidth) of ad content are not supported by the UE. 7) The ad content is provided to the UE during the ad insertion time, or the streamed content includes the ads. NOTE: Group-based TAI, which targets the specific group among the users watching the same BC service, should also be considered but is out scope of the present document. UE Core IMS SCF MF Ad Server 1 Session initiation (clause 8.3.1.1, 8.4.1.1, …) 4 Ad content selection 6 Ad insertion 2 IPTV service state detection 5 Send ad insertion information to MF 7. Ad content delivery 3. State informed to Ad Server ETSI ETSI TS 182 027 V3.5.1 (2011-03) 115
|
a51f761c27385e5a8c90041b2c701012
|
182 027
|
8.15 Procedures for inter-destination media synchronization
| |
a51f761c27385e5a8c90041b2c701012
|
182 027
|
8.15.1 MSAS - SC
| |
a51f761c27385e5a8c90041b2c701012
|
182 027
|
8.15.1.1 SCF-based media synchronization
| |
a51f761c27385e5a8c90041b2c701012
|
182 027
|
8.15.1.1.1 Mapping 1: SC in UE
|
Figure 38 provides an overview of the information flows for inter-destination content synchronization according to Mapping 1 from clause 5.4.2. Figure 38: Procedure for inter-destination content synchronization (1) IPTV session initiation, e.g. BC session initiation according to clause 8.3.1.1, or CoD session initiation according to clause 8.4.1.1. The following steps (2) to (8) are all tunnelled over the broadcast session established in steps (1). (2) The UE (SC) sends a synchronization initiation request to the SCF (MSAS), indicating that it wants to participate in the inter-destination synchronization process. The request includes the IPTV content identifier (see clause I.1), identifying the to-be-synchronized content. The synchronization group identifier (SyncGroupId), in combination with the IPTV content identifier, identifies the group of UEs (SCs) that is synchronized as a group for the identified IPTV content. NOTE 1: The ways that a UE can obtain a SyncGroupId are similar to obtaining a phone conference id. For example, one user can request a new SyncGroupId through an off-line process, and share it with other users through an offline process. If the group of users does already have a group identifier, e.g. a phone conference id, they may reuse this identifier. Clause 8.21.3 describes the reuse of the SSC room identifier for this purpose. (2) Sync Initiation Request (IPTV content identifier, SyncGroupId) Repeat UE (SC) (3) Sync InitiationResponse, MSAS address (1) IPTV Session Initiation (4) Sync Status Information (6) Sync Settings Instruction (5) Calculate sync settings (7) Sync Termination Request (8) Sync Termination Response MSAS (media-oriented part) MSAS SCF (session-oriented part of MSAS) ETSI ETSI TS 182 027 V3.5.1 (2011-03) 116 (3) The SCF confirms the participation of the UE in the inter-destination synchronization process. The response includes the address of the media-oriented part of the MSAS. (4) The UE (SC) sends its synchronization status information to the media-oriented part of the MSAS, using the address obtained in step (3). NOTE 1a: Direct intra-MSAS communication may be possible, but it is out of scope of the present document. (5) The media-oriented part of the MSAS aggregates synchronization status information from multiple UEs (SCs) and calculates the appropriate synchronization settings for each UE (SC). NOTE 2: Examples of algorithms to calculate the synchronization settings instructions from collected synchronization status information may be found in [i.11]. (6) The media-oriented part of the MSAS sends a synchronization settings instruction to the UE (SC). Steps (4) - (6) may be repeated at regular time intervals. (7) The UE sends a synchronization termination request, indicating that it is no longer active in the inter-destination synchronization process. This could be e.g. because of a channel change by the UE. (8) The SCF confirms the termination of the UE's participation in the inter-destination synchronization process NOTE 3: The UE can initiate and terminate multiple synchronization sessions within a broadcast session, both consecutive and simultaneous. The above procedures are generally applicable to all IPTV services (BC, CoD, N-PVR, Ad, UGC, Shared Content, etc.) with the IPTV content identifier in step (2) identifying the to-be-synchronized content.
|
a51f761c27385e5a8c90041b2c701012
|
182 027
|
8.15.1.1.2 Mapping 2: SC in Transport
|
The procedures according to Mapping 2 from clause 5.4.2 are the same as above with the following changes: • Step (1) is not applicable. • Tunnelling over the broadcast session is not applicable. • The MSAS is an elementary function of the SCF or a stand-alone (possibly distributed) functional entity. • The SC is an elementary function of the Transport Functions. • The request in step (2) includes a media stream identifier. • The SyncGroupId may be used to identify multiple synchonisation groups, or it may be populated with the value "default". NOTE 1: How the SC obtains the SyncGroupId is not described in the present document. NOTE 2: If the MSAS serves SCs according to both Mapping 1 and Mapping 2 for a specific IPTV service, then the MSAS has to correlate the IPTV content identifier (BCServiceId, CoDId, etc., see clause I.1) in Mapping 1, with the appropriate media stream identifier in Mapping 2.
|
a51f761c27385e5a8c90041b2c701012
|
182 027
|
8.15.2 MSAS - SC'
|
Figure 38A shows a flow for the exchange of synchronization status information between a media-stream-modifying Synchronization Client (SC') and an MSAS. ETSI ETSI TS 182 027 V3.5.1 (2011-03) 117 SC’ (1) Sync Initiation Request MSAS (2) Sync Initiation Response (3) Sync Status Information Repeat (5) Sync Termination Request (6) Sync Termination Response (4) Acknowledgement Figure 38A: Media synchronization in case of media-stream-modifying SC' (1) The MSAS sends a synchronization initiation request to the media-stream-modifying SC', indicating that the SC' will participate in the inter-destination synchronization process. The request includes an identification of the to-be-synchronized media stream(s). (2) The SC' confirms its participation in the inter-destination synchronization process. (3) The SC' sends synchronization status information on the synchronicity relationship between incoming and outgoing media streams to the MSAS. (4) The MSAS returns an acknowledgement message to the SC'. Steps (3) - (4) may be repeated at regular time intervals. (5) The MSAS sends a synchronization termination request, indicating that the SC' is no longer active in the inter-destination synchronization process for the identified media stream(s). (6) The SC' confirms the termination of its participation in the inter-destination synchronization process.
|
a51f761c27385e5a8c90041b2c701012
|
182 027
|
8.16 Signalling flows for network-controlled trick play
|
Figure 39 provides the signalling flow for controlling trick play of a Broadcast TV channel, CoD, N-PVR or other IPTV session by a network element. In order to apply trick modes to a Broadcast TV channel, a BC TV with trick play session must first be established. ETSI ETSI TS 182 027 V3.5.1 (2011-03) 118 Figure 39: Signalling flow for network-controlled trick play 1) Broadcast TV, CoD or N-PVR session initiation. NOTE 1: The Broadcast TV, CoD or N-PVR sessions are initiated by the appropriate procedures in clauses 8.3.1.1, 8.4.1.1 and 8.5.2, respectively. 2) Based on an event detected by the SCF, e.g. a trigger received from an external application, the SCF sends a notification to the UE to request stream control. The notification procedure from clause 8.11.1.1. shall be applied. The notification response includes media action data. 3) If the existing session is a Broadcast TV session, a transition from BC TV to BC TV with trick play takes place according to clause 8.3.5. 4) The UE uses the content control channel to perform the trick play command, e.g. "pause", "fast forward", etc. NOTE 2: How the SCF is triggered by external applications and how media action data is sent from the SCF to external applications is not described by this procedure. 8.17 Push Procedures
|
a51f761c27385e5a8c90041b2c701012
|
182 027
|
8.17.1 Push CoD session
|
Push CoD session comprises two main steps: • Step 1: The SCF initiates the CoD content download from MF to UE. The detailed procedure can be referred to clause 8.18.2. • Step 2: The UE selects the media content in its storage device which has been downloaded from MF and views it. NOTE: The content is stored on the UE after step 1, hence in step 2 it is not required to have any further interactions between the UE and the network entities to either access or play the content. Core IMS/RACS MCF UE SCF (2) Notification procedure using signalling path (4) Control of content stream MF (1) Broadcast TV, CoD, N-PVR or other IPTV session initiation (3) Transition from Broadcast TV to Broadcast TV with trick play ETSI ETSI TS 182 027 V3.5.1 (2011-03) 119 8.18 Unicast Content Upload/Download Procedures The procedures described here are for upload/download cases distinguished from streaming cases (described in clause 8.4). NOTE: The generic content upload/download procedures described below can be referred by IPTV services such as UGC upload/download, Ad, etc. The unicast content upload/download session may be initiated by either by UE or SCF.
|
a51f761c27385e5a8c90041b2c701012
|
182 027
|
8.18.1 Signalling Flows for UE-initiated Unicast Content Upload/Download
|
Figure 39A depicts the typical steps that occur when the UE initiate a request to upload/download content by unicast. Figure 39A: UE-initiated unicast content upload/download session initiation 1) The UE initiates an upload/download request to the SCF. 2) The session initiation request is routed by the Core IMS entities up to the SCF. 3) The SCF performs service authorization. If the UE is allowed to upload/download contents, the SCF forwards the session initiation request to the selected MF which handles media content upload/download. 4) Signalling procedures for the establishment of content upload/download channel take place between the UE and the MF. The procedure of content channel negotiation is similar as the one defined in clause 8.4.1.2.1, but the media control channel is not needed here. During the negotiation, the MF offers UE the location of the uploading/downloading content for content upload/download. 5) The MF confirms the establishment of the dialogue with the UE. 6) The SCF sends this confirmation to the Core IMS. (7) Resources Commit (4) Content Upload/Download Channel Setup SCF UE MF Core IMS RACS (1) Session Initiation Request (2) Session Initiation Request (3) Session Initiation Request Content Upload/Download (8) Session Initiation Response (6) Session Initiation Response (5) Session Initiation Response ETSI ETSI TS 182 027 V3.5.1 (2011-03) 120 7) The P-CSCF within the Core IMS interacts with the RACS to commit all resources previously reserved. This includes opening pinholes for exchanging content delivery. 8) The P-CSCF forwards the dialogue confirmation to the UE. 8.18.2 Signalling Flows for SCF-initiated Unicast Content Download Figure 39B depicts the typical steps that occur when the SCF initiate a request to download content by unicast. Figure 39B: Signalling flows for SCF-initiated unicast content download 1) The SCF identifies the media content which will be downloaded to the UE, and then sends a download session initiation request to the UE (described in clause 8.4.1.1.2 from step 1 to step 4). 2) The UE check if it will accept the media content. NOTE: The checking criteria can include one or more methods such as its storage capability to compare with size of the media content, the configuration of the UE if it will accept the media content, the selection of the User if the user accepts the content. 3) If the UE accepts the request, signalling procedures for establishment of media content download channel take place between the UE and the MF based on the procedures in clause 8.4.1.2.2. 4) The UE confirms the establishment of the dialogue with the SCF and commit the resource previously reserved. (described in clause 8.4.1.1.2 from step 6 to step 11). 5) After this point, the selected MF can deliver the media content to the UE (ie. media content download to the UE). UE saves it in its storage device. (2) logical check (1) Session Initiation Request SCF UE MF Core IMS RACS (5) Content Download (3) Media content download delivery channel establish (4) Session Initiation Response and resource commit ETSI ETSI TS 182 027 V3.5.1 (2011-03) 121
|
a51f761c27385e5a8c90041b2c701012
|
182 027
|
8.19 Multicast Content Download Procedures
|
Multicast Content Download Procedures are out of scope of the present document.
|
a51f761c27385e5a8c90041b2c701012
|
182 027
|
8.20 Signalling flows for restricted trick play
|
The restricted trick play procedure can be used by network to disallow specified trick play functions on any segment of the content. Figure 39C depicts the typical signalling flow of restricted trick play. Figure 39C: procedure of restrict trick play 1) Broadcast TV with trick play, CoD session initiation or other IPTV session initiation. The Broadcast TV with trick play session use the procedures specified in clauses 8.3.1.1, and the CoD session use the procedures specified in clauses 8.4.1.1. 2) SCF acquires the restriction policy on trick play according to the information of initial request, e.g. the IPTV content identifier (clause I.1), user ID. NOTE 1: For example, SCF may fetch the pre-configured restriction policy from the content metada based on the IPTV content identifier; SCF may also generate the restriction policy based on the user subscription data and/or the IPTV content identifier. 3) SCF transmits restriction policy to MF, and informs MF to implement restriction. 4) When the MF receives UE's content control requests specified in clause 8.4.1.1.1 (Signalling flows for CoD session initiation), MF executes the restricted trick play according to the policy, such as deny return a forbidden response to UE in case trick play is disallowed. NOTE 2: The steps 2 and 3 may happened at any time during or after the step 1 initiation session. Core IMS/RACS MF UE SCF (2) Acquiring restriction policy (3) Information of restriction policy (1) Broadcast TV with trick play, CoD session initiation, or other IPTV session initiation (3)Response to Information (4) Content control requests specified in clause 8.4.1 ETSI ETSI TS 182 027 V3.5.1 (2011-03) 122
|
a51f761c27385e5a8c90041b2c701012
|
182 027
|
8.21 Shared Service Control (SSC) procedures
| |
a51f761c27385e5a8c90041b2c701012
|
182 027
|
8.21.1 Overview
|
Shared Service Control procedures allow a group of users sharing the control commands related to a service (e.g. BC, CoD) and correlating the sessions related to the same service. The virtual place established to share the services is called an SSC room. This room has only one service running at a time; this service may be BC/CoD/UGC/N-PVR/PCh services as defined in the present specification. In the following, details are worked out for shared BC and CoD services only. Figure 39D gives an example of shared service control between two users. Figure 39D SSC procedures comprise three types: • creating an SSC room: this type of procedure allows a user to create an SSC room, indicating a list of users associated to the room, policies and related rights. Optionally, the room is associated with a specific service. • selecting and entering an SSC room: this type of procedure allows a user to select an SSC room and to enter it. Optionally, a service is selected (e.g. BC, CoD), linking it to a room. The procedure ends with initiating the related session. • controlling the service: this type of procedure allows a authorised user to perform service control commands (e.g. trick-play, channel change) to the service associated to the room.
|
a51f761c27385e5a8c90041b2c701012
|
182 027
|
8.21.2 Room creation procedure for SSC
|
Figure 39E depicts the typical steps that occur when the UE creates an SSC room and publishes related information. UE A (IPTV) UE B (IPTV) MF IPTV SCF SIP SESSION A SIP SESSION B Content Content ETSI ETSI TS 182 027 V3.5.1 (2011-03) 123 Figure 39E: SSC Room Creation procedure 1A) The UE sends a SSC Room Creation Request through the Core IMS to the SCF. This request may contain information such as: - the service identifier if the room is associated with only one service item; - and optionally additional information such asa list of users allowed to join the room and associated rights through an SSC room policy as described in annex B (e.g. trick-play authorisation on the content, initiation of a service linked to the room). 1B) The SCF checks if the user has the rights to create the room and records the SSC room information. It sends an SSC Room creation Response including the SSC room identifier through to core IMS to the UE. 2) Publication of SSC room information is performed by informing the SSF, by triggering the SCF to send a notification or recommendation, or by sending a message to appropriate other UEs. 3) The SCF may optionally publish the information about this new SSC room to the users in the list indicated in SSC room creation request. NOTE: This procedure can be repeated when the service is being shared in order to update SSC room information e.g. by updating the SSC room policy. In that case the request will indicate the SSC room identifier.
|
a51f761c27385e5a8c90041b2c701012
|
182 027
|
8.21.3 Room selection procedure for SSC
|
The room selection procedure comprises the following steps: Step 1: SSC room selection • Using the SSC room identifier, the UE selects the room it wants to join and retrieves associated parameters, such as the SSC room policy. Step 2: Entering the selected SSC room • The UE enters the room and initiates a service session. If no service is associated with the room at the time of entering, the UE first selects a service. Figure 39F depicts the typical steps that occur during the room selection procedure. UE CORE IMS SCF 2. Publication of SSC information 1A. SSC RoomCreation Request 1B. SSC Room Creation Response 1B. SSC Room Creation Response 1A. SSC Room Creation Request SSF ETSI ETSI TS 182 027 V3.5.1 (2011-03) 124 Figure 39F: room selection procedure for SSC 1) The UE selects a SSC room based on the room identifier and as defined in step 2 of the room creation procedure through: - service selection procedure with SSF as defined in clause 8.2 step 4; - notification procedure from SCF as defined in clause 8.11.1, recommendation procedures as defined in clause 8.13; - messaging procedure with other UE as defined in clause 9.3. The response includes information of the SSC room, e.g. service id currently being watched in the SSC room, offset of the content at the present and the SSC room policy. For CoD, the CoDOffset from SAD is included in the room selection response so the UE can calculate the media offset. NOTE 1: Handling the case where the UE is not authorized to receive SSC room information depends on the room selection procedure involved. In case of SSF selection, the SSF can perform personalisation such that only allowed SSC rooms are sent to the UE. In case of notification or recommendation, the SCF will not send notifications to UEs that are not allowed to enter that SSC room. In case of message exchanges between UEs, if a UE sends the SSC room ID to another UE that is not allowed to enter the room, this UE will blocked when trying to enter the room. A message may be displayed to the user in this case. 2) Optionally, if no service is active in the SSC room, the UE selects a BC, CoD, UGC or N-PVR service through: - service selection procedure with SSF as defined in clause 8.2 step 4; - notification procedure from SCF as defined in clause 8.11.1; - recommendation procedures as defined in clause 8.13; - messaging procedure with other UE as defined in clause 9.3; or - IPTV Content Marker Retrieval procedure as defined in clause 8.23.2. UE CORE IMS SCF MF SSF 2. select a service for SSC 1. select a SSC room for shared service control 3. initiate a service for SSC ETSI ETSI TS 182 027 V3.5.1 (2011-03) 125 3) In case of CoD, N-PVR or UGC, each UE that enters the room initiates a CoD/N-PVR content/UGC watching session indicating the selected content as defined in clauses 8.4.1 for CoD, 8.5.1.2. for N-PVR and 8.9.3 for UGC. It additionally indicates a SSC room identifier. In addition to rights checking described in clauses 8.4.1 for CoD, 8.5.1.2. for N-PVR and 8.9.3 for UGC, the SCF shall check if the user has the rights to enter the room, which includes SSC room member authorisation and Service ID check,. If a session has already been established by another UE within the same SSC room, the SCF shall correlate this session with the new one using the SSC room identifier and selects the same MF. It shall indicate to the MF that this session has to be correlated with the other within the same SSC room ID. For an ongoing CoD service, if the CoDOffset received in the room selection response is not sufficient, each UE that starts sharing the service can request the media offset directly from the MF over the media control channel, once the service has been initiated. NOTE 2: The SCF can also select an MF for each UE, similar to the non-shared case. In case of BC, if a BC session has not been established by the UE, then each UE that wants to enter the room initiates a BC session indicating the selected content as defined in clause 8.3.1. It additionally indicates a SSC room identifier. The BC channel indicated in the session initiation request shall be the one of the shared channel. If a BC session is ongoing, the UE shall switch to the channel being watched by other users of the same SSC room as defined in clause 8.3.4 and shall indicate to the SCF which channel is being watched and the SSC room identifier. The SCF shall check if the user has the rights to be part of the group of users sharing the control. Optionally, the SSC room policy is pushed towards the MF. If synchronization is needed for sharing content, the procedures in clause 8.15 shall be applied and the SyncGroupId shall be populated with the SSC room identifier. The session initiation should be forwarded to the same SCF for the different UE that wants to enter the room. If not, this requires synchronisation procedures between SCFs that are not specified in this release.
|
a51f761c27385e5a8c90041b2c701012
|
182 027
|
8.21.4 Shared service control procedures
|
Depending on the SSC room policy, one or more UEs may perform room moderation tasks and/or content control. This can include adding and removing content to the SSC room. Additionally service commands, such as CoD trick play or BC channel changes, can be performed for the shared service in the SSC room. The change in service state following from this service command is then reflected towards all other UEs involved in the shared service. The SSC room policy can indicate that room moderation and/or floor control is applicable to the shared service. This allows for resolving potential command conflicts that may occur due to interactions between service and/or media control commands received from different users. NOTE: The extent of room moderation and/or floor control can be described by the room policy and may be subject to application design. Appendix B includes further details on the various policies and their use. If synchronization is needed for shared service control, the procedures in clause 8.15 will be applied and the SyncGroupId shall be populated with the SSC room identifier.
|
a51f761c27385e5a8c90041b2c701012
|
182 027
|
8.21.4.1 Shared BC channel changes
|
Depending on the SSC room policy, when a BC service is shared in an SSC room, the channel changes issued by an UE will be reflected towards all others UEs involved in the shared service. The SSC room policy indicates how conflicts in case of non-overlapping BC service packages are handled. For example, if all UEs involved in the shared BC service have a subscription to the same BC service package(s), no specific handling of conflicts is required. If the BC service packages that each UE is subscribed to do not completely overlap, the notification mechanism is employed to indicate and/or resolve conflicts at the UE that causes the conflict occurrence due to an issued channel change command. ETSI ETSI TS 182 027 V3.5.1 (2011-03) 126 Figure 39G depicts the typical steps that occur when one of the UEs involved in the shared BC service issues a BC channel change: Figure 39G: Shared BC channel changes 1) The UE performs broadcast TV channel switching according to clause 8.3.4. 2) If conflicts arise due to non-overlapping BC service packages of the UEs involved in the shared BC service, the UE receives a notification from the SCF to indicate and/or resolve the conflict. Depending on the SSC room policy, the notification contains a message to be displayed on the UE screen and/or instructions for the UE how to handle the conflict. If multiple UEs are impacted by the conflict, each of these UEs should receive a notification. NOTE: Indication of the conflict can be implemented e.g. as visual pop-up on the UE screen, asking the user how to handle the conflict, or through automatically-handled notifications, that e.g. remove the user from the SSC room. The exact service behaviour is subject to implementation choices and can be described in the SSC room policy. 3) If no conflict has occurred, or if conflicts have been resolved, the channel change is reflected towards each UE involved in the shared BC service. The notification procedures from clause 8.11. may be employed.
|
a51f761c27385e5a8c90041b2c701012
|
182 027
|
8.21.4.2 Shared CoD trick play commands
|
Depending on the SSC room policy, when a CoD service is shared in an SSC room, the trick play commands issued by an UE will be reflected towards all others UEs involved in the shared service. The SSC room policy indicates how conflicts in case of (near-)simultaneously received trick play commands are handled. Figure 39H depicts the typical steps that occur when one of the UEs involved in the shared CoD service issues a CoD trick play command. UE CORE IMS SCF MF Other UEs ECF/EFF 1. Broadcast TV channel switching (clause 8.3.4) 2. Notification using signalling path (8.11.1) 3. Instruction for reflecting channel change ETSI ETSI TS 182 027 V3.5.1 (2011-03) 127 Figure 39H: Shared CoD trick play commands 1) The UE issues a media control command, i.e. CoD trick play command, to the serving MF. 2) If the SSC room policy has not been pushed to the MF during shared service initiation, the MF pulls the room policy from the SCF. NOTE 1: The pull mechanism for requesting the SSC room policy by the MF from the SCF also allows for updating the SSC room policy depending on the service states. 3) If conflicts arise due to e.g. (near-)simultaneously received trick play commands of the UEs involved in the shared CoD service, the MF notifies the SCF. 4) The UE receives a notification from the SCF to indicate and/or resolve the conflict. Depending on the SSC room policy, the notification contains a message to be displayed on the UE screen and/or instructions for the UE how to handle the conflict. If multiple UEs are impacted by the conflict, each of these UEs should receive a notification. NOTE 2: Indication of the conflict can be implemented e.g. as visual pop-up on the UE screen, asking the user how to handle the conflict, or through automatically-handled notifications, that e.g. prevent to command being executed. The exact service behaviour is subject to implementation choices and can be described in the SSC room policy. 5) The MF sends the media control response to the UE. 6) If no conflicts have occurred, or if conflicts have been resolved, the media control command is reflected towards each UE involved in the shared CoD service. The notification procedures from clause 8.11. may be employed. SSC Room control UE CORE IMS SCF MF 1. Media Control Request Other UEs 6. Instruction for reflecting media control command 2b. Room policy Response 5. Media Control Response 2a. Room policy Request 4. Notification using signalling path (8.11.1) 3. Indicate conflict ETSI ETSI TS 182 027 V3.5.1 (2011-03) 128
|
a51f761c27385e5a8c90041b2c701012
|
182 027
|
8.21.5 Room deletion procedure for SSC
|
Figure 39I depicts the typical steps that occur when the UE deletes an SSC room. Figure 39I: SSC Room Deletion procedure 1) The UE sends a SSC Room Deletion Request through the Core IMS to the SCF. This request may contain information such as: - the SSC Room Identifier of the to-be-deleted SSC room; - optionally, the service identifier if the room is associated with only one service item; - and optionally additional information such as list of users that need to be informed of the room deletion. 2) The SCF checks if the user has the rights to delete the room and records the SSC room information. It sends an SSC Room Deletion Response including the SSC room identifier through to core IMS to the UE. 3) Deletion of published SSC room information is performed by informing the SSF, by triggering the SCF to send a notification or recommendation, or by sending a message to appropriate other UEs. 4) The SCF may optionally notify the users in the list indicated in SSC room deleted request that the room has been deleted.
|
a51f761c27385e5a8c90041b2c701012
|
182 027
|
8.22 Personalized Service Composition (PSC) procedures
| |
a51f761c27385e5a8c90041b2c701012
|
182 027
|
8.22.1 General
|
This clause describes procedures for the PSC service where multiple BC and or CoD sessions are composed into a single Personalized Service Composition. Existing BC/CoD procedures are used for session setup in order to compose the PSC. Additional steps include selection and configuration of the PSC between the UE and SSF, handling of cases where there are insufficient resources available for the full PSC and synchronization of the PSC constituting media streams. NOTE: This clause only applies when multiple BC and/or CoD sessions need to be associated with each other at the SCF and/or other functional entities. Initiating multiple not-associated BC/CoD sessions and including multiple media streams within a single BC or CoD session are implicitly covered by clauses 8.3.1.1 and 8.4.1.1. UE CORE IMS SCF 1A. SSC Room Deletion Request 2B. SSC Room Deletion Response 2A. SSC Room Deletion Response 1B. SSC Room Deletion Request SSF 4. Notification of SSC room deletion 3. Removal of published SSC information ETSI ETSI TS 182 027 V3.5.1 (2011-03) 129 The following compositions of multicast and unicast media streams are supported: • UE receiving multiple multicast streams within multiple BC sessions. • UE receiving multiple unicast streams within multiple CoD sessions. • UE receiving any combination of multicast and unicast streams within BC and/or CoD sessions.
|
a51f761c27385e5a8c90041b2c701012
|
182 027
|
8.22.2 PSC session initiation
|
Figure 39Ia depicts the typical steps that occur during the establishment of a Personalized Service Composition session and its constituting BC/CoD sessions. Figure 39Ia: Signaling flows for Personalized Service Composition 1) The UE makes a selection of a Personalized Service Composition (PSC) from the SSF. The PSC, to be composed from multiple BC and/or CoD sessions, is either preconfigured in the SSF or configured by the user. The UE generates a PSCid that correlates the different BC/CoD sessions in the PSC. NOTE 1: PSC combinations of multiple BC and/or CoD sessions may require more complex EPG data, as supported by e.g. OMA BCAST service guide. NOTE 2: Users can bookmark a particular PSC combination including its PSCid for future usage. 2) The UE initiates a PSC session with the SCF. The PSC session initiation request contains the PSCid and the IPTV content identifiers of the PSC constituting BC/CoD sessions, see clause I.1. Such content identifiers are for example BCServiceId (clause 7.4.1), CoDId (clause 7.4.1), N-PVRContentId (clause 7.4.1), ad content id (clause 8.14.1) UGC content id (clause 8.9.2) and/or shared content identifier (see clause 8.21.2). It may also contain handling instructions, e.g. instruction for the case that there is insufficient bandwidth to constitute all requested BC/CoD sessions simultaneously. 3) The SCF initiates a BoC or CoD session to the UE, following the procedures of clauses 8.3.1.1.2 or 8.4.1.1.2. The session initiation request includes the PSCid which is used by the UE to correlate the incoming BC/CoD session initiation request with the PSC session. 4) The SCF initiates additional BoC and/or CoD sessions to the UE to build the PSC. Step 4) may be repeated zero or more times. UE RACS SCF (1) Content selection by the UE, generating PSCid SSF MF Core IMS (2) PSC session initiation request (PSCid) (6) PSC session initiation response (3) SCF-initiated BC or CoD session initiation (8.3.1/8.4.1) including PSCid (4) SCF initiated additional BC/CoD session initiation (8.3.1/8.4.1) including PSCid (5) Verification of resource availability, optional SCF-initiated modification of the PSC Repeat 0:n ETSI ETSI TS 182 027 V3.5.1 (2011-03) 130 5) The SCF verifies resources availability. If step 3) and/or one or more of the steps 4) fails due to insufficient resources, then the SCF may try and set up an alternative offer that is either preconfigured in the SCF or signalled as handling instructions in step 2). Examples of such an alternative offer are downgrading, not-initiating or terminating one or more of the PSC constituting BC/CoD sessions, or terminating the PSC session as a whole. An example of the downgrading case is described in clause 8.22.3. 6) The SCF confirms the establishment of the PSC session. At this point, the PSC constituting BC/CoD sessions and their associated media streams are available at the UE and they can be presented to the user as a composite, e.g. picture-in-picture, replacing an audio stream, etcetera. If synchronization is needed between the media streams within the PSC, the procedures in clause 8.15 will be applied. Once the PSC session is established, the UE or the SCF may use the PSCid and the associated PSC constituting BC/CoD sessions to perform actions on the PSC as a whole, for example adding or removing PSC constituting BC/CoD sessions; N-PVR recording the PSC; or terminating the PSC session as a whole. NOTE 3: There are many ways that Personalised Service Composition can be combined with other IPTV services. Examples of these are N-PVR recording of a PSC; continue viewing a PSC on another device, bookmarking of a PSC, shared PSC content; PSC trick play.
|
a51f761c27385e5a8c90041b2c701012
|
182 027
|
8.22.3 Session modification during PSC session initiation
|
The SCF may modify IPTV sessions during the PSC session initiation. Figure 39Ib shows an example of steps that could be taken if resource allocation failure occurs during the PSC session set-up. In this example, the resources for a BC session are reduced in order to use those resources for the CoD session. The example assumes that the quality of the BC session could be scaled back, e.g. by using scalable video or by switching from high definition to standard definition. ETSI ETSI TS 182 027 V3.5.1 (2011-03) 131 Figure 39Ib: Example of session modification during PSC session initiation 1) PSC selection, see clause 8.22.2 step 1. 2) PSC session initiation, see clause 8.22.2, step 2. 3) BC session initiation within PSC, see clause 8.22.2, step 3. UE RACS SCF (1) Content selection by the UE, generating PSCid SSF MF Core IMS (2) PSC session initiation request (PSCid) (6) PSC session initiation response (3) SCF-initiated BC session initiation (8.3.1) including PSCid (4) SCF initiated CoD session initiation (8.4.1) including PSCid (5) SCF-initiated modification of the BC session CoD session initiation request (PSCid) CoD session initiation response resource allocation failure BC session modification request BC session modification response resource allocation modification BC session modification response (4a) CoD continued … resource reservation and allocation CoD session initiation response CoD session initiation response resource allocation failure ETSI ETSI TS 182 027 V3.5.1 (2011-03) 132 4) CoD session initiation within PSC, see clause 8.22.2, step 4. In this example, the resource allocation fails. The CoD session initiation is halted. 5) The SCF verifies resources availability, see clause 8.22.2, step 5. In this example, the SCF detects resource allocation failure. The SCF tries to set up an alternative offer. In this example, the SCF downscales the previously established BC session using a BC session modification procedure see clause 8.3.2, figure 16. 4a) The SCF continues the halted CoD session initiation. Because of the resources freed in step 5), this step is completed successfully. 6) The SCF confirms the establishment of the PSC session, see clause 8.22.2, step 6.
|
a51f761c27385e5a8c90041b2c701012
|
182 027
|
8.22.4 PSC session release
|
When the PSC session is no longer needed, it is released by the UE or SCF.
|
a51f761c27385e5a8c90041b2c701012
|
182 027
|
8.22.4.1 UE-initiated PSC session release
|
Figure 39Ic shows the information flow for UE-initiated PSC session release. Figure 39Ic: UE-initiated PSC session release 1) The UE sends a PSC session termination request to the SCF. 2) The SCF terminates the PSC constituting BC/CoD sessions following the procedures of clause 8.3.3 figure 18 and/or clause 8.4.3, figure 30. 3) The SCF confirms the PSC session termination to the UE.
|
a51f761c27385e5a8c90041b2c701012
|
182 027
|
8.22.4.2 SCF-initiated PSC session release
|
Figure 39Id shows the information flow for SCF-initated PSC session release. NOTE: The system may decide to terminate PSC if all of the constituting IPTV sessions have been terminated. Figure 39Id: SCF-initiated PSC session release 1) The SCF sends a PSC session termination request to the UE. (1) PSC session termination request RACS SCF SSF MF Core IMS (2) UE-initiated release of the PSC consituting BC and/or CoD sessions (8.3.3/8.3.4) (3) PSC session termination confirm UE (1) PSC session termination request RACS SCF SSF MF Core IMS (2) SCF-initiated release of the PSC consituting BC and/or CoD sessions (8.3.3/8.3.4) (3) PSC session termination confirm UE ETSI ETSI TS 182 027 V3.5.1 (2011-03) 133 2) The UE terminates the PSC constituting BC/CoD sessions following the procedures of clause 8.3.3, figure 17 and/or clause 8.4.3, figure 29. 3) The UE confirms the PSC session termination to the SCF. 8.23 Signalling flows for IPTV Content Marker service procedures IPTV Content Marker service procedures consist of two types (see clause 7.5.2). • Storing of IPTV Content Marker data: this type of procedure allows a user to store configurable pointers to content (entire content or parts of content, e.g. favourite scene) and be able to quickly access that content. • Retrieving of IPTV Content Marker data: this type of procedure allows a user to exchange and share IPTV favourite data.
|
a51f761c27385e5a8c90041b2c701012
|
182 027
|
8.23.1 IPTV Content Marker storing procedures
|
Figure 39J provides an overview of the information flows for IPTV Content Marker storing. This procedure can occur at any time during IPTV services (BC/CoD/N-PVR/etc.). Figure 39J: IPTV Content Marker storing procedure 1) The UE sends a IPTV Content Marker storing request to save content information. This content information may include various information, e.g. the entire/scene of content with/without current watching. 2) The IMS core forwards this request to the SCF. 3) The SCF stores the indicated content information as Content Marker data for this user. The data model of IPTV Content Marker items is defined in clause 7.5.2. 4) The SCF confirms storage of IPTV Content Marker data. 5) The IMS core forwards the response to the UE.
|
a51f761c27385e5a8c90041b2c701012
|
182 027
|
8.23.2 IPTV Content Marker retrieval procedures
|
Figure 39K provides an overview of the information flows for IPTV Content Marker retrieval. This procedure can occur at any time and may be used to share IPTV Content Markers. UE Core IMS SCF (1) IPTV Content Marker Storing Request (3) IPTV Content Marker (2) IPTV Content Marker Storing Request (4) IPTV Content Marker Storing Response (5) IPTV Content Marker Storing Response store ETSI ETSI TS 182 027 V3.5.1 (2011-03) 134 Figure 39K: IPTV Content Marker retrieval procedure 1) The UE sends a IPTV Content Marker retrieval request. NOTE: The IPTV content identifier (clauseI.1) or other parameters (e.g. the fields required by the user) may be specified in the request to help filtering the IPTV Content Marker data. 2) The SSF returns IPTV Content Marker retrieval response. The response shall contain the user's IPTV Content Markers. If there is any user id in IPTVContentMarkerSourceUser parameter, then the SSF response also contains the indicated user's IPTV Content Marker data. If there is any IPTV content identifier or other parameters in the request, then the SSF retrieves and responds the indicated IPTV Content Marker data.When retrieving that user's IPTV Content Marker data, the SSF shall perform authorization according to that other user's IPTVContentMarkerAuthorizedViewUser settings. Alteratively, the UE may fetch the IPTV Content Markers from the SCF. In that case the SCF shall generate the IPTV Content Marker retrieval response. This response shall contain the user's IPTV Content Markers. If there is any user id in IPTVContentMarkerSourceUser parameter, then the SCF response also contains the indicated user's IPTV Content Marker data. If there is any IPTV content identifier or other parameters in the request, then the SSF retrieves and responds the indicated IPTV Content Marker data. When retrieving that user's IPTV Content Marker data, the SCF shall perform authorization according to that other user's IPTVContentMarkerAuthorizedViewUser settings.
|
a51f761c27385e5a8c90041b2c701012
|
182 027
|
8.23.3 IPTV Content Marker update/removal procedures
|
Figure 39L provides an overview of the information flows for IPTV Content Marker update/deletion. Figure 39L: IPTV Content Marker update/removal procedure UE Core IMS SCF (1) IPTV Content Marker Update Request (3) IPTV Content marker update/removal (2) IPTV Content Marker Update Request (4) IPTV Content Marker Update Response (5) IPTV Content Marker Update Response UE SSF (1) IPTV Content Marker Request (2) IPTV Content Marker Response ETSI ETSI TS 182 027 V3.5.1 (2011-03) 135 1) The UE sends a IPTV Content Marker Update request to update/remove content marker data. In case of update, the request includes the IPTVContentMarkerID and updated parameters. In case of removal, the request can include a specific IPTVContentMarkerID or no IPTVContentMarkerID. The latter means that all content markers shall be removed. 2) The IMS core forwards this request to the SCF. 3) The SCF updates or removes the indicated Content Markers for this user. In case of update, the parameters that are not indicated in the request shall not be changed. 4) The SCF confirms update/removal of IPTV Content Marker data. 5) The IMS core forwards the response to the UE.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.