hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
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. |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 8.24 Role of BGF in IPTV | In certain IPTV scenarios there is a need to bypass the BGF for scalability reasons. For example, the BGF could be bypassed when using MPEG2-TS directly over UDP transport, as well as, for RTP(RTCP) transmission when there is no RTCP towards the network. It shall be possible to bypass the BGF. Its use is a local decision taken by the network provider during the IPTV session setup based on the session information provided. |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 8.25 Procedures for service initiation by remote UE | The service initiation by remote UE can be used by one remote UE to activate the target UE to start-up the IPTV service, for example, it can be used to remote start-up UGC, CoD or BC services. Figure 39M depicts the typical steps for service initiated by Remote UE. ETSI ETSI TS 182 027 V3.5.1 (2011-03) 136 Figure 39M: Service initiation by Remote UE 1A) The Remote UE sends a remote service start-up request through the Core IMS to the SCF. The request carries the necessary parameters indicating the service identified by the IPTV service type identifier (see clause I.2), e.g. BC service or UGC service, IPTV content identifier (see clause I.1) when appropriate, user identifier of Target UE which start-up the service and user identifier of the remote UE. 1B) The SCF performs service authorization as described in clause 5.1, if the Remote UE is allowed to perform remote start-up operation of the service, the SCF forwards the remote service start-up request through the core IMS to the Target UE. And the user of Target UE may deny the request even if the SCF authorized. NOTE 1: The SCF authorizes the remote UE by checking the user profile of the Target UE. 1C) The Target UE sends a remote service start-up response through the Core IMS to the SCF. 1D) The SCF forwards remote service start-up response through the Core IMS to the Remote UE. NOTE 2: The remote service start-up request in steps 1A-1D may directly sent to the target UE if SCF does not need to perform authorization. 2) The Target UE initiates the service indicated in the remote start-up request, e.g. BC or CoD session initiation following the procedures of clauses 8.3.1.1 or 8.4.1.1. CORE IMS SCF MF 2). Service initiation procedures Target UE Remote UE 1A. Remote service start-up Request 1A. Remote service start-up Request 1D. Remote service start-up Response 1D. Remote service start-up Response 1B. Remote service start-up Request 1B. Remote service start-up Request 1C. Remote service start-up Response 1C. Remote service start-up Response ETSI ETSI TS 182 027 V3.5.1 (2011-03) 137 8.26 Signalling flows for IPTV service state data updates/requests IPTV service state data may be updated by MF as described in clause 8.26.1. Furthermore, IPTV service state data requests may be initiated by the SCF as described in clause 8.26.2. The procedures are limited to data within the SSD model and which the SCF cannot derive directly from ongoing traffic and events. |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 8.26.1 IPTV service state data updated by MF | The procedure described in figure 39N is used to update IPTV service state data by the MF. The SSD may need to be updated for example when a user pauses a streaming or terminates the session. Figure 39N: IPTV service state data updated by MF MF is triggered by an event, e.g. by detecting a pause or and end of a session and decides to send changes of SSD to the SCF. 1) MF sends an SSD update request to save the current SSD. This request may also include a indicator to inform the SCF of the reason for the SSD update. 2) The IMS core forwards this request to the SCF. 3) The SCF updates the SSD. 4) The SCF confirms the SSD update. 5) The IMS core forwards the response to the MF. 8.26.2 IPTV service state data update requested by the SCF This procedure allows the SCF to acquire an update of the current service state from the MF during an ongoing session. Figure 39O provides an overview of the information flow for an SSD update request by the SCF. This procedure can occur at any time during ongoing IPTV services (CoD/N-PVR/, etc.). (1) SSD update Request (3) Save SSD update SCF Core IMS MF Event triggering the SSD update (2) SSD update Request (4) SSD update Response (5) SSD update Response ETSI ETSI TS 182 027 V3.5.1 (2011-03) 138 Figure 39O: SCF IPTV service state data Request Procedure 1) The SCF sends an SSD request to the MF, via the IMS core, to request the service state 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 an SSD response. 5) The IMS core forwards the response to the SCF, which updates the SSD accordingly. 9 Interactions between IPTV services and other TISPAN services Several approaches can be employed for realizing the interaction between IPTV services and other TISPAN services. This clause describes approaches that are considered within the TISPAN architecture, e.g. where application servers interact directly through Core IMS. Two other approaches involving 3GPP SCIM and OSA/Parlay methods are described in annex C. |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 9.1 Presence and IPTV | IPTV services may be combined with the presence service capability. This clause describes the mechanisms that apply when IPTV services are combined with the presence service capability. These mechanisms may also be used for other purposes then publishing user presence information. For example they may be used to gather statistics about BC TV Service or user behaviour information. |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 9.1.1 Presence architecture and functional description | The architecture and functional description of the presence service capability when used in relation to the IPTV services conform to TS 182 008 [10]. SCF Core IMS MF (1) IPTV SSD Request (3) MF fetches the information (2) IPTV SSD Request (4) IPTV SSD Response (5) IPTV SSD Response ETSI ETSI TS 182 027 V3.5.1 (2011-03) 139 |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 9.1.2 Presence attributes for IPTV | The Presence attributes defined in TS 182 008 [10] apply. In addition, the following specific IPTV attributes shall be supported: • BC service activated; • CoD service activated; • PVR service activated. If the IPTV presence attribute "channel currently accessed" is supported, then the machine-readable part of the identification of the channel shall be globally unique. The term globally unique here means that there is no ambiguity in the identification of the channel if presentity and watcher (for terminology, see in TS 182 008 [10]) are with different network operators and/or in different countries. The following specific IPTV attributes may also be supported: • IPTV service activated; • IPTV service type identifier (see clause I.2) should be used to identify which service(s) are activated: - UGC service activated; - PCoD service activated; - TAI service activated; - PCh service activated; - SSC service activated; - PSC service activated. • IPTV content identifier (see clause I.1) should be used to identify which content(s) are currently accessed/watched: - BC TV Service currently accessed; - programme currently watched, when available; - content currently accessed. • current service state (e.g. paused, playing, in trick play mode). • IPTV service access history. It is up to user's decision to include specific IPTV attributes in presence document. Note that if a service relies on user's presence information, but the user has decided not to publish this information, the user may not be able to utilize the service. When the "BC service activated" attribute is included in a presence document, the attributes "BC TV Service currently accessed" and "programme currently watched" may also be included, depending on user preferences. These attributes shall not be present in a document if the "BC service activated" attribute is not present. When the "CoD service activated" or the "PVR service activated" attribute is included in a presence document, the attribute "content currently accessed" may also be included depending on user preferences. This attribute shall not be present if the "CoD service activated" or the "PVR service activated attribute" is not present. ETSI ETSI TS 182 027 V3.5.1 (2011-03) 140 |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 9.1.3 SIP related procedure | The SIP related procedures defined in ES 283 030 [13] apply. The publication of CoD related presence information happens: • after completion of CoD session initiation procedure; • after completion of CoD session termination procedure. The publication of BC related presence information happens: • after completion of BC session initiation procedure; • after completion of the BC session termination procedure; • optionally, when the UE successfully subscribes to a particular multicast channel (i.e. channel hopping). In order to cope with overload possibly caused by numerous channel-hopping, it shall be possible to define a timer to limit the number of publications. This timer is started and reinitialised after each channel change. Publication shall only be sent when the timer elapses. NOTE: Preventing overload caused by numerous IPTV service access entries, is possible by defining a timer or ceiling to limit the number of publications. The publication of UGC related presence information happens: • after completion of UGC creation session initiation procedure; • after completion of UGC creation session termination procedure; • after completion of UGC watching session initiation procedure; • after completion of UGC watching session termination procedure. The publication of PCoD related presence information happens: • after completion of PCoD session initiation procedure; • after completion of PCoD session termination procedure. The publication of PCh related presence information happens: • after completion of PCh session initiation procedure; • after completion of PCh session termination procedure. The publication of TAI related presence information happens: • after completion of TAI session initiation procedure; • after completion of TAI session termination procedure. |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 9.2 Incoming call management | The combination of basic IPTV services (e.g. Broadcast, CoD and N-PVR) with telephony allows a user to have increased control over incoming calls when watching TV. This clause describes an approach, where the IPTV SCF decides based on incoming call state, IPTV service state and user profile settings how to handle the call. Approaches using only standard IMS telephony mechanisms to inform IPTV UE of incoming calls are described in [2]. Also, if the user is registered with the same IMPU on the UE (Phone) and UE (IPTV ) normal IMS forking procedures (as described in [2], clause 4.2.7) apply. The following procedure only applies if the user is registered with different IMPUs on the aforementioned UEs or when forking results in the IPTV SCF being involved. ETSI ETSI TS 182 027 V3.5.1 (2011-03) 141 |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 9.2.1 Procedure for incoming call management | Figure 39P shows a signalling flows for incoming call management. Figure 39P: Signalling flows for incoming call management NOTE 1: "Incoming call" indicates an incoming call that may come from different sources such as a telephony AS, an originating network, or a UE. 1) An incoming call is received by the Core IMS. 2) The Core IMS forwards the session initiation request to SCF. 3) The SCF retrieves user profiles and IPTV service and call state. 4) Optionally, the SCF notifies the user and ask what to do with the incoming call, based on IPTV service and call state, if this is indicated in the user profile (see clause 9.2.2). In case of no answer from the user on the IPTV UE B1 after a timeout, SCF may perform any of the actions in step 5. 5) Optionally, the SCF performs one or more actions. For example, these actions are performed based on - the IPTV service and call state; - and/or the answer of the user if step 4 is performed and an answer from the UE has been received by the SCF; - and/or indications in the user profile (e.g. pause on incoming call using network-controlled trick play from clause 8.16 or redirect the call to voicemail). 6) Telephony session establishment: based on the outcome of the previous steps the SCF handles the incoming call (e.g. accept, reject the call or forward to another AS). CORE IMS SCF Incoming call 1. Session Initiation Request 4. UE notification and selection (clause 9.2.2 / 9.2.3) 2. Session Initiation Request 3. User profile check and state handling 6. Telephony session establishment 5. SCF-Controlled action 7. UE notification UE B2 (Phone) UE B1 (IPTV) User B User A ETSI ETSI TS 182 027 V3.5.1 (2011-03) 142 7) Optionally, the SCF notifies the user on its UE B1 (IPTV ) about the incoming call (e.g. "caller id" presentation on the TV) and/or optionally, about the action that has been performed during step 4 on behalf of the user. NOTE 2: The order of the steps 4-7 may change. Steps 4, 5 and 7 are optional. For example, an incoming call notification that requires user action is covered on step 4; an incoming call notification that only present the incoming call (e.g. "caller id") is covered by step 7. 9.2.2 Incoming call accepted on a phone device Figure 39Q shows a signalling flow for an incoming call accepted by user. Figure 39Q: Signalling flows for an incoming call accepted by user 1) The SCF sends a notification to UE B1 (IPTV) with a message about incoming call from user A (using notification procedures using signalling path as described in clause 8.11.1.1). 2) User B may select from multiple options how to handle incoming call, for example: - Accept on TV; the TV signal is paused and phone is ringing. Steps 1-3 from previous clause §9.2.1 UE B1 (IPTV) CORE IMS SCF UE B2 (Phone) Incoming call Network 1. Notification about incoming call 2. Selection of option for handling call 3. Selection response for handling call 4. Session Initiation Request to UE Phone 5. Session Initiation Request to UE Phone User A User B 10. Session established 9. Session Initiation Response 8. Session Initiation Response 7. Session Initiation Response 6. Session Initiation Response Pick up ETSI ETSI TS 182 027 V3.5.1 (2011-03) 143 - Accept on phone; the call is forwarded to user B's UE B2 (Phone). According to his user profile and service and call states, the TV can either be paused or can continue. - Route to mailbox; if user B does not answer the call or based on his user profile, the call is forwarded to his voicemail box. - Refuse; user B does not answer the call. 3) Based on the user decision in step 2, UE B1 (IPTV) sends to SCF response how to handle the incoming call 4) - 5) The SCF forwards the session initiation request to UE B2 (Phone) via Core IMS in B2BUA mode (The SCF stays in the call path). 6) - 7) UE B2 (Phone) sends a session initiation response to the originating network via the SCF (in B2BUA mode). 8) - 9) SCF sends the session initiation response to the originating network via the Core IMS. 10) Telephone session established. |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 9.3 Message and IPTV | 9.3.1 Messaging procedures Messaging procedure is used for several purposes: where messages are sent between users or between system and users. Following procedures may be primarily used for immediate messaging described in TS 181 016 [15] in section in clause 6.2.3 to provide services specified in TS 122 340 [16] together with IPTV services. Several additional specific use cases described in TS 181 016 [15] (e.g. in clause in annex A) require integration of existing messaging systems (in this case IMS based messaging) with IPTV service logic to provide blended IPTV and messaging service (e.g. messaging during BC service or chat discussion related to content or related to used IPTV service, etc.). Figure 40 depicts the typical steps that occur when the UE wants to send message from one user to one or more other users using signalling path. Figure 40: messaging procedure using signalling path 1) UE sends a message request via IMS core to SCF using signalling path for IMS messaging mechanisms [2]. Message contains message itself (supporting different media content types as in [16]) and also parameters which identify related IPTV service blended with this messaging procedure. 1. Message request send via core IMS CORE IMS SCF 1..n UEs 3. Message forwarded via core IMS to 1..n UEs UE 2. Validating request, evaluate destination address based on service logic, generate message and presentation rules ETSI ETSI TS 182 027 V3.5.1 (2011-03) 144 2) SCF evaluates appropriate destination UEs for delivery message to specified group of users (as users interaction related with IPTV services) based on service logic (and other conditions e.g. user profile or messaging rules) specified for required IPTV service. SCF may also modify/generate messages (original message may be included together with additional IPTV related information e.g. watched channel, form of presentation of message, etc.). 3) SCF sends message (original/modified) via IMS core using IMS messaging framework [2] to one or more UEs. NOTE : In this example the messaging service function is not explicitly shown for brevity. IMS messages may traverse the messaging service function, and are under service provider control. Furthermore, while figure 40 shows the SCF in the path of the IMS message, this is an option and need not be the case for all IMS messages originating/terminating from/to an IPTV end user. The SCF would typically be in the signaling path of an IMS message if the message is addressed explicitly to it, or if it has to perform some special procedure on the message. 9.3.2 Procedures for deliver messages of BC service using media path This clause describes mechanisms of deliver messages that are associated with a BC service using media path. These mechanisms may be used for some purposes. For example they may be used to participate in a comment service associated with a BC program; one user can send his comment to the SCF using IMS immediate message services, then the SCF and the MF deliver the comments to all users who subscribed to the comment service associated with the BC service. Figure 41 depicts the typical steps that occur when one user sends IMS immediate messages to SCF, and SCF and MF deliver the message to users who subscribed to the message services associated with the BC service. NOTE 1: The parameters for joining the multicast group, i.e. multicast address, need to be available to UE before it receives the messages delivered using media path. Figure 41: Deliver messages of BC service using media path 1) UE joins a BC service and the messages multicast group associated with the BC service, e.g. comment services of a BC service. 2) UE initiates an IMS immediate message request carrying the message, which is specified in the IMS stage 2 specification [2]. The immediate message is routed by Core IMS to the SCF in charge of the delivery of messages associated with the BC service. (2) Send IMS Message to SCF UE Core IMS SCF MF (1) UE joins a BC service and the message group associated with the BC service (3) Notification procedures using media path (in clause 8.11.1.2) ETSI ETSI TS 182 027 V3.5.1 (2011-03) 145 3) The SCF detects which BC service is associated with the IMS immediate message e.g. by the destination of the immediate message, and sends the IMS immediate message to the selected MF. The MF transfers the IMS immediate message to the multicast group associated with the BC service. The procedures use mechanisms of delivering notification using media path specified in clause 8.11.1.2, and the notification request from SCF to the selected MF at least contains parameters of BC service ID and the message. NOTE 2: Existing mechanisms of IMS could be used for the SCF to distinguish IMS immediate message from normal IMS message, e.g. by checking the content type of the message body. |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 9.4 Event Handling involving the SCF | Event handling by the SCF takes place if the SCF receives events from several sources. The events can include requests from the UE, new content arrival notification, presence updates, trick play reports from MF, channel change reports from UE, events from other NGN application servers, external applications and so on. Usage of this procedure occurs in several cases under clause 8. SCF involvement is required depending on the event and the user profile configuration. Examples include incoming call management involving multiple UE's (e.g. pause on incoming call), emergency warning and alerting systems, or parental control. In such cases the SCF needs to correlate the event with the right UE and apply service logic to determine the applicable action to the UE and/or MF. Figure 42: Event handling involving the SCF 1) The SCF receives an incoming event which requires handling. NOTE 1: It is up to the IPTV Service Provider, on behalf of the user and/or based on the service requirements, to decide when to route an incoming event to the SCF a or send it directly to the UE. 2) The SCF correlates the incoming event with the designated user/group of users and/or UE's, performs authentication and detects the ongoing IPTV service status. Detection of the IPTV service status is done based on IPTV Service Action Data or using IPTV Presence information. NOTE 2: The SCF can decide which (if any) further actions to perform, e.g. based on user preferences and detected service state. 3) The SCF performs an action towards the UE and or MF, e.g. it can send a notification to the UE or instruct the UE to send a trick play command/change the channel. UE Core IMS SCF 3 SCF action towards UE and/or MF 2 Event handling MF 1 Incoming event triggering the handling ETSI ETSI TS 182 027 V3.5.1 (2011-03) 146 |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 10 Security | |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 10.1 Authentication | Authentication procedures for the Ut reference point conforms to TS 187 003 [5]. |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 10.2 Content Protection | The locations and related reference points of the following elementary functions are defined in TS 187 003 [5]. They are reproduced below for information. For content protection the following elementary functions are used: • Content licensing: This elementary function handles the licenses issuing related functions, including generation and distribution of the licenses to the desired entities. • Key management: This elementary function handles the management of the security keys on behalf of the content usage profiles as defined in the content licencing, including generate and provide the keys and corresponding parameters to the desired entities. • Content encryption: This elementary function handles the content protection related operations, e.g. content encryption and encapsulation operations, etc. These three elementary functions may be flexibly located in existing functional entities or new ones as a whole or in independent parts. NOTE: Some of these elementary functions may be executed on-line (in real-time) or off-line (in this case could be part of the management). |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 10.3 Service Protection | The locations and related reference points of the following sets of elementary functions are defined in TS 187 003 [5]. The function groups are reproduced below for information. The service membership (SMF), service key management (SKMF) and service protection (SPF) functions described in this clause each involve a set of elementary functions required as part of a generic model for service protection. The SMF, SKMF, and SPF do not duplicate, but collaborate and interact with existing elementary functions in order to perform service protection. For service protection the following sets of elementary functions are used: • Service membership elementary functions (SMF): This set of elementary functions handles the granting and revoking of service access rights to access the IPTV services. Metadata related to the service rights management are maintained by the SMF. NOTE 1: The SMF is handled in an array of existing elementary functions (e.g. service key triggering function) and functional entities. For example, service authorization may be provided by the SCF, and meta-data is maintained in the UPSF. • Service key management function (SKMF): This set of elementary functions acts on behalf of the Service Membership Function and as such manages service security keys, including generating and providing keys and corresponding parameters to the desired entities. • Service protection function (SPF): This (set of elementary) function(s) handles the service protection related options, e.g. service confidentiality, integrity operations and authorization at the service access point, etc, using the keys generated in SKMF. NOTE 2: The SPF includes group association, e.g. multicast group. ETSI ETSI TS 182 027 V3.5.1 (2011-03) 147 |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 11 Charging | IMS charging principles apply as defined in ES 282 010 [i.3]. TISPAN IMS-based IPTV shall use the generic IMS charging model using the standardized Rf reference point for offline- and Ro reference point for online charging. NOTE: Further IPTV service-specific charging may be required in addition to the generic IMS charging but is out of scope for the present document in this release. |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 12 Management | |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 12.1 Management requirements | For each IPTV service, several entities require to be provisioned with necessary network parameters (e.g. multicast addresses for multicast services, source of original content, etc.) and to associate specific content or service with these network parameters. These entities are: • the SSF, as it needs to provide the UE with the content identifier associated to an IPTV service and possibly with a set of network parameters (control and/or content channel descriptions) necessary to initiate an IPTV session; • the MFs, as they need to associate a content identifier with multicast or unicast streams to be delivered to the UE; • the SCF, as it may also need to provide the UE with network parameters in response to service initiation requests, in configurations where the SSF does not provide this information beforehand. Consistent information has to be provisioned on these entities. |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 12.2 Content management | Content management functionalities are responsible for managing acquisition of content and service information (e.g. metadata) from content and its metadata sources of content provider, controlling validation and/or processing/adaptation to the required format and also to provide management functionalities for supporting distribution of the prepared content to the media delivery function and distribution of content among different media delivery functions. NOTE: Content management is used in the case of offline or online ingest of the content. The online ingest means receiving content directly streamed from the content provider. The offline ingest refers to content files delivered by other means than the online (e.g. such on physical media like DVD, CD, etc.). The content management is used by the IPTV service provider to statically provision the content. Content management functionalities can consist of the following groups of elementary functions: • Content acquisition - responsible for content management functionalities needed to acquire, aggregate and import content/metadata from multiple external sources of content providers. • Content validation/adaptation - after acquisition it could be necessary to manage content/metadata format validation and verification as well as to define a relation between content and its metadata. Management can also control media or metadata adaptation and/or processing (e.g. transcoding, packaging, scheduling, resolution conversion, editing, etc.) to the required type of media files or streams. ETSI ETSI TS 182 027 V3.5.1 (2011-03) 148 • Content distribution Control - management functionalities for control the distribution of content and its metadata from content providers when content acquisition/ content validation/adaptation were performed to appropriate functional entity (e.g. media files storage in MDF). This function handles the whole lifecycle of the content and provide management support for its distribution to media delivery distributed architecture (e.g. uploads on video streamers, moving according to management criteria such as popularity, regionalization, un-referenced content, MDF resources and so on). Additionally, this function can control the content distribution among MDFs (e.g. delete content in some MDFs, moving content from one MDF to other MDFs) according to some criteria such as content popularity. |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 13 Support of Metadata | |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 13.1 Introduction | IPTV Metadata enriches the service experience of the IPTV Services a user has access to. IPTV Metadata may originate from the User, the NGN Service Provider, the Application Provider or the Content Provider. The Metadata should be processed, filtered and enriched by involved IPTV solution entities in order to improve the user experience. NOTE 1: Processing, Filtering and Enriching Metadata may be based on techniques like personal preferences, additional subscribed-to services and other means and are out of scope of the present document. NOTE 2: How user originated Metadata is injected into the IPTV solution is out of scope of the present document. NOTE 3: Content metadata may be delivered along with the content in real time (from MDF). In this case metadata might differ from the metadata already stored in the SSF and therefore SSF can require update them with relevant metadata from MDF. Also, IPTV CRS might be a service requiring the SCF to access actualised metadata. Generally, if UE or other entity needed most updated metadata it is requesting them from SSF (SSF is responsible acquire most updated metadata). NOTE 4: The mechanisms and handling of all possible cases for synchronization of metadata cross multiple IPTV Fes, are not provided in the current specification. The access to Metadata may be considered as a service in itself which shall be protected by appropriate service authorization means before the Metadata is delivered to the UE. |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 13.2 SSF support | IPTV Metadata may be delivered outside of an IPTV service session by the SSF. Xa shall be used for the Metadata delivery. |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 13.3 SCF/MF support | IPTV Metadata may be delivered as part of a normal IPTV service session or inside an IPTV service session dedicated to Metadata delivery. In the first case, the Metadata is sent in addition to Media as part of the IPTV session. In either case the Metadata capabilities are negotiated during session setup or session modification between UE and SCF. The Metadata itself is delivered via the MDF through unicast or multicast via Xd. ETSI ETSI TS 182 027 V3.5.1 (2011-03) 149 |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 14 Support of Mobility Capabilities | To support the mobility capabilities of IPTV services, the UE shall support roaming in the Visited Network. When the UE is located in the Visited Network, it can access the IPTV services in its own home network. Sometimes when the IPTV Service Provider servers both home network and visited network, the MF can server both visited network and home network. Annex H give interconnection examples to support of mobility capabilities. |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 15 Emergency alert | The IPTV solution shall enable deliver emergency alerting based on different aspects (e.g. type of emergency situation, priority, and locality). TISPAN IMS based IPTV subsystems may in practice also require secure mechanisms to acquire, verify and inject the appropriate content (alert message or emergency live transmission) after ensuring that it comes from an authorized source. The emergency alerts will only achieve their purpose if they are immediately delivered to UE (interruption of actually watched content may be required) when they alert the public promptly, accurately and efficiently and then correctly decoded and rendered on the user equipment. Following examples of procedures may be used for delivery of emergency alert to UE (other existing delivery mechanisms are also possible): • using notification procedures to deliver message (notification procedures as in clause 8.11.1.1) with confirmation of delivery; • using notification procedures using multicast media path as described in clause 8.11.1.2 (for stream insertion or replacement of actually watched content) or to deliver live emergency transmission via multicast (e.g. using SCF-initiated BC session initiation). NOTE: Emergency alert capability can be subject to local or regional regulation. ETSI ETSI TS 182 027 V3.5.1 (2011-03) 150 Annex A (informative): Integration of non-SIP-AS Service Discovery Function in IMS based IPTV A.1 Introduction Clause 5 defines Service Discovery and Selection (SD and S) as a two step process consisting of Service Discovery and Service Selection. While clause 5 focuses on discovering services by an SIP based SDF entity, the Service Selection uses non-SIP mechanisms. This annex describes using non-SIP SDF to reuse standard non-SIP Service Discovery technologies such as DVB-IP Service Discovery as specified in TS 102 034 [6]. A.2 Architecture Transport Control Functions SSF Core IMS Transport Processing Functions IPTV Media Functions CoD-MCF CoD-MDF BC-MCF BC-MDF N-PVR-MCF N-PVR-MDF IPTV Service Control Functions CoD-SCF BC-SCF N-PVR-SCF Xc Xd Gm Gq' Xa ISC e2 UPSF Cx e4 RACS NASS UE IPTV Media Control Functions IPTV Media Delivery Functions Sh Ut y2 SDF Xp Media Delivery, Distribution & Storage Transport Functions Application and IPTV Service Functions Xa’ Figure A.1: Functional architecture for IPTV services integrating non-SIP SDF A.2.1 Functional entities Figure A.1 depicts the IMS based IPTV architecture based on figure A.2 using a non-SIP AS SDF for Service Discovery. All entities are defined in clause 5. ETSI ETSI TS 182 027 V3.5.1 (2011-03) 151 A.2.2 Reference points Figure A.1 depicts the IMS based IPTV architecture based on figure A.2 using a non-SIP AS SDF for Service Discovery. All shown reference points are defined in clause 6 except Xa' which is described in the following clause. A.2.2.1 UE - SDF (Xa') This reference point delivers Service Discovery Information, i.e. SSF addresses in the form of URIs and/or ip-address, from the SDF to the UE. Both Unicast and Multicast delivery of this information is possible. The use of Xa' conforms to TS 102 034 [6] clause 5.2.5, where the term "HNED" is to be replaced by "UE" and where "Location(s)" carries the SSF address(es). A.2.3 Procedures A.2.3.1 IPTV service attachment and selection Figure A.2 defines steps 3 and 4 of figure 9 in case the SDF is not SIP-AS based. Figure A.2: IPTV service attachment and selection 1) The UE requests the SDF it was assigned. This assignment may have occurred during the network attachment phase, during offline provisioning or by other means. 2) The SDF determines the proper SSF (or SSFs). It is for further study how the SDF may take into account the UE's capabilities, the user's profile and/or the location of the UE (Personalized Service Discovery). 3) Configuration information that includes the SSF address(es) is (are) routed back to the UE. 4) The UE requests the SSF to get the selection data. 5) The SSF delivers the requested data to the UE. NOTE: If a non-SIP AS SDF is used for IPTV service attachment, no IMS registration prior to step 1) of figure A.2 is required. Therefore, step 2 of figure 9 (IMS registration) can occur in parallel to, before or after the procedure described in figure A.2. UE SDF SSF (2) SSF Election (1) attachToIPTV (3) Service Config Info ( Elected SSF address,...) (4) request selection data (5) retrieve selection data (EPG, CoD catalog, …) ETSI ETSI TS 182 027 V3.5.1 (2011-03) 152 Annex B (normative): Policies for Shared Service Control B.1 SSC room policies An SSC Policy is associated with an SSC room, identified by the RoomId attribute. A user in an SSC room has an SSC Privilege containing the allowed actions by that user. Additionally, SSC room privileges can be allocated to service logic for performing room administration tasks. Note that this annex does not describe an SSC room data model, nor does it describe implementation of the SSC room itself. Figure B.1 shows a generic data model for an SSC Policy. Figure B.1: Data model for SSC Policy • Room Administration actions: - AddUser: boolean indicating whether the user is allowed to add other users to the SSC room. Adding users to the room is done by extending the list of allowed users associated to the room, that is exchanged during SSC room creation (step 1A of clause 8.21.2). - NotifyUser: boolean indicating whether the user is allowed to send notifications to other users of the SSC room. If a user is allowed to send notifications related to the SSC room, the messaging procedures from clause 8.11 apply. - InitiateRoom: boolean indicating whether the user is allowed to initiate a service in the SSC room (clause 8.21.3, step 3). If the SSC room has been created by another user, this user may or may not be allowed to do that. ETSI ETSI TS 182 027 V3.5.1 (2011-03) 153 - DeleteRoom: boolean indicating whether the user is allowed to delete the SSC room. SSC room deletion is performed according to clause 8.21.5. - GiveFloor: boolean indicating whether the user is allowed to give the floor to another user in the room. Typically, a chairman has this right. Specific procedures for floor control are out of scope of this release. - TakeFloor: boolean indicating whether the user is allowed to take floor control. Typically, a presenter has this right. Specific procedures for floor control are out of scope of this release. - SendMessage: boolean indicating whether the user is allowed to send messages to other users of the SSC room. If a user is allowed to send messages related to the SSC room, the messaging procedures from clause 9.3. apply. - IsAdmin: boolean indicating whether the user has administrator rights. - IsInitiator: boolean indicating whether the user has initiated this SSC room, and has associated rights. - ArbitrateConflict: boolean indicating whether the user has right to arbitrate a conflict. An example of such conflict is different users wanting to watch different BC channels. NOTE: Different approaches for the arbitration of conflicts exist, but are not describing further here. • ContentControl actions: Describes actions that can be performed in relation to content services. In case of a shared BC service, the content is a channel. In case of a shared CoD service, the content is a CoD item and so on: - AddContent: boolean indicating whether the user is allowed to add the content to the SSC room. - ChangeContent: boolean indicating whether the user is allowed to change the content being watched in the SSC room. - RemoveContent: boolean indicating whether the user is allowed to remove content from the SSC room. - BlockContent: boolean indicating whether the user is allowed to block content from being watched in the SSC room. Parental control may be a reason to block content. - TrickplayControl: PlayContent: boolean indicating whether the user is allowed to play content. PauseContent: boolean indicating whether the user is allowed to pause content. RewindContent: boolean indicating whether the user is allowed to rewind content. RestartContent: boolean indicating whether the user is allowed to restart content. FastForwardContent: boolean indicating whether the user is allowed to fast forward content. StopContent: boolean indicating whether the user is allowed to stop content in the SSC room. The SSC policy, or part of it, may be performed at the UE or at the MF. This would prevent the user from sending administration and/or content control actions that are is not allowed to. Policy distribution towards the UE is not described in the present document. Tight floor control follows strict rules on the actions that users may perform in relation to the service state of the SSC room. This may require a more detailed floor control policy that sets those rules. It could describe the use of timers and master allocation through e.g. tokens. Such policy is not described in the present document. Loose floor control allows any user to perform administration and/or content control actions without first taking the floor. This can result in control conflicts. An example is when two users are simultaneously trying to switch to different BC channels. Such conflicts should be automatically resolved by the network, so that the service state of the SSC room and the associated UE's remain aligned. ETSI ETSI TS 182 027 V3.5.1 (2011-03) 154 Annex C (informative): Architectures for Interactions between IPTV services and other TISPAN services This Annex contains examples of architectures that can enable the interaction between IPTV services and other TISPAN services. The examples of architectures given refer to existing work and serve to clarify how service interaction can achieved by using this existing work. For these architectures, it is assumed that service interaction requires a dedicated Application Server that may explicitly implement the blended service functionality (e.g. pausing the TV on incoming call, or watching apart together). Such an AS can be seen as an external application with respect to the TISPAN IPTV architecture. C.1 Interaction based on an OSA/Parlay/Parlay X SCS This approach is based an OSA/Parlay/Parlay X Service Capability Server (SCS), that provisions standardized interfaces and APIs to external and third party application servers. The use of such an SCS is described in ES 204 915 [i.5], ES 202 504 [i.6], TS 129 198 [i.7] and TS 129 199 [i.19]. C.1.1 Service Capability Server (SCS) The OSA SCS acts as a secure gateway between the underlying network and the application with the OSA architecture. It is responsible for providing specific service abilities to third party applications. An SCS further serves to make an abstraction of the functionality offered by the network, in effect offering the service capability features of the underlying network to the third party applications. C.1.2 Architecture Figure C.1 shows a simplified version of the IMS-based IPTV architecture from figure 2 in clause 5.1.1, with interfaces to an SCS and subsequent external applications. ETSI ETSI TS 182 027 V3.5.1 (2011-03) 155 Figure C.1: Interaction between TISPAN IMS-based IPTV architecture and an OSA/Parlay/Parlay X SCS C.2 Interaction based on a 3GPP SCIM This approach is based on a Service Capability Interaction Manager (SCIM), that allows for service association and dynamic service triggering. The use of such an SCIM is described in TS 123 002 [i.8], TS 123 218 [i.9] and 3GPP TR 23.810 [i.10]. C.2.1 Service Capability Interaction Manager (SCIM) The Service Capability Interaction Manager (SCIM)is a function that manages the interaction between IPTV services and other NGN services, by e.g. associating the IPTV services with other NGN services and dynamic triggering the services in the ongoing session based on the information about the relational session or user's status. C.2.2 Architecture Figure C.2 shows a simplified version of the IMS-based IPTV architecture from figure 2 in clause 5.1.1, with interfaces to an SCIM and subsequent external applications. Transport Processing Functions UE IPTV AS ISC ISC Core IMS NASS RACS e2 Gq’ e4 IPTV MF IPTV MCF IPTV MDF Xp Gm Ut y2 Xd Xc ExternalApplications(OSA AS) OSA/ Parlay/Parlay X Gateway (SCS) e.g. CORBA/SOAP OSA/Parla API Transport Processing Functions UE IPTV AS ISC ISC Core IMS NASS RACS e2 Gq’ e4 IPTV MF IPTV MCF IPTV MDF Xp Gm Ut y2 Xd Xc ExternalApplications(OSA AS) OSA/Parlay/Parlay X Gateway (SCS) e.g. CORBA/SOAP OSA/Parlay API ETSI ETSI TS 182 027 V3.5.1 (2011-03) 156 Transport Processing Functions UE IPTV AS ISC ISC Core IMS NASS RACS e2 Gq’ e4 IPTV MF IPTV MCF IPTV MDF Xp Gm Ut y2 Xd Xc External Applications (SIP AS) 3GPP SCIM ISC ISC ISC Figure C.2: Interaction between TISPAN IMS-based IPTV architecture and a 3GPP SCIM ETSI ETSI TS 182 027 V3.5.1 (2011-03) 157 Annex D (informative): Mapping of elementary functions D.1 Mapping of elementary functions to generic capabilities Mapping of elementary functions in table D.1 show which elementary function (listed in clause 5.1.4) are applicable to generic capabilities (described in clause 5.1.3A). Table D.1: Mapping of elementary functions to generic capabilities Elementary function Discover and select content Service control Service interact Media control Deliver media Content protection Content mng. and distribution Service Protection Service interaction 1 network attachment X 2 registration X 3 resource management X 4 charging information X X 5 service discovery X 6 service authorization X X X 7 service selection X X X 8 service initiation X X 9 service control X X X 10 service information handling X X X X 11 service configuration X 12 session initiation X X X 13 session modification X X X 14 session termination X X X 15 multicast based media delivery X 16 unicast based media delivery X 17 content download/upload X 18 control of multicast streaming X X 19 control of unicast streaming X X 20 control of download/ upload 21 content ingestion/receiving X X 22 content recording X 23 content storage X 24 content adaptation X 25 content acquisition X 26 content validation X 27 content distribution X 28 content licencing X 29 key management X X 30 content encryption X 31 user profile/data mng. X X ETSI ETSI TS 182 027 V3.5.1 (2011-03) 158 Elementary function Discover and select content Service control Service interact Media control Deliver media Content protection Content mng. and distribution Service Protection Service interaction 32 accounting/right control X X X 33 status/state (changes) detection/reporting X X X X 34 common notification X X X 35 messaging X X 36 presence X X 37 inter-destination media synchronization X X X D.2 Mapping of elementary functions to functional entities Mapping of elementary functions in table D.2 show which elementary function (listed in clause 5.1.4) are applicable to functional entities (described in clause 5.1.3). Table D.2: Mapping of elementary functions to functional entities Elementary function UE SSF SDF Core IMS SCF UPSF MCF MDF 1 network attachment X X 2 registration X X X 3 resource management X 4 charging information X X X 5 service discovery X 6 service authorization X X X 7 service selection X X 8 service initiation X X 9 service control X X X 10 service information handling X X 11 service configuration X X X 12 session initiation X X X 13 session modification X X X 14 session termination X X 15 multicast based media delivery X 16 unicast based media delivery X X 17 content download/ upload X X 18 control of multicast streaming X X 19 control of unicast streaming X X 20 control of download/ upload X X 21 content ingestion/receiving X X 22 content recording X X 23 content storage X X 24 content adaptation X 25 content acquisition 26 content validation 27 content distribution 28 content licencing 29 key management 30 content encryption X 31 user profile/data mng. X X X ETSI ETSI TS 182 027 V3.5.1 (2011-03) 159 Elementary function UE SSF SDF Core IMS SCF UPSF MCF MDF 32 accounting/right control X X X 33 status/state (changes) detection/reporting X X X X 34 common notification X X 35 messaging X X 36 presence X X 37 inter-destination media synchronization X X D.3 Mapping of elementary functions to IPTV services Mapping of elementary functions in table D.3 show which elementary function (listed in clause 5.1.4) are applicable for described IPTV services (described in TS 181 016 [15]). ETSI ETSI TS 182 027 V3.5.1 (2011-03) 160 Table D.3: Mapping of elementary functions to IPTV services Elementary function BC CoD N-PVR C-PVR BCwTP UGC Push CoD Ad. CRS Notif. Msg Presen ce 1 network attachment x x x x x x x x x x x x 2 registration x x x x x x x x x x x x 3 resource management x x x x x x x 4 charging information x x x x x 5 service discovery x x x 6 service authorization x x x x x x x x x x x x 7 service selection x x x x x x 8 service initiation x x x x x x x x x x x x 9 service control x x x x x x x x x x x x 10 service information handling x x 11 service configuration x x x x x x x x x x x x 12 session initiation x x x x 13 session modification x x x x x x 14 session termination x x x x x x x x x 15 multicast based media delivery x x x x 16 unicast based media delivery x x x x x x 17 content download/ upload x x x 18 control of multicast streaming x x x x x x x 19 control of unicast streaming x x x x x x x 20 control of download/ upload x x x x x x x 21 content ingestion/receiving x x x x x x x 22 content recording x x x 23 content storage x x x x x 24 content adaptation x x x 25 content acquisition x x x x x x 26 content validation x x x x x 27 content distribution x x x x x x 28 content licencing x x x x x 29 key management x x x x x 30 content encryption x x x x x 31 user profile/data mng. x x x 32 accounting/right control x x x x x x x x x 33 status/state (changes) detection/reporting x x x x x x x x x 34 common notification x x x 35 messaging x x 36 presence x x 37 inter-destination media synchronization x x x x x ETSI ETSI TS 182 027 V3.5.1 (2011-03) 161 Annex E (informative): Implementation Examples for Targeted Advertising Annex E describes implemtation examples for the following options: • Advertising performed exclusively by TISPAN IPTV entities. Also referred to an "Internal Advertising" option. • Advertising performed by an external system based on SCTE, [i.12], [i.13] and [i.14]. Also referred to as an "SCTE-130 based External Advertising" option. • Advertising performed by an external system based on OMA. Also referred to as an "OMA MobAd based External Advertising" option. E.1 Internal Advertising Architecture Option This clause specifies the entities involved in the TISPAN-IPTV specific advertising architecture, the procecures and the interfaces involved between the TISPAN entities. E.1.1 Void E.1.2 Advertising architecture Refer to clause 5.1.1. E.1.3 Reference points Refer to clause 6. E.1.4 Procedures for targeted ad insertion (TAI) In internal option, the Ad Server described in clause 8.14 is instantiated to a logical SCF that is in charge of Ad service which is responsible for IPTV service status detection, ad content selection and subsequent ad service control. NOTE: In specialized implementation, the SCF in charge of Ad service (i.e. SCF2) can be co-located with the SCF in charge of BC, CoD or other IPTV services (i.e. SCF1). E.1.4.1 Signalling flows for TAI at UE side When the ad insertion takes place at UE side, the UE is informed by ad insertion indication from SCF in charge of Ad service, and initiates individual session request for Ad content, which implies that multiple sessions may exist on the UE during the ad insertion time. Figure E.1 depicts the typical steps when UE is informed of targeted ad insertion indication. ETSI ETSI TS 182 027 V3.5.1 (2011-03) 162 Figure E.1: signalling flows for UE performing TAI 1) Some IPTV session is established between UE and SCF1 as procedures described in clause 8, e.g. BC session in clause 8.3, CoD session in clause 8.4 etc., and the related IPTV content is delivered to the UE. 2) The SCF2 detects the ongoing IPTV service state (e.g. the current BC program ID, the commercial break of the program, the current CoD content id, the trick-play events, etc.) of specific user and decides to trigger ad insertion. Detection of the IPTV service status is done based on IPTV Service Action Data or using IPTV Presence information. 3) SCF2 selects targeted ad content for the user, which can be inserted to the specific content. The user profile (e.g. shopping habits, user preference) is used to help locating of appropriate ad content targeted to specific user or user group. 4) SCF2 sends UE the notification of ad insertion information, using procedures specified in clause 8.11.1. The ad insertion information includes the selected ad content identifier, insertion time (begin time and/or length), and other information needed for ad insertion. 5) UE initiates the session initiation or modification procedure for ad content acquisition and the selected ad content is delivered to the UE. 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, with SCF2 responsible for the Ad service control and MF responsible for Ad content control and delivery. NOTE: The session modification is only possible when the same SCF handles CoD and Ad sessions. 6) The UE performs the ad insertion, i.e. renders the ad content exclusively or in parallel with the ongoing IPTV content (e.g. in PiP). 7) When the ad insertion times 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. E.1.4.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 SCF2 and performs the ad insertion, i.e. delivery ad content to the UE during the ad insertion time of IPTV content play back. Figure E.2 depicts the typical steps when MF is informed of the ad insertion information. UE Core IMS SCF1 SCF2 MF 1 Session initiation (clause 8) 2 IPTV service status detection 3 Ad content selection 5 Session initiation/modification for ad content (8.3.1/8.3.2/8.4.1/8.4.2) 6 Ad insertion 7 Session Release for ad content (8.3.3/8.4.3) 4 Notification for ad insertion (8.11.1) ETSI ETSI TS 182 027 V3.5.1 (2011-03) 163 Figure E.2 signalling flows for MF performing TAI 1) Some IPTV session is established between UE and SCF1 as procedures described in clause 8, e.g. BC session in clause 8.3, CoD session in clause 8.4 etc., and the related IPTV content is delivered to the UE. 2) The SCF2 detects the ongoing IPTV service status (e.g. the current BC program ID, the commercial break of the program, the current CoD content id, the trick-play events) of specific user and decides to trigger ad insertion. Detection of the IPTV service status is done based on IPTV Service Action Data or using IPTV Presence information. 3) SCF2 selects targeted ad content for the user, which can be inserted to the specific IPTV content. The user profile (e.g. shopping habits, user preference, etc.) is used to help locating of appropriate ad content targeted to specific user. 4) SCF2 sends the ad insertion information to the MF which is responsible for IPTV content delivery and control. The information includes the selected ad content identifier(s) insertion time (begin time and/or length), and other information needed for ad insertion. Playlist information may be used as ad insertion information. NOTE: In the case of co-located entities, step 2 to 4 can be combined in step 1. 5) MF acquires the selected ad content and performs ad insertion, i.e. the selected ad content is delivered separately from the IPTV content or it is inserted as part of ongoing IPTV content. The MF may perform transcoding if the codec of ad content is not supported by the UE. The MF may perform session modification if needed (e.g; the ad content uses different network parameters, the stream is delivered separately, etc.). It is up to SCF preference/policy on how out-of-band insertion indicators work with the in-band insertion indicators, e.g. the in-band insertion indicator has precedence over the out-of-band indicator when both are present. 6) The ad content is provided to the UE during the ad insertion time. UE Core IMS SCF1 SCF2 2 IPTV service status detection 3 Ad content selection MF 1 Session initiation (clause 8) 4 Ad insertion indication 6. Ad content provision 5 Ad insertion ETSI ETSI TS 182 027 V3.5.1 (2011-03) 164 E.2 SCTE-130 Based External Advertising Architecture Option This clause specifies the entities defined by SCTE-130, complete architecture for advertising, the procedures and necessary interfaces between TISPAN and SCTE-130 entities. E.2.1 SCTE-130 Definitions SCTE-130 has defined the following advertising entities in [i.12]: • Ad Decision Service (ADS): The Ad Decision Service determines how advertising content is combined with non-advertising (i.e. entertainment) content assets. The decisions made by an ADS may be straightforward (i.e. specific ad content placed at a specific time in a specific asset) or arbitrarily complex (based on subscriber data, advertising zone, etc.). • Ad Management Service (ADM): The Ad Management Service defines messages in support of ad insertion activities. The primary consumer of these messages is an ADS. The message interfaces exposed by an ADM allow for both preconfigured ad decisions as well as real-time fulfillment models. ADM detection of a placement opportunity is outside the scope of the specification. However, the ADM may be a service consumer of a POIS and/or a CIS in order to obtain such information. • Content Information Service (CIS): The Content Information Service manages metadata describing all the assets (both advertising assets and non-advertising assets) available to the other SCTE 130 logical services. The CIS provides query and notification interfaces to the other logical services. • Placement Opportunity Information Service (POIS): The Placement Opportunity Information Service (POIS) holds, maintains, or retains descriptions of placement opportunities. • Subscriber Information Service (SIS): The Subscriber Information Service manages the per-subscriber information relevant to ad placement decisions. The SIS provides mechanisms surrounding privacy issues. E.2.2 SCTE-130 based Advertising Architecture Figure E.3 shows the interfaces between the SCTE-130 advertising specific entities and the TISPAN IPTV architecture. ETSI ETSI TS 182 027 V3.5.1 (2011-03) 165 Figure E.3: Interaction between TISPAN IMS-based IPTV architecture and SCTE-130 advert entities The SCF entity can be interconnected with the Ad Decision service by the ADx reference point to request for placement decision. POIS is an external entity. SIS may be either covered by SCF, by SCF and UPSF, or by a complete external entity. The MF entity can be interconnected with the Ad Decision service by the ADy reference point to request placement decisions. The UE entity can be interconnected with the Ad Decision Service by the ADz reference point to request placement decisions. A deployment can have SCF,MF and/or the UE contact Ad Decision Service and perform ad insertion depending on the type of placement opportinuties that are detected by that particular entity. The option of where the ADM functions exist is a deployment choice that is not mandated by SCTE-130. Transport Control Functions SSF Core IMS Transport Processing Functions IPTV Media Functions IPTV Service Control Functions (SCF) Xc Xd Gm Gq' Xa ISC e2 UPSF Cx e4 RACS NASS UE IPTV Media Control Functions (MCF) IPTV Media Delivery Functions (MDF) Sh Ut y2 SDF Sh ISC Xp Media Delivery, Distribution & Storage Transport Functions Application and IPTV Service Functions ADx ADy ADS POIS SIS ADM CIS SIS SIS ADM External SCTE-130 Advertising Sub-system ADz ADM ETSI ETSI TS 182 027 V3.5.1 (2011-03) 166 E.2.3 Reference points E.2.3.1 IPTV Service Control Functions (SCF) - SCTE-130 External Ad system (ADx) This reference point is used to exchange advertising related messages between SCF and an SCTE-130 external Advertising sub-system. ADx reference point sends and receives messages from/to the ADS, POIS and SIS entities and the TISPAN IPTV SCF and conforms to appropriate SCTE130 part specification as indicated in [i.12]. The use of ADx between SCF and ADS conforms to SCTE130-3 [i.14]. It can be a subset of SCTE130-3 [i.14] depending on the functionality supported in the SCF and ADS and that is declared during the discovery and registration phases. E.2.3.2 IPTV Media Function (MF) - SCTE-130 External Ad system (ADy) This reference point is used to exchange advertising related messages between MF and an SCTE-130 external Advertising sub-system. ADy reference point should be used to send and receive messages from/to the ADS,POIS and SIS entites and the TISPAN IPTV MF and conforms to appropriate SCTE130 part specification as indicated in [i.12]. The MF entity is interconnected with the Ad Decision service by the ADy reference point to made ad-selection and ad-placement requests for broadcast services. The use of ADy between MF and ADS conforms to SCTE130-3 [i.14]. It can be a subset of SCTE130-3 [i.14] depending on the functionality supported in the ADS and MF and that is declared during the discovery and registration phases. E.2.3.3 IPTV User Equipment (UE) - SCTE-130 External Ad system (ADz) This reference point is used to exchange advertising related messages between UE and an SCTE-130 external Advertising sub-system. ADz reference point should be used to send and receive messages from/to the ADS, POIS entities and the TISPAN UE and conforms to appropriate SCTE130 part specification as indicated in [i.12]. The UE entity is interconnected with the Ad Decision service by the ADz reference point to made ad-selection and ad-placement requests. The use of ADz between UE and ADS conforms to a relevant subset of SCTE130-3 [i.14]. It can be a subset of SCTE130-3 [i.14] depending on the functionality supported in the ADS and UE and that is declared during the discovery and registration phases. E.2.4 Procedures for Targeted Ad Insertion (TAI) Several deployment scenarios are supported by SCTE-130. The call flows below depicts specific example scenarios in which either the MF or the UE is involved in service state detection. Other deployment scenarios can have the SCF only being involved or the MF, UE and /or SCF being involved, where each entity handle different events. NOTE: Due to the stateful nature on the service channel established by the registration messages as described in SCTE 130-3 [i.14], deployments should consider the scalability and load on the ADS while supporting this option. ETSI ETSI TS 182 027 V3.5.1 (2011-03) 167 E.2.4.1 Signalling flows for UE performing TAI E.2.4.1.1 UE detects service state Figure E.4: Signalling flows for UE performing TAI(Case: UE detects service state) 1) In the discovery step, the AD server becomes aware of the existence of the ADM. This can be through manually configuration, or by dynamically subscribing to an entity that can report to the AD server that a UE is online. 2) The external AD server requests a list of offered placement services and capabilities, and receives these from the ADM logical entity in the UE. These actions of the external ad sub-system are not dependent on the existence of a session and can be triggered from a variety of sources, eg. network, application, external ad sub-system. 3) Based on the current advertising campaign, the ad server (ADS) registers with a particular ADM, in this case the UE, with the placement services required. Pre-roll, post roll and interstitial placement opportunity existence is often pre-determined, and interactive applications such as CoD also offer the possibility of spontaneous placement opportunities provided by user events, eg. fast-forward, rewind, etc. 4) An IPTV session is established between UE and SCF as described in clause 8, e.g. CoD session in clause 8.4.1.1, etc. and some IPTV content is delivered to the UE. 5) The service state of on-going IPTV session is detected on the UE (e.g. the current CoD content id, the BC channel Id, the trick-play events, etc.). 10. Placement Status notification/ Response UE SCF MF Ad Server 4. Session initiation (clause 8.3.1.1, 8.4.1.1, …) 8. Ad insertion 5. IPTV service state detection Core IMS 2. List ADM services 3. ADS Registration 6. Placement Opportunity Request/ Placement Decision Response 7. Session initiation/modification for fetching Ad content 9. Session termination/modification for Ad content 1 Discovery ETSI ETSI TS 182 027 V3.5.1 (2011-03) 168 6) The UE initiates a placement request to the Ad server and sends it the list of placement opportunities and other targeting information (service state of on-going session, user information, etc.) that allows the Ad Server to select the appropriate target ads. The Ad server responds with relevant placement/ad insertion information that can include the selected ad content identifier, insertion time (begin time and/or length), and other information needed for ad insertion. 7) 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 clause 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. 8) 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). 9) When the ad insertion time is up, the session for ad content is released, if one has been created, and UE resumes the rendering of the IPTV content. 10) A placement status message exchange takes place between the UE and the external ADS. The purpose of that exchange is to report placement decision fulfilment data and may include other events an ADM considers of interest to an ADS. Placement decision fulfilment data typically contains information regarding how the user viewed the ad content, along with any operations such as pause or fast-forward. ETSI ETSI TS 182 027 V3.5.1 (2011-03) 169 E.2.4.1.2 MF detects service state Figure E.5: Signalling flows for UE performing TAI Note that the discovery procedure is not shown here: 1) The external AD server requests a list of offered placement services and capabilities, and receives these from the ADM logical entity in the MF. These actions of the external ad sub-system are not dependent on the existence of a session and can be triggered from a variety of sources, eg. network, application, external ad sub-system. 2) Based on the current advertising campaign, the ad server (ADS) registers with a particular ADM, in this case the MF, with the placement services required. Pre-roll, post roll and interstitial placement opportunity existence is often pre-determined, and interactive applications such as CoD also offer the possibility of spontaneous placement opportunities provided by user events, eg. fast-forward, rewind, etc. 3) An IPTV session is established between UE and SCF as described in clause 8, e.g. CoD session in clause 8.4.1.1 etc., and some IPTV content is delivered to the UE. 4) The service state of on-going IPTV session is detected on the MF (e.g. the commercial break of the program, the current CoD content id, the trick-play events, etc.). 5) The MF initiates a placement request/response exchange that allows the Ad Server to select the appropriate target ads which can be inserted in the currently streamed content. 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. 10. Placement Status notification 5. Placement Request/Response 2. Registration 1. List ADM services UE Core IMS SCF Ad Server MF 3. Session initiation (clause 8) 4. IPTV service status detection 8. Session initiation/modification for ad content (8.3/8.4) 6a. Notification of ad insertion decision 6b. Notification for ad insertion (8.11.1) 7. AD 9. Session Release for ad content (8.3/8.4) ETSI ETSI TS 182 027 V3.5.1 (2011-03) 170 6) The notification procedures specified in clause 8.11.1 are applied to deliver the ad insertion information to the UE. 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. 7) 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 clause 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. 8) 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). 9) When the ad insertion time is up, the session for ad content is released, if one has been created, and UE resumes the rendering of the IPTV content. 10) A placement status message exchange takes place between the MF and the external ADS. The purpose of that exchange is to report placement decision fulfilment data and may include other events an ADM considers of interest to an ADS. Placement decision fulfilment data typically contains information regarding how the user viewed the ad content, along with any operations such as pause or fast-forward. ETSI ETSI TS 182 027 V3.5.1 (2011-03) 171 E.2.4.2 Signalling flows for MF performing TAI E.2.4.2.1 MF detects service state Figure E.6: Signalling flows for MF performing TAI Note that the discovery procedure is not shown here: 1) The external AD server requests a list of offered placement services and capabilities, and receives these from the ADM logical entity in the MF. These actions of the ad sub-system are not dependent on the existence of a session and can be triggered from a variety of sources, eg. network, application, external ad sub-system. 2) Based on the current advertising campaign, the ADS registers with a particular ADM, in this case the MF, with the placement services required. Pre-roll, post roll and interstitial placement opportunity existence is often pre-determined, and interactive applications such as CoD also offer the possibility of spontaneous placement opportunities provided by user events, eg. fast-forward, rewind, etc. 3) An IPTV session is established between UE and SCF (CoD) as described in clause 8, e.g. CoD session in clause 8.4.1.1, etc., and some IPTV content is delivered to the UE. 4) The service state of on-going IPTV session is detected on the MF (e.g. the commercial break of the program, the current CoD content id, the trick-play events, etc.). 2. Registration 1. List ADM services 5. Placement Request/Response 8. Placement Status notification UE Core IMS SCF Ad Server MF 3. Session initiation (clause 8) 6. Session initiation/modification for ad content (8.4) 7. Session Release for ad content (8.4) 4. IPTV service status detection ETSI ETSI TS 182 027 V3.5.1 (2011-03) 172 5) The MF initiates a placement/request response exchange that allows the Ad Server to select the appropriate target ads which can be inserted in the currently streamed content. 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. Optionally, the ad content may be delivered to the UE via a new session. 7) When the ad insertion time is up, the session for ad content is released, if one has been created, as procedures described in clause 8.4, and UE resumes the rendering of the IPTV content. 8) A placement status message exchange takes place between the MF and the external ADS. The purpose of that exchange is to report placement decision fulfilment data and may include other events an ADM considers of interest to an ADS. Placement decision fulfilment data typically contains information regarding how the user viewed the ad content, along with any operations such as pause or fast-forward. E.3 OMA MobAd Based External Architecture Option This clause specifies the OMA MobAd (Mobile Advertising) entities, complete architecture for advertising, the procedures and necessary interfaces between TISPAN and OMA MobAd entities [i.15] and [i.16]. E.3.1 OMA MobAd Definitions Ad Server: Network resident functions specified by the MobAd Enabler [i.16]. Ad Engine: Device resident functions specified by the MobAd Enabler [i.16]. Ad App: An application running on the Device which interacts with the Ad Engine in order to present Ad(s) to the user. SP App: An Ad enabled network Application that is executing within the Service Provider environment (e.g. MMSC or SP-portal) and interacts with the MobAd Enabler for providing Ads as part of its service (e.g. requesting Ads, providing metrics data). SP App is not one of the MobAd Enabler Entities on the Network, but an external actor which interacts with them. Contextualisation: Tailoring and matching an advertising campaign to User's Context. In practical terms, this can include statically or dynamically associating a given User context (e.g.: "around Marble Arch in London, after 6pm, if using a streaming-capable Device"), to a varying degree of detail, with an advertising campaign. The above can imply using any data known and/or assumed about the User Context, e.g. location, device capabilities, etc. Personalisation: Tailoring and matching an advertising campaign to a set of User(s)' characteristics, such as demographics, tastes, preferences, etc. In practical terms, this can include statically or dynamically allocating a group of users which are to be participants in a given campaign, based on targeting criteria associated with a campaign. It can imply using static and dynamic data known and/or assumed about the User, which may be distributed in e.g.: User Profile, subscriber profiles, preferences and similar. This process can be self-improving throughout the campaign. NOTE: In this annex OMA's usage of the term "interface" is followed for consistency, this may differs from the use in other TISPAN's specification. Figure E.7 shows the OMA MobAd 1.0 architecture [i.16]. ETSI ETSI TS 182 027 V3.5.1 (2011-03) 173 Figure E.7: OMA MobAd Architecture Diagram OMA MobAd 1.0 has defined the following advertising entities in [i.16]: • Ad Server: The Ad Server is a MobAd enabler component resident in the network (outside the device) that performs actions grouped in the following high-level functions: - Ad selection function: select the most appropriate Ad(s)/Ad Campaign(s) primarily using: Contextualisation and Personalisation information, Ad Metadata and applicable MobAd Rules. - Ad delivery function: the delivery of Ad(s)/Ad Campaigns can be done via Pull, Push or Broadcast. - Ad Metrics handling function: collect and process Ad Metrics data. - User/service data management function: manage user's Personalisation and Contextualisation data, MobAd Rules, user groups, Ad Channels, etc. • Ad Engine: The Ad Engine (see clause E.4.1 Definitions) is a MobAd Enabler component resident on the device that performs actions grouped in the following high-level functions: - Ad acquisition and delivery function: the acquiring of Ad(s)/Ad Campaigns can be done via Pull, Push or Broadcast. - Ad selection function: select Ads from the cache. - Ad metrics handling function: augment Ad Metrics data received from Ad Apps and report it to the Ad Server. - User/service/device data handling function: gather and process user's Personalisation and Contextualisation data, monitor and process device static and/or dynamic status (e.g. device resource threshold) and apply MobAd Rules. • SP App (SP Application): The SP App is an external entity that requests and receives Ad(s)/Ad Campaign(s) from Ad Server, and embeds them in content that is provided to the user. SP App records Ad Metrics data related to the Ad(s) and reports Ad Metrics data to the Ad Server. Ad Server Ad Engine Ad App SP App MobAd-3 MobAd-2 MobAd-1 Delv-1 Legend: Mandatory Interface Optional Interface MobAd components Entities external to MobAd MobAd Enabler ETSI ETSI TS 182 027 V3.5.1 (2011-03) 174 • Ad App (Ad Application): The Ad App is an external entity running on the device that requests and receives Ad(s) from Ad Engine, and presents them to the user. Ad App also report Ad Metrics data to the Ad Engine. The interfaces defined in OMA MobAd 1.0 are: • MobAd-1 is an interface exposed by the Ad Engine to the Ad App. The Ad App uses this interface to request and obtain Ads and their associated Ads identifiers from the Ad Engine, as well as to report Ad Metrics data to the Ad Engine, accompanied by the associated Ads identifiers. • MobAd-2 is an interface exposed by the Ad Server to the SP App. The SP App uses this interface to request and obtain Ad(s), reference(s) to Ad(s), associated Ad(s) identifiers and possibly additional information (to be determined in the TS stage), as well as to report Ad Metrics data, accompanied by the associated Ad(s) identifier(s). • MobAd-3 is an interface exposed by the Ad Server to the Ad Engine. The Ad Engine uses this interface to request and obtain Ad(s), reference(s) to Ad(s), their associated Ad(s) identifier(s) and Ad Metadata from the Ad Server, as well as to report Ad Metrics data to the Ad Server, accompanied by the associated Ad(s) identifier(s). • Delv-1 is an optional interface exposed by the Ad Engine. The Ad Engine receives Ad(s) and/or Ad Metadata over this interface from the Ad Server via underlying push and/or broadcast delivery mechanisms. The Ad Server uses this interface to push either Ad(s) or notification that Ad(s) are available for retrieval. The Ad Server may also use this interface to provide service notification to the Ad Engine. E.3.2 OMA MobAd based Advertising Architecture Figure E.8 shows the interfaces between the OMA MobAd advertising specific entities and the TISPAN IPTV architecture. ETSI ETSI TS 182 027 V3.5.1 (2011-03) 175 Figure E.8: Interaction between TISPAN IMS-based IPTV architecture and OMA MobAd entities The SCF/MCF entities can be considered as SP App in MobAd and are interconnected with the Ad Server by the MobAd-2 interface to request for placement decision. The UE is interconnected with the Ad Server by the MobAd-3 interface to request Ad in case of Ad pulling. E.3.3 Reference Points E.3.3.1 IPTV SCF/MCF - MobAd External Ad system (MobAd-2) This interface is used to exchange advertising related messages between SCF/MCF and a MobAd external Advertising sub-system. MobAd-2 interface should be used to exchange messages between the Ad Server and the TISPAN IPTV SCF/MCF. The use of MobAd-2 interface between SCF/MCF and Ad Server conforms to OMA MobAd AD [i.16]. Transport Control Functions SSF Core IMS Transport Processing Functions IPTV Media Functions IPTV Service Control Functions (SCF) Xc Xd Gm Gq' Xa ISC e2 UPSF Cx e4 RACS NASS UE IPTV Media Control Functions (MCF) IPTV Media Delivery Functions (MDF) Sh Ut y2 SDF Sh ISC Xp Media Delivery, Distribution & Storage Transport Functions Application and IPTV Service Functions MobAd-2 External OMA MobAd Advertising Sub-system MobAd-2 MobAd-3 Ad Engine SP App SP App Ad App Ad Server ETSI ETSI TS 182 027 V3.5.1 (2011-03) 176 E.3.3.2 IPTV UE - MobAd External Ad system (MobAd-3) This interface is used to exchange advertising related messages between UE and a MobAd external Advertising sub-system. MobAd-3 interface should be used to for the UE to request Ad from the Ad Server. The use of MobAd-3 interface between UE and Ad Server conforms to OMA MobAd AD [i.16]. E.3.4 Procedures for Targeted Ad Insertion (TAI) In OMA MobAd option, the Ad Server described in clause 8.14 is instantiated to the Ad Server (defined in OMA MobAd AD [i.16]) that is in charge of Ad service which is responsible for ad content selection and subsequent ad service control. The SCF and MF are instantiated to the SP App (defined in OMA MobAd AD [i.16]) which is a Service Provider Application system for ad request and ad response. E.3.4.1 Signalling Flows for TAI at UE side When the ad insertion takes place at UE side, the UE is informed by ad insertion indication from SCF in charge of Ad service, and initiates individual session request for Ad content, which implies that multiple sessions may exist on the UE during the ad insertion time. Alternatively, the UE can request ad from Ad Server directly using the MobAd-3 interface, which is specified in OMA MobAd AD [i.16]. UE can have the ad content stored locally for the ad insertion at the UE side. And also, the Ad Server can send appropriate ads to the MCF or MF beforehand to facilitate the ad request from UE. These can be done by offline means and out of scope of the present document. Figure E.9 depicts the typical steps when UE is informed of targeted ad insertion indication. Figure E.9: signalling flows for UE performing TAI 1) Some IPTV session is established between UE and SCF as procedures described in clause 8, e.g. BC session in clause 8.3, CoD session in clause 8.4 etc., and some IPTV content is delivered to the UE. UE Core IMS SCF Ad Server MF 1 Session initiation (clause 8) 2 IPTV service status detection 3b Ad content selection 5 Session initiation/modification for ad content (8.3.1/8.3.2/8.4.1/8.4.2) 7 Session Release for ad content (8.3.3/8.4.3) 4 Notification for ad insertion (8.11.1) 3a OMA MobAd Ad Request 3c OMA MobAd Ad Response 3d Send information to MF 6 Ad insertion ETSI ETSI TS 182 027 V3.5.1 (2011-03) 177 2) The SCF detects the ongoing IPTV service status (e.g. the current BC program ID, the commercial break of the program, the current CoD content id, the trick-play events, etc.) of specific user and decides to trigger ad insertion. Detection of the IPTV service status is done based on IPTV Service Action Data or using IPTV Presence information. 3) The SCF sends a OMA MobAd Ad Request message to the target Ad Server for the user. The Ad Server acquires the contextualisation and personalisation data relavant to the user and selects the appropriate target ads. The ads on the Ad Server can be stored locally or come from external entities. The selected ads can be inserted in the currently streamed content. The Ad Server sends the OMA MobAd Ad Response message including the selected target ads information to the SCF. In step 3d, the SCF sends the target ad information and the ad insertion indication back to a selected MF. 4) SCF sends UE the notification of ad insertion indication, using procedures specified in clause 8.11.1. The ad insertion indication includes the selected ad content identifier, the user id, insertion time (begin time and/or length), and other information needed for ad insertion. 5) UE initiates the session initiation or modification procedure for ad content acquisition and the selected ad content is delivered to the UE. 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, with Ad Server responsible for the Ad service control and MF responsible for Ad content control and delivery. 6) The UE performs the ad insertion, i.e. renders the ad content exclusively or in parallel with the ongoing IPTV content (e.g. in PiP). 7) When the ad insertion times 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. E.3.4.2 Signalling flows for TAI at MF side When the ad insertion takes place at MF, the MF is informed of the ad insertion indication from the SCF and performs the ad insertion, i.e. delivery ad content to the UE during the ad insertion time of IPTV content play back. Figure E.10 depicts the typical steps when MF is informed of the ad insertion indication. Figure E.10: signalling flows for MF performing TAI 1) Some IPTV session is established between UE and SCF1 as procedures described in clause 8, e.g. BC session in clause 8.3, CoD session in clause 8.4 etc., and some IPTV content is delivered to the UE. UE Core IMS SCF 2 IPTV service status detection MF 1 Session initiation (clause 8) 5 Ad content provision 4 Ad insertion Ad Server 3a OMA MobAd Ad Request 3c OMA MobAd Ad Response 7. Ad content provision ETSI ETSI TS 182 027 V3.5.1 (2011-03) 178 2) The SCF detects the ongoing IPTV service status (e.g. the current BC program ID, the commercial break of the program, the current CoD content id, the trick-play events) of specific user and decides to trigger ad insertion. Detection of the IPTV service status is done based on IPTV Service Action Data or using IPTV Presence information. 3) The SCF sends an OMA MobAd Ad rRequest message to the target Ad Server for the user. The Ad Server acquires the contextualisation and personalisation data relavant to the user and selects the appropriate target ads. The ads on the Ad Server can be stored locally or come from external entities. The selected ads can be inserted in the currently streamed content. The Ad Server sends the OMA MobAd Ad Response message including the selected target ad information to the SCF. In step 3d, the SCF sends the target ads informaion and the ad insertion indication back to a selected MF. 4) MF acquires and stores the selected ad content, and performs ad insertion, i.e. the selected ad content is delivered separately from the IPTV content or it is inserted as part of ongoing IPTV content. 5) The ad content is provided to the UE during the ad insertion time. ETSI ETSI TS 182 027 V3.5.1 (2011-03) 179 Annex F (informative): Mapping between TISPAN entities and external architectures Clause F.1 describes a mapping of the functional entities defined by others Advertising standards with the TISPAN IPTV functional entities. F.1 Mapping between TISPAN entities and SCTE-130 entities This clause describes a mapping of the functional entities defined by SCTE with the TISPAN IPTV functional entities. Placement Opportunity Information Service (POIS) and Ad Decision Service (ADS) are considered out of scope of TISPAN architecture because placement opportunities providing and Advert placement decision are not defined as TISPAN entities tasks. Link between ADS and ADM is considered as a reference point in scope of TISPAN. Other modules can be mapped with current TISPAN entities as they cover TISPAN entities tasks. In table F.1, is presented entities defined in the SCTE-130 [i.12] to [i.14], their roles and concerned TISPAN entities. ETSI ETSI TS 182 027 V3.5.1 (2011-03) 180 Table F.1 SCTE-130 entity name Role TISPAN Entity concerned TISPAN entity task covered POIS Provides placement opportunities Out of scope (external entity) - SIS Manage subscriber information relevant for Ad SCF/UPSF/External entity SCF task from clause 5.1.5.2: Select appropriate ad content for specific user or user group, based on user profile (e.g. user preference, shopping habits, location information, etc.) and IPTV service status (e.g. current BC program ID, commercial break in BC service or pause during CoD content playback). CIS Manage assets metadata SCF SCF task from clause 5.1.5.2: Select appropriate ad content for specific user or user group, based on user profile (e.g. user preference, shopping habits, location information, etc.) and IPTV service status (e.g. current BC program ID, commercial break in BC service or pause during CoD content playback). ADM Provides placement opportunities based on POIS and CIS information Defines messages for Ad insertion Activities SCF (for TAI) and MCF (for Broadcast) SCF tasks from clause 5.1.5.2: Select appropriate ad content for specific user or user group, based on user profile (e.g. user preference, shopping habits, location information, etc.) and IPTV service status (e.g. current BC program ID, commercial break in BC service or pause during CoD content playback). Send ad insertion indication to MF. MCF tasks from clause 5.1.5.3: Handle ad insertion control of MDF, i.e. control the fetching of the ad content and synchronization between ad content and IPTV content, including accounting for delay or drift in broadcast TV schedules. ADS Decide ad placement relative to content based on ADM placement opportunities Out of scope (external entity) - ETSI ETSI TS 182 027 V3.5.1 (2011-03) 181 F.2 Mapping between TISPAN Entities and OMA MobAd Entities TISPAN entities can use the interfaces exposed by Ad Server and Ad Engine for advertising purposes. Modules can be mapped with current TISPAN entities as they cover TISPAN entities tasks. Table F.2 shows the presented entities defined in the OMA MobAd, their roles and concerned TISPAN entities. Table F.2 OMA MobAd entity name Role TISPAN Entity concerned TISPAN entity task covered Ad Server Ad selection, Ad delivery, Ad Metrics data handling, data management Out of scope Use the interface exposed by Ad Server Ad Engine Ad selection, Ad acquisition and delivery, Ad Metrics data handling, data managment UE UE task from 8.14: When the ad insertion takes place at UE side, the UE is informed by ad insertion indication from SCF in charge of Ad service, and initiates individual session request for Ad content, which implies that multiple sessions exist on the UE during the ad insertion time. SP App Request and receive Ad, insert Ads to the content, report Ad Metrics data SCF/MF SCF task from clause 5.1.5.2: Select appropriate ad content for specific user or user group, based on user profile (e.g. user preference, shopping habits, location information, etc.) and IPTV service status (e.g. current BC program ID, commercial break in BC service or pause during CoD content playback). MDF task from clause 5.1.5.3: Recognize appropriate in-band /out-of-band Ad insertion indicators (eg-cue messages as defined in ITU-T Recommendation J.181 [i.18]), when present. These Ad insertion indicators define positions within the IPTV content where advertisement content can be inserted /replaced. This task may be done by coordination with an external advertising sub-system. Ad App Request and receive Ad, report Ad Metrics data UE UE task from clause 8.14: When the ad insertion takes place at UE side, the UE is informed by ad insertion indication from SCF in charge of Ad service, and initiates individual session request for Ad content, which implies that multiple sessions exist on the UE during the ad insertion time. ETSI ETSI TS 182 027 V3.5.1 (2011-03) 182 Annex G (informative): Ad placement options This annex presents examples for implemented of Ad placement by existing mechanism from other SDOs. G.1 IPTV Ad placement: SCTE-130 option In SCTE-130 [i.14], four types of ad insertion opportunities exists: • Pre-roll (a placement opportunity preceding an entertainment asset). • Post-roll (a placement opportunity following the play out of an entertainment asset). • Interstitial (a placement opportunity occurring during the play out of an entertainment asset). • Pause (placement opportunity as a result of a subscriber pressing the pause button). They can be separated in two options: predetermined placement opportunities (Pre/Post roll and Interstitial) and unexpected placement opportunities (Pause). The predetermined option should be used for the following types of stored contents: BC, COD, N-PVR and UGC contents. The unexpected option could be used for all sorts of stored contents: BC with trick mode, COD, N-PVR, UGC, timeshift. ETSI ETSI TS 182 027 V3.5.1 (2011-03) 183 Annex H (informative): Interconnection Models to support of Mobility Capabilities TISPAN IMS based IPTV can recognize at least the following basic scenarios for roaming and interconnection to home network (not need support all of them): a) pure data access remotely to IPTV SP/content provider; b) IMS interconnect to home IPTV provider (described in clause H.1); c) visited - home network roaming between IPTV providers (served only from home network); d) visited - home network roaming between IPTV providers (served from home and/or visited network). Scenario A: IMS based IPTV user accessing via remote data access to home IPTV SP Because the UE accessing home IPTV SP from remote network without IMS, the user uses some remote data IP connection (e.g. VPN or secure remote access) to connect UE to his home network. Over this connection can be transferred all media and signaling to the subscriber directly from his Home Network. Because such a connection should going over any IP network (also best effort) also without resource reservation mechanisms, no QoS can be really ensured. NOTE 1: This scenario is out of scope of the current release. Scenario B: IMS based IPTV roaming with visiting IMS provider without IMS based IPTV solution This scenario is the simplest one with using core IMS. User will use IPTV services provided from IPTV functional elements from his Home Network. The IMS elements of visited network perform just IMS roaming via network attachment and registration in visited network and forward all other request to home network and its IMS IPTV SP (e.g. registration, service discovery/selection, service initiation/modification/termination). Service selection information and media are delivered from Home network over interconnection. The quality of the IPTV service for the end customer should be same as in home network (when interconnection and visited network assure enough resources and QoS), but no reuse of local media delivery resources for the provider is possible (because in visited network have no IMS based IPTV platform). NOTE 2: This scenario is described in clause H.1. Scenario C: IMS based IPTV roaming with visiting IPTV Service Provider with TISPAN IMS-IPTV solution (only home served) Additionally to the previous scenario the following one expects the IMS based IPTV platform is available in Visited Network, however all content and services are delivered only from Home Network. This solution expect that delivery of the content, metadata and service discovery, selection and service initiation, modification and termination will be done from home network. Also it could be required from Home Network IMS based IPTV solution to provide transcoding and content adaptation to adapt media to parameters required for entering the Visited Network (or this could be done in edge of visited network). Scenario D: IMS based IPTV roaming with visiting IPTV Service Provider with IMS-IPTV solution (home and/or partially visited IPTV platform served) If there is an IPTV solution in Visited Network, possibly having similar content for CoD, BC, PVR service, it is useful and more efficient to use this local resources in visited network as deliver all content over interconnection. The content which is available in Visited Network is not needed to be transferred over an interconnection network and allocate interconnection bandwidth/resources. For this purpose both providers should agree on the same identification of content, sharing service discovery and selection information, content security, billing clearing, and for sure about all parameters required for roaming agreements (e.g. QoS, Service Level Agreement). Other IPTV services or content not available in offer of visited IMS IPTV SP are provided as in previous scenario by home network and by user home IPTV service provider. ETSI ETSI TS 182 027 V3.5.1 (2011-03) 184 H.1 Interconnection model using IMS roaming to home IMS IPTV Figure H.1 illustrates the model of interconnection with the Visited Network within Core IMS involved. UE can request IPTV services in the Home Network by connecting to the Visited Network. Core IMS in the Visited Network can request resources from the RACS in the Visited Network through the interface Gq'. Core IMS in the Home Network can request resources from the RACS in the Home Network through the interface Gq'. UE can attach to the Visited Network through the interface e1 so that the NASS in the Visited Network can assign IP address for the UE and discovery the address of P-CSCF in the Visited Network. Core IMS in the Visited Network can transfer the IPTV service request from the UE through the interface Ic to the Core IMS in the Home Network through the connection of their own IBCF(Intermediate Breakout Control Function). UE can connect the SSF to select IPTV services through the interface Xa which is already defined. UE can connect to the IPTV SCF to configure parameters through the interface Ut which is already defined. Core IMS in both network connect to their own UPSF to get user profiles through their own interface Cx. Figure H.1 H.2 Signalling flows The clauses below explain the signalling flows of UE start-up procedures and CoD procedures when the UE is located in the Visited Network. In Broadcast procedures, N-PVR and other services, they are similar as CoD procedures. NOTE: Following procedure are indicative to show one possible way how should IMS roaming be handle between home and visited network. ETSI ETSI TS 182 027 V3.5.1 (2011-03) 185 H.2.1 UE start-up procedures Figure H.2 1) Network Attachment In this step the UE attaches to the network. The procedures for network attachment are defined in ES 282 004 [3]. This step includes IP configuration, P-CSCF address discovery of Visited Network, etc. 2) IMS Registration in Visited Network In this step, the UE performs regular IMS Registration as defined in TS 182 006 [2]. 3) P-CSCF within Core IMS in Visited Network submits the registration request to the I-CSCF within the Core IMS in the Home Network. In this step, the UE performs regular IMS Registration as defined in TS 123 002 [i.8]. 4) Core IMS in the Visited Network return parameters (e.g. P-CSCF address of Home Network) to the UE. 5) The step is the same as step 3 to 4 in figure 9 of clause 8.2. ETSI ETSI TS 182 027 V3.5.1 (2011-03) 186 H.2.2 CoD procedures Figure H.3 1) The UE initiates a dialogue to the CoD service and submit the request to the Core IMS in the Visited Network, similar to steps 3 to 5 in clause 8.4.1.1.1. 2) Core IMS in the Visited Network forwards the request to the Core IMS in the Home Network. 3) The session initiation request is routed by the Core IMS in the Home Network up to the SCF. 4) 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. 5) Signalling procedures for establishment of a content control channel and optionally content delivery channels take place between the UE and the MF (see similar clause 8.4.1.2.1). 6 to 8) The steps are the same as step 7 to 10 not including step 8 of clause 8.4.1.1.1. 9) The Core IMS in the Home Network forwards this confirmation to the Core IMS in the Visited Network. 10) The P-CSCF within the Core IMS in the Visited Network interacts with the RACS in the Visited Network to commit all resources previously reserved. This includes opening pinholes for exchanging content control messages and/or content delivery. 11) The P-CSCF in the Visited Network forwards the dialogue confirmation to the UE. ETSI ETSI TS 182 027 V3.5.1 (2011-03) 187 After this point, UE may use the content control channel to request content to be streamed and the actual content will then be delivered to the UE. The content control channel will also be used to carry UE requests for controlling the streams, e.g. "pause", "fast forward", etc. NOTE: Resources reserve/commit between Core IMS and RACS in the home network is optional when selected MF in the visited network servers the UE. ETSI ETSI TS 182 027 V3.5.1 (2011-03) 188 Annex I (informative): IPTV Identifiers This annex provides an overview of generic IPTV identifiers used in the present document. I.1 IPTV content identifiers Table I.1 provides an overview over IPTV content identifiers. Table I.1: IPTV content identifiers IPTV Service IPTV content identifier Clause(s) Identifies … BC BCServiceId 7.4.1 … a BC channel BC ProgrammeId 7.4.1 … a BC programme CoD CoDId 7.4.1 … CoD PVR PVRContentId 7.4.1 …PVR content UGC UGC content id 8.9.2 … UGC Ad ad content id 8.14.1 … an advertisement clip PCh PCh id 8.10 … a personalized channel NOTE: In case of BC, the IPTV content identifier contains the BCServiceId, the ProgrammeId or both. Table I.2: Use of IPTV content identifiers by other IPTV services Other IPTV service/feature Clause(s) IPTV content identifier is used to identify content that is … BC N/A (only BC content) CoD N/A (only CoD content) PVR 7.1 … used by the UE to activate a PVR session related to the PVR content Time shift N/A … time-shifted Preview 8.7 … previewed Parental controlled - … parentally controlled UGC N/A (only UGC content) PCh 8.10 … concatenated into a personalised channel CR 8.13 … recommended by the CR service Ad 8.14.1.1 … subjected to ad insertion Sync 8.15 … synchronised Trick-play 8.16 8.20 … controlled through network-controlled trick play Push CoD N/A (only CoD content) Content upload/download 8.18 8.19 … up/downloaded SSC 8.21 … controlled together with other users PSC 8.22 … used to build a personalised service composition Content marker 7.5.2.5 8.23 … marked Remote UE 8.25 … remotely intiated and controlled Presence 9.1 … being watched, as published to other users and/or IPTV services ETSI ETSI TS 182 027 V3.5.1 (2011-03) 189 I.2 IPTV service type identifier Table I.3 provides an overview over IPTV service types that are identified by an IPTV service type identifier. Table I.3: IPTV service type identifiers IPTV Service Type Broadcast (BC) Broadcast with trick play Content on Demand (CoD) Personal Video Recorder (PVR) Network Personal Video Recorder (N-PVR) Consumer Personal Video Recorder (C-PVR) Time shift Preview Parental controlled (PC) User Generated Content (UGC) Personalised Channel (PCh) Content Recommendation (CR) Targeted Advertisement Insertion (TAI) Push Content on Demand Content upload/download Shared Service Control (SSC) Personalised Service Composition (PSC) Content marker (CM) Remote UE ETSI ETSI TS 182 027 V3.5.1 (2011-03) 190 Annex J (informative): Bibliography ETSI TS 126 237: "Universal Mobile Telecommunications System (UMTS); LTE; IP Multimedia Subsystem (IMS) based Packet Switch Streaming (PSS) and Multimedia Broadcast/Multicast Service (MBMS) User Service; Protocols (3GPP TS 26.237 Release 8)". ETSI ETSI TS 182 027 V3.5.1 (2011-03) 191 Annex K (informative): Change history Change history Date WG Doc. CR Rev CAT Title / Comment Current Version New Version 30-05-08 17bTD256r1 001 A Fixing Figure 34 in TS 182 027 for Release 3. Corresponds to 17bTD260 3.0.0 3.0.1 30-05-08 17bTD255r2 002 1 D 16 Editor's notes on Release 3, Guidance to contributors 3.0.0 3.0.1 06-06-08 17bTD195r3 003 1 B Notification procedures 3.0.0 3.0.1 02-07-08 18WTD074r2 004 F Corrections in step numbering 3.0.1 3.0.2 02-07-08 18WTD052r4 005 1 B WI2070 User generated content in IPTV architecture 3.0.1 3.0.2 02-07-08 18WTD070r3 006 B Modification of content distribution related description in clause 12 3.0.1 3.0.2 02-07-08 18WTD086r2 007 D Proposal for ToC of TS182 027 on value added services 3.0.1 3.0.2 02-07-08 18WTD138r3 008 B Service Control function for IPTV content recommendation service 3.0.1 3.0.2 02-07-08 18WTD139r2 009 B Include procedures for IPTV recommendation service 3.0.1 3.0.2 02-07-08 18WTD140r1 010 D Clarification of notification service 3.0.1 3.0.2 02-07-08 18WTD181r1 011 B Network-initiated CoD session 3.0.1 3.0.2 02-07-08 18WTD071r6 012 B Support Push CoD service in IMS-based IPTV Architecture 3.0.1 3.0.2 02-07-08 18WTD082r4 013 C Reselection of MDF 3.0.1 3.0.2 02-07-08 18WTD083r7 014 C Notification using media path 3.0.1 3.0.2 02-07-08 18WTD085r2 015 B Advertising functions in IPTV architecture 3.0.1 3.0.2 02-07-08 18WTD084r3 016 B User Profile for Parent Control 3.0.1 3.0.2 01-10-08 18bTD288r1 017 D WI2070 ToC Drafting: Changes to clauses 5 and 8 3.0.2 3.0.3 01-10-08 18bTD194r1 018 B Session Transfer procedure 3.0.2 3.0.3 01-10-08 18bTD257r1 019 A WI2070, adding references to stage 1 3.0.2 3.0.3 01-10-08 18bTD143r2 020 B Sharing Bookmarks Between Multiple IPTV Users 3.0.2 3.0.3 01-10-08 18bTD170r3 021 D Generic SCF and MF 3.0.2 3.0.3 01-10-08 18bTD169r2 022 D "CoD-based" UGC procedures 3.0.2 3.0.3 01-10-08 18bTD085r2 023 B UGC Functions in IPTV Architecture 3.0.2 3.0.3 01-10-08 18bTD080r3 024 B IPTV Advertising Service Procedures 3.0.2 3.0.3 01-10-08 18bTD076r2 025 B Procedure of CoD content preview 3.0.2 3.0.3 01-10-08 18bTD079r3 026 1 B Personalized Channel Functions 3.0.2 3.0.3 01-10-08 18bTD128r3 027 B Architectures for NGN Service Blending 3.0.2 3.0.3 01-10-08 18bTD131r3 028 B WI2070 Synchronization Architecture 3.0.2 3.0.3 01-10-08 18bTD196r2 029 A Correction of inconsistency of IPTV presence timer definition between stage 2 and 3 3.0.2 3.0.3 01-10-08 18bTD091r5 030 C Clarification of Push CoD service 3.0.2 3.0.3 01-10-08 18bTD224r4 031 B WI2070 messaging 3.0.2 3.0.3 01-10-08 18bTD130r3 032 B Network-controlled Trick Play 3.0.2 3.0.3 01-10-08 18bTD081r4 033 B Deliver Messages Associated with a BC Service Using Media Path 3.0.2 3.0.3 01-10-08 18bTD094r6 034 B Clarification of Network initiated service 3.0.2 3.0.3 01-10-08 18bTD095r4 035 B Procedures of Network initiated BC service 3.0.2 3.0.3 06-11-08 19WTD047r1 036 D Typo Correction Fig C1 3.0.2 3.0.4 06-11-08 19WTD192r2 037 B IPTV Elementary functions 3.0.2 3.0.4 06-11-08 19WTD179r1 038 B Addition of playlist generation task for SCF 3.0.2 3.0.4 06-11-08 19WTD093r2 039 B Functions and Procedures for CRS 3.0.2 3.0.4 06-11-08 19WTD175r2 040 F Cleaning up references [2] and [12] 3.0.2 3.0.4 06-11-08 19WTD140r2 041 F Advertising Procedures- Name Update 3.0.2 3.0.4 06-11-08 19WTD143r3 042 B Advertising Procedures- MCF Role 3.0.2 3.0.4 12-11-08 19WTD091r2 043 B Capability of SCF on event detection 3.0.2 3.0.4 12-11-08 19WTD092r3 044 B PVR procedures 3.0.2 3.0.4 12-11-08 19WTD094r3 045 B Procedures for PPV Service 3.0.2 3.0.4 12-11-08 19WTD050r2 046 B User Generated Content Session Coordination 3.0.2 3.0.4 12-11-08 19WTD051r2 047 B User Generated Content Procedures Coordination note 3.0.2 3.0.4 12-11-08 19WTD095r2 048 B Uploading of UGC Content Description 3.0.2 3.0.4 12-11-08 19WTD144r3 049 C Traditional Broadcast Advertising Procedures 3.0.2 3.0.4 12-11-08 19WTD111r2 050 F COD offset use 3.0.2 3.0.4 12-11-08 19WTD177r3 051 B IPTV Bookmark data model 3.0.2 3.0.4 12-11-08 19WTD142r7 052 C Advertising Procedures- MDF Role 3.0.2 3.0.4 ETSI ETSI TS 182 027 V3.5.1 (2011-03) 192 Change history Date WG Doc. CR Rev CAT Title / Comment Current Version New Version 12-11-08 19WTD149r1 053 F Alignment of terminology for the IMS-based IPTV procedures 3.0.2 3.0.4 14-11-08 CRs 17 to 53 TB approved at TISPAN#19 and clean-up by ETSI Secretariat 3.0.4 3.1.0 05-12-08 19bTD169r2 054 D WI2070 editorial fixes 3.1.0 3.1.2 05-12-08 19bTD164r1 055 A Deleting informative reference to IPTV stage 1 3.1.0 3.1.2 05-12-08 19bTD054r1 056 F Editorial change 3.1.0 3.1.2 05-12-08 19bTD117r1 057 B Personalized Stream Composition 3.1.0 3.1.2 05-12-08 19bTD184r2 058 C Targeted ad insertion clarification 3.1.0 3.1.2 05-12-08 19bTD125r4 059 B IPTV Service Access History Data Model 3.1.0 3.1.2 05-12-08 19bTD112r2 060 C Clarification of notification procedures 3.1.0 3.1.2 05-12-08 19bTD131r1 061 B Elementary functions mapping 3.1.0 3.1.2 05-12-08 19bTD180r1 062 A Multiple services packages in BC session initiation 3.1.0 3.1.2 05-12-08 19bTD185r1 063 F Clarification on User Profile configuration 3.1.0 3.1.2 05-12-08 19bTD086r3 064 B Modification of targeted advertising flows for CoD services 3.1.0 3.1.2 05-12-08 19bTD153r2 065 F Signalling flow at MF side 3.1.0 3.1.2 05-12-08 19bTD113r2 066 B Event Handling-Involving SCF 3.1.0 3.1.2 05-12-08 19bTD114r2 067 B IPTV Status Detection 3.1.0 3.1.2 05-12-08 19bTD059r3 068 B PCh Specific Information 3.1.0 3.1.2 05-12-08 19bTD087r3 069 B Addition of Signalling flows of playlist generation by SCF and playlist acquisition by MF from SCF 3.1.0 3.1.2 05-12-08 19bTD128r5 070 B Push CoD service procedures 3.1.0 3.1.2 05-12-08 19bTD182r1 071 F Obsolete use of BC MCF/SCF 3.1.0 3.1.2 05-12-08 19bTD218r2 072 D Editor notes for open issues 3.1.0 3.1.2 05-12-08 19bTD055r3 073 B Add Signalling Flows for CoD service action data update 3.1.0 3.1.2 05-12-08 19bTD061r3 074 B Generic Content Upload/Download Procedures 3.1.0 3.1.2 05-12-08 19bTD056r4 075 B Procedures for Restricted Trick Play 3.1.0 3.1.2 05-12-08 19bTD152r5 076 B Advert alignment SCTE 3.1.0 3.1.2 05-12-08 19bTD154r3 077 F Content recommendation attributes in user profile 3.1.0 3.1.2 05-12-08 19bTD130r4 078 B IPTV roaming in IMS-based IPTV Architecture 3.1.0 3.1.2 05-12-08 19bTD183r4 079 B Shared content procedures 3.1.0 3.1.2 05-12-08 19bTD212r5 080 C PPV- Adding required step to call flows in clause 8.3.8 3.1.0 3.1.2 05-12-08 19bTD181r2 081 C Alternative solution for PPV 3.1.0 3.1.2 05-12-08 19bTD193r4 082 D Clarification of CoD Session Transfer 3.1.0 3.1.2 05-12-08 19bTD129r7 083 C Modification of UGC procedures 3.1.0 3.1.2 05-12-08 19bTD060r3 084 B Personalized Channel Procedures 3.1.0 3.1.2 30-01-09 19tTD197r1 085 D Editor's note on relationship between Xc and BC tasks 3.1.2 3.1.3 30-01-09 19tTD078r3 086 C Clarification of UGC Creation Procedure 3.1.2 3.1.3 30-01-09 19tTD079r2 087 C Clarification of UGC Watching Procedure 3.1.2 3.1.3 30-01-09 19tTD080r4 088 B Procedure for Personal Service Composition 3.1.2 3.1.3 30-01-09 19tTD081r2 089 C Synchronization of Shared Content 3.1.2 3.1.3 30-01-09 19tTD082r2 090 B Synchronization Procedures 3.1.2 3.1.3 30-01-09 19tTD147r1 091 C Playlist parameters 3.1.2 3.1.3 30-01-09 19tTD202r2 092 D Cleanup of IPTV Bookmark Terminology 3.1.2 3.1.3 30-01-09 19tTD149r3 093 B Shared Service Control procedure 3.1.2 3.1.3 30-01-09 19tTD183r2 094 F Modification on procedures for shared content 3.1.2 3.1.3 30-01-09 19tTD101r1 095 F Modifications to Flows and Assumptions in Session Transfer 3.1.2 3.1.3 30-01-09 19tTD107r2 096 B Signalling Flows for IPTV Favourites procedures 3.1.2 3.1.3 30-01-09 19tTD185r3 097 B Reuse Media Channel for CoD Services 3.1.2 3.1.3 03-03-09 20WTD224r1 099 F Correcting figure 7 3.1.3 3.1.4 03-03-09 20WTD093r1 100 C Alignment of UGC watching with CoD procedures 3.1.3 3.1.4 03-03-09 20WTD223r1 102 D IPTV Content Marker cleanup 3.1.3 3.1.4 03-03-09 20WTD197r2 103 B Metadata exchange with SSF 3.1.3 3.1.4 03-03-09 20WTD072r1 104 B Support for Bypassing BGF in IPTV Flows 3.1.3 3.1.4 03-03-09 20WTD087r3 105 C PVR Content Update Procedure 3.1.3 3.1.4 03-03-09 20WTD125r2 106 F Resolve Editor's Notes for PVR service 3.1.3 3.1.4 03-03-09 20WTD076r2 107 B Unclear specification for notification on the media stream in conjunction with BC service 3.1.3 3.1.4 03-03-09 20WTD092r2 108 C IPTV service status 3.1.3 3.1.4 03-03-09 20WTD126r2 109 D Amendments on Advertising Related Clauses 3.1.3 3.1.4 03-03-09 20WTD122r4 110 B Preview Procedures for BC Service 3.1.3 3.1.4 ETSI ETSI TS 182 027 V3.5.1 (2011-03) 193 Change history Date WG Doc. CR Rev CAT Title / Comment Current Version New Version 03-03-09 20WTD288r3 111 B Add Procedures for Service Initiation by Remote UE 3.1.3 3.1.4 03-03-09 20WTD123r4 112 B Add Procedure for UGC Creation Session Initiated by Remote UE 3.1.3 3.1.4 03-03-09 20WTD128r3 113 B Delete Editor's Note: UGC Creation Procedures 3.1.3 3.1.4 03-03-09 20WTD074r2 114 B Incomplete specification on Personalized Channel service 3.1.3 3.1.4 03-03-09 20WTD127r6 115 B Content related Content Marker Retrieving Procedure 3.1.3 3.1.4 03-03-09 20WTD073r3 116 B Unclear Messaging Procedures 3.1.3 3.1.4 03-03-09 20WTD130r3 117 B PPV User Profile Definition 3.1.3 3.1.4 03-03-09 20WTD086r3 118 C SSC procedures clarifications 3.1.3 3.1.4 10-03-09 CRs 54 to 118 (except 98) TB approved at TISPAN#20 3.1.4 3.2.0 25-03-09 20bTD207r1 119 D Fixing figure 8B 3.2.0 3.2.1 25-03-09 20bTD120r1 120 B Clarification on UGC Creation Session 3.2.0 3.2.1 25-03-09 20bTD119r1 121 F Delete Push CoD procedures in Annex B 3.2.0 3.2.1 25-03-09 20bTD230r2 122 B Procedures for Shared Service Control 3.2.0 3.2.1 25-03-09 20bTD280r1 123 B IPTV interconnection types 3.2.0 3.2.1 25-03-09 20bTD065r2 124 F Correction on PVR Off-line Capture Request Procedures 3.2.0 3.2.1 25-03-09 20bTD067r2 125 B C-PVR User Profile Definition 3.2.0 3.2.1 25-03-09 20bTD244r3 126 B IPTV_SCF-initiated UGC Watching 3.2.0 3.2.1 25-03-09 20bTD061r4 127 B Personalized Channel Service Procedure 3.2.0 3.2.1 25-03-09 20bTD062r2 128 B Clarification on Notification through Media Path 3.2.0 3.2.1 25-03-09 20bTD241r2 129 B Synchronisation with SC in Transport 3.2.0 3.2.1 25-03-09 20bTD246r2 130 B Synchronization and Transcoding 3.2.0 3.2.1 25-03-09 20bTD323r1 131 B Note on Synchronisation 3.2.0 3.2.1 25-03-09 20bTD334r1 132 B Proposal for revised Annex E 3.2.0 3.2.1 25-03-09 20bTD273r3 133 B OMA MobAd Advertising Architecture Option 3.2.0 3.2.1 25-03-09 20bTD066r4 134 B C-PVR SAD data model definition 3.2.0 3.2.1 25-03-09 20bTD063r4 135 B Publication of UGC Content Description 3.2.0 3.2.1 25-03-09 20bTD069r2 136 B Push CoD procedure resues SCF initiated unicast content download procedure 3.2.0 3.2.1 25-03-09 20bTD064r3 137 B Clarification on UE-initiated Unicast Content Upload/Download 3.2.0 3.2.1 25-03-09 20bTD068r3 138 D Message Transfer on Media Path 3.2.0 3.2.1 25-03-09 20bTD239r4 139 B IPTV Service Identifier 3.2.0 3.2.1 25-03-09 20bTD026r8 140 B Alignment of Session Transfer Call Flows with stage 1 3.2.0 3.2.1 25-03-09 20bTD109r4 142 B Usage of presence for IPTV services 3.2.0 3.2.1 25-03-09 20bTD112r4 143 B integration with 3GPP PSS or MBMS 3.2.0 3.2.1 06-04-09 20bTD028r7 141 B Modifications to Targeted Advertisement section 8.14 and Annex F 3.2.0 3.2.2 07-05-09 WG2-07-060r1 144 B TAI Procedures using OMA MobAd 3.2.2 3.2.3 07-05-09 WG2-07-026r1 145 A Clarification on playlist for content distributed over multiple MF 3.2.2 3.2.3 07-05-09 WG2-07-027r2 146 B Data model for playlist 3.2.2 3.2.3 07-05-09 WG2-07-021r1 147 B Synchronisation Tasks 3.2.2 3.2.3 07-05-09 WG2-07-032r1 148 C SCF-MF interaction 3.2.2 3.2.3 07-05-09 WG2-07-033r1 149 C UGC removal 3.2.2 3.2.3 07-05-09 WG2-07-030r1 150 C Content markers clarification 3.2.2 3.2.3 07-05-09 WG2-07-058r1 151 F Correction on PVR Impulsive Capture Request Procedures 3.2.2 3.2.3 07-05-09 WG2-07-049r1 152 B Update of annex D 3.2.2 3.2.3 07-05-09 WG2-07-061r2 153 F CoD Preview Procedure 3.2.2 3.2.3 07-05-09 WG2-07-013r4 154 B IPTV service state revisited 3.2.2 3.2.3 07-05-09 WG2-07-056r3 155 F Correction on PVR SAD model 3.2.2 3.2.3 07-05-09 WG2-07-057r3 156 B Add PVR Type attribute to IPTV SAD structure 3.2.2 3.2.3 07-05-09 WG2-07-011r1 157 D Editorial Cleanup 3.2.2 3.2.3 07-05-09 WG2-07-068r1 158 D Editorial fixes on SAD and CR history 3.2.2 3.2.3 07-05-09 WG2-07-051r4 159 F Correction on Generic TAI Procedures 3.2.2 3.2.3 07-05-09 WG2-07-052r4 160 B IPTV Ad Service Procedures 3.2.2 3.2.3 07-05-09 WG2-07-019r2 161 B Pre-selection of User Generated Content 3.2.2 3.2.3 07-05-09 WG2-070-035r3 162 B Network initiated content marking 3.2.2 3.2.3 07-05-09 WG2-070-036r1 163 B Optional support for UE sending offset to the network in Session transfer 3.2.2 3.2.3 07-05-09 WG2-07-029r4 164 B Modification of N-PVR capture procedures 3.2.2 3.2.3 07-05-09 WG2-07-023r2 165 B Personalised Service Composition 3.2.2 3.2.3 ETSI ETSI TS 182 027 V3.5.1 (2011-03) 194 Change history Date WG Doc. CR Rev CAT Title / Comment Current Version New Version 07-05-09 WG2-07-010r2 166 B IPTV Content Identifier 3.2.2 3.2.3 07-05-09 WG2-07-017r2 167 B Resolving SSC issues 3.2.2 3.2.3 07-05-09 WG2-07-028r4 168 B Modification of mappings with IMS based IPTV 3.2.2 3.2.3 07-05-09 WG2-07-031r4 169 C Parental control clarifications 3.2.2 3.2.3 07-05-09 WG2-07-047r3 170 B IPTV services R2/R3, M/O 3.2.2 3.2.3 07-05-09 WG2-07-048r2 171 B Emergency alert 3.2.2 3.2.3 07-05-09 WG2-07-054r3 172 B UE-utilized PCh 3.2.2 3.2.3 07-05-09 WG2-07-055r2 173 B CRS Data Model and Procedure 3.2.2 3.2.3 07-05-09 WG2-07-072r5 174 B SSF-SCF Reference Point 3.2.2 3.2.3 07-05-09 WG2-07-059r3 175 B UGC Specific Information 3.2.2 3.2.3 07-05-09 WG2-07-034r5 176 B Incoming call management 3.2.2 3.2.3 07-05-09 WG2-07-014r4 177 B MAD and SAD 3.2.2 3.2.3 18-06-09 21WTD207r2 178 D Editors Note For Service Access History 3.2.5 3.2.6 18-06-09 21WTD144r4 179 B SCTE 130TAI arch and references 3.2.5 3.2.6 18-06-09 21WTD153r2 180 B SCTE 130TAI procedures 3.2.5 3.2.6 18-06-09 21WTD122r2 181 F Editors Notes on User Generated Content 3.2.5 3.2.6 18-06-09 21WTD123r1 182 B Editors Note on Service State 3.2.5 3.2.6 18-06-09 21WTD124r2 183 B Editors Note on N-PVR and Unicast 3.2.5 3.2.6 18-06-09 21WTD125r2 184 B Editors Note on SCF Event Handling 3.2.5 3.2.6 18-06-09 21WTD126r2 185 B Editors Note Content Ingres and Transcoding 3.2.5 3.2.6 18-06-09 21WTD127r3 186 B Definition Service Action Data 3.2.5 3.2.6 18-06-09 21WTD128r4 187 B Clarification of Mandatory and Optional 3.2.5 3.2.6 18-06-09 21WTD130r3 188 B Synchronisation Identifier 3.2.5 3.2.6 18-06-09 21WTD133r2 189 B IPTV Service State Data correction 3.2.5 3.2.6 18-06-09 21WTD134r2 190 B IPTV Service State Data usage 3.2.5 3.2.6 18-06-09 21WTD135r4 191 C IPTV Shared Service Control Policies 3.2.5 3.2.6 18-06-09 21WTD136r3 192 C Incoming Call Management 3.2.5 3.2.6 18-06-09 21WTD083r4 193 D SIP related Procedure Editor note removal 3.2.5 3.2.6 19-06-09 21WTD155r3 194 B Editor notes in Session Transfer 3.2.5 3.2.6 19-06-09 21WTD208r4 195 D Usage Of PCh Control Message 3.2.5 3.2.6 19-06-09 21WTD233r1 196 D List of Services 3.2.5 3.2.6 19-06-09 21WTD265r2 197 C IPTV Charging 3.2.5 3.2.6 19-06-09 21WTD266r2 198 C Note access to user data 3.2.5 3.2.6 19-06-09 21WTD283r1 199 F Correction on C-PVR SAD Data Model 3.2.5 3.2.6 19-06-09 21WTD050r4 200 B IPTV Security 3.2.5 3.2.6 19-06-09 21WTD143r3 201 B General TAI UE based 3.2.5 3.2.6 19-06-09 21WTD154r2 202 B Editor notes in TAI generic procedure 3.2.5 3.2.6 19-06-09 21WTD253r2 203 D Issue 3 editors note on privacy issues 3.2.5 3.2.6 19-06-09 21WTD236r1 204 D Deletion of Annex ZZY 3.2.5 3.2.6 19-06-09 21WTD303r1 205 C Note metadata synchronization 3.2.5 3.2.6 19-06-09 21WTD309r1 206 C Resolving SSC editor notes 3.2.5 3.2.6 19-06-09 21WTD311r1 207 C Resolving Presence editor notes 3.2.5 3.2.6 18-06-09 21WTD232r2 209 D Editor's notes cleanup 3.2.5 3.2.6 18-06-09 21WTD183r3 210 F Mandatory versus optional services 3.2.5 3.2.6 CRs 119 to 207 and 209, 210 approved at TISPAN#21 3.2.6 3.3.0 26-08-09 21bTD070r1 211 F Figure 21 Call Flow Correction 3.3.0 3.3.1 26-08-09 21bTD145r1 212 F CoD Call Flow Description Correction 3.3.0 3.3.1 01-10-09 22WTD035r2 213 B Synchronisation Clients in the Transport networks 3.3.1 3.3.3 01-10-09 22WTD210r3 214 C IMS IPTV Draft 3.3.1 3.3.3 Publication 3.3.3 3.3.4 Input draft 3.3.4 3.4.0 05-02-10 02(10)0008r3 215 C Functional_Modification_of_Sync_Architecture 3.4.0 3.4.1 14-04-10 02(10)0042r1 216 C Editorial_Corrections 3.4.0 3.4.1 15-09-10 02(10)157r1 217 D Term consistency on service discovery information 3.4.1 3.4.2 update of CR numbers and work item reference 3.4.2 3.4.3 publication 3.4.3 3.5.1 ETSI ETSI TS 182 027 V3.5.1 (2011-03) 195 History Document history V2.0.0 February 2008 Publication V2.4.1 July 2009 Publication V3.4.1 January 2010 Publication V3.5.1 March 2011 Publication |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 1 Scope | The present document defines a profile of the Gateway Control Protocol (H.248.1) to be used for controlling Border Gateway Functions (BGF), as defined in ES 282 003 [3]. |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 2 References | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. • For a specific reference, subsequent revisions do not apply. • Non-specific reference may be made only to a complete document or a part thereof and only in the following cases: - if it is accepted that it will be possible to use all future changes of the referenced document for the purposes of the referring document; - for informative references. Referenced documents which are not found to be publicly available in the expected location might be found at http://docbox.etsi.org/Reference. NOTE: While any hyperlinks included in this clause were valid at the time of publication ETSI cannot guarantee their long term validity. |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 2.1 Normative references | The following referenced documents are indispensable for the application of the present document. For dated references, only the edition cited applies. For non-specific references, the latest edition of the referenced document (including any amendments) applies. [1] ITU-T Recommendation H.248.1 (2005): "Gateway control protocol: Version 3" including its Amendment 1 (2008) "Corrections and clarifications". [2] Void. [3] ETSI ES 282 003: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Resource and Admission Control Sub-System (RACS): Functional Architecture". [4] ITU-T Recommendation H.248.45 (2006): "Gateway control protocol: MGC information package". [5] ITU-T Recommendation H.460.18 (2005): "Traversal of H.323 signalling across network address translators and firewalls". [6] IETF RFC 5234: "Augmented BNF for Syntax Specifications: ABNF". [7] IETF RFC 3264: "An Offer/Answer Model with Session Description Protocol (SDP)". [8] IETF RFC 2663: "IP Network Address Translator (NAT) Terminology and Considerations". [9] ITU-T Recommendation H.248.37 (2008): "Gateway control protocol: IP NAPT traversal package". [10] ITU-T Recommendation H.248.54 (2007): "Gateway control protocol: MPLS support package". [11] ITU-T Recommendation H.248.56 (2007): "Gateway control protocol: Packages for virtual private network support". Inclusive Corrigendum 1 (2009) "VLAN package clarifications". ETSI ETSI TS 183 018 V3.5.2 (2010-01) 10 [12] ITU-T Recommendation H.248.40 (2007): "Gateway Control Protocol: Application Data Inactivity Detection Package". [13] ITU-T Recommendation H.248.14 (2009): "Gateway control protocol: Inactivity timer package". [14] ITU-T Recommendation Q.3303.2 (2007): "Protocol at the interface between a Policy Decision Physical Entity (PD-PE) and a Policy Enforcement Physical Entity (PE-PE) (Rw Interface): H.248 Alternative". [15] ITU-T Recommendation H.248.11 (2002): "Gateway control protocol: Media gateway overload control package". Inclusive Corrigendum 1 (2008) "Clarifying MG-overload event relationship with ADD commands". [16] ITU-T Recommendation H.248.41 (2006): "Gateway control protocol: IP domain connection package" including its Amendment 1 (2008) "IP Realm Availability Package". [17] ITU-T Recommendation H.248.52 (2008): "Gateway control protocol: QoS Support packages" including its Amendment 1 (2009) "Clarifications and updates to the differentiated services package". [18] ITU-T Recommendation H.248.43 (2008): "Gateway control protocol: Packages for gate management and gate control". [19] ITU-T Recommendation H.248.53 (2009): "Gateway control protocol: Traffic management packages". [20] Void. [21] Void. [22] ETSI ES 283 018 (V1.1.4): "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Resource and Admission Control: H.248 Profile for controlling Border Gateway Functions (BGF) in the Resource and Admission Control Subsystem (RACS); Protocol specification". [23] ITU-T Recommendation H.248.49 (2007): "Gateway control protocol: Session description protocol RFC and capabilities packages". [24] ITU-T Recommendation H.248.36 (2005): "Gateway control protocol: Hanging Termination Detection package". [25] ITU-T Recommendation H.248.47 (2008): "Gateway control protocol: Statistic conditional reporting package". [26] Void. [27] Void. [28] IETF RFC 4566: "SDP: Session Description Protocol". [29] IETF RFC 1123: "Requirements for Internet Hosts - Application and Support". [30] ITU-T Recommendation H.248.8: "Gateway control protocol: Error code and service change reason description". [31] IETF RFC 3605: "Real Time Control Protocol (RTCP) attribute in Session Description Protocol (SDP)". [32] ETSI ES 283 018 (V2.7.1): "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Resource and Admission Control: H.248 Profile for controlling Border Gateway Functions (BGF) in the Resource and Admission Control Subsystem (RACS); Protocol specification". ETSI ETSI TS 183 018 V3.5.2 (2010-01) 11 [33] ITU-T H.Imp248.1 Version 2 (2008): "Implementors' Guide for Recommendation H.248.1 Version 2 (Media Gateway Control Protocol) and its Corrigendum 1 (03/2004)". NOTE: Available at: http://www.itu.int/rec/T-REC-H.Imp248.1-200805-I/en. [34] ITU-T Recommendation H.248.58 (2008): "Gateway control protocol: Packages for application level H.248 statistics". [35] Void. [36] IETF RFC 4975 (2007): "The Message Session Relay Protocol (MSRP)". [37] ETSI TS 187 003 (V1.7.1): "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); NGN Security; Security Architecture". [38] IETF RFC 3551: "RTP Profile for Audio and Video Conferences with Minimal Control". |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 2.2 Informative references | The following referenced documents are not essential to the use of the present document but they assist the user with regard to a particular subject area. For non-specific references, the latest version of the referenced document (including any amendments) applies. [i.1] ETSI TS 102 333: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Gate control protocol". [i.2] ETSI TS 183 025: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); H.248 Non-call related procedures and management system interaction". [i.3] IETF RFC 2327: "SDP: Session Description Protocol". [i.4] ETSI ES 282 001: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); NGN Functional Architecture". [i.5] ITU-T Recommendation V.152: "Procedures for supporting voice-band data over IP networks". Inclusive Corrigendum 1 (09/2005) and Corrigendum 2 (05/2006). [i.6] IETF RFC 4301: "Security Architecture for the Internet Protocol". [i.7] ITU-T Recommendation H.248.18: "Gateway control protocol: Package for support of multiple profiles". [i.8] IETF RFC 3550: "RTP: A Transport Protocol for Real-Time Applications". [i.9] IEEE 802.3: "Ethernet Working Group". [i.10] ITU-T Recommendation Y.1221 (2002): "Traffic control and congestion control in IP based networks". Inclusive a) Amendment 1 (2004): 'Extensions to transfer capabilities', b) Amendment 2 (11/2005): 'Further extension to transfer capabilities ', c) Amendment 3 (10/2007): "New Appendix IV - Example methods for determining token-bucket parameters". [i.11] ITU-T Recommendation Y.1541 (2006): "Network performance objectives for IP-based services". [i.12] ETSI TS 181 005: "Telecommunications and Internet Converged Services and Protocols for Advanced Networking (TISPAN); Service and Capability Requirements". [i.13] Void. [i.14] Void. [i.15] Void. [i.16] Void. [i.17] Void. ETSI ETSI TS 183 018 V3.5.2 (2010-01) 12 [i.18] ETSI TR 183 068 (V0.0.4): "Telecommunications and Internet Converged Services and Protocols for Advanced Networks (TISPAN); Guidelines on using Ia H.248 profile for control of Border Gateway Functions (BGF); Border Gateway Guidelines". [i.19] ITU-T Recommendation H.248.57 (2008): "Gateway Control Protocol: RTP Control Protocol Package". [i.20] IETF RFC 3711: "The Secure Real-time Transport Protocol (SRTP)". [i.21] IETF RFC 4145: "TCP-Based Media Transport in the Session Description Protocol (SDP)". [i.22] ETSI TR 183 025: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); H.248 Non-call related procedures and management system interaction". |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 3 Definitions and abbreviations | |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: address: term used for "network address" (a.k.a. IP address) Border Gateway Function (BGF): packet-to-packet gateway for user plane media traffic NOTE 1: The BGF performs both policy enforcement functions and NA(P)T functions under the control of the SPDF. NOTE 2: A Border Gateway Function (BGF) provides the interface between two IP-transport domains. It may reside at the boundary between an access network and a core network or between two core networks, as defined in ES 282 001 [i.4]. The BGF has the "H.248 MG" role in the scope of this Profile. gate: represents a transport plane function enabling or disabling the unidirectional forwarding of IP packets under specified conditions (e.g. QoS) NOTE: See TS 102 333 [i.1]. IP-to-IP interworking modes: available SDP information elements and values in the signalled SDP "media description" (mainly "m=" and "a=" lines) by the SPDF (MGC), may be used to categorize following interworking modes from BGF (MG) perspective (see also annex G in [i.18]): (1) "Media-agnostic": - the "m=" line values of media type (<media>) and media format (<fmt>) are not allowing to conclude for the BGF (MG) on the transported "media" information; (2) "Media-aware": - the "m=" line values of media type (<media>), transport protocol (<proto>) and media format (<fmt>) are unambiguously defining the entire protocol stack of the H.248 IP termination, i.e. the BGF (MG) knows transported "media" information and the underlying transport protocol type; (3) "Transport protocol-agnostic" (or briefly "transport-agnostic"): - the BGF (MG) may not conclude from signalled SDP information elements on the transported IP payload information (see note); (4) "Transport protocol-aware" (or briefly "transport-aware"): - the value of the IP protocol field is indicated by the signalled SDP information elements, e.g. by the "m=" line value of the transport protocol (<proto>) field. ETSI ETSI TS 183 018 V3.5.2 (2010-01) 13 NOTE: The BGF (MG) could principally derive the used transport protocol by analyzing the protocol field (http://www.iana.org/assignments/protocol-numbers) in the IP header, but such a function is beyond H.248. The BGF (MG) is still transport protocol-agnostic from H.248 point of view. pinhole: configuration of two associated H.248 IP Terminations within the same H.248 Context, which allows/prohibits unidirectional forwarding of IP packets under specified conditions NOTE 1: A pinhole may also be referred to as a "gate". NOTE 2: E.g. address tuple. NOTE 3: See ITU-T Recommendation H.248.37 [9]. NOTE 4: See annex A in TR 183 068 [i.18]. NOTE 5: It has to be noted that there is also a different definition for "pinhole", which is used in the context of H.323 systems (see ITU-T Recommendation H.460.18 [5]). The difference is the fact that the "H.248 pinhole" and "gate" are unidirectional, whereas the "H.323 pinhole" is bidirectional. port: term used for "transport port" (a.k.a. L4 port) Resource and Admission Control Subsystem (RACS): provides admission control and gate control functionalities NOTE: Including the control of NAPT and priority marking. Service Policy Decision Function (SPDF): logical policy decision element for Service Based Policy control (SBP) NOTE: The SPDF makes policy decisions using policy rules for Service Based Policy control (SBP). The SPDF has the "H.248 MGC" role in the scope of this Profile. transcoding: translation from one type of encoded media format to another different media format EXAMPLE 1: G.711 A-law to μ-law or vice versa. EXAMPLE 2: G.711 to G.726-40K. EXAMPLE 3: G.729 to AMR with 4.75 rate. EXAMPLE 4: G.711 to a broadband codec that operates at 256 kbps, etc. NOTE 1: The definition of "transcoding" is according to clause 3.10/ITU-T Recommendation V.152 [i.5]. NOTE 2: Transcoding belongs to the category of "media aware" IP-to-IP interworking (see above). transport address: combination of an Address and a Port |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: ABNF Augmented Backus-Naur Form AC Admission Control AF Application Function B2BIH Back-to-Back IP Host (mode) B2BRE Back-to-Back RTP Endsystem (mode) BGF Border Gateway Function BGW Border GateWay C-BGF Core-BGF CBR Constant BitRate CNAME Canonical End-Point Identifier CoAC Context Admission Control DA Destination Address DP Destination Port DSCP Differentiated Services Code Point GCP Gate Control Protocol ETSI ETSI TS 183 018 V3.5.2 (2010-01) 14 HR High Resolution (Report) HW HardWare IBCF Interconnect Border Control Function I-BGF Interconnect-BGF ICMP Internet Control Message Protocol IMS IP Multimedia Subsystem IP Internet Protocol IPR IP Router (mode) IPsec IP Security (RFC 4301 [i.6]) LD Local Descriptor (H.248 protocol element) Local Destination (H.248 naming convention) LS Local Source (H.248 naming convention) MG Media Gateway MGC Media Gateway Controller MID Message IDentifier (H.248) MP Measuring Points MPLS Multi Protocol Label Switching NA Not Applicable NAPT Network Address and Port Translation NAPT-PT NAPT and Protocol Translation NAT Network Address Translation NGN Next Generation Network PCI Protocol Control Information PHB Per-Hop Behaviour QoS Quality of Service RACS Resource and Admission Control Subsystem RD Remote Descriptor (H.248 protocol element) Remote Destination (H.248 naming convention) RFC Request For Comments (IETF) RP Reporting Points RS Remote Source (H.248 naming convention) RTCP RTP Control Protocol RTP Real-time Transport Protocol RTSP Real Time Streaming Protocol SA Source Address SAF Source Address Filtering SAM Source Address Mask SBP Service Based Policy control SCTP Stream Control Transport Protocol SDES Source Description SDP Session Description Protocol SIP Session Initiation Protocol SP Source Port SPDF Service Policy Decision Function SPF Source Port Filtering SPR (Remote) Source Port SPRR (Remote) Source Port Range SRTP Secure Real-time Transport Protocol SSRC Synchronization Source (Identifier StAC Stream Admission Control TCP Transmission Control Protocol THF Topology Hiding Function THIG Topology Hiding Interconnection Gateway TISPAN Telecommunications and Internet converged Services and Protocols for Advanced Networking Tman Traffic Management UDP User Datagram Protocol VBR Variable BitRate VLAN Virtual LAN VPN Virtual Private Network XR eXtension Reports ETSI ETSI TS 183 018 V3.5.2 (2010-01) 15 |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 4 Applicability | |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 4.1 Architecture | The present document defines an H.248 Profile for the reference point between the Service Policy Decision Function (SPDF) and the Border Gateway Function (BGF), known as the Ia reference point. The SPDF interacts with the BGF to request services. This reference point is used for communication between the SPDF and a Core Border Gateway Function (C-BGF) and between the SPDF and an Interconnect Border Gateway Function (I-BGF). Specific requirements for this reference point are described in ES 282 003 [3]. Figure 1 illustrates the architecture assumed in the present document. SPDF IP Transport Network (Core) IP Transport Network (Access/Core) Scope of the present document BGF AF Figure 1: Reference architecture The names 'BGF' and 'SPDF' are terminology of the RACS functional architecture (stage 2). The SPDF role in this protocol (stage 3) specification is provided by the H.248 MGC entity and the BGF role by the H.248 MG entity. The associated stage 2 and stage 3 names are used synonymously in this H.248 profile specification. |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 4.2 Border Gateway Guidelines | Guidelines for usage and implementation of border gateways are described in [i.18]. |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5 Profile description | |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.1 Profile identification | Table 1: Profile identification Profile name: ETSI_BGF Version: 3 ETSI ETSI TS 183 018 V3.5.2 (2010-01) 16 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.