hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
c5937175d0844f0d1c6367fc4efb0735 | 102 010 | 9.7 IPV4 and IPV6 | DECT can support IPV4 as well as IPV6. |
c5937175d0844f0d1c6367fc4efb0735 | 102 010 | 9.8 Voice service | If voice over IP is used in the fixed network, it seems to be more economic to transcode in the DECT Fixed Part the voice-over-IP data to the DECT ADPCM speech service, for transport across the air interface. The main advantages are that the IP overhead is removed and a minimum delay can be guaranteed. |
c5937175d0844f0d1c6367fc4efb0735 | 102 010 | 10 Recommendations | It is recommended to produce a Technical Specification, that defines the additions which are necessary in the DECT standard to support roaming using IP mobility. The DECT Fixed Part that gives access to an IP-network needs to broadcast its identity and it seems that for the system identification the existing DECT ARI-c... |
a5bc5caa6a12f54c9b616486f46aa232 | 101 941 | 1 Scope | The present document studies the implications of standardization of IP Terminals utilizing Ethernet, PSTN and ISDN connection methods. |
a5bc5caa6a12f54c9b616486f46aa232 | 101 941 | 2 References | For the purposes of this Technical Report (TR) the following references apply: [1] ETSI EN 301 234 (V1.2.1): "Digital Audio Broadcasting (DAB); Multimedia Object Transfer (MOT) protocol". [2] ETSI TBR 21: "Terminal Equipment (TE); Attachment requirements for pan-European approval for connection to the analogue Public S... |
a5bc5caa6a12f54c9b616486f46aa232 | 101 941 | 3 Definitions and abbreviations | |
a5bc5caa6a12f54c9b616486f46aa232 | 101 941 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: Public telecommunications network: telecommunications network used to provide publicly available telecommunications services Copied from: Brussels, 12 July 2000, COM(2000)393, Proposal for a "DIRECTIVE OF THE EUROPEAN PARLIAMENT AND OF... |
a5bc5caa6a12f54c9b616486f46aa232 | 101 941 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: ANSI American National Standards Institute ATM Forum ATM Forum CATV Community Access Television CEN European Committee for Standardization CENELEC Committee European de Normalization Electrotechnique DTMF Dual Tone Multi Frequency ECMA Standar... |
a5bc5caa6a12f54c9b616486f46aa232 | 101 941 | 4 The need for standards for IP terminals | With new telephone infrastructures coming up as telephony over CATV networks, Intranets, the Internet we also see IP-Telephone terminals, connected via an Ethernet interface, replacing the legacy analogue and digital ISDN phones. To secure the overall quality of the communication system and to maintain certain level of... |
a5bc5caa6a12f54c9b616486f46aa232 | 101 941 | 5 Available standards for most common terminals | In the legacy telecommunication network, the most common public offered interfaces are for the Public Switched Telephone Network: • The analogue presented, commonly designated PSTN or POTS interfaces; and • the digital presented, using ISDN techniques. Typical basic standards for terminals to be connected to the above ... |
a5bc5caa6a12f54c9b616486f46aa232 | 101 941 | 6 Related standards and work in progress | This clause gives an overview of standardization bodies that are active in areas related to IP terminals and identifies active work items and standards and for IP terminals that are already in place. The information provided by this clause can be used to identify the open gaps in the standardization process for IP term... |
a5bc5caa6a12f54c9b616486f46aa232 | 101 941 | 6.1 ETSI-TIPHON | ETSI's Project TIPHON defines standards and specifications to ensure the interoperability of services built on traditional voice networks with those employing the emerging next generation networks based on Internet Protocol (IP) technology. EP TIPHON specifications also assist in the transparent migration of those serv... |
a5bc5caa6a12f54c9b616486f46aa232 | 101 941 | 6.2 ETSI-STQ | The objective of STQ is to ensure the co-ordination, production (where appropriate) and maintenance of end-to-end speech quality related deliverables, for the timely and economic development of equipment for use with existing and future fixed/mobile network telecommunications service offerings from network operators. T... |
a5bc5caa6a12f54c9b616486f46aa232 | 101 941 | 6.3 ETSI-SPAN | ETSI SPAN (Services and Protocol for Advanced Networks) is ETSI's core competence centre for fixed networks standardization including IP based networks. It is responsible for all aspects of standardization for present and future converged networks including mobility aspects within fixed networks, using existing and eme... |
a5bc5caa6a12f54c9b616486f46aa232 | 101 941 | 6.4 ECMA TC32-TG17 | ECMA TC32-TG17 develops Standards and Technical Reports for IP-based multimedia communications in a business environment. Emphasis of their work is on: • the interconnection of PISN components via IP networks • the interworking of PISNs and IP networks via a gateway No particular work on IP terminals is being done in E... |
a5bc5caa6a12f54c9b616486f46aa232 | 101 941 | 6.5 ITU-T | |
a5bc5caa6a12f54c9b616486f46aa232 | 101 941 | 6.5.1 SG12 | The terminal standard P.31x is in an early state. For the new Study Period a special question (B/12) was created. Therefore a new wider approach is expected in February 2001. For the time being the most important terminal parameters are captured in ITU-T Recommendation G.177 [6]. Actually it is a network standard but t... |
a5bc5caa6a12f54c9b616486f46aa232 | 101 941 | 6.5.2 SG16 | H series SG16 is the home of all ITU-T Multimedia standards. The H-Series standards with the protocol definition. In the moment there is a big discussion on what protocol family should used (H-Series vs. IETF-Protocols). NOTE 1: There is a heavy debate. NOTE 2: In one case there was a common standardization approach ME... |
a5bc5caa6a12f54c9b616486f46aa232 | 101 941 | 6.6 TIA | As the communications industry rushes to provide homes and businesses with reliable two-way voice, video and data transmission, TIA's User Premises Equipment Division (UPED) - and more specifically, Engineering Committee TR-41 User Premises Telecommunications Equipment Requirements - has kept pace by launching projects... |
a5bc5caa6a12f54c9b616486f46aa232 | 101 941 | 6.7 IEEE 802,3af | The IEEE 802,3af [13] committee is very active on the powering issue of IP equipment over Ethernet, see the parts of the Project Authorization Request below, and the web site http://grouper.ieee.org/groups/802/3/af/. IEEE-SA Standards Board Project Authorization Request (PAR) (1999-Rev 1) TITLE: [Information technology... |
a5bc5caa6a12f54c9b616486f46aa232 | 101 941 | 7 Proposals for further standardization work | |
a5bc5caa6a12f54c9b616486f46aa232 | 101 941 | 7.1 General | For the standardization of IP-Telephone a lot of work is on going in different standardization bodies. Protocol and interoperability for IP-Telephony in general is handled by ETSI-Tiphon this of-course is also valid foe IP-Telephony terminals. Acoustical aspects of terminals are handled by ETSI-STQ and collaboration is... |
a5bc5caa6a12f54c9b616486f46aa232 | 101 941 | 7.2 ACTIONS | |
a5bc5caa6a12f54c9b616486f46aa232 | 101 941 | 7.2.1 Acoustics | ETSI, preferably ETSI-STQ can take actions to define the acoustical specifications for an IP-Telephony terminal, taking the ISDN terminal specifications as a staring point. |
a5bc5caa6a12f54c9b616486f46aa232 | 101 941 | 7.2.2 Powering over Ethernet | To be able to use IP telephones also in emergency situations the powering concept has to be capable of handling a normal mode and restricted mode, in analogy with the ISDN situation. ETSI-TC AT, based on earlier well accepted standardization of terminals and public offered interfaces, is in the best position to take th... |
ea95b96975f6c75cd5c52b67212cdb6f | 101 971 | 1 Scope | The present document concerns availability and reliability modeling for IP cable communication networks. Availability and reliability parameters for cable access networks are addressed in the context of end-to-end performance. The document focuses on the design considerations of IP based networks for survivability. It ... |
ea95b96975f6c75cd5c52b67212cdb6f | 101 971 | 2 References | For the purposes of this Technical Report (TR) the following references apply: [1] T1 TR.PP.70: "A Reliability/Availability Framework for IP-based Networks and Services". [2] ITU-T Recommendation E.436: "Customer Affecting Incidents and blocking Defects Per Million". [3] Void. [4] ITU-T Recommendation I.350: "General a... |
ea95b96975f6c75cd5c52b67212cdb6f | 101 971 | 3 Definitions and abbreviations | Also see clause 8.2. |
ea95b96975f6c75cd5c52b67212cdb6f | 101 971 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: access: function required to initiate or request a service accuracy: degree of conformity of a measured or calculated value to its actual or specified value alternate routing: routing of a call or message over a substitute route when a... |
ea95b96975f6c75cd5c52b67212cdb6f | 101 971 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: ARMA Autoregressive Moving Average ATIS Alliance for Telecommunications Industry Solutions ATM Asynchronous Transfer Mode BER Bit Error Rate BGP Border Gateway Protocol B-ISDN Broadband-ISDN CCS Common Channel Signaling CIP Critical Infrastruc... |
ea95b96975f6c75cd5c52b67212cdb6f | 101 971 | 4 IP network survivability framework | Service View Network View Service Level Agreements Network Requirements User perceived Performance Metrics Network Performance Metrics Figure 4.1: IP network survivability framework Service view clause describes those attributes of importance to the service users. It includes the concept of service outages based upon a... |
ea95b96975f6c75cd5c52b67212cdb6f | 101 971 | 6 Key concepts | IP Network Reliability Performance (as discussed in the present document) has two perspectives: (i) the service view, and (ii) the network view. Generally, the service view will be important to both end users as well as other service providers. The network view will be most important to the owner and operator of the ne... |
ea95b96975f6c75cd5c52b67212cdb6f | 101 971 | 6.1 Service view | The service view drives the network reliability and availability requirements. Service users experience network failure modes as service failures or as unacceptable service performance while trying to access and use a service. There are four (4) key attributes that need to be considered: 1) Service criticality: Service... |
ea95b96975f6c75cd5c52b67212cdb6f | 101 971 | 6.2 Network view | The network needs to satisfy two views: the service view to meet service users' expectations and the network owner view to satisfy the network owners' costs and Operations, Administration, Maintenance and Provisioning (OAM&P) requirements. The network failure mode behavior when technology fails, when people cause a pro... |
ea95b96975f6c75cd5c52b67212cdb6f | 101 971 | 6.3 Causal attributes | The causal attributes are technology failures such as hardware and software failures, OAM&P activities (e.g. software upgrades), environmental incidents (e.g.an earthquake and traffic overloads such as control messages), and procedural errors. The IP Network is designed and operated to both mitigate and mask the causal... |
ea95b96975f6c75cd5c52b67212cdb6f | 101 971 | 6.4 Service characteristics | Figure 6.1 is a representation of service characteristics, breaking out the service availability function over time into three service categories: Successful Performance, Incorrect Performance, and Non-Performance. Depending on the network design, service can even be superior when customers receive performance beyond a... |
ea95b96975f6c75cd5c52b67212cdb6f | 101 971 | 6.5 Network outages versus service outages | Network outages are loss of network resources due to failures, acts of nature, or operational activities. The loss of a network resource can impact services, reduce the available bandwidth or simply result in the loss of network protection. The loss of network resources may also be transient and have no impact on the n... |
ea95b96975f6c75cd5c52b67212cdb6f | 101 971 | 6.6 Service and operations dependability | This clause describes the hierarchy of attributes or metrics used to organize and set reliability and maintainability requirements for the public carrier IP network. The primary attributes (observable effects) are separated from the secondary attributes (causes) to facilitate solution flexibility. This flexibility is r... |
ea95b96975f6c75cd5c52b67212cdb6f | 101 971 | 7 Network design considerations for survivability | Figure 7.1 illustrates the design considerations for network survivability. The considerations are grouped into prevention and mitigation/masking strategies. Prevention strategies either prevent the occurrence or reduce the frequency of occurrence of network node and link failures due to technology failures, environmen... |
ea95b96975f6c75cd5c52b67212cdb6f | 101 971 | 7.1 Reference network architecture | Figures 7.3 and 7.4 provide a description of a user-to-user connection on an IP network (this connection is also known as a hypothetical reference path in ITU-T Recommendation Y.1541). NOTE: When restoration needs to be done at the physical layer underlying the architecture of figure 7.3, consideration must also be giv... |
ea95b96975f6c75cd5c52b67212cdb6f | 101 971 | 7.2 Traffic analysis issues in IP based networks | Traffic analysis techniques are very important to the characterization and definition of network reliability and availability. The spread of IP based networks and services has led to a need for tools to better assess the survivability, reliability, and availability of these networks, particularly as IP infrastructures ... |
ea95b96975f6c75cd5c52b67212cdb6f | 101 971 | 7.3 Causes of service outages | The key causes of IP service outages are listed below along with each of their root causes. ETSI ETSI TR 101 971 V1.1.1 (2003-05) 23 |
ea95b96975f6c75cd5c52b67212cdb6f | 101 971 | 7.3.1 Hardware failures | • Single points of failure. • High failure rates due to new unproven technology, poorly centered and highly stressed circuit designs, uncontrolled operating environment, insufficient equipment cooling, insufficient ElectroStatic Discharge (ESD) protection. • Poor fault detection coverage. • Slow network restoration. • ... |
ea95b96975f6c75cd5c52b67212cdb6f | 101 971 | 7.3.2 Software failures | • Unstructured, overly complex and large amounts of poorly documented code. • Processor speed. • Poor fault detection coverage and slow software recovery. • Slow network restoration. • Unreliable network restoration. • Immature processes resulting in design and load build defects. |
ea95b96975f6c75cd5c52b67212cdb6f | 101 971 | 7.3.3 OAMP activities | • GUI and physical design that facilitates human error. • Inadequate training or procedures resulting in human error. • Network elements not designed for in-service upgrades. |
ea95b96975f6c75cd5c52b67212cdb6f | 101 971 | 7.3.4 Environmental incidents | • Environmentally high risk site location. • Poor building design or location of equipment in the building. • Inadequate training or procedures resulting in human error. • No site diversity. NOTE: Environmental incidents include: temperature, humidity, electrical storms, floods, office vibrations, earthquakes, power li... |
ea95b96975f6c75cd5c52b67212cdb6f | 101 971 | 7.3.5 Traffic overloads (bearer and control message traffic) | • Lack of overload controls. • Immature development processes resulting inadequate overload controls. • Poor load balancing by protocols. ETSI ETSI TR 101 971 V1.1.1 (2003-05) 24 |
ea95b96975f6c75cd5c52b67212cdb6f | 101 971 | 7.4 IP protection and restoration technologies | The following lists some of the IP-based network restoration/protection technologies, their application and restoration times. Table 7.1: IP-based Network Restoration/Protection Technologies Restoration and Protection Name Network Application Area Network Area Restoration Time Border Gateway Protocol (BGP-4) Paths betw... |
ea95b96975f6c75cd5c52b67212cdb6f | 101 971 | 8 Guides and metrics | The lack of industry consistency for IP network reliability makes it virtually impossible for network providers to know if what they are building will deliver the services reliability performance required by end users. This is further complicated by the fact that network service providers specify network availability w... |
ea95b96975f6c75cd5c52b67212cdb6f | 101 971 | 8.1.1 The DPM parameter and its advantages | The rapid evolution of IP networks requires a standardized methodology to evaluate IP network reliability in terms of actual customer impact of outages. This can be done using the concept of a defect, normalized to a defined rate - Defects Per Million (DPM) [2], which is a useful complement to traditional reliability m... |
ea95b96975f6c75cd5c52b67212cdb6f | 101 971 | 8.1.1.1.1 Session: a service perspective | Any failure may or may not lead to a customer impact, and a lot of this connection has to do with the service session, the transaction, the protocol, and the tolerance of the end user. Take a service perspective: any use of a service is initiated, continues, and is terminated. Call this complete use of service a sessio... |
ea95b96975f6c75cd5c52b67212cdb6f | 101 971 | 8.1.1.1.2 Examples | In each example, you can trace the flow of condition to customer impact through figure 8.1. VoIP example: Some network condition (possibly some network failure, or maybe even just congestion) would cause a delayed packet. These delayed packets could then affect one or more transactions (could be someone speaking a sent... |
ea95b96975f6c75cd5c52b67212cdb6f | 101 971 | 8.1.2.1 IP backbone network DPM | • Units: Each unit is 1 Port-Hour. For each customer connection, or access port, into the IP Backbone there are 24 daily port-hours available. • Formula: DPM = ((sum (Total Down Port-Hours)/sum (Total Available Port-Hours)) x 1 000 000 for the reported time period, e.g. daily. • Definitions: - Total Available Port-Hour... |
ea95b96975f6c75cd5c52b67212cdb6f | 101 971 | 8.1.2.2 Access Facilities DPM | • Units: Each unit is 1 Port-Hour. For each customer connection, or access port, into the IP Backbone there are 24 daily port-hours available. • Formula: DPM = ((sum (Total Down Port-Hours)/sum (Total Available Port-Hours)) x 1 000 000 for the reported time period (e.g. daily). • Definitions: - Total Available Port-Hou... |
ea95b96975f6c75cd5c52b67212cdb6f | 101 971 | 8.1.3 DPM usage considerations | Care should be taken in relating defect definitions and measurements to other types of analysis, for example, those using the impact, duration and frequency of failure events. DPM is a quality-based unit of measure that can be applied to a broad range of existing metrics: • System downtime of 3 minutes per year is equi... |
ea95b96975f6c75cd5c52b67212cdb6f | 101 971 | 8.2 Reliability/availability SLA types | Several types of SLAs are considered below: EXAMPLE: SLAs between an ISP (Internet Service Provider) and a service user, and between a TSP (Transport Service Provider) and an ISP. For the former, the ISP is providing a wide range of services to end-users, and for the latter the TSP is providing transport of packets acr... |
ea95b96975f6c75cd5c52b67212cdb6f | 101 971 | 8.2.1 ISP to user reliability/availability SLA metrics | Service activation/change time: The time to activate a service or a service change measured from receipt of the request to when service/service change is ready for successful use (functions as specified). Service restoration ratio: The percentage of service restorations that are successfully completed by the service pr... |
ea95b96975f6c75cd5c52b67212cdb6f | 101 971 | 8.2.2 ISP to ISP metrics | Service activation/change time: The percent of service/service change requests that are completed within "ta" minutes, measured from the receipt of the requests to when services/service changes are ready for successful use (functions as specified). Service restoration ratio: The percentage of service restorations that ... |
ea95b96975f6c75cd5c52b67212cdb6f | 101 971 | 8.2.3 TSP to ISP reliability/availability SLA metrics | Service activation/change time: The percent of service/service change requests that are completed within "ta" minutes, measured from the receipt of the requests to when services/service changes are ready for successful use (functions as specified). Service restoration ratio: The percentage of service restorations that ... |
ea95b96975f6c75cd5c52b67212cdb6f | 101 971 | 8.2.4 ISP to supplier metrics | Dead-on-arrival: The average percentage of defective hardware delivered hardware, between receipt and Solution cut-over. Software release insertion aborts: The average percentage of software release insertions that need to be aborted because of software defects. Maintenance costs: The costs for planned and unplanned ma... |
ea95b96975f6c75cd5c52b67212cdb6f | 101 971 | 8.2.5 Network attributes and metrics | Network element outage failure rate: The frequency of network element outages of greater than "to" second durations, where "to" seconds is sufficient to cause a network service outage. The metric is applied for all service impacts from partial to complete network element outages. The unit of measure is "failures per ye... |
ea95b96975f6c75cd5c52b67212cdb6f | 101 971 | 8.3 Prediction analysis modeling | |
ea95b96975f6c75cd5c52b67212cdb6f | 101 971 | 8.3.1 Design guide for IP based network reliability prediction and analysis | Mitigation of failure rates is achieved by the use of mature technologies and good design practices. To further improve solution reliability, masking design approaches such as network element redundancy or network link protection are used. Network design requires architectures that ensure reachability, restoration/prot... |
ea95b96975f6c75cd5c52b67212cdb6f | 101 971 | 8.4 How to use the metrics | |
ea95b96975f6c75cd5c52b67212cdb6f | 101 971 | 8.4.1 Reliability/availability SLA proposal | Current SLAs, used to make legally binding service contracts with service customers, consider a wide range of Quality of Service attributes such as delay, throughput, utilization and packet loss. However, they are not equally rich in service reliability attributes such as service denial, service failure, and service do... |
ea95b96975f6c75cd5c52b67212cdb6f | 101 971 | 8.4.1.1 Terminology | In the present document the following terms are used as defined: • Service Failure Rate, the frequency of service failure, is used to describe service reliability. • Service Downtime is used to describe service availability. These terms each require a definition of service failure: • Service Failure Threshold is the se... |
ea95b96975f6c75cd5c52b67212cdb6f | 101 971 | 8.4.1.2 Service vs. network solution reliability/availability | The applications that are provided by IP network service offerings experience network outages as packet delay and loss. Therefore network outages impact differently depending on the type of service as well as the extent and duration of the network outage. Service reliability attributes such as service denial, service f... |
ea95b96975f6c75cd5c52b67212cdb6f | 101 971 | 8.4.1.3 Reliability/Availability SLA Framework | |
ea95b96975f6c75cd5c52b67212cdb6f | 101 971 | 8.4.1.3.1 Introduction | Most of the reliability/availability SLA requirements will be driven by the market. The challenge for the Service Provider is to set best-in-class reliability/availability SLAs, yet minimize the cost to own, operate and maintain the Network Solution. This means that reliability/availability SLAs are a set of requiremen... |
ea95b96975f6c75cd5c52b67212cdb6f | 101 971 | 8.4.1.3.2 Reliability/availability-SLA process | The following is a set of steps (see figure 8.7) used to specify reliability/availability-SLAs: 1) Propose an initial set of metrics depending on service type. 2) Propose initial set of reliability/availability SLA requirements and agreement conditions based on: a) User Tolerance to failure and downtime. b) Impact of s... |
ea95b96975f6c75cd5c52b67212cdb6f | 101 971 | 8.4.1.3.3 Reliability/availability SLA template | The following template lists the key clauses of an reliability/availability SLA: Conditions, Categories, and Metrics. Not all template metrics are used for all services and in all markets. They represent the set of metrics from which the Service Provider chooses based on business considerations. |
ea95b96975f6c75cd5c52b67212cdb6f | 101 971 | 8.4.1.3.4 Reliability/availability SLA conditions | The reliability/availability SLA requirements shall be met subject to the following conditions: 1) Service Period is the period of total calendar time that the reliability/availability SLA applies (e.g. 24/7 or excluding a specified maintenance window). 2) Measurement Conditions defines the measurement method and stati... |
ea95b96975f6c75cd5c52b67212cdb6f | 101 971 | 8.4.1.3.5 Reliability/availability SLA categories | The service class hierarchy is dynamic depending on the service type and the market segment. The proposal is to combine in various ways and in varying degrees two independent attributes of a service: 1) Service Criticality: categorizes the criticality of the service from the users' perspectives. The criticality drives ... |
ea95b96975f6c75cd5c52b67212cdb6f | 101 971 | 8.4.1.3.6 Sample reliability/availability SLAs | To illustrate the template the following lists sample reliability/availability SLAs between an ISP and a service user or group of service users. Note that these numbers should not be viewed as proposed industry standards. Category A1 Type: ISP to Service User EXAMPLE: Voice over IP service for a Stock Exchange. Metric ... |
ea95b96975f6c75cd5c52b67212cdb6f | 101 971 | 8.5 Guides | |
ea95b96975f6c75cd5c52b67212cdb6f | 101 971 | 8.5.1 Supplier compliance guide | To de-risk the introduction of a network solution, the ISP should be involved throughout the supplier's development and introduction lifecycle of the solution. The following lists this involvement: • The Service Provider should review the supplier's network reliability, availability and maintenance predictions. These p... |
ea95b96975f6c75cd5c52b67212cdb6f | 101 971 | 8.5.2 Service solution reliability/availability SLA guide | Most reliability/availability SLA requirements will be driven by market competition rather than industry wide agreed requirements. The challenge for the Service Provider is to set best-in-class reliability/availability SLAs, yet minimize the cost of operations and maintenance. This means that reliability/availability S... |
ea95b96975f6c75cd5c52b67212cdb6f | 101 971 | 8.5.3 Network solution reliability/availability measurement guide | Network wide reliability metrics for a solution are not directly measured but are calculated from the individual failure modes of links and nodes that can be directly observed or measured. The network wide metrics are calculated either based on each specific network configuration or for a set of specified reference net... |
ea95b96975f6c75cd5c52b67212cdb6f | 101 971 | 9 Application to cable networks | The TS 101 909 series of Technical Specifications address inter-operability of Network Elements for IP cable communications (IPCablecom). These specifications target the implementation over cable access networks of VoIP, with QoS equivalent to that of the PSTN [19], [38]. Therefore they relate to conveyance over cable ... |
ea95b96975f6c75cd5c52b67212cdb6f | 101 971 | 9.1 IPCablecom zones and domains | CMS CMS CMS PSTN Gateway PSTN Gateways PSTN Gateway Administrative Domain PST PST Administrative Domain Administrative Domain V V PST V Cable Operator A Zone 1 Cable Operator A Zone 2 Managed IP Backbone Cable Operator B Zone 3 Cable Operator C Zone 4 Figure 9.1: Zones and administrative domains An IPCablecom zone cons... |
f7b79157a53dfc97618a941856d11848 | 101 963 | 1 Scope | The present document aims to describe the high level service features of European Cable Communications Operators and the European cable industry for time critical multimedia IP Cable Communications, to analyse these, make an assessment of their relative priorities and to collate them into a Technical Report. The presen... |
f7b79157a53dfc97618a941856d11848 | 101 963 | 2 References | For the purposes of this Technical Report (TR) the following references apply: [1] ITU-T Recommendation J.1: "Terms, definitions and acronyms applicable to the transmission of television and sound-programme signals and of related data signals". [2] PacketCable PKT-TR-ARCH1.2-V01-001229: "PacketCable 1.2 Architecture Fr... |
f7b79157a53dfc97618a941856d11848 | 101 963 | 3 Definitions and abbreviations | |
f7b79157a53dfc97618a941856d11848 | 101 963 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: On-Net(work): voice call or data transmission session in which the originating and terminating devices are connected to a single IPCablecom network which may consist of one or more zones or domains Off-Net(work): voice call or data tra... |
f7b79157a53dfc97618a941856d11848 | 101 963 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: 3PTY Three ParTY calling AN Access Node ANS ANnouncement Server BRI Basic Rate ISDN (Integrated Services Digital Network) CC Call Content CEC Commission of the European Communities ETSI ETSI TR 101 963 V1.1.1 (2002-04) 13 CFB Call Forward Busy... |
f7b79157a53dfc97618a941856d11848 | 101 963 | 4 Fundamental Service Definition | The European cable operator's service definition is based broadly on the IPCablecom Reference Architecture (ITU-T Draft Recommendations J.160, J.162 and J.112, see bibliography). Within this architecture, several networks of differing types may be interconnected to offer an end-to-end service, e.g. telephony. This clau... |
f7b79157a53dfc97618a941856d11848 | 101 963 | 4.1 General | The fundamental need of the european cable operators is to have the ability to deliver over their HFC networks, voice telephony services which are indistinguishable to the end-user in performance and functionality from those delivered from modern DLEs over conventional PSTN or CSN. There is the need to compete with the... |
f7b79157a53dfc97618a941856d11848 | 101 963 | 4.2 Additional core network interface functionality | |
f7b79157a53dfc97618a941856d11848 | 101 963 | 4.2.1 QoS (Phase 1) | National specific regulatory voice quality licence requirements may be applicable in some European Countries but in general IPCablecom voice quality must be equivalent or better than existing PSTN service in order to gain acceptance in the marketplace. This level of voice quality is sometimes referred to as "Carrier Qu... |
f7b79157a53dfc97618a941856d11848 | 101 963 | 4.2.2 Supporting trunking gateways to PSTN (Phase 1) | While the support of SS7 trunks to the PSTN is mandated by national specific regulations, interfacing to support internal MG to MGC interfaces is an option. This interface may be based on either ITU-T Draft Recommendation J.171 (see bibliography), recently published as TS 101 909-13 [12] which is expected to allow for ... |
f7b79157a53dfc97618a941856d11848 | 101 963 | 4.2.3 Supporting signalling gateways to SS7 networks | The following functionality is also necessary in the indicated time scales (as defined above): • Full support of SS7 signalling protocol including connectivity to STP and SCP for the circuit connection and provision of number translation services and other Intelligent Network (IN) facilities (Phase 1) - Transactions (T... |
f7b79157a53dfc97618a941856d11848 | 101 963 | 4.3 Reference networks | The needs of the European cable industry are based on the IPCablecom Reference Architecture (see bibliography). Within this architecture, several types of networks are interconnected to offer an end-to-end service. This clause is concerned with the needs of European cable operators for the exchange of data and signalli... |
f7b79157a53dfc97618a941856d11848 | 101 963 | 4.3.1 Off-network calls using NCS | In the first phase of NCS, on-network IP to IP calls is assumed to be restricted to one zone and one domain. For off-network calls, the PSTN will be used. In this case interworking is necessary between the IP network and the CSN/PSTN. Within the IPCablecom architecture this function is carried out by a PSTN Gateway. Ap... |
f7b79157a53dfc97618a941856d11848 | 101 963 | 4.3.2 Off-network using IPCablecom network | In this situation interworking is not necessary. Packets will be travelling through the IP networks without bearer conversion. However, there is a need for the interchange of signalling information between Call Management Servers. As in the case of a circuit switched network, the gateway will need to support part or al... |
f7b79157a53dfc97618a941856d11848 | 101 963 | 4.3.3 LCS: V5.2 Gateway connection to PSTN | An alternative implementation of a PSTN gateway is to use a V5.2 access to a DLE, which in turn handles all on-network and off-network calls, including calls to the PSTN. In the case, the implementation may be based on the mapping of the NCS protocol to V5.2. For details see clause 5.2. |
f7b79157a53dfc97618a941856d11848 | 101 963 | 4.3.4 Packet switched network | In this situation interworking is not required. Packets will be travelling through the IP networks without bearer conversion. The gateway in this case could be a router configuration, but due to issues such as IP number plans, latency, standard interfaces, etc, this needs further study. There is a need for the intercha... |
f7b79157a53dfc97618a941856d11848 | 101 963 | 4.4 IPCablecom architecture framework | At a very high level, the IPCablecom architecture contains three network types: the "HFC Access Network", one or more "Managed IP Networks" and the PSTN (or other CSN). The Access Node (AN) provides connectivity between the Access Network and the IP Network. The Signalling Gateway (SG) and the Media Gateway (MG) provid... |
f7b79157a53dfc97618a941856d11848 | 101 963 | 4.5 IPCablecom zones and domains | An IPCablecom zone consists of the set of MTAs in one or more HFC access networks that are managed by a single functional CMS as shown in figure 3. Interfaces between functional components within a single zone are defined in the IPCablecom specifications. Interfaces between zones (e.g. CMS-CMS) have not been defined an... |
f7b79157a53dfc97618a941856d11848 | 101 963 | 4.6 Detailed network functionality | |
f7b79157a53dfc97618a941856d11848 | 101 963 | 4.6.1 IPCablecom network interfaces | Between the IPCablecom zones or domains and the domain of another network there will need to be a gateway for interfacing purposes. For telephony services, network X could be a conventional circuit switched network or another packet switched network using either IPCablecom or some other packet switched technology. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.