hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
6c8062f076f6234917e5d886e07a5663 | 103 143 | 6.1.9 CRS transfer between GLDBs | The CRS can be transferred from the responsibility of one GLDB to another GLDB to avoid CRS spectrum usage interruption for making CRS registration and authentication again at the destination GLDB. The procedure of CRS transfer from one GLDB to another GLDB is shown in Figure 6.11. ETSI ETSI TS 103 143 V1.1.1 (2015-01)... |
6c8062f076f6234917e5d886e07a5663 | 103 143 | 6.2 Flow charts for determining the available channels of a CRS | This clause shows the flow charts which give the operation sequences of a database in determining the operational parameters of a CRS. There are two variants of the operation sequences based on how incumbents' information is exchanged. Figure 6.12 shows the case when databases synchronize their incumbent information. F... |
6c8062f076f6234917e5d886e07a5663 | 103 143 | 7 Overview on GLDB Functional requirements | From the above described procedures the following functional requirements can be derived: 1. If incumbent's information is shared among GLDBs, a GLDB shall identify incumbents under the management of other GLDBs whose coverage area is potentially interfered by the CRS managed by the said GLDB. 2. If incumbent's informa... |
00b8be8005f8d11eff35f07711becee2 | 103 161-19 | 1 Scope | The present document describes the architecture and protocols that are required for playing announcements in Voice- over-IP (VoIP) IPCablecom networks. Announcements are typically needed for calls that do not complete. Additionally, they may be used to provide enhanced information services to the caller. Different carr... |
00b8be8005f8d11eff35f07711becee2 | 103 161-19 | 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... |
00b8be8005f8d11eff35f07711becee2 | 103 161-19 | 2.1 Normative references | The following referenced documents are necessary for the application of the present document. [1] ETSI TS 103 161-6: "Access, Terminals, Transmission and Multiplexing (ATTM); Integrated Broadband Cable and Television Networks; IPCablecom 1.5; Part 6: Event Message Specification". [2] IETF RFC 3435: "Media Gateway Contr... |
00b8be8005f8d11eff35f07711becee2 | 103 161-19 | 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 103 161-13: "Access, Terminals, Transmission and Multiplexing (ATTM); Integrated Broadband Cable and Television Networks; IPCablecom 1.5; Part... |
00b8be8005f8d11eff35f07711becee2 | 103 161-19 | 3 Definitions and abbreviations | |
00b8be8005f8d11eff35f07711becee2 | 103 161-19 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: announcement server: also known as audio servers, Announcement Servers are network components that manage and play informational tones and messages in response to events that occur in the network NOTE: Most announcements are media stre... |
00b8be8005f8d11eff35f07711becee2 | 103 161-19 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: AAU Advanced Audio Server ABNF Augmented Backus Naur Form ACK Acknowledgement ANC Announcement Controller ANP Announcement Player ASP Audio Server Protocol ASR Automatic Speech Recognition BAU Basic Audio Server BNF Backus Naur Form CMS Call M... |
00b8be8005f8d11eff35f07711becee2 | 103 161-19 | 4 Void | |
00b8be8005f8d11eff35f07711becee2 | 103 161-19 | 5 Technical Overview | The present document defines a suite of signalling protocols for providing announcement and media services in an IPCablecom network. This clause: • defines the architectural requirements for providing IPCablecom announcement and media services; • defines and categorizes announcement and media types; • defines the compo... |
00b8be8005f8d11eff35f07711becee2 | 103 161-19 | 5.1 Architectural Requirements | The architectural requirements and assumptions for providing Audio and Media Services for a IPCablecom Network are listed below. These requirements are based upon the specifications and technical reports that define the IPCablecom architecture. ETSI ETSI TS 103 161-19 V1.1.1 (2011-10) 11 |
00b8be8005f8d11eff35f07711becee2 | 103 161-19 | 5.1.1 Call Destination | The Audio Server Specification must define how announcements are provided for IPCablecom on-net to off-net and on- net to on-net calls. NOTE: Announcements for off-net to on-net calls will usually be handled by the PSTN as a result of SS7 clearing messages. However when appropriate, they also may be played from the IPC... |
00b8be8005f8d11eff35f07711becee2 | 103 161-19 | 5.1.2 Media Formats | A Media Player must be able to generate the required announcements in any of the code formats required by the IPCablecom Codec specification [3]. |
00b8be8005f8d11eff35f07711becee2 | 103 161-19 | 5.1.3 Security | Audio shall be signalled and played in a secure manner. Media Player Controllers and Media Players shall support the security protocols defined in the IPCablecom Security specification [4]. |
00b8be8005f8d11eff35f07711becee2 | 103 161-19 | 5.1.4 Operational Support Systems | Media Player Controllers shall support the IPCablecom billing and event message protocols as defined in [1], as applicable to the applications they support. No requirement has been identified for support of event reporting by the Media Player. |
00b8be8005f8d11eff35f07711becee2 | 103 161-19 | 5.2 Announcement Definitions | Announcements can be divided into four distinct categories: tones, fixed-content, variable content, and interactive announcements. |
00b8be8005f8d11eff35f07711becee2 | 103 161-19 | 5.2.1 Tones | Includes tones such as reorder, busy and ring back. See [i.2] and [i.1] for details. |
00b8be8005f8d11eff35f07711becee2 | 103 161-19 | 5.2.2 Fixed-content Announcements | Fixed-content Announcements consist of audio messages with fixed-content that require no user interaction. For example, "Your call did not go through. Please hang up and try your call again." |
00b8be8005f8d11eff35f07711becee2 | 103 161-19 | 5.2.3 Variable Content Announcements | Variable Content Announcements are messages that contain a customizing parameter(s) yet require no user interaction. For example, "The number you have dialled, 321-9876, has been changed. The new number is 321-6789." |
00b8be8005f8d11eff35f07711becee2 | 103 161-19 | 5.2.4 Interactive Announcements | Interactive Announcements are announcements that require user interaction, DTMF (Dual Tone Multi-Frequency) or IVR. For example, "The number you have dialled, 541-321-9876, has been changed. The new number is 541-321-6789. To be connected to the new number, at a cost of thirty-five cents, please press 1." |
00b8be8005f8d11eff35f07711becee2 | 103 161-19 | 5.2.5 Naming Conventions for Endpoint Identifiers | A flat name space for endpoints is used, with audio ports indicated by the prefix aud and the port number, e.g. aud/12@audio-server-3.whatever.net. Wildcards ($, *) may be used in place of the port numbers in accordance with standard NCS rules for wild card use. ETSI ETSI TS 103 161-19 V1.1.1 (2011-10) 12 Systems that ... |
00b8be8005f8d11eff35f07711becee2 | 103 161-19 | 5.3 Interfaces | The IPCablecom Audio Server Specification defines a set of interfaces between the components responsible for providing audio services. Figure 12 illustrates the interfaces between these components. Only where an interface is exposed is it expected to meet IPCablecom specification requirements. Media Player (MP) CMS Med... |
00b8be8005f8d11eff35f07711becee2 | 103 161-19 | 6 Ann-1 Interface: CMS-MTA and MGC-MG | The CMS-MTA and MGC-MG announcement interfaces are implemented by the Legacy Audio Package of the NCS/TGCP protocol, which provides the playback of tones and fixed-content announcements to the end-users. |
00b8be8005f8d11eff35f07711becee2 | 103 161-19 | 6.1 CMS-MTA Interface | Each MTA in the network may store a predefined set of simple announcements locally. When an announcement is needed, the CMS will decide if it should instruct the MTA to play a local announcement or set up a connection between the MTA and a Network MP and have the announcement played over the network. Playing simple ann... |
00b8be8005f8d11eff35f07711becee2 | 103 161-19 | 6.1.1 Announcement List | The MTA may store and play a defined set of announcements for common network situations. These announcements may be played using the Announcement Server Package defined in RFC 3435 [2], using URI (Universal Resource Identifiers) to identify the announcements. Cached versions of all announcement URIs should be refreshed... |
00b8be8005f8d11eff35f07711becee2 | 103 161-19 | 6.2 MGC-MG Interface | The MG announcement interface (Ann-1) allows for the MGC to request the MG play fixed-content announcements to PSTN end-users. The MGC/MG announcement interface package does not specify any standard announcements to be stored locally in the MG. All announcements are provisioned dynamically and are referenced accordingl... |
00b8be8005f8d11eff35f07711becee2 | 103 161-19 | 7 Ann-2 interface: MPC-MP | |
00b8be8005f8d11eff35f07711becee2 | 103 161-19 | 7.1 Introduction | An MP (Media Player) is a shared resource in the IPCablecom Network that can be instructed to provide media services to an end-user or terminal. These services include streaming fixed-content, variable content and interactive announcements to IPCablecom subscribers. For example, the MP is responsible for playing prompt... |
00b8be8005f8d11eff35f07711becee2 | 103 161-19 | 7.2 Audio Package Concepts | The Base and Advanced Audio Packages support both simple and complex audio structures. A simple audio structure might be a single announcement such as "Welcome to Bell South's Automated Directory Assistance Service." A more complex audio structure might consist of an announcement followed by voice variable followed by ... |
00b8be8005f8d11eff35f07711becee2 | 103 161-19 | 7.2.1 Understanding Audio Segments | An audio segment is a reference that resolves to one or more audio recordings. There are four types of audio segments: Physical: A physical segment is the simplest type of segment, a single recording. The recording could be a single word, such as "one", or an extended block of speech, such as "Our office is closed at t... |
00b8be8005f8d11eff35f07711becee2 | 103 161-19 | 7.2.2 Segment Identifiers | Provisioned segments and segments recorded at runtime are identified by URIs as defined in RFC 2396, [i.3] Uniform Resource Identifiers: Generic Syntax. A URI can be a simple name or it can be a URL. Three URL schemes are allowed: the file: scheme, the ftp:scheme, and the http: scheme. The file: scheme is used for audi... |
00b8be8005f8d11eff35f07711becee2 | 103 161-19 | 7.2.3 Segment Life | Physical segments may be provisioned or they may be recorded during the course of a call. A physical segment recorded during the course of a call can be either transient or persistent. A transient physical segment lasts only for the duration of the call during which it was recorded. A persistent physical segment lasts ... |
00b8be8005f8d11eff35f07711becee2 | 103 161-19 | 7.2.4 Nested Sets And Sequences | Nested definition of both sets and sequences is allowed, i.e. it is legal to define a set of sets or a sequence of sequences. In addition, audio structures may also be specified by intermixing sets and sequences, and it is possible to specify a set of sequences or a sequence containing one or more set elements. Direct ... |
00b8be8005f8d11eff35f07711becee2 | 103 161-19 | 7.2.5 Sequence Example | In the following example, a provisioner has provisioned one physical segment and two variable segments and has provisioned a sequence, http:/mysegment, which is an ordered list of the three segments. The sequence when played speaks the following: "Today's date is <weekday> <date>." Figure 3: Sequence Example |
00b8be8005f8d11eff35f07711becee2 | 103 161-19 | 7.2.6 Set Example | To support an application which plays a particular piece of audio in either Arabic, Welsh, or Tibetan, a provisioner could define a set with the pre-defined selector, "lang", and would use define three of the possible values for that selector, "ara", "cym", and "tib". The provisioner would provision three audio segment... |
00b8be8005f8d11eff35f07711becee2 | 103 161-19 | 7.2.7 Set With Nested Sequence Example | In this example, the provisioner has provisioned three physical segments, one in Arabic, one in Welsh, and one in Tibetan, and the provisioner has also provisioned three date variables. Using these six segments the provisioner has provisioned three sequences, each consisting of a physical segment followed by a date var... |
00b8be8005f8d11eff35f07711becee2 | 103 161-19 | 7.3 Base Audio Package | |
00b8be8005f8d11eff35f07711becee2 | 103 161-19 | 7.3.1 Abstract | This event package provides support for the standard IVR operations of PlayAnnouncement, PlayCollect, and PlayRecord. It supports direct references to simple audio as well as indirect references to simple and complex audio. It provides audio variables, control of audio interruptibility, digit buffer control, special ke... |
00b8be8005f8d11eff35f07711becee2 | 103 161-19 | 7.3.2 Events | Table 4: Events Symbol Definition R S Duration ma(parms) ManageAudio BR variable oc OperationComplete x of(parms) OperationFailed x pa(parms) PlayAnnouncement TO variable pc(parms) PlayCollect TO variable pr(parms) PlayRecord TO variable PlayAnnouncement: Plays an announcement in situations where there is no need for i... |
00b8be8005f8d11eff35f07711becee2 | 103 161-19 | 7.3.3 Signal Interactions | If an Audio Package signal is active on an endpoint and another signal of the same type is applied, the two signals including parameters and parameter values will be compared. If the signals are identical, the signal in progress will be allowed to continue and the new signal will be discarded. Because of this behaviour... |
00b8be8005f8d11eff35f07711becee2 | 103 161-19 | 7.3.4 Parameters | The PlayAnnouncement, PlayRecord, and PlayCollect events may each be qualified by a string of parameters, most of which are optional. Where appropriate, parameters default to reasonable values. If a required parameter is not supplied an error is returned to the application. These parameters are shown in table 5. Table ... |
00b8be8005f8d11eff35f07711becee2 | 103 161-19 | 7.3.5 Type-ahead | The Audio Server supports type-ahead by default. Type-ahead is not supported for the Play event because by definition no digit collection is done during this event. Type-ahead can be turned off for all prompts associated with a PlayCollect or PlayRecord event by setting the Clear Digit Buffer parameter. ETSI ETSI TS 10... |
00b8be8005f8d11eff35f07711becee2 | 103 161-19 | 7.3.6 Return Parameters | Each event has an associated set of possible return parameters that are returned with either the OperationComplete or OperationFailed events. These parameters are listed in table 6. Table 6: Return Parameters Symbol Definition pa pc pr ma ap amount played F C C F dc digits collected F O O F na number of attempts F M M ... |
00b8be8005f8d11eff35f07711becee2 | 103 161-19 | 7.3.7 Segment Descriptors | Segment descriptors are used with the an, ip, rp, nd, ns, fa, and sa parameters to define the segments that make up an announcement. There are two kinds of segment descriptors: Table 8: Segment Descriptors Symbol Definition <URI> segment identifier vb variable Segment Identifier: A URI identifying a provisioned entity,... |
00b8be8005f8d11eff35f07711becee2 | 103 161-19 | 7.3.8 Variable Syntax | The syntax supports two kinds of variables. Embedded variables are variables that have been provisioned as part of an audio segment. At runtime the call agent references the segment and specifies a value for the variable. Typically embedded variables are provisioned along with recorded speech, e.g. "A representative wi... |
00b8be8005f8d11eff35f07711becee2 | 103 161-19 | 7.3.9 Variable Definitions | Variable types and subtypes are specified in table 9. Table 9: Variable Types and Subtypes Type Subtype Definition dat mdy, dmy, etc. Date mdy Month-Day-Year dym Day-Year-Month dig gen, ndn Digits gen Generic ndn North American DN dur Duration mth Month mny <ISO 4217 three letter codes> Money num crd, ord Number crd Ca... |
00b8be8005f8d11eff35f07711becee2 | 103 161-19 | 7.3.10 Timers | Four timers are defined in this package: • First digit timer (FDT). • Interdigit timer (IDT). • Interdigit critical timer (ICT). • Extra digit timer (EDT). Consistent implementation of the interaction between timers is important for applications that use audio servers that meet the present document. The following guide... |
00b8be8005f8d11eff35f07711becee2 | 103 161-19 | 7.3.11 Examples | This clause presents a number of syntax examples. Play an announcement that consists of a single segment: S: pa(an=file://12333) Play an announcement that consists of multiple segments: S: pa(an=file://ann798,file://ann300,file://ann4747) Play an announcement that consists of a recording followed by three seconds of si... |
00b8be8005f8d11eff35f07711becee2 | 103 161-19 | 7.4 Advanced Audio Package | |
00b8be8005f8d11eff35f07711becee2 | 103 161-19 | 7.4.1 Abstract | The Advanced Audio package extends the Base Audio package by adding the set capability which the user can use to create an arbitrary number of user defined qualifiers to be used in resolving complex audio structures. For example, the user could define qualifiers for any or all of the following: • language; • accent; • ... |
00b8be8005f8d11eff35f07711becee2 | 103 161-19 | 7.4.2 Sets | A set is a provisioned collection of semantically related audio segments with an associated selector. Each set is assigned a unique URI. A set can contain physical segments, sequences, other sets, or variables. At runtime the value of the selector is used to determine which element of the set is played. Individual sele... |
00b8be8005f8d11eff35f07711becee2 | 103 161-19 | 7.4.3 Selectors | Selector types, except for the predefined "lang" (language) selector, are defined by the user. For each selector type, the user must define a range of values that the selector can assume. Selectors apply to individual audio segments. If an event specifies multiple segments, each segment have its own set of selectors. I... |
00b8be8005f8d11eff35f07711becee2 | 103 161-19 | 7.4.4 Selector Encoding | Provisioned segments and segments recorded at runtime are identified by URIs as defined in RFC 2396 [i.3], Uniform Resource Identifiers: Generic Syntax. A URI can be a simple name or it can be a URL. If a URL refers to audio stored on a node other than the Audio Server it must contain all the information necessary to r... |
00b8be8005f8d11eff35f07711becee2 | 103 161-19 | 7.4.5 Variable Order | When a provisioned segment containing more than one variable is referenced at runtime, the variable values shall be supplied in the order in which they occur in the provisioned segment. This principle extends to sets. If the elements of a set contain more than one variable then for all elements of the set the variables... |
00b8be8005f8d11eff35f07711becee2 | 103 161-19 | 7.4.6 Overrides | A provisioned physical segment may be replaced (or overridden) by a persistent physical segment. The URI of the provisioned physical segment will then resolve to the persistent physical segment. The overriding persistent audio can subsequently be deleted and the original provisioned audio can be restored. A provisioned... |
00b8be8005f8d11eff35f07711becee2 | 103 161-19 | 7.4.7 Parameters | Table 13: Parameters Symbol Definition pa pc pr ma oa override persistent audio F F F O ra restore persistent audio F F F O NOTE: O = Optional M = Mandatory F = Forbidden Override Persistent Audio: The id of the segment to be overridden and the id of the overriding segment. Restore Persistent Audio: The id of the segme... |
00b8be8005f8d11eff35f07711becee2 | 103 161-19 | 7.4.8 Return Codes | The following return codes are defined for the Advanced Audio Package. Table 14: Return Codes Return Code Meaning 650 Bad selector type 651 Bad selector value 652 Missing selector 653 Missing selector value 654 Wrong number of selector 655 Remove override error 656 Override error 657 Unable to override non-existent seg... |
00b8be8005f8d11eff35f07711becee2 | 103 161-19 | 7.4.9 Examples | This clause presents a number of examples of how sets and selectors are used. Play an announcement in English. S: pa(an=file://audio/xyztel/hello?lang=eng) ETSI ETSI TS 103 161-19 V1.1.1 (2011-10) 31 Play an announcement in a Danish, female voice with a Cajun accent. S: pa(an=file://audio/xyztel/hello?lang=dan& gender=... |
00b8be8005f8d11eff35f07711becee2 | 103 161-19 | 7.5 Overview | The purpose of this document is to provide extensions to support speech recognition, natural language understanding, and dialog manager resources in the MGCP (NCS) based media server framework. This is a superset of the PASS BAU package, and the BAU package is assumed present with this package. The package is also comp... |
00b8be8005f8d11eff35f07711becee2 | 103 161-19 | 7.5.1 Speech Recognition Extensions to the BAU package | Table 15 extends table 4, clause 7.3.2. Table 15: S1 Events Symbol Definition R S Duration prg(parms) PlayRecognize TO variable mac(parms) ManageASRContext BR variable PlayRecognize: PlayRecognize extends the PlayCollect signal. PlayRecognize plays a prompt and recognizes spoken utterance and/or collects DTMF digits en... |
00b8be8005f8d11eff35f07711becee2 | 103 161-19 | 7.5.2 Signal Interactions | If an Audio Package signal is active on an endpoint and another signal of the same type is applied, the two signals including parameters and parameter values will be compared if the signals are identical, the signal in progress will be allowed to continue and the new signal will be discarded. Because of this behaviour ... |
00b8be8005f8d11eff35f07711becee2 | 103 161-19 | 7.5.3 Parameters | The PlayRecognize and ManageASRContext events may each be qualified by a string of parameters, most of which are optional. Where appropriate, reasonable default parameter values have been defined. If a required parameter is not supplied an error is returned to the application. The PlayRecognize command re-uses the foll... |
00b8be8005f8d11eff35f07711becee2 | 103 161-19 | 7.5.4 Type-ahead | The Audio Server supports type-ahead by default. Type-ahead is not supported for the Play event because by definition no digit collection is done during this event. Type-ahead can be turned off for all prompts associated with a PlayCollect or PlayRecord event by setting the Clear Digit Buffer parameter. |
00b8be8005f8d11eff35f07711becee2 | 103 161-19 | 7.5.5 Return Parameters | Each event has an associated set of possible return parameters, which are returned with either the OperationComplete or OperationFailed events. These parameters are listed in table 17. Table 17 extends clause 7.3.6, table 6. Values not specified are forbidden. Table 17: S3. Return Parameters Symbol Definition prg ma ma... |
00b8be8005f8d11eff35f07711becee2 | 103 161-19 | 7.5.6 Grammar Descriptors | Grammar descriptors are used with the ldg, sdg, ag, rsp, rip and rtp parameters to define the grammars to be managed for the subsequent PlayRecognize signal. There are two kinds of grammar descriptors: Table 19: S5. Grammar Descriptors Symbol Definition <URI> Grammar identifier Inline Inline definition of the grammar G... |
00b8be8005f8d11eff35f07711becee2 | 103 161-19 | 7.5.7 Examples | This clause presents samples of automatic speech recognition interactions. Play a prompt and collect the speaker's voice input for PIN code validation… S:mac(ldg ag= file://grammar-digits,rulePIN). S:prg(lwt=1000 sva=0.5 dtmf=true bth=0.9) O: SPR/oc(na=1 ru=1234) ETSI ETSI TS 103 161-19 V1.1.1 (2011-10) 36 |
00b8be8005f8d11eff35f07711becee2 | 103 161-19 | 7.6 Formal Syntax Description | This description uses ABNF (RFC 2234 [i.4]) to formally describe the syntax of the Basic Audio Package and the Advanced Audio Package. The two packages have the same syntax except for the encoding of selector types and selector values in the query field of the URI and the persistent audio override capabilities. See RFC... |
26796e170892d4de841919772b78ef1c | 103 161-3 | 1 Scope | The present document specifies the media aspects of the interfaces between IPCablecom client devices for audio and video communication. Specifically, it identifies the audio and video codecs necessary to provide the highest quality and the most resource-efficient service delivery to the customer. The present document a... |
26796e170892d4de841919772b78ef1c | 103 161-3 | 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... |
26796e170892d4de841919772b78ef1c | 103 161-3 | 2.1 Normative references | The following referenced documents are necessary for the application of the present document. [1] PKT-TR-ARCH1.5-V02-070412: "PacketCable 1.5, Architecture Framework Technical Report", April 12, 2007, Cable Television Laboratories, Inc. [2] PKT-SP-DQOS1.5-I04-090624: "PacketCable 1.5 Specifications, Dynamic Quality-of-... |
26796e170892d4de841919772b78ef1c | 103 161-3 | 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] PKT-SP-SEC1.5-I03-090624, PacketCable 1.5 Security Specification, June 24, 2009, Cable Television Laboratories, Inc. [i.2] Void. [i.3] Void. [i.4] Voi... |
26796e170892d4de841919772b78ef1c | 103 161-3 | 3 Definitions and abbreviations | |
26796e170892d4de841919772b78ef1c | 103 161-3 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: audio server: audio server plays informational announcements in IPCablecom network NOTE: Media announcements are needed for communications that do not complete and to provide enhanced information services to the user. The component par... |
26796e170892d4de841919772b78ef1c | 103 161-3 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: ANS Answer Tone NOTE: As per ITU-T Recommendation V.25. ASCII American Standard Code for Information Interchange CDMA Code Division Multiple Access CED Facsimile CallED tone NOTE: Defined in ITU-T Recommendation T.30. CIF Common Intermediate F... |
26796e170892d4de841919772b78ef1c | 103 161-3 | 4 Void | |
26796e170892d4de841919772b78ef1c | 103 161-3 | 5 Background | This clause outlines the IPCablecom 1.5 architecture support elements and the DOCSIS network infrastructure necessary to deliver quality audio and video service. It is intended to clarify external interfaces and functional requirements necessary to implement the targeted audio and video quality using speech and video c... |
26796e170892d4de841919772b78ef1c | 103 161-3 | 5.1 IPCablecom Voice Communications Quality Requirements | As defined in the IPCablecom architecture document [1], requirements for toll-quality voice communications service in IPCablecom include numerous metrics to ensure competitive or superior quality and service to the PSTN. In order to support these requirements, network plant and equipment may have to be groomed. In orde... |
26796e170892d4de841919772b78ef1c | 103 161-3 | 5.2 Network Preparation for Codec Support | The critical areas of network performance, which must be optimized in tandem with codecs, are packet loss, latency, and jitter. Elaboration of network/codec implications for each of these areas follows. |
26796e170892d4de841919772b78ef1c | 103 161-3 | 5.2.1 Packet Loss Control | There is a direct correlation between packet integrity and audio quality. Anecdotal codec research suggests initial 3 % packet loss rate results, on average, in a reduction in Mean Opinion Score (MOS) scores of 0,5 point, on a scale of 5. Due to less-than-pristine conditions and human-detectable compromises with most c... |
26796e170892d4de841919772b78ef1c | 103 161-3 | 5.2.2 Latency Control | Control of overall latency requires a hand-in-hand effort by the system resources and the application-in this case, a speech or video application dominated by the codec component. There are multiple device elements and network components inducing latency during traversal of an audio signal from capture of the speaker's... |
26796e170892d4de841919772b78ef1c | 103 161-3 | 5.2.2.1 Latency Control: Buffering | While network jitter and corresponding buffering increase call latency, another source of buffering can be induced by the application as a corrective response to severe packet loss. Although the ultimate solution to additional buffering delay is a pristine network, realistically some packet loss will occur. Accounting ... |
26796e170892d4de841919772b78ef1c | 103 161-3 | 5.2.2.2 Latency Control: Optimal Framing/Packetization | As outlined in clause 5.2.1, the loss of audio data frames can have a severe impact on audio quality. The packing of multiple audio frames into a single packet will exacerbate the problem, effectively expanding the loss of one packet into the loss of multiple adjacent audio frames of data. This also increases latency b... |
26796e170892d4de841919772b78ef1c | 103 161-3 | 5.2.2.3 Latency Control: Packet Timing Optimization | To avoid additional buffering delay, packets shall be sent at a rate equal to integral multiples of the audio sample frame rate of the codec. This synchronization results in lockstep between the codec framing and packet transmission. The frame sizes of the codecs are shown in table 1. Default packetization periods are ... |
26796e170892d4de841919772b78ef1c | 103 161-3 | 5.2.3 Codec Transcoding Minimization | Transcoding occurs whenever a packetized voice signal encounters an edge device without compatible codec support. Transcoding introduces additional latency during the decode/recode stage. Additionally, if transcoding resources at the edge gateway are shared, additional delay can be introduced. Transcoding between compr... |
26796e170892d4de841919772b78ef1c | 103 161-3 | 5.2.4 Bandwidth Minimization | There are two primary mechanisms that client devices may employ to minimize the amount of bandwidth used for their audio/video applications: • A compressed, low bitrate codec may be applied, thus reducing the bandwidth required. • A codec may employ some form of variable bitrate transmission. The selection of codecs oc... |
26796e170892d4de841919772b78ef1c | 103 161-3 | 6 Device Requirements for Audio codec support | As markets evolve, endpoint codecs will change too, and neither a provider nor a customer can be expected to replace their cable modem/MTA frequently to accommodate these market changes. Given the rapid growth of the digital wireless market in particular, it is likely that, at some point, a statistically significant po... |
26796e170892d4de841919772b78ef1c | 103 161-3 | 6.1 Dynamic Update Capability | All MTA devices shall be capable of downloading new software from authorized sources. |
26796e170892d4de841919772b78ef1c | 103 161-3 | 6.2 Maximum Service Outage | If the MTA supports life-line services (such as 911 emergency service), service disruption shall not exceed 20 seconds excluding reboot time when downloading new software to the MTA. |
26796e170892d4de841919772b78ef1c | 103 161-3 | 6.3 Minimum Processing Capability | All MTA devices shall be capable of supporting the equivalent simultaneous execution of codec combinations shown in the following table. Although the present specification does not mandate the support of either G.728 or G.729 Annex E, this requirement provides the necessary reserve capacity for additional future codecs... |
26796e170892d4de841919772b78ef1c | 103 161-3 | 6.4 Minimum Audio Codec Storage Capability | All MTA devices shall be capable of maintaining simultaneously, in device memory or storage, all mandatory and recommended codecs specified herein (i.e. equivalent storage for G.711, G.728, G.729 Annex E, internet Low Bit rate Codec [iLBC™], and BroadVoice™16 [BV16]). Although the present specification does not mandate... |
26796e170892d4de841919772b78ef1c | 103 161-3 | 7 Audio Codecs Specifications | |
26796e170892d4de841919772b78ef1c | 103 161-3 | 7.1 Feature Support | Offering a competitive and/or superior product requires support for more than toll-quality delivery of audio. In addition to features and signalling capabilities, which are beyond the scope of the present document, the audio codec application must provide transparent support for certain audio features. These include ge... |
26796e170892d4de841919772b78ef1c | 103 161-3 | 7.1.1 DTMF Support | Dual-tone multi-frequency (DTMF) support allows employment of dual-tone multiple frequency signals by either an autodialing system or through manual entry of tones. In order for DTMF tones to be captured correctly by the receiving device, tonal integrity (frequency accuracy and signal duration) must be maintained even ... |
26796e170892d4de841919772b78ef1c | 103 161-3 | 7.1.2 Fax and Modem Support | IPCablecom needs to support analog fax and modem interfaces for two reasons. First, fax and modem equipment are common in residences, and customers will continue to use these familiar devices for some years to come. Second, even with cable modem access, many SOHO or ISP users will continue to access their dial-up netwo... |
26796e170892d4de841919772b78ef1c | 103 161-3 | 7.1.3 Echo Compensation Support | When end-to-end delay in an audio communication is more than 20 milliseconds, an artifact called line echo can occur. This echo, if not removed, will be heard by the remote talker (thus it is also called talker echo) whenever he or she speaks. Line echo is created at the telephone interface of the MTA, or the PSTN inte... |
26796e170892d4de841919772b78ef1c | 103 161-3 | 7.1.4 Asymmetrical Services Support | MTA devices should be capable of supporting employment of different codecs for upstream and downstream audio channels. This allows potential optimization of device resources, network bandwidth, and user service quality. |
26796e170892d4de841919772b78ef1c | 103 161-3 | 7.1.5 Hearing-impaired Services Support | For over one million hearing-impaired North Americans and 20 million North Americans with some amount of hearing loss, TTY (teletype technology) equipment can be the primary communication link to the outside world. This type of equipment has evolved lacking the type of standardization allowing broad interoperability am... |
26796e170892d4de841919772b78ef1c | 103 161-3 | 7.1.7 Packet Loss Concealment | All Media Gateways and Media Terminal Adaptors shall detect audio packet loss and implement some method to conceal losses from end-users. Specifications for low bit rate codecs (e.g. G.728, G.729, iLBC, BV16) include methods for concealment (the packet loss concealment method for iLBC, as defined and included in [34] i... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.