hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
6c20142db410ff122a3cb510f7a6cc43 | 186 015-1 | 4.2 Identification of the implementation | Identification of the Implementation Under Test (IUT) and the system in which it resides - the System Under Test (SUT) should be filled in so as to provide as much detail as possible regarding version numbers and configuration options. The product supplier information and client information should both be filled in if ... |
6c20142db410ff122a3cb510f7a6cc43 | 186 015-1 | 4.2.1 Date of the statement | Date of the statement: |
6c20142db410ff122a3cb510f7a6cc43 | 186 015-1 | 4.2.2 Implementation Under Test (IUT) identification | IUT name: IUT version: |
6c20142db410ff122a3cb510f7a6cc43 | 186 015-1 | 4.2.3 System Under Test (SUT) identification | SUT name: Hardware configuration: Operating system: |
6c20142db410ff122a3cb510f7a6cc43 | 186 015-1 | 4.2.4 Product supplier | Name: Address: Telephone number: Facsimile number: Additional information: |
6c20142db410ff122a3cb510f7a6cc43 | 186 015-1 | 4.2.5 Client | Name: Address: Telephone number: Facsimile number: Additional information: |
6c20142db410ff122a3cb510f7a6cc43 | 186 015-1 | 4.2.6 PICS contact person | Name: Telephone number: Facsimile number: Additional information: |
6c20142db410ff122a3cb510f7a6cc43 | 186 015-1 | 4.3 PICS proforma tables | |
6c20142db410ff122a3cb510f7a6cc43 | 186 015-1 | 4.3.1 Global statement of conformance | (Yes/No) Are all mandatory capabilities implemented? ETSI ETSI TS 186 015-1 V2.1.1 (2009-07) 9 |
6c20142db410ff122a3cb510f7a6cc43 | 186 015-1 | 4.3.2 Terminal and network capabilities | Table 1: Network capabilities Item Item description Reference Status Support 1 Is the blind transfer supported? 5.11.6 [2] o.11 2 Is the assured transfer supported? 5.11.6 [2] o.11 3 Is the consultative transfer supported? 5.11.6 [2] o.11 4 The AS initiate the special REFER handling procedures when a 403 Forbidden or 5... |
057e018c19a0f5b48f5c34a406bf0790 | 188 005-1 | 1 Scope | The present document identifies the requirements for the NGN Network Resource Model (NRM). This NRM is an information model of the NGN Resources defined in the NGN specified by ETSI TISPAN which captures the management aspects (i.e. the management view of the NGN). Clause 4 of the present document captures the general ... |
057e018c19a0f5b48f5c34a406bf0790 | 188 005-1 | 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 accept... |
057e018c19a0f5b48f5c34a406bf0790 | 188 005-1 | 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 TS 188 003: "Telecommunications and Internet con... |
057e018c19a0f5b48f5c34a406bf0790 | 188 005-1 | 2.2 Informative references | The following referenced documents are not essential to the use of the present document but they assist the user with regard to a particular subject area. For non-specific references, the latest version of the referenced document (including any amendments) applies. [i.1] ETSI TR 180 001: "Telecommunications and Interne... |
057e018c19a0f5b48f5c34a406bf0790 | 188 005-1 | 3 Abbreviations | For the purposes of the present document, the following abbreviations apply: AF Application Function AGCF Access Gateway Control Function AGF Access Gateway Function AMF Access Management Function A-MGF Access Media Gateway Function A-RACF Access Resource and Admission Control Function ARF Access Relay Function ASF Typ... |
057e018c19a0f5b48f5c34a406bf0790 | 188 005-1 | 4 General requirements | The following general and high-level requirements apply for the NRM: • NRM related requirements in TR 180 001 [i.1]. The present document provides a description of the content and capabilities of NGN Release 1 which need to be supported by the NRM. • NRM related requirements in TS 188 003 [1]. The present document prov... |
057e018c19a0f5b48f5c34a406bf0790 | 188 005-1 | 4.1 Reuse of specifications | To avoid overlap and duplication, the Network Resource Model should import relevant definitions (e.g. Object classes, attributes, etc.) from the 3GPP, TMF, ITU-T etc. where appropriate. |
057e018c19a0f5b48f5c34a406bf0790 | 188 005-1 | 4.2 Granularity of Managed Objects | This clause states requirements on the level of granularity for managed entities. |
057e018c19a0f5b48f5c34a406bf0790 | 188 005-1 | 4.2.1 Motivation, remarks, or examples | Based on, (see ES 282 001 [3]), the TISPAN NGN overall architecture (see figure 2) is the starting point for decomposition of the TISPAN NGN. Entities of this overall architecture are further decomposed recursively. This decomposition is performed in three dimensions: • Decomposition into layer entities e.g. Service La... |
057e018c19a0f5b48f5c34a406bf0790 | 188 005-1 | 4.2.2 Requirements | Requirement 1: • Each subsystem that has manageable aspects which are agreed on the basis of documented technical analysis performed on existing TISPAN specifications or are documented within an agreed Use case for an NGN management interface shall map to one manageable model element of the NGN Network Resource Model. ... |
057e018c19a0f5b48f5c34a406bf0790 | 188 005-1 | 4.3 Inter Domain Management | |
057e018c19a0f5b48f5c34a406bf0790 | 188 005-1 | 4.3.1 Motivation, remarks, or examples | According to the NGN functional architecture (see ES 282 001 [3]), functional entities or subsystems may be distributed over network/service provider domain borders. E.g. a network attachment subsystem, an I-BGF, or a service-layer subsystem that supports nomadism may be distributed between a visited and a home network... |
057e018c19a0f5b48f5c34a406bf0790 | 188 005-1 | 4.3.2 Requirements | Requirement 1: • The Network Resource Model shall allow management of resources which are shared between administrative domains. |
057e018c19a0f5b48f5c34a406bf0790 | 188 005-1 | 5 NGN Managed Entities | ES 282 001 [3] describes the overall TISPAN NGN functional architecture, its subsystems and the relationships between them. The present document, together with the Functional Architectures of the IMS (see ES 282 007 [7]), PES (see ES 282 002 [4]), IMS based PES (see TS 182 012 [i.2]), NAS (see ES 282 004 [5]), and RACS... |
057e018c19a0f5b48f5c34a406bf0790 | 188 005-1 | 5.1 Analysis of Service Layer | |
057e018c19a0f5b48f5c34a406bf0790 | 188 005-1 | 5.1.1 Common Managed Entities | The following entities are defined in ES 282 001 [3]. IBCF IWF Transfer Functions Transport control To/From other IP networks Service Control Subsystems Transport Layer Service Layer ASF (type 2) UPSF ASF (type 1) Data Collection Charging mediation Mediation to other management applications … SLF Figure 3: Common compo... |
057e018c19a0f5b48f5c34a406bf0790 | 188 005-1 | 5.1.2 The IMS | The following Core IMS entities are defined in ES 282 007 [7]. Other IP Networks IP Transport (Access and Core) T-MGF I-BGF AS UPSF P-CSCF I/S-CSCF BGCF SLF Charging Functions IWF « Core IMS» Mw Mw/Mk/Mm 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 Admissio... |
057e018c19a0f5b48f5c34a406bf0790 | 188 005-1 | 5.1.3 PSTN/ISDN Emulation Subsystem | The following entities are defined in ES 282 002 [4]. Distributor Service A Service B Service C Master Customer Data Customer Location Trunk Routing Service 1 Service 2 Service 3 PSTN/ISDN Services AGCF TGCF SGCF AGF AGF S/T Z AS MGF e A - BGF I - BGF RACS IN PSTN / ISDN RG Gq’ Topology Hiding Gateway Other NGN’s Other... |
057e018c19a0f5b48f5c34a406bf0790 | 188 005-1 | 5.1.4 IMS-based PSTN/ISDN Emulation Subsystem | The following entities are defined in TS 182 012 [i.2]. Other IP Networks IP Transport (Access and Core) T-MGF I-BGF UPSF BGCF Charging Functions IWF IMS-based PES Mw Mx Mr Mg Mj Mi Mp Mn Gm Gq' ISC/Ma 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 ... |
057e018c19a0f5b48f5c34a406bf0790 | 188 005-1 | 5.2 Analysis of Transport Layer | |
057e018c19a0f5b48f5c34a406bf0790 | 188 005-1 | 5.2.1 Transfer Functions | The following entities are defined in ES 282 001 [3]. T-MGF I-BGF C-BGF MRFP Transfer Functions SGF ARF RCEF Other networks User Equipment Service Layer A-MGF NASS RACS L2TF Figure 7: Transport Layer Managed Components As a result of analysis, the following entities are required to be modelled in the NRM. TISPAN Entity... |
057e018c19a0f5b48f5c34a406bf0790 | 188 005-1 | 5.2.2 NASS | The following entities are defined in ES 282 004 [5]. a4 Service control subsystems and applications TE CNG a3 a1 a2 e1 e2 e4 e3 Resource and Admission Control Subsystem CLF NACF CPECF AMF PDBF UAAF ARF e1 e2 e5 CNGCF UE Figure 8: TISPAN NAS As a result of analysis, the following entities are required to be modelled in... |
057e018c19a0f5b48f5c34a406bf0790 | 188 005-1 | 5.2.3 RACS | The following entities are defined in ES 282 003 [6]. Di Transport Layer Rq Di A-RACF Ia e4 Re Gq’ Ra NASS AF SPDF Core Border Node BGF Ip Edge RCEF L2T Point Access Node RACS UE Ds Di Transport Layer Rq Di A-RACF Ia e4 Re Gq’ Ra NASS AF SPDF Core Border Node BGF Ip Edge RCEF L2T Point Access Node RACS UE Ds Figure 9: ... |
057e018c19a0f5b48f5c34a406bf0790 | 188 005-1 | 5.3 List of NGN Managed Entities | |
057e018c19a0f5b48f5c34a406bf0790 | 188 005-1 | 5.3.1 Required NGN Managed Entities | Based on the analysis of clauses 5.1 and 5.2, the NGN entities to be managed are: TISPAN Entity AMF (Access Management Function) A-MGF (Access) A-RACF ARF ASF Type 1 (Application Server Function (ASF) Type 1) ASF Type 2 (Application Server Function (ASF) Type 2) BGCF C-BGF CLF (Connectivity Session Location and Reposit... |
057e018c19a0f5b48f5c34a406bf0790 | 188 005-1 | 5.3.2 Candidate NGN Managed Entities identified for further study | TISPAN Entity Charging and data Collection Function Trunk Routing Customer Location AGF (Access Gateway Function) R-MGF (Residential Media Gateway Function) Media Gateway Function BGF L2TF ETSI ETSI TS 188 005-1 V2.1.1 (2009-02) 17 Annex A (normative): Agreed Use Cases This clause captures agreed use cases. Table A.1: ... |
f70fb7e2e21534cac81ae96c16587368 | 187 001 | 1 Scope | The present document defines the security requirements pertaining to TISPAN NGN Release 1. The present document holds requirements for the various NGN subsystems defined at a stage 1 level. The present document covers security requirements for both the NGN core network, and the NGN access network(s). The main scope of ... |
f70fb7e2e21534cac81ae96c16587368 | 187 001 | 2 References | The following documents contain provisions which, through reference in this text, constitute provisions of the present document. • 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. • ... |
f70fb7e2e21534cac81ae96c16587368 | 187 001 | 3 Definitions and abbreviations | |
f70fb7e2e21534cac81ae96c16587368 | 187 001 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: anonymous communication: anonymous communication session is given when a user receiving a communication session cannot identify the originating user |
f70fb7e2e21534cac81ae96c16587368 | 187 001 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: 3G 3rd Generation 3GPP 3rd Generation Partnership Project AA Authentication & Authorization ACR Anonymous Communications Rejection AF Application Function ALG Application Layer Gateway AP Authentication Proxy AS Application Server CNG Customer... |
f70fb7e2e21534cac81ae96c16587368 | 187 001 | 4 Security Requirements | Security requirements described in clause 4 are identified by a symbolic security requirement identifier (e.g. R-SP-n) for quick reference and along with some textual description. The security requirements are listed without any implied preference or priority. It is pointed out that not all security requirements are mu... |
f70fb7e2e21534cac81ae96c16587368 | 187 001 | 4.1 Security Policy Requirements | A security policy defines the legitimate users of a system and what they are allowed to do. It states what information must be protected from which threats. In environments with heterogeneous user communities, multiple vendors' equipment, differing threat models, and uneven deployment of security functionality, assuran... |
f70fb7e2e21534cac81ae96c16587368 | 187 001 | 4.3 Identity and Secure Registration Requirements | The following requirements aims to mitigate against masquerading, spoofing, and impersonation of NGN terminals, devices/systems (HW/SW) and users. The requirements aim to provide measures against identity theft, misuse/authorized use of NGN services/applications. (R-IR- 1): It shall be possible to implicitly register I... |
f70fb7e2e21534cac81ae96c16587368 | 187 001 | 4.4 Communications and Data Security Requirements | Clause 4.4 contains such requirements that address communications and data security. Data, in this context, can mean either user data (e.g. voice, video, text stream) or management data. |
f70fb7e2e21534cac81ae96c16587368 | 187 001 | 4.4.1 General Communications and Data Security Requirements | General (R-CD- 1): Confidentiality and integrity of IMS signalling shall be applied in a hop-to-hop fashion. (UE-to-P-CSCF and among other NEs). NDS (R-CD- 2): Network Domain Security (NDS) shall be provided at the network layer and comply to TS 133 210 [3]. (R-CD- 3): All NDS/IP traffic shall pass through a SEGF (Secu... |
f70fb7e2e21534cac81ae96c16587368 | 187 001 | 4.4.2 Integrity and Replay Protection Requirements | General (R-CD- 13): Integrity protection of signalling, control communications and of stored data shall be provided. (R-CD- 14): It shall be possible to ensure the origin, integrity and freshness of authentication data, particularly of the cipher key. Access Security (R-CD- 15): Integrity protection shall be applied be... |
f70fb7e2e21534cac81ae96c16587368 | 187 001 | 4.4.3 Confidentiality Requirements | General (R-CD- 18): Confidentiality of communications should be achieved by cryptographic encryption. Confidentiality of stored data shall be achieved by cryptographic encryption or by access controls. (R-CD- 19): Confidentiality of signalling and control messages shall be enforced if required by the application or in ... |
f70fb7e2e21534cac81ae96c16587368 | 187 001 | 4.5 Privacy Requirements | (R-P- 1): It shall be possible to protect the network topology from exposure toward other domains. It shall also be possible for a security domains to define and implement protection against traffic analysis for signalling and management protocols. (R-P- 2): User location and usage patterns shall be kept from unwanted ... |
f70fb7e2e21534cac81ae96c16587368 | 187 001 | 4.6 Key Management Requirements | (R-KM- 1): Key management and key distribution between SEGFs shall comply to the Network Domain Security TS 133 210 [3]. (R-KM- 2): The UE and the AS shall be able to resume a previously established secure session. (R-KM- 3): The key management mechanism must be able to traverse a NAT/NATP device. |
f70fb7e2e21534cac81ae96c16587368 | 187 001 | 4.7 Secure Management Requirements | Security Management requirements are for further study. |
f70fb7e2e21534cac81ae96c16587368 | 187 001 | 4.8 NAT/Firewall Interworking Requirements | Firewall is here understood in a generic sense. A firewall could be an application-level gateway (ALG), a proxy, a packet-filter, a NAT/NATP device or a combination of all of those. A Security Gateway Function is an entity on the border of the IP security domain and is used to secure native IP based protocols over the ... |
f70fb7e2e21534cac81ae96c16587368 | 187 001 | 4.9 Non-Repudiation Requirements | Non-repudiation requirements are for further study. |
f70fb7e2e21534cac81ae96c16587368 | 187 001 | 4.10 Availability and DoS protection Requirements | (R-AD- 1): Mechanisms shall be provided to mitigate denial-of-service attacks. (R-AD- 2): Provide access control mechanisms to ensure that authorized users only can access the service. (R-AD- 3): It shall be possible to prevent intruders from restricting the availability of services by logical means. (R-AD- 4): Availab... |
f70fb7e2e21534cac81ae96c16587368 | 187 001 | 4.11 Assurance Requirements | (R-AS- 1): The TISPAN NGN shall provide guidance for evaluating and certifying NGN equipment and systems. (R-AS- 2): Security implications of potential misuse of protocols used in NGN shall be documented through a TVRA. This enables users to assess the security they need before deploying the given protocol. |
f70fb7e2e21534cac81ae96c16587368 | 187 001 | 4.12 Requirements on Strength of Security Mechanisms | The guidelines defined in EG 202 238 [4] shall be followed when defining or selecting cryptographic algorithms in TISPAN. |
f70fb7e2e21534cac81ae96c16587368 | 187 001 | 5 NGN Security Release 1 Requirements Mapping | Clause 5 maps the security requirements identified in clause 4 to the different subsystems as well as the interfaces they applies to. Clause 5 is intended as an informational clause to make it easier to trace requirements per interface and subsystem. Other networks Other subsystems Core IMS PSTN/ISDN Emulation subsyste... |
f70fb7e2e21534cac81ae96c16587368 | 187 001 | 5.1 Network Access SubSystem (NASS) | Requirements related to NASS Security Requirements (R-AA- 24): NASS shall support both the use explicit (e.g. PPP or IEEE 802.1x) and/or implicit line authentication (e.g. MAC address authentication or line authentication) of the users/subscribers. In the case of the implicit access authentication, it shall rely only o... |
f70fb7e2e21534cac81ae96c16587368 | 187 001 | 5.2 Resource and Admission Control Subsystem (RACS) | Requirements related to RACS Security Requirements (R-AA- 27): As the interface between the Application Function (AF) and RACS can be inter-operator, the RACS shall authenticate and authorize the Application Function (AF). (R-SP- 1): The TISPAN NGN network shall be logically and physically divided into security domains... |
f70fb7e2e21534cac81ae96c16587368 | 187 001 | 5.3 The Core IP Multimedia Subsystem (IMS) | Requirements related to Core IMS Security Requirements (R-AA- 1): Access to NGN networks, services, and applications shall be provided for authorized users only. (R-AA- 3): In non-early deployment scenarios, IMS authentication shall be independent from access authentication. (R-AA- 4): An ISIM shall be used to access a... |
f70fb7e2e21534cac81ae96c16587368 | 187 001 | 5.4 The PSTN/ISDN Emulation subsystem (PES) | Requirements related to PES Security Requirements (R-AA- 28): A media gateway controller must be able to handle authentication of multiple media gateways, i.e. to maintain multiple security associations with different media gateways. (R-SP- 1): The TISPAN NGN network shall be logically and physically divided into secur... |
f70fb7e2e21534cac81ae96c16587368 | 187 001 | 5.5 Application Server (AS) | Clause 5.5 lists the security requirements related to the Application Systems. NOTE: This is not a separate subsystem, but has been included to make it easier to track AS related requirements. Security Requirements (R-AA- 1): Access to NGN networks, services, and applications shall be provided for authorized users only... |
e79f48614b821558e326131aea55b05e | 186 012-1 | 1 Scope | The present document specifies the protocol implementation conformance statement of the Subaddressing (SUB) service, based on IP Multimedia Call Control Protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP) Stage 3. Within the Next Generation Network (NGN) the stage 3 description is... |
e79f48614b821558e326131aea55b05e | 186 012-1 | 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 accept... |
e79f48614b821558e326131aea55b05e | 186 012-1 | 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 283 003: "Telecommunications and Internet con... |
e79f48614b821558e326131aea55b05e | 186 012-1 | 2.2 Informative references | The following referenced documents are not essential to the use of the present document but they assist the user with regard to a particular subject area. For non-specific references, the latest version of the referenced document (including any amendments) applies. Not applicable. |
e79f48614b821558e326131aea55b05e | 186 012-1 | 3 Definitions and abbreviations | |
e79f48614b821558e326131aea55b05e | 186 012-1 | 3.1 Definitions | For the purposes of the present document, the terms and definitions given in TS 181 002 [2] and RFC 3261 [3] apply. |
e79f48614b821558e326131aea55b05e | 186 012-1 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: HOLD communication HOLD IMS IP Multimedia Subsystem IP Internet Protocol ISDN Integrated Service Data Network NGN Next Generation Network OCB Outgoing Communication Barring PSTN Public Switched Telephone Network SDP Session Description Protoco... |
e79f48614b821558e326131aea55b05e | 186 012-1 | 4.1 Instructions for completing the PICS proforma | 4.1.1 More detailed instructions are given at the beginning of the different clauses of the PICS proforma The supplier of the implementation shall complete the PICS proforma in each of the spaces provided. If necessary, the supplier may provide additional comments separately in clause 5. |
e79f48614b821558e326131aea55b05e | 186 012-1 | 4.1.1.1 Purposes and structure | The purpose of this PICS proforma is to provide a mechanism whereby a supplier of an implementation of the requirements defined in reference specification [1] to [6] may provide information about the implementation in a standardized manner. The PICS proforma is subdivided into clauses for the following categories of in... |
e79f48614b821558e326131aea55b05e | 186 012-1 | 4.1.2 Abbreviations and conventions | The PICS proforma is composed of an information in tabular form in accordance with the guidelines presented in ISO/IEC 9646-7 [4]. Item column It contains a number that identifies the item in the table. Item description column It describes each respective item (e.g. parameters, timers, etc.). Reference column It gives ... |
e79f48614b821558e326131aea55b05e | 186 012-1 | 4.2 Identification of the implementation | Identification of the Implementation Under Test (IUT) and the system in which it resides - the System Under Test (SUT) should be filled in so as to provide as much detail as possible regarding version numbers and configuration options. The product supplier information and client information should both be filled in if ... |
e79f48614b821558e326131aea55b05e | 186 012-1 | 4.2.1 Date of the statement | Date of the statement: |
e79f48614b821558e326131aea55b05e | 186 012-1 | 4.2.2 Implementation Under Test (IUT) identification | IUT name: IUT version: |
e79f48614b821558e326131aea55b05e | 186 012-1 | 4.2.3 System Under Test (SUT) identification | SUT name: Hardware configuration: Operating system: ETSI ETSI TS 186 012-1 V1.0.0 (2008-06) 9 |
e79f48614b821558e326131aea55b05e | 186 012-1 | 4.2.4 Product supplier | Name: Address: Telephone number: Facsimile number: Additional information: |
e79f48614b821558e326131aea55b05e | 186 012-1 | 4.2.5 Client | Name: Address: Telephone number: Facsimile number: Additional information: |
e79f48614b821558e326131aea55b05e | 186 012-1 | 4.2.6 PICS contact person | Name: Telephone number: Facsimile number: Additional information: |
e79f48614b821558e326131aea55b05e | 186 012-1 | 4.3 PICS proforma tables | |
e79f48614b821558e326131aea55b05e | 186 012-1 | 4.3.1 Global statement of conformance | (Yes/No) Are all mandatory capabilities implemented? ETSI ETSI TS 186 012-1 V1.0.0 (2008-06) 10 |
e79f48614b821558e326131aea55b05e | 186 012-1 | 4.3.2 Roles and network capabilities | Table 1: Roles and network capabilities Item Item description Reference Status Support 1 [UE] Is the Subaddressing service provided? 3 o 2 Is the Subaddressing service provided? 3 o 3 [MGCF] Is the interworking of isub parameter in the user part of an URI and the Subaddress contained in an ATP parameter in an ISUP mess... |
e79f48614b821558e326131aea55b05e | 186 012-1 | 5 Additional information for PICS | ETSI ETSI TS 186 012-1 V1.0.0 (2008-06) 11 History Document history V1.0.0 June 2008 Publication |
8d6b81b6feaac0bfdd1bdac27a4cbbf8 | 186 025-4 | 1 Scope | The present document is for an initial release of a PSTN/ISDN Emulation Sub-system (PES) performance benchmark. The same tests can be used also for legacy PSTN/ISDN networks or for inter-working tests between PSTN/ISDN emulation subsystem and legacy PSTN and ISDN. The metrics measured and reported are for performance o... |
8d6b81b6feaac0bfdd1bdac27a4cbbf8 | 186 025-4 | 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... |
8d6b81b6feaac0bfdd1bdac27a4cbbf8 | 186 025-4 | 2.1 Normative references | The following referenced documents are necessary for the application of the present document. [1] ETSI TS 101 563: "Speech and multimedia Transmission Quality (STQ); IMS/PES exchange performance requirements". [2] Recommendation ITU-T Q.543: "Digital exchange performance design objectives". [3] ETSI TS 183 036: "Teleco... |
8d6b81b6feaac0bfdd1bdac27a4cbbf8 | 186 025-4 | 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] ETSI TS 186 025-1: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); IMS/PES Performance Benchmark; ... |
8d6b81b6feaac0bfdd1bdac27a4cbbf8 | 186 025-4 | 3 Definitions and abbreviations | |
8d6b81b6feaac0bfdd1bdac27a4cbbf8 | 186 025-4 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: background load: workload applied to an SUT during a benchmark test, for the purpose of consuming SUT resources during a benchmark test and changing the traffic intensity at which the capacity of the SUT is reached benchmark report: do... |
8d6b81b6feaac0bfdd1bdac27a4cbbf8 | 186 025-4 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: AGCF Access Gateway Control Function DLE Destination Local Exchange IBCF Interconnection Border Control Function IMS IP Multimedia Subsystem ISDN Media GateWay Controler ISUP ISDN User Part MGC Media GateWay Controler MGW Media Gateway NGN Nex... |
8d6b81b6feaac0bfdd1bdac27a4cbbf8 | 186 025-4 | 4 Metrics and design objectives | 4.1 Delay probability - non-ISDN or mixed (ISDN - non-ISDN) environment This clause defines delay parameters related to non-ISDN environment and mixed (ISDN - non-ISDN) environment. The values are based on the values in Recommendation ITU-T Q.543 [2] and TS 101 563 [1]. ETSI ETSI TS 186 025-4 V2.2.1 (2013-06) 8 Table 1... |
8d6b81b6feaac0bfdd1bdac27a4cbbf8 | 186 025-4 | 4.2 Call processing performance objectives | |
8d6b81b6feaac0bfdd1bdac27a4cbbf8 | 186 025-4 | 4.2.1 Premature release | The probability that an exchange malfunction will result in the premature release of an established connection in any one minute interval should be: P ≤ 2 x 10-5 |
8d6b81b6feaac0bfdd1bdac27a4cbbf8 | 186 025-4 | 4.2.2 Release failure | The probability that an exchange malfunction will prevent the required release of a connection should be: P ≤ 2 x 10-5 |
8d6b81b6feaac0bfdd1bdac27a4cbbf8 | 186 025-4 | 4.2.3 Incorrect charging or accounting | The probability of a call attempt receiving incorrect charging or accounting treatment due to an exchange malfunction should be: P ≤ 10-4 |
8d6b81b6feaac0bfdd1bdac27a4cbbf8 | 186 025-4 | 4.2.4 Misrouting | The probability of a call attempt misrouted following receipt by the exchange of a valid address should be: P ≤ 10-4 |
8d6b81b6feaac0bfdd1bdac27a4cbbf8 | 186 025-4 | 4.2.5 No tone | The probability of a call attempt encountering no tone following receipt of a valid address by the exchange should be: P ≤ 10-4 |
8d6b81b6feaac0bfdd1bdac27a4cbbf8 | 186 025-4 | 4.2.6 Other failures | The probability of the exchange causing a call failure for any other reason not identified specifically above should be: P ≤ 10-4 |
8d6b81b6feaac0bfdd1bdac27a4cbbf8 | 186 025-4 | 4.3 Transmission performance | |
8d6b81b6feaac0bfdd1bdac27a4cbbf8 | 186 025-4 | 4.3.1 64 kbit/s switched connections | The probability of a connection being established with an unacceptable transmission quality across the exchange should be: P ≤ 10-5 The transmission quality across the exchange is said to be unacceptable when the bit error ratio is above the alarm condition. ETSI ETSI TS 186 025-4 V2.2.1 (2013-06) 27 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.