hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
41869e024dc6b21d4da074944c39ada9 | 101 853 | 7.5.1.3 Margin on receiver sensitivity | The link (or fade) margin on receiver sensitivity for P-MP system ( PMP M ) is the margin considered during the planning phase of the system development. In the interference analysis there are two ways to consider this parameter. 1) The power margins used in the analysis are equal to those used during the cell planning... |
41869e024dc6b21d4da074944c39ada9 | 101 853 | 7.5.1.4 Cell radius | The cell radius of P-MP system defines the cell area where the interference (for a subset of interference classes) will be evaluated or the source of interference will be placed. Therefore, the maximum radius, once given the system parameters and a reasonable margin, shall be considered. ETSI ETSI TR 101 853 V1.1.1 (20... |
41869e024dc6b21d4da074944c39ada9 | 101 853 | 7.5.1.5 Antenna pattern and gain | The antenna parameters are very important in the evaluation of the interference. If the actual values of antenna pattern are not available it is possible to use the masks reported in the relevant ETSI standard for P-MP antennas. Indeed, for the antenna gain is necessary to have the actual values. |
41869e024dc6b21d4da074944c39ada9 | 101 853 | 7.5.2 Evaluation parameters | |
41869e024dc6b21d4da074944c39ada9 | 101 853 | 7.5.2.1 Class B1 evaluation parameters | In the case of CRS that interferes the P-P system it is possible to evaluate using equation (28) the minimum distances (between CRS and P-P) requested to avoid any interference effect for different angle decoupling. The smaller are the distances the better is the degree of co-existence. |
41869e024dc6b21d4da074944c39ada9 | 101 853 | 7.5.2.2 Class B2 evaluation parameters | In the case of P-P system that interferes the CRS of P-MP system it is possible to evaluate using equation (32) the minimum distances (between CRS and P-P) requested to avoid any interference effect for different angle decoupling. The smaller are the distances the better is the degree of co-existence. |
41869e024dc6b21d4da074944c39ada9 | 101 853 | 7.5.2.3 Class B3 evaluation parameters | In the case where the sources of interference (toward P-P system) are the TS of P-MP system equations (36) and (37) provide us which are the TS that, alone, generate a smaller C/I ratio on P-P system, once provided the geometry of P-P and CRS. But this is the actual behaviour if the P-MP system is TDMA or FDMA; while f... |
41869e024dc6b21d4da074944c39ada9 | 101 853 | 7.5.2.4 Class B4 evaluation parameters | In the case of P-P system that interferes the TS of a P-MP system equation (40) provides which are the TS that are interfered (C/I ratio less than ( ) min I C ), for a given geometry of P-P and CRS, in terms of percentage of cell area (%KO). Obviously, for a given geometry, the smaller is the percentage the better is t... |
41869e024dc6b21d4da074944c39ada9 | 101 853 | 8.1 Considerations related to a specific class of interference | In this clause are reported some qualitative considerations on the degree of co-existence between two systems when one particular kind of interference class (defined in clause 5) is taken into account. In particular, the problems of site sharing (the two systems use the same mast for CRS's), near site placing (the two ... |
41869e024dc6b21d4da074944c39ada9 | 101 853 | 8.1.2 Class A2 considerations | This class regards the interference from a TS of the interfering system to the CRS of the useful system. Due to the symmetry with class A1 (already pointed out in clause 6) the same considerations of clause 8.1.1 apply also to class A2. |
41869e024dc6b21d4da074944c39ada9 | 101 853 | 8.1.3 Class A3 considerations | This class regards the interference from the CRS of the interfering system to the CRS of the useful system. In this case a minimum distance between the two CRS's is requested, see equation (16), thus no site sharing is possible. Moreover, in order to reduce the distance requested to a few hundreds meters (low degree of... |
41869e024dc6b21d4da074944c39ada9 | 101 853 | 8.1.4 Class A4 considerations | This class regards the interference from a TS of the interfering system to a TS of the useful system. In this case the site sharing is possible but does not relax the problem of co-existence. In order to control the mutual interference between TS's is necessary to provide a useful guard band that reduces the minimum di... |
41869e024dc6b21d4da074944c39ada9 | 101 853 | 8.2 General rules to accomplish co-existence | In this clause some general rules (that are not directly associated to a particular class) to accomplish co-existence are given. In particular, one clause regards the rules on system's parameters while the other is related to general deployment rules that could facilitate the co-existence on the same area with the mini... |
41869e024dc6b21d4da074944c39ada9 | 101 853 | 8.2.2 Deployment rules | A useful deployment rule to facilitate the co-existence of two FDD P-MP systems operating on the same area it is to assign one of the two paired sub bands (foreseen in many ERC recommendations) for the downlink and the other for uplink. In this way the only interference classes to be considered are A1 and A2 (see claus... |
41869e024dc6b21d4da074944c39ada9 | 101 853 | 8.3 Parameters not available in EN's | In clause 6 is reported a list of parameters (necessary for the interference analysis) that are labelled as "not available in the EN's", in the sense that only some sort of limits are available in EN's. This labelling reflect the necessity (see annexes A and B) to have tighter values than the limits usually reported in... |
41869e024dc6b21d4da074944c39ada9 | 101 853 | 9.1 Considerations related to a specific class of interference | In this clause are reported some qualitative considerations on the degree of co-existence between a P-MP and a P-P systems when only one kind of interference class (classes B defined in clause 5) is taken into account. In particular, the problems of site sharing (the two systems use the same mast), the distance and ang... |
41869e024dc6b21d4da074944c39ada9 | 101 853 | 9.1.1 Class B1 considerations | This class regards the interference from the CRS of the P-MP system to the P-P system, thus it involves only two sites and it can be considered as P-P/P-P co-existence (since it requires distance and co-ordination area). No site sharing is possible and between CRS and P-P sites a minimum distance is required. This dist... |
41869e024dc6b21d4da074944c39ada9 | 101 853 | 9.1.2 Class B2 considerations | This class regards the interference from the P-P system to the CRS of the P-MP system. Due to the geometric symmetry with class B1 the same considerations of clause 9.1.1 apply also to class B2. Thus, it is necessary a minimum distance between CRS and P-P site to avoid interference. |
41869e024dc6b21d4da074944c39ada9 | 101 853 | 9.1.3 Class B3 considerations | This class regards the interference from the TS of the P-MP system to the P-P system. Site sharing is the worst situation (see annex B) and requires the highest frequency separation. In general, even without site sharing, if no sufficient frequency decoupling is provided and if the P-P link crosses the P-MP cell area t... |
41869e024dc6b21d4da074944c39ada9 | 101 853 | 9.1.4 Class B4 considerations | This class regards the interference from the P-P system to the TS of the P-MP system. Due to the geometric symmetry with class B3 the same considerations of clause 9.1.3 apply also to class B4; i.e. this interference situation requires a wide guard band in order to avoid the interference on P-MP TS placed on the P-P li... |
41869e024dc6b21d4da074944c39ada9 | 101 853 | 9.2 General rules to accomplish co-existence | In this clause some general rules (that are not directly associated to a particular class) to accomplish co-existence are given. In particular, one clause regards the rules on system's parameters while the other is related to general deployment rules that could facilitate the co-existence on the same area with the mini... |
41869e024dc6b21d4da074944c39ada9 | 101 853 | 9.2.1 Rules on system's parameters | The following rules can be easily derived by methodologies described in clause 7. • The greater is the NFD the smaller is the requested guard band or the minimum distance. This rule obviously applies to all classes of interference. Thus, the NFD values (for both P-MP and P-P systems) derived from EN's must be as close ... |
41869e024dc6b21d4da074944c39ada9 | 101 853 | 9.2.2 Deployment rules | Two different deployment scenarios can be considered: the first when only one P-P site is within the deployment area of P-MP system (urban area), the second when the entire P-P link (both sites) is within the deployment area of P-MP system. The two following rules hold for the two different scenarios. 1) One P-P site: ... |
41869e024dc6b21d4da074944c39ada9 | 101 853 | 9.3 Parameters not available in EN's | The same considerations of clause 8.3 also apply for P-MP and P-P co-existence. ETSI ETSI TR 101 853 V1.1.1 (2000-10) 39 Annex A: Examples of P-MP vs P-MP co-existence analysis In this clause some examples of co-existence analysis between two P-MP systems with different characteristics (channel spacing, access method, ... |
325ecee8875dbf3fb781baa13aad5b26 | 101 655 | 1 Scope | The present document presents a summary of experiences collected from the use of automatic interoperability testing in a real-world interoperability testing event at the RCS/VoLTE interoperability event held in Kranj (Slovenia) from 1st to 12th October, 2012. More specifically it addresses the use of test systems which... |
325ecee8875dbf3fb781baa13aad5b26 | 101 655 | 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... |
325ecee8875dbf3fb781baa13aad5b26 | 101 655 | 2.1 Normative references | The following referenced documents are necessary for the application of the present document. Not applicable. |
325ecee8875dbf3fb781baa13aad5b26 | 101 655 | 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 EG 202 810: "Methods for Testing and Specification (MTS); Automated Interoperability Testing; Methodology and Framework". [i.2] ETSI TS 124 229 (... |
325ecee8875dbf3fb781baa13aad5b26 | 101 655 | 3 Abbreviations | For the purposes of the present document, the abbreviations given in TS 124 229 [i.2] and the following apply: AS Application Server CSCF Call Session Control Function DNS Domain Name Server ENUM E.164 NUmber Mapping EPC Evolved Packet Core EUT Equipment Under Test GSM Global System for Mobile Communications GSMA GSM A... |
325ecee8875dbf3fb781baa13aad5b26 | 101 655 | 4 Automated interoperability testing | Interoperability is a key factor in the widespread commercial success of any given technology in the telecommunication sector. Interoperability fosters diversity as well as competition in a market. Vendors can achieve interoperability of their products only if they agree and implement a common set of open standards. Ho... |
325ecee8875dbf3fb781baa13aad5b26 | 101 655 | 4.1 ETSI Plugtests | Plugtests are interoperability testing events that are organized by ETSI to offer its members as well as non-members a means to assess interoperability between systems and the maturity of standards. These events are attended by vendors that implement systems based on standards and depending on the event also by observe... |
325ecee8875dbf3fb781baa13aad5b26 | 101 655 | 5 ETSI/GSMA/MSF RCS/VoLTE Plugtest Event | |
325ecee8875dbf3fb781baa13aad5b26 | 101 655 | 5.1 IMS core network NNI interoperability testing | The Internet Protocol (IP) Multimedia Subsystem (IMS) TS 124 229 [i.2] is an architectural framework for delivering IP multimedia to fixed as well as mobile users. It was originally designed by the wireless standards body 3rd Generation Partnership Project (3GPP). It is a major step in the evolution of telecommunicatio... |
325ecee8875dbf3fb781baa13aad5b26 | 101 655 | 5.2 Event Summary | The RCS/VoLTE interoperability event was held in Kranj, Slovenia from October 1st to 12th 2012 at the Sintesio laboratory. See the complete summary of the whole event in the whitepaper "RCS VoLTE Interoperability Event 2012; Multivendor testing in global RCS/VoLTE Networks" [i.15]. The planned main focus was the assess... |
325ecee8875dbf3fb781baa13aad5b26 | 101 655 | 5.3 IMS Interoperability Test Automation | This clause discusses the use of automated testing in the context of the RCS/VoLTE interoperability test event. In case of IMS core network testing the operation of IMS user equipment is difficult to achieve since their interfaces are generally graphical and proprietary. In order to automate completely test execution, ... |
325ecee8875dbf3fb781baa13aad5b26 | 101 655 | 5.3.1 IMS Interoperability Test Tool Implementation | For the RCS/VoLTE interoperability test event ETSI implemented a test system based on TTCN-3 ES 201 873-1 [i.6] which is the test automation language of choice at ETSI. Use of TTCN-3 has many benefits including independence from the technology to be tested, independence from a particular testing tool, abstraction, and ... |
325ecee8875dbf3fb781baa13aad5b26 | 101 655 | 5.3.2 Use of the Test Tool | Trace captures of manual interoperability test executions were recorded independently in parallel test sessions. For the offline analysis of these trace captures two IMS interoperability test tool instances were used in parallel. Each test tool instance was first configured with IP address and port information of all p... |
325ecee8875dbf3fb781baa13aad5b26 | 101 655 | 5.3.3 Event Feedback on Automated Interoperability Test Tool | In general, the use of the IMS interoperability test tool was a great success. A comparison with the time and effort spent on interoperability trace analysis during earlier IMS interoperability events shows a reduction of 50 % in time. This reduction has been reached by applying automated trace analysis through the exe... |
5334619ff08f6f07368a2df9311244eb | 101 651 | 1 Scope | The present document provides information on the electromagnetic environmental conditions encountered where telecommunications equipment is installed and is a compilation of data concerning electromagnetic environmental conditions. In the present document only locations for equipment that are in the telecommunication n... |
5334619ff08f6f07368a2df9311244eb | 101 651 | 2 References | |
5334619ff08f6f07368a2df9311244eb | 101 651 | 2.1 Normative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the reference document (including any amendments) applies. Referenced documents which ar... |
5334619ff08f6f07368a2df9311244eb | 101 651 | 2.2 Informative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the reference document (including any amendments) applies. NOTE: While any hyperlinks in... |
5334619ff08f6f07368a2df9311244eb | 101 651 | 3 Definitions and abbreviations | |
5334619ff08f6f07368a2df9311244eb | 101 651 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: NOTE: The definitions taken from the IEC Publication No. 60050 (161) [i.7] have reference in parentheses. Audio (low) Frequency (AF): frequency interval from 0 Hz to 20 kHz NOTE: It may sometimes be convenient to extend the use of this... |
5334619ff08f6f07368a2df9311244eb | 101 651 | 3.2 Abbreviations | For the purposes of the present document the following abbreviations apply: AC Alternating Current ASD Adjustable Speed Drive CT Cordless Telephony CT-2 Cordless Telephone, second generation DC Direct Current DCS Digital Cellular System DECT Digital Enhanced Cordless Telecommunications EMC Electro-Magnetic Compatibilit... |
5334619ff08f6f07368a2df9311244eb | 101 651 | 4 Application area | The present document applies to telecommunication equipment installed and controlled by the network operator which is installed in telecommunications centres, outdoor locations and customer's premises. It does not make references to equipment dependent details. |
5334619ff08f6f07368a2df9311244eb | 101 651 | 5 Characteristics of environments | |
5334619ff08f6f07368a2df9311244eb | 101 651 | 5.1 Telecommunication and Data centres | |
5334619ff08f6f07368a2df9311244eb | 101 651 | 5.1.0 General | The internal electrical power distribution is a 48 V DC nominal (alternatively 60 V DC) (according to ETSI EN 300 132-2 [i.2]) and a 230 V/400 V AC nominal 50 Hz (according to ETSI ETS 300 132-1 [i.1]). In data centres the power distribution can be 365 V DC ± 15 V. It is assumed that switching of loads on the DC supply... |
5334619ff08f6f07368a2df9311244eb | 101 651 | 5.1.1 Class 1 - major telecommunication and data centres | This environmental class applies to major telecommunication centres in dedicated locations controlled by the network operator. These would typically be located in urban areas. The telecommunication centre has its own electricity power transformed from the public distribution network. The AC power distribution inside th... |
5334619ff08f6f07368a2df9311244eb | 101 651 | 5.1.2 Class 2 - minor telecommunication and data centres | This environmental class applies to telecommunication centres in dedicated locations controlled by the network operator. These would typically be located in rural areas serving the local community, and may often be unmanned. The telecommunication centre may draw its electrical power from the public supply network eithe... |
5334619ff08f6f07368a2df9311244eb | 101 651 | 5.2 Class 3 - outdoor locations | This environmental class applies to an unattended telecommunications site such as street furniture, telephone boxes, repeaters and amplifiers on trunk cables, or to concentrators and cable distribution boxes. This environmental class may apply also to equipment buried below ground level. Repeaters on submarine cables a... |
5334619ff08f6f07368a2df9311244eb | 101 651 | 5.3 Class 4 - customers' premises | This environmental class (location) encompasses the locations that have the attributes defined in clause 6, table 1. ETSI ETSI TR 101 651 V2.1.1 (2016-01) 10 As a first approach to a quantitative characteristic an attempt has been made to fit the "disturbance levels" specified by IEC/TR 61000-2-5 [i.6] into tables 2 to... |
5334619ff08f6f07368a2df9311244eb | 101 651 | 6 Attributes of customers' premises | Table 1 Media Attributes Radiated: - no amateur radio closer than 20 m; - no broadcast transmitter closer than 1 km; - paging and portable communication systems; - high concentration of ITE; - possible presence of diathermy therapy equipment; - possible proximity of local substation; - possible presence of audio/hearin... |
5334619ff08f6f07368a2df9311244eb | 101 651 | 7 Notation to tables 2 to 7 | In tables 2 to 7, the following notation has been used: Correlated parameters: correlated parameter values are arranged vertically and separated by ";" e.g.: A; B; C; ... a; b; c; ... Functional relations: functional relations are always piecemeal linear and defined by their break-points. A discontinuity where a parame... |
5334619ff08f6f07368a2df9311244eb | 101 651 | 8 Characteristic severities of environmental parameters | In tables 2 to 7, the characteristic severities and other characteristics of the relevant environmental parameters are stated for the environmental class for telecommunication network equipment. It is often not feasible to model the disturbances/parameters in every detail. For instance the temporal evolution of transie... |
a6b8f0778f2cbac10235066e366e8034 | 101 648 | 1 Scope | The present document provides guidelines for the definition of additional Managed Object Classes, the use of existing Managed Object Class definitions and the inclusion of these objects in existing inheritance and containment hierarchies. The present document: • Provides general rules for defining Managed Objects. • Pr... |
a6b8f0778f2cbac10235066e366e8034 | 101 648 | 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, edition number, version number, etc.) or non-specific. • For a specific reference, subsequent revisions do not apply. • Fo... |
a6b8f0778f2cbac10235066e366e8034 | 101 648 | 3 Definitions and abbreviations | |
a6b8f0778f2cbac10235066e366e8034 | 101 648 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: standards: this generic term is used in the present document to refer to ITU-R Recommendations, ETSI ETSs ENs and ETRs, ECMA TRs, ISO/IEC standards and EWOS TRs. |
a6b8f0778f2cbac10235066e366e8034 | 101 648 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: ASN.1 Abstract Syntax Notation One CMIP Common Management Information Protocol CMIS Common Management Information Service DMI Definition of Management Information ECMA European Computer Manufacturers Association E/R Entity-Relationship ETR ETS... |
a6b8f0778f2cbac10235066e366e8034 | 101 648 | 4 Purpose and Structure of Modelling Guidelines | The objective of the present document is to provide guidance to those ETSI Working Groups producing TMN Management Information Models (MIM). It aims to: • enable models developed by different groups to co-exist; • assist in producing consistency across models developed by different groups. The use of the guidelines is ... |
a6b8f0778f2cbac10235066e366e8034 | 101 648 | 5 Pre-Information Modelling Work | |
a6b8f0778f2cbac10235066e366e8034 | 101 648 | 5.1 Introduction | The development of Management Information Models is just one part of the activities involved in the definition and development of TMNs. There are several models of software system (waterfall, spiral) which distinguish between different activities. There is a consensus that eliciting and analysis of the needs and constr... |
a6b8f0778f2cbac10235066e366e8034 | 101 648 | 5.2 M.3020 TMN Interface Definition Methodology | |
a6b8f0778f2cbac10235066e366e8034 | 101 648 | 5.2.1 General | The TMN interface specification methodology is defined in ITU-T Recommendation M.3020 [2]. This Recommendation describes the process of deriving TMN interface specifications from TMN user requirements. The process is divided into a number of steps. User requirements are expressed as management services, which are decom... |
a6b8f0778f2cbac10235066e366e8034 | 101 648 | 5.2.2 The definition process | |
a6b8f0778f2cbac10235066e366e8034 | 101 648 | 5.2.2.1 Tasks, information and relationships | Several tasks are linked to form the TMN interface specification process, as defined in ITU-T Recommendation M.3020 [2]. These tasks are defined as follows (excluding protocol tasks): • describe TMN management services; • describe TMN management context; ETSI TR 101 648 V1.2.1 (1999-02) 10 • perform information modelli... |
a6b8f0778f2cbac10235066e366e8034 | 101 648 | 5.2.2.2 Describe TMN management services task | This task is concerned with identifying the management activities to be supported by the TMN. For each activity the management goals and examples of the benefits to TMN users from these goals are identified. |
a6b8f0778f2cbac10235066e366e8034 | 101 648 | 5.2.2.3 Describe TMN management context task | This task is concerned with identifying the roles, resources and functions associated with each management activity. Relationships are also specified, in the form of scenarios. |
a6b8f0778f2cbac10235066e366e8034 | 101 648 | 5.2.2.4 Perform information modelling task | This task is concerned with identifying existing (generic and technology-specific) and new object classes which will support the management activities identified earlier in the process. |
a6b8f0778f2cbac10235066e366e8034 | 101 648 | 5.2.2.5 Consolidate available information task | This task is concerned with ensuring that each and every management function is supported by one or more object classes. This may require the previous two tasks to be repeated iteratively until the set of object classes is satisfactory. |
a6b8f0778f2cbac10235066e366e8034 | 101 648 | 5.2.2.6 Define management information schema task | This task is concerned with defining the information model in terms of the managing system view of the managed system. In particular, it identifies the containment (naming) relationships for the object classes. The output of this task is a complete specification of the information exchange aspects of a TMN interface. E... |
a6b8f0778f2cbac10235066e366e8034 | 101 648 | 5.3 The Ensemble - a specification framework | |
a6b8f0778f2cbac10235066e366e8034 | 101 648 | 5.3.1 General | The Ensemble concept was developed by the Network Management Forum (NMF) "[…] to enable management system specifiers to define clearly which management standards are appropriate to their problems and how they are to be used". In other words, an Ensemble is a complete specification of a management problem and its soluti... |
a6b8f0778f2cbac10235066e366e8034 | 101 648 | 5.3.2 Ensemble structure | The basic structure of an Ensemble is made up of four main sections, which may be further enhanced and extended by the specifier: Introduction, containing general header information, a brief description of the Ensemble, its scope and any relationships to other Ensembles. ETSI TR 101 648 V1.2.1 (1999-02) 12 Management c... |
a6b8f0778f2cbac10235066e366e8034 | 101 648 | 5.3.2.1 Management context | |
a6b8f0778f2cbac10235066e366e8034 | 101 648 | 5.3.2.1.1 Management view and level of abstraction | The management view and level of abstraction may be defined in general terms using the TMN LLA ITU-T Recommendation M.3010 [13] and the OSI systems management functional areas ITU-T Recommendation X.701 [5]. The layers of the TMN LLA can be placed on one axis of a table, and the functional areas on the other axis. This... |
a6b8f0778f2cbac10235066e366e8034 | 101 648 | 5.3.2.1.2 Resources | The resources are those entities, physical or logical, which are to be managed. Only those resources which are relevant to the Ensemble are described. The descriptions must be sufficient to enable the specifier to identify appropriate managed object classes and their relationships. The greater the detail available, the... |
a6b8f0778f2cbac10235066e366e8034 | 101 648 | 5.3.2.1.3 Functions | The management functions are defined at three levels ITU-T Recommendation M.3020 [2]: • Management Services (MSs). • Management Function Sets (MFSs). • Management Functions (MFs). These levels provide a convenient means of categorizing and decomposing Ensemble functionality. The MFs themselves map directly to CMIS serv... |
a6b8f0778f2cbac10235066e366e8034 | 101 648 | 5.3.2.2 Information model | Information model specification is addressed in clause 6 of the present document. |
a6b8f0778f2cbac10235066e366e8034 | 101 648 | 5.3.2.3 Scenarios | Scenarios define the dynamic aspects of the Ensemble specification, showing how the managed object classes are used to support the functions defined in the management context. All the scenarios relevant to the Ensemble must be defined, all functions must map to a scenario. Scenarios are defined using message flow diagr... |
a6b8f0778f2cbac10235066e366e8034 | 101 648 | 5.4 ODP based approach (ITU-T G.851-1) - Methodology overview | |
a6b8f0778f2cbac10235066e366e8034 | 101 648 | 5.4.1 Introduction | From a network management point of view, the RM-ODP (Reference Model for Open Distributed Processing) provides an object oriented framework (for distributed management systems) that allows user requirements for each management application (for example configuration management), the information (or data) related to the ... |
a6b8f0778f2cbac10235066e366e8034 | 101 648 | 5.4.2 RM-ODP viewpoint descriptions | Complete descriptions of the RM-ODP viewpoints can be found in the references listed in clause 2. A brief description of RM-ODP viewpoints follows: • Enterprise viewpoint: A viewpoint on an ODP system and its environment that focuses on the purpose, scope and policies of that system. An enterprise specification enables... |
a6b8f0778f2cbac10235066e366e8034 | 101 648 | 5.4.3 Using RM-ODP viewpoints in a specification design methodology | Although the reference model for open distributed processing provides an approach to modelling (i.e. the RM-ODP viewpoints), it does not provide a prescriptive methodology that can be followed in developing a system. This subclause introduces the methodology, using the RM-ODP viewpoints, for use in the standardization ... |
a6b8f0778f2cbac10235066e366e8034 | 101 648 | 5.5 Additional Information | This subclause collects some advice which augments the methodologies described above. |
a6b8f0778f2cbac10235066e366e8034 | 101 648 | 5.5.1 Representation of structure | Rather than trying to represent all aspects of the structure of the managed resources, strive for the simplest representation of the structure which just meets the management requirements. Use attributes within a single object to model parts of resource structure provided that: • they are intuitively passive data rathe... |
a6b8f0778f2cbac10235066e366e8034 | 101 648 | 5.5.2 Goals of the pre-information modelling work | In summary, without the expenditure of an enormous effort, requirements should be: • unambiguous; • stated in a structured format; ETSI TR 101 648 V1.2.1 (1999-02) 17 • clear and accessible to a non-expert reader; and • non overlapping. It should be possible to trace through from the requirements to the solution (manag... |
a6b8f0778f2cbac10235066e366e8034 | 101 648 | 5.5.3 Reference material | Additional information supporting the definition of management requirements and information can be found at the EURESCOM Website called E-MOL ([WWW]: http://www.eurescom.de/~public-web-deliverables/p600-series/P609/emolgate.htm). This site contains repositories of information likely to be useful to people defining info... |
a6b8f0778f2cbac10235066e366e8034 | 101 648 | 6 Principles for the application of GDMO | |
a6b8f0778f2cbac10235066e366e8034 | 101 648 | 6.1 Introduction | The preceding clause showed only the first step of the process solving a particular TMN problem. In the second step, a formal or semi-formal notation must be applied to create the entities of the information model describing a TMN system. This clause provides guidelines on how to create object classes using the GDMO sy... |
a6b8f0778f2cbac10235066e366e8034 | 101 648 | 6.2 Use of Attributes | |
a6b8f0778f2cbac10235066e366e8034 | 101 648 | 6.2.1 Value Set Specification for Attributes | In general only the basic ASN.1 Type should be specified in an attribute template using ATTRIBUTE SYNTAX. Do not use subtyping or PERMITTED VALUES syntax. The basic type of an attribute is fixed under inheritance and can never change. Required Values are those values that must be fully supported by an instantiated mana... |
a6b8f0778f2cbac10235066e366e8034 | 101 648 | 6.2.2 Specifying Required, Permitted and Supported Values | The permitted and required values sets may be included in the specification of the managed object class when the attribute is inserted into that class, or when the attribute is inherited by a subclass. These sets could be further modified (subject to the same rules) in an implementation agreement. This option could be ... |
a6b8f0778f2cbac10235066e366e8034 | 101 648 | 6.2.3 Guidelines for Attribute-Value Set Selection | When selecting the basic type (as defined above) for an attribute, choose the ASN.1 type that includes all values that could possibly fit within the semantics of the attribute. Specify this basic type in the actual definition of the attribute. If the attribute is to be used in several different managed object classes w... |
a6b8f0778f2cbac10235066e366e8034 | 101 648 | 6.2.4 General Attribute Guidelines | When it is necessary to specify attributes in objects that are being developed in other experts groups, the group requesting the attribute must specify default values and behaviour. Regional options should be contained in ITU objects as conditional packages so that they are available to other regions. Group Attributes ... |
a6b8f0778f2cbac10235066e366e8034 | 101 648 | 6.3 Use of Inheritance | |
a6b8f0778f2cbac10235066e366e8034 | 101 648 | 6.3.1 General Inheritance Guidelines | Inheritance Rules The inheritance rules defined in the present document shall not conflict with those specified in ITU-T Recommendation X.721 [7] Management Information Model and ITU-T Recommendation X.722 [8] Guidelines for the Definition of Managed Objects. Conditional Packages are always inherited from the superclas... |
a6b8f0778f2cbac10235066e366e8034 | 101 648 | 6.3.2 Principles and Guidelines for Instantiable Classes | Inheritance Rules Specify a class as instantiable whenever any of the following conditions are met: • The class models one or more aspects of a resource that need to be managed. • The class is necessary to support management functions such as event logs and event reporting filters. Instantiable object classes may be cr... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.