hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
7bacf70a4dd0b8f943de5e517835b45e | 102 105 | 4.3.2 OMG standardization | The Object Management Group (OMG), established in 1989, is a world-wide software consortium whose goal is to introduce object-oriented standards to the software industry. The OMG is producing standardized specifications which aim to define an object-oriented framework for distributed applications. The main achievement ... |
7bacf70a4dd0b8f943de5e517835b45e | 102 105 | 4.3.3 Standardization of Object Oriented Methods within ITU-T | In working draft Recommendation Z.109 (see Bibliography), "SDL in combination with UML", ITU-T SG10 is studying the possible alignment between the UML and SDL which is defined in ITU-T Recommendation Z.100 [9]. The objective is to define a mapping of UML concepts (possibly a subset) to the SDL language (SDL-2000), so t... |
7bacf70a4dd0b8f943de5e517835b45e | 102 105 | 4.4 Case studies of three types of standard | In order to evaluate the possibility of using the UML within the ETSI standardization process, three different types of standard were reviewed as simple case studies. The types of standard considered were: - protocol specifications; - specifications of physical characteristics; - conformance test specifications. NOTE I... |
7bacf70a4dd0b8f943de5e517835b45e | 102 105 | 4.4.1 Protocol | |
7bacf70a4dd0b8f943de5e517835b45e | 102 105 | 4.4.1.1 Specifying protocol standards | Because the purpose of a protocol standard is to specify the behaviour of an implementation, i.e., there is some processing involved which is likely to be software-intensive, there is a clear opportunity to use object-orientation in its development. The three stage method for describing communications protocols (see CC... |
7bacf70a4dd0b8f943de5e517835b45e | 102 105 | 4.4.1.2 Requirements capture | Use cases and use case diagrams with some textual description can be used to capture the initial requirements of a protocol. As the example in Figure 5 shows, they can also help to simplify the communication of requirements between parties by defining them in a common and easily understandable language. Stage 1 standar... |
7bacf70a4dd0b8f943de5e517835b45e | 102 105 | 4.4.1.3 Functional modelling | As can be seen in Table 2 and in subclause 4.3, many of the diagrams used in the UML bear a strong resemblance to those already produced for most Stage 2 standards: Table 2: Mapping of Stage 2 and UML diagrams Stage 2 diagram UML equivalent functional entity model use case & object diagram relationship with basic servi... |
7bacf70a4dd0b8f943de5e517835b45e | 102 105 | 4.4.1.4 Detailed description | |
7bacf70a4dd0b8f943de5e517835b45e | 102 105 | 4.4.1.4.1 Behaviour specification | Protocol behaviour can be specified using sequence, collaboration, or statechart diagrams. However, without agreed and proven action semantics, the UML cannot offer the simulation and validation capabilities of SDL and is unlikely to be able to replace it as the language of choice for the specification of normative beh... |
7bacf70a4dd0b8f943de5e517835b45e | 102 105 | 4.4.1.4.2 Data specification | It is possible to specify protocol information elements using class diagrams in a similar way to that shown in Figure 11 and Figure 12 for physical characteristics. However, the UML's lack of encoding rules makes this approach less attractive than the use of ASN.1 in specifying protocol data elements which can be sent,... |
7bacf70a4dd0b8f943de5e517835b45e | 102 105 | 4.4.2 Test specification | When testing the implementation of a specification, a number of tests on different layers have to be performed. On the bottom layer, conformance to physical specifications is tested; on the top layers, there are interoperability and network integration tests. ETSI has accepted some test suites for these layers as stand... |
7bacf70a4dd0b8f943de5e517835b45e | 102 105 | 4.4.2.1 Feasibility of using the UML for test specification | With the CTMF and various additional ETSI guidelines, an extensive and proven methodology exists for writing TTCN test specifications. At the moment, there is no need to change this methodology to one that incorporates the UML. The main technical reason for this is that the UML currently lacks many features needed for ... |
7bacf70a4dd0b8f943de5e517835b45e | 102 105 | 4.4.2.1.1 Using the UML to increase test specification readability | ETSI test purpose specifications are usually given as textual descriptions in tables which contain the following rows: - name; - reference; - purpose; - description; - pass criteria; - selection; - preamble; - postamble. Sometimes, informal MSCs are used to provide high level test behaviour descriptions in a graphical ... |
7bacf70a4dd0b8f943de5e517835b45e | 102 105 | 4.4.2.1.2 Deriving test purposes from a UML protocol specification | From a high-level, modelling point of view, test cases seem to be equivalent to UML use cases. Use cases represent the required interactions between a system and actors which are outside the system itself. It is very probable that during testing, an implementation will be checked to ensure that it meets all of the requ... |
7bacf70a4dd0b8f943de5e517835b45e | 102 105 | 4.4.3 Specification of physical characteristics | |
7bacf70a4dd0b8f943de5e517835b45e | 102 105 | 4.4.3.1 Standards specifying physical characteristics | Although specifications related to protocols make up the largest part of ETSI's output of standards, there are also many which specify requirements for the physical characteristics of an item claiming conformance to the standard. Such characteristics include power consumption, electromagnetic radiation, safe access to ... |
7bacf70a4dd0b8f943de5e517835b45e | 102 105 | 4.4.3.2 Open Network Provision (ONP) leased lines | |
7bacf70a4dd0b8f943de5e517835b45e | 102 105 | 4.4.3.2.1 ONP standards | To assess the feasibility and possible benefits of using object orientation in the development of this type of standard, the range of specifications defining the connection characteristics of the digital Open Network Provision (ONP) leased lines was considered. These standards are: - ETS 300 247 [1] 2 048 kbit/s digita... |
7bacf70a4dd0b8f943de5e517835b45e | 102 105 | 4.4.3.2.2 Traditional specification of leased line characteristics | These standards already use a loose form of object-orientation by specifying the characterizing parameters of each leased line type in a table of standard entries as shown in Table 3. Table 3: Table of empty connection attributes Connection type attributes Value Description Nature Reference subclause Information transf... |
7bacf70a4dd0b8f943de5e517835b45e | 102 105 | 4.4.3.2.3 Use of UML to specify leased line characteristics | There are a number of ways in which this information might have been shown using UML rather than tables and Figure 11 indicates one such method. The 'Leased Line' class is shown as an aggregation of the 'Connection Type', 'Network Performance Sub-Attributes' and 'Error Parameters' classes each of which posses attribute... |
7bacf70a4dd0b8f943de5e517835b45e | 102 105 | 4.4.3.2.4 Summary | Without developing this model further, it is clear that the UML could be of some value in the early stages of developing standards of this type specifying physical characteristics. However, it is also arguable that the tabular presentation used in the ONP Leased Line standards is adequate for their intended use and tha... |
7bacf70a4dd0b8f943de5e517835b45e | 102 105 | 4.5 Tool support | In the standard making process at ETSI, a number of requirements for using new methods (such as the UML) and tools should be met. They are: - the ability to interface to existing methods & standards (MSC, SDL, TTCN, ASN.1) already in use; - the availability of tool support and a common exchange format; - graphical anal... |
7bacf70a4dd0b8f943de5e517835b45e | 102 105 | 4.5.1 Current situation | |
7bacf70a4dd0b8f943de5e517835b45e | 102 105 | 4.5.1.1 OO notations for industry | Current trends in specification techniques show that industry needs methods and tools for the following reasons: ETSI ETSI TR 102 105 V1.1.1 (1999-08) 28 - to automate the production of software; - to improve its quality; - to manage system complexity; - to model the system at a high-level independently of any implemen... |
7bacf70a4dd0b8f943de5e517835b45e | 102 105 | 4.5.1.2 Standardization and industrialization of UML | UML unifies different modelling languages by suppressing many of the differences and redundancies. OMG's specification documents and technical papers are being elaborated continuously to provide a primary source for experts as well as for developers of supporting tools, e.g. modelling tools. OMG support is a fundamenta... |
7bacf70a4dd0b8f943de5e517835b45e | 102 105 | 4.5.1.3 Tool support for UML | |
7bacf70a4dd0b8f943de5e517835b45e | 102 105 | 4.5.1.3.1 UML-based tools | |
7bacf70a4dd0b8f943de5e517835b45e | 102 105 | 4.5.1.3.1.1 Support for standard UML | One of the most widely-used UML tools on the market today is Rational Rose from the Rational Software Corporation. Rose supports IS development using the UML notation for the specification and description of systems. It implements a large subset of the UML concepts including UML interfaces and diagrams, propagation of... |
7bacf70a4dd0b8f943de5e517835b45e | 102 105 | 4.5.1.3.1.2 Support for extended UML | The current UML notation is missing several of the concepts necessary for the high-level design of real-time systems. The Real-Time Object-Oriented Modelling language (ROOM) which is similar to the UML, offers an alternative to these limitations. However, in Rational's ObjectTime tool which supports ROOM, actions are i... |
7bacf70a4dd0b8f943de5e517835b45e | 102 105 | 4.5.1.3.2 SDL-UML based tools | |
7bacf70a4dd0b8f943de5e517835b45e | 102 105 | 4.5.1.3.2.1 Telelogic Tau | Telelogic includes support for some UML diagrams in its Tau tool set. Specifically, class diagrams and statechart diagrams can be drawn with the Tau graphical editor. The tool set also provides means for forward engineering from UML to SDL: Classes can be translated into different kinds of type or process definitions. ... |
7bacf70a4dd0b8f943de5e517835b45e | 102 105 | 4.5.1.3.2.2 Verilog ObjectGEODE | Verilog provides extensions, such as a class diagram editor, to its ObjectGEODE tool to support a combined UML-SDL design path. Within the tool, UML is used for high-level modelling and SDL is then used for detailed design and simulation. In a complementary approach, Verilog has developed a direct interface to the Rose... |
7bacf70a4dd0b8f943de5e517835b45e | 102 105 | 4.5.1.3.3 Tool summary | To summarize, it can be said that reasonable tool support exists for the UML, although a common interchange format has yet to be implemented. The forward engineering capabilities of existing tools, such as mapping between UML and SDL, are limited. This aspect should be greatly improved when more precise semantics are d... |
7bacf70a4dd0b8f943de5e517835b45e | 102 105 | 4.5.2 What is needed | |
7bacf70a4dd0b8f943de5e517835b45e | 102 105 | 4.5.2.1 UML features for strong tool support | From a tool support point of view, a suitable UML notation should: - allow users to exchange meaningful visual models the tools should support a common interchange format; - provide for new integration between tools, processes and domains in particular the tools should support the extensibility mechanisms (e.g. tags an... |
7bacf70a4dd0b8f943de5e517835b45e | 102 105 | 4.5.2.2 Standardization framework for UML | As part of its mission, the OMG defines new standards for software engineering that allow the modelling of the real world through the representation of objects. Thus, initial design functionality can easily be expanded by, for example, extending some components or adding new objects to the system. This object engineeri... |
7bacf70a4dd0b8f943de5e517835b45e | 102 105 | 4.5.2.3 Action semantics for UML | The provision of an action semantics for UML is the subject of a current RFP aimed at extending UML by the definition of consistent action semantics for statechart transitions and method bodies in the objects. For the UML tool providers, this will allow them to develop verification tools such as simulators to validate ... |
7bacf70a4dd0b8f943de5e517835b45e | 102 105 | 4.5.2.4 XMI interchange format for UML | XML Metadata Interchange (XMI) is a proposal to an OMG RFP on Stream-based Model Interchange Format (SMIF). The purpose of SMIF is to allow the interchange of models and thus the interchange of information between UML modelling tools and/or metadata repositories based on the OMG MOF standard. It should be stressed that... |
7bacf70a4dd0b8f943de5e517835b45e | 102 105 | 4.5.2.5 Tool interoperability and model extensibility | A combination of tools from different vendors is often necessary to design a system and to document the developed models and programs. However, in practice, such combinations are difficult to achieve because of poor interchange capabilities which require translation or manual re-entry of information, with the inherent ... |
7bacf70a4dd0b8f943de5e517835b45e | 102 105 | 4.5.2.6 SDL-UML alignment and tool support | In respect of ETSI's needs in the standard making process, the mission of a tool manufacturer is to provide its customers with integrated solutions and tools that enhance their productivity, reduce time-to-market and improve the quality of their software. The basic principles of the UML definition meet these needs. Rel... |
7bacf70a4dd0b8f943de5e517835b45e | 102 105 | 5 Conclusions | It was not obvious from the summary in Table 1 how and where object orientation would fit into the overall ETSI standards-making process. However, by studying the potential use of the UML in the three most significant types of standard (protocol specifications, the definition of physical characteristics and the specifi... |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 1 Scope | The present document specifies interoperability Test Descriptions (TDs) for Inter-IMS Network to Network Interface (II-NNI) interoperability testing for the IP Multimedia Call Control Protocol based on Stage 3 Session Initiation Protocol (SIP) and Session Description Protocol (SDP) standard, TS 124 229 [1]. Interconnec... |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 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... |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 2.1 Normative references | The following referenced documents are necessary for the application of the present document. [1] ETSI TS 124 229 (V9.5.0): "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; IP multimedia call control protocol based on Session Initiation Protocol (SIP) and S... |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 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 TR 133 978: "Universal Mobile Telecommunications System (UMTS); Security aspects of early IP Multimedia Subsystem (IMS) (3GPP TR 33.978 version 7... |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 3 Abbreviations | For the purposes of the present document, the following abbreviations apply: 3GPP 3rd Generation Partnership Project ACL Automatic Congestion Level ACM Address Complete Message ACR Anonymous Communication Rejection ACR-CB Anonymous Communication Rejection – Communication Barring AKA Authentication and Key Agreement ALG... |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4 IMS NNI Interoperability Test Specification | |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.1 Introduction | The IMS NNI Interoperability Test Descriptions (TDs) defined in the following clauses are derived from the Test Purposes (TPs) specified in TS 186 011-1 [2]. The TDs cover both basic call procedures such as call establishment and call release and a selection of the most common supplementary services. ETSI ETSI TS 186 0... |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.2 Test Prerequisites | |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.2.1 IP Version | These test specifications are based on the use of IPv4 for SIP message transport throughout all IMS nodes as specified in TR 123 981 [i.2] but do not exclude the use of IPv6 in the case that all involved IMS nodes support this version of the IP protocol. |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.2.2 Authentication and Security | The current test specification supports as default full IMS TS 133 203 [7] 3GPP security. Non-compliance with full IMS security features defined in TS 133 203 [7] is expected to be a problem mainly at the UE side, because of the potential lack of support of the USIM/ISIM interface (especially in 2G-only devices) and of... |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.2.3 Registration and Subscription | |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.2.3.1 SIP Call Flow | This clause describes the registration call flow under the authentication and security scope described in clause 4.2.2. |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.2.3.1.1 Early IMS Registration and Subscription Call Flow | Early IMS security does not allow SIP requests to be protected using an IPsec Security Association (SA) because it does not perform a key agreement procedure. IPsec security associations are not set up between UE and P-CSCF, as they are in the full IMS security solution. For early IMS security, the expected registratio... |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.2.3.1.2 Full IMS Registration and Subscription Call Flow | For full IMS security, the expected registration and subscription sequence is: Step Direction Message Comment UE IMS 1 The UE establishes an IP bearer as required by its specific access network (optional). 2 P-CSCF address discovery using DHCP procedures for IPv4 (optional). 3 REGISTER The UE sends initial registr... |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.2.3.1.3 SIP Digest Registration and Subscription Call Flow | For SIP Digest authentication without key agreement and null authentication, the expected registration and subscription sequence is: Step Direction Message Comment UE IMS 1 The UE establishes an IP bearer as required by its specific access network (optional). 2 P-CSCF address discovery using DHCP procedures for IPv4... |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.2.4 Supported Options | |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.2.4.1 Security | Support for security agreement is optional in case of Full IMS Reg. It shall only be used in case all IMS nodes support it. |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.2.4.2 Signalling Compression | "No SigComp" is the default signalling configuration in all test descriptions. Tests may be executed with signalling compression if the required nodes support it. |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.2.5 Number Resolution | "ENUM (RFC 3761 [i.4]) is a capability that transforms E.164 numbers into domain names and then uses the DNS (Domain Name System) to discover NAPTR records that specify the services available for a specific domain name." (TR 184 008 [i.3]). The test infrastructure focuses on the use of Infrastructure ENUM to map a tele... |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.3 Test Infrastructure | In these clauses we define the involvement of the various IMS nodes specifically as they pertain to NNI testing. The configuration of the nodes is described. Points of control and observation are identified and static test configurations are described. The Mw interface or the Ic interface if topology hiding is required... |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.3.1 Core IMS Nodes | The current testing scope includes IMS roaming and border control functionality. For IMS roaming, Mw reference point between IMS core in visited network (P-CSCF) and IMS core in home network will be monitored for testing purposes. For border control functionality, Mx reference point between IMS Core and IBCF, Ici refer... |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.3.1.1 P-CSCF | |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.3.1.1.1 Relevant Interfaces | The P-CSCF constitutes the point of entry for UE signalling into the IMS core. The Gm interface between the P-CSCF and the UE is used as a point of control and observation (PCO) for NNI interoperability testing purposes. In the case of IMS roaming configurations the Mw reference point of the P-CSCF is exposed at the NN... |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.3.1.1.2 Node Configuration | The P-CSCF should be configured to support the pre-requisites outlined in clause 4.2. |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.3.1.2 S-CSCF | |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.3.1.2.1 Relevant Interfaces | The S-CSCF is the core IMS node delivering IMS services to subscribers. When no border control functionalities are applied, the Mw reference point between the S-CSCF and either I- or S-CSCF in another network domain is used as a PO against which NNI interoperability tests are validated. The Mw interfaces between I- and... |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.3.1.2.2 Node Configuration | The S-CSCF should be configured to support the pre-requisites outlined in clause 4.2. When applicable based on the specific configuration, the S-CSCF must be provisioned to support required Application Servers (AS) as trusted nodes. |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.3.1.3 I-CSCF | |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.3.1.3.1 Relevant Interfaces | The I-CSCF is the contact point within an operator's network for all connections destined to a user of that network operator, or a roaming user currently located within that network operator's service area. When no border control functionalities are applied, the Mw reference point between the I-CSCF and an S-CSCF in an... |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.3.1.3.2 Node Configuration | The I-CSCF should be configured to support the pre-requisites outlined in clause 4.2. ETSI ETSI TS 186 011-2 V4.1.3 (2012-05) 16 |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.3.1.4 IBCF | |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.3.1.4.1 Relevant Interfaces | The IBCF is the core IMS node providing border control functionalities such as topology hiding, transport plane control, screening of SIP signalling or application level gateway (for instance enabling communication between IPv6 and IPv4 SIP applications). However, the IBCF can act also as a pass-through entity between ... |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.3.1.4.2 Node Configuration | The IBCF should be configured to support the pre-requisites outlined in clause 4.2. The IBCF node will be present in all tests to be executed. In case the requirement to support topology hiding is not explicitly stated in the pre-conditions of a test description it shall be assumed that the IBCF does not apply this fun... |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.3.1.5 HSS | |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.3.1.5.1 Relevant Interfaces | The HSS constitutes the repository for IMS subscriber information. The Cx interface between the HSS and the S-CSCF and/or I-CSCF is considered an internal IMS interface. |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.3.1.5.2 Node Configuration | The HSS should be configured within each IMS participating in an interoperability test, i.e. IMS_A as well as IMS_B, to interact with CSCFs as required using DIAMETER Cx interfaces. Users should be provisioned to match the sample profiles listed in table 1. In addition, each IMS shall have its own unique domain. Also t... |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.3.1.6 MRFC | |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.3.1.6.1 Relevant Interfaces | The Media Resource Function Controller (MRFC) is a signalling plane node that acts as a SIP User Agent to the S-CSCF, and which controls the MRFP across an H.248 interface. The Mr interface between the MRFC and the S-CSCF, the Cr/Sr interfaces to the AS and the Mp interface to the MRFP are considered internal IMS inter... |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.3.1.6.2 Node Configuration | The MRFC should be configured to support the pre-requisites outlined in clause 4.2. The need to activate the MRFC as part of an IMS core network depends highly on the test description to be executed. |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.3.1.7 MRFP | |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.3.1.7.1 Relevant Interfaces | The Media Resource Function Processor (MRFP) is a media plane node that implements all media-related functions. The Mp interface between the MRFP and the MRFC is considered an internal IMS interface. |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.3.1.7.2 Node Configuration | The MRFP should be configured to support the pre-requisites outlined in clause 4.2. The need to activate the MRFP as part of an IMS core network depends highly on the test description to be executed. |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.3.1.8 MGCF | |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.3.1.8.1 Relevant Interfaces | The Media Gateway Controller Function (MGCF) does call control protocol conversion between SIP and ISUP. It also controls the resources in a Media Gateway across an H.248 interface. The Mg reference point between the MGCF and an I-CSCF in the same network domain is used as a PO against which NNI interoperability tests ... |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.3.1.8.2 Node Configuration | The MGCF should be configured to support the pre-requisites outlined in clause 4.2. The need to activate the MGCF as part of an IMS core network depends highly on the test description to be executed. |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.3.1.9 MGF | |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.3.1.9.1 Relevant Interfaces | The Media Gateway Function (MGF) interfaces with the media plane of the CS network, by converting between RTP and PCM. It can also transcode when the codecs do not match. The reference points of the MGF with other entities are out of the scope of the test descriptions in the present document. |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.3.1.9.2 Node Configuration | The MGF should be configured to support the pre-requisites outlined in clause 4.2. The need to activate the MGF as part of an IMS core network depends highly on the test description to be executed. ETSI ETSI TS 186 011-2 V4.1.3 (2012-05) 18 |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.3.1.10 SGF | |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.3.1.10.1 Relevant Interfaces | The Signalling Gateway Function (SGF) interfaces with the signalling plane of the CS. It transforms lower layer protocols as Stream Control Transmission Protocol (SCTP) into Message Transfer Part (MTP) protocol), to pass ISDN User Part (ISUP) from the MGCF to the CS network. |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.3.1.10.2 Node Configuration | The SGF should be configured to support the pre-requisites outlined in clause 4.2. The need to activate the SGF as part of an IMS core network depends highly on the test description to be executed. |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.3.2 External IMS core Nodes | |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.3.2.1 UE | |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.3.2.1.1 Relevant Interfaces | The UE is considered to act as a stimulus node in this test specification. The Gm interface between the P-CSCF and the UE is used as a Point of Control and Observation (PCO) for NNI interoperability tests. |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.3.2.1.2 Node Configuration | The UE should be configured to support the pre-requisites outlined in clause 4.2. The test descriptions in the present document assume that a UE supports basic call and messaging functionality, target refresh based on UPDATE and on re-INVITE method, message transport via UDP and TCP, and the use of at least one of the ... |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.3.2.2 AS | |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.3.2.2.1 Relevant Interfaces | Interworking between external Application Servers (AS) and the IMS core is under the scope of the present document. The ISC interface between the S-CSCF and the AS is used as a Point of Observation (PO) for NNI interoperability tests. |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.3.2.2.2 Node Configuration | The AS should be configured to support the pre-requisites outlined in clause 4.2. The test descriptions in the present document assume that an AS supports the use of the supplementary services HOLD (see TS 124 410 [10]), CDIV (see TS 124 404 [11]), ACR-CB (see TS 124 411 [12]), OIP/OIR (see TS 124 407 [13]), IPTV(see T... |
1b570a6648bd6e802a749e39655a3b23 | 186 011-2 | 4.3.3 Supporting IMS Nodes |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.