hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
9014ba8dbedbe826dd149c7c9bc99edf | 188 002-2 | 5.4.2.1 Definition | This represents the relationship between NgnIMSServiceProfile IOC and ApplicationServiceProfile IOC. |
9014ba8dbedbe826dd149c7c9bc99edf | 188 002-2 | 5.4.2.2 Roles | Name Definition theApplicationServiceProfile Represents the Application Service Profile IOCs that may be associated to an IMS Service Profile. |
9014ba8dbedbe826dd149c7c9bc99edf | 188 002-2 | 5.4.3 relatedSuMSubscribedService | |
9014ba8dbedbe826dd149c7c9bc99edf | 188 002-2 | 5.4.3.1 Definition | This represents the relationship between SubscribedServiceGroup IOC and SuMSubscribedService IOC. |
9014ba8dbedbe826dd149c7c9bc99edf | 188 002-2 | 5.4.3.2 Roles | Name Definition theSuMSubscribedService Represents the SuMSubscribedService IOCs associated to a SuMSubscribedServiceGroup. |
9014ba8dbedbe826dd149c7c9bc99edf | 188 002-2 | 5.4.4 relatedRegistrationGroup | |
9014ba8dbedbe826dd149c7c9bc99edf | 188 002-2 | 5.4.4.1 Definition | This represents the relationship between AgcfServiceProfile and RegistrationGroup. |
9014ba8dbedbe826dd149c7c9bc99edf | 188 002-2 | 5.4.4.2 Roles | Name Definition theRegistationGroup Represents the RegistrationGroup IOC used for registration of the line defined in AgcfServiceProfile. |
9014ba8dbedbe826dd149c7c9bc99edf | 188 002-2 | 5.4.4.3 Constraints | This relationship is Conditional. The condition is that no object instance of Individual Registration is present for the same object instance of AgcfServiceProfile. |
9014ba8dbedbe826dd149c7c9bc99edf | 188 002-2 | 5.4.5 relatedRegistrationGroupPrivateId | |
9014ba8dbedbe826dd149c7c9bc99edf | 188 002-2 | 5.4.5.1 Definition | This represents the relationship between RegistrationGroup and SuMCredentials. |
9014ba8dbedbe826dd149c7c9bc99edf | 188 002-2 | 5.4.5.2 Roles | Name Definition theRegistationGroupPrivateId Represents the Private Identification in SuMCredentials IOC associated to a Registration Group. ETSI ETSI TS 188 002-2 V3.1.1 (2009-12) 23 |
9014ba8dbedbe826dd149c7c9bc99edf | 188 002-2 | 5.4.6 relatedRegistrationGroupIMSPublicId | |
9014ba8dbedbe826dd149c7c9bc99edf | 188 002-2 | 5.4.6.1 Definition | This represents the relationship between RegistrationGroup and IMSPublicIdentification. |
9014ba8dbedbe826dd149c7c9bc99edf | 188 002-2 | 5.4.6.2 Roles | Name Definition theRegistationGroupIMSPublicId Represents the IMS Public Identification associated to a Registration Group. |
9014ba8dbedbe826dd149c7c9bc99edf | 188 002-2 | 5.4.7 relatedIndividualRegistrationPrivateId | |
9014ba8dbedbe826dd149c7c9bc99edf | 188 002-2 | 5.4.7.1 Definition | This represents the relationship between IndividualRegistration and SuMCredentials. |
9014ba8dbedbe826dd149c7c9bc99edf | 188 002-2 | 5.4.7.2 Roles | Name Definition theIndividualRegistationPrivateId Represents the Private Identification in SuMCredentials IOC associated to a line with an Individual Registration. |
9014ba8dbedbe826dd149c7c9bc99edf | 188 002-2 | 5.4.8 relatedAgcfServiceProfileIMSPublicId | |
9014ba8dbedbe826dd149c7c9bc99edf | 188 002-2 | 5.4.8.1 Definition | This represents the relationship between AgcfServiceProfile and IMSPublicIdentification. |
9014ba8dbedbe826dd149c7c9bc99edf | 188 002-2 | 5.4.8.2 Roles | Name Definition theAgcfServiceProfileIMSPublicId Represents the IMS Public Identification associated to the AgcfServiceProfile. |
9014ba8dbedbe826dd149c7c9bc99edf | 188 002-2 | 5.4.9 relatedAgcfDefaultCharacteristics | |
9014ba8dbedbe826dd149c7c9bc99edf | 188 002-2 | 5.4.9.1 Definition | This represents the relationship between AgcfServiceProfile and AgcfDefaultCharacteristics. |
9014ba8dbedbe826dd149c7c9bc99edf | 188 002-2 | 5.4.9.2 Roles | Name Definition theAgcfDefaultCharacteristics Represents the AgcfDefaultCharacteristics associated to the AgcfServiceProfile. |
9014ba8dbedbe826dd149c7c9bc99edf | 188 002-2 | 5.4.10 relatedAgcfApplicationCapabilities | |
9014ba8dbedbe826dd149c7c9bc99edf | 188 002-2 | 5.4.10.1 Definition | This represents the relationship between AgcfServiceProfile and AgcfApplicationCapabilities. ETSI ETSI TS 188 002-2 V3.1.1 (2009-12) 24 |
9014ba8dbedbe826dd149c7c9bc99edf | 188 002-2 | 5.4.10.2 Roles | Name Definition theAgcfApplicationCapabilities Represents the AgcfApplicationCapabilities associated to the AgcfServiceProfile. |
9014ba8dbedbe826dd149c7c9bc99edf | 188 002-2 | 5.5 Information attribute definitions | |
9014ba8dbedbe826dd149c7c9bc99edf | 188 002-2 | 5.5.1 Definition and legal values | Table 5.5.1.1 defines the attributes that are present in several IOCs of the present document. The attributes related to 3GPP IOCs are defined in TS 132.172 [7]. ETSI ETSI TS 188 002-2 V3.1.1 (2009-12) 25 Table 5.5.1.1: Attribute definition table Attribute Name Definition Legal Values (see note) agcfDefaultCharacterist... |
b6c9efb8f3afc1d10658973a2ac7c420 | 188 002-1 | 1 Scope | The purpose of the present document is the definition of the necessary requirements for the Subscription Management (SuM) which is paramount for the NGN service delivery within TISPAN NGN. The present document contains the specification of the requirements for the following: • An end-to-end information model to cover a... |
b6c9efb8f3afc1d10658973a2ac7c420 | 188 002-1 | 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 or version number) or non-specific. • For a specific reference, subsequent revisions do not apply. • For a n... |
b6c9efb8f3afc1d10658973a2ac7c420 | 188 002-1 | 3 Definitions, and abbreviations | |
b6c9efb8f3afc1d10658973a2ac7c420 | 188 002-1 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: offered service: service offered by the Service Provider to the market service profile: collection of service and user related data as defined in TS 129 228 [11] service provider: entity that offers services to subscribers NOTE: The ex... |
b6c9efb8f3afc1d10658973a2ac7c420 | 188 002-1 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: AS Application Server CLF Connectivity session Location and repository Function CPE Customer Premises equipment CRBT Color Ring Back Tone. DSL Digital Subscriber Line eTOM enhanced Telecom Operation Map GPRS General Packet Radio Service IMS IP... |
b6c9efb8f3afc1d10658973a2ac7c420 | 188 002-1 | 4 Subscription Management (SuM) description | |
b6c9efb8f3afc1d10658973a2ac7c420 | 188 002-1 | 4.1 SuM overview | Allowing service providers to deliver, control, monitor and bill services to their subscribers in a timely and correct manner, require the translation of each specific subscription into necessary/optional network data and their provisioning on the appropriate network functionalities such as UPSF, AS, CPE, etc. Subscrip... |
b6c9efb8f3afc1d10658973a2ac7c420 | 188 002-1 | 4.2 SuM and eTOM fulfilment process | Subscription Management (SuM) can be viewed as part of the eTOM fulfilment process, in particular the customer relationship management process, the service management and operations process and the resource management and operation processes. However, the first release of the present document focuses only on the servic... |
b6c9efb8f3afc1d10658973a2ac7c420 | 188 002-1 | 5 SuM value chain model | |
b6c9efb8f3afc1d10658973a2ac7c420 | 188 002-1 | 5.1 Introduction | The Subscription Management (SuM) value chain model concerns the definition of high level use-case in the context of Subscription Management (SuM), which allows the development of a broad overview. The high level use-case is depicted in figure 4. It is required to have a description for each use case within the present... |
b6c9efb8f3afc1d10658973a2ac7c420 | 188 002-1 | 5.2 Manage subscription use-cases | The manage subscription use-case is an abstract use-case. It includes all more concrete use-cases listed below: • Create subscription: This use-case allows the service provider to create a new subscription. • Delete subscription: This use-case allows the service provider to delete an existing subscription. • Update sub... |
b6c9efb8f3afc1d10658973a2ac7c420 | 188 002-1 | 5.3 Manage users use-cases | The manage users use-case is an abstract use-case. It includes the following concrete use-cases: • Create user: Allows the subscriber to add a new user to his subscription. • Delete user: Allows the subscriber to delete a user from his subscription. • Update user: Allows the subscriber to (re)configure a user. It may a... |
b6c9efb8f3afc1d10658973a2ac7c420 | 188 002-1 | 5.5 "Manage NGN SuM data" use-cases | The "manage NGN SuM data" is an abstract use-case which includes the following concrete use-case: • Install subscriber: Allows the installation of a new subscriber. • Update subscriber: Allows the (re)configuration of a subscriber. • Delete subscriber: Delete a subscriber. • Read subscriber: Get the information related... |
b6c9efb8f3afc1d10658973a2ac7c420 | 188 002-1 | 6 SuM high level requirements | |
b6c9efb8f3afc1d10658973a2ac7c420 | 188 002-1 | 6.1 Introduction | As described before, Subscription Management (SuM) is related to all the artefacts needed by service providers to provision their network with the data related to a specific subscription. Furthermore, these artefacts must allow subscribers to configure their services if they have configuration access rights. Subscripti... |
b6c9efb8f3afc1d10658973a2ac7c420 | 188 002-1 | 6.2 Requirements on information model | The purposes of specifying a SuM information model is to capture all the information needed for the management of a specific subscription. This information concerns network access identification and credential, user /subscriber identification, service identifications and credentials. Within this first release of the do... |
b6c9efb8f3afc1d10658973a2ac7c420 | 188 002-1 | 6.3 Requirements on functional architecture | The purpose of the SuM functional architecture is the design of the NOSIs needed for management of a specific subscriber, user, service profile and user services. The SuM functional architecture shall deliver the necessary NOSIs for the resource provisioning and service activation processes. R1) The SuM functional arch... |
b6c9efb8f3afc1d10658973a2ac7c420 | 188 002-1 | 6.4 Requirements on TISPAN NGN functional entities | The master NGN functional entities where subscription data are stored are the following: • UPSF: holds service-level user related information. • AS: contains SuM relevant data for value-added services. • CLF: contain user accesses network information. • NACF. • PDBF: contains user authentication data (user identity, li... |
b6c9efb8f3afc1d10658973a2ac7c420 | 188 002-1 | 6.5 Security requirements | R1) The SuM solution shall comply with specific local, national, and regional security regulations. R2) Subscription data shall be safeguarded against unapproved disclosure or usage. R3) Access to SuM data shall only be permitted in an authorized and secure manner. R4) Secure mechanisms shall be available for the trans... |
879cc01d34dc985b6a63a5ed38449474 | 188 001 | 1 Scope | The purpose of the present document is to specify a high level architecture and design principles for the NGN Management OSS Architecture Release 1. The NGN management Architecture specified in the present document is structured in three views: • The Business Requirements view: this presents the business concepts, stra... |
879cc01d34dc985b6a63a5ed38449474 | 188 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. • ... |
879cc01d34dc985b6a63a5ed38449474 | 188 001 | 3 Definitions and abbreviations | |
879cc01d34dc985b6a63a5ed38449474 | 188 001 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: interaction pattern: a well defined sequence of messages exchanged between a provider and a user NOTE: For example the ebXML business transaction activity Request/Confirm. IRP (Integration Reference Point): architectural concept that i... |
879cc01d34dc985b6a63a5ed38449474 | 188 001 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: 3GPP 3rd Generation Partnership Project ABE Aggregate Business Entity API Application Programme Interface CCV Common Communication Vehicle CM Configuration Management CMIP Common Management Information Protocol CN Core Network CORBA Common Obj... |
879cc01d34dc985b6a63a5ed38449474 | 188 001 | 4 Introduction to NGN OSS management views | The NGN Network Architecture [12] builds on 3GPP IP Multimedia Subsystem (IMS) specifications for part of its network architecture and extends them to cover the fixed network requirements. The specification of the NGN OSS Architecture should cover the management of this extended network and its services. The NGN OSS Ar... |
879cc01d34dc985b6a63a5ed38449474 | 188 001 | 5 Business requirements view | The business requirements for the NGN network encompass the following paradigms: • the Next Generation Network (NGN), as defined by TISPAN (ES 282 001 [12], which distinguishes service layer and transport layer. This new network must interact with legacy networks (PSTN, GSM, etc.); • new business and operational requir... |
879cc01d34dc985b6a63a5ed38449474 | 188 001 | 5.1 Overview of the ETSI TISPAN NGN Architecture | Figure 2 provides an overview of the NGN Architecture (ES 282 001 [12]). The network subsystems are divided into 2 layers (Service layer and Transport Layer). The NGN OSS Architecture (clause 6) reflects this division of NGN resources into two layers. Other networks Other subsystems Core IMS PSTN/ISDN Emulation subsyst... |
879cc01d34dc985b6a63a5ed38449474 | 188 001 | 5.2 NGN business and operational requirements | Business and operational requirements for NGN management are specified within different sources, amongst which: • OSS Vision, TR 188 004 [20]; • eTOM Business Process Framework (TMF GB921 series [14]; ITU-T Recommendation M.3050 series [1]); • OSS Requirements and Priorities, TS 188 003 (see bibliography); • OSS Servic... |
879cc01d34dc985b6a63a5ed38449474 | 188 001 | 5.2.1 NGN OSS vision | The "OSS Vision" document presents business, regulatory and operational requirements, utilizing the eTOM as reference business process framework, and referring to the TeleManagement Forum NGOSS (New Generation Operation Systems and Software) program as reference industry approach for development of OSSs. |
879cc01d34dc985b6a63a5ed38449474 | 188 001 | 5.2.2 eTOM business process framework | eTOM is a business process model or framework that has the objective of describing and classifying the business processes required for a Service Provider; it analyzes the processes to different levels of detail according to their significance and priority for the business. eTOM uses hierarchical decomposition to struct... |
879cc01d34dc985b6a63a5ed38449474 | 188 001 | 6 Functional/information view | The functional/information Architecture view describes the components, functions and information needed to fulfil the Business Requirements in order to provide the NGN OSS Services as defined in TS 188 002 (see bibliography). |
879cc01d34dc985b6a63a5ed38449474 | 188 001 | 6.1 Principles underlying the view | The NGN OSS functional/information view builds on the following principles: • The OASIS Service Oriented Architecture (SOA) [19]. NOTE: This does not rule out the import of non-SOA-based or "legacy" standards from 3GPP, TMF or other organizations. • The 3GPP Integration Reference Point (IRP) concept [3], [4], [5], [6],... |
879cc01d34dc985b6a63a5ed38449474 | 188 001 | 6.3 Entities composing the NGN OSS view | This clause introduces the definitions of the different entities used to describe the NGN OSS Functional/Information View and provides their formal definition with additional explanations. |
879cc01d34dc985b6a63a5ed38449474 | 188 001 | 6.3.1 Overview | The NGN OSS Service and the NGN OSS Service Interface are the main basic entities used in the description of the NGN OSS View. An NGN OSS Service Interface provides access to functionality for managing the NGN in a way that supports the eTOM operational processes. 16 ETSI ETSI TS 188 001 V1.2.1 (2006-03) NGN OSS Servic... |
879cc01d34dc985b6a63a5ed38449474 | 188 001 | 6.3.2 NGN OSS Service Interface | NGN OSS Service Interface (NGN OSS SI) (graphically depicted as a lollipop): a well defined grouping of related NGN OSS Operations and constant data which are necessary to deliver coherent business or system functionality. The NGN OSS Service Interface is: • The fundamental unit of standardization. • An aggregation of ... |
879cc01d34dc985b6a63a5ed38449474 | 188 001 | 6.3.3 NGN OSS Service Interface Consumer | NGN OSS Service Interface Consumer (NGN OSS SIC) (graphically depicted as a crescent): a well defined grouping of related NGN OSS Operations and constant data which represent the user/consumer of an NGN OSS Service Interface. NGN OSS Service Interface Consumer is: • The means through which an NGN OSS Service indicates ... |
879cc01d34dc985b6a63a5ed38449474 | 188 001 | 6.3.4 NGN OSS Service | NGN OSS Service (depicted as an ellipse): A behaviour or set of behaviours, made available through a profitable aggregation of NGN Service Interfaces, offered by one entity for use by others through their NGN OSS Service Interface Consumers; this usage is governed by a service description. The NGN OSS Services are: • C... |
879cc01d34dc985b6a63a5ed38449474 | 188 001 | 6.3.5 NGN OSS Operation | NGN OSS Operation (NGN OSS Op): a behaviour which is published as a member of an NGN OSS Service Interface or an NGN OSS Service Interface Consumer. NGN OSS Operation(s): • Is bound to a specific NGN OSS Service Interface or NGN OSS Service Interface Consumer. • Represents a published behaviour of the NGN OSS service e... |
879cc01d34dc985b6a63a5ed38449474 | 188 001 | 6.3.6 NGN OSS Service Interface Group | NGN OSS Service Interface Group (NGN OSS SIG): a grouping of NGN OSS Service Interfaces that belong together according to a given logic or context. NGN OSS Service Interface Group(s): • Are basically collections of NGN OSS Services Interfaces that have similar characteristics or business objectives. Possible examples o... |
879cc01d34dc985b6a63a5ed38449474 | 188 001 | 6.4 The NGN OSS Function/Information View Reference Model | Using the entities introduced in the previous clause, the NGN OSS Functional/Information View Reference Model (figure 5) can be presented as a collection of NGN OSS Services which provide groups of NGN OSS Operations that are exposed as NGN OSS Service Interfaces and that use the NGN OSS Service Interfaces of other NFN... |
879cc01d34dc985b6a63a5ed38449474 | 188 001 | 7 Implementation view | Essentially the NGN OSS implementation view is the transformation of the functional and information view into a implementation view as shown in figure 1. Note that constraints, and requirements, are placed on the implementation view covering cost, legacy, performance and preferences. The most important preferences are ... |
879cc01d34dc985b6a63a5ed38449474 | 188 001 | 7.1 Introduction to SOA implementation | A Service Oriented Architecture (SOA) is a software architecture involving loosely coupled, location independent services generally using the so-called "find-bind-execute" paradigm for the communication between SOA service providers, SOA service users and a SOA service registry. Any given service may assume a client or... |
879cc01d34dc985b6a63a5ed38449474 | 188 001 | 7.2 Implications of SOA implementation | TMF NGOSS specifications (one of the fundamental sources for developing the TISPAN NGN OSS Architecture) are based upon the use of the eTOM Business Process framework, the SID Information Model, and the NGOSS Technology Neutral Architecture. In particular, the TMF NGOSS Technology Neutral Architecture (TNA) (TMF 053), ... |
879cc01d34dc985b6a63a5ed38449474 | 188 001 | 7.3 Implementation View Reference Model | The NGN OSS architecture implementation view requires the use of a reference model. As illustrated in figure 7, at the highest level of abstraction, this reference model is composed of: • NGN OSS Basic Framework Services, providing the infrastructure necessary to support the distributed nature of the NGN OSS Architectu... |
879cc01d34dc985b6a63a5ed38449474 | 188 001 | 7.4 Role of Registry/Directories in SOA Implementation | This latter principle has very considerable impact on the architecture as it means that components must register themselves and that clients of these components use a "find-bind-execute model". This means that the interactions between components are established dynamically at run time unlike the traditional concept of ... |
879cc01d34dc985b6a63a5ed38449474 | 188 001 | 7.5 SOA Registry/Directory Organization | An important aspect of a SOA is that a Directory is needed to support the trading and registration services to support the "find" operation. These directories, an example being the UDDI directories used for Web Services, need to have a taxonomy or classification schema for organizing the registered web services. In thi... |
879cc01d34dc985b6a63a5ed38449474 | 188 001 | 8 Security of Management | The security of management aspects are transverse, they cover the three architecture views: Business Requirements, Functional/Information Architecture and Implementation. Detailed Security architecture implementation is for further study. 9 Linking Business, Functional/Information and Implementation Views The NGN OSS B... |
879cc01d34dc985b6a63a5ed38449474 | 188 001 | 9.1 Assumptions for linkage | For ETSI TISPAN, the following assumptions hold: • eTOM business requirements are expected to be valid for the NGN OSS, even if today's eTOM may need further elaboration of some business processes to cover NGN. • 3GPP management requirements, functional/information architecture and implementation views are a prime reso... |
879cc01d34dc985b6a63a5ed38449474 | 188 001 | 9.2 Route to convergence | There is a need to converge TMF NGOSS, ITU-T, 3GPP, and TMF MTNM and IPNM specifications. The proposed approach is that ETSI NGN OSS focuses on the definition of service-oriented, technology independent management interfaces for the OSS which is sufficiently decoupled from individual 3GPP, MTNM/IPNM and ITU-T network r... |
879cc01d34dc985b6a63a5ed38449474 | 188 001 | 10.3 Service Management (SM) Service Interface Group | The Service Management (SM) Service Interface Group includes those management functions dealing with Service development, management and operations. All management functions within the SM Service Interface Group will be "resource/technology independent" and will not have any knowledge of the underlying resources involv... |
879cc01d34dc985b6a63a5ed38449474 | 188 001 | 10.4 Resource Management (RM) Service Interface Group | While the Service Management (SM) Service Interface Group has the responsibility for managing the service lifecycle and the delivery and assurance of service instances independently from the type of underlying resources, the Resource Management (RM) Service Interface Group is responsible for the management of the logic... |
879cc01d34dc985b6a63a5ed38449474 | 188 001 | 10.4.1 Service Resource Management (SRM) Service Interface Group | While the Service Management (SM) Service Interface Group has the responsibility for managing the service lifecycle and the delivery and assurance of service instances, the Service Resource Management (SRM) Service Interface Group is responsible for the management of the implementation and logical infrastructure resour... |
879cc01d34dc985b6a63a5ed38449474 | 188 001 | 10.4.2 Transport Resource Management (TRM) Service Interface Group | The Transport Resource Management (TRM) Service Interface Group is responsible for the realization of the required connectivity and for the configuration of other provisioned service related aspects in the NGN. This includes functions such as selection of network technologies, routing, network resource management, inve... |
879cc01d34dc985b6a63a5ed38449474 | 188 001 | 10.5 Managed NGN Resources Service Interface Group | Managed Resource Service Interface Groups group the functions provided by Managed Elements present in the network and used by the Resource Management Service Interface Group. Their identification is for further study. |
879cc01d34dc985b6a63a5ed38449474 | 188 001 | 11 NGN OSS Service Interfaces | |
879cc01d34dc985b6a63a5ed38449474 | 188 001 | 11.1 Introduction to TISPAN NGN OSS Service Interfaces | The previous clause has identified several NGN OSS Service Interface Groups, each grouping a number of NGN OSS Service Interfaces. The next step, for each NGN OSS Service Interface Group, identifies and further decomposes these NGN OSS Service Interface Groups in order to determine those NGN OSS Service Interfaces that... |
f1526bf206ce07c31451b6b9b1049088 | 186 022-3 | 1 Scope | The present document specifies the Abstract Test Suite (ATS) and partial Protocol Implementation eXtra Information for Testing (PIXIT) proforma based on the Test Suite Structure and Test purposes defined in TS 186 022-2 [2]. The TSS&TP have been developed to test the Terminating Identification Presentation (TIP) and Te... |
f1526bf206ce07c31451b6b9b1049088 | 186 022-3 | 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... |
f1526bf206ce07c31451b6b9b1049088 | 186 022-3 | 2.1 Normative references | The following referenced documents are necessary for the application of the present document. [1] ETSI TS 124 615 (V8.3.0): "Digital cellular telecommunications system (Phase 2+); Universal Mobile Telecommunications System (UMTS); LTE; Communication Waiting (CW) using IP Multimedia (IM) Core Network (CN) subsystem; Pro... |
f1526bf206ce07c31451b6b9b1049088 | 186 022-3 | 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. Not applicable. |
f1526bf206ce07c31451b6b9b1049088 | 186 022-3 | 3 Definitions and abbreviations | |
f1526bf206ce07c31451b6b9b1049088 | 186 022-3 | 3.1 Definitions | For the purposes of the present document, the terms and definitions given in ISO/IEC 9646-7 [6], TS 102 587-2 [9] and TS 102 790-3 [3] apply. |
f1526bf206ce07c31451b6b9b1049088 | 186 022-3 | 3.2 Abbreviations | For the purposes of the present document, the abbreviations given in ISO/IEC 9646-1 [5], ISO/IEC 9646-7 [6], TS 102 790-3 [3] and TS 124 615 [1] apply. |
f1526bf206ce07c31451b6b9b1049088 | 186 022-3 | 4 Abstract Test Method (ATM) | For the purposes of the present document, the ATM described in clause 4 of TS 102 790-3 [3] applies with following additions. |
f1526bf206ce07c31451b6b9b1049088 | 186 022-3 | 4.1 Configurations for testing UE | The Gm interface is located between SUT (UE) and the IMS. ETSI ETSI TS 186 022-3 V3.1.1 (2012-01) 7 SUT TS UE IMS Gm Figure 1: Test configuration CF_1GmUE The ISC interface provides an access to the AP. SUT IMS AS ISC TS Figure 2: Test configuration CF_1ISC |
f1526bf206ce07c31451b6b9b1049088 | 186 022-3 | 5 The ATS development process | |
f1526bf206ce07c31451b6b9b1049088 | 186 022-3 | 5.1 Requirements and Test Purposes | For each test purpose there is a table defined in clause 5 of TS 186 022-2 [2]. The requirements applicable to this TP are given by a reference to TS 124 615 [1]. There are no explicit formulations of requirements. |
f1526bf206ce07c31451b6b9b1049088 | 186 022-3 | 5.2 ATS structure | |
f1526bf206ce07c31451b6b9b1049088 | 186 022-3 | 5.2.1 Test case grouping | The ATS structure defined in Table 1 is based on the structuring of Test Purposes in clause 4 of TS 186 022-2 [2]. The group names in column 2 of Table 1 are those assigned in the ATS; they are based on the names provided in clause 4 of TS 186 022-2 [2], but use the naming conventions defined for the ATS (see clause 5.... |
f1526bf206ce07c31451b6b9b1049088 | 186 022-3 | 5.2.2 Test case identifiers | The test case names are built up according to the following scheme: "<TC>"_"<Group index>"_"<TC number>" where: a) double quotes (") are used to enclose literal strings; b) <Group path index> is the group index in Table 1 (which uniquely identifies the path of groups/subgroups); ETSI ETSI TS 186 022-3 V3.1.1 (2012-01) ... |
f1526bf206ce07c31451b6b9b1049088 | 186 022-3 | 5.3 ATS specification framework |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.