hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
b708cbb24b9b1d04a3865f5f2ea8c6ab | 182 012 | 6 Service Architecture | |
b708cbb24b9b1d04a3865f5f2ea8c6ab | 182 012 | 6.1 Overview | The service architecture for the PES and the IMS subsystems is the same. The generic behaviour of a application server functions is identical with respect to the PSTN/ISDN Emulation Subsystem and the TISPAN IMS. However, depending on the type of services to be emulated, certain application servers may need to understan... |
b708cbb24b9b1d04a3865f5f2ea8c6ab | 182 012 | 6.2 Reference points | |
b708cbb24b9b1d04a3865f5f2ea8c6ab | 182 012 | 6.2.1 Reference Point S-CSCF - ASF (ISC Reference Point) | The role of the ISC reference point is identical with respect to the PSTN/ISDN Emulation Subsystem and the IMS subsystem. The information provided over the ISC reference point shall enable an AS to distinguish between access lines receiving PES services via a VGW and access lines receiving PES services via an AGCF both... |
b708cbb24b9b1d04a3865f5f2ea8c6ab | 182 012 | 6.2.2 Reference Point UPSF - SIP AS or OSA SCS (Sh Reference Point) | The role of the Sh reference point with respect to the PSTN/ISDN Emulation Subsystem and the IMS subsystem is identical. |
b708cbb24b9b1d04a3865f5f2ea8c6ab | 182 012 | 6.2.3 Reference Point UPSF - IM SSF (Si Reference Point) | The role of the Si reference point with respect to the PSTN/ISDN Emulation Subsystem and the IMS subsystem is identical. |
b708cbb24b9b1d04a3865f5f2ea8c6ab | 182 012 | 6.2.4 Reference Point ASF- SLF (Dh Reference Point) | The role of the Dh reference point with respect to the PSTN/ISDN Emulation Subsystem and the IMS subsystem is identical. |
b708cbb24b9b1d04a3865f5f2ea8c6ab | 182 012 | 6.2.5 Reference Point ASF - UE and ASF-AGCF (Ut Reference Point) | The role of the Ut reference point with respect to the PSTN/ISDN Emulation Subsystem and the IMS subsystem is identical. The Ut reference point enables a A-VGW or R-VGW acting as a UE to manage information related to the services provided to the legacy equipment (e.g. ISDN terminal, ISDN PBX) it connects. The Ut refere... |
b708cbb24b9b1d04a3865f5f2ea8c6ab | 182 012 | 7 External interfaces | |
b708cbb24b9b1d04a3865f5f2ea8c6ab | 182 012 | 7.1 Interfaces with entities in the transfer plane | Transfer plane entities are defined in ES 282 001 [1]. |
b708cbb24b9b1d04a3865f5f2ea8c6ab | 182 012 | 7.1.1 Reference Point MGCF - T-MGF (Mn Reference Point) | The role of this reference point with respect to the PSTN/ISDN Emulation Subsystem and the IMS subsystem is identical. |
b708cbb24b9b1d04a3865f5f2ea8c6ab | 182 012 | 7.1.2 Reference Point MGCF - SGF (Ie Reference Point) | The Ie reference point enables the MGCF to exchange SS7 signalling information over IP with the SGF, according to the SIGTRAN architecture. |
b708cbb24b9b1d04a3865f5f2ea8c6ab | 182 012 | 7.1.3 Reference Point AS - SGF (P3 Reference Point) | The PES uses the SGF primarily in support of the MGCF signalling to the PSTN, as does the IMS subsystem. In addition, some Application Servers involved in supporting PES users may use the SGF to support non call related signalling interactions with the PSTN (e.g. TCAP-based messages for CCBS). |
b708cbb24b9b1d04a3865f5f2ea8c6ab | 182 012 | 7.1.4 Reference Point MRFC - MRFP (Mp Reference Point) | The role of this reference point with respect to the PSTN/ISDN Emulation Subsystem and the IMS subsystem is identical. |
b708cbb24b9b1d04a3865f5f2ea8c6ab | 182 012 | 7.2 Interface with the UE | Conventional SIP UEs do not exist in PES. In PES, the User Equipment comprises one or more analogue/ISDN terminals and gateway to which they are connected, via either the Z, U, S/T or T reference point. This gateway may be an Access or Residential Media Gateway or a SIP based Access or Residential Voice over IP Gateway... |
b708cbb24b9b1d04a3865f5f2ea8c6ab | 182 012 | 7.3 Interfaces with the user profile | The SLF and UPSF entities are defined in ES 282 001 [1]. The behaviour of the UPSF and SLF in relation to the PSTN/ISDN Emulation Subsystem is identical to its behaviour in relation to the IMS subsystem ES 282 007 [2]. ETSI ETSI TS 182 012 V2.1.4 (2008-03) 18 |
b708cbb24b9b1d04a3865f5f2ea8c6ab | 182 012 | 7.3.1 Interface with the SLF (Dx Reference Point) | The role of this reference point with respect to the PSTN/ISDN Emulation Subsystem and the IMS subsystem are identical. |
b708cbb24b9b1d04a3865f5f2ea8c6ab | 182 012 | 7.3.2 Interface with the UPSF (Cx Reference Point) | The role of this reference point with respect to the PSTN/ISDN Emulation Subsystem and the IMS subsystem are identical. |
b708cbb24b9b1d04a3865f5f2ea8c6ab | 182 012 | 7.4 Interfaces with Charging Functions | The following functional entities in the PES may act as charging trigger points: - AS; - BGCF; - (I-/P-/S-) CSCF; - MGCF; - MRFC; - AGCF. For off-line charging the Rf interface is used. For on-line charging the Ro interface is used. Details are described in ES 282 010 [7]. NOTE: The IBCF to which the PES is connected m... |
b708cbb24b9b1d04a3865f5f2ea8c6ab | 182 012 | 8 Interconnection with other networks | |
b708cbb24b9b1d04a3865f5f2ea8c6ab | 182 012 | 8.1 Interfaces with the PSTN/ISDN | Interconnection at the signalling level is provided via the SGF. Interconnection at the media level is provided by the trunk interfaces at the T-MGF. |
b708cbb24b9b1d04a3865f5f2ea8c6ab | 182 012 | 8.2 Interfaces with other external IP-based Subsystems | Interconnection with other IP-based subsystems (including other PSTN/ISDN Emulation subsystems) is typically performed via the IBCF at the signalling level. NOTE 1: Use of the IBCF is dependant on the implementations of the interconnected operators. In case of incoming sessions from other IP networks, and in case an IB... |
b708cbb24b9b1d04a3865f5f2ea8c6ab | 182 012 | 11 Mode of operation | |
b708cbb24b9b1d04a3865f5f2ea8c6ab | 182 012 | 11.1 General Principles | Emulating PSTN/ISDN services using the IMS-based PES architecture described in the present document assumes that the logic of the service to be emulated resides in one or more application servers rather than in the AGCF or in gateways. Emulating most PSTN supplementary services requires that at least one Application Se... |
b708cbb24b9b1d04a3865f5f2ea8c6ab | 182 012 | 11.2 Service Provisioning | |
b708cbb24b9b1d04a3865f5f2ea8c6ab | 182 012 | 11.2.1 Provisioning in the UPSF | The service profile of PES users is stored in the UPSF as for any other type of user. Appropriate filter criteria are set to ensure that PES-enabled Application Servers are involved in the processing of calls from/to PES-users. Setting these criteria does not require any specific service point trigger beyond those used... |
b708cbb24b9b1d04a3865f5f2ea8c6ab | 182 012 | 11.2.2 Provisioning in the AGCF | The following IMS parameters are assumed to be available, for every line, in a local data base of the AGCF: - private user identities; - public user identities; - home network domain names; - address of the AS to be used for service configuration management (for use over the Ut reference point); and NOTE: Some of the l... |
b708cbb24b9b1d04a3865f5f2ea8c6ab | 182 012 | 11.3 Registration | Registration and deregistration procedures are initiated by Voice over IP gateways (A-VGW and R-VGW) at the Gm reference point on behalf of each line or group of lines it serves. The rest of the procedures are identical in the PES and IMS subsystems. Registration and deregistration procedures are initiated by the AGCF ... |
b708cbb24b9b1d04a3865f5f2ea8c6ab | 182 012 | 11.4 Service code commands | Users of analog terminals usually manage supplementary services using service code commands using the syntax defined in ETS 300 738 [10], clause 6.1.1. The AGCF has the necessary service independent logic to determine whether a special dial tone needs to be delivered after the service prefix. In case dial tone needs to... |
b708cbb24b9b1d04a3865f5f2ea8c6ab | 182 012 | 12 AGCF behaviour | |
b708cbb24b9b1d04a3865f5f2ea8c6ab | 182 012 | 12.1 AGCF components | The AGCF can be decomposed into three logical components: • The Media Gateway Controller. • The Feature Manager. • The IMS Agent. Figure 8 provides an overview of the AGCF logical structure. ETSI ETSI TS 182 012 V2.1.4 (2008-03) 25 Session Processing Registration Processing Event Subscription /Notification CLF NASS AGC... |
b708cbb24b9b1d04a3865f5f2ea8c6ab | 182 012 | 12.2 Media Gateway Controller | The Media Gateway Controller component performs the following functions: • keep track of the media gateway state (e.g. registration/deregistration); • keep track of the line state (e.g. idle, active, parked, out of service, etc.); • control the connection configuration (media flows topology and directionality) in media... |
b708cbb24b9b1d04a3865f5f2ea8c6ab | 182 012 | 12.3 Feature Manager | The Feature Manager is the functional block in AGCF that provides the coordination between the IMS core and the Media Gateways. For that, it holds a call and connection model that associate lines to call states and IMS dialogs. Figure 9 shows a call and connection configuration where an analogue line is connected to tw... |
b708cbb24b9b1d04a3865f5f2ea8c6ab | 182 012 | 12.4 IMS Agent | The IMS agent encompasses the functionality of an IMS UE and P-CSCF. It communicates with other IMS entities using the SIP profile described in ES 283 003 [4]. The following functionality is implemented in the IMS agent: • Send/receive messages to/from the IMS entities. The received messages are sent to the Feature Man... |
b708cbb24b9b1d04a3865f5f2ea8c6ab | 182 012 | 13 Physical scenarios | Various physical scenarios can be derived from the functional architecture described in the previous clauses. How this functional architecture maps to physical devices and how many of the functional interfaces remain visible in a network implementation is outside the scope of standardization. Possible implementations r... |
60c334e5a4f7f64c2951525c2e46cc2e | 181 019 | 1 Scope | The present document specifies network requirements: • to support connection and interoperation of business communication capabilities (either hosted in NGCN or NGN) to the NGN; and • to support connection and interoperation of business communication capabilities to other business communication capabilities (either hos... |
60c334e5a4f7f64c2951525c2e46cc2e | 181 019 | 2 References | |
60c334e5a4f7f64c2951525c2e46cc2e | 181 019 | 2.1 Normative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the reference document (including any amendments) applies. Referenced documents which ar... |
60c334e5a4f7f64c2951525c2e46cc2e | 181 019 | 2.2 Informative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the reference document (including any amendments) applies. NOTE: While any hyperlinks in... |
60c334e5a4f7f64c2951525c2e46cc2e | 181 019 | 3 Definitions and abbreviations | |
60c334e5a4f7f64c2951525c2e46cc2e | 181 019 | 3.1 Definitions | For the purposes of the present document, the terms and definitions given in ETSI TS 122 519 [9] apply. |
60c334e5a4f7f64c2951525c2e46cc2e | 181 019 | 3.2 Abbreviations | For the purposes of the present document, the abbreviations given in ETSI TS 122 519 [9] apply. |
60c334e5a4f7f64c2951525c2e46cc2e | 181 019 | 4 Capabilities for the support of IP multimedia services | The provisions of the present document are contained in ETSI TS 122 519 [9]. |
60c334e5a4f7f64c2951525c2e46cc2e | 181 019 | 5 PSTN/ISDN emulation service | The provisions of the present document are contained in ETSI TS 122 519 [9]. |
60c334e5a4f7f64c2951525c2e46cc2e | 181 019 | 6 Codecs services | The provisions of the present document are contained in ETSI TS 122 519 [9]. |
60c334e5a4f7f64c2951525c2e46cc2e | 181 019 | 7 Network attachment requirements | The provisions of the present document are contained in ETSI TS 122 519 [9]. |
60c334e5a4f7f64c2951525c2e46cc2e | 181 019 | 8 CPE configuration | The provisions of the present document are contained in ETSI TS 122 519 [9]. |
60c334e5a4f7f64c2951525c2e46cc2e | 181 019 | 9 Network management | The provisions of the present document are contained in ETSI TS 122 519 [9]. |
60c334e5a4f7f64c2951525c2e46cc2e | 181 019 | 10 Control of processing overload | The provisions of the present document are contained in ETSI TS 122 519 [9]. ETSI ETSI TS 181 019 V3.0.0 (2015-10) 7 |
60c334e5a4f7f64c2951525c2e46cc2e | 181 019 | 11 IP addressing | The provisions of the present document are contained in ETSI TS 122 519 [9]. |
60c334e5a4f7f64c2951525c2e46cc2e | 181 019 | 12 NGN interconnection | The provisions of the present document are contained in ETSI TS 122 519 [9]. |
60c334e5a4f7f64c2951525c2e46cc2e | 181 019 | 13 IPTV | The provisions of the present document are contained in ETSI TS 122 519 [9]. |
60c334e5a4f7f64c2951525c2e46cc2e | 181 019 | 14 Transport stratum | The provisions of the present document are contained in ETSI TS 122 519 [9]. ETSI ETSI TS 181 019 V3.0.0 (2015-10) 8 Annex A (informative): Change history Date WG Doc. CR Rev CAT Title / Comment Current Version New Version 03-09-2015 NTECH(15)12 _005 001 D Alignment with 3GPP TS 22.519 2.0.0 3.0.0 ETSI ETSI TS 181 019 ... |
d65cbf1d92ccd5769ec9de06d2326895 | 182 028 | 1 Scope | The present document describes the IPTV functional architecture and functions of an NGN Integrated IPTV system by integrating of IPTV functions into the NGN architecture. For example, interactions and information flows between the IPTV functional entities and other functional entities will be specified. The specificati... |
d65cbf1d92ccd5769ec9de06d2326895 | 182 028 | 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... |
d65cbf1d92ccd5769ec9de06d2326895 | 182 028 | 2.1 Normative references | The following referenced documents are necessary for the application of the present document. [1] ETSI TS 181 016 (Release 3): "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Service Layer Requirements to integrate NGN services and IPTV". [2] ETSI TS 102 034: "Digital... |
d65cbf1d92ccd5769ec9de06d2326895 | 182 028 | 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] "An application-level QoS comparison of inter-destination synchronization schemes for continuous media multicasting", Toshiro Nunome; Shuji Tasaka, IE... |
d65cbf1d92ccd5769ec9de06d2326895 | 182 028 | 3 Definitions and abbreviations | |
d65cbf1d92ccd5769ec9de06d2326895 | 182 028 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: Inter-Destination Media Synchronization (IDMS): feature for exchanging arrival time and delay information, resulting in substantial synchronisation of the media outputs of two or more UEs, as presented to their users IPTV content ident... |
d65cbf1d92ccd5769ec9de06d2326895 | 182 028 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: ADM Ad Management Service ADS Ad Decision Service ADSS Ad Selection Service A-RACF Access Resource And Admission Control Function AS Application Server ASF Application Server Function BC Broadcast BCG Broadcast Content Guide BPG Broadcast Prog... |
d65cbf1d92ccd5769ec9de06d2326895 | 182 028 | 4 NGN IPTV subsystem | This clause outlines architectural approach adopted in the present document. The approach is then applied to introduce high level IPTV architecture and functional groups in NGN architecture. ETSI ETSI TS 182 028 V3.5.1 (2011-02) 11 |
d65cbf1d92ccd5769ec9de06d2326895 | 182 028 | 4.1 Concept and Architectural Approach | The present document focuses on defining flexible functional architecture, which can: • allow development of new IPTV subsystem in NGN; • integrate existing IPTV subsystem in NGN; • extend both to support other NGN services; as defined in the service level requirements [1]. The support for other NGN services has a wide... |
d65cbf1d92ccd5769ec9de06d2326895 | 182 028 | 4.2 High Level Architecture Overview | Figure 1 presents high-level NGN IPTV functional overview and location of IPTV capabilities in the TISPAN NGN. The high level overview illustrates principal functional groups for NGN IPTV services. The functional groups map to IPTV roles as defined in clause 4.3. The functional groups are used to derive more detailed f... |
d65cbf1d92ccd5769ec9de06d2326895 | 182 028 | 4.3 Functional groups | In the context of the present document functional groups are used to describe several functional entities grouped together according to some condition, e.g. location in the certain functional layer. ETSI ETSI TS 182 028 V3.5.1 (2011-02) 12 |
d65cbf1d92ccd5769ec9de06d2326895 | 182 028 | 4.3.1 Application Functions | Within the present document, the term "Application Functions" includes IPTV and NGN Application Functions. NGN Applications: provides the user with rich multimedia applications distributed across multiple NGN subsystems. For example, session follow up or messaging exchange between fixed and mobile terminals, presentati... |
d65cbf1d92ccd5769ec9de06d2326895 | 182 028 | 4.3.2 IPTV Service Control and Media Delivery Functions | Enables operation of IPTV services in NGN. The key functionality of this layer is to provide, but not limited to, media distribution, selection and allocation of media delivery units, IPTV session control and management, interactions with other NGN components for admission control and resource allocation, as well as co... |
d65cbf1d92ccd5769ec9de06d2326895 | 182 028 | 4.3.3 Transport Functions | Transport Control Functions: contains common NGN components RACS and NASS, provides policy control, resource reservation and admission control as well as IP address provisioning, network level user authentication and access network configuration as defined in TISPAN. Transport layer definition includes definition from ... |
d65cbf1d92ccd5769ec9de06d2326895 | 182 028 | 4.3.4 End User Functions | Customer transport: provides connection to one or multiple access networks and one or multiple home network segments. UE: provides user interactions and control over delivery of IPTV and other NGN services. IPTV terminal processes serviced multimedia and presents it in user acceptable format. User interactions may incl... |
d65cbf1d92ccd5769ec9de06d2326895 | 182 028 | 4.3.5 Management Functions | The IPTV Management Functions include: Service Fulfilment: the functions required to fulfil the IPTV service to the End-User. Service Assurance: the functions required to assure the IPTV service provided to the End-User. Service Billing: the functions required to ensure proper billing to the end user of delivered IPTV ... |
d65cbf1d92ccd5769ec9de06d2326895 | 182 028 | 4.3.6 Content Provider Functions | The functions provided by the entity that owns or is licensed to sell content or content assets. These are normally the sourcing of content, metadata and usage rights. |
d65cbf1d92ccd5769ec9de06d2326895 | 182 028 | 4.4 IPTV services | NGN integrated IPTV supports the following IPTV services [1]: • Broadcast TV (with or without trick modes). • Content on Demand (CoD). • Personal Video Recording (cPVR, nPVR). • Pay Per View (PPV). • Interactive TV (iTV). • near CoD (nCoD). • push CoD (pCoD). • User Generated Content (UGC). • Profiling and personalizat... |
d65cbf1d92ccd5769ec9de06d2326895 | 182 028 | 5.1 Functional entities | The functional groups presented on figure 1 contain the following functional entities used to deliver NGN IPTV services. |
d65cbf1d92ccd5769ec9de06d2326895 | 182 028 | 5.1.1 Core IPTV functions | NGN Application FE: application providing functionality across single or multiple subsystem, e.g. messaging exchange between fixed and mobile terminals, presentation of incoming calls and phone list management on TV, IPTV gaming applications based on user presence, NGN applications may include service mediation and coo... |
d65cbf1d92ccd5769ec9de06d2326895 | 182 028 | 5.1.2 Supporting IPTV functions | Media Preparation FE: a group of functions for manipulating, "preparing", content to enable content delivery to the UE. Examples of content preparation are encryption, encoding, keys and access rights generation. Such processes may be executed off-line, being considered as belonging to media content management, or on-l... |
d65cbf1d92ccd5769ec9de06d2326895 | 182 028 | 5.1.3 Transport functions | RACS: TISPAN resource admission and control subsystem. NASS: TISPAN network attachment subsystem. Transport Processing Functions: as defined in clause 4.3. ETSI ETSI TS 182 028 V3.5.1 (2011-02) 19 |
d65cbf1d92ccd5769ec9de06d2326895 | 182 028 | 5.1.4 Customer Transport functions | Delivery Network Gateway (DNG): device that is connected to one or multiple access networks and one or multiple home network segments. User equipment function: provides user interactions and control over delivery of IPTV and other NGN services. May include the following elementary functions: • Broadcast-Client Function... |
d65cbf1d92ccd5769ec9de06d2326895 | 182 028 | 5.2 Reference points | This clause describes reference points for NGN integrated IPTV architecture as shown on figure 2. Reference points between the core IPTV functional entities are summarized in table 1. Table 1: Reference points between core IPTV functional entities FE/ Reference point UE IPTV-C CFIA SD&S UPSF IUDF MCF MDF UE --- Ct2 Tr ... |
d65cbf1d92ccd5769ec9de06d2326895 | 182 028 | 5.2.1 Tr - IPTV transactional | Reference point between UE and Application Functions: • Used for UE Authentication and Authorization during initialization. NOTE: UE authentication may also be done directly via e2 reference point. • Used for user Authentication and Authorization for IPTV service during initialization. • Used to provide UE with one or ... |
d65cbf1d92ccd5769ec9de06d2326895 | 182 028 | 5.2.2 Ct2 - UE facing IPTV control | Optional reference point between UE and IPTV Control: • Acts as initial UE point of contact to request delivery of the selected IPTV service. • Returns nominated service (media) delivery control function. • Provides enough information for IPTV Control to check that UE has been authorized (by the Customer Facing IPTV Ap... |
d65cbf1d92ccd5769ec9de06d2326895 | 182 028 | 5.2.3 Sa - IPTV control and Media Control Function | Reference point between IPTV control and Media Control Function: • Used to interact with the Media Control Function (MCF) entity of the IPTV service selected by a user (e.g. provides information to the MCF that the user is authorized to access the selected IPTV service). • Used to notify the IPTV control with informati... |
d65cbf1d92ccd5769ec9de06d2326895 | 182 028 | 5.2.4 Ss - Service selection | Optional Ss - Service selection reference point between Customer facing IPTV applications and IPTV control: • Used to notify the IPTV control entity of the IPTV service selected by the user. • Used to notify the Customer Facing IPTV Application the UE initial entry point to the selected service (Media Control Function)... |
d65cbf1d92ccd5769ec9de06d2326895 | 182 028 | 5.2.5 Xc - UE and IPTV Media Control Function | Xc reference point (media control) - logical end-to-end reference point between the UE and the IPTV Media Control Function (MCF): • used to exchange media control messages for controlling of the delivery IPTV Media flows. NOTE: Transport related reference points are used to carry media control messages over underlying ... |
d65cbf1d92ccd5769ec9de06d2326895 | 182 028 | 5.2.7 Xd - UE and IPTV Media Delivery Function | Xd reference point (media delivery) - logical end-to-end reference point between UE and IPTV Media Delivery Function (MDF): • carries IPTV media data by appropriate means to the UE (delivers content streams). NOTE: Transport related reference points are used to carry media delivery data over underlying transport segmen... |
d65cbf1d92ccd5769ec9de06d2326895 | 182 028 | 5.2.8 e2 - NASS access | The e2 reference point is defined in ES 282 007 [8] and ES 282 004 [9]. |
d65cbf1d92ccd5769ec9de06d2326895 | 182 028 | 5.2.9 e4 - NASS and RACS | The e4 reference point is defined in ES 282 003 [10] and ES 282 004 [9]. ETSI ETSI TS 182 028 V3.5.1 (2011-02) 22 |
d65cbf1d92ccd5769ec9de06d2326895 | 182 028 | 5.2.10 Gq' - RACS | |
d65cbf1d92ccd5769ec9de06d2326895 | 182 028 | 5.2.11 Ud - access to IPTV user data | In the federated approach: • Used by IPTV application server functions, IPTV subscriber management to access subset of IPTV profiles, which are hosted in IUDF. In the consolidated approach: • User Data implements UPSF functionality. • Used to access user data located in User Data function. The Reference point is betwee... |
d65cbf1d92ccd5769ec9de06d2326895 | 182 028 | 5.2.12 Ug - access to NGN user data | In the federated approach: • Used by IPTV applications to provision and access federalized data from service level subsystems, e.g. IMS, NGN App UDF, mobile, other profile and non-NGN user data. • Used by converged applications (e.g. communicational features on TV, mobile session handover) to provision and access feder... |
d65cbf1d92ccd5769ec9de06d2326895 | 182 028 | 5.2.13 Ss' - access to SD&S data | Optional Ss' reference point between Customer facing IPTV applications and SD&S used to retrieve service and optionally service provider information from the SD&S server, e.g. EPG, content metadata, service information updates, service provider details. ETSI ETSI TS 182 028 V3.5.1 (2011-02) 23 |
d65cbf1d92ccd5769ec9de06d2326895 | 182 028 | 5.3 Generic IPTV Capabilities | This clause describes generic IPTV capabilities - capabilities provided by IPTV functional entities and exposed via interfaces on the high level architecture. The capabilities are used to deliver a variety of IPTV services as defined in the detailed procedures. IPTV Generic IPTV Capabilities: • service discovery and se... |
d65cbf1d92ccd5769ec9de06d2326895 | 182 028 | 5.3.1 Inter-destination media synchronization | Inter-destination media synchronization is an optional generic capability, aimed at servicing corresponding service level requirement as defined in clause A.9.6 of [1]. 5.3.1.1 Synchronization architecture The Media Synchronization Application Server (MSAS) and Synchronization Client (SC) are functions that provide int... |
d65cbf1d92ccd5769ec9de06d2326895 | 182 028 | 5.3.1.1.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... |
d65cbf1d92ccd5769ec9de06d2326895 | 182 028 | 5.3.1.1.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 IPTV Control. For synchronisation using a direct communication channel between multiple UEs, the MSAS is co-located with the SC. •... |
d65cbf1d92ccd5769ec9de06d2326895 | 182 028 | 5.3.1.1.3 Modification and re-origination of media streams | In addition to inter-destination media synchronization, additional synchronization 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... |
d65cbf1d92ccd5769ec9de06d2326895 | 182 028 | 5.3.1.2 Synchronization reference points | |
d65cbf1d92ccd5769ec9de06d2326895 | 182 028 | 5.3.1.2.1 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... |
d65cbf1d92ccd5769ec9de06d2326895 | 182 028 | 5.3.1.2.2 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... |
d65cbf1d92ccd5769ec9de06d2326895 | 182 028 | 5.4 Elementary functions | This clause describes generic IPTV capabilities - capabilities provided by IPTV functional entities and exposed via interfaces on the high level architecture. The capabilities are used to deliver a variety of IPTV services as defined in the detailed procedures. General elementary functions: 1) Network attachment 2) Reg... |
d65cbf1d92ccd5769ec9de06d2326895 | 182 028 | 6 Operational framework | |
d65cbf1d92ccd5769ec9de06d2326895 | 182 028 | 6.1 IPTV delivery modes | Integrated IPTV subsystem supports IPTV or NGN service using IP delivery modes: • Unicast: delivery mode where information packets are sent to a single destination. • Multicast: delivery mode of forwarding information packets to a group of destinations. • Combinations and interchanging of both inside a given service. I... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.