hash
stringlengths 32
32
| doc_id
stringlengths 7
13
| section
stringlengths 3
121
| content
stringlengths 0
3.82M
|
|---|---|---|---|
d65cbf1d92ccd5769ec9de06d2326895
|
182 028
|
11.3 Media broadcast with trick modes
|
This clause provides the flows for the media broadcast with trick modes IPTV services integrated into the TISPAN NGN architecture and inter-working with the NGN common functions and components. The clause presents generic flows and does not mandate placement of functions. DRM flows are not included. 14. CoD VCR- control 13. Authorisation verification 1. Acquisition of SD&S information 2. UE 4. 9. Pause life TV. Play from the pause position. Setup 10. Resource reservation 12. Pause life TV. Play from the pause position. Setup 15. Automatic resource release 11. Transport MCF IPTVC 3. 5. Linear TV channels A 6. Join channel A 7. Channel A 8. Pause life TV. Pause. Leave channel A RACS MDF IUDF SD&S/ CFIA Figure 16: NGN media broadcast with trick modes procedure The flows shows generic case where MDF providing linear TV is not co-located with MCF providing "on-demand" functionality. MCF and MDF can be located in the same place. 1) UE requests SD&S information from SD&S. 2) SD&S verifies user profiles from IUDF. 3) Media broadcast with trick modes is a subscription based service. At the subscription time, Customer Facing IPTV Applications optionally create authorization record (play ticket) to authorize this service. 4) SD&S is returned to the user. 5) MDF outputs BTV multimedia stream, such as regular TV channels or scheduled content. 6) UE requests transport to join linear TV channel A (BTV multicast stream). Optionally, resource admission control may take place at this stage. For Multicast, this is typically performed by an A-RACF, which can be separately located or collocated with the Transport Processing Function [10]. This is shown by a dotted line. ETSI ETSI TS 182 028 V3.5.1 (2011-02) 42 7) Channel A is delivered. 8) User requests to pause linear TV channel. UE requests transport to leave linear TV channel A. 9) User requests to re-start play from the paused position. UE issues setup command and requests IPTV Control the location of the MCF. Optionally ticket data is supplied. This selection is optional, previously selected MCF can be used or the default MCF can be supplied to the UE during service initialization steps. 10) IPTV control selects MCF based upon operator defined criterions and requests RACS to allocate resources between the end-points. Distributed RACS interfaces are allowed. 11) IPTV control replies MCF location to UE. 12) UE issues play command and requests MCF to deliver media from the pause position supplying position. 13) MCF optionally verifies user credentials to request multimode delivery. 14) UE utilizes VCR style control over media. 15) Automatic resource release follows session termination, which can be initiated either by end point UE or MCF, or by an IP network. Although it is not necessary to explicitly tear-down an old reservation, we recommend that during normal operation MCF or IPTV Control send a teardown request to RACS as soon as the session has finished. Return to live linear TI channel is achieved by repeating steps 6) and 7). Return to trick mode is archived by repeating steps 8) to 13). NGN IPTV media broadcast with trick modes service is combination of separate BTV and CoD IPTV sessions joined together at the service level. See clause 11.1 for definition of CoD NGN IPTV session and clause 11.2 for definition of BTV NGN IPTV session. NGN IPTV media broadcast with trick modes session is a service level aggregation as defined above and is not used for billing purposes.
|
d65cbf1d92ccd5769ec9de06d2326895
|
182 028
|
11.4 Near CoD
|
This clause provides the flows for the Near CoD IPTV services integrated into the TISPAN NGN architecture and inter- working with the NGN common functions and components. The clause presents generic flows and does not mandate placement of functions. DRM flows are not included. ETSI ETSI TS 182 028 V3.5.1 (2011-02) 43 3. Acquisition of SD&S 1. Init Near CoD Channels 5. Reply the Near CoD Services offers 6. Purchase the Near CoD Service 4. Check 8. Reply the Channel list of the Near CoD Service 9. Join the upcoming Near CoD i Channel to Begin Playback 11. Near CoD Channel i 12. Leave current Near CoD Channel i 13. Join the next Near CoD i + 1 Channel for Skip Forward 15. Near CoD Channel i + 1 16. Leave the current Near CoD Channel to End Playback ... 2. Near CoD Channels Near CoD Channel 1 Near CoD Channel n Rolling Start . . . 7. Update 10. 14. ... UE Transport RACS MDF IUDF/ UPSF SD&S/ CFIA IPTV Control Figure 17: NGN IPTV near CoD procedure The flow represents a generic case where MDF provides a CoD content on a set of multicast channels with a fixed interval, e.g. an interval of 15 minutes. For example, one content's playback time is 148 minutes. Near CoD Channel 0 starts output stream at time offset 00 minutes. Near CoD Channel 1 starts output stream at time offset 15 minutes, and so on until Near CoD Channel 9 starts output stream at time offset 135 minutes. 1) IPTV Control requests the MDF to initiate the Near CoD channels. 2) MDF outputs Near CoD channel streams to the transport. 3) UE requests the Near CoD services information from SD&S. ETSI ETSI TS 182 028 V3.5.1 (2011-02) 44 4) SD&S checks the user profiles from IUDF/UPSF. 5) SD&S returned Near CoD Services offered. 6) UE purchases the Near CoD from CF IPTV Applications. 7) CF IPTV Applications updates the user profiles from IUDF/UPSF to record the purchase. 8) CF IPTV Applications returned the Channel list of the Near CoD Service which the user just purchased. Each channel has information of Start Time and End Time. 9) UE requests transport to join Near CoD channel i which was the next rolling start channel by the time of the request. 10) Optionally, resource admission control may take place at this stage. For Multicast, this is typically performed by an A-RACF, which can be separately located or collocated with the Transport Processing Function [10]. 11) Near CoD Channel i is delivered. 12) User requests to Skip Forward. UE requests transport to leave Near CoD Channel +1. 13) UE requests transport to join Near CoD channel +i+1 which was the next channel. 14) Optionally, resource admission control may take place at this stage. For Multicast, this is typically performed by an A-RACF, which can be separately located or collocated with the Transport Processing Function [10]. 15) Near CoD Channel i+1 is delivered. 16) User requests to Stop or End play the Near Cod. UE requests transport to leave Near CoD Channel +i. Step (1) and (2) is the flow of setup of Near CoD. Step (3) to (8) is the flow of Service Discovery & Selection of Near CoD. Step (10) to (17) is the flow of UE playback control of Near CoD. Steps (12) to (16) are the optional interaction flow during the playback of Near CoD. Steps 12-15 applicable for other trick mode operations: e.g. skip backward.
|
d65cbf1d92ccd5769ec9de06d2326895
|
182 028
|
11.5 Push CoD
| |
d65cbf1d92ccd5769ec9de06d2326895
|
182 028
|
11.5.1 Push CoD procedures using notification
|
IPTV ASF (CFIA) IPTV-C UE UPSF/ IUDF 2. Check profile & notification Push CoD rules 6. UE accept content 5. Deliver Notification about Push CoD content to UE 4. Push CoD event 1. Subscribe to Push CoD service 3. Accepted 7. Push CoD content is delivered to UE MF MCF & MDF Figure 18: Push CoD services procedure ETSI ETSI TS 182 028 V3.5.1 (2011-02) 45 The detailed description of procedure is following: 1) User subscribes to Push CoD service. 2) According to policies the CFIA may request IPTV sub-profile of federalized user profile from IUDF or UPSF. CFIA decides user authorization to use a service based on received information and service logic. 3) CFIA authorizes request and confirms successful subscription to the UE. NOTE: IPTV Service provider may initiate Push CoD without explicit user subscription in which case 1-3 may be optional. 4) New Push CoD event acts as a trigger for CFIA. 5) CFIA delivers notification to the UE (including CoD content identifier) using notification framework. 6) UE may accept delivery of Push COD. 7) UE initiate via IPTV-C either CoD content delivery as described in clause 11.2 or CoD content download from MDF. The content may be either viewed immediately or stored for later viewings.
|
d65cbf1d92ccd5769ec9de06d2326895
|
182 028
|
11.6 User generated content
| |
d65cbf1d92ccd5769ec9de06d2326895
|
182 028
|
11.6.1 Overview
|
There are two types of User Generated Content (UGC) procedures: • creation of the User Generated Content: this type of procedure allows a user to declare UGC with its metadata and upload/upstream his/her own content to the network as discussed in clause A.9.1.2 [1] and in accordance with the IPTV SP policies for UCG services. • watching of User Generated Content: this type of procedure allows a user to select and watch User Generated Content. NOTE: The UGC watching procedure may start before the UGC creation procedure has been completed, e.g. as defined in Clause A.9.1.2 of [1].
|
d65cbf1d92ccd5769ec9de06d2326895
|
182 028
|
11.6.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 CFIA and receives a content ID for the UGC from the CFIA. 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 CFIA 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. Step 3: Creation of User Generated Content. • The UE initiates a session with the CFIA and MF in order to create the User Generated Content (i.e. upload/upstream (unicast) the content to the MF). The MF provides the CFIA with the location at which the UGC becomes available. Step 4: Publication of User Generated Content information by the CFIA. • The CFIA establishes the relationship between UGC content ID, UGC description, and optionally the MF, and publishes this UGC description information to the SD&S. The UGC description publication by the CFIA in step 4 may take place before, during or after the UGC content creation delivery session initiation in step 3. ETSI ETSI TS 182 028 V3.5.1 (2011-02) 46 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. Figure 19: UGC creation procedure The UGC procedure comprises the following major steps: 1) The UE sends a request for User Generated Content declaration. 1a) The UE sends a User Generated Content Declaration Request to the CFIA. This request asks for a unique content ID (that is independent of the address where the UGC can be retrieved by other UEs). 1b) The CFIA may check user rights and user profile prior to granting the UE permission to create UGC and generates a unique UGC ID. 1c) The CFIA confirms that the UE can create UGC by sending a Declaration Response containing the UCG ID and the designated MCF/MDF where the UCG can be created (uploaded/upstreamed). 2) The UE sends a request for UGC description: 2a) The Description Request contains a description of the User Generated Content (e.g. name, type, restriction, textual description, selected group users, type of content, coding). 2b) The CFIA records the UGC description, establishes the relationship between UGC ID and UGC description and sends a UGC Description Response to the UE. 3) UE initiates creation of User Generated Content for uploading or upstreaming the content to the designated MDF and confirms to the CFIA the publication of content (making it available for usage). 4) The CFIA establishes the relationship between UGC ID, UGC description and optionally UGC location (address), and publishes this UGC information to the SD&S. The UE can modify or terminate the established UGC creation session at a later stage. CFIA MF 1c. UGC Declaration Response 4. Publication UGC delivery initiation/modification/termination (clause 11.6.3) 1b. Check rights & user profile User Data SD&S 1a. UGC Declaration Request 3. UGC Creation 2a. UGC Description Request 2b. UGC Description Response UE ETSI ETSI TS 182 028 V3.5.1 (2011-02) 47
|
d65cbf1d92ccd5769ec9de06d2326895
|
182 028
|
11.6.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 SD&S. 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 (see clause 11.6.2, steps 1, 2 and 4), but not yet created (see clause 11.6.2, step 3). Step 2: Watching of UGC: • Session initiation can be performed by the UE or the CFIA 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 Push CoD session (see clause 11.5.1, figure 18) when the UGC is created. Figure 19A: UGC watching procedure 1) The UE selects UGC through service selection procedure with SD&S as defined in clause 8.2 step 4. The SD&S may restrict the list of UGC depending on user identity and UE capabilities. Alternatively, UGC availability is triggered through the notification procedure from the CFIA as defined in clause 11.8.2 or recommendation procedure from the CFIA as defined in clause 11.9.2. The UE may also pre-select UGC that has already been declared and published (clause 11.6.2, steps 1, 2 and 4), but not yet created (see clause 11.6.2, step 3). This UGC pre-selection is described in steps 1a) - 1c). 2) After publication, the CFIA can send a notification for the availability of UGC to selected UEs (using the existing mechanism from clause 11.8.2). 3) The notification can trigger the delivery of UGC to selected UEs of one or more users (e.g. based on a user's subscription) using existing procedures (e.g. Linear TV defined in clause 11.1 or Multimedia CoD defined in clause 11.2). If the user pre-selected UGC, then this UGC will be delivered using Push CoD (see clause 11.5.1, figure 18) and the UE automatically accepts the notification and initiates a watching session to the MF. The UE can modify or terminate the established UGC creation session later on. UE CFIA MF User Data SD&S 1a. UGC pre-selection request 1. UGC Selection 1b. CFIA stores UGC pre- selection 1c. UGC pre-selection response 3. UGC watching initiation UGC watching modification/termination 2. Notification of UGC availability ETSI ETSI TS 182 028 V3.5.1 (2011-02) 48
|
d65cbf1d92ccd5769ec9de06d2326895
|
182 028
|
11.7 Pay Per View
|
Thus clause discusses pay per view service. PPV service provides access to regular IPTV content (e.g. BC, CoD, UGC) through packaged service offers (e.g. pay per packages of assets, pay per specific program or pay per series) with pre-defined access conditions (e.g. pay per number of views or access time). PPV service is defined by IPTV SP. Notification service may be used to notify the UE about available PPV services. Alternatively, the UE may select PPV services from available offer using SD&S. NOTE: PPV package may contains combination of multiple IPTV content (e.g. BC, CoD, etc.) within single PPV service offer. IPTV ASF (CFIA) IPTV-C UE UPSF/ IUDF 2. Check profile & notification PPV rules 6. Deliver Notification about end of PPV period to UE 5. Expiration of PPV event 3. Subscription accepted 7. Terminate PPV and release resources MCF & MDF 4. Service initiation and delivery of IPTV content during PPV limited period 1. Subscribe to PPV service Figure 19B: PPV services High level description of service procedure: 1) User subscribes to PPV service. 2) The CFIA may request IPTV sub-profile of federalized user profile from IUDF or UPSF. CFIA authorizes access to the service based on User Profile and service access logic (e.g. pay per view /time / number of plays). Payment may be requested and/or user credit may be checked before authorizing service access. 3) CFIA authorizes request and confirms successful subscription to the UE. 4) UE chooses to use PPV service and requests delivery of PPV content via existing procedures (e.g. Linear TV in 11.1, Multimedia content on demand (CoD) in clause 11.2 or User generated content in 11.6). PPV may provide access for a limited period to the specified content (e.g. TV channels, CoD assets, etc.). CFIA may need to push access control via IPTV-C to RACS and revoke when PPV service expires. 5) Expiration of PPV purchase acts as a trigger for CFIA. 6) CFIA delivers notification about expiration in advance to the UE (including timeout when service ends or offer to extend PPV period) using notification framework. 7) PPV service is terminated and also resources are released using existing procedures (following procedures used for service initiation in step 4). ETSI ETSI TS 182 028 V3.5.1 (2011-02) 49 11.8 Messaging and notification services
|
d65cbf1d92ccd5769ec9de06d2326895
|
182 028
|
11.8.1 Messaging procedures
|
If messages are delivered via CFIA, then the role of Common NGN ASF is to terminate and process multiple incoming messages into generic format before passing to CFIA for presentation to the UE. This is illustrated by the figure below. The responses from the UE via CFIA should be passed back to Common NGN ASF, which will route the messages to the appropriate destination. UE2 IPTV ASF (CFIA) NGN ASF 1. Send Message 2. Send message UE1 9. Present / Announce incoming message 3. Send message 5. Forwarding User Data 4. Check profile & messaging forwarding 8. Confirm of delivery 6. Deliver Message to destination 7. Confirm of delivery Figure 20: Messaging between IPTV UEs Messaging between IPTV UEs: 1) User 1 sends a message from UE1 to the IPTV user 2 at the UE2. 2) The UE1 sends request with attached message and recipient identifier to the CFIA. 3) The CFIA forwards message to the NGN ASF messaging server. 4) According to policies the NGN ASF may request IPTV sub-profile of federalized user profile from NGN IUDF if this information is not stored in NGN ASF. The NGN ASF identified destination UE based on policy and destination information. 5) Based on policies the NGN ASF decides that the message should be forwarded to the IPTV UE2. The Common NGN ASF informs CFIA about the incoming message. 6) The CFIA delivers message to the UE 2. 7) Successful delivery is confirmed to UE 1 via CFIA. 8) Successful delivery is confirmed to UE 1 via CFIA. 9) The message is presented to user 2. NOTE: The message can be directly delivered from and to Common NGN ASF.
|
d65cbf1d92ccd5769ec9de06d2326895
|
182 028
|
11.8.2 Notification procedures
|
Common notification framework should be used for notifications about services from internal elements, e.g. CFIA or NGN applications (NGN ASF) to IPTV UE as described in procedures below. Such notifications can include, for example, emergency alerting, advertising, content recommendation or maintenance notification. ETSI ETSI TS 182 028 V3.5.1 (2011-02) 50 IPTV ASF (CFIA) NGN ASF (or IPTV-C) 5. Send notification UE1 6. OK UPSF/ User Data 4. Check profile & notification message rules 8. OK 7. Deliver Notification message to UE1 3. Notification event 1. Subscribe Notification service 2. Confirmed subscription 9. Message presented to UE or store in message box Figure 21: Procedure for notification services Procedure for notification services: 1) User 1 subscribe to Notification service. 2) IPTV control (or NGN ASF) authorizes and confirms successful subscription to notification service. NOTE 1: Step 1 and 2 may be performed via CFIA. NOTE 2: IPTV Service provider may initiate notification service to the UE, e.g. for maintenance purposes without explicit user subscription in which case 1-2 may be optional. 3) New notification event acts as a trigger. 4) According to policies the IPTV-C may request IPTV sub-profile of federalized user profile from IUDF or UPSF. IPTV-C decides user authorization and the appropriate UE to send notification to. 5) IPTV-C inform CFIA about notification event. 6) CFIA acknowledges notification event. NOTE 3: Step 5 and 6 are optional, e.g. when NGN ASF or IPTV-C notifies the UE directly. 7) Notification message is delivered to UE (via Tr reference point). 8) Successful delivery is confirmed to IPTV-C (or NGN ASF as external notification server). NOTE 4: Step 1 and 2 may be performed via CFIA. 9) Message is present to user or stored on UE for future presentation.
|
d65cbf1d92ccd5769ec9de06d2326895
|
182 028
|
11.9 Recommendations
|
The Content and Service Recommendation Service (CRS) is used for providing recommendations to IPTV users or user groups. The recommendation service may make recommendations to user/groups based on different criteria which include user profile, preferences settings, current viewing habits, historic user activities as defined in [1]. The recommendation may be in form of text message (notification), multimedia message, content bookmark (pointer to recommended content) or video recommendation streamed from MDF. ETSI ETSI TS 182 028 V3.5.1 (2011-02) 51 The CRS service procedures include 2 main functions: 1) Aggregation of metadata for recommendations, e.g.: a) List of users with unique identifiers and associated service profiles. b) Asset metadata for CoD and linear TV, EPG/BCG. c) Historic information about user consumption of IPTV services. 2) Generation of recommendations on request of external triggers. The architecture supports different ways to deliver recommendations to the UE. Typically, content recommendations could be included into customer facing IPTV application. However, other delivery means are possible, e.g. common notifications framework can be used to deliver recommendations as defined in clause 11.8. The notifications framework can be used e.g. to deliver time-sensitive recommendations to the user.
|
d65cbf1d92ccd5769ec9de06d2326895
|
182 028
|
11.9.1 Recommendations overview
|
A high level procedure for content and service recommendations is presented on figure 22. Figure 22: High Level Procedures for CRS 1) Aggregation and user configuration of profile or preferences for CRS. NOTE: This user configuration part of the step is optional. The recommendations may be based only on IPTV SP user profile. 2) An application detects recommendation opportunity and requests for content recommendations. For example, such an event could be a user action of accessing or navigating CFIA, changes in the presence state or change in the service offers. 3) The application after detecting recommendation opportunity may send recommendation notifications to the UE immediately (push based CRS, push from CRS towards UE). Notification framework (described in clause 11.8.2 Notification procedures) is used to deliver CRS recommendation notifications (e.g. as a text message (notification), multimedia message, content bookmark, pointer to recommended content). 4) CFIA may provide CRS recommendation data, e.g. in addition to SD&S services information during service navigation the recommendations may be included into the CFIA user interface. In this case step 3 is optional. The UE may request additional data at step 4 (e.g. advertising clips, previews, trailers, etc.).
|
d65cbf1d92ccd5769ec9de06d2326895
|
182 028
|
11.9.2 Recommendations procedures
|
This clause describes intermediate level procedures for content and service recommendations. UE MCF/MDF IPTV-C 4. Delivery of content recommendations 3. Recommendation Notification CFIA SD&S UPSF/IUDF CRS NGN ASF PS 1. Aggregation and configuration of user profiles 2. Recommendation trigger/request ETSI ETSI TS 182 028 V3.5.1 (2011-02) 52 3. User profile updates UE UPSF/ IUDF SD&S CFIA CRS 5. Content consumption updates NGN ASF PS 6. Content consumption updates 4. Content updates Aggregation and configuration of user profile 1. User profile updates 2. Figure 23: Aggregation and configuration of user profile Aggregation of metadata for content recommendations: 1) User can update his preferences and profile at the chosen time. 2) The updates are incorporated into the user profile. 3) User Profile data is pushed to the CRS. 4) BTV and CoD asset metadata is pushed to the CRS. 5) User consumptions of CoD or BTV content is pushed to the CRS. 6) User consumptions of BTV channels and optionally time on the channel is pushed to the CRS. NOTE 1: Steps 3 to 6 are illustrated in the push mode. Alternatively, CRS can pull this information in the pull mode. UE UPSF/ IUDF SD&S CFIA 3. Request recommendations for multiple services CRS NGN ASF PS 1. Acquisition of SD&S information 2. Profile Check 5. Service offers with personalised recommendations 4. List of recommendations Recommendation request and delivery 6. Service navigation 7. Request recommendations for selected service 8. List of recommendations 9. Service selections with personalised recommendations Figure 24: Recommendation request and delivery Recommendations Request and Delivery 1) UE requests SD&S information from SD&S. 2) SD&S verifies user profile from IUDF/UPSF. The location of IUDF/UPSF and data model, e.g. centralized or federated is described in clause 9. 3) If service selection is included into CFIA then CFIA can optionally request CRS recommendation in addition to SD&S services according to the user profile. ETSI ETSI TS 182 028 V3.5.1 (2011-02) 53 4) CRS returns recommendations for multiple services according to user profile, e.g. recommendations for bTV, CoD. 5) Personalized service offers with recommendations are returned to the UE. 6) User navigates through IPTV services. 7) CFIA requests CRS recommendation for user selected service. 8) CRS returns recommendations for the selected service according to user profile. 9) Service options with personalized recommendations are delivered to the UE. NOTE 2: The service delivery itself is not affected by the service recommendations. 11.10 Advertising NGN Integrated IPTV Advertising (Ad) service supports the following procedures: 1) Targeted ad insertion: Ad content is provided to the UE during the IPTV CoD or bTV session based on the user profile (user preference, historic metadata, location information, presence state). The ad content is provided at the predefined time or place: e.g. during commercial breaks on BTV channels, during PAUSE in the trick mode or as pre-roll/post-roll for CoD asset. 2) Interactive Advertising (push/pull): Advertising content offered to the user (e.g. red button) and triggered by the UE selection. The UE may be able to interact with some content. 3) Regionalized/localized Ad-insertion: Ad content (local or regionalized) is inserted into the IPTVbroadcast stream without targeting specific users or user groups. However, it may be targeted to regions or zones depending on network topology. If targeted advertising is supported, the targeting could be towards individual users or specific user groups. Targeted advertising may be based on multiple criteria, e.g. user profile, preference, presence information, watched content, shopping habits, location. Advertising can contain user actions, e.g. to allow user purchasing advertised content, services or take other actions. 11.10.1 Advertising procedures Ad insertion implies that an IPTV session exists prior to the insertion time. The targeted ad is selected by the ADSS (Ad Selection Service). The following ad insertion opportunities exist for multicast (e.g. bTV) and unicast (e.g. trick modes, CoD, nPVR, tsTV) based services. Ad insertion opportunities for unicast based services: 1) Pre-roll (a placement opportunity preceding an entertainment asset). 2) Post-roll (a placement opportunity following the play out of an entertainment asset). 3) Interstitial (a placement opportunity occurring during the play out of an entertainment asset). 4) Pause (placement opportunity as a result of a subscriber pressing the pause button). 5) Overlay (overlay triggers, e.g. overlaid red button triggering interactive ads). Ad insertion opportunities for multicast based services: 1) Ad breaks (placement opportunity typically indicated by in-band ad-insertion markers within IPTV content, which is allowed to be replaced by ads). 2) Overlay (overlay triggers, e.g. overlaid red button triggering interactive ads). 3) Interstitial (a placement opportunity occurring during the play out of an entertainment asset). ETSI ETSI TS 182 028 V3.5.1 (2011-02) 54 The ad insertion can be performed at either UE side or MF side: • When UE performs ad insertion, it is informed or determines ad insertion opportunity, receives both IPTV content and ad content, and renders them in a sequential or simultaneous way. • When MF performs ad insertion, it is informed or determines of ad insertion opportunity, retrieves ad content and delivers the combined stream to the UE. The major steps of TAI are as follows: • Placement opportunity detection. • Ad content selections. • Ad content delivery and presentation. 11.10.2 Network side unicast based advertisement This clause defines network side advertisement procedures for pre-roll, post-roll and pause ad placement opportunities discussed in clause 11.10.1. Figure 25 presents network side pre-roll and post roll advertisement procedure for unicast based services. The procedure is applicable for the following services: • Content on Demand. • Network PVR. • Time-shift TV. UE RACS MCF/ MDF UPSF/ IUDF CFIA 2. User Profile 4. Ad Request IPTVC 1. Content Selection 6. Instruct to create personalised play-list 9. Unicast Session Setup ADS 3. 5. 7. 8. Acknowledgement and personalised playlist Figure 25: Pre-roll and post-roll advertisement for unicast based services. 1) User selected a content following SD&S procedure discussed in clause 6.3. 2) CFIA optionally requests current profile in order to request an ad. 3) UPSF/IUDF returns current profile. 4) CFIA requests personalized ads from ADS. 5) ADS returned content identifiers for personalized ads. ETSI ETSI TS 182 028 V3.5.1 (2011-02) 55 6) CFIA requests MCF(s) to create personalized play lists containing main selected content and ads. Optionally trick mode operations can be disabled for ads sat the time of play-list creation. 7) MCF confirms creation of the play-list. 8) CFIA returns name of the personalized play-list in the asset URL. 9) UE initiates unicast session setup. Normal procedure for corresponding service type (e.g. CoD, nPVR) applies. Figure 26 presents advertisement "on pause" for unicast based services. The procedure is applicable for the following services: • Content on Demand. • Network PVR. • Time Shift TV. • Trick Modes on Broadcast TV when the channel is delivered via unicast. Figure 26: "On pause" advertisement for unicast based services 1) User selected a content following SD&S procedure discussed in clause 6.3 and starting interactive session. 2) User paused content session. 3) Pause triggers MCF to request personalized ad from CFIA. 4) CFIA optionally requests current user profile in order to request an ad. 5) UPSF/IUDF returns current profile. 6) CFIA requests personalized ads from ADS. 7) ADS returned content identifiers for personalized ads. 8) CFIA returns to MCF one or more ad identifiers. 9) MCF instructs MDF to play ads. Ads are being played. 10) User requests to continue content session. ETSI ETSI TS 182 028 V3.5.1 (2011-02) 56 11) Play request triggers MCF/MDF to stop playing ads. 11.10.3 Advertising procedures using notification Same procedures as described in clause 11.9.1 may be applicable for delivering advertising to UE. 11.11 Procedures for inter-destination media synchronization 11.11.1 Mapping 1: SC in UE Figure 24 provides an overview of the information flows for inter-destination content synchronization according to Mapping 1 from clause 5.3.1.1.2. UE (SC) IPTV-C (session oriented part of MSAS) 1. Sync Initiation Request (IPTV Content Identifier, SyncGroupId) 2. Sync Initiation Response (MSAS address) 3. Sync Status Information 4. Calculate sunc settings 5. Sync Status Instruction 6. Sync Termination Request 7. Sync Termination Response Repeat MSAS, (media- oriented part) MSAS Figure 27: Procedure for inter-destination content synchronization 1) The UE (SC) sends a synchronization initiation request to the IPTV Control (MSAS), indicating that it wants to participate in the inter-destination synchronization process. The request includes the IPTV content identifier, 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. 2) The IPTV Control confirms its participation in the inter-destination synchronization process. The response also includes the address of the media-oriented part of the MSAS. 3) The UE (SC) sends its synchronization status information to the media-oriented part of the MSAS. , using the address obtained in step (2). NOTE: Direct intra-MSAS communication may be possible, but it is out of scope of the present document. 4) The media-oriented part of the MSAS aggregates synchronization status information from multiple UEs (SCs) and calculates the appropriate synchronization settings for each SC. NOTE 2: Examples of algorithms to calculate the synchronization settings instructions from collected synchronization status information may be found in [i.1]. 5) The media-oriented part of the MSAS sends a synchronization settings instruction to the UE (SC). ETSI ETSI TS 182 028 V3.5.1 (2011-02) 57 Steps 3) to 5) may be repeated at regular time intervals. 6) 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. 7) The IPTV Control confirms the termination of its 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. 11.11.2 Mapping 2: SC in Transport The procedures according to Mapping 2 from clause 5.3.1.1.2 are the same as above with the following changes: • Tunnelling over the Ct2 reference point is not applicable. • The MSAS is an elementary function of the IPTV Control or a stand-alone Application Server. • The SC is an elementary function of the Transport Functions. • The request in step (1) includes a media stream identifier. • The SyncGroupId may be used to identify multiple synchronization 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 in Mapping 1, with the appropriate media stream identifier in Mapping 2. 11.12 Service continuation This clause discusses procedures for service continuation. 11.12.1 Procedure for unicast service continuation between NGN IPTV UEs Figures 28 and 29 present procedure for unicast based service continuation between NGN IPTV UEs. The procedure is applicable for the following services: • Trick modes on broadcast TV. • Content on Demand. • Time-shift TV. • Network PVR. Service continuation contains two stages - pause and restart. ETSI ETSI TS 182 028 V3.5.1 (2011-02) 58 Service Pause Procedure: UE1 RACS MCF UPSF/ UDAF SD&S and CF IPTV apps 2. Interactive Media Delivery 5. Service Transfer Request (asset bookmark) 4. Pause of Media Delivery IPTVC 1. Content Selection and Unicast Session Setup 3. Session Transfer 7. Session Termination and Resource Release 6. Asset Bookmark Figure 28: Unicast based service pause 1) Content Selection and Unicast Session Setup. Normal procedure for corresponding service type (e.g. CoD, nPVR) applies. 2) Interactive media delivery. 3) Session transfer decision. 4) UE optionally puts video session on hold. 5) UE requests CFIA to put the service on hold passing asset bookmark containing current play time. 6) CFIA attached asset bookmark to the service profile for later restart. 7) Session is terminated between UE and MF. Normal session termination procedure for corresponding service type (e.g. CoD, nPVR) applies. Service Restart Procedure: Figure 29: Unicast based service restart 1) UE requests CFIA to restart service (e.g. CoD, nPVR, tsTV session). 2) CFIA requests user profile foe the available paused assets. 3) CFIA returns assets available for restart, asset URLs and bookmarks UE. ETSI ETSI TS 182 028 V3.5.1 (2011-02) 59 4) UE initiates unicast session setup. Normal procedure for corresponding service type (e.g. CoD, nPVR) applies, Content delivery is requested from the paused position. 11.12.2 Service continuation between fixed NGN between fixed NGN Integrated IPTV UE and 3GPP mobile UE Figure 30 presents procedure for session continuation between fixed NGN IPTV UE and 3GPP PSS based Streaming Service. 1. Get CoD Offers UE1 3GPP PSS Portal UPSF/ UDAF/ IUDF CFIA IPTV AS 10. Asset Identifier, NPT offset 9. Request paused assets 2. CoD catalog (asset URLs) IPTV- C 3. Video session setup 11. List of paused assets 6. Acknowlegement 5. Pause session (Asset Identifier, NPT offset) PSS-SCF 3GPP MSC 3GPP Mobile TV MF UE2 TISPAN 4. Pause 7. Release session 13. Nominated MF 8. Acknowlegement IPTV MF 12. Establish CoD session 14. Establish CoD session with NPT offset 15. Video NOTE: PSS - Packet-switched Streaming Service. Figure 30: Procedure for session continuation between TISPAN NGN Integrated IPTV UE and IMS based 3GPP mobile UE Session Pause: 1) 3GPP UE1 requests CoD offers. 2) CoD offers are returned to the UE1. 3) UE1 sets up video delivery session. 4) User decides to restart the video later. 5) UE requests to pause session to be restarted later. 3GPP PSS-SCF passes asset identifier and NPT time offset to be included into the user profile. 6) Session pause is confirmed to the UE. 7) The UE1 releases CoD session. 8) Session release confirmed to the UE1. ETSI ETSI TS 182 028 V3.5.1 (2011-02) 60 Session restart: 1) IPTV UE2 requests PAUSED assets from CFIA. 2) CFIA requests the assets from the user profile. 3) CFIA passes list of paused assets to the UE2. 4) UE2 selects the asset and requests IPTVC to establish a video session. 5) IPTVC selected MF and informs the UE2. 6) UE2 requests selected MF to start video delivery from the pause position. 7) Video is delivered using CoD session. 11.13 Remote control of IPTV services 11.13.1 Procedure for Remote Mobile Control of IPTV (Provisioning) Figure 31A presents procedures for provisioning aspects for remote control of NGN IPTV services. 1. UE1 IPTV UE2 remote NGN ASF Mobile SCF 7. 4. 5. CFIA Common NGN ASF Notifications 6. 2. 3. 8. Figure 31A: Binding mobile terminal to IPTV account Device binding: 1) UE (user) requests to bind new mobile device to IPTV account through CFIA. 2) The CFIA notifies common NGN notifications about binding. 3) Common NGN ASF (Notifications) asks to the Mobile Service Control Function to acknowledge the binding. 4) The Mobile SCF sends an SMS requesting confirmation from the mobile device being bound. 5) The remote UE (e.g. mobile) confirms binding. 6) The Mobile SCF acknowledges to the Common NGN ASF (Notifications). 7) The Common NGN ASF (Notifications) registers the binding internally, and acknowledges to the CFIA. 8) End user receives confirmation to IPTV UE. ETSI ETSI TS 182 028 V3.5.1 (2011-02) 61 Figure 31B: Acquisition of content profiles Acquisition of content profiles: 1 and 2) The CMS updates the external NGN ASF Mobile SCF about CoD Catalogue (e.g. via push operation). 3 and 4) The SD&S updates the external NGN ASF Mobile SCF about EPG (e.g. via push operation). 5 and 6) The NGN ASF Mobile SCF requests updates about PPV offerings available to the UPSF (e.g. via a pull operation). 11.13.2 Procedure for Remote Mobile Control of IPTV (Operations) Figure 32A presents operational aspects for remote control of NGN IPTV services. Figure 32A: IPTV Content Purchase from remote UE Content purchase: 1) Remote UE, e.g. mobile UE, selects content and requests purchase. 2) If the content is IPTV content, purchased content is reflected in the IPTV user profile. The content purchased is available immediately, after the profile update, for playback on the IPTV UE. 3) IPTV profile update is acknowledged to the Mobile SCF. 4) Mobile SCF acknowledges successful content purchase to the remote UE. ETSI ETSI TS 182 028 V3.5.1 (2011-02) 62 Figure 32B: cPVR management from remote UE Mobile cPVR management: 1) Mobile UE schedules a recording on the remote IPTV UE. 2) The request is passed by Mobile SCF to common NGN ASF (Notifications). 3) The Common NGN ASF (Notifications) targets the appropriate IPTV UE and sends the recording notification. The IPTV UE schedules recording operation and reports back to the notification service the acknowledgement. In this case, the recording operation will be performed onto the IPTV UE local storage. 4) The acknowledgement is reported back to Mobile SCF. 5) Mobile SCF acknowledges recording schedule. 11.14 Personalized Channel Personalized Channel (PCh) service allows user to define and watch one or multiple pre-configured/scheduled content items as a single (virtual) channel. Personalized Channel information is stored in the user service profile (PCh information). Figure 33: Overview of PCh service procedures UE CFIA 3. PCh Configuration 9. PCh service Termination 4. PCh event based on schedule 2. Request authorization 5.PCh initiation REPEAT 1. PCh Service request (purchase & setup) 3. PCh Configuration confirmation ETSI ETSI TS 182 028 V3.5.1 (2011-02) 63 1) User selects and purchases content for PCh, e.g. from the offers provided by SD&S. UE requests Customer Facing IPTV Applications to setup PCh service. 2) CFIA checks service access authorization with UPSF/IUDF. 3) User defines and configures personalized channel with one or more content items discovered via SD&S, e.g. define name for the channel, items on the channel, order, time when each item should be played. Channel definition is confirmed to the UE. 4) Optionally, PCh event (e.g. start of the channel or playout of the new scheduled content item) may trigger CFIA notification to the UE, e.g. via notification. 5) CFIA initiates PCh service towards IPTV-C based on service logic, PCh schedule and user availability to watch personalized channel. 6) IPTV-C reserves required resources. 7) IPTV-C notifies MCF to start delivery of the personalized content from MDF. 8) MDF delivers the content to UE on Xd interface. NOTE: Content could be controlled as for any CoD service via Xc reference point. 9) PCh can be terminated either by MCF or UE. MCF may terminate PCh when all the content on the channel has been delivered to the UE, or when the channel or user subscription has expired. 11.15 Time Shift TV The Time Shift TV (tsTV) service allows user to view a programme content that has already been broadcasted. In order to enable tsTV IPTV SP needs to record a programme/content in the MDF. IPTV SP may limit BC content available for tsTV. Timeshift TV service is similar to nPVR. However, it is not necessary for the user (e.g. IPTV UE) to indicate in advance content be recorded. tsTV content is automatically recorded by the MDF. Timeshift TV may have expiration time for tsTV assets. The expiration time is typically different between tsTV and nPVR assets (tsTV expiration being commonly shorter, e.g. days weeks vs. months to nPVR). During tsTV service, if a program has not been finished, the UE may catch up with the live broadcasted programme (similar to Media broadcast with trick modes discussed in clause 11.3). In order to provide time-shift TV service, MDF records allowed TV programs available on the selected broadcast channels. The Time shifted TV programs is later selected by UE from EPG (BCG) via SD&S as discussed in clause 6.3.2. The user selects time shift content from the information provided by the SD&S similarly to other CoD content. Consequently, initiation and termination of time-shift service should follow CoD procedures described in clause 11.2. 11.16 PVR service This clause describes PVR service. In order to provide PVR service, the UE initially selects content from SD&S (EPG/BCG) and requests recording via customer facing IPTV application. Content is recorded in the MDF for nPVR or directly in the UE for cPVR. NOTE: A specific type of cPVR service can be identified - local PVR. The difference between client PVR and local PVR is the use of IPTV service control functions for recording management, e.g. IPTV CFIA may send notifications regarding the recording of specific content to UE, which then acts upon it for cPVR. Optionally network resources can be allocated following specified procedures, e.g. for broadcast TV. For the local PVR the recording is controlled by the UE independently of IPTV service control functions. The UE manages recording based on local or external EPG information. After the recording has been initiated, UE may request either from CFIA (or from local storage) a list of scheduled and recorded content. ETSI ETSI TS 182 028 V3.5.1 (2011-02) 64 nPVR can support both coupled and decoupled mode. In the coupled mode, client is allocated precise disk quota on a selected MDF. The MCF associated with the MDF is always selected for interactive control over nPVR services. In decoupled mode of nPVR service, statistical optimizations are possible, e.g. only one or small number of content copies may be created and users are redirected to the nearest copies via Ct2 interface. The nPVR service initiation or content delivery's procedures shall comply with CoD or time-shift TV procedures defined in clause 11.2. An MDF can only provides to the UE recordings of nPVR programs available (scheduled and recorded) from the same MDF. 11.17 Emergency alert As discussed in the service level requirements [1], the IPTV architecture shall enable delivery of emergency alert notifications based on different aspects, e.g. type of emergency situation, priority, and locality. IPTV integrated subsystems may also required secure mechanisms to acquire, verify and inject alert content, e.g. alert message or emergency live transmission, after verification of the source. The emergency alerts shall immediately and with minimum delay be delivered to the UE. An interruption of active content may be required: • There are three basic procedures for delivering emergency alert to UE: Using dedicated broadcast channel for emergency alert delivery. The UE shall receive the emergency channel for the duration and in parallel to other IPTV service. The delivery mechanism shall comply with linear TV procedure described in Clause 11.1. The notification message format shall comply with the notification schema defined in clause A.4 [14]. • Using notification procedure for message delivery with delivery confirmation. The notification shall follow procedure defined in clause 11.8.2. The notification message format shall comply with the notification schema defined in clause A.4 [14]. • Using advertising procedure for stream insertion or replacement of currently watched content. The procedure for including emergency content shall follow generic advertisement procedure defined in clause 11.10 for delivery live emergency transmission. NOTE: Emergency alert capability can be subject to local or regional regulation. 11.18 Content Bookmark An IPTV Content Bookmark service consists of two main steps: • creation of IPTV Content Bookmark: allows a user to create and store configurable pointers to content, e.g. entire or parts of content (favourite scene) to be able to quickly access the content • retrieving of IPTV Content Bookmark: allows to exchange and share IPTV favourite data. Figure 33 provides an overview of IPTV Content Bookmark creation and retrieval. This procedure is applicable at any time during IPTV session (e.g. during BC, CoD, nPVR session) or at the SD&S stage (e.g. EPG browsing). ETSI ETSI TS 182 028 V3.5.1 (2011-02) 65 Figure 34: Creation, storage and retrieval of IPTV Content Bookmark 1) The UE requests CFIA to create Content Bookmark and optionally supplies additional data (e.g. description). The bookmark data may include content information. 2) The CFIA may check user profile prior to creating content bookmark. CFIA creates bookmark and generates a unique content bookmark ID. Content Bookmark may be stored in user profile. 3) The CFIA may inform SD&S about the Content Bookmark creation and update SD&S metadata. 4) The CFIA confirms creation and successful storage of Content Bookmark data. 5) The UE sends to CFIA request for retrieval Content Bookmark. 6) The CFIA requests Content Bookmark and generate response including content identification, pointer to the bookmarked position, additional metadata. The information should be sufficient to initiate content delivery from the bookmarked position. 7) The CFIA send content bookmark to UE. 11.19 Interactive TV procedures Personalized interactive IPTV services and interworking with external ASFs (as discussed in annex A), e.g. with external application, is supported via: 1) Common NGN ASF, for interactions between IPTV and: - other NGN services as defined in [1]; - other TISPAN service level subsystems, e.g. IMS; - other non TISPAN services, such as Internet. 2) OSA/Parlay/Parlay X SCS, for interactions between IPTV and Parlay services. 5. IPTV Content Bookmark retrieving request 7. IPTV Content Bookmark retrieving response UE CFIA MF User profile SD&S 2. Check rights, user profile and store Content Bookmark 3. Add CM metadata to SD&S 4. IPTV Content Bookmark creation response SD&S service selection or consumption of IPTV content 6. Acquire Content Bookmark ETSI ETSI TS 182 028 V3.5.1 (2011-02) 66 Any defined IPTV service may be part of interactive personalized TV service (e.g. in combination with presence, messaging). Interactive TV service may be a combination of existing TV service and external application. High level procedure, which is applicable to: • Interactive TV (e.g. interactive advertising, shows). • Games. • Pictures. • Educational services (quiz, tests). • Voting. • TV shopping. • Chatting. • Maps. • Community and Social network services. • Internet widgets (e.g. via RSS feed for informational portals with weather, news, horoscopes, stock information, etc.) is presented in figure 35. UE UPSF/ IUDF CFIA & SD&S External ASFs Common NGN ASF UEs 2. Check user profile & authorization 1. Start Interactive IPTV service 5. Interactive TV application 6. Terminate Interactive TV application and release resources 3. Initiate Interactive TV application 4. Start Interactive IPTV service response Figure 35: Personalized Interactive TV applications 1) UE discovers interactive IPTV application via SD&S and request service initiation from CFIA. 2) CFIA optionally checks user profile, requests authorization and information for service personalization. 3) CFIA requests Common NGN ASF to setup interactions with external ASFs, if external ASFs are used. 4) CFIA replies to the UE optionally attaching information for initiating and using interactive TV service. 5) UE initiates personalized interactive IPTV service, e.g. interacting with application or with other users. 6) UE requests termination of Interactive IPTV application. CFIA releases all resources allocated for the interactive TV applications. ETSI ETSI TS 182 028 V3.5.1 (2011-02) 67 Annex A (informative): Interactions between other TISPAN services and IPTV services This approach assumes that service interaction are based on a dedicated Application Server Function (called common ASF) that may explicitly implement the blended service functionality (e.g. pausing the TV on incoming call, e-mail notifications, incoming call notifications). Such an ASF can be seen as an NGN Application with respect to the TISPAN IPTV architecture. As shown on figure A.1. Common NGN ASF provides interactions between IPTV: • other NGN services as defined in [1]; • other non TISPAN services, such as Internet; • with other TISPAN service level subsystems, e.g. between IPTV and IMS. A common ASF can be used for delivering customized notifications from multiple service domains (notification sources), e.g. IMS-IM, IMS call alert, emergency notification, SMS message, e-mail alert, RSS feed, other to IPTV UE. The notifications could be delivered to the UE based on user profile, location, presence and may require response from the UE as shown on figure A.1. A common ASF can be used for presence, e.g. presence server as discussed in annex C. Figure A.1: Interactions between IPTV and other NGN applications and services NOTE: Such interactions are based upon existing interfaces. A.1 Interactions 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.2] and ES 202 504 [i.3]. ETSI ETSI TS 182 028 V3.5.1 (2011-02) 68 The OSA SCS acts as a secure gateway between the underlying network and the application with the OSA architecture, e.g. 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. Figure A.2 shows a simplified version of NGN integrated IPTV architecture, with interfaces to an SCS and subsequent external applications. Figure A.2: Interaction between TISPAN Integrated IPTV and an OSA/Parlay/Parlay X SCS ETSI ETSI TS 182 028 V3.5.1 (2011-02) 69 Annex B (informative): Interaction procedure between IPTV and other service level subsystems This clause provides interaction procedure between IPTV and other service level subsystems, e.g. IMS, for composite services. The flow assumes that users are registered in IMS subsystem. The procedure describes multimedia and communication features in converged NGN IPTV applications: caller ID on the TV screen User 1 calls User 2 and both are in IMS domain. User 2 is subscribed to a converged IPTV service - caller ID notification with options to accept, forward or reject incoming call when another IPTV service is active via the IPTV UE. The clause presents generic functional steps and does not mandate placement of functions. DRM functions are not included. 7. 12. S -CSCF can forward INVITE to User 2 home UE 1. Originating c all from User 1 to User 2 2. S - CSCF accesses User 2 profile 4. Check IPTV profile, IPTV presence 10. User 2 accepted the call 11. Call accepted 3. Call invitation is delivered to common NGN ASF 5. Optional request of IPTV profile data (if n ot readily available) 8. 6. Optional return of IPTV profile data 9. Deliver call line ID to the UE Core IMS IPTV UE User 2 IPTV IUDF NGN UDAF UPSF User profile IPTV ASF NGN ASF IMS S CSCF IMS UE IMS UE Core IMS Figure B.1: High level interactions procedure between IPTV and other service level subsystems - IMS/IPTV inter-working 1) User 1 initiates a call to user 2 from his IMS device UE1. After traversing through the IMS CSCF chain invitation (e.g. SIP INVITE) is delivered to the S-CSCF for User 2. 2) S-CSCF access user profile data. Dotted arrows indicate that IMS user profile has been requested from UPSF. 3) S-CSCF, based upon IMS user profile, sends the invitation on ISC interface to common NGN ASF-. The NGN ASF is an Application Server Function. Optimizations are possible, e.g. a timer in S-CSCF can automatically deliver call upon no response. 4) NGN ASF checks IPTV user profile: a) either by requesting IPTV sub-profile of federalized user profile from NGN IUDF; b) or directly from IPTV subsystem from IUDF. ETSI ETSI TS 182 028 V3.5.1 (2011-02) 70 5) NGN IUDF optionally request IUDF for IPTV profile. 6) IUDF returns requested information. 7) IPTV user profile information is returned to NGN ASF. 8) NGN ASF, based on IPTV user profile and presence, delivers incoming call notification either to the IPTV ASF (Customer facing IPTV application) or directly to the IPTV UE. In the first case steps 9) and 10) are optional. Common NGN ASF and other ASF can be located separately, co-located or can be deployed as application package. They are shown separately to cover generic case. 9) IPTV ASF invokes IPTV application to show call line ID to IPTV UE2. 10) User 2 from IPTV UE chooses to answer the call on IMS UE. 11) IPTV ASF (or IPTV UE) notifies NGN ASF that the call setup can be continued. 12) NGN ASF returns invitation to S-CSCF to be delivered to User 2 IMS home device. 13) S-CSCF delivers invitation to User 2 IMS home device. ETSI ETSI TS 182 028 V3.5.1 (2011-02) 71 Annex C (informative): Presence attributes for IPTV IPTV services may be combined with the presence service capability. The following specific IPTV attributes are supported: • Broadcast TV with or without trick modes service activated. • CoD service activated. • PVR service activated. • Near CoD (nCoD). • Interactive TV service activated. The following specific IPTV attributes may also be supported: • Service currently accessed. • Content currently accessed. • Presence filtering for buddy list members. • Buddy list management. It is up to user's decision to include specific IPTV attributes in Presence document. Service level requirements [1] require that IPTV solution should be able to access and provide presence information. It is outside the current release to evaluate whether there is sufficient access to the presence service (i.e. the attribute described) for integrated IPTV subsystem. ETSI ETSI TS 182 028 V3.5.1 (2011-02) 72 Annex D (informative): Possible evolution path for NGN Integrated IPTV This annex considers possible migration scenarios from existing solutions (i.e. DVB-IPI, ATIS-IIF) or between NGN based IPTV architectures. D.1 Evolution of IPTV architectures towards NGN For evolution considerations, each evolutional step provides additional functionality and features for additional values IPTV services. For example, it could be the Quality of Experience (QoE) for the end users, convergence TV with other telecommunications features and interactive multimedia services. An efficient introduction of new services and reduction of the operating costs may be another important motivation to evolve the IPTV systems (as shown in figure D.1). NGN Converged IPTV Combination of NGN-Integrated and IMS-based IPTV in a single architectural framework NGN IMS based IPTV Introduces interfaces to NASS, RACS and user profile. IPTV service ocntrol is based on IP Multimedia Subsystem, integration into TISPAN NGN via IMS Non-NGN IPTV IPTV solutions including applicatiuons., service conmtrol and media delivery with integration with NGN NGN Integrated IPTV Introduces interfaces to NASS, RACS and user profile. Evolution of NGN dedicated IPTV, integration into TISPAN NGN, interworking & integration with IMS Figure D.1: The potential IPTV evolution paths for NGN based IPTV architectures In comparison with proprietary Non-NGN IPTV solutions, NGN integrated IPTV can provide standardized IPTV services and features with standardized IPTV control and media delivery functions. NGN based IPTV in both cases enables the integration with User Profile Server Function (UPSF), Network Attachment Subsystem (NASS), Resource and Admission Control Subsystem (RACS) to realize personalized value-added IPTV features and to use network resources more efficiently. Evolution towards NGN IMS based IPTV is based on the observation that IMS may be used as a unified service control platform for some of the NGN services, consequently it can be used for IPTV control. NGN based IPTV can either be based on IMS (IMS based IPTV) or interwork with IMS (NGN integrated IPTV). However, we cannot expect that all NGN services in the future will be only IMS based. Therefore convergence, combination or interaction of IMS with IPTV features can lead to NGN converged IPTV, which can be foreseen in the future as common architecture framework (NGN converged IPTV) for coexistence between NGN Integrated IPTV, IMS based IPTV and new NGN services and subsystems. ETSI ETSI TS 182 028 V3.5.1 (2011-02) 73 D.2 Possible migration and switch over scenarios This informative annex discusses migration scenarios from and to NGN integrated IPTV. Table D.1: Migration and switch over scenarios Evolution step UE Transport MC&DF Service control Application Non-NGN STB Content delivery network IPTV middleware TISPAN NGN integrated IPTV UE Transport processing, NASS & RACS MCF & MDF IPTV-C/AS Interaction with IMS and other NGN subsystems CFIA, SD&S TISPAN IMS based IPTV UE Transport processing, NASS & RACS MCF & MDF IMS SCF, SSF, SDF NGN Converged IPTV architecture UE Transport processing, NASS & RACS MCF & MDF This part is for future study in TISPAN NGN IPTV architectures ETSI ETSI TS 182 028 V3.5.1 (2011-02) 74 Annex E (informative): Mapping of elementary functions E.1 Mapping between elementary functions and generic capabilities Table E.1 presents mapping between elementary functions identified in clause 5.4 and generic capabilities identified in clause 5.3. ETSI ETSI TS 182 028 V3.5.1 (2011-02) 75 Table E.1: Mapping between elementary functions and generic capabilities Elementary function Discovery & selection Service control Service interact Media control Deliver media Content protection Service Protection Content mng. & distribution Service interaction 1 network attachment X 2 registration X 3 resource management X 4 charging information X 5 service discovery X 6 service authorization X X X 7 service selection X X X 8 service initiation X X X 9 service control X 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 licensing X 29 key management X X 30 content encryption X 31 user profile/data mng. X 32 accounting/right control 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 38 Media and data confidentiality/Integrity X ETSI ETSI TS 182 028 V3.5.1 (2011-02) 76 E.2 Mapping between elementary functions and functional entities Table E.2 presents mapping between elementary functions identified in clause 5.4 and functional entities identified in clause 5.2. Table E.2. Mapping of elementary functions to functional entities Elementary function UE SD&S CFIA IPTV-C IUDF UPSF MCF MDF 1 network attachment X 2 registration X X X 3 resource management X X 4 charging information X X 5 service discovery X 6 service authorization 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 12 session initiation 13 session modification 14 session termination 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 licensing 29 key management 30 content encryption X 31 user profile/data mng. X X X 32 accounting/right control X X X 33 status/state (changes) detection/reporting X X X X X 34 common notification X X 35 messaging X X 36 presence X X 37 inter-destination media synchronization X X ETSI ETSI TS 182 028 V3.5.1 (2011-02) 77 E.3 Mapping between elementary functions and IPTV services Table E.3 presents mapping between elementary functions identified in clause 5.4 and IPTV services as defined in [1]. Table E.3: Mapping between elementary functions and IPTV services [1]. Elementary function BC CoD nPVR cPVR BCwTP UGC Push CoD Adv CRS Notif Msg Presence 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 licensing 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) x x x x x x x x x ETSI ETSI TS 182 028 V3.5.1 (2011-02) 78 Elementary function BC CoD nPVR cPVR BCwTP UGC Push CoD Adv CRS Notif Msg Presence detection/reporting 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 028 V3.5.1 (2011-02) 79 Annex F (informative): NGN integrated IPTV mapping to other IPTV architectures NGN Integrated IPTV subsystem architecture supports IPTV service level requirements defined in [1] and provides integration of new or existing IPTV solutions (such as those defined by DVB, ATIS IIF, ITU etc) into the TISPAN NGN architecture. This annex describes mapping of other IPTV architectures to NGN Integrated IPTV architecture. F.1 Mapping between NGN integrated IPTV subsystem and ITU-T non-IMS IPTV architecture Comparing ITU-T IPTV architecture [i.10] with ETSI TISPAN NGN integrated IPTV (the present document) the following mapping of functional entities can be identified: Table F.1: Mapping between ITU-T non-IMS IPTV functions and TISPAN NGN Integrated IPTV functional entities ITU-T non-IMS NGN IPTV [i.10] TISPAN NGN Integrated IPTV IPTV Application Functions 9.2.1 Customer Facing IPTV Application FE (CFIA), Service Discovery and Selection (SD&S)* (in part) IPTV Service Control Functional Block 9.3.1 IPTV Control (IPTV-C) Service User Profile Functional Block 9.3.2 User Data Function (UPSF) Content Distribution & Location Control Functions 9.4.1 Media Control Function (MCF) Content Delivery & Storage Functions 9.4.2 Media Delivery Function (MDF) Content Preparation Functions 9.2.3 Content acquisition & preparation functions Application Profile Functional Block 9.2.2 IPTV User Data FE (IUDF) Service & content protection Service & Content Protection (SCP) NOTE: The in ITU-T non-IMS NGN IPTV application functions enable to UE select and purchase content as well as provide content metadata and other information which are in TISPAN Integrated IPTV functions of Service Discovery & Selection function. Figure F.1 illustrate mapping between functional entities discussed in table F.1. ETSI ETSI TS 182 028 V3.5.1 (2011-02) 80 Figure F.1: Mappings of ITU-T non-IMS functional architecture to TISPAN NGN integrated IPTV (ITU-T Recommendation Y.1910 [i.10], figure 10-2: NGN non-IMS IPTV architecture) SD&S CFIA MDF MCF IPTV-C UPSF Content acquisition & preparation functions DRM IUDF ETSI ETSI TS 182 028 V3.5.1 (2011-02) 81 Annex G (informative): Interconnection Models supporting Mobility Capabilities TISPAN NGN integrated IPTV subsystem consider in the future releases the following scenarios for roaming and interconnection to the home network: 1) remote data access to IPTV/content provider; 2) visited - home network roaming between IPTV providers (served only from home network); 3) visited - home network roaming between IPTV providers (served form home or visited network); 4) interconnect between NGN integrated IPTV and IMS based IPTV. Scenario A: Remote IPTV user access to home IPTV SP via remote data connection The remote IPTV UE can access home IPTV SP via remote IP connection (e.g. via VPN or secure remote access). The control signalling and media delivery can reach directly Home Network IPTV SP. However, remote IP connection goes via third party IP network relying on the functionality provided by the transport control layer and without agreement between home and visited networks the QoS cannot be ensured. NOTE: This scenario is outside the scope of TISPAN for current release. Scenario B: IPTV roaming by IPTV SP in the Home Network via IPTV SP in the Visited Network (home services) In this scenario, IPTV platform is available in the Visited Network. However, it proxies service request to the IPTV SP in the home network and the content and services are delivered only from Home Network. In this scenario, the delivery of the content, metadata, service discovery, selection, service initiation, modification and termination is done from home network. It may be required from Home Network IPTV SP to provide transcoding and content adaptation to adapt media to parameters required for entering the Visited Network (alternatively this could be done at the edge of visited network). Scenario C: IPTV roaming by IPTV SP in the Visited Network with IPTV SP in the Home Network (home and visited services) As scenario B, but IPTV SP in the visited network only request content form the home network if it is not available in the visited network. Scenario D: IPTV roaming by IMS based IPTV SP in the visited network Scenarios B and C applied to the case when IPTV SP in the visited network is based on IMS. ETSI ETSI TS 182 028 V3.5.1 (2011-02) 82 Annex H (informative): SCTE based targeted advertising architecture H.1 Definitions The SCTE has defined the following advertisement system functional entities [i.6] and [i.7]: • 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 communicates placement opportunity and placement status to the ADS. The message interfaces exposed by an ADM allow for both preconfigured ad decisions as well as real-time fulfilment models. Possible ways for detection of a placement opportunity are discussed in clause 11.10. In addition, 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. H.2 SCTE-130 based Advertising Architecture Figure H.1 shows the interfaces between the SCTE-130 advertising specific entities and the TISPAN IPTV architecture. ETSI ETSI TS 182 028 V3.5.1 (2011-02) 83 Figure H.1: Interaction between TISPAN Integrated IPTV architecture and SCTE-130 functional entities The IPTV applications are interconnected with the ADS by the ADx reference points to request ad placement decision. The ADM functionality in MF is interconnected with the Ad Decision Service by the ADy reference points to request ad placement decision. As shown on figure H.1, POIS is an external entity. However, ad placement opportunities may be detected by the MF based on cues defined in [i.8]. SIS may be either exposed by IUDF or user Data. ADM located in CFIA, MF and optionally UE can coexist and are not mutually exclusive. H.3 Reference points H.3.1 IPTV Applications - SCTE-130 ADS (ADx) This reference point is used to exchange advertising related messages between an ADM in the CFIA and an SCTE-130 Advertising sub-system. ADx reference point should be used to send and receive messages from/to the ADS, POIS and SIS entities and the TISPAN IPTV Applications. The use of ADx between SCF and ADS conforms to SCTE-130-3 [i.7]. It may be a subset of SCTE-130-3 [i.7] depending on the functionality supported in the CFIA and ADS and that is declared during the discovery and registration phases. ETSI ETSI TS 182 028 V3.5.1 (2011-02) 84 H.3.2 IPTV Media Function (MF) - SCTE-130 ADS (ADy) This reference point is used to exchange advertising related messages between MF and an SCTE-130 ADS for unicast and broadcast services. ADy reference point should be used to send and receive messages from/to the ADS and the TISPAN IPTV MF. It may be a subset of SCTE 130-3 depending on the functionality supported in the MF and ADS and that is declared during the discovery and registration phases. The MF entity is interconnected with the Ad Decision service by the ADy reference point to made ad-selection and ad- placement requests for both broadcast and unicast (e.g. for interstitial, pause opportunities) services. The use of ADy between MCF and ADS conforms to SCTE-130-3 [i.7]. It may be a subset of SCTE-130-3 [i.7] depending on the functionality supported in the MF and ADS and that is declared during the discovery and registration phases. H.3.3 MF Ad Splicer - TISPAN Ad MF (ADc) This reference point is used to exchange ad streaming related messages in order to control streaming of ads by the ad splicer from Ad MF. The use of ADc between MF ad splicer and TISPAN Ad MF conforms to SCTE-130. H.3.4 IPTV User Equipment (UE) - SCTE-130 ADS (ADz) This optional 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 and the TISPAN UE. 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 SCTE-130-3 [i.7]. It may be a subset of depending on the functionality supported in the ADS and UE and that is declared during the discovery and registration phases. H.4 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. Interface between ADS and ADM is considered as a reference point in scope of TISPAN. Table H.1 describes mapping between TISPAN IPTV functional entities and SCTE functional entities. ETSI ETSI TS 182 028 V3.5.1 (2011-02) 85 Table H.1: Mapping between TISPAN IPTV functional entities and SCTE functional entities SCTE-130 entity name Role TISPAN Entity TISPAN entity role POIS Provides placement opportunities MF / External entity MF tasks from clause 11.10.1 "When MF performs ad insertion, it is informed or determines of ad insertion opportunity, retrieves ad content and delivers the combined stream to the UE." SIS Manage subscriber information relevant for Ad IUDF / User Data / External entity IUDF/User Data role is defined in clause 5.1.1. CIS Manage assets metadata SD&S / Media Preparation (Acquisition) / External entity SD&S role is defined in clause 5.1.1. Media Preparation role is defined in clause 5.1.2. ADM Provides placement opportunities based on POIS and CIS information Defines messages for Ad insertion Activities CFIA - applications and unicast TAI MF - unicast and multicast TAI CFIA role is defined in clause 11.10.2 and on figure 25. ADS Decide ad placement relative to content based on ADM placement opportunities NGN ASF entity/External entity Defined externally [i.5], [i.6] and [i.7]. ETSI ETSI TS 182 028 V3.5.1 (2011-02) 86 Annex I (informative): NGN integrated IPTV support for hybrid services The present document integrates IPTV/TV systems, e.g. defined in [2], into NGN architecture. Some of IPTV subsystems and service level requirements [1] may include hybrid services. The present document does not preclude using IP delivery for a consumer's complete IPTV service offering or for partially combined with other TV services in a hybrid service scenario. For example, a service provider may chose to offer broadcast services (e.g. broadcast TV) via an independent channel while providing interactive, download or CoD IPTV services via the IP network. NGN integrated IPTV may support hybrid delivery of IPTV services, e.g.: • Live TV delivery over external TV delivery systems such as DVB-T, DVB-S, DVB-C, DVB-H, 3GPP MBMS, other. • Other IPTV services delivered over NGN integrated IPTV such as CoD, UGC, iTV, other as defined above. Hybrid approaches can offer advantages both to the service provider and the consumer and widen the application of TISPAN NGN Integrated IPTV, e.g. where a part of the IPTV content is delivered over an independent non-IP delivery network, such as. terrestrial broadcast, direct-to-home satellite, hybrid fibre-coax or optical distribution network, which is outside of scope for TISPAN. ETSI ETSI TS 182 028 V3.5.1 (2011-02) 87 Annex J (informative): Bibliography ETSI TR 187 008: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); NAT traversal feasibility study report". ETSI ETSI TS 182 028 V3.5.1 (2011-02) 88 Annex K (informative): Change history Date WG Doc. CR Rev CAT Title / Comment Current Version New Version 26/09/08 18bTD222r2 001 R1 B NGN Integrated IPTV new features impacts 3.0.0 3.0.1 26/09/08 18bTD221r3 002 B NGN integrated IPTV - architecture & migration scenarios 3.0.0 3.0.1 05/11/08 19WTD193r1 003 B IPTV Elementary functions 3.0.1 3.0.2 05/11/08 19WTD152r2 004 F Editorial modifications of the Linear TV procedure 3.0.1 3.0.2 05/11/08 19WTD053r2 005 B WI2074_Synchronization_Architecture 3.0.1 3.0.2 05/11/08 19WTD150r1 006 F Resource release procedure in the Linear TV 3.0.1 3.0.2 CRS 001 to 006 TB approved 3.0.2 3.1.0 28/11/08 19bTD132r1 007 B IPTV Elementary functions mapping 3.1.0 3.1.1 28/11/08 19bTD175r3 008 B Recommendation service procedures 3.1.0 3.1.1 28/11/08 19bTD174r3 009 D Linear TV procedure for coupled mode 3.1.0 3.1.1 28/11/08 19bTD176r2 010 B Advertising 3.1.0 3.1.1 28/11/08 19bTD219r1 011 B Editor notes for open issues 3.1.0 3.1.1 28/11/08 19bTD134r2 012 B IPTV Service procedure using notification 3.1.0 3.1.1 28/11/08 19bTD135r3 013 B IPTV procedures for CRS and Ads 3.1.0 3.1.1 23/01/09 19tTD083r1 014 B Synchronization Procedures 3.1.1 3.1.2 23/01/09 19tTD176r1 015 C Functional architecture 3.1.1 3.1.2 23/01/09 19tTD177r1 016 C R3 tasks for MCF & MDF 3.1.1 3.1.2 23/01/09 19tTD219r1 017 F Remote control of NGN integrated IPTV services from mobile or other NGN UE 3.1.1 3.1.2 23/01/09 19tTD218r2 018 F Fixed mobile service continuation 3.1.1 3.1.2 25/02/09 20WTD094r2 019 C Procedures for User Generated Content 3.1.2 3.1.3 25/02/09 20WTD214r1 020 F Service continuation between NGN IPTV enabled devices 3.1.2 3.1.3 25/02/09 20WTD216r1 021 F Unicast based advertisement flows 3.1.2 3.1.3 CRS 007 to 021 TB approved 3.1.3 3.2.0 20/03/09 20bTD262r1 022 F Refining of the user data functions 3.2.0 3.2.1 20/03/09 20bTD102r2 023 F Non specified reference points 3.2.0 3.2.1 20/03/09 20bTD103r3 024 B Mapping of ITU-T non-IMS NGN IPTV architecture to NGN Integrated IPTV 3.2.0 3.2.1 20/03/09 20bTD104r3 025 C Supporting entities 3.2.0 3.2.1 20/03/09 20bTD105r2 026 B Procedures for Personalized Channel 3.2.0 3.2.1 20/03/09 20bTD264r3 027 B Interactions between other TISPAN services and IPTV services (support for OSA/Parlay/Parlay X 3.2.0 3.2.1 20/03/09 20bTD265r3 028 B Optimised bandwidth utilisation during CoD 3.2.0 3.2.1 Corrections to implementations of CRs 022 to 028 3.2.1 3.2.3 29/04/09 WG2-07-020r1 029 r1 B User Generated Content Procedures 3.2.3 3.2.4 29/04/09 WG2-07-022r1 030 r1 B Synchronization Procedures 3.2.3 3.2.4 29/04/09 WG2-07-037r3 031 r3 B IPTV services R2/R3, M/O 3.2.3 3.2.4 29/04/09 WG2-07-038r1 032 r1 B Time shifted TV 3.2.3 3.2.4 29/04/09 WG2-07-039r3 033 r3 B Personal Video Recording service 3.2.3 3.2.4 29/04/09 WG2-07-040r1 034 r1 B Pay Per View 3.2.3 3.2.4 29/04/09 WG2-07-041r2 035 r2 B Emergency Alert 3.2.3 3.2.4 29/04/09 WG2-07-042r1 036 r1 B Content Bookmarks 3.2.3 3.2.4 29/04/09 WG2-07-065r1 037 r1 D Editorial clarifications 3.2.3 3.2.4 29/04/09 WG2-07-066r1 038 r1 F Review of editor's notes 3.2.3 3.2.4 29/04/09 WG2-07-067r1 039 r1 B Ss' reference point 3.2.3 3.2.4 29/04/09 WG2-07-044r1 040 r1 B Update of annex 3.2.3 3.2.4 29/04/09 WG2-07-045r2 041 r2 B Interactive IPTV services 3.2.3 3.2.4 29/04/09 WG2-07-046r2 042 r2 B IPTV interconnection 3.2.3 3.2.4 11/06/09 21WTD180r1 043 R1 B Emergency notifications using multicast 3.2.5 3.2.6 11/06/09 21WTD184r1 044 R1 B Hybrid services 3.2.5 3.2.6 11/06/09 21WTD181r1 045 R1 D Review of Editors note 3.2.5 3.2.6 11/06/09 21WTD185r1 046 R1 F Service & content protection 3.2.5 3.2.6 11/06/09 21WTD179r4 047 R4 B SCTE based advertising architecture 3.2.5 3.2.6 11/06/09 21WTD049r4 048 R4 B IPTV Security 3.2.5 3.2.6 11/06/09 21WTD131r3 050 R3 B Synchronization Identifier 3.2.5 3.2.6 Publication 3.2.6 3.3.1 Input Draft 3.3.1 3.4.0 05-02-10 02(10)0010r3 051 C Functional_Modification_of_Sync_Architecture 3.4.0 3.4.1 ETSI ETSI TS 182 028 V3.5.1 (2011-02) 89 Date WG Doc. CR Rev CAT Title / Comment Current Version New Version 14-04-10 02(10)0044r1 052 C Editorial_Corrections 3.4.0 3.4.1 Update of CR numbers and work item reference 3.4.1 3.4.2 publication 3.4.2 3.5.1 ETSI ETSI TS 182 028 V3.5.1 (2011-02) 90 History Document history V2.0.0 January 2008 Publication V3.3.1 October 2009 Publication V3.5.1 February 2011 Publication
|
86919c5cbe6ae3a9111381a9d140111c
|
181 018
|
1 Scope
|
The present document identifies the capabilities that a TISPAN NGN shall provide in order to guarantee an adequate Quality of Service (QoS) to the media flows and it defines the specific requirements for an NGN environment related to the identified capabilities. The present document defines requirements for a TISPAN Release 2 NGN. The present document does not define classes of services or values for the parameters used to define the classes of services: this work is done by other standardization bodies. The present document defines detailed requirements based on clause 4.11 in [1]. NOTE: The present document uses the term "NGN" only in the context of TISPAN.
|
86919c5cbe6ae3a9111381a9d140111c
|
181 018
|
2 References
|
The following documents contain provisions which, through reference in this text, constitute provisions of the present document. • 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. • For a non-specific reference, the latest version applies. 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. [1] ETSI TS 181 005: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Services and Capabilities Requirements".
|
86919c5cbe6ae3a9111381a9d140111c
|
181 018
|
3 Definitions and abbreviations
| |
86919c5cbe6ae3a9111381a9d140111c
|
181 018
|
3.1 Definitions
|
For the purposes of the present document, the terms and definitions given in TR 180 000 and the following apply: network probe: network element able to intercept the media flow and provide some information to the control layer QoS reporting: this mechanism identifies the ability for some network elements to collect the values of some QoS metrics of a single service instance NOTE: Example of QoS metrics could be delay, packet loss, etc. resource monitoring: this mechanism identifies the ability to monitor the topologies and resources of the transport segments controlled by RACS NOTE: Resource monitoring includes detecting the actual usage of these resources. ETSI ETSI TS 181 018 V2.0.0 (2007-08) 6
|
86919c5cbe6ae3a9111381a9d140111c
|
181 018
|
3.2 Abbreviations
|
For the purposes of the present document, the following abbreviations apply: ADSL Asymmetrical Digital Subscriber Line AF Application Function ATM Asynchronous Transfer Mode BGF Border Gateway Function BoD Bandwidth on Demand BRAS Broadband Remote Access Server CAC Call Admission Control CAC Connection Admission Control CBR Constant Bit Rate CLP Cell Loss Priority CoS Class of Service CPE Customer Premises Equipment NGN Next Generation Network OSS Operating Support Systems PCR Peak Cell Rate QoS Quality of Service RACS Resource Admission Control Subsystem TRIM Topology and Resource Information Model UE User Equipment VBR Variable Bit Rate VC Virtual Channel VP Virtual Path
|
86919c5cbe6ae3a9111381a9d140111c
|
181 018
|
4 General requirements
|
The following general requirements shall be fulfilled in a TISPAN NGN: • The NGN shall support QoS reporting mechanisms in order to indicate to the control/service/management elements (e.g. RACS, accounting functions) the QoS really achieved by the bearer flows. • The NGN shall support resource monitoring mechanisms in order to determine the available network resources (e.g. link bandwidth, port utilization, queue depth). The assumption is made that creation of the inventory of the network resources shall be done via suitable interfaces. • The NGN shall support dynamic policy provisioning mechanisms in order to allow the change on demand of the policies applied to a single user access (e.g. change the maximum bandwidth of an ADSL access). • The NGN shall support end-to-end QoS control to allow guaranteed QoS levels to be provided between connectivity end points. Several QoS classes should be supported. • In a single provider domain environment, according to the user service profile, the NGN shall be able to downgrade the QoS after a QoS degradation is detected.
|
86919c5cbe6ae3a9111381a9d140111c
|
181 018
|
5 Specific requirements
| |
86919c5cbe6ae3a9111381a9d140111c
|
181 018
|
5.1 QoS reporting
| |
86919c5cbe6ae3a9111381a9d140111c
|
181 018
|
5.1.1 Information sources
|
It is required that at least one of the following elements is able to provide QoS reporting information per service basis: • CPE/Customer Network Gateway. ETSI ETSI TS 181 018 V2.0.0 (2007-08) 7 • Border Gateway Function (BGF). • Network probes. In addition it should be possible to have also other information sources such as Access Nodes, IP edge nodes, etc.
|
86919c5cbe6ae3a9111381a9d140111c
|
181 018
|
5.1.2 Services
|
Gathering of QoS reporting information shall be provided for both session and non session based services (e.g. content based services).
|
86919c5cbe6ae3a9111381a9d140111c
|
181 018
|
5.1.3 QoS reporting information
|
QoS reporting information: • For session based services reporting at least the following information shall be provided: number of packets received, packet loss, average delay, and jitter. In addition, it should be possible to also report other quality metrics. • For non session based services reporting at least the following information should be supported: number of packets received, packet loss, number of retransmitted packets. In addition, it should be possible to also report other quality metrics. It may also be possible for the information sources to process the information gathered. For example, processing can be used to determine the urgency in reporting the information and/or to reduce the forwarding capacity needed to transfer the information or for generating aggregate information starting from raw ones.
|
86919c5cbe6ae3a9111381a9d140111c
|
181 018
|
5.1.4 Granularity
|
The granularity used by the network elements to generate the QoS reporting information shall be an operator choice on a per service basis and per information source basis. The QoS reporting may be triggered by pre-defined events, e.g. thresholds violation, during a session or a service instance. Exhaustive QoS reporting information at the end of service shall be supported (e.g. communication session, video streaming). The level of granularity shall be such that it is sufficient for purpose without causing excessive load to the requester and responder of QoS reporting, as well as the network traffic. The QoS reporting should contain a timestamp indicating the time at which the observation was made.
|
86919c5cbe6ae3a9111381a9d140111c
|
181 018
|
5.1.5 Use of QoS Reporting information
|
Use of the QoS reporting information: • The control/service/management elements that use the QoS reporting information shall be able to process the information gathered. • The QoS control layer shall be able to change the admission control and/or enforcement policies used for QoS purposes based on QoS reporting information. The policies to be changed are an operator choice and could be one or more of the following: the enforcement policies for the media flow related to the QoS reporting information; the enforcement policies for other media flows of the same user; the enforcement policies for the media flows of other users; the admission control and/or enforcement policies for a particular network segment; the admission control and/or enforcement policies for new media flows requests. • The accounting functionalities shall be able to use the QoS reporting information to enrich the CDR provided to the billing systems. ETSI ETSI TS 181 018 V2.0.0 (2007-08) 8 • The management functionalities shall be able to use the QoS reporting information for off line analysis (e.g. for planning purposes).
|
86919c5cbe6ae3a9111381a9d140111c
|
181 018
|
5.2 Resource monitoring
| |
86919c5cbe6ae3a9111381a9d140111c
|
181 018
|
5.2.1 General
|
The ability to offer end-to-end QoS control in an NGN is of fundamental importance as new services and applications with ever increasing QoS requirements become available. Management of application QoS requirements where a number of services are being provided over individual links requires knowledge of the available bandwidth on the link. In order to achieve these requirements the RACS needs to have an accurate and current knowledge of the available network resources in the transport layer, e.g. in case of a network device failure or congestion occurring this may impact on available QoS due to increased load or delays caused by re-routing. The RACS needs also to have knowledge of the status of each network component (nodes and links) under its control. This information may be held in accordance with a Topology and Resource Information Model (TRIM) and made available to RACS to provide the required information for QoS control. The sources and types of information are described in the following clauses. In general, RACS shall have knowledge of the network topology, routing information and total resource capacity including capacity in each forwarding class and shall be made aware of dynamic changes in the network (e.g. device or link failure).
|
86919c5cbe6ae3a9111381a9d140111c
|
181 018
|
5.2.2 Information sources
|
Topology, resource and routing information may be acquired from a number of different sources, including external systems such as OSS and directly from the network elements controlled by the RACS system. The information may be stored in accordance with the information model and made available to the RACS system. Resource Monitoring employs a number of different sources: primarily the Access Node and IP Edge, but where true end-to-end QoS provision requires knowledge of the number or type of CPE connections, the CPE/Customer Network Gateway must support the resource monitoring mechanism in order to monitor the whole network from CPE to BGF. The information sources are dependent on the access technologies in use. Information Sources: sources of the information shall be OSS Functions and whatever resource(s) the RACS controls. RACS may need information from one or more elements about their environment. Although information must be maintained about the whole network, aggregation may allow RACS to receive the required information from a subset of these elements. In addition to the above list it may be possible to identify other information sources (e.g. CPE) depending on the type of access network in use. Consideration should be given to a range of access architectures when identifying the possible information sources.
|
86919c5cbe6ae3a9111381a9d140111c
|
181 018
|
5.2.3 Resource Monitoring information
|
The Resource monitoring information available may vary depending on the type of resource in use. This in turn depends upon the type of access architecture involved. Some consideration also needs to be given to the types of application in use and their QoS requirements as these have an impact on the resource information required. The information are dynamically updated and stored in such a way as to be accessible to the RACS. Types of information: can be separated into three different categories: • Devices and interfaces of the physical network topology. • Routing information that describes the connectivity through the topology. • Resource availability information. ETSI ETSI TS 181 018 V2.0.0 (2007-08) 9 Within these categories there may be static and dynamic information. For instance the topology information may comprise static information acquired during the bootstrap phase, plus dynamic updates due to devices or interfaces taken out of service due to failure or for maintenance purposes etc. Routing information is potentially dynamic as it may change due to re-routing caused by network topology changes. Resource availability is initially provided as static information, but is updated dynamically with usage. Resource monitoring information: the resources monitored shall be: • Network devices (static). • Links (static). • Bandwidth available on the link (static or dynamic). • Port utilization (dynamic). • Queue depth (static). • Queue utilization (dynamic). In addition it should also be possible to monitor other information such as latency, L2 capacity, port capacity, VP capacity and VC capacity, CoS bandwidth availability where required - see clause 5.2.5. It may also be possible for the information sources to process the information gathered e.g. to reduce the overhead in the RACS. In addition RACS may be able to derive some information by processing the available data (e.g. to calculate the current available link bandwidth from the total link bandwidth figure by maintaining knowledge of the current utilization of resources).
|
86919c5cbe6ae3a9111381a9d140111c
|
181 018
|
5.2.4 Granularity
|
The granularity for providing the Resource monitoring information shall be a trade-off between the amount of information and the traffic within the network. Scalability issues need to be considered to avoid a high management overhead. Granularity: • The resource information shall be made available in a timely manner, e.g. scheduled or periodic. • The granularity used by the network elements to generate the resource monitoring information shall be an operator choice on a per resource basis and per information source basis. • The level of granularity shall be such that it is sufficient for purpose without causing excessive load to the resource or monitoring function, as well as the network traffic. • The resource information should contain a timestamp indicating the time at which the measurement was made
|
86919c5cbe6ae3a9111381a9d140111c
|
181 018
|
5.2.5 Use of resource monitoring information
|
The Resource monitoring information may be used for different purposes: primarily to provide the knowledge to the control elements to enable them to make informed decisions on what policies to apply to the network elements, but it could also be used for other purposes such as to monitor performance for fault prediction or other purposes, or for off-line management or planning purposes. Use of the Resource monitoring information: • The Resource monitoring information shall be in a suitable format to enable the control/service/management elements that use it to be able to access and process it. • The RACS shall be able to change the admission control and/or enforcement policies used for QoS purposes based on the Resource monitoring information. This should apply to the admission control and/or enforcement policies for new media flows requests. ETSI ETSI TS 181 018 V2.0.0 (2007-08) 10 • The Resource monitoring information shall be made available to other sub-systems for the purposes of performance/fault management, planning purposes, etc.
|
86919c5cbe6ae3a9111381a9d140111c
|
181 018
|
5.3 Dynamic policy provisioning
|
As a key part of an NGN's ability to offer QoS, RACS shall be able to activate and enforce existing policies governing the bandwidth available to a particular User. In addition to this, RACS shall also be able to dynamically define new policies based on information from a number of sources, including network devices and management systems, and implement these policies. This places a number of requirements on the TISPAN architecture: 1) RACS shall support provisioning and configuration of policies to be used to guarantee the requested QoS level. This includes to dynamically create/update/remove/query/activate/de-activate policies. 2) RACS should be able to control both Upstream and Downstream bandwidth resources. 3) RACS shall be able to change the Upstream and Downstream bandwidth available to a particular subscriber. Such changes may apply to all traffic classes offered to the subscriber or a subset of those classes.
|
86919c5cbe6ae3a9111381a9d140111c
|
181 018
|
5.4 End-to-end QoS requirements
|
When a user requests a service it is likely that a number of different network domains are involved in providing the service to the user. If the service is offered with a given level of QoS there must be a mechanism to pass the QoS requirements over the end-to-end path to ensure that this level of QoS is maintained. The process of end-to-end QoS control can be divided into two phases: 1) The QoS requirements are passed to the relevant network domains. 2) The network domains act on the requirements to enforce the requested level of QoS on the specific end-to-end connectivity path. Optionally a third phase could be to monitor the connectivity path to ensure the requested QoS is maintained. Requirements • The NGN shall provide a mechanism to pass per session or aggregate QoS requirements to each relevant network domain. QoS requirements may be different for the signalling and media flow paths. • The NGN shall support a mechanism to apply the end-to-end QoS requirements to the transport layer in each domain between connectivity end points. It is up to the individual domains how to ensure the QoS guarantee. • QoS Reporting mechanisms may be activated to monitor the QoS provided in each domain to ensure the end-to-end QoS is provided at the end of the service instance. Types of requirement The end-to-end QoS requirements may include one or more of the following: • Bandwidth. • Latency. • Jitter.
|
86919c5cbe6ae3a9111381a9d140111c
|
181 018
|
5.5 Charging
|
1) RACS should collect and provide charging information related to the resource reservation request, the resource modification request, the release and the abort request of the network resources. 2) RACS should collect and provide charging information related to the modification of QoS, during an active session in the intra domain and in the inter domain scenarios. NOTE: The use of RACS QoS based charging information is an operator choice. ETSI ETSI TS 181 018 V2.0.0 (2007-08) 11 Annex A (informative): Scenarios A.1 Use of sophisticated admission control algorithms Admission control schemes can be classified into deterministic schemes and statistical schemes according to the way RACS handles the QoS requirements within a request sent by an AF. Deterministic admission control schemes are characterized by worst-case assumptions, that is overbooking is prevented and reservations are based on the peak bandwidth. This approach provides a deterministic QoS to all users, but needlessly constrain the number of requests that can be granted simultaneously, and lead to an under-utilization of resources related to how bursty and variable the admitted traffic is. Statistical schemes provide a probabilistic QoS guarantee instead of deterministic one since they reserve resources based on a probability distribution of the bandwidth consumption of VBR sources, resulting in higher resource utilization due to statistical multiplexing. The risk with such approach is that bearer flows can receive downgraded quality. In the RACS you probably can implement a deterministic scheme till you manage CBR sources (e.g. voice traffic), although codec negotiation may imply under utilization of the resources since the use of the preferred codec within an offer is not mandatory. As soon as RACS manages variable bit-rate flows the waste of bandwidth caused by a deterministic approach of course increases. In that situation the RACS should probably implement a statistical method: the amount of bandwidth that a particular flow will need over a specific layer 2 technology can be determine based on a acceptable level of multiplexing and combining the peak requested bandwidth with the traffic characteristic of the flow (e.g. burstiness and packet size) RACS can be aware of for example thanks to the Reservation Class parameter in the Gq' interface. In figure A.1 four different variable bit-rate flows are shown with the same peak bandwidth but with different characteristic as regard burstiness and average bandwidth. Using a deterministic approach based on the peak bandwidth for example only two requests could be granted. Using the average bandwidth as parameter all the flows should be admitted. B2 B3 B1 B4 ? Figure A.1: Admission control for VBR flows ETSI ETSI TS 181 018 V2.0.0 (2007-08) 12 Having feedbacks of the quality bearer flows are achieving can be useful for improving RACS operating. Based on QoS reports you can, for example: • tune the threshold (e.g. overbooking factor) within the admission algorithm. Referring to figure A.1, whether two flows have been already admitted and a third request is received it could be possible to accept the third request since for the admitted flows you receive a quality report well above a warning threshold. If then the new feedback RACS receives shows that the quality is lowering it could be possible to deny the four request although, for example, looking only at the average bandwidth all flows should be admitted; • cope with variable bit-rate sources that behave differently from what is modelled within the RACS; • better deal with priority and pre-emption mechanism. For example you can decide not to pre-empt a request if the quality of the already admitted flows is over a certain threshold although you have to admit a flow with an higher priority; or you can decide to perform the pre-emption operations only when a decrease in the quality of the bearer flows is notified. A.2 L2 topology awareness and traffic management options Let is consider a RACS controlling an ATM-based access network. In order to effective perform resource management, it should be aware of the L2 topology and of the traffic management options such as congestion control mechanisms implemented. In fact such mechanisms impact on the quality of the bearer flows received no matter which traffic conditioning policies you enforce both on the IP edge an access node. Focusing on Connection Admission Control (CAC) mechanism within an ATM network different approaches can be used. The simplest form among all CAC algorithms, is the so-called Peak Bandwidth Allocation that uses only the knowledge of the PCR parameter to compare against the network available bandwidth and decide whether to accept the configuration of new connection or not. This algorithm ensures that the sum of requested resources and existing connections is bounded by the physical link capacity. but prevents any multiplexing gain among the VC and VP configured into the network. Another approach is to admit new connection allocating a bandwidth between the peak cell rate and the sustained cell rate. As a result, the sum of all the admitted connections' peak cell rates may be greater than the outgoing link capacity. If a statistical approach is used in the ATM network, RACS should be aware of it and should exactly know for example the different overbooking factors used in all the interfaces of the various ATM switches. Referring to figure A.2 in order to admit a flow from UE-1 overbooking along the path towards the IP Edge should be taken into account. Access Node IP Edge ATM Network a b c d e f UE-1 Overbooking: 150% Overbooking: 130% Overbooking: 200% Figure A.2: L2 ATM Access Network In such a scenario, if RACS can not collect all the needed information QoS reporting mechanism could help RACS to take into account the state within the ATM network without the need of gathering a lot of data and nevertheless being able to cope with all the situations. As soon as QoS reports degrade, RACS shall for example lower the available bandwidth. ETSI ETSI TS 181 018 V2.0.0 (2007-08) 13 A.3 Coexistence of managed and un-managed traffic RACS receives reservation requests only for a subset of the traffic entering the network. Situations exist where the presence of un-managed traffic may impact on the performance of the higher priority flows managed by the RACS. Let is consider the ATM access network depicted in figure A.2: over all the links (a, b, c,…) un-managed traffic can be present participating in the creation of congestion situation in which the managed traffic can be discarded although it should not according to the information available at the RACS level. A similar situation may be foreseen considering queuing and scheduling configurations in the IP Edge node. In figure A.3, a hierarchical scheduler for managing traffic entering an ATM-based access network where Virtual Circuits are multiplexed within Virtual Path is shown. The number of queues varies from one level to another: a priority queue dedicated for Voice traffic is configured at the VC level but not at the VP level. In such a scenario, if a subscriber starts a voice call, the data traffic that he sends into the network impacts on the delay and on the bandwidth available for his voice traffic. Moreover also the data traffic of other users on the same VP impacts on his voice quality. As a final remark, also the data traffic of users on other VPs on the same BRAS port can impact voice quality whether a congestion situation in the ATM network occurs and data cells have not the CLP bit set to 0. Voice Data LLQ VC PCR shaper ATM Cells HW LW VP PCR shaper WRR STM1 VP PCR shaper WRR Voice Data VC PCR shaper ATM Cells Figure 3: BRAS hierarchical scheduler According to this scenario, QoS Reporting mechanism could help RACS to be informed of the un-managed traffic entering the network under its control and accordingly react. As soon as QoS reports degrade, RACS shall for example lower the available bandwidth. A.4 Bandwidth on Demand This scenario describes a Bandwidth on Demand (BoD) service offered to a User which allows the user to boost his access bandwidth to a higher level for a limited period of time. The objective is to study the requirements on the RACS functionalities to deliver such a service. Note that charging aspects are considered out of scope for this example. The service would allow users who usually have e.g. 512 Kbps of access bandwidth available to increase this to a higher bandwidth, e.g. 2 Mbps, for a limited period of time. The service could offer a number of options: 1) Request for increased downstream bandwidth for a specified time. This would allow the user to e.g. download content at a higher rate than normal. In this case only downstream traffic would need to be boosted. ETSI ETSI TS 181 018 V2.0.0 (2007-08) 14 2) Request for increased bi-directional bandwidth for a specified time. This would allow the user to e.g. share content or take part in a video conference and enjoy an improved image and sound quality. 3) Request for increased bandwidth for a specific service which would only affect the traffic associated with that service, e.g. a "Video Boost" service. 4) Request for increased bandwidth for some specific content. Of course any of the options above (time based, service based and content based) could be combined. The service would benefit the user by allowing him to enjoy an improved QoS for a limited duration without the cost of subscribing to a permanent increase in bandwidth. The benefit to the Service Provider would be to offer a chargeable service to the user with the added incentive that the user may decide to upgrade to a higher bandwidth service on a permanent basis. The traffic affected by a bandwidth change may be all of the traffic to/from a particular subscriber or only a specific subset related to the given service requested. For example, in option (3) above only the video traffic would benefit from the newly available bandwidth. Also, depending on the service requested, bandwidth changes may have an impact on upstream and/or downstream traffic. Bandwidth rates and the services to which they apply may be explicitly requested by the user or the user may request pre-defined policies. The request could be performed through a web portal. When explicitly requesting a bandwidth rate, the user must include sufficient information to identify the traffic that should be boosted. When requesting a pre-defined policy, the user must minimally indicate the policy s/he wants to activate. In this last scenario the user/web portal may be unaware of the specific bandwidth change that RACS will apply in the network since RACS will hide this information. Figure A.4 represents an example of a possible realization of this service. 1. We assume the User CPE Network Session is already established and that the user policy can be applied. There may or may not be a default policy applied 2. A User logs into the Web Portal and selects to activate the BoD Service 3. The portal forwards the request onto the RACS 4. RACS determines whether there are sufficient resources to admit the request (assume yes) 5. A new BoD Policy Rule is applied to the Network cloud 6. RACS provides a positive response to the user via the portal RACS 5 1 3 2 6 4 6 1. We assume the User CPE Network Session is already established and that the user policy can be applied. There may or may not be a default policy applied 2. A User logs into the Web Portal and selects to activate the BoD Service 3. The portal forwards the request onto the RACS 4. RACS determines whether there are sufficient resources to admit the request (assume yes) 5. A new BoD Policy Rule is applied to the Network cloud 6. RACS provides a positive response to the user via the portal RACS 5 1 3 2 6 4 6 RACS 5 1 3 2 6 4 6 Figure 4: Bandwidth-on-Demand scenario The sequence of operations is as follows: • The user logs on to a web portal and selects the BoD service. • The Web Portal forwards the request to the RACS including an indication of quantity for bandwidth boost (this may be explicitly indicated in the request, or it is possible to reference pre-defined BoD classes). • The RACS may determine whether there are sufficient network bandwidth resources to admit the request (we assume there are). ETSI ETSI TS 181 018 V2.0.0 (2007-08) 15 • A new policy is applied in the network for the subscriber according to the quantity of bandwidth requested. • A positive response is forwarded to the user. • If the Admission Control fails, the user is notified, and no upgrade is configured. ETSI ETSI TS 181 018 V2.0.0 (2007-08) 16 Annex B (informative): Bibliography • ETSI TS 185 001: "Telecommunication and Internet converged Services and Protocols for Advanced Networking (TISPAN); Next Generation Network (NGN); Quality of Service (QoS) Framework and Requirements". • ETSI ES 282 003: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Resource and Admission Control Sub-system (RACS); Functional Architecture". • ETSI TS 182 019: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Resource and Admission Control Sub-system (RACS); Functional Architecture; Release 2". • ETSI TR 182 022: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Architectures for QoS handling". • ETSI TS 183 017: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Resource and Admission Control: DIAMETER protocol for session based policy set-up information exchange between the Application Function (AF) and the Service Policy Decision Function (SPDF); Protocol specification". • ETSI TR 180 000: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); NGN Terminology". ETSI ETSI TS 181 018 V2.0.0 (2007-08) 17 History Document history V2.0.0 August 2007 Publication
|
01ee8faf3e3b55e6b1aa35d28a018fce
|
181 016
|
1 Scope
|
The present document is to describe the Service Layer requirements for IPTV service within NGN especially focusing on the integration of IPTV services with the communication services defined in TISPAN. This work complements the working item initiated for addressing the transport layer network capabilities in order to support IPTV services. The present document is complementary to the TS 181 014 "Requirements for Network Transport Capabilities to support IPTV Services" [3]. The present document shall not preclude the service to be supported in a converged (fixed - mobile) scenario.
|
01ee8faf3e3b55e6b1aa35d28a018fce
|
181 016
|
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.
|
01ee8faf3e3b55e6b1aa35d28a018fce
|
181 016
|
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] OMA-RD-BCAST-V1_0-20090212-A: "Mobile Broadcast Services Requirements". NOTE: Available at http://member.openmobilealliance.org/ftp/Public_documents/BCAST/Permanent_documents/OMA-RD- BCAST-V1_0-20090212-A.zip. [2] ETSI TS 181 001: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Videotelephony over NGN; Stage 1 service description". [3] ETSI TS 181 014: "Telecommunications and Internet Converged Services and Protocols for Advanced Networking (TISPAN); Requirements for network transport capabilities to support IPTV services". [4] ETSI TS 182 008: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Presence Service; Architecture and functional description [Endorsement of 3GPP TS 23.141 and OMA-AD-Presence-SIMPLE-V1-0]". [5] ETSI TS 181 006: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Direct Communication Service in NGN; Service Description [Endorsement of OMA-ERELD-PoC-V1]". ETSI ETSI TS 181 016 V3.3.1 (2009-07) 8 [6] ETSI TS 122 340: "Universal Mobile Telecommunications System (UMTS); IP Multimedia Subsystem (IMS) messaging; Stage 1 (3GPP TS 22.340 version 7.0.0 Release 7)". [7] ETSI TS 181 002: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Multimedia Telephony with PSTN/ISDN simulation services". [8] ETSI TS 187 001 (V2.1.5): "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); NGN SECurity (SEC); Requirements". [9] ETSI TS 181 005: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Services and Capabilities Requirements".
|
01ee8faf3e3b55e6b1aa35d28a018fce
|
181 016
|
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 TR 180 000: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); NGN Terminology". [i.2] ETSI TS 187 005: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); NGN Release 2 Lawful Interception; Stage 2 definition". [i.3] ETSI TS 182 019: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Content Delivery Network (CDN) architecture - Interconnection with TISPAN IPTV architectures".
|
01ee8faf3e3b55e6b1aa35d28a018fce
|
181 016
|
3 Definitions and abbreviations
| |
01ee8faf3e3b55e6b1aa35d28a018fce
|
181 016
|
3.1 Definitions
|
For the purposes of the present document, the following terms and definitions apply: broadcast TV: television programming transmitted and intended for reception by anyone within range of the transmitter or lawfully connected to a cable distribution system but where the consumer has no control over the content or timing of what he receives, apart from the ability to select a particular channel NOTE: There is no interactivity between user and the service or content providers. It is sometimes referred to as "Linear TV". channel change: specific action initiated by an end-user (e.g. push remote control button) at time t0 through which the presentation of a previous channel is replaced by the presentation of the new channel of broadcast TV service, as selected by the end-user channel change time: time elapsed between the moment the end-user selects a new channel and the moment this channel is presented at the final quality level of the channel consumer: domain where the IPTV services are consumed NOTE: The consumer domain may consist of a single terminal used directly for service consumption or may be a complex network of terminals and related devices, including consumer operated mobile devices. The domain itself may also be a mobile end device. In this case, the delivery system of a transport provider would be a Wireless Wide Area Network (WWAN). A single consumer domain may be connected via two or more networks to a number of service providers obtaining content from multiple content providers. consumer network: network owned and operated by an end-user relying on the services of a transport provider for external connectivity; in this context, the definition includes home networks, wireless "hot spots", hotel networks, etc. ETSI ETSI TS 181 016 V3.3.1 (2009-07) 9 Consumer-Originated Content (COC): content generated by a user for the purpose of making it available to other users NOTE: The content may be private, or intended for a restricted audience or intended for unrestricted audience. It is the equivalent of User-Generated Content. content aggregation: aggregation of Broadcast Channels (BC) and content titles (CoD) among content and service providers Content on Demand (CoD): users can select their required content with the assistance of the Electronic Programme Guide (EPG) at the user preferred time NOTE: The content is then transmitted uniquely (unicast) to that consumer who can usually use VCR-like functionalities (for example, fast-forward, rewind or pause) to control their viewing of the content. A special form of Content on Demand (CoD) is Video on Demand (VoD). Content Provider (CP): entity that owns or is licensed to sell content or content assets downloadable applications: interactive applications downloaded to IPTV Terminal device if and when invoked by subscriber, or service provider Electronic Programme Guide (EPG): assistance tool which helps users to locate the content they want and to facilitate the selection of IPTV services for watching, recording, etc. Electronic Service Guide (ESG): enables service and content providers to describe the services and content they make available, or offer for subscription or purchase NOTE: It also enables a method for describing how to access the services. From the user perspective the ESG can be seen as an entry point to discover the currently available or scheduled services and content and to filter those based on their preferences. Furthermore, the ESG provides the entry point to interactive services. The ESG consists of both EPG and interactivity data. external content: content which the consumer acquires from a CP which is not the IPTV SP, but which is acquired via the IPTV SP NOTE 1: A business relationship needs to exist between the CP and the IPTV SP prior to the acquisition. The IPTV SP delivers the content to the consumer making use of the services capabilities provided by the NGN SP. External content may be recommended by the IPTV SP or integrated into the IPTV SP content offers. NOTE 2: The content provider role includes content brokers acting as CP and is not limited to content producers. interaction channel: logical channel for point-to-point communication through which the UE interacts with the IPTV Services interactive TV: delivers functionality beyond that generally associated with the traditional television reception where the consumer can interact with the program content interactivity data: contains information that is used by the UE to offer interactive services to the user, where the services are associated with the broadcast or on-demand content inter-destination media synchronization: synchronization of media units such that they are outputted simultaneously at different destinations NOTE: These interactive services enable users to e.g. vote during TV shows or to obtain content related to the broadcast content. IPTV Service Provider: entity that offers IPTV services to the Customers making use of the services capabilities provided by the NGN Service Provider IPTV solution: composition of functions and interfaces needed to provide the IPTV service media action data: information about actions that are performed to control the media NOTE: These actions may have been performed by the user, by network elements that constitute the IPTV solution or by external applications. ETSI ETSI TS 181 016 V3.3.1 (2009-07) 10 native applications: interactive applications that are part of the in-built software or permanently downloaded with the IPTV Terminal Device software in order to interact with the IPTV Terminal device hardware and to provide a quick response NGN Service Provider: entity that offers NGN based services which shares a consistent set of policies and common technologies near CoD: similar to CoD but sent to the user by multicast rather than unicast NOTE: Service providers often transmit the same material over several channels, each with a different start time and may decide to open channels to successive users can receive the content from whatever point it has reached when they join (much like Broadcast TV). Users can also opt to join the programme at its next scheduled start time. non-IPTV terminal device applications: web or mobile applications that interact with the IPTV system to modify the settings of the IPTV environment or extend the IPTV experience to these devices non-linear AV services: any audiovisual media services where the user decides upon the moment in time when a specific programme is transmitted on the basis of a choice of content selected by the service provider Pay Per View (PPV): offering of pay-television broadcasts to consumers in such a manner that they can make a "one-off" purchase of a particular programme event (for example, a boxing match) separately from their regular package or subscription NOTE: The programme event is shown at the same time to everyone ordering it (as opposed to a CoD programme event). Personalized Channel: particular list of programs that is scheduled on the basis of the user profile, in which each program is selected from the EPG/ESG that is available to the user, including BC channels or packages and CoD categories NOTE: Personalized Channel is equivalent to Virtual Channel or Personal Channel. Personalized Service Composition: service offering alternative streams, either alternative video streams (e.g. camera-angles), audio streams (e.g. audio languages) or text streams (e.g. subtitles), where users can select their preferred content streams for personalized consumption Personal Video Recorder (PVR): service whereby the user can store video content from Broadcast TV and replay it at any convenient time NOTE: This can be achieved using either a client device or cPVR where the storage device forms part of the consumer network or a network facility (nPVR). Consumers can lease disk space from a provider and select content for storage, as required. Recording takes place at the network server and can be downloaded at a later time as required, again using VCR-like functionality. Push CoD: service where content is pre-loaded to the IPTV terminal equipment local storage by the IPTV Service Provider based on user subscription NOTE: The user may have no direct control of what content is downloaded. The IPTV Service Provider may make the choice based on users' preferences and habits. Content is available on local storage for direct consumption by user and the user has control over viewed content. ETSI ETSI TS 181 016 V3.3.1 (2009-07) 11 Quality of Experience (QoE): purely subjective measure from the user's perspective of the overall value of the service provided NOTE: Apart from its being user dependent, it will invariably be influenced by the user's terminal device (LD or HDTV), his environment (in the car or at home), his expectations (mobile or corded telephone), the nature of the content and its importance (a simple yes/no message or an orchestral concert). Mean Opinion Score used for assessing the quality of telephone connections is a limited form of QoE measurement process, relating to a specific media type, in a controlled environment and without specific user expectations. For video, the methods of monitoring objective performance are discussed in other organizations such as ITU-T. For example, there exists related work on "FR"(Full Reference), "RR"(Reduced Reference) and "NR"(No Reference) concepts. Scalable Video Coding: video coding scheme that allows for hierarchical compression in the sense that decoding a particular layer depend on one or more enhancement layers NOTE 1: Scalability may be in three dimensions, i.e. spatial (resolution), temporal (frame rate), and quality (SNR). NOTE 2: Such encoding schemes depend on the targeted application. Depending on the context, the enhancement layers could be transmitted or filtered in any node the stream crosses, including the sender and the receiver. server-based applications: network-accessible interactive applications that are accessed via remote terminal services, for example to save on the processing and storage requirements on the IPTV Terminal equipment, these can be run externally on Interactive Application Servers service discovery: process through which the UE acquires the information about available services including location of Electronic Service Guide (ESG) Service Provider (SP): entity providing a service to the subscriber NOTE: Different types of service providers may be relevant for television services on IP, see IPTV Service Provider and NGN Service Provider. time-shift TV: facility whereby audio visual information can be stored in the network (see nPVR) whilst it is being broadcast and remain available for later viewing NOTE: The user is able to start the playback before or after the recording finishes, or use any of the usual VCR functions, as required. transport provider: entity connecting consumers and Service Providers NOTE: The delivery system usually is composed of access networks and core or backbone networks, which may use a variety of network technologies and be owned by a number of different operators. trick modes: facility to allow the user to control the playback of content, such as pause, fast and slow playback, reverse playback, rewinding, jumping forwards or backwards, playing at double speed, etc. User-Generated Content (UGC): content generated by a user for the purpose of making it available to other users NOTE: The content may be private, or intended for a restricted audience or intended for unrestricted audience. It is the equivalent of Consumer-Originated Content. VCR functions: common functionalities of a video cassette recorder, such as select/cancel, start, stop, pause (with or without freeze frame), fast forward, reverse, scan forward or reverse (both with or without image), and setting and resetting memory marks
|
01ee8faf3e3b55e6b1aa35d28a018fce
|
181 016
|
3.2 Abbreviations
|
For the purposes of the present document, the following abbreviations apply: API Application Programming Interface AV AudioVisual BC Broadcast Channels CB Content Broker ETSI ETSI TS 181 016 V3.3.1 (2009-07) 12 CBMS Convergence of Broadcast and Mobile Services CDN Content Delivery Network COC Consumer-Originated Content CoD Content on Demand CP Content Provider cPVR client Personal Video Recorder (see also PVR, nPVR) DRM Digital Rights Management DVB Digital Video Broadcasting DVB-H Digital Video Broadcasting - Handheld DVB-SI Digital Video Broadcasting - Service Information DVD Digital Video Disk EPG Electronic Programme Guide (see also IPG) ESG Electronic Service Guide FR Full Reference HD/HDTV High Definition (TV) HLFR High-Level Functional Requirement IMS IP Multimedia Subsystem IP Internet Protocol IPG Interactive Programme Guide (see also EPG) IPR Intellectual Property Rights IPTV Internet Protocol TeleVision ISDN Integrated Services Digital Network LD Low Definition (TV) LI Lawful Interception MCD Media Content Distribution nCoD near Content-on-Demand (see also CoD) NGN Next Generation Network nPVR network Personal Video Recorder (see also PVR, cPVR) NR No Reference PAP Picture and Picture PDA Personal Digital Assistant PIP Picture In Picture PPV Pay Per View PSTN Public Switched Telephone Network PVR Personal Video Recorder QoE Quality of Experience QoS Quality of Service RR Reduced Reference SD Standard Definition (TV) SD&S Service Discovery and Service selection SNR Signal to Noise Ratio SP Service Provider SR Special Report STB Set-Top Box TR Technical Report TS Technical Specification UE User Equipment UGC User-Generated Content UMTS Universal Mobile Telecommunications System UP User Profile VCR Video Cassette Recording VoD Video on Demand VoIP Voice Over Internet Protocol WWAN Wireless Wide Area Network
|
01ee8faf3e3b55e6b1aa35d28a018fce
|
181 016
|
4 Overview on TISPAN IPTV services
|
Several standards on IPTV services are evolving in other standards organizations, including DVB, ATIS IIF and OMA. The ETSI TISPAN architecture shall provide the necessary capabilities to support the IPTV service requirements considering the services covered by the present document. ETSI ETSI TS 181 016 V3.3.1 (2009-07) 13 The TISPAN-NGN network should be aware of an ongoing IPTV service provision in order to be able to provide the correct handling of IPTV service. IPTV services require that the video be stored in multiple coding schemes (and DRM methods) to support a variety of screen resolutions and access bandwidths. IPTV services support in Fixed Mobile Convergence network is required. The present document is complementary to TS 181 014 [3].
|
01ee8faf3e3b55e6b1aa35d28a018fce
|
181 016
|
4.1 IPTV roles
|
To provide IPTV services to the users, different roles could be identified within an NGN. Figure 1 represents all the roles identified for IPTV service. Transport Provider IPTV Service Provider Transport Domain Consumer Content Provider NGN Service Provider Content Domain Service Domain Consumer Domain Figure 1 Grouping of some or all of the different roles under the same administrative environment is an operator option, as defined in NGN operator role in [9]. For example the IPTV Service Provider and the NGN Service Provider may belong to the same administrative environment, or the Content Provider, the IPTV Service Provider, the NGN Service Provider and the Transport Provider may all belong to the same or different administrative environments. The roles are described as follows: The Content Provider is the entity that owns or is licensed to sell content or content assets. Although the IPTV Service Provider is the primary source for the Consumer, a direct logical information flow may be set up between Content Provider and Consumer, for example for rights management and content protection. How the Content Provider receipts content from its owners is outside the scope of the present document. Consumers may also be originators of content. The IPTV Service Provider is the entity that offers IPTV services to the Customers making use of the services capabilities provided by the NGN Service Provider. It can perform user authentication at the application level. This entity may also provide metadata, content encryption and physical binaries. How the IPTV Service Provider receipts content from the Content Provider is outside the scope of the present document. The IPTV Service Provider may offer wholesale content aggregation services to Content Providers enabling the dynamic delivery of Broadcast Channels (BC) and content titles (CoD) between Content Domain and Service Domain. NOTE 1: This role is based on the Application Provider role defined in [9] and it is specialized in the context of the IPTV service. ETSI ETSI TS 181 016 V3.3.1 (2009-07) 14 The NGN Service Provider is the entity that offers NGN based services which shares a consistent set of policies and common technologies. The NGN Service Provider provides common functionalities e.g. user service authentication and identification, service control, charging, etc. Several IPTV Service Providers can use the same NSP to deliver IPTV services to the Customers. The NGN Service Provider may also provide IPTV service. NOTE 2: This role is based on the NGN Service Provider role defined in [9] and it is specialized in the context of the IPTV service. The Transport Provider is the entity connecting the Consumer and the Service Providers. The Consumer is the entity where the IPTV services are consumed.
|
01ee8faf3e3b55e6b1aa35d28a018fce
|
181 016
|
4.2 TISPAN IPTV services
|
The IPTV service description can best be built by categorizing the baseline components that will compose the complete service. The following is the list of categories that have so far been identified and which will be used to derive the initial requirements for the IPTV service and to ensure that the architectural requirements are reasonably comprehensive for the service evolution. A list of IPTV service categories considered in the present document is listed below. More information on these can be found in annex A. • Entertaining: - Broadcast TV (with or without trick modes). - Trick Modes. - Pay Per View. - Content on Demand (CoD). - Personal Video Recording (PVR). - Near CoD. - Interactive TV. - Push CoD. - Audio. - User Generated Content (upload, download, upstreaming, downstreaming). - Personalized service composition. • Advertising. • Regulatory: - Emergency Information. - Applications for the disabled. - Content Advisories. - Educational facilities. • Hybrid Services. • External Content. • Content Aggregation. ETSI ETSI TS 181 016 V3.3.1 (2009-07) 15 There is another category of services, non-video related, delivered from the provider to the consumer that play a critical role in the interaction with the NGN services. This category is called "Service Information" and consists of the following features/services. • Electronic Programme Guide (EPG). • Service Discovery and Selection. • IPTV User Profile. • Parental Control Service. • Notification Services. • IPTV user profiling. • IPTV Content Recommendation Service. TISPAN NGN services shall not be impacted by IPTV services, however some interworking between IPTV services and NGN services should be considered. This interworking shall allow the IPTV services to use the capabilities of the networks to provide the user with an optimized and user friendly solution. Therefore, consideration for the interaction of the IPTV services and TISPAN NGN services is required, leading to the following category of services: • IPTV and NGN Service Interaction: - Watching Apart Together. - Presence based games. - Incoming call management. - Seamless switching among devices. - Content sharing on a multimedia conference. - Sharing the remote control.
|
01ee8faf3e3b55e6b1aa35d28a018fce
|
181 016
|
5 Service requirements
|
NOTE: When referencing the OMA BCAST requirements [1] following OMA BCAST specific words should be replaced throughout the requirements with TISPAN specific words as shown below: • "Mobile Broadcast" replaced with "Broadcast". • "Wireless network" replaced with "network". • "Broadcast Service" replaced with "Broadcast TV service".
|
01ee8faf3e3b55e6b1aa35d28a018fce
|
181 016
|
5.1 General
|
5.1.1 The IPTV solution shall support the individual addressability of devices acting as UEs located in the Consumer Network. 5.1.2 One user can access a service through multiple UEs simultaneously. 5.1.3 One user can access multiple services through an UE simultaneously. 5.1.4 The interactive IPTV solution shall be an open solution, that is Operators and Service Providers shall be able to create new service logics that involve both multimedia and communication features. ETSI ETSI TS 181 016 V3.3.1 (2009-07) 16 5.1.5 The interactive IPTV solution may support downloading service logics on the end-devices (for example via Open API on the STB). 5.1.6 To allow for integrated service logics, the IPTV solution shall have the ability to authenticate the user not just the device. 5.1.7 The interactive IPTV solution shall allow multiple users in front of one TV-SET to communicate their status. 5.1.8 Users shall be able to pick pieces of the IPTV content (if allowed by relevant policies) and to send them directly to other users on their IMS devices (also other than TV). 5.1.9 IPTV services should include operator controlled services, where the operator provides authorization to the user to use these services. 5.1.10 The IPTV solution should support the ability to provide the IPTV services in a FMC and seamless mobility environment. 5.1.11 The NGN network need to be aware of the IPTV application/service of the session to provide the required QoS for that session. 5.1.12 The IPTV solution should reuse the existing NGN architecture (subsystems, components and protocols) to achieve the requirements and enable service control convergence. 5.1.13 Interworking with existing IPTV systems needs to be considered, allowing legacy IPTV equipment to operate in NGN networks efficiently. 5.1.14 The following OMA Broadcast High-Level Functional Requirements of [1], clause 6.1, table 2 apply: HLFR-01, HLFR-03, HLFR-06, HLFR-08, HLFR-09 and HLFR-12. 5.1.15 The IPTV solution shall support the addressing of each user, within a single subscription, individually towards the device where the user has made himself accessible. 5.1.16 The IPTV solution shall support the capability of accessing the IPTV and NGN services from different type of devices depending on their capabilities (PCs, TVs, PDAs or game consoles at home or in the office). 5.1.17 The IPTV solution shall support the adaptation of media format (e.g. video in TV format or in compressed format for mobile devices) to accommodate different UEs or different network conditions. 5.1.17A The IPTV service shall be able to perform the adaptation of media format at anytime during the lifetime of the IPTV session according to the network conditions. 5.1.17B The IPTV should support scalable video coding. NOTE 1: Analysis of the impact of scalable video codecs and transport mechanisms on the IPTV and other NGN subsystems is out of scope of the current release. 5.1.18 The IPTV solution shall support the capability of moving/transferring an ongoing IPTV service from any type of device to another. 5.1.18A The IPTV solution shall support the capability of replicating an ongoing IPTV service from any type of device to another. 5.1.19 It shall be possible to define the minimum set of capabilities for UE (e.g. standard definition TV). 5.1.20 The IPTV solution shall support the capability of making available the UE characteristics (e.g. related to picture resolution) so they can be taken into account for delivering of content and/or access to different services. 5.1.21 Different picture aspects and resolutions for display must be supported (e.g. covering the range from the smallest screen of portable terminals to the largest flat screen TV). ETSI ETSI TS 181 016 V3.3.1 (2009-07) 17 5.1.22 The IPTV solution should support the preparation of content for efficient delivery to consumers. (e.g. transcode the content into a lower bit rate, from HD to SD, or by removing some parts, e.g. audio tracks in languages not needed, to reduce the size of content, etc.). 5.1.23 The IPTV subsystem shall support the capability to provide service resilience (e.g. resilience against single point of failure in the media, broadcast or application server). 5.1.24 The IPTV solution shall provide the capability of receiving and correctly processing the metadata for content coming from the service/content providers. 5.1.25 Metadata may be provided in conjunction with the audiovisual contents of the IPTV service. 5.1.26 The metadata delivery without the audiovisual contents of the IPTV service should be possible. 5.1.27 The IPTV solution should support both multicast and unicast metadata delivery. 5.1.28 The IPTV solution should support 3rd parties metadata (e.g. content recommendations) in addition to metadata from service/content providers. 5.1.29 The IPTV solution shall support mechanisms to address and identify each of the user's UEs. 5.1.30 The IPTV solution should support mechanisms to recognize UEs belonging to one or more specific end-users. 5.1.31 The IPTV solution shall support mechanisms for personalized channel set-up and control on a per subscription basis. 5.1.31A The IPTV solution should support mechanisms for flexible, personalized service composition set-up and control. 5.1.32 The IPTV solution should provide mechanisms to allow distribution of content and metadata between content provider and IPTV service provider. NOTE 2: Specification of the Content Delivery Network (CDN) within the IPTV Service is provided in TS 182 019 [i.3]. Specification of Media Content Distribution (MCD) external to the IPTV Service domain is outside the scope of TISPAN, and may be coordinated with ETSI TC MCD and other relevant external organizations. 5.1.33 The IPTV solution should enable ingress of content from external sources (e.g. Web based TV). 5.1.34 The IPTV solution should enable interaction/integration with internet services (e.g. e-mails, web pages or other multimedia services, etc.). 5.1.35 The IPTV solution should support multiple pay-per-X scenarios (e.g. Pay per view /time / number of plays). 5.1.36 The IPTV solution should provide Multimedia TV messaging. 5.1.37 The IPTV solution shall support mechanisms for emergency alerting based on different aspects (e.g. type of emergency situation, priority, locality). 5.1.38 The IPTV solution should provide hybrid PVR services (as combination of PVR related services like cPVR and nPVR, remote recording, etc.). 5.1.39 The IPTV solution should support the reuse of reserved resources where appropriate (e.g. media channels reused for subsequent content with same characteristics upon a switch).
|
01ee8faf3e3b55e6b1aa35d28a018fce
|
181 016
|
5.2 Generic Entertainment Requirements
|
5.2.1 The IPTV solution shall support the following entertainment services: Broadcast TV with or without trick modes. Time-shift TV. ETSI ETSI TS 181 016 V3.3.1 (2009-07) 18 Trick Modes using a PVR. Personal Video Recorder (PVR). Pay Per View. Content on Demand (COD). Near CoD (nCoD). Interactive TV. Push CoD. Audio. User Generated Content (UGC). Personalized service composition. 5.2.2 The IPTV solution shall support the capability of for an IPTV service to making available its characteristics (e.g. bit rate, coding format, etc.). 5.2.3 The IPTV solution shall support a capability of flexible multiple screen rendering (e.g. Picture In Picture (PIP), split screen as in side by side or Picture and Picture (PAP), or multiple pictures in an NxM mosaic) of multiple video streams of broadcast TV and VoD. 5.2.4 The IPTV solution should support the capability of controlling broadcast with trick modes services (e.g. pause, play). 5.2.5 The IPTV solution should support the capability of controlling PVR services (e.g. schedule program recording, delete schedule). 5.2.5A The IPTV solution should enable a user to share control of his access to the user's PVR services with other users in accordance with legal aspects and operator policies. 5.2.6 The IPTV solution shall support mechanisms and interfaces for the UE and external applications to control the streaming of video and audio content (e.g. trick modes). 5.2.6A The IPTV solution should support restricted trick play functions on any segment of content (e.g. restrict fast forward during an advertisement rendering or copyright announcement). 5.2.7 The IPTV solution shall support mechanisms for an IPTV service provider to share information in real time with the user. The information can be about operations and maintenance issues or charging related issues like total expenditure to date. 5.2.8 The IPTV solution should support mechanisms for the user to content marker IPTV service information and/or content. 5.2.9 The IPTV solution should support mechanisms for the IPTV Service Provider to offer personalized content markers to the users. 5.2.9A The IPTV solution should enable a user to share content marker(s) with other users in accordance with legal aspects and operator policies. 5.2.9B The IPTV solution should refer to content (BC, CoD or other) in a way that is independent of the address where the content can be retrieved. 5.2.9C The IPTV solution should support mechanisms to resolve references to content (BC, CoD or other), e.g. to find the address where referenced content can be retrieved. NOTE 1: Requirements 5.2.9B and 5.2.9C are applicable to content (BC channel, CoD title or other) referenced in an Electronic Program Guide, through IPTV Presence, in IPTV Content markers and other. 5.2.10 The IPTV solution should be able to include unicast and multicast contents sequentially or in parallel in the same IPTV service session. ETSI ETSI TS 181 016 V3.3.1 (2009-07) 19 5.2.11 The IPTV solution should support upload of user generated content. 5.2.12 The IPTV solution should support upstreaming of user generated content. 5.2.13 The IPTV solution should support download of user generated content. 5.2.14 The IPTV solution should support downstreaming of user generated content. 5.2.14A The IPTV solution should support buffering/storage of user generated content. 5.2.14B The IPTV solution should support real-time consumption of upstreaming user generated content. 5.2.15 The IPTV solution should support mechanisms for publishing UGC content information (e.g. via EPG) to the users. 5.2.16 The IPTV Solution should provide a mechanism for the user who has generated the content to control access to the content by other users. 5.2.17 The IPTV solution shall be able to allow any permitted/authorised device to remotely control IPTV services on another device include scheduling PVR recording (for cPVR and/or nPVR), uploading of UGC, etc. NOTE 2: Copyright laws of many countries prohibit users to upload or stream copyrighted materials without permission of the copyright owner. Technical provisions may be needed to curb illegal user behaviour. Examples of such provisions are identity registration, removal of illegally stored content and blocking of illegally streamed content. NOTE 3: Peer-to-peer VoIP clients, on-line games, user generated content and many other applications might be used to carry (voice) communication between users. As such, user-generated content may be subject to lawful intercept ion of such communications. Future regulatory changes in this direction are always a possibility. NOTE 4: User-generated content has the property that some of it may become very popular in a very short time. This may result in flooding of the network. In the past, Telephony Service Providers have made provisions to handle mass calling and protect emergency services. IPTV Service Providers may take similar provisions to protect the network from too popular user-generated content. 5.2.18 The IPTV solution should support mechanism for user to upload or modify a description for the content they create (e.g. home movie description). 5.2.19 The IPTV solution should support mechanisms for exchanging media action data between the UE, external applications and network elements of the IPTV solution. 5.2.20 The IPTV Service Provider should be able to initiate download of content (e.g. recorded Broadcast program, CoD) to the local storage of either specific users or groups of users. 5.2.21 In the Push CoD services, the content shall be downloaded into the local storage of the user, and then be available for direct consumption, after the user selection is confirmed. 5.2.21A The IPTV Service Provider should be able to offer and initiate consumption of IPTV service (e.g. BC service, CoD service) on behalf of the user. After confirmation from the user, the IPTV service can be delivered in real time. 5.2.22 The users should be able to make their comments for specific content available to other authorized users. 5.2.23 The IPTV solution should support mechanisms for users to make their history of viewed content available to other authorized users. NOTE 5: Requirements 5.2.22 and 5.2.23 do not mandate the mechanism(s) to be used for content specific comments or history of viewed content. 5.2.24 The IPTV solution should support mechanisms to provide content preview to the users, either for live content (e.g. BC program) or on-demand content (e.g. CoD content). ETSI ETSI TS 181 016 V3.3.1 (2009-07) 20 5.2.25 The IPTV solution should provide mechanism to combine cPVR and nPVR based on user or system based rules. 5.2.26 The IPTV solution should provide mechanism to distribute (by streaming or download) any nPVR records to local storage of end devices with defined record parameters (e.g. encoding, resolution) and related metadata. 5.2.27 The IPTV solution should support alternative streams to allow a flexible, personalized service composition of video, audio and text (subtitle) streams. NOTE 6: Copyright laws or agreements with content providers may prohibit modification of copyrighted materials (e.g. replacing an audio stream) without permission of the copyright owner.
|
01ee8faf3e3b55e6b1aa35d28a018fce
|
181 016
|
5.3 Security
|
The security requirements for IPTV are described in clause 4.13 of TS 187 001 [8].
|
01ee8faf3e3b55e6b1aa35d28a018fce
|
181 016
|
5.4 Charging
|
5.4.1 Charging; NGN operator controlled charging should be considered for the IPTV services.
|
01ee8faf3e3b55e6b1aa35d28a018fce
|
181 016
|
5.5 Service Discovery
|
5.5.1 The IPTV solution shall support service discovery. 5.5.2 The IPTV solution shall support the discovery of services provided by different service providers. 5.5.3 The IPTV solution shall support personalized service discovery (e.g. the service discovery based on user preferences (subscription, habit etc.) and device capabilities). 5.5.4 The IPTV solution may support service discovery based on the location of the user. 5.5.5 The IPTV solution shall support pushing and/or pulling of ESG from the IPTV Service Provider to the UE.
|
01ee8faf3e3b55e6b1aa35d28a018fce
|
181 016
|
5.6 Service Delivery
|
5.6.1 The IPTV service shall define mechanisms to appropriately distinguish different types of incoming sessions. 5.6.2 The IPTV solution shall support services delivered to a Consumer Network from one or more service providers over an IP transport stream. 5.6.3 The IPTV solution should support roaming as defined in [i.1]. 5.6.4 The IPTV solution should support nomadism of UEs as defined in [i.1]. 5.6.5 For roaming users, the IPTV solution shall support mechanisms for discovering and selecting home provider IPTV services. 5.6.5A For roaming users, the IPTV solution should provide a mechanism to share the user information (e.g. user account, charging information, service authentication information, etc.) based on the business agreement between IPTV Service Provider in the home network and the IPTV Service Provider in the visited network. 5.6.6 The IPTV solution shall support regionalized delivery of content and metadata in accordance with applicable regulations. ETSI ETSI TS 181 016 V3.3.1 (2009-07) 21
|
01ee8faf3e3b55e6b1aa35d28a018fce
|
181 016
|
5.7 User Profile
|
5.7.1 The IPTV solution shall support mechanisms for IPTV service providers to add/delete/modify user profiles. 5.7.2 The IPTV solution shall provide a mechanism for the user to add, remove and modify his or her user profile (e.g. edit a preference data used for content recommendation). 5.7.3 The user should be able to maintain his/her preferences regarding IPTV services as such and in combination with other available services to the user in the NGN network. 5.7.4 The network shall support the user option to change (permanently or temporarily) his user profile from any device capable to access his user data. 5.7.5 It shall be possible to define users, within the subscription, with administration rights over other specified users. 5.7.6 The IPTV subsystem shall support the capability to personalize service based upon user profile or group of user profiles (e.g. resolve personalized content). 5.7.7 The IPTV subsystem shall support the capability for different profile based service personalization (e.g. advertisements, news, traffic information, retrieved from search engines, other).
|
01ee8faf3e3b55e6b1aa35d28a018fce
|
181 016
|
5.8 Parental Control
|
5.8.1 It shall be possible for a user (defined to have administrative rights) to modify user profiles to place controls on users, belonging to the same subscription, for access to services and content (e.g. prevent purchases, set purchasing limits, etc.). 5.8.2 It shall be possible to authenticate the user with administrative rights when placing controls on other users. 5.8.3 An authorization framework must be supported to enforce parental controls based on some type of criteria. The criteria shall be set up on one or more specific classification of the program. 5.8.4 When a user requests an IPTV service, it should be possible to dynamically request authorization from a user who has administrative rights over the user consuming the content.
|
01ee8faf3e3b55e6b1aa35d28a018fce
|
181 016
|
5.9 Interoperability
|
5.9.1 The following OMA Broadcast Requirement of [1], clause 6.1.3, table 5 applies: IOP-01.
|
01ee8faf3e3b55e6b1aa35d28a018fce
|
181 016
|
5.10 Internationalization
|
5.10.1 The IPTV service should be capable of supporting various content rating standards to avoid improper access to content. 5.10.2 The IPTV solution should be capable of supporting the various TV picture definitions that are in common use. 5.10.3 The IPTV solution should be capable of supporting various the various TV aspect ratios that are in common use.
|
01ee8faf3e3b55e6b1aa35d28a018fce
|
181 016
|
5.11 Terminal Provisioning
|
5.11.1 The Terminal provisioning function for IPTV Services shall be defined. ETSI ETSI TS 181 016 V3.3.1 (2009-07) 22
|
01ee8faf3e3b55e6b1aa35d28a018fce
|
181 016
|
5.12 Service Provisioning
|
5.12.1 The following OMA Broadcast Requirements of [1] clause 6.2.6 table 13 apply: PROV-2, PROV-3. 5.12.2 It shall be possible to permit visiting end user to subscribe to content or services.
|
01ee8faf3e3b55e6b1aa35d28a018fce
|
181 016
|
5.13 Quality of Experience
|
5.13.1 The IPTV solution may support QoE concepts such as Full Reference (FR), Reduced Reference (RR) and No Reference (NR) to validate the quality of delivered IPTV services to the IPTV consumer. 5.13.2 An IPTV solution supporting QoE concepts should provide a framework that identifies the key QoE components and measurement points. 5.13.3 The IPTV solution should support channel change times which support good QoE to the user. 5.13a Application Level QoS 5.13A.1 The IPTV solution should support solution(s) for inter-destination media synchronization. 5.13A.2 The IPTV solution should support solution(s) for synchronizing media streams from different origins.
|
01ee8faf3e3b55e6b1aa35d28a018fce
|
181 016
|
5.14 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. 5.14.3 The IPTV solution may provide a mechanism for evaluating how many users are currently accessing a particular content or service, e.g. are watching football match on a broadcast TV channel. NOTE: Any collection of user information related to the consumption of IPTV services should comply with local regulations. The information should be handled privately and securely within IPTV solution. 5.14.4 The IPTV solution shall support mechanisms for an IPTV service provider to offer an IPTV Content Recommendation Service to specific users or user groups on a per subscription basis. 5.14.5 The IPTV Content Recommendation Service shall support mechanisms for a subscriber to access and set his recommendation profile e.g. to switch on/off receiving recommendations, or to set the criteria of accepting or blocking certain content recommendation and so on. 5.14.6 The IPTV Content Recommendation Service should support mechanisms for an IPTV service provider to recommend IPTV contents related to specific user or service provider criteria, e.g.: Related to the program being watched by the user. Based on user profile, IPTV UE capabilities or user preferences. For upcoming programs, or popular movies, etc. 5.14.7 The IPTV Content Recommendation Service should support mechanisms for an IPTV service provider to provide content recommendation information based on the presence status of IPTV UE or user (e.g. online, offline, or other presence information like willingness to be disturbed by recommendations). ETSI ETSI TS 181 016 V3.3.1 (2009-07) 23
|
01ee8faf3e3b55e6b1aa35d28a018fce
|
181 016
|
5.15 Advertising
|
5.15.1 The IPTV solution shall support traditional broadcast advertising. 5.15.2 The IPTV solution should support IPTV advertising targeted towards individual users or specific user groups (targeted advertising which they subscribe or permit). IPTV advertising may be based on multiple criteria, e.g. user profile, preference, presence information, shopping habits or location. 5.15.3 The IPTV solution should support mechanisms to provide interactive IPTV advertising (e.g. Opt-in ad, Click-to-call, etc.) which contains active user interactions/actions (e.g. purchase of advertised product or order of the content). 5.15.4 The IPTV solution should support one or more delivery mechanisms (e.g. multicast, uni-cast, or file download) for IPTV advertising. 5.15.5 The IPTV solution should provide mechanisms to collect/aggregate, store and manipulate with information about user actions on specific IPTV advertising. This capability may be subject to local/regional regulation or user privacy.
|
01ee8faf3e3b55e6b1aa35d28a018fce
|
181 016
|
5.16 External content
|
5.16.1 The IPTV solution shall support a mechanism that delivers external content to a Consumer making use of same delivery mechanisms that are used for content that is stored inside the IPTV SP domain. NOTE 1: This requirement does not introduce a new IPTV role (see the roles in figure 1), rather it clarifies tasks of the Content Providers and IPTV Service Providers. The consumer needs to have a business relation with the IPTV SP. In addition the consumer might have a business relation with the CP that offers external content. The case with a single business relation (i.e. the consumer having a business relationship with the IPTV SP only) can be described as the IPTV SP offering "white labelled" external content. 5.16.2 The IPTV solution shall support interaction with content aggregation services, including, but not limited to: Content aggregation for the delivery of Broadcast (BC) television channels. Content aggregation for the delivery of Content on Demand (COD). NOTE 2: This requirement does not make any assumption on the business model (e.g. wholesale) or direction of money flow between the IPTV Service Provider and the Content Provider. 5.16.3 The IPTV solution should support delivery of external content with QoS or QoE. In this case IPTV SP could provide IPTV capabilities, such as content storage, to place external content to locations where the content is likely to be consumed. 5.16.4 The IPTV solution should support integration of external content with other IPTV services, e.g. Recommendation Service. 5.16.5 The IPTV solution should support mechanisms to exchange relevant information about the consumer between the IPTV SP and the CP that offers the external content. ETSI ETSI TS 181 016 V3.3.1 (2009-07) 24 6 Interaction of IPTV Services and other TISPAN Services
|
01ee8faf3e3b55e6b1aa35d28a018fce
|
181 016
|
6.1 General
|
TISPAN NGN services shall not be impacted by IPTV services, however some interworking between IPTV services and NGN services should be considered. This interworking shall allow the IPTV services to use the capabilities of the networks to provide the user with an optimized and user friendly solution. Therefore, consideration for the interaction of the IPTV services and TISPAN NGN services is required. The general interaction related requirements are presented below: 6.1.1 The IPTV solution shall be able to integrate with (and eventually reuse) the NGN communication services in a way that enable users to intercept and manage incoming call, to send messages, to make video and audio calls, to open data sessions, to use presence information (e.g. "the watched channel", "do not disturb"), and to accept contents that embed communication activities (audio/video/messaging). 6.1.2 The IPTV solution in NGN should be aware of an ongoing IPTV service provision taking into account user subscription, presence, etc. That will allow it to manage other communications accordingly, for example, the IPTV solution should know how to handle other communications while e.g. the IPTV Content on Demand service is on (send voice calls to the STB for example), managing QoS based on session profile, etc. 6.1.3 It shall be possible to support NGN applications and NGN communication services. The following clauses provide some, and non exhaustive, examples of NGN services which may interact with IPTV.
|
01ee8faf3e3b55e6b1aa35d28a018fce
|
181 016
|
6.1.1 Presence
|
The presence service results in presence information of a user and information on a user's devices, services and service components being managed by the network. While channel and content metadata is typically available from SD&S, it is also possible to associate presence information to IPTV channels or content. Such information can include e.g. program status (on air, delayed 5 minutes, current genre, currently running title, etc). Consumers of related presence information could be users as well as other NGN services, e.g. the Personalized Channel Service. The presence service provides access to presence information to be made available to users or services including IPTV services. A presence-enabled service, as observed by the user, is a service in which the user can control the dissemination of his presence information to other users and services, and also be able to explicitly identify which other users and services to which he provides presence status. Example services might include: • Electronic Program Guide (EPG) personalization based on presence on top of locally stored data. • Targeted advertising based especially when correlated with time of day. • Use of presence with the user profile to request special services. • Use of presence with authentication for TV based shopping services as a credit card substitute. • A genre based Presentity Service distributing a list of channels on which movies belonging to their associated genre are currently running. Using Presence allows e.g. to reach non-IPTV Devices. Presence is an attribute related to, but quite different from mobility information, and is a service that can be exploited to create additional services. Presence service in NGN is defined in TS 182 008 [4]. ETSI ETSI TS 181 016 V3.3.1 (2009-07) 25 Presence will enable the users of IPTV services to show their ability and willingness to be reached for communication by defining, e.g. a set of information for the devices the user is using and the services he/she is using. This information is known as presence information and may also be referred to as "user generated presence". "Network generated presence" information relates to status information inside the network, e.g. on the program status as mentioned before. Users' presence information may be related to, e.g. their connection status, location information, channel currently accessed or acceptable communication means. Presence information on channel currently accessed may be used by another user to instruct his set-top box with a single click to switch to the identified channel, or to instruct his set-top box to keep following identified channel changes. There may be significant delays in this following, depending on the update speed of the presence service. Any published presence information should only be disseminated to users that are authorized to receiving this presence information according to the presentity policies. Users can also define a set of access rules to control access to their presence information. The presence specific interaction requirements are presented below: 6.1.1.1 It shall be possible to define presence information related to the IPTV experience, e.g. channel currently accessed. The identification of the channel currently accessed shall be machine-readable. Language dependent information may also be made available to watchers. 6.1.1.2 It shall be possible to have presence information presented on TV screen. 6.1.1.3 It shall be possible to manage the IPTV-related presence information that is shown to each person on a user's watcher list. 6.1.1.4 The IPTV solution should be able to access presence information. 6.1.1.5 The IPTV solution should be able to provide presence information. 6.1.1.6 The watched channel should be reflected in the user's presence status and external application, e.g. another user, should be able to use it together with other presence information (e.g. NGN Communication Presence). 6.1.1.7 The user shall have control on who has access to his/her presence information. 6.1.1.8 It should be possible to distribute IPTV service data information (e.g. on IPTV channels, IPTV content genres, individual IPTV content or personalized EPG services) through the Presence Service.
|
01ee8faf3e3b55e6b1aa35d28a018fce
|
181 016
|
6.1.2 Direct Communication
|
Direct Communication service enables real-time communication one-to-one and one-to-many with the press of a button. Direct Communication provides the use of the generic capabilities of the IMS and the Push to Talk Service defined by OMA, ensuring global interoperability. Direct Communication in NGN is described in TS 181 006 [5].
|
01ee8faf3e3b55e6b1aa35d28a018fce
|
181 016
|
6.1.3 Immediate Messaging
|
There are many different types of messaging services available both in the wired and wireless worlds. Some messaging services are supported in both environments; others are only to be found in one. The expectations of the services differ in that some are designed to be used in what is perceived as "real" time, whereas others are designed as a "mailbox" service where the message is stored ready for collection or delivery at a later stage. NGN Messaging services incorporate one or more of the following messaging types immediate messaging and Session based messaging. With Immediate messaging the sender expects immediate message delivery in what is perceived as real time. ETSI ETSI TS 181 016 V3.3.1 (2009-07) 26 With Session based messaging a communications association is established between two or more users before communication can take place. In the simplest form Session based messaging maybe a direct communication between two users. The messaging services for NGN are described in TS 122 340 [6]. 6.1.3.1 The IPTV solution should provide a mechanism for users who subscribe to an IPTV immediate messaging service and have the right to send immediate messages to other users in an immediate messaging service group watching the same program. Immediate messaging shall be limited to users who have expressed their willingness to be accessed by the immediate messaging service and particular sender.
|
01ee8faf3e3b55e6b1aa35d28a018fce
|
181 016
|
6.1.4 Video Telephony
|
Video telephony is a real time conversational service using video media and audio or other types of media. The service is assumed to be applicable only to dedicated terminal equipment with video capabilities. The video telephony service may be considered as a specific instance of an IP multimedia service, or as part of the Multimedia Telephony with PSTN/ISDN Simulation Services. The Video Telephony Service in NGN is defined in TS 181 001 [2].
|
01ee8faf3e3b55e6b1aa35d28a018fce
|
181 016
|
6.1.5 Multimedia Telephony
|
From the human user point of view, Multimedia Telephony with PSTN/ISDN simulation services, provides a suite of services that are, in most aspects, the same as those already existing in the PSTN/ISDN. Multimedia Telephony makes use of IMS, which is an inherently multimedia service control platform. Therefore, Multimedia Telephony with PSTN/ISDN Simulation Services, whilst drawing on the existing service features in the PSTN/ISDN, is not limited to voice media as in PSTN/ISDN, but generally applicable regardless of the media used (voice, video, etc.). In addition to the capabilities to establish a bi-directional point-to-point communication between two parties, a selected number of PSTN/ISDN Simulation services was defined, corresponding to perceived popular PSTN/ISDN supplementary services. Among them, the following are the mandatory services: • Communication Diversion. • Identity Presentation and Restriction services. • Malicious Communication. • Anonymous Communication Rejection. The Multimedia Telephony Service in NGN is defined in TS 181 002 [7].
|
01ee8faf3e3b55e6b1aa35d28a018fce
|
181 016
|
7 Interaction with IPTV Services
| |
01ee8faf3e3b55e6b1aa35d28a018fce
|
181 016
|
7.1 Interaction Channel
|
7.1.1 The following OMA Broadcast Requirements of [1] clause 6.2.2 table 9 apply: IC-01, IC-02, IC-03 and IC-04.
|
01ee8faf3e3b55e6b1aa35d28a018fce
|
181 016
|
7.2 Notifications
|
7.2.1 The following OMA Broadcast Requirements of [1] clause 6.2.8 table 15 apply: NOTIF-01, NOTIF-02 and NOTIF-03. ETSI ETSI TS 181 016 V3.3.1 (2009-07) 27 Annex A (informative): TISPAN IPTV services descriptions A.1 Entertaining In the particular case of entertainment, the services so far identified are described and listed below. A.1.1 Broadcast TV Broadcast TV service on the IPTV platform corresponds to the classic form of television offered by cable, terrestrial broadcasters and direct broadcast satellite providers, in which the programme content is transmitted according to a schedule defined by the service provider and is intended for real-time consumption by the end user. The service therefore provides an essentially continuous stream flowing from the content provider to the terminal device in the consumer network. This type of service is sometimes known as a "linear broadcast" or "push content" service. Channel selection to receive the desired broadcast stream ("signal") is supported, but users have no direct control over broadcast content. A limited form of interactivity may be available in some cases. Examples include the case of a user watching a Quiz Show who may be able to compete for prizes by submitting answers. Alternatively, a user watching a current affairs programme may want to send a comment to the interviewer. Both these interactions use a separate channel. Other users will be unaware of the comments received unless these are quoted by the interviewer or displayed as on-screen text messages. Content may be received from the originator by the service provider via satellite or other means. The content provider may replicate the content stream to several service providers, who in turn may replicate it to multiple delivery networks. Each delivery network will usually replicate the stream to multiple consumer networks. Individual Service Providers may provide additional processing of the video stream, e.g. insertion of local content channels, advertising, etc. A.1.1a Time-shift TV (tsTV) Time shift TV is the service where the IPTV service provider can store (record) the broadcast content in the network for later viewing. The recording can be done for a time window (e.g. days or weeks or individual show based on EPG), where some or all the programs from the window can be offered later to IPTV users and delivered as CoD assets. TsTV differs from trick modes using a PVR because it does not require user interaction to retain or remove content. Trick modes may be allowed. Catch-up on time shift TV is the service where during Fast Forward a user is automatically switched by the network to live TV stream, when Fast Forward reaches the current life stream. A.1.2 Personal Video Recording Although Broadcast TV is intended for real time consumption, some end users may wish to record the broadcast content for later viewing. Whilst this can be accomplished simply with a VCR the increasing availability of PVR has led to greater "trick mode" functionality. By copying the broadcast content to a PVR the consumer is enabled to enhance his experience by pausing, rewinding, jumping forwards or backwards, playing at double speed, etc. during such later viewing, all using the inherent storage capability of the PVR. The PVR itself may be a separate physical device (set top box) or it may be a logical device (addressable hard disk storage in some multi-purpose unit) either in the Consumer Network (cPVR) or, provided by the SP (nPVR). In any of these cases, the user can replay the programme at any convenient time and the nPVR feature is sometimes regarded as "time-shift TV", enabling a viewer to receive and view the desired content at some later time. In case of cPVR, an authorized remote device that may be located outside of the Consumer Network can be used to control PVR recording. ETSI ETSI TS 181 016 V3.3.1 (2009-07) 28 A.1.3 Pay Per View (PPV) Pay Per View (PPV) is an offering of pay-television broadcasts to consumers in such a manner that they can make a "one-off" purchase of a particular programme event (for example, a boxing match) separately from their regular package or subscription. The programme event is shown at the same time to everyone ordering it (as opposed to a CoD programme event). The qualities of IPTV PPV include: • The PPV session is a multicast session. • The Service Provider determines the schedule of when the content is transmitted. • The content is an object that has finite boundaries, meaning it has a defined beginning and end. • The user cannot control the transmission source to randomly move through the content object. A.1.4 Content on Demand (CoD) The Content on Demand (CoD) service provides an essentially two phased distribution from the Content Provider to the terminal device in the Consumer Network. The Service Provider acquires the content from the Content Provider via physical media delivery, electronic interconnection or other means and may provide additional processing of the video stream, for example, the insertion of branding, local content, advertising, etc. The Service Provider then makes the content available to the consumer's terminal equipment. There may be multiple independent unicast viewing sessions for a given piece of content. A navigation screen enables the consumer to access the desired content, as and when required. CoD services usually include VCR-like functions (Pause, play, rewind and fast forward of the video) as well as trick- play support (e.g. jump five minutes backward). CoD is differentiated from broadcast video in that: • The user is in control of what is selected and transmitted for viewing. • The user is in control of when a given item of content is viewed. • The CoD content is an object that has finite boundaries, having a defined beginning and end. A.1.5 Near CoD (nCoD) Near CoD is similar to CoD but is sent to user by multicast rather than unicast. Usually, a specific piece of content is transmitted at scheduled intervals, for example a particular film may be started every fifteen minutes on different channels. A viewer can either register a wish to see a particular rendition of it, as selected from an EPG or can be directed to a particular channel at the next scheduled starting time, depending on the service provider's policy. Some networks operate an "open channel" policy, where the start of the play-out may be triggered by the first request for the specific content item and subsequent viewers can join the channel at any time, picking up the programme from whatever point it has reached. A.1.6 Interactive TV Interactive TV applications deliver functionality beyond that generally associated with the traditional television reception. The enablement of interactive TV features generally increases the appeal and popularity of broadcast channels and is a key mechanism to allow differentiation between service offerings. Interactive TV applications often include: • Non-IPTV Terminal Device applications: Web or mobile applications that interact with the IPTV system to modify the settings of the IPTV environment. • Server-based applications: Network-accessible interactive applications that are accessed via remote terminal services, for example to save on the processing and storage requirements on the IPTV Terminal equipment, these can be run externally on Interactive Application Servers. ETSI ETSI TS 181 016 V3.3.1 (2009-07) 29 • Downloadable applications: Interactive Applications downloaded to IPTV Terminal device if and when invoked by subscriber, or service provider. • Native applications: Interactive Applications that are part of the in-built software or permanently downloaded with the IPTV Terminal Device software in order to interact with the IPTV Terminal device hardware and to provide a quick response. • Hybrid Interactive Applications: a combination of native and downloadable interactive applications. Interactive Applications can be invoked in a number of ways regardless of whether they are associated with a particular programming event (e.g. the Big Brother voting application) or they are standalone (e.g. gaming applications): • Click to action: interactive applications that ask for consumer interaction to either invoke or dismiss (e.g. interactive advertisement, call forwarding application, voting application). • Informational: Additional data to provide more details on a particular subject or channel (for example, news, weather information, stock information, live election results, etc.). • Notification or Event Driven: Interactive Applications that respond to service provider or regulatory events to generate an alert/notification for the consumer to take a specific action (e.g. payment overdue notice, bill paid notification, calling line identifier). A.1.7 Push CoD In streaming video content distribution services such as broadcast TV or streaming CoD, the rendering of the content on the display device occurs simultaneously, or at least overlaps with the distribution of the content. A download based content distribution service, in contrast, downloads a complete logical content element (a programme, an episode of a programme series, etc.) to local storage (for example, as part of the set top box function) in a first phase that then enables the consumer to trigger the rendering of the video content at a later time. Such triggering may be allowed at any time after receipt of the content, only at or after some later time determined by the service provider or after some later trigger signal sent by the content or service provider. A.1.8 Audio Audio is another form of content that can be offered by the service operator to the consumer; similarly to video content, it can be offered in a variety of fashions including, but certainly not limited to: • Dedicated music channels (per genre of music). • Music on Demand. • Download store or play later. • IP Radio Multicast. • Rolling news broadcasts. • Audio books. A.2 Regulatory and Governmental requirements Traditional communications and broadcasting services are strictly regulated throughout Europe and in most countries of the world. It is reasonable to suppose that governments will seek to impose similar regulations on NGN communications providers including IPTV service operators. ETSI ETSI TS 181 016 V3.3.1 (2009-07) 30 A.2.1 Emergency Information IPTV networks must be compliant with these regulatory requirements for emergency alerts. These regulations typically require the carriage of emergency alert messages issued by national, state or local authorities. IPTV systems will in practice require secure mechanisms to acquire, verify and inject the appropriate content after ensuring that it comes from an authorized source. The emergency alerts will only achieve their purpose if they are correctly decoded and rendered on the user equipment, and when they alert the public promptly, accurately and efficiently. This means that any delay associated with the transmission or decoding of this content must be minimized. The interaction of emergency alert system with other non-video IPTV services (e.g. voice messaging) is a subject for further study. A.2.2 Lawful Interception (LI) IPTV systems are capable of carrying person-to-person communications as such may in some jurisdictions be regarded as telecommunications channels and thus required to comply with local legislation and regulatory requirements concerning lawful Interception of communications. Refer to TS 187 005 [i.2] for more information. This may be a subject for further study, possibly in ETSI TC-LI. A.2.3 Applications for the disabled The physical design of user equipment and its operation to facilitate its use by consumers with disabilities is beyond the scope of this paper and is for further study, possibly by ETSI TC-HF. However, a number of countries already require that the audio content of many television programmes be made available to hearing disabled users by displaying the audio as text or in sign language on the television screen, a trend which is likely to continue. It is expected that IPTV services will likewise be required to display the audio component as text or in sign language, and to provide audio description services where appropriate, on much the same basis as today's broadcast television. Administrations requiring the use of sub-titles or sign language usually also have requirements on the selection of programmes for provision of these additional access services; details of this are beyond the scope of the present document, as are the requirements for speed and verbosity of the speech or captioning. These matters and the details of overlay positioning are largely matters for national regulation and the content providers. A.2.4 Content advisories A content rating system for TV content providing guidance for parental controls is a legal requirement in most countries and is implemented by a variety of technologies. This may mean that several different "flavours" of the control mechanism will be required. The necessary data are normally provided by the content provider, usually based on statutory ratings. IPTV terminal equipment will be expected to support equivalent capabilities to the content advisories and parental controls specified for traditional television services. A.2.5 Educational facilities IPTV services will provide a video content distribution of a variety of types - broadcast, on demand and interactive. While these services are usually regarded as a consumer medium, similar services can be provided to educational establishments, carrying relevant programming. Whereas traditional broadcast services usually make educational content available according to a fixed schedule, IPTV services offer significantly greater flexibility in scheduling their content to the needs of educational institutions, especially in conjunction with the use of CoD, nCoD or nPVR facilities. Thus, together with their greater capability for interactivity, IPTV network services are potentially of great interest in distribution of educational content at all levels. IPTV services, also have the potential for another educational application, that the provision of remote access to educational content for "distance learning". The remote site in this service is more typically characterized as a consumer or small business location rather than a large institutional setting, though its use in correctional institutions may be appropriate, especially where only a small number of detainees have a specific learning requirement. ETSI ETSI TS 181 016 V3.3.1 (2009-07) 31 A.3 Advertising Traditional television services often incorporate advertising content, usually as a means of revenue generation. It is therefore to be expected that IPTV services will include traditional advertising and probably introduce new concepts. A.3.1 Advertising mechanisms "Ad insertion" can be performed locally, regionally or nationally in IPTV services using serving streaming server as a part of a schedule or combined media asset. IPTV serving streaming server can produce a combined output stream from main program and personalized assets. Personalization, referred to also as advertising, can target large groups, small groups, users or account profiles. "Ad insertion" may be performed locally, regionally or nationally using an "ad-splicer" which is a form of switch which can produce a combined video output stream by locating and using video splice points from the digital cue tones to trigger an "ad server" to play out the relevant advertising content between programme items or during specially scheduled programme breaks. Such breaks are often regulated as to their duration and frequency and may be timed for climactic points in the programme to avoid losing viewers by "channel-hopping". In addition, inserted advertisement may be rendered with restricted trick play functions. For example, users may prefer to choose contents having been paid by advertiser for free, and in exchange, they will not be able to perform trick play function during the advertisement segment. "Banners" are advertisements or programme content that typically run across the top or bottom of a TV screen during the programme content. "Interstitials" are additional pages between informational text pages, whilst "pop-up" ads do just that! IPTV consumers are expected to be able to "opt-in" to targeted direct marketing initiatives using their "user-specific" data, for example giving them the opportunity of being included in special promotions. IPTV will open new opportunities for localization and personalization of advertising content, thus reinforcing its relevance and will be able to provide information about who is watching what programs and what channels. The opportunity to aggregate this information will enable advertising to be targeted to specific groups producing a dramatic improvement over current methods of audience measurement. Near real-time monitoring could be utilized to further refine the placement of relevant ads. The inherent addressability of IPTV will allow ads can be targeted at large groups, small groups, or even individual television sets. Advertisements may be constructed from individual elements such as different scenes and languages to convey messages targeted to particular groups of consumers. IPTV advertising will be made far more relevant in IPTV services than in today's broadcast TV world. A.3.2 Traditional broadcast advertising in IPTV Broadcast TV advertisements can already be inserted on a national, regional or local basis sometimes using complicated scheduling to accomplish all three mechanisms in a single commercial break. As IPTV becomes more widely available and its flexibility understood, advertisers will clearly wish to exploit the new capabilities available to them, some of which are enumerated in the succeeding clauses. A.3.3 Advertising developments Future IPTV advertising developments might include those based around the consumers' personal lifestyles, for example. Shopping habits - Consumers may wish to register such things as their store loyalty cards or other preferences with their IPTV service providers as a means of receiving targeted ads. Personal preferences - Consumer will be able to specify their willingness to watch certain types of advertising either by: Specifying products, subjects or goods in which they are interested or those in which they have no interest. ETSI ETSI TS 181 016 V3.3.1 (2009-07) 32 Interactive advertising - Could be: • Multi-dimensional, allowing the user to navigate links within the advertisement to find additional details of the products shown or to access special offers. If a consumer "opts in" to the ad, their contact information may be downloaded by the advertiser to enable direct marketing. • Consumers could have an interactive session with commercials, perhaps using the remote control. • A "click to call" feature could enable the consumer to initiate a telephone call to discuss the product. • Content Advertisement to enable consumers to look for specific items or services where the advertisements are content in their own right and can be sought by users. • TV Guide advertising - advertising content could be associated with the programme content. • Advertising of business services on IPTV could include simple directory listings or more complex multimedia advertising. • IPTV services could include an application allowing the delivery of direct mail advertising which may be in text or multimedia format. • Polling applications could incorporate advertising content. • A "ticker" application could deliver continuous advertising messages, perhaps in exchange for "free" entertainment content. Advergaming - is a feature predicted by some marketers looking for new ways to place their products before their potential consumers in the future. This might take two forms: • The ads themselves being the games. • In-Game advertising, where the game includes references to products being marketed and where the outcome of the game is influenced by the player's responses. Consumer Log - IPTV could give consumers an option to create a database of interesting advertising messages delivered during a TV broadcast and to allow the review those messages later, to request further information or to make a purchase. When an advertising message is thus stored on the consumer's PVR, the advertising targeting application could use the information to trigger the presentation of a more detailed message. Many of these processes may currently be under laws to protect consumers' privacy thus advertisers and service providers would have to give considerable attention to their processes, not least to create and maintain a sufficiently robust audit trail of such activity. A.4 Service information These services usually consist of non-video services that are delivered from the service provider to the consumer, either explicitly (perhaps requesting or enabling the consumer to take a particular action or to provide EPG data) or implicitly (for example, to apply a control the consumer network equipment). A.4.1 Electronic Programme Guide (EPG) The EPG (otherwise known as the Interactive Programme Guide (IPG)) is a service facilitated by middleware, which provides the consumer with detailed information about the content available to them. The user is able to interact with the network using the remote device to control the STB and thus to receive the EPG information. This user interaction will usually result in a network control action, which may include: • Push mode. • Pull mode. • Transmission of specific content. ETSI ETSI TS 181 016 V3.3.1 (2009-07) 33 • Query of Content. • Transmitting full content information. • Transmitting selected partial content information. • Filtering of the content (e.g. parental control). There is a variety of standards associated with EPG, the most important of which are the DVB-SI standard from DVB and the A/55 standard from ATSC. These define the data tables for interpretation by the middleware. Even though there are differences in the terminology of the different sponsoring bodies, they have common aims and these same aims must be supported by the IPTV architecture. The standards address the typical method of broadcast, in which all channels available to a consumer are transmitted simultaneously. In the IPTV model where only requested channels will be transmitted, some of the concepts that drive the EPG will vary. In the IPTV model, a master list mapping every channel to its multicast server address will be required at every consumer's terminal. The EPG will use this information to display available programmes which can be searched by the consumer, to enable a selection to be made. The terminal must have data about the channels and the events. The delivery of these data from the network is dependent on the employment by the service provider of either: • Push model, where the consumer's terminal equipment receives and stores content from EPG server and updates to the content are automatic, thus the programme information available to the consumer is always up to-date. • Pull Model, where updates have to be manually requested from the EPG server; whilst this data is usually stored in the consumer's terminal equipment, it is not necessarily up-to-date. A.4.2 Electronic Service Guide (ESG) The Electronic Service Guide (ESG) enables service and content providers to describe the services and content they make available, or offer for subscription or purchase. It also enables a method for describing how to access the services. From the user perspective the Service Guide can be seen as an entry point to discover the currently available or scheduled services and content and to filter those based on their preferences. Similar to the retrieval of EPG data, an ESG can be either pushed or pulled onto the consumer premises. An interesting property of the ESG, distinguishing it from an EPG, is that it provides the entry point to interactive TV services, such as those mentioned in clause A.1.6. That is, the ESG can contain information on interactivity with content that is related to what is on TV or interactivity with actual TV programme content. This interactivity is described in the interactivity data. The ESG consists of both EPG and interactivity data, as shown in figure A.1. ESG EPG Interactivity data Figure A.1 Relating to the IPTV roles from clause 4.1, the IPTV Service Provider aggregates EPG and interactivity data into an ESG and makes it available to the consumer. Interactivity data is generated by either the IPTV Service Provider or the Content Provider. ETSI ETSI TS 181 016 V3.3.1 (2009-07) 34 A.4.3 Service Discovery and selection Service Discovery (SD) is a mechanism which discovers the available IPTV services that are compatible with the available Consumer Network equipment. Service Discovery may also enable the user to request a specific service to be delivered to the Consumer Network for rendering on a particular terminal device. Once the user has requested the execution of the service then the Service Discovery will ensure that it is delivered in a format and to a device that is able to execute the service. For instance, an HDTV session will not be opened towards a low resolution receiver. A.4.4 IPTV User Profile The IPTV User Profile contains information about how a user can make use of the IPTV Services as such or in combination with other available services to the user in the NGN network. It can, for example, contain the services available to the user, the viewing preferences for a specific user or the rights associated with the user. The User Profile enables users to modify the default service delivery details and to customize their personal preferences for their range of services. A.4.5 Parental control services Many parents are concerned about their young children watching programs with content that is more suitable for older children or adults. Most parents are concerned that their younger children might watch programs with unsuitable content and it is with this in mind that most countries have rating systems in place such that the content transmitted on commercial television services is defined as suitable for different age groups. These ratings are usually assigned by national bodies, employing strict guidelines to define their rating process. These rating systems provide the mechanism for deciding the suitability of a particular content for a minor based on the child's age. The ratings are usually hierarchical, and hence ratings applicable for a certain viewer age group indicate that the content is suitable for viewers whose age is greater than the rating. Music and games are similarly rated in many countries and sometimes those with explicit lyrics or pictures are specifically marked to warn parents of their content. In addition to these controls, commercial TV networks are restricted in most countries from broadcasting inappropriate material during times when children are likely to be watching. The IPTV service should enable the consumer to control access to content that is accessible at any given time based on its classification, rating, age of audience or other optional criteria such as: cost, channel number, actor, start time, length, etc. This feature could also be available to restrict access to a particular channel though this is perhaps more appropriate as a terminal device function or as a user preference. The set restriction could also be removed by providing a means to prove authority for viewing a particular channel or content. Parental controls may also be made available for other services provided by the IPTV service provider (e.g. electronic games or the purchase content). Parental Controls can be enforced at two different points; at the platform level (by the consumer) and at the policy level (by the service provider). At the platform level, the consumer can create multiple users, each having different access rights. Dependent on the system, a "child profile" user may not even be able to see reference to "adult" material on the EPG. At the policy level, the service provider can set limitations (with or without the consumer's knowledge!) per user profile. Parental Controls can also be enforced dynamically at IPTV session activation. Even if the rating suits well with the requested program or CoD, the parent may want to be alerted when the child starts an IPTV session. He may find that the child wants to watch a content at inappropriate time. The use case could be the following: a child wants to watch a CoD and starts a CoD session initiation. An SMS is sent to the parent to request authorization. If the parent answers "yes", the IPTV CoD session can start. If not, the IPTV COD session activation is stopped. The service logic could also set timer in order not to interrogate the parent anytime the child wants to watch a content. For example, if the answer is "no", next session that occurs before the timer has elapsed would be denied without any alerting to the parent. ETSI ETSI TS 181 016 V3.3.1 (2009-07) 35 A.4.6 Notification services Notification services (for example Caller ID, Alert Messages, etc.) refer to services that can be displayed, (usually as overlaid text) on a consumer's television while they are watching video content. These messages are displayed in a window varying in size depending on the application and the preference of the user or the IPTV service provider. Depending on the circumstance, this window can be initiated at a time specified by the consumer (for example, to act as an alarm clock) or by the service provider or by a system event. It may or may not be accompanied by an audio event, and may or may not require a specific action for its dismissal or invocation, for example, click to close. An appropriate signalling mechanism is used to convey the notification from its source, via the IPTV platform to the terminal device for rendition onto the consumer's screen. A.4.7 Content Recommendation Content recommendation is aiming to provide guidance and recommendation about actual or future available IPTV contents to specific users or user groups who have subscribed to this service based on the user profiles content metadata (e.g. user preferences, watching habits, user characteristics). The recommended content can be BC programs, COD contents, advertisements, or any IPTV applications which should be possibly interesting to the users. Content recommendation may be based on several Program related recommendation criteria as follows: • Recommendation which is related to the program that the user is currently watching. The recommended contents are evaluated according to the metadata of current program. This type of recommendation is usually for specific user. • Recommendation which is based on the user profile. The recommended contents are evaluated based on the user profile. This type of recommendation is usually for specific user or user group. • Recommendation which relates to user profiling, e.g. information about user consumption of content and services over a period of time such as previously watched programs on broadcast TV channels, consumed CoD assets, frequently used integrated IPTV and NGN services. • Recommendation which is for new movie publications, upcoming programs, or popular movies and so on. The recommended contents may have no relationship with what the user is currently watching, e.g. the user may be watching TV, browsing EPG, or playing game. This type of recommendation can be provided to all users, specific user group, or even individual user. Presence information may be used for delivering "off-line" and "on-line" content recommendations as follows: • Off-line: recommendation when the IPTV UE is offline. There is a relationship between the IPTV UE and other UE (e.g. mobile equipment like cell phone) to which IPTV service provider may send recommendation. • On-line: recommendation when the IPTV UE is online and the user has provided other presence information. IPTV service provider may send recommendation to the IPTV UE. A.5 Hybrid services The IP delivery channel may be used for a consumer's complete service offering or may be combined with other TV services in a hybrid service offering. For example, a service provider may chose to offer broadcast services via an independent channel whilst providing interactive, download or CoD TV services via the IP network. A number of variants of such hybrid services are possible. The non-IP content may be delivered over a completely independent delivery network, such as terrestrial broadcast, direct-to-home satellite, hybrid fibre-coax or optical distribution network. Such hybrid approaches can offer advantages both to the service provider and the consumer, perhaps reducing the risk from new technologies, giving faster time to market and providing a degree of resilience in overall service delivery. ETSI ETSI TS 181 016 V3.3.1 (2009-07) 36 A.6 External Content and Content Aggregation Compared with broadcast TV services, a major benefit of IPTV service is its ability to deliver a wider variety of content. Any particular IPTV service provider will be able to hold only a finite content library and carry only a limited number of broadcast channels, but by allowing access to "third party" content providers catering for specific or minority interests, such content (both broadcast channels and stored content) being most likely to be delivered via a CoD-like mechanism. The overall service becomes very much more appealing to its consumers. A consumer might acquire external content from several CP via its IPTV SP. Figure A.1A illustrates the difference of external content and content not characterized as external content. Content Provider Content Provider Transport Provider IPTV Service Provider Transport Domain Consumer Content Provider A NGN Service Provider Content Domain IPTV SP administrative Domain Consumer Domain Content Provider B with external content Service Domain Content aggregation Figure A.1A: External content and content aggregation This means that in order to provide a comprehensive offering an IPTV Service Provider (SP) could need to have business relationships with a large number of Content Providers (CP), some of whom may be extremely specialized, thus effectively providing a "library" service to their consumers. In turn, this necessitates an effective indexing system as to what content is available and where it is located. This may suggest the need for a Content Broker (CB). Whilst this is not seen as a "domain", as described in clause 4.1 of the present document, such content brokers would provide liaison between the Content Provider (CP) and the IPTV Service Provider (SP) domains. In such cases, it is envisaged that the consumer would ask his preferred IPTV SP either for specific content, e.g. "I want to watch a film of the 1966 Football World Cup final" or request a more generalized search e.g." What Charlie Chaplin films are available for download?". The SP would first search the resources of his preferred CPs and if the specific material was available advise the consumer as to how to retrieve it and at what cost. If the material was not available or for generalized requirements, the SP would pass the request to the CB who would locate the required material in his index and advise the relevant CP of the requirement, and tell SP where the material was located, how it could be retrieved and at what cost. The SP would then inform the consumer who could then choose whether or not to complete the transaction. The whole process bears comparison with that of an internet search engine. Alternatively, IPTV SP could have a business relationship with some Content Providers to deliver their content with QoS or QoE. The IPTV SP delivers the content to the consumer making use of the services capabilities provided by the NGN SP. The IPTV SP could provide IPTV capabilities, such as content distribution service to place some of the content to locations where the content is likely to be consumed or provide other services, e.g. restrict unauthorized redistribution. IPTV SP could also include content from the "preferred" CPs into other IPTV services, e.g. Content Recommendation. There might be a direct business relationship between the Consumer and one or more Content Providers, as long as the content is delivered via the IPTV Service Provider platform. However, even though there is a business relationship directly between the consumer and CP, a separate business relationship must exist between third party CP and IPTV SP. ETSI ETSI TS 181 016 V3.3.1 (2009-07) 37 Uncontrolled redistribution of such content is not to be supported, thus it will need to be appropriately protected by a DRM scheme. The required content may be carried via the network interfaces shown in clause 4.1 or there may be additional signalling interfaces between the SP and CP to enable appropriate access to the content. This example describes a consumer requirement in terms of CoD or download services, but in the general case the external content could equally be a broadcast channel, perhaps a requirement from an expatriate Australian in London wanting to watch the broadcast television coverage of the Melbourne Cup. A.7 Use case examples for IPTV and NGN services interaction The integration of IPTV services with other NGN services allows for new value-added services in which the basic Broadcast, CoD and N-PVR services can be extended and/or combined with other NGN services, such as Presence, (Multimedia) Telephony and more complex services. This interworking allows the IPTV services to use the capabilities of the network to provide the user with an optimized and user friendly solution. In this clause a non-exhaustive list of use case examples is given to indicate the possibilities for service orchestration and interaction. A.7.1 Watching Apart Together The combination of basic IPTV services such as Broadcast, CoD and N-PVR, with Presence, allows a user to search for other users, e.g. buddies or people having similar interests, that are watching TV or viewing a CoD/N-PVR content at the same time the user is consuming that service. That user may then consider communicating with these other users in a number of ways, e.g. through an instant-messaging chat service or by having an audio and/or video conferencing session. These services lead to a situation where users, while physically separated, can watch apart together, increasing their sense of co-presence. A.7.1.1 Use case: chatting during live TV For example, user A is watching a football match by having a BC session in place. Since he would like to discuss the match with friends or fans of the team X he supports, he can open an instant messaging client and search for "young supporters of team X watching the match now that are available for chatting". The user then receives a list of other users that fulfil the search criteria and he can continue to select user B and start a chatting session with him. A.7.1.2 Use case: videoconference during live TV Instead of having an instant-messaging session in place, user A and user B can also decide to communicate through a multimedia telephony session. By having a microphone and/or webcam connected to the set-top box, both users can have the incoming videoconference session placed as picture-in-picture on their TV, while the associated audio signals are routed though the TV speakers or a separate audio path. A.7.1.3 Use case: recommending programs In a third example, user A is watching an interesting program. He can see on his buddy list that user B is watching a different program. User A would like to notify user B about the show he is watching. He can select user B on his buddy list and send him a recommendation. Use B receives a pop-up, stating that user A is watching a program he might like. User B can then directly switch to the program that user A is watching. User A receives a notification that informs him about the choice user B has made. A.7.2 Presence based games User A is watching the TV. He receives an instant message on the TV screen that says "In a minute some adverts will be transmitted… watch carefully the spot of new FJ TVBOX… do not switch the channel, and you could win the new STB by FJ". The message is sent to all the users that are not using a FJ TVBOX, and the winner is chosen among all of them that really watched the spot. ETSI ETSI TS 181 016 V3.3.1 (2009-07) 38 A.7.3 Incoming call management The combination of basic IPTV services such as Broadcast, CoD and N-PVR, with Telephony, allows a user to have increased control over incoming calls when watching TV. While User A is watching TV, he receives a notification that warns him about an incoming call. The caller-ID shows him that the call is from user B. User B, who calls him from his telephone. User A can then select between several options to handle the incoming call: • Accept on TV; the TV signal is paused or muted and the incoming voice signal can be heard over the TV speakers. • Accept on mobile; the call is forwarded to user A's mobile phone. According to his user profile, the TV can either be paused or can continue. • Route to mailbox; user A does not answer the call. Instead, the call is forwarded to his voicemail box. • Refuse; user A does not answer the call. User B may receive a notification that informs him about the option that user A has selected. If the user's response to the incoming call leads to a change in IPTV service state through a media control operation by the user (e.g. user pauses the TV), external service logic is informed about this change and its cause. Similarly, if the user's response to the incoming call leads to a change in IPTV service state through a media control operation by external service logic, the user equipment and/or the relevant network elements of the IPTV solution are informed about this change and its cause. A.7.4 Seamless switching among devices User A is watching the TV and has activated the TV Call Manager for his mobile phone. User A receives a video communication on his mobile phone and, as described in the previous use case on Multiple Incoming call management, a little pop-up on the TV warns User A that there is an incoming video communication on his mobile, shows the caller id, and asks for instructions. User A initially accepts the video communication on the mobile. Then the user can choose to: • switch the video communication on the TV set, reducing the TV program on a smaller picture (with automatic switch of audio of the program in mute mode); • split the media components of the video communication among the mobile phone (audio component) and the TV (video component) reducing the TV program on a smaller picture on the TV. A.7.4a Seamless Replication of an IPTV service among devices User A is watching the TV or any content on demand with his family. He has to leave the room and would like to continue viewing the same content from his mobile device or from another room without interrupting the first session. A.7.5 Content sharing on a multimedia conference User A, employee of FJ Company, is watching the communication of FJ's CEO on TV. User A considers the program very interesting and would like his colleague User B to watch the same program. Therefore User A calls his colleague User B and adds the specific content streaming to the conference, so inviting User B to watch the program too. ETSI ETSI TS 181 016 V3.3.1 (2009-07) 39 A.7.6 Immediate messages sharing with all the user watching the same program User A is watching a program on the TV. The program is discussing about "The reason for the weather being warmer and warmer" among several experts. User A is interested in this discussion, and he wants to join and shares his own views. User A opens the immediate message client on the TV. He inputs his views and pushes the button marked with "VIEW" to send them. All users watching the program could receive his views. And other users' views are also shown on his TV. A.7.7 Sharing the remote control The control over basic IPTV services such as Broadcast, CoD and N-PVR lies with the user. Exposing this control functionality, e.g. trick-play, to the network and/or other users enables a large variety of value-added services. A.7.7.1 Use case: joint control over CoD movie For example, user A is watching a CoD movie. From his buddy list he observes that user B is also watching TV. He invites user B to join him in watching the movie. Both user A and B now can have full trick-play control over the movie. If user A pauses the movie, the movie is automatically paused for user B as well. A.7.7.2 Use case: follow a buddies' zapping behaviour during live TV In another example, user A can see on his buddy list that user B is also watching TV. User A invites user B to take over his remote control. User B accepts and from that point on, he controls both his own as well as user A's zapping behaviour. A.8 Service examples defined by other organizations The above service examples gave a good overview of different IPTV services. However, there are several organizations that have defined service descriptions and use cases which may be variations of the abovementioned or which were not listed above at all. In this clause some references are made to relevant work written by other organizations. A.8.1 Service examples from OMA BCAST OMA BCAST working group has specified an OMA broadcast service. The use cases are mobile specific broadcast use cases, but similar in the nature as TISPAN NGN IPTV broadcast services. The following use cases are considered applicable. When referencing the OMA BCAST requirements, the following OMA BCAST specific words should be replaced throughout the requirements with TISPAN specific words as shown below: • "Mobile Broadcast" replaced with "Broadcast". • "Wireless network" replaced with "network". • "Free-to-air" replaced with "free of charge". ETSI ETSI TS 181 016 V3.3.1 (2009-07) 40 Use Case Clause in [1] Discovering and the available Mobile Broadcast Services and their descriptions 5.1 Protected Mobile Broadcast Services and content delivered within 5.2 Mobile Broadcast Service with auxiliary data and interaction 5.3 Mobile broadcast file distribution - example of news service 5.4 Personalized news broadcast 5.5 Communications related broadcast 5.6 Rich media news broadcast 5.7 Activation of already downloaded Broadcast Service content 5.8 Scalable Viewing of Mobile Broadcast Content 5.9 A.8.2 Service examples from DVB CBMS DVB CBMS (Convergence of Broadcast and Mobile Services) has defined Use Cases that are relevant to the ongoing work in TISPAN WG1 on IPTV (WI 01042). Below is a table listing the DVB use cases that are relevant also to TISPAN IPTV work. Use Case Clause in [i.3] Mobile TV and Radio 5.1 Interactive TV 5.2 Download of audiovisual content/applications/services/ software to devices 5.3 Broadcast of audiovisual streams along with auxiliary information streams to be rendered synchronously and (optionally) containing interaction entry points 5.4 Unattended information download with off-line consumption and interaction entry points 5.5 Broadcast of a common core of services to all terminals, together with a set of services unique to an individual operator 5.6 A.9 Miscellaneous service examples A.9.1 User-Generated Content A feature of the IP-enabled networks on which the offerings are deployed, is the ability for subscribers to upload content they create, and make it available to any other subscriber for viewing, live or offline. Description of the content may also be added or modified by the subscriber who created it. The description should be provided to other subscribers to let them know more about this content when they watch it. The content may be private (for example, the output of home security devices), intended for a restricted audience (for example, family and friends or a TV game show in which the user participates) or intended for unrestricted audience. In this service, the user acts as a content source to the service provider. The service provider then enables distribution of the content through the regular IPTV services, freely available or PPV, and listed on the EPG or accessible via the searching or browsing facilities. Figure A.2 is a conceptual illustration how user generated content reaches watching users. Figure A.2: Conceptual illustration of generation and distribution of user generated content ETSI ETSI TS 181 016 V3.3.1 (2009-07) 41 Different methods of distributing user-generated content into the network may be distinguished: • Upload: the IPTV network receives user-generated content by file upload. • Streaming: the IPTV network receives streaming user-generated content. A.9.1.1 Use case: Home movie sharing, upload For example, user A has recorded a nice home video of his family picnic and has stored it on his PVR. He uploads the video to the network and then publishes the video metadata so others (e.g. family members) can now see the video at their convenience. A.9.1.2 Use case: Home movie sharing, streaming For example, user A has recorded a nice home video of his son's football game and has stored it on his PVR. He receives a request from user B (e.g. a family member) to share the video. User A starts streaming the video into the network and user B can directly watch the video without having to wait. A.9.1.3 Use case: UGC on STB without storage For example, user A has a webcam connected to his STB and is making a movie of him and his daughter playing a game. Since his STB has no storage facilities, the movie is streamed and recorded in the network. User B (e.g. a family member) can now view this recorded stream at a later time instant. A.9.1.4 Use case: Game show participation For example, user A has a webcam connected to his STB and wants to participate in a game show. During the game show, he receives an invite to participate. When user A starts participating, the live feed from his webcam is streamed into the network and merged into the game show broadcast. Other users watching the game show now see user A appearing in the show as participant. There must be an interface to the platform for users to be able to upload or make content available to other users. There must be an interface to the platform that enables other users to access user generated content. These services can be made available to a configurable set of users, or generally available with or without subscription or usage fees. These services may be protected from viewing by unauthorized consumers by DRM mechanisms and must include parental guidance and content ratings where appropriate. NOTE: The management of uploading of UGC may be by a remote device. UGC content information needs to be published to the users (e.g. via EPG), so that the authorized users are able to access the UGC content information (e.g. via EPG), and view the content which they are interested in. The user can use any permitted/authorized device to remotely start another IPTV device uploading UGC content. For example, the user is at work in his office, and he wants to monitor the home circumstance, but the monitoring device is not uploading the content at that moment, so the user uses his mobile phone to request the monitoring device to start uploading the home circumstance content. A.9.1.5 Use case: Live User Generated Content consumption For example, user A is making live User Generated Content broadcasts. Whenever user A has some interesting facts or clips to share, he starts an upstreaming user-generated-content session. User B and user C both have a subscription to the user A broadcasts. They receive a notification when user A comes "on the air". User B happens to be present when he receives the notification, and he watches the user A broadcast in real time. User C is not home, but he has set his C-PVR to record all transmissions from user A. ETSI ETSI TS 181 016 V3.3.1 (2009-07) 42 A.9.2 Games Electronic Games are inherently entertainment service growth areas and include a number of aspects which impact and interact with a service and network operator's IPTV infrastructure. Electronic Games consist largely of the following two products: • Multi-Player games - gamers play against other users over network links (gamers therefore need to first purchase and load the game into their console or game device). • Single player games (Games-on-Demand) - gamers play premium games directly downloadable through broadband connection. A.9.3 Pictures The popularity of digital still and video cameras has contributed to the growth of digital images being stored by consumers on home devices such as PCs or on internet web-sites that offer storage services. In addition there is a growing trend for media devices such as television receivers and DVD players to offer the ability to support the presentation of digital pictures. As such the IPTV platform should also be able to support these media formats thus enabling consumers to share their personal content. The ability to store, manage and view digital pictures is hence an important service that may be offered by service providers in addition to the video related services. The IPTV pictures service is very similar in concept to the user contributed video service except that the contributed content is still images rather than video content. A.9.4 Content markers While watching a content of any IPTV Service (e.g. BC Service, COD, PVR), it should be possible for the user to identify a position in the content (a "content marker") for the later use. The content marker may consist of the point in time of the content marked by user, and additionally, some descriptions or name may be added by the user for himself (personalized content marker description). The user should be able to create and name content markers for actually viewed content or future content (e.g. from EPG) on any IPTV device (e.g. a home TV), and may be able to retrieve, or view content markers from another authorized device (e.g. a mobile phone). The user should be able to manage his content markers, such as deleting, renaming or modifying his content markers or their descriptions. When a user begins to watch content, the related content markers they had set before should be available to the user (e.g. show them via user interface) and then take subsequent actions. For example, if the user selects one of the content markers, the content will skip and start directly from the particular point identified by the content marker. Meanwhile, the content marker information (e.g. user's content marker name and description for this particular user) should be shown to user via EPG (as additional information to generic EPG) or during the content viewing process, etc. A.9.5 User participation Television shows stimulate more and more the participation of users. Starting from simple messaging to a TV show or dialling in by phone, users will become live participants in TV shows with live streaming footage through user webcams and fast, real-time interaction between the participating users and the TV show. Figure A.3 is a conceptual illustration how signals from the studio and participating user(s) are mixed and broadcast to television-watching users. This mixing capability could be offered as a service from a Service Provider to small Content Providers that may not be able to afford this type of advanced mixing capability. NOTE 1: This example does not make any assumption on the mixing capability nor on its architectural location. ETSI ETSI TS 181 016 V3.3.1 (2009-07) 43 Figure A.3: Conceptual illustration of user participation in the generation of content Figure A.4 is a conceptual illustration how users may participate in a game within the context of studio content. NOTE 2: If the studio Content Provider and the gaming Service Provider are not the same party, then there should be a business relationship between the two, or at least an understanding that this type of value added services is allowed. NOTE 3: This example uses the gaming service for illustration purposes only. Figure A.4: Conceptual illustration of user participation with content, "gaming apart together" A.9.6 Synchronization-sensitive interactive services IPTV services like BC and CoD may be used as components for services that combine communication, context and content into a blended user experience. IPTV delays and delay differences may spoil the quality of experience of some of such services. This clause presents examples in which excessive delays would be detrimental to the interactive service experience. NOTE 1: The examples are not IPTV services as such, but interactive services that may use IPTV services as service component. NOTE 2: Some of the examples are also described elsewhere in the present document from different perspectives, e.g. from the perspective of service interactions. ETSI ETSI TS 181 016 V3.3.1 (2009-07) 44 A.9.6.1 Watching Apart Together Figure A.5 illustrates the "Watching Apart Together" use case, which is a form of indirect user participation with content. User A and User B are watching the same soccer match, while simultaneously having an open communication line (e.g. voice, webcam, text chat, etc.) between them. Even though User A and User B are at different locations, they share the same soccer-match experience. However, delay difference will spoil this experience. If User A sees a goal happening a significant time before User B, then User B cannot directly share the excitement of User B about the goal. Delay difference of a second are already significant and spoil the watching-apart-together experience. Goal !!!! Huh ?? Soccer match User 2 User 1 Fast connection Slow connection Watching apart together Figure A.5: Delay differences spoiling a watching-apart-together experience A.9.6.2 Gaming Apart Together A use case similar to watching apart together is gaming apart together. Two viewers may play against each other using a broadcasted game-show as a basis. The gaming-apart-together service could be delivered by a third party that adds value to broadcasted game shows. As responsiveness is essential to such a service, delay differences of as little as 100 ms could already spoil the fairness and hence experience of gaming apart together. A.9.6.3 Remote game show participation A use case related to the previous one is when people at home participate in a live television game show, e.g. by phoning in or using the webcam. Delays of more than a few 50 ms would already impede smooth interaction between the game show and the participant. A.9.7 Use Cases for Hybrid PVR Hybrid PVR service allows combination of network PVR features and local or client PVR functionalities. There exist multiple scenarios or situation when client PVR is disabled to record show (e.g. end device is disconnected in time of scheduled recording or network parameters are not sufficient to stream or missing capacity of storage in local device) IPTV solution should record in network and later deliver to end device. Second use case can apply in case of different end device capabilities (resolution, encoding, etc.) record by nPVR can be done in several formats but appropriate record will be distributed to end device storage to later preview. ETSI ETSI TS 181 016 V3.3.1 (2009-07) 45 A.10 Use case examples for Personalized Channel A Personalized Channel, also called a Virtual Channel or Personal Channel, is a particular list of programs that is scheduled on the basis of the user profile, in which each program is selected from the EPG/ESG that is available to the user, including BC channels or packages and CoD categories. As a result of this scheduling, each program in the personalized channel is allocated to a single time slot, and there may be overlapping or breaks between two time slots, in which cases particular controls on the channel are handled (e.g. content targeting during breaks, PVR triggering when overlapping occurs). After the personalized channel has been configured for a specific user, all programs included in the personalized channel can be played one after another according their time slots respectively, which liberates the user from complex actions about channel switching, movie searching etc. and enhances the user's experience. A.10.1 Use case: personalized channel configuration User A is browsing the EPG. At some moment he presses a key on the remote control and there appears indication information which allows User A to create a personalized channel that fits his personal preference. User A then enters a new name, for example "UserA_Channel001", to identify the personalized channel. For every time slot on the channel, User A can arrange his favourite programs coming from other BC channels, CoD categories, etc. After these steps are completed, a new channel with its program schedule is available to User A. The channel "UserA_Channel001" is then displayed together with other BC channels on the TV whenever User A browses the EPG at a later time. Moreover, User A can modify the existing configuration of his personalized channel, e.g. insert a new program into the list (with a specific time slot), change the schedule time of (on-demand) programs in the list and delete one or more programs from the schedule. A.10.2 Use case: startup with personalized channel A personalized channel, for example "UserA_Channel001" has been created for User A, and when User A turns on the TV, content scheduled at user's current time in his personalized channel is displayed on the screen directly after User A is registered. A.10.3 Use case: content targeting during personalized channel breaks User A has pre-configured his preference, shopping habits etc. in his profile at an earlier time. Now he is watching his personalized channel, for example "UserA_Channel001". If one program has just ended but the next one will be available 5 minutes later (e.g. live program), i.e. there may be a 5-minute break between the two programs. During this time segment there will be no program for User A but a series of commercial advertisements that meets User A's preference and shopping habits. User B has configured to accept recommendation of IPTV content. Now he is watching his personalized channel, for example "UserB_Channel002". During a break, one or more recommended content items are played one by one according to User B's subscription (preference for IPTV content). The recommended programs may include forms of movie highlights, bookmarks, content previews etc. A.11 Use case examples for content preview There are scenarios for service provider to offer content preview to enable the user to evaluate his interest on the content before he could choose to enjoy or pay for it. Content preview may provide part of the content (e.g. segment collections) or much lower resolution of the content or both, so that the users have a quick view on the content, based on which appropriate choice can be made by the users, e.g. to enjoy or order the regular content. ETSI ETSI TS 181 016 V3.3.1 (2009-07) 46 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 content can be provided as a integral part of the offering for CoD service (e.g. trailer, highlights from movie, etc.). For example, access to preview content could be provided, for free, and could be logically coupled with the regular CoD asset (e.g. linked via metadata). Both preview content and CoD should be provided using the same mechanism. In a second use case there is only one content identifier for both preview and regular content (e.g. CoD or BC content). In order to watch or preview this content it is required to indicate whether preview or regular content viewing is requested. Based on this indication either preview or regular content itself is played. It is noted that preview of live content is likely played in real time, showing the live content, e.g. as regular BC channel. A.12 Use case examples for Personalized Service Composition This clause presents use case examples for the personalization of the TV viewing experience for both broadcast and content-on-demand. A.12.1 Use case: personalized broadcast service composition settings User A is watching a football match on a German TV channel. He can configure his preference for English language, so that he receives the English-spoken comments with the match. The user sees in his EPG that also written comments are available in the form of subtitles, so he decides to add these subtitles to the TV channel. He also sees that he can select different camera positions, so during the match User A can regularly switch camera positions to get different views of the match. The next time User A starts watching the German TV channel, his preconfigured preferences ensure that he again receives English spoken comments together with subtitles. A.12.2 Use case: personalized content-on-demand service composition settings User A wants to watch a movie (CoD). He can configure his preference for English language, so that he receives the English-spoken sound track with the movie. The next time User A requests CoD, his preconfigured preferences ensure that he again receives English-spoken sound track. A.13 Use case examples for IPTV Roaming This clause presents use case examples for IPTV roaming. Please note that for home network and visited network. Both Transport Provider and NGN Service Provider are in different domain. A.13.1 Use case: IPTV Roaming without IPTV Service Provider in visited network Alice subscribes IPTV services from SP A in location X. When she moves to location Y where no IPTV Service Provider is in but only Transport Provider and NGN Service Provider, Alice use her IPTV terminal to connect to SP A and to consume IPTV services provided by SP A in home network. ETSI ETSI TS 181 016 V3.3.1 (2009-07) 47 A.13.2 Use case: IPTV Roaming with IPTV Service Provider in visited network Carl subscribes IPTV services from SP A in location X. When she moves to location Y where SP B is in, there are three circumstances as follows. • If SP A and SP B are the same IPTV Service Provider, then Carl use her IPTV terminal to connect to SP A to consume the services provided by IPTV SP A in home network. • If SP A and SP B are not the same IPTV Service Provider and there is business agreement between these two providers. Content in SP A can be delivered to SP B, then she can access and watch the content from SP B. • If SP A and SP B are not the same IPTV Service Provider and there is no business agreement between these two providers. In this circumstance, it is the same as clause A13.1 for Carl to consume IPTV services. ETSI ETSI TS 181 016 V3.3.1 (2009-07) 48 Annex B (informative): Change history Date WG Doc. CR CR Rev CAT Title / Comment Current Version New Version 30-05-08 17bTD299r1 001 B Use cases and requirements on user-generated content 3.0.0 3.0.1 30-05-08 17bTD059r3 002 B Use cases on service interaction 3.0.0 3.0.1 30-05-08 17bTD060r3 003 B Requirements on IPTV services with service interaction 3.0.0 3.0.1 30-05-08 17bTD066r3 004 B WI1059 Use cases on user participation 3.0.0 3.0.1 30-05-08 17bTD120r5 005 B Requirements on Advertising of IPTV service 3.0.0 3.0.1 30-05-08 17bTD119r4 006 B Requirements on immediate messaging 3.0.0 3.0.1 30-05-08 17bTD121r2 007 B Use cases and requirements on Personal Channel 3.0.0 3.0.1 30-05-08 17bTD122r2 008 B Overview of Content Recommendation on IPTV service 3.0.0 3.0.1 30-05-08 17bTD123r3 009 B Requirement on Parent Control 3.0.0 3.0.1 30-05-08 17bTD124r2 010 C Requirements of multiple screen rendering in IPTV 3.0.0 3.0.1 30-05-08 17bTD125r2 011 B Requirements for supporting content bookmark in IPTV 3.0.0 3.0.1 30-05-08 17bTD191r2 012 B Mix between streaming and broadcast flows in the same session 3.0.0 3.0.1 30-05-08 17bTD192r3 013r1 1 B Introduction of PVR controlled by a remote device 3.0.0 3.0.1 30-05-08 17bTD116r3 014 B Release 3 - IPTV requirements 3.0.0 3.0.1 02-07-08 18WTD049r2 015 B Requirements on service interaction 3.0.1 3.0.2 02-07-08 18WTD051r2 016 B Requirements on user generated content 3.0.1 3.0.2 02-07-08 18WTD053r2 017 B Use cases & requirements on synchronization sensitive services 3.0.1 3.0.2 02-07-08 18WTD058r2 018 B Requirements on wholesale IPTV services 3.0.1 3.0.2 02-07-08 18WTD137r1 019 F Clarifying recommendation service 3.0.1 3.0.2 02-07-08 18WTD183r2 020 C Dynamic parental control 3.0.1 3.0.2 02-07-08 18WTD198r1 021 D Editorial changes to uses cases 3.0.1 3.0.2 02-07-08 18WTD250r2 022 C IPTV Content Recommendation Service stage 1 3.0.1 3.0.2 02-07-08 18WTD251r2 023 B Requirements on Push CoD 3.0.1 3.0.2 02-07-08 18WTD088r5 024 B Requirements on UGC 3.0.1 3.0.2 02-07-08 18WTD297r2 025 B Management of UGC upload 3.0.1 3.0.2 02-07-08 18WTD069r3 026 B New requirements of UGC 3.0.1 3.0.2 02-07-08 18WTD087r3 027 B Requirements on IPTV Presence 3.0.1 3.0.2 02-07-08 18WTD184r2 028 B Scalable video coding requirement 3.0.1 3.0.2 All CRs TB approved at TISPAN#18 3.0.2 3.1.1 26-09-08 18bTD104r1 029 B Editorial corrections for Sub-clause A.4.1 of WI1059 3.1.1 3.1.2 26-09-08 18bTD127r2 030 B Use Case on TV Personalization 3.1.1 3.1.2 26-09-08 18bTD074r4 031 B Network Managed PVR Function 3.1.1 3.1.2 26-09-08 18bTD075r3 032 B Requirement of content preview 3.1.1 3.1.2 26-09-08 18bTD088r3 033 B Clarification the concept of Push CoD 3.1.1 3.1.2 26-09-08 18bTD089r3 034 B Requirement of Push CoD 3.1.1 3.1.2 26-09-08 18bTD140r3 035 B Sharing PVR Content and Personal Bookmarks Between Multiple IPTV Users 3.1.1 3.1.2 26-09-08 18bTD200r2 036 F User profiling 3.1.1 3.1.2 26-09-08 18bTD201r2 037 F Time-shift TV service 3.1.1 3.1.2 26-09-08 18bTD204r2 038 F Clarifications of relationship with the third party CP 3.1.1 3.1.2 26-09-08 18bTD090r6 039 B Requirement of network initiated service 3.1.1 3.1.2 26-09-08 18bTD219r3 041 B Release 3 - IPTV requirements 3.1.1 3.1.2 26-09-08 18bTD220r3 042 B Hybrid PVR service 3.1.1 3.1.2 05-11-08 19WTD052r2 043 B User Generated Content Synchronization 3.1.2 3.1.3 05-11-08 19WTD048r2 044 B User Generated Content Amateur TV 3.1.2 3.1.3 05-11-08 19WTD049r3 045 B User Generated Content in Real Time 3.1.2 3.1.3 05-11-08 19WTD054r2 046 B Personalized Stream Composition Definition 3.1.2 3.1.3 05-11-08 19WTD055r2 047 B Personalized Stream Composition Requirements 3.1.2 3.1.3 05-11-08 19WTD098r4 048 B User Cases for IPTV Roaming 3.1.2 3.1.3 14-11-08 CRs 029 to 048 except 040 TB approved at TISPAN#19 and clean-up by ETSI Secretariat 3.1.3 3.2.0 28-11-08 19bTD111r4 049 B Location Independent Bookmarks 3.2.0 3.2.1 28-11-08 19bTD127r2 050 B Requirements of IPTV Roaming 3.2.0 3.2.1 28-11-08 19bTD177r6 051 F Clarifications of relationship with the third party CP 3.2.0 3.2.1 28-11-08 19bTD057r6 052 B Requirement on Reuse Media Channel 3.2.0 3.2.1 23-01-09 19tTD204r3 053 C Linking Presence Information, IPTV channels, content and personalized EPG services 3.2.1 3.2.2 23-01-09 19tTD217r3 054 B Channel Change Clarifications 3.2.1 3.2.2 27-02-09 20WTD095r1 055 B Editorial Alignment 3.2.2 3.2.3 27-02-09 20WTD105r2 056 F Cleanup of IPTV Bookmark Terminology 3.2.2 3.2.3 27-02-09 20WTD119r1 057 F Numbering correction of stage1 TS 3.2.2 3.2.3 27-02-09 20WTD287r2 058 D Proposal to editor's notes 3.2.2 3.2.3 27-02-09 20WTD289r1 059 B Include Requirement and use case for IPTV service replication 3.2.2 3.2.3 27-02-09 20WTD077r2 060 C Revision of clause 5.16 - Third party content and wholesale content aggregation 3.2.2 3.2.3 27-02-09 20WTD078r2 061 C Revision of clause A6 - Third Party Content and wholesale content aggregation 3.2.2 3.2.3 Publication 3.2.3 3.3.1 ETSI ETSI TS 181 016 V3.3.1 (2009-07) 49 Annex C (informative): Bibliography • ETSI TR 102 473: "Digital Video Broadcasting (DVB); IP Datacast over DVB-H: Use Cases and Services". • ETSI TS 102 034: "Digital Video Broadcasting (DVB); Transport of MPEG-2 TS Based DVB Services over IP Based Networks". • CM-IPTV0430: "Commercial Requirements for Fast Channel Change". ETSI ETSI TS 181 016 V3.3.1 (2009-07) 50 History Document history V3.3.1 July 2009 Publication
|
11bfd00eff57f176f6d38989d38a2789
|
181 014
|
1 Scope
|
The present document specifies the generic network transport capability requirements to support IPTV services, including Broadcast TV and Content on Demand services, based on the characteristics of IPTV services. The present document does not describe the IPTV service per se but the network capabilities that are needed to support these services by specifying the network requirements related to the transport layer, to support these services, taking terminal capabilities into account. Account is therefore taken of the specifications of IPTV services of other organizations as the DVB.
|
11bfd00eff57f176f6d38989d38a2789
|
181 014
|
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. For online referenced documents, information sufficient to identify and locate the source shall be provided. Preferably, the primary source of the referenced document should be cited, in order to ensure traceability. Furthermore, the reference should, as far as possible, remain valid for the expected life of the document. The reference shall include the method of access to the referenced document and the full network address, with the same punctuation and use of upper case and lower case letters. NOTE: While any hyperlinks included in this clause were valid at the time of publication ETSI cannot guarantee their long term validity.
|
11bfd00eff57f176f6d38989d38a2789
|
181 014
|
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] ETSI TS 181 016: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Service Layer Requirements to integrate NGN services and IPTV". [2] ETSI TS 102 034: "Digital Video Broadcasting (DVB); Transport of MPEG-2 TS Based DVB Services over IP Based Networks". [3] ITU-T Recommendation Y.2011: "General principles and general reference model for Next Generation Networks". [4] ETSI TS 102 005: "Digital Video Broadcasting (DVB);Specification for the use of Video and Audio Coding in DVB services delivered directly over IP protocols". [5] ETSI TS 187 001: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); NGN SECurity (SEC); Requirements". ETSI ETSI TS 181 014 V2.0.0 (2007-11) 6
|
11bfd00eff57f176f6d38989d38a2789
|
181 014
|
2.2 Informative references
|
[6] ETSI TR 102 033: "Digital Video Broadcasting (DVB); Architectural framework for the delivery of DVB-services over IP-based networks".
|
11bfd00eff57f176f6d38989d38a2789
|
181 014
|
3 Definitions and abbreviations
| |
11bfd00eff57f176f6d38989d38a2789
|
181 014
|
3.1 Definitions
|
For the purposes of the present document, the following definitions apply: Broadcast TV: television programming transmitted and intended for reception by anyone within range of the transmitter or lawfully connected to a cable distribution system but where the consumer has no control over the content or timing of what he receives, apart from the ability to select a particular channel NOTE: It is sometimes referred to as "Linear TV". Consumer: domain where the IPTV services are consumed NOTE: The consumer domain may consist of a single terminal used directly for service consumption or may be a complex network of terminals and related devices, including consumer operated mobile devices. The domain itself may also be a mobile end device. In this case, the delivery system of a transport provider would be a Wireless Wide Area Network (WWAN). A single consumer domain may be connected via two or more networks to a number of service providers obtaining content from multiple content providers. Consumer Network: network owned and operated by an end-user relying on the services of a transport provider for external connectivity; in this context, the definition includes home networks, wireless "hot spots", hotel networks, etc. Content on Demand (CoD): Users can select their required content with the assistance of the Electronic Programme Guide (EPG) at the user preferred time NOTE: The content is then transmitted uniquely (unicast) to that consumer who can usually use VCR-like functionalities (for example, fast-forward, rewind or pause) to control their viewing of the content. A special form of Content on Demand (CoD) is Video on Demand (VoD). Content Provider: entity that owns or is licensed to sell content or content assets Electronic Programme Guide (EPG): assistance tool which helps users to locate the content they want and to facilitate the selection of IPTV services for watching, recording, etc. IPTV Service Provider: entity that offers IPTV services to the Customers making use of the services capabilities provided by the NGN Service Provider Service Provider: entity providing a service to the subscriber NOTE: Different types of service providers may be relevant for television services on IP, see IPTV Service Provider and NGN Service Provider. Transport Provider: entity connecting consumers and Service Providers NOTE: The delivery system usually is composed of access networks and core or backbone networks, which may use a variety of network technologies and be owned by a number of different operators. VCR functions: common functionalities of a video cassette recorder, such as select/cancel, start, stop, pause (with or without freeze frame), fast forward, reverse, scan forward or reverse (both with or without image), and setting and resetting memory marks ETSI ETSI TS 181 014 V2.0.0 (2007-11) 7
|
11bfd00eff57f176f6d38989d38a2789
|
181 014
|
3.2 Abbreviations
|
For the purposes of the present document, the following abbreviations apply: CoD Content on Demand DVB Digital Video Broadcasting EPG Electronic Programme Guide (see also IPG) HD High Definition (TV) IP Internet Protocol IPG Interactive Programme Guide (see also EPG) IPR Intellectual Property Rights IPTV Internet Protocol Television NGN Next Generation Network QoS Quality of Service RTSP Real-Time Streaming Protocol SD Standard Definition (TV) TV Television UE User Equipment VCR Video Cassette Recorder WWAN Wireless Wide Area Network
|
11bfd00eff57f176f6d38989d38a2789
|
181 014
|
4 Overview
|
The present document describes the requirements on the TISPAN NGN transport layer to support IPTV services irrespective of the service control mechanism employed. Several standards on IPTV are evolving in other standards organizations, including DVB, ATIS IIF and OMA (see annex C for more information). The ETSI TISPAN architecture shall provide the necessary transport capabilities to support the requirements of the main ongoing standards on IPTV. The present document notes the ongoing developments in this area as well as existing deployments and describes the requirements for the following network transport capabilities: • Admission control. • Support of Multicast and Unicast. • Security. • User Data. • Accounting. • NAT traversal. • Resource management. The present document is complimentary to TS 181 016 [1] that contains several examples of relevant IPTV services.
|
11bfd00eff57f176f6d38989d38a2789
|
181 014
|
5 IPTV Context Requirements
|
Many of the following requirements are largely derived from the ATIS IIF document, as generic requirements relevant for the IPTV context. In these, the word "architecture" has been replaced by "solution", since they are not so much functional requirements but rather related to the service that IPTV is to provide to the user. Other requirements specific to the present document have also been included. 5.1 The IPTV solution shall allow for two-way communications between the Service Provider and a UE within the consumer network. 5.2 The IPTV solution shall support services delivered to a consumer network from one or more service providers over an IP transport stream. ETSI ETSI TS 181 014 V2.0.0 (2007-11) 8 5.3 The IPTV solution shall allow the delivery of multiple COD content profiles e.g. HD, SD and multichannel audio to the consumer. 5.4 The IPTV solution shall be capable of supporting multiple IP transport streams providing services from one or more service providers to a single consumer network. 5.5 The IPTV solution may support the delivery of multiple services over common managed IP transport with a controllable IP Quality of Service (QoS). 5.6 The IPTV solution shall support the individual addressability of devices acting as UEs within the consumer network. 5.7 The IPTV solution shall include a mechanism for user provisioning, profiling and registration. 5.8 The IPTV solution shall provide a mechanism to protect privacy of the consumer. 5.9 The IPTV solution shall ensure that the storage and management of user related data is in accordance with the relevant national regulations. 5.10 The IPTV solution shall make efficient use of network transport capabilities.
|
11bfd00eff57f176f6d38989d38a2789
|
181 014
|
6 Network transport capabilities required
| |
11bfd00eff57f176f6d38989d38a2789
|
181 014
|
6.1 Admission Control
|
The TISPAN NGN transport stratum must offer an Admission Control solution for admission of IPTV services over the Access and Core network resources from the consumer network to the service source In particular, the Admission Control solution must be: • accurate (i.e. admits the right multicast or unicast sessions on the right resources); • bandwidth efficient (i.e. only rejects multicast or unicast sessions which are indeed in excess of the current network capacity and accept as many multicast or unicast sessions as possible that can indeed fit in the current network capacity); • reactive (i.e. adjust fast to changes in network conditions such as failure or dynamic rerouting and adjust quickly to changes in shared resource usage such as a UE switching between a multicast and unicast IPTV services); • able to handle resources that can be used by either multicast or unicast (e.g. it would not be feasible to partition the available access line bandwidth between unicast only and multicast only IPTV services); and • able to handle resources shared by other non IPTV services (e.g. internet data and VoIP and other communication services).
|
11bfd00eff57f176f6d38989d38a2789
|
181 014
|
6.2 Multicast and Unicast Support
|
The use of Multicast improves network resource utilization and QoS in large-scale IPTV deployments. . Therefore the access and core networks should have multicast transport and routing capability. The related multicast protocol, multicast management and control should be supported in access and core networks. IPTV solutions shall be able to make use of the underlying multicast facility if it is available (e.g. streaming servers and other service layer elements). Content delivery of Multicast and Unicast streams types are: • Multicast contents delivery: - Streaming type. ETSI ETSI TS 181 014 V2.0.0 (2007-11) 9 • Unicast contents delivery: - Streaming type. - Download type.
|
11bfd00eff57f176f6d38989d38a2789
|
181 014
|
6.3 Security
|
The security requirements for IPTV are described in clause 4.13 of TS 187 001 [5].
|
11bfd00eff57f176f6d38989d38a2789
|
181 014
|
6.4 User data
|
It shall be possible to define User profiles for access to IPTV services.
|
11bfd00eff57f176f6d38989d38a2789
|
181 014
|
6.5 Accounting
|
It shall be possible to collect appropriate accounting data.
|
11bfd00eff57f176f6d38989d38a2789
|
181 014
|
6.6 NAT Traversal
|
A mechanism shall be provided for NAT traversal. ETSI ETSI TS 181 014 V2.0.0 (2007-11) 10 Annex A (informative): Admission Control for Multicast and Unicast The individual services within the general group of IPTV services can be divided into those that multicast-based and those that are unicast-based. Both groups can present a dynamic demand on the network. The first group of Media Broadcast (multicast) services normally require as much of the network as possible to be provisioned with sufficient capacity to support the total number of multicast streams via preprovisioned multicast routing that will undergo admission control checks at the time of the preconfiguration. However parts of the network (particularly the access network and access link to the consumer network) cannot be preconfigured to simultaneously carry all possible multicast streams and therefore network resources need to be utilized dynamically in these parts of the network and will require admission control at the time of service selection by the user. It should be noted that an individual IPTV multicast stream would normally utilize preconfigured multicast resources for part of its transport path (e.g. over the core from the head end to the IP edges and possibly on to all access nodes) and utilize dynamically allocated resources for the remaining parts of the multicast tree (e.g. in the access network and link to the consumer network). Not all multicast streams will follow the same network partition of preconfigured and dynamically allocated resources. For example the most popular broadcast channels may use a preconfigured routing allocation from the head end to all access nodes and only use dynamic resources in the home network and on the access link, whereas more specialized channels may use preconfigured from the head end to the IP edge and dynamic resources from the IP edge to the home network.. The second group of Content on Demand (unicast) services are allocated only when required and therefore require mechanisms to control load. Content on Demand (CoD) services have a number of particular characteristics: • The take up rate of a CoD service is very hard to predict. It can vary extremely fast and is highly dependent on many parameters which are completely outside the network operator's control such as attractiveness of the accessible content (film catalogue), promotional offers, special programs (sports event, movie release), etc. • The bandwidth of a single CoD session is fairly high (1,5 Mbit/s to 15 Mbit/s) relative to link speeds found in some segments of the Core network (e.g. 1 Gb/s Ethernet) close to the Access Network. For example, assuming 4 Mbit/s per CoD stream, it only takes 500 users simultaneously using the CoD service (out of the 10 000 s users attached to an IP Edge Device) to entirely consume the bandwidth of two 1 Gb/s Ethernet links which may be connecting the IP Edge Device to the Core network. If non-CoD traffic is also consuming bandwidth, or if additional CoD users also request CoD content, serious congestion will occur on the Core links to the IP Edge Devices resulting in very serious degradation to all the CoD users (possibly to the point where they cannot watch the program at all because of Video coding sensitivity to loss). Failure of one of the two uplinks of the IP Edge Devices means that congestion occurs even earlier (from about 250 simultaneous users, out of 10 000 s). • The CoD content may be distributed from a limited number of CoD content locations, each feeding potentially a very large CoD traffic aggregate into the core, where the speeds of the CoD aggregate is comparable, and can even exceed, the link speeds used in the core network (e.g. 10 Gb/s). For example, a cluster of CoD Pumps may be able to collectively stream from one location several thousands of CoD streams simultaneously into the Core network. If more than 2 500 of these streams happen to transit through the same 10 Gb/s Core link on their way to their respective destination CoD users (say because perhaps another 10 Gb/s link just went down), serious congestion will also be encountered on this core link. ETSI ETSI TS 181 014 V2.0.0 (2007-11) 11 Core networks are typically engineered such that they can deal with the peak load in the absence of failure as well as under most common failure situations. However, it is not always cost-economical to engineer each and every segment of the network so that it can cope with the peak load under less common but more catastrophic failure situations (e.g. multiple simultaneous failures). Similarly, it is not always cost economical to engineer each and every segment of the network to cope for the absolute worst peak load and absolute worst load distribution (focused overload). In the face of such catastrophic failure and/or unanticipated peak load, traditional Internet-style networks simply offer a degraded service where each user is left with reduced throughput and is expected to adjust accordingly. However, as Next Generation networks are intended to carry non-elastic multimedia applications with strong Service Level Agreements (such as the performance requirements of TS 102 034 [2]), it is important that those networks can react more appropriately in the face of catastrophic failure and/or unanticipated peak load in a segment of the network. In particular, it is essential to avoid a situation where all/many sessions all get affected to the point where they become useless because they all get insufficient throughput. The approach to avoid this is through the support of Admission Control whereby some subset of the sessions (selected according to some operator policy) would be denied service in order to leave sufficient capacity to the remaining sessions. ETSI ETSI TS 181 014 V2.0.0 (2007-11) 12 Annex B (informative): Other considerations The following requirements should be also considered: • User traffic model including other service's traffic (e.g. VoIP, Internet access). • Several qualities of video services, and bandwidths of video traffic (e.g. MPEG, H.264 stream). • Number of channels offered as the IPTV services. As a reference, ITU-T Recommendation Y.2011 [3]. Appendix I describes following IPTV requirements. Typical bandwidth requirements for support of each of the services proposed are: • HDTV: 20 Mbit/s × 3 channels; • Videophone: 4 Mbit/s × 4 channels; • Internet service: 20 Mbit/s; • High Quality Voice Service: 2 Mbit/s. EXAMPLE Total bandwidth: approximately 100 Mbit/s. ETSI ETSI TS 181 014 V2.0.0 (2007-11) 13 Annex C (informative): Existing IPTV specifications Work is proceeding in a number of organizations on the definition of IPTV services and the mechanisms by which they can be provided. For example: • TR 102 033 [6] describes an architectural framework for the delivery of DVB services over IP based networks and includes descriptions of IPTV services; • TS 102 034 [2] specifies the transport of MPEG2 based DVB services over IP based networks and defines RTSP profiles for Live Media Broadcast (LMB), Media Broadcast with Trick Modes (MBwTM) and Content on Demand (CoD); and • TS 102 005 [4] specifies the use of Video and Audio Coding in DVB services delivered directly over IP protocols (i.e. not involving an MPEG2 transport stream). In addition the ATIS IIF has produced an IPTV requirements document. ETSI ETSI TS 181 014 V2.0.0 (2007-11) 14 History Document history V2.0.0 November 2007 Publication
|
885db1f16a0263596c8657865a6cf498
|
182 025
|
1 Scope
|
The present document provides architecture and functional requirements for business trunking for the Next Generation Network. The present document also specifies the protocol requirements for the NGCN to attach to the NGN (in particular the IM CN subsystem) and also any protocol requirements relation to application servers provided in support of business trunking. Business trunking is a set of NGN capabilities that may be applied to communications between Next Generation Corporate Networks (NGCN) using the NGN as a transit. The structure of the present document reflects the historical structure of previous versions of it. All references to ETSI TS 124 525 [30] are intended to be to the entire contents of the referenced document, which now forms the contents of the present document, and not to any part which might be implied by any headings within the present document.
|
885db1f16a0263596c8657865a6cf498
|
182 025
|
2 References
| |
885db1f16a0263596c8657865a6cf498
|
182 025
|
2.1 Normative references
|
References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the reference document (including any amendments) applies. 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. The following referenced documents are necessary for the application of the present document. [1] Void. [2] Void. [3] Void. [4] Void. [5] Void. [6] Void. [7] Void. [8] Void. [9] Void. [10] Void. [11] Void. [12] Void. [13] Void. [14] Void. [15] Void. [16] Void. ETSI ETSI TS 182 025 V3.4.0 (2015-10) 6 [17] Void. [18] Void. [19] Void. [20] Void. [21] Void. [22] Void. [23] Void. [24] Void. [25] Void. [26] Void. [27] Void. [28] Void. [29] Void. [30] ETSI TS 124 525: "Universal Mobile Telecommunications System (UMTS); LTE; Business trunking; Architecture and functional description".
|
885db1f16a0263596c8657865a6cf498
|
182 025
|
2.2 Informative references
|
References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the reference document (including any amendments) applies. NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee their long term validity. The following referenced documents are not necessary for the application of the present document but they assist the user with regard to a particular subject area. Not applicable.
|
885db1f16a0263596c8657865a6cf498
|
182 025
|
3 Definitions and abbreviations
| |
885db1f16a0263596c8657865a6cf498
|
182 025
|
3.1 Definitions
|
For the purposes of the present document, the terms and definitions given in ETSI TS 124 525 [30] apply.
|
885db1f16a0263596c8657865a6cf498
|
182 025
|
3.2 Abbreviations
|
For the purposes of the present document, the abbreviations given in ETSI TS 124 525 [30] apply.
|
885db1f16a0263596c8657865a6cf498
|
182 025
|
4 Overview
|
The provisions of the present document are contained in ETSI TS 124 525 [30].
|
885db1f16a0263596c8657865a6cf498
|
182 025
|
5 Functional architecture
|
The provisions of the present document are contained in ETSI TS 124 525 [30]. ETSI ETSI TS 182 025 V3.4.0 (2015-10) 7
|
885db1f16a0263596c8657865a6cf498
|
182 025
|
6 Procedures
|
The provisions of the present document are contained in ETSI TS 124 525 [30].
|
885db1f16a0263596c8657865a6cf498
|
182 025
|
7 Use of transport functions
|
The provisions of the present document are contained in ETSI TS 124 525 [30].
|
885db1f16a0263596c8657865a6cf498
|
182 025
|
8 Security
|
The provisions of the present document are contained in ETSI TS 124 525 [30].
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.