hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
a51f761c27385e5a8c90041b2c701012 | 182 027 | 8.5.0 PVR use for non-BC services | Although the procedures in the following clauses focus on PVR-recording of BC services (clause 8.3), they may be applicable to the recording of other IPTV services. Depending on the service, specific requirements on e.g. user subscription and profile may apply. Examples such as Content on Demand (clause 8.4) and Person... |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 8.5.0A Signalling Flows for PVR Using Impulsive Request | Figure 32 depicts the typical steps that occur when the UE makes an impulsive request for a PVR service. Core IMS SCF MF (1).Playlist communication during CoD session initiation(in Clause 8.4.6) (4).New content delivery (2).Request for content switch (3). Content switch response UE ETSI ETSI TS 182 027 V3.5.1 (2011-03)... |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 8.5.1 Network PVR service procedures | Network PVR (N-PVR) service is used by the UE to ask for a capture of live content by the network and to access it later on. The N-PVR service procedures comprise two major steps: Step 1: Request for N-PVR Service Capture Request. The UE sends an N-PVR content capture request to the SCF. This request can be: • an impul... |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 8.5.1.1 Signalling Flows for Network-PVR Service Capture Request | This can be handled as an off-line request or as an impulsive request. |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 8.5.1.1.1 Signalling Flows for Network-PVR Using Impulsive Request | Refer to clause 8.5.0A. |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 8.5.1.1.2 Signalling flows for the Network-PVR off-line capture request | Refer to clause 8.5.0B. ETSI ETSI TS 182 027 V3.5.1 (2011-03) 93 |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 8.5.1.2 Signalling flows for Network-PVR content session | Figure 34 depicts the typical steps that occur when the UE makes a request to retrieve/resume previously recorded N-PVR content. NOTE: If the N-PVR content has been previously downloaded to the UE, it can watch it locally without using the following procedures. Figure 34: Signalling flows for Network-PVR content sessio... |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 8.5.2 Client PVR service procedures | Client PVR (C-PVR) service is used by the UE to ask for a capture of live content locally or by the remote client device and to access the recorded content later on. NOTE 1: In case of local capture requests that do not need network IPTV management or authorization, the recording can be handled locally on the client wi... |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 8.5.2.1 Signalling Flows for Client-PVR Service Capture Request | |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 8.5.2.1.1 Signalling Flows for Client-PVR Using Impulsive Request | Refer to clause 8.5.0A. |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 8.5.2.1.2 Signalling flows for the Client-PVR off-line capture request | Refer to clause 8.5.0B. |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 8.5.2.2 Signalling flows for Client-PVR recording session | Figure 34A depicts the typical steps when the SCF makes a request to initiate the recording of the content. For the scenario when the UE makes an impulsive request for a C-PVR service, the existing BC session may be reused if one exists instead of the following procedures. ETSI ETSI TS 182 027 V3.5.1 (2011-03) 95 Figur... |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 8.5.3 PVR content update procedures | Figure 34B: PVR content update procedure UE CORE IMS SCF SSF (1). PVR content update request (3). PVR content update response (2) Apply PVR Information update (1). PVR content update request (3). PVR content update response Core IMS BC-SCF UE C-PVR-SCF (1) Notification procedure using signalling path (in Clause 8.11.1.... |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 8.6 Time Shift service procedures | The Time Shift service is used by the UE to view a programme that has already occurred or started. It is necessary for the IPTV operator to store a programme in order for this service to be available. Note that unlike N-PVR it is not necessary for a UE to indicate that a programme shall be recorded but it is not always... |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 8.7 Preview procedures | 8.7.1 Preview procedures for BC service The preview content of BC service may have lower bit-rate compared with the corresponding regular BC content, hence requires lower bandwidth. The BC content preview procedures may take place in either one of the following cases: 1) Multi-screen BC preview: Preview the BC service ... |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 8.7.1.1 Session initiation procedures for multi-screen BC preview | The procedures described in clause 8.3.1.1 apply for multi-screen BC preview session initiation, with the following differences: • The initiation request carries the BC service IDs available for preview, and the maximum bandwidth needed for muti-screen preview. In case there is a primary stream (i.e. a regular BC servi... |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 8.8 Parental control procedures | On receipt of a CoD session initiation request as defined in 8.4.1 or BC session initiation request as defined in clause 8.3.1, the SCF shall chek the following parameters in IPTV user profile in the following order: • If the requested content is not compatible with parental control level or PC-ClassificationRestrictio... |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 8.9 UGC procedures | |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 8.9.1 Overview | There are two types of UGC procedures: • creation of the User Generated Content: this type of procedure allows a user to declare and upload/upstream his/her own content to the network; • watching of User Generated Content: this type of procedure allows a user to select and watch User Generated Content. NOTE: The clause... |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 8.9.2 UGC creation procedure | The UGC creation procedure comprises four major steps: Step 1: Declaration of User Generated Content • The UE sends a User Generated Content creation request to the SCF and receives a content ID for the UGC from the SCF. The content ID is independent of the address where the UGC can be retrieved by other UEs. Step 2: P... |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 8.9.3 UGC watching procedure | The UGC watching procedure comprises two major steps: Step 1: Selection of UGC • The selection of the UGC may be done through the SSF. Alternatively, UGC selection can be triggered by a content recommendation or a notification. The UE may also pre-select UGC that has already been declared and published (clause 8.9.2, s... |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 8.9.4 UGC removal procedure | The user can decide to remove one of his/her UGC by using UGC description procedure as defined in clause 8.9.2. The operator can decide to remove the created UGC at any time due to local or legal policies. It may inform the user that has created the UGC by using the Notification procedure as defined in clause 8.11.1.1 ... |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 8.10.1 Generic Procedure for PCh service | Figure 34F shows the major steps enabling the PCh service. ETSI ETSI TS 182 027 V3.5.1 (2011-03) 104 Figure 34F: Major steps for PCh service 1) The PCh declaration procedure takes place between UE and SCF. The UE sends a PCh Declaration Request to the SCF via Core IMS, and the initial PCh information, containing the PC... |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 8.10.2 MF Option for PCh Service Provision | Figure 34G depicts the PCh service procedure that utilizes a single unicast session for all PCh content items, including BC. Figure 34G: MF option for PCh service provision 1) The PCh session initiated by the UE, as similar with the one defined in 8.4.1 for CoD initiation procedure with the following differences: - The... |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 8.10.3 UE Option for PCh Service Provision | Figure 34H depicts the signalling flow for UE option of PCh service provision, which enables the SCF to control UE to alter the PCh session between unicast and multicast depending on the type of viewed item. Figure 34H: UE option for PCh service provision 1) The PCh session initiated by the UE according to the type of ... |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 8.11.1.1 Notification procedures using signalling path | Figure 35 depicts the typical steps that occur when the SCF wants to notification the user on a particular event using signalling path. Figure 35: notification procedure using signalling path Priori to the procedure, it is considered that the SCF has detected an event that would cause the notification to be sent to the... |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 8.11.1.2 Notification procedures using multicast media path | Figure 35A depicts the steps that occur when the SCF and MF use the multicast media path to send a notification to users who are watching a specific BC channel. Figure 35A: notification procedure using multicast media path When receiving a notification trigger event from external entity (e.g. SCF in charge of BC servic... |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 8.12 Procedures for IPTV User Profile Configuration | This clause describes the generic procedures for IPTV user profile configuration. These procedures may be used in conjunction with other procedures for delivery of other IPTV services - e.g. Content recommendation service, N-PVR. Figure 35B: User Profile Configuration procedures 1) The user (on UE) makes a request to t... |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 8.13 Content Recommendation service procedures | The Content Recommendation Service (CRS) is used for providing recommendations to IPTV users or user groups. The content recommendation service may make recommendations to user/groups based on different criteria which include user profile e.g. preferences settings, current viewing habits of user, etc. The CRS service p... |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 8.14 Advertising (Ad) service procedures | There are several types of procedures in Advertising (Ad) service, including: 1) Targeted ad insertion: some selected ad content is provided to the UE during the IPTV content playback, based on the user profile (user preference, shopping habits, location information, etc.) and the IPTV service status (e.g. current BC p... |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 8.14.1 Generic Procedures for targeted ad insertion (TAI) | Ad insertion implies that an IPTV sesssion exists prior to the insertion time. The targeted ad is selected by the SCF with regard to user profile (e.g. shopping habits) or other criteria, e.g current BC program. IPTV content and ad content in the context of ad insertion can be described as: • IPTV content: the content ... |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 8.14.2 Generic Signalling for Targeted Ad insertion | NOTE: The term Ad Server is used for the generic purpose of Ad selection and/or control, and it can be implemented in SCF or externally, based on the examples in annex E. |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 8.14.2.1 Signalling flows for TAI at UE side | When the ad insertion takes place at UE side, the UE is informed about ad insertion information from SCF. The UE may initiate individual session request for Ad content, which implies that multiple sessions exist on the UE during the ad insertion time. Other means for retrieving the content are also envisioned. Figure 3... |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 8.14.2.2 Signalling flows for TAI at MF side | When the ad insertion takes place at MF, the MF is informed of the ad insertion information from the SCF. The MF performs the ad insertion, i.e. delivery ad content to the UE during the ad insertion time of IPTV content play back. Figure 37 depicts the typical steps when MF is informed of the ad insertion indication. F... |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 8.15 Procedures for inter-destination media synchronization | |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 8.15.1 MSAS - SC | |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 8.15.1.1 SCF-based media synchronization | |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 8.15.1.1.1 Mapping 1: SC in UE | Figure 38 provides an overview of the information flows for inter-destination content synchronization according to Mapping 1 from clause 5.4.2. Figure 38: Procedure for inter-destination content synchronization (1) IPTV session initiation, e.g. BC session initiation according to clause 8.3.1.1, or CoD session initiatio... |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 8.15.1.1.2 Mapping 2: SC in Transport | The procedures according to Mapping 2 from clause 5.4.2 are the same as above with the following changes: • Step (1) is not applicable. • Tunnelling over the broadcast session is not applicable. • The MSAS is an elementary function of the SCF or a stand-alone (possibly distributed) functional entity. • The SC is an ele... |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 8.15.2 MSAS - SC' | Figure 38A shows a flow for the exchange of synchronization status information between a media-stream-modifying Synchronization Client (SC') and an MSAS. ETSI ETSI TS 182 027 V3.5.1 (2011-03) 117 SC’ (1) Sync Initiation Request MSAS (2) Sync Initiation Response (3) Sync Status Information Repeat (5) Sync Termination Re... |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 8.16 Signalling flows for network-controlled trick play | Figure 39 provides the signalling flow for controlling trick play of a Broadcast TV channel, CoD, N-PVR or other IPTV session by a network element. In order to apply trick modes to a Broadcast TV channel, a BC TV with trick play session must first be established. ETSI ETSI TS 182 027 V3.5.1 (2011-03) 118 Figure 39: Sig... |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 8.17.1 Push CoD session | Push CoD session comprises two main steps: • Step 1: The SCF initiates the CoD content download from MF to UE. The detailed procedure can be referred to clause 8.18.2. • Step 2: The UE selects the media content in its storage device which has been downloaded from MF and views it. NOTE: The content is stored on the UE a... |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 8.18.1 Signalling Flows for UE-initiated Unicast Content Upload/Download | Figure 39A depicts the typical steps that occur when the UE initiate a request to upload/download content by unicast. Figure 39A: UE-initiated unicast content upload/download session initiation 1) The UE initiates an upload/download request to the SCF. 2) The session initiation request is routed by the Core IMS entitie... |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 8.19 Multicast Content Download Procedures | Multicast Content Download Procedures are out of scope of the present document. |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 8.20 Signalling flows for restricted trick play | The restricted trick play procedure can be used by network to disallow specified trick play functions on any segment of the content. Figure 39C depicts the typical signalling flow of restricted trick play. Figure 39C: procedure of restrict trick play 1) Broadcast TV with trick play, CoD session initiation or other IPTV... |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 8.21 Shared Service Control (SSC) procedures | |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 8.21.1 Overview | Shared Service Control procedures allow a group of users sharing the control commands related to a service (e.g. BC, CoD) and correlating the sessions related to the same service. The virtual place established to share the services is called an SSC room. This room has only one service running at a time; this service ma... |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 8.21.2 Room creation procedure for SSC | Figure 39E depicts the typical steps that occur when the UE creates an SSC room and publishes related information. UE A (IPTV) UE B (IPTV) MF IPTV SCF SIP SESSION A SIP SESSION B Content Content ETSI ETSI TS 182 027 V3.5.1 (2011-03) 123 Figure 39E: SSC Room Creation procedure 1A) The UE sends a SSC Room Creation Reques... |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 8.21.3 Room selection procedure for SSC | The room selection procedure comprises the following steps: Step 1: SSC room selection • Using the SSC room identifier, the UE selects the room it wants to join and retrieves associated parameters, such as the SSC room policy. Step 2: Entering the selected SSC room • The UE enters the room and initiates a service sessi... |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 8.21.4 Shared service control procedures | Depending on the SSC room policy, one or more UEs may perform room moderation tasks and/or content control. This can include adding and removing content to the SSC room. Additionally service commands, such as CoD trick play or BC channel changes, can be performed for the shared service in the SSC room. The change in se... |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 8.21.4.1 Shared BC channel changes | Depending on the SSC room policy, when a BC service is shared in an SSC room, the channel changes issued by an UE will be reflected towards all others UEs involved in the shared service. The SSC room policy indicates how conflicts in case of non-overlapping BC service packages are handled. For example, if all UEs invol... |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 8.21.4.2 Shared CoD trick play commands | Depending on the SSC room policy, when a CoD service is shared in an SSC room, the trick play commands issued by an UE will be reflected towards all others UEs involved in the shared service. The SSC room policy indicates how conflicts in case of (near-)simultaneously received trick play commands are handled. Figure 39... |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 8.21.5 Room deletion procedure for SSC | Figure 39I depicts the typical steps that occur when the UE deletes an SSC room. Figure 39I: SSC Room Deletion procedure 1) The UE sends a SSC Room Deletion Request through the Core IMS to the SCF. This request may contain information such as: - the SSC Room Identifier of the to-be-deleted SSC room; - optionally, the s... |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 8.22 Personalized Service Composition (PSC) procedures | |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 8.22.1 General | This clause describes procedures for the PSC service where multiple BC and or CoD sessions are composed into a single Personalized Service Composition. Existing BC/CoD procedures are used for session setup in order to compose the PSC. Additional steps include selection and configuration of the PSC between the UE and SS... |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 8.22.2 PSC session initiation | Figure 39Ia depicts the typical steps that occur during the establishment of a Personalized Service Composition session and its constituting BC/CoD sessions. Figure 39Ia: Signaling flows for Personalized Service Composition 1) The UE makes a selection of a Personalized Service Composition (PSC) from the SSF. The PSC, t... |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 8.22.3 Session modification during PSC session initiation | The SCF may modify IPTV sessions during the PSC session initiation. Figure 39Ib shows an example of steps that could be taken if resource allocation failure occurs during the PSC session set-up. In this example, the resources for a BC session are reduced in order to use those resources for the CoD session. The example ... |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 8.22.4 PSC session release | When the PSC session is no longer needed, it is released by the UE or SCF. |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 8.22.4.1 UE-initiated PSC session release | Figure 39Ic shows the information flow for UE-initiated PSC session release. Figure 39Ic: UE-initiated PSC session release 1) The UE sends a PSC session termination request to the SCF. 2) The SCF terminates the PSC constituting BC/CoD sessions following the procedures of clause 8.3.3 figure 18 and/or clause 8.4.3, figu... |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 8.22.4.2 SCF-initiated PSC session release | Figure 39Id shows the information flow for SCF-initated PSC session release. NOTE: The system may decide to terminate PSC if all of the constituting IPTV sessions have been terminated. Figure 39Id: SCF-initiated PSC session release 1) The SCF sends a PSC session termination request to the UE. (1) PSC session terminatio... |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 8.23.1 IPTV Content Marker storing procedures | Figure 39J provides an overview of the information flows for IPTV Content Marker storing. This procedure can occur at any time during IPTV services (BC/CoD/N-PVR/etc.). Figure 39J: IPTV Content Marker storing procedure 1) The UE sends a IPTV Content Marker storing request to save content information. This content infor... |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 8.23.2 IPTV Content Marker retrieval procedures | Figure 39K provides an overview of the information flows for IPTV Content Marker retrieval. This procedure can occur at any time and may be used to share IPTV Content Markers. UE Core IMS SCF (1) IPTV Content Marker Storing Request (3) IPTV Content Marker (2) IPTV Content Marker Storing Request (4) IPTV Content Marker ... |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 8.23.3 IPTV Content Marker update/removal procedures | Figure 39L provides an overview of the information flows for IPTV Content Marker update/deletion. Figure 39L: IPTV Content Marker update/removal procedure UE Core IMS SCF (1) IPTV Content Marker Update Request (3) IPTV Content marker update/removal (2) IPTV Content Marker Update Request (4) IPTV Content Marker Update R... |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 8.24 Role of BGF in IPTV | In certain IPTV scenarios there is a need to bypass the BGF for scalability reasons. For example, the BGF could be bypassed when using MPEG2-TS directly over UDP transport, as well as, for RTP(RTCP) transmission when there is no RTCP towards the network. It shall be possible to bypass the BGF. Its use is a local decisi... |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 8.25 Procedures for service initiation by remote UE | The service initiation by remote UE can be used by one remote UE to activate the target UE to start-up the IPTV service, for example, it can be used to remote start-up UGC, CoD or BC services. Figure 39M depicts the typical steps for service initiated by Remote UE. ETSI ETSI TS 182 027 V3.5.1 (2011-03) 136 Figure 39M: ... |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 8.26.1 IPTV service state data updated by MF | The procedure described in figure 39N is used to update IPTV service state data by the MF. The SSD may need to be updated for example when a user pauses a streaming or terminates the session. Figure 39N: IPTV service state data updated by MF MF is triggered by an event, e.g. by detecting a pause or and end of a session... |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 9.1 Presence and IPTV | IPTV services may be combined with the presence service capability. This clause describes the mechanisms that apply when IPTV services are combined with the presence service capability. These mechanisms may also be used for other purposes then publishing user presence information. For example they may be used to gather... |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 9.1.1 Presence architecture and functional description | The architecture and functional description of the presence service capability when used in relation to the IPTV services conform to TS 182 008 [10]. SCF Core IMS MF (1) IPTV SSD Request (3) MF fetches the information (2) IPTV SSD Request (4) IPTV SSD Response (5) IPTV SSD Response ETSI ETSI TS 182 027 V3.5.1 (2011-03)... |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 9.1.2 Presence attributes for IPTV | The Presence attributes defined in TS 182 008 [10] apply. In addition, the following specific IPTV attributes shall be supported: • BC service activated; • CoD service activated; • PVR service activated. If the IPTV presence attribute "channel currently accessed" is supported, then the machine-readable part of the iden... |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 9.1.3 SIP related procedure | The SIP related procedures defined in ES 283 030 [13] apply. The publication of CoD related presence information happens: • after completion of CoD session initiation procedure; • after completion of CoD session termination procedure. The publication of BC related presence information happens: • after completion of BC ... |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 9.2 Incoming call management | The combination of basic IPTV services (e.g. Broadcast, CoD and N-PVR) with telephony allows a user to have increased control over incoming calls when watching TV. This clause describes an approach, where the IPTV SCF decides based on incoming call state, IPTV service state and user profile settings how to handle the c... |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 9.2.1 Procedure for incoming call management | Figure 39P shows a signalling flows for incoming call management. Figure 39P: Signalling flows for incoming call management NOTE 1: "Incoming call" indicates an incoming call that may come from different sources such as a telephony AS, an originating network, or a UE. 1) An incoming call is received by the Core IMS. 2)... |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 9.3 Message and IPTV | 9.3.1 Messaging procedures Messaging procedure is used for several purposes: where messages are sent between users or between system and users. Following procedures may be primarily used for immediate messaging described in TS 181 016 [15] in section in clause 6.2.3 to provide services specified in TS 122 340 [16] toge... |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 9.4 Event Handling involving the SCF | Event handling by the SCF takes place if the SCF receives events from several sources. The events can include requests from the UE, new content arrival notification, presence updates, trick play reports from MF, channel change reports from UE, events from other NGN application servers, external applications and so on. ... |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 10 Security | |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 10.1 Authentication | Authentication procedures for the Ut reference point conforms to TS 187 003 [5]. |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 10.2 Content Protection | The locations and related reference points of the following elementary functions are defined in TS 187 003 [5]. They are reproduced below for information. For content protection the following elementary functions are used: • Content licensing: This elementary function handles the licenses issuing related functions, inc... |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 10.3 Service Protection | The locations and related reference points of the following sets of elementary functions are defined in TS 187 003 [5]. The function groups are reproduced below for information. The service membership (SMF), service key management (SKMF) and service protection (SPF) functions described in this clause each involve a set... |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 11 Charging | IMS charging principles apply as defined in ES 282 010 [i.3]. TISPAN IMS-based IPTV shall use the generic IMS charging model using the standardized Rf reference point for offline- and Ro reference point for online charging. NOTE: Further IPTV service-specific charging may be required in addition to the generic IMS char... |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 12 Management | |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 12.1 Management requirements | For each IPTV service, several entities require to be provisioned with necessary network parameters (e.g. multicast addresses for multicast services, source of original content, etc.) and to associate specific content or service with these network parameters. These entities are: • the SSF, as it needs to provide the UE... |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 12.2 Content management | Content management functionalities are responsible for managing acquisition of content and service information (e.g. metadata) from content and its metadata sources of content provider, controlling validation and/or processing/adaptation to the required format and also to provide management functionalities for supporti... |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 13 Support of Metadata | |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 13.1 Introduction | IPTV Metadata enriches the service experience of the IPTV Services a user has access to. IPTV Metadata may originate from the User, the NGN Service Provider, the Application Provider or the Content Provider. The Metadata should be processed, filtered and enriched by involved IPTV solution entities in order to improve t... |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 13.2 SSF support | IPTV Metadata may be delivered outside of an IPTV service session by the SSF. Xa shall be used for the Metadata delivery. |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 13.3 SCF/MF support | IPTV Metadata may be delivered as part of a normal IPTV service session or inside an IPTV service session dedicated to Metadata delivery. In the first case, the Metadata is sent in addition to Media as part of the IPTV session. In either case the Metadata capabilities are negotiated during session setup or session modi... |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 14 Support of Mobility Capabilities | To support the mobility capabilities of IPTV services, the UE shall support roaming in the Visited Network. When the UE is located in the Visited Network, it can access the IPTV services in its own home network. Sometimes when the IPTV Service Provider servers both home network and visited network, the MF can server bo... |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 15 Emergency alert | The IPTV solution shall enable deliver emergency alerting based on different aspects (e.g. type of emergency situation, priority, and locality). TISPAN IMS based IPTV subsystems may in practice also require secure mechanisms to acquire, verify and inject the appropriate content (alert message or emergency live transmis... |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 1 Scope | The present document defines a profile of the Gateway Control Protocol (H.248.1) to be used for controlling Border Gateway Functions (BGF), as defined in ES 282 003 [3]. |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 2 References | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. • For a specific reference, subsequent revisions do not apply. • Non-specific reference may be made only to a complete document or a part thereof and only in the following cases: - if it is accept... |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 2.1 Normative references | The following referenced documents are indispensable for the application of the present document. For dated references, only the edition cited applies. For non-specific references, the latest edition of the referenced document (including any amendments) applies. [1] ITU-T Recommendation H.248.1 (2005): "Gateway control... |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 2.2 Informative references | The following referenced documents are not essential to the use of the present document but they assist the user with regard to a particular subject area. For non-specific references, the latest version of the referenced document (including any amendments) applies. [i.1] ETSI TS 102 333: "Telecommunications and Interne... |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 3 Definitions and abbreviations | |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: address: term used for "network address" (a.k.a. IP address) Border Gateway Function (BGF): packet-to-packet gateway for user plane media traffic NOTE 1: The BGF performs both policy enforcement functions and NA(P)T functions under the... |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: ABNF Augmented Backus-Naur Form AC Admission Control AF Application Function B2BIH Back-to-Back IP Host (mode) B2BRE Back-to-Back RTP Endsystem (mode) BGF Border Gateway Function BGW Border GateWay C-BGF Core-BGF CBR Constant BitRate CNAME Can... |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 4 Applicability | |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 4.1 Architecture | The present document defines an H.248 Profile for the reference point between the Service Policy Decision Function (SPDF) and the Border Gateway Function (BGF), known as the Ia reference point. The SPDF interacts with the BGF to request services. This reference point is used for communication between the SPDF and a Cor... |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 4.2 Border Gateway Guidelines | Guidelines for usage and implementation of border gateways are described in [i.18]. |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5 Profile description | |
1e3c7e6a783f798e804b24eccd66846f | 183 018 | 5.1 Profile identification | Table 1: Profile identification Profile name: ETSI_BGF Version: 3 ETSI ETSI TS 183 018 V3.5.2 (2010-01) 16 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.