hash
stringlengths
32
32
doc_id
stringlengths
7
13
section
stringlengths
3
121
content
stringlengths
0
2.2M
147b91ca74342ff380d1c2f52f551a43
103 161-5
7.1.5 Gate Coordination
The Gate Coordination messages in the COPS Gate Control interface, Gate-Open and Gate-Close, provide an unsolicited feedback mechanism from the CMTS to the CMS in order to maintain state-synchronization between these elements. This is particularly useful in the case of a pre-mature MTA-initiated reservation or committa...
147b91ca74342ff380d1c2f52f551a43
103 161-5
7.2 COPS Profile for IPCablecom
IP QoS Admission Control is the act of managing QoS resource allocation based on administrative policies and available resource. IP QoS Admission Control Service uses a client/server architecture. The high level operational modules are depicted in figure 10. The administrative policies are stored as policy database and...
147b91ca74342ff380d1c2f52f551a43
103 161-5
7.3 Gate Control Protocol Message Formats
Protocol messages for Gate Control are transported within the COPS protocol messages. COPS uses a TCP connection established between the CMTS and the Gate Controller, and uses the mechanisms specified in [i.10] to secure the communication path.
147b91ca74342ff380d1c2f52f551a43
103 161-5
7.3.1 COPS Common Message Format
Each COPS message consists of the COPS header followed by a number of typed objects. The GC and CMTS must support COPS messaging as defined below. 0 1 2 3 Version Flags Op-Code Client-type Message length Figure 11: Common COPS Message Header Version is a 4-bit field giving the current COPS version number. This must be ...
147b91ca74342ff380d1c2f52f551a43
103 161-5
7.3.2 Additional COPS Objects for Gate Control
As with the COPS-PR and COPS-RSVP client types, the IPCablecom client type defines a number of object formats. These objects must be placed inside a Decision object, C-Num = 6, C-Type = 4 (Client specific Decision Data) when carried from GC to CMTS in a decision message. They must also be placed in a ClientSI object, C...
147b91ca74342ff380d1c2f52f551a43
103 161-5
7.3.2.1 TransactionID
The TransactionID contains a token that is used by the GC to match responses from the CMTS to the previous requests, and the command type that identifies the action to be taken or response. Length = 8 S-Num = 1 S-Type = 1 Transaction Identifier Gate Command Type Transaction Identifier is a 16-bit quantity that may be u...
147b91ca74342ff380d1c2f52f551a43
103 161-5
7.3.2.2 Subscriber-ID
The Subscriber-ID identifies the subscriber for this service request. Its main use is to prevent various denial-of-service attacks. Length = 8 S-Num = 2 S-Type = 1 IP v4 address (32-bits) or Length = 20 S-Num = 2 S-Type = 2 IP v6 address (128-bits)
147b91ca74342ff380d1c2f52f551a43
103 161-5
7.3.2.3 GateID
This object identifies the gate or set of gates referenced in the command message, or assigned by the CMTS for a response message. Length = 8 S-Num = 3 S-Type = 1 GateID (32-bits)
147b91ca74342ff380d1c2f52f551a43
103 161-5
7.3.2.4 Activity-Count
When used in a GATE-ALLOC message, this object specifies the maximum number of gates that can be simultaneously allocated to the indicated subscriber-ID. This object returns, in a GATE-SET-ACK or GATE-ALLOC-ACK message, the number of gates assigned to a single subscriber. It is useful in preventing denial-of-service at...
147b91ca74342ff380d1c2f52f551a43
103 161-5
7.3.2.5 Gate-Spec
Length = 60 S-Num = 5 S-Type = 1 Direction ProtocolID Flags Session Class Source IP Address (32-bits) Destination IP Address (32-bits) Source Port (16-bits) Destination Port (16-bits) DiffServ Code Point Timer T1 value Reserved Timer-T7 value Timer-T8 value Token Bucket Rate [r] (32-bit IEEE floating point number) Toke...
147b91ca74342ff380d1c2f52f551a43
103 161-5
7.3.2.6 Remote-Gate-Info
Length=36 S-Num = 6 S-Type = 1 CMTS IP Address (32-bits) CMTS Port (16-bits) Flags, defined below Remote GateID Algorithm Reserved Security Key (16 bytes) This object has been deprecated. S-Num 6 is reserved to prevent misinterpretation.
147b91ca74342ff380d1c2f52f551a43
103 161-5
7.3.2.7 Event-Generation-Info
The object contains all the information necessary to support the event messages as specified and required in [i.4]. Length = 44 S-Num = 7 S-Type = 1 Primary-Record-Keeping-Server-IP-Address (32-bits) Primary-Record-Keeping-Server-Port Flags, see below Reserved Secondary-Record-Keeping-Server-IP-Address (32-bits) Second...
147b91ca74342ff380d1c2f52f551a43
103 161-5
7.3.2.8 Media-Connection-Event-Info
This object has been deprecated by dqos-n-02185 in coordination with em-n-02182. S-Num 8 is reserved to prevent misinterpretation.
147b91ca74342ff380d1c2f52f551a43
103 161-5
7.3.2.9 IPCablecom-Reason
This object contains the reason why the gate is being deleted. Length = 8 S-Num = 13 S-Type = 1 Reason-code Reason Sub-code The Reason-code values defined in the present document are: 0: Gate-Delete Operation 1: Gate-Close Operation The Reason Sub-codes are defined as: Gate-Delete Operation 0 = Normal operation 1 = Loc...
147b91ca74342ff380d1c2f52f551a43
103 161-5
7.3.2.10 IPCablecom-Error
A client-specific error object is defined as follows. Length = 8 S-Num = 9 S-Type = 1 Error-code Error Sub-code The Error-code values defined in the present document are: 1 = No gates currently available 2 = Unknown GateID 3 = Illegal Session Class value 4 = Subscriber exceeded gate limit 5 = Gate already set 6 = Missi...
147b91ca74342ff380d1c2f52f551a43
103 161-5
7.3.2.11 Electronic-Surveillance-Parameters
The Electronic-Surveillance-Parameters object contains all the information necessary to support Electronic Surveillance. This object may be included in the Gate-Set to enable Electronic Surveillance. A CMTS must accept this object in the Gate-Set and perform the appropriate actions as defined below. Length = 48 S-Num =...
147b91ca74342ff380d1c2f52f551a43
103 161-5
7.3.2.12 Session-Description-Parameters
Length S-Num = 11 S-Type = 1 This object has been deprecated by dqos-n-03026. S-Num 11 is reserved to prevent misinterpretation.
147b91ca74342ff380d1c2f52f551a43
103 161-5
7.3.3 Definition of Gate Control Messages
Messages that perform gate control between the GC and CMTS must be defined and formatted as follows. Note that messages from GC to CMTS are COPS Decision messages, and messages from CMTS to GC are COPS Report messages. <Gate-Control-Cmd> :: = <COPS-Common-Header> <Handle> <Context> <Decision-Flags> <ClientSI-Data> <Cli...
147b91ca74342ff380d1c2f52f551a43
103 161-5
7.4 Gate Control Protocol Operation
147b91ca74342ff380d1c2f52f551a43
103 161-5
7.4.1 Initialization Sequence
When the CMTS (i.e. COPS PEP) boots, it must listen for incoming COPS connections on the IANA-assigned TCP port number 2126. Any Gate Controller with a need to contact the CMTS must establish a TCP connection to the CMTS on that port. It is expected that multiple Gate Controllers will establish COPS connections with a ...
147b91ca74342ff380d1c2f52f551a43
103 161-5
7.4.2 Operation Sequence
The protocol between the Gate Controller and CMTS is for purposes of resource control and resource allocation policy. The Gate Controller implements all the allocation policies, and uses that information to manage the set of gates implemented in the CMTS. The Gate Controller initializes the gates with specific source, ...
147b91ca74342ff380d1c2f52f551a43
103 161-5
7.4.3 Procedures for Allocating a new Gate
A GATE-ALLOC message is sent by the Gate Controller to the CMTS at the time the 'Call_Setup' message is sent from the originating MTA, as shown in figure 15. The use of GATE-ALLOC ensures that not too many sessions are being simultaneously requested from a given MTA. This mechanism may be used to control a denial of se...
147b91ca74342ff380d1c2f52f551a43
103 161-5
7.4.4 Procedures for Authorizing Resources Through a Gate
The GATE-SET message is sent by the Gate Controller to the CMTS to initialize or modify the operational parameters of the gate(s). Figure 16 is an example of the GATE-SET signalling. GC CMTS MTA "Call Setup" GATE-ALLOC GATE-ALLOC-ACK ETSI ETSI TS 103 161-5 V1.1.1 (2011-10) 65 Figure 16: Sample Signalling of Gate-Set If...
147b91ca74342ff380d1c2f52f551a43
103 161-5
7.4.5 Procedures for Querying a Gate
When a Gate Controller wishes to find out the current parameter settings of a gate, it sends to the CMTS a GATE-INFO message. The CMTS must respond to a GATE-INFO message with either a GATE-INFO-ACK (indicating success) or a GATE-INFO-ERR (indicating failure). The TransactionID in the response must match the Transactio...
147b91ca74342ff380d1c2f52f551a43
103 161-5
7.4.6 Procedures for Committing a Gate
When the MTA successfully performs the initial Commit operation (as described in clause 6.2.1 for an embedded MTA) for a Gate, the CMTS must send a Gate-Open message.
147b91ca74342ff380d1c2f52f551a43
103 161-5
7.4.7 Procedures for Closing a Gate
The CMTS must release all resources associated with the gate, delete the gate, delete associated Service Flow(s) using a DOCSIS® DSD message, and send a Gate-Close message when it receives an explicit release message from the MTA client (as described in clause 6.3.3 for embedded MTAs), or when it detects that the clien...
147b91ca74342ff380d1c2f52f551a43
103 161-5
7.4.8 Procedures for Deleting a Gate
In a normal call flow, a gate is deleted by the CMTS when it receives a DSD-REQ message. The CMTS also deletes a gate at the receipt of a GATE-CLOSE message. If both upstream and downstream gates are reserved or committed then the CMTS must adhere to the following rules: • For an E-MTA initiated DSD-REQ which includes ...
147b91ca74342ff380d1c2f52f551a43
103 161-5
7.4.9 Termination Sequence
When the CMTS is shutting down its TCP connection to the GC, it may first send a DELETE-REQUEST-STATE message (including the handle object used in the REQUEST message). The CMTS may follow that with a CLIENT- CLOSE message. These messages are optional because the GC is stateless and because the COPS protocol requires a...
147b91ca74342ff380d1c2f52f551a43
103 161-5
7.4.10 Failure Scenario
When a CMTS detects the loss of the TCP or COPS connection to the GC, e.g. if the GC suffers a catastrophic failure, the CMTS must keep all established gates in place. One method of maintaining status of the TCP or COPS connection is through use of the COPS Keep-Alive messages. In this case if the CMTS does not receive...
147b91ca74342ff380d1c2f52f551a43
103 161-5
7.5 CMS Use of Gate Protocol
The CMS must ensure that all codecs agreed during negotiation fit within the resource envelope requested from the CMTS using gate communication. CMS must use LUB algorithm provided in clause 6.1.1 to determine b, r, p, m, and M values. ETSI ETSI TS 103 161-5 V1.1.1 (2011-10) 68 The CMS should make sure that the Gate Co...
147b91ca74342ff380d1c2f52f551a43
103 161-5
7.6 Gate-Coordination
The Gate-Controller keeps the state of each gate. The Gate-Controller creates a gate on the CMTS using the Gate-Alloc or Gate-Set message. The Gate-Controller may delete a gate via the Gate-Delete command or may query the CMTS for information associated with a particular gate using the Gate-Info message. The CMTS infor...
147b91ca74342ff380d1c2f52f551a43
103 161-5
7.6.1 Connecting a Call
The successful connection of a normal call requires three events happening in close succession: • The CMS requests commitment of resources at the local MTA • The CMTS indicates that resources have been committed by the local MTA • Coordination of local and remote resource commitment is coordinated on the signalling pla...
147b91ca74342ff380d1c2f52f551a43
103 161-5
7.6.2 Terminating a Call
The termination of a call, as in the case of the connection, requires three events within a short time frame: • The CMS requests release of resources at the local MTA • The CMTS indicates that resources have been released by the local MTA • Coordination of local and remote resource release is coordinated on the signall...
147b91ca74342ff380d1c2f52f551a43
103 161-5
8 Timer Definitions and Values
Several timers are referenced in the present document. This clause contains the list of those timers, and their recommended values.
147b91ca74342ff380d1c2f52f551a43
103 161-5
8.1 Timer T0
This timer is implemented in the CMTS in the Gate state machine, and limits the period of time that a gate may be allocated without the gate parameters being set. This enables the CMTS to recover the GateID resources when the Call Management System fails to complete the signalling sequence for a new session. This timer...
147b91ca74342ff380d1c2f52f551a43
103 161-5
8.2 Timer T1
This timer is implemented in the CMTS in the Gate state machine, and limits the period of time that may elapse between the authorization and a commit is performed. This timer is started whenever a Gate is established. This timer is reset when the Gate goes to a COMMITTED state. On expiration of this timer, the CMTS mus...
147b91ca74342ff380d1c2f52f551a43
103 161-5
8.3 Timer T2
This timer is no longer used.
147b91ca74342ff380d1c2f52f551a43
103 161-5
8.4 Timer T3
This timer is no longer used.
147b91ca74342ff380d1c2f52f551a43
103 161-5
8.5 Timer T4
This timer is no longer used.
147b91ca74342ff380d1c2f52f551a43
103 161-5
8.6 Timer T5
This timer is implemented in the CMS. It controls the synchronization between local MTA resource release and CMTS verification of the closure of the local gate. When the CMS sends the MTA a message to delete the connection, the CMS must ensure that the gate is closed in the CMTS within T5. This timer is reset when the ...
147b91ca74342ff380d1c2f52f551a43
103 161-5
8.7 Timer T6
This timer is no longer used.
147b91ca74342ff380d1c2f52f551a43
103 161-5
8.8 Timer T7
The CMTS must set the Timeout for Admitted QoS Parameters for the service flow to the value specified for this timer. In the case of a flow with multiple sub-flows, the flow's Timeout for Admitted QoS Parameters is set to the value of timer T7 from the most recently received Gate-Set message for any sub-flow on the flo...
147b91ca74342ff380d1c2f52f551a43
103 161-5
8.9 Timer T8
The CMTS must set the Timeout for Active QoS Parameters for the service flow to the value specified in for this timer. In the case of a flow with multiple sub-flows, the flow's Timeout for Active QoS Parameters is set to the value of timer T8 from the most recently received Gate-Set message for any sub-flow on the flow...
f2dbd5f462250ffb0478707fe6d5dd25
102 992
1 Scope
The present document describes an optional extension to the DVB-T2 second-generation transmission system for digital terrestrial television broadcasting, as specified in [1]. This extension takes the form of the addition of transmitter- signature information, and is primarily intended for use in single-frequency networ...
f2dbd5f462250ffb0478707fe6d5dd25
102 992
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...
f2dbd5f462250ffb0478707fe6d5dd25
102 992
2.1 Normative references
The following referenced documents are necessary for the application of the present document. [1] ETSI EN 302 755: "Digital Video Broadcasting (DVB); Frame Structure channel coding and modulation for a second generation digital terrestrial television broadcasting system (DVB-T2)".
f2dbd5f462250ffb0478707fe6d5dd25
102 992
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] FAN P. (2004): "Spreading sequence design and theoretical limits for quasisynchronous CDMA systems". EURASIP Journal on Wireless Communications and Ne...
f2dbd5f462250ffb0478707fe6d5dd25
102 992
3 Definitions, symbols and abbreviations
f2dbd5f462250ffb0478707fe6d5dd25
102 992
3.1 Definitions
For the purposes of the present document, the following terms and definitions apply: auxiliary cell: cell in an auxiliary stream auxiliary stream: sequence of cells carrying data of as yet undefined modulation and coding, which may be used for future extensions or as required by broadcasters or network operators B cell...
f2dbd5f462250ffb0478707fe6d5dd25
102 992
3.2 Symbols
For the purposes of the present document, the following symbols apply.
f2dbd5f462250ffb0478707fe6d5dd25
102 992
3.2.1 Symbols relating to auxiliary-stream signature method
bBS, j bit value in DVB-T2 BB scrambling sequence having index j j integer index of positions in BB scrambling sequence ( bBS, j above) K total number of cells in the transmitter-signature auxiliary stream L number of T2 frames per TX-SIG frame, within which the cycle of cell positions in the auxiliary stream repeats M...
f2dbd5f462250ffb0478707fe6d5dd25
102 992
3.2.2 Symbols relating to FEF-based signature method
cl, ′ k the complex modulation value for 'carrier' ′ k in signature period l cq value of element of Frank sequence having index q d parameter of Zeng's section-III.C method [i.2] the duration of the signature cyclic prefix, Δ =14546T fc the centre frequency of the emitted RF signal h integer index of sequence, in range...
f2dbd5f462250ffb0478707fe6d5dd25
102 992
3.3 Abbreviations
For the purposes of the present document, the following abbreviations apply: ACF Auto-Correlation Function DFT Discrete Fourier Transform DVB-T2 second-generation Terrestrial Digital Video Broadcasting NOTE: As specified in EN 302 755 [1]. FEF Future Extension Frame NOTE: As specified in EN 302 755 [1]. FFT Fast Fourie...
f2dbd5f462250ffb0478707fe6d5dd25
102 992
4 General description
f2dbd5f462250ffb0478707fe6d5dd25
102 992
4.1 Context
EN 302 755 [1] describes the coding and modulation for the second-generation digital terrestrial television broadcasting system known as DVB-T2. It provides the means whereby digital content can be broadcast to viewers and other consumers of content. It offers many options for network operators, including the ability t...
f2dbd5f462250ffb0478707fe6d5dd25
102 992
4.2 General principles
Clearly, to include a signature unique to a transmitter implies at least a partial departure from the general SFN principle of radiating identical signals from every transmitter - some part of the signal must be different. However, a cardinal principle remains, that the addition of transmitter signatures must not distu...
f2dbd5f462250ffb0478707fe6d5dd25
102 992
5 Transmitter signature using auxiliary streams
f2dbd5f462250ffb0478707fe6d5dd25
102 992
5.1 General description
This signature method uses one auxiliary stream in the DVB-T2 signal to carry transmitter identification information. There may also be other auxiliary streams, for other purposes, before or after (or both) the actual auxiliary stream used as a transmitter signature. In line with the DVB-T2 specification there may also...
f2dbd5f462250ffb0478707fe6d5dd25
102 992
5.2 How the auxiliary streams are formed
We first define the order of the M N cells before insertion of B cells. The M transmitters to be signalled are denoted tx_id_1, tx_id_2, …tx_id_M. In the first T2 frame of the TX-SIG frame the N cells signalling tx_id_1 come first followed by the N cells of tx_id_2 etc. until tx_id_M. For each new T2 frame the M N cell...
f2dbd5f462250ffb0478707fe6d5dd25
102 992
5.3 Special considerations for MISO
Clause 5.2 fully describes the necessary operations for all SISO modes. However, special considerations apply when MISO is used, as noted in the following quote from clause 8.3.7 of EN 302 755 [1]: "The cell values for auxiliary streams need not be the same for all transmitters in a single frequency network. However, i...
f2dbd5f462250ffb0478707fe6d5dd25
102 992
5.4 L1 signalling for TX-SIG auxiliary streams
f2dbd5f462250ffb0478707fe6d5dd25
102 992
5.4.1 Configurable L1-post signalling
In accordance with clause 7.2.3.1 of EN 302 755 [1], the use of a transmitter-signature auxiliary stream shall be signalled by including an entry in the auxiliary-stream loop of the DVB-T2 configurable L1-post signalling whose AUX_STREAM_TYPE is set to '0000'. The corresponding 28-bit AUX_PRIVATE_CONF field shall be us...
f2dbd5f462250ffb0478707fe6d5dd25
102 992
5.4.2 Dynamic L1-post signalling
When the AUX_STREAM_TYPE of the DVB-T2 configurable L1-post signalling is '0000' the 48-bit AUX_PRIVATE_DYN field of the DVB-T2 Dynamic L1-post signalling shall be used in the following way: TX_SIG_FRAME_INDEX 8 bits AUX_STREAM_START 22 bits RESERVED 18 bits TX_SIG_FRAME_INDEX: This 8-bit field is the index of the curr...
f2dbd5f462250ffb0478707fe6d5dd25
102 992
6 Transmitter signature using FEFs
f2dbd5f462250ffb0478707fe6d5dd25
102 992
6.1 General description
In this signature method, the transmitter signature is sent in a FEF part. Typically this FEF part would only be sent once per DVB-T2 superframe, and thus sufficiently infrequently to reduce capacity losses to a minimum. However, it may be sent more frequently if a network operator so chooses. Every transmitter in the ...
f2dbd5f462250ffb0478707fe6d5dd25
102 992
6.2 The P1 symbol in the signature FEF part
The signature FEF part shall start with a P1 symbol, as defined in clause 9.8 of [1]. The duration of the P1 symbol is therefore 2 048 T, where T is the "elementary time period for the bandwidth in use", as defined in [1]. The content of the P1 signalling data (S1 and S2 fields) of this signature-FEF P1 symbol shall be...
f2dbd5f462250ffb0478707fe6d5dd25
102 992
6.3 The other-use period
The P1 symbol of the signature FEF shall be immediately followed by the other-use period. The function of this period is to permit the network operator to adjust the total length of the signature FEF part to suit other constraints, or to permit the transmission of an as yet undefined waveform for some future use. EXAMP...
f2dbd5f462250ffb0478707fe6d5dd25
102 992
6.4 The first and second signature periods
The other-use period of the signature FEF part shall be immediately followed by the first and second signature periods, which are identical in form. Each comprises a signature waveform, preceded by a cyclic prefix. Each signature waveform shall have a length of 216 T = 65 536T . The signature waveform shall be preceded...
f2dbd5f462250ffb0478707fe6d5dd25
102 992
6.5 The set of eight discrete sequences
f2dbd5f462250ffb0478707fe6d5dd25
102 992
6.5.1 General
The signature waveforms shall be derived from a set of eight discrete sequences, which are chosen to have generalised orthogonality (GO) properties, see [i.1]. Generalised orthogonality means that each sequence is orthogonal to the other sequences in the set, not only directly, but also when the sequences are cyclicall...
f2dbd5f462250ffb0478707fe6d5dd25
102 992
6.5.2 The initial perfect sequence
The initial perfect sequence shall be the following sequence of complex numbers: ( ) 023 1 ,1,0 , Frank 32 32 mod 32 2 1024 L = ⎪⎭ ⎪⎬ ⎫ ⎪⎩ ⎪⎨ ⎧ = ⎥⎦ ⎥ ⎢⎣ ⎢ π q e q q j where x⎣⎦ represents the floor of x, the greatest integer whose value does not exceed x, and j = −1. This sequence is of length 1 024 elements. The elem...
f2dbd5f462250ffb0478707fe6d5dd25
102 992
6.5.3 The Hadamard sequences
The Hadamard sequences shall be the rows of the following Hadamard matrix: Hadamard8 = 1 1 1 1 1 1 1 1 1 −1 1 −1 1 −1 1 −1 1 1 −1 −1 1 1 −1 −1 1 −1 −1 1 1 −1 −1 1 1 1 1 1 −1 −1 −1 −1 1 −1 1 −1 −1 1 −1 1 1 1 −1 −1 −1 −1 1 1 1 −1 −1 1 −1 1 1 −1 ⎡ ⎣ ⎢ ⎢ ⎢ ⎢ ⎢ ⎢ ⎢ ⎢ ⎢ ⎢ ⎤ ⎦ ⎥ ⎥ ⎥ ⎥ ⎥ ⎥ ⎥ ⎥ ⎥ ⎥
f2dbd5f462250ffb0478707fe6d5dd25
102 992
6.5.4 The intermediate set of GO sequences
The intermediate set of eight length-8 192 sequences shall be constructed as follows. (This follows the general method of Section III.C (2) of [i.2], with parameter d =1, which itself incorporates the same author's Procedure 1 as its last stage.) Let 023 1 ,1,0 where , L = q cq , denote the values of the perfect sequen...
f2dbd5f462250ffb0478707fe6d5dd25
102 992
6.5.5 The final set of GO sequences
The final set of eight GO discrete sequences is formed by re-applying the Procedure 1 of [i.2] to the intermediate set ′ S defined in clause 6.5.4. Consider the intermediate set ′ S as an n × m matrix (having the n sequences ′ s i as its rows), and take its transpose ′ S T , so that the sequences now form its columns. ...
f2dbd5f462250ffb0478707fe6d5dd25
102 992
6.6 The band-limited waveforms
f2dbd5f462250ffb0478707fe6d5dd25
102 992
6.6.1 General
The discrete sequences defined in clause 6.6 cannot be emitted as they stand, as they would occupy too great a bandwidth. The bandwidth needs to be constrained to match that of the DVB-T2 signal into which the waveforms will be inserted. This shall be done in the following defined manner, in order that the correlation ...
f2dbd5f462250ffb0478707fe6d5dd25
102 992
6.6.2 The 64K DFT
The discrete spectrum Vh,k of each sequence sh defined in clause 6.5 shall be calculated as follows: Vh,k = sh,i e−j2π ik N i=0 N −1 ∑ k = 0,1,L N −1 ( ) where N = 65536. The values Vh,k denote the spectral components of the sequence with index h where each k corresponds to a baseband frequency k fU = k TU . For k ≥N 2...
f2dbd5f462250ffb0478707fe6d5dd25
102 992
6.6.3 The filtering window and its application
The discrete spectrum of each sequence shall be both truncated and shaped by the use of the following window: W ′ k = 0.42+0.5cosπ ′ k KH ⎛ ⎝ ⎜ ⎞ ⎠ ⎟ +0.08cos2π ′ k KH ⎛ ⎝ ⎜ ⎞ ⎠ ⎟ −KH ≤′ k ≤KH , 0 otherwise ⎧ ⎨ ⎪ ⎩ ⎪ where KH = 27264. The windowed spectrum of each sequence shall be calculated as: X h, ′ k =W ′ k ′ V h,...
f2dbd5f462250ffb0478707fe6d5dd25
102 992
6.7 Modulation - the emitted waveform
This clause defines the emitted waveform in a manner closely analogous to clause 9.5 of the DVB-T2 specification [1]. Clause 9.5 of [1] defines the emitted T2 signal "when neither FEFs nor PAPR reduction are used". It starts with an arbitrary origin for time t at the start of a particular T2 frame, and counts out T2 fr...
9123564b9bba0c09c2382f92ed1ba380
102 950-2
1 Scope
The purpose of the present document is to provide Test Suite Structure and Test Purposes (TSS & TP) for conformance tests of the conformance test suite for TTCN-3 as defined in ETSI ES 201 873-1 [1] in compliance with the relevant guidance given in the pro forma for TTCN-3 reference test suite ETSI TS 102 995 [4]. In t...
9123564b9bba0c09c2382f92ed1ba380
102 950-2
2 References
9123564b9bba0c09c2382f92ed1ba380
102 950-2
2.1 Normative 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 referenced document (including any amendments) applies. Referenced documents which a...
9123564b9bba0c09c2382f92ed1ba380
102 950-2
2.2 Informative 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 referenced document (including any amendments) applies. NOTE: While any hyperlinks i...
9123564b9bba0c09c2382f92ed1ba380
102 950-2
3 Definition of terms, symbols and abbreviations
9123564b9bba0c09c2382f92ed1ba380
102 950-2
3.1 Terms
For the purposes of the present document, the terms given in ISO/IEC 9646-1 [2], ISO/IEC 9646-7 [3], ETSI ES 201 873-1 [1] (TTCN-3) and the following apply: Abstract Test Suite (ATS): test suite composed of abstract test cases ICS pro forma: document, in the form of a questionnaire, which when completed for an implemen...
9123564b9bba0c09c2382f92ed1ba380
102 950-2
3.2 Symbols
Void.
9123564b9bba0c09c2382f92ed1ba380
102 950-2
3.3 Abbreviations
For the purposes of the present document, the following abbreviations apply: ATS Abstract Test Suite ICS Implementation Conformance Statement ISO International Organization for Standardization IUT Implementation Under Test IXIT Implementation eXtra Information for Testing MTS Methods for Testing and Specification OSI O...
9123564b9bba0c09c2382f92ed1ba380
102 950-2
4 Test Suite Structure (TSS)
The Test Suite Structure is in close alignment with V4.14.1 of ETSI ES 201 873-1 [1], containing: a) positive syntactical tests ("Syn" filename prefix of the test case name); b) positive semantical tests ("Sem" filename prefix of the test case name); c) negative syntactical tests ("NegSyn" filename prefix of the test c...
ae46d4a064bbd179e81aa4eea2c8ee4d
103 161-2
1 Scope
ae46d4a064bbd179e81aa4eea2c8ee4d
103 161-2
1.1 IPCablecom Overview
The IPCablecom project defines interface specifications that can be used to develop interoperable equipment capable of providing packet-based voice, video and other high-speed multimedia services over hybrid fibre coax (HFC) cable systems utilizing the DOCSIS® protocol [i.14]. Any reference to DOCSIS® in the present do...
ae46d4a064bbd179e81aa4eea2c8ee4d
103 161-2
1.2 IPCablecom Motivation
The emergence of the Internet Protocol (IP) as the standard transport for packet data networks has enabled a revolution in communications services and applications. NOTE: IPCablecom 1.5 supports only IPv4 at the present time. This online revolution is demonstrated by the widespread use of email, chat groups, music, vid...
ae46d4a064bbd179e81aa4eea2c8ee4d
103 161-2
1.3 IPCablecom Project Phasing
The IPCablecom architecture is designed to be a robust, complete, end-to-end broadband architecture that supports voice, video, and other multimedia services. The architecture is capable of supporting millions of subscribers over multiple cable operator networks. It is understood that the initial focus of the IPCableco...
ae46d4a064bbd179e81aa4eea2c8ee4d
103 161-2
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...
ae46d4a064bbd179e81aa4eea2c8ee4d
103 161-2
2.1 Normative references
The following referenced documents are necessary for the application of the present document. Not applicable.
ae46d4a064bbd179e81aa4eea2c8ee4d
103 161-2
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-3: "Access, Terminals, Transmission and Multiplexing (ATTM); Integrated Broadband Cable and Television Networks; IPCablecom 1.5; Part ...
ae46d4a064bbd179e81aa4eea2c8ee4d
103 161-2
3 Definitions and abbreviations
ae46d4a064bbd179e81aa4eea2c8ee4d
103 161-2
3.1 Definitions
For the purposes of the present document, the following terms and definitions apply: access control: limiting the flow of information from the resources of a system only to authorized persons, programs, processes or other system resources on a network admitted: allowed asymmetric key: encryption key or decryption key u...
ae46d4a064bbd179e81aa4eea2c8ee4d
103 161-2
3.2 Abbreviations
For the purposes of the present document, the following abbreviations apply: ANC Announcement Controller ANP Announcement Player ETSI ETSI TS 103 161-2 V1.1.1 (2011-10) 12 ANS Announcement Server ASP Audio Server Protocol BPI+ Baseline Privacy Interface Plus CA Call Agent CDR Call Detail Record CIC Circuit Identificati...
ae46d4a064bbd179e81aa4eea2c8ee4d
103 161-2
4 Void
ae46d4a064bbd179e81aa4eea2c8ee4d
103 161-2
5 IPCablecom 1.5
IPCablecom 1.5 is a definition for the specifications that define the IPCablecom 1.5 reference architecture. In this version of the architecture framework, the emphasis is on specification of: • the subscriber environment and its interface requirements to the IPCablecom network including the DOCSIS® HFC access network,...