hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
83fb431f48ecf1b90224c947495fb807 | 183 004 | 3 Definitions and abbreviations | |
83fb431f48ecf1b90224c947495fb807 | 183 004 | 3.1 Definitions | For the purposes of the present document, the terms and definitions given in TS 124 504 [19] apply. |
83fb431f48ecf1b90224c947495fb807 | 183 004 | 3.2 Abbreviations | For the purposes of the present document, the abbreviations given in TS 124 504 [19] apply. |
83fb431f48ecf1b90224c947495fb807 | 183 004 | 4 Communications Diversion (CDIV) | The provisions of the present document are contained in TS 124 504 [19]. ETSI ETSI TS 183 004 V2.5.0 (2008-06) 7 Annex A (informative): Signalling Flows Information is contained in TS 124 504 [19]. ETSI ETSI TS 183 004 V2.5.0 (2008-06) 8 Annex B (informative): Example of filter criteria Information is contained in TS 124 504 [19]. ETSI ETSI TS 183 004 V2.5.0 (2008-06) 9 Annex C (informative): Coding considerations Information is contained in TS 124 504 [19]. ETSI ETSI TS 183 004 V2.5.0 (2008-06) 10 Annex D (informative): Bibliography Information is contained in TS 124 504 [19]. ETSI ETSI TS 183 004 V2.5.0 (2008-06) 11 Annex E (informative): Change history Information is contained in TS 124 504 [19]. ETSI ETSI TS 183 004 V2.5.0 (2008-06) 12 History Document history V2.4.0 January 2008 Publication V2.5.0 June 2008 Publication |
ab1c63542674cc1bca784b5679b06cff | 182 018 | 1 Scope | The present document describes the specific TISPAN requirements for controls to manage overload of processing resources in NGNs. In particular, it addresses overload control between nearest neighbours. |
ab1c63542674cc1bca784b5679b06cff | 182 018 | 2 References | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. • For a specific reference, subsequent revisions do not apply. • Non-specific reference may be made only to a complete document or a part thereof and only in the following cases: - if it is accepted that it will be possible to use all future changes of the referenced document for the purposes of the referring document; - for informative references. Referenced documents which are not found to be publicly available in the expected location might be found at http://docbox.etsi.org/Reference. For online referenced documents, information sufficient to identify and locate the source shall be provided. Preferably, the primary source of the referenced document should be cited, in order to ensure traceability. Furthermore, the reference should, as far as possible, remain valid for the expected life of the document. The reference shall include the method of access to the referenced document and the full network address, with the same punctuation and use of upper case and lower case letters. NOTE: While any hyperlinks included in this clause were valid at the time of publication ETSI cannot guarantee their long term validity. |
ab1c63542674cc1bca784b5679b06cff | 182 018 | 2.1 Normative references | The following referenced documents are indispensable for the application of the present document. For dated references, only the edition cited applies. For non-specific references, the latest edition of the referenced document (including any amendments) applies. [1] ITU-T recommendation E.412: "Network management controls". [2] ETSI TR 182 015: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Next Generation Networks; Architecture for Control of Processing Overload". [3] ETSI ES 282 003: " Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Resource and Admission Control Sub-system (RACS); Functional Architecture". [4] ETSI TS 181 005 V2.4.0 (2007-11): "Telecommunications and Internet Converged Services and Protocols for Advanced Networking (TISPAN); Service and Capability Requirements". |
ab1c63542674cc1bca784b5679b06cff | 182 018 | 3 Abbreviations | For the purposes of the present document, the following abbreviations apply: IMS IP Multimedia Subsystem ISDN Integrated Service Digital Network NGN Next Generation Network ETSI ETSI TS 182 018 V2.0.0 (2008-01) 6 PSTN Public Switched Telecommunication Network QoS Quality of Service RACS Resource Admission Subsystem SCF Session Control Function SIP Session Initiation Protocol SLA Service Level Agreement |
ab1c63542674cc1bca784b5679b06cff | 182 018 | 4 TISPAN NGN overload control requirements | |
ab1c63542674cc1bca784b5679b06cff | 182 018 | 4.1 High level overload control requirements | In TS 181 005 [4] we have the following requirements for overload control. The NGN shall have mechanisms available to control overload that: 1) automatically maximize effective throughput (i.e. admitted service requests/sec) at an overloaded resource; 2) achieve this throughout the duration of an overload event, and irrespective of the overloaded resource's capacity or of the number of sources of overload; 3) are configurable by the service provider so that, under processing overload, a high proportion of response times at overloaded resources are low enough so as not to cause customers to prematurely abandon service requests; 4) should be possible to be applied within a service provider's NGN, and between different service providers' NGNs; 5) should be possible to be applied within an NGN subsystem (e.g. IMS, PSTN/ISDN emulation) and between different NGN subsystems. NOTE: As a general rule, an NGN's call, session and command processing resources can experience prolonged processing overload under the appropriate circumstances (e.g. partial, or full, server failure, high rates of incoming service requests). Consequently, it needs to be equipped with some form of overload detection and control (including expansive controls such as load balancing and resource replication), in order to keep response times just low enough under such processing overload to preclude customers abandoning their service requests prematurely. Many pieces of equipment will have internal load control, which aims to meet the ideal behaviour described in ITU-T recommendation E.412 [1] and shown graphically in figure 1. The object of these internal controls is to bound the system response time by rejecting some of the workload (because rejecting workload requires less effort than accepting it). As the load increases requests are rejected, but because the rejected requests still consume some processing resource, the rate at which requests can be accepted falls. As a consequence, such internal load control can only protect the physical host against overload to a limited extent. Severe overloads will reduce the rate at which useful work can be done, and very severe overloads may cause the system to operate incorrectly or with unacceptably long response times. ETSI ETSI TS 182 018 V2.0.0 (2008-01) 7 Figure 1: hedoo Typical overload behaviour in a host with internal load control. By deploying a distributed overload control, in which systems suppress some service requests before they reach an overloaded neighbour, the overloaded system is protected from more extreme overloads thus enabling it to operate at near optimum load. For the fulfilment of these NGN requirements, the use of such nearest neighbour overload controls an essential component. The issues regarding overload controls for NGNs have been discussed at some length in [2] which provides some initial requirements for overload controls. These requirements are further elaborated in the present document and allocated into different categories. The requirements are also extended to cover the case where an overloaded target has a non-enumerable set of sources (e.g. SIP user agents overloading an SCF) The overload control requirements for systems loaded by a set of non-enumerable sources may be similar to those for a source loaded by a known, enumerable set of sources, but the approach may be very different. In the enumerable sources case, we may want to control the relative performance seen by each source, offer SLAs to particular sources and have a variety of fairness criteria to use. In the non-enumerable sources case, the issue is one of reducing the aggregate demand, and the fate of individual sources is less predictable. The definition of fairness would perhaps depend on ensuring equitable treatment over a series of overloads, rather than trying to meet fairness criteria between many sources over a single overload event. Those requirements that are not appropriate for non-enumerable sources are labelled as such. |
ab1c63542674cc1bca784b5679b06cff | 182 018 | 4.2 General requirements for Nearest Neighbour load control | These requirements are general, and any overload control should address these requirements. REQ 1 A control shall automatically reduce the load that is sent to an overloaded host. REQ 2 A control shall aim to maximize the number of fully processed service requests at an overloaded host, subject to meeting any QoS constraints for the application (e.g. response times). REQ 3 The overload control restriction shall apply only to defined events which will depend on the reference point that is being controlled. NOTE 1: This information may be thought of as within the domain of the applications on the NGN servers. It is the application that "knows" which requests to offer to the control for possible rejection, the control provides the infrastructure for the restriction to occur. REQ 4 A control shall be aware of differing importance levels of service requests, and be configurable to reject lower importance service requests in favour of service requests of higher importance level (for example to protect calls to emergency services). REQ 5 When several inter-acting controls are active at an overloaded host at the same time, they shall converge to an acceptable steady-state when the amount of work sent by each of the sources is constant. REQ 6 A control shall be configurable by the service provider to enable the enforcement of SLAs i.e. to divide the capacity of an overloaded resource between hosts from which requests are received (or groups of hosts) according to agreed policies. NOTE 2: It is inappropriate to attempt to manage SLAs for individual sources from a set of non-enumerable sources. ETSI ETSI TS 182 018 V2.0.0 (2008-01) 8 REQ 7 A control shall enforce fair allocation of overloaded processing resources between competing request sources (a request source in this context means the host from which the overloaded resource receives the request, not necessarily the originating host). NOTE 3: It is the SLA that defines the resources allocated to a request source by an overloaded resource. A fair allocation of resources implies that the resource consumed by every source is appropriate given the SLA allocated to that source. It does not necessarily require that the each request source obtains the same amount of processing resource. REQ 8 The behaviour of the control shall be fully-specified. REQ 9 A control shall allow manual configuration of the overload control's components via a management interface. REQ 10 A control shall operate (optionally) without manual configuration of the overload control parameters. REQ 11 A control shall output network management data on event occurrence (e.g. control activation/termination) and on demand from network management (e.g. counts of service requests admitted and rejected by the overload control). REQ 12 A control shall have adequate security from malicious actions. It shall not be possible for a host to instantiate a restriction able to reject service requests destined for a different host. NOTE 4: This implies that a mechanism for the verification of the identity of hosts originating restriction messages is required. REQ 13 A control shall be applicable within a network, and between networks. REQ 14 It should be possible to apply overload control between different NGN subsystems. REQ 15 A control shall react quickly to changes in the workload sent to the host it is protecting. REQ 16 A control shall be capable of dealing with work received from hosts which do not support it. Such hosts that are part of a finite set of sources shall not receive disproportionate benefit (i.e. requirements 6 and 7 shall still hold). |
ab1c63542674cc1bca784b5679b06cff | 182 018 | 4.3 Deployment specific requirements | The following requirements relate to different deployment options of the protected host and its traffic sources. Particular controls will need to address these deployments, so any overload control architecture must support or enable these requirements. REQ 17 Controls are required for scenarios where hosts receive service requests from an uncountable number of unknown sources as well as scenarios where hosts receive service requests from a known set of sources. A particular overload target may have a mixture of known, enumerable sources as well as an unknown, non-enumerable set of sources. In those cases, it shall be possible for the controls to inter-work, such that the SLAs for the enumerable sources are protected and the non-enumerable sources are managed on the basis of the aggregate workload from them all. REQ 18 A control shall inter-work with proxies, load balancing and load forking. |
ab1c63542674cc1bca784b5679b06cff | 182 018 | 4.4 Application specific requirements | The general requirements above relate to overload controls that act between hosts that are nearest neighbours, i.e. host load control. Application specific requirements arise from the need for some applications to perform functions closely related to host load control. Many of these requirements are not naturally part of host load control, as they are specific to a particular protocol/application, but they may be implemented by an application using the basic infrastructure used for host overload control. An important feature of these application level controls is that they have an application defined granularity, whereas host load control only distinguished between flows on the basis of the host from which the request is received. ETSI ETSI TS 182 018 V2.0.0 (2008-01) 9 REQ 19 A control shall enforce fair allocation of an overloaded processing resource between competing controlled application layer level streams of service requests, where such streams need not have a 1:1 correspondence to nearest neighbour hosts. REQ 20 A control shall be configurable by the service provider to enable the enforcement of SLAs for application level flows (to divide the capacity of an overloaded resource between competing application level requests flows according to agreed policies). This would allow a service provider to use the nearest neighbour load control infrastructure to protect well behaved flows when processing congestion is being caused by "badly behaved" flows, even though those flows are from the same nearest neighbour. REQ 21 A control shall facilitate an application to automatically limit ineffective service requests by detecting specific destination application layer names/addresses that are attracting a high reject rate and selectively controlling demand to them. ETSI ETSI TS 182 018 V2.0.0 (2008-01) 10 Annex A (informative): Comparison between RACS and nearest neighbour overload control The Resource Admission Control Sub-system (RACS) [3] is responsible for regulating access to NGN resources. Initially, one might think that nearest neighbour load control is simply a specific subset of the functionality of RACS as its role is to regulate access to computational resource. In that case, it might seem paradoxical that nearest neighbour load control is additional to the architecture while RACS is an integrated part of the architecture. The key to resolving this apparent paradox is to understand the fundamentally different objectives of the two. RACS is specifically designed to manage access to resources in the transport stratum that deliver service to end users, i.e. it regulates access to bandwidth to ensure the QoS targets of the user session are maintained. It is an integral part of the service delivery and is designed to allow end to end admission control to be achieved. The RACS infrastructure enables the resource for a particular end user session to be secured on an end to end basis before the session is admitted. Nearest neighbour load control, on the other hand, is not integrated into the service logic. There is no end to end co- ordination of the nearest neighbour load control admission decisions, they are all local (independent) decisions extending only as far as nearest neighbours - the admission decisions are not service based - nearest neighbour load control is not accepting or rejecting a user session rather it is accepting or rejecting the request processing on that particular node. To clearly demonstrate the difference, consider the fact that nearest neighbour load control may be deployed between servers that implement RACS. The differences between RACS and nearest neighbour load control are summarized in table 1. Table 1: A comparison between RACS and nearest neighbour load control RACS Nearest neighbour load control Request acceptance by RACS implies that resource is reserved for that request Acceptance of request by nearest neighbour load control does not imply a reservation of any processing resource Provides complex distributed functionality Only affects nearest neighbours Objective is service QoS control Objective is processing infrastructure protection May be a concrete instantiation - one can touch a physical system that only implements RACS functions Only exists as a component in physical systems that implement NGN functions ETSI ETSI TS 182 018 V2.0.0 (2008-01) 11 History Document history V2.0.0 January 2008 Publication |
b708cbb24b9b1d04a3865f5f2ea8c6ab | 182 012 | 1 Scope | The present document describes an IMS-based functional architecture for the PSTN/ISDN Emulation Subsystem (PES) of the ETSI TISPAN NGN overall architecture. The IMS-based PSTN/ISDN Emulation Subsystem described herein supports the emulation of PSTN services for analog terminals and ISDN services for ISDN terminals and PBXs. These may be connected directly to residential gateways or access gateways, or via V5 access networks. The present document provides a framework for an IMS-based functional architecture and is considered to be a preliminary version. In addition, in order to fulfil the requirements of different operators and national regulatory requirements, this architecture will need to be enhanced. See annex A for a list of potential open areas. |
b708cbb24b9b1d04a3865f5f2ea8c6ab | 182 012 | 2 References | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. • For a specific reference, subsequent revisions do not apply. • Non-specific reference may be made only to a complete document or a part thereof and only in the following cases: - if it is accepted that it will be possible to use all future changes of the referenced document for the purposes of the referring document; - for informative references. Referenced documents which are not found to be publicly available in the expected location might be found at http://docbox.etsi.org/Reference. For online referenced documents, information sufficient to identify and locate the source shall be provided. Preferably, the primary source of the referenced document should be cited, in order to ensure traceability. Furthermore, the reference should, as far as possible, remain valid for the expected life of the document. The reference shall include the method of access to the referenced document and the full network address, with the same punctuation and use of upper case and lower case letters. NOTE: While any hyperlinks included in this clause were valid at the time of publication ETSI cannot guarantee their long term validity. |
b708cbb24b9b1d04a3865f5f2ea8c6ab | 182 012 | 2.1 Normative references | The following referenced documents are indispensable for the application of the present document. For dated references, only the edition cited applies. For non-specific references, the latest edition of the referenced document (including any amendments) applies. [1] ETSI ES 282 001: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); NGN Functional Architecture Release 1". [2] ETSI ES 282 007: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); IP Multimedia Subsystem (IMS) Functional architecture". [3] ETSI TS 182 006: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); IP Multimedia Subsystem (IMS); Stage 2 description". [4] ETSI ES 283 003: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); IP Multimedia Call Control Protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP) Stage 3 [3GPP TS 24.229 [Release 7], modified]". ETSI ETSI TS 182 012 V2.1.4 (2008-03) 7 [5] ETSI TS 183 043: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); IMS-based PSTN/ISDN Emulation; Stage 3 specification". [6] ETSI TS 183 021: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); NGN Release 1; Endorsement of 3GPP TS 29.162 Interworking between IM CN Sub-system and IP networks". [7] ETSI ES 282 010: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Charging management Endorsement of 3GPP TS 32.240 Release 7, 3GPP TS 32.260 Release 7, 3GPP TS 32.297 Release 7, 3GPP TS 32.298 Release 7 and 3GPP TS 32.299 Release 7, modified". [8] ETSI ES 201 915-1: "Open Service Access (OSA); Application Programming Interface (API); Part 1: Overview (Parlay 3)". [9] IETF RFC 3136: "The SPIRITS architecture". [10] ETSI ETS 300 738: "Human Factors (HF); Minimum Man-Machine Interface (MMI) to public network based supplementary services". [11] ITU-T Recommendation H.248: "Gateway control protocol". [12] ETSI EN 300 659 (all parts): "Access and Terminals (AT); Analogue access to the Public Switched Telephone Network (PSTN); Subscriber line protocol over the local loop for display (and related) services". [13] ETSI ETR 150: "V5 interface; Public Switched Telephone Network (PSTN) mappings". |
b708cbb24b9b1d04a3865f5f2ea8c6ab | 182 012 | 2.2 Informative references | Not Applicable. |
b708cbb24b9b1d04a3865f5f2ea8c6ab | 182 012 | 3 Definitions and abbreviations | |
b708cbb24b9b1d04a3865f5f2ea8c6ab | 182 012 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: Access Gateway (AG): gateway device that interworks a significant number of analogue lines/ISDN accesses (directly or via an V5 Access Network) to a packet network and is located at the operator's premises NOTE: An AG can take the form of a Media Gateway (A-MGW) or a Voice over IP Gateway (A-VGW). Media Gateway (MGW): gateway device acting at the media/transport plane, providing the functions of an MGF as defined in ES 282 001 [1] NOTE 1: A MGW may additionally relay signalling traffic, in which case it also provides the functions of an SGF as defined in ES 282 001 [1]. NOTE 2: In the present document, Media Gateway refers both to Access Gateways and to Residential Gateways, to form a A-MGW, or a R-MGW, respectively. Media Gateway Controller (MGC): See ITU-T Recommendation H.248 [11]. Residential Gateway (RG): gateway device that interworks a small number of analogue lines/ISDN accesses NOTE: A residential gateway typically contains one or two analogue lines/ISDN accesses and is located at the customer premises. A RG can take the form of a Media Gateway (R-MGW) or a Voice over IP Gateway (R-VGW). ETSI ETSI TS 182 012 V2.1.4 (2008-03) 8 Voice over IP Gateway (VGW): SIP-based gateway device that connects legacy equipment to the NGN NOTE 1: A Voice over IP Gateways (VGW) plays the role of an IMS UE with regards to the P-CSCF. NOTE 2: A Voice over IP Gateway can be classified as a AG or RG, to form a A-VGW, or a R-VGW, respectively. |
b708cbb24b9b1d04a3865f5f2ea8c6ab | 182 012 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: AF Application Function AG Access Gateway AGCF Access Gateway Control Function A-MGF Access Media Gateway Function A-MGW Access Media GateWay AN Access Node AS Application Server ASF Application Server Function ATA Analogue Terminal Adaptor A-VGW Access Voice over IP GateWay BCSM Basic Call State Model BGCF Breakout Gateway Control Function BGF Border Gateway Function CCBS Call Completion on Busy Subscriber CSCF Call Session Control Function DDI Direct Dialling In DNS Domain Name Server DSS1 Digital Subscriber Signalling System No.1 GW GateWay HSS Home Subscriber Server IBCF Interconnection Border Control Function I-CSCF Interrogating-Call Session Control Function IM IP Multimedia IMS IP Multimedia Subsystem IM-SSF IP Multimedia-Service Switching Function ISDN Integrated Services Digital Network ISUP ISDN User Part IWF InterWorking Function MG Media Gateway MGC Media Gateway Controller MGCF Media Gateway Control Function MGF Media Gateway Function MGW Media Gateway MRFC Multimedia Resource Function Controller MRFP Multimedia Resource Function Processor NAPT Network Address Port Translation NASS Network Attachment SubSystem NGN Next Generation Network OSA Open Service Access PBX Private Branch Exchange P-CSCF Proxy-Call Session Control Function PES PSTN/ISDN Emulation Subsystem PSTN Public Switched Telephone Network RACS Resource and Admission Control Subsystem RG Residential Gateway R-MGF Residential-MGF R-MGW Residential Media GateWay R-VGW Residential Voice over IP GateWay SCIM Service Capability Interaction Manager SCS Service Capability Server S-CSCF Serving-Call Session Control Function ETSI ETSI TS 182 012 V2.1.4 (2008-03) 9 SIGTRAN SIGnalling TRANsport SIP Session Initiation Protocol SLF Subscription Locator Function SS7 Signalling System n°7 SSF Service Switching Function TDM Time Division Multiplexing TGW Trunking Gateway T-MGF Trunking Media Gateway Function UE User Equipment UPSF User Profile Server Function VGW Voice over IP GateWay VoIP Voice over IP |
b708cbb24b9b1d04a3865f5f2ea8c6ab | 182 012 | 4 Overview | |
b708cbb24b9b1d04a3865f5f2ea8c6ab | 182 012 | 4.1 PSTN/ISDN Emulation subsystem environment | Figure 1 shows the PSTN/ISDN Emulation Subsystem and its relationships with other TISPAN NGN subsystem. Applications/ User Profiles Resource and Admission Control Subsystem Residential and Access MGW TISPAN PSTN/ISDN Emulation Subsystem Core IMS PSTN/ISDN (TDM based) Network Attachment Subsystem Charging functions Network Management Functions Other MM Subsystems Residential and Access VGW Figure 1: PSTN/ISDN Emulation Subsystem and its environment |
b708cbb24b9b1d04a3865f5f2ea8c6ab | 182 012 | 4.2 Signalling configurations | Figure 2 illustrates the signalling configurations supported by the PSTN/ISDN Emulation Subsystem (PES) described in the present document. PSTN/ISDN Emulation Subsystem ISDN/PSTN ISDN/PSTN Trunk Trunk T-MGF T-MGF V5.x AN analog access ISDN access V5.x AN analog access ISDN access MGW/ VGW MGW/ VGW Figure 2: Signalling Configurations ETSI ETSI TS 182 012 V2.1.4 (2008-03) 10 Legacy terminals, i.e. analog phones and ISDN phones may be connected to R-VGW, R-MGW, A-VGW and A-MGW, using the interfaces based on the Z, S/T and U reference point, respectively. ISDN PBXs may be connected to an A-VGW or A-MGW using the interfaces based on the T reference point. When connected to an AG (A-VGW or A-MGW) a legacy terminal or ISDN PBX may be connected directly to the AG or indirectly via a V5.xAccess Node. The R-VGW and A-VGW are connected to the IMS PES via the Gm reference point. The R-MGW and A-MGW are connected to the IMS PES via the P1 reference point. PSTN/ISDN islands may also be connected via trunking media gateway function (T-MGF), controlled via the Mn reference point. Transit network functionality is supported as provided by the IMS ES 282 007 [2]. |
b708cbb24b9b1d04a3865f5f2ea8c6ab | 182 012 | 4.3 Constraints on services | The range of services that can be emulated in TISPAN NGN Release 1 is constrained by the functional architecture and the IMS SIP profile defined in ES 283 003 [4] on the Mw/Mx and ISC reference points, and of the Gm reference points in case of VGW. |
b708cbb24b9b1d04a3865f5f2ea8c6ab | 182 012 | 4.4 Overlap signalling | Overlap sending is a mechanism that is used for dialling over analogue and ISDN accesses, and is inbuilt in the inter- exchange signalling systems of the PSTN/ISDN networks. As such, it is a mechanism that the IMS-based PSTN/ISDN emulation subsystem architecture shall support, in a similar manner as for the PSTN. To support overlap signalling the PES shall support the following functionality: • at the originating side, the VGW and the AGCF shall support the ability to collect digits sent by the user to the extent of its knowledge of the dialling plan in use. As a result, the completeness of the number may be unknown, and the VGW and AGCF may, dependent on operator policy, use overlap sending; • Networks supporting overlap sending should provide a B2BUA function that has the ability to collect digits, before routeing to another network that does not support overlap sending, such that the address information is provided in a single message; • at the terminating side, e.g. when connected to a legacy PBX, the VGW and the AGCF should support based on operator policy the ability to transfer digits to the user using overlap sending; • at the terminating side, e.g. when connected to a legacy PBX, an AS may support the ability to transfer digits to the user dependent on operator policy, using overlap sending; • In case of an incoming call (from another network), the I-CSCF or TrRF or O-MGCF, possibly in combination with HSS/DNS/ENUM, will forward the call only when a sufficient number of digits have been received: - for terminating cases to access the service profile assigned to a user. Only for cases additional digits not relevant for the IMS service profile lookup are received as overlap signalling, e.g. for DDI towards a PBX, based on network options this additional overlap signalling should be sent towards the terminating user; - for transit cases when the number received points towards another network to select and forward the call to an appropriate network egress point (e.g. IBCF or I-MGCF). the solution shall interoperate with IMS networks not supporting overlap signalling without requiring any changes in those networks. NOTE 1: A terminating IMS network not supporting overlap signalling will perform a database lookup to assign a S-CSCF for an incoming call and will return a 404 error response to an INVITE with an incomplete number. • in interconnection scenarios, as a network option, it shall be possible to support overlap signalling. NOTE 2: In the PES network the service level provided to the user should not be dependent on using overlap or en-bloc sending. ETSI ETSI TS 182 012 V2.1.4 (2008-03) 11 |
b708cbb24b9b1d04a3865f5f2ea8c6ab | 182 012 | 5 Functional architecture | |
b708cbb24b9b1d04a3865f5f2ea8c6ab | 182 012 | 5.1 Overview | The functional architecture described in the preent document is one of the possible architectural options for structuring the TISPAN PSTN/ISDN Emulation Subsystem (PES) identified in the TISPAN NGN overall architecture ES 282 001 [1]. This functional architecture uses the same architecture as the IMS defined in ES 282 007 [2] with extensions defined in the present document. Figure 3 provides an overview of the functional entities that make up this architecture and shows their relationships to the other components of the NGN architecture. Other IP Net- works IP Transport (Access and Core) T - MGF I - BGF UPSF I/S - CSCF BGCF SLF Charging Functions IWF PES Mw Mx Mr Mg Mj Mi Mp Mn Gm Gq ' ISC Cx Dx Dh Sh Ic Rf /Ro Rf /Ro Ib Iw Gq ' PSTN/ ISDN SGF MRFC MGCF MRFP Resource and Admission Control Subsystem Ie Mw IBCF Mx Mk Other types of service logic PSTN/ISDN Emulation logic Application Rf /Ro AGCF Gq ' P1 Mw P3 Ut Ut Network Attachment Subsyste e2 e2 Mx P - CSCF Mx Mx analog acc. ISDN acc. A/R- MGW A/R- VGW Figure 3: PSTN/ISDN Emulation Subsystem - Functional Architecture Most of the functional entities inside the PSTN/ISDN Emulation Subsystem are identical or derived from their IMS counterpart 282 007 [2], with the noticeable exception of an Access Gateway Control Function (AGCF) that has the responsibility of controlling residential and access media gateways. For the other functional entities, any differences are noted in the following clause. A physical entity can house functional entities supporting both PES and IMS, that can be supported by a common addressing scheme. |
b708cbb24b9b1d04a3865f5f2ea8c6ab | 182 012 | 5.2 Overview of Functional entities of the PES | |
b708cbb24b9b1d04a3865f5f2ea8c6ab | 182 012 | 5.2.1 Access Gateway Control Function (AGCF) | This functional entity is the first point of contact for Residential Media Gateway (R-MGW) and Access Media Gateways (A-MGW). This entity is specific to the PSTN/ISDN emulation subsystem. It performs the following functions: • Act as an MGC for controlling media gateways functions (R-MGF and A-MGF) located in residential and access gateways. • Interact with the resource and admission control subsystem (RACS). • Interact with the network attachment subsystem (NASS) to retrieve line profile information. ETSI ETSI TS 182 012 V2.1.4 (2008-03) 12 • Perform signalling interworking between SIP at the Mw/Mx reference point and analog/ISDN signalling. The analog and ISDN signalling information is conveyed over the P1 reference point. • Perform signalling interworking between XCAP at the Ut reference point and legacy subscriber line (e.g. ISDN) signalling via the P1 reference point. NOTE 1: The main use-case for the interworking between XCAP and legacy subscriber line signalling is supplementary service control (registration, activation, deactivation, interrogation). • Act as a SIP User Agent with regard to IMS SIP functional entities. • Perform functions normally assigned to a P-CSCF on behalf of legacy terminals connected behind the media gateways (such as managing SIP registration procedures, generating asserted identities, and creating charging identifiers). The AGCF appears as a P-CSCF to the other CSCFs. The SIP signalling capabilities available to the AGCF are limited to those available at the Mw/Mx reference. Moreover, the AGCF shall provide basic feature logic for: • delivering the appropriate dialtone pattern; • processing mid-call events, as described in clause 12. NOTE 2: A solution based on AGCF will provide similar response time (e.g. dial tone, ring tone) as today in the PSTN networks. In case of AGCF failure, stable calls shall be preserved. Depending on implementation options, the AGCF may or may not be capable of implementing service-independent feature logic for dealing with register recall events, when it does, it can make certain decisions such as whether or not to apply dial tone on register recall, whereas in implementations where the AGCF does not implement feature logic, such decisions must be left for the AS to make. Further details on the AGCF structure and behaviour are provided in clause 12. NOTE 3: If desired, a network operator could choose to deploy an MGC that controls a set of media gateways following most of the AGCF call processing rules defined in the present document, and supports the Gm interface into an IMS or PES network via a P-CSCF, but this entity would fill the role of "Gateway (VGW)" depicted in figure 3 and would not be part of the trusted IMS core. AGCF/VGW shall support a generic solution for calls without dialling information, e.g. fixed destination call or deferred fixed destination call. |
b708cbb24b9b1d04a3865f5f2ea8c6ab | 182 012 | 5.2.2 Multimedia Resource Function Controller (MRFC) | The behaviour of the MRFC is identical in the PSTN/ISDN Emulation Subsystem and in the IMS subsystem ES 282 007 [2]. |
b708cbb24b9b1d04a3865f5f2ea8c6ab | 182 012 | 5.2.3 Media Gateway Control Function (MGCF) | The role of the MGCF is identical in the PSTN/ISDN Emulation Subsystem and in the IMS subsystem ES 282 007 [2]. Signalling procedures for interworking with ISUP signalling are slightly different due to the presence of encapsulated ISUP information inside the PES and the need to ensure full ISDN transparency in case of ISDN calls transiting through the PES. |
b708cbb24b9b1d04a3865f5f2ea8c6ab | 182 012 | 5.2.4 Proxy Call Session Control Function (P-CSCF) | The behaviour of the P-CSCF is identical in the PSTN/ISDN Emulation Subsystem and in the IMS subsystem ES 282 007 [2]. However, the P-CSCF is not used in configurations where an AGCF is required to control residential or access media gateways. In such cases, all functions normally provided by the P-CSCF will be provided directly by the AGCF. ETSI ETSI TS 182 012 V2.1.4 (2008-03) 13 |
b708cbb24b9b1d04a3865f5f2ea8c6ab | 182 012 | 5.2.5 Service Call Session Control Function (S-CSCF) | The behaviour of the S-CSCF is identical in the PSTN/ISDN Emulation Subsystem and in the IMS subsystem ES 282 007 [2]. |
b708cbb24b9b1d04a3865f5f2ea8c6ab | 182 012 | 5.2.6 Interrogating Call Session Control Function (I-CSCF) | The behaviour of the I-CSCF is identical in the PSTN/ISDN Emulation Subsystem and in the IMS subsystem ES 282 007 [2]. |
b708cbb24b9b1d04a3865f5f2ea8c6ab | 182 012 | 5.2.7 Breakout Gateway Control Function (BGCF) | The behaviour of the BGCF is identical in the PSTN/ISDN Emulation Subsystem and in the IMS subsystem ES 282 007 [2]. |
b708cbb24b9b1d04a3865f5f2ea8c6ab | 182 012 | 5.3 Internal Reference Points | |
b708cbb24b9b1d04a3865f5f2ea8c6ab | 182 012 | 5.3.1 Reference Point MGCF - CSCF (Mg Reference Point) | The Mg reference point allows the MGCF to forward incoming session signalling (from the PSTN) to the CSCF for the purpose of interworking with PSTN networks. The protocol used for the Mg reference point is SIP. SIP messages may contain encapsulated ISUP information. The role of this reference point is identical in the PES and IMS subsystems. Details are described in TS 182 006 [3]. |
b708cbb24b9b1d04a3865f5f2ea8c6ab | 182 012 | 5.3.2 Reference Point CSCF - MRFC (Mr Reference Point) | The Mr reference point allows the S-CSCF to relay signalling messages between an application server function and an MRFC. The protocol used for the Mr reference point is SIP. The role of this reference point is identical in the PES and IMS subsystems ES 282 007 [2]. Details are described in TS 182 006 [3]. 5.3.3 Reference Point CSCF - CSCF and AGCF - CSCF (Mw Reference Point) The Mw reference point allows the communication and forwarding of signalling messaging between CSCFs and between an AGCF and a CSCF, e.g. during registration and session control. The protocol used for the Mw reference point is SIP. SIP messages exchanged over the Mw reference point may contain encapsulated ISUP information, except between the AGCF and a CSCF. The role of this reference point is identical in the PES and IMS subsystems ES 282 007 [2]. Details are described in TS 182 006 [3]. |
b708cbb24b9b1d04a3865f5f2ea8c6ab | 182 012 | 5.3.4 Reference Point CSCF - BGCF (Mi reference point) | This reference point allows the Serving CSCF to forward the session signalling to the Breakout Gateway Control Function for the purpose of interworking to the PSTN networks. The protocol used for the Mi reference point is SIP. SIP messages exchanged over the Mi reference point may contain encapsulated ISUP information. ETSI ETSI TS 182 012 V2.1.4 (2008-03) 14 The role of this reference point is identical in the PES and IMS subsystems ES 282 007 [2]. Details are described in TS 182 006 [3]. |
b708cbb24b9b1d04a3865f5f2ea8c6ab | 182 012 | 5.3.5 Reference Point BGCF - MGCF (Mj reference point) | This reference point allows the Breakout Gateway Control Function to forward the session signalling to the Media Gateway Control Function (and vice-versa) for the purpose of interworking to the PSTN networks. This reference point may also be used by an MGCF to forward session signalling to the BGCF in case of transit scenarios, if the MGCF supports transit routeing. The protocol for the Mj reference point is SIP, possibly with encapsulated ISUP information. The role of this reference point is identical in the PES and IMS subsystems ES 282 007 [2]. Details are described in TS 182 006 [3]. |
b708cbb24b9b1d04a3865f5f2ea8c6ab | 182 012 | 5.3.6 Reference Point BGCF - BGCF (Mk reference point) | This reference point allows the Breakout Gateway Control Function to forward the session signalling to another Breakout Gateway Control Function. The Mk reference point is SIP, possibly with encapsulated ISUP information. The role of this reference point is identical in the PES and IMS subsystems. Details are described in TS 182 006 [3]. 5.3.7 Reference Point AGCF, CSCF or BGCF - IBCF (Mx Reference Point) The Mx reference point allows the communication and forwarding of signalling messages between an AGCF, CSCF or a BGCF and an IBCF. NOTE: The protocol used for the Mx reference point is SIP. The role of this reference point is identical in the PES and IMS subsystems. SIP messages exchanged over the Mx reference point may contain encapsulated ISUP information, except between the AGCF and the IBCF. Details are described in TS 182 006 [3]. |
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 understand and terminate the ISUP protocol encapsulated in SIP. Three types of Application Server Functions (ASF) can be accessed by the IMS-based PES, through the ISC or Ma reference point (see figure 4). • SIP Application Servers (SIP AS). • The IM-SSF Application Server. • The OSA SCS Application Server. ETSI ETSI TS 182 012 V2.1.4 (2008-03) 15 A SIP Application Server may contain "Service Capability Interaction Manager" (SCIM) functionality and other application servers. The SCIM functionality is an application which performs the role of interaction management. The internal structure of the application server is outside the standards. The purpose of the IM SSF is to enable access to IN service logic programs hosted in legacy SCPs. The IM-SSF functionality encompasses the emulation of the IN Call Model (BCSM) on top of SIP signalling, IN triggering and feature management mechanisms, emulation of the IN Service Switching Finite State Machine and interworking with INAP. NOTE 1: The role of the IM-SSF is identical in the PSTN/ISDN Emulation Subsystem and in the IMS subsystem ES 282 007 [2]. Basic behaviour is also identical. However, in the PES case, mapping procedures may take into account ISUP information encapsulated in SIP messages. NOTE 2: The IM SSF is intended to enable access from the PES to IN service logic programs hosted in legacy SCPs. Access to PES services (i.e. hosted in SIP-based Application Servers) from legacy SSPs in the PSTN/ISDN is outside the scope of the present document. Appropriate gateway functions (e.g. SPIRITS gateway as defined in RFC 3136 [9]) have to be implemented in the PSTN/ISDN network for supporting such scenarios. The purpose of the OSA Service Capability Server is to provide access to OSA applications, according to the OSA/Parlay framework ES 201 915-1 [8]. Further details can be found in TS 182 006 [3]. UPSF PSTN/ISDN Emulation Subsystem Transport Layer S-CSCF OSA SCS SIP-AS IN SCF OSA AS Sh Sh Si Cx ISC/Ma OSA API INAP Dx IM-SSF SLF Dh Figure 4: Value Added Services architecture The Service-CSCF to AS interface is used to forward SIP requests, based on filter criteria associated with the originating or destination user. The Interrogating-CSCF to AS interface is used to forward SIP requests destined to a Public Service Identity hosted by the AS directly to that AS. The procedures between AGCF and AS (using reference points Mw, Mx, Ic and ISC) shall be standard and open to allow for interoperability of equipment from different vendors which may be located in different operators' networks. ETSI ETSI TS 182 012 V2.1.4 (2008-03) 16 |
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 of which use the same public user identity. |
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 reference point enables the AGCF to manage information related to the services provided to the legacy equipment (e.g. ISDN terminal, ISDN PABX) connected to the Residential or Access Media Gateways it controls. The Ut reference point applies to SIP Application Servers only. Details are described in ES 282 007 [2]. 6.2.6 Reference Point I-CSCF - AS (Ma Reference Point) The role of the Ma reference point with respect to the PSTN/ISDN Emulation Subsystem and the IMS subsystem is identical. This interface between Interrogating-CSCF and the Application Servers (i.e. SIP Application Server, OSA Service Capability Server, or CAMEL IM-SSF) is used to forward SIP requests destined to a Public Service Identity hosted by an Application Server directly to the Application Server. Details are described in TS 182 006 [3]. ETSI ETSI TS 182 012 V2.1.4 (2008-03) 17 |
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. When the user equipment is connected to an Access Gateway, this may be via existing V5.x Access Nodes. A Voice over IP Gateways (A-VGW and R-VGW) plays the role of a UE with regards to the P-CSCF-. VoIP gateways (A/R-VGW) interact with IMS PES via the Gm and Ut reference points. The protocol used for the Gm reference point is SIP. Details are described in ES 282 007 [2]. The role of these reference point (Gm and Ut) are identical in the PES and IMS subsystems. Media Gateways connecting legacy equipment (analog/ISDN terminals and ISDN PBXs) interact with the PES via the P1 reference point. The protocols used for the P1 reference point are H.248. When connecting ISDN terminals/PBXs to the MGW (directly or via a V5 AN), the P1 reference point also comprises back hauled DSS1. In case the access is connected via V5 Access Nodes, the analog signalling information is conveyed over the P1 reference point using back hauled V5 signalling or H.248. |
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 may also act as a charging trigger point. |
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 IBCF is used, the IBCF determines the next hop in IP routing depending on received signalling information, based on configuration data and/or data base look up. The next hop may be an I-CSCF, a BGCF or another IBCF. Interconnection between PSTN/ISDN emulation subsystems occurs either between two home domains (e.g. session originating and terminating domain) or between a visited domain and a home domain (i.e. support of roaming capabilities, see note 2). ETSI ETSI TS 182 012 V2.1.4 (2008-03) 19 NOTE 2: Roaming scenarios are inherently supported in the IMS-based PES just as the IMS architecture enables UEs in a visited network to access their home IMS via a P-CSCF in the visited IMS. When serving lines via an AGCF, due to the static characteristics of access lines connected to an AGCF, the roaming scenario supported by the IMS-based PES will typically be permanent (i.e. non-nomadic), unless rewiring of the access line to a different A-MGW is performed; typically known as wholesale scenario, this form of permanent roaming is achieved by means of an access line being physically connected to a A-MGW and an AGCF in one operator's domain and receiving its home PES services from another operator's IMS (as shown in figures 5 and 6). The above also implies that different access lines connected to the same AGCF in a visited network can receive PES services from different operators' home IMS-based PES. As in any roaming agreement, certain information will have to be exchanged off-line between the visited and home operators; for the particular scenario where the AGCF resides in a different operator's network than the rest of the IMS, this information includes the configuration of the lines being served (see clause 11.2.2) as well as an indication of the respective capabilities of the AGCF and the PES AS for them to interoperate (e.g. whether or not the AGCF supports service-independent feature logic for dealing with mid-call events). The format or the means to exchange such information is outside the scope of the present document. Based on signalling information received from the PES and local policy rules, and if an IBCF is used, the IBCF decides on a per session basis whether the RACS should be involved in the interconnection. NOTE 3: Depending on the operator policies, the decision as to whether or not media level interconnection is required (i.e. an I-BGF is inserted in the media path) for a particular session may be taken by the RACS, based on the "resource reservation service class" information that may be received from the IBCF. The RACS also choose the appropriate interconnect link for media traffic based on the information received from the IBCF, if an IBCF exists and is used. Figure 5 illustrates the case where no I-BGF is inserted. Figure 6 illustrates the case where an I-BGF is inserted by the visited network. All other interconnect scenarios identified in ES 282 007 [2] annex B are also applicable to the PES. S-CSCF AGCF IBCF IBCF Mx Mx Ic PES (visited) PES (home) To/from terminating home network Originating Visited Network Originating Home Network Access Transport Network RACS Core Transport Networks C-BGF Media Flows Figure 5: PES interconnect scenario without I-BGF ETSI ETSI TS 182 012 V2.1.4 (2008-03) 20 S-CSCF AGCF IBCF IBCF Mx Mx Ic PES (visited) PES (home) To/from terminating home network Originating Visited Network Originating Home Network Access Transport Network RACS Core Transport Networks C-BGF Media Flows I-BGF RACS Figure 6: PES interconnect scenario with I-BGF NOTE 4: As a network operator's option, an I-CSCF with encryption-based topology hiding capabilities (THIG) may also be inserted in the PES before the IBCF. This is not represented on figures 5 and 6. 9 Interfaces with the Network Attachment Subsystem (NASS) The e2 reference point supports information transfer between the P-CSCF or the AGCF and the Network Attachment Subsystem. The role of this reference point with respect to the PSTN/ISDN Emulation Subsystem and the IMS subsystem is identical. NOTE: Interaction with the NASS is not be required in case the AGCF controls access gateways only. 10 Interface with the Resource and Admission Control Subsystem (RACS) The Gq' reference point enables the P-CSCF or the AGCF to interact with the resource control subsystem for the following purposes: - authorization of QoS resources; - resource reservation; - gate control (including NAPT binding information relay). With regard to the RACS architecture; the P-CSCF and the AGCF play the role of an Application Function (AF). The role of this reference point with respect to the PSTN/ISDN Emulation Subsystem and the IMS subsystem is identical. NOTE: Interaction with the NASS may not be required in case the AGCF controls access gateways only and dedicated transport resources are used to support PES traffic. ETSI ETSI TS 182 012 V2.1.4 (2008-03) 21 In case of network interconnection, interactions with the resource control subsystem may also take place at the edge of the PES, at the IBCF level for the following purposes: - gate control (including NAPT binding information relay). With regard to the RACS architecture; the IBCF plays the role of an Application Function (AF). Details are described in TS 183 021 [6]. |
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 Server be inserted in the SIP signalling path. For certain call configurations, this requires that encapsulated ISUP information be sent/received by some of these application servers (TS 183 043 [5]). The logic embedded in the AGCF is either interworking logic (e.g. the AGCF has to know how to convert the information contained in an incoming SIP INVITE into a presentation message of the protocol for display services over analog lines as defined in EN 300 659 [12]) or service independent feature logic. On receipt of an off-hook event from a media gateway at the beginning of a call initiation sequence, the AGCF shall apply dial tone unless not required by a feature associated with that line (e.g. fixed destination call). The AGCF's behaviour on receipt of other line events depends on whether or not the AGCF is capable of implementing the feature logic associated with that line, as an example, on a register recall event notification from a media gateway, the AGCF shall determine whether or not to apply dial tone if the AGCF is capable of implementing feature logic for that line; however, if the AGCF is not aware of the feature logic associated with a line and supports mid-call invocation of supplementary services, then it shall send an indication to the AS that register recall has occurred and wait for an indication back as to whether or not dial tone should be applied. Although some application servers may be dedicated to the provision of PES-specific services, the PES architecture does not restrict the type of applications that a PES-user can access (see figure 7). ETSI ETSI TS 182 012 V2.1.4 (2008-03) 22 IMS-based PES Application Servers Embedding PSTN/ISDN emulation logic Application Servers With other types of logic ISC P-CSCF MG AGCF MGCF SS7/TDM networks VGW Gm Gm P1 P1 Analog access ISDN access Figure 7: Service Access via the PES |
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 in relation to the IMS subsystem ES 282 007 [2]. |
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 line parameters mentioned above may be shared across a number of lines (e.g. private user identities are shared by all the lines belonging to an implicitly registered group and home network domain names can be shared across all the lines belonging to the same home IMS-based PES operator). The present document does not mandate a particular data model to be implemented in the AGCF provided that the above information is available and uniquely identifiable by the AGCF on a per-line basis. - (optionally) a temporary public user identity that the line will be implicitly registered against. The use of temporary public user identities in the present document is the same as that described in TS 182 006 [3], i.e. a temporary public user identity is used in the initial registration to register a group of public user identities associated with it. Temporary public user identities shall be, for the present document, provisioned into the AGCF (which contains the functionality of a UE) by means outside the scope of the present document. The allocation of private and public user identities is left to each operator to decide. Two approaches are identified: - One private user identity is assigned to a group of lines/subscribers. ETSI ETSI TS 182 012 V2.1.4 (2008-03) 23 In this scenario, the operator may choose to allocate a temporary public user identity for a group of lines to be implicitly registered against. When available, such temporary public user identity shall be used in the initial registration request. - One private user identity is associated with each line connected to the media gateways controlled by the AGCF. Each private user identity is associated with one home network domain name. The association between a line (represented by a termination identifier on a media gateway) and one or more public user identities is provisioned in the AGCF. The public and private user identities must be known by both the AGCF and the UPSF. It is up to the network operators to ensure that the AGCF and UPSF have consistent information. In addition to the above, each line may be characterized by a line type (e.g. loop calling, PBX, line reversal on answer etc. as described in ETR 150 [13]). The following information may also be provisioned on a per-line basis or on a per media gateway basis: - a default dial-tone; - a default digit-map; and - a default ring cadence. Depending on operator-specific requirements and the features implemented, certain "feature marks" may also be needed in the AGCF on a per-line basis; examples of this include: - Calling Line Identity display to user equipment - this feature mark may be needed in cases where, even if no Calling Line Identity information is signalled to the AGCF, the AGCF needs to instruct to the A-MGW whether to send a "Calling Line Identity unavailable" indication or no indication at all to that line depending on whether or not the user has subscribed to Calling Line Identity presentation services. - Priority line – this feature mark may be required in cases where the AGCF needs to treat calls from or to that line as having priority over other lines controlled by the same AGCF. - Fixed destination call/deferred destination call/ normal line - this feature mark may be required for the AGCF to know whether or not dial tone needs to be applied after off-hook event is detected in the line. In the case of deferred destination call lines, dial tone needs to be applied for a period of time after which dial tone needs to be removed and a call to the fixed destination address (as specified below) be placed. - Fixed destination address - this feature mark is required for the AGCF to know the address it needs to place a call to for lines marked as fixed destination call or deferred destination call lines. - Mid-call Malicious Call Indication - this feature mark may be needed when mid-call Malicious Call Indication is required since, an AGCF that implements service independent feature logic for dealing with mid-call events would autonomously apply dial tone after a register recall event unless this feature mark is activated. The AGCF needs to be made aware of dial tone changes in case some specific supplementary services are activated. For that purpose it subscribes to the appropriate SIP events. |
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 on behalf of each line or group of lines connected to the media gateways it controls, based on the information contained in service change messages received from those media gateways and local configuration information. The rest of the procedures are identical in the PES and IMS subsystems. ETSI ETSI TS 182 012 V2.1.4 (2008-03) 24 A group of lines is represented by a set of public user identities sharing the same private user identity, home domain and, optionally, a temporary public user identity (to be used in the initial registration). One of the public user identities is explicitly registered; note that, if present, the temporary public user identity shall be used for the initial explicit registration. Other public user identities are implicitly registered. The list of implicitly registered identities is returned by the UPSF to the AGCF. It should be noted that creating large registration groups may lead to excessively long signalling messages, any issues associated with this need to be solved by implementation. If the list of registered identities returned by the UPSF does not match the list of public user identities associated with the private user identity, the AGCF should take appropriate management actions outside the scope of the present document. |
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 be applied, the AGCF can also determine whether a special dial tone needs to be delivered. |
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 AGCF SIP stack Gq' R-MGF /A-MGF SPDF RACS P1 Mw e2 Feature Manager IMS Agent MGC IMS Agent IMS Agent MGC H.248 Stack Line-based Configuration data Ut Figure 8: AGCF internal structure |
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 gateways; • control the connection of tones and announcements in media gateways; • receive line events and DTMF digits from media gateways; • request media gateways to monitor line events and DTMF digits; • perform basic digit analysis sufficient determine end of dialling to detect emergency calls (see note); • provide line signals to media gateways; • download "Digit Maps" to media gateways; • controls media mapping and transcoding; • controls signal processing features such as echo cancellation in media gateways. NOTE: The full digit analysis procedure required for normal call routing purposes is performed by the S-CSCF and Application Servers. ETSI ETSI TS 182 012 V2.1.4 (2008-03) 26 |
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 two parties, each of these relationships being associated with a call state and a SIP dialogue. SIP Dialogue #1 SIP Dialogue #2 Analogue Line Leg#2 Leg#1 Dialogue/call state Dialogue/call state Figure 9: AGCF Call and Connection model The feature manager component performs the following functions: • Perform mediation of signalling events between Media gateways and S-CSCF in accordance with the connection model of AGCF. • Request the registration of lines to the IMS core. Two possible mechanisms are be supported: - registration/deregistration of individual endpoints or registration/deregistration of the group of lines. • Interacts with Application Servers to retrieve the current dial tone from the subscriber profile. • When the AGCF supports service-independent feature logic for mid-call events, the feature manager shall invokes basic features logic for processing mid call events, based on the call state and connection configuration. • When the AGCF does not support service-independent feature logic for mid-call events, the feature manager shall send an indication to the AS that a certain mid-call event has occurred and wait for an indication back as to what actions should be performed next NOTE: User input leading to mid call events may take various forms (e.g. register-recall, register-recall followed by one or more digits, one or more digits, etc.) depending on the network policies. Signalling procedures in support of the above processing logic is outside the scope of this technical specification but shall be compatible with the constraints of the P1 and Mw reference points. • Perform the mapping between alert information received from SIP signalling and ring patterns. • Subscribe to the state of the lines behind media gateways in order to be informed when an individual line is deregistered (e.g. due to operational action a line may be no longer active). • Manage the subscription for event report request from AS. The notification is delivered to the right AS. ETSI ETSI TS 182 012 V2.1.4 (2008-03) 27 |
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 Manager that is responsible for processing them in accordance with the actual connection model of the line. • Communicate with an I-CSCF (potentially via an IBCF) in order to address the right S-CSCF in the same or a different operator's network. The identity of I-CSCF can be derived from DNS query. • Interact with the Resource and Admission Control Subsystems (RACS). • Interfaces with the Network Attachment Subsystem (NASS) in order to retrieve information related to the IP- connectivity access session (e.g. physical location of the user equipment), when the media gateway is located in the customer premises (i.e. residential media gateway). The IMS agent is considered a trusted network element and therefore, security is equivalent to other IMS network elements. |
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 range from obvious scenarios with a one to one mapping between functional entities and physical entities, to physical architectures mimicking the hierarchical architecture of legacy networks (i.e. local and transit levels), based on only two types of physical nodes: call servers and media gateways. ETSI ETSI TS 182 012 V2.1.4 (2008-03) 28 Annex A (informative): Areas of discussion and potential open items So far, areas of discussion and potential open items include at least the following: • Registration through the AGCF: - Overlap sending. • Interworking between AGCF and AS: - Clarify what parts of encapsulated ISUP are needed. Alternative solutions to it. - Usage of Ut reference point. • Alignment with 3GPP: - Clarify the usage of encapsulated ISUP information. ETSI ETSI TS 182 012 V2.1.4 (2008-03) 29 History Document history V2.1.4 March 2008 Publication |
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 hosted in NGCN or NGN); and • to support connection and interoperation of business communication capabilities to other business communication capabilities located in or connected to the ISDN and PSTN; and • to support PABX functionality (hosted enterprise services) in an NGN. NOTE 1: Network requirements to support connection of NGCN directly connected to an NGN are specified. NOTE 2: Attachment of legacy PBX functionality to the NGN is not specified in the present document. It is assumed that existing legacy service requirements apply in this case. The present document also specifies network requirements for communication between NGCN capabilities (including user equipment) to other NGCN capabilities of the same enterprise through the NGN (e.g. geographically separated). The present document does not specify NGCN services, nor does it specify network based application services provided to a user of an NGCN. |
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 are not found to be publicly available in the expected location might be found at http://docbox.etsi.org/Reference. NOTE: While any hyperlinks included in this clause were valid at the time of publication, ETSI cannot guarantee their long term validity. The following referenced documents are necessary for the application of the present document. [1] Void. [2] Void. [3] Void. [4] Void. [5] Void. [6] Void. [7] Void. [8] Void . [9] ETSI TS 122 519: "Universal Mobile Telecommunications System (UMTS); LTE; Business Communication Requirements (3GPP TS 22.519)". ETSI ETSI TS 181 019 V3.0.0 (2015-10) 6 |
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 included in this clause were valid at the time of publication, ETSI cannot guarantee their long term validity. 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] Void. [i.2] Void. |
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 V3.0.0 (2015-10) 9 History Document history V2.0.0 November 2007 Publication V3.0.0 October 2015 Publication |
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 specification starts from outlining high-level IPTV functional architecture, functional groups and is further developed into the more detailed functional architecture, reference points and operational modes. The architecture is intended to support requirements defined by the respective ETSI TISPAN requirement definitions [1] and allow integration new or existing IPTV solutions (such as those defined by DVB, ATIS IIF, ITU, etc.) within the NGN architecture. The resulting architecture should, should rely as much as possible on common components and integrates, coexist with other TISPAN NGN services. The following areas are covered: • Authentication and authorization. • Content Protection (including DRM). • Capability exchange. • Resource Management. • Policy Management. • Charging. • User Profiles. The architecture focuses on closer integration between IPTV services and NGN networks, migration scenarios from existing solutions (i.e. DVB-IPI, ATIS-IIF) into NGN and common components. |
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 are not found to be publicly available in the expected location might be found at http://docbox.etsi.org/Reference. NOTE: While any hyperlinks included in this clause were valid at the time of publication ETSI cannot guarantee their long term validity. |
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 Video Broadcasting (DVB); Transport of MPEG-2 TS Based DVB Services over IP Based Networks". [3] ETSI TS 122 240: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Service requirements for 3GPP Generic User Profile (GUP); Stage 1 (3GPP TS 22.240)". ETSI ETSI TS 182 028 V3.5.1 (2011-02) 8 [4] ETSI TS 123 240: "Universal Mobile Telecommunications System (UMTS); LTE; 3GPP Generic User Profile (GUP) requirements; Architecture (Stage 2) (3GPP TS 23.240)". [5] ETSI ES 282 001 (Release 2): "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); NGN Functional Architecture ". [6] ETSI TS 182 027 (Release 3): "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); IPTV Architecture; IPTV functions supported by the IMS subsystem". [7] IETF RFC 2782: "A DNS RR for specifying the location of services (DNS SRV)". [8] ETSI ES 282 007 (Release 2): "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); IP Multimedia Subsystem (IMS); Functional architecture". [9] ETSI ES 282 004 (Release 2): "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); NGN Functional Architecture; Network Attachment Sub-System (NASS)". [10] ETSI ES 282 003 (Release 2): "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Resource and Admission Control Sub-system (RACS); Functional Architecture". [11] ETSI TS 187 003 (Release 2): "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); NGN Security; Security Architecture". [12] ETSI ES 282 010 (Release 2): "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Charging management [Endorsement of 3GPP TS 32.240 Release 7, 3GPP TS 32.260 Release 7, 3GPP TS 32.297 Release 7, 3GPP TS 32.298 Release 7 and 3GPP TS 32.299 Release 7, modified]". [13] ETSI TS 132 240: "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Telecommunication management; Charging management; Charging architecture and principles (3GPP TS 32.240)". [14] ETSI TS 183 064 (Release 2): "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Dedicated IPTV subsystem stage 3 specification". |
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, IEICE transactions on communications, ISSN 0916-8516, Vol. 87 (2004), No. 10, pp. 3057-3067 (11). [i.2] ETSI ES 204 915 (all parts): "Open Service Access (OSA); Application Programming Interface (API) (Parlay 6)". [i.3] ETSI ES 202 504 (all parts): "Open Service Access (OSA); Parlay X Web Services; (Parlay X 3)". [i.4] ETSI TR 187 013: "Telecommunications and Internet Converged Services and Protocols for Advanced Networking (TISPAN); Feasibility study on IPTV security architecture". [i.5] SCTE-130 part 1: "Digital Program Insertion - Advertising Systems Interfaces; Part 1 Advertising Systems Overview". [i.6] SCTE-130 part 2: "Digital Program Insertion - Advertising Systems Interfaces; Part 2: Core Data Elements". [i.7] SCTE-130 part 3: "Digital Program Insertion - Advertising Systems Interfaces; Part 3: Ad Management Service (ADM) Interface". ETSI ETSI TS 182 028 V3.5.1 (2011-02) 9 [i.8] SCTE-35: "Digital Program Insertion Cueing Message for Cable". [i.9] ETSI TS 182 028 (V2.0.0): "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); IPTV Architecture; Dedicated subsystem for IPTV functions". [i.10] ITU-T Recommendation Y.1910: "IPTV functional architecture". |
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 identifier: super class of the identifiers that identify content in specific IPTV services media stream identifier: identifier carried in a unicast or multicast media stream that identifies that specific media stream |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.