hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
26796e170892d4de841919772b78ef1c | 103 161-3 | 7.1.8 Fax Relay | IPCablecom needs to support fax interfaces since fax equipment continues to be used by both residential and business customers. The recommended solution for supporting fax is to employ Call Management Server or Media Gateway Controller controlled fax relay. Fax relay involves demodulating the T.30 transmission and send... |
26796e170892d4de841919772b78ef1c | 103 161-3 | 7.1.8.1 T.38 Over UDPTL | T.38 version 0 allows for a number of transport options including TCP and UDP. The UDP transport option is referred to as UDPTL in [20]. MTAs and Media Gateways shall support UDPTL. Within UDPTL, additional options allow support for redundancy or forward error correction. MTAs and Media Gateways shall support redundanc... |
26796e170892d4de841919772b78ef1c | 103 161-3 | 7.1.8.2 T.38 Over RTP | T.38 running over the RTP protocol as described in [20] is currently out of scope. |
26796e170892d4de841919772b78ef1c | 103 161-3 | 7.1.9 DTMF Relay | RFC 2833 [24] specifies in-band RTP payload formats and usage to carry DTMF, modem and fax tones, line states, and call progress tones across an IP network either as recognized "telephone events" or as a set of parameters defining a tone by its volume, frequency, modulation and duration of its components. Besides the t... |
26796e170892d4de841919772b78ef1c | 103 161-3 | 7.1.10 V.152 Transmission | IPCablecom needs to support modem equipment interfaces since many residential and business customers still make use of dial-up modem lines for various services. These services include dial-up network access for work, home security systems, and many home electronic devices. In addition, support for TTY is also necessary... |
26796e170892d4de841919772b78ef1c | 103 161-3 | 7.1.10.1 V.152 Transition Triggers | The following tones are all triggers for switching to voice band data transmission: 1 100 Hz (CNG), V.21 preamble, V.18 Annex A, 2 100 Hz (for example ANS also known as CED, ANSam, /ANS, /ANSam). If an MTA or Media Gateway detects V.18 Annex A or 2 100 Hz tone, and V.152 has been negotiated for the connection, the endp... |
26796e170892d4de841919772b78ef1c | 103 161-3 | 7.1.10.1.1 Considerations for Simultaneous T.38 and Voice Band Data Support | Certain signals that would cause a T.38 switch also cause a switch to voice band data. Since T.38 is more reliable and consumes less bandwidth than V.152 with redundancy, T.38 is the preferred method for transmitting fax calls. If both T.38 and V.152 have been specified by the CMS, the CMS preference for T.38 and V.152... |
26796e170892d4de841919772b78ef1c | 103 161-3 | 7.1.11 Security Considerations | V.152 uses RTP and RTCP for its transmission. The security requirements for RTP and RTCP defined in the security specifications [i.1] shall be followed. |
26796e170892d4de841919772b78ef1c | 103 161-3 | 7.2 Mandatory Codecs | The following codecs shall be supported in all MTAs and MGs. |
26796e170892d4de841919772b78ef1c | 103 161-3 | 7.2.1 G.711 | G.711 (both µ-law and A-law versions) [17] shall be supported in all MTAs and MGs. This codec provides toll-quality voice and is ubiquitous. It provides the "fallback" position for services such as fax, modem, and hearing-impaired services support, as well as common gateway transcoding support. In addition, G.711 is us... |
26796e170892d4de841919772b78ef1c | 103 161-3 | 7.3 Recommended Codecs | In addition to G.711, it is RECOMMENDED that MTAs and MGs also support at least one of the following codecs. |
26796e170892d4de841919772b78ef1c | 103 161-3 | 7.3.1 iLBC | iLBC [34], [35] should be supported in all MTAs and MGs. IPCablecom has as a mandate to provide toll or superior voice quality. iLBC is a mid-bitrate (13,3 kb/s and 15,2 kb/s), high-quality solution. When iLBC is supported, both the 20 ms and 30 ms frame size modes shall be supported. iLBC provides high quality, low-ba... |
26796e170892d4de841919772b78ef1c | 103 161-3 | 7.3.2 BV16 | BroadVoice16 [37], [38] should be supported in all MTAs and MGs. IPCablecom has as a mandate to provide toll or superior voice quality. BroadVoice16 (BV16) is a mid-bitrate, high-quality solution. BV16 provides high quality, low-bandwidth performance for on-net calls and ensures high performance for applications such a... |
26796e170892d4de841919772b78ef1c | 103 161-3 | 7.4 Optional Codecs | MTAs and MGs may support the following codecs. |
26796e170892d4de841919772b78ef1c | 103 161-3 | 7.4.1 G.728 | G.728 [22] may be supported in all MTAs and MGs. IPCablecom has as a mandate to provide toll or superior voice quality. G.728 provides high quality, low-bandwidth performance for on-net calls and ensures the highest possible performance for applications such as IVR systems. In addition, it provides superior background ... |
26796e170892d4de841919772b78ef1c | 103 161-3 | 7.4.2 G.729 Annex E | G.729 Annex E [23] may be supported in all MTAs. IPCablecom has as a mandate to provide toll or superior voice quality. G.729E is a mid-bitrate (11,8 kb/s), high-quality solution. G.729 Annex E provides high quality, low-bandwidth performance for on-net calls and ensures the highest possible performance for application... |
26796e170892d4de841919772b78ef1c | 103 161-3 | 7.4.3 G.722 | G.722 [42] is the earliest international standard on wideband speech coding. G.722 may be supported in wideband- capable MTAs and MGs. If G.722 is used, MTAs and MGs shall support 10 ms, 20 ms, and 30 ms packetization rates. G.722 is a multi-rate wideband speech codec for 16 kHz sampled signals. It has three selectable... |
26796e170892d4de841919772b78ef1c | 103 161-3 | 7.5 Optional Features | |
26796e170892d4de841919772b78ef1c | 103 161-3 | 7.5.1 Wideband Codecs | Given that the majority of early customers will be "black phone" users, support for wideband (i.e. greater than circuit voice bandwidth) codecs on either MTAs or MGs is not being mandated. However, some vendors optionally may choose to differentiate their product by selecting components that will support higher fidelit... |
26796e170892d4de841919772b78ef1c | 103 161-3 | 7.5.2 Optional Codecs | A vendor may supply any codecs not described herein. ETSI ETSI TS 103 161-3 V1.1.1 (2011-04) 25 |
26796e170892d4de841919772b78ef1c | 103 161-3 | 7.5.3 Voice Activity Detection (VAD) | A vendor may employ VAD to reduce bandwidth consumption. If employed, this capability shall be optional, allowing disabling. Some codecs have associated VAD implementations (e.g. G.729B), while many others do not (e.g. G.711, G.728, and G.722). In the latter cases, the VAD implementation shall adhere to the IMTC Voice-... |
26796e170892d4de841919772b78ef1c | 103 161-3 | 7.6 Session Description of Codecs | Session descriptor protocol (SDP) messages are used to describe multimedia sessions for the purposes of session announcement, session invitation, and other forms of multimedia session initiation. SDP descriptions are used in Network Call Signalling (NCS) [3]. This clause describes the required specification of the code... |
26796e170892d4de841919772b78ef1c | 103 161-3 | 7.6.1 iLBC Session Description | Parameters are mapped to SDP in a standard way. When conveying information by SDP, the encoding name shall be "iLBC" (the same as the MIME subtype [35]). If 20 ms frame size mode is used, local iLBC encoder shall send "mode" parameter in the SDP "a=fmtp" attribute by copying them directly from the MIME media type strin... |
26796e170892d4de841919772b78ef1c | 103 161-3 | 7.6.2 BV16 Session Description | Parameters are mapped to SDP in a standard way. When conveying information by SDP, the encoding name shall be "BV16" (the same as the MIME subtype 0). An example of the media representation in SDP for describing BV16 when 20 ms frame size mode is used might be: m=audio 3456 RTP/AVP 97 a=rtpmap: 97 BV16/8000 a=mptime: 2... |
26796e170892d4de841919772b78ef1c | 103 161-3 | 7.6.3 G.722 Session Description | Parameters are mapped to SDP in a standard way. When conveying information by SDP, the encoding name shall be "G722". G.722 has a static payload type of 9 as specified in [7]. ETSI ETSI TS 103 161-3 V1.1.1 (2011-04) 29 Following is an example of the media representation in SDP for describing G.722 (using static payload... |
26796e170892d4de841919772b78ef1c | 103 161-3 | 8 Video Requirements | |
26796e170892d4de841919772b78ef1c | 103 161-3 | 8.1 Overview | Packet-based video applications are one of the major potential enhancements to an IPCablecom service offering. Residential and business video conferencing, distance learning, and distance selling are just a few of the applications possible. Yet this technology is nascent, and the precise content, form, and technology d... |
26796e170892d4de841919772b78ef1c | 103 161-3 | 8.2 IPCablecom Video Devices | The IPCablecom Multimedia Terminal Adapter 2 (MTA-2) offers video in addition to audio communication. The functional requirements of MTA-2 will be specified in the future. |
26796e170892d4de841919772b78ef1c | 103 161-3 | 8.3 Video Encoder Requirements | The video encoder provides a self-contained digital bitstream that may be combined with a media bitstream and/or signals. The video decoder performs the reverse process. Pictures are sampled at an integer multiple of the video-line rate. This sampling clock and the digital network clock are asynchronous. The transmissi... |
26796e170892d4de841919772b78ef1c | 103 161-3 | 8.4 Video Format Requirements | As stated in ITU-T Recommendation H.263 [i.10]: "To permit a single recommendation to cover use in and between regions using 625- (PAL) and 525- (NTSC) line television standards, the source coder operates on pictures based on a common intermediate format (CIF). The standards of the input and output television signals, ... |
26796e170892d4de841919772b78ef1c | 103 161-3 | 8.5 H.263 Annexes | In addition to the H.263 baseline codec, there are several annexes that can improve the picture quality (with respect to frame rate, resolution, and bit-per-pixel coding efficiency). All of these annexes may be supported as optional codec features. Brief descriptions (from the H.263 recommendation) of each of the annex... |
26796e170892d4de841919772b78ef1c | 103 161-3 | 8.6 Multipoint Conferencing Support | In addition to the basic operation for encoding and decoding video streams, the MTA-2 may include support for multipoint conferences. If so, there are several commands particular to the video codec that enable multipoint support. These are: |
26796e170892d4de841919772b78ef1c | 103 161-3 | 8.6.1 Freeze Picture Request | Causes the decoder to freeze its displayed picture until a freeze picture release signal is received or a time-out period of at least six seconds has expired. The transmission of this signal is by external means. |
26796e170892d4de841919772b78ef1c | 103 161-3 | 8.6.2 Fast Update Request | Causes the encoder to encode its next picture in INTRA mode with coding parameters to avoid buffer overflow. The transmission method for this signal is by external means. |
26796e170892d4de841919772b78ef1c | 103 161-3 | 8.6.3 Freeze Picture Release | A signal from an encoder that has responded to a fast update request and allows a decoder to exit from its freeze picture mode and display decoded pictures in the normal manner. This signal is transmitted in the picture header of the first picture coded in response to the fast update request. ETSI ETSI TS 103 161-3 V1.... |
26796e170892d4de841919772b78ef1c | 103 161-3 | 8.6.4 Continuous Presence Multipoint (CPM) | In H.263, a negotiable CPM mode is provided in which up to four independent H.263 QCIF bitstreams can be multiplexed as independent "sub-bitstreams" into one new video bitstream. Capability exchange for this mode is signalled by external means. Each sub-bitstream is considered as a normal H.263 bitstream and therefore ... |
26796e170892d4de841919772b78ef1c | 103 161-3 | 8.7 Signalling Messages | At the time of this specification, the precise signalling protocol for all client devices has not been specified, but the following discussion demonstrates the necessary signals, whatever the protocol. H.245 [i.8] provides an example of essential signalling components vital to an MTA-2 video call. Not only can H.245 be... |
26796e170892d4de841919772b78ef1c | 103 161-3 | 9 RTCP Requirements and RTCP Usage | |
26796e170892d4de841919772b78ef1c | 103 161-3 | 9.1 RTP Requirements | The voice and fax/modem pass-through media flows shall be transported using IETF Real-Time Transport Protocol (RTP) and Real-Time Transport Control Protocol (RTCP) as defined in RFC 1889 [16] and RFC 1890 [7]. All IPCablecom devices supporting RTP (e.g. MTAs, trunking gateways, audio servers) shall support RTCP as defi... |
26796e170892d4de841919772b78ef1c | 103 161-3 | 9.2 RTCP Requirements | To facilitate vendor interoperability, the following RTCP profile has been defined for IPCablecom-compliant endpoints. In the event that a discrepancy arises between the RFCs and this profile, this profile will take precedence. |
26796e170892d4de841919772b78ef1c | 103 161-3 | 9.2.1 General Requirements of the IPCablecom RTCP Profile | IPCablecom endpoints shall send RTCP messages, as described in RFC 1889 [16] and RFC 1890 [7] and profiled below. Endpoints may start transmitting RTCP messages as soon as the RTP session has been established, even if RTP packets are not being sent or received. An RTP session is considered established once each endpoin... |
26796e170892d4de841919772b78ef1c | 103 161-3 | 9.2.2 Security Requirements for RTP and RTCP in IPCablecom | IPCablecom endpoints shall not conform to the security requirements described in the RTP/RTCP RFC and drafts. Instead, IPCablecom endpoints shall implement RTP and RTCP security as specified in the IPCablecom Security Specification [i.1]. |
26796e170892d4de841919772b78ef1c | 103 161-3 | 9.2.3 Extended RTCP Reports | The RTCP XR VoIP Metrics Report Block as defined in [29] shall be sent by endpoints if negotiated on a given connection as defined in IPCablecom Network Based Call Signalling Protocol Specification [3] and Trucking Gateway Control Protocol Specification [21]. IPCablecom endpoints may send other RTCP XR payload types. I... |
26796e170892d4de841919772b78ef1c | 103 161-3 | 9.2.3.1 Reporting Call Quality Metrics using RTCP XR | |
26796e170892d4de841919772b78ef1c | 103 161-3 | 9.2.3.1.1 RTCP XR VoIP Metrics Requirements | The RTCP XR VoIP Metrics [29] report provides a set of performance metrics that can be helpful in diagnosing problems affecting call quality. RTCP XR is a media path reporting protocol, i.e. messages are exchanged between endpoints, however they may be captured by intermediate network probes or analyzers, or potentiall... |
26796e170892d4de841919772b78ef1c | 103 161-3 | 9.2.3.1.2 Definition of Metrics related to Packet Loss and Discard | The VoIP Metrics [29] payload contains six metrics related to packet or frame loss and discard. An average packet loss rate and an average packet discard rate report the proportion of packets lost or discarded on the call to date. A set of four burst parameters report the distribution of lost and discarded packets occu... |
26796e170892d4de841919772b78ef1c | 103 161-3 | 9.2.3.1.3 Definition of Metrics Related to Delay | The VoIP Metrics payload includes two delay metrics [29]. The Round Trip Delay is the delay between RTP interfaces, as typically measured using RTCP Sender Report (SR) or Receiver Report (RR) [16]. The End System Delay incorporates the vocoder encoding and decoding delay, the packetization delay, and the current nomina... |
26796e170892d4de841919772b78ef1c | 103 161-3 | 9.2.3.1.4 Definition of Metrics related to Signal | The Signal Level, Noise Level and estimated Residual Echo Return Loss are intended to support the diagnosis of problems related to loss plan or PSTN echo. The intent is to report useful information that would typically be available from a vocoder or echo canceller rather than to impose the overhead of additional measur... |
26796e170892d4de841919772b78ef1c | 103 161-3 | 9.2.3.1.5 Definition of Metrics related to Call Quality | Call quality metrics are useful when assessing the overall quality of a call [29]. A listening quality metric represents the effects of vocoder distortion, lost and discarded packets, noise and signal level on user perceived quality. A conversational quality metric also includes the effects of delay and echo on user pe... |
26796e170892d4de841919772b78ef1c | 103 161-3 | 9.2.3.1.6 Definition of Parameters related to endpoint configuration | These parameters in table 13 describe some key configuration parameters of the IPCablecom endpoint, that are useful in monitoring service quality and identifying some types of configuration related problems. ETSI ETSI TS 103 161-3 V1.1.1 (2011-04) 41 Table 13: Parameters related to endpoint configuration METRIC Descrip... |
fe53979c5804215b25abea6103facc0e | 103 129 | 1 Scope | The present document describes the modulation, channel coding and signalling protocol system (denoted the "System", "DVB Carrier Identification" or "DVB-CID" for the purposes of the present document) intended for the identification of the host carrier it belongs to. The system uses Binary Phase Shift Keying (BPSK) spre... |
fe53979c5804215b25abea6103facc0e | 103 129 | 2 References | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the reference document (including any amendments) applies. Referenced documents which ar... |
fe53979c5804215b25abea6103facc0e | 103 129 | 2.1 Normative references | The following referenced documents are necessary for the application of the present document. [1] IEEE™ standards association, EUI-64 Guidelines: "Guidelines for 64-bit Global Identifier (EUI-64™)" Registration Authority. NOTE: Available at: http://standards.ieee.org/develop/regauth/tut/eui64.pdf. [2] Recommendation IT... |
fe53979c5804215b25abea6103facc0e | 103 129 | 2.2 Informative references | The following referenced documents are not necessary for the application of the present document but they assist the user with regard to a particular subject area. [i.1] IETF RFC 2373 (July 1998): "IP Version 6 Addressing Architecture". ETSI ETSI TS 103 129 V1.1.2 (2014-03) 7 [i.2] National Marine Electronic Associatio... |
fe53979c5804215b25abea6103facc0e | 103 129 | 3 Definitions, symbols and abbreviations | |
fe53979c5804215b25abea6103facc0e | 103 129 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: CID carrier: transmission signal that transports the Content ID content ID: possible content of information field carried by CID NOTE: As described in clause 4.2. DVB CID global unique identifier: unique identifier for the modulator th... |
fe53979c5804215b25abea6103facc0e | 103 129 | 3.2 Symbols | For the purposes of the present document, the following symbols apply: α roll-off factor A the signal identified by the CID B the signal being interfered ∗ B C ,0 [W/Hz] signal B power spectral density, at the E/S where the CID is decoded ci chip comp_factor_CIDA [dB] compensation factor to be added to the link budget ... |
fe53979c5804215b25abea6103facc0e | 103 129 | 3.3 Abbreviations | For the purposes of the present document, the following abbreviations apply: ASCII American Standard Code for Information Interchange BCD Binary Coded Decimal BCH Bose, Ray-Chaudhuri, Hocquenghem code BPSK Binary Phase Shift Keying CID Carrier IDentification CRC Cyclic Redundancy Check CRC8 Cyclic Redundancy Check with... |
fe53979c5804215b25abea6103facc0e | 103 129 | 4 Host Carrier identification information | The following specifies the host carrier identification information that is transported by the CID carrier. The information that identifies the host carrier contains mandatory the DVB CID Global Unique Identifier, fixed by the equipment manufacturer, that shall not be editable by the user, and the CID format revision c... |
fe53979c5804215b25abea6103facc0e | 103 129 | 4.1 DVB CID Global Unique Identifier | The 64-bit DVB CID Global Unique Identifier is based on the IEEE-defined 64-bit extended unique identifier (EUI-64 [1]) and is sent in two parts of 32 bits. It can be derived from a 48 bit MAC address or a 48 bit Space Data Association modulator identifier as described below. A 48 bit MAC address assigned to a modulato... |
fe53979c5804215b25abea6103facc0e | 103 129 | 4.2 Content ID table | The Content ID table (see table 1) lists the possible content of the Information field carried by CID. The CID format revision code (Content ID 0) shall be transmitted; other information is optional, and the Content ID value indicates the corresponding Information field content. If the telephone is sent, all 3 Telephon... |
fe53979c5804215b25abea6103facc0e | 103 129 | 5 DVB CID construction | The Carrier ID Transmitter Block diagram is shown in figure 1. It shall be possible to disable the CID in an equipment by hardware or software. Figure 1: An example Carrier ID transmission block diagram ETSI ETSI TS 103 129 V1.1.2 (2014-03) 13 |
fe53979c5804215b25abea6103facc0e | 103 129 | 5.1 DVB CID frame construction | |
fe53979c5804215b25abea6103facc0e | 103 129 | 5.1.1 DVB CID Frame format | The syntax and semantics of the CID_Frame are defined in table 3. This CID_Frame will contain the DVB CID Global Unique Identifier and 2 content ID's. Table 3: Syntax and semantics Syntax No. of bits Mnemonic CID_Frame () { unique_word 22 bslbf id_high 32 uimsbf content_id_1 5 uimsbf content_id_information_1 24 uimsbf ... |
fe53979c5804215b25abea6103facc0e | 103 129 | 5.1.2 CRC8 | The calculation below for CRC-8 shall be used for crc_1 and crc_2 in CID_Frame (see clause 5.1.1 and table 3), and for the creation of the check_digits_octet when displaying a DVB CID Global Unique Identifier (see clause 4.1). The CRC8 is a systematic 8-bit CRC encoder. The generator polynomial shall be: GCRC8(X) = (X5... |
fe53979c5804215b25abea6103facc0e | 103 129 | 5.1.3 BCH FEC | The FEC is a (127, 85) 6-error correcting systematic BCH code, shortened by 16 bits to (111, 69). The encoding operation is defined as an operation involving polynomials over GF(2). The first data bit sent is the coefficient of the highest degree term in the degree 68 data polynomial D(x). The first parity bit sent is ... |
fe53979c5804215b25abea6103facc0e | 103 129 | 5.2 Scrambling | All bits in a CID_Frame except the unique word bits are scrambled. The scrambling polynomial is: x^9 + x^5 + 1. The initial state is 0x41. The feedback value x^9 + x^5 is the output. The scrambler does not advance over the unique words. The scrambler is reset to the initial state at the start of each CID_Frame. 0 0 1 0... |
fe53979c5804215b25abea6103facc0e | 103 129 | 5.3 Repetition | The scrambled CID bits (unique word and scrambled bits) are repeated 4 times. Unique Word (22 bits) Global Unique Identifier_high (32 bits) Content ID_1 type (5 bits) Information1 (24 bits) CRC 1 (8 bits) FEC 1 (42 bits) Global Unique Identifier_low (32 bits) Content ID_2 type (5 bits) Information 2 (24 bits) CRC 2 (8 ... |
fe53979c5804215b25abea6103facc0e | 103 129 | 5.4 Differential encoder | All repeated CID bits are differentially encoded. Differential Encoder Z-1 Input NOTE Unique word bits are also differentially encoded. Figure 5: Symbol Differential Encoder |
fe53979c5804215b25abea6103facc0e | 103 129 | 5.5 Chipping | Chipping is applied on every bit after differential encoding. The chipping ratio (spreading) is 4 096 chips/bit at all supported symbol rates. Each bit is chipped using the same 4 096 bit pattern. The chipping pattern is created using a LFSR polynomial of x15 + x14 + 1 with an initial state of [0 1 0 1 0 0 0 0 1 0 0 1 ... |
fe53979c5804215b25abea6103facc0e | 103 129 | 5.6 Chip mapping into BPSK constellation | After chipping, each chip ci of the sequence of CID_frames shall be mapped into BPSK constellation, generating a modulation symbol yi as a complex vector in the format (I,Q) (I being the in-phase component and Q the quadrature component). Chip mapping into the BPSK constellation shall follow figure 7. The normalized av... |
fe53979c5804215b25abea6103facc0e | 103 129 | 5.7 Nyquist filter | After mapping into constellation, the signal shall be square root raised cosine filtered. The roll-off factor shall be α = 0,35. The baseband square root raised cosine filter shall have a theoretical function defined by the following expression: 1 ) ( = f H for ( ) α − < 1 N f f 2 1 2 sin 2 1 2 1 ) ( ⎪⎭ ⎪⎬ ⎫ ⎪⎩ ⎪⎨ ⎧ ⎥ ... |
fe53979c5804215b25abea6103facc0e | 103 129 | 5.8 Gain adjust | A gain adjust has to be performed in order to produce a constant power spectral density of the DVB CID signal relative to the power spectral density of the center of the host carrier at the level as detailed in table 6. The power spectral density accuracy shall be within ±0,5 dB. ETSI ETSI TS 103 129 V1.1.2 (2014-03) 1... |
fe53979c5804215b25abea6103facc0e | 103 129 | 5.9 Complex Mix | At the output of the modulator the carrier ID signal is sent at +220 Hz offset when the modulator is configured not to introduce a spectrum inversion in the host carrier signal. At the output of the modulator the carrier ID signal is sent at -220 Hz offset when the modulator is configured to introduce a spectrum invers... |
fe53979c5804215b25abea6103facc0e | 103 129 | 6 DVB CID carrier phase noise specification | For chip rate 224 kHz (host carrier symbol rate ≥ 512 kBd) the close-in TX phase noise for the DVB CID signal shall be as specified in table 7, which extends the mask in [i.3] below 10 Hz maintaining 1/f3 slope down to 1 Hz. For chip rate 112 kHz (host carrier symbol rate < 512 kBd) the close-in TX phase noise for the ... |
56a9d5a3814aade3d36313e0d52e081b | 103 161-1 | 1 Scope | The present document, provides an overview of the standards in TS 103 161 series. |
56a9d5a3814aade3d36313e0d52e081b | 103 161-1 | 2 References | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the reference document (including any amendments) applies. Referenced documents which ar... |
56a9d5a3814aade3d36313e0d52e081b | 103 161-1 | 2.1 Normative References | The following referenced documents are necessary for the application of the present document. Not applicable. |
56a9d5a3814aade3d36313e0d52e081b | 103 161-1 | 2.2 Informative references | The following referenced documents are not necessary for the application of the present document but they assist the user with regard to a particular subject area. [i.1] ETSI TS 101 909-3: "Access and Terminals (AT); Digital Broadband Cable Access to the Public Telecommunications Network; IP Multimedia Time Critical Se... |
56a9d5a3814aade3d36313e0d52e081b | 103 161-1 | 3 Definitions and abbreviations | |
56a9d5a3814aade3d36313e0d52e081b | 103 161-1 | 3.1 Definitions | For the purposes of the present document, the terms and definitions apply: IPCablecom: ETSI deliverables including an architecture and a series of specifications that enable the delivery of real time services (such as telephony) over the cable television networks using cable modems |
56a9d5a3814aade3d36313e0d52e081b | 103 161-1 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: CMS Call Management Server CMSS Call Management Server Signaling CMTS Cable Modem Termination System DTMF Dual Tone Multi Frequency E-MTA Embedded Media Terminal Adapter IP Internet Protocol IVR Interactive Voice Response MGCI Media Gateway Co... |
56a9d5a3814aade3d36313e0d52e081b | 103 161-1 | 4 Overview of the multi-part deliverable | The ETSI TS 103 161 series together present an IPCablecom 1.5 network architecture for the provision of voice and multimedia IP services. The TS 103 161 series of standards represent a cohesive set of interwoven specifications that jointly evolved to present different phases of IPCablecom 1.5 network developments. Chan... |
56a9d5a3814aade3d36313e0d52e081b | 103 161-1 | 4.1 Part 1: Overview | TS 103 161-1 is the present document. ETSI ETSI TS 103 161-1 V1.1.1 (2011-06) 10 4.2 Part 2: Architectural framework for the delivery of time critical services over Cable Television networks using cable modems TS 103 161-2 [i.6] defines architecture framework for IPCablecom 1.5 networks including all major system compo... |
56a9d5a3814aade3d36313e0d52e081b | 103 161-1 | 4.4 Part 4: Network Call Signalling Protocol | TS 103 161-4 [i.8] defines a profile of the Media Gateway Controller Protocol (MGCP) for IPCablecom 1.5 embedded clients, MGCP is a call signalling protocol for use in a centralized call control architecture, and assumes relatively simple client devices. The call signalling protocol is one layer of the overall IPCablec... |
56a9d5a3814aade3d36313e0d52e081b | 103 161-1 | 4.6 Part 6: Event Message Specification | TS 103 161-6 [i.10] defines the concept of Event Messages used to collect usage for the purposes of billing within the IPCablecom 1.5 architecture. It details the protocol used to carry these messages, defines the various Event Messages, lists the attributes each Event Message contains, and lists the required and optio... |
56a9d5a3814aade3d36313e0d52e081b | 103 161-1 | 4.8 Part 8: Network Call Signalling (NCS) MIB Requirements | TS 103 161-8 [i.12] defines the MIB module in full which supplies the basic management object for the IPCablecom 1.5 NCS protocol. |
56a9d5a3814aade3d36313e0d52e081b | 103 161-1 | 4.9 Part 9: Security | TS 103 161-9 [i.13] defines the Security architecture, protocols, algorithms, associated functional and technological requirements that provide for the security of the IPCablecom 1.5 network. |
56a9d5a3814aade3d36313e0d52e081b | 103 161-1 | 4.10 Part 10: Management Information Base (MIB) Framework | TS 103 161-10 [i.14] describes the framework in which IPCablecom 1.5 MIBs are defined. It provides information on the management requirements of IPCablecom specified devices and functions, and how these requirements are supported in the MIB. It is intended to support and complement the actual MIB documents, which are i... |
56a9d5a3814aade3d36313e0d52e081b | 103 161-1 | 4.11 Part 11: Media terminal adapter (MTA) device provisioning | TS 103 161-11 [i.15] defines the protocol mechanisms for provisioning of an IPCablecom 1.5 embedded-MTA device by a single provisioning and network management provider. |
56a9d5a3814aade3d36313e0d52e081b | 103 161-1 | 4.12 Part 12: Management Event Mechanism | TS 103 161-12 [i.16] defines the Management Event Mechanism that IPCablecom 1.5 elements can use to report asynchronous events that indicate malfunction situations and notifications about important non-fault situations. Events are defined in this part as conditions requiring the reporting of information to management s... |
56a9d5a3814aade3d36313e0d52e081b | 103 161-1 | 4.13 Part 13: Trunking Gateway Control Protocol - MGCP option | TS 103 161-13 [i.17] describes the Trunking Gateway Control Protocol (TGCP) profile of an application programming interface (MGCI) and a corresponding protocol (MGCP) for controlling trunking gateways from external call control elements. A trunking gateway is a network element that provides analog, emulated analog, or ... |
56a9d5a3814aade3d36313e0d52e081b | 103 161-1 | 4.15 Part 15: Analog Trunking for PBX Specification | TS 103 161-15 [i.19] defines extensions to the IPCablecom Network-based Call Signaling (NCS) protocol to support the analog trunking for PBX interfaces on an embedded Voice over IP client device in a IPCablecom environment. It describes the functional requirements for an embedded client to support one-way incoming, one... |
56a9d5a3814aade3d36313e0d52e081b | 103 161-1 | 4.16 Part 16: Signalling for Call Management Server | TS 103 161-16 [i.20] describes the IPCablecom Call Management Server (CMS) to CMS Signalling protocol intended for use by a CMS to communicate with another CMS in order to support packet-based voice and other real-time multimedia applications. This part defines a profile of the IETF SIP protocol for use within IPCablec... |
56a9d5a3814aade3d36313e0d52e081b | 103 161-1 | 4.17 Part 17: CMS Subscriber Provisioning Specification | TS 103 161-17 [i.21] defines the interface used between the Call Management Server (CMS) and Provisioning Server (PS) for the exchange of service provisioning information. The interface employs a Web Service model. Specified in Web Service Description Language 1.1 (WSDL 1.1) [i.4], the interface transports XML encoded ... |
56a9d5a3814aade3d36313e0d52e081b | 103 161-1 | 4.18 Part 18: Media Terminal Adapter Extension MIB | TS 103 161-18 [i.22] defines the Media terminal adapter Extension MIB which includes new objects that are being introduced beyond IPCablecom 1.0 for MTA. 4.19 Part 19: IPCablecom Audio Server Protocol Specification - MGCP option TS 103 161-19 [i.23] defines a set of signalling protocols that are used to provide announc... |
56a9d5a3814aade3d36313e0d52e081b | 103 161-1 | 4.20 Part 20: Management Event MIB Specification | TS 103 161-20 [i.24], Management Event MIB, provides a common data and format definition for events (informative, alarm, etc.). It also specifies by what means events are transmitted. Use of a common event mechanism facilitates management of the MTA in a multi-vendor environment and provides a standard means to impleme... |
56a9d5a3814aade3d36313e0d52e081b | 103 161-1 | 4.21 Part 21: Signalling Extension MIB Specification | TS 103 161-21 [i.25] defines the IPCablecom 1.5 IPCablecom Extension Signaling MIB. New objects that are being introduced beyond IPCablecom 1.0 for Signaling MIBS are grouped in this document. ETSI ETSI TS 103 161-1 V1.1.1 (2011-06) 14 History Document history V1.1.1 June 2011 Publication |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 1 Scope | The present document defines an electronic interface between two systems for the exchange of information relating to the establishment and management of lawful required action, typically Lawful Interception. Typically this interface would be used between on one side, a Communications Service Provider and on the other s... |
976608640a22d1bd9d51b7e2a9dc8dd6 | 103 120 | 2 References |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.