hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
5774cc07066e9e25e8acfa2230bb2abb | 102 068 | 11.1 General | The connections for assistive technology can be split into data, audio, and video. These connections can be treated independently. Some assistive devices will need to support more than one type. In that case, several connection interfaces must be supported. It is proposed that the simplest possible interfaces should be... |
5774cc07066e9e25e8acfa2230bb2abb | 102 068 | 11.2 Data | The data interface should be an RS-232. On top of the RS-232 interface, a protocol dependent on the type of assistive device must be run. If desired, this interface can be carried over either a suitable physical layer such as USB or Bluetooth (which are used in the present document as examples). This would give the pro... |
5774cc07066e9e25e8acfa2230bb2abb | 102 068 | 11.2.1 Applicable requirements for data over RS-232 | The interface should be in accordance with the EIA-232-F specification [14] with the assistive device acting as Data Terminal Equipment (DTE) and the ICT device acting as Data Communications Equipment (DCE). DB9 connectors are recommended. |
5774cc07066e9e25e8acfa2230bb2abb | 102 068 | 11.2.2 Applicable requirements for data over USB | The interface should be in accordance with the Universal Serial Bus Specification [17] with the assistive device acting as master (the host device) and the ICT device acting as slave. |
5774cc07066e9e25e8acfa2230bb2abb | 102 068 | 11.2.3 Applicable requirements for data over Bluetooth | Data over Bluetooth should be in accordance with the serial profile as specified in volume 2 of the Bluetooth specification [16]. This profile specifies which parts of the Bluetooth core have to be implemented. The Bluetooth core is specified in volume 1 of the Bluetooth specification [15]. ETSI ETSI TR 102 068 V1.1.3 ... |
5774cc07066e9e25e8acfa2230bb2abb | 102 068 | 11.2.4 Applicable requirements for data over wireless LAN | The interface should be in accordance with the specifications available on http://standards.ieee.org/catalog/olis/index.html. On the assistive device side, TCP/IP protocol and Telnet (RFC standards) should be used. In addition to the above, on the assistive device side, IP addresses need to be allocated in the same ran... |
5774cc07066e9e25e8acfa2230bb2abb | 102 068 | 11.2.6 Suggested assistive device specific commands | It is suggested that the following additional AT commands are defined for use by assistive devices. Command Possible response(s) +CASS=<sub-command>[,<param>] +CASS: <response> +CASS ERROR: <error code> +CASS=? +CASS: (list of supported <sub-command>s) It is necessary that the definition of the +CASS (arbitrarily chose... |
5774cc07066e9e25e8acfa2230bb2abb | 102 068 | 11.2.6.1 Enter terminal mode | +CASS command with sub-command Possible response(s) +CASS=TERM +CASS: TERM OK +CASS ERROR: <error code> The +CASS=TERM command should put the data connection in ANSI text terminal mode. From now on everything written to the screen of the ICT device is copied to assistive device via the data connection, while all text s... |
5774cc07066e9e25e8acfa2230bb2abb | 102 068 | 11.2.6.2 Increase or decrease time-outs | +CASS command with sub-command Possible response(s) +CASS=TOUT,<+n>/<-n> +CASS: TOUT OK +CASS ERROR: <error code> Multiply or decrease all time-outs with a factor n. ETSI ETSI TR 102 068 V1.1.3 (2002-11) 28 |
5774cc07066e9e25e8acfa2230bb2abb | 102 068 | 11.3 Audio | It is recommended that where an analogue audio interface is provided it should be similar to that in laptop PCs and PC audio cards. If desired, this interface can be carried over either USB or Bluetooth. This would give the following protocol stack alternatives: ICT device Assistive device Audio profile Bluetooth Audio... |
5774cc07066e9e25e8acfa2230bb2abb | 102 068 | 11.3.1 Applicable requirements for wired analogue audio | Standard 3,5 mm connectors should be used. ICT devices should be equipped with jacks (female). Assistive devices should be equipped with jacks. Cables should be fitted with plugs (male). The electrical specification of a line audio input to the ICT device should be: • Input impedance > 10 kΩ; • Maximum input level 1 VR... |
5774cc07066e9e25e8acfa2230bb2abb | 102 068 | 11.3.2 Applicable requirements for audio over USB | The interface should be according to the Universal Serial Bus Specification [17] with the assistive device acting as master (the host device) and the ICT device acting as slave. |
5774cc07066e9e25e8acfa2230bb2abb | 102 068 | 11.3.3 Applicable requirements for audio over Bluetooth | Audio over Bluetooth should be according to the headset profile as specified in volume 2 of the Bluetooth specification [16]. This profile specifies which parts of the Bluetooth core have to be implemented. The Bluetooth core is specified in volume 1 of the Bluetooth specification [15]. |
5774cc07066e9e25e8acfa2230bb2abb | 102 068 | 11.4 Video | Due to the variations in technical param, their complexity and the quick development in the area, no proposal is presently made for video. However, there are many de-facto standards in this area. |
5774cc07066e9e25e8acfa2230bb2abb | 102 068 | 12 Recommendations and conclusions | An eEurope community that allows everyone fair access to advanced information and communication media must include those citizens whose disabilities are such that they cannot use devices designed for all. For this group of users, often with multiple disabilities, it is crucial that affordable, effective and usable assi... |
dfd8dec9b97e6d7ed4fe116bda246f25 | 102 024-6 | 1 Scope | The present document applies to IP networks that provide voice telephony in accordance with any of the TIPHON Scenarios. The objective with the present document is to collect all results of various VoIP speech transmission quality tests and related information. The measurement descriptions are provided in order to expl... |
dfd8dec9b97e6d7ed4fe116bda246f25 | 102 024-6 | 2 References | For the purposes of this Technical Report (TR) the following references apply: [1] ETSI TR 101 329-6 (V2.1.1): "Telecommunications and Internet Protocol Harmonization Over Networks (TIPHON) Release 3; End-to-end Quality of Service in TIPHON systems; Part 6: Actual measurements of network and terminal characteristics an... |
dfd8dec9b97e6d7ed4fe116bda246f25 | 102 024-6 | 3 List of Measurement Results | The first version of the present document, published as TR 101 329-6 [1] in TIPHON Release 3 has covered measurement gained during the period 1999 to 2001; the conclusions from which have contributed to the other documents of the TS/TR 101 329 series of ETSI deliverables. In addition the measurement results from the 2n... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 1 Scope | The present document specifies the design and specification requirements obtained from reverse engineering a set of ITU recommendations, consisting of J.arch (architectural framework), J.istp (IPCablecom Signalling Transfer Protocol), and J.tgcp (Trunking Gateway Control Protocol). These documents are part of a set of ... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 2 References | For the purposes of this Technical Report (TR) the following references apply: [1] ITU-T Recommendation J.160 (J.arch): "Architectural framework for the delivery of time critical services over cable television networks using cable modems". [2] ITU-T Recommendation J.165 (J.istp): "IPCablecom Signalling Transport Protoc... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 3 Definitions and abbreviations | |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: Access Node (AN): As used in the present document, an Access Node is a layer two termination device that terminates the network end of the J.112 connection. It is technology specific. In ITU-T Recommendation J.112 [4] annex A it is cal... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 3.2 Abbreviations | For the purposes of the present document, the following symbols apply: AN Access Node ANC Announcement Controller ANP Announcement Player ANS Announcement Server CA Call Agent CIC Circuit Identification Code CM Cable Modem CMS Call Management Server DHCP Dynamic Host Configuration Protocol DNS Domain Name System DPC De... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 4 Overview and purpose | The present document describes the design and specification requirements for a sub-set of the ITU-T IPCablecom documents. These requirements have been obtained through reverse engineering of the applicable documents, i.e. the General Architecture (J.arch or J.160 [1], the IPCablecom Signalling Transport Protocol (J.ist... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 4.1 History and relationships to other standards | This historical background is given for information only. The IPCablecom architecture is stand alone, and can be considered, with its references, complete. Historically, it may be of interest to note that PacketCable set of specifications is a complete design of a decomposed set of components, focused on Northern Ameri... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 4.2 ITU-T IPCablecom framework | The objective of the IPCablecom Architecture Framework document (J.arch) is to provide a high-level reference framework that identifies the functional components and defines the interfaces necessary to implement the capabilities detailed in the individual IPCablecom specifications as listed above. It is not a complete ... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 4.2.1 IPCablecom reference architecture | At a high level, the IPCablecom architecture references three networks: • The J.112/J.162 HFC Access Network. • The Managed IP Network. • The PSTN. A general overview of the IPCablecom architecture with most of its components is shown in figure 1. The access node (AN) provides connectivity between the J.112 HFC Access ... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 4.2.2 Interfaces | Between the networks, a number of interfaces can be distinguished. These interfaces are: • NCS over J.112 between the managed IP network and the subscriber. Since this is an open IP interface, is not considered "trusted" and operations initiated from the HFC must be validated, authorized, authenticated, and made secure... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 4.2.3 Bundling and unbundling of components | The architecture with the several components shown in figure 1 does not specifically require any bundling or unbundling of components. The components shown are logical components, and a vendor may or may not bundle any managed IP component with another. As a result, "TGCP" and "ISTP" can be considered to be "internal" ... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 4.2.4 IPCablecom zones and domains | Within the IPCablecom architecture, zones and domains have been defined to support various operation business and network deployment options: • A zone is the set of MTA's controlled by a single CMS. • Domains are one or more zones managed by an administrative entity, sharing a common Managed IP network. ETSI ETSI TR 10... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 5 Requirements obtained from J.arch | |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 5.1 Overview | |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 5.1.1 Scope | This clause describes the requirements obtained from reverse engineering the ITU-T J.arch document (J.160 [1]). The source document used has been written by the Study Group 9 of the ITU-T. The title of this file is "Draft New Recommendation J.160 (J.arch): Architectural framework for the delivery of time critical servi... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 5.1.2 What is J.arch? | J.arch is a globalized ITU version of the PacketCable architecture specification. The commercial and regulatory issues have been removed from it, though, as compared to the original document. Furthermore, ITU references are used instead of North American ones, which have been moved to annexes, appendices, or supplement... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 5.1.3 Three architectures, possible three phases | Operators can choose to deploy one or more of the phased in architectures • Line Control Signalling (LCS) supporting GR-303 or V5.2 remote digital terminal interface; this is mostly for operators who have local/central office switches or must rollout today. Most IPCablecom functions are bundled in the local switch. • N... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 5.2 Commercial requirements for IPCablecom | |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 5.2.1 Implicit commercial requirements | The following commercial requirements are implicit in the IPCablecom architecture, and may have had more impact on the design of the framework than even explicit requirements: • The architecture must support the time to market business considerations cable operators for deploying packet based services, including the bu... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 5.2.2 Legal/Regulator observations | • Legal/Regulatory issues for voice over IP and cable voice services are not settled yet in law or regulation agencies. • These issues may be different for voice over IP over cable than for phone companies. • No particular regulatory issues are assumed by the use of PSTN or voice over IP. ETSI ETSI TR 102 019 V1.1.1 (2... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 5.3 Technical requirements | |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 5.3.1 Architecture goals of J.arch | |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 5.3.1.1 General architecture goals | • Voice quality must be comparable to or better than the PSTN as perceived by the end-user. • The architecture must be scalable, and capable of supporting up to millions of subscribers. • One-way delay for local IP access and IP egress (i.e. excluding the IP backbone network) must meet the delay requirements for all IP... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 5.3.1.2 Call signalling requirements | • It must define a network-based signalling paradigm that allows operator management of set top terminals, with the intelligence for features mostly residing in the operators equipment and managed IP network: this is called Network Control Signalling (NCS). It is somewhat similar to the IETF and soft-switch approaches,... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 5.3.1.3 Call features | This clause lists the call features the architecture must support. Though the architecture must support these features, an operator may chose to support them or not, and a subscriber may be offered a choice of the features based upon the operators marking strategy. While this is a first cut feature set, it is expected ... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 5.3.1.4 Quality of Service (QoS) requirements | With respect to Quality of Service (QoS), the following requirements can be listed for the architecture: • It must provide set of policy mechanisms to provide and manage QoS for IPCablecom services over the access network. • It must provide priority admission control mechanisms for both upstream and downstream directio... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 5.3.1.5 Codec and media stream requirements | With respect to the codec and media stream requirements, the following requirements can be listed: • It must minimize the effects that delay, packet-loss, and jitter have on voice-quality in the IP telephony environment. • It must define a minimum set of audio codecs that must be supported on all IPCablecom endpoint de... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 5.3.1.6 Device provisioning and OSS requirements | With respect to device provisioning and the OSS, the following requirements can be listed: • It should support dynamic and static provisioning of customer premise equipment (MTA and CM). • Normal provisioning changes should not require a reboot of the MTA. • It should allow dynamic assignment and management of IP addre... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 5.3.1.7 Security requirements | The following security requirements can be listed: In the context of IPCablecom, security is not a good word to use, as it has been used to mean Lawful Intercept (as in national security) as well as subscriber and operator security and privacy. However, till now, no one has come up with a better word, so the context mu... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 5.3.1.8 Managed IP network goal | The managed IP network must be able to assume bounds on the QoS performance parameters, e.g. packet loss, for packets traversing the network. |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 5.3.2 Requirements from components | A question in general can be: are there any component level requirements? The J.arch document contains the following phrase: "This clause describes the functional components present in an IPCablecom network. Component descriptions are not intended to define or imply product implementation requirements but instead to de... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 5.3.2.1 Trust | The motto here is the famous "trust, but verify". Trust means that information is sent over channels that are assumed to be secure. In the PSTN this is gained more by technology than intent, as channels, particularly digital channels, are difficult to tap or intercept for bearer channels, and SS7 is very difficult to i... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 5.3.2.2 Subscriber side requirements | • IPCablecom MTA must support the J.112 Network Call Signalling (NCS) protocol. • An embedded MTA (E-MTA) is a single hardware device that incorporates a cable modem as well as an IPCablecom MTA component. • IPCablecom specifications currently only must support embedded MTAs; "stand alone" MTAs without CMs are thus not... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 5.3.2.3 MTA Functional requirements | The MTA functional requirements listed here are for information only, as the J.arch document does not cover the MTA requirements. But it is very necessary to understand what the MTA expects when trying to understand the architecture. Note that this is not a comprehensive MTA list; a large number of requirements and fea... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 5.3.2.4 Access Node (AN) MTA functional requirements | These are the requirements on IPCablecom from the Access Node: • It must support NCS/J.112/HFC based MTA subscriber access to the Managed IP network, including: - It must provide required QoS to the CM based upon policy configuration. - It must allocate upstream bandwidth in accordance to CM requests and network QoS po... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 5.3.2.5 Access Node (AN) MTA managed IP functional requirements | • It must support in the Managed IP network: - It must support the reservation of any backbone QoS and bandwidth necessary to complete the service reservation. - It must record usage of resources per call using IPCablecom Event Messages. |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 5.3.2.6 CMS Call agent functions | Call Agent functions are responsible for providing signalling services using the NCS protocol to the MTA. This is often called "line side" call processing, and includes the functions of: • It must implement call features, and manage subscriber access to other subscribers possibly over the network. • It must maintain ca... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 5.3.2.7 CMS Announcement controller functions | These are the requirements on the CMS for announcement services. The announcement server may optionally be network based using SS7 TCAP messages (possibly based on INAP). However, if it is an internal component, using IP RTP streams, then it must provide the features as listed below. In the future, it may provide video... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 5.3.2.8 Implicit CMS goal | "By centralising call state and service processing in the CMS, the service provider is in a position to centrally manage the reliability of the service provided. In addition the service provider gains full access to all software and hardware in the event that a defect that impacts subscriber services occurs. Software c... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 5.3.2.9 MGC requirements | This clause only contains a very small part of the MGC requirements. The MGC has the major responsibility of handling network signalling, which is covered in TGCP and ISTP in much more detail. Both the TGCP and ISTP are listed in following clauses of the present document. ETSI ETSI TR 102 019 V1.1.1 (2002-02) 23 The fo... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 5.3.2.10 MGC functions | This overview of MGC functions is only included for information to aid the understanding of the MGC functions. As with the MGC requirements, not all requirements are list here, and many more are in TGCP. In reality, the real purpose of the MGC is to support a 'global' view of trunks to the PSTN, providing a single (red... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 5.3.2.11 MG requirements | The MG requirements are: • It must provide bearer channel and may provide in-band signalling connectivity to the PSTN. • It must implement all the call state and intelligence and controls the operation of the Media Gateway through the TGCP protocol: this includes creation, modification and deletion of connections as we... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 5.3.2.12 MG functions | The following is a list of functions performed by the Media Gateway: • It must terminate and control physical circuits in the form of bearer channels from the PSTN. • It must discriminate between media and Channel Associated In-band signalling information from the PSTN circuit. • It must detect events on endpoints and ... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 5.3.2.13 SS7 signalling gateway functions | These are the SS7 signalling gateway functions. More information on this is to be found in the ISTP. • It must terminate physical SS7 signalling links. • It must implement security features. • It must terminate Message Transfer Part level 1, 2, 3. • It must implement MTP network management functions. • It must support ... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 5.3.2.14 PSTN signalling requirements | • It must support SS7 ISUP/TCAP/SCCP/MTP3, 2, 1: - The signalling gateway function only supports non-facility associated signalling in the form of SS7 (SS7). - ISUP and TCAP are both required, but not INAP or AIN (the MGC could use these but they are not mentioned in the Architecture). - It supports initialization, add... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 5.3.2.15 OSS requirements | With respect to IP/IETF servers, the following requirements can be listed: • The Ticket Granting Server must use a Kerberos server. A ticket contains information used to set up authentication, privacy, integrity and access control for the call signalling between the MTA and the CMS. • It must use a Dynamic Host Configu... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 5.3.2.16 Media streams: RTP | • IPCablecom must use the IETF standard RTP (RFC 1899 [8] - Real-time Transport Protocol) to transport all media streams in the IPCablecom network. • IPCablecom must use the RTP profile for audio and video streams as defined in IETF RFC 1890 [9]. |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 5.3.2.17 Provisioning | • MTA provisioning: - It must provision the MTA's devices and endpoints: provisioning includes: initialization; authentication; registration; other configuration functions. - It must use SNMPv3 to interface the MTA to element management systems for MTA device provisioning. NOTE: The SNMP v.3 managed object mode... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 5.3.2.18 Event management | • It must generate and store data records containing information about network usage and activities as sets of event messages to provide a complete record of the service. This complete record of the service is often referred to as a Call Detail Record (CDR). • It must offer Event Messages or CDRs may be sent to one or ... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 5.3.2.19 Quality of Service | |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 5.3.2.19.1 Static QoS | • IPCablecom Quality of Service signalling to the MTA may be handled at the application layer (SDP parameters), network layer 3 (RSVP), or at the data-link layer 2 (J.112 QoS). ETSI ETSI TR 102 019 V1.1.1 (2002-02) 26 |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 5.3.2.19.2 Dynamic QoS | • IPCablecom Dynamic QoS (D-QoS) must authorize resources at the time of the call to theft of service attack types: this includes: - Maximum Allowed QoS Envelope - The maximum allowed QoS envelope enumerates the maximum QoS resource (e.g., "2 grants of 160 bytes per 10 ms") the MTA is allowed to admit for a given media... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 5.3.2.20 Announcement options | • It must allow the MTA to play locally stored announcements to provide informative progress tones to the end user independently of the network state (e.g., congestion). • It must support simple, fixed-content announcements (e.g., all-lines-busy) stored at the Media Gateway to provide announcements to PSTN users. • It ... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 5.3.2.21 Security: Privacy and fraud prevention | • It must address both subscriber and operator needs. • It must specify security required for each external protocol interface. • It must consider authentication, access control, integrity, confidentiality and non-repudiation. • An IPCablecom protocol interface may employ zero, one or more of these services to address ... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 5.3.2.22 Time of day requirements | • In order to maintain service quality all network equipment clocks must be maintained to within 200 ms of Universal Time Co-ordinated (UTC). • It may use the Network Time Protocol (NTP); this is the "recommended" protocol for IPCablecom time synchronization. • All systems that generate billing event messages must sync... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 5.3.2.23 Clocks | • In order to minimize the overrun or under-run of play-out buffers due to the difference in clock speed between plesiochronous entities, all ANs must lock their downstream transmission rate to a clock derived from a source that reflects a Stratum-3 clock. • MTAs must use the downstream transmission rate to derive the ... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 5.3.2.24 IP addressing | |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 5.3.2.24.1 One CM and one MTA | • IPCablecom IP address must use IPv4: - All IPCablecom embedded MTAs must have two IP addresses: one for the CM and one for the MTA. - All IPCablecom embedded MTAs must have 2 MAC addresses: one for the CM and one for the MTA. • It must support a private IP address for the CM host function in the case where NAT transl... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 5.3.2.24.2 Dynamic IP addressing | • Since calls are based on a mapping of a subscriber's service to an endpoint identifier and an IP address, the operator must be able to configure the system to minimize changes in IP address during a call. NOTE: Fully Qualified Domain Name (FQDN) issues relating to DHCP and DNS are not part of the scope of the j.arch,... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 5.3.2.25 Packet prioritization | • Prioritization for QoS of packets over the managed IP backbone is out of scope and considered implementation dependent. • Prioritization for signalling packets is out of scope and considered implementation dependent: - TGCP address some of the issues; - ISTP uses SCTP to handle these issues. |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 5.3.2.26 Fax support | • IPCablecom must support real-time fax transmission. • Fax transmission must use ITU-T Recommendation G.711 [5] for audio encoding/decoding. • If a call is established using a compressed Codec, the embedded MTA must be instructed to look for fax tones. If fax tones are detected, the CMS must be notified and the MTA wi... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 5.3.2.27 Analogue modem support | • The MTA must detect modem tones and, when such tones are detected, the CMS must instruct the MTA to switch over to the G.711 Codec if it is not already in use. Note that this places a requirement on the embedded device to monitor the voice stream and to detect analogue modem tones. • It must support switching over to... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 6 Requirements obtained from J.istp | |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 6.1 Overview | |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 6.1.1 Scope | This clause describes the requirements obtained from reverse engineering the ITU-T J.istp document (J.165 [2]). The source document used has been written by the Study Group 9 of the ITU-T. The title of this file is "Revised Draft Recommendation J.165 (J.istp): IPCablecom signalling transport protocol", as of October 20... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 6.1.2 What is J.istp? | J.istp is an ITU-T version of the Internet Signalling Transport Protocol (ISTP) released in 1999 by Cablelabs. For the moment, this ISTP has been adapted by the ITU in draft j.istp. Note that, unlike TGCP, there is no API defined in ISTP only a protocol, since most current SS7 vendors supply their own API for TCAP and ... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 6.1.2.1 Note on SG and ISTP | A note on SG and ISTP: SG and ISTP are not the same thing: • The signalling gateway (SG) is a logical component (a set of equipment) that forms the single point of interface for SS7 messages to the PSTN and contains all layers of the SS7 stack; the MG is the interface for bearer channels only. • ISTP is a protocol impl... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 6.1.2.2 Protocol distribution in IPCablecom elements | Figure 3 shows the protocol distribution in IPCablecom elements: MPT1 MPT2 MPT3 Physical IP TCP SCTP TCAP ISUP SCCP ISTP Physical IP TCP SCTP ISTP TCAP ISUP ISTP-User (SG) ISTP-Users (CMS, MGC, etc) SS7 network IP based network Figure 3: Protocol distribution in IPCablecom elements |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 6.1.2.3 General ISTP functions | The general ISTP functions are: • Initialization. • Registration of circuit Ids. • Address mapping between SS7 and IP domains. • ISUP maps based on point code and circuit identification code. • TCAP maps based on point code and transaction ID. ETSI ETSI TR 102 019 V1.1.1 (2002-02) 30 • ISUP/TCAP message delivery using ... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 6.1.2.4 ISTP specification goals | • It must support cable companies' penetration into residential and business markets for multimedia services, including voice. • It must support a low cost replacement strategy for PSTN switching, peripheral, and control equipment using IP based technology. • It must support a network that can provide higher level feat... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 6.1.2.5 ISTP in decomposed IPCablecom gateway | SS7 Signaling Switched Circuit PSTN Signaling Gateway ISTP Media Gateway Controller ISTP Call Management Server ISTP Media Gateway Managed IP Network PCM trunks SS7 Links IP Connections Figure 4: ISP in decomposed IPCablecom gateway ETSI ETSI TR 102 019 V1.1.1 (2002-02) 31 |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 6.1.2.6 Areas beyond the scope of J.istp | • Address layer management (SNMP), security, and measurements covered in other IPCablecom Recommendations, but the SG must adhere to those requirements within the J.arch framework. • Implementation and vendor dependent issues, such as performance, functional distribution, network configuration, etc. • Details about CMS... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 6.1.2.7 ISTP and IETF | • ISTP uses IP, DNS, and a lot of IETF RFCs. • ISTP uses the SCTP for underlying transport. • However, ISTP currently does not use other SIGTRAN protocols, since they are not RFC status. • It has been proposed to use M3UA and possibly SUA. • Even if M3UA and SUA were used, most of ISTP still exist to handle the many re... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 6.2 J.istp: Technical requirements | |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 6.2.1 J.istp: Framework and architecture requirements | |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 6.2.1.1 High Level SG/ISTP requirements | • It should reduce the cost of deploying a SS7 based interface to the public network: - lower initial cost using standard interfaces with multi-vendor equipment selection; thus it must support certification and interoperability testing; - lower operation cost, using fewer point codes; - lower initial cost and operation... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 6.2.1.2 Support of J.arch framework service goals | ISTP and the SG must support J.arch/J.nsc service goals including: • Voice or other media content conversion. • Call control signalling. • Quality of service control. • Call control signalling interoperability with the existing public network. • Media interfaces to the existing public network. • Data transactions to pu... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 6.2.1.3 SG SS7 termination requirements | • The SG must appear as a normal SS7 endpoint to the connecting PSTN network. • The SG must terminate physical SS7 signalling links from the PSTN (A, F links). • The SG must ensure that the Gateway security is consistent with IPCablecom and SS7 network security requirements. • The SG must terminate Message Transfer Par... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 6.2.1.4 Functional SG signalling requirements | • It must transport "raw" ISUP and TCAP messages to IPCablecom components in their native format; it may "normalize a variant SS7 message to a ITU or ANSI standard format. • It must perform ISUP address mapping to support flexible mapping of Point Codes to the appropriate Media Gateway Controller (MGC). The addressed M... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 6.2.1.5 Functional SG interface requirements | • It must support the OSS back-office interfaces for SG configuration and capabilities. • It must support SNMPv3 based MIBs and operation, administration and management of SG configuration and capabilities. The requirement for SNMP is a j.arch requirement: the description of SG related MIBs is out of the scope of the p... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 6.2.1.6 Architecture Zone/Domain goals | • A SG may appear as a single point code to the SS7 network, where it is viewed as a "signalling endpoint", or may appear as multiple point codes and endpoints, running on a single SG element. • It must support multiple call models, vendor components, or versions in different IP based call agent components on the same ... |
878d19834f9835ca434f2b8023a1fef9 | 102 019 | 6.2.1.7 Reliable underlying transport | • It must support SS7 messages over IP on a managed IP network in a reliable and near real time fashion. It may use SCTP or TCP over a managed IP network. Note that it is the vendor and operator's responsibility to configure the selected stack and network to meet timing, reliability and security requirements for signal... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.