hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
a51f761c27385e5a8c90041b2c701012 | 182 027 | 7.3.1.5 Global settings: user action recordable | The "user actions recordable" parameter indicates whether user actions can be recorded by the network as part of the IPTV service action data. |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 7.3.1.5A Global settings: PC-CostLimit | This parameter defines the cost limit of an individual content when toll content (e.g. PPV content) is involved. It has a string value. |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 7.3.1.5B Global settings: PC-TotalCostLimit | This parameter defines the cost limit on all IPTV content over a period of time. It has a string value. This parameter may be defined on the basis of day, week, month or year. There can be several occurrences of this parameter. |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 7.3.1.5C Global settings: PC-ClassificationRestriction | This parameter defines the classifications of the content (e.g. news, action movies, parental rating, …) which are not allowed, in case of Parental Control. It has an enumerated value. |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 7.3.1.5D Global settings: PC-TimePeriodRestriction | This parameter defines time period of the day, in case of Parental Control, during which all IPTV services are restricted. It has a time segment value, which includes a start time and a time length. There can be several occurrences of this parameter. |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 7.3.1.5E Global settings: PC-TotalPlayTimeLimit | This parameter defines the total play time which can be consumed for IPTV services, in case of Parental Control. It has a string value. This parameter may be defined on the basis of day or week. |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 7.3.1.5F Global settings: PC-AdminUser | The "PC-AdminUser " parameter defines a list of administrative users (identified by a SIP-URI) that have access to the user's profile and can modify it. Only the users indicated in this list have the rights to change PC related parameters in the profile. |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 7.3.1.5G Global settings: dynamic PC-activation | The " dynamic PC-activation " parameter indicates whether dynamic parental control is activated or not. If activated, any session initiation request that does not suit the parental-control rules well, will trigger a request to the contact defined in the "PC-Contact" parameter. |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 7.3.1.5H Global settings: PC-Contact | The "PC-Contact" parameter indicates a list of users (SIP URI or mobile phone number) to be contacted at session initiation request if dynamic PC-activation is on. NOTE: Parental control related parameters in Global Settings object class can be optionally and dynamically configured according to user strategy. ETSI ETSI... |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 7.3.1.6 N-PVR storage-limit | This attribute defines a limit allocated per user for N-PVR contents. It can be expressed in time or volume. There can be several occurrences of this parameter. |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 7.3.1.6A PVR: IPTVContentMarkerAuthorizedViewUser | The "IPTVContentMarkerAuthorizedViewUser" parameter indicates a list of users authorized to view PVR IPTV Content Markers of this user. The data model of IPTV Content Markers is defined in clause 7.5. |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 7.3.1.6B PVR: IPTVContentMarkerSourceUser | The "IPTVContentMarkerSourceUser" parameter indicates a list of other users from which PVR IPTV Content Markers can be accessed. The data model of IPTV Content Markers is defined in clause 7.5. NOTE: The authorization to access a user's IPTV Content Markers does not imply access rights to the content. Separate acquisit... |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 7.3.1.6C PVR: AuthorizedControlUser | The "AuthorizedControlUser" parameter indicates a list of users authorized to initiate the PVR capture request on behalf of this user. |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 7.3.1.7 BC: ParentalControlLevel | This parameter defines the Parental Control Level of the BC services. It has an enumerated value. |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 7.3.1.7A BC: IPTVContentMarkerAuthorizedViewUser | The "IPTVContentMarkerAuthorizedViewUser" parameter indicates a list of users authorized to view BC IPTV Content Markers of this user. The data model of IPTV Content Markers is defined in clause 7.5. 7.3.1.7B BC: IPTVContentMarkerSourceUser The "IPTVContentMarkerSourceUser" parameter indicates a list of other users fro... |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 7.3.1.8 CoD: IPTVContentMarkerAuthorizedViewUser | The "IPTVContentMarkerAuthorizedViewUser" parameter indicates a list of users authorized to view CoD IPTV Content Markers of this user. The data model of IPTV Content Markers is defined in clause 7.5. 7.3.1.9 CoD: IPTVContentMarkerSourceUser The "IPTVContentMarkerSourceUser" parameter indicates a list of other users fr... |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 7.3.1.10 PCh: PChId | This attribute contains the unique identifier of the PCh list. It has a string value. ETSI ETSI TS 182 027 V3.5.1 (2011-03) 40 |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 7.3.1.11 PCh: PChExpiryTime | This attribute defines the expiry time of the PCh list. It has a timestamp value. |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 7.3.1.12 PCh: PChItemServiceType | This attribute defines the service type of the item within a PCh list. It has an enumerated value and refers to BC, CoD or N-PVR. |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 7.3.1.13 PCh: PChItemContentId | This attribute defines the referenced content id of the item within a PCh list: • In case of BC, it shall consist of the "BCServiceId" as well as the "ProgrammeId" (see clause 7.4.1). • In case of CoD, it shall be set to the "CoDId" (see clause 7.4.1). • In case of N-PVR, it shall be set to the "N-PVRContentId" (see cl... |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 7.3.1.14 PCh: PChItemStartTime | This attribute indicates the start time of playing a content item within a PCh list. It has a timestamp value. |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 7.3.1.15 PCh: PChItemEndTime | This attribute indicates the end time of playing a content item within a PCh list. It has a timestamp value. |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 7.3.1.16 PCh: PChItemOffset | This optional attribute indicates the offset from beginning of the content item in case the item is CoD or N-PVR., from which the item is ready to play. It has a timestamp value. If this attribute is not present, the item shall be played from the beginning. NOTE: The availability of PCh information should be guaranteed... |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 7.3.1.17 CR Settings: CR notifications | Activate, deactivate content recommendation notifications, or other actions for further study. |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 7.3.1.18 UGC storage-limit | This attribute defines a limit allocated per user for UGC contents. It can be expressed in time or volume. |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 7.3.1.19 UGC: AuthorizedControlUser | The "AuthorizedControlUser" parameter indicates a list of users authorized to activate the target UE remotely for initiation of the UGC service. |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 7.3.1.20 ICM Settings: ICM rules | This attribute allows the user to set the behaviour of its IPTV service when combined with telephony services. It defines the behaviour of the IPTV service when user is receiving an incoming call, i.e. accept on TV, on phone, refuse, pause on incoming call (using network-controlled trick play from clause 8.16) or redir... |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 7.3.2 Usage of IPTV user profile | The IPTV user profile may be used to customize the user IPTV experience. For instance: • The CoD profile parental control level should be used to filter a CoD catalog. • The UE capabilities associated with an IPTV user profile UE data may be used for customization of IPTV service selection data that is provided by the ... |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 7.3.3 Life cycle | UE List: The information about the UE(s) that an IPTV user is currently associated with may be purged when the IPTV user deregisters and/or logs off. This is to avoid persisting UE related information when the IPTV user logs off that particular UE. |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 7.4 IPTV service action data | |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 7.4.0 General | IPTV service action data: this category encompasses information related to the actions the user may have taken while accessing services such as BC or CoD (e.g. ordering a CoD - Choosing to pause while viewing a live event). Those data are required to enable IPTV session portability for the user. This category also comp... |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 7.4.1 Data model | Figure 8: IPTV Service action data - data model This data model assumes that each IPTV user is allocated at least an IMS Public User Identity and an IPTV Service Action data profile is associated with this IMS Public User Identity. NOTE 1: The "ProgrammeId" attribute is unique, as it refers to one and only one entry in... |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 7.4.2 Life cycle | • CoD list: Items may be removed when they are no longer accessible (e.g. the offer they were attached to has expired.) or when the entitled number of visualizations has been reached. Alternatively, items are purged when the expiration time associated with the CoDOffset (identified using CoDOffserExpiryTime) expires. •... |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 7.5 IPTV information storing/sharing services | |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 7.5.1 General | This clause defines data models to be used by IPTV information sharing or targeting services. NOTE: Accessibility, as well as the legal use of data related to sharing or targeted services should be considered. |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 7.5.2 IPTV Content Marker | 7.5.2.1 General This clause defines the data model of IPTV Content Markers for BC/CoD/N-PVR services. The intention of IPTV Content Markers is twofold: 1) To store configurable pointers to content and be able to quickly access that content. 2) Enable users to exchange and share IPTV Content Markers. NOTE: Exchanging IP... |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 7.5.2.4 IPTV service type identifier | This attribute identifies the type of IPTV service this IPTV Content Marker refers to, see clause I.2. 7.5.2.5 IPTV Content Identifier This attribute shall identify the content this particular IPTV Content Marker refers to, as specified in clause I.1. • In case of BC, it shall consist of the "BCServiceId" as well as th... |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 7.5.3 IPTV Service Access History | 7.5.3.1 Data model This clause defines the data model for IPTV service access history, which can be used for: • User preference extraction needed by service personalization and targeting (e.g. targeted Ad, CRS, personalized EPG, etc.). • Sharing consumption history among authorized users. NOTE: How the user preference ... |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 7.5.3.4 ServiceType | This attribute identifies the service type of a user's service access history, as specified in clause I.2. It shall always be present and has a enumerated value. 7.5.3.5 ReferencedContentID This attribute identifies the associated content accessed by the user in the context of specific ServiceType, as specified in clau... |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 7.5.3.6 Rating | This optional attribute indicates the user rating for the referened content. It has a numerated value (e.g. one-star, two-stars, etc.). 7.5.3.7 AccessStartTime This attribute is used to identify the time when the access to the content is started. It shall always be present and has a timestamp value. UserID: String Acce... |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 7.6 IPTV Content Recommendation profile | The IPTV Content Recommendation Profile (IPTV CR Profile) data model describes the user preference on specific type of the content, which is needed in personalized services e.g. CRS, TAI. Figure 8C: Content Recommendation Profile data model |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 7.6.1 Genre | This element describes user's preference for the genre of the content. It has a string data type. There may be multiple occurrences of this element, with different preference value attached to each occurrence, indicating the relative priority with respect to other Genre elements. |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 7.6.2 Keyword | This element describes user's preference for the keyword summarizing the content. It has a string data type. There may be multiple occurrences of this element, with different preference value attached to each occurrence, indicating the relative priority with respect to other Keyword elements. |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 7.6.3 Creator | This element describes user's preference for the creator or staff who created the content, e.g. favourite director, actor/actress. It has a string data type. There may be multiple occurrences of this element, with different preference value attached to each occurrence, indicating the relative priority with respect to o... |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 7.6.4 CreationLocation | This element describes user's preference for the location of the content where it was created. It has a string data type. There may be multiple occurrences of this element, with different preference value attached to each occurrence, indicating the relative priority with respect to other CreationLocation elements. IPTV... |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 7.6.5 CreationDate | This element describes user's preference for the date of the content when it was created. It has a string data type. There may be multiple occurrences of this element, with different preference value attached to each occurrence, indicating the relative priority with respect to other CreationDate elements. NOTE: The dat... |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 7.7 IPTV Service State Data | |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 7.7.1 Data model | Figure 8D shows the data model for IPTV Service State Data. IPTV Service State Data may be held in network elements that constitute the IPTV solution or external applications. Figure 8D: IPTV Service State Data - data model IPTV Service State may include state information, state transition information, state history in... |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 7.7.2 Life cycle | IPTV Service State Data records are kept while the associated service(s) are ongoing. Alternatively, entries may also be purged when the expiration time associated with a service state value (identified using ServiceStateExpiryTime) expires. |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 8 Procedures | |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 8.1 IPTV addressing mechanisms | |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 8.1.1 IPTV end-users identification and addressing mechanisms | End-user identification and addressing shall be done according to what is defined in document TS 182 006 [2]. |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 8.1.2 Addressing of nodes | As specified by TS 182 006 [2], those network nodes with reference points supporting the SIP protocol shall be identifiable using a valid SIP URI. |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 8.2 UE start-up procedure | Figure 9 depicts the typical steps that occur at power up of the UE. Some of the steps are not new in them selves, but exist already in NGN. ETSI ETSI TS 182 027 V3.5.1 (2011-03) 50 Figure 9: UE start-up procedure 1) Network Attachment In this step the UE attaches to the network. The procedures for network attachment a... |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 8.3 Broadcast session | The procedures described here are for streaming cases distinguished from upload/download cases (described in clause 8.19). Before the User Equipment can join a multicast channel, a session initiation procedure shall take place as described in clause 8.3.1. One session initiation is associated to one or more service pac... |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 8.3.1 Signalling flows for broadcast session initiation | |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 8.3.1.1 Overview of the signalling flows for session initiation | |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 8.3.1.1.1 UE-initiated BC session initiation | Figure 12 provides an overview of the information flows for UE-initiated BC session initiation. Figure 12: UE-initiated BC session initiation 1) The UE initiates a dialogue to the BC service which refers to the service package(s). 2) The session initiation request is routed by the Core IMS entities up to the SCF in cha... |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 8.3.1.1.2 SCF-initiated BC session initiation | Figure 12A provides an overview of the information flows for SCF-initiated BC session initiation. Figure 12A: SCF-initiated BC session initiation 1) The SCF sends a session initiation request to the UE via the core IMS. 2) The Core IMS forwards the session initiation request to the UE. 3) If the UE accepts the request,... |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 8.3.1.2 Signalling flows for the establishment of the delivery channel | |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 8.3.1.2.1 SCF-initiated establishment of the delivery channel | Figure 13 shows information flows applicable when SCF initiates the establishment of content delivery channel. ETSI ETSI TS 182 027 V3.5.1 (2011-03) 55 SCF UE Core IMS RACS (44) Media Offer for Content Channels (42) Media Offer for Content Channels (45) Media Answer for Content Channels (47) Media Answer for Content Ch... |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 8.3.1.2.2 UE-initiated establishment of the delivery channel | Figure 14 provides an overview of the information flows for UE-initiated establishment of content delivery channel necessary to handle the BC service. ETSI ETSI TS 182 027 V3.5.1 (2011-03) 56 SCF UE Core IMS RACS (41) Media Offer for Content Channels (43) Media Offer for Content Channels (46) Media Answer for Content C... |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 8.3.2 Signalling flows for BC session modification | The BC session modification procedure is used to modify network parameters necessary to handle the BC service in an existing session. The BC session modification procedure is initiated by the UE or the SCF. |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 8.3.2.1 UE-initiated BC session modification | Figure 15 provides an overview of the information flows for UE-initiated BC session modification. ETSI ETSI TS 182 027 V3.5.1 (2011-03) 57 Figure 15: UE-initiated BC session modification 1) The UE initiates a session modification procedure in order to start a modification of network parameters necessary to handle the B... |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 8.3.2.2 SCF-initiated BC session modification | Figure 16 provides an overview of the information flows for SCF-initiated session modification. SCF UE Core IMS RACS (7) Content Control and Content Delivery Flows (3) Content Delivery Channel Setup/Modification (1) Session Modification Request (2) Session Modification Request (4) Session Modification Response (5) Reso... |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 8.3.3 Signalling flows for broadcast session release | |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 8.3.3.1 UE-initiated session release | Figure 17 provides an overview of the information flows for UE-initiated session release. SCF UE Core IMS RACS (7) Content Control and Content Delivery Flows (3) Content Delivery Channels Setup/Modification (2) Session Modification Request (1) Session Modification Request (6) Session Modification Response (5) Resources... |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 8.3.3.2 SCF-initiated session release | Figure 18 provides an overview of the information flows for SCF-initiated session release. ETSI ETSI TS 182 027 V3.5.1 (2011-03) 60 SCF UE Core IMS RACS (5) Session Termination Confirm (4) Session Termination Confirm (1) Session Termination Request (3) Session Termination Request (2) Resources release Figure 18: SCF-in... |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 8.3.4 Signalling flow for Broadcast TV channel switching | Figure 19 provides an example of a signalling flow for channel switching. It shows how the SCF can be informed about what channel is currently being watched. Core IMS SCF (3) Inform channel change (4) Inform channel change ECF/EFF (1) Switch multicast channel UE (2) Delay Figure 19: Broadcast TV channel switching ETSI ... |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 8.3.7 Signalling flows for Broadcast TV with trick play session release | When the UE terminates the Broadcast TV with trick play the UE shall follow the same flows as clause 8.4.3.1. |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 8.3.8 Signalling flows for Pay Per View service | Figure 20A depicts signalling flows for PPV service, this procedure applies for IPTV users subscribing to a PPV program scheduled on a channel to which the user is not subscribed to. ETSI ETSI TS 182 027 V3.5.1 (2011-03) 64 Figure 20A: Signalling flows for Pay Per View session Prior to the PPV program session initiatio... |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 8.4 CoD session | The procedures described here are for streaming cases distinguished from upload/download cases (described in clause 8.18). RACS SCF UE Core IMS ECF/EFF (3) PPV program session release (1) PPV program session initiation (2) Content Delivery Flows ETSI ETSI TS 182 027 V3.5.1 (2011-03) 65 |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 8.4.1 Signalling Flows for CoD session initiation | Before the User Equipment can view the content, a session initiation procedure shall take place as described in clause 8.4.1. The UE retrieves necessary network parameters to handle the CoD service before the session initiation procedure (from the SSF), or as part of the session initiation procedure, or after the sessi... |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 8.4.1.1 Overall signalling flows for CoD session initiation | |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 8.4.1.1.1 UE-initiated CoD session initiation | Figure 21 provides an overview of the information flows for UE-initiated CoD session initiation. Figure 21: UE-initiated CoD session initiation 1) (Optionally) UE may retrieve COD offset from service action data. 2) (Optionally) SSF may return COD offset for specified content. 3) The UE initiates a dialogue to the CoD ... |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 8.4.1.1.2 SCF-initiated CoD session initiation | Figure 21A provides an overview of the information flows for SCF-initiated CoD session initiation. ETSI ETSI TS 182 027 V3.5.1 (2011-03) 67 SCF UE MF Core IMS RACS (12) Content Control Flows (4) Session IInitiation Request (3) Session Initiation Request (2) Session Initiation Request (8) Session Initiation Response (7)... |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 8.4.1.2 Media Channel Negotiation (MCN) | The following clauses go into details related to Content Control and/or Delivery Channel Setup steps in the session initiation in clause 8.4.1.1 (step 6 in clause 8.4.1.1.1 and step 5 in clause 8.4.1.1.2, respectively). 8.4.1.2.1 Signalling flows for the establishment of the content control and content delivery channel... |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 8.4.1.2.3 Signalling flows for the establishment of the content control channel from UE | Figure 24 provides an overview of the information flows for UE-initiated establishment of the content control channel. SCF UE MF Core IMS RACS (46) Media Answer for Content Control (45) Media Answer for Content Control (41) Media Offer for Content Control (43) Media Offer for Content Control (44) Media Offer for Conten... |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 8.4.2 Signalling Flows for CoD session modification | The CoD session modification procedure is used to add, remove or modify one or more content delivery channels in an existing session. The CoD session modification procedure is initiated by the UE or the MF. The session modification procedure shall take place immediately after the session initiation procedure (e.g. usin... |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 8.4.2.0A UE-initiated CoD session modification | Figure 25 provides an overview of the information flows for UE-initiated CoD session modification. ETSI ETSI TS 182 027 V3.5.1 (2011-03) 71 Figure 25: UE-initiated CoD session modification 1) The UE initiates a session modification procedure in order to start a negotiation for one or more content delivery channel(s). 2... |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 8.4.2.0B MF-initiated CoD session modification | Figure 26 provides an overview of the information flows for MF-initiated CoD session modification. Figure 26: MF-initiated CoD session modification 1) The MF initiates a session modification procedure in order to start a negotiation for one or more content delivery channel(s). 2) The SCF performs service authorization ... |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 8.4.2.2 Signalling flows for the modification of the content delivery channels from MF | Figure 28 provides an overview of the information flows for MF-initiated modification of the content delivery channel. ETSI ETSI TS 182 027 V3.5.1 (2011-03) 74 SCF UE MF Core IMS RACS (44) Media Offer for Content Delivery (42) Media Offer for Content Delivery (41) Media Offer for Content Delivery (45) Media Answer for ... |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 8.4.3 Signalling Flows for CoD session release | |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 8.4.3.1 UE-initiated session release | Figure 29 provides an overview of the information flows for UE-initiated session release. ETSI ETSI TS 182 027 V3.5.1 (2011-03) 75 SCF UE MF Core IMS RACS (7) Session Termination Confirm (6) Session Termination Confirm (5)Session Termination Confirm (1) Session Termination Request (3) Session Termination Request (4) Se... |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 8.4.3.2 SCF-initiated session release | Figure 30 provides an overview of the information flows for SCF-initiated session release. ETSI ETSI TS 182 027 V3.5.1 (2011-03) 76 SCF UE MF Core IMS RACS (6) Session Termination Confirm (7) Session Termination Confirm (2)Session Termination Confirm (5) Session Termination Request (3) Session Termination Request (1) S... |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 8.4.3.3 MF-initiated session release | Figure 31 provides an overview of the information flows for MF-initiated session release. ETSI ETSI TS 182 027 V3.5.1 (2011-03) 77 SCF UE MF Core IMS RACS (5) Session Termination Confirm (6) Session Termination Confirm (7)Session Termination Confirm (4) Session Termination Request (2) Session Termination Request (1) Se... |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 8.4.4 Signalling Flows for CoD session transfer | The CoD session transfer is used to transfer an on-going CoD session from one terminal called transferor UE to another one called transferee UE. The transferor UE and the transferee UE must be served by different or the same SCF. The session transfer could be handled directly between both terminals or can be managed by... |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 8.4.4.1 Terminal centric session transfer pushed from transferor UE to transferee UE | Figure 31A provides an overview of the information flows for direct CoD session transfer between the transferor UE (UE1) and the transferee UE (UE2). For clarity purpose, core-IMS is not indicated in the figure but all messages go through it. In this scenario the transferor UE discovers the devices to which a potential... |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 8.4.5 Signalling flows for CoD service action data update/Requests | CoD service action data may be updated by UE as described in clause 8.4.5.1 and generically may be updated by MF as described in clause 8.4.5.2. Furthermore, CoD service action data requests may be initiated by the SCF as described in clause 8.4.5.3. |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 8.4.5.1 CoD service action data updated by UE | The UE use the procedure described in figure 31D to save a current CoD SAD. This procedure may occur at any time. The most common use case is the stop CoD viewing request. Figure 31D: CoD service action data updated by UE 1) The UE sends a CoD SAD update request to save the current position of the content. This request... |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 8.4.5.2 CoD service action data updated by MF | The procedure described in figure 31E is used to save a CoD service action data by MF. This CoD SAD may need to be updated for example when a user pauses a streaming, terminates the session or if the MF detects that the UE becomes unexpectedly offline. Figure 31E: CoD service action data updated by MF 1) CoD session in... |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 8.4.5.3 CoD Service Action Data requested by the SCF | This procedure allows the SCF to acquire the current offset in a streamed content during an ongoing session in case such information is not available and required. Figure 31F provides an overview of the information flow for a CoD SAD request by the SCF to acquire the offset. This procedure can occur at any time during ... |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 8.4.6.1 IPTV Data Model for playlist | |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 8.4.6.1.1 General | This clause defines the data model for playlist for IPTV CoD/N-PVR/Ad content delivery, which can be used for content delivery. UE RACS Core IMS SCF MF (1) Session Initiation Request (2) Session Initiation Request (5) playlist interpretation (4) Session Initiation Request including playlist information 6) Steps 6-11 of... |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 8.4.6.1.2 ContentD | This attribute identifies the associated content. • In case of CoD, it shall be set to the "CoDId" (see clause 7.4.1). • In case of N-PVR, it shall be set to the "N-PVRContentId" (see clause 7.4.1). • In case of Ad, it shall contain the ad content id (see clause 8.14.1). |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 8.4.6.1.3 Duration | This optional attribute may be used to identify the duration of IPTV content. |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 8.4.6.1.4 Begin Time | This optional attribute may be used to identify the starting point of IPTV content. |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 8.4.6.1.5 Restricted trick play | This optional attribute may be used to identify whether trick play control for IPTV content is allowed or not. 8.4.7 Signalling flows for generating playlist by SCF and sending playlist information from SCF to MF during an existing CoD session Figure 31I provides an overview of the information flows for playlist genera... |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 8.4.8 Content switch procedure within a CoD playlist | Figure 31J provides an overview of the information flows for content switch within a CoD playlist. UE RACS Core IMS SCF MF (1) Existing CoD session (2) Detection of event and playlist generation/update (3) playlist information (4) playlist interpretation ETSI ETSI TS 182 027 V3.5.1 (2011-03) 89 Figure 31J: Content swit... |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 8.5 PVR service procedures |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.