hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
a6b8f0778f2cbac10235066e366e8034 | 101 648 | 6.3.3 Principles and Guidelines for Uninstantiable Classes | Generate an uninstantiable class to group characteristics (attributes, operations and notifications) that will perform a similar function or purpose in a variety of managed objects. The variety of managed objects can then be defined as subclasses of the uninstantiated class. Generate an uninstantiable class to ensure t... |
a6b8f0778f2cbac10235066e366e8034 | 101 648 | 6.4 Use of Multiple Inheritance | The principles and guidelines summarized in this clause extend, and sometimes supersede, those dealing with strict inheritance and described in the preceding clause. When specifying a managed object class using multiple inheritance, refer to the rules and guidelines for strict inheritance before applying those describe... |
a6b8f0778f2cbac10235066e366e8034 | 101 648 | 6.4.1 Multiple Inheritance Rules and Guidelines | Multiple inheritance refers to the ability of a subclass to be formed from more than one superclass. That is, the subclass inherits the operations, attributes, notifications, packages and behaviour from more than one superclass. Multiple inheritance is regarded as an optional facility to be used by object designers whe... |
a6b8f0778f2cbac10235066e366e8034 | 101 648 | 6.4.2 Multiple Inheritance | Multiple inheritance must not be used to model a containment relationship when that relationship can be logically modelled using name bindings and the containment tree. Use multiple inheritance to combine the characteristics of two or more managed object classes under the following conditions only: • the managed object... |
a6b8f0778f2cbac10235066e366e8034 | 101 648 | 6.5 Use of Allomorphism | There are circumstances in which managing systems capable to manage a certain set of managed objects are expected - at least to the extent to the standard features - to manage extended variants of those. In a multi-vendor network, for example, there are equipments from several suppliers adding different proprietary spe... |
a6b8f0778f2cbac10235066e366e8034 | 101 648 | 6.6 Use of Relationships | |
a6b8f0778f2cbac10235066e366e8034 | 101 648 | 6.6.1 General Rules and Guidelines | General rules are: • provide a consistent approach to represent all kinds of relationships and their properties externally from the MO classes. The relationship definition approach should also include cardinality; • provide a graphical expression of all system relationships; • name objects from the root (or system equi... |
a6b8f0778f2cbac10235066e366e8034 | 101 648 | 6.6.2 Modelling Relations with Attributes | Relations may be specified within the managed object class using a relationship attribute. This is suitable when the relation is known explicitly at the time of object definition. The attributes may be single or set-valued, depending on whether one or many managed object instances are involved in a particular type of r... |
a6b8f0778f2cbac10235066e366e8034 | 101 648 | 6.6.3 Modelling Relations with Managed Object Classes | Some relationships may be better specified separately from the classes which participate in the relationship. These include: • relationships which specify an effect on the behaviour of one or more other managed objects; • relationships which are expected to become more complex for example by the addition of more relate... |
a6b8f0778f2cbac10235066e366e8034 | 101 648 | 6.6.4 Modelling Relations with Name Bindings | There are two conditions which designers should take into consideration when defining relationships using name bindings. These are: • a naming relationship actually exists between two instances. This is not necessarily the same as the existence of a containment relationship between two instances since it is possible to... |
a6b8f0778f2cbac10235066e366e8034 | 101 648 | 6.7 Use of Structuring | This subclause summarizes the modelling principles that deal with reflecting the inherent structure of network and system resources in managed object instances. In this instance, the class hierarchy cannot be used because it no longer exists during execution. Instead the managed object designer must rely on the structu... |
a6b8f0778f2cbac10235066e366e8034 | 101 648 | 6.8 Use of Optionality | This subclause summarizes the guidelines for the use of optionality as a specification tool when defining managed object classes. Optionality is treated in its most general sense - meaning choice in the management process, conditional presence and ambiguity. Ambiguity is treated since the major drawback of inappropriat... |
a6b8f0778f2cbac10235066e366e8034 | 101 648 | 6.9 Behaviour Specification | This subclause summarizes modelling guidelines for behavioural specifications in plain English (SDL & Z behaviours will be different). These guidelines are in addition to those in ITU-T Recommendation X.720 [6]. Behaviour descriptions should be structured as follows: • general behaviour; • relationship behaviour; • cre... |
a6b8f0778f2cbac10235066e366e8034 | 101 648 | 6.9.1 Guidelines and Principles for Class Invariants | Instances of every instantiable class can be created, either by a CREATE operation, or by a local method which initializes an instance of the class, including all its attributes. If there are no attribute defaults or initialized values, then the missing values must be supplied at the time of creation. This may be done ... |
a6b8f0778f2cbac10235066e366e8034 | 101 648 | 6.9.2 Behavioural Preconditions and Postconditions | Use pre and postcondition clauses in GDMO, these will reflect the dynamic pre and postconditions. Pre and postconditions may use Class Invariants. The Class Invariant is inherited into all subclasses of the class where it is defined. The class invariant must be preserved without change in all descendant subclasses of t... |
a6b8f0778f2cbac10235066e366e8034 | 101 648 | 6.10 Use of Packages | Packages consisting of a combination of behaviour definitions, attributes, attribute groups, operations, notifications and parameters may be defined for subsequent insertion into a managed object under the Characterized By or Conditional Package constructs. All external packages are registered in an attribute inherited... |
a6b8f0778f2cbac10235066e366e8034 | 101 648 | 6.10.1 Mandatory Packages | Each object shall contain at least one mandatory (Characterized By) package. The use of multiple packages is an equivalent alternative to multiple inheritance. The specification of mandatory packages is encouraged to assist in profiling. |
a6b8f0778f2cbac10235066e366e8034 | 101 648 | 6.10.2 Conditional Packages (X.720 subclause 5.1.5) | The PRESENT IF clause should include a meaningful condition preferably (NOT "if an instance supports it") unless it is intended to indicate optionality. For example the condition could be based on support of a particular function or relationship. An example of a "good" conditionality statement is the crossConnectionPoi... |
ba406d5307b169fce900bc5dbfe44ef0 | 101 685 | 1 Scope | The present document gives guidance on timing and synchronization aspects and defines requirements for ATM Networks. This includes a model of network interactions as well as a simplified model of the function on which most requirements will be assigned, i.e., the Interworking Function (IWF). In relation to the models a... |
ba406d5307b169fce900bc5dbfe44ef0 | 101 685 | 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... |
ba406d5307b169fce900bc5dbfe44ef0 | 101 685 | 3 Definitions and abbreviations | |
ba406d5307b169fce900bc5dbfe44ef0 | 101 685 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply. Network-Synchronous Operation: synchronization of the physical layer (usually by a timing distribution of a timing signal traceable to a Primary Reference Clock PRC, see EN 300 462-3-1 [2] and EN 300 462-6-1 [5]) Service Synchronizatio... |
ba406d5307b169fce900bc5dbfe44ef0 | 101 685 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: AAL ATM Adaptation Layer ATM Asynchronous Transfer Mode B-TE Broadband Terminal Equipment CBR Constant Bit Rate CDV Cell Delay Variation CSI Convergence Sub-layer Indication CTD Cell Transfer Delay ISDN Integrated Services Digital Network IWF ... |
ba406d5307b169fce900bc5dbfe44ef0 | 101 685 | 4 General | As ATM is essentially a packet oriented transmission technology, the ATM network nodes do not require any synchronization of the ATM layer. At any entrance point of an ATM multiplexer or an ATM switch, an individual device shall provide cell timing adaptation of the incoming signal to the internal timing. The principle... |
ba406d5307b169fce900bc5dbfe44ef0 | 101 685 | 5 ATM Network Reference Models | |
ba406d5307b169fce900bc5dbfe44ef0 | 101 685 | 5.1 Reference interfaces, Equipment and Synchronization | Figure 1 shows the reference configuration for ATM Network interworking with private or public circuit switched networks (generally called STM Network) and with Broadband Terminal Equipment (B-TE). The ATM network comprises a number of ATM switches and multiplexors. The IWFs shown in figure 1 are those relevant for syn... |
ba406d5307b169fce900bc5dbfe44ef0 | 101 685 | 5.2 Hypothetical Networks Connection Reference Model | Figure 3 shows a hypothetical network connection reference model used to analyze jitter and wander performance of services carried over ATM. A chain of M islands is considered each containing a chain of N ATM switches. N and M are for further study. ETSI ETSI TR 101 685 V1.1.1 (1999-08) 9 ATM Network AALx AALx 1 N Serv... |
ba406d5307b169fce900bc5dbfe44ef0 | 101 685 | 6.1 General | The synchronization related characteristics of the service synchronization (wander and jitter in particular) depend on the characteristics of the ATM network itself, that is mainly CDV. In the following, the relationship between CDV, jitter and wander of the services and the used clock recovery method is discussed. |
ba406d5307b169fce900bc5dbfe44ef0 | 101 685 | 6.2 Synchronization Related Characteristics | |
ba406d5307b169fce900bc5dbfe44ef0 | 101 685 | 6.2.1 Cell Delay Variation (CDV) | When a constant bit rate stream is fed into an ATM network the stream is mapped into the ATM cell payload and the ATM cells passed to the physical layer at regular intervals (ignoring waiting time jitter etc.). On traversing the ATM network, in the absence of cell delay variation, the cells would arrive with constant i... |
ba406d5307b169fce900bc5dbfe44ef0 | 101 685 | 6.2.2 Wander Limits | The limit for long term phase wander for a 2Mbit/s PDH CBR stream, as defined by ITU-T Recommendation G.823 [8], is 36, 9 UI at 1, 2 × 10-5 Hz (daily wander limit) down to 18 UI between 0,01 Hz and 1,667 Hz. An adaptive method as described in subclause 7.3, has been used in some tests. Given any change in network load ... |
ba406d5307b169fce900bc5dbfe44ef0 | 101 685 | 6.2.3 Jitter Limits | The jitter limit for a 2 Mbit/s PDH CBR stream, as defined by ITU-T Recommendation G.823 [8], is 1,5 UI Peak to Peak between 20 Hz and 100 kHz. An adaptive method has been considered also in this case for some tests. The time constant of the adaptive method is approximately 0,8 s. The amount of jitter above 20 Hz is li... |
ba406d5307b169fce900bc5dbfe44ef0 | 101 685 | 7.1 Network - Synchronous Operation | In forcing an end-station (the CBR equipment in figure 7) to operate in synchronism with the network clock the effects of CDV can be completely eliminated. As shown in figure 7 (the figure indicates the principle for one direction only, the same applies in the opposite direction) the service clock is derived directly f... |
ba406d5307b169fce900bc5dbfe44ef0 | 101 685 | 7.2 Synchronous Residual Time Stamps (SRTS) Method | The above network synchronous option has the drawback that not all end-stations and CBR sources would wish to synchronize to the network clock. In these instances one option is to transport information about the source clock across the ATM network to eliminate playout buffer depletion or overflow. The technique adopted... |
ba406d5307b169fce900bc5dbfe44ef0 | 101 685 | 7.3 Adaptive Methods | Where ATM cells traverse a number of different ATM networks, it may not be possible to provide a common network clock to the transmitting and receiving end-stations. Also, some services may not require the purity of clock available from the above network synchronous or SRTS schemes. In these instances it may only be po... |
ba406d5307b169fce900bc5dbfe44ef0 | 101 685 | 9 Equipment Synchronization Related Requirements | |
ba406d5307b169fce900bc5dbfe44ef0 | 101 685 | 9.1 Interworking Function (IWF) for CBR Services | In the context of the present document, the Interworking Function (IWF) provides necessary adaptations of CBR bit streams to cell streams and vice versa. AALx ATM layer functions AALx Slip Control Tx Clock Network Clock for SRTS (Note) Network Clock for SRTS (Note) Free running Clock Network Clock ATM cells Time Slots ... |
ba406d5307b169fce900bc5dbfe44ef0 | 101 685 | 9.2 Broadband Terminal Equipment (B-TE) | For the purposes of the present document, the native terminal equipment (B-TE) is defined as a device able to establish a communication through a B-ISDN on a per call basis. In the example shown in figure 9 the main B-TE synchronization related functions for a voice service are described. ETSI ETSI TR 101 685 V1.1.1 (1... |
ba406d5307b169fce900bc5dbfe44ef0 | 101 685 | 9.3 ATM Switch | Devices included in ATM network are ATM Switches and ATM multiplexors. Two aspects are important in the ATM equipment regarding the synchronization of the physical layer: the possibility to be connected to a Synchronization Network and the possibility to maintain a defined quality level of the timing in case of failure... |
ba406d5307b169fce900bc5dbfe44ef0 | 101 685 | 10.1 SRTS Clock Recovery | Of the two methods currently recommended in ITU-T Recommendation I.363 [12] for the transfer of CBR service timing information between source and destination, i.e. SRTS (Synchronous Residual Time Stamp) and Adaptive Clock, only the first one has been specified in some detail: a description of the method can be found in... |
ba406d5307b169fce900bc5dbfe44ef0 | 101 685 | 10.1.1 Simulations Models | Jitter Accumulation In order to evaluate the jitter introduced in CBR services because of SRTS mechanism it is possible to resort to a fairly simple mathematical model "DS1 and DS3 Jitter Accumulation in a Network of ATM Islands with SRTS Timing Recovery - Initial Results" (see Bibliography). In reference "DS1 and DS3 ... |
ba406d5307b169fce900bc5dbfe44ef0 | 101 685 | 10.1.2 Jitter Accumulation Results | For the E1 service transport, the following values apply: N = 3 008, Fs = 2 048 000, Fnx = 2 430 000 (1) M = NF nx F s (1+ δ) (2) By numerical solution of the equation: M − M = ρ (3) for ρ = 0,997, δ = 18,352 ppm is found. Results for the peak-to-peak jitter are shown in figure 12 as a function of number of cascaded ... |
ba406d5307b169fce900bc5dbfe44ef0 | 101 685 | 10.1.3 Wander Accumulation Results | To validate the simulation model for diurnal wander accumulation the case in which only WPM clock noise is present was first considered: this case has been investigated analytically by G. M. Garner (see Bibliography). In figure 14 results from 10 independent simulation runs are compared with analytical results from G. ... |
ba406d5307b169fce900bc5dbfe44ef0 | 101 685 | 10.2 Adaptive Method Clock Recovery | The performance of ATM networks in transporting Constant Bit Rate (CBR) services with assigned quality of service is strongly dependent on a number of factors intimately connected with switch fabric design (such as switch architecture, buffering scheme and buffer discipline), traffic control mechanisms at different lev... |
ba406d5307b169fce900bc5dbfe44ef0 | 101 685 | 10.2.1 CBR and VBR traffic sharing the same output buffer | Initial simulation results have been obtained based on the model shown in figure 16. In this figure it is shown a single ATM switch with one buffer per output port, five input ports (port #1 - #5) with 155,52 Mbit/s interfaces and one input port (port #6) with 2,048 Mbit/s interface. Port #1 is loaded with a VBR source... |
ba406d5307b169fce900bc5dbfe44ef0 | 101 685 | 10.2.2 CBR traffic with dedicated output buffer | Some simulation results both for jitter and wander are provided for the case when CBR services use a dedicated output buffer in order to minimize cell delay variations. The simple structure of one single ATM switch has been considered. At a first level of approximation the behaviour of the source clock frequency recove... |
ba406d5307b169fce900bc5dbfe44ef0 | 101 685 | 11 Application of the Synchronization Methods | The following synchronization options have been identified within an ATM network: - Network-synchronous operation: this is the recommended method when traffic streams shall be merged and when interworking with PSTN. It is also the recommended method when a network clock is available at the IWF and the service user does... |
533299cc07734fc1db9f66aa08cfaaa0 | 101 683 | 1 Scope | ........................................................................................................................................................5 |
533299cc07734fc1db9f66aa08cfaaa0 | 101 683 | 2 References | ................................................................................................................................................6 |
533299cc07734fc1db9f66aa08cfaaa0 | 101 683 | 3 Definitions and abbreviations | ..................................................................................................................7 |
533299cc07734fc1db9f66aa08cfaaa0 | 101 683 | 3.1 Definitions | ..........................................................................................................................................................7 |
533299cc07734fc1db9f66aa08cfaaa0 | 101 683 | 3.2 Abbreviations | .....................................................................................................................................................7 |
533299cc07734fc1db9f66aa08cfaaa0 | 101 683 | 4 Background | ..............................................................................................................................................8 |
533299cc07734fc1db9f66aa08cfaaa0 | 101 683 | 5 Spectrum Utilization Parameters | ..............................................................................................................9 |
533299cc07734fc1db9f66aa08cfaaa0 | 101 683 | 5.1 Frequency Bands and Parameters | .......................................................................................................................9 |
533299cc07734fc1db9f66aa08cfaaa0 | 101 683 | 5.2 RF Carriers | .......................................................................................................................................................10 |
533299cc07734fc1db9f66aa08cfaaa0 | 101 683 | 5.2.1 Spurious Emissions | .....................................................................................................................................10 |
533299cc07734fc1db9f66aa08cfaaa0 | 101 683 | 6 HIPERLAN/2 Services and Functions | ...................................................................................................10 |
533299cc07734fc1db9f66aa08cfaaa0 | 101 683 | 6.1 Introduction | ......................................................................................................................................................10 |
533299cc07734fc1db9f66aa08cfaaa0 | 101 683 | 6.2 HIPERLAN/2 Physical Layer | ...........................................................................................................................12 |
533299cc07734fc1db9f66aa08cfaaa0 | 101 683 | 6.3 HIPERLAN/2 DLC Functions | ..........................................................................................................................13 |
533299cc07734fc1db9f66aa08cfaaa0 | 101 683 | 6.3.1 Data transport functions | ..............................................................................................................................14 |
533299cc07734fc1db9f66aa08cfaaa0 | 101 683 | 6.3.1.1 Medium Access Control | ........................................................................................................................14 |
533299cc07734fc1db9f66aa08cfaaa0 | 101 683 | 6.3.1.2 Error Control | .........................................................................................................................................15 |
533299cc07734fc1db9f66aa08cfaaa0 | 101 683 | 6.3.2 Radio Link Control functions | .....................................................................................................................15 |
533299cc07734fc1db9f66aa08cfaaa0 | 101 683 | 6.3.2.1 Association Control Function | ................................................................................................................15 |
533299cc07734fc1db9f66aa08cfaaa0 | 101 683 | 6.3.2.2 Radio Resource Control | ........................................................................................................................16 |
533299cc07734fc1db9f66aa08cfaaa0 | 101 683 | 6.3.2.3 DLC control function | ............................................................................................................................17 |
533299cc07734fc1db9f66aa08cfaaa0 | 101 683 | 6.4 Convergence Layer | ...........................................................................................................................................17 |
533299cc07734fc1db9f66aa08cfaaa0 | 101 683 | 7 Security | ..................................................................................................................................................17 |
533299cc07734fc1db9f66aa08cfaaa0 | 101 683 | 8 Network Management | ............................................................................................................................18 History..............................................................................................................................................................19 ETSI ETSI TR 101 683 V1.1... |
e408d42ef6ef4e1e2b6d5ec107ba6d56 | 101 643 | 1 Scope | The present document serves as an introduction to the GSM 09.xx-series. In clause 4, the technical requirements for Public Land Mobile Network (PLMN) interworking are introduced, and in clause 5 there is a summary of the contents of the GSM 09.xx-series. |
e408d42ef6ef4e1e2b6d5ec107ba6d56 | 101 643 | 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... |
e408d42ef6ef4e1e2b6d5ec107ba6d56 | 101 643 | 3 Abbreviations | In addition to those below, abbreviations used in the present document are listed in GSM 01.04. BSS Base Station System CSPDN Circuit Switched Public Data Network EIR Equipment Identity Register GSM Global System for Mobile communications HLR Home Location Register ISDN Integrated Services Digital Network IWF Interwork... |
e408d42ef6ef4e1e2b6d5ec107ba6d56 | 101 643 | 4 Interworking requirements | |
e408d42ef6ef4e1e2b6d5ec107ba6d56 | 101 643 | 4.1 Definitions of interworking | Within the scope of CCITT I.500-series of recommendations the term interworking is used to express interactions between networks, between end systems, or between parts thereof, with the aim of providing an end-to-end communication. The interactions required rely on functions and on the means to select these functions w... |
e408d42ef6ef4e1e2b6d5ec107ba6d56 | 101 643 | 4.2 Interworking between networks | Network interworking is required whenever a PLMN and a non-PLMN together are involved to provide an end-to-end connection and may be required in instance of a PLMN to PLMN connection (GSM 09.07). Although the GSM PLMN is not an integrated part of the ISDN network it is the intention to provide ISDN similar services to ... |
e408d42ef6ef4e1e2b6d5ec107ba6d56 | 101 643 | 4.2.1 Signalling requirements for Call Control | For network interworking, signalling requirements have to be defined. Existing call control signalling procedures (e.g. Signalling System No 7 (SS7), ISDN User Part (ISUP), Telephone User Part (TUP) when interworking with ISDN) will be used between the PLMN and other types of network. |
e408d42ef6ef4e1e2b6d5ec107ba6d56 | 101 643 | 4.2.2 Inter PLMN signalling requirements | For the support of services to mobile stations roaming between different PLMNs it is required to provide the means for the conveyance of Mobile Application Part (MAP) messages (e.g. the support of SS7 Message Transfer Part (MTP), Signalling Connection Control Part (SCCP) and Transaction Capabilities (TC)). |
e408d42ef6ef4e1e2b6d5ec107ba6d56 | 101 643 | 4.3 Service interworking | Service interworking is required when the Teleservices at the calling and called terminals are different. No service interworking has been identified as a requirement of the GSM system for PSTN/ISDN network based services (GSM 02.xx-series). |
e408d42ef6ef4e1e2b6d5ec107ba6d56 | 101 643 | 4.4 Supplementary service interworking | The supplementary services are described in GSM 02.04 and in GSM 02.8x and 02.9x-series. The way of providing supplementary service interworking between PLMNs and other CEPT networks is treated in GSM 03.11 and in GSM 03.8x and 03.9x-series, where each supplementary service IWF is described. ETSI ETSI TR 101 643 V8.0.0... |
e408d42ef6ef4e1e2b6d5ec107ba6d56 | 101 643 | 5 Introduction to GSM 09.xx-series | |
e408d42ef6ef4e1e2b6d5ec107ba6d56 | 101 643 | 5.1 GSM 09.02: Mobile Application Part specification | In GSM 09.02 the configuration of the GSM PLMN is treated, defining the entities of the GSM system, and the interconnection between PLMNs is treated. The entities of the PLMN are listed below: - Home Location Register (HLR); - Visitor Location Register (VLR); - Mobile-services Switching Centre (MSC); - Base Station Sys... |
da4d6d40a2afb6fd02ebd8ca49c45b16 | 101 673 | 1 Scope | The present document is an overview of a set of specifications [1] to [5] defining the network-network interface to enable service interoperability between ATM networks. This will be achieved through adequate specification of network-network interfaces in the following planes: - the Network User and Control Planes; - t... |
da4d6d40a2afb6fd02ebd8ca49c45b16 | 101 673 | 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... |
da4d6d40a2afb6fd02ebd8ca49c45b16 | 101 673 | 3 Abbreviations | For the purposes of the present document, the following abbreviations apply: ATM Asynchronous Transfer Mode EASI ETSI project, ATM Services Interoperability ETSI European Telecommunications Standards Institute NNI Network-Network Interface VC Virtual Channel VCC Virtual Channel Connection VP Virtual Path VPC Virtual Pa... |
da4d6d40a2afb6fd02ebd8ca49c45b16 | 101 673 | 4 Phases | The ATM Specifications initially define two distinct phases. The first (Phase 1) provides an interoperability specification covering a limited set of features and capabilities, while the second (Phase 2) covers aspects which are enhancements to Phase 1. Additional functionality may be defined in further phases. The mai... |
da4d6d40a2afb6fd02ebd8ca49c45b16 | 101 673 | 5 Network Architecture | The network architecture forming the basis for the present document is described in figure 1. which gives an overview of the technical scope and the interfaces to be provided for the interconnection of ATM networks. These interfaces allow for the interoperability of ATM networks and the exchange of information between ... |
da4d6d40a2afb6fd02ebd8ca49c45b16 | 101 673 | 6 Items identified to specify the ATM EASI interfaces | This clause provides a list of topics which are covered by the specifications of the NNI.easi interface and the X.easi. For some topics there are different degrees of specification, depending upon whether it is for Phase 1 or Phase 2. Furthermore, some topics are only relevant for Phase 2. |
da4d6d40a2afb6fd02ebd8ca49c45b16 | 101 673 | 6.1 NNI.easi interface | - Network Architecture: - Numbering Plan; - Interworking with non-ATM networks; - Generic requirements and capabilities of the NNI.easi interface: - User Plane: - Physical Layer; - ATM Layer; - Control Plane: - Protocol stack at the NNI.easi interface; - ATM transfer capability of signalling channels; - Support of supp... |
da4d6d40a2afb6fd02ebd8ca49c45b16 | 101 673 | 6.2 X.easi interface | - Business model for inter-connected ATM Services provision: - Policy issues; - ATM Interconnect services and process model; - Pre-Service Interconnect Services and Processes: - Interconnect Service Definition Processes; - Interconnect Service Establishment Processes; - Interconnect Service Administration Processes; - ... |
625d86633e60eed5ed3e9b798388ad75 | 101 672-1 | 1 Scope | The present document aims to identify the user's needs regarding the management of networks and services provided by the PNOs or Service providers, how this information should be presented and what are the tools needed for managing this information properly. At the same time relevant information is provided to the user... |
625d86633e60eed5ed3e9b798388ad75 | 101 672-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, edition number, version number, etc.) or non-specific. • For a specific reference, subsequent revisions do not apply. • F... |
625d86633e60eed5ed3e9b798388ad75 | 101 672-1 | 3 Symbols and abbreviations | ANALYSIS, BELGACOM, BT, COMPASS, CONCERT, DEUTSCHE TELEKOM, GARDNER GROUP GLOBAL ONE, MATAV, OFTEL, OVUM, POLISH TELECOM, TELECOM ITALIA, TELENOR and UNISOURCE are brand marks. WINDOWS is a trade mark of Microsoft Corporation. LINUX/UNIX = PC operating systems. |
625d86633e60eed5ed3e9b798388ad75 | 101 672-1 | 3.1 Symbols | For the purposes of the present document, the following symbols apply: APERAKS UN EDIFACT Message COMDIS UN EDIFACT Message CHGORDRES UN EDIFACT Message CREADV UN EDIFACT Message DEBADV UN EDIFACT Message ETSI ETSI TR 101 672-1 V1.1.5 (1999-07) 7 INVOIC UN EDIFACT "Invoice" Message ORDERS UN EDIFACT "Order" Message ORD... |
625d86633e60eed5ed3e9b798388ad75 | 101 672-1 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: ANEC European association for the co-ordination of consumer representation in standardization API Application Programming Interface CDR Call Details Record CENTREX CENTRal EXchange CPE Customer Premise Equipment CRD Call Record Detail E-billin... |
625d86633e60eed5ed3e9b798388ad75 | 101 672-1 | 4 Distinct Categories of Users | "User" is a word very often used in the standardization area but with various possible meanings. It can be understood as "user of standard" or "user of products/services" possibly conforming to one or several standards. This report is focused on the latter category of users. Nevertheless, in this area "users of product... |
625d86633e60eed5ed3e9b798388ad75 | 101 672-1 | 5 Users' needs | A survey was carried out among telecoms managers with 25% of interviewees from SME via 100 telephone and 24 face to face interviews among 5 European countries: • France; • Germany; • Italy; • Sweden; • UK. ETSI ETSI TR 101 672-1 V1.1.5 (1999-07) 9 The classification by nature of business was the following: 0% 5% 10% 15... |
625d86633e60eed5ed3e9b798388ad75 | 101 672-1 | 5.1 Possible utilization of charging and traffic information | Companies can use charging information for a number of different purposes: ETSI ETSI TR 101 672-1 V1.1.5 (1999-07) 10 |
625d86633e60eed5ed3e9b798388ad75 | 101 672-1 | 5.1.1 Managing the network | To ensure that the network configuration is at its optimum performance. The Call Details Record (CDR) provided by some network providers, is of utmost importance to Telecom managers and strategy planners in order to manage budgets, make model simulations and forecast future expenditures and formulate budgets. It is the... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.