- ETSI TISPAN
| Contribution Number | Title | Short Description | Date | |
| 1 | 18bTD195r2 | 18bTD195r2_WI_2071_ Correction_of_inconsistency_ of_IPTV_presence_timer_ definition_between_ stage_2_and_3 | Summary for change In ETSI TISPAN TS 182 027 R2, IPTV presence timer is defined as follows: "In order to cope with overload possibly caused by numerous channel-hopping, it shall be possible to define a timer set up to limit the number of publications. This timer is started after each publication, and any channel hopping triggered before the timer elapses shall not be taken into account as a criteria for publication of a presence document." In case a channel change occurs just after the publication, this will not be reported even if the user does change the channel for long. In ETSI TISPAN TS 183 027, the timer (called Tcc timer) is not trigerred after each publication but after each channel change (Cf. clause 5.1.6). This latter definition is more in line with the requirement and more accurate to provide the channel really watched by the user. Therefore, this contribution aligns the timer definition in stage 2 with what is defined in stage 3. |
26 Sept. 2008 |
| 2 | 19WTD109r2 | 19WTD109r2_WI_2070_ Advert_alignment_SCTE-TFI | Reason for change This contribution is related to editor's note inviting to propose to discuss applicability of advanced advertising standards defined by SCTE to the architecture. Summary for change Add SCTE references, SCTE entities <> TISPAN entities mapping, add placement strategy from SCTE standard |
03 - 05 November 2008 |
| 3 | 19WTD110r2 | 19WTD110r2_WI_2070_ Advert_SIG_flow_MF_side | Reason for change Current advertising call flows does not take into account two types of placement opportunities defined in SCTE 130 part 3 : predetermined and unexpected. Ad-SCF entity merged with other SCF entities. Summary for change Introduction of ad insertion type ; Proposition to modify signaling flow for TAI at MF side |
03 - 05 November 2008 |
| 4 | 19WTD111r2 | 19WTD111r2_WI_2070_ COD_offset | Reason for change Current TISPAN procedures specify how to retrieve COD offsets for all COD but does not specify how to retrieve a COD offset for one specific COD , and does not explicit procedures to save COD offset Summary of change Modification of the COD session initiation to propose resuming VOD from the last saved offset. New procedure to save the COD offset |
03 - 05 November 2008 |
| 5 | 19WTD112r1 | 19WTD112r1_WI_2070_ CR_attributes_UEprofile | Reason for change The current IPTV user profile structure does not permit to store user profiling and content recommandation data. Summary for change Update the IPTV user profile structure with user profiling and CR data. |
03 - 05 November 2008 |
| 6 | 19bTD152r5 | 19bTD152r5_WI_2070_ Advert_alignment_SCTE | Summary for change Add SCTE-130 references, SCTE-130 entities <> TISPAN entities mapping |
24-28 Nov. 2008 |
| 7 | 19bTD153r2 | 19bTD153r2_WI_2070_ Advert_SIG_flow_MF_side | Reason for change Current advertising call flows does not take into account two types of placement opportunities defined in SCTE 130 part 3 : predetermined and unexpected. Ad-SCF entity Summary for change Introduction of ad insertion type merged with other SCF entities. |
24-28 Nov. 2008 |
| 8 | 19bTD154r3 | 19bTD154_WI_2070_CR_ attributes_UEprofile_r3 | Reason for change The current IPTV user profile structure does not permit to store user profiling and content recommendation data. It is proposed in this contribution to handle below requirement from TS 181 016 V3.1.2 regarding User profiling and Recommendation: 5.14.1 The IPTV solution shall support mechanisms for an IPTV service provider to collect information about user consumption of content and services over a period of time, e.g. watched programs on broadcast TV channels, consumed CoD assets, frequently used integrated IPTV and NGN services. 5.14.2 The IPTV solution shall support mechanisms for an IPTV service provider to use this information for IPTV content and service recommendations. Summary for change Update the IPTV user profile structure with user CR notification Creation of a new clause on Content Recommendation |
24-28 Nov. 2008 |
- Open IPTV Forum
| Contribution Number | Title | Short Description | Date | |
| 1 | OIPTVF-MD- Protocols-125- UE_profile_ alignment_ with_TISPAN.DOC | UE profile alignment with TISPAN | Proposal of alignment with TISPAN for UE profile | 5 September 2008 |
| 2 | OIPTVF-MD- Protocols-126- XCAP_alignment_ with_TISPAN.DOC | XCAP_alignment_with_TISPAN | Proposal of alignment with TISPAN for XCAP | 5 September 2008 |
| 3 | OIPTVF-MD- Protocols-127- Thomson_Technical_ review_on_ protocol_ specification.doc | Thomson_Technical_review_ on_protocol_specification | Complete check of protocol specification for consistencies | 5 September 2008 |
| 4 | OIPTVF-MD- Protocols-134- IPTV_presence_ schema_ modifications.DOC | IPTV_presence_schema_ modifications | Proposal of alignment with TISPAN for IPTV presence schema | 5 September 2008 |
