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 TS 182 027 V3.5.1 (2011-03) 39 |
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 acquisition of these rights might be necessary. |
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 from which BC 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 acquisition of these rights might be necessary. |
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 from which CoD 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 acquisition of these rights might be necessary. |
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 clause 7.4.1). |
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 by mechanisms aligned with user profile and content metadata validity rules. |
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 redirect the call to voicemail. NOTE: Further actions are beyond the scope of this release. ETSI ETSI TS 182 027 V3.5.1 (2011-03) 41 |
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 SSF to the IPTV user (based on capabilities of the UE that the IPTV user is currently associated with). Thanks to the IPTV user profile standardization, any equipment can render the same IPTV environment to the user. The IPTV user profile may also be used to allow or deny access to IPTV services. |
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 comprises IPTV service state information (e.g. current BC program ID, commercial break in BC service, pause during CoD playback, list of CoDs and associated status, record status of recordings, trick play events). The recipient of the IPTV service action data shall ensure they comply with the data protection regulations that apply in the authorized jurisdiction that the service is delivered (see also TS 187 016 [19]). ETSI ETSI TS 182 027 V3.5.1 (2011-03) 42 |
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 the EPG. NOTE 2: Although the "Bookmark" attribute could be used as an indirect way to identify the programme, it is seen as more convenient and immediate to use the ProgrammeId for that purpose. IPTV service action data includes the following information: • The list of CoDs that the user has ordered and associated status, CodOffset which is offset in the content where the user has paused and CodOffsetExpiryTime which is expiration time associated with the CodOffset value. ActionData Id: string IPTV Service Action BC Bookmarks BCServiceId: string ProgrammeId: string Bookmark: timestamp BookmarkExpiryTime: timestamp NPVR items NPVRContentId: string BCServiceId: string RecordStartDate: timestamp RecordEndDate: timestamp RecordDescription: string RecordStatus: enumerated RecordOffset: string RecordOffsetExpiryTime timestamp RecordExpiryTime: timestamp Available CoD CoDId: string CoDDeliveryStatus: enumerated CoDOffset: string CoDOffsetExpiryTime: timestamp 0..n 0..n 0..n UGC items UGCContentId: string UGCCreationTime: timestamp UGCTargetUserId: string UGCGenre:string UGCTitle:string UGCOriginator:string UGCDescription: string UGCAuthorizedViewUser: string 0..n 0..n CPVR items CPVRContentId: string BCServiceId: string TargetUEId: string RecordStartDate: timestamp RecordEndDate: timestamp RecordDescription: string ETSI ETSI TS 182 027 V3.5.1 (2011-03) 43 • The list of BC TV services (or programmes) that the user has paused (and is hence likely to resume later) including the bookmark value associated with the paused BC TV service or Programme and BookMarkExpiryTime which is expiration time associated with the bookmark value. • The list of N-PVR contents that the user has asked to be recorded. This would include the following parameters: - N-PVRContentId: it refers to a content identifier used by the UE to activate an N-PVR session related to the N-PVR content. NOTE 3: In the case when a specific programme has been requested to be recorded, this ID would be the same as ProgrammeID, and the RecordStartDate and RecordEndDate attributes would be optional. - BCServiceId: the identifier of the BC service that is to be recorded. - (Optionally) RecordStartDate: the start date (and time) of the recording. - (Optionally) RecordEndDate: the end date (and time) of the recording. - (Optionally) RecordDescription: a description of the recording made by the user when he/she requested to record the live content. - RecordStatus: the status of such a recording (requested - scheduled - available - failed). - RecordOffset: the offset in the N-PVR content where the user might have paused while actually watching it. - RecordOffsetExpiryTime: expiration time associated with the RecordOffset. - RecordExpiryTime: the expiration time associated with the recording value. • The list of C-PVR contents that the user has asked to be recorded. This would include the following parameters: - BCServiceId: the identifier of the BC service that is to be recorded. - TargetUEId: the identifier of Target UE which stores the content. - (Optional) C-PVRContentId: the identifier of the C-PVR content, can be used as an index for user. NOTE 4: In the case when a specific programme has been requested to be recorded, this ID would be the same as ProgrammeID, and the RecordStartDate and RecordEndDate attributes would be optional. - (Optional) RecordStartDate: the start date (and time) of the recording. - (Optional) RecordEndDate: the end date (and time) of the recording. - (Optional) RecordDescription: a description of the recording made by the user when he/she requested to record the live content. - RecordStatus: the status of such a recording (requested - scheduled - available - failed). |
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. • BC bookmarks are kept in the profile while the BC TV service or Programme they refer to is available in the media server. Alternatively, entries may also be purged when the expiration time associated with BookMark value (identified using BookmarkExpiryTime) expires. • N-PVR items are kept in the profile while the content they refer to is available in the Network PVR server(s). Alternatively, entries may also be purged when the expiration time associated with Recording value (identified using RecordExpiryTime) expires. Failed recordings may be purged on a regular configurable basis. ETSI ETSI TS 182 027 V3.5.1 (2011-03) 44 |
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 IPTV Content Markers between users does not imply a transfer of access rights. Separate acquisition of these rights might be necessary. IPTV Content Marker IPTVContentMarkerID: String OwnerUserID: String IPTV service type identifier: String IPTV content identifier: String StartTimeOfIPTVContentMarker: timestamp EndTimeOfIPTVContentMarker: timestamp UserComment: String GenerationTime: timestamp ExpiryTime: timestamp Figure 8A: IPTV Content Marker - data model Figure 8A depicts the data model assumes that each IPTV user is allocated at least an IMS Public User Identity and individual IPTV Bookmark data items are associated with this IMS Public User Identity. Each of the entries within an IPTV Bookmark item may be rendered to the end-user. Concerning life cycle, items may be removed when the content they refer to does no longer exist. Alternatively, items are purged when the expiration time associated with the content marker (identified using ExpiryTime) expires. 7.5.2.2 IPTVContentMarkerID Unique identifier to distinguish between several of a user's IPTV Content Markers. It shall always be present. 7.5.2.3 OwnerUserID This attribute shall identify the user owning the IPTV Content Marker by means of the IMPU. It shall always be present. ETSI ETSI TS 182 027 V3.5.1 (2011-03) 45 |
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 the "ProgrammeId" (see clause 7.4.1) 7.5.2.6 StartTimeOfIPTVContentMarker This optional timestamp may be used to identify a starting point for playback of referred-to content. If it is not present playback should start at the beginning of the content. NOTE: StartTimeOfIPTVContentMarker and EndTimeOfIPTVContentMarker are intended as guidance for playback logic to point to particularly interesting scenes within the content they are associated to. 7.5.2.7 EndTimeOfIPTVContentMarker This optional timestamp may be used to identify an ending point for playback of referred-to content. If it is not present playback should end at the end of the content. NOTE: StartTimeOfIPTVContentMarker and EndTimeOfIPTVContentMarker are intended as guidance for playback logic to point to particularly interesting scenes within the content they are associated to. 7.5.2.8 UserComment The user may comment an IPTV Content Marker/the content referred to by the IPTV Content Marker item. 7.5.2.9 GenerationTime This optional timestamp may store the point in time when the IPTV Content Marker item was created. 7.5.2.10 ExpiryTime This optional timestamp indicates when the associated IPTV Content Marker item expires. |
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 is extracted from the IPTV service access history is out of scope of the present document. ETSI ETSI TS 182 027 V3.5.1 (2011-03) 46 Figure 8B: IPTV service access history data model Figure 8B depicts the data model assumed that each IPTV user is allocated at least an IMS Public User Identity (i.e. IMPU) and one or multiple IPTV service access history items are associated with this identifier. The entries of IPTV service access history may be rendered to the user through authorization rules or be processed by the service provider subject to appropriate privacy and regularity mechanisms. 7.5.3.2 UserID This attribute identifies who is the IPTV service access history item is associated. It shall always be present and has a string value. 7.5.3.3 AccessHistoryID This attribute is used to distinguish between several IPTV service access history items of a user.It shall always be present and has a string value. |
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 clause I.1. It shall always be present and has a string value. |
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 AccessHistoryID: String ServiceType: Enumerated ReferencedContentID: String Rating: enumerated AccessStartTime: Timestamp AccessEndTime: Timestamp HistoryExpiryTime: Timestamp IPTV Service Access History ETSI ETSI TS 182 027 V3.5.1 (2011-03) 47 7.5.3.8 AccessEndTime This attribute is used to identify the time when the access to the content is ended. It shall always be present and has a timestamp value. 7.5.3.9 HistoryExpiryTime This optional attribute identifies the expiry time of an IPTV service access history item. It has a timestamp value. |
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 other Creator elements. |
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 CR Profile Genre: string Keyword: string Creator: string CreationLocation: string CreationDate: string ETSI ETSI TS 182 027 V3.5.1 (2011-03) 48 |
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 data model for CR profile can be extended to fulfill needs in pratical implementations. |
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 information, state transition history information and/or media action data/commands, e.g. current BC program ID, commercial break in BC service, pause during CoD playback, list of CoDs and associated status, record status of recordings, trick play status (e.g. play, stop, pause, or other media action data). IPTV Service State has the following generic attributes: • IPTVServiceTypeIdentifier. • IPTVContentIdentifier. • ServiceState: state information that can be enumerated, e.g. trick play status or - commands. IPTV Service State IPTVServiceTypeIdentifier: enumerated IPTVContentIdentifier: string ServiceState: enumerated ServiceStateInformation: string ServiceStateExpiryTime: timestamp BC Service State TrickPlayActivated: boolean SSC Service State SSCRoomId: string 0..n PSC Service State PSCid: string 0..n Ad Service State AdInsertionPoint: string IPTV Service State Data ServiceStateDataId: string 0.n ETSI ETSI TS 182 027 V3.5.1 (2011-03) 49 • ServiceStateInformation: string with additional service state information, e.g. state (transition) history. • ServiceStateExpiryTime, timestamp indicating the expiry time of the IPTV Service State, see clause 7.7.2. The default value of ServiceStateExpiryTime indicates that it expires when the associated ongoing service is terminated. Specific IPTV services may have additional attributes for their IPTV Service State, and specific implementations of generic IPTV Service State attributes: • BC Service State: TrickPlayActivated, which is "true" if trick play has been activated, see clause 8.3.5. • Ad Service State: AdInsertionPoint, see clause 8.14.1. • SSC Service State: SSCRoomID and the IPTV Service State of the IPTV services under SSC control, see clause 8.21. • PSC Service State: PSCid and the IPTV Service States of the IPTV services that the PSC is composed of, see clause 8.22. NOTE 1: The data model for SSC - and PSC Service State follows the so-called "composite design pattern". The individual BC and CoD Service States have their own ServiceState and ServiceStateInformation attributes, which are associated in the combined SSC - or PSC Service State. NOTE 2: Additional attributes for other IPTV Services are not specified in TISPAN Release 3. |
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 are defined in ES 282 004 [3]. This step includes IP configuration, P-CSCF address discovery, etc. 2) IMS Registration In this step, the UE performs regular IMS Registration as defined in TS 182 006 [2]. 3) Service Attachment In this step, the UE retrieves the service attachment information (server addresses and other relevant information) needed to retrieve the appropriate information to access the services that the user is authorized to. The user preferences and the capabilities of the UE can be taken into account to enable personalized service discovery. The UE could retrieve the service attachment information through the Push mode and Pull mode. Push mode: When the UE attaches to the IMS network, the SDF actively sends the service attachment information to the UE. Pull mode: After the UE attaches to the IMS network, the UE actively requests the service attachment information from the SDF. NOTE 1: The SDF discovery can be performed in several ways: through NASS attachment, by manual provisioning, using IFC e.g. third-party registration, etc. 4) Service Selection In this step, the UE retrieves data related to specific services and makes appropriate service selection. NOTE 2: In case the UE needs to directly contact a network functional element, (e.g. a Service Control Function - SCF, or SSF), it should perform GBA authentication, for key management purposes. This procedure will secure further communication taking place between the UE and the IPTV Service Control Function. The GBA bootstrapping procedure is defined in GAA - TS 133 220 [4] and is referenced in the TISPAN NGN Security architecture - TS 187 003 [5]. This step is not affecting the functional behaviour of any of the entities involved in this start-up phase and thus, it is not displayed in this flow. ETSI ETSI TS 182 027 V3.5.1 (2011-03) 51 The detailed sequence of steps 3 and 4 is described in the figures below: 2. attach to IPTV Core IMS SDF User Profile UE SSF 3. SSF Election 1.attach to IPTV 4. service attachment information (Elected SSF address,...) 5. service attachment information (Elected SSF address,...) 6. request selection data 7. receive selection data (EPG,CoD catalog,...) Figure 10: IPTV service attachment and selection in pull mode 1) The UE makes a service attachment request. 2) The core IMS relays the request to the appropriate entity (here, SDF). 3) The SDF determines the proper SSF (or SSFs) according to the UE's capabilities, the user's profile and also the location of the UE (Personalized Service Discovery). The user profile may be retrieved from the UPSF or any other entity where it is stored. 4) Service attachment information that includes the SSF address(es) is (are) routed back to the UE. 5) Core IMS relays the service attachment information related to IPTV services back to UE. 6) The UE requests the SSF to get the selection data. 7) The SSF delivers the requested data to the UE. For the purpose of service attachment update, steps 4 and 5 described above can be repeated at any time after completion of the IPTV service attachment and selection procedure. ETSI ETSI TS 182 027 V3.5.1 (2011-03) 52 Core IMS SDF User Profile UE SSF 2. SSF Election 3. service attachment information (Elected SSF address,...) 4. service attachment information (Elected SSF address,...) 5. request selection data 6. receive selection data (EPG,CoD catalog,...) 1.Getting the status of the UE Figure 11: IPTV service attachment and selection in push mode 1) The SDF gets the status of the UE, e.g. the S-CSCF sends a third-party REGISTER request to the SDF after the IMS Registration or by other method, then the SDF gets the status of the UE. 2) The SDF determines the proper SSF (or SSFs) according to the UE's capabilities, the user's profile and also the location of the UE (Personalized Service Discovery). The user profile may be retrieved from the UPSF or any other entity where it is stored. 3) Service attachment information that includes the SSF address(es) is (are) routed back to the UE. 4) Core IMS relays the service attachment information related to IPTV services back to UE. 5) The UE requests the SSF to get the selection data. 6) The SSF delivers the requested data to the UE. |
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 packages. SCF does not participate in channel change control in order to avoid zapping delays. The UE retrieves necessary network parameters to handle the BC TV Service either before the session initiation procedure (from the SSF) or as part of the session initiation procedure (from the SCF). The SSF and/or the SCF acquire network parameters from management entities. NOTE: Alternative methods could exist, but they out of scope for this release. The session may be modified using the procedure described in clause 8.3.2 in the following cases: • The BC TV Service is modified. ETSI ETSI TS 182 027 V3.5.1 (2011-03) 53 • Currently allocated resources are not sufficient and the User Equipment wishes to join a multicast channel with different QoS requirements (e.g. zapping from a SD to HD channel). The session modification procedure may take place before or after the request to change channel, in order to avoid increasing zapping delays. In the later case, the session modification procedure is initiated by the UE and the new channel is delivered using currently allocated resources until this procedure and any additional resource reservations that may be required are completed. The session can be terminated by the User Equipment using the procedures described in clause 8.3.3 or by the network. Interactions between the IMS and the RACS take place at different steps of the session initiation and modification and release. Additional resource control procedures not triggered by the IMS may also take place and are not described in the following clauses. |
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 charge of the requested BC service. 3) Signalling procedures for the establishment of one or more content delivery channels network parameters necessary to handle the BC service take place between the UE and the SCF (see clause 8.3.1.2). NOTE: In a particular protocol realization, the messages supporting step 3 may be embedded in the messages supporting session initiation. 4) The SCF confirms the dialogue establishment. SCF UE Core IMS RACS (7) Content Control and Content Delivery Flows (1) SessionIInitiationRequest (2) Session Initiation Request (4) Session Initiation Response (5) ResourcesCommit (6) Session Initiation Response (3) Content Delivery Channel Setup ECF/EFF ETSI ETSI TS 182 027 V3.5.1 (2011-03) 54 5) The P-CSCF within the Core IMS interacts with the RACS to commit all resources and to activate the service package(s) in transport network element at edge of network for enabling multicast joining. 6) The P-CSCF forwards the dialogue confirmation to the UE. 7) The UE starts joining multicast channels and receiving multicast flows. |
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, signalling procedures for the establishment of one or more content delivery channels network parameters necessary to handle the BC service take place between the UE and the SCF (see clause 8.3.1.2). NOTE 1: In a particular protocol realization, the messages supporting step 3 may be embedded in the messages supporting session initiation. 4) The UE confirms the establishment of the dialogue with the SCF. 5) The P-CSCF within the Core IMS interacts with the RACS to commit all resources and to activate the service package(s) in transport network element at edge of network for enabling multicast joining. 6) The core IMS forwards this confirmation to the SCF. 7) The UE starts joining multicast channels and receiving multicast flows. NOTE 2: SCF can initiate BC notification to UE (The procedure is described in clause 8.11.1), when UE receive the notification, it can initiate the BC session as figure 12. |
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 Channels (43) Resources Reservation (46) Resources Reservation Figure 13: Establishment of the delivery channel (42) The SCF initiates the establishment of one or more content delivery channels with the UE, by sending a media offer through the Core IMS. (43) The P-CSCF within the Core IMS interacts with the RACS according to the description given in the media offer. (44) The P-CSCF within the Core IMS forwards the media offer to the UE. (45) The UE provides a media answer to the Core IMS. (46) The P-CSCF within the Core IMS interacts with the RACS to update the configuration according to the media answer. (47) The media answer is propagated to the SCF. |
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 Channels (44) Media Answer for Content Channels (42) Resources Reservation (45) Resources Reservation Figure 14: Establishment of the delivery channel (41) The UE initiates the establishment of one or more content delivery channels with the SCF, by sending a media offer through the Core IMS. (42) The P-CSCF within the Core IMS interacts with the RACS to reserve transport resources according to the media offer. (43) The media offer is forwarded to the SCF. (44) The SCF sends a media answer through the Core IMS. (45) Within the Core IMS, the P-CSCF interacts with the RACS to update the previous reservation (optional). (46) The media answer is propagated to the UE. |
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 BC service. 2) The session modification request is forwarded to the SCF through the Core IMS. 3) Procedures for the negotiation of the network parameters necessary to handle the BC service take place between the UE and the SCF (see clause 8.3.1.2). NOTE: In a particular protocol realization, the messages supporting step 3 may be embedded in the messages supporting session modification. 4) The SCF acknowledges the session modification. 5) The P-CSCF within the Core IMS interacts with the RACS to commit all resources previously reserved. 6) The P-CSCF forwards the confirmation to the UE. 7) The UE starts joining multicast channels and receiving multicast flows. |
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) ResourcesCommit (6) Session Modification Response ECF/ EFF ETSI ETSI TS 182 027 V3.5.1 (2011-03) 58 Figure 16: SCF-initiated BC session modification 1) The SCF initiates a session modification procedure in order to start a negotiation for network parameters necessary to handle the BC service. 2) The session modification request is forwarded to the UE by the Core IMS. 3) Procedures for the negotiation of the network parameters necessary to handle the BC service take place between the UE and the MF (see clause 8.3.1.2). NOTE: In a particular protocol realization, the messages supporting step 3 may be embedded in the messages supporting session modification. 4) The UE confirms the modification of the session. 5) The P-CSCF within the Core IMS interacts with the RACS to commit all resources previously reserved. 6) The Core IMS forwards this modification to the SCF. 7) The UE starts joining multicast channels and receiving multicast flows. |
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) ResourcesCommit (4) Session Modification Response ECF/ EFF ETSI ETSI TS 182 027 V3.5.1 (2011-03) 59 SCF UE Core IMS RACS (5) Session Terimnation Confirm (4) Session Termination Confirm (1) Session ITermination Request (3) Session Termination Request (2) Resources release Figure 17: UE-initiated broadcast session release 1) The UE initiates a session termination. 2) The P-CSCF interacts with the RACS to release all transport resources that had been reserved for this session and to deactivate the service package in transport network element to prevent invalid multicast joining. 3) The Session Termination Request is routed by the Core IMS entities up to the SCF. 4) The SCF returns a Session Termination Confirm to the Core IMS. 5) The P-CSCF forwards the Session Termination Confirm to the UE. |
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-initiated broadcast session release 1) The SCF initiates a session termination. 2) The P-CSCF interacts with the RACS to release all transport resources that had been reserved for this session and to deactivate the service package in transport network element to prevent invalid multicast joining. 3) The Session Termination Request is routed by the Core IMS entities up to the UE. 4) The UE returns a Session Termination Confirm to the Core IMS. 5) The Core IMS forwards the Session Termination Confirm to the SCF. |
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 ETSI TS 182 027 V3.5.1 (2011-03) 61 1) The UE leaves a multicast channel and joins another multicast channel. 2) A delay may be applied. If the user switches channel again during this delay time, the flow is restarted at step 1. 3) The UE sends information about which channel is being watched. 4) Core IMS routes the information to the SCF. The SCF stores channel change information in the Service Action Data. 8.3.5 Signalling flows for transition from Broadcast TV to Broadcast TV with trick play Figure 20 provides the signalling flow for trick play of a Broadcast TV channel. In order to apply trick modes to a Broadcast TV session, this must be established as indicated in clause 8.3.1. The same session is used in the trick play session modification, in order not to change the bandwidth requirements on the network. At successful conclusion of these procedures the UE seamlessly transitions from viewing Broadcast TV to Broadcast TV with trick play. NOTE: As an alternative to the session modification, it is possible to initiate a separate session for trick modes handling, in addition to the Broadcast TV one, while keeping control of the bandwidth requirements between the two of them. This method is, however, out of the scope of the present document. ETSI ETSI TS 182 027 V3.5.1 (2011-03) 62 Figure 20: Signalling flow for initiating trick play of broadcast TV channel 1) Broadcast TV session initiation. NOTE 1: The procedures are the same as clause 8.3.2, Overview of the signalling flows for session initiation. RACS and channel establishment have been removed for purpose of simplification. 2) The UE sends information on the current channel being watched, in order for the SCF to know what channel should be recorded. 3) Core IMS routes the information to the SCF. Core IMS/RACS MCF UE SCF (2) Inform current channel (3) Inform current channel (4) Session Modification Request & Media offer for Content Control and Content Delivery Channel (5) Session Modification Request & Media offer for Content Control and Content Delivery Channel (6) Session Initiation Request & Media offer for Content Control and Content Delivery Channel (7) Session Initiation Response & Media answer for Content Control and Content Delivery Channel (8) Session Modification Response & Media answer for Content Control and Content Delivery Channel (9) Session Modification Response & Media answer for Content Control and Content Delivery Channel el ECF/EFF (10) Leave multicast channel (11) Content Control and Content Delivery Flows MF Reserver Resources Reserver Commit (1) Broadcast TV session initiation ETSI ETSI TS 182 027 V3.5.1 (2011-03) 63 4) When the UE initiates trick play mode of a Broadcast TV the UE sends a session modify request which includes a media offer for a content control channel and content delivery channel with the MF. If trick play service is not available for the UE, the session modification is not sent. NOTE 2: The Broadcast TV with trick play session modification is performed on the same session as the Broadcast TV session initiation. The existing reservation (for broadcast) needs to be modified to add a unicast flow that reuses the resources dedicated to the user. In the figure, RACS has been combined with Core IMS for the purpose of simplification. NOTE 3: Steps 2 and 3 are optional in a generic Broadcast TV session, but are required if trick play is activated. The implementation of both steps as separate messages or combined with step 4 is an implementation issue. 5) After reserving resources in RACS Core IMS forwards the session modification request to the SCF. 6) The SCF forwards the session modification request as a new session initiation to the MF along with the channel indication. The MF will determine if the programme currently broadcasted has trick play support.. Prior to replying the MF uses real time to calculate the media offset for the broadcast TV channel when replying with the offered media. If trick play service is not available for the UE the session modification is rejected and the old Broadcast TV session initiation (along with the previous reserved committed resources) is maintained. 7) The MF sends the session modification response to the SCF. 8) The SCF forwards the session modification response to the Core IMS. 9) After committing resources in RACS Core IMS forwards the session modification response to the UE. 10) The UE leaves the multicast channel. 11) The UE starts playing content and receiving unicast flow. NOTE 4: Alternatives to the above call-flow are for further study. 8.3.6 Signalling flows for transition from Broadcast TV with trick play to Broadcast TV The UE returns from Broadcast TV trick play to linear Broadcast TV, for example when the UE switches channels from a paused channel to another live Broadcast TV channels, or when the UE fast-forwarding in a unicast stream and catches up with the live Broadcast TV channel. The trigger to transition from Broadcast TV with Trick Play to Broadcast TV may be initiated by the UE, SCF or MCF. NOTE: The event to trigger the transition is outside of the present document. The UE or SCF may request a Broadcast TV session modification as described in clause 8.3.2, titled Overview of the signalling flows for session modification. The difference is that the Broadcast TV session modification is performed on the same session, in order to release unicast resources, and the SCF is responsible for releasing the resources in the MCF with a session termination request/response. The MCF may request a session termination towards SCF which in turn performs Broadcast TV session modification towards the UE. |
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 initiation, users should have subscribed a PPV program. The subscription information which may be saved as user profile include the user's indentity, BC service ID and BC program ID of the PPV program. 1) UE initiates the PPV program session as the BC session initiation procedures specified in clause 8.3.1.1.1, The PPV specific steps here are as follows: i) The PPV program session initiation request includes the BC service ID and the BC program ID of the PPV program. ii) When SCF receives the request, the SCF identifies the program according to the BC service ID and BC program ID, and verifies based on the IPTV user profile, that the program has been PPV subscribed. Upon successful verification, the SCF verifies that the program is ready to start, i.e. the current time is greater than/equal to program start time. Then accepts the request. If not, it refuses the request. NOTE 1: The SCF authorizes the BC Session Initiation for that BC Service ID based on the fact that BC Program ID has been PPV subscribed. In the answer to the session initiation, the SCF includes information related to that authorized PPV program to enable the Core IMS to provision RACS with necessary parameters. NOTE 2: The initiation of PPV program session may be triggered by the user's action or the notification from SCF (e.g. SCF detects the PPV program is ready to start, and sends a notification to UE as specified in clause 8.11.1). 2) The UE starts joining multicast channels and receiving multicast flows. 3) UE or SCF initiates the PPV program session release procedure as BC session release procedures specified in clause 8.3.3. As part of the PPV program session release, RACS is updated by removing the BC Service. NOTE 3: Session release for PPV service can be initiated either by SCF or UE. SCF initiates session release when detects the PPV program is over. NOTE 4: An alternative solution using release 2 mechanisms can also be used. The SCF indicates the BC service ID that identifies the PPV program either at session initiation (clause 8.3.1) if the PPV programm is already authorised or by initiating a session modification (clause 8.3.2). If the BC session is on-going when the authorisation duration has elapsed, the SCF modify the session to remove the appropriate BC service ID from the authorised BC service list. |
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 session initiation procedure (from the MF). The session can be terminated by the User Equipment using the procedures described in clause 8.4.3.1 or by the network clause 8.4.3.2. Interactions between the IMS and the RACS take place at different steps of the session initiation/modification and release. In certain cases such as in conventional content server deployments, it may be preferable that a content control channel and content delivery channel(s) be established separately. |
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 service. (10) Resources Commit (6) Content Control and/or Delivery Channel Setup UE (3) Session Initiation Request (11) Session Initiation Response SSF (1)Retrieve stored offset (optional) (2) COD offset (optional) (4) Session Initiation Request (7) Session Initiation (9) Session Initiation Response (8) Retrieve stored offset (optional) RACS (5) Session Initiation Request Core IMS MF SCF Respons e (12) Content Control flows ETSI ETSI TS 182 027 V3.5.1 (2011-03) 66 4) The session initiation request is routed by the Core IMS entities up to the SCF in charge of the requested CoD service. 5) The SCF performs service authorization as described in clause 5.1. If the UE is allowed to access the content, the SCF forwards the session initiation request to the selected MF. 6) Signalling procedures for establishment of a content control channel and optionally (see note 2) content delivery channels take place between the UE and the MF (see clause 8.4.1.2.1). NOTE 1: In a particular protocol realization, the messages supporting step 6 may be embedded in the messages supporting session initiation. NOTE 2: The establishment of the content delivery channel in the session initiation is only optional when network has provided information for only content control channel setup. In this case, the content delivery channel is established during session modification. 7) The MF confirms the establishment of the dialogue with the UE. 8) (Optionally) If the session initiation does not include a COD offset, the SCF may try to retrieve a stored offset for this CoD service in service action data. In this case, the SCF includes this offset in the session initiation answer. 9) The SCF forwards this confirmation to the Core IMS. 10) The P-CSCF within the Core IMS interacts with the RACS to commit all resources previously reserved. This includes opening pinholes for exchanging content control messages and/or content delivery. 11) The P-CSCF forwards the dialogue confirmation to the UE. |
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) Ressources Commit (6) Session Initiation Response (5) Content Control and/or Content Delivery Channel Setup (9) Session Initiation Response (1) Retrieve COD offset (optional) SSF (10) Retrieve COD offset (optional) (11) COD offset (optional) Figure 21A: SCF-initiated CoD session initiation 1) (Optionally) The SCF may retrieves the COD offset if present in service action data. 2) The SCF sends a session initiation request including the COD offset to the MF. 3) The SCF sends a session initiation request to the UE via the core IMS. 4) The Core IMS forwards the session initiation request to the UE. 5) If the UE accepts the request, signalling procedures for establishment of a content control channel and optionally (see note 2) content delivery channels take place between the UE and the MF via the SCF (see clause 8.4.1.2.2). NOTE 1: In a particular protocol realization, the messages supporting step 5 may be embedded in the messages supporting session initiation. NOTE 2: The establishment of the content delivery channel in the session initiation is only optional when network has provided information for only content control channel setup. In this case, the content delivery channel is established during session modification. 6) The UE confirms the establishment of the dialogue with the SCF. 7) The P-CSCF within the Core IMS interacts with the RACS to commit all resources previously reserved. This includes opening pinholes for exchanging content control messages and/or content delivery. 8) The core IMS forwards this confirmation to the SCF. 9) The MF confirms the establishment of the dialogue with the SCF. 10) (Optionally) UE may retrieve COD offset from service action data. 11) (Optionally) SSF may return COD offset for specified content. ETSI ETSI TS 182 027 V3.5.1 (2011-03) 68 After this point, UE may use the content control channel to request content to be streamed and the actual content will be then delivered/streamed over the content delivery channels. The content control channel will also be used to carry UE requests for controlling the streams, e.g. "pause", "fast forward", etc. |
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 channels from MF Figure 22 shows information flows applicable when network parameters necessary to handle the CoD service are provided by the MF as part of the session initiation procedure. This set of information flows assume that the UE does not receive a description of the network parameters required from the SSF before initiating the session. SCF UE MF Core IMS RACS (44) Media Offer for Content Control and Content Delivery (42) Media Offer for Content Control and Content Delivery (41) Media Offer for Content Control and Content Delivery (45) Media Answer for Content Control and Content Delivery (47) Media Answer for Content Control and Content Delivery (48) Media Answer for Content Control and Content Delivery (43) Resources Reservation (46) Resources Reservation Figure 22: Signalling flows for the establishment of the content control and content delivery channels from MF (41) The MF initiates negotiation of a content control channel and one or more content delivery channels with the UE, by sending a media offer to the SCF. (42) The media offer is forwarded to the Core IMS. (43) The P-CSCF within the Core IMS interacts with the RACS to reserve transport resources for the content control channel and one ore more content delivery channels. (44) The P-CSCF within the Core IMS forwards the media offer to the UE. (45) The UE provides a media answer to the Core IMS. (46) The P-CSCF within the Core IMS interacts with the RACS to update the reservation (optional). ETSI ETSI TS 182 027 V3.5.1 (2011-03) 69 (47) The media answer for the content control channel and one or more content delivery channels is propagated to the SCF. (48) The SCF forwards the media answer to the MF. 8.4.1.2.2 Signalling flows for the establishment of the content control and content delivery channels from UE Figure 23 provides an overview of the information flows for UE-initiated negotiation of the network parameters necessary to handle the CoD service. This set of information flows assume that the UE receives a description of the network parameters required from the SSF before initiating the session. SCF UE MF Core IMS RACS (44) Media Offer for Content Control and Content Delivery (45) Media Answer for Content Control and Content Delivery (41) Media Offer for Content Control and Content Delivery (43) Media Offer for Content Control and Content Delivery (48) Media Answer for Content Control and Content Delivery (46) Media Answer for Content Control and Content Delivery (42) Resources Reservation (47) Resources Reservation Figure 23: Signalling flows for the establishment of the content control and content delivery channels from UE (41) The UE initiates negotiation of a content control channel and one or more content delivery channels with the MF, by sending a media offer to the Core IMS. (42) The P-CSCF within the Core IMS interacts with the RACS to reserve transport resources for the content control channel and one or more content delivery channels. (43) The media offer is forwarded to the SCF. (44) The SCF forwards the media offer to the MF. (45) The MF provides a media answer to the SCF. (46) The SCF forward the media answer to the Core IMS. (47) Within the Core IMS, the P-CSCF interacts with the RACS to update the previous reservation (optional). (48) The media answer for the content control channel and one or more content delivery channels is propagated to the UE. ETSI ETSI TS 182 027 V3.5.1 (2011-03) 70 |
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 Content Control (48) Media Answer for Content Control (42) Resources Reservation (47) Resources Reservation Figure 24: Signalling flows for the establishment of the content control channel from UE (41) The UE initiates negotiation of a content control channel with the MF, by sending a media offer to the Core IMS. (42) The P-CSCF within the Core IMS interacts with the RACS to reserve transport resources for the content control channel. (43) The media offer is forwarded to the SCF. (44) The SCF forwards the media offer to the MF. (45) The MF provides a media answer to the SCF. (46) The SCF forward the media answer to the Core IMS. (47) Within the Core IMS, the P-CSCF interacts with the RACS to update the previous reservation (optional). (48) The media answer for the content control channel is propagated to the UE. |
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. using network parameters retrieved from content control messages) when no content delivery channels were set during this previous phase. In case of a session modification, the content delivery channel setup/modification procedure is always triggered by the entity initiating the session modification. |
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) The session modification request is forwarded to the SCF through the Core IMS. 3) The SCF performs service authorization as described in clause 5.1. If the UE is allowed to modify the content, the SCF forwards the session modification request to the MF. 4) Procedures for establishment of a content delivery channels take place between the UE and the MF (see clause 8.4.2.1). NOTE: The messages supporting step 4 are embedded in the messages supporting session modification. 5) The MF confirms the modification of the session. 6) The SCF forwards this modification to the Core IMS. 7) The P-CSCF within the Core IMS interacts with the RACS to commit all resources previously reserved. This includes opening pinholes for content delivery. 8) The P-CSCF forwards the confirmation to the UE. After this point, UE may request content to be delivered over the content control channel and the actual content will be then delivered over the content delivery channels. The content control channel will also be used to carry UE requests for controlling the streams over the content delivery channels, e.g. "pause", "fast forward", etc. (4) Content Control and/or Content Delivery Channel Setup (7) Resources Commit SCF UE MF Core IMS RACS (1) Session Modification Request (2) Session Modification Request (3) Session Modification Request (5) Session Modification Response (6) Session Modification Response (8) Session Modification Response Content Control and Content Delivery Flows ETSI ETSI TS 182 027 V3.5.1 (2011-03) 72 |
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 as described in clause 5.1. The SCF forwards the session modification request to the MF. 3) The session modification request is forwarded to the UE by the Core IMS. 4) Procedures for establishment of a content delivery channels take place between the UE and the MF (see clause 8.4.2.2). NOTE: The messages supporting step 4 are embedded in the messages supporting session modification. 5) The UE confirms the modification of the session. 6) The P-CSCF within the Core IMS interacts with the RACS to commit all resources previously reserved. This includes opening pinholes for content delivery. 7) The Core IMS forwards this modification to the SCF. 8) The SCF forwards the confirmation to the MF. After this point, UE may send a request over the content control channel to stream content and the actual content will be then delivered over the content delivery channels. (6) Resources Commit (4) Content Control and/or Content Delivery Channel Setup SCF UE MF Core IMS RACS (1) Session Modification Request (3) Session Modification Request (2) Session Modification Request (5) Session Modification Response (7) Session Modification Response (8) Session Modification Response Content Control and Content Delivery Flows ETSI ETSI TS 182 027 V3.5.1 (2011-03) 73 The content control channel will also be used to carry UE requests for controlling the content streams e.g. "pause", "fast forward", etc. 8.4.2.1 Signalling flows for the establishment/modification of the content delivery channel from UE Figure 27 provides an overview of the information flows for UE-initiated establishment or modification of the content delivery channel. SCF UE MF Core IMS RACS (48) Media Answer for Content Delivery (46) Media Answer for Content Delivery (41) Media Offer for Content Delivery (43) Media Offer for Content Delivery (44) Media Offer for Content Delivery (45) Media Answer for Content Delivery (42) Resources Reservation (47) Resources Reservation Figure 27: Signalling flows for the establishment/modification of the content delivery channel from UE (41) The UE initiates negotiation of one or more content delivery channel with the MF, by sending a media offer to the Core IMS. (42) The P-CSCF within the Core IMS interacts with the RACS to reserve transport resources for the content delivery channels. (43) The media offer is forwarded to the SCF. (44) The SCF forwards the media offer to the MF. (45) The MF provides a media answer to the SCF. (46) The SCF forward the media answer to the Core IMS. (47) Within the Core IMS, the P-CSCF interacts with the RACS to update the previous reservation (optional). (48) The media answer for the content delivery channels is propagated to the UE. |
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 Content Delivery (47) Media Answer for Content Delivery (48) Media Answer for Content Delivery (43) Resources Reservation (46) Resources Reservation Figure 28: Signalling flows for the modification of the content delivery channels from MF (41) The MF initiates negotiation of one or more content delivery channels with the UE, by sending a media offer to the SCF. (42) The media offer is forwarded to the Core IMS. (43) The P-CSCF within the Core IMS interacts with the RACS to reserve transport resources for the content delivery channels. (44) The P-CSCF within the Core IMS forwards the media offer to the UE. (45) The UE provides a media answer to the Core IMS. (46) The P-CSCF within the Core IMS interacts with the RACS to update the reservation (optional). (47) The media answer for the content delivery channels is propagated to the SCF. (48) The SCF forwards the media answer to the MF. |
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) Session Termination Request (2) Resources release Figure 29: UE-initiated session release 1) The UE initiate a session termination. 2) The P-CSCF interacts with the RACS to release all transport resources that had been reserved for this session. 3) The Session Termination Request is routed by the Core IMS entities up to the SCF. 4) The SCF forwards the Session Termination Request to the appropriate Media Function. 5) The Media Function (i.e. the MCF) release all resources associated with the session and returns a Session Termination Confirm. 6) The SCF forwards the Session Termination Confirm to the Core IMS. 7) The P-CSCF forwards the Session Termination Confirm to the UE. |
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) Session Termination Request (4) Resources release Figure 30: SCF-initiated session release 1) The SCF initiates a session termination towards the MF. 2) The Media Function (i.e. the MCF) releases all resources associated with the session and returns a Session Termination Confirm. 3) The SCF initiates a session termination towards the UE. 4) The P-CSCF interacts with the RACS to release all transport resources that had been reserved for this session. 5) The Session Termination Request is routed by the Core IMS entities up to the UE. 6) The UE returns a Session Termination Confirm to the Core IMS. 7) The Core IMS forwards the Session Termination Confirm to the SCF. |
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) Session Termination Request (3) Resources release Figure 31: MF-initiated session release 1) The MF initiates a session termination towards the SCF. 2) The SCF forwards the session termination request to the Core IMS. 3) The P-CSCF interacts with the RACS to release all transport resources that had been reserved for this session. 4) The Session Termination Request is routed by the Core IMS entities up to the UE. 5) The UE returns a Session Termination Confirm to the Core IMS. 6) The Core IMS forwards the Session Termination Confirm to the SCF. 7) The SCF forwards the Session Termination Confirm to the MF that releases all resources associated with the session. |
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 the transferee SCF. In the latter case, the transferor SCF will initiate a CoD session with the transferee UE at session transfer request from the transferor UE. NOTE: 3GPP Release 9 specifications are limited to UE centric push mode for session transfer, i.e. only the case in clause 8.4.4.1 is addressed by 3GPP in release 9. For reference, the related 3GPP specifications are TS 123 237 [17] and TS 124 237 [18]. |
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 transfer can be initiated. The transferor UE selects a devices and initiates the procedure. ETSI ETSI TS 182 027 V3.5.1 (2011-03) 78 Figure 31A: Terminal centric session transfer pushed from transferor UE to transferee UE 1) UE1 has initiated a dialogue to the CoD service as defined in clause 8.4.1. A session is on going with the MF1. 2) The user decides to transfer the session to another device. UE1 performs device discovery as defined in TS 123 237 [17], and TS 124 237 [18] to discover the devices that it can transfer the session to. 3) The UE1 may send an offset notification to the SCF. If the SCF has not received an offset notification from UE1 it uses CoD Service Action Data requested by the SCF procedure to acquire an offset. (3) Offset Notification SCF UE1 MF2 UE2 (4) Session Transfer Request MF1 (5) Session Transfer Request (8) Session Transfer Start Notification (6) Session Transfer Response (7) Session Transfer Response (10) Session Transfer Complete Notification (1) Session Initiation (11) Session termination (9) Session Initiation (2) Discover devices ETSI ETSI TS 182 027 V3.5.1 (2011-03) 79 4) UE1 sends a Session Transfer Request to the SCF via the core-IMS containing Session transfer identifier- STI (identity of the session to be transferred). The SCF obtains the CoD content-id, and perform service authorisation and checks that the user is authorised to perform session transfer. The SCF also obtains the UE2 identity and the target user identity from the incoming request. To allow UE2 to acquire the content id used to set up the initial session, UE1 shall include the content id in the session transfer request. 5) The Session Transfer Request, including the offset, is forwarded from the SCF to the UE2 via the Core-IMS. 6) UE2 receives an invitation to initiate a CoD session for the content indicated by the content-id. It acknowledges the Request by sending a Session Transfer Response to the SCF via the Core-IMS. 7) The SCF forwards the Session Transfer Response to the UE1 via the Core-IMS. 8) The UE2 informs the UE1 that it initiates the CoD session initiation by sending a Session Transfer Start Notification to the UE1 via the core-IMS. NOTE 1: This message can optionally go through the SCF. 9) CoD session initiation between the UE2 and MF2 via core-IMS is done as defined in clause 8.4.1.1.1. 10) The UE2 informs the UE1 that CoD session initiation is complete by sending a Session Transfer Complete Notification to the UE1. NOTE 2: This message can optionally go through the SCF. 11) The UE1 terminates the CoD session with the MF1 as defined in clause 8.4.3.1. 8.4.4.2 Network centric session Transfer pushed from transferor UE to transferee UE Figure 31B provides an overview of the information flows for CoD session transfer between the transferror UE (UE1) and the transferee UE (UE2) managed by the transferor SCF. For clarity purpose, core-IMS is not indicated in the figure but all messages go through it. ETSI ETSI TS 182 027 V3.5.1 (2011-03) 80 Figure 31B: Network centric session Transfer pushed from transferor UE to transferee UE 1) UE1 has initiated a dialogue to the CoD service as defined in clause 8.4.1. A session is on going with the MF1. The user decides to transfer the session to the another device. UE1 performs device discovery as defined by TS 123 237 [17], and TS 124 237 [18]. 2) The UE1 may send an offset notification to the SCF. If the SCF has not received an offset notification from UE1 it uses CoD Service Action Data requested by the SCF procedure to acquire an offset. 3) UE1 sends a Session Transfer Request to the SCF via the Core- containing the Session Tranfer Identfier-STI (the identity of the session to be transferred) and if necessary the UE2 ID (e.g. if the user ID corresponds to multiple UEs). The SCF obtains the CoD content-id, and performs service authorisation and also checks that the user is authorised to perform session transfer. The SCF also obtains the UE2 identity and the target user identity from the incoming request. To allow UE2 to acquire the content id used to set up the initial session, UE1 shall include the content id in the session transfer request. 4) The SCF replies by a Session Transfer Response to the UE1. UE1 MF 2 SCF UE2 (4) Session Transfer Request MF1 (1) Session Initiation (5) Session Transfer Response (6) Session Transfer Start Notification (7) Session Initiation (8) Session Transfer Complete Notification (9) Session termination (3) Offset Notification (2) Discover devices ETSI ETSI TS 182 027 V3.5.1 (2011-03) 81 5) The SCF informs the UE1 that it initiates the CoD session initiation by sending a Session Transfer Start Notification to the UE1 via the core-IMS. 6) SCF-initiated CoD session initiation between the UE2 and MF2 is done by the SCF as defined in clause 8.4.1.1.2. 7) The SCF informs the UE1 that CoD session initiation is complete by sending a Session Transfer Complete Notification to the UE1. 8) The SCF terminates the CoD session between the UE1 and the MF1 as defined in clause 8.4.3.2. 8.4.4.3 Session Replication pushed from transferor UE to transferee UE This scenario is identical to the session transfer in clause 8.4.4.1 with the exception that the last step of terminating the session towards the transferor UE is not carried out. Hence, the transferor UE maintains his session as well. At the end of the procedure both the transferor UE and the transferee UE have independent sessions watching same content from the same or a different MF. 8.4.4.4 Session Transfer pulled by the transferee UE Figure 31C provides an overview of the information flows for direct CoD session transfer between the transferor UE (UE1) and the transferee UE (UE2). In this scenario the transferee UE discovers the devices and the active sessions on these devices that he can transfer to his own device. ETSI ETSI TS 182 027 V3.5.1 (2011-03) 82 Figure 31C: Session Transfer pulled by the transferee UE 1) UE1 has initiated a dialogue to the CoD service as defined in clause 8.4.1.1.1. A session is on going with the MF1. 2) The user decides to go to his device UE2, to transfer an ongoing CoD session from device UE1. The user on UE2 performs device discovery and requests from SCF the active sessions on these devices, as defined by TS 123 237 [17], and TS 124 237 [18]. SCF UE1 MF2 UE2 MF1 (4) Session Transfer Start Notification (5) Session Transfer Complete Notification (6) Session termination (3) Session Initiation Core IMS (1) Session Initiation (2) Discover devices and active sessions ETSI ETSI TS 182 027 V3.5.1 (2011-03) 83 3) The user on UE2 sends a Session initiation to the SCF via the core-IMS, to transfer the session from device UE1. The UE includes the Session Transfer Identfier-STI (identity of the session to be transferred) in his request. The SCF obtains the CoD content-id, from the incoming session initiation request (acquired by UE2 in step2), and performs service authorisation and checks that the user is authorised to perform session transfer. UE1 may send an offset notification to SCF. If the SCF has not received an offset notification from UE1 it uses network initated content marker procedure to acquire an offset. 4) UE2 informs the UE1 that it initiates the CoD session initiation by sending a Session Transfer Start Notification to the UE1 via the core-IMS. NOTE 1: This message can optionally go through the SCF. 5) The UE2 informs the UE1 that CoD session initiation is complete by sending a Session Transfer Complete Notification to the UE1. NOTE 2: This message can optionally go through the SCF. 6) The UE1 terminates the CoD session with the MF1 as defined in clause 8.4.3.1. 8.4.4.5 Session Replication Between transferor to transferee in a pull mode transfer This scenario is identical to the session transfer in clause 8.4.4.4 with the exception that the last step of terminating the session towards the transferor UE is not carried out. Hence, the transferor UE maintains his session as well. At the end of the procedure both the transferor UE and the transferee UE have independent sessions watching same content from the same or a different MF. |
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 may also include a indicator to inform the SCF of the reason for the CoD SAD update. 2) The IMS core forwards this request to the SCF. SCF UE Core IMS (1) CoD SAD update request (2) CoD SAD update Request (5) CoD SAD update Response (4) CoD SAD update Response (3) Save content offset ETSI ETSI TS 182 027 V3.5.1 (2011-03) 84 3) The SCF store this offset as service action data for this user. 4) The SCF confirms the CoD SAD update. 5) The IMS core forwards the response to the UE. |
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 initiation is performed as described in clause 8.4.1. 2) MF detects a pause, end of session or that the UE becomes offline unexpectedly. The MF may decides to send changes of SAD to SCF. 3) MF sends a CoD SAD update request to save the current CoD SAD. This request may also include a indicator to inform the SCF of the reason for the CoD SAD update. 4) The IMS core forwards this request to the SCF. 5) The SCF updates the CoD SAD. 6) The SCF confirms the CoD SAD update. 7) The IMS core forwards the response to the MF. ETSI ETSI TS 182 027 V3.5.1 (2011-03) 85 |
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 IPTV services (CoD/N-PVR/, etc.). Figure 31F: SCF SAD Request Procedure 1) The SCF sends a SAD request to the MF, via the IMS core, to request the offset during an ongoing IPTV service. 2) The IMS core forwards this request to the appropriate MF for the IPTV service. 3) The MF acquires the requested information. 4) The MF returns to core IMS the requested information in a SAD response. 5) The IMS core forwards the response to the SCF. 8.4.6 Signalling flows for generating playlist by SCF and sending playlist information from SCF to MF during CoD session initiation Figure 31G provides an overview of the information flows for playlist generation by SCF and sending playlist information from SCF to MF when UE initiated CoD session. SCF Core IMS MF (1) IPTV SAD Request (3) MF fetches the information (2) IPTV SAD Request (4) IPTV SAD Response (5) IPTV SAD Response ETSI ETSI TS 182 027 V3.5.1 (2011-03) 86 Figure 31G: Playlist communication during CoD session initiation 1) The UE initiates a dialogue to the CoD service as defined in clause 8.4.1.1.1, step 3. 2) The session initiation request is routed by the Core IMS entities up to the SCF in charge of the requested CoD service as defined in clause 8.4.1.1.1, step 4. 3) The SCF performs service authorization as described in clause 5.1. If the UE is allowed to access the service, the SCF generates playlist information or fetches a pre-configured playlist from a repository, based on the content ID carried in the session initiation request. Other information (e.g. the User ID, etc.) may also be used to generate the playlist. The playlist contains the list of content ID to be played and optionally content duration and restricted trick-play indication for each content. The data model for playlist is defined in clause 8.4.6.1. 4) The SCF selects an appropriate MF and forwards the session initiation request including playlist information to the selected MF. NOTE 1: The above procedure supports only content delivery from one single MF. 5) The MF interprets playlist information and prepares for content delivery. 6) Content Control and or Content Delivery Channel Setup procedures and finalization of the CoD Session initiation procedure follow clause 8.4.1.1.1, steps 6-11. NOTE 2: During this signalling, the UE might learn that a playlist was generated and act accordingly. Depending on the service type, the UE might already have learned the playlist in advance of service invocation. |
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 8.4.1.1.1 (3) playlist generation/ fetching ETSI ETSI TS 182 027 V3.5.1 (2011-03) 87 Figure 31H: IPTV playlist |
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 generation by SCF and sending playlist information from SCF to MF during an existing CoD session. This playlist may be a new playlist or an update. IPTV playlist IPTV Content ContentID: String Duration: String Begin Time: String Restricted trick play: boolean 1…n ETSI ETSI TS 182 027 V3.5.1 (2011-03) 88 Figure 31I: Playlist communication during an existing CoD session 1) A CoD session has been successfully established as described in clause 8.4.1.1. 2) Due to detecting an event, the SCF may choose to generate or update playlist information for the ongoing CoD session. The playlist contains the list of content ID to be played and optionally content duration and restricted trick-play indication for each content. 3) The SCF passes the playlist information to the MF. 4) The MF interprets the playlist information and acts accordingly. This may have immediate impact on the ongoing media channel. NOTE: A new or updated playlist might make a modification of the session necessary. |
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 switch within a CoD playlist 1) The UE initiates a dialogue to the CoD service as defined in clause 8.4.6. In addition,the playlist which is generated by the SCF as defined in clause 8.4.6 may be forwarded to the UE by the MF for user to choose the subsequent content. 2) The UE sends the content switch request related to the selected content within the playlist. The similar mechanism defined in TS 126 234 [i.20] clause 5.5.4.2 may be used here. 3) The MF checks that the selected content is referred in the playlist, and confirms the request. 4) The MF starts to deliver the new content, reusing the established media channel in case of the numbers of channels and QoS requirements are the same as the previous channel. NOTE: Session modifications may be needed if QoS requirements of the new content is not the same as the previous one. |
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.