hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
1648b3e8e46828428b32588407b8d464 | 183 025 | 5.3 H.248 Service State | One of the key descriptors of Terminations in the present document is the ServiceStates property within the Termination State Descriptor: Possible values: InService The termination is in-service and functioning normally. OutOfService The termination is out-of-service and not available for traffic. Test The termination ... |
1648b3e8e46828428b32588407b8d464 | 183 025 | 6 Management Primitives | As stated previously, specific management systems, architectures and protocols are outside the scope of the present document. Rather, the present document considers only a high level set of primitives which directly result in the triggering of H.248 signalling. The following management primitives are defined in the pre... |
1648b3e8e46828428b32588407b8d464 | 183 025 | 7 Failure/Recovery Scenarios | Certain failure scenarios also result in the triggering of H.248 signalling. The present document defines the following set of such scenarios: • Nodal failure and recovery of a MG/MGC. This can be due to hardware or software faults. • Termination failure and recovery. Examples of this are termination failure/recovery o... |
1648b3e8e46828428b32588407b8d464 | 183 025 | 8 Redundancy Scenarios | The H.248 non call related procedures are also impacted by the redundancy architectures chosen at a MG/MGC. Examples of such scenarios are: • MGC Hand-Off. This functionality enables a MGC to terminate an existing control association and establish a new control association to an alternative MGC. This procedure can be a... |
1648b3e8e46828428b32588407b8d464 | 183 025 | 9 General Use Cases | The following use cases and their interaction with the H.248 non-call related procedures are considered in the present document. Configuration Management: • Enable MG. • Enable MGC. • Disable MG (Graceful). • Disable MG (Immediate). • Disable MGC. • Enable Termination. • Disable Termination (Graceful). • Disable Termin... |
1648b3e8e46828428b32588407b8d464 | 183 025 | 10.1 Enable MG | This management primitive is applicable to both the MGC and MG. It is recommended that this primitive is initially sent to the MGC and subsequently to the MG. |
1648b3e8e46828428b32588407b8d464 | 183 025 | 10.1.1 Enable MG (at MGC) | This use case is triggered by management action that results in a MG being enabled at the MGC. There are no H.248 procedures associated with this action. The MGC simply awaits a registration from the MG (see clause 10.1.2). |
1648b3e8e46828428b32588407b8d464 | 183 025 | 10.1.2 Enable MG (at MG) | This use case is triggered by management action that results in a MG being brought into service. The MG will have been provisioned with the identity/address of one or more MGC(s). The H.248 procedures are dependent on whether the MG undergoes a cold or warm boot and are as follows: MG Cold Boot 1) The MG registers with... |
1648b3e8e46828428b32588407b8d464 | 183 025 | 10.2 Enable MGC | This management primitive is applicable only to the MGC and results in a MGC being brought into service. The MGC will have been provisioned with the H.248 mid and possibly the transport address of the H.248 control association of its MGs. The following H.248 procedures are performed: 1) The MGC may optionally check on ... |
1648b3e8e46828428b32588407b8d464 | 183 025 | 10.3 Disable MG (Graceful) | This primitive is applicable to both the MG and MGC and covers the use case of management action that results in a MG being taken out of service gracefully. It is recommended that the network management system performs a Disable MG (Graceful) command to the MGC. The one scenario where a Disable MG (Graceful) command to... |
1648b3e8e46828428b32588407b8d464 | 183 025 | 10.3.1 Disable MG (Graceful) (at MGC) | On receipt of this primitive, the MGC performs the following actions: 1) The MGC inhibits any new calls/connections to the MG and allows existing calls/connections to expire naturally/normally. 2) In the event of new calls originating from the MG (e.g. an AGW), the MGC would handle them appropriately via call related p... |
1648b3e8e46828428b32588407b8d464 | 183 025 | 10.3.2 Disable MG (Graceful) (at MG) | The following H.248 procedures are applied: 1) The MG informs the MGC via the MG SERVICE CANCELLATION (GRACEFUL) procedure. This procedure enables the MG to specify a timer (the ServiceChangeDelay) during which it is anticipated that all existing calls/connections on that MG will expire normally. 2) If applicable, the ... |
1648b3e8e46828428b32588407b8d464 | 183 025 | 10.4 Disable MG (Immediate) | This primitive is applicable to both the MG and MGC and covers the use case of management action that results in a MG being taken out of service immediately. |
1648b3e8e46828428b32588407b8d464 | 183 025 | 10.4.1 Disable MG (Immediate) (at MGC) | On receipt of this primitive, the MGC performs the following actions: 1) The MGC inhibits any new calls/connections to the MG and force releases existing calls/connections. 2) In the event of new calls originating from the MG (e.g. an AGW), the MGC would handle them appropriately via call related procedures (e.g. rejec... |
1648b3e8e46828428b32588407b8d464 | 183 025 | 10.4.2 Disable MG (Immediate) (at MG) | The following H.248 procedures are performed: 1) The MG informs the MGC via the MG SERVICE CANCELLATION (FORCED) procedure. 2) The MG responds to the management system. Note that existing connections are still hanging on the MG. 3) On receipt of the MG SERVICE CANCELLATION (FORCED) message, the MGC force releases any c... |
1648b3e8e46828428b32588407b8d464 | 183 025 | 10.5 Disable MGC | This primitive is sent to a MGC and results in a MGC being taken out of service. Prior to the MGC being disabled, it is recommended that the MGC inform its dependent MGs to move their control associations to an alternative MGC via the MGC HANDOFF procedure (clause 10.18) or that all dependent MGs are disabled prior to ... |
1648b3e8e46828428b32588407b8d464 | 183 025 | 10.6 Enable Termination | This management primitive is applicable to both the MGC and MG. It is recommended that this primitive is initially sent to the MGC and subsequently to the MG. |
1648b3e8e46828428b32588407b8d464 | 183 025 | 10.6.1 Enable Termination (at MGC) | The following H.248 procedures are performed: 1) The MGC may: a) Optionally assume that the corresponding termination is in-service on the MG, in which case the MGC attempts to use the termination and will receive an error code if the termination is not available at the MG end. On receipt of any such error code, the MG... |
1648b3e8e46828428b32588407b8d464 | 183 025 | 10.6.2 Enable Termination (at MG) | The following H.248 procedures are performed: 1) The MG informs the MGC via the MG TERMINATION AVAILABLE procedure. If a successful response is obtained the termination is now in-service at both the MG and MGC. If a negative response/error descriptor is received, the MG periodically repeats the MG TERMINATION AVAILABLE... |
1648b3e8e46828428b32588407b8d464 | 183 025 | 10.7 Disable Termination (Graceful) | This primitive is applicable to both the MG and MGC and covers the use case of management action that results in a termination being taken out of service gracefully. It is recommended that the network management system performs a Disable Termination (Graceful) command to the MGC. The one scenario where a Disable Termin... |
1648b3e8e46828428b32588407b8d464 | 183 025 | 10.7.1 Disable Termination (Graceful) (at MGC) | The following actions are performed: 1) The MGC prevents any new calls/connections being offered to the affected termination. 2) If there are any current calls/connections on the termination, the MGC allows them to expire normally/naturally. 3) When all calls are released, the MGC informs the management system. ETSI ET... |
1648b3e8e46828428b32588407b8d464 | 183 025 | 10.7.2 Disable Termination (Graceful) (at MG) | The following actions are performed: 1) The MG informs the MGC via the MG TERMINATION OOS GRACEFUL procedure. This procedure enables the MG to specify a timer (the ServiceChangeDelay) during which it is anticipated that all existing calls/connections on that MG termination will expire normally. On receipt of this messa... |
1648b3e8e46828428b32588407b8d464 | 183 025 | 10.8 Disable Termination (Immediate) | This primitive is applicable to both the MG and MGC and covers the use case of management action that results in a termination being taken out of service immediately. |
1648b3e8e46828428b32588407b8d464 | 183 025 | 10.8.1 Disable Termination (Immediate) (at MGC) | The following H.248 procedures are performed: 1) The MGC force releases all affected calls/connections, subtracting appropriate terminations on the MG. |
1648b3e8e46828428b32588407b8d464 | 183 025 | 10.8.2 Disable Termination (Immediate) (at MG) | This use case is triggered by management action that results in a MG termination being taken out of service immediately. The following H.248 procedures are performed: 1) The MG informs the MGC via the MG TERMINATION UNAVAILABLE procedure. 2) The MGC now force releases all affected calls/connections including subtractin... |
1648b3e8e46828428b32588407b8d464 | 183 025 | 10.9 MG Failure and Recovery | This use case is triggered by a hardware/software failure on the MG. The following H.248 procedures are performed: 1) If possible, the MG informs the MGC via the MG SERVICE CANCELLATION (FORCED) procedure. The MGC force releases all affected calls. 2) On recovering, the MG restarts and informs the MGC. The procedures o... |
1648b3e8e46828428b32588407b8d464 | 183 025 | 11.1 MG Registration (Cold Boot) | Table 11.1-1 shows the contents of the MG REGISTRATION (COLD BOOT) and MG REGISTRATION (COLD BOOT) Ack command/response pair. Table 11.1-1: MG Registration (Cold Boot) and MG Registration (Cold Boot) Ack Command / Response Initiated Information element name Information element required Information element description C... |
1648b3e8e46828428b32588407b8d464 | 183 025 | 11.2 MG Restoration | Table 11.2-1 shows the contents of the MG Restoration and MG Restoration Ack command/response pair. Table 11.2-1: MG Restoration and MG Restoration Ack Command / Response Initiated Information element name Information element required Information element description Context M This information element indicates the H.24... |
1648b3e8e46828428b32588407b8d464 | 183 025 | 11.3 Packages Audit | This procedure is typically performed against the ROOT termination, in which case the MG returns all supported packages. It is also possible for the MGC to request a packages audit against other than the ROOT termination (e.g. a circuit termination) in which case the MG returns the sub-set of the packages that are appl... |
1648b3e8e46828428b32588407b8d464 | 183 025 | 11.4 Context Audit | This procedure is invoked by the MGC to check/determine the list of active contexts and related terminations on the MG. There are a number of variations to this audit dependent on the amount of information available to the MGC prior to the audit (e.g. context identity known or termination naming scheme known etc.). A M... |
1648b3e8e46828428b32588407b8d464 | 183 025 | 11.5 MG Termination Available | Table 11.5-1 shows the contents of the MG Termination Available and MG Termination Available Ack command/response pair. Table 11.5-1: MG Termination Available and MG Termination Available Ack Command / Response Initiated Information element name Information element required Information element description Context M Thi... |
1648b3e8e46828428b32588407b8d464 | 183 025 | 11.6 MG Termination Unavailable | Table 11.6-1 shows the contents of the MG Termination Unavailable and MG Termination Unavailable Ack command/response pair. Table 11.6-1: MG Termination Unavailable and MG Termination Unavailable Ack Command / Response Initiated Information element name Information element required Information element description Conte... |
1648b3e8e46828428b32588407b8d464 | 183 025 | 11.7 Audit Termination State | Table 11.7-1 shows the contents of Audit Termination State and Audit Termination State Ack command/response pair. Table 11.7-1: Audit Termination State and Audit Termination State Ack Command / Response Initiated Information element name Information element required Information element description Context M This inform... |
1648b3e8e46828428b32588407b8d464 | 183 025 | 11.8 Set ROOT Termination Events/Properties | Table 11.8-1 shows the contents of Set ROOT Termination Events/Properties and Set ROOT Termination Events/Properties Ack command/response pair. Table 11.8-1: Set ROOT Termination Events/Properties and Set ROOT Termination Events/Properties Ack Command / Response Initiated Information element name Information element re... |
1648b3e8e46828428b32588407b8d464 | 183 025 | 11.9 MGC Initiated Service Restoration | Table 11.9-1 shows the contents of the MGC Initiated Service Restoration and MGC Initiated Service Restoration Ack command/response pair. Table 11.9-1: MGC Initiated Service Restoration and MGC Initiated Service Restoration Ack Command / Response Initiated Information element name Information element required Informati... |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 1 Scope | The present document specifies the architecture and functions of an IPTV system that makes use of the NGN IMS architecture and its features, implementing the requirements defined in TS 181 014 [14] and TS 181 016 [15]. The present document has taken IPTV solutions defined by other organizations (such as DVB, ATIS IIF, ... |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 2 References | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the reference document (including any amendments) applies. Referenced documents which ar... |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 2.1 Normative references | The following referenced documents are necessary for the application of the present document. [1] ETSI ES 282 001: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); NGN Functional Architecture". [2] ETSI TS 182 006: "Telecommunications and Internet converged Services an... |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 2.2 Informative references | The following referenced documents are not necessary for the application of the present document but they assist the user with regard to a particular subject area. [i.1] DSL Forum Technical Report TR-126: "Triple-play Services Quality of Experience (QoE) Requirements". [i.2] Void. [i.3] ETSI ES 282 010: "Telecommunicat... |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 3 Definitions and abbreviations | |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: content control: procedure for controlling content delivery NOTE: e.g. starting content delivery, playback of content (such as pause, fast and slow playback, reverse playback. rewinding, jumping forwards or backwards), stopping content... |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: ADM Ad Management Service ADS Ad Decision Service AS Application Server BC BroadCast CIS Content Information Service CM Content marker CoD Content on Demand C-PVR Client Personal Video Recorder CR Content Recommendation CRS Content Recommendat... |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 4 High-level overview | User Equipment Application Functions & IPTV Service Functions Core IMS User Profiles Manage- ment Functions Content Provider Functions Media Delivery, Distribution & Storage Transport Control Functions Transport Processing Functions Transport Functions Figure 1: High level functional architecture for IMS-based IPTV NOT... |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 5 Overview of functional entities | |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 5.1 Functional architecture for IPTV services | |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 5.1.1 Functional architecture overview | The overall functional architecture for IPTV service is shown in figure 2. ETSI ETSI TS 182 027 V3.5.1 (2011-03) 18 Figure 2: Functional architecture for IPTV services NOTE 1: Only Xc and Xd are explicitly shown as traversing the Transport Processing Functions. For the sake of simplicity other reference points are only... |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 5.1.2 IPTV services | |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 5.1.2.0 Compliance | An IPTV solution is compliant to the present document if the following points are fulfilled. • All mandatory services and features are implemented as specified in the present document. • If an optional service or feature is implemented, then it is implemented as specified in the present document. • If an optional servi... |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 5.1.3 Functional entities | Refer to clause 5.1.5. |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 5.1.3A Generic Capabilities | IPTV Generic IPTV Capabilities: 1. service discovery and selection 2. service control 3. service interaction 4. media control 5. media delivery 6. content protection 7. content management and distribution 8. interactions with other NGN services ETSI ETSI TS 182 027 V3.5.1 (2011-03) 21 |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 5.1.4 Elementary Functions (EF) | General: 1. network attachment 2. registration 3. resource Management 4. charging information IPTV elementary functions: Service related elementary functions 5. service discovery 6. service authorization 7. service selection 8. service initiation 9. service control 10. service information handling (e.g. metadata) 11. s... |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 5.1.4.1 Content Security Functions (CSF) | Content security elementary functions are described in clause 10.2. |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 5.1.5 Functional Entities | |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 5.1.5.1 Service Discovery and Selection Functions (SDF and SSF) | The Service Discovery Function (SDF) and Service Selection Function (SSF) are functions which provide information necessary to the UE to select an IPTV service. Tasks of the SDF: • Generates and/or provides the service attachment information. • Provides personalized service discovery. The service attachment information... |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 5.1.5.2 IPTV Service Control Functions (SCF) | Tasks of SCF: • Service authorization during session initiation and session modification, which includes checking IPTV users' profiles in order to allow or deny access to the service. • Credit limit and credit control (using the on-line charging systems ES 282 010 [i.3]). In addition, the SCF performs the following tas... |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 5.1.5.3 IPTV Media Control and Delivery Functions (MCF and MDF) | IPTV Media Functions are in charge of controlling and delivering the media flows to the UE. They are split into Media Control Functions (MCF) and Media Delivery Functions (MDF). Tasks of Media Control Function (MCF): • Handling media flow control of MDF. • May manage the media processing of MDF. • Monitoring the status... |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 5.1.5.4 UPSF | The UPSF holds the IMS user profile and possibly IPTV specific profile data (see clause 7). It communicates with IPTV Service Control Functions at the Sh reference points and with the Core IMS at the Cx reference point as defined in ES 282 007 [11]. When multiple instances of a UPSF exist, the Core IMS and the IPTV Ser... |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 5.1.5.5 Transport processing functions | IPTV services make use of generic transport processing functions defined in ES 282 001 [1]. 5.2 Interactions between Service Control function and Media Functions The relationship between Service Control Function (SCF) and Media Function (MF), composed of Media Control Function and Media Delivery Function, is shown in f... |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 5.3 Void | |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 5.4 Inter-destination media synchronization | Inter-destination media synchronization is an optional generic capability, aimed at servicing requiring this capability, see TS 181 016 [15], clause A.9.6 for examples. The Media Synchronization Application Server (MSAS) and Synchronization Client (SC) are functions that provide inter-destination media synchronization.... |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 5.4.1 Functional entities MSAS and SC | The inter-destination media synchronization (IDMS) mechanism uses the concept of synchronization sessions. Each synchronization session involves a Media Synchronization Application Server (MSAS) and multiple Synchronization Clients (SC). A synchronization session is used for the inter-destination synchronization of IPT... |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 5.4.2 Mapping onto the IPTV architecture | The synchronization architecture can be mapped onto the IPTV architecture in the following ways. Mapping 1: SC in UE • The session-oriented part of the MSAS is an elementary function of the SCF. For synchronisation using a direct communication channel between multiple UEs, the MSAS is co-located with the SC in a UE. • ... |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 5.4.3 Modification and re-origination of media streams | In addition to inter-destination media synchronization, additional synchronisation measures are needed in case a media stream is modified or re-originated during transport. Examples of these are transcoding, HD-to-SD conversion and user-generated comments to a live broadcast. In such cases, additional media-stream-modi... |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 5.5 IPTV Service State | |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 5.5.1 General | IPTV service states is defined as a snapshot of the information related to an ongoing IPTV service, see clause 3.1. Examples include the current BC program ID, the ID of current CoD content, the state of PVR recordings, the media state of services and invoked trick play events, commercial breaks in services and combina... |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 5.5.2 Relationship between IPTV Service State and IPTV presence | Generally, a hierarchical relation exists between the internal service states of Functional Elements, the IPTV Service State information and Presence information; the internal service state information can be aggregated in IPTV Service State, and IPTV Service State data can be used to update Presence. |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 6 Reference points | |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 6.1 UE - SSF (Xa) | This reference point between UE and SSF is used by the UE to make appropriate service selections. |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 6.2 UE - IPTV Service Control Functions (Ut) | This reference point between UE and IPTV Service Control Functions is used by the UE for the purpose of service profile configuration. Use of the Ut reference point conforms to ES 282 007 [11]. |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 6.3 UE - Core IMS (Gm) | Use of the Gm reference point conforms to ES 282 007 [11]. |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 6.4 UE - Media Control Functions (Xc) | This Xc reference point (for media control) is a logical end-to-end reference point between the UE and the IPTV Media Control Function that is used to exchange media control messages for controlling the IPTV Media flow. NOTE: Transport related reference points are used to carry media control messages over underlaying t... |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 6.5 UE - Media Delivery Functions (Xd) | This Xd reference point (for media delivery) is a logical end-to-end reference point between the UE and the IPTV Media Delivery Function that is used to deliver media data. NOTE: Transport related reference points are used to carry media delivery data over underlaying transport segment (defined in ES 282 001 [1]) and a... |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 6.6 IPTV Service Control Functions (SCF) - UPSF (Sh) | Use of the Sh reference point conforms to ES 282 007 [11]. |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 6.7 Core IMS - UPSF (Cx) | Use of the Cx reference point conforms to ES 282 007 [11]. |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 6.8 Core IMS - IPTV Service Control Functions (ISC) | Use of the ISC reference point conforms to ES 282 007 [11]. |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 6.9 Core IMS - IPTV Media Functions (y2) | This reference point between S-CSCF and IPTV Media Control Function (MCF) carries IPTV Service Control Signalling originating from the IPTV Service Control Function (SCF) to control the MCF. In case the CSCF and the Media Control Function are in different administrative domains, signalling flows go through an IBCF. ETS... |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 6.10 Core IMS - SDF (ISC) | Use of the ISC reference point conforms to ES 282 007 [11]. |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 6.11 SDF - UPSF (Sh) | Use of the Sh reference point conforms to ES 282 007 [11]. |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 6.12 Void | Void. |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 6.13 Application Functions - NASS (e2) | Use of the e2 reference point conforms to ES 282 007 [11] and ES 282 004 [3]. NOTE: Application Function entities associated to IPTV services such as core IMS and SCF may query the UE location from the CLF in order to fulfil their tasks. |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 6.14 Core IMS - RACS (Gq') | Use of the Gq' reference point conforms to ES 282 007 [11] and ES 282 003 [8]. |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 6.15 NASS - RACS (e4) | Use of the e4 reference point conforms to ES 282 003 [8] and ES 282 004 [3]. |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 6.16 IPTV Service Control Functions - SLF (Dh) | Use of the Dh reference point conforms to ES 282 007 [11]. |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 6.17 Core IMS - SLF (Dx) | Use of the Dx reference point conforms to ES 282 007 [11]. 6.18 IPTV Media Control Function - IPTV Media Delivery Function (Xp) This Xp reference point between the Media Control Function (MCF) and Media Delivery Function is used to control media delivery sessions to support media delivery session setup when content is ... |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 6.19 MSAS-SC reference point (Sync) | This optional reference point is between Media Synchronization Application Server (MSAS) and media-stream-synchronizing Synchronization Client (SC). It is used to set up synchronization sessions and to exchange synchronization status information and synchronization settings instructions with functional entities in the ... |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 6.20 MSAS-SC' reference point (Sync') | This optional reference point is between Media Synchronization Application Server (MSAS) and media-stream-modifying Synchronization Client (SC'). It is used to set up synchronization sessions and to exchange synchronization status information with functional entities in the network where to-be-synchronized media stream... |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 6.21 SSF-SCF reference point (Ss') | The Ss' optional reference point between IPTV SCF and SSF is used to exchange required service information and/or service provider information(e.g. service provider details, UGC specific information, etc. NOTE 1: Since SSF is not designed for content metadata maintenance/management. How the content metadata is managed ... |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 7 User data | |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 7.1 Classification of information | Five categories of user data are involved in providing IPTV services: 1. IMS-profile: This category includes all information required to establish IMS sessions and access IPTV services hosted in Application Servers, as described in TR 182 005 [i.4]. 2. Communication Services profile: This category encompasses all infor... |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 7.2 Location and access to user data | The user data is located in UPSF or in more functions/locations as described in clause 7.2.1. When all user data is stored in the UPSF only, as transparent data associated to Application Server functions then this approach is referred to as the consolidated approach. If user data is stored at multiple locations and dis... |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 7.2.1 Data management functions | IMS-profile information is managed by the UPSF. Communication Services profile information may be managed by dedicated database functions, the Application Server functions hosting the communication services, or by the UPSF as transparent data (repository function) associated to these Application Server functions. In th... |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 7.2.2 Access from other application servers | User data stored in the UPSF can be accessed by Application Servers at the Sh reference point. Direct access to user data stored in Application Servers is outside the scope of the present document. However, part of these data may be indirectly exposed through Web Services and/or SIP Event packages. |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 7.2.3 Access from User Equipment (UE) | A subset of IPTV user-profile information may be accessed from the User Equipment at the Ut reference point. |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 7.2.4 Access from the SSF | For the purpose of personalized service selection, the SSF may need to access user data. In the case when such user data is stored in the UPSF, it can be accessed by the SSF at the Sh reference point when the SSF is in the same domain. On the contrary, when such user data is stored in the AS or in a stand alone server ... |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 7.3 IPTV user profile structure | |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 7.3.1 IPTV user profile structure | An IPTV user profile comprises: • zero, one or more instances of the UE object class comprising UE capabilities attribute and associated UE ID; • at least one instance of a Broadcast (BC) or a Content on Demand (CoD) object class (see figure 7); • zero or one instance of the Global settings object class; • zero or one ... |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 7.3.1.1 BC service package | A service package is a group of one or more BC service. |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 7.3.1.2 BC service | A service relates to a particular TV channel and associated quality definition (e.g. SD or HD). |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 7.3.1.3 UE | Contains the UE's Id and its capabilities. |
a51f761c27385e5a8c90041b2c701012 | 182 027 | 7.3.1.4 Global settings: language preference | This attribute defines which default language the user would like to use. For instance, this could be the default language for the GUI that is displayed on the UE, and/or the default language used for subtitles. BC Service Package Id: String Description: String BC Service package Profile Id: String IPTV Profile Parenta... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.